On Mon, 11 Mar 2013 18:43:02 +0100, Tomasz Muras <nexor1...@gmail.com> said:
> Correct. 1.9 is still supported (it won't be for long) and can stay in > stable. I am thinking that I would would package 2.5 and then 2.6 in > unstable and do not let it migrate into testing - unless LTS upstream > version is released. Does it make sense? AFAIK, if a package is not intended to go into testing, it should be in experimental rather than unstable. > One thing I'm not sure about is what will happen to current users of > moodle package. They have 1.9 in squeeze, there will be nothing in > wheezy but then the package will appear back in jessie - but with no > upgrade path. The only way to get moodle back will be to drop the > package completely (and drop DB) and re-install it. Of course we could > provide some manual instructions to install 2.2 package and then > upgrade to 2.4. IIRC, technically, we wouldn't need to worry about upgrades, since we only need to do upgrades from the previous Debian release. Of course, that's not a very nice thing to do. One option is to provide a 2.2 deb package that they can download from some other repository (we could probably dump it somewhere in Alioth). That would probably be easier than having to install 2.2 via a non-deb method. And you could add a preinst script in the 2.5 package that would abort the upgrade if the user tries to upgrade from 1.9. -- Hubert Chathi <uho...@debian.org> -- Jabber: hub...@uhoreg.ca PGP/GnuPG key: 1024D/124B61FA http://www.uhoreg.ca/ Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org