After botching a PostgreSQL upgrade (and successfully restoring from a Bareos backup), I decided to take the opportunity to upgrade this package to the latest Bareos. It was way more complex than I thought and I didn't feel comfortable adopting the package to potentially throw a wrench in the backup systems of unsuspecting users, but I do have a mostly complete PKGBUILD and patch files.
I have two patches formatted to be applied with git am to the current repo (commit 959a0859dfb7). Patch 1 updates Bareos to 25.0.1 and adds gcc14 as a dependency since I could not for the life of me figure out how to make Bareos build on gcc15, no amount of -Wno-error-s did the trick. It also updates the contained patches since the source files changed. Link to Patch 1
Patch 2 is where I'm feeling far less confident. For reasons I do not understand, the current PKGBUILD lists out every single file to be installed manually. I did my very best to update those, but it feels error prone. Here is a list of files that the Bareos install procedure creates, are NOT packaged, and that I didn't include in the PKGBUILD since I either couldn't figure out where they went or seemed to reference a module that didn't have a package currently. This patch, Link to Patch 2, includes all the updates to the packaging functions where I COULD figure out which package the files belonged to.
If anyone is brave enough to give it a go, let me know if I'm on the right track! It appears to be working, though I expect there are missing features that I don't know about since I have a simple use case. I'm sure there's some way that the original author generated all those install lines for specific files, but I have no idea how that was done and doing it manually is a pain.
Pinned Comments