Bug#323895: libglademm2.0: builds a library package with the same name and different ABI on rebuild

Package: libglademm2.0 Severity: serious libglademm2.0-1c102 is a shared library that exports C++ interfaces, which means that it must undergo the transition described at if the package is to remain in Debian. However, since th

Bug#323896: libtextwrap-dev: Fail to upgrade when libtextwrap1 0.1-1 is installed

Package: libtextwrap-dev Version: 0.1-2 Severity: serious Setting severity to serious as I believe policy states clearly that a package must conflict with other packages containing the same file as the package itself. When trying to upgrade my sid chroot, I ran into this problem: Unpacking re

Bug#323737: FTBFS: Too few template-parameter lists

On Fri, Aug 19, 2005 at 08:03:38AM +0200, Kevin Glynn wrote: > Matt Kraai writes: > > Package: mozart > > Version: 1.3.1.20040616-8 > > Severity: serious > > > > mozart fails to build because of two "too few > > template-parameter-lists" errors: > > > > > c++ -DHAVE_CONFIG_H -I. > -I/tmp

Processed: merging 323852 323887, merging 323852 323890

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.4 > merge 323852 323887 Bug#323852: unknown token: db_fset Bug#323887: /var/lib/dpkg/info/base-config.postinst: line 59: syntax error near unexpected token `db_fset' Bug#323854: Bug in po

Bug#323893: python2.3-syck: Segfault when parsing

Package: python2.3-syck Version: 0.42-9 Severity: grave Justification: renders package unusable Segfault when trying to parse YAML data. I have included the YAML data as well as a the end of a strace log just in case. --- BEGIN YAML DATA: --- --- ## #

Bug#323737: FTBFS: Too few template-parameter lists

Matt Kraai writes: > Package: mozart > Version: 1.3.1.20040616-8 > Severity: serious > > mozart fails to build because of two "too few > template-parameter-lists" errors: > > > c++ -DHAVE_CONFIG_H -I. > > -I/tmp/buildd/mozart-1.3.1.20040616/mozart/platform/emulator > > -DSITE_PROPERT

Bug#323890: acknowledged by developer (Re: Bug#323890: base-config: db_fset bug *still* exists)

> Debian Bug Tracking System <[EMAIL PROTECTED]> [2005-08-19 > 07:53]: > > This is an automatic notification regarding your Bug report #323890: > base-config: db_fset bug *still* exists, which was filed against the > base-config package. > > It has been closed by one of the developers, namely Stev

Processed: patches submitted to svn

Processing commands for [EMAIL PROTECTED]: > package zaptel-source Ignoring bugs not assigned to: zaptel-source > tags 302836 + pending Bug#302836: zaptel-source: zaphfc module missing after compiling modules Tags were: patch Tags added: pending > tags 323753 + pending Bug#323753: zaptel-source:

Bug#323890: marked as done (base-config: db_fset bug *still* exists)

Your message dated Thu, 18 Aug 2005 22:35:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323890: base-config: db_fset bug *still* exists has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the ca

Bug#323887: marked as done (/var/lib/dpkg/info/base-config.postinst: line 59: syntax error near unexpected token `db_fset')

Your message dated Thu, 18 Aug 2005 22:30:55 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323887: /var/lib/dpkg/info/base-config.postinst: line 59: syntax error near unexpected token `db_fset' has caused the attached Bug report to be marked as done. This means that you claim tha

Processed: severity of 323852 is grave, merging 323852 323863, severity of 323887 is grave ... ... ...

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.4 > severity 323852 grave Bug#323852: unknown token: db_fset Bug#323854: Bug in postinst script causes installation failure Severity set to `grave'. > merge 323852 323863 Bug#323852: unkn

Processed: tagging 320017

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.8.14 > tags 320017 + pending Bug#320017: vim: Arbitrary code execution in modelines (CAN-2005-2368) Tags were: woody sarge patch security Tags added: pending > End of message, stopping proc

Bug#323890: base-config: db_fset bug *still* exists

Package: base-config Version: 2.70 Severity: serious the bug db_fset *still* exists! /var/lib/dpkg/info/base-config.postinst: line 59: syntax error near unexpected token `db_fset' dpkg: error processing base-config (--configure): subprocess post-installation script returned error exit status 2

Bug#323883: neutrino: ftbfs [sparc] Package requirements (libnjb >= 2.2) were not met.

Package: neutrino Version: 0.8.4-2 Severity: serious Justification: fails to build from source neutrino failed to build on a sparc buildd. It did build on my sparc pbuilder however. My guess is this may be due to a build-dependancy that should be versioned and isn't. checking for xgettext... /

Bug#317082: Not just a dpkg bug

On Thu, Aug 18, 2005 at 02:47:46PM +0900, GOTO Masanori wrote: > At Wed, 17 Aug 2005 22:05:42 +0200, > Andreas Jochens wrote: > > I guess you will generally have many more issues than this one when you > > try to build 64-bit packages on a 32-bit buildd (e.g. compiling and > > running 64-bit prog

Bug#323881: bakery2.0: builds a library package with the same name and different ABI on rebuild

Package: bakery2.0 Severity: serious libbakery2.0-1 is a shared library that exports C++ interfaces, which means that it must undergo the transition described at if the package is to remain in Debian. However, since this librar

Processed: (no subject)

Processing commands for [EMAIL PROTECTED]: > severity 323863 grave Bug#323863: base-config: line 59: syntax error near unexpected token `db_fset' Severity set to `grave'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrat

Bug#323863: marked as done (base-config: line 59: syntax error near unexpected token `db_fset')

Your message dated Thu, 18 Aug 2005 21:31:47 -0400 with message-id <[EMAIL PROTECTED]> and subject line (no subject) has caused the attached Bug report 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 your responsibility to reo

Bug#323854: marked as done (Bug in postinst script causes installation failure)

Your message dated Thu, 18 Aug 2005 20:58:00 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#323854: Bug in postinst script causes installation failure has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#318553: marked as done (newlib: FTBFS: Tries to build 64-bit version without amd64-libs-dev)

Your message dated Thu, 18 Aug 2005 17:32:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#318553: fixed in newlib 1.13.0-1 has caused the attached Bug report 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 yo

Bug#323365: marked as done (bluez-utils: Arbitrary command execution through inproper escaping in hcid's security.c)

Your message dated Thu, 18 Aug 2005 17:32:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323365: fixed in bluez-utils 2.19-1 has caused the attached Bug report 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

Bug#323852: marked as done (unknown token: db_fset)

Your message dated Thu, 18 Aug 2005 20:58:00 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#323854: Bug in postinst script causes installation failure has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#323858: marked as done (monotone: package has unmet dependencies)

Your message dated Thu, 18 Aug 2005 17:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323858: fixed in monotone 0.22-2 has caused the attached Bug report 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 yo

Bug#323798: [sparc] corrupted double-linked list

At Thu, 18 Aug 2005 15:56:19 +0200, Andreas Barth wrote: > during building openmotif on sparc, this error happened: > > gcc -g -O2 -Wall -Wno-unused -Wno-comment -o .libs/periodic periodic.o > ../../../lib/Xm/.libs/libXm.so -L/usr/X11R6/lib > ../../../lib/Mrm/.libs/libMrm.so > /build/buildd/op

Bug#323874: gftp-gtk: Crashes on disconnect

Package: gftp-gtk Version: 2.0.18-7 Severity: grave Justification: renders package unusable After connecting to a remote ftp server to upload a file, clicking on the disconnect icon causes gftp to crash (disappears from the workspace). It happened several times and once caused the system to lock

Bug#323040: CAN number

This is CAN-2005-2612 -- see shy jo signature.asc Description: Digital signature

Bug#323854: base-config: syntax error near db_fset

Package: base-config Version: 2.70 Followup-For: Bug #323854 After unpacking 0B of additional disk space will be used. Setting up base-config (2.70) ... /var/lib/dpkg/info/base-config.postinst: line 59: syntax error near unexpected token `db_fset' dpkg: error processing base-config (--configure)

Bug#323852: base-config fails to install

Package: base-config Version: 2.70 Followup-For: Bug #323852 Installing base-config gives the following error: /var/lib/dpkg/info/base-config.postinst: line 59: syntax error near unexpected token `db_fset' -- System Information: Debian Release: testing/unstable APT prefers unstable APT polic

Bug#323858: monotone: package has unmet dependencies

James Ring skrev: > I've tried to install monotone for the first time this morning, and it > comes up with the following error: > > The following packages have unmet dependencies: > monotone: Depends: libboost-date-time1.33.0 (< > 1.32.0+1.33.0-cvs20050727-99) but 1.33.0-1 is to be installed >

Bug#322723: #322723 D-I: 'id route add' fails w/ "Network is unreachable"

With help from waldi I have done some additional tests for this issue yesterday and today. Here are the main results: - the problem is still there if Sarge's 'ip' is used instead of the busybox version - the problem is still there if the new linux-image-2.6.12-1-386 (2.6.12-5) kernel is used

Processed: reassign 323506 to beecrypt, bug 323506 is forwarded to Bob Deblier <[EMAIL PROTECTED]> ...

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.4 > reassign 323506 beecrypt Bug#323506: libbeecrypt6-dev: Can't build anything Bug reassigned from package `libbeecrypt6-dev' to `beecrypt'. > forwarded 323506 Bob Deblier <[EMAIL PROTEC

Bug#323858: monotone: package has unmet dependencies

Package: monotone Severity: grave Justification: renders package unusable Subject: monotone: Package has unmet dependencies in Sid? Package: monotone Severity: grave Justification: renders package unusable Hi there, I've tried to install monotone for the first time this morning, and it comes up

Processed: Re: Bug#323854: Bug in postinst script causes installation failure

Processing commands for [EMAIL PROTECTED]: > severity 323854 serious Bug#323854: Bug in postinst script causes installation failure Severity set to `serious'. > merge 323854 323852 Bug#323852: unknown token: db_fset Bug#323854: Bug in postinst script causes installation failure Merged 323852 3238

Bug#323722: maintainer seems MIA, we should orphan this package.

On Thu, Aug 18, 2005 at 11:02:21AM -0600, Hubert Chan wrote: > On Thu, 18 Aug 2005 12:57:18 +0200, Sven Luther <[EMAIL PROTECTED]> said: > > >> Well, in fact, there was a quite harsh discussion re: progsreiserfs, > >> including upstream Hans Reiser himself. > > > Mmm, i was under the impression t

Bug#323852: More information...

1. This is not a serious policy issue (severity: serious) but an important bug (severity: important). 2. The problem is a syntax error in the "for" list, in which the last item contains a backslash when it shouldn't. 3. Look at bug # 323854 for a patch/workaround until this is fixed in the packag

Processed: Re: Bug#323506: libbeecrypt6-dev: Can't build anything

Processing commands for [EMAIL PROTECTED]: > severity 320425 grave Bug#320425: beecrypt: /usr/lib/libbeecrypt.so: undefined reference to `b64crc' Severity set to `grave'. > merge 320425 323506 Bug#320425: beecrypt: /usr/lib/libbeecrypt.so: undefined reference to `b64crc' Bug#323506: libbeecrypt6-

Bug#323506: libbeecrypt6-dev: Can't build anything

severity 320425 grave merge 320425 323506 thanks On Thu, Aug 18, 2005 at 10:23:06PM +1000, Anibal Monsalve Salazar wrote: > On Thu, Aug 18, 2005 at 07:12:08AM -0500, John Goerzen wrote: > >On Thu, Aug 18, 2005 at 02:52:04PM +1000, Anibal Monsalve Salazar wrote: > >>On Tue, Aug 16, 2005 at 10:40:10

Bug#323852: unknown token: db_fset

Package: base-config Version: 2.70 Severity: serious Upgrading from 2.69 to 2.70 I got the following lines: Preparing to replace base-config 2.69 (using .../base-config_2.70_all.deb) ... Unpacking replacement base-config ... Setting up base-config (2.70) ... /var/lib/dpkg/info/base-config.postinst

