Hi, Chris Hofstaedtler <z...@debian.org> writes:
> On Mon, Jul 28, 2025 at 11:27:17AM +0200, Carsten Leonhardt wrote: >> Hi, >> >> my mail from last week didn't receive any feedback. >> >> Let's look at this another way: I think this boils down to the question >> what kind of support we will need to give after the release. My take is >> that it will be either: >> >> a) users where the upgrade didn't go through because they didn't affirm >> that their systems are fit for the upgrade of the bacula database >> (very easy and quick to fix). > > Note that this is only true, _if_ the upgrade is aborted before > anything else was done by APT. If APT started installing packages, > and there are ordering issues, users can very well end up in a > situation that is very hard to recover from. > > One example that was found is #1108193 and fixed. > Another is #1109119, with currently no resolution in sight. > As such aborting upgrades seems very risky this time. > > Chris should we recommend upgrading to bacula from backports before the dist-upgrade in the release notes? That will perform the database upgrade and seems like an easy workaround. Regards Carsten
