Bug 1869324 - Can't upgrade from F32 to F33
Summary: Can't upgrade from F32 to F33
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-obsolete-packages
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miro Hrončok
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-17 14:00 UTC by Artem
Modified: 2020-08-20 15:27 UTC (History)
13 users (show)

Fixed In Version: fedora-obsolete-packages-33-22
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-20 15:27:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Artem 2020-08-17 14:00:56 UTC
Description of problem:
At this moment not possible to simply update from F32 to F33.


Version-Release number of selected component (if applicable):
epiphany-3.36.3-1.fc32


How reproducible:
sudo dnf system-upgrade download --refresh --releasever=33 --enablerepo=\*ing --rpmverbosity=debug -v


Actual results:
Error: Transaction test error:
  file /usr/bin/epiphany from install of epiphany-1:3.37.2-2.fc33.x86_64 conflicts with file from package epiphany-runtime-1:3.36.3-1.fc32.x86_64
  file /usr/lib64/epiphany/libephymain.so from install of epiphany-1:3.37.2-2.fc33.x86_64 conflicts with file from package epiphany-runtime-1:3.36.3-1.fc32.x86_64
  file /usr/lib64/epiphany/libephymisc.so from install of epiphany-1:3.37.2-2.fc33.x86_64 conflicts with file from package epiphany-runtime-1:3.36.3-1.fc32.x86_64
  file /usr/lib64/epiphany/libephysync.so from install of epiphany-1:3.37.2-2.fc33.x86_64 conflicts with file from package epiphany-runtime-1:3.36.3-1.fc32.x86_64
  file /usr/lib64/epiphany/web-process-extensions/libephywebprocessextension.so from install of epiphany-1:3.37.2-2.fc33.x86_64 conflicts with file from package epiphany-runtime-1:3.36.3-1.fc32.x86_64
  file /usr/libexec/epiphany/ephy-profile-migrator from install of epiphany-1:3.37.2-2.fc33.x86_64 conflicts with file from package epiphany-runtime-1:3.36.3-1.fc32.x86_64
  file /usr/share/glib-2.0/schemas/org.gnome.epiphany.gschema.xml from install of epiphany-1:3.37.2-2.fc33.x86_64 conflicts with file from package epiphany-runtime-1:3.36.3-1.fc32.x86_64


Expected results:
Successful upgrade for user without any hassle.

Comment 1 Michael Catanzaro 2020-08-17 14:41:13 UTC
I think this is a bug in how we Obsoletes packages from fedora-obsolete-packages. Our policy is:

# All Obsoletes: entries MUST be versioned (including the release), with the
# version being the same as or just higher than the last version-release of the
# obsoleted package.  This allows the package to return to the distribution
# later.  The best possible thing to do is to find the last version-release
# which was in the distribution, add one to the release, and add that version
# without using a dist tag.  This allows a rebuild with a bumped Release: to be
# installed.

So following that policy, fedora-obsolete-packages has:

# Remove in F35
%obsolete_ticket https://bugzilla.redhat.com/show_bug.cgi?id=1781359
%obsolete epiphany-runtime 1:3.36.0-2

But this has failed because Epiphany of course still gets updated in Fedora 32 and is now at version 1:3.36.3-1. It's going to keep getting updated indefinitely to higher 3.36 versions. To keep it obsoleted for good, we would have to set this to at least 1:3.37.0-0. That's not what the guidance says to do, but surely it's the right thing to do here because if we set it to one release after the last build, it will break next time we update F32 again. (There's even a new update pending already, 3.36.4.)

Comment 2 Miro Hrončok 2020-08-17 19:06:21 UTC
We can surely obsolete something like 1:3.36.99 and bump the epoch if it ever gets reintroduced.

Comment 3 Michael Catanzaro 2020-08-17 19:29:50 UTC
1:3.36.99 will be fine.

Epiphany in rawhide is already 3.37 so no need to worry about epoch.

Comment 4 Miro Hrončok 2020-08-20 11:57:52 UTC
Pushed, but Koji cannot build now.


Note You need to log in before you can comment on or make changes to this bug.