I'm considering orphaning moin in EPEL

[Ville-Pekka Vainio]

Hi,

I took ownership of the moin package in Fedora and EPEL for about six
months ago. I haven't gotten around to doing almost anything to it,
though, mostly because I have to admit that I'm not that interested in
EPEL since I don't run any EL installations myself.

The other hurdle in updating moin is that the package in EPEL is really
old by now. It's in version 1.5 and the newest upstream version is 1.9.
If there was an update submitted for moin, we'd need to also have some
instructions on how to convert the wiki data into a format which is
suitable for the new version, and frankly, I don't know how to do that,
since I've only gotten involved with moin during the 1.7 era. All I know
is that trying to go from 1.5 to 1.6 was really difficult when it was
tested with the Fedora wiki data back when Fedora was still running
moin.

In June I thought I'd have the time and the interest to figure out the
data migration procedure from 1.5 to 1.8, but I clearly don't and I'm
sorry it took me so long to realize this.

So, what should we do with moin in EPEL? Is there anyone on the list
who's interested in taking over the package? If not, I see two
possibilities here. Either we orphan moin completely, or I ship an
update to 1.8 (as 1.9 might be a bit too new for a server oriented
distribution) with a notice saying that those who upgrade are on their
own with the data migration.

[Kevin Fenzi]

On Wed, 23 Dec 2009 14:11:26 +0200
Ville-Pekka Vainio  wrote:

...snip...
> So, what should we do with moin in EPEL? Is there anyone on the list
> who's interested in taking over the package? If not, I see two
> possibilities here. Either we orphan moin completely, or I ship an
> update to 1.8 (as 1.9 might be a bit too new for a server oriented
> distribution) with a notice saying that those who upgrade are on their
> own with the data migration.

Hopefully someone will be interested in taking it on.

If not, please DO NOT just push an incompatible update. 
The only way you can do that is if there is a known security issue and
you can't backport the fix to the old version.

Hopefully someone can figure out how to let it auto update from the
package...

kevin

[Stephen John Smoogen]

On Wed, Dec 23, 2009 at 5:02 PM, Kevin Fenzi  wrote:
> On Wed, 23 Dec 2009 14:11:26 +0200
> Ville-Pekka Vainio  wrote:
>
> ...snip...
> > So, what should we do with moin in EPEL? Is there anyone on the list
> > who's interested in taking over the package? If not, I see two
> > possibilities here. Either we orphan moin completely, or I ship an
> > update to 1.8 (as 1.9 might be a bit too new for a server oriented
> > distribution) with a notice saying that those who upgrade are on their
> > own with the data migration.
>
> Hopefully someone will be interested in taking it on.
>
> If not, please DO NOT just push an incompatible update.
> The only way you can do that is if there is a known security issue and
> you can't backport the fix to the old version.
>
> Hopefully someone can figure out how to let it auto update from the
> package...

Its pretty much impossible. We had to go through the directories with
a complicated sed/awk script and that got most of the issues. after
that it was a hand by hand fix. And then you have to know where the
person put those files which is installation dependant. There are
several security issues that have been found in moin over time so we
could do this as a security fix...

as far as I can tell webapps are terrible things to have with EPEL's
policy because they are so transient.