On Sat, Apr 10, 2021 at 07:33:42PM +0200, Fabio Valentini wrote:
On Tue, Apr 6, 2021 at 12:42 PM Fabio Valentini
<decathorpe(a)gmail.com> wrote:
> ---
A quick update:
I have created the missing bodhi updates where the packagers obviously
just forgot to file one, or missed the announcement of the
updates-testing activation point (i.e. builds for f35 and f34 (and
sometimes f33 or even f32) exist, but no bodhi update for f34 was
created).
As far as I can see, this leaves 21 packages with issues, those being
various combinations of:
- a missing commit in f34 dist-git branch,
- a missing koji build for f34,
- mistagged packages, possibly related to a build that happened right
during mass branching (looking at you, gecode).
Question regarding further actions:
- Would it be OK if I fix a few packages where there are missing
*builds* for f34 as well?
(Of course, only where it is obvious that the packager just forgot to
merge the same changes that already happened on rawhide and f33
branches.)
+1
- Would it be OK if I file freeze exceptions for the bodhi updates
that fix upgrade path, or is it fine if they are just 0day-updates?
(Freeze-excepting packages that land on any images would probably be a
good idea, but I don't know how to check that for individual
packages.)
0day-updates should be enough.
Zbyszek