[Python-apps-team] Bug#796378: pelican: devserver's tcp port 8000 is also used by squid-deb-proxy

Daniel Stender debian at danielstender.com
Fri Aug 21 15:39:18 UTC 2015


Package: pelican
Version: 3.6.3-1
Severity: normal

Hi,

Pelican's devserver is running on port 8000 like squid-deb-proxy does by default, I would suggest to patch the default configuration of Pelican. Reassigning no problem with me.

Best,
DS

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.1.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pelican depends on:
ii  libpython2.7-stdlib [python-argparse]  2.7.10-3
ii  python                                 2.7.9-1
ii  python-blinker                         1.3.dfsg2-1
ii  python-dateutil                        2.2-2
ii  python-docutils                        0.12+dfsg-1
ii  python-feedgenerator                   1.7-2
ii  python-jinja2                          2.8-1
ii  python-markdown                        2.6.2-1
ii  python-pkg-resources                   18.0.1-2
ii  python-pygments                        2.0.1+dfsg-1.1
ii  python-six                             1.9.0-3
ii  python-tz                              2012c+dfsg-0.1
ii  python-unidecode                       0.04.16-1
pn  python:any                             <none>

pelican recommends no packages.

Versions of packages pelican suggests:
ii  pandoc       1.13.2.1~dfsg-1+b6
pn  pelican-doc  <none>
ii  python-bs4   4.3.2-2

-- no debconf information



More information about the Python-apps-team mailing list