Bug 4294 - mageia2a3, kde 4.8 no kdesecrets packets
Summary: mageia2a3, kde 4.8 no kdesecrets packets
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-27 11:09 CET by episteme promeneur
Modified: 2012-01-27 17:40 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description episteme promeneur 2012-01-27 11:09:40 CET
Description of problem:

there is a new technology with kde 4.8 : kde secret

KSecretService is a new framework for sharing saved passwords and other credentials between a wider range of applications. KSecretService uses KDE's well-known interfaces through a Freedesktop-compliant API with other password systems, transparently for the user. KSecretService improves integration of KDE applications into other workspaces and allows 3rd party applications to plug into KDE's secure password saving system. 

where are the packets ?

kdesecrets
kdesecret-dev
kdesecrets-debug
Comment 1 John Balcaen 2012-01-27 17:40:11 CET
It's currently a work in progress :
- the package itself need a patch to build correctly since it's requesting a macro available in kde-workspace when it should be in kdelibs (reported to upstream author)
- the build of this package is a currently quite ugly :
  - you need to build kdelibs, then ksecrets & once it's done you need to rebuild kdelibs against ksecrets-devel (& then eventually rebuild kwallet if it was pushed to earlier)

Since i was not able to test it *before* (because i'm usually testing kde before even commiting on svn) i did not push it on repository.
However since it's building it's already available on the svn ( http://svnweb.mageia.org/packages/cauldron/ksecrets/ since 4.7.95) if you wanna test (i add an ugly BR to kde-workspace until i find the time to add a correct patch against it to push it correctly )

Closing as fixed (because i have too many bugs open) but also because i'll have a look on it (i promise) on this week end.

Status: NEW => RESOLVED
CC: (none) => balcaen.john
Resolution: (none) => FIXED


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