[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Dealing with ci.d.n for package regressions

Paul Gevers writes ("Re: Dealing with ci.d.n for package regressions"):
> Can we carry this discussion over to debian-ci@lists.debian.org (added
> in CC now)?

Sure.  Dropped the other lists.

> 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.

> 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 ?


Ian Jackson <ijackson@chiark.greenend.org.uk>   These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Reply to: