#6638 lower version from f26-rebuild has been tagged into f26
Closed: Fixed 7 years ago Opened 7 years ago by ignatenkobrain.

Long story short: during mass rebuild, we built dnf-plugins-core to 1.0.1 in f26, but after mass rebuild during merge 1.0.0 has been tagged into f26 even newer version was there. Which resulted into downgrade of package in koji (not sure about compose itself).

I think this would be case for some unknown number of packages.


[brain@ignatenko-w541 dnf-plugins-core]$ koji list-history --build=dnf-plugins-core-1.0.0-0.rc1.2.fc26.1
Fri Feb 10 15:30:08 2017 dnf-plugins-core-1.0.0-0.rc1.2.fc26.1 tagged into f26-rebuild by releng [still active]
Tue Feb 14 16:58:08 2017 dnf-plugins-core-1.0.0-0.rc1.2.fc26.1 tagged into f26-pending by mohanboddu
Tue Feb 14 18:43:35 2017 dnf-plugins-core-1.0.0-0.rc1.2.fc26.1 untagged from f26-pending by autopen
Tue Feb 14 18:43:35 2017 dnf-plugins-core-1.0.0-0.rc1.2.fc26.1 tagged into f26 by autopen [still active]
[brain@ignatenko-w541 dnf-plugins-core]$ koji list-history --build=dnf-plugins-core-1.0.1-1.fc26
Fri Feb 10 10:58:52 2017 dnf-plugins-core-1.0.1-1.fc26 tagged into f26-pending by jmracek
Fri Feb 10 10:59:02 2017 dnf-plugins-core-1.0.1-1.fc26 untagged from f26-pending by autopen
Fri Feb 10 10:59:02 2017 dnf-plugins-core-1.0.1-1.fc26 tagged into f26 by autopen [still active]

I suspect that multiple packages are affected by this...

It got into the rawhide compose. Just search for downgraded packages in the report.

Here's the list:

Package: dnf-plugins-core-1.0.0-0.rc1.2.fc26.1
Old package: dnf-plugins-core-1.0.1-1.fc26

Package: fleet-commander-admin-0.7.3-3.fc26
Old package: fleet-commander-admin-0.8.0-1.fc26

Package: gimagereader-3.2.0-3.fc26
Old package: gimagereader-3.2.1-1.fc26

Package: python-cerberus-1.0.1-3.fc26
Old package: python-cerberus-1.1-1.fc26

Package: python-colander-1.3.1-4.fc26
Old package: python-colander-1.3.2-1.fc26

Package: python-maps-4.0.0-2.fc26
Old package: python-maps-4.2.0-1.fc26

all except 2 are mine :joy:

Releng git repo has a script for detecting exactly this, check-latest-build.py. Here's its output when I ran it (it took about an hour to run):

