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
with
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:
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 Releas
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/debia
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
ineffect
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
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)?
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-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
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
l
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
Package: guile-1.8
Version: 1.8.3+1-1
Severity: normal
Starting lilypond ends in:
lilypond: Symbol `scm_i_freelist' has different size in shared object, consider
re-linking
GNU LilyPond 2.10.29
Speicherzugriffsfehler
So lilypond is completely unusable at the moment.
mfg ar
-- System Inform
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
Speic
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
"RewriteO
Package: k3b
Version: 0.12.12-1
Followup-For: Bug #353826
A few days ago I updated my kernel from 2.4 to 2.6 and now my
k3bsetup-window is empty and not usable.
k3b complains about some rights of cdrdao and suggests to run k3bsetup,
but k3bsetup is not usable.
mfg ar
-- System Information:
D
Am Sonntag, den 10.04.2005, 18:59 -0700 schrieb Thomas Bushnell BSG:
> Andreas Rittershofer <[EMAIL PROTECTED]> writes:
>
> > Am Sonntag, den 10.04.2005, 09:02 -0400 schrieb Daniel Burrows:
> >> On Sunday 10 April 2005 03:55 am, Andreas Rittershofer wrote:
> >>
Am Sonntag, den 10.04.2005, 09:02 -0400 schrieb Daniel Burrows:
> On Sunday 10 April 2005 03:55 am, Andreas Rittershofer wrote:
> > Fehler: Falsche lilypond-Version: 2.1.36 (2.3.22, 2.4.5)
>
> I believe it's telling you that there's a \version "2.1.36" comma
lilypond-book generates *.ly-files in the
lilypond-book-output-directory.
But when I try manually to start lilypond with one of these generated
files I get:
GNU LilyPond 2.4.5
Processing `lily-1008508509.ly'
Analysiere...
Fehler: Falsche lilypond-Version: 2.1.36 (2.3.22, 2.4.5)
Fehler: Erwägen Si
Package: lilypond
Version: 2.4.5-2
Severity: normal
lilypond-book does not work correctly:
A part of my output is:
At the beginning:
/usr/bin/lilypond-book (GNU LilyPond) 2.4.5
Ãffne Pipe `kpsexpand \$TEXMF'
Ãffne Pipe `kpsewhich -expand-path=\$T1FONTS'
drums.lytex lesen...
Zerlegen...
Ãffne F
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
--
Package: lilypond
Version: 2.2.6-3
Severity: wishlist
With apt-get I get version 2.2.6 in testing debian, the actual version
on the lilypond homepage is 2.4.2. Why is the apt-get version so old?
mfg ar
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstab
20 matches
Mail list logo
