Processed: Re: Bug#625828: libipc-sharelite-perl: FTBFS on armel: test failures

Processing commands for cont...@bugs.debian.org: > tags 625828 + squeeze Bug #625828 [libipc-sharelite-perl] libipc-sharelite-perl: FTBFS on armel: test failures Added tag(s) squeeze. > thanks Stopping processing here. Please contact me if you need assistance. -- 625828: http://bugs.debian.org/

Bug#625828: libipc-sharelite-perl: FTBFS on armel: test failures

tags 625828 + squeeze thanks On Fri, May 06, 2011 at 12:38:42PM +0300, Niko Tyni wrote: > Package: libipc-sharelite-perl > Version: 0.17-1 > Severity: serious > Tags: wheezy sid > User: debian-p...@lists.debian.org > Usertags: perl-5.12-transition > > This package failed to build on armel only ag

Bug#624469: Intermittent failure to start.

On May 08, Josh Triplett wrote: > Any chance this represents a conflict with udev from the initramfs? This is the only explanation, but in this case you should see the old process with ps. Try again by immediately running something like "strace -v -s 200 udevd" at the shell prompt so we can see e

Bug#624469: Intermittent failure to start.

Package: udev Version: 168-1 Followup-For: Bug #624469 One more note: this occurred after a fresh install of stable and upgrade to unstable, with no unusual steps taken. - Josh Triplett -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Archi

Processed: severity of 624469 is serious

Processing commands for cont...@bugs.debian.org: > # Makes the system unusable without manually starting udev at boot time after > a delay > severity 624469 serious Bug #624469 [udev] Fails to start: failed to bind control socket (address in use) Severity set to 'serious' from 'important' > tha

Bug#626028: bliss: FTBFS: AMD64-specific .symbols

Source: bliss Version: 0.71-1 Severity: serious Justification: fails to build from source Builds of bliss are failing on nearly all architectures because debian/libbliss1d.symbols wound up listing as mandatory some symbols that g++ defines only on AMD64 (including kfreebsd-amd64). Could you pleas

Bug#626025: console-setup: FTBFS: Bad number of antecedents at ./ckbcomp line 3078, line 372.

Source: console-setup Version: 1.73 Severity: serious From my pbuilder build log: ... ./fbsdmap --terminfo >terminfo ./fbsdmap --termcap >termcap make[2]: Leaving directory `/tmp/buildd/console-setup-1.73/Fonts' cd Keyboard && /usr/bin/make build-mini-linux make[2]: Entering directory `/tmp/build

Processed: limit source to digikam, tagging 620873, tagging 622266, tagging 620676

Processing commands for cont...@bugs.debian.org: > #digikam (2:1.9.0-2) UNRELEASED; urgency=low > # > # * Rebuild against experimental KDE SC 4.6.2 > #- Fixes "Experimental: uninstallable" (Closes: #620676) > #- Fixes "Experimental: digikam and showfoto don't start" (Closes: > #620873) >

Bug#625825: Fixed in gcc-4.6.0-7, please revert the work around

Fixed in gcc-4.6.0-7, please revert the work around. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#555175: marked as done (FTBFS with binutils-gold)

Your message dated Sun, 8 May 2011 01:29:45 +0100 with message-id and subject line Re: FTBFS with binutils-gold has caused the Debian Bug report #555175, regarding FTBFS with binutils-gold to be marked as done. This means that you claim that the problem has been dealt with. If this is not the cas

Bug#615751: marked as done (matchbox-panel: ftbfs with gold or ld --no-add-needed)

Your message dated Sat, 07 May 2011 23:51:41 + with message-id and subject line Bug#615751: fixed in matchbox-panel 0.9.3-4 has caused the Debian Bug report #615751, regarding matchbox-panel: ftbfs with gold or ld --no-add-needed to be marked as done. This means that you claim that the proble

Bug#555590: marked as done (FTBFS with binutils-gold)

Your message dated Sat, 07 May 2011 23:51:54 + with message-id and subject line Bug#90: fixed in matchbox-panel-manager 0.1-4 has caused the Debian Bug report #90, regarding FTBFS with binutils-gold to be marked as done. This means that you claim that the problem has been dealt with.

Bug#555589: marked as done (FTBFS with binutils-gold)

Your message dated Sat, 07 May 2011 23:51:41 + with message-id and subject line Bug#89: fixed in matchbox-panel 0.9.3-4 has caused the Debian Bug report #89, regarding FTBFS with binutils-gold to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#555468: marked as done (FTBFS with binutils-gold)

Your message dated Sat, 07 May 2011 23:51:27 + with message-id and subject line Bug#555468: fixed in liquidwar 5.6.4-3 has caused the Debian Bug report #555468, regarding FTBFS with binutils-gold to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#625038: marked as done (plee-the-bear: FTBFS: avl_base.hpp:137:15: error: 'ptrdiff_t' does not name a type)

Your message dated Sat, 07 May 2011 23:49:56 + with message-id and subject line Bug#625038: fixed in libclaw 1.6.1-4 has caused the Debian Bug report #625038, regarding plee-the-bear: FTBFS: avl_base.hpp:137:15: error: 'ptrdiff_t' does not name a type to be marked as done. This means that yo

Bug#624919: marked as done (libclaw: FTBFS: avl_base.hpp:137:15: error: 'ptrdiff_t' does not name a type)

Your message dated Sat, 07 May 2011 23:49:56 + with message-id and subject line Bug#624919: fixed in libclaw 1.6.1-4 has caused the Debian Bug report #624919, regarding libclaw: FTBFS: avl_base.hpp:137:15: error: 'ptrdiff_t' does not name a type to be marked as done. This means that you clai

Bug#624878: marked as done (vtk: FTBFS: metaUtils.cxx:805:3: error: 'ptrdiff_t' was not declared in this scope)

Your message dated Sat, 07 May 2011 23:10:48 + with message-id and subject line Bug#624878: fixed in vtk 5.6.1-5 has caused the Debian Bug report #624878, regarding vtk: FTBFS: metaUtils.cxx:805:3: error: 'ptrdiff_t' was not declared in this scope to be marked as done. This means that you cl

Bug#556491: marked as done (FTBFS with binutils-gold)

Your message dated Sat, 07 May 2011 23:07:11 + with message-id and subject line Bug#556491: fixed in terminatorx 3.82-7.4 has caused the Debian Bug report #556491, regarding FTBFS with binutils-gold to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#626020: zookeeper: FTBFS on mips: The method close() of type FileSnap must override a superclass method

Source: zookeeper Version: 3.3.1+dfsg1-2 Severity: serious Justification: fails to build from source zookeeper FTBFS on mips: [javac] -- [javac] 12. ERROR in /build/buildd-zookeeper_3.3.1+dfsg1-2+b1-mips-QpsLaC/zookeeper-3.3.1+dfsg1/src/java/mai [javac] n/org/apache/zookeepe

Bug#626019: libsane-perl: FTBFS on sparc (test hang?)

Package: libsane-perl Version: 0.03-1 Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) See https://buildd.debian.org/status/fetch.php?pkg=libsane-perl&arch=sparc&ver=0.03-1%2Bb1&stamp=1304502766 dh_auto_test make[1]: Entering dir

Bug#625150: marked as done (matplotlib: FTBFS: ln: creating symbolic link `/build/user-matplotlib_0.99.3-1-amd64-C4ZThE/matplotlib-0.99.3/debian/python-matplotlib-doc/usr/share/doc/python-matplotlib-d

Your message dated Sat, 07 May 2011 22:50:01 + with message-id and subject line Bug#625150: fixed in matplotlib 1.0.1-2 has caused the Debian Bug report #625150, regarding matplotlib: FTBFS: ln: creating symbolic link `/build/user-matplotlib_0.99.3-1-amd64-C4ZThE/matplotlib-0.99.3/debian/pyth

Bug#555588: marked as done (FTBFS with binutils-gold)

Your message dated Sat, 07 May 2011 22:49:28 + with message-id and subject line Bug#88: fixed in matchbox-keyboard 0.1+svn20080916-5 has caused the Debian Bug report #88, regarding FTBFS with binutils-gold to be marked as done. This means that you claim that the problem has been dealt

Bug#555587: marked as done (FTBFS with binutils-gold)

Your message dated Sat, 07 May 2011 22:49:11 + with message-id and subject line Bug#87: fixed in matchbox-desktop 2.0-2 has caused the Debian Bug report #87, regarding FTBFS with binutils-gold to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#555284: marked as done (FTBFS with binutils-gold)

Your message dated Sat, 07 May 2011 22:44:58 + with message-id and subject line Bug#555284: fixed in libmatchbox 1.9-6 has caused the Debian Bug report #555284, regarding FTBFS with binutils-gold to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#625953: marked as done (linux-2.6: orinoco_pci module is no longer present)

Your message dated Sat, 07 May 2011 23:40:19 +0100 with message-id <1304808019.3203.149.camel@localhost> and subject line Re: Bug#625953: linux-2.6: orinoco_pci module is no longer present has caused the Debian Bug report #625953, regarding linux-2.6: orinoco_pci module is no longer present to be

Bug#619281: marked as done (hdf5: FTBFS: Error: Kind 16 not supported for type REAL)

