shawn wrote: > Package: debootstrap > Version: 1.0.39 > Severity: normal > Tags: d-i > > if you use debootstrap unstable foo --include=systemd-sysv > --exclude=sysvinit > the install fails dpkg: regarding .../systemd-sysv_44-1_i386.deb containing systemd-sysv: systemd-sysv conflicts with sysvinit sysvinit (version 2.88dsf-22.1) is present and installed. dpkg: error processing /var/cache/apt/archives/systemd-sysv_44-1_i386.deb (--unpack): conflicting packages - not installing systemd-sysv The problem is that debootstrap handles --exclude before adding required priority packages to its list, so sysvinit is added back then. #557322 is a prior bug report about this, and has a patch that at least handles excluding it from the required priority packages, although it may still be added back by dependency resolution. > besides having this annoying for testing, esp with systemd-nspawn, > having this work will > be a prerequisite for having systemd be the default, or at least > installable in debian-installer I don't think that's necessarily true, there are many ways d-i could handle getting systemd installed, and if it were made the default, --exclude would not be needed at all. -- see shy jo
Attachment:
signature.asc
Description: Digital signature