[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#695508: marked as done (udd: bugs.cgi - bugs filed against multiple packages is not associated with a source)

Your message dated Tue, 29 Jan 2013 16:56:03 +0100
with message-id <20130129155603.GA8284@xanadu.blop.info>
and subject line Re: Bug#695508: udd: bugs.cgi - bugs filed against multiple packages is not associated with a source
has caused the Debian Bug report #695508,
regarding udd: bugs.cgi - bugs filed against multiple packages is not associated with a source
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
695508: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695508
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: qa.debian.org
Severity: normal
User: qa.debian.org@packages.debian.org
Usertags: udd

The bug #694368 is filed against libfuzzy2, libfuzzy-dev (src:
ssdeep).  At least in the view [1], this means that the "package"
column gets the PTS link wrong.  It links to p.qa.d.o/libfuzzy2 and
p.qa.d.o/libfuzzy-dev (respectively), but it should have linked to
p.qa.d.o/ssdeep in both cases.  This is not a huge problem as the
PTS fixes this with a redirect, but ...

I suspect also causes bugs.cgi not discovering the unblock hint for
ssdeep.  On a related note; as ssdeep is unblocked the package will
problably migrate in a week (causing the example disappear from the
view).  Let me know if I should find more information before then.

~Niels

[1] http://udd.debian.org/bugs.cgi?release=wheezy_not_sid&merged=ign&fnewerval=7&rc=1&sortby=id&sorto=asc&chints=1&ctags=1&cdeferred=1&crttags=1

--- End Message ---
--- Begin Message --- 
On 05/01/13 at 23:53 +0100, Ivo De Decker wrote:
> Hi Lucas,
> 
> On Sat, Dec 29, 2012 at 12:05:38PM +0100, Lucas Nussbaum wrote:
> > > I could try to create a patch, but I don't know where to get the data to do
> > > the test, so I'll leave that to someone else.
> 
> > If you could write a basic patch, I could try to test it myself.
> > 
> > Alternatively, you could get the BTS data using rsync:
> > $ rsync bugs-mirror.debian.org::
> > bts-spool-db   	[bugs-mirror.debian.org] active bug spool
> > bts-spool-archive	[bugs-mirror.debian.org] archived bug spool
> > bts-spool-index	[bugs-mirror.debian.org] bug index files
> > bts-versions   	[bugs-mirror.debian.org] bts package version information
> > But I'm not sure it's worth the trouble.
> 
> To run the bugs import, a number of files from /srv/bugs.debian.org/etc are
> also needed. I don't know if they are available somewhere.
> 
> Most of the necessary files can be empty or generated from other data, so I
> was able to do some basic testing, and I created a patch (attached) that
> should fix the import part of this bug.

Hi,

I've just applied your patch. Thanks!

Lucas

--- End Message ---
Reply to: