Community packages repository for version 22

[Łukasz Szczepanik]

Hi,

From Bareos 22 version something has changed with packages repository location for community repo. The newest community version  points to "current" location instead of "release/22" like for subscription repository.

I see a problem with this approach. My Bareos config is fully managed by Puppet. If I point repository path to "current" my Bareos config could be upgraded automatically without my knowledge if Bareos will release new version eg. 23. I want to avoid such situation.

Is there any chance that Bareos 22 version and next ones will be located in 'release/<version>'  in community repo ?

Thank you 

  

[Willem Basson]

Some clarity about the future of the community repos will actually be very much appreciated.
release/21 recently disappeared, and we had to switch to https://download.bareos.org/release-old-deleteme/21/Debian_11
Turns out that was short lived, and release-old-deleteme was... you guessed it. Deleted.
If we aren't ready for bareos version 22, is our only viable option to build debian packages ourselves?

[Frank Kohler]

On 5/8/23 20:21, Willem Basson wrote:

Some clarity about the future of the community repos will actually be very much appreciated.

Message-ID: <363ce0d7-23c7-a4c0...@bareos.com>

or

https://www.bareos.com/bareos-release-policy/

release/21 recently disappeared, and we had to switch to https://download.bareos.org/release-old-deleteme/21/Debian_11
Turns out that was short lived, and release-old-deleteme was... you guessed it. Deleted.
If we aren't ready for bareos version 22, is our only viable option to build debian packages ourselves?

Either github.com/bareos or
contact Bareos for subscription access to repositories. We have a hosting partner program as well if that applies.

Thank you 

 

best:
Frank

-- 
Frank Kohler
Bareos GmbH & Co. KG           
Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: Stephan Dühr, J. Steffens, P. Storz

[Willem Basson]

I think we are both out of luck. https://www.bareos.com/bareos-release-policy/ explains the what the community repos will have from now on.

[wizh...@gmail.com]

Ran into this too.

"Designed for testing and home environments "  and  "not for production" are unfortunate. Home use is not considered production I guess, we need to avoid it for any real backup use at all now.

Sounds like they are on the same path as bacula, which is why I switched to bareos in the first place.

[Frank Kohler]

Nope, merely mandatory #legaldisclaimer.
Feature set is equal to subscription repo

--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/092efe97-c81c-4329-8d30-7261155ab05dn%40googlegroups.com.

-- 
Frank 
Bareos GmbH & Co. KG           
Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: Stephan Dühr, J. Steffens, P. Storz

[Douglas Hammond]

Thank you for clarifying..

> You received this message because you are subscribed to a topic in the Google Groups "bareos-users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/bareos-users/JWw7RVS8qBg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to bareos-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/7feb7457-53e7-ad2b-447f-998ba3866b4b%40bareos.com.



--
Douglas Hammond
VA3DJX

[JH]

Hi,

I have this problem too ( release/21 recently disappeared).

After many years with Bareos, it is time to go back to Bacula.

Very sad and a lot of work

[Douglas Hammond]

After clarification, the "current" release should be stable and is the
same code they use for their subscription builds, don't feel quite as
bad as I did.

This actually sounds better than bareos's past releases as patches for
the current version were not available without subscription if you can
trust that stabe is actually stable.

This does have the caveat though "could be upgraded automatically
without my knowledge", which is a very big concern especially for
major versions.

I get they want to charge for the convenience of their prebuilt
packages as you can build it on your own for linux is easy enough.
BUT the build process for windows clients is not documented and the
closest info is
https://groups.google.com/g/bareos-devel/c/GEXnhQp9y00/m/ZmiPpO4uAwAJ
which is no longer relevant with the updated build system.

For now, guess I'd build my own for linux on tagged versions and keep
around a copy of the current windows version that was released around
the time of the new tag.

> To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/aa0fd89a-3f09-4a71-9d5f-43c4f780ef60n%40googlegroups.com.



--
Douglas Hammond
VA3DJX

[Łukasz Szczepanik]

I got the same impression about the new community repo design. 

It seems that from now on I have NO control over the Bareos version installed on my production server and clients. 

To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/CAG9T%2BQQh7qj%2BFYArBXngtk5H9Q9vPjZmLTLx1FncEybUZg9N%2Bg%40mail.gmail.com.

--

Lukasz Szczepanik | Site Reliability Engineer

lszcz...@opera.com

The information in this email and any attachments is CONFIDENTIAL INFORMATION and is solely for the attention of the intended recipient. If you are not the intended recipient, then you have received this message in error and therefore reading it, copying it, or in any way disclosing its content to any other person is unauthorized. If you have received this message in error, please notify the sender by reply email and then immediately delete this email (including any attachments).

[Denis Yesakov]

What is the problem to compile on your own?

You can compile community-checked versions.

The support is still in the community.

I made builds of 22.0.3 for aarch and x86 works without problems 

[Dick Essebaggers]

can somebody give a hint/link on how to compile older client versions for Debian systems?

[Andreas Rogge]

Am 11.05.23 um 23:28 schrieb Douglas Hammond:

> This does have the caveat though "could be upgraded automatically
> without my knowledge", which is a very big concern especially for
> major versions.

You're still using your package manager to install the update, so if it
happens automatically then it was you who automated it and if it happens
without your knowledge then it was you who chose to ignore it.

Having said that, I totally get your concern for major versions. These
may come with some more implications than a patch- or feature-release.
However, if you as a community can agree on a realistic time-frame you
would need to prepare for the arrival of a new major release, then I
don't see why we wouldn't notify you in advance.

Best Regards,
Andreas

--
Andreas Rogge andrea...@bareos.com
Bareos GmbH & Co. KG Phone: +49 221-630693-86
http://www.bareos.com

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH

Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz