Bug#733766: marked as done (libxmp: FTBFS on big endian arches: failed tests)

Your message dated Wed, 01 Jan 2014 09:49:11 + with message-id and subject line Bug#733766: fixed in libxmp 4.2.1+dfsg-2 has caused the Debian Bug report #733766, regarding libxmp: FTBFS on big endian arches: failed tests to be marked as done. This means that you claim that the problem has be

Processed: tagging 733391

Processing commands for cont...@bugs.debian.org: > tags 733391 + help Bug #733391 [src:abiword] abiword: FTBFS: itex2MML.y:298:25: error: 'ret_str' undeclared (first use in this function) Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 733391:

Bug#733727: wine32: /usr/lib/i386-linux-gnu/wine/bin/wine32: could not open

Package: wine32 Version: 1.6.1-10 Followup-For: Bug #733727 A workaround is to symlink /usr/lib/i386-linux-gnu/wine/bin/wine to /usr/lib/i386-linux-gnu/wine/bin/wine32. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (50

Processed: fixed 698231 in 1.4.5-1+deb6u1

Processing commands for cont...@bugs.debian.org: > fixed 698231 1.4.5-1+deb6u1 Bug #698231 {Done: Salvatore Bonaccorso } [memcached] memcached: CVE-2013-0179 Marked as fixed in versions memcached/1.4.5-1+deb6u1. > thanks Stopping processing here. Please contact me if you need assistance. -- 698

Bug#720816: openscenegraph uninstallable

Control: block 724686 by -1 Control: block 719402 by -1 Upstream may be releasing 3.2.1 soon, but there is still no definite date (http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/2013-December/065775.html). As far as I can tell, the only packaging change needed (beyond

Processed: Re: Bug#720816: openscenegraph uninstallable

Processing control commands: > block 724686 by -1 Bug #724686 [src:flightgear] flightgear: unbuildable on !linux archs 724686 was not blocked by any bugs. 724686 was blocking: 724678 Added blocking bug(s) of 724686: 720816 > block 719402 by -1 Bug #719402 [src:fgrun] fgrun: FTBFS: (.text+0x3d5): u

Bug#725557: marked as done (ruby-hpricot: FTBFS: ERROR: Test "ruby2.0" failed: /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require': cannot load such file -- fast_xs (LoadError))

Your message dated Wed, 1 Jan 2014 15:03:03 +0100 with message-id <20140101140302.ga20...@nq.home.zeha.at> and subject line Re: ruby-hpricot: FTBFS: ERROR: Test "ruby2.0" failed: /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require': cannot load such file -- fast_xs has caused t

Bug#730896: kexec-tools: FTBFS: stdc-predef.h:30:26: fatal error: bits/predefs.h: No such file or directory

Hi, Sorry for the answer time :) El Lunes, 16 de diciembre de 2013 12:23:52 Khalid Aziz escribió > I have tried to reproduce this problem multiple times so I could debug > it and have failed to reproduce it. Error message looks like issue with > glibc. buildd shows amd64 package for kexec-tools b

Bug#733643: memcached: diff for NMU version 1.4.13-0.3

Control: tags 706426 + patch pending Control: tags 733643 + patch pending Dear maintainer, I've prepared an NMU for memcached (versioned as 1.4.13-0.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Salvatore diff -Nru memcached-1.4.13/debian/chan

Processed: memcached: diff for NMU version 1.4.13-0.3

Processing control commands: > tags 706426 + patch pending Bug #706426 [memcached] memcached: CVE-2011-4971: remote denial of service Added tag(s) pending. > tags 733643 + patch pending Bug #733643 [memcached] memcached: CVE-2013-7239: SASL authentication allows wrong credentials to access memcac

Processed: memcached: diff for NMU version 1.4.13-0.3

Processing control commands: > tags 706426 + patch pending Bug #706426 [memcached] memcached: CVE-2011-4971: remote denial of service Ignoring request to alter tags of bug #706426 to the same tags previously set > tags 733643 + patch pending Bug #733643 [memcached] memcached: CVE-2013-7239: SASL a

Processed: Re: Bug#731753: gnome crashes on login but gnome-classic doesn't

Processing control commands: > severity -1 important Bug #731753 [gnome-shell] gnome crashes on login but gnome-classic doesn't Severity set to 'important' from 'serious' > tags -1 + moreinfo Bug #731753 [gnome-shell] gnome crashes on login but gnome-classic doesn't Added tag(s) moreinfo. -- 731

Bug#731753: gnome crashes on login but gnome-classic doesn't

Control: severity -1 important Control: tags -1 + moreinfo Le lundi 09 décembre 2013 à 07:34 -0500, Thomas Hehl a écrit : > Subject: gnome-shell: gnome crashes on login but gnome-classic does not > Package: gnome-shell > Version: 3.4.2-7+deb7u1 > Justification: can't use the GUI > Severity: seriou

Bug#733769: marked as done (evince-hwp: FTBFS: intltoolize: Command not found)

Your message dated Wed, 01 Jan 2014 15:19:12 + with message-id and subject line Bug#733769: fixed in evince-hwp 0.1.1-2 has caused the Debian Bug report #733769, regarding evince-hwp: FTBFS: intltoolize: Command not found to be marked as done. This means that you claim that the problem has be

Bug#733825: marked as done (apt-listchanges: missing dependency on dpkg-dev)

Your message dated Wed, 01 Jan 2014 15:18:56 + with message-id and subject line Bug#733825: fixed in apt-listchanges 2.85.13 has caused the Debian Bug report #733825, regarding apt-listchanges: missing dependency on dpkg-dev to be marked as done. This means that you claim that the problem has

Bug#715435: marked as done (nginx-naxsi-ui: fails to install: post-installation script returned error exit status 1)

Your message dated Wed, 01 Jan 2014 15:23:13 + with message-id and subject line Bug#715435: fixed in nginx 1.4.4-3 has caused the Debian Bug report #715435, regarding nginx-naxsi-ui: fails to install: post-installation script returned error exit status 1 to be marked as done. This means that

Processed: tagging 733002

Processing commands for cont...@bugs.debian.org: > tags 733002 + fixed-upstream Bug #733002 [src:mariadb-5.5] mariadb-5.5: FTBFS w/bison 3.x Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 733002: http://bugs.debian.org/cgi-bin/bugrepo

Bug#733184: marked as done (libmicrohttpd: FTBFS on kfreebsd-* (symbol errors))

Your message dated Wed, 01 Jan 2014 16:18:46 + with message-id and subject line Bug#733184: fixed in libmicrohttpd 0.9.33-1 has caused the Debian Bug report #733184, regarding libmicrohttpd: FTBFS on kfreebsd-* (symbol errors) to be marked as done. This means that you claim that the problem h

Bug#733869: python-stdnum: FTBFS: tries to access internet

Source: python-stdnum Version: 0.9-1 Severity: serious Justification: fails to build from source Dear Maintainer, Your package fails to build from source on machines which do not have internet connection. --8<-- running build_ext Searching for distribute Reading https://pypi.pyth

Processed: severity of 732199 is grave

Processing commands for cont...@bugs.debian.org: > # Makes the package currently useless in testing > severity 732199 grave Bug #732199 {Done: David Prévot } [xul-ext-greasemonkey] xul-ext-greasemonkey: Migrated to testing prematurely (unsuitable dependencies) Severity set to 'grave' from 'import

Bug#700406: marked as done (radare2-bindings: FTBFS: cp: cannot stat 'python/*.so': No such file or directory)

Your message dated Wed, 01 Jan 2014 17:00:07 + with message-id and subject line Bug#700406: fixed in radare2-bindings 0.9.6-1 has caused the Debian Bug report #700406, regarding radare2-bindings: FTBFS: cp: cannot stat 'python/*.so': No such file or directory to be marked as done. This means

Bug#707431: marked as done (radare2-bindings: FTBFS: ld: cannot find -lperl)

Your message dated Wed, 01 Jan 2014 17:00:07 + with message-id and subject line Bug#700406: fixed in radare2-bindings 0.9.6-1 has caused the Debian Bug report #700406, regarding radare2-bindings: FTBFS: ld: cannot find -lperl to be marked as done. This means that you claim that the problem ha

Bug#726800: marked as done (xzgv: fails to upgrade from wheezy, needs empty dummy prerm)

Your message dated Wed, 01 Jan 2014 17:03:35 + with message-id and subject line Bug#726800: fixed in xzgv 0.9.1-3 has caused the Debian Bug report #726800, regarding xzgv: fails to upgrade from wheezy, needs empty dummy prerm to be marked as done. This means that you claim that the problem ha

