Matthew Palmer a écrit :
reassign 389579 libapache2-mod-auth-mysql
thanks
On Mon, Oct 30, 2006 at 06:52:45PM -0500, Filipus Klutiero wrote:
Matthew Palmer a écrit :
On Sun, Oct 29, 2006 at 01:43:47AM -0400, Filipus Klutiero wrote:
This bug is against the libapache-mod-auth-mysql source package, not the
binary package, which has no bug.
Well then, please assign the bug to the source package, then.
This is what I'm doing.
No you're not.
It is what I was doing.
The 'reassign' command only manipulates the value of the
'binary package' attribute of the bug report. If you view the bugs page for
the libapache-mod-auth-mysql binary package during the time that you've
reassigned the bug to that package, you will see that the bug shows up in
that package's list -- moreover, it does *not* show up in the
libapache2-mod-auth-mysql package's bug list.
Determining whether a bug is assigned to a binary package or to a source
package of the same name can't be done mechanically. As the BTS is
mechanical, it doesn't represent things perfectly. It also doesn't care
about being too exact and simply considers that all bugs are assigned to
a binary package.
At the moment
all you're doing is moving the bug to a binary package that, by your own
acknowledgement, does not contain the bug.
Reassigning to a binary package and a source package of the same name
are two mechanically indistinguishable things.
Have you tried assigning a bug to a source package which did *not* have a
binary package of the same name? What was the result?
Yes. See #393592.
One needs to use context to determine if the bug is against the source or
binary package.
Once you've taught the BTS software about context, you may feel free to
fiddle around. Until then, please leave the bug alone.
No problem, I didn't intend to spend any more time on this. I'm leaving
you the responsability to handle this bug report (or to fix it :) ).
