Bug#685351: src:gnumed-client: Missing source code for *.js files
Package: src:gnumed-client Version: 1.1.17-1 Severity: serious Justification: Policy 2.1 gnumed-doc installs /usr/share/doc/gnumed/user-manual/rsrc/System/JSTreeContrib/jquery.jstree.js. However, the file is present in the source package without source code. Instructions on which tools were used to create it are also missing. And the lack of copyright notices probably renders the package non-distributable. All or most of these issues seem to apply to other javascript files in the package (like jquery.foswiki.js). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685353: qemu-kvm: kvm process hangs with 100% CPU usage
Package: qemu-kvm Version: 1.1.0+dfsg-3 Severity: grave Justification: causes non-serious data loss Dear Maintainer, I currently run 3 VMs using libvirt/qemu-kvm. Two of them are mostly idle and stable, but the third one locks up within 1 or 2 days. This third VM uses an emulated ES1370 sound card (host has an ASUS Xonar DX sound card), to stream host audio input to an icecast server using darkice. The hanging kvm process uses 100% CPU, there's no serial console anymore, no access to VNC anymore. No output on netconsole either. Unfortunately, I cannot even get a useful gdb backtrace: # gdb GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 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 x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. (gdb) attach 3259 Attaching to process 3259 Reading symbols from /usr/bin/kvm...Reading symbols from /usr/lib/debug/usr/bin/kvm...done. Unable to read JIT descriptor from remote memory! (gdb) info threads Id Target Id Frame· * 1process 3259 kvm 0x7f32ebb20f7b in ?? () (gdb) thread apply all bt full Thread 1 (process 3259): #0 0x7f32ebb20f7b in ?? () No symbol table info available. #1 0x7f32ee9758c0 in ?? () No symbol table info available. #2 0xc1dc11134e09ed00 in ?? () No symbol table info available. #3 0x7f32ee9758c0 in ?? () No symbol table info available. #4 0x7f32eeb0c4d0 in ?? () No symbol table info available. #5 0x002c in ?? () No symbol table info available. #6 0x03d4 in ?? () No symbol table info available. #7 0xf05cb962 in ?? () No symbol table info available. #8 0x7f32ee98aa70 in ?? () No symbol table info available. #9 0x in ?? () No symbol table info available. (gdb)· No useful strace output either: # strace -ff -p3259 Process 3259 attached with 2 threads - interrupt to quit [pid 3270] futex(0x7f32ec94ea80, FUTEX_WAIT_PRIVATE, 2, NULL^C unfinished ... Process 3259 detached Process 3270 detached Both the guest and the host use this kernel: Linux version 3.2.0-3-amd64 (Debian 3.2.23-1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Mon Jul 23 02:45:17 UTC 2012 kvm command line (run by libvirt): 105 3259 61.3 27.2 1540272 1071712 ? RLl Aug18 1331:39 /usr/bin/kvm -S -M pc-1.1 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name mp3 -uuid 25d2b76c-9533-c55a-b5e2-07da213886f1 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/mp3.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/vg_vms/lv_mp3,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-di -netdev tap,fd=20,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:b1:e7:80,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:2 -vga cirrus -device ES1370,id=sound0,bus=pci.0,addr=0x6 -device i6300esb,id=watchdog0,bus=pci.0,addr=0x7 -watchdog-action reset -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 I tried running with clocksource=acpi_pm inside the VM, or without VNC, all the same: Hung kvm within 1 or 2 days. libvirt domain XML: domain type='kvm' id='3' namemp3/name uuid25d2b76c-9533-c55a-b5e2-07da213886f1/uuid memory unit='KiB'1048576/memory currentMemory unit='KiB'1048576/currentMemory vcpu placement='static'1/vcpu os type arch='x86_64' machine='pc-1.1'hvm/type boot dev='hd'/ /os features acpi/ apic/ pae/ /features clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashrestart/on_crash devices emulator/usr/bin/kvm/emulator disk type='block' device='disk' driver name='qemu' type='raw'/ source dev='/dev/vg_vms/lv_mp3'/ target dev='vda' bus='virtio'/ alias name='virtio-disk0'/ address type='pci' domain='0x' bus='0x00' slot='0x05' function='0x0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='52:54:00:b1:e7:80'/ source bridge='br0'/
Bug#650454: checkgmail: keeps popping up login window but fails to log in
On Mon, Aug 20, 2012 at 3:17 AM, Jonathan Nieder jrnie...@gmail.com wrote: Sandro Tosi wrote: If you want to upload it to stable, feel free to. Thanks. pu bug filed. awesome, thanks! I'm not a DD, so I can't upload directly. If the release team gives the ok, would you like to sponsor the upload? (If not, that's fine and I can look for another sponsor.) I'd prefer if you could look for another sponsor. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685351: src:gnumed-client: Missing source code for *.js files
Hi Stepan, thanks for your QA work in the pool of Debian sources. I just would like you to know that I will not handle this bug until there is some kind of outcome of the currently running discussion at debian-devel list starting here: http://lists.debian.org/debian-devel/2012/08/msg00365.html In the current situation from my perspective it also would not make sense to seek even further through the package pool for cases like this until there is some consensus about this - it might end up at noise in the BTS and keeps people busy instead of focussing on the release. Kind regards and thanks for the report anyway Andreas. On Mon, Aug 20, 2012 at 09:59:44AM +0400, Stepan Golosunov wrote: Package: src:gnumed-client Version: 1.1.17-1 Severity: serious Justification: Policy 2.1 gnumed-doc installs /usr/share/doc/gnumed/user-manual/rsrc/System/JSTreeContrib/jquery.jstree.js. However, the file is present in the source package without source code. Instructions on which tools were used to create it are also missing. And the lack of copyright notices probably renders the package non-distributable. All or most of these issues seem to apply to other javascript files in the package (like jquery.foswiki.js). -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685351: Help: Please seek for sources of some JS files in GNUmed [Was: Bug#685351: src:gnumed-client: Missing source code for *.js files]
Hi, after reading the bug report twice I noticed that the problem is actually not comparable to the issue discussed currently on debian-devel@l.d.o, because the files are actually used in the package and not replaced. So if you want to help Debian Med you can do some research and find the sources of the following files inside the gnumed-doc package: user-manual/rsrc/System/JSTreeContrib/jquery.jstree.js user-manual/rsrc/System/JQueryPlugin/plugins/foswiki/jquery.foswiki.js user-manual/rsrc/System/PatternSkin/pattern.js user-manual/rsrc/System/JavascriptFiles/foswikiForm.js user-manual/rsrc/System/JavascriptFiles/foswikiString.js user-manual/rsrc/System/JavascriptFiles/foswikiPref.js Please halpe me saving my time and doing some more technical work. This could be your contribution to fix a RC bug in Wheezy. Kind regards Andreas. - Forwarded message from Stepan Golosunov ste...@golosunov.pp.ru - Date: Mon, 20 Aug 2012 09:59:44 +0400 From: Stepan Golosunov ste...@golosunov.pp.ru To: Debian Bug Tracking System sub...@bugs.debian.org Subject: Bug#685351: src:gnumed-client: Missing source code for *.js files X-Debian-PR-Message: report 685351 X-Debian-PR-Package: src:gnumed-client X-Debian-PR-Keywords: X-Debian-PR-Source: gnumed-client X-Spam_score: -2.3 Package: src:gnumed-client Version: 1.1.17-1 Severity: serious Justification: Policy 2.1 gnumed-doc installs /usr/share/doc/gnumed/user-manual/rsrc/System/JSTreeContrib/jquery.jstree.js. However, the file is present in the source package without source code. Instructions on which tools were used to create it are also missing. And the lack of copyright notices probably renders the package non-distributable. All or most of these issues seem to apply to other javascript files in the package (like jquery.foswiki.js). ___ Debian-med-packaging mailing list debian-med-packag...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging - End forwarded message - -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685353: qemu-kvm: kvm process hangs with 100% CPU usage
On 20.08.2012 10:01, Mike Gerber wrote: Package: qemu-kvm Version: 1.1.0+dfsg-3 Severity: grave Justification: causes non-serious data loss Dear Maintainer, I currently run 3 VMs using libvirt/qemu-kvm. Two of them are mostly idle and stable, but the third one locks up within 1 or 2 days. This third VM uses an emulated ES1370 sound card (host has an ASUS Xonar DX sound card), to stream host audio input to an icecast server using darkice. Does this also happen without ES1370 device? Do other guests use this device too? How active the audio/sound usage is? It is vital to understand where the problem is as close as possible, since it isn't easy to reproduce the problem, and you apparently pointed out one difference (ES1370) which might be the root of the issue, but might be not. The hanging kvm process uses 100% CPU, there's no serial console anymore, no access to VNC anymore. No output on netconsole either. Unfortunately, I cannot even get a useful gdb backtrace: # gdb GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 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 x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. (gdb) attach 3259 Attaching to process 3259 Reading symbols from /usr/bin/kvm...Reading symbols from /usr/lib/debug/usr/bin/kvm...done. Unable to read JIT descriptor from remote memory! (gdb) info threads Id Target Id Frame· * 1process 3259 kvm 0x7f32ebb20f7b in ?? () (gdb) thread apply all bt full Thread 1 (process 3259): #0 0x7f32ebb20f7b in ?? () No symbol table info available. You can try installing qemu-kvm-gdb to get symbol table. That might be useful. If that wont help, it'll mean we have a bug in qemu-kvm package at providing debugging info. No useful strace output either: # strace -ff -p3259 Process 3259 attached with 2 threads - interrupt to quit [pid 3270] futex(0x7f32ec94ea80, FUTEX_WAIT_PRIVATE, 2, NULL^C unfinished ... Process 3259 detached Process 3270 detached Hmm. And that's all? In that case it'd be very nice really to have a backtrace. Both the guest and the host use this kernel: Linux version 3.2.0-3-amd64 (Debian 3.2.23-1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Mon Jul 23 02:45:17 UTC 2012 kvm command line (run by libvirt): 105 3259 61.3 27.2 1540272 1071712 ? RLl Aug18 1331:39 /usr/bin/kvm -S -M pc-1.1 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name mp3 -uuid 25d2b76c-9533-c55a-b5e2-07da213886f1 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/mp3.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/vg_vms/lv_mp3,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-di -netdev tap,fd=20,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:b1:e7:80,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:2 -vga cirrus -device ES1370,id=sound0,bus=pci.0,addr=0x6 -device i6300esb,id=watchdog0,bus=pci.0,addr=0x7 -watchdog-action reset -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 That's nothing fancy/unusual. I tried running with clocksource=acpi_pm inside the VM, or without VNC, all the same: Hung kvm within 1 or 2 days. Any help on how to track this down - for example how to make gdb output useful - would be appreciated! As for gdb - see above. Meanwhile I'll try to see if debugging generally works. Also, there's a new version (prerelease - I sent an unblock request to the release team about it) available at my site -- http://www.corpit.ru/mjt/tmp/qemu-kvm/ , in particular, http://www.corpit.ru/mjt/tmp/qemu-kvm/qemu-kvm_1.1.1+dfsg-1_amd64.deb (it is all signed with my regular debian gpg key if you're concerned). Can you please try this version too? It contains many bugfixes in all areas, and there's some (albiet small) chance this issue is already fixed. What activity your guest performs? Maybe I can try to reproduce your issue locally, you provided almost all information needed for this except of some mention of the workload. Thank you for a good bugreport! /mjt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685314: qemu-kvm: Newer versions of qemu-kvm break libguestfs
tags 685314 - moreinfo + pending thanks On 20.08.2012 01:38, Hilko Bengen wrote: Michael, libguestfs-test-tool runs fine qemu-kvm_1.1.1+dfsg-1_amd64.deb. Ok. I'm assuming this is #680719, which indeed looks very close. Marking as pending-upload. Thank you for verifying! Thanks for your quick response. heh. I wish it is always this simple -- I already had everything for the reply, including the package ready (well, almost -- note it is UNRELEASED still) for upload ;) Now waiting for the release team to process the unblock request. Thanks, /mjt -- 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#685314: qemu-kvm: Newer versions of qemu-kvm break libguestfs
Processing commands for cont...@bugs.debian.org: tags 685314 - moreinfo + pending Bug #685314 [qemu-kvm] qemu-kvm: Newer versions of qemu-kvm break libguestfs Removed tag(s) moreinfo. Bug #685314 [qemu-kvm] qemu-kvm: Newer versions of qemu-kvm break libguestfs Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 685314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685314 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#684824: marked as done (apr: FTBFS: rm: cannot remove `libtoolT': No such file or directory)
Your message dated Mon, 20 Aug 2012 08:54:47 +0200
with message-id 20120820065447.ga19...@xanadu.blop.info
and subject line Re: Bug#684824: apr: FTBFS: rm: cannot remove `libtoolT': No
such file or directory
has caused the Debian Bug report #684824,
regarding apr: FTBFS: rm: cannot remove `libtoolT': No such file or directory
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.)
--
684824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: apr
Version: 1.4.6-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120814 qa-ftbfs
Justification: FTBFS in wheezy on amd64
Hi,
During a rebuild of all packages in *wheezy*, your package failed to
build on amd64.
Relevant part:
debian/rules build
dh_testdir
mkdir -p build-amd64/docs
./buildconf
buildconf: checking installation...
buildconf: python version 2.7.3rc2 (ok)
buildconf: autoconf version 2.69 (ok)
buildconf: libtool version 2.4.2 (ok)
buildconf: copying libtool helper files using /usr/bin/libtoolize
buildconf: creating include/arch/unix/apr_private.h.in ...
buildconf: creating configure ...
buildconf: generating 'make' outputs ...
buildconf: rebuilding rpm spec file
# we need to force the use of bash here. Otherwise, if apr is built with
# /bin/sh - /bin/bash, the resulting libtool will not work on systems
# where /bin/sh - /bin/dash
cd build-amd64 CFLAGS= -pipe -Wall -g -O2 CPPFLAGS= LDFLAGS=
ac_cv_prog_AWK=mawk apr_cv_sctp=no CONFIG_SHELL=/bin/bash /bin/bash
../configure --host=x86_64-linux-gnu --build=x86_64-linux-gnu
--enable-layout=Debian --includedir=\${prefix}/usr/include/apr-1.0
--with-installbuilddir=\${prefix}/usr/share/apr-1.0/build
--enable-nonportable-atomics --enable-allocator-uses-mmap
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
Configuring APR library
Platform: x86_64-pc-linux-gnu
checking for working mkdir -p... yes
APR Version: 1.4.6
checking for chosen layout... Debian
checking for x86_64-linux-gnu-gcc... x86_64-linux-gnu-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-linux-gnu-gcc accepts -g... yes
checking for x86_64-linux-gnu-gcc option to accept ISO C89... none needed
checking for a sed that does not truncate output... /bin/sed
Applying APR hints file rules for x86_64-pc-linux-gnu
setting CPPFLAGS to -DLINUX=2
adding -D_REENTRANT to CPPFLAGS
adding -D_GNU_SOURCE to CPPFLAGS
(Default will be unix)
checking whether make sets $(MAKE)... yes
checking how to run the C preprocessor... x86_64-linux-gnu-gcc -E
checking for gawk... (cached) mawk
checking whether ln -s works... yes
checking for x86_64-linux-gnu-ranlib... no
checking for ranlib... ranlib
checking for a BSD-compatible install... /usr/bin/install -c
checking for rm... rm
checking for as... as
checking for cpp... cpp
checking for x86_64-linux-gnu-ar... no
checking for ar... ar
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for library containing strerror... none required
checking whether system uses EBCDIC... no
performing libtool configuration...
checking how to print strings... printf
checking for a sed that does not truncate output... (cached) /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by x86_64-linux-gnu-gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking the maximum length of command line arguments... 3458764513820540925
checking whether the shell understands some XSI constructs... yes
Bug#684848: marked as done (tcsh: FTBFS: | /«PKGBUILDDIR»/conftest.c:20: undefined reference to `crypt')
Your message dated Mon, 20 Aug 2012 09:19:53 +0200
with message-id 20120820071953.ga18...@xanadu.blop.info
and subject line Re: Bug#684848: tcsh: FTBFS: | /«PKGBUILDDIR»/conftest.c:20:
undefined reference to `crypt'
has caused the Debian Bug report #684848,
regarding tcsh: FTBFS: | /«PKGBUILDDIR»/conftest.c:20: undefined reference to
`crypt'
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.)
--
684848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: tcsh
Version: 6.18.01-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120814 qa-ftbfs
Justification: FTBFS in wheezy on amd64
Hi,
During a rebuild of all packages in *wheezy*, your package failed to
build on amd64.
Relevant part:
gcc -o tcsh -Wl,-z,relro -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Werror=format-security -D_FILE_OFFSET_BITS=64 -I. -I. sh.o sh.dir.o
sh.dol.o sh.err.o sh.exec.o sh.char.o sh.exp.o sh.file.o sh.func.o sh.glob.o
sh.hist.o sh.init.o sh.lex.o sh.misc.o sh.parse.o sh.print.o sh.proc.o
sh.sem.o sh.set.o sh.time.o glob.o mi.termios.o ma.setp.o vms.termcap.o
tw.help.o tw.init.o tw.parse.o tw.spell.o tw.comp.o tw.color.o ed.chared.o
ed.refresh.o ed.screen.o ed.init.o ed.inputl.o ed.defns.o ed.xmap.o ed.term.o
tc.alloc.o tc.bind.o tc.const.o tc.defs.o tc.disc.o tc.func.o tc.nls.o
tc.os.o tc.printf.o tc.prompt.o tc.sched.o tc.sig.o tc.str.o tc.vers.o
tc.who.o -ltermcap -lcrypt
make[3]: Entering directory `/«PKGBUILDDIR»/nls'
C
et
finnish
french
german
greek
italian
ja
pl
russian
spanish
ukrainian
make[3]: Leaving directory `/«PKGBUILDDIR»/nls'
make[2]: Leaving directory `/«PKGBUILDDIR»'
/usr/bin/make catalogs
make[2]: Entering directory `/«PKGBUILDDIR»'
make[3]: Entering directory `/«PKGBUILDDIR»/nls'
make[3]: Nothing to be done for `catalogs'.
make[3]: Leaving directory `/«PKGBUILDDIR»/nls'
make[2]: Leaving directory `/«PKGBUILDDIR»'
make[1]: Leaving directory `/«PKGBUILDDIR»'
debian/rules override_dh_auto_test
make[1]: Entering directory `/«PKGBUILDDIR»'
LS_COLORS= make check || (cat testsuite.log ; false)
make[2]: Entering directory `/«PKGBUILDDIR»'
{\
echo '# Signature of the current package.'; \
echo 'm4_define([AT_PACKAGE_NAME], [tcsh])';\
echo 'm4_define([AT_PACKAGE_TARNAME], [tcsh])'; \
echo 'm4_define([AT_PACKAGE_VERSION], [6.18.01])'; \
echo 'm4_define([AT_PACKAGE_STRING],[tcsh 6.18.01])';\
echo 'm4_define([AT_PACKAGE_BUGREPORT], [http://bugs.gw.com/])'; \
} ./tests/package.m4
autom4te --language=autotest -I ./tests \
./tests/testsuite.at -o tests/testsuite.tmp
mv tests/testsuite.tmp tests/testsuite
/bin/sh ./tests/testsuite
## ##
## tcsh 6.18.01 test suite. ##
## ##
1: beepcmd skipped (aliases.at:3)
2: cwdcmd ok
3: jobcmd skipped (aliases.at:19)
4: helpcommand skipped (aliases.at:20)
5: periodicskipped (aliases.at:21)
6: precmd skipped (aliases.at:22)
7: postcmd ok
8: shell ok
9: -b ok
10: -c ok
11: -d skipped (arguments.at:34)
12: -e ok
13: -f skipped (arguments.at:46)
14: -i ok
15: -l skipped (arguments.at:61)
16: -m skipped (arguments.at:65)
17: -q skipped (arguments.at:71)
18: -s ok
19: -t ok
20: -v ok
21: -x ok
22: -V skipped
(arguments.at:126)
23: -X
Bug#685324: [Pkg-mediawiki-devel] Bug#685324: Local File Inclusion Vulnerability in contrib script
On Sun, 19 Aug 2012, Benny Baumann wrote: Please upgrade the php-geshi package to latest upstream. With the freeze this is no longer possible. If this is indeed a security issue, we can either apply a backported fix or have the package removed from the release, at this point in time. bye, //mirabilos -- «MyISAM tables -will- get corrupted eventually. This is a fact of life. » “mysql is about as much database as ms access” – “MSSQL at least descends from a database” “it's a rebranded SyBase” “MySQL however was born from a flatfile and went downhill from there” – “at least jetDB doesn’t claim to be a database” (#nosec)‣‣‣ Please let MySQL and MariaDB finally die! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650454: checkgmail: keeps popping up login window but fails to log in
Sandro Tosi wrote: I'd prefer if you could look for another sponsor. Will do. Thanks again for the quick feedback. Ciao, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#570516: md UUID changed
On 19.08.2012 21:13, Ivo De Decker wrote: Hi, On Mon, Feb 21, 2011 at 11:59:25AM +, Steve McIntyre wrote: The hostname didn’t change. However the latter might be possible, I don’t really know. The MD array was built from lenny’s d-i. I've just started to upgrade my main fileserver at home from Lenny to Squeeze, and I think I've been bitten by this bug (or something very similar) in a big way. I've started off with a system running a locally-built 2.6.28 kernel and a number of RAID devices, all configured with version 0.9 superblocks (the default in Lenny, AFAICT). It seems both the reports for this bug are for upgrades from lenny to squeeze. Is this bug still relevant for wheezy? Does this problem still happen? If the problem is related to an upgrade from lenny, the bug should be marked as fixed in mdadm 3.2.2-1, as we don't support upgrades from lenny to something post-squeeze. Since no one had any idea where it come from to start with, and whenever this is related to upgrading or not, no one still have an idea what to do with it... :) /mjt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685360: AMD SB 750 + Logitech USB keyboard broken and system unbootable with Linux 3.2 (regression from 2.6.38)
Package: linux-image-3.2.0-0.bpo.2-amd64 Severity: serious Hi, I've experienced this regression from squeeze, so I'm noting it before I forget and wheezy's released... I have a desktop machine with a motherboard that has an AMD SB 750 south bridge with an integrated USB controller. With Linux 2.6.38, custom built, and pretty much all earlier versions, the Logitech K350 keyboard, plugged in through that little unifying receiver, works fine, as does the Logitech LX8 mouse, plugged in through its own, slightly larger receiver. When I boot the Debian kernel 3.2.x with an initrd, the machine freezes on boot before the initrd processing starts, strangely enough. I built my own copy of 3.2.27 with .config from 2.6.38 + make oldconfig, and it booted, but the keyboard simply didn't work. Googling brought up some similar problems, but nothing seems to be exactly the same: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1000255 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/991932 #658029 This half-hour investigation was all the time I had for this this weekend. I'll try to do more and attach more information here as soon as I get a chance. A git bisect would probably be quick enough, but I didn't have a checkout handy at the time. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678262: mdadm: fails to honour INITRDSTART='none' in /etc/default/mdadm
On 19.08.2012 16:39, Andreas Henriksson wrote: Hello! Talked the other day with mjt on irc about mdadm problems I was having that seems very much like this issue. We debugged it and mjt found some issues... He probably knows much more then what I'm about to write here... I filed a separate bugreport about this, #685161 . But now when I think of it more, it looks like all 3 the most important bugs against mdadm are due to the same root cause: missing raid levels in the mdadm.conf and initramfs script choking on the missing /proc/mdstat as the result. They are: #685161 mdadm initramfs script panics with modern mdadm being unable to load any modules #644389 suspect non-working mdadm.conf created during install #678262 mdadm: fails to honour INITRDSTART='none' in /etc/default/mdadm (This last one, even if titled differently, has the same bug as the root cause - we check for /proc/mdstat BEFORE checking for INITRDSTART=none). And it needs a bit more rewriting -- I'm preparing a modified initramfs hook+script pair to resolve this issue for good. [] (On a related note, the panic script function looks for a panic=X cmdline argument and tries to reboot after X seconds of showing the panic message instead of giving a rescue shell THIS IS BROKEN. The reboot command in initramfs does nothing! Everybody gets rescue shell access!) Yes, but this is initramfs-tools issue, not mdadm issue for sure :) /mjt -- 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#685360: AMD SB 750 + Logitech USB keyboard broken and system unbootable with Linux 3.2 (regression from 2.6.38)
Processing commands for cont...@bugs.debian.org: reassign 685360 src:linux 3.2.0-0.bpo.2 Bug #685360 [linux-image-3.2.0-0.bpo.2-amd64] AMD SB 750 + Logitech USB keyboard broken and system unbootable with Linux 3.2 (regression from 2.6.38) Warning: Unknown package 'linux-image-3.2.0-0.bpo.2-amd64' Bug reassigned from package 'linux-image-3.2.0-0.bpo.2-amd64' to 'src:linux'. Ignoring request to alter found versions of bug #685360 to the same values previously set Ignoring request to alter fixed versions of bug #685360 to the same values previously set Bug #685360 [src:linux] AMD SB 750 + Logitech USB keyboard broken and system unbootable with Linux 3.2 (regression from 2.6.38) The source 'linux' and version '3.2.0-0.bpo.2' do not appear to match any binary packages Marked as found in versions linux/3.2.0-0.bpo.2. thanks Stopping processing here. Please contact me if you need assistance. -- 685360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685360 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#685364: piwigo: CVE-2012-2208 CVE-2012-2209
Package: piwigo Severity: grave Tags: security Justification: user security hole Please see http://archives.neohapsis.com/archives/bugtraq/2012-04/0196.html Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685366: condor: CVE-2012-3416
Package: condor Severity: grave Tags: security Justification: user security hole Please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3416 for more information. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684708: mdadm: support external metadata arrays correctly
On 13.08.2012 14:10, Miquel van Smoorenburg wrote: Package: mdadm Version: 3.2.5-1 Severity: serious Tags: patch wheezy sid The initramfs hook supplied by mdadm doesn't install mdmon. Also, mdmon is not included in the .udeb for the installer. This means that if you have an array with external metadata (ddf or, more widely used, imsm - Intel Matrix Raid) that it will come up readonly. This causes the installer to hang or the system not being able to boot if root is on that array. The attached patch does a couple of things: - it makes sure mdadm is included in the initramfs and the udeb package - it adds a mdadm-waitidle script that runs just before reboot/halt. For all arrays that are still running, it sets safe_mode_delay to a low version, sets sync_action to idle, and waits for the array(s) to go idle. This is needed so that the array is clean, otherwise it will start to resync at the next boot. - it adds 2 lines of code to mdmon.c so that it symlinks its pidfile into /run/sendsigs.omit.d - mdmon should not be killed at shutdown, we still need it after the rootfs has been unmounted. There's one more thing missing in there: mdmon should be re-started from real root after switching from rootfs -- the takeover. I guess it needs to be added to mdadm-raid. BTW, why mdadm-waitidle is a separate script? Can't we fold it into mdadm-raid directly? The more I think about this all, the more it looks like it is too heavily change for wheezy. I understand the situation, but I still think it is not a good idea in general. Oh well. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684708: mdadm: support external metadata arrays correctly
On 20/08/12 10:42, Michael Tokarev wrote: On 13.08.2012 14:10, Miquel van Smoorenburg wrote: Package: mdadm Version: 3.2.5-1 Severity: serious Tags: patch wheezy sid The initramfs hook supplied by mdadm doesn't install mdmon. Also, mdmon is not included in the .udeb for the installer. This means that if you have an array with external metadata (ddf or, more widely used, imsm - Intel Matrix Raid) that it will come up readonly. This causes the installer to hang or the system not being able to boot if root is on that array. The attached patch does a couple of things: - it makes sure mdadm is included in the initramfs and the udeb package - it adds a mdadm-waitidle script that runs just before reboot/halt. For all arrays that are still running, it sets safe_mode_delay to a low version, sets sync_action to idle, and waits for the array(s) to go idle. This is needed so that the array is clean, otherwise it will start to resync at the next boot. - it adds 2 lines of code to mdmon.c so that it symlinks its pidfile into /run/sendsigs.omit.d - mdmon should not be killed at shutdown, we still need it after the rootfs has been unmounted. There's one more thing missing in there: mdmon should be re-started from real root after switching from rootfs -- the takeover. I guess it needs to be added to mdadm-raid. Why restarted... surely it just can carry-on as it was. Since e.g. /run doesn't change pre-/post- real-root. BTW, why mdadm-waitidle is a separate script? Can't we fold it into mdadm-raid directly? The more I think about this all, the more it looks like it is too heavily change for wheezy. I understand the situation, but I still think it is not a good idea in general. Oh well. -- Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684708: mdadm: support external metadata arrays correctly
On 20.08.2012 14:05, Dmitrijs Ledkovs wrote: On 20/08/12 10:42, Michael Tokarev wrote: [] There's one more thing missing in there: mdmon should be re-started from real root after switching from rootfs -- the takeover. I guess it needs to be added to mdadm-raid. Why restarted... surely it just can carry-on as it was. Since e.g. /run doesn't change pre-/post- real-root. Because it keeps the mdmon and supported libraries mapped from within rootfs -- neither of which can be freed after deleted by switch_root. Ie, this way we keep the initial rootfs (the one which comes from initramfs) dirty. --takeover/--offroot (does mdadm running from initramfs sets the latter?) is the way how it is designed to be used. /mjt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645999: marked as done (lbzip2: uses excessive amounts of memory when decompressing highly compressible data)
Your message dated Mon, 20 Aug 2012 10:17:37 + with message-id e1t3p3b-0001rs...@franck.debian.org and subject line Bug#645999: fixed in lbzip2 2.2-1 has caused the Debian Bug report #645999, regarding lbzip2: uses excessive amounts of memory when decompressing highly compressible data 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.) -- 645999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: lbzip2 Version: 0.23-1 Severity: important lbzip2 uses excessive amounts of memory (and is killed) when decompressing highly compressible data and the writer (aka: muxer) is slow. I recently tried to decompress some hard drive images, which have large sections of zero filled area, unfortunately due to runaway memory usage these files were uncompressable with lbzip2. What I think is happening, the splitter pulls some blocks of highly compressed input into ram, a worker gets one and enters scan mode, which causes it to very rapidly find and queue up many of the small compressed blocks for decompression. Nothing in the code directly throttles output block creation between decompressor and muxer, so if the muxer can't write out blocks quickly enough to keep up the process size explodes. The throttling between splitter and muxer does not help here because the just one splitter is around 16G of output, even if the splitter loads only one block I won't have enough ram to decompress into ram that single input block. The simple test case below, use 100G of compressed zeros. This file has a little more than 6 blocks of input from splitter's perspective. On a machine with 6G of ram and 4 processors, it takes about 10 seconds to be killed, at that time it had used 20G of virtual memory and 6G of resident memory. The kill is fast for me because I do not have swap enabled on this machine. If swap even a small (2G) swap was enabled the system will trash various things to disk for several minutes before the OOM-killer triggers... so if you are on linux and have swap enabled, I recommend monitoring top and hitting ^C on lbzip2 when you run the test case. The simple test case: === # generate input file for problem report dd if=/dev/zero bs=1024k count=$[1024*100] | ./lbzip2 -c9 zero.bz2 102400+0 records in 102400+0 records out 107374182400 bytes (107 GB) copied, 648.662 s, 166 MB/s # check size of file ls -l zero.bz2 -rw-r--r-- 1 user user 5726783 2011-10-20 04:44 zero.bz2 # reproduce problem, the kill -9 /usr/bin/time ./lbzip2 -cd zero.bz2 | sleep 30 Command terminated by signal 9 22.40user 5.72system 0:10.48elapsed 268%CPU (0avgtext+0avgdata 24060336maxresident)k 12312inputs+0outputs (11major+1508100minor)pagefaults 0swaps # confirm OOM kill in dmesg dmesg | grep lbzip2 | tail -2 [622439.076387] Out of memory: Kill process 10299 (lbzip2) score 739 or sacrifice child [622439.076391] Killed process 10299 (lbzip2) total-vm:20247368kB, anon-rss:6015048kB, file-rss:4kB === With this example input the muxer writing to /dev/null can't keep up with just two workers... this is killed: lbzip2 -cd -n 2 zero.bz2 /dev/null Even running in single worker mode is killed: lbzip2 -cd -n 1 zero.bz2 | sleep 60 -- System Information: Debian Release: squeeze/sid APT prefers natty-updates APT policy: (500, 'natty-updates'), (500, 'natty-security'), (500, 'natty') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-11-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lbzip2 depends on: ii libbz2-1.01.0.5-6ubuntu1 high-quality block-sorting file co ii libc6 2.13-0ubuntu13 Embedded GNU C Library: Shared lib lbzip2 recommends no packages. lbzip2 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: lbzip2 Source-Version: 2.2-1 We believe that the bug you reported is fixed in the latest version of lbzip2, which is due to be installed in the Debian FTP archive. 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 645...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mikolaj Izdebski zurg...@gmail.com (supplier of updated lbzip2 package) (This message was generated automatically at their request; if you believe that there is a problem with it
Bug#685376: postinst fails on non-default Debian kernels and is useless on =3.4
Package: makedev Version: 2.3.1-91 Severity: serious Hi, the debian/postinst of makedev currently contains the following code: # force update of fb devices if kernel is Linux = 2.4 and they already exist kern_rev1=`uname -r | sed -e 's@^\([^.]*\)\..*@\1@'` kern_rev2=`uname -r | sed -e 's@^[^.]*\.\([^.]*\)\..*@\1@'` if [ `uname -s` = Linux ] [ $kern_rev1 -ge 2 ] [ $kern_rev2 -ge 4 ] [ -e /dev/fb0 ] then MAKEDEV fb fi This fails boldly on my machine with linux-image-3.4-trunk-amd64 being installed as `uname -r` returns 3.4-trunk-amd64. And even if it would return 3.4.0, the condition is false for 3.x kernels before 3.4 (like the 3.2 in Wheezy) → serious because of that. A possible fix would be kern_rev2=`uname -r | sed -e 's@^[^.]*\.\([0-9]*\).*@\1@'` But then the if condition still has to be updated, as it won't trigger with [3.0..3.4[ Regards Evgeni -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.4-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684708: mdadm: support external metadata arrays correctly
On 20-08-12 11:42 AM, Michael Tokarev wrote: There's one more thing missing in there: mdmon should be re-started from real root after switching from rootfs -- the takeover. I guess it needs to be added to mdadm-raid. Is that really necessary? Can't we just leave it as-is, so the number of changes is minimized for now? On systems that don't have external metadata arrays (i.e. most of them) mdmon won't be running anyway. BTW, why mdadm-waitidle is a separate script? Can't we fold it into mdadm-raid directly? Well no, because it needs to run after all filesystems have been unmounted and root is read-only. Unless ofcourse you change mdadm-raid to run after root has been remounted read-only, but I do not know what consequences that change would have. The more I think about this all, the more it looks like it is too heavily change for wheezy. I understand the situation, but I still think it is not a good idea in general. Oh well. Well I still think this is more a bugfix than a new feature, since right now the functionality is there, it's just broken. Mike. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684817: lilypond: FTBFS: (process:29483): Pango-WARNING **: error opening config file '/root/.pangorc': Permission denied
On 18/08/12 at 21:49 -0700, Don Armstrong wrote: tag 684817 unreproducible retitle 684817 segfault in lilypond thanks On Tue, 14 Aug 2012, Lucas Nussbaum wrote: During a rebuild of all packages in *wheezy*, your package failed to build on amd64. I've rebuild this on wheezy on amd64. The actual error is a segfault in lilypond (or something which lilypond is calling) which I am unable to reproduce in a wheezy pbuilder chroot (nor have I seen this particular error before.) The pango warning is just a red herring; it happens all over the place and is a bug in pango. If you are able to reproduce this build failure, please send me a coredump and a backtrace so I have a chance of tracking down what is happening. If it doesn't reproduce, it should be downgraded, but I'd like to see a backtrace if you can possibly get one (and it doesn't look like stack smashing.) Hi, My build ran with DEB_BUILD_OPTIONS=parallel=10. Maybe the failure only occurs with parallel builds. Anyway, while I could reproduce the failure starting the build inside sbuild, I could not reproduce it in a normal chroot. Feel free to either close or downgrade (there's a reasonable path to building the package even if it fails inside sbuild = probably not RC). Lucas -- 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#685366: condor: CVE-2012-3416
Processing commands for cont...@bugs.debian.org: fixed 685366 condor/7.8.2~dfsg.1-1 Bug #685366 [condor] condor: CVE-2012-3416 The source condor and version 7.8.2~dfsg.1-1 do not appear to match any binary packages Marked as fixed in versions condor/7.8.2~dfsg.1-1. thanks Stopping processing here. Please contact me if you need assistance. -- 685366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685366 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#685366: marked as done (condor: CVE-2012-3416)
Your message dated Mon, 20 Aug 2012 13:48:26 +0200 with message-id 20120820114826.GA3160@meiner and subject line Re: Bug#685366: condor: CVE-2012-3416 has caused the Debian Bug report #685366, regarding condor: CVE-2012-3416 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.) -- 685366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: condor Severity: grave Tags: security Justification: user security hole Please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3416 for more information. Cheers, Moritz ---End Message--- ---BeginMessage--- fixed 685366 condor/7.8.2~dfsg.1-1 thanks On Mon, Aug 20, 2012 at 11:28:23AM +0200, Moritz Muehlenhoff wrote: Package: condor Severity: grave Tags: security Justification: user security hole Please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3416 for more information. This issue was fixed in the last upload to unstable. An unblock request has been send to allow migration into wheezy: http://bugs.debian.org/685070 Michael -- Michael Hanke http://mih.voxindeserto.de---End Message---
Bug#685386: x-tile requires python-gconf
Package: x-tile Version: 2.2.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? x-tile stopped working * What exactly did you do (or not do) that was effective (or ineffective)? * ran x-tile from the command line Output: :~$ x-tile Traceback (most recent call last): File /usr/bin/x-tile, line 30, in module import gtk, gconf ImportError: No module named gconf * did some googling * apt-get install python-gconf which was not listed as a required package * What was the outcome of this action? All is well * What outcome did you expect instead? A resolution achieved using synaptic. done. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages x-tile depends on: ii python 2.7.3~rc2-1 ii python2.6 2.6.8-0.2 ii python2.7 2.7.3~rc2-2.1 x-tile recommends no packages. x-tile suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685317: marked as done (ruby-merb-haml: missing dependency on ruby-haml)
Your message dated Mon, 20 Aug 2012 12:32:39 + with message-id e1t3r9r-0001vz...@franck.debian.org and subject line Bug#685317: fixed in ruby-merb-haml 1.1.3-2 has caused the Debian Bug report #685317, regarding ruby-merb-haml: missing dependency on ruby-haml 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.) -- 685317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ruby-merb-haml Version: 1.1.3-1 Severity: serious ruby-merb-haml imports haml and so needs to depend on it. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.4.0 (SMP w/4 CPU cores) Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ruby-merb-haml depends on: ii ruby 4.9 ii ruby1.8 [ruby-interpreter]1.8.7.358-4 ii ruby1.9.1 [ruby-interpreter] 1.9.3.194-1 ruby-merb-haml recommends no packages. ruby-merb-haml suggests no packages. -- no debconf information -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are ---End Message--- ---BeginMessage--- Source: ruby-merb-haml Source-Version: 1.1.3-2 We believe that the bug you reported is fixed in the latest version of ruby-merb-haml, which is due to be installed in the Debian FTP archive. 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 685...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tollef Fog Heen tfh...@debian.org (supplier of updated ruby-merb-haml 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, 19 Aug 2012 19:24:04 +0200 Source: ruby-merb-haml Binary: ruby-merb-haml libmerb-haml-ruby libmerb-haml-ruby1.8 Architecture: source all Version: 1.1.3-2 Distribution: unstable Urgency: low Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Tollef Fog Heen tfh...@debian.org Description: libmerb-haml-ruby - Transitional package for ruby-merb-haml libmerb-haml-ruby1.8 - Transitional package for ruby-merb-haml ruby-merb-haml - Plugin library for Merb that provides access to ruby-haml Closes: 685317 Changes: ruby-merb-haml (1.1.3-2) unstable; urgency=low . * Add missing depends on ruby-haml. Closes: #685317. Checksums-Sha1: 270dab0ed53735f398390d0b96af76196547ab9e 2221 ruby-merb-haml_1.1.3-2.dsc 43ec85d3a0de3d25f50876b7381855baf41ad367 3682 ruby-merb-haml_1.1.3-2.debian.tar.gz 3addea26683d3fa797cd07ce3b40faf96fe9e0ad 8160 ruby-merb-haml_1.1.3-2_all.deb 75354d5b195e1ac888395a73da0a107e2d95bd62 2492 libmerb-haml-ruby_1.1.3-2_all.deb 7d35af872eef31025de0f4d98cb5967f5e5a9dc0 2500 libmerb-haml-ruby1.8_1.1.3-2_all.deb Checksums-Sha256: 5ee1b00e5eb790db5b843715b68373c0f16b1ff181fdd0e774b145363d95010a 2221 ruby-merb-haml_1.1.3-2.dsc 69fcc64e291f533ebfd946490759cd6ca7249bdd6c55efb21bfa032ae6aec920 3682 ruby-merb-haml_1.1.3-2.debian.tar.gz ca1538d19eadcee64b98574d629eec452f4d0dfb55fe767f7cdc596a17545d92 8160 ruby-merb-haml_1.1.3-2_all.deb eea12eb812c161070a9af767157ace86db5412d0608c908ab5f6c53f7f3bfab6 2492 libmerb-haml-ruby_1.1.3-2_all.deb 92d4477b7ce0f6b3fda45ffa6a968769dda31e77ec4c5897cd8aa0b8a851616b 2500 libmerb-haml-ruby1.8_1.1.3-2_all.deb Files: a54b50b35e3c61c814dea3425c68069d 2221 ruby optional ruby-merb-haml_1.1.3-2.dsc c6cf02e648afe14c4d4f699e05ce8831 3682 ruby optional ruby-merb-haml_1.1.3-2.debian.tar.gz 84cea4a4857409feed774e67271ad64c 8160 ruby optional ruby-merb-haml_1.1.3-2_all.deb 2ea93f175c5b16d14ab9c89b0f54d8ab 2492 oldlibs extra libmerb-haml-ruby_1.1.3-2_all.deb 78f52f611ee2d5879e1e81c14f43125b 2500 oldlibs extra libmerb-haml-ruby1.8_1.1.3-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJQMSPZAAoJELZaSHHKGdcXXwMQAMWly7iOZObiIL2Zj4pQr/XS gkmPww8PoCE2kMHgM7PLHUZapv0ykuM04h5AhXu/sLI/1sbtm3GGTs+e+Br7q81J gTcHI2eC+9iw4oTHN/2fMQVPRz456F/Q4MnDSGTs82Zq7ArGcNGIj23QbUpl0Xf3 6K64ooV8JQLjqMxLU/xnpnt0xF4fA7U+azb/mvAD5aeTKvrfVpXZ+u/G+v+lLu19
Bug#674089: Possible release note for systems running PHP through CGI.
Hi all, [multiple messages from d-d and d-r merged together] I am also concerned that a *simple* solution to restore the old behaviour in a secure way is not provided: maybe php5-cgi should install a sensible default configuration in /etc/apache2/conf.d/ ? I have prepared new update for PHP based on comments from d-d. The commit is here: http://anonscm.debian.org/gitweb/?p=pkg-php/php.git;a=commit;h=72eef08994f65b227103509617652d7c0bf0587a To sum the changes: - create dummy php5_cgi module, which has the required configuration inside - enable this module if upgrading from anything older than 5.4.4-5 - the module is not enabled on fresh installs (user has to enable it manually) - update NEWS.Debian to: php5 (5.4.4-5) unstable; urgency=low Please be aware that the mime-types package dropped non-standard definitions for PHP that might affect any systems using PHP 5 running as CGI or FastCGI. Following definitions were dropped: application/x-httpd-phpphtml pht php application/x-httpd-php-source phps application/x-httpd-php3 php3 application/x-httpd-php3-preprocessed php3p application/x-httpd-php4 php4 application/x-httpd-php5 php5 The php5-cgi package mitigates any known issues by creating a (dummy) apache2 module php5_cgi with a configuration containing handlers for all previously defined extensions. Even though we believe that this configuration should keep your PHP scripts interpreted, it might be a good idea to check your apache2 site-wide configuration and also any specific PHP configuration for websites running on your system. As far as we know definitions from the mime-types packages are not used in any other webserver included in Debian, but it might affect any application which relies on system MIME types to interpret PHP files. -- Ondřej Surý ond...@debian.org Wed, 15 Aug 2012 10:31:31 +0200 - Update the README.Debian to match current state. I will upload this change as part of 5.4.6-1 upload to Debian experimental and if everything is ok, I'll merge it back to 5.4.4-5 targeted to unstable-testing. As far as the mime-support package is concerned, I think that we reached the consensus that we will not add the entries back, and that the consequences will be documented in the php5-cgi package's NEWS file and in the release notes. I agree on that, even though I think that PHP should have it's own mimetype definition (same as python or perl, e.g. application/x-php, but let's keep this discussion out of this issue, since it's something different). I guess we could consider that for a very specific, low-popcon package. But knowingly interrupting upgrades for a well-known problem, on a very high number of systems? I'm not sure that's appropriate. Quite the opposite, actually. I believe that update that I just did should solve any backwards compatibility issues. (Crossed fingers... have to do thourough testing first, I tend to make mistakes from time to time.) Many of the users of php5-cgi will be doing so because they are using other web servers. The discussion in #674089 seems to mainly revolve around Apache. How does this affect other web servers? I am not aware of any other (Debian shipped) web server which uses system-wide mime-types. At least both nginx and lighttpd don't depend on system mime types for interpreting PHP files (both use extension based definitions). - In Squeeze, using default configurations, files with .php in their name such as foo.php.jpeg are executed as PHP scripts by the Apache web servers runing PHP scripts through php5-cgi. Charles, did you test that or you base that claim on Christoph's mails? I have just tested both php5-cgi in standard configuration as recommended in README.Debian and this claim doesn't seem to be true: $ wget -q -O - http://localhost:8080/index.php bar $ wget -q -O - http://localhost:8080/index.php.jpeg ?php echo 'foo'; ? Also Apache2 documentation is very clear on that issue: See http://httpd.apache.org/docs/2.2/mod/mod_mime.html#multipleext If more than one extension is given that maps onto the same type of meta-information, then the one to the right will be used, except for languages and content encodings. For example, if .gif maps to the MIME-type image/gif and .html maps to the MIME-type text/html, then the file welcome.gif.html will be associated with the MIME-type text/html. However there could be a problem when you use MIME-type and handler together (which we *don't* use): Care should be taken when a file with multiple extensions gets associated with both a MIME-type and a handler. This will usually result in the request being handled by the module associated with the handler. Maybe that's because it's expected they would be PHP scripts emitting JPEG files, not plain JPEG files? This seems like a feature to me, not a bug. Why was
Bug#685397: gimp: CVE-2012-3403
Package: gimp Severity: grave Tags: security Justification: user security hole Please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3403 for details and patches. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685398: squidclamav: CVE-2012-3501
Package: squidclamav Severity: grave Tags: security Justification: user security hole Please see http://seclists.org/oss-sec/2012/q3/235 for more information and a link to the upstream commit. Remember we're in freeze, so an isolated fix should be applied instead of updating to a new upstream release. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685397: gimp: CVE-2012-3403
On Mon, Aug 20, 2012 at 03:04:13PM +0200, Moritz Muehlenhoff wrote: Package: gimp Severity: grave Tags: security Justification: user security hole Please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3403 for details and patches. And another issue: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3481 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683284: marked as done (CVE-2012-3438)
Your message dated Mon, 20 Aug 2012 13:32:43 + with message-id e1t3s5z-0001ac...@franck.debian.org and subject line Bug#683284: fixed in graphicsmagick 1.3.16-1.1 has caused the Debian Bug report #683284, regarding CVE-2012-3438 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.) -- 683284: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: graphicsmagick Severity: grave Tags: security Please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3438 for details. Please fix this for Wheezy with an isolated fix instead of updating to a new upstream release (since the freeze is in effect) This doesn't warrant a DSA, but can be fixed through a stable point update for Squeeze (adding Jonathan to CC, who's managing this) Cheers, Moritz ---End Message--- ---BeginMessage--- Source: graphicsmagick Source-Version: 1.3.16-1.1 We believe that the bug you reported is fixed in the latest version of graphicsmagick, which is due to be installed in the Debian FTP archive. 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 683...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated graphicsmagick package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 18 Aug 2012 15:08:57 +0200 Source: graphicsmagick Binary: graphicsmagick libgraphicsmagick3 libgraphicsmagick1-dev libgraphicsmagick++3 libgraphicsmagick++1-dev libgraphics-magick-perl graphicsmagick-imagemagick-compat graphicsmagick-libmagick-dev-compat graphicsmagick-dbg Architecture: source amd64 all Version: 1.3.16-1.1 Distribution: unstable Urgency: low Maintainer: Daniel Kobras kob...@debian.org Changed-By: gregor herrmann gre...@debian.org Description: graphicsmagick - collection of image processing tools graphicsmagick-dbg - format-independent image processing - debugging symbols graphicsmagick-imagemagick-compat - image processing tools providing ImageMagick interface graphicsmagick-libmagick-dev-compat - image processing libraries providing ImageMagick interface libgraphics-magick-perl - format-independent image processing - perl interface libgraphicsmagick++1-dev - format-independent image processing - C++ development files libgraphicsmagick++3 - format-independent image processing - C++ shared library libgraphicsmagick1-dev - format-independent image processing - C development files libgraphicsmagick3 - format-independent image processing - C shared library Closes: 683284 Changes: graphicsmagick (1.3.16-1.1) unstable; urgency=low . * Non-maintainer upload. * [SECURITY] Fix CVE-2012-3438: apply patch from upstream repo: http://graphicsmagick.hg.sourceforge.net/hgweb/graphicsmagick/graphicsmagick/rev/d6e469d02cd2 coders/png.c: Some typecasts were inconsistent with libpng-1.4 and later. (Closes: #683284) Checksums-Sha1: b9e2178a3e08032b171a20f9d3f3a4b069aaf5a3 2631 graphicsmagick_1.3.16-1.1.dsc 224322db69e3c2ea7ff75e87cdd546e8d1878418 159080 graphicsmagick_1.3.16-1.1.diff.gz 58f06875141cc9108be344a14b3166766891b81e 1029270 graphicsmagick_1.3.16-1.1_amd64.deb f09702a6ea974da8c76b3126768c36e93a08a0f9 1319926 libgraphicsmagick3_1.3.16-1.1_amd64.deb 4b2ab72edd7e6006b5379a17698f136aae439087 1815114 libgraphicsmagick1-dev_1.3.16-1.1_amd64.deb c17694a8e7f292b755fd4506166939281d428730 152838 libgraphicsmagick++3_1.3.16-1.1_amd64.deb 4b7e222016ad1e125774b258d6aae7cbac05dce9 404920 libgraphicsmagick++1-dev_1.3.16-1.1_amd64.deb 17bb8a4429f2dcebff533d3185de8931a3e3e272 81778 libgraphics-magick-perl_1.3.16-1.1_amd64.deb d6c59a308c21b200e1863f51cd6c3521379c5b69 3259936 graphicsmagick-dbg_1.3.16-1.1_amd64.deb d8864b1bcdb593e868e95c709712180c71612078 15934 graphicsmagick-imagemagick-compat_1.3.16-1.1_all.deb 0fc07df33fdf62429550d48b4ba0860e35fc6a80 19526 graphicsmagick-libmagick-dev-compat_1.3.16-1.1_all.deb Checksums-Sha256: cfe2f45f3728c1c7902385e3c2ce8bf3dd65bd6a458865bad9b80e7d8025fc8d 2631 graphicsmagick_1.3.16-1.1.dsc 0103133d738608d087724f5c8bf8f04638f9a46be0741d185dc26463d0d2b1f8 159080 graphicsmagick_1.3.16-1.1.diff.gz
Bug#674089: Possible release note for systems running PHP through CGI.
Le Mon, Aug 20, 2012 at 02:57:10PM +0200, Ondřej Surý a écrit : I have prepared new update for PHP based on comments from d-d. The commit is here: http://anonscm.debian.org/gitweb/?p=pkg-php/php.git;a=commit;h=72eef08994f65b227103509617652d7c0bf0587a Hi Ondřej, many thanks for this work. Charles, did you test that or you base that claim on Christoph's mails? I have just tested both php5-cgi in standard configuration as recommended in README.Debian and this claim doesn't seem to be true: $ wget -q -O - http://localhost:8080/index.php bar $ wget -q -O - http://localhost:8080/index.php.jpeg ?php echo 'foo'; ? I did not test, and was trusting from http://bugs.debian.org/589384, which requested the removal of the PHP media types for Wheezy, that the problem was still present in some configurations. Good to see that we are heading towards a solution anyway. What shall I do with #674089 ? I can reassign it to php5-cgi so that your next upload closes it, or do we still need release notes ? Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#570516: md UUID changed
On Sun, Aug 19, 2012 at 07:13:33PM +0200, Ivo De Decker wrote: Hi, On Mon, Feb 21, 2011 at 11:59:25AM +, Steve McIntyre wrote: The hostname didn’t change. However the latter might be possible, I don’t really know. The MD array was built from lenny’s d-i. I've just started to upgrade my main fileserver at home from Lenny to Squeeze, and I think I've been bitten by this bug (or something very similar) in a big way. I've started off with a system running a locally-built 2.6.28 kernel and a number of RAID devices, all configured with version 0.9 superblocks (the default in Lenny, AFAICT). It seems both the reports for this bug are for upgrades from lenny to squeeze. Is this bug still relevant for wheezy? Does this problem still happen? If the problem is related to an upgrade from lenny, the bug should be marked as fixed in mdadm 3.2.2-1, as we don't support upgrades from lenny to something post-squeeze. As Michael says, we have no idea what causes the bug. Please don't close it just because it's old. -- Steve McIntyre, Cambridge, UK.st...@einval.com Managing a volunteer open source project is a lot like herding kittens, except the kittens randomly appear and disappear because they have day jobs. -- Matt Mackall -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674089: Possible release note for systems running PHP through CGI.
On Mon, Aug 20, 2012 at 3:35 PM, Charles Plessy ple...@debian.org wrote: Charles, did you test that or you base that claim on Christoph's mails? I have just tested both php5-cgi in standard configuration as recommended in README.Debian and this claim doesn't seem to be true: $ wget -q -O - http://localhost:8080/index.php bar $ wget -q -O - http://localhost:8080/index.php.jpeg ?php echo 'foo'; ? I did not test, and was trusting from http://bugs.debian.org/589384, which requested the removal of the PHP media types for Wheezy, that the problem was still present in some configurations. Ah, I see; it gets executed when there is no know handler or mime-type for second extension. E.g. index.php.jpeg works as expected (e.g. returning PHP source code), index.php.blubb but gets executed. I don't think there's any harm in disabling php.foobar and php.blubb files. Good to see that we are heading towards a solution anyway. What shall I do with #674089 ? I can reassign it to php5-cgi so that your next upload closes it, or do we still need release notes ? I think we still might need release notes, but it needs to be updated based on final impact of changes we have done. I am not sure if the information about filename.php.unknown-mime-type is worth release notes or just NEWS file in PHP. My guess would be latter, but opinions may vary. Also I am not happy that we make these changes so late in release cycle, but I guess we now have to find a way how to cope with them and still make release team happy. I think the changes I have done are least intrusive, but again opinions may vary. O. -- Ondřej Surý ond...@sury.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#147832: catching fclose errors.
tags 147832 + patch
bye
Hi,
I offer the attached patch to fix this bug. It uses a temporary file
and overwrite the servlist_.conf file only if fclose returns without
errors.
I've intentionally ignored the file permissions issue mentioned above.
HTH
--
Walter Franzini
http://aegis.stepbuild.org/
Index: xchat-2.8.8/src/common/servlist.c
===
--- xchat-2.8.8.orig/src/common/servlist.c 2012-08-20 15:34:54.0 +0200
+++ xchat-2.8.8/src/common/servlist.c 2012-08-20 15:59:53.607555834 +0200
@@ -1077,17 +1077,24 @@
ircserver *serv;
GSList *list;
GSList *hlist;
+ char *servlist = servlist_.conf;
+ char *new_servlist;
+
#ifndef WIN32
int first = FALSE;
- snprintf (buf, sizeof (buf), %s/servlist_.conf, get_xdir_fs ());
+ snprintf (buf, sizeof (buf), %s/servlist_.conf.new, get_xdir_fs ());
if (access (buf, F_OK) != 0)
first = TRUE;
#endif
- fp = xchat_fopen_file (servlist_.conf, w, 0);
+ new_servlist = malloc (strlen(servlist) + 5);
+ strcpy (new_servlist, servlist);
+ strcat (new_servlist, .new);
+
+ fp = xchat_fopen_file (new_servlist, w, 0);
if (!fp)
- return FALSE;
+ goto failure;
#ifndef WIN32
if (first)
@@ -1140,17 +1147,25 @@
hlist = hlist-next;
}
- if (fprintf (fp, \n) 1)
- {
- fclose (fp);
- return FALSE;
- }
+ fprintf (fp, \n);
list = list-next;
}
- fclose (fp);
- return TRUE;
+ if (0 == fclose (fp))
+ {
+#ifdef WIN32
+ unlink (servlist); /* win32 can't rename to an existing file */
+#endif
+ xchat_rename_file (new_servlist, servlist, 0);
+
+ free (new_servlist);
+ return TRUE;
+ }
+
+failure:
+ free(new_servlist);
+ return FALSE;
}
static void
Processed (with 5 errors): catching fclose errors.
Processing commands for cont...@bugs.debian.org: tags 147832 + patch Bug #147832 [xchat] xchat: loses server list if disk fills up Bug #527638 [xchat] xchat: server list file ~/.xchat2/servlist_.conf written non-atomically Bug #605003 [xchat] loss of data Added tag(s) patch. Added tag(s) patch. Added tag(s) patch. bye Hi, I offer the attached patch to fix this bug. It uses a temporary file and overwrite the servlist_.conf file only if fclose returns without errors. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 147832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=147832 527638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527638 605003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605003 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#683839: modemmanager fiddles with ttyUSB devices without asking first
On 04.08.2012 19:52, Ian Jackson wrote: I have been having trouble getting our reprap (open hardware 3D printer) connecting reliably. Sometimes the host control softare gets EBUSY and at other times it appears to suffer protocol violations during startup. The reprap shows up as a ttyUSB emulated serial device. Please attach the output of udevadm info --attribute-walk --name=/dev/ttyUSB0 This should include the VID/PID and driver name which should be enough to blacklist this particular device. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: severity of 683839 is important
Processing commands for cont...@bugs.debian.org: severity 683839 important Bug #683839 [modemmanager] modemmanager fiddles with ttyUSB devices without asking first Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 683839: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683839 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#672959: kfreebsd-*: panic: vm_fault_copy_wired
Something that popped into mind: Has the exact sysvinit version where this issue crept in been positively identified? While the bug report was filed against version 2.88dsf-22.1, I'm wondering if that was the exact sysvinit version where fsck.ufs started crashing the boot process in such a systematic way. Could someone from the debian-bsd list check this using earlier binaries from ( http://snapshot.debian.org/package/sysvinit/ ) and report whether any of them magically fixes the issue? If this is the case, it would allow us to backtrack the source of the bug. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682138: libsuil-0-0: Where are the Qt and Gtk modules?
suil package is still broken for gtk2 on qt4 UIs, because suil expect gtk2 dev libs to be preset on the system. please add this to debian/rules configure: --gtk2-lib-name=libgtk-x11-2.0.so.0 so that suil works for someone without libgtk2.0-dev installed. thanks
Bug#682146: marked as done (nuitka: broken if g++ is not installed: TypeError: argument of type 'NoneType' is not iterable)
Your message dated Mon, 20 Aug 2012 14:48:19 + with message-id e1t3th9-00062u...@franck.debian.org and subject line Bug#682146: fixed in nuitka 0.3.24+ds-1 has caused the Debian Bug report #682146, regarding nuitka: broken if g++ is not installed: TypeError: argument of type 'NoneType' is not iterable 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.) -- 682146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682146 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nuitka Version: 0.3.23.1+ds-1 Severity: serious If g++ is not installed, nuitka doesn't work at all: $ echo 42 test.py $ nuitka test.py TypeError: argument of type 'NoneType' is not iterable: File /usr/share/nuitka/nuitka/build/SingleExe.scons, line 191: if clang in env[ CXX ]: Setting the CXX environment variable doesn't help much: $ CXX=g++-4.6 nuitka test.py KeyError: 'CXXVERSION': File /usr/share/nuitka/nuitka/build/SingleExe.scons, line 216: gpp_version = int( env[ CXXVERSION ].replace( ., ) ) File /usr/lib/scons/SCons/Environment.py, line 409: return self._dict[key] Installing g++ does fix the problem, but this package is neither depended on nor recommended by nuitka. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages nuitka depends on: ii g++-4.6 4.6.3-8 ii python 2.7.3-1 ii python-dev 2.7.3-1 ii scons 2.1.0-1 Versions of packages nuitka recommends: pn python-lxml none pn python-qt4 none -- Jakub Wilk ---End Message--- ---BeginMessage--- Source: nuitka Source-Version: 0.3.24+ds-1 We believe that the bug you reported is fixed in the latest version of nuitka, which is due to be installed in the Debian FTP archive. 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 682...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kay Hayen kayha...@gmx.de (supplier of updated nuitka 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, 18 Aug 2012 21:19:17 +0200 Source: nuitka Binary: nuitka Architecture: source all Version: 0.3.24+ds-1 Distribution: unstable Urgency: low Maintainer: Kay Hayen kayha...@gmx.de Changed-By: Kay Hayen kayha...@gmx.de Description: nuitka - Python compiler with full language support and CPython compatibil Closes: 682145 682146 683090 Changes: nuitka (0.3.24+ds-1) unstable; urgency=low . * New upstream pre-release. * Detect the absence of g++ and gracefully fallback to the compiler depended on. (Closes: #682146) * Changed usage of temp files in developer scripts to be secure. (Closes: #682145) * Added support for DEB_BUILD_OPTIONS=nocheck to skip the test runs. (Closes: #683090) Checksums-Sha1: e5a22b015258ed9fb66124d1dbcac6c1254959a0 1432 nuitka_0.3.24+ds-1.dsc 0a929f5b44d9be38ca331f0aa9fcafc31e2e3169 331482 nuitka_0.3.24+ds.orig.tar.gz 0e29d35f57c7c62fe1cc66d37ad80774ff4190ee 6225 nuitka_0.3.24+ds-1.debian.tar.gz bea26593f1ca861e597b1ca56c201bddba7a83ed 343174 nuitka_0.3.24+ds-1_all.deb Checksums-Sha256: 2b6722d480617646752543426f7e2e32370245e9a6f1f391332a1b4e63fada0e 1432 nuitka_0.3.24+ds-1.dsc 0bfc049b162b97eac0ba0554d67cf1f8c075da49f3fa705679617338491478fd 331482 nuitka_0.3.24+ds.orig.tar.gz 24df494eb337aceca641ea5becc979021cdd1a3dcf46d1bda2d143c9834025d0 6225 nuitka_0.3.24+ds-1.debian.tar.gz fd2d23af251fef53970263de57bdbdb9d45c83dedb6bbd497168f39ad245d498 343174 nuitka_0.3.24+ds-1_all.deb Files: ef87f7ddbf39b1be33d597431ab82ff1 1432 python optional nuitka_0.3.24+ds-1.dsc 0e376fcacb55c939f43ad1df06f280b3 331482 python optional nuitka_0.3.24+ds.orig.tar.gz 56180c5c898bea74432598308eefbe6b 6225 python optional nuitka_0.3.24+ds-1.debian.tar.gz c5f38809316b4915b047a01aa122c2ab 343174 python optional nuitka_0.3.24+ds-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlAySskACgkQjRFFY3XAJMhtBACglYdyyFUeyebWyo+Ra0MBJcn7 vSQAn0SPdFE3UdAi0F4wZj6akyR8n1jI =q/ov -END PGP SIGNATUREEnd
Bug#679840: marked as done (iptables-persistent: fails to install in chroot - modprobe fails)
Your message dated Mon, 20 Aug 2012 14:48:11 +
with message-id e1t3th1-00060q...@franck.debian.org
and subject line Bug#679840: fixed in iptables-persistent 0.5.6
has caused the Debian Bug report #679840,
regarding iptables-persistent: fails to install in chroot - modprobe 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.)
--
679840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: iptables-persistent
Version: 0.5.5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
modprobe is now available, new problems show up:
During a test with piuparts I noticed your package failed to install in
a chroot. As per definition of the release team this makes the package
too buggy for a release, thus the severity.
In a chroot there is no kernel installed, so no modules can be loaded.
Even if a kernel were installed, it may not match $(uname -r).
Maybe the ischroot command in debianutils could be helpful.
From the attached log (scroll to the bottom...):
Selecting previously unselected package iptables-persistent.
(Reading database ... 7029 files and directories currently installed.)
Unpacking iptables-persistent (from .../iptables-persistent_0.5.5_all.deb) ...
update-rc.d: using dependency based boot sequencing
Setting up iptables-persistent (0.5.5) ...
dpkg: error processing iptables-persistent (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
iptables-persistent
Since that was not too helpful, I added a set -x and ran
dpkg --configure --pending:
[...]
+ db_get iptables-persistent/autosave_v4
+ _db_cmd 'GET iptables-persistent/autosave_v4'
+ _db_internal_IFS='
'
+ IFS=' '
+ printf '%s\n' 'GET iptables-persistent/autosave_v4'
+ IFS='
'
+ IFS='
'
+ read -r _db_internal_line
+ RET=true
+ case ${_db_internal_line%%[ ]*} in
+ return 0
+ '[' xtrue = xtrue ']'
+ modprobe -q iptable_filter
dpkg: error processing iptables-persistent (--configure):
subprocess installed post-installation script returned error exit status 1
and lets increate the verboseness of the failing command, too:
(chroot)# modprobe -vvv iptable_filter
libkmod: DEBUG ../libkmod/libkmod-module.c:519 kmod_module_new_from_lookup:
input alias=iptable_filter, normalized=iptable_filter
libkmod: DEBUG ../libkmod/libkmod-module.c:525 kmod_module_new_from_lookup:
lookup modules.dep iptable_filter
libkmod: DEBUG ../libkmod/libkmod.c:550 kmod_search_moddep:
file=/lib/modules/3.2.0-2-amd64/modules.dep.bin modname=iptable_filter
libkmod: DEBUG ../libkmod/libkmod.c:554 kmod_search_moddep: could not open
moddep file '/lib/modules/3.2.0-2-amd64/modules.dep.bin'
libkmod: DEBUG ../libkmod/libkmod-module.c:529 kmod_module_new_from_lookup:
lookup modules.symbols iptable_filter
libkmod: DEBUG ../libkmod/libkmod-module.c:533 kmod_module_new_from_lookup:
lookup install and remove commands iptable_filter
libkmod: DEBUG ../libkmod/libkmod-module.c:537 kmod_module_new_from_lookup:
lookup modules.aliases iptable_filter
libkmod: DEBUG ../libkmod/libkmod.c:431 kmod_lookup_alias_from_alias_bin:
file=/lib/modules/3.2.0-2-amd64/modules.alias.bin name=iptable_filter
libkmod: DEBUG ../libkmod/libkmod-module.c:549 kmod_module_new_from_lookup:
Failed to lookup iptable_filter
libkmod: INFO ../libkmod/libkmod.c:319 kmod_unref: context 0x7fbeb1792290
released
cheers,
Andreas
iptables-persistent_0.5.5.log.gz
Description: GNU Zip compressed data
---End Message---
---BeginMessage---
Source: iptables-persistent
Source-Version: 0.5.6
We believe that the bug you reported is fixed in the latest version of
iptables-persistent, which is due to be installed in the Debian FTP archive.
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 679...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Rütten andreasruet...@gmx.de (supplier of updated iptables-persistent
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: Thu, 02 Aug 2012 22:50:05 +0200
Source: iptables-persistent
Binary: iptables-persistent
Architecture: source all
Version: 0.5.6
Bug#685386: marked as done (x-tile requires python-gconf)
Your message dated Mon, 20 Aug 2012 14:48:24 +
with message-id e1t3the-00063b...@franck.debian.org
and subject line Bug#685386: fixed in x-tile 2.2.1-2
has caused the Debian Bug report #685386,
regarding x-tile requires python-gconf
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.)
--
685386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: x-tile
Version: 2.2.1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
x-tile stopped working
* What exactly did you do (or not do) that was effective (or
ineffective)?
* ran x-tile from the command line
Output:
:~$ x-tile
Traceback (most recent call last):
File /usr/bin/x-tile, line 30, in module
import gtk, gconf
ImportError: No module named gconf
* did some googling
* apt-get install python-gconf
which was not listed as a required package
* What was the outcome of this action?
All is well
* What outcome did you expect instead?
A resolution achieved using synaptic. done.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages x-tile depends on:
ii python 2.7.3~rc2-1
ii python2.6 2.6.8-0.2
ii python2.7 2.7.3~rc2-2.1
x-tile recommends no packages.
x-tile suggests no packages.
-- no debconf information
---End Message---
---BeginMessage---
Source: x-tile
Source-Version: 2.2.1-2
We believe that the bug you reported is fixed in the latest version of
x-tile, which is due to be installed in the Debian FTP archive.
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 685...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ricardo Mones mo...@debian.org (supplier of updated x-tile 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, 20 Aug 2012 15:47:42 +0200
Source: x-tile
Binary: x-tile
Architecture: source all
Version: 2.2.1-2
Distribution: unstable
Urgency: low
Maintainer: Ricardo Mones mo...@debian.org
Changed-By: Ricardo Mones mo...@debian.org
Description:
x-tile - tile selected windows in different ways
Closes: 685386
Changes:
x-tile (2.2.1-2) unstable; urgency=low
.
* debian/control
- Fix binary dependencies: add python-gconf, python-gtk2 and remove
unused ${shlibs:Depends} (Closes: #685386)
- Add Vcs headers pointing to git.debian.org
Checksums-Sha1:
9345fe1cf11e9253f5e4ac46de1ebfc935aaa48b 1197 x-tile_2.2.1-2.dsc
610f31661655e90ecc1523bc1492312baccf4493 2800 x-tile_2.2.1-2.debian.tar.gz
ae108d0e6d4961cf53204f4beac05d5f956f74c8 133030 x-tile_2.2.1-2_all.deb
Checksums-Sha256:
99b5410bc11efad5ee8689df8279c4ab3b3bf6babd4ccfff52f725c31c9185bf 1197
x-tile_2.2.1-2.dsc
391b2f256357db6ac81e62d4f8384b0a8ca5ba98a0f83b00db733774d4b58822 2800
x-tile_2.2.1-2.debian.tar.gz
e9b5af9473ad014a263f8c270dd0a7ca6d83b539352e9ede076a626c29051e31 133030
x-tile_2.2.1-2_all.deb
Files:
2b79825a3b29e3276adff07a15b10e42 1197 x11 optional x-tile_2.2.1-2.dsc
6bfeb38ab5cde291fa12496db518b4bb 2800 x11 optional x-tile_2.2.1-2.debian.tar.gz
6b185bc913e91cd7c85ec4620a98623b 133030 x11 optional x-tile_2.2.1-2_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAlAyR6wACgkQLARVQsm1XayF0ACeL2TUQDgu+ScMXlhSClRMYqu2
0bUAoJ7XKEtRpXTFdHwx9D0BnDImxj8a
=MdQP
-END PGP SIGNATUREEnd Message---
Processed: severity of 684817 is important
Processing commands for cont...@bugs.debian.org: severity 684817 important Bug #684817 [src:lilypond] segfault in lilypond Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 684817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684817 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#672959: kfreebsd-*: panic: vm_fault_copy_wired
Hi, Martin-Éric Racine wrote: Something that popped into mind: Has the exact sysvinit version where this issue crept in been positively identified? AFAIK not yet, because nobody tried. While the bug report was filed against version 2.88dsf-22.1, I'm wondering if that was the exact sysvinit version where fsck.ufs started crashing the boot process in such a systematic way. Could someone from the debian-bsd list check this using earlier binaries from ( http://snapshot.debian.org/package/sysvinit/ ) and report whether any of them magically fixes the issue? If this is the case, it would allow us to backtrack the source of the bug. Will do! Thanks for the hint! 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#685353: qemu-kvm: kvm process hangs with 100% CPU usage
* Mike Gerber schrieb: * Michael Tokarev schrieb: On 20.08.2012 10:01, Mike Gerber wrote: I currently run 3 VMs using libvirt/qemu-kvm. Two of them are mostly idle and stable, but the third one locks up within 1 or 2 days. This third VM uses an emulated ES1370 sound card (host has an ASUS Xonar DX sound card), to stream host audio input to an icecast server using darkice. Does this also happen without ES1370 device? Do other guests use this device too? How active the audio/sound usage is? It is vital to understand where the problem is as close as possible, since it isn't easy to reproduce the problem, and you apparently pointed out one difference (ES1370) which might be the root of the issue, but might be not. The VM would be useless without the ES1370, as I am using it to stream audio to an icecast server on the same VM (see above.) I *could* test without the sound device but I doubt that would be useful. On the other hand, the other VMs don't have any load yet (still a test setup.) Audio usage is almost full time (stream is on about 50% of the time), for two MP3 encoded streams (one high, one low quality.) Also, this guest is the only one using audio, the others don't even have the emulated ES1370 configured. Cheers, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#662130: Upstream bug assigned
An upstream bug has been filled, and assigned. http://piwigo.org/bugs/view.php?id=2663 They plan to replace JSmin with JavaScriptPacker It looks like they're shooting for 2.5.0beta1 to have the fix in place. John Taggart -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685353: qemu-kvm: kvm process hangs with 100% CPU usage
Hi Michael, * Michael Tokarev schrieb: On 20.08.2012 10:01, Mike Gerber wrote: I currently run 3 VMs using libvirt/qemu-kvm. Two of them are mostly idle and stable, but the third one locks up within 1 or 2 days. This third VM uses an emulated ES1370 sound card (host has an ASUS Xonar DX sound card), to stream host audio input to an icecast server using darkice. Does this also happen without ES1370 device? Do other guests use this device too? How active the audio/sound usage is? It is vital to understand where the problem is as close as possible, since it isn't easy to reproduce the problem, and you apparently pointed out one difference (ES1370) which might be the root of the issue, but might be not. The VM would be useless without the ES1370, as I am using it to stream audio to an icecast server on the same VM (see above.) I *could* test without the sound device but I doubt that would be useful. On the other hand, the other VMs don't have any load yet (still a test setup.) Audio usage is almost full time (stream is on about 50% of the time), for two MP3 encoded streams (one high, one low quality.) (gdb) attach 3259 Attaching to process 3259 Reading symbols from /usr/bin/kvm...Reading symbols from /usr/lib/debug/usr/bin/kvm...done. Unable to read JIT descriptor from remote memory! (gdb) info threads Id Target Id Frame· * 1process 3259 kvm 0x7f32ebb20f7b in ?? () (gdb) thread apply all bt full Thread 1 (process 3259): #0 0x7f32ebb20f7b in ?? () No symbol table info available. You can try installing qemu-kvm-gdb to get symbol table. That might be useful. If that wont help, it'll mean we have a bug in qemu-kvm package at providing debugging info. It's already installed (Reading symbols from /usr/lib/debug/usr/bin/kvm...done.), so that might be a bug with the debugging info - or with my use of gdb. No useful strace output either: # strace -ff -p3259 Process 3259 attached with 2 threads - interrupt to quit [pid 3270] futex(0x7f32ec94ea80, FUTEX_WAIT_PRIVATE, 2, NULL^C unfinished ... Process 3259 detached Process 3270 detached Hmm. And that's all? In that case it'd be very nice really to have a backtrace. Yep, that's all. I left it running for about a minute and that is all output, until I hit ^C. kvm command line (run by libvirt): 105 3259 61.3 27.2 1540272 1071712 ? RLl Aug18 1331:39 /usr/bin/kvm -S -M pc-1.1 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name mp3 -uuid 25d2b76c-9533-c55a-b5e2-07da213886f1 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/mp3.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/vg_vms/lv_mp3,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-di -netdev tap,fd=20,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:b1:e7:80,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:2 -vga cirrus -device ES1370,id=sound0,bus=pci.0,addr=0x6 -device i6300esb,id=watchdog0,bus=pci.0,addr=0x7 -watchdog-action reset -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 That's nothing fancy/unusual. Also, the problem happens without the watchdog, too. As for gdb - see above. Meanwhile I'll try to see if debugging generally works. Please check it, maybe I'm doing something wrong. Also, there's a new version (prerelease - I sent an unblock request to the release team about it) available at my site -- http://www.corpit.ru/mjt/tmp/qemu-kvm/ , in particular, http://www.corpit.ru/mjt/tmp/qemu-kvm/qemu-kvm_1.1.1+dfsg-1_amd64.deb (it is all signed with my regular debian gpg key if you're concerned). Can you please try this version too? It contains many bugfixes in all areas, and there's some (albiet small) chance this issue is already fixed. I'm running it now. It will take some time to see if there's any improvement, as it took one or two days until the bug occured. What activity your guest performs? Maybe I can try to reproduce your issue locally, you provided almost all information needed for this except of some mention of the workload. Oh, you must have overseen it? It streams audio using darkice (darkice-full from deb-multimedia.org for MP3 support, to be precise) and archiving the stream. About 50% CPU (on one CPU) usually. The system is not in production use yet, so there's no significant network load, just the darkice talking to the icecast2 on the same VM. Initially I had planned to use the host sound card using PCI passthrough, but then I found out that the machine doesn't have an IOMMU... So I
Bug#685418: lbzip2: build-arch target in debian/rules doesn't work
Package: lbzip2 Version: 2.1-1 Severity: grave Justification: renders package unusable build-arch of debian/rules doesn't work properly. The package can be built using build target, but buildd builds packages using build-arch and build-indep (if they are present). As a result packages built by buildd have no content except for documentation. Such packages are obviously completely unusable, hence the grave severity. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684421: FTBFS: tests require internet connectivity
I agree with Felix, starting a local https server would be the best way - but it implies IMO too much overhead, and would bloat build-dependencies (and thus probably scare the release team from accepting this into Wheezy), so I'm uploading with the patch I prepared. Thanks, -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#662854: Wheezy confirmed
Note - upgraded my work desktop to Wheezy today and am experiencing same bug. So definitely introduced in upgrade from Squeeze to Wheezy. My workaround at home was write a script to use rdesktop instead of Remmina. You can also mitigate the effect by forcing Remmina to connect to the console when it won't kill all your work in progress if you disconnect. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685423: libqtcore4: MultiArch - cannot be configured because libqtcore4:i386 is at a different version (4:4.8.2-2+b1)
Source: libqtcore4 Version: 4.8.2+dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, I've been running SID for a long time and finally needed to install Skype to communicate over wifi. When installing skype I used the instructions to install on amd64 from http://wiki.debian.org/skype The relevant details are: # dpkg --add-architecture i386 # apt-get update # wget -O skype-install.deb http://www.skype.com/go/getskype-linux-deb # dpkg -i skype-install.deb This installed fine last week. However, when updating last Tuesday or Wednesday, I got this error messages amongst a bunch of others dpkg: error processing libqtgui4:amd64 (--configure): package libqtgui4:amd64 4:4.8.2-2+b1 cannot be configured because libqtgui4:i386 is at a different version (4:4.8.2+dfsg-1) dpkg: error processing libqtcore4:i386 (--configure): package libqtcore4:i386 4:4.8.2-2+b1 cannot be configured because libqtcore4:amd64 is at a different version (4:4.8.2+dfsg-1) dpkg: error processing libqtgui4:i386 (--configure): package libqtgui4:i386 4:4.8.2+dfsg-1 cannot be configured because libqtgui4:amd64 is at a different version (4:4.8.2-2+b1) dpkg: error processing libqtcore4:amd64 (--configure): package libqtcore4:amd64 4:4.8.2+dfsg-1 cannot be configured because libqtcore4:i386 is at a different version (4:4.8.2-2+b1) Setting up libcap2:amd64 (1:2.22-1.2) ... Setting up libjack-jackd2-0:amd64 (1.9.8~dfsg.4+20120529git007cdc37-3) ... dpkg: error processing libqt4-xml:amd64 (--configure): package libqt4-xml:amd64 4:4.8.2+dfsg-1 cannot be configured because libqt4-xml:i386 is at a different version (4:4.8.2-2+b1) dpkg: error processing libqt4-xml:i386 (--configure): package libqt4-xml:i386 4:4.8.2-2+b1 cannot be configured because libqt4-xml:amd64 is at a different version (4:4.8.2+dfsg-1) dpkg: dependency problems prevent configuration of qt4-linguist-tools: qt4-linguist-tools depends on libqt4-xml (= 4:4.8.2-2+b1); however: Version of libqt4-xml:amd64 on system is 4:4.8.2+dfsg-1. qt4-linguist-tools depends on libqtcore4 (= 4:4.8.2-2+b1); however: Version of libqtcore4:amd64 on system is 4:4.8.2+dfsg-1. It's trying to install: The following extra packages will be installed: libqt4-dbus libqt4-declarative libqt4-declarative-gestures libqt4 -declarative-particles libqt4-designer libqt4-dev libqt4-dev-bin libqt4-help libqt4-network:i386 libqt4-opengl libqt4-opengl-dev libqt4-qt3support libqt4-script libqt4-scripttools libqt4-sql libqt4-sql-mysql libqt4-sql-sqlite libqt4-svg libqt4-test libqt4-xml:i386 libqt4-xmlpatterns libqtcore4:i386 libqtgui4 libqtgui4:i386 qdbus qt4-demos qt4-designer qt4-dev-tools qt4-linguist-tools qt4-qmake qt4-qmlviewer Suggested packages: libqt4-declarative-folderlistmodel libqt4-declarative-shaders firebird-dev libmysqlclient-dev libpq-dev libsqlite0-dev libsqlite3-dev unixodbc-dev libthai0:i386 libicu48:i386 qt4-qtconfig qt4-qtconfig:i386 The following packages will be upgraded: libqt4-dbus libqt4-declarative libqt4-declarative-gestures libqt4 -declarative-particles libqt4-designer libqt4-dev libqt4-dev-bin libqt4-help libqt4-network:i386 libqt4-opengl libqt4-opengl-dev libqt4-qt3support libqt4-script libqt4-scripttools libqt4-sql libqt4-sql-mysql libqt4-sql-sqlite libqt4-svg libqt4-test libqt4-xml:i386 libqt4-xmlpatterns libqtcore4:i386 libqtgui4 libqtgui4:i386 qdbus qt4-demos qt4-designer qt4-dev-tools qt4-linguist-tools qt4-qmake qt4-qmlviewer Anything else I can offer to help, please ask -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684004: Waiting for RT approval
tag 684004 pending thanks Hi! This bug is pending an upload. We are currently waiting the RT to decide if they pre-approve the changes in the package before uploading (see #685331). Kinds regards, Lisandro. -- 12: Es posible insertar imagenes en los documentos y archivos al trabajar con Word * No o Si Damian Nadales http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Processed: Waiting for RT approval
Processing commands for cont...@bugs.debian.org: tag 684004 pending Bug #684004 [calligra] calligra: Buffer overflow Ignoring request to alter tags of bug #684004 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 684004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684004 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: [bts-link] source package accountsservice
Processing commands for cont...@bugs.debian.org:
#
# bts-link upstream status pull for source package accountsservice
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was
bts-link-de...@lists.alioth.debian.org).
# remote status report for #674419 (http://bugs.debian.org/674419)
# Bug title: gnome-shell: segfaults in libaccountservice
# * https://bugs.freedesktop.org/show_bug.cgi?id=50112
# * remote status changed: RESOLVED - REOPENED
# * remote resolution changed: FIXED - (?)
# * reopen upstream
tags 674419 - fixed-upstream
Bug #674419 [libaccountsservice0] gnome-shell: segfaults in libaccountservice
Bug #673185 {Done: Alessio Treglia ales...@debian.org} [libaccountsservice0]
gnome-shell: segfault in libaccountsservice.so.0.0.0
Bug #673211 [libaccountsservice0] gnome-shell: segfault in
libaccountsservice.so.0.0.0
Removed tag(s) fixed-upstream.
Removed tag(s) fixed-upstream.
Removed tag(s) fixed-upstream.
usertags 674419 - status-RESOLVED resolution-FIXED
Usertags were: status-RESOLVED resolution-FIXED.
Usertags are now: .
usertags 674419 + status-REOPENED
There were no usertags set.
Usertags are now: status-REOPENED.
# remote status report for #674419 (http://bugs.debian.org/674419)
# Bug title: gnome-shell: segfaults in libaccountservice
# * https://bugs.freedesktop.org/show_bug.cgi?id=50112
# * remote status changed: RESOLVED - REOPENED
# * remote resolution changed: FIXED - (?)
# * reopen upstream
tags 674419 - fixed-upstream
Bug #674419 [libaccountsservice0] gnome-shell: segfaults in libaccountservice
Bug #673185 {Done: Alessio Treglia ales...@debian.org} [libaccountsservice0]
gnome-shell: segfault in libaccountsservice.so.0.0.0
Bug #673211 [libaccountsservice0] gnome-shell: segfault in
libaccountsservice.so.0.0.0
Ignoring request to alter tags of bug #674419 to the same tags previously set
Ignoring request to alter tags of bug #673185 to the same tags previously set
Ignoring request to alter tags of bug #673211 to the same tags previously set
usertags 674419 - status-RESOLVED resolution-FIXED
Usertags were: status-REOPENED.
Usertags are now: status-REOPENED.
usertags 674419 + status-REOPENED
Usertags were: status-REOPENED.
Usertags are now: status-REOPENED.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
673185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673185
673211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673211
674419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674419
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: [bts-link] source package kdepim
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package kdepim # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #128813 (http://bugs.debian.org/128813) # Bug title: kmail: Signature should not be word-wrapped # * http://bugs.kde.org/show_bug.cgi?id=145645 # * remote status changed: UNCONFIRMED - RESOLVED # * remote resolution changed: (?) - WAITINGFORINFO # * closed upstream tags 128813 + fixed-upstream Bug #128813 [kmail] kmail: Signature should not be word-wrapped Added tag(s) fixed-upstream. usertags 128813 - status-UNCONFIRMED Usertags were: status-UNCONFIRMED. Usertags are now: . usertags 128813 + status-RESOLVED resolution-WAITINGFORINFO There were no usertags set. Usertags are now: status-RESOLVED resolution-WAITINGFORINFO. # remote status report for #194624 (http://bugs.debian.org/194624) # Bug title: kmail: Should process the encoding prior to filtering # * http://bugs.kde.org/show_bug.cgi?id=48927 # * remote status changed: UNCONFIRMED - RESOLVED # * remote resolution changed: (?) - WAITINGFORINFO # * closed upstream tags 194624 + fixed-upstream Bug #194624 [kmail] kmail: Should process the encoding prior to filtering Added tag(s) fixed-upstream. usertags 194624 - status-UNCONFIRMED Usertags were: status-UNCONFIRMED. Usertags are now: . usertags 194624 + status-RESOLVED resolution-WAITINGFORINFO There were no usertags set. Usertags are now: status-RESOLVED resolution-WAITINGFORINFO. # remote status report for #223566 (http://bugs.debian.org/223566) # Bug title: kmail: Needs a way of extracting encapsulated messages into regular mail folders. # * http://bugs.kde.org/show_bug.cgi?id=77698 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - WAITINGFORINFO # * closed upstream tags 223566 + fixed-upstream Bug #223566 [kmail] kmail: Needs a way of extracting encapsulated messages into regular mail folders. Added tag(s) fixed-upstream. usertags 223566 - status-NEW Usertags were: status-NEW. Usertags are now: . usertags 223566 + status-RESOLVED resolution-WAITINGFORINFO There were no usertags set. Usertags are now: status-RESOLVED resolution-WAITINGFORINFO. # remote status report for #240256 (http://bugs.debian.org/240256) # Bug title: kmail: Include an option to force 8-bit sending of mail # * http://bugs.kde.org/show_bug.cgi?id=79929 # * remote status changed: UNCONFIRMED - RESOLVED # * remote resolution changed: (?) - WAITINGFORINFO # * closed upstream tags 240256 + fixed-upstream Bug #240256 [kmail] kmail: Include an option to force 8-bit sending of mail Added tag(s) fixed-upstream. usertags 240256 - status-UNCONFIRMED Usertags were: status-UNCONFIRMED. Usertags are now: . usertags 240256 + status-RESOLVED resolution-WAITINGFORINFO There were no usertags set. Usertags are now: status-RESOLVED resolution-WAITINGFORINFO. # remote status report for #315766 (http://bugs.debian.org/315766) # Bug title: kmail: crash after question for sending a receive notification # * http://bugs.kde.org/show_bug.cgi?id=98390 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - UNMAINTAINED # * closed upstream tags 315766 + fixed-upstream Bug #315766 [kmail] kmail: crash after question for sending a receive notification Added tag(s) fixed-upstream. usertags 315766 - status-NEW Usertags were: status-NEW. Usertags are now: . usertags 315766 + status-RESOLVED resolution-UNMAINTAINED There were no usertags set. Usertags are now: status-RESOLVED resolution-UNMAINTAINED. # remote status report for #326592 (http://bugs.debian.org/326592) # Bug title: crash when cancelling GPG query after selecting different folder # * http://bugs.kde.org/show_bug.cgi?id=180741 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - UNMAINTAINED # * closed upstream tags 326592 + fixed-upstream Bug #326592 [kmail] crash when cancelling GPG query after selecting different folder Added tag(s) fixed-upstream. usertags 326592 - status-NEW Usertags were: status-NEW. Usertags are now: . usertags 326592 + status-RESOLVED resolution-UNMAINTAINED There were no usertags set. Usertags are now: status-RESOLVED resolution-UNMAINTAINED. # remote status report for #448599 (http://bugs.debian.org/448599) # Bug title: kmail: gmail IMAP: attachments are not visible untill user view message source # * http://bugs.kde.org/show_bug.cgi?id=93426 # * remote status changed: NEW - REOPENED usertags 448599 - status-NEW Usertags were: status-NEW. Usertags are now: . usertags 448599 + status-REOPENED There were no usertags set. Usertags are now: status-REOPENED. # remote status report for #523742 (http://bugs.debian.org/523742) # Bug title: [akregator]
Bug#630846: axiom: OpenMath C library doesn't allow commercial use
Greetings! Aren't we close enough to release to make this not worth the effort? Take care, Jonathan Nieder jrnie...@gmail.com writes: Hi again, In January, Jonathan Nieder wrote: Sam Geeraerts wrote: The file zips/omcv1.4a.tgz/OMCv1.4a/src/copyright says The SOFTWARE is provided for non-commercial use only. I see that this has been fixed upstream and in sid; thanks! Would it make sense to remove the OpenMath C library from axiom in stable as well? (A quick grep does not find any code that uses it.) Ping. I can prepare a package for stable that does that if you'd like; what do you think? Thanks, Jonathan -- Camm Maguirec...@maguirefamily.org == The earth is but one country, and mankind its citizens. -- Baha'u'llah -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [bts-link] source package abiword
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package abiword # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #681060 (http://bugs.debian.org/681060) # Bug title: abiword: Crash when copying Unicode text from Firefox # * http://bugzilla.abisource.com/show_bug.cgi?id=13280 # * remote status changed: (?) - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 681060 + fixed-upstream Bug #681060 [abiword] abiword: Crash when copying Unicode text from Firefox Added tag(s) fixed-upstream. usertags 681060 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. # remote status report for #682215 (http://bugs.debian.org/682215) # Bug title: abiword: system-wide papersize settings ignored # * http://bugzilla.abisource.com/show_bug.cgi?id=12823 # * remote status changed: (?) - NEW usertags 682215 + status-NEW There were no usertags set. Usertags are now: status-NEW. thanks Stopping processing here. Please contact me if you need assistance. -- 681060: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681060 682215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682215 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#630846: axiom: OpenMath C library doesn't allow commercial use
Hi, Camm Maguire wrote: Greetings! Aren't we close enough to release to make this not worth the effort? After wheezy is released, squeeze will still have a year of life. So I'd say no. Hoping that clarifies, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [bts-link] source package spring
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package spring # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #562794 (http://bugs.debian.org/562794) # Bug title: spring segfaults in singleplayer game (with AIs) # * http://springrts.com/mantis/view.php?id=1780 # * remote status changed: (?) - resolved # * remote resolution changed: (?) - not-fixable # * upstream said bug is wontfix tags 562794 + upstream wontfix Bug #562794 [spring] spring segfaults in singleplayer game (with AIs) Added tag(s) wontfix. usertags 562794 + status-resolved resolution-not-fixable There were no usertags set. Usertags are now: status-resolved resolution-not-fixable. # remote status report for #564001 (http://bugs.debian.org/564001) # Bug title: spring SEGFAULTS in multiplayer game # * http://springrts.com/mantis/view.php?id=1781 # * remote status changed: (?) - resolved # * remote resolution changed: (?) - fixed # * closed upstream tags 564001 + fixed-upstream Bug #564001 [spring] spring SEGFAULTS in multiplayer game Added tag(s) fixed-upstream. usertags 564001 + status-resolved resolution-fixed There were no usertags set. Usertags are now: resolution-fixed status-resolved. # remote status report for #67 (http://bugs.debian.org/67) # Bug title: spring segfaults somewhere in rendering # * http://springrts.com/mantis/view.php?id=3143 # * remote status changed: (?) - resolved # * remote resolution changed: (?) - fixed # * closed upstream tags 67 + fixed-upstream Bug #67 [spring] spring segfaults somewhere in rendering Added tag(s) fixed-upstream. usertags 67 + status-resolved resolution-fixed There were no usertags set. Usertags are now: resolution-fixed status-resolved. thanks Stopping processing here. Please contact me if you need assistance. -- 562794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562794 564001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564001 67: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=67 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: [bts-link] source package python-django
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package python-django # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #557474 (http://bugs.debian.org/557474) # Bug title: python-django: inconsistent behaviour of LocaleMiddleware w.r.t. to default language # * http://code.djangoproject.com/ticket/9340 # * remote status changed: (?) - new usertags 557474 + status-new There were no usertags set. Usertags are now: status-new. # remote status report for #653177 (http://bugs.debian.org/653177) # Bug title: Model __eq__ does not compare correctly between normal objects and deferred objects # * http://code.djangoproject.com/ticket/11892 # * remote status changed: (?) - new usertags 653177 + status-new There were no usertags set. Usertags are now: status-new. # remote status report for #663230 (http://bugs.debian.org/663230) # Bug title: With RemoteUserMiddleware, users keep being logged in after web server stops sending REMOTE_USER headers # * http://code.djangoproject.com/ticket/17869 # * remote status changed: (?) - reopened usertags 663230 + status-reopened There were no usertags set. Usertags are now: status-reopened. # remote status report for #683648 (http://bugs.debian.org/683648) # Bug title: Django's HTMLParser incompatible with python 2.7.3 # * http://code.djangoproject.com/ticket/18239 # * remote status changed: (?) - closed # * remote resolution changed: (?) - fixed # * closed upstream tags 683648 + fixed-upstream Bug #683648 [python-django] Django's HTMLParser incompatible with python 2.7.3 Added tag(s) fixed-upstream. usertags 683648 + status-closed resolution-fixed There were no usertags set. Usertags are now: resolution-fixed status-closed. thanks Stopping processing here. Please contact me if you need assistance. -- 683648: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683648 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#685425: eagle: Uninstallable on amd64 multiarch
Package: eagle Version: 5.10.0-2 Severity: grave Justification: renders package unusable Requires ia32-libs, which conflicts with multiarch. Please re-package appropriately. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (650, 'unstable'), (600, 'stable'), (550, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages eagle depends on: ii eagle-data 5.10.0-2 ii fontconfig-config 2.9.0-6 ii ia32-libs 20120102 ii lib32gcc1 1:4.7.1-2 ii lib32stdc++6 4.7.1-2 ii lib32z11:1.2.7.dfsg-13 ii libc6-i386 2.13-33 Versions of packages eagle recommends: ii extra-xdg-menus 1.0-4 eagle suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684421: marked as done (FTBFS: tests require internet connectivity)
Your message dated Mon, 20 Aug 2012 18:02:38 + with message-id e1t3wjc-0008wq...@franck.debian.org and subject line Bug#684421: fixed in ruby-net-http-persistent 2.7-2 has caused the Debian Bug report #684421, regarding FTBFS: tests require internet connectivity 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.) -- 684421: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-net-http-persistent Version: 2.7-1 Severity: serious Tags: sid, wheezy Justification: fails to build from source This package requires internet connectivity for its test suite to pass. Package builds should not rely on external network connectivity, but should be self-contained. Just removing the three affected methods from test/test_net_http_persistent.rb seems to work but I'm not sure if that's the right thing to do. Build log: # Running tests: ESE..E... Finished tests in 0.790200s, 106.3022 tests/s, 354.3407 assertions/s. 1) Error: test_connection_for_http_class_with_fakeweb(TestNetHttpPersistent): SocketError: getaddrinfo: Name or service not known /usr/lib/ruby/1.8/net/http.rb:560:in `initialize' /usr/lib/ruby/1.8/net/http.rb:560:in `open' /usr/lib/ruby/1.8/net/http.rb:560:in `connect' /usr/lib/ruby/1.8/timeout.rb:53:in `timeout' /usr/lib/ruby/1.8/timeout.rb:101:in `timeout' /usr/lib/ruby/1.8/net/http.rb:560:in `connect' /usr/lib/ruby/1.8/net/http.rb:553:in `do_start' /usr/lib/ruby/1.8/net/http.rb:548:in `start' ./debian/ruby-net-http-persistent//usr/lib/ruby/vendor_ruby/net/http/persistent.rb:511:in `connection_for' ./test/test_net_http_persistent.rb:358:in `test_connection_for_http_class_with_fakeweb' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:1058:in `run_test' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:1058:in `run' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:823:in `_run_suite' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:815:in `map' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:815:in `_run_suite' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:802:in `_run_suites' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:802:in `map' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:802:in `_run_suites' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:775:in `_run_anything' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:964:in `run_tests' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:951:in `send' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:951:in `_run' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:950:in `each' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:950:in `_run' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:939:in `run' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:697:in `autorun' -e:1 2) Error: test_connection_for_no_ssl_reuse(TestNetHttpPersistent): SocketError: getaddrinfo: Name or service not known /usr/lib/ruby/1.8/net/http.rb:560:in `initialize' /usr/lib/ruby/1.8/net/http.rb:560:in `open' /usr/lib/ruby/1.8/net/http.rb:560:in `connect' /usr/lib/ruby/1.8/timeout.rb:67:in `timeout' /usr/lib/ruby/1.8/timeout.rb:101:in `timeout' /usr/lib/ruby/1.8/net/http.rb:560:in `connect' /usr/lib/ruby/1.8/net/http.rb:553:in `do_start' /usr/lib/ruby/1.8/net/http.rb:548:in `start' ./debian/ruby-net-http-persistent//usr/lib/ruby/vendor_ruby/net/http/persistent.rb:511:in `connection_for' ./test/test_net_http_persistent.rb:391:in `test_connection_for_no_ssl_reuse' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:1058:in `run_test' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:1058:in `run' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:823:in `_run_suite' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:815:in `map' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:815:in `_run_suite' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:802:in `_run_suites' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:802:in `map' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:802:in `_run_suites' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:775:in `_run_anything' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:964:in `run_tests' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:951:in `send' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:951:in `_run' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:950:in `each' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:950:in `_run' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:939:in `run' /usr/lib/ruby/vendor_ruby/minitest/unit.rb:697:in `autorun'
Bug#674089: Possible release note for systems running PHP through CGI.
On Monday 20 August 2012, Ondřej Surý wrote: Ah, I see; it gets executed when there is no know handler or mime-type for second extension. E.g. index.php.jpeg works as expected (e.g. returning PHP source code), index.php.blubb but gets executed. I don't think there's any harm in disabling php.foobar and php.blubb files. There is also the case that the extensions after .php are known to Apache but are not associated with mime types or handlers. For example, there are extensions like .de and .en which cause the Content-Language header to be set, extensions for setting the charset (e.g. .utf8) and extensions for setting the content-encoding (none configured by default). I don't know how often this is actually used together with php. Setting the Content-* headers in the php script seems saner to me. Good to see that we are heading towards a solution anyway. What shall I do with #674089 ? I can reassign it to php5-cgi so that your next upload closes it, or do we still need release notes ? I think we still might need release notes, but it needs to be updated based on final impact of changes we have done. I am not sure if the information about filename.php.unknown-mime-type is worth release notes or just NEWS file in PHP. My guess would be latter, but opinions may vary. Maybe add just a small paragraph that the configuration of the extensions has changed and php users should read the NEWS file? Cheers, Stefan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685425: marked as done (eagle: Uninstallable on amd64 multiarch)
Your message dated Mon, 20 Aug 2012 14:13:30 -0400 with message-id CANg8-dCDchAQaa7N5HF8-tPOA0QfN2fKK9B=i2xyyanfopx...@mail.gmail.com and subject line Re: Bug#685425: eagle: Uninstallable on amd64 multiarch has caused the Debian Bug report #685425, regarding eagle: Uninstallable on amd64 multiarch 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.) -- 685425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: eagle Version: 5.10.0-2 Severity: grave Justification: renders package unusable Requires ia32-libs, which conflicts with multiarch. Please re-package appropriately. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (650, 'unstable'), (600, 'stable'), (550, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages eagle depends on: ii eagle-data 5.10.0-2 ii fontconfig-config 2.9.0-6 ii ia32-libs 20120102 ii lib32gcc1 1:4.7.1-2 ii lib32stdc++6 4.7.1-2 ii lib32z11:1.2.7.dfsg-13 ii libc6-i386 2.13-33 Versions of packages eagle recommends: ii extra-xdg-menus 1.0-4 eagle suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- On Mon, Aug 20, 2012 at 2:03 PM, Matthias Urlichs matth...@urlichs.de wrote: Package: eagle Version: 5.10.0-2 Severity: grave Justification: renders package unusable Requires ia32-libs, which conflicts with multiarch. Please re-package appropriately. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (650, 'unstable'), (600, 'stable'), (550, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages eagle depends on: ii eagle-data 5.10.0-2 ii fontconfig-config 2.9.0-6 ii ia32-libs 20120102 ii lib32gcc1 1:4.7.1-2 ii lib32stdc++6 4.7.1-2 ii lib32z11:1.2.7.dfsg-13 ii libc6-i386 2.13-33 Versions of packages eagle recommends: ii extra-xdg-menus 1.0-4 eagle suggests no packages. -- no debconf information The version in wheezy (5.12.0-3) doesn't depend on ia32-libs and has been multiarched [1]. 5.10.0-2 is the squeeze version which shouldn't care about multiarch support. [1] http://packages.debian.org/wheezy/eagle Cheers, Scott---End Message---
Bug#672959: kfreebsd-*: panic: vm_fault_copy_wired
On 20/08/12 16:07, Axel Beckert wrote: Has the exact sysvinit version where this issue crept in been positively identified? AFAIK not yet, because nobody tried. 2.88dsf-22.1 is simply what I had installed when I filed the bug. It most likely affects earlier versions too. It would be a good idea to check this I think. Axel, have you tested any more recent versions than this? In particular 2.88dsf-23 and 2.88dsf-28 made changes relevant to kFreeBSD. When I disabled parallel init as explained in [1], that avoided the crash. So that narrows down the affected versions at least a /little/ bit; concurrent boot became default in 2.88dsf-3. [1] http://bugs.debian.org/672959#20 Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672959: [Pkg-sysvinit-devel] Bug#672959: kfreebsd-*: panic: vm_fault_copy_wired
Maybe I am stupit or something, but if fsck called by some init script causes the kernel to crash, why are you trying to figure out how the init script changed to cause this, instead of looking at the kernel and fsck? If the kernel can crash, it is a bug in the kernel. If fsck can cause the kernel, this might be a bug in fsck. But I fail to see how calling fsck and causing a crash in the kernel can be a bug in the script calling fsck. why isn't this bug reassigned to the freebsd kernel? -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594753: DVD burned by braser are not working
Hi, all. I forgot this bug until today, when I have tried to burn three DVD using brasero without success. But, if I burn some files or an ISO image to a CD, it works! My info: * DVD drive: LG HL-DT-ST DVDRAM GSA-4167B, DL11 * Brasero 3.4.1-2 * Debian testing updated today So, the bug is still here, I hope some day in a near future I can burn DVD without problems. -- Saludos Fran -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 682166
Processing commands for cont...@bugs.debian.org: tags 682166 + unreproducible Bug #682166 [shogun-python-modular] upgrade fails due to rm: cannot remove `/usr/lib/python2.6/dist-packages/shogun/Classifier': Is a directory Added tag(s) unreproducible. thanks Stopping processing here. Please contact me if you need assistance. -- 682166: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682166 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: closing 682166
Processing commands for cont...@bugs.debian.org: close 682166 Bug #682166 [shogun-python-modular] upgrade fails due to rm: cannot remove `/usr/lib/python2.6/dist-packages/shogun/Classifier': Is a directory Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 682166: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682166 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#684734: marked as done (pyhoca-cli: ImportError: No module named pyhoca.cli)
Your message dated Mon, 20 Aug 2012 18:32:37 +
with message-id e1t3wmd-0006jk...@franck.debian.org
and subject line Bug#684734: fixed in pyhoca-cli 0.2.0.4-1
has caused the Debian Bug report #684734,
regarding pyhoca-cli: ImportError: No module named pyhoca.cli
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.)
--
684734: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684734
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: pyhoca-cli
Version: 0.2.0.3-1
Severity: grave
Justification: renders package unusable
pyhoca-cli doesn't start:
$ pyhoca-cli
/usr/lib/python2.7/dist-packages/x2go/__init__.py:183: UserWarning: libevent
version mismatch: system version is '2.0.19-stable' but this gevent is compiled
against '2.0.16-stable'
from gevent import monkey
Traceback (most recent call last):
File /usr/bin/pyhoca-cli, line 105, in module
from pyhoca.cli import current_home, PyHocaCLI, runtime_error
ImportError: No module named pyhoca.cli
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages pyhoca-cli depends on:
ii python 2.7.3-2
ii python-setproctitle 1.0.1-1+b1
ii python-x2go 0.2.0.8-1
ii python2.7 [python-argparse] 2.7.3-2
--
Jakub Wilk
---End Message---
---BeginMessage---
Source: pyhoca-cli
Source-Version: 0.2.0.4-1
We believe that the bug you reported is fixed in the latest version of
pyhoca-cli, which is due to be installed in the Debian FTP archive.
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 684...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel mike.gabr...@das-netzwerkteam.de (supplier of updated pyhoca-cli
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 20 Aug 2012 09:08:31 +0200
Source: pyhoca-cli
Binary: pyhoca-cli
Architecture: source all
Version: 0.2.0.4-1
Distribution: unstable
Urgency: low
Maintainer: X2Go Packaging Team pkg-x2go-de...@lists.alioth.debian.org
Changed-By: Mike Gabriel mike.gabr...@das-netzwerkteam.de
Description:
pyhoca-cli - Command line X2Go client written in Python
Closes: 684734
Changes:
pyhoca-cli (0.2.0.4-1) unstable; urgency=low
.
* New upstream release. (Closes: #684734).
* /debian/control:
+ Versioned Build-Depends on python (= 2.6.6-14~).
+ Add ${python:Depends} to Depends.
+ Fix typo (corrected: bandwidth) in long description.
Checksums-Sha1:
9198cb9af83d96d3f74499fe382ca5aab441aaa1 2053 pyhoca-cli_0.2.0.4-1.dsc
fbfc8a6854e9d742cf989b94c970e3249a5c7fc0 39686 pyhoca-cli_0.2.0.4.orig.tar.gz
bae4cd11c3420667be36467d333bb11916aca9a9 15479
pyhoca-cli_0.2.0.4-1.debian.tar.gz
9db3827c7714ce6e386d1e7137a0b727add9e9d6 34134 pyhoca-cli_0.2.0.4-1_all.deb
Checksums-Sha256:
87d98011f3190add1231e7534877a0381b7dc27a9dc4ebb176e4846be55a5430 2053
pyhoca-cli_0.2.0.4-1.dsc
f90f55394a629ef8798086933360bd5cfd29aea04de540ca75beb13a654e92e7 39686
pyhoca-cli_0.2.0.4.orig.tar.gz
ef3586e2abc2e1dd0b953096a15322dab79bf04021381255d34d1eecdb9d2f8c 15479
pyhoca-cli_0.2.0.4-1.debian.tar.gz
33aab708cc1f5eaf524638c0450b791a5461dd9e8c6579d0358c429788973b6a 34134
pyhoca-cli_0.2.0.4-1_all.deb
Files:
85c94fc37f302450bd9a19202ee20c92 2053 python optional pyhoca-cli_0.2.0.4-1.dsc
b2456243c9398425747beb49d02d9372 39686 python optional
pyhoca-cli_0.2.0.4.orig.tar.gz
83c282ec0de538360f70a83389d163c6 15479 python optional
pyhoca-cli_0.2.0.4-1.debian.tar.gz
905c8391db3408900a4ed485d19e6b88 34134 python optional
pyhoca-cli_0.2.0.4-1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJQMn70AAoJEKtkX0BihqfQCtMP/3chhzVPTsoVDZPrO4ZcsFOS
yxClIG/VmwO57v65ofJHqad+uMYP1QK16FhKWShKx2RPBPRjAfYxLlUS57Qdf3d3
qeM9daMxM7gze05a5ngmI204hIO1JKMAoXpRo4c2N4SABPMxgSAMLPPThfjZK7zh
YgiQKLiBwMaDiw/tCWCpNTG22iIGnOahaklgCanKrzO4On1ODapfhjGYaw2hD69/
NkaKTVdnq0G3RYKhfSej04RPf/f/O+ckay4tkeu0cuWxaqPPCf2EEgtUEXFGki8r
Bug#685353: qemu-kvm: kvm process hangs with 100% CPU usage
Hi Michael,
The hanging kvm process uses 100% CPU, there's no serial console anymore,
no
access to VNC anymore. No output on netconsole either. Unfortunately, I
cannot
even get a useful gdb backtrace:
Finally, I figured out how to get a useful backtrace. Running gdb and then
using attach $PID doesn't give me symbols, but gdb /usr/bin/kvm -p $PID
does (tested with qemu-kvm{,-dbg} 1.1.1+dfsg-1). I will send a backtrace as
soon as the problem occurs again.
Cheers,
Mike
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672959: [Pkg-sysvinit-devel] Bug#672959: kfreebsd-*: panic: vm_fault_copy_wired
On 20/08/12 19:26, Petter Reinholdtsen wrote: If the kernel can crash, it is a bug in the kernel. Well, something in the initscripts could be telling the kernel to do something bad. Maybe to do with the rootfs, or swap. Then it might be acceptable for the kernel to panic and that wouldn't be a kernel bug. Probably some initscript is at fault here, but since I don't know which one yet, I filed against sysvinit until we know where to reassign it. If fsck can cause the kernel [to crash], this might be a bug in fsck. I'm not sure that fsck itself causes this. Because if I boot a shell instead of /sbin/init, and run initscripts manually (including fsck), it doesn't panic. I think when sysvinit runs initscripts in parallel, it does some buffering of console output, so that makes it hard to know what was running at the time of the panic. I think fsck must have already finished running when the panic happens (or else we wouldn't see it mentioned?). Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684604: eclipse-rcp: eclipse 3.8 hangs on splash screen with Loading Workbench after update from 3.7.2
Jakub Adam jakub.a...@ktknet.cz writes: Hi Felix, hello Jakub, On 19.8.2012 19:31, Felix Natter wrote: I'd really like to help you, but this file: /usr/lib/eclipse/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info is not there any more. It will be back when you reinstall eclipse-platform. That you are missing it right now is a good sign, means you will get correct version from the latest package when installed and we don't have to care about its content. You shouldn't ever run eclipse as root of course, or it will be overwritten. Here are the contents of bundles.info: #version=1 com.ibm.icu,4.4.2.v20110823,plugins/com.ibm.icu_4.4.2.v20110823.jar,4,false com.jcraft.jsch,0.1.42,plugins/com.jcraft.jsch_0.1.42.jar,4,false javax.el,2.2.0,plugins/javax.el_2.2.0.jar,4,false javax.servlet,3.0.0.v201103241327,plugins/javax.servlet_3.0.0.v201103241327.jar,4,false javax.servlet.jsp,2.2.0.v201103241327,plugins/javax.servlet.jsp_2.2.0.v201103241327.jar,4,false org.apache.ant,1.8.3.v20120321-1730,plugins/org.apache.ant_1.8.3.v20120321-1730/,4,false org.apache.commons.codec,1.4.0,plugins/org.apache.commons.codec_1.4.0.jar,4,false org.apache.commons.httpclient,3.1.0,plugins/org.apache.commons.httpclient_3.1.0.jar,4,false org.apache.commons.logging,1.0.4.v20080605-1930,plugins/org.apache.commons.logging_1.0.4.v20080605-1930.jar,4,false org.apache.el,7.0.26,plugins/org.apache.el_7.0.26.jar,4,false org.apache.felix.gogo.command,0.12.0,plugins/org.apache.felix.gogo.command_0.12.0.jar,4,false org.apache.felix.gogo.runtime,0.10.0,plugins/org.apache.felix.gogo.runtime_0.10.0.jar,4,false org.apache.felix.gogo.shell,0.10.0,plugins/org.apache.felix.gogo.shell_0.10.0.jar,4,false org.apache.jasper,7.0.26,plugins/org.apache.jasper_7.0.26.jar,4,false org.apache.juli,7.0.26,plugins/org.apache.juli_7.0.26.jar,4,false org.apache.lucene.analysis,2.9.4,plugins/org.apache.lucene.analysis_2.9.4.jar,4,false org.apache.lucene.core,2.9.4,plugins/org.apache.lucene.core_2.9.4.jar,4,false org.apache.tomcat.api,7.0.26,plugins/org.apache.tomcat.api_7.0.26.jar,4,false org.apache.tomcat.util,7.0.26,plugins/org.apache.tomcat.util_7.0.26.jar,4,false org.eclipse.ant.core,3.2.400.dist,plugins/org.eclipse.ant.core_3.2.400.dist.jar,4,false org.eclipse.compare,3.5.300.dist,plugins/org.eclipse.compare_3.5.300.dist.jar,4,false org.eclipse.compare.core,3.5.200.dist,plugins/org.eclipse.compare.core_3.5.200.dist.jar,4,false org.eclipse.core.boot,3.1.300.dist,plugins/org.eclipse.core.boot_3.1.300.dist.jar,4,false org.eclipse.core.commands,3.6.1.dist,plugins/org.eclipse.core.commands_3.6.1.dist.jar,4,false org.eclipse.core.contenttype,3.4.200.dist,plugins/org.eclipse.core.contenttype_3.4.200.dist.jar,4,false org.eclipse.core.databinding,1.4.1.dist,plugins/org.eclipse.core.databinding_1.4.1.dist.jar,4,false org.eclipse.core.databinding.beans,1.2.200.dist,plugins/org.eclipse.core.databinding.beans_1.2.200.dist.jar,4,false org.eclipse.core.databinding.observable,1.4.1.dist,plugins/org.eclipse.core.databinding.observable_1.4.1.dist.jar,4,false org.eclipse.core.databinding.property,1.4.100.dist,plugins/org.eclipse.core.databinding.property_1.4.100.dist.jar,4,false org.eclipse.core.expressions,3.4.400.dist,plugins/org.eclipse.core.expressions_3.4.400.dist.jar,4,false org.eclipse.core.externaltools,1.0.100.dist,plugins/org.eclipse.core.externaltools_1.0.100.dist.jar,4,false org.eclipse.core.filebuffers,3.5.200.dist,plugins/org.eclipse.core.filebuffers_3.5.200.dist.jar,4,false org.eclipse.core.filesystem,1.3.200.dist,plugins/org.eclipse.core.filesystem_1.3.200.dist.jar,4,false org.eclipse.core.filesystem.linux.x86,1.4.0.dist,plugins/org.eclipse.core.filesystem.linux.x86_1.4.0.dist.jar,4,false org.eclipse.core.jobs,3.5.200.dist,plugins/org.eclipse.core.jobs_3.5.200.dist.jar,4,false org.eclipse.core.net,1.2.200.dist,plugins/org.eclipse.core.net_1.2.200.dist.jar,4,false org.eclipse.core.net.linux.x86,1.1.200.dist,plugins/org.eclipse.core.net.linux.x86_1.1.200.dist.jar,4,false org.eclipse.core.resources,3.8.0.dist,plugins/org.eclipse.core.resources_3.8.0.dist.jar,4,false org.eclipse.core.runtime,3.8.0.dist,plugins/org.eclipse.core.runtime_3.8.0.dist.jar,4,true org.eclipse.core.runtime.compatibility,3.2.200.dist,plugins/org.eclipse.core.runtime.compatibility_3.2.200.dist.jar,4,false org.eclipse.core.runtime.compatibility.auth,3.2.300.dist,plugins/org.eclipse.core.runtime.compatibility.auth_3.2.300.dist.jar,4,false org.eclipse.core.runtime.compatibility.registry,3.5.100.dist,plugins/org.eclipse.core.runtime.compatibility.registry_3.5.100.dist/,4,false org.eclipse.core.variables,3.2.600.dist,plugins/org.eclipse.core.variables_3.2.600.dist.jar,4,false org.eclipse.cvs,1.2.0.dist,plugins/org.eclipse.cvs_1.2.0.dist.jar,4,false org.eclipse.debug.core,3.7.100.dist,plugins/org.eclipse.debug.core_3.7.100.dist.jar,4,false org.eclipse.debug.ui,3.8.0.dist,plugins/org.eclipse.debug.ui_3.8.0.dist.jar,4,false
Bug#681654: About kstars-data-extra-tycho2 distributability
Hi Debian-Legal On the package kstars-data-extra-tycho2 it has arisen a doubt about its distributability: See bug #681654 I think there is no problem with data distributability, and just a minor issue with package's Copyright file which I think I fixed on 1.1r1-8 at http://mentors.debian.net/package/kstars-data-extra-tycho2 Please have a look at it. I'm willing to help with any further info or change to the package. Thanks in advance Noel Torres er Envite signature.asc Description: This is a digitally signed message part.
Bug#674089: Possible release note for systems running PHP through CGI.
Hi Ondřej. On Mon, 2012-08-20 at 14:57 +0200, Ondřej Surý wrote: http://anonscm.debian.org/gitweb/?p=pkg-php/php.git;a=commit;h=72eef08994f65b227103509617652d7c0bf0587a - You mention in the README.Debian now, that no other webserver likely used /etc/mime.types. Wasn't there someone who meant lighthttp was also using it? - I like the changes to the wording of the PHP 5 CGI and Apache HTTP Server section. - Where you write: add the mentioned configuration block to one or more virtual sites. ... you may even refine that to add the mentioned configuration block to one or more virtual hosts or directories. - Where you write: It's advised to not mixmatch mod_php and php5-cgi in the same is that intended, that php5-fpm is missing? To the rules: - They seem ok for a security point of view. - When using FilesMatch, one can slightly optimise the subpatterns, by placing ?: after the (, e.g. .+\.ph(?:p[345]?|t|tml)$ - At the places where you Deny, one might perhaps add Satisfy All again. It's All per default, but if one has set that to Any in main server context, your deny-intention might geht ineffective again. I agree on that, even though I think that PHP should have it's own mimetype definition (same as python or perl, e.g. application/x-php, but let's keep this discussion out of this issue, since it's something different). +1 on that. I am not aware of any other (Debian shipped) web server which uses system-wide mime-types. At least both nginx and lighttpd don't depend on system mime types for interpreting PHP files (both use extension based definitions). Ah ok,... so ignore my question from above... :) If more than one extension is given that maps onto the same type of meta-information, then the one to the right will be used, except for languages and content encodings. For example, if .gif maps to the MIME-type image/gif and .html maps to the MIME-type text/html, then the file welcome.gif.html will be associated with the MIME-type text/html. Right, the others already pointed out in the meantime, what can still happen. I guess we should be largely safe of all this now. Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#672959: [Pkg-sysvinit-devel] Bug#672959: kfreebsd-*: panic: vm_fault_copy_wired
Petter Reinholdtsen wrote: Maybe I am stupit or something, but if fsck called by some init script causes the kernel to crash, No, it doesn't. As I wrote, clearly something _after_ the fsck does that. 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#672959: kfreebsd-*: panic: vm_fault_copy_wired
Hi Steven, Steven Chamberlain wrote: 2.88dsf-22.1 is simply what I had installed when I filed the bug. It most likely affects earlier versions too. It would be a good idea to check this I think. Axel, have you tested any more recent versions than this? So far all my tests where with 2.88dsf-31 which is the most up-to-date version as far as I can see. Not sure about the version when I ran into it initially, but it was probably not older than a few weeks. 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
Processed: Re: Bug#672959: kfreebsd-*: panic: vm_fault_copy_wired
Processing commands for cont...@bugs.debian.org: # probably want to reassign this to another package later, but... found 672959 sysvinit/2.88dsf-31 Bug #672959 [src:sysvinit] kfreebsd-*: panic: vm_fault_copy_wired Marked as found in versions sysvinit/2.88dsf-31. thanks Stopping processing here. Please contact me if you need assistance. -- 672959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672959 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: bug 684076 is forwarded to http://www.munin-monitoring.org/ticket/1238
Processing commands for cont...@bugs.debian.org: forwarded 684076 http://www.munin-monitoring.org/ticket/1238 Bug #684076 [munin] munin-cgi-graph: User can load new config, pointing log to arbitrary file Set Bug forwarded-to-address to 'http://www.munin-monitoring.org/ticket/1238'. thanks Stopping processing here. Please contact me if you need assistance. -- 684076: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684076 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: bug 684075 is forwarded to http://www.munin-monitoring.org/ticket/1234
Processing commands for cont...@bugs.debian.org: forwarded 684075 http://www.munin-monitoring.org/ticket/1234 Bug #684075 [munin-plugins-core] munin: insecure state file handling, munin-root Set Bug forwarded-to-address to 'http://www.munin-monitoring.org/ticket/1234'. thanks Stopping processing here. Please contact me if you need assistance. -- 684075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684075 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#672959: [Pkg-sysvinit-devel] Bug#672959: kfreebsd-*: panic: vm_fault_copy_wired
On 20/08/12 20:16, Axel Beckert wrote: [...] clearly something _after_ the fsck does that. Looking back at my 'dot' graph of initscript dependencies, it seems like freebsdutils is the only thing that is free to run before, after, or at the same time as checkroot.sh and thus could be affected by how long it takes to run. Then mtab.sh would be the next thing to run after both checkroot.sh and freebsdutils are finished. freebsdutils might try to rm and recreate /etc/mtab as a symlink while fsck is running, if it is not already there. Or more likely that would fail because I think it would be still read-only at that point. Or instead it may try to mount things on /dev/fd, /proc or /sys while fsck is running. I don't know what implications that could have. Do you think freebsdutils should really wait for checkroot? Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685439: Use of uninitialized value $_[0] in hash element at /usr/bin/apt-show-versions line 729.
Package: apt-show-versions Version: 0.18 Severity: grave $ apt-show-versions |head Use of uninitialized value $_[0] in hash element at /usr/bin/apt-show-versions line 729. Use of uninitialized value in string comparison (cmp) at /usr/bin/apt-show-versions line 721. Use of uninitialized value $_[0] in hash element at /usr/bin/apt-show-versions line 729. Use of uninitialized value in string comparison (cmp) at /usr/bin/apt-show-versions line 721. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-486 Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages apt-show-versions depends on: ii apt 0.9.7.4 ii libapt-pkg-perl 0.1.26+b1 ii perl [libstorable-perl] 5.14.2-12 apt-show-versions recommends no packages. apt-show-versions 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: reopening 682166
Processing commands for cont...@bugs.debian.org:
reopen 682166
Bug #682166 {Done: Soeren Sonnenburg so...@debian.org}
[shogun-python-modular] upgrade fails due to rm: cannot remove
`/usr/lib/python2.6/dist-packages/shogun/Classifier': Is a directory
Bug reopened
Ignoring request to alter fixed versions of bug #682166 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
682166: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682166
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#684024: python-adodb: broken binary-indep target
On Sun, 12 Aug 2012 21:01:50 +0200, Evgeni Golov wrote: The following patch would fix the issue: [..] Besides that the package ships .pyc files which as an ftp-master auto-reject reason: % lintian -F python-adodb_2.10-1.1_amd64.changes E: python-adodb: package-installs-python-bytecode usr/share/pyshared/adodb/__init__.pyc E: python-adodb: package-installs-python-bytecode usr/share/pyshared/adodb/adodb.pyc E: python-adodb: package-installs-python-bytecode usr/share/pyshared/adodb/adodb_access.pyc E: python-adodb: package-installs-python-bytecode usr/share/pyshared/adodb/adodb_mssql.pyc E: python-adodb: package-installs-python-bytecode usr/share/pyshared/adodb/adodb_mxodbc.pyc E: python-adodb: package-installs-python-bytecode usr/share/pyshared/adodb/adodb_mxoracle.pyc E: python-adodb: package-installs-python-bytecode usr/share/pyshared/adodb/adodb_mysql.pyc E: python-adodb: package-installs-python-bytecode usr/share/pyshared/adodb/adodb_oci8.pyc E: python-adodb: package-installs-python-bytecode usr/share/pyshared/adodb/adodb_odbc.pyc E: python-adodb: package-installs-python-bytecode usr/share/pyshared/adodb/adodb_odbc_mssql.pyc E: python-adodb: package-installs-python-bytecode usr/share/pyshared/adodb/adodb_postgres.pyc E: python-adodb: package-installs-python-bytecode usr/share/pyshared/adodb/adodb_pyodbc.pyc E: python-adodb: package-installs-python-bytecode usr/share/pyshared/adodb/adodb_sqlite.pyc E: python-adodb: package-installs-python-bytecode usr/share/pyshared/adodb/adodb_vfp.pyc Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Joan Baez: Forever Young signature.asc Description: Digital signature
Bug#678714: [Pkg-kde-extras] Bug#678714: [kde-gtk-config] src: Fix freezing problem on load
Hi, the [1] patch is not really useful. It's removing symlinks but it's not harmful to follow them in this case. It's not a recursive/iterative function so it's harmless. It shouldn't be applied. Yes, you are right. I made test sample and checked it. So the first point in this bug report is false. Useless patch was removed. the [2] patch, on one part is fixing the bug like i did, I updated this patch to decrease the difference. on the other it's setting the first entry in the combo box for no apparent reason... When KDE is installed at least one icon theme is present in system. But without this change [1] user will see empty icons and empty combobox item at first run or if theme from his settings is not exist. I believe this should be fixed. Just remove your settings file and test the application. Best regards, Boris [1] https://github.com/tehnick/kde-gtk-config-debian/blob/master/debian/patches/fix-loading-icons#L33 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684851: scim-canna: FTBFS: scim_canna_imengine_setup.cpp:156:8: error: 'GtkTooltips' does not name a type
Hi,
During a rebuild of all packages in *wheezy*, your package failed to
build on amd64.
Relevant part:
x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I..
-DSCIM_CANNA_LOCALEDIR=\/usr/share/locale\
-DSCIM_ICONDIR=\/usr/share/scim/icons\ -pthread -I/usr/include/scim-1.0
-I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0
-I/usr/include/freetype2 -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/libpng12 -I/usr/include/scim-1.0 -g -O2 -MT
canna_imengine_setup_la-scim_canna_imengine_setup.lo -MD -MP -MF
.deps/canna_imengine_setup_la-scim_canna_imengine_setup.Tpo -c
scim_canna_imengine_setup.cpp -fPIC -DPIC -o
.libs/canna_imengine_setup_la-scim_canna_imengine_setup.o
scim_canna_imengine_setup.cpp:156:8: error: 'GtkTooltips' does not name a
type
I think that this already fixed in scim-canna 1.0.0-4.1.
I will request unblock to release team.
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682166: marked as done (upgrade fails due to rm: cannot remove `/usr/lib/python2.6/dist-packages/shogun/Classifier': Is a directory)
Your message dated Mon, 20 Aug 2012 23:03:22 + with message-id e1t3b0e-0004ct...@franck.debian.org and subject line Bug#682166: fixed in shogun 1.1.0-6 has caused the Debian Bug report #682166, regarding upgrade fails due to rm: cannot remove `/usr/lib/python2.6/dist-packages/shogun/Classifier': Is a directory 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.) -- 682166: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: shogun-python-modular Version: 1.1.0-5 Severity: important I believe I have ran into this already on few boxes while upgrading to current state of wheezy or sid: ... Preparing to replace shogun-python-modular 1.0.0-1 (using .../shogun-python-modular_1.1.0-5_amd64.deb) ... rm: cannot remove `/usr/lib/python2.6/dist-packages/shogun/Classifier': Is a directory rm: cannot remove `/usr/lib/python2.6/dist-packages/shogun/Clustering': Is a directory rm: cannot remove `/usr/lib/python2.6/dist-packages/shogun/Distance': Is a directory rm: cannot remove `/usr/lib/python2.6/dist-packages/shogun/Distribution': Is a directory rm: cannot remove `/usr/lib/python2.6/dist-packages/shogun/Evaluation': Is a directory rm: cannot remove `/usr/lib/python2.6/dist-packages/shogun/Features': Is a directory rm: cannot remove `/usr/lib/python2.6/dist-packages/shogun/IO': Is a directory rm: cannot remove `/usr/lib/python2.6/dist-packages/shogun/Kernel': Is a directory rm: cannot remove `/usr/lib/python2.6/dist-packages/shogun/Library': Is a directory rm: cannot remove `/usr/lib/python2.6/dist-packages/shogun/Mathematics': Is a directory rm: cannot remove `/usr/lib/python2.6/dist-packages/shogun/ModelSelection': Is a directory rm: cannot remove `/usr/lib/python2.6/dist-packages/shogun/Preprocesconfigured to not write apport reports sor': Is a directory rm: cannot remove `/usr/lib/python2.6/dist-packages/shogun/Regression': Is a directory rm: cannot remove `/usr/lib/python2.6/dist-packages/shogun/Structure': Is a directory dpkg: error processing /var/cache/apt/archives/shogun-python-modular_1.1.0-5_amd64.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Preparing to replace python-h5py 2.0.0-1 (using .../python-h5py_2.0.1-2+b1_amd64.deb) .. ... in this light it might well worth testing upgrade from squeeze to wheezy having shogun-python-modular installed... Cheers! -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages shogun-python-modular depends on: ii libarpack23.1.1-2 ii libatlas3-base3.8.4-7 ii libc6 2.13-33 ii libgcc1 1:4.7.1-2 ii libglpk0 4.45-1 ii libhdf5-7 [libhdf5-7] 1.8.8-9 ii libjson0 0.9-1.1 ii liblzma5 5.1.1alpha+20120614-1 ii liblzo2-2 2.06-1 ii libpython2.6 2.6.8-0.2 ii libpython2.7 2.7.3~rc2-2.1 ii libshogun11 1.1.0-5 ii libstdc++64.7.1-2 ii libxml2 2.8.0+dfsg1-4 ii python2.7.3~rc2-1 ii python-numpy [python-numpy-abi9] 1:1.6.2-1 ii python2.6 2.6.8-0.2 ii python2.7 2.7.3~rc2-2.1 ii zlib1g1:1.2.7.dfsg-13 Versions of packages shogun-python-modular recommends: ii python-matplotlib 1.1.1~rc2-1 ii python-scipy 0.10.1+dfsg1-3 shogun-python-modular suggests no packages. -- debconf-show failed ---End Message--- ---BeginMessage--- Source: shogun Source-Version: 1.1.0-6 We believe that the bug you reported is fixed in the latest version of shogun, which is due to be installed in the Debian FTP archive. 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 682...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution
Processed: limit source to meta-gnome3, tagging 681757
Processing commands for cont...@bugs.debian.org: #meta-gnome3 (1:3.4+2) UNRELEASED; urgency=low # # * Add architecture tweaks for unavailable packages: rygel, aisleriot, #seed. Closes: #681757. # limit source meta-gnome3 Limiting to bugs with field 'source' containing at least one of 'meta-gnome3' Limit currently set to 'source':'meta-gnome3' tags 681757 + pending Bug #681757 [src:meta-gnome3] uninstallable meta-packages (prevents testing migration) Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 681757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681757 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: limit source to evince, tagging 678995, tagging 658139
Processing commands for cont...@bugs.debian.org: #evince (3.4.0-3) UNRELEASED; urgency=low # # * Build with all hardening flags. Closes: #678995. # * Re-add evince.mime with only application/pdf supported. #Closes: #658139. # limit source evince Limiting to bugs with field 'source' containing at least one of 'evince' Limit currently set to 'source':'evince' tags 678995 + pending Bug #678995 [src:evince] src:evince: please build with PIE and bindnow Added tag(s) pending. tags 658139 + pending Bug #658139 [evince] missing mime entry Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 658139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658139 678995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678995 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#649014: marked as done (gnome-core: gnome-packagekit is not ready to be in the default install)
Your message dated Tue, 21 Aug 2012 01:03:13 +0200 with message-id 1345503793.5401.42.camel@tomoyo and subject line Fixed in wheezy has caused the Debian Bug report #649014, regarding gnome-core: gnome-packagekit is not ready to be in the default install 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.) -- 649014: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649014 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gnome-core Version: 1:3.0+3 Severity: serious With missing features like #606025 in packagekit, it seems to me that exposing this in the default wheezy desktop install is a bad idea. Cheers, Julien ---End Message--- ---BeginMessage--- Hi, as explained by the gnome-packagekit maintainer, version 3.4 should have the required features and should therefore be appropriate. Furthermore we don’t have much choice since update-manager does not look really usable in its current state. Cheers, -- .''`. Josselin Mouette : :' : `. `' `End Message---
Bug#685418: marked as done (lbzip2: build-arch target in debian/rules doesn't work)
Your message dated Tue, 21 Aug 2012 00:02:37 + with message-id e1t3bvz-0002sd...@franck.debian.org and subject line Bug#685418: fixed in lbzip2 2.2-2 has caused the Debian Bug report #685418, regarding lbzip2: build-arch target in debian/rules doesn't work 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.) -- 685418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: lbzip2 Version: 2.1-1 Severity: grave Justification: renders package unusable build-arch of debian/rules doesn't work properly. The package can be built using build target, but buildd builds packages using build-arch and build-indep (if they are present). As a result packages built by buildd have no content except for documentation. Such packages are obviously completely unusable, hence the grave severity. ---End Message--- ---BeginMessage--- Source: lbzip2 Source-Version: 2.2-2 We believe that the bug you reported is fixed in the latest version of lbzip2, which is due to be installed in the Debian FTP archive. 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 685...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mikolaj Izdebski zurg...@gmail.com (supplier of updated lbzip2 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, 20 Aug 2012 18:59:20 +0200 Source: lbzip2 Binary: lbzip2 Architecture: source amd64 Version: 2.2-2 Distribution: unstable Urgency: low Maintainer: Mikolaj Izdebski zurg...@gmail.com Changed-By: Mikolaj Izdebski zurg...@gmail.com Description: lbzip2 - fast, multi-threaded bzip2 utility Closes: 685418 Changes: lbzip2 (2.2-2) unstable; urgency=low . * debian/rules: Add a working build-arch target, closes: #685418. Checksums-Sha1: 472608c026e9af07d82afe5fcd13ed7750a6f2a3 1169 lbzip2_2.2-2.dsc c58e9c7d64f609f0c64fba624646a3d07df2f215 5373 lbzip2_2.2-2.debian.tar.bz2 98c897e5267808c1dc48b1164b84593fe4c331b2 80098 lbzip2_2.2-2_amd64.deb Checksums-Sha256: 4c175c3abb21edea56d692c0df25d0bf6095fe4ac3a4f79e5942855a5108f146 1169 lbzip2_2.2-2.dsc 8e934105272f9bebb95eda4cbe859f754e5fa9283cc4f53ed7d6765465f9bded 5373 lbzip2_2.2-2.debian.tar.bz2 ecb484bb354c050b442828dad94e902bb814a6e65c34b70e0bd2c11109601174 80098 lbzip2_2.2-2_amd64.deb Files: d63ec0b15b2231c49583fb4f80f381fa 1169 utils extra lbzip2_2.2-2.dsc 586f36bbbdb29b56efc2660e4094a2e1 5373 utils extra lbzip2_2.2-2.debian.tar.bz2 b4fd66a626683e97d45fa197bbd794c6 80098 utils extra lbzip2_2.2-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlAyzYsACgkQMDatjqUaT92VLwCgkcymCDYG1kqAXAoncejK/SMN Bk0AoIJ8nSsQPCOG18DZLQRAfKS+hw0B =o3rg -END PGP SIGNATUREEnd Message---
Bug#685463: scim-canna: FTBFS: mv: cannot stat `/tmp/buildd/scim-canna-1.0.0/debian/scim-canna/usr/lib/scim-1.0/1.4.0/IMEngine/canna.a': No such file or directory
Source: scim-canna
Version: 1.0.0-4.1
Severity: serious
Justification: fails to build from source
Tag: patch
Hi,
scim-canna FTBFS on latest unstable.
-
libtool: install: warning: remember to run `libtool --finish
/usr/lib/x86_64-linux-gnu/scim-1.0/1.4.0/SetupUI'
make[3]: Leaving directory `/tmp/buildd/scim-canna-1.0.0/src'
make[2]: Leaving directory `/tmp/buildd/scim-canna-1.0.0/src'
Making install in data
make[2]: Entering directory `/tmp/buildd/scim-canna-1.0.0/data'
make[3]: Entering directory `/tmp/buildd/scim-canna-1.0.0/data'
make[3]: Nothing to be done for `install-exec-am'.
test -z /usr/share/scim/icons || mkdir -p --
/tmp/buildd/scim-canna-1.0.0/debian/scim-canna/usr/share/scim/icons
/usr/bin/install -c -m 644 'scim-canna.png'
'/tmp/buildd/scim-canna-1.0.0/debian/scim-canna/usr/share/scim/icons/scim-canna.png'
make[3]: Leaving directory `/tmp/buildd/scim-canna-1.0.0/data'
make[2]: Leaving directory `/tmp/buildd/scim-canna-1.0.0/data'
make[2]: Entering directory `/tmp/buildd/scim-canna-1.0.0'
make[3]: Entering directory `/tmp/buildd/scim-canna-1.0.0'
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/tmp/buildd/scim-canna-1.0.0'
make[2]: Leaving directory `/tmp/buildd/scim-canna-1.0.0'
make[1]: Leaving directory `/tmp/buildd/scim-canna-1.0.0'
mv /tmp/buildd/scim-canna-1.0.0/debian/scim-canna/usr/lib/scim-1.0/`pkg-config
--variable=scim_binary_version scim`/IMEngine/canna.a \
/tmp/buildd/scim-canna-1.0.0/debian/scim-canna/usr/lib/scim-1.0/`pkg-config
--variable=scim_binary_version scim`/IMEngine/libcanna.a
mv: cannot stat
`/tmp/buildd/scim-canna-1.0.0/debian/scim-canna/usr/lib/scim-1.0/1.4.0/IMEngine/canna.a':
No such file or directory
make: *** [install] Error 1
-
scim converted to multiarch. But scim-canna does not yet convert to multiarch.
I created a patch which revice this problem, and attached.
Please check and apply.
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
scim-canna_1.0.0-4.1_amd64.build.gz
Description: GNU Zip compressed data
scim-canna-1.0.0.debdiff
Description: Binary data
Bug#672959: [Pkg-sysvinit-devel] Bug#672959: kfreebsd-*: panic: vm_fault_copy_wired
Hi, I tried commenting out the code in checkroot.sh that remounts the rootfs as writable after fsck is finished. It still panics, but then the filesystem isn't marked as dirty on next boot (because fsck succeeded, marked it as clean, and the fs was still mounted read-only at the time of the panic). Adding a sleep atop of mtab.sh doesn't seem to delay the panic. I figure that would be the next script to run after checkroot.sh. On 20/08/12 20:50, Steven Chamberlain wrote: freebsdutils is [...] free to run before, after, or at the same time as checkroot.sh I've been looking into that. freebsd-utils provides udev and checkroot depends on that. That seems to affect the ordering of /etc/rcS.d/S* symlinks at least. But the /etc/init.d/.depend.boot file as used by startpar, doesn't seem to reflect that dependency at all. Either way, I didn't manage to fix anything yet by changing the dependencies of the initscripts around. I can successfully boot a system with a dirty rootfs by starting a shell instead of /sbin/init, and then: cd /etc/rcS.d for i in S* ; do sh $i start ; done Whereas invoking this instead, would trigger the kernel panic, whether I mount linprocfs beforehand or not: /sbin/startpar -p 4 -t 20 -T 3 -M boot -P N -R S And the same happens even with -p 0. This is a single-CPU VM running kfreebsd-i386. I'm beginning to think that startpar is malfunctioning in some way (after checkroot.sh returns, but before it runs the next script). Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685469: ekg2: missing copyright file
Package: ekg2 Version: 1:0.3.1-1 Severity: serious Justification: Policy 12.5 User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed that your package does not contain a copyright file. # ls -la /usr/share/doc/ekg2 total 0 drwxr-xr-x 2 root root 140 Aug 21 02:42 . drwxr-xr-x 154 root root 3580 Aug 21 02:42 .. lrwxrwxrwx 1 root root 26 Nov 14 2011 commands-pl.txt - ../../ekg2/commands-pl.txt lrwxrwxrwx 1 root root 25 Nov 14 2011 session-en.txt - ../../ekg2/session-en.txt lrwxrwxrwx 1 root root 25 Nov 14 2011 session-pl.txt - ../../ekg2/session-pl.txt lrwxrwxrwx 1 root root 22 Nov 14 2011 vars-en.txt - ../../ekg2/vars-en.txt lrwxrwxrwx 1 root root 22 Nov 14 2011 vars-pl.txt - ../../ekg2/vars-pl.txt # ls -lad /usr/share/doc/ekg2 drwxr-xr-x 2 root root 140 Aug 21 02:42 /usr/share/doc/ekg2 Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685470: xmess-x,xmess-sdl: missing copyright file after squeeze-wheezy upgrade
Package: xmess-x,xmess-sdl Version: 0.146-2 Severity: serious Justification: Policy 12.5 User: debian...@lists.debian.org Usertags: piuparts Hi, during an experimental test with piuparts I noticed that the copyright file of your package sis missing after an upgrade from squeeze to wheezy. Cheers, Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674324: ruby-net-sftp: FTBFS: test failed - confirm
I was able to reproduce this bug today in my machine Debian Sid, amd64 /-\ ... Finished in 2834.900157 seconds. 1) Failure: test_from_buffer_should_correctly_parse_buffer_and_return_attribute_object(Protocol::V04::TestAttributes) [./protocol/04/test_attributes.rb:15:in `test_from_buffer_should_correctly_parse_buffer_and_return_attribute_object' /usr/lib/ruby/vendor_ruby/mocha/integration/test_unit/ruby_version_186_and_above.rb:22:in `__send__' /usr/lib/ruby/vendor_ruby/mocha/integration/test_unit/ruby_version_186_and_above.rb:22:in `run']: 9 expected but was 5. 2) Failure: test_from_buffer_should_correctly_parse_buffer_with_attribute_subset_and_return_attribute_object(Protocol::V04::TestAttributes) [./protocol/04/test_attributes.rb:47:in `test_from_buffer_should_correctly_parse_buffer_with_attribute_subset_and_return_attribute_object' /usr/lib/ruby/vendor_ruby/mocha/integration/test_unit/ruby_version_186_and_above.rb:22:in `__send__' /usr/lib/ruby/vendor_ruby/mocha/integration/test_unit/ruby_version_186_and_above.rb:22:in `run']: 1 expected but was 5. 3) Failure: test_parse_name_packet_should_use_correct_name_class(Protocol::V04::TestBase) [./protocol/04/test_base.rb:25:in `test_parse_name_packet_should_use_correct_name_class' /usr/lib/ruby/vendor_ruby/mocha/integration/test_unit/ruby_version_186_and_above.rb:22:in `__send__' /usr/lib/ruby/vendor_ruby/mocha/integration/test_unit/ruby_version_186_and_above.rb:22:in `run']: 493 expected but was 16777217. 4) Failure: test_parse_name_packet_should_use_correct_name_class(Protocol::V05::TestBase) [./protocol/04/test_base.rb:25:in `test_parse_name_packet_should_use_correct_name_class' /usr/lib/ruby/vendor_ruby/mocha/integration/test_unit/ruby_version_186_and_above.rb:22:in `__send__' /usr/lib/ruby/vendor_ruby/mocha/integration/test_unit/ruby_version_186_and_above.rb:22:in `run']: 493 expected but was 16777217. 5) Failure: test_from_buffer_should_correctly_parse_buffer_and_return_attribute_object(Protocol::V06::TestAttributes) [./protocol/06/test_attributes.rb:9:in `test_from_buffer_should_correctly_parse_buffer_and_return_attribute_object' /usr/lib/ruby/vendor_ruby/mocha/integration/test_unit/ruby_version_186_and_above.rb:22:in `__send__' /usr/lib/ruby/vendor_ruby/mocha/integration/test_unit/ruby_version_186_and_above.rb:22:in `run']: 9 expected but was 5. 6) Failure: test_from_buffer_should_correctly_parse_buffer_with_attribute_subset_and_return_attribute_object(Protocol::V06::TestAttributes) [./protocol/06/test_attributes.rb:51:in `test_from_buffer_should_correctly_parse_buffer_with_attribute_subset_and_return_attribute_object' /usr/lib/ruby/vendor_ruby/mocha/integration/test_unit/ruby_version_186_and_above.rb:22:in `__send__' /usr/lib/ruby/vendor_ruby/mocha/integration/test_unit/ruby_version_186_and_above.rb:22:in `run']: 1 expected but was 5. 7) Failure: test_parse_name_packet_should_use_correct_name_class(Protocol::V06::TestBase) [./protocol/04/test_base.rb:25:in `test_parse_name_packet_should_use_correct_name_class' /usr/lib/ruby/vendor_ruby/mocha/integration/test_unit/ruby_version_186_and_above.rb:22:in `__send__' /usr/lib/ruby/vendor_ruby/mocha/integration/test_unit/ruby_version_186_and_above.rb:22:in `run']: 493 expected but was 16777217. 418 tests, 1059 assertions, 7 failures, 0 errors ... /\ -- Josué M. Abarca S. Vos mereces Software Libre. PGP key 4096R/70D8FB2A 2009-06-17 Huella de clave = B3ED 4984 F65A 9AE0 6511 DAF4 756B EB4B 70D8 FB2A -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
