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

Bug#222077: [debbugs packaging] Need to create the hash dirs db_h/00..99

On Thu, Jun 29, 2006 at 03:29:07PM -0700, Don Armstrong wrote:
> On Thu, 29 Jun 2006, Bill Allombert wrote:
> > Before Etch is frozen ? We already missed the Sarge deadline.
> Ideally; we're a bit far away from that now, though. The top item on
> my prority list is fixing the bugs, not polishing the package for a
> release in the intermediate state it is in right now.
> > Sure, but we still ship a 3-year old package that has easily fixable
> > issue and is several releases behind the upstream version.
> It's not several releases behind. The upstream version *IS* the Debian
> version. Upstream releases when it uploads a new version to Debian.

The Debian bug server use a much more recent snapshot than the Debian
package and is certainly a production-level installation.

> > Should I do an NMU ?
> If you have patches to fix the outstanding issues with the package, by

Sure, where is the list of outstanding issues you would like to fix prior
uploading ?

> all means submit them, but NMUing the codebase as it stands now will
> produce packages which are of worse quality than those currently
> distributed.

As you know, you alread commited the patches I had to the debbugs
repository.  But I can pick them and apply them on top of menu 2.4.1 and
upload that as an NMU. That will not be of worse quality that 2.4.1 is.

> So no, you shouldn't NMU.

So what should I do ? It is two year now that I try to get that fixed.

It is not as if NMUing would break the Debian bug server.

If you do not want to maintain the Debian package, well, don't.

Bill. <ballombe@debian.org>

Imagine a large red swirl here. 

Reply to: