Bug 752439 - newer nvr on Fedora 15
Summary: newer nvr on Fedora 15
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lirc
Version: 16
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Jarod Wilson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-09 14:11 UTC by Oliver Henshaw
Modified: 2011-12-06 01:01 UTC (History)
3 users (show)

Fixed In Version: lirc-0.9.0-7.fc16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 01:01:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Oliver Henshaw 2011-11-09 14:11:43 UTC
Description of problem:

I still have the F15 lirc-libs installed after preupgrading from F15 -> F16.

$ rpm -q lirc-libs
lirc-libs-0.9.0-7.fc15.x86_64
$ repoquery lirc-libs
lirc-libs-0:0.9.0-3.fc16.i686
lirc-libs-0:0.9.0-3.fc16.x86_64

Additionally, the F15 package seems to have some fixes not in the F15 package.

Comment 1 Nicola Soranzo 2011-11-17 15:42:29 UTC
In fact, this F15 update breaks the upgrade path, described at:

http://fedoraproject.org/wiki/Packaging/NamingGuidelines#Package_Versioning

Comment 2 Fedora Update System 2011-11-17 21:15:10 UTC
lirc-0.9.0-7.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/lirc-0.9.0-7.fc16

Comment 3 Fedora Update System 2011-11-19 05:59:07 UTC
Package lirc-0.9.0-7.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lirc-0.9.0-7.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-16092/lirc-0.9.0-7.fc16
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2011-12-06 01:01:34 UTC
lirc-0.9.0-7.fc16 has been pushed to the Fedora 16 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.