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
