On Fri, Jan 17, 2014 at 01:25:28PM +0800, Rolf Leggewie wrote: > On 17.01.2014 11:47, Adam Borowski wrote: > > When attempting to upgrade or uninstall+install: > > Setting up polipo (1.0.4.1-5) ... > > Starting polipo: Couldn't open log file /var/log/polipo: Is a directory > > invoke-rc.d: initscript polipo, action "start" failed. > > thank you for your report and my apologies for the problem. For what > it's worth, I cannot reproduce it in a chroot. And looking at the diff > to the latest version I don't see anything immediately obvious that > might be causing this. My suspicion is it has something to do with > http://anonscm.debian.org/gitweb/?p=collab-maint/polipo.git;a=commit;h=520dc059bf1c3b93b243c47c47bde5f4c1e697a3 > > What version are you upgrading from?
>From 1.0.4.1-4. The system has been installed recently (a vserver container) and never had a version earlier than that; the config though comes from an old box, from earlier versions of polipo. None of settings it does set seems to be related, though. Reportbug attached all non-comment lines to the original report. > Did you set or unset $NAME somewhere? Not to my knowledge. > Does "env|grep -i name" show anything? LOGNAME=root (or LOGNAME=kilobyte as the user) > The log file should be /var/log/polipo/polipo.log, not > /var/log/polipo. What happens if you hardcode the configuration to > LOGFILE=/var/log/polipo/polipo.log in /etc/polipo/config? Setting up polipo (1.0.4.1-5) ... Starting polipo: /etc/polipo/config:155: unknown config variable LOGFILE Couldn't open log file /var/log/polipo: Is a directory invoke-rc.d: initscript polipo, action "start" failed. Meow! -- A tit a day keeps the vet away. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
