On Tue, Jan 13, 2015 at 07:24:09PM +0100, Jakub Hrozek wrote:
On Tue, Jan 13, 2015 at 07:22:50PM +0100, Jakub Hrozek wrote:
> On Tue, Jan 13, 2015 at 11:31:40AM +0100, Sumit Bose wrote:
> > On Mon, Jan 12, 2015 at 06:08:04PM +0100, Jakub Hrozek wrote:
> > > On Mon, Jan 12, 2015 at 05:54:43PM +0100, Sumit Bose wrote:
> > > > > Thank you for the review. This should happen if your AD domain
name (not
> > > > > the real name) contains upper-case characters. This spelling is
kept in
> > > > > sysdb but get lower-cased e.g. in the getgrnam() output.
I've add a 8th
> > > > > patch which should fix it.
> > > >
> > > > Please ignore the 8th patch, it will cause other issues. I'll try
to
> > > > come up with an alternative fix.
> > > >
> > > > bye,
> > > > Sumit
> > >
> > > If you prefer, I can check the current patches, chances are the issue
> > > will not be related to this patchset, so we can just do an incremental
> > > fix.
> >
> > Please find attached a new version with a fixed 8th patch.
> >
> > bye,
> > Sumit
>
> I'm sorry, but patch #8 still doesn't work for me..the first pass is
> fine, but then in the second pass, the group membership is removed.
>
> I also see some EEXIST failures in the logs..would you like to see the
> logs or access to the machine?
btw the other patches have my ACK and can be pushed.
I pushed the ACK-ed patches to master:
* 62d919aea98edd1095f6a22241903d4c045b46ed
* 3cd287313d93e29f9754feb46017dba2a039affd
* f1f22df95996390f63266ebacb624e521d934592
* 942ebb62c8df766a22271103abd518ddae02ea3a
* e6046d23b3e90102fb3c796737ced03fb5a60fea
* 2fc12875f7d51248799016c19c1298b85e06a286
* d8ceb194023a2cdc8bc183acc322e9a7fb6fe2b1
and sssd-1-12:
* 5730f53f1fd47a2a485593048adf540c66d09934
* 04455af12b45a4790039e3655467cf164799c627
* 161c2fa226a31001d184594476616143d7fe34d3
* 87cc3049b74705afbb182fcceeec3c9fd5b668da
* 6b57aa03c7810dc45c79f087eb47a05c55f64056
* 1869e832b811cc0aae833cbf9f24fa151001f2b2
* 497e35d5d4b58f7194b11528be8a5f2ea7aca351