[MIR] libseccomp

 * Does it FTBFS currently? builds fine with only main enabled
 * Does it have a test suite? yes, but it is disabled in the build
 * Does Ubuntu carry a delta? yes, but only to adjust it to build on i386 and amd64
 * it has a symbols file
 * Does it have a bug subscriber in Ubuntu? no
 * Does it have a watch file? yes
 * Is its update history slow or sporadic? slow
 * Is the current release packaged? no. Upstream indicates "Change the API to be context-aware; eliminates all internal state but breaks compatibility with the previous 0.1.0 release"
 * Will entering main make it harder for the people currently keeping it up to date? possibly-- the driver for this MIR is LXC and one of the two main LXC maintainers in Ubuntu is not core-dev (the other is)
 * Lintian warnings: clean
 * Is debian/rules a mess? no, it's fine
 * Errors/warnings during the build: no
 * Incautious use of malloc/sprintf: no (malloc calls are all properly checked)
 * Uses of sudo or LD_LIBRARY_PATH: no
 * Important bugs (crashers, etc) in Debian or Ubuntu: no. mostly around documentation
 * Does the package have a CVE history? no
 * An in depth security audit is not warranted at this time

While I'd like to see this promoted to main and seeded on its own to promote its use (as opposed to just because lxc wants it), there is some work that is still needed. Conditional ACK if the following are met:
 * the test suite is enabled in the build
 * ensure the Ubuntu delta is upstreamed to Debian
 * a bug subscriber is added
 * the package is updated to 1.0.1 (and submitted to Debian)

Thanks for the review and sorry for the delay in my reply.

Ubuntu was brought back in sync with Debian recently and got slightly out of sync again today as I added a delta to run the testsuite at build time. Said delta has been submitted to Debian, so hopefully we'll get back in sync in the near future.

I subscribed to the package so any bug will be showing up in my containers-related mail folder.

I think that's all the concerned above addressed, let me know if you need anything more.

The conditions of the MIR have now been met (except for the bug subscriber, which I maintain would is a good idea). ACK

I seeded libseccomp-dev to promote its use and adjusted the overrides:
Override component to main
libseccomp 1.0.1-2 in raring: universe/libs -> main
libseccomp-dev 1.0.1-2 in raring amd64: universe/libdevel/optional -> main
libseccomp-dev 1.0.1-2 in raring i386: universe/libdevel/optional -> main
libseccomp1 1.0.1-2 in raring amd64: universe/libs/optional -> main
libseccomp1 1.0.1-2 in raring i386: universe/libs/optional -> main
Override [y|N]? y
5 publications overridden.