Bug#341420: marked as done (code in exts/dbase is not DFSG-free)
 

Raphael Geissert <atomo64@gmail.com> (29/11/2008):
> 2008/11/29 Holger Levsen <holger@layer-acht.org>:
> > Huh? We are in a permanent bugsquashing party, cause we want to
> > release lenny.

Still, coordination and communication matter.

> Right, but it is a DFSG-freeness issue and those take time to
> *properly* resolve.

Sure. You're also expected as maintainer to ack the bug (especially an
RC one in a trying-to-release period). It sounds to me that just saying
“ACK, no need to NMU, we're actively working on getting this fixed”
after the severity got bumped would have done the job. For people
crawling through the RC bug list, that's nice to have a clue that people
are working on this or that bug, so that one can focus on others.

> > This is a RC bugs since three weeks, so I rather think the
> > php-maintainers have been unpolite leaving it open so long...

Maybe Holger meant “without any reply”, but I can't speak for him.

> If you or anybody else has a magic trick to reach every copyright
> owner out there in a matter of a couple of days then please share it
> with the rest of the mere mortals out there.

Sure (see RPC, Sun, etc.; or SGI)…

> We already fixed another DFSG issue a month or so ago, all we needed
> was some time to properly resolve the issue.

… sure as well; just as noted above, a notice to the bug would be nice.

> My point is: I find it very impolite to just come and upload a package
> without even trying to contact the maintainers as to coordinate the
> changes, without further investigation, in a DFSG purist intolerant
> position.

Coordination and communication got lacking, no need to get so angry. ;)

Mraw,
KiBi.

Bug#341420: marked as done (code in exts/dbase is not DFSG-free)
 

hiya,

On Sun, Nov 30, 2008 at 01:43:22AM +0100, Holger Levsen wrote:
> Huh? We are in a permanent bugsquashing party, cause we want to release lenny.
> This is a RC bugs since three weeks, so I rather think the php-maintainers
> have been unpolite leaving it open so long...

for future reference a number of us who are either active or semi-active with
php maintenance are also often on irc, so if writing an email is too cumbersome
you can also ping us (raphael or myself, anyway) on #debian-devel.

however, i'd still suggest that the best practice would be to attach something to
the bug for posterity (and yes, the same applies to the "undocumented"
php-maint intentions as well)

personally i don't object to having an NMU done for this, though a "heads up"
would have been appreciated.


sean

Bug#341420: marked as done (code in exts/dbase is not DFSG-free)
 

On Sun, Nov 30, 2008 at 03:29:14PM +0000, Ben Hutchings wrote:
> > > * Non-maintainer upload.
> > > * Remove exts/dbase from orig tarball (Closes: #341420)

> > Do you mind at least contacting the maintainers?

> > I find your upload very impolite.

> php5 had an RC bug open with an obvious fix available for 3 weeks. The
> fix was to remove code that was not even being built, so it was
> low-risk. Why exactly should I have hesitated to NMU?

devref 5.11.1., "How to do a NMU"? :

NMUs which fix important, serious or higher severity bugs are
encouraged and accepted. You should endeavor to reach the
current maintainer of the package; they might be just about to
upload a fix for the problem, or have a better solution.

[...]

At times, the release manager or an organized group of
developers can announce a certain period of time in which the
NMU rules are relaxed. This usually involves shortening the
period during which one is to wait before uploading the fixes,
and shortening the DELAYED period. It is important to notice
that even in these so-called bug squashing party times, the
NMU'er has to file bugs and contact the developer first, and act
later.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slangasek@ubuntu.com vorlon@debian.org


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Bug#341420: marked as done (code in exts/dbase is not DFSG-free)
 

On Sun, 2008-11-30 at 18:45 -0600, Raphael Geissert wrote:
> [I would appreciate if you respected the CoC]
>
> 2008/11/30 Ben Hutchings <ben@decadent.org.uk>:
> [...]
> >
> > php5 had an RC bug open with an obvious fix available for 3 weeks. The
>
> What looks obvious to you may not be obvious to the others, please
> refrain from making such statements.
>
> > fix was to remove code that was not even being built, so it was
> > low-risk. Why exactly should I have hesitated to NMU?
>
> As already stated by Steve: because of devref 5.11.1, and because of
> mere courtesy.

You're right, I'm sorry.

7.2.2 actually contradicts 5.11.1, but I accept that I should have
either notified my intent to NMU or used the delayed queue.

> Also, the issue affects all versions of php from php3 to php5.

Then please assign clones of the bug to php3 and php4.

> So in
> case you are interested in "fixing" the whole problem then deal with
> the copies at archive.d.o, snapshot.d.n, and master.

I don't believe there is quite the same concern over commercial
distribution there.

Ben.

--
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
A fail-safe circuit will destroy others.