On Wed, 2016-04-13 at 15:22 +0200, Michael Biebl wrote:
> Am 13.04.2016 um 15:13 schrieb Sam Morris:
> >
> > Scratch that, I just figured it out. Although I had policykit-1 from
> > testing installed, libpolkit-backend-1-0 from stable was still
> > installed. After upgrading that too, and restarting polkitd.service,
> > the new code with the fix is used and everything works fine!
> >
> > Perhaps polkit-1 could be made to depend on the exact ${binary:Version}
> > of libpolkit-backend-1-0 to prevent this kind of version skew from
> > happening again.
> I wouldn't mind tightening the inter-package dependencies and would
> suggest a shlibs.local file as I use in tracker [1].
> I don't see a downside in doing so and it would prevent issues like
> yours. Unless Simon disagress, let's reassign this to policykit-1.I guess another alternative would be to fold the contents of libpolkit- backend-1-0 into policykit-1. It doesn't seem like a public library and doesn't have any other clients. -- Sam Morris <https://robots.org.uk/> CAAA AA1A CA69 A83A 892B 1855 D20B 4202 5CDA 27B9
signature.asc
Description: This is a digitally signed message part
