On Sat, 2010-12-04 at 15:26 +0100, Loïc Minier wrote: > On Sat, Dec 04, 2010, Roger Leigh wrote: > > Are all Ubuntu releases affected, or just the later ones? When was > > sysvinit removed? > > The current Ubuntu development release (natty, to be 11.04) is not > affected anymore as I fixed build-essential there, but pretty much all > the maintained one are affected. We still support 6.06 (dapper) which > will be end-of-lifed in 2011/06 (+5y), and it didn't have upstart, but > all releases since 6.06 had upstart: > upstart | 0.3.9-2 | hardy | source, amd64, i386 > upstart | 0.3.9-8 | jaunty | source, amd64, i386 > upstart | 0.6.3-10 | karmic | source, amd64, i386 > upstart | 0.6.5-6 | lucid | source, amd64, i386 > upstart | 0.6.6-3 | maverick | source, amd64, i386 > in particular 10.04 (lucid), which is to be supported until 2015/04. > For clarity, the above are the currently supported Ubuntu releases affected by the bug. There are also the EOL releases 6.10 (with upstart 0.2.7-7), 7.04, 7.10, and 8.10) and it may be desirable for some people to build things in these EOL chroots.
> I'm not sure 6.06 is a big issue, but Jamie is in the Ubuntu security > team, so he can comment about that one. My guess is that sysvinit is > already installed in the chroot anyway, so the sysvinit workaround > doesn't hurt. 6.06 is not an issue for our team as the way that we build our chroots includes sysvinit. The patch as submitted is currently quite simple, but the technique could be refined such that we check for only specific releases, but I don't think that this is required since in natty and latter there is no sysvinit to remove from the list anyway. -- Jamie Strandboge | http://www.ubuntu.com
signature.asc
Description: This is a digitally signed message part
