Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #741465
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#825423: supermin + sbuild + linux-image = broken chroot |
| Date | 2016-05-27 00:00 +0200 |
| Message-ID | <rDbtU-3dI-5@gated-at.bofh.it> (permalink) |
| References | <rD9BM-26y-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
[Multipart message — attachments visible in raw view] - view raw
Control: reassign -1 src:linux Control: severity -1 normal On Thu, 2016-05-26 at 21:48 +0200, Santiago Vila wrote: > Package: src:linux,src:supermin,src:sbuild > Severity: serious > Justification: Breaks other packages > X-Debbugs-Cc: sanvila@debian.org > > Dear maintainers: > > I think this is a bug in linux, but I'm not 100% sure. > Please do agree with the other maintainers on which package is to blame. > > > I'm building packages for stretch using sbuild and a stretch chroot. > > The machine itself is also running stretch (it's a qemu virtual > machine, but this is irrelevant here). > > When I build the supermin package, linux-image-amd64 is installed as a > build-dependency. > > When the package has been built and the build-dependencies are removed > afterwards, this is what happens: As an aside, disposable chroots are a far better way to achieve reliable clean builds than removing build-dependencies after building. [...] > Hit:1 http://httpredir.debian.org/debian stretch InRelease > Reading package lists... > Reading package lists... > Building dependency tree... > Reading state information... > You might want to run 'apt-get -f install' to correct these. > The following packages have unmet dependencies: > linux-image-4.5.0-2-amd64 : Depends: kmod but it is not installed > Depends: linux-base but it is not installed > Depends: initramfs-tools (>= 0.110~) but it is not installed or > linux-initramfs-tool > E: Unmet dependencies. Try using -f. > -------------------------------------------------------------------------------- > > i.e. every other package fails from this point. > > The chroot is broken and it requires manual intervention to be fixed. > > > The reason for this, I think, is that linux-image refuses to be uninstalled > if it detects that it's the same version which is running in the system. [...] Not exactly. It tries to prompt you using debconf, with the default being to abort the uninstallation. But of course sbuild presumably sets DEBIAN_FRONTEND=noninteractive since you should never be prompted during an automatic build... I'm inclined to add a check to linux-image prerm scripts that skips the question when DEBIAN_FRONTEND=noninteractive. Aside from that, I might add the check for a chroot or container, if there's a simple way to do that. Ben. -- Ben Hutchings Usenet is essentially a HUGE group of people passing notes in class. - Rachel Kadel, `A Quick Guide to Newsgroup Etiquette'
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#825423: supermin + sbuild + linux-image = broken chroot Santiago Vila <sanvila@unex.es> - 2016-05-26 22:00 +0200
Bug#825423: supermin + sbuild + linux-image = broken chroot Hilko Bengen <bengen@debian.org> - 2016-05-26 23:10 +0200
Bug#825423: supermin + sbuild + linux-image = broken chroot Ben Hutchings <ben@decadent.org.uk> - 2016-05-27 00:00 +0200
Bug#825423: supermin + sbuild + linux-image = broken chroot Aurelien Jarno <aurelien@aurel32.net> - 2016-06-04 11:30 +0200
Bug#825423: supermin + sbuild + linux-image = broken chroot Ben Hutchings <ben@decadent.org.uk> - 2016-06-04 17:40 +0200
Bug#825423: supermin + sbuild + linux-image = broken chroot Santiago Vila <sanvila@unex.es> - 2016-06-04 18:10 +0200
Bug#825423: supermin + sbuild + linux-image = broken chroot Ben Hutchings <ben@decadent.org.uk> - 2016-06-04 19:20 +0200
csiph-web