> On 12 Mar 2025, at 20:21, Santiago Vila <sanv...@debian.org> wrote:
> 
> El 12/3/25 a las 20:02, Christoph Schmidt-Hieber escribió:
>> In your instructions, I do not understand the following terms:
>> “reassign”
>> “add an affects on src:stimfit”
>> “visible in the BTS web page”
> 
> Those are terms used when dealing with the Debian bug system.
> The full explanation may be found here:
> 
> https://www.debian.org/Bugs/server-control
> 
> Before reporting that stimfit does not build from source,
> I look here to be sure that nobody reported it before:
> 
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=stimfit
> 
> If the real bug is not in stimfit, but instead
> in one of the build-depends, the right thing to
> do would be to reassign the bug to the package actually
> making stimfit not to build ok.
> 
> However, the reassign operation makes the bug to
> disappear from the above web page, and I would
> not find it if I were looking for duplicates.
> 
> The "affects" operation tells the Debian bug system
> that a bug in one package really affects another package,
> and the outcome is that the bug is still shown in the
> web page for the affected package.
> 
> Thanks.

Thank you for the explanation. Now I understand your original message.
In fact the bug ist *not* in one of the build depends, it’s in stimfit so that
I do not have to do any of this reassignment magic.

I have prepared a new version of stimfit that closes this bug. If you can
sponsor it, I could upload it to Debian mentors. Otherwise I’d contact one
of the other usual suspects.

Best wishes
Christoph

Reply via email to