Bug#714699: [Pkg-libvirt-maintainers] Bug#714699: libvirt: CVE-2013-2218: crash when listing network interfaces with filters

2013-07-01 Thread Guido Günther
On Mon, Jul 01, 2013 at 10:43:07PM +0200, Salvatore Bonaccorso wrote: Package: libvirt Version: 1.0.6-1 Severity: grave Tags: security upstream patch fixed-upstream Hi, the following vulnerability was published for libvirt. CVE-2013-2218[0]: crash when listing network interfaces with

Bug#711116: gdm3 don't start - GLib-CRITICAL: g_variant_compare

2013-07-01 Thread Shiva Iyer
Package: gdm3 Version: 3.4.1-9 Followup-For: Bug #76 I have version 3.4.1-9 of gdm3 installed, but I still have this issue. I am only able to use Gnome in fallback mode. When I try Gnome shell, the error message in the subject line is logged to /var/log/gdm3/:0-slave.log and the screen just

Bug#713274: marked as done (kiki-the-nano-bot: FTBFS: --configdir: not found)

2013-07-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Jul 2013 22:48:08 + with message-id e1utmte-0007cj...@franck.debian.org and subject line Bug#713274: fixed in kiki-the-nano-bot 1.0.2+dfsg1-5 has caused the Debian Bug report #713274, regarding kiki-the-nano-bot: FTBFS: --configdir: not found to be marked as done.

Processed: [bts-link] source package clutter-1.0

2013-07-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package clutter-1.0 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to

Processed: primus bug triaging

2013-07-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: # I guess we have to unmark the bug as found in the version # in unstable for britney to let us migrate to testing? notfound 712666 0~20130601-1 Bug #712666 [primus] primus: fatal: failed to load PRIMUS_LOAD_GLOBAL Ignoring request to alter

Processed (with 1 errors): primus bug triaging

2013-07-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: # I guess we have to unmark the bug as found in the version in unstable for britney to let us migrate to testing? Unknown command or malformed arguments to command. notfound 712666 0~20130601-1 Bug #712666 [primus] primus: fatal: failed to load

Bug#710727: marked as done (awffull: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/awffull/examples/sample.conf.gz)

2013-07-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Jul 2013 23:18:01 + with message-id e1utnm9-0006co...@franck.debian.org and subject line Bug#710727: fixed in awffull 3.10.2-3 has caused the Debian Bug report #710727, regarding awffull: postinst uses /usr/share/doc content (Policy 12.3):

Bug#710733: marked as done (monsterz-data: fails to upgrade from 'testing' - trying to overwrite /usr/share/games/monsterz/graphics/icon.png)

2013-07-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Jul 2013 23:18:33 + with message-id e1utnmf-0006kb...@franck.debian.org and subject line Bug#710733: fixed in monsterz 0.7.1-7 has caused the Debian Bug report #710733, regarding monsterz-data: fails to upgrade from 'testing' - trying to overwrite

Bug#714707: nagios3-cgi: fails to install: subprocess installed post-installation script returned error exit status 10

2013-07-01 Thread Andreas Beckmann
Package: nagios3-cgi Version: 3.4.1-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the

Processed: user debian...@lists.debian.org, usertagging 669769, severity of 669769 is serious ...

2013-07-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). usertags 669769 piuparts There were no usertags set. Usertags are now: piuparts. severity 669769 serious Bug #669769 {Done: Georges Khaznadar

Bug#714547: marked as done (gnome-panel: Gnome-panel does not appear)

2013-07-01 Thread Debian Bug Tracking System
Your message dated Tue, 02 Jul 2013 02:21:35 +0200 with message-id 51d21d0f.9080...@debian.org and subject line gnome-shell: Execution of main.js threw exception: TypeError: GnomeBluetoothApplet.KillswitchState is undefined has caused the Debian Bug report #714547, regarding gnome-panel:

Bug#712861: marked as done (gnome-bluetooth: Breaks gnome-shell: GnomeBluetoothApplet.KillswitchState is undefined)

