Package: privoxy
Version: 3.0.21-3
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.15.0-rc2-zeitbloms-zeitvertreib-00107-g76429f1 (SMP w/4 CPU 
cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages privoxy depends on:
ii  adduser              3.113+nmu3
ii  init-system-helpers  1.18
ii  initscripts          2.88dsf-53
ii  libc6                2.18-5
ii  libpcre3             1:8.31-5
ii  logrotate            3.8.7-1
ii  lsb-base             4.1+Debian12
ii  perl                 5.18.2-2+b1
ii  zlib1g               1:1.2.8.dfsg-1

Versions of packages privoxy recommends:
ii  doc-base  0.10.5

privoxy suggests no packages.

-- Configuration Files:
/etc/privoxy/config changed:
user-manual /usr/share/doc/privoxy/user-manual
confdir /etc/privoxy
logdir /var/log/privoxy
actionsfile match-all.action # Actions that are applied to all sites and maybe 
overruled later on.
actionsfile default.action   # Main actions file
actionsfile user.action      # User customizations
filterfile default.filter
filterfile user.filter      # User customizations
logfile logfile
listen-address  127.0.0.1:8118
toggle  1
enable-remote-toggle  0
enable-remote-http-toggle  0
enable-edit-actions 0
enforce-blocks 0
buffer-limit 4096
enable-proxy-authentication-forwarding 0
forwarded-connect-retries  0
accept-intercepted-requests 0
allow-cgi-request-crunching 0
split-large-forms 0
keep-alive-timeout 5
tolerate-pipelining 1
socket-timeout 300


-- no debconf information
Subject: systemd[1]: [/lib/systemd/system/privoxy.service:9] Not an absolute 
path, ignoring: $PIDFILE
Package: privoxy
Version: 3.0.21-3
Severity: normal

Dear Maintainer,

this is a sid-system with systemd. The file  
/lib/systemd/system/privoxy.service:9] seems to cleanly apply an absolute path 
to $PIDFILE, but gets "Not an absolute path, ignoring: $PIDFILE"
I can reproduce this with actual privoxy-version.

Thanks!

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.15.0-rc2-zeitbloms-zeitvertreib-00107-g76429f1 (SMP w/4 CPU 
cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages privoxy depends on:
ii  adduser              3.113+nmu3
ii  init-system-helpers  1.18
ii  initscripts          2.88dsf-53
ii  libc6                2.18-5
ii  libpcre3             1:8.31-5
ii  logrotate            3.8.7-1
ii  lsb-base             4.1+Debian12
ii  perl                 5.18.2-2+b1
ii  zlib1g               1:1.2.8.dfsg-1

Versions of packages privoxy recommends:
ii  doc-base  0.10.5

privoxy suggests no packages.

-- Configuration Files:
/etc/privoxy/config changed:
user-manual /usr/share/doc/privoxy/user-manual
confdir /etc/privoxy
logdir /var/log/privoxy
actionsfile match-all.action # Actions that are applied to all sites and maybe 
overruled later on.
actionsfile default.action   # Main actions file
actionsfile user.action      # User customizations
filterfile default.filter
filterfile user.filter      # User customizations
logfile logfile
listen-address  127.0.0.1:8118
toggle  1
enable-remote-toggle  0
enable-remote-http-toggle  0
enable-edit-actions 0
enforce-blocks 0
buffer-limit 4096
enable-proxy-authentication-forwarding 0
forwarded-connect-retries  0
accept-intercepted-requests 0
allow-cgi-request-crunching 0
split-large-forms 0
keep-alive-timeout 5
tolerate-pipelining 1
socket-timeout 300


-- no debconf information


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to