Your message dated Sat, 07 May 2011 22:32:27 + with message-id and subject line Bug#619281: fixed in hdf5 1.8.6-2 has caused the Debian Bug report #619281, regarding hdf5: FTBFS: Error: Kind 16 not supported for type REAL to be marked as done. This means that you claim that the problem has be

Bug#625893: marked as done (c++-4.5: not found)

Your message dated Sat, 07 May 2011 22:24:50 + with message-id and subject line Bug#625893: fixed in dragonegg 2.8-3 has caused the Debian Bug report #625893, regarding c++-4.5: not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#618768: marked as done (llvm-gcc-4.5: Incompatible plugin version (dragonegg.so))

Your message dated Sat, 07 May 2011 22:24:50 + with message-id and subject line Bug#618768: fixed in dragonegg 2.8-3 has caused the Debian Bug report #618768, regarding llvm-gcc-4.5: Incompatible plugin version (dragonegg.so) to be marked as done. This means that you claim that the problem ha

Bug#625110: marked as done (caret: FTBFS: StatisticRandomNumberOperator.h:38:7: error: 'ptrdiff_t' does not name a type)

Your message dated Sat, 07 May 2011 22:20:16 + with message-id and subject line Bug#625110: fixed in caret 5.6.2~dfsg.1-3 has caused the Debian Bug report #625110, regarding caret: FTBFS: StatisticRandomNumberOperator.h:38:7: error: 'ptrdiff_t' does not name a type to be marked as done. This

Bug#614175: confirm liblua5.1-filesystem0

Downgrading liblua5.1-filesystem0 to stable gets prosody working again. -- see shy jo signature.asc Description: Digital signature

Bug#618696: closed by Adam C Powell IV (Re: elmer: multiple licensing issues)

Le samedi 07 mai 2011 à 23:20 +0200, Francesco Poli a écrit : > since I don't think CeCILL-C meets the DFSG: A bit out of topic but you are probably wrong here. All CeCILL licenses are DFSG compliant. Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subjec

Bug#625605: marked as done (Preinst script in otrs2 package fails during dist-upgrade from lenny to squeeze.)

Your message dated Sat, 07 May 2011 21:28:54 + with message-id and subject line Bug#625605: fixed in otrs2 2.4.9+dfsg1-3+squeeze1 has caused the Debian Bug report #625605, regarding Preinst script in otrs2 package fails during dist-upgrade from lenny to squeeze. to be marked as done. This me

Bug#624670: marked as done (exim4 dkim plugin - % in dkim signature logged to paniclog)

Your message dated Sat, 07 May 2011 21:27:08 + with message-id and subject line Bug#624670: fixed in exim4 4.72-6+squeeze1 has caused the Debian Bug report #624670, regarding exim4 dkim plugin - % in dkim signature logged to paniclog to be marked as done. This means that you claim that the pr

Bug#618696: closed by Adam C Powell IV (Re: elmer: multiple licensing issues)

On Wed, 04 May 2011 15:08:02 -0400 Adam C Powell IV wrote: [...] > On Wed, 2011-04-13 at 17:27 -0400, Adam C Powell IV wrote: > > On Wed, 2011-04-13 at 23:00 +0200, Francesco Poli wrote: > > > On Wed, 13 Apr 2011 16:43:37 -0400 Adam C Powell IV wrote: > > > > Let me see if upstream will work with

Processed: Re: Bug#625937: kdevelop: crash when opening source file

Processing commands for cont...@bugs.debian.org: > reassign 625937 kdelibs5-plugins 4:4.6.2-1 Bug #625937 [kdevelop] kdevelop: crash when opening source file Bug reassigned from package 'kdevelop' to 'kdelibs5-plugins'. Bug No longer marked as found in versions kdevelop/4:4.0.1-1. Bug #625937 [kde

Bug#625937: kdevelop: crash when opening source file

reassign 625937 kdelibs5-plugins 4:4.6.2-1 retitle 625937 kdevelop 4.1.x or earlier does not work with KDE SC 4.6 affects 625937 kdevelop thanks Hello, On šeštadienis 07 Gegužė 2011 10:42:10 Salvo Tomaselli wrote: > kdevelop crashes when i try to open a .c file, but it is fine with .txt > files a

Bug#623036: closed by Matthijs Möhlmann (Bug#623036: fixed in pdns 2.9.22-9)

The bug has not been fixed in 2.9.22-9. I still get the same error message in the log. Is there anything else I can do to supply more information? Tiger!P -- A random quote: Een reden is alleen maar interessant als je het doel er van snapt. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@l

Bug#625521: Severity justification

Hi Steve, could you please justify severity critical for this bug? Now that it is assigned to xorg, the report does not prevent a glibc migration from happening starting from tomorrow. The only thing that will is #625607 (cmake: Segfaults on sparc). If this bug warrants delaying glibc's migrat

