Bug 772431 - Update libXNVCtrl to 295.09
Summary: Update libXNVCtrl to 295.09
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: libXNVCtrl
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-08 02:17 UTC by Robert Scheck
Modified: 2013-05-02 21:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 958987 (view as bug list)
Environment:
Last Closed: 2013-02-13 08:09:36 UTC
Type: ---


Attachments (Terms of Use)

Description Robert Scheck 2012-01-08 02:17:32 UTC
Description of problem:
Please update libXNVCtrl to 295.09, the 169.12 version in Fedora is very old
and current gnome-applet-sensors is also looking for a newer version than our
Fedora is currently shipping.

Version-Release number of selected component (if applicable):
libXNVCtrl-169.12-5.fc15

How reproducible:
Everytime, see above and below
  
Actual results:
libXNVCtrl-169.12-5

Expected results:
libXNVCtrl-295.09-1 (or better)

Additional info:
Looks like upstream switched from imake to standard Makefiles. I don't think
the ABI is compatible, so maybe a soname bump is required?

Comment 1 Robert Scheck 2012-01-22 14:22:51 UTC
Adam, ping? Can you please reply to this report somehow? Thank you.

Comment 2 Alex Butcher 2012-06-09 19:13:28 UTC
Alex Murray's indicator-sensors for GNOME 3 also needs a newer version of libXNVCtrl for its nVidia sensor plugin to work.

Comment 3 Alex Murray 2012-07-17 11:33:20 UTC
Yeah it would be great to see an updated version as there is no way to check the library's version at compile time and hence even say #ifdef out the code which requires the newer version to allow it to compile against the old version currently in Fedora - and as a recent convert to Fedora from Ubuntu I'd love to get indicator-sensors packaged for Fedora but this currently blocks that...

Comment 4 Fedora End Of Life 2013-01-16 10:00:44 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2013-02-13 08:09:39 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 6 Alex Butcher 2013-02-13 12:10:10 UTC
Still a bug in Fedora 18!

http://koji.fedoraproject.org/koji/packageinfo?packageID=4836

Please re-open against F18.


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