[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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.


Reply to: