-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/25/2009 12:15 PM, Stephen Gallagher wrote:
> On 09/25/2009 11:31 AM, Jakub Hrozek wrote:
>> On 09/25/2009 05:12 PM, Stephen Gallagher wrote:
>>> Nack
>
>>> The changes to sssd.spec.in are unnecessary. The upgrade_config.py
>>> already does an in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/25/2009 11:31 AM, Jakub Hrozek wrote:
> On 09/25/2009 05:12 PM, Stephen Gallagher wrote:
>> Nack
>
>> The changes to sssd.spec.in are unnecessary. The upgrade_config.py
>> already does an internal check and bails out if the version is already
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/25/2009 05:12 PM, Stephen Gallagher wrote:
> Nack
>
> The changes to sssd.spec.in are unnecessary. The upgrade_config.py
> already does an internal check and bails out if the version is already
> matched.
>
I know there is a check in the scrip
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/25/2009 10:50 AM, Jakub Hrozek wrote:
> Convert the example config to v2 format, upgrade config on update only
>
> Also, instead of having an LDAP proxy domain as an example, show a
> native LDAP config.
Nack
The changes to sssd.spec.in are un
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Convert the example config to v2 format, upgrade config on update only
Also, instead of having an LDAP proxy domain as an example, show a
native LDAP config.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fed
