orphaning many packages
pertusus at free.fr
Sat Dec 6 12:24:20 UTC 2008
Some more misc packages I'd like to orphan.
I orphaned only devel. I'd like to remain co-maintainer. I'd prefer also
be only co-maintainer for other branches, but obviously only if somebody
volunteer to be the primary maintainer. So if you want to be maintainer,
please state for which branches. Some already have co-maintainers, they
should have priority for ownership.
In my opinion gnash and tetex-tex4ht are strategic packages for Fedora
and if nobody steps up a kind of collective maintainance should be
People interested in gnash should also take agg and flasm, in my
opinion. They should also help reviewing ming:
And also mtasc, I added it to the wishlist and made a srpm here:
ming and mtasc are used for tests. (and also swftools, but I think
that swftools packaging is still out of reach for now).
The OpenDAP server stack (an interested maintainer should take them
all... and maybe package olfs, the hyrax front-end):
It should be renamed tex-tex4ht. There is a system of 2 level sources.
Literal sources are included, but second level sources are really used.
With the debian packager, and with upstream, we collaborated on a debian
script that can be used to rebuild the second level sources from the
There is the Consolekit issue. I hope that it would be fixed one day?
It is an interesting package in my opinion since it looks good while
being very lightweight. Trouble is that upstream is dead and so is not
resyncing with xdm, so retiring this package may unfortunatly be the
best thing to do.
I should not be the primary maintainer, but only a co-maintainer,
don't know how I became primary maintainer.
Those perl modules are very low maintainance:
This is an a2ps dependency. There are unresolved bugs that can be seen
in debian, but overall it works fine and is pretty dead upstream so is
very low maintainance.
Very low maintainance
Very low maintainance
Very low maintainance dead upstream packages
Though libnet10 is an older version of a dead package, there are
certainly some codes not in fedora that still use that api, for
example some stuff here:
It is properly parallel installable with libnet so in my opinion
should stay indefinitely (or as long as it builds).
There are a lot of people wanting to have shared libraries for this
one. I always resisted for the reasons stated in
especially in that case I think that at some point somebody will
resurect libnet since, as far as I know there is no replacement.
More information about the devel