Bug#319568: marked as done (FTBFS: Missing namespace qualifiers)

Your message dated Thu, 18 Aug 2005 13:32:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#319568: fixed in dansguardian 2.8.0.6-antivirus-6.3.8-1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#292792: marked as done (insecure temporary file security holes (CAN-2005-0017 CAN-2005-0018))

Your message dated Thu, 18 Aug 2005 13:32:19 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#292792: fixed in f2c 20020621-4 has caused the attached Bug report 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 you

Bug#305971: marked as done (f2c: segfaults on m68k)

Your message dated Thu, 18 Aug 2005 13:32:19 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#305971: fixed in f2c 20020621-4 has caused the attached Bug report 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 you

Bug#309321: marked as done (approx: Approx stops processing TCP rx queue)

Your message dated Thu, 18 Aug 2005 16:55:19 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#309321: approx: Approx stops processing TCP rx queue has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not t

Bug#323741: marked as done (FTBFS: Cannot find emacs)

Your message dated Thu, 18 Aug 2005 13:32:50 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323741: fixed in muse-el 3.01.arch.201-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it i

Bug#322746: any progress?

Is there any progress being made on this bug? I can't install any more debconf-using packages on my system, or packages uses perl for maintainer scripts, and this is quite bad. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' :proud Debian developer and author: http://debiansystem.inf

Processed: merging 304604 322746, severity of 322746 is critical

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.5 > merge 304604 322746 Bug#304604: perl: heap corruption causes installation of other packages to fail (debconf is aborting) with new glibc Bug#322746: glibc detected *** double free or

Bug#322210: [m68k] ocaml-nox: can not be removed

On Thu, Aug 18, 2005 at 09:48:10AM +0200, Stefano Zacchiroli wrote: > On Thu, Aug 18, 2005 at 07:56:28AM +0200, Christian T. Steigies wrote: > > I tried to clean my buildd and now its broke worse than ever: > > > > Preparing to replace ocaml-nox 3.08.3-6 (using > > .../ocaml-nox_3.08.3-7_m68k.deb)

Bug#323734: FTBFS: Unsatisfiable build-dependency on ocaml-nox-3.08

Hello, On Wed, Aug 17, 2005 at 08:33:30AM -0700, Matt Kraai wrote: > Package: mldonkey > Version: 2.5.28-2 > Severity: serious > > mldonkey fails to build because it has an unsatisfiable > build-dependency on ocaml-nox-3.08: > > > -> Considering ocaml-nox-3.08 > >-> Trying ocaml-nox-3.08 >

Processed: retitle 320017 to vim: Arbitrary code execution in modelines (CAN-2005-2368)

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.4 > # Add CVE ID. > retitle 320017 vim: Arbitrary code execution in modelines (CAN-2005-2368) Bug#320017: vim: Arbitrary code execution in modelines Changed Bug title. > End of message,

Bug#323722: maintainer seems MIA, we should orphan this package.

Sven Luther wrote: >On Thu, Aug 18, 2005 at 05:37:48PM +0200, Jos? Luis Tall?n wrote: > > >>Sven Luther wrote: >> >> > >Well, i personally couldn't care less, since i don't use reiserfs, which is >known to eat data for breakfast, > Hmmm... that was *years* ago, when Linux2.4's VM was not st

Bug#323819: evolution-sharp: FTBFS: Package mono was not found in the pkg-config sear path

Package: evolution-sharp Version: 0.8-1 Severity: serious Hi, Your package is failing to build with the following error: checking for mono >= 1.0.0... Package mono was not found in the pkg-config search path. Perhaps you should add the directory containing `mono.pc' to the PKG_CONFIG_PATH envir

Processed: Re: e2fsck segfault

Processing commands for [EMAIL PROTECTED]: > severity 318463 grave Bug#318463: e2fsck segfault Severity set to `grave'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIB

Bug#266164: marked as done (qt-embedded-free: FTBFS with gcc-3.4: there are no arguments to `clear' that depend on a template parameter, so a declaration of `clear' must be available)

