Zitat von niftydrinks <[email protected]>:
Maik,Thanks for your response. I appreciate and understand that the subscription fees are used to fund Bareos development. That is absolutely fair.However, this creates a problem for organizations that want to test the software and feel confident that it will work in their particular environment. With the current issue in 14.2.2, this is impossible. The community edition is fundamentally broken due to this bug. Not being able to trust a restore is Bad.
It is a somewhat special point of view to say "fundamentally broken". It is a (known) bug in limited number of releases which can impact part of a restore in some special use cases (autolabeling, filestore, file span multiple volumes). Furthermore there are "workarounds" available if the impact is really that high for you. You can use the previous release, build your own from the sources including the fix or hire someone doing that for you. You can even easly create a setup without autolabeling and be done for this special bug.
Demanding on this base additional unpaid effort because you don't like the numerous workarounds is a little bit strange.
Regards Andreas -- 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 [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