Processed: user v...@packages.debian.org, usertagging 625941, usertagging 624688, usertagging 624804 ...

Processing commands for cont...@bugs.debian.org: > user v...@packages.debian.org Setting user to v...@packages.debian.org (was james...@debian.org). > usertags 625941 + vim-common Bug#625941: vim: FTBFS on amd64 (test61 FAILED) There were no usertags set. Usertags are now: vim-common. > usertags 6

Bug#618768: llvm-gcc-4.5: Incompatible plugin version (dragonegg.so)

Le vendredi 06 mai 2011 à 23:46 +0200, Sylvestre Ledru a écrit : > Le mercredi 04 mai 2011 à 19:28 +0200, Urs Janssen a écrit : > > The reported problem still exists: > Indeed. Digging more. The error is in dragonegg-2.8/llvm-backend.cpp The version checks is done against the exact version of gcc:

Bug#618768: llvm-gcc-4.5: Incompatible plugin version (dragonegg.so)

Le mercredi 04 mai 2011 à 19:28 +0200, Urs Janssen a écrit : > The reported problem still exists: Indeed. Here is the actual code executed: $ echo 'int main(void){return 0;}' > foo.c $ /usr/lib/gcc/x86_64-linux-gnu/4.5.2/cc1 -iplugindir=/usr/lib/gcc/x86_64-linux-gnu/4.5.2/plugin foo.c -fplugin=/usr

Processed: Re: Bug#625143: pyoptical: FTBFS: ImportError: No module named serial

Processing commands for cont...@bugs.debian.org: > reassign 625143 python-serial Bug #625143 [src:pyoptical] pyoptical: FTBFS: ImportError: No module named serial Bug reassigned from package 'src:pyoptical' to 'python-serial'. Bug No longer marked as found in versions pyoptical/0.3-1. > thanks St

Bug#625143: pyoptical: FTBFS: ImportError: No module named serial

reassign 625143 python-serial thanks On Mon, May 02, 2011 at 02:45:56PM +0200, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build on > amd64. > > Relevant part: > > /usr/bin/fakeroot debian/rules clean > > dh clean > >dh_testdir > >dh_auto_clean

Processed: Re: Bug#625966: libmodplug1: libmodplug <= 0.8.8.2 .abc Stack-Based Buffer Overflow

Processing commands for cont...@bugs.debian.org: > forwarded 625966 konsta...@ieee.org Bug #625966 [libmodplug1] libmodplug1: libmodplug <= 0.8.8.2 .abc Stack-Based Buffer Overflow Set Bug forwarded-to-address to 'konsta...@ieee.org'. > thanks Stopping processing here. Please contact me if you n

Bug#625043: marked as done (itksnap: FTBFS: itkImageIORegion.h:62:11: error: 'ptrdiff_t' does not name a type)

Your message dated Sat, 7 May 2011 13:17:38 -0400 with message-id <20110507171738.GA7532@meiner> and subject line Re: Bug#625043: itksnap: FTBFS: itkImageIORegion.h:62:11: error: 'ptrdiff_t' does not name a type has caused the Debian Bug report #625043, regarding itksnap: FTBFS: itkImageIORegion.h

Bug#621078: redhat-cluster: /usr/include/pils/plugin.h:23:20: fatal error: ltdl.h: No such file or directory

reassign 621078 libpils2-dev retitle 621078 libpils2-dev: Missing dependency on libltdl-dev thanks On Wed, Apr 06, 2011 at 01:18:29PM +0200, Salvatore Bonaccorso wrote: > > In file included from /usr/include/stonith/stonith.h:47:0, > > from /usr/include/heartbeat/heartbeat.h:52, >

Processed: Re: Bug#621078: redhat-cluster: /usr/include/pils/plugin.h:23:20: fatal error: ltdl.h: No such file or directory

Processing commands for cont...@bugs.debian.org: > reassign 621078 libpils2-dev Bug #621078 [src:redhat-cluster] redhat-cluster: /usr/include/pils/plugin.h:23:20: fatal error: ltdl.h: No such file or directory Bug #623930 [src:redhat-cluster] redhat-cluster: FTBFS: fatal error: ltdl.h: No such f

Bug#624767: libbuffy-bindings: FTBFS

On Sun, May 01, 2011 at 02:14:34PM +0100, Dominic Hargreaves wrote: > This package fails to build from source in a clean sid chroot: > > creating build/temp.linux-i686-2.7 > gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall > -Wstrict-prototypes -g -O2 -fPIC -I/usr/include/glib-2.0

Bug#581950: backuppc: perl-suid is going away with Perl 5.12

