Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #57419
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't |
| Date | 2017-04-02 15:40 +0200 |
| Message-ID | <trNTz-133-7@gated-at.bofh.it> (permalink) |
| References | <tazai-2DY-11@gated-at.bofh.it> <trIAx-61K-1@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: tag -1 pending On Sun, 2017-04-02 at 09:50 +0200, intrigeri wrote: [...] > I see no obvious perfect solution. The options I can think of are: > > 1. Keeping things as-is: > - Affected systems: partial upgrades, systems where Recommends were > manually disabled; I don't think that full upgrades from Jessie > to Stretch are affected, since the initramfs is updated via > a dpkg trigger, after all packages have been upgraded. > In other words, only advanced users are affected. > - Impact: initramfs is not generated, and APT/dpkg exit with an > error message that tells the user what the problem is, and > suggests how to fix it. > > 2. Making initramfs-tools-core depend on a new enough busybox: pulls > busybox (installed size 746 kB, no dependencies besides libc6) even > on systems that don't need it, i.e. those that haven't cryptsetup > installed, and haven't busybox already pulled by anything else. [...] How about "Breaks: busybox (<< 1:1.22.0-17~)"? I think that does the job. I've actually committed that change but failed to upload yet. Ben. -- Ben Hutchings It is impossible to make anything foolproof because fools are so ingenious.
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't Jan Echternach <jan@goneko.de> - 2017-02-14 01:30 +0100
Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't intrigeri <intrigeri@debian.org> - 2017-04-02 10:00 +0200
Bug#855094: [pkg-cryptsetup-devel] Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't Guilhem Moulin <guilhem@guilhem.org> - 2017-04-02 10:20 +0200
Bug#855094: [pkg-cryptsetup-devel] Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't intrigeri <intrigeri@debian.org> - 2017-04-02 10:50 +0200
Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't Ben Hutchings <ben@decadent.org.uk> - 2017-04-02 15:40 +0200
Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't Ben Hutchings <ben@decadent.org.uk> - 2017-04-02 16:00 +0200
Processed: Re: Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't owner@bugs.debian.org (Debian Bug Tracking System) - 2017-04-02 15:40 +0200
Bug#855094: marked as done (initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't) owner@bugs.debian.org (Debian Bug Tracking System) - 2017-04-09 02:10 +0200
csiph-web