5:42 a.m.
Hi everybody,
It's that time of the year again, and this time there's not that many
downgrades to complain about (packages with "obvious" causes, like
F34FTBFS, already excluded from the list).
However, the list also includes some pretty important "critpath"
packages (ostree (!), rpm-ostree, libuv, ...), which should probably
be fixed before F34 is released. Shipping with old ostree packages
OOTB seems like a bad idea, especially for the Editions that are built
on top of it.
For the other problems: What should be done about them? Some
successful builds only need the missing bodhi update created, some
others additionally need dist-git changes merged from rawhide (?) and
a build in koji.
Full list of package downgrades below (plus my best-effort
investigation for the cause).
Fabio
---
- YafaRay-0:3.5.1-8.fc33 > YafaRay-0:3.5.1-7.fc34
- YafaRay-blender-0:3.5.1-8.fc33 > YafaRay-blender-0:3.5.1-7.fc34
- YafaRay-devel-0:3.5.1-8.fc33 > YafaRay-devel-0:3.5.1-7.fc34
- YafaRay-lib-0:3.5.1-8.fc33 > YafaRay-lib-0:3.5.1-7.fc34
YafaRay seems to have been updated on f33 but not on f34, or the
release bump was done to the "main" integer instead of appending .1
after dist if it was a stable-release-branch-only change.
- android-tools-1:30.0.5p1-1.fc33 > android-tools-0:20180828gitc7815d675-8.fc33
This package switched to a different upstream and a sane versioning
scheme, but apparently needs an Epoch to fix the upgrade path.
- charliecloud-0:0.22-2.fc33 > charliecloud-0:0.21-2.fc34
- charliecloud-doc-0:0.22-2.fc33 > charliecloud-doc-0:0.21-2.fc34
- charliecloud-test-0:0.22-2.fc33 > charliecloud-test-0:0.21-2.fc34
This package was updated for f35 and f33 but not for f34.
- compat-golang-github-git-lfs-gitobj-2-devel-1:1.4.1-1.fc33 >
compat-golang-github-git-lfs-gitobj-2-devel-0:2.0.1-2.fc34
I have seen this package before, and it looks like the versioning of
the compat package is off (or at least, the Epoch is missing on F34+).
- conky-0:1.12.1-1.fc33 > conky-0:1.11.6-2.fc34
Was successfully built for f34, but no bodhi update was submitted.
- container-selinux-2:2.160.0-1.fc33 >
container-selinux-2:2.158.0-1.gite78ac4f.fc34
Bad rhcontainerbot (built for f34, but no update created).
- cppad-devel-0:20210000.3-3.fc33 > cppad-devel-0:20210000.3-2.fc34
- cppad-doc-0:20210000.3-3.fc33 > cppad-doc-0:20210000.3-2.fc34
Update was built for f34, but no bodhi update was created.
- erfa-0:1.7.2-2.fc33 > erfa-0:1.7.2-1.fc34
- erfa-devel-0:1.7.2-2.fc33 > erfa-devel-0:1.7.2-1.fc34
Bad Release tag in F33 screwing with upgrade path.
- gecode-0:6.2.0-6.fc33 > gecode-0:6.2.0-5.fc34
- gecode-devel-0:6.2.0-6.fc33 > gecode-devel-0:6.2.0-5.fc34
- gecode-doc-0:6.2.0-6.fc33 > gecode-doc-0:6.2.0-5.fc34
- gecode-examples-0:6.2.0-6.fc33 > gecode-examples-0:6.2.0-5.fc34
Newer fc34 package has been tagged f35-only, f34 has an older fc34
package. Maybe it was built during the F34 branch point and something
screwed up.
- golang-tinygo-x-llvm-devel-0:0-0.17.20210315git435a266.fc33 >
golang-tinygo-x-llvm-devel-0:0-0.16.20201119git570e7a6.fc34
Updated for f32 and f33, but not for f34 or rawhide.
- gqrx-0:2.14.4-2.fc33 > gqrx-0:2.14.4-1.fc34
Updated for f33 and rawhide, but not for f34.
- hamlib-0:4.1-2.fc33 > hamlib-0:4.1-1.fc34
- hamlib-c++-0:4.1-2.fc33 > hamlib-c++-0:4.1-1.fc34
- hamlib-c++-devel-0:4.1-2.fc33 > hamlib-c++-devel-0:4.1-1.fc34
- hamlib-devel-0:4.1-2.fc33 > hamlib-devel-0:4.1-1.fc34
- hamlib-doc-0:4.1-2.fc33 > hamlib-doc-0:4.1-1.fc34
- perl-hamlib-0:4.1-2.fc33 > perl-hamlib-0:4.1-1.fc34
- python3-hamlib-0:4.1-2.fc33 > python3-hamlib-0:4.1-1.fc34
- tcl-hamlib-0:4.1-2.fc33 > tcl-hamlib-0:4.1-1.fc34
Rebuilt on f33 but not on f34 or rawhide.
- hyperscan-0:5.4.0-1.fc33 > hyperscan-0:5.3.0-6.fc34
- hyperscan-devel-0:5.4.0-1.fc33 > hyperscan-devel-0:5.3.0-6.fc34
Updated to 5.4.0 only on f33, but not for f34 or rawhide.
- icedtea-web-0:2.0.0-pre.2.alpha13.patched1.fc33 >
icedtea-web-0:2.0.0-pre.0.3.alpha16.patched1.fc34.3
Versioning snafu - alpha 13 should not sort higher than alpha 16, I guess.
- kata-runtime-0:1.12.1-3.fc33 > kata-runtime-0:1.12.1-2.fc34
Versioning snafu. Package also dumps half its spec file contents into
the %description tag:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1718489
- klog-0:1.4.7-2.fc33 > klog-0:1.4.4-3.fc34
Updated to 1.4.7 only for f32 and f33, but not f34 or rawhide.
- libreswan-0:4.3-1.fc33 > libreswan-0:4.2-1.fc34
Version 4.3 was built for f33 and rawhide, but not for f34.
- libuv-1:1.41.0-1.fc33 > libuv-1:1.40.0-2.fc34
- libuv-devel-1:1.41.0-1.fc33 > libuv-devel-1:1.40.0-2.fc34
- libuv-static-1:1.41.0-1.fc33 > libuv-static-1:1.40.0-2.fc34
libuv 1.41.0 was built for f34, but the bodhi update is stuck (build
is mistagged in koji?):
https://bodhi.fedoraproject.org/updates/FEDORA-2021-9ab6c1ee93
- mingw32-libusbx-0:1.0.24-1.fc33 > mingw32-libusbx-0:1.0.22-7.fc34
- mingw32-libusbx-static-0:1.0.24-1.fc33 >
mingw32-libusbx-static-0:1.0.22-7.fc34
- mingw64-libusbx-0:1.0.24-1.fc33 > mingw64-libusbx-0:1.0.22-7.fc34
- mingw64-libusbx-static-0:1.0.24-1.fc33 >
mingw64-libusbx-static-0:1.0.22-7.fc34
mingw-libusbx 1.0.24 was built for f33 and rawhide, but not for f34.
- nagios-plugins-nrpe-0:4.0.3-6.fc33 > nagios-plugins-nrpe-0:4.0.3-3.fc34
- nrpe-0:4.0.3-6.fc33 > nrpe-0:4.0.3-3.fc34
Rebuilt for f33 and rawhide, but not for f34.
- nsd-0:4.3.5-1.fc33 > nsd-0:4.3.2-3.fc34
Updated to 4.3.5 for f33 and rawhide, but not on f34.
- ostree-0:2021.1-2.fc33 > ostree-0:2020.8-2.fc34
- ostree-devel-0:2021.1-2.fc33 > ostree-devel-0:2020.8-2.fc34
- ostree-grub2-0:2021.1-2.fc33 > ostree-grub2-0:2020.8-2.fc34
- ostree-libs-0:2021.1-2.fc33 > ostree-libs-0:2020.8-2.fc34
- ostree-tests-0:2021.1-2.fc33 > ostree-tests-0:2020.8-2.fc34
2021.1 was built for f34, but no bodhi update was created.
- python-PyLEMS-doc-0:0.5.2-1.fc33 > python-PyLEMS-doc-0:0.5.1-2.fc34
- python3-PyLEMS-0:0.5.2-1.fc33 > python3-PyLEMS-0:0.5.1-2.fc34
Updated to 0.5.2 for f32, f33, and rawhide, but not for f34.
- python-niapy-doc-0:2.0.0-0.2rc10.fc33 > python-niapy-doc-0:2.0.0-0.1rc13.fc34
- python3-niapy-0:2.0.0-0.2rc10.fc33 > python3-niapy-0:2.0.0-0.1rc13.fc34
Versioning snafu. rc10 should not sort higher than rc13, I assume.
- python-scrapy-doc-0:2.4.1-1.fc33 > python-scrapy-doc-0:1.5.1-10.fc34
- python3-scrapy-0:2.4.1-1.fc33 > python3-scrapy-0:1.5.1-10.fc34
The 2.4.1 update had been built for f34, but no bodhi updates has been
submitted.
- python3-pyunicorn-0:0.6.1-2.fc33 > python3-pyunicorn-0:0.6.1-1.fc34
Version 0.6.1-2 has been built for f32, f33, and rawhide, but not for f34.
- recoll-0:1.30.0-1.fc33 > recoll-0:1.29.2-1.fc34
- recoll-gssp-0:1.30.0-1.fc33 > recoll-gssp-0:1.29.2-1.fc34
- recoll-kio-0:1.30.0-1.fc33 > recoll-kio-0:1.29.2-1.fc34
Version 1.30.0 has been built for f34, but no bodhi update was submitted.
- reportd-0:0.7.4-8.fc33 > reportd-0:0.7.4-4.fc34
Changes that appear to have been intended to land in rawhide were only
pushed to f33 (???).
- resalloc-0:3.4-1.fc33 > resalloc-0:3.3-3.fc34
- resalloc-server-0:3.4-1.fc33 > resalloc-server-0:3.3-3.fc34
- python3-resalloc-0:3.4-1.fc33 > python3-resalloc-0:3.3-3.fc34
Version 3.4 has been built for f32, f33, and rawhide, but not for f34.
- rpm-ostree-0:2021.3-2.fc33 > rpm-ostree-0:2021.2-2.fc34
- rpm-ostree-devel-0:2021.3-2.fc33 > rpm-ostree-devel-0:2021.2-2.fc34
- rpm-ostree-libs-0:2021.3-2.fc33 > rpm-ostree-libs-0:2021.2-2.fc34
Failed to build, probably due to the missing ostree updates ...
- scap-security-guide-0:0.1.55-1.fc33 > scap-security-guide-0:0.1.54-2.fc34
- scap-security-guide-doc-0:0.1.55-1.fc33 >
scap-security-guide-doc-0:0.1.54-2.fc34
Updated to 0.1.55 on f32, f33, and rawhide, but not on f34.
- tinygo-0:0.17.0-1.fc33 > tinygo-0:0.16.0-3.fc34
tinygo 0.17.0 was built for f32 and f33, but not f34 or rawhide.
- virt-dib-1:1.44.1-1.fc33 > virt-dib-0:1.45.3-3.fc34
This subpackage seems to have been accidentally dropped from F34+ when
it was dropped for RHEL 9?
- ydotool-0:0.2.0-5.fc33 > ydotool-0:0.2.0-4.fc34
Rawhide-only rebuilt commit was unnecessarily merged and built for f32
and f33, but not for f34.
- yoshimi-0:2.0-1.fc33 > yoshimi-0:1.7.4-2.fc34
yoshimi 2.0 was built for f34, but no bodhi update was created.
5:48 a.m.
New subject: Package downgrades from Fedora 33 -> Fedora 34 (including ostree
+ rpm-ostree)
On Tue, Apr 06, 2021 12:42:33 +0200, Fabio Valentini wrote:
Hi everybody,
Hello!
Thanks very much for catching this.
- python-PyLEMS-doc-0:0.5.2-1.fc33 >
python-PyLEMS-doc-0:0.5.1-2.fc34
- python3-PyLEMS-0:0.5.2-1.fc33 > python3-PyLEMS-0:0.5.1-2.fc34
Updated to 0.5.2 for f32, f33, and rawhide, but not for f34.
Building and pushing an update to F34 now.
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) |
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
6 a.m.
New subject: Package downgrades from Fedora 33 -> Fedora 34 (including ostree
+ rpm-ostree)
On Tue, Apr 6, 2021 at 12:43 PM Fabio Valentini <decathorpe(a)gmail.com>
wrote:
- libuv-1:1.41.0-1.fc33 > libuv-1:1.40.0-2.fc34
- libuv-devel-1:1.41.0-1.fc33 > libuv-devel-1:1.40.0-2.fc34
- libuv-static-1:1.41.0-1.fc33 > libuv-static-1:1.40.0-2.fc34
libuv 1.41.0 was built for f34, but the bodhi update is stuck (build
is mistagged in koji?):
https://bodhi.fedoraproject.org/updates/FEDORA-2021-9ab6c1ee93
I unpushed the libuv update and queued it to stable again. Hopefully this
is enough to fix this.
--
Kalev
10 a.m.
New subject: Package downgrades from Fedora 33 -> Fedora 34 (including ostree
+ rpm-ostree)
On Tue, Apr 6, 2021 at 1:01 PM Kalev Lember <kalevlember(a)gmail.com> wrote:
On Tue, Apr 6, 2021 at 12:43 PM Fabio Valentini <decathorpe(a)gmail.com> wrote:
>
> - libuv-1:1.41.0-1.fc33 > libuv-1:1.40.0-2.fc34
> - libuv-devel-1:1.41.0-1.fc33 > libuv-devel-1:1.40.0-2.fc34
> - libuv-static-1:1.41.0-1.fc33 > libuv-static-1:1.40.0-2.fc34
>
> libuv 1.41.0 was built for f34, but the bodhi update is stuck (build
> is mistagged in koji?):
> https://bodhi.fedoraproject.org/updates/FEDORA-2021-9ab6c1ee93
I unpushed the libuv update and queued it to stable again. Hopefully this is enough to
fix this.
Apparently that was enough. Thanks!
Fabio
9:28 a.m.
New subject: Package downgrades from Fedora 33 -> Fedora 34 (including ostree
+ rpm-ostree)
On Tue, Apr 06, 2021 at 12:42:33PM +0200, Fabio Valentini wrote:
- icedtea-web-0:2.0.0-pre.2.alpha13.patched1.fc33 >
icedtea-web-0:2.0.0-pre.0.3.alpha16.patched1.fc34.3
Versioning snafu - alpha 13 should not sort higher than alpha 16, I guess.
In case it's not obvious, it's the change from "pre.2" to
"pre.0.3" that is
the oops.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
4:28 p.m.
New subject: Package downgrades from Fedora 33 -> Fedora 34 (including ostree
+ rpm-ostree)
On Tue, Apr 06, 2021 at 10:28:08AM -0400, Matthew Miller wrote:
On Tue, Apr 06, 2021 at 12:42:33PM +0200, Fabio Valentini wrote:
> - icedtea-web-0:2.0.0-pre.2.alpha13.patched1.fc33 >
> icedtea-web-0:2.0.0-pre.0.3.alpha16.patched1.fc34.3
>
> Versioning snafu - alpha 13 should not sort higher than alpha 16, I guess.
In case it's not obvious, it's the change from "pre.2" to
"pre.0.3" that is
the oops.
Strictly speaking, we don't require versions to not go down
(i.e. 'distro-sync --releasever=34' is recommended over 'upgrade
--releasever=34').
So while ugly, this is not a problem.
Zbyszek
9:40 a.m.
Hi,
On Tue, Apr 6, 2021, at 6:42 AM, Fabio Valentini wrote:
Hi everybody,
It's that time of the year again, and this time there's not that many
downgrades to complain about (packages with "obvious" causes, like
F34FTBFS, already excluded from the list).
However, the list also includes some pretty important "critpath"
packages (ostree (!), rpm-ostree, libuv, ...), which should probably
be fixed before F34 is released. Shipping with old ostree packages
OOTB seems like a bad idea, especially for the Editions that are built
on top of it.
Hi, thanks for raising this. The two updates are
https://bodhi.fedoraproject.org/updates/FEDORA-2021-33f693d20d
https://bodhi.fedoraproject.org/updates/FEDORA-2021-971f672259
9:58 a.m.
New subject: Package downgrades from Fedora 33 -> Fedora 34 (including ostree
+ rpm-ostree)
On Tue, Apr 6, 2021 at 4:43 PM Colin Walters <walters(a)verbum.org> wrote:
Hi,
On Tue, Apr 6, 2021, at 6:42 AM, Fabio Valentini wrote:
> Hi everybody,
>
> It's that time of the year again, and this time there's not that many
> downgrades to complain about (packages with "obvious" causes, like
> F34FTBFS, already excluded from the list).
>
> However, the list also includes some pretty important "critpath"
> packages (ostree (!), rpm-ostree, libuv, ...), which should probably
> be fixed before F34 is released. Shipping with old ostree packages
> OOTB seems like a bad idea, especially for the Editions that are built
> on top of it.
Hi, thanks for raising this. The two updates are
https://bodhi.fedoraproject.org/updates/FEDORA-2021-33f693d20d
https://bodhi.fedoraproject.org/updates/FEDORA-2021-971f672259
Thanks! It would probably be a good idea to request freeze exceptions
for them sooner rather than later, so testing of the candidate images
will be done with the new versions.
Fabio
1:39 p.m.
New subject: Package downgrades from Fedora 33 -> Fedora 34 (including ostree
+ rpm-ostree)
On 4/6/21 10:58 AM, Fabio Valentini wrote:
On Tue, Apr 6, 2021 at 4:43 PM Colin Walters
<walters(a)verbum.org> wrote:
>
> Hi,
>
> On Tue, Apr 6, 2021, at 6:42 AM, Fabio Valentini wrote:
>> Hi everybody,
>>
>> It's that time of the year again, and this time there's not that many
>> downgrades to complain about (packages with "obvious" causes, like
>> F34FTBFS, already excluded from the list).
>>
>> However, the list also includes some pretty important "critpath"
>> packages (ostree (!), rpm-ostree, libuv, ...), which should probably
>> be fixed before F34 is released. Shipping with old ostree packages
>> OOTB seems like a bad idea, especially for the Editions that are built
>> on top of it.
>
> Hi, thanks for raising this. The two updates are
> https://bodhi.fedoraproject.org/updates/FEDORA-2021-33f693d20d
> https://bodhi.fedoraproject.org/updates/FEDORA-2021-971f672259
Thanks! It would probably be a good idea to request freeze exceptions
for them sooner rather than later, so testing of the candidate images
will be done with the new versions.
The following two bugs have been proposed as FE:
- https://bugzilla.redhat.com/show_bug.cgi?id=1946727
- https://bugzilla.redhat.com/show_bug.cgi?id=1946731
3:07 p.m.
New subject: Package downgrades from Fedora 33 -> Fedora 34 (including ostree
+ rpm-ostree)
On Tue, Apr 06, 2021 at 12:42:33PM +0200, Fabio Valentini wrote:
- virt-dib-1:1.44.1-1.fc33 > virt-dib-0:1.45.3-3.fc34
This subpackage seems to have been accidentally dropped from F34+ when
it was dropped for RHEL 9?
What happened here was part of libguestfs (Epoch 1) was split into a
separate upstream repo and Fedora package called guestfs-tools (Epoch 0).
I don't really want to use Epoch 1 for the whole of the new package.
I wonder if it will work to just put Epoch 1 into the virt-dib
subpackage? Let's see ...
We're not shipping virt-dib in RHEL 9.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
3:20 p.m.
New subject: Package downgrades from Fedora 33 -> Fedora 34 (including ostree
+ rpm-ostree)
On Wed, Apr 07, 2021 at 09:07:53PM +0100, Richard W.M. Jones wrote:
On Tue, Apr 06, 2021 at 12:42:33PM +0200, Fabio Valentini wrote:
> - virt-dib-1:1.44.1-1.fc33 > virt-dib-0:1.45.3-3.fc34
>
> This subpackage seems to have been accidentally dropped from F34+ when
> it was dropped for RHEL 9?
What happened here was part of libguestfs (Epoch 1) was split into a
separate upstream repo and Fedora package called guestfs-tools (Epoch 0).
I don't really want to use Epoch 1 for the whole of the new package.
I wonder if it will work to just put Epoch 1 into the virt-dib
subpackage? Let's see ...
So yes is the answer. I'll push the appropriate update soon.
Rich.
We're not shipping virt-dib in RHEL 9.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
12:33 p.m.
New subject: Package downgrades from Fedora 33 -> Fedora 34 (including ostree
+ rpm-ostree)
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.)
- 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.)
Fabio
---
- YafaRay-0:3.5.1-8.fc33 > YafaRay-0:3.5.1-7.fc34
- YafaRay-blender-0:3.5.1-8.fc33 > YafaRay-blender-0:3.5.1-7.fc34
- YafaRay-devel-0:3.5.1-8.fc33 > YafaRay-devel-0:3.5.1-7.fc34
- YafaRay-lib-0:3.5.1-8.fc33 > YafaRay-lib-0:3.5.1-7.fc34
YafaRay seems to have been updated on f33 but not on f34, or the
release bump was done to the "main" integer instead of appending .1
after dist if it was a stable-release-branch-only change.
I have unpushed the update that broke the upgrade path for YafaRay.
It had collected -2 negative karma already, and it bumped a SONAME in
F33 / stable.
- conky-0:1.12.1-1.fc33 > conky-0:1.11.6-2.fc34
Was successfully built for f34, but no bodhi update was submitted.
Created a bodhi update:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-90f942916f
- container-selinux-2:2.160.0-1.fc33 >
container-selinux-2:2.158.0-1.gite78ac4f.fc34
Bad rhcontainerbot (built for f34, but no update created).
Created a bodhi update:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-ac9daea36e
- cppad-devel-0:20210000.3-3.fc33 >
cppad-devel-0:20210000.3-2.fc34
- cppad-doc-0:20210000.3-3.fc33 > cppad-doc-0:20210000.3-2.fc34
Update was built for f34, but no bodhi update was created.
Created a bodhi update:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-5f179fa2c6
- python-scrapy-doc-0:2.4.1-1.fc33 >
python-scrapy-doc-0:1.5.1-10.fc34
- python3-scrapy-0:2.4.1-1.fc33 > python3-scrapy-0:1.5.1-10.fc34
The 2.4.1 update had been built for f34, but no bodhi updates has been
submitted.
Created a bodhi update:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-ee5190cbb0
- yoshimi-0:2.0-1.fc33 > yoshimi-0:1.7.4-2.fc34
yoshimi 2.0 was built for f34, but no bodhi update was created.
Created a bodhi update:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-4b3d6a519d
1:46 p.m.
New subject: Package downgrades from Fedora 33 -> Fedora 34 (including ostree
+ rpm-ostree)
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
4:12 a.m.
New subject: Package downgrades from Fedora 33 -> Fedora 34 (including ostree
+ rpm-ostree)
On 4/10/21 8:46 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Sat, Apr 10, 2021 at 07:33:42PM +0200, Fabio Valentini wrote:
> - 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
Go for it, I say! And thanks for doing all of this.
> - 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.
Agreed.
--
Kalev
5:54 a.m.
New subject: Package downgrades from Fedora 33 -> Fedora 34 (including ostree
+ rpm-ostree)
On Sun, Apr 11, 2021 at 11:12 AM Kalev Lember <kalevlember(a)gmail.com> wrote:
On 4/10/21 8:46 PM, Zbigniew Jędrzejewski-Szmek wrote:
> On Sat, Apr 10, 2021 at 07:33:42PM +0200, Fabio Valentini wrote:
>> - 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
Go for it, I say! And thanks for doing all of this.
>> - 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.
Agreed.
Great, less work for me. ;)
All cases where the missing build was an obvious oversight should be
fixed now, and the remaining issues should just be versioning mishaps
(e.g. bumped Release only on stable branch but not on F34 / Rawhide,
instead of appending .1 after %{?dist}).
Other than that, that leaves only a handful of package downgrades that
are caused by FTBFS issues on F34+.
I'll keep an eye on this, and re-run my checks after the current batch
of bodhi updates is pushed to the testing repos, but I think all "real
issues" should be fixed now (details below).
Fabio
---
- charliecloud-0:0.22-2.fc33 > charliecloud-0:0.21-2.fc34
Merged, built, and update submitted:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-0d811a26c1
- gecode-0:6.2.0-6.fc33 > gecode-0:6.2.0-5.fc34
Bumped release and rebuilt on f35 and f34 to account for koji snafu at
f34 branch point:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-c7bafa26a5
https://bodhi.fedoraproject.org/updates/FEDORA-2021-ea8f4e12af
- klog-0:1.4.7-2.fc33 > klog-0:1.4.4-3.fc34
All dist-git branches had up-to-date commits, but update was only
built for F33 and F32.
So ... built, and update submitted F34:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-5677441800
- libreswan-0:4.3-1.fc33 > libreswan-0:4.2-1.fc34
Merged, built, and update submitted:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-51852f56bd
- mingw32-libusbx-0:1.0.24-1.fc33 > mingw32-libusbx-0:1.0.22-7.fc34
- mingw32-libusbx-static-0:1.0.24-1.fc33 >
mingw32-libusbx-static-0:1.0.22-7.fc34
- mingw64-libusbx-0:1.0.24-1.fc33 > mingw64-libusbx-0:1.0.22-7.fc34
- mingw64-libusbx-static-0:1.0.24-1.fc33 >
mingw64-libusbx-static-0:1.0.22-7.fc34
Merged, built, and update submitted:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-cd89a72b72
- nagios-plugins-nrpe-0:4.0.3-6.fc33 > nagios-plugins-nrpe-0:4.0.3-3.fc34
- nrpe-0:4.0.3-6.fc33 > nrpe-0:4.0.3-3.fc34
Merged, built, and update submitted:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-32c0a7f123
- nsd-0:4.3.5-1.fc33 > nsd-0:4.3.2-3.fc34
Merged, built, and update submitted:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-33fcb048ee
- python3-pyunicorn-0:0.6.1-2.fc33 > python3-pyunicorn-0:0.6.1-1.fc34
Merged, built, and update submitted:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-fcfaba6d79
- ydotool-0:0.2.0-5.fc33 > ydotool-0:0.2.0-4.fc34
Merged, built, and update submitted:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-857257f9aa
12:08 a.m.
New subject: Package downgrades from Fedora 33 -> Fedora 34 (including ostree
+ rpm-ostree)
Dne 10. 04. 21 v 19:33 Fabio Valentini napsal(a):
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).
We should advertise bodhi activation point more aggressively. I filed
https://github.com/fedora-infra/bodhi/issues/4207
Miroslav
1106
days inactive
1115
days old
15 comments
9 participants
participants (9)
-
Ankur Sinha -
Colin Walters -
Dusty Mabe -
Fabio Valentini -
Kalev Lember -
Matthew Miller -
Miroslav Suchý -
Richard W.M. Jones -
Zbigniew Jędrzejewski-Szmek