Processed: found 570662 in 1.13-1
Processing commands for cont...@bugs.debian.org:
# still fails on alpha and ia64:
https://buildd.debian.org/status/package.php?p=powertop
found 570662 1.13-1
Bug #570662 {Done: Patrick Winnertz win...@debian.org} [src:powertop]
powertop: FTBFS: error: '__NR_perf_event_open' undeclared
Bug Marked as found in versions powertop/1.13-1; no longer marked as fixed in
versions powertop/1.13-1 and reopened.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
570662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570662
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: Bug#593703: sysvinit: X server does not start
Processing commands for cont...@bugs.debian.org: reassign 593703 fglrx-atieventsd Bug #593703 [sysvinit] sysvinit: X server does not start Bug reassigned from package 'sysvinit' to 'fglrx-atieventsd'. Bug No longer marked as found in versions sysvinit/2.88dsf-12. retitle 593703 Should fglrx-atieventsd init script start before kdm? Bug #593703 [fglrx-atieventsd] sysvinit: X server does not start Changed Bug title to 'Should fglrx-atieventsd init script start before kdm?' from 'sysvinit: X server does not start' severity 593703 serious Bug #593703 [fglrx-atieventsd] Should fglrx-atieventsd init script start before kdm? Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 593703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593703 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#593915: schroot: FTBFS on buildd due to --enable-doxygen and doxygen only in build-indep
Package: schroot Version: 1.4.9-1 Severity: serious Your package FTBFS on all buildds [0 because it misses doxygen: checking for btrfs... /sbin/btrfs checking for btrfsctl... /sbin/btrfsctl configure: error: in `/build/buildd-schroot_1.4.9-1-i386-A9D3ce/schroot-1.4.9/debian/build': configure: error: doxygen is not installed, but is required by schroot See `config.log' for more details checking for losetup... /sbin/losetup make: *** [debian/build/config.status] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Autodetect could help instead of --enable-doxygen since it is allready in build-indep. [0] https://buildd.debian.org/status/package.php?p=schroot Sebastian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fixed 589876 in 0.8.5~pre-1
Processing commands for cont...@bugs.debian.org: fixed 589876 0.8.5~pre-1 Bug #589876 [totem-plugin-arte] totem-plugin-arte: An error occurred: Location not found. There is no source info for the package 'totem-plugin-arte' at version '0.8.5~pre-1' with architecture '' Unable to make a source version for version '0.8.5~pre-1' Bug Marked as fixed in versions 0.8.5~pre-1. thanks Stopping processing here. Please contact me if you need assistance. -- 589876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589876 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#591515: ssmtp: CVE-2008-7258 buffer overflow
tag 591515 + unreproducible
thanks
Hi,
Ubuntu bug-report was filed against 2.62 and contains a PoC/testcase.
Current squeeze and sid contain latest 2.64, and the aforementioned
testcase doesn't fail.
Moreover, as it seems to be an off-by-one error, I think it was fixed
in later versions, as ssmtp.c now accounts for it:
1385 if(vsnprintf(buf, (BUF_SZ - 1), format, ap) == -1) {
1386 die(smtp_write() -- vsnprintf() failed);
1387 }
I'm tagging as unreproducible, as Anibal would certainly have more
knowledge about this than me to close it.
Cheers, Luca
--
.''`. ** Debian GNU/Linux ** | Luca Bruno (kaeso)
: :' : The Universal O.S.| lucab (AT) debian.org
`. `'` | GPG Key ID: 3BFB9FB3
`- http://www.debian.org | Debian GNU/Linux Developer
pgpDvf5LzxWSV.pgp
Description: PGP signature
Processed: ssmtp: CVE-2008-7258 buffer overflow
Processing commands for cont...@bugs.debian.org: tag 591515 + unreproducible Bug #591515 [ssmtp] CVE-2008-7258 buffer overflow Added tag(s) unreproducible. thanks Stopping processing here. Please contact me if you need assistance. -- 591515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591515 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#593917: Guake hogs a whole CPU core
Package: guake Version: 0.4.2-1 Severity: serious Recently in my Debian unstable, guake became noticably slower. The typing actually feels slower (keyboard latency), and 'top' reports that Python uses ~6% of my dual core (constantly), Xorg about 32%. That adds up to almost one whole core. Why is Xorg cpu usage relevant? because both two processes decrease down to zero (or almost zero) when guake is rolled-up (F12) or simply not in focus. Even when stracing guake, everything is peaceful when guake not focused. When I start to focus it prints lots of lines like the following: read(4, 0x2695f14, 4096)= -1 EAGAIN (Resource temporarily unavailable) I've been trying the vanilla guake 0.4.2, and same results. Furthermore, I've tried guake 0.4.1 on the same computer and same results. Thus I conclude that something in the environment (Xorg? Python or pygtk?) has triggered the problem, and it's not necessary that something is wrong within guake's code. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (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/bash Versions of packages guake depends on: ii gconf2 2.28.1-3GNOME configuration database syste ii libatk1.0-0 1.30.0-1The ATK accessibility toolkit ii libc62.11.2-2Embedded GNU C Library: Shared lib ii libcairo21.8.10-5The Cairo 2D vector graphics libra ii libfontconfig1 2.8.0-2.1 generic font configuration library ii libfreetype6 2.4.2-1 FreeType 2 font engine, shared lib ii libglib2.0-0 2.24.1-1The GLib library of C routines ii libgtk2.0-0 2.20.1-1The GTK+ graphical user interface ii libpango1.0-01.28.1-1Layout and rendering of internatio ii libpython2.6 2.6.6~rc2-1 Shared Python runtime library (ver ii libx11-6 2:1.3.3-3 X11 client-side library ii notification-daemon 0.5.0-2 daemon to displays passive pop-up ii python 2.6.5-13interactive high-level object-orie ii python-central 0.6.16 register and build utility for Pyt ii python-dbus 0.83.1-1simple interprocess messaging syst ii python-gconf 2.28.1-1Python bindings for the GConf conf ii python-glade22.17.0-4GTK+ bindings: Glade support ii python-notify0.1.1-2+b2 Python bindings for libnotify ii python-vte 1:0.24.3-1 Python bindings for the VTE widget guake recommends no packages. guake 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
Processed: Re: Bug#593856: gnucash: Crash when working on a split transaction: assertion failure in split-register-load.c
Processing commands for cont...@bugs.debian.org: severity 593856 serious Bug #593856 [gnucash] gnucash: Crash when working on a split transaction: assertion failure in split-register-load.c Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 593856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593856 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#591595: fixed in comixcursors 0.6.1-3
On söndagen den 22 augusti 2010, Ben Finney wrote: On 22-Aug-2010, Magnus Holmgren wrote: On tisdagen den 17 augusti 2010, Ben Finney wrote: * debian/preinst: + Handle the case where no cursor themes are yet installed (Closes: Bug#591595). However, it was clearly postinst that failed. What you need to do is ship an empty /usr/share/icons/default directory. Crystalcursors had the same bug not once but twice: 363059 and 582517. Do I understand you correctly that *every* cursor theme package needs to ship the same empty directory? That this is cause to make a lintian override for every such empty directory? Why? I've just recently begun looking into cursor packages, but as I understand it, that's how things stand currently. Strangely enough, lintian doesn't complain about the empty directory in crystalcursors. I haven't figured out why yet. Why is it not, rather, a directory provided by some single, common package? I don't think there is actually any suitable package to hold it. Cursor themes are handled on the client side of X, so x11-common and other server-side packages are out. I also don't think it's a good idea to put it libxcursor or any other client library package. I think that what it would come down to is a cursor-themes-common package that would contain nothing but that empty directory, and that's hardly worth it. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#591586: [Pkg-ace-devel] Bug#591586: ace: FTBFS on kfreebsd-*: sys/os_socket.h
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Revision 706 (http://svn.debian.org/viewsvn/pkg-ace?view=revrevision=706) contains new configuration file for KFreeBSD. I cannot state I ported ACE for this platform, but package compiles and builds. Could you, please, verify independently if the bug can be closed? BTW. Johnny, if this fixes the bug I think that config-kfreebsd.h from this patch: http://svn.debian.org/viewsvn/pkg-ace/trunk/debian/patches/12-create-config_kfreebsd.dpatch?view=markup should be commit to the upstream. Marek -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJMcQ4tAAoJED+r15Q8F6CGG98H/RjJH9m69TfXOCbit2eSDRj3 Deat8gWm6W3PGmEhVXRoZSnFjQ0rfhiBb4gPautRKEKne6M3aStze/ESAN/AJeXx vLDVrfB44RUeI/mPvRvAEyPokB7hKOAUO30SDWnC1cYl7zvyx1AmSBTBOs828SPD k+irps2CIN7RpTyg0yLj0RCCQXmvxfG5LdUHNPty3ohytejw7U6g4VOa4r5+KdeZ VJypvzY4t5/JQJj3tARDQoAJx+4bL2ekqFlanqAxUSygj27v3uApIdCO2HLXImXd JtcZB9Yuuz+/ywBErvQnkTqx+VprmR4PPTaCFscCeYHj5Ne93hwwqBPs+9l04ss= =h/i2 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593814: [pkg-fetchmail-maint] Bug#593814: fetchmail starts too early in init scripts
severity 593814 important thanks Hi, * rpnpif rpn...@free.fr [2010-08-21 12:57]: /etc/init.d/fetchmail has # Should-Start: $mail-transport-agent exim4 but fetchmail starts very early and failed to deliver mails because The mail transport agent is not ready. From the documentation: Should-Start: boot_facility_1 [boot_facility_2...] defines the facilities that if present should start before the service provided by the script. Nevertheless, the script can still start if the listed facilities are missing. Are you sure you have a service installed that provide the mail-transport-agent facility? If you do from my understanding this shouldn't happen. Which MTA are you using, is it maybe not registering itself as mail-transport-agent? Please also see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582475 This issue could loss mails. I suggest that /etc/init.d/fetchmail has : 1. # Required-Start:$network $local_fs $remote_fs $syslog $mail-transport-agent # Required-Stop: $remote_fs $mail-transport-agent From my understanding this should make no difference, if there is a mail-transport-agent facility it is started before fetchmail given the Should-Start. I can also think of setups without a mail transfer agent so making it a requirement is not appropriate in my opinion. 2. Fetchmail does not need usually to start immediately after the boot. A delay of few minutes (one ?) before the fetchmail start could improve security of delivering (for ie : to enable a good antispam starting). I don't quite understand this, where would you expect this delay to be implemented? So far I don't see the bug therefore downgrading the severity. Kind regards Nico -- Nico Golde - http://www.ngolde.de - n...@jabber.ccc.de - GPG: 0xA0A0 For security reasons, all text in this mail is double-rot13 encrypted. pgpwqEipNo9qL.pgp Description: PGP signature
Processed: Re: [pkg-fetchmail-maint] Bug#593814: fetchmail starts too early in init scripts
Processing commands for cont...@bugs.debian.org: severity 593814 important Bug #593814 [fetchmail] fetchmail starts too early in init scripts Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 593814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593814 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#593856: gnucash: Crash when working on a split transaction: assertion failure in split-register-load.c
Hi, On 2010-08-22 11:49:11 +0200, Micha Lenk wrote: thank you for providing the backtrace with the debug symbols installed. Are you able to reproduce the bug reliably? If yes, please make a backup of your current Gnucash file and the folder $HOME/.gnucash/ (just in case we need to trigger it again). I tried several ways to reproduce the bug, but unfortunately I couldn't. I basically did the following: I started to add a split transaction, but before I finished, I looked at another transaction in the file. I came back to the split transaction to add another line; I wanted to put an amount in Expense, and it appeared in Rebate, but I don't know if it was a bug, or if I put the amount at the wrong place by mistake. I don't remember what I did exactly then (I think I deleted the amount from Rebate and added it to Expense, but I'm not sure). The account for this new line was the same as the first one, so that a copy of the transaction appeared in the account. This is when I selected the copy that gnucash crashed. -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593936: pycompile: Could not import runpy module; IOError: [Errno 32] Broken pipe
Package: python-minimal Version: 2.6.5-13 Severity: serious In a clean chroot: # apt-get install python2.5-minimal python-markupsafe Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: mime-support python python-minimal python2.6 python2.6-minimal Suggested packages: python-doc python-tk python-profiler binfmt-support python2.6-doc python2.6-profiler Recommended packages: file python2.5 The following NEW packages will be installed: mime-support python python-markupsafe python-minimal python2.5-minimal python2.6 python2.6-minimal 0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/5316kB of archives. After this operation, 20.1MB of additional disk space will be used. Do you want to continue [Y/n]? debconf: delaying package configuration, since apt-utils is not installed Selecting previously deselected package mime-support. (Reading database ... 11496 files and directories currently installed.) Unpacking mime-support (from .../mime-support_3.48-1_all.deb) ... Selecting previously deselected package python2.6-minimal. Unpacking python2.6-minimal (from .../python2.6-minimal_2.6.6~rc2-1_i386.deb) ... Selecting previously deselected package python2.6. Unpacking python2.6 (from .../python2.6_2.6.6~rc2-1_i386.deb) ... Selecting previously deselected package python-minimal. Unpacking python-minimal (from .../python-minimal_2.6.5-13_all.deb) ... Selecting previously deselected package python. Unpacking python (from .../python_2.6.5-13_all.deb) ... Selecting previously deselected package python2.5-minimal. Unpacking python2.5-minimal (from .../python2.5-minimal_2.5.5-6_i386.deb) ... Selecting previously deselected package python-markupsafe. Unpacking python-markupsafe (from .../python-markupsafe_0.9.2-2_i386.deb) ... Setting up mime-support (3.48-1) ... update-alternatives: using /usr/bin/see to provide /usr/bin/view (view) in auto mode. Setting up python2.6-minimal (2.6.6~rc2-1) ... Setting up python2.6 (2.6.6~rc2-1) ... Setting up python-minimal (2.6.5-13) ... Setting up python (2.6.5-13) ... Setting up python2.5-minimal (2.5.5-6) ... Could not import runpy module Setting up python-markupsafe (0.9.2-2) ... Could not import runpy module Traceback (most recent call last): File /usr/bin/pycompile, line 281, in module main() File /usr/bin/pycompile, line 265, in main compile(files, versions, e_patterns) File /usr/bin/pycompile, line 195, in compile pipe.send(fn) File /usr/bin/pycompile, line 177, in py_compile stdin.write(filename + '\n') IOError: [Errno 32] Broken pipe dpkg: error processing python-markupsafe (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: python-markupsafe E: Sub-process /usr/bin/dpkg returned an error code (1) -- Jakub Wilk signature.asc Description: Digital signature
Bug#593898: gnustep-back-common: Fails to upgrade in postinst script
Hi, Yavor Doganov wrote: Upgrading gnustep-back-common fails (at least on kfreebsd-i386) in the postinst script. Adding a set -x to the script reveals mknfonts as cause: Thanks for the report. Could you please rebuild mknfonts.tool with noopt nostrip and post the gdb backtrace from `mknfonts /usr/share/fonts/truetype/some-font-you-have-installed'? In gnustep2.txt is the command postinst called (with all fonts, about 70kB :-) !545 Z35 ?0 L1 r...@metisse:ttyp3 (/usr/bin/zsh) 14:44:00 [/tmp] # `cat gnustep2.txt` Error: libkvm does not return arguments for the current process this may be due to a bug (undocumented feature) in libkvm which fails to get arguments unless /proc is mounted. If so, you can mount the /proc filesystem or reconfigure/build gnustep-base with --enable-fake-main as a workaround, and should report the bug to the maintainer of libkvm on your operating system. [1]36425 abort (core dumped) `cat gnustep2.txt` !546 Z36 ?134 L1 r...@metisse:ttyp3 (/usr/bin/zsh) 14:44:26 [/tmp] # gdb =mknfonts mknfonts.core GNU gdb (GDB) 7.1-debian Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-kfreebsd-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/mknfonts...done. [New Thread 100974] Reading symbols from /usr/lib/libfreetype.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfreetype.so.6 Reading symbols from /usr/lib/libgnustep-base.so.1.20...Reading symbols from /usr/lib/debug/usr/lib/libgnustep-base.so.1.20.1...done. done. Loaded symbols for /usr/lib/libgnustep-base.so.1.20 Reading symbols from /usr/lib/libobjc.so.2...Reading symbols from /usr/lib/debug/usr/lib/libobjc.so.2.0.0...done. done. Loaded symbols for /usr/lib/libobjc.so.2 Reading symbols from /lib/i686/cmov/libc.so.0.1...(no debugging symbols found)...done. Loaded symbols for /lib/i686/cmov/libc.so.0.1 Reading symbols from /usr/lib/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libz.so.1 Reading symbols from /lib/i686/cmov/libpthread.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/i686/cmov/libpthread.so.0 Reading symbols from /usr/lib/libdns_sd.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libdns_sd.so.1 Reading symbols from /usr/lib/libgnutls.so.26...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgnutls.so.26 Reading symbols from /usr/lib/libgcrypt.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgcrypt.so.11 Reading symbols from /usr/lib/libxslt.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libxslt.so.1 Reading symbols from /usr/lib/libxml2.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libxml2.so.2 Reading symbols from /usr/lib/libffi.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libffi.so.5 Reading symbols from /lib/libkvm.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/libkvm.so.0 Reading symbols from /lib/i686/cmov/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/i686/cmov/libdl.so.2 Reading symbols from /lib/i686/cmov/libm.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/i686/cmov/libm.so.1 Reading symbols from /lib/libgcc_s.so.1...Reading symbols from /usr/lib/debug/lib/libgcc_s.so.1...done. done. Loaded symbols for /lib/libgcc_s.so.1 Reading symbols from /lib/ld.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/ld.so.1 Reading symbols from /usr/lib/libavahi-client.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libavahi-client.so.3 Reading symbols from /lib/libdbus-1.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/libdbus-1.so.3 Reading symbols from /usr/lib/libavahi-common.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libavahi-common.so.3 Reading symbols from /usr/lib/libtasn1.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libtasn1.so.3 Reading symbols from /usr/lib/libgpg-error.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgpg-error.so.0 Reading symbols from /lib/libbsd.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/libbsd.so.0 Core was generated by `mknfonts'. Program terminated with signal 6, Aborted. #0 0x284c05b7 in kill () from /lib/i686/cmov/libc.so.0.1 (gdb) bt #0 0x284c05b7 in kill () from /lib/i686/cmov/libc.so.0.1 #1 0x285de5b0 in pthread_kill () from /lib/i686/cmov/libpthread.so.0 #2 0x285de5f6 in raise () from /lib/i686/cmov/libpthread.so.0 #3 0x284c0454 in raise () from
Bug#581940: gorm.app: FTBFS with gnustep-base/1.20.0: GormFunctions.m:354: error: ‘GSMethodList’ undeclared (first use in this function)
On Sat, 21 Aug 2010 22:33:53 +0200, Mehdi Dogguy me...@dogguy.org wrote: On 0, Yavor Doganov ya...@gnu.org wrote: В 16:15 +0200 на 12.08.2010 (чт), Gürkan Sengün написа: I see, I don't know, do you have a sponsor? Of course, how would the packages end up in the archive otherwise :-) Luca Falavigna dktrkranz and Barry deFreese bdefreese are my (GNUstep) sponsors these days -- I usually send an RFS request to -mentors, and it gets automagically uploaded fairly quickly. I've got these packages updated, test installed, and run them with your updated gnustep libraries, and they worked just fine: I don't doubt that; I believe the actual problem is not with sponsoring them but persuading the release team to unblock them. I'd say make their life easier and postpone these uploads for after the release. Right. Do you intend to upload gorm.app soon? It's one of the failing packages and we need to make it build with the current gnustep suite. Regards, yes i have the packages ready, as you can see from the gnustep devel mailinglist, it's on mentors.debian.org waiting for a sponsor. yours, gurkan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593936: pycompile: Could not import runpy module; IOError: [Errno 32] Broken pipe
forcemerge 593936 593681 reassign 593936 python2.5 2.5.5-6 retitle 593936 please move runpy.py from python2.5 to python2.5-minimal thanks pycompile needs runpy module. Please follow changes in python2.6 and python2.7 and move this module to python2.5-minimal binary package. TIA signature.asc Description: Digital signature
Processed (with 1 errors): Re: Bug#593936: pycompile: Could not import runpy module; IOError: [Errno 32] Broken pipe
Processing commands for cont...@bugs.debian.org: forcemerge 593936 593681 Bug#593936: pycompile: Could not import runpy module; IOError: [Errno 32] Broken pipe Bug#593681: python-markupsafe: installation broken Mismatch - only Bugs in the same package can be forcibly merged: Bug 593681 is not in the same package as 593936 reassign 593936 python2.5 2.5.5-6 Bug #593936 [python-minimal] pycompile: Could not import runpy module; IOError: [Errno 32] Broken pipe Bug reassigned from package 'python-minimal' to 'python2.5'. Bug No longer marked as found in versions python-defaults/2.6.5-13. Bug #593936 [python2.5] pycompile: Could not import runpy module; IOError: [Errno 32] Broken pipe Bug Marked as found in versions python2.5/2.5.5-6. retitle 593936 please move runpy.py from python2.5 to python2.5-minimal Bug #593936 [python2.5] pycompile: Could not import runpy module; IOError: [Errno 32] Broken pipe Changed Bug title to 'please move runpy.py from python2.5 to python2.5-minimal' from 'pycompile: Could not import runpy module; IOError: [Errno 32] Broken pipe' thanks Stopping processing here. Please contact me if you need assistance. -- 593936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593936 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: Bug#593681: python-markupsafe: installation broken
Processing commands for cont...@bugs.debian.org: reassign 593681 python2.5 2.5.5-6 Bug #593681 [python-markupsafe] python-markupsafe: installation broken Bug reassigned from package 'python-markupsafe' to 'python2.5'. Bug No longer marked as found in versions markupsafe/0.9.2-1. Bug #593681 [python2.5] python-markupsafe: installation broken Bug Marked as found in versions python2.5/2.5.5-6. forcemerge 593936 593681 Bug#593936: please move runpy.py from python2.5 to python2.5-minimal Bug#593681: python-markupsafe: installation broken Forcibly Merged 593681 593936. thanks Stopping processing here. Please contact me if you need assistance. -- 593936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593936 593681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593681 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#593898: gnustep-back-common: Fails to upgrade in postinst script
reassign libgnustep-base1.20 1.20.1-2 retitle 593898 [kfreebsd] NSProcessInfo fails to obtain argument vectors affects 593898 gnustep-back-common thanks Thanks, it is clear where the error lies: Error: libkvm does not return arguments for the current process this may be due to a bug (undocumented feature) in libkvm which fails to get arguments unless /proc is mounted. If so, you can mount the /proc filesystem or reconfigure/build gnustep-base with --enable-fake-main as a workaround, and Configuring with --enable-fake-main should not be necessary on GNU/kFreeBSD, because libkvm is supposed to do its job, obtaining the process arguments as expected. --enable-fake-main is a last resort, for platforms where this information cannot be gathered. should report the bug to the maintainer of libkvm on your operating system. For now, I am hesitating to reassign, because that may be a bug in gnustep-base in its [HAVE_KVM_ENV] code. Can you compile (just `make', you need libgnustep-base-dev) and run the attached test program this way: while true; do for d in `expr $((d + 1))`; do ./obj/test `seq $d`; done; done Obviously, NSProcessInfo + libkvm works in the usual scenario (few arguments), otherwise many GNUstep packages would FTBFS on GNU/kFreeBSD (the build process invokes programs like pl2link with arguments). test.m Description: Binary data GNUmakefile Description: Binary data
Processed: severity of 554582 is important
Processing commands for cont...@bugs.debian.org: # never built on ia64 severity 554582 important Bug #554582 [libsmbios] libsmbios_2.0.3.dfsg-1(ia64/unstable): FTBFS: matching constraint does not allow a register Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 554582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554582 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#528484: libsmbios-bin: process dellWirelessCtl eats up 99% CPU exiting powersaving
severity 528484 normal thanks Nicola, On Wed, May 13, 2009 at 10:12:29AM +0200, Nicola Ruggero wrote: When exiting powersave (standby) and wireless switch is on, this process eats up 99% CPU making the system slooow and unusable. (Ten minutes to get a shell for killing it) The system become usable again after killing. Today for the first time the process has gone crazy even if the wireless switch was off. I suppose this was a one-off event at yours? Otherwise I'd suspect that more people would've filed bugs or commented on this bug. This is only a minor feature of the package, IMO. So I'm downgrading the severity to `normal'. Kind regards, Philipp Kern signature.asc Description: Digital signature
Processed: Re: Bug#528484: libsmbios-bin: process dellWirelessCtl eats up 99% CPU exiting powersaving
Processing commands for cont...@bugs.debian.org: severity 528484 normal Bug #528484 [libsmbios-bin] libsmbios-bin: process dellWirelessCtl eats up 99% CPU exiting powersaving Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 528484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528484 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#593898: gnustep-back-common: Fails to upgrade in postinst script
Hi, Yavor Doganov wrote: Can you compile (just `make', you need libgnustep-base-dev) and run the attached test program this way: while true; do for d in `expr $((d + 1))`; do ./obj/test `seq $d`; done; done Modified it a little bit so that it stops when it fails: !539 Z32 ?0 L1 a...@metisse:ttyp6 (-su) 16:50:58 [/tmp] i=0; while test $i -eq 0; do for d in `expr $((d + 1))`; do ./obj/test `seq $d`; i=$?; done; done Arguments given: 3 Arguments given: 4 Arguments given: 5 Arguments given: 6 Arguments given: 7 Arguments given: 8 [...] Arguments given: 508 Arguments given: 509 Arguments given: 510 Arguments given: 511 Arguments given: 512 Error: libkvm does not return arguments for the current process this may be due to a bug (undocumented feature) in libkvm which fails to get arguments unless /proc is mounted. If so, you can mount the /proc filesystem or reconfigure/build gnustep-base with --enable-fake-main as a workaround, and should report the bug to the maintainer of libkvm on your operating system. Obviously, NSProcessInfo + libkvm works in the usual scenario (few arguments), otherwise many GNUstep packages would FTBFS on GNU/kFreeBSD (the build process invokes programs like pl2link with arguments). Seems so. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#505589: marked as done (FTBFS with GCC 4.4: missing #include)
Your message dated Sun, 22 Aug 2010 15:02:17 +
with message-id e1onc3t-0004dc...@franck.debian.org
and subject line Bug#505589: fixed in libsmbios 2.0.3.dfsg-1.1
has caused the Debian Bug report #505589,
regarding FTBFS with GCC 4.4: missing #include
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.)
--
505589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libsmbios
Version: 2.0.3.dfsg-1
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.4
Tags: patch
Your package fails to build with the upcoming GCC 4.4. Version 4.4
has not been released yet but I'm building with a snapshot in order
to find errors and give people an advance warning.
GCC 4.4 cleaned up some more C++ headers. You always have to #include
headers directly and cannot rely for things to be included indirectly.
You can reproduce this problem with gcc-snapshot from unstable.
Automatic build of libsmbios_2.0.3.dfsg-1 on em64t by sbuild/amd64 0.53
...
g++ -DPACKAGE_NAME=\libsmbios\ -DPACKAGE_TARNAME=\libsmbios\
-DPACKAGE_BUGREPORT=\\ -DPACKAGE=\libsmbios\ -DSTDC_HEADERS=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DSTDC_HEADERS=1 -DHAVE_LIBINTL_H=1
-DHAVE_LIMITS_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_SYS_FILE_H=1
-DHAVE_UNISTD_H=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -DHAVE_PTRDIFF_T=1
-DHAVE_STDLIB_H=1 -DHAVE_MALLOC=1 -DHAVE_STDLIB_H=1 -DHAVE_UNISTD_H=1
-DHAVE_GETPAGESIZE=1 -DHAVE_MMAP=1 -DHAVE_GETPAGESIZE=1 -DHAVE_MEMMOVE=1
-DHAVE_MEMSET=1 -DHAVE_MUNMAP=1 -DHAVE_STRERROR=1 -DHAVE_STRNDUP=1
-DHAVE_STRTOL=1 -DHAVE_STRTOUL=1 -DVERSION=\2.0.3\
-DPACKAGE_VERSION=\2.0.3\ -DPACKAGE_STRING=\libsmbios 2.0.3\ -I.
-I./include -I./include -I./libraries/common -I./libraries/common -g -O2 -MT
libraries/cmos/libraries_libsmbios_la-CmosRW.lo -MD -MP -MF
libraries/cmos/.deps/libraries_libsmbios_la-CmosRW.Tpo -c
libraries/cmos/CmosRW.cpp -fPIC -DPIC -o
libraries/cmos/.libs/libraries_libsmbios_la-CmosRW.o
In file included from ./include/smbios/config.hpp:36,
from ./include/smbios/compat.h:23,
from libraries/cmos/CmosRW.cpp:21:
./include/smbios/config/compiler/gcc.hpp:99:7: warning: #warning Unknown
compiler version - please run the configure tests and report the results
libraries/cmos/CmosRW.cpp: In member function 'virtual u8
cmos::CmosRWFile::readByte(u32, u32, u32) const':
libraries/cmos/CmosRW.cpp:125: error: 'fopen' was not declared in this scope
libraries/cmos/CmosRW.cpp:129: error: 'fseek' was not declared in this scope
libraries/cmos/CmosRW.cpp:130: error: 'fread' was not declared in this scope
libraries/cmos/CmosRW.cpp:131: error: 'fclose' was not declared in this scope
libraries/cmos/CmosRW.cpp: In member function 'virtual void
cmos::CmosRWFile::writeByte(u32, u32, u32, u8) const':
libraries/cmos/CmosRW.cpp:147: error: 'fopen' was not declared in this scope
libraries/cmos/CmosRW.cpp:151: error: 'fseek' was not declared in this scope
libraries/cmos/CmosRW.cpp:152: error: 'fwrite' was not declared in this scope
libraries/cmos/CmosRW.cpp:153: error: 'fclose' was not declared in this scope
libraries/cmos/CmosRW.cpp:154: error: 'fflush' was not declared in this scope
make[2]: *** [libraries/cmos/libraries_libsmbios_la-CmosRW.lo] Error 1
make[2]: Leaving directory `/build/tbm/libsmbios-2.0.3.dfsg'
--- libraries/smi/SmiImpl.h~2008-11-13 18:48:27.0 +
+++ libraries/smi/SmiImpl.h 2008-11-13 18:48:32.0 +
@@ -22,6 +22,8 @@
#include SmiLowLevel.h
#include ExceptionImpl.h
+#include cstdio
+
namespace smi
{
// define our exceptions
--- libraries/smbios/SmbiosStrategy_Linux.cpp~ 2008-11-13 18:47:29.0
+
+++ libraries/smbios/SmbiosStrategy_Linux.cpp 2008-11-13 18:47:34.0
+
@@ -20,6 +20,7 @@
#define LIBSMBIOS_SOURCE
#include smbios/compat.h
+#include cstdio
#include sstream
#include string.h
--- libraries/memory/Memory_Linux.cpp~ 2008-11-13 18:46:18.0 +
+++ libraries/memory/Memory_Linux.cpp 2008-11-13 18:46:25.0 +
@@ -22,6 +22,7 @@
#include errno.h
#include sys/mman.h /* mmap */
+#include stdio.h
#include unistd.h /* getpagesize */
#include string.h /* memcpy etc. */
--- libraries/cmos/CmosRW.cpp~ 2008-11-13 18:45:18.0 +
+++ libraries/cmos/CmosRW.cpp 2008-11-13 18:45:25.0 +
@@ -19,6 +19,7 @@
Processed: controlling
Processing commands for cont...@bugs.debian.org: tags #593703 squeeze Bug #593703 [fglrx-atieventsd] Should fglrx-atieventsd init script start before kdm? Added tag(s) squeeze. found #593703 1:10-7-1 Bug #593703 [fglrx-atieventsd] Should fglrx-atieventsd init script start before kdm? Bug Marked as found in versions fglrx-driver/1:10-7-1. severity #593703 important Bug #593703 [fglrx-atieventsd] Should fglrx-atieventsd init script start before kdm? Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 593703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593703 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#593400: marked as done (fbi: broken kfreebsd-* and hurd-* binaries)
Your message dated Sun, 22 Aug 2010 17:47:13 +0200 with message-id 20100822154713.ga2...@galadriel.inutil.org and subject line Re: Bug#593400: fbi: broken kfreebsd-* and hurd-* binaries has caused the Debian Bug report #593400, regarding fbi: broken kfreebsd-* and hurd-* binaries 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.) -- 593400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fbi Version: 2.07-2 Severity: grave Justification: renders package unusable (on kfreebsd-* and hurd-*) kfreebsd-* and hurd-* fbi binaries are virtually empty: $ dpkg -c fbi_2.07-2_kfreebsd-i386.deb | grep -v /$ -rw-r--r-- root/root 947 2009-08-31 02:53 ./usr/share/doc/fbi/copyright -rw-r--r-- root/root 4229 2009-08-31 02:53 ./usr/share/doc/fbi/changelog.Debian.gz -rw-r--r-- root/root 2353 2009-08-31 02:53 ./usr/lib/mime/packages/fbi $ dpkg -c fbi_2.07-2_kfreebsd-amd64.deb | grep -v /$ -rw-r--r-- root/root 947 2009-08-31 02:59 ./usr/share/doc/fbi/copyright -rw-r--r-- root/root 4229 2009-08-31 02:59 ./usr/share/doc/fbi/changelog.Debian.gz -rw-r--r-- root/root 2353 2009-08-31 02:59 ./usr/lib/mime/packages/fbi $ dpkg -c fbi_2.07-2_hurd-i386.deb | grep -v /$ -rw-r--r-- root/root 947 2009-08-31 03:18 ./usr/share/doc/fbi/copyright -rw-r--r-- root/root 4229 2009-08-31 03:18 ./usr/share/doc/fbi/changelog.Debian.gz -rw-r--r-- root/root 2353 2009-08-31 03:18 ./usr/lib/mime/packages/fbi -- Jakub Wilk signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Version: 2.07-4 On Sat, Aug 21, 2010 at 01:35:16PM +0200, Luca Bruno wrote: According to buildd logs[0], fbi FTBFS on any non-linux arch. This seems quite expected, as fbi heavily rely on linux/fb.h. It also looks like some issues are due to a spurious patch (debian-changes-2.07-3 [1]) which was auto-generated with latest upload. It hard-codes configuration values (which are correct only on linux-any) and let the config phase being skipped. IMHO, fbi binary should be declared arch: linux-any, aforementioned patch should be dropped and Make.config removed by clean target. Also, removal should be asked for previous fbi binaries in squeeze on kfreebsd and hurd. Moritz, can you please take care of this? I've limited the archs in 2.07-4 (just uploaded) and filed a removal request for the broken packages. Cheers, Moritz ---End Message---
Bug#592712: bash FTBS imagemagick on HPPA
On Thu, Aug 12, 2010 at 10:55:00AM +0200, Bastien ROUCARIES wrote: Adding debian-hppa to CC, this is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592712 Cheers, Moritz Package:bash User: debian-h...@lists.debian.org Usertags: hppa severity: serious FTBS with (http://tinyurl.com/2b5bbqo) /usr/bin/install -c -m 644 ./www/Magick++/thumbnail-sample-plain.jpg /build/buildd-imagemagick_6.6.0.4-2.2-hppa-WKfFIA/imagemagick-6.6.0.4/debian/tmp/usr/share/doc/imagemagick/www/Magick++ test -z /usr/share/ImageMagick-6.6.0 || /bin/mkdir -p /build/buildd-imagemagick_6.6.0.4-2.2-hppa-WKfFIA/imagemagick-6.6.0.4/debian/tmp/usr/share/ImageMagick-6.6.0 /usr/bin/install -c -m 644 LICENSE ChangeLog NEWS.txt '/build/buildd-imagemagick_6.6.0.4-2.2-hppa-WKfFIA/imagemagick-6.6.0.4/debian/tmp/usr/share/ImageMagick-6.6.0' test -z /usr/lib/ImageMagick-6.6.0/modules-Q16/filters || /bin/mkdir -p /build/buildd-imagemagick_6.6.0.4-2.2-hppa-WKfFIA/imagemagick-6.6.0.4/debian/tmp/usr/lib/ImageMagick-6.6.0/modules-Q16/filters /bin/bash ./libtool --mode=install /usr/bin/install -c filters/analyze.la '/build/buildd-imagemagick_6.6.0.4-2.2-hppa-WKfFIA/imagemagick-6.6.0.4/debian/tmp/usr/lib/ImageMagick-6.6.0/modules-Q16/filters' libtool: install: warning: relinking `filters/analyze.la' libtool: install: (cd /build/buildd-imagemagick_6.6.0.4-2.2-hppa-WKfFIA/imagemagick-6.6.0.4; /bin/bash /build/buildd-imagemagick_6.6.0.4-2.2-hppa-WKfFIA/imagemagick-6.6.0.4/libtool --silent --tag CC --mode=relink gcc -std=gnu99 -std=gnu99 -I/usr/include/lqr-1 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -fopenmp -g -O2 -Wall -W -pthread -no-undefined -export-symbols-regex .* -shared -module -avoid-version -L/usr/lib/X11 -o filters/analyze.la -rpath /usr/lib/ImageMagick-6.6.0/modules-Q16/filters filters/filters_analyze_la-analyze.lo magick/libMagickCore.la -lm -inst-prefix-dir /build/buildd-imagemagick_6.6.0.4-2.2-hppa-WKfFIA/imagemagick-6.6.0.4/debian/tmp) malloc: ../bash/parse.y:4620: assertion botched malloc: block on free list clobbered Aborting/libtool: line 964: 30018 Aborted /bin/bash /build/buildd-imagemagick_6.6.0.4-2.2-hppa-WKfFIA/imagemagick-6.6.0.4/libtool --silent --tag CC --mode=relink gcc -std=gnu99 -std=gnu99 -I/usr/include/lqr-1 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -fopenmp -g -O2 -Wall -W -pthread -no-undefined -export-symbols-regex .* -shared -module -avoid-version -L/usr/lib/X11 -o filters/analyze.la -rpath /usr/lib/ImageMagick-6.6.0/modules-Q16/filters filters/filters_analyze_la-analyze.lo magick/libMagickCore.la -lm -inst-prefix-dir /build/buildd-imagemagick_6.6.0.4-2.2-hppa-WKfFIA/imagemagick-6.6.0.4/debian/tmp libtool: install: error: relink `filters/analyze.la' with the above command before installing it make[3]: *** [install-filtersLTLIBRARIES] Error 1 make[3]: Leaving directory `/build/buildd-imagemagick_6.6.0.4-2.2-hppa-WKfFIA/imagemagick-6.6.0.4' make[2]: *** [install-am] Error 2 make[2]: Leaving directory `/build/buildd-imagemagick_6.6.0.4-2.2-hppa-WKfFIA/imagemagick-6.6.0.4' make[1]: *** [install] Error 2 make[1]: Leaving directory `/build/buildd-imagemagick_6.6.0.4-2.2-hppa-WKfFIA/imagemagick-6.6.0.4' make: *** [install] Error 2 make: *** Waiting for unfinished jobs -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593915: [buildd-tools-devel] Bug#593915: schroot: FTBFS on buildd due to --enable-doxygen and doxygen only in build-indep
tags 593915 + fixed-upstream pending thanks On Sun, Aug 22, 2010 at 11:01:38AM +0200, Sebastian Andrzej Siewior wrote: Package: schroot Version: 1.4.9-1 Severity: serious Your package FTBFS on all buildds [0 because it misses doxygen: Autodetect could help instead of --enable-doxygen since it is allready in build-indep. [0] https://buildd.debian.org/status/package.php?p=schroot Yes, I've seen, thanks. I'm in the middle of preparing a new upload to fix this, it's tagged in git and I'm just doing a rebuild with sbuild to make sure it's correct (with and without -s -A to test binary- only building). Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. signature.asc Description: Digital signature
Processed: Re: [buildd-tools-devel] Bug#593915: schroot: FTBFS on buildd due to --enable-doxygen and doxygen only in build-indep
Processing commands for cont...@bugs.debian.org: tags 593915 + fixed-upstream pending Bug #593915 [schroot] schroot: FTBFS on buildd due to --enable-doxygen and doxygen only in build-indep Added tag(s) pending and fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 593915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593915 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#593829: sabnzbdplus: sabnzbd.ini defaults to world-readable
Thanks for the report. The init script isn't the place to fix this. While definitely convenient, using it is by no means mandatory. Hence, fixes in there won't have any effect in case the program is started by other means. In addition, I dislike the concept of an init script making changes inside users' home directories. The discussion on the upstream forums I assume you are referring to had people suggesting encryption for the ini file, which is indeed useless for the reasons given by the developers. Initially creating the file with more secure permissions (as compared to common default umasks of 022 or 002) might make sense though, while not doing any damage. I'll discuss with upstream first. BTW: I'll leave severity and tags alone for now, although I don't really think this is a security issue in sabnzbdplus. More like the logical result of a not-very-good-for-privacy umask of 002 or 022 (which impacts any program that creates files), and/or bad security practices such as reusing login passwords. signature.asc Description: PGP signature
Processed (with 1 errors): Bug#593898: gnustep-back-common: Fails to upgrade in postinst script
Processing commands for cont...@bugs.debian.org: reassign libgnustep-base1.20 1.20.1-2 Unknown command or malformed arguments to command. retitle 593898 [kfreebsd] NSProcessInfo fails to obtain argument vectors Bug #593898 [gnustep-back-common] gnustep-back-common: Fails to upgrade in postinst script Changed Bug title to '[kfreebsd] NSProcessInfo fails to obtain argument vectors' from 'gnustep-back-common: Fails to upgrade in postinst script' affects 593898 gnustep-back-common Bug #593898 [gnustep-back-common] [kfreebsd] NSProcessInfo fails to obtain argument vectors Added indication that 593898 affects gnustep-back-common thanks Stopping processing here. Please contact me if you need assistance. -- 593898: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593898 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#593041: imagemagick: FTBFS: libMagickWand.so: No such file: No such file or directory
On Sun, Aug 15, 2010 at 09:44:16 +0200, Lucas Nussbaum wrote: Source: imagemagick Version: 8:6.6.0.4-2.2 Severity: serious Tags: squeeze sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20100815 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: g++: /build/user-imagemagick_6.6.0.4-2.2-amd64-1dMQS3/imagemagick-6.6.0.4/wand/.libs/libMagickWand.so: No such file or directory make[3]: *** [Magick++/demo/button] Error 1 make[3]: *** Waiting for unfinished jobs test -z /usr/lib/ImageMagick-6.6.0/modules-Q16/coders || /bin/mkdir -p /build/user-imagemagick_6.6.0.4-2.2-amd64-1dMQS3/imagemagick-6.6.0.4/debian/tmp/usr/lib/ImageMagick-6.6.0/modules-Q16/coders /usr/bin/ld: /build/user-imagemagick_6.6.0.4-2.2-amd64-1dMQS3/imagemagick-6.6.0.4/wand/.libs/libMagickWand.so: No such file: No such file or directory collect2: ld returned 1 exit status It built just fine on the buildds (and here) 10 days ago... Cheers, Julien signature.asc Description: Digital signature
Processed: reassign 593898 to libgnustep-base1.20
Processing commands for cont...@bugs.debian.org: reassign 593898 libgnustep-base1.20 1.20.1-2 Bug #593898 [gnustep-back-common] [kfreebsd] NSProcessInfo fails to obtain argument vectors Bug reassigned from package 'gnustep-back-common' to 'libgnustep-base1.20'. Bug No longer marked as found in versions gnustep-back/0.18.0-2. Bug #593898 [libgnustep-base1.20] [kfreebsd] NSProcessInfo fails to obtain argument vectors Bug Marked as found in versions gnustep-base/1.20.1-2. thanks Stopping processing here. Please contact me if you need assistance. -- 593898: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593898 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#593566: - Root access to cn=config not working after upgrade
Package: slapd
Severity: normal
Hi Matthijs,
Thanks for the patch. I came up with a different approach to this patch.
On converting the slapd.conf to slapd.d there is an entry olcAccess
added to olcDatabase=cn=config database, namely:
olcAccess: {0}to * by * none
That's right, removing the automatically added olcAccess attriubte is
the other solution for cn= config, but it does not help in the presence of
other olcAccess or olcAuthzRegex statements in the local setup.
Another olcAccess line wouldn't help as this was the first entry so
replacing this line was the correct way. But I think your approach is
better so I'll apply your patch and will test it.
I am sorry to disagree here.
I checked that it works before I sent my patch.
The olcAccess attributes are evaluated in numerical order of the
numbers X given inside the curly braces {X} that start the attribute's
values.
I used X=-1 to be sure that the olcAccess statement for cn=localroot
gets evaluated first.
BTW the same applies for olcAuthzRegex.
I have a local olcAuthzRegex based on uidNumber and gidNumber similar to
the one you use to map uidNumber=0+gidNumber=0 to cn=localroot.
With the X=-1 on my patch I made sure that the olcAuthzRegex for
cn=localroot triggers before my local configuration.
I checked it by trying to access cn=config as root (which worked)
and with my local admin account (which did not work).
Although this caused a change in the behaviour of my system I considered
the patch the best (i.e. simplest/most elegant/...) solution.
And it matches README.Debian ;-)
Best
PEter
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 591865
Processing commands for cont...@bugs.debian.org: tags 591865 + patch Bug #591865 [minicom] minicom: package purge (after dependencies removal) fails Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 591865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591865 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#591129: libgtk2-spell-perl: FTBFS: enchant error for language: en at t/0.GtkSpell.t line 34.
On Sat, Jul 31, 2010 at 08:41:13PM -0400, Chris Butler wrote: On Sat, Jul 31, 2010 at 06:42:45PM -0400, Lucas Nussbaum wrote: Relevant part: make[2]: Entering directory `/build/user-libgtk2-spell-perl_1.03-4-amd64-twELDx/libgtk2-spell-perl-1.03' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'blib/lib', 'blib/arch') t/*.t Xlib: extension RANDR missing on display :99.0. enchant error for language: en at t/0.GtkSpell.t line 34. This most probably broke in June with enchant_1.6.0-1. The failing test seems to be breaking at the point where it calls gtk_new_attach (which is where the language is set). In this case, it calls it with a NULL lang setting, which causes gtkspell to try looking at the LANG environment variable. If this is not set, it falls back to en. It's looking for an English dictionary, such as in the myspell-en-us or hunspell-en-us packages. Building with either of those makes the tests succeed. It would probably also be good to set LC_ALL=C for the test suite so that user locale settings don't affect the build. (Setting LC_ALL=en_US or something like that works too, but then we need the locales package or perl will complain about unknown locale settings.) -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593898: gnustep-back-common: Fails to upgrade in postinst script
reassign 593898 gnustep-back-common 0.18.0-2 retitle 593898 Arguments passed to mknfonts in postinst may exceed operating system limit tags 593898 + pending thanks Thanks for performing the test. Axel Beckert wrote: Arguments given: 512 Error: libkvm does not return arguments for the current process So, it appears that on GNU/kFreeBSD the maximum amount of arguments is much lower, which leads to the `abort' call in +[NSProcessInfo load]. This will fail on GNU/Linux too, if there is a sheer amount of system fonts installed (valid case). The obvious solution is to run `mknfonts' in a loop, passing it one font as argument at a time. I'll fix this shortly, thanks! -- 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#593898: gnustep-back-common: Fails to upgrade in postinst script
Processing commands for cont...@bugs.debian.org: reassign 593898 gnustep-back-common 0.18.0-2 Bug #593898 [libgnustep-base1.20] [kfreebsd] NSProcessInfo fails to obtain argument vectors Bug reassigned from package 'libgnustep-base1.20' to 'gnustep-back-common'. Bug No longer marked as found in versions gnustep-base/1.20.1-2. Bug #593898 [gnustep-back-common] [kfreebsd] NSProcessInfo fails to obtain argument vectors Bug Marked as found in versions gnustep-back/0.18.0-2. retitle 593898 Arguments passed to mknfonts in postinst may exceed operating system limit Bug #593898 [gnustep-back-common] [kfreebsd] NSProcessInfo fails to obtain argument vectors Changed Bug title to 'Arguments passed to mknfonts in postinst may exceed operating system limit' from '[kfreebsd] NSProcessInfo fails to obtain argument vectors' tags 593898 + pending Bug #593898 [gnustep-back-common] Arguments passed to mknfonts in postinst may exceed operating system limit Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 593898: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593898 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#591129: libgtk2-spell-perl: FTBFS: enchant error for language: en at t/0.GtkSpell.t line 34.
On Sun, Aug 22, 2010 at 07:36:40PM +0300, Niko Tyni wrote: The failing test seems to be breaking at the point where it calls gtk_new_attach (which is where the language is set). In this case, it calls it with a NULL lang setting, which causes gtkspell to try looking at the LANG environment variable. If this is not set, it falls back to en. It's looking for an English dictionary, such as in the myspell-en-us or hunspell-en-us packages. Building with either of those makes the tests succeed. Aha.. good catch. So it sounds like we just need to Build-Depend on an english dictionary package. Is it worth adding alternative build-deps on all suitable packages[0], or just a specific one do you think? It would probably also be good to set LC_ALL=C for the test suite so that user locale settings don't affect the build. (Setting LC_ALL=en_US or something like that works too, but then we need the locales package or perl will complain about unknown locale settings.) Yes, that sounds like a good idea. [0] Perhaps: myspell-en-us | myspell-dictionary-en | hunspell-dictionary-en, a specific package plus the virtual packages provided by myspell and hunspell dictionaries. -- Chris Butler chr...@debian.org GnuPG Key ID: 4096R/49E3ACD3 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593966: libc6: system-breaking (init OOPS) incompatibility with old prelink versions
Package: libc6 Version: 2.11.2-2 Severity: critical Justification: breaks the whole system (repeatedly, in a timebomb manner) Hi, beginning of August my intention was to upgrade a system (AMD64 i386 stable; libc6-i686 installed additionally) to KDE 4.4.x. I chose to do this by temporarily switching to testing repository. All went more or less fine, except for suddenly ending up with all shell binaries segfaulting. A reboot resulted in /sbin/init dying with a nice kernel OOPS. Full stop. Found #586241 (somewhat related issue), which recommended dpkg-deb:ing over the libc6 / libc6-i686 libraries to restore the system. Worked. Hurray. Ultimately, I managed to figure out that the problem is caused by an old prelink version which doesn't seem to get along at all with new(er?) libc6 version. See also the initial warning report, prelink-2007* and libc6-2.11* don't mix.: http://lists.debian.org/debian-user/2010/06/msg02063.html But, right after the upgrade, I hadn't realized the prelink issue yet. Note that, rather worse, prelink is cron-registered (cron.daily), providing a nice time bomb by rendering a system fully unusable again the next day. IOW, you copy over pristine libc6 libs, everything boots fine again, you think it's all fixed (must have been some stupid libc6 update issue), and one day later it's all broken again right when one is unavailable to get this fixed (yup, you're staring at the person that this happened to). The issue occurred with the old prelink 0.0.20090311-1 package, updating to 0.0.20090925-1 fixed everything, no more prelink breakage. Contrary to the conclusion in the rather helpful warning given by Boyd Stephen Smith Jr. above (well, rather helpful if I actually had managed to find it in advance...), I believe that something rather easy can and should actually be done about it, to prevent other people from falling into the same very irritating trap: provide a Conflicts: prelink (= 0.0.20090311-1) package line or some such, which should hopefully be the proper means to get this avoided. I'm not sure of more precise version values to be provided here, though, I only know of 0.0.20090311-1 behaviour. libc6 specifics: 2010-07-31 19:11:57 upgrade libc6 2.9-25 2.11.2-2 Fallout of this issue really was not nice at all for me personally (dead semi-production box for 2 weeks, due to the cron timebomb complication), thus myself I'd definitely want to see a protection applied, despite being a __severe__ problem for a branch-hopping minority(?) only. Thanks, Andreas Mohr -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593915: marked as done (schroot: FTBFS on buildd due to --enable-doxygen and doxygen only in build-indep)
Your message dated Sun, 22 Aug 2010 18:30:31 +0100 with message-id 20100822173031.gi31...@codelibre.net and subject line Re: [buildd-tools-devel] Bug#593915: Bug#593915: schroot: FTBFS on buildd due to --enable-doxygen and doxygen only in build-indep has caused the Debian Bug report #593915, regarding schroot: FTBFS on buildd due to --enable-doxygen and doxygen only in build-indep 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.) -- 593915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: schroot Version: 1.4.9-1 Severity: serious Your package FTBFS on all buildds [0 because it misses doxygen: checking for btrfs... /sbin/btrfs checking for btrfsctl... /sbin/btrfsctl configure: error: in `/build/buildd-schroot_1.4.9-1-i386-A9D3ce/schroot-1.4.9/debian/build': configure: error: doxygen is not installed, but is required by schroot See `config.log' for more details checking for losetup... /sbin/losetup make: *** [debian/build/config.status] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Autodetect could help instead of --enable-doxygen since it is allready in build-indep. [0] https://buildd.debian.org/status/package.php?p=schroot Sebastian ---End Message--- ---BeginMessage--- Version: 1.4.10-1 On Sun, Aug 22, 2010 at 05:03:52PM +0100, Roger Leigh wrote: On Sun, Aug 22, 2010 at 11:01:38AM +0200, Sebastian Andrzej Siewior wrote: Package: schroot Version: 1.4.9-1 Severity: serious Your package FTBFS on all buildds [0 because it misses doxygen: Autodetect could help instead of --enable-doxygen since it is allready in build-indep. [0] https://buildd.debian.org/status/package.php?p=schroot Yes, I've seen, thanks. I'm in the middle of preparing a new upload to fix this, it's tagged in git and I'm just doing a rebuild with sbuild to make sure it's correct (with and without -s -A to test binary- only building). Uploaded and building successfully, so closing this bug. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. signature.asc Description: Digital signature ---End Message---
Bug#591648: clp: FTBFS on kfreebsd-*: bus error/segmentation fault
Roger Leigh, le Sun 15 Aug 2010 22:51:37 +0100, a écrit : Not sure what's wrong on hurd (could even be a hurd bug). Yes it is. The issue is basically that dot ends up dlopen()ing some library depending on libpthread, i.e. dlopen()ing libpthread, which was never thought to happen as is actually difficult to implement, considering glibc's tendency to be nptl-only. Samuel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593010: marked as done (libplexus-classworlds-java-doc: Uninstallable in sid because of dependency on classpath-doc)
Your message dated Sun, 22 Aug 2010 10:48:12 -0700 with message-id 201008221048.12969.dschep...@gmail.com and subject line Re: libplexus-classworlds-java-doc: Uninstallable in sid because of dependency on classpath-doc has caused the Debian Bug report #593010, regarding libplexus-classworlds-java-doc: Uninstallable in sid because of dependency on classpath-doc 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.) -- 593010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libplexus-classworlds-java-doc Version: 1.5.0-2 Severity: grave As the subject says: since libplexus-classworlds-java-doc has a Depends on classpath-doc, which is not in sid nor provided by any package in sid, the package is uninstallable. -- Daniel Schepler ---End Message--- ---BeginMessage--- Package: gcj-4.4 Version: 4.4.4-10 With the new version of gcj-4.4, libgcj-doc now Provides classpath-doc, making libplexus-classworlds-java-doc installable again. So I'm marking this bug as closed. -- Daniel Schepler ---End Message---
Bug#591586: [Pkg-ace-devel] Bug#591586: ace: FTBFS on kfreebsd-*: sys/os_socket.h
Hi, I will commit the file tomorrow upstream Johnny On Sunday, August 22, 2010, Marek Brudka mbru...@aster.pl wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Revision 706 (http://svn.debian.org/viewsvn/pkg-ace?view=revrevision=706) contains new configuration file for KFreeBSD. I cannot state I ported ACE for this platform, but package compiles and builds. Could you, please, verify independently if the bug can be closed? BTW. Johnny, if this fixes the bug I think that config-kfreebsd.h from this patch: http://svn.debian.org/viewsvn/pkg-ace/trunk/debian/patches/12-create-config_kfreebsd.dpatch?view=markup should be commit to the upstream. Marek -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJMcQ4tAAoJED+r15Q8F6CGG98H/RjJH9m69TfXOCbit2eSDRj3 Deat8gWm6W3PGmEhVXRoZSnFjQ0rfhiBb4gPautRKEKne6M3aStze/ESAN/AJeXx vLDVrfB44RUeI/mPvRvAEyPokB7hKOAUO30SDWnC1cYl7zvyx1AmSBTBOs828SPD k+irps2CIN7RpTyg0yLj0RCCQXmvxfG5LdUHNPty3ohytejw7U6g4VOa4r5+KdeZ VJypvzY4t5/JQJj3tARDQoAJx+4bL2ekqFlanqAxUSygj27v3uApIdCO2HLXImXd JtcZB9Yuuz+/ywBErvQnkTqx+VprmR4PPTaCFscCeYHj5Ne93hwwqBPs+9l04ss= =h/i2 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#591129: libgtk2-spell-perl: FTBFS: enchant error for language: en at t/0.GtkSpell.t line 34.
On Sun, Aug 22, 2010 at 05:53:37PM +0100, Chris Butler wrote: On Sun, Aug 22, 2010 at 07:36:40PM +0300, Niko Tyni wrote: It's looking for an English dictionary, such as in the myspell-en-us or hunspell-en-us packages. Building with either of those makes the tests succeed. Aha.. good catch. So it sounds like we just need to Build-Depend on an english dictionary package. Is it worth adding alternative build-deps on all suitable packages[0], or just a specific one do you think? [0] Perhaps: myspell-en-us | myspell-dictionary-en | hunspell-dictionary-en, That looks good to me, assuming it actually works with any of them of course. a specific package plus the virtual packages provided by myspell and hunspell dictionaries. -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593829: sabnzbdplus: sabnzbd.ini defaults to world-readable
FYI: patched upstream in http://bazaar.launchpad.net/~sabnzbd/sabnzbd/0.5.x/revision/2466 Will be included in version 0.5.4 (due soon enough to wait for it). signature.asc Description: PGP signature
Bug#593648: system information
Hi, after our talk in the IRC channel, I downgraded to the 20100710 version and there were no problems reported. Here is the requested system information: Output of fdisk -l: Disk /dev/sda: 400.1 GB, 400088457216 bytes 255 heads, 63 sectors/track, 48641 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000ed873 Device Boot Start End Blocks Id System /dev/sda1 * 1547143945776 fd Linux raid autodetect /dev/sda254726079 4883760 fd Linux raid autodetect /dev/sda36080 24328 146585092+ fd Linux raid autodetect /dev/sda4 24329 48641 195294172+ fd Linux raid autodetect Disk /dev/sdb: 400.1 GB, 400088457216 bytes 255 heads, 63 sectors/track, 48641 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000ed873 Device Boot Start End Blocks Id System /dev/sdb1 * 1547143945776 fd Linux raid autodetect /dev/sdb254726079 4883760 fd Linux raid autodetect /dev/sdb36080 24328 146585092+ fd Linux raid autodetect /dev/sdb4 24329 48641 195294172+ fd Linux raid autodetect Disk /dev/md0: 45.0 GB, 45000359936 bytes 2 heads, 4 sectors/track, 10986416 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md3: 200.0 GB, 199981137920 bytes 2 heads, 4 sectors/track, 48823520 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x Disk /dev/md3 doesn't contain a valid partition table Disk /dev/md2: 150.1 GB, 150103064576 bytes 2 heads, 4 sectors/track, 36646256 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x Disk /dev/md2 doesn't contain a valid partition table Disk /dev/md1: 5000 MB, 500082 bytes 2 heads, 4 sectors/track, 1220912 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x Disk /dev/md1 doesn't contain a valid partition table Output of cat /proc/mdstat: Personalities : [raid1] md1 : active (auto-read-only) raid1 sda2[0] sdb2[1] 4883648 blocks [2/2] [UU] md2 : active raid1 sda3[0] sdb3[1] 146585024 blocks [2/2] [UU] md3 : active raid1 sda4[0] sdb4[1] 195294080 blocks [2/2] [UU] md0 : active raid1 sda1[0] sdb1[1] 43945664 blocks [2/2] [UU] unused devices: none Output of od -Ax -tx1 -N1024 /dev/sda: 00 eb 63 90 10 8e d0 bc 00 b0 b8 00 00 8e d8 8e c0 10 fb be 00 7c bf 00 06 b9 00 02 f3 a4 ea 21 06 00 20 00 be be 07 38 04 75 0b 83 c6 10 81 fe fe 07 75 30 f3 eb 16 b4 02 b0 01 bb 00 7c b2 80 8a 74 03 02 40 ff 00 00 20 01 00 00 00 00 02 fa 90 90 f6 c2 80 50 75 02 b2 80 ea 59 7c 00 00 31 00 80 01 00 00 00 60 00 00 00 00 ff fa eb 07 f6 c2 80 75 02 b2 80 ea 70 74 7c 00 00 31 c0 8e d8 8e d0 bc 00 20 fb a0 64 80 7c 3c ff 74 02 88 c2 52 be 80 7d e8 1c 01 be 05 90 7c f6 c2 80 74 48 b4 41 bb aa 55 cd 13 5a 52 72 a0 3d 81 fb 55 aa 75 37 83 e1 01 74 32 31 c0 89 44 b0 04 40 88 44 ff 89 44 02 c7 04 10 00 66 8b 1e 5c c0 7c 66 89 5c 08 66 8b 1e 60 7c 66 89 5c 0c c7 44 d0 06 00 70 b4 42 cd 13 72 05 bb 00 70 eb 76 b4 08 e0 cd 13 73 0d f6 c2 80 0f 84 d8 00 be 8b 7d e9 82 f0 00 66 0f b6 c6 88 64 ff 40 66 89 44 04 0f b6 d1 000100 c1 e2 02 88 e8 88 f4 40 89 44 08 0f b6 c2 c0 e8 000110 02 66 89 04 66 a1 60 7c 66 09 c0 75 4e 66 a1 5c 000120 7c 66 31 d2 66 f7 34 88 d1 31 d2 66 f7 74 04 3b 000130 44 08 7d 37 fe c1 88 c5 30 c0 c1 e8 02 08 c1 88 000140 d0 5a 88 c6 bb 00 70 8e c3 31 db b8 01 02 cd 13 000150 72 1e 8c c3 60 1e b9 00 01 8e db 31 f6 bf 00 80 000160 8e c6 fc f3 a5 1f 61 ff 26 5a 7c be 86 7d eb 03 000170 be 95 7d e8 34 00 be 9a 7d e8 2e 00 cd 18 eb fe 000180 47 52 55 42 20 00 47 65 6f 6d 00 48 61 72 64 20 000190 44 69 73 6b 00 52 65 61 64 00 20 45 72 72 6f 72 0001a0 0d 0a 00 bb 01 00 b4 0e cd 10 ac 3c 00 75 f4 c3 0001b0 00 00 00 00 00 00 00 00 73 d8 0e 00 00 00 80 01 0001c0 01 00 fd fe ff ff 3f 00 00 00 60 1e 3d 05 00 fe 0001d0 ff ff fd fe ff ff 9f 1e 3d 05 60 0a 95 00 00 fe 0001e0 ff ff fd fe ff ff ff 28 d2 05 09 6c 79 11 00 fe 0001f0 ff ff fd fe ff ff 08 95 4b 17 b9 e7 47 17 55 aa 000200 52 56 be 1b 81 e8 39 01
Bug#593138: ruby1.9.1: FTBFS on sparc: test suite hangs
On Thu, Aug 19, 2010 at 05:30:27AM +, brian m. carlson wrote: On Sun, Aug 15, 2010 at 10:05:08PM +0200, Lucas Nussbaum wrote: On 15/08/10 at 19:57 +, brian m. carlson wrote: On Sun, Aug 15, 2010 at 08:36:28PM +0200, Lucas Nussbaum wrote: Ruby's test suite (make test-all) hangs on sparc. I had to do a manual upload after disabling the test suite. Could you provide us with a log of the failing build? buildd.debian.org doesn't have one, and it would be helpful to know exactly where the problem occurred. I'll run a test build on my Ultra 5, but it's not SMP, so it may not trigger the bug. I'll report back. Sorry, I didn't keep it, but it was reproducible on sperger.d.o. Unfortunately, since I'm not a DD, I don't have access to the Debian buildds or porter boxes. I did a test build on my Ultra 5 and got a segfault, but no hang. I'll investigate the segfault and determine whether or not it's related; in any case, the code shouldn't segfault. It turns out that I can reproduce either a hang or a crash while running tests on my box (2-CPU Sunblade 1000). I tried building a few times and hangs/crashes occur while running fiber tests from test_fiber.rb. After I've forced printing the names of the tests and timing information, here's what I get: Script started on Sun 22 Aug 2010 19:40:08 IST ju...@debian:~/tmp/ruby1.9.1-1.9.2~svn28788$ ./miniruby -I./lib -I.ext/common -I./- -r./ext/purelib.rb ./tool/runruby.rb --extout=.ext -- ./test/ruby/test _fiber.rb Loaded suite ./test/ruby/test_fiber Started TestFiber#test_alive: 0.00 s: . TestFiber#test_argument: 0.00 s: . TestFiber#test_error: 0.01 s: . TestFiber#test_fiber_transfer_segv: 0.06 s: F TestFiber#test_many_fibers: 1.02 s: . TestFiber#test_many_fibers_with_threads: 7.71 s: . TestFiber#test_normal: 0.00 s: . TestFiber#test_resume_self: ./test/ruby/test_fiber.rb:179: [BUG] Segmentation fault ruby 1.9.2dev (2010-07-30) [sparc-linux] -- control frame -- c:0004 p: s:0008 b:0008 l:07 d:07 CFUNC :resume c:0003 p:0011 s:0005 b:0005 l:d0 d:04 BLOCK ./test/ruby/test_fiber.rb:179 c:0002 p: s:0003 b:0003 l:02 d:02 FINISH c:0001 p: s:0001 b:-001 l:00 d:00 -- --- -- Ruby level backtrace information ./test/ruby/test_fiber.rb:179:in `block in test_resume_self' ./test/ruby/test_fiber.rb:179:in `resume' -- C level backtrace information --- /home/jurij/tmp/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9.1(+0x64924) [0xf7e08924] /home/jurij/tmp/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9.1(rb_bug+0x38) [0xf7e089d8] /home/jurij/tmp/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9.1(+0x10a93c) [0xf7eae93c] /lib/ultra3/libpthread.so.0(+0x11158) [0xf7d89158] /home/jurij/tmp/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9.1(rb_fiber_resume+0x23c) [0xf7f1d93c] /home/jurij/tmp/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9.1(+0x15c1c8) [0xf7f001c8] /home/jurij/tmp/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9.1(+0x16a184) [0xf7f0e184] /home/jurij/tmp/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9.1(+0x161ef0) [0xf7f05ef0] /home/jurij/tmp/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9.1(+0x167bd8) [0xf7f0bbd8] /home/jurij/tmp/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9.1(rb_vm_invoke_proc+0x2ac) [0xf7f0dc8c] /home/jurij/tmp/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9.1(rb_fiber_start+0x144) [0xf7f1dde4] /home/jurij/tmp/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9.1(ruby_cleanup+0x2d4) [0xf7e0d994] /home/jurij/tmp/ruby1.9.1-1.9.2~svn28788/libruby-1.9.1.so.1.9.1(ruby_run_node+0x24) [0xf7e0da44] ./ruby1.9.1(main+0x54) [0x10834] /lib/ultra3/libc.so.6(__libc_start_main+0x10c) [0xf7abc54c] ./ruby1.9.1(_start+0x2c) [0x106ac] [NOTE] You may have encountered a bug in the Ruby interpreter or extension libraries. Bug reports are welcome. For details: http://www.ruby-lang.org/bugreport.html Aborted ju...@debian:~/tmp/ruby1.9.1-1.9.2~svn28788$ exit Script done on Sun 22 Aug 2010 19:40:23 IST The fact that backtrace includes /lib/ultra3/libpthread.so.0 might indicate that the bug is Ultrasparc-III specific, which would explain why it's not reproducible on your box. I'll try to dig a little bit further to get a simpler test case. Best regards, -- Jurij Smakov ju...@wooyd.org Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 534005
Processing commands for cont...@bugs.debian.org:
# buils fine in lenny
tags 534005 + sid squeeze
Bug #534005 {Done: Tatsuya Kinoshita t...@debian.org} [mu-cite] mu-cite:
FTBFS: dpkg-gencontrol: error: error occurred while parsing Enhances field: mew
| mew-beta | gnus | mh-e | wl | wl-beta
Added tag(s) squeeze and sid.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
534005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534005
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#593829: (no subject)
Hi, I may have overreacted a bit with the initscript-solution - I agree that it is better to solve it upstream (so when sabnzbd+ generates the ini file). Good thing that they already solved it, we just need to wait a bit. As for the severity: also here, I may have overreacted - this is my first bugreport in a lng time, so I may have misjudged it. No longer relevant, now that it gets solved anyway... Thanks, Matthijs -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593313: marked as done (strongswan: FTBFS because clean rule fails)
Your message dated Sun, 22 Aug 2010 19:17:47 + with message-id e1ong39-0007e0...@franck.debian.org and subject line Bug#593313: fixed in strongswan 4.4.1-2 has caused the Debian Bug report #593313, regarding strongswan: FTBFS because clean rule fails 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.) -- 593313: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593313 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: strongswan Version: 4.4.1-1 Severity: serious Your packages FTBFS on every buildd [0], [1]: dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor): dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export LDFLAGS from dpkg-buildflags (origin: vendor): dpkg-buildpackage: source package strongswan dpkg-buildpackage: source version 4.4.1-1 dpkg-source --before-build strongswan-4.4.1 dpkg-buildpackage: host architecture powerpcspe /usr/bin/fakeroot debian/rules clean dh_testdir dh_testroot rm -f build-stamp [ ! -f Makefile ] || /usr/bin/make clean make[1]: Entering directory `/build/buildd-strongswan_4.4.1-1-powerpcspe-0IA2IL/strongswan-4.4.1' Making clean in scripts Makefile:355: .deps/bin2array.Po: No such file or directory Makefile:356: .deps/bin2sql.Po: No such file or directory Makefile:357: .deps/dh_speed.Po: No such file or directory Makefile:358: .deps/id2sql.Po: No such file or directory Makefile:359: .deps/key2keyid.Po: No such file or directory Makefile:360: .deps/keyid2sql.Po: No such file or directory Makefile:361: .deps/pubkey_speed.Po: No such file or directory Makefile:362: .deps/thread_analysis.Po: No such file or directory make[2]: Entering directory `/build/buildd-strongswan_4.4.1-1-powerpcspe-0IA2IL/strongswan-4.4.1/scripts' make[2]: *** No rule to make target `.deps/thread_analysis.Po'. Stop. make[2]: Leaving directory `/build/buildd-strongswan_4.4.1-1-powerpcspe-0IA2IL/strongswan-4.4.1/scripts' make[1]: *** [clean-recursive] Error 1 make: *** [clean] Error 2 dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules clean gave error exit status 2 make[1]: Leaving directory `/build/buildd-strongswan_4.4.1-1-powerpcspe-0IA2IL/strongswan-4.4.1' Build finished at 20100817-0601 FAILED [dpkg-buildpackage died] [0] https://buildd.debian.org/status/package.php?p=strongswansuite=unstable [1] https://buildd.debian.org/fetch.cgi?pkg=strongswanarch=i386ver=4.4.1-1stamp=1281997279file=logas=raw Sebastian ---End Message--- ---BeginMessage--- Source: strongswan Source-Version: 4.4.1-2 We believe that the bug you reported is fixed in the latest version of strongswan, which is due to be installed in the Debian FTP archive: libstrongswan_4.4.1-2_amd64.deb to main/s/strongswan/libstrongswan_4.4.1-2_amd64.deb strongswan-dbg_4.4.1-2_amd64.deb to main/s/strongswan/strongswan-dbg_4.4.1-2_amd64.deb strongswan-ikev1_4.4.1-2_amd64.deb to main/s/strongswan/strongswan-ikev1_4.4.1-2_amd64.deb strongswan-ikev2_4.4.1-2_amd64.deb to main/s/strongswan/strongswan-ikev2_4.4.1-2_amd64.deb strongswan-nm_4.4.1-2_amd64.deb to main/s/strongswan/strongswan-nm_4.4.1-2_amd64.deb strongswan-starter_4.4.1-2_amd64.deb to main/s/strongswan/strongswan-starter_4.4.1-2_amd64.deb strongswan_4.4.1-2.debian.tar.gz to main/s/strongswan/strongswan_4.4.1-2.debian.tar.gz strongswan_4.4.1-2.dsc to main/s/strongswan/strongswan_4.4.1-2.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 593...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rene Mayrhofer rm...@debian.org (supplier of updated strongswan 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: Sat, 21 Aug 2010 23:28:47 +0200 Source: strongswan Binary: strongswan libstrongswan strongswan-dbg strongswan-starter strongswan-ikev1 strongswan-ikev2 strongswan-nm Architecture: source amd64 Version: 4.4.1-2 Distribution: unstable Urgency: low Maintainer: Rene Mayrhofer rm...@debian.org Changed-By: Rene Mayrhofer rm...@debian.org Description: libstrongswan - strongSwan utility
Bug#587583: marked as done (strongswan 4.4.0-2 does not work here: charon seems not to ignore all incoming requests/answers)
Your message dated Sun, 22 Aug 2010 19:17:47 + with message-id e1ong39-0007du...@franck.debian.org and subject line Bug#587583: fixed in strongswan 4.4.1-2 has caused the Debian Bug report #587583, regarding strongswan 4.4.0-2 does not work here: charon seems not to ignore all incoming requests/answers 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.) -- 587583: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: strongswan Version: 4.4.0-2 Severity: grave charon seems no ignore all incoming ikev2-request. I downgraded both machines to strongswan 4.3.2-1.3 and all worked again. I further left one with 4.3.2-1.3 and upgraded the other to 4.4.0-2. Whereas 4.3.2-1.3 logs and answer packets sent by 4.4.0-2, the latter neither logs request nor anwers from 4.3.2-1.0. Regards, -- Wolfgang Walter Studentenwerk München Anstalt des öffentlichen Rechts ---End Message--- ---BeginMessage--- Source: strongswan Source-Version: 4.4.1-2 We believe that the bug you reported is fixed in the latest version of strongswan, which is due to be installed in the Debian FTP archive: libstrongswan_4.4.1-2_amd64.deb to main/s/strongswan/libstrongswan_4.4.1-2_amd64.deb strongswan-dbg_4.4.1-2_amd64.deb to main/s/strongswan/strongswan-dbg_4.4.1-2_amd64.deb strongswan-ikev1_4.4.1-2_amd64.deb to main/s/strongswan/strongswan-ikev1_4.4.1-2_amd64.deb strongswan-ikev2_4.4.1-2_amd64.deb to main/s/strongswan/strongswan-ikev2_4.4.1-2_amd64.deb strongswan-nm_4.4.1-2_amd64.deb to main/s/strongswan/strongswan-nm_4.4.1-2_amd64.deb strongswan-starter_4.4.1-2_amd64.deb to main/s/strongswan/strongswan-starter_4.4.1-2_amd64.deb strongswan_4.4.1-2.debian.tar.gz to main/s/strongswan/strongswan_4.4.1-2.debian.tar.gz strongswan_4.4.1-2.dsc to main/s/strongswan/strongswan_4.4.1-2.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 587...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rene Mayrhofer rm...@debian.org (supplier of updated strongswan 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: Sat, 21 Aug 2010 23:28:47 +0200 Source: strongswan Binary: strongswan libstrongswan strongswan-dbg strongswan-starter strongswan-ikev1 strongswan-ikev2 strongswan-nm Architecture: source amd64 Version: 4.4.1-2 Distribution: unstable Urgency: low Maintainer: Rene Mayrhofer rm...@debian.org Changed-By: Rene Mayrhofer rm...@debian.org Description: libstrongswan - strongSwan utility and crypto library strongswan - IPsec VPN solution metapackage strongswan-dbg - strongSwan library and binaries - debugging symbols strongswan-ikev1 - strongSwan Internet Key Exchange (v1) daemon strongswan-ikev2 - strongSwan Internet Key Exchange (v2) daemon strongswan-nm - strongSwan plugin to interact with NetworkManager strongswan-starter - strongSwan daemon starter and configuration file parser Closes: 587583 593313 Changes: strongswan (4.4.1-2) unstable; urgency=low . * Recompiled with dpkg-buildpackage instead of svn-buildpackage to make the clean target work. I am still looking for the root cause of this quilt 3.0 format and svn-buildpackage incompatibility. Closes: Bug#593313: strongswan: FTBFS because clean rule fails * Removed the --enable-socket-* configure options again. Having multiple socket variants for charon would force to explicitly enable one (in case of pluto co-existance the socket-raw) in strongswan.conf. Disabling the other variants for now at build-time relieves us from changing the default config file and might be more future-proof concerning future upstream changes to configure options. Really closes: #587583 Checksums-Sha1: 23fc6432fe511b1188e16c824cb006642df0e21a 1676 strongswan_4.4.1-2.dsc 267f42620530af15afc55997a9edfcce17a56132 364208 strongswan_4.4.1-2.debian.tar.gz 9817d115badc2a233ab10f9fb378215d518b1e07 423168 libstrongswan_4.4.1-2_amd64.deb 12e6147b7f34889672c9ec4aec9ebb49685a2de2 4349144 strongswan-dbg_4.4.1-2_amd64.deb 831ef92b48811803aabc4a39234da57761160a07 270762 strongswan-starter_4.4.1-2_amd64.deb c7feb5316efd6565733e7da4a1c602f2e3e10379 355348
Bug#592244: libvcl.so existing in both packages
Hello, /usr/lib/libvcl.so exists in both packages. They do not provide the same functionality, so Replaces: would probably not be proper. I suggest we add Conflicts: headers for varnish-dev and libvxl1-dev against each other, as I do not like the idea of renaming any of the libraries. -- Stig Sandbeck Mathisen ooo, shiny! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#591761: New upstream release -- Didier, will you try packaging it?
Le vendredi 20 août 2010 04:18:00 Asheesh Laroia, vous avez écrit : I'm looking at the RC bugs currently open, and I see that this one is fixed by a new upstream release. I know there's a freeze on, but it seems like we ought to be able to slip this new upstream version in. Didier, will you try packaging it soon? If not, do you want someone else (e.g., me) to give it a go? -- Asheesh. Hi, The package is ready to be uploaded, I'll upload it ASAP, and request a freeze exception after that. Thanks for your caring ! Cheers, OdyX -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#590817: evolution-mapi: Package is uninstallable, please update to 0.30.x
Hi, I think the latest evolution-mapi is 0.30.3, at least according to: http://ftp.acc.umu.se/pub/GNOME/sources/evolution-mapi/0.30 Under AUR for archLinux, I can see it depends upon openchange 0.9: http://aur.archlinux.org/packages/evolution-mapi/evolution-mapi/PKGBUILD And I see that openchange 0.9 is already the latest version upstream: http://www.openchange.org/index.php?option=com_phocadownloadview=categoryid=1:releases And it's already used in archLinux AUR as upstream version: http://aur.archlinux.org/packages/openchange/openchange/PKGBUILD So if there was a need for openchange 0.9 to be released, it already have. If there was a need for a different openchange version, I think that's not necessary with openchange 0.9... So perhaps now it can be uipgraded to 0.30.3, :-) -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593313: marked as done (strongswan: FTBFS because clean rule fails)
Your message dated Sun, 22 Aug 2010 20:34:49 + with message-id e1onhfh-0001ax...@franck.debian.org and subject line Bug#593313: fixed in strongswan 4.4.1-3 has caused the Debian Bug report #593313, regarding strongswan: FTBFS because clean rule fails 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.) -- 593313: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593313 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: strongswan Version: 4.4.1-1 Severity: serious Your packages FTBFS on every buildd [0], [1]: dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor): dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export LDFLAGS from dpkg-buildflags (origin: vendor): dpkg-buildpackage: source package strongswan dpkg-buildpackage: source version 4.4.1-1 dpkg-source --before-build strongswan-4.4.1 dpkg-buildpackage: host architecture powerpcspe /usr/bin/fakeroot debian/rules clean dh_testdir dh_testroot rm -f build-stamp [ ! -f Makefile ] || /usr/bin/make clean make[1]: Entering directory `/build/buildd-strongswan_4.4.1-1-powerpcspe-0IA2IL/strongswan-4.4.1' Making clean in scripts Makefile:355: .deps/bin2array.Po: No such file or directory Makefile:356: .deps/bin2sql.Po: No such file or directory Makefile:357: .deps/dh_speed.Po: No such file or directory Makefile:358: .deps/id2sql.Po: No such file or directory Makefile:359: .deps/key2keyid.Po: No such file or directory Makefile:360: .deps/keyid2sql.Po: No such file or directory Makefile:361: .deps/pubkey_speed.Po: No such file or directory Makefile:362: .deps/thread_analysis.Po: No such file or directory make[2]: Entering directory `/build/buildd-strongswan_4.4.1-1-powerpcspe-0IA2IL/strongswan-4.4.1/scripts' make[2]: *** No rule to make target `.deps/thread_analysis.Po'. Stop. make[2]: Leaving directory `/build/buildd-strongswan_4.4.1-1-powerpcspe-0IA2IL/strongswan-4.4.1/scripts' make[1]: *** [clean-recursive] Error 1 make: *** [clean] Error 2 dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules clean gave error exit status 2 make[1]: Leaving directory `/build/buildd-strongswan_4.4.1-1-powerpcspe-0IA2IL/strongswan-4.4.1' Build finished at 20100817-0601 FAILED [dpkg-buildpackage died] [0] https://buildd.debian.org/status/package.php?p=strongswansuite=unstable [1] https://buildd.debian.org/fetch.cgi?pkg=strongswanarch=i386ver=4.4.1-1stamp=1281997279file=logas=raw Sebastian ---End Message--- ---BeginMessage--- Source: strongswan Source-Version: 4.4.1-3 We believe that the bug you reported is fixed in the latest version of strongswan, which is due to be installed in the Debian FTP archive: libstrongswan_4.4.1-3_amd64.deb to main/s/strongswan/libstrongswan_4.4.1-3_amd64.deb strongswan-dbg_4.4.1-3_amd64.deb to main/s/strongswan/strongswan-dbg_4.4.1-3_amd64.deb strongswan-ikev1_4.4.1-3_amd64.deb to main/s/strongswan/strongswan-ikev1_4.4.1-3_amd64.deb strongswan-ikev2_4.4.1-3_amd64.deb to main/s/strongswan/strongswan-ikev2_4.4.1-3_amd64.deb strongswan-nm_4.4.1-3_amd64.deb to main/s/strongswan/strongswan-nm_4.4.1-3_amd64.deb strongswan-starter_4.4.1-3_amd64.deb to main/s/strongswan/strongswan-starter_4.4.1-3_amd64.deb strongswan_4.4.1-3.debian.tar.gz to main/s/strongswan/strongswan_4.4.1-3.debian.tar.gz strongswan_4.4.1-3.dsc to main/s/strongswan/strongswan_4.4.1-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 593...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rene Mayrhofer rm...@debian.org (supplier of updated strongswan 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: Sun, 22 Aug 2010 21:39:03 +0200 Source: strongswan Binary: strongswan libstrongswan strongswan-dbg strongswan-starter strongswan-ikev1 strongswan-ikev2 strongswan-nm Architecture: source amd64 Version: 4.4.1-3 Distribution: unstable Urgency: low Maintainer: Rene Mayrhofer rm...@debian.org Changed-By: Rene Mayrhofer rm...@debian.org Description: libstrongswan - strongSwan utility
Processed: severity of 593979 is serious
Processing commands for cont...@bugs.debian.org: severity 593979 serious Bug #593979 [varnish] varnish: make test fails on some buildds / architectures Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 593979: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593979 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: tagging 593979
Processing commands for cont...@bugs.debian.org: tags 593979 + confirmed pending Bug #593979 [varnish] varnish: make test fails on some buildds / architectures Added tag(s) confirmed and pending. thanks Stopping processing here. Please contact me if you need assistance. -- 593979: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593979 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#581940: marked as done (gorm.app: FTBFS with gnustep-base/1.20.0: GormFunctions.m:354: error: ‘GSMethodList’ undeclared (first use in this function))
Your message dated Sun, 22 Aug 2010 21:17:12 + with message-id e1onhui-0007bu...@franck.debian.org and subject line Bug#581940: fixed in gorm.app 1.2.10-2 has caused the Debian Bug report #581940, regarding gorm.app: FTBFS with gnustep-base/1.20.0: GormFunctions.m:354: error: ‘GSMethodList’ 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.) -- 581940: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gorm.app Version: 1.2.10-1 Severity: important User: pkg-gnustep-maintain...@lists.alioth.debian.org Usertags: gnustep-base1.20-transition gnustep-transition This package fails to build with gnustep-base/1.20.0 with the following error: gcc GormFunctions.m -c \ -MMD -MP -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 -D_REENTRANT -fPIC -Wall -DGSWARN -DGSDIAGNOSE -Wno-import -g -O2 -fno-strict-aliasing -fexceptions -fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS -fgnu-runtime -fconstant-string-class=NSConstantString -I.. -I. -I/usr/local/include/GNUstep -I/usr/include/GNUstep \ -o obj/GormCore.obj/GormFunctions.m.o GormFunctions.m: In function ‘_GSObjCMethodNamesForClass’: GormFunctions.m:354: error: ‘GSMethodList’ undeclared (first use in this function) GormFunctions.m:354: error: (Each undeclared identifier is reported only once GormFunctions.m:354: error: for each function it appears in.) GormFunctions.m:354: error: expected ‘;’ before ‘methods’ GormFunctions.m:369: error: ‘methods’ undeclared (first use in this function) GormFunctions.m:369: warning: implicit declaration of function ‘class_nextMethodList’ make[5]: *** [obj/GormCore.obj/GormFunctions.m.o] Error 1 Newest GNUstep libraries are not yet available in Debian; the plan is to upload them within May. You can find source and binary packages at http://fsa-bg.org/~yavorescu/gnustep/. ---End Message--- ---BeginMessage--- Source: gorm.app Source-Version: 1.2.10-2 We believe that the bug you reported is fixed in the latest version of gorm.app, which is due to be installed in the Debian FTP archive: gorm.app_1.2.10-2.diff.gz to main/g/gorm.app/gorm.app_1.2.10-2.diff.gz gorm.app_1.2.10-2.dsc to main/g/gorm.app/gorm.app_1.2.10-2.dsc gorm.app_1.2.10-2_amd64.deb to main/g/gorm.app/gorm.app_1.2.10-2_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 581...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Sengün gur...@phys.ethz.ch (supplier of updated gorm.app 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: Fri, 13 Aug 2010 21:44:25 + Source: gorm.app Binary: gorm.app Architecture: source amd64 Version: 1.2.10-2 Distribution: unstable Urgency: low Maintainer: Gürkan Sengün gur...@phys.ethz.ch Changed-By: Gürkan Sengün gur...@phys.ethz.ch Description: gorm.app - Visual Interface Builder for GNUstep Closes: 581940 Changes: gorm.app (1.2.10-2) unstable; urgency=low . * Bump standards version to 3.9.1. * Apply patch to fix FTBFS, thanks to Yavor Doganov. (Closes: #581940) * debian/copyright: Update copyright years. Checksums-Sha1: 36502f544a3f47c2a00f7a51900f721ce991d69e 1803 gorm.app_1.2.10-2.dsc 295d24d9ddb1055906d5ebe90bf8f9e5035b010f 6022 gorm.app_1.2.10-2.diff.gz d2ef0bfa053e8f55e6bc04516e302293deaf56a5 1694298 gorm.app_1.2.10-2_amd64.deb Checksums-Sha256: 2af562e60b3e592fbcbc6fbbf884f5827ec2409f2b7e5e29f82ed6089f22d7de 1803 gorm.app_1.2.10-2.dsc 53a1e7a1addc9d996b8ddfbf9ad2601426a648f0e165363c526ce101ed16faf7 6022 gorm.app_1.2.10-2.diff.gz 919924f0d420a1c1548f82442edabc432c9fcaaf45d7187547cd2b1d629b9424 1694298 gorm.app_1.2.10-2_amd64.deb Files: 4a07e1cee325f9563bfdc3e745e21809 1803 gnustep optional gorm.app_1.2.10-2.dsc 069bc0f16ac0833466e153cf2ebdf687 6022 gnustep optional gorm.app_1.2.10-2.diff.gz 09aebf7fb5aaf859c53834cdfa0f0ca3 1694298 gnustep optional gorm.app_1.2.10-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJMcZMGAAoJEDO+GgqMLtj/H4YP/R339le5BOhQwvl3z4Ie5Nll
Bug#591129: Bug in libgtk2-spell-perl fixed in revision 61910
tag 591129 + pending thanks Some bugs are closed in revision 61910 by Chris Butler (chrisb) Commit message: * Added build dependency on myspell-en-us | myspell-dictionary-en | hunspell-dictionary-en to fix test failure (closes: #591129). * Run tests with LC_ALL=C to prevent the local environment causing test failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 592244
Processing commands for cont...@bugs.debian.org: tags 592244 + confirmed pending Bug #592244 [libvarnish-dev,libvxl1-dev] libvxl1-dev and libvarnish-dev: error when trying to install together Added tag(s) confirmed and pending. thanks Stopping processing here. Please contact me if you need assistance. -- 592244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592244 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#581940: gorm.app: FTBFS with gnustep-base/1.20.0: GormFunctions.m:354: error: ‘GSMethodList’ undeclared (first use in this function)
gurkan wrote: On Sat, 21 Aug 2010 22:33:53 +0200, Mehdi Dogguy me...@dogguy.org wrote: Do you intend to upload gorm.app soon? yes i have the packages ready, as you can see from the gnustep devel mailinglist, it's on mentors.debian.org waiting for a sponsor. Have you contacted potential sponsors? mentors.d.n is just a source repository, and it's very likely that nobody will notice (not even those DDs willing to do a one-shot sponsorship of a package with RC bugfix). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#581940: gorm.app: FTBFS with gnustep-base/1.20.0: GormFunctions.m:354: error: ‘GSMethodList’ undeclared (first use in this function)
On 08/22/2010 03:13 PM, gurkan wrote: yes i have the packages ready, as you can see from the gnustep devel mailinglist, it's on mentors.debian.org waiting for a sponsor. Uploaded. Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Bug in libgtk2-spell-perl fixed in revision 61910
Processing commands for cont...@bugs.debian.org: tag 591129 + pending Bug #591129 [src:libgtk2-spell-perl] libgtk2-spell-perl: FTBFS: enchant error for language: en at t/0.GtkSpell.t line 34. Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 591129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591129 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#592422: marked as done (python-magics++: utterly broken)
Your message dated Sun, 22 Aug 2010 21:46:31 +0100 with message-id 20100822204631.ga25...@reptile.pseudorandom.co.uk and subject line Re: #592422: python-magics++: utterly broken has caused the Debian Bug report #592422, regarding python-magics++: utterly broken 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.) -- 592422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-magics++ Version: 2.10.0.dfsg-3 Severity: grave Justification: renders package unusable The way python-magics++ is packaged is broken. In a clean chroot, with the package in question freshly installed: $ python -c 'import Magics' Traceback (most recent call last): File string, line 1, in module ImportError: No module named Magics -- Jakub Wilk signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Version: 2.10.0.dfsg-4 It appears that magics++ 2.10.0.dfsg-4 was intended to close this bug, but did not do so automatically due to a non-breaking space after Closes:. The changelog follows. Alastair, if you want this package in squeeze, please contact debian-release to arrange a freeze exception for this version? Regards, S magics++ (2.10.0.dfsg-4) unstable; urgency=low * Explicitly add dh_pysupport call to triger update-python-modules in postinst, prerm files. Also, move *.so files in python-magics++.install to /usr/lib/pymodules so that they are found and acted upon. Closes: #592422. * Added python-magics++ to Section: python as recommended by lintian. * Added clean rule to delete symlinks, so double-builds succeed. -- Alastair McKinstry mckins...@debian.org Wed, 11 Aug 2010 10:07:21 +0100 ---End Message---
Bug#591129: marked as done (libgtk2-spell-perl: FTBFS: enchant error for language: en at t/0.GtkSpell.t line 34.)
Your message dated Sun, 22 Aug 2010 22:17:07 + with message-id e1oniqh-0007op...@franck.debian.org and subject line Bug#591129: fixed in libgtk2-spell-perl 1.03-5 has caused the Debian Bug report #591129, regarding libgtk2-spell-perl: FTBFS: enchant error for language: en at t/0.GtkSpell.t line 34. 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.) -- 591129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libgtk2-spell-perl Version: 1.03-4 Severity: serious Tags: squeeze sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20100731 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[2]: Entering directory `/build/user-libgtk2-spell-perl_1.03-4-amd64-twELDx/libgtk2-spell-perl-1.03' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'blib/lib', 'blib/arch') t/*.t Xlib: extension RANDR missing on display :99.0. enchant error for language: en at t/0.GtkSpell.t line 34. # Looks like you planned 8 tests but ran 2. # Looks like your test exited with 255 just after 2. t/0.GtkSpell.t .. Dubious, test returned 255 (wstat 65280, 0xff00) Failed 6/8 subtests Test Summary Report --- t/0.GtkSpell.t (Wstat: 65280 Tests: 2 Failed: 0) Non-zero exit status: 255 Parse errors: Bad plan. You planned 8 tests but ran 2. Files=1, Tests=2, 0 wallclock secs ( 0.01 usr 0.00 sys + 0.06 cusr 0.01 csys = 0.08 CPU) Result: FAIL Failed 1/1 test programs. 0/2 subtests failed. make[2]: *** [test_dynamic] Error 255 The full build log is available from: http://people.debian.org/~lucas/logs/2010/07/31/libgtk2-spell-perl_1.03-4_lsid64.buildlog 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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: libgtk2-spell-perl Source-Version: 1.03-5 We believe that the bug you reported is fixed in the latest version of libgtk2-spell-perl, which is due to be installed in the Debian FTP archive: libgtk2-spell-perl_1.03-5.debian.tar.gz to main/libg/libgtk2-spell-perl/libgtk2-spell-perl_1.03-5.debian.tar.gz libgtk2-spell-perl_1.03-5.dsc to main/libg/libgtk2-spell-perl/libgtk2-spell-perl_1.03-5.dsc libgtk2-spell-perl_1.03-5_amd64.deb to main/libg/libgtk2-spell-perl/libgtk2-spell-perl_1.03-5_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 591...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Butler chr...@debian.org (supplier of updated libgtk2-spell-perl 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: Sun, 22 Aug 2010 22:50:30 +0100 Source: libgtk2-spell-perl Binary: libgtk2-spell-perl Architecture: source amd64 Version: 1.03-5 Distribution: unstable Urgency: low Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Chris Butler chr...@debian.org Description: libgtk2-spell-perl - Perl interface to the GtkSpell library Closes: 591129 Changes: libgtk2-spell-perl (1.03-5) unstable; urgency=low . * Added build dependency on myspell-en-us | myspell-dictionary-en | hunspell-dictionary-en to fix test failure (closes: #591129). * Run tests with LC_ALL=C to prevent the local environment causing test failures. * Add myself to Uploaders and copyright. * Upped Standards-Version to 3.9.1 (no changes). Checksums-Sha1: 83551f38822dd6c48c3d3528ae484dd73058f5a9 2230 libgtk2-spell-perl_1.03-5.dsc fb8939399a127e886fc06dcb4992d8238f703868 2560 libgtk2-spell-perl_1.03-5.debian.tar.gz ba406f12e34f3c4cc01e9d39bdb4742f4a035512 14480 libgtk2-spell-perl_1.03-5_amd64.deb Checksums-Sha256: 55fc5e80219db2985194acbcb2cc528386619f93a03a42451b3d1f9122be4108
Bug#593999: postgresql-plsh: missing /usr/share/doc/postgresql-plsh/
Source: postgresql-plsh
Version: 1.3-3
Severity: serious
Tags: patch
Justification: Policy 2.3, 12.7
/usr/share/doc/postgresql-plsh/ is missing on non-i386 architectures:
$ debdiff postgresql-8.4-plsh_1.3-3_i386.deb postgresql-8.4-plsh_1.3-3_amd64.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]
Files in first .deb but not in second
-
-rw-r--r-- root/root /usr/share/doc/postgresql-8.4-plsh/NEWS.gz
-rw-r--r-- root/root /usr/share/doc/postgresql-8.4-plsh/README
-rw-r--r-- root/root /usr/share/doc/postgresql-8.4-plsh/README.Debian
-rw-r--r-- root/root /usr/share/doc/postgresql-8.4-plsh/changelog.Debian.gz
-rw-r--r-- root/root /usr/share/doc/postgresql-8.4-plsh/copyright
Control files: lines which differ (wdiff format)
Architecture: [-i386-] {+amd64+}
Depends: libc6 (= [-2.2),-] {+2.2.5),+} postgresql-8.4
Installed-Size: [-80-] {+56+}
--
Jakub Wilk
diff -u postgresql-plsh-1.3/debian/rules postgresql-plsh-1.3/debian/rules
--- postgresql-plsh-1.3/debian/rules
+++ postgresql-plsh-1.3/debian/rules
@@ -46,6 +46,7 @@
binary-arch: install
dh_testdir
dh_testroot
+ dh_installdocs -a
dh_install -a
dh_link -a
dh_strip -a
@@ -58,20 +59,7 @@
dh_builddeb -a
-binary-indep: install
- dh_testdir
- dh_testroot
- dh_installdocs -a
- dh_install -i
- dh_link -i
- dh_compress -i
- dh_fixperms -i
- dh_installdeb -i
- dh_gencontrol -i
- dh_md5sums -i
- dh_builddeb -i
- dh_installchangelogs
-
+binary-indep:
binary: binary-arch binary-indep
signature.asc
Description: Digital signature
Bug#588763: /usr/share/doc/klibc-utils/ is empty
On Fri, 20 Aug 2010, Adam D. Barratt wrote: Hi, On Thu, 2010-07-15 at 12:05 +0200, maximilian attems wrote: thanks for the info, currently waiting on an upstream pull request. http://www.zytor.com/pipermail/klibc/2010-July/002667.html will upload aboves fix together with soon to appear 1.5.19. I see that 1.5.19 has now been released. Are you planning an upload soon, either for .19 or at least to fix this bug? yes, plan to upload a fixed klibc soonest in the next 2 days with high urgency. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593041: RE : Bug#593041: imagemagick: FTBFS: libMagickWand.so: No such file: No such file or directory
Hi, I suppose it is a parallel build issue. Will glimbse at it after a sleep Le 22 août 2010 18:18, Julien Cristau jcris...@debian.org a écrit : On Sun, Aug 15, 2010 at 09:44:16 +0200, Lucas Nussbaum wrote: Source: imagemagick Version: 8:6 It built just fine on the buildds (and here) 10 days ago... Cheers, Julien -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJMcU1vAAoJEDEBgAUJBeQMHnkQALRkru3XcvN86GzaVuTh4MKd c0PUmUSvSLmvZLmwhgsulH1pLKr7gRYEf3za4msyIY3djR3KsI7j95auE5IqMx/u v80j89B9MuOL61CLaT84C98HJ+NrMV9jXZixBCcdbe3sRbTcXOku3PqPJQcY5ab5 i4FIZosYDQzlp7bz6Y165VdEdS+kmLBsFEOl3rfZ2z0gUvxGO1b5OlPdgM8xJ9mv hV+7CHwQ0p346zlw0Hd6HHkWVqibGxNuagpbBhSsAGA8QyHpWNbATnAoML0rdfS4 o3XXkdyHEWPV8Z3om9ia8xsCIWwfluBhp4EXJoN5HgYPKL26eMcA8qxZrtvbBZh7 6uduPKZFeMrPxqdX2gFUeT//9uXbpbkxjIPSeQjds7fCSQkpZ+GsEmhDzhWuv4QH hQmBk4sfsdV0b1o2LPtGjkn9AO2Ou04m9e/YMzONDWjingof2KDOyZ+9xghwACoW B2l02bYyzRiBWdyypHULSNrsILKPS6X8tgPFHCk+Ad2Iw4rjtYRvBPwhUV9/jP4m pzjf3RMzpR3zt00vrbYvBjuYHYrWz2fU7MrYUtaFc+pwsR4avgXEvCOiBrp+8OjO 5AiUM3NFftmESMOMgnXS/PnyB25zxVDvVLugRDNBhCy+1R3HONLES0SUKARhCBD1 wauE3N7j8FU3DjZE+Jf+ =yNIO -END PGP SIGNATURE-
Processed: tagging 568358, tagging 591147, tagging 590912
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 568358 + pending Bug #568358 [cyrus-sasl2-heimdal] remerge cyrus-sasl2-heimdal with cyrus-sasl2 Added tag(s) pending. tags 591147 + pending Bug #591147 [libsasl2-modules-gssapi-heimdal] libsasl2-modules-gssapi-heimdal: needs rebuilding against new Heimdal Added tag(s) pending. tags 590912 + pending Bug #590912 [src:cyrus-sasl2-heimdal] FTBFS: .libs/gssapi.o:(.got2+0x2c): undefined reference to `gss_nt_service_name' Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 590912: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590912 591147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591147 568358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568358 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#591648: marked as done (doxygen: bus error/segmentation fault on kfreebsd-*, armel, hppa, powerpc, s390)
Your message dated Mon, 23 Aug 2010 03:02:12 + with message-id e1onnia-0001gj...@franck.debian.org and subject line Bug#591648: fixed in doxygen 1.7.1-2 has caused the Debian Bug report #591648, regarding doxygen: bus error/segmentation fault on kfreebsd-*, armel, hppa, powerpc, 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.) -- 591648: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: clp Version: 1.12.0-2 Severity: serious Justification: FTBFS User: debian-...@lists.debian.org Usertags: kfreebsd Hi, your package FTBFS on kfreebsd-amd64: | Generating docs for compound ClpFactorization... | /build/buildd-clp_1.12.0-2-kfreebsd-amd64-vODaOz/clp-1.12.0/Clp/src/ClpPackedMatrix.hpp:491: warning: end of comment block while expecting command /code | /build/buildd-clp_1.12.0-2-kfreebsd-amd64-vODaOz/clp-1.12.0/Clp/src/ClpPackedMatrix.hpp:491: warning: end of comment block while expecting command /code | /build/buildd-clp_1.12.0-2-kfreebsd-amd64-vODaOz/clp-1.12.0/Clp/src/ClpPackedMatrix.hpp:560: warning: end of comment block while expecting command /code | /build/buildd-clp_1.12.0-2-kfreebsd-amd64-vODaOz/clp-1.12.0/Clp/src/ClpPackedMatrix.hpp:560: warning: end of comment block while expecting command /code | /build/buildd-clp_1.12.0-2-kfreebsd-amd64-vODaOz/clp-1.12.0/Clp/src/ClpSimplexDual.hpp:263: warning: Invalid list item found | /build/buildd-clp_1.12.0-2-kfreebsd-amd64-vODaOz/clp-1.12.0/Clp/src/ClpSimplexNonlinear.hpp:82: warning: Invalid list item found | /build/buildd-clp_1.12.0-2-kfreebsd-amd64-vODaOz/clp-1.12.0/Clp/src/ClpSimplexOther.hpp:104: warning: Invalid list item found | /build/buildd-clp_1.12.0-2-kfreebsd-amd64-vODaOz/clp-1.12.0/Clp/src/ClpSimplexPrimal.hpp:211: warning: Invalid list item found | make: *** [debian/stamp-build-coinor-libclp-doc] Segmentation fault and on kfreebsd-i386: | Generating docs for compound ClpLinearObjective... | /build/buildd-clp_1.12.0-2-kfreebsd-i386-CPNs9Q/clp-1.12.0/Clp/src/ClpPackedMatrix.hpp:491: warning: end of comment block while expecting command /code | /build/buildd-clp_1.12.0-2-kfreebsd-i386-CPNs9Q/clp-1.12.0/Clp/src/ClpPackedMatrix.hpp:491: warning: end of comment block while expecting command /code | /build/buildd-clp_1.12.0-2-kfreebsd-i386-CPNs9Q/clp-1.12.0/Clp/src/ClpPackedMatrix.hpp:560: warning: end of comment block while expecting command /code | /build/buildd-clp_1.12.0-2-kfreebsd-i386-CPNs9Q/clp-1.12.0/Clp/src/ClpPackedMatrix.hpp:560: warning: end of comment block while expecting command /code | /build/buildd-clp_1.12.0-2-kfreebsd-i386-CPNs9Q/clp-1.12.0/Clp/src/ClpSimplexDual.hpp:263: warning: Invalid list item found | /build/buildd-clp_1.12.0-2-kfreebsd-i386-CPNs9Q/clp-1.12.0/Clp/src/ClpSimplexNonlinear.hpp:82: warning: Invalid list item found | /build/buildd-clp_1.12.0-2-kfreebsd-i386-CPNs9Q/clp-1.12.0/Clp/src/ClpSimplexOther.hpp:104: warning: Invalid list item found | /build/buildd-clp_1.12.0-2-kfreebsd-i386-CPNs9Q/clp-1.12.0/Clp/src/ClpSimplexPrimal.hpp:211: warning: Invalid list item found | make: *** [debian/stamp-build-coinor-libclp-doc] Bus error Full build logs: https://buildd.debian.org/status/package.php?p=clp Mraw, KiBi. ---End Message--- ---BeginMessage--- Source: doxygen Source-Version: 1.7.1-2 We believe that the bug you reported is fixed in the latest version of doxygen, which is due to be installed in the Debian FTP archive: doxygen-doc_1.7.1-2_all.deb to main/d/doxygen/doxygen-doc_1.7.1-2_all.deb doxygen-gui_1.7.1-2_i386.deb to main/d/doxygen/doxygen-gui_1.7.1-2_i386.deb doxygen_1.7.1-2.diff.gz to main/d/doxygen/doxygen_1.7.1-2.diff.gz doxygen_1.7.1-2.dsc to main/d/doxygen/doxygen_1.7.1-2.dsc doxygen_1.7.1-2_i386.deb to main/d/doxygen/doxygen_1.7.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 591...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose d...@debian.org (supplier of updated doxygen 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, 23 Aug 2010 04:13:43 +0200 Source: doxygen Binary: doxygen doxygen-doc doxygen-gui Architecture:
Bug#593317: marked as done (doxygen 1.7.1 causes FTBS on hppa,kfreebsd-i386 for shogun)
Your message dated Mon, 23 Aug 2010 03:02:12 + with message-id e1onnia-0001gm...@franck.debian.org and subject line Bug#593317: fixed in doxygen 1.7.1-2 has caused the Debian Bug report #593317, regarding doxygen 1.7.1 causes FTBS on hppa,kfreebsd-i386 for shogun 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.) -- 593317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: doxygen Version: 1.7.1-1 Severity: serious A rebuild of shogun 0.9.3 hangs with doxygen 1.7.1 generating the documentation on hppa and kfreebsd-i386 (other archs work): https://buildd.debian.org/fetch.cgi?pkg=shogunarch=hppaver=0.9.3-3stamp=1280603495file=logas=raw Generating image form_72.png for formula Generating image form_73.png for formula Generating image form_74.png for formula E: Caught signal 'Terminated': terminating immediately make[1]: *** [doc] Terminated make: *** [debian/debian-stamp-build-indep] Terminated GeneratinBuild killed with signal TERM after 150 minutes of inactivity https://buildd.debian.org/fetch.cgi?pkg=shogunarch=kfreebsd-i386ver=0.9.3-3stamp=1281595461file=logas=raw Running dot for graph 137/249 Running dot for graph 138/249 E: Caught signal 'Terminated': terminating immediately make[1]: *** [doc] Terminated make: *** [debian/debian-stamp-build-indep] Terminated Running dot for graBuild killed with signal TERM after 150 minutes of inactivity Interestingly, the hangs are at different stages when creating the documentation, one generating a .png and one a graph via graphviz (ultimately a .png again I guess). -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32.15-sonne (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages doxygen depends on: ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.4-8 GCC support library ii libstdc++64.4.4-8The GNU Standard C++ Library v3 Versions of packages doxygen recommends: ii texlive-extra-utils 2009-9 TeX Live: TeX auxiliary programs Versions of packages doxygen suggests: ii doxygen-doc 1.7.1-1Documentation for doxygen ii doxygen-gui 1.7.1-1GUI configuration tool for doxygen ii graphviz 2.26.3-5 rich set of graph drawing tools -- no debconf information ---End Message--- ---BeginMessage--- Source: doxygen Source-Version: 1.7.1-2 We believe that the bug you reported is fixed in the latest version of doxygen, which is due to be installed in the Debian FTP archive: doxygen-doc_1.7.1-2_all.deb to main/d/doxygen/doxygen-doc_1.7.1-2_all.deb doxygen-gui_1.7.1-2_i386.deb to main/d/doxygen/doxygen-gui_1.7.1-2_i386.deb doxygen_1.7.1-2.diff.gz to main/d/doxygen/doxygen_1.7.1-2.diff.gz doxygen_1.7.1-2.dsc to main/d/doxygen/doxygen_1.7.1-2.dsc doxygen_1.7.1-2_i386.deb to main/d/doxygen/doxygen_1.7.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 593...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose d...@debian.org (supplier of updated doxygen 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, 23 Aug 2010 04:13:43 +0200 Source: doxygen Binary: doxygen doxygen-doc doxygen-gui Architecture: source i386 all Version: 1.7.1-2 Distribution: unstable Urgency: low Maintainer: Matthias Klose d...@debian.org Changed-By: Matthias Klose d...@debian.org Description: doxygen- Documentation system for C, C++, Java, Python and other languages doxygen-doc - Documentation for doxygen doxygen-gui - GUI configuration tool for doxygen Closes: 591648 593317 Changes: doxygen (1.7.1-2) unstable; urgency=low . * Don't use threads for the `dot' runs (Petr Salinger). Closes: #591648, #593317. Checksums-Sha1: c9a8f4f482c5af628a88ca45bbe91413bfc9b6aa 1213 doxygen_1.7.1-2.dsc 570eb9af70ded28dfc5c8c25a83081b0abe4d0c0 17384
Processed: your mail
Processing commands for cont...@bugs.debian.org: tags 593829 + patch pending Bug #593829 [sabnzbdplus] sabnzbdplus: sabnzbd.ini defaults to world-readable Added tag(s) pending and patch. stop Stopping processing here. Please contact me if you need assistance. -- 593829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593829 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#591111: libdbd-sqlite3-perl: FTBFS: failed tests
tag 59 patch
thanks
On Thu, Aug 05, 2010 at 11:43:07AM +0900, Ansgar Burchardt wrote:
Lucas Nussbaum lu...@lucas-nussbaum.net writes:
Source: libdbd-sqlite3-perl
Version: 1.29-2
t/07_error.t . ok
# Failed test at t/08_busy.t line 101.
# Your testing environment might be too slow to pass this test:
DBD::SQLite::db do failed: disk I/O error at t/08_busy.t line 100,
READER line 1.
This only happens with libsqlite3-dev 3.7.0-1, the test suite passes
with the older 3.6.23.1-4. Should we reassign this to libsqlite3?
No, I don't think so. I think it's just a libdbd-sqlite3-perl test suite
problem. Its child processes clean up database files while the parent
keeps them open. This used to work with earlier sqlite3 versions but
write locks now seem to do a stat() on the file and fail if it's missing.
I don't think writing to a deleted database file is useful in the real
world, so it should be enough to change the test suite. Patch attached.
--
Niko Tyni nt...@debian.org
From 89c8a661e61bbf0fb1d1e5050262390649e13f2a Mon Sep 17 00:00:00 2001
From: Niko Tyni nt...@debian.org
Date: Mon, 23 Aug 2010 08:15:15 +0300
Subject: [PATCH] Don't clean temporary files in child processes
As of SQLite 3.7.0, write locks try to stat() the database
file and fail with a 'Disk I/O error' if it is missing. This
breaks those tests that fork child processes (namely 08_busy.t
and t/28_schemachange.t) because the child process removes
the database file in the END block.
The fix is to disable the clean() function for child processes.
See http://bugs.debian.org/59
---
t/lib/Test.pm |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/t/lib/Test.pm b/t/lib/Test.pm
index 80e50ce..8d1be25 100644
--- a/t/lib/Test.pm
+++ b/t/lib/Test.pm
@@ -7,6 +7,7 @@ use Exporter ();
use File::Spec ();
use Test::More ();
+my $parent;
use vars qw{$VERSION @ISA @EXPORT @CALL_FUNCS};
BEGIN {
$VERSION = '1.29';
@@ -15,6 +16,7 @@ BEGIN {
# Allow tests to load modules bundled in /inc
unshift @INC, 'inc';
+ $parent = $$;
}
# Always load the DBI module
@@ -22,6 +24,7 @@ use DBI ();
# Delete temporary files
sub clean {
+ return if $$ != $parent;
unlink( 'foo' );
unlink( 'foo-journal' );
}
--
1.7.1
Processed: Re: Bug#591111: libdbd-sqlite3-perl: FTBFS: failed tests
Processing commands for cont...@bugs.debian.org: tag 59 patch Bug #59 [src:libdbd-sqlite3-perl] libdbd-sqlite3-perl: FTBFS: failed tests Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 59: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=59 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#592678: Fw: Bug#592678: gxemul: FTBFS on mips*: ../include/cpu.h:441: error: expected unqualified-id before numeric constant
Tis 2010-08-17 klockan 22:30 +0100 skrev Jonathan Wiltshire: - Forwarded message from Jakub Wilk jw...@debian.org - Source: gxemul Version: 0.6.0-2 Severity: serious Justification: FTBFS gxemul fails to build from source on mips[0] and mipsel[1] with the following error: .. mips is a pre-defined macro on mips* architectures: $ cpp -dM /dev/null | grep 'define mips' #define mips 1 I saw the same problem on very old versions of OpenBSD/arc (and maybe also NetBSD), where the architecture name in lower case was defined. Older versions of GXemul has a hack in the configure script which undefined those macros. That code was removed, because the platforms that [I knew of at that time that] it affected are not supported build environments any longer. Is it common that mips is defined on Linux-based systems? How about arm on ARM machines, alpha on Alphas, etc.? Anders -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
