Processed: Re: Bug#650667: problems with reading of /proc/
Processing commands for cont...@bugs.debian.org: forwarded 650667 http://www.freebsd.org/cgi/query-pr.cgi?pr=163076 Bug #650667 [kfreebsd-image-9.0-0-amd64] kfreebsd-9: problems with reading of /proc/self/maps Set Bug forwarded-to-address to 'http://www.freebsd.org/cgi/query-pr.cgi?pr=163076'. severity 650667 serious Bug #650667 [kfreebsd-image-9.0-0-amd64] kfreebsd-9: problems with reading of /proc/self/maps Severity set to 'serious' from 'important' End of message, stopping processing here. Please contact me if you need assistance. -- 650667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650552: [Pkg-javascript-devel] Bug#650552: Bug#650552: Bug#650552: Bug#650552: node-expat: FTBFS: EBADF, Bad file descriptor '/usr/lib/package.json'
On 05/12/2011 02:42, Jonas Smedegaard wrote: On 11-12-05 at 08:32am, Jonas Smedegaard wrote: On 11-12-04 at 07:06pm, Aaron M. Ucko wrote: Jonas Smedegaard d...@jones.dk writes: Not sure if the proper approach is to reasign or file another bug and make one of them affect the other - and since I maintain both packages I will simply spend my time on fixing the issue instead :-) Commendably practical; thanks for the prompt fix. :-) It looks like you may need to nudge the buildd maintainers, though; I'm not one myself, just a regular DD who keeps tabs on packages showing up on amd64 but not i386 or vice versa. The package needs a minor update anyway - I just wanted to wait another cycle (and get some sleep) to ensure the fixed d-shlibs had entered unstable, as I don't want to use versioned dependencies for bugfixes if avoidable. node-vows, off course (not d-shlibs - I am confused this morning). ...but then when rebuilding node-expat now it fails with another error mysterious to me: Waf: Entering directory `/tmp/buildd/node-expat-1.4.1/build' [1/2] cxx: node-expat.cc - build/default/node-expat_1.o [2/2] cxx_link: build/default/node-expat_1.o - build/default/node-expat.node Waf: Leaving directory `/tmp/buildd/node-expat-1.4.1/build' 'build' finished successfully (0.821s) NODE_PATH=/tmp/buildd/node-expat-1.4.1/debian/node-node-expat//usr/lib/nodejs node test.js node: symbol lookup error: /tmp/buildd/node-expat-1.4.1/build/default/node-expat.node: undefined symbol: _ZNK2v86String10WriteAsciiEPciii make: *** [build/node-node-expat] Error 127 I have now pushed the work, for others to try repeat the error from the Git. Perhaps Jérémy Lal has a clue about it...? This problem is caused by the fact you're building with latest libv8-dev, but nodejs 0.4 wasn't. I'll upload a nodejs 0.4 built against libv8 3.5 later today. Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651032: /usr/sbin/rpc.idmapd: rpc.idmapd referring to none existing library
Hello Steve and Kevin, To fix Debian Bug#649491[1], I moved the .so files to /lib and applied the following patch: --- a/libnfsidmap.c 2010-12-09 04:07:53.0 +1100 +++ b/libnfsidmap.c 2011-12-05 11:23:46.0 +1100 @@ -61,7 +61,7 @@ static struct mapping_plugin **nfs4_plug static struct mapping_plugin **gss_plugins = NULL; #ifndef PATH_PLUGINS -#define PATH_PLUGINS /usr/lib/libnfsidmap +#define PATH_PLUGINS /lib/libnfsidmap #endif #define PLUGIN_INIT_FUNC libnfsidmap_plugin_init [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649491 As Michael reported, libnfsidmap is still looking for the plugins in /usr/lib/libnfsidmap. What do I need to change in libnfsidmap to make it find the plugins in /lib/libnfsidmap? Please see Michael's report below. Cheers, Anibal As Michael has reported, libnfsidmap2 is still looking On Mon, Dec 05, 2011 at 08:18:08AM +0100, Michael Rasmussen wrote: Package: nfs-common Version: 1:1.2.5-2+b1 Severity: grave File: /usr/sbin/rpc.idmapd Justification: renders package unusable rpc.idmapd -v rpc.idmapd: libnfsidmap: using domain: midgaard rpc.idmapd: libnfsidmap: Unable to load plugin: /usr/lib/libnfsidmap/nsswitch.so: cannot open shared object file: No such file or directory rpc.idmapd: libnfsidmap: requested translation method, 'nsswitch', is not available rpc.idmapd: Unable to create name to user id mappings. rpc.idmapd is searching for libnfsidmap plugins in the wrong directory so bug #650904 must be reopen since the provided change made to libnfsidmap2 does not make any difference rpc.idmapd still uses /usr/lib/libnfsidmap. -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 172 udp785 ypbind 171 udp785 ypbind 172 tcp786 ypbind 171 tcp786 ypbind -- /etc/default/nfs-common -- NEED_STATD=no STATDOPTS= NEED_IDMAPD=yes NEED_GSSD= -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs Domain = midgaard [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- balder:/home /home nfs4 defaults,proto=tcp,retry=5,hard,intr,async,_netdev,rsize=32768,wsize=32768 0 0 -- /proc/mounts -- rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0 balder:/home/ /home nfs4 rw,relatime,vers=4,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.2.79,minorversion=0,local_lock=none,addr=192.168.2.2 0 0 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages nfs-common depends on: ii adduser 3.113 ii initscripts 2.88dsf-13.13 ii libc6 2.13-21 ii libcap2 1:2.22-1 ii libcomerr2 1.42-1 ii libdevmapper1.02.1 2:1.02.67-2 ii libevent-2.0-5 2.0.16-stable-1 ii libgssapi-krb5-21.10+dfsg~alpha1-6 ii libgssglue1 0.3-3.1 ii libk5crypto31.10+dfsg~alpha1-6 ii libkeyutils11.5.2-2 ii libkrb5-3 1.10+dfsg~alpha1-6 ii libnfsidmap20.24-3 ii libtirpc1 0.2.2-5 ii libwrap07.6.q-21 ii lsb-base3.2-28 ii rpcbind 0.2.0-6 ii ucf 3.0025+nmu2 Versions of packages nfs-common recommends: ii python 2.7.2-9 nfs-common suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650552: [Pkg-javascript-devel] Bug#650552: Bug#650552: Bug#650552: Bug#650552: node-expat: FTBFS: EBADF, Bad file descriptor '/usr/lib/package.json'
On 11-12-05 at 09:24am, Jérémy Lal wrote: On 05/12/2011 02:42, Jonas Smedegaard wrote: On 11-12-05 at 08:32am, Jonas Smedegaard wrote: On 11-12-04 at 07:06pm, Aaron M. Ucko wrote: Jonas Smedegaard d...@jones.dk writes: Not sure if the proper approach is to reasign or file another bug and make one of them affect the other - and since I maintain both packages I will simply spend my time on fixing the issue instead :-) Commendably practical; thanks for the prompt fix. :-) It looks like you may need to nudge the buildd maintainers, though; I'm not one myself, just a regular DD who keeps tabs on packages showing up on amd64 but not i386 or vice versa. The package needs a minor update anyway - I just wanted to wait another cycle (and get some sleep) to ensure the fixed d-shlibs had entered unstable, as I don't want to use versioned dependencies for bugfixes if avoidable. node-vows, off course (not d-shlibs - I am confused this morning). ...but then when rebuilding node-expat now it fails with another error mysterious to me: Waf: Entering directory `/tmp/buildd/node-expat-1.4.1/build' [1/2] cxx: node-expat.cc - build/default/node-expat_1.o [2/2] cxx_link: build/default/node-expat_1.o - build/default/node-expat.node Waf: Leaving directory `/tmp/buildd/node-expat-1.4.1/build' 'build' finished successfully (0.821s) NODE_PATH=/tmp/buildd/node-expat-1.4.1/debian/node-node-expat//usr/lib/nodejs node test.js node: symbol lookup error: /tmp/buildd/node-expat-1.4.1/build/default/node-expat.node: undefined symbol: _ZNK2v86String10WriteAsciiEPciii make: *** [build/node-node-expat] Error 127 I have now pushed the work, for others to try repeat the error from the Git. Perhaps Jérémy Lal has a clue about it...? This problem is caused by the fact you're building with latest libv8-dev, but nodejs 0.4 wasn't. I'll upload a nodejs 0.4 built against libv8 3.5 later today. Hmm - I suspect this means nodejs-dev should then depend not only on libv8-dev equal-or-larger than current but also on libv8-dev lower than current+1. Not sure about the exact syntax, but believe it is used several other packages as well... - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#650995: #650995 dependency loop: a possible explanation
Hi all, Following the hints: - /etc/init.d/keymap.sh has Required-Start: $remote_fs - /etc/insserv.conf defines $remote_fs as including $local_fs - /etc/insserv.conf defines $local_fs as including mountall - mountall.sh has Required-Start: checkfs - checkfs.sh has Required-Start: checkroot - checkroot has Should-Start: keymap - and we loop. Roland. -- Roland Mas La menace de la baffe pèse plus lourd que la baffe elle-même. -- in Sri Raoul le petit yogi (Gaudelette) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650709: murrine-themes broken by libgtk-3-0
On Fri, 02 Dec 2011 13:21:47 +0100, Yves-Alexis Perez wrote: murrine-themes is uninstallable in sid because libgtk-3-0 added a versioned breaks. No, it's not uninstallable, it's not co-installable with libgtk3 since, indeed, GTK3 breaks the gtk3 themes in murrine-themes. There's no fixed version for now, so you'll have to choose. This is unfortunate indeed, but it's not murrine-themes fault that gtk3 changed incompatibly. It is quite difficult to have a desktop without libgtk3. Would it be possible to remove the GTK3 theme until it is fixed? The GTK3 theme is useless without libgtk3. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 650829 to fso-frameworkd and fso-config-gta02: error when trying to install together
Processing commands for cont...@bugs.debian.org: retitle 650829 fso-frameworkd and fso-config-gta02: error when trying to install together Bug #650829 [fso-config-gta02,fso-frameworkd] fso-frameworkd and fso-config-gta01: error when trying to install together Changed Bug title to 'fso-frameworkd and fso-config-gta02: error when trying to install together' from 'fso-frameworkd and fso-config-gta01: error when trying to install together' thanks Stopping processing here. Please contact me if you need assistance. -- 650829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650709: murrine-themes broken by libgtk-3-0
On lun., 2011-12-05 at 09:56 +0100, Vincent Bernat wrote: On Fri, 02 Dec 2011 13:21:47 +0100, Yves-Alexis Perez wrote: murrine-themes is uninstallable in sid because libgtk-3-0 added a versioned breaks. No, it's not uninstallable, it's not co-installable with libgtk3 since, indeed, GTK3 breaks the gtk3 themes in murrine-themes. There's no fixed version for now, so you'll have to choose. This is unfortunate indeed, but it's not murrine-themes fault that gtk3 changed incompatibly. It is quite difficult to have a desktop without libgtk3. Would it be possible to remove the GTK3 theme until it is fixed? The GTK3 theme is useless without libgtk3. Well, maybe you could install the testing version? Yes, GTK3 themes could be removed, but that wouldn't be my preferred solution, honestly. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#650995: causes dependency loop in boot sequence (according to insserv)
Hi all, Package: console-common Version: 0.7.86 Severity: serious Installation of console-common 0.7.86 has failed in unstable for me with the following insserv error: I'd like to think of it as a console-common error which causes insserv to reject the keymap.sh script header causing dpkg to report an error state :) Setting up console-common (0.7.86) ... Looking for keymap to install: NONE insserv: There is a loop between service checkfs and cryptdisks if started insserv: loop involving service cryptdisks at depth 12 insserv: loop involving service checkroot at depth 11 insserv: There is a loop between service nfs-common and hwclock if started insserv: loop involving service hwclock at depth 12 insserv: There is a loop between service lvm2 and cryptdisks-early if started insserv: loop involving service cryptdisks-early at depth 12 insserv: There is a loop between service checkfs and cryptdisks if started insserv: There is a loop between service nfs-common and hwclock if started insserv: There is a loop between service lvm2 and cryptdisks-early if started insserv: loop involving service mountnfs at depth 8 insserv: loop involving service nfs-common at depth 7 insserv: loop involving service portmap at depth 6 insserv: loop involving service mountall at depth 4 insserv: loop involving service checkfs at depth 3 insserv: loop involving service lvm2 at depth 2 insserv: loop involving service udev at depth 1 insserv: loop involving service mtab at depth 13 insserv: There is a loop between service mountall and checkfs if started insserv: loop involving service keymap at depth 16 insserv: loop involving service hibernate-cleanup at depth 20 insserv: loop involving service networking at depth 22 insserv: loop involving service restorecond at depth 32 insserv: There is a loop between service mountnfs and nfs-common if started insserv: loop involving service alsa-utils at depth 33 insserv: loop involving service ifupdown-clean at depth 34 insserv: loop involving service console-screen at depth 34 insserv: exiting now without changing boot order! update-rc.d: error: insserv rejected the script header dpkg: error processing console-common (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: console-common There is a change in dependency information in the keymap.sh init.d script of console-common 0.7.86 that is not fully articulated in the changelog: diff -Nru console-common-0.7.85/debian/keymap.sh console-common-0.7.86/debian/keymap.sh --- console-common-0.7.85/debian/keymap.sh 2009-11-01 05:41:53.0 +1000 +++ console-common-0.7.86/debian/keymap.sh 2011-12-05 01:05:31.0 +1000 @@ -1,8 +1,8 @@ #!/bin/sh ### BEGIN INIT INFO # Provides: keymap -# Required-Start: mountdevsubfs -# Required-Stop: +# Required-Start: mountdevsubfs $remote_fs +# Required-Stop:$remote_fs # Default-Start:S # Default-Stop: # X-Interactive: true --- checkroot.sh declares a Should-Start depndency on keymap which is a declaration that keymap service should start before checkroot.sh when present, but now keymap is declaring that it only starts once the $remote_fs virtual boot checkpoint is satisfied which is much much later in the boot process. This is an impossible relationship because checkroot.sh is required by other services which must start before $remote_fs is satisfied. I would like to know why this change in dependency was made by the console-common maintainers? Thanks, Kel. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650935:
block 650935 by 650025 thanks I'll keep 650935 open to prevent duplicates. The real issue is in package vtk see 650025 Java glue libraries are located in /usr/lib/jni/*.so not in /usr/lib/*.so -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: block 650935 by 650025 Bug #650935 [src:gdcm] gdcm: FTBFS against vtk 5.8 Was not blocked by any bugs. Added blocking bug(s) of 650935: 650025 thanks Stopping processing here. Please contact me if you need assistance. -- 650935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649708: marked as done (Please Build-Depend on ghostscript, not gs-common.)
Your message dated Mon, 05 Dec 2011 10:33:08 + with message-id e1rxvra-0007fw...@franck.debian.org and subject line Bug#649708: fixed in magnus 20060324-7 has caused the Debian Bug report #649708, regarding Please Build-Depend on ghostscript, not gs-common. 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 649708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: magnus Version: 20060324-6 Severity: important User: debian-print...@lists.debian.org Usertags: drop-gs-common Hi, magnus currently Build-Depends on gs-common, which is a transitional package. The next upload of ghostscript (currently) plans to drop both gs-common and the ghostscript Provides: gs-common. As soon as that upload happens, it will make magnus FTBFS. Please replace the Build-Depends on gs-common to a Build-Depends on ghostscript. Cheers, OdyX ---End Message--- ---BeginMessage--- Source: magnus Source-Version: 20060324-7 We believe that the bug you reported is fixed in the latest version of magnus, which is due to be installed in the Debian FTP archive: magnus_20060324-7.diff.gz to main/m/magnus/magnus_20060324-7.diff.gz magnus_20060324-7.dsc to main/m/magnus/magnus_20060324-7.dsc magnus_20060324-7_amd64.deb to main/m/magnus/magnus_20060324-7_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 649...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ralf Treinen trei...@debian.org (supplier of updated magnus 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 05 Dec 2011 10:49:30 +0100 Source: magnus Binary: magnus Architecture: source amd64 Version: 20060324-7 Distribution: unstable Urgency: low Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Ralf Treinen trei...@debian.org Description: magnus - Computational group theory software with GUI Closes: 649708 Changes: magnus (20060324-7) unstable; urgency=low . * QA upload * debian/control: changed build-dependency on gs-common to ghostscript Thanks to Miguel de Val Borro for the patch. (closes: #649708). Checksums-Sha1: 69e9d7174487976d030770d32cb9046ab596ccf1 1069 magnus_20060324-7.dsc cc464222be3063a4dbb64fb429ca9531ebd6fa88 17872 magnus_20060324-7.diff.gz 5ec7a1ff290a66546b95b4737a3331599caf5f85 3681572 magnus_20060324-7_amd64.deb Checksums-Sha256: 2cd984127e9294f9374e09200d88cf0f317eedf367f4ff260ee5b62edc3525df 1069 magnus_20060324-7.dsc d7e97666a2790a19353a57b67fe347e7f5e7b854b7b08b813543dcc04a65f675 17872 magnus_20060324-7.diff.gz 231c6fc145a1e8c1b4c163bd8b3b3375761284c06f529ce04978b17925e5c665 3681572 magnus_20060324-7_amd64.deb Files: fd4048437609f3a6001f59096205aef7 1069 math extra magnus_20060324-7.dsc a68b9bcc65b90dc5d2db9c556bc7d828 17872 math extra magnus_20060324-7.diff.gz 3556b0276aa9fbe907e37cbddc6d35bc 3681572 math extra magnus_20060324-7_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk7cmZgACgkQtzWmSeC6BME60ACfftrl038SbHdOXTJkQGi/DGam goIAni909lTMGDKHCQ6i53lN8uJDRg9A =u4xm -END PGP SIGNATURE- ---End Message---
Processed: your mail
Processing commands for cont...@bugs.debian.org: block 649339 by 650025 Bug #649339 [release.debian.org] vtk 5.8 transition Was blocked by: 650936 650935 Added blocking bug(s) of 649339: 650025 thanks Stopping processing here. Please contact me if you need assistance. -- 649339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: unblock 649339 by 650935 Bug #649339 [release.debian.org] vtk 5.8 transition Was blocked by: 650936 650025 650935 Removed blocking bug(s) of 649339: 650935 thanks Stopping processing here. Please contact me if you need assistance. -- 649339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649536: fixed, but wrongly, in splix 2.0.0+svn299-2
reopen 649536 retitle 649536 printer-driver-splix: ppd-updater installed in wrong directory thanks Hi Luca, unfortunately, I noticed that the PPD-updater snippet is installed in /usr/share/ppd-updaters/ and not in /usr/share/cups/ppd-updaters/. I plea guilty as this mistake was already in the patch I proposed you in #647536, but this should be fixed anyway, hence I'm re-opening this bug. Cheers, -- OdyX -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#649536: fixed, but wrongly, in splix 2.0.0+svn299-2
Processing commands for cont...@bugs.debian.org:
reopen 649536
Bug #649536 {Done: Luca Niccoli lultimou...@gmail.com} [printer-driver-splix]
printer-driver-splix: ppd-updater trigger is installed in wrong package
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
retitle 649536 printer-driver-splix: ppd-updater installed in wrong directory
Bug #649536 [printer-driver-splix] printer-driver-splix: ppd-updater trigger is
installed in wrong package
Changed Bug title to 'printer-driver-splix: ppd-updater installed in wrong
directory' from 'printer-driver-splix: ppd-updater trigger is installed in
wrong package'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
649536: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Fix uninstallable problem
Processing commands for cont...@bugs.debian.org: # bug renders package uninstallable severity 651031 grave Bug #651031 [pidentd] Installation error: update-rc.d: error: expected runlevel [0-9S] (did you forget . ?) Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 651031: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651031: Fix uninstallable problem
On Mon, 2011-12-05 at 11:41 +0100, Martin Stigge wrote: Options after -- are passed to update-rc.d which expects the pattern (start|stop) runlevel ., violated by stop 20 .. Uh, (start|stop) NN runlevel(s) . of course. Martin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 649536 in 2.0.0+svn299-2
Processing commands for cont...@bugs.debian.org: found 649536 2.0.0+svn299-2 Bug #649536 [printer-driver-splix] printer-driver-splix: ppd-updater installed in wrong directory Bug Marked as found in versions splix/2.0.0+svn299-2. thanks Stopping processing here. Please contact me if you need assistance. -- 649536: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650995: causes dependency loop in boot sequence (according to insserv)
[Luk Claes] That does not give any clues. The only difference in this regard is the addition of $remote_fs to Required-Start and Required-Stop. Removing these, makes it work like before. Perhaps looking at the dotty graph generated using '/usr/share/insserv/check-initd-order -g' can give you an idea why? The script '/usr/share/insserv/make-testsuite' can be used to create a test suite to reproduce the problem, but I guess it is not really interesting in this case. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650681: fuse: i386-linux-gnu/libfuse.so points to /lib/libfuse and not libfuse in the same directory
tag 650681 pending thanks uploading in late evening.. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: fuse: i386-linux-gnu/libfuse.so points to /lib/libfuse and not libfuse in the same directory
Processing commands for cont...@bugs.debian.org: tag 650681 pending Bug #650681 [libfuse-dev] fuse: i386-linux-gnu/libfuse.so points to /lib/libfuse and not libfuse in the same directory Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 650681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651058: pidgin-libnotify: gnome-shell crashes or restarts on notifications
Package: pidgin-libnotify Version: 0.14-6 Severity: grave Justification: renders package unusable Dear Maintainer, When the plugin is active in pidgin and you receive a message, instead of the regular notification you would receive about it gnome-shell crashes and takes down your whole session and X with it. The only clue about it I could find was in .xsession-errors: Cogl:ERROR:./cogl-bitmap.c:401:_cogl_bitmap_map: assertion failed: (!bitmap-mapped) x-session-manager[30464]: WARNING: Application 'gnome-shell.desktop' killed by signal On other kind of notifications (users logging in and out), gnome-shell just restarts. I couldn't find any message or error in any log that would be related to this. This is duplicated on amd64 arch too. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (100, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pidgin-libnotify depends on: ii libatk1.0-0 2.2.0-2 ii libc6 2.13-21 ii libcairo2 1.10.2-6.1 ii libfontconfig1 2.8.0-3 ii libfreetype62.4.8-1 ii libgdk-pixbuf2.0-0 2.24.0-1 ii libglib2.0-02.30.2-4 ii libgtk2.0-0 2.24.8-2 ii libnotify4 0.7.4-1 ii libpango1.0-0 1.29.4-2 ii pidgin 2.10.0-1+b2 pidgin-libnotify recommends no packages. pidgin-libnotify suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651061: vice: crashes with Signal 4 on amd64.
Package: vice Version: 2.3.dfsg-2 Severity: grave Justification: renders package unusable I just upgraded to vice 2.3.dfsg-2 and every emulator in the suite now crashes before displaying any window. The following is a sample output from x64: $ x64 [begin paste] Reading configuration file `/home/eregil/.vice/vicerc'. Loading palette `/usr/lib/vice/C64/vice.vpl'. Loading palette `/usr/lib/vice/C64/vice.vpl'. *** VICE Version 2.3 *** OS compiled for: Linux GUI compiled for: GTK+ CPU compiled for: AMD64/x86_64 Compiler used: GCC-4.6.2 Current OS: not yet implemented Current CPU: Unknown CPU Welcome to x64, the free portable C64 Emulator. Current VICE team members: D. Lem, A. Matthies, M. Pottendorfer, S. Trikaliotis, M. van den Heuvel, C. Vogelgsang, F. Gennari, D. Kahlin, A. Lankila, Groepaz, I. Korb, E. Smith, O. Seibert. This is free software with ABSOLUTELY NO WARRANTY. See the About VICE command for more info. XRandR: XRandR reports current display: 1280x1024@60 Loading system file `/usr/lib/vice/C64/kernal'. C64MEM: Kernal rev #3. Loading system file `/usr/lib/vice/C64/basic'. Loading system file `/usr/lib/vice/C64/chargen'. Loading system file `/usr/lib/vice/PRINTER/mps803'. Palette: Loading palette `/usr/lib/vice/PRINTER/mps803.vpl'. Received signal 4. Exiting... [end paste] I experience this on KDE 4 as well as Gnome 3 and XFCE 4. Version 2.3.dfsg-1 worked fine. Rebuilding the package on my own box also seems to fix the problem, which may (or may not) be limited to the uploaded amd64 binary (at this time I don't have a testing/unstable debian installed on platforms other than amd64). If you need any further information please feel free to ask. Best regards. Pier Luigi Pau -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vice depends on: ii dpkg1.16.1.2 ii install-info4.13a.dfsg.1-8 ii libasound2 1.0.24.1-4 ii libatk1.0-0 2.2.0-2 ii libc6 2.13-21 ii libcairo2 1.10.2-6.1 ii libfontconfig1 2.8.0-3 ii libfreetype62.4.8-1 ii libgcc1 1:4.6.2-5 ii libgdk-pixbuf2.0-0 2.24.0-1 ii libglib2.0-02.30.2-4 ii libgtk2.0-0 2.24.8-2 ii libieee1284-3 0.2.11-10 ii libjpeg88c-2 ii libpango1.0-0 1.29.4-2 ii libpcap0.8 1.1.1-10 ii libpng12-0 1.2.46-3 ii libreadline66.2-8 ii libstdc++6 4.6.2-5 ii libx11-62:1.4.4-4 ii libxrandr2 2:1.3.2-2 ii libxxf86vm1 1:1.1.1-2 ii zlib1g 1:1.2.3.4.dfsg-3 vice recommends no packages. vice suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#647992: Possible cause (unlikely)
Briefly: Because Debian is using kernel 3.1.x and has CONFIG_SECCOMP turned on, all attempts to call time() with the seccomp sandbox active and using a glibc old enough that it uses the vsyscall page for such calls will 'Aw, snap!' the renderer: http://code.google.com/p/chromium/issues/detail?id=104084 http://code.google.com/p/seccompsandbox/issues/detail?id=17 This is fixed, but very recently... but this is likely moot since Debian doesn't turn on the seccomp sandbox. When you do, take note... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651064: regdatasmooth: Invalid call to fminunc.
Package: octave-data-smoothing Version: 1.2.0-3 Severity: grave Tags: patch Justification: renders package unusable regdatasmooth currently fails to run, with error: Invalid call to fminunc. I can reproduce the error in Demonstration 1 from http://octave.sourceforge.net/data-smoothing/function/regdatasmooth.html, but it also occurs for a trival example such as regdatasmooth( [1:5], [1:5] ) Since regdatasmooth is the chief function in octave-data-smoothing, this bug essentially renders the package unusable. But happily, upstream seems to be already on to it, it appears to be fixed in the latest version 1.2.3. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages octave-data-smoothing depends on: ii octave-optim 1.0.16-1 ii octave3.2 3.2.4-12 octave-data-smoothing recommends no packages. octave-data-smoothing suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650958: [Pkg-samba-maint] Bug#650958: Bug#650958: samba INTERNAL ERROR: Signal 11 - PANIC - BACKTRACE: 16 stack frames
Quoting Christian PERRIER (bubu...@debian.org): Quoting Tiago Caxias (tcx.talie...@gmail.com): Package: samba Version: 2:3.6.1-3 Severity: grave Justification: renders package unusable Could you try cleaning out /var/cache/samba/printing?It is likely that a printer TDB cache file has invalid data in it. signature.asc Description: Digital signature
Bug#650995: causes dependency loop in boot sequence (according to insserv)
Quoting Petter Reinholdtsen (p...@hungry.com): [Stefano Zacchiroli] Installation of console-common 0.7.86 has failed in unstable for me with the following insserv error: Since bellini.debian.org stopped having a compiler installed, my archive wide consistency check of the init.d script dependencies have not been operational. I thus lack the ability to guess which of these scripts have a loop. URL: http://lintian.debian.org/~pere/test-20110605.log show no loops, so the problem must have been introduced after this. Looking at the scripts, restorecond seem to be a new one. Could it be the cause of the loop? Do you get any clues from running /usr/share/insserv/check-archive-initd-scripts? On my own system, the problem doesn't only happen for console-common, but for samba(which has to be updated as well), so I indeed suspect that this problem might not be lying in these packages. signature.asc Description: Digital signature
Bug#650995: causes dependency loop in boot sequence (according to insserv)
Quoting Petter Reinholdtsen (p...@hungry.com): [Stefano Zacchiroli] Installation of console-common 0.7.86 has failed in unstable for me with the following insserv error: Since bellini.debian.org stopped having a compiler installed, my archive wide consistency check of the init.d script dependencies have not been operational. I thus lack the ability to guess which of these scripts have a loop. URL: http://lintian.debian.org/~pere/test-20110605.log show no loops, so the problem must have been introduced after this. Looking at the scripts, restorecond seem to be a new one. Could it be the cause of the loop? Do you get any clues from running /usr/share/insserv/check-archive-initd-scripts? Changes in 0.7.86 were supposed to be trivial so that RC bug is a (bad) surprise for me...:-( It is quite likely that I need help to fix this. I'll try to look at the problem tonight but can't really promise anything. Could console-common be a victim of another package problem that was hidden until one of the packages in the loop is updated? signature.asc Description: Digital signature
Bug#650995: causes dependency loop in boot sequence (according to insserv)
Package: console-common Followup-For: Bug #650995 Hi, I am also getting the same error when upgrading console-common to 0.7.86. [Kel Modderman] I would like to know why this change in dependency was made by the console-common maintainers? Perhaps they have tried to fix a lintian error: $ lintian /var/cache/apt/archives/console-common_0.7.85_all.deb W: console-common: debconf-is-not-a-registry usr/sbin/install-keymap W: console-common: debconf-is-not-a-registry usr/share/console/getkmapchoice.pl E: console-common: init.d-script-missing-dependency-on-remote_fs etc/init.d/keymap.sh: required-start This error indicates /usr might be necessary before using /etc/init.d/keymap.sh. This script invokes commands in /usr if console-tools package is installed: [ -x /usr/bin/unicode_start ] || [ -x /bin/unicode_start ] || return [ -x /usr/bin/unicode_stop ] || [ -x /bin/unicode_stop ] || return Note that /bin/unicode_* are available in kbd package, which is used in my installation. So console-tools might have to move /usr/bin/unicode_* to /bin/ to avoid such a dependency loop. Thanks, -- YOSHINO Yoshihito yy.y.ja...@gmail.com -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages console-common depends on: ii console-data 2:1.12-1 ii debconf [debconf-2.0] 1.5.41 ii debianutils4.1 ii kbd1.15.3-7 ii lsb-base 3.2-28 console-common recommends no packages. console-common suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651068: file conflict with cups-pdf prevents upgrade to 1.4.4-7+squeeze1
Package: cups Version: 1.4.4-7+squeeze1 Severity: grave Tags: squeeze I tried to run an apt-get dist-upgrade, but cups doesn't upgrade cleanly because of a conflict with package cups-pdf: joe@tux:~$ sudo apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Starting Starting 2 Done Done The following packages will be upgraded: cups 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 12 not fully installed or removed. Need to get 0 B/2,020 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? Reading changelogs... Done Preconfiguring packages ... (Reading database ... 167164 files and directories currently installed.) Preparing to replace cups 1.4.4-7 (using .../cups_1.4.4-7+squeeze1_i386.deb) ... Stopping Common Unix Printing System: cupsd. Unpacking replacement cups ... dpkg: error processing /var/cache/apt/archives/cups_1.4.4-7+squeeze1_i386.deb (--unpack): trying to overwrite '/etc/cups', which is also in package cups-pdf 2.5.0-16 configured to not write apport reports dpkg-deb: subprocess paste killed by signal (Broken pipe) Starting Common Unix Printing System: cupsdcupsd: Child exited with status 1! Message from syslogd@tux at Dec 5 09:10:18 ... cupsd: Unable to read configuration file '/etc/cups/cupsd.conf' - exiting! .. Errors were encountered while processing: /var/cache/apt/archives/cups_1.4.4-7+squeeze1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) joe@tux:~$ -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cups depends on: ii adduser 3.112+nmu2 add and remove users and groups ii bc 1.06.95-2The GNU bc arbitrary precision cal pn cups-client none (no description available) pn cups-common none (no description available) pn cups-ppdc none (no description available) ii debconf [debconf-2. 1.5.36.1 Debian configuration management sy ii ghostscript 8.71~dfsg2-9 The GPL Ghostscript PostScript/PDF ii libavahi-client30.6.27-2+squeeze1Avahi client library ii libavahi-common30.6.27-2+squeeze1Avahi common library ii libc6 2.11.2-10Embedded GNU C Library: Shared lib pn libcups2none (no description available) pn libcupscgi1 none (no description available) pn libcupsdriver1 none (no description available) pn libcupsimage2 none (no description available) pn libcupsmime1none (no description available) pn libcupsppdc1none (no description available) ii libdbus-1-3 1.2.24-4+squeeze1simple interprocess messaging syst ii libgcc1 1:4.4.5-8GCC support library ii libgnutls26 2.8.6-1 the GNU TLS library - runtime libr ii libgssapi-krb5-21.8.3+dfsg-4squeeze2 MIT Kerberos runtime libraries - k ii libijs-0.35 0.35-7 IJS raster image transport protoco ii libkrb5-3 1.8.3+dfsg-4squeeze2 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.23-7.2 OpenLDAP libraries ii libpam0g1.1.1-6.1+squeeze1 Pluggable Authentication Modules l ii libpaper1 1.1.24 library for handling paper charact ii libpoppler5 0.12.4-1.2 PDF rendering library ii libslp1 1.2.1-7.8OpenSLP libraries ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii libusb-0.1-42:0.1.12-16 userspace USB programming library ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii poppler-utils 0.12.4-1.2 PDF utilitites (based on libpopple ii procps 1:3.2.8-9/proc file system utilities ii ssl-cert1.0.28 simple debconf wrapper for OpenSSL ii ttf-freefont20090104-7 Freefont Serif, Sans and Mono True ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages cups recommends: ii cups-driver-gutenprint 5.2.6-1 printer drivers for CUPS ii foomatic-filters4.0.5-6 OpenPrinting printer support - fil ii ghostscript-cups8.71~dfsg2-9 The GPL Ghostscript PostScript/PDF Versions of packages cups suggests: pn cups-bsd none (no description available) ii cups-pdf 2.5.0-16 PDF printer for CUPS ii
Bug#650995: causes dependency loop in boot sequence (according to insserv)
[Christian PERRIER] On my own system, the problem doesn't only happen for console-common, but for samba(which has to be updated as well), so I indeed suspect that this problem might not be lying in these packages. It would be useful to know which package with init.d scripts you have installed. Please provide the output from dpkg -S /etc/init.d/*|cut -d: -f1|sort -u Given that it is a loop, it is useful to try to idenfity which set of packages need to be installed together for the loop to form. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640583: terraintool: FTBFS: xargs: /usr/lib/jvm/java-6-openjdk/bin/javac: No such file or directory
+++ Miguel de Val-Borro [2011-12-04 14:30 +0100]: tags 640583 patch thanks On Mon, Sep 05, 2011 at 09:34:15PM +0200, Mònica Ramírez Arceda wrote: During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: debian/rules build dh --with javahelper build dh_testdir dh_auto_configure jh_linkjars dh_auto_build jh_build find src -name *.java -and -type f -print0 | xargs -0 /usr/lib/jvm/java-6-openjdk/bin/javac -cp :debian/_jh_build.terraintool -d debian/_jh_build.terraintool -source 1.5 xargs: /usr/lib/jvm/java-6-openjdk/bin/javac: No such file or directory make: *** [build] Error 1 The attached patch fixes the error by removing the definition of the JAVA_HOME variable in rules. Sorry - I didn't spot this till now. I've applied the patch but doing an upload is fruitless until javahelper is fixed. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649842 I'll try and get to the bottom of this. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#554330: diff for NMU
Am Montag, den 05.12.2011, 00:59 +0100 schrieb Johann Felix Soden: The attached patch solves the FTBFS with binutils-gold and waits to be sponsored. Hi, I applied your patch in the git repository and did more cleanup. When I try to build the package with pbuilder, it still fails to build: g++ -m64 -Wl,--as-needed -Wl,-O1 -o esperanza fancyplaylistview.o minimode.o shortcutmanager.o filedialog.o systemtray.o playerbutton.o progressframe.o volumebar.o main.o playerwidget.o progressindicator.o mdns.o playlistview.o serverdialog.o moc_esperanza_plugin.o moc_fancyplaylistview.o moc_filedialog.o moc_mdns.o moc_minimode.o moc_playerbutton.o moc_playerwidget.o moc_playlistview.o moc_progressframe.o moc_progressindicator.o moc_serverdialog.o moc_shortcutmanager.o moc_systemtray.o moc_volumebar.o-L/usr/lib -lxmmsclient -lxmmsclient++ -lboost_signals -lX11 ../dialogs/lastfm/liblastfm.a ../dialogs/medialibdialog/libmedialibdialog.a ../dialogs/streamingdialog/libstreamingdialog.a ../dialogs/firsttimewizard/libfirsttimewizard.a ../dialogs/preferencesdialog/libpreferencesdialog.a ../dialogs/aboutdialog/libaboutdialog.a ../dialogs/xmms2dpreferences/libxmms2dpreferences.a ../dialogs/equalizer/libequalizer.a ../tools/grepshortcutkeydlg/libgrepshortcutkeydlg.a ../tools/globalshortcut/libglobalshortcut.a ../lib/liblib.a ../../data/libdata.a -lQtXml -lQtGui -lQtNetwork -lQtCore -lpthread /usr/bin/ld: ../tools/globalshortcut/libglobalshortcut.a(globalshortcutmanager_x11.o): undefined reference to symbol 'XKeycodeToKeysym' /usr/bin/ld: note: 'XKeycodeToKeysym' is defined in DSO /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libX11.so so try adding it to the linker command line /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libX11.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status Are you interested in maintaining esperanza? -- Benjamin Drung Debian Ubuntu Developer signature.asc Description: This is a digitally signed message part
Processed: severity of 628914 is serious, severity of 621377 is serious, severity of 621460 is serious ...
Processing commands for cont...@bugs.debian.org: severity 628914 serious Bug #628914 [src:postler] Uses obsolete Berkeley DB library version (libdb4.8-dev), update b-d to versionless libdb-dev Severity set to 'serious' from 'important' severity 621377 serious Bug #621377 [clisp] Still uses libdb4.8 Severity set to 'serious' from 'important' severity 621460 serious Bug #621460 [subversion] Still uses libdb4.8 Severity set to 'serious' from 'important' severity 621447 serious Bug #621447 [sendmail] Still uses libdb4.8 Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 621447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621447 628914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628914 621460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621460 621377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639772: marked as done (slrn: FTBFS: checking for the slang library and header files ... no)
Your message dated Mon, 05 Dec 2011 15:10:46 +
with message-id e1rxabq-0007uy...@franck.debian.org
and subject line Bug#639772: fixed in slrn 1.0.0~pre18-1.2
has caused the Debian Bug report #639772,
regarding slrn: FTBFS: checking for the slang library and header files ... no
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
639772: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: slrn
Version: 1.0.0~pre18-1.1
Severity: serious
Justification: FTBFS
Tags: patch
Hi,
slrn FTBFS on latest unstable.
I confirmed on amd64/cowbuilder.
And you can see build log following.
armhf:
http://buildd.debian-ports.org/status/fetch.php?pkg=slrnarch=armhfver=1.0.0%7Epre18-1.1%2Bb2stamp=1314291701
sh4:
http://buildd.debian-ports.org/status/fetch.php?pkg=slrnarch=sh4ver=1.0.0%7Epre18-1.1%2Bb1stamp=1314321508
-
checking for an implementation of va_copy()... yes
checking for an implementation of __va_copy()... yes
checking whether va_lists can be copied by value... no
checking for ncurses5-config... /usr/bin/ncurses5-config
checking for terminfo... yes
checking for the slang library and header files ... no
configure: error: unable to find the slang library and header file slang.h
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
-
I attached full log.
Could you check your packge?
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
slrn_1.0.0~pre18-1.1_amd64.build.gz
Description: GNU Zip compressed data
---End Message---
---BeginMessage---
Source: slrn
Source-Version: 1.0.0~pre18-1.2
We believe that the bug you reported is fixed in the latest version of
slrn, which is due to be installed in the Debian FTP archive:
slrn_1.0.0~pre18-1.2.diff.gz
to main/s/slrn/slrn_1.0.0~pre18-1.2.diff.gz
slrn_1.0.0~pre18-1.2.dsc
to main/s/slrn/slrn_1.0.0~pre18-1.2.dsc
slrn_1.0.0~pre18-1.2_i386.deb
to main/s/slrn/slrn_1.0.0~pre18-1.2_i386.deb
slrnpull_1.0.0~pre18-1.2_i386.deb
to main/s/slrn/slrnpull_1.0.0~pre18-1.2_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 639...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann gre...@debian.org (supplier of updated slrn 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 ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 03 Dec 2011 15:12:43 +0100
Source: slrn
Binary: slrn slrnpull
Architecture: source i386
Version: 1.0.0~pre18-1.2
Distribution: unstable
Urgency: low
Maintainer: Jörg Sommer jo...@alea.gnuu.de
Changed-By: gregor herrmann gre...@debian.org
Description:
slrn - threaded news reader (fast for slow links)
slrnpull - pulls a small newsfeed from an NNTP server
Closes: 607332 639772
Changes:
slrn (1.0.0~pre18-1.2) unstable; urgency=low
.
* Non-maintainer upload.
* Fix FTBFS: checking for the slang library and header files ... no:
tell configure about the multiarched slang lib; build-depend on dpkg-dev
(= 1.16.0). Remove rpath that gets introduced by the multiarch path.
(Closes: #639772)
* Fix cleanscore breaks with perl 5.12: new patch
cleanscore-prototypes.dpatch.
(Closes: #607332)
Checksums-Sha1:
1d4aaa9722b3099bd978f523cec864d9624e160c 2056 slrn_1.0.0~pre18-1.2.dsc
903023cb4c024b7901b125701c869d943f6f299b 53987 slrn_1.0.0~pre18-1.2.diff.gz
166ae71bb30d437e8dc8eaaa5780c32babf5c8b3 804362 slrn_1.0.0~pre18-1.2_i386.deb
a79270ccbeb583786d10ce2eb48d779ab4570339 143930
slrnpull_1.0.0~pre18-1.2_i386.deb
Checksums-Sha256:
7e08755f4b4df501fb3ce08a52f6aad75a64729c213dddcf11ae9cb6296234aa 2056
slrn_1.0.0~pre18-1.2.dsc
bc8ddcbcc2511917b5f64cfc72a1b4fcaf8b122cf386fd93ae1e129f25cd9816 53987
slrn_1.0.0~pre18-1.2.diff.gz
04bbd9409fe8a8171d36c6732b98589f80015e69349ec1527ad649417fe47353 804362
slrn_1.0.0~pre18-1.2_i386.deb
e6e1a71b52b21e45deb28c40783181da589f7c75995ffe58d6b243641bd0d854 143930
slrnpull_1.0.0~pre18-1.2_i386.deb
Files:
ae46ce4bddd91d8302bbd1a82832f24e 2056 news optional slrn_1.0.0~pre18-1.2.dsc
9d53e1d57924fd28bc66e8974049ce2b 53987 news optional
slrn_1.0.0~pre18-1.2.diff.gz
Bug#635126: status of ruby 1.9.1 wrt porting
On Sat, Dec 03, 2011 at 01:35:40PM -0500, Lennart Sorensen wrote: On Fri, Dec 02, 2011 at 11:37:34AM +, Hector Oron wrote: Lennart, could you try to rebuild on armhf, we are trying to bootstrap armhf in official main and contrib Debian archive, but build seems to hang: See https://buildd.debian.org/status/fetch.php?pkg=ruby1.9.1arch=armhfver=1.9.3.0-1stamp=1322758500 Now, trying to build with -fno-tree-sra. It appears it failed in TestFiber#test_many_fibers_with_threads as far as I can tell. Strangely the run-test-suites.bash didn't continue after the crash even though it looks like it should have and simply ignored the error. I had to control-c it to getback to a prompt. The system was completely idle at the time too. I tried adding armhf to the list of archs needing -fno-tree-sra, and it made no difference at all. Exact same crash in the same place. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#527407: marked as done (ecasound2.2: Build-Depends on libjack0.100.0-dev)
Your message dated Mon, 05 Dec 2011 15:16:28 + with message-id e1rxahm-0008lh...@franck.debian.org and subject line Bug#650890: Removed package(s) from unstable has caused the Debian Bug report #527407, regarding ecasound2.2: Build-Depends on libjack0.100.0-dev 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 527407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527407 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ecasound2.2 Version: 2.5.2-3 Severity: minor User: pkg-multimedia-maintain...@lists.alioth.debian.org Usertags: drop-versioned-libjack Hi, Your package build-depends upon libjack0.100.0-dev, which will dissappear in an upcoming upload of the Jack Audio Connection Kit. The correct package to depend upon is libjack-dev. Your package will not fail to build once the new jack is uploaded, because libjack-dev Provides libjack0.100.0-dev, and thus you don't need to do an upload just for this, but we would like to drop the Provides at some point. If you could change the build-dependency in a following upload, it would be greatly appreciated. -- Saludos, Felipe Sateler On behalf of the Debian Multimedia Maintainers. ---End Message--- ---BeginMessage--- Version: 2.7.0-1.1+rm Dear submitter, as the package ecasound2.2 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/650890 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) ---End Message---
Bug#650958: [Pkg-samba-maint] Bug#650958: Bug#650958: samba INTERNAL ERROR: Signal 11 - PANIC - BACKTRACE: 16 stack frames
Yes, of course. I'll do it as soon as I'll get home. Just a couple of things: 1 - this happened right after an aptitude full-upgrade 2 - my samba server isn't serving printing services for some months now. My wife switched from windows to mac so I stopped sharing printers in smb.conf and started cups sharing. On Mon, Dec 5, 2011 at 6:59 AM, Christian PERRIER bubu...@debian.orgwrote: Quoting Christian PERRIER (bubu...@debian.org): Quoting Tiago Caxias (tcx.talie...@gmail.com): Package: samba Version: 2:3.6.1-3 Severity: grave Justification: renders package unusable Could you try cleaning out /var/cache/samba/printing?It is likely that a printer TDB cache file has invalid data in it. -- Tiago Caxias
Bug#607267: /usr/bin/scp: fails to notice close() errors
Hi Michal, On Mon, Dec 05, 2011 at 12:41:21AM +0100, Michal Suchanek wrote: Excerpts from Helmut Grohne's message of Sat Dec 03 17:33:04 +0100 2011: Hi, On Sun, Jan 02, 2011 at 03:48:05PM +0100, Michal Suchanek wrote: This same issue also happens with cp(1) from coreutils. I verified that this statement is wrong. It is not. This probably depends on the point of view. From the current context it is not clear what this issue is. Please read the analysis in the latter message. I think we should split this up in two issues: 1) Not checking the return value of close(). This is a very real bug in openssh, but not in coreutils (seem my analysis). 2) Not fsyncing the files before closeing them. It is not the job of cp nor scp to guarantee that any file has reached the disk. So this bug will not be fixed. If it was their job, tools like sync(1) would not exist in the first place. If it was, you could file this bug report against every single package handling files in the archive (except for a handful). Since that would be insane, I simply dropped this request in my previous reply. I should have made this more explicit. Can we now ignore 2) and concentrate on 1)? A quick grep of the openssh source indicates that checking close is overrated. Who needs errors anyway? I want that it works!!1!eleven And for it to work it needs to report errors when they happen. I guess I should have used explicit irony tags here. Unfortunately fixing ssh will not be a small patch. It might be best to simply document the issue in man 1 scp. Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#477751: tackling this bug
Hi Daniel, On Mon, Dec 05, 2011 at 12:05:26AM +0100, Daniel Leidert wrote: My thoughts on this are pretty easy. There are IMO three mechanisms to use: (1) Register the catalog, if it exists (and unregister any registered catalog, if it doesn't exist anymore). So users can remove the package catalog file. (2) Register the catalog only during installation, but not during upgrade. Usually we only add a catalog reference to the super catalog. This is what I proposed. It can be done today with a simple change to debhelper and no changes to sgml-base. (3) Catalog files should be written at build time not during installation. Instead of creating /etc/sgml/package.cat during installation, this should be created during package build. So the user can edit /etc/sgml/package.cat and /etc/sgml/catalog and we preserve these changes. Initially I thought about this as well. The problem with this is that currently /etc/sgml/package.cat is not owned by any package. So by switching a package to this model, each installation would prompt the user for those files. If the user now changes /etc/sgml/package.cat and we need to ship an updated file, he should usually be asked, if he wishes to update the file during installation. IMO we don't need to check, what has been disabled or not. Or does this have any advantages IYO? It works without asking the user questions during upgrade. This applies both to a transitioning period and to the long term when a package.cat changes. I don't really care whether the user is asked on package upgrades after he changes those files. But installations where no user changed those files should definitely not ask the user. So I propose that either you come up with a method to cleanly take over ownership of those configuration files or we use my approach. In any case this bug should be fixed some way or another. Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635126: status of ruby 1.9.1 wrt porting
Hello Lennart, 2011/12/5 Lennart Sorensen lsore...@csclub.uwaterloo.ca: I tried adding armhf to the list of archs needing -fno-tree-sra, and it made no difference at all. Exact same crash in the same place. Yes, that matches my tests. Thanks very much for trying. -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651077: lxc: Invalid veth names
Package: lxc Version: 0.7.5-12 Severity: grave Justification: renders package unusable Dear Maintainer, It seems that LXC uses invalid veth names when launching a new container. If you create two container using virtual Ethernet interfaces, the first one will load fine but with the second one, you will have the following error: # lxc-start -n container -f /srv/lxc/container/config lxc-start: failed to create veth--veth854Hig : File exists lxc-start: failed to create netdev lxc-start: failed to create the network lxc-start: failed to spawn 'container' lxc-start: No such file or directory - failed to remove cgroup '/cgroup/container' It looks like LXC is trying to create an interface named `veth--veth854Hig' but this name is invalid due to the two `-'. A look at ifconfig can confirm that: # ifconfig -a veth- Link encap:Ethernet HWaddr be:86:2f:8a:fe:3b inet6 addr: fe80::bc86:2fff:fe8a:fe3b/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX packets:5291 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2008 (1.9 KiB) TX bytes:537310 (524.7 KiB) So when we launch a second container, it is conflicting with the already created `veth-' interface. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lxc depends on: ii debconf [debconf-2.0] 1.5.41 ii libc6 2.13-21 ii libcap21:2.22-1 Versions of packages lxc recommends: ii debootstrap 1.0.38 ii libcap2-bin 1:2.22-1 Versions of packages lxc suggests: pn lxctl none -- debconf information: lxc/shutdown: stop lxc/directory: /var/lib/lxc lxc/title: lxc/auto: true -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651032: /usr/sbin/rpc.idmapd: rpc.idmapd referring to none existing library
Hello, On 12/05/2011 03:25 AM, Anibal Monsalve Salazar wrote: Hello Steve and Kevin, To fix Debian Bug#649491[1], I moved the .so files to /lib and applied the following patch: --- a/libnfsidmap.c 2010-12-09 04:07:53.0 +1100 +++ b/libnfsidmap.c 2011-12-05 11:23:46.0 +1100 @@ -61,7 +61,7 @@ static struct mapping_plugin **nfs4_plug static struct mapping_plugin **gss_plugins = NULL; #ifndef PATH_PLUGINS -#define PATH_PLUGINS /usr/lib/libnfsidmap +#define PATH_PLUGINS /lib/libnfsidmap #endif #define PLUGIN_INIT_FUNC libnfsidmap_plugin_init [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649491 Why not just use the --with-pluginpath configuration flag? That's how we do it in Fedora... steved. As Michael reported, libnfsidmap is still looking for the plugins in /usr/lib/libnfsidmap. What do I need to change in libnfsidmap to make it find the plugins in /lib/libnfsidmap? Please see Michael's report below. Cheers, Anibal As Michael has reported, libnfsidmap2 is still looking On Mon, Dec 05, 2011 at 08:18:08AM +0100, Michael Rasmussen wrote: Package: nfs-common Version: 1:1.2.5-2+b1 Severity: grave File: /usr/sbin/rpc.idmapd Justification: renders package unusable rpc.idmapd -v rpc.idmapd: libnfsidmap: using domain: midgaard rpc.idmapd: libnfsidmap: Unable to load plugin: /usr/lib/libnfsidmap/nsswitch.so: cannot open shared object file: No such file or directory rpc.idmapd: libnfsidmap: requested translation method, 'nsswitch', is not available rpc.idmapd: Unable to create name to user id mappings. rpc.idmapd is searching for libnfsidmap plugins in the wrong directory so bug #650904 must be reopen since the provided change made to libnfsidmap2 does not make any difference rpc.idmapd still uses /usr/lib/libnfsidmap. -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 172 udp785 ypbind 171 udp785 ypbind 172 tcp786 ypbind 171 tcp786 ypbind -- /etc/default/nfs-common -- NEED_STATD=no STATDOPTS= NEED_IDMAPD=yes NEED_GSSD= -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs Domain = midgaard [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- balder:/home /home nfs4 defaults,proto=tcp,retry=5,hard,intr,async,_netdev,rsize=32768,wsize=32768 0 0 -- /proc/mounts -- rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0 balder:/home/ /home nfs4 rw,relatime,vers=4,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.2.79,minorversion=0,local_lock=none,addr=192.168.2.2 0 0 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages nfs-common depends on: ii adduser 3.113 ii initscripts 2.88dsf-13.13 ii libc6 2.13-21 ii libcap2 1:2.22-1 ii libcomerr2 1.42-1 ii libdevmapper1.02.1 2:1.02.67-2 ii libevent-2.0-5 2.0.16-stable-1 ii libgssapi-krb5-21.10+dfsg~alpha1-6 ii libgssglue1 0.3-3.1 ii libk5crypto31.10+dfsg~alpha1-6 ii libkeyutils11.5.2-2 ii libkrb5-3 1.10+dfsg~alpha1-6 ii libnfsidmap20.24-3 ii libtirpc1 0.2.2-5 ii libwrap07.6.q-21 ii lsb-base3.2-28 ii rpcbind 0.2.0-6 ii ucf 3.0025+nmu2 Versions of packages nfs-common recommends: ii python 2.7.2-9 nfs-common suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607267: /usr/bin/scp: fails to notice close() errors
Excerpts from Helmut Grohne's message of Mon Dec 05 15:54:19 +0100 2011: Hi Michal, On Mon, Dec 05, 2011 at 12:41:21AM +0100, Michal Suchanek wrote: Excerpts from Helmut Grohne's message of Sat Dec 03 17:33:04 +0100 2011: is not clear what this issue is. Please read the analysis in the latter message. I think we should split this up in two issues: 1) Not checking the return value of close(). This is a very real bug in openssh, but not in coreutils (seem my analysis). 2) Not fsyncing the files before closeing them. It is not the job of cp nor scp to guarantee that any file has reached the disk. So this bug will not be fixed. If it was their job, tools like sync(1) would not exist in the first place. If it was, you could file this bug report against every single package handling files in the archive (except for a handful). Since that would be insane, I simply dropped this request in my previous reply. I should have made this more explicit. Can we now ignore 2) and concentrate on 1)? No. If I wanted this semantics I could use shred(1). I want my files saved. Note that this same issue has been found and fixed in dpkg. Thanks Michal -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651077: lxc: Invalid veth names
severity 651077 normal tag 651077 moreinfo thanks On 12/05/2011 04:45 PM, Spack wrote: If you create two container using virtual Ethernet interfaces, the first one will load fine but with the second one, you will have the following error: how did you create the container (which template)? what are the veth.name entries in both of your container configs? -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#651077: lxc: Invalid veth names
Processing commands for cont...@bugs.debian.org: severity 651077 normal Bug #651077 [lxc] lxc: Invalid veth names Severity set to 'normal' from 'grave' tag 651077 moreinfo Bug #651077 [lxc] lxc: Invalid veth names Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 651077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651068: file conflict with cups-pdf prevents upgrade to 1.4.4-7+squeeze1
Could you post the output of: ls -lhd /etc/cups dpkg -L cups-pdf |grep /etc/cups dpkg -L cups |grep /etc/cups Regards, -- Yves-Alexis Perez ANSSI/ACE/LAM -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#641488: marked as done (bup: FTBFS on sparc (bus error in bloom test))
Your message dated Mon, 05 Dec 2011 16:13:07 + with message-id e1rxbab-0002nq...@franck.debian.org and subject line Bug#641488: fixed in bup 0.25~git2011.11.04-1 has caused the Debian Bug report #641488, regarding bup: FTBFS on sparc (bus error in bloom test) 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 641488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bup Version: 0.24b-1.1 Severity: serious Hi, bup FTBFS on sparc: https://buildd.debian.org/status/fetch.php?pkg=buparch=sparcver=0.24b-1.1stamp=1313905299 The failure is reproducible on smetana.d.o. From what I can tell, it crashes in lib/bup/t/tbloom.py:test_bloom, line 18 (b.add_idx(ix)), specifically in the call to bloom_add(). Here's a disassembly of that function, the crash is at 0x111c 1020 bloom_add: 1020: 9d e3 bf 80 save %sp, -128, %sp 1024: 13 00 00 41 sethi %hi(0x10400), %o1 1028: 82 07 bf f8 add %fp, -8, %g1 102c: c2 23 a0 5c st %g1, [ %sp + 0x5c ] 1030: 2f 00 00 48 sethi %hi(0x12000), %l7 1034: 7f ff ff d3 call f80 __sparc_get_pc_thunk.l7 1038: ae 05 e2 9c add %l7, 0x29c, %l7! 1229c __FRAME_END__+0xf0ac 103c: 92 1a 7c d0 xor %o1, -816, %o1 1040: 82 07 bf fc add %fp, -4, %g1 1044: c0 27 bf e8 clr [ %fp + -24 ] 1048: 92 05 c0 09 add %l7, %o1, %o1 104c: 90 10 00 19 mov %i1, %o0 1050: 94 07 bf ec add %fp, -20, %o2 1054: 96 07 bf f4 add %fp, -12, %o3 1058: 98 07 bf e8 add %fp, -24, %o4 105c: c0 27 bf ec clr [ %fp + -20 ] 1060: 9a 07 bf f0 add %fp, -16, %o5 1064: c0 77 bf f0 clrx [ %fp + -16 ] 1068: b0 10 20 00 clr %i0 106c: c0 77 bf f8 clrx [ %fp + -8 ] 1070: 40 00 48 ed call 13424 PyArg_ParseTuple@plt 1074: c2 23 a0 60 st %g1, [ %sp + 0x60 ] 1078: 80 a2 20 00 cmp %o0, 0 107c: 02 40 00 5d be,pn %icc, 11f0 bloom_add+0x1d0 1080: c2 07 bf f8 ld [ %fp + -8 ], %g1 1084: 86 10 20 01 mov 1, %g3 1088: c4 07 bf f4 ld [ %fp + -12 ], %g2 108c: 87 28 c0 01 sll %g3, %g1, %g3 1090: 86 00 e0 10 add %g3, 0x10, %g3 1094: 80 a0 c0 02 cmp %g3, %g2 1098: 14 40 00 56 bg,pn %icc, 11f0 bloom_add+0x1d0 109c: d6 07 bf f0 ld [ %fp + -16 ], %o3 10a0: 13 19 99 99 sethi %hi(0x6400), %o1 10a4: 92 12 62 67 or %o1, 0x267, %o1 ! 6667 _end+0x6665309f 10a8: 80 5a c0 09 smul %o3, %o1, %g0 10ac: 93 40 00 00 rd %y, %o1 10b0: 85 3a e0 1f sra %o3, 0x1f, %g2 10b4: 93 3a 60 03 sra %o1, 3, %o1 10b8: 92 22 40 02 sub %o1, %g2, %o1 10bc: 87 2a 60 02 sll %o1, 2, %g3 10c0: 85 2a 60 04 sll %o1, 4, %g2 10c4: 84 00 c0 02 add %g3, %g2, %g2 10c8: 84 a2 c0 02 subcc %o3, %g2, %g2 10cc: 12 40 00 49 bne,pn %icc, 11f0 bloom_add+0x1d0 10d0: c6 07 bf fc ld [ %fp + -4 ], %g3 10d4: 80 a0 e0 05 cmp %g3, 5 10d8: 02 40 00 48 be,pn %icc, 11f8 bloom_add+0x1d8 10dc: b0 10 00 02 mov %g2, %i0 10e0: 80 a0 e0 04 cmp %g3, 4 10e4: 12 40 00 43 bne,pn %icc, 11f0 bloom_add+0x1d0 10e8: 80 a0 60 25 cmp %g1, 0x25 10ec: 14 40 00 41 bg,pn %icc, 11f0 bloom_add+0x1d0 10f0: c4 07 bf e8 ld [ %fp + -24 ], %g2 10f4: 96 00 80 0b add %g2, %o3, %o3 10f8: 80 a0 80 0b cmp %g2, %o3 10fc: 1a 40 00 38 bcc,pn %icc, 11dc bloom_add+0x1bc 1100: 9e 10 20 01 mov 1, %o7 1104: b0 10 20 28 mov 0x28, %i0 1108: a0 10 20 25 mov 0x25, %l0 110c: a2 10 20 14 mov 0x14, %l1 1110: 10 68 00 03 b %xcc, 111c bloom_add+0xfc 1114: a4 10 00 0b mov %o3, %l2 1118: c2 07 bf f8 ld [ %fp + -8 ], %g1 111c: c6 00 80 00 ld [ %g2 ], %g3 1120: b8 26 00 01 sub %i0, %g1, %i4 1124: b2 24 00 01 sub %l0, %g1, %i1 1128: c4 08 a0 04 ldub [ %g2 + 4 ], %g2 112c: 9a 38 00 1c xnor %g0, %i4, %o5 1130: 98 8f 20 20 andcc %i4, 0x20, %o4 1134:
Bug#641637: marked as done (bup: build-dependency (pandoc) not available on mipsel/s390)
Your message dated Mon, 05 Dec 2011 16:13:07 + with message-id e1rxbab-0002nw...@franck.debian.org and subject line Bug#641637: fixed in bup 0.25~git2011.11.04-1 has caused the Debian Bug report #641637, regarding bup: build-dependency (pandoc) not available on mipsel/s390 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 641637: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bup Version: 0.24b-1.1 Severity: serious Tags: patch Hi, pandoc was removed from the archive on some archs, which means bup is now unbuildable on mipsel and s390. Worked around with: --- debian/control.old 2011-09-14 21:49:17.0 +0200 +++ debian/control 2011-09-14 21:49:57.0 +0200 @@ -2,7 +2,8 @@ Section: admin Priority: extra Maintainer: Jon Dowland j...@debian.org -Build-Depends: debhelper (= 7.0.50~), pandoc, python-dev, python-support, +# pandoc is not available on all archs. silly, but there you go. +Build-Depends: debhelper (= 7.0.50~), pandoc [!ia64 !mipsel !s390 !hurd-i386], python-dev, python-support, git (= 1:1.7.0.4-2) | git-core Standards-Version: 3.9.2 Homepage: http://github.com/apenwarr/bup The other option is removing bup on those archs as well. Cheers, Julien ---End Message--- ---BeginMessage--- Source: bup Source-Version: 0.25~git2011.11.04-1 We believe that the bug you reported is fixed in the latest version of bup, which is due to be installed in the Debian FTP archive: bup_0.25~git2011.11.04-1.debian.tar.gz to main/b/bup/bup_0.25~git2011.11.04-1.debian.tar.gz bup_0.25~git2011.11.04-1.dsc to main/b/bup/bup_0.25~git2011.11.04-1.dsc bup_0.25~git2011.11.04-1_i386.deb to main/b/bup/bup_0.25~git2011.11.04-1_i386.deb bup_0.25~git2011.11.04.orig.tar.gz to main/b/bup/bup_0.25~git2011.11.04.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 641...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jon Dowland j...@debian.org (supplier of updated bup 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 05 Dec 2011 15:44:38 + Source: bup Binary: bup Architecture: source i386 Version: 0.25~git2011.11.04-1 Distribution: unstable Urgency: low Maintainer: Jon Dowland j...@debian.org Changed-By: Jon Dowland j...@debian.org Description: bup- highly efficient file backup system based on git Closes: 641488 641637 643060 649351 Changes: bup (0.25~git2011.11.04-1) unstable; urgency=low . [ Teemu Ikonen ] * New upstream version. * Add a proper patch 'no-werror' for the previous NMU, fixing FTBFS (closes: #643060). * Refresh patches 'mangle-version' and 'excise-tornado' to work with the new upstream version. * rules: - override dh_auto_configure: Call ./configure without arguments. - override dh_auto_clean: Remove files generated by configure. . [ Jon Dowland ] * We've merged upstream commit 8953dc8 (a couple ahead of bup-0.25-rc1) * Acknowledge NMU. Thanks Julien Cristau! * Don't use pandoc on architectures where it's missing. Thanks Julien Cristau. Closes: #641637. * New package should fix python dependency. Closes: #649351. * Fix an unaligned-access problem which caused FTBFS on SPARC. Thanks once again Julien Cristau. Closes: #641488. Checksums-Sha1: 160a6a5195f829c175dc70c4ceca46299b0a99f5 1349 bup_0.25~git2011.11.04-1.dsc e77da9a2cba5604ce6f7b369379eb2621d1f73f5 357592 bup_0.25~git2011.11.04.orig.tar.gz da63a547b261b925af2aa0cf4cdc90da90609b33 4349 bup_0.25~git2011.11.04-1.debian.tar.gz debe6839b615cc2b8e54008d920d7bd550989b42 160722 bup_0.25~git2011.11.04-1_i386.deb Checksums-Sha256: 7ea73ff18e47601b0d596c4da65fd5797b389e544236c4706e2065b7125077b2 1349 bup_0.25~git2011.11.04-1.dsc a40de6e414fdbb61b2913faabc504e8e4958a786c8d377842be1bd84e5c8a5e5 357592 bup_0.25~git2011.11.04.orig.tar.gz ed990af7856768f2e27ad745d1848f4373a8f2c53a17a1d72a424e5e1a5d5f37 4349 bup_0.25~git2011.11.04-1.debian.tar.gz 9b042d7340c7b6cff6e3af599d474208079edf1d04d61b5fab70645cd0020545 160722 bup_0.25~git2011.11.04-1_i386.deb Files: 0aaa868e1e2cf4d639e4e4370debc518 1349 admin extra
Bug#649351: marked as done (uninstallable due to broken dependencies)
Your message dated Mon, 05 Dec 2011 16:13:07 + with message-id e1rxbab-0002ng...@franck.debian.org and subject line Bug#649351: fixed in bup 0.25~git2011.11.04-1 has caused the Debian Bug report #649351, regarding uninstallable due to broken dependencies 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 649351: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bup Version: 0.24b-1.1 Severity: serious Hi, bup has been in the above state since Python 2.6 - 2.7 transition as the default python version in unstable. Please, could we fix its dependencies to python2.6 package or make sure it works with Python 2.7 and in turn make it depend on python = 2.7. Thank you, Raf -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: powerpc (ppc) Kernel: Linux 3.0.0-2-powerpc Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bup depends on: ii git [git-core] 1:1.7.7.3-1 ii git-core1:1.7.7.3-1 ii libc6 2.13-21 ii python 2.7.2-9 ii python-fuse 2:0.2.1-7 ii python-support 1.0.14 ii python-tornado 2.1.0-1 Versions of packages bup recommends: ii par2 0.4-11 bup suggests no packages. ---End Message--- ---BeginMessage--- Source: bup Source-Version: 0.25~git2011.11.04-1 We believe that the bug you reported is fixed in the latest version of bup, which is due to be installed in the Debian FTP archive: bup_0.25~git2011.11.04-1.debian.tar.gz to main/b/bup/bup_0.25~git2011.11.04-1.debian.tar.gz bup_0.25~git2011.11.04-1.dsc to main/b/bup/bup_0.25~git2011.11.04-1.dsc bup_0.25~git2011.11.04-1_i386.deb to main/b/bup/bup_0.25~git2011.11.04-1_i386.deb bup_0.25~git2011.11.04.orig.tar.gz to main/b/bup/bup_0.25~git2011.11.04.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 649...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jon Dowland j...@debian.org (supplier of updated bup 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 05 Dec 2011 15:44:38 + Source: bup Binary: bup Architecture: source i386 Version: 0.25~git2011.11.04-1 Distribution: unstable Urgency: low Maintainer: Jon Dowland j...@debian.org Changed-By: Jon Dowland j...@debian.org Description: bup- highly efficient file backup system based on git Closes: 641488 641637 643060 649351 Changes: bup (0.25~git2011.11.04-1) unstable; urgency=low . [ Teemu Ikonen ] * New upstream version. * Add a proper patch 'no-werror' for the previous NMU, fixing FTBFS (closes: #643060). * Refresh patches 'mangle-version' and 'excise-tornado' to work with the new upstream version. * rules: - override dh_auto_configure: Call ./configure without arguments. - override dh_auto_clean: Remove files generated by configure. . [ Jon Dowland ] * We've merged upstream commit 8953dc8 (a couple ahead of bup-0.25-rc1) * Acknowledge NMU. Thanks Julien Cristau! * Don't use pandoc on architectures where it's missing. Thanks Julien Cristau. Closes: #641637. * New package should fix python dependency. Closes: #649351. * Fix an unaligned-access problem which caused FTBFS on SPARC. Thanks once again Julien Cristau. Closes: #641488. Checksums-Sha1: 160a6a5195f829c175dc70c4ceca46299b0a99f5 1349 bup_0.25~git2011.11.04-1.dsc e77da9a2cba5604ce6f7b369379eb2621d1f73f5 357592 bup_0.25~git2011.11.04.orig.tar.gz da63a547b261b925af2aa0cf4cdc90da90609b33 4349 bup_0.25~git2011.11.04-1.debian.tar.gz debe6839b615cc2b8e54008d920d7bd550989b42 160722 bup_0.25~git2011.11.04-1_i386.deb Checksums-Sha256: 7ea73ff18e47601b0d596c4da65fd5797b389e544236c4706e2065b7125077b2 1349 bup_0.25~git2011.11.04-1.dsc a40de6e414fdbb61b2913faabc504e8e4958a786c8d377842be1bd84e5c8a5e5 357592 bup_0.25~git2011.11.04.orig.tar.gz ed990af7856768f2e27ad745d1848f4373a8f2c53a17a1d72a424e5e1a5d5f37 4349 bup_0.25~git2011.11.04-1.debian.tar.gz
Bug#477751: tackling this bug
Helmut Grohne wrote: Good. This would also necessitate a versioned dependency on sgml-base. Yes, easy since it already uses misc:Depends. Do you want a diff for debhelper? Would be appreciated. -- see shy jo signature.asc Description: Digital signature
Bug#651081: doxygen: endless loop while building documentation
Package: doxygen Version: 1.7.6-1 Severity: grave doxygen 1.7.6-1 fails to build documentation of various packages, and goes into an endless loop, wasting the build power of the build daemons. Downgrading to 1.7.4-4 fixes the issue. Some failing logs: - https://buildd.debian.org/status/fetch.php?pkg=globus-gsi-proxy-corearch=s390xver=4.7-3stamp=1323079572 - https://buildd.debian.org/status/fetch.php?pkg=libjsoncpparch=powerpcver=0.6.0%7Erc2-2stamp=1323081887 - https://buildd.debian.org/status/fetch.php?pkg=libjsoncpparch=sparcver=0.6.0%7Erc2-2stamp=1323075800 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages doxygen depends on: ii libc6 2.13-21 ii libgcc1 1:4.6.2-5 ii libstdc++6 4.6.2-5 Versions of packages doxygen recommends: ii doxygen-latex 1.7.6-1 Versions of packages doxygen suggests: ii doxygen-doc none ii doxygen-gui none ii graphviz 2.26.3-8+b1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639636: nodejs: FTBFS/armel - testsuite fails
Thanks to the abel guest access i got, libv8 builds and pass tests on armel and
armhf.
I'm still having *one* test failing, if anyone has an idea about why :
var f = new Buffer('über', 'ucs2');
assert.deepEqual(f, new Buffer([252, 0, 98, 0, 101, 0, 114, 0]));
Giving this result :
https://buildd.debian.org/status/fetch.php?pkg=nodejsarch=armelver=0.4.12-2stamp=1323100281file=log
Couldn't be linked to some wrong endianness assumption ?
Jérémy.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650552: [Pkg-javascript-devel] Bug#650552: node-expat: FTBFS: EBADF, Bad file descriptor '/usr/lib/package.json'
On Mon, 5 Dec 2011 15:37:04 +0700, Jonas Smedegaard wrote: On 11-12-05 at 09:24am, Jérémy Lal wrote: This problem is caused by the fact you're building with latest libv8-dev, but nodejs 0.4 wasn't. I'll upload a nodejs 0.4 built against libv8 3.5 later today. Hmm - I suspect this means nodejs-dev should then depend not only on libv8-dev equal-or-larger than current but also on libv8-dev lower than current+1. Not sure about the exact syntax, but believe it is used several other packages as well... I use that same kind of dependency with josm and josm-plugins. Depends: josm (= 0.0.svn4487) Breaks: josm (= 0.0.svn4488) (and the same with Build-Depends/Build-Conflicts) Sure, each time I upload a new josm, josm-plugins becomes uninstallable and gets an RC, but it's the only way to keep things consistent. (and yes, it's currently uninstallable just for that reason) My 0.02€, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature
Bug#650552: [Pkg-javascript-devel] Bug#650552: node-expat: FTBFS: EBADF, Bad file descriptor '/usr/lib/package.json'
On 05/12/2011 17:53, David Paleino wrote: On Mon, 5 Dec 2011 15:37:04 +0700, Jonas Smedegaard wrote: On 11-12-05 at 09:24am, Jérémy Lal wrote: This problem is caused by the fact you're building with latest libv8-dev, but nodejs 0.4 wasn't. I'll upload a nodejs 0.4 built against libv8 3.5 later today. Hmm - I suspect this means nodejs-dev should then depend not only on libv8-dev equal-or-larger than current but also on libv8-dev lower than current+1. Not sure about the exact syntax, but believe it is used several other packages as well... I use that same kind of dependency with josm and josm-plugins. Depends: josm (= 0.0.svn4487) Breaks: josm (= 0.0.svn4488) I just used : libv8-dev (= 3.5.10.24), libv8-dev ( 3.6) Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607267: /usr/bin/scp: fails to notice close() errors
Hi Michal, On Mon, Dec 05, 2011 at 05:03:25PM +0100, Michal Suchanek wrote: Excerpts from Helmut Grohne's message of Mon Dec 05 15:54:19 +0100 2011: Can we now ignore 2) and concentrate on 1)? No. If I wanted this semantics I could use shred(1). Please report a separate bug about not using fsync then. (or clone this bug) They can be fixed independently. I want my files saved. Honestly. You seem to have a rather different view on this issue than the rest of the world (otherwise it would have been reported way earlier). As for me I really do *not* want fsync here. For instance when I use a slow usb storage device, I really want cp to finish before the copied stuff is written to permanent storage. So even I would assume that the fsync issue is just wontfix (even though I am not the openssh maintainer). Note that this same issue has been found and fixed in dpkg. This is good and all. But in general tools simply do not provide fsync semantics and people actually expect that now. When firefox tried to introduce fsync, it was disabled for performance reasons again. If you need it, go sync after you copy. (Or write patches.) Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649491: libnfsidmap2: still happens with 0.24-3
Package: libnfsidmap2 Version: 0.24-3 Followup-For: Bug #649491 I get the exact bug with 0.24-3 . -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnfsidmap2 depends on: ii libc6 2.13-21 ii libldap-2.4-2 2.4.25-4+b1 libnfsidmap2 recommends no packages. libnfsidmap2 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622051: isakmpd: FTBFS: (.text+0x4f): undefined reference to `inflateEnd'
user debian-d...@lists.debian.org
usertags 622051 multiarch
thanks
Here's one more patch, fixing problem with multiarch library locations.
It should be used with the following modification to debian/rules.
diff -Nru isakmpd-20041012/debian/rules isakmpd-20041012/debian/rules
--- isakmpd-20041012/debian/rules 2010-06-11 15:29:56.0 +
+++ isakmpd-20041012/debian/rules 2011-08-20 09:02:33.0 +
@@ -2,6 +2,8 @@
UPSTREAM_VERSION ?=20041012
b := $(CURDIR)/debian/isakmpd
+DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
+export MULTIARCHLIB := /usr/lib/$(DEB_HOST_MULTIARCH)
%:
dh $@
Description: Instead of hardcoded location of libraries, use the value
provided from debian/rules.
Author: Ilya Barygin bary...@gmail.com
--- isakmpd-20041012.orig/sysdep/linux/GNUmakefile.sysdep
+++ isakmpd-20041012/sysdep/linux/GNUmakefile.sysdep
@@ -25,8 +25,8 @@
# THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
-LIBGMP:= /usr/lib/libgmp.a
-LIBCRYPTO:= /usr/lib/libcrypto.a
+LIBGMP:= ${MULTIARCHLIB}/libgmp.a
+LIBCRYPTO:= ${MULTIARCHLIB}/libcrypto.a
LIBSYSDEPDIR:= ${.CURDIR}/sysdep/common/libsysdep
LIBSYSDEP:= ${LIBSYSDEPDIR}/libsysdep.a
Bug#651087: FTBFS: dh_install: gtk3-im-libthai missing files (usr/lib/gtk-3.0/*/immodules/*.so), aborting
Package: gtk-im-libthai Version: 0.2.1-1 Severity: serious Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: ubuntu-patch origin-ubuntu precise Hi there gtk-im-libthai failed to build on armhf, and it would fail to build on other architectures too as gtk+3.0 now uses multiarch pathnames for immodules. Please find a trivial patch attached. Thanks! -- Loïc Minier diff -Nru gtk-im-libthai-0.2.1/debian/changelog gtk-im-libthai-0.2.1/debian/changelog --- gtk-im-libthai-0.2.1/debian/changelog 2011-11-20 06:02:44.0 +0100 +++ gtk-im-libthai-0.2.1/debian/changelog 2011-12-05 18:43:08.0 +0100 @@ -1,3 +1,9 @@ +gtk-im-libthai (0.2.1-1ubuntu1) precise; urgency=low + + * Use Gtk+ multiarch pathnames for gtk+-3.0 immodules. + + -- Loïc Minier loic.min...@ubuntu.com Mon, 05 Dec 2011 18:42:57 +0100 + gtk-im-libthai (0.2.1-1) unstable; urgency=low * New upstream release diff -Nru gtk-im-libthai-0.2.1/debian/gtk3-im-libthai.install gtk-im-libthai-0.2.1/debian/gtk3-im-libthai.install --- gtk-im-libthai-0.2.1/debian/gtk3-im-libthai.install 2011-11-20 04:12:47.0 +0100 +++ gtk-im-libthai-0.2.1/debian/gtk3-im-libthai.install 2011-12-05 18:42:39.0 +0100 @@ -1,2 +1,2 @@ -usr/lib/gtk-3.0/*/immodules/*.so +usr/lib/*/gtk-3.0/*/immodules/*.so debian/im-switch/th-gtk3-im-libthaietc/X11/xinit/xinput.d
Bug#650995: causes dependency loop in boot sequence (according to insserv)
[Petter Reinholdtsen] Given that it is a loop, it is useful to try to idenfity which set of packages need to be installed together for the loop to form. I finally had a chance to have a look by creating a chroot. The problem can be reproduced using a simple debootstrap and then installing console-common. The loop is between the keymap.sh script in console-common and the checkroot.sh script in initscripts. checkroot have a soft start dependency on keymap provided by keymap.sh, and keymap.sh depend indirectly on checkroot via the $remote_fs virtual facility. The reason checkroot depend on keymap is because it believe it will be used to load the correct console keymap, and this need to be done before checkroot to ensure the root password can be typed using the normal keyboard layout if fsck fail and sulogin ask for the root password before continuing the rescue boot. In short, keymap.sh can't depend on $remote_fs before checkroot is changed to drop its dependency on it (or it can change its provide string to something else than keymap, but that is probably a bad idea). -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648202: FTBFS: qemu-user-static
serverity 648202 important retitle 648202 FTBFS with binutils-gold thanks On Wed, Nov 09, 2011 at 12:17:02PM -0300, Gerardo Esteban Malazdrewicz wrote: -- /usr/bin/make -C /home/gerardo/apt-src/qemu-0.15.1+dfsg/user-static-build make[1]: Entering directory `/home/gerardo/apt-src/qemu-0.15.1+dfsg/user-static-build' make[2]: Nothing to be done for `all'. LINK i386-linux-user/qemu-i386 /usr/bin/ld.gold.real: error: cannot find -lnss3 /usr/bin/ld.gold.real: error: cannot find -lnssutil3 /usr/bin/ld.gold.real: error: cannot find -lsmime3 /usr/bin/ld.gold.real: error: cannot find -lssl3 collect2: ld returned 1 exit status make[2]: *** [qemu-i386] Error 1 make[1]: *** [subdir-i386-linux-user] Error 2 make[1]: Leaving directory `/home/gerardo/apt-src/qemu-0.15.1+dfsg/user-static-build' make: *** [build-stamp] Error 2 --- it looks like you were building with binutils-gold, and i cannot reproduce that with the standard binutils. lowering the severity. newer versions also built on the standard buildd infrastructure: https://buildd.debian.org/qemu i wasn't able to get it to successfully build with binutils-gold either, although not for the same reason; it seems to use considerably more disk space. live well, vagrant -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650995: Downgrade solves for me as well
I can confirm that downgrading to console-common_0.7.85_all.deb fixes the problem for me as well. Here's the requested list: $ dpkg -S /etc/init.d/*|cut -d: -f1|sort -u dpkg-query: no path found matching pattern /etc/init.d/lastfmsubmitd~. dpkg-query: no path found matching pattern /etc/init.d/lastmp~. dpkg-query: no path found matching pattern /etc/init.d/nfs-kernel-server.dpkg-new. dpkg-query: no path found matching pattern /etc/init.d/nfs-kernel-server.dpkg-old. dpkg-query: no path found matching pattern /etc/init.d/nfs-kernel-server~. acpid alsa-utils anacron apache2.2-common at avahi-daemon binfmt-support bluez console-common cpufrequtils cron cups dbus dnet-common exim4-base fam fuse gdm gdm3 hddtemp hdparm ifupdown initscripts kbd keyboard-configuration lastfmsubmitd lastmp lm-sensors mcelog memcached module-init-tools mpd mysql-server-5.0 mysql-server-5.1 netbase network-manager nfs-common nfs-kernel-server ntp openbsd-inetd openssh-server pcscd policykit portmap postfix ppp procps pulseaudio resolvconf rpcbind rsync rsyslog samba sane-utils sasl2-bin screen smartmontools smokeping squid sudo sysv-rc udev udftools unattended-upgrades util-linux virtualbox virtualbox-ose-guest-utils winbind x11-common xen-utils-common xfs -- ..ooOO ch...@chiappa.net | My opinions are my own OOoo.. ..ooOO chris.chia...@oracle.com | and certainly not those OOoo.. ..ooOO http://www.chiappa.net/~chris/ | of my employer OOoo.. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: Bug#648202: FTBFS: qemu-user-static
Processing commands for cont...@bugs.debian.org: serverity 648202 important Unknown command or malformed arguments to command. retitle 648202 FTBFS with binutils-gold Bug #648202 [qemu] FTBFS: qemu-user-static Changed Bug title to 'FTBFS with binutils-gold' from 'FTBFS: qemu-user-static' thanks Stopping processing here. Please contact me if you need assistance. -- 648202: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648202 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644091: genus2reduction: diff for NMU version 0.3-2.2
tags 634342 + pending
tags 644091 + patch
tags 644091 + pending
thanks
Dear maintainer,
I've prepared an NMU for genus2reduction (versioned as 0.3-2.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key ID: 0x8649AA06
: :' : Debian GNU/Linux user, admin, developer - http://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of Free Software Foundation Europe
`-NP: Melissa Etheridge: You Can't Always Get What You Want
diff -u genus2reduction-0.3/debian/rules genus2reduction-0.3/debian/rules
--- genus2reduction-0.3/debian/rules
+++ genus2reduction-0.3/debian/rules
@@ -7,3 +7,3 @@
CFLAGS += -I/usr/include/pari
-LDFLAGS += -lpari
+LDADD += -lpari
DEB_MAKE_INSTALL_TARGET = install DESTDIR=$(DEB_DESTDIR)
diff -u genus2reduction-0.3/debian/control genus2reduction-0.3/debian/control
--- genus2reduction-0.3/debian/control
+++ genus2reduction-0.3/debian/control
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Tim Abbott tabb...@mit.edu
Homepage: http://www.math.u-bordeaux.fr/~liu/G2R/
-Build-Depends: cdbs (= 0.4.23-1.1), debhelper (= 5), quilt, patchutils (= 0.2.25), cdbs (= 0.4.27), libpari-dev, libgmp3-dev
+Build-Depends: cdbs (= 0.4.23-1.1), debhelper (= 5), quilt, patchutils (= 0.2.25), cdbs (= 0.4.27), libpari-dev (= 2.5.0), libgmp3-dev
Standards-Version: 3.7.3
Package: genus2reduction
diff -u genus2reduction-0.3/debian/changelog genus2reduction-0.3/debian/changelog
--- genus2reduction-0.3/debian/changelog
+++ genus2reduction-0.3/debian/changelog
@@ -1,3 +1,17 @@
+genus2reduction (0.3-2.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix Unversioned build-dependency on libpari-dev: make it versioned.
+(Closes: #644091)
+ * Fix Please allow building with ld --as-needed:
+add patch from Ubuntu / Andreas Moog:
+- Libraries needed to link the package should go into LDADD and after
+ sources on the linker command line to fix an issue with ld --as-needed
+ (LP: #770735)
+(Closes: #634342)
+
+ -- gregor herrmann gre...@debian.org Mon, 05 Dec 2011 18:59:09 +0100
+
genus2reduction (0.3-2.1) unstable; urgency=medium
* Non-maintainer upload.
diff -u genus2reduction-0.3/debian/control.in genus2reduction-0.3/debian/control.in
--- genus2reduction-0.3/debian/control.in
+++ genus2reduction-0.3/debian/control.in
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Tim Abbott tabb...@mit.edu
Homepage: http://www.math.u-bordeaux.fr/~liu/G2R/
-Build-Depends: @cdbs@, libpari-dev, libgmp3-dev
+Build-Depends: @cdbs@, libpari-dev (= 2.5.0), libgmp3-dev
Standards-Version: 3.7.3
Package: genus2reduction
diff -u genus2reduction-0.3/debian/patches/makefile.patch genus2reduction-0.3/debian/patches/makefile.patch
--- genus2reduction-0.3/debian/patches/makefile.patch
+++ genus2reduction-0.3/debian/patches/makefile.patch
@@ -4,11 +4,11 @@
+++ src/Makefile 2008-02-08 15:22:00.0 -0800
@@ -0,0 +1,14 @@
+CFLAGS = -O2 -I/usr/include/pari
-+LDFLAGS = -lpari
++LDADD = -lpari
+CC = gcc
+
+genus2reduction:
-+ ${CC} ${CFLAGS} ${LDFLAGS} -o genus2reduction genus2reduction.c
++ ${CC} ${CFLAGS} ${LDFLAGS} -o genus2reduction genus2reduction.c ${LDADD}
+
+install: genus2reduction
+ mkdir -p ${DESTDIR}/usr/bin
signature.asc
Description: Digital signature
Processed: genus2reduction: diff for NMU version 0.3-2.2
Processing commands for cont...@bugs.debian.org: tags 634342 + pending Bug #634342 [genus2reduction] genus2reduction: Please allow building with ld --as-needed Added tag(s) pending. tags 644091 + patch Bug #644091 [src:genus2reduction] genus2reduction: Unversioned build-dependency on libpari-dev Added tag(s) patch. tags 644091 + pending Bug #644091 [src:genus2reduction] genus2reduction: Unversioned build-dependency on libpari-dev Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 644091: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644091 634342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632501: marked as done (logrotate/experimental: FTBFS (kfreebsd): config.c:525:38: error: 'O_CLOEXEC' undeclared (first use in this function))
Your message dated Mon, 05 Dec 2011 18:18:30 + with message-id e1rxd7w-00086y...@franck.debian.org and subject line Bug#632501: fixed in logrotate 3.8.1-1 has caused the Debian Bug report #632501, regarding logrotate/experimental: FTBFS (kfreebsd): config.c:525:38: error: 'O_CLOEXEC' undeclared (first use in this function) 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 632501: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:logrotate Version: 3.7.9-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: cc -Wall -D_GNU_SOURCE -DGNU/kFreeBSD -DVERSION=\3.7.9\ -Wall -g -O2-c -o config.o config.c command-line:0:4: warning: missing whitespace after the macro name [enabled by default] config.c: In function 'readConfigFile': config.c:525:38: error: 'O_CLOEXEC' undeclared (first use in this function) config.c:525:38: note: each undeclared identifier is reported only once for each function it appears in config.c:553:18: error: 'MAP_POPULATE' undeclared (first use in this function) config.c:565:38: error: 'MADV_DONTFORK' undeclared (first use in this function) make[1]: *** [config.o] Error 1 Full build log at https://buildd.debian.org/status/fetch.php?pkg=logrotatearch=kfreebsd-i386ver=3.7.9-1stamp=1308756972 Regards Christoph If you have further questions please mail debian-...@lists.debian.org -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? ---End Message--- ---BeginMessage--- Source: logrotate Source-Version: 3.8.1-1 We believe that the bug you reported is fixed in the latest version of logrotate, which is due to be installed in the Debian FTP archive: logrotate_3.8.1-1.debian.tar.gz to main/l/logrotate/logrotate_3.8.1-1.debian.tar.gz logrotate_3.8.1-1.dsc to main/l/logrotate/logrotate_3.8.1-1.dsc logrotate_3.8.1-1_i386.deb to main/l/logrotate/logrotate_3.8.1-1_i386.deb logrotate_3.8.1.orig.tar.gz to main/l/logrotate/logrotate_3.8.1.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 632...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Martin p...@debian.org (supplier of updated logrotate 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 05 Dec 2011 17:58:16 + Source: logrotate Binary: logrotate Architecture: source i386 Version: 3.8.1-1 Distribution: unstable Urgency: low Maintainer: Paul Martin p...@debian.org Changed-By: Paul Martin p...@debian.org Description: logrotate - Log rotation utility Closes: 182261 334137 379843 576362 632501 635184 648025 649598 Changes: logrotate (3.8.1-1) unstable; urgency=low . * New upstream release + Changes in 3.8.0 fix build problems on non-POSIX architectures (Closes: #632501) + New config options: dateyesterday, maxsize, su. (See manpage.) (maxsize Closes: #635184) * New patch: + man-compressext-576362.patch. Correct manpage about compressext, compressoptions behaviour. (Closes: #576362) * debian/logrotate.README.Debian: update now that rsyslog is default for new installs. (Closes: #649598) * Incidentally, rsyslog is now default syslog, and that doesn't use savelog but makes use of logrotate. (Closes: #379843) * Install logrotate.conf.5 (a redirect to logrotate.8) (Closes: #182261) * debian/control: depend on cron-daemon as an alternative to cron. (Closes: #334137) * lintian warning fix: move debian/logrotate.copyright to debian/copyright * debian/control: add Breaks: postgresql-common (= 126) as its config file requires an su. Postgres maintainer is aware and awaits this upload. * Upload to unstable. (Closes: #648025) Checksums-Sha1: 1d0e40c2a7041d7e815351777251654d0ad2fdad 1705 logrotate_3.8.1-1.dsc 1df36cee76a9c4c7438f35ca3599a7bdd68a09b5 48827 logrotate_3.8.1.orig.tar.gz 5589087cecc0173aeacdd4e1ddeba89ade5c4f23 21690 logrotate_3.8.1-1.debian.tar.gz
Processed: severity of 638813 is serious
Processing commands for cont...@bugs.debian.org: severity 638813 serious Bug #638813 [src:qtcreator] qtcreator: FTBFS: error: no matching function for call to 'qMin(double, qreal)' Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 638813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638813 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649491: Bug#651032: /usr/sbin/rpc.idmapd: rpc.idmapd referring to none existing library
On Mon, Dec 05, 2011 at 10:52:18AM -0500, Steve Dickson wrote:
Why not just use the --with-pluginpath configuration flag?
That's how we do it in Fedora...
The --with-pluginpath configuration option isn't in 0.24.
I run
./configure --help
and it doesn't list the --with-pluginpath configuration option.
The configure commands doesn't unrecognize the --with-pluginpath option.
See below.
CFLAGS=-Wall -g -O2 ./configure --host=i486-linux-gnu \
--build=i486-linux-gnu --prefix=/usr --mandir=\${prefix}/share/man \
--infodir=\${prefix}/share/info --with-pluginpath=/lib/libnfsidmap
configure: WARNING: unrecognized options: --with-pluginpath
The git repo has patches to add the --with-pluginpath configuration
option. Do you plan to release libnfsidmap 0.25 soon?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Bug#648202: FTBFS: qemu-user-static
Processing commands for cont...@bugs.debian.org: severity 648202 important Bug #648202 [qemu] FTBFS with binutils-gold Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 648202: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648202 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607267: /usr/bin/scp: fails to notice close() errors
Excerpts from Helmut Grohne's message of Mon Dec 05 18:15:53 +0100 2011: Hi Michal, On Mon, Dec 05, 2011 at 05:03:25PM +0100, Michal Suchanek wrote: Excerpts from Helmut Grohne's message of Mon Dec 05 15:54:19 +0100 2011: Can we now ignore 2) and concentrate on 1)? No. If I wanted this semantics I could use shred(1). Please report a separate bug about not using fsync then. (or clone this bug) They can be fixed independently. I want my files saved. Honestly. You seem to have a rather different view on this issue than the rest of the world (otherwise it would have been reported way earlier). I would guess that most of the rest of the world is not aware of this issue. It's probably not been like that since day 1 of Linux. I suspect that at some point Linux implemented some optimization that allows close() to finish before the space for the written data is even allocated and others like that which leads to these issues. As for me I really do *not* want fsync here. For instance when I use a slow usb storage device, I really want cp to finish before the copied stuff is written to permanent storage. Why? Either you want the data on the storage so you eject it and wait for eject to finish anyway or you are doing something else in the meantime so you can do so regardless of cp finishing or not. So even I would assume that the fsync issue is just wontfix (even though I am not the openssh maintainer). Note that this same issue has been found and fixed in dpkg. This is good and all. But in general tools simply do not provide fsync semantics and people actually expect that now. When firefox tried to introduce fsync, it was disabled for performance reasons again. If you need it, go sync after you copy. (Or write patches.) No, it is not good at all that fsync is not used in things like cp. It was not used in dpkg which led to severe system corruption which is now fixed but any other tools used to manipulate files should do the same. Otherwise they are useless. Thanks Michal -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650193: [pkg-ggz-maintainers] Bug#650193: ggz-python: should this package be removed?
On sön, 2011-11-27 at 17:12 +0100, Jakub Wilk wrote: Source: ggz-python Version: 0.0.14.1-1 Severity: serious User: debian...@lists.debian.org Usertags: proposed-removal Dear Maintainer, While reviewing some packages, your package came up as a possible candidate for removal from Debian, Yeah, maybe the whole ggz suite should be removed (again). Upstream seems to be stalled. But some GNOME stuff depends on some ggz libraries, so I don't know how to go forward. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639636: nodejs: FTBFS/armel - testsuite fails
On 05/12/2011 17:51, Jérémy Lal wrote:
Thanks to the abel guest access i got, libv8 builds and pass tests on armel
and armhf.
I'm still having *one* test failing, if anyone has an idea about why :
var f = new Buffer('über', 'ucs2');
assert.deepEqual(f, new Buffer([252, 0, 98, 0, 101, 0, 114, 0]));
Giving this result :
https://buildd.debian.org/status/fetch.php?pkg=nodejsarch=armelver=0.4.12-2stamp=1323100281file=log
Couldn't be linked to some wrong endianness assumption ?
It isn't, after doing some testing on abel, i observe this strange behavior :
build/default/node
/home/kapouer/nodejs/nodejs-0.4.12/test/simple/test-buffer.js
never outputs errors,
while
python tools/test.py simple/test-buffer
always does.
I'm stuck.
Jérémy.
PS: wild cc-ing nodejs-dev, in case someone there already knows why :)
the test mentionned above is the only one failing, and it's been there for
a long time.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650995: causes dependency loop in boot sequence (according to insserv)
I've removed $remote_fs from /etc/init.d/keymap.sh - Required-Start and dpkg --configure --pending has finalized console-common's installation. Thank you all for your pointers :) -- Regards. Yannick Le Saint (kyncani) y.lesa...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650995: causes dependency loop in boot sequence (according to insserv)
Quoting Kel Modderman (k...@otaku42.de): I would like to know why this change in dependency was made by the console-common maintainers? I'll check this ASAP. It might be a change that accidentally leaked into the VCS (when I worked on this package yesterday, I found a few pending changes additionnally to the issue I was working on (which was related to /run transition) signature.asc Description: Digital signature
Processed: forcibly merging 650995 651043
Processing commands for cont...@bugs.debian.org: forcemerge 650995 651043 Bug#650995: causes dependency loop in boot sequence (according to insserv) Bug#651043: [console-common] Can't upgrade console-common Bug#651000: console-common: Circular dependency during upgrade Forcibly Merged 650995 651000 651043. thanks Stopping processing here. Please contact me if you need assistance. -- 651000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651000 651043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651043 650995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: forcibly merging 650995 651036
Processing commands for cont...@bugs.debian.org: forcemerge 650995 651036 Bug#650995: causes dependency loop in boot sequence (according to insserv) Bug#651036: update-rc.d: error: insserv rejected the script header Bug#651000: console-common: Circular dependency during upgrade Bug#651043: [console-common] Can't upgrade console-common Forcibly Merged 650995 651000 651036 651043. thanks Stopping processing here. Please contact me if you need assistance. -- 651000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651000 651036: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651036 651043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651043 650995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: maloc: diff for NMU version 0.2-2.3
Processing commands for cont...@bugs.debian.org: tags 643441 + patch Bug #643441 [src:maloc] maloc: FTBFS: vnm.c:913:21: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 643441: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643441: maloc: diff for NMU version 0.2-2.3
tags 643441 + patch
thanks
Dear maintainer,
I've prepared an NMU for maloc (versioned as 0.2-2.3) and uploaded it. The diff
is attached to this message.
Regards.
--
Tim Retout dioc...@debian.org
diff -u maloc-0.2/debian/changelog maloc-0.2/debian/changelog
--- maloc-0.2/debian/changelog
+++ maloc-0.2/debian/changelog
@@ -1,3 +1,11 @@
+maloc (0.2-2.3) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * debian/patches/format-security.diff: New patch to fix build when
+-Werror=format-security is enabled. (Closes: #643441)
+
+ -- Tim Retout dioc...@debian.org Mon, 05 Dec 2011 18:41:08 +
+
maloc (0.2-2.2) unstable; urgency=low
* Non-maintainer upload.
only in patch2:
unchanged:
--- maloc-0.2.orig/debian/patches/format-security.diff
+++ maloc-0.2/debian/patches/format-security.diff
@@ -0,0 +1,24 @@
+Description: Fix build when -Werror=format-security is enabled.
+Author: Tim Retout dioc...@debian.org
+Bug-Debian: http://bugs.debian.org/643441
+
+--- maloc-0.2.orig/src/vsys/vnm.c
maloc-0.2/src/vsys/vnm.c
+@@ -910,7 +910,7 @@
+ fprintf(cons[unit],# MC-shell I/O capture file.\n);
+ now = time(VNULL);
+ sprintf(str,# Creation Date and Time: %s,ctime(now));
+-fprintf(cons[unit],str);
++fprintf(cons[unit],%s,str);
+ fprintf(cons[unit],
+ ##\n);
+ } else if (unit == 3) {
+@@ -920,7 +920,7 @@
+ fprintf(cons[unit],# MC-shell history file.\n);
+ now = time(VNULL);
+ sprintf(str,# Creation Date and Time: %s,ctime(now));
+-fprintf(cons[unit],str);
++fprintf(cons[unit],%s,str);
+ fprintf(cons[unit],
+ ##\n);
+ }
Bug#639991: marked as done (guile-1.8-non-dfsg fails to build from source in unstable)
Your message dated Mon, 05 Dec 2011 19:34:54 + with message-id e1rxejs-0002nb...@franck.debian.org and subject line Bug#639991: fixed in guile-1.8-non-dfsg 1.8.8+1-1.1 has caused the Debian Bug report #639991, regarding guile-1.8-non-dfsg fails to build from source in unstable 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 639991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639991 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: guile-1.8-non-dfsg Version: 1.8.8+1-1 Severity: serious Tags: sid wheezy Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu oneiric ubuntu-patch patch at http://launchpadlibrarian.net/78695380/guile-1.8-non-dfsg_1.8.8%2B1-1_1.8.8%2B1-1ubuntu1.diff.gz (the build fails a second time trying to remove the non-existent dir file) dpkg-source --before-build guile-1.8-non-dfsg-1.8.8+1 dpkg-buildpackage: host architecture amd64 fakeroot debian/rules clean dh clean --parallel --with autoreconf debian/rules override_dh_testdir make[1]: Entering directory `/home/packages/tmp/guile-1.8-non-dfsg-1.8.8+1' dh_testdir GUILE-VERSION debian/changelog make[1]: Leaving directory `/home/packages/tmp/guile-1.8-non-dfsg-1.8.8+1' dh_auto_clean -O--parallel dh_autoreconf_clean -O--parallel debian/rules override_dh_clean make[1]: Entering directory `/home/packages/tmp/guile-1.8-non-dfsg-1.8.8+1' dh_clean debian/guile-1.8-doc-non-dfsg.info debian/guile-1.8-doc-non-dfsg.install \ doc/goops/goops-1.8.texi \ doc/ref/guile-1.8.texi \ doc/goops/goops-1.8.info \ doc/ref/guile-1.8.info \ doc/ref/guile-1.8.info-1 \ doc/ref/guile-1.8.info-2 \ doc/ref/guile-1.8.info-3 \ doc/ref/guile-1.8.info-4 \ doc/ref/guile-1.8.info-5 \ doc/ref/guile-1.8.info-6 \ doc/ref/guile-1.8.info-7 make[1]: Leaving directory `/home/packages/tmp/guile-1.8-non-dfsg-1.8.8+1' debian/rules build dh build --parallel --with autoreconf debian/rules override_dh_testdir make[1]: Entering directory `/home/packages/tmp/guile-1.8-non-dfsg-1.8.8+1' dh_testdir GUILE-VERSION debian/changelog make[1]: Leaving directory `/home/packages/tmp/guile-1.8-non-dfsg-1.8.8+1' debian/rules override_dh_autoreconf make[1]: Entering directory `/home/packages/tmp/guile-1.8-non-dfsg-1.8.8+1' cd doc/goops ln -sf goops.texi goops-1.8.texi cd doc/ref ln -sf guile.texi guile-1.8.texi dh_autoreconf -- autoreconf -i --force --verbose autoreconf: `configure.ac' or `configure.in' is required dh_autoreconf: autoreconf -i --force --verbose autoreconf -i --force --verbose returned exit code 1 make[1]: *** [override_dh_autoreconf] Error 2 make[1]: Leaving directory `/home/packages/tmp/guile-1.8-non-dfsg-1.8.8+1' make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 ---End Message--- ---BeginMessage--- Source: guile-1.8-non-dfsg Source-Version: 1.8.8+1-1.1 We believe that the bug you reported is fixed in the latest version of guile-1.8-non-dfsg, which is due to be installed in the Debian FTP archive: guile-1.8-doc-non-dfsg_1.8.8+1-1.1_all.deb to non-free/g/guile-1.8-non-dfsg/guile-1.8-doc-non-dfsg_1.8.8+1-1.1_all.deb guile-1.8-non-dfsg_1.8.8+1-1.1.debian.tar.gz to non-free/g/guile-1.8-non-dfsg/guile-1.8-non-dfsg_1.8.8+1-1.1.debian.tar.gz guile-1.8-non-dfsg_1.8.8+1-1.1.dsc to non-free/g/guile-1.8-non-dfsg/guile-1.8-non-dfsg_1.8.8+1-1.1.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 639...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated guile-1.8-non-dfsg 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 03 Dec 2011 20:08:26 +0100 Source: guile-1.8-non-dfsg Binary: guile-1.8-doc-non-dfsg Architecture: source all Version: 1.8.8+1-1.1 Distribution: unstable Urgency: low Maintainer: Rob Browning r...@defaultvalue.org Changed-By: gregor herrmann gre...@debian.org Description: guile-1.8-doc-non-dfsg - Reference documentation for Guile 1.8 (non-DFSG items) Closes: 639991 Changes: guile-1.8-non-dfsg (1.8.8+1-1.1) unstable; urgency=low . *
Bug#643441: marked as done (maloc: FTBFS: vnm.c:913:21: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Mon, 05 Dec 2011 19:38:27 + with message-id e1rxemt-00035b...@franck.debian.org and subject line Bug#643441: fixed in maloc 0.2-2.3 has caused the Debian Bug report #643441, regarding maloc: FTBFS: vnm.c:913:21: error: format not a string literal and no format arguments [-Werror=format-security] 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 643441: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: maloc Version: 0.2-2.2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs hardening-format-security hardening Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: gcc -DHAVE_CONFIG_H -I. -I. -I../../src/aaa_inc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c vnm.c -fPIC -DPIC -o .libs/vnm.o vnm.c: In function 'Vnm_open': vnm.c:913:21: error: format not a string literal and no format arguments [-Werror=format-security] vnm.c:923:21: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[4]: *** [vnm.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/maloc_0.2-2.2_lsid64.buildlog This happened because since dpkg 1.16.0 [0], hardening flags are enabled under various conditions. [0] http://lists.debian.org/debian-devel-announce/2011/09/msg1.html 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. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: maloc Source-Version: 0.2-2.3 We believe that the bug you reported is fixed in the latest version of maloc, which is due to be installed in the Debian FTP archive: libmaloc-dev_0.2-2.3_amd64.deb to main/m/maloc/libmaloc-dev_0.2-2.3_amd64.deb libmaloc1_0.2-2.3_amd64.deb to main/m/maloc/libmaloc1_0.2-2.3_amd64.deb maloc_0.2-2.3.diff.gz to main/m/maloc/maloc_0.2-2.3.diff.gz maloc_0.2-2.3.dsc to main/m/maloc/maloc_0.2-2.3.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tim Retout dioc...@debian.org (supplier of updated maloc 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 05 Dec 2011 18:41:08 + Source: maloc Binary: libmaloc1 libmaloc-dev Architecture: source amd64 Version: 0.2-2.3 Distribution: unstable Urgency: low Maintainer: Michael Banck mba...@debian.org Changed-By: Tim Retout dioc...@debian.org Description: libmaloc-dev - Object-oriented Abstraction Layer for C (development files) libmaloc1 - Object-oriented Abstraction Layer for C Closes: 643441 Changes: maloc (0.2-2.3) unstable; urgency=low . * Non-maintainer upload. * debian/patches/format-security.diff: New patch to fix build when -Werror=format-security is enabled. (Closes: #643441) Checksums-Sha1: 2a1655b6facf07b17afb3d2867cca07e4ff38d9d 1072 maloc_0.2-2.3.dsc d74b40f1303cb36de742f46c83593da19eeb6ccb 2913 maloc_0.2-2.3.diff.gz 43b0698114304b8cffa7015df294856014128dd2 61180 libmaloc1_0.2-2.3_amd64.deb d7004c4e013bdb42d075aed2a18b2febc0162394 119018 libmaloc-dev_0.2-2.3_amd64.deb Checksums-Sha256: e37a94d692fc386e9f4db5bfe67a4c17e9f7f8671a2948d31aef1f14d1b19366 1072 maloc_0.2-2.3.dsc 186d6a24f436489cc04c8168a5d341667775be71c5f1dfcd09f9d2899d31b30b 2913 maloc_0.2-2.3.diff.gz 8fbbd505269a8cb7af951a6d58e41815980eaeb7976303cafbca8e011721181a 61180 libmaloc1_0.2-2.3_amd64.deb eecab8cf448b9cc40497175d7f1c8bc3b96feb07e8f95f140b645ad0dbee2803 119018 libmaloc-dev_0.2-2.3_amd64.deb Files: a485f68abd4f75da88c222bc679fecff 1072 devel optional maloc_0.2-2.3.dsc b980cd41b1e6c53a9f049ea503b8b557 2913 devel optional maloc_0.2-2.3.diff.gz
Bug#607267: /usr/bin/scp: fails to notice close() errors
On Mon, Dec 5, 2011 at 19:57:59 +0100, Michal Suchanek wrote: I would guess that most of the rest of the world is not aware of this issue. Please kindly take me off your nonsense rants. And better yet, take them off the debian bug tracking system. TIA, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649625: webkit unmaintained security-wise (again)
Hi, On Tue, Nov 22, 2011 at 09:39:41PM +0100, Moritz Muehlenhoff wrote: Source: webkit Severity: grave [..] I have no idea, whether this LTS branch exists, but webkit is - as in Squeeze - unmaintained wrt security updates. [..] I guess the consequence is to pick one of the two as the default browser for Wheezy and to demote webkit as another unsupported HTML render engine usable to render a HTML help, but not for a full browser (just like khtml and qtwebkit) If the situation persists, it may be worth warning *squeeze* users, through a dedicated DSA/d-security-announce, as well as a dedicated paragraph in the next point release announce ? -- Simon Paillard -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651068: file conflict with cups-pdf prevents upgrade to 1.4.4-7+squeeze1
On Mon, Dec 05, 2011 at 05:12:23PM +0100, Yves-Alexis Perez wrote: Could you post the output of: ls -lhd /etc/cups Hmm, looks like I had some interesting corruption in my filesystem: joe@tux:~$ ls -lhd /etc/cups lrwxrwxrwx 1 root root 15 Mar 8 2011 /etc/cups - libdl-2.11.2.so After fixing this, I'm able to upgrade properly. Thanks for the pointer. --Joe -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650995: causes dependency loop in boot sequence (according to insserv)
Quoting Kel Modderman (k...@otaku42.de): I would like to know why this change in dependency was made by the console-common maintainers? This happened in r314 of our SVN, in a commit of mine, meant to fix #633048. I actually had no intent of doing this change. I guess that it was (for areason I can't even imagine) pending in my local SVN copy...and I couldn't even notice it when doing svn diff before committing. And, to make it worse, it seems that the (probably too) short test I did before uploading didn't reveal the problem..:-( Sorry for the trouble to everybody who was annoyed by this issue. I just fixed it in console-common 0.7.87. Thanks, Kel, for your analysis. signature.asc Description: Digital signature
Bug#649491: Bug#651032: /usr/sbin/rpc.idmapd: rpc.idmapd referring to none existing library
On 12/05/2011 01:42 PM, Anibal Monsalve Salazar wrote:
On Mon, Dec 05, 2011 at 10:52:18AM -0500, Steve Dickson wrote:
Why not just use the --with-pluginpath configuration flag?
That's how we do it in Fedora...
The --with-pluginpath configuration option isn't in 0.24.
I run
./configure --help
and it doesn't list the --with-pluginpath configuration option.
The configure commands doesn't unrecognize the --with-pluginpath option.
See below.
CFLAGS=-Wall -g -O2 ./configure --host=i486-linux-gnu \
--build=i486-linux-gnu --prefix=/usr --mandir=\${prefix}/share/man \
--infodir=\${prefix}/share/info --with-pluginpath=/lib/libnfsidmap
configure: WARNING: unrecognized options: --with-pluginpath
The git repo has patches to add the --with-pluginpath configuration
option. Do you plan to release libnfsidmap 0.25 soon?
Sure.. I'll try to get one out asap...
steved.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650958: [Pkg-samba-maint] Bug#650958: Bug#650958: samba INTERNAL ERROR: Signal 11 - PANIC - BACKTRACE: 16 stack frames
Just removed every file in that directory and tried to restart samba with the minimal smb.conf and got the exact same error. On Mon, Dec 5, 2011 at 3:25 PM, Tiago Caxias tcx.talie...@gmail.com wrote: Yes, of course. I'll do it as soon as I'll get home. Just a couple of things: 1 - this happened right after an aptitude full-upgrade 2 - my samba server isn't serving printing services for some months now. My wife switched from windows to mac so I stopped sharing printers in smb.conf and started cups sharing. On Mon, Dec 5, 2011 at 6:59 AM, Christian PERRIER bubu...@debian.orgwrote: Quoting Christian PERRIER (bubu...@debian.org): Quoting Tiago Caxias (tcx.talie...@gmail.com): Package: samba Version: 2:3.6.1-3 Severity: grave Justification: renders package unusable Could you try cleaning out /var/cache/samba/printing?It is likely that a printer TDB cache file has invalid data in it. -- Tiago Caxias -- Tiago Caxias
Bug#651068: marked as done (file conflict with cups-pdf prevents upgrade to 1.4.4-7+squeeze1)
Your message dated Mon, 5 Dec 2011 22:33:04 +0200 with message-id capzxpqcgtvcsopwkxwmhdi1r-n1fev7xtxge95i-64w0xxc...@mail.gmail.com and subject line Re: [Pkg-cups-devel] Bug#651068: file conflict with cups-pdf prevents upgrade to 1.4.4-7+squeeze1 has caused the Debian Bug report #651068, regarding file conflict with cups-pdf prevents upgrade to 1.4.4-7+squeeze1 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 651068: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651068 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cups Version: 1.4.4-7+squeeze1 Severity: grave Tags: squeeze I tried to run an apt-get dist-upgrade, but cups doesn't upgrade cleanly because of a conflict with package cups-pdf: joe@tux:~$ sudo apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Starting Starting 2 Done Done The following packages will be upgraded: cups 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 12 not fully installed or removed. Need to get 0 B/2,020 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? Reading changelogs... Done Preconfiguring packages ... (Reading database ... 167164 files and directories currently installed.) Preparing to replace cups 1.4.4-7 (using .../cups_1.4.4-7+squeeze1_i386.deb) ... Stopping Common Unix Printing System: cupsd. Unpacking replacement cups ... dpkg: error processing /var/cache/apt/archives/cups_1.4.4-7+squeeze1_i386.deb (--unpack): trying to overwrite '/etc/cups', which is also in package cups-pdf 2.5.0-16 configured to not write apport reports dpkg-deb: subprocess paste killed by signal (Broken pipe) Starting Common Unix Printing System: cupsdcupsd: Child exited with status 1! Message from syslogd@tux at Dec 5 09:10:18 ... cupsd: Unable to read configuration file '/etc/cups/cupsd.conf' - exiting! .. Errors were encountered while processing: /var/cache/apt/archives/cups_1.4.4-7+squeeze1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) joe@tux:~$ -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cups depends on: ii adduser 3.112+nmu2 add and remove users and groups ii bc 1.06.95-2The GNU bc arbitrary precision cal pn cups-client none (no description available) pn cups-common none (no description available) pn cups-ppdc none (no description available) ii debconf [debconf-2. 1.5.36.1 Debian configuration management sy ii ghostscript 8.71~dfsg2-9 The GPL Ghostscript PostScript/PDF ii libavahi-client30.6.27-2+squeeze1Avahi client library ii libavahi-common30.6.27-2+squeeze1Avahi common library ii libc6 2.11.2-10Embedded GNU C Library: Shared lib pn libcups2none (no description available) pn libcupscgi1 none (no description available) pn libcupsdriver1 none (no description available) pn libcupsimage2 none (no description available) pn libcupsmime1none (no description available) pn libcupsppdc1none (no description available) ii libdbus-1-3 1.2.24-4+squeeze1simple interprocess messaging syst ii libgcc1 1:4.4.5-8GCC support library ii libgnutls26 2.8.6-1 the GNU TLS library - runtime libr ii libgssapi-krb5-21.8.3+dfsg-4squeeze2 MIT Kerberos runtime libraries - k ii libijs-0.35 0.35-7 IJS raster image transport protoco ii libkrb5-3 1.8.3+dfsg-4squeeze2 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.23-7.2 OpenLDAP libraries ii libpam0g1.1.1-6.1+squeeze1 Pluggable Authentication Modules l ii libpaper1 1.1.24 library for handling paper charact ii libpoppler5 0.12.4-1.2 PDF rendering library ii libslp1 1.2.1-7.8OpenSLP libraries ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii libusb-0.1-42:0.1.12-16
Bug#650958: [Pkg-samba-maint] Bug#650958: Bug#650958: samba INTERNAL ERROR: Signal 11 - PANIC - BACKTRACE: 16 stack frames
Quoting Tiago Caxias (tcx.talie...@gmail.com): Just removed every file in that directory and tried to restart samba with the minimal smb.conf and got the exact same error. Do you have files in /var/run/samba? signature.asc Description: Digital signature
Bug#650958: [Pkg-samba-maint] Bug#650958: Bug#650958: samba INTERNAL ERROR: Signal 11 - PANIC - BACKTRACE: 16 stack frames
$ ls /var/run/samba/ brlock.tdb gencache_notrans.tdb locking.tdb nmbd.pid notify.tdbserverid.tdb unexpected= connections.tdb gencache.tdb messages.tdb notify_onelevel.tdb printer_list.tdb sessionid.tdb Want me to clear that dir? On Mon, Dec 5, 2011 at 8:37 PM, Christian PERRIER bubu...@debian.orgwrote: Quoting Tiago Caxias (tcx.talie...@gmail.com): Just removed every file in that directory and tried to restart samba with the minimal smb.conf and got the exact same error. Do you have files in /var/run/samba? -- Tiago Caxias
Bug#639636: [node-dev] Re: Bug#639636: nodejs: FTBFS/armel - testsuite fails
On Mon, Dec 5, 2011 at 20:02, Jérémy Lal kapo...@melix.org wrote:
On 05/12/2011 17:51, Jérémy Lal wrote:
Thanks to the abel guest access i got, libv8 builds and pass tests on armel
and armhf.
I'm still having *one* test failing, if anyone has an idea about why :
var f = new Buffer('über', 'ucs2');
assert.deepEqual(f, new Buffer([252, 0, 98, 0, 101, 0, 114, 0]));
Giving this result :
https://buildd.debian.org/status/fetch.php?pkg=nodejsarch=armelver=0.4.12-2stamp=1323100281file=log
Couldn't be linked to some wrong endianness assumption ?
It isn't, after doing some testing on abel, i observe this strange behavior :
build/default/node
/home/kapouer/nodejs/nodejs-0.4.12/test/simple/test-buffer.js
never outputs errors,
while
python tools/test.py simple/test-buffer
always does.
I'm stuck.
Jérémy.
PS: wild cc-ing nodejs-dev, in case someone there already knows why :)
the test mentionned above is the only one failing, and it's been there for
a long time.
It looks like a off-by-one error. To wit:
{0:252,1:0,2:98,3:0,4:101,5:0,6:114,7:0
{0:0,1:98,2:0,3:101,4:0,5:114,6:0,7:120
It's quite possibly been fixed. Does it happen with v0.6.5?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650958: [Pkg-samba-maint] Bug#650958: Bug#650958: samba INTERNAL ERROR: Signal 11 - PANIC - BACKTRACE: 16 stack frames
Quoting Tiago Caxias (tcx.talie...@gmail.com): $ ls /var/run/samba/ brlock.tdb gencache_notrans.tdb locking.tdb nmbd.pid notify.tdbserverid.tdb unexpected= connections.tdb gencache.tdb messages.tdb notify_onelevel.tdb printer_list.tdb sessionid.tdb Want me to clear that dir? Yep. It can't hurt anyway. Later on, we can try the same in /var/lib/samba but that one requires preserving files (depending on your setup, some files there can be important to keep). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650995: marked as done (causes dependency loop in boot sequence (according to insserv))
Your message dated Mon, 05 Dec 2011 21:03:43 + with message-id e1rxfhp-0005sz...@franck.debian.org and subject line Bug#650995: fixed in console-common 0.7.87 has caused the Debian Bug report #650995, regarding causes dependency loop in boot sequence (according to insserv) 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 650995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: console-common Version: 0.7.86 Severity: serious Installation of console-common 0.7.86 has failed in unstable for me with the following insserv error: Setting up console-common (0.7.86) ... Looking for keymap to install: NONE insserv: There is a loop between service checkfs and cryptdisks if started insserv: loop involving service cryptdisks at depth 12 insserv: loop involving service checkroot at depth 11 insserv: There is a loop between service nfs-common and hwclock if started insserv: loop involving service hwclock at depth 12 insserv: There is a loop between service lvm2 and cryptdisks-early if started insserv: loop involving service cryptdisks-early at depth 12 insserv: There is a loop between service checkfs and cryptdisks if started insserv: There is a loop between service nfs-common and hwclock if started insserv: There is a loop between service lvm2 and cryptdisks-early if started insserv: loop involving service mountnfs at depth 8 insserv: loop involving service nfs-common at depth 7 insserv: loop involving service portmap at depth 6 insserv: loop involving service mountall at depth 4 insserv: loop involving service checkfs at depth 3 insserv: loop involving service lvm2 at depth 2 insserv: loop involving service udev at depth 1 insserv: loop involving service mtab at depth 13 insserv: There is a loop between service mountall and checkfs if started insserv: loop involving service keymap at depth 16 insserv: loop involving service hibernate-cleanup at depth 20 insserv: loop involving service networking at depth 22 insserv: loop involving service restorecond at depth 32 insserv: There is a loop between service mountnfs and nfs-common if started insserv: loop involving service alsa-utils at depth 33 insserv: loop involving service ifupdown-clean at depth 34 insserv: loop involving service console-screen at depth 34 insserv: exiting now without changing boot order! update-rc.d: error: insserv rejected the script header dpkg: error processing console-common (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: console-common let me know what extra information I can provide to debug this. Cheers. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages console-common depends on: ii console-data 2:1.12-1 ii console-tools 1:0.2.3dbs-70 ii debconf [debconf-2.0] 1.5.41 ii debianutils4.1 ii lsb-base 3.2-28 console-common recommends no packages. console-common suggests no packages. -- debconf information: console-data/keymap/powerpcadb: console-data/keymap/ignored: console-data/keymap/full: console-data/keymap/template/keymap: * console-data/keymap/policy: Don't touch keymap console-data/bootmap-md5sum: none console-data/keymap/template/layout: console-data/keymap/family: qwerty console-data/keymap/template/variant: ---End Message--- ---BeginMessage--- Source: console-common Source-Version: 0.7.87 We believe that the bug you reported is fixed in the latest version of console-common, which is due to be installed in the Debian FTP archive: console-common_0.7.87.dsc to main/c/console-common/console-common_0.7.87.dsc console-common_0.7.87.tar.gz to main/c/console-common/console-common_0.7.87.tar.gz console-common_0.7.87_all.deb to main/c/console-common/console-common_0.7.87_all.deb dh-consoledata_0.7.87_all.deb to main/c/console-common/dh-consoledata_0.7.87_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 650...@bugs.debian.org, and the maintainer will reopen
Bug#651000: marked as done (console-common: Circular dependency during upgrade)
Your message dated Mon, 05 Dec 2011 21:03:43 + with message-id e1rxfhp-0005sz...@franck.debian.org and subject line Bug#650995: fixed in console-common 0.7.87 has caused the Debian Bug report #650995, regarding console-common: Circular dependency during upgrade 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 650995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: console-common Version: 0.7.86 Severity: grave Justification: renders package unusable insserv: There is a loop between service nfs-common and hwclock if started insserv: loop involving service hwclock at depth 11 insserv: loop involving service checkroot at depth 10 insserv: There is a loop between service checkfs and mtab if started insserv: loop involving service mtab at depth 11 insserv: There is a loop between service checkfs and checkroot if started insserv: There is a loop between service nfs-common and hwclock if started insserv: loop involving service keyboard-setup at depth 10 insserv: There is a loop between service checkfs and mtab if started insserv: loop involving service mountnfs at depth 7 insserv: loop involving service nfs-common at depth 6 insserv: loop involving service portmap at depth 5 insserv: loop involving service mountall at depth 4 insserv: loop involving service checkfs at depth 3 insserv: loop involving service lvm2 at depth 2 insserv: loop involving service module-init-tools at depth 13 insserv: There is a loop between service mountall and checkfs if started insserv: There is a loop between service mountnfs and nfs-common if started insserv: loop involving service keymap at depth 21 insserv: loop involving service alsa-utils at depth 23 insserv: loop involving service networking at depth 21 insserv: exiting now without changing boot order! update-rc.d: error: insserv rejected the script header dpkg: error processing console-common (--configure): subprocess installed post-installation script returned error exit status 1 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages console-common depends on: ii console-data 2:1.12-1 ii console-tools 1:0.2.3dbs-70 ii debconf [debconf-2.0] 1.5.41 ii debianutils4.1 ii lsb-base 3.2-28 console-common recommends no packages. console-common suggests no packages. -- debconf information: console-data/keymap/powerpcadb: console-data/keymap/ignored: console-data/keymap/full: console-data/keymap/template/keymap: * console-data/keymap/policy: Select keymap from arch list console-data/bootmap-md5sum: bff6f7422c3fbac725bc7c16d5785cc4 console-data/keymap/template/layout: * console-data/keymap/family: qwerty console-data/keymap/template/variant: ---End Message--- ---BeginMessage--- Source: console-common Source-Version: 0.7.87 We believe that the bug you reported is fixed in the latest version of console-common, which is due to be installed in the Debian FTP archive: console-common_0.7.87.dsc to main/c/console-common/console-common_0.7.87.dsc console-common_0.7.87.tar.gz to main/c/console-common/console-common_0.7.87.tar.gz console-common_0.7.87_all.deb to main/c/console-common/console-common_0.7.87_all.deb dh-consoledata_0.7.87_all.deb to main/c/console-common/dh-consoledata_0.7.87_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 650...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Perrier bubu...@debian.org (supplier of updated console-common 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 05 Dec 2011 21:08:35 +0100 Source: console-common Binary: console-common dh-consoledata Architecture: source all Version: 0.7.87 Distribution: unstable Urgency: low Maintainer: Alastair McKinstry mckins...@debian.org Changed-By: Christian Perrier bubu...@debian.org Description:
Bug#651036: marked as done (update-rc.d: error: insserv rejected the script header)
Your message dated Mon, 05 Dec 2011 21:03:43 + with message-id e1rxfhp-0005sz...@franck.debian.org and subject line Bug#650995: fixed in console-common 0.7.87 has caused the Debian Bug report #650995, regarding update-rc.d: error: insserv rejected the script header 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 650995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: console-common Version: 0.7.86 Severity: normal Dear Maintainer, upgrade fails with: insserv: There is a loop between service cryptdisks and checkroot if started insserv: loop involving service checkroot at depth 8 insserv: loop involving service keymap at depth 7 insserv: There is a loop between service cryptdisks and checkroot if started insserv: loop involving service checkfs at depth 3 insserv: loop involving service cryptdisks at depth 2 insserv: loop involving service udev at depth 1 insserv: There is a loop between service keymap and mountnfs if started insserv: loop involving service mountnfs at depth 19 insserv: loop involving service networking at depth 18 insserv: loop involving service console-screen at depth 21 insserv: There is a loop between service keymap and mountoverflowtmp if started insserv: loop involving service mountoverflowtmp at depth 19 insserv: loop involving service mountall-bootclean at depth 18 insserv: There is a loop between service keymap and mountall if started insserv: loop involving service mountall at depth 17 insserv: loop involving service keyboard-setup at depth 13 insserv: loop involving service cryptdisks-early at depth 15 insserv: There is a loop between service mountall and checkfs if started insserv: loop involving service resolvconf at depth 21 insserv: loop involving service module-init-tools at depth 21 insserv: exiting now without changing boot order! update-rc.d: error: insserv rejected the script header -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages console-common depends on: ii console-data 2:1.12-1 ii console-tools 1:0.2.3dbs-70 ii debconf [debconf-2.0] 1.5.41 ii debianutils4.1 ii lsb-base 3.2-28 console-common recommends no packages. console-common suggests no packages. -- debconf information: console-data/keymap/powerpcadb: console-data/keymap/ignored: console-data/keymap/full: console-data/keymap/template/keymap: * console-data/keymap/policy: Select keymap from arch list console-data/bootmap-md5sum: bdc0a74cc7c5303e088ecd80101bf707 console-data/keymap/template/layout: * console-data/keymap/family: qwertz console-data/keymap/template/variant: ---End Message--- ---BeginMessage--- Source: console-common Source-Version: 0.7.87 We believe that the bug you reported is fixed in the latest version of console-common, which is due to be installed in the Debian FTP archive: console-common_0.7.87.dsc to main/c/console-common/console-common_0.7.87.dsc console-common_0.7.87.tar.gz to main/c/console-common/console-common_0.7.87.tar.gz console-common_0.7.87_all.deb to main/c/console-common/console-common_0.7.87_all.deb dh-consoledata_0.7.87_all.deb to main/c/console-common/dh-consoledata_0.7.87_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 650...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Perrier bubu...@debian.org (supplier of updated console-common 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 05 Dec 2011 21:08:35 +0100 Source: console-common Binary: console-common dh-consoledata Architecture: source all Version: 0.7.87 Distribution: unstable Urgency: low Maintainer: Alastair McKinstry mckins...@debian.org Changed-By: Christian Perrier bubu...@debian.org Description: console-common - basic infrastructure for text console configuration dh-consoledata - debhelper-based script to help
Bug#651043: marked as done ([console-common] Can't upgrade console-common)
Your message dated Mon, 05 Dec 2011 21:03:43 + with message-id e1rxfhp-0005sz...@franck.debian.org and subject line Bug#650995: fixed in console-common 0.7.87 has caused the Debian Bug report #650995, regarding [console-common] Can't upgrade console-common 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 650995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: console-common Version: 0.7.86 Severity: normal --- Please enter the report below this line. --- Error message: E: Sub-process /usr/bin/dpkg returned an error code (1) A instalação de um pacote falhou. Tentando recuperar: Configurando console-common (0.7.86) ... Looking for keymap to install: br-abnt2 insserv: There is a loop between service checkroot and keyboard-setup if started insserv: loop involving service keyboard-setup at depth 14 insserv: loop involving service keymap at depth 13 insserv: There is a loop between service checkroot and keyboard-setup if started insserv: loop involving service mtab at depth 6 insserv: loop involving service checkroot at depth 5 insserv: loop involving service hostname at depth 4 insserv: loop involving service hwclock at depth 19 insserv: loop involving service module-init-tools at depth 20 insserv: exiting now without changing boot order! update-rc.d: error: insserv rejected the script header dpkg: erro processando console-common (--configure): sub-processo script post-installation instalado retornou estado de saída de erro 1 Erros foram encontrados durante o processamento de: console-common --- System information. --- Architecture: amd64 Kernel: Linux 3.1.0-1-amd64 Debian Release: wheezy/sid 500 unstablewww.debian-multimedia.org 500 unstablesft.if.usp.br 500 testing http.us.debian.org 500 stable dl.google.com --- Package information. --- Depends(Version) | Installed -+-=== debconf(= 0.5) | 1.5.41 OR debconf-2.0 | debianutils(= 1.13) | 4.1 console-data | 2:1.12-1 kbd | 1.15.3-7 OR console-tools (= 1:0.2.3dbs-54) | lsb-base(= 3.0) | 3.2-28 Package's Recommends field is empty. Package's Suggests field is empty. -- ASD Consultoria, Rio, RJ Arq. Sávio M Ramos Só usamos Linux desde 2000 www.debian.org ---End Message--- ---BeginMessage--- Source: console-common Source-Version: 0.7.87 We believe that the bug you reported is fixed in the latest version of console-common, which is due to be installed in the Debian FTP archive: console-common_0.7.87.dsc to main/c/console-common/console-common_0.7.87.dsc console-common_0.7.87.tar.gz to main/c/console-common/console-common_0.7.87.tar.gz console-common_0.7.87_all.deb to main/c/console-common/console-common_0.7.87_all.deb dh-consoledata_0.7.87_all.deb to main/c/console-common/dh-consoledata_0.7.87_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 650...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Perrier bubu...@debian.org (supplier of updated console-common 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 05 Dec 2011 21:08:35 +0100 Source: console-common Binary: console-common dh-consoledata Architecture: source all Version: 0.7.87 Distribution: unstable Urgency: low Maintainer: Alastair McKinstry mckins...@debian.org Changed-By: Christian Perrier bubu...@debian.org Description: console-common - basic infrastructure for text console configuration dh-consoledata - debhelper-based script to help packaging console data files Closes: 650995 Changes: console-common (0.7.87) unstable; urgency=low . * Drop dependency on $remote_fs that accidentally leaked in 0.7.86 init script. Closes: #650995 Checksums-Sha1: 125771c49c496b452902b1a9af49b3e605983e9b 1617 console-common_0.7.87.dsc 3661a834fb1466a0ebd8d077b6f60dd0e07aa1bf 171811 console-common_0.7.87.tar.gz 9d1ce6d8fce361345d30c7b1e4b531a568f9ea4b 128384
Processed: Re: Bug#620437: xmlrpc-epi: please use LDFLAGS, not LIBADD, for external lib dependencies
Processing commands for cont...@bugs.debian.org: severity 620437 serious Bug #620437 [xmlrpc-epi] xmlrpc-epi: please use LDFLAGS, not LIBADD, for external lib dependencies Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 620437: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620437 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650958: [Pkg-samba-maint] Bug#650958: Bug#650958: samba INTERNAL ERROR: Signal 11 - PANIC - BACKTRACE: 16 stack frames
Did that but the error remains. about var/lib: root@panda:~# ls /var/lib/samba/ account_policy.tdb ntdrivers.tdb.bak passdb.tdb registry.tdb usershares/ group_mapping.ldb.replaced ntforms.tdb.bak perfmon/secrets.tdb wins.dat group_mapping.tdb ntprinters.tdb.bak printers/ share_info.tdb wins.tdb root@panda:~# ls /var/lib/samba/*/ /var/lib/samba/perfmon/: /var/lib/samba/printers/: COLOR/ IA64/ W32ALPHA/ W32MIPS/ W32PPC/ W32X86/ WIN40/ x64/ /var/lib/samba/usershares/: On Mon, Dec 5, 2011 at 8:54 PM, Christian Perrier bubu...@debian.orgwrote: Quoting Tiago Caxias (tcx.talie...@gmail.com): $ ls /var/run/samba/ brlock.tdb gencache_notrans.tdb locking.tdb nmbd.pid notify.tdbserverid.tdb unexpected= connections.tdb gencache.tdb messages.tdb notify_onelevel.tdb printer_list.tdb sessionid.tdb Want me to clear that dir? Yep. It can't hurt anyway. Later on, we can try the same in /var/lib/samba but that one requires preserving files (depending on your setup, some files there can be important to keep). -- Tiago Caxias
Bug#651104: bup: FTBFS(kfreebsd) testsuite failure
Package: src:bup Version: 0.25~git2011.11.04-1 Severity: serious Tags: sid wheezy User: debian-...@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-...@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: ! lib/bup/t/txstat.py test_timespec_behavior: Traceback (most recent call last): File wvtest.py, line 123, in _runtest f() File /build/buildd-bup_0.25~git2011.11.04-1-kfreebsd-amd64-YzC4g3/bup-0.25~git2011.11.04/lib/bup/t/txstat.py, line 56, in test_timespec_behavior _helpers.bup_utime_ns(path, (frac_ts, frac_ts)) OSError: [Errno 78] Function not implemented: '/tmp/bup-tmetadata-_kb9pL/foo' ! txstat.py:56 [Errno 78] Function not implemented: '/tmp/bup-tmetadata-_kb9pL/foo' EXCEPTION 0.070s ok Full build log at https://buildd.debian.org/status/fetch.php?pkg=buparch=kfreebsd-amd64ver=0.25%7Egit2011.11.04-1stamp=1323104542 Regards Christoph If you have further questions please mail debian-...@lists.debian.org -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#620437: xmlrpc-epi: please use LDFLAGS, not LIBADD, for external lib dependencies
Hi Steve No sign of any progress on this bug in quite a while, and now it's causing build failures in Debian too with multi-arch. Are you planning to work on this in the near future? Ah sorry, I actually did this back in April and had everything staged in my git at https://robincornel...@github.com/robincornelius/xmlrpc-epi-debian.git but then never did that last step to finish off by getting it uploaded by a DD. Worse than that the upstream change log hints I fixed this upstream in Feb last year ;-/ I expect that git repro is lagging behind latest packaging policy now so will need another update, but hopefully a pretty trivial one. If you could take a peek and see if everything else is now fine with it i'll also check it over tomorrow when i'm in the office and see if we can get this uploaded. Robin Robin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
