File: 03_fix_manpages.patch

package info (click to toggle)
ldapscripts 2.0.8-1
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 492 kB
  • ctags: 21
  • sloc: sh: 707; makefile: 167
file content (14 lines) | stat: -rw-r--r-- 1,532 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
From: Alexander Gerasiov <gq@debian.org>
Subject: Fix in manpage to prevent lintian warning.
 Lintian dislike too long lines in manpage, so I've added non-significal space
 in filter example.
Forwarded: not-needed

--- a/man/man5/ldapscripts.5
+++ b/man/man5/ldapscripts.5
@@ -75,4 +75,4 @@
 .B "Additional information: value does not conform to assertion syntax".
 Setting slapd's debug level to 32 shows additional details :
 .B "get_ava: illegal value for attributeType uidNumber".
-This is *not* a bug : the ldapscripts tend to use the power of LDAP filters to easily find users (or groups) using either a uidNumber (numerical value) or a uid (string value). The following filter (used by ldapfinger(1)) will generate the above message if $_USER is a login : "(|(&(objectClass=posixAccount)(|(uid=$_USER)(uidNumber=$_USER)))(&(objectClass=posixGroup)(|(cn=$_USER)(gidNumber=$_USER))))" because filter part "(uidNumber=$_USER)" requires an integer but gets a string. You can mostly ignore those warnings.
+This is *not* a bug : the ldapscripts tend to use the power of LDAP filters to easily find users (or groups) using either a uidNumber (numerical value) or a uid (string value). The following filter (used by ldapfinger(1)) will generate the above message if $_USER is a login : "(|(&(objectClass=posixAccount)(|(uid=$_USER)(uidNumber=$_USER))) (&(objectClass=posixGroup)(|(cn=$_USER)(gidNumber=$_USER))))" because filter part "(uidNumber=$_USER)" requires an integer but gets a string. You can mostly ignore those warnings.