Hello,
On ketvirtadienis 24 Gruodis 2009 09:22:57 Beojan Stanislaus wrote:
> On Thursday 24 December 2009 01:43:22 you wrote:
> > Good luck!!!
> >
> > I won't be surprised if 4.3.4 would still be waiting in unstable when
>
> 4.4.0
>
> > or 1 will be released.
> > 4.3.3 -- stillbirth
> > 4.3.2
On 2009-12-23 Diederik de Haas wrote:
> Searching for a way to configure it manually (config files) did bring
> something interesting to light: the package policykit was removed, but
> not it's configuration file. And no other package starting with
> 'policykit' was installed!
>
> Could that b
On Fri, Dec 25, 2009 at 1:29 AM, Diederik de Haas wrote:
> On 2009-12-23 Diederik de Haas wrote:
>> Searching for a way to configure it manually (config files) did bring
>> something interesting to light: the package policykit was removed, but
>> not it's configuration file. And no other packag
On 2009-12-25 George Kiagiadakis wrote:
> policykit and policykit-1 are incompatible with each other.
That's not the impression I got from the changelog (0.94-1):
Rename package to policykit-1. Upstream (at least temporarily) forked
the project to make it installable in parallel with policyki
On Fri, Dec 25, 2009 at 2:03 AM, Diederik de Haas wrote:
> On 2009-12-25 George Kiagiadakis wrote:
>> policykit and policykit-1 are incompatible with each other.
> That's not the impression I got from the changelog (0.94-1):
> Rename package to policykit-1. Upstream (at least temporarily) forked
>
On 2009-12-25 George Kiagiadakis wrote:
> Yes, they are co-installable, but I mean that the API is incompatible,
> so you can't take a policykit-based application and compile it with
> policykit-1. Much like Qt3 and Qt4 are incompatible with each other.
Thanks for the explanation, installing policy
6 matches
Mail list logo
