Update individual Add-On's in PAKfire

IPfire: Core is now on 180 (Testing-Repository):
Installed Add-On: bacula and may others
Because of my infrastructure I cannot update bacula from 9 to 11.

To my knowledge all available updates are installed by the Pakfire GUI at the same time. One cannot select individual AddOns only. Maybe I’m wrong and just don’t know on how to do it.

Q: Is there a way in Pakfire to individually update AddOn’s?
My workaround not to update bacula is as follows:

  • Update Core and all AddOns with pakfire (Testing-Repository)
  • Uninstall bacula
  • Select Stable Repository
  • Re-Install bacula
  • Select Testing-Repository again.

I wonder whether this workaround will still works once bacula11 is part of Stable-Repository.

Bear in mind that bacula has been on version 13.x since mid last year.

What infrastructure issue prevents you updating from version 9.x to 11.x or 13.x?

No, that won’t work anymore as the version11.x will then be the only version available in both the Stable and Testing branches.

In the past I remember a person wanting to install an older version of an addon and he figured out the url for the addon versions and manually downloaded the file and then figured out the commands to run from the command line, including the gpg signature checking to be able to install that older version. He basically had to read through the IPFire pakfire code to figure out what happened normally and then use those commands on the console to download and install a previous version.

However I have not been able to find that with my searching through the forum posts. You might have more luck.

Bear in mind that with that when you do a core update you will also have the addon updated so you will need to uninstall and then do the same manual install again.

The other way would be to build your own local addon version of bacula at the version number that you want.


Thanks for your quick reply :slight_smile:

In know that latest bacula software is on version 13. Nevertheless Debian12 (bookworm) is still on bacula9.

I really don’t want to nor intend to frickle around with standard procedures. This will cause trouble sooner or later. As bacula-server will not work with higher client versions I must either not upgrade ipfire or drop bacula backup on ipfire or change my backup method for ipfire.
I tend for the later.

Anyway thanks for your support.

Debian keeps everything very stable but that also results in it having very old versions of some of the software.

I build all my bacula programs from source so I can stay on top of the versions.
Probably early next year I will do the IPFire update to version 13 as that branch will have been released for 1.5 years by then.

An alternative that you could use is to download and install the version 13.x .deb files from bacula. Those could then be installed on your debian bookworm in place of the currently installed versions.

Bacula have a white paper on installing the .deb binaries

The only thing that has changed from that documentation is the use of apt-key which has been deprecated in debian/ubuntu etc. It was mentioned recently in the bacula mailing list and a link was provided for how to use the latest approach.


Hello pv flick,

I also have the nearly identical issue. The only difference is that the machines on my local network are Slackware Linux. Slackware is also at bacula-9.6.7. My understanding that all the machines an a given network that uses bacula need to all be the same version. I, too, thought that Pakfire was more flexible, but as you have pointed out, it isn’t.

I’d like to thank Adolf Belka for the resource links. I will be looking through them to see if I can come up with a resolution for myself.

If anyone else has any suggestions that may be of help I’d greatly appreciate it.