On Tue, Jul 15, 2003 at 06:42:59PM +0200, Ivo Timmermans wrote: > Robert Millan wrote: > > On Tue, May 27, 2003 at 05:15:59PM +0200, Marcus Brinkmann wrote: > > > On Tue, May 27, 2003 at 10:59:50AM +0200, Robert Millan wrote: > > > > my apologises, Marcus. i'll follow your suggestion next time. > > > > > > It never hurts to ask if you see something unusual. Any unexplained > > > difference between GNU/Linux and GNU/Hurd is by definition unusual :). > > > > I _did_ ask (in one of the *-hurd mls). then two people responded with > > opposite opinions on wether it's a system bug or a bug in the package. the > > discussion didn't get any further. > > So has it gotten any further? Does this bug still exist?
No, we're stuck as neither Marcus or me has time for this. If you can help, that's very welcome. > Does it > still apply to libgcrypt only, or is it rather something that should > be reassigned to some toolchain component? libgcrypt is just an example that is probably a good test case; we don't know where it belongs exactly but the bug affects Xfree86 and other packages. -- Robert Millan
