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 > dch: Did you see that warning? Press RETURN to continue... > > $ bts status 504907 > bug_num 504907 > source unknown [...] > 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. At the moment, I'm inclined to say that it's an issue on the BTS side. Requesting a list of bugs for the source package "soci" via SOAP returns 0 bugs, whereas requesting those for the /binary/ package "soci" returns two; however, as far as I can see, there is no such binary package. > I've tried reassigning the relevant bugs to the source package but > I'm unable to see how to set the source field in bts status, which I > think is what debchange is reading. The warning is being caused by a combination of issues, stemming from the fact that requesting a list of all bugs affecting the "soci" source package currently returns no results (as mentioned above). The BTS's SOAP interface doesn't return source package names by default when requesting a bug's status, which is why it shows up as "unknown" in "bts status". I've made a local change to make "status" pass the parameter specifying that source information should be returned, which I'll commit soon. As far as I'm aware, you can't explicitly set the "source" field on a bug once it's been filed; the BTS derives it. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
