On Thu, Dec 26, 2013 at 10:03:12AM -0800, Russ Allbery wrote: > Niels Thykier <niels@thykier.net> writes: > > We have deployed a change in Britney that causes her to pay more > > attention to essential packages. In particular, all packages now have > > to be co-installable with the essential set. Previously, a package > > could conflict with a essential package. It would still be considered > > installable by Britney as long as the transitive dependency closure of > > the package did not (explicitly) require the essential package it > > conflicted with. > This has implications for upstart, doesn't it? It still conflicts with > sysvinit, which is essential. On Thu, Dec 26, 2013 at 10:23:42AM -0800, Josh Triplett wrote: > Here's the complete list of packages in latest unstable that would > violate this new criterion: > ~$ aptitude search '?conflicts(?essential)' > p systemd-sysv - system and service manager - SysV links > p upstart - event-based init daemon > This new criterion would seem to make life difficult for the maintainers > of these and other potential future alternatives to the current set of > essential packages. Well, the fix is known; I was waiting for feedback on <http://lists.debian.org/debian-devel/2013/11/msg00389.html> before uploading, but there hasn't been any except for ratholing about openrc. I'll go ahead and upload the fixed sysvinit to NEW today. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slangasek@ubuntu.com vorlon@debian.org
Attachment:
signature.asc
Description: Digital signature