Re: Bug#625449: Permanent BSP patch
Le Wed, May 04, 2011 at 10:33:39AM -0700, Russ Allbery a écrit :
> Charles Plessy <plessy@debian.org> writes:
>
> > My main concern is that most NMU workflows are not considering VCSes and
> > therefore not helpful when there is a race condition between the NMUer
> > and the maintainer.
>
> If they follow the standard procedure of posting the NMU diff to the bug,
> I'm not sure why they wouldn't be helpful. Surely any conceivable VCS is
> capable of importing that patch?
I already received patches that were half-mailquoted, and therefore impossible
to apply without human editing. I also received dpkg “3.0” patches that
consist on dozen of lines, just for modifying a single line in the upstream
sources. Once a NMUer was more helpful and commited his changes, but forgot to
“svn add” his patch. Another time (not recently, I admit) I was rushed into
uploading changes that were confirmed a couple of days later by Upstream to be
not appropriate. Another time, my package was NMUed while I was working on the
new upstream release that fixed the problem. Et cætera.
Since we are short of manpower, why would we recommend in the DevRef to not
coordinate with active maintainers ? Unless the issue is urgent, and I strongly
thing that not all RC bugs are equally urgent, we should aim at minimising the
overall work load.
I know that I am over-reacting, but I can not help feeling the pushy attitude
to be confrontational, top-down and divisive.
Cheers,
--
Charles
Reply to: