Bug 27842 - ldapseach-wrapper erkennt nur Leerzeichen, aber keine Tabs
ldapseach-wrapper erkennt nur Leerzeichen, aber keine Tabs
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: LDAP
UCS 3.0
All Linux
: P5 enhancement (vote)
: UCS 3.1
Assigned To: Philipp Hahn
Arvid Requate
: interim-1
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-07-06 09:42 CEST by Philipp Hahn
Modified: 2012-12-12 21:08 CET (History)
2 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Cleanup
Max CVSS v3 score:
hahn: Patch_Available+


Attachments
ldapsearch-wrapper (40.00 KB, application/octet-stream)
2012-07-06 09:42 CEST, Philipp Hahn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2012-07-06 09:42:30 CEST
Created attachment 4512 [details]
ldapsearch-wrapper

COLUMNS=200 man ldif | grep tab
A line may be continued by starting the next line with a single space or tab

Das macht ldapseach-wrapper gerade unbrauchbar für andere Aufgaben, wie z.B.
das Verarbeiten von LDIF-Daten aus anderen Quellen als ldapseach oder slapcat.
Comment 1 Philipp Hahn univentionstaff 2012-08-03 22:20:38 CEST
Umgesetzt.
svn34609, univention-config-registry_8.0.1-1.389.201208032206
Comment 2 Arvid Requate univentionstaff 2012-09-06 16:33:55 CEST
Verified:
 * Code review OK
 * tests/unwrap konsistent
 * Changelog OK
 * Funktion OK

root@master10:~# diff <(univention-ldapsearch -x | ldapsearch-wrapper) \
     <(univention-ldapsearch -x | sed 's/^ /\t/' | ldapsearch-wrapper) \
     && echo ok
ok
Comment 3 Stefan Gohmann univentionstaff 2012-12-12 21:08:50 CET
UCS 3.1-0 has been released: 
 http://forum.univention.de/viewtopic.php?f=54&t=2125

If this error occurs again, please use "Clone This Bug".