On 6/3/14, 3:35 PM, John Zaitseff wrote:
> Hi,
> 
> It is somewhat disheartening to see a bug that I've opened in 2011
> still unchanged in status---even though I've provided solutions over
> the years.  The last time the maintainer, David Martínez Moreno,
> made a release was in 2010.
> 
> I still use this package extensively, and, in fact, was the one
> responsible for its complete reworking back in 2010---see the
> changelog entry for 1.1.5-1.
> 
> I would like to suggest taking over maintainership of the viewvc
> package, as suggested in bug #532611 (messages 27 and 28).  I am not
> (yet!) sure of the procedure to do so, but I will be investigating,
> as I aim to become a Debian Maintainer (and then Developer) in the
> near future...

        Hah, how funny! :-) Hello, John.  Funny because I was looking at my 
list of
packages (I have been doing updates to a lot of them since January or so) and I
saw that viewvc and memcached are falling behind, so I started working in viewvc
some hours ago and I even put a repo up in Alioth to give people visibility and
also to allow collaboration in case this happens again.

        As you can imagine I do not want this to keep happening.  I am now going
through your changes but I don't see a lot of new things now as the last time
(for 1.1.5).  I'm still cleaning the tarball and the bitrot that accumulated
over time, but I hope to have finished by tomorrow.

        You can take a look at
http://anonscm.debian.org/gitweb/?p=collab-maint/viewvc.git;a=summary.

        And I totally understand your feeling that it is disheartening.  In 
fact that
was what led me to adopt viewvc (see the changelog for the 0.9.4+svn20060318-1
version to give you an idea of the package state by that time.)  I hope that
having a public repo with the changes will prevent this disconnection from
happening, as you would need to apply for a -guest account in Alioth and you
might change yourself the source, and I (or any other DD) could upload a new
version.

        I hope to have solved some of your concerns with the above.  Thanks 
anyway for
your unconditional support and stubbornness updating this bug. :-)


                Ender.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to