On 5/19/21 1:02 PM, Howard Chu wrote: > Michael Ströder wrote: >> On 5/18/21 6:23 PM, Howard Chu wrote: >>> Michael Ströder wrote: >>>> On 5/18/21 10:28 AM, Nick Milas wrote: >>>>> On 18/5/2021 1:55 π.μ., Michael Ströder wrote: >>>>>> Missing space after SUBSTR? >>>>> On 18/5/2021 1:57 π.μ., Howard Chu wrote: >>>>>> Yes, but there is only one attribute value #2 in the attribute. Pay >>>>>> attention to what the error message tells you. >>>>> >>>>> You were both right, thank you. >>>>> >>>>> Turns out that all trailing spaces of the copied (and inserted) ldif >>>>> sections were cut off (obviously during the copy process), so I had to >>>>> manually add them in wrapped lines which happened to be wrapped at a >>>>> space character... Tricky. >>>> >>>> It might be easier for such small schema changes to use a GUI LDAP >>>> client to avoid exactly this kind of problem. >>> >>> I don't see how that is relevant. The first problem is that he was trying >>> to do a wholesale replace of a schema file. If instead he had just a diff >>> of the old and new versions of the schema, he could of course have fed that >>> into an ldapmodify operation - whether by GUI or by CLI. >> >> Yes, he could have done this. With yet another tool required to create >> the LDIF diff. Or did you mean normal textual diff? This sometimes does >> not work. >> >> With a normal input form it would have been pretty easy just to edit a >> single attribute value without piping stuff through several tools. It's >> one of the rare cases where a GUI is IMHO better. > > I don't see how this makes the initial step any easier. Presumably he starts > with an old version and new version schema file. How is a GUI going to let > him create the diff between these any more easily than a command line?
In this particular case the admin would have just edited one or very few input field(s) and then hit the submit button. BTW: web2ldap internally only applies diffs after user edited the entry. > How does a GUI prevent a copy/paste from losing trailing spaces, any > more reliably than a command line? I assume that in this particular case the admin was confused by line-wrapping and/or his text editor has whitespace-cleaning enabled. The latter is pretty usual. We're talking here about behaviour of human beings which differs a lot (UX aspects). Thus your and my assumptions are subject to YMMV. Ciao, Michael.
