Hi Ian,
On 08-05-18 14:10, Ian Jackson wrote:
> Paul Gevers writes ("Re: Dealing with ci.d.n for package regressions"):
>> On 04-05-18 15:24, Ian Jackson wrote:
>>> I think therefore that tests should be triggered based, additionally,
>>> on binary package dependencies as found in the archive. For every
>>> binary package B which is produced by a source package S and depends
>>> on another binary package D: tests of S should be retriggered for
>>> updates to D. "Depends on" would probably mean "is mentioned as first
>>> alternative in any Depends on Recommends requirement". This can be
>>> determined from the published metadata without unpacking any source
>>> packages or looking at Testsuite-Triggers.
>>
>> Let me ponder on this a bit more.
>
> Let me know what you think.
I think I already wrote the answer in a later e-mail. Britney does this
already directly. It doesn't need to use the Testsuite-Triggers for that.
>> The code to calculate which packages are triggered lives here:
>> https://salsa.debian.org/release-team/britney2/blob/master/britney.py
>> (bfa02859 Line 334-340)
>
> Thanks. I haven't worked on Britney before. Can you point me to
> instructions for testing changes to it ?
https://release.debian.org/doc/britney/contributing-to-britney.html
Paul
Attachment:
signature.asc
Description: OpenPGP digital signature