[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#707193: [ITR] templates://nss-pam-ldapd/{nslcd.templates,libnss-ldapd.templates}



Arthur de Jong wrote:
> This is what will be in NEWS.Debian file for 0.9.0:
> 
>     The 0.9 release changes the communication protocol used between the
>     NSS and PAM modules on one end and the nslcd process on the other
>     end.
> 
>     This means that after an upgrade, if the new nslcd is running,
>     processes that have the old NSS or PAM module already loaded will be
>     unable to perform queries.
> 
>     For example, if a screensaver, that was running before the upgrade,
>     has locked the screen during the upgrade the user will no longer be
>     able to unlock the screen.

That last paragraph has a bit if a foreign accent - it just needs some
reshuffled commas:

      For example, if a screensaver that was running before the upgrade
      has locked the screen during the upgrade, the user will no longer be
      able to unlock the screen.

("Defining" relative clauses aren't surrounded by commas in English,
but on the other hand there should usually be a comma between an "if"
clause and its "then" clause.)

> And these are the new packages (pynslcd will use the exact same
> templates and configuration file as nslcd):
> 
> Package: pynslcd
> Description: Daemon for NSS and PAM lookups using LDAP (Python implementation)
               d
No initial capitalisation, please.

Perhaps we could shorten that slightly to:

  Description: daemon for NSS and PAM lookups via LDAP - Python version

>  This package provides a daemon for retrieving user account, and other
>  system information from LDAP.

I've already pointed out the un-English comma in this sentence for
nslcd.  My patch had:

   This package provides a daemon for retrieving user account and similar
   system information from LDAP.

>  .
>  It is used by the libnss-ldapd and libpam-ldapd packages but by itself
>  is not very useful. This is an alternative to the nslcd package but
>  implemented in Python.
>  .
>  Note that pynslcd is currently EXPERIMENTAL and has not undergone the
>  same testing that nslcd has.

Oddly placed paragraph breaks.  Why not:

  Package: nslcd
  Description: daemon for NSS and PAM lookups via LDAP
   This package provides a daemon for retrieving user account and similar
   system information from LDAP. It is used by the libnss-ldapd and
   libpam-ldapd packages but is not very useful by itself.

  Package: pynslcd
  Description: daemon for NSS and PAM lookups via LDAP - Python version
   This package provides a daemon for retrieving user account and similar
   system information from LDAP. It is used by the libnss-ldapd and
   libpam-ldapd packages but is not very useful by itself.
   .
   This is an alternative Python implementation of nslcd. Note that it is
   currently EXPERIMENTAL and has not undergone the same testing as nslcd.

> Package: nslcd-utils
> Description: Utilities for querying LDAP via nslcd
               u
Again, no initial capitalisation, please.

>  These programmes provide for means to query and update information in
>  LDAP via nslcd.

That's not even the normal en_GB spelling for software programs, and
providing "for" means is wrong.

>  .
>   getent.ldap - perform LDAP lookups bypassing nsswitch configuration
>   chsh.ldap - change a user's shell in LDAP

Oh, so these are the utilities in question?  In reverse alphabetical
order.  Make it:

  Description: utilities for querying LDAP via nslcd
   This package provides tools to query and update information in LDAP
   via nslcd:
    * chsh.ldap - change a user's shell in LDAP;
    * getent.ldap - perform LDAP lookups bypassing nsswitch configuration.

-- 
JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package


Reply to: