[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

gtk-gnutella (was: more current kernels for sarge in volatile)



Hi,

* Anand Kumria (wildfire@progsoc.uts.edu.au) [051230 02:20]:
> I think it'd more useful for users if the debian-volatile group were
> able to process requests (such as gtk-gnutella) by maintainers in a
> timely fashion.
> 
> I'm pretty disappointed so far; despite being contacted via IRC a few
> days ago by Martin, who:

what do you expect by this mail to happen? Annoy Martin? Increase our
frustration level?

> 	- wasn't able to determine whether I was a Debian developer or
> 	  not (I am).

Well, I usually would expect that - if something worked wrong in your
opinion with the automatic running script - you directly contact the
team. For the non-team members: there was a reject of the upload; the
technical reason is that Anand's key is in the .pgp-file and not in the
.gpg-file as most of the keys. This was not by bad purpose, but such
issues sometimes just exist.


> 	- hadn't actually bothered to look over the upload changelog I
> 	  had uploaded

This is not true.


> You have maintainers who want to support their users but whom you are
> ignoring.

This is not true. You send mails to the volatile contact address, and we
answered. There are massive reasons against gtk-gnutella as written in
e.g. http://lists.debian.org/debian-volatile/2005/12/msg00001.html -
Martin has been extra nice, and still wanted to work out a way to
include this package. I'm way more conservative than Martin is.

It is always easy to claim "from my maintainers point of view, doing
this and that will help users of my package". However, we as volatile
team have (also) to take care of the larger picture - long-term trust
and supportability etc. And it is not true that just because some
maintainer says "it works fine", everything works fine. Otherwise, there
wouldn't be e.g. any RC bugs in Debian sid.



> It seems to me your are wasting your time by ovrelooking the former for
> the latter as well as letting down whatever userbase volatile has.

If you think the volatile team is making wrong decisions, you are free
to try to convince us or even ask the DPL on replacing the team (I'm not
going to argue we're not delegated, and even running volatile on private
hardware - if the DPL wants to use his constitutional right, we're going
to give him way) - however, please refrain from using killer arguments
like "letting down whatever userbase volatile has".


Regards,
Andi
-- 
  http://home.arcor.de/andreas-barth/



Reply to: