Hi, Eduard: On Tuesday 31 August 2010 20:40:28 you wrote: > Version: 56959 > > #include <hallo.h> > > * Jesús M. Navarro [Tue, Aug 31 2010, 03:57:15PM]: > > BindAddress: 127.0.0.1 192.168.0.1 > > > > Then, the cron.daily script will fail with the following error: > > > > mithrandir:/etc/apt-cacher-ng# /etc/cron.daily/apt-cacher-ng > > Cannot connect, no alternative (socket file) available > > no such host: 127.0.0.1192.168.0.1 > > I think there is junk in your line mentioned above, maybe unprintable > chars?
As per vim, there's no junk in that line. Just in case I deleted it and rewrited it from scratch. Same results, so it seems it's a "real" bug. > Anyhow, this bug cannot fixed in Stable. It's a bug, nevertheless. And there *might* be ways to resolve it in Stable (i.e.: changing the comment to state that it won't take more than one IP: that won't change the package behaviour so I think it would be acceptable for Stable). On the other hand, given that a patch is provided that won't change current working configs it might be considered for next point release. > Try the backport from > > http://www.unix-ag.uni-kl.de/~bloch/acng/download/backports/ I'll give it a try when I have some time for it and I'll tell you. > > This bug is somehow related to 545337. > > As related as I am to the Emperor of China. Are you cousins, per chance? Bug 545337 is about inacurate documentation regarding the very same option that is giving me problems. Maybe my bug is a mistake in the comment (maybe apt-cacher-ng is not expected to take more than one IP on the config file). That makes both bugs "somehow related" in my book but, hey, it's not me the one that will resolve any of them, so do as you see fit. Cheers. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
