Package: polipo
Version: 1.0.4.1-4
Severity: grave
Tags: patch
Justification: renders package (mostly) unusable

Polipo crashes after few minutes of browsing on my amd64 boxen with
syslog logging enabled. Since syslog logging is now the default, I think
grave severity is appropriate, even if other arches are unaffected.

This issue is fixed by upstream commit
136f10f7c918c51c0dc9b3ee750a509bbc96772e "Fix logging to syslog on
arches that need va_copy."

You should also consider shipping upstream git instead of just
backporting that one commit. Juliusz Chroboczek is "applying patches
that people send me, but not doing any new development or making any new
releases", so it's mostly bugfixes accumulating there.

cheers,
    Jan

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (800, 'testing'), (550, 'unstable'), (10, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages polipo depends on:
ii  libc6     2.17-93
ii  lsb-base  4.1+Debian12

polipo recommends no packages.

polipo suggests no packages.

-- Configuration Files:
/etc/cron.daily/polipo changed [not included]
/etc/polipo/config changed [not included]

-- no debconf information

Attachment: signature.asc
Description: Digital signature

Reply via email to