Bug#456992: smbfs: mount.cifs fails with mount error: could not find target server. TCP name ... not found
On Tue, Dec 18, 2007 at 04:13:40PM -0800, Steve Langasek wrote: Hi Julian, Hi Steve! On Tue, Dec 18, 2007 at 10:03:57PM +, Julian Gilbey wrote: Package: smbfs Version: 3.0.28-1~lenny1 Severity: serious I have just upgraded from 3.0.27a-1 to this version, and now when I try to mount my Samba partition, I get the following error: euclid:~ # mount -t cifs //WGS-SVR-001/RMStaff /mnt/wggs/rmstaff -o credentials=/etc/wggs.credentials,uid=jdg,gid=jdg mount error: could not find target server. TCP name WGS-SVR-001/RMStaff not found No ip address specified and hostname not found euclid:~ # Any idea why this might be the case? I've never seen this error before, and I can list the partition just fine. Also: smbclient --user jgi --command=dir //WGS-SVR-001/RMStaff works just fine. Is this hostname resolvable via DNS (i.e., how about ping WGS-SVR-001 instead of smbclient as a test)? The mount.cifs program doesn't support WINS-based host resolution (nor mount.smbfs, IIRC). C.f. bug #311709. I'll check and let you know. But something has clearly changed between version 3.0.27a-1 and this version, as it did work until now. And if it is a DNS issue, then how on earth am I meant to specify the partition to mount.cifs?! Many thanks for the swift response. Julian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457014: ocaml-nox: Bad permissions on ocamldoc-api-ref-config
On Wed, Dec 19, 2007 at 08:59:50AM +0100, Stefano Zacchiroli wrote: I just tried on my home box (amd64/sid), and cannot reproduce the error you describe on recompiling cryptgps. mmmh, this is strange, I really don't see how can it built find for you: the cdbs class now invokes /usr/share/cdbs/1/class/ocamldoc-api-ref-config and that file is not executable here: $ ls -l /usr/share/cdbs/1/class/ocamldoc-api-ref-config -rw-r--r-- 1 root root 2238 2007-12-17 13:41 /usr/share/cdbs/1/class/ocamldoc-api-ref-config Can you please check whether the above file is executable for you or not? I've committed on the svn repo what I think is a fix for this (see my previous post to this bugreport). Before uploading however, I'll wait for some info from Ralf, since given his test in which the FTBFS does not manifest itself I fear there is something more to be understood ... Cheers. -- Stefano Zacchiroli -*- PhD in Computer Science ... now what? [EMAIL PROTECTED],debian.org,bononia.it} -%- http://www.bononia.it/zack/ (15:56:48) Zack: e la demo dema ?/\All one has to do is hit the (15:57:15) Bac: no, la demo scema\/right keys at the right time signature.asc Description: Digital signature
Processed: setting package to camlp4 camlp4-extra ocaml ocaml-base ocaml-base-nox ocaml-compiler-libs ocaml-interp ocaml-mode ocaml-native-compilers ocaml-nox ocaml-source ...
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.11 package camlp4 camlp4-extra ocaml ocaml-base ocaml-base-nox ocaml-compiler-libs ocaml-interp ocaml-mode ocaml-native-compilers ocaml-nox ocaml-source Ignoring bugs not assigned to: ocaml-native-compilers ocaml-interp ocaml-compiler-libs ocaml-mode ocaml-nox ocaml-base camlp4-extra ocaml camlp4 ocaml-source ocaml-base-nox tags 457014 + pending Bug#457014: ocaml-nox: Bad permissions on ocamldoc-api-ref-config Tags were: confirmed Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457014: ocaml-nox: Bad permissions on ocamldoc-api-ref-config
On Wed, Dec 19, 2007 at 08:44:32AM +0100, Ralf Treinen wrote: I just tried on my home box (amd64/sid), and cannot reproduce the error you describe on recompiling cryptgps. mmmh, this is strange, I really don't see how can it built find for you: the cdbs class now invokes /usr/share/cdbs/1/class/ocamldoc-api-ref-config and that file is not executable here: $ ls -l /usr/share/cdbs/1/class/ocamldoc-api-ref-config -rw-r--r-- 1 root root 2238 2007-12-17 13:41 /usr/share/cdbs/1/class/ocamldoc-api-ref-config Can you please check whether the above file is executable for you or not? TIA Cheers. -- Stefano Zacchiroli -*- PhD in Computer Science ... now what? [EMAIL PROTECTED],debian.org,bononia.it} -%- http://www.bononia.it/zack/ (15:56:48) Zack: e la demo dema ?/\All one has to do is hit the (15:57:15) Bac: no, la demo scema\/right keys at the right time signature.asc Description: Digital signature
Bug#457014: ocaml-nox: Bad permissions on ocamldoc-api-ref-config
Hi, On Tue, Dec 18, 2007 at 11:52:11PM -0500, Daniel Schepler wrote: Package: ocaml-nox Version: 3.10.0-9 Severity: serious I'm seeing several ocaml-related build failures. For example, from my cryptgps build log using an i386 pbuilder chroot: ... ocamlopt -inline 1 -unsafe -c crypt_3des.ml ocamlopt -inline 1 -unsafe -c crypt_blowfish32.ml ocamlopt -a -o cryptgps.cmxa crypt_aux.cmx cryptsystem_64.cmx cryptmodes_64.cmx crypt_blowfish.cmx crypt_des.cmx crypt_3des.cmx crypt_blowfish32.cmx make[1]: Leaving directory `/tmp/buildd/cryptgps-0.2.1' touch debian/stamp-makefile-build DEB_MAKE_CHECK_TARGET unset, not running checks /bin/sh: line 2: /usr/share/cdbs/1/class/ocamldoc-api-ref-config: Permission denied make: *** [build/libcryptgps-ocaml-dev] Error 126 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 I can also reproduce this on amd64 using ocaml packages compiled from source. I just tried on my home box (amd64/sid), and cannot reproduce the error you describe on recompiling cryptgps. ocaml: 3.10.0-9 cryptgps: 0.2.1-3 Can you send a complete log, including the exact versions of the involved packages? -Ralf. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436200: marked as done (since last update motion suddenly won't store motion-triggered movies)
Your message dated Wed, 19 Dec 2007 08:32:07 + with message-id [EMAIL PROTECTED] and subject line Bug#436200: fixed in motion 3.2.9-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: motion Version: 3.2.3-2.1+b3 Severity: grave Justification: renders package unusable since last update motion suddenly won't store motion-triggered movies when run with -n -d 255 it gives the following output: [0] Processing thread 0 - config file /etc/motion/motion.conf [0] Unknown config option always_changes: No such file or directory [0] Unknown config option debug_parameter: No such file or directory [1] Thread is from /etc/motion/motion.conf [1] Thread started [1] motion-httpd/3.2.3 running, accepting connections [1] motion-httpd: waiting for data on port TCP 8080 [1] Started stream webcam server in port 8000 [1] File of type 2 saved to: /data/webcam/snapshot.jpg [1] File of type 32 saved to: /data/webcam/20070806-timelapse.mpg [1] File of type 2 saved to: /data/webcam/snapshot.jpg [1] File of type 2 saved to: /data/webcam/snapshot.jpg [1] Codec not found: Success mpeg1 support is not included it says and msmpeg4 and mpeg4 give the logging as seen above. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18-3-686 (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages motion depends on: ii debconf [debconf-2.0 1.5.13 Debian configuration management sy ii liba52-0.7.4 0.7.4-11library for decoding ATSC A/52 str ii libavcodec1d 0.cvs20070307-6 ffmpeg codec library ii libavformat1d0.cvs20070307-6 ffmpeg file format library ii libavutil1d 0.cvs20070307-6 ffmpeg utility library ii libc62.6-2 GNU C Library: Shared libraries ii libdc1394-13 1.1.0-3+b1 high level programming interface f ii libgsm1 1.0.10-13 Shared libraries for GSM speech co ii libjpeg626b-13 The Independent JPEG Group's JPEG ii libmysqlclient15off 5.0.41a-1 MySQL database client library ii libogg0 1.1.3-2 Ogg Bitstream Library ii libpq5 8.2.4-2 PostgreSQL C client library ii libraw1394-8 1.2.1-2 library for direct access to IEEE ii libtheora0 0.0.0.alpha7.dfsg-2 The Theora Video Compression Codec ii libvorbis0a 1.1.2.dfsg-2The Vorbis General Audio Compressi ii libvorbisenc21.1.2.dfsg-2The Vorbis General Audio Compressi ii zlib1g 1:1.2.3.3.dfsg-5compression library - runtime Versions of packages motion recommends: ii ffmpeg 0.cvs20070307-6 multimedia player, server and enco -- debconf information: motion/moved_conf_dir: ---End Message--- ---BeginMessage--- Source: motion Source-Version: 3.2.9-1 We believe that the bug you reported is fixed in the latest version of motion, which is due to be installed in the Debian FTP archive: motion_3.2.9-1.diff.gz to pool/main/m/motion/motion_3.2.9-1.diff.gz motion_3.2.9-1.dsc to pool/main/m/motion/motion_3.2.9-1.dsc motion_3.2.9-1_i386.deb to pool/main/m/motion/motion_3.2.9-1_i386.deb motion_3.2.9.orig.tar.gz to pool/main/m/motion/motion_3.2.9.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. Juan Angulo Moreno [EMAIL PROTECTED] (supplier of updated motion package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 14 Nov 2007 15:14:33 -0400 Source: motion Binary: motion Architecture: source i386 Version: 3.2.9-1 Distribution: unstable Urgency: low Maintainer: Juan Angulo Moreno [EMAIL PROTECTED] Changed-By: Juan Angulo Moreno [EMAIL PROTECTED] Description: motion - V4L capture program supporting motion detection Closes: 285247 328752 385938 394196 394242 410074 415512 425774 427228 436200 445750 447013 Changes:
Bug#456992: smbfs: mount.cifs fails with mount error: could not find target server. TCP name ... not found
On Wed, Dec 19, 2007 at 07:47:34AM +, Julian Gilbey wrote: I have just upgraded from 3.0.27a-1 to this version, and now when I try to mount my Samba partition, I get the following error: euclid:~ # mount -t cifs //WGS-SVR-001/RMStaff /mnt/wggs/rmstaff -o credentials=/etc/wggs.credentials,uid=jdg,gid=jdg mount error: could not find target server. TCP name WGS-SVR-001/RMStaff not found No ip address specified and hostname not found euclid:~ # Any idea why this might be the case? I've never seen this error before, and I can list the partition just fine. Also: smbclient --user jgi --command=dir //WGS-SVR-001/RMStaff works just fine. Is this hostname resolvable via DNS (i.e., how about ping WGS-SVR-001 instead of smbclient as a test)? The mount.cifs program doesn't support WINS-based host resolution (nor mount.smbfs, IIRC). C.f. bug #311709. I'll check and let you know. But something has clearly changed between version 3.0.27a-1 and this version, as it did work until now. And if it is a DNS issue, then how on earth am I meant to specify the partition to mount.cifs?! Well, are you sure that something in your DNS didn't change since the point when you were using 3.0.27a? I really don't know of any other way this would've worked for you with the given commandline. To mount such shares without DNS support, you have three options: - add your own entry in /etc/hosts - add nss_wins from the winbind package to your nsswitch.conf - use the ip= option to mount.cifs Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#456860: gromacs: FTBFS: checking size of int... configure: error: cannot compute sizeof (int)
Am Dienstag, den 18.12.2007, 16:39 -0800 schrieb Nicholas Breen: Is it somewhere publically available? I'd be happy to test it as well, it'll be interesting to see if it also works with GROMACS 3.3.3-beta packages. Yes, you can find it in the SVN repository linked at http://packages.qa.debian.org/o/openmpi.html Thanks for testing! (And telling me that 3.3.3-beta is out. I totally missed that.) Best regards Manuel signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#456844: same bug on libboost-regex-dev (1.34.1-2.1) and on -3
Hi! I was updating from my own version of -2 compiled against the new libicu to the newly uploaded -2.1 version (which should more or less be the same as my version) when I noticed that the new libboost-regex-dev still depends on libicu36-dev instead of libicu-dev, for what I see you forgot to change that on the Depends of libboost-regex-dev on the control file. This also seems to happen on -3 version which is currently in experimental. Regards... -- Manty/BestiaTester - http://manty.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: .
Processing commands for [EMAIL PROTECTED]: forwarded 456399 upstream Bug#456399: dash 0.5.4-3 dies with SIGBUS on sparc Noted your statement that Bug has been forwarded to upstream. 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#457044: History of the session before reboot
Here's the whole session from login to reboot, hoping this will help sorry, but messages are in french --- [EMAIL PROTECTED]:~$ ns1 Password: channel 1: open failed: administratively prohibited: open failed Last login: Tue Dec 18 10:59:04 2007 from lnxgw.mimizan.com Linux ns1.mimizan.net 2.6.18-4-686 #1 SMP Mon Mar 26 17:17:36 UTC 2007 i686 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. No mail. [EMAIL PROTECTED]:~] $ apt-get update Réception de : 1 http://security.debian.org stable/updates Release.gpg [189B] Ign http://security.debian.org stable/updates/main Translation-fr Ign http://security.debian.org stable/updates/contrib Translation-fr Ign http://security.debian.org stable/updates/non-free Translation-fr Réception de : 2 http://security.debian.org testing/updates Release.gpg [189B] Ign http://security.debian.org testing/updates/main Translation-fr Ign http://security.debian.org testing/updates/contrib Translation-fr Ign http://security.debian.org testing/updates/non-free Translation-fr Atteint http://security.debian.org stable/updates Release Atteint http://security.debian.org testing/updates Release Ign http://security.debian.org stable/updates/main Packages/DiffIndex Ign http://security.debian.org stable/updates/contrib Packages/DiffIndex Ign http://security.debian.org stable/updates/non-free Packages/DiffIndex Ign http://security.debian.org testing/updates/main Packages/DiffIndex Ign http://security.debian.org testing/updates/contrib Packages/DiffIndex Ign http://security.debian.org testing/updates/non-free Packages/DiffIndex Atteint http://security.debian.org stable/updates/main Packages Atteint http://security.debian.org stable/updates/contrib Packages Atteint http://security.debian.org stable/updates/non-free Packages Atteint http://security.debian.org testing/updates/main Packages Atteint http://security.debian.org testing/updates/contrib Packages Atteint http://security.debian.org testing/updates/non-free Packages Réception de : 3 http://debian.ibisc.univ-evry.fr stable Release.gpg [378B] Ign http://debian.ibisc.univ-evry.fr stable/main Translation-fr Ign http://debian.ibisc.univ-evry.fr stable/contrib Translation-fr Ign http://debian.ibisc.univ-evry.fr stable/non-free Translation-fr Réception de : 4 http://debian.ibisc.univ-evry.fr testing Release.gpg [189B] Ign http://debian.ibisc.univ-evry.fr testing/main Translation-fr Ign http://debian.ibisc.univ-evry.fr testing/contrib Translation-fr Ign http://debian.ibisc.univ-evry.fr testing/non-free Translation-fr Réception de : 5 http://debian.ibisc.univ-evry.fr stable Release [58,2kB] Réception de : 6 http://debian.ibisc.univ-evry.fr testing Release [68,5kB] Réception de : 7 http://debian.ibisc.univ-evry.fr stable/main Packages [4287kB] Réception de : 8 http://debian.ibisc.univ-evry.fr stable/contrib Packages [62,9kB] Réception de : 9 http://debian.ibisc.univ-evry.fr stable/non-free Packages [84,5kB] Réception de : 10 http://debian.ibisc.univ-evry.fr testing/main Packages [4892kB] Réception de : 11 http://debian.ibisc.univ-evry.fr testing/contrib Packages [79,7kB] Réception de : 12 http://debian.ibisc.univ-evry.fr testing/non-free Packages [91,7kB] 9625ko réceptionnés en 17s (547ko/s) Lecture des listes de paquets... Fait [EMAIL PROTECTED]:~] $ apt-get upgrade -s Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Les paquets suivants ont été conservés : phpix xinetd Les paquets suivants seront mis à jour : apt-listchanges groff groff-base kernel-image-2.6-686 libbind9-0 libc6 libc6-dev libdns22 libisc11 libisccc0 libisccfg1 liblwres9 libssl0.9.7 linux-image-2.6.18-4-686 locales 15 mis à jour, 0 nouvellement installés, 0 à enlever et 2 non mis à jour. Inst linux-image-2.6.18-4-686 [2.6.18.dfsg.1-12] (2.6.18.dfsg.1-12etch2 Debian-Security:stable) Inst libc6-dev [2.7-3] (2.7-4 Debian:testing) [] Inst libc6 [2.7-3] (2.7-4 Debian:testing) Conf libc6 (2.7-4 Debian:testing) Inst groff [1.18.1.1-13] (1.18.1.1-15 Debian:testing) [] Inst groff-base [1.18.1.1-13] (1.18.1.1-15 Debian:testing) Inst libisc11 [1:9.3.4-2] (1:9.3.4-2etch1 Debian-Security:stable) Inst libdns22 [1:9.3.4-2] (1:9.3.4-2etch1 Debian-Security:stable) Inst libisccc0 [1:9.3.4-2] (1:9.3.4-2etch1 Debian-Security:stable) Inst libisccfg1 [1:9.3.4-2] (1:9.3.4-2etch1 Debian-Security:stable) Inst libbind9-0 [1:9.3.4-2] (1:9.3.4-2etch1 Debian-Security:stable) Inst liblwres9 [1:9.3.4-2] (1:9.3.4-2etch1 Debian-Security:stable) Inst locales [2.7-3] (2.7-4 Debian:testing) Inst apt-listchanges [2.75] (2.79 Debian:testing) Inst kernel-image-2.6-686 [1:2.6.18+6etch1] (1:2.6.18+6etch2 Debian-Security:stable)
Bug#456398: dash 0.5.4-3 (alpha/unstable): FTBFS: undefined reference to `imaxdiv'
On Sat, Dec 15, 2007 at 01:36:11AM -0800, Steve Langasek wrote: The lastest version of dash in unstable is failing to build with the following error: [...] cc -Wall -g -O2 -Wall -o dash alias.o arith_yacc.o arith_yylex.o cd.o error.o eval.o exec.o expand.o histedit.o input.o jobs.o mail.o main.o memalloc.o miscbltin.o mystring.o options.o parser.o redir.o show.o trap.o output.o printf.o system.o test.o times.o var.o builtins.o init.o nodes.o signames.o syntax.o arith_yacc.o: In function `do_binop': /build/buildd/dash-0.5.4/build-tmp/../src/arith_yacc.c:99: undefined reference to `imaxdiv' /build/buildd/dash-0.5.4/build-tmp/../src/arith_yacc.c:99: undefined reference to `imaxdiv' collect2: ld returned 1 exit status make[4]: *** [dash] Error 1 [...] A full build log can be found at http://buildd.debian.org/fetch.cgi?pkg=dasharch=alphaver=0.5.4-3stamp=1197300195file=logas=raw. This appears to be a result of a new patch, 0026-ARITH-Add-assignment-and-intmax_t-support.diff, introduced in this version. Although there's an imaxdiv() manpage on alpha, I can't find any evidence that it's implemented on this architecture. Hi Steve, but it should, me thinks, imaxdiv() is in posix ieee1003.1-2004 and LSB 1.3 http://www.opengroup.org/onlinepubs/009695399/functions/imaxdiv.html http://refspecs.freestandards.org/LSB_1.3.0/gLSB/gLSB.html#AEN3263 Thanks, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#456399: [PATCH] [EVAL] Fix unaligned trap on sparc
From: Steve Langasek [EMAIL PROTECTED]
dash dies on sparc with a SIGBUS due to an arithmetic error introduced
with commit 03b4958, this patch fixes it.
---
Hi Gerrit,
dash 0.5.4-3 dies on sparc with a SIGBUS due to an arithmetic error
introduced with the patch
0030-EXEC-Fixed-execing-of-scripts-with-no-hash-bang.diff. The
attached
patch fixes the problem.
Thanks for the patch, Steve.
Hi Herbert, I suggest to apply this change from Steve.
Regards, Gerrit.
src/eval.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/eval.c b/src/eval.c
index a8feaa0..fd2c394 100644
--- a/src/eval.c
+++ b/src/eval.c
@@ -722,7 +722,7 @@ evalcommand(union node *cmd, int flags)
}
/* Reserve one extra spot at the front for shellexec. */
- argv = nargv = stalloc(sizeof (char *) * (argc + 2)) + 1;
+ argv = nargv = ((char **)stalloc(sizeof (char *) * (argc + 2))) + 1;
for (sp = arglist.list ; sp ; sp = sp-next) {
TRACE((evalcommand arg: %s\n, sp-text));
*nargv++ = sp-text;
--
1.5.3.4
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457044: My box didn't reboot after upgrading linux-image-2.6.18-4-686
Package: linux-image-2.6.18-4-686 Version: linux-image-2.6.18-4-686 2.6.18.dfsg.1-12etch2 Severity: critical Justification: breaks the whole system This morning, as usual I did : apt-get update apt-get upgrade today, there was a security update on linux-image-2.6.18-4-686 I followed the given instructions : You are attempting to install a kernel version that is the same as the version you are currently running (version 2.6.18-4-686). The modules list is quite likely to have been changed, and the modules dependency file /lib/modules/2.6.18-4-686/modules.dep needs to be re-built. It can not be built correctly right now, since the module list for the running kernel are likely to be different from the kernel installed. I am creating a new modules.dep file, but that may not be correct. It shall be regenerated correctly at next reboot. ? I repeat: you have to reboot in order for the modules file to be created correctly. Until you reboot, it may be impossible to load some modules. Reboot as soon as this install is finished (Do not reboot right now, since you may not be able to boot back up until installation is over, but boot immediately after). I can not stress that too much. You need to reboot soon. So I rebooted my machine (a distant one) And then... nothing else. My production server never came up until now. I asked to my hosting provider an electrical reboot as I had no way to act, but the machine didn't boot. As it's a distant server, I can't tell you what error messages it can show. The only thing I can provide is the listing of the session from the apt-get upgrade command to the reboot command I'll send it in a next post Of course, I'm not sending this report for the concerned server, as at the moment it's dead, but from a local test box with a very similar configuration -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Shell: /bin/sh linked to /bin/bash -- Ce message a été vérifié par MailScanner pour des virus ou des polluriels et rien de suspect n'a été trouvé. For all your IT requirements visit: http://www.transtec.co.uk
Bug#457014: marked as done (ocaml-nox: Bad permissions on ocamldoc-api-ref-config)
Your message dated Wed, 19 Dec 2007 11:02:05 + with message-id [EMAIL PROTECTED] and subject line Bug#457014: fixed in ocaml 3.10.0-10 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: ocaml-nox Version: 3.10.0-9 Severity: serious I'm seeing several ocaml-related build failures. For example, from my cryptgps build log using an i386 pbuilder chroot: ... ocamlopt -inline 1 -unsafe -c crypt_3des.ml ocamlopt -inline 1 -unsafe -c crypt_blowfish32.ml ocamlopt -a -o cryptgps.cmxa crypt_aux.cmx cryptsystem_64.cmx cryptmodes_64.cmx crypt_blowfish.cmx crypt_des.cmx crypt_3des.cmx crypt_blowfish32.cmx make[1]: Leaving directory `/tmp/buildd/cryptgps-0.2.1' touch debian/stamp-makefile-build DEB_MAKE_CHECK_TARGET unset, not running checks /bin/sh: line 2: /usr/share/cdbs/1/class/ocamldoc-api-ref-config: Permission denied make: *** [build/libcryptgps-ocaml-dev] Error 126 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 I can also reproduce this on amd64 using ocaml packages compiled from source. -- Daniel Schepler ---End Message--- ---BeginMessage--- Source: ocaml Source-Version: 3.10.0-10 We believe that the bug you reported is fixed in the latest version of ocaml, which is due to be installed in the Debian FTP archive: camlp4-extra_3.10.0-10_i386.deb to pool/main/o/ocaml/camlp4-extra_3.10.0-10_i386.deb camlp4_3.10.0-10_i386.deb to pool/main/o/ocaml/camlp4_3.10.0-10_i386.deb ocaml-base-nox_3.10.0-10_i386.deb to pool/main/o/ocaml/ocaml-base-nox_3.10.0-10_i386.deb ocaml-base_3.10.0-10_i386.deb to pool/main/o/ocaml/ocaml-base_3.10.0-10_i386.deb ocaml-compiler-libs_3.10.0-10_i386.deb to pool/main/o/ocaml/ocaml-compiler-libs_3.10.0-10_i386.deb ocaml-interp_3.10.0-10_i386.deb to pool/main/o/ocaml/ocaml-interp_3.10.0-10_i386.deb ocaml-mode_3.10.0-10_all.deb to pool/main/o/ocaml/ocaml-mode_3.10.0-10_all.deb ocaml-native-compilers_3.10.0-10_i386.deb to pool/main/o/ocaml/ocaml-native-compilers_3.10.0-10_i386.deb ocaml-nox_3.10.0-10_i386.deb to pool/main/o/ocaml/ocaml-nox_3.10.0-10_i386.deb ocaml-source_3.10.0-10_all.deb to pool/main/o/ocaml/ocaml-source_3.10.0-10_all.deb ocaml_3.10.0-10.diff.gz to pool/main/o/ocaml/ocaml_3.10.0-10.diff.gz ocaml_3.10.0-10.dsc to pool/main/o/ocaml/ocaml_3.10.0-10.dsc ocaml_3.10.0-10_i386.deb to pool/main/o/ocaml/ocaml_3.10.0-10_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Zacchiroli [EMAIL PROTECTED] (supplier of updated ocaml package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 19 Dec 2007 08:37:02 +0100 Source: ocaml Binary: ocaml-compiler-libs ocaml-native-compilers ocaml-base ocaml-nox ocaml-mode ocaml-interp ocaml-source camlp4-extra ocaml-base-nox ocaml camlp4 Architecture: source i386 all Version: 3.10.0-10 Distribution: unstable Urgency: low Maintainer: Debian OCaml Maintainers [EMAIL PROTECTED] Changed-By: Stefano Zacchiroli [EMAIL PROTECTED] Description: camlp4 - Pre Processor Pretty Printer for OCaml camlp4-extra - Pre Processor Pretty Printer for OCaml - extras ocaml - ML language implementation with a class-based object system ocaml-base - Runtime system for ocaml bytecode executables ocaml-base-nox - Runtime system for ocaml bytecode executables ocaml-compiler-libs - OCaml interpreter and standard libraries ocaml-interp - OCaml interactive interpreter and standard libraries ocaml-mode - A major mode for editing Objective Caml in Emacs ocaml-native-compilers - Native code compilers of the ocaml suite (the .opt ones) ocaml-nox - ML language implementation with a class-based object system ocaml-source - Sources for Objective Caml Closes: 457014 Changes: ocaml (3.10.0-10) unstable; urgency=low . [ Stefano Zacchiroli ] * ignore ocamldoc-api-ref-config when invoking dh_fixperms, so that it remains executable (closes: #457014) Files: 89c82957989c46e8b33fc94745c31e89 1218 devel optional ocaml_3.10.0-10.dsc 3f9ca7594139b6e5d6900b23c45480dd 90695 devel optional ocaml_3.10.0-10.diff.gz
Bug#456721: [Pkg-openmpi-maintainers] Processed: Re: Bug#456721:libpetsc.so depends on unexistent libraries
Am Dienstag, den 18.12.2007, 21:23 -0600 schrieb Dirk Eddelbuettel: On 19 December 2007 at 01:29, Manuel Prinz wrote: | I'm not sure about that. I didn't see that on a quick read of chapters 8 | and 10, though policy states in 10.2: | Packages that use libtool to create shared libraries should | include the .la files in the -dev package, unless the package | relies on libtool's libltdl library, in which case the .la | files must go in the run-time library package. That's not what I had I mind. I think there was a more general recommendation of sticking .so files, headers files, static libraries, ... into the -dev package. Anyway, I may well be wrong. You're right, chapter 8 is about that. It explains how the packaging has to be done and that static libraries have to go into the -dev package. But I can't find that one has to provide static libraries. Some comments and questions: [...] 2) I do not understand some of the file splits. Eg why /usr/lib/libmca_common_sm.so.0 Why does that need to be in /usr/lib/ and not hidden below like the other mca* ones ? Ldd on the Rmpi library doesn't show it, maybe other MPI usage does. Do you know a case where it is needed? The files was placed in /usr/lib before and not in /usr/lib/openmpi where the private libs where, so I expected it to be essential. I installed everything in the place where upstream installs them. (Leaving the symlinking aside.) 3) Links like libopen-rte.so.0 - openmpi/lib/libopen-rte.so.0 libopen-rte.so - openmpi/lib/libopen-rte.so.0 work but shouldn't it be libopen-rte.so.0 - openmpi/lib/libopen-rte.so.0 libopen-rte.so - libopen-rte.so.0 Doesn't really matter -- mere cosmetics. You're right but I think we should change this nevertheless. I'll commit a patch. Since it's cosmetic, it can go to the next upload. (Which will be the new upstream version, I guess.) 4) Should mpi.h be in /usr/include ? I had to tell Rmpi that the main MPI dir is /usr/lib/openmpi/, then everythings works due to the usual include/ and lib/ split. Good question. LAM provides a file named mpi.h as well but just installs it in the private include dir. This should work for us as well, though I just spotted that a package named pgapack ships a mpi.h file too. Even if we want to handle it via alternatives (which LAM doesn't) we have check the situation in pgapack, so we don't get a problem there. What is the advantage to have mpi.h in /usr/include? (Just curious.) 5) Some Lintian warnings remain (but I now added two more silencers, so the last two should go) -- could you try and see why your man page patch doesn't cover'em ? I know that problem. It seems to be related to the whitespaces in the program name. I guess that's simply not allowed and not quite sure how to fix that. I'm not so much of a *roff person, to be honest. But I try to figure that out, though it has a low priority in my list. Best regards Manuel signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#454212: megahal: Confirmed in etch
Package: megahal
Version: 9.1.1a-1
Followup-For: Bug #454212
Confirmed using etch i386 (though an amd64 processor). Attached output
of megahal and strace.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages megahal depends on:
ii libc6 2.3.6.ds1-13etch2 GNU C Library: Shared libraries
megahal recommends no packages.
-- no debconf information
[EMAIL PROTECTED]:~$ megahal
++
||
| ## ## ####### |
| ## ## # ## # # ## # # # ### |
| # ## # # # ## ## ## # # # |
| ## # # ### ## ## ## # # # ### |
| ## # ## ## ## ## ## # # # |
| ## ## ## ## ## ### ###r6 |
||
|Copyright(C) 1998 Jason Hutchens|
++
Segmentation fault
[EMAIL PROTECTED]:~$ strace megahal
execve(/usr/bin/megahal, [megahal], [/* 30 vars */]) = 0
uname({sys=Linux, node=nmcgovern, ...}) = 0
brk(0) = 0x805
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0xb7fd7000
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or
directory)open(/etc/ld.so.cache, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=73905, ...}) = 0
mmap2(NULL, 73905, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7fc4000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)open(/lib/tls/i686/cmov/libm.so.6, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`3\0\000..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=145136, ...}) = 0
mmap2(NULL, 147584, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb7f9f000
mmap2(0xb7fc2000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x22) = 0xb7fc2000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)open(/lib/tls/i686/cmov/libc.so.6, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\240O\1..., 512) =
512fstat64(3, {st_mode=S_IFREG|0644, st_size=1241392, ...}) = 0
mmap2(NULL, 1247388, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb7e6e000
mmap2(0xb7f95000, 28672, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x127) = 0xb7f95000
mmap2(0xb7f9c000, 10396, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7f9c000
close(3)= 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7e6d000
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7e6c000
mprotect(0xb7f95000, 20480, PROT_READ) = 0
set_thread_area({entry_number:-1 - 6, base_addr:0xb7e6c6c0, limit:1048575,
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0,
useable:1}) = 0
munmap(0xb7fc4000, 73905) = 0
brk(0) = 0x805
brk(0x8071000) = 0x8071000
stat64(/home/nmcgovern/.megahal, {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
open(/home/nmcgovern/.megahal/megahal.logi, O_WRONLY|O_APPEND|O_CREAT, 0666)
= 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=304, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7fd6000
fstat64(3, {st_mode=S_IFREG|0644, st_size=304, ...}) = 0
_llseek(3, 304, [304], SEEK_SET)= 0
time(NULL) = 1198064259
open(/etc/localtime, O_RDONLY)= 4
fstat64(4, {st_mode=S_IFREG|0644, st_size=1323, ...}) = 0
fstat64(4, {st_mode=S_IFREG|0644, st_size=1323, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7fd5000
read(4, TZif\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\7\0\0\0\7\0..., 4096) =
1323
close(4)= 0
munmap(0xb7fd5000, 4096)= 0
stat64(/etc/localtime, {st_mode=S_IFREG|0644, st_size=1323, ...}) = 0
write(3, MegaHALv8\nCopyright (C) 1998 Jas..., 76) = 76
open(/home/nmcgovern/.megahal/megahal.txt, O_WRONLY|O_APPEND|O_CREAT, 0666) =
4
fstat64(4, {st_mode=S_IFREG|0644, st_size=304, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7fd5000
fstat64(4,
Bug#456898: GSL linking issue with new '--as-needed' option to GNU ld [Was: Bug#456898: libgsl0ldbl: Uses symbols from libcblas.so, but not linked with it]
At Tue, 18 Dec 2007 09:23:30 -0600, Dirk Eddelbuettel wrote: /usr/lib/libgsl.so: undefined reference to `cblas_zher2k' /usr/lib/libgsl.so: undefined reference to `cblas_strsv' /usr/lib/libgsl.so: undefined reference to `cblas_zdotc_sub' [ many more of these ] Can you see a way forward on this? Is is maybe a question of link order, ie could -lgslcblas -lgsl be an answer? The option -Wl,--as-needed needs to be disabled in some way, if it's applied globally it's certainly not compatible with libraries that depend on other libraries (surely a fairly common occurrence?). The link order is not a factor. Maybe there is some official way to turn off that feature in qmake, or to make it behave more intelligently with regard to external libraries vs Qt libraries. Otherwise one could put the gsl library at the end of the libraries list with -Wl,--no-as-needed: -Wl,--no-as-needed -lgsl -lgslcblas -lm -- Brian Gough -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#456596: Non-maintainer upload.
diff -Nru /tmp/z2bNG5yT2j/gcc-defaults-1.61/debian/changelog
/tmp/eh3mQ9ni2v/gcc-defaults-1.61.1/debian/changelog
--- /tmp/z2bNG5yT2j/gcc-defaults-1.61/debian/changelog 2007-09-04
02:41:56.0 +0200
+++ /tmp/eh3mQ9ni2v/gcc-defaults-1.61.1/debian/changelog2007-12-19
10:17:55.0 +0100
@@ -1,3 +1,10 @@
+gcc-defaults (1.61.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add gdc, make gdc-4.1 the default. Closes: #456596
+
+ -- Arthur Loiret [EMAIL PROTECTED] Wed, 19 Dec 2007 10:17:51 +0100
+
gcc-defaults (1.61) unstable; urgency=medium
* libgcj-common: Update classmap db's for gcj-4.3 as well.
diff -Nru /tmp/z2bNG5yT2j/gcc-defaults-1.61/debian/control
/tmp/eh3mQ9ni2v/gcc-defaults-1.61.1/debian/control
--- /tmp/z2bNG5yT2j/gcc-defaults-1.61/debian/control2007-09-03
00:12:53.0 +0200
+++ /tmp/eh3mQ9ni2v/gcc-defaults-1.61.1/debian/control 2007-12-19
10:00:31.0 +0100
@@ -238,3 +238,13 @@
This is a dependency package providing the default GNU Ada compiler.
Per policy, all packages that contain Ada sources must use this package
in their Build-Depends line.
+
+Package: gdc
+Priority: optional
+Architecture: any
+Depends: gdc-${pv:gdc} ${reqv:gdc}
+Replaces: gdc-4.1 ( 0.25-4.1.2-18)
+Description: The D compiler
+ This is a dependency package providing the default D compiler.
+ Per policy, all packages that contain D sources must use this package
+ in their Build-Depends line.
diff -Nru /tmp/z2bNG5yT2j/gcc-defaults-1.61/debian/README.Debian
/tmp/eh3mQ9ni2v/gcc-defaults-1.61.1/debian/README.Debian
--- /tmp/z2bNG5yT2j/gcc-defaults-1.61/debian/README.Debian 2007-09-01
12:05:15.0 +0200
+++ /tmp/eh3mQ9ni2v/gcc-defaults-1.61.1/debian/README.Debian2007-12-19
10:08:47.0 +0100
@@ -67,6 +67,7 @@
gobjc++ : gobjc++-4.2
gnat: gnat-4.2
gpc : gpc-2.1-3.4
+ gdc : gdc-4.1
Most of the documentation for GCC including the manual pages is
licensed under the GFDL and therefore not included in the main section.
@@ -155,8 +156,8 @@
Matthias Klose [EMAIL PROTECTED]
Ray Dassen [EMAIL PROTECTED]
Philip Blundell [EMAIL PROTECTED](arm-linux)
-Jeff Bailey [EMAIL PROTECTED](hurd-i386)
-Joel Baker [EMAIL PROTECTED] (netbsd-i386)
+Jeff Bailey [EMAIL PROTECTED](hurd-i386)
+Joel Baker [EMAIL PROTECTED] (netbsd-i386)
Ben Collins [EMAIL PROTECTED](sparc-linux)
Falk Hueffner [EMAIL PROTECTED] (alpha-linux)
Randolph Chung [EMAIL PROTECTED] (ia64-linux, hppa-linux)
@@ -165,6 +166,7 @@
Gerhard Tonn [EMAIL PROTECTED] (s390-linux)
Roman Zippel [EMAIL PROTECTED] (m68k-linux)
Ludovic Brenta [EMAIL PROTECTED] (gnat)
+Arthur Loiret [EMAIL PROTECTED] (gdc)
===
diff -Nru /tmp/z2bNG5yT2j/gcc-defaults-1.61/debian/README.Debian.m4
/tmp/eh3mQ9ni2v/gcc-defaults-1.61.1/debian/README.Debian.m4
--- /tmp/z2bNG5yT2j/gcc-defaults-1.61/debian/README.Debian.m4 2006-08-14
00:05:29.0 +0200
+++ /tmp/eh3mQ9ni2v/gcc-defaults-1.61.1/debian/README.Debian.m4 2007-12-19
09:59:30.0 +0100
@@ -72,6 +72,7 @@
ifenabled(`gobjc++',` gobjc++ : gobjc++-PV_GOBJCXX')
ifenabled(`gnat',` gnat: gnat-PV_GCC')
ifenabled(`gpc',` gpc : gpc-PV_GPC')
+ifenabled(`gdc',` gdc : gdc-PV_GDC')
ifenabled(`chill',`chill : chill-PV_CHILL')
ifdef(`GFDL',`dnl
@@ -172,8 +173,8 @@
Matthias Klose [EMAIL PROTECTED]
Ray Dassen [EMAIL PROTECTED]
Philip Blundell [EMAIL PROTECTED](arm-linux)
-Jeff Bailey [EMAIL PROTECTED](hurd-i386)
-Joel Baker [EMAIL PROTECTED] (netbsd-i386)
+Jeff Bailey [EMAIL PROTECTED](hurd-i386)
+Joel Baker [EMAIL PROTECTED] (netbsd-i386)
Ben Collins [EMAIL PROTECTED](sparc-linux)
Falk Hueffner [EMAIL PROTECTED] (alpha-linux)
Randolph Chung [EMAIL PROTECTED] (ia64-linux, hppa-linux)
@@ -182,6 +183,7 @@
Gerhard Tonn [EMAIL PROTECTED] (s390-linux)
Roman Zippel [EMAIL PROTECTED] (m68k-linux)
Ludovic Brenta [EMAIL PROTECTED] (gnat)
+Arthur Loiret [EMAIL PROTECTED] (gdc)
===
diff -Nru /tmp/z2bNG5yT2j/gcc-defaults-1.61/debian/rules
/tmp/eh3mQ9ni2v/gcc-defaults-1.61.1/debian/rules
--- /tmp/z2bNG5yT2j/gcc-defaults-1.61/debian/rules 2007-09-03
00:46:50.0 +0200
+++ /tmp/eh3mQ9ni2v/gcc-defaults-1.61.1/debian/rules2007-12-19
10:09:29.0 +0100
@@ -71,6 +71,7 @@
REL_NO_421 := $(shell expr $(VMINOR) - 55)$(REL_EXT)
GPC_VERSION:= 2.1
Bug#456898: GSL linking issue with new '--as-needed' option to GNU ld [Was: Bug#456898: libgsl0ldbl: Uses symbols from libcblas.so, but not linked with it]
On 19 December 2007 at 11:53, Brian Gough wrote: | At Tue, 18 Dec 2007 09:23:30 -0600, | Dirk Eddelbuettel wrote: | /usr/lib/libgsl.so: undefined reference to `cblas_zher2k' | /usr/lib/libgsl.so: undefined reference to `cblas_strsv' | /usr/lib/libgsl.so: undefined reference to `cblas_zdotc_sub' | [ many more of these ] | | Can you see a way forward on this? Is is maybe a question of link order, ie | could -lgslcblas -lgsl be an answer? | | The option -Wl,--as-needed needs to be disabled in some way, if it's | applied globally it's certainly not compatible with libraries that | depend on other libraries (surely a fairly common occurrence?). The | link order is not a factor. | | Maybe there is some official way to turn off that feature in qmake, or | to make it behave more intelligently with regard to external libraries | vs Qt libraries. Otherwise one could put the gsl library at the end | of the libraries list with -Wl,--no-as-needed: | | -Wl,--no-as-needed -lgsl -lgslcblas -lm Thanks for the follow-up -- I agree with your point. Now we need to see if Debian is set on --as-needed wand wants it globally. Which could be an issue as you politely point out... Aurelien, comments/corrections? Dirk -- Three out of two people have difficulties with fractions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457062: exiftags: CVE-2007-6356 CVE-2007-6355 multiple vulnerabilities
Package: exiftags Severity: grave Tags: security Hi, the following CVE (Common Vulnerabilities Exposures) id was published for exiftags. CVE-2007-6356[0]: | exiftags before 1.01 allows attackers to cause a denial of service | (infinite loop) via recursive IFD references in the EXIF data in a | JPEG image. CVE-2007-6355[1]: | Unspecified vulnerability in exiftags before 1.01 has | unknown impact and attack vectors, resulting from a field | offset overflow, a different vulnerability than | CVE-2007-6354. If you fix this vulnerability please also include the CVE id in your changelog entry. For further information: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-6356 [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-6355 Kind regards Nico -- Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. pgpouDCSOObuf.pgp Description: PGP signature
Bug#456721: [Pkg-openmpi-maintainers] Processed: Re: Bug#456721:libpetsc.so depends on unexistent libraries
On 19 December 2007 at 13:08, Manuel Prinz wrote: | Am Dienstag, den 18.12.2007, 21:23 -0600 schrieb Dirk Eddelbuettel: | On 19 December 2007 at 01:29, Manuel Prinz wrote: | | I'm not sure about that. I didn't see that on a quick read of chapters 8 | | and 10, though policy states in 10.2: | | Packages that use libtool to create shared libraries should | | include the .la files in the -dev package, unless the package | | relies on libtool's libltdl library, in which case the .la | | files must go in the run-time library package. | | That's not what I had I mind. I think there was a more general recommendation | of sticking .so files, headers files, static libraries, ... into the -dev | package. Anyway, I may well be wrong. | | You're right, chapter 8 is about that. It explains how the packaging has | to be done and that static libraries have to go into the -dev package. | But I can't find that one has to provide static libraries. | | Some comments and questions: [...] | | 2) I do not understand some of the file splits. Eg why | /usr/lib/libmca_common_sm.so.0 | Why does that need to be in /usr/lib/ and not hidden below like the other | mca* ones ? Ldd on the Rmpi library doesn't show it, maybe other MPI | usage does. Do you know a case where it is needed? | | The files was placed in /usr/lib before and not in /usr/lib/openmpi | where the private libs where, so I expected it to be essential. I | installed everything in the place where upstream installs them. (Leaving | the symlinking aside.) Ah, so upstream places it there? I always buy that argument :) | 3) Links like | | libopen-rte.so.0 - openmpi/lib/libopen-rte.so.0 | libopen-rte.so - openmpi/lib/libopen-rte.so.0 | | work but shouldn't it be | | libopen-rte.so.0 - openmpi/lib/libopen-rte.so.0 | libopen-rte.so - libopen-rte.so.0 | | Doesn't really matter -- mere cosmetics. | | You're right but I think we should change this nevertheless. I'll commit | a patch. Since it's cosmetic, it can go to the next upload. (Which will | be the new upstream version, I guess.) | | 4) Should mpi.h be in /usr/include ? I had to tell Rmpi that the main MPI | dir is /usr/lib/openmpi/, then everythings works due to the usual | include/ and lib/ split. | | Good question. LAM provides a file named mpi.h as well but just installs | it in the private include dir. This should work for us as well, though I | just spotted that a package named pgapack ships a mpi.h file too. Even Ignore pgapack in Debian right now. I have been working on a new version with new copyright but it took some time to sort out, and is almost finished. Pgapack will then be sanely packaged instead of being a bit of a mess. | if we want to handle it via alternatives (which LAM doesn't) we have | check the situation in pgapack, so we don't get a problem there. What is | the advantage to have mpi.h in /usr/include? (Just curious.) Easy to find? | 5) Some Lintian warnings remain (but I now added two more silencers, so the | last two should go) -- could you try and see why your man page patch | doesn't cover'em ? | | I know that problem. It seems to be related to the whitespaces in the | program name. I guess that's simply not allowed and not quite sure how | to fix that. I'm not so much of a *roff person, to be honest. But I try | to figure that out, though it has a low priority in my list. I think this went away on my actual upload as I wrote later. Dirk | Best regards | Manuel -- Three out of two people have difficulties with fractions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: retitle 457062 to exiftags: CVE-2007-635{4,5,6} multiple vulnerabilities
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.10.11
retitle 457062 exiftags: CVE-2007-635{4,5,6} multiple vulnerabilities
Bug#457062: exiftags: CVE-2007-6356 CVE-2007-6355 multiple vulnerabilities
Changed Bug title to `exiftags: CVE-2007-635{4,5,6} multiple vulnerabilities'
from `exiftags: CVE-2007-6356 CVE-2007-6355 multiple vulnerabilities'.
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#457063: asterisk: CVE-2007-6430 remote unauthenticated sessions
Package: asterisk Severity: grave Tags: security Hi, the following CVE (Common Vulnerabilities Exposures) id was published for asterisk. CVE-2007-6430[0]: | Due to the way database-based registrations (realtime) | are processed, IP addresses are not checked when the | username is correct and there is no password. An | attacker may impersonate any user using host-based | authentication without a secret, simply by guessing the | username of that user. This is limited in scope to | administrators who have set up the registration database | (realtime) for authentication and are using only | host-based authentication, not passwords. However, both | the SIP and IAX protocols are affected. If you fix this vulnerability please also include the CVE id in your changelog entry. For further information: [0] http://downloads.digium.com/pub/security/AST-2007-027.html Kind regards Nico -- Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. pgp7vz1hkIhkH.pgp Description: PGP signature
Bug#457064: FTBFS: boost fails to build from source
Package: boost Severity: serious Justification: ftbfs from source Version: 1.34.1-2.1 Hello, Your package doesn't build from source in cowbuilder: --- cd tools/jam/src sh build.sh cc mv bin.*/bjam . ### ### Using 'cc' toolset. ### rm -rf bootstrap mkdir bootstrap gcc-4.1 -o bootstrap/jam0 command.c compile.c debug.c execunix.c expand.c fileunix.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c parse.c pathunix.c pathvms.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c native.c w32_getreg.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c execnt.c filent.c build.sh: line 15: gcc-4.1: command not found make: *** [/tmp/buildd/boost-1.34.1/tools/jam/src/bjam] Error 127 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 pbuilder: Failed autobuilding of package - Aborting with an error - unmounting dev/pts filesystem - unmounting proc filesystem - Copying COW directory - Invoking pbuilder - Cleaning COW directory --- Please fix this -- .''`. Patrick Winnertz [EMAIL PROTECTED] : :' : GNU/Linux Debian Developer `. `'` http://www.der-winnie.de http://d.skolelinux.org/~winnie `- Debian - when you have better things to do than fixing systems signature.asc Description: This is a digitally signed message part.
Bug#445959: icedove - FTBFS: error: 'asm' operand has impossible constraints
Hello. Any news regarding this? The last message from Bastian Blank dated 27 Oct 2007 contained a patch but nobody answered and the package hasn't been uploaded since then, it is still stuck on unstable. I am not demanding anything, just doing a ping :-). Thanks!!! -- Ivan Baldo - [EMAIL PROTECTED] - http://ibaldo.codigolibre.net/ ICQ 10215364 - Phone/FAX (598) (2) 613 3223. Caldas 1781, Malvin, Montevideo, Uruguay, South America. We believe that we are free, but in reality we are not! Are we? Alternatives: [EMAIL PROTECTED] - http://go.to/ibaldo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#456898: GSL linking issue with new '--as-needed' option to GNU ld [Was: Bug#456898: libgsl0ldbl: Uses symbols from libcblas.so, but not linked with it]
Dirk Eddelbuettel a écrit : On 19 December 2007 at 11:53, Brian Gough wrote: | At Tue, 18 Dec 2007 09:23:30 -0600, | Dirk Eddelbuettel wrote: | /usr/lib/libgsl.so: undefined reference to `cblas_zher2k' | /usr/lib/libgsl.so: undefined reference to `cblas_strsv' | /usr/lib/libgsl.so: undefined reference to `cblas_zdotc_sub' | [ many more of these ] | | Can you see a way forward on this? Is is maybe a question of link order, ie | could -lgslcblas -lgsl be an answer? | | The option -Wl,--as-needed needs to be disabled in some way, if it's | applied globally it's certainly not compatible with libraries that | depend on other libraries (surely a fairly common occurrence?). The | link order is not a factor. I think this case is pretty rare. If a library depends on on other libraries, it usually links with them. Given the very few packages that have a problem with this linker option, it seems to confirm that this is rare. | Maybe there is some official way to turn off that feature in qmake, or | to make it behave more intelligently with regard to external libraries | vs Qt libraries. Otherwise one could put the gsl library at the end | of the libraries list with -Wl,--no-as-needed: | | -Wl,--no-as-needed -lgsl -lgslcblas -lm Thanks for the follow-up -- I agree with your point. Now we need to see if Debian is set on --as-needed wand wants it globally. Which could be an issue as you politely point out... From my point of view using -Wl,--no-as-needed is only a workaround to the problem. I really think that libgsl should be linked with libgslcblas. -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457062: (no subject)
Hi, there is just another CVE id for exiftags: CVE-2007-6354[0]: | Unspecified vulnerability in exiftags before 1.01 has | unknown impact and attack vectors, resulting from a field | offset overflow, a different vulnerability than | CVE-2007-6355. Please check back with upstream for the difference to CVE-2007-6355. I had a quick look at the source changes and its not obvious what the difference should be. [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-6354 Kind regards Nico -- Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. pgpGl7H9OWP0O.pgp Description: PGP signature
Bug#456721: [Pkg-openmpi-maintainers] Processed: Re: Bug#456721:libpetsc.so depends on unexistent libraries
Hi, The patch looks good, it should fix all of the breakage. Just a couple of little points of clarification below. On Wed, 2007-12-19 at 06:58 -0600, Dirk Eddelbuettel wrote: On 19 December 2007 at 13:08, Manuel Prinz wrote: | Am Dienstag, den 18.12.2007, 21:23 -0600 schrieb Dirk Eddelbuettel: | On 19 December 2007 at 01:29, Manuel Prinz wrote: | | I'm not sure about that. I didn't see that on a quick read of chapters 8 | | and 10, though policy states in 10.2: | | Packages that use libtool to create shared libraries should | | include the .la files in the -dev package, unless the package | | relies on libtool's libltdl library, in which case the .la | | files must go in the run-time library package. | | That's not what I had I mind. I think there was a more general recommendation | of sticking .so files, headers files, static libraries, ... into the -dev | package. Anyway, I may well be wrong. | | You're right, chapter 8 is about that. It explains how the packaging has | to be done and that static libraries have to go into the -dev package. | But I can't find that one has to provide static libraries. I think the confusion is: the .la files are not the static libs, they are libtool metadata files. The -dev package needs to include the .a static libs. The .la files are completely optional, and there's some difference of opinion on whether or not they are beneficial. If upstream installs them, I'd put them in the -dev package. | Some comments and questions: [...] | | 2) I do not understand some of the file splits. Eg why |/usr/lib/libmca_common_sm.so.0 | Why does that need to be in /usr/lib/ and not hidden below like the other | mca* ones ? Ldd on the Rmpi library doesn't show it, maybe other MPI | usage does. Do you know a case where it is needed? | | The files was placed in /usr/lib before and not in /usr/lib/openmpi | where the private libs where, so I expected it to be essential. I | installed everything in the place where upstream installs them. (Leaving | the symlinking aside.) Ah, so upstream places it there? I always buy that argument :) Makes sense. There are some libs which are dynamically loaded by the program after it starts, like plugins etc., those do not need to be in /usr/lib. Those which the program links, and which are loaded right at runtime, need to be in /usr/lib. I don't know openmpi well enough to know which category these are in, but my code only noticed the absence of libmpi.so.0 and libmpi_f77.so.0 (presumably it would have noticed libmpi_cpp.so.0 if it had been C++). Either way, where upstream puts it is probably the right place for it. The only exception being libmpi.so which is an alternatives symlink and not a regular symlink in order to fit in with the other MPI implementations. | if we want to handle it via alternatives (which LAM doesn't) we have | check the situation in pgapack, so we don't get a problem there. What is | the advantage to have mpi.h in /usr/include? (Just curious.) Easy to find? Sure, though mpicc should include the -I required to find it anyway. It's up to you. I'd leave it in its own dir to avoid possible collisions. Thanks again for your work on the package! Cheers, -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457014: ocaml-nox: Bad permissions on ocamldoc-api-ref-config
On Wednesday 19 December 2007 03:11:35 am Stefano Zacchiroli wrote: On Wed, Dec 19, 2007 at 08:59:50AM +0100, Stefano Zacchiroli wrote: I just tried on my home box (amd64/sid), and cannot reproduce the error you describe on recompiling cryptgps. mmmh, this is strange, I really don't see how can it built find for you: the cdbs class now invokes /usr/share/cdbs/1/class/ocamldoc-api-ref-config and that file is not executable here: $ ls -l /usr/share/cdbs/1/class/ocamldoc-api-ref-config -rw-r--r-- 1 root root 2238 2007-12-17 13:41 /usr/share/cdbs/1/class/ocamldoc-api-ref-config Can you please check whether the above file is executable for you or not? I've committed on the svn repo what I think is a fix for this (see my previous post to this bugreport). Before uploading however, I'll wait for some info from Ralf, since given his test in which the FTBFS does not manifest itself I fear there is something more to be understood ... Cheers. My guess is that the file was executable on the original builder's machine, which appeared to be amd64 from the buildd page. Therefore, the amd64 packages have the file executable (as I can verify, as the package also builds fine for me using a vanilla pbuilder amd64 chroot). But since dpkg-source doesn't preserve permissions on new files created by the .diff.gz part of the source package, any binaries built by the buildd's (or built from source on amd64 as happened in my case) won't have it executable. If that's the cause, then the proper fix would be to insert a chmod +x .../ocamldoc-api-ref-config in debian/rules. -- Daniel Schepler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#456895: marked as done (glpi: depends on apache)
Your message dated Wed, 19 Dec 2007 14:17:03 + with message-id [EMAIL PROTECTED] and subject line Bug#456895: fixed in glpi 0.68.3.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: glpi Version: 0.68.3.2-1 Severity: serious Justification: Policy 11.5 The glpi package currently depends on apache2, with an alternative on all apache variants, but not on the virtual package httpd. Therefore, it isn’t possible to install it with another web server. -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée ---End Message--- ---BeginMessage--- Source: glpi Source-Version: 0.68.3.2-2 We believe that the bug you reported is fixed in the latest version of glpi, which is due to be installed in the Debian FTP archive: glpi_0.68.3.2-2.diff.gz to pool/main/g/glpi/glpi_0.68.3.2-2.diff.gz glpi_0.68.3.2-2.dsc to pool/main/g/glpi/glpi_0.68.3.2-2.dsc glpi_0.68.3.2-2_all.deb to pool/main/g/glpi/glpi_0.68.3.2-2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pierre Chifflier [EMAIL PROTECTED] (supplier of updated glpi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 19 Dec 2007 15:07:09 +0100 Source: glpi Binary: glpi Architecture: source all Version: 0.68.3.2-2 Distribution: unstable Urgency: low Maintainer: Pierre Chifflier [EMAIL PROTECTED] Changed-By: Pierre Chifflier [EMAIL PROTECTED] Description: glpi - IT and Asset management software Closes: 450976 456895 Changes: glpi (0.68.3.2-2) unstable; urgency=low . * Add alternate dependency on httpd (Closes: #456895) * Add Dutch debconf translation (Closes: #450976) * Bump standards version to 3.7.3 (no changes) * Update my email address Files: a413412a62b5161b9bd20d3456314378 558 web optional glpi_0.68.3.2-2.dsc 5d3cace3fe5148bf0c9e9aa606a4e050 9980 web optional glpi_0.68.3.2-2.diff.gz c9d066d62d2d038e138c8dfdcfe81f66 1375496 web optional glpi_0.68.3.2-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHaSW3twVrWo1fQMsRAqtDAKCV6yKcnrEzJQA2qBs9DAh3EdIjeQCgpa/S ufNzhlinDgvvwcx4JwMvTxg= =QJNM -END PGP SIGNATURE- ---End Message---
Bug#456825: marked as done (libvirt: FTBFS: dpkg-shlibdeps: failure: couldn't find library libvirt.so.0 needed by debian/libvirt-doc/usr/share/doc/libvirt-doc/examples/.libs/info1 (its RPATH is '').)
Your message dated Wed, 19 Dec 2007 15:17:03 + with message-id [EMAIL PROTECTED] and subject line Bug#456825: fixed in libvirt 0.3.3-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: libvirt version: 0.3.3-5 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20071217 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. Relevant part: dh_installchangelogs -plibvirt-doc ./ChangeLog dh_installudev -plibvirt-doc dh_install -plibvirt-doc --sourcedir=debian/tmp dh_link -plibvirt-doc dh_pycentral -plibvirt-doc pycentral: pycentral debhelper: missing XB-Python-Version attribute in package libvirt-doc dh_python -plibvirt-doc dh_python: Doing nothing since dh_pycompat exists; dh_pysupport or dh_pycentral should do the work. You can remove dh_python from your rules file. dh_strip -plibvirt-doc dh_compress -plibvirt-doc dh_fixperms -plibvirt-doc dh_makeshlibs -plibvirt-doc dh_installdeb -plibvirt-doc dh_perl -plibvirt-doc dh_shlibdeps -plibvirt-doc dpkg-shlibdeps: failure: couldn't find library libvirt.so.0 needed by debian/libvirt-doc/usr/share/doc/libvirt-doc/examples/.libs/info1 (its RPATH is ''). Note: libraries are not searched in other binary packages that do not have any shlibs file. To help dpkg-shlibdeps find private libraries, you might need to set LD_LIBRARY_PATH. dh_shlibdeps: command returned error code 512 make: *** [binary-predeb-IMPL/libvirt-doc] Error 1 dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules binary gave error exit status 2 The full build log is available from: http://people.debian.org/~lucas/logs/2007/12/17 A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: libvirt Source-Version: 0.3.3-6 We believe that the bug you reported is fixed in the latest version of libvirt, which is due to be installed in the Debian FTP archive: libvirt-bin_0.3.3-6_powerpc.deb to pool/main/libv/libvirt/libvirt-bin_0.3.3-6_powerpc.deb libvirt-dev_0.3.3-6_powerpc.deb to pool/main/libv/libvirt/libvirt-dev_0.3.3-6_powerpc.deb libvirt-doc_0.3.3-6_all.deb to pool/main/libv/libvirt/libvirt-doc_0.3.3-6_all.deb libvirt0_0.3.3-6_powerpc.deb to pool/main/libv/libvirt/libvirt0_0.3.3-6_powerpc.deb libvirt_0.3.3-6.diff.gz to pool/main/libv/libvirt/libvirt_0.3.3-6.diff.gz libvirt_0.3.3-6.dsc to pool/main/libv/libvirt/libvirt_0.3.3-6.dsc python-libvirt_0.3.3-6_powerpc.deb to pool/main/libv/libvirt/python-libvirt_0.3.3-6_powerpc.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. Guido Guenther [EMAIL PROTECTED] (supplier of updated libvirt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 19 Dec 2007 13:45:58 +0100 Source: libvirt Binary: python-libvirt libvirt-dev libvirt-doc libvirt0 libvirt-bin Architecture: source powerpc all Version: 0.3.3-6 Distribution: unstable Urgency: low Maintainer: Debian Libvirt Maintainers [EMAIL PROTECTED] Changed-By: Guido Guenther [EMAIL PROTECTED] Description: libvirt-bin - the programs for the libvirt library libvirt-dev - development files for the libvirt library libvirt-doc - documentation for the libvirt library libvirt0 - library for interfacing with Xen other virtualization systems python-libvirt - libvirt python bindings Closes: 455859 456825 Changes: libvirt (0.3.3-6) unstable; urgency=low . * don't include precompiled examples in the doc package (Closes: #456825) * remove RHism from manpage (Closes: #455859) * bump
Bug#451268: wrong direntries from makeinfo 4.11
Hi Karl, you remember http://lists.gnu.org/archive/html/bug-texinfo/2007-10/msg00020.html where the This is foobar, produced by ... ended up in the START-INFO-DIR-ENTRY? With 4.11 PLUS your patch from the above it is still happening, minimal not working texi file I could generate: \input texinfo @setfilename untitled.info @direntry * : (). aaa . @end direntry @bye generates output: START-INFO-DIR-ENTRY This is foo.info, produced by makeinfo version 4.11 from foo.texi. * : (). aaa . END-INFO-DIR-ENTRY Which is bad. The problem is that your fix is only done in cmds.c, but not for cm_direntry (in the begin_insertion function) in insertion.c. Could you comment on the following fix I tried. It does in fact generate the right dir entry code in the output file, but may have other consequences I do not forsee. Here is that diff: --- texinfo-4.11.dfsg.1.orig/makeinfo/insertion.c 2007-12-19 16:19:35.0 +0100 +++ texinfo-4.11.dfsg.1/makeinfo/insertion.c2007-12-19 16:19:41.0 +0100 @@ -488,7 +488,7 @@ close_single_paragraph (); filling_enabled = no_indent = 0; inhibit_paragraph_indentation = 1; - insert_string (START-INFO-DIR-ENTRY\n); + add_word (START-INFO-DIR-ENTRY\n); break; case documentdescription: Thanks a lot Norbert --- Dr. Norbert Preining [EMAIL PROTECTED]Vienna University of Technology Debian Developer [EMAIL PROTECTED] Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- LUBCROY (n.) The telltale little lump in the top of your swimming trunks which tells you you are going to have to spend half an hour with a safety pin trying to pull the drawstring out again. --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#450452: marked as done (does install a dangling symlink as clisp-link - ../lib/clisp-*/clisp-link)
Your message dated Wed, 19 Dec 2007 16:02:07 + with message-id [EMAIL PROTECTED] and subject line Bug#450452: fixed in clisp 1:2.43-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: xindy version: 2.2~beta2-3 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20071106 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. Relevant part: make[2]: Entering directory `/build/user/xindy-2.2~beta2/rte/ordrules' clisp -q -norc -c ordrulei.lsp ;; Compiling file /build/user/xindy-2.2~beta2/rte/ordrules/ordrulei.lsp ... ;; Wrote file /build/user/xindy-2.2~beta2/rte/ordrules/ordrulei.fas ;; Wrote file /build/user/xindy-2.2~beta2/rte/ordrules/ordrulei.c 0 errors, 0 warnings make[2]: Leaving directory `/build/user/xindy-2.2~beta2/rte/ordrules' clisp-link add-module-set ordrules /usr/lib/clisp/full tmp make[1]: clisp-link: Command not found make[1]: *** [tmp] Error 127 make[1]: Leaving directory `/build/user/xindy-2.2~beta2/rte' make: *** [build-arch-stamp] Error 1 dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules binary gave error exit status 2 The full build log is available from http://people.debian.org/~lucas/logs/2007/11/06 A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: clisp Source-Version: 1:2.43-1 We believe that the bug you reported is fixed in the latest version of clisp, which is due to be installed in the Debian FTP archive: clisp-dev_2.43-1_amd64.deb to pool/main/c/clisp/clisp-dev_2.43-1_amd64.deb clisp-doc_2.43-1_all.deb to pool/main/c/clisp/clisp-doc_2.43-1_all.deb clisp_2.43-1.diff.gz to pool/main/c/clisp/clisp_2.43-1.diff.gz clisp_2.43-1.dsc to pool/main/c/clisp/clisp_2.43-1.dsc clisp_2.43-1_amd64.deb to pool/main/c/clisp/clisp_2.43-1_amd64.deb clisp_2.43.orig.tar.gz to pool/main/c/clisp/clisp_2.43.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. Peter Van Eynde [EMAIL PROTECTED] (supplier of updated clisp 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, 13 Dec 2007 05:31:23 +0100 Source: clisp Binary: clisp-dev clisp clisp-doc Architecture: source all amd64 Version: 1:2.43-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: clisp - GNU CLISP, a Common Lisp implementation clisp-dev - GNU CLISP, a Common Lisp implementation (development files) clisp-doc - GNU CLISP, a Common Lisp implementation (documentation) Closes: 443804 448431 450452 Changes: clisp (1:2.43-1) unstable; urgency=low . * New upstream release. * removed the lisp-* hack, use real version in all scripts (Closes: #450452) * Use default gcc again * Fixed dpkg warnings about unable to delete old directory `/usr/lib/clisp (Closes: #448431) * Added support for module berkeley-db (Closes: #443804) Files: 2e91452958cd350e2dad4ed4b1e6a0b3 828 interpreters optional clisp_2.43-1.dsc 4f58d0d23dae2e37824cbe49204a9356 10441100 interpreters optional clisp_2.43.orig.tar.gz 9a92b96adb67f9fb08ecdf3c9b57eb6e 16914 interpreters optional clisp_2.43-1.diff.gz 95b6309748469ab4e021653188c99ab2 478612 doc optional clisp-doc_2.43-1_all.deb 2c89be69129f2936be256b448f5d3821 4505052 interpreters optional clisp_2.43-1_amd64.deb ad365a69d89b011adedbe5762e06 3878946 devel optional clisp-dev_2.43-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHYf+n11ldN0tyliURApX6AKCNIRDjhj2N+FPsZZYxsoz8fzpEdQCghCoj SWRxU6PcUH+3ZGkCDaieEeg=
Bug#454212: megahal: Confirmed in etch
Hello, * Neil McGovern [Wed, Dec 19, 2007 at 11:42:23AM +]: Confirmed using etch i386 (though an amd64 processor). Attached output of megahal and strace. Thanks for reproducing this bug. Unfortunately the backtrack doesn't give much information. I'll try to figure out what's going on from the source, and perhaps provide a debian package with debugging enabled. Laurent. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Patch for dpkg-shlibdeps failure
Processing commands for [EMAIL PROTECTED]: tag 453798 patch Bug#453798: xdb: FTBFS: dpkg-shlibdeps: failure: couldn't find library libxdb.so.1 needed by debian/libxdb-dev/usr/bin/deletall (its RPATH is ''). There were no tags set. Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 456350 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.11 severity 456350 important Bug#456350: python-visual: FTBFS: New or changed copyright notices discovered! Severity set to `important' from `serious' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#453798: Patch for dpkg-shlibdeps failure
tag 453798 patch thanks --- xdb-1.2.0~/debian/rules +++ xdb-1.2.0/debian/rules @@ -70,7 +70,7 @@ dh_md5sums -plibxdb1 dh_builddeb -plibxdb1 -libxdb-dev: build +libxdb-dev: build libxdb1 dh_testdir -plibxdb-dev dh_testroot -plibxdb-dev dh_clean -v -plibxdb-dev -k @@ -109,7 +109,7 @@ dh_compress -plibxdb-dev dh_fixperms -plibxdb-dev dh_installdeb -plibxdb-dev - dh_shlibdeps -plibxdb-dev + dh_shlibdeps -plibxdb-dev -Llibxdb1 -ldebian/tmp/usr/lib dh_gencontrol -plibxdb-dev dh_makeshlibs -plibxdb-dev -V dh_md5sums -plibxdb-dev Cheers, Matej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#456992: smbfs: mount.cifs fails with mount error: could not find target server. TCP name ... not found
On Wed, Dec 19, 2007 at 01:23:30AM -0800, Steve Langasek wrote: On Wed, Dec 19, 2007 at 07:47:34AM +, Julian Gilbey wrote: I have just upgraded from 3.0.27a-1 to this version, and now when I try to mount my Samba partition, I get the following error: euclid:~ # mount -t cifs //WGS-SVR-001/RMStaff /mnt/wggs/rmstaff -o credentials=/etc/wggs.credentials,uid=jdg,gid=jdg mount error: could not find target server. TCP name WGS-SVR-001/RMStaff not found No ip address specified and hostname not found euclid:~ # Is this hostname resolvable via DNS (i.e., how about ping WGS-SVR-001 instead of smbclient as a test)? The mount.cifs program doesn't support WINS-based host resolution (nor mount.smbfs, IIRC). C.f. bug #311709. euclid:~ $ host WGS-SVR-001 WGS-SVR-001.local does not exist (Authoritative answer) euclid:~ $ I'll check and let you know. But something has clearly changed between version 3.0.27a-1 and this version, as it did work until now. And if it is a DNS issue, then how on earth am I meant to specify the partition to mount.cifs?! Well, are you sure that something in your DNS didn't change since the point when you were using 3.0.27a? I really don't know of any other way this would've worked for you with the given commandline. I've reinstalled 3.0.27a-1, and my /etc/fstab entry works (line broken for readability): //WGS-SVR-002/Shared\040Documents /mnt/wggs/shared smbfs user,noauto,credentials=/etc/wggs.credentials,uid=jdg,gid=jdg 0 0 but you are correct: the command line with -t cifs does not work. However, with 3.0.27a, the command line: mount -t smbfs //WGS-SVR-001/RMStaff /mnt/wggs/rmstaff -o \ credentials=/etc/wggs.credentials,uid=jdg,gid=jdg does work, whereas with 3.0.28-1~lenny1, this same command line gives the TCP name not found error. So clearly *something* has changed. To mount such shares without DNS support, you have three options: - add your own entry in /etc/hosts - add nss_wins from the winbind package to your nsswitch.conf - use the ip= option to mount.cifs Many thanks! Julian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#454158: tomboy: Mono.Addins assembly could not be loaded
Tomboy is still broken on my Sid AMD64 machine. Steps I've done so far: 1) dpkg-reconfigure libmono-addins0.2-cil libmono-addins-gui0.2-cil tomboy 2) rm -r ~/.tomboy 3) run tomboy Tomboy says: $ tomboy ... ** (Tomboy:13758): WARNING **: The following assembly referenced from /usr/lib/tomboy/Tomboy.exe could not be loaded: Assembly: Mono.Addins(assemblyref_index=7) Version:0.2.0.0 Public Key: 0738eb9f132ed756 The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/usr/lib/tomboy). ... Packages versions: $ dpkg -l | grep addins ii libmono-addins-gui0.2-cil 0.3~svn.r90520-1 GTK# frontend library ii libmono-addins0.2-cil 0.3~svn.r90520-1 addin framework fir $ dpkg -l | grep tomboy ii tomboy 0.8.2-1desktop note taking Vit -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#454158: [pkg-mono-group] Bug#454158: tomboy: Mono.Addins assembly could not be loaded
On Wed, 2007-12-19 at 17:55 +0100, Vitezslav Kotrla wrote: Tomboy is still broken on my Sid AMD64 machine. Steps I've done so far: 1) dpkg-reconfigure libmono-addins0.2-cil libmono-addins-gui0.2-cil tomboy 2) rm -r ~/.tomboy 3) run tomboy Is the cli-common version 0.5.1 or higher? If not, ugprade cli-common and dpkg-reconfigure both mono-addins packages again. -- Regards, Mirco 'meebey' Bauer PGP-Key ID: 0xEEF946C8 FOSS Developer[EMAIL PROTECTED] http://www.meebey.net/ PEAR Developer[EMAIL PROTECTED] http://pear.php.net/ Debian Developer [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457088: mpi.h is missing
Package: libopenmpi-dev Version: 1.2.4-5 Severity: serious --- Please enter the report below this line. --- Hi, the mpi.h is missing. I found it in /usr/lib/openmpi/include/ please add at least a symlink or something to /usr/include the is breaks the python-petsc4py package for example: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456869 It used to work before. I could fix it by patching the build scripts to include /usr/lib/openmpi/include/, but the right solution imho is to fix libopenmpi-dev. Thanks, Ondrej --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-2-686 Debian Release: lenny/sid 500 unstableftp.cz.debian.org 500 unstabledebian.certik.cz --- Package information. --- Depends (Version) | Installed ==-+- libopenmpi1(= 1.2.4-5) | 1.2.4-5 openmpi-common (= 1.2.4-5) | 1.2.4-5 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#432665: marked as done (wxmaxima: Not connected to maxima!)
Your message dated Wed, 19 Dec 2007 19:01:21 +0100 with message-id [EMAIL PROTECTED] and subject line wxmaxima bug fixed in 0.7.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--- Subject: wxmaxima: Not connected to maxima! Package: wxmaxima Version: 0.7.0a-1 Severity: grave Justification: renders package unusable If I launch wxmaxima I have this message Not connected to maxima!. I tried a solution to change in the file /home/arnaud/.wxMaxima the line maxima=1 with maxima=/usr/bin/maxima or maxima=/usr/bin/maxima I read this on a reportbug for wxmaxima 0.7.1, but it does not work here. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Versions of packages wxmaxima depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libgcc11:4.1.1-21GCC support library ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libwxbase2.6-0 2.6.3.2.1.5 wxBase library (runtime) - non-GUI ii libwxgtk2.6-0 2.6.3.2.1.5 wxWidgets Cross-platform C++ GUI t ii libxml22.6.27.dfsg-1 GNOME XML library ii maxima 5.10.0-6 A computer algebra system -- base ii maxima-doc 5.10.0-6 A computer algebra system -- docum wxmaxima recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Package: wxmaxima Version: 0.7.1-1 The bug was fixed by wxMaxima developpers on 2006-10-10, bug #1573741 in wxMaxima bugs. It was a '' missing in front of a variable in the C++ code, and it is no longer present since version 0.7.1, which is the one in unstable. Almacha ---End Message---
Bug#457089: gdmkeyword 'auto' deprecated
Package: gdm Version: 2.20.2-1 Severity: grave Justification: renders package unusable When trying to start gdm, it errors saying gdmkeyword 'auto' deprecated and errors out. It does not write to /var/log/gdm nor to ~/.xsession-errors. I cannot find anywhere that the gdmkeyword is located. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.23.11-slh-smp-1 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gdm depends on: ii adduser 3.105add and remove users and groups ii debconf [debconf-2.0] 1.5.17 Debian configuration management sy ii fluxbox [x-window-manag 1.0.0+deb1-4 Highly configurable and low resour ii gksu2.0.0-5 graphical frontend to su ii gnome-session 2.20.2-1 The GNOME 2 Session Manager ii gnome-terminal [x-termi 2.18.3-1 The GNOME 2 terminal emulator appl ii konsole [x-terminal-emu 4:3.5.8.dfsg.1-2 X terminal emulator for KDE ii kwin [x-window-manager] 4:3.5.8.dfsg.1-2 the KDE window manager ii libart-2.0-22.3.19-3 Library of functions for 2D graphi ii libatk1.0-0 1.20.0-1 The ATK accessibility toolkit ii libattr11:2.4.39-1 Extended attribute shared library ii libc6 2.7-4GNU C Library: Shared libraries ii libcairo2 1.4.12-1 The Cairo 2D vector graphics libra ii libdbus-1-3 1.1.2-1 simple interprocess messaging syst ii libdbus-glib-1-20.74-1 simple interprocess messaging syst ii libdmx1 1:1.0.2-2X11 Distributed Multihead extensio ii libfontconfig1 2.5.0-2 generic font configuration library ii libglade2-0 1:2.6.2-1library to load .glade files at ru ii libglib2.0-02.14.4-2 The GLib library of C routines ii libgnomecanvas2-0 2.20.1.1-1 A powerful object-oriented display ii libgtk2.0-0 2.12.3-2 The GTK+ graphical user interface ii libpam-modules 0.99.7.1-5 Pluggable Authentication Modules f ii libpam-runtime 0.99.7.1-5 Runtime support for the PAM librar ii libpam0g0.99.7.1-5 Pluggable Authentication Modules l ii libpango1.0-0 1.18.3-1 Layout and rendering of internatio ii librsvg2-2 2.18.2-1 SAX-based renderer library for SVG ii librsvg2-common 2.18.2-1 SAX-based renderer library for SVG ii libselinux1 2.0.15-2+b1 SELinux shared libraries ii libwrap07.6.dbs-14 Wietse Venema's TCP wrappers libra ii libx11-62:1.0.3-7X11 client-side library ii libxau6 1:1.0.3-2X11 authorisation library ii libxdmcp6 1:1.0.2-2X11 Display Manager Control Protoc ii libxext61:1.0.3-2X11 miscellaneous extension librar ii libxi6 2:1.1.3-1X11 Input extension library ii libxinerama11:1.0.2-1X11 Xinerama extension library ii libxml2 2.6.30.dfsg-3GNOME XML library ii lsb-base3.1-24 Linux Standard Base 3.1 init scrip ii metacity [x-window-mana 1:2.20.1-1 A lightweight GTK2 based Window Ma ii xbase-clients 1:7.3+8 miscellaneous X clients - metapack ii xterm [x-terminal-emula 229-1X terminal emulator Versions of packages gdm recommends: ii dialog 1.1-20071028-1Displays user-friendly dialog boxe ii gdm-themes 0.5.1 Themes for the GNOME Display Manag ii whiptail 0.52.2-11.1 Displays user-friendly dialog boxe ii xnest 2:1.4.1~git20071212-1 Nested X server ii xserver-xorg 1:7.3+8 the X.Org X server ii zenity 2.20.1-1 Display graphical dialog boxes fro -- debconf information: gdm/daemon_name: /usr/bin/gdm * shared/default-x-display-manager: gdm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457088: marked as done (mpi.h is missing)
Your message dated Wed, 19 Dec 2007 12:15:48 -0600 with message-id [EMAIL PROTECTED] and subject line [Pkg-openmpi-maintainers] Bug#457088: mpi.h is missing 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: libopenmpi-dev Version: 1.2.4-5 Severity: serious --- Please enter the report below this line. --- Hi, the mpi.h is missing. I found it in /usr/lib/openmpi/include/ please add at least a symlink or something to /usr/include the is breaks the python-petsc4py package for example: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456869 It used to work before. I could fix it by patching the build scripts to include /usr/lib/openmpi/include/, but the right solution imho is to fix libopenmpi-dev. Thanks, Ondrej --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-2-686 Debian Release: lenny/sid 500 unstableftp.cz.debian.org 500 unstabledebian.certik.cz --- Package information. --- Depends (Version) | Installed ==-+- libopenmpi1(= 1.2.4-5) | 1.2.4-5 openmpi-common (= 1.2.4-5) | 1.2.4-5 ---End Message--- ---BeginMessage--- On Wed, Dec 19, 2007 at 06:49:15PM +0100, Ondrej Certik wrote: Package: libopenmpi-dev Version: 1.2.4-5 Severity: serious --- Please enter the report below this line. --- Hi, the mpi.h is missing. I found it in /usr/lib/openmpi/include/ please add at least a symlink or something to /usr/include the is breaks the python-petsc4py package for example: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456869 It used to work before. I could fix it by patching the build scripts to include /usr/lib/openmpi/include/, but the right solution imho is to fix libopenmpi-dev. Nope, as we as package maintainers simply changed the location. Study the configure options you have in your client (source) code. For what it's worth, I just made the same change in Rmpi (being its maintainer). mpi.h not being in /usr/include is not a bug. and certainly not a serious bug. Please show some more restraint. You can always ask us off-line, as you have seen in the last few days we tend to respond quickly. Dirk Thanks, Ondrej --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-2-686 Debian Release: lenny/sid 500 unstableftp.cz.debian.org 500 unstabledebian.certik.cz --- Package information. --- Depends (Version) | Installed ==-+- libopenmpi1(= 1.2.4-5) | 1.2.4-5 openmpi-common (= 1.2.4-5) | 1.2.4-5 ___ Pkg-openmpi-maintainers mailing list [EMAIL PROTECTED] http://lists.alioth.debian.org/mailman/listinfo/pkg-openmpi-maintainers -- Three out of two people have difficulties with fractions. ---End Message---
Bug#455487: marked as done (dia: please remove libunicode-dev from your build-deps)
Your message dated Wed, 19 Dec 2007 18:32:04 + with message-id [EMAIL PROTECTED] and subject line Bug#455487: fixed in dia 0.96.1-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: dia Version: 0.96.1-5 Severity: serious Hi, We are trying to remove libunicode from Debian. dia still build-depends on it, but doesn't link with it, so it's probably not needed. Could you please remove it from your build-deps? Marking this as serious since dia will FTBFS when we will have removed libunicode. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: dia Source-Version: 0.96.1-6 We believe that the bug you reported is fixed in the latest version of dia, which is due to be installed in the Debian FTP archive: dia-common_0.96.1-6_all.deb to pool/main/d/dia/dia-common_0.96.1-6_all.deb dia-gnome_0.96.1-6_i386.deb to pool/main/d/dia/dia-gnome_0.96.1-6_i386.deb dia-libs_0.96.1-6_i386.deb to pool/main/d/dia/dia-libs_0.96.1-6_i386.deb dia_0.96.1-6.diff.gz to pool/main/d/dia/dia_0.96.1-6.diff.gz dia_0.96.1-6.dsc to pool/main/d/dia/dia_0.96.1-6.dsc dia_0.96.1-6_i386.deb to pool/main/d/dia/dia_0.96.1-6_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. Roland Stigge [EMAIL PROTECTED] (supplier of updated dia package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 19 Dec 2007 12:25:39 +0100 Source: dia Binary: dia-libs dia-common dia-gnome dia Architecture: source i386 all Version: 0.96.1-6 Distribution: unstable Urgency: low Maintainer: Debian Dia Team [EMAIL PROTECTED] Changed-By: Roland Stigge [EMAIL PROTECTED] Description: dia- Diagram editor dia-common - Diagram editor (common files) dia-gnome - Diagram editor (GNOME version) dia-libs - Diagram editor (library files) Closes: 449646 455487 Changes: dia (0.96.1-6) unstable; urgency=low . * debian/control: - Removed libunicode-dev from Build-Depends (Closes: #455487) - Standards-Version: 3.7.2 - 3.7.3 - Removed dpatch from Build-Depends - Added Homepage field * debian/watch: New contents for version=3 file (Closes: #449646) Files: 384c41ee63fe3d6dd7415c3065911eb0 968 graphics optional dia_0.96.1-6.dsc f3fe96aef55cc22e44d0106ee3e5e22f 98838 graphics optional dia_0.96.1-6.diff.gz 12f3fc5aca37d61fe8beaf693d06d262 4115182 graphics optional dia-common_0.96.1-6_all.deb 55b64e956e3ad9a78d13a6fac078a45a 702842 graphics optional dia-libs_0.96.1-6_i386.deb cbf3b3446cda10361989e5c9a2176e02 190654 graphics optional dia_0.96.1-6_i386.deb 1c7ebc23ad05319cf43d92281a158095 191596 gnome optional dia-gnome_0.96.1-6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHaW3ccaH/YBv43g8RAjXAAJ4s0BSr45Uosm7S475frGkjlILnRQCgx396 94RJ2rfsGvcr7Lf56skw2Vs= =ZOYm -END PGP SIGNATURE- ---End Message---
Bug#457088: [Pkg-openmpi-maintainers] Bug#457088: mpi.h is missing
On Dec 19, 2007 7:15 PM, Dirk Eddelbuettel [EMAIL PROTECTED] wrote: On Wed, Dec 19, 2007 at 06:49:15PM +0100, Ondrej Certik wrote: Package: libopenmpi-dev Version: 1.2.4-5 Severity: serious --- Please enter the report below this line. --- Hi, the mpi.h is missing. I found it in /usr/lib/openmpi/include/ please add at least a symlink or something to /usr/include the is breaks the python-petsc4py package for example: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456869 It used to work before. I could fix it by patching the build scripts to include /usr/lib/openmpi/include/, but the right solution imho is to fix libopenmpi-dev. Nope, as we as package maintainers simply changed the location. Study the configure options you have in your client (source) code. For what it's worth, I just made the same change in Rmpi (being its maintainer). mpi.h not being in /usr/include is not a bug. and certainly not a serious bug. Please show some more restraint. You can always ask us off-line, as you have seen in the last few days we tend to respond quickly. I am sorry I put the severity wrong. But you, as the maintainer can adjust it as you see fit. As to the real problem - I just asked about exactly this on debian-python: http://lists.debian.org/debian-python/2007/12/msg00030.html and I think include files belong to /usr/include, accordig to the FHS: http://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html#USRINCLUDEDIRECTORYFORSTANDARDINCLU So it's imho a bug and should be reopened. (I know how to fix petsc4py, I just tried and confirmed it works, but I think it's a bug that should be fixed in openmpi, not petsc4py). Why do you think the header files shouldn't be in /usr/include? Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457063: asterisk: CVE-2007-6430 remote unauthenticated sessions
Nico Golde wrote: CVE-2007-6430[0]: | Due to the way database-based registrations (realtime) | are processed, IP addresses are not checked when the | username is correct and there is no password. An | attacker may impersonate any user using host-based | authentication without a secret, simply by guessing the | username of that user. This is limited in scope to | administrators who have set up the registration database | (realtime) for authentication and are using only | host-based authentication, not passwords. However, both | the SIP and IAX protocols are affected. This is affecting unstable and stable. oldstable is not affected. I'll upload 1.4.16 (.1 due soon probably, since .16 has a major bug) to unstable probably tomorrow or the day after that. For stable, I don't think that the vulnerability is serious enough to warrant a DSA. Maybe s-p-u is a better candidate? Regards, Faidon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457088: [Pkg-openmpi-maintainers] Bug#457088: mpi.h is missing
On Wed, Dec 19, 2007 at 07:40:13PM +0100, Ondrej Certik wrote: On Dec 19, 2007 7:15 PM, Dirk Eddelbuettel [EMAIL PROTECTED] wrote: On Wed, Dec 19, 2007 at 06:49:15PM +0100, Ondrej Certik wrote: Package: libopenmpi-dev Version: 1.2.4-5 Severity: serious --- Please enter the report below this line. --- Hi, the mpi.h is missing. I found it in /usr/lib/openmpi/include/ please add at least a symlink or something to /usr/include the is breaks the python-petsc4py package for example: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456869 It used to work before. I could fix it by patching the build scripts to include /usr/lib/openmpi/include/, but the right solution imho is to fix libopenmpi-dev. Nope, as we as package maintainers simply changed the location. Study the configure options you have in your client (source) code. For what it's worth, I just made the same change in Rmpi (being its maintainer). mpi.h not being in /usr/include is not a bug. and certainly not a serious bug. Please show some more restraint. You can always ask us off-line, as you have seen in the last few days we tend to respond quickly. I am sorry I put the severity wrong. But you, as the maintainer can adjust it as you see fit. As to the real problem - I just asked about exactly this on debian-python: http://lists.debian.org/debian-python/2007/12/msg00030.html and I think include files belong to /usr/include, accordig to the FHS: http://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html#USRINCLUDEDIRECTORYFORSTANDARDINCLU So it's imho a bug and should be reopened. (I know how to fix petsc4py, I just tried and confirmed it works, but I think it's a bug that should be fixed in openmpi, not petsc4py). Why do you think the header files shouldn't be in /usr/include? As you may know, we are trying to let Open MPI coexist with MPICH and LAM. /usr/include is fine for _non-conflicting_ files as good as a general rule, but not so clear if several packages provide it. By 'staying out of each others way' it is easier to build against several MPI implementations. So no bug here. Thanks, Dirk -- Three out of two people have difficulties with fractions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457014: ocaml-nox: Bad permissions on ocamldoc-api-ref-config
Hi, On Wed, Dec 19, 2007 at 09:11:35AM +0100, Stefano Zacchiroli wrote: On Wed, Dec 19, 2007 at 08:59:50AM +0100, Stefano Zacchiroli wrote: I just tried on my home box (amd64/sid), and cannot reproduce the error you describe on recompiling cryptgps. mmmh, this is strange, I really don't see how can it built find for you: the cdbs class now invokes /usr/share/cdbs/1/class/ocamldoc-api-ref-config and that file is not executable here: $ ls -l /usr/share/cdbs/1/class/ocamldoc-api-ref-config -rw-r--r-- 1 root root 2238 2007-12-17 13:41 /usr/share/cdbs/1/class/ocamldoc-api-ref-config Can you please check whether the above file is executable for you or not? It is indeed executable on my machine : % ls -l /usr/share/cdbs/1/class/ocamldoc-api-ref-config -rwxr-xr-x 1 root root 2238 2007-11-10 17:27 /usr/share/cdbs/1/class/ocamldoc-api-ref-config This is ocaml-nox 3.10.0-9 on amd64. Daniel Schepler [EMAIL PROTECTED] wrote: My guess is that the file was executable on the original builder's machine, which appeared to be amd64 from the buildd page. Therefore, the amd64 packages have the file executable (as I can verify, as the package also builds fine for me using a vanilla pbuilder amd64 chroot). But since dpkg-source doesn't preserve permissions on new files created by the .diff.gz part of the source package, any binaries built by the buildd's (or built from source on amd64 as happened in my case) won't have it executable. If I undestand right this could only happen when the file in question is part of the tarball, but this doesn't seem to be the case : % ar x ocaml-nox_3.09.2-9_amd64.deb % tar tvfz data.tar.gz | grep ocamldoc-api-ref-config no output lines -Ralf. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457014: ocaml-nox: Bad permissions on ocamldoc-api-ref-config
On Wed, Dec 19, 2007 at 20:24:47 +0100, Ralf Treinen wrote: Hi, On Wed, Dec 19, 2007 at 09:11:35AM +0100, Stefano Zacchiroli wrote: On Wed, Dec 19, 2007 at 08:59:50AM +0100, Stefano Zacchiroli wrote: I just tried on my home box (amd64/sid), and cannot reproduce the error you describe on recompiling cryptgps. mmmh, this is strange, I really don't see how can it built find for you: the cdbs class now invokes /usr/share/cdbs/1/class/ocamldoc-api-ref-config and that file is not executable here: $ ls -l /usr/share/cdbs/1/class/ocamldoc-api-ref-config -rw-r--r-- 1 root root 2238 2007-12-17 13:41 /usr/share/cdbs/1/class/ocamldoc-api-ref-config Can you please check whether the above file is executable for you or not? It is indeed executable on my machine : % ls -l /usr/share/cdbs/1/class/ocamldoc-api-ref-config -rwxr-xr-x 1 root root 2238 2007-11-10 17:27 /usr/share/cdbs/1/class/ocamldoc-api-ref-config This is ocaml-nox 3.10.0-9 on amd64. The amd64 package in the archive is fine. On all other architectures, that file has mode 0644. Daniel Schepler [EMAIL PROTECTED] wrote: My guess is that the file was executable on the original builder's machine, which appeared to be amd64 from the buildd page. Therefore, the amd64 packages have the file executable (as I can verify, as the package also builds fine for me using a vanilla pbuilder amd64 chroot). But since dpkg-source doesn't preserve permissions on new files created by the .diff.gz part of the source package, any binaries built by the buildd's (or built from source on amd64 as happened in my case) won't have it executable. If I undestand right this could only happen when the file in question is part of the tarball, but this doesn't seem to be the case : % ar x ocaml-nox_3.09.2-9_amd64.deb % tar tvfz data.tar.gz | grep ocamldoc-api-ref-config no output lines This is about the source package. The amd64 deb was built from an svn checkout, where this file was +x. On other architectures, it was built from the unpacked source package. Since this file isn't in the orig tarball, it's created from the diff.gz, and so isn't executable. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457097: ejabberd dont start
Package: ejabberd
Version: 1.1.2-6
Severity: grave
Justification: renders package unusable
hi, i start the ejabberd service and seems to die
scarlet:~# /etc/init.d/ejabberd start
Starting jabber server: ejabberd.
scarlet:~# ejabberdctl
RPC failed on the node [EMAIL PROTECTED]: {'EXIT',
{badarg,
[{ets,
lookup,
[hooks,
{ejabberd_ctl_process,
global}]},
{ejabberd_hooks,
run_fold,
4},
{ejabberd_ctl,process,1},
{rpc,
'-handle_call/3-fun-0-',
5}]}}
scarlet:~#
how to i can increase more log level for debug and get more info?
i have a empty /var/log/ejabberd/
i try to manual start:
scarlet:~# su - ejabberd -c /usr/sbin/ejabberd -noshell -s
{error_logger,{{2007,12,19},{16,25,25}},Protocol: ~p: register error:
~p~n,[i
net_tcp,{{badmatch,{error,duplicate_name}},[{inet_tcp_dist,listen,1},{net_kerne
l,start_protos,4},{net_kernel,start_protos,3},{net_kernel,init_node,2},{net_kern
el,init,1},{gen_server,init_it,6},{proc_lib,init_p,5}]}]}
{error_logger,{{2007,12,19},{16,25,25}},crash_report,[[{pid,0.20.0},{registere
d_name,net_kernel},{error_info,{error,badarg}},{initial_call,{gen,init_it,[gen_s
erver,0.17.0,0.17.0,{local,net_kernel},net_kernel,{ejabberd,shortnames,15000
},[]]}},{ancestors,[net_sup,kernel_sup,0.8.0]},{messages,[]},{links,[#Port0.8
,0.17.0]},{dictionary,[{longnames,false}]},{trap_exit,true},{status,running},
{heap_size,233},{stack_size,21},{reductions,415}],[]]}
{error_logger,{{2007,12,19},{16,25,25}},supervisor_report,[{supervisor,{local,ne
t_sup}},{errorContext,start_error},{reason,{'EXIT',nodistribution}},{offender,[{
pid,undefined},{name,net_kernel},{mfa,{net_kernel,start_link,[[ejabberd,shortnam
es]]}},{restart_type,permanent},{shutdown,2000},{child_type,worker}]}]}
{error_logger,{{2007,12,19},{16,25,25}},supervisor_report,[{supervisor,{local,ke
rnel_sup}},{errorContext,start_error},{reason,shutdown},{offender,[{pid,undefine
d},{name,net_sup},{mfa,{erl_distribution,start_link,[]}},{restart_type,permanent
},{shutdown,infinity},{child_type,supervisor}]}]}
{error_logger,{{2007,12,19},{16,25,25}},crash_report,[[{pid,0.7.0},{registered
_name,[]},{error_info,{shutdown,{kernel,start,[normal,[]]}}},{initial_call,{appl
ication_master,init,[0.5.0,0.6.0,{appl_data,kernel,[application_controller,e
rl_reply,auth,boot_server,code_server,disk_log_server,disk_log_sup,erl_prim_load
er,error_logger,file_server_2,fixtable_server,global_group,global_name_server,he
Bug#457088: [Pkg-openmpi-maintainers] Bug#457088: mpi.h is missing
On 12/19/07, Dirk Eddelbuettel [EMAIL PROTECTED] wrote: On Wed, Dec 19, 2007 at 07:40:13PM +0100, Ondrej Certik wrote: On Dec 19, 2007 7:15 PM, Dirk Eddelbuettel [EMAIL PROTECTED] wrote: On Wed, Dec 19, 2007 at 06:49:15PM +0100, Ondrej Certik wrote: Package: libopenmpi-dev Version: 1.2.4-5 Severity: serious --- Please enter the report below this line. --- Hi, the mpi.h is missing. I found it in /usr/lib/openmpi/include/ please add at least a symlink or something to /usr/include the is breaks the python-petsc4py package for example: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456869 It used to work before. I could fix it by patching the build scripts to include /usr/lib/openmpi/include/, but the right solution imho is to fix libopenmpi-dev. Nope, as we as package maintainers simply changed the location. Study the configure options you have in your client (source) code. For what it's worth, I just made the same change in Rmpi (being its maintainer). mpi.h not being in /usr/include is not a bug. and certainly not a serious bug. Please show some more restraint. You can always ask us off-line, as you have seen in the last few days we tend to respond quickly. I am sorry I put the severity wrong. But you, as the maintainer can adjust it as you see fit. As to the real problem - I just asked about exactly this on debian-python: http://lists.debian.org/debian-python/2007/12/msg00030.html and I think include files belong to /usr/include, accordig to the FHS: http://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html#USRINCLUDEDIRECTORYFORSTANDARDINCLU So it's imho a bug and should be reopened. (I know how to fix petsc4py, I just tried and confirmed it works, but I think it's a bug that should be fixed in openmpi, not petsc4py). Why do you think the header files shouldn't be in /usr/include? As you may know, we are trying to let Open MPI coexist with MPICH and LAM. /usr/include is fine for _non-conflicting_ files as good as a general rule, but not so clear if several packages provide it. By 'staying out of each others way' it is easier to build against several MPI implementations. I meant something like /usr/include/openmpi/ So no bug here. I am not going to argue with you if it is a bug or not, but imho all packages I know use /usr/include, also I provided references that suggest to do it as I say. Can you provide some arguments why you think they are wrong? Ondrej Thanks, Dirk -- Three out of two people have difficulties with fractions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457063: asterisk: CVE-2007-6430 remote unauthenticated sessions
On Wed, Dec 19, 2007 at 08:52:10PM +0200, Faidon Liambotis wrote: Nico Golde wrote: CVE-2007-6430[0]: | Due to the way database-based registrations (realtime) | are processed, IP addresses are not checked when the | username is correct and there is no password. An | attacker may impersonate any user using host-based | authentication without a secret, simply by guessing the | username of that user. This is limited in scope to | administrators who have set up the registration database | (realtime) for authentication and are using only | host-based authentication, not passwords. However, both | the SIP and IAX protocols are affected. This is affecting unstable and stable. oldstable is not affected. I'll upload 1.4.16 (.1 due soon probably, since .16 has a major bug) to unstable probably tomorrow or the day after that. For stable, I don't think that the vulnerability is serious enough to warrant a DSA. I agree that a DSA is not warranted. Maybe s-p-u is a better candidate? s-p-u handling is sluggish, the next asterisk DSA will likely appear before it enters the next point release. A more serious asterisk issue will surely appear, so let's just postpone it. Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: [SPAM] - Bug#457097: ejabberd dont start - Bayesian Filter detected spam
Processing commands for [EMAIL PROTECTED]: severity 457097 normal Bug#457097: ejabberd dont start 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#457100: xscreensaver: cannot allocate any color - crashes X
Package: xscreensaver Version: 5.04-2 Severity: grave Justification: renders package unusable Launching xscreensaver-demo gives this: $ xscreensaver-demo antmaze: couldn't allocate color black: using black. antmaze: couldn't allocate black either! When xscreensaver timeouts and tries to launch a screensaver it also crashes the X server. An strace reveals that xscreensaver tries to read /usr/lib/X11/Xcms.txt which is not available in any of the Debian packages -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (900, 'stable'), (500, 'testing'), (100, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.23.9 (PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages xscreensaver depends on: ii libatk1.0-01.20.0-1 The ATK accessibility toolkit ii libc6 2.7-4 GNU C Library: Shared libraries ii libcairo2 1.4.12-1 The Cairo 2D vector graphics libra ii libglade2-01:2.6.2-1 library to load .glade files at ru ii libglib2.0-0 2.14.4-2 The GLib library of C routines ii libgtk2.0-02.12.3-2 The GTK+ graphical user interface ii libice62:1.0.4-1 X11 Inter-Client Exchange library ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii libpam0g 0.99.7.1-5Pluggable Authentication Modules l ii libpango1.0-0 1.18.3-1 Layout and rendering of internatio ii libsm6 2:1.0.3-1+b1 X11 Session Management library ii libx11-6 2:1.0.3-7 X11 client-side library ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar ii libxinerama1 1:1.0.2-1 X11 Xinerama extension library ii libxml22.6.30.dfsg-3 GNOME XML library ii libxmu61:1.0.3-1 X11 miscellaneous utility library ii libxpm41:3.5.7-1 X11 pixmap library ii libxrandr2 2:1.2.2-1 X11 RandR extension library ii libxrender11:0.9.4-1 X Rendering Extension client libra ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library ii libxxf86misc1 1:1.0.1-2 X11 XFree86 miscellaneous extensio ii libxxf86vm11:1.0.1-2 X11 XFree86 video mode extension l ii netpbm 2:10.0-11 Graphics conversion tools Versions of packages xscreensaver recommends: ii libjpeg-progs 6b-14 Programs for manipulating JPEG fil ii perl [perl5] 5.8.8-12 Larry Wall's Practical Extraction ii wamerican [wordlist] 6-2.1 American English dictionary words ii xloadimage4.1-16 Graphics file viewer under X11 -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457097: [SPAM] - Bug#457097: ejabberd dont start - Bayesian Filter detected spam
severity 457097 normal
thanks
On 12/19/07, Fernando Toledo [EMAIL PROTECTED] wrote:
Package: ejabberd
Version: 1.1.2-6
Severity: grave
Justification: renders package unusable
I guess it's not ejabberd fault.
hi, i start the ejabberd service and seems to die
scarlet:~# /etc/init.d/ejabberd start
Starting jabber server: ejabberd.
It's started.
scarlet:~# ejabberdctl
RPC failed on the node [EMAIL PROTECTED]: {'EXIT',
It looks that there's something wrong with your networking setup. Does
your server have a hostname other than localhost?
how to i can increase more log level for debug and get more info?
i have a empty /var/log/ejabberd/
It's a bad symptom. Who is an owner of /var/lib/ejabberd and /var/log/ejabberd?
i try to manual start:
scarlet:~# su - ejabberd -c /usr/sbin/ejabberd -noshell -s
{error_logger,{{2007,12,19},{16,25,25}},Protocol: ~p: register error:
~p~n,[i
net_tcp,{{badmatch,{error,duplicate_name}}
This (duplicate_name) means that another ejabberd instance is already running.
Please, show the ejabberd config, doublecheck the owner and
permissions of /var/log/ejabberd and /var/lib/ejabberd, and also show
your networking settings (hostname, /etc/hosts, /etc/resolv.conf).
--
Sergei Golovan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457101: xserver-xorg crashes with signal 11
Package: xserver-xorg Version: 1:7.3+8 Severity: grave amd64 After upgrading from 7.2+5 X crashes with signal 11. Nvidia drivers were recompiled with correct gcc version. ... (**) Mouse0: Buttons: 9 (**) Mouse0: Sensitivity: 1 (II) evaluating device (Mouse0) (II) XINPUT: Adding extended input device Mouse0 (type: MOUSE) (II) evaluating device (Keyboard0) (II) XINPUT: Adding extended input device Keyboard0 (type: KEYBOARD) (II) Mouse0: ps2EnableDataReporting: succeeded Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! Backtrace: 0: /usr/bin/X11/X(xf86SigHandler+0x6a) [0x47557a] 1: /lib/libc.so.6 [0x2b7ae1f1c040] 2: /lib/libc.so.6(realloc+0x79) [0x2b7ae1f61da9] 3: /usr/bin/X11/X(Xrealloc+0x1b) [0x564abb] 4: /usr/bin/X11/X [0x4bc6e9] 5: /usr/lib/xorg/modules/drivers//nvidia_drv.so [0x2b7ae4cfd7a3] Fatal server error: Caught signal 11. Server aborting (II) Screen 0 shares mem io resources (II) Screen 1 shares mem io resources Curiously aptitude enabled this update just with the last update. Previous version of aptitude was holding back this update (safe-upgrade). BTW where can I recover 7.2+5 packages for amd64 other than in my cache? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457100: xscreensaver: cannot allocate any color - crashes X
Emil wrote: Package: xscreensaver Version: 5.04-2 Severity: grave Justification: renders package unusable Launching xscreensaver-demo gives this: $ xscreensaver-demo antmaze: couldn't allocate color black: using black. antmaze: couldn't allocate black either! When xscreensaver timeouts and tries to launch a screensaver it also crashes the X server. An strace reveals that xscreensaver tries to read /usr/lib/X11/Xcms.txt which is not available in any of the Debian packages Hi Emil, I really believe this is more a problem with you xserver that a xscreensaver issue, try running: $ /usr/lib/xscreensaver/antmaze This should launch a little window with a screensaver, if this don't work then I believe is an issue with your xserver. In that case I'm usign X.Org 1.4.0: [EMAIL PROTECTED]:~$ Xorg -version X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20071119-1) Current Operating System: Linux hyperion 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64 Build Date: 20 November 2007 02:55:16AM Which is yours? Regards, Jose Luis. -- ghostbar on debian linux 'sid' 2.6.22 x86_64-SMP - #382503 Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Cristóbal, Venezuela. http://chaslug.org.ve GPG: 0xCACAB118 signature.asc Description: OpenPGP digital signature
Bug#456992: smbfs: mount.cifs fails with mount error: could not find target server. TCP name ... not found
On Wed, Dec 19, 2007 at 01:23:30AM -0800, Steve Langasek wrote: To mount such shares without DNS support, you have three options: - add your own entry in /etc/hosts - add nss_wins from the winbind package to your nsswitch.conf - use the ip= option to mount.cifs I used the second solution, and it worked fine. Many thanks! Julian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#456352: marked as done (scratchbox2: FTBFS: preload/interface.master: No such file or directory)
Your message dated Wed, 19 Dec 2007 20:47:06 + with message-id [EMAIL PROTECTED] and subject line Bug#456352: fixed in scratchbox2 1.99.0.22 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: scratchbox2 Version: 1.99.0.20 Severity: serious Hi, Your package is failing to build with the following error: [PERL] preload/wrappers.c /bin/sh: line 1: preload/interface.master: No such file or directory make[2]: *** [preload/wrappers.c] Error 1 Kurt ---End Message--- ---BeginMessage--- Source: scratchbox2 Source-Version: 1.99.0.22 We believe that the bug you reported is fixed in the latest version of scratchbox2, which is due to be installed in the Debian FTP archive: scratchbox2_1.99.0.22.dsc to pool/main/s/scratchbox2/scratchbox2_1.99.0.22.dsc scratchbox2_1.99.0.22.tar.gz to pool/main/s/scratchbox2/scratchbox2_1.99.0.22.tar.gz scratchbox2_1.99.0.22_i386.deb to pool/main/s/scratchbox2/scratchbox2_1.99.0.22_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. Riku Voipio [EMAIL PROTECTED] (supplier of updated scratchbox2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Dec 2007 23:27:48 +0200 Source: scratchbox2 Binary: scratchbox2 Architecture: source i386 Version: 1.99.0.22 Distribution: unstable Urgency: low Maintainer: Riku Voipio [EMAIL PROTECTED] Changed-By: Riku Voipio [EMAIL PROTECTED] Description: scratchbox2 - Transparent cross compiling environment Closes: 456352 456528 Changes: scratchbox2 (1.99.0.22) unstable; urgency=low . * New upstream version * Fix building on 386, closes: #456352 * Fix amd64 multilib install location, closes: #456528 Files: aa48bb413d383a3b014d0f168a62d2cc 722 utils extra scratchbox2_1.99.0.22.dsc 86fe9040c3a49233cf0e7a66de0dafc6 303875 utils extra scratchbox2_1.99.0.22.tar.gz b21b4185fed83d6b5b4b195fe4d6e3f0 116242 utils extra scratchbox2_1.99.0.22_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHaYBCibPvMsrqrwMRAqeTAKCrGihsTaiZX3ZkBD5CuCy0vvbqewCg6yCL hw4oyTiw0vBmLIiFAKUUVjY= =rT7U -END PGP SIGNATURE- ---End Message---
Bug#457101: xserver-xorg crashes with signal 11
reassign 457101 nvidia-glx severity 457101 important kthxbye On Wed, Dec 19, 2007 at 21:12:50 +0100, Ivan Sergio Borgonovo wrote: Package: xserver-xorg Version: 1:7.3+8 Severity: grave amd64 After upgrading from 7.2+5 X crashes with signal 11. Nvidia drivers were recompiled with correct gcc version. Using a proprietary driver, you're pretty much on your own. In any case, you need to provide your complete X log and xorg.conf. ... (**) Mouse0: Buttons: 9 (**) Mouse0: Sensitivity: 1 (II) evaluating device (Mouse0) (II) XINPUT: Adding extended input device Mouse0 (type: MOUSE) (II) evaluating device (Keyboard0) (II) XINPUT: Adding extended input device Keyboard0 (type: KEYBOARD) (II) Mouse0: ps2EnableDataReporting: succeeded Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! Backtrace: 0: /usr/bin/X11/X(xf86SigHandler+0x6a) [0x47557a] 1: /lib/libc.so.6 [0x2b7ae1f1c040] 2: /lib/libc.so.6(realloc+0x79) [0x2b7ae1f61da9] 3: /usr/bin/X11/X(Xrealloc+0x1b) [0x564abb] 4: /usr/bin/X11/X [0x4bc6e9] 5: /usr/lib/xorg/modules/drivers//nvidia_drv.so [0x2b7ae4cfd7a3] Fatal server error: Caught signal 11. Server aborting (II) Screen 0 shares mem io resources (II) Screen 1 shares mem io resources Curiously aptitude enabled this update just with the last update. Previous version of aptitude was holding back this update (safe-upgrade). BTW where can I recover 7.2+5 packages for amd64 other than in my cache? In testing, or snapshot.debian.net. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#456528: marked as done (scratchbox2: Has files in /usr/lib32/)
Your message dated Wed, 19 Dec 2007 20:47:06 + with message-id [EMAIL PROTECTED] and subject line Bug#456528: fixed in scratchbox2 1.99.0.22 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: scratchbox2 Version: 1.99.0.19 Severity: serious Hi, Your package has files in the /usr/lib32 dir on amd64: /usr/lib32/libsb2/libsb2.so.1 /usr/lib32/libsb2/libsb2.so.1.99.0.19 This will break things when you try to remove your package. Please move those files to be within /emul/ia32-linux/usr/lib/ so probably /emul/ia32-linux/usr/lib/libsb2/ Kurt ---End Message--- ---BeginMessage--- Source: scratchbox2 Source-Version: 1.99.0.22 We believe that the bug you reported is fixed in the latest version of scratchbox2, which is due to be installed in the Debian FTP archive: scratchbox2_1.99.0.22.dsc to pool/main/s/scratchbox2/scratchbox2_1.99.0.22.dsc scratchbox2_1.99.0.22.tar.gz to pool/main/s/scratchbox2/scratchbox2_1.99.0.22.tar.gz scratchbox2_1.99.0.22_i386.deb to pool/main/s/scratchbox2/scratchbox2_1.99.0.22_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. Riku Voipio [EMAIL PROTECTED] (supplier of updated scratchbox2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Dec 2007 23:27:48 +0200 Source: scratchbox2 Binary: scratchbox2 Architecture: source i386 Version: 1.99.0.22 Distribution: unstable Urgency: low Maintainer: Riku Voipio [EMAIL PROTECTED] Changed-By: Riku Voipio [EMAIL PROTECTED] Description: scratchbox2 - Transparent cross compiling environment Closes: 456352 456528 Changes: scratchbox2 (1.99.0.22) unstable; urgency=low . * New upstream version * Fix building on 386, closes: #456352 * Fix amd64 multilib install location, closes: #456528 Files: aa48bb413d383a3b014d0f168a62d2cc 722 utils extra scratchbox2_1.99.0.22.dsc 86fe9040c3a49233cf0e7a66de0dafc6 303875 utils extra scratchbox2_1.99.0.22.tar.gz b21b4185fed83d6b5b4b195fe4d6e3f0 116242 utils extra scratchbox2_1.99.0.22_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHaYBCibPvMsrqrwMRAqeTAKCrGihsTaiZX3ZkBD5CuCy0vvbqewCg6yCL hw4oyTiw0vBmLIiFAKUUVjY= =rT7U -END PGP SIGNATURE- ---End Message---
Processed: Re: Bug#457101: xserver-xorg crashes with signal 11
Processing commands for [EMAIL PROTECTED]: reassign 457101 nvidia-glx Bug#457101: xserver-xorg crashes with signal 11 Bug reassigned from package `xserver-xorg' to `nvidia-glx'. severity 457101 important Bug#457101: xserver-xorg crashes with signal 11 Severity set to `important' from `grave' kthxbye 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#457088: [Pkg-openmpi-maintainers] Bug#457088: mpi.h is missing
On 19 December 2007 at 20:38, [EMAIL PROTECTED] wrote: | As you may know, we are trying to let Open MPI coexist with MPICH and | LAM. | | /usr/include is fine for _non-conflicting_ files as good as a general | rule, but not so clear if several packages provide it. By 'staying | out of each others way' it is easier to build against several MPI | implementations. | | I meant something like /usr/include/openmpi/ You lost me. Please make up your mind as to whether you think it is a problem because we do or do not use /usr/include, or /usr/include/openmpi ? We use /usr/include/openmpi now, and we think that's the right way: [EMAIL PROTECTED]:~$ dpkg -L libopenmpi-dev | grep mpi.h /usr/lib/openmpi/include/mpi.h /usr/lib/openmpi/include/openmpi/ompi/mpi/f77/prototypes_mpi.h [EMAIL PROTECTED]:~$ dpkg -l libopenmpi-dev Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-==-==- ii libopenmpi-dev 1.2.4-5 high performance message passing library -- header files [EMAIL PROTECTED]:~$ No bug here, and if you could excuse me now, I got real work to do. Dirk -- Three out of two people have difficulties with fractions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#454158: update
Is the cli-common version 0.5.1 or higher? If not, ugprade cli-common and dpkg-reconfigure both mono-addins packages again. Done, it works now! Mirco, you are my hero today. Thank you very much. Vit -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457088: [Pkg-openmpi-maintainers] Bug#457088: mpi.h is missing
On Wed, Dec 19, 2007 at 14:45:06 -0600, Dirk Eddelbuettel wrote: You lost me. Please make up your mind as to whether you think it is a problem because we do or do not use /usr/include, or /usr/include/openmpi ? Either would be ok. /usr/lib isn't. We use /usr/include/openmpi now, and we think that's the right way: No, you don't, you're using a subdirectory of /usr/lib/, and that's a serious bug. [EMAIL PROTECTED]:~$ dpkg -L libopenmpi-dev | grep mpi.h /usr/lib/openmpi/include/mpi.h /usr/lib/openmpi/include/openmpi/ompi/mpi/f77/prototypes_mpi.h Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457088: [Pkg-openmpi-maintainers] Bug#457088: mpi.h is missing
| I meant something like /usr/include/openmpi/ You lost me. Please make up your mind as to whether you think it is a problem because we do or do not use /usr/include, or /usr/include/openmpi ? We use /usr/include/openmpi now, and we think that's the right way: I agree that is the right way, but you don't use /usr/include/openmpi, but /usr/lib/openmpi/include, as you have just shown: [EMAIL PROTECTED]:~$ dpkg -L libopenmpi-dev | grep mpi.h /usr/lib/openmpi/include/mpi.h /usr/lib/openmpi/include/openmpi/ompi/mpi/f77/prototypes_mpi.h [EMAIL PROTECTED]:~$ dpkg -l libopenmpi-dev Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-==-==- ii libopenmpi-dev 1.2.4-5 high performance message passing library -- header files [EMAIL PROTECTED]:~$ No bug here, and if you could excuse me now, I got real work to do. I am sorry for taking your time. And I appreciate your work on openmpi. Unfortunately I still don't understand how it works. I admit it can be my fault. Let me repeat my question: Why does openmpi use /usr/lib instead of /usr/include? Other libraries use /usr/include, like petsc (/usr/include/petsc), libmesh (/usr/include/libmesh), gtk (/usr/include/gtk-2.0) etc. etc. Usually, as I understand it, they also use /usr/lib/something/include, but they always link from /usr/include. Also, I, as a user, was used to using /usr/include (/something) for everything, that's why I thought it'd the de facto standard, isn't it? And if not, is there some policy for that? I only found links I posted above, suggesting to use /usr/include. Thanks a lot, Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457063: asterisk: CVE-2007-6430 remote unauthenticated sessions
Hi Faidon, * Faidon Liambotis [EMAIL PROTECTED] [2007-12-19 20:18]: Nico Golde wrote: CVE-2007-6430[0]: | Due to the way database-based registrations (realtime) | are processed, IP addresses are not checked when the | username is correct and there is no password. An | attacker may impersonate any user using host-based | authentication without a secret, simply by guessing the | username of that user. This is limited in scope to | administrators who have set up the registration database | (realtime) for authentication and are using only | host-based authentication, not passwords. However, both | the SIP and IAX protocols are affected. This is affecting unstable and stable. oldstable is not affected. I'll upload 1.4.16 (.1 due soon probably, since .16 has a major bug) to unstable probably tomorrow or the day after that. [...] Sounds good, thanks for taking care of it. Kind regards Nico -- Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. pgpSooH9CPukn.pgp Description: PGP signature
Bug#457100: marked as done (xscreensaver: cannot allocate any color - crashes X)
Your message dated Wed, 19 Dec 2007 17:13:29 -0430 with message-id [EMAIL PROTECTED] and subject line Bug#457100: xscreensaver: cannot allocate any color - crashes X 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: xscreensaver Version: 5.04-2 Severity: grave Justification: renders package unusable Launching xscreensaver-demo gives this: $ xscreensaver-demo antmaze: couldn't allocate color black: using black. antmaze: couldn't allocate black either! When xscreensaver timeouts and tries to launch a screensaver it also crashes the X server. An strace reveals that xscreensaver tries to read /usr/lib/X11/Xcms.txt which is not available in any of the Debian packages -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (900, 'stable'), (500, 'testing'), (100, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.23.9 (PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages xscreensaver depends on: ii libatk1.0-01.20.0-1 The ATK accessibility toolkit ii libc6 2.7-4 GNU C Library: Shared libraries ii libcairo2 1.4.12-1 The Cairo 2D vector graphics libra ii libglade2-01:2.6.2-1 library to load .glade files at ru ii libglib2.0-0 2.14.4-2 The GLib library of C routines ii libgtk2.0-02.12.3-2 The GTK+ graphical user interface ii libice62:1.0.4-1 X11 Inter-Client Exchange library ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii libpam0g 0.99.7.1-5Pluggable Authentication Modules l ii libpango1.0-0 1.18.3-1 Layout and rendering of internatio ii libsm6 2:1.0.3-1+b1 X11 Session Management library ii libx11-6 2:1.0.3-7 X11 client-side library ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar ii libxinerama1 1:1.0.2-1 X11 Xinerama extension library ii libxml22.6.30.dfsg-3 GNOME XML library ii libxmu61:1.0.3-1 X11 miscellaneous utility library ii libxpm41:3.5.7-1 X11 pixmap library ii libxrandr2 2:1.2.2-1 X11 RandR extension library ii libxrender11:0.9.4-1 X Rendering Extension client libra ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library ii libxxf86misc1 1:1.0.1-2 X11 XFree86 miscellaneous extensio ii libxxf86vm11:1.0.1-2 X11 XFree86 video mode extension l ii netpbm 2:10.0-11 Graphics conversion tools Versions of packages xscreensaver recommends: ii libjpeg-progs 6b-14 Programs for manipulating JPEG fil ii perl [perl5] 5.8.8-12 Larry Wall's Practical Extraction ii wamerican [wordlist] 6-2.1 American English dictionary words ii xloadimage4.1-16 Graphics file viewer under X11 -- no debconf information ---End Message--- ---BeginMessage--- Emil wrote: On 19 December 2007, Jose Luis Rivas Contreras [EMAIL PROTECTED] wrote: I really believe this is more a problem with you xserver that a xscreensaver issue, try running: $ /usr/lib/xscreensaver/antmaze This should launch a little window with a screensaver, if this don't work then I believe is an issue with your xserver. In that case I'm usign X.Org 1.4.0: Hi Jose, There was nothing wrong with xscreensaver, please close this bug. I've traced my problem to this: kernel was compiled with gcc-4.1 while the nvidia module was compiled with gcc-4.2. I've recompiled the nvidia module with the same compiler and everything is fine now. -- ghostbar on debian linux 'sid' 2.6.22 x86_64-SMP - #382503 Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Cristóbal, Venezuela. http://chaslug.org.ve GPG: 0xCACAB118 signature.asc Description: OpenPGP digital signature ---End Message---
Bug#457100: xscreensaver: cannot allocate any color - crashes X
On 19 December 2007, Jose Luis Rivas Contreras [EMAIL PROTECTED] wrote: I really believe this is more a problem with you xserver that a xscreensaver issue, try running: $ /usr/lib/xscreensaver/antmaze This should launch a little window with a screensaver, if this don't work then I believe is an issue with your xserver. In that case I'm usign X.Org 1.4.0: Hi Jose, There was nothing wrong with xscreensaver, please close this bug. I've traced my problem to this: kernel was compiled with gcc-4.1 while the nvidia module was compiled with gcc-4.2. I've recompiled the nvidia module with the same compiler and everything is fine now. -- Regards, Emil -- Hal 9000: Dave, put those Windows disks downDave...DAVE! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457088: [Pkg-openmpi-maintainers] Bug#457088: mpi.h is missing
On Wednesday 19 December 2007, Dirk Eddelbuettel wrote: On 19 December 2007 at 22:23, Julien Cristau wrote: | On Wed, Dec 19, 2007 at 14:45:06 -0600, Dirk Eddelbuettel wrote: | You lost me. Please make up your mind as to whether you think it is a | problem because we do or do not use /usr/include, or | /usr/include/openmpi ? | | Either would be ok. /usr/lib isn't. | | We use /usr/include/openmpi now, and we think that's the right way: | | No, you don't, you're using a subdirectory of /usr/lib/, and that's a | serious bug. Why?Many projects live off a common root dir, and Open MPI does just like others do. IIRC it does so upstream too. Sure. That common root dir is called /usr - and often used as a prefix for installations. /Sune - who thinks it is the duty of the maintainer to fix upstream crappyness - especially fhs stuff. -- I'm not able to telnet to the tool of a mailer on a cache, how does it work? First you should log on the device, so that you never need to delete from the RAM IDE command prompt over the MIDI PCI mailer. signature.asc Description: This is a digitally signed message part.
Bug#457088: [Pkg-openmpi-maintainers] Bug#457088: mpi.h is missing
On 19 December 2007 at 22:15, Ondrej Certik wrote: | | I meant something like /usr/include/openmpi/ | | You lost me. Please make up your mind as to whether you think it is a problem | because we do or do not use /usr/include, or /usr/include/openmpi ? | | We use /usr/include/openmpi now, and we think that's the right way: | | I agree that is the right way, but you don't use /usr/include/openmpi, | but /usr/lib/openmpi/include, as you have just shown: Ah, ok. That's still no bug but metaphysical. Some people like a common 'root' directory for projects. Rmpi, for one, expects lib/ and include inside an MPI_DIR somewhere which you can either supply as env var / configure var or hope it gets found. And for that matter, it does get found in Rmpi 0.5-5-2 and the upcoming new upstream release 0.5-6. Thanks, Dirk | | | [EMAIL PROTECTED]:~$ dpkg -L libopenmpi-dev | grep mpi.h | /usr/lib/openmpi/include/mpi.h | /usr/lib/openmpi/include/openmpi/ompi/mpi/f77/prototypes_mpi.h | [EMAIL PROTECTED]:~$ dpkg -l libopenmpi-dev | Desired=Unknown/Install/Remove/Purge/Hold | | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed | |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) | ||/ Name Version Description | +++-==-==- | ii libopenmpi-dev 1.2.4-5 high performance message passing library -- header files | [EMAIL PROTECTED]:~$ | | No bug here, and if you could excuse me now, I got real work to do. | | I am sorry for taking your time. And I appreciate your work on | openmpi. Unfortunately I still don't understand how it works. I admit | it can be my fault. | | Let me repeat my question: | | Why does openmpi use /usr/lib instead of /usr/include? Other libraries | use /usr/include, like petsc (/usr/include/petsc), libmesh | (/usr/include/libmesh), gtk | (/usr/include/gtk-2.0) etc. etc. Usually, as I understand it, they | also use /usr/lib/something/include, but they always link from | /usr/include. | | Also, I, as a user, was used to using /usr/include (/something) for | everything, that's why I thought it'd the de facto standard, isn't it? | And if not, | is there some policy for that? I only found links I posted above, | suggesting to use /usr/include. | | Thanks a lot, | Ondrej -- Three out of two people have difficulties with fractions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457088: [Pkg-openmpi-maintainers] Bug#457088: mpi.h is missing
On 19 December 2007 at 22:23, Julien Cristau wrote: | On Wed, Dec 19, 2007 at 14:45:06 -0600, Dirk Eddelbuettel wrote: | | You lost me. Please make up your mind as to whether you think it is a problem | because we do or do not use /usr/include, or /usr/include/openmpi ? | | Either would be ok. /usr/lib isn't. | | | We use /usr/include/openmpi now, and we think that's the right way: | | No, you don't, you're using a subdirectory of /usr/lib/, and that's a | serious bug. Why?Many projects live off a common root dir, and Open MPI does just like others do. IIRC it does so upstream too. Dirk -- Three out of two people have difficulties with fractions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457063: asterisk: CVE-2007-6430 remote unauthenticated sessions
Moritz Muehlenhoff wrote: On Wed, Dec 19, 2007 at 08:52:10PM +0200, Faidon Liambotis wrote: Nico Golde wrote: CVE-2007-6430[0]: | Due to the way database-based registrations (realtime) | are processed, IP addresses are not checked when the | username is correct and there is no password. An | attacker may impersonate any user using host-based | authentication without a secret, simply by guessing the | username of that user. This is limited in scope to | administrators who have set up the registration database | (realtime) for authentication and are using only | host-based authentication, not passwords. However, both | the SIP and IAX protocols are affected. This is affecting unstable and stable. oldstable is not affected. I'll upload 1.4.16 (.1 due soon probably, since .16 has a major bug) to unstable probably tomorrow or the day after that. For stable, I don't think that the vulnerability is serious enough to warrant a DSA. I agree that a DSA is not warranted. Maybe s-p-u is a better candidate? s-p-u handling is sluggish, the next asterisk DSA will likely appear before it enters the next point release. Please don't denigrate SRM. The next point release is planned to happen before the end of the year or early next year. It's true that it took a long time, though it's not because we were sluggish. There were some issues with the teams internals. When they got solved ries crashed and we had to start from scratch due to no backup being available which we asked for more than one year. Apparantly the backup was not planned because of some backup policy noone knew about. Those three problems are fixed in the meantime, so without any unforseeable misfortune a release will happen very soon. Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#264107: marked as done (O: dia2code -- a dia-UML code generator)
Your message dated Wed, 19 Dec 2007 22:32:05 + with message-id [EMAIL PROTECTED] and subject line Bug#264107: fixed in dia2code 0.8.3-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: WNPP Severity: normal I really don't know what I'm doing with this anymore, and I am unable to give it the attention that it needs, so therefore I am orphaning it. This package really needs someone to take over the upstream, it's pretty safe to say that they are dead considering their last release was in January of 2002. If nobody comes along to take over in a little while, I'm going to go ahead and suggest the removal of this package from Debian. Morgan ---End Message--- ---BeginMessage--- Source: dia2code Source-Version: 0.8.3-3 We believe that the bug you reported is fixed in the latest version of dia2code, which is due to be installed in the Debian FTP archive: dia2code_0.8.3-3.diff.gz to pool/main/d/dia2code/dia2code_0.8.3-3.diff.gz dia2code_0.8.3-3.dsc to pool/main/d/dia2code/dia2code_0.8.3-3.dsc dia2code_0.8.3-3_i386.deb to pool/main/d/dia2code/dia2code_0.8.3-3_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Francesco Aloe [EMAIL PROTECTED] (supplier of updated dia2code package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 19 Dec 2007 18:33:39 +0100 Source: dia2code Binary: dia2code Architecture: source i386 Version: 0.8.3-3 Distribution: unstable Urgency: low Maintainer: Francesco Aloe [EMAIL PROTECTED] Changed-By: Francesco Aloe [EMAIL PROTECTED] Description: dia2code - a dia-UML code generator Closes: 264107 Changes: dia2code (0.8.3-3) unstable; urgency=low . * debian/watch: fixed obsolete and not working watch file. Closes #49789. * debian/control: removed build-dep on automake1.4 and added automake. * debian/dirs: removed this file because it was not needed. * Removed some superfluous newlines, trailing whitespaces and fixed typos. . dia2code (0.8.3-2) unstable; urgency=low . * New maintainer (Closes: #264107) * debian/control: updated standards version to 3.7.3 * debian/control: removed build-dep on doc-to-man and added cdbs, patchutils * debian/rules: switched to cdbs * debian/compat: updated to 5 * debian/patches: managed patches by cdbs simple-patchsys * Fixed manpage: added some options missing * debian/dia2code.sgml: removed this file because it was used for to generate the manpage, is now being used the upstream manpage Files: 8f00d18f4745b446cbacef6fddab02a5 645 devel optional dia2code_0.8.3-3.dsc bf7f5d467dda74effc6362bf6a7bb82c 4389 devel optional dia2code_0.8.3-3.diff.gz af2419a62d524e143638c1bb03fb4dc8 52628 devel optional dia2code_0.8.3-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHaZhNHYflSXNkfP8RAqkUAKCDIDeanUVnrPZ0teSRnzdEIrscsACfTIYu URIrUq0+pgO4nxjOfY/+gYA= =L4jG -END PGP SIGNATURE- ---End Message---
Bug#457088: [Pkg-openmpi-maintainers] Bug#457088: Bug#457088: mpi.h is missing
On 19 December 2007 at 22:54, Sune Vuorela wrote: | On Wednesday 19 December 2007, Dirk Eddelbuettel wrote: | On 19 December 2007 at 22:23, Julien Cristau wrote: | | On Wed, Dec 19, 2007 at 14:45:06 -0600, Dirk Eddelbuettel wrote: | | You lost me. Please make up your mind as to whether you think it is a | | problem because we do or do not use /usr/include, or | | /usr/include/openmpi ? | | | | Either would be ok. /usr/lib isn't. | | | | We use /usr/include/openmpi now, and we think that's the right way: | | | | No, you don't, you're using a subdirectory of /usr/lib/, and that's a | | serious bug. | | Why?Many projects live off a common root dir, and Open MPI does just | like others do. IIRC it does so upstream too. | | Sure. That common root dir is called /usr - and often used as a prefix for | installations. Thanks for coming in late and missing what the discussion was about. You made sure that I'll be just that much more likely to just plain skip posts of yours in the futures. | /Sune | - who thinks it is the duty of the maintainer to fix upstream crappyness - | especially fhs stuff. Go outside and get some fresh air. Or catch some sleep. Or do both. Dirk, now truly done with this thread. -- Three out of two people have difficulties with fractions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#430247: marked as done (ldbl128 transition for alpha, powerpc, sparc, s390)
Your message dated Wed, 19 Dec 2007 22:35:29 + with message-id [EMAIL PROTECTED] and subject line Bug#430247: fixed in libbinio 1.4-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: libbinio-dev Severity: serious User: [EMAIL PROTECTED] Usertags: goal-ldbl128 Discussed in http://lists.debian.org/debian-devel/2007/05/msg01173.html With glibc-2.5 and gcc-4.1.2 (and gcc-4.2), the 'long double' data type did change from a 64bit representation to a 128bit representation on alpha, powerpc, sparc, s390. To allow partial upgrades of packages, we will need to rename all packages holding libraries with the long double data type in their API. Both libc and libstdc++ do not need to be renamed, because they support both representations. We rename the library packages on all architectures to avoid name mismatches between architectures (you can avoid the renaming by supporting both datatype representations in the library as done in glibc and libstdc++, but unless a library is prepared for that, it does not seem to be worth the effort). It is suggested to rename a package libfoo1 to libfoo1ldbl; please wait with the renaming if the package depends on another library package which needs renaming. This package has been indentified as one with header files in /usr/include matching 'long *double'. Please close this bug report if it is a false positive, or rename the package accordingly. ---End Message--- ---BeginMessage--- Source: libbinio Source-Version: 1.4-8 We believe that the bug you reported is fixed in the latest version of libbinio, which is due to be installed in the Debian FTP archive: libbinio-dev_1.4-8_alpha.deb to pool/main/libb/libbinio/libbinio-dev_1.4-8_alpha.deb libbinio1ldbl_1.4-8_alpha.deb to pool/main/libb/libbinio/libbinio1ldbl_1.4-8_alpha.deb libbinio_1.4-8.diff.gz to pool/main/libb/libbinio/libbinio_1.4-8.diff.gz libbinio_1.4-8.dsc to pool/main/libb/libbinio/libbinio_1.4-8.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek [EMAIL PROTECTED] (supplier of updated libbinio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 15 Dec 2007 03:31:06 -0800 Source: libbinio Binary: libbinio-dev libbinio1ldbl Architecture: source alpha Version: 1.4-8 Distribution: unstable Urgency: high Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Steve Langasek [EMAIL PROTECTED] Description: libbinio-dev - binary I/O stream class library (development files) libbinio1ldbl - binary I/O stream class library Closes: 430247 Changes: libbinio (1.4-8) unstable; urgency=high . * QA upload. * Rename libbinio1c2 to libbinio1ldbl for the ldbl128 transition on alpha, powerpc, s390, and sparc. Closes: #430247. Files: 1944d346bb6ccf7c0839880bda8d7d5e 597 libs optional libbinio_1.4-8.dsc 6642c0c7b8ac6f56c68ed92cc122ecb2 17001 libs optional libbinio_1.4-8.diff.gz ca305b4cd92af6382397dff81effbf16 32392 libs optional libbinio1ldbl_1.4-8_alpha.deb d3a64a2e73f8da678087b0e01538b7fe 38052 libdevel optional libbinio-dev_1.4-8_alpha.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHY7xfKN6ufymYLloRAiboAJ4j/0GAsxV0XSP99g2WPXWF53QwTACgnPbk TPaQR+/3j1CSm/fvbcX5JZI= =a5iT -END PGP SIGNATURE- ---End Message---
Bug#454964: marked as done (adplug - FTBFS: undefined reference to `binostream::writeFloat(__float128, binio::FType)')
Your message dated Wed, 19 Dec 2007 22:35:29 + with message-id [EMAIL PROTECTED] and subject line Bug#430247: fixed in libbinio 1.4-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: adplug Version: 2.0.1-6 Severity: serious There was an error while trying to autobuild your package: Automatic build of adplug_2.0.1-6 on debian-31.osdl.marist.edu by sbuild/s390 98 [...] /bin/sh ../libtool --tag=CXX --mode=link g++ -g -O2 ../src/.libs/libadplug.la -lbinio -o adplugdb adplugdb.o -lstdc++ mkdir .libs g++ -g -O2 -o .libs/adplugdb adplugdb.o ../src/.libs/libadplug.so /usr/lib/libbinio.so -lstdc++ ../src/.libs/libadplug.so: undefined reference to `binostream::writeFloat(__float128, binio::FType)' collect2: ld returned 1 exit status make[2]: *** [adplugdb] Error 1 make[2]: Leaving directory `/build/buildd/adplug-2.0.1/adplugdb' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/build/buildd/adplug-2.0.1' make: *** [build-stamp] Error 2 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 ** Build finished at 20071205-1038 FAILED [dpkg-buildpackage died] ---End Message--- ---BeginMessage--- Source: libbinio Source-Version: 1.4-8 We believe that the bug you reported is fixed in the latest version of libbinio, which is due to be installed in the Debian FTP archive: libbinio-dev_1.4-8_alpha.deb to pool/main/libb/libbinio/libbinio-dev_1.4-8_alpha.deb libbinio1ldbl_1.4-8_alpha.deb to pool/main/libb/libbinio/libbinio1ldbl_1.4-8_alpha.deb libbinio_1.4-8.diff.gz to pool/main/libb/libbinio/libbinio_1.4-8.diff.gz libbinio_1.4-8.dsc to pool/main/libb/libbinio/libbinio_1.4-8.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek [EMAIL PROTECTED] (supplier of updated libbinio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 15 Dec 2007 03:31:06 -0800 Source: libbinio Binary: libbinio-dev libbinio1ldbl Architecture: source alpha Version: 1.4-8 Distribution: unstable Urgency: high Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Steve Langasek [EMAIL PROTECTED] Description: libbinio-dev - binary I/O stream class library (development files) libbinio1ldbl - binary I/O stream class library Closes: 430247 Changes: libbinio (1.4-8) unstable; urgency=high . * QA upload. * Rename libbinio1c2 to libbinio1ldbl for the ldbl128 transition on alpha, powerpc, s390, and sparc. Closes: #430247. Files: 1944d346bb6ccf7c0839880bda8d7d5e 597 libs optional libbinio_1.4-8.dsc 6642c0c7b8ac6f56c68ed92cc122ecb2 17001 libs optional libbinio_1.4-8.diff.gz ca305b4cd92af6382397dff81effbf16 32392 libs optional libbinio1ldbl_1.4-8_alpha.deb d3a64a2e73f8da678087b0e01538b7fe 38052 libdevel optional libbinio-dev_1.4-8_alpha.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHY7xfKN6ufymYLloRAiboAJ4j/0GAsxV0XSP99g2WPXWF53QwTACgnPbk TPaQR+/3j1CSm/fvbcX5JZI= =a5iT -END PGP SIGNATURE- ---End Message---
Bug#457088: [Pkg-openmpi-maintainers] Bug#457088: Bug#457088: mpi.h is missing
reopen 457088 #justification: fhs violation is a debian policy violation and this breaks #other packages thanks On Wednesday 19 December 2007, Dirk Eddelbuettel wrote: Thanks for coming in late and missing what the discussion was about. I have read the discussion in the bug report. If it is anywhere else, please point to it instead of playing smart-ass. From the fhs: /usr/include : Directory for standard include files. /usr/lib : Libraries for programming and packages mpi.h surely only fits in first category. /Sune -- I'm not able to load the software from Flash 2.2, how does it work? First you need to connect to the mother board. signature.asc Description: This is a digitally signed message part.
Processed: Re: [Pkg-openmpi-maintainers] Bug#457088: Bug#457088: mpi.h is missing
Processing commands for [EMAIL PROTECTED]: reopen 457088 Bug#457088: mpi.h is missing Bug reopened, originator not changed. #justification: fhs violation is a debian policy violation and this breaks #other packages 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#456851: marked as done (rmpi: FTBFS: error: mpi.h: No such file or directory)
Your message dated Wed, 19 Dec 2007 22:47:06 + with message-id [EMAIL PROTECTED] and subject line Bug#456851: fixed in rmpi 0.5-5-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: rmpi version: 0.5-5-1 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20071217 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. Relevant part: make[1]: Entering directory `/build/user/rmpi-0.5-5/src' gcc -std=gnu99 -I/usr/share/R/include -I/usr/share/R/include -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\ -DPACKAGE_VERSION=\\ -DPACKAGE_STRING=\\ -DPACKAGE_BUGREPORT=\\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DUNKNOWN -fPIC -fpic -g -O2 -c RegQuery.c -o RegQuery.o gcc -std=gnu99 -I/usr/share/R/include -I/usr/share/R/include -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\ -DPACKAGE_VERSION=\\ -DPACKAGE_STRING=\\ -DPACKAGE_BUGREPORT=\\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DUNKNOWN -fPIC -fpic -g -O2 -c Rmpi.c -o Rmpi.o In file included from Rmpi.c:18: Rmpi.h:1:17: error: mpi.h: No such file or directory In file included from Rmpi.c:18: Rmpi.h:14: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'mpitype' Rmpi.c:24: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token Rmpi.c:25: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token Rmpi.c:26: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token Rmpi.c:27: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token Rmpi.c:28: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token [...] The full build log is available from: http://people.debian.org/~lucas/logs/2007/12/17 A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: rmpi Source-Version: 0.5-5-2 We believe that the bug you reported is fixed in the latest version of rmpi, which is due to be installed in the Debian FTP archive: r-cran-rmpi_0.5-5-2_i386.deb to pool/main/r/rmpi/r-cran-rmpi_0.5-5-2_i386.deb rmpi_0.5-5-2.diff.gz to pool/main/r/rmpi/rmpi_0.5-5-2.diff.gz rmpi_0.5-5-2.dsc to pool/main/r/rmpi/rmpi_0.5-5-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. Dirk Eddelbuettel [EMAIL PROTECTED] (supplier of updated rmpi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 19 Dec 2007 16:22:44 -0600 Source: rmpi Binary: r-cran-rmpi Architecture: source i386 Version: 0.5-5-2 Distribution: unstable Urgency: low Maintainer: Dirk Eddelbuettel [EMAIL PROTECTED] Changed-By: Dirk Eddelbuettel [EMAIL PROTECTED] Description: r-cran-rmpi - GNU R package interfacing MPI libraries for distributed computing Closes: 456851 Changes: rmpi (0.5-5-2) unstable; urgency=low . * debian/control: Set versioned Build-Depends on libopenmpi-dev (= 1.2.4-5) . * configure.ac, configure: Patched to also search in /usr/lib/openmpi for include/mpi.h and libraries; patch sent upstream; will be in next (upstream) release 0.5-6 (Closes: #456851) Files: 6e871df715473811de83de8717c69df8 706 math optional rmpi_0.5-5-2.dsc 7d1ad23b83dd3509529bb0145cf28ded 3030 math optional rmpi_0.5-5-2.diff.gz 5c582ae546a4f51808ca1ea7c3a5d932 169996 math optional
Bug#457088: [Pkg-openmpi-maintainers] Bug#457088: Bug#457088: mpi.h is missing
Hi Ondrej! Am Mittwoch, den 19.12.2007, 22:15 +0100 schrieb Ondrej Certik: Unfortunately I still don't understand how it works. I admit it can be my fault. No problem. I'll try to explain the situation and reasoning below. Let me repeat my question: Why does openmpi use /usr/lib instead of /usr/include? Other libraries use /usr/include, like petsc (/usr/include/petsc), libmesh (/usr/include/libmesh), gtk (/usr/include/gtk-2.0) etc. etc. Usually, as I understand it, they also use /usr/lib/something/include, but they always link from /usr/include. I guess there's some misunderstanding here. mpi.h is located in /usr/lib/openmpi/include so it does not conflict with other MPI packages. But this directory is symlinked to /usr/include/mpi via alternatives, along with the compilers. So this ensures that the mpicc you use matches the /usr/include/mpi/mpi.h that is used and therefore prohibits conflicts. This is true for all MPI packages that provide mpi.h and mpicc (and similar compiler wrappers). So including /usr/include/mpi in your include file search path is the right thing to do. Given that, it does not matter if your package compiles for example against openmpi or lam4. Also, I, as a user, was used to using /usr/include (/something) for everything, that's why I thought it'd the de facto standard, isn't it? And if not, is there some policy for that? I only found links I posted above, suggesting to use /usr/include. You're right, /usr/include is still the search path. To the best of my knowledge the current behavior is in agreement with policy since we provide mpi.h under /usr/include. It's just in the mpi sub-directory to not get in conflict with other MPI packages. (MPI should be MPI, right?) Unfortunately, dpkg and other tools that can scan for files in packages are not aware of symlinks created by update-alternatives. So you just might have missed /usr/include/mpi. Hope I was able to clarify the issue. And I don't think it's a bug as well. Best regards Manuel signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#457088: marked as done (mpi.h is missing)
Your message dated Wed, 19 Dec 2007 17:15:21 -0600 with message-id [EMAIL PROTECTED] and subject line [Pkg-openmpi-maintainers] Bug#457088: Bug#457088: Bug#457088: mpi.h is missing 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: libopenmpi-dev Version: 1.2.4-5 Severity: serious --- Please enter the report below this line. --- Hi, the mpi.h is missing. I found it in /usr/lib/openmpi/include/ please add at least a symlink or something to /usr/include the is breaks the python-petsc4py package for example: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456869 It used to work before. I could fix it by patching the build scripts to include /usr/lib/openmpi/include/, but the right solution imho is to fix libopenmpi-dev. Thanks, Ondrej --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-2-686 Debian Release: lenny/sid 500 unstableftp.cz.debian.org 500 unstabledebian.certik.cz --- Package information. --- Depends (Version) | Installed ==-+- libopenmpi1(= 1.2.4-5) | 1.2.4-5 openmpi-common (= 1.2.4-5) | 1.2.4-5 ---End Message--- ---BeginMessage--- On 19 December 2007 at 23:43, Sune Vuorela wrote: | reopen 457088 | #justification: fhs violation is a debian policy violation and this breaks | #other packages | thanks | | On Wednesday 19 December 2007, Dirk Eddelbuettel wrote: | Thanks for coming in late and missing what the discussion was about. | | I have read the discussion in the bug report. If it is anywhere else, please | point to it instead of playing smart-ass. | | From the fhs: | /usr/include : Directory for standard include files. | /usr/lib : Libraries for programming and packages | | mpi.h surely only fits in first category. Dude: [EMAIL PROTECTED]:~$ find /usr/lib -name \*h | grep -v openmpi | wc -l 680 [EMAIL PROTECTED]:~$ I hope you do understand that this means that I have 680 non-openmpi headers below /usr/lib. Ok? Please see Manuel's posts to the various threads. I am not going to repeat everything again and again. pkg-openmpi is an open group. If for once you feel like being constructive, join and patch debian/rules, preferably after discussion on the group's list. Dirk | /Sune | -- | I'm not able to load the software from Flash 2.2, how does it work? | | First you need to connect to the mother board. | ___ | Pkg-openmpi-maintainers mailing list | [EMAIL PROTECTED] | http://lists.alioth.debian.org/mailman/listinfo/pkg-openmpi-maintainers -- Three out of two people have difficulties with fractions. ---End Message---
Bug#457088: [Pkg-openmpi-maintainers] Bug#457088: Bug#457088: Bug#457088: mpi.h is missing
Dear Sune! Am Mittwoch, den 19.12.2007, 23:43 +0100 schrieb Sune Vuorela: I have read the discussion in the bug report. If it is anywhere else, please point to it instead of playing smart-ass. That applies to everyone: I don't like the tone of the recent emails and would be glad if we could all calm down and keep the discussion at a technical level, so we can spend our time on working on Debian and not flaming each other. From the fhs: /usr/include : Directory for standard include files. /usr/lib : Libraries for programming and packages mpi.h surely only fits in first category. mpi.h is provided in /usr/include/mpi via update-alternatives, as every other include file needed by an MPI implementation is, so I do not see the problem here. I don't find a reference in the policy that states that one is not allowed to symlink to where the files reside in the filesystem. Actually, all packages using update-alternatives I looked at so far put their stuff in /usr/lib/package. If that's wrong, we can correct that. But from what I saw this is common practice. mpich even has files in /usr/lib/mpich/bin. IANADD, so I may be wrong and looked at broken packages. Could you please give me some insight how a solution would look like in your eyes? Thanks in advance! Best regards Manuel signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#456721: [Pkg-openmpi-maintainers] Processed: Re: Bug#456721:libpetsc.so depends on unexistent libraries
Am Mittwoch, den 19.12.2007, 06:58 -0600 schrieb Dirk Eddelbuettel: On 19 December 2007 at 13:08, Manuel Prinz wrote: | if we want to handle it via alternatives (which LAM doesn't) we have | check the situation in pgapack, so we don't get a problem there. What is | the advantage to have mpi.h in /usr/include? (Just curious.) Easy to find? Moving it to /usr/include/mpi.h would mean to move everything under the mpi packages' subdirectories to /usr/include, handling the common filenames via update-alternatives. This is quite complex because one has to work around #220044 and friends as we do now for the libs. It also requires changes in the other packages, so we should provide patches for them too and coordinate stuff like that. I don't see it as problem. It comes in handy if you compile multiple MPI packages like Nicholas does with gromacs. Best regards Manuel signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#456721: [Pkg-openmpi-maintainers] Processed: Re: Bug#456721:libpetsc.so depends on unexistent libraries
Hi Adam! Thanks for your explanations. I have one question still: Am Mittwoch, den 19.12.2007, 08:40 -0500 schrieb Adam C Powell IV: I think the confusion is: the .la files are not the static libs, they are libtool metadata files. The -dev package needs to include the .a static libs. The .la files are completely optional, and there's some difference of opinion on whether or not they are beneficial. If upstream installs them, I'd put them in the -dev package. The reasoning for dropping the .la files was that we don't build .a files. My understanding is that .la is useless without .a, so installing them did not make much sence to me. Or am I wrong here? Either way, where upstream puts it is probably the right place for it. The only exception being libmpi.so which is an alternatives symlink and not a regular symlink in order to fit in with the other MPI implementations. That was the reasoning why I did that. Sure, though mpicc should include the -I required to find it anyway. It's up to you. I'd leave it in its own dir to avoid possible collisions. That was my reason for handling it that way. Best regards Manuel signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#451513: For those who cares about #451513
Package: log4cpp Version: 1.0-2 Followup-For: Bug #451513 The problem was not only in timestamps. I had also implement 02_doc_install patch, case $(DESTDIR) was missing in install target of doc/Makefile.in Here is my patch in attachment. -- System Information: Debian Release: lenny/sid APT prefers testing-proposed-updates APT policy: (700, 'testing-proposed-updates'), (700, 'testing'), (670, 'proposed-updates'), (670, 'stable'), (600, 'unstable'), (550, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-vserver-686 (SMP w/2 CPU cores) Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Shell: /bin/sh linked to /bin/bash diff -raNu log4cpp-1.0.orig/debian/changelog log4cpp-1.0/debian/changelog --- log4cpp-1.0.orig/debian/changelog 2007-12-20 02:29:02.0 +0300 +++ log4cpp-1.0/debian/changelog2007-12-20 02:37:17.0 +0300 @@ -1,3 +1,12 @@ +log4cpp (1.0-2.1) unstable; urgency=low + + * Non-maintainer upload. + * Fix FTBFS caused by autotools call (closes: #451513): ++ debian/rules: touch autotools source files to prevent autoconf run; ++ 02_doc_install.diff: install some docs into $(DESTDIR)/path. + + -- Alexander GQ Gerasiov [EMAIL PROTECTED] Thu, 20 Dec 2007 02:34:41 +0300 + log4cpp (1.0-2) unstable; urgency=low * Bump SONAME. (Closes: #445928). diff -raNu log4cpp-1.0.orig/debian/patches/02_doc_install.diff log4cpp-1.0/debian/patches/02_doc_install.diff --- log4cpp-1.0.orig/debian/patches/02_doc_install.diff 1970-01-01 03:00:00.0 +0300 +++ log4cpp-1.0/debian/patches/02_doc_install.diff 2007-12-20 02:29:19.0 +0300 @@ -0,0 +1,30 @@ +--- log4cpp-1.0.orig/doc/Makefile.in 2007-09-03 13:53:35.0 +0400 log4cpp-1.0/doc/Makefile.in2007-12-20 02:16:06.0 +0300 +@@ -525,18 +525,18 @@ + ln -s ./latex/refman.pdf @[EMAIL PROTECTED] + + install-data-local: +- $(mkinstalldirs) $(man3dir) ++ $(mkinstalldirs) $(DESTDIR)$(man3dir) + @for i in ./man/man3/log4cpp.3 ./man/man3/log4cpp_*.3; do \ + inst=`basename $$i | sed 's/_/::/g'`; \ +- echo $(INSTALL_DATA) $$i$(man3dir)/$$inst; \ +- $(INSTALL_DATA) $$i $(man3dir)/$$inst; \ ++ echo $(INSTALL_DATA) $$i $(DESTDIR)$(man3dir)/$$inst; \ ++ $(INSTALL_DATA) $$i $(DESTDIR)$(man3dir)/$$inst; \ + done +- $(mkinstalldirs) $(docdir) +- cp -r html/. $(docdir) +- $(RM) -r -f $(docdir)/CVS \ +- $(docdir)/Makefile.am \ +- $(docdir)/Makefile.in \ +- $(docdir)/Makefile ++ $(mkinstalldirs) $(DESTDIR)$(docdir) ++ cp -r html/. $(DESTDIR)$(docdir) ++ $(RM) -r -f $(DESTDIR)$(docdir)/CVS \ ++ $(DESTDIR)$(docdir)/Makefile.am \ ++ $(DESTDIR)$(docdir)/Makefile.in \ ++ $(DESTDIR)$(docdir)/Makefile + + uninstall-local: + $(RM) $(man3dir)/log4cpp.3 diff -raNu log4cpp-1.0.orig/debian/patches/series log4cpp-1.0/debian/patches/series --- log4cpp-1.0.orig/debian/patches/series 2007-12-20 02:29:02.0 +0300 +++ log4cpp-1.0/debian/patches/series 2007-12-20 02:29:19.0 +0300 @@ -1 +1,2 @@ 01_bump_soname.diff +02_doc_install.diff diff -raNu log4cpp-1.0.orig/debian/rules log4cpp-1.0/debian/rules --- log4cpp-1.0.orig/debian/rules 2007-12-20 02:29:02.0 +0300 +++ log4cpp-1.0/debian/rules2007-12-20 02:29:19.0 +0300 @@ -1,5 +1,8 @@ #!/usr/bin/make -f +configure/liblog4cpp5:: + touch -r aclocal.m4 configure.in + include /usr/share/cdbs/1/class/autotools.mk include /usr/share/cdbs/1/rules/debhelper.mk include /usr/share/cdbs/1/rules/patchsys-quilt.mk
Bug#456721: [Pkg-openmpi-maintainers] Processed: Re: Bug#456721:libpetsc.so depends on unexistent libraries
Le jeudi 20 décembre 2007 à 00:42 +0100, Manuel Prinz a écrit : Am Mittwoch, den 19.12.2007, 08:40 -0500 schrieb Adam C Powell IV: I think the confusion is: the .la files are not the static libs, they are libtool metadata files. The -dev package needs to include the .a static libs. The .la files are completely optional, and there's some difference of opinion on whether or not they are beneficial. If upstream installs them, I'd put them in the -dev package. The reasoning for dropping the .la files was that we don't build .a files. My understanding is that .la is useless without .a, so installing them did not make much sence to me. Or am I wrong here? You are wrong, sorry :p Just open one .la file and you will understand. They are supposed to hide the complexity of dynamic libraries. For example, if you are linking thanks to libtool with a dyn library, you can use the .la file to link it. And if this library has dependencies, the .la will tell you that. It will also provide you the name of the library, linker flags, version Example: # grep dependency myGreatLibraryWhichNeedsPcre.la dependency_libs=' -L/usr/lib -lpcreposix -lpcre' I hope I am clear on this ;) Sylvestre signature.asc Description: Ceci est une partie de message numériquement signée
Bug#455872: splashy: Fails to initialize, messes up loading other modules
On Tuesday 18 December 2007 16:31:09 Luis Mondesi wrote: If you have libdirectfb-0.9.25-x installed, can you please remove it? It seems that even though Splashy links against libdirectfb-1.0.x (from Sid), the binary tries to access the older version of the lib causing the -3 errors. Please report back ASAP as we are getting ready to do a bug fix release. Removing libdirectfb-0.9.25 definately helped. Splashy now generally works, although not perfectly: 1) After about 5% progress while booting, the boot process stalls (with Splashy visible) until F2 is pressed, at which point booting continues (Splashy still being displayed). 2) After logging into X, there are some small black spots near the top of the screen. This is X.org 1:7.3+8 with NVidia drivers 100.14.19-1 compiled from source. Regards, Georg -- Georg Wittenburg http://page.mi.fu-berlin.de/~wittenbu/ signature.asc Description: This is a digitally signed message part.
Bug#451268: wrong direntries from makeinfo 4.11
With 4.11 PLUS your patch from the above it is still happening, Ah, the case before had a @dircategory. I didn't try without. (I surmise that's the difference, anyway.) - insert_string (START-INFO-DIR-ENTRY\n); + add_word (START-INFO-DIR-ENTRY\n); I installed it. Thanks very much. karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#456849: marked as done (libaqbanking: FTBFS: Package libgwenhywfar38-dev has no installation candidate)
Your message dated Thu, 20 Dec 2007 01:01:59 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#456849: libaqbanking: FTBFS: Package libgwenhywfar38-dev has no installation candidate 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: libaqbanking version: 2.3.3-2 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20071217 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. Relevant part: ** Using build dependencies supplied by package: Build-Depends: bzip2, cdbs, debhelper (= 4.1.16), doxygen, kdelibs4-dev, libchipcard3-dev, libglade2-dev, libgwenhywfar38-dev (= 2.5.4-2), libktoblzcheck1-dev (= 1.6-2), libssl-dev Checking for already installed source dependencies... bzip2: missing cdbs: missing debhelper: missing Using default version 5.0.62 doxygen: missing kdelibs4-dev: missing libchipcard3-dev: missing libglade2-dev: missing libgwenhywfar38-dev: missing Default version of libgwenhywfar38-dev not sufficient, no suitable version found. Skipping for now, maybe there are alternatives. libktoblzcheck1-dev: missing Using default version 1.16-1 libssl-dev: missing Checking for source dependency conflicts... Reading package lists... Building dependency tree... Reading state information... Package libgwenhywfar38-dev is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package libgwenhywfar38-dev has no installation candidate apt-get failed. Package installation failed Trying to reinstall removed packages: Trying to uninstall newly installed packages: Source-dependencies not satisfied; skipping libaqbanking The full build log is available from: http://people.debian.org/~lucas/logs/2007/12/17 A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: libaqbanking Version: 3.0.0-1 This bug is fixed in experimental. An upload to unstable will follow soon. Anyway, thanks for your feedback. Regards Micha ---End Message---
Bug#457120: openssh-server: subprocess post-installation script returned error exit status 1
Package: openssh-server Version: 1:4.6p1-7 Severity: critical Justification: breaks the whole system This bug is rated critical because it breaks apt-get upgrade and leaves the system in a dangerously unstable state. apt-get upgrade aborts: Setting up libsnmp-session-perl (1.11-1) ... Setting up netatalk (2.0.3-7) ... Installing new version of config file /etc/default/netatalk ... Installing new version of config file /etc/logcheck/ignore.d.server/netatalk ... Installing new version of config file /etc/netatalk/afpd.conf ... Installing new version of config file /etc/init.d/netatalk ... Starting Netatalk services (this will take a while): atalkd afpd papd. Errors were encountered while processing: openssh-server ssh E: Sub-process /usr/bin/dpkg returned an error code (1) apt-get install openssh-server Reading package lists... Done Building dependency tree... Done openssh-server is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 373 not upgraded. 2 not fully installed or removed. Need to get 0B of archives. After unpacking 0B of additional disk space will be used. Setting up openssh-server (1:4.6p1-7) ... /etc/ssh/sshd_config: line 74: Bad configuration option: NoneEnabled /etc/ssh/sshd_config: terminating, 1 bad configuration options invoke-rc.d: initscript ssh, action restart failed. dpkg: error processing openssh-server (--configure): subprocess post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of ssh: ssh depends on openssh-server; however: Package openssh-server is not configured yet. dpkg: error processing ssh (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: openssh-server ssh 72 73 UsePAM yes 74 NoneEnabled yes Sorry for the ugly formatting, in the unstable state I am not able to use a real editor and vi mangles cut and paste and makes editing difficult. The package will install when you remove the offending line from /etc/ssh/sshd_config.However, apt-get upgrade does not invoke the configure scripts when run again. It is possible that out of around 1000 packages upgraded, openssh-server was the last to be configured and apt-get didn't really abort.:wq -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages openssh-server depends on: ii adduser 3.105 add and remove users and groups ii debconf [debconf-2.0] 1.5.17 Debian configuration management sy ii dpkg 1.14.12package maintenance system for Deb ii libc6 2.7-4 GNU C Library: Shared libraries ii libcomerr21.40.3-1 common error description library ii libkrb53 1.6.dfsg.3~beta1-2 MIT Kerberos runtime libraries ii libpam-modules0.99.7.1-5 Pluggable Authentication Modules f ii libpam-runtime0.99.7.1-5 Runtime support for the PAM librar ii libpam0g 0.99.7.1-5 Pluggable Authentication Modules l ii libselinux1 2.0.15-2+b1SELinux shared libraries ii libssl0.9.8 0.9.8g-3 SSL shared libraries ii libwrap0 7.6.dbs-14 Wietse Venema's TCP wrappers libra ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip ii openssh-client1:4.6p1-7 secure shell client, an rlogin/rsh ii zlib1g1:1.2.3.3.dfsg-7 compression library - runtime openssh-server recommends no packages. -- debconf information: ssh/new_config: true * ssh/use_old_init_script: true * ssh/disable_cr_auth: false ssh/encrypted_host_key_but_no_keygen: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: setting package to gnome-keyring libgnome-keyring0 libgnome-keyring-dev libpam-gnome-keyring ...
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.11 package gnome-keyring libgnome-keyring0 libgnome-keyring-dev libpam-gnome-keyring Ignoring bugs not assigned to: libpam-gnome-keyring libgnome-keyring0 libgnome-keyring-dev gnome-keyring tags 456967 + pending Bug#456967: gnome-keyring: keyring daemon segfaults Tags were: patch 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: your mail
Processing commands for [EMAIL PROTECTED]: tag 451513 patch Bug#451513: log4cpp: FTBFS: updated timestamp cause failing autotools run There were no tags set. Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457122: hal: subprocess post-installation script returned error exit status 2
Package: hal Version: 0.5.10-4 Severity: grave Justification: renders package unusable hal went splat on dist-upgrade making other packages (gnome, etc) uninstallable. apt-get dist-upgade [...] Errors were encountered while processing: hal gnome-power-manager gnome-desktop-environment gnome E: Sub-process /usr/bin/dpkg returned an error code (1) cervantes:/home/whitis# apt-get install hal gnome-power-manager gnome-desktop-environment gnome Reading package lists... Done Building dependency tree Reading state information... Done hal is already the newest version. gnome-power-manager is already the newest version. gnome-desktop-environment is already the newest version. gnome is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded. 4 not fully installed or removed. Need to get 0B of archives. After unpacking 0B of additional disk space will be used. Setting up hal (0.5.10-4) ... Reloading system message bus config...Failed to open connection to system message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused invoke-rc.d: initscript dbus, action force-reload failed. Starting Hardware abstraction layer: hald invoke-rc.d: initscript hal, action start failed. dpkg: error processing hal (--configure): subprocess post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of gnome-power-manager: gnome-power-manager depends on hal (= 0.5.10-1); however: Package hal is not configured yet. dpkg: error processing gnome-power-manager (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of gnome-desktop-environment: gnome-desktop-environment depends on gnome-power-manager (= 2.20.1); however: Package gnome-power-manager is not configured yet. dpkg: error processing gnome-desktop-environment (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of gnome: gnome depends on gnome-desktop-environment (= 1:2.20.2); however: Package gnome-desktop-environment is not configured yet. dpkg: error processing gnome (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: hal gnome-power-manager gnome-desktop-environment gnome E: Sub-process /usr/bin/dpkg returned an error code (1) cervantes:/home/whitis# dpkg-reconfigure hal /usr/sbin/dpkg-reconfigure: hal is broken or not fully installed cervantes:/home/whitis# apt-get install hal Reading package lists... Done Building dependency tree Reading state information... Done hal is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded. 4 not fully installed or removed. Need to get 0B of archives. After unpacking 0B of additional disk space will be used. Setting up hal (0.5.10-4) ... Reloading system message bus config...Failed to open connection to system message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused invoke-rc.d: initscript dbus, action force-reload failed. Starting Hardware abstraction layer: hald invoke-rc.d: initscript hal, action start failed. dpkg: error processing hal (--configure): subprocess post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of gnome-power-manager: gnome-power-manager depends on hal (= 0.5.10-1); however: Package hal is not configured yet. dpkg: error processing gnome-power-manager (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of gnome-desktop-environment: gnome-desktop-environment depends on gnome-power-manager (= 2.20.1); however: Package gnome-power-manager is not configured yet. dpkg: error processing gnome-desktop-environment (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of gnome: gnome depends on gnome-desktop-environment (= 1:2.20.2); however: Package gnome-desktop-environment is not configured yet. dpkg: error processing gnome (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: hal gnome-power-manager gnome-desktop-environment gnome E: Sub-process /usr/bin/dpkg returned an error code (1) cervantes:/home/whitis# ls /var/run/dbus/system_bus_socket /var/run/dbus/system_bus_socket cervantes:/home/whitis# ls -lgF /var/run/dbus/system_bus_socket srwxrwxrwx 1 root 0 2007-12-17 10:48 /var/run/dbus/system_bus_socket= cervantes:/home/whitis# lsof /var/run/dbus/system_bus_socket cervantes:/home/whitis# ps axlww | fgrep -i dbus 0 0 11355 11354 22 0 2416 292 - S? 0:00 dbus-daemon --session --print-address --nofork 1 1000 15074 1 15 0 2412 652 - Ss ? 0:00 dbus-daemon --fork --print-address 26 --print-pid 28 --session 0 0 15122 15557 18 0 2080 564 - R+ pts/1 0:00 fgrep -i
Processed: Re: Bug#457122: hal: subprocess post-installation script returned error exit status 2
Processing commands for [EMAIL PROTECTED]: severity 457122 important Bug#457122: hal: subprocess post-installation script returned error exit status 2 Severity set to `important' from `grave' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#456858: libchipcard3: FTBFS: Package libgwenhywfar38-dev has no installation candidate
Processing commands for [EMAIL PROTECTED]: # let's make this a removal request clone 456858 -1 Bug#456858: libchipcard3: FTBFS: Package libgwenhywfar38-dev has no installation candidate Bug 456858 cloned as bug 457129. retitle -1 RM: libchipcard3 -- RoM; obsolete; FTBFS Bug#457129: libchipcard3: FTBFS: Package libgwenhywfar38-dev has no installation candidate Changed Bug title to `RM: libchipcard3 -- RoM; obsolete; FTBFS' from `libchipcard3: FTBFS: Package libgwenhywfar38-dev has no installation candidate'. severity -1 normal Bug#457129: RM: libchipcard3 -- RoM; obsolete; FTBFS Severity set to `normal' from `serious' submitter -1 ! Bug#457129: RM: libchipcard3 -- RoM; obsolete; FTBFS Changed Bug submitter from Lucas Nussbaum [EMAIL PROTECTED] to Micha Lenk [EMAIL PROTECTED]. reassign -1 ftp.debian.org Bug#457129: RM: libchipcard3 -- RoM; obsolete; FTBFS Bug reassigned from package `libchipcard3' to `ftp.debian.org'. 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#456858: libchipcard3: FTBFS: Package libgwenhywfar38-dev has no installation candidate
# let's make this a removal request clone 456858 -1 retitle -1 RM: libchipcard3 -- RoM; obsolete; FTBFS severity -1 normal submitter -1 ! reassign -1 ftp.debian.org stop Lucas Nussbaum submitted this bug: Package: libchipcard3 version: 3.0.4-1 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20071217 qa-ftbfs Justification: FTBFS on i386 During a rebuild of all packages in sid, your package failed to build on i386. libchipcard3 build depends on libgwenhywfar38-dev which is obsoleted by libgwenhywfar47-dev. libgwenhywfar38-dev is not going to be reintroduced again. Now, libchipcard (= 4) is in the archive and makes libchipcard3 obsolete. So, ftp-masters, please remove libchipcard3 from the archive. The only package still build-depending on libchipcard3 is libaqbanking, which is already updated (to use libchipcard instead) in experimental. So, as soon as libaqbanking = 3 hits unstable, libchipcard3 can safely be removed from the archive. Sorry for this somewhat jolty transition of libgwenhywfar. I should have prepared it a little more. On the other hand I learned a lot, and promise to do it better the next time. Regards Micha -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: forcibly merging 456915 457064
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.7 forcemerge 456915 457064 Bug#456915: boost: FTBFS: build.sh: line 15: gcc-4.1: command not found Bug#457064: FTBFS: boost fails to build from source Forcibly Merged 456915 457064. 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]
