Processed: tagging 704426

Processing commands for cont...@bugs.debian.org: > tags 704426 + security Bug #704426 {Done: Michael Gilbert } [isc-dhcp] isc-dhcp: cve-2013-2494 Added tag(s) security. > thanks Stopping processing here. Please contact me if you need assistance. -- 704426: http://bugs.debian.org/cgi-bin/bugrepo

Processed: 703146 affects pbuilder

Processing commands for cont...@bugs.debian.org: > affects 703146 pbuilder Bug #703146 {Done: Christian Perrier } [debootstrap] apt: BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key (6.0/squeeze)? Bug #704190 {Done: Christian Perrier } [debootstrap] ltsp-build-client fails because of

Processed: Re: linux-image-3.2.0-4-amd64 fails to boot on apple iMac

Processing commands for cont...@bugs.debian.org: > # boot failure, hardware-specific, regression > severity 703468 important Bug #703468 [src:linux] linux-image-3.2.0-4-amd64 fails to boot on apple iMac Severity set to 'important' from 'grave' > End of message, stopping processing here. Please co

Processed: tagging 697619

Processing commands for cont...@bugs.debian.org: > tags 697619 + patch Bug #697619 [initramfs-tools] Many HID drivers not included in initramfs Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 697619: http://bugs.debian.org/cgi-bin/bugreport.cgi

Bug#703239: The failure to properly resize the window automatically is caused by, installation resetting this auto-resize feature

I would like to report that auto-resizing of root window now works as expected after tweaking the setting of virtualbox. I found out that the X11 root window did not resize automatically when the virtualbox window on the host (XP) changed its size because it seems that the setting for auto-resize

Processed: Re: [3.2.35-2 -> 3.2.39-1 regression] fails to boot on apple iMac

Processing commands for cont...@bugs.debian.org: > found 703468 linux/3.2.41-2 Bug #703468 [src:linux] linux-image-3.2.0-4-amd64 fails to boot on apple iMac Marked as found in versions linux/3.2.41-2. > quit Stopping processing here. Please contact me if you need assistance. -- 703468: http://bu

Bug#703468: [3.2.35-2 -> 3.2.39-1 regression] fails to boot on apple iMac

found 703468 linux/3.2.41-2 quit Jonathan Nieder wrote: > I think a good place to start would be to try 3.2.41-2 from unstable, > since it includes some i915 fixes. Ah, looking back over the log I see that's been tried. So: > A good next step would be to try 3.8.y from experimental. If it > w

Bug#703468: [3.2.35-2 -> 3.2.39-1 regression] fails to boot on apple iMac

Hi, Michael Gilbert wrote: >> The following string is still recognizable: >> i915_gem_init_ppgtt+0x93/0x16c [i915] > > This is going to take some work on your end to get fixed. 3.2.39-1 > included backported patches from aspects of the i915 driver. I think a good place to start would be to try

Bug#703468: linux-image-3.2.0-4-amd64 fails to boot on apple iMac

> The following string is still recognizable: > i915_gem_init_ppgtt+0x93/0x16c [i915] This is going to take some work on your end to get fixed. 3.2.39-1 included backported patches from aspects of the i915 driver. To help, you could do some testing by unapplying those patches and rebuilding the

Bug#704251: marked as done ([fp-compiler] On upgrade, update-alternatives error may occur)

Your message dated Sun, 31 Mar 2013 21:25:50 -0400 with message-id and subject line re: [fp-compiler] On upgrade, update-alternatives error may occur has caused the Debian Bug report #704251, regarding [fp-compiler] On upgrade, update-alternatives error may occur to be marked as done. This mean

Bug#634560: marked as done (r-cran-rjags: FTBFS: configure: error: "JAGS module directory /usr/lib/JAGS/modules-2.2.0 does not exist.")

Your message dated Sun, 31 Mar 2013 21:10:00 -0400 with message-id <20130401010959.ga3...@lordsutch.dyndns.org> and subject line Fixed quite a while ago has caused the Debian Bug report #634560, regarding r-cran-rjags: FTBFS: configure: error: "JAGS module directory /usr/lib/JAGS/modules-2.2.0 doe

Bug#704257: marked as done (missing dependency)

Your message dated Mon, 1 Apr 2013 02:52:12 +0200 with message-id <20130401025212.08c6e...@fornost.bigon.be> and subject line Re: missing dependency has caused the Debian Bug report #704257, regarding missing dependency to be marked as done. This means that you claim that the problem has been deal

Bug#659390: bug#670232

On Sun, Mar 31, 2013 at 08:04:26PM -0400, Antoine Beaupré wrote: > Hi Ana, and others, > > I will not have time to process this bug in the next two weeks, feel > free to NMU or RM. > I looked into it and after populating the database by hand and also fixing manually the initial issue [1]. It does

Bug#704426: marked as done (isc-dhcp: cve-2013-2494)

Your message dated Mon, 01 Apr 2013 00:32:47 + with message-id and subject line Bug#704426: fixed in isc-dhcp 4.2.4-6 has caused the Debian Bug report #704426, regarding isc-dhcp: cve-2013-2494 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#659390: bug#670232

Hi Ana, and others, I will not have time to process this bug in the next two weeks, feel free to NMU or RM. A. -- Evil exists to glorify the good. Evil is negative good. It is a relative term. Evil can be transmuted into good. What is evil to one at one time, becomes good at another time to som

Bug#704426: isc-dhcp: cve-2013-2494

package: isc-dhcp severity: serious version: 4.2.2.dfsg.1-5 The embedded bind library is affected by the subject issue. I am currently working on fixed packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lis

Processed: Re: closing 658295, closing 659390

Processing commands for cont...@bugs.debian.org: > # the pending was to fix a minor bug, reported in the same bug report... > tag 659390 -pending Bug #659390 [semanticscuttle] semanticscuttle: config.default.php not found Removed tag(s) pending. > thanks Stopping processing here. Please contact m

Bug#704423: marked as done (systemd: gdm does not start, user sessions have multiple issues, root session works normally)

Your message dated Mon, 01 Apr 2013 00:35:18 +0200 with message-id <5158ba26.9020...@debian.org> and subject line Re: Bug#704423: systemd: gdm does not start, user sessions have multiple issues, root session works normally has caused the Debian Bug report #704423, regarding systemd: gdm does not s

Processed: Re: non-free license: requires to obey US export regulation even, when not in the US

Processing control commands: > retitle -1 please include correct license in upstream tarball Bug #700169 [src:acpica-unix] non-free license: requires to obey US export regulation even when not in the US Changed Bug title to 'please include correct license in upstream tarball' from 'non-free lice

Bug#700169: non-free license: requires to obey US export regulation even, when not in the US

Control: retitle -1 please include correct license in upstream tarball Control: severity -1 normal Michael Stapelberg writes: > Can we just ignore this bug for wheezy? To me, the licensing intention > seems very clear. I think that's fine. The package seems to be also licensed under the GPL-2 ev

Bug#704423: systemd: gdm does not start, user sessions have multiple issues, root session works normally

...Wow, I feel really dumb right now. That was all it took to get things working. Thank you so much! (I have to wonder now, though... if that package is necessary to make things work properly, why isn't a dependency of the package?) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.d

Bug#704423: systemd: gdm does not start, user sessions have multiple issues, root session works normally

Get us a debug log of the boot process [1] > ii util-linux 2.20.1-5.3 > > Versions of packages systemd recommends: > pn libpam-systemd Make sure to install libpam-systemd. Michael [1] http://freedesktop.org/wiki/Software/systemd/Debugging -- Why is it that all of the instrument

Bug#704300: [scuttle]

Hi, could you try changing second line in /usr/share/scuttle/www/header.inc.php from ini_set('display_errors', '1'); to ini_set('display_errors', '0'); ? This should silence those warnings not to appear in a browser window. It's a crude hack, of course. Cheers, Jan -- To UNSUBSCRIBE, em

Bug#704423: systemd: gdm does not start, user sessions have multiple issues, root session works normally

Package: systemd Version: 44-11 Severity: grave Justification: renders package unusable Dear Maintainer, ***I'm marking this as grave because it causes some fairly serious usability issues for me, if you feel this status is incorrect please feel free to change it.*** As you might know, much of G

Bug#704422: dovecot-solr: Segfault using dovecot-solr plug-in

Package: dovecot-solr Version: 1:2.1.7-7 Severity: grave Justification: renders package unusable Dear Maintainer, After setting up a tomcat-solr instance, if I try to use the dovecot-solr plug-in, I get segfaults on login. I modified my dovecot.conf as follows: mail_plugins = $mail_plugins

Bug#703358: marked as done (virtualbox-guest-dkms: vboxvideo_drm.c fails to compile after upgrade of linux-headers-3.2.0-4 from 3.2.35-2 to 3.2.39-2)

Your message dated Sun, 31 Mar 2013 20:52:05 + with message-id and subject line Bug#703358: fixed in virtualbox 4.1.18-dfsg-2+deb7u1 has caused the Debian Bug report #703358, regarding virtualbox-guest-dkms: vboxvideo_drm.c fails to compile after upgrade of linux-headers-3.2.0-4 from 3.2.35-2

Bug#703239: marked as done (virtualbox-guest-x11: Bad return status for module build on kernel)

Your message dated Sun, 31 Mar 2013 20:52:05 + with message-id and subject line Bug#703358: fixed in virtualbox 4.1.18-dfsg-2+deb7u1 has caused the Debian Bug report #703358, regarding virtualbox-guest-x11: Bad return status for module build on kernel to be marked as done. This means that you

Bug#703823: marked as done (amarok: Not installable)

Your message dated Sun, 31 Mar 2013 22:39:35 +0200 with message-id <51589f07.1050...@gmail.com> and subject line Closing has caused the Debian Bug report #703823, regarding amarok: Not installable to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#614498: svn 90

hi I tried guppy SVN 90. It works with python 2.7 in Debian wheezy. a. -- Andrea Mennucc "E' un mondo difficile. Che vita intensa!" (Tonino Carotone) signature.asc Description: Digital signature

Processed: tagging as pending bugs that are closed by packages in NEW

Processing commands for cont...@bugs.debian.org: > # Sunday 31 March 19:03:13 UTC 2013 > # Tagging as pending bugs that are closed by packages in NEW > # http://ftp-master.debian.org/new.html > # > # Source package in NEW: href="http://packages.qa.debian.org/virtualbox";>virtualbox > tags 703358

Processed: Re: open-vm-tools: fails to upgrade do failing to stop the old daemon

Processing commands for cont...@bugs.debian.org: > severity 686200 minor Bug #686200 [open-vm-tools] open-vm-tools: fails to upgrade do failing to stop the old daemon Severity set to 'minor' from 'serious' > retitle 686200 doesn't need the additional sleep 1 in init anymore Bug #686200 [open-vm-t

Bug#686200: open-vm-tools: fails to upgrade do failing to stop the old daemon

severity 686200 minor retitle 686200 doesn't need the additional sleep 1 in init anymore thanks Bernd Zeimetz wrote: > you've added the one second sleep "fix" to the init script again i have not added it, i kept it, and included a non-intrusive version of the patch you did in the NMU (see 2:9.2.

Bug#704418: openjdk-7: Re: Your message to Ubuntu-devel-discuss awaits moderator approval

Source: openjdk-7 Version: 7u17-2.3.8-1 Severity: serious The maintainer address bounces as it switched to the Ubuntu devel mailing list: ubuntu-devel-discuss-boun...@lists.ubuntu.com writes: > Your mail to 'Ubuntu-devel-discuss' with the subject > > Processing of openjdk-7_7u17-2.3.8-1_amd64

Bug#695224: Locale::Maketext versioning in perl package

Dear release team, There is a problem with the perl package, as discussed in onwards, whereby the application of the security fix in that ticket now causes double-escaping problems where people workaround the problem by escaping themsel

Bug#704190: ltsp-build-client fails because of apt GPG error

Control: tags 704190 confirmed On Sun, Mar 31, 2013 at 03:37:25PM +0200, Peter Tuharsky wrote: > thanks for reply. Both mirrors You gave don't work, ltsp-build-client ends > with > error such as: > > E: unknown location http.debian.net/debian/dists/wheezy/InRelease > error: LTSP client installat

Processed: Re: Bug#704190: ltsp-build-client fails because of apt GPG error

Processing control commands: > tags 704190 confirmed Bug #704190 {Done: Christian Perrier } [debootstrap] ltsp-build-client fails because of apt GPG error Bug #703146 {Done: Christian Perrier } [debootstrap] apt: BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key (6.0/squeeze)? Added t

Bug#659861: Processed: your mail

Adam D. Barratt dixit: > I don't think you can (in either case). You can mark a bug as found / fixed in > a binary version, but the BTS will translate that to the corresponding source > version. Similarly bug versions apply to the package, not to particular > architectures. Hrm. > I think the cl

Bug#704190: ltsp-build-client fails because of apt GPG error

Package: debootstrap Version: 1.0.44 Followup-For: Bug #704190 Vagrant, thanks for reply. Both mirrors You gave don't work, ltsp-build-client ends with error such as: E: unknown location http.debian.net/debian/dists/wheezy/InRelease error: LTSP client installation ended abnormally I don't see a

Bug#659390: closing 658295, closing 659390

unarchive 659390 reopen 659390 found 659390 0.98.4+dfsg-1 severity 659390 grave thanks On Sun, Aug 19, 2012 at 04:53:33PM -0400, David Prévot wrote: > close 658295 0.98.4+dfsg-1 > close 659390 0.98.4+dfsg-1 > thanks > The bugs have not been closed automatically because they were fixed in > version

Bug#659390: bug#670232

On Sun, Mar 31, 2013 at 03:23:23PM +0200, Ana Guerrero wrote: > unarchive 659390 > reopen 659390 > found 659390 0.98.4+dfsg-1 > severity 659390 grave > thanks > > On Sun, Aug 19, 2012 at 04:53:33PM -0400, David Prévot wrote: > > close 658295 0.98.4+dfsg-1 > > close 659390 0.98.4+dfsg-1 > > thanks

Processed: Re: closing 658295, closing 659390

Processing commands for cont...@bugs.debian.org: > unarchive 659390 Bug #659390 {Done: David Prévot } [semanticscuttle] semanticscuttle: config.default.php not found Unarchived Bug 659390 > reopen 659390 Bug #659390 {Done: David Prévot } [semanticscuttle] semanticscuttle: config.default.php not

Bug#659861: Processed: your mail

On 31.03.2013 00:17, Thorsten Glaser wrote: Adam D. Barratt dixit: In which case it should probably be closed, as it doesn't apply to any current package in the archive and no changes in the package are required to resolve it. OK. Hrm. How do I tell the BTS’ version tracking that it’s fixe

Bug#704111: marked as done (clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting.)

Your message dated Sun, 31 Mar 2013 12:32:44 + with message-id and subject line Bug#704111: fixed in clang 1:3.0-6.2 has caused the Debian Bug report #704111, regarding clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting. to be

Bug#704266: libdr-tarantool-perl: FTBFS: test failure: t/110-netsplit-readahead.t

On Sat, Mar 30, 2013 at 05:23:25PM +, Dominic Hargreaves wrote: > Source: libdr-tarantool-perl > Version: 0.35-1 > Severity: serious > Justification: FTBFS > Tags: sid > > This package FTBFS in a clean sid chroot: > > # Failed test 'delay maximum' > # at t/110-netsplit-readahead.t line 14

Bug#704267: libdr-tarantool-perl: FTBFS: test failure: t/050-async-client.t

On Sun, Mar 31, 2013 at 12:54:32PM +0100, Dominic Hargreaves wrote: > > FWIW it didn't fail here in a sid am64 chroot. > > True; in sid, the failure (with 0.15-1) seems to come at > > # Failed test 'errstr' > # at t/020-low_level_client.t line 125. > # 'Duplicate key exists

Bug#704267: libdr-tarantool-perl: FTBFS: test failure: t/050-async-client.t

On Sun, Mar 31, 2013 at 04:00:24PM +0600, Andrey Rahmatullin wrote: > On Sat, Mar 30, 2013 at 05:37:27PM +, Dominic Hargreaves wrote: > > In a clean wheezy chroot: > > > > ok 51 - code > > not ok 52 - errstr > > > > # Failed test 'errstr' > > # at t/050-async-client.t line 268. > > #

Bug#704267: libdr-tarantool-perl: FTBFS: test failure: t/050-async-client.t

On Sat, Mar 30, 2013 at 05:37:27PM +, Dominic Hargreaves wrote: > In a clean wheezy chroot: > > ok 51 - code > not ok 52 - errstr > > # Failed test 'errstr' > # at t/050-async-client.t line 268. > # 'Lua error: stack overflow (call: out of stack)' > # doesn't match '

Bug#704278: marked as done (anarchism won't start because of missing init script)

Your message dated Sun, 31 Mar 2013 15:57:35 +0600 with message-id <20130331095735.ga17...@belkar.wrar.name> and subject line Re: Bug#704278: anarchism won't start because of missing init script has caused the Debian Bug report #704278, regarding anarchism won't start because of missing init scrip