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

Re: Bug#251561: Read error when configuring timezone



At Wed, 2 Jun 2004 15:03:40 +0200,
Robert Millan wrote:
> 
> On Wed, Jun 02, 2004 at 01:12:20PM +0200, Marcus Brinkmann wrote:
> > 
> > This is definitely a new one.  Looks like glibc breakage to me.  But
> > if tzconfig works later on, it might be a more subtle problem.
> > Definitely worth taking a closer look.
> > 
> > On the rant issue, I don't think there is anything special about
> > cross-hurd wrt to bug reports.  The bug cropped up using crosshurd,
> > probably because it is the first thing in a new hurd install that
> > makes the bug pop up.  In any case, reporting it as a bug to crosshurd
> > sounds appropriate to me, if only to make it apparent that crosshurd
> > doesn't work until this problem is fixed.  Of course this doesn't look
> > like a problem you can address in crosshurd, so the appropriate
> > reaction for you as the maintainer is to reassign the bug to, well,
> > the hurd package (as a general place holder for hurd specific bugs of
> > unknown origin - we can reassign it to glibc if we think it is a glibc
> > issue, etc).
> 
> The BTS tracks bugs per-package. When bugs are known or at least suspected
> to be in a particular package, they're assigned in it. I don't find it
> suitable to use particular packages as general place-holders. In this
> situations we normaly use virtual BTS entries (e.g., general, wnpp, etc).
> 
> If what we actualy need is a BTS entry for the system in general (e.g., gnu),
> this should be requested to the BTS admins (by using the BTS, of course).
> Using the "general" virtual package.

I'd be fine with this (in general, I leave this to Jeff to decide if
he wants to go for it).  The point here is that we don't want to
bother individual package maintainers with the bug reports they can't
do nothing about, and provide them with a package to assign it to.

So far the hurd package has been used for this purpose (not often, but
a couple of times).  That's what I said above.  If a better solution
is acceptable and preferred in Debian, then that's just as fine.

Thanks,
Marcus



Reply to: