Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1880768 - libxml2 in F33 has lower version than in F32, breaks upgrade to F33
Summary: libxml2 in F33 has lower version than in F32, breaks upgrade to F33
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libxml2
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Igor Raits
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F33BetaFreezeException
TreeView+ depends on / blocked
 
Reported: 2020-09-19 20:18 UTC by Zbigniew Jędrzejewski-Szmek
Modified: 2020-09-25 16:55 UTC (History)
5 users (show)

Fixed In Version: libxml2-2.9.10-7.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-21 13:09:49 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Zbigniew Jędrzejewski-Szmek 2020-09-19 20:18:06 UTC 
Description of problem:
Release	Stable version	Version in testing
Fedora 34	libxml2-2.9.10-7.fc34	
Fedora 33	libxml2-2.9.10-4.fc33	libxml2-2.9.10-7.fc33
Fedora 32	libxml2-2.9.10-7.fc32

Enabling updates-testing fixes the upgrade.
Comment 1 Fedora Blocker Bugs Application 2020-09-19 20:19:36 UTC 
Proposed as a Freeze Exception for 33-beta by Fedora user zbyszek using the blocker tracking app because:

 Lower version of the package in F33 breaks upgrade from F32.
Comment 2 Fedora Update System 2020-09-20 11:24:10 UTC 
FEDORA-2020-dd2fc19b78 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-dd2fc19b78
Comment 3 Kamil Páral 2020-09-21 10:25:41 UTC 
Zbyszek, what exactly gets broken? The upgrade process uses the distrosync approach, so a lower version in F33 shouldn't actually matter too much. Does the upgrade not proceed?
Comment 4 Zbigniew Jędrzejewski-Szmek 2020-09-21 12:03:02 UTC 
Yes, I expected 'dnf upgrade --releasever' to work.

In the past we certainly had the rule that packages in Fn+1 were supposed to sort higher than those in Fn.
But I'm not sure if that is still the case. Packaging guidelines don't say that directly, even though they
list some allowed exceptions, so it implies that the rule is still valid
(https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_you_need_to_change_an_old_branch_without_rebuilding_the_others,
https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_rawhide_is_allowed_to_lag_temporarily).
I think this should be prominently clarified in the guidelines.

That said, it seems wrong to have a lower version in Fn+1. The version in Fn clearly has some additional fixes,
and other packages may rely on them. The new version is already built and tested, so it's just a matter of
pushing it to stable.
Comment 5 Kamil Páral 2020-09-21 12:58:04 UTC 
That requirement has been scratched when dnf switched to using distrosync instead of update. I'm quite sure about it, because we also dropped the upgradepath Taskotron check when that happened: https://pagure.io/taskotron/issue/244 . I'm not sure if I can find a better ticket about it, though, and it should definitely be better documented.

> The new version is already built and tested, so it's just a matter of pushing it to stable.

Yes, but it also defeats the idea of a freeze, where we allow only bugfixes and highly important updates through. A potential improvement here would be to automatically enable updates-testing *if and only if* the target release has updates-testing enabled by default. That would require some non-trivial patching, though.
Comment 6 Zbigniew Jędrzejewski-Szmek 2020-09-21 13:09:49 UTC 
OK, let's close this then.
Comment 7 Fedora Update System 2020-09-25 16:55:12 UTC 
FEDORA-2020-dd2fc19b78 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.