package tracking system issues

[Jay Berkenbilt <qjb@debian.org>]

How does one report problems with the package tracking system?  I
followed the link on packages.qa.debian.org and got no response.
That's certainly not a complaint -- I don't necessarily expect to get
a response right away, but I have no way of tracking this or knowing
whether my comments have been received.

There are three things that seem wrong about what's on the package
tracking package for icu (http://packages.qa.debian.org/i/icu.html):

 1.  The system warns that the bug tracking system contains patches,
     but there aren't any bugs with patches except one bug that has
     been closed for a long time and in fact will be archived in one
     day.  There's a note about a patch from Ubuntu.  Maybe it's
     counting that.

 2.  PTS shows one release critical bug and shows that icu (source) is
     buggy in the testing status area.  There aren't any release
     critical bugs against icu right now.  Even clicking on the link
     from PTS doesn't show any.  Also, the release critical bug report
     doesn't show any bugs against icu.  There is a bug against icu28
     which creates a binary package with the same name as one of icu's
     packages (this is the release critical bug).  Maybe PTS is
     getting confused by that?

 3.  ICU has not been rebuilt on hppa (like anything else recently
     uploaded), m68k, or sparc, but PTS is not showing it to be out of
     date on those platforms.  I thought it always showed that even
     when there were other issues such as the age being too low.

If anyone can shed some light on any of these, that would be helpful.
It looks like PTS has had many recent improvements, which is great.
If there are a few problems, I'd like to do my duty and report them so
that they can get fixed while the changes are fresh.  The first thing
I did was look for a pseudopackage in the bug tracking system for PTS,
but I couldn't find one.  Perhaps I overlooked it?

Thanks!

-- 
Jay Berkenbilt <qjb@debian.org>