Bug#451193: ReadSeq (Was: Thoughts on the Vienna RNA package)
Hi,
> > - It uses a patched version of Readseq. Maybe we should consider to
> > build Vienna on Debian's readseq, possibly by adopting its patches if
> > they are not disruptive. By the way, we could incorporate the Debian
> > package for readseq in our repository, if its current maintainer
> > agrees.
>
> As a former maintainer of readseq I would like to clarify the situation
> from my point of view:
>
> 4. I handed over the package to Michael Schmitz <schmitz@debian.org>
> (Changelog entry "took over from Andreas Tille 'cuz readseq is actually
> in use at our site"). I'm a little bit unsure whether this is
> valid until today - at least the package has some lintian
> problems and IMHO definitely needs polishing. (Michael, are
> you able and willing to work on this package?)
I'm no longer at the lab in Duesseldorf but I could certainly continue to
work on it. The additions I put in to accomodate the use in Duesseldorf
should perhaps stay in, even though those guys mostly switched to bioperl
these days.
> My suggestion is that we immediately move the packaging stuff to Debian-Med
> SVN and add Michael and mayelf to Uploaders, while the maintainer should
> be the Debian-Med packaging team (Michael, I hope you would not regard this
> as piracy ...).
Not at all - I had pertty much forgotten about readseq.
> Somebody should discuss with upstream whether they prefer that we
> "release new versions" of readseq1 or that we maintain a set of patches
> inside Debian. In any way if there are good reasons to patch readseq
> (working nicely with another package would be such a good reason) we
> should just do it inside the Debian package.
I believe there really is no upstream activity anymore. Patches for
supporting other packages is just what I did to it anyway, so keep
adding more (making sure it keeps working for the old test cases).
I had tried to get one of the bioinformatics guys involved as maintainer
with no success. If it comes to the worst, they will know who to blame.
Michael
Reply to: