Bug#379479: marked as done (statdataml: FTBFS: Error: package 'XML' could not be loaded)
Your message dated Mon, 31 Jul 2006 23:02:15 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379479: fixed in statdataml 1.0.9-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: statdataml Version: 1.0.9-2 Severity: serious Hello, There was a problem while autobuilding your package: > Automatic build of statdataml_1.0.9-2 on avidan by sbuild/i386 0.49 > Build started at 20060722-0257 > ** ... > /usr/bin/fakeroot debian/rules binary-arch > dh_testdir > dh_testroot > dh_clean -k > mkdir -p > /build/buildd/statdataml-1.0.9/debian//r-cran-statdataml/usr/lib/R/library > R CMD INSTALL -c -l > /build/buildd/statdataml-1.0.9/debian//r-cran-statdataml/usr/lib/R/library > StatDataML/R/StatDataML > * Installing *source* package 'StatDataML' ... > ** R > ** inst > ** preparing package for lazy loading > Loading required package: XML > Error: package 'XML' could not be loaded > In addition: Warning message: > there is no package called 'XML' in: library(pkg, character.only = TRUE, > logical = TRUE, lib.loc = lib.loc) > Execution halted > ERROR: lazy loading failed for package 'StatDataML' > ** Removing > '/build/buildd/statdataml-1.0.9/debian/r-cran-statdataml/usr/lib/R/library/StatDataML' > make: *** [install] Error 1 > ** > Build finished at 20060722-0259 > FAILED [dpkg-buildpackage died] -- Julien Danjou .''`. Debian Developer : :' : http://julien.danjou.info `. `' http://people.debian.org/~acid `- 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD --- End Message --- --- Begin Message --- Source: statdataml Source-Version: 1.0.9-3 We believe that the bug you reported is fixed in the latest version of statdataml, which is due to be installed in the Debian FTP archive: octave-statdataml_1.0.9-3_amd64.deb to pool/main/s/statdataml/octave-statdataml_1.0.9-3_amd64.deb r-cran-statdataml_1.0.9-3_amd64.deb to pool/main/s/statdataml/r-cran-statdataml_1.0.9-3_amd64.deb statdataml_1.0.9-3.diff.gz to pool/main/s/statdataml/statdataml_1.0.9-3.diff.gz statdataml_1.0.9-3.dsc to pool/main/s/statdataml/statdataml_1.0.9-3.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. Michael Ablassmeier <[EMAIL PROTECTED]> (supplier of updated statdataml 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: Tue, 1 Aug 2006 07:30:44 +0200 Source: statdataml Binary: octave-statdataml r-cran-statdataml Architecture: source amd64 Version: 1.0.9-3 Distribution: unstable Urgency: low Maintainer: Debian QA Group <[EMAIL PROTECTED]> Changed-By: Michael Ablassmeier <[EMAIL PROTECTED]> Description: octave-statdataml - GNU Octave package for XML-based data exchange r-cran-statdataml - GNU R package for XML-based data exchange Closes: 379479 Changes: statdataml (1.0.9-3) unstable; urgency=low . * QA Upload * Add r-cran-xml to Build-Depends (Closes: #379479) Kudos to Luca Bruno * Add missing binary-indep Target to debian/rules * Conforms with Latest Standards Version 3.7.2 Files: 8b8e0ea35839c637a61aff7f4522930d 738 math optional statdataml_1.0.9-3.dsc 14ba3887a0f4b2fa7f282a9ded3a58dc 5344 math optional statdataml_1.0.9-3.diff.gz 87f4c3db359233e376834f8a78342a7a 150512 math optional r-cran-statdataml_1.0.9-3_amd64.deb 16eafb83e55bad1bce75e1b013b7336a 27956 math optional octave-statdataml_1.0.9-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEzuwjEFV7g4B8rCURAhJJAKCc4lRyuhMq7Nob5Ogrgsyb9WWwQgCdGRTz clXayeUx2LOOcL+JEOEPP5w= =iDZi -END PGP SIGNATURE- --- End Message ---
Processed: tagging 379714
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.20 > tags 379714 pending Bug#379714: libxslt1-dev should depend on libgcrypt11-dev, libgpg-error-dev There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#379775: #379775: FTBFS: links object files twice
hi, the object files are listed in libtool (predep_objects). After removing this line the build goes well. Also, after an autoconf/automake update this issue is gone but the package fails to build the following way: [..] ar: transportaddressblock.o~ranlib: No such file or directory [..] bye, - michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380721: azureus: Azureus won't start, calls script from swt-3.1
Package: azureus Version: 2.4.0.2-3 Severity: grave Tags: patch Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 $ azureus /usr/bin/azureus: line 2: /usr/share/java-config/libswt-3.1-java: No such file or directory Please change line 2 of /usr/bin/azureus to call SWT-3._2_, instead of SWT-3.1: . /usr/share/java-config/libswt-3.2-java Ingo - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (800, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.7-schwan20060725 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages azureus depends on: ii libcommons-cli-java 1.0-8 API for working with the command l ii liblog4j1.2-java 1.2.13-1 Logging library for java ii libseda-java 3.0-3 the Staged Event-Driven Architectu ii libswt-gtk-3.2-java 3.2-1 Standard Widget Toolkit for GTK Ja ii sun-java5-jre [java2-runtime] 1.5.0-07-1 Sun Java(TM) Runtime Environment ( Versions of packages azureus recommends: pn java-package (no description available) - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEzu0h4XrXtQkN2NURAoXPAKC5A1ug0OQtu3mYoD0Ga3oUST2QvwCeNuSW tr+2Br+Z573HSdqmoWC7RN0= =j37c -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#376249: marked as done (spandsp: runaway `extern "C"' in )
Your message dated Mon, 31 Jul 2006 22:47:26 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376249: fixed in spandsp 0.0.2pre26-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: spandsp Version: 0.0.2pre25-1 Tags: patch Severity: serious Justification: part of the reason yate fails to build (#358131) debian/patches/nonmmx.dpatch is meant to disable on architectures other than i386. However, due to a combination of upstream changes, it applies with too much fuzz, and leaves an `extern "C"' with no closing bracket. Since one of the upstream changes is an equivalent check for __i386__, the patch can simply be removed. Thanks, Matej --- End Message --- --- Begin Message --- Source: spandsp Source-Version: 0.0.2pre26-1 We believe that the bug you reported is fixed in the latest version of spandsp, which is due to be installed in the Debian FTP archive: libspandsp-dev_0.0.2pre26-1_i386.deb to pool/main/s/spandsp/libspandsp-dev_0.0.2pre26-1_i386.deb libspandsp-doc_0.0.2pre26-1_all.deb to pool/main/s/spandsp/libspandsp-doc_0.0.2pre26-1_all.deb libspandsp1_0.0.2pre26-1_i386.deb to pool/main/s/spandsp/libspandsp1_0.0.2pre26-1_i386.deb spandsp_0.0.2pre26-1.diff.gz to pool/main/s/spandsp/spandsp_0.0.2pre26-1.diff.gz spandsp_0.0.2pre26-1.dsc to pool/main/s/spandsp/spandsp_0.0.2pre26-1.dsc spandsp_0.0.2pre26.orig.tar.gz to pool/main/s/spandsp/spandsp_0.0.2pre26.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. Tzafrir Cohen <[EMAIL PROTECTED]> (supplier of updated spandsp 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: Tue, 1 Aug 2006 06:27:47 +0100 Source: spandsp Binary: libspandsp-dev libspandsp1 libspandsp-doc Architecture: source i386 all Version: 0.0.2pre26-1 Distribution: unstable Urgency: low Maintainer: Debian VoIP Team <[EMAIL PROTECTED]> Changed-By: Tzafrir Cohen <[EMAIL PROTECTED]> Description: libspandsp-dev - Telephony signal processing library libspandsp-doc - Documentation for the spandsp signal processing library libspandsp1 - Telephony signal processing library Closes: 376249 377374 Changes: spandsp (0.0.2pre26-1) unstable; urgency=low . * New upstream release. * Added get-orig-source target. * Removed unneeded and buggy nommx.dpatch (Closes: #376249, #377374) Files: 4d9833c506114760c2394c7322f8cf20 896 libs optional spandsp_0.0.2pre26-1.dsc 2b28a75b1d7c49616534bd7264317241 1417752 libs optional spandsp_0.0.2pre26.orig.tar.gz e4622595c8bae24baadf2f7308d5d252 3363 libs optional spandsp_0.0.2pre26-1.diff.gz 74cbf8523d39415b717849150cabee29 597300 doc optional libspandsp-doc_0.0.2pre26-1_all.deb 7e8bc6530f876553b25fa3c7e4c5c8c1 174676 libs optional libspandsp1_0.0.2pre26-1_i386.deb 3f09dceda5178b1e5b673ec56e92d20e 259762 libdevel optional libspandsp-dev_0.0.2pre26-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEzuc9oCzanz0IthIRAh2hAJ95WD2QSLxC3ZHXn6lpF/nHLfeLwACeMIQe XrsDyzMH8fVNpfW0/1+ZQZ0= =Tr8r -END PGP SIGNATURE- --- End Message ---
Bug#379822: marked as done (FTBFS: doesn't recognize autoconf 2.60)
Your message dated Mon, 31 Jul 2006 22:47:23 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379822: fixed in ksubtile 1.2-5 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: ksubtile Version: 1.2-4 Severity: serious Your package fails to build from source because it doesn't recognize Autoconf 2.60. A patch similar to http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946 should fix this problem. For some background, please see the discussion at http://lists.debian.org/debian-devel/2006/07/msg00958.html > Automatic build of ksubtile_1.2-4 on prehension by sbuild/sparc 0.47 ... > make[1]: Entering directory `/build/tbm/ksubtile-1.2' > *** YOU'RE USING autoconf (GNU Autoconf) 2.60. > *** KDE requires autoconf 2.53 or newer > make[1]: *** [cvs] Error 1 > make[1]: Leaving directory `/build/tbm/ksubtile-1.2' > make: *** [makebuilddir/ksubtile] Error 2 -- Martin Michlmayr http://www.cyrius.com/ --- End Message --- --- Begin Message --- Source: ksubtile Source-Version: 1.2-5 We believe that the bug you reported is fixed in the latest version of ksubtile, which is due to be installed in the Debian FTP archive: ksubtile_1.2-5.diff.gz to pool/main/k/ksubtile/ksubtile_1.2-5.diff.gz ksubtile_1.2-5.dsc to pool/main/k/ksubtile/ksubtile_1.2-5.dsc ksubtile_1.2-5_i386.deb to pool/main/k/ksubtile/ksubtile_1.2-5_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ana Beatriz Guerrero Lopez <[EMAIL PROTECTED]> (supplier of updated ksubtile 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, 29 Jul 2006 12:46:34 +0200 Source: ksubtile Binary: ksubtile Architecture: source i386 Version: 1.2-5 Distribution: unstable Urgency: medium Maintainer: Ana Beatriz Guerrero Lopez <[EMAIL PROTECTED]> Changed-By: Ana Beatriz Guerrero Lopez <[EMAIL PROTECTED]> Description: ksubtile - subtitle editor for KDE Closes: 379822 Changes: ksubtile (1.2-5) unstable; urgency=medium . * Dropping re-libtoolizing at build time, instead updating libtool with a patch. (Closes: #379822). Files: b138ee909a4f197caf60dbeba847febb 698 kde optional ksubtile_1.2-5.dsc f69064d97b7ff6ed0a7471cf13cefe65 247569 kde optional ksubtile_1.2-5.diff.gz eadc581fda76ba0620b74223927595ff 246204 kde optional ksubtile_1.2-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEzuZ6ipBneRiAKDwRAqIjAJ96dv6B0tBvIAYYEiiPumpHxwNicwCfUKYo PElG5iR2fItvkYnD4pDGOkM= =jMSF -END PGP SIGNATURE- --- End Message ---
Bug#378864: marked as done (zaptel-source 1.2.7 fails to build)
Your message dated Mon, 31 Jul 2006 22:47:34 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#378864: fixed in zaptel 1:1.2.7-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: zaptel-source Version: 1:1.2.7-1 Arch: i386 Building the Zaptel Kernel modules does not work. Here's the build error message: dh_testroot dh_clean -k make modules KERNEL_SOURCES=/lib/modules/2.6.17-1-686/build MODVERSIONS=detect KERNEL=linux-2.6.17-1-686 make[2]: Entering directory `/usr/src/modules/zaptel' make[2]: *** No rule to make target `modules'. Stop. make[2]: Leaving directory `/usr/src/modules/zaptel' make[1]: *** [binary-modules] Error 2 make[1]: Leaving directory `/usr/src/modules/zaptel' make: *** [kdist_build] Error 2 Tried to build using module-assistant on Etch (2.6.15) and Sid (2.6.17), both as of 19.7.06, to no avail. Also tried on Ubuntu Dapper Drake, always the error above shows up. The same Etch, Sid (and Dapper) machines would build zaptel-source 1.2.6 perfectly. Therefore I believe this to be a package bug. --- End Message --- --- Begin Message --- Source: zaptel Source-Version: 1:1.2.7-2 We believe that the bug you reported is fixed in the latest version of zaptel, which is due to be installed in the Debian FTP archive: libtonezone-dev_1.2.7-2_i386.deb to pool/main/z/zaptel/libtonezone-dev_1.2.7-2_i386.deb libtonezone1_1.2.7-2_i386.deb to pool/main/z/zaptel/libtonezone1_1.2.7-2_i386.deb zaptel-source_1.2.7-2_all.deb to pool/main/z/zaptel/zaptel-source_1.2.7-2_all.deb zaptel_1.2.7-2.diff.gz to pool/main/z/zaptel/zaptel_1.2.7-2.diff.gz zaptel_1.2.7-2.dsc to pool/main/z/zaptel/zaptel_1.2.7-2.dsc zaptel_1.2.7-2_i386.deb to pool/main/z/zaptel/zaptel_1.2.7-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. Mark Purcell <[EMAIL PROTECTED]> (supplier of updated zaptel 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: Tue, 1 Aug 2006 06:29:39 +0100 Source: zaptel Binary: libtonezone1 zaptel-source zaptel libtonezone-dev Architecture: source all i386 Version: 1:1.2.7-2 Distribution: unstable Urgency: low Maintainer: Debian VoIP Team <[EMAIL PROTECTED]> Changed-By: Mark Purcell <[EMAIL PROTECTED]> Description: libtonezone-dev - tonezone library (development) libtonezone1 - tonezone library (runtime) zaptel - zapata telephony utilities zaptel-source - Zapata telephony interface (source code for kernel driver) Closes: 378864 Changes: zaptel (1:1.2.7-2) unstable; urgency=low . * Copying Makefile as before to the source package, Copying some extra files now needed for building (Closes: #378864) Files: 30f67419b42acd844873922df47306f2 942 comm optional zaptel_1.2.7-2.dsc 2fd312a6ffa4abaa78b5128db12a4a96 140307 comm optional zaptel_1.2.7-2.diff.gz e39bc8d8e64b5075cf9b97a9de7ff09a 923442 devel optional zaptel-source_1.2.7-2_all.deb f70a082ea908e57300719750447a15cd 156676 comm optional zaptel_1.2.7-2_i386.deb 7c2a484aed6d0f4aaf8301fe242486b8 22124 libs optional libtonezone1_1.2.7-2_i386.deb efbb032ef6408a00d685cf5efd2f25ea 23166 libdevel optional libtonezone-dev_1.2.7-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEzudMoCzanz0IthIRAlIuAJ9zNdkYmkT7faQ/q7MH/dYn1UdSmACcCglR xLJXeSnLk7YdX5iErBUVijA= =Zw7p -END PGP SIGNATURE- --- End Message ---
Bug#379811: marked as done (FTBFS: doesn't recognize autoconf 2.60)
Your message dated Mon, 31 Jul 2006 22:47:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379811: fixed in kdbg 2.0.4-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: kdbg Version: 2.0.4-1 Severity: serious Your package fails to build from source because it doesn't recognize Autconf 2.60. A patch similar to http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946 should fix this problem. For some background, please see the discussion at http://lists.debian.org/debian-devel/2006/07/msg00958.html > Automatic build of kdbg_2.0.4-1 on prehension by sbuild/sparc 0.47 ... > /usr/bin/make -f admin/Makefile.common > make[1]: Entering directory `/build/tbm/kdbg-2.0.4' > *** YOU'RE USING autoconf (GNU Autoconf) 2.60. > *** KDE requires autoconf 2.53 or newer > make[1]: *** [cvs] Error 1 > make[1]: Leaving directory `/build/tbm/kdbg-2.0.4' > make: *** [build-stamp] Error 2 -- Martin Michlmayr http://www.cyrius.com/ --- End Message --- --- Begin Message --- Source: kdbg Source-Version: 2.0.4-2 We believe that the bug you reported is fixed in the latest version of kdbg, which is due to be installed in the Debian FTP archive: kdbg_2.0.4-2.diff.gz to pool/main/k/kdbg/kdbg_2.0.4-2.diff.gz kdbg_2.0.4-2.dsc to pool/main/k/kdbg/kdbg_2.0.4-2.dsc kdbg_2.0.4-2_i386.deb to pool/main/k/kdbg/kdbg_2.0.4-2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ana Beatriz Guerrero Lopez <[EMAIL PROTECTED]> (supplier of updated kdbg 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, 29 Jul 2006 14:19:18 +0200 Source: kdbg Binary: kdbg Architecture: source i386 Version: 2.0.4-2 Distribution: unstable Urgency: medium Maintainer: Ana Beatriz Guerrero Lopez <[EMAIL PROTECTED]> Changed-By: Ana Beatriz Guerrero Lopez <[EMAIL PROTECTED]> Description: kdbg - graphical debugger interface Closes: 379811 Changes: kdbg (2.0.4-2) unstable; urgency=medium . * Dropping re-libtoolizing at build time, instead updating libtool with a patch. (Closes: #379811). Files: a440076ae872789c8de0d510527759a5 651 devel optional kdbg_2.0.4-2.dsc 2a9be43e2020c1f0af0e4a69bde2c4b0 48211 devel optional kdbg_2.0.4-2.diff.gz db04ebee8fa7f8181c28fcad6a06d655 291586 devel optional kdbg_2.0.4-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEzuepipBneRiAKDwRAuxtAJ4tpQCWfXyPuX+6gRQF0GmOvB/JQACghcu0 J2WvLiXJUIJY0JwUHV8RCWA= =dk5k -END PGP SIGNATURE- --- End Message ---
Bug#293025: Updated package available for NMU
I'm not a debian developer, but I have an updated package ready for an NMU. Rather than the previous patch, I opted for the following which changes the initialization rather than the declaration of EOMoreThanOneException, thereby preserving the public interface in EOUtilities.h. My patched version is available in my local apt repository: http://juckel.net/apt/unstable/. --- gnustep-dl2-0.9.1.orig/EOAccess/EOUtilities.m +++ gnustep-dl2-0.9.1/EOAccess/EOUtilities.m @@ -74,7 +74,7 @@ #include -static NSString *EOMoreThanOneException = @"EOMoreThanOneException"; +NSString *EOMoreThanOneException = @"EOMoreThanOneException"; //static NSString *NSObjectNotAvailableException = @"NSObjectNotAvailableException"; -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380593: marked as done (ldirectord: unwanted emailalerts)
Your message dated Mon, 31 Jul 2006 20:17:15 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#380593: fixed in heartbeat 1.2.4-13 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: ldirectord-2 Version: 2.0.6-1 Severity: serious ldirectord-2 has been reported to be trying to send emailalerts even if not configured to do so. I haven't verified this behaviour myself, and I don't have time to right now. This bug should hold ldirectord-2 out of etch, until I (or someone else) gets a chance to investigate further. If worst comes to worse, email alearts can just be stripped out of the ldirectord source code. But I doubt anything that drastic is required. -- Horms H: http://www.vergenet.net/~horms/ W: http://www.valinux.co.jp/en/ --- End Message --- --- Begin Message --- Source: heartbeat Source-Version: 1.2.4-13 We believe that the bug you reported is fixed in the latest version of heartbeat, which is due to be installed in the Debian FTP archive: heartbeat-dev_1.2.4-13_i386.deb to pool/main/h/heartbeat/heartbeat-dev_1.2.4-13_i386.deb heartbeat_1.2.4-13.diff.gz to pool/main/h/heartbeat/heartbeat_1.2.4-13.diff.gz heartbeat_1.2.4-13.dsc to pool/main/h/heartbeat/heartbeat_1.2.4-13.dsc heartbeat_1.2.4-13_i386.deb to pool/main/h/heartbeat/heartbeat_1.2.4-13_i386.deb ldirectord_1.2.4-13_all.deb to pool/main/h/heartbeat/ldirectord_1.2.4-13_all.deb libpils-dev_1.2.4-13_i386.deb to pool/main/h/heartbeat/libpils-dev_1.2.4-13_i386.deb libpils0_1.2.4-13_i386.deb to pool/main/h/heartbeat/libpils0_1.2.4-13_i386.deb libstonith-dev_1.2.4-13_i386.deb to pool/main/h/heartbeat/libstonith-dev_1.2.4-13_i386.deb libstonith0_1.2.4-13_i386.deb to pool/main/h/heartbeat/libstonith0_1.2.4-13_i386.deb stonith_1.2.4-13_i386.deb to pool/main/h/heartbeat/stonith_1.2.4-13_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. Simon Horman <[EMAIL PROTECTED]> (supplier of updated heartbeat package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 31 Jul 2006 17:25:03 +0900 Source: heartbeat Binary: libstonith-dev ldirectord libstonith0 heartbeat libpils-dev libpils0 stonith heartbeat-dev Architecture: source i386 all Version: 1.2.4-13 Distribution: unstable Urgency: low Maintainer: Simon Horman <[EMAIL PROTECTED]> Changed-By: Simon Horman <[EMAIL PROTECTED]> Description: heartbeat - Subsystem for High-Availability Linux heartbeat-dev - Subsystem for High-Availability Linux - development files ldirectord - Monitors virtual services provided by LVS libpils-dev - Plugin and Interface Loading System - development files libpils0 - Plugin and Interface Loading System libstonith-dev - Interface for remotely powering down a node in the cluster libstonith0 - Interface for remotely powering down a node in the cluster stonith- Interface for remotely powering down a node in the cluster Closes: 379904 380180 380593 Changes: heartbeat (1.2.4-13) unstable; urgency=low . * shmget-perms.patch Fix local denial of service caused by incorrect permisions on a shared memory page. CVE-2006-3815, DSA-1128 (closes: #379904) * ldirectord-1.141-emailalert-1-quiet.patch Don't send email alerts if the alert address is not configured (closes: #380593) * ldirectord-1.139.patch, ldirectord-1.141-emailalert-2-global.patch Allow emailalert and emailalertfreq directives to be global as well as per-virtual service * ldirectord-1.141-readline_workaround.patch readline doesn't seem to return lines after Net::FTP has been called, so split them up by hand. * Added build dependancy on iptables, as it is needed to supply the correct path to iptables for the portblock resource (closes: #380180) * Added recommends iptables to heartbeat-2, as it is needed for the portblock resource to function correctly Files: 2a936ed9d818dd07779649df89462126 895 admin optional heartbeat_1.2.4-13.dsc d18fb5b8a722cf1316a021cdddebf062 19143 admin optional heartbea
Bug#379904: marked as done (heartbeat: Local DoS due to world-writable shared memory [CVE-2006-3815])
Your message dated Mon, 31 Jul 2006 20:17:15 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379904: fixed in heartbeat 1.2.4-13 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: heartbeat Version: 1.2.4-12 Severity: grave Tags: security patch Hi! Recently, a local DoS due to world-writable/readable shared memory permissions was found and fixed in heartbeat: Upstream fix: http://cvs.linux-ha.org/viewcvs/viewcvs.cgi/linux-ha/heartbeat/heartbeat.c?r1=1.513&r2=1.514 This has been assigned CVE-2006-3815. Please mention this number in the changelog when you fix this to ease tracking. Thank you! Martin -- Martin Pitthttp://www.piware.de Ubuntu Developer http://www.ubuntu.com Debian Developer http://www.debian.org In a world without walls and fences, who needs Windows and Gates? signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: heartbeat Source-Version: 1.2.4-13 We believe that the bug you reported is fixed in the latest version of heartbeat, which is due to be installed in the Debian FTP archive: heartbeat-dev_1.2.4-13_i386.deb to pool/main/h/heartbeat/heartbeat-dev_1.2.4-13_i386.deb heartbeat_1.2.4-13.diff.gz to pool/main/h/heartbeat/heartbeat_1.2.4-13.diff.gz heartbeat_1.2.4-13.dsc to pool/main/h/heartbeat/heartbeat_1.2.4-13.dsc heartbeat_1.2.4-13_i386.deb to pool/main/h/heartbeat/heartbeat_1.2.4-13_i386.deb ldirectord_1.2.4-13_all.deb to pool/main/h/heartbeat/ldirectord_1.2.4-13_all.deb libpils-dev_1.2.4-13_i386.deb to pool/main/h/heartbeat/libpils-dev_1.2.4-13_i386.deb libpils0_1.2.4-13_i386.deb to pool/main/h/heartbeat/libpils0_1.2.4-13_i386.deb libstonith-dev_1.2.4-13_i386.deb to pool/main/h/heartbeat/libstonith-dev_1.2.4-13_i386.deb libstonith0_1.2.4-13_i386.deb to pool/main/h/heartbeat/libstonith0_1.2.4-13_i386.deb stonith_1.2.4-13_i386.deb to pool/main/h/heartbeat/stonith_1.2.4-13_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. Simon Horman <[EMAIL PROTECTED]> (supplier of updated heartbeat package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 31 Jul 2006 17:25:03 +0900 Source: heartbeat Binary: libstonith-dev ldirectord libstonith0 heartbeat libpils-dev libpils0 stonith heartbeat-dev Architecture: source i386 all Version: 1.2.4-13 Distribution: unstable Urgency: low Maintainer: Simon Horman <[EMAIL PROTECTED]> Changed-By: Simon Horman <[EMAIL PROTECTED]> Description: heartbeat - Subsystem for High-Availability Linux heartbeat-dev - Subsystem for High-Availability Linux - development files ldirectord - Monitors virtual services provided by LVS libpils-dev - Plugin and Interface Loading System - development files libpils0 - Plugin and Interface Loading System libstonith-dev - Interface for remotely powering down a node in the cluster libstonith0 - Interface for remotely powering down a node in the cluster stonith- Interface for remotely powering down a node in the cluster Closes: 379904 380180 380593 Changes: heartbeat (1.2.4-13) unstable; urgency=low . * shmget-perms.patch Fix local denial of service caused by incorrect permisions on a shared memory page. CVE-2006-3815, DSA-1128 (closes: #379904) * ldirectord-1.141-emailalert-1-quiet.patch Don't send email alerts if the alert address is not configured (closes: #380593) * ldirectord-1.139.patch, ldirectord-1.141-emailalert-2-global.patch Allow emailalert and emailalertfreq directives to be global as well as per-virtual service * ldirectord-1.141-readline_workaround.patch readline doesn't seem to return lines after Net::FTP has been called, so split them up by hand. * Added build dependancy on iptables, as it is needed to supply the correct path to iptables for the portblock resource (closes: #380180) * Added recommends iptables to heartbeat-2, as it is needed for the portblock resource to function correctly Files: 2a936ed9d818dd07779649df89462126 895 admin optional heartbeat_1.2.4-13
Bug#380180: marked as done (heartbeat: portblock syntax errors in 1.2.3-9sarge5)
Your message dated Mon, 31 Jul 2006 20:17:15 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#380180: fixed in heartbeat 1.2.4-13 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: heartbeat Version: 1.2.3-9sarge5 Severity: grave Tags: patch Justification: renders package unusable After upgrading to 1.2.3-9sarge5, heartbeat kept rebooting the system as there were errors running the portblock resource script. This bug applies to people which use portblock as heartbeat service to drop incoming network packets when service takeover. The syntax error is due to a missing iptables path which results in "command not found" errors in /etc/ha.d/resource.d/portblock. Fixing is simple, patch is attached (putting iptables back into place). -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.16-2-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages heartbeat depends on: ii adduser 3.63 Add and remove users and groups ii iproute 20041019-3 Professional tools to control the ii iputils-ping 3:20020927-2 Tools to test the reachability of ii libc6 2.3.2.ds1-22sarge3 GNU C Library: Shared libraries an ii libglib1.21.2.10-9 The GLib library of C routines ii libnet1 1.1.2.1-2 library for the construction and h ii libpils0 1.2.3-9sarge5 Plugin and Interface Loading Syste ii libstonith0 1.2.3-9sarge5 Interface for remotely powering do ii python2.3.5-2An interactive high-level object-o -- no debconf information --- portblock.original 2006-07-28 09:35:16.0 +0200 +++ portblock 2006-07-28 09:19:26.0 +0200 @@ -68,7 +68,7 @@ *) exit 3;; esac } -iptables= +iptables=/sbin/iptables BlockOrUnblock=block --- End Message --- --- Begin Message --- Source: heartbeat Source-Version: 1.2.4-13 We believe that the bug you reported is fixed in the latest version of heartbeat, which is due to be installed in the Debian FTP archive: heartbeat-dev_1.2.4-13_i386.deb to pool/main/h/heartbeat/heartbeat-dev_1.2.4-13_i386.deb heartbeat_1.2.4-13.diff.gz to pool/main/h/heartbeat/heartbeat_1.2.4-13.diff.gz heartbeat_1.2.4-13.dsc to pool/main/h/heartbeat/heartbeat_1.2.4-13.dsc heartbeat_1.2.4-13_i386.deb to pool/main/h/heartbeat/heartbeat_1.2.4-13_i386.deb ldirectord_1.2.4-13_all.deb to pool/main/h/heartbeat/ldirectord_1.2.4-13_all.deb libpils-dev_1.2.4-13_i386.deb to pool/main/h/heartbeat/libpils-dev_1.2.4-13_i386.deb libpils0_1.2.4-13_i386.deb to pool/main/h/heartbeat/libpils0_1.2.4-13_i386.deb libstonith-dev_1.2.4-13_i386.deb to pool/main/h/heartbeat/libstonith-dev_1.2.4-13_i386.deb libstonith0_1.2.4-13_i386.deb to pool/main/h/heartbeat/libstonith0_1.2.4-13_i386.deb stonith_1.2.4-13_i386.deb to pool/main/h/heartbeat/stonith_1.2.4-13_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. Simon Horman <[EMAIL PROTECTED]> (supplier of updated heartbeat package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 31 Jul 2006 17:25:03 +0900 Source: heartbeat Binary: libstonith-dev ldirectord libstonith0 heartbeat libpils-dev libpils0 stonith heartbeat-dev Architecture: source i386 all Version: 1.2.4-13 Distribution: unstable Urgency: low Maintainer: Simon Horman <[EMAIL PROTECTED]> Changed-By: Simon Horman <[EMAIL PROTECTED]> Description: heartbeat - Subsystem for High-Availability Linux heartbeat-dev - Subsystem for High-Availability Linux - development files ldirectord - Monitors virtual services provided by LVS libpils-dev - Plugin and Interface Loading System - development files libpils0 - Plugin and Interface Loading System libstonith-dev - Interface for remotely powering down a node in the cluster libstonith0 - Interface for remotely powering down a node in the cluster stonith- Interface for remotely powering down a node in the cluster Closes: 379904 380180 3805
Bug#379359: marked as done (Installation failure)
Your message dated Mon, 31 Jul 2006 20:17:39 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379359: fixed in kiwi 1.9.8-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) --- Begin Message --- Package: python-kiwi Severity: grave Version: 1.9.8-5 Trying to upgrade to the latest version of python-kiwi yields this: Setting up python-kiwi (1.9.8-5) ... Traceback (most recent call last): File "/usr/sbin/update-python-modules", line 268, in ? process(basedir,install_modules(py_installed)) File "/usr/sbin/update-python-modules", line 150, in process func(basedir, dir, file) File "/usr/sbin/update-python-modules", line 122, in install_modules_func os.symlink(fullpath,destpath) OSError: [Errno 17] File exists dpkg: error processing python-kiwi (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: python-kiwi E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up python-kiwi (1.9.8-5) ... Traceback (most recent call last): File "/usr/sbin/update-python-modules", line 268, in ? process(basedir,install_modules(py_installed)) File "/usr/sbin/update-python-modules", line 150, in process func(basedir, dir, file) File "/usr/sbin/update-python-modules", line 122, in install_modules_func os.symlink(fullpath,destpath) OSError: [Errno 17] File exists dpkg: error processing python-kiwi (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: python-kiwi Regards: David -- /) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\ // ~ // Diamond-white roses of fire // \) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/ --- End Message --- --- Begin Message --- Source: kiwi Source-Version: 1.9.8-6 We believe that the bug you reported is fixed in the latest version of kiwi, which is due to be installed in the Debian FTP archive: kiwi_1.9.8-6.diff.gz to pool/main/k/kiwi/kiwi_1.9.8-6.diff.gz kiwi_1.9.8-6.dsc to pool/main/k/kiwi/kiwi_1.9.8-6.dsc python-kiwi_1.9.8-6_all.deb to pool/main/k/kiwi/python-kiwi_1.9.8-6_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. Gustavo Noronha Silva <[EMAIL PROTECTED]> (supplier of updated kiwi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 31 Jul 2006 23:22:58 -0300 Source: kiwi Binary: python-kiwi Architecture: source all Version: 1.9.8-6 Distribution: unstable Urgency: medium Maintainer: Gustavo Noronha Silva <[EMAIL PROTECTED]> Changed-By: Gustavo Noronha Silva <[EMAIL PROTECTED]> Description: python-kiwi - a graphical framework to construct simple UI Closes: 379359 Changes: kiwi (1.9.8-6) unstable; urgency=medium . * debian/preinst: - added to handle problems in upgrade caused by -4 and earlier being built with a python-support version which was buggy when handling "outside" modules (Closes: #379359) * debian/rules: - cleaning up; removing commented code that is not needed anymore and remove the code that sed's the python version, for that is done by the tools now * urgency medium to get the buggy version out of testing soon Files: b6605c75a701cc22850fbc3f57575d19 809 python optional kiwi_1.9.8-6.dsc 0e2fde22b438d58f1803e90d7f732b4b 3500 python optional kiwi_1.9.8-6.diff.gz b8b8a0ca363881c0b9c530ccdec906cf 161054 python optional python-kiwi_1.9.8-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEzsM5t1anjIgqbEsRAkgDAKDssuwuxew4o07k6r1lPW67Toq1qQCcDNzZ CUu2KuS1IgFwQ8aOUxZKsZM= =u2Ka -END PGP SIGNATURE- --- End Message ---
Bug#379531: Uploading new package
You asked how you should upload your package to Debian. I really do wonder how you got your package uploaded in the first place. You are supposed to get a sponsor for your package. If you have your package ready, I suggest you send a mail to debian-mentors explaining why you need your package uploaded, and where the new version is ready. -- Greetings, Marga -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#358696: This is dangerous, please make it default to disabled
On Mon, 2006 Jul 31 13:47:21 -0300, Henrique de Moraes Holschuh wrote: > > > > Define "(un)suitable for UPS management." Does this definition include > > most people's desktop systems? > > Suitable for UPS management: > Load: > Powers up when AC returns > Can be informed that it must shutdown by the UPS > (through NUT). Okay, so pretty much anything that can run NUT. Nice. > UPS: > Does delayed load shutdown upon shutdown command > Does not power up the load before it has enough charge > to do a delayed shutdown, plus safety margin. Pretty basic stuff, yes. > Always power-cycles the load after a shutdown command is > ACK'ed to the controlling host. Even if AC > returns, and it doesn't need to shutdown anymore. Many low-end UPSes fail here. Power races would be an academic issue if not for this. > Communicates the host when battery charge is below a > certain threshold, so that it can shutdown safely. > Powers up the load if the batteries have enough charge, > and an AC cycle happens while the load is offline. > Powers up the load after a timer expires, if no AC cycles > happen AND the load was broght offline by an explicit > delayed shutdown command. > > Anything else is unsuitable. Hi, I'm Bob, and I have an unsuitable UPS. Can I use it with Debian? > Any PC97 desktop should be suitable for proper UPS management. And just > FYI, PC97 requires WoL on all ethernet devices, not that you need WoL for > a proper UPS setup, but you somehow got the idea that WoL was a > server-grade feature... Fair enough, but a UPS with an Ethernet port (and a means of configuring WoL) certainly is. If not in purpose, then in price. > > No, but any decent power supply will present a load pretty close to it, > > Only ones with PFC. Decent power supplies have PFC. > > number of machines connected, but large numbers of machines connected are > > not exactly a typical scenario. > > No, but your hard-drive doing emergency unloads is a typical scenario, and > desktop HDs don't like those unloads *at* *all*. Do not do it (and as I > already said, the only proper way to know the HD heads are unloaded requires > kernel cooperation, and it is NOT done by userspace currently). > > I know you were under the mistaken impression that we could guarantee all > HD heads were unloaded in userspace, and before halt runs. We not only > cannot do it, we also do not *attempt* to do it. The only thing in Debian > initscripts that really tries to take care of HD head unloads is the halt > command. > > You can, of course, try to make sure hdparm was run and actually uloaded all > heads for your particular configuration, but it is not an acceptable > default, because we cannot get it right every time. So implement it as an > admin-enabled, admin-configured option by all means. But *not* as a > default. Perhaps the sleep-then-reboot loop belongs inside the halt command, then. At some point, there's going to be little difference between cutting power to the PSU, and having the PSU do a soft poweroff. > > need to. What more shutdown magic do you need on a hard disk that is not > > spinning? > > None. If the disk spun down, but hdparm doesn't work for all disks. And we > cannot reliably spin down all disks and uload heads from userspace, for all > possible configurations. Thus, anything that relies on this cannot be made > a default. > > > If you're talking about a flaky hardware RAID array where you can't stop > > SCSI plus all software RAID arrays. I mean _after_ mdadm is stopped. Not that any distinction is currently made between RAID setups, flaky or otherwise. > The bad thing in your patch is that the maintainer made it non-optional, and > the default. I understand it will not be a default anymore, which is enough > for me. I agree that having it non-optional is undesirable. > > You: Do a normal system shutdown. Rely on server-grade features (e.g. WOL > > No. Me: make the whole behaviour you want *optional*, and not the default, > because it is dangerous and we don't have a lick of a chance of making it > safe for all setups. > > packet from a networked UPS) to resume operation, or an "On/Off state: ON" > > No. Rely on standard PC97 ACPI desktop BIOS option "always power on on AC > return", which is the correct way to deal with machines that need to restart > when an UPS powers it up again. Correct? The PC will then always turn on when the AC returns, e.g. when being plugged in, or after a power outage when it was off to begin with. The PSU's hard power switch isn't a solution, either, as it is often inconvenient/inaccessible and many newer consumer PSUs don't even have one. The real solution is
Bug#379818: Patch to fix FTBFS: doesn't recognize autoconf 2.60
Hi,
I have prepared a (quite trivial) patch which makes the package build
with autoconf 2.60 (attached below).
Greetings Arjan Oosting
diff -u konserve-0.10.3/debian/changelog konserve-0.10.3/debian/changelog
--- konserve-0.10.3/debian/changelog
+++ konserve-0.10.3/debian/changelog
@@ -1,3 +1,10 @@
+konserve (0.10.3-2.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * debian/patches/01_admin_update.diff: update to support autoconf 2.60 (Closes: #379818)
+
+ -- Arjan Oosting <[EMAIL PROTECTED]> Tue, 1 Aug 2006 02:56:01 +0200
+
konserve (0.10.3-2.1) unstable; urgency=low
* Non-maintainer upload.
diff -u konserve-0.10.3/debian/patches/01_admin_update.diff konserve-0.10.3/debian/patches/01_admin_update.diff
--- konserve-0.10.3/debian/patches/01_admin_update.diff
+++ konserve-0.10.3/debian/patches/01_admin_update.diff
@@ -1,6 +1,6 @@
-diff -Nua /home/alex/debian/konserve/upstream/konserve-0.10.3/admin/acinclude.m4.in ./acinclude.m4.in
+diff -Naur konserve-0.10.3.orig/admin/acinclude.m4.in konserve-0.10.3/admin/acinclude.m4.in
--- konserve-0.10.3.orig/admin/acinclude.m4.in 2004-02-06 16:04:24.0 +0100
-+++ konserve-0.10.3/admin/acinclude.m4.in 2005-08-17 16:44:36.945570440 +0200
konserve-0.10.3/admin/acinclude.m4.in 2006-08-01 03:02:30.0 +0200
@@ -16,8 +16,8 @@
dnlYou should have received a copy of the GNU Library General Public License
@@ -1204,9 +1204,9 @@
+ PKG_CHECK_MODULES($1,$2,$3,$4)
+])
+
-diff -Nua /home/alex/debian/konserve/upstream/konserve-0.10.3/admin/am_edit ./am_edit
+diff -Naur konserve-0.10.3.orig/admin/am_edit konserve-0.10.3/admin/am_edit
--- konserve-0.10.3.orig/admin/am_edit 2004-01-29 15:58:27.0 +0100
-+++ konserve-0.10.3/admin/am_edit 2005-08-17 16:44:36.908576064 +0200
konserve-0.10.3/admin/am_edit 2006-08-01 03:02:30.0 +0200
@@ -483,6 +483,7 @@
$MakefileData =~ s/$lookup/$replacement/;
$lookup =~ s/\\\$\\\(CXXFLAGS\\\)/\\\$\\\(KCXXFLAGS\\\)/;
@@ -1283,9 +1283,9 @@
if ( !( $MakefileData =~ s/^(.*generated .*by automake.*\n)/$1$progIdLine/ ) ) {
warn "automake line not found in $makefile\n";
# Fallback: first line
-diff -Nua /home/alex/debian/konserve/upstream/konserve-0.10.3/admin/conf.change.pl ./conf.change.pl
+diff -Naur konserve-0.10.3.orig/admin/conf.change.pl konserve-0.10.3/admin/conf.change.pl
--- konserve-0.10.3.orig/admin/conf.change.pl 2003-11-19 11:21:14.0 +0100
-+++ konserve-0.10.3/admin/conf.change.pl 2005-08-17 16:44:36.823588984 +0200
konserve-0.10.3/admin/conf.change.pl 2006-08-01 03:02:30.0 +0200
@@ -81,7 +81,7 @@
# on autoconf 250, it ends with '# CONFIG_HEADER section'
#
@@ -1295,9 +1295,9 @@
# (pattern: /^\s+#\sRun the commands associated with the file./)
if (/^\s*for\s+ac_file\s+in\s+.*CONFIG_FILES/ ) {
-diff -Nua /home/alex/debian/konserve/upstream/konserve-0.10.3/admin/config.guess ./config.guess
+diff -Naur konserve-0.10.3.orig/admin/config.guess konserve-0.10.3/admin/config.guess
--- konserve-0.10.3.orig/admin/config.guess 2002-10-26 18:44:28.0 +0200
-+++ konserve-0.10.3/admin/config.guess 2005-08-17 16:44:36.871581688 +0200
konserve-0.10.3/admin/config.guess 2006-08-01 03:02:30.0 +0200
@@ -1,9 +1,9 @@
#! /bin/sh
# Attempt to guess a canonical system name.
@@ -1907,9 +1907,9 @@
# Apollos put the system type in the environment.
-diff -Nua /home/alex/debian/konserve/upstream/konserve-0.10.3/admin/config.sub ./config.sub
+diff -Naur konserve-0.10.3.orig/admin/config.sub konserve-0.10.3/admin/config.sub
--- konserve-0.10.3.orig/admin/config.sub 2002-10-26 18:44:28.0 +0200
-+++ konserve-0.10.3/admin/config.sub 2005-08-17 16:44:36.875581080 +0200
konserve-0.10.3/admin/config.sub 2006-08-01 03:02:30.0 +0200
@@ -1,9 +1,9 @@
#! /bin/sh
# Configuration validation subroutine script.
@@ -2377,9 +2377,9 @@
-vxsim* | -vxworks* | -windiss*)
vendor=wrs
;;
-diff -Nua /home/alex/debian/konserve/upstream/konserve-0.10.3/admin/configure.in.bot.end ./configure.in.bot.end
+diff -Naur konserve-0.10.3.orig/admin/configure.in.bot.end konserve-0.10.3/admin/configure.in.bot.end
--- konserve-0.10.3.orig/admin/configure.in.bot.end 2002-09-21 23:13:34.0 +0200
-+++ konserve-0.10.3/admin/configure.in.bot.end 2005-08-01 12:35:31.699056064 +0200
konserve-0.10.3/admin/configure.in.bot.end 2006-08-01 03:02:30.0 +0200
@@ -1,6 +1,39 @@
+# Check if KDE_SET_PREFIX was called, and --prefix was passed to configure
+if test -n "$kde_libs_prefix" -a -n "$given_prefix"; then
@@ -2421,9 +2421,9 @@
echo "Please remove the file $cache_file after changing your setup"
echo "so that configure will find the changes next time."
echo ""
-diff -Nua /home/alex/debian/konserve/upstream/konserve-0.10.3/admin/cvs.sh ./cvs.sh
konserve-0.10.3.orig/admin/cvs.sh 2004-01-30 10:11:51.0 +0100
-+++ konserve-0.10.3/admin/cvs.sh 2005-08-1
Bug#380697: FTBFS: AL/al{,c}.h: No such file or directory
Package: soya Severity: serious Hi, soya_0.12-1 FTBFS with the following error: _soya.c:19:19: error: AL/al.h: No such file or directory _soya.c:20:20: error: AL/alc.h: No such file or directory and a lot of conseguences (e.g. X undeclared). Roberto -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.5 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) (ignored: LC_ALL set to [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 379818
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.20 > tags 379818 patch Bug#379818: FTBFS: doesn't recognize autoconf 2.60 There were no tags set. Tags added: patch > 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#380700: FTBFS: cast from 'char*' to 'int' loses precision
Package: raidutils Version: 0.0.6-1 Severity: serious Hi, raidutils_0.0.6-1 FTBFS on all 64bit arches with the following error: osd_unix.cpp: In function 'int BufferAlloc(uLONG, char**, uLONG, char**, int)': osd_unix.cpp:2654: error: cast from 'char*' to 'int' loses precision make[3]: *** [raideng-osd_unix.o] Error 1 The same function has already been cursed by #302597. Thanks, Roberto -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.5 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) (ignored: LC_ALL set to [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380699: FTBFS: sh: latex: command not found
Package: yodl Version: 2.01.03-1 Severity: serious Hi, yodl_2.01.03-1 FTBFS with the following error: latex yodl.latex sh: latex: command not found execute - program indicates failure (status 32512) execute - program indicates failure (status 32512) execute - program indicates failure (status 256) execute - program indicates failure (status 256) make: *** [build-stamp] Error 1 Roberto -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.5 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) (ignored: LC_ALL set to [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#364374: marked as done (Build-Dep on mozilla (library), please transition to xulrunner)
Your message dated Mon, 31 Jul 2006 17:32:57 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#364374: fixed in greasemonkey 0.6.4-5 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: greasemonkey Severity: wishlist Heya, It looks like your package still depends on a mozilla library in testing. As upstream declared mozilla to be dead and moved all functionality that is needed to embed gecko and friends to a new software suite (xulrunner), you should update your package to work with those. At the moment, it looks like we don't want to release etch with mozilla [1]. This means that your package needs to update it's build-dependencies to the new packages provided by xulrunner. The interface shouldn't have changed, so looking at this mapping, changing the packaging a bit and doing a test-build should be enough: libnspr-dev -> libnspr4-dev libnspr4-> libnspr4-0d libnss-dev -> libnss3-dev libnss3 -> libnss3-0d mozilla-dev -> libxul-dev (probably, you may need to change include pathes) Maybe you've been lucky and upstream already transitioned to use the xulrunner environment. Marc Footnotes: [1] Mozilla security maintenance isn't easy anyway, but releasing it and with that promising security support *after* it was declared dead by upstream would be insane. So we don't want to do that. --- End Message --- --- Begin Message --- Source: greasemonkey Source-Version: 0.6.4-5 We believe that the bug you reported is fixed in the latest version of greasemonkey, which is due to be installed in the Debian FTP archive: firefox-greasemonkey_0.6.4-5_all.deb to pool/main/g/greasemonkey/firefox-greasemonkey_0.6.4-5_all.deb greasemonkey_0.6.4-5.diff.gz to pool/main/g/greasemonkey/greasemonkey_0.6.4-5.diff.gz greasemonkey_0.6.4-5.dsc to pool/main/g/greasemonkey/greasemonkey_0.6.4-5.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. Michael Spang <[EMAIL PROTECTED]> (supplier of updated greasemonkey 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, 29 Jul 2006 14:44:02 -0400 Source: greasemonkey Binary: firefox-greasemonkey Architecture: source all Version: 0.6.4-5 Distribution: unstable Urgency: low Maintainer: Michael Spang <[EMAIL PROTECTED]> Changed-By: Michael Spang <[EMAIL PROTECTED]> Description: firefox-greasemonkey - firefox extension which enables customization of webpages with us Closes: 364374 Changes: greasemonkey (0.6.4-5) unstable; urgency=low . * Transition dependency on obsolete package mozilla-dev to its replacement libxul-dev (Closes: #364374) * Fixed debian/rules to avoid redundant builds Files: 872e511abbeb57d976957aa71ff2c073 625 web optional greasemonkey_0.6.4-5.dsc e9581383a6bca3bac10a2f4eededa472 2333 web optional greasemonkey_0.6.4-5.diff.gz e56622e56697d57e8e85dde5f73d9aee 33014 web optional firefox-greasemonkey_0.6.4-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEzp2JgcCJIoCND9ARAqOAAKCcm5ZIr0owLol4uaEXVCv8slbN1gCgvddN ZvY+qnu7QlYlbS9c0vompoI= =xC4m -END PGP SIGNATURE- --- End Message ---
Processed: Fixed in NMU of lilo 1:22.6.1-7.1
Processing commands for [EMAIL PROTECTED]: > tag 374477 + fixed Bug#374477: lilo: creates devices in postinstall with mknod not MAKEDEV Tags were: pending patch 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]
Processed: Intent to NMU
Processing commands for [EMAIL PROTECTED]: > Tags 374477 + pending Bug#374477: lilo: creates devices in postinstall with mknod not MAKEDEV Tags were: patch 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#374477: Intent to NMU
Tags 374477 + pending thanks I've prepared the package for the patch that Martin provided and I'm going to upload it as an NMU. I'm providing the full diff for the NMU, which is basically the same patch Martin provided plus the changelog entry. -- Love, Marga diff -u lilo-22.6.1/debian/changelog lilo-22.6.1/debian/changelog --- lilo-22.6.1/debian/changelog +++ lilo-22.6.1/debian/changelog @@ -1,3 +1,11 @@ +lilo (1:22.6.1-7.1) unstable; urgency=medium + + * Non-Maintainer Upload to fix a policy violation due to the use of mknod +instead of MAKEDEV. Thanks to Martin Ferrari for the patch. +(Closes: #374477) + + -- Margarita Manterola <[EMAIL PROTECTED]> Mon, 31 Jul 2006 17:12:34 -0300 + lilo (1:22.6.1-7) unstable; urgency=low * Maintenance upload. diff -u lilo-22.6.1/debian/lilo.postinst lilo-22.6.1/debian/lilo.postinst --- lilo-22.6.1/debian/lilo.postinst +++ lilo-22.6.1/debian/lilo.postinst @@ -52,13 +52,7 @@ # Create the missing devices echo -n "Creating network block devices... " pushd /dev > /dev/null - i=0 - while [ $i != 128 ]; do - if [ ! -b nbd$i ]; then - /bin/mknod nbd$i b 43 $i - fi - i=$(($i+1)) - done + ./MAKEDEV nb popd > /dev/null echo "done." fi
Bug#379492: Patch to fix FTBFS: doesn't recognize autoconf 2.60
Hi,
I have prepared a (quite trivial) patch which makes the package build
with autoconf 2.60 (attached below).
Greetings Arjan Oosting
diff -u klog-0.3.3/debian/changelog klog-0.3.3/debian/changelog
--- klog-0.3.3/debian/changelog
+++ klog-0.3.3/debian/changelog
@@ -1,3 +1,11 @@
+klog (0.3.3-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * admin/cvs.sh: update to support autoconf 2.60 (Closes: #379492,
+379815)
+
+ -- Arjan Oosting <[EMAIL PROTECTED]> Tue, 1 Aug 2006 02:35:18 +0200
+
klog (0.3.3-2) unstable; urgency=low
* Built against new hamlib. (Closes: #360197)
only in patch2:
unchanged:
--- klog-0.3.3.orig/admin/cvs.sh
+++ klog-0.3.3/admin/cvs.sh
@@ -29,7 +29,7 @@
{
AUTOCONF_VERSION=`$AUTOCONF --version | head -n 1`
case $AUTOCONF_VERSION in
- Autoconf*2.5* | autoconf*2.5* ) : ;;
+ Autoconf*2.5* | autoconf*2.5* | autoconf*2.6* ) : ;;
"" )
echo "*** AUTOCONF NOT FOUND!."
echo "*** KDE requires autoconf 2.52, 2.53 or 2.54"
@@ -44,7 +44,7 @@
AUTOHEADER_VERSION=`$AUTOHEADER --version | head -n 1`
case $AUTOHEADER_VERSION in
- Autoconf*2.5* | autoheader*2.5* ) : ;;
+ Autoconf*2.5* | autoheader*2.5* | autoheader*2.6*) : ;;
"" )
echo "*** AUTOHEADER NOT FOUND!."
echo "*** KDE requires autoheader 2.52 or 2.53 (part of autoconf)"
signature.asc
Description: Dit berichtdeel is digitaal ondertekend
Bug#379812: Patch to fix FTBFS: doesn't recognize autoconf 2.60
Hi, I have prepared a (quite trivial) patch which makes the package build with autoconf 2.60 (attached below). Greetings Arjan Oosting diff -u kde-style-polyester-0.9.2/debian/changelog kde-style-polyester-0.9.2/debian/changelog --- kde-style-polyester-0.9.2/debian/changelog +++ kde-style-polyester-0.9.2/debian/changelog @@ -1,3 +1,10 @@ +kde-style-polyester (0.9.2-1.1) unstable; urgency=low + + * Non-maintainer upload. + * admin/cvs.sh: update to recognize autoconf 2.60 (Closes: #379812) + + -- Arjan Oosting <[EMAIL PROTECTED]> Tue, 1 Aug 2006 01:41:51 +0200 + kde-style-polyester (0.9.2-1) unstable; urgency=low * New upstream release only in patch2: unchanged: --- kde-style-polyester-0.9.2.orig/admin/cvs.sh +++ kde-style-polyester-0.9.2/admin/cvs.sh @@ -32,7 +32,7 @@ required_autoconf_version="2.53 or newer" AUTOCONF_VERSION=`$AUTOCONF --version | head -n 1` case $AUTOCONF_VERSION in - Autoconf*2.5* | autoconf*2.5* ) : ;; + Autoconf*2.5* | autoconf*2.5* | autoconf*2.6* ) : ;; "" ) echo "*** AUTOCONF NOT FOUND!." echo "*** KDE requires autoconf $required_autoconf_version" @@ -47,7 +47,7 @@ AUTOHEADER_VERSION=`$AUTOHEADER --version | head -n 1` case $AUTOHEADER_VERSION in - Autoconf*2.5* | autoheader*2.5* ) : ;; + Autoconf*2.5* | autoheader*2.5* | autoheader*2.6* ) : ;; "" ) echo "*** AUTOHEADER NOT FOUND!." echo "*** KDE requires autoheader $required_autoconf_version" signature.asc Description: Dit berichtdeel is digitaal ondertekend
Processed: tagging 373733
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.20 > tags 373733 + pending Bug#373733: balazar: segfaults when starting a game There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 379812, tagging 379492, tagging 379815
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.20 > tags 379812 patch Bug#379812: FTBFS: doesn't recognize autoconf 2.60 There were no tags set. Tags added: patch > tags 379492 patch Bug#379492: klog: FTBFS: autoconf 2.60 is not supported There were no tags set. Bug#379815: FTBFS: doesn't recognize autoconf 2.60 Tags added: patch > tags 379815 patch Bug#379815: FTBFS: doesn't recognize autoconf 2.60 Tags were: patch Bug#379492: klog: FTBFS: autoconf 2.60 is not supported Tags added: patch > 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#281348: marked as done (Segfault due to python-soya on AMD64 arch when running Slune)
Your message dated Mon, 31 Jul 2006 15:33:28 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#281348: fixed in soya 0.12-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: python-soya Version: 0.8.2-1 Severity: grave There isn't much to say, I try to run Slune on my AMD64 Sid machine, and it segfaults immediately, due to something in python-soya. I've sent an straced output to the maintainer, and can send it to anyone else who wants, but I won't post it here, it's about 5700 lines long. This is the entire output to a calling xterm: * Slune * Slune lives in /usr/share/games * Soya 3D * Using 8 bits stencil buffer * Soya 3D * version 0.8.1 * Using OpenGL 1.5.2 NVIDIA 66.29 * - renderer : GeForce FX 5900XT/AGP/SSE2 * - vendor : NVIDIA Corporation * - maximum number of lights: 8 * - maximum number of clip planes : 6 * - maximum number of texture units : 4 * - maximum texture size: 4096 pixels Segmentation fault A window pops up for a fraction of a second, then goes away as soon as the segfault hits. I'm using an nVidia geforce 5900, with the nvidia drivers, if that matters (I see the package depends on mesa...). -- System Information: Debian Release: 3.1 Architecture: amd64 (x86_64) Kernel: Linux 2.6.9.2004.11.08 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages python-soya depends on: ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an ii libfreetype6 2.1.7-2.2 FreeType 2 font engine, shared lib ii libgcc1 1:3.4.2-3 GCC support library ii libsdl1.2debian 1.2.7-10 Simple DirectMedia Layer ii libstdc++51:3.3.5-2 The GNU Standard C++ Library v3 ii python2.3.4-4An interactive high-level object-o ii python-editobj0.5.6-1Python object editor ii python-imaging-tk 1.1.4-3Python Imaging Library ImageTk Mod ii python-opengl 2.0.1.08-5 Python binding to OpenGL ii python2.3-opengl [python- 2.0.1.08-5 Python binding to OpenGL ii xlibmesa-gl [libgl1] 4.3.0.dfsg.1-8 Mesa 3D graphics library [XFree86] ii xlibmesa-glu [libglu1]4.3.0.dfsg.1-8 Mesa OpenGL utility library [XFree -- no debconf information --- End Message --- --- Begin Message --- Source: soya Source-Version: 0.12-1 We believe that the bug you reported is fixed in the latest version of soya, which is due to be installed in the Debian FTP archive: python-soya_0.12-1_i386.deb to pool/main/s/soya/python-soya_0.12-1_i386.deb soya_0.12-1.diff.gz to pool/main/s/soya/soya_0.12-1.diff.gz soya_0.12-1.dsc to pool/main/s/soya/soya_0.12-1.dsc soya_0.12.orig.tar.gz to pool/main/s/soya/soya_0.12.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. Marc Dequènes (Duck) <[EMAIL PROTECTED]> (supplier of updated soya package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 31 Jul 2006 22:28:50 +0200 Source: soya Binary: python-soya Architecture: source i386 Version: 0.12-1 Distribution: unstable Urgency: low Maintainer: Marc Dequènes (Duck) <[EMAIL PROTECTED]> Changed-By: Marc Dequènes (Duck) <[EMAIL PROTECTED]> Description: python-soya - high level 3D engine for Python Closes: 281348 325540 Changes: soya (0.12-1) unstable; urgency=low . * New upstream release: + fixed crashes on 64 bits architectures (thanks to the nice debug work of Vincent Fourmond) (Closes: #281348). + fixed a minor syntax warning (Closes: #325540). * Conflicts with incompatible versions of slune and balazar. Files: a5c5427f1da68351e5815558796f2090 946 python optional soya_0.12-1.dsc 256675d230927eee76911fb580898407 2614521 python optional soya_0.12.orig.tar.gz 59ce0b93b7ee4c91c0937b4d17679af8 5741 python optional soya_0.12-1.diff.gz cced4bfa56bf32d37ece815d928ad16b 1236166 python optional python-soya_0.12-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEznCTsc
Bug#380616: marked as done (beagle: Beagle version 0.2.7-1 uninstallable due to unmet dependency)
Your message dated Mon, 31 Jul 2006 15:32:41 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#380616: fixed in beagle 0.2.7-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: beagle Version: 0.2.6-2 Severity: grave Justification: renders package unusable Upon trying to upgrade Beagle from version 0.2.6-2 to version 0.2.7-1, the following error occurs: The following packages have unmet dependencies: beagle: Depends: libgmime2.1-cil (>= 2.2.1) but 2.1.19-1 is to be installed E: Broken packages -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages beagle depends on: ii adduser 3.95Add and remove users and groups ii bash 3.1-5 The GNU Bourne Again SHell ii libatk1.0-0 1.12.1-1The ATK accessibility toolkit ii libc62.3.6-16GNU C Library: Shared libraries ii libcairo21.2.0-3 The Cairo 2D vector graphics libra ii libexif120.6.13-4library to parse EXIF files ii libfontconfig1 2.3.2-7 generic font configuration library ii libgalago-cil0.3.2-4 CLI bindings for libgalago ii libgconf2.0-cil 2.8.3-1 CLI binding for GConf 2.12 ii libglade2.0-cil 2.8.3-1 CLI binding for the Glade librarie ii libglib2.0-0 2.10.3-3The GLib library of C routines ii libglib2.0-cil 2.8.3-1 CLI binding for the GLib utility l ii libgmime2.1-cil 2.1.19-1CLI binding for the MIME library, ii libgnome2.0-cil 2.8.3-1 CLI binding for GNOME 2.12 ii libgnomevfs2-0 2.14.2-1GNOME virtual file-system (runtime ii libgtk2.0-0 2.8.18-1The GTK+ graphical user interface ii libgtk2.0-cil2.8.3-1 CLI binding for the GTK+ toolkit 2 ii libmono-corlib1.0-cil1.1.13.8-1 Mono core library (1.0) ii libmono-sharpzip0.6-cil 1.1.13.8-1 Mono SharpZipLib library ii libmono-sharpzip0.84-cil 1.1.13.8-1 Mono SharpZipLib library ii libmono-sqlite1.0-cil1.1.13.8-1 Mono Sqlite library ii libmono-system-data1.0-cil 1.1.13.8-1 Mono System.Data library ii libmono-system-runtime1.0-ci 1.1.13.8-1 Mono System.Runtime library ii libmono-system-web1.0-cil1.1.13.8-1 Mono System.Web library ii libmono-system1.0-cil1.1.13.8-1 Mono System libraries (1.0) ii libmono0 1.1.13.8-1 libraries for the Mono JIT ii libmono1.0-cil 1.1.13.8-1 Mono libraries (1.0) ii libpango1.0-01.12.3-1+b1 Layout and rendering of internatio ii librsvg2-2 2.14.4-2SAX-based renderer library for SVG ii libsqlite0 2.8.16-1SQLite shared library ii libx11-6 2:1.0.0-7 X11 client-side library ii libxcursor1 1.1.5.2-5 X cursor management library ii libxext6 1:1.0.0-4 X11 miscellaneous extension librar ii libxfixes3 1:3.0.1.2-4 X11 miscellaneous 'fixes' extensio ii libxi6 1:1.0.0-5 X11 Input extension library ii libxinerama1 1:1.0.1-4 X11 Xinerama extension library ii libxrandr2 2:1.1.0.2-4 X11 RandR extension library ii libxrender1 1:0.9.0.2-4 X Rendering Extension client libra ii libxss1 1:1.0.1-4 X11 Screen Saver extension library ii mono-runtime 1.1.13.8-1 Mono runtime Versions of packages beagle recommends: ii poppler-utils 0.4.5-4.1 PDF utilitites (based on libpopple -- no debconf information --- End Message --- --- Begin Message --- Source: beagle Source-Version: 0.2.7-2 We believe that the bug you reported is fixed in the latest version of beagle, which is due to be installed in the Debian FTP archive: beagle-backend-evolution_0.2.7-2_all.deb to pool/main/b/beagle/beagle-backend-evolution_0.2.7-2_all.deb beagle-dev_0.2.7-2_i386.deb to pool/main/b/beagle/beagle-dev_0.2.7-2_i386.deb beagle_0.2.7-2.diff.gz to pool/main/b/beagle/beagle_0.2.7-2.diff.gz beagle_0.2.7-2.dsc to pool/main/b/beagle/beagle_0.2.7-2.dsc beagle_0.
Bug#313233: marked as done (slune: segfault on AMD64)
Your message dated Mon, 31 Jul 2006 15:33:28 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#281348: fixed in soya 0.12-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: slune Version: 1.0.7-1 Severity: normal slune dies with a segfault on AMD64: * Slune * Slune lives in /usr/share/games * Soya 3D * Using 8 bits stencil buffer * Soya 3D * version 0.9.2 * Using OpenGL 1.2 Mesa 4.0.4 * - renderer : Mesa DRI G400 20020221 AGP 1x * - vendor : VA Linux Systems Inc. * - maximum number of lights: 8 * - maximum number of clip planes : 6 * - maximum number of texture units : 2 * - maximum texture size: 256 pixels * Slune * (Psyco not found ; if you are using an x86 processor, * installing psyco can speed up Slune a little) Segmentation fault -- System Information: Debian Release: 3.1 Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages slune depends on: ii python2.3.5-2An interactive high-level object-o ii python-2play 0.1.7-1peer-to-peer network game engine ii python-openal 0.1.4-5port for Python of the OpenAL libr ii python-pyvorbis 1.3-1 A Python interface to the Ogg Vorb ii python-soya 0.9.2-1high level 3D engine for Python -- no debconf information --- End Message --- --- Begin Message --- Source: soya Source-Version: 0.12-1 We believe that the bug you reported is fixed in the latest version of soya, which is due to be installed in the Debian FTP archive: python-soya_0.12-1_i386.deb to pool/main/s/soya/python-soya_0.12-1_i386.deb soya_0.12-1.diff.gz to pool/main/s/soya/soya_0.12-1.diff.gz soya_0.12-1.dsc to pool/main/s/soya/soya_0.12-1.dsc soya_0.12.orig.tar.gz to pool/main/s/soya/soya_0.12.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. Marc Dequènes (Duck) <[EMAIL PROTECTED]> (supplier of updated soya package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 31 Jul 2006 22:28:50 +0200 Source: soya Binary: python-soya Architecture: source i386 Version: 0.12-1 Distribution: unstable Urgency: low Maintainer: Marc Dequènes (Duck) <[EMAIL PROTECTED]> Changed-By: Marc Dequènes (Duck) <[EMAIL PROTECTED]> Description: python-soya - high level 3D engine for Python Closes: 281348 325540 Changes: soya (0.12-1) unstable; urgency=low . * New upstream release: + fixed crashes on 64 bits architectures (thanks to the nice debug work of Vincent Fourmond) (Closes: #281348). + fixed a minor syntax warning (Closes: #325540). * Conflicts with incompatible versions of slune and balazar. Files: a5c5427f1da68351e5815558796f2090 946 python optional soya_0.12-1.dsc 256675d230927eee76911fb580898407 2614521 python optional soya_0.12.orig.tar.gz 59ce0b93b7ee4c91c0937b4d17679af8 5741 python optional soya_0.12-1.diff.gz cced4bfa56bf32d37ece815d928ad16b 1236166 python optional python-soya_0.12-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEznCTsczZcpAmcIYRAvBVAJ9kBvVKiyqGaNuwCbZnSH5AkVjk3QCgprg7 mB2OXd/HFOA+UobkjOgZ6dQ= =mLum -END PGP SIGNATURE- --- End Message ---
Processed: heartbeat-2: Local DoS due to world-writable shared memory [CVE-2006-3815]
Processing commands for [EMAIL PROTECTED]: > notfound 380289 2.0.6-1 Bug#380289: heartbeat-2: Local DoS due to world-writable shared memory [CVE-2006-3815] Bug marked as not found in version 2.0.6-1. (By the way, this Bug is currently marked as done.) > notfound 380289 2.0.6-0bpo1 Bug#380289: heartbeat-2: Local DoS due to world-writable shared memory [CVE-2006-3815] Bug marked as not found in version 2.0.6-0bpo1. (By the way, this Bug is currently marked as done.) > 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#380423: marked as done (Version 2.0.4, that fixes several security issues, was released)
Your message dated Tue, 1 Aug 2006 09:00:25 +0900 with message-id <[EMAIL PROTECTED]> and subject line Cheers has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: wordpress Version: 2.0.3-1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Wordpress announced release 2.0.4 and in the release note, there is something written about "several important security fixes", this version shall contain. Please update the Debian package. This report was initially set to 'grave', because I cannot find any information about the security issues. If you have more information, feel free to downgrade this report. Thanks for your work. Regards, Daniel - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.08060320 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages wordpress depends on: ii apache [httpd] 1.3.34-2versatile, high-performance HTTP s ii mysql-client-5.0 [virtual-my 5.0.22-3mysql database client binaries ii php4 4:4.4.2-1.1 server-side, HTML-embedded scripti ii php4-mysql 4:4.4.2-1.1 MySQL module for php4 wordpress recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEzCj8dg0kG0+YFBERAlACAJoCtF0X+czdb3Ehcj9GQnwK7DzRvQCfYgR6 iKf2vjx3RPsGGtSENOGQAfw= =UpVP -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Thanks for the bug report. I very quickly packaged the release before passing out from a million hour travelling ordeal from Korea to the UK. I couldn't find the changelog so this is one of those disconcerting, "I don't know what security bugs" are being fixed releases. Not cool. --- End Message ---
Processed: Re: Bug#380652: squid fails to start because of "Function not implemented" error
Processing commands for [EMAIL PROTECTED]: > severity 380652 important Bug#380652: squid fails to start because of "Function not implemented" error Severity set to `important' from `grave' > retitle 380652 squid 2.6 needs epoll() support which is not in kernel Bug#380652: squid fails to start because of "Function not implemented" error Changed Bug title. > 2.4.x Unknown command or malformed arguments to command. > retitle 377697 squid 2.6 compiled with epoll() support does not start Bug#377697: New version of squid hangs at startup Changed Bug title. > with kernel <= 2.6.x Unknown command or malformed arguments to command. > merge 380652 377697 Bug#377697: squid 2.6 compiled with epoll() support does not start Bug#380652: squid 2.6 needs epoll() support which is not in kernel Merged 377697 380652. > 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#380652: squid fails to start because of "Function not implemented" error
severity 380652 important retitle 380652 squid 2.6 needs epoll() support which is not in kernel 2.4.x retitle 377697 squid 2.6 compiled with epoll() support does not start with kernel <= 2.6.x merge 380652 377697 thanks Hi Ambrose, squid 2.6.STABLE is compiled with epoll() support turned on by default. The epoll() functions are supported only in kernels 2.6.x. Since etch will ship with 2.6 as default and 2.4 will not be supported anymore, squid will carry a notice in README.Debian stating that kernels previous than 2.6.x are not supported anymore. This bug was also already opened as 377697. I'm merging your reported with the previous one. Please check the bug reports before opening a new bug, next time. Regards, -- Luigi Gangitano -- <[EMAIL PROTECTED]> -- <[EMAIL PROTECTED]> GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618 924C 0C26 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: your mail
Processing commands for [EMAIL PROTECTED]: > tag 378571 +patch Bug#378571: courier-authdaemon: socket directory should have 750 permissions Tags were: security Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#370169: marked as done (lilo package don't finish this setting up)
Your message dated Tue, 1 Aug 2006 00:25:00 +0200 with message-id <[EMAIL PROTECTED]> and subject line non-bug? has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: lilo Version: 1:22.6.1-7+b1 Severity: normal # apt-get dist-upgrade Setting up lilo (22.6.1-7+b1) ... cp: too many input files dpkg: error processing lilo (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: lilo E: Sub-process /usr/bin/dpkg returned an error code (1) -- 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.4 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages lilo depends on: ii debconf 1.5.1 Debian configuration management sy ii libc62.3.6-7 GNU C Library: Shared libraries ii libdevmapper1.02 2:1.02.05-2 The Linux Kernel Device Mapper use lilo recommends no packages. -- debconf information: lilo/bad_bitmap: lilo/upgrade: lilo/runme: false * lilo/new-config: --- End Message --- --- Begin Message --- * Martín Ferrari [Mon, 31 Jul 2006 14:17:16 -0300]: > After reading this bug report, I looked into lilo.postinst, and the > only use of "cp" is at: >cp /usr/share/lilo/*.bmp /boot > If this reports "cp: too many input files", it should be some problem > with that directory on the user's machine. > As the user hasn't replied in the last 40 days, I suggest closing this RC > bug. I agree with this, let's close it. -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org The true teacher defends his pupils against his own personal influence. -- Amos Bronson Alcott --- End Message ---
Bug#378346: gnucash crash on alpha
Hi Steve; you said a bit ago that you were going to try to rebuild libgail.so so that a more useful backtrace from the gnucash crash on alpha could be obtained. Should I keep on waiting for this, or proceed on a different tack? I think that upstream would be happy to take the lead on debugging it, since it's a pretty serious failure, but they would need access to an alpha machine with all the build dependencies available. Gnucash 2.0.1 has been released this week, so it's also possible that this will make the bug go away on its own, though that seems pretty unlikely. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#378571: courier-authdaemon: Patch
Package: courier-authdaemon Followup-For: Bug #378571 I couldn't find out why this has changed since sarge, where it shipped with 770 daemon:daemon permissions. Also, as the submitter points, upstreams ships with 750, as can be seen in Makefile.*: chmod 750 $(DESTDIR)@authdaemonvar@ I attach the (trivial) patch to change the permissions as it used to be. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8) --- courier-authlib-0.58/debian/permissions 2006-07-31 13:09:21.0 -0300 +++ courier-authlib-0.58/debian/permissions.new 2006-07-31 18:07:55.0 -0300 @@ -3,5 +3,5 @@ /etc/courier/authmysqlrc 660 daemon daemon /etc/courier/authdaemonrc 660 daemon daemon /var/run/courier 755 daemon daemon -/var/run/courier/authdaemon 755 daemon daemon +/var/run/courier/authdaemon 750 daemon daemon
Bug#380658: [Pkg-openldap-devel] Bug#380658: slapd: Package upgrade hangs
Hi Steve, Steve Langasek schrieb: >>When upgrading from 2.3.24-1 to 2.3.24-2 the package installation hangs. >>I have to press Ctrl+C. Apt-get asked me to install a new version of >>slapd.conf which I did not. Maybe this is related to this behaviour. > > > Are you running nss_ldap on this system? If so, please see bug #379728. yes, disabling nss_ldap resolved the problem. Thanks for the hint. Greetings Roland signature.asc Description: OpenPGP digital signature
Bug#380233: [pkg-ntp-maintainers] Bug#380233: package transition leaves a mess of old ntp-server and ntp-simple stuff, including dangerous purge possibilities
On Sun, Jul 30, 2006 at 10:56:11PM +0100, Max Bowsher wrote: > Peter Eisentraut wrote: > > The init script might be a bit of an issue because you might have two > > init scripts trying to start the same program, but there are interlocks > > that should prevent that. > > The post-upgrade state is exactly that - two init scripts for the same > program, both active. Even if there are interlocks, it is still messy. I think the only thing we can do about that is using something like "update-rc.d -f ntp-server remove" in the postinst. And I'm not really sure that's a good idea. > >> Additionally, if an incautious sysadmin was to purge the old > >> packages, then the old ntp-simple postinst script will cause serious > >> damage to the existing ntp installation, in particular, deleting the > >> 'ntp' user, as well as deleting the /var/lib/ntp/ and > >> /var/log/ntpstats/ directories. > > > > My answer to that is that you shouldn't randomly purge packages at > > random times. > > What then, _is_ the proper way to purge packages? I haven't found any > way to preview the results of a purge without peeking inside > /var/lib/dpkg/info/ . > > > We could, however, try to document a sequence of steps > > to clean up your system after an upgrade. Basically, if you restart > > ntp after you purge ntp-server, you should be fine. > > > > The ntp-simple and ntp-refclock packages can be safely removed at any > > time I believe. > > No, not at all. As I said, the ntp-simple postinst deletes the 'ntp' > user account during purge, which the new ntp packages still use. Note that the /etc/init.d/ntp script creates those again. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380537: marked as done (slapd: Fails to start after upgrade to from 2.3.23 to 2.3.24)
Your message dated Mon, 31 Jul 2006 12:16:53 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380537: [Pkg-openldap-devel] Bug#380537: slapd: Fails to
start after upgrade to from 2.3.23 to 2.3.24
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: slapd
Version: 2.3.24-2
Severity: grave
Justification: renders package unusable
Hello
After upgrading from 2.3.23 to 2.3.24, slapd refuses to start:
[EMAIL PROTECTED]:~$ /etc/init.d/slapd start
No configuration file was found for slapd at /etc/ldap/slapd.conf.
If you have moved the slapd configuration file please modify
/etc/default/slapd to reflect this. If you chose to not
configure slapd during installation then you need to do so
prior to attempting to start slapd.
slapd.conf is owned by root.root, and chown-ing it to root.openldap fixes
the problem. Maybe this should be done by the upgrade script?
Peter.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-beyond2.1-mh4
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages slapd depends on:
ii adduser 3.95 Add and remove users and groups
ii coreutils 5.97-1 The GNU core utilities
ii debconf [debconf-2.0] 1.5.3Debian configuration management sy
ii libc6 2.3.6-16 GNU C Library: Shared libraries
ii libdb4.24.2.52+dfsg-1Berkeley v4.2 Database Libraries [
ii libiodbc2 3.52.4-3 iODBC Driver Manager
ii libldap-2.3-0 2.3.24-2 OpenLDAP libraries
ii libltdl31.5.22-4 A system independent dlopen wrappe
ii libperl5.8 5.8.8-6 Shared Perl library
ii libsasl22.1.19.dfsg1-0.2 Authentication abstraction library
ii libslp1 1.2.1-5 OpenSLP libraries
ii libssl0.9.8 0.9.8b-2 SSL shared libraries
ii libwrap07.6.dbs-9Wietse Venema's TCP wrappers libra
ii perl [libmime-base64-pe 5.8.8-6 Larry Wall's Practical Extraction
ii psmisc 22.2-1 Utilities that use the proc filesy
Versions of packages slapd recommends:
pn db4.2-util (no description available)
ii libsasl2-modules2.1.19.dfsg1-0.2 Pluggable Authentication Modules f
-- debconf information:
slapd/fix_directory: true
* shared/organization: localdomain
slapd/upgrade_slapcat_failure:
slapd/backend: BDB
* slapd/allow_ldap_v2: false
slapd/no_configuration: false
slapd/move_old_database: true
slapd/suffix_change: false
slapd/slave_databases_require_updateref:
* slapd/dump_database_destdir: /var/backups/slapd-VERSION
slapd/autoconf_modules: true
* slapd/domain: poggs.net
slapd/password_mismatch:
slapd/invalid_config: true
slapd/upgrade_slapadd_failure:
* slapd/dump_database: always
slapd/migrate_ldbm_to_bdb: false
slapd/purge_database: false
slapd/admin:
--- End Message ---
--- Begin Message ---
On Mon, Jul 31, 2006 at 07:43:04PM +0100, Peter Hicks wrote:
> Torsten Landschoff wrote:
> > Hmm, that's weird because the main function in Debian's slapd contains
> > code that reads like this:
> >
> > if ( read_config( configfile, configdir ) != 0 ) {
> > /* error handling */
> > }
> > if ( username != NULL || groupname != NULL ) {
> > slap_init_user( username, groupname );
> > }
> >
> > Therefore this error should not happen.
> I can't reproduce the problem any more - I purged and reinstalled slapd
> yesterday - it was in a bit of a state after a botched install of another
> package.
> False alarm, I believe the bug can be closed as I can't reproduce it any more.
> Apologies :(
Ok, closing the report. Thanks for following up.
--
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
--- End Message ---
Bug#380658: [Pkg-openldap-devel] Bug#380658: slapd: Package upgrade hangs
On Mon, Jul 31, 2006 at 06:49:12PM +0200, Roland Gruber wrote: > Package: slapd > Version: 2.3.24-2 > Severity: grave > Justification: renders package unusable > When upgrading from 2.3.24-1 to 2.3.24-2 the package installation hangs. > I have to press Ctrl+C. Apt-get asked me to install a new version of > slapd.conf which I did not. Maybe this is related to this behaviour. Are you running nss_ldap on this system? If so, please see bug #379728. -- 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/
Bug#380537: [Pkg-openldap-devel] Bug#380537: slapd: Fails to start after upgrade to from 2.3.23 to 2.3.24
Hi Torsten
Torsten Landschoff wrote:
> Hmm, that's weird because the main function in Debian's slapd contains
> code that reads like this:
>
> if ( read_config( configfile, configdir ) != 0 ) {
> /* error handling */
> }
> if ( username != NULL || groupname != NULL ) {
> slap_init_user( username, groupname );
> }
>
> Therefore this error should not happen.
I can't reproduce the problem any more - I purged and reinstalled slapd
yesterday - it was in a bit of a state after a botched install of another
package.
False alarm, I believe the bug can be closed as I can't reproduce it any more.
Apologies :(
Peter.
--
Peter Hicks | e: [EMAIL PROTECTED] | g: 0xE7C839F4 | w: www.poggs.com
A: Because it destroys the flow of the conversation
Q: Why is top-posting bad?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#377262: python-parted NMU.
Colin Watson wrote: > On Wed, Jul 12, 2006 at 03:58:01PM +, Gustavo Franco wrote: >> python-parted (0.11.3) unstable; urgency=low >> >> * Non-maintainer upload. >> * debian/control: >>- Build-Depends on libparted1.7. (Closes: #374209) >> * Merge new parted API patch by Colin Watson. (Closes: #284081, #377262) >>[debian/patches/01_newapi.dpatch] >> >> -- Gustavo Franco <[EMAIL PROTECTED]> Wed, 12 Jul 2006 12:01:35 -0300 > > I understand there were a few API changes in libparted 1.7 as well. Have > you looked at wrapping these at all? Unfortunately, not yet. I think it would be better decide if the current implementation will be kept in Debian or it will be transitioned to the other. python-parted has 5 RC bugs and isn't testing so i've other priorities for the moment. Feedback is still appreciated though. regards, Gustavo Franco - <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#380619: cupsys: does not start at all
Processing commands for [EMAIL PROTECTED]: > severity 380619 serious Bug#380619: cupsys: does not start at all Severity set to `serious' from `normal' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 380571 is normal
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.20 > severity 380571 normal Bug#380571: linux-uvc - FTBFS: Nothing to be done for `binary-arch'. Severity set to `normal' from `serious' > 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#380663: Cupsys starts when first installed, but silently exits and will never run again
Package: cupsys Version: 1.2.1-3 Severity: grave Twice, now, I've had the experience of having to not only remove, but purge cupsys and reinstall it in order to get my bog-standard HP Laserjet to work. Both times, everything was fine immediately after the reinstall, but when I tried to print a few days later, nothing happened. lpq reports "lpq: Unable to connect to server". "/etc/init.d/cupsys restart" returns no visible error, but lpq still says it can't connect to server and ps reports no cupsys process. And there's NOTHING in error_log. Literally, it's an empty file. Nothing in /var/log/messages either. No program should ever, ever fail silently. I really do NOT want to have to reinstall CUPS every time I need to print. Just in case it helps: NewPicking:/home/carlf# lsof -i TCP:631 NewPicking:/home/carlf# (That's after trying "/etc/init.d/cupsys start".) -- 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-k7 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages cupsys depends on: ii adduser 3.95Add and remove users and groups ii debconf [debconf-2.0]1.5.2 Debian configuration management sy ii gs-esp 8.15.1.dfsg.1-2 The Ghostscript PostScript interpr ii libacl1 2.2.39-1Access control list shared library ii libc62.3.6-15GNU C Library: Shared libraries ii libcupsimage21.2.1-3 Common UNIX Printing System(tm) - ii libcupsys2 1.2.1-3 Common UNIX Printing System(tm) - ii libdbus-1-2 0.62-4 simple interprocess messaging syst ii libgnutls13 1.4.1-1 the GNU TLS library - runtime libr ii libldap2 2.1.30-13+b1OpenLDAP libraries ii libpam0g 0.79-3.1Pluggable Authentication Modules l ii libpaper11.1.19 Library for handling paper charact ii libslp1 1.2.1-5 OpenSLP libraries ii lsb-base 3.1-10 Linux Standard Base 3.1 init scrip ii patch2.5.9-4 Apply a diff file to an original ii perl-modules 5.8.8-4 Core Perl modules ii procps 1:3.2.7-2 /proc file system utilities ii xpdf-utils [poppler-util 3.01-9 Portable Document Format (PDF) sui ii zlib1g 1:1.2.3-13 compression library - runtime Versions of packages cupsys recommends: ii cupsys-client 1.2.1-3 Common UNIX Printing System(tm) - ii foomatic-filters3.0.2-20060712-1 linuxprinting.org printer support ii smbclient 3.0.22-1 a LanManager-like simple client fo -- debconf information: cupsys/raw-print: true cupsys/backend: ipp, lpd, parallel, socket, usb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380635: marked as done (libsdl1.2debian-all: Packageuninstallable)
Your message dated Mon, 31 Jul 2006 11:10:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#380635: libsdl1.2debian-all: Packageuninstallable has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: libsdl1.2debian-all Severity: grave Justification: renders package unusable Hi, libdirectfb-0.9-24 has been removed from unstable anb sdl need to be rebuild : # apt-get install libsdl1.2debian-all Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: libsdl1.2debian-all: Depends: libdirectfb-0.9-24 but it is not installable E: Broken packages Christian -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (900, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.1 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) --- End Message --- --- Begin Message --- On Mon, Jul 31, 2006 at 03:36:31PM +0200, Christian Marillat wrote: > Package: libsdl1.2debian-all > Severity: grave > Justification: renders package unusable > libdirectfb-0.9-24 has been removed from unstable anb sdl need to be rebuild : This rebuild has already been scheduled by way of binNMU. -- 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/ --- End Message ---
Processed: your mail
Processing commands for [EMAIL PROTECTED]: > merge 380115 380318 Bug#380115: xmms shows file selection box, but doesn't say a beep Bug#380318: xmms is missing some libraries Bug#380321: XMMS loads no output plugins Merged 380115 380318 380321. > 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#380659: marked as done (directfb: FTBFS on powerpc)
Your message dated Mon, 31 Jul 2006 20:02:13 +0200 with message-id <[EMAIL PROTECTED]> and subject line BR crossed with upload of fixed packages - closing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: directfb Version: 0.9.25.1-2 Severity: serious http://buildd.debian.org/fetch.php?pkg=directfb&arch=powerpc&ver=0.9.25.1-2&stamp=1153861344&file=log Build fails with: ../../../lib/direct/system.c: In function 'direct_pagesize': ../../../lib/direct/system.c:64: error: 'PAGE_SIZE' undeclared (first use in this function) pgpQ2YafOi5ad.pgp Description: PGP signature --- End Message --- --- Begin Message --- Version: 0.9.25.1-3 --- End Message ---
Processed: Bug#379714: libxslt1-dev should depend on libgcrypt11-dev, libgpg-error-dev
Processing commands for [EMAIL PROTECTED]: > retitle 379714 libxslt1-dev should depend on libgcrypt11-dev, libgpg-error-dev Bug#379714: modxslt: FTBFS: libtool: link: `/usr/lib/libgcrypt.la' is not a valid libtool archive Changed Bug title. > reassign 379714 libxslt1-dev 1.1.17-2 Bug#379714: libxslt1-dev should depend on libgcrypt11-dev, libgpg-error-dev Bug reassigned from package `modxslt' to `libxslt1-dev'. > 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#379714: libxslt1-dev should depend on libgcrypt11-dev, libgpg-error-dev
retitle 379714 libxslt1-dev should depend on libgcrypt11-dev, libgpg-error-dev reassign 379714 libxslt1-dev 1.1.17-2 thanks Julien Danjou <[EMAIL PROTECTED]> writes: [...] >> creating libmodxslt0.la >> /bin/sed: can't read /usr/lib/libgcrypt.la: No such file or directory >> libtool: link: `/usr/lib/libgcrypt.la' is not a valid libtool archive >> make[1]: *** [libmodxslt0.la] Error 1 [...] This is caused by dangling references to libgcrypt.la and libgpg-error.la in libexslt.la. Please either remove libexslt.la, or make libxslt1-dev depend on libgcrypt11-dev and libgpg-error-dev. Thanks, Matej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380318: not fixed in Version 1:1.2.10+20060729-1
Hi, I'm afraid the bug isn't closed in version 1:1.2.10+20060729-1. bhaal:archives# dpkg -I xmms_1%3a1.2.10+20060729-1_amd64.deb new debian package, version 2.0. size 2231656 bytes: control archive= 4375 bytes. 1144 bytes,26 lines control 8161 bytes, 117 lines md5sums 469 bytes,17 lines * postinst #!/bin/sh 408 bytes,13 lines * postrm #!/bin/sh 36 bytes, 1 lines shlibs Package: xmms Version: 1:1.2.10+20060729-1 Section: sound Priority: optional Architecture: amd64 Depends: libc6 (>= 2.3.5-1), libglib1.2 (>= 1.2.0), libgtk1.2 (>= 1.2.10-4), libice6, libsm6, libx11-6, libxext6, libxi6, libxxf86vm1 Recommends: unzip Installed-Size: 6992 Maintainer: Daniel Baumann <[EMAIL PROTECTED]> [description snipped] bhaal:archives# dpkg --contents xmms_1%3a1.2.10+20060729-1_amd64.deb | grep so$ -rw-r--r-- root/root 13400 2006-07-29 12:55 ./usr/lib/xmms/Input/libwav.so -rw-r--r-- root/root 9080 2006-07-29 12:55 ./usr/lib/xmms/Input/libtonegen.so Sorry, I don't have time to take look at the source package right now, so I can't supply more information/a better bug report... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380658: slapd: Package upgrade hangs
Package: slapd Version: 2.3.24-2 Severity: grave Justification: renders package unusable When upgrading from 2.3.24-1 to 2.3.24-2 the package installation hangs. I have to press Ctrl+C. Apt-get asked me to install a new version of slapd.conf which I did not. Maybe this is related to this behaviour. -- 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.17.1 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages slapd depends on: ii adduser 3.95 Add and remove users and groups ii coreutils 5.96-5 The GNU core utilities ii debconf [debconf-2.0] 1.5.2Debian configuration management sy ii libc6 2.3.6-15 GNU C Library: Shared libraries ii libdb4.24.2.52-23.1 Berkeley v4.2 Database Libraries [ ii libiodbc2 3.52.4-3 iODBC Driver Manager ii libldap-2.3-0 2.3.24-2 OpenLDAP libraries ii libltdl31.5.22-4 A system independent dlopen wrappe ii libperl5.8 5.8.8-4 Shared Perl library ii libsasl22.1.19.dfsg1-0.2 Authentication abstraction library ii libslp1 1.2.1-5 OpenSLP libraries ii libssl0.9.8 0.9.8b-2 SSL shared libraries ii libwrap07.6.dbs-9Wietse Venema's TCP wrappers libra ii perl [libmime-base64-pe 5.8.8-4 Larry Wall's Practical Extraction ii psmisc 22.2-1 Utilities that use the proc filesy Versions of packages slapd recommends: ii db4.2-util 4.2.52-23.1 Berkeley v4.2 Database Utilities ii libsasl2-modules2.1.19.dfsg1-0.2 Pluggable Authentication Modules f -- debconf information: slapd/fix_directory: true * shared/organization: test slapd/upgrade_slapcat_failure: slapd/backend: BDB * slapd/allow_ldap_v2: true slapd/no_configuration: false slapd/move_old_database: true slapd/suffix_change: false slapd/invalid_suffix: false slapd/slave_databases_require_updateref: * slapd/dump_database_destdir: /var/backups/slapd-VERSION slapd/autoconf_modules: true * slapd/domain: o=test.c=de slapd/password_mismatch: slapd/invalid_config: true slapd/upgrade_slapadd_failure: * slapd/dump_database: when needed slapd/migrate_ldbm_to_bdb: false slapd/purge_database: false slapd/admin: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: merging 378498 379264
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.20 > merge 378498 379264 Bug#378498: Needs recompilation because of ghci 6.4.2 Bug#379264: FTBFS: needs to update for new ghc6 Merged 378498 379264. > 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#380659: directfb: FTBFS on powerpc
Package: directfb Version: 0.9.25.1-2 Severity: serious http://buildd.debian.org/fetch.php?pkg=directfb&arch=powerpc&ver=0.9.25.1-2&stamp=1153861344&file=log Build fails with: ../../../lib/direct/system.c: In function 'direct_pagesize': ../../../lib/direct/system.c:64: error: 'PAGE_SIZE' undeclared (first use in this function) pgpj5BGlq2TiK.pgp Description: PGP signature
Bug#376979: democracyplayer: still present in 0.8.5-1
Hi Ryan, On Thu, Jul 27, 2006 at 06:50:30PM -0500, Ryan Nowakowski wrote: > On Fri, Jul 28, 2006 at 12:03:48AM +0200, Uwe Hermann wrote: > > Hi Ryan, > > > > On Thu, Jul 27, 2006 at 03:07:51PM -0500, Ryan Nowakowski wrote: > > > > Why are your movies in ~/Movies/Democracy? Are you on a Mac? The Debian > > > > package uses ~/.democracy/Movies as the movie directory... > > > > > > That's where democracy put them when I was running the package from > > > http://www.getdemocracy.com > > > > The package is no longer available from > > http://www.getdemocracy.com/downloads/debian.php as it has entered > > unstable a while ago. Did you accidentally get the Ubuntu version from > > there? > > I don't think so: > > [EMAIL PROTECTED]:~$ export COLUMNS=200; dpkg -l democracyplayer > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed > |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: > uppercase=bad) > ||/ Name Version > Description > +++--- > ii democracyplayer 0.8.5-1 > GTK+ based RSS video aggregator > [EMAIL PROTECTED]:~$ apt-cache show democracyplayer > Package: democracyplayer > Priority: optional > Section: net > Installed-Size: 2772 > Maintainer: Uwe Hermann <[EMAIL PROTECTED]> > Architecture: i386 > Version: 0.8.5-1 > Depends: libatk1.0-0 (>= 1.12.1), libboost-python1.33.1, libc6 (>= 2.3.6-6), > libcairo2 (>= 1.2.0), libfontconfig1 (>= 2.3.0), libgcc1 (>= 1:4.1.0), > libglib2.0-0 (>= 2.10.0), libgtk2.0-0 (>= 2.8.0), libnspr4-0d, libpango1.0-0 > (>= 1.12.3), libstdc++6 (>= 4.1.0), libx11-6, libxcursor1 (>> 1.1.2), > libxext6, libxfixes3, libxi6, libxine1 (>= 1.1.1+cvs20060621-1), > libxinerama1, libxrandr2, libxrender1, libxul0d, zlib1g (>= 1:1.2.1), > python2.4, python (>= 2.3), python (<< 3), python2.4-gtk2, python2.4-gnome2, > python2.4-gnome2-extras, python2.4-glade2, democracyplayer-data (>= 0.8.5-1) > Suggests: ttf-bitstream-vera > Filename: pool/main/d/democracyplayer/democracyplayer_0.8.5-1_i386.deb > Size: 494394 > MD5sum: ee7e7dc63004399309a3c611bbf6806b > SHA1: c5ae233805cc2102d4c87fb72348a9aa9cb6b70d > SHA256: 5784562ce17ab87bf04360a0c78e043db57a75ad17dec1e6ceb33b9f795deb1d > Description: GTK+ based RSS video aggregator > Democracy Player is a platform for Internet television and video. > It allows you to download and watch videos from RSS feeds (including > podcasts, video blogs, and BitTorrent feeds). > > > Also, the packages I built did use ~/.democracy/Movies quite from the > > beginning, not sure what happened here... > > Hrmm... maybe I configured it to explicitly put stuff in my Movies > directory. I don't remember. > > > Anyways, please try 'dpkg --purge democracyplayer democracyplayer-data' > > and then 'apt-get update && apt-get install democracyplayer', maybe > > that helps... > > Didn't help. > > > > > > ii libnspr4-0d 1.8.0.4-1 NetScape Portable > > > > > Runtime Library > > > > [...] > > > > > ii libxul0d 1.8.0.4-2 Gecko engine library > > > > > > > > This is a bit odd - why is one of them 1.8.0.4-1 and the other > > > > 1.8.0.4-2? They should usually both have the same version, I think. > > > > > > That sounds like a package dependency problem. If they should be the > > > same version then whatever package requires them should specify the same > > > version for both. > > > > Good point. Maybe I should fix the dependencies in order to force at > > least xulrunner >= 1.8.0.4-2 and gnome-python-extras >= 2.14.0-2 > > (which switched to xulrunner in that version). > > > > Which version of gnome-python-extras do you have? > > I assume you mean python2.4-gnome2-extras: > [EMAIL PROTECTED]:~$ dpkg -l python2.4-gnome2-extras > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed > |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: > uppercase=bad) > ||/ Name Version > Description > +++--- > ii python2.4-gnome2-extras 2.12.1-3 > Python bindings for the GNOME desktop environment Ah, yes, gnome-python-extras is the source package, python2.4-gnome2-extras is one of the binary packages. Anyways, as far as I can see python2.4-gnome2-extras has been renamed to python-gnome2-extras, and the version (of python2.4
Bug#374477: lilo: patch
Package: lilo Version: 1:22.6.1-7+b1 Followup-For: Bug #374477 Patch to use makedev instead of mknod -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8) Versions of packages lilo depends on: ii debconf 1.5.2 Debian configuration management sy ii libc62.3.6-15GNU C Library: Shared libraries ii libdevmapper1.02 2:1.02.07-1 The Linux Kernel Device Mapper use lilo recommends no packages. -- debconf information excluded --- lilo-22.6.1/debian/lilo.postinst2006-07-31 13:45:25.0 -0300 +++ lilo-22.6.1/debian/lilo.postinst.new2006-07-31 13:42:51.0 -0300 @@ -52,13 +52,7 @@ # Create the missing devices echo -n "Creating network block devices... " pushd /dev > /dev/null - i=0 - while [ $i != 128 ]; do - if [ ! -b nbd$i ]; then - /bin/mknod nbd$i b 43 $i - fi - i=$(($i+1)) - done + ./MAKEDEV nb popd > /dev/null echo "done." fi
Bug#370169: non-bug?
After reading this bug report, I looked into lilo.postinst, and the only use of "cp" is at: cp /usr/share/lilo/*.bmp /boot If this reports "cp: too many input files", it should be some problem with that directory on the user's machine. As the user hasn't replied in the last 40 days, I suggest closing this RC bug. -- Martín Ferrari
Processed: your mail
Processing commands for [EMAIL PROTECTED]: > tag 374477 +patch Bug#374477: lilo: creates devices in postinstall with mknod not MAKEDEV There were no tags set. Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#376812: libglide2: Reproducible segmentation fault with Voodoo2
Processing commands for [EMAIL PROTECTED]: > severity 376812 grave Bug#376812: libglide2: Reproducible segmentation fault with Voodoo2 Severity set to `grave' from `important' > 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#276989: marked as done (kernel-patch-uml does not appear to be in a releasable state for sarge)
Your message dated Mon, 31 Jul 2006 19:04:33 +0200 with message-id <[EMAIL PROTECTED]> and subject line kernel-patch-uml has been removed, closing outstanding 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) --- Begin Message --- Package: kernel-patch-uml Version: 20040824-1 Severity: serious Justification: or in the maintainer's opinion makes the package unsuitable for release mdz: off-topic, but while I have you ... :-) Does the kernel-patch-uml package work with kernels newer than the ones currently suggested? vorlon: perhaps, perhaps not Heh. From a release standpoint, how should k-p-uml be handled? vorlon: honestly? it wouldn't be entirely unreasonable to remove it from sarge UML hasn't worked properly on Debian for months I understand this to mean that kernel-patch-uml (and it's reverse-build-dependencies, such as user-mode-linux) should be removed from sarge. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.7-1-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 --- End Message --- --- Begin Message --- Hello, as the subject says, kernel-patch-uml has been removed from the repository as UML support is included in upstream kernels now. After some examination I decided the bugs submitted to it don't apply anymore or are obsolete WRT to current user-mode-linux kernel packages. If you disagree feel free to discuss on the mailing list at [EMAIL PROTECTED] about the issue. Thanks PS: sorry Matt ;) -- mattia :wq! signature.asc Description: Digital signature --- End Message ---
Bug#270992: marked as done (kernel-patch-powerpc-2.4.26: 2.4.26 powerpc package is scheduled for removal, see 2.4.27 package for bug reports.)
Your message dated Mon, 31 Jul 2006 19:03:19 +0200 with message-id <[EMAIL PROTECTED]> and subject line old 2.4 kernel bug has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: kernel-patch-powerpc-2.4.26 Version: 2.4.26-1 Severity: critical The 2.4.26 powerpc kernels have been scheduled for removal from sid/sarge as soon as the ftp-master process the bug report asking for their removal (#270989). This is a placeholder bug to redirect users/bugreporters to the kernel-patch-powerpc-2.4.27 package. Friendly, Sven Luther -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 2.6.8-powerpc Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] -- no debconf information --- End Message --- --- Begin Message --- dear bug subitters, thanks for your bug report. Newest Debian unstable ships much newer linux 2.6 kernels. So either your bug repot got solved or due to new packageing is no longer relevant. therefor closing. if you still experience the mentioned problem, don't hesitate to write back and the report will be reopened. you might want to test out the daily builds of the debian installer: http://www.debian.org/devel/debian-installer/ the next beta 3 installer for Debian Etch is expected soon. :) thanks for your feedback. best regards -- maks --- End Message ---
Bug#358696: This is dangerous, please make it default to disabled
On Fri, 28 Jul 2006, Daniel Richard G. wrote: > On Fri, 2006 Jul 28 16:12:35 -0300, Henrique de Moraes Holschuh wrote: > > There is no tradeoff without the hack, and the hack is only needed in > > hardware unsuitable for UPS management. Thus, it must be optional. It is > > dangerous to data and the hardware, so it should not be the default. > > Define "(un)suitable for UPS management." Does this definition include > most people's desktop systems? Suitable for UPS management: Load: Powers up when AC returns Can be informed that it must shutdown by the UPS (through NUT). UPS: Does delayed load shutdown upon shutdown command Does not power up the load before it has enough charge to do a delayed shutdown, plus safety margin. Always power-cycles the load after a shutdown command is ACK'ed to the controlling host. Even if AC returns, and it doesn't need to shutdown anymore. Communicates the host when battery charge is below a certain threshold, so that it can shutdown safely. Powers up the load if the batteries have enough charge, and an AC cycle happens while the load is offline. Powers up the load after a timer expires, if no AC cycles happen AND the load was broght offline by an explicit delayed shutdown command. Anything else is unsuitable. Any PC97 desktop should be suitable for proper UPS management. And just FYI, PC97 requires WoL on all ethernet devices, not that you need WoL for a proper UPS setup, but you somehow got the idea that WoL was a server-grade feature... > > You have transient responses to power cuts. Watch in an osciloscope, > > computer hardware is not a resistive load. > > No, but any decent power supply will present a load pretty close to it, Only ones with PFC. > production server-room environments.) If someone's got a rack setup where a > UPS power cutoff will fry everything, they've got a much bigger problem > than what we're discussing here. Yes. > number of machines connected, but large numbers of machines connected are > not exactly a typical scenario. No, but your hard-drive doing emergency unloads is a typical scenario, and desktop HDs don't like those unloads *at* *all*. Do not do it (and as I already said, the only proper way to know the HD heads are unloaded requires kernel cooperation, and it is NOT done by userspace currently). I know you were under the mistaken impression that we could guarantee all HD heads were unloaded in userspace, and before halt runs. We not only cannot do it, we also do not *attempt* to do it. The only thing in Debian initscripts that really tries to take care of HD head unloads is the halt command. You can, of course, try to make sure hdparm was run and actually uloaded all heads for your particular configuration, but it is not an acceptable default, because we cannot get it right every time. So implement it as an admin-enabled, admin-configured option by all means. But *not* as a default. > > > All of which can be done (and already is, I believe). The only thing that > > > the system is doing while waiting for poweroff is "sleep 15m; > > > reboot"---no > > > disks need to be spinning for that. > > > > If you did not call halt, plus told the kernel to shutdown the devices, no, > > it was *not* done. > > > > And the kernel is the *only* thing that really knows how to properly > > powerdown the devices. Currently, we cannot ask it to do so from userspace > > easily, and if we did, we could not access the disks anymore for example. > > We have "hdparm -Y". We can't access the disk after that, but we shouldn't > need to. What more shutdown magic do you need on a hard disk that is not > spinning? None. If the disk spun down, but hdparm doesn't work for all disks. And we cannot reliably spin down all disks and uload heads from userspace, for all possible configurations. Thus, anything that relies on this cannot be made a default. > If you're talking about a flaky hardware RAID array where you can't stop SCSI plus all software RAID arrays. > > The issue is how the initscript behaves if the NUT shutdown command doesn't > > kill everything to kingdon come in 5 seconds. In fact, a proper UPS is > > going to be programmed to actually *delay* the powerdown load command for > > enough time to allow the load to try to powerdown for real by itself. > > Assuming things are as I had in my patch, the idea is to have all machines > connected to a given UPS configured with a similar wait-until-poweroff- > else-reboot time (if they don't shutdown straightaway). The bad thing in your patch is that the maintainer made it non-optional, and the default. I understand it will not be a default an
Bug#380657: linux-ntfs: FTBFS on alpha
Package: linux-ntfs Version: 1.13.1-2 Severity: serious http://buildd.debian.org/fetch.php?pkg=linux-ntfs&arch=alpha&ver=1.13.1-2&stamp=1153789838&file=log Build fails with: logging.c: In function 'ntfs_log_handler_syslog': logging.c:365: error: incompatible types in assignment logging.c: In function 'ntfs_log_handler_fprintf': logging.c:450: error: incompatible types in assignment pgptzlIMbOxjx.pgp Description: PGP signature
Bug#380089: possibly inadequate solution
also sprach maximilian attems <[EMAIL PROTECTED]> [2006.07.31.1658 +0100]: > anyway the initramfs-tools implementation targets 1.9.0-4sarge1, > so i'm happy on your input for the sarge specific version. difficult to say. creating mdadm.conf (see /usr/share/mdadm/mkconf) and running `mdadm -Asayes --run` should do. If it doesn't do what mdrun used to do, and even better, I am in trouble. But so far, I've had no indication that it doesn't work the way I expect it. Anyway, mdrun will be in etch, albeit deprecated. I'll only remove it after etch if everything goes well. Thus, we could potentially revert to mdrun in the last second before the release. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft <[EMAIL PROTECTED]> : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system signature.asc Description: Digital signature (GPG/PGP)
Bug#380089: possibly inadequate solution
On Mon, Jul 31, 2006 at 03:13:32PM +0100, martin f krafft wrote: > also sprach maximilian attems <[EMAIL PROTECTED]> [2006.07.31.1439 +0100]: > > mdrun was avoided due too getting random md devices. > > although according to fjp older mdadm seems to have it's share > > of problems: > > http://lists.debian.org/debian-boot/2006/07/msg00244.html > > These problems should be solved with 2.5. Frans was testing with > 2.4, which had these problems as confirmed by upstream. cool to hear that it was an 2.4 specific trouble. anyway the initramfs-tools implementation targets 1.9.0-4sarge1, so i'm happy on your input for the sarge specific version. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380499: [Build-common-hackers] Bug#380499: cdbs 0.4.45 simple-patchsys.mk doesn't properly distinguish patches
Note that the freeze cutoff for cdbs is approaching, so we need an idea on this really quickly. Am Sonntag, 30. Juli 2006 22:19 schrieb Peter Eisentraut: > Christopher Martin wrote: > > Notice how debian/patches/04_am_maintainer_mode.diff is skipped > > because "it's already applied" even though it clearly isn't? There is > > a similarly named but different patch, > > debian/patches/common/04_am_maintainer_mode.diff, which is perhaps > > confusing CDBS. > > We need a per-patch stamp file to fix various other misbehaviors, which > is why this sort of setup is out of luck. Apparently someone thought > that the actual patch directory should be read-only, so devising a > patch stamp naming scheme that can handle this is a bit tricky. > > Currently we have > > $(call cdbs_update_stamp,debian/stamp-patch-$$(basename $$patch)) > > Considering that the patch directory can be chosen arbitrarily (a > feature that you make use of), we can't just stick the directory name > in there. > > Anyone got an idea? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380652: squid fails to start because of "Function not implemented" error
Package: squid
Version: 2.6.1-3
Severity: grave
Justification: renders package unusable
On my kernel (2.4.28), starting the updated squid results in a crash
with the following logged in the syslog:
Jul 31 11:30:58 tea (squid): comm_select_init: epoll_create(): (38) Function
not implemented
Running squid directly shows the following:
# su proxy -c '/usr/sbin/squid -N'
FATAL: comm_select_init: epoll_create(): (38) Function not implemented
Squid Cache (Version 2.6.STABLE1): Terminated abnormally.
CPU Usage: 0.130 seconds = 0.110 user + 0.020 sys
Maximum Resident Size: 0 KB
Page faults with physical i/o: 578
Running it directly and under strace shows the following:
# su proxy -c 'strace /usr/sbin/squid -N'
[stuff deleted]
open("/var/run/squid.pid", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or
directory)
getrlimit(RLIMIT_CORE, {rlim_cur=0, rlim_max=RLIM_INFINITY}) = 0
setrlimit(RLIMIT_CORE, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0
getrlimit(RLIMIT_NOFILE, {rlim_cur=1024, rlim_max=1024}) = 0
setrlimit(RLIMIT_NOFILE, {rlim_cur=1024, rlim_max=1024}) = 0
getrlimit(RLIMIT_DATA, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0
mmap2(NULL, 217088, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x32f000
epoll_create(1024) = -1 ENOSYS (Function not implemented)
time([1154361075]) = 1154361075
open("/etc/localtime", O_RDONLY)= 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=1252, ...}) = 0
fstat64(3, {st_mode=S_IFREG|0644, st_size=1252, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x128000
read(3, "TZif\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\4\0\0\0\4\0"..., 4096) =
1252
close(3)= 0
munmap(0x128000, 4096) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1252, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1252, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1252, ...}) = 0
socket(PF_FILE, SOCK_DGRAM, 0) = 3
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
connect(3, {sa_family=AF_FILE, path="/dev/log"}, 16) = 0
send(3, "<9>Jul 31 11:51:15 squid: comm_s"..., 90, MSG_NOSIGNAL) = 90
write(2, "FATAL: comm_select_init: epoll_c"..., 72FATAL: comm_select_init:
epoll_create(): (38) Function not implemented
) = 72
write(2, "Squid Cache (Version 2.6.STABLE1"..., 58Squid Cache (Version
2.6.STABLE1): Terminated abnormally.
) = 58
getrusage(RUSAGE_SELF, {ru_utime={0, 11}, ru_stime={0, 2}, ...}) = 0
write(2, "CPU Usage: 0.130 seconds = 0.110"..., 50CPU Usage: 0.130 seconds =
0.110 user + 0.020 sys
) = 50
write(2, "Maximum Resident Size: 0 KB\n", 28Maximum Resident Size: 0 KB
) = 28
write(2, "Page faults with physical i/o: 3"..., 35Page faults with physical
i/o: 306
) = 35
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
kill(9438, SIGABRT) = 0
--- SIGABRT (Aborted) @ 0 (0) ---
+++ killed by SIGABRT +++
Process 9438 detached
#
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.28-ow1
Locale: LANG=zh_TW.Big5, LC_CTYPE=zh_TW.Big5 (charmap=BIG5)
Versions of packages squid depends on:
ii adduser 3.95 Add and remove users and groups
ii coreutils 5.97-1 The GNU core utilities
ii debconf [debconf-2.0] 1.5.2 Debian configuration management sy
ii libc6 2.3.6-16 GNU C Library: Shared libraries
ii libdb4.3 4.3.29-6 Berkeley v4.3 Database Libraries [
ii libldap2 2.1.30-13 OpenLDAP libraries
ii libpam0g 0.79-3.1 Pluggable Authentication Modules l
ii logrotate 3.7.1-3Log rotation utility
ii lsb-base 3.1-10 Linux Standard Base 3.1 init scrip
ii netbase 4.25 Basic TCP/IP networking system
ii squid-common 2.6.1-3Internet Object Cache (WWW proxy c
squid recommends no packages.
-- debconf information:
squid/fix_cachedir_perms: false
* squid/largefiles_warning:
squid/anonymize_headers:
* squid-cgi/cachemgr:
squid/old_version: false
squid/http_anonymizer:
squid/authenticate_program:
squid/fix_lines: true
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#361846: marked as done (non-free license for core.schema)
Your message dated Mon, 31 Jul 2006 17:26:30 +0200 with message-id <[EMAIL PROTECTED]> and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: openldap2.2 Severity: serious The license for the file core.schema says: ## Portions Copyright (C) The Internet Society (1997-2003). ## All Rights Reserved. ## ## This document and translations of it may be copied and furnished to ## others, and derivative works that comment on or otherwise explain it ## or assist in its implementation may be prepared, copied, published ## and distributed, in whole or in part, without restriction of any ## kind, provided that the above copyright notice and this paragraph are ## included on all such copies and derivative works. However, this ## document itself may not be modified in any way, such as by removing ## the copyright notice or references to the Internet Society or other ## Internet organizations, except as needed for the purpose of ## developing Internet standards in which case the procedures for ## copyrights defined in the Internet Standards process must be ## followed, or as required to translate it into languages other than ## English. ## ## The limited permissions granted above are perpetual and will not be ## revoked by the Internet Society or its successors or assigns. ## ## This document and the information contained herein is provided on an ## "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING ## TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ## BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION ## HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF ## MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. The ftpmasters have recently rejected a package that contains another schema file with identical license text, and there was no obvious opposition to that decision on Debian legal [0], so the current understanding seems to be that this license is not free. I don't necessarily agree with all that, but this bug can serve as an incentive to getting this issue resolved. [0] http://lists.debian.org/debian-legal/2006/04/threads.html --- End Message --- --- Begin Message --- This package has been removed now. -- Martin Michlmayr http://www.cyrius.com/ --- End Message ---
Processed: reassign 378498 to haskell-hsql
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.20 > reassign 378498 haskell-hsql Bug#378498: Needs recompilation because of ghci 6.4.2 Bug reassigned from package `libghc6-hsql-dev' to `haskell-hsql'. > 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#329212: marked as done (fisg: Fisg segfault)
Your message dated Mon, 31 Jul 2006 17:32:29 +0200 with message-id <[EMAIL PROTECTED]> and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: fisg Version: 0.3.8-2 Severity: grave Justification: renders package unusable fisg segfault while parsing file, strace output attached -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.31-GRSEC Locale: LANG=it_IT, LC_CTYPE=it_IT (charmap=ISO-8859-1) Versions of packages fisg depends on: ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an -- no debconf information fisg.strace.log.bz2 Description: BZip2 compressed data --- End Message --- --- Begin Message --- This package has been removed from Debian because it's no longer maintained upstream. -- Martin Michlmayr http://www.cyrius.com/ --- End Message ---
Bug#201219: marked as done (gnome-pim: FTBFS: Broken Build-Depends)
Your message dated Mon, 31 Jul 2006 17:39:57 +0200 with message-id <[EMAIL PROTECTED]> and subject line gnome-pim removal has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: gnome-pim Version: 1.4.9-2 Severity: serious The gnome-pim source package Build-Depends on libgnome-pilot1-dev, which no longer exists in unstable. It seems you need to upgrade this to libgnome-pilot2-dev. -- 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 --- --- Begin Message --- The gnome-pim package has been removed from Debian. The reason is that it is "old, obsolete, unmaintained upstream, and doesn't work properly. Better alternatives (Evolution, Contacts, ...) are available in Debian." -- Martin Michlmayr http://www.cyrius.com/ --- End Message ---
Bug#360397: marked as done (python2.4-numpy: Depends on atlas2 which is not available)
Your message dated Mon, 31 Jul 2006 17:48:14 +0200 with message-id <[EMAIL PROTECTED]> and subject line resolved has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: python2.4-numpy Severity: grave Tags: experimental Justification: renders package unusable Depends on atlas2 which is not available. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'testing'), (55, 'breezy') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-acid2 Locale: LANG=hr_HR.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) --- End Message --- --- Begin Message --- It seems this has been resolved now. -- Martin Michlmayr http://www.cyrius.com/ --- End Message ---
Bug#304092: marked as done (ultrapossum-slapd: FTBFS: failed test)
Your message dated Mon, 31 Jul 2006 17:27:24 +0200 with message-id <[EMAIL PROTECTED]> and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: ultrapossum-slapd Version: 0.0.4+2.2.20sb2-1 Severity: serious Hi, building the package ultrapossum-slapd in a clean sid build environment (with pbuilder) on i386 results in: = [...] Using ldapsearch to check that master slapd is running... Waiting 5 seconds for slapd to start... Starting slave slapd on TCP/IP port 9012... Using ldapsearch to check that slave slapd is running... Waiting 20 seconds for syncbackup to receive changes... modify data Waiting 10 seconds for syncbackup to receive changes... Using ldapsearch to read all the entries from the master... Using ldapsearch to read all the entries from the slave... Using ldapsearch to read all the entries from the another slave... Filtering ldapsearch results... Filtering original ldif used to create database... Comparing retrieved entries from master and slave... Filtering original ldif used to create database... Comparing retrieved entries from master and slave... test failed - master and another slave databases differ > ./scripts/test101-syncbackup [1mfailed[m (exit 1) make[6]: *** [bdb-yes] Error 1 make[6]: Leaving directory `/tmp/buildd/ultrapossum-slapd-0.0.4+2.2.20sb2/upstream/build-tree/openldap-2.2.20/tests' make[5]: *** [test] Error 2 make[5]: Leaving directory `/tmp/buildd/ultrapossum-slapd-0.0.4+2.2.20sb2/upstream/build-tree/openldap-2.2.20/tests' make[4]: *** [test] Error 2 make[4]: Leaving directory `/tmp/buildd/ultrapossum-slapd-0.0.4+2.2.20sb2/upstream/build-tree/openldap-2.2.20' make[3]: *** [check-local] Error 2 make[3]: Leaving directory `/tmp/buildd/ultrapossum-slapd-0.0.4+2.2.20sb2/upstream' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/tmp/buildd/ultrapossum-slapd-0.0.4+2.2.20sb2/upstream' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/buildd/ultrapossum-slapd-0.0.4+2.2.20sb2' make: *** [build-stamp] Error 2 = Please note that on other arches, the packages FTBFS, too, but for different reasons (linker error, other tests). Thanks for considering. -- DARTS - Debian Archive Regression Test Suite http://darts.alioth.debian.org/ Please note that this report has not been generated fully automatically. DARTS just helped finding the problem. --- End Message --- --- Begin Message --- ultrapossum has been removed from Debian because it is "dead upstream, unmaintained, depends on removed openldap2.2"; please see #378885. -- Martin Michlmayr http://www.cyrius.com/ --- End Message ---
Bug#308088: marked as done (ultrapossum-slapd: FTBFS: test020-proxycache failed.)
Your message dated Mon, 31 Jul 2006 17:27:24 +0200 with message-id <[EMAIL PROTECTED]> and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: ultrapossum-slapd Version: 0.0.4+2.2.20sb3-1 Severity: serious Hi, Your package is failing to build with the following error: > Starting test020-proxycache ... Starting master slapd on TCP/IP port 9011... Using ldapsearch to check that master slapd is running... Waiting 5 seconds for slapd to start... Using ldapadd to populate the master directory... Starting proxy cache on TCP/IP port 9012... Using ldapsearch to check that proxy slapd is running... Waiting 5 seconds for slapd to start... Waiting 5 seconds for slapd to start... Waiting 5 seconds for slapd to start... Waiting 5 seconds for slapd to start... Waiting 5 seconds for slapd to start... Waiting 5 seconds for slapd to start... ldapsearch failed (1)! ./scripts/test020-proxycache: line 99: kill: (30490) - No such process > ./scripts/test020-proxycache failed (exit 1) make[6]: *** [bdb-yes] Error 1 Note that I'm seeing this on i386 too. Kurt --- End Message --- --- Begin Message --- ultrapossum has been removed from Debian because it is "dead upstream, unmaintained, depends on removed openldap2.2"; please see #378885. -- Martin Michlmayr http://www.cyrius.com/ --- End Message ---
Bug#297853: marked as done (needs to be ported to new parted API)
Your message dated Mon, 31 Jul 2006 17:32:54 +0200 with message-id <[EMAIL PROTECTED]> and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: libparted-swig-perl Version: 0.1.20020731-2 Severity: grave Yann, I'm sorry that this bug report comes as late as it does; it really should have been filed a long time ago, but somehow this package was overlooked previously. The libparted-swig-perl package depends on libparted1.6-0, which is no longer present in unstable, having been replaced with libparted1.6-12. This new version of parted is needed for the upcoming d-i release candidate, so libparted-swig-perl is being removed from testing to allow it in (again, apologies for the lack of notice). The parted upgrade is accompanied by an API change, not just an ABI change, so this is probably not as simple as a recompile of parted-swig. Please see the related bug on python-parted, bug #284081, for a discussion of the issues involved. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: alpha Kernel: Linux 2.4.27-2-generic Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages libparted-swig-perl depends on: ii libc6.1 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libparted1.6-0 1.6.11-9 The GNU Parted disk partitioning s ii perl5.8.4-6 Larry Wall's Practical Extraction ii perl-base [perlapi-5.8.4] 5.8.4-6 The Pathologically Eclectic Rubbis --- End Message --- --- Begin Message --- dead upstream; out of date; RC buggy -- Martin Michlmayr http://www.cyrius.com/ --- End Message ---
Processed: reassign to correct packages
Processing commands for [EMAIL PROTECTED]: > reassign 377983 dansguardian Bug#377983: dansguardian-2.8.0.6-antivirus-6.3.8-1-1: Dansguardian crashes on etch. Warning: Unknown package 'dansguardian-2.8.0.6-antivirus-6.3.8-1-1' Bug reassigned from package `dansguardian-2.8.0.6-antivirus-6.3.8-1-1' to `dansguardian'. > -- 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#351145: marked as done (Please stop build modules for python2.1/python2.2)
Your message dated Mon, 31 Jul 2006 17:33:19 +0200 with message-id <[EMAIL PROTECTED]> and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: python-orbit Usertag: python2 Please stop build modules for python2.1/python2.2 from the python-orbit source package. Although there is still discussion about the python version(s) to support, it is clear that python2.1 and python2.2 are dropped. We are targeting a python version >= 2.4 as the default python version for etch (python2.3 is still the default python version), so it may not be wrong to support python2.4, when you drop support for python2.1 and python2.2. The severity of this report will be raised to serious when the python2.1 and python2.2 are removed from unstable. --- End Message --- --- Begin Message --- This package has been removed because it's "obsolete". -- Martin Michlmayr http://www.cyrius.com/ --- End Message ---
Bug#247192: marked as done (gnome-pim: uninstallable due to conflict with gnome-pim-conduits)
Your message dated Mon, 31 Jul 2006 17:39:57 +0200 with message-id <[EMAIL PROTECTED]> and subject line gnome-pim removal has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: gnome-pim Version: 1.4.9-2.1 Severity: serious I am unable to upgrade to gnome-pim version 1.4.9-2.1. # apt-get install gnome-pim [...] Unpacking replacement gnome-pim ... dpkg: error processing /var/cache/apt/archives/gnome-pim_1.4.9-2.1_i386.deb (--unpack): trying to overwrite `/usr/share/pixmaps/gnome-calendar-conduit.png', which is also in package gnome-pim-conduits dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/gnome-pim_1.4.9-2.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) # dpkg -l gnome-pim gnome-pim-conduits [...] ii gnome-pim 1.4.9-2calendar and address book for GNOME ii gnome-pim-cond 1.4.9-2Palm synchronization for calendar and addres Thanks, -Chris --- End Message --- --- Begin Message --- The gnome-pim package has been removed from Debian. The reason is that it is "old, obsolete, unmaintained upstream, and doesn't work properly. Better alternatives (Evolution, Contacts, ...) are available in Debian." -- Martin Michlmayr http://www.cyrius.com/ --- End Message ---
Bug#380537: [Pkg-openldap-devel] Bug#380537: slapd: Fails to start after upgrade to from 2.3.23 to 2.3.24
Hi Peter,
On Mon, Jul 31, 2006 at 07:05:45AM +0100, Peter Hicks wrote:
> >> slapd.conf is owned by root.root, and chown-ing it to root.openldap fixes
> >> the problem.
> >
> > Is this because the perms on the file are 0640?
>
> Spot on.
Hmm, that's weird because the main function in Debian's slapd contains
code that reads like this:
if ( read_config( configfile, configdir ) != 0 ) {
/* error handling */
}
if ( username != NULL || groupname != NULL ) {
slap_init_user( username, groupname );
}
Therefore this error should not happen. Could you be so kind to provide
an strace of slapd starting, about like this one:
# strace -e trace=setuid32,open /usr/sbin/slapd \
-d 0 -g openldap -u openldap
open("/etc/ldap/slapd.conf", O_RDONLY|O_LARGEFILE) = 8
[...]
setuid32(101) = 0
# getent passwd 101
openldap:x:101:103:OpenLDAP Server Account,,,:/var/lib/ldap:/bin/false
As you can see it works fine on my system, with the same slapd version.
I am curious why it does not work for you...
Greetings
Torsten
signature.asc
Description: Digital signature
Bug#379265: patch for RC bug: FTBFS: needs an update for new ghc6
Hi John, I have prepared a little update for haskell-magic to fix the FTBFS and make libghc6-magic-dev installable again. I have attached my diff. Greetings Arjan Oosting diff -Nru /tmp/GYDPIgfOyG/magic-haskell-1.0.3/debian/changelog /tmp/PPj7bsdfc5/magic-haskell-1.0.3.1/debian/changelog --- /tmp/GYDPIgfOyG/magic-haskell-1.0.3/debian/changelog 2005-10-17 07:02:56.0 +0200 +++ /tmp/PPj7bsdfc5/magic-haskell-1.0.3.1/debian/changelog 2006-07-31 15:03:58.0 +0200 @@ -1,3 +1,13 @@ +magic-haskell (1.0.3.1) unstable; urgency=low + + * Non-maintainer upload. + * Updates for the new ghc6 version (Closes: #379265): +- debian/control: update the build dependency on ghc6. +- magic.cabal: add base to the Cabal Build-Depends as it is hidden by + default now. + + -- Arjan Oosting <[EMAIL PROTECTED]> Mon, 31 Jul 2006 14:50:24 +0200 + magic-haskell (1.0.3) unstable; urgency=low * Rebuilt against ghc6 6.4.1. diff -Nru /tmp/GYDPIgfOyG/magic-haskell-1.0.3/debian/control /tmp/PPj7bsdfc5/magic-haskell-1.0.3.1/debian/control --- /tmp/GYDPIgfOyG/magic-haskell-1.0.3/debian/control 2005-10-17 07:02:43.0 +0200 +++ /tmp/PPj7bsdfc5/magic-haskell-1.0.3.1/debian/control 2006-07-31 14:53:36.0 +0200 @@ -1,8 +1,8 @@ Source: magic-haskell Priority: optional Maintainer: John Goerzen <[EMAIL PROTECTED]> -Build-Depends: debhelper (>= 4.0.0), ghc6 (>= 6.4.1), ghc6 (<< 6.4.1-999), hugs (>= 98.200503.08), haskell-devscripts (>= 0.5.10), libmagic-dev -Build-Depends-Indep: debhelper (>= 4.0.0), haddock, ghc6 (>= 6.4.1), haskell-devscripts (>= 0.5.10), libmagic-dev +Build-Depends: debhelper (>= 4.0.0), ghc6 (>= 6.4.2), ghc6 (<< 6.4.2-999), hugs (>= 98.200503.08), haskell-devscripts (>= 0.5.10), libmagic-dev +Build-Depends-Indep: debhelper (>= 4.0.0), haddock, ghc6 (>= 6.4.2), haskell-devscripts (>= 0.5.10), libmagic-dev Standards-Version: 3.6.2 Section: devel diff -Nru /tmp/GYDPIgfOyG/magic-haskell-1.0.3/magic.cabal /tmp/PPj7bsdfc5/magic-haskell-1.0.3.1/magic.cabal --- /tmp/GYDPIgfOyG/magic-haskell-1.0.3/magic.cabal 2005-08-16 16:50:11.0 +0200 +++ /tmp/PPj7bsdfc5/magic-haskell-1.0.3.1/magic.cabal 2006-07-31 14:58:06.0 +0200 @@ -15,7 +15,7 @@ Magic.Operations Other-Modules: Magic.Utils, Magic.TypesLL -Build-Depends: haskell-src +Build-Depends: base, haskell-src GHC-Options: -O2 -- CC-Options: -Iglue Extensions: ForeignFunctionInterface, TypeSynonymInstances signature.asc Description: Dit berichtdeel is digitaal ondertekend
Bug#379137: marked as done (boinc-client errors out with a "Floating point exception" error when application is launched.)
Your message dated Mon, 31 Jul 2006 07:17:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379137: fixed in boinc 5.4.10-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: boinc-client Version: 5.4.10-1 Severity: grave Justification: renders package unusable I think the CFLAGS option "-ffast-math" is the culprit. -- 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.17.6 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages boinc-client depends on: ii adduser 3.95 Add and remove users and groups ii libc6.1 2.3.6-15 GNU C Library: Shared libraries ii libcomerr21.39-1 common error description library ii libcurl3 7.15.4-1 Multi-protocol file transfer libra ii libgcc1 1:4.1.1-9 GCC support library ii libidn11 0.6.5-1GNU libidn library, implementation ii libkrb53 1.4.3-8MIT Kerberos runtime libraries ii libssl0.9.8 0.9.8b-2 SSL shared libraries ii libstdc++64.1.1-9The GNU Standard C++ Library v3 ii lsb-base 3.1-10 Linux Standard Base 3.1 init scrip ii python2.3.5-9An interactive high-level object-o ii zlib1g1:1.2.3-13 compression library - runtime boinc-client recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: boinc Source-Version: 5.4.10-2 We believe that the bug you reported is fixed in the latest version of boinc, which is due to be installed in the Debian FTP archive: boinc-client_5.4.10-2_i386.deb to pool/main/b/boinc/boinc-client_5.4.10-2_i386.deb boinc-dev_5.4.10-2_i386.deb to pool/main/b/boinc/boinc-dev_5.4.10-2_i386.deb boinc-manager_5.4.10-2_i386.deb to pool/main/b/boinc/boinc-manager_5.4.10-2_i386.deb boinc_5.4.10-2.diff.gz to pool/main/b/boinc/boinc_5.4.10-2.diff.gz boinc_5.4.10-2.dsc to pool/main/b/boinc/boinc_5.4.10-2.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. Frank S. Thomas <[EMAIL PROTECTED]> (supplier of updated boinc 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: Tue, 25 Jul 2006 12:55:10 +0200 Source: boinc Binary: boinc-manager boinc-dev boinc-client Architecture: source i386 Version: 5.4.10-2 Distribution: unstable Urgency: medium Maintainer: Debian BOINC Maintainers <[EMAIL PROTECTED]> Changed-By: Frank S. Thomas <[EMAIL PROTECTED]> Description: boinc-client - core client for the BOINC distributed computing infrastructure boinc-dev - development files to build applications for BOINC projects boinc-manager - GUI to control and monitor the BOINC core client Closes: 379137 Changes: boinc (5.4.10-2) unstable; urgency=medium . [ Frank S. Thomas ] * Removed -ffast-math from the client's optimization flags because it causes a floating point exception on Alpha when the client is started. (closes: #379137) * Added conffile /etc/boinc-client/log_flags.xml which can be used to turn on/off logging and debugging messages. For a detailed list of messages that can be turned on/off, see http://boinc.berkeley.edu/client_msgs.php Note that this file was renamed to cc_config.xml in BOINC (>= 5.5.2). * Applied patches from Peter Bailis <[EMAIL PROTECTED]> for the boinc_cmd manual page. Thanks again Peter! * debian/control: - Added boinc-app-seti to boinc-client's Suggests field. Files: f4ff656b8a5e6d288e37b1bf354673c7 1374 net optional boinc_5.4.10-2.dsc 4cbf3a43f06aff0879230c9a16d3f11d 35342 net optional boinc_5.4.10-2.diff.gz e168afd4f1ea5f5d13ffcb5f8c86521b 296728 net optional boinc-client_5.4.10-2_i386.deb f6e0455137fd121319ef0d261af9d1c3 699840 x11 optional boinc-manager_5.4.10-2_i386.deb 1d7ec24f626f7b78bdd01cf614e2d5a1 359272 devel optional
Processed: severity of 380636 is important
Processing commands for [EMAIL PROTECTED]: > severity 380636 important Bug#380636: python-imdbpy: misses parsers Severity set to `important' from `grave' > 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#380597: python-tk: /usr/bin/pycentral: /usr/bin/python: bad interpreter: No such file or directory
tags 380597 + unreproducible moreinfo severity 380597 important thanks can't reproduce that; which were the versions of python2.3, python-defaults and python-central before the upgrade? why don't you dist-upgrade? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#380597: python-tk: /usr/bin/pycentral: /usr/bin/python: bad interpreter: No such file or directory
Processing commands for [EMAIL PROTECTED]: > tags 380597 + unreproducible moreinfo Bug#380597: python-tk: /usr/bin/pycentral: /usr/bin/python: bad interpreter: No such file or directory There were no tags set. Tags added: unreproducible, moreinfo > severity 380597 important Bug#380597: python-tk: /usr/bin/pycentral: /usr/bin/python: bad interpreter: No such file or directory Severity set to `important' from `critical' > 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#380089: possibly inadequate solution
also sprach maximilian attems <[EMAIL PROTECTED]> [2006.07.31.1439 +0100]: > mdrun was avoided due too getting random md devices. > although according to fjp older mdadm seems to have it's share > of problems: > http://lists.debian.org/debian-boot/2006/07/msg00244.html These problems should be solved with 2.5. Frans was testing with 2.4, which had these problems as confirmed by upstream. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft <[EMAIL PROTECTED]> : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system signature.asc Description: Digital signature (GPG/PGP)
Processed: tagging 380636
Processing commands for [EMAIL PROTECTED]: > tags 380636 confirmed Bug#380636: python-imdbpy: misses parsers There were no tags set. Tags added: confirmed > 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#361024: problem solved by upgrading libc6
Hello, FWIW, upgrading libc6 to 2.3.6-17 solved it. See also bug #226716. Thank you! Best, --Toni++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380089: possibly inadequate solution
On Sun, Jul 30, 2006 at 07:25:20PM -0700, Steve Langasek wrote: > On Sat, Jul 29, 2006 at 05:53:27PM +0100, martin f krafft wrote: > > Anyway, I disagree with the way 0.73 fixes the bug: it replicates > > the functionality provided by mdadm >=2.5-1 into a hack within the > > package. Granted, the hack is only used when mdadm >=2.5-1 is not > > installed, but still, it's a hack. > > > The maintainer failed to give any reasons why his solution is > > preferred over a simple conflict against mdadm <<2.5-1, which is > > what I proposed even before we started the transition. I do not see > > why we should have a hack ensuring that everything works when mdadm > > <<2.5-1 is installed, instead of just ensuring that a newer mdadm > > should be installed by means of a conflict. Then again, a conflict > > could possibly remove the mdadm package altogether, which would be > > equally bad. There seems to be no way to tell Debian to conflict > > with versions prior to a specific package's specific version, but to > > ensure an upgrade as a resolution conflict, not the package's > > removal. > > Yes, that would be a dependency then, not a conflict. The reasons for not > making this a dependency are clear. > > The reasons for wishing to avoid a versioned Conflicts: are also clear to > me, being precisely those that you describe above. indeed aboves thoughts where the primary reason. also i wanted to stay on the path of a proven solution: ubuntu had faced the same transition to dapper from breezy, with prior mdadm without mdadm hooks and they choose to add this small functionality to mkinitramfs. afaik from their bug tracking system this worked out. this "duplicate" code will be easily dropped postetch. > So making initramfs-tools compatible with older versions of mdadm seems like > a good idea to me. Are there specific reasons why you think the proposed > solution is technically inadequate? the implementation itself needs more test, i had a test sarge upgrade box that weekend where it worked out fine. mdrun was avoided due too getting random md devices. although according to fjp older mdadm seems to have it's share of problems: http://lists.debian.org/debian-boot/2006/07/msg00244.html so i hope to stay in contact with madduck to check out on which range the chosen solution works and refine it. best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380636: python-imdbpy: misses parsers
Package: python-imdbpy Version: 2.6-1 Severity: grave Justification: renders package unusable Hi, wanted to try out the imdbpy package, but the parsers for http and sql are missing. Only local and mobile are installed. Andreas -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.6 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages python-imdbpy depends on: ii libc6 2.3.6-16 GNU C Library: Shared libraries ii python2.3.5-11 An interactive high-level object-o ii python-support0.3.8 automated rebuilding support for p python-imdbpy recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380635: libsdl1.2debian-all: Packageuninstallable
Package: libsdl1.2debian-all Severity: grave Justification: renders package unusable Hi, libdirectfb-0.9-24 has been removed from unstable anb sdl need to be rebuild : # apt-get install libsdl1.2debian-all Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: libsdl1.2debian-all: Depends: libdirectfb-0.9-24 but it is not installable E: Broken packages Christian -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (900, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.1 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: merge 379492 379815
Processing commands for [EMAIL PROTECTED]: > merge 379492 379815 Bug#379492: klog: FTBFS: autoconf 2.60 is not supported Bug#379815: FTBFS: doesn't recognize autoconf 2.60 Merged 379492 379815. > 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#380638: matrixssl: FTBFS: error: 'BITS_PER_LONG' undeclared
Package: matrixssl Version: 1.7.3-1 Severity: serious Hello, There was a problem while autobuilding your package: > Automatic build of matrixssl_1.7.3-1 on avidan by sbuild/i386 0.49 > Build started at 20060731-1542 > ** ... > debian/rules build > mkdir -p gnu/static gnu/shared > (cd gnu/static && tar xzf -) <'matrixssl-1-7-3-open.tar.gz' > (cd gnu/shared && tar xzf -) <'matrixssl-1-7-3-open.tar.gz' > touch unpack-gnu-stamp > gcc -v > Using built-in specs. > Target: i486-linux-gnu > Configured with: ../src/configure -v > --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr > --enable-shared --with-system-zlib --libexecdir=/usr/lib > --without-included-gettext --enable-threads=posix --enable-nls > --program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu > --enable-libstdcxx-debug --enable-mpfr --with-tune=i686 > --enable-checking=release i486-linux-gnu > Thread model: posix > gcc version 4.1.2 20060729 (prerelease) (Debian 4.1.1-10) > /usr/bin/make -Cgnu/static/matrixssl/src libmatrixssl.a \ > STATIC=libmatrixssl.a DFLAGS='-Wall -g -O2' > make[1]: Entering directory > `/build/buildd/matrixssl-1.7.3/gnu/static/matrixssl/src' > gcc -Wall -g -O2 -DLINUX -I./ -c -o cipherSuite.o cipherSuite.c > gcc -Wall -g -O2 -DLINUX -I./ -c -o matrixSsl.o matrixSsl.c > matrixSsl.c:40: warning: 'copyright' defined but not used > gcc -Wall -g -O2 -DLINUX -I./ -c -o sslDecode.o sslDecode.c > sslDecode.c: In function 'matrixSslDecode': > sslDecode.c:493: warning: 'currentCert' may be used uninitialized in this > function > gcc -Wall -g -O2 -DLINUX -I./ -c -o sslEncode.o sslEncode.c > gcc -Wall -g -O2 -DLINUX -I./ -c -o sslv3.o sslv3.c > gcc -Wall -g -O2 -DLINUX -I./ -c -o os/debug.o os/debug.c > gcc -Wall -g -O2 -DLINUX -I./ -c -o os/linux/linux.o os/linux/linux.c > In file included from /usr/include/linux/cpumask.h:86, > from /usr/include/asm-i486/processor.h:23, > from /usr/include/asm/processor.h:8, > from /usr/include/asm-i486/timex.h:10, > from /usr/include/asm/timex.h:8, > from os/linux/linux.c:43: > /usr/include/linux/bitmap.h: In function 'bitmap_zero': > /usr/include/linux/bitmap.h:128: error: 'BITS_PER_LONG' undeclared (first use > in this function) > /usr/include/linux/bitmap.h:128: error: (Each undeclared identifier is > reported only once > /usr/include/linux/bitmap.h:128: error: for each function it appears in.) > /usr/include/linux/bitmap.h: In function 'bitmap_fill': > /usr/include/linux/bitmap.h:143: error: 'BITS_PER_LONG' undeclared (first use > in this function) > /usr/include/linux/bitmap.h: In function 'bitmap_copy': > /usr/include/linux/bitmap.h:149: error: 'BITS_PER_LONG' undeclared (first use > in this function) > /usr/include/linux/bitmap.h: In function 'bitmap_and': > /usr/include/linux/bitmap.h:160: error: 'BITS_PER_LONG' undeclared (first use > in this function) > /usr/include/linux/bitmap.h: In function 'bitmap_or': > /usr/include/linux/bitmap.h:169: error: 'BITS_PER_LONG' undeclared (first use > in this function) > /usr/include/linux/bitmap.h: In function 'bitmap_xor': > /usr/include/linux/bitmap.h:178: error: 'BITS_PER_LONG' undeclared (first use > in this function) > /usr/include/linux/bitmap.h: In function 'bitmap_andnot': > /usr/include/linux/bitmap.h:187: error: 'BITS_PER_LONG' undeclared (first use > in this function) > /usr/include/linux/bitmap.h: In function 'bitmap_complement': > /usr/include/linux/bitmap.h:196: error: 'BITS_PER_LONG' undeclared (first use > in this function) > /usr/include/linux/bitmap.h: In function 'bitmap_equal': > /usr/include/linux/bitmap.h:205: error: 'BITS_PER_LONG' undeclared (first use > in this function) > /usr/include/linux/bitmap.h: In function 'bitmap_intersects': > /usr/include/linux/bitmap.h:214: error: 'BITS_PER_LONG' undeclared (first use > in this function) > /usr/include/linux/bitmap.h: In function 'bitmap_subset': > /usr/include/linux/bitmap.h:223: error: 'BITS_PER_LONG' undeclared (first use > in this function) > /usr/include/linux/bitmap.h: In function 'bitmap_empty': > /usr/include/linux/bitmap.h:231: error: 'BITS_PER_LONG' undeclared (first use > in this function) > /usr/include/linux/bitmap.h: In function 'bitmap_full': > /usr/include/linux/bi
Processed: Re: retitle 352084 to kazehakase: Build-Dep on mozilla (library), should transition to xulrunner
Processing commands for [EMAIL PROTECTED]: > retitle 352084 kazehakase: Build-Dep on mozilla (library), should transition > to xulrunner Bug#352084: kazehakase: Build-Dep on mozilla (library), should transition to xulrunner Changed Bug title. (By the way, that Bug is currently marked as done.) > 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: Re: Bug#380619: cupsys: does not start at all
Processing commands for [EMAIL PROTECTED]: > severity 380619 normal Bug#380619: cupsys: does not start at all Severity set to `normal' from `grave' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 379265
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.20 > tags 379265 patch Bug#379265: FTBFS: needs an update for new ghc6 There were no tags set. Tags added: patch > 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#318548: marked as done (libxbox: FTBFS: pointer targets in passing argument 2 of 'xbox_smc_read' differ in signedness)
Your message dated Mon, 31 Jul 2006 05:32:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#318548: fixed in libxbox 0.1-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: libxbox Severity: serious Version: 0.1-1 >From my build log: ... rm -f libxbox.so libxbox.so.* *.o test gcc -g -O2 -shared -fPIC -Wall -Werror -D_REENTRANT -I include -c -o libxbox-i2c.o libxbox-i2c.c cc1: warnings being treated as errors libxbox-i2c.c: In function 'xbox_temperatures': libxbox-i2c.c:119: warning: pointer targets in passing argument 2 of 'xbox_smc_read' differ in signedness libxbox-i2c.c:119: warning: pointer targets in passing argument 2 of 'xbox_smc_read' differ in signedness libxbox-i2c.c: In function 'xbox_fanspeed': libxbox-i2c.c:123: warning: pointer targets in passing argument 2 of 'xbox_smc_read' differ in signedness libxbox-i2c.c: In function 'xbox_smc_version': libxbox-i2c.c:176: warning: pointer targets in passing argument 2 of 'xbox_smc_read' differ in signedness libxbox-i2c.c: In function 'xbox_av_cable': libxbox-i2c.c:204: warning: pointer targets in passing argument 2 of 'xbox_smc_read' differ in signedness make[1]: *** [libxbox-i2c.o] Error 1 make[1]: Leaving directory `/tmp/buildd/libxbox-0.1' make: *** [build-stamp] Error 2 -- System Information: Debian Release: testing/unstable Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-9-amd64-k8 Locale: LANG=en, LC_CTYPE=en (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) -- Daniel Schepler "Please don't disillusion me. I [EMAIL PROTECTED]haven't had breakfast yet." -- Orson Scott Card --- End Message --- --- Begin Message --- Source: libxbox Source-Version: 0.1-2 We believe that the bug you reported is fixed in the latest version of libxbox, which is due to be installed in the Debian FTP archive: libxbox-dev_0.1-2_i386.deb to pool/main/libx/libxbox/libxbox-dev_0.1-2_i386.deb libxbox0_0.1-2_i386.deb to pool/main/libx/libxbox/libxbox0_0.1-2_i386.deb libxbox_0.1-2.diff.gz to pool/main/libx/libxbox/libxbox_0.1-2.diff.gz libxbox_0.1-2.dsc to pool/main/libx/libxbox/libxbox_0.1-2.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. Michael Ablassmeier <[EMAIL PROTECTED]> (supplier of updated libxbox package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 31 Jul 2006 14:13:59 +0200 Source: libxbox Binary: libxbox0 libxbox-dev Architecture: source i386 Version: 0.1-2 Distribution: unstable Urgency: low Maintainer: Debian QA Group <[EMAIL PROTECTED]> Changed-By: Michael Ablassmeier <[EMAIL PROTECTED]> Description: libxbox-dev - Headers for use with libxbox libxbox0 - Shared library for Xbox Linux utilities Closes: 318548 Changes: libxbox (0.1-2) unstable; urgency=low . * QA Upload (Ack NMU, Closes: #318548) * Set Maintainer to QA Group, Orphaned: #377861 * Conforms to latest Standards Version Files: ac194a0d30801c3ee6ed304bf23beb71 576 - extra libxbox_0.1-2.dsc 4d957a87d7ed45b30240a239a9fdd651 2475 - extra libxbox_0.1-2.diff.gz c7f6e7e46cbad5a0957affc586d818e1 15886 libdevel extra libxbox-dev_0.1-2_i386.deb 85874a8d5c5d90686f2dc2956fcb0aca 9430 libs extra libxbox0_0.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEzfUpEFV7g4B8rCURAvsvAJ9nV2H6xt9MWDRRFBNfZwnjCe4UVACgxxMk tWzYY0+xEgljmIBetKyqXww= =qd6v -END PGP SIGNATURE- --- End Message ---
Processed: Re: Bug#379530: libjaxp1.3-java: FTBFS: Missing Build-Depends on 'gcj'
Processing commands for [EMAIL PROTECTED]: > severity 379530 normal Bug#379530: libjaxp1.3-java: FTBFS: Missing Build-Depends on 'gcj' Severity set to `normal' from `serious' > tags 379530 - patch Bug#379530: libjaxp1.3-java: FTBFS: Missing Build-Depends on 'gcj' Tags were: patch Tags removed: patch > tags 379530 + moreinfo Bug#379530: libjaxp1.3-java: FTBFS: Missing Build-Depends on 'gcj' There were no tags set. Tags added: moreinfo > thank 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]