Bug#732853: marked as done (radare2: FTBFS on various archs)

Your message dated Wed, 01 Jan 2014 17:00:07 + with message-id and subject line Bug#732853: fixed in radare2 0.9.6-1 has caused the Debian Bug report #732853, regarding radare2: FTBFS on various archs to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#732578: Issue after conversion of AppArmor package to dh(1) and Multi-Arch

Hi, intrigeri wrote (27 Dec 2013 00:49:09 GMT) : > https://buildd.debian.org/status/fetch.php?pkg=apparmor&arch=i386&ver=2.8.0-4&stamp=1388104085 > says libapparmor-perl still lacks /usr/lib/perl5/LibAppArmor.pm. I can reproduce this by building -4 with pbuilder + a sid/i386 chroot and a sid/amd6

Bug#544709: marked as done (linux-image-2.6.30-1-686: /proc/acpi/button/lid/*/state always says "open")

Your message dated Wed, 01 Jan 2014 17:25:24 + with message-id and subject line Bug#733328: Removed package(s) from unstable has caused the Debian Bug report #544709, regarding linux-image-2.6.30-1-686: /proc/acpi/button/lid/*/state always says "open" to be marked as done. This means that yo

Bug#671079: marked as done (hotkey-setup: Please remove dependency on console-tools, which is being removed)

Your message dated Wed, 01 Jan 2014 17:25:24 + with message-id and subject line Bug#733328: Removed package(s) from unstable has caused the Debian Bug report #671079, regarding hotkey-setup: Please remove dependency on console-tools, which is being removed to be marked as done. This means th

Bug#730929: marked as done (ruby-parsetree: FTBFS: Hard dependency on ruby1.8)

Your message dated Wed, 01 Jan 2014 17:25:05 + with message-id and subject line Bug#713940: Removed package(s) from unstable has caused the Debian Bug report #730929, regarding ruby-parsetree: FTBFS: Hard dependency on ruby1.8 to be marked as done. This means that you claim that the problem h

Bug#709084: marked as done (fim SEGVs immediately)

Your message dated Wed, 01 Jan 2014 17:26:14 + with message-id and subject line Bug#733481: Removed package(s) from unstable has caused the Debian Bug report #709084, regarding fim SEGVs immediately to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#730331: marked as done (xmem: Needs update to libprocps1-dev)

Your message dated Wed, 01 Jan 2014 17:27:13 + with message-id and subject line Bug#733668: Removed package(s) from unstable has caused the Debian Bug report #730331, regarding xmem: Needs update to libprocps1-dev to be marked as done. This means that you claim that the problem has been dealt

Bug#730331: marked as done (xmem: Needs update to libprocps1-dev)

Your message dated Wed, 01 Jan 2014 17:27:25 + with message-id and subject line Bug#733668: Removed package(s) from unstable has caused the Debian Bug report #730331, regarding xmem: Needs update to libprocps1-dev to be marked as done. This means that you claim that the problem has been dealt

Bug#732235: brutalchess bugs #732235 and #732227

Hi Markus, Markus Koschany writes: > I'm attaching a debdiff with the latest changes of brutalchess that > fixes the FTBFS and the broken -p option. Unfortunately the only way to > fix the latter is to disable the "quake" option because those models > were never shipped by upstream. > > The chan

Bug#732235: brutalchess bugs #732235 and #732227

Hi Vincent, On 01.01.2014 18:22, Vincent Legout wrote: > Hi Markus, > > Markus Koschany writes: > >> I'm attaching a debdiff with the latest changes of brutalchess that >> fixes the FTBFS and the broken -p option. Unfortunately the only way to >> fix the latter is to disable the "quake" option

Processed: python-owncloud doesn't works with resent versions of libocsync >= 0.91.0

Processing control commands: > tag 733435 -pending Bug #733435 [src:pyowncloud] pyowncloud: FTBFS: dpkg-buildpackage: error: dpkg-source: error: unrepresentable changes to source Removed tag(s) pending. -- 733435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733435 733874: http://bugs.debia

Bug#733874: python-owncloud doesn't works with resent versions of libocsync >= 0.91.0

Package: python-owncloud Version: 0.3.1-1 Severity: grave Tags: upstream Justification: renders package unusable Forwarded: https://github.com/csawyerYumaed/pyOwnCloud/issues/61 Control: tag 733435 -pending python-owncloud is not able to use ocsync version > 0.91.0. But ocsync >= 0.91.0 is needed