Your message dated Thu, 18 Aug 2005 18:56:59 +0200 with message-id <[EMAIL PROTECTED]> and subject line Removed has caused the attached Bug report 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 your responsibility to reopen t

Bug#295147: marked as done (Library package of older version without reverse-depends)

Your message dated Thu, 18 Aug 2005 18:56:59 +0200 with message-id <[EMAIL PROTECTED]> and subject line Removed has caused the attached Bug report 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 your responsibility to reopen t

Bug#323722: maintainer seems MIA, we should orphan this package.

On Thu, 18 Aug 2005 12:57:18 +0200, Sven Luther <[EMAIL PROTECTED]> said: >> Well, in fact, there was a quite harsh discussion re: progsreiserfs, >> including upstream Hans Reiser himself. > Mmm, i was under the impression that there are two different things, > progreiserfs and reiserfsprog, one

Bug#323722: maintainer seems MIA, we should orphan this package.

On Thu, Aug 18, 2005 at 05:37:48PM +0200, Jos? Luis Tall?n wrote: > Sven Luther wrote: > > >On Thu, Aug 18, 2005 at 12:40:11PM +0200, Jos? Luis Tall?n wrote: > > > > > > > >Ok, but now that sarge is released, what are the plans for etch ? The > >question > >is if i keep parted without reiserfs

Bug#323669: baycomusb: FTBFS: error: 'USBDEVFS_URB_ISO_ASAP' undeclared

On Thu, Aug 18, 2005 at 08:56:32AM +0200, Joop PG4I wrote: > On 8/17/05, Kurt Roeckx <[EMAIL PROTECTED]> wrote: > > > adapttests.c:1312: error: 'USBDEVFS_URB_ISO_ASAP' undeclared (first use in > > this > > function) > > I don't understand. USBDEVFS_URB_ISO_ASAP is declared 0x0002 in > ../usbdrv/

Bug#297849: marked as done (ts10: FTBFS (amd64/gcc-4.0): static declaration of 'dataMode' follows non-static declaration)

Your message dated Thu, 18 Aug 2005 09:02:30 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#297849: fixed in ts10 0.8.030519-1 has caused the attached Bug report 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

Bug#323741: FTBFS: Cannot find emacs

Matt Kraai <[EMAIL PROTECTED]> writes: > Package: muse-el > Version: 3.01.arch.201-2 > Severity: serious > Tags: patch > > muse-el fails to build because it cannot find emacs: > >> EMACS=emacs SITEFLAG=--no-site-file ../scripts/publish html QuickStart >> ../scripts/publish: line 4: emacs: command

Bug#323722: maintainer seems MIA, we should orphan this package.

Sven Luther wrote: >On Thu, Aug 18, 2005 at 12:40:11PM +0200, Jos? Luis Tall?n wrote: > > > >Ok, but now that sarge is released, what are the plans for etch ? The question >is if i keep parted without reiserfs support, or if i add it again ? > > If there really is interest in support for Reis

Bug#323738: marked as done (FTBFS: tar options passed after contents)

Your message dated Thu, 18 Aug 2005 07:17:03 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323738: fixed in mindterm 1.2.1-11 has caused the attached Bug report 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

Bug#323463: marked as done (cfdisk: segmentation fault)

Your message dated Thu, 18 Aug 2005 07:32:15 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323463: fixed in util-linux 2.12p-6 has caused the attached Bug report 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

Bug#323726: marked as done (FTBFS: Unable to include Xv.h and Xvlib.h)

Your message dated Thu, 18 Aug 2005 16:07:27 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug already fixed has caused the attached Bug report 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 your responsibility t

Bug#323798: [sparc] corrupted double-linked list

Package: glibc Version: 2.3.5-3 Severity: serious Hi, during building openmotif on sparc, this error happened: gcc -g -O2 -Wall -Wno-unused -Wno-comment -o .libs/periodic periodic.o ../../../lib/Xm/.libs/libXm.so -L/usr/X11R6/lib ../../../lib/Mrm/.libs/libMrm.so /build/buildd/openmotif-2.2.3

