Hi, On Tue, Feb 07, 2006 at 03:24:33PM +0100, Filip Van Raemdonck wrote: > package: mingw32 > severity: minor > > The mingw32 package contains a symlink > /usr/share/man/man1/i586-mingw32msvc-gccbug.1.gz which points to > gccbug.1.gz in the same directory, but I have no such page on my system > (likely because I have no native gcc installed). > > Since the package includes full manpages for the other i586-mingw32 > commands, it probably should for gccbug too.
Well, it probably can't supply gccbug.1.gz, as that may conflict with a native package as you suggest -- and given that it probably doesn't do what we would want anyway, except in the hands of an expert user (mingw's bts is on sf, and we have reportbug et al. for ours); then if this is a bug, I guess the solution is to simply remove all i586-mingw32msvc-gccbug related bits from the package. If someone knows of it AND (rightly) thinks the bug they found in mingw should go directly to upstream gcc-maint using it, then they probably also have it installed. Otherwise, by default, we should probably steer reports related to this package back through the people who have added additional layers to it. So my choices would be: a) Close this report and leave it as it is. People who expect gccbug and are familiar with its use will probably find the dangling link does what they might expect. b) Depend on gcc, closing the dangle and this bug. c) Modify the upstream distribution further during the package build to purge any reference to gccbug. Which would you prefer? (question open to other interested parties too) cheers, Ron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
