[pkg-bacula-devel] Handling DB Upgrades for 11

[Mario Pranjic]

On 12/23/20 8:48 AM, Sven Hartge wrote:
> I currently lean towards the approach to patch upstreams upgrade files and
> remove every branching path that is not used by us, for example the ones
> upgrading from 5.x or 7.x to 11, as those could only happen when a user
> tries to upgrade from Debian 8 or 9 directly to Debian 11, which is
> something not supported by Debian as a whole.
>
> By removing all the branching paths we would get a clean upgrade script
> the extractor would work on again *and* the script would be still usable
> in case a user wants/needs to do a fully manual non-dbconfig upgrade.
I like the idea. No need to mess with stuff we don't need and no harm 
done if we ditch it.

As for issues with dbupgrade script and diff between clean install and 
upgrade from 9.6.7 in db structure, I will report it today with some 
examples om bacula-devel list.

Best regards,

--
Mario.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-bacula-devel/attachments/20201223/85dfba2f/attachment.sig>