On Wed, Feb 22, 2023 at 06:18:23AM -0500, Neal Gompa wrote:
> On Tue, Feb 21, 2023 at 3:48 PM Matthew Miller <mattdm(a)fedoraproject.org>
wrote:
> >
> > I was asked to weigh in on
https://pagure.io/releng/issue/7215 as a
> > priority. Last time we talked about this we didn't really get anywhere...
> >
> >
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
> >
> > ... and that ticket hasn't moved, because fixing it isn't trivial.
> >
> >
> > What we're doing now — as has been the case for several years, already
noted
> > in the previous discussion — has very little end-user value. Also as noted
> > in that thread (as in the ticket)... that's unfortunate, because it did
> > bring some real benefits (and could possibly do even more.)
> >
>
> Our tooling has been broken for a long time and contributions to that
> tooling is just not going to happen since nobody can run this stuff
> outside of Fedora infrastructure. It's a sad state of affairs indeed.
It's not "broken" just because it doesn't do what you would like it to
do. Please can we not disparage other peoples work?
The reason it behaves this way is because koji has no concept of 'newer
version' or 'older version'. It has only when a valid build was tagged
into a tag, and pungi operates on that with 'give me the latest tagged
packages in these tags'.
We could merge current repos into the newly created one from pungi, but
it would be a vast amount of work. It would mean all repodata would need
to be regenerated. That said, it could be done, but no one has had the
cycles to work on it.
I'm guessing this would also make composes slower and less reliable?
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org