Bug#319563: marked as done (FTBFS: PIC register %ebx clobbered in asm)

Your message dated Thu, 18 Aug 2005 06:32:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#319563: fixed in ffmpeg 0.cvs20050811-1 has caused the attached Bug report 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

Processed: Re: Bug#312618: reopen

Processing commands for [EMAIL PROTECTED]: > reopen 322210 Bug#322210: [m68k] ocaml-nox: can not be removed Bug reopened, originator not changed. > merge 312618 322210 Bug#312618: ocaml-nox: Installation fails when emacsen-common is not configured Bug#322210: [m68k] ocaml-nox: can not be removed

Bug#323659: marked as done (libquicktime1: Fails at install.)

Your message dated Thu, 18 Aug 2005 15:26:19 +0200 with message-id <[EMAIL PROTECTED]> and subject line libquicktime4linux0 doesn't exist in Debian has caused the attached Bug report 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

Bug#322210: Bug#312618: reopen

reopen 322210 merge 312618 322210 thanks On Thu, Aug 18, 2005 at 03:03:37PM +0200, Robert Millan wrote: > > Preparing to replace ocaml-nox 3.08.3-3 (using > .../ocaml-nox_3.08.3-7_i386.deb) ... > ERROR: emacsen-common being used before being configured. > ERROR: This is likely a bug in the ocaml

Bug#312618: reopen

reopen 312618 thanks Same bug strikes again? Either of the prerm's fail so seemingly there is no upgrade path. Preparing to replace ocaml-nox 3.08.3-3 (using .../ocaml-nox_3.08.3-7_i386.deb) ... ERROR: emacsen-common being used before being configured. ERROR: This is likely a bug in the ocaml-n

Processed: subversion

Processing commands for [EMAIL PROTECTED]: > # Yes, it seems to be related to libapr0 > retitle 316143 subversion: segfault when adding a directory Bug#316143: subversion: segfault (not due to libapr0) when add a directory Changed Bug title. > -- Stopping processing here. Please contact me if yo

Processed: reopen

Processing commands for [EMAIL PROTECTED]: > reopen 312618 Bug#312618: ocaml-nox: Installation fails when emacsen-common is not configured Bug reopened, originator not changed. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator

Processed: Re: Bug#317104: Patch

Processing commands for [EMAIL PROTECTED]: > tag 317104 pending Bug#317104: libgda2: FTBFS: cannot find postgresql headers Tags were: patch Tags added: pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, D

Processed: WTF?

Processing commands for [EMAIL PROTECTED]: > severity 208967 grave Bug#208967: docbook2man uses hyphens instead of minus signs Severity set to `grave'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bu

Bug#317104: Patch

tag 317104 pending thanks On Thu, Aug 18, 2005 at 09:19:57AM +0200, Martin Pitt wrote: > tag 317104 patch > thanks > > Hi! Hi, > I announced this transition long ago, described how to fix it, and > even provided a patch: > > > http://people.ubuntu.com/~pitti/patches/postgresql-transition/li

Bug#321360: Bug actually in linux-kernel-headers

Hi, For the record, this bug is actually due to an error in the linux-kernel-headers. I already filed a bug for it a couple of weeks ago, see #321246. Regards, Regis -- "While a monkey can be a manager, it takes a human to be an engineer" Erik Zapletal

Bug#323506: libbeecrypt6-dev: Can't build anything

On Thu, Aug 18, 2005 at 07:12:08AM -0500, John Goerzen wrote: >On Thu, Aug 18, 2005 at 02:52:04PM +1000, Anibal Monsalve Salazar wrote: >>On Tue, Aug 16, 2005 at 10:40:10PM -0500, John Goerzen wrote: >>>collect2: ld returned 1 exit status >> >>Please see bug #323500. > >Did you perhaps mean 320425?

Bug#323399: marked as done (snowflake: segfaults)

Your message dated Thu, 18 Aug 2005 05:02:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323399: fixed in snowflake 0.01a-7 has caused the attached Bug report 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

