Bug 1043181 - epoch revision for f20 is lower than f19 and causes issues with fedup
Summary: epoch revision for f20 is lower than f19 and causes issues with fedup
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: imsettings
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-14 17:26 UTC by Robert Lightfoot
Modified: 2013-12-26 22:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-20 08:04:40 UTC
Type: Bug


Attachments (Terms of Use)

Description Robert Lightfoot 2013-12-14 17:26:35 UTC
Description of problem:
Following fedup instructions the f19 imsettings remain because it is "newer" than the f20 version.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Akira TAGOH 2013-12-16 09:21:09 UTC
$ koji latest-pkg f19-updates imsettings
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
imsettings-1.6.7-1.fc19                   f19-updates           tagoh
$ koji latest-pkg f20-updates imsettings
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
imsettings-1.6.7-1.fc20                   f20-updates           tagoh

No epoch is used on both. how did you estimate that?

Comment 2 Akira TAGOH 2013-12-20 08:04:40 UTC
upgrading with fedup from f19 to f20 works for me.

Comment 3 Robert Lightfoot 2013-12-26 22:35:40 UTC
This may be closed now.  At the time it was written imsettings-1.6.7-1.fc20 was not in updates, but updates-testing and this was the issue for fedup.


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