Processed: block 733435 with 733874

Processing commands for cont...@bugs.debian.org: > block 733435 with 733874 Bug #733435 [src:pyowncloud] pyowncloud: FTBFS: dpkg-buildpackage: error: dpkg-source: error: unrepresentable changes to source 733435 was not blocked by any bugs. 733435 was not blocking any bugs. Added blocking bug(s) o

Bug#733875: broken on s390x

Package: samhain Version: 2.8.3a-1 Severity: grave Hi, samhain is broken in stable on s390x: } root@zani:~# /usr/sbin/samhain } assertion failed (x_dnmalloc.c): hashval < AMOUNTHASH } Aborted It'd be great if that could be fixed in wheezy also. Cheers, weasel -- To UNSUBSCRIBE, email to deb

Bug#732235: marked as done (brutalchess: FTBFS fatal error: freetype/freetype.h: No such file or directory)

Your message dated Wed, 01 Jan 2014 18:03:22 + with message-id and subject line Bug#732235: fixed in brutalchess 0.5.2+dfsg-5 has caused the Debian Bug report #732235, regarding brutalchess: FTBFS fatal error: freetype/freetype.h: No such file or directory to be marked as done. This means th

Processed: severity of 720244 is grave

Processing commands for cont...@bugs.debian.org: > severity 720244 grave Bug #720244 [src:ruby-netcdf] ruby-netcdf: FTBFS with ruby2.0: /usr/lib/ruby/2.0.0/rubygems/ext/builder.rb:60:in `run': extconf failed: (Gem::InstallError) Severity set to 'grave' from 'important' > thanks Stopping processi

Processed: found 709841 in 24.2.0esr-1

Processing commands for cont...@bugs.debian.org: > found 709841 24.2.0esr-1 Bug #709841 [iceweasel] iceweasel: spurious out of memory + crash (segmentation fault) Marked as found in versions iceweasel/24.2.0esr-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 7

Processed: tagging 732666

Processing commands for cont...@bugs.debian.org: > tags 732666 + pending Bug #732666 [libvirt-bin] libvirt-bin: special device cgroup_memory does not exist Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 732666: http://bugs.debian.org/cgi-bi

Bug#732666: [Pkg-libvirt-maintainers] Bug#732666: severity:serious, since it breaks the upgrade

On Tue, Dec 31, 2013 at 08:52:21PM +, Solveig wrote: > Severity: serious > found 732666 libvirt/1.2.0-1 > > thanks > > Setting up libvirt-bin (1.2.0-1) ... > [ ok ] Stopping libvirt management daemon: libvirtd not running. > [] Starting libvirt management daemon: libvirtdmount: special de

Bug#732666: marked as done (libvirt-bin: special device cgroup_memory does not exist)

Your message dated Wed, 01 Jan 2014 21:21:32 + with message-id and subject line Bug#732666: fixed in libvirt 1.2.0-2 has caused the Debian Bug report #732666, regarding libvirt-bin: special device cgroup_memory does not exist to be marked as done. This means that you claim that the problem ha

Bug#732666: [Pkg-libvirt-maintainers] Bug#732666: severity:serious, since it breaks the upgrade

Hi, Le 01/01/2014 20:24, Guido Günther a écrit : If you don't have memory cgroups enabled in the kernel you already broke the daemon restart yourself by configuring it in. The discussion is moot since we'll detect this dynamically in the future (with the next upload) but it's rather a configurat

Bug#733643: marked as done (memcached: CVE-2013-7239: SASL authentication allows wrong credentials to access memcache)

Your message dated Wed, 01 Jan 2014 21:47:14 + with message-id and subject line Bug#733643: fixed in memcached 1.4.13-0.2+deb7u1 has caused the Debian Bug report #733643, regarding memcached: CVE-2013-7239: SASL authentication allows wrong credentials to access memcache to be marked as done.

Bug#733184: libmicrohttpd: FTBFS on kfreebsd-* (symbol errors)

On Tue, 2013-12-31 at 14:40 +0100, Bertrand Marc wrote: > Thank you for reporting this FTBS. It seems that EXPORT.sym was ignored > due to a misconfiguration upstream. This was easily fixed after > contacting the main upstream coder. > > I prepared a new package fixing the list of exported symbols

