Bug 985829 - need current version packaged (2.10)
need current version packaged (2.10)
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: ykclient (Show other bugs)
20
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Dennis Gilmore
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-18 06:41 EDT by John Dennis
Modified: 2014-03-24 02:44 EDT (History)
3 users (show)

See Also:
Fixed In Version: ykclient-2.12-1.fc19
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-03-24 02:40:48 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description John Dennis 2013-07-18 06:41:41 EDT
The ykclient package is out of date. The currently packaged version is 2.7, released 2 years ago. The current version is 2.10 released 2 months ago.

FreeRADIUS 3.0 has added yubikey support but it's failing to build because it's missing the ykclient_request_process symbol in libykclient.

Would you please package the new version for F18, F19 and rawhide.

Thank you.
Comment 1 Fedora End Of Life 2013-12-21 09:21:11 EST
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.
Comment 2 John Dennis 2013-12-23 10:13:08 EST
F20 still has version the old 2.7 version, please package the current version.
Comment 3 Fedora Update System 2014-03-13 18:29:23 EDT
ykclient-2.12-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/ykclient-2.12-1.fc20
Comment 4 Fedora Update System 2014-03-13 18:29:32 EDT
ykclient-2.12-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/ykclient-2.12-1.fc19
Comment 5 John Dennis 2014-03-13 22:09:19 EDT
Nick, now that ykclient has been updated you can enable the yubikey support in the freeradius spec file. Please do this for F20 and rawhide.
Comment 6 Fedora Update System 2014-03-15 11:01:54 EDT
Package ykclient-2.12-1.fc19, pam_yubico-2.14-1.fc19:
* 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 ykclient-2.12-1.fc19 pam_yubico-2.14-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-3826/pam_yubico-2.14-1.fc19,ykclient-2.12-1.fc19
then log in and leave karma (feedback).
Comment 7 Fedora Update System 2014-03-24 02:40:48 EDT
ykclient-2.12-1.fc20, pam_yubico-2.14-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 8 Fedora Update System 2014-03-24 02:44:50 EDT
ykclient-2.12-1.fc19, pam_yubico-2.14-1.fc19 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.