[ First I need to confess that I know Yaroslav, work with him, and even
encouraged him to package NiPyPE to ease my neuroscientist research life. ]
I'm astonished by this thread. I'd never have expected that a simple technical
issue can cause such waves.
Just to get it straight for myself:
1. A package needs to be updated to the latest upstream (might have
happended before in Debian)
2. Maintainer says "I'm not uploading right now to unstable, nor letting you
do so"
3. Maintainer doesn't justify this decision with any _technical_
reasons. Who knows why?
4. NMU happens to delayed queue (despite the maintainer being listed
as Lowtreshold-NMU-welcome) -- 10 days of time to settle the issue
in whatever way.
5. Instead, NMU is killed, everybody is pissed off: "random guy",
"hijack", "advertisment on debian-planet", "people express their
"deepest concerns about this type of behavior", ...
It seems like we have witnessed a great success. The law has been
defended -- no updates the "wrong" way -- although we still seem to
have difficulties to pinpoint which of our many laws actually apply to
this evil attack.
Now the package is team-maintained -- ah no: is going to be
team-maintained, since no upload happened yet. I honestly believe that
team-maintainance is superior, but you still need _individuals_ to do
the maintenance. So, who is going to update the package?
Let me anticipate the "Join the team, do it yourself"-answer. I guess it
is better if Yaroslav does it, since he already has the updated package
(remember: that is how it started). He could do exactly the same thing
again (with a tiny change in the changelog) and the problem is solved.
But maybe we should think about some punishment so all interested
parties learn as much as they want from this incident. But wait -- we are
already punishing -- no upload has been done.
But why do I care? I could use networkx from experimental (as has been
suggested previously)!
Oh, that package is also outdated....
Go team!
Michael
--
GPG key: 1024D/3144BE0F Michael Hanke
http://mih.voxindeserto.de
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
