Bug#477694: FTBFS: ext/threads/t/stress_re.t fails sporadically on sparc

On Fri, Apr 25, 2008 at 10:29:03PM +0200, Florian Weimer wrote: > * Niko Tyni: > > > It doesn't show up on my own sparc uniprocessor host, which has the > > Etch kernel, so it's either specific to new kernels or SMP hosts. As it > > works on sperger in the sid chroot, it would seem that newer vers

Processed: fixed 477068 in 1.8.1.13-1

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.26 > fixed 477068 1.8.1.13-1 Bug#477068: xulrunner_1.9~b5-2(mips/experimental): FTBFS: expected constructor, destructor, or type conversion before 'XPTC_InvokeByIndex' Bug marked as fixe

Bug#455673: [Fwd: Patch to fix 474530 and 455673]

Forwarded to present information. Kumar -- Kumar Appaiah, 458, Jamuna Hostel, Indian Institute of Technology Madras, Chennai - 600 036 --- Begin Message --- tags 474530 + patch tags 455673 + patch thanks (CCing Alexander and James who were interested in NMUing this a while back). Hi! Please fi

Processed: Patch to fix 474530 and 455673

Processing commands for [EMAIL PROTECTED]: > tags 474530 + patch Bug#474530: debian-xcontrol - FTBFS: error: ISO C++ forbids declaration of 'auto_ptr' with no type There were no tags set. Bug#455673: FTBFS with GCC 4.3: missing #includes Tags added: patch > tags 455673 + patch Bug#455673: FTBFS

Bug#476806: marked as done (AssertionError when archiving empty maildirs)

Your message dated Sat, 26 Apr 2008 05:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#476806: fixed in archivemail 0.7.2-3 has caused the Debian Bug report #476806, regarding AssertionError when archiving empty maildirs to be marked as done. This means that you claim that th

Bug#474530: Patch to fix 474530 and 455673

tags 474530 + patch tags 455673 + patch thanks (CCing Alexander and James who were interested in NMUing this a while back). Hi! Please find attached a patch to fix this bug. I now can say for sure that this fixes the FTBFS, but it fails to build with the new g++ snapshot (4.4.0). But I guess tha

Bug#477438: roundup - security update broke my installation

Hi Toni, thanks... I'm terribly sorry for the mistake, and guess I have created a fix (tested yesterday or so by Floris) which is to say "escape=1" instead of the original "escape=0" in the offending position (your line number is correct, Floris' not). Could you please try to see if running with

Bug#477962: tellico: FTBFS: Nonexistent build-dependency: libyaz2-dev

User: [EMAIL PROTECTED] > Usertags: qa-ftbfs-20080425 qa-ftbfs > Justification: FTBFS on i386 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on i386. > > This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3 is now >

Processed: reopening a bug

Processing commands for [EMAIL PROTECTED]: > reopen 472630 Bug#472630: audacious-crossfade: audacious segfaults Bug reopened, originator not changed. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, De

Processed: Patch to fix 474792

Processing commands for [EMAIL PROTECTED]: > tags 474792 + patch Bug#474792: debtags-edit: FTBFS: TagMenu.tcc:74: error: 'auto_ptr' was not declared in this scope There were no tags set. Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug t

Bug#474792: Patch to fix 474792

tags 474792 + patch thanks Hi! Please find attached a patch to fix this bug by adding the missing #include in the problematic file. HTH. Kumar -- Kumar Appaiah, 458, Jamuna Hostel, Indian Institute of Technology Madras, Chennai - 600 036 diff -Nru --exclude changelog debtags-edit-1.3/src/TagM

Processed: Patch to fix 476066.

Processing commands for [EMAIL PROTECTED]: > tags 476066 + patch Bug#476066: wml: FTBFS: configure: warning: CFLAGS=-g -O2: invalid host type There were no tags set. Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system adminis

Bug#476066: Patch to fix 476066.

tags 476066 + patch thanks Hi! Please find attached a patch to fix this bug, by unexporting the compiler flags set by dpkg-buildpackage. HTH. Kumar -- Kumar Appaiah, 458, Jamuna Hostel, Indian Institute of Technology Madras, Chennai - 600 036 diff -Nru --exclude changelog wml-2.0.11ds1/debian/

Bug#474856: marked as done (lordsawar: FTBFS: cwchar:52:24: error: wchar.h: No such file or directory)

Your message dated Sat, 26 Apr 2008 01:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#474856: fixed in lordsawar 0.0.8-2 has caused the Debian Bug report #474856, regarding lordsawar: FTBFS: cwchar:52:24: error: wchar.h: No such file or directory to be marked as done. This

Bug#423149: marked as done (kxmleditor handles entity references incorrectly)

Your message dated Fri, 25 Apr 2008 19:55:30 -0500 with message-id <[EMAIL PROTECTED]> and subject line kxmleditor has been removed from Debian, closing #423149 has caused the Debian Bug report #423149, regarding kxmleditor handles entity references incorrectly to be marked as done. This means th

Bug#353882: marked as done (oftpd: Remote DoS vulnerability)

Your message dated Fri, 25 Apr 2008 20:00:46 -0500 with message-id <[EMAIL PROTECTED]> and subject line oftpd has been removed from Debian, closing #353882 has caused the Debian Bug report #353882, regarding oftpd: Remote DoS vulnerability to be marked as done. This means that you claim that the

Bug#424598: marked as done (FTBFS: conflicting types for 'readlink')

Your message dated Fri, 25 Apr 2008 19:52:29 -0500 with message-id <[EMAIL PROTECTED]> and subject line gnome-find has been removed from Debian, closing #424598 has caused the Debian Bug report #424598, regarding FTBFS: conflicting types for 'readlink' to be marked as done. This means that you cl

Bug#417061: marked as done (FTBFS with GCC 4.3: identifier 'static_assert' will become a keyword in C++0x)

Your message dated Sat, 26 Apr 2008 00:17:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#417061: fixed in holotz-castle 1.3.10-1 has caused the Debian Bug report #417061, regarding FTBFS with GCC 4.3: identifier 'static_assert' will become a keyword in C++0x to be marked as don

Processed: retitle 477751 to dh_installcatalogs: Don't readd catalog on every upgrade to the catalog

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.26 > retitle 477751 dh_installcatalogs: Don't readd catalog on every upgrade to > the catalog Bug#477751: docbook-xml: Don't readd your catalog on every upgrade to the super catalog Cha

Bug#477930: reassign 477930 to scons

# Automatically generated email from bts, devscripts version 2.9.6 reassign 477930 scons 0.98.0-1 thanks kio-locate can be built on a clean&updated sid chroot as long as scons < 0.98.0-1 scons >= 0.98.0-1 does not set: -I/usr/include/kde/ -I/usr/include/qt3 Which is: admin/kde.py: env.Append(

Processed: reassign 477930 to scons

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.6 > reassign 477930 scons 0.98.0-1 Bug#477930: kio-locate: FTBFS: does not find Qt/KDE includes Bug reassigned from package `kio-locate' to `scons'. > thanks Stopping processing here. Pl

Bug#471060: Processed: 'dh_installinit -n' does not fix the problem.

On Fri, Apr 25, 2008 at 01:38:39PM -0400, Joey Hess wrote: > AFAIK, start-stop-daemon still defaults to refusing to stop a daemon if > the executable has changed from the executable it initially started. Ie: "still defaults" - since when? i've never seen that behaviour. start-stop-daemon uses pi

Bug#475905: egroupware-felamimail: Missing package dependencies

Am Sonntag, 13. April 2008 schrieb Michael Tuschik: > egroupware-felamimail doesn't work after installation via apt-get. I > installed two additional packages "php-auth" and "php-net-imap" > and now felamimail works ok. Could you be more specific about what errors you see? It is quite possible t

Bug#477974: undeclared conflicts with package john

