Bug#855287: varnish: change of listening port without effect
Package: varnish Version: 5.0.0-6 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? A change of the port varnish should listen in /etc/default/varnish is without any effect, it remains sitting on 6081. *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages varnish depends on: ii adduser 3.115 ii gcc 4:6.3.0-1 ii init-system-helpers 1.47 ii libbsd0 0.8.3-1 ii libc6 2.24-9 ii libc6-dev [libc-dev] 2.24-9 ii libedit2 3.1-20160903-3 ii libjemalloc1 3.6.0-9.1 ii libncurses5 6.0+20161126-1 ii libpcre3 2:8.39-2 ii libtinfo5 6.0+20161126-1 ii libvarnishapi15.0.0-6 ii lsb-base 9.20161125 varnish recommends no packages. Versions of packages varnish suggests: pn varnish-doc -- Configuration Files: /etc/default/varnish changed [not included] /etc/varnish/default.vcl changed [not included] -- no debconf information
Bug#855268: squid: PID file at wrong place -> not installable
Package: squid Version: 3.5.23-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I tried to install squid via apt-get install squid The problem is here: Feb 16 08:32:08 dx151 systemd[1]: Starting LSB: Squid HTTP Proxy version 3.x... Feb 16 08:32:08 dx151 squid[5885]: Starting Squid HTTP Proxy: squid failed! Feb 16 08:32:08 dx151 systemd[1]: squid.service: PID file /var/run/squid.pid not readable (yet?) after start: No such file or directory Feb 16 08:37:08 dx151 systemd[1]: squid.service: Start operation timed out. Terminating. Feb 16 08:37:08 dx151 systemd[1]: Failed to start LSB: Squid HTTP Proxy version 3.x. Feb 16 08:37:08 dx151 systemd[1]: squid.service: Unit entered failed state. Feb 16 08:37:08 dx151 systemd[1]: squid.service: Failed with result 'timeout'. dpkg: error processing package squid (--configure): subprocess installed post-installation script returned error exit status 1 Obviously the installer script tries to put the PID file in /var/run. This can not work, because squid has no write access to /var/run which is owned by root.root. Instead squid should put its PID file in /var/run/squid which is owned by proxy.proxy. The error seems to be in multiple places, also in some autogenerated systemd files for squid.service. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages squid depends on: ii adduser 3.115 ii libc62.24-9 ii libcap2 1:2.25-1 ii libcomerr2 1.43.4-2 ii libdb5.3 5.3.28-12+b1 ii libdbi-perl 1.636-1+b1 ii libecap3 1.0.1-3.2 ii libexpat12.2.0-2 ii libgcc1 1:6.3.0-6 ii libgssapi-krb5-2 1.15-1 ii libkrb5-31.15-1 ii libldap-2.4-22.4.44+dfsg-3 ii libltdl7 2.4.6-2 ii libnetfilter-conntrack3 1.0.6-2 ii libnettle6 3.3-1 ii libpam0g 1.1.8-3.5 ii libsasl2-2 2.1.27~101-g0780600+dfsg-2 ii libstdc++6 6.3.0-6 ii libxml2 2.9.4+dfsg1-2.2 ii logrotate3.11.0-0.1 ii lsb-base 9.20161125 ii netbase 5.4 ii squid-common 3.5.23-1 Versions of packages squid recommends: ii libcap2-bin 1:2.25-1 Versions of packages squid suggests: pn resolvconf pn smbclient pn squid-cgi ii squid-purge 3.5.23-1 ii squidclient 3.5.23-1 ic ufw 0.35-4 pn winbindd -- Configuration Files: /etc/init.d/squid changed [not included] /etc/squid/squid.conf changed [not included] /etc/ufw/applications.d/squid changed [not included] -- no debconf information
Bug#746029: ejabberd: only admin can connect after upgrade
Package: ejabberd Version: 2.1.11-1 Severity: grave Justification: renders package unusable Dear Maintainer, After an apt-get upgrade, no one except admin can connect to the ejabberd server. All users except admin get "Fehler beim Einlesen von XML-Dateien." -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ejabberd depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.52 ii erlang-asn11:17.0-dfsg-1 ii erlang-base [erlang-abi-15.b] 1:17.0-dfsg-1 ii erlang-crypto 1:17.0-dfsg-1 ii erlang-inets 1:17.0-dfsg-1 ii erlang-mnesia 1:17.0-dfsg-1 ii erlang-odbc1:17.0-dfsg-1 ii erlang-public-key 1:17.0-dfsg-1 ii erlang-ssl 1:17.0-dfsg-1 ii erlang-syntax-tools1:17.0-dfsg-1 ii libc6 2.18-4 ii libexpat1 2.1.0-4 ii libpam0g 1.1.8-3 ii libssl1.0.01.0.1g-3 ii openssl1.0.1g-3 ii ucf3.0027+nmu1 ii zlib1g 1:1.2.8.dfsg-1 ejabberd recommends no packages. Versions of packages ejabberd suggests: ii imagemagick 8:6.7.7.10+dfsg-1 pn libunix-syslog-perl -- debconf information: ejabberd/password: (password omitted) ejabberd/verify: (password omitted) ejabberd/user: ejabberd/nomatch: ejabberd/hostname: localhost -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#730086: courier-pop-ssl not able to upgrade: error
Package: courier-pop-ssl Version: 0.68.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? apt-get upgrade * What was the outcome of this action? apt-get is not able to upgrade courier-pop-ssl Holen: 1 http://debian.tu-bs.de/debian/ testing/main courier-pop-ssl amd64 0.68.2-1+b1 [31,0 kB] Es wurden 31,0 kB in 0 s geholt (216 kB/s). Lese Changelogs... Fertig (Lese Datenbank ... 86950 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Ersetzen von courier-pop-ssl 0.68.2-1 (durch .../courier-pop-ssl_0.68.2-1+b1_amd64.deb) ... Stopping Courier POP3-SSL server:/var/run/courier/pop3d-ssl.pid.lock: No such file or directory invoke-rc.d: initscript courier-pop-ssl, action "stop" failed. dpkg: Warnung: Unterprozess altes pre-removal-Skript gab den Fehlerwert 1 zurück dpkg: stattdessen wird Skript aus dem neuen Paket probiert ... Stopping Courier POP3-SSL server:/var/run/courier/pop3d-ssl.pid.lock: No such file or directory invoke-rc.d: initscript courier-pop-ssl, action "stop" failed. dpkg: Fehler beim Bearbeiten von /var/cache/apt/archives/courier-pop-ssl_0.68.2-1+b1_amd64.deb (--unpack): Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück insserv: warning: current start runlevel(s) (empty) of script `courier-pop-ssl' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `courier-pop-ssl' overrides LSB defaults (0 1 6). Fehler traten auf beim Bearbeiten von: /var/cache/apt/archives/courier-pop-ssl_0.68.2-1+b1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.11-2-amd64 (SMP w/1 CPU core) 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 courier-pop-ssl depends on: ii courier-pop 0.68.2-1+b1 ii courier-ssl 0.68.2-1+b1 ii debconf 1.5.52 courier-pop-ssl recommends no packages. Versions of packages courier-pop-ssl suggests: pn courier-doc -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728041: insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `courier-pop-ssl' overrides LSB defaults (0 1 6).
Package: courier-pop-ssl Version: 0.68.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** 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? apt-get upgrade fails at courier-pop-ssl because of: insserv: warning: current start runlevel(s) (empty) of script `courier-pop-ssl' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `courier-pop-ssl' overrides LSB defaults (0 1 6). Fehler traten auf beim Bearbeiten von: /var/cache/apt/archives/courier-pop-ssl_0.68.2-1+b1_amd64.deb *** End of the template - remove these lines *** -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.10-3-amd64 (SMP w/1 CPU core) 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 courier-pop-ssl depends on: ii courier-pop 0.68.2-1+b1 ii courier-ssl 0.68.2-1+b1 ii debconf 1.5.51 courier-pop-ssl recommends no packages. Versions of packages courier-pop-ssl suggests: pn courier-doc -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674996: linkchecker: wrong 404 reports
Package: linkchecker Version: 7.8-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Normal use of linkchecker via command line. linkchecker reports a lot of 404 errors, but when I open the reported URLs manually, everything is fine and the pages open in a browser without an error - so the output of linkchecker is unreliable at the moment, the reported 404 errors are wrong. * 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 lines *** -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/1 CPU core) 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 linkchecker depends on: ii libc6 2.13-32 ii python 2.7.2-10 ii python2.7 2.7.3~rc2-2.1 linkchecker recommends no packages. Versions of packages linkchecker suggests: pn clamav-daemon pn linkchecker-gui pn linkchecker-web pn python-cssutils pn python-gconf pn python-geoip pn python-optcomplete pn python-pysqlite2 pn python-twill pn python-utidylib -- Configuration Files: /etc/linkchecker/linkcheckerrc changed: [output] [text] [gml] [dot] [csv] separator=* [sql] [html] [blacklist] [xml] [gxml] [checking] [filtering] [authentication] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#652070: awstats: virtualname / SiteDomain accepts nearly everything
Package: awstats Version: 7.0~dfsg-3 Severity: grave Justification: renders package unusable Dear Maintainer, *** 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 lines *** - AWstats runs fine for months. - Yesterday apt updated Perl. - Now AWSTats directives %virtualname and SiteDomain accepts nearly all records of the logfile, even with an arbirtray string as SiteDomain, for example SiteDomain="fhawefruzasdfh" -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/1 CPU core) 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 awstats depends on: ii perl 5.14.2-6 Versions of packages awstats recommends: ii coreutils 8.13-3 ii libnet-xwhois-perl 0.90-3 Versions of packages awstats suggests: ii apache2 2.2.21-3 ii apache2-mpm-prefork [httpd] 2.2.21-3 ii libgeo-ipfree-perl ii libnet-dns-perl ii libnet-ip-perl ii liburi-perl 1.59-1 -- Configuration Files: /etc/awstats/awstats.conf changed [not included] /etc/awstats/awstats.conf.local changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#651128: Wrong symbolic link
The problem is caused due to a wrong symbolic link to prototype.js. After correcting this symbolic link, TYPO3 runs fine. Viele Grüße Andreas Rittershofer -- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#651128: typo3: ../. !.Core: Error handler (BE): PHP Warning: filemtime(): stat failed for /var/lib/typo3-dummy/typo3/contrib/prototype/prototype.js in /usr/share/typo3/typo3_src-4.5/t3lib/class.t3
Package: typo3 Version: 4.5.6+dfsg1-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? I wanted to add the first page at root level - this is not possible, see error log. * 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 lines *** -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages typo3 depends on: ii typo3-database 4.5.6+dfsg1-1 ii typo3-dummy 4.5.6+dfsg1-1 ii typo3-src-4.5 4.5.6+dfsg1-1 typo3 recommends no packages. typo3 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#618337: linkchecker: Linkchecker throws a traceback
Package: linkchecker Version: 6.4-1 Severity: grave Justification: renders package unusable Traceback (most recent call last): File "/usr/bin/linkchecker", line 36, in import linkcheck.checker File "/usr/lib/python2.6/dist-packages/linkcheck/checker/__init__.py", line 153, in from . import (fileurl, unknownurl, ftpurl, httpurl, File "/usr/lib/python2.6/dist-packages/linkcheck/checker/fileurl.py", line 29, in from ..bookmarks import firefox ImportError: No module named bookmarks -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) 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 linkchecker depends on: ii libc6 2.11.2-11Embedded GNU C Library: Shared lib ii python 2.6.6-3+squeeze5 interactive high-level object-orie ii python-central 0.6.16+nmu1 register and build utility for Pyt linkchecker recommends no packages. Versions of packages linkchecker suggests: ii apache2 2.2.17-1 Apache HTTP Server metapackage ii apache2-mpm-prefork [httpd] 2.2.17-1 Apache HTTP Server - traditional n pn clamav-daemon (no description available) pn python-cssutils(no description available) pn python-geoip (no description available) pn python-optcomplete (no description available) pn python-pysqlite2 (no description available) pn python-twill (no description available) pn python-utidylib(no description available) -- Configuration Files: /etc/linkchecker/linkcheckerrc changed: [output] [text] [gml] [dot] [csv] separator=* [sql] [html] [blacklist] [xml] [gxml] [checking] [filtering] [authentication] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#452647: lilypond: Speicherzugriffsfehler
Package: lilypond Version: 2.10.29-1 Severity: grave Justification: renders package unusable Yesterday I made an aptitude update aptitude safe-upgrade and now lilypond reports: lilypond: Symbol `scm_i_freelist' has different size in shared object, consider re-linking GNU LilyPond 2.10.29 Speicherzugriffsfehler I cannot use it any more. mfg ar -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.17-rc6 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages lilypond depends on: ii guile-1.8 1.8.3+1-1The GNU extension language and Sch ii guile-1.8-libs 1.8.3+1-1Main Guile libraries ii libc6 2.6.1-6 GNU C Library: Shared libraries ii libfontconfig1 2.5.0-2 generic font configuration library ii libfreetype62.3.5-1+b1 FreeType 2 font engine, shared lib ii libgcc1 1:4.2.2-3GCC support library ii libglib2.0-02.14.3-1 The GLib library of C routines ii libgmp3c2 2:4.2.2+dfsg-1 Multiprecision arithmetic library ii libltdl31.5.24-1 A system independent dlopen wrappe ii libpango1.0-0 1.18.3-1 Layout and rendering of internatio ii libstdc++6 4.2.2-3 The GNU Standard C++ Library v3 ii lilypond-data 2.10.29-1LilyPond music typesetter (data fi ii python 2.4.4-6 An interactive high-level object-o ii zlib1g 1:1.2.3.3.dfsg-7 compression library - runtime Versions of packages lilypond recommends: ii lilypond-doc 2.10.29-1 LilyPond Documentation in HTML, PS -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#421205: typo3: mod_rewrite - problem: internal server error
Package: typo3 Version: 4.0.2+debian-3 Severity: grave Justification: renders package unusable After installing typo3 via aptitude I get in my browser: Internal Server Error The logfile says: mod_rewrite: maximum number of internal redirects reached. Assuming configuration error. Use "RewriteOptions MaxRedirects" to increase the limit if neccessary. But this seems not to be the problem, which I assume is a loop in the redirects. mfg ar -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.4.27-2-386 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages typo3 depends on: ii graphicsmagick 1.1.7-13collection of image processing too ii php4-gd 6:4.4.4-8+etch1 GD module for php4 ii sendmail-bin [mail-trans 8.13.4-3sarge3 powerful, efficient, and scalable ii typo3-dummy 4.0.2-2 Empty TYPO3 site package for start ii typo3-src-4.04.0.2+debian-3 Powerful content management framew -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#303872: lilypond-data: broken dependencies
Package: lilypond-data Version: 2.4.5-1 Severity: grave Justification: renders package unusable Today I got with apt-get update and apt-get upgrade a new lilypond-data, but this removed lilypond itself. So now I have an actual lilypond-data, but no lilypond - the package is unusable. mfg ar -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.25 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages lilypond-data depends on: ii tetex-bin 2.0.2-28 The teTeX binary files -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
