On 2014-07-28 15:40:46 +0200, Joachim Breitner wrote: > Unfortunately, the upstream author believes that programs expecting a > fully qualified domain names to exist are broken.
In any case, this is unrelated to the problem here. Without libnss-myhostname, there was a working FQDN on my machine. After libnss-myhostname got installed (automatically, due to some dependency), exim4 failed to provide the FQDN, just the short name. It shouldn't have broken a correctly configured machine! > So I guess we should add a conflicts to affected packages. Please, conflict with exim4. Otherwise the issue remains unnoticed by apt-listbugs. > BTW, what should the FQDN even be here? My laptop doesn’t have a FQDN > that resolves to it, so the concept seems to be dubious at least. You may find the concept dubious on a laptop (though setting up a resolvable FQDN is very easy for programs that need one), but libnss-myhostname also breaks machines on a fixed network with a FQDN resolvable everywhere. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
