Bug#785052: Uploading 8.2 to experimental?

[Marco d'Itri]

On Nov 09, David Prévot  wrote:

> Any hint to deal with encryption would be welcome, I might upload to
> experimental if I go the path of failing install if encryption is enable
> in preinst unless there is a better solution (and I hope there is…).
Upload it straight to unstable with this check, since you can implement 
it easily and it will allow people to use the package.
If a more complex solution will prove to be needed and it will be 
possible to implement it then you can always add it later.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#785052: Uploading 8.2 to experimental?

[David Prévot]

On Thu, Aug 20, 2015 at 03:57:01PM +0200, David Prévot wrote:

> It’s almost ready to be uploaded to experimental. I need to figure out
> if the encryption upgrade can be automated first.

I keep updating the VCS to the latest upstream releases, and publish
packages to people.d.o, but unfortunately, I have still no clue how to
manage an upgrade with encryption enabled (i.e., following upstream
documentation doesn’t get me to migrate manually to the new encryption,
even going threw the “normal” process – upgrading to latest 8.0, then
latest 8.1, etc. –), so I don’t really know how to proceed from here.

A first step could be to fail the upgrade in preinst with a big fat
warning if encryption is enable, maybe even decrypt everything in
preinst if possible (note that it may take a lot of time depending on
the amount of data, and possibly expose data to third party, so I don’t
think such behaviour should be the default).

Any hint to deal with encryption would be welcome, I might upload to
experimental if I go the path of failing install if encryption is enable
in preinst unless there is a better solution (and I hope there is…).

Regards

David


signature.asc
Description: PGP signature