Package: schleuder Version: 3.0.1-1 Severity: important Tags: confirmed help
It's still unclear to me, and I'm calling for help and input with this, how the upgrade path should look like. The situation currently is the following: - 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. I'm all in for a "clean" upgrade path wheezy -> jessie -> stretch. I've therefore patched 'schleuder install' which would fail if '/var/lib/schleuder' contains v2 data [1]. However, the part of postinst which would check if an upgrade is made, iterate over the subfolders in '/var/lib/schleuder' and call the migrate command on each of them is still missing, but isn't such a big deal, obviously. 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". Any opinions, feedback would be greatly appreciated! Thanks, Georg [1] https://anonscm.debian.org/git/pkg-ruby-extras/schleuder.git/diff/debian/patches/0001-lib-fix-paths-and-enable-upgrades.patch?id=4a48f7b154a4693151d2d5cc2a98ef0c0703d652
signature.asc
Description: Digital signature
