Processed: Re: Bug#379904: heartbeat: Local DoS due to world-writable shared memory [CVE-2006-3815]
Processing commands for [EMAIL PROTECTED]: > notfound 379904 1.2.3-9sarge5 Bug#379904: heartbeat: Local DoS due to world-writable shared memory [CVE-2006-3815] Bug marked as not found in version 1.2.3-9sarge5. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#379584: FTBFS: autoconf missing
package webalizer tags 379584 +patch quit With a non-empty file, life is better ;) Shame on me -- MBdC diff -ruN webalizer-2.01.10/debian/control webalizer-2.01.10-patch/debian/control --- webalizer-2.01.10/debian/control 2006-07-29 05:55:32.0 +0200 +++ webalizer-2.01.10-patch/debian/control 2006-07-29 04:51:52.0 +0200 @@ -3,7 +3,7 @@ Section: web Maintainer: Jose Carlos Medeiros <[EMAIL PROTECTED]> Uploaders: Ola Lundqvist <[EMAIL PROTECTED]> -Build-Depends: debhelper (>= 4.1.16), libgd2-noxpm-dev, libttf-dev, libpng12-dev, libdb4.2-dev, libgd2-noxpm, libttf2, zlib1g-dev, gettext, po-debconf, autotools-dev, libgeoip-dev, dpatch +Build-Depends: debhelper (>= 4.1.16), libgd2-noxpm-dev, libttf-dev, libpng12-dev, libdb4.2-dev, libgd2-noxpm, libttf2, zlib1g-dev, gettext, po-debconf, autotools-dev, libgeoip-dev, dpatch, autoconf Standards-Version: 3.7.2 Package: webalizer
Processed: FTBFS: autoconf missing
Processing commands for [EMAIL PROTECTED]: > package webalizer Ignoring bugs not assigned to: webalizer > tags 379584 +patch Bug#379584: FTBFS: missing autoconf Tags were: patch Tags added: patch > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: FTBFS: autoconf missing
Processing commands for [EMAIL PROTECTED]: > package webalizer Ignoring bugs not assigned to: webalizer > tags 379584 +patch Bug#379584: FTBFS: missing autoconf There were no tags set. Tags added: patch > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#379584: FTBFS: autoconf missing
package webalizer tags 379584 +patch quit Here's a trivial patch for the issue. -- MBdC
Bug#374946: cupsys: 1.2.1-3 does not work: Perhaps it's the config file?
Kenshi, It seems that this bug is caused by some default in the cupsd.conf file. I didn't change the original conf file, and installation of newer cups would overwrite the old cupsd.conf and install the new one at every upgrade. This time I made sure the old conf file stays in place after the upgrade, and now everything works fine after upgrade to cupsys 1.2.2-1. I attach my conf file (the old one, which came with version 1.2.1-2, the one that works fine for me) below in hope you can figure out what was going on. I'll play with this a little bit more myself... Cheers, Slaven # # # Sample configuration file for the Common UNIX Printing System (CUPS) # scheduler. See "man cupsd.conf" for a complete description of this # file. # # Log general information in error_log - change "info" to "debug" for # troubleshooting... LogLevel debug # Administrator user group... SystemGroup lpadmin # Only listen for connections from the local machine. # These settings are configured in /etc/cups/cups.d/ports.conf so that # changing them does not require to change this file. # Listen localhost:631 # Listen /var/run/cups/cups.sock # Show shared printers on the local network. # The 'Browsing' setting is configured in /etc/cups/cups.d/browse.conf # so that changing it does not require to change this file. # Browsing Off BrowseOrder allow,deny BrowseAllow @LOCAL BrowseAddress @LOCAL # Default authentication type, when authentication is required... DefaultAuthType Basic # Restrict access to the server... Order allow,deny Allow localhost # Restrict access to the admin pages... Encryption Required Order allow,deny Allow localhost # Restrict access to configuration files... AuthType Basic Require user @SYSTEM Order allow,deny Allow localhost # Set the default printer/job policies... # Job-related operations must be done by the owner or an adminstrator... Require user @OWNER @SYSTEM Order deny,allow # All administration operations require an adminstrator to authenticate... AuthType Basic Require user @SYSTEM Order deny,allow # Only the owner or an administrator can cancel or authenticate a job... Require user @OWNER @SYSTEM Order deny,allow Order deny,allow # Include files in /etc/cups/conf.d Port 631 Browsing on # #
Processed: Re: Bug#379571: jabref: FTBFS: [javac] The import sun.misc cannot be resolved
Processing commands for [EMAIL PROTECTED]: > tags 379571 unreproducible Bug#379571: jabref: FTBFS: [javac] The import sun.misc cannot be resolved There were no tags set. Tags added: unreproducible > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#375660: marked as done (libwww-myspace-perl: missing dependencies on libwww-mechanize-perl and libconfig-general-perl)
Your message dated Fri, 28 Jul 2006 17:17:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#375660: fixed in libwww-myspace-perl 0.48-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: libwww-myspace-perl Version: 0.48-1 Severity: grave Justification: renders package unusable missing dependencies. Please read the documentation carefully and ensure that they are declared. thanks. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages libwww-myspace-perl depends on: ii perl 5.8.8-6Larry Wall's Practical Extraction libwww-myspace-perl recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libwww-myspace-perl Source-Version: 0.48-2 We believe that the bug you reported is fixed in the latest version of libwww-myspace-perl, which is due to be installed in the Debian FTP archive: libwww-myspace-perl_0.48-2.diff.gz to pool/main/libw/libwww-myspace-perl/libwww-myspace-perl_0.48-2.diff.gz libwww-myspace-perl_0.48-2.dsc to pool/main/libw/libwww-myspace-perl/libwww-myspace-perl_0.48-2.dsc libwww-myspace-perl_0.48-2_all.deb to pool/main/libw/libwww-myspace-perl/libwww-myspace-perl_0.48-2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Moreno Garza <[EMAIL PROTECTED]> (supplier of updated libwww-myspace-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 24 Jul 2006 20:56:26 -0500 Source: libwww-myspace-perl Binary: libwww-myspace-perl Architecture: source all Version: 0.48-2 Distribution: unstable Urgency: low Maintainer: David Moreno Garza <[EMAIL PROTECTED]> Changed-By: David Moreno Garza <[EMAIL PROTECTED]> Description: libwww-myspace-perl - Access MySpace.com profile information from Perl Closes: 375659 375660 375661 375666 Changes: libwww-myspace-perl (0.48-2) unstable; urgency=low . * Adding missing runtime dependencies (Closes: #375659, #375660, #375661, #375666). Files: b671aad6195128c9ea2f6372d244247a 997 perl optional libwww-myspace-perl_0.48-2.dsc d9e4442562151582511fdafae88d5002 2361 perl optional libwww-myspace-perl_0.48-2.diff.gz e972128d3e7d6402a5b8b9bd716b7c31 169386 perl optional libwww-myspace-perl_0.48-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEyqYGmBxf18ZxJX0RAmXOAJ91sXrObjvA9FO0TmbvEZK+OCJ4ygCcDCpn pblfZzWa77qlfCXbmo/SbB0= =F/v4 -END PGP SIGNATURE- --- End Message ---
Bug#375659: marked as done (libwww-myspace-perl: missing dependency on libspiffy-perl (for Spiffy.pm))
Your message dated Fri, 28 Jul 2006 17:17:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#375659: fixed in libwww-myspace-perl 0.48-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: libwww-myspace-perl Version: 0.48-1 Severity: grave Justification: renders package unusable the libwww-myspace-perl package is missing a dependency on either libspiffy-perl or libclass-spiffy-perl... i'm not sure which actually provides Spiffy.pm, but libwww-myspace-perl can't find it. thanks. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages libwww-myspace-perl depends on: ii perl 5.8.8-6Larry Wall's Practical Extraction libwww-myspace-perl recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libwww-myspace-perl Source-Version: 0.48-2 We believe that the bug you reported is fixed in the latest version of libwww-myspace-perl, which is due to be installed in the Debian FTP archive: libwww-myspace-perl_0.48-2.diff.gz to pool/main/libw/libwww-myspace-perl/libwww-myspace-perl_0.48-2.diff.gz libwww-myspace-perl_0.48-2.dsc to pool/main/libw/libwww-myspace-perl/libwww-myspace-perl_0.48-2.dsc libwww-myspace-perl_0.48-2_all.deb to pool/main/libw/libwww-myspace-perl/libwww-myspace-perl_0.48-2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Moreno Garza <[EMAIL PROTECTED]> (supplier of updated libwww-myspace-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 24 Jul 2006 20:56:26 -0500 Source: libwww-myspace-perl Binary: libwww-myspace-perl Architecture: source all Version: 0.48-2 Distribution: unstable Urgency: low Maintainer: David Moreno Garza <[EMAIL PROTECTED]> Changed-By: David Moreno Garza <[EMAIL PROTECTED]> Description: libwww-myspace-perl - Access MySpace.com profile information from Perl Closes: 375659 375660 375661 375666 Changes: libwww-myspace-perl (0.48-2) unstable; urgency=low . * Adding missing runtime dependencies (Closes: #375659, #375660, #375661, #375666). Files: b671aad6195128c9ea2f6372d244247a 997 perl optional libwww-myspace-perl_0.48-2.dsc d9e4442562151582511fdafae88d5002 2361 perl optional libwww-myspace-perl_0.48-2.diff.gz e972128d3e7d6402a5b8b9bd716b7c31 169386 perl optional libwww-myspace-perl_0.48-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEyqYGmBxf18ZxJX0RAmXOAJ91sXrObjvA9FO0TmbvEZK+OCJ4ygCcDCpn pblfZzWa77qlfCXbmo/SbB0= =F/v4 -END PGP SIGNATURE- --- End Message ---
Bug#375661: marked as done (libwww-myspace-perl: missing dependency on libcontextual-return-perl)
Your message dated Fri, 28 Jul 2006 17:17:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#375661: fixed in libwww-myspace-perl 0.48-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: libwww-myspace-perl Version: 0.48-1 Severity: grave Justification: renders package unusable missing dependency on libcontextual-return-perl please resolve by declaring, thanks. --elijah -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages libwww-myspace-perl depends on: ii perl 5.8.8-6Larry Wall's Practical Extraction libwww-myspace-perl recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libwww-myspace-perl Source-Version: 0.48-2 We believe that the bug you reported is fixed in the latest version of libwww-myspace-perl, which is due to be installed in the Debian FTP archive: libwww-myspace-perl_0.48-2.diff.gz to pool/main/libw/libwww-myspace-perl/libwww-myspace-perl_0.48-2.diff.gz libwww-myspace-perl_0.48-2.dsc to pool/main/libw/libwww-myspace-perl/libwww-myspace-perl_0.48-2.dsc libwww-myspace-perl_0.48-2_all.deb to pool/main/libw/libwww-myspace-perl/libwww-myspace-perl_0.48-2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Moreno Garza <[EMAIL PROTECTED]> (supplier of updated libwww-myspace-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 24 Jul 2006 20:56:26 -0500 Source: libwww-myspace-perl Binary: libwww-myspace-perl Architecture: source all Version: 0.48-2 Distribution: unstable Urgency: low Maintainer: David Moreno Garza <[EMAIL PROTECTED]> Changed-By: David Moreno Garza <[EMAIL PROTECTED]> Description: libwww-myspace-perl - Access MySpace.com profile information from Perl Closes: 375659 375660 375661 375666 Changes: libwww-myspace-perl (0.48-2) unstable; urgency=low . * Adding missing runtime dependencies (Closes: #375659, #375660, #375661, #375666). Files: b671aad6195128c9ea2f6372d244247a 997 perl optional libwww-myspace-perl_0.48-2.dsc d9e4442562151582511fdafae88d5002 2361 perl optional libwww-myspace-perl_0.48-2.diff.gz e972128d3e7d6402a5b8b9bd716b7c31 169386 perl optional libwww-myspace-perl_0.48-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEyqYGmBxf18ZxJX0RAmXOAJ91sXrObjvA9FO0TmbvEZK+OCJ4ygCcDCpn pblfZzWa77qlfCXbmo/SbB0= =F/v4 -END PGP SIGNATURE- --- End Message ---
Bug#379571: jabref: FTBFS: [javac] The import sun.misc cannot be resolved
tags 379571 unreproducible thanks On Mon, 24 Jul 2006 13:13:19 +0200, Andreas Jochens wrote: [Sorry for the late reply, I've been on holidays and mostly offline last week.] > When building 'jabref' in a clean i386/unstable chroot, > I get the following error: > > # apt-get build-dep jabref > [...] > # dpkg-buildpackage -b > [...] > [javac] 324. ERROR in > /root/jabref-2.0.1+2.1b2/src/java/net/sf/jabref/expor$ > [javac] (at line 3) > [javac] import sun.misc.CharacterEncoder; > [javac] > [javac] The import sun.misc cannot be resolved > Thanks for your bug report! I have to admit that I'm a little surprised because I have built the package in a clean (pbuilder) chroot without problems (after enabling the debconf questions, otherwise Sun Java doesn't work). To make sure I tried it again right now and it still works. I guess from your error message that you compiled it with some other java compiler, which does not work. Could you please try again after making sure that you either have Sun Java in your chroot or non-free in the relevant sources.list and debconf not set to noninteractive. If it still doesn't work for me please send me the complete output of the commands. Cheers, gregor -- .''`. http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4 : :' : debian: the universal operating system - http://www.debian.org/ `. `' member of https://www.vibe.at/ | how to reply: http://got.to/quote/ `-NP: Dave Brubeck: It's A Raggy Waltz signature.asc Description: Digital signature
Bug#375666: marked as done (libwww-myspace-perl: please declare dependency on liblocale-subcountry-perl)
Your message dated Fri, 28 Jul 2006 17:17:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#375666: fixed in libwww-myspace-perl 0.48-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: libwww-myspace-perl Version: 0.48-1 Severity: grave Justification: renders package unusable please declare dependencies on liblocale-subcountry-perl for libwww-myspace-perl. it doesn't work without it. thanks. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages libwww-myspace-perl depends on: ii perl 5.8.8-6Larry Wall's Practical Extraction libwww-myspace-perl recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libwww-myspace-perl Source-Version: 0.48-2 We believe that the bug you reported is fixed in the latest version of libwww-myspace-perl, which is due to be installed in the Debian FTP archive: libwww-myspace-perl_0.48-2.diff.gz to pool/main/libw/libwww-myspace-perl/libwww-myspace-perl_0.48-2.diff.gz libwww-myspace-perl_0.48-2.dsc to pool/main/libw/libwww-myspace-perl/libwww-myspace-perl_0.48-2.dsc libwww-myspace-perl_0.48-2_all.deb to pool/main/libw/libwww-myspace-perl/libwww-myspace-perl_0.48-2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Moreno Garza <[EMAIL PROTECTED]> (supplier of updated libwww-myspace-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 24 Jul 2006 20:56:26 -0500 Source: libwww-myspace-perl Binary: libwww-myspace-perl Architecture: source all Version: 0.48-2 Distribution: unstable Urgency: low Maintainer: David Moreno Garza <[EMAIL PROTECTED]> Changed-By: David Moreno Garza <[EMAIL PROTECTED]> Description: libwww-myspace-perl - Access MySpace.com profile information from Perl Closes: 375659 375660 375661 375666 Changes: libwww-myspace-perl (0.48-2) unstable; urgency=low . * Adding missing runtime dependencies (Closes: #375659, #375660, #375661, #375666). Files: b671aad6195128c9ea2f6372d244247a 997 perl optional libwww-myspace-perl_0.48-2.dsc d9e4442562151582511fdafae88d5002 2361 perl optional libwww-myspace-perl_0.48-2.diff.gz e972128d3e7d6402a5b8b9bd716b7c31 169386 perl optional libwww-myspace-perl_0.48-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEyqYGmBxf18ZxJX0RAmXOAJ91sXrObjvA9FO0TmbvEZK+OCJ4ygCcDCpn pblfZzWa77qlfCXbmo/SbB0= =F/v4 -END PGP SIGNATURE- --- End Message ---
Bug#379904: heartbeat: Local DoS due to world-writable shared memory [CVE-2006-3815]
On Wed, Jul 26, 2006 at 11:18:57AM +0200, Martin Pitt wrote: > Package: heartbeat > Version: 1.2.4-12 > Severity: grave > Tags: security patch > > Hi! > > Recently, a local DoS due to world-writable/readable shared memory > permissions was found and fixed in heartbeat: > > Upstream fix: > > > http://cvs.linux-ha.org/viewcvs/viewcvs.cgi/linux-ha/heartbeat/heartbeat.c?r1=1.513&r2=1.514 > > This has been assigned CVE-2006-3815. Please mention this number in > the changelog when you fix this to ease tracking. Thanks, I will get a new relase out for this. Though it probably will not be until next week. -- Horms H: http://www.vergenet.net/~horms/ W: http://www.valinux.co.jp/en/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#379904: heartbeat: Local DoS due to world-writable shared memory [CVE-2006-3815]
Processing commands for [EMAIL PROTECTED]: > clone 379904 -1 Bug#379904: heartbeat: Local DoS due to world-writable shared memory [CVE-2006-3815] Bug 379904 cloned as bug 380289. > reassign -1 heartbeat-2 Bug#380289: heartbeat: Local DoS due to world-writable shared memory [CVE-2006-3815] Bug reassigned from package `heartbeat' to `heartbeat-2'. > retitle -1 heartbeat-2: Local DoS due to world-writable shared memory > [CVE-2006-3815] Bug#380289: heartbeat: Local DoS due to world-writable shared memory [CVE-2006-3815] Changed Bug title. > found -1 2.0.5-8 Bug#380289: heartbeat-2: Local DoS due to world-writable shared memory [CVE-2006-3815] Bug marked as found in version 2.0.5-8. > found -1 2.0.6-1 Bug#380289: heartbeat-2: Local DoS due to world-writable shared memory [CVE-2006-3815] Bug marked as found in version 2.0.6-1. > found -1 2.0.6-0bpo1 Bug#380289: heartbeat-2: Local DoS due to world-writable shared memory [CVE-2006-3815] Bug marked as found in version 2.0.6-0bpo1. > found 379904 1.2.3-9sarge5 Bug#379904: heartbeat: Local DoS due to world-writable shared memory [CVE-2006-3815] Bug marked as found in version 1.2.3-9sarge5. > found 379904 1.2.3-9sarge4 Bug#379904: heartbeat: Local DoS due to world-writable shared memory [CVE-2006-3815] Bug marked as found in version 1.2.3-9sarge4. > found 379904 1.2.4-11bpo1 Bug#379904: heartbeat: Local DoS due to world-writable shared memory [CVE-2006-3815] Bug marked as found in version 1.2.4-11bpo1. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: closing 367809
Processing commands for [EMAIL PROTECTED]: > # Fixed on NMU since months. > close 367809 Bug#367809: Please configure with --disable-scrollkeeper 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Loïc Minier <[EMAIL PROTECTED]> Removed pending tag. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380180: heartbeat: portblock syntax errors in 1.2.3-9sarge5
On Fri, Jul 28, 2006 at 09:57:24AM +0200, Kostja Siefen wrote: > Package: heartbeat > Version: 1.2.3-9sarge5 > Severity: grave > Tags: patch > Justification: renders package unusable > > > After upgrading to 1.2.3-9sarge5, heartbeat kept rebooting the system as > there were errors running the portblock resource script. > > This bug applies to people which use portblock as heartbeat service > to drop incoming network packets when service takeover. > > The syntax error is due to a missing iptables path which results in > "command not found" errors in /etc/ha.d/resource.d/portblock. > > Fixing is simple, patch is attached (putting iptables back into place). Thanks. I suspect that the problem is that ther eis a missing build depenancy on iptables, and thus its path is not being auto-detected and filled in at build-time. I'll get this fixed for the next release. -- Horms H: http://www.vergenet.net/~horms/ W: http://www.valinux.co.jp/en/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#364800: no answer to dnsmasq broadcasts
On Tue, Jul 18, 2006 at 05:40:50PM +0200, Frédéric Massot wrote: > Hi, > > It was well that, DHCPOFFER replies was blocked by iptables. I corrected > the rules of the firewall. So, I guess we can just mark this bug closed version 2.32-2 too? Cheers, Christian Aichinger signature.asc Description: Digital signature
Bug#358696: This is dangerous, please make it default to disabled
On Fri, 2006 Jul 28 16:12:35 -0300, Henrique de Moraes Holschuh wrote: > > There is no tradeoff without the hack, and the hack is only needed in > hardware unsuitable for UPS management. Thus, it must be optional. It is > dangerous to data and the hardware, so it should not be the default. Define "(un)suitable for UPS management." Does this definition include most people's desktop systems? > You have transient responses to power cuts. Watch in an osciloscope, > computer hardware is not a resistive load. No, but any decent power supply will present a load pretty close to it, making such a transient negligible. (I know this to be the case in production server-room environments.) If someone's got a rack setup where a UPS power cutoff will fry everything, they've got a much bigger problem than what we're discussing here. > The situation is bad when everything powers up at the same time too, yes. > That's why it isn't all powered up at once in server rooms, blade > enclosures, etc. Yes. No problem with wanting staggered shutdown, when you have a large number of machines connected, but large numbers of machines connected are not exactly a typical scenario. > > All of which can be done (and already is, I believe). The only thing that > > the system is doing while waiting for poweroff is "sleep 15m; reboot"---no > > disks need to be spinning for that. > > If you did not call halt, plus told the kernel to shutdown the devices, no, > it was *not* done. > > And the kernel is the *only* thing that really knows how to properly > powerdown the devices. Currently, we cannot ask it to do so from userspace > easily, and if we did, we could not access the disks anymore for example. We have "hdparm -Y". We can't access the disk after that, but we shouldn't need to. What more shutdown magic do you need on a hard disk that is not spinning? If you're talking about a flaky hardware RAID array where you can't stop the platters without it self-destructing, then fine. I recall that the scripts check for RAID, and behave differently in that case. > The issue is how the initscript behaves if the NUT shutdown command doesn't > kill everything to kingdon come in 5 seconds. In fact, a proper UPS is > going to be programmed to actually *delay* the powerdown load command for > enough time to allow the load to try to powerdown for real by itself. Assuming things are as I had in my patch, the idea is to have all machines connected to a given UPS configured with a similar wait-until-poweroff- else-reboot time (if they don't shutdown straightaway). This approach is admittedly not the best one---ideally you'd have some sort of statically-linked "death watch" daemon that would do the same thing, but also monitor the UPS, and broadcast an "online" signal if the power returns. You'd no longer have to configure any wait-until-poweroff time, and the aforementioned tradeoff goes away. But this is a wishlist item. Anyway, the disagreement comes down to this: Me: Keep the system minimally running, so that it powers off when the UPS cuts the power, so that it will turn on again when the power returns, given the default behavior and limitations of PC hardware. Do sensible steps to avoid data loss (stop the disks, etc.). Have this be the default, as PC users are the common case. You: Do a normal system shutdown. Rely on server-grade features (e.g. WOL packet from a networked UPS) to resume operation, or an "On/Off state: ON" BIOS setting (despite the problems associated with that). Have this be the default, as the risk of data loss from fragile storage media trumps that of system unavailability after an extended outage. Mr. Quette will have to decide this, but I don't think you've made a strong case for a power-cut being significantly detrimental to data or hardware. Yes, there are circumstances where this can happen, but these are exceptions to the rule. And in one well-known case (RAID arrays), the scripts can easily do something different. > > I think you'll take issue with the NUT documentation, then, as it > > specifically suggests this approach. > > I will. But maybe, perchance, the NUT docs don't suggest you do it unless > you own hardware that cannot do it properly? I didn't read it yet. I'm getting the impression that "hardware that cannot do it properly," as you mean it, includes most PCs and non-server machines. Your view carries the day if NUT's userbase is not mostly these. --Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#378446: bluez-utils: me too
Package: bluez-utils Version: 3.1-3 Followup-For: Bug #378446 I can't get my mobile pairing either, it does not accept the pin. Tried /usr/lib/bluetooth/add-passkey both manually and by the init script, no difference. dbus-monitor didn't show anything passkey related either. Thanks, Feri. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages bluez-utils depends on: ii libbluetooth23.1-1 Library to use the BlueZ Linux Blu ii libc62.3.6-16GNU C Library: Shared libraries ii libdbus-1-2 0.62-4 simple interprocess messaging syst ii libdbus-glib-1-2 0.62-4 simple interprocess messaging syst ii libglib2.0-0 2.10.3-3The GLib library of C routines ii libusb-0.1-4 2:0.1.12-2 userspace USB programming library ii lsb-base 3.1-10 Linux Standard Base 3.1 init scrip ii makedev 2.3.1-82creates device files in /dev ii module-init-tools3.2.2-3 tools for managing Linux kernel mo ii sysvinit 2.86.ds1-15 System-V-like init utilities ii udev 0.093-1 /dev/ and hotplug management daemo bluez-utils recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366512: ted: Fails to display file
On May 9, Steve Langasek ([EMAIL PROTECTED]) wrote: > Is there any chance that bug #365403 is relevant to this case? I can reproduce this bug. It's not related to #365403. Steps: # cdebootstrap -f minimal unstable unstable # chroot unstable # apt-get install vnc4server xbase-clients ted xterm xfonts-base Ted works when I start it from the chroot and tell it to connect to :0 (i.e. my local X server, running on the host). But it fails if I start vncserver inside the chroot and tell Ted to connect to that server. I would have loved to investigate this problem further, BUT I COULD NOT, SINCE I COULD NOT GET TED TO BUILD WITH DEBUGGING SYMBOLS. What a mess. And it's not even completeley the maintainer's fault, since I couldn't even pass CFLAGS to the upstream build system... I can't even remember the last time when I've seen such a piece of software... Sorry, but I had to get that off my mind... If someone can tell me a way to actually build ted with debugging information I'll look into this further. HTH, Christian Aichinger signature.asc Description: Digital signature
Bug#379827: marked as done (FTBFS: doesn't recognize autoconf 2.60)
Your message dated Fri, 28 Jul 2006 14:32:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379827: fixed in kile 1:1.9.1-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: kile Version: 1:1.9.1-1 Severity: serious Your package fails to build from source because it doesn't recognize Autoconf 2.60. A patch similar to http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946 should fix this problem. For some background, please see the discussion at http://lists.debian.org/debian-devel/2006/07/msg00958.html > Automatic build of kile_1:1.9.1-1 on usurper by sbuild/amd64 0.46 ... > make[1]: Entering directory `/build/tbm/kile-1.9.1' > *** YOU'RE USING autoconf (GNU Autoconf) 2.60. > *** KDE requires autoconf 2.53 or newer > make[1]: *** [cvs] Error 1 > make[1]: Leaving directory `/build/tbm/kile-1.9.1' > make: *** [makebuilddir/kile] Error 2 -- Martin Michlmayr http://www.cyrius.com/ --- End Message --- --- Begin Message --- Source: kile Source-Version: 1:1.9.1-2 We believe that the bug you reported is fixed in the latest version of kile, which is due to be installed in the Debian FTP archive: kile-i18n_1.9.1-2_all.deb to pool/main/k/kile/kile-i18n_1.9.1-2_all.deb kile_1.9.1-2.diff.gz to pool/main/k/kile/kile_1.9.1-2.diff.gz kile_1.9.1-2.dsc to pool/main/k/kile/kile_1.9.1-2.dsc kile_1.9.1-2_amd64.deb to pool/main/k/kile/kile_1.9.1-2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ana Beatriz Guerrero Lopez <[EMAIL PROTECTED]> (supplier of updated kile package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Jul 2006 22:20:06 +0200 Source: kile Binary: kile kile-i18n Architecture: source amd64 all Version: 1:1.9.1-2 Distribution: unstable Urgency: low Maintainer: Debian KDE Extras Team <[EMAIL PROTECTED]> Changed-By: Ana Beatriz Guerrero Lopez <[EMAIL PROTECTED]> Description: kile - KDE Integrated LaTeX Environment kile-i18n - translations for Kile, the KDE Integrated LaTeX Environment Closes: 379827 Changes: kile (1:1.9.1-2) unstable; urgency=low . [Mark Purcell] * Update debian/watch . [Ana Beatriz Guerrero Lopez] * Dropping re-libtoolizing at build time, instead updating libtool with a patch. (Closes: #379827). Files: 4a42a68f493d628998e5758332adce8d 750 tex optional kile_1.9.1-2.dsc 01574ce4567124b5062f624ba441f5e2 258799 tex optional kile_1.9.1-2.diff.gz 1df227de8efb56b6a2ff34b1c2889e9d 3067770 tex optional kile-i18n_1.9.1-2_all.deb 3ddd64e651e280cd9b4e11d1ce48fd24 1952034 tex optional kile_1.9.1-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEyn82vGr7W6HudhwRArTKAJ9W3BoE1AgxwSzBdjp8UjVSn1Y3BwCgpYv4 C5Nu4C7dGPhiXaJrDanTars= =/UyT -END PGP SIGNATURE- --- End Message ---
Bug#379440: quodlibet broken after update of python packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, quodlibet 0.22 entered the archive, and uses Python 2.4. So is this bug still occurring with the new version? Regards, Bastian - -- ,''`. Bastian Kleineidam : :' :GnuPG Schlüssel `. `'gpg --keyserver wwwkeys.pgp.net --recv-keys 32EC6F3E `- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEynKYeBwlBDLsbz4RAqIaAKCkzZdkCRxSWCeu7gJJRdhD8Q5o/gCeMkFZ G+EBNbfvRB67DV76SSaD2rk= =3254 -END PGP SIGNATURE-
Bug#380254: yelp crashes on start
On Fri, Jul 28, 2006, Bas Zoetekouw wrote: > Yelp crashes spontaneously a few seconds after start (either from the > commnd line, or from an application's help menu). > > The bug buddy thingy gives a huge backtrace, which I'm attaching. Does it still crash if you disable accessibility in the GNOME preferences? (logout and back in before trying) -- Loïc Minier <[EMAIL PROTECTED]>
Bug#380269: libnet-xmpp-perl: FTBFS: Test failures
Package: libnet-xmpp-perl Version: 1.0-1 Severity: serious From my pbuilder build log: ... /usr/bin/make test make[1]: Entering directory `/tmp/buildd/libnet-xmpp-perl-1.0' PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/1_load.ok t/2_client_jabberd1.4ok 2/5# Failed test (t/2_client_jabberd1.4.t at line 49) # Failed test (t/2_client_jabberd1.4.t at line 50) # Failed test (t/2_client_jabberd1.4.t at line 51) # Looks like you failed 3 tests of 5. t/2_client_jabberd1.4dubious Test returned status 3 (wstat 768, 0x300) DIED. FAILED tests 3-5 Failed 3/5 tests, 40.00% okay t/3_client_jabberd2..ok 4/5 skipped: Cannot open connection (maybe a firewall?) t/iq.ok t/jidok t/messageok t/packet_iqauth..ok t/packet_iqrosterok t/presence...ok t/rawxml.ok t/roster.ok Failed Test Stat Wstat Total Fail Failed List of Failed --- t/2_client_jabberd1.4.t3 768 53 60.00% 3-5 4 subtests skipped. Failed 1/11 test scripts, 90.91% okay. 3/650 subtests failed, 99.54% okay. make[1]: *** [test_dynamic] Error 255 make[1]: Leaving directory `/tmp/buildd/libnet-xmpp-perl-1.0' make: *** [install-stamp] Error 2 -- Daniel Schepler
Bug#330937: marked as done (FTBFS: ICE on m68k, arm and hppa)
Your message dated Fri, 28 Jul 2006 14:02:49 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#330937: fixed in kbarcode 2.0.4-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: kbarcode Version: 1.8.0-3 Severity: grave Tags: sid Please see #323133: internal compiler error: in cp_expr_size, at cp/cp-objcp-common.c:101 or the build logs on arm, hppa and m68k. You can fix this by: * debian/control: Add 'g++-3.4 [arm m68k hppa], ' to Build-Depends * debian/rules: Add: ### GCC4_ICES_HERE := arm m68k hppa DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH) ifneq (,$(findstring $(DEB_BUILD_ARCH),$(GCC4_ICES_HERE))) export CC=gcc-3.4 export CPP=cpp-3.4 export CXX=g++-3.4 endif ### somewhere on top of the file. Cheers Luk -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDPVTU5UTeB5t8Mo0RAu14AKCfkXWCn8I86zJrRihnKYLV9O/idwCdHGZk IMHGLcb7dGi7RmRflbPVBz4= =PpuZ -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: kbarcode Source-Version: 2.0.4-1 We believe that the bug you reported is fixed in the latest version of kbarcode, which is due to be installed in the Debian FTP archive: kbarcode_2.0.4-1.diff.gz to pool/main/k/kbarcode/kbarcode_2.0.4-1.diff.gz kbarcode_2.0.4-1.dsc to pool/main/k/kbarcode/kbarcode_2.0.4-1.dsc kbarcode_2.0.4-1_i386.deb to pool/main/k/kbarcode/kbarcode_2.0.4-1_i386.deb kbarcode_2.0.4.orig.tar.gz to pool/main/k/kbarcode/kbarcode_2.0.4.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mark Purcell <[EMAIL PROTECTED]> (supplier of updated kbarcode package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Jul 2006 21:30:19 +0100 Source: kbarcode Binary: kbarcode Architecture: source i386 Version: 2.0.4-1 Distribution: unstable Urgency: low Maintainer: Debian KDE Extras Team <[EMAIL PROTECTED]> Changed-By: Mark Purcell <[EMAIL PROTECTED]> Description: kbarcode - barcode and label printing application for KDE Closes: 215385 303338 314013 330937 342975 346743 357331 Changes: kbarcode (2.0.4-1) unstable; urgency=low . [ Mark Purcell ] * New upstream release * Ack NMU's: - FTBFS: ICE on m68k, arm and hppa (Closes: #330937) - FTBFS: build-depends on removed xlibs-dev (Closes: #346743) - kbarcode_1.8.0-2(GNU/k*BSD): out of date config.sub/config.guess (Closes: #303338) - error in doc-base file (Closes: #215385) - Package explicitely build-depends on g++-3.4 (Closes: #342975) - [INTL:de] German PO file corrections (Closes: #314013) - Please update config.* (Closes: #357331) . [ Fathi Boudra ] * Added to Recommends: libqt3-mt-mysql | libqt3-mt-psql | libqt3-mt-odbc | libqt3-mt-sqlite | libqt3-mt-ibase Files: de1b8378e67ca14f1cc2f00e2f02fc63 685 kde optional kbarcode_2.0.4-1.dsc 86f62225995d9c55a0b8b0bf1dd0e403 1171749 kde optional kbarcode_2.0.4.orig.tar.gz 69b7f59a2e1b20960b5034b6004e4dfc 5447 kde optional kbarcode_2.0.4-1.diff.gz 703af512ba8903eb0059968dd453f014 533696 kde optional kbarcode_2.0.4-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEynZToCzanz0IthIRAhY1AJ0Vou3xyUVNQ0+Fm1I13jyBFP8/8gCgmY7U KlOlezWKio/fPhUvPF6PQCk= =VOEB -END PGP SIGNATURE- --- End Message ---
Bug#379893: marked as done (FTBFS: doesn't recognize autoconf 2.60)
Your message dated Fri, 28 Jul 2006 14:04:40 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379893: fixed in scribus-ng 1.3.3.2.dfsg-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: scribus-ng Version: 1.3.3.2.dfsg-1 Severity: serious Your package fails to build from source because it doesn't recognize Autoconf 2.60. A patch similar to http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1= 543983&r2=555946 should fix this problem. For some background, please see the discussion at http://lists.debian.org/debian-devel/2006/07/msg00958.html > Automatic build of scribus-ng_1.3.3.2.dfsg-1 on usurper by sbuild/amd64 0.46 ... > /usr/bin/make -f Makefile.cvs > make[1]: Entering directory `/build/tbm/scribus-ng-1.3.3.2.dfsg' > make[2]: Entering directory `/build/tbm/scribus-ng-1.3.3.2.dfsg' > *** YOU'RE USING autoconf (GNU Autoconf) 2.60. > *** Scribus requires autoconf 2.53 or newer > make[2]: *** [cvs] Error 1 -- Martin Michlmayr http://www.cyrius.com/ --- End Message --- --- Begin Message --- Source: scribus-ng Source-Version: 1.3.3.2.dfsg-2 We believe that the bug you reported is fixed in the latest version of scribus-ng, which is due to be installed in the Debian FTP archive: scribus-ng_1.3.3.2.dfsg-2.diff.gz to pool/main/s/scribus-ng/scribus-ng_1.3.3.2.dfsg-2.diff.gz scribus-ng_1.3.3.2.dfsg-2.dsc to pool/main/s/scribus-ng/scribus-ng_1.3.3.2.dfsg-2.dsc scribus-ng_1.3.3.2.dfsg-2_i386.deb to pool/main/s/scribus-ng/scribus-ng_1.3.3.2.dfsg-2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Oleksandr Moskalenko <[EMAIL PROTECTED]> (supplier of updated scribus-ng package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Jul 2006 13:19:41 -0600 Source: scribus-ng Binary: scribus-ng Architecture: source i386 Version: 1.3.3.2.dfsg-2 Distribution: unstable Urgency: medium Maintainer: Oleksandr Moskalenko <[EMAIL PROTECTED]> Changed-By: Oleksandr Moskalenko <[EMAIL PROTECTED]> Description: scribus-ng - Open Source Desktop Page Layout - developmental branch Closes: 379077 379893 Changes: scribus-ng (1.3.3.2.dfsg-2) unstable; urgency=medium . * debian/patches/02-cvs_sh.dpatch: Added a patch that fixes autoconf-2.60 detection failure (Closes: #379893). Setting urgency=medium for this. * debian/control: Checked the liblcms1 dependency and it is >= 1.13 (Closes: #379077). * debian/scribus-ng.lintian: Updated lintian overrides. Files: 6a9546da66dd772b88dc3e0c875dfa31 865 graphics optional scribus-ng_1.3.3.2.dfsg-2.dsc d7557457722ce446078c47b5dca6f074 356274 graphics optional scribus-ng_1.3.3.2.dfsg-2.diff.gz 1b8b471db4cd69bbe85462a2c3cac0c5 7093468 graphics optional scribus-ng_1.3.3.2.dfsg-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEynpa2ihvMmxfGWsRAoxnAKCkQBiOqxzTb+hC2fpBvIOvDIxzZQCggaHQ BDHvm1jj+cpAx3eG9eap/u8= =fXbe -END PGP SIGNATURE- --- End Message ---
Processed: setting package to cinepaint cinepaint-data libcinepaint0 libcinepaint-dev, tagging 367543 ...
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.20 > package cinepaint cinepaint-data libcinepaint0 libcinepaint-dev Ignoring bugs not assigned to: libcinepaint-dev libcinepaint0 cinepaint cinepaint-data > tags 367543 + pending Bug#367543: cinepaint cannot load its plugins There were no tags set. Tags added: pending > tags 374264 + pending Bug#374264: cinepaint: FTBFS: gtk linking problems There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380270: libnet-jabber-perl: FTBFS: Test failures
Package: libnet-jabber-perl Version: 2.0-2 Severity: serious From my pbuilder build log: ... /usr/bin/make test make[1]: Entering directory `/tmp/buildd/libnet-jabber-perl-2.0' PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/1_load..ok t/2_client# Failed test (t/2_client.t at line 49) # Failed test (t/2_client.t at line 50) # Failed test (t/2_client.t at line 51) # Looks like you failed 3 tests of 5. dubious Test returned status 3 (wstat 768, 0x300) DIED. FAILED tests 3-5 Failed 3/5 tests, 40.00% okay t/iq..ok t/jid.ok ... Failed Test Stat Wstat Total Fail Failed List of Failed --- t/2_client.t3 768 53 60.00% 3-5 Failed 1/49 test scripts, 97.96% okay. 3/3376 subtests failed, 99.91% okay. make[1]: *** [test_dynamic] Error 255 make[1]: Leaving directory `/tmp/buildd/libnet-jabber-perl-2.0' make: *** [install-stamp] Error 2 -- Daniel Schepler
Bug#380189: xvncviewer: xrealvncviewer no longer works after using pump
tags 38018 + unreproduceable help severity 38018 normal thanks Hi First of all I need to report that this problem can not be reproduced by me, so you need to specify exactly how you run the server and the client, network setup etc. 1) How do you start the client? More specifically what hostname did you connect to? 2) You say that it do not display anything. Do it disconnect or is the screen black or what do you mean with do not display anything? 3) Did you upgrade anything during this or was it just pump that you run? 4) What iptables rules do you have? 5) What did you do with pump? 6) How did you start the server? 7) If you upgraded, from which version of vnc did you upgrade? Regards, // Ola On Fri, Jul 28, 2006 at 11:00:07AM +0200, Vincent Lefevre wrote: > Package: xvncviewer > Version: 3.3.7-12 > Severity: grave > Justification: causes non-serious data loss > > After using pump, xvncviewer no longer works (with a local server). > All the unsaved data in the current X session are lost. Moreover, > I can restart the VNC server and xvncviewer, and all the processes > are running, but the VNC viewer doesn't display anything. > > Note: the eth1 address has changed (as expected), but lo is still up: > > loLink encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:671939 errors:0 dropped:0 overruns:0 frame:0 > TX packets:671939 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1844990014 (1.7 GiB) TX bytes:1844990014 (1.7 GiB) > > Xfree86 without VNC works normally. > > Currently I can't investigate more deeply. I'll try later to see if > rebooting the machine makes xvncviewer work again or if the problem > was due to a system upgrade. > > -- System Information: > Debian Release: testing/unstable > APT prefers testing > APT policy: (900, 'testing'), (900, 'stable'), (200, 'unstable') > Architecture: powerpc (ppc) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.17-1-powerpc > Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1) > > Versions of packages xvncviewer depends on: > ii dpkg 1.13.21package maintenance system for > Deb > ii libc6 2.3.6-15 GNU C Library: Shared libraries > ii libgcc1 1:4.1.1-5 GCC support library > ii libice6 6.9.0.dfsg.1-6 Inter-Client Exchange library > ii libsm66.9.0.dfsg.1-6 X Window System Session > Management > ii libstdc++64.1.1-5The GNU Standard C++ Library v3 > ii libx11-6 6.9.0.dfsg.1-6 X Window System protocol client > li > ii libxaw7 6.9.0.dfsg.1-6 X Athena widget set library > ii libxext6 6.9.0.dfsg.1-6 X Window System miscellaneous > exte > ii libxmu6 6.9.0.dfsg.1-6 X Window System miscellaneous > util > ii libxt66.9.0.dfsg.1-6 X Toolkit Intrinsics > ii vnc-common3.3.7-12 Virtual network computing server > s > ii zlib1g1:1.2.3-13 compression library - runtime > > Versions of packages xvncviewer recommends: > ii xfonts-base 6.9.0.dfsg.1-6 standard fonts for X > > -- no debconf information > > -- - Ola Lundqvist --- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | +46 (0)54-10 14 30 +46 (0)70-332 1551 | | http://www.opal.dhs.org UIN/icq: 4912500 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#346743: marked as done (kbarcode: FTBFS: build-depends on removed xlibs-dev)
Your message dated Fri, 28 Jul 2006 14:02:49 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#346743: fixed in kbarcode 2.0.4-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: kbarcode Version: 1.8.0-3.1 Severity: serious Hello, This is a serious bug filed against your package because it build-depends on xlibs-dev, which as announced in [1] a while ago, is no longer available in sid. This makes your package fail to build from source. [1] http://lists.debian.org/debian-devel-announce/2005/11/msg00022.html To fix this bug, you need to update your build-dependencies and substitute xlibs-dev for the list of individual X development libraries that your package needs to be built. You can find detailed information about how to do that in the DependsXlibsDev wiki page [2]. [2] http://wiki.debian.org/DependsXlibsDev As indicated by the Release Team [3], the full transition from XFree86 to Xorg is a release blocker for Etch, which means that Etch will not be released until this bug is fixed (or your package removed from testing). So, please, try to fix in a timely manner. [3] http://lists.debian.org/debian-devel-announce/2005/10/msg4.html The number of affected packages by the xlibs-dev transition is huge, so if you feel like helping with patches or uploads, feel free to follow the instructions contained in the wiki page above. A list of affected packages can be found here [4]. [4] http://people.debian.org/~adeodato/release-usertag/transition-xlibs-dev Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your collaboration! -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org --- End Message --- --- Begin Message --- Source: kbarcode Source-Version: 2.0.4-1 We believe that the bug you reported is fixed in the latest version of kbarcode, which is due to be installed in the Debian FTP archive: kbarcode_2.0.4-1.diff.gz to pool/main/k/kbarcode/kbarcode_2.0.4-1.diff.gz kbarcode_2.0.4-1.dsc to pool/main/k/kbarcode/kbarcode_2.0.4-1.dsc kbarcode_2.0.4-1_i386.deb to pool/main/k/kbarcode/kbarcode_2.0.4-1_i386.deb kbarcode_2.0.4.orig.tar.gz to pool/main/k/kbarcode/kbarcode_2.0.4.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mark Purcell <[EMAIL PROTECTED]> (supplier of updated kbarcode package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Jul 2006 21:30:19 +0100 Source: kbarcode Binary: kbarcode Architecture: source i386 Version: 2.0.4-1 Distribution: unstable Urgency: low Maintainer: Debian KDE Extras Team <[EMAIL PROTECTED]> Changed-By: Mark Purcell <[EMAIL PROTECTED]> Description: kbarcode - barcode and label printing application for KDE Closes: 215385 303338 314013 330937 342975 346743 357331 Changes: kbarcode (2.0.4-1) unstable; urgency=low . [ Mark Purcell ] * New upstream release * Ack NMU's: - FTBFS: ICE on m68k, arm and hppa (Closes: #330937) - FTBFS: build-depends on removed xlibs-dev (Closes: #346743) - kbarcode_1.8.0-2(GNU/k*BSD): out of date config.sub/config.guess (Closes: #303338) - error in doc-base file (Closes: #215385) - Package explicitely build-depends on g++-3.4 (Closes: #342975) - [INTL:de] German PO file corrections (Closes: #314013) - Please update config.* (Closes: #357331) . [ Fathi Boudra ] * Added to Recommends: libqt3-mt-mysql | libqt3-mt-psql | libqt3-mt-odbc | libqt3-mt-sqlite | libqt3-mt-ibase Files: de1b8378e67ca14f1cc2f00e2f02fc63 685 kde optional kbarcode_2.0.4-1.dsc 86f62225995d9c55a0b8b0bf1dd0e403 1171749 kde optional kbarcode_2.0.4.orig.tar.gz 69b7f59a2e1b20960b5034b6004e4dfc 5447 kde optional kbarcode_2.0.4-1.diff.gz 703af512ba8903eb0059968dd453f014 533696 kde optional kba
Processed: Fixed in NMU of cinepaint 0.20-1-1.3
Processing commands for [EMAIL PROTECTED]: > tag 367543 + fixed Bug#367543: cinepaint cannot load its plugins Tags were: pending Tags added: fixed > tag 374264 + fixed Bug#374264: cinepaint: FTBFS: gtk linking problems Tags were: pending Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380271: SECURITY: Merge table are unaffected from later right revokations.
Package: mysql-server-4.1 Version: 4.1.11a-4sarge5 Severity: grave Tags: security patch Hello MySQL today announced a new upstream version for mysql-server-4.1 that fixes a security problem: Security fix: If a user has access to MyISAM table t, that user can create a MERGE table m that accesses t. However, if the user's privileges on t are subsequently revoked, the user can continue to access t by doing so through m. If this behavior is undesirable, you can start the server with the new --skip-merge option to disable the MERGE storage engine. http://bugs.mysql.com/bug.php?id=15195 The bug affects 3.23 woody 4.0 sarge 4.1 sarge 5.0 unstable although in 3.23 and 4.0 it's even more unlikely as merge tables couldn't even span databases i.e. table based rights would have to be revoked. Does this justify a DSA? If so, can you register a CVE id? bye, -christian- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#373785: Anything new?
Hi, Anything new about this bug? You said that you'll ask for removal of zpkg from unstable once it's not needed. I was looking through RC bugs that affect etch and there is no update on this issue for a year now. Thanks, Baruch -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: your mail
Processing commands for [EMAIL PROTECTED]: > retitle #379624 FTBFS of the java bytecode generator on IA64 Bug#379624: FTBFS: `debian/smarteiffel/usr/lib/smarteiffel/bin/compile': No such file or directory Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#358696: This is dangerous, please make it default to disabled
On Fri, 28 Jul 2006, Daniel Richard G. wrote: > The time period should be configurable; I just suggested 15 minutes as a > default. You could set a higher value, but the tradeoff is that if the > power returns, the system is unavailable for that time period. There is no tradeoff without the hack, and the hack is only needed in hardware unsuitable for UPS management. Thus, it must be optional. It is dangerous to data and the hardware, so it should not be the default. It is fairly simple, really, unless I missed something major (which is always possible). > > 2. Not powering off the box by itself (read: allowing halt and the kernel to > > do its job and cut power cleanly) means it will be subject to high > > transients when the UPS shuts down the load. This will, in turn, make it > > worse for the other loads that have not been properly shut down. It would > > be a disaster in a server farm. > > Please elaborate on how server equipment is subjected to a transient when a > UPS cuts power to it. (If anything, the situation is much worse when it is > powered back on.) You have transient responses to power cuts. Watch in an osciloscope, computer hardware is not a resistive load. The situation is bad when everything powers up at the same time too, yes. That's why it isn't all powered up at once in server rooms, blade enclosures, etc. > > 3. Non-controlled shutdowns are *very* bad for all hardware, including > > desktop systems. For starters, all disks will be subject to emergency head > > unloads. The halt utility does a lot of work-around on kenrel bugs to make > > sure disks are parked, RAID arrays are in read-only mode or shutdown, etc > > for a damn good reason. > > All of which can be done (and already is, I believe). The only thing that > the system is doing while waiting for poweroff is "sleep 15m; reboot"---no > disks need to be spinning for that. If you did not call halt, plus told the kernel to shutdown the devices, no, it was *not* done. And the kernel is the *only* thing that really knows how to properly powerdown the devices. Currently, we cannot ask it to do so from userspace easily, and if we did, we could not access the disks anymore for example. > Isn't this already the case for non-networked UPSes? When the interface is > serial or USB, it can only be connected to (and controlled by) a single, > master host. The issue is how the initscript behaves if the NUT shutdown command doesn't kill everything to kingdon come in 5 seconds. In fact, a proper UPS is going to be programmed to actually *delay* the powerdown load command for enough time to allow the load to try to powerdown for real by itself. > > Thus, implementing the work around proposed in this bug report as a default > > behaviour is not acceptable. Please revert the change, or make it optional, > > and *not* enabled by default. I would go even further and actively > > discourage heavily the use of this option, as it can damage the hardware. > > I think you'll take issue with the NUT documentation, then, as it > specifically suggests this approach. I will. But maybe, perchance, the NUT docs don't suggest you do it unless you own hardware that cannot do it properly? I didn't read it yet. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: block
Processing commands for [EMAIL PROTECTED]: > block 379835 with 380226 Bug#379835: NTFS (partition) not recreated correctly after resize:incorrect start sector Was not blocked by any bugs. Blocking bugs of 379835 added: 380226 > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#170144: marked as done (xtet42: FTBFS: Build-Depends on xlib6g-dev)
Your message dated Fri, 28 Jul 2006 12:01:39 -0700 with message-id <[EMAIL PROTECTED]> and subject line Package has been removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xtet42 Severity: normal (This is an automatically generated bug, based on the current contents of the Sources file for the main section.) This source package contains a build dependency on xlib6g-dev. This needs to be updated since the xlib6g* packages will disappear by the time of the next release. Be aware that, in addition to xlibs-dev, you may also need to specify libxaw7-dev. Also, if your source package uses imake, you will need to specify xutils as well. --- End Message --- --- Begin Message --- This package was removed in a cleanup by the QA team, so I'm closing this bug. -- Michael Janssen --- Jamuraa --- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --- End Message ---
Bug#379501: marked as done (digikam: FTBFS: grep: /usr/lib/libltdl.la: No such file or directory)
Your message dated Fri, 28 Jul 2006 19:06:20 +0100 with message-id <[EMAIL PROTECTED]> and subject line Fwd: [Pkg-kde-extras] Fixed in upload of digikam 1:0.9-beta1-2 to experimental has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: digikam Version: 0.9-beta1-1 Severity: serious Hello, There was a problem while autobuilding your package: > Automatic build of digikam_0.9-beta1-1 on avidan by sbuild/i386 0.49 > Build started at 20060723-1144 > ** ... > /usr/share/qt3/bin/moc > /build/buildd/digikam-0.9-beta1/./digikam/utilities/setup/setupslideshow.h -o > setupslideshow.moc > /bin/bash ../../../libtool --silent --tag=CXX --mode=compile g++ > -DHAVE_CONFIG_H -I. > -I/build/buildd/digikam-0.9-beta1/./digikam/utilities/setup -I../../.. > -I/build/buildd/digikam-0.9-beta1/./digikam/digikam > -I/build/buildd/digikam-0.9-beta1/./digikam/libs/dialogs > -I/build/buildd/digikam-0.9-beta1/./digikam/libs/dimg > -I/build/buildd/digikam-0.9-beta1/./digikam/libs/widgets/common > -I/usr/include/gphoto2 -I/usr/include -I/usr/include/kde -I/usr/include/kde > -I/usr/share/qt3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT > -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align > -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG > -O2 -g -Wall -O2 -Wformat-security -Wmissing-format-attribute > -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common > -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT > -DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE -c -o setupslideshow.lo > /build/buildd/digikam-0.9-beta1/./digikam/utilities/setup/setupslideshow.cpp > /usr/share/qt3/bin/moc > /build/buildd/digikam-0.9-beta1/./digikam/utilities/setup/setupidentity.h -o > setupidentity.moc > /bin/bash ../../../libtool --silent --tag=CXX --mode=compile g++ > -DHAVE_CONFIG_H -I. > -I/build/buildd/digikam-0.9-beta1/./digikam/utilities/setup -I../../.. > -I/build/buildd/digikam-0.9-beta1/./digikam/digikam > -I/build/buildd/digikam-0.9-beta1/./digikam/libs/dialogs > -I/build/buildd/digikam-0.9-beta1/./digikam/libs/dimg > -I/build/buildd/digikam-0.9-beta1/./digikam/libs/widgets/common > -I/usr/include/gphoto2 -I/usr/include -I/usr/include/kde -I/usr/include/kde > -I/usr/share/qt3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT > -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align > -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG > -O2 -g -Wall -O2 -Wformat-security -Wmissing-format-attribute > -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common > -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT > -DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE -c -o setupidentity.lo > /build/buildd/digikam-0.9-beta1/./digikam/utilities/setup/setupidentity.cpp > /bin/bash ../../../libtool --silent --tag=CXX --mode=link g++ -Wno-long-long > -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion > -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -g -Wall > -O2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor > -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE > -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION > -DQT_CLEAN_NAMESPACE-o libsetup.la -L/usr/share/qt3/lib -L/usr/lib > -L/usr/lib -lgphoto2 -lm -L/usr/lib -lgphoto2_port setup.lo setupcamera.lo > setupimgplugins.lo cameraselection.lo setupgeneral.lo gpiface.lo setupmime.lo > setupplugins.lo setupcollections.lo setupmetadata.lo setupeditor.lo > setupmisc.lo setupicc.lo setupiofiles.lo setupslideshow.lo setupidentity.lo > grep: /usr/lib/libltdl.la: No such file or directory > /bin/sed: can't read /usr/lib/libltdl.la: No such file or directory > libtool: link: `/usr/lib/libltdl.la' is not a valid libtool archive > make[5]: *** [libsetup.la] Error 1 > make[5]: Leaving directory > `/build/buildd/digikam-0.9-beta1/obj-i486-linux-gnu/digikam/utilities/setup' > make[4]: *** [all-recursive] Error 1 > make[4]: Leaving directory > `/build/buildd/digikam-0.9-beta1/obj-i486-linux-gnu/digikam/utilities' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory > `/build/buildd/digikam-0.9-beta1/obj-i486-linux-gnu/digikam' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory > `/build/buildd/digikam-0.9-beta1/obj-i486-linux-gnu' > make[1]: *** [all] Er
Bug#379555: marked as done (bacula-doc: FTBFS: Missing Build-Depends on 'tetex-bin')
Your message dated Fri, 28 Jul 2006 11:17:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379555: fixed in bacula-doc 1.38.11.1-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: bacula-doc Version: 1.38.11.1-1 Severity: serious Tags: patch When building 'bacula-doc' in a clean 'unstable' chroot, I get the following error: # Add here commands to compile the package. cd /bacula-doc-1.38.11.1/debian/tmp-build/manual && /usr/bin/make tex dvipdf make[1]: Entering directory `/bacula-doc-1.38.11.1/debian/tmp-build/manual' Making version 1.38.11 (28 June 2006) latex -interaction=batchmode bacula.tex make[1]: latex: Command not found make[1]: [tex] Error 127 (ignored) makeindex bacula.idx -o bacula.ind 2>/dev/null make[1]: *** [tex] Error 127 make[1]: Leaving directory `/bacula-doc-1.38.11.1/debian/tmp-build/manual' make: *** [build-stamp] Error 2 Please add the missing Build-Depends on 'tetex-bin' to debian/control. Regards Andreas Jochens diff -urN ../tmp-orig/bacula-doc-1.38.11.1/debian/control ./debian/control --- ../tmp-orig/bacula-doc-1.38.11.1/debian/control 2006-07-24 09:27:34.0 + +++ ./debian/control2006-07-24 09:27:31.0 + @@ -2,7 +2,7 @@ Section: doc Priority: optional Maintainer: John Goerzen <[EMAIL PROTECTED]> -Build-Depends: debhelper (>= 5) +Build-Depends: debhelper (>= 5), tetex-bin Standards-Version: 3.7.2 Package: bacula-doc --- End Message --- --- Begin Message --- Source: bacula-doc Source-Version: 1.38.11.1-2 We believe that the bug you reported is fixed in the latest version of bacula-doc, which is due to be installed in the Debian FTP archive: bacula-doc_1.38.11.1-2.diff.gz to pool/main/b/bacula-doc/bacula-doc_1.38.11.1-2.diff.gz bacula-doc_1.38.11.1-2.dsc to pool/main/b/bacula-doc/bacula-doc_1.38.11.1-2.dsc bacula-doc_1.38.11.1-2_all.deb to pool/main/b/bacula-doc/bacula-doc_1.38.11.1-2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. John Goerzen <[EMAIL PROTECTED]> (supplier of updated bacula-doc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Jul 2006 12:59:25 -0500 Source: bacula-doc Binary: bacula-doc Architecture: source all Version: 1.38.11.1-2 Distribution: unstable Urgency: low Maintainer: John Goerzen <[EMAIL PROTECTED]> Changed-By: John Goerzen <[EMAIL PROTECTED]> Description: bacula-doc - Documentation for Bacula Closes: 379555 Changes: bacula-doc (1.38.11.1-2) unstable; urgency=low . * Fixed missing tetex build-deps. Oops. Closes: #379555. Files: 044d1638c6b170f2f7c442b2e2f42ee1 622 doc optional bacula-doc_1.38.11.1-2.dsc 3f147d5341222a15e820152783069ad0 4337 doc optional bacula-doc_1.38.11.1-2.diff.gz a6c9a8b46d4df8e1d1557692dba66bf4 4344342 doc optional bacula-doc_1.38.11.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEylIG3PeFtIodmh8RAlDSAKC2IV2Uzn1AeeldFR6Oe40eKfquJQCeOH8G ERP73yhYiDDUmjQDeRqoAqc= =rJFL -END PGP SIGNATURE- --- End Message ---
Bug#358696: This is dangerous, please make it default to disabled
On Fri, 2006 Jul 28 14:46:47 -0300, Henrique de Moraes Holschuh wrote: > > 1. The UPS may take more than 15 minutes to shutdown the load. You cannot > assume things like this, and you will cause data loss if you get it wrong: > the power-off could come with the system fully online. The time period should be configurable; I just suggested 15 minutes as a default. You could set a higher value, but the tradeoff is that if the power returns, the system is unavailable for that time period. > 2. Not powering off the box by itself (read: allowing halt and the kernel to > do its job and cut power cleanly) means it will be subject to high > transients when the UPS shuts down the load. This will, in turn, make it > worse for the other loads that have not been properly shut down. It would > be a disaster in a server farm. Please elaborate on how server equipment is subjected to a transient when a UPS cuts power to it. (If anything, the situation is much worse when it is powered back on.) > 3. Non-controlled shutdowns are *very* bad for all hardware, including > desktop systems. For starters, all disks will be subject to emergency head > unloads. The halt utility does a lot of work-around on kenrel bugs to make > sure disks are parked, RAID arrays are in read-only mode or shutdown, etc > for a damn good reason. All of which can be done (and already is, I believe). The only thing that the system is doing while waiting for poweroff is "sleep 15m; reboot"---no disks need to be spinning for that. > 4. It is very probable that in any non-home scenarios, an UPS will protect > more than one equipment. In those scenarios, the UPS is configured to NOT > accept "immediate shutdown the load" command from any of the equipments, > just from the main controller host. Nut is geared to work fine and > specifically support such configurations. This has to be taken into > account. Isn't this already the case for non-networked UPSes? When the interface is serial or USB, it can only be connected to (and controlled by) a single, master host. > Thus, implementing the work around proposed in this bug report as a default > behaviour is not acceptable. Please revert the change, or make it optional, > and *not* enabled by default. I would go even further and actively > discourage heavily the use of this option, as it can damage the hardware. I think you'll take issue with the NUT documentation, then, as it specifically suggests this approach. --Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: found 358696 in 2.0.4-1
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.20 > found 358696 2.0.4-1 Bug#358696: Avoiding halt and rebooting blindly is dangerous Bug marked as found in version 2.0.4-1. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: notfound 358696 in 2.0.3-4
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.20 > notfound 358696 2.0.3-4 Bug#358696: Avoiding halt and rebooting blindly is dangerous Bug marked as not found in version 2.0.3-4. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380240: sn: Doubled configuration value causes data loss
On 28-Jul-06, 11:05 (CDT), Steve Greenland <[EMAIL PROTECTED]> wrote: > I can recover this > data by clearing out the entire spool directory and refetching > for the upstream server Actually, I can't, because sn renumbers articles, and thus my newsrc will be out-of-sync. Steve -- Steve Greenland The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. -- seen on the net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#353092: No release since 2004
Hi, The package hadn't seen an update since 2004 and the bug you reported will need an updated version. Is there a reason to keep alicq? Are there no alternatives that you can find? Since upstream seems to be abandoned I think that the only recourse Debian can take to fix the bug is to remove the package. Regards, Baruch Even -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: This is dangerous, please make it default to disabled
Processing commands for [EMAIL PROTECTED]: > Version: 2.0.4-1 Unknown command or malformed arguments to command. > reopen 358696 ! Bug#358696: nut: problem with init script "poweroff" command behavior 'reopen' is deprecated when a bug has been closed with a version; use 'found' or 'submitter' as appropriate instead. Bug reopened, originator set to Henrique de Moraes Holschuh <[EMAIL PROTECTED]>. > retitle 358696 Avoiding halt and rebooting blindly is dangerous Bug#358696: nut: problem with init script "poweroff" command behavior Changed Bug title. > severity 358696 grave Bug#358696: Avoiding halt and rebooting blindly is dangerous Severity set to `grave' from `important' > found 2.0.4-1 Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380247: bacula-doc: FTBFS: Manual contains LaTeX errors
severity 380247 normal thanks On Fri, Jul 28, 2006 at 06:54:16PM +0200, Frank Küster wrote: > Package: bacula-doc > Severity: serious > Tags: patch > > latex bacula.tex will fail, even when all needed depends are installed. I just built it again, and it works. What exactly are you seeing? > The files are full of further LaTeX problems: Use of the obsolete \bf > command instead of \bfseries (will cause trouble when fonts are changed, > and the letter kerning might already be amiss), declaration of a new > fontsize with hard-coded cmr which might also cause trouble, etc.pp. I would be happy to forward that on to upstream. > Note that the attached patch loads the non-free html.sty, because the > original document uses commands from it. I'm going to file a separate > bug about this. Unfortunately, that means I can't apply it. Until I see some actual evidence that there is an actual problem, I don't see what the problem is. -- John
Processed: Re: Bug#380247: bacula-doc: FTBFS: Manual contains LaTeX errors
Processing commands for [EMAIL PROTECTED]: > severity 380247 normal Bug#380247: bacula-doc: FTBFS: Manual contains LaTeX errors Severity set to `normal' from `serious' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#374946: 374946 still present in cupsys 1.2.2-1
The same problem still persists here after upgrading to 1.2.2-1; all my network printers are out of business. Only versions 1.2.1-2 and earlier work, so downgrading is at the moment the only workaround. > - Could you try to update cups to 1.2.2-1? > - If you still have a problem, please set LogLevel debug in > cupsd.conf and restart. Is there any message in > /var/log/cups/error_log? > - Please send me your /etc/cups/cupd.conf after the update. I'll try to do this by the end of the day, after the work. Best, Slaven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#380249: bacula-doc: FTBFS: Missing Build-Depends on non-free latex2html
Processing commands for [EMAIL PROTECTED]: > severity 380249 normal Bug#380249: bacula-doc: FTBFS: Missing Build-Depends on non-free latex2html Severity set to `normal' from `serious' > tags unreproducible Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380254: yelp crashes on start
Package: yelp Version: 2.14.2-2 Severity: grave Yelp crashes spontaneously a few seconds after start (either from the commnd line, or from an application's help menu). The bug buddy thingy gives a huge backtrace, which I'm attaching. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.9 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages yelp depends on: ii docbook-xml4.4-5 standard XML documentation system, ii gconf2 2.14.0-1 GNOME configuration database syste ii gnome-doc-utils0.6.1-1 a collection of documentation util ii libatk1.0-01.12.1-1 The ATK accessibility toolkit ii libbonobo2-0 2.14.0-1 Bonobo CORBA interfaces library ii libbz2-1.0 1.0.3-3 high-quality block-sorting file co ii libc6 2.3.6-16 GNU C Library: Shared libraries ii libgcc11:4.1.1-9 GCC support library ii libgconf2-42.14.0-1 GNOME configuration database syste ii libglade2-01:2.5.1-2+b1 library to load .glade files at ru ii libglib2.0-0 2.10.3-3 The GLib library of C routines ii libgnome2-02.14.1-2 The GNOME 2 library - runtime file ii libgnomeprint2.2-0 2.12.1-3 The GNOME 2.2 print architecture - ii libgnomeprintui2.2-0 2.12.1-4 GNOME 2.2 print architecture User ii libgnomeui-0 2.14.1-2 The GNOME 2 libraries (User Interf ii libgnomevfs2-0 2.14.2-1 GNOME virtual file-system (runtime ii libgtk2.0-02.8.18-1 The GTK+ graphical user interface ii liborbit2 1:2.14.0-2libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.12.3-1+b1 Layout and rendering of internatio ii libpopt0 1.10-2lib for parsing cmdline parameters ii libstartup-notification0 0.8-1 library for program launch feedbac ii libstdc++6 4.1.1-9 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.0-7 X11 client-side library ii libxml22.6.26.dfsg-2 GNOME XML library ii libxslt1.1 1.1.17-2 XSLT processing library - runtime ii libxul0d 1.8.0.4-1 Gecko engine library ii xml-core 0.09-0.1 XML infrastructure and XML catalog ii zlib1g 1:1.2.3-13compression library - runtime yelp recommends no packages. -- no debconf information backtrace.txt.gz Description: Binary data
Bug#377841: marked as done (FTBFS: error: missing terminating " character)
Your message dated Fri, 28 Jul 2006 19:33:38 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#377841: FTBFS: error: missing terminating " character has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: libflorist-3.15p-1 Version: 3.15p-4 Severity: serious Your package fails to build in unstable: > Automatic build of libflorist-3.15p-1_3.15p-4 on > test.track.rz.uni-augsburg.de by sbuild/powerpc 0.47 ... > gnatgcc -w -g -O2 -DVERSION="\"Florist-3.15p (20020604)\"" -DLIBS="\"-lnsl > -lrt -lpthread \"" -o c-posix c-posix.c -lnsl -lrt -lpthread > c-posix.c: In function 'create_c': > c-posix.c:6347: error: missing terminating " character > c-posix.c:6348: error: expected identifier before '.' token > c-posix.c:6348: error: expected ')' before ';' token > c-posix.c:6348: error: stray '\' in program > c-posix.c:6348: error: missing terminating " character > c-posix.c:6349: error: expected ';' before '}' token > make[1]: *** [c-posix] Error 1 -- Martin Michlmayr http://www.cyrius.com/ --- End Message --- --- Begin Message --- The package has just been removed from the archive. I will upload a new version under a different name, i.e. source package: libflorist (= 2006-1) binary packages: libflorist-dev, libflorist2006 But that will have to wait until August. -- Ludovic Brenta. --- End Message ---
Bug#379555: bacula-doc: FTBFS: Missing Build-Depends on 'tetex-bin'
Andreas Jochens <[EMAIL PROTECTED]> wrote: > Please add the missing Build-Depends on 'tetex-bin' to debian/control. tetex-bin is not sufficient, tetex-extra is needed. Please also allow TeXLive to be used instead of teTeX, since teTeX is dead upstream and will be superceded by TeXLive. This makes the following Build-Depends line: > Regards > Andreas Jochens > > diff -urN ../tmp-orig/bacula-doc-1.38.11.1/debian/control ./debian/control > --- ../tmp-orig/bacula-doc-1.38.11.1/debian/control 2006-07-24 > 09:27:34.0 + > +++ ./debian/control 2006-07-24 09:27:31.0 + > @@ -2,7 +2,7 @@ > Section: doc > Priority: optional > Maintainer: John Goerzen <[EMAIL PROTECTED]> > -Build-Depends: debhelper (>= 5) > +Build-Depends: debhelper (>= 5), tetex-bin > Standards-Version: 3.7.2 Build-Depends: debhelper (>= 5), tetex-extra | texlive-latex-recommended, tetex-extra | texlive-fonts-recommended Regards, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Bug#380249: bacula-doc: FTBFS: Missing Build-Depends on non-free latex2html
severity 380249 normal tags unreproducible thanks On Fri, Jul 28, 2006 at 07:03:18PM +0200, Frank Küster wrote: > bacula.tex (or in fact bacula.sty which it uses) needs html.sty. The > \usepackage- or \RequirePackage-line is missing (included in the patch > for the other FTBFS bug I filed), but it uses commands from html.sty, > and I have no idea where else they could be defined. It builds fine for me, and I don't have latex2html installed. Just saying "this shouldn't work, but it does, and I don't know why" is neither helpful nor serious. I specifically removed the line that includes html.sty to make it work without latex2html. I am not a TeX expert, but it works. > - stop creating the html documentation, fix the document to use only > hyperref commands to typset its URLs HTML documentation isn't generated now.
Processed: closing 368883
Processing commands for [EMAIL PROTECTED]: > close 368883 Bug#368883: qt4-x11: FTBFS on alpha 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Filipus Klutiero <[EMAIL PROTECTED]> > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380249: bacula-doc: FTBFS: Missing Build-Depends on non-free latex2html
Package: bacula-doc Severity: serious bacula.tex (or in fact bacula.sty which it uses) needs html.sty. The \usepackage- or \RequirePackage-line is missing (included in the patch for the other FTBFS bug I filed), but it uses commands from html.sty, and I have no idea where else they could be defined. This would put bacula-doc into contrib. However, there are alternatives: - stop creating the html documentation, fix the document to use only hyperref commands to typset its URLs - fix the document to use only hyperref commands to typeset its URLs, and try to use hevea or tex4ht to create html (I have no experience with hevea, but some good with tex4ht). Should you need any help with LaTeX code, feel free to contact the [EMAIL PROTECTED] mailinglist. Regards, Frank -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (99, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.16-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Bug#380250: tpkg-debarch should support "arm-linux-gnu" target (was Re: small quirks setting up a cross-compile toolchain)
Package: toolchain-source Severity: grave Tags: patch toolchain-source as it stands is currently unusable for building ARM cross-compiler targets. It appears that you must specify "arm-linux-gnu" to several of the builds in order to get the install to work correctly. However, this target is not supported by tpkg-debarch. The attached patch is not a complete solution, but it at least makes it *possible* to build for arm again (so long as you use the magic "arm-linux-gnu" incantation). Nathanael Nerode <[EMAIL PROTECTED]> wrote: > See, there's your problem. Try: > tpkg-make arm-linux-gnu > TPKG_SERVER=ftp.yi.org tpkg-install-libc arm-linux-gnu > > And you should end up with only arm-linux-gnu. > > For obscure reasons (which I would like to get rid of), some parts of the > cross-tools structure care about exactly what form of the system name you > give to the tools, while others use the canonical name. > > If you still end up with two different things come back and complain to > whoever's generating arm-linux. Okay, so when I did that, I would get this message every so often: "Hmph - dunno the arm-linux-gnu arch" ... and then eventually: http://ftp.yi.org/debian/dists/testing/main/binary-none/Packages.gz => /tmp/tpkg-install-libc.CMosC11963/packageset.gz' Resolving ftp.yi.org... 209.172.55.241 Connecting to ftp.yi.org|209.172.55.241|:80... connected. HTTP request sent, awaiting response... 404 Not Found 09:49:26 ERROR 404: Not Found. binary-none, eh? So I added "arm-linux-gnu" to tpkg-debarch, and that made it work!!! --- /usr/bin/tpkg-debarch 2005-01-06 08:26:04.0 -0800 +++ /usr/bin/tpkg-debarch.new 2006-07-28 10:10:29.0 -0700 @@ -4,7 +4,7 @@ alpha-linux) debarch=alpha ;; -arm-linux|arm) +arm-linux|arm-linux-gnu|arm) debarch=arm ;; hppa-linux|hppa)
Bug#380247: bacula-doc: FTBFS: Manual contains LaTeX errors
Package: bacula-doc
Severity: serious
Tags: patch
latex bacula.tex will fail, even when all needed depends are installed.
No idea how you managed to build it in the first place. Attached is a
patch that makes it run. I did not check the output.
The files are full of further LaTeX problems: Use of the obsolete \bf
command instead of \bfseries (will cause trouble when fonts are changed,
and the letter kerning might already be amiss), declaration of a new
fontsize with hard-coded cmr which might also cause trouble, etc.pp.
Note that the attached patch loads the non-free html.sty, because the
original document uses commands from it. I'm going to file a separate
bug about this.
Regards, Frank
diff -Nur bacula-doc-1.38.11.1.old/manual/autochangers.tex
bacula-doc-1.38.11.1/manual/autochangers.tex
--- bacula-doc-1.38.11.1.old/manual/autochangers.tex2006-04-14
19:08:57.0 +0200
+++ bacula-doc-1.38.11.1/manual/autochangers.tex2006-07-28
16:54:40.0 +0200
@@ -98,7 +98,7 @@
\footnotesize
\begin{verbatim}
-cat /proc/scsi/sg/device_hdr /proc/scsi/sg/devices
+cat /proc/scsi/sg/device\_hdr /proc/scsi/sg/devices
\end{verbatim}
\normalsize
Binary files bacula-doc-1.38.11.1.old/manual/bacula.pdf and
bacula-doc-1.38.11.1/manual/bacula.pdf differ
diff -Nur bacula-doc-1.38.11.1.old/manual/bacula.sty
bacula-doc-1.38.11.1/manual/bacula.sty
--- bacula-doc-1.38.11.1.old/manual/bacula.sty 2005-05-13 19:23:00.0
+0200
+++ bacula-doc-1.38.11.1/manual/bacula.sty 2006-07-28 17:17:48.0
+0200
@@ -27,8 +27,9 @@
\ProvidesPackage{bacula}[2005/01/09]
%%
%%
+\RequirePackage{html}
\newcommand*{\elink}[2]{%
- \htmladdnormallink{#1}{#2}%
+ \href{#1}{#2}% url/hyperref, no need to escape #
}
%%
\newcommand*{\ilink}[2]{%
diff -Nur bacula-doc-1.38.11.1.old/manual/bacula.tex
bacula-doc-1.38.11.1/manual/bacula.tex
--- bacula-doc-1.38.11.1.old/manual/bacula.tex 2006-07-28 18:52:39.0
+0200
+++ bacula-doc-1.38.11.1/manual/bacula.tex 2006-07-28 18:35:39.0
+0200
@@ -35,16 +35,14 @@
\title{\includegraphics{./bacula-logo.eps} \\ \bigskip
\begin{center}
- \large{It comes in the night and sucks
- the essence from your computers. }
+\large{}It comes in the night and sucks the essence from your
+computers.
\end{center}
}
\author{Kern Sibbald}
-\date{\vspace{1.0in}\today \\
- This manual documents Bacula version \input{version} \\
- \vspace{0.2in}\\
- Copyright \copyright 1999-2006, Kern Sibbald \\
- \vspace{0.2in}\\
+\date{\vspace{1.0in}\today % \\
+ This manual documents Bacula version \input{version} \\[0.5in]
+ Copyright \copyright 1999-2006, Kern Sibbald \\[0.5in]
Permission is granted to copy, distribute and/or modify this document under
the terms of the \\
GNU Free Documentation License, Version 1.2 published by the Free Software
Foundation; \\
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. \\
diff -Nur bacula-doc-1.38.11.1.old/manual/bootstrap.tex
bacula-doc-1.38.11.1/manual/bootstrap.tex
--- bacula-doc-1.38.11.1.old/manual/bootstrap.tex 2006-01-17
10:36:36.0 +0100
+++ bacula-doc-1.38.11.1/manual/bootstrap.tex 2006-07-28 17:47:22.0
+0200
@@ -11,7 +11,7 @@
own bootstrap files, or so that you can edit a bootstrap file produced by {\bf
Bacula}. However, normally the bootstrap file will be automatically created
for you during the
-\ilink{restore_command}{_ConsoleChapter} command in the Console program, or
+\ilink{restore-command}{_ConsoleChapter} command in the Console program, or
by using a
\ilink{ Write Bootstrap}{writebootstrap} record in your Backup
Jobs, and thus you will never need to know the details of this file.
diff -Nur bacula-doc-1.38.11.1.old/manual/catmaintenance.tex
bacula-doc-1.38.11.1/manual/catmaintenance.tex
--- bacula-doc-1.38.11.1.old/manual/catmaintenance.tex 2006-04-14
19:08:57.0 +0200
+++ bacula-doc-1.38.11.1/manual/catmaintenance.tex 2006-07-28
18:17:44.0 +0200
@@ -199,7 +199,7 @@
in the time to insert or search for records.
For each of the databases, you may get significant improvements by adding
-additional indexes. The comments in the Bacula make_xxx_tables give some
+additional indexes. The comments in the Bacula make\_xxx\_tables give some
indications as to what indexes may be appropriate. Please see below
for specific instructions on checking indexes.
@@ -226,9 +226,9 @@
There is also a PostgreSQL FAQ question number 3.3 that may
answer some of your questions about how to improve performance
of the PostgreSQL engine:
-\elink{
+\href{
http://www.postgresql.org/docs/faqs.FAQ.html#3.3}
-{http://www.postgresql.org/docs/faqs.FAQ.html#3.3}.
+{http://www.postgresql.org/docs/faqs.FAQ.html\#3.3}.
\subsection*{Performance Issues Indexes}
diff -Nur bacula-doc-1.38.11.1.old/manual/configure.tex
bacula-doc-1.38.11.1/manual/configure.tex
--- bacula-doc-1.38.11.1.
Bug#379819: marked as done (FTBFS: doesn't recognize autoconf 2.60)
Your message dated Fri, 28 Jul 2006 19:00:23 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#379819: FTBFS: doesn't recognize autoconf 2.60 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: keybled Version: 0.65-6 Severity: serious Your package fails to build from source because it doesn't recognize Autoconf 2.60. A patch similar to http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946 should fix this problem. For some background, please see the discussion at http://lists.debian.org/debian-devel/2006/07/msg00958.html > Automatic build of keybled_0.65-6 on usurper by sbuild/amd64 0.46 ... > make[1]: Entering directory `/build/tbm/keybled-0.65' > *** YOU'RE USING autoconf (GNU Autoconf) 2.60. > *** KDE requires autoconf 2.53 or newer > make[1]: *** [cvs] Error 1 > make[1]: Leaving directory `/build/tbm/keybled-0.65' > make: *** [build-stamp] Error 2 -- Martin Michlmayr http://www.cyrius.com/ --- End Message --- --- Begin Message --- Version: 0.65-7 This bug has been fixed in version 0.65-7. Closing the bug. On Tue, Jul 25, 2006 at 08:59:15PM +0200, Martin Michlmayr wrote: > Package: keybled > Version: 0.65-6 > Severity: serious > > Your package fails to build from source because it doesn't recognize > Autoconf 2.60. A patch similar to > http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946 > should fix this problem. For some background, please see the > discussion at > http://lists.debian.org/debian-devel/2006/07/msg00958.html > > > > Automatic build of keybled_0.65-6 on usurper by sbuild/amd64 0.46 > ... > > make[1]: Entering directory `/build/tbm/keybled-0.65' > > *** YOU'RE USING autoconf (GNU Autoconf) 2.60. > > *** KDE requires autoconf 2.53 or newer > > make[1]: *** [cvs] Error 1 > > make[1]: Leaving directory `/build/tbm/keybled-0.65' > > make: *** [build-stamp] Error 2 > > -- > Martin Michlmayr > http://www.cyrius.com/ > > -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net --- End Message ---
Bug#379895: Patch for two RC bugs
tag 379261 + patch tag 379895 + patch thanks Hi, Attached to this mail is a patch which fixes two RC bugs. Greetings Arjan --- yacas-1.0.57/debian/control +++ yacas-1.0.57/debian/control @@ -3,7 +3,7 @@ Priority: extra Maintainer: Gopal Narayanan <[EMAIL PROTECTED]> Standards-Version: 3.6.1.1 -Build-Depends: lynx,libfltk1.1-dev,debhelper (>=2.0.86),docbook-to-man, libgsl0-dev, automake, autoconf, freeglut3-dev, libxmu-dev, libxt-dev +Build-Depends: lynx,libfltk1.1-dev,debhelper (>=2.0.86),docbook-to-man, libgsl0-dev, automake, autoconf, freeglut3-dev, libxmu-dev, libxt-dev, libxi-dev Package: yacas Architecture: any --- yacas-1.0.57/debian/rules +++ yacas-1.0.57/debian/rules @@ -57,7 +57,8 @@ dh_clean -k dh_installdirs dh_installdocs -a - $(MAKE) prefix=`pwd`/debian/yacas/usr \ + $(MAKE) datarootdir=`pwd`/debian/yacas/usr/share \ + prefix=`pwd`/debian/yacas/usr \ sysconfdir=`pwd`/debian/yacas/etc install above=`pwd` # cd proteus; $(MAKE) prefix=$(ABOVE)/debian/yacas-proteus/usr etcprefix=$(ABOVE)/debian/yacas-proteus install -f makefile.linux --- yacas-1.0.57/debian/changelog +++ yacas-1.0.57/debian/changelog @@ -1,3 +1,12 @@ +yacas (1.0.57-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * Urgency medium because it fixes two RC bugs. + * Add build dependency on libxi-dev. (Closes: #379261) + * Call make install with datarootdir variable. (Closes: #379895) + + -- Arjan Oosting <[EMAIL PROTECTED]> Fri, 28 Jul 2006 17:08:24 +0200 + yacas (1.0.57-2.1) unstable; urgency=low * NMU to fix the bugs listed below, as the maintainer appears to be MIA. signature.asc Description: Dit berichtdeel is digitaal ondertekend
Processed: Patch for two RC bugs
Processing commands for [EMAIL PROTECTED]: > tag 379261 + patch Bug#379261: FTBFS: /usr/bin/ld: cannot find -lXi There were no tags set. Tags added: patch > tag 379895 + patch Bug#379895: yacas: FTBFS: tries to install under / There were no tags set. Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380241: gnupg-agent: gpgkey2ssh has no man page, no --help, no -h and fails with assertions
Package: gnupg-agent Version: 1.9.20-1.1 Severity: grave Justification: renders package unusable I just can't know how to use that piece of shi^H^Hoftware that has no help, no -h, no --help, nor man page, and fails with horrible assertions errors when you lauch it: dcoder hades] gpgkey2ssh gpgkey2ssh: gpgkey2ssh.c:255: main: Assertion `argc == 2' failed. [1]16608 abort gpgkey2ssh [madcoder hades] gpgkey2ssh --help gpgkey2ssh: gpgkey2ssh.c:269: main: Assertion `(algorithm_id == 1) || (algorithm_id == 17)' failed. [1]16609 abort gpgkey2ssh --help [madcoder hades] gpgkey2ssh -h gpgkey2ssh: gpgkey2ssh.c:269: main: Assertion `(algorithm_id == 1) || (algorithm_id == 17)' failed. [1]16620 abort gpgkey2ssh -h -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380240: sn: Doubled configuration value causes data loss
Package: sn Version: 0.3.8-4 Severity: grave (A note about the "grave" severity: I lost data. I can recover this data by clearing out the entire spool directory and refetching for the upstream server, but that's not really ideal, is it? It's not significantly different than a mail client deleting messages unexpectedly.) In /etc/cron.daily/sn, there is a setting for the EXPIRETIME variable. I set this to "1y". Nonetheless, I discovered this morning that everything older than a week had been expired, because EXPIRETIME was overridden in the /etc/news/sn/debian_config file. There was no hint that variable was set in two different places. The installation config did not prompt for a default expire time, as it did for the other two values in debian_config. The value was specified in the cron.daily/sn file (which *is* a configuration file) with no warning that it might be overridden. README.Debian doesn't document the use of debian_config. Suggestions: 1. Remove EXPIRETIME from debian_config. Since you're not going to prompt for it during install, it shouldn't be in that file. 2. Remove the definition of EXPIRETIME from cron.daily/sn: at least then I'd have a hint that it was being set from somewhere else. Bonus points for including comment that tells the user where it should be set, rather than making them hunt for it. Regards, Steve -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (900, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-686 Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=ANSI_X3.4-1968) Versions of packages sn depends on: ii debconf [debconf 1.5.2 Debian configuration management sy ii ed 0.2-20 The classic unix line editor ii libc62.3.6-16GNU C Library: Shared libraries ii mailx1:8.1.2-0.20050715cvs-1 A simple mail user agent ii netbase 4.25Basic TCP/IP networking system ii postfix [mail-tr 2.2.10-2A high-performance mail transport ii psmisc 22.2-1 Utilities that use the proc filesy ii tcpd 7.6.dbs-9 Wietse Venema's TCP wrapper utilit ii zlib1g 1:1.2.3-13 compression library - runtime sn recommends no packages. -- debconf information: * sn/onlylocal: false * sn/runfrom: manually -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380161: marked as done (tuxtype: still ships /usr/share/tuxtype/data)
Your message dated Fri, 28 Jul 2006 08:32:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#380161: fixed in tuxtype 1.5.6.dfsg1-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: tuxtype Version: 1.5.6.dfsg1-2 Severity: grave Justification: renders package unusable tuxtype continues to ship the entire /usr/share/tuxtype/data hierarchy itself, leading to a massive file conflict with tuxtype-data. Could you please drop the duplicate files for real? -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.1 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages tuxtype depends on: ii libc6 2.3.6-16 GNU C Library: Shared libraries ii libsdl-image1.21.2.5-2 image loading library for Simple D ii libsdl-mixer1.21.2.6-1.1 mixer library for Simple DirectMed ii libsdl-ttf2.0-02.0.8-2 ttf library for Simple DirectMedia ii libsdl1.2debian1.2.11-1 Simple DirectMedia Layer ii ttf-gentium1.02-2Gentium TrueType font ii tuxtype-data 1.5.6.dfsg1-2 Data files for the Educational Typ tuxtype recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: tuxtype Source-Version: 1.5.6.dfsg1-3 We believe that the bug you reported is fixed in the latest version of tuxtype, which is due to be installed in the Debian FTP archive: tuxtype-data_1.5.6.dfsg1-3_all.deb to pool/main/t/tuxtype/tuxtype-data_1.5.6.dfsg1-3_all.deb tuxtype_1.5.6.dfsg1-3.diff.gz to pool/main/t/tuxtype/tuxtype_1.5.6.dfsg1-3.diff.gz tuxtype_1.5.6.dfsg1-3.dsc to pool/main/t/tuxtype/tuxtype_1.5.6.dfsg1-3.dsc tuxtype_1.5.6.dfsg1-3_i386.deb to pool/main/t/tuxtype/tuxtype_1.5.6.dfsg1-3_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Holger Levsen <[EMAIL PROTECTED]> (supplier of updated tuxtype package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Jul 2006 11:59:56 + Source: tuxtype Binary: tuxtype-data tuxtype Architecture: source i386 all Version: 1.5.6.dfsg1-3 Distribution: unstable Urgency: low Maintainer: Holger Levsen <[EMAIL PROTECTED]> Changed-By: Holger Levsen <[EMAIL PROTECTED]> Description: tuxtype- Educational Typing Tutor Game Starring Tux tuxtype-data - Data files for the Educational Typing Tutor Game Starring Tux Closes: 380161 Changes: tuxtype (1.5.6.dfsg1-3) unstable; urgency=low . * fix debian rules, so binary-indep target is only build when that target is called (Closes: #380161) Files: e6baeacab9f90ab110255b123639490d 674 games optional tuxtype_1.5.6.dfsg1-3.dsc d33260526a31575ac948fc1cc484333f 9088 games optional tuxtype_1.5.6.dfsg1-3.diff.gz 46af9c3cfedb3223cffe8ddedbd07bb0 6751730 games optional tuxtype-data_1.5.6.dfsg1-3_all.deb e259e707f95a9923f225fd4be4c58623 57690 games optional tuxtype_1.5.6.dfsg1-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEyilceYl9593Atw0RAnLyAKCY9P/LtFy3MkWnH/nkvj+4H8OYEwCeM/vN SCKoiGbeKvMep4jVcrJaGw0= =xnSr -END PGP SIGNATURE- --- End Message ---
Processed: Re: Processed: Re: Bug#379835: NTFS (partition) not recreated correctly after resize: incorrect start sector
Processing commands for [EMAIL PROTECTED]: > reassign 380226 parted 1.7.1-2.1 Bug#380226: NTFS (partition) not recreated correctly after resize:incorrect start sector Warning: Unknown package 'libparted' Bug reassigned from package `libparted' to `parted'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380220: bacula-director-mysql: Start fails with *** glibc detected *** free(): invalid pointer: 0x080ea648 ***
tags 380220 unreproducible severity 380220 important thanks On Fri, Jul 28, 2006 at 03:36:51PM +0200, root wrote: > Version: 1.38.11-1 > Severity: grave > Justification: renders package unusable I can't duplicate this. I will need some more information -- specifically, your bacula-dir.conf file and the steps you took to cause it. Does it do this even with the vanilla out of the box package? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#380220: bacula-director-mysql: Start fails with *** glibc detected *** free(): invalid pointer: 0x080ea648 ***
Processing commands for [EMAIL PROTECTED]: > tags 380220 unreproducible Bug#380220: bacula-director-mysql: Start fails with *** glibc detected *** free(): invalid pointer: 0x080ea648 *** There were no tags set. Tags added: unreproducible > severity 380220 important Bug#380220: bacula-director-mysql: Start fails with *** glibc detected *** free(): invalid pointer: 0x080ea648 *** Severity set to `important' from `grave' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380231: [CVE-2006-3747] Off-by-one flaw exists in the Rewrite module, mod_rewrite
On Fri, Jul 28, 2006 at 05:06:38PM +0200, Daniel Leidert wrote: > The latest release notes [1] of apache 1.3.37, 2.0.59 and 2.2.3 contains a > note, about an off-by-one flaw (CVE-2006-3747 [2]). > > [1] http://www.apache.org/dist/httpd/Announcement2.2.html > [2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3747 > > Please check, if the Debian package(s) is/are vulnerable. apache + apache2 packages are affected. DSA in preparation. Thanks for the report. (Please see also #380182) Steve -- signature.asc Description: Digital signature
Bug#380128: info: Incorrect (?) (unclear) copyright statement
Hi Karl! We got notified that info and its man page refer to GPL without v2, while the COPYING file refers to GPLv2. On Don, 27 Jul 2006, Helge Kreutzmann wrote: > The file /usr/share/doc/info/copyright contains: > This program is free software; you can redistribute it and/or modify > it under the terms of the GNU General Public License as published by > the Free Software Foundation; either version 2, or (at your option) > any later version. > > ... > > On Debian GNU/Linux systems, the complete text of the GNU General > Public License can be found in `/usr/share/common-licenses/GPL' file. > > > However, both the man page for info as well as info clearly state: > >Copyright C 2004 Free Software Foundation, Inc. There is NO warranty. >You may redistribute this software under the terms of the GNU General >Public License. For more information about these matters, see the >files named COPYING. > > and > > There is NO warranty. You may redistribute this software > under the terms of the GNU General Public License. > For more information about these matters, see the files named COPYING. > > > Since the file COPYING is not shipped by Debian, I could not check there. [...] > Given the authorship, I assume this is an (consistent) oversight in the > source for both the man page and the programm itself. For clarity, > COPYING should be checked. > > I suggest the following: > *Contact upstream and ask to clarify > *Patch both the man page and the programm to refer to > /usr/share/doc/info/copyright > instead of the file "COPYING" so that the reader is drawn to a file > actually shipped in the package (or, alternativly, ship COPYING as > well). I assume that info is also GPLv2 as I stated in the copyright file, and as specified in the COPYING file. So is it ok that I patch the info man page and program to give this more specific version GPLv2? Thanks a lot and all the best! Norbert --- Dr. Norbert Preining Università di Siena gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- Rome wasn't burned in a day. --- Douglas Adams, The Hitchhikers Guide to the Galaxy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380231: [CVE-2006-3747] Off-by-one flaw exists in the Rewrite module, mod_rewrite
Package: apache Version: 1.3.34-2 Severity: grave Tags: security -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The latest release notes [1] of apache 1.3.37, 2.0.59 and 2.2.3 contains a note, about an off-by-one flaw (CVE-2006-3747 [2]). [1] http://www.apache.org/dist/httpd/Announcement2.2.html [2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3747 Please check, if the Debian package(s) is/are vulnerable. Regards, Daniel - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.08060320 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages apache depends on: ii apache-common 1.3.34-2 support files for all Apache webse ii debconf [debconf-2.0] 1.5.2 Debian configuration management sy ii libc6 2.3.6-16 GNU C Library: Shared libraries ii libdb4.3 4.3.29-6 Berkeley v4.3 Database Libraries [ ii libexpat1 1.95.8-3.2 XML parsing C library - runtime li ii libmagic1 4.17-2 File type determination library us ii logrotate 3.7.1-3Log rotation utility ii lsb-base 3.1-10 Linux Standard Base 3.1 init scrip ii mime-support 3.37-1 MIME files 'mime.types' & 'mailcap ii perl 5.8.8-6Larry Wall's Practical Extraction apache recommends no packages. - -- debconf information excluded -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEyif+dg0kG0+YFBERAiX2AJ98Pu062RB/oGwJl2203bfkT+l9FQCeONDR 2xQ6gHZYpYvpau1HDRhoZqE= =goy6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Fixed in NMU of quiteinsanegimpplugin 0.3-6.1
Processing commands for [EMAIL PROTECTED]: > tag 379830 + fixed Bug#379830: FTBFS: doesn't recognize autoconf 2.60 There were no tags set. Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#374264: Fix for this bug
This patch fixes the bug. A "dch -r" should be enough before upload. diff -urN cinepaint-0.20-1.orig/debian/changelog cinepaint-0.20-1/debian/changelog --- cinepaint-0.20-1.orig/debian/changelog 2006-07-28 15:08:39.0 +0200 +++ cinepaint-0.20-1/debian/changelog 2006-07-28 15:15:43.862278728 +0200 @@ -1,3 +1,11 @@ +cinepaint (0.20-1-1.3) UNRELEASED; urgency=low + + * NMU + * debian/rules: +- Remove link flag "--as-needed" (closes: #374264, #367543) + + -- Oystein Gisnas <[EMAIL PROTECTED]> Fri, 28 Jul 2006 15:13:22 +0200 + cinepaint (0.20-1-1.2) unstable; urgency=low * NMU diff -urN cinepaint-0.20-1.orig/debian/rules cinepaint-0.20-1/debian/rules --- cinepaint-0.20-1.orig/debian/rules 2006-07-28 15:08:39.0 +0200 +++ cinepaint-0.20-1/debian/rules 2006-07-28 15:12:35.434924040 +0200 @@ -12,8 +12,6 @@ include /usr/share/cdbs/1/class/autotools.mk include /usr/share/cdbs/1/rules/simple-patchsys.mk -DEB_CONFIGURE_EXTRA_FLAGS := "LDFLAGS=-Wl,--as-needed" - # Debhelper Arguments DH_ALWAYS_EXCLUDE := CVS:.svn DEB_DH_INSTALL_ARGS := --sourcedir=debian/tmp signature.asc Description: Dette er en digitalt signert meldingsdel
Bug#377299: sitebar: CVE-2006-3320: cross-site scripting
Thijs Kinkhorst wrote: > > > CVE-2006-3320: "Cross-site scripting (XSS) vulnerability in command.php > > in SiteBar 3.3.8 and earlier allows remote attackers to inject arbitrary > > web script or HTML via the command parameter." > > I've already fixed this by NMU in unstable. I've also prepared an > updated package for stable - question is if the security team wants to > release an advisory for this and if this package is ok. See attachment. > > Let me know, if it's ok I'll upload it to stable-security. Please adjust the distribution to stable-security and the urgency to high, then proceed. Regards, Joey -- Let's call it an accidental feature. -- Larry Wall Please always Cc to me when replying to me on the lists. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: phpqladmin: CVE-2006-3301: cross-site scripting
Processing commands for [EMAIL PROTECTED]: > retitle 376442 phpqladmin: many cross site scripting problems Bug#376442: phpqladmin: CVE-2006-3301: cross-site scripting Changed Bug title. > tags 376442 +upstream Bug#376442: phpqladmin: many cross site scripting problems Tags were: security Tags added: upstream > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380182: Confirmed
A security advisory is pending. This bug applies to both the apache and apache2 packages. Same fix in both packages, but in different locations... Steve -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: fixed package available at http://layer-acht.org/tuxtype - waiting for upload by sponsor...
Processing commands for [EMAIL PROTECTED]: > tag 380161 pending Bug#380161: tuxtype: still ships /usr/share/tuxtype/data There were no tags set. Tags added: pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#376442: phpqladmin: CVE-2006-3301: cross-site scripting
retitle 376442 phpqladmin: many cross site scripting problems tags 376442 +upstream thanks Hello, > CVE-2006-3301: "Multiple cross-site scripting (XSS) vulnerabilities in > phpQLAdmin 2.2.7 and earlier allow remote attackers to inject arbitrary > web script or HTML via the domain parameter in (1) user_add.php or (2) > unit_add.php." I've taken a look, and those files are indeed vulnerable, but a quick look at some of the other files in the package reveals that there are many more problems in many files, some examples: - domain_add.php $_REQUEST["domain"] - domain_add_form.php $server - domain_del.php $domain - domain_detail.php $msg - search.php $msg - ezmlm_detail.php $msg - config_detail.php $msg - user_detail.php $msg - control_detail.php $msg - home.php $msg just to name the first 10 I encountered. What next? I don't think it makes sense to create a big patch just for Debian, but rather to get a newly fixed upstream in - since upstream will need to fix this problem in any case. I propose to: - Remove the package from testing; - Keep this bug open until upstream has addressed the issues; - Package that version and only then let phpqladmin flow back into testing. Thijs signature.asc Description: This is a digitally signed message part
Bug#379835: NTFS (partition) not recreated correctly after resize: incorrect start sector
clone 379835 -1 reassign -1 libparted 1.7.1-2.1 thanks On Thursday 27 July 2006 14:05, Frans Pop wrote: > Conclusion: either resize_partition calls the wrong libparted function, > or there is a bug in parted's ped_disk_set_partition_geom function. As discussed with Otavio on IRC, this seems to be a bug in libparted. I will see if I can provide a test script that demonstrates the case. I am cloning this BR rather than reassigning it because it looks like there may be other issues as well: - start sector of partitions may change even when not resizing (see: https://launchpad.net/distros/ubuntu/+source/parted/+bug/32529) - even if I correct the physical partition and ntfsresize runs well after that, Windows Vista still refuses to boot pgpNNUaoAN6cA.pgp Description: PGP signature
Processed: reopening 379200
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.20 > reopen 379200 Bug#379200: bluez-utils: FTBFS because sudo clears the environment 'reopen' is deprecated when a bug has been closed with a version; use 'found' or 'submitter' as appropriate instead. Bug reopened, originator not changed. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#379835: NTFS (partition) not recreated correctly after resize: incorrect start sector
Processing commands for [EMAIL PROTECTED]: > clone 379835 -1 Bug#379835: NTFS (partition) not recreated correctly after resize:incorrect start sector Bug 379835 cloned as bug 380226. > reassign -1 libparted 1.7.1-2.1 Bug#380226: NTFS (partition) not recreated correctly after resize:incorrect start sector Warning: Unknown package 'libparted' Bug reassigned from package `partman-partitioning' to `libparted'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#379830: FTBFS: doesn't recognize autoconf 2.60
Hello,
> > Your package fails to build from source because it doesn't recognize
> > Autoconf 2.60.
> Aurelien is on holidays. Can someone please NMU.
I've done so. Attached is the diff.
Thijs
diff -u quiteinsanegimpplugin-0.3/debian/changelog quiteinsanegimpplugin-0.3/debian/changelog
--- quiteinsanegimpplugin-0.3/debian/changelog
+++ quiteinsanegimpplugin-0.3/debian/changelog
@@ -1,3 +1,10 @@
+quiteinsanegimpplugin (0.3-6.1) unstable; urgency=high
+
+ * Non-maintainer upload for RC bug.
+ * Fix FTBFS: doesn't recognize autoconf 2.60 (Closes: #379830).
+
+ -- Thijs Kinkhorst <[EMAIL PROTECTED]> Fri, 28 Jul 2006 15:34:57 +0200
+
quiteinsanegimpplugin (0.3-6) unstable; urgency=low
* Relibtoolize the package to get rid of a lot of unneeded
only in patch2:
unchanged:
--- quiteinsanegimpplugin-0.3.orig/admin/cvs.sh
+++ quiteinsanegimpplugin-0.3/admin/cvs.sh
@@ -29,7 +29,7 @@
{
AUTOCONF_VERSION=`$AUTOCONF --version | head -n 1`
case $AUTOCONF_VERSION in
- Autoconf*2.5* | autoconf*2.5* ) : ;;
+ Autoconf*2.5* | autoconf*2.5* | autoconf*2.6* ) : ;;
"" )
echo "*** AUTOCONF NOT FOUND!."
echo "*** KDE requires autoconf 2.52, 2.53 or 2.54"
@@ -44,7 +44,7 @@
AUTOHEADER_VERSION=`$AUTOHEADER --version | head -n 1`
case $AUTOHEADER_VERSION in
- Autoconf*2.5* | autoheader*2.5* ) : ;;
+ Autoconf*2.5* | autoheader*2.5* | autoheader*2.6* ) : ;;
"" )
echo "*** AUTOHEADER NOT FOUND!."
echo "*** KDE requires autoheader 2.52 or 2.53 (part of autoconf)"
signature.asc
Description: This is a digitally signed message part
Bug#380220: bacula-director-mysql: Start fails with *** glibc detected *** free(): invalid pointer: 0x080ea648 ***
Package: bacula-director-mysql Version: 1.38.11-1 Severity: grave Justification: renders package unusable After update bacula fails with *** glibc detected *** free(): invalid pointer: 0x080ea648 *** /etc/init.d/bacula-director start Starting Bacula Director: /usr/sbin/bacula-dir -- -c /etc/bacula/bacula-dir.conf -u bacula -g bacula *** glibc detected *** free(): invalid pointer: 0x080ea648 *** /etc/init.d/bacula-director: line 53: 21112 Aborted start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- $ARGS failed. Any hints? I'm just trying to recompile the package, .. Thanks for any help tilo [EMAIL PROTECTED] -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages bacula-director-mysql depends on: hi bacula-director-common1.38.11-1 Network backup, recovery and verif ii dbconfig-common 1.8.17 common framework for packaging dat ii debconf [debconf-2.0] 1.4.72 Debian configuration management sy ii libc6 2.3.6-16 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-9 GCC support library ii libmysqlclient15off 5.0.19-2 mysql database client library ii libssl0.9.8 0.9.8b-2 SSL shared libraries ii libstdc++64.1.1-9The GNU Standard C++ Library v3 ii libwrap0 7.6.dbs-9 Wietse Venema's TCP wrappers libra ii mysql-client 5.0.19-2 mysql database client (current ver ii mysql-client-5.0 [mysql-clien 5.0.19-2 mysql database client binaries ii python2.3 2.3.5-9.1 An interactive high-level object-o ii zlib1g1:1.2.3-11 compression library - runtime Versions of packages bacula-director-mysql recommends: ii mysql-server 5.0.19-2 mysql database server (current ver ii mysql-server-5.0 [mysql-serve 5.0.19-2 mysql database server binaries -- debconf information: bacula-director-mysql/mysql/admin-pass: (password omitted) * bacula-director-mysql/db_password: (password omitted) bacula-director-mysql/mysql_root_password: (password omitted) bacula-director-mysql/mysql/app-pass: (password omitted) bacula-director-mysql/app-password-confirm: (password omitted) bacula-director-mysql/password-confirm: (password omitted) bacula-director-mysql/mysql/admin-user: bacula-director-mysql/purge: false bacula-director-mysql/remove-error: abort bacula-director-mysql/import-oldsettings: * bacula-director-mysql/remove_catalog_on_purge: false * bacula-director-mysql/dbconfig-install: false bacula-director-mysql/db/app-user: bacula bacula-director-mysql/upgrade-backup: true bacula-director-mysql/install-error: abort bacula-director-mysql/db/dbname: bacula bacula-director-mysql/create_mysql_tables: true bacula-director-mysql/remote/host: bacula-director-mysql/upgrade-error: abort bacula-director-mysql/remote/port: bacula-director-mysql/passwords-do-not-match: * bacula-director-mysql/db_host: localhost bacula-director-mysql/dbconfig-upgrade: true bacula-director-mysql/remote/newhost: bacula-director-mysql/database-type: mysql * bacula-director-mysql/create_tables: true bacula-director-mysql/mysql/method: unix socket bacula-director-mysql/internal/reconfiguring: false * bacula-director-mysql/mysql_root_username: root bacula-director-mysql/dbconfig-reinstall: false bacula-director-mysql/dbconfig-remove: * bacula-director-mysql/db_user: bacula -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#379200: reopen bluez-utils FTBFS
found 379200 bluez-utils/3.1-3 thanks Seems like there still is one reference to $(PWD) in debian/rules. :( I'd also like to request an urgency=medium upload. Thanks, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org The surest way to corrupt a youth is to instruct him to hold in higher esteem those who think alike than those who think differently. -- F. Nietzsche
Bug#377692: phpwiki: edit any page impossible (PhotoAlbum.php complains)
Hello Matt, > Upon further investigation this seems to be just one symptom of a larger > problem. PHPwiki is being very inefficient in its use of memory. I don't think is is release critical - there's quite some applications in Debian that use a lot of memory and they aren't removed from the release too... I suggest to downgrade this to 'important'. > I'm about to upload a new package which fixes many other bugs, but I've > currently got no good solution for this other than suggesting that you > raise the memory limit in php.ini, I've documented this in the > README.Debian file. I intend to raise the issue with the PHPwiki > developers to see if they believe there is anything that can be done to > reduce the amount of memory that PHPwiki requires. That would certainly be a good idea. Good luck! Thijs signature.asc Description: This is a digitally signed message part
Bug#379982: Misuse of alternatives
Sorry, I had written this before I saw your first reply to this bug. On Fri, Jul 28, 2006 at 11:06:08AM +0100, MJ Ray wrote: > Christian Aichinger <[EMAIL PROTECTED]> wrote: > > Since that violates policy, the removal of /usr/bin/git > > As explained, I do not see why this violates policy, as the > git shell script offers the git-core functionality. I think that reasoning is flawed. gitfm offers a different functionality as git-scm. Desciding if you're running interactively or not is IMHO a hack you had to add because of #362543. If a user calls /usr/bin/git, it really _is_ completely different. > What other way is there for a neat transition for stable users? As stated above I believe it violates policy, but I happen to think that it's actually a really nice way to transition /usr/bin/git. So I'd propose to ask debian-release if we can tag this etch-ignore or downgrade to important for the timeframe of etch. That would IMHO be the nicest solution for this. Comments? HTH, Christian Aichinger signature.asc Description: Digital signature
Bug#378249: courier-authlib: doesn't use shlibs
* Charles Fry [Sat, 22 Jul 2006 13:14:29 -0400]: Uh, hi, seems like I forgot to flag this mail as needing a reply. > > As a week has passed, this bug is now 0-day NMUable. Charles, were you > > thinking on doing it yourself? (Just asking as to no step on somebody > > else's toes.) > Well, I've never dealt with an issue like this before, so I'd be much > more comfortable if someone else either did it or walked me through it. Let me know what you prefer. I'm happy both to upload a fix myself, or to help you with what you may need for uploading yoursef. > My vote would be to just include libcourierauth, since that is the only > library that is currently used external to courier itself. I am fairly > certain that the other libraries are all for internal use by courier. Okay, good. Cheers, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org Proper treatment will cure a cold in seven days, but left to itself, a cold will hang on for a week. -- Darrell Huff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: sitebar: CVE-2006-3320: cross-site scripting
Processing commands for [EMAIL PROTECTED]: > tags 377299 +patch Bug#377299: sitebar: CVE-2006-3320: cross-site scripting Tags were: fixed security Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#375077: initrd needs its own, static, nsswitch.conf
> I have 251-5 installed and am still seeing: > udevd[PID]: nss_ldap: failed to bind to LDAP server I had the same problem with 251-5. I used "compat ldap" in my nsswitch.conf, it will work if you change compat to files. Bram
Processed: Fixed in NMU of sitebar 3.3.8-1.1
Processing commands for [EMAIL PROTECTED]: > tag 377299 + fixed Bug#377299: sitebar: CVE-2006-3320: cross-site scripting Tags were: security Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#377299: sitebar: CVE-2006-3320: cross-site scripting
tags 377299 +patch thanks Hello, > CVE-2006-3320: "Cross-site scripting (XSS) vulnerability in command.php > in SiteBar 3.3.8 and earlier allows remote attackers to inject arbitrary > web script or HTML via the command parameter." I've already fixed this by NMU in unstable. I've also prepared an updated package for stable - question is if the security team wants to release an advisory for this and if this package is ok. See attachment. Let me know, if it's ok I'll upload it to stable-security. Attached are the diffs for the sid NMU and the proposed sarge NMU. Thanks. Thijs diff -u sitebar-3.2.6/debian/changelog sitebar-3.2.6/debian/changelog --- sitebar-3.2.6/debian/changelog +++ sitebar-3.2.6/debian/changelog @@ -1,3 +1,11 @@ +sitebar (3.2.6-7.1) unstable; urgency=low + + * Non-maintainer upload for security bug fix. + * Properly encode the 'command' parameter of command.php +(CVE-2006-3320, Closes: #377299). + + -- Thijs Kinkhorst <[EMAIL PROTECTED]> Fri, 28 Jul 2006 14:42:47 +0200 + sitebar (3.2.6-7) unstable; urgency=low * Updated maintainer field to reference my shiny new debian.org address only in patch2: unchanged: --- sitebar-3.2.6.orig/command.php +++ sitebar-3.2.6/command.php @@ -3814,7 +3814,7 @@ ?> -command)?> +command))?> hasErrors()) diff -u sitebar-3.3.8/debian/changelog sitebar-3.3.8/debian/changelog --- sitebar-3.3.8/debian/changelog +++ sitebar-3.3.8/debian/changelog @@ -1,3 +1,11 @@ +sitebar (3.3.8-1.1) unstable; urgency=high + + * High urgency upload for RC security bug fix. + * Properly encode the 'command' parameter of command.php +(CVE-2006-3320, Closes: #377299). + + -- Thijs Kinkhorst <[EMAIL PROTECTED]> Fri, 28 Jul 2006 14:29:31 +0200 + sitebar (3.3.8-1) unstable; urgency=low * New upstream release and new maintainer (Closes: #358893) only in patch2: unchanged: --- sitebar-3.3.8.orig/command.php +++ sitebar-3.3.8/command.php @@ -5809,7 +5809,7 @@ ?> ? -command)?> +command))?> signature.asc Description: This is a digitally signed message part
Bug#315155: fixed
Hi, http://ftp.fi.debian.org/debian/pool/main/t/tuxtype/tuxtype_1.5.6.dfsg1-2_ia64.deb shows this is fixed in the new release. regards, Holger pgp9KUersS3DF.pgp Description: PGP signature
Processed: close
Processing commands for [EMAIL PROTECTED]: > close 315155 1.5.6.dfsg1-2 Bug#315155: tuxtype depends on libstdc++2.10-glibc2.2 on ia64 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 1.5.6.dfsg1-2, send any further explanations to Matthias Klose <[EMAIL PROTECTED]> > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: jpeg-xmms build issues with gcc 4.1
Processing commands for [EMAIL PROTECTED]: > forwarded 379497 [EMAIL PROTECTED] Bug#379497: libjpeg-mmx: FTBFS: Error: suffix or operands invalid for `ldmxcsr' Noted your statement that Bug has been forwarded to [EMAIL PROTECTED] > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#379497: jpeg-xmms build issues with gcc 4.1
forwarded 379497 [EMAIL PROTECTED] thanks hi, jpeg-xmms fails to build from source using gcc 4.1: > gcc -O2 -I. -c -o fdctdata.o fdctdata.c > gcc -O2 -I. -c -o jquant_x86simd.o jquant_x86simd.c > /tmp/ccT4Nyhx.s: Assembler messages: > /tmp/ccT4Nyhx.s:59: Error: suffix or operands invalid for `ldmxcsr' > make[1]: *** [jquant_x86simd.o] Error 1 > make[1]: Leaving directory `/build/buildd/libjpeg-mmx-0.1.5' various other vendors like gentoo already use a slightly modified patch from the following bugreport filed against gcc: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26653 as it stands this is a issue with jpeg-mmx, not gcc. You can find the full bugreport (also with some ways to fix this issue) in the Debian Bug Tracking System: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379497 I'am no ASM/SSE Expert, so i think it would be best if you guys could have a look at the patches provided in the above link and could tell me if its safe to include them in the package. bye, - michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#379821: marked as done (FTBFS: doesn't recognize autoconf 2.60)
Your message dated Fri, 28 Jul 2006 04:02:16 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379821: fixed in yakuake 2.7.5-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: yakuake Version: 2.7.5-1 Severity: serious Your package fails to build from source because it doesn't recognize Autoconf 2.60. A patch similar to http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946 should fix this problem. For some background, please see the discussion at http://lists.debian.org/debian-devel/2006/07/msg00958.html > Automatic build of yakuake_2.7.5-1 on usurper by sbuild/amd64 0.46 ... > make[1]: Entering directory `/build/tbm/yakuake-2.7.5' > *** YOU'RE USING autoconf (GNU Autoconf) 2.60. > *** KDE requires autoconf 2.53 or newer > make[1]: *** [cvs] Error 1 > make[1]: Leaving directory `/build/tbm/yakuake-2.7.5' > make: *** [makebuilddir/yakuake] Error 2 -- Martin Michlmayr http://www.cyrius.com/ --- End Message --- --- Begin Message --- Source: yakuake Source-Version: 2.7.5-2 We believe that the bug you reported is fixed in the latest version of yakuake, which is due to be installed in the Debian FTP archive: yakuake_2.7.5-2.diff.gz to pool/main/y/yakuake/yakuake_2.7.5-2.diff.gz yakuake_2.7.5-2.dsc to pool/main/y/yakuake/yakuake_2.7.5-2.dsc yakuake_2.7.5-2_i386.deb to pool/main/y/yakuake/yakuake_2.7.5-2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ana Beatriz Guerrero Lopez <[EMAIL PROTECTED]> (supplier of updated yakuake package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Jul 2006 21:03:17 +0200 Source: yakuake Binary: yakuake Architecture: source i386 Version: 2.7.5-2 Distribution: unstable Urgency: medium Maintainer: Ana Beatriz Guerrero Lopez <[EMAIL PROTECTED]> Changed-By: Ana Beatriz Guerrero Lopez <[EMAIL PROTECTED]> Description: yakuake- a Quake-style terminal emulator based on KDE Konsole technology Closes: 359244 379821 Changes: yakuake (2.7.5-2) unstable; urgency=medium . * Substituting re-libtoolizing at build time with patches. (Closes: #379821) * Adding spanish translation from Juan Manuel Garcia Molina <[EMAIL PROTECTED]> (Closes: #359244) * Added copyright of the debian packaging. Files: 0081ed33fcf6ede5527462159dc3cfc0 624 kde optional yakuake_2.7.5-2.dsc 2c51af8beed9f8b9e464bdc241518274 250338 kde optional yakuake_2.7.5-2.diff.gz b10e1848cff766b5f93495b7d758ae69 74456 kde optional yakuake_2.7.5-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEyessipBneRiAKDwRAvx+AKCUaFr6xi2PTkCDfP+CMMO7DWAhegCgiWMr Eay9zWxYL7oJf541Ab0ylRM= =rnuO -END PGP SIGNATURE- --- End Message ---
Bug#380142: marked as done (libgtk-perl: FTBFS: Build-Depends on obsolete libgii0-dev)
Your message dated Fri, 28 Jul 2006 04:32:30 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#380142: fixed in libgtk-perl 0.7009-10 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: libgtk-perl Version: 0.7009-9 Severity: serious From my pbuilder build log: ... -> Attempting to parse the build-deps : pbuilder-satisfydepends,v 1.28 2006/05/30 23:45:45 dancer Exp $ -> Considering debhelper (>> 4.1) -> Trying debhelper -> Considering perl (>> 5.8.1) -> Trying perl -> Considering gtkglarea5-dev -> Trying gtkglarea5-dev -> Considering libgnomeprint-dev (>= 0.37-10) -> Trying libgnomeprint-dev -> Considering libcapplet1-dev (>= 1:1.5.11-11) -> Trying libcapplet1-dev -> Considering libgdk-pixbuf-gnome-dev (>= 0.22.0-9) -> Trying libgdk-pixbuf-gnome-dev -> Considering libggi2-dev -> Trying libggi2-dev -> Considering libgii0-dev -> Trying libgii0-dev -> Cannot install libgii0-dev; apt errors follow: Reading package lists... Done Building dependency tree... Done perl is already the newest version. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libgii0-dev: Depends: libgii0 (= 1:0.9.1-0.2) but it is not going to be installed E: Broken packages E: Could not satisfy build-dependency. E: pbuilder-satisfydepends failed. The problem is that libggi2-dev now uses libgii1 instead of libgii0, so it can't be installed along with libgii0-dev. (Actually, is there any reason to be build depending on libggi in the first place? None of the binary packages link against it.) -- Daniel Schepler --- End Message --- --- Begin Message --- Source: libgtk-perl Source-Version: 0.7009-10 We believe that the bug you reported is fixed in the latest version of libgtk-perl, which is due to be installed in the Debian FTP archive: libgdk-pixbuf-perl_0.7009-10_i386.deb to pool/main/libg/libgtk-perl/libgdk-pixbuf-perl_0.7009-10_i386.deb libgladexml-perl_0.7009-10_i386.deb to pool/main/libg/libgtk-perl/libgladexml-perl_0.7009-10_i386.deb libgnome-perl_0.7009-10_i386.deb to pool/main/libg/libgtk-perl/libgnome-perl_0.7009-10_i386.deb libgnome-print-perl_0.7009-10_i386.deb to pool/main/libg/libgtk-perl/libgnome-print-perl_0.7009-10_i386.deb libgtk-imlib-perl_0.7009-10_i386.deb to pool/main/libg/libgtk-perl/libgtk-imlib-perl_0.7009-10_i386.deb libgtk-perl_0.7009-10.diff.gz to pool/main/libg/libgtk-perl/libgtk-perl_0.7009-10.diff.gz libgtk-perl_0.7009-10.dsc to pool/main/libg/libgtk-perl/libgtk-perl_0.7009-10.dsc libgtk-perl_0.7009-10_i386.deb to pool/main/libg/libgtk-perl/libgtk-perl_0.7009-10_i386.deb libgtkglarea-perl_0.7009-10_i386.deb to pool/main/libg/libgtk-perl/libgtkglarea-perl_0.7009-10_i386.deb libgtkhtml-perl_0.7009-10_i386.deb to pool/main/libg/libgtk-perl/libgtkhtml-perl_0.7009-10_i386.deb libgtkxmhtml-perl_0.7009-10_i386.deb to pool/main/libg/libgtk-perl/libgtkxmhtml-perl_0.7009-10_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bart Martens <[EMAIL PROTECTED]> (supplier of updated libgtk-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Jul 2006 22:49:43 +0200 Source: libgtk-perl Binary: libgdk-pixbuf-perl libgtk-imlib-perl libgladexml-perl libgnome-print-perl libgtkglarea-perl libgtkxmhtml-perl libgnome-perl libgtkhtml-perl libgtk-perl Architecture: source i386 Version: 0.7009-10 Distribution: unstable Urgency: low Maintainer: Bart Martens <[EMAIL PROTECTED]> Changed-By: Bart Martens <[EMAIL PROTECTED]> Description: libgdk-pixbuf-perl - Perl module for the gdkpixbuf library libgladexml-perl - Perl module for the libglade library libgnome-perl - Perl module for the gnome and zvt libraries libgnome-print-perl - Perl module for the gnome print library libgtk-imlib-perl - Perl
Processed: updated patch
Processing commands for [EMAIL PROTECTED]: > tags 379497 + help Bug#379497: libjpeg-mmx: FTBFS: Error: suffix or operands invalid for `ldmxcsr' Tags were: patch Tags added: help > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#379497: updated patch
tags 379497 + help
thanks
hi,
see attached patch, *& can be omitted, though. Another posibility is to
use:
__asm__ ( "ldmxcsr (%0)\n" : : "X" (trunc_mxcsr) );
i lack the needed SSE/ASM/Intel know-how, tagging with help, asking
upstream for what would be the best solution. Both gentoo and other rpm
packages use the attached patch for fixing this problem.
bye,
- michael
--- libjpeg-mmx-0.1.5.orig/jquant_x86simd.c
+++ libjpeg-mmx-0.1.5/jquant_x86simd.c
@@ -104,7 +104,7 @@
/* Initialise zero block flags */
/* Set up SSE rounding mode */
- __asm__ ( "ldmxcsr %0\n" : : "X" (trunc_mxcsr) );
+ __asm__ ( "ldmxcsr %0\n" : : "m" (trunc_mxcsr) );
for (i=0; i < 64 ; i+=4)
{
Bug#379982: Misuse of alternatives
Christian Aichinger <[EMAIL PROTECTED]> wrote: > Since that violates policy, the removal of /usr/bin/git As explained, I do not see why this violates policy, as the git shell script offers the git-core functionality. What other way is there for a neat transition for stable users? > is documented in git's NEWS.Debian and git's popcon count Popularity doesn't make it right for a new package to use binary names from an existing one. git-core is new next release, so it should give way for now. I think the git maintainer has already been far more flexible than he needed to be. > is somewhere at 190, I think the easiest solution is to just kill > the alternatives and let git-core have the file. That solution was previously rejected by maintainers. > If somebody does an NMU please remember to adjust the version in > debian/NEWS. Please do not NMU this previously-rejected approach without further discussion. If the consensus is that using alternatives for this transition is a policy violation, I will encourage git's maintainer to stop renaming the upstream's git to gitfm in the diff.gz for now. If there is an alternative neat transition possible, what is it? Thanks, -- MJR/slef Laux nur mia opinio: vidu http://people.debian.org/~mjr/ Bv sekvu http://www.uk.debian.org/MailingLists/#codeofconduct -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#380187: debian-boot: fails to initialise platinumfb-driver based video controller
Processing commands for [EMAIL PROTECTED]: > reassign 380187 installation-reports Bug#380187: debian-boot: fails to initialise platinumfb-driver based video controller Warning: Unknown package 'debian-boot' Bug reassigned from package `debian-boot' to `installation-reports'. > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: closing 333907
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.20 > close 333907 Bug#333907: FTBFS: build-depends on a non-existing package 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Luk Claes <[EMAIL PROTECTED]> > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
