Bug 573796 - libassuan-2.0.x available
Summary: libassuan-2.0.x available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libassuan
Version: 14
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 582775 (view as bug list)
Depends On: 622979
Blocks: 496454 F14Target
TreeView+ depends on / blocked
 
Reported: 2010-03-15 20:02 UTC by Fabian Affolter
Modified: 2010-09-01 05:44 UTC (History)
4 users (show)

Fixed In Version: libksba-1.0.8-1.fc14
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-01 05:44:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Fabian Affolter 2010-03-15 20:02:21 UTC
There is a new release of libassuan available.

The latest version is 2.0.0.

Comment 1 Rex Dieter 2010-03-15 20:10:49 UTC
We'll have to tread carefully, it's api/abi incompatible with prior releases.

Will likely have to target F-14 for this one, but since libassuan-1.0.x was a static lib only, maybe we can make things parallel-installable.

Comment 2 Rex Dieter 2010-04-15 19:19:17 UTC
*** Bug 582775 has been marked as a duplicate of this bug. ***

Comment 3 Rex Dieter 2010-07-23 17:37:09 UTC
I'd like to get this into Fedora 14 at least, I've ping'd my fellow maintainers for feedback.

Comment 4 Fedora Update System 2010-08-10 22:39:40 UTC
dirmngr-1.1.0-1.fc14,gnupg2-2.0.16-1.fc14,libksba-1.0.8-1.fc14,libgpg-error-1.9-1.fc14,libassuan-2.0.0-1.fc14 has been submitted as an update for Fedora 14.
http://admin.fedoraproject.org/updates/dirmngr-1.1.0-1.fc14,gnupg2-2.0.16-1.fc14,libksba-1.0.8-1.fc14,libgpg-error-1.9-1.fc14,libassuan-2.0.0-1.fc14

Comment 5 Rex Dieter 2010-08-10 22:41:11 UTC
pending update, there seems to be at least some items not yet ported to use libassuan api v2, like gpa.  I'm testing other stuff too, but if this is still the case, will try making some sort of libassuan1 compat pkg

Comment 6 Rex Dieter 2010-08-11 22:17:48 UTC
libassuan1 pkg review, bug #622979

Comment 7 Fedora Update System 2010-08-12 19:49:05 UTC
dirmngr-1.1.0-1.fc14, gnupg2-2.0.16-1.fc14, libassuan-2.0.0-1.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update dirmngr gnupg2 libassuan'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/dirmngr-1.1.0-1.fc14,gnupg2-2.0.16-1.fc14,libassuan-2.0.0-1.fc14

Comment 8 Fedora Update System 2010-08-16 16:04:06 UTC
dirmngr-1.1.0-1.fc14, gnupg2-2.0.16-1.fc14, libassuan-2.0.0-2.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update dirmngr gnupg2 libassuan'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/dirmngr-1.1.0-1.fc14,gnupg2-2.0.16-1.fc14,libassuan-2.0.0-2.fc14

Comment 9 Fedora Update System 2010-08-25 01:23:07 UTC
libksba-1.0.8-1.fc14, libgpg-error-1.9-1.fc14, dirmngr-1.1.0-1.fc14, gnupg2-2.0.16-1.fc14, libassuan-2.0.0-2.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update libksba libgpg-error dirmngr gnupg2 libassuan'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/libksba-1.0.8-1.fc14,libgpg-error-1.9-1.fc14,dirmngr-1.1.0-1.fc14,gnupg2-2.0.16-1.fc14,libassuan-2.0.0-2.fc14

Comment 10 Fedora Update System 2010-09-01 05:43:57 UTC
libksba-1.0.8-1.fc14, libgpg-error-1.9-1.fc14, dirmngr-1.1.0-1.fc14, gnupg2-2.0.16-1.fc14, libassuan-2.0.0-2.fc14 has been pushed to the Fedora 14 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.