MIR libdlrestrictions1 and libdlrestrictions-dev

[Scott Kitterman]

Binary package hint: pkg-kde-tools
Availability: Part of pkg-kde-tools, already in Main. Built on all archs.
Rationale: Needed as build-depends/depends for KDE packaging from Debian. In not promoted would add significant diff/maintenance burden. Should also increase reliability of packages and reduce risk of unexplained crashes due to binary incompatibility.
Security: No issues, see below.
Quality assurance:
Has good defaults and works with KDE packages it's intended to work with.
No debconf questions.
No outstanding bugs in Debian/Ubuntu
http://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=pkg-kde-tools
https://bugs.launchpad.net/ubuntu/+source/pkg-kde-tools
The package is maintained well in Debian. kubuntu-dev will deal with Ubuntu issues if any.
No exotic hardware.
Uses test suite during build.
UI standards: N/A
Dependencies:
All build and binary dependencies are in Main
Standards compliance: Packages are FHS and Debian policy compliant
Maintenance: The packages are well maintained in Debian and will be looked after in Ubuntu by kubuntu-dev.
 Background information:
The package descriptions should is good.
Security checks
Check how many vulnerabilities the package had in the past and how they were handled by upstream and the Debian/Ubuntu package:
No history of security issues.
No security relevant binaries.

[Colin Watson (cjwatson)]

I've pre-promoted this to unblock the KDE team. There's been no communication to archive admins that I've seen of binary packages from a source that's already in main needing MIR approval before promotion, and had I not happened to look at #ubuntu-release backlog I'd very likely have promoted this without thought.

Since Matthias has said this needs an MIR, by all means conduct a review; that will certainly do no harm. My promotion of these packages isn't irreversible; if the MIR team feels this package is unconscionable, then the transition tracker can be used to track removal of dependencies on it from packages in main, and the pain accruing to the kubuntu-dev team from that will be much the same either way. This just means that they can get on with their work for now.

[Matthias Klose (doko)]

my mistake. it was my understanding that these binary packages come from another source package, in which case it's good to have a report to document that the code was already in main.