Bug#704738: squid3: @DEFAULT_CONFIG_FILE@ not replaced
Package: squid3 Version: 3.1.6-1.2+squeeze3 Severity: minor In the manual page of squid3 is @DEFAULT_CONFIG_FILE@ not replaced when the package is build. The same for @DEFAULT_MIME_TABLE@ and @DEFAULT_ERROR_DIR@ -- System Information: Debian Release: 6.0.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_NL.utf8, LC_CTYPE=nl_NL.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages squid3 depends on: ii adduser3.112+nmu2add and remove users and groups ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libcap21:2.19-3 support for getting/setting POSIX. ii libcomerr2 1.41.12-4stable1 common error description library ii libdb4.8 4.8.30-2 Berkeley v4.8 Database Libraries [ ii libexpat1 2.0.1-7+squeeze1 XML parsing C library - runtime li ii libgcc11:4.4.5-8 GCC support library ii libgssapi-krb5-2 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - k ii libk5crypto3 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - C ii libkrb5-3 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.23-7.3OpenLDAP libraries ii libltdl7 2.2.6b-2 A system independent dlopen wrappe ii libpam0g 1.1.1-6.1+squeeze1Pluggable Authentication Modules l ii libsasl2-2 2.1.23.dfsg1-7Cyrus SASL - authentication abstra ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii libxml22.7.8.dfsg-2+squeeze7 GNOME XML library ii logrotate 3.7.8-6 Log rotation utility ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii netbase4.45 Basic TCP/IP networking system ii squid3-common 3.1.6-1.2+squeeze3A full featured Web Proxy cache (H squid3 recommends no packages. Versions of packages squid3 suggests: pn resolvconfnone (no description available) ii smbclient 2:3.5.6~dfsg-3squeeze9 command-line SMB/CIFS clients for pn squid-cgi none (no description available) pn squidclient none (no description available) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#496800: [pkg-mono-group] Bug#496800: Bug#496800: dependency problem between mono and mono-common and mono-jit
Hallo, Mono-devel 1.2.5.1-1+lenny1, which has a dependency to mono 1.2.5.1-1+lenny1, should be removed then also to prevent the same problems. Yours sincerely, Frans Luteijn. Xout Europe BV De Virieusingel 4 P.O. Box 223 5300 AE Zaltbommel The Netherlands P: +31(0)88 77 88 200 F: +31(0)88 77 88 299 E: [EMAIL PROTECTED] W: www.xout.eu Jo Shields wrote: On Wed, 2008-08-27 at 17:50 +0200, Frans Luteijn wrote: It is a fresh install without any old dependicies. When I select mono I don't expect such dependicy problems which cannot normally be solved. It should normally be build with the right version or it should not be in the repository. You're right. It should not. And it's NOT a problem in Lenny, which does not contain any binary package called mono, nor a problem with the Debian Mono packages, which haven't produced a mono binary for a long time. The problem lies in testing-security, which uploaded a security update in November 2007 to security.debian.org - which was superceded 2 weeks later. We (the Mono team) have no ability to remove the obsolete problem package from the FTP servers. We have now opened a bug against ftp.debian.org, at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496806 - That's the place to target complaints about this problem, which are completely beyond our control.
Bug#496800: [pkg-mono-group] Bug#496800: dependency problem between mono and mono-common and mono-jit
It is a fresh install without any old dependicies. When I select mono I don't expect such dependicy problems which cannot normally be solved. It should normally be build with the right version or it should not be in the repository. Met vriendelijke groet, Frans Luteijn. Xout Europe BV De Virieusingel 4 P.O. Box 223 5300 AE Zaltbommel The Netherlands P: +31(0)88 77 88 200 F: +31(0)88 77 88 299 E: [EMAIL PROTECTED] W: www.xout.eu Jo Shields wrote: On Wed, 2008-08-27 at 16:48 +0200, F. Luteijn wrote: Package: mono Version: 1.2.5.1-1+lenny1 Severity: normal Mono is dependent on mono-common (= 1.2.5.1-1+lenny1) and mono-jit (= 1.2.5.1-1+lenny1), but those packages are not available. Installing mono (and mono-dev also) will fail and installing mono-common or mono-jit will remove mono. Remove mono. It's a useless metapackage which was removed ages ago - and is still causing us problems like this because there appears to be no mechanism for removing obsolete packages from testing-security.
Bug#368269: quagga: ripd does not update routing table with propagated routes
Christian Hammers schreef: severity 368269 normal tags 368269 + moreinfo thanks Hello On 2006-05-21 F.A.G. Luteijn wrote: After upgrading to 0.98.3-7.2 all propagated routes are not imported into the routingtable. I downgraded to 0.98.3-7 and I have got the routes of my firewall back. After upgrading again I have lost those routes again. Routes are propagated correctly, but not picked up. Have you rebooted the system after upgrading? Just to be sure.. No, I didn't. But that should not make any difference. I only reboot a computer when I change the kernel. But I had a power failure last week, so everything has been booted up cleanly. And that didn't change anything. Do you use RIP authentication? No, I don't. I do not use any authentication. I have attached my conf-files and as you can see, they are quite straightforward. Maybe you're affected by a config / behaviour change due to the security update. Please take a look at the Release Notes or in http://bugzilla.quagga.net/show_bug.cgi?id=262 At least there were no further problem reports on Quagga+RIP after the security update. As I understand, you have changed the defaults for authentication. I hardly believe, that changing those defaults solve any of the security issues that were solved here. I even think it is a breach of the policy for security-updates. (See also Securing Debian Manual, 12.3.4: http://www.debian.org/doc/manuals/securing-debian-howto/ch12.en.html#s12.3.4) bye, -christian- I hope, I have answered your questions, Yours sincerely, -- Frans Luteijn PGP PblKey fprnt=C4 87 CE AF BC B6 98 C1 EF 42 A1 9A E2 C0 42 5B GPG PblKey fprnt=ED20 0F25 C233 DC59 3FFA 170E D0BF 15F5 0BA6 1355 ! -*- rip -*- ! ! RIPd sample configuration file ! ! $Id: ripd.conf.sample,v 1.11 1999/02/19 17:28:42 developer Exp $ ! hostname ripd password 8 cbxcypPiMhZdk enable password 8 7i2T7CpNFqGLc service password-encryption ! ! debug rip events ! debug rip packet ! router rip # default-information originate network 172.19.0.0/16 network 192.168.1.0/24 network 192.168.2.0/24 network 192.168.3.0/24 redistribute connected ! network 11.0.0.0/8 ! network eth0 ! route 10.0.0.0/8 ! distribute-list private-only in eth0 ! !access-list private-only permit 10.0.0.0/8 !access-list private-only deny any access-list local permit 127.0.0.0/8 access-list local permit 192.168.2.0/24 access-list local deny any ! line vty access-class local ! !log stdout ! log file /var/log/quagga/ripd.log ! -*- rip -*- ! ! RIPd sample configuration file ! ! $Id: ripd.conf.sample,v 1.11 1999/02/19 17:28:42 developer Exp $ ! hostname ripd ! password zebra ! ! debug rip events ! debug rip packet ! router rip network 192.168.2.0/24 ! network 11.0.0.0/8 ! network eth0 ! route 10.0.0.0/8 ! distribute-list private-only in eth0 ! !access-list private-only permit 10.0.0.0/8 !access-list private-only deny any access-list local permit 127.0.0.0/8 ! line vty access-class local ! !log stdout ! log file /var/log/quagga/ripd.log
Bug#300824: [Pkg-nagios-devel] Bug#300824: nagios-common: nagios won't start with --nicelevel option
sean finney schreef: tags 300824 unreproducible thanks hi, On Tue, Mar 22, 2005 at 03:43:36AM +0100, F.A.G. Luteijn wrote: Nagios will not start with the option --nicelevel $NICENESS i can't reproduce this. could you send the output of sh -x /etc/init.d/nagios start ? thanks. sean -- Name: signature.asc signature.asc Type: application/pgp-signature Description: Digital signature I've done as you requested. The result is in the first attached file. The result of the command 'ps -ef|grep nagios' after executing the first file is the following: nobody8277 1 0 Mar22 ?00:02:52 /usr/bin/python /usr/sbin/nagios-statd --pid=/var/run/nagios-statd.pid root 25764 25615 0 00:54 pts/000:00:00 grep nagios After executing the second file the result of the same command is: nobody8277 1 0 Mar22 ?00:02:52 /usr/bin/python /usr/sbin/nagios-statd --pid=/var/run/nagios-statd.pid nagios 25790 1 0 00:56 ?00:00:00 /usr/sbin/nagios /etc/nagios/nagios.cfg root 25837 25615 0 00:57 pts/000:00:00 grep nagios I have also changed the --quiet option with the --verbose option. See the result in the third attached file. I have come to the conclusion, that the problem might be in start-stop-daemon. The version of dpkg (which start-stop-daemon is part of) is 1.9.21. Yours sincerely, -- Frans Luteijn PGP PblKey fprnt=C4 87 CE AF BC B6 98 C1 EF 42 A1 9A E2 C0 42 5B GPG PblKey fprnt=ED20 0F25 C233 DC59 3FFA 170E D0BF 15F5 0BA6 1355 NAGIOS1.TXT Description: application/unknown-content-type-txtfile NAGIOS2.TXT Description: application/unknown-content-type-txtfile NAGIOS3.TXT Description: application/unknown-content-type-txtfile
Bug#263388: [Fwd: [ISC-Bugs #12140] Ticket Resolved]
I've got this reply from ISC. I have been unable to test it, so I don't know if it is realy fixed Yours sincerely, -- Frans Luteijn PGP PblKey fprnt=C4 87 CE AF BC B6 98 C1 EF 42 A1 9A E2 C0 42 5B GPG PblKey fprnt=ED20 0F25 C233 DC59 3FFA 170E D0BF 15F5 0BA6 1355 ---BeginMessage--- According to our records, your request: [ISC-Bugs #12140]: Bind saves faulty cachefile and cannot be started again has been resolved. If you have any further questions or concerns, please respond to this message. ---End Message---