Bug#323506: libbeecrypt6-dev: Can't build anything

On Thu, Aug 18, 2005 at 02:52:04PM +1000, Anibal Monsalve Salazar wrote: > On Tue, Aug 16, 2005 at 10:40:10PM -0500, John Goerzen wrote: > >collect2: ld returned 1 exit status > > Please see bug #323500. Did you perhaps mean 320425? I looked at it, and it looked similar, but I couldn't tell for

Bug#323124: tinyca: crashes on startup

On Thu, Aug 18, 2005 at 01:36:12PM +0200, Martin Zobel-Helas wrote: > > [EMAIL PROTECTED]:~$ tinyca2 > > Gtk-CRITICAL **: gtk_widget_get_style: assertion `GTK_IS_WIDGET > > (widget)' failed at /usr/lib/tinyca/CERT.pm line 119. > > Segmentatie fout > > Could you send a backtrace please, i can't rep

Processed: tor: setting found and fixed

Processing commands for [EMAIL PROTECTED]: > # mark it as existing in all versions currently in Debian but the latest > # hurd > found #323786 0.0.9.10-1 Bug#323786: Tor security advisory: DH handshake flaw Bug marked as found in version 0.0.9.10-1. > # m68k, also testing > found #323786 0.1.0.12

Bug#323733: FTBFS

Hi, it looks like this FTBFS is caued by building it with "-Os". This seems to exclude the __buildin_* intrinsics that are used for memcmp (#define memcmp __buildin_memcmp). Cheers, Michael -- Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo -- To UNSUBSCRIBE, email

Bug#310398: pgadmin3 and pgadmin3-data versions

Hi It would appear that pgadmin3 is uninstallable because of version incompatibility between the two packages: pgadmin31.0.2-7 pgadmin3-data 1.2.0-2 Is this likely to be resolved soon or is there a prescribed workaround? Thanks Clive -- www.clivemenzies.co.uk ... ...strategies for

Bug#323124: tinyca: crashes on startup

Hi Jasper, > When trying tot start the new version of tinyca, it crashes directly: > > [EMAIL PROTECTED]:~$ tinyca2 > Gtk-CRITICAL **: gtk_widget_get_style: assertion `GTK_IS_WIDGET > (widget)' failed at /usr/lib/tinyca/CERT.pm line 119. > Segmentatie fout Could you send a backtrace please, i ca

Bug#323786: Tor security advisory: DH handshake flaw

Package: tor Version: 0.1.0.11-1 Severity: grave Tags: security - Forwarded message from Roger Dingledine <[EMAIL PROTECTED]> - From: Roger Dingledine <[EMAIL PROTECTED]> Subject: Tor security advisory: DH handshake flaw To: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Date: Thu, 11 Aug

Bug#322112: marked as done (mailman: Group mismatch error for wrapper script)

Your message dated Thu, 18 Aug 2005 12:37:05 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#322112: mailman: Group mismatch error for wrapper script has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#323619: typo in python-egenix-stack dependency

reassign 323619 python-egenix-mxstack thanks * Matthias Klose <[EMAIL PROTECTED]> [2005-08-17 18:04]: > Package: python-egenix-stack > Version: 2.0.6-1 Do you mean egenix-mx-base which builds python2.x-egenix-mxstack packages? (stack vs mxstack) -- Martin Michlmayr http://www.cyrius.com/ -- T

Processed: Re: Bug#323619: typo in python-egenix-stack dependency

Processing commands for [EMAIL PROTECTED]: > reassign 323619 python-egenix-mxstack Bug#323619: typo in python-egenix-stack dependency Warning: Unknown package 'python-egenix-stack' Bug reassigned from package `python-egenix-stack' to `python-egenix-mxstack'. > thanks Stopping processing here. Pl

Bug#320036: marked as done (bash exits 0 on errors reading stdin (and perhaps other scripts))

Your message dated Thu, 18 Aug 2005 13:05:10 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#320036: bash exits 0 on errors reading stdin (and perhaps other scripts) (forwarded from Ian Jackson) has caused the attached Bug report to be marked as done. This means that you claim that