Hi, On Sun, Feb 13, 2011 at 06:07:17PM +, Dominic Hargreaves wrote: > It appears that they have fixed this in Fedora with a trivial C > wrapper: > > >

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 625986 normal Bug #625986 [jbossas4] FTBFS due to API changes in Hibernate 3.6.x Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 625986: http://bugs.debian.org/cgi

Bug#625647: exim4: Exim configuration error→error in ACL: unknown ACL condition/modifier

Em 06.Mai.2011 (sexta), Andreas Metzler disse: > On 2011-05-04 Cyril Brulebois wrote: > > Package: exim4-daemon-light > > Version: 4.75-2+b1 > > Severity: grave > > Justification: Trivial configuration but non-working package > > > Hi, > > > upgrading exim4 from 4.75-2 to 4.75-2+b1 broke my q

Bug#625985: net-snmp: FTBFS on kfreebsd-*: ./.libs/libnetsnmpmibs.so: undefined reference to `kd'

Source: net-snmp Version: 5.4.3~dfsg-2.1 Severity: serious Justification: FTBFS User: debian-...@lists.debian.org Usertags: kfreebsd Hi, (-bsd + buildd maints in x-d-cc) your package still FTBFS, but only on kfreebsd-* now. I can't replicate this in an uptodate chroot on the kfreebsd-amd64 porte

Bug#625908: Please whitelist libmath-random-perl for non-free autobuilding

