#9262 F-32 updates-testing contains f-33 content
Closed: Fixed 4 years ago by kevin. Opened 4 years ago by pbrobinson.

There's Fedora 33 content in updates-testing.

 pcre                                                        aarch64                                8.44-1.fc33                                               updates-testing                                181 k
 python-unversioned-command                                  noarch                                 3.8.2~rc1-1.fc33                                          updates-testing                                 14 k
 python3                                                     aarch64                                3.8.2~rc1-1.fc33                                          updates-testing                                 30 k
 python3-dbus                                                aarch64                                1.2.16-1.fc33                                             updates-testing                                133 k
 python3-libs                                                aarch64                                3.8.2~rc1-1.fc33                                          updates-testing                                7.4 M
 python3-pyparted                                            aarch64                                1:3.11.4-1.fc32                                           updates-testing                                105 k
 sed                                                         aarch64                                4.8-1.fc33                                                updates-testing                                301 k
 

This might be easier to read, it's just a sample.


pcre aarch64 8.44-1.fc33 updates-testing 181 k
python-unversioned-command noarch 3.8.2~rc1-1.fc33 updates-testing 14 k
python3 aarch64 3.8.2~rc1-1.fc33 updates-testing 30 k
python3-dbus aarch64 1.2.16-1.fc33 updates-testing 133 k
python3-libs aarch64 3.8.2~rc1-1.fc33 updates-testing 7.4 M
python3-pyparted aarch64 1:3.11.4-1.fc32 updates-testing 105 k
sed aarch64 4.8-1.fc33 updates-testing 301 k

Add it seems some f32 content is in a f33-updates-testing-pending tag. They might have been ones that should have been tagged to both f32/f33

koji list-tagged f33-updates-testing-pending
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
asterisk-17.2.0-1.fc32                    f33-updates-testing-pending  jsmith
bitlbee-discord-0.4.2-5.20200211git69e16be.fc32  f33-updates-testing-pending  tc01
golang-x-crypto-0-0.34.20200211git86ce3cb.fc32  f33-updates-testing-pending  eclipseo
kf5-kirigami2-5.67.1-1.fc32               f33-updates-testing-pending  rdieter
nextpnr-0-0.10.20200129git85f4452.fc32    f33-updates-testing-pending  somlo
palp-2.1-15.fc32                          f33-updates-testing-pending  jjames
perl-CGI-Simple-1.25-1.fc32               f33-updates-testing-pending  spot
perl-Mail-Message-3.009-1.fc32            f33-updates-testing-pending  spot
planarity-3.0.0.5-6.fc32                  f33-updates-testing-pending  jjames
python-construct-2.10.56-1.fc32           f33-updates-testing-pending  terjeros
python-mutagen-1.44.0-1.fc32              f33-updates-testing-pending  mbaldessari
qqc2-desktop-style-5.67.1-1.fc32          f33-updates-testing-pending  rdieter
qutebrowser-1.10.0-1.fc33                 f33-updates-testing-pending  fnux
rancid-3.11-1.fc32                        f33-updates-testing-pending  cra
rust-proptest-0.9.5-3.fc32                f33-updates-testing-pending  jistone
sugar-maze-29-2.fc32                      f33-updates-testing-pending  pbrobinson

This is very likely due to mirrormanager pointing fedora-32 to rawhide. :)

There are not actually any fc33 rpms in the f32 repos, it's just mirrormanager. I've opened an infra ticket to fix it.

Those ones in f33-updates-testing-pending seem to be stuck from branching. I'll try and unstick them.

https://pagure.io/fedora-infrastructure/issue/8653 is the mirrormanager ticket.

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

4 years ago

Login to comment on this ticket.

Metadata