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. -- Robert Millan "[..] but the delight and pride of Aule is in the deed of making, and in the thing made, and neither in possession nor in his own mastery; wherefore he gives and hoards not, and is free from care, passing ever on to some new work." -- J.R.R.T., Ainulindale (Silmarillion)