2013-07-01 Thread Debian Bug Tracking System
Your message dated Tue, 02 Jul 2013 02:21:35 +0200 with message-id 51d21d0f.9080...@debian.org and subject line gnome-shell: Execution of main.js threw exception: TypeError: GnomeBluetoothApplet.KillswitchState is undefined has caused the Debian Bug report #714547, regarding gnome-bluetooth:

Bug#714545: marked as done (gnome doesn't start)

2013-07-01 Thread Debian Bug Tracking System
Your message dated Tue, 02 Jul 2013 02:21:35 +0200 with message-id 51d21d0f.9080...@debian.org and subject line gnome-shell: Execution of main.js threw exception: TypeError: GnomeBluetoothApplet.KillswitchState is undefined has caused the Debian Bug report #714547, regarding gnome doesn't start

Bug#712926: marked as done (gnome-shell: Execution of main.js threw exception: TypeError: GnomeBluetoothApplet.KillswitchState is undefined)

2013-07-01 Thread Debian Bug Tracking System
Your message dated Tue, 02 Jul 2013 02:21:35 +0200 with message-id 51d21d0f.9080...@debian.org and subject line gnome-shell: Execution of main.js threw exception: TypeError: GnomeBluetoothApplet.KillswitchState is undefined has caused the Debian Bug report #714547, regarding gnome-shell:

Bug#714711: libfolia: FTBFS: No package 'ticcutils' found

2013-07-01 Thread Aaron M. Ucko
Source: libfolia Version: 0.10-4 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of libfolia in minimal environments (as on the autobuilders) have been failing: checking for ticcutils... no configure: error: Package requirements

Bug#714712: postgis: FTBFS - mvn: not found (missing B-D on maven)

2013-07-01 Thread Aaron M. Ucko
Source: postgis Version: 2.0.3-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of postgis in minimal environments (as on the autobuilders) have been failing: cd /«PKGBUILDDIR»/java/jdbc mvn --offline

Bug#714715: Rygel segmentation fault to open

2013-07-01 Thread Fernando Ike
Package: rygel Version: 0.19.3-1 Severity: grave Hi! I'm have a problem to open Rygel. It's segmentation fault. Below is gdb output fike@klatoon:~$ gdb rygel GNU gdb (GDB) 7.6 (Debian 7.6-4) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

Bug#710211: Current and upcoming toolchain changes for jessie

2013-07-01 Thread Steve M. Robbins
Hi Daniel, I'd like some more information regarding these two bugs, where Boost has defined but not used a local typedef. On Fri, Jun 14, 2013 at 09:24:20AM +0800, Daniel Hartwig wrote: severity 710210 serious severity 710211 serious So a serious bug is defined as: a severe violation of

Bug#713540: marked as done (ddccontrol: FTBFS: ld: notebook.o: undefined reference to symbol 'round@@GLIBC_2.2.5')

2013-07-01 Thread Debian Bug Tracking System
Your message dated Tue, 02 Jul 2013 03:03:58 + with message-id e1utqso-0002tq...@franck.debian.org and subject line Bug#713540: fixed in ddccontrol 0.4.2-11 has caused the Debian Bug report #713540, regarding ddccontrol: FTBFS: ld: notebook.o: undefined reference to symbol

Processed: severity of 693604 is important

2013-07-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: severity 693604 important Bug #693604 [avahi-daemon] avahi-daemon takes 100% CPU right after boot and at every restart of CUPS Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need

Bug#714595: liballegro4.2-dev: not installable in sid

2013-07-01 Thread Ralf Treinen
On Mon, Jul 01, 2013 at 10:07:31PM +0200, Tobias Hansen wrote: the dev package is now called liballegro4-dev. If you still think there is a bug, please explain again. But liballegro4.2-dev is still there : % rmadison -s sid liballegro4.2-dev liballegro4.2-dev | 2:4.4.2-2.1 | sid | amd64,

<    1   2