On 03/28/2011 03:20 PM, Dmitri Pal wrote:
On 03/28/2011 04:38 PM, Pavel Zůna wrote:
This patch handles the issue in a kind of stupid way, but I couldn't
think of anything better.
It adds a new flag parameter to user-add (--noprivate). With this
flag, the command marks the private group about
On 03/28/2011 04:20 PM, Dmitri Pal wrote:
On 03/28/2011 04:38 PM, Pavel Zůna wrote:
This patch handles the issue in a kind of stupid way, but I couldn't
think of anything better.
It adds a new flag parameter to user-add (--noprivate). With this
flag, the command marks the private group about
On 03/28/2011 04:38 PM, Pavel Zůna wrote:
> This patch handles the issue in a kind of stupid way, but I couldn't
> think of anything better.
>
> It adds a new flag parameter to user-add (--noprivate). With this
> flag, the command marks the private group about to be created for
> deletion and is de
Pavel Zůna wrote:
On 2011-03-28 23:05, Rob Crittenden wrote:
Pavel Zůna wrote:
This patch handles the issue in a kind of stupid way, but I couldn't
think of anything better.
It adds a new flag parameter to user-add (--noprivate). With this flag,
the command marks the private group about to be
On 03/28/2011 04:56 PM, Adam Young wrote:
To give a little more context: we are llong to split out the logic
used to define the views of the entities from the reusable portion of
the toolkit. This patch introduces a builder object which contains
the temporary state of the entity build process
On 2011-03-28 23:05, Rob Crittenden wrote:
Pavel Zůna wrote:
This patch handles the issue in a kind of stupid way, but I couldn't
think of anything better.
It adds a new flag parameter to user-add (--noprivate). With this flag,
the command marks the private group about to be created for deletio
Pavel Zůna wrote:
This patch handles the issue in a kind of stupid way, but I couldn't
think of anything better.
It adds a new flag parameter to user-add (--noprivate). With this flag,
the command marks the private group about to be created for deletion and
is deleted after the user is created.
This patch handles the issue in a kind of stupid way, but I couldn't
think of anything better.
It adds a new flag parameter to user-add (--noprivate). With this flag,
the command marks the private group about to be created for deletion and
is deleted after the user is created. The only excepti
On 03/28/2011 10:03 AM, Dmitri Pal wrote:
On 03/27/2011 12:27 AM, Adam Young wrote:
http://freeipa.org/page/Main_Page
In what way?
Well, the obvious was the 2.0 announcement needed to get up there. I
see that has happened.
But it also seems so...generic? I'd like to integrate in the loo
Rob Crittenden wrote:
Simo Sorce wrote:
One is a memory leak that can happen in some error paths.
It is not highly probable to happen, so it can be deferred to post GA
The other is a uninitialized variable that could cause a segfault in
some cases (not seen on the wild, depends on an error path
Target branches: master, ipa-2-0
---
When duplicate user is added an inconsistent error message to the rest
of the framework is printed. This patch changes this to standard
duplicate error message.
https://fedorahosted.org/freeipa/ticket/1116
>From 5c2613c6e171c8085eddf84a35fc6c4be2fd640b Mon Se
Target branches: master, ipa-2-0
---
Most of the pwpolicy_* commands do include cospriority in the result
and potentially in the attribute rights (--all --rights). Especially
when --raw output is requested. This patch fixes it for all
pwpolicy commands.
https://fedorahosted.org/freeipa/ticket/110
We should gracefully handle the case where no TGT has been forwarded.
Right now we return a 500 error.
ticket 1101
rob
freeipa-rcrit-756-ccache.patch
Description: application/mbox
___
Freeipa-devel mailing list
Freeipa-devel@redhat.com
https://www.r
Stephen Gallagher wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/28/2011 09:15 AM, Dmitri Pal wrote:
On 03/28/2011 07:23 AM, Pavel Zuna wrote:
With this patch, the gidNumber is set automatically only if it wasn't
specified explicitly by the user.
Ticket #1127
Pavel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/28/2011 09:15 AM, Dmitri Pal wrote:
> On 03/28/2011 07:23 AM, Pavel Zuna wrote:
>> With this patch, the gidNumber is set automatically only if it wasn't
>> specified explicitly by the user.
>>
>> Ticket #1127
>>
>> Pavel
>>
>>
>>
On 03/28/2011 06:54 AM, Jan Cholasta wrote:
This patch enables the user to specify netmask/prefix length with IP
addresses (see
http://packages.python.org/netaddr/netaddr.ip.IPNetwork-class.html)
during installation for proper DNS reverse zone setup.
https://fedorahosted.org/freeipa/ticket/91
Change the wording of the error message "The IPA Server hostname cannot
resolve to localhost" to "The IPA Server hostname must not resolve to
localhost".
https://fedorahosted.org/freeipa/ticket/1009
--
Jan Cholasta
>From 69084689247691fb9d7a89ea636e0273d3185e22 Mon Sep 17 00:00:00 2001
From: J
On 03/28/2011 07:23 AM, Pavel Zuna wrote:
> With this patch, the gidNumber is set automatically only if it wasn't
> specified explicitly by the user.
>
> Ticket #1127
>
> Pavel
>
>
> ___
> Freeipa-devel mailing list
> Freeipa-devel@redhat.com
> https://ww
With this patch, the gidNumber is set automatically only if it wasn't specified
explicitly by the user.
Ticket #1127
Pavel
freeipa-pzuna-87-fixgidnumber.patch
Description: application/mbox
___
Freeipa-devel mailing list
Freeipa-devel@redhat.com
http
This patch enables the user to specify netmask/prefix length with IP
addresses (see
http://packages.python.org/netaddr/netaddr.ip.IPNetwork-class.html)
during installation for proper DNS reverse zone setup.
https://fedorahosted.org/freeipa/ticket/910
--
Jan Cholasta
>From 800eaf3c5caa3c7fcde3
20 matches
Mail list logo
