Package downgrades from f32 -> f33 (categorized list inside)

[Fabio Valentini]

Following up on the recent discussion, I've checked repository
contents of f32 and f33 for downgrades and categorized them. I also
dropped packages with F33FTBFS issues from the list since for these
the reason for the downgrade is already documented as a bug.

# Koji tagging / compose issues?

(builds are either missing from the f33 tag for no reason or are tagged with
f33 but not included in composes)

- distgen is newer in 32 than in 33:
  0:1.6-1.fc32 > 0:1.5-3.fc33
- enchant2 is newer in 32 than in 33:
  0:2.2.9-1.fc32 > 0:2.2.8-2.fc33
- libdkimpp is newer in 32 than in 33:
  0:2.0.0-6.fc32 > 0:2.0.0-3.fc32
- swift-lang is newer in 32 than in 33:
  0:5.2.5-1.fc32 > 0:5.2.4-3.fc33

# Built for f34 (and f32) but not f33:

(packages were updated but package maintainer seems to have missed the f33
branch point and has not submitted updates for f33)

- ck is newer in 32 than in 33:
  0:0.7.0-3.fc32 > 0:0.6.0-10.fc32
- cockpit-podman is newer in 32 than in 33:
  0:22-1.fc32 > 0:21-1.fc33
- fdupes is newer in 32 than in 33:
  1:2.1.1-1.fc32 > 1:2.1.0-2.fc33
- golang-github-willf-bitset is newer in 32 than in 33:
  0:1.1.11-1.fc32 > 0:1.1.10-5.fc33
- libmediainfo is newer in 32 than in 33:
  0:20.08-1.fc32 > 0:20.03-3.fc33
- mediainfo is newer in 32 than in 33:
  0:20.08-1.fc32 > 0:20.03-3.fc33
- ncmpc is newer in 32 than in 33:
  0:0.39-1.fc32 > 0:0.38-2.fc33
- procps-ng is newer in 32 than in 33:
  0:3.3.16-1.fc32 > 0:3.3.15-9.fc33
- python-ogr is newer in 32 than in 33:
  0:0.13.1-1.fc32 > 0:0.13.0-1.fc33
- rpm-ostree is newer in 32 than in 33:
  0:2020.4-1.fc32 > 0:2020.3-1.fc33
- yoshimi is newer in 32 than in 33:
  0:1.7.2-1.fc32 > 0:1.7.1-2.fc33

# Missing only bodhi updates:

(packages were updated for f33 after beta freeze but no bodhi updates were
submitted)

- blender is newer in 32 than in 33:
  1:2.83.1-1.fc32 > 1:2.82a-5.fc33
- fuse-overlayfs is newer in 32 than in 33:
  0:1.1.2-1.fc32 > 0:1.1.0-11.dev.git800011b.fc33
- relval is newer in 32 than in 33:
  0:2.5.1-1.fc32 > 0:2.5.0-3.fc33
- skopeo is newer in 32 than in 33:
  1:1.1.1-1.fc32 > 1:1.0.1-16.dev.git091f924.fc33

# Package downgrades (not updated in master / f33):

(packages were only updated in stable branches, but never in master or f33)

- appstream-data is newer in 32 than in 33:
  0:32-8.fc32 > 0:32-7.fc33
- buildah is newer in 32 than in 33:
  0:1.15.1-1.fc32 > 0:1.15.0-0.68.dev.git2c46b4b.fc33
- containers-common is newer in 32 than in 33:
  1:1.1.1-1.fc32 > 1:1.0.1-16.dev.git091f924.fc33
- fedmsg is newer in 32 than in 33:
  0:1.1.2-1.fc32 > 0:1.1.1-11.fc33
- gnome-remote-desktop is newer in 32 than in 33:
  0:0.1.8-2.fc32 > 0:0.1.7-5.fc33
- gnome-shell-extension-material-shell is newer in 32 than in 33:
  0:3-2.fc32 > 0:3-1.fc33
- python-certbot-dns-google is newer in 32 than in 33:
  0:1.7.0-1.fc32 > 0:1.5.0-1.fc33
- python3-operator-courier is newer in 32 than in 33:
  0:2.1.9-3.fc32 > 0:2.1.9-2.fc33

# Weird Release tag screws up rpmdev-bumpspec:

(rpmdev-bumpspec screwed up the upgrade path due to mass rebuild commit)

- radare2 is newer in 32 than in 33:
  0:4.5.0-2.fc32 > 0:4.5.0-1.fc33.1

# Packages not included in mass rebuild?

- tmt is newer in 32 than in 33:
  0:0.20-1.fc32 > 0:0.19-1.fc33

# Uh, WTF?

(no idea what went wrong here)

- python3-magic is newer in 32 than in 33:
  0:5.38-2.fc32 > 0:0.4.15-4.fc33
