Bug#685087: kernel panic in tcp_v4_err() on icmp unreachable
On Mon, Aug 20, 2012 at 02:45:47AM +0100, Ben Hutchings wrote: On Thu, 2012-08-16 at 18:17 +0200, Carsten Wolff wrote: Source: linux-2.6 Version: 2.6.32-45 Hi, we hit the above kernel panic twice in two days. There is a bugfix in upstream stable, but it did not make it to 2.6.32, just later kernels: http://git.kernel.org/?p=linux/kernel/git/davem/net- next.git;a=commit;h=8f49c2703b33519aaaccc63f571b465b9d2b3a2d David, is there any reason why this shouldn't be backported to 2.6.32, or might need adjustment? It originally went into 2.6.37 and was then backported to 2.6.{34,35,36}. David already told me he didn't have time to maintain fixes for 2.6.32, which I can understand considering the number of stable branches now. However I usually backport fixes from 3.0 so in general I have all the required fixes. I don't have this fix in my queue right now, so I'm adding it now. Thanks for letting me know! Willy -- To UNSUBSCRIBE, email to debian-bugs-dist-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
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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685352: duplicity: follows symlink to check for file specified with --exclude-if-present
Package: duplicity Version: 0.6.18-2 Severity: normal My firefox profile directory is a symlink to an encfs mount point: [23+0]~$ ls -l .mozilla/firefox/ total 8 drwxr-xr-x 5 itz itz 4096 Jul 21 23:00 failsafe lrwxrwxrwx 1 itz itz 29 Feb 18 2012 firefox-profile - ../../Private/firefox-profile -rw-r--r-- 1 itz itz 167 Jun 1 17:45 profiles.ini [24+0]~$ mount | grep encfs encfs on /home/itz/Private/firefox-profile type fuse.encfs (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000,default_permissions) encfs is a fuse based filesystem, so that means everything under firefox-profile is inaccessible to other users, including root. When I give the --exclude-if-present option to duplicity, it tries to locate that file underneath the symlink, even if --exclude-other-filesystems is given as well. Leading to disaster: [110+0]~# duplicity --encrypt-key C6FF61AD --use-agent --exclude-other-filesystems --exclude-if-present .nobup --name 'matica!home!itz' /home/itz ssh://foolinux.lan/duplicity Local and Remote metadata are synchronized, no sync needed. Last full backup date: none No signatures found, switching to full backup. Traceback (most recent call last): File /usr/bin/duplicity, line 1404, in module with_tempdir(main) File /usr/bin/duplicity, line 1397, in with_tempdir fn() File /usr/bin/duplicity, line 1372, in main full_backup(col_stats) File /usr/bin/duplicity, line 502, in full_backup globals.backend) File /usr/bin/duplicity, line 380, in write_multivol globals.gpg_profile, globals.volsize) File /usr/lib/python2.7/dist-packages/duplicity/gpg.py, line 320, in GPGWriteFile data = block_iter.next(min(block_size, bytes_to_go)).data File /usr/lib/python2.7/dist-packages/duplicity/diffdir.py, line 507, in next result = self.process(self.input_iter.next(), size) File /usr/lib/python2.7/dist-packages/duplicity/diffdir.py, line 188, in get_delta_iter for new_path, sig_path in collated: File /usr/lib/python2.7/dist-packages/duplicity/diffdir.py, line 281, in collate2iters for relem1 in riter1: File /usr/lib/python2.7/dist-packages/duplicity/selection.py, line 175, in Iterate subpath, val = diryield_stack[-1].next() File /usr/lib/python2.7/dist-packages/duplicity/selection.py, line 155, in diryield s = self.Select(new_path) File /usr/lib/python2.7/dist-packages/duplicity/selection.py, line 209, in Select result = sf(path) File /usr/lib/python2.7/dist-packages/duplicity/selection.py, line 509, in exclude_sel_func if path.append(filename).exists(): File /usr/lib/python2.7/dist-packages/duplicity/path.py, line 516, in append return self.__class__(self.base, self.index + (ext,)) File /usr/lib/python2.7/dist-packages/duplicity/path.py, line 496, in __init__ self.setdata() File /usr/lib/python2.7/dist-packages/duplicity/path.py, line 501, in setdata self.stat = os.lstat(self.name) OSError: [Errno 13] Permission denied: '/home/itz/.mozilla/firefox/firefox-profile/.nobup' duplicity should only check for the presence of --exclude-if-present file under real directories, and not under symlinks to directories. It should also skip this check if --exclude-other-filesystems is given as well and the directory is a mountpoint. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.4.9-custom (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages duplicity depends on: ii libc6 2.13-33 ii librsync1 0.9.7-9 ii python 2.7.3~rc2-1 ii python-gnupginterface 0.3.2-9.1 ii python2.7 2.7.3~rc2-2.1 Versions of packages duplicity recommends: ii python-paramiko 1.7.7.1-3 ii rsync3.0.9-3 Versions of packages duplicity suggests: ii lftp 4.3.6-1 ii ncftp 2:3.2.5-1.1 pn python-botonone pn python-cloudfiles none pn python-gdata none ii python-pexpect 2.4-1 pn tahoe-lafs none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-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#685249: qmf-tool doesn't start: ImportError: No module named cqpid / Failed: TypeError - __init__() takes at most 2 arguments (3 given)
Hmm. I'm wondering, why there's no 0.16-1 in the archives. Maybe I missed to upload it. That's more or less bad. Will update to 0.16-1 and a 0.14-2 for wheezy. Am 18.08.2012 22:17, schrieb Jakub Wilk: Package: qpid-tools Version: 0.14-1 Severity: important If python-cqpid is not installed, qmf-tool doesn't start: $ qmf-tool Traceback (most recent call last): File /usr/bin/qmf-tool, line 31, in module import cqpid ImportError: No module named cqpid If python-cqpid is installed... qmf-tool doesn't start either: $ qmf-tool Failed: TypeError - __init__() takes at most 2 arguments (3 given) (Disclaimer: I have no idea what is the purpose of qmf-tool. I discovered that it doesn't work by running some semi-automatic tests.) -- 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 qpid-tools depends on: ii python 2.7.3-2 ii python-cqmf20.16-7 ii python-qmf2 0.16-7 ii python-qpid 0.16-1 ii python-qpid-extras-qmf 0.16-1 ii python-setuptools 0.6.24-1 ii python2.7 2.7.3-3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685342: iceweasel: [regression] Provides low-resolution icon to the window manager
On Sun, Aug 19, 2012 at 07:24:00PM -0400, Andreas Kloeckner wrote: Package: iceweasel Version: 14.0.1-2 Severity: minor Dear Maintainer, when I use Alt-Tab to switch between applications in Gnome Shell, the icon for Iceweasel used to be nice and high-resolution, but with the upgrade to 14.x it reverted to looking a low-res pixelated mess. I know that this is certainly the most important bug on the planet, but I'd appreciate a fix nonetheless. :) I think this is due to https://bugzilla.mozilla.org/show_bug.cgi?id=776325 which will be fixed in version 15, in a couple weeks. You can give a try to a beta on http://mozilla.debian.net. Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-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
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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685354: unblock: sendfile/2.1b.20080616-5.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package sendfile The RC bug #668721 was fixed in NMU and the package should migrate to testing. Thanks for your work on Debian release Andreas. unblock sendfile/2.1b.20080616-5.1 -- System Information: Debian Release: 6.0.5 Architecture: i386 (i686) Kernel: Linux 2.6.36-xenU-4814-i386 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685355: KeyError: 'CODENAME'
Package: unattended-upgrades Version: 0.79.3 Severity: normal I've got this message from Cron for the last three days: | /etc/cron.daily/apt: | Traceback (most recent call last): | File /usr/bin/unattended-upgrade, line 56, in module | DISTRO_CODENAME = lsb_release.get_distro_information()['CODENAME'] | KeyError: 'CODENAME' The last successful run was on Aug 16. A manual execution appears to work without error (see attached). Cheers -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages unattended-upgrades depends on: ii apt0.9.7.4 ii apt-utils 0.9.7.4 ii debconf [debconf-2.0] 1.5.46 ii lsb-base 4.1+Debian7 ii lsb-release4.1+Debian7 ii python 2.7.3-2 ii python-apt 0.8.7 ii ucf3.0025+nmu3 unattended-upgrades recommends no packages. Versions of packages unattended-upgrades suggests: pn bsd-mailx none ii ssmtp [mail-transport-agent] 2.64-7 -- Configuration Files: /etc/apt/apt.conf.d/50unattended-upgrades changed: // Automatically upgrade packages from these origin patterns Unattended-Upgrade::Origins-Pattern { // Codename based matching: // This will follow the migration of a release through different // archives (e.g. from testing to stable and later oldstable). // o=Debian,n=squeeze; // o=Debian,n=squeeze-updates; // o=Debian,n=squeeze-proposed-updates; // o=Debian,n=squeeze,l=Debian-Security; // Archive or Suite based matching: // Note that this will silently match a different release after // migration to the specified archive (e.g. testing becomes the // new stable). o=Debian,a=unstable; // o=Debian,a=stable; // o=Debian,a=stable-updates; // o=Debian,a=proposed-updates; origin=Debian,archive=stable,label=Debian-Security; }; // List of packages to not update Unattended-Upgrade::Package-Blacklist { // vim; // libc6; // libc6-dev; // libc6-i686; }; // This option allows you to control if on a unclean dpkg exit // unattended-upgrades will automatically run // dpkg --force-confold --configure -a // The default is true, to ensure updates keep getting installed //Unattended-Upgrade::AutoFixInterruptedDpkg false; // Split the upgrade into the smallest possible chunks so that // they can be interrupted with SIGUSR1. This makes the upgrade // a bit slower but it has the benefit that shutdown while a upgrade // is running is possible (with a small delay) //Unattended-Upgrade::MinimalSteps true; // Install all unattended-upgrades when the machine is shuting down // instead of doing it in the background while the machine is running // This will (obviously) make shutdown slower //Unattended-Upgrade::InstallOnShutdown true; // Send email to this address for problems or packages upgrades // If empty or unset then no email is sent, make sure that you // have a working mail setup on your system. A package that provides // 'mailx' must be installed. E.g. u...@example.com Unattended-Upgrade::Mail root; // Set this value to true to get emails only on errors. Default // is to always send a mail if Unattended-Upgrade::Mail is set //Unattended-Upgrade::MailOnlyOnError true; // Do automatic removal of new unused dependencies after the upgrade // (equivalent to apt-get autoremove) //Unattended-Upgrade::Remove-Unused-Dependencies false; // Automatically reboot *WITHOUT CONFIRMATION* if a // the file /var/run/reboot-required is found after the upgrade //Unattended-Upgrade::Automatic-Reboot false; // Use apt bandwidth limit feature, this example limits the download // speed to 70kb/sec //Acquire::http::Dl-Limit 70; -- debconf information: * unattended-upgrades/enable_auto_updates: true root@frost:~# unattended-upgrade --debug --dry-run Initial blacklisted packages: Starting unattended upgrades script Allowed origins are: ['o=Debian,a=unstable', 'origin=Debian,archive=stable,label=Debian-Security'] Checking: ifupdown ([Origin component:'main' archive:'unstable' origin:'Debian' label:'Debian' site:'http.debian.net' isTrusted:True, Origin component:'' archive:'' origin:'' label:'' site:'ftp.ro.debian.org' isTrusted:False]) Checking: jsvc ([Origin component:'main' archive:'unstable' origin:'Debian' label:'Debian' site:'http.debian.net' isTrusted:True, Origin component:'' archive:'' origin:'' label:'' site:'ftp.ro.debian.org' isTrusted:False]) Checking: libcommons-daemon-java ([Origin component:'main' archive:'unstable' origin:'Debian' label:'Debian' site:'http.debian.net' isTrusted:True, Origin component:'' archive:'' origin:'' label:'' site:'ftp.ro.debian.org' isTrusted:False])
Bug#459219: android-tools packaging
W dniu 15.08.2012 20:48, Laszlo Boszormenyi (GCS) pisze: On Wed, 2012-08-15 at 16:07 +0200, Adnan Hodzic wrote: On Tue, Aug 14, 2012 at 8:01 PM, Laszlo Boszormenyi (GCS) g...@debian.hu wrote: I think this ITP should be several ones. One for command like tools like adb , one for Eclipse plugin and one for the emulator at least. I never looked too much at Android SDK structure - have it installed on one machine but then decided to create android-tools package cause I was mainly using adb and fastboot commands. ATM Adnan's work is great. I'm a DD and just changed bits in his packaging to be perfect. Thank you for appreciating my work. Which bits did you change because I don't see any chances in the code. I've my own package, not yet uploaded to anywhere. Attached a diff what I've changed. I was wrong by the way, it's Marcin who made a very good package of android-tools. He tries to outsmart debhelper and do some parts by hand. It's not needed, just show debhelper where it can find the files. Also, install manpage as is, not with the binary. Thanks for deb.diff - I am too used to debhelper 7 where all steps were present in debian/rules ;) I would be happy to maintain android-tools with him or me for Debian and he is for Ubuntu but with the same package base. I plan to apply for DM soon so we could co-maintain it in Debian and just request syncs in Ubuntu. But decided to first get some packages sponsored otherwise it would does not have sense. Also why do you think we should separate them in couple of pieces instead of having the installer which could let you select which pieces you want and which you don't? I personally would like to have it all in a single package, thus why I started working on this installer. But you are fetching binaries so I do not think that it may end in 'main' part of Debian. Not to mention lack of support for architectures other then i386/amd64 which mean no adb/fastboot for my Efika MX Smartbook (which runs armhf). May add more CLI tools to android-tools package, but currently it seems to be a good start. Adding more tools is in TODO - so far users of package does not requested other ones. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#456165: Show stopers for handbreak in debian ?
Hello, I have great interest in seeing handbreak in debian, From the bug, I can read that there were missing dup/dup_free functions in libdvdnav, they have been merged upstream, and are available in the current libdvdnav package in debian. the other issue seemed to be the mkvparse package, that is now in too. what is missing to push handbreak into Debian ? Thanks for you great effort ! -- Niv Sardi -- Free Software hacker hacktivist pgp0L7erc7rNg.pgp Description: PGP signature
Bug#685356: quotatool: Quota reporting on XFS filesytsems is broken. Upstream repository has fix.
Package: quotatool Version: 1.4.12-1 Severity: important Tags: upstream Dear Maintainer, The current version of repquota is broken, as found by xfstests test 219. This is a regression introduced since the upstream 4.00-pre release. This upstream commit fixes the problem: http://linuxquota.git.sourceforge.net/git/gitweb.cgi?p=linuxquota/linuxquota;a=commit;h=6ba6546dd167297cb9ed69d0257ee245b0faea47 repquota: Fix reporting for XFS Conversion to generic quota scanning introduced a bug for XFS where we stopped scanning after quotactl reported first error. quotactl for XFS however reports ENOENT when it has nothing to report for a particular user / group and we shouldn't stop scanning after that. We tried to test for this but the test was wrong. Fix it. Essentially, without the above commit, repquota is broken to the point of being useless on XFS filesystems - it will stop reporting quotas as soon as a user/group ID is found that has no quota associated with it (i.e. daemon, bin, etc). -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.4-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages quotatool depends on: ii libc6 2.13-34 Versions of packages quotatool recommends: ii quota 4.00-4 quotatool suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-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-dist-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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685357: unblock: beast-mcmc/1.6.2-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package beast-mcmc There was some longish discussion about unfreezing beast-mcmc which was blocked due to some misbeaviour of new queue which created binary versions of architectures that never should have been happened[1]. Thanks to ftpmaster this issue was finally settled[2] and I wonder whether you might consider to unblock beast-mcmc. [1] http://lists.debian.org/debian-release/2012/07/msg00878.html [2] http://qa.debian.org/excuses.php?package=beast-mcmc unblock beast-mcmc/1.6.2-3 -- System Information: Debian Release: 6.0.5 Architecture: i386 (i686) Kernel: Linux 2.6.36-xenU-4814-i386 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668081: ITP: wmcore -- a dockapp that shows the usage of each core in the system.
On 08/04/2012 19:55, bitman wrote: Package: wnpp Severity: wishlist Owner: bitman bit...@bitmania.de * Package name: wmcore Version : 0.0.2 Upstream Author : bitman bit...@bitmania.de * URL : http://www.bitmania.de * License : GPL Programming Lang: C Description : a dockapp that shows the usage of each core in the system. The dockapp splits into two displays, the upper one showing the common usage of the system and the lower display showing one graph per each core. It detects the number of cores and computes the usage to be represented as a bar graph. wmcore works with a variable number of cores, the display is tested with 1 up to 16 (simulated) cores. Hi, is anybody using this dockapp? Bitman, what do you think about move your application to the dockapps repository (http://repo.or.cz/w/dockapps.git/)? Bitman, I am not using this dockapp, therefore packaging it is not good idea for me. Probably more people at wmaker-dev or wmaker-user can help you to package it. Else, if you are using debian, probably you can package this application (is easy, is a small application), I can help you. Best regards, kix -- ||// //\\// Rodolfo kix Garcia ||\\// //\\ http://www.kix.es/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685315: [python-django] upgrade to 1.4.1-1 fails
Hi, On Sun, 19 Aug 2012, Riccardo Magliocchetti wrote: upgrading django to 1.4.1 does not work here: Something weird is going on then. I have not seen this problem. Preparing to replace python-django 1.4-1 (using .../python-django_1.4.1-1_all.deb) ... Unpacking replacement python-django ... dpkg: error processing /var/cache/apt/archives/python-django_1.4.1-1_all.deb (--unpack): unable to open '/usr/share/pyshared/django/middleware/csrf.py.dpkg-new': No such file or directory Please show me the output of thoses commands: $ find /usr/share/pyshared/django -type l | xargs ls -al $ find /usr/lib/python2.6/dist-packages/ -type l | (while read file; do test -d $file echo $file - $(readlink $file) ; done) $ find /usr/lib/python2.7/dist-packages/ -type l | (while read file; do test -d $file echo $file - $(readlink $file) ; done) See http://raphaelhertzog.com/2011/07/18/deciphering-one-of-dpkg-weirdest-errors-unable-to-open-pathtofoo-dpkg-new/ for some explanations of what might cause the problem. The other directories which might contain csrf.py are: $ dpkg -L python-django|grep csrf /usr/share/pyshared/django/middleware/csrf.py /usr/share/pyshared/django/views/csrf.py /usr/share/pyshared/django/views/decorators/csrf.py /usr/share/pyshared/django/contrib/flatpages/tests/csrf.py /usr/lib/python2.7/dist-packages/django/middleware/csrf.py /usr/lib/python2.7/dist-packages/django/views/csrf.py /usr/lib/python2.7/dist-packages/django/views/decorators/csrf.py /usr/lib/python2.7/dist-packages/django/contrib/flatpages/tests/csrf.py /usr/lib/python2.6/dist-packages/django/middleware/csrf.py /usr/lib/python2.6/dist-packages/django/views/csrf.py /usr/lib/python2.6/dist-packages/django/views/decorators/csrf.py /usr/lib/python2.6/dist-packages/django/contrib/flatpages/tests/csrf.py Does one of those directories point back to /usr/share/pyshared/django/middleware by mistake ? (Note that it might be an ancestor directory involved too) Did you setup some symlinks to replace one of those directories ? Does it fail again if you retry the upgrade? Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-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-dist-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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685358: byzanz: VCS-Git should point to packaging, not upstream repository
Package: byzanz Version: 0.2.2+git22.10.2011-1.3 Severity: minor The VCS-Git field should point to the location of the Version Control System repository used to maintain the given package (devref 6.5.2.2). ATM it's pointing to the upstream sources : VCS-git: git://git.gnome.org/byzanz Please remove this field if the package is not maintained in a VCS. Thanks ! -- Etienne Millon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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-dist-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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685070: unblock: condor/7.8.2~dfsg.1-1
Hi, On Fri, Aug 17, 2012 at 08:36:02AM +0200, Michael Hanke wrote: If you want more specific information, please let me know what you need and I'll get upstream to chime in. This is just a ping. The package would be ready to migrate. Is there anything else you require from me for a migration, or any other information that I could get you? Thanks, Michael -- Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685327: qa.debian.org: report packager on package migration fail
On 20/08/12 at 23:54 +0530, Ritesh Raj Sarraf wrote: Package: qa.debian.org Severity: wishlist When a package is uploaded to unstable, after the 10 day window it automatically migrates to testing. If there are issues (which could be bug reports, or unsatisfied packages, or policy violations), the package does not migrate. It would be helpful that under such scenarios, the packager is sent an email about the migration failure. Hi, While it is not implemented, a nice and fairly easy way to fix that could be to add an RSS feed output on http://udd.debian.org/dmd.cgi ... (patch welcomed) Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684044: unblock: nodejs/0.6.19~dfsg1-4
Hi, As we said repeatedly, we've been avoiding adding new packages to wheezy for a while now. I think that the point that Jonas is trying to make is that NodeJS isn't new, it's only new to wheezy, and only because of the name conflict. The whole node vs. nodejs is not an excuse, let alone a reason, to diverge from the current practice, IMO. I don't think you'd be diverging in this case. Cheers, Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685327: qa.debian.org: report packager on package migration fail
Hi, On Mon, Aug 20, 2012 at 11:54:35PM +0530, Ritesh Raj Sarraf wrote: Package: qa.debian.org Severity: wishlist When a package is uploaded to unstable, after the 10 day window it automatically migrates to testing. If there are issues (which could be bug reports, or unsatisfied packages, or policy violations), the package does not migrate. It would be helpful that under such scenarios, the packager is sent an email about the migration failure. Mail is already sent when a package migrates succesfully, so absence of such mail on the expected time should give you a hint. The situations you describe already grant very likely you have received an RC bug mail describing the problem. You already know an RC bug will prevent your package from migrating, so another mail telling the obvious is just useless IMO. regards, -- Ricardo Mones ~ bash: ./signature: No such file or directory /bin/bash signature.asc Description: Digital signature
Bug#685359: packaging-tutorial: broken gnujump links
Package: packaging-tutorial - Forwarded message from Stéphane Kanschine carx...@hexecho.net - From: Stéphane Kanschine carx...@hexecho.net To: lu...@lucas-nussbaum.net Date: Tue, 14 Aug 2012 18:07:49 +0200 Subject: packaging turorial Salutations Lucas, J'espère que ça va bien depuis le temps. Ton packaging tutorial est bien fait, je l'ai parcouru et éprouvé. Je venais juste te soumettre une correction que tu as peut-être déjà. À la page 68, la version et le lien pour GNUjump ne sont plus disponibles. La version en ligne est maintenant la 1.0.8 et la structure du lien a changé pour : http://ftp.gnu.org/gnu/gnujump/gnujump-1.0.8.tar.gz Numériquement, Stéphane alias carxwol -- Après quelques minutes il lui faut faire demi-tour car son phare s'endort. - End forwarded message - -- To UNSUBSCRIBE, email to debian-bugs-dist-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-dist-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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685361: busybox bunzip2 chokes on some valid inputs (bunzip error -5)
Package: busybox Version: 1:1.17.1-8 Severity: important Example file -- http://www.cpan.org/src/5.0/perl-5.16.1.tar.bz2 Regular bunzip2 decompresses it okay, busybox gives this: $ busybox bzip2 -t perl-5.16.1.tar.bz2 bzip2: bunzip error -5 Filing this under squeeze version number, -- this is an old bug which is still present in 1.20 version. I dunno when it started. The bug is at least important, since it is bad when an archiver can't decompress some random archive, and other stuff start breaking due to this. /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681767: linux-image-3.2.0-3-rt-amd64: irq/23-eth0 high load
On Mon, 20 Aug 2012 04:46:53 +0100 Ben Hutchings b...@decadent.org.uk wrote: On Mon, 2012-07-16 at 10:48 +, Yevgeny Kosarhevsky wrote: Package: src Version: 3.2.21-3 Severity: critical Justification: causes serious data loss What data? My peers reported packet loss. Switching back to 2.6.32 kernel solved the issue. Dear Maintainer, I get a heavy load on irq/23-eth0: 1086 root -51 0 000 S 2.0 0.0 0:31.04 irq/23-eth0 I don't think 2% CPU time is a 'heavy load'. This is only occured after upgrading from 2.6.32 kernel. The LA was 0.00 on previous kernel, now it's 1.44 [...] But you are not comparing like with like. On a real-time kernel, IRQ handlers are scheduled as tasks and are accounted in the load average. On a standard kernel as you were running before, IRQ handlers are accounted separately. So, is there really a problem here? Did you actually mean to install a real-time kernel? Since there was a packet loss, I think there is a problem. I don't know if it's related with [ 1966.544292] NOHZ: local_softirq_pending 08 [ 2108.848600] NOHZ: local_softirq_pending 08 -- Yevgeny Kosarzhevsky phao...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684044: unblock: nodejs/0.6.19~dfsg1-4
On 20.08.2012 08:40, Thomas Goirand wrote: As we said repeatedly, we've been avoiding adding new packages to wheezy for a while now. I think that the point that Jonas is trying to make is that NodeJS isn't new, it's only new to wheezy, and only because of the name conflict. new to wheezy is precisely what new means in the context of adding new packages to wheezy. The whole node vs. nodejs is not an excuse, let alone a reason, to diverge from the current practice, IMO. I don't think you'd be diverging in this case. I think there may have been a misunderstanding somewhere. The current practice is not to add packages which aren't already in wheezy to the release. Unblocking nodejs involves adding a package which isn't already in wheezy to the release. I'm not sure how unblocking it would therefore be anything other than diverging from current practice. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650636: ITP: gephi -- The Open Graph Viz Platform
Hi Vadim, any progress on gephi ITP? Do you need help/sponsoring? If you are no more interested in it, would you care to retitle it as a RFP? Cheers, Luca -- To UNSUBSCRIBE, email to debian-bugs-dist-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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685318: blueman-applet: does not start due to missing icon(s)
Thanks for the report. I suspect something's wrong with your GTK environment. You could start a python console, issue 'import gtk' and check the output of gtk.icon_theme_get_default().list_icons(). It should include all those standard icon names. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683378: CVE-2012-0283
On Sat, Aug 18, 2012 at 11:38:51AM +0200, Tanguy Ortolo wrote: Tanguy Ortolo, 2012-08-17 11:04+0200: I have just had a look to the code: squeeze is affected. I shall prepare an update by hand. Well, after looking more closely, it appears that in fact, it is not. The fix for version 0.0.20120125 in testing does apply to 0.0.20091225 in stable after some modifications, but: 1. it breaks some functionnality; 2. it is useless, because it is meant to cover a use case that did not exist at the time (the code to process the POST argument do=media fo the possible attack is only present in 0.0.20120125). So, sorry for my hesitation with this bug… Thanks, I've updated the Debian security tracker. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670592: ps deprecation url 404
Sami Kerola wrote: Please notice that the 'highly annoying and uncessary' message can be turned off by procps-ng packager with ./configure option '--disable-whining do not print unnecessary warnings (slackware-ism)'. Have you tried it? I doubt it. The #ifdef BUILD_WITH_WHINE conditional compile in proc/ksym.c breaks because of bit rot. And does nobody read Dijkstra these days? Andrew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685362: postgresql-common: server does not listen in ipv6 after install
Package: postgresql-common Version: 134 Severity: normal Tags: ipv6 Dear Maintainer, After a fresh install of amd64 testing with postgresql, the server was not listening on IPv6. This turned out to be due to 1. listen_addresses = 'localhost' in postgresql.conf 2. ::1 ip6-localhost ip6-loopback in etc/hosts i.e. the servers listens on localhost, but localhost is no longer configured to have an IPv6 address. On a debian system postgresql should be listening in both IPv4 and IPv6 out of the box. Best, Simon -- 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/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 postgresql-common depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.44 ii logrotate 3.8.1-4 ii lsb-base 4.1+Debian7 ii postgresql-client-common 134 ii procps1:3.3.3-2 ii ssl-cert 1.0.31 postgresql-common recommends no packages. postgresql-common suggests no packages. -- debconf information: postgresql-common/obsolete-major: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685363: ITP: impressive-editor -- Editor for Impressive presentation tool
Package: wnpp Severity: wishlist Owner: Yao Wei (魏銘廷) m...@lxde.org * Package name: impressive-editor Version : 0.0.1 Upstream Author : Yao Wei (魏銘廷) m...@lxde.org * URL : https://github.com/medicalwei/impressive-editor * License : GPL-2 Programming Lang: Python Description : Editor for Impressive presentation tool This is my personal project. Impressive is a convenient presentation tool, but it must use command line to launch and is very difficult to configure slides. I was asked by a Impressive user to make this frontend, and they want to pack this application to their educational distro (named EzGo) based on Ubuntu. Thanks, Yao Wei -- To UNSUBSCRIBE, email to debian-bugs-dist-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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685365: mpd: init script shows start-create-db in help message, but does not support it
Package: mpd Version: 0.16.7-2 Severity: normal Dear Maintainer, The help output for /etc/init.d/mpd includes the start-create-db action: root@twin:/var/lib/mpd/music# /etc/init.d/mpd --help Usage: /etc/init.d/mpd {start|start-create-db|stop|restart|force-reload} However trying to execute it only prints the help again: root@twin:/var/lib/mpd/music# /etc/init.d/mpd start-create-db Usage: /etc/init.d/mpd {start|start-create-db|stop|restart|force-reload} Indeed /etc/init.d/mpd contains no mention of start-create-db other than the help output. It's probably a left-over and should be removed to avoid confusion. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mpd depends on: ii adduser 3.113+nmu3 ii libao41.1.0-2 ii libasound21.0.25-4 ii libaudiofile1 0.3.4-1 ii libavahi-client3 0.6.31-1 ii libavahi-common3 0.6.31-1 ii libavahi-glib10.6.31-1 ii libavcodec53 6:0.8.3-6 ii libavformat53 [libavformat-extra-53] 6:0.8.3-6 ii libavutil51 [libavutil-extra-51] 6:0.8.3-6 ii libc6 2.13-35 ii libcurl3-gnutls 7.26.0-1 ii libfaad2 2.7-8 ii libflac8 1.2.1-6 ii libgcc1 1:4.7.1-2 ii libglib2.0-0 2.32.3-1 ii libid3tag00.15.1b-10 ii libjack0 [libjack-0.116] 1:0.121.3+20120418git75e3e20b-2 ii libmad0 0.15.1b-7 ii libmikmod23.1.12-4 ii libmms0 0.6.2-3 ii libmp3lame0 3.99.5+repack1-3 ii libmpcdec62:0.1~r459-4 ii libogg0 1.3.0-4 ii libpulse0 2.0-6 ii libsamplerate00.1.8-5 ii libshout3 2.2.2-8 ii libsqlite3-0 3.7.13-1 ii libstdc++64.7.1-2 ii libvorbis0a 1.3.2-1.3 ii libvorbisenc2 1.3.2-1.3 ii libvorbisfile31.3.2-1.3 ii libwavpack1 4.60.1-3 ii lsb-base 4.1+Debian7 ii zlib1g1:1.2.7.dfsg-13 mpd recommends no packages. Versions of packages mpd suggests: ii avahi-daemon 0.6.31-1 pn icecast2 none ii ncmpcpp [mpd-client] 0.5.10-1 pn pulseaudionone -- Configuration Files: /etc/mpd.conf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685348: org-mode: wrong indentation with auto-fill within lists
Hi Luis, could you please follow this up directly on the org-mode mailing list ? http://thread.gmane.org/gmane.emacs.orgmode/59078 Cheers, --Seb On Aug/19, Luis Mochan wrote: Package: org-mode Version: 7.8.11-1 Severity: normal When I start a list like * List 1. a very long item 1, so long that it reaches into the right margin 2. item 2 and I have auto-fill-mode turned on, the first item is split into two or more lines as * List 1. a very long item 1, so long that it reaches into the right margin 2. item 2 The problem is that the second line of the first item is no longer part of the list! I expected the line to be split with additional spaces as * List 1. a very long item 1, so long that it reaches into the right margin 2. item 2 so that item 1 is an ordinary item with two lines. This is annoying, as it is not easy (or I haven't found yet) a simple way to indent correctly that second line. A simple TAB doesn't work, so I have to move to the beginning of the line and add a couple of spaces. Furthermore, this used to work with emacs-23 and its support for org-mode until I installed the package org-mode. (I installed the package to get the info documentation). Sorry if this is not a bug and this odd behavior can be configured away, but I couldn't find how. Thanls and regards, Luis Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (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 org-mode depends on: ii dpkg 1.16.4.3 ii emacs23 23.4+1-3 ii install-info 4.13a.dfsg.1-10 org-mode recommends no packages. Versions of packages org-mode suggests: pn ditaanone pn easypg none pn remember-el none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675360: hello
-- Hello my dear, How are you today? I hope fine. From miss Miranda.
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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#662639: gnome-shell: frequent lockups on hardware accelerated actions
Confirmed with 3.4.2-1. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685327: qa.debian.org: report packager on package migration fail
On Monday 20 August 2012 01:18 PM, Ricardo Mones wrote: Mail is already sent when a package migrates succesfully, so absence of such mail on the expected time should give you a hint. The situations you describe already grant very likely you have received an RC bug mail describing the problem. You already know an RC bug will prevent your package from migrating, so another mail telling the obvious is just useless IMO. It won't hurt to receive an extra email. No. Migration blockages are not always due to RC bugs. I filed this report because I got hit by this. My package, open-iscsi, was blocked because its dependent package, scsi-modules provided by the kernel, recently stopped building on all architectures. For this situation, I never got an email. So, please, if it can be done, it'll be good. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#612944: testing/virt-manager/d-bus/xming/
I have a similar problem. (virt-manager:3025): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-TFwAzA7png: Verbindungsaufbau abgelehnt - virt-manager cant find the d-bus daemon, which is running - is looking in the wrong directory (/tmp) for the socket (/var/run) quickfix: restarting Xming seems to help dbus-launch --exit-with-session virt-manager -- To UNSUBSCRIBE, email to debian-bugs-dist-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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685368: Upload of scim-tables to testing-proposed-update
Package: release.debian.org Severity: normal Greetings Release Team, I'm writing to you as I would like your approval to upload scim-tables package to testing-proposed-update in order to fix bug #684835. The main change is a new patch to fix the FTBFS, others include the updates of debhelper related files, compat file, debian-standard-version, etc. Please find the relevant diff here: https://github.com/tzhuan/scim-tables-debain-0.5.9/compare/master...0.5.9-2 Best regards, Tz-Huan -- 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/4 CPU cores) Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to zh_TW.UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685367: installation-report: Wheezy beta installed on powermac g4 900 MHz w/ ATI rage graphicscard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.47 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** - -- Package-specific info: Boot method: CD Image version: imagename Date: Date and time of the install Machine: powermac g4 900 MHz Partitions: df -Tl will do; the raw partition table is preferred Automatic Partitioning was used, using the whole 40 GB Harddisk, putting all files into a single / partition with the xfs filesystem. More detailed partitioning-information is going to be given before long. Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [o] Detect network card:[o] Configure network: [o] Detect CD: [o] Load installer modules: [o] Clock/timezone setup: [o] User/password setup:[o] Detect hard drives: [o] Partition hard drives: [o] Install base system:[o] Install tasks: [o] Install boot loader:[o] Overall install:[ ] w/out x-server Comments/Problems: The Installation went OK, but the graphical XFCE-Desktop was not usable, because the x-server was not workable. I actually had to start the system with the yaboot-command-line 'Linux init 1' to get a usable VT, once lightdm was installed. Else, when trying to start the x-server, there was just pixel-mud displayed in the lower half of the screen, the system froze. I tried x-autoconfiguration with 'X -configure' in the /etc/X11/ directory in single user mode, but this did not change the situation, doing manual alterations to xorg.conf did not change the situation either. So I attach the xorg.conf-file, I tried, too. Probably this is going to be reported against the r128 x-video-driver. X-logfiles are going to be included in the repoert then, as soon as I tried more detailed manual X-configuration and hat a look at Xorg.0.log myself. There are several option that might work, contained in the autogenerated xorg.conf -file. It might also be worth a try, using the framebuffer-device instead of r128. - -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=7.0 (wheezy) - installer build 20120712 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux g4b 3.2.0-3-powerpc #1 Thu Jun 28 10:24:24 UTC 2012 ppc GNU/Linux lspci -knn: :00:0b.0 Host bridge [0600]: Apple Inc. UniNorth 1.5 AGP [106b:002d] lspci -knn: Kernel driver in use: agpgart-uninorth lspci -knn: :00:10.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Rage 128 PF/PRO AGP 4x TMDS [1002:5046] lspci -knn: Kernel driver in use: aty128fb lspci -knn: 0001:10:0b.0 Host bridge [0600]: Apple Inc. UniNorth 1.5 PCI [106b:002e] lspci -knn: 0001:10:17.0 Unassigned class [ff00]: Apple Inc. KeyLargo Mac I/O [106b:0022] (rev 03) lspci -knn:Kernel driver in use: macio lspci -knn: 0001:10:18.0 USB controller [0c03]: Apple Inc. KeyLargo USB [106b:0019] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 0001:10:19.0 USB controller [0c03]: Apple Inc. KeyLargo USB [106b:0019] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 0002:20:0b.0 Host bridge [0600]: Apple Inc. UniNorth 1.5 Internal PCI [106b:002f] lspci -knn: 0002:20:0e.0 FireWire (IEEE 1394) [0c00]: LSI Corporation FW322/323 [TrueFire] 1394a Controller [11c1:5811] lspci -knn: Subsystem: LSI Corporation FW322/323 [TrueFire] 1394a Controller [11c1:5811] lspci -knn: Kernel driver in use: firewire_ohci lspci -knn: 0002:20:0f.0 Ethernet controller [0200]: Apple Inc. UniNorth GMAC (Sun GEM) [106b:0021] (rev 01) lspci -knn: Kernel driver in use: gem usb-list: usb-list: Bus 01 Device 01: OHCI Host Controller [1d6b:0001] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 00 usb-list:Manufacturer: Linux 3.2.0-3-powerpc ohci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 01 Device 02: USB Keyboard [0a81:0101] usb-list:Level 01 Parent 01 Port 00 Class 00(ifc ) Subclass 00 Protocol 00 usb-list:Manufacturer: CHESEN usb-list:Interface 00: Class 03(HID ) Subclass 01 Protocol 01
Bug#672806: fai: unclear NEWS.Debian entry for 4.0
On Fri, 17 Aug 2012 16:37:27 -0700, Jonathan Nieder jrnie...@gmail.com said: makes it crystal clear to sysadmins what immediate action on their part is required. But your proposal is more a link to the changelog. Reading it does not give any practical information what has changed or what needs to be changed. And the changelog is very long and detailed. There I've tried to summaries the important changes from the changelog into this NEWS entry. And because many things haved changed, it was getting longer than NEWS entries in the past. -- regards Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-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-dist-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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685370: snoopy: [INTL:sk] Slovak po-debconf translation
Package: snoopy Severity: wishlist Tags: l10n patch Version: 1.8.0-4 The sk.po attached. regards # Slovak translations for snoopy package # Slovenské preklady pre balík snoopy. # Copyright (C) 2012 THE snoopy'S COPYRIGHT HOLDER # This file is distributed under the same license as the snoopy package. # Automatically generated, 2012. # Slavko li...@slavino.sk, 2012. # msgid msgstr Project-Id-Version: snoopy 1.8.0-4\n Report-Msgid-Bugs-To: mh+debian-packa...@zugschlus.de\n POT-Creation-Date: 2007-02-26 13:12+0100\n PO-Revision-Date: 2012-08-20 11:12+0200\n Last-Translator: Slavko li...@slavino.sk\n Language-Team: slovenčina debian-l10n-slo...@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Language: sk\n Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n=2 n=4) ? 1 : 2;\n X-POFile-SpellExtra: preload etc ld prednačítaná snoopy\n #. Type: boolean #. Description #: ../templates:1001 msgid Install snoopy library to /etc/ld.so.preload? msgstr Nainštalovať knižnicu snoopy do /etc/ld.so.preload? #. Type: boolean #. Description #: ../templates:1001 msgid snoopy is a library that can only reliably do its work if it is mandatorily preloaded via /etc/ld.so.preload. Since this can potentially do harm to the system, your consent is needed. msgstr snoopy je knižnica, ktorá môže robiť svoju prácu spoľahlivo, len ak je povinne prednačítaná pomocou /etc/ld.so.preload. Keďže to potenciálne môže poškodiť systém, je potrebný váš súhlas.
Bug#685368: Upload of scim-tables to testing-proposed-update
On 20.08.2012 10:49, Tz-Huan Huang wrote: I'm writing to you as I would like your approval to upload scim-tables package to testing-proposed-update in order to fix bug #684835. I assume because of the new upstream version already in unstable? The main change is a new patch to fix the FTBFS, That sounds like it should be fine, but we'd need to see the patch to be sure. others include the updates of debhelper related files, compat file, debian-standard-version, etc. These, otoh, aren't really appropriate changes to be making during a freeze, particularly for an upload via t-p-u. If any of them are required to fix the RC bug then they might be okay, but again we'd need to see the diff. Please find the relevant diff here: https://github.com/tzhuan/scim-tables-debain-0.5.9/compare/master...0.5.9-2 Please could you attach a source debdiff between the package currently in testing and the proposed t-p-u upload to this bug report? It makes it much easier to track, and more transparent, as to exactly what was approved for upload. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685327: qa.debian.org: report packager on package migration fail
On Tue, Aug 21, 2012 at 2:24 AM, Ritesh Raj Sarraf wrote: When a package is uploaded to unstable, after the 10 day window it automatically migrates to testing. If there are issues (which could be bug reports, or unsatisfied packages, or policy violations), the package does not migrate. It would be helpful that under such scenarios, the packager is sent an email about the migration failure. I would think this is something for the release team's scripts. I asked about it on the IRC channel of the release team and was told that you should just run this in crontab `grep-excuses 'Ritesh Raj Sarraf'`. I guess this bug should just be closed. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685371: mod-mono: [INTL:sk] Slovak po-debconf translation
Package: mod-mono Severity: wishlist Tags: l10n patch Version: 2.10-3.1 The sk.po attached. regards # Slovak translations for mod-mono package # Slovenské preklady pre balík mod-mono. # Copyright (C) 2012 THE mod-mono'S COPYRIGHT HOLDER # This file is distributed under the same license as the mod-mono package. # Automatically generated, 2012. # Slavko li...@slavino.sk, 2012. # msgid msgstr Project-Id-Version: mod-mono 2.10-3.1\n Report-Msgid-Bugs-To: mod-m...@packages.debian.org\n POT-Creation-Date: 2011-03-20 23:00+\n PO-Revision-Date: 2012-08-20 12:24+0200\n Last-Translator: Slavko li...@slavino.sk\n Language-Team: slovenčina debian-l10n-slo...@lists.debian.org\n Language: sk\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n=2 n=4) ? 1 : 2;\n X-POFile-SpellExtra: NET libapache2-mod-mono mod-mono-server4\n X-POFile-SpellExtra: mod-mono-server2\n #. Type: select #. Description #: ../libapache2-mod-mono.templates:2001 msgid Mono server to use: msgstr Použitý server mono: #. Type: select #. Description #: ../libapache2-mod-mono.templates:2001 msgid The libapache2-mod-mono module can be used with one of two different Mono ASP.NET backends:\n - mod-mono-server2: implements ASP.NET 2.0 features;\n - mod-mono-server4: implements ASP.NET 4.0 features. msgstr Modul libapache2-mod-mono možno použiť s jedným z dvoch rôznych riešení Mono ASP.NET:\n - mod-mono-server2: implementuje vlastnosti ASP.NET 2.0;\n - mod-mono-server4: implementuje vlastnosti ASP.NET 4.0.
Bug#685327: qa.debian.org: report packager on package migration fail
On Mon, Aug 20, 2012 at 03:03:33PM +0530, Ritesh Raj Sarraf wrote: On Monday 20 August 2012 01:18 PM, Ricardo Mones wrote: Mail is already sent when a package migrates succesfully, so absence of such mail on the expected time should give you a hint. The situations you describe already grant very likely you have received an RC bug mail describing the problem. You already know an RC bug will prevent your package from migrating, so another mail telling the obvious is just useless IMO. It won't hurt to receive an extra email. That's just because you still don't receive enough. Not everybody is so lucky ;) No. Migration blockages are not always due to RC bugs. I filed this report because I got hit by this. My package, open-iscsi, was blocked because its dependent package, scsi-modules provided by the kernel, recently stopped building on all architectures. For this situation, I never got an email. So, please, if it can be done, it'll be good. Sure, and not receiving it 10 days after uploading should have been a hint something was wrong, as said. Anyway that's a matter of preferences. As long as implementation is opt-in only it will be good. regards, -- Ricardo Mones ~ Physics is like sex: sure, it may give some practical results, but that's not why we do it.Richard Feynman signature.asc Description: Digital signature
Bug#672806: fai: unclear NEWS.Debian entry for 4.0
Thomas Lange wrote: On Fri, 17 Aug 2012 16:37:27 -0700, Jonathan Nieder jrnie...@gmail.com said: makes it crystal clear to sysadmins what immediate action on their part is required. But your proposal is more a link to the changelog. Reading it does not give any practical information what has changed or what needs to be changed. Sorry for the lack of clarity. My example was probably lacking because I lack a deep enough understanding of fai to make a good summary. Better to list requirements, I guess. Please do: * Tell the sysadmin exactly what they need to do. Be specific. Please do not: * List every change, or even every important change. That is what reference documentation is for. * Assume that the sysadmin knows something. A sysadmin might have installed fai for the sake of a specific user and not know anything about it personally. The instructions in NEWS.Debian.gz should be clear enough for the sysadmin to know what needs to be done and hence who needs to be contacted. [...] There I've tried to summaries the important changes from the changelog into this NEWS entry. That's a noble cause, but it's not what NEWS.Debian.gz is for. NEWS.Debian.gz is shown and emailed to the sysadmin by apt-listchanges and meant to deliver specific advice about immediate action required due to the upgrade. A separate NEWS.gz file would be nice, and then the NEWS.Debian.gz could point to that. Or the changelog would be fine, in my opinion. Hoping that clarifies, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685372: nap: [INTL:sk] Slovak po-debconf translation
Package: nap Severity: wishlist Tags: l10n patch Version: 1.5.4-5 The sk.po attached. regards # Slovak translations for nap package # Slovenské preklady pre balík nap. # Copyright (C) 2012 THE nap'S COPYRIGHT HOLDER # This file is distributed under the same license as the nap package. # Automatically generated, 2012. # Slavko li...@slavino.sk, 2012. # msgid msgstr Project-Id-Version: nap 1.5.4-5\n Report-Msgid-Bugs-To: n...@packages.debian.org\n POT-Creation-Date: 2008-08-16 18:52-0300\n PO-Revision-Date: 2012-08-20 12:32+0200\n Last-Translator: Slavko li...@slavino.sk\n Language-Team: slovenčina debian-l10n-slo...@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Language: sk\n Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n=2 n=4) ? 1 : 2;\n #. Type: boolean #. Description #: ../templates:1001 msgid Do you want napping to be installed setuid? msgstr Chcete aby bol napping nainštalovaný so setuid? #. Type: boolean #. Description #: ../templates:1001 msgid The napping executable, which is responsible for collecting ping results for nap, can be installed with the set-user-id bit set, so that it will be able to open a raw network socket required to send ping packets. msgstr Spustiteľný súbor, ktorý sa stará o zhromažďovanie výsledkov ping pre nap, môže byť nainštalovaný s nastaveným príznakom set-user-id, takže bude môcť otvárať sieťové sokety, potrebné na posielanie paketov ping. #. Type: boolean #. Description #: ../templates:1001 msgid Enabling this feature may be a security risk, so it is disabled by default. If in doubt, it is suggested that you leave it disabled. msgstr Zapnutie tejto možnosti môže byť bezpečnostným rizikom, preto je predvolene vypnutá. Ak neviete, čo to znamená, odporúčame ponechať ju vypnutú.
Bug#685374: gom: [INTL:sk] Slovak po-debconf translation
Package: gom Severity: wishlist Tags: l10n patch Version: 0.30.2-5.1 The sk.po attached. regards # Slovak translations for gom package # Slovenské preklady pre balík gom. # Copyright (C) 2012 THE gom'S COPYRIGHT HOLDER # This file is distributed under the same license as the gom package. # Slavko li...@slavino.sk, 2012. # msgid msgstr Project-Id-Version: gom 0.30.2-5.1\n Report-Msgid-Bugs-To: abs...@debian.org\n POT-Creation-Date: 2007-02-16 18:44+0100\n PO-Revision-Date: 2012-08-20 12:41+0200\n Last-Translator: Slavko li...@slavino.sk\n Language-Team: slovenčina debian-l10n-slo...@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Language: sk\n Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n=2 n=4) ? 1 : 2;\n X-POFile-SpellExtra: gom gomconfig start boot etc init rc root\n #. Type: boolean #. Description #: ../gom.templates:1001 msgid Initialize mixer on system startup? msgstr Inicializovať mixér pri štarte systému? #. Type: boolean #. Description #: ../gom.templates:1001 msgid If you choose this option, \/etc/init.d/gom start\ (on system startup, or if run manually) will set mixer settings to your saved configuration. msgstr Ak si zvolíte túto možnosť, „/etc/init.d/gom start” (pri štarte systému alebo pri manuálnom spustení) načíta nastavenia mixéra z uloženej konfigurácie. #. Type: boolean #. Description #: ../gom.templates:1001 msgid You may use upstream's \gomconfig\ script as root later to fine-tune the settings. msgstr Neskôr môžete na jemné doladenie nastavení použiť skript „gomconfig” ako root. #. Type: boolean #. Description #: ../gom.templates:3001 msgid Remove /etc/gom completely? msgstr Odstrániť úplne /etc/gom? #. Type: boolean #. Description #: ../gom.templates:3001 msgid The /etc/gom directory seems to contain additional local customization files. Please choose whether you want to remove it entirely. msgstr Vyzerá to, že adresár /etc/gom obsahuje dodatočné, lokálne upravené súbory. Prosím, vyberte si, či ich ho chcete úplne odstrániť. #. Type: boolean #. Description #: ../gom.templates:4001 msgid Remove obsoleted /etc/rc.boot/gom? msgstr Odstrániť zastaraný /etc/rc.boot/gom? #. Type: boolean #. Description #: ../gom.templates:4001 msgid The /etc/rc.boot/gom file is obsoleted but might contain local customizations. msgstr Súbor /etc/rc.boot/gom je zastaraný, ale môže obsahovať lokálne úpravy.
Bug#685375: Breaks booting with nfsroot
Package: live-boot Version: 3.0~b1-1 Severity: normal Hi, I'm trying to setup a FAI netbooting environment, which uses live-boot for booting the installation system via NFS. As union filesystem, I'm using overlayfs by using the union=overlayfs kernel commandline parameter. the live-boot scripts all seem to run as expected. However, in the last stage, run-init fails with this error message: run-init: nuking initramfs contents: Directory not empty. Kernel panic - not syncing: Attempted to kill init! [...] By booting with 'break=init', I could verify that /root is fully in place, that is, all bind mounts succeeded. However, a rm -rf /live/overlayfs fails with Device busy. If I manually 'umount /tmp/overlayfs', the boot process continues successfully. While reading the commit logs, I noticed this commit: http://live.debian.net/gitweb?p=live-boot.git;a=commitdiff;h=9dac5b65e0e6aaa9e194ec5e423476c78f6209e5 Laying tmpfs on /live/overlay only during initramfs stage, fixes boot failure with plain filesystems (Closes: #681579). --- diff --git a/scripts/boot/9990-overlay.sh b/scripts/boot/9990-overlay.sh index cb12c4b..00c53c8 100755 --- a/scripts/boot/9990-overlay.sh +++ b/scripts/boot/9990-overlay.sh @@ -155,9 +155,8 @@ setup_unionfs () # tmpfs file systems touch /etc/fstab - mkdir -p /live - mount -t tmpfs tmpfs /live mkdir -p /live/overlay + mount -t tmpfs tmpfs /live/overlay # Looking for persistence devices or files if [ -n ${PERSISTENCE} ] [ -z ${NOPERSISTENCE} ] It seems to me that when you mount the tmpfs in /live/overlay, you need to umount it before booting manually as well, that is, after bind-mounting /live to the final boot location. Cheers, Reinhard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685275: uwsgi-plugin-python: segmentation fault with python26
Hi Boris, Thanks for informations on this issue. I would forward it to the upstream developers, as segmentation faults are certainly not normal. Best, Janos On Sun, Aug 19, 2012 at 7:10 PM, Boris Bobrov breton.li...@gmail.com wrote: В сообщении от Sunday 19 of August 2012 17:29:52 вы написали: severity 685275 normal thanks Hi Boris, [...] The problem was in cache in data/pages/*/cache/. It uses Python byte code and removing it as suggested on [0] helped. [0]: http://moinmo.in/HelpOnUpdatingPython I don't know if it is normal that uwsgi falls with segfault, but my problem is solved. If it is normal, sorry for the false bugreport. -- WBR, Boris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685377: bash-completion: fusermount -u does not complete curlftpfs-mounts
Package: bash-completion Version: 1:2.0-1 Severity: minor Tags: patch Because the filesystem-type of curlftpfs-mount in /etc/mtab is just fuse instead of fuse.curlftp or something like that (cf. sshfs = fuse.sshfs), they are not completed. This patch fixes that. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (900, 'stable'), (600, 'unstable'), (100, 'proposed-updates'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages bash-completion depends on: ii bash 4.2-4 ii dpkg 1.16.4.3 bash-completion recommends no packages. bash-completion suggests no packages. -- no debconf information --- /usr/share/bash-completion/completions/fusermount.orig 2012-06-17 21:09:06.0 +0200 +++ /usr/share/bash-completion/completions/fusermount 2012-08-20 12:37:39.451274139 +0200 @@ -11,7 +11,7 @@ ;; -u) COMPREPLY=( $( compgen -W $( awk \ -'{ if ($3 ~ /^fuse\./) print $2 }' /etc/mtab 2/dev/null ) \ +'{ if ($3 ~ /^fuse(\.|$)/) print $2 }' /etc/mtab 2/dev/null ) \ -- $cur ) ) return 0 ;;
Bug#684931: /usr/share/x11/xkb/symbols/fi: AltGr problem
I actually filed the same bug a couple of years ago, as I recall. The behavior is the same, so no change seems to have taken place. Some debugging notes first. Always try X11 apps first, to see if the problem is with X11. If X11 works, then the problem is with something on top of X11, usually GTK or KDE. The problem with X11 can be with a number of things such as the key symbols .h file, the Compose file, or the actual file for the specific keyboard. In this case, I tried entering U+0111 (Altgr-§-d) with xkb-data version 1.8-2 on debian stable, and xkb-data version 2.5-1ubuntu1.3 on the latest desktop ubuntu. I got the same results on both. If you try X11 (xterm, xev) everything works. Same for KDE (kaffeine et al). If you open gnome-terminal or some other gnome app, you will first get only a plain d. To rule out font problems, paste § to the gnome app. It should show up just fine. The solution is to change to the XIM input method. You can do this from the right mouse button for some apps, but for others you have to fiddle with the input settings globally. Once XIM is set as the input method, you get your Islandic đ. The behavior is obviously still wrong. GTK apps should work without the users having to fiddle with their input method settings. All input methods (at least the default one) should understand all correct input. However, I hope the above demonstrated conclusively that the problem is not with X11 or its configurations. The problem lies with input methods other than XIM when using GTK. Troy -- To UNSUBSCRIBE, email to debian-bugs-dist-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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685378: dpkg: multiarch: Conflict due to different package version while update
Package: dpkg Version: 1.16.8 Severity: important Dear Maintainer, during an update I run into th following situation: ---8--- libqtcore4 : Breaks: libqtcore4:i386 (!= 4:4.8.2-2) but 4:4.8.2-2+b1 is installed libqtcore4:i386 : Breaks: libqtcore4 (!= 4:4.8.2-2+b1) but 4:4.8.2-2 is installed ---8--- Trying to install libqtcore4 by hand results in: ---8--- # LANG=C dpkg -i /var/cache/apt/archives/libqtcore4_4%3a4.8.2-2+b1_amd64.deb (Reading database ... 328035 files and directories currently installed.) Preparing to replace libqtcore4:amd64 4:4.8.2-2 (using .../libqtcore4_4%3a4.8.2-2+b1_amd64.deb) ... Unpacking replacement libqtcore4:amd64 ... dpkg: error processing /var/cache/apt/archives/libqtcore4_4%3a4.8.2-2+b1_amd64.deb (--install): trying to overwrite shared '/usr/share/doc/libqtcore4/changelog.Debian.gz', which is different from other instances of package libqtcore4:amd64 Errors were encountered while processing: /var/cache/apt/archives/libqtcore4_4%3a4.8.2-2+b1_amd64.deb # ---8--- It seems to me, that dpkg is unable to handle the +bX version in a correct manner. For my understanding the version a.b.c+bX should be handled as eaqual to version a.b.c in this case. Regards Bene -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages dpkg depends on: ii libbz2-1.0 1.0.6-4 ii libc62.13-35 ii liblzma5 5.1.1alpha+20120614-1 ii libselinux1 2.1.9-5 ii tar 1.26-4 ii zlib1g 1:1.2.7.dfsg-13 dpkg recommends no packages. Versions of packages dpkg suggests: ii apt 0.9.7.4 -- no debconf information -- Linutronix GmbH Phone: +49 7556 91 98 91; Fax.: +49 7556 91 98 86 Firmensitz: D-88690 Uhldingen, Auf dem Berg 3 Registergericht: Freiburg i. Br., HRB 700 806; Geschäftsführer: Heinz Egger, Thomas Gleixner -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645422: xfce4-terminal: System bell does not work
Package: xfce4-terminal Followup-For: Bug #645422 It seems this is by design - you will want to edit .config/Terminal/terminalrc and set MiscBell=TRUE (the default is FALSE). It should take effect as soon as you save the file. See http://docs.xfce.org/apps/terminal/advanced (of course, the ideal situation would be to have similar configurability to Konsole, which allows you to set an arbitrary command to be run for every beep, for those who find the standard PC beep rather too intrusive) -MD -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685379: [CRASH] Uncaught exception OverflowError in Frontend/Gtk/ui.py:682
Package: update-manager-gnome Version: 0.200.5-1 Severity: normal File: /usr/share/pyshared/UpdateManager/Frontend/Gtk/ui.py *** /tmp/update-manager-bug0v3Fg9 The information below has been automatically generated. Please do not remove this from your bug report. - Exception Type: type 'exceptions.OverflowError' - Exception Value: OverflowError('signed integer is greater than maximum',) - Exception Origin: _MainThread(MainThread, started 140694750893824) - Exception Traceback: File /usr/bin/update-manager, line 38, in module app.main() File /usr/lib/pymodules/python2.6/UpdateManager/Application.py, line 421, in main self._frontend.init_frontend() File /usr/lib/pymodules/python2.6/UpdateManager/Frontend/Gtk/__init__.py, line 70, in init_frontend self._ui = GtkUI(self) File /usr/lib/pymodules/python2.6/UpdateManager/Frontend/Gtk/ui.py, line 641, in __init__ self.gconf_store_launch_time() File /usr/lib/pymodules/python2.6/UpdateManager/Frontend/Gtk/ui.py, line 682, in gconf_store_launch_time int(time.time())) -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages update-manager-gnome depends on: ii gconf22.28.1-6 GNOME configuration database syste ii gksu 2.0.2-5graphical frontend to su ii python2.6.6-3+squeeze7 interactive high-level object-orie ii python-dbus 0.83.1-1 simple interprocess messaging syst ii python-gconf 2.28.1-1 Python bindings for the GConf conf ii python-gobject2.21.4+is.2.21.3-1 Python bindings for the GObject li ii python-gtk2 2.17.0-4 Python bindings for the GTK+ widge ii python-support1.0.10 automated rebuilding support for P ii python-vte1:0.24.3-3 Python bindings for the VTE widget ii update-manager-core 0.200.5-1 APT update manager core functional update-manager-gnome recommends no packages. Versions of packages update-manager-gnome suggests: ii software-properties-gtk0.60.debian-3 manage the repositories that you i ii update-notifier0.99.3debian8 Daemon which notifies about packag -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685340: [php-maint] Bug#685340: php5-common: provide one /etc/apache2/conf.d/php5.conf for all SAPIs
On Mon, Aug 20, 2012 at 1:11 AM, Christoph Anton Mitterer cales...@scientia.net wrote: This would have the advantages: - All SAPIs share the same config, thus no surprises. I am not sure it that's a good idea (even when I drop your mix of AddType and SetHandler). I'll try to come with something else which doesn't involve installing apache configuration files when install php5-cli package. - No longer the need for manually configuring Apache with respect to PHP when using CGI/FCGI That's simply not true. - You will have to configure Apache manually for CGI/FastCGI, because you can install mod_php along with php5-cgi - and having both serving PHP files would create just a mess. - For FastCGI using php5-cgi - you have to create a fastcgi wrapper, so again it needs manual configuration. - And FPM doesn't work with libapache2-mod-fcgid at all and needs libapache2-mod-fastcgi from non-free, so again manual intervention is required. We can largely drop the special section about CGI from README.Debian Not much can be dropped. I personally, would strongly recommend AGAINST also having the Action/ScriptAlias directive there; admins or package maintainers should place them in the Directory definitions where this is needed. I agree on that, but from different reasons (as documented in README.Debian) - the php5-cgi is webserver agnostic and we don't want it to conflict with libapache2-mod-php5(filter). It's simply unclean and even dangerous to enable interpretation of PHP files server-wide, as it's now done by mod_php packages. Why? You keep pushing your opinions without giving any technical reason. Default Debian configuration is secure (it allows only files in /var/www to be accessed). #Note: The following is a security measure to remove any possible mappings that would also apply on “middle extensions” (for example “test.php.png”). RemoveType php You keep repeating this, but Apache manual says: 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. So either you or Apache manual is wrong. Files ?*.php AddType application/x-php php /Files Again you keep pushing Files vs FilesMatch, but did you do or see any performance tests. I would guess that processing the PHP file in most common scenarios would be much longer than the performance hit induced by using FilesMatch. I would rather have the configuration files simple to read than tuned to max performance. Compare: FilesMatch .+\.ph(p[345]?|tml|t)$ SetHandler application/x-httpd-php /FilesMatch FilesMatch .+\.phps$ SetHandler application/x-httpd-php-source /FilesMatch to Files ?*.php SetHandler application/x-httpd-php /Files Files ?*.pht SetHandler application/x-httpd-php /Files Files ?*.php3 SetHandler application/x-httpd-php /Files Files ?*.php4 SetHandler application/x-httpd-php /Files Files ?*.php5 SetHandler application/x-httpd-php /Files Files ?*.phtml SetHandler application/x-httpd-php /Files Files ?*.phps SetHandler application/x-httpd-php-source /Files The FilesMatch form is much simpler to read and modify en masse. -- Ondřej Surý ond...@sury.org -- To UNSUBSCRIBE, email to debian-bugs-dist-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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685380: gnarwl: [INTL:sk] Slovak po-debconf translation
Package: gnarwl Severity: wishlist Tags: l10n patch Version: 3.6.dfsg-6 The sk.po attached. regards # #Translators, if you are not familiar with the PO format, gettext #documentation is worth reading, especially sections dedicated to #this format, e.g. by running: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # #Some information specific to po-debconf are available at #/usr/share/doc/po-debconf/README-trans # or http://www.debian.org/intl/l10n/po-debconf/README-trans # #Developers do not need to manually edit POT or PO files. # Slavko li...@slavino.sk, 2012. # msgid msgstr Project-Id-Version: gnarwl 3.6.dfsg-6\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2006-12-02 06:20+0100\n PO-Revision-Date: 2012-08-20 12:59+0200\n Last-Translator: Slavko li...@slavino.sk\n Language-Team: slovenčina debian-l10n-slo...@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Language: sk\n Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n=2 n=4) ? 1 : 2;\n X-POFile-SpellExtra: ldap dc vasadomena gnarwl 389 Gnarwl LDAP local\n #. Type: string #. Description #: ../templates:1001 msgid Name/address of the LDAP server: msgstr Meno/adresa servera LDAP: #. Type: string #. Description #: ../templates:1001 msgid Gnarwl contacts a LDAP server in order to get information about vacation messages and accounts. Please specify the server, optionally with the port to be used. msgstr Gnarwl získava informácie o dovolenkových správach a účtoch zo servera LDAP. Prosím, zadajte server, prípadne aj použitý port. #. Type: string #. Description #: ../templates:1001 msgid Example: ldap.yourdomain.local:389 msgstr Príklad: ldap.vasadomena.local:389 #. Type: string #. Description #: ../templates:2001 msgid Base DN of the LDAP server: msgstr Base DN servera LDAP: #. Type: string #. Description #: ../templates:2001 msgid In order to access the LDAP server, please specify the base gnarwl should use for LDAP queries. msgstr Kvôli prístupu k serveru LDAP, prosím, zadajte základ, ktorý má gnarwl požiť pri hľadaní v LDAP. #. Type: string #. Description #: ../templates:2001 msgid Example: dc=yourdomain,dc=somewhere msgstr Príklad: dc=vasadomena,dc=niekde
Bug#685381: efingerd: [INTL:sk] Slovak po-debconf translation
Package: efingerd Severity: wishlist Tags: l10n patch Version: 1.6.2.7 The sk.po attached. regards # Slovak translations for efingerd package # Slovenské preklady pre balík efingerd. # Copyright (C) 2012 THE efingerd'S COPYRIGHT HOLDER # This file is distributed under the same license as the efingerd package. # Automatically generated, 2012. # Slavko li...@slavino.sk, 2012. # msgid msgstr Project-Id-Version: efingerd 1.6.2.7\n Report-Msgid-Bugs-To: efing...@packages.debian.org\n POT-Creation-Date: 2010-01-01 21:30+0100\n PO-Revision-Date: 2012-08-20 13:21+0200\n Last-Translator: Slavko li...@slavino.sk\n Language-Team: slovenčina debian-l10n-slo...@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Language: sk\n Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n=2 n=4) ? 1 : 2;\n X-POFile-SpellExtra: passwd efingerd finger UID\n #. Type: boolean #. Description #: ../templates:1001 msgid Permit users to have their own configurable finger replies? msgstr Povoliť používateľom používať ich vlastné nastaviteľné odpovede finger? #. Type: boolean #. Description #: ../templates:1001 msgid You can decide if efingerd honours users' ~/.efingerd files. msgstr Môžete rozhodnúť, či bude efingerd používať používateľské súbory ~/.efingerd. #. Type: boolean #. Description #: ../templates:1001 msgid If someone from network fingers given user, and the user has ~/.efingerd file readable and executable for efingerd daemon, this file will be executed and its output will be sent to the fingerer. msgstr Ak niekto zo siete zisťuje daného používateľa, a tento používateľ má súbor ~/.efingerd čitateľný a spustiteľný démonom efingerd, tento súbor bude spustený a jeho výstup bude odoslaný hľadajúcemu. #. Type: boolean #. Description #: ../templates:1001 msgid This can be either desired or not, depending on your system policy. In particular, allowing .efingerd files allows users to cheat about their real identity. However, efingerd can be configured to display users' full names (from passwd) as the first line of the reply, so they cannot hide themselves completely. msgstr Toto môže, ale nemusí byť žiadané, v závislosti na systémovej politike. Vo všeobecnosti, povolenie súborov .efingerd poskytuje používateľom možnosť klamať o svojej reálnej identite. Avšak, efingerd môže byť nastavený tak, aby zobrazoval úplné mená používateľov (z passwd) ako prvý riadok odpovede, takže sa používatelia nedokážu úplne skryť. #. Type: boolean #. Description #: ../templates:1001 msgid There is however a slight security concern: if you allow .efingerd files, these files will be executed under efingerd UID, so malicious users gain access to all files owned by efingerd - this becomes important when you make efingerd to log into some files writable by the daemon, unless you take appropriate precautions. msgstr Existuje však aj malý bezpečnostný problém: ak povolíte súbory .efingerd, tieto súbory môžu byť spúšťané s právami UID efingerd, takže škodliví používatelia môžu získať prístup k všetkým súborom vlastneným efingerd – toto sa môže stať dôležité, keď nastavíte efingerd na zaznamenávanie do nejakých súborov, zapisovateľných pre tohoto démona, pokiaľ neurobíte predbežné opatrenia. #. Type: boolean #. Description #: ../templates:1001 msgid If you are the only user, or you trust your users, there is no reason to disable .efingerd files (and this is probably a reason you want to install efingerd for). However, if you expect your users to be nasty, you should better think about protecting from them - in particular, if you enable logging, make sure they cannot fiddle with the logfile - this is UP TO YOU. msgstr Ak ste len používateľ, alebo dôverujte svojim používateľom, neexistuje dôvod na zakázanie súborov .efingerd (a je to pravdepodobne aj dôvod, kvôli ktorému inštalujete efingerd). Ale ak očakávate, že vaši používatelia budú zlí, mali by ste sa viac zamyslieť nad ochranou pred nimi – vo všeobecnosti, ak povolíte zaznamenávanie, zaistite aby nemohli manipulovať so súborom záznamu *. toto je len na vás. #. Type: boolean #. Description #: ../templates:2001 msgid Display users' real names? msgstr Zobraziť skutočné mená používateľov? #. Type: boolean #. Description #: ../templates:2001 msgid By default, efingerd displays users real names (from passwd) as the first line of finger reply. You may want to suppress it, but if you allow the use of .efingerd files at the same time, be aware that users can hide their identity for the fingerer. msgstr Predvolene, efingerd zobrazuje reálne používateľské mená (z passwd) ako prvý riadok odpovede finger. Môžete to vypnúť, ale ak zároveň povolíte použitie súborov .efingerd, pamätajte, že používatelia môžu skryť svoju identitu. #. Type: boolean #. Description #: ../templates:2001 msgid If in doubt, select this option. msgstr Ak neviete čo to znamená, vyberte túto možnosť.
Bug#685382: mysql-server: bind :: results in listening to IPv6 only
Package: mysql-server Version: 5.5.24+dfsg-6 Severity: important Dear Maintainer, when trying to make mysql listen on both interfaces like described here: http://dev.mysql.com/doc/refman/5.5/en/ipv6-server-config.html it will listen on IPv6 ONLY! $ mysqld --bind-address=:: $ netstat -ltpn|grep -i mysql tcp6 0 0 :::3306 :::*LISTEN 27119/mysqld When setting bind-address=:: in the my.cnf it's the exact same behaviour. Since it is a very basic requirement I consider this a major bug. Thank you -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages mysql-server depends on: ii mysql-server-5.5 5.5.24+dfsg-6 mysql-server recommends no packages. mysql-server suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685383: PHP cannot handle uploads bigger than 2GB
Package: php5 Version: 5.3.3-7+squeeze14 Tags: patch, upstream, lfs PHP doesn't support uploads of files bigger than 2GB. It's a known bug in upstream - https://bugs.php.net/bug.php?id=44522 - but the fix still isn't in and there doesn't seem to be any answer. Right now I'm running with the patch from above, tweaked a bit to apply to the PHP in squeeze, which I'm attaching. A part of it (the conversion from atoi() to atol() ) is already included in the php5 package in testing (version 5.4.4-4) but the rest doesn't seem to be there. The patch is kludgy and I'd agree to fix it up a bit if there's the possibility to be accepted. This is reproducible with setting in php.ini the upload_max_filesize to something more than 2GB, post_max_size to the same value, having the following code in a php file: ? if (!move_uploaded_file($file['tmp_name'], /tmp/testfile)) { echo doesn't work; } else { echo works; } @unlink(/tmp/testfile); ? And running from somewhere dd if=/dev/zero of=bigf bs=1M count=4099 curl -F file=@bigf 'http://some.server.addr/upload.php' (fixing the url to reflect the position of the php file) As for the reason for this, a lot of sites (including mine) actually need this kind of upload, as there's no good way to push files to it otherwise (I've seen suggestions to use FTP) that the users can easily use. With the proliferation of big video files, there's a lot of stuff people want to upload which goes above these limits. -- Regards, Vasil Kolev diff -ruN php5-5.3.3.orig/main/rfc1867.c php5-5.3.3/main/rfc1867.c --- php5-5.3.3.orig/main/rfc1867.c 2010-03-18 22:37:25.0 + +++ php5-5.3.3/main/rfc1867.c 2012-08-16 12:55:20.191343090 + @@ -764,7 +764,8 @@ { char *boundary, *s = NULL, *boundary_end = NULL, *start_arr = NULL, *array_index = NULL; char *temp_filename = NULL, *lbuf = NULL, *abuf = NULL; - int boundary_len = 0, total_bytes = 0, cancel_upload = 0, is_arr_upload = 0, array_len = 0; + int boundary_len = 0, cancel_upload = 0, is_arr_upload = 0, array_len = 0; + long total_bytes = 0; int max_file_size = 0, skip_upload = 0, anonindex = 0, is_anonymous; zval *http_post_files = NULL; HashTable *uploaded_files = NULL; diff -ruN php5-5.3.3.orig/main/SAPI.h php5-5.3.3/main/SAPI.h --- php5-5.3.3.orig/main/SAPI.h 2010-03-18 22:37:25.0 + +++ php5-5.3.3/main/SAPI.h 2012-08-16 12:56:43.563342213 + @@ -82,7 +82,7 @@ char *post_data, *raw_post_data; char *cookie_data; long content_length; - uint post_data_length, raw_post_data_length; + uint IGNORE_post_data_length, IGNORE_raw_post_data_length; char *path_translated; char *request_uri; @@ -113,6 +113,7 @@ int argc; char **argv; int proto_num; + long post_data_length, raw_post_data_length; } sapi_request_info; @@ -120,7 +121,7 @@ void *server_context; sapi_request_info request_info; sapi_headers_struct sapi_headers; - int read_post_bytes; + long read_post_bytes; unsigned char headers_sent; struct stat global_stat; char *default_mimetype; diff -ruN php5-5.3.3.orig/sapi/apache/mod_php5.c php5-5.3.3/sapi/apache/mod_php5.c --- php5-5.3.3.orig/sapi/apache/mod_php5.c 2010-03-12 10:28:59.0 + +++ php5-5.3.3/sapi/apache/mod_php5.c 2012-08-16 12:57:54.471343210 + @@ -533,7 +533,7 @@ SG(request_info).request_uri = r-uri; SG(request_info).request_method = (char *)r-method; SG(request_info).content_type = (char *) table_get(r-subprocess_env, CONTENT_TYPE); - SG(request_info).content_length = (content_length ? atoi(content_length) : 0); + SG(request_info).content_length = (content_length ? atol(content_length) : 0); SG(sapi_headers).http_response_code = r-status; SG(request_info).proto_num = r-proto_num; diff -ruN php5-5.3.3.orig/sapi/apache2filter/sapi_apache2.c php5-5.3.3/sapi/apache2filter/sapi_apache2.c --- php5-5.3.3.orig/sapi/apache2filter/sapi_apache2.c 2010-02-05 18:59:05.0 + +++ php5-5.3.3/sapi/apache2filter/sapi_apache2.c 2012-08-16 12:58:55.867343008 + @@ -420,7 +420,7 @@ efree(content_type); content_length = (char *) apr_table_get(f-r-headers_in, Content-Length); - SG(request_info).content_length = (content_length ? atoi(content_length) : 0); + SG(request_info).content_length = (content_length ? atol(content_length) : 0); apr_table_unset(f-r-headers_out, Content-Length); apr_table_unset(f-r-headers_out, Last-Modified); diff -ruN php5-5.3.3.orig/sapi/apache2handler/sapi_apache2.c php5-5.3.3/sapi/apache2handler/sapi_apache2.c --- php5-5.3.3.orig/sapi/apache2handler/sapi_apache2.c 2010-05-04 09:51:03.0 + +++ php5-5.3.3/sapi/apache2handler/sapi_apache2.c 2012-08-16 12:59:27.399379866 + @@ -484,7 +484,7 @@ r-no_local_copy = 1; content_length = (char *) apr_table_get(r-headers_in, Content-Length); - SG(request_info).content_length = (content_length ? atoi(content_length) : 0); + SG(request_info).content_length = (content_length ? atol(content_length) : 0);
Bug#684437: ***SPAM***Re: Bug#684437: unblock: fpc/2.6.0-6
On Fri, 2012-08-10 at 23:16 +0100, peter green wrote: Philipp Kern wrote: Uhm, is it really required by policy to delete backup files that weren't created by the package in the first place? diff -Nru fpc-2.6.0/debian/fp-compiler.postrm.in fpc-2.6.0/debian/fp-compiler.postrm.in --- fpc-2.6.0/debian/fp-compiler.postrm.in 2012-05-06 21:43:32.0 + +++ fpc-2.6.0/debian/fp-compiler.postrm.in 2012-08-09 22:55:10.0 + @@ -4,12 +4,14 @@ ACTION=$1 -CFG_FILE=/etc/fpc-${VERSION}.cfg +CFG_FILE=/etc/fpc-${VERSION} # Debhelper code #DEBHELPER# if test ${ACTION} = purge then - rm -f ${CFG_FILE} + rm -f ${CFG_FILE}.cfg + rm -f ${CFG_FILE}.bak + rm -f ${CFG_FILE}.*dpkg* fi The second part does not make me happy. The .bak file is created by the package under some circumstances (certain upgrade scenarios I believe). I don't understand why abou put in the .*dpkg* line though. ccing him to ask. Sorry for late replay. The *.dpkg* are crated when upgrading with conflicts between local modifications and new supplied default script. These are normally to be removed by user, but when you are purging a file you are getting rid of all configuration, so I thought it was no need to keep these files. Cheers, signature.asc Description: This is a digitally signed message part
Bug#685384: unblock: uwsgi/1.2.3+dfsg-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hello, Please unblock package uwsgi. There is a bug with a release in Wheezy that is making init script useless after a reload. The fix is to remove `name` parameter from start-stop-daemon. I am sending debdiff. unblock uwsgi/1.2.3+dfsg-3 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.4-trunk-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 diff -Nru uwsgi-1.2.3+dfsg/debian/changelog uwsgi-1.2.3+dfsg/debian/changelog --- uwsgi-1.2.3+dfsg/debian/changelog 2012-07-16 22:05:11.0 +0200 +++ uwsgi-1.2.3+dfsg/debian/changelog 2012-08-20 13:02:48.0 +0200 @@ -1,3 +1,10 @@ +uwsgi (1.2.3+dfsg-3) unstable; urgency=low + + * Remove `name` option from start-stop-daemon as master process is +changing its name on reloads. Thanks Andreas Motl for the patch. + + -- Janos Guljas ja...@resenje.org Mon, 20 Aug 2012 12:32:43 +0200 + uwsgi (1.2.3+dfsg-2) unstable; urgency=low * Remove uwsgi-plugin-luajit binary package. (Closes: #680132) diff -Nru uwsgi-1.2.3+dfsg/debian/uwsgi-files/init/specific_daemon uwsgi-1.2.3+dfsg/debian/uwsgi-files/init/specific_daemon --- uwsgi-1.2.3+dfsg/debian/uwsgi-files/init/specific_daemon 2012-03-17 20:46:49.0 +0100 +++ uwsgi-1.2.3+dfsg/debian/uwsgi-files/init/specific_daemon 2012-08-20 12:31:27.0 +0200 @@ -79,8 +79,7 @@ start-stop-daemon --stop --quiet \ --retry=QUIT/30/KILL/5 \ ---pidfile $PIDFILE \ ---name $NAME +--pidfile $PIDFILE RETVAL=$? [ $RETVAL = 2 ] return 2 @@ -100,8 +99,7 @@ start-stop-daemon --stop --quiet \ --signal=HUP \ ---pidfile $PIDFILE \ ---name $NAME +--pidfile $PIDFILE RETVAL=$? @@ -121,8 +119,7 @@ start-stop-daemon --stop --quiet \ --signal=TERM \ ---pidfile $PIDFILE \ ---name $NAME +--pidfile $PIDFILE RETVAL=$?
Bug#685385: geoip-database-contrib: [INTL:sk] Slovak po-debconf translation
Package: geoip-database-contrib Severity: wishlist Tags: l10n patch Version: 1.7 The sk.po attached. regards # LANGUAGE translation of the the geoip-database-contrib debconf template # Copyright (C) 2012 the geoip-database-contrib package's copyright holder # This file is distributed under the same license as the geoip-database-contrib package. # Slavko li...@slavino.sk, 2012. # msgid msgstr Project-Id-Version: geoip-database-contrib 1.7\n Report-Msgid-Bugs-To: geoip-database-cont...@packages.debian.org\n POT-Creation-Date: 2010-12-30 19:21+0100\n PO-Revision-Date: 2012-08-20 13:39+0200\n Last-Translator: Slavko li...@slavino.sk\n Language-Team: slovenčina debian-l10n-slo...@lists.debian.org\n Language: sk\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n=2 n=4) ? 1 : 2;\n X-POFile-SpellExtra: GeoLite cron geoip-database-contribupdate MaxMind\n X-POFile-SpellExtra: root\n #. Type: boolean #. Description #: ../templates:1001 msgid Automatically update the database every month? msgstr Automaticky aktualizovať databázu každý mesiac? #. Type: boolean #. Description #: ../templates:1001 msgid The GeoLite database on the MaxMind website is updated monthly. If you choose to automatically update the local copy of the database, a cron script will be installed to download the new version from the Internet on the tenth of every month. msgstr Databáza GeoLite na webovej stránke MaxMind je aktualizovaná mesačne. Ak si zvolíte automatickú aktualizáciu lokálnej kópie databázy, bude nainštalovaný skript cron, ktorý stiahne novú verziu z internetu, vždy desiateho v mesiaci. #. Type: boolean #. Description #: ../templates:1001 msgid If you choose not to update the database automatically, you can do it by hand by running the 'geoip-database-contrib_update' command as root. msgstr Ak si zvolíte neaktualizovať databázu automaticky, môžete to urobiť manuálne spustením príkazu „geoip-database-contrib_update” ako root.
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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685168: Acknowledgement (vera++: Missing CXXFLAGS (hardening))
Dear Mathieu, Thanks for your report and hints. I have removed the overriding settings. This should fix the problem. An updated version of the package is available on debian mentors and waiting for a sponsor. I am going to check if my previous sponsor can upload it for me. Best regards, signature.asc Description: This is a digitally signed message part.
Bug#669565: RFS: gammaray/1.1.0-1 [ITP] -- Tool for examining the internals of Qt application
Hi Felix, On 16.8.2012 11:04, Felix Geyer wrote: I noticed some issues in the copyright file: - This one is missing: ./core/palettemodel.cpp: Copyright (C) 2010 Ariya Hidayatariya.hida...@gmail.com - tools/ has been moved to core/tools/ - cmake/* is missing. Some of those files don't have a license header. It would be good to check with upstream under what license they are released. I fixed what I could figure out myself, for the rest of files in cmake/ I asked upstream [1], missing license headers are now added in their git [2] and also in our d/copyright. Regards, Jakub [1] https://mail.kdab.com/pipermail/gammaray-interest/2012-August/48.html [2] https://github.com/KDAB/GammaRay/commits/master -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685387: pm-utils: Broken hibernate in Wheezy
Package: pm-utils Version: 1.4.1-9 Severity: normal Dear Maintainer, Use Wheezy, kernel update yesterday broke hibernate, hibernation does not work in Ubuntu since version 12.04. The system goes to sleep, but does not wake up. If you do spill it just does not find that sleep. The logs: Aug 20 08:34:45 fl kernel: [0.821208] PM: Hibernation image not present or could not be loaded. Aug 20 08:34:45 fl kernel: [1.895650] PM: Hibernation image partition 8:5 present Aug 20 08:34:45 fl kernel: [1.895654] PM: Looking for hibernation image. Aug 20 08:34:45 fl kernel: [1.895897] PM: Hibernation image not present or could not be loaded. Give the console command sudo pm-hibernate - no reaction. I give sudo pm-suspend - goes into standby. Sleeping(and wake up) working on echo disk /sys/power/state. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-486 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pm-utils depends on: ii powermgmt-base 1.31 Versions of packages pm-utils recommends: ii hdparm 9.39-1+b1 ii kbd 1.15.3-9 ii procps 1:3.3.3-2 ii vbetool 1.1-2 Versions of packages pm-utils suggests: ii cpufrequtils008-1 ii ethtool 1:3.4.2-1 pn radeontool none ii wireless-tools 30~pre9-8 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681051: closed by أحمد المحمودي (Ahmed El-Mahmoudy) aelmahmo...@sabily.org (Bug#681051: fixed in xpra 0.3.6+dfsg-1)
The menus still pop up offscreen. Single screen layout: Screen 0: minimum 320 x 200, current 1200 x 1600, maximum 8192 x 8192 HDMI-0 connected 1200x1600+0+0 left (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 60.0 1024x768 60.0 800x60060.3 640x48060.0 720x40070.1 DVI-0 connected (normal left inverted right x axis y axis) 1280x1024 60.0 + 1280x960 60.0 1024x768 60.0 800x60060.3 640x48060.0 720x40070.1 VGA-0 disconnected (normal left inverted right x axis y axis) dual screen: Screen 0: minimum 320 x 200, current 2480 x 1600, maximum 8192 x 8192 HDMI-0 connected 1200x1600+0+0 left (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 60.0 1024x768 60.0 800x60060.3 640x48060.0 720x40070.1 DVI-0 connected 1280x1024+1200+0 (normal left inverted right x axis y axis) 359mm x 287mm 1280x1024 60.0*+ 1280x960 60.0 1024x768 60.0 800x60060.3 640x48060.0 720x40070.1 VGA-0 disconnected (normal left inverted right x axis y axis) The xpra dummy server: Screen 0: minimum 320 x 175, current 2560 x 1600, maximum 8192 x 4096 default connected 2560x1600+0+0 0mm x 0mm 1920x1440 75.0 60.0 1600x1200 85.0 75.0 70.0 65.0 60.0 1680x1050 85.0 10.0 75.0 70.0 60.0 1400x1050 85.0 75.0 70.0 60.0 1440x900 60.0 20.0 1280x1024 85.0 75.0 60.0 1024x768 85.0 25.0 87.0 75.0 70.0 60.0 800x60085.0 25.0 75.0 72.0 70.0 65.0 60.0 56.0 320x20085.0 5120x3200 10.0 3840x2880 10.0 3840x2560 10.0 3840x2048 10.0 2048x2048 10.0 2560x1600 10.0* 2048x1536 60.0 1856x1392 75.0 60.0 1792x1344 75.0 60.0 1920x1200 10.0 1920x1080 10.0 1600x900 20.0 1280x960 85.0 60.0 1360x768 20.0 60.0 800x1280 20.0 1280x800 20.0 1152x864 100.0 85.0 75.0 70.0 60.0 800x1242 20.0 1280x762 20.0 720x1280 25.0 1280x720 25.0 720x1242 25.0 1280x682 25.0 768x1024 25.0 768x98625.0 1024x730 25.0 960x72085.0 75.0 60.0 928x69675.0 60.0 600x1024 25.0 1024x600 25.0 896x67275.0 60.0 600x98625.0 1024x562 25.0 832x62475.0 536x96025.0 960x53625.0 536x92225.0 600x80025.0 960x49825.0 600x76225.0 800x56225.0 840x52585.0 75.0 70.0 60.0 480x85425.0 848x48025.0 480x81025.0 480x80025.0 800x48025.0 848x44225.0 700x52585.0 75.0 70.0 60.0 480x76225.0 640x51285.0 75.0 60.0 720x45060.0 640x48085.0 75.0 73.0 60.0 720x40085.0 680x38460.0 640x40085.0 576x432 100.0 85.0 75.0 70.0 60.0 640x35085.0 512x38487.0 85.0 75.0 70.0 60.0 416x31275.0 400x30085.0 75.0 72.0 60.0 56.0 320x24085.0 75.0 73.0 60.0 360x20085.0 320x17585.0 8192x4096 75.0 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685168: Status pending
tags #685168 + pending signature.asc Description: This is a digitally signed message part.
Bug#678409: xpra: mouse position out of sync
Hello, Excerpts from Antoine Martin's message of Sat Aug 18 14:57:24 +0200 2012: FYI, You can find the source tarballs here (xpra only - nothing else): https://www.xpra.org/src/ I don't think this bug is fixed either in 0.3.x, 0.4.x or even trunk. But please do give it a try to confirm. Since I am not able to reproduce it and the questions have not been answered, I will probably have to close this bug as 'needinfo'. I cannot reproduce the bug either, It only happened once. It may be related to using Xvfb as opposed to Xorg with the dummy driver but it may be just random race condition somewhere that is triggered rarely. Note this happened on first attach of xpra session and detaching and reattaching the session fixed the problem. Also note that my window manager does manage (eg. resize) windows when they are mapped. I used no virtualization other than xpra. It is also possible that it happened because I started firefox interactively while the session was attached as opposed to pre-starting it before attaching the session. Thanks Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685384: unblock: uwsgi/1.2.3+dfsg-3
Hi Adam, On Mon, Aug 20, 2012 at 2:17 PM, Adam D. Barratt a...@adam-barratt.org.uk wrote: On 20.08.2012 12:37, Janos Guljas wrote: Please unblock package uwsgi. There is a bug with a release in Wheezy that is making init script useless after a reload. The fix is to remove `name` parameter from start-stop-daemon. I am sending debdiff. What name does the daemon end up running under? (Presumably not uwsgi.) The name is changed from uwsgi to uwsgi-core. Regards, Adam Best, Janos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685384: unblock: uwsgi/1.2.3+dfsg-3
On 20.08.2012 12:37, Janos Guljas wrote: Please unblock package uwsgi. There is a bug with a release in Wheezy that is making init script useless after a reload. The fix is to remove `name` parameter from start-stop-daemon. I am sending debdiff. What name does the daemon end up running under? (Presumably not uwsgi.) Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685388: Package new upstream version 7.5 in experimental
Package: gdb Severity: wishlist Dear maintainer, please, consider packaging the new upstream version 7.5 of gdb in experimental. Thanks, Andrey -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#270505: Compressed debuginfo
gdb 6.8.50.20081120.python-1 (28 Nov 2008) contains in the changelog: - Compressed debug information support; the new gold linker can generate compressed debug sections. So the reported issue (07 Sep 2004) is resolved? Andrey -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685389: please provide a Git repo for the packaging
Package: mediathekview Version: 2.4.0-4 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, there's currently no VCS-* link in mediathekview's debian/control file and I also did not find any repo on debian's svn and git server. Please consider doing the packaging in a public Git repo and use the VCS-* links in debian/control. Thank you, Thomas Koch -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQMi0mAAoJEAf8SJEEK6ZafQEQAKJdxhS8jeaVbbeJAMlf3Nn7 eC38fy7jYM0wYuagxhS3xUmr2NdENz251KCQm6WvfSII1yRNs8y7y8uzWsU733UI klZxdL6tlWN9UwVJBHdHFxrBzOKrCvycws1e8fip4U8sB8AcAjnrb82abwiRKhy3 Y0D93O90rIb55vN/EcMhL1+zPZ8WblqFMLf8uOqs6KN10eAx9396zKn/Pq9DGnyc GPkgbNmfjfKyWOw8mZDK1ho9PR+mTz7ev1CTr/b/qTBABtAbrsUxZt8y6DKoJzkD efovf9BUHqm6xkecwAz4OrPUd5gmpGLlmIQRSJbq1HjmQ2sNFzYHerkiuku5t5rK 96+ujLuBhygEn0mjuPECPM60oaEg1SRYWHexXWASRTKsBPE/zovuBZskCutA5Fa7 rc4Kcg1p7pZQFB2l3WNcHjUWj6eXotRpqerzGS54LrXDqWxPo3NW7n51Vo/+evMl lpQjbgScdhTo4FP++BpQOrst0CwZhQfOHJWlp+etGGE/olj14klb3dmi0/G1aAZ1 JmwzR6cyS4olqZ0+CLYGY6w8FYu7Ekm6s/LqocpQl5kt2NEbtqRaNAOHRCDW7baY j2qhbAeud2vMbCSR+FUQMaSeHlaz8cNEQp3GKQG8np8lHItRHGxm3S0QvVEF+Zw6 AJnndFfgSuJXdXKScf+0 =0d/C -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681767: linux-image-3.2.0-3-rt-amd64: irq/23-eth0 high load
Control: retitle -1 rt: NAPI softirq not being scheduled properly Control: tag -1 upstream On Mon, 2012-08-20 at 11:06 +0300, Yevgeny Kosarzhevsky wrote: On Mon, 20 Aug 2012 04:46:53 +0100 Ben Hutchings b...@decadent.org.uk wrote: On Mon, 2012-07-16 at 10:48 +, Yevgeny Kosarhevsky wrote: Package: src Version: 3.2.21-3 Severity: critical Justification: causes serious data loss What data? My peers reported packet loss. Switching back to 2.6.32 kernel solved the issue. You must accept the risk of loss of data transmitted using UDP. The phrase 'causes serious data loss' refers only to data in non-volatile storage (or that is reported as having been stored there). Dear Maintainer, I get a heavy load on irq/23-eth0: 1086 root -51 0 000 S 2.0 0.0 0:31.04 irq/23-eth0 I don't think 2% CPU time is a 'heavy load'. This is only occured after upgrading from 2.6.32 kernel. The LA was 0.00 on previous kernel, now it's 1.44 [...] But you are not comparing like with like. On a real-time kernel, IRQ handlers are scheduled as tasks and are accounted in the load average. On a standard kernel as you were running before, IRQ handlers are accounted separately. So, is there really a problem here? Did you actually mean to install a real-time kernel? Since there was a packet loss, I think there is a problem. I don't know if it's related with [ 1966.544292] NOHZ: local_softirq_pending 08 [ 2108.848600] NOHZ: local_softirq_pending 08 The number 08 apparently represents the NET_RX softirq, which is usually responsible for receiving packets after a network interrupt (NAPI). And this warning seems to mean that it is marked as pending, but somehow hasn't been scheduled. So this is very likely related. Ben. -- Ben Hutchings The most exhausting thing in life is being insincere. - Anne Morrow Lindberg signature.asc Description: This is a digitally signed message part
Bug#685354: unblock: sendfile/2.1b.20080616-5.1
Control: tags -1 + moreinfo On 20.08.2012 07:14, Andreas Tille wrote: Please unblock package sendfile The RC bug #668721 was fixed in NMU and the package should migrate to testing. Am I reading the maintainer scripts correctly in that they modify (or at least attempt to modify) several files not shipped by the package, including /etc/services and /etc/csh.login, both of which are conffiles? Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632477: wmbutton: Clicking Middle Mouse Button has no effect
Hi, run wmbutton using the -m argument. Something is wrong in the code or in the manpage, because the default option (in manpage) is middle button enabled. I think this bug could be closed, but I will hold it open to solve the code/manpage problem. Thanks a lot for your bug report. Best regards, kix -- ||// //\\// Rodolfo kix Garcia ||\\// //\\ http://www.kix.es/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685390: libbliss1d: libbliss should be linked against libgmp
Package: libbliss1d Version: 0.72-2 Severity: normal The following build warnings should be taken care of dpkg-shlibdeps: warning: symbol __gmpz_init used by debian/libbliss1d/usr/lib/libbliss.so.1d.0 found in none of the libraries dpkg-shlibdeps: warning: symbol __gmpz_set_si used by debian/libbliss1d/usr/lib/libbliss.so.1d.0 found in none of the libraries dpkg-shlibdeps: warning: symbol __gmpz_clear used by debian/libbliss1d/usr/lib/libbliss.so.1d.0 found in none of the libraries dpkg-shlibdeps: warning: symbol __gmpz_mul_si used by debian/libbliss1d/usr/lib/libbliss.so.1d.0 found in none of the libraries -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libbliss1d depends on: ii libc6 2.13-32 ii libgcc1 1:4.7.0-8 ii libstdc++6 4.7.0-8 libbliss1d recommends no packages. Versions of packages libbliss1d suggests: ii libbliss-dev 0.72-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684437: ***SPAM***Re: Bug#684437: unblock: fpc/2.6.0-6
Hi, On Mon, 20 Aug 2012, Abou Al Montacir wrote: I don't understand why abou put in the .*dpkg* line though. ccing him to ask. Sorry for late replay. The *.dpkg* are crated when upgrading with conflicts between local modifications and new supplied default script. These are normally to be removed by user, but when you are purging a file you are getting rid of all configuration, so I thought it was no need to keep these files. dpkg already takes care of removing those files during purge (as well as foo~, foo% and foo.bak). $ grep -A1 -r REMOVECONFFEXTS lib/dpkg/ lib/dpkg/dpkg.h:#define REMOVECONFFEXTS~, .bak, %, \ lib/dpkg/dpkg.h- DPKGTEMPEXT, DPKGNEWEXT, DPKGOLDEXT, DPKGDISTEXT Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685391: Installs unusable header file perf.h
Source: firebird-dev Version: 2.5.2~svn+54698.ds4-1 Severity: normal firebird-dev installs /usr/include/perf.h, which contains the line: #include ../jrd/perf_proto.h Needless to say, that other header is not installed. Please do not install an unusable header. Ben. -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685392: better message when picasa is out of space
Package: shotwell Version: 0.12.3-2 Severity: wishlist Hi, When your free 1Gb of Picasa storage runs out, attempting to upload via Shotwell will result in 403 errors. As the Picasa API docs note, there is a way to determine how much space is left. https://developers.google.com/picasa-web/faq#quota It would be great if Shotwell could look at this information and indicate if the quote was all used up. Thanks, Anand -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679717: Help with unremoved files after purge
Hello Rene, Rene Engelhard r...@debian.org schrieb am 15.08.2012, 9:19 +0200: On Tue, Aug 14, 2012 at 06:44:08PM +0200, Rene Engelhard wrote: BUT better (and this is what almost all extensions INCLUDING voikko do since lng before you packaged this) is to unpack the extension into /usr/lib/libreoffice/share/extensions and do nothing (libreoffice-common has triggers which call the above). This new path and unpacked contents is a feature since OOo 3.3 iirc And note that even that sync_extensions is not needed anymore in 3.6.1 as I just learned - and that javasettingsunopkginstall.xml is gone. One more reason to migrate to the unpacked scenario because then you don't need *any* maintainer scipts here anymore. So do I need to call any trigger after extracting the files to this place? I've seen none in voikko. On a Debian wheezy, I get now dubious error messages („wrong operating system”), when selecting the corresponding menu entry in LibreOffice Writer. I'll test it again with the OXT installed by hand but I think it worked before. Voikko also installs the OXT under /usr/share/voikko, does this make sense? The old package was accessodf, the new one is libreoffice-accessodf, is there a transition needed? You can find the package at the following places: git://alioth.debian.org/git/pkg-a11y/accessodf.git http://crustulus.de/libreoffice-accessodf_0.1-1.2_all.deb Thanks Sebastian -- Blog (English | Deutsch): http://crustulus.de/blog Teste das freie Latein-Deutsch-Wörterbuch: http://freedict.org/dict?Form=dict3Database=lat-deu Freedict: Free multilingual dictionary databases - http://www.freedict.org signature.asc Description: Digital signature
Bug#684044: unblock: nodejs/0.6.19~dfsg1-4
On Mon, 20 Aug 2012, Adam D. Barratt wrote: The current practice is not to add packages which aren't already in wheezy to the release. Unblocking nodejs involves adding a package which isn't already in wheezy to the release. I'm not sure how unblocking it would therefore be anything other than diverging from current practice. In all honesty, I have never quite understood this practice. What purpose does it have to not allow new packages in wheezy? We're trying to avoid regressions and new packages have few chances of creating regressions (since they're new). Of course to avoid being overwhelmed with new packages (which could create supplementary workloads later in the freeze), you should not allow them by default. But when a maintainer does the effort to argue for its inclusion, he's likely also going to do the effort of keep it in a state where it's releasable (and if not, you can always use the large stick ok, but if anything goes wrong, we'll remove it again since you're going in too late). Coming back to this specificic case, we have lots of users of node and some popular node-based tools (I'm using node-less myself) so I feel that it's quite unproductive to keep those tools out of the release when a part of the delay has been due to the tech-ctte... Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org