#11101 f38-rebuild merging into f38 overrode higher EVR pkgs already built (from side tag)
Closed: Fixed a year ago by mtasaka. Opened a year ago by mtasaka.

[tasaka1@localhost ~]$ koji latest-pkg f38-build rubygem-glib2
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
rubygem-glib2-4.0.5-2.fc38                f38                   releng
[tasaka1@localhost ~]$ koji list-history --build rubygem-glib2-4.0.5-2.fc38
Sat Jan 21 06:50:34 2023 rubygem-glib2-4.0.5-2.fc38 tagged into f38-rebuild by releng [still active]
Tue Jan 24 01:27:06 2023 rubygem-glib2-4.0.5-2.fc38 tagged into f38 by humaton [still active]

This is broken. Actually there is rubygem-glib2-4.0.8-1.fc38:

Sun Jan 22 15:03:26 2023 rubygem-glib2-4.0.8-1.fc38 tagged into f38-build-side-62158 by mtasaka
Sun Jan 22 18:30:16 2023 rubygem-glib2-4.0.8-1.fc38 tagged into f38-build-side-62158-signing-pending by bodhi
Sun Jan 22 18:31:53 2023 rubygem-glib2-4.0.8-1.fc38 untagged from f38-build-side-62158-signing-pending by autopen
Sun Jan 22 18:31:53 2023 rubygem-glib2-4.0.8-1.fc38 tagged into f38-build-side-62158-testing-pending by autopen
Sun Jan 22 18:34:07 2023 rubygem-glib2-4.0.8-1.fc38 untagged from f38-build-side-62158-testing-pending by bodhi
Sun Jan 22 18:34:10 2023 rubygem-glib2-4.0.8-1.fc38 untagged from f38-build-side-62158 by bodhi
Sun Jan 22 18:34:44 2023 rubygem-glib2-4.0.8-1.fc38 tagged into f38 by bodhi [still active]

As the result, now I see this broken deps report:
https://bugzilla.redhat.com/show_bug.cgi?id=2164004


I guess the reason only rubygem-cairo-gobject-4.0.8-2.fc38 is correctly into f38 buildroot is that I built rubygem-cairo-gobject-4.0.8-1.fc38 directly into f38-build instead of f38-build-side-62158 (by mistake), which I guess prevented f38-rebuild tag rubygem-cairo-gobject-4.0.5-2.fc38 from being merged into f38. And anyway I built rubygem-cairo-gobject-4.0.8-2.fc38, this time into f38-build-side-62158, which was merged into f38 through bodhi side-tag merge.

I fixed the following this morning:

 c4core-0.1.11-4.fc38                                                   
 calendar-1.37-7.20211220cvs.fc37
 cyrus-imapd-3.6.0-3.fc38
 epiphany-44~alpha-3.fc38
 fast_float-3.9.0-1.fc38
 festival-2.5.0-17.fc36                          
 freeipa-4.10.1-3.fc38               
 gnome-builder-43.4-6.fc38
 golang-github-armon-circbuf-0-0.2
 golang-github-docker-libtrust-0
 golang-github-zmap-zcrypto-0-14.20
 golang-modernc-mathutil-1.4.1-6.fc38
 golang-x-crypto-0-20.20220412git7b82a4e.fc37
 golang-x-image-0-0.26.20201223git35266b9.fc37
 grass-8.2.1-1.fc38
 intel-ipsec-mb-1.3.0-3.fc38
 iotop-c-1.23-1.fc38
 klamav-0.46-41.fc38
 libldb-2.7.0-2.fc38
 libtdb-1.4.8-1.fc38
 libtevent-0.14.0-1.fc38
 mapnik-3.1.0-24.fc38 
 ocspd-1.9.0-26.fc38
 python-azure-mgmt-synapse-2.1.0b2-5.fc37
 python-cerberus-1.3.3-1.fc38
 python-cerberus-1.3.4-1.fc38
 python-hpack-4.0.0-7.fc37
 radsecproxy-1.9.2-1.fc38
 rubygem-atk-4.0.8-2.fc38
 rubygem-clutter-4.0.8-1.fc38
 rubygem-clutter-gdk-4.0.8-1.fc38
 rubygem-clutter-gstreamer-4.0.8-1.fc38
 rubygem-clutter-gtk-4.0.8-1.fc38
 rubygem-gdk3-4.0.8-1.fc38
 rubygem-gdk4-4.0.8-2.fc38
 rubygem-gdk_pixbuf2-4.0.8-1.fc38
 rubygem-gio2-4.0.8-1.fc38
 rubygem-glib2-4.0.8-1.fc38
 rubygem-gobject-introspection-4.0.8-1.fc38
 rubygem-gstreamer-4.0.8-1.fc38
 rubygem-gtk3-4.0.8-1.fc38
 rubygem-gtksourceview3-4.0.8-1.fc38
 rubygem-pango-4.0.8-1.fc38
 rubygem-poppler-4.0.8-1.fc38
 rubygem-rsvg2-4.0.8-1.fc38
 rubygem-vte3-4.0.8-1.fc38
 rubygem-webkit2-gtk-4.0.8-1.fc38
 rust-fd-find-8.2.1-10.fc38
 rust-lscolors-0.13.0-1.fc38
 rust-lsd-0.22.0-3.fc38
 tex-cjw-20090907-9.fc36
 yara-4.3.0-0.rc1.3.fc38

Does that address this?

Metadata Update from @phsmoura:
- Issue tagged with: low-trouble, medium-gain, ops

a year ago

Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

a year ago

Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Reporter (was: Waiting on Assignee)

a year ago

Perhaps good, however now I am waiting for https://bugzilla.redhat.com/show_bug.cgi?id=2164004 to be closed for conformation: the bug reports should be closed today or tomorrow automatically when dependency is resolved.

Ok, now the above bug is closed, so this is confirmed fixed. Thank you.

Metadata Update from @mtasaka:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog