Bug#342931: doesn't work on alpha

reassign 342931 klibc 1.1.1-4 # completely broken binaries on an arch == RC severity 342931 grave tags 342931 patch thanks Well, I haven't been able to reproduce Norbert's exact error, but I think this may be due to differences in successive versions of klibc. Here's what I am able to reproduce:

Processed: Re: doesn't work on alpha

Processing commands for [EMAIL PROTECTED]: reassign 342931 klibc 1.1.1-4 Bug#342931: doesn't work on alpha Bug reassigned from package `initramfs-tools' to `klibc'. # completely broken binaries on an arch == RC severity 342931 grave Bug#342931: doesn't work on alpha Severity set to `grave'.

Bug#320548: libsdl-perl: broken dependency

Le vendredi 16 décembre 2005 à 01:21 +0100, Tanguy Ortolo a écrit : Package: libsdl-perl Followup-For: Bug #320548 libsdl-perl needs libsdl-gfx1.2, that has been replaced by libsdl-gfx1.2-dev. What do you mean ? One is the shared library, the other is the development library. -- .''`.

Bug#343571: libc6: FTBFS [powerpc] weak alias issues

Package: libc6 Version: 2.3.5-8 Severity: serious Tags: patch Justification: no longer builds from source I was unable to build the latest version of glibc on an up to date powerpc unstable system. The following patch fixes it for me. The fixes come straight out of mainline glibc. ---

Bug#339415: libc6: Seen also on powerpc

Package: libc6 Version: 2.3.5-8 Followup-For: Bug #339415 The following patch, taken from mainline glibc cvs fixes the problem for me. --- sysdeps/wordsize-32/Makefile~ 2002-09-19 01:47:56.0 -0500 +++ sysdeps/wordsize-32/Makefile2005-11-16 13:19:03.0 -0600 @@ -2,5

Processed: Re: [Pkg-alsa-devel] Bug#343555: alsa-source: fails to configure with bash 3.1 as /bin/sh

Processing commands for [EMAIL PROTECTED]: tags 343555 pending Bug#343555: alsa-source: fails to configure with bash 3.1 as /bin/sh There were no tags set. Tags added: pending stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator

Processed: merge

Processing commands for [EMAIL PROTECTED]: severity 343556 grave Bug#343556: alsa-source: upgrade to 1.0.10-2 fails Severity set to `grave'. merge 343556 343555 Bug#343555: alsa-source: fails to configure with bash 3.1 as /bin/sh Bug#343556: alsa-source: upgrade to 1.0.10-2 fails Merged 343555

Processed: merging 342223 343218

Processing commands for [EMAIL PROTECTED]: severity 342223 grave Bug#342223: Makefile.cpu is missing in experimental 2.6.15-rc4 header-packages Severity set to `grave'. merge 342223 343218 Bug#342223: Makefile.cpu is missing in experimental 2.6.15-rc4 header-packages Bug#343218: Headers are

Bug#343555: marked as done (alsa-source: fails to configure with bash 3.1 as /bin/sh)

Your message dated Fri, 16 Dec 2005 01:17:19 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#343555: fixed in alsa-driver 1.0.10-3 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#343556: marked as done (alsa-source: upgrade to 1.0.10-2 fails)

Your message dated Fri, 16 Dec 2005 01:17:19 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#343555: fixed in alsa-driver 1.0.10-3 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#343555: [Pkg-alsa-devel] Bug#343555: alsa-source: fails to configure with bash 3.1 as /bin/sh

tags 343555 pending stop Aaron M. Ucko wrote: Package: alsa-source Version: 1.0.10-2 Severity: grave Justification: renders package unusable alsa-source's config script fails on my system (which has bash 3.1-1 installed as /bin/sh); AFAICT, the problem is constructs such as

Processed: really merge 342223 343218 :)

Processing commands for [EMAIL PROTECTED]: reassign 343218 linux-headers-2.6.15-rc5 Bug#343218: Headers are useless because missing file /usr/src/linux-headers-2.6.15-rc5/arch/i386/Makefile.cpu Bug reassigned from package `linux-headers-2.6.15-rc5-686-smp' to `linux-headers-2.6.15-rc5'. tags

Bug#343555: [Pkg-alsa-devel] Bug#343555: alsa-source: fails to configure with bash 3.1 as /bin/sh

Please test 1.0.10-3 which is now in incoming http://incoming.debian.org or unstable. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#320548: libsdl-perl: broken dependency

Josselin Mouette a écrit : Le vendredi 16 décembre 2005 à 01:21 +0100, Tanguy Ortolo a écrit : Package: libsdl-perl Followup-For: Bug #320548 libsdl-perl needs libsdl-gfx1.2, that has been replaced by libsdl-gfx1.2-dev. What do you mean ? One is the shared library, the other is the

Bug#343556: works now

Hi, just installed 1.0.10-3 from incoming. Installation works now, thank you. Goodbyte, Gerd. -- The last thing one knows in constructing a work is what to put first. -- Blaise Pascal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble?

Bug#343583: kernel-source-2.4.27: kernel-source and kernel-image version out of sync for Sparc

Package: kernel-source-2.4.27 Version: 2.4.27-10sarge1 Severity: serious Justification: no longer builds from source -- System Information: Debian Release: 3.1 Architecture: sparc (sparc64) Kernel: Linux 2.4.27-2-sparc64 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Hello, When

Bug#339688: any ETA for this bug?

Hello, this bug is blocking some development. I have heard about troubles with user management in fuse-utils but this should not prevent other package upgrades. In my case it blocks the latest C++ transition. I plan to NMU fuse with the new version and maybe some obvious fixes before this year

Bug#343545: tetex-bin: config fails; updmap cannot find arabtex.map

severity 343545 important # not reassigning to arabtex for now because it's the tex maintainers' fault thanks Lionel Elie Mamane [EMAIL PROTECTED] wrote: Package: tetex-bin Version: 3.0-12 Severity: grave Justification: renders package unusable Dear Lionel, thanks for reporting that bug;

Processed: Re: Bug#343545: tetex-bin: config fails; updmap cannot find arabtex.map

Processing commands for [EMAIL PROTECTED]: severity 343545 important Bug#343545: tetex-bin: config fails; updmap cannot find arabtex.map Severity set to `important'. # not reassigning to arabtex for now because it's the tex maintainers' fault thanks Stopping processing here. Please contact

Bug#343443: linux-image-2.6.14-2-k7: initrd(yaird) doesn't contain HD modules

Package: linux-image-2.6.14-2-k7 Version: 2.6.14-5 Followup-For: Bug #343443 The default installation did not boot failing to found hard disk devices. Generating initrd with old mkinitrd generated a valid initrd image. With all the needed modules to boot my machine. I figure it out only by

Bug#323321: marked as done (FTBFS: Unable to define uoff_t)

Your message dated Fri, 16 Dec 2005 12:12:03 + with message-id [EMAIL PROTECTED] and subject line Fixed in 0.8.10-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 your responsibility to

Bug#343461: marked as done (geoip_1.3.14-1(unstable/arm/grieg): needs libtool update for arm)

Your message dated Fri, 16 Dec 2005 04:02:06 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#343461: fixed in geoip 1.3.14-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 your

Bug#318974: marked as done (libxbsql0: CXX 4.0 transition)

Your message dated Fri, 16 Dec 2005 04:32:08 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#318974: fixed in xbsql 0.11-5 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

Bug#343583: marked as done (kernel-source-2.4.27: kernel-source and kernel-image version out of sync for Sparc)

Your message dated Fri, 16 Dec 2005 04:36:10 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#343583: kernel-source-2.4.27: kernel-source and kernel-image version out of sync for Sparc has caused the attached Bug report to be marked as done. This means that you claim that the problem

Bug#335148: marked as done (removal of automake1.6)

Your message dated Fri, 16 Dec 2005 04:32:08 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#335148: fixed in xbsql 0.11-5 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

Bug#343599: ghemical: This package depends on libsc5 which is not exist in sarg e amd64

Package: ghemical Severity: grave Justification: renders package unusable -- System Information: Debian Release: 3.1 Architecture: amd64 (x86_64) Kernel: Linux 2.6.12.3 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of

Bug#343599: additional information

If possible, should be build against libsc6 which is available on sarge amd64. # apt-get install ghemical Reading Package Lists... Done Building Dependency Tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the

Bug#343599: ghemical: This package depends on libsc5 which is not exist in sarg e amd64

Hi, On Fri, Dec 16, 2005 at 02:19:14PM +0100, Gregoire Masliah wrote: Package: ghemical Severity: grave Justification: renders package unusable Which version of ghemical are you looking at? The .deb from http://amd64.debian.net/debian/pool/main/g/ghemical/ghemical_1.90-2_amd64.deb depends on

Bug#343599: (no subject)

Hi, the version of ghemical i've attempted to install is 1.01-2 thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#343606: libcatalyst-perl: missing build-dep on libtemplate-perl

Package: libcatalyst-perl Severity: serious Version: 5.61-1 Fails to build without Template available, it's in Makefile.PL... -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -- | signature.asc

Bug#343599: (no subject)

On Fri, Dec 16, 2005 at 02:53:19PM +0100, Gregoire Masliah wrote: the version of ghemical i've attempted to install is 1.01-2 I have requested a rebuild for the amd64 archive which should make ghemical installable on stable/amd64 again. thanks for the report, Michael -- Michael Banck Debian

Bug#343608: Core dump at start

Package: irssi Version: 0.8.10-1 Severity: grave [(status)] *** glibc detected *** double free or corruption (!prev): 0x08686118 *** zsh: 10273 abort (core dumped) irssi % gdb /usr/bin/irssi core-irssi-1134742770-6-10273 GNU gdb 6.3.90_20051119-debian Copyright 2004 Free Software

Bug#338309: ndiswrapper-source: oops in update_wireless_stats

Adrian, thanks for the patch. Works great. :-) Claudio, I retried the 1.5 with 2.16.11: no problem, so *it's* a kernel upgrade matter or, if you prefer, call it as an incompatibility between 1.5 sources and 2.6.14 kernel ;-) BTW, is there any reason to not have the latest (1.6 1.7) sources

Bug#336983: PATCH: Fix for qemu build on PowerPC

On Dec 15, 2005, at 9:17 PM, Josh Triplett wrote: Guillem Jover wrote: On Thu, Dec 15, 2005 at 07:45:23PM -0800, Daniel Gimpelevich wrote: If that release is imminent, there is something that I would like to take care of beforehand: I think I have found a bug that causes random garbage to

Bug#343611: Can not be installed

Package: tex4ht Version: 20050402.1817-1 Severity: grave I was trying to upgarde to version 20051130-1: -=*[ROOT ZSH]*=- [EMAIL PROTECTED]:/root # apt-get -f -u -t unstable install tex4ht Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This

Bug#343556: [Pkg-alsa-devel] Bug#343555: alsa-source: fails to configure with bash 3.1 as /bin/sh

This version fixes the problem. Thanks, -Ivan On Fri, Dec 16, 2005 at 11:23:55AM +0100, Thomas Hood wrote: Please test 1.0.10-3 which is now in incoming http://incoming.debian.org or unstable. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of

Bug#343612: libgc: FTBFS on arm platforms

Package: libgc Severity: serious Tags: patch Justification: no longer builds from source libgc 6.6 FTBFS on arm platforms using any current gcc/binutils combo, bailing out with an error of the following type: Error: Rn must not overlap other operands -- `swp r3,r5,[r3]' The ARM 'swp Rd,

Bug#341398: Please, post backtraces

Hi, If you get racoon to disapear, please run under gdb, add -F option (to stay in foreground) and post backtrace. -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#343608: Core dump at start

Can you run strace -o irssi.log irssi and send me irssi.log -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Processed: Re: Bug#343543: rageircd: user authentication can be bypassed by not providing a password

Processing commands for [EMAIL PROTECTED]: severity #343543 important Bug#343543: rageircd: user authentication can be bypassed by not providing a password Severity set to `important'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system

Processed: tagging 339343

Processing commands for [EMAIL PROTECTED]: tags 339343 pending Bug#339343: swish-e - FTBFS: Failed to find [swish-config] in PATH There were no tags set. Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system

Processed: tagging 343612

Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.10 tags 343612 upstream pending Bug#343612: libgc: FTBFS on arm platforms Tags were: patch Tags added: upstream, pending End of message, stopping processing here. Please contact me if

Bug#343612: marked as done (libgc: FTBFS on arm platforms)

Your message dated Fri, 16 Dec 2005 11:02:15 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#343612: fixed in libgc 1:6.6-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 your

Processed: merge

Processing commands for [EMAIL PROTECTED]: severity 340900 important Bug#340900: kronolith: saves but does not display events Severity set to `important'. severity 254981 important Bug#254981: kronolith: Events are not saved/displayed Severity set to `important'. tags 340900 + upstream

Bug#343250: [Bulk] Re: Bug#343250: upx-ucl-beta: broken on 64-bit systems

Robert Luberda wrote: Thanks for your report. I've just uploaded new CVS snapshot of upx-ucl-beta (1.94+0.20051214cvs-1). Could you please check if the problem still exists in that version? It fails to be build from sources on amd64 with the following error: g++ -O2 -g -DWITH_UCL -o

Bug#337870: FTBFS (alpha): conflicting types for 'strlen'

Attached please find two patches. patch-1.txt is minimal, just enough to make the build succeed. It modified fvwm/alpha_header.h so that it uses the proper (standardized!) headers instead of declaring things itself. This is, I hope, sufficient to fix the bug in question. patch-2.txt includes the

Processed: your mail

Processing commands for [EMAIL PROTECTED]: severity 341228 serious Bug#341228: mazeofgalious: patent infringement Severity set to `serious'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian

Bug#341228: Severity rising

Guerkan Senguen wrote: I have read them and I still disagree to you. Here is a short explaination, why I raised the severity again: * A patent applies even if you don't know of it. This means, one have to _first_ check all the patents, and _then_ upload/distribute a program. Otherwise, one can

Bug#343042: linux-image-2.6.14-2-686: Boot aborts with message, '/bin/cat: /sys/block/hda/hda1/dev: No such file or directory'

I can confirm, as others have mentioned, that this bug affects AMD systems as well. All of my symptoms were identical to others reported. I chose to downgrade yaird to testing and this resolved the problem (now running 2.6.14-5). I appears to me that the patch mentioned above doesn't apply

Bug#338930: gambas - FTBFS: creating symbolic link: Permission denied

The patch below allows the package to be built. A quick glance at it doesn't indicate any huge problems, but since I don't the package at all, I didn't test it. Hopefully this is helpful in gettinga fixed upload done anyway. Happy hacking. --- gambas-1.0.12/debian/rules 2005-12-16

Bug#341766: marked as done (firefox: FTBFS: Not using -fPIC to make shared lib.)

Your message dated Fri, 16 Dec 2005 14:17:16 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#341766: fixed in firefox 1.5.dfsg-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#343185: marked as done (firefox: Not available on powerpc.)

Your message dated Fri, 16 Dec 2005 14:17:16 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#341766: fixed in firefox 1.5.dfsg-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#337269: gatos: FTBFS: invalid lvalue in assignment

If I change src/i2c.c, line 398 to be like this: if (loop) (N1) ? (N2=N) : (N1 = N) ; if (N2) loop = 0 ; } Then the build continues, but fails later with this error: g++ -Wall -pipe -O -o .libs/xatitv xatitv.o xutils.o .libs/xatitvS.o ./.libs/libgatos.so -L/usr/lib /usr/lib/libibtk.so

Bug#341676: marked as done (liboctaviz.so not found)

Your message dated Fri, 16 Dec 2005 14:32:08 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#341676: fixed in octaviz 0.4.0-13 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#343109: boa-constructor: Fails to start

Hello, Can you start boa-constructor, and send me the full console output ? You should have something like: $ boa-constructor Starting Boa Constructor v0.3.0 importing wxPython reading user preferences Created directory: /home/op/.boa-constructor Created directory:

Processed: your mail

Processing commands for [EMAIL PROTECTED]: tags 343109 +unreproducible +sarge +moreinfo Unknown tag/s: +sarge, +moreinfo. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs

Bug#329758: marked as done (libbusiness-onlinepayment-perl: FTBFS: Missing Build-Depends on 'libtie-ixhash-perl, libnet-ssleay-perl, liburi-perl')

Your message dated Fri, 16 Dec 2005 15:17:08 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#329758: fixed in libbusiness-onlinepayment-perl 2.99devel3.00+03-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

Bug#335973: marked as done (FTBFS: Tests fail)

Your message dated Fri, 16 Dec 2005 15:17:10 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#335973: fixed in libjson-perl 1.00-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

Bug#343092: recovery ?

Would anyone be kind enough to provide recovery instructions for this issue, for current state and/or when the newer linux-image are available? Link to an appropriate man page qualify :) Thanks, Jean-Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe.

Bug#337269: gatos: FTBFS: invalid lvalue in assignment

If I knew, I would, but didn't find how to. I'm tempted to orphan the package, as it's for rather old video cards, and that there is a new gatos Christian Lars Wirzenius a écrit : If I change src/i2c.c, line 398 to be like this: if (loop) (N1) ? (N2=N) : (N1 = N) ; if (N2) loop = 0 ; }

Bug#341234: NMU diff

Attached is an NMU diff for these two grave bugs. I will be uploading the NMU to delayed/3days. diff -ruN ../orig/apt-move-4.2.24/Makefile apt-move-4.2.24/Makefile --- ../orig/apt-move-4.2.24/Makefile2003-02-22 10:56:27.0 + +++ apt-move-4.2.24/Makefile2005-12-17

Processed: Debian Kerberosish: r2292 - in cyrus-sasl2-mit: . debian/current debian/current/debian debian/current/debian/patches debian/current/p

Processing commands for [EMAIL PROTECTED]: tags 332703 pending Bug#332703: FTBFS: Syntax error before MD5_CTX Tags were: fixed patch Tags added: pending tags 285605 pending Bug#285605: cyrus-sasl2: FTBFS (amd64/gcc-4.0): static declaration of 'global_callbacks' follows non-static declaration

Processed: Debian Kerberosish: r2296 - in cyrus-sasl2-mit: . debian debian/current debian/current/cyrus-sasl2-mit debian/current/cyrus-sasl2-mit/debian debian/current/cyrus-sasl2-mit/debian/patches de

Processing commands for [EMAIL PROTECTED]: tags 332703 pending Bug#332703: FTBFS: Syntax error before MD5_CTX Tags were: pending fixed patch Tags added: pending tags 285605 pending Bug#285605: cyrus-sasl2: FTBFS (amd64/gcc-4.0): static declaration of 'global_callbacks' follows non-static

Bug#341228: Severity rising

On Fri, Dec 16, 2005 at 10:05:11PM +0100, Daniel Baumann wrote: Guerkan Senguen wrote: I have read them and I still disagree to you. Here is a short explaination, why I raised the severity again: * A patent applies even if you don't know of it. This means, one have to _first_ check all the

Bug#276865: marked as done (cyrus-sasl2-mit: Local privilege escalation on setuid environment (CAN-2004-0884))

Your message dated Fri, 16 Dec 2005 19:17:06 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#276865: fixed in cyrus-sasl2-mit 2.1.19-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

Bug#285613: marked as done (cyrus-sasl2-mit: FTBFS (amd64/gcc-4.0): static declaration of 'global_callbacks' follows non-static declaration)

Your message dated Fri, 16 Dec 2005 19:17:06 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#285613: fixed in cyrus-sasl2-mit 2.1.19-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

Bug#343611: Can not be installed

Dear Juhapekka, On Fri, 16 Dec 2005, Juhapekka Tolvanen wrote: Package: tex4ht Version: 20050402.1817-1 Severity: grave I was trying to upgarde to version 20051130-1: Sorry about the goof-up. Version 20051130 is indeed uninstallable and is superceded by 20051214 which should work fine

Bug#338100: marked as done (licq_1.3.2-4_m68k: FTBFS: /bin/moc: No such file or directory)

Your message dated Sat, 17 Dec 2005 04:32:37 +0100 with message-id [EMAIL PROTECTED] and subject line licq_1.3.2-4_m68k: FTBFS: /bin/moc: No such file or directory 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#340850: still fails

reopen 340850 found 340850 1.85-2 thanks sparc and some other buildds failed to build with this error. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Processed: Same problem

Processing commands for [EMAIL PROTECTED]: # Fixed in 20051214-1 close 343611 20051214-1 Bug#343611: Can not be installed 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 20051214-1, send any further explanations to Juhapekka Tolvanen

Processed: still fails

Processing commands for [EMAIL PROTECTED]: reopen 340850 Bug#340850: units: FTBFS: makeinfo: Command not found Bug reopened, originator not changed. found 340850 1.85-2 Bug#340850: units: FTBFS: makeinfo: Command not found Bug marked as found in version 1.85-2. thanks Stopping processing

Bug#343679: gloox: ftbfs [sparc] doxygen: Command not found

Package: gloox Severity: serious Justification: no longer builds from source gloox failed to build on a sparc buildd, duplicated on my sparc pbuilder. It also failed on all other buildds. touch build-arch-stamp dh_testdir doxygen make: doxygen: Command not found make: *** [build-indep-stamp]

Bug#337296: kitchensync crashes during the first run

On Thursday 03 November 2005 01:24 pm, Hervé Leroux wrote: Subject: kitchensync crashes during the first run Package: kitchensync Version: 4:3.4.2-2 Severity: grave Justification: renders package unusable When I run kitchensync for the first time (or after deleting

Processed: bug supposedly fixed in kmail from kde 3.4

Processing commands for [EMAIL PROTECTED]: close 329766 4:3.4.1-1 Bug#329766: kmail ignores send mail button 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 4:3.4.1-1, send any further explanations to Sven Bergner [EMAIL PROTECTED]

Bug#340850: still fails

Timestamp skew was a red herring. It's a missing build-depends. -- John Hasler [EMAIL PROTECTED] Elmwood, WI USA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#342887: util-linux: too early yet too late

Package: util-linux Version: 2.12r-2 Followup-For: Bug #34288 You could also make the argument that it runs too late--since it runs after checkroot, even after copying the symlinked localtime into /etc/, the root filesystem will still be checked every other boot. I'm not sure what exactly

Processed: Fixed in NMU of ettercap 1:0.7.1-1sarge1

Processing commands for [EMAIL PROTECTED]: tag 311615 + fixed Bug#311615: ettercap: [CAN-2005-1796] buffer overflow in ec_curses.c Tags were: fixed sarge patch security Tags added: fixed quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system

Processed: Fixed in NMU of backup-manager 0.5.7-1sarge1

Processing commands for [EMAIL PROTECTED]: tag 308897 + fixed Bug#308897: backup-manager: insecure default configuration Tags were: fixed sarge security patch Tags added: fixed tag 315582 + fixed Bug#315582: backup-manager: insecure handling of temporary files Tags were: fixed sarge security

Processed: Fixed in NMU of kazehakase 0.2.7-2.sarge1

Processing commands for [EMAIL PROTECTED]: tag 325124 + fixed Bug#325124: segfault visiting any site if no tab is open (e.g. upon startup) Tags were: fixed patch Tags added: fixed tag 326509 + fixed Bug#326509: Segfaults always when opening Kazehakase's website from the menu Tags were: fixed

Processed: Fixed in NMU of gtk+2.0 2.6.4-3.1

Processing commands for [EMAIL PROTECTED]: tag 339431 + fixed Bug#339431: CVE-2005-3186: Integer overflow in gdk-pixbuf's XPM code Tags were: fixed patch fixed-in-experimental security Tags added: fixed quit Stopping processing here. Please contact me if you need assistance. Debian bug

Bug#296609: marked as done (fam: can not unmount floppy)

Your message dated Fri, 16 Dec 2005 21:22:45 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#296609: fixed in fam 2.7.0-6sarge1 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#316579: marked as done (fam: compact flash card destroyed)

Your message dated Fri, 16 Dec 2005 21:22:45 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#316579: fixed in fam 2.7.0-6sarge1 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#323318: marked as done (Array element has incomplete type)

Your message dated Fri, 16 Dec 2005 21:30:23 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#320256: fixed in kernel-source-2.4.27 2.4.27-10sarge1 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

Bug#322591: marked as done (awstats: [CAN-2005-1527] arbitrary command injection)

Your message dated Fri, 16 Dec 2005 21:19:49 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#322591: fixed in awstats 6.4-1sarge1 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#322607: marked as done (SECURITY: HTTP proxy responses with both Transfer-Encoding and Content-Length headers (CAN-2005-2088))

Your message dated Fri, 16 Dec 2005 21:19:02 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#322607: fixed in apache 1.3.33-6sarge1 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#309308: marked as done (kernel-image-2.6.8-2-686-smp: null pointer oops on udp packets)

Your message dated Fri, 16 Dec 2005 21:30:24 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#309308: fixed in kernel-source-2.6.8 2.6.8-16sarge1 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

Bug#323318: marked as done (Array element has incomplete type)

Your message dated Fri, 16 Dec 2005 21:30:23 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#323318: fixed in kernel-source-2.4.27 2.4.27-10sarge1 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

Bug#338296: marked as done (common-lisp-controller 4.15sarge2 broke clisp+cl-asdf)

Your message dated Fri, 16 Dec 2005 21:20:42 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#338296: fixed in common-lisp-controller 4.15sarge3 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

Bug#311357: marked as done (kernel-image-2.6.8-2: via-rhine fails to reserve I/O region, no networking available)

Your message dated Fri, 16 Dec 2005 21:30:24 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#311357: fixed in kernel-source-2.6.8 2.6.8-16sarge1 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

Processed: severity of 343192 is wishlist

Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.9 severity 343192 wishlist Bug#343192: cupsys: infrastructure for dvi autodetection and printing missing. Severity set to `wishlist'. End of message, stopping processing here. Please

Processed: Fixed in NMU of f-prot-installer 0.5.14.sarge.1

Processing commands for [EMAIL PROTECTED]: tag 323930 + fixed Bug#323930: f-prot-installer: Script /usr/bin/f-prot doesn't work with f-prot 4.6.0 Tags were: fixed sarge Tags added: fixed quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system

Processed: Fixed in NMU of gdk-pixbuf 0.22.0-8.1

Processing commands for [EMAIL PROTECTED]: tag 339458 + fixed Bug#339458: CVE-2005-3186: Integer overflow in gdk-pixbuf's XPM code Tags were: fixed patch security Tags added: fixed quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system

Processed: Fixed in NMU of lm-sensors 1:2.9.1-1sarge2

Processing commands for [EMAIL PROTECTED]: tag 324193 + fixed Bug#324193: lm-sensors: Insecure tempfile usage in pwmconfig Tags were: etch patch security Tags added: fixed quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator

Processed: Fixed in NMU of mdadm 1.9.0-4sarge1

Processing commands for [EMAIL PROTECTED]: tag 299623 + fixed Bug#299623: mdadm: Fails to upgrade while udev installed Tags were: pending confirmed fixed sarge patch Tags added: fixed quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system

Processed: Fixed in NMU of mantis 0.19.2-4.1

Processing commands for [EMAIL PROTECTED]: tag 330682 + fixed Bug#330682: mantis: Several vulnerabilities in Mantis Tags were: fixed pending security Tags added: fixed tag 335938 + fixed Bug#335938: mantis: Mantis t_core_path File Inclusion Vulnerability Tags were: fixed pending security Tags

Processed: Fixed in NMU of polygen 1.0.6-7sarge1

Processing commands for [EMAIL PROTECTED]: tag 325468 + fixed Bug#325468: polygen: ignores umask Tags were: fixed security Tags added: fixed quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)

Bug#312106: marked as done (preconfiguration bug break woody to sarge upgrade)

Your message dated Fri, 16 Dec 2005 21:35:37 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#312106: fixed in nut 2.0.1-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 your

Bug#317739: marked as done (XSS in phpbb2 (MS IE only) [CAN-2005-2161])

Your message dated Fri, 16 Dec 2005 21:37:12 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#317739: fixed in phpbb2 2.0.13+1-6sarge1 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#318284: marked as done (CAN-2005-2256 directory traveral vulnerability)

Your message dated Fri, 16 Dec 2005 21:37:18 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#318284: fixed in phppgadmin 3.5.2-5 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#321974: marked as done (upgrade forces pdns-server to use pipe backend)

Your message dated Fri, 16 Dec 2005 21:36:09 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#321974: fixed in pdns 2.9.17-13sarge2 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

  1   2   >