Jens Seidel wrote, 12 September 2007 08:00:
[...]
Hhm, I noticed that
http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=hex-a-hop
sometimes contains fixed bugs with "Done" status as outstanding and
sometimes not.
I first wanted to report it until I saw that a package has to be built
on *all* architectures. This is *not* true for hex-a-hop (m68) so I
expect (according to the quoted mail) that also "Done" bugs
(such as #438800) show up as unresolved (but I would prefer to have
these bugs listed as resolved).
That's a slight imprecision on my part, although in practical terms it
rarely makes a difference. The bug must be not present on all architectures.
Although hex-a-hop is out-of-sync on m68k, that doesn't affect the bug's
status. The bug is marked as found in -3 and fixed in -4 but m68k currently
has -2 which is not marked as being affected by the bug.
Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
