The big Debian day

Oh well… today I upgraded a server at my workplace from Sarge to Etch. This went fairly well EXCEPT that the machine was quite slow afterwards and Samba didn’t work anymore. No problem, I thought, because during the upgrade the Samba was displaying a note that I’ll need to change the passdb line, because it doesn’t support chained backend lists anymore.
The problem was, that this didn’t help. To make a long story short:
During the upgrade the file /etc/libnss-ldap.conf has been overwritten without any notification. There’s even no /etc/libnss-ldap.conf.dpkg-old file.
Apparently the QA of the Etch release failed in this particular case. Am I the only one who’s using LDAP?

Update:
Meebey hinted me to have a look at the config file. The problem is, that the config file has a Debconf header, which indicates that it is handled by debconf. I’m used to edit those files anyway, because usually debconf (or the package scripts) notices if the file was changed manually and gives a warning about this issue. Well, the libnss-ldap package seems to be rather dumb and doesn’t recognize when something has been changed within its configuration file. So, removing the debconf header will prevent this from happening again. Thanks, Meebey!

Published

4 comments

  1. Ingo, I can understand your frustration, annoyance and upset at what's happened to m68k and its status within Debian. Please don't take everything off line and give up: it's quite possible that Freescale / Coldfire processors (or whatever they're called – I can't remember at the moment) can get m68k back on track – there's nothing to stop
    m68k synching up on a point release, is there? You've done a deal of hard work – please reconsider, because walking away now would devalue some of your effort.
    Thanks for reading this. Andy

  2. AFAIK nobody really knows where the “Universal Operating System” moniker came from; it was just made up one day by the website maintainers (or at least so I'm told by folks who've been around in Debian much longer than I). I'd be just as happy to see it replaced with something a little less grandiose.

Comments are closed.