Bug#396178: fixed

Hi, this is fixed in svn, see http://lists.alioth.debian.org/pipermail/pkg-cyrus-sasl2-debian-devel/2006-October/000285.html and http://lists.alioth.debian.org/pipermail/pkg-cyrus-sasl2-commits/2006-October/99.html Just wait for the next release. bye, Martin -- Powered by Debian GNU / Linu

Bug#381549: Brand new install of jwchat fails post-installation script

Hi Philip, Philip Craig wrote: > Package: jwchat > Version: 1.0beta2-6 > Severity: grave > Justification: renders package unusable > /var/lib/dpkg/info/jwchat.postinst: line 37: a2enmod: command not found > Versions of packages jwchat depends on: > ii apache [httpd]1.3.34-2 ve

Bug#325285: any news on this bug?

Hi, I just noticed this bug and I'm asking if there is any process? Will there be a fix for sarge? bye, Martin -- Powered by Debian GNU Linux http://blog.mein-horde.de signature.asc Description: OpenPGP digital signature

Bug#358812: CVE-2006-1260: File disclosure vulnerability

Moritz Muehlenhoff wrote: > Could you check, whether Horde 3.0.4 and 2.2.8 from stable are affected? Both are affected (for horde2 the file can be found in horde/util ). bye, Martin -- Powered by Debian GNU / Linux signature.asc Description: OpenPGP digital signature

Bug#348148: gksu: depend on non existing package

Steve Langasek wrote: > Very strange. What does 'apt-cache policy gconf2' show? Does apt-get > update change anything? > client:/home/blackm# apt-cache policy gconf2 gconf2: Installed: (none) Candidate: (none) Package pin: (not found) Version table: 2.12.1-8 1000 500 ftp://

Bug#348148: gksu: depend on non existing package

Steve Langasek wrote: > On Sun, Jan 15, 2006 at 11:17:22AM +0100, Martin Lohmeier wrote: > >>Package: gksu >>Version: 1.3.6-1 >>Severity: grave >>Justification: renders package unusable > > >>gksu depend on gconf2 which has been replaced by gconf2-co

Bug#348148: gksu: depend on non existing package

Package: gksu Version: 1.3.6-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 gksu depend on gconf2 which has been replaced by gconf2-common. bye, Martin - -- System Information: Debian Release: testing/unstable APT prefers unstable APT

Bug#340900: Missing README.Debian file

Graham Seaman wrote: > Apologies for this. I fired off that email too quickly. The file does > exist, it's just gzipped. > Please cancel the other bugreport you made for this. > > Sorry... > Graham Let the report open and just change the comment in /etc/horde/horde3/conf.php to "/usr/share/doc/ho

Bug#340900: kronolith: saves but does not display events

Graham Seaman wrote: > What's the best way to go from here? Do I need to start installing > packages from testing? I've had a look, and appear to have the usual > cascade of dependencies (testing version of pear, etc), which will > effectively > convert my system from stable to testing, which I wo

Bug#340900: kronolith: saves but does not display events

Graham Seaman wrote: > I am running the horde on a server running debian stable, used for > several different virtual hosts. I've previously had problems when I've > tried to include large packages with many dependencies from testing or > unstable on a system like this. If you could give me some g

Bug#332290: horde3: Application is in a severely insecure state during configuration

Mike O'Connor wrote: > Package: horde3 > Version: 3.0.5-1 > Severity: critical > Tags: security > Justification: root security hole > > As part of the installation procedure in README.Debian, you are told to > configure horde3 via a web interface. This is done using an > Administrator account whi

Bug#332289: permissions on /etc/horde/horde3/* are too lax

Mike O'Connor wrote: > Package: horde3 > Version: 3.0.5-1 > Severity: critical > Tags: security > Justification: root security hole > > In the README.Debian, in section 6. it is recommended that the end > user executes: > > chown root.www config/* > chmod 0440 config/* > > bec

Bug#311776: More info please

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Jens, I tryed to reproduce this, but failed (it's working here). Can you give some more infos (your httpd.conf, .htaccess & password file,...) by, Martin - -- Powered by Debian GNU / Linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU

Bug#311514: This bug is not grave

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: kopete Version: 3.3.2-5 Severity: normal Hi Krisztian, this is no grave bug, since grace mean: makes the package in question unusable or mostly so, or causes data loss, or introduces a security hole allowing acces

Bug#311202: ttthreeparser: confirm the FTBFS

Package: ttthreeparser Followup-For: Bug #311202 Hi, building this package also fails here, but the error is different: [...] make[1]: Entering directory `/usr/src/ttthreeparser/ttthreeparser-1.4' Translating TTCN3Lexer.g ANTLR Parser Generator Version 2.7.2 1989-2003 jGuru.com Translating T

Bug#301590: lirc-modules-source: does not accept kernel source

Package: lirc-modules-source Version: 0.7.1pre2-3 Severity: grave Justification: renders package unusable Hi, the packages does not automaticly build with linux 2.6.11 I have the source of my current kernel in /usr/src/linux, but after configuring lirc-modules-source, he complains /usr/src/l

Bug#297323: run apt-get build-dep blitz++

Package: blitz++ Version: 1:0.8-3 Followup-For: Bug #297323 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, run apt-get build-dep blitz++ before you try to build the package. This installed g77 here. by, Martin - -- System Information: Debian Release: 3.1 APT prefers testing APT pol

Bug#291031: postfix: Upgrade from Postfix 2.1.4-5 to 2.1.5-4 fails #3

Package: postfix Version: 2.1.5-4 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, when updating postfix I got the following error: Running newaliases postalias: fatal: dict_mkmap_func: unsupported dictionary type: mysql does not allow m