Comment 20 for bug 14929

Hi Steve,

On Mon, Apr 18, 2005 at 01:56:17AM -0700, Steve Langasek wrote:
> I think it's worth a lot to provide as smooth of an upgrade path as
> possible, and leave the README for cases we can't reasonably handle. Can

Yeah.

> this particular LDIF incompatibility be dealt with in fix_ldif?

In theory fix_ldif could be improved to handle all incompatibilities. If
we know them...

> > > The issue seems to be that slapcat created the root entry like this:
> > > uidNumber: 0000
> > > gidNumber: 0000
>
> > > but slapadd barfs on that, saying it is an invalid number! Changing
> > > the 0000 to 0 for the user and group settings worked fine
>
> > ... and another incompatibility.
>
> It would be better if fix_ldif knew about schemas and could therefore know
> which entries to automatically change; but even without that, we could
> safely edit the LDIF for this when it's a known attrib like uidNumber or
> gidNumber, couldn't we?

I think we could. OTOH I'd rather find out where those "0000" values are
coming from. Or wtf "0000" is an invalid number. Crazy stuff!

> A naive patch for this might look like the one attached.

Yep, naive but might work. Not to mention that there might be other
integer fields which will go mad like this. I wonder if there is a perl
module with full schema parsing support which would make writing
something like this much easier.

Greetings

 Torsten