- texlive-arphic is newer in 32 than in 33:
  9:svn15878.0-21.fc32 > 9:svn15878-27.fc33
- texlive-babel-malay-doc is newer in 32 than in 33:
  9:svn43235-21.fc32 > 9:svn43234-27.fc33
- texlive-tudscr is newer in 32 than in 33:
  9:svn51675-21.fc32 > 9:LPPL-27.fc33

If you see one of your packages on this list, please remedy the
downgrade / upgrade path issue accordingly, if possible. We don't want
f33 to have older software than f32 :)

Fabio

[Miro Hrončok]

On 26. 08. 20 12:18, Fabio Valentini wrote:
>  - python3-magic is newer in 32 than in 33:
>     0:5.38-2.fc32 > 0:0.4.15-4.fc33 
python3-magic from Fedora 32 is obsoleted by python3-file-magic

python3-magic from Fedora 33 is a different project, no direct upgrade path.

-- 
Miro Hrončok
--
Phone: [phone]
IRC: mhroncok

[Richard Shaw]

On Wed, Aug 26, 2020 at 5:19 AM Fabio Valentini <decathorpe(a)gmail.com&gt;
wrote:

>  # Built for f34 (and f32) but not f33:
>
>  (packages were updated but package maintainer seems to have missed the f33
>  branch point and has not submitted updates for f33)
>
>  - fdupes is newer in 32 than in 33:
>    1:2.1.1-1.fc32 > 1:2.1.0-2.fc33
>  
Taking care of this now.

Thanks,
Richard

[Petr Šplíchal]

Hi!

>  # Packages not included in mass rebuild?
>
>  - tmt is newer in 32 than in 33:
>    0:0.20-1.fc32 > 0:0.19-1.fc33 
Recently I was unable to build a fresh tmt package for rawhide
because of a missing build dependency:

    https://koji.fedoraproject.org/koji/taskinfo?taskID=48098490
    https://koji.fedoraproject.org/koji/taskinfo?taskID=50191342

    Problem: conflicting requests
    - nothing provides libguestfs-tools-c needed by
python3-testcloud-0.3.5-3.fc33.noarch

Seems the problem happens only for some build host architectures
(although tmt is noarch). Today I was able to build the package
successfully (on another build host). Any recommendation on how
to prevent these random failures? Thanks.

psss...

[Miro Hrončok]

On 26. 08. 20 17:45, Petr Šplíchal wrote:
>  Hi!
>  
> > # Packages not included in mass rebuild?
> >
> > - tmt is newer in 32 than in 33:
> >    0:0.20-1.fc32 > 0:0.19-1.fc33
>  Recently I was unable to build a fresh tmt package for rawhide
>  because of a missing build dependency:
>  
>       https://koji.fedoraproject.org/koji/taskinfo?taskID=48098490
>       https://koji.fedoraproject.org/koji/taskinfo?taskID=50191342
>  
>       Problem: conflicting requests
>       - nothing provides libguestfs-tools-c needed by
>  python3-testcloud-0.3.5-3.fc33.noarch
>  
>  Seems the problem happens only for some build host architectures
>  (although tmt is noarch). Today I was able to build the package
>  successfully (on another build host). Any recommendation on how
>  to prevent these random failures? Thanks. 
Do this:

https://src.fedoraproject.org/rpms/pungi/pull-request/4

In testcloud. If at all possible.

If not possible, then testcloud needs to exclude i686 and so does tmt.

-- 
Miro Hrončok
--
Phone: [phone]
IRC: mhroncok

[kevin]

On Wed, Aug 26, 2020 at 05:45:24PM +0200, Petr Šplíchal wrote:
>  Hi!
>  
>  > # Packages not included in mass rebuild?
>  >
>  > - tmt is newer in 32 than in 33:
>  >   0:0.20-1.fc32 > 0:0.19-1.fc33
>  
>  Recently I was unable to build a fresh tmt package for rawhide
>  because of a missing build dependency:
>  
>      https://koji.fedoraproject.org/koji/taskinfo?taskID=48098490
>      https://koji.fedoraproject.org/koji/taskinfo?taskID=50191342
>  
>      Problem: conflicting requests
>      - nothing provides libguestfs-tools-c needed by
>  python3-testcloud-0.3.5-3.fc33.noarch
>  
>  Seems the problem happens only for some build host architectures
>  (although tmt is noarch). Today I was able to build the package
>  successfully (on another build host). Any recommendation on how
>  to prevent these random failures? Thanks. 
This is because we no longer build a i686 kernel, and libguestfs needs a
kernel. So, it will not be available on i686. 

You should be able to: 

ExclusiveArch: %{kernel_arches} noarch

and I think koji will now do the right thing. 

kevin