[ Reordering the paragraph ]
On Tue, 02 Dec 2014, Don Armstrong wrote:
So should I use source as a base and then restrict to the set of
source packages available in found_versions (if any)?
It depends on what you're using that field for. If you're using it to
show a set of bugs which may
Control: reassign -1 debbugs
Control: affects -1 tracker.debian.org
Control: retitle -1 Bugs in binary packages which have migrated from one source
package to another show up in the wrong source package
On Wed, 03 Dec 2014, Raphael Hertzog wrote:
On Tue, 02 Dec 2014, Don Armstrong wrote:
It
On Mon, 01 Dec 2014, Don Armstrong wrote:
It would be nice if we could just use the source field instead of
doing our own mapping bug the value of the source field doesn't make
much sense to me... why does it list so many source packages and not
only one like on
On Tue, 8 Jul 2014 23:41:51 +0200 Raphael Hertzog hert...@debian.org wrote:
[ Cc ow...@bugs.debian.org for a question ]
Sorry; I missed this the first time around until Paul Wise pinged me on
IRC about it.
On Fri, 04 Jul 2014, Andreas Cadhalpun wrote:
Looking at [1] I find it strange, that
[ Cc ow...@bugs.debian.org for a question ]
On Fri, 04 Jul 2014, Andreas Cadhalpun wrote:
Looking at [1] I find it strange, that it says:
'1 bug tagged help in the BTS'
While at the same time there is no open bug and indeed clicking on the '1
bug' link leads to [2] without a bug.
Probably
Package: tracker.debian.org
Severity: normal
Dear maintainer,
thanks for the new package tracker. ;)
Looking at [1] I find it strange, that it says:
'1 bug tagged help in the BTS'
While at the same time there is no open bug and indeed clicking on the
'1 bug' link leads to [2] without a bug.
6 matches
Mail list logo
