Bug#855287: varnish: change of listening port without effect

2017-02-16 Thread Andreas Rittershofer
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

Bug#855268: squid: PID file at wrong place -> not installable

2017-02-16 Thread Andreas Rittershofer
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

Bug#746029: ejabberd: only admin can connect after upgrade

2014-04-27 Thread Andreas Rittershofer
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

Bug#730086: courier-pop-ssl not able to upgrade: error

2013-11-20 Thread Andreas Rittershofer
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

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).

2013-10-27 Thread Andreas Rittershofer
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

Bug#674996: linkchecker: wrong 404 reports

2012-05-29 Thread Andreas Rittershofer
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

Bug#652070: awstats: virtualname / SiteDomain accepts nearly everything

2011-12-14 Thread Andreas Rittershofer
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)?

Bug#651128: Wrong symbolic link

2011-12-06 Thread Andreas Rittershofer
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

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

2011-12-05 Thread Andreas Rittershofer
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

Bug#618337: linkchecker: Linkchecker throws a traceback

2011-03-14 Thread Andreas Rittershofer
Package: linkchecker Version: 6.4-1 Severity: grave Justification: renders package unusable Traceback (most recent call last): File /usr/bin/linkchecker, line 36, in module import linkcheck.checker File /usr/lib/python2.6/dist-packages/linkcheck/checker/__init__.py, line 153, in module

Bug#452647: lilypond: Speicherzugriffsfehler

2007-11-24 Thread Andreas Rittershofer
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

Bug#421205: typo3: mod_rewrite - problem: internal server error

2007-04-27 Thread Andreas Rittershofer
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