$ ./check-latest-build.py f26
dnf-plugins-core-1.0.0-0.rc1.2.fc26.1 < dnf-plugins-core-1.0.1-1.fc26
flatpak-0.8.3-1.fc26 < flatpak-0.8.3-2.fc26
fleet-commander-admin-0.7.3-3.fc26 < fleet-commander-admin-0.8.0-1.fc26
gimagereader-3.2.0-3.fc26 < gimagereader-3.2.1-1.fc26
iio-sensor-proxy-2.1-2.fc26 < iio-sensor-proxy-2.2-1.fc26
jetty-schemas-3.1-2.fc26 < jetty-schemas-3.1-7.fc25
kdepim-16.12.2-1.fc26 < kdepim-16.12.2-2.fc26
krdc-16.12.2-1.fc26 < krdc-16.12.2-2.fc26
krfb-16.12.2-1.fc26 < krfb-16.12.2-2.fc26
lcd4linux-0.11-0.14.svn1200.fc26 < lcd4linux-0.11-0.15.svn1200.fc26
module-build-service-1.1.1-3.fc26 < module-build-service-1.2.0-1.fc26
os-apply-config-5.0.0-2.fc26 < os-apply-config-5.0.0.0b2-1.fc26
perl-Net-CalDAVTalk-0.09-2.fc26 < perl-Net-CalDAVTalk-0.10-1.fc26
perl-Net-CardDAVTalk-0.03-2.fc26 < perl-Net-CardDAVTalk-0.05-1.fc26
perl-ORLite-1.98-10.fc25 < perl-ORLite-1.98-12.fc26
php-zendframework-zend-servicemanager-3.2.0-2.fc26 < php-zendframework-zend-servicemanager-3.2.1-1.fc26
policycoreutils-2.5-21.fc26 < policycoreutils-2.5-22.fc26
python-cerberus-1.0.1-3.fc26 < python-cerberus-1.1-1.fc26
python-colander-1.3.1-4.fc26 < python-colander-1.3.2-1.fc26
python-fuckit-4.8.0-8.fc26 < python-fuckit-4.8.0-9.fc26
python-maps-4.0.0-2.fc26 < python-maps-4.2.0-1.fc26
python-oslo-versionedobjects-1.8.0-1.fc26 < python-oslo-versionedobjects-1.17.0-1.fc26
python-piexif-1.0.10-2.fc26 < python-piexif-1.0.12-1.fc26
python-pillow-4.0.0-2.fc26 < python-pillow-4.0.0-3.fc26
python-sanic-0.2.0-2.fc26 < python-sanic-0.3.1-1.fc26
python-tqdm-4.11.1-2.fc26 < python-tqdm-4.11.2-1.fc26
python-units-0.06-4.fc26 < python-units-0.07-1.fc26
python-uvloop-0.7.2-2.fc26 < python-uvloop-0.8.0-1.fc26
python-winrm-0.2.2-2.fc26 < python-winrm-0.2.2-3.fc26
qlandkartegt-1.8.1-8.fc24 < qlandkartegt-1.8.1-10.fc26
qmapshack-1.7.2-1.fc26 < qmapshack-1.7.2-3.fc26
qt-virt-manager-0.39.60-3.fc26 < qt-virt-manager-0.39.60-4.fc26
quake2-5.34-6.fc26 < quake2-6.00-9.fc26
remmina-1.2.0-0.29.20161226gitd1a4a73.fc26 < remmina-1.2.0-0.30.20161226gitd1a4a73.fc26
rolekit-0.5.1-3.fc26 < rolekit-0.5.1-4.fc26
speedtest-cli-0.3.2-7.fc26 < speedtest-cli-0.3.2-8.fc26
suricata-3.2-1.fc26 < suricata-3.2.1-1.fc26
x11vnc-0.9.14-3.fc26 < x11vnc-0.9.14-4.fc26
xrootd-4.6.0-2.fc26 < xrootd-4.6.0-3.fc26

Thanks @kalev!

Does anybody from releng is going to fix this?

the mass-tag script and all of how koji works, has no concept of nvr. the dnf-plugins-core build done by the mass rebuild was started after the build done by jmracek so in the way that koji works, the mass rebuild build was newer. because the mass rebuild build was a lower nvr it could just be untagged. and the latest build would have a higher nvr ensuring that the upgrade path works

Metadata Update from @ausil:
- Issue assigned to mohanboddu

7 years ago

Untagged the builds for f26 tag:

$ koji untag-build f26 dnf-plugins-core-1.0.0-0.rc1.2.fc26.1 flatpak-0.8.3-1.fc26 fleet-commander-admin-0.7.3-3.fc26 gimagereader-3.2.0-3.fc26 iio-sensor-proxy-2.1-2.fc26 jetty-schemas-3.1-2.fc26 kdepim-16.12.2-1.fc26 krdc-16.12.2-1.fc26 krfb-16.12.2-1.fc26 lcd4linux-0.11-0.14.svn1200.fc26 module-build-service-1.1.1-3.fc26 os-apply-config-5.0.0-2.fc26 perl-Net-CalDAVTalk-0.09-2.fc26 perl-Net-CardDAVTalk-0.03-2.fc26 perl-ORLite-1.98-10.fc25 php-zendframework-zend-servicemanager-3.2.0-2.fc26 policycoreutils-2.5-21.fc26 python-cerberus-1.0.1-3.fc26 python-colander-1.3.1-4.fc26 python-fuckit-4.8.0-8.fc26 python-maps-4.0.0-2.fc26 python-oslo-versionedobjects-1.8.0-1.fc26 python-piexif-1.0.10-2.fc26 python-pillow-4.0.0-2.fc26 python-sanic-0.2.0-2.fc26 python-tqdm-4.11.1-2.fc26 python-units-0.06-4.fc26 python-uvloop-0.7.2-2.fc26 python-winrm-0.2.2-2.fc26 qlandkartegt-1.8.1-8.fc24 qmapshack-1.7.2-1.fc26 qt-virt-manager-0.39.60-3.fc26 quake2-5.34-6.fc26 rolekit-0.5.1-3.fc26 speedtest-cli-0.3.2-7.fc26 suricata-3.2-1.fc26 x11vnc-0.9.14-3.fc26 xrootd-4.6.0-2.fc26 remmina-1.2.0-0.29.20161226gitd1a4a73.fc26 --force

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

7 years ago

Login to comment on this ticket.

Metadata