Bug#400477: [critical] sky2 patch is applied?
Package: linux-2.6 Severity: critical Tags: patch I don't see patch about Yukon FE ram buffer initialization (sky2 module) in Debian Kernel changelog: http://packages.debian.org/changelogs/pool/main/l/linux-2.6/current/changelog Please, this patch[1] is very important and is present in stable 2.6.18.2 Kernel as comment in: http://bugzilla.kernel.org/show_bug.cgi?id=6839 [1] http://bugzilla.kernel.org/attachment.cgi?id=9313action=view Best regards, Renato S. Yamane -- Renato S. Yamane Fingerprint: 68AE A381 938A F4B9 8A23 D11A E351 5030 D420 515A PGP Server: http://pgp.mit.edu/ -- KeyID: 0xD420515A http://www.renatoyamane.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409687: marked as done (FTBFS: Could not find module `MissingH.Logging.Logger':)
Your message dated Thu, 22 Feb 2007 19:47:03 + with message-id [EMAIL PROTECTED] and subject line Bug#409687: fixed in srcinst 0.8.7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: srcinst Version: 0.8.6 Severity: serious Tags: sid This package fails to build in sid (but not in etch): Automatic build of srcinst_0.8.6 on em64t by sbuild/amd64 0.52 ... dh_testdir #make test-ghc6 # Add here commands to compile the package. ./setup build srcinst.hs:25:7: Could not find module `MissingH.Logging.Logger': Use -v to see a list of the files searched for. Preprocessing executables for srcinst-0.8.4... Building srcinst-0.8.4... make: *** [build-stamp] Error 1 -- Martin Michlmayr http://www.cyrius.com/ ---End Message--- ---BeginMessage--- Source: srcinst Source-Version: 0.8.7 We believe that the bug you reported is fixed in the latest version of srcinst, which is due to be installed in the Debian FTP archive: srcinst_0.8.7.dsc to pool/main/s/srcinst/srcinst_0.8.7.dsc srcinst_0.8.7.tar.gz to pool/main/s/srcinst/srcinst_0.8.7.tar.gz srcinst_0.8.7_i386.deb to pool/main/s/srcinst/srcinst_0.8.7_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. John Goerzen [EMAIL PROTECTED] (supplier of updated srcinst package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 22 Feb 2007 05:12:48 -0600 Source: srcinst Binary: srcinst Architecture: source i386 Version: 0.8.7 Distribution: unstable Urgency: low Maintainer: John Goerzen [EMAIL PROTECTED] Changed-By: John Goerzen [EMAIL PROTECTED] Description: srcinst- Build and install Debian packages completely from source Closes: 409687 Changes: srcinst (0.8.7) unstable; urgency=low . * Updated for newer MissingH. Closes: #409687. Files: 61b8ca5c6d04d028c4eac097b21d55e8 605 utils optional srcinst_0.8.7.dsc f1321a9ef96ce0d32a2721dd7e5a8a33 13910 utils optional srcinst_0.8.7.tar.gz f3304fe727fcb5c2662640e1ef7d39b2 208676 utils optional srcinst_0.8.7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF3e+mTvSuJuBy3ggRAt4rAJwNPGK+uP6HZeUOBTbGOlJ1ejLsyACeKS+c wQYbR/sTpbW+HYiuRPFy1Es= =y33/ -END PGP SIGNATURE- ---End Message---
Bug#411652: marked as done (bacula-sd: fails to install - dependency problem)
Your message dated Thu, 22 Feb 2007 19:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#411652: fixed in bacula 1.38.11-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: bacula-sd Version: 1.38.11-7+b1 Severity: grave Justification: renders package unusable at install time I have the following messages : colibri:~# apt-get install bacula-common bacula-sd 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. The following information may help to resolve the situation: The following packages have unmet dependencies: bacula-sd: PreDepends: bacula-common (= 1.38.11-7+b1) but 1.38.11-7 is to be installed E: Broken packages -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-k7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) ---End Message--- ---BeginMessage--- Source: bacula Source-Version: 1.38.11-8 We believe that the bug you reported is fixed in the latest version of bacula, which is due to be installed in the Debian FTP archive: bacula-client_1.38.11-8_all.deb to pool/main/b/bacula/bacula-client_1.38.11-8_all.deb bacula-common_1.38.11-8_all.deb to pool/main/b/bacula/bacula-common_1.38.11-8_all.deb bacula-console-gnome_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-console-gnome_1.38.11-8_amd64.deb bacula-console-wx_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-console-wx_1.38.11-8_amd64.deb bacula-console_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-console_1.38.11-8_amd64.deb bacula-director-common_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-director-common_1.38.11-8_amd64.deb bacula-director-mysql_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-director-mysql_1.38.11-8_amd64.deb bacula-director-pgsql_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-director-pgsql_1.38.11-8_amd64.deb bacula-director-sqlite3_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-director-sqlite3_1.38.11-8_amd64.deb bacula-director-sqlite_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-director-sqlite_1.38.11-8_amd64.deb bacula-fd_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-fd_1.38.11-8_amd64.deb bacula-sd-mysql_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-sd-mysql_1.38.11-8_amd64.deb bacula-sd-pgsql_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-sd-pgsql_1.38.11-8_amd64.deb bacula-sd-sqlite3_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-sd-sqlite3_1.38.11-8_amd64.deb bacula-sd-sqlite_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-sd-sqlite_1.38.11-8_amd64.deb bacula-sd_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-sd_1.38.11-8_amd64.deb bacula-server_1.38.11-8_all.deb to pool/main/b/bacula/bacula-server_1.38.11-8_all.deb bacula-traymonitor_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-traymonitor_1.38.11-8_amd64.deb bacula_1.38.11-8.diff.gz to pool/main/b/bacula/bacula_1.38.11-8.diff.gz bacula_1.38.11-8.dsc to pool/main/b/bacula/bacula_1.38.11-8.dsc bacula_1.38.11-8_all.deb to pool/main/b/bacula/bacula_1.38.11-8_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. John Goerzen [EMAIL PROTECTED] (supplier of updated bacula package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 22 Feb 2007 12:58:55 -0600 Source: bacula Binary: bacula-director-sqlite3 bacula-console bacula-director-sqlite bacula-client bacula-traymonitor bacula-console-gnome bacula bacula-director-pgsql bacula-director-common bacula-fd bacula-console-wx bacula-director-mysql bacula-sd-pgsql bacula-common bacula-server bacula-sd-sqlite bacula-sd bacula-sd-sqlite3 bacula-sd-mysql Architecture: source amd64 all Version: 1.38.11-8 Distribution: unstable Urgency: high Maintainer: John Goerzen [EMAIL PROTECTED] Changed-By:
Bug#411961: watchdog: wd_keepalive uses /KA_PIDFILE as pidfile
On Thu, Feb 22, 2007 at 08:49:16AM +0100, Mario 'BitKoenig' Holbe wrote: since 5.3-1 wd_keepalive stores it's pid in /KA_PIDFILE and not in /var/run/wd_keepalive.pid anymore. This breaks the wd_keepalive init-script. Yes, I know. This is a stupid bug that occured during upstream release. I'm already preparing a new upstream version which will result in a new Debian package as well. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
Bug#362588: marked as done (dvifb: does not respond to pressed keys or mouse)
Your message dated Thu, 22 Feb 2007 19:32:08 + with message-id [EMAIL PROTECTED] and subject line Bug#362588: fixed in tmview 1:01.03-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) ---BeginMessage--- Package: dvifb Version: 1:01.03-11 Severity: grave Justification: renders package unusable When using dvifb on my G3, it will render upper part of the first page of the dvi file correctly (by upper part I mean the portion that fits on the screen). Then it will not respond properly to any keys pressed on the keyboard (i.e. q or ?? won't work), only Control-C will work for quitting dvifb (it would be very bad if that wouldn't work either). Mouse operation does not work correctly either. (When I press the left button, nothing happens most of the time, but sometimes, things scroll to the left. Pressing the right button and moving the mouse allows me to scroll upwards until all of the page is gone.) The GPM mouse event repeat type is set to msc, i.e. MouseSystems protocol as the dvifb documentation suggests. If you need further information, I am happy to assist in any way I can. Kind regards, Manuel -- System Information: Debian Release: 3.1 Architecture: powerpc (ppc) Kernel: Linux 2.4.32 Locale: LANG=en_GB.ISO-8859-1, LC_CTYPE=en_GB.ISO-8859-1 (charmap=ISO-8859-1) Versions of packages dvifb depends on: ii gpm 1.19.6-19sarge1 General Purpose Mouse Interface ii libc62.3.2.ds1-22GNU C Library: Shared libraries an ii libkpathsea3 2.0.2-30sarge4 path search library for teTeX (run ii tetex-bin2.0.2-30sarge4 The teTeX binary files -- no debconf information ---End Message--- ---BeginMessage--- Source: tmview Source-Version: 1:01.03-13 We believe that the bug you reported is fixed in the latest version of tmview, which is due to be installed in the Debian FTP archive: dvifb_01.03-13_i386.deb to pool/main/t/tmview/dvifb_01.03-13_i386.deb dvilx_01.03-13_i386.deb to pool/main/t/tmview/dvilx_01.03-13_i386.deb dvisvga_01.03-13_i386.deb to pool/main/t/tmview/dvisvga_01.03-13_i386.deb tmview_01.03-13.diff.gz to pool/main/t/tmview/tmview_01.03-13.diff.gz tmview_01.03-13.dsc to pool/main/t/tmview/tmview_01.03-13.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. Sam Hocevar (Debian packages) [EMAIL PROTECTED] (supplier of updated tmview package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 22 Feb 2007 20:09:00 +0100 Source: tmview Binary: dvifb dvisvga dvilx Architecture: source i386 Version: 1:01.03-13 Distribution: unstable Urgency: high Maintainer: Sam Hocevar (Debian packages) [EMAIL PROTECTED] Changed-By: Sam Hocevar (Debian packages) [EMAIL PROTECTED] Description: dvifb - dvi viewer for framebuffer devices dvilx - dvi viewer for X dvisvga- dvi viewer for SVGAlib Closes: 349889 362588 Changes: tmview (1:01.03-13) unstable; urgency=high . * fb/writefb.c: + Fix character reading on big-endian machines that made dvifb unusable on PowerPC (Closes: #362588). * doc/tmview.1: + Fix formatting errors in the manpage, thanks to Nicolas François (Closes: #349889). Files: d017e3a7ee049e2ce259f6e972dc0a27 643 tex optional tmview_01.03-13.dsc d72393435576e3f09ff60df67b24f2c2 25243 tex optional tmview_01.03-13.diff.gz 263f31c9a568bf7d6142a321ce3f798f 130422 tex optional dvisvga_01.03-13_i386.deb 8daef913e20b5c66dfc948c34c90934d 131830 tex optional dvilx_01.03-13_i386.deb 613af95a845e34a7639591328a032ea2 130938 tex optional dvifb_01.03-13_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF3exDfPP1rylJn2ERAjNMAJ0YDf9ze086sNM3FgGtMbHtSTOzsgCgjcm3 cn/6pbwM3JKmO4ptIWajRvw= =Qtfc -END PGP SIGNATURE- ---End Message---
Processed: Re: Bug#411978: libnss-mdns: Should be in /lib
Processing commands for [EMAIL PROTECTED]: tag 411978 + pending Bug#411978: libnss-mdns: Should be in /lib There were no tags set. Tags added: pending 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]
Bug#412003: FTBFS (alpha): DEFINEMACRO: max. 61 arguments supported, not 1
Package: yodl Version: 2.10-1 Severity: serious Justification: no longer builds from source yodl does not build on Alpha: [...] ./build manual mkdir -p html latex pdf ps txt /tmp/yodl-2.10/src/bin/yodl -D XXMACROPATH=. -I .:/tmp/yodl-2.10/macros/yodl -o out html manual Yodl2html 2.10 std.html.yo:100: DEFINEMACRO: max. 61 arguments supported, not 1 std.html.yo:106: DEFINEMACRO: max. 61 arguments supported, not 3 std.html.yo:110: DEFINEMACRO: max. 61 arguments supported, not 1 std.html.yo:113: DEFINEMACRO: max. 61 arguments supported, not 0 std.html.yo:121: DEFINEMACRO: max. 61 arguments supported, not 0 std.html.yo:131: DEFINEMACRO: max. 61 arguments supported, not 3 std.html.yo:137: DEFINEMACRO: max. 61 arguments supported, not 1 std.html.yo:141: DEFINEMACRO: max. 61 arguments supported, not 1 std.html.yo:146: DEFINEMACRO: max. 61 arguments supported, not 3 std.html.yo:156: DEFINEMACRO: max. 61 arguments supported, not 1 Terminating after 10 errors execute - program indicates failure (status 256) execute - program indicates failure (status 256) execute - program indicates failure (status 256) execute - program indicates failure (status 256) make: *** [build-stamp] Error 1 [...] Full log at http://buildd.debian.org/fetch.cgi?pkg=yodlarch=alphaver=2.10-1stamp=1171904919 I have no idea why this happens only on Alpha. The compiler warnings might be something to look at. Falk -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: alpha Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.20 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411978: libnss-mdns: Should be in /lib
tag 411978 + pending stop (Fix uploaded to DELAYED/2 this afternoon.) -- Loïc Minier [EMAIL PROTECTED]
Bug#409681: marked as done (Broken depends on non-existing package)
Your message dated Thu, 22 Feb 2007 18:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#409681: fixed in missingh 0.18.1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: libhugs-missingh Version: 0.18.0 Severity: grave Tags: sid libhugs-missingh in sid (but not in etch) has a dependency on libhugs-hunit that cannot be fulfilled: | Depends: hugs (= 98.200503.08), libhugs-filepath, libhugs-hunit, libhugs-hslogger but libhugs-hunit is not in testing or sid anymore: 2331:[EMAIL PROTECTED]: ~] madison libhugs-hunit libhugs-hunit | 1.0-8 |stable | all 2332:[EMAIL PROTECTED]: ~] -- Martin Michlmayr http://www.cyrius.com/ ---End Message--- ---BeginMessage--- Source: missingh Source-Version: 0.18.1 We believe that the bug you reported is fixed in the latest version of missingh, which is due to be installed in the Debian FTP archive: libghc6-missingh-dev_0.18.1_i386.deb to pool/main/m/missingh/libghc6-missingh-dev_0.18.1_i386.deb libhugs-missingh_0.18.1_all.deb to pool/main/m/missingh/libhugs-missingh_0.18.1_all.deb missingh-doc_0.18.1_all.deb to pool/main/m/missingh/missingh-doc_0.18.1_all.deb missingh_0.18.1.dsc to pool/main/m/missingh/missingh_0.18.1.dsc missingh_0.18.1.tar.gz to pool/main/m/missingh/missingh_0.18.1.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. John Goerzen [EMAIL PROTECTED] (supplier of updated missingh package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 22 Feb 2007 06:58:05 -0600 Source: missingh Binary: libhugs-missingh libghc6-missingh-dev missingh-doc Architecture: source i386 all Version: 0.18.1 Distribution: unstable Urgency: low Maintainer: John Goerzen [EMAIL PROTECTED] Changed-By: John Goerzen [EMAIL PROTECTED] Description: libghc6-missingh-dev - Library of utility functions for Haskell, GHC6 package libhugs-missingh - Library of utility functions for Haskell, Hugs package missingh-doc - Documentation for Haskell utility library Closes: 409681 Changes: missingh (0.18.1) unstable; urgency=low . * Fixed hugs HUnit dep. Closes: #409681. Files: 235ae445d8294e5bdac37e1cf0ccb6e0 924 devel optional missingh_0.18.1.dsc 886d376ace957d1c142f3fdf6bda6e72 129194 devel optional missingh_0.18.1.tar.gz e47f37dc7d3c49f4675266990d8a6d20 91964 devel optional libhugs-missingh_0.18.1_all.deb 77678b2b4b3383e3debe6658c0450c70 93486 doc optional missingh-doc_0.18.1_all.deb 4037b1c7104d520e22e63f22bdb6582b 942386 devel optional libghc6-missingh-dev_0.18.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF3d4oTvSuJuBy3ggRApJVAJ0XVJOKCgwWAJsgmnr9Zvf0iDinegCdGgcx PWDsjuLxxy8VG0/7UcFv1Fw= =V01J -END PGP SIGNATURE- ---End Message---
Bug#410463: [Pkg-octave-devel] Bug#410463: octave2.9-forge: FTBFS: error: invalid matrix index = 1
* Kurt Roeckx [EMAIL PROTECTED] [2007-02-22 18:36]: I don't understand what the problem is getting the new version into testing thru unstable. octave2.9 2.9.9-8 is already approved by the release team to go to testing, but it being blocked by the RC bug (#411863). There is no reason to believe that this bug doesn't affect testing, so you should probably mark it as such. You are right, I was confused. I forgot that we asked for unblocking 2.9.9-8. In this case, I will prepare 2.9.9-8etch1 (2.9.9-9 has been released to experimental). Thanks, -- Rafael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#411975: file conflicts between libdballe-dev and other liballe-* packages
Processing commands for [EMAIL PROTECTED]: reassign 411975 libdballe-dev,libdballef-dev Bug#411975: file conflicts between libdballe-dev and other liballe-* packages Warning: Unknown package 'libdballef-dev' Warning: Unknown package 'libdballe-db-dev' Warning: Unknown package 'libdballe-msg-dev' Warning: Unknown package 'libdballef-dev' Bug reassigned from package `libdballe-dev, libdballef-dev, libdballe-db-dev, libdballe-msg-dev' to `libdballe-dev,libdballef-dev'. -- 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 411944
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.27 tags 411944 + upstream confirmed Bug#411944: CVE-2007-1006: format string overflows Tags were: fixed-upstream patch security Tags added: upstream, 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#411988: libswt3.2-gtk-jni 3.2.1-5 depends on libc6 (= 2.5) and is uninstallable
Package: libswt3.2-gtk-jni Version: 3.2.1-5 Severity: serious The following packages are BROKEN: libswt3.2-gtk-jni The following packages will be upgraded: eclipse eclipse-jdt eclipse-jdt-gcj eclipse-pde eclipse-pde-gcj eclipse-platform eclipse-platform-gcj eclipse-rcp eclipse-rcp-gcj eclipse-source libswt3.2-gtk-gcj libswt3.2-gtk-java 13 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. The following packages have unmet dependencies: libswt3.2-gtk-jni: Depends: libc6 (= 2.5) but 2.3.6.ds1-13 is installed. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-k1 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages libswt3.2-gtk-jni depends on: ii libatk1.0-0 1.12.4-2 The ATK accessibility toolkit ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libcairo2 1.2.4-4 The Cairo 2D vector graphics libra ii libglib2.0-02.12.6-2 The GLib library of C routines ii libgtk2.0-0 2.8.20-5 The GTK+ graphical user interface ii libxtst61:1.0.1-5X11 Testing -- Resource extension Versions of packages libswt3.2-gtk-jni recommends: ii libgcc1 1:4.1.1-21 GCC support library ii libgl1-mesa-glx [libgl1] 6.5.1-0.5 A free implementation of the OpenG ii libglu1-mesa [libglu1]6.5.1-0.5 The OpenGL utility library (GLU) ii libgnome2-0 2.16.0-2 The GNOME 2 library - runtime file ii libgnomeui-0 2.14.1-2 The GNOME 2 libraries (User Interf ii libgnomevfs2-01:2.14.2-6 GNOME virtual file-system (runtime ii libnspr4-0d 1.8.0.9-1 NetScape Portable Runtime Library ii libstdc++64.1.1-21 The GNU Standard C++ Library v3 ii libxul0d 1.8.0.9-1 Gecko engine library -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410463: [Pkg-octave-devel] Bug#410463: octave2.9-forge: FTBFS: error: invalid matrix index = 1
On Wed, Feb 21, 2007 at 10:46:27PM +0100, Rafael Laboissiere wrote: * Thomas Weber [EMAIL PROTECTED] [2007-02-21 15:23]: Package: octave2.9 reassign 410463 octave2.9-forge thanks Am Samstag, den 10.02.2007, 21:38 +0100 schrieb Kurt Roeckx: error: invalid matrix index = 1 error: evaluating assignment expression near line 158, column 12 error: evaluating if command near line 156, column 3 error: called from `test' in file `/usr/share/octave/2.9.9/m/testfun/test.m' error: near line 7 of file `fntests.m' This is a bug in the way octave2.9-forge creates its test files (they are simply not valid). However, fixing this turned up a bug in Octave 2.9. This bug is nasty, as it eats all memory during octave2.9-forge's unit tests. I guess buildd admins won't like that too much. Fortunately, it's already fixed upstream and a small patch suffices. Although this bug does not concern the versions of the packages now in testing (octave2.9_2.9.9-7 and octave2.9-forge_2006.07.09+dfsg1-7), I understand that it would be good to have the version in testing also fixed. So either we fix the tests and ask debian-release for a new version of both octave2.9 and octave2.9-forge or we disable them and try to get octave2.9-forge in its current state into Etch. Alternatively, we could let things as they are now. After all, the packages in testing are not affected. At any rate, if we really want this bug fixed in testing, we would maximize the odds of having octave2.9 accepted by applyin both patches 50_correct_test and 50_parse-inline-brackets to 2.9.9-7 and asking the release managers to consider unblocking the resulting 2.2.9-7etch1 version. I don't understand what the problem is getting the new version into testing thru unstable. octave2.9 2.9.9-8 is already approved by the release team to go to testing, but it being blocked by the RC bug (#411863). There is no reason to believe that this bug doesn't affect testing, so you should probably mark it as such. If you get a new version of octave2.9 in testing, octave2.9-forge in testing will have a problem too (#410463). I suggest you just fix things in unstable and ask the release team to approve the changes. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411978: libnss-mdns: Should be in /lib
Package: libnss-mdns Version: 0.9-0.1 Severity: critical Justification: breaks unrelated software Hi, When /usr is not mounted and libnss-mdns is installed hostname lookups will fail because lib_mdns* is in /usr/lib instead of /lib. Apart from the more obvious things like nfs-mounting /usr, something like postfix can also fail as it just copies the nss modules from /lib into it's chroot.. Causing a broken setup for resolving, which in turn can cause mail bounces.. Sjoerd -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-xen-686 Locale: LANG=C, LC_CTYPE=nl_NL (charmap=ISO-8859-1) Versions of packages libnss-mdns depends on: ii avahi-daemon0.6.16-2 Avahi mDNS/DNS-SD daemon ii base-files 4Debian base system miscellaneous f ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii perl5.8.8-7 Larry Wall's Practical Extraction libnss-mdns recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411818: openafs-modules-source: Fails to compile/install on 2.6.8.3-mckinley-smp (ia64): linux/modversions.h
Ippokratis Pandis [EMAIL PROTECTED] writes: Well, it looks like the problem is specific to ia64 with 2.6 kernel. It wouldn't surprise me too much if the ia64 port has bit-rotted a little. I'm not sure how many people are using that architecture with AFS. Thank you for the additional information. I want to look it over more thoroughly and try to understand what's happening, but I don't have the time to do so immediately. I'll try to get to that soon, and if you haven't heard from me in a week, please feel free to ping me. (In the meantime, you may also want to consider raising this on openafs-info and seeing if anyone else has any ideas, although the installation problem may be due to the Debian-specific patches to rename the module to openafs instead of libafs.) -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411961: marked as done (watchdog: wd_keepalive uses /KA_PIDFILE as pidfile)
Your message dated Thu, 22 Feb 2007 11:17:07 + with message-id [EMAIL PROTECTED] and subject line Bug#411961: fixed in watchdog 5.3.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: watchdog Version: 5.3-1 Severity: grave Hello, since 5.3-1 wd_keepalive stores it's pid in /KA_PIDFILE and not in /var/run/wd_keepalive.pid anymore. This breaks the wd_keepalive init-script. Thanks for your work regards Mario -- Oh Du mein Koenig ... Eine Netzgroesse schrieb mal sinngemaess: Du musst es so lesen wie ich es meine, nicht so wie ich es schreibe. Ich meine es natuerlich so, wie Du es schreibst 8--) O.G. Schwenk - de.comm.chatsystems signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: watchdog Source-Version: 5.3.1-1 We believe that the bug you reported is fixed in the latest version of watchdog, which is due to be installed in the Debian FTP archive: watchdog_5.3.1-1.diff.gz to pool/main/w/watchdog/watchdog_5.3.1-1.diff.gz watchdog_5.3.1-1.dsc to pool/main/w/watchdog/watchdog_5.3.1-1.dsc watchdog_5.3.1-1_i386.deb to pool/main/w/watchdog/watchdog_5.3.1-1_i386.deb watchdog_5.3.1.orig.tar.gz to pool/main/w/watchdog/watchdog_5.3.1.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. Michael Meskes [EMAIL PROTECTED] (supplier of updated watchdog package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 22 Feb 2007 11:46:30 +0100 Source: watchdog Binary: watchdog Architecture: source i386 Version: 5.3.1-1 Distribution: unstable Urgency: low Maintainer: Michael Meskes [EMAIL PROTECTED] Changed-By: Michael Meskes [EMAIL PROTECTED] Description: watchdog - software watchdog Closes: 411961 Changes: watchdog (5.3.1-1) unstable; urgency=low . * New upstream version, closes: #411961 Files: fabf1e97915f239b9b7fec10bdc86bcb 588 admin extra watchdog_5.3.1-1.dsc e14e9e54ef839f9f74b62c175298914d 167983 admin extra watchdog_5.3.1.orig.tar.gz 699fd56848d1eedd68d4c2ab1305dc2d 20 admin extra watchdog_5.3.1-1.diff.gz a2cf70255527148df843b4559588debd 64802 admin extra watchdog_5.3.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF3XaKVkEm8inxm9ERAnndAJ93M6nCNNBe93InEBqSHcJ1pLjkjACfdsqT G8jZw92P3Id3JGx3YzIlYqI= =XXGh -END PGP SIGNATURE- ---End Message---
Bug#411975: file conflicts between libdballe-dev and other liballe-* packages
Package: libdballe-dev, libdballef-dev, libdballe-db-dev, libdballe-msg-dev Severity: serious Justification: file conflicts, policy violation hi, both libdballe-dev and libdballef-dev do ship `/usr/lib/libdballef.a' amongst other files but do not conflict or add a diversion, thus fail on installation in the same environment: [..] dpkg: error processing /var/cache/apt/archives/libdballef-dev_3.0.1-1_amd64.deb (--unpack): trying to overwrite `/usr/lib/libdballef.a', which is also in package libdballe-dev [..] also, libdballe-db-dev conflicts with libdballe-msg-dev: [..] Unpacking libdballe-dev (from .../libdballe-dev_2.6-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libdballe-dev_2.6-1_amd64.deb (--unpack): trying to overwrite `/usr/include/dballe/msg/level.h', which is also in package libdballe-msg-dev [..] detailed list of file conflicts: http://qa.debian.org/~filippo/file_conflicts/unstable-conflicts bye, - michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410859: liboil0.3: wrongly assumes that all Intel chips support CP14 timestamp
I think all XScale processors have CP14 timestamp (see
http://download.intel.com/design/intelxscale/XScaleDatasheet4.pdf) but
it's in register 1, not register 0. The original report is right in
that StrongArm processors do not have a CP14. Therefore the following
*should* work:
--- liboil-0.3.10.orig/liboil/liboilcpu.c 2006-11-06 01:37:03.0
+
+++ liboil-0.3.10/liboil/liboilcpu.c2007-02-22 13:41:31.0 +
@@ -620,7 +620,7 @@
{
unsigned int ts;
__asm__ __volatile__ (
-mrc p14, 0, %0, c0, c0, 0 \n
+mrc p14, 0, %0, c1, c0, 0 \n
: =r (ts));
return ts;
}
@@ -629,7 +629,8 @@
oil_cpu_detect_arm(void)
{
#ifdef __linux__
- int arm_implementer;
+ int arm_implementer = 0;
+ char arm_architecture = 0;
char *cpuinfo;
char *s;
@@ -640,18 +641,16 @@
arm_implementer = strtoul (s, NULL, 0);
free(s);
}
+ s = get_cpuinfo_line(cpuinfo, CPU architecture);
+ if (s) {
+char *p = s + strspn(s, \t);
+arm_architecture = *p;
+free(s);
+ }
- switch(arm_implementer) {
-case 0x69: /* Intel */
- /* assume that all Intel chips support CP14 timestamp */
- _oil_profile_stamp = oil_profile_stamp_xscale;
- break;
-case 0x41: /* ARM */
- /* ARM chips are known to not have timestamping available from
- * user space */
- break;
-default:
- break;
+ /* only Intel XScale processors support CP14 timestamp */
+ if (arm_implementer == 0x69 arm_architecture == '5') {
+_oil_profile_stamp = oil_profile_stamp_xscale;
}
free (cpuinfo);
-- END --
In practice it still results in SIGILL, so I agree we should never use
oil_profile_stamp_xscale().
Ben.
--
Ben Hutchings
Beware of bugs in the above code;
I have only proved it correct, not tried it. - Donald Knuth
signature.asc
Description: This is a digitally signed message part
Bug#411537: Only half-fixed: platex is still a problem
# copy of a mail already sent to [EMAIL PROTECTED] (which is down until # tomorrow morning) clone 411537 -1 found -1 2005.dfsg.2-12 retitle -1 installs /usr/bin/platex, which is also in package ptex-bin thanks As indicated in the bug log, there's one more problem to solve. We're not there yet, but the discussion among the upstream developers shows progress. Essentially, a solution seems to be decided upon, but the implementation is unclear. I'd rather wait for them to decide on that, in order to not deviate from upstream. Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Processed: Only half-fixed
Processing commands for [EMAIL PROTECTED]: clone 411537 -1 Bug#411537: texlive-extra-utils: Installs /usr/bin/dvidvi, which is also in package dvidvi Bug 411537 cloned as bug 411969. found -1 2005.dfsg.2-12 Bug#411969: texlive-extra-utils: Installs /usr/bin/dvidvi, which is also in package dvidvi Bug marked as found in version 2005.dfsg.2-12. retitle -1 installs /usr/bin/platex, which is also in package ptex-bin Bug#411969: texlive-extra-utils: Installs /usr/bin/dvidvi, which is also in package dvidvi Changed Bug title. (By the way, that 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#410463: [Pkg-octave-devel] Bug#410463: octave2.9-forge: FTBFS: error: invalid matrix index = 1
* Rafael Laboissiere [EMAIL PROTECTED] [2007-02-21 22:46]: Although this bug does not concern the versions of the packages now in testing (octave2.9_2.9.9-7 and octave2.9-forge_2006.07.09+dfsg1-7), I understand that it would be good to have the version in testing also fixed. So either we fix the tests and ask debian-release for a new version of both octave2.9 and octave2.9-forge or we disable them and try to get octave2.9-forge in its current state into Etch. Alternatively, we could let things as they are now. After all, the packages in testing are not affected. At any rate, if we really want this bug fixed in testing, we would maximize the odds of having octave2.9 accepted by applyin both patches 50_correct_test and 50_parse-inline-brackets to 2.9.9-7 and asking the release managers to consider unblocking the resulting 2.2.9-7etch1 version. In the above and in other messages I meant 2.9.9-6 (not 2.9.9-7) as the version in testing. Sorry for the confusion. In preparation for the 2.9.9-6etch1 release, I created a branch for octave2.9/etch in the SVN repository. Caveat: this branch is not yet fully tested. -- Rafael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#376812: -fno-strict-aliasing didn't work
On Thu, Feb 22, 2007 at 05:18:46AM +0200, Guillem Jover wrote: Hey, On Sun, 2007-02-18 at 22:05:01 +0100, Wouter Verhelst wrote: I rebuilt the package using -fno-strict-aliasing and -g (which took quite some time), and ran it inside an etch chroot on a sarge box; the kernel was a stock sarge kernel with the sarge 3dfx module. That didn't fix the problem. Thanks for testing! Ok, could you try the packages at: http://people.debian.org/~guillem/glide/ Yes, these do work. You may want to change the version number, though, because I got a message from dpkg that I was downgrading the package. -- Lo-lan-do Home is where you have to wash the dishes. -- #debian-devel, Freenode, 2004-09-22 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409685: marked as done (FTBFS: Could not find module `MissingH.GetOpt')
Your message dated Thu, 22 Feb 2007 19:17:01 + with message-id [EMAIL PROTECTED] and subject line Bug#409685: fixed in arch2darcs 1.0.9 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: arch2darcs Version: 1.0.8 Severity: serious Tags: sid This package fails to build in sid (but not in etch): Automatic build of arch2darcs_1.0.8 on em64t by sbuild/amd64 0.52 ... configure: Using runghc found on system at: /usr/bin/runghc configure: No runhugs found configure: No happy found configure: No alex found configure: Using hsc2hs: /usr/bin/hsc2hs configure: No c2hs found configure: No cpphs found configure: No greencard found ./setup build arch2darcs.hs:31:7: Could not find module `MissingH.GetOpt': Use -v to see a list of the files searched for. Preprocessing executables for arch2darcs-1.0.6... Building arch2darcs-1.0.6... make[1]: *** [all] Error 1 make[1]: Leaving directory `/build/tbm/arch2darcs-1.0.8' make: *** [build-stamp] Error 2 -- Martin Michlmayr http://www.cyrius.com/ ---End Message--- ---BeginMessage--- Source: arch2darcs Source-Version: 1.0.9 We believe that the bug you reported is fixed in the latest version of arch2darcs, which is due to be installed in the Debian FTP archive: arch2darcs_1.0.9.dsc to pool/main/a/arch2darcs/arch2darcs_1.0.9.dsc arch2darcs_1.0.9.tar.gz to pool/main/a/arch2darcs/arch2darcs_1.0.9.tar.gz arch2darcs_1.0.9_i386.deb to pool/main/a/arch2darcs/arch2darcs_1.0.9_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. John Goerzen [EMAIL PROTECTED] (supplier of updated arch2darcs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 22 Feb 2007 05:11:54 -0600 Source: arch2darcs Binary: arch2darcs Architecture: source i386 Version: 1.0.9 Distribution: unstable Urgency: low Maintainer: John Goerzen [EMAIL PROTECTED] Changed-By: John Goerzen [EMAIL PROTECTED] Description: arch2darcs - Convert Arch/tla repositories to Darcs Closes: 409685 Changes: arch2darcs (1.0.9) unstable; urgency=low . * Update to build against newer MissingH. Closes: #409685. Files: 904a5bfcf17a318022b267aa3282d1b0 614 devel optional arch2darcs_1.0.9.dsc 6ede53ff500ebf39690b1ac2d6e0e7f9 14570 devel optional arch2darcs_1.0.9.tar.gz 444aa13ec90f33e524a55e8f5cef7bef 196308 devel optional arch2darcs_1.0.9_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF3emcTvSuJuBy3ggRAmuxAJ9JgnfE+whuTNumg+U13JRPcmuFAgCfVBoV VAJTXkSVC2qZjLFLBIbCjiI= =OWpe -END PGP SIGNATURE- ---End Message---
Processed: setting package to zd1211-firmware, tagging 363271, tagging 383604, tagging 411912
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.27 package zd1211-firmware Ignoring bugs not assigned to: zd1211-firmware tags 363271 + pending Bug#363271: zd1211-firmware: new upstream version available There were no tags set. Tags added: pending tags 383604 + pending Bug#383604: zd1211-firmware: files at the wrong location for kernel tree's zd1211rw There were no tags set. Tags added: pending tags 411912 + pending Bug#411912: debian etch should ship with working zd1211rw firmware 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: severity of 400477 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 severity 400477 important Bug#400477: sky2 module (patch available) Severity set to `important' from `critical' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#412003: FTBFS (alpha): DEFINEMACRO: max. 61 arguments supported, not 1
Dear Falk Hueffner, you wrote: Package: yodl Version: 2.10-1 Severity: serious Justification: no longer builds from source Brrr... Sounds ominous. Especially since the 2.04a *did* build on Alpha. I looked at the logs, and did notice some unexpected and possibly serious warnings, which definitely need some attention. One of the changes implemented in version 2.10 is the use of size_t rather than unsigned. It looks as though that's both the cause of the unexpected warnings and the cause of the execution problem. Actually, yodl builds fine, but then its execution shows unexpected behavior. E.g., messages like std.html.yo:100: DEFINEMACRO: max. 61 arguments supported, not 1 are of course remarkable: if 61 is the maximum number, then 1 should not qualify for an error, should it? Now my problem is that as far as I know nobody in my environment uses the Alpha running Debian Linux. I can ask around, maybe one of my colleagues has an Alpha. But on the other hand: maybe you could provide me with a (temporary) account on an Alpha so I can research the problem's cause myself rather than using a real `man-in-the-middle' who I would constantly have to ask to perform the next test. So, thanks for letting me know about this problem. I'll certainly have a look at it as soon as possible. Depending on me gaining access to an Alpha, the repair may either come quickly or not as quickly. Cheers, -- Frank B. Brokken Computing Center, University of Groningen (+31) 50 363 9281 Public PGP key: http://pgp.surfnet.nl:11371/ Key Fingerprint: 8E36 9FC4 1DAA FCDF 1A0D B19F DAC4 BE50 38C6 6170 signature.asc Description: Digital signature
Bug#410859: liboil0.3: wrongly assumes that all Intel chips support CP14 timestamp
This was already fixed upstream on 1st January
(http://webcvs.freedesktop.org/liboil/liboil/liboil/liboilcpu.c?r1=1.36r2=1.37)
so I'm going to apply that change and upload:
--- liboilcpu.c 2006/11/06 02:04:58 1.36
+++ liboilcpu.c 2007/01/01 09:33:33 1.37
@@ -615,15 +615,17 @@
/* arm */
#ifdef __arm__
+#if 0
static unsigned long
oil_profile_stamp_xscale(void)
{
unsigned int ts;
__asm__ __volatile__ (
-mrc p14, 0, %0, c0, c0, 0 \n
+mrc p14, 0, %0, c1, c0, 0 \n
: =r (ts));
return ts;
}
+#endif
static void
oil_cpu_detect_arm(void)
@@ -643,9 +645,6 @@
switch(arm_implementer) {
case 0x69: /* Intel */
- /* assume that all Intel chips support CP14 timestamp */
- _oil_profile_stamp = oil_profile_stamp_xscale;
- break;
case 0x41: /* ARM */
/* ARM chips are known to not have timestamping available from
* user space */
-- END --
Ben.
--
Ben Hutchings
Beware of bugs in the above code;
I have only proved it correct, not tried it. - Donald Knuth
signature.asc
Description: This is a digitally signed message part
Bug#412021: grub fails to cope with '/boot' on different partition to '/'
Package: grub Version: 0.97-23 Severity: critical Justification: breaks the whole system My /boot partition is on /dev/hda11, so in menu.lst it says: root (hd0,11) update-grub trashes that and resets each case to: root (hd0,0) This happens whenever a new kernel is installed and it leaves the system unbootable. My workaround is to manually edit menu.lst after each time a new kernel is installed and before rebooting. baron:/boot/grub# grep -v -e '^$' -e '^#' menu.lst default 0 timeout 5 color cyan/blue white/blue title Debian GNU/Linux, kernel 2.6.18.baron.20070221.0915 root(hd0,11) kernel /vmlinuz-2.6.18.baron.20070221.0915 root=/dev/hda1 ro initrd /initrd.img-2.6.18.baron.20070221.0915 savedefault title Debian GNU/Linux, kernel 2.6.18.baron.20070221.0915 (single-user mode) root(hd0,11) kernel /vmlinuz-2.6.18.baron.20070221.0915 root=/dev/hda1 ro single initrd /initrd.img-2.6.18.baron.20070221.0915 savedefault title Debian GNU/Linux, kernel 2.6.18-custom.01 root(hd0,11) kernel /vmlinuz-2.6.18-custom.01 root=/dev/hda1 ro initrd /initrd.img-2.6.18-custom.01 savedefault title Debian GNU/Linux, kernel 2.6.18-custom.01 (single-user mode) root(hd0,11) kernel /vmlinuz-2.6.18-custom.01 root=/dev/hda1 ro single initrd /initrd.img-2.6.18-custom.01 savedefault title Debian GNU/Linux, kernel 2.6.18-3-686 root(hd0,11) kernel /vmlinuz-2.6.18-3-686 root=/dev/hda1 ro initrd /initrd.img-2.6.18-3-686 savedefault title Debian GNU/Linux, kernel 2.6.18-3-686 (single-user mode) root(hd0,11) kernel /vmlinuz-2.6.18-3-686 root=/dev/hda1 ro single initrd /initrd.img-2.6.18-3-686 savedefault title Debian GNU/Linux, kernel 2.6.17-2-686 root(hd0,11) kernel /vmlinuz-2.6.17-2-686 root=/dev/hda1 ro initrd /initrd.img-2.6.17-2-686 savedefault title Debian GNU/Linux, kernel 2.6.17-2-686 (single-user mode) root(hd0,11) kernel /vmlinuz-2.6.17-2-686 root=/dev/hda1 ro single initrd /initrd.img-2.6.17-2-686 savedefault baron:/boot/grub# cp menu.lst menu.lst.save baron:/boot/grub# update-grub Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /vmlinuz-2.6.18.baron.20070221.0915 Found kernel: /vmlinuz-2.6.18-custom.01 Found kernel: /vmlinuz-2.6.18-3-686 Found kernel: /vmlinuz-2.6.17-2-686 Updating /boot/grub/menu.lst ... done baron:/boot/grub# diff menu.lst.save menu.lst 119c119 root (hd0,11) --- root (hd0,0) 125c125 root (hd0,11) --- root (hd0,0) 131c131 root (hd0,11) --- root (hd0,0) 137c137 root (hd0,11) --- root (hd0,0) 143c143 root (hd0,11) --- root (hd0,0) 149c149 root (hd0,11) --- root (hd0,0) 155c155 root (hd0,11) --- root (hd0,0) 161c161 root (hd0,11) --- root (hd0,0) -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.baron.20070221.0915 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages grub depends on: ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libncurses5 5.5-5Shared libraries for terminal hand grub recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410838: marked as done (FTBFS: Could not find module `MissingH.Path')
Your message dated Thu, 22 Feb 2007 21:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#410838: fixed in darcs-buildpackage 0.5.11 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: darcs-buildpackage Version: 0.5.10 Severity: serious Tags: sid This package fails to compile in sid (but not in etch): Automatic build of darcs-buildpackage_0.5.10 on coconut0 by sbuild/ia64 0.49 ... configure: No c2hs found configure: No cpphs found configure: No greencard found ./setup build Darcs.hs:12:7: Could not find module `MissingH.Path': Use -v to see a list of the files searched for. Preprocessing executables for darcs-buildpackage-0.5.3... Building darcs-buildpackage-0.5.3... make[1]: *** [all] Error 1 make[1]: Leaving directory `/build/tbm/darcs-buildpackage-0.5.10' make: *** [build-stamp] Error 2 -- Martin Michlmayr http://www.cyrius.com/ ---End Message--- ---BeginMessage--- Source: darcs-buildpackage Source-Version: 0.5.11 We believe that the bug you reported is fixed in the latest version of darcs-buildpackage, which is due to be installed in the Debian FTP archive: darcs-buildpackage_0.5.11.dsc to pool/main/d/darcs-buildpackage/darcs-buildpackage_0.5.11.dsc darcs-buildpackage_0.5.11.tar.gz to pool/main/d/darcs-buildpackage/darcs-buildpackage_0.5.11.tar.gz darcs-buildpackage_0.5.11_i386.deb to pool/main/d/darcs-buildpackage/darcs-buildpackage_0.5.11_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. John Goerzen [EMAIL PROTECTED] (supplier of updated darcs-buildpackage package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 22 Feb 2007 05:19:42 -0600 Source: darcs-buildpackage Binary: darcs-buildpackage Architecture: source i386 Version: 0.5.11 Distribution: unstable Urgency: low Maintainer: John Goerzen [EMAIL PROTECTED] Changed-By: John Goerzen [EMAIL PROTECTED] Description: darcs-buildpackage - Suite to help with Debian packages in Darcs archives Closes: 410838 Changes: darcs-buildpackage (0.5.11) unstable; urgency=low . * Update to MissingH 0.18.0. Closes: #410838. Files: 99d12baecb25874560f0ef884652137d 732 devel optional darcs-buildpackage_0.5.11.dsc 07ffdbd55a5d0f928a10dbb02f2e9376 44601 devel optional darcs-buildpackage_0.5.11.tar.gz 3469b53a74f455f2df274fd695862be8 1856444 devel optional darcs-buildpackage_0.5.11_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF3gn3TvSuJuBy3ggRAmx0AJ9dloKxPJr9XTyLVDSfT08Bl2Vq4gCeN++M jo0JHOevVPe8vUqTtrvj1vA= =MpY0 -END PGP SIGNATURE- ---End Message---
Bug#411652: closed by John Goerzen [EMAIL PROTECTED] (Bug#411652: fixed in bacula 1.38.11-8)
Hi, It still doesn't work for me. Take a look at this : colibri:~# apt-get install bacula-common bacula-sd 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. The following information may help to resolve the situation: The following packages have unmet dependencies: bacula-sd: PreDepends: bacula-common (= 1.38.11-7+b1) but 1.38.11-8 is to be installed E: Broken packages colibri:~# Maybe it's because I'm using i386 architecture... Regards nb Le jeudi 22 février 2007 à 19:51 +, Debian Bug Tracking System a écrit : This is an automatic notification regarding your Bug report #411652: bacula-sd: fails to install - dependency problem, which was filed against the bacula-sd package. It has been closed by John Goerzen [EMAIL PROTECTED]. Their explanation is attached below. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact John Goerzen [EMAIL PROTECTED] by replying to this email. Debian bug tracking system administrator (administrator, Debian Bugs database) pièce jointe message de courriel Message transféré De: John Goerzen [EMAIL PROTECTED] À: [EMAIL PROTECTED] Sujet: Bug#411652: fixed in bacula 1.38.11-8 Date: Thu, 22 Feb 2007 19:32:03 + Source: bacula Source-Version: 1.38.11-8 We believe that the bug you reported is fixed in the latest version of bacula, which is due to be installed in the Debian FTP archive: bacula-client_1.38.11-8_all.deb to pool/main/b/bacula/bacula-client_1.38.11-8_all.deb bacula-common_1.38.11-8_all.deb to pool/main/b/bacula/bacula-common_1.38.11-8_all.deb bacula-console-gnome_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-console-gnome_1.38.11-8_amd64.deb bacula-console-wx_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-console-wx_1.38.11-8_amd64.deb bacula-console_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-console_1.38.11-8_amd64.deb bacula-director-common_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-director-common_1.38.11-8_amd64.deb bacula-director-mysql_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-director-mysql_1.38.11-8_amd64.deb bacula-director-pgsql_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-director-pgsql_1.38.11-8_amd64.deb bacula-director-sqlite3_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-director-sqlite3_1.38.11-8_amd64.deb bacula-director-sqlite_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-director-sqlite_1.38.11-8_amd64.deb bacula-fd_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-fd_1.38.11-8_amd64.deb bacula-sd-mysql_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-sd-mysql_1.38.11-8_amd64.deb bacula-sd-pgsql_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-sd-pgsql_1.38.11-8_amd64.deb bacula-sd-sqlite3_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-sd-sqlite3_1.38.11-8_amd64.deb bacula-sd-sqlite_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-sd-sqlite_1.38.11-8_amd64.deb bacula-sd_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-sd_1.38.11-8_amd64.deb bacula-server_1.38.11-8_all.deb to pool/main/b/bacula/bacula-server_1.38.11-8_all.deb bacula-traymonitor_1.38.11-8_amd64.deb to pool/main/b/bacula/bacula-traymonitor_1.38.11-8_amd64.deb bacula_1.38.11-8.diff.gz to pool/main/b/bacula/bacula_1.38.11-8.diff.gz bacula_1.38.11-8.dsc to pool/main/b/bacula/bacula_1.38.11-8.dsc bacula_1.38.11-8_all.deb to pool/main/b/bacula/bacula_1.38.11-8_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. John Goerzen [EMAIL PROTECTED] (supplier of updated bacula package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 22 Feb 2007 12:58:55 -0600 Source: bacula Binary: bacula-director-sqlite3 bacula-console bacula-director-sqlite bacula-client bacula-traymonitor bacula-console-gnome bacula bacula-director-pgsql bacula-director-common bacula-fd bacula-console-wx bacula-director-mysql bacula-sd-pgsql bacula-common bacula-server bacula-sd-sqlite bacula-sd bacula-sd-sqlite3 bacula-sd-mysql Architecture: source amd64 all Version: 1.38.11-8 Distribution: unstable Urgency: high Maintainer: John Goerzen
Bug#410859: marked as done (liboil0.3: wrongly assumes that all Intel chips support CP14 timestamp)
Your message dated Thu, 22 Feb 2007 22:02:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#410859: fixed in liboil 0.3.10-1.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---BeginMessage---
Package: liboil0.3
Version: 0.3.10-1
Severity: grave
Tags: patch
All programs linked with liboil0.3 are causing a SIGILL on an IXP4xx
XScale CPU. This is due to the following code in liboil/liboilcpu.c:
switch(arm_implementer) {
case 0x69: /* Intel */
/* assume that all Intel chips support CP14 timestamp */
_oil_profile_stamp = oil_profile_stamp_xscale;
I don't know how to detect if an Intel CPU has support for CP14
timestamp, therefore I suggests to disable this detection for now. Here
is the patch I used:
--- liboil-0.3.10.orig/liboil/liboilcpu.c
+++ liboil-0.3.10/liboil/liboilcpu.c
@@ -644,7 +644,7 @@
switch(arm_implementer) {
case 0x69: /* Intel */
/* assume that all Intel chips support CP14 timestamp */
- _oil_profile_stamp = oil_profile_stamp_xscale;
+ /* _oil_profile_stamp = oil_profile_stamp_xscale; */
break;
case 0x41: /* ARM */
/* ARM chips are known to not have timestamping available from
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: arm (armv5tel)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-ixp4xx
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Versions of packages liboil0.3 depends on:
ii libc62.3.6.ds1-10 GNU C Library: Shared libraries
liboil0.3 recommends no packages.
-- no debconf information
---End Message---
---BeginMessage---
Source: liboil
Source-Version: 0.3.10-1.1
We believe that the bug you reported is fixed in the latest version of
liboil, which is due to be installed in the Debian FTP archive:
liboil0.3-dev_0.3.10-1.1_i386.deb
to pool/main/libo/liboil/liboil0.3-dev_0.3.10-1.1_i386.deb
liboil0.3_0.3.10-1.1_i386.deb
to pool/main/libo/liboil/liboil0.3_0.3.10-1.1_i386.deb
liboil_0.3.10-1.1.diff.gz
to pool/main/libo/liboil/liboil_0.3.10-1.1.diff.gz
liboil_0.3.10-1.1.dsc
to pool/main/libo/liboil/liboil_0.3.10-1.1.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.
Ben Hutchings [EMAIL PROTECTED] (supplier of updated liboil package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 22 Feb 2007 21:18:15 +
Source: liboil
Binary: liboil0.3 liboil0.3-dev
Architecture: source i386
Version: 0.3.10-1.1
Distribution: unstable
Urgency: low
Maintainer: David Schleef [EMAIL PROTECTED]
Changed-By: Ben Hutchings [EMAIL PROTECTED]
Description:
liboil0.3 - Library of Optimized Inner Loops
liboil0.3-dev - Library of Optimized Inner Loops (development headers)
Closes: 410859
Changes:
liboil (0.3.10-1.1) unstable; urgency=low
.
* Non-maintainer upload.
* Disabled use of system register on StrongArm and XScale processors
(Closes: #410859)
Files:
141a191b153b3caf8de224f2c863fc9f 610 devel optional liboil_0.3.10-1.1.dsc
8f450e754ebdb20cfda02eeeff7c7d2f 32080 devel optional liboil_0.3.10-1.1.diff.gz
b5be656261d043883a85c3c8c0670cfc 143956 libs optional
liboil0.3_0.3.10-1.1_i386.deb
3e543c56ae2b7847c44513e889cc9ff4 282182 libdevel optional
liboil0.3-dev_0.3.10-1.1_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFF3g9b79ZNCRIGYgcRAp0bAJ0TcQ1nNmLJnG5TU1aAsKKhxeS+oACfSOhV
L+9457A6C3fLF0iJTw+bNUE=
=tiR0
-END PGP SIGNATURE-
---End Message---
Bug#412021: grub fails to cope with '/boot' on different partition to '/'
Your changing (hd0,?) in the wrong place. Look a little higher up in the menu.lst file. The entries you are changing are regenerated every time update-grub is run. On Thu, Feb 22, 2007 at 09:28:13PM +, Bernard Boudet wrote: Package: grub Version: 0.97-23 Severity: critical Justification: breaks the whole system My /boot partition is on /dev/hda11, so in menu.lst it says: root (hd0,11) update-grub trashes that and resets each case to: root (hd0,0) This happens whenever a new kernel is installed and it leaves the system unbootable. My workaround is to manually edit menu.lst after each time a new kernel is installed and before rebooting. baron:/boot/grub# grep -v -e '^$' -e '^#' menu.lst default 0 timeout 5 color cyan/blue white/blue title Debian GNU/Linux, kernel 2.6.18.baron.20070221.0915 root(hd0,11) kernel /vmlinuz-2.6.18.baron.20070221.0915 root=/dev/hda1 ro initrd /initrd.img-2.6.18.baron.20070221.0915 savedefault title Debian GNU/Linux, kernel 2.6.18.baron.20070221.0915 (single-user mode) root(hd0,11) kernel /vmlinuz-2.6.18.baron.20070221.0915 root=/dev/hda1 ro single initrd /initrd.img-2.6.18.baron.20070221.0915 savedefault title Debian GNU/Linux, kernel 2.6.18-custom.01 root(hd0,11) kernel /vmlinuz-2.6.18-custom.01 root=/dev/hda1 ro initrd /initrd.img-2.6.18-custom.01 savedefault title Debian GNU/Linux, kernel 2.6.18-custom.01 (single-user mode) root(hd0,11) kernel /vmlinuz-2.6.18-custom.01 root=/dev/hda1 ro single initrd /initrd.img-2.6.18-custom.01 savedefault title Debian GNU/Linux, kernel 2.6.18-3-686 root(hd0,11) kernel /vmlinuz-2.6.18-3-686 root=/dev/hda1 ro initrd /initrd.img-2.6.18-3-686 savedefault title Debian GNU/Linux, kernel 2.6.18-3-686 (single-user mode) root(hd0,11) kernel /vmlinuz-2.6.18-3-686 root=/dev/hda1 ro single initrd /initrd.img-2.6.18-3-686 savedefault title Debian GNU/Linux, kernel 2.6.17-2-686 root(hd0,11) kernel /vmlinuz-2.6.17-2-686 root=/dev/hda1 ro initrd /initrd.img-2.6.17-2-686 savedefault title Debian GNU/Linux, kernel 2.6.17-2-686 (single-user mode) root(hd0,11) kernel /vmlinuz-2.6.17-2-686 root=/dev/hda1 ro single initrd /initrd.img-2.6.17-2-686 savedefault baron:/boot/grub# cp menu.lst menu.lst.save baron:/boot/grub# update-grub Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /vmlinuz-2.6.18.baron.20070221.0915 Found kernel: /vmlinuz-2.6.18-custom.01 Found kernel: /vmlinuz-2.6.18-3-686 Found kernel: /vmlinuz-2.6.17-2-686 Updating /boot/grub/menu.lst ... done baron:/boot/grub# diff menu.lst.save menu.lst 119c119 root (hd0,11) --- root (hd0,0) 125c125 root (hd0,11) --- root (hd0,0) 131c131 root (hd0,11) --- root (hd0,0) 137c137 root (hd0,11) --- root (hd0,0) 143c143 root (hd0,11) --- root (hd0,0) 149c149 root (hd0,11) --- root (hd0,0) 155c155 root (hd0,11) --- root (hd0,0) 161c161 root (hd0,11) --- root (hd0,0) -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.baron.20070221.0915 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages grub depends on: ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libncurses5 5.5-5Shared libraries for terminal hand grub recommends no packages. -- no debconf information ___ Pkg-grub-devel mailing list [EMAIL PROTECTED] http://lists.alioth.debian.org/mailman/listinfo/pkg-grub-devel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: forcibly merging 411988 411980
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.27 forcemerge 411988 411980 Bug#411988: libswt3.2-gtk-jni 3.2.1-5 depends on libc6 (= 2.5) and is uninstallable Bug#411980: Please build against unstable libc6 Forcibly Merged 411980 411988. 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#412021: grub fails to cope with '/boot' on different partition to '/'
On Fri, Feb 23, 2007 at 09:23:22AM +1100, Jason Thomas wrote: Your changing (hd0,?) in the wrong place. Look a little higher up in the menu.lst file. The entries you are changing are regenerated every time update-grub is run. Arggh! You are quite right... I needed to change: # groot=(hd0,0) to: # groot=(hd0,11) This bug can be closed. But I hope it serves a place to help others who may make the same mistake. Thanks! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380552: a possible medium term soloution
peter green [EMAIL PROTECTED] wrote: would it be possible to reduce the test to only cause a warning until it is worked out what about the build environment is causing the false positive? I think that may be a reasonable thing to do here. This test is trying to check that pwd can read very long paths, specifically 256 levels of directories below the test's current directory. The error message indicates that it is failing after going 265 levels up (i.e. outside of the build directory, closer to the root). The error seems to suggest that lstat() failed, though none of the documented reasons for failure seem plausible. Another possibility is that the filesystem on the buildd is corrupt and one .. link does not point to the correct directory. (Lack of read permission on a directory is another possibility I thought of, but that results in a different error message.) Ben. -- Ben Hutchings Beware of bugs in the above code; I have only proved it correct, not tried it. - Donald Knuth signature.asc Description: This is a digitally signed message part
Bug#412021: marked as done (grub fails to cope with '/boot' on different partition to '/')
Your message dated Thu, 22 Feb 2007 20:55:30 -0200 with message-id [EMAIL PROTECTED] and subject line Bug#412021: grub fails to cope with '/boot' on different partition to '/' has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: grub Version: 0.97-23 Severity: critical Justification: breaks the whole system My /boot partition is on /dev/hda11, so in menu.lst it says: root (hd0,11) update-grub trashes that and resets each case to: root (hd0,0) This happens whenever a new kernel is installed and it leaves the system unbootable. My workaround is to manually edit menu.lst after each time a new kernel is installed and before rebooting. baron:/boot/grub# grep -v -e '^$' -e '^#' menu.lst default 0 timeout 5 color cyan/blue white/blue title Debian GNU/Linux, kernel 2.6.18.baron.20070221.0915 root(hd0,11) kernel /vmlinuz-2.6.18.baron.20070221.0915 root=/dev/hda1 ro initrd /initrd.img-2.6.18.baron.20070221.0915 savedefault title Debian GNU/Linux, kernel 2.6.18.baron.20070221.0915 (single-user mode) root(hd0,11) kernel /vmlinuz-2.6.18.baron.20070221.0915 root=/dev/hda1 ro single initrd /initrd.img-2.6.18.baron.20070221.0915 savedefault title Debian GNU/Linux, kernel 2.6.18-custom.01 root(hd0,11) kernel /vmlinuz-2.6.18-custom.01 root=/dev/hda1 ro initrd /initrd.img-2.6.18-custom.01 savedefault title Debian GNU/Linux, kernel 2.6.18-custom.01 (single-user mode) root(hd0,11) kernel /vmlinuz-2.6.18-custom.01 root=/dev/hda1 ro single initrd /initrd.img-2.6.18-custom.01 savedefault title Debian GNU/Linux, kernel 2.6.18-3-686 root(hd0,11) kernel /vmlinuz-2.6.18-3-686 root=/dev/hda1 ro initrd /initrd.img-2.6.18-3-686 savedefault title Debian GNU/Linux, kernel 2.6.18-3-686 (single-user mode) root(hd0,11) kernel /vmlinuz-2.6.18-3-686 root=/dev/hda1 ro single initrd /initrd.img-2.6.18-3-686 savedefault title Debian GNU/Linux, kernel 2.6.17-2-686 root(hd0,11) kernel /vmlinuz-2.6.17-2-686 root=/dev/hda1 ro initrd /initrd.img-2.6.17-2-686 savedefault title Debian GNU/Linux, kernel 2.6.17-2-686 (single-user mode) root(hd0,11) kernel /vmlinuz-2.6.17-2-686 root=/dev/hda1 ro single initrd /initrd.img-2.6.17-2-686 savedefault baron:/boot/grub# cp menu.lst menu.lst.save baron:/boot/grub# update-grub Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /vmlinuz-2.6.18.baron.20070221.0915 Found kernel: /vmlinuz-2.6.18-custom.01 Found kernel: /vmlinuz-2.6.18-3-686 Found kernel: /vmlinuz-2.6.17-2-686 Updating /boot/grub/menu.lst ... done baron:/boot/grub# diff menu.lst.save menu.lst 119c119 root (hd0,11) --- root (hd0,0) 125c125 root (hd0,11) --- root (hd0,0) 131c131 root (hd0,11) --- root (hd0,0) 137c137 root (hd0,11) --- root (hd0,0) 143c143 root (hd0,11) --- root (hd0,0) 149c149 root (hd0,11) --- root (hd0,0) 155c155 root (hd0,11) --- root (hd0,0) 161c161 root (hd0,11) --- root (hd0,0) -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.baron.20070221.0915 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages grub depends on: ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libncurses5 5.5-5Shared libraries for terminal hand grub recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- [EMAIL PROTECTED] writes: On Fri, Feb 23, 2007 at 09:23:22AM +1100, Jason Thomas wrote: Your changing (hd0,?) in the wrong place. Look a little higher up in the menu.lst file. The entries you are changing are regenerated every time update-grub is run. Arggh! You are quite right... I needed to change: # groot=(hd0,0) to: # groot=(hd0,11) This bug can be closed. But I hope it serves a place to help others who may
Bug#405900: swf-player: should be updated for iceape/iceweasel
swf-player is using the Netscape Plugin API, which does *not* require linking against any Mozilla libraries. It only requires the header files from one of the -dev packages. Therefore I believe the following patch: --- plugin/Makefile.am~ 2006-01-09 20:33:42.0 + +++ plugin/Makefile.am 2007-02-22 23:07:54.0 + @@ -11,7 +11,7 @@ libswfdecmozilla_la_SOURCES = plugin.c libswfdecmozilla_la_CFLAGS = $(GLOBAL_CFLAGS) $(MOZILLA_CFLAGS) $(X_CFLAGS) \ -DBINDIR=\$(bindir)/\ -libswfdecmozilla_la_LDFLAGS = -module -avoid-version $(X_LIBS) $(MOZILLA_LIBS) +libswfdecmozilla_la_LDFLAGS = -module -avoid-version $(X_LIBS) libswfdecmozilla_la_LIBADD = -lXt -- END -- plus autoreconf fixes this. With this change, I was able to load a swfdec plugin built against libxul-dev into Firefox 2.0. Ben. -- Ben Hutchings Beware of bugs in the above code; I have only proved it correct, not tried it. - Donald Knuth signature.asc Description: This is a digitally signed message part
Bug#403222: marked as done ([etch] lilo: fails to write the boot information (LVM system))
Your message dated Thu, 22 Feb 2007 23:17:04 + with message-id [EMAIL PROTECTED] and subject line Bug#403222: fixed in lilo 1:22.8-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: lilo Version: 1:22.6.1-9 Severity: important After a kernel upgrade, lilo refused to write the information in MBR. twix:/etc/lvm# apt-cache policy linux-image-2.6.18-3-686 linux-image-2.6.18-3-686: Installed: 2.6.18-7 Candidate: 2.6.18-7 Version table: 2.6.18-8 0 99 http://ftp.lug.ro sid/main Packages *** 2.6.18-7 0 900 http://ftp.lug.ro etch/main Packages 100 /var/lib/dpkg/status This is the output if I run by hand and is the same thing stored in /var/log/lilo* twix:/etc/lvm# lilo device-mapper: table ioctl failed: No such device or address Fatal: device-mapper: dm_task_run(DM_DEVICE_TABLE) failed libdevmapper1.02 was upgraded (from 2:1.02.08-1) as an attempt to make lilo recognize the thing, but no avail. twix:/etc/lvm# apt-cache policy libdevmapper1.02 dmsetup libdevmapper1.02: Installed: 2:1.02.12-1 Candidate: 2:1.02.12-1 Version table: *** 2:1.02.12-1 0 99 http://ftp.lug.ro sid/main Packages 100 /var/lib/dpkg/status 2:1.02.08-1 0 900 http://ftp.lug.ro etch/main Packages dmsetup: Installed: 2:1.02.08-1 Candidate: 2:1.02.08-1 Version table: 2:1.02.12-1 0 99 http://ftp.lug.ro sid/main Packages *** 2:1.02.08-1 0 900 http://ftp.lug.ro etch/main Packages 100 /var/lib/dpkg/status twix:/etc/lvm# dmsetup info Name: hdapool-homefilesystem State: ACTIVE Tables present:LIVE Open count:1 Event number: 0 Major, minor: 254, 1 Number of targets: 2 UUID: LVM-phH0IvJRU30v0gAD64awZMzaG3FLwh6WzyAkYV9zve915YQ5GuoFXcI78Gz0tu2Z Name: hdapool-rootfilesystem State: ACTIVE Tables present:LIVE Open count:1 Event number: 0 Major, minor: 254, 0 Number of targets: 1 UUID: LVM-phH0IvJRU30v0gAD64awZMzaG3FLwh6W80vcbMjIVabaeeQk0k7trdSoeZxden1Q -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (900, 'testing'), (99, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8) Versions of packages lilo depends on: ii debconf 1.5.8 Debian configuration management sy ii libc62.3.6.ds1-8 GNU C Library: Shared libraries ii libdevmapper1.02 2:1.02.12-1 The Linux Kernel Device Mapper use ii mbr 1.1.9-2 Master Boot Record for IBM-PC comp lilo recommends no packages. -- debconf information: liloconfig/fstab_broken: liloconfig/banner: liloconfig/liloconf_incompatible: lilo/bad_bitmap: liloconfig/use_lba32: true lilo/upgrade: liloconfig/liloconf_exists: liloconfig/configuring_base: lilo/runme: false liloconfig/use_current_lilo: true liloconfig/wipe_old_liloconf: false liloconfig/instruction: liloconfig/activate_error: liloconfig/select_bitmap: /boot/coffee.bmp liloconfig/lilo_error: lilo/new-config: liloconfig/odd_fstab: liloconfig/install_from_root_device: true liloconfig/make_active_partition: true liloconfig/maintitle: liloconfig/mbr_error: liloconfig/lilo_warning: liloconfig/install_mbr: false liloconfig/no_changes: ---End Message--- ---BeginMessage--- Source: lilo Source-Version: 1:22.8-1 We believe that the bug you reported is fixed in the latest version of lilo, which is due to be installed in the Debian FTP archive: lilo-doc_22.8-1_all.deb to pool/main/l/lilo/lilo-doc_22.8-1_all.deb lilo_22.8-1.diff.gz to pool/main/l/lilo/lilo_22.8-1.diff.gz lilo_22.8-1.dsc to pool/main/l/lilo/lilo_22.8-1.dsc lilo_22.8-1_i386.deb to pool/main/l/lilo/lilo_22.8-1_i386.deb lilo_22.8.orig.tar.gz to pool/main/l/lilo/lilo_22.8.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. Andrés Roldán [EMAIL PROTECTED] (supplier of updated lilo 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
Bug#401393: marked as done (Previously working LVM setup mysteriously broken.)
Your message dated Thu, 22 Feb 2007 23:17:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#401393: fixed in lilo 1:22.8-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---BeginMessage---
Package: lilo
Version: 1:22.6.1-9
Severity: grave
My system has a somewhat unusual setup: I'm using lvm on RAID1. Sometime
recently, lilo just quit working:
[EMAIL PROTECTED]:~$ sudo lilo
Warning: COMPACT may conflict with LBA32 on some systems
device-mapper: table ioctl failed: No such device or address
Fatal: device-mapper: dm_task_run(DM_DEVICE_TABLE) failed
This happens with all versions of lilo back to 7.1 (which is from before
the computer in question existed). Web searches turn up references to old
bugs that prevented lilo from working with lvm2 systems. But the disk
configuration on this system hasn't changed since I built it and it's always
used lilo, so that can't possibly be it. The only thing I can think of is
that maybe there's an incompatibility with recent 2.6.18 kernels; I don't
have easy access to the console at the moment, though [0].
Daniel
[0] because the console is the TV, and right now my girlfriend is using
it to play video games :-P
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages lilo depends on:
ii debconf 1.5.9 Debian configuration management sy
ii libc62.3.6.ds1-8 GNU C Library: Shared libraries
ii libdevmapper1.02 2:1.02.12-1 The Linux Kernel Device Mapper use
ii mbr 1.1.9-2 Master Boot Record for IBM-PC comp
lilo recommends no packages.
-- debconf information:
liloconfig/fstab_broken:
liloconfig/banner:
liloconfig/liloconf_incompatible:
lilo/bad_bitmap:
liloconfig/use_lba32: true
lilo/upgrade:
liloconfig/liloconf_exists:
liloconfig/configuring_base:
lilo/runme: false
liloconfig/use_current_lilo: true
liloconfig/wipe_old_liloconf: false
liloconfig/instruction:
liloconfig/activate_error:
liloconfig/select_bitmap: /boot/coffee.bmp
liloconfig/lilo_error:
lilo/new-config:
liloconfig/odd_fstab:
liloconfig/install_from_root_device: true
liloconfig/make_active_partition: true
liloconfig/maintitle:
liloconfig/mbr_error:
liloconfig/lilo_warning:
liloconfig/install_mbr: false
liloconfig/no_changes:
---End Message---
---BeginMessage---
Source: lilo
Source-Version: 1:22.8-1
We believe that the bug you reported is fixed in the latest version of
lilo, which is due to be installed in the Debian FTP archive:
lilo-doc_22.8-1_all.deb
to pool/main/l/lilo/lilo-doc_22.8-1_all.deb
lilo_22.8-1.diff.gz
to pool/main/l/lilo/lilo_22.8-1.diff.gz
lilo_22.8-1.dsc
to pool/main/l/lilo/lilo_22.8-1.dsc
lilo_22.8-1_i386.deb
to pool/main/l/lilo/lilo_22.8-1_i386.deb
lilo_22.8.orig.tar.gz
to pool/main/l/lilo/lilo_22.8.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.
Andrés Roldán [EMAIL PROTECTED] (supplier of updated lilo package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 22 Feb 2007 22:52:37 +
Source: lilo
Binary: lilo-doc lilo
Architecture: source i386 all
Version: 1:22.8-1
Distribution: unstable
Urgency: low
Maintainer: Andrés Roldán [EMAIL PROTECTED]
Changed-By: Andrés Roldán [EMAIL PROTECTED]
Description:
lilo - LInux LOader - The Classic OS loader can load Linux and others
lilo-doc - Documentation for LILO (LInux LOader)
Closes: 396487 399057 400150 401393 403222 404409 406543 407697 407847 408576
Changes:
lilo (1:22.8-1) unstable; urgency=low
.
* New upstream release.
* Acknowledging NMUs, big thanks guys.
Closes: #396487, #399057, #400150, #404409, #406543, #408576
Closes: #407847, #407697, #401393, #403222
* debian/patches/{02_makefile-adds.dpatch,07_devfs_msg.dpatch}:
- Updated to fit new version.
*
Bug#403222: marked as done ([etch] lilo: fails to write the boot information (LVM system))
Your message dated Thu, 22 Feb 2007 23:17:04 + with message-id [EMAIL PROTECTED] and subject line Bug#401393: fixed in lilo 1:22.8-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: lilo Version: 1:22.6.1-9 Severity: important After a kernel upgrade, lilo refused to write the information in MBR. twix:/etc/lvm# apt-cache policy linux-image-2.6.18-3-686 linux-image-2.6.18-3-686: Installed: 2.6.18-7 Candidate: 2.6.18-7 Version table: 2.6.18-8 0 99 http://ftp.lug.ro sid/main Packages *** 2.6.18-7 0 900 http://ftp.lug.ro etch/main Packages 100 /var/lib/dpkg/status This is the output if I run by hand and is the same thing stored in /var/log/lilo* twix:/etc/lvm# lilo device-mapper: table ioctl failed: No such device or address Fatal: device-mapper: dm_task_run(DM_DEVICE_TABLE) failed libdevmapper1.02 was upgraded (from 2:1.02.08-1) as an attempt to make lilo recognize the thing, but no avail. twix:/etc/lvm# apt-cache policy libdevmapper1.02 dmsetup libdevmapper1.02: Installed: 2:1.02.12-1 Candidate: 2:1.02.12-1 Version table: *** 2:1.02.12-1 0 99 http://ftp.lug.ro sid/main Packages 100 /var/lib/dpkg/status 2:1.02.08-1 0 900 http://ftp.lug.ro etch/main Packages dmsetup: Installed: 2:1.02.08-1 Candidate: 2:1.02.08-1 Version table: 2:1.02.12-1 0 99 http://ftp.lug.ro sid/main Packages *** 2:1.02.08-1 0 900 http://ftp.lug.ro etch/main Packages 100 /var/lib/dpkg/status twix:/etc/lvm# dmsetup info Name: hdapool-homefilesystem State: ACTIVE Tables present:LIVE Open count:1 Event number: 0 Major, minor: 254, 1 Number of targets: 2 UUID: LVM-phH0IvJRU30v0gAD64awZMzaG3FLwh6WzyAkYV9zve915YQ5GuoFXcI78Gz0tu2Z Name: hdapool-rootfilesystem State: ACTIVE Tables present:LIVE Open count:1 Event number: 0 Major, minor: 254, 0 Number of targets: 1 UUID: LVM-phH0IvJRU30v0gAD64awZMzaG3FLwh6W80vcbMjIVabaeeQk0k7trdSoeZxden1Q -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (900, 'testing'), (99, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8) Versions of packages lilo depends on: ii debconf 1.5.8 Debian configuration management sy ii libc62.3.6.ds1-8 GNU C Library: Shared libraries ii libdevmapper1.02 2:1.02.12-1 The Linux Kernel Device Mapper use ii mbr 1.1.9-2 Master Boot Record for IBM-PC comp lilo recommends no packages. -- debconf information: liloconfig/fstab_broken: liloconfig/banner: liloconfig/liloconf_incompatible: lilo/bad_bitmap: liloconfig/use_lba32: true lilo/upgrade: liloconfig/liloconf_exists: liloconfig/configuring_base: lilo/runme: false liloconfig/use_current_lilo: true liloconfig/wipe_old_liloconf: false liloconfig/instruction: liloconfig/activate_error: liloconfig/select_bitmap: /boot/coffee.bmp liloconfig/lilo_error: lilo/new-config: liloconfig/odd_fstab: liloconfig/install_from_root_device: true liloconfig/make_active_partition: true liloconfig/maintitle: liloconfig/mbr_error: liloconfig/lilo_warning: liloconfig/install_mbr: false liloconfig/no_changes: ---End Message--- ---BeginMessage--- Source: lilo Source-Version: 1:22.8-1 We believe that the bug you reported is fixed in the latest version of lilo, which is due to be installed in the Debian FTP archive: lilo-doc_22.8-1_all.deb to pool/main/l/lilo/lilo-doc_22.8-1_all.deb lilo_22.8-1.diff.gz to pool/main/l/lilo/lilo_22.8-1.diff.gz lilo_22.8-1.dsc to pool/main/l/lilo/lilo_22.8-1.dsc lilo_22.8-1_i386.deb to pool/main/l/lilo/lilo_22.8-1_i386.deb lilo_22.8.orig.tar.gz to pool/main/l/lilo/lilo_22.8.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. Andrés Roldán [EMAIL PROTECTED] (supplier of updated lilo 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
Bug#380552: a possible medium term soloution
On Thu, Feb 22, 2007 at 10:52:38PM +, you wrote: I think that may be a reasonable thing to do here. The reasonable thing would have been to not bitch about the binary upload. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401393: marked as done (Previously working LVM setup mysteriously broken.)
Your message dated Thu, 22 Feb 2007 23:17:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#403222: fixed in lilo 1:22.8-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---BeginMessage---
Package: lilo
Version: 1:22.6.1-9
Severity: grave
My system has a somewhat unusual setup: I'm using lvm on RAID1. Sometime
recently, lilo just quit working:
[EMAIL PROTECTED]:~$ sudo lilo
Warning: COMPACT may conflict with LBA32 on some systems
device-mapper: table ioctl failed: No such device or address
Fatal: device-mapper: dm_task_run(DM_DEVICE_TABLE) failed
This happens with all versions of lilo back to 7.1 (which is from before
the computer in question existed). Web searches turn up references to old
bugs that prevented lilo from working with lvm2 systems. But the disk
configuration on this system hasn't changed since I built it and it's always
used lilo, so that can't possibly be it. The only thing I can think of is
that maybe there's an incompatibility with recent 2.6.18 kernels; I don't
have easy access to the console at the moment, though [0].
Daniel
[0] because the console is the TV, and right now my girlfriend is using
it to play video games :-P
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages lilo depends on:
ii debconf 1.5.9 Debian configuration management sy
ii libc62.3.6.ds1-8 GNU C Library: Shared libraries
ii libdevmapper1.02 2:1.02.12-1 The Linux Kernel Device Mapper use
ii mbr 1.1.9-2 Master Boot Record for IBM-PC comp
lilo recommends no packages.
-- debconf information:
liloconfig/fstab_broken:
liloconfig/banner:
liloconfig/liloconf_incompatible:
lilo/bad_bitmap:
liloconfig/use_lba32: true
lilo/upgrade:
liloconfig/liloconf_exists:
liloconfig/configuring_base:
lilo/runme: false
liloconfig/use_current_lilo: true
liloconfig/wipe_old_liloconf: false
liloconfig/instruction:
liloconfig/activate_error:
liloconfig/select_bitmap: /boot/coffee.bmp
liloconfig/lilo_error:
lilo/new-config:
liloconfig/odd_fstab:
liloconfig/install_from_root_device: true
liloconfig/make_active_partition: true
liloconfig/maintitle:
liloconfig/mbr_error:
liloconfig/lilo_warning:
liloconfig/install_mbr: false
liloconfig/no_changes:
---End Message---
---BeginMessage---
Source: lilo
Source-Version: 1:22.8-1
We believe that the bug you reported is fixed in the latest version of
lilo, which is due to be installed in the Debian FTP archive:
lilo-doc_22.8-1_all.deb
to pool/main/l/lilo/lilo-doc_22.8-1_all.deb
lilo_22.8-1.diff.gz
to pool/main/l/lilo/lilo_22.8-1.diff.gz
lilo_22.8-1.dsc
to pool/main/l/lilo/lilo_22.8-1.dsc
lilo_22.8-1_i386.deb
to pool/main/l/lilo/lilo_22.8-1_i386.deb
lilo_22.8.orig.tar.gz
to pool/main/l/lilo/lilo_22.8.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.
Andrés Roldán [EMAIL PROTECTED] (supplier of updated lilo package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 22 Feb 2007 22:52:37 +
Source: lilo
Binary: lilo-doc lilo
Architecture: source i386 all
Version: 1:22.8-1
Distribution: unstable
Urgency: low
Maintainer: Andrés Roldán [EMAIL PROTECTED]
Changed-By: Andrés Roldán [EMAIL PROTECTED]
Description:
lilo - LInux LOader - The Classic OS loader can load Linux and others
lilo-doc - Documentation for LILO (LInux LOader)
Closes: 396487 399057 400150 401393 403222 404409 406543 407697 407847 408576
Changes:
lilo (1:22.8-1) unstable; urgency=low
.
* New upstream release.
* Acknowledging NMUs, big thanks guys.
Closes: #396487, #399057, #400150, #404409, #406543, #408576
Closes: #407847, #407697, #401393, #403222
* debian/patches/{02_makefile-adds.dpatch,07_devfs_msg.dpatch}:
- Updated to fit new version.
*
Bug#388616: Making mediawiki FHS compliant (was: Upgrade)
Steve Langasek [EMAIL PROTECTED] wrote: On Wed, Feb 21, 2007 at 12:54:38PM +0100, Frank Küster wrote: To me that looks a bit more complicated than one would like, but still quite manageable, and acceptable for fixing a RC bug in etch. What do you think? It's at least an order of magnitude more complicated (=error-prone) than the solution Romain has implemented, That's correct, not solving the FHS violation is simpler than doing it. and it still doesn't address the FHS requirement for the actual configuration to be stored under /etc, so I don't see the point. Then we misunderstood each other. I'm always talking about moving the actual configuration (LocalSettings.php and AdminSettings.php) to /etc/mediawiki1.7. The old package does not ship any of these files. They are created by a menu-driven php script, and the local admin is instructed to put the created files into /var/lib/mediawiki1.7. The new package would instruct the local admin to put them in /etc/mediawiki1.7, it would ship symlinks in /var/lib/mediawiki1.7/ so that they are found, and add a one-line patch to the templates for each of these files to get the internal path information right. So far, so simple. The only complicated bit is the transition, it would look like I've written (but not tested) below. Regards, Frank *** preinst *** etcdir=/etc/mediawiki1.7 vardir=/var/lib/mediawiki1.7 movext=.moved-by-preinst for file in LocalSettings.php AdminSettings.php; do etcfile=$etcdir/$file # there might already be a symlink in $vardir, but to a non-default location if [ -L $vardir/$file ]; then # register that $etcdir is a good default touch $etcfile.etcdefault linkdest=`readlink $vardir/file` if [ ! $etcfile = $linkdest ]; then if [ -e $linkdest ]; then mv $linkdest $etcfile chmod --reference $linkdest $etcfile chown --reference $linkdest $etcfile cat $linkdest EOF This file has been moved to $etcfile by mediawiki1.7's maintainer scripts EOF fi # still a symlink from old install? No longer needed if [ -L $etcfile ]; then rm $etcfile; fi # can we move the file from $vardir to its new location at once? if [ -e $etcfile ]; then destfile=$etcdir/$file$movext else destfile=$etcdir/$file fi if [ -f $vardir/$file ]; then # ordinary file, move to $etcdir mv $vardir/$file $destfile # else # Nothing, I assume dpkg will change the symlink dest itself fi done *** preinst *** *** config *** movext=.moved-by-preinst for file in LocalSettings.php AdminSettings.php; do if [ -e $etcdir/$file$movext* ]; then if [ -f $etcdir/$file.etcdefault ]; then db_set mediawiki/FHSmove$file $etcdir fi db_input low mediawiki/FHSmove$file || true fi done db_go || true *** config *** *** postinst *** etcdir=/etc/mediawiki1.7 vardir=/var/lib/mediawiki1.7 movext=.moved-by-preinst for file in LocalSettings.php AdminSettings.php; do etcfile=$etcdir/$file if [ -e $etcfile$movext ]; then db_get mediawiki/FHSmove$file || true which=$RET # can be /etc/mediawiki1.7 or /var/lib/mediawiki1.7 if [ $which = /var/lib/mediawiki1.7 ]; then test ! -e $etcfile || mv $etcfile $etcfile/$file.moved-by-postiinst mv $etcfile.movext $etcfile sed -i '[EMAIL PROTECTED]@pattern_depends_on_PHP_patch@' $etcfile else mv $etcfile.movext $etcfile.moved-from-var-directory fi rm $etcfile.etcdefault 2/dev/null || true fi done *** postinst *** *** templates *** Template: mediawiki/FHSmoveLocalSettings.php Type: select Choices: /etc/mediawiki1.7, /var/lib/mediawiki1.7 Default: /var/lib/mediawiki1.7 Description_: Which of two mediawiki1.7 configuration files should be used? In older versions, mediawiki1.7 kept the configuration file LocalSettings.php in its data directory, /var/lib/mediawiki1.7, but now it will be searched for in /etc/mediawiki1.7. The system has detected that you already have this file in /etc, too. . From which location should the new configuration file be taken? . If your installation of Mediawiki worked as intended in the past, it is safe to take the default. [repeat the same for AminSettings.php] *** templates *** -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Processed: Re: ogre: FTBFS: cannot allocate an object of abstract type 'CEGUI::OgreCEGUITexture'
Processing commands for [EMAIL PROTECTED]: reassign 43 cegui-mk2 Bug#43: ogre: FTBFS: cannot allocate an object of abstract type 'CEGUI::OgreCEGUITexture' Bug reassigned from package `ogre' to `cegui-mk2'. 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#411113: ogre: FTBFS: cannot allocate an object of abstract type 'CEGUI::OgreCEGUITexture'
reassign 43 cegui-mk2 thanks This bug is a result of a change between cegui-mk2 0.4 and 0.5 http://svn.sourceforge.net/viewvc/crayzedsgui/cegui_mk2/trunk/include/CEGUITexture.h?r1=1125r2=1230pathrev=1230 which is both source- and binary-incompatible. No doubt there are others. Such incompatible changes should result in a change of library version (both soname and library package name). However, library transitions are banned during a freeze, so version 0.5 should not have been uploaded at all. I believe it may be possible to undo the damage by uploading the previous version with the epoch bumped so that it still counts as newer. However, I am no expert in this. Ben. -- Ben Hutchings Beware of bugs in the above code; I have only proved it correct, not tried it. - Donald Knuth signature.asc Description: This is a digitally signed message part
Bug#411078: license.terms for utils/base64/base64.tcl not included
On Fri, Feb 16, 2007, Steve Langasek wrote: Er, what? the authors hereby grant permission to use, copy, modify, distribute, and license doesn't grant to amsn the right to modify? Yes, there is a missing license statement, and that is a serious bug. But I don't understand the claim that the file shouldn't be distributed. Hi, when I look for license.terms in the package, I see this: % grep -r license.terms * utils/base64/yencode.tcl:# See the file license.terms for information on usage and redistribution utils/base64/base64.tcl:# See the file license.terms for information on usage and redistribution utils/base64/uuencode.tcl:# See the file license.terms for information on usage and redistribution utils/macosx/QuickTimeTcl3.1/movie.tcl:# See the file license.terms for information on usage and redistribution utils/BWidget-1.7.0/Makefile.in:# See the file license.terms for information on usage and redistribution utils/BWidget-1.7.0/ChangeLog: * LICENSE.txt: Removed LGPL license; added Tcl-license terms. utils/http2.4/http.tcl:# See the file license.terms for information on usage and And when I have a look at utils/BWidget-1.7.0/LICENSE.txt as suggested by the grep results, I actually find the terms of the Tcl license as stated in Philippe's link. Thus, the terms are in the package, but not explicitely. Is it necessary to create a license.terms file here and put it in /usr/share/doc/amsn for instance? Isn't is sufficient to ask upstream to correct this in a later release? Is it worth mentioning in README.Debian? -- Mohammed Adnène Trojette
Processed: your mail
Processing commands for [EMAIL PROTECTED]: package libpam-ldap Ignoring bugs not assigned to: libpam-ldap forcemerge 385950 386077 Bug#385950: libpam-ldap: Broken regexp in postinst script Bug#386077: libpam-ldap: postinst a bit borked; perl search/replace have '/', recommend using '|' or other char instead Forcibly Merged 385950 386077. 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: found 411113 in 0.5.0-1
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.27 found 43 0.5.0-1 Bug#43: ogre: FTBFS: cannot allocate an object of abstract type 'CEGUI::OgreCEGUITexture' Bug marked as found in version 0.5.0-1. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411652: closed by John Goerzen [EMAIL PROTECTED] (Bug#411652: fixed in bacula 1.38.11-8)
On Thu, Feb 22, 2007 at 11:17:15PM +0100, nb wrote: Hi, It still doesn't work for me. Take a look at this : Fixed packages have not yet hit your mirror. Since I uploaded on amd64, give it 24-48 hours. -- John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405900: marked as done (swf-player: should be updated for iceape/iceweasel)
Your message dated Fri, 23 Feb 2007 02:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#405900: fixed in swfdec0.3 0.3.6-2.2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: swf-player Version: 0.3.6-2.1 Severity: grave Justification: renders package unusable swf-player installs plugins into following directories: /usr/lib/mozilla-snapshot/plugins /usr/lib/mozilla-firefox/plugins These directories are not used by iceape/iceweasel or even by firefox 1.5.dfsg+1.5.0.7-2 which is currently in the testing. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (999, 'testing'), (150, 'unstable'), (50, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) -- Regards, Sasha. Alexandra N. Kossovsky, software engineer. e-mail: [EMAIL PROTECTED] ---End Message--- ---BeginMessage--- Source: swfdec0.3 Source-Version: 0.3.6-2.2 We believe that the bug you reported is fixed in the latest version of swfdec0.3, which is due to be installed in the Debian FTP archive: libswfdec0.3-dev_0.3.6-2.2_i386.deb to pool/main/s/swfdec0.3/libswfdec0.3-dev_0.3.6-2.2_i386.deb libswfdec0.3_0.3.6-2.2_i386.deb to pool/main/s/swfdec0.3/libswfdec0.3_0.3.6-2.2_i386.deb swf-player_0.3.6-2.2_i386.deb to pool/main/s/swfdec0.3/swf-player_0.3.6-2.2_i386.deb swfdec0.3_0.3.6-2.2.diff.gz to pool/main/s/swfdec0.3/swfdec0.3_0.3.6-2.2.diff.gz swfdec0.3_0.3.6-2.2.dsc to pool/main/s/swfdec0.3/swfdec0.3_0.3.6-2.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. Ben Hutchings [EMAIL PROTECTED] (supplier of updated swfdec0.3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 23 Feb 2007 01:53:27 + Source: swfdec0.3 Binary: libswfdec0.3 swf-player libswfdec0.3-dev Architecture: source i386 Version: 0.3.6-2.2 Distribution: unstable Urgency: low Maintainer: David Schleef [EMAIL PROTECTED] Changed-By: Ben Hutchings [EMAIL PROTECTED] Description: libswfdec0.3 - SWF (Macromedia Flash) decoder library libswfdec0.3-dev - SWF (Macromedia Flash) decoder library swf-player - Mozilla plugin for SWF files (Macromedia Flash) Closes: 405900 Changes: swfdec0.3 (0.3.6-2.2) unstable; urgency=low . * Non-maintainer upload * Disabled linking of plugin against Mozilla libraries (Closes: #405900) Files: 5cfc7e3f93d8f0be784951d04e08de41 800 - optional swfdec0.3_0.3.6-2.2.dsc 17afbb92d6b265c5350192627cb05b9f 81867 - optional swfdec0.3_0.3.6-2.2.diff.gz 5543894a989a6c084329bfe9d8e4698f 385256 libdevel optional libswfdec0.3-dev_0.3.6-2.2_i386.deb aa01a9ce246178700cc9c687b94cd727 290444 libs optional libswfdec0.3_0.3.6-2.2_i386.deb cf1980378bf9a05871b6a6c6381fefa0 50082 utils optional swf-player_0.3.6-2.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF3k7F79ZNCRIGYgcRAih1AKDFjjqZXUhG+gj/ySWSY6RSBqKqqACfWiQX hPwIBqaK/5k1x/4qTEeiGlA= =VGXe -END PGP SIGNATURE- ---End Message---
Bug#412045: Problem when Installing mysql-server-5.0
Package: mysql-server-5.0 Version: 5.0.32-6 Severity: critical Justification: breaks the whole system At first mysql-server-5.0 unable to start, then I purge mysql-server-5.0 and reinstall back. Now I am having this problem where, this package cannot be installed -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages mysql-server-5.0 depends on: ii adduser 3.102Add and remove users and groups ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libdbi-perl 1.53-1 Perl5 database interface by Tim Bu ii libgcc1 1:4.1.1-21 GCC support library ii libmysqlclient15off 5.0.32-6 mysql database client library ii libncurses5 5.5-5Shared libraries for terminal hand ii libreadline55.2-2GNU readline and history libraries ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libwrap07.6.dbs-12 Wietse Venema's TCP wrappers libra ii lsb-base3.1-23 Linux Standard Base 3.1 init scrip ii mysql-client-5.05.0.32-6 mysql database client binaries ii mysql-common5.0.32-7 mysql database common files (e.g. ii passwd 1:4.0.18.1-6 change and administer password and ii perl5.8.8-7 Larry Wall's Practical Extraction ii psmisc 22.3-1 Utilities that use the proc filesy ii zlib1g 1:1.2.3-13 compression library - runtime Versions of packages mysql-server-5.0 recommends: ii mailx1:8.1.2-0.20050715cvs-1 A simple mail user agent -- debconf information: mysql-server-5.0/really_downgrade: false mysql-server-5.0/need_sarge_compat: false mysql-server-5.0/start_on_boot: true mysql-server/error_setting_password: mysql-server-5.0/nis_warning: mysql-server-5.0/postrm_remove_databases: false mysql-server-5.0/need_sarge_compat_done: false -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: your mail
Processing commands for [EMAIL PROTECTED]: clone 405900 -1 Bug#405900: swf-player: should be updated for iceape/iceweasel Bug 405900 cloned as bug 412047. reopen -1 Bug#412047: swf-player: should be updated for iceape/iceweasel 'reopen' is deprecated when a bug has been closed with a version; use 'found' or 'submitter' as appropriate instead. Bug reopened, originator not changed. severity -1 normal Bug#412047: swf-player: should be updated for iceape/iceweasel 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]
Bug#411980: marked as done (Please build against unstable libc6)
Your message dated Fri, 23 Feb 2007 07:26:30 +0100 with message-id [EMAIL PROTECTED] and subject line eclipse and experimental libc6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: libswt3.2-gtk-jni Version: 3.2.1-5 Severity: wishlist Hi, I think libswt3.2-gtk-jni 3.2.1-5 was mistakingly built against experimental's libc6 (2.5). Could you please build it against unstable's? Thanks! I apologize if this is on purpose or if this bug was already reported (bugs.d.o is currently down). Bye, -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.20-1-686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Versions of packages libswt3.2-gtk-jni depends on: ii libatk1.0-0 1.12.4-2 The ATK accessibility toolkit ii libc6 2.3.6.ds1-12 GNU C Library: Shared libraries ii libcairo2 1.2.4-4 The Cairo 2D vector graphics libra ii libglib2.0-02.12.9-1 The GLib library of C routines ii libgtk2.0-0 2.8.20-5 The GTK+ graphical user interface ii libxtst61:1.0.1-5X11 Testing -- Resource extension Versions of packages libswt3.2-gtk-jni recommends: ii libgcc1 1:4.1.1-21 GCC support library ii libgl1-mesa-glx [libgl1] 6.5.1-0.5 A free implementation of the OpenG ii libglu1-mesa [libglu1]6.5.1-0.5 The OpenGL utility library (GLU) ii libgnome2-0 2.16.0-2 The GNOME 2 library - runtime file ii libgnomeui-0 2.14.1-2 The GNOME 2 libraries (User Interf ii libgnomevfs2-01:2.14.2-6 GNOME virtual file-system (runtime ii libnspr4-0d 1.8.0.9-1 NetScape Portable Runtime Library ii libstdc++64.1.1-21 The GNU Standard C++ Library v3 ii libxul0d 1.8.0.9-1 Gecko engine library -- no debconf information -- Loïc Minier [EMAIL PROTECTED] ---End Message--- ---BeginMessage--- Version: 3.2.1-6 Sorry for the the inconvinience. I built eclipse in the wrong chroot Cheers, Michael -- .''`. | Michael Koch [EMAIL PROTECTED] : :' : | Free Java Developer http://www.classpath.org `. `' | `-| 1024D/BAC5 4B28 D436 95E6 F2E0 BD11 5923 A008 2763 483B ---End Message---
Bug#411988: marked as done (libswt3.2-gtk-jni 3.2.1-5 depends on libc6 (= 2.5) and is uninstallable)
Your message dated Fri, 23 Feb 2007 07:26:30 +0100 with message-id [EMAIL PROTECTED] and subject line eclipse and experimental libc6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: libswt3.2-gtk-jni Version: 3.2.1-5 Severity: serious The following packages are BROKEN: libswt3.2-gtk-jni The following packages will be upgraded: eclipse eclipse-jdt eclipse-jdt-gcj eclipse-pde eclipse-pde-gcj eclipse-platform eclipse-platform-gcj eclipse-rcp eclipse-rcp-gcj eclipse-source libswt3.2-gtk-gcj libswt3.2-gtk-java 13 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. The following packages have unmet dependencies: libswt3.2-gtk-jni: Depends: libc6 (= 2.5) but 2.3.6.ds1-13 is installed. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-k1 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages libswt3.2-gtk-jni depends on: ii libatk1.0-0 1.12.4-2 The ATK accessibility toolkit ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libcairo2 1.2.4-4 The Cairo 2D vector graphics libra ii libglib2.0-02.12.6-2 The GLib library of C routines ii libgtk2.0-0 2.8.20-5 The GTK+ graphical user interface ii libxtst61:1.0.1-5X11 Testing -- Resource extension Versions of packages libswt3.2-gtk-jni recommends: ii libgcc1 1:4.1.1-21 GCC support library ii libgl1-mesa-glx [libgl1] 6.5.1-0.5 A free implementation of the OpenG ii libglu1-mesa [libglu1]6.5.1-0.5 The OpenGL utility library (GLU) ii libgnome2-0 2.16.0-2 The GNOME 2 library - runtime file ii libgnomeui-0 2.14.1-2 The GNOME 2 libraries (User Interf ii libgnomevfs2-01:2.14.2-6 GNOME virtual file-system (runtime ii libnspr4-0d 1.8.0.9-1 NetScape Portable Runtime Library ii libstdc++64.1.1-21 The GNU Standard C++ Library v3 ii libxul0d 1.8.0.9-1 Gecko engine library -- no debconf information ---End Message--- ---BeginMessage--- Version: 3.2.1-6 Sorry for the the inconvinience. I built eclipse in the wrong chroot Cheers, Michael -- .''`. | Michael Koch [EMAIL PROTECTED] : :' : | Free Java Developer http://www.classpath.org `. `' | `-| 1024D/BAC5 4B28 D436 95E6 F2E0 BD11 5923 A008 2763 483B ---End Message---
Bug#411988: marked as done (libswt3.2-gtk-jni 3.2.1-5 depends on libc6 (= 2.5) and is uninstallable)
Your message dated Fri, 23 Feb 2007 07:26:30 +0100 with message-id [EMAIL PROTECTED] and subject line eclipse and experimental libc6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: libswt3.2-gtk-jni Version: 3.2.1-5 Severity: serious The following packages are BROKEN: libswt3.2-gtk-jni The following packages will be upgraded: eclipse eclipse-jdt eclipse-jdt-gcj eclipse-pde eclipse-pde-gcj eclipse-platform eclipse-platform-gcj eclipse-rcp eclipse-rcp-gcj eclipse-source libswt3.2-gtk-gcj libswt3.2-gtk-java 13 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. The following packages have unmet dependencies: libswt3.2-gtk-jni: Depends: libc6 (= 2.5) but 2.3.6.ds1-13 is installed. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-k1 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages libswt3.2-gtk-jni depends on: ii libatk1.0-0 1.12.4-2 The ATK accessibility toolkit ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libcairo2 1.2.4-4 The Cairo 2D vector graphics libra ii libglib2.0-02.12.6-2 The GLib library of C routines ii libgtk2.0-0 2.8.20-5 The GTK+ graphical user interface ii libxtst61:1.0.1-5X11 Testing -- Resource extension Versions of packages libswt3.2-gtk-jni recommends: ii libgcc1 1:4.1.1-21 GCC support library ii libgl1-mesa-glx [libgl1] 6.5.1-0.5 A free implementation of the OpenG ii libglu1-mesa [libglu1]6.5.1-0.5 The OpenGL utility library (GLU) ii libgnome2-0 2.16.0-2 The GNOME 2 library - runtime file ii libgnomeui-0 2.14.1-2 The GNOME 2 libraries (User Interf ii libgnomevfs2-01:2.14.2-6 GNOME virtual file-system (runtime ii libnspr4-0d 1.8.0.9-1 NetScape Portable Runtime Library ii libstdc++64.1.1-21 The GNU Standard C++ Library v3 ii libxul0d 1.8.0.9-1 Gecko engine library -- no debconf information ---End Message--- ---BeginMessage--- Version: 3.2.1-6 Sorry for the the inconvinience. I built eclipse in the wrong chroot Cheers, Michael -- .''`. | Michael Koch [EMAIL PROTECTED] : :' : | Free Java Developer http://www.classpath.org `. `' | `-| 1024D/BAC5 4B28 D436 95E6 F2E0 BD11 5923 A008 2763 483B ---End Message---
Bug#411980: marked as done (Please build against unstable libc6)
Your message dated Fri, 23 Feb 2007 07:26:30 +0100 with message-id [EMAIL PROTECTED] and subject line eclipse and experimental libc6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: libswt3.2-gtk-jni Version: 3.2.1-5 Severity: wishlist Hi, I think libswt3.2-gtk-jni 3.2.1-5 was mistakingly built against experimental's libc6 (2.5). Could you please build it against unstable's? Thanks! I apologize if this is on purpose or if this bug was already reported (bugs.d.o is currently down). Bye, -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.20-1-686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Versions of packages libswt3.2-gtk-jni depends on: ii libatk1.0-0 1.12.4-2 The ATK accessibility toolkit ii libc6 2.3.6.ds1-12 GNU C Library: Shared libraries ii libcairo2 1.2.4-4 The Cairo 2D vector graphics libra ii libglib2.0-02.12.9-1 The GLib library of C routines ii libgtk2.0-0 2.8.20-5 The GTK+ graphical user interface ii libxtst61:1.0.1-5X11 Testing -- Resource extension Versions of packages libswt3.2-gtk-jni recommends: ii libgcc1 1:4.1.1-21 GCC support library ii libgl1-mesa-glx [libgl1] 6.5.1-0.5 A free implementation of the OpenG ii libglu1-mesa [libglu1]6.5.1-0.5 The OpenGL utility library (GLU) ii libgnome2-0 2.16.0-2 The GNOME 2 library - runtime file ii libgnomeui-0 2.14.1-2 The GNOME 2 libraries (User Interf ii libgnomevfs2-01:2.14.2-6 GNOME virtual file-system (runtime ii libnspr4-0d 1.8.0.9-1 NetScape Portable Runtime Library ii libstdc++64.1.1-21 The GNU Standard C++ Library v3 ii libxul0d 1.8.0.9-1 Gecko engine library -- no debconf information -- Loïc Minier [EMAIL PROTECTED] ---End Message--- ---BeginMessage--- Version: 3.2.1-6 Sorry for the the inconvinience. I built eclipse in the wrong chroot Cheers, Michael -- .''`. | Michael Koch [EMAIL PROTECTED] : :' : | Free Java Developer http://www.classpath.org `. `' | `-| 1024D/BAC5 4B28 D436 95E6 F2E0 BD11 5923 A008 2763 483B ---End Message---
Bug#412045: Problem when Installing mysql-server-5.0
severity 412045 serious thanks System Administrator [EMAIL PROTECTED] wrote: Package: mysql-server-5.0 Version: 5.0.32-6 Severity: critical Justification: breaks the whole system From your description, it rather seems as if only the package cannot be installed or configured, and this might result in dpkg, apt and aptitude refusing to install more packages. But you didn't indicate why the whole system breaks. At first mysql-server-5.0 unable to start, then I purge mysql-server-5.0 and reinstall back. Now I am having this problem where, this package cannot be installed Please post the error messages that you got when you tried to install. If you no longer have them, please send the output of dpkg -l mysql-server-5.0 dpkg --configure -a apt-get -f install Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Processed: Re: Problem when Installing mysql-server-5.0
Processing commands for [EMAIL PROTECTED]: severity 412045 serious Bug#412045: Problem when Installing mysql-server-5.0 Severity set to `serious' 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#412045: Problem when Installing mysql-server-5.0
tags 412045 + unreproducible moreinfo stop Hello Mr. Systemadministrator :) On 2007-02-23 System Administrator wrote: At first mysql-server-5.0 unable to start, then I purge mysql-server-5.0 and reinstall back. Now I am having this problem where, this package cannot be installed Can you show me any error messages or better a complete logfile (use script) of your attempt to install mysql-server-5.0 so that I can get a hint what may be wrong? As nobody else reported erros it's probably something specific to your system. bye, -christian- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#412045: Problem when Installing mysql-server-5.0
Processing commands for [EMAIL PROTECTED]: tags 412045 + unreproducible moreinfo Bug#412045: Problem when Installing mysql-server-5.0 There were no tags set. Tags added: unreproducible, moreinfo 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]
Bug#412054: strigi-daemon: segmentation fault
Package: strigi-daemon Version: 0.3.11-1 Severity: grave Justification: renders package unusable I see the segmentation fault in strigi as soon as I start the indexing. Probably some libraries are missing. [EMAIL PROTECTED]:~/.strigi $ strigidaemon 2007-02-23 07:30:43,212 [3078698688] WARN DaemonConfigurator - created default config for indexed dirs 2007-02-23 07:30:43,213 [3078698688] DEBUG strigi.daemon - filter manager initialized /usr/lib/strigi/strigita_kfile.so /usr/lib/strigi/strigita_magic.so /usr/lib/strigi/strigita_libextractor.so /usr/lib/strigi/strigita_xattr.so 2007-02-23 07:30:56,126 [3078695856] DEBUG strigi.IndexScheduler - 0 real files in the database 2007-02-23 07:30:56,126 [3078695856] DEBUG strigi.IndexScheduler - going to index listFiles /home/rrs listFiles /home/rrs/.evolution listFiles /home/rrs/.gnome2 listFiles /home/rrs/.kde listFiles /home/rrs/.mozilla listFiles /home/rrs/.mozilla-thunderbird 2007-02-23 07:30:58,670 [3078695856] DEBUG strigi.IndexScheduler - 0 files to remove 2007-02-23 07:30:58,670 [3078695856] DEBUG strigi.IndexScheduler - 129687 files to add or update Loading `libextractor_exiv2' plugin failed: libextractor_exiv2.so: cannot open shared object file: No such file or directory Loading `libextractor_ole2' plugin failed: libextractor_ole2.so: cannot open shared object file: No such file or directory Loading `libextractor_ogg' plugin failed: libextractor_ogg.so: cannot open shared object file: No such file or directory Loading `libextractor_mpeg' plugin failed: libextractor_mpeg.so: cannot open shared object file: No such file or directory Segmentation fault -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing'), (550, 'unstable'), (500, 'stable'), (350, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.20-rt8-vanilla-dellxps-skas3-v8.2 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages strigi-daemon depends on: ii libbz2-1.0 1.0.3-6 high-quality block-sorting file co ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libclucene0 0.9.16a-1library for full-featured text sea ii libdbus-1-3 1.0.2-1 simple interprocess messaging syst ii libexpat1 1.95.8-3.4 XML parsing C library - runtime li ii libgcc1 1:4.1.1-21 GCC support library ii liblog4cxx9c2a 0.9.7-6 A logging library for C++ ii libssl0.9.8 0.9.8c-4 SSL shared libraries ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libstreamindexer0 0.3.11-1 streamindexer library for Strigi D ii libstreams0 0.3.11-1 streams library for for Strigi Des ii wv 1.2.4-1 Programs for accessing Microsoft W ii xpdf-utils [poppler-utils] 3.01-9 Portable Document Format (PDF) sui ii zlib1g 1:1.2.3-13 compression library - runtime strigi-daemon recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#412055: strigi-daemon: segmentation fault
Package: strigi-daemon Version: 0.3.11-1 Severity: grave Justification: renders package unusable I see the segmentation fault in strigi as soon as I start the indexing. Probably some libraries are missing. [EMAIL PROTECTED]:~/.strigi $ strigidaemon 2007-02-23 07:30:43,212 [3078698688] WARN DaemonConfigurator - created default config for indexed dirs 2007-02-23 07:30:43,213 [3078698688] DEBUG strigi.daemon - filter manager initialized /usr/lib/strigi/strigita_kfile.so /usr/lib/strigi/strigita_magic.so /usr/lib/strigi/strigita_libextractor.so /usr/lib/strigi/strigita_xattr.so 2007-02-23 07:30:56,126 [3078695856] DEBUG strigi.IndexScheduler - 0 real files in the database 2007-02-23 07:30:56,126 [3078695856] DEBUG strigi.IndexScheduler - going to index listFiles /home/rrs listFiles /home/rrs/.evolution listFiles /home/rrs/.gnome2 listFiles /home/rrs/.kde listFiles /home/rrs/.mozilla listFiles /home/rrs/.mozilla-thunderbird 2007-02-23 07:30:58,670 [3078695856] DEBUG strigi.IndexScheduler - 0 files to remove 2007-02-23 07:30:58,670 [3078695856] DEBUG strigi.IndexScheduler - 129687 files to add or update Loading `libextractor_exiv2' plugin failed: libextractor_exiv2.so: cannot open shared object file: No such file or directory Loading `libextractor_ole2' plugin failed: libextractor_ole2.so: cannot open shared object file: No such file or directory Loading `libextractor_ogg' plugin failed: libextractor_ogg.so: cannot open shared object file: No such file or directory Loading `libextractor_mpeg' plugin failed: libextractor_mpeg.so: cannot open shared object file: No such file or directory Segmentation fault -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing'), (550, 'unstable'), (500, 'stable'), (350, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.20-rt8-vanilla-dellxps-skas3-v8.2 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages strigi-daemon depends on: ii libbz2-1.0 1.0.3-6 high-quality block-sorting file co ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libclucene0 0.9.16a-1library for full-featured text sea ii libdbus-1-3 1.0.2-1 simple interprocess messaging syst ii libexpat1 1.95.8-3.4 XML parsing C library - runtime li ii libgcc1 1:4.1.1-21 GCC support library ii liblog4cxx9c2a 0.9.7-6 A logging library for C++ ii libssl0.9.8 0.9.8c-4 SSL shared libraries ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libstreamindexer0 0.3.11-1 streamindexer library for Strigi D ii libstreams0 0.3.11-1 streams library for for Strigi Des ii wv 1.2.4-1 Programs for accessing Microsoft W ii xpdf-utils [poppler-utils] 3.01-9 Portable Document Format (PDF) sui ii zlib1g 1:1.2.3-13 compression library - runtime strigi-daemon recommends no packages. -- no debconf information -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. Stealing logic from one person is plagiarism, stealing from many is research. The great are those who achieve the impossible, the petty are those who cannot - rrs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411922: FW: libpam-ldap upgrade breaks pam_ldap.conf and can't login
Il giorno mer, 21/02/2007 alle 16.23 -0500, Jamie ffolliott ha scritto: Package: libpam-ldap Version: 180-1.6 3rd report - can we please get an acknowledgement from somebody? The package is still broken in how it handles existing settings upon upgrades, and these settings are critical to authentication working. [...] I'll provide a patch during the weekend. Bye, Giuseppe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
