Bug 891929 - please update to 3.1.3
Summary: please update to 3.1.3
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: yubikey-personalization-gui
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Maxim Burgerhout
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-04 14:25 UTC by Patrick C. F. Ernzer
Modified: 2013-12-14 03:22 UTC (History)
2 users (show)

Fixed In Version: yubikey-personalization-gui-3.1.11-2.fc20
Clone Of:
Environment:
Last Closed: 2013-12-14 03:22:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
outpiut of rpmbuild -bc yubikey-personalization-gui.spec (3.83 KB, text/plain)
2013-01-05 00:09 UTC, Patrick C. F. Ernzer
no flags Details
patch to spec file to build 3.1.3 (1.27 KB, patch)
2013-01-05 00:32 UTC, Patrick C. F. Ernzer
no flags Details | Diff

Description Patrick C. F. Ernzer 2013-01-04 14:25:00 UTC
Description of problem:
yubikey-personalization-gui 3.1.3 (released 2012-12-21) is available
http://www.yubico.com/products/services-software/personalization-tools/use/cross-platform-personalization-tool-release-notes/

Could you please update the package in F17, F18 and rawhide?

Version-Release number of selected component (if applicable):
yubikey-personalization-gui-3.1.2-1.fc17.x86_64

How reproducible:
always

Steps to Reproduce:
1. get shiny new production YubiKey NEO (mine arrived yesterday, had a beta NEO before that)
2. try to personalise it with yubikey-personalization-gui-3.1.2-1.fc17.x86_64
  
Actual results:
YubiKey NEO not detected.
Go read release notes, 3.1.3 has fixes for the production NEO

Expected results:
Ability to personalize production YubiKey NEO. It seems I need 3.1.3

Additional info:

Comment 1 Maxim Burgerhout 2013-01-04 14:38:57 UTC
My NEO dropped in the mail last week too, so this is on my list. Building 3.1.3 requires an update of ykpers to 1.11.1 though, iirc, so it's going to take a little time.

Comment 2 Patrick C. F. Ernzer 2013-01-04 17:07:31 UTC
about ykpers; yeah just noticed and updated 886539

about time: no worries, I was able to program my NEO with the updated ykpers.

Comment 3 Patrick C. F. Ernzer 2013-01-05 00:09:33 UTC
Created attachment 672626 [details]
outpiut of rpmbuild -bc yubikey-personalization-gui.spec

FWIW; as opposed to ykpers-1.11.1, this one is not a simple rebuild. :-(

Comment 4 Patrick C. F. Ernzer 2013-01-05 00:32:48 UTC
Created attachment 672627 [details]
patch to spec file to build 3.1.3

doh! ignore previous comment. I had forgotten to update ykpers-devel to 1.11.1

After updating, it built just fine.

yubikey-personalization-gui comes up fine, but I did not overwrite the config I set with ykpersonalize 1.11.1 on another PC earlier.

Comment 5 Fedora End Of Life 2013-07-04 06:15:12 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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 17'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 6 Fedora End Of Life 2013-08-01 17:46:21 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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 7 Patrick C. F. Ernzer 2013-08-16 13:18:35 UTC
F19 still has 3.1.2
re-opening and adjusting version

Comment 8 Fedora Update System 2013-12-01 20:42:22 UTC
yubikey-personalization-gui-3.1.11-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/yubikey-personalization-gui-3.1.11-2.fc20

Comment 9 Maxim Burgerhout 2013-12-01 20:43:53 UTC
Also submitted an updated build for F19

Comment 10 Fedora Update System 2013-12-02 23:51:23 UTC
Package yubikey-personalization-gui-3.1.11-2.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing yubikey-personalization-gui-3.1.11-2.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-22549/yubikey-personalization-gui-3.1.11-2.fc20
then log in and leave karma (feedback).

Comment 11 Patrick C. F. Ernzer 2013-12-12 13:57:41 UTC
Thanks Maxim,
had a test with the F19 one, it recognised all the yuibis I could get my hands on.
I did not re-write any of the yubis, if you want me to, then I'll have to check at home if I still have any yubis not in active use.
Suggest bug gets closed. Seems all OK from this end.

Comment 12 Fedora Update System 2013-12-14 03:22:06 UTC
yubikey-personalization-gui-3.1.11-2.fc20 has been pushed to the Fedora 20 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.