Bug#188913: marked as done (chipmunk-log: FTBFS: syntax errors in psys headers)
Your message dated Wed, 24 May 2006 23:02:07 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#188913: fixed in psys 1.56-4 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) ---BeginMessage--- Package: chipmunk-log Version: 5.58-2 Severity: serious From my build log: ... make[2]: Leaving directory `/tmp/buildd/chipmunk-log-5.58/src/ana' gcc -O2 -DBSD -Dlinux -DF_OK=0 -I/usr/include/ -I/usr/include/psys -I. -DLOGLIB=\/usr/share/chipmunk-log-libs\ -DF_OK=0 -c -o log.o log.c In file included from /usr/include/psys/p2c.h:74, from log.c:56: /usr/include/psys/strings.h:32: syntax error before pstr_StrBuf /usr/include/psys/strings.h:34: syntax error before '*' token /usr/include/psys/strings.h:37: syntax error before Char ... log.c:15598: register name not specified for `__result' log.c:15598: register name not specified for `__result' log.c:17307: register name not specified for `__result' log.c:17307: register name not specified for `__result' log.c:17311: register name not specified for `__result' log.c:17311: register name not specified for `__result' make[1]: *** [log.o] Error 1 make[1]: Leaving directory `/tmp/buildd/chipmunk-log-5.58/src' make: *** [build-stamp] Error 2 I can't tell whether the source is failing to include a prerequisite header first, or whether there's a problem in /usr/include/psys/p2c.h. If the latter, feel free to reassign the bug to libpsys-dev. -- System Information Debian Release: testing/unstable Kernel Version: Linux frobnitz 2.4.21-pre5 #1 Sat Mar 1 09:01:10 PST 2003 i686 unknown unknown GNU/Linux -- Daniel Schepler Please don't disillusion me. I [EMAIL PROTECTED]haven't had breakfast yet. -- Orson Scott Card ---End Message--- ---BeginMessage--- Source: psys Source-Version: 1.56-4 We believe that the bug you reported is fixed in the latest version of psys, which is due to be installed in the Debian FTP archive: libpsys-dev_1.56-4_i386.deb to pool/main/p/psys/libpsys-dev_1.56-4_i386.deb libpsys1_1.56-4_i386.deb to pool/main/p/psys/libpsys1_1.56-4_i386.deb psys_1.56-4.diff.gz to pool/main/p/psys/psys_1.56-4.diff.gz psys_1.56-4.dsc to pool/main/p/psys/psys_1.56-4.dsc 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. Andrew Pollock [EMAIL PROTECTED] (supplier of updated psys 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: Sat, 15 Apr 2006 22:10:10 -0700 Source: psys Binary: libpsys1 libpsys-dev Architecture: source i386 Version: 1.56-4 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Andrew Pollock [EMAIL PROTECTED] Description: libpsys-dev - p-system emulation libraries for Chipmunk tools [development] libpsys1 - p-system emulation runtime libraries for Chipmunk tools Closes: 188913 196275 201196 347106 Changes: psys (1.56-4) unstable; urgency=low . * QA Group upload orphaning this package * debian/rules: bumped debhelper compatibility version to 4 * debian/control: rephrased package description synopsis * debian/control: changed Section: to libdevel * Incorporates previous NMUs (closes: #201196) . psys (1.56-3.2) unstable; urgency=low . * Help xlibs-dev transition * Splitted xlibs-dev build-dep. (Closes: #347106) . psys (1.56-3.1) unstable; urgency=low . * Non-maintainer upload * Avoid headers with the same name as system headers (Closes: Bug#188913) * Use stdarg.h instead of varargs.h (Closes: Bug#196275) Files: 88f408b3b5727d1ae1574c5c5a68d2be 580 libdevel optional psys_1.56-4.dsc d12141690f46cc8bba75ea82d3b7e787 6540 libdevel optional psys_1.56-4.diff.gz 8855878f871a8548a1a3d2fdb5fd6e55 178448 libs optional libpsys1_1.56-4_i386.deb b9f8eeaacbb57ca14cdbc41951693b51 180266 libdevel optional libpsys-dev_1.56-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEdUKrIblXXKfZFgIRAlJmAJ9FjZBpU6jrJXEl7D8HVBzhd0FoXwCgl+jJ gkKsslbM3k7wUZDuXCRXa0A= =5mt/ -END PGP SIGNATURE- ---End Message---
Bug#196275: marked as done (psys: FTBFS with gcc-3.3: Uses obsolete varargs.h)
Your message dated Wed, 24 May 2006 23:02:07 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#196275: fixed in psys 1.56-4
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)
---BeginMessage---
Package: psys
Version: 1.56-3
Severity: serious
From my build log:
...
gcc -O2 -DBSD -Dlinux -DF_OK=0 -D_REENTRANT -fPIC -I../include -I. -c -o
newcrt.o newcrt.c
In file included from newcrt.c:8:
/usr/lib/gcc-lib/i386-linux/3.3/include/varargs.h:4:2: #error GCC no longer
implements varargs.h.
/usr/lib/gcc-lib/i386-linux/3.3/include/varargs.h:5:2: #error Revise your code
to use stdarg.h.
newcrt.c:845: error: parse error before va_dcl
newcrt.c:846: error: syntax error before '{' token
newcrt.c:853: warning: parameter names (without types) in function declaration
newcrt.c:853: warning: data definition has no type or storage class
...
make[1]: *** [newcrt.o] Error 1
make[1]: Leaving directory `/tmp/buildd/psys-1.56/src'
make: *** [build-stamp] Error 2
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux frobnitz 2.4.21-pre5 #1 Sat Mar 1 09:01:10 PST 2003 i686
Locale: LANG=C, LC_CTYPE=C
--
Daniel Schepler Please don't disillusion me. I
[EMAIL PROTECTED]haven't had breakfast yet.
-- Orson Scott Card
---End Message---
---BeginMessage---
Source: psys
Source-Version: 1.56-4
We believe that the bug you reported is fixed in the latest version of
psys, which is due to be installed in the Debian FTP archive:
libpsys-dev_1.56-4_i386.deb
to pool/main/p/psys/libpsys-dev_1.56-4_i386.deb
libpsys1_1.56-4_i386.deb
to pool/main/p/psys/libpsys1_1.56-4_i386.deb
psys_1.56-4.diff.gz
to pool/main/p/psys/psys_1.56-4.diff.gz
psys_1.56-4.dsc
to pool/main/p/psys/psys_1.56-4.dsc
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.
Andrew Pollock [EMAIL PROTECTED] (supplier of updated psys 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: Sat, 15 Apr 2006 22:10:10 -0700
Source: psys
Binary: libpsys1 libpsys-dev
Architecture: source i386
Version: 1.56-4
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group [EMAIL PROTECTED]
Changed-By: Andrew Pollock [EMAIL PROTECTED]
Description:
libpsys-dev - p-system emulation libraries for Chipmunk tools [development]
libpsys1 - p-system emulation runtime libraries for Chipmunk tools
Closes: 188913 196275 201196 347106
Changes:
psys (1.56-4) unstable; urgency=low
.
* QA Group upload orphaning this package
* debian/rules: bumped debhelper compatibility version to 4
* debian/control: rephrased package description synopsis
* debian/control: changed Section: to libdevel
* Incorporates previous NMUs (closes: #201196)
.
psys (1.56-3.2) unstable; urgency=low
.
* Help xlibs-dev transition
* Splitted xlibs-dev build-dep. (Closes: #347106)
.
psys (1.56-3.1) unstable; urgency=low
.
* Non-maintainer upload
* Avoid headers with the same name as system headers
(Closes: Bug#188913)
* Use stdarg.h instead of varargs.h (Closes: Bug#196275)
Files:
88f408b3b5727d1ae1574c5c5a68d2be 580 libdevel optional psys_1.56-4.dsc
d12141690f46cc8bba75ea82d3b7e787 6540 libdevel optional psys_1.56-4.diff.gz
8855878f871a8548a1a3d2fdb5fd6e55 178448 libs optional libpsys1_1.56-4_i386.deb
b9f8eeaacbb57ca14cdbc41951693b51 180266 libdevel optional
libpsys-dev_1.56-4_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFEdUKrIblXXKfZFgIRAlJmAJ9FjZBpU6jrJXEl7D8HVBzhd0FoXwCgl+jJ
gkKsslbM3k7wUZDuXCRXa0A=
=5mt/
-END PGP SIGNATURE-
---End Message---
Bug#347106: marked as done (psys: FTBFS: build-depends on removed xlibs-dev)
Your message dated Wed, 24 May 2006 23:02:07 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#347106: fixed in psys 1.56-4 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) ---BeginMessage--- Package: psys Version: 1.56-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--- ---BeginMessage--- Source: psys Source-Version: 1.56-4 We believe that the bug you reported is fixed in the latest version of psys, which is due to be installed in the Debian FTP archive: libpsys-dev_1.56-4_i386.deb to pool/main/p/psys/libpsys-dev_1.56-4_i386.deb libpsys1_1.56-4_i386.deb to pool/main/p/psys/libpsys1_1.56-4_i386.deb psys_1.56-4.diff.gz to pool/main/p/psys/psys_1.56-4.diff.gz psys_1.56-4.dsc to pool/main/p/psys/psys_1.56-4.dsc 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. Andrew Pollock [EMAIL PROTECTED] (supplier of updated psys 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: Sat, 15 Apr 2006 22:10:10 -0700 Source: psys Binary: libpsys1 libpsys-dev Architecture: source i386 Version: 1.56-4 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Andrew Pollock [EMAIL PROTECTED] Description: libpsys-dev - p-system emulation libraries for Chipmunk tools [development] libpsys1 - p-system emulation runtime libraries for Chipmunk tools Closes: 188913 196275 201196 347106 Changes: psys (1.56-4) unstable; urgency=low . * QA Group upload orphaning this package * debian/rules: bumped debhelper compatibility version to 4 * debian/control: rephrased package description synopsis * debian/control: changed Section: to libdevel * Incorporates previous NMUs (closes: #201196) . psys (1.56-3.2) unstable; urgency=low . * Help xlibs-dev transition * Splitted xlibs-dev build-dep. (Closes: #347106) . psys (1.56-3.1) unstable; urgency=low . * Non-maintainer upload * Avoid headers with the same name as system headers (Closes: Bug#188913) * Use stdarg.h instead of varargs.h (Closes: Bug#196275) Files: 88f408b3b5727d1ae1574c5c5a68d2be 580 libdevel optional psys_1.56-4.dsc d12141690f46cc8bba75ea82d3b7e787 6540 libdevel optional psys_1.56-4.diff.gz 8855878f871a8548a1a3d2fdb5fd6e55 178448 libs optional libpsys1_1.56-4_i386.deb b9f8eeaacbb57ca14cdbc41951693b51 180266 libdevel optional libpsys-dev_1.56-4_i386.deb -BEGIN PGP
Bug#368429: marked as done (Error processing manpages-dev when upgrading)
Your message dated Thu, 25 May 2006 00:32:08 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#365547: fixed in manpages 2.28-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) ---BeginMessage--- Package: manpages-dev Version: 2.22-1 Severity: important Failure to upgrade: Reading changelogs... Done (Reading database ... 131617 files and directories currently installed.) Preparing to replace manpages-dev 2.22-1 (using .../manpages-dev_2.28-1_all.deb) ... Unpacking replacement manpages-dev ... dpkg: error processing /var/cache/apt/archives/manpages-dev_2.28-1_all.deb (--unpack): trying to overwrite `/usr/share/man/man3/sem_destroy.3.gz', which is also in package glibc-doc dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/manpages-dev_2.28-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Best regards Andrei Emeltchenko -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-rc5 Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Versions of packages manpages-dev depends on: ii manpages 2.28-1 Manual pages about using a GNU/Lin manpages-dev recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: manpages Source-Version: 2.28-2 We believe that the bug you reported is fixed in the latest version of manpages, which is due to be installed in the Debian FTP archive: manpages-dev_2.28-2_all.deb to pool/main/m/manpages/manpages-dev_2.28-2_all.deb manpages_2.28-2.diff.gz to pool/main/m/manpages/manpages_2.28-2.diff.gz manpages_2.28-2.dsc to pool/main/m/manpages/manpages_2.28-2.dsc manpages_2.28-2_all.deb to pool/main/m/manpages/manpages_2.28-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. Martin Schulze [EMAIL PROTECTED] (supplier of updated manpages 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, 25 May 2006 09:06:11 +0200 Source: manpages Binary: manpages manpages-dev Architecture: source all Version: 2.28-2 Distribution: unstable Urgency: medium Maintainer: Martin Schulze [EMAIL PROTECTED] Changed-By: Martin Schulze [EMAIL PROTECTED] Description: manpages - Manual pages about using a GNU/Linux system manpages-dev - Manual pages about using GNU/Linux for development Closes: 365489 365547 Changes: manpages (2.28-2) unstable; urgency=medium . * Adjusted rmdir(2) according to upstream (Bug#205238) * Updated the URL for the Single Unix Specification v2 in missing(7) * Added a versioned Replaces entry against glibc-doc due to semaphor manpages shipped with glibc-doc (Closes: Bug#365547) * Fixed double braces in stdin(3) (Closes: Bug#365489) Files: d4034d01352068526466616961e03bcc 584 doc - manpages_2.28-2.dsc 8f76a6b681fe1b82ebabdd9d138327b6 49442 doc - manpages_2.28-2.diff.gz 046a554e9698c05cab6be1e398419fe1 461510 doc important manpages_2.28-2_all.deb fb2f5843ebf87699cd1f1ea05221a12f 1173428 doc standard manpages-dev_2.28-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEdVmmW5ql+IAeqTIRArzEAJ9bAb8DUkBlhRhNO7qMMaWm+mqoOwCfcshZ 9cAuUlQzulXm7J1CJ+zV70g= =xV/3 -END PGP SIGNATURE- ---End Message---
Bug#368281: marked as done (manpages-dev: conflicts with glibc-doc)
Your message dated Thu, 25 May 2006 00:32:08 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#365547: fixed in manpages 2.28-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) ---BeginMessage--- Package: manpages-dev Version: 2.28-1 It would appear that there's a conflict with glibc-doc 2.3.6-7 (which is the version in testing right now): Preparing to replace manpages-dev 2.22-1 (using .../manpages-dev_2.28-1_all.deb) ... Unpacking replacement manpages-dev ... dpkg: error processing /var/cache/apt/archives/manpages-dev_2.28-1_all.deb (--unpack): trying to overwrite `/usr/share/man/man3/sem_destroy.3.gz', which is also in package glibc-doc dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/manpages-dev_2.28-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ---End Message--- ---BeginMessage--- Source: manpages Source-Version: 2.28-2 We believe that the bug you reported is fixed in the latest version of manpages, which is due to be installed in the Debian FTP archive: manpages-dev_2.28-2_all.deb to pool/main/m/manpages/manpages-dev_2.28-2_all.deb manpages_2.28-2.diff.gz to pool/main/m/manpages/manpages_2.28-2.diff.gz manpages_2.28-2.dsc to pool/main/m/manpages/manpages_2.28-2.dsc manpages_2.28-2_all.deb to pool/main/m/manpages/manpages_2.28-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. Martin Schulze [EMAIL PROTECTED] (supplier of updated manpages 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, 25 May 2006 09:06:11 +0200 Source: manpages Binary: manpages manpages-dev Architecture: source all Version: 2.28-2 Distribution: unstable Urgency: medium Maintainer: Martin Schulze [EMAIL PROTECTED] Changed-By: Martin Schulze [EMAIL PROTECTED] Description: manpages - Manual pages about using a GNU/Linux system manpages-dev - Manual pages about using GNU/Linux for development Closes: 365489 365547 Changes: manpages (2.28-2) unstable; urgency=medium . * Adjusted rmdir(2) according to upstream (Bug#205238) * Updated the URL for the Single Unix Specification v2 in missing(7) * Added a versioned Replaces entry against glibc-doc due to semaphor manpages shipped with glibc-doc (Closes: Bug#365547) * Fixed double braces in stdin(3) (Closes: Bug#365489) Files: d4034d01352068526466616961e03bcc 584 doc - manpages_2.28-2.dsc 8f76a6b681fe1b82ebabdd9d138327b6 49442 doc - manpages_2.28-2.diff.gz 046a554e9698c05cab6be1e398419fe1 461510 doc important manpages_2.28-2_all.deb fb2f5843ebf87699cd1f1ea05221a12f 1173428 doc standard manpages-dev_2.28-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEdVmmW5ql+IAeqTIRArzEAJ9bAb8DUkBlhRhNO7qMMaWm+mqoOwCfcshZ 9cAuUlQzulXm7J1CJ+zV70g= =xV/3 -END PGP SIGNATURE- ---End Message---
Bug#365547: marked as done (manpages-dev uninstallable because of conflicting file sem_destroy.3.gz from glibc-doc)
Your message dated Thu, 25 May 2006 00:32:08 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#365547: fixed in manpages 2.28-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) ---BeginMessage--- Package: manpages-dev Version: 2.28-1 Severity: grave Running apt-get upgrade yields the following error message: Preparing to replace manpages-dev 2.27-1 (using .../manpages-dev_2.28-1_all.deb) ... Unpacking replacement manpages-dev ... dpkg: error processing /var/cache/apt/archives/manpages-dev_2.28-1_all.deb (--unpack): trying to overwrite `/usr/share/man/man3/sem_destroy.3.gz', which is also in package glibc-doc dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/manpages-dev_2.28-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Michael -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (300, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.11 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages manpages-dev depends on: ii manpages 2.28-1 Manual pages about using a GNU/Lin manpages-dev recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: manpages Source-Version: 2.28-2 We believe that the bug you reported is fixed in the latest version of manpages, which is due to be installed in the Debian FTP archive: manpages-dev_2.28-2_all.deb to pool/main/m/manpages/manpages-dev_2.28-2_all.deb manpages_2.28-2.diff.gz to pool/main/m/manpages/manpages_2.28-2.diff.gz manpages_2.28-2.dsc to pool/main/m/manpages/manpages_2.28-2.dsc manpages_2.28-2_all.deb to pool/main/m/manpages/manpages_2.28-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. Martin Schulze [EMAIL PROTECTED] (supplier of updated manpages 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, 25 May 2006 09:06:11 +0200 Source: manpages Binary: manpages manpages-dev Architecture: source all Version: 2.28-2 Distribution: unstable Urgency: medium Maintainer: Martin Schulze [EMAIL PROTECTED] Changed-By: Martin Schulze [EMAIL PROTECTED] Description: manpages - Manual pages about using a GNU/Linux system manpages-dev - Manual pages about using GNU/Linux for development Closes: 365489 365547 Changes: manpages (2.28-2) unstable; urgency=medium . * Adjusted rmdir(2) according to upstream (Bug#205238) * Updated the URL for the Single Unix Specification v2 in missing(7) * Added a versioned Replaces entry against glibc-doc due to semaphor manpages shipped with glibc-doc (Closes: Bug#365547) * Fixed double braces in stdin(3) (Closes: Bug#365489) Files: d4034d01352068526466616961e03bcc 584 doc - manpages_2.28-2.dsc 8f76a6b681fe1b82ebabdd9d138327b6 49442 doc - manpages_2.28-2.diff.gz 046a554e9698c05cab6be1e398419fe1 461510 doc important manpages_2.28-2_all.deb fb2f5843ebf87699cd1f1ea05221a12f 1173428 doc standard manpages-dev_2.28-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEdVmmW5ql+IAeqTIRArzEAJ9bAb8DUkBlhRhNO7qMMaWm+mqoOwCfcshZ 9cAuUlQzulXm7J1CJ+zV70g= =xV/3 -END PGP SIGNATURE- ---End Message---
Bug#368155: marked as done (manpages-dev: conflicts with glibc-doc)
Your message dated Thu, 25 May 2006 00:32:08 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#365547: fixed in manpages 2.28-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) ---BeginMessage--- Package: manpages-dev Version: 2.22-1 Severity: normal This package contains the file /usr/share/man/man3/sem-destroy.3.gz which is also in the package glibc-doc. -- A true pessimist won't be discouraged by a little success. ---End Message--- ---BeginMessage--- Source: manpages Source-Version: 2.28-2 We believe that the bug you reported is fixed in the latest version of manpages, which is due to be installed in the Debian FTP archive: manpages-dev_2.28-2_all.deb to pool/main/m/manpages/manpages-dev_2.28-2_all.deb manpages_2.28-2.diff.gz to pool/main/m/manpages/manpages_2.28-2.diff.gz manpages_2.28-2.dsc to pool/main/m/manpages/manpages_2.28-2.dsc manpages_2.28-2_all.deb to pool/main/m/manpages/manpages_2.28-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. Martin Schulze [EMAIL PROTECTED] (supplier of updated manpages 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, 25 May 2006 09:06:11 +0200 Source: manpages Binary: manpages manpages-dev Architecture: source all Version: 2.28-2 Distribution: unstable Urgency: medium Maintainer: Martin Schulze [EMAIL PROTECTED] Changed-By: Martin Schulze [EMAIL PROTECTED] Description: manpages - Manual pages about using a GNU/Linux system manpages-dev - Manual pages about using GNU/Linux for development Closes: 365489 365547 Changes: manpages (2.28-2) unstable; urgency=medium . * Adjusted rmdir(2) according to upstream (Bug#205238) * Updated the URL for the Single Unix Specification v2 in missing(7) * Added a versioned Replaces entry against glibc-doc due to semaphor manpages shipped with glibc-doc (Closes: Bug#365547) * Fixed double braces in stdin(3) (Closes: Bug#365489) Files: d4034d01352068526466616961e03bcc 584 doc - manpages_2.28-2.dsc 8f76a6b681fe1b82ebabdd9d138327b6 49442 doc - manpages_2.28-2.diff.gz 046a554e9698c05cab6be1e398419fe1 461510 doc important manpages_2.28-2_all.deb fb2f5843ebf87699cd1f1ea05221a12f 1173428 doc standard manpages-dev_2.28-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEdVmmW5ql+IAeqTIRArzEAJ9bAb8DUkBlhRhNO7qMMaWm+mqoOwCfcshZ 9cAuUlQzulXm7J1CJ+zV70g= =xV/3 -END PGP SIGNATURE- ---End Message---
Bug#368585: marked as done (glibc-doc: conflict with manpages-dev package)
Your message dated Thu, 25 May 2006 00:32:08 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#365547: fixed in manpages 2.28-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) ---BeginMessage--- Package: glibc-doc Severity: normal There is error info when upgrading manpages-dev and glibc-doc dpkg: error processing /var/cache/apt/archives/manpages-dev_2.28-1_all.deb (--unpack): trying to overwrite `/usr/share/man/man3/sem_destroy.3.gz', which is also in package glibc-doc -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (800, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13-kender.dsdt.bis Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) ---End Message--- ---BeginMessage--- Source: manpages Source-Version: 2.28-2 We believe that the bug you reported is fixed in the latest version of manpages, which is due to be installed in the Debian FTP archive: manpages-dev_2.28-2_all.deb to pool/main/m/manpages/manpages-dev_2.28-2_all.deb manpages_2.28-2.diff.gz to pool/main/m/manpages/manpages_2.28-2.diff.gz manpages_2.28-2.dsc to pool/main/m/manpages/manpages_2.28-2.dsc manpages_2.28-2_all.deb to pool/main/m/manpages/manpages_2.28-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. Martin Schulze [EMAIL PROTECTED] (supplier of updated manpages 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, 25 May 2006 09:06:11 +0200 Source: manpages Binary: manpages manpages-dev Architecture: source all Version: 2.28-2 Distribution: unstable Urgency: medium Maintainer: Martin Schulze [EMAIL PROTECTED] Changed-By: Martin Schulze [EMAIL PROTECTED] Description: manpages - Manual pages about using a GNU/Linux system manpages-dev - Manual pages about using GNU/Linux for development Closes: 365489 365547 Changes: manpages (2.28-2) unstable; urgency=medium . * Adjusted rmdir(2) according to upstream (Bug#205238) * Updated the URL for the Single Unix Specification v2 in missing(7) * Added a versioned Replaces entry against glibc-doc due to semaphor manpages shipped with glibc-doc (Closes: Bug#365547) * Fixed double braces in stdin(3) (Closes: Bug#365489) Files: d4034d01352068526466616961e03bcc 584 doc - manpages_2.28-2.dsc 8f76a6b681fe1b82ebabdd9d138327b6 49442 doc - manpages_2.28-2.diff.gz 046a554e9698c05cab6be1e398419fe1 461510 doc important manpages_2.28-2_all.deb fb2f5843ebf87699cd1f1ea05221a12f 1173428 doc standard manpages-dev_2.28-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEdVmmW5ql+IAeqTIRArzEAJ9bAb8DUkBlhRhNO7qMMaWm+mqoOwCfcshZ 9cAuUlQzulXm7J1CJ+zV70g= =xV/3 -END PGP SIGNATURE- ---End Message---
Bug#358575: Purging mailman safely
Would replacing (please excuse the line wrap): for file in $(sed -e ':/etc/mailman:!d' -e 's:^[0-9a-f]* *::' /var/lib/ucf/hashfile); do with for file in $(sed -e '\|^[0-9a-fA-F]\+[[:space:]]\+/etc/mailman/|!d' -e 's|^[0-9a-fA-F]\+[[:space:]]\+||' /var/lib/ucf/hashfile); do in /var/lib/dpkg/info/mailman.postrm (is this the right file?) allow me to safely purge 2.1.7-1 without having to compile and install 2.1.8-1 first? I assume the same would apply to Sarge users. Thanks, Roger -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#349354: initramfs-tools - kernel -udev dependency loop
On May 25, maximilian attems [EMAIL PROTECTED] wrote: These packages are not actually needed by udev, and again they may be unpacked in the wrong order. Next? i know that these packages are not needed by udev itself, they are going to be installed on an upgrade to a new linux-image So what? udev still needs to check that they have been installed before it can continue. udev disables itself for 2.4 kernels, why can't it do that for 2.6.8? It does, but people do not expect that an udev upgrade will disable it, and they are right. otherwise stick that super special config in one of the package you depend on aka initscripts or makedev or lsb-base.. I do not know what you are writing about. -- ciao, Marco signature.asc Description: Digital signature
Bug#368160: marked as done (manpages-dev: conflicts with glibc-doc)
Your message dated Thu, 25 May 2006 00:32:08 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#365547: fixed in manpages 2.28-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) ---BeginMessage--- Package: upgrade-reports Severity: normal When I try to upgrade my system I have the next problem (Copy Paste from my terminal): Preparando para reemplazar manpages-dev 2.22-1 (usando .../manpages-dev_2.28-1_all.deb) ... Desempaquetando el reemplazo de manpages-dev ... dpkg: error al procesar /var/cache/apt/archives/manpages-dev_2.28-1_all.deb (--unpack): intentando sobreescribir `/usr/share/man/man3/sem_destroy.3.gz', que está también en el paquete glibc-doc dpkg-deb: el subproceso paste fue terminado por la señal (Tubería rota) Se encontraron errores al procesar: /var/cache/apt/archives/manpages-dev_2.28-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) I remove de glib-doc package and I can upgrade. But when I try to reinstall glib-doc, I have the same problem: Desempaquetando glibc-doc (de .../glibc-doc_2.3.6-7_all.deb) ... dpkg: error al procesar /var/cache/apt/archives/glibc-doc_2.3.6-7_all.deb (--unpack): intentando sobreescribir `/usr/share/man/man3/sem_init.3.gz', que está también en el paquete manpages-dev dpkg-deb: el subproceso paste fue terminado por la señal (Tubería rota) Se encontraron errores al procesar: /var/cache/apt/archives/glibc-doc_2.3.6-7_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) If I can help us, please let me know. Sorry for my Argentinian English. Regards. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-k7 Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to es_AR.UTF-8) ---End Message--- ---BeginMessage--- Source: manpages Source-Version: 2.28-2 We believe that the bug you reported is fixed in the latest version of manpages, which is due to be installed in the Debian FTP archive: manpages-dev_2.28-2_all.deb to pool/main/m/manpages/manpages-dev_2.28-2_all.deb manpages_2.28-2.diff.gz to pool/main/m/manpages/manpages_2.28-2.diff.gz manpages_2.28-2.dsc to pool/main/m/manpages/manpages_2.28-2.dsc manpages_2.28-2_all.deb to pool/main/m/manpages/manpages_2.28-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. Martin Schulze [EMAIL PROTECTED] (supplier of updated manpages 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, 25 May 2006 09:06:11 +0200 Source: manpages Binary: manpages manpages-dev Architecture: source all Version: 2.28-2 Distribution: unstable Urgency: medium Maintainer: Martin Schulze [EMAIL PROTECTED] Changed-By: Martin Schulze [EMAIL PROTECTED] Description: manpages - Manual pages about using a GNU/Linux system manpages-dev - Manual pages about using GNU/Linux for development Closes: 365489 365547 Changes: manpages (2.28-2) unstable; urgency=medium . * Adjusted rmdir(2) according to upstream (Bug#205238) * Updated the URL for the Single Unix Specification v2 in missing(7) * Added a versioned Replaces entry against glibc-doc due to semaphor manpages shipped with glibc-doc (Closes: Bug#365547) * Fixed double braces in stdin(3) (Closes: Bug#365489) Files: d4034d01352068526466616961e03bcc 584 doc - manpages_2.28-2.dsc 8f76a6b681fe1b82ebabdd9d138327b6 49442 doc - manpages_2.28-2.diff.gz 046a554e9698c05cab6be1e398419fe1 461510 doc important manpages_2.28-2_all.deb fb2f5843ebf87699cd1f1ea05221a12f 1173428 doc standard manpages-dev_2.28-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEdVmmW5ql+IAeqTIRArzEAJ9bAb8DUkBlhRhNO7qMMaWm+mqoOwCfcshZ 9cAuUlQzulXm7J1CJ+zV70g= =xV/3 -END PGP SIGNATURE- ---End Message---
Bug#368804: Invalid/Lock password options don't work
Hi Stephan, Brian May schrieb: If I use the Invalid Password option in the Unix section of a user, I get a password of *. This is not invalid. pam_ldap accepts the password fine and allows the user to log in. Perhaps that means the fault is with pam_ldap, not sure. can you tell me why pam-ldap accepts a * as password? Should LDAP accounts not be formated just like accounts in /etc/(passwd|shadow)? How do I disable an account, setting no userPassword attribute at all? When I set a user password which starts with * then getent shadow shows me an x in the password field. Greetings Roland -- LDAP Account Manager http://lam.sourceforge.net signature.asc Description: OpenPGP digital signature
Bug#338369: libcgi-formbuilder-perl FTBFS
Heya, This bug has been open for ages now, even though Don gave a hint for an (ugly) solution - building the package actually succeeds if libhtml-parser-perl (which contains Html::Entities) is not installed, so build-conflicting with it would ensure that this package builds. I really don't think that this would be a good solution, but it would be nice to kill off this RC bug finally! Marc -- BOFH #100: IRQ dropout -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 368255
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.19 tags 368255 + unreproducible Bug#368255: FTBFS: Missing Build-Depends (python-setuptools) There were no tags set. Tags added: unreproducible 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#368572: marked as done (tulip_2.0.4-1(amd64/unstable): error: cast from 'const GraphObserver*' to 'unsigned int' loses precision)
Your message dated Thu, 25 May 2006 01:32:13 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#368572: fixed in tulip 2.0.4-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) ---BeginMessage--- Package: tulip Version: 2.0.4-1 Severity: serious Hello, There was an error while trying to autobuild your package: g++ -DHAVE_CONFIG_H -I. -I../../../../library/tulip/src -I../../.. -I../../../../library/tulip/include -I../../../../thirdparty/gzstream -I../../../.. -D_TULIP_LIB_DIR=\/usr/lib/\ -DNDEBUG -O3 -funroll-loops -pipe -MT Bfs.lo -MD -MP -MF .deps/Bfs.Tpo -c ../../../../library/tulip/src/Bfs.cpp -fPIC -DPIC -o .libs/Bfs.o ../../../../library/tulip/include/tulip/ObservableGraph.h: In member function 'size_t std::lessGraphObserver*::operator()(const GraphObserver*, const GraphObserver*) const': ../../../../library/tulip/include/tulip/ObservableGraph.h:34: error: cast from 'const GraphObserver*' to 'unsigned int' loses precision ../../../../library/tulip/include/tulip/ObservableGraph.h:34: error: cast from 'const GraphObserver*' to 'unsigned int' loses precision make[5]: *** [Bfs.lo] Error 1 make[5]: Leaving directory `/build/buildd/tulip-2.0.4/BUILD/library/tulip/src' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/build/buildd/tulip-2.0.4/BUILD/library/tulip' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/build/buildd/tulip-2.0.4/BUILD/library' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/buildd/tulip-2.0.4/BUILD' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd/tulip-2.0.4/BUILD' make: *** [/build/buildd/tulip-2.0.4/stamps/build] Error 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=amd64pkg=tulipver=2.0.4-1 Best regards Frederik Schueler ---End Message--- ---BeginMessage--- Source: tulip Source-Version: 2.0.4-3 We believe that the bug you reported is fixed in the latest version of tulip, which is due to be installed in the Debian FTP archive: libtulip-2.0-dev_2.0.4-3_i386.deb to pool/main/t/tulip/libtulip-2.0-dev_2.0.4-3_i386.deb libtulip-2.0c2a_2.0.4-3_i386.deb to pool/main/t/tulip/libtulip-2.0c2a_2.0.4-3_i386.deb libtulip-ogl-2.0-dev_2.0.4-3_i386.deb to pool/main/t/tulip/libtulip-ogl-2.0-dev_2.0.4-3_i386.deb libtulip-ogl-2.0c2a_2.0.4-3_i386.deb to pool/main/t/tulip/libtulip-ogl-2.0c2a_2.0.4-3_i386.deb libtulip-qt-2.0-dev_2.0.4-3_i386.deb to pool/main/t/tulip/libtulip-qt-2.0-dev_2.0.4-3_i386.deb libtulip-qt-2.0c2a_2.0.4-3_i386.deb to pool/main/t/tulip/libtulip-qt-2.0c2a_2.0.4-3_i386.deb tulip_2.0.4-3.diff.gz to pool/main/t/tulip/tulip_2.0.4-3.diff.gz tulip_2.0.4-3.dsc to pool/main/t/tulip/tulip_2.0.4-3.dsc tulip_2.0.4-3_i386.deb to pool/main/t/tulip/tulip_2.0.4-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. Yann Dirson [EMAIL PROTECTED] (supplier of updated tulip 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: Wed, 24 May 2006 23:05:41 +0200 Source: tulip Binary: libtulip-qt-2.0-dev libtulip-ogl-2.0c2a libtulip-2.0-dev libtulip-qt-2.0c2a libtulip-ogl-2.0-dev libtulip-2.0c2a tulip Architecture: source i386 Version: 2.0.4-3 Distribution: unstable Urgency: low Maintainer: Yann Dirson [EMAIL PROTECTED] Changed-By: Yann Dirson [EMAIL PROTECTED] Description: libtulip-2.0-dev - Tulip graph library - core development files libtulip-2.0c2a - Tulip graph library - core runtime libtulip-ogl-2.0-dev - Tulip graph library - OpenGL development files libtulip-ogl-2.0c2a - Tulip graph library - OpenGL runtime libtulip-qt-2.0-dev - Tulip graph library - Qt/OpenGL gui development files libtulip-qt-2.0c2a - Tulip graph library - Qt/OpenGL gui runtime tulip - A system dedicated to the visualization of huge graphs Closes: 368572 Changes: tulip (2.0.4-3) unstable; urgency=low . * Updated patches: * Upstream fix for 64bit platforms (Closes: #368572 for real this time). Files: df304934375c8a0b2c03088e9afdb3bf 932 graphics optional tulip_2.0.4-3.dsc
Bug#368832: gnome-media-common: fails to install
Package: gnome-media-common Severity: grave Justification: renders package unusable Try to replace the file /usr/share/omf/gnome-media/grecord-zh_CN.omf which is part of the package gnome-media -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13.2 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368255: FTBFS: Missing Build-Depends (python-setuptools)
Interestingly enough, cdbs version 0.4.36 does not even contain the mentioned test cases distutils-3.sh and distutils-4.sh, so something is wrong here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368833: libgnome-media0: Fails to install
Package: libgnome-media0 Severity: grave Justification: renders package unusable Tries to replace the file /usr/lib/bonobo/servers/GNOME_Media_CDDBSlave2.server which is part of the package gnome-media -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13.2 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368835: drupal: Execution of arbitrary files in certain Apache configurations
Package: drupal Version: 4.5.8-1 Severity: grave Tags: security Justification: user security hole http://drupal.org/node/65409 EXECUTION OF ARBITRARY FILES IN CERTAIN APACHE CONFIGURATIONS * Advisory ID: DRUPAL-SA-2006-006 * Project: Drupal core * Date: 2006-May-24 * Security risk: highly critical * Impact: Drupal core * Exploitable from: remote * Vulnerability: Execution of arbitrary files DESCRIPTION Certain -- alas, typical -- configurations of Apache allows execution of carefully named arbitrary scripts in the files directory. Drupal now will attempt to automatically create a .htaccess file in your files directory to protect you. VERSIONS AFFECTED - All Drupal versions before 4.6.7 and also Drupal 4.7.0. SOLUTION If you are running Drupal 4.6.x then upgrade to Drupal 4.6.7. If you are running Drupal 4.7.0 then upgrade to Drupal 4.7.1. Make sure you have a .htaccess in your files dir and it contains this line: SetHandler This_is_a_Drupal_security_line_do_not_remove REPORTED BY milw0rm CONTACT The security contact for Drupal can be reached at security at drupal.org or using the form at [http://drupal.org/contact]. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages drupal depends on: ii apache-ssl [httpd]1.3.34-2 versatile, high-performance HTTP s ii apache2-mpm-prefork [httpd] 2.0.55-4 traditional model for Apache2 ii debconf [debconf-2.0] 1.5.0 Debian configuration management sy ii libapache2-mod-php4 4:4.4.2-1 server-side, HTML-embedded scripti ii makepasswd1.10-3 Generate and encrypt passwords ii mysql-client-5.0 [mysql-clien 5.0.18-7 mysql database client binaries ii php4-cgi 4:4.4.2-1 server-side, HTML-embedded scripti ii php4-cli 4:4.4.2-1 command-line interpreter for the p ii php4-mysql4:4.4.2-1 MySQL module for php4 ii php4-pgsql4:4.4.2-1 PostgreSQL module for php4 ii postfix [mail-transport-agent 2.1.5-9A high-performance mail transport ii postgresql-client 7.5.19 front-end programs for PostgreSQL ii wwwconfig-common 0.0.45 Debian web auto configuration Versions of packages drupal recommends: ii mysql-server-5.0 [mysql-serve 5.0.18-7 mysql database server binaries ii postgresql7.5.19 object-relational SQL database man -- debconf information: drupal/remove_backups: false drupal/createuser_failed: drupal/db_auto_update: true drupal/dropdb_failed: drupal/upgradedb_impossible: drupal/dbgeneration: false drupal/dbtype: MySQL drupal/database_doremove: false drupal/createdb_failed: drupal/dbserver: localhost drupal/webserver: apache drupal/upgradedb_failed: drupal/dbname: drupal drupal/dbuser: drupal drupal/dbadmin: root drupal/initdb_failed: drupal/conffile_failed: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#347593: segfaults on amd64 on ttf-freefont 20051206
Steve Langasek wrote: Hi Tim, I'm having trouble at the moment getting GLX working on my amd64, so I can't test this problem, but I'm told that foobillard works ok on amd64 with the current ttf-freefont in unstable. Can you check whether you're still able to reproduce this bug? Thanks, The latest package seems to have fixed the bug. Thanks for this. Tim. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368507: marked as done (libroxen-imho_0.99-3(amd64/unstable): Build-depends on pike7.4 which has been removed from the archive)
Your message dated Thu, 25 May 2006 02:32:07 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#368507: fixed in libroxen-imho 0.99-4 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) ---BeginMessage--- Package: libroxen-imho Version: 0.99-3 Severity: serious Hello, There was an error while trying to autobuild your package: ** Using build dependencies supplied by package: Build-Depends: debhelper, pike7.4-dev | pike7.6-dev | pike7, po-debconf it failed on ALL architectures because pike7.4 is not in the archive anymore, please fix your build dependency accordingly. A full build log can be found at: http://buildd.debian.org/build.php?arch=amd64pkg=libroxen-imhover=0.99-3 Best regards Frederik Schueler ---End Message--- ---BeginMessage--- Source: libroxen-imho Source-Version: 0.99-4 We believe that the bug you reported is fixed in the latest version of libroxen-imho, which is due to be installed in the Debian FTP archive: libroxen-imho_0.99-4.diff.gz to pool/main/libr/libroxen-imho/libroxen-imho_0.99-4.diff.gz libroxen-imho_0.99-4.dsc to pool/main/libr/libroxen-imho/libroxen-imho_0.99-4.dsc libroxen-imho_0.99-4_i386.deb to pool/main/libr/libroxen-imho/libroxen-imho_0.99-4_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. Turbo Fredriksson [EMAIL PROTECTED] (supplier of updated libroxen-imho 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, 25 May 2006 11:03:04 +0200 Source: libroxen-imho Binary: libroxen-imho Architecture: source i386 Version: 0.99-4 Distribution: unstable Urgency: low Maintainer: Turbo Fredriksson [EMAIL PROTECTED] Changed-By: Turbo Fredriksson [EMAIL PROTECTED] Description: libroxen-imho - Web-based e-mail module for Roxen (using IMAP) Closes: 368507 Changes: libroxen-imho (0.99-4) unstable; urgency=low . * Add roxen4 as depends * Put build-depends on pike7.6-dev FIRST because of limitations on the auto-builders. Closes: #368507 * Set compat level to at least 4 in debian/compat. Update debian/rules to not install into 'debian/tmp/' but instead 'debian/libroxen-imho/'. * Update the standards version to 3.7.2 * Fix/update extended descriptions in template. * Add dependency on debconf | debconf-2.0 Files: e4b95bc2b2f92c7786d7f47cfa2977a2 621 web optional libroxen-imho_0.99-4.dsc 9da105ba3627dc88388cf47d1ad36494 9852 web optional libroxen-imho_0.99-4.diff.gz d43a943eb8dc5b80e14caad186e4a038 121258 web optional libroxen-imho_0.99-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEdXYEmlWzPKccHgARAjTFAJ9uNFklwHpmkkEHgRM9cJH7iTea2wCeLdrj QTFjAQ8wSoFDQ1bITUCLLN8= =Fs7h -END PGP SIGNATURE- ---End Message---
Bug#368838: xmorph_1:20060525(amd64/unstable): diw_map.c:47:28: error: X11/bitmaps/gray: No such file or directory
Package: xmorph Version: 1:20060525 Severity: serious Hello, There was an error while trying to autobuild your package: if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../libmorph -I../intl -Wall -g -O2 -DREAL=double -DRGBA_MESH_WARP -DNDEBUG_LIBMORPH_REF_COUNT -Wall -g -O2 -MT xmorph-diw_map.o -MD -MP -MF .deps/xmorph-diw_map.Tpo -c -o xmorph-diw_map.o `test -f 'diw_map.c' || echo './'`diw_map.c; \ then mv -f .deps/xmorph-diw_map.Tpo .deps/xmorph-diw_map.Po; else rm -f .deps/xmorph-diw_map.Tpo; exit 1; fi diw_map.c:47:28: error: X11/bitmaps/gray: No such file or directory diw_map.c: In function 'mpt_scroll_cb': diw_map.c:1018: warning: cast from pointer to integer of different size diw_map.c: In function 'image_scroll_cb': diw_map.c:1057: warning: cast from pointer to integer of different size diw_map.c: In function 'init_diw_stuff': diw_map.c:1736: error: 'gray_bits' undeclared (first use in this function) diw_map.c:1736: error: (Each undeclared identifier is reported only once diw_map.c:1736: error: for each function it appears in.) diw_map.c:1736: error: 'gray_width' undeclared (first use in this function) diw_map.c:1736: error: 'gray_height' undeclared (first use in this function) make[3]: *** [xmorph-diw_map.o] Error 1 make[3]: Leaving directory `/build/buildd/xmorph-20060525/xmorph' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/buildd/xmorph-20060525' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd/xmorph-20060525' make: *** [build-stamp] Error 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=amd64pkg=xmorphver=1:20060525 Best regards Frederik Schueler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368837: klic_3.003-gm1-1(amd64/unstable): /bin/sh: ../debian/configure.expect: Permission denied
Package: klic Version: 3.003-gm1-1 Severity: serious Hello, There was an error while trying to autobuild your package: patching file runtime/sched.c patching file runtime/trace.c cd klic-3.003 patch -p1 ../debian/patch3.suppress-mktemp-warning patching file runtime/gunix.c patching file runtime/trace.c cd klic-3.003 ../debian/configure.expect /bin/sh: ../debian/configure.expect: Permission denied make: *** [configure-stamp] Error 126 A full build log can be found at: http://buildd.debian.org/build.php?arch=amd64pkg=klicver=3.003-gm1-1 Best regards Frederik Schueler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337712: marked as done (sysklogd: Puts link in /usr/doc)
Your message dated Thu, 25 May 2006 02:47:21 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#337712: fixed in sysklogd 1.4.1-18
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)
---BeginMessage---
Package: sysklogd
Version: 1.4.1-17
Severity: serious
Justification: Policy 12.3
Section 12.3 of Debian policy Additional documentation says:
Former Debian releases placed all additional documentation in
/usr/doc/package. This has been changed to /usr/share/doc/package, and
packages must not put documentation in the directory
/usr/doc/package.
I believe this package violates this rule by installing a symlink in
/usr/doc/. It is the aim that etch will not have any packages
installing things into the directory /usr/doc/.
I believe this can be rectified by removing the relevant bits in the
postinst and prerm files for sysklogd and klogd.
Thanks,
Stephen Quinney
-- 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.12-1-k7
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages sysklogd depends on:
ii klogd [linux-kernel-log-daemo 1.4.1-17 Kernel Logging Daemon
ii libc6 2.3.5-7GNU C Library: Shared libraries an
sysklogd recommends no packages.
-- no debconf information
---End Message---
---BeginMessage---
Source: sysklogd
Source-Version: 1.4.1-18
We believe that the bug you reported is fixed in the latest version of
sysklogd, which is due to be installed in the Debian FTP archive:
klogd_1.4.1-18_i386.deb
to pool/main/s/sysklogd/klogd_1.4.1-18_i386.deb
sysklogd_1.4.1-18.diff.gz
to pool/main/s/sysklogd/sysklogd_1.4.1-18.diff.gz
sysklogd_1.4.1-18.dsc
to pool/main/s/sysklogd/sysklogd_1.4.1-18.dsc
sysklogd_1.4.1-18_i386.deb
to pool/main/s/sysklogd/sysklogd_1.4.1-18_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.
Martin Schulze [EMAIL PROTECTED] (supplier of updated sysklogd 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, 25 May 2006 11:07:52 +0200
Source: sysklogd
Binary: sysklogd klogd
Architecture: source i386
Version: 1.4.1-18
Distribution: unstable
Urgency: medium
Maintainer: Martin Schulze [EMAIL PROTECTED]
Changed-By: Martin Schulze [EMAIL PROTECTED]
Description:
klogd - Kernel Logging Daemon
sysklogd - System Logging Daemon
Closes: 98631 127579 154805 164153 225895 241350 255590 266985 284914 320119
322769 337712 347333 350764
Changes:
sysklogd (1.4.1-18) unstable; urgency=medium
.
* Removed asm/atomic.h since it is not needed anymore. (closes:
Bug#350764)
* Fixed typo in NMU-Disclaimer (closes: Bug#225895)
* Corrected getconf call in debian/rules to fix lagefile support
(closes: Bug#320119)
* Applied patch by Joey Hess to prevent klogd to be stopped/started too
fast (closes: Bug#284914)
* Finish /usr/share/doc transition with patch by Julien Cristau (closes:
Bug#337712, Bug#322769, Bug#255590)
* Reset the 'restart' flag immediately after entering the restart code.
Thanks to Dean Gaudet (closes: Bug#154805)
* Added support for /etc/default/{syslogd,klogd} files to contain
commandline arguments for syslogd and klogd (closes: Bug#98631,
Bug#127579, Bug#241350, Bug#266985)
* Added a description of system log level and link to sysctl(8) (closes:
Bug#164153)
* Acknowledging Joey's NMUs (closes: Bug#347333)
Files:
01aaa7e2e4af25e1ac7633f27b49173f 539 admin important sysklogd_1.4.1-18.dsc
079d5fd0973fc760c13a2b78a62cb422 25901 admin important
sysklogd_1.4.1-18.diff.gz
23c7049b894d5f4cf84e6076317eabfd 58096 admin important
sysklogd_1.4.1-18_i386.deb
bdceb4e32f8122f5f75c3147afdfffc9 39414 admin important klogd_1.4.1-18_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEdXtUW5ql+IAeqTIRAq3UAJ9X6R8YVAaoay4nvGpnEPTLtFYATgCfUq9+
XWqMumxdUJVpnhOTaL8cvJM=
=wx77
-END PGP SIGNATURE-
---End Message---
Bug#368765: marked as done (syslog-ng: ia64 buildd log indicates that bison is a needed build dependency)
Your message dated Thu, 25 May 2006 03:17:07 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#368765: fixed in syslog-ng 1.9.11-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) ---BeginMessage--- Package: syslog-ng Version: 1.9.9-1 Severity: serious Justification: no longer builds from source I was looking through the buildd logs for syslog to see why it wasn't in testing yet and I found the following in the ia64 build log: yacc -d `test -f 'cfg-grammar.y' || echo './'`cfg-grammar.y /bin/sh: yacc: command not found Syslog-ng appears to only build dep on flex and some other stuff. Flex only suggests bison, however. Bison should probaly be a build dep also since it seems perfectly valid to not install a suggested package when installing build deps. This problems appeears to be exactly the problem that the ia64 buildd is having. wt -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages syslog-ng depends on: ii libc6 2.3.6-7GNU C Library: Shared libraries ii util-linux2.12r-8Miscellaneous system utilities Versions of packages syslog-ng recommends: ii logrotate 3.7.1-3Log rotation utility -- no debconf information ---End Message--- ---BeginMessage--- Source: syslog-ng Source-Version: 1.9.11-1 We believe that the bug you reported is fixed in the latest version of syslog-ng, which is due to be installed in the Debian FTP archive: syslog-ng_1.9.11-1.diff.gz to pool/main/s/syslog-ng/syslog-ng_1.9.11-1.diff.gz syslog-ng_1.9.11-1.dsc to pool/main/s/syslog-ng/syslog-ng_1.9.11-1.dsc syslog-ng_1.9.11-1_i386.deb to pool/main/s/syslog-ng/syslog-ng_1.9.11-1_i386.deb syslog-ng_1.9.11.orig.tar.gz to pool/main/s/syslog-ng/syslog-ng_1.9.11.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. SZALAY Attila [EMAIL PROTECTED] (supplier of updated syslog-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: Thu, 25 May 2006 11:21:50 +0200 Source: syslog-ng Binary: syslog-ng Architecture: source i386 Version: 1.9.11-1 Distribution: unstable Urgency: low Maintainer: SZALAY Attila [EMAIL PROTECTED] Changed-By: SZALAY Attila [EMAIL PROTECTED] Description: syslog-ng - Next generation logging daemon Closes: 350120 350344 357071 367256 368765 Changes: syslog-ng (1.9.11-1) unstable; urgency=low . * New upstream version - Fixed log facility and priority detecting. (Closes: #350120, #350344, #357071, #367256) * Added bison to Build-Dependency. (Closes: #368765) Files: fa7df7f59b5adca2f68909a03edd5a49 622 admin extra syslog-ng_1.9.11-1.dsc 595882ee38767710d5910961633dd01e 314717 admin extra syslog-ng_1.9.11.orig.tar.gz 60e8579f413791ffc41f4d34c06c21a7 8369 admin extra syslog-ng_1.9.11-1.diff.gz 3680db0dd249162c1f1634a473ac445e 165560 admin extra syslog-ng_1.9.11-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEdYFA23Gu/Kug6LIRAnEGAJ9qHz9y9lCli4vQ/WcyGat1pmUdrwCgm91H yziWKpQIJgX+INwNy/z5WLk= =8OKQ -END PGP SIGNATURE- ---End Message---
Bug#350764: marked as done (sysklogd_1.4.1-17.1(mipsel/unstable): FTBFS: includes kernel header in userspace)
Your message dated Thu, 25 May 2006 02:47:21 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#350764: fixed in sysklogd 1.4.1-18
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)
---BeginMessage---
Package: sysklogd
Version: 1.4.1-17.1
Severity: serious
There was an error while trying to autobuild your package:
Automatic build of sysklogd_1.4.1-17.1 on mayer by sbuild/mipsel 85
Build started at 20060113-1423
[...]
make[1]: Entering directory `/build/buildd/sysklogd-1.4.1'
gcc -O2 -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-DSYSV -fomit-frame-pointer -fno-strength-reduce -DSYSLOG_INET
-DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\syslogd.pid\
-DDEBRELEASE=\17.1\ -c syslogd.c
gcc -O2 -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-DSYSV -fomit-frame-pointer -fno-strength-reduce -c pidfile.c
gcc -o syslogd syslogd.o pidfile.o
gcc -O2 -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-DSYSV -fomit-frame-pointer -fno-strength-reduce -DFSSTND
-DDEBRELEASE=\17.1\ -c klogd.c
gcc -O2 -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-DSYSV -fomit-frame-pointer -fno-strength-reduce -DALLOW_KERNEL_LOGGING -c
syslog.c
gcc -O2 -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-DSYSV -fomit-frame-pointer -fno-strength-reduce -DFSSTND -c ksym.c
gcc -O2 -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-DSYSV -fomit-frame-pointer -fno-strength-reduce -DFSSTND -c ksym_mod.c
In file included from /usr/include/asm/atomic.h:26,
from module.h:31,
from ksym_mod.c:97:
/usr/include/asm/cpu-features.h:15:35: error: cpu-feature-overrides.h: No
such file or directory
make[1]: *** [ksym_mod.o] Error 1
make[1]: Leaving directory `/build/buildd/sysklogd-1.4.1'
make: *** [build] Error 2
A full build log can be found at:
http://buildd.debian.org/build.php?arch=mipselpkg=sysklogdver=1.4.1-17.1
---End Message---
---BeginMessage---
Source: sysklogd
Source-Version: 1.4.1-18
We believe that the bug you reported is fixed in the latest version of
sysklogd, which is due to be installed in the Debian FTP archive:
klogd_1.4.1-18_i386.deb
to pool/main/s/sysklogd/klogd_1.4.1-18_i386.deb
sysklogd_1.4.1-18.diff.gz
to pool/main/s/sysklogd/sysklogd_1.4.1-18.diff.gz
sysklogd_1.4.1-18.dsc
to pool/main/s/sysklogd/sysklogd_1.4.1-18.dsc
sysklogd_1.4.1-18_i386.deb
to pool/main/s/sysklogd/sysklogd_1.4.1-18_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.
Martin Schulze [EMAIL PROTECTED] (supplier of updated sysklogd 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, 25 May 2006 11:07:52 +0200
Source: sysklogd
Binary: sysklogd klogd
Architecture: source i386
Version: 1.4.1-18
Distribution: unstable
Urgency: medium
Maintainer: Martin Schulze [EMAIL PROTECTED]
Changed-By: Martin Schulze [EMAIL PROTECTED]
Description:
klogd - Kernel Logging Daemon
sysklogd - System Logging Daemon
Closes: 98631 127579 154805 164153 225895 241350 255590 266985 284914 320119
322769 337712 347333 350764
Changes:
sysklogd (1.4.1-18) unstable; urgency=medium
.
* Removed asm/atomic.h since it is not needed anymore. (closes:
Bug#350764)
* Fixed typo in NMU-Disclaimer (closes: Bug#225895)
* Corrected getconf call in debian/rules to fix lagefile support
(closes: Bug#320119)
* Applied patch by Joey Hess to prevent klogd to be stopped/started too
fast (closes: Bug#284914)
* Finish /usr/share/doc transition with patch by Julien Cristau (closes:
Bug#337712, Bug#322769, Bug#255590)
* Reset the 'restart' flag immediately after entering the restart code.
Thanks to Dean Gaudet (closes: Bug#154805)
* Added support for /etc/default/{syslogd,klogd} files to contain
commandline arguments for syslogd and klogd (closes: Bug#98631,
Bug#127579, Bug#241350, Bug#266985)
* Added a description of system log level and link to sysctl(8) (closes:
Bug#164153)
*
Bug#320119: marked as done (sysklogd: Large file support is broken in the sarge version)
Your message dated Thu, 25 May 2006 02:47:21 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#320119: fixed in sysklogd 1.4.1-18
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)
---BeginMessage---
Package: sysklogd
Version: 1.4.1-17
Severity: grave
Justification: causes non-serious data loss
After upgrading our main syslog server to sarge, I found that some log files
were not updating. This was traced to the fact that large filesystem support
was not enabled properly. I applied the following patch to the debian/rules
file, and recompiled the package, and it works fine now.
--- debian/rules.orig 2005-07-27 13:29:59.0 +0800
+++ debian/rules2005-07-27 13:24:30.0 +0800
@@ -30,7 +30,7 @@
ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS)))
CFLAGS = -g -O2 -Wall $(getconf LFS_CFLAGS) -D_LARGEFILE_SOURCE
else
-CFLAGS = -O2 -Wall $(getconf LFS_CFLAGS) -D_LARGEFILE_SOURCE
+CFLAGS = -O2 -Wall $(getconf LFS_CFLAGS) -D_LARGEFILE64_SOURCE
-D_FILE_OFFSET_BITS=64
endif
ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
STRIP = -s
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.12.3
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages sysklogd depends on:
ii klogd [linux-kernel-log-dae 1.4.1-17 Kernel Logging Daemon
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
-- no debconf information
---End Message---
---BeginMessage---
Source: sysklogd
Source-Version: 1.4.1-18
We believe that the bug you reported is fixed in the latest version of
sysklogd, which is due to be installed in the Debian FTP archive:
klogd_1.4.1-18_i386.deb
to pool/main/s/sysklogd/klogd_1.4.1-18_i386.deb
sysklogd_1.4.1-18.diff.gz
to pool/main/s/sysklogd/sysklogd_1.4.1-18.diff.gz
sysklogd_1.4.1-18.dsc
to pool/main/s/sysklogd/sysklogd_1.4.1-18.dsc
sysklogd_1.4.1-18_i386.deb
to pool/main/s/sysklogd/sysklogd_1.4.1-18_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.
Martin Schulze [EMAIL PROTECTED] (supplier of updated sysklogd 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, 25 May 2006 11:07:52 +0200
Source: sysklogd
Binary: sysklogd klogd
Architecture: source i386
Version: 1.4.1-18
Distribution: unstable
Urgency: medium
Maintainer: Martin Schulze [EMAIL PROTECTED]
Changed-By: Martin Schulze [EMAIL PROTECTED]
Description:
klogd - Kernel Logging Daemon
sysklogd - System Logging Daemon
Closes: 98631 127579 154805 164153 225895 241350 255590 266985 284914 320119
322769 337712 347333 350764
Changes:
sysklogd (1.4.1-18) unstable; urgency=medium
.
* Removed asm/atomic.h since it is not needed anymore. (closes:
Bug#350764)
* Fixed typo in NMU-Disclaimer (closes: Bug#225895)
* Corrected getconf call in debian/rules to fix lagefile support
(closes: Bug#320119)
* Applied patch by Joey Hess to prevent klogd to be stopped/started too
fast (closes: Bug#284914)
* Finish /usr/share/doc transition with patch by Julien Cristau (closes:
Bug#337712, Bug#322769, Bug#255590)
* Reset the 'restart' flag immediately after entering the restart code.
Thanks to Dean Gaudet (closes: Bug#154805)
* Added support for /etc/default/{syslogd,klogd} files to contain
commandline arguments for syslogd and klogd (closes: Bug#98631,
Bug#127579, Bug#241350, Bug#266985)
* Added a description of system log level and link to sysctl(8) (closes:
Bug#164153)
* Acknowledging Joey's NMUs (closes: Bug#347333)
Files:
01aaa7e2e4af25e1ac7633f27b49173f 539 admin important sysklogd_1.4.1-18.dsc
079d5fd0973fc760c13a2b78a62cb422 25901 admin important
sysklogd_1.4.1-18.diff.gz
23c7049b894d5f4cf84e6076317eabfd 58096 admin important
sysklogd_1.4.1-18_i386.deb
bdceb4e32f8122f5f75c3147afdfffc9 39414 admin important klogd_1.4.1-18_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEdXtUW5ql+IAeqTIRAq3UAJ9X6R8YVAaoay4nvGpnEPTLtFYATgCfUq9+
XWqMumxdUJVpnhOTaL8cvJM=
=wx77
-END PGP SIGNATURE-
---End
Bug#305479: is it me you looking for?
Hi there lovely, I was searching the net few days ago. I am neaw to this thing. and saw your profile. I decided to email you cause I found you attractive. I might come down to your city in few weeks. Let me know if we can meet each other in person. I bam attractive girl.a I am subre you won't regret it. Replby to my personal email at [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368681: cvs: does not flag conflicted copies anymore
I cannot reproduce what you are describing. Could you please elaborate ? Sure. First, it happens on branches when using -j (some tag of head) -j (some other tag of head). First, I tried in a local repo, I didn't reproduce it, BUT I got something weird from cvs status anyway, so here it is: cvs status changelog === File: changelog Status: Unresolved Conflict Working revision:1.307.2.4 cvs status: Can't parse date/time: `Result of merge UTC'. Result of merge UTC Repository revision: 1.307.2.4 /home/cvs/debian/cyrus21-imapd/debian/changelog,v Commit Identifier: (none) Sticky Tag: sarge-branch (branch: 1.307.2) Sticky Date: (none) Sticky Options: (none) Notice the strange error message cvs status: Can't parse date/time: `Result of merge UTC'. Then I tried it using a remote repository, in Alioth, over ssh. Here's the full dump: $ export CVSROOT=:ext:[EMAIL PROTECTED]:/cvsroot/pkg-hpijs $ cvs -q checkout -d test-merge -r sarge-backport-branch hplip [ messages from cvs checkout removed -- all works fine ] $ cd test-merge/ $ cvs log debian/changelog | head -20 RCS file: /cvsroot/pkg-hpijs/hplip/debian/changelog,v Working file: debian/changelog head: 1.207 branch: locks: strict access list: symbolic names: debian_version_0_9_11-1bpo1: 1.102.2.7 debian_version_0_9_11-2: 1.207 debian_version_0_9_11-1: 1.202 debian_version_0_9_10-1: 1.187 debian_version_0_9_9-2: 1.181 debian_version_0_9_9-1: 1.177 debian_version_0_9_8-1_unreleased: 1.160 debian_version_0_9_7-3bpo1: 1.102.2.6 debian_version_0_9_7-4: 1.132 debian_version_0_9_7-3: 1.130 debian_version_0_9_7-0_2sarge1: 1.102.2.3 debian_version_0_9_7-2: 1.128 $ cvs update -dP -j debian_version_0_9_7-3 -j debian_version_0_9_11-2 [ cvs update log removed. Some conflicts happen, no weird error messages show up ] $ cvs status debian/README.Source === File: README.Source Status: Up-to-date Working revision:1.5.2.1 Repository revision: 1.5.2.1 /cvsroot/pkg-hpijs/hplip/debian/README.Source,v Sticky Tag: sarge-backport-branch (branch: 1.5.2) Sticky Date: (none) Sticky Options: (none) $ head -n6 debian/README.Source README.Source $Id: README.Source,v 1.5.2.1 2006/05/24 03:40:28 hmh Exp $ === $Id: README.Source,v 1.6 2006/03/18 19:09:22 hmh Exp $ 1.6 Notice the file has a broken conflict, which is not detected by cvs status. Nothing else detects it either, if I commit, I will commit a conflicted file with conflict hunks. The update command above is guaranteed to cause conflicts, as that merge has been already performed (and committed) in that branch. But I did notice the error when trying that merge *the first time around*, when those changes had not been committed yet. The environment: LC_MESSAGES=en_US.ISO-8859-1 LANG=pt_BR.ISO-8859-1 RSYNC_RSH=ssh Local CVS version: $ cvs --version Concurrent Versions System (CVS) 1.12.13 (client/server) $ dpkg -s cvs | grep Version: Version: 1:1.12.13-2 Remote CVS version: $ ssh cvs.alioth.debian.org cvs --version Concurrent Versions System (CVS) 1.12.9 (client/server) $ ssh cvs.alioth.debian.org dpkg -s cvs | grep Version: Version: 1:1.12.9-14 -- 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]
Bug#368846: emacs-snapshot: FTBFS with new coreutils
Package: emacs-snapshot Version: 1:20060524-1 Severity: serious Tags: patch There was a problem building this week's snapshot. From the end of the `debuild' log (sorry for the German, but the problem should be clear anyway): # save binary from deletion mv src/emacs src/nox-emacs touch emacs-nox-stamp dh_testdir touch build-stamp fakeroot debian/rules binary dh_testdir touch build-stamp cd debian csplit -s -f README. README.in '/@@PATCH_LIST_HERE@@/' cp debian/README.00 debian/README.tmp dpatch-list-patch | tail +2 | grep -v -e '^debian/patches/' | \ sed '[EMAIL PROTECTED] [EMAIL PROTECTED]@' debian/README.tmp tail: „+2“ kann nicht zum Lesen geöffnet werden: Datei oder Verzeichnis nicht gefunden tail +2 debian/README.01 debian/README.tmp tail: „+2“ kann nicht zum Lesen geöffnet werden: Datei oder Verzeichnis nicht gefunden make: *** [debian/README.Debian] Fehler 1 debuild: fatal error at line 1224: fakeroot debian/rules binary failed The reason is a change in the coreutils package, which as of version 5.96-1 conforms to the POSIX 2001 standard by default; that standard disallows the `program +k file' syntax. The following patch fixes the problem: --- debian/rules~ 2006-05-25 12:46:42.0 +0200 +++ debian/rules2006-05-25 13:45:29.0 +0200 @@ -317,9 +317,9 @@ debian/README.Debian: debian/README.in debian/patches/*.dpatch cd debian csplit -s -f README. README.in '/@@PATCH_LIST_HERE@@/' cp debian/README.00 debian/README.tmp - dpatch-list-patch | tail +2 | grep -v -e '^debian/patches/' | \ + dpatch-list-patch | tail -n +2 | grep -v -e '^debian/patches/' | \ sed '[EMAIL PROTECTED] [EMAIL PROTECTED]@' debian/README.tmp - tail +2 debian/README.01 debian/README.tmp + tail -n +2 debian/README.01 debian/README.tmp mv debian/README.tmp debian/README.Debian .PHONY: debian/README.Debian DEB_TRASH += debian/README.tmp debian/README.00 debian/README.01 -- 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.16.18 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Bug#367059: 1.5 regression?
On Thursday 25 May 2006 04:30, Filipus Klutiero wrote: Hi, is it possible to confirm that this is a 1.5 regression, and that the issue didn't exist in 1.4? Yes, with version 1.4 everything worked fine. It's an issue of the latest version. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368838: marked as done (xmorph_1:20060525(amd64/unstable): diw_map.c:47:28: error: X11/bitmaps/gray: No such file or directory)
Your message dated Thu, 25 May 2006 05:47:08 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#368838: fixed in xmorph 1:20060526.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) ---BeginMessage--- Package: xmorph Version: 1:20060525 Severity: serious Hello, There was an error while trying to autobuild your package: if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../libmorph -I../intl -Wall -g -O2 -DREAL=double -DRGBA_MESH_WARP -DNDEBUG_LIBMORPH_REF_COUNT -Wall -g -O2 -MT xmorph-diw_map.o -MD -MP -MF .deps/xmorph-diw_map.Tpo -c -o xmorph-diw_map.o `test -f 'diw_map.c' || echo './'`diw_map.c; \ then mv -f .deps/xmorph-diw_map.Tpo .deps/xmorph-diw_map.Po; else rm -f .deps/xmorph-diw_map.Tpo; exit 1; fi diw_map.c:47:28: error: X11/bitmaps/gray: No such file or directory diw_map.c: In function 'mpt_scroll_cb': diw_map.c:1018: warning: cast from pointer to integer of different size diw_map.c: In function 'image_scroll_cb': diw_map.c:1057: warning: cast from pointer to integer of different size diw_map.c: In function 'init_diw_stuff': diw_map.c:1736: error: 'gray_bits' undeclared (first use in this function) diw_map.c:1736: error: (Each undeclared identifier is reported only once diw_map.c:1736: error: for each function it appears in.) diw_map.c:1736: error: 'gray_width' undeclared (first use in this function) diw_map.c:1736: error: 'gray_height' undeclared (first use in this function) make[3]: *** [xmorph-diw_map.o] Error 1 make[3]: Leaving directory `/build/buildd/xmorph-20060525/xmorph' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/buildd/xmorph-20060525' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd/xmorph-20060525' make: *** [build-stamp] Error 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=amd64pkg=xmorphver=1:20060525 Best regards Frederik Schueler ---End Message--- ---BeginMessage--- Source: xmorph Source-Version: 1:20060526.1 We believe that the bug you reported is fixed in the latest version of xmorph, which is due to be installed in the Debian FTP archive: gtkmorph-example_20060526.1_all.deb to pool/main/x/xmorph/gtkmorph-example_20060526.1_all.deb gtkmorph_20060526.1_i386.deb to pool/main/x/xmorph/gtkmorph_20060526.1_i386.deb libmorph-dev_20060526.1_i386.deb to pool/main/x/xmorph/libmorph-dev_20060526.1_i386.deb libmorph_20060526.1_i386.deb to pool/main/x/xmorph/libmorph_20060526.1_i386.deb xmorph_20060526.1.dsc to pool/main/x/xmorph/xmorph_20060526.1.dsc xmorph_20060526.1.tar.gz to pool/main/x/xmorph/xmorph_20060526.1.tar.gz xmorph_20060526.1_i386.deb to pool/main/x/xmorph/xmorph_20060526.1_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. A Mennucc1 [EMAIL PROTECTED] (supplier of updated xmorph 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, 25 May 2006 14:03:47 +0200 Source: xmorph Binary: gtkmorph-example gtkmorph libmorph-dev libmorph xmorph Architecture: source i386 all Version: 1:20060526.1 Distribution: unstable Urgency: low Maintainer: A Mennucc1 [EMAIL PROTECTED] Changed-By: A Mennucc1 [EMAIL PROTECTED] Description: gtkmorph - Digital image warp and morph (gtk) gtkmorph-example - digital image warp and morph, examples libmorph - digital image warping library libmorph-dev - digital image warping library (development files) xmorph - digital image warp and morph (x11) Closes: 368838 Changes: xmorph (1:20060526.1) unstable; urgency=low . * needs to build-dep on 'xbitmaps'. Fixes FTBFS, thanks to Frederik Schüler (Closes: #368838). * Bumped standards version. Files: bc85f4e4aec93d32a071744ab68b1eaf 717 graphics optional xmorph_20060526.1.dsc 4ce4e829698cfa27edc24ae92c0d34b8 1562696 graphics optional xmorph_20060526.1.tar.gz 29b162fca2ee6f191d6520635ec99288 104492 libs optional libmorph_20060526.1_i386.deb 5f063727e317ad3c48292d29f14b5165 46034 graphics optional xmorph_20060526.1_i386.deb 500366d013f816a58e743226f8198e3e 60068 libdevel optional libmorph-dev_20060526.1_i386.deb
Bug#368681: cvs: does not flag conflicted copies anymore
On Thu, May 25, 2006 at 08:51:44AM -0300, Henrique de Moraes Holschuh wrote: I cannot reproduce what you are describing. Could you please elaborate ? Sure. First, it happens on branches when using -j (some tag of head) -j (some other tag of head). First, I tried in a local repo, I didn't reproduce it, BUT I got something weird from cvs status anyway, so here it is: cvs status changelog === File: changelog Status: Unresolved Conflict Working revision:1.307.2.4 cvs status: Can't parse date/time: `Result of merge UTC'. Result of merge UTC Repository revision: 1.307.2.4 /home/cvs/debian/cyrus21-imapd/debian/changelog,v Commit Identifier: (none) Sticky Tag: sarge-branch (branch: 1.307.2) Sticky Date: (none) Sticky Options: (none) Notice the strange error message cvs status: Can't parse date/time: `Result of merge UTC'. Then I tried it using a remote repository, in Alioth, over ssh. Here's the full dump: $ export CVSROOT=:ext:[EMAIL PROTECTED]:/cvsroot/pkg-hpijs $ cvs -q checkout -d test-merge -r sarge-backport-branch hplip [ messages from cvs checkout removed -- all works fine ] $ cd test-merge/ $ cvs log debian/changelog | head -20 RCS file: /cvsroot/pkg-hpijs/hplip/debian/changelog,v Working file: debian/changelog head: 1.207 branch: locks: strict access list: symbolic names: debian_version_0_9_11-1bpo1: 1.102.2.7 debian_version_0_9_11-2: 1.207 debian_version_0_9_11-1: 1.202 debian_version_0_9_10-1: 1.187 debian_version_0_9_9-2: 1.181 debian_version_0_9_9-1: 1.177 debian_version_0_9_8-1_unreleased: 1.160 debian_version_0_9_7-3bpo1: 1.102.2.6 debian_version_0_9_7-4: 1.132 debian_version_0_9_7-3: 1.130 debian_version_0_9_7-0_2sarge1: 1.102.2.3 debian_version_0_9_7-2: 1.128 $ cvs update -dP -j debian_version_0_9_7-3 -j debian_version_0_9_11-2 [ cvs update log removed. Some conflicts happen, no weird error messages show up ] $ cvs status debian/README.Source === File: README.Source Status: Up-to-date Working revision:1.5.2.1 Repository revision: 1.5.2.1 /cvsroot/pkg-hpijs/hplip/debian/README.Source,v Sticky Tag: sarge-backport-branch (branch: 1.5.2) Sticky Date: (none) Sticky Options: (none) $ head -n6 debian/README.Source README.Source $Id: README.Source,v 1.5.2.1 2006/05/24 03:40:28 hmh Exp $ === $Id: README.Source,v 1.6 2006/03/18 19:09:22 hmh Exp $ 1.6 Notice the file has a broken conflict, which is not detected by cvs status. Nothing else detects it either, if I commit, I will commit a conflicted file with conflict hunks. It seems this is a design decision by CVS upstream - see http://www.cygwin.com/ml/cygwin/2006-03/msg00668.html for another description of the same bug. It's rather annoying that they have changed the behaviour so blatantly from what people are used to... -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] Welcome my son, welcome to the machine. signature.asc Description: Digital signature
Bug#368855: dpkg : erreur de traitement de autoconf
Package: autoconf Version: 2.59.cvs.2006.05.13-1 Severity: grave Justification: renders package unusable Since today's apt-get dist-upgrade I get this message: Dépaquetage de autoconf (à partir de .../autoconf_2.59.cvs.2006.05.13-1_all.deb) ... Paramétrage de autoconf (2.59.cvs.2006.05.13-1) ... install-info(/usr/info/standards.info): failed to lock dir for editing! Le fichier existe. dpkg : erreur de traitement de autoconf (--configure) : le sous-processus post-installation script a retourné une erreur de sortie d'état 17 Des erreurs ont été rencontrées pendant l'exécution : autoconf E: Sub-process /usr/bin/dpkg returned an error code (1) The folder /usr/info/ doesn't exist on my system. autoconf and automake remain unconfigured and unusable after this upgrade. I uninstalled autoconf and automake (via dpkg -r because apt-get remove was failing with the same error code) until this bug is fixed. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages autoconf depends on: ii debianutils 2.16 Miscellaneous utilities specific t ii m41.4.4-1a macro processing language ii perl 5.8.8-4Larry Wall's Practical Extraction Versions of packages autoconf recommends: pn automaken none (no description available)
Bug#368857: linux-wlan-ng-firmware: Should be in contrib
Package: linux-wlan-ng-firmware Severity: serious Justification: Policy 2.2 As I understand it, the sole purpose of this package is to download non-free firmware. This fits into 'contrib', not 'main', since it depends on non-free software for its ultimate operation. Packages like this are given as an example of packages for contrib. From Policy 2.2.2: Examples of packages which would be included in _contrib_ are: ... * wrapper packages or other sorts of free accessories for non-free programs. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-rc3y Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Fixed in NMU of packagesearch 2.0.6-0.1
Processing commands for [EMAIL PROTECTED]: tag 357355 + fixed Bug#357355: FTBS: fails to build for current unstable (duplicate template instantiation) Tags were: patch Bug#360553: packagesearch_2.0.6(amd64/unstable): FTBFS: duplicate explicit instantiation of 'class Tagcoll::OpSetint' Tags added: fixed tag 360553 + fixed Bug#360553: packagesearch_2.0.6(amd64/unstable): FTBFS: duplicate explicit instantiation of 'class Tagcoll::OpSetint' Tags were: fixed patch Bug#357355: FTBS: fails to build for current unstable (duplicate template instantiation) 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#339526: marked as done (spamassassin: CVE-2005-3351: Bus Error Spam Detection Bypass Vulnerability)
Your message dated Thu, 25 May 2006 15:38:34 +0200 with message-id [EMAIL PROTECTED] and subject line reopening 339526, found 339526 in 3.0.3-2, notfound 339526 in 3.1.0a-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) ---BeginMessage--- Package: spamassassin Version: 3.0.3-1 Severity: grave File: spamassassin Security Focus is reporting a problem with spamassassin: http://www.securityfocus.com/bid/15373 In short, there is a perl regexp that crashes if spamassassin tries to pass an email with thousands of addressess in it. They refer to the spamassassin bugzilla: http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4570 In that bugzilla entry someone suggested this patch: http://issues.apache.org/SpamAssassin/attachment.cgi?id=3121 And the end of the bugzilla report it says that the fix was committed with 331942. -- Geoff Crompton ---End Message--- ---BeginMessage--- Version: 3.1.0a-1 this bug does not concern etch/sid. closing bug for those versions. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org signature.asc Description: Digital signature ---End Message---
Bug#368846: emacs-snapshot: FTBFS with new coreutils
Sven Joachim [EMAIL PROTECTED] writes: - dpatch-list-patch | tail +2 | grep -v -e '^debian/patches/' | \ + dpatch-list-patch | tail -n +2 | grep -v -e '^debian/patches/' | \ Thanks! This version built correctly on almost all buildds since that particular version of coreutils hasn't reached them yet, so I'll merge your patch in the next upload. -- ,''`. : :' :Romain Francoise [EMAIL PROTECTED] `. `' http://people.debian.org/~rfrancoise/ `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#358575: Purging mailman safely
On Thu, May 25, 2006 at 08:37:10AM +0100, Roger Lynn wrote: Would replacing (please excuse the line wrap): for file in $(sed -e ':/etc/mailman:!d' -e 's:^[0-9a-f]* *::' /var/lib/ucf/hashfile); do with for file in $(sed -e '\|^[0-9a-fA-F]\+[[:space:]]\+/etc/mailman/|!d' -e 's|^[0-9a-fA-F]\+[[:space:]]\+||' /var/lib/ucf/hashfile); do sed lines are not the easiest to read when one didn't write them in the last 5 minutes. Take the line from 2.1.8-1, it is the one I stand behind. in /var/lib/dpkg/info/mailman.postrm (is this the right file?) That's the right file. allow me to safely purge 2.1.7-1 without having to compile and install 2.1.8-1 first? The line from 2.1.8-1 should be OK. You can test what files it will touch by running the part between $() (without the $()) and looking at the output. If it does something wrong, please tell me. I assume the same would apply to Sarge users. Yes. Or they can fish 2.1.5-8sarge3 out of the proposed update queue. -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#368681: cvs: does not flag conflicted copies anymore
Processing commands for [EMAIL PROTECTED]: tag 368681 = upstream Bug#368681: cvs: does not flag conflicted copies anymore Tags were: moreinfo Tags set to: 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#368857: [Linux-wlan-ng-devel] Bug#368857: linux-wlan-ng-firmware: Should be in contrib
On Thu, May 25, 2006 at 09:25:11AM -0400, Dylan Thurston wrote: As I understand it, the sole purpose of this package is to download non-free firmware. This fits into 'contrib', not 'main', since it depends on non-free software for its ultimate operation. Packages like this are given as an example of packages for contrib. From Policy 2.2.2: Examples of packages which would be included in _contrib_ are: ... * wrapper packages or other sorts of free accessories for non-free programs. Maybe you are right, but before doing the split (see later) I would like to be sure. The driver and the orig.tgz is DFSG clean. It works with no firmware on most adapters. We removed from the orig.tgz the firmware files (included in the upstream tgz, a project founded by the chip/firmware producer IIRC) since there was no license saying: yes, you can redistribute these files. This package includes a 10 lines shell script that uses svn to checkout the firmware files from the upstream svn repository. For convenience we put this shell script in the same source package (actually in the diff.gz). This driver does not need the maybe-non-free stuff, but some users may be interested in using the firmware files. We could split the source package in two, one for main and one for contrib, but since I'm not sure this borderline situation is a real policy violation, I've not done it jet. In case it is, we will split. But I'm not that sure that this is a clear policy violation. This is not a wrapper package, nor a package that depends on a non free external software. Any idea if a similar package exists in main/contrib? Regards -- Enrico Tassi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#358575: #358575 and sarge
On Wed, May 24, 2006 at 07:22:11PM +0100, Sam Morris wrote: Will you consider fixing this in Sarge also? I have submitted an update to sarge in early April. It will be reviewed by the stable release managers and (I hope) part of the next sarge point release. It seems I submitted it too late for inclusion in 3.1r2. -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368832: gnome-media-common: fails to install
tag 368832 + pending tag 368833 + pending thanks Le jeudi 25 mai 2006 à 10:46 +0200, yves caniou a écrit : Package: gnome-media-common Severity: grave Justification: renders package unusable Try to replace the file /usr/share/omf/gnome-media/grecord-zh_CN.omf which is part of the package gnome-media These bugs are fixed in the SVN repository, but the new version is waiting for the ftp-masters to accept the new nautilus-cd-burner packages. -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom signature.asc Description: Ceci est une partie de message numériquement signée
Bug#368681: cvs: does not flag conflicted copies anymore
tag 368681 = upstream thanks On Thu, 25 May 2006, Steve McIntyre wrote: I'm planning on digging into it further over the next couple of days; I'm very tempted to patch this change back out, if it is this simple... Can we have a warning in place until then? Of course this bug should be warning enough (given the severity), but not everyone uses apt-listbugs... -- 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]
Bug#368681: cvs: does not flag conflicted copies anymore
On Thu, May 25, 2006 at 11:18:44AM -0300, Henrique de Moraes Holschuh wrote: On Thu, 25 May 2006, Steve McIntyre wrote: Notice the file has a broken conflict, which is not detected by cvs status. Nothing else detects it either, if I commit, I will commit a conflicted file with conflict hunks. It seems this is a design decision by CVS upstream - see http://www.cygwin.com/ml/cygwin/2006-03/msg00668.html I did not expect CVS upstream to be actively sabotaging CVS. Thank you for warning me about it. Please consider adding a very visible warning in the NEWS.Debian file (I'd add it as a debconf note of priority high, but to each its own) about it ASAP. for another description of the same bug. It's rather annoying that they have changed the behaviour so blatantly from what people are used to... So, after a non-joke merge I have a thousand files I have to manually verify for conflicts, because CVS will flag *all* of them the same way in the cvs status and cvs update commands (which are almost always the means used to verify a working copy before a commit), on top of allowing commits of conflicted crap without a warning? I didn't test a graphical front-end, but people using those expect to have those bright-red ! marks on conflicted files after a merge, I guess this won't work anymore either. Need I remind anyone that manually grepping for conflict markers is NOT something the majority of CVS users will do, because the tool was, until a few days ago, supposed to do it for them? This change of behaviour is dangerous, and dumb beyond measure. Doing such a change silently just adds to the injury, and it is not acceptable at all. I hope we can do something about it. I'm planning on digging into it further over the next couple of days; I'm very tempted to patch this change back out, if it is this simple... -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] ...In the UNIX world, people tend to interpret `non-technical user' as meaning someone who's only ever written one device driver. -- Daniel Pead signature.asc Description: Digital signature
Bug#368681: cvs: does not flag conflicted copies anymore
On Thu, 25 May 2006, Steve McIntyre wrote: Notice the file has a broken conflict, which is not detected by cvs status. Nothing else detects it either, if I commit, I will commit a conflicted file with conflict hunks. It seems this is a design decision by CVS upstream - see http://www.cygwin.com/ml/cygwin/2006-03/msg00668.html I did not expect CVS upstream to be actively sabotaging CVS. Thank you for warning me about it. Please consider adding a very visible warning in the NEWS.Debian file (I'd add it as a debconf note of priority high, but to each its own) about it ASAP. for another description of the same bug. It's rather annoying that they have changed the behaviour so blatantly from what people are used to... So, after a non-joke merge I have a thousand files I have to manually verify for conflicts, because CVS will flag *all* of them the same way in the cvs status and cvs update commands (which are almost always the means used to verify a working copy before a commit), on top of allowing commits of conflicted crap without a warning? I didn't test a graphical front-end, but people using those expect to have those bright-red ! marks on conflicted files after a merge, I guess this won't work anymore either. Need I remind anyone that manually grepping for conflict markers is NOT something the majority of CVS users will do, because the tool was, until a few days ago, supposed to do it for them? This change of behaviour is dangerous, and dumb beyond measure. Doing such a change silently just adds to the injury, and it is not acceptable at all. I hope we can do something about it. -- 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: Re: Bug#368832: gnome-media-common: fails to install
Processing commands for [EMAIL PROTECTED]: tag 368832 + pending Bug#368832: gnome-media-common: fails to install There were no tags set. Tags added: pending tag 368833 + pending Bug#368833: libgnome-media0: Fails to install 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#368872: libxslt: FTBFS on alpha/MIPS
Package: libxslt Version: 1.1.16-1 Severity: serious Justification: no longer builds from source libxslt FTBFS on alpha/MIPS since over 3 weeks. I have no clue about the causes/fix (please refer to the buildd logs) and am filing in case the maintainers didn't notice the issue yet. This is one of the top 10 stallers according to Bjorn Stenberg's site, stalling [partially] 17 packages directly, including postgresql-8.1 8.1.4-1 (among other issues), which fixes several vulnerabilities. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368795: libtktable: Call a missing file
On Thu, May 25, 2006 at 01:39:28AM +0300, Thierry Randrianiriana wrote: Package: libtktable Version: 2.9-3 Severity: serious libtktable calls a missing file in pkgIndex.tcl 'libTktable2.9.a' instead of 'libTktable2.9.so'. I have the error : couldn't load file /usr/lib/Tktable2.9/libTktable2.9.a: /usr/lib/Tktable2.9/libTktable2.9.a: cannot open shared object file: No such file or directory while executing load /usr/lib/Tktable2.9/libTktable2.9.a Tktable (package ifneeded script) invoked from within ... So, tktable 2.9-3 isn't how I intended it anyway. I wanted binary packages named libtktable-2.9-dev and libtktable-2.9, to gracefully prevent new versions moving to testing before depending applications are uploaded. Lars is apparently too busy to do uploads. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#358493: marked as done (FTBFS: testsuite failures.)
Your message dated Thu, 25 May 2006 08:17:21 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#358493: fixed in tagcoll 1.6.2-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)
---BeginMessage---
Package: tagcoll
Version: 1.6.1-1
Severity: serious
Justification: no longer builds from source
tagcoll fails to build on Alpha, IA64 and Sparc. E.g. alpha:
make[3]: Entering directory `/tmp/buildd/tagcoll-1.6.1/tests'
[...]
tagcoll_mmapindex: .
tagcoll_opset: ./bin/sh: line 4: 8481 Aborted (core dumped)
${dir}$tst
FAIL: libtagcoll-test
Checking normal copy... plain, remove-unfaceted, remove-tags, patch, items, OK.
Checking reverse... plain, double, OK.
Checking grep... plain, OK.
Checking diff... plain, OK.
PASS: tagcoll-test
==
1 of 2 tests failed
Full logs at
http://buildd.debian.org/build.php?arch=pkg=tagcoll
Falk
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: alpha
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-rc4-dirty
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15)
---End Message---
---BeginMessage---
Source: tagcoll
Source-Version: 1.6.2-2
We believe that the bug you reported is fixed in the latest version of
tagcoll, which is due to be installed in the Debian FTP archive:
libtagcoll-dev_1.6.2-2_i386.deb
to pool/main/t/tagcoll/libtagcoll-dev_1.6.2-2_i386.deb
tagcoll_1.6.2-2.diff.gz
to pool/main/t/tagcoll/tagcoll_1.6.2-2.diff.gz
tagcoll_1.6.2-2.dsc
to pool/main/t/tagcoll/tagcoll_1.6.2-2.dsc
tagcoll_1.6.2-2_i386.deb
to pool/main/t/tagcoll/tagcoll_1.6.2-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.
Arnaud Fontaine [EMAIL PROTECTED] (supplier of updated tagcoll 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: Wed, 24 May 2006 00:01:22 +0200
Source: tagcoll
Binary: libtagcoll-dev tagcoll
Architecture: source i386
Version: 1.6.2-2
Distribution: unstable
Urgency: low
Maintainer: Enrico Zini [EMAIL PROTECTED]
Changed-By: Arnaud Fontaine [EMAIL PROTECTED]
Description:
libtagcoll-dev - Functions used to manipulate tagged collections (development
vers
tagcoll- Commandline tool to perform operations on tagged collections
Closes: 358493
Changes:
tagcoll (1.6.2-2) unstable; urgency=low
.
* Fix FTBFS on alpha by adding g++-4.1 in Build-Depends. Closes: #358493.
* Update Standards-Version to 3.7.2 (no changes needed).
* Added myself to Uploaders.
Files:
40169a4d1e8b72d18f05f1cbb8f69373 796 libdevel optional tagcoll_1.6.2-2.dsc
3e6d9266140a46ab35bd06f4862bb7b1 4548 libdevel optional tagcoll_1.6.2-2.diff.gz
7ee50c6971da7c1f94f29767a4573441 857034 misc optional tagcoll_1.6.2-2_i386.deb
2a1f8b9548330fc287e77890d05f7deb 2462612 libdevel optional
libtagcoll-dev_1.6.2-2_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEdch39LSwzHl+v6sRAp+bAJ9njQvuBf0sAMxXnsjKz4u1aMNmqQCgiuQM
cB4VHeAvew5ttUn7JRZZTDU=
=R27v
-END PGP SIGNATURE-
---End Message---
Bug#368681: cvs: does not flag conflicted copies anymore
Hi all! =) On 5/25/06, Henrique de Moraes Holschuh [EMAIL PROTECTED] wrote: Can we have a warning in place until then? Of course this bug should be warning enough (given the severity), but not everyone uses apt-listbugs... I'm already on the trail to see if reversing this works... If so, we can expect a -3 stomping this RC out in the shortest time :D I do suppose however, that still putting the warning in would be nice, especially for folks expecting the _new_ behavior (could be wrogn though)... Cheers, Zakame -- Zak B. Elep || http://zakame.spunge.org [EMAIL PROTECTED] || [EMAIL PROTECTED] 1486 7957 454D E529 E4F1 F75E 5787 B1FD FA53 851D
Bug#368855: marked as done (dpkg : erreur de traitement de autoconf)
Your message dated Thu, 25 May 2006 09:09:09 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#368855: =?UTF-8?Q?dpkg=C2=A0:?= erreur de traitement de autoconf 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) ---BeginMessage--- Package: autoconf Version: 2.59.cvs.2006.05.13-1 Severity: grave Justification: renders package unusable Since today's apt-get dist-upgrade I get this message: Dépaquetage de autoconf (à partir de .../autoconf_2.59.cvs.2006.05.13-1_all.deb) ... Paramétrage de autoconf (2.59.cvs.2006.05.13-1) ... install-info(/usr/info/standards.info): failed to lock dir for editing! Le fichier existe. dpkg : erreur de traitement de autoconf (--configure) : le sous-processus post-installation script a retourné une erreur de sortie d'état 17 Des erreurs ont été rencontrées pendant l'exécution : autoconf E: Sub-process /usr/bin/dpkg returned an error code (1) The folder /usr/info/ doesn't exist on my system. autoconf and automake remain unconfigured and unusable after this upgrade. I uninstalled autoconf and automake (via dpkg -r because apt-get remove was failing with the same error code) until this bug is fixed. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages autoconf depends on: ii debianutils 2.16 Miscellaneous utilities specific t ii m41.4.4-1a macro processing language ii perl 5.8.8-4Larry Wall's Practical Extraction Versions of packages autoconf recommends: pn automaken none (no description available) ---End Message--- ---BeginMessage--- Jean-Philippe [EMAIL PROTECTED] writes: Since today's apt-get dist-upgrade I get this message: Dépaquetage de autoconf (à partir de .../autoconf_2.59.cvs.2006.05.13-1_all.deb) ... Paramétrage de autoconf (2.59.cvs.2006.05.13-1) ... install-info(/usr/info/standards.info): failed to lock dir for editing! Le fichier existe. dpkg : erreur de traitement de autoconf (--configure) : le sous-processus post-installation script a retourné une erreur de sortie d'état 17 Des erreurs ont été rencontrées pendant l'exécution : autoconf E: Sub-process /usr/bin/dpkg returned an error code (1) This is not a bug in the autoconf package. You have a stale /usr/share/info/dir.lock. If you remove it, it will fix the problem. install-info should have advised you of this, but it has a bug that kept it from doing so. -- Ben Pfaff email: [EMAIL PROTECTED] web: http://benpfaff.org ---End Message---
Bug#368864: tomcat5: fails throwing a java.lang.OutOfMemoryError exception
Package: tomcat5 Version: 5.0.30-9 Severity: grave Justification: renders package unusable When there have been some 5 to 10 web application deployments, it throws this exception: java.lang.OutOfMemoryError: PermGen space It makes tomcat nearly unusable, because yo must restart it every time it shows that behaviour. Anyway, I've found that it is a known bug so it has been corrected in some Tomcat version. Check this link [1]. [1] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6419958 -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (400, 'testing'), (300, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-k7 Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Versions of packages tomcat5 depends on: ii adduser 3.63 Add and remove users and groups ii apache2-common2.0.54-5 next generation, scalable, extenda ii apache2-utils [apache-uti 2.0.54-5 utility programs for webservers ii libtomcat5-java 5.0.30-9 Java Servlet engine -- core librar ii sun-j2sdk1.5 [java2-runti 1.5.0+update06 Java(TM) 2 SDK, Standard Edition, -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#358575: #358575 and sarge
* Lionel Elie Mamane ([EMAIL PROTECTED]) [060525 16:58]: On Wed, May 24, 2006 at 07:22:11PM +0100, Sam Morris wrote: Will you consider fixing this in Sarge also? I have submitted an update to sarge in early April. It will be reviewed by the stable release managers and (I hope) part of the next sarge point release. It seems I submitted it too late for inclusion in 3.1r2. It was basically just after the freeze for sarge r2. We will consider it for r3 (as soon as we are technicaly able to :). Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368645: CVE-2006-2313, CVE-2006-2314: encoding conflicts
Martin Pitt wrote: Hi Florian, hi security team, hi everyone else, just for the record, sid has updated packages already. I'm 70% into completing the security update for sarge. However, due to the nature of the vulns, the patches are enormous, and thus require meticulous porting and testing. Unfortunately I will be away from now until Sunday. I hope to have fixed packages ready on Sunday. I will report back when I'm done. Oh dear! Thanks a lot. Regards, Joey Given enough thrust pigs will fly, but it's not necessarily a good idea. 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]
Bug#366343: close #366343?
Can i close #366343 this bug now or maybe you want to wait for 0.12 release? Regards, Gonéri pgpYOqD6WQbEq.pgp Description: PGP signature
Bug#358493: Deleting tagcoll builds on escher.debian.org
Hello Falk, now that the new tagcoll is uploaded, I don't need the intermediate build results on the sid dchroot on escher. Since they are occupying more than 800Mb I'd like to delete them, unless you planned to do some investigation on them. Please let me know soon. If I won't hear anything within a week, I'll go on and clean my dchroot. Ciao, Enrico -- GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#368883: qt4-x11: FTBFS on alpha
Package: qt4-x11 Version: 4.1.2-2 Severity: serious Justification: no longer builds from source gcc ICEd when attempting to build qt4-x11 on alpha on 2006-05-14. I don't know what's the issue and what could fix. However, 4.1.2-1 built and the changes to -2 seem minimal, so it should be easy to check whether there was a gcc regression or the qt4-x11 changes triggered the FTBFS and need a workaround. qt4-x11 needs an update for X11R7 to reach testing, and I heard that transition was planned for soon (possibly under 1 week). So, until this bug is fixed, either it will a blocker, or 4.1.2-1 will be pushed on alpha (which looks better, *if* doing that is possible). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368113: marked as done (does not remove /var/lib/preload on purge)
Your message dated Thu, 25 May 2006 10:02:14 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#368113: fixed in preload 0.2-7 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) ---BeginMessage--- Package: preload Version: 0.2-6 Severity: serious preload does not remove /var/lib/preload (and the state file in there) on purge. It probably should clean up after itself. Peter ---End Message--- ---BeginMessage--- Source: preload Source-Version: 0.2-7 We believe that the bug you reported is fixed in the latest version of preload, which is due to be installed in the Debian FTP archive: preload_0.2-7.diff.gz to pool/main/p/preload/preload_0.2-7.diff.gz preload_0.2-7.dsc to pool/main/p/preload/preload_0.2-7.dsc preload_0.2-7_i386.deb to pool/main/p/preload/preload_0.2-7_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. Kari Pahula [EMAIL PROTECTED] (supplier of updated preload 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, 25 May 2006 02:10:56 +0300 Source: preload Binary: preload Architecture: source i386 Version: 0.2-7 Distribution: unstable Urgency: low Maintainer: Kari Pahula [EMAIL PROTECTED] Changed-By: Kari Pahula [EMAIL PROTECTED] Description: preload- adaptive readahead daemon Closes: 368113 368115 Changes: preload (0.2-7) unstable; urgency=low . * Fail successfully with a warning if daemon is already running on init.d start or stopped on init.d stop. (Closes: #368113) * Remove /var/lib/preload/ in postrm purge. (Closes: #368115) Files: 4f605b51e9d220a1e19ee31b1047fca5 569 misc optional preload_0.2-7.dsc 5200b6d713fa1f683f28028220f496cf 5039 misc optional preload_0.2-7.diff.gz 51b3f9a950a51640eb442c6ef9267982 33554 misc optional preload_0.2-7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEdeJveYl9593Atw0RArZsAJ9NhJtQb6ftRkNguxDg4wDTWZ+y5ACfZsp8 t2bo3Q9eX/RtTyo+qjEm4jY= =2Iuf -END PGP SIGNATURE- ---End Message---
Bug#361995: marked as done (evolution: Creating new address book creates only an alias, but deleting deletes the original folder)
Your message dated Thu, 25 May 2006 10:32:11 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#361995: fixed in evolution 2.6.1-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) ---BeginMessage--- Package: evolution Version: 2.4.2.1-2 Severity: critical Justification: causes serious data loss X-Debbugs-Cc: [EMAIL PROTECTED] When I create a new address book, this only creates an alias to an exisiting one (the last in the list of those available - but tried only once). Deleting this new (alias) addressbook, however, does also delete the real data behind it. Trying to access the original folder result in the following error message: We were unable to open this addressbook. Please check that the path my-home/.evolution/addressbook/local exists and that you have permission to access it. Steps to reproduce: new - addressbook delete the new addressbook the content of the aliased folder will be lost Best regads Ben -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.6 Locale: LANG=en_GB.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Versions of packages evolution depends on: ii evolution-data-serve 1.4.2.1-2 evolution database backend server ii gconf2 2.14.0-1GNOME configuration database syste ii gnome-icon-theme 2.8.0-4 GNOME Desktop icon theme ii gtkhtml3.8 3.8.1-1.1 HTML rendering/editing library - b ii libart-2.0-2 2.3.17-1Library of functions for 2D graphi ii libatk1.0-0 1.10.1-2The ATK accessibility toolkit ii libaudiofile00.2.6-6 Open-source version of SGI's audio ii libavahi-client3 0.6.4-2 Avahi client library ii libavahi-common3 0.6.9-6 Avahi common library ii libavahi-compat-howl 0.6.9-6 Avahi Howl compatibility library ii libavahi-glib1 0.6.9-6 Avahi glib integration library ii libbonobo2-0 2.14.0-1Bonobo CORBA interfaces library ii libbonoboui2-0 2.8.1-2 The Bonobo UI library ii libc62.3.6-4 GNU C Library: Shared libraries an ii libcairo21.0.2-3 The Cairo 2D vector graphics libra ii libcamel1.2-61.4.2.1-1 The Evolution MIME message handlin ii libcomerr2 1.37-2 common error description library ii libdb4.2 4.2.52-18 Berkeley v4.2 Database Libraries [ ii libdbus-1-2 0.61-5 simple interprocess messaging syst ii libebook1.2-51.4.2.1-1 Client library for evolution addre ii libecal1.2-3 1.4.2.1-1 Client library for evolution calen ii libedataserver1.2-4 1.4.2.1-1 Utility library for evolution data ii libedataserverui1.2- 1.4.2.1-1 GUI utility library for evolution ii libesd-alsa0 [libesd 0.2.35-2Enlightened Sound Daemon (ALSA) - ii libfontconfig1 2.3.1-2 generic font configuration library ii libfreetype6 2.1.10-1FreeType 2 font engine, shared lib ii libgail-common 1.8.3-1 GNOME Accessibility Implementation ii libgail171.8.3-1 GNOME Accessibility Implementation ii libgconf2-4 2.14.0-1GNOME configuration database syste ii libgcrypt11 1.2.2-1 LGPL Crypto library - runtime libr ii libglade2-0 1:2.5.1-2 library to load .glade files at ru ii libglib2.0-0 2.10.1-2The GLib library of C routines ii libgnome-keyring00.4.3-1 GNOME keyring services library ii libgnome-pilot2 2.0.12-1.2 Support libraries for gnome-pilot ii libgnome2-0 2.8.1-2 The GNOME 2 library - runtime file ii libgnomecanvas2-02.12.0-1A powerful object-oriented display ii libgnomeprint2.2-0 2.12.1-2The GNOME 2.2 print architecture - ii libgnomeprintui2.2-0 2.12.1-1GNOME 2.2 print architecture User ii libgnomeui-0 2.8.1-3 The GNOME 2 libraries (User Interf ii libgnomevfs2-0 2.14.0-1GNOME virtual file-system (runtime ii libgnutls11 1.0.16-14 GNU TLS library - runtime library ii libgpg-error01.2-1
Bug#353881: marked as done (evolution: Cannot remove task lists plus existing lists do not function)
Your message dated Thu, 25 May 2006 10:32:11 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#361995: fixed in evolution 2.6.1-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) ---BeginMessage--- Package: evolution Version: 2.4.2.1-1 Severity: normal I have created three task lists in the task manager: two with some previous version of Evolution, one just now. The lists are now: Local Computer Personal list1 list2 list3 The lists list1-list3 cannot be removed. The option exists in the context menu but nothing happens when selected. In addition, for a task only the lists Personal and list1 can be selected: list2 and list3 exist in the task list selection and seem to be selectable but when selected result in list1. In addition, the task seems to exist in all three lists at the same time: when all of these are selected as shown, the same task is seen three times, each with different colors according to the task lists list1--list3. I have removed (apt-get remove --purge evolution) and reinstalled evolution and removed all the data files for it in my home directory (both .evolutio and under .gconf) but the phenomenon persists - as do the lists, wherever they exist. Shouldn't all data be stored in one place? Harri K. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Versions of packages evolution depends on: ii evolution-dat 1.4.2.1-1 evolution database backend server ii gconf22.12.1-9 GNOME configuration database syste ii gnome-icon-th 2.12.1-2 GNOME Desktop icon theme ii gtkhtml3.83.8.1-1HTML rendering/editing library - b ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libatk1.0-0 1.10.3-1 The ATK accessibility toolkit ii libaudiofile0 0.2.6-6Open-source version of SGI's audio ii libbonobo2-0 2.10.1-1 Bonobo CORBA interfaces library ii libbonoboui2- 2.10.1-2 The Bonobo UI library ii libc6 2.3.5-13 GNU C Library: Shared libraries an ii libcairo2 1.0.2-3The Cairo 2D vector graphics libra ii libcamel1.2-6 1.4.2.1-1 The Evolution MIME message handlin ii libcomerr21.38+1.39-WIP-2005.12.31-1 common error description library ii libcompfaceg1 1:1.5.2-3 Compress/decompress images for mai ii libdb4.2 4.2.52-23 Berkeley v4.2 Database Libraries [ ii libebook1.2-5 1.4.2.1-1 Client library for evolution addre ii libecal1.2-3 1.4.2.1-1 Client library for evolution calen ii libedataserve 1.4.2.1-1 Utility library for evolution data ii libedataserve 1.4.2.1-1 GUI utility library for evolution ii libesd-alsa0 0.2.36-3 Enlightened Sound Daemon (ALSA) - ii libfontconfig 2.3.2-1.1 generic font configuration library ii libfreetype6 2.1.7-2.4 FreeType 2 font engine, shared lib ii libgail-commo 1.8.8-1GNOME Accessibility Implementation ii libgail17 1.8.8-1GNOME Accessibility Implementation ii libgconf2-4 2.12.1-9 GNOME configuration database syste ii libgcrypt11 1.2.2-1LGPL Crypto library - runtime libr ii libglade2-0 1:2.5.1-2 library to load .glade files at ru ii libglib2.0-0 2.8.6-1The GLib library of C routines ii libgnome-keyr 0.4.6-2GNOME keyring services library ii libgnome-pilo 2.0.12-1.4 Support libraries for gnome-pilot ii libgnome2-0 2.12.0.1-5 The GNOME 2 library - runtime file ii libgnomecanva 2.12.0-2 A powerful object-oriented display ii libgnomeprint 2.12.1-3 The GNOME 2.2 print architecture - ii libgnomeprint 2.12.1-2 GNOME 2.2 print architecture User ii libgnomeui-0 2.10.1-1 The GNOME 2 libraries (User Interf ii libgnomevfs2- 2.12.2-5 GNOME virtual file-system (runtime ii libgnutls11 1.0.16-14 GNU TLS library - runtime library ii
Bug#368876: contains /usr/X11R6/bin - conflicts with x11-common
Package: ppxp Version: 0.2001080415-14 Severity: grave Hello, this contains /usr/X11R6 /usr/X11R6/bin so this happends: Unpacking replacement x11-common ... dpkg: error processing /var/cache/apt/archives/x11-common_1%3a7.0.20_i386.deb (--unpack): trying to overwrite `/usr/X11R6/bin', which is also in package ppxp I think this dirs should just remove from the package. greetings, Florian Ludwig -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.16-1-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages ppxp depends on: ii libc6 2.3.6-9GNU C Library: Shared libraries ii libncurses5 5.5-2 Shared libraries for terminal hand ii libreadline5 5.1-7 GNU readline and history libraries ii zlib1g1:1.2.3-11 compression library - runtime ppxp recommends no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#358493: Deleting tagcoll builds on escher.debian.org
Enrico Zini [EMAIL PROTECTED] writes: now that the new tagcoll is uploaded, I don't need the intermediate build results on the sid dchroot on escher. Since they are occupying more than 800Mb I'd like to delete them, unless you planned to do some investigation on them. Please let me know soon. If I won't hear anything within a week, I'll go on and clean my dchroot. Feel free to remove it, I'll look into it on my own machine if I get around to... -- Falk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#360417: marked as done (kernel-patch-bootsplash: Package description refers to missing userland tools package named 'bootsplash')
Your message dated Thu, 25 May 2006 19:52:57 +0200 with message-id [EMAIL PROTECTED] and subject line bootsplash uploaded 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) ---BeginMessage--- Package: kernel-patch-bootsplash Severity: grave Justification: renders package unusable As seen below, the package description refers to a userland package that does not exist, hence making this code essentially useless. The repository mentioned as a workaround in previous bug reports is no longer active. This package needs to be added to the main Debian archine. Regards, Matt Description: Bootsplash enables a graphical boot screen (kernel-patch) The bootsplash patch enables a graphical boot screen similar to that of Windows. Features include: . - Nice graphics (JPEG) - Antialiased text rendering (TrueType) - Animations (MNG) - Progress Bar - Diaplay of boot messages above or below a graphic. - Fully themeable . This package contains only the bootsplash kernel patch, you may need the userland tools in the bootsplash package to enable all features (such as a progress bar). . The patch should work for kernels 2.4.18, 2.4.20 - 2.4.25, 2.6.0-test9 - 2.6.0-test11, and 2.6.0 - 2.6.4. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) ---End Message--- ---BeginMessage--- Hi, I've just uploaded the bootsplash package along with a theme: http://qa.debian.org/[EMAIL PROTECTED] Closing the bug. Cheers, Free ---End Message---
Bug#358493: Deleting tagcoll builds on escher.debian.org
On Thu, May 25, 2006 at 06:30:54PM +0200, Falk Hueffner wrote: Feel free to remove it, I'll look into it on my own machine if I get around to... Removed. Thanks a lot! Ciao, Enrico -- GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#368101: (no subject)
I see this segfault on debian-amd64/unstable as well. Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368115: marked as done (init.d/preload stop fails when preload is not running)
Your message dated Thu, 25 May 2006 10:02:14 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#368115: fixed in preload 0.2-7 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) ---BeginMessage--- Package: preload Version: 0.2-6 Severity: serious When preload is not running anymore, then running /etc/init.d/preload stop again fails, returning with a non-zero exit code. There's more than one thing wrong here: | galaxy:~# /etc/init.d/preload stop | Stopping preload: preload. | galaxy:~# /etc/init.d/preload stop | Stopping preload: galaxy:~# First, that's just ugly. Secondly, this means that removing/upgrading the package will break, as you try to stop in prerm: | galaxy:~# dpkg --purge preload | (Reading database ... 224414 files and directories currently installed.) | Removing preload ... | Stopping preload: invoke-rc.d: initscript preload, action stop failed. | dpkg: error processing preload (--purge): | subprocess pre-removal script returned error exit status 1 | Starting preload: preload. | Errors were encountered while processing: | preload Saying something like 'FAILED (not running)' when it's not running, and then exiting with 0 would probably work. (The script exists because it runs with set -e and you call start-stop-daemon without --oknodo, which will make it exit with a non-zero status when it can't stop anything, thereby exiting the script). Peter ---End Message--- ---BeginMessage--- Source: preload Source-Version: 0.2-7 We believe that the bug you reported is fixed in the latest version of preload, which is due to be installed in the Debian FTP archive: preload_0.2-7.diff.gz to pool/main/p/preload/preload_0.2-7.diff.gz preload_0.2-7.dsc to pool/main/p/preload/preload_0.2-7.dsc preload_0.2-7_i386.deb to pool/main/p/preload/preload_0.2-7_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. Kari Pahula [EMAIL PROTECTED] (supplier of updated preload 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, 25 May 2006 02:10:56 +0300 Source: preload Binary: preload Architecture: source i386 Version: 0.2-7 Distribution: unstable Urgency: low Maintainer: Kari Pahula [EMAIL PROTECTED] Changed-By: Kari Pahula [EMAIL PROTECTED] Description: preload- adaptive readahead daemon Closes: 368113 368115 Changes: preload (0.2-7) unstable; urgency=low . * Fail successfully with a warning if daemon is already running on init.d start or stopped on init.d stop. (Closes: #368113) * Remove /var/lib/preload/ in postrm purge. (Closes: #368115) Files: 4f605b51e9d220a1e19ee31b1047fca5 569 misc optional preload_0.2-7.dsc 5200b6d713fa1f683f28028220f496cf 5039 misc optional preload_0.2-7.diff.gz 51b3f9a950a51640eb442c6ef9267982 33554 misc optional preload_0.2-7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEdeJveYl9593Atw0RArZsAJ9NhJtQb6ftRkNguxDg4wDTWZ+y5ACfZsp8 t2bo3Q9eX/RtTyo+qjEm4jY= =2Iuf -END PGP SIGNATURE- ---End Message---
Bug#368101: fte segfault: downgrade to stable's 0.50.0-1.1 works
I've also got the segfault (i386). I downgraded to version 0.50.0-1.1 from stable, which moved back to slang1 (and removed jed). This version does not have the segfault. -- There are books on Win32, so we are as open as you need. -- attributed to Bill Gates +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ Noel Maddy [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368886: spe startup process crash
Subject: spe startup process crash Package: spe Version: 0.8.2a+repack-0.1 Severity: grave Justification: renders package unusable *** Please type your report below this line *** Hi, spe is great but seems to not to be usable on an up-to-date sid. apt-get install spe. spe startup process crashes : If you experience any problems please install wxPython v2.6.1.0. SPE v0.8.2.a (c)2003-2005 www.stani.be If spe fails to start: - type python SPE.py --debug debug.txt 21 at the command prompt (or if you use tcsh: python SPE.py --debug debug.txt) - send debug.txt with some info to spe.stani.be[at]gmail.com Encrypted debugging disabled. If you prefer encrypted debugging, install the Python Cryptography Toolkit from http://www.amk.ca/python/code/crypto Launching application... (python:1695): Gdk-CRITICAL **: gdk_draw_drawable: assertion `src != NULL' failed and it looks like it has entered into an infinite loop. No spe window appears. It looks like one missing dependency. Xavier -- System Information:
Bug#368883: qt4-x11: FTBFS on alpha
Filipus Klutiero [EMAIL PROTECTED] writes: gcc ICEd when attempting to build qt4-x11 on alpha on 2006-05-14. I don't know what's the issue and what could fix. However, 4.1.2-1 built and the changes to -2 seem minimal, so it should be easy to check whether there was a gcc regression or the qt4-x11 changes triggered the FTBFS and need a workaround. Isn't an ICE always a compiler bug? In any case, nothing in the Qt code changed between -1 and -2, so it's certainly a GCC regression. -- Captain Logic is not steering this tugboat. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366816: CVE-2006-2542
This bug is also known as CVE-2006-2542. Please mention this in the changelog. A more suitable patch to fix this problem imho is the attached one. Regards, Joey -- Given enough thrust pigs will fly, but it's not necessarily a good idea. Please always Cc to me when replying to me on the lists. diff -u xmcd-2.6/libdi_d/config.sh xmcd-2.6/libdi_d/config.sh --- xmcd-2.6/libdi_d/config.sh +++ xmcd-2.6/libdi_d/config.sh @@ -46,9 +46,9 @@ SCRDIR=$XMCDLIB/scripts SITES=$CFGDIR/sites TBLDIR=$XMCDLIB/tbl -OWNER=bin -GROUP=bin -CDIRPERM=777 +OWNER=root +GROUP=audio +CDIRPERM=03775 DFLT_CGIPATH='/~cddb/cddb.cgi' CDDBCATS=rock jazz blues newage classical reggae folk country soundtrack misc data BROWSERS=mozilla netscape Mosaic diff -u xmcd-2.6/debian/changelog xmcd-2.6/debian/changelog --- xmcd-2.6/debian/changelog +++ xmcd-2.6/debian/changelog @@ -1,3 +1,11 @@ +xmcd (2.6-14woody1) oldstable-security; urgency=high + + * Non-maintainer upload by the Security Team + * Fully implemented non-world-writeable directories [libdi_d/config.sh +alias xmcdconfig, CVE-2006-2542] + + -- Martin Schulze [EMAIL PROTECTED] Thu, 25 May 2006 20:32:48 +0200 + xmcd (2.6-14) unstable; urgency=low * last upload of the day - list GPL version of COPYING files shipped
Bug#365282: Please reopen this bug
Hello, I am getting exactly the same symptoms as the original reporter. I am pointing to the ftp.uk.debian.org unstable repositories. Thanks, Noah -- Creativity can be a social contribution, but only in so far as society is free to use the results. - R. Stallman
Bug#368890: mysql-dfsg-4.1: Need to update to new upstream version 4.1.19 to fix security bugs
Package: mysql-dfsg-4.1 Severity: grave Tags: security Justification: user security hole The stable version was updated (4.1.11a-4sarge3) to handle security bugs fixed in upstream version 4.1.19. The testing version should reflect these changes. The best way would be to update to the new upstream version. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.16.13 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368898: Apt: segmentation fault when trying to read package indexes
Package: apt Version: 0.6.44.1 Severity: grave Description: i think this says it all... (making sure previously downloaded packages are not the problem:) moose:/home/coutal# rm /var/lib/apt/lists/* rm: cannot remove `/var/lib/apt/lists/partial': Is a directory moose:/home/coutal# rm /var/lib/apt/lists/partial/* rm: cannot remove `/var/lib/apt/lists/partial/*': No such file or directory moose:/home/coutal# apt-get update Get:1 http://mirror.hamakor.org.il unstable Release.gpg [189B] Get:2 http://mirror.hamakor.org.il unstable Release [38.3kB] Get:3 http://mirror.hamakor.org.il unstable/main Packages [3121kB] Get:4 http://mirror.hamakor.org.il unstable/contrib Packages [49.1kB] Get:5 http://mirror.hamakor.org.il unstable/non-free Packages [65.3kB] Fetched 3274kB in 48s (68.1kB/s) Segmentation faultsts... 0% moose:/home/coutal# from now on, every operation attempted causes a segmentation fault as well. sources.list: deb http://mirror.hamakor.org.il/pub/mirrors/debian/ unstable main contrib non-free the rest of the apt configuration files have not been touched from their defaults. i have checked that the packages file was intact - the md5 signature matched the Release file, and the Release file was properly signed. uname: Linux moose 2.6.16-1-k7 #2 Thu May 4 18:35:10 UTC 2006 i686 GNU/Linux This message was sent using IMP, the Internet Messaging Program.
Bug#368872: libxslt: FTBFS on alpha/MIPS
On Thu, May 25, 2006 at 11:48:02AM -0400, Filipus Klutiero wrote: libxslt FTBFS on alpha/MIPS since over 3 weeks. I have no clue about the causes/fix (please refer to the buildd logs) and am filing in case the maintainers didn't notice the issue yet. This is one of the top 10 stallers according to Bjorn Stenberg's site, stalling [partially] 17 packages directly, including postgresql-8.1 8.1.4-1 (among other issues), which fixes several vulnerabilities. The pairing of alpha/mips/mipsel indicates that the package has a problem building in environments that use sudo as rootcmd. The most likely culprit is relying on $(PWD) to be set in the environment, which is not guaranteed; please use the GNU make variable $(CURDIR) instead. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#156259: marked as done (db4.0: does not build from source)
Your message dated Thu, 25 May 2006 12:36:59 -0700 with message-id [EMAIL PROTECTED] and subject line fixed 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) ---BeginMessage--- Package: db4.0 Version: N/A; reported 2002-08-11 Severity: normal Hi Matthew, When attempting to build db4.0 I get: gcc -c -I. -I../dist/../include -I../dist/../include_auto -D_GNU_SOURCE -D_REENTRANT -O2 -Wall -g ../dist/../mutex/mut_tas.c -fPIC -DPIC -o .libs/mut_tas.lo ../dist/../mutex/mut_tas.c: In function `__db_tas_mutex_init_4000': ../dist/../mutex/mut_tas.c:73: warning: implicit declaration of function `MUTEX_INIT' ../dist/../mutex/mut_tas.c:73: structure has no member named `tas' ../dist/../mutex/mut_tas.c:76: structure has no member named `spins' ../dist/../mutex/mut_tas.c: In function `__db_tas_mutex_lock_4000': ../dist/../mutex/mut_tas.c:105: structure has no member named `spins' ../dist/../mutex/mut_tas.c:109: warning: implicit declaration of function `MUTEX_SET' ../dist/../mutex/mut_tas.c:109: structure has no member named `tas' ../dist/../mutex/mut_tas.c:97: warning: `nspins' might be used uninitialized in this function ../dist/../mutex/mut_tas.c: In function `__db_tas_mutex_unlock_4000': ../dist/../mutex/mut_tas.c:180: warning: implicit declaration of function `MUTEX_UNSET' ../dist/../mutex/mut_tas.c:180: structure has no member named `tas' make[1]: *** [mut_tas.lo] Error 1 make[1]: Leaving directory `/amd/ftoomsh/old.root/cats/wildfire/Debian/progsoc/db4.0-4.0.14/build-tree/db-4.0.14/build_unix' make: *** [stampdir/build-stamp] Error 2 Building from pristine source works. Anand -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux sutekh 2.4.18-586tsc #1 Sun Apr 14 10:57:57 EST 2002 i686 Locale: LANG=C, LC_CTYPE=C ---End Message--- ---BeginMessage--- This bug is fixed. The folks who reported it, and especially the related bug 144165, were so rude about it that I'm not going to provide any more information. Go look it up yourself. -- I've been on the wagon now for more than a decade. Not a single goto in all that time. I just don't need them any more. I don't even use break or continue now, except on social occasions of course. And I don't get carried away. --Richard Heathfield ---End Message---
Bug#368872: [xml/sgml-pkgs] Bug#368872: libxslt: FTBFS on alpha/MIPS
On Thu, May 25, 2006 at 11:48:02AM -0400, Filipus Klutiero [EMAIL PROTECTED] wrote: Package: libxslt Version: 1.1.16-1 Severity: serious Justification: no longer builds from source libxslt FTBFS on alpha/MIPS since over 3 weeks. I have no clue about the causes/fix (please refer to the buildd logs) and am filing in case the maintainers didn't notice the issue yet. I saw that, and i don't see any reason why it'd FTBFS. Trying to build on one of the debian alpha or mips server is on my TODO list. This is one of the top 10 stallers according to Bjorn Stenberg's site, stalling [partially] 17 packages directly, including postgresql-8.1 8.1.4-1 (among other issues), which fixes several vulnerabilities. Well, I should re-prioritize my TODO list... Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368883: qt4-x11: FTBFS on alpha
Brian Nelson a écrit : Isn't an ICE always a compiler bug? Yes, I was just asking if it was a new bug or a pre-existing one. In any case, nothing in the Qt code changed between -1 and -2, so it's certainly a GCC regression. Thanks for the information...I guess that's bad news. It seems there are almost 2 monthes of changes in the gcc 4.0 branch between 4.0.3-1 and 4.0.3-3, so it's quite possible that it's indeed a GCC regression. When looking at the gcc-4.0 bugs reported in Debian's BTS for 4.0.3-1, I can't see much that would explain this. I'm completely clueless about building, but somebody should start by figuring which GCC regression is blocking this. Given the fact that branch 4.0 looks very inactive, maybe the easiest thing would be to identify the changeset which introduced this regression.
Bug#346250: marked as done ((no subject))
Your message dated Thu, 25 May 2006 22:36:00 +0200 with message-id [EMAIL PROTECTED] and subject line your mail 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) ---BeginMessage--- Subject: revelation: don't complete deb configuration Package: revelation Version: 0.4.5-2 Severity: grave Justification: renders package unusable -- 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.15-rc4 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) Versions of packages revelation depends on: ii cracklib2 2.7-18pro-active password checker librar ii gconf2 2.10.1-6 GNOME configuration database syste ii gnome-icon-theme 2.10.1-2 GNOME Desktop icon theme ii libbonoboui2-0 2.10.1-1 The Bonobo UI library ii libglib2.0-0 2.8.4-2 The GLib library of C routines ii libgnomeui-0 2.10.1-1 The GNOME 2 libraries (User Interf ii libgtk2.0-02.8.9-2 The GTK+ graphical user interface ii libpanel-applet2-0 2.10.2-1 library for GNOME 2 panel applets ii python 2.3.5-3 An interactive high-level object-o ii python-crypto 2.0.1+dfsg1-1 cryptographic algorithms and proto ii python-gnome2 2.10.0-4 Python bindings for the GNOME desk ii python-gnome2-extras 2.10.2-1 Python bindings for the GNOME desk ii python-gtk22.6.3-2 Python bindings for the GTK+ widge ii python-xml 0.8.4-1 XML tools for Python [dummy packag ii python2.3-gnome2 2.10.0-4 Python bindings for the GNOME desk ii shared-mime-info 0.16-3FreeDesktop.org shared MIME databa revelation recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- On Fri, Jan 06, 2006 at 05:49:22PM +0100, Andrea Beciani wrote: Subject: revelation: don't complete deb configuration Package: revelation Version: 0.4.5-2 Severity: grave Justification: renders package unusable your bug report is not understandable. You have been asked for more informations already, and gave no answer in more than 3 monthes. I also close the bug. Please reopen it (or submit a new one) with more extensive informations if it's approrpriate. Cheers, -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org signature.asc Description: Digital signature ---End Message---
Bug#368902: underscore.sty non-free as shipped; author relicense available
Package: texlive Version: 2005-1 Severity: serious underscore.sty as shipped in texlive has the following non-free license: % Copyright 1998,2001 Donald Arseneau; Distribute freely if unchanged. However, I wrote to Donald Arseneau and he agreed to relicense this file under the LPPL; including his mail in the debian/copyright file should make underscore.sty distributable in main (and also permit inclusion in tetex as well). I've quoted his mail below. - Josh Triplett Donald Arseneau wrote: Josh Triplett [EMAIL PROTECTED] writes: % Copyright 1998,2001 Donald Arseneau; Distribute freely if unchanged. Would you be willing to license this file under the standard LaTeX Project Public License, or another Free Software license? Yeah. Following that original short permission, I should use the LPPL. signature.asc Description: OpenPGP digital signature
Processed: severity of 368633 is normal
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.20 severity 368633 normal Bug#368633: partman: LVM automatic partitioning not undoable Severity set to `normal' from `critical' 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: Bus error on IA64 when doing gst-inspect decodebin
Processing commands for [EMAIL PROTECTED]: reassign 366953 liboil0.3 Bug#366953: Bus error on IA64 when doing gst-inspect decodebin Bug reassigned from package `gst-plugins-base0.10' to `liboil0.3'. close 366953 0.3.9-1 Bug#366953: Bus error on IA64 when doing gst-inspect decodebin 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 0.3.9-1, send any further explanations to Sebastian Dröge [EMAIL PROTECTED] stop 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: blocking 368905 with 340576
Processing commands for [EMAIL PROTECTED]: package interchange-doc Ignoring bugs not assigned to: interchange-doc block 368905 by 340576 Bug#368905: interchange-doc: Useless without interchange in testing Was not blocked by any bugs. Blocking bugs added: 340576 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#363938: isdnutils-xtools fails to install
On Thu, Apr 20, 2006 at 04:04:55PM -0700, Steve Langasek wrote: On Thu, Apr 20, 2006 at 08:00:35PM +0200, Reinhold Schoeb wrote: Package: isdnutils-xtools Version: 1:3.8.2005-12-06-4 Severity: grave Justification: renders package unusable After the last xorg-Update this package was removed by apt-get and now fails to install. Here is my log : Die folgenden Pakete haben nichterfüllte Abhängigkeiten: isdnutils-xtools: Hängt ab: libice6 soll aber nicht installiert werden This is because x11-common conflicts with this version of isdnutils-xtools, because it installs binaries in /usr/X11R6/bin and /usr/X11R6/bin is going away with Xorg 7. It was actually reasonably appropriate before for isdnutils-xtools to install to /usr/X11R6, because the package does build-depend on xutils; unfortunately, the debian packaging manually moves the binaries from /usr/bin to /usr/X11R6/bin, so a binNMU isn't sufficient to fix this problem... I'm preparing a NMU in delayed/2 for that. patch is attached. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org diff -u isdnutils-3.8.2005-12-06/debian/changelog isdnutils-3.8.2005-12-06/debian/changelog --- isdnutils-3.8.2005-12-06/debian/changelog +++ isdnutils-3.8.2005-12-06/debian/changelog @@ -1,3 +1,11 @@ +isdnutils (1:3.8.2005-12-06-4.1) unstable; urgency=high + + * Non-maintainer upload. + * Install files to /usr/bin instead of /usr/X11R6/bin. Closes: #363938. + * Urgency set to high due to RC Bug fix. + + -- Pierre Habouzit [EMAIL PROTECTED] Thu, 25 May 2006 23:35:07 +0200 + isdnutils (1:3.8.2005-12-06-4) unstable; urgency=low * capi20: Regenerate Makefile.in. Closes: #318808. diff -u isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.files isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.files --- isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.files +++ isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.files @@ -1,2 +1 @@ -usr/X11R6 etc/X11/app-defaults/XISDNLoad diff -u isdnutils-3.8.2005-12-06/debian/finish-install-first.sh isdnutils-3.8.2005-12-06/debian/finish-install-first.sh --- isdnutils-3.8.2005-12-06/debian/finish-install-first.sh +++ isdnutils-3.8.2005-12-06/debian/finish-install-first.sh @@ -7,8 +7,8 @@ rm -f debian/tmp/etc/isdn/eftusers ln -s ../ftpusers debian/isdneurofile/etc/isdn/eftusers install -m 0444 Mini-FAQ/isdn-faq.* debian/isdnutils-doc/usr/share/doc/isdnutils-doc/Mini-FAQ/ - mv debian/tmp/usr/share/man/man1/xisdnload.1* debian/isdnutils-xtools/usr/X11R6/man/man1/ - mv debian/tmp/usr/bin/x* debian/isdnutils-xtools/usr/X11R6/bin/ + mv debian/tmp/usr/share/man/man1/xisdnload.1* debian/isdnutils-xtools/usr/man/man1/ + mv debian/tmp/usr/bin/x* debian/isdnutils-xtools/usr/bin/ cp xmonisdn/README debian/isdnutils-xtools/usr/share/doc/isdnutils-xtools/README.xmonisdn # move some extra stuff from upstream source into debian tree cp ipppd/NOTES.IPPPD ipppd/README* debian/README.MPPP debian/ipppd/usr/share/doc/ipppd/ @@ -90,3 +90,3 @@ fi - # in the old situation, the app-defaults are under usr/X11R6 + # in the old situation, the app-defaults are under usr/ # which is moved out to the package anyway, so no need to add it to .files diff -u isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.dirs isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.dirs --- isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.dirs +++ isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.dirs @@ -1,5 +1,4 @@ etc/isdn -usr/X11R6/bin -usr/X11R6/man/man1 +usr/man/man1 usr/lib/menu usr/share/doc/isdnutils-xtools diff -u isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.menu isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.menu --- isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.menu +++ isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.menu @@ -2,10 +2,10 @@ section=Apps/Net\ title=X11 ISDN Monitor\ - command=/usr/X11R6/bin/xmonisdn\ + command=/usr/bin/xmonisdn\ description=xmonisdn is an xbiff-like display of the state of the ISDN line. ?package(isdnutils-xtools):needs=X11\ section=Apps/Net\ title=X11 ISDN Load\ - command=/usr/X11R6/bin/xisdnload\ + command=/usr/bin/xisdnload\ description=xisdnload shows a graphical display of the throughput, and the\ background colour tells you whether there is a connection. signature.asc Description: Digital signature
Bug#368911: prelude-manager: Broken depend on libpreludedb0
Package: prelude-manager Severity: grave Justification: renders package unusable The package libpreludedb0 doesn't seem available and is needed in order to install the package prelude-manager. Regards. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.18-bf2.4 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- Cedric Foll Ingénieur Sécurité Réseaux Division Informatique, Rectorat de Rouen If you think technology can solve your security problems, then you don't understand the problems and you don't understand the technology. Bruce Schneier
Bug#368902: [Pkg-texlive-maint] Bug#368902: underscore.sty non-free as shipped; author relicense available
Hi Josh! Thanks for reporting this. We (=tetex and texlive maintainers in Debian) are currently evaluation all files, checking for licenses etc. This is a tedious process and will take - well let's hope not ages, but long time. The problem with TeX especially that many of the input files are 10+ years old, when licensing was not an issue at all. On Don, 25 Mai 2006, Josh Triplett wrote: Package: texlive Version: 2005-1 Severity: serious underscore.sty as shipped in texlive has the following non-free license: % Copyright 1998,2001 Donald Arseneau; Distribute freely if unchanged. However, I wrote to Donald Arseneau and he agreed to relicense this file under the LPPL; including his mail in the debian/copyright file should make underscore.sty distributable in main (and also permit inclusion in tetex as well). I've quoted his mail below. - Josh Triplett Donald Arseneau wrote: Josh Triplett [EMAIL PROTECTED] writes: % Copyright 1998,2001 Donald Arseneau; Distribute freely if unchanged. Would you be willing to license this file under the standard LaTeX Project Public License, or another Free Software license? Yeah. Following that original short permission, I should use the LPPL. I will keep this in mind, but we are only now starting with creating the necessary infrastructure, ie checking all files via the TeX Catalogue entries of the licenses, and verifying the licenses. Best wishes Norbert --- Dr. Norbert Preining preining AT logic DOT at Università di Siena gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- Ford had his own code of ethics. It wasn't much of one, but it was his and he stuck by it, more or less. One rule he made was never to buy his own drinks. He wasn't sure if that counted as an ethic, but you have to go with what you've got. --- Douglas Adams, The Hitchhikers Guide to the Galaxy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368890: marked as done (mysql-dfsg-4.1: Need to update to new upstream version 4.1.19 to fix security bugs)
Your message dated Thu, 25 May 2006 17:57:38 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#368890: mysql-dfsg-4.1: Need to update to new upstream version 4.1.19 to fix security bugs 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) ---BeginMessage--- Package: mysql-dfsg-4.1 Severity: grave Tags: security Justification: user security hole The stable version was updated (4.1.11a-4sarge3) to handle security bugs fixed in upstream version 4.1.19. The testing version should reflect these changes. The best way would be to update to the new upstream version. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.16.13 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) ---End Message--- ---BeginMessage--- hi harry, On Thu, May 25, 2006 at 11:59:28AM -0700, Harry Edmon wrote: The stable version was updated (4.1.11a-4sarge3) to handle security bugs fixed in upstream version 4.1.19. The testing version should reflect these changes. The best way would be to update to the new upstream version. the bug is fixed in unstable as well, and will naturally propagate to testing as part of the automated archive process. in fact, filing a critical bug will prevent this from happening (packages with critical bugs do not automatically migrate to testing), so i'm going to close the bug. if you need the fix in the meantime, you should pull it in from unstable. christian: feel free to publically refute me if you believe we should leave this open and talk to the testing-security folks :) sean -- signature.asc Description: Digital signature ---End Message---
Bug#367986: Acknowledgement (sylpheed-gtk1: ..moving mail between folders within Sg1-1.0.6, crashes X.)
On Wed, May 24, 2006 at 08:11:09PM -0700, Steve Langasek wrote: On Thu, May 25, 2006 at 04:17:02AM +0200, Arnt Karlsen wrote: ..could it be a font thing? These crashes started after the font I had set up for Sylpheed-gtk1, disappeared off this box, everything else works like it should, AFAICT. Uh, it could be tied somehow to the fonts, but I don't see any way to debug it on that basis alone as I can't imagine any way that would cause an X server to crash *or* cause an app to chew up memory. GTK2 app maybe, but GTK1 was all about core (i.e. server-side) fonts, so I don't see how that could occur. signature.asc Description: Digital signature
Bug#368633: partman: LVM automatic partitioning not undoable
I've temporarily reworded the partman-auto template to not claim that actions can be undone, but it would be nice if p-a-l could be fixed to act like the rest of partman and confirm before touching disk. If that change is made, the partman-auto template can be reverted to the old wording. In the meantime, this bug isn't critical anymore, so downgrading. -- see shy jo signature.asc Description: Digital signature
Bug#368883: qt4-x11: FTBFS on alpha
Le Jeu 25 Mai 2006 22:30, Filipus Klutiero a écrit : Brian Nelson a écrit : Isn't an ICE always a compiler bug? Yes, I was just asking if it was a new bug or a pre-existing one. In any case, nothing in the Qt code changed between -1 and -2, so it's certainly a GCC regression. Thanks for the information...I guess that's bad news. It seems there are almost 2 monthes of changes in the gcc 4.0 branch between 4.0.3-1 and 4.0.3-3, so it's quite possible that it's indeed a GCC regression. When looking at the gcc-4.0 bugs reported in Debian's BTS for 4.0.3-1, I can't see much that would explain this. I'm completely clueless about building, but somebody should start by figuring which GCC regression is blocking this. Given the fact that branch 4.0 looks very inactive, maybe the easiest thing would be to identify the changeset which introduced this regression. one can also try to compile it with gcc 4.1 -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpgodT8j8Pjf.pgp Description: PGP signature
Bug#366953: Bus error on IA64 when doing gst-inspect decodebin
reassign 366953 liboil0.3 close 366953 0.3.9-1 stop On Fri, May 12, 2006, Sebastian Dröge wrote: currently banshee FTBFS on IA64 because of a bus error when trying to do gst-inspect decodebin: checking for GStreamer 0.10 decodebin plugin... /build/buildd/banshee-0.10.10/./configure: line 23193: 28319 Bus error $gst_inspect $element /dev/null 2/dev/null Thanks, I believe this was fixed in liboil0.3 0.3.9-1. Bye, -- Loïc Minier [EMAIL PROTECTED] You can gtk_main_run, but you can't gtk_widget_hide. --danw, 19-jul-04
Processed: [bts-link] source package koffice
Processing commands for [EMAIL PROTECTED]: # # bts-link upstream status pull for source package koffice # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). # remote status report for #354804 # * http://bugs.kde.org/show_bug.cgi?id=127992 # * remote status changed: (?) - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 354804 + fixed-upstream Bug#354804: krita: TIFF and PNG exports don't work with a CMYK image There were no tags set. Tags added: fixed-upstream usertags 354804 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: resolution-FIXED status-RESOLVED. # remote status report for #366679 # * http://bugs.kde.org/show_bug.cgi?id=127994 # * remote status changed: (?) - NEW usertags 366679 + status-NEW There were no usertags set. Usertags are now: status-NEW. # remote status report for #367059 # * http://bugs.kde.org/show_bug.cgi?id=125944 forwarded 367059 http://bugs.kde.org/127296, merged-upstream: http://bugs.kde.org/show_bug.cgi?id=125944 Bug#367059: krita: renders colors incorrectly on ppc Forwarded-to-address changed from http://bugs.kde.org/127296 to http://bugs.kde.org/127296, merged-upstream: http://bugs.kde.org/show_bug.cgi?id=125944. 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#368905: interchange-doc: Useless without interchange in testing
Package: interchange-doc Version: 5.2.0-1 Severity: serious This package is useless without interchange. Since interchange is not in testing (and will not be until after grave bug #340576 is fixed) I am filing this bug to keep interchange-doc out of testing as well. See http://lists.debian.org/debian-qa/2006/05/msg00026.html http://lists.debian.org/debian-release/2006/05/msg00198.html http://lists.debian.org/debian-release/2006/05/msg00200.html -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-3-k7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) regards, -- Kevin B. McCarty [EMAIL PROTECTED] Physics Department WWW: http://www.princeton.edu/~kmccarty/Princeton University GPG: public key ID 4F83C751 Princeton, NJ 08544 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368917: lbdb: does not work with coreutils 5.96-1 (sort: open failed: +1: No such file or directory)
Package: lbdb Version: 0.31.1 Severity: serious Hello, lbdb is broken with coreutils 5.96-1 (works fine with 5.94-1): % lbdbq foo sort: open failed: +1: No such file or directory lbdbq: no matches I'm don't know why the +1 was accepted in previous sort versions, and whether this bug belongs to coreutils instead. Thanks, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org A lie can go round the world before the truth has got its boots on. -- Terry Pratchett -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367986: Acknowledgement (sylpheed-gtk1: ..moving mail between folders within Sg1-1.0.6, crashes X.)
On Fri, 26 May 2006 00:16:54 +0300, Daniel wrote in message [EMAIL PROTECTED]: On Wed, May 24, 2006 at 08:11:09PM -0700, Steve Langasek wrote: On Thu, May 25, 2006 at 04:17:02AM +0200, Arnt Karlsen wrote: ..could it be a font thing? These crashes started after the font I had set up for Sylpheed-gtk1, disappeared off this box, everything else works like it should, AFAICT. Uh, it could be tied somehow to the fonts, but I don't see any way to debug it on that basis alone as I can't imagine any way that would cause an X server to crash *or* cause an app to chew up memory. GTK2 app maybe, but GTK1 was all about core (i.e. server-side) fonts, so I don't see how that could occur. ..ok, any kinda stunt I can try to help you guys find out? -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353997: marked as done (libmyodbc: create packages for libmysqlclient14 and libmysqlclient15)
Your message dated Thu, 25 May 2006 15:32:22 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#353997: fixed in myodbc 3.51.11-6 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) ---BeginMessage--- Package: libmyodbc Version: 3.51.11-5 Severity: important libmyodbc depends on libmysqlclient12. This version is too old for some purposes. For example when connecting with DataArchitect from thekompany (a commercial database modelling application) to a mysql4.1 database, an error occurs, saying that the mysql client version is too old for the used authentication mechanism: Client does not support authentication protocol requested by server; consider upgrading MySQL client I've compiled libmyodbc using libmysqlclient14 instead of libmysqlclient12 and now this error is gone. So there are should be packages for libmysqlclient14 and libmysqlclient15, too. Maybe it would be enough to depend on _any_ version of libmysqlclient (then there should be a meta-package of libmysqlclient), but I do not know whether this would lead to other incompatibilities. However, in the current situation the only available libmyodbc package is not usable with the mysql4.1 package available in Debian. Marco -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-k7 Locale: LANG=POSIX, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages libmyodbc depends on: ii debconf [debconf-2.0]1.4.70 Debian configuration management sy ii libc62.3.5-13GNU C Library: Shared libraries an ii libltdl3 1.5.22-2A system independent dlopen wrappe ii libmysqlclient12 4.0.24-10sarge1 mysql database client library ii odbcinst1debian1 2.2.11-9Support library and helper program ii zlib1g 1:1.2.3-9 compression library - runtime Versions of packages libmyodbc recommends: ii libiodbc2 3.52.4-2 iODBC Driver Manager ii unixodbc 2.2.11-9 ODBC tools libraries -- debconf information: * libmyodbc/addtoodbc: true ---End Message--- ---BeginMessage--- Source: myodbc Source-Version: 3.51.11-6 We believe that the bug you reported is fixed in the latest version of myodbc, which is due to be installed in the Debian FTP archive: libmyodbc_3.51.11-6_amd64.deb to pool/main/m/myodbc/libmyodbc_3.51.11-6_amd64.deb myodbc_3.51.11-6.diff.gz to pool/main/m/myodbc/myodbc_3.51.11-6.diff.gz myodbc_3.51.11-6.dsc to pool/main/m/myodbc/myodbc_3.51.11-6.dsc 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. Steve Langasek [EMAIL PROTECTED] (supplier of updated myodbc 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, 25 May 2006 15:14:40 -0700 Source: myodbc Binary: libmyodbc Architecture: source amd64 Version: 3.51.11-6 Distribution: unstable Urgency: low Maintainer: Steve Langasek [EMAIL PROTECTED] Changed-By: Steve Langasek [EMAIL PROTECTED] Description: libmyodbc - the MySQL ODBC driver Closes: 331559 353997 Changes: myodbc (3.51.11-6) unstable; urgency=low . * Add Swedish debconf translation, thanks to Daniel Nylander [EMAIL PROTECTED] (closes: #331559). * Rebuild against libmysqlclient15-dev, as libmysqlclient12 no longer exists. Closes: #353997. * Also rebuild against unixodbc-dev (= 2.2.11-13), to pull in a small ABI change on 64-bit archs that's been backported from 2.2.12. This also requires a patch to driver/prepare.c. * No longer specify extra build flags to request a 64-bit-clean ABI; the headers from the unixodbc-dev package have been fixed to always declare this for us. Files: ba1d1681b77ba829736c59a140eaa959 657 libs optional myodbc_3.51.11-6.dsc 86b7d28d5ae2b97fc5b2c1b14c6fb7f5 49571 libs optional myodbc_3.51.11-6.diff.gz b4d390c3723e5de81c937d12854961ba 75132 libs optional libmyodbc_3.51.11-6_amd64.deb -BEGIN PGP SIGNATURE- Version:
Bug#361067: marked as done (libmyodbc depends on unavailable libmysqlclient12)
Your message dated Thu, 25 May 2006 15:32:22 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#353997: fixed in myodbc 3.51.11-6 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) ---BeginMessage--- Package: libmyodbc Severity: grave Justification: renders package unusable The package libmyodbc depends on unavailable package libmysqlclient12. -- 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.15-7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) ---End Message--- ---BeginMessage--- Source: myodbc Source-Version: 3.51.11-6 We believe that the bug you reported is fixed in the latest version of myodbc, which is due to be installed in the Debian FTP archive: libmyodbc_3.51.11-6_amd64.deb to pool/main/m/myodbc/libmyodbc_3.51.11-6_amd64.deb myodbc_3.51.11-6.diff.gz to pool/main/m/myodbc/myodbc_3.51.11-6.diff.gz myodbc_3.51.11-6.dsc to pool/main/m/myodbc/myodbc_3.51.11-6.dsc 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. Steve Langasek [EMAIL PROTECTED] (supplier of updated myodbc 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, 25 May 2006 15:14:40 -0700 Source: myodbc Binary: libmyodbc Architecture: source amd64 Version: 3.51.11-6 Distribution: unstable Urgency: low Maintainer: Steve Langasek [EMAIL PROTECTED] Changed-By: Steve Langasek [EMAIL PROTECTED] Description: libmyodbc - the MySQL ODBC driver Closes: 331559 353997 Changes: myodbc (3.51.11-6) unstable; urgency=low . * Add Swedish debconf translation, thanks to Daniel Nylander [EMAIL PROTECTED] (closes: #331559). * Rebuild against libmysqlclient15-dev, as libmysqlclient12 no longer exists. Closes: #353997. * Also rebuild against unixodbc-dev (= 2.2.11-13), to pull in a small ABI change on 64-bit archs that's been backported from 2.2.12. This also requires a patch to driver/prepare.c. * No longer specify extra build flags to request a 64-bit-clean ABI; the headers from the unixodbc-dev package have been fixed to always declare this for us. Files: ba1d1681b77ba829736c59a140eaa959 657 libs optional myodbc_3.51.11-6.dsc 86b7d28d5ae2b97fc5b2c1b14c6fb7f5 49571 libs optional myodbc_3.51.11-6.diff.gz b4d390c3723e5de81c937d12854961ba 75132 libs optional libmyodbc_3.51.11-6_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEdi1ZKN6ufymYLloRAoPXAKCGVADFhdZyQZpAoFAPOhqCFnZAqwCgsmxb 72aKpcxzSPuIXxRKyG0sXcU= =hjGx -END PGP SIGNATURE- ---End Message---
Bug#363938: isdnutils-xtools fails to install
tag 363938 + patch thanks On Thu, Apr 20, 2006 at 04:04:55PM -0700, Steve Langasek wrote: On Thu, Apr 20, 2006 at 08:00:35PM +0200, Reinhold Schoeb wrote: Package: isdnutils-xtools Version: 1:3.8.2005-12-06-4 Severity: grave Justification: renders package unusable After the last xorg-Update this package was removed by apt-get and now fails to install. Here is my log : Die folgenden Pakete haben nichterfüllte Abhängigkeiten: isdnutils-xtools: Hängt ab: libice6 soll aber nicht installiert werden This is because x11-common conflicts with this version of isdnutils-xtools, because it installs binaries in /usr/X11R6/bin and /usr/X11R6/bin is going away with Xorg 7. It was actually reasonably appropriate before for isdnutils-xtools to install to /usr/X11R6, because the package does build-depend on xutils; unfortunately, the debian packaging manually moves the binaries from /usr/bin to /usr/X11R6/bin, so a binNMU isn't sufficient to fix this problem... sorry I sent the wrong patch. here is the one. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org diff -u isdnutils-3.8.2005-12-06/debian/changelog isdnutils-3.8.2005-12-06/debian/changelog --- isdnutils-3.8.2005-12-06/debian/changelog +++ isdnutils-3.8.2005-12-06/debian/changelog @@ -1,3 +1,11 @@ +isdnutils (1:3.8.2005-12-06-4.1) unstable; urgency=high + + * Non-maintainer upload. + * Install files to /usr/bin instead of /usr/X11R6/bin. Closes: #363938. + * Urgency set to high due to RC Bug fix. + + -- Pierre Habouzit [EMAIL PROTECTED] Thu, 25 May 2006 23:35:07 +0200 + isdnutils (1:3.8.2005-12-06-4) unstable; urgency=low * capi20: Regenerate Makefile.in. Closes: #318808. diff -u isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.files isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.files --- isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.files +++ isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.files @@ -1,2 +1,2 @@ -usr/X11R6 +usr/bin/x* etc/X11/app-defaults/XISDNLoad diff -u isdnutils-3.8.2005-12-06/debian/finish-install-first.sh isdnutils-3.8.2005-12-06/debian/finish-install-first.sh --- isdnutils-3.8.2005-12-06/debian/finish-install-first.sh +++ isdnutils-3.8.2005-12-06/debian/finish-install-first.sh @@ -7,8 +7,8 @@ rm -f debian/tmp/etc/isdn/eftusers ln -s ../ftpusers debian/isdneurofile/etc/isdn/eftusers install -m 0444 Mini-FAQ/isdn-faq.* debian/isdnutils-doc/usr/share/doc/isdnutils-doc/Mini-FAQ/ - mv debian/tmp/usr/share/man/man1/xisdnload.1* debian/isdnutils-xtools/usr/X11R6/man/man1/ - mv debian/tmp/usr/bin/x* debian/isdnutils-xtools/usr/X11R6/bin/ + mv debian/tmp/usr/share/man/man1/xisdnload.1* debian/isdnutils-xtools/usr/man/man1/ + mv debian/tmp/usr/bin/x* debian/isdnutils-xtools/usr/bin/ cp xmonisdn/README debian/isdnutils-xtools/usr/share/doc/isdnutils-xtools/README.xmonisdn # move some extra stuff from upstream source into debian tree cp ipppd/NOTES.IPPPD ipppd/README* debian/README.MPPP debian/ipppd/usr/share/doc/ipppd/ diff -u isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.dirs isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.dirs --- isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.dirs +++ isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.dirs @@ -1,5 +1,5 @@ etc/isdn -usr/X11R6/bin -usr/X11R6/man/man1 +usr/bin +usr/man/man1 usr/lib/menu usr/share/doc/isdnutils-xtools diff -u isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.menu isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.menu --- isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.menu +++ isdnutils-3.8.2005-12-06/debian/isdnutils-xtools.menu @@ -2,10 +2,10 @@ section=Apps/Net\ title=X11 ISDN Monitor\ - command=/usr/X11R6/bin/xmonisdn\ + command=/usr/bin/xmonisdn\ description=xmonisdn is an xbiff-like display of the state of the ISDN line. ?package(isdnutils-xtools):needs=X11\ section=Apps/Net\ title=X11 ISDN Load\ - command=/usr/X11R6/bin/xisdnload\ + command=/usr/bin/xisdnload\ description=xisdnload shows a graphical display of the throughput, and the\ background colour tells you whether there is a connection. signature.asc Description: Digital signature
Bug#366034: Regarding MD5 code by RSA Data Security
I think this debian-legal (sub-)thread might be of interest: http://lists.debian.org/debian-legal/2005/02/msg00108.html HTH -- :-( This Universe is buggy! Where's the Creator's BTS? ;-) .. Francesco Poli GnuPG Key ID = DD6DFCF4 Key fingerprint = C979 F34B 27CE 5CD8 DC12 31B5 78F4 279B DD6D FCF4 pgpdbJO2VY2R7.pgp Description: PGP signature
Bug#368929: rkhunter --update doesn't work
Package: rkhunter Version: 1.2.8-4 Severity: grave # rkhunter --update Running updater... /usr/bin/rkhunter: line 4994: /rkhunter/scripts/check_update.sh: No such file or directory Ready. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-3-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages rkhunter depends on: ii debconf [debconf 1.4.30.13 Debian configuration management sy ii file 4.12-1 Determines file type using magic ii mailx1:8.1.2-0.20040524cvs-4 A simple mail user agent ii net-tools1.60-10 The NET-3 networking toolkit ii perl 5.8.4-8sarge4 Larry Wall's Practical Extraction ii wget 1.9.1-12retrieves files from the web -- debconf information: * rkhunter/cron_daily_run: true * rkhunter/cron_db_update: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
