At Tue, 1 Jun 2004 14:19:14 +0200, Robert Millan wrote: > See http://bugs.debian.org/251561
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). Thanks, Marcus