Processed: Re: Bug#733869: python-stdnum: FTBFS: tries to access internet

Processing control commands: > tags -1 + pending Bug #733869 [src:python-stdnum] python-stdnum: FTBFS: tries to access internet Added tag(s) pending. -- 733869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To

Bug#733869: python-stdnum: FTBFS: tries to access internet

Control: tags -1 + pending On Wed, 2014-01-01 at 20:22 +0400, Dmitry Shachnev wrote: > Your package fails to build from source on machines which > do not have internet connection. Thanks. I think the wrong thing ended up in setup.py. Will do a new upload shortly. Thanks, -- -- arthur - adej...

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tag 733869 + pending Bug #733869 [src:python-stdnum] python-stdnum: FTBFS: tries to access internet Ignoring request to alter tags of bug #733869 to the same tags previously set > thanks Stopping processing here. Please contact me if you need ass

Bug#733869: marked as done (python-stdnum: FTBFS: tries to access internet)

Your message dated Wed, 01 Jan 2014 23:03:41 + with message-id and subject line Bug#733869: fixed in python-stdnum 0.9-2 has caused the Debian Bug report #733869, regarding python-stdnum: FTBFS: tries to access internet to be marked as done. This means that you claim that the problem has been

Bug#733727: marked as done (wine32: /usr/lib/i386-linux-gnu/wine/bin/wine32: could not open)

Your message dated Thu, 02 Jan 2014 01:34:22 + with message-id and subject line Bug#733727: fixed in wine 1.6.1-11 has caused the Debian Bug report #733727, regarding wine32: /usr/lib/i386-linux-gnu/wine/bin/wine32: could not open to be marked as done. This means that you claim that the probl

Bug#733846: pidgin: crash on startup: illegal hardware instruction / invalid opcode

It seems unlikely that pidgin is at fault here, given that it hasn't been updated in almost a year. Do you happen to have gstreamer0.10-buzztard installed? Does this still happen if you remove it? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe"

Bug#733846: pidgin: crash on startup: illegal hardware instruction / invalid opcode

On Wed, Jan 01, 2014 at 10:01:05PM -0500, Ari Pollak wrote: > It seems unlikely that pidgin is at fault here, given that it hasn't > been updated in almost a year. Do you happen to have > gstreamer0.10-buzztard installed? Does this still happen if you remove it? Yes, I had it installed and removin

Bug#733760: marked as done (kmod: FTBFS: command not found)

Your message dated Thu, 02 Jan 2014 03:21:10 + with message-id and subject line Bug#733760: fixed in kmod 16-2 has caused the Debian Bug report #733760, regarding kmod: FTBFS: command not found to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#733908: radare2-bindings: FTBFS: jni.h: No such file or directory

Source: radare2-bindings Version: 0.9.6-1 Severity: serious Justification: fails to build from source Builds of radare2-bindings in minimal environments (as on the autobuilders) have been failing: test_wrap.c:135:17: fatal error: jni.h: No such file or directory #include

Bug#731127: marked as done (libghc-xmonad-contrib-dev uninstallable on sid)

Your message dated Thu, 2 Jan 2014 04:45:35 + with message-id <20140102044535.ga11...@riva.ucam.org> and subject line Re: Bug#731127: [Pkg-haskell-maintainers] Bug#731127: libghc-xmonad-contrib-dev uninstallable on sid has caused the Debian Bug report #731127, regarding libghc-xmonad-contrib-d

Bug#733916: slim: memory corruption in slim child

Package: slim Version: 1.3.4-2 Severity: grave Justification: renders package unusable Dear Maintainer, when attempting to login with slim 1.3.4-2, the login screen keeps hanging after entering the correct username/password. An attached strace offered an error message I did not find in any other

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

Processing commands for cont...@bugs.debian.org: > # Thursday 2 January 07:03:12 UTC 2014 > # 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/geotranz";>geotranz > tags 729313

Bug#733917: linbox FTBFS: build failed on post-compile-test on mips/mipsel

Package: linbox Version: 1.3.2-1 Severity: serious Tags: sid patch Justification: FTBFS In an attempt to build libqb on mips/mipsel, build failed on testing: < PASS: test-charpoly < make[5]: *** Deleting file `test-det.log' < make[5]: *** [test-det.log] Terminated < make: *** [build-arch]