[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#698245: unblock: moodle/2.2.3.dfsg-2.6~wheezy2



On 03/11/2013 09:35 PM, Jonathan Wiltshire wrote:
On Mon, Mar 11, 2013 at 06:43:02PM +0100, Tomasz Muras wrote:
On 03/11/2013 05:22 PM, Jonathan Wiltshire wrote:
Just to clarify before I do it: stable stays as it is; remove moodle
>from Wheezy and you will work on the basis of getting 2.5 into Jessie?
Intermediate versions can always go into backports of course.

On Mon, Mar 11, 2013 at 02:40:55PM -0400, Hubert Chathi wrote:
On Mon, 11 Mar 2013 18:43:02 +0100, Tomasz Muras <nexor1984@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?

Yes.

AFAIK, if a package is not intended to go into testing, it should be in
experimental rather than unstable.

Unstable is fine. Protecting unstable doesn't make any sense for a package
that isn't in testing anyway. When the freeze is lifted normal transition
will take place.

Great, sounds like a plan to me. I'll document it on http://wiki.debian.org/Moodle and update all interested.

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.

This is why I suggest using wheezy-backports.

Great, we're not promising any security updates in *-backports, so we can have:
* Moodle 1.9 in squeeze
* nothing in wheezy
* Moodle 2.2 with security issues in wheezy-backports, just to cover for users that want to use it for the upgrade path * LTS (possibly 2.6) in unstable, with migration to testing blocked until the version is confirmed LTS. The preinst check seems like a good idea.


Tomek


Reply to: