I also had a go at this today. :)
I built a gnome-keyring package for Precise in my PPA:
https://launchpad.net/~ginggs/+archive/sru
It is adam-stokes' last attempt plus the following changes:
- Change gnome-keyring's Recommends on libp11-kit-gnome-keyring
to Depends.
- Change libp11-kit-gnome-keyring's Breaks and Replaces on
gnome-keyring to (<< ${binary:Version}).
@eraserix: I agree that installing libp11-kit-gnome-keyring:i386 is
correct for the test case, not gnome-keyring:i386 as it contains the
executables and is not co-installable.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/859600
Title:
Please convert gnome-keyring to multiarch
Status in “gnome-keyring” package in Ubuntu:
Fix Released
Status in “gnome-keyring” source package in Precise:
In Progress
Status in “gnome-keyring” source package in Quantal:
Won't Fix
Status in “gnome-keyring” source package in Raring:
Fix Released
Status in “gnome-keyring” package in Debian:
New
Bug description:
[Impact]
Several applications are relying on this package as seen in comments 5 and 6.
[Test case]
Attempt to install both i386/amd64 versions and preferably verify if the
reported applications in this bug are able to run successfully
[Regression Potential]
Minimal, several rdepends build testing have been completed successfully and
nothing in the keyring code is attempting to dlopen any hardcoded library paths.
gnome-keyring is still installing libraries to /usr/lib instead of the
multarch compatible /usr/lib/$(DEB_HOST_MULTIARCH) directory. The
attached patch does the conversion.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
