Jonas Smedegaard <d...@jones.dk> (2014-11-25): > August 8th, Debian began supporting¹ choice among several init systems. > August 21st, Debian changed² default init. > > To me, flexibility is an important feature of Debian. I am excited that > Debian extends its flexibility to cover several init systems. > > Others agree, apparently³: Among those testing our system while this new > flexibility is in place, ~20% use a non-default init system. > > For fresh installs, picking a non-default init requires a workaround: > First install default init system, then replace with your own choice. > Remember to also check for and purge any cruft pulled in by that detour. > > October 17th a fix was proposed at <https://bugs.debian.org/668001#20>. > > @Testers of Debian: Please test debootstrap with that patch applied and > report your experiences, good and bad, to <668...@bugs.debian.org>. > > @Debian-installer team: Please reconsider applying that patch. If not > targeted Jessie then in another suite: Any degree of adoption eases > ability to test, which in turn eases ability to adopt further.
I'm not sure why people seem to believe that broadcasting a call for tests through their blog, Planet Debian, various Debian mailing lists, etc. is going to change anything here. I've already mentioned that having debootstrap stop pulling an init system might make sense at some point. In the meanwhile, debootstrap is not going to receive any patching in the dependency resolving area. KiBi. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141125173133.gk6...@mraw.org
