Your message dated Sat, 20 Jan 2007 05:23:20 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#407260: No sane upgrade path from etch to lenny
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: mailman
Version: 1:2.1.9-4
Severity: serious
Justification: Makes package unsuitable for release in one maintainer's opinion
We should sort that out before release; if RMs disagree (e.g. punt it
to a point release), feel free to tag etch-ignore and/or downgrade
severity so as not to block release just for that.
If other pkg-mailman members disagree, feel free to discuss.
--
Lionel
--- Begin Message ---
Hi,
Assuming lenny will have Mailman 2.2, if we want to have an upgrade
path from etch to lenny, we better backport that bin/export to 2.1.9
and get it in etch (so that we can call it from mailman 2.2's preinst
script). Alternatively, we package mailman 2.2 as mailman2.2 and let
"mailman" be 2.1.x and not handle automatic upgrades at all. I must
say I'd prefer the first solution.
Someone feels up to doing that in time for etch, that is very, very,
soon?
In the meantime, I'm contacting the RMs to see what our options are.
--
Lionel
--- Begin Message ---
pgphSkcjDb116.pgp
Description: PGP message
--- End Message ---
--- End Message ---
--- Begin Message ---
Hat: maintainer of Mailman package in Debian
Hi,
It has just come to my attention that there will be no upgrade path
from the version of Mailman in etch at this time (2.1.9) to the
version lenny will most probably have (2.2.x), but there will be an
upgrade path from the yet-unreleased 2.1.y, y>9, to 2.2.x, and an
upgrade path from 2.1.9 to 2.1.y.
The reason is a fundamental file format change in how data is stored;
mailman 2.1.10 will have an "export" binary that will export the data
to a neutral (XML) format and Mailman 2.2 will have an "import" binary
that will import that format. We can do the "export" in preinst and
the "import" in postinst, but only if the package being upgraded from
contains that bin/export/.
(Shipping the said bin/export as part of the Mailman 2.2 package will
be highly inconvenient; it is a python script that imports a
significant part of Mailman itself; we'd have to basically ship a
private copy of Mailman 2.1 in the Mailman 2.2 package.)
My question is: Will you accept a freeze-exception update to mailman,
or a point-release update to mailman later, to add the said bin/export
to the etch package of mailman 2.1?
Even if we include the current version of bin/export (from their SVN
repository, the 2.1.x branch) in the etch-mailman package, there is a
non-zero risk that the said XML format will change and that we will
need to update it in a point release of etch to ensure an upgrade path
to lenny.
--
Lionel
--- End Message ---
--- End Message ---
--- Begin Message ---
Version: 1:2.1.9-5
Fixed in Version: 1:2.1.9-5, but forgot to mention that in changelog:
mailman (1:2.1.9-5) unstable; urgency=medium
* Ship bin/export.py from upstream SVN to make automatic upgrades to
lenny possible.
-- Lionel Elie Mamane <[EMAIL PROTECTED]> Sat, 20 Jan 2007 05:04:11 +0100
--- End Message ---
