Your message dated Tue, 12 Dec 2023 15:46:03 +0100
with message-id <[email protected]>
and subject line Re: busybox: possible file loss during upgrade arising from
/usr-merge
has caused the Debian Bug report #1057218,
regarding resolvconf: possible file loss in upgrades due to /usr-merge
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1057218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057218
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: resolvconf
Version: 1.92
Severity: serious
User: [email protected]
Usertags: dep17p1
Hi Andrej,
I am very sorry for not having seen this earlier. There is a tricky case
where upgrading from bookworm to sid may loose files if you
simultaneously change implementation. I am working on the analysis and
it probably looks like:
resolvconf:
1.91+nmu1:
issues:
- files:
- /sbin/resolvconf
others:
systemd-resolved:
255~rc3-3: unstable
what: ineffective conflicts
suites: bookworm|trixie
'1.92':
issues:
- files:
- /usr/sbin/resolvconf
others:
openresolv:
3.12.0-1: bullseye
3.12.0-3: bookworm
3.13.1-1: trixie|unstable
systemd-resolved:
252.17-1~deb12u1: bookworm
252.19-1~deb12u1: bookworm-proposed-updates
252.5-2~bpo11+1: bullseye-backports
254.5-1: trixie
254.5-1~bpo12+2: bookworm-backports
what: ineffective conflicts
suites: unstable
This is a meant as a migration blocker. If you want to migrate
resolvconf for other reasons, consider uploading a revert. Otherwise,
please wait a bit for me to better understand the situation.
I am filing a similar bug with way more details against systemd-sysv.
Helmut
--- End Message ---
--- Begin Message ---
Hi,
On Fri, Dec 01, 2023 at 07:07:20PM +0100, Helmut Grohne wrote:
> I am very sorry to tell you that I found a contrieved /usr-merge problem
> with the busybox upload. In essence, Conflicts allow for concurrent
> unpacks in weired situations. As a consequence, you may miss the busybox
> binary if you upgrade from bookworm to trixie and change from
> busybox-static to busybox or vice versa in the process. I do not have a
> solution at this time and file this bug as a migration blocker. If you
> want to get rid of the rc bug, you may upload a revert. Otherwise,
> please wait until we have a better understanding of the problem.
We now have a better understanding.
In particular, the loss scenario requires "scheduling a package for
removal" using "dpkg --set-selections" and then unpacking a conflicting
package. apt only ever does this when it has to perform a temporary
removal. The only known scenario where this was observed for real is
when two packages are upgraded and the updated versions mutualy conflict
with old versions of one another. This is not the case for busybox and
also not for openresolv. For systemd, we will be restoring lost files in
postinst. If we ever encounter real loss scenarios for either package,
it can be mitigated as follows:
1. Identify all of the lost files.
2. For all regular files, create backup copies in your package in the
data.tar. I suggest to use hard links to avoid increasing the package
size.
3. In postinst check for absence of any lost file and restore it from
the backup copy.
In case the lost file is not a regular file, no backup copy is
necessary. Directories and symbolic links can be restored directly.
This mitigation needs to be in effect until the trixie release and then
can be removed.
I am now closing these bugs, because apt handles the multiple
providers-for-the-same-facility situation without temporary removals.
For instance, if you have a bookworm systemd with busybox and miniramfs
(an arbitrary package that happens to depend on busybox). Then you
change your sources to sid (which has a /usr-moved busybox) and apt
install busybox-static (thus changing provider). Then apt will remove
busybox (from bookworm with files in /sbin) before installing
busybox-static (from sid with files in /usr/sbin) hence not causing the
loss scenario. What I'm saying about busybox here likewise holds for
openresolv.
The way to experience this loss appears to require using dpkg directly
and we consider that sufficiently unlikely that we don't handle this
case. The release-notes already require upgrades to be performed with
apt and we can add an additional warning about this case.
Helmut
--- End Message ---
