Bacula for 22.04/Jammy

[Babiel]

Hi,

it looks like Bacula / bacula-client has been removed from 22.04/Jammy, while it was and is still available for 21.04.

Is there a chance to get it back in 22.04? That'd be really handy.

Were there specific reasons to remove it? I couldn't find anything useful / official so far.

[ Impact ]

 * bacula 9.6.7-3build1 was removed from 22.04 jammy before release due to FTBFS.

 * The FTBFS was fixed in Debian 9.6.7-4 on March 12, 2022 but not imported in time for the release

 * 9.6.7-4 and 9.6.7-5 (which features an additional cross-compiling fix plus some Debian package cleanups) exists in kinetic+ and both of these build and operate on Jammy

 * Due to this, bacula exists in all releases prior and post jammy, and is missing in jammy only

 * This is a popular bug with 18 people noting it affects them

[ Test Plan ]

 * At least one community user has tested the previously prepared PPA package and has specifically reported success with 2 others noting they are using it

 * A few basic operational autopkgtests exist and pass

 * I downloaded and ran the upstream regression test suite. I ran it against both the upstream git branch ‘Branch-9.6’ as well as the source in our proposed Ubuntu package. There are 4 test failures however they fail with both source trees (not just our version of it). This regression test suite appears to be run manually, sporadically and not automatically. So the fact the other 118 tests all pass OK give me some confidence this package is working largely OK (even if not a perfect record).

[ Where problems could occur ]

 * The regression risk is a little different to normal since there is currently no version of bacula in jammy, however, users will still be upgrading to jammy from a previous version (e.g. focal) and/or may still have the older package installed after having upgraded to jammy and once this SRU is released will upgrade to this version

 * The proposed upload is a no-change from the 9.6.7-5 version that has existed in Debian (testing) since May 2022 and is also released in Kinetic.

 * Debian stable shipped the same upstream version (9.6.7-3) but missing the FTBFS fixes from 9.6.7-4 so these are not as widely tested.

[ Other Info ]

 * Alex Murray has uploaded the package (9.6.7-5~22.04.1), which is currently in the jammy NEW queue. I believe this will need assistance from the teams to get through source new and binary new similar to the recent collected SRU (https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1971093)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Alex Murray (alexmurray)]

As can be seen at https://launchpad.net/ubuntu/+source/bacula/+publishinghistory bacula was removed from Ubuntu during the jammy development cycle as it failed to compile:

> FTBFS, removed from Debian testing, blocks libssl transition; Debian bug #997139

The process to get this back into jammy would be a StableReleaseUpdate - https://wiki.ubuntu.com/StableReleaseUpdates - so a version of bacula which compiles on jammy would have to be prepared and then this procedure can be followed to get it published back into Ubuntu 22.04 LTS.

[Eric Bollengier (ebl)]

Hello,

Bacula 9.6.7 is pretty old, can you upgrade for the tests to 11.0.6 ?

Thanks
Eric

Le mer. 18 mai 2022, 13:55, Alex Murray <email address hidden> a
écrit :

> As can be seen at
> https://launchpad.net/ubuntu/+source/bacula/+publishinghistory bacula
> was removed from Ubuntu during the jammy development cycle as it failed
> to compile:
>
> > FTBFS, removed from Debian testing, blocks libssl transition; Debian
> bug #997139
>
> The process to get this back into jammy would be a StableReleaseUpdate -
> https://wiki.ubuntu.com/StableReleaseUpdates - so a version of bacula
> which compiles on jammy would have to be prepared and then this
> procedure can be followed to get it published back into Ubuntu 22.04
> LTS.
>
> --
> You received this bug notification because you are subscribed to bacula
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1973322
>
> Title:
> Bacula for 22.04/Jammy
>
> Status in bacula package in Ubuntu:
> Confirmed
>
> Bug description:
> Hi,
>
> it looks like Bacula / bacula-client has been removed from
> 22.04/Jammy, while it was and is still available for 21.04.
>
> Is there a chance to get it back in 22.04? That'd be really handy.
>
> Were there specific reasons to remove it? I couldn't find anything
> useful / official so far.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1973322/+subscriptions
>
>

[Alex Murray (alexmurray)]

FYI I have rebuilt the version of bacula for jammy in a PPA - https://launchpad.net/~alexmurray/+archive/ubuntu/lp1973322 - if anyone could give this a test and let me know how it works for you, then we can look at trying to release it via an SRU. Thanks.

[Hiroaki Hashi (hashiz)]

I started testing bacula-client in Alex's repository.
I will run my backup job for a few days.

[Hiroaki Hashi (hashiz)]

I ran a backup job for a few days, using bacula-client in Alex's repository .
This works fine.
I tried the following:
--Incremental backup
--Full Backup
--Restore Files

[Hiroaki Hashi (hashiz)]

I've been testing bacula-server in Alex's repository for a week.
It works fine in my usage.

I testing following environment
Catalog DB: mysql
Storage: FILE storage on NFS mounted NAS
Clients: Ubuntu 22.04 Client x 2

[Kundarsa (kundarsa)]

> As can be seen at
> https://launchpad.net/ubuntu/+source/bacula/+publishinghistory bacula
> was removed from Ubuntu during the jammy development cycle as it failed
> to compile:

