[DRE-maint] Bug#853841: schleuder: Decide how the schleuder v2 -> v3 upgrade path should look like

Georg Faerber georg at riseup.net
Mon Feb 6 19:21:32 UTC 2017


Hi Christian,

On 17-02-01 20:40:40, Christian Hofstaedtler wrote:
> * Georg Faerber <georg at riseup.net> [170201 13:15]:
> > - schleuder doesn't exist in jessie, but in wheezy.
> > - According to popcon, there are currently four installs out there.
> > - I'm aware of some large installations with >100 lists each.
> 
> > Upstream is more in favor of failing (hence the code) if v2 data is
> > found, asking the user to move the data out of the way, resume the
> > install and migrate after this, which is a (more) manual process then;
> > but maybe this would be tolerable as well, because, I guess, most people
> > running schleuder have at least some basic script skills. A positive
> > side effect would be to cleanup up '/var/lib/schleuder', so we don't
> > keep old data inside there "forever".
> 
> I'd think moving /var/lib/schleuder out of the way in the postinst
> is acceptable here; just let the user know you're doing that (print
> something, don't use debconf).

Thanks for your input!

Any advice to which place I should move the data?

Cheers,
Georg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20170206/735c479e/attachment.sig>


More information about the Pkg-ruby-extras-maintainers mailing list