On Wednesday 29 August 2007, John Goerzen wrote:
> On Wed August 29 2007 8:30:09 am Michail Bachmann wrote:
> > I have read the whole thread and it seems to me the licensing concerns
> > will be resolved soon. IMO in the mean time it would be easier to keep
> > the openssl dependency so this package can be tested (by us at least).
>
> If the licensing is in doubt, we can't do that.  We must test it as it will
> be released.  I don't actually anticipate any change in the licensing
> situation any time soon at this time.

Sad, but we will have to accept this. Looks like we need another private 
repository... :-(

The (not really) funny thing is, a part of bacula (the bacula-director) will 
be linked against libssl anyway since libpq depends on it. Now I can only 
hope you dont plan to remove postgresql support as well...

> > > I will add this to NEWS.Debian to make it more prominent.
> >
> > Yes, please. Or temporarily revert the change ;-)
> >
> > The change is pretty invasive, since dropping the encryption support
> > means even if we disable the encryption before upgrading all backup
> > clients it will be impossible for us to restore any files which were be
> > stored before the change.
>
> The version of Bacula in stable did not support encrypted backups.  It did
> use OpenSSL, but only for network communication.  This particular problem
> will only be impacting people that are tracking testing or unstable.
>
> Of course, the communication problem could impact users of stable, which is
> why I'll add the note to NEWS.Debian.   Debian does not officially support
> testing -> testing or unstable -> unstable upgrades.  (That's why these are
> called "Testing" and "unstable")

Thanks for the explanation.

> I'll also note in README.Debian how people that wish to use encryption can
> build their own debs.

I think this is unnecessary, since you dont plan to support this functionality 
anyway and teasing the user with disabled functionality is just cruel :-). 
IMO a commented out line in debian/rules should suffice for the people who 
wish to build their own packages.

CU Micha

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to