I think the make file has -Werror on causing a failure on a depreciation warning for OpenSSL. Can simply remove and release.

[David White (cppege-david-9ei9ny)]

@alexmurray thank you for the work in creating the PPA. Is there any reason this is tracking 9.6.7 rather than a more recent version?

[Lupe Christoph (lupe)]

@alexmurray, thanks for the PPA. I just upgraded to jammy (yeah, I'm late) and found bacula missing. I very grateful for your work. I will replace the remnants the jammy upgrade left with your PPA and report any problems in this ticket.

[Joey (joeysr20det)]

Any news on this? We're really hoping to get this back up and running soon as we're limping by using an alternative. I would have waited on upgrading to this LTS if I would have known this was missing :(

[Joe (cpukid)]

Thanks @alexmurray for the interim solution. Really surprised that Bacula still isn't in 22.04. Seems like an LTS should have added this back fairly quickly. I'm running an LTS exactly because it's a production environment and part of that is to have access to a great backup solution like Bacula.

[Alex Murray (alexmurray)]

FYI I have prepared a backport from the current version in kinetic to jammy - this is now sitting in the New queue - https://launchpad.net/ubuntu/jammy/+queue?queue_state=0&queue_text=bacula - and needs assistance from the SRU team (or perhaps an AA?) to get it into jammy-proposed

[Trent Lloyd (lathiat)]

I have updated the bug description with the SRU template

[Trent Lloyd (lathiat)]

Based on the SRU team discussions about adding packages back into the release afterwards a couple months ago, I believe this should be good to go.

It doesn't appear in the normal SRU queue as it's in state New, rather than unapproved. It can be found here:
https://launchpad.net/ubuntu/jammy/+queue?queue_state=0&queue_text=bacula

Looking to get this approved.

[Robie Basak (racb)]

The SRU team concluded that it is acceptable to re-add bacula to 22.04 as a stable release update. However there are a few things to clear up.

The package version string doesn't seem appropriate to me. I suggest something like 9.6.7-5~ubuntu0.22.04.1 to avoid a potential collision with Debian.

Please amend the Test Plan to rigorously verify a "normal use scenario", and investigate the existing regression test suite failures.

We need security team sign-off please, for any implications for ESM. This may be implied since Alex prepared the upload, but it's safer to be explicit.

Please check for reverse dependencies of bacula in Jammy that might be affected, for example via alternates.

> Is there any reason this is tracking 9.6.7 rather than a more recent version?

22.10 released with 9.6.7-5 and 23.04 with 9.6.7-7. Mantic is still on 9.6.7-7. We cannot introduce into Jammy a package higher than those versions, because otherwise users upgrading from 22.04 up to those would face a functional regression or the inability to receive security updates against this package. If you need a higher version in 22.04, getting software from other sources such as the backports pocket or a snap are your alternative options (but then you need those sources to have the newer version you want, etc).

[Steve Langasek (vorlon)]

Hello Babiel, or anyone else affected,

Accepted bacula into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bacula/9.6.7-5~22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted bacula (9.6.7-5~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

bacula/9.6.7-5~22.04.1 (i386)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#bacula

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Mauricio Faria de Oliveira (mfo)]

Hi Trent (@lathiat),

Apparently, bacula in jammy is no longer required?

If so, the package should be removed from jammy-proposed.
It can be tagged verification failed (or ping an ~ubuntu-archive admin).

Thanks,
Mauricio

[Kevin Morgan (kmu0acc)]

Dear All,

I have successfully installed the following Bacula packages (9.6.7-5~22.04.1), on my system:-

Distributor ID: Ubuntu
Description: Ubuntu 22.04.3 LTS
Release: 22.04
Codename: jammy
Architecture: amd64

which was a fresh installation, not an upgrade, in the following order:-

"bacula-director-mysql/jammy-proposed" (N.B. I had to temporarily uninstall the 'validate password component' in mysql to get the 'dbconfig' component of the package to accept my completely conforming password !)

"bacula-client/jammy-proposed"

"bacula-fd/jammy-proposed"

"bacula-doc"

"bacula-director/jammy-proposed"

"bacula-console-qt/jammy-proposed"

All seem to work fine and I can confirm several successful backups of selected files to tape,

regards,

Kevin.

[Linus Walther (linwalth)]

Though it has been tested already and the issue seems to be fixed, this issue has not seen any change in a long while. It would be really useful to have Bacula back on 22.04 regularily.

[Ian Young (h-ian)]

It looks like the SRU bot reported issues with the proposed package 235 days ago (in June last year) because the i386 variant didn't build and nothing has happened since then.

I tried installing a daily build of *24*.04 to see what the situation is there, as I'd expect to upgrade my 22.04 machines at some point. It looks like it has Bacula 13, so FD not compatible with anything but a Bacula 13 DIR. I don't know whether the daily x86-64 build having it means it's guaranteed to ship as part of the LTS.

[Robie Basak (racb)]

Now is a good time to raise this - while we're developing the next release, rather than after it is released :-)

Unless something changes, Noble will release with bacula 13.0.3-1 in April. However during development this status may change. I suggest anyone interested watches for bugs in this package and tracks its status at https://launchpad.net/ubuntu/+source/bacula.