Processed: Re: Bug#323773: apache 1.3.33-7 segfaults when php4_module 4.4.0-1 enabled

Processing commands for [EMAIL PROTECTED]: > reassign 323773 libapache-mod-php4 Bug#323773: apache 1.3.33-7 segfaults when php4_module 4.4.0-1 enabled Bug reassigned from package `apache' to `libapache-mod-php4'. > kthxbye Stopping processing here. Please contact me if you need assistance. Debi

Processed: Re: Bug#323747: kdelibs-data: upgrading from 4:3.3.2-6.1 to 4:3.4.2-1 broke kicker & konqueror & more

Processing commands for [EMAIL PROTECTED]: > severity 323747 serious Bug#323747: kdelibs-data: upgrading from 4:3.3.2-6.1 to 4:3.4.2-1 broke kicker & konqueror & more Severity set to `serious'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking sys

Bug#323773: apache 1.3.33-7 segfaults when php4_module 4.4.0-1 enabled

reassign 323773 libapache-mod-php4 kthxbye Please be more careful in your selection of packages to file bugs against in future. -Thom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#323399: confirmed

On Thu, 2005-08-18 at 09:59 +0100, Paul Brossier wrote: > for info, i could reproduce this bug using the latest X packages and > debian kernel. Thanks. Hm. The bug seems to be here (from semctl(2)): This function has three or four arguments, depending on cmd. When there are

Processed: not a bug, at least not in lam4-dev

Processing commands for [EMAIL PROTECTED]: > severity 316815 normal Bug#316815: there is no i386-linux-g++ Severity set to `normal'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) --

Processed: RE: sodipodi: segfault on startup on 64 bit platforms

Processing commands for [EMAIL PROTECTED]: > severity 287925 serious Bug#287925: sodipodi: segfault on startup on 64 bit platforms Severity set to `serious'. > tags 287925 +patch Bug#287925: sodipodi: segfault on startup on 64 bit platforms There were no tags set. Tags added: patch > thanks Stop

Bug#316815: not a bug, at least not in lam4-dev

severity 316815 normal thanks run strings on the binary, it does have i486-linux-gnu-g++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#323722: marked as done (maintainer seems MIA, we should orphan this package.)

Your message dated Thu, 18 Aug 2005 02:41:57 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323722: maintainer seems MIA, we should orphan this package. has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#321210: marked as done (debtags-edit: ftbfs [sparc] error: 'consumer' was not declared in this scope)

Your message dated Thu, 18 Aug 2005 11:24:19 +0200 with message-id <[EMAIL PROTECTED]> and subject line debtags-edit has been build for sparc has caused the attached Bug report 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

Processed: test case for semctl segv on ppc

Processing commands for [EMAIL PROTECTED]: > reassign 323399 libc6 Bug#323399: snowflake: segfaults Bug reassigned from package `snowflake' to `libc6'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bu

Bug#323722: maintainer seems MIA, we should orphan this package.

Roberto Lumbreras wrote: >Hi Sven... > >Jose Luis Tallon email is bouncing because he seems to be using some >stupid RBL that bans every DSL user in the planet. Try sending mail from >other account and it will work. > > Thanks, Rober... i'll have to remove that i think. >Jose Luis is in the new

Bug#317082: Not just a dpkg bug

At Thu, 18 Aug 2005 10:24:14 +0200, Andreas Jochens wrote: > There is already an inofficial buildd for the ppc64 architecture > running for 'unstable'. The respective ppc64 package archive is located at > > deb http://debian-ppc64.alioth.debian.org/gcc4 unstable main > > and almost 95% of all sou

Bug#318510: jni.h

to get the include directory and the include file, use: $ gcc --print-file-name=include/jni.h /usr/lib/gcc/i486-linux-gnu/4.0.2/include/jni.h $ gcc --print-file-name=include /usr/lib/gcc/i486-linux-gnu/4.0.2/include however, that directory is in the standard include path. -- To UNSUBSCRIBE,

  1   2   >