On Mon, 2008-12-22 at 18:45 +0000, Adam D. Barratt wrote: > On Mon, 2008-12-22 at 17:57 +0000, Neil Williams wrote: > > $ dch -a --closes 504907 > > dch: No bugs found for package soci > > dch warning: bug #504907 belongs to package soci (src ?), > > not to soci: disabling closing changelog entry [...] > > I'm not sure if this is a regression in bugs.debian.org or a problem > > in debchange, but it now appears to be impossible to stop dch disabling > > the --closes functionality for bugs filed against the source package. > > The relevant code in debchange hasn't changed for a while. I've asked on > IRC whether there's been a recent change in debbugs which would account > for this.
Having discussed this a little more with one of the BTS maintainers, I believe I've now got a clearer understanding of what's going on. The central issue is the fact that the bug is (well, was) filed against the binary package "soci" which does not exist. In the past, the BTS attempted to guess what you meant in such cases, which wasn't always correct; there have therefore been some recent(ish) changes which mean that such bugs don't appear in a query for bugs assigned to the source package. The solution is to assign the bug to "src:soci", which I've done for the bug you used as an example. That means it appears in a query for bugs in the source package, either via SOAP or using http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=soci ; unfortunately not everything has been updated yet, so http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504907 doesn't currently work. A naive "fix" would be to make debchange look at binary package bugs in the absence of any filed against the source package. Doing so would open a can of worms, however; for example, the archive currently contains a source package named "sm" which produces an "r-cran-sm" binary package and a "screen-message" source package which produces an "sm" binary package. For that reason, I'm not sure there's much that debchange can / should do here. [For reference, I believe that #509498, filed a short while ago against bugs.debian.org is another instance of the same underlying issue]. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
