Bug 1047058 - Please make fedora-release more compatible with respect to yum changes related to releasever
Summary: Please make fedora-release more compatible with respect to yum changes relate...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-release
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dennis Gilmore
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-28 18:53 UTC by Bruno Wolff III
Modified: 2014-02-26 13:55 UTC (History)
2 users (show)

Fixed In Version: fedora-release-19-8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-23 08:36:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
patch for rawhide (533 bytes, patch)
2013-12-28 18:53 UTC, Bruno Wolff III
no flags Details | Diff
patch for f20 (519 bytes, patch)
2013-12-28 18:55 UTC, Bruno Wolff III
no flags Details | Diff
Patch for f19 (524 bytes, patch)
2013-12-28 18:56 UTC, Bruno Wolff III
no flags Details | Diff

Description Bruno Wolff III 2013-12-28 18:53:55 UTC
Created attachment 842731 [details]
patch for rawhide

Description of problem:
Recently yum made two changes which primarily impacted people using generic-release instead of fedora-release. However it would be nice if fedora-release also was changed to align with these changes.
The first change was that when provides is used with a version string, the whole string is used now instead of the version of the package. (If there is no version string, then the version of the package is used.) This affected people using generic-release as it provided a version string for redhat-release that included the version and release of the package. This change would also affect people who set disroverpkg to system-release for either package. There probably aren't many people who have done that, but it isn't unreasonable.
The other change is that distropkg is now a list and the default is ['system-release(release)', 'redhat-release']. Since system-release(release) is listed first it would be nice if that was provided, so that yum (and eventually dnf and livecd-creator) didn't have to look at two provides to pick up the release version used by default for releasever.
There are two bugs that have been filed related to this change for other packages that might provide more insight on the change. (bug 1044675 and bug 1040607)
	
My the suggested changes are:
Remove the explicit version on the system-release provides.
Add a provides for system-release(release).

These yum changes are currently in rawhide, f20 updates and f19 updates-testing.

Comment 1 Bruno Wolff III 2013-12-28 18:55:11 UTC
Created attachment 842732 [details]
patch for f20

Comment 2 Bruno Wolff III 2013-12-28 18:56:22 UTC
Created attachment 842744 [details]
Patch for f19

Comment 3 Fedora Update System 2014-02-19 13:26:08 UTC
fedora-release-19-8 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/fedora-release-19-8

Comment 4 Fedora Update System 2014-02-19 13:51:38 UTC
fedora-release-20-3 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/fedora-release-20-3

Comment 5 Fedora Update System 2014-02-22 00:39:23 UTC
Package fedora-release-19-8:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing fedora-release-19-8'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-2791/fedora-release-19-8
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2014-02-23 08:36:55 UTC
fedora-release-20-3 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2014-02-26 13:55:05 UTC
fedora-release-19-8 has been pushed to the Fedora 19 stable repository.  If problems still persist, 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.