Package: john-data Version: 1.7.2.-1 Severity: grave Selecting previously deselected package john-data. Unpacking john-data (from .../john-data_1.7.2-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/john-data_1.7.2-1_all.deb (--unpack): trying to overwrite `/usr/share/john/password

Processed: Re: Bug#477964: gnat-4.3: FTBFS: grep: ../libgnatvsn/gnatvsn.ads: No such file or directory

Processing commands for [EMAIL PROTECTED]: > severity 477964 important Bug#477964: gnat-4.3: FTBFS: grep: ../libgnatvsn/gnatvsn.ads: No such file or directory Severity set to `important' from `serious' > tags 477964 moreinfo Bug#477964: gnat-4.3: FTBFS: grep: ../libgnatvsn/gnatvsn.ads: No such f

Processed: tagging 477961

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.26 > tags 477961 + pending Bug#477961: libnet-z3950-perl: FTBFS: Nonexistent build-dependency: libyaz2-dev There were no tags set. Tags added: pending > End of message, stopping processi

Bug#477961: libnet-z3950-perl: FTBFS: Nonexistent build-dependency: libyaz2-dev

On Sat, 26 Apr 2008 02:44:31 +0200, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build on i386. > > E: Package libyaz2-dev has no installation candidate Yup, it's libyaz3-dev now. But libnet-z3950-perl will become a transitional dummy package anyway, i

Bug#477964: gnat-4.3: FTBFS: grep: ../libgnatvsn/gnatvsn.ads: No such file or directory

severity 477964 important tags 477964 moreinfo merge 477964 465671 thanks I built the package built successfully without any problem on i386 and amd64, and the buildds successfully on all other architectures. Two days ago. Since you build with 8 parallel threads, I think this is another symptom

Bug#477239: marked as done (exim4-base: empty argument in init.d prevents starting)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477236: fixed in exim4 4.69-3 has caused the Debian Bug report #477236, regarding exim4-base: empty argument in init.d prevents starting to be marked as done. This means that you claim that

Bug#477236: marked as done (exim4-daemon-heavy: restart of exim4 fails after pdate )

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477239: fixed in exim4 4.69-3 has caused the Debian Bug report #477239, regarding exim4-daemon-heavy: restart of exim4 fails after pdate to be marked as done. This means that you claim tha

Bug#477258: marked as done (Fails to start because of incorrect command-line arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477239: fixed in exim4 4.69-3 has caused the Debian Bug report #477239, regarding Fails to start because of incorrect command-line arguments to be marked as done. This means that you claim

Bug#477258: marked as done (Fails to start because of incorrect command-line arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477194: fixed in exim4 4.69-3 has caused the Debian Bug report #477194, regarding Fails to start because of incorrect command-line arguments to be marked as done. This means that you claim

Bug#477194: marked as done (exim4: Starting MTA:exim: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477194: fixed in exim4 4.69-3 has caused the Debian Bug report #477194, regarding exim4: Starting MTA:exim: incompatible command-line options or arguments to be marked as done. This means

Bug#477562: marked as done (exim4-daemon-light: init script fails to start: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477194: fixed in exim4 4.69-3 has caused the Debian Bug report #477194, regarding exim4-daemon-light: init script fails to start: incompatible command-line options or arguments to be marked

Bug#477562: marked as done (exim4-daemon-light: init script fails to start: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477236: fixed in exim4 4.69-3 has caused the Debian Bug report #477236, regarding exim4-daemon-light: init script fails to start: incompatible command-line options or arguments to be marked

Processed: Re: Bug#476977: Security fix in new upstream release

Processing commands for [EMAIL PROTECTED]: > severity 476977 important Bug#476977: Security fix in new upstream release Severity set to `important' from `critical' > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator,

Bug#476987: marked as done (exim4-daemon-light: fails to install: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#476987: fixed in exim4 4.69-3 has caused the Debian Bug report #476987, regarding exim4-daemon-light: fails to install: incompatible command-line options or arguments to be marked as done.

Bug#477239: marked as done (exim4-base: empty argument in init.d prevents starting)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477562: fixed in exim4 4.69-3 has caused the Debian Bug report #477562, regarding exim4-base: empty argument in init.d prevents starting to be marked as done. This means that you claim that

Bug#477236: marked as done (exim4-daemon-heavy: restart of exim4 fails after pdate )

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477258: fixed in exim4 4.69-3 has caused the Debian Bug report #477258, regarding exim4-daemon-heavy: restart of exim4 fails after pdate to be marked as done. This means that you claim tha

Bug#477258: marked as done (Fails to start because of incorrect command-line arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477236: fixed in exim4 4.69-3 has caused the Debian Bug report #477236, regarding Fails to start because of incorrect command-line arguments to be marked as done. This means that you claim

Bug#477562: marked as done (exim4-daemon-light: init script fails to start: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477562: fixed in exim4 4.69-3 has caused the Debian Bug report #477562, regarding exim4-daemon-light: init script fails to start: incompatible command-line options or arguments to be marked

Bug#477258: marked as done (Fails to start because of incorrect command-line arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477258: fixed in exim4 4.69-3 has caused the Debian Bug report #477258, regarding Fails to start because of incorrect command-line arguments to be marked as done. This means that you claim

Bug#477562: marked as done (exim4-daemon-light: init script fails to start: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477239: fixed in exim4 4.69-3 has caused the Debian Bug report #477239, regarding exim4-daemon-light: init script fails to start: incompatible command-line options or arguments to be marked

Bug#476977: Security fix in new upstream release

severity 476977 important stop Am Sonntag, 20. April 2008 schrieb Lars Wilke: > The fixed security problems are grave, if you have > directories writable by the webserver in you docroot (in most > windows server the complete docroot writable by default, but > many linux servers are also set up

Bug#477562: marked as done (exim4-daemon-light: init script fails to start: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477258: fixed in exim4 4.69-3 has caused the Debian Bug report #477258, regarding exim4-daemon-light: init script fails to start: incompatible command-line options or arguments to be marked

Bug#477194: marked as done (exim4: Starting MTA:exim: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477236: fixed in exim4 4.69-3 has caused the Debian Bug report #477236, regarding exim4: Starting MTA:exim: incompatible command-line options or arguments to be marked as done. This means

Bug#477236: marked as done (exim4-daemon-heavy: restart of exim4 fails after pdate )

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477236: fixed in exim4 4.69-3 has caused the Debian Bug report #477236, regarding exim4-daemon-heavy: restart of exim4 fails after pdate to be marked as done. This means that you claim tha

Bug#477194: marked as done (exim4: Starting MTA:exim: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477258: fixed in exim4 4.69-3 has caused the Debian Bug report #477258, regarding exim4: Starting MTA:exim: incompatible command-line options or arguments to be marked as done. This means

Bug#477258: marked as done (Fails to start because of incorrect command-line arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477562: fixed in exim4 4.69-3 has caused the Debian Bug report #477562, regarding Fails to start because of incorrect command-line arguments to be marked as done. This means that you claim

Bug#477236: marked as done (exim4-daemon-heavy: restart of exim4 fails after pdate )

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477562: fixed in exim4 4.69-3 has caused the Debian Bug report #477562, regarding exim4-daemon-heavy: restart of exim4 fails after pdate to be marked as done. This means that you claim tha

Bug#477236: marked as done (exim4-daemon-heavy: restart of exim4 fails after pdate )

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477194: fixed in exim4 4.69-3 has caused the Debian Bug report #477194, regarding exim4-daemon-heavy: restart of exim4 fails after pdate to be marked as done. This means that you claim tha

Bug#477239: marked as done (exim4-base: empty argument in init.d prevents starting)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477258: fixed in exim4 4.69-3 has caused the Debian Bug report #477258, regarding exim4-base: empty argument in init.d prevents starting to be marked as done. This means that you claim that

Bug#477239: marked as done (exim4-base: empty argument in init.d prevents starting)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477194: fixed in exim4 4.69-3 has caused the Debian Bug report #477194, regarding exim4-base: empty argument in init.d prevents starting to be marked as done. This means that you claim that

Bug#477194: marked as done (exim4: Starting MTA:exim: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477239: fixed in exim4 4.69-3 has caused the Debian Bug report #477239, regarding exim4: Starting MTA:exim: incompatible command-line options or arguments to be marked as done. This means

Bug#477194: marked as done (exim4: Starting MTA:exim: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477562: fixed in exim4 4.69-3 has caused the Debian Bug report #477562, regarding exim4: Starting MTA:exim: incompatible command-line options or arguments to be marked as done. This means

Bug#477239: marked as done (exim4-base: empty argument in init.d prevents starting)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477239: fixed in exim4 4.69-3 has caused the Debian Bug report #477239, regarding exim4-base: empty argument in init.d prevents starting to be marked as done. This means that you claim that

Processed: Re: Bug#477968: yafray: FTBFS: src/yafraycore/color.h:37: error: expected constructor, destructor, or type conversion before 'class'

Processing commands for [EMAIL PROTECTED]: > tag 477968 confirmed Bug#477968: yafray: FTBFS: src/yafraycore/color.h:37: error: expected constructor, destructor, or type conversion before 'class' There were no tags set. Tags added: confirmed > thanks Stopping processing here. Please contact me i

Bug#477751: dh_installcatalogs: Don't readd catalog on every upgrade to the super catalog

reassign 477751 debhelper retitle 477751 dh_installcatalogs: Don't readd catalog on every upgrade to the super catalog thanks Am Freitag, den 25.04.2008, 00:35 +0200 schrieb Jörg Sommer: > Package: docbook-xml > Version: 4.5-5 > Severity: serious > Justification: Policy 10.7.3 > > Hi, > > poli

Bug#477968: yafray: FTBFS: src/yafraycore/color.h:37: error: expected constructor, destructor, or type conversion before 'class'

tag 477968 confirmed thanks On 26/04/2008, Lucas Nussbaum wrote: > Feel free to downgrade this bug to 'important' if your package is only built > on i386, and this bug is specific to gcc 4.3 (i.e the package builds fine > with gcc 4.2). No, confirmed. Mraw, KiBi. pgpRn5Z7Y4BaC.pgp Description:

Processed (with 1 errors): Re: Bug#477751: dh_installcatalogs: Don't readd catalog on every upgrade to the super catalog

Processing commands for [EMAIL PROTECTED]: > reassign 477751 debhelper Bug#477751: docbook-xml: Don't readd your catalog on every upgrade to the super catalog Bug reassigned from package `docbook-xml' to `debhelper'. > retitle 477751 dh_installcatalogs: Don't readd catalog on every upgrade to

Processed: tagging 477959

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.26 > tags 477959 + pending Bug#477959: git-buildpackage: FTBFS: ImportError: No module named dateutil.parser There were no tags set. Tags added: pending > End of message, stopping proce

Bug#477968: yafray: FTBFS: src/yafraycore/color.h:37: error: expected constructor, destructor, or type conversion before 'class'

Package: yafray Version: 0.0.9+dfsg-1 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080425 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc

Bug#477965: php-net-socket: FTBFS: /bin/sh: /usr/bin/pear: No such file or directory

Package: php-net-socket Version: 1.0.8-1 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080425 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc 4.2, because

Bug#477962: tellico: FTBFS: Nonexistent build-dependency: libyaz2-dev

Package: tellico Version: 1.3.1-1 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080425 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3

Bug#477959: git-buildpackage: FTBFS: ImportError: No module named dateutil.parser

Package: git-buildpackage Version: 0.4.25 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080425 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc 4.2, because

Bug#477970: libgimp-perl: FTBFS: rm: cannot remove `/build/user/libgimp-perl-2.0.dfsg+2.2pre1.dfsg/debian/libgimp-perl/ usr/lib/gimp/2.0/plug-ins/redeye': No such file or directory

Package: libgimp-perl Version: 2.0.dfsg+2.2pre1.dfsg-3 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080425 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc

Bug#477963: lhapdf: FTBFS: test-lhapdf-ccwrap.cc:23: error: 'strcpy' was not declared in this scope

Package: lhapdf Version: 5.3.1-1 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080425 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3

Bug#477960: manpages-tr: FTBFS: seems to take a very long time to build

Package: manpages-tr Version: 1.0.5 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080425 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. I killed the first xml2man instance (the one for apropos.1) after 30

Bug#477956: the: FTBFS: cp: cannot create regular file `debian/tmp-doc/usr/share/THE': No such file or directory

Package: the Version: 3.1-4 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080425 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. Also, {,} is a bashism. Fix it before I report it :-) This rebuild was done

Bug#477969: libmcal: FTBFS: drivers.c:1: error: stray '\' in program

Package: libmcal Version: 0.6-16 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080425 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3

Bug#477966: vifm: FTBFS: **Error**: You must have `autoconf' installed to.

Package: vifm Version: 0.3a-2 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080425 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3 is

Bug#477967: netatalk: FTBFS: changed copyrights

Package: netatalk Version: 2.0.3-9 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080425 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc

Bug#477957: kdenetwork: FTBFS: /build/user/kdenetwork-3.5.9/./configure: line 40202: xmms-config: command not found

Package: kdenetwork Version: 4:3.5.9-1 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080425 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc 4.2, because

Bug#477964: gnat-4.3: FTBFS: grep: ../libgnatvsn/gnatvsn.ads: No such file or directory

Package: gnat-4.3 Version: 4.3.0-5 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080425 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc

Bug#477961: libnet-z3950-perl: FTBFS: Nonexistent build-dependency: libyaz2-dev

Package: libnet-z3950-perl Version: 0.51-4 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080425 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc 4.2

Bug#477958: libexosip2: FTBFS: Unsatisfiable build-dependency: libosip2-dev(inst 3.0.3-2-1 ! >= wanted 3.1)

Package: libexosip2 Version: 3.1.0-1 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080425 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc

Processed: Re: 477020

Processing commands for [EMAIL PROTECTED]: > severity 477020 serious Bug#477020: nuapplet: FTBFS: CMake Error: Can't find gnutls library developpement files! Severity set to `serious' from `important' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug track

Processed: tagging 477930

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.6 > tags 477930 confirmed Bug#477930: kio-locate: FTBFS: does not find Qt/KDE includes There were no tags set. Tags added: confirmed > End of message, stopping processing here. Please co

Bug#473940: marked as done (rudiments: FTBFS: error: unrecognized command line option "-Wno-long-double")

Your message dated Sat, 26 Apr 2008 02:29:14 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#473940: rudiments: FTBFS: error: unrecognized command line option "-Wno-long-double" has caused the Debian Bug report #473940, regarding rudiments: FTBFS: error: unrecognized command li

Bug#477013: marked as done (esperanza: FTBFS: Checking for Xmms2 Client C++ Bindings ... no)

Your message dated Sat, 26 Apr 2008 02:25:26 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#477013: esperanza: FTBFS: Checking for Xmms2 Client C++ Bindings ... no has caused the Debian Bug report #477013, regarding esperanza: FTBFS: Checking for Xmms2 Client C++ Bindings ...

Bug#476069: marked as done (nessus-libraries: FTBFS: configure: error: can only configure for one host and one target at a time)

Your message dated Fri, 25 Apr 2008 22:32:14 + with message-id <[EMAIL PROTECTED]> and subject line Bug#476069: fixed in nessus-libraries 2.2.10-2 has caused the Debian Bug report #476069, regarding nessus-libraries: FTBFS: configure: error: can only configure for one host and one target at a

Bug#476016: marked as done (poker-engine: FTBFS: 1 of 22 tests failed)

Your message dated Sat, 26 Apr 2008 02:27:11 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#476016: poker-engine: FTBFS: 1 of 22 tests failed has caused the Debian Bug report #476016, regarding poker-engine: FTBFS: 1 of 22 tests failed to be marked as done. This means that you

Bug#474630: original motivation for __init__.py detection

Hi. I'm also an upstream developer on both Twisted and Nevow. Chris just explained what's going on to me and I think it might be helpful in resolving this issue if I explained the twisted plugin system's motivation and design in a bit more depth. Basically, the idea behind the Twisted plug

Processed: tagging 476987

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.25 > tags 476987 confirmed pending Bug#476987: exim4-daemon-light: fails to install: incompatible command-line options or arguments There were no tags set. Tags added: confirmed, pending

Processed: tagging 477258

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.25 > tags 477258 confirmed pending Bug#477258: Fails to start because of incorrect command-line arguments Tags were: pending confirmed patch Bug#477194: exim4: Starting MTA:exim: incompat

Bug#477260: kexec-tools: fails to build on powerpc.

On Fri, Apr 25, 2008 at 01:52:10PM -0600, Khalid Aziz wrote: > Previous release of kexec-tools did not build on powerpc which is why I > had removed powerpc from the list of architectures (see > ). Are you sure > this version (20080227) build

Processed: tagging 477236

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.25 > tags 477236 confirmed pending Bug#477236: exim4-daemon-heavy: restart of exim4 fails after pdate Tags were: pending confirmed patch Bug#477194: exim4: Starting MTA:exim: incompatibl

Bug#476069: nessus-libraries: FTBFS: configure: error: can only configure for one host and one target at a time

On Mon, Apr 14, 2008 at 01:41:09PM +0200, Lucas Nussbaum wrote: > Package: nessus-libraries > Version: 2.2.10-1 > Severity: serious > User: [EMAIL PROTECTED] > Usertags: qa-ftbfs-20080413 qa-ftbfs > Justification: FTBFS on i386 > > Hi, > > During a rebuild of all packages in sid, your package fai

Processed: Mark as fixed in unstable...

Processing commands for [EMAIL PROTECTED]: > fixed 477068 1.8.1.14-1 Bug#477068: xulrunner_1.9~b5-2(mips/experimental): FTBFS: expected constructor, destructor, or type conversion before 'XPTC_InvokeByIndex' Bug marked as fixed in version 1.8.1.14-1. > thanks Stopping processing here. Please co

Processed: tagging 477239

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.25 > tags 477239 confirmed pending Bug#477239: exim4-base: empty argument in init.d prevents starting Tags were: pending confirmed patch Bug#477194: exim4: Starting MTA:exim: incompatible

Bug#477068: Mark as fixed in unstable...

fixed 477068 1.8.1.14-1 thanks As discussed on #debian-bugs, the BTS believes that 1.8.1.14-1 is affected by this bug, because the changelog entry for 1.9~b5-3 merged the unstable changelog, see [1]. As suggested by vorlon, I'm correcting the BTS' opinion on this matter, rather than using a bigge

Bug#477735: marked as done (vifm_0.3a-2(sparc/unstable): FTBFS on sparc; missing dependencies)

Your message dated Fri, 25 Apr 2008 21:02:46 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477735: fixed in vifm 0.3a-3 has caused the Debian Bug report #477735, regarding vifm_0.3a-2(sparc/unstable): FTBFS on sparc; missing dependencies to be marked as done. This means that you

Bug#477772: bug affects arm and armel

I'm seeing this bug on armel, so I guess the bug affects both arm and armel. There's also a FTBFS on armel, it crashes while running the test suite: http://buildd.debian.org/fetch.cgi?&pkg=subversion&ver=1.4.6dfsg1-3&arch=armel&stamp=1208240382&file=log -- see shy jo signature.asc Description

Bug#477808: marked as done (blender: CVE-2008-1102 arbitrary code execution via crafted .blend file)

Your message dated Fri, 25 Apr 2008 21:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477808: fixed in blender 2.45-5 has caused the Debian Bug report #477808, regarding blender: CVE-2008-1102 arbitrary code execution via crafted .blend file to be marked as done. This means

Processed: tagging 477194

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.25 > tags 477194 confirmed pending Bug#477194: exim4: Starting MTA:exim: incompatible command-line options or arguments Tags were: pending confirmed patch Bug#477236: exim4-daemon-heavy:

Bug#477454: bugs is serious, sorry

> Am Donnerstag, 24. April 2008 19:46:38 schrieben Sie: > > No, this can't result in a lawsuit against Debian, please take your > > bullshit elsewhere, kthxbye. > At least in Germany, it can. It is not legal to insult a person in public > (even with free speech). So if Sebastian Dröge is indeed fr

Bug#470860: marked as done (distcc has missing depends on dbus)

Your message dated Fri, 25 Apr 2008 21:02:11 + with message-id <[EMAIL PROTECTED]> and subject line Bug#470860: fixed in distcc 2.18.3-6 has caused the Debian Bug report #470860, regarding distcc has missing depends on dbus to be marked as done. This means that you claim that the problem has

Processed: tagging 477562

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.25 > tags 477562 confirmed pending Bug#477562: exim4-daemon-light: init script fails to start: incompatible command-line options or arguments Tags were: patch Bug#477194: exim4: Starting

Bug#477438: roundup - security update broke my installation

Hi, On Fri, 25.04.2008 at 19:21:16 +0200, Andreas Unterkircher <[EMAIL PROTECTED]> wrote: > Just want to confirm that my roundup installation also stopped working > after the security update - the same symptoms like Floris described. > I was able to fix it like it was described by Floris, but

Bug#468050: marked as done (Security problems present in xwine)

Your message dated Fri, 25 Apr 2008 22:23:45 +0100 with message-id <[EMAIL PROTECTED]> and subject line xwine has been removed from Debian, closing #468050 has caused the Debian Bug report #468050, regarding Security problems present in xwine to be marked as done. This means that you claim that t

  1   2   3   >