On Sun, Mar 16, 2025 at 10:05:57PM +0100, Michael Biebl wrote:
> It's correct that there is no native support in dpkg(-maintscript-helper) to
> transfer ownership of conffiles properly from one package to another.
>
> It is doable though with some contortions, see e.g.
> https://salsa.debian.org/s
It's correct that there is no native support in
dpkg(-maintscript-helper) to transfer ownership of conffiles properly
from one package to another.
It is doable though with some contortions, see e.g.
https://salsa.debian.org/systemd-team/systemd/-/commit/d6483013d5779d4d465a1e174e44a754b941d0e6
On Mon, May 15, 2023 at 10:56:20PM +0200, Andrea Bolognani wrote:
> On Sat, May 13, 2023 at 06:09:22PM +0200, Christoph Anton Mitterer wrote:
> > On Sat, 2023-05-13 at 12:09 +0200, Andrea Bolognani wrote:
> > As said in my message #10 in this bug,... I don't think it's necessary
> > that the conffi
On Sat, May 13, 2023 at 06:09:22PM +0200, Christoph Anton Mitterer wrote:
> On Sat, 2023-05-13 at 12:09 +0200, Andrea Bolognani wrote:
> As said in my message #10 in this bug,... I don't think it's necessary
> that the conffiles are cleaned up exactly the version after they have
> been dropped.
>
On Sat, 2023-05-13 at 12:09 +0200, Andrea Bolognani wrote:
> However, I'm afraid we might have missed our chance.
>
> At this point, nobody is going to be upgrading from 5.6.0-3, but from
> a more recent version of libvirt-daemon-system where the conffiles in
> question are already not considered
On Fri, May 12, 2023 at 04:36:14PM +0200, Christoph Anton Mitterer wrote:
> On Fri, 2023-05-12 at 14:27 +0200, Andrea Bolognani wrote:
> > I think at this point we can assume that most people who have hit the
> > issue on upgrade will have cleaned things up manually by now, so I'd
> > be inclined t
On Fri, 2023-05-12 at 14:27 +0200, Andrea Bolognani wrote:
> I think at this point we can assume that most people who have hit the
> issue on upgrade will have cleaned things up manually by now, so I'd
> be inclined to close the bug and move on.
>
> Any objections?
Well not a strong objection fro
So, this affected upgrades from buster (libvirt 5.0.0) to bullseye
(libvirt 7.0.0).
We're now about to release bookworm (libvirt 9.0.0) and the
rm_conffile snippet is not even present in the package anymore.
I think at this point we can assume that most people who have hit the
issue on upgrade wi
Guess the reason might be that the version used with dpkg-maintscript-
helper rm_conffile could be wrong.
(AFAIU, the version that needs to be specified for that is NOT
the version where the conffile was dropped, but rather "the
latest version of the package whose upgrade should trigger
the operat
Package: libvirt-daemon-system
Version: 6.0.0-2
Severity: normal
/etc/init.d/virtlogd 8b6942d513cc5b6ec130556952577850 obsolete
/etc/init.d/libvirtd 6615f190c140a2e0aeecfc082716d026 obsolete
/etc/init.d/libvirt-guests 7efd4986a88c0f0bd1c5ae9826802b3f obsolete
Those files are not properly clean
10 matches
Mail list logo
