On 04/20/2012 05:49 PM, Sumit Bose wrote:
I take samba4 and libldb from the ipa-devel repo. There are even
versions for my very old F15 devel system.
Yup, one of the first things I tried.
But those conflict with the libsmbclient in f16. If you try to remove or
update libsmbclient you'll disco
On Fri, Apr 20, 2012 at 12:37:08PM -0400, John Dennis wrote:
> We're supposed to be working on master now, not 2.2. But master has
> dependencies on samba4. Those dependencies can only be resolved on
> F17, an unreleased platform.
>
> I think it's reasonable for IPA developers to work on the curre
Make some minor improvements to user-status.
This beefs up the docs a bit, adds nsaccountlock to the output and
includes the time we checked each master.
It is a bit of a kludge to put nsaccountlock into the summary but I
don't want to return it per-server, it should be the same across them a
On Fri, 2012-04-20 at 16:09 -0400, Dmitri Pal wrote:
> I was under the assumption that to be able to wrap things properly you
> need both user password in clear that you have only at the moment the
> hashes are created and the key for the branch office replica. Is this
> the wrong assumption? If y
On 04/19/2012 07:43 PM, Simo Sorce wrote:
> Ok, this come close to a proper solution but not quite.
> So first of all, kerberos keys are available in the master, we do not
> need to also store the clear txt password and regenerate them, but we do
> need to be able to convey them to the replica wrap
On 04/20/2012 03:39 PM, Stephen Gallagher wrote:
On Fri, 2012-04-20 at 22:27 +0300, Alexander Bokovoy wrote:
:)
It failed to build due to koji issues, not the build issues.
Yes, the koji build failed due to koji issues, but since koji was bonked
I tried to build it in mock on my machine with
On Fri, 20 Apr 2012, Stephen Gallagher wrote:
On Fri, 2012-04-20 at 22:27 +0300, Alexander Bokovoy wrote:
:)
It failed to build due to koji issues, not the build issues.
We had also incompatible libldb in F16/F15 that prevented us going to
alpha18 instead of alpha16 in those distributions.
I
On Fri, 2012-04-20 at 22:27 +0300, Alexander Bokovoy wrote:
> :)
>
> It failed to build due to koji issues, not the build issues.
>
> We had also incompatible libldb in F16/F15 that prevented us going to
> alpha18 instead of alpha16 in those distributions.
>
> I hope Andreas (CC:) will be able t
On Fri, 20 Apr 2012, John Dennis wrote:
On 04/20/2012 01:35 PM, Alexander Bokovoy wrote:
Hi John,
On Fri, 20 Apr 2012, John Dennis wrote:
We're supposed to be working on master now, not 2.2. But master has
dependencies on samba4. Those dependencies can only be resolved on
F17, an unreleased pl
Ticket #2622
If we get an error from dogtag we always did raise a
CertificateOperationError exception with a message describing the
problem. Unfortuanately that error message did not go into the log,
just sent back to the caller. The fix is to format the error message
and send the same message to
... and this build failed due to issues in Koji
DEBUG util.py:257:
http://kojipkgs.fedoraproject.org/packages/authconfig/6.1.16/2.fc16/x86_64/authconfig-6.1.16-2.fc16.x86_64.rpm:
[Errno 14] PYCURL ERROR 7 - "couldn't connect to host"
DEBUG util.py:257: Trying other mirror.
Looks like some netwo
On 04/20/2012 01:35 PM, Alexander Bokovoy wrote:
Hi John,
On Fri, 20 Apr 2012, John Dennis wrote:
We're supposed to be working on master now, not 2.2. But master has
dependencies on samba4. Those dependencies can only be resolved on
F17, an unreleased platform.
I think it's reasonable for IPA
Hi John,
On Fri, 20 Apr 2012, John Dennis wrote:
We're supposed to be working on master now, not 2.2. But master has
dependencies on samba4. Those dependencies can only be resolved on
F17, an unreleased platform.
I think it's reasonable for IPA developers to work on the current
Fedora releas
We're supposed to be working on master now, not 2.2. But master has
dependencies on samba4. Those dependencies can only be resolved on F17,
an unreleased platform.
I think it's reasonable for IPA developers to work on the current Fedora
release (F16) and not have to resort to trying to develop
A new DNS permission that went into 2.2 uses all lower case to be
consistent with existing DNS Permissions. This switches it to use mixed
case as well. We'll investigate renaming the existing entries as well.
rob
>From cbe2981f1501c8c87fcad5a18d7bf4bc3c1d747c Mon Sep 17 00:00:00 2001
From: Rob
On 04/19/2012 08:35 PM, John Dennis wrote:
On 04/19/2012 07:04 AM, Petr Viktorin wrote:
On 04/18/2012 09:32 PM, John Dennis wrote:
Now that there are warnings, is pedantic mode necessary?
Great question, I also pondered that as well. My conclusion was there
was value in separating aggressiven
16 matches
Mail list logo