Merge Opportunities Report - 2020-02-04

[Bryce Harrington]

On Wed, Feb 05, 2020 at 08:15:40AM +0100, Christian Ehrhardt wrote:
> On Wed, Feb 5, 2020 at 8:13 AM Christian Ehrhardt <
> christian.ehrhardt at canonical.com> wrote:
> >> low   ipxe                      1.0.0+git-20190125.36a4c85-4
> >> 1.0.0+git-20190109.133f4c4-0ubuntu2
> >
> >
> > @bryce - If you have overrides, as long as Debian is on 1.0.0+git-20190125
> > we can skip it from this list.
> >
> >
> >> low   spice-protocol            0.14.0-1
> >> 0.14.0-0ubuntu1
> >>
> >
> > \o/ Debian got to 14 - this can be a sync now, I will do that
> >
> 
> And 5 minutes later I'm as smart as I was last year already :-/
> This is a case of tarball mismatch.
> @Bryce - could we skip this from the list as long as it stays on 0.14.0 in
> Debian ?

I can see we'll need several different kinds of blacklists.  :-)

The existing blacklist is for packages where Ubuntu is the upstream, so
don't need "merged".

For these two packages we need versioned blacklists, which exclude
listing packages from Debian for a given upstream version number.

I've sketched in a preliminary implementation that should work, but want
to get a bit more testing time on it before rolling it out.

Brainstorming a bit, I think we may be interested in blacklisting a
couple other situations:

  * The new debian version would introduce a regression, so we want to
    skip that particular debian dash number.

  * Debian has moved to a newer upstream version than what we want to be
    shipping for the current devel series.  E.g. we want to stick with
    upstream's LTS version.  We'll reconsider once the next devel series
    opens.

Are there other situations beyond these two plus the two mentioned
earlier, that we may want to blacklist?

Bryce