Bug#645959: p11-kit looks in /usr/lib/$arch/pkcs11 for modules, nothing installs there?

[Andreas Metzler]

On 2011-10-20 Steve Langasek <steve.langasek at canonical.com> wrote:
[...]
> I see that the p11-kit package in unstable is converted for
> multiarch.  Great to see!  However, it looks like libp11-kit0 is
> meant to integrate with pkcs modules from other packages, all of
> which currently install to /usr/lib/pkcs11 - whereas because the
> library is multiarched, it only looks in
> /usr/lib/$(DEB_HOST_MULTIARCH)/pkcs11, and will never find these
> modules.

> Should libp11-kit0 declare a Breaks: against the versions of these packages
> which install to /usr/lib/pkcs11, and a transition done? 

Hello,

a transition using Breaks looks too heavy-handed to me. Installing
multi-arched p11-kit does not break other software's use of PKCS#11
modules. Also at least on Debian using relative paths and relying on
the module search path simply has never worked, the initial p11-kit
(0.3-1) upload already used the multi-arch path. Ubuntu was quicker
(first upload July 28) but I doubt there are many active users yet. If
the currently available modules moved, p11-kit users could make use of
them without specifying the full path in the configuration file.

I guess the critical part of the transition is to not break other
PKCS#11 users with the new path.

> Or should libp11-kit0 be patched to support looking up modules in
> both locations?
[...]

Won't this introduce problems on partial upgrades to multiarch? Evil
things might happen if a i386 p11-kit tried to load a amd64 module
from /usr/lib/.

cu andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'