Bug#765076: general: No way to have a clean chroot for building packages
On Sun, Jun 19, 2016 at 06:19:09PM +0100, Simon McVittie wrote: > Package: init > Version: 1.34 > > On Mon, 13 Oct 2014 at 13:12:42 +0200, Santiago Vila wrote: > > Before systemd arrived, it was possible to have a chroot free from > > init packages (not needed to build packages). > > This was the case in jessie due to the transitional packages necessary > to move from sysvinit to systemd-sysv|sysvinit-core. In stretch, it > should now be possible again: init is non-Essential, and has dropped > from Priority: required to Priority: important. Unfortunately, as of today, it is not anymore possible to upgrade from jessie to stretch: # apt-get upgrade [...] # apt-get dist-upgrade [...] E: This installation run will require temporarily removing the essential package sysvinit-utils:amd64 due to a Conflicts/Pre-Depends loop. This is often bad, but if you really want to do it, activate the APT::Force-LoopBreak option. E: Internal Error, Could not early remove sysvinit-utils:amd64 (2) I can reproduce this on a jessie system with very few packages installed and this single line in sources.list: deb http://httpredir.debian.org/debian stretch main If this problem is the result of fixing this bug, I would rather keep the bug unfixed and leave things as before. Thanks.
Bug#765076: general: No way to have a clean chroot for building packages
Control: reassign -1 general Control: retitle -1 init should not be Essential On Tue, Dec 16, 2014 at 12:04:17 +0100, Holger Levsen wrote: control: reassign -1 debootstrap control: retitle -1 variant=buildd should not install init systems Hi, On Montag, 13. Oktober 2014, Joey Hess wrote: It seems reasonable for debootstrap --variant=buildd to omit any init systems, if it doesn't already. seems reasonable indeed, reassigning accordingly. That means making init non-essential. Which is not debootstrap's responsibility. Cheers, Julien signature.asc Description: Digital signature
Bug#765076: general: No way to have a clean chroot for building packages
control: reassign -1 debootstrap control: retitle -1 variant=buildd should not install init systems Hi, On Montag, 13. Oktober 2014, Joey Hess wrote: It seems reasonable for debootstrap --variant=buildd to omit any init systems, if it doesn't already. seems reasonable indeed, reassigning accordingly. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#765076: general: No way to have a clean chroot for building packages
control: reassign -1 general signature.asc Description: This is a digitally signed message part.
Bug#765076: general: No way to have a clean chroot for building packages
Package: general Before systemd arrived, it was possible to have a chroot free from init packages (not needed to build packages). Now if I do apt-get dist-upgrade inside a minimal chroot (using schroot here), I get this: The following NEW packages will be installed: acl adduser dmsetup init libcap2-bin libcryptsetup4 libdevmapper1.02.1 libkmod2 libncursesw5 libprocps3 libudev1 procps systemd systemd-sysv udev 0 upgraded, 15 newly installed, 0 to remove and 0 not upgraded. Need to get 4614 kB of archives. After this operation, 21.9 MB of additional disk space will be used. Do you want to continue? [Y/n] I'm not sure what package is to blame here (which is why I'm using general). Maybe it is the introduction of a new essential package called init, combined with the fact that apt-get insists that all essential packages should be installed. In either case, the end result is that I'm forced to install init packages in a chroot which is used to build packages, something that didn't happen in wheezy. This is clearly a regression and I hope that it is fixed before the release of jessie. Please reassign/clone as appropriate. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765076: general: No way to have a clean chroot for building packages
On 2014-10-13 13:12, Santiago Vila wrote: Package: general Before systemd arrived, it was possible to have a chroot free from init packages (not needed to build packages). [...] In either case, the end result is that I'm forced to install init packages in a chroot which is used to build packages, something that didn't happen in wheezy. This is clearly a regression and I hope that it is fixed before the release of jessie. Please reassign/clone as appropriate. Thanks. In Wheezy, sysvinit was essential, so you would have the same issue in stable (just with a different init system). ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765076: general: No way to have a clean chroot for building packages
On Mon, Oct 13, 2014 at 01:43:29PM +0200, Niels Thykier wrote: In Wheezy, sysvinit was essential, so you would have the same issue in stable (just with a different init system). Oops. You are right. So this is not really a regression, only an undesirable feature that we have had in the system for a long time. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765076: general: No way to have a clean chroot for building packages
On Oct 13, Santiago Vila sanv...@unex.es wrote: Oops. You are right. So this is not really a regression, only an undesirable feature that we have had in the system for a long time. I would be happy to fix it FWIW, but I am not sure that there is a way to do it outside of debootstrap which will not cause more issues. -- ciao, Marco signature.asc Description: Digital signature
Bug#765076: general: No way to have a clean chroot for building packages
On Mon, Oct 13, 2014 at 02:34:39PM +0200, Marco d'Itri wrote: On Oct 13, Santiago Vila sanv...@unex.es wrote: Oops. You are right. So this is not really a regression, only an undesirable feature that we have had in the system for a long time. I would be happy to fix it FWIW, but I am not sure that there is a way to do it outside of debootstrap which will not cause more issues. Found a workaround: Using equivs, I created a package called init version 2. Then apt-get dist-upgrade does not want to install the usual init package. I'm starting to believe this should be fixed in apt. A real fix would be a way to tell apt-get not to install new essential packages unless they are dependencies of currently installed packages. Is there not an apt.conf setting for that yet? If the system is not so broken that dpkg/apt-get are still able to install new essential packages, then apt-get does not really help by installing an essential package that I removed by hand, because I could install it by hand myself. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765076: general: No way to have a clean chroot for building packages
Santiago Vila wrote: Before systemd arrived, it was possible to have a chroot free from init packages (not needed to build packages). It seems reasonable for debootstrap --variant=buildd to omit any init systems, if it doesn't already. -- see shy jo signature.asc Description: Digital signature
Bug#765076: general: No way to have a clean chroot for building packages
Hi, Joey Hess jo...@debian.org writes: Santiago Vila wrote: Before systemd arrived, it was possible to have a chroot free from init packages (not needed to build packages). It seems reasonable for debootstrap --variant=buildd to omit any init systems, if it doesn't already. It seems a bit hacky to have debootstrap exclude essential packages. The proper solution is (IMHO) to work on dropping the essential bit on init and work on downgrading its priority from required to important. Having it no longer essential would stop apt from wanting to reinstall it. The priority reduction is (again IMHO) reasonable as there are use cases where one does not need init, like chroot environments. This seems pretty similar to the kernel. For this we probably need to a, make sysv-rc essential (for invoke-rc.d) and b, make sure no package calls init q or similar. Last I heard there were still one or two packages doing so in their postinst. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765076: general: No way to have a clean chroot for building packages
control: reassign -1 debootstrap control: retitle -1 variant=buildd should not install init systems Hi, On Montag, 13. Oktober 2014, Joey Hess wrote: It seems reasonable for debootstrap --variant=buildd to omit any init systems, if it doesn't already. seems reasonable indeed, reassigning accordingly. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#765076: general: No way to have a clean chroot for building packages
Holger Levsen hol...@layer-acht.org (2014-10-13): control: reassign -1 debootstrap control: retitle -1 variant=buildd should not install init systems Hi, On Montag, 13. Oktober 2014, Joey Hess wrote: It seems reasonable for debootstrap --variant=buildd to omit any init systems, if it doesn't already. seems reasonable indeed, reassigning accordingly. On the other hand, reassigning bug reports to packages without putting their maintainers in Cc is very much not reasonable. KiBi. signature.asc Description: Digital signature
