On 2026-01-18 13:37, Paul Gevers wrote:
Control: close -1
# Because I filed this bug myself, I decided to use this command;
don't imitate lightly
Hi Trupti,
On 1/16/26 10:00, Sébastien Villemot wrote:
Le mercredi 14 janvier 2026 à 20:29 +0100, Paul Gevers a écrit :
On 1/14/26 20:05, Sébastien Villemot wrote:
Paul: if my statement above is correct, what would be the right
course
of action?
The right action would be to get those pacakges fixed, e.g. via
filing
bugs (cloning and reassigning might be appropriate). When the bugs
are
in place, I can hint src:openblas into testing.
Thanks, this has been done by Trupti.
After hitting the sent button, I realized I hadn't been overly
explicit. Let me try to explain what I had in mind. As we now consider
the bugs to lie in the other packages, after the reassigning there
shouldn't be a bug against src:openblas anymore. This bug is (until my
close trickles through) blocking migration. It is also no longer
actionable by the openblas maintainers. If I had done the bug
management, I would have first fixed metadata (removal of current
affects, removal of help tag) and then reassigned the two clones and
the original. Also please be aware that the maintainers of the
packages you reassign bugs to only get a mail from the bts with the
results of the control commands. It is considered courtesy to CC them
on the reassign message (e.g. by using <package>@packages.debian.org)
with a short explanation for the reassign.
Paul
Hi Paul,
Apologies for the doing wrong process of reassignment— I wasn’t aware of
the preferred BTS workflow at the time. Thanks for pointing it out; I’ll
take care to follow this approach in future.
Best regards,
Trupti