[see also bug#625908, cc-ed] Please can you add libmath-random-perl to the whitelist for non-free autobuilding. According to debian/copyright, the reason for it being non-free is due to restrictions that prevent copying/distribution for "direct commercial advantage". As far as I can see, this does

Bug#624902: gdcm: FTBFS: gdcmswigPYTHON_wrap.cxx:3716:13: error: 'ptrdiff_t' does not name a type

Mathieu, I just fixed a similar bug in insighttoolkit (it's as simple as including ). I can prepare and upload gdcm 2.0.17-3 with a patch to do so. Before doing so, I wanted to check whether you want to take a different strategy with this, e.g. new upstream. Cheers, -Steve signature.asc Descr

Bug#620676: [digikam] Experimental: uninstallable

I'm having the same problem. Package is uninstallable due to unresolvable dependencies on the following packages: libmarblewidget10 libkdcraw8 libkexiv2-8 As a workaround, I downloaded the source package including dependencies, and built the package myself using dpkg-buildpackage (I didn't chan

Bug#625962: marked as done ([sparse] FTBFS in sid pbuilder)

Your message dated Sat, 07 May 2011 14:55:00 + with message-id and subject line Bug#625962: fixed in sparse 0.4.3+20110419-1 has caused the Debian Bug report #625962, regarding [sparse] FTBFS in sid pbuilder to be marked as done. This means that you claim that the problem has been dealt with.

Bug#625051: marked as done (mldonkey: FTBFS: src/utils/lib/CryptoPP.cc:165:26: error: uninitialized const 'CryptoPP::g_nullNameValuePairs' [-fpermissive])

Your message dated Sat, 07 May 2011 14:54:08 + with message-id and subject line Bug#625051: fixed in mldonkey 3.0.7-2 has caused the Debian Bug report #625051, regarding mldonkey: FTBFS: src/utils/lib/CryptoPP.cc:165:26: error: uninitialized const 'CryptoPP::g_nullNameValuePairs' [-fpermissiv

Bug#624937: marked as done (late: FTBFS: ball.h:113:19: error: 'NULL' was not declared in this scope)

Your message dated Sat, 07 May 2011 14:52:07 + with message-id and subject line Bug#624937: fixed in late 0.1.0-12 has caused the Debian Bug report #624937, regarding late: FTBFS: ball.h:113:19: error: 'NULL' was not declared in this scope to be marked as done. This means that you claim that

Bug#624978: marked as done (kball: FTBFS: src/gamemenu.cpp:224:52: error: 'mkdir' was not declared in this scope)

Your message dated Sat, 07 May 2011 14:50:54 + with message-id and subject line Bug#624978: fixed in kball 0.0.20041216-8 has caused the Debian Bug report #624978, regarding kball: FTBFS: src/gamemenu.cpp:224:52: error: 'mkdir' was not declared in this scope to be marked as done. This means

Bug#624287: CVE-2009-5022

Attached is a patch to create tiff-3.9.4-5+squeeze2 from tiff-3.9.4-5+squeeze1. I have tested by building in unstable. While I'm certain that the patch applies, I was not able to reproduce the problem using the test case posted in upstream's bugzilla. In any case, I don't believe that's essentia

Bug#625953: linux-2.6: orinoco_pci module is no longer present

Hi Mike, On Sat, May 07, 2011 at 11:31:07AM +0100, Mike wrote: > As per subject, the orinoco_pci module is missing from 2.6.38 kernel > images, so my router can no longer connect to the network. Prism 2/2.5/3 support in the orinoco driver (HERMES_PRISM) is disabled by default as of Linux 2.6.35 [

Processed: updating versions

Processing commands for cont...@bugs.debian.org: > notfound 624287 3.8.2-11.3 Bug #624287 {Done: Jay Berkenbilt } [tiff] CVE-2009-5022 There is no source info for the package 'tiff' at version '3.8.2-11.3' with architecture '' Unable to make a source version for version '3.8.2-11.3' Bug No longer

Bug#624287: CVE-2009-5022

Moritz Muehlenhoff wrote: > http://bugzilla.maptools.org/show_bug.cgi?id=1999 has been assigned > CVE-2009-5022. Actually, it doesn't apply to oldstable either. That code didn't exist before 3.9. So I'll prepare packages for stable-security only. -- To UNSUBSCRIBE, email to debian-bugs-rc-

Bug#624287: marked as done (CVE-2009-5022)

Your message dated Sat, 07 May 2011 10:04:40 -0400 with message-id <20110507100437.0294273558.qww314159@soup> and subject line updating versions has caused the Debian Bug report #624287, regarding CVE-2009-5022 to be marked as done. This means that you claim that the problem has been dealt with. I

Processed: tagging 625110

Processing commands for cont...@bugs.debian.org: > tags 625110 + pending Bug #625110 [src:caret] caret: FTBFS: StatisticRandomNumberOperator.h:38:7: error: 'ptrdiff_t' does not name a type Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 6251

Processed: tagging 625977

Processing commands for cont...@bugs.debian.org: > tags 625977 + pending Bug #625977 [apparmor-utils] apparmor-utils: uninstallable on kfreebsd-* Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 625977: http://bugs.debian.org/cgi-bin/bugreport

Processed (with 1 errors): updating versions

Processing commands for cont...@bugs.debian.org: > Version: 3.9.5-1 Unknown command or malformed arguments to command. > found 624287 3.8.2-11.3 Bug #624287 [tiff] CVE-2009-5022 There is no source info for the package 'tiff' at version '3.8.2-11.3' with architecture '' Unable to make a source ve

Processed: reassign 625975 to src:nmap, forcibly merging 621938 625975

Processing commands for cont...@bugs.debian.org: > # *sigh* > reassign 625975 src:nmap Bug #625975 [src:namp] nmap: FTBFS Warning: Unknown package 'src:namp' Bug reassigned from package 'src:namp' to 'src:nmap'. > forcemerge 621938 625975 Bug#621938: nmap: FTBFS: nse_openssl.cc:11:25: fatal error:

Bug#625941: vim: FTBFS on amd64 (test61 FAILED)

On Sat, May 07, 2011 at 10:50:43AM +0200, Julien Cristau wrote: > vim failed to build on the amd64 buildd: > https://buildd.debian.org/status/fetch.php?pkg=vim&arch=amd64&ver=2%3A7.3.154%2Bhg~74503f6ee649-2%2Bb1&stamp=1304465102 I think this is a timing issue. That test has to do with the undo su

Bug#624287: CVE-2009-5022

Moritz Muehlenhoff wrote: > http://bugzilla.maptools.org/show_bug.cgi?id=1999 has been assigned > CVE-2009-5022. This bug was already fixed in 3.9.5, so it only affects stable and oldstable. I'll update the found/fixed versions and prepare packages for stable and oldstable. -- Jay Berkenbilt

Processed (with 1 errors): Re: Bug#625975: nmap: FTBFS

Processing commands for cont...@bugs.debian.org: > reassign 625975 src:namp Bug #625975 [nmap] nmap: FTBFS Bug reassigned from package 'nmap' to 'src:namp'. Warning: Unknown package 'src:namp' Warning: Unknown package 'src:namp' Bug No longer marked as found in versions nmap/5.21-1. Warning: Unkno

Bug#625975: nmap: FTBFS

reassign 625975 src:namp forcemerge 621938 625975 thanks On Sat, 2011-05-07 at 16:31 +0300, Adrian Bunk wrote: > Package: nmap > Version: 5.21-1 > Severity: serious and already filed as #621938 nearly a month ago. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debia

Processed: bug 625051 is forwarded to https://savannah.nongnu.org/bugs/index.php?33257, tagging 625051

Processing commands for cont...@bugs.debian.org: > forwarded 625051 https://savannah.nongnu.org/bugs/index.php?33257 Bug #625051 [src:mldonkey] mldonkey: FTBFS: src/utils/lib/CryptoPP.cc:165:26: error: uninitialized const 'CryptoPP::g_nullNameValuePairs' [-fpermissive] Set Bug forwarded-to-addres

Bug#624884: marked as done (alex4: FTBFS: stat.h:106:22: error: expected identifier or '(' before '[' token)

Your message dated Sat, 07 May 2011 13:47:10 + with message-id and subject line Bug#624884: fixed in alex4 1.1-5 has caused the Debian Bug report #624884, regarding alex4: FTBFS: stat.h:106:22: error: expected identifier or '(' before '[' token to be marked as done. This means that you claim

Bug#625977: apparmor-utils: uninstallable on kfreebsd-*

Package: apparmor-utils Version: 2.6.1-3 Severity: grave User: debian-...@lists.debian.org Usertag: kfreebsd Justification: renders package unusable apparmor-utils is "Architecture: any", but it depends on apparmor, which is "Architecture: linux-any". As a consequence, apparmor-utils is not ins

Bug#625877: xserver-xorg-core 1.10.2: resizing konsole hangs xserver

On Friday 06 May 2011, Cyril Brulebois wrote: > reassign 625877 nvidia-glx > thanks > > Hi, > > Wolfgang Walter (06/05/2011): > > Package: xserver-xorg-core > > Version: 2:1.10.1-2 > > Severity: grave > > > > After upgrading from xserver-xorg-core 2:1.9.5-1 to version > > 2:1.10.1-2 the xserver

Processed: limit source to mldonkey, tagging 625051

Processing commands for cont...@bugs.debian.org: > #mldonkey (3.0.7-2) unstable; urgency=low > # > # * Fix FTBFS with g++ 4.6 (Closes: #625051) > # > limit source mldonkey Limiting to bugs with field 'source' containing at least one of 'mldonkey' Limit currently set to 'source':'mldonkey' > tags

Bug#625975: nmap: FTBFS

Package: nmap Version: 5.21-1 Severity: serious <-- snip --> g++ -c -I/usr/include/lua5.1 -Ilibdnet-stripped/include -Inbase -Insock/include -O2 -Wall -D_GNU_SOURCE -Wall -fno-strict-aliasing -DHAVE_CONFIG_H -DNMAP_NAME=\"Nmap\" -DNMAP_URL=\"http://nmap.org\"; -DNMAP_PLATFORM=\"x86_6

Bug#625972: plexus-containers: FTBFS: Cannot find symbol Multimaps.newLinkedHashMap

Source: plexus-containers Version: 1.0~beta3.0.7-4 Severity: serious From my pbuilder build log: ... compile: [mkdir] Created dir: /tmp/buildd/plexus-containers-1.0~beta3.0.7/plexus-container-default/build/generated-sources [javac] /usr/share/maven-ant-helper/maven-build.xml:326: warning

Bug#625966: libmodplug1: libmodplug <= 0.8.8.2 .abc Stack-Based Buffer Overflow

Package: libmodplug1 Version: 1:0.8.8.1-2 Severity: grave Tags: security upstream Justification: user security hole Hello, As the security contact for VLC media player, this was brought to my attention: http://www.exploit-db.com/exploits/17222/ I can confirm the bug happens, but I have

Bug#616052: Still interested in maintaining opendchub in Debian?

Hi, I noticed that this bug has been open for a while and that the Git repository used for maintaining the package[1] is no longer available. For these reasons, I am wondering whether you are still interested in maintaining opendchub in Debian or not. Regards, Ansgar [1]

Bug#563050: Closing #563050

Version: 0.7.4-1 Hi, the latest upload of beast should fix this. Regards, -- Alessio Treglia          | www.alessiotreglia.com Debian Developer         | ales...@debian.org Ubuntu Core Developer    | quadris...@ubuntu.com 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0 -- To UNSUBSCRIBE,

Bug#595743: marked as done (beast: FTBFS: Build killed with signal TERM after 150 minutes of inactivity)

Your message dated Sat, 7 May 2011 14:36:08 +0200 with message-id and subject line Closing #563050 has caused the Debian Bug report #563050, regarding beast: FTBFS: Build killed with signal TERM after 150 minutes of inactivity to be marked as done. This means that you claim that the problem has

Bug#563050: marked as done (beast: FTBFS on some architectures (infinite loop?))

Your message dated Sat, 7 May 2011 14:36:08 +0200 with message-id and subject line Closing #563050 has caused the Debian Bug report #563050, regarding beast: FTBFS on some architectures (infinite loop?) to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#553963: Closing #553963

Version: 0.7.4-1 Hi, the latest upload of beast fixed this. Regards, -- Alessio Treglia          | www.alessiotreglia.com Debian Developer         | ales...@debian.org Ubuntu Core Developer    | quadris...@ubuntu.com 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0 -- To UNSUBSCRIBE, email

Bug#553963: marked as done (FTBFS with binutils-gold)

Your message dated Sat, 7 May 2011 14:32:51 +0200 with message-id and subject line Closing #553963 has caused the Debian Bug report #553963, regarding FTBFS with binutils-gold to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#625964: goldencheetah: FTBFS on GNU/kFreeBSD

Package: goldencheetah Version: 2.0.0-1 Severity: serious The build log seems that the package fails to build from source on kfreebsd-*. On May 6, 2011 at 1:45AM +, noreply (at buildd.debian.org) wrote: > * Source package: goldencheetah > * Version: 2.0.0-1 > * Architecture: kfreebsd-amd6

Bug#625963: vile: FTBFS on armel and s390 (hangs in configure?)

Package: vile Version: 9.8e-1 Severity: serious Justification: fails to build from source See https://buildd.debian.org/status/package.php?p=vile Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lis

Bug#625962: [sparse] FTBFS in sid pbuilder

Package: sparse Version: 0.4.3-1 Severity: serious debian/rules build dh build dh_testdir dh_auto_configure dh_auto_build make[1]: Entering directory `/tmp/buildd/sparse-0.4.3' CC test-lexing.o CC target.o CC parse.o In file included from parse.c:25:0: pa

Bug#564799: marked as done (beast: should this package be removed?)

Your message dated Sat, 07 May 2011 12:17:20 + with message-id and subject line Bug#564799: fixed in beast 0.7.4-1 has caused the Debian Bug report #564799, regarding beast: should this package be removed? to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#625961: pcp: FTBFS on the buildds ($HOME not set)

Package: pcp Version: 3.4.0 Severity: serious Justification: fails to build from source See https://buildd.debian.org/status/package.php?p=pcp Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.

Bug#625919: marked as done (udev: broken in minimal installation.)

Your message dated Sat, 7 May 2011 14:08:55 +0200 with message-id <20110507120855.gb9...@bongo.bofh.it> and subject line Re: Bug#625919: udev: broken in minimal installation. has caused the Debian Bug report #625919, regarding udev: broken in minimal installation. to be marked as done. This means

Processed: ming: diff for NMU version 1:0.4.3-1.1

Processing commands for cont...@bugs.debian.org: > tags 606006 + pending Bug #606006 [ming] Fix FTBFS with ld --no-add-needed Bug #623927 [ming] ming: FTBFS: undefined reference to symbol 'png_set_sig_bytes@@PNG12_0' Added tag(s) pending. Added tag(s) pending. > thanks Stopping processing here.

Bug#606006: ming: diff for NMU version 1:0.4.3-1.1

tags 606006 + pending thanks Dear maintainer, I've prepared an NMU for ming (versioned as 1:0.4.3-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Ansgar diff -u ming-0.4.3/debian/changelog ming-0.4.3/debian/changelog --- ming-0.4.3/debian/cha

Bug#619140: freemind: fails to start: "Checking Java Version..." forever

I am trying to reproduce this Bug... Just one quick question: You're using OpenJDK, right? And if you do, does switching to the Sun-JDK "fix" it for you? This worked for me, I've installed the JDK from Sun and modified /usr/bin/freemind: --- /usr/bin/freemind 2011-05-07 13:21:55.0 +

Bug#625957: [telepathy-sunshine] Countinously disconnecting

Package: telepathy-sunshine Version: 0.1.8-2 Severity: grave --- Please enter the report below this line. --- Gadu-Gadu disconnects many very often, making it not usable when compared to other Gadu-Gadu clients for Linux. Sometimes its not even possible to reconnect anymore with message on termin

Processed: bug 579450 is not forwarded

Processing commands for cont...@bugs.debian.org: > notforwarded 579450 Bug #579450 [swig1.3] swig: perl bindings make incorrect assumptions about the size of IVs Unset Bug forwarded-to-address > thanks Stopping processing here. Please contact me if you need assistance. -- 579450: http://bugs.de

Processed: retitle / affects 579450

Processing commands for cont...@bugs.debian.org: > retitle 579450 swig: perl bindings make incorrect assumptions about the size > of IVs Bug #579450 [swig1.3] libdevice-cdio-perl: FTBFS with perl 5.12.0-1: 64-bit integers Changed Bug title to 'swig: perl bindings make incorrect assumptions about

Bug#625956: src:doxygen: missing source for src/jquery.js

Package: src:doxygen Version: 1.7.4-1 Severity: serious Tags: upstream Justification: missing source The doxygen source package contains only the compressed ("minified") version of jquery.js. Of course it probably shouldn't embed jquery.js at all, but if it does, it should embed an editable, uncom

Processed: tagging 625955

Processing commands for cont...@bugs.debian.org: > tags 625955 - upstream Bug #625955 [seahorse-plugins] seahorse-plugins: dependencies problem Removed tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 625955: http://bugs.debian.org/cgi-bin/bugrepor

  1   2   >