Hi Adam,
thanks for all your bugreports, I really appreciate your help and
suggestions. But this time I think you're wrong. RNG *always* shows the
latest info from
bugs.debian.org/reportbug-ng
It always gets the html from this URL and parses it. Please have a look
at the first lines of this site:
Debian Bug report logs: package reportbug-ng in unstable (versions
0.2007.03.24, 0.2007.03.29)
This means for some archs, 0.2007.03.24 is still the current version in
unstable and in this version #416132 was not yet fixed.
There is a difference when you look at the bugs at RNG's *source* package
bugs.debian.org/src:reportbug-ng
where #416132 is of course closed.
In contrast to reportbug, I'm not showing the status of he source
package on purpose since some packages like kdelibs have thousands of
bugs, while shiping many binary packages like kate which has only a few
dozens of bugs. If I'd show all the bugs from kdelibs if someone queries
for kate, the user would be overwhelmed by thousands of unrelated
bugreports.
If you agree, I'll close your bugreport. Feel free to reopen it if you
don't agree with me.
Cheers,
Bastian
Adam Porter schrieb:
> Looking at the bugs for r-ng, it shows #416132 as "Outstanding," but going to
> the b.d.o page for r-ng in Konqueror shows that same bug as "Resolved."
--
Bastian Venthur http://venthur.de
Debian Developer venthur at debian org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
