Hi Jan,

Thanks for the feedback. I see and understand the potential problem you are highlighting.

There could be people running the bacula director and storage daemons with versions earlier than the current released one. This could be due to slower updates with some distros for example. These people could not use a more recent version of the File daemon than their director/storage daemons.

By establishing versioned bacula-fd packages I take it that you mean that when you install bacula in IPFire with pakfire that you have a selection of different bacula-fd versions to choose from. I am not sure whether that is possible/allowed or not in IPFire and have no idea how to implement it.

I am building and installing bacula on all my other systems from source  and so I have the latest version running and so I had just suggested that I provide that update into IPFire, as a patch, as I am already building and installing it as a local add-on.

I think the simplest approach is to leave bacula 9.0.6 in IPFire, ie the status quo. It still seems to work with the current released version of director and storage daemons. If that ever changes then we can deal with it at that time.

I will continue installing the latest version of bacula as a locally built add-on as I have been doing for some time.

All of my bacula patch proposals can then be removed from patchwork.

Adolf

On 13/06/2020 16:03, jan.lentfer@web.de wrote:

Dear all,

when upgrading bacula-fd (client), please keep in mind you are forcing server upgrades on to people. While newer director and storage-daemon work with older client releases it’s not the case  the other way around. So either do not upgrade the client too hasty or establish versioned bacula-fd packages.

Best regards Jan Am 13. Juni 2020, 15:37 +0200 schrieb Adolf Belka ahb.ipfire@gmail.com:

...

Dear all,

Bacula has just been updated to 9.6.5

I will send out a new patch email with the change from 9.0.6 to 9.6.5

I have implemented this on all my computer systems and it is running fine, including on my IPFire system.

The previous patch from 9.0.6 to 9.6.3 that is in the patchwork system can be removed as it hadn't yet been accepted into the IPFire build and will now be overtaken by the new patch.

Adolf