Bug#396851: marked as done (FTBFS: Non-ascii '�' in input, consider using package inputenc)

Your message dated Fri, 03 Nov 2006 21:02:17 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#396851: fixed in ecasound2.2 2.4.4-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 no

Bug#396279: x11-common: sarge to etch upgrade fails if xlbiff is installed.

severity 395927 serious severity 396279 important thanks On Wed, Nov 01, 2006 at 08:29:29PM -0800, Steve Langasek wrote: > > The Sarge package xlbiff includes the file /usr/X11R6/bin/xlbiff > The xlbiff package in sarge is at version 4.1-1, and x11-common in etch > already has a conflicts: with

Processed: Re: Bug#396279: x11-common: sarge to etch upgrade fails if xlbiff is installed.

Processing commands for [EMAIL PROTECTED]: > severity 395927 serious Bug#395927: xlbiff: Causes upgrade of x11-common to fail with "trying to overwrite `/usr/X11R6/bin', which is also in package xlbiff" Severity set to `serious' from `normal' > severity 396279 important Bug#396279: x11-common: s

Bug#395278: marked as done (ttf-vlgothic: installation failure due to invalid characters)

Your message dated Fri, 03 Nov 2006 20:47:15 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#395278: fixed in ttf-vlgothic 20061026-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 i

Bug#394845: marked as done (davfs2_1.1.2-1(hppa/unstable): FTBFS: missing define)

Your message dated Fri, 03 Nov 2006 20:32:12 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#394845: fixed in davfs2 1.1.2-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 not the case it is now y

Processed: closing 385660

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.21 > # fixed but not done? sigh > close 385660 1.8.70-1 Bug#385660: bogofilter/qdbm build fails testsuite due to bus errors in vlopen 'close' is deprecated; see http://www.debian.org/Bugs/

Bug#395019: More details regarding disk numbering change

For people (like me) who've picked up this bug via rc-alert or apt-list-bugs and paniced.. The change is simply that partition numbers start at 1, not 0. See [1] As for the bug itself... I'd suggest a NEWS.Debian file entry that says that grub2 users must do an install-grub and update-grub cycle

Bug#396842: marked as done (util-linux: FTBFS (amd64): install: cannot stat `sys-utils/rdev': No such file or directory)

Your message dated Fri, 03 Nov 2006 20:02:28 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#396842: fixed in util-linux 2.12r-15 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 no

Bug#391167: marked as done (libnss-ldap: can't boot since 251-5.2 upgrade)

Your message dated Fri, 03 Nov 2006 18:47:30 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#375077: fixed in libnss-ldap 251-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#375077: marked as done (udevd: nss_ldap: failed to bind to LDAP server -> boot fails)

Your message dated Fri, 03 Nov 2006 18:47:30 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#375215: fixed in libnss-ldap 251-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#391167: marked as done (libnss-ldap: can't boot since 251-5.2 upgrade)

Your message dated Fri, 03 Nov 2006 18:47:30 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#375215: fixed in libnss-ldap 251-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#375077: marked as done (udevd: nss_ldap: failed to bind to LDAP server -> boot fails)

Your message dated Fri, 03 Nov 2006 18:47:30 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#375077: fixed in libnss-ldap 251-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#396836: gaim-encryption: Segfaults on loading

tags 396836 unreproducible -- Can you provide mor details regarding this segfault? Does it happen only on startup? Or anytime you load the plugin during gaim use? Could you try reseting your generetad keys to see if it persists? (Keep the old ones as backup, in case this proves helpful they can h

Bug#391167: marked as done (libnss-ldap: can't boot since 251-5.2 upgrade)

Your message dated Fri, 03 Nov 2006 18:47:30 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#391167: fixed in libnss-ldap 251-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#391053: marked as done (libnss-ldap: /lib/init/rw is not created on upgrade)

Your message dated Fri, 03 Nov 2006 18:47:30 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#390926: fixed in libnss-ldap 251-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#390926: marked as done (libnss-ldap needs a versioned dependency on initscripts)

Your message dated Fri, 03 Nov 2006 18:47:30 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#391053: fixed in libnss-ldap 251-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#391053: marked as done (libnss-ldap: /lib/init/rw is not created on upgrade)

Your message dated Fri, 03 Nov 2006 18:47:30 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#391053: fixed in libnss-ldap 251-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

Processed: gaim-encryption: Segfaults on loading

Processing commands for [EMAIL PROTECTED]: > tags 396836 unreproducible Bug#396836: Segfaults on loading There were no tags set. Tags added: unreproducible > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bu

Bug#390926: marked as done (libnss-ldap needs a versioned dependency on initscripts)

Your message dated Fri, 03 Nov 2006 18:47:30 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#390926: fixed in libnss-ldap 251-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#375215: marked as done (libnss-ldap hangs udev at startup)

Your message dated Fri, 03 Nov 2006 18:47:30 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#375077: fixed in libnss-ldap 251-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#375215: marked as done (libnss-ldap hangs udev at startup)

Your message dated Fri, 03 Nov 2006 18:47:30 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#375215: fixed in libnss-ldap 251-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#375077: marked as done (udevd: nss_ldap: failed to bind to LDAP server -> boot fails)

Your message dated Fri, 03 Nov 2006 18:47:30 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#391167: fixed in libnss-ldap 251-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#375215: marked as done (libnss-ldap hangs udev at startup)

Your message dated Fri, 03 Nov 2006 18:47:30 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#391167: fixed in libnss-ldap 251-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#377895: marked as done (libnss-ldap: Problem with "-" in LDAP Base DN)

Your message dated Fri, 03 Nov 2006 18:47:30 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#377895: fixed in libnss-ldap 251-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#311188: debian-edu-config release critical bug

Hi Steffen, On Fri, Nov 03, 2006 at 09:32:21PM +1100, Steffen Joeris wrote: > I know that this is an old and long discussed bug, but please allow me to > raise the discussion again right now as I think that the issue is not > completely clear. > First of all the bug is called: "debian-edu-confi

Bug#396980: mlton_20061026-1 (hppa/unstable): FTBFS: regression in supported archs?

Package: mlton Version: 20061026-1 Severity: serious Hi Stephen, The fix for bug #394981 isn't propagating to testing, because the new version of mlton now fails to build on all architectures except for i386, not all with the same error. Since Packages-arch-specific already lists mlton as being

Bug#378346: libgail crashes on alpha

On Mon, Oct 16, 2006 at 04:42:30PM +0200, Loïc Minier wrote: > On Thu, Jul 20, 2006, Steve Langasek wrote: > > > At the very least, I would appreciate it if you could verify whether > > > the bug is reproducible or not. > > > See bug #378346 for the bug report. > > Here is the error that triggers

Bug#396973: marked as done (gdb: can not debug any program linked with pthread.)

Your message dated Fri, 03 Nov 2006 20:53:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line (No subject header) 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

Bug#396973: gdb: can not debug any program linked with pthread.

On Fri, Nov 03, 2006 at 08:05:32PM -0500, Nick Lewycky wrote: > Attached. Here's the exact session I ran: > ptrace(0x19 /* PTRACE_??? */, 29003, 0xc, 0xff888354) = -1 EINVAL (Invalid > argument) > >>Architecture: i386 (x86_64) > >>Shell: /bin/sh linked to /bin/bash > >>Kernel: Linux 2.6.18.1 >

Bug#375518: marked as done (cenon.app: Critical error executing Cenon)

Your message dated Fri, 03 Nov 2006 17:18:12 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#375518: fixed in cenon.app 3.81-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 y

Bug#396973: gdb: can not debug any program linked with pthread.

Daniel Jacobowitz wrote: > On Fri, Nov 03, 2006 at 08:05:32PM -0500, Nick Lewycky wrote: > >>Attached. Here's the exact session I ran: > >>ptrace(0x19 /* PTRACE_??? */, 29003, 0xc, 0xff888354) = -1 EINVAL (Invalid >>argument) > Architecture: i386 (x86_64) Shell: /bin/sh linked to /bin/

Bug#392776: MBR still useful

Just a quick note, I noticed this bug using rc-alert. mbr is still useful, at least in one specific case, which is when using grub and a Highpoint HPT366 or 370 device (and possible later devices) Basically, these IDE/RAID controllers use a sector on the disk which is also one of the sectors grub

Bug#396973: gdb: can not debug any program linked with pthread.

On Fri, Nov 03, 2006 at 07:29:59PM -0500, Nick Lewycky wrote: > Severity: grave > Justification: renders package unusable Obviously not for everyone; it passes the testsuite during package build. I can only assume that either your C library or kernel has somehow gotten broken. Could you run "str

Processed: Patch for ktorrent FTBFS (#395897)

Processing commands for [EMAIL PROTECTED]: > tags 395897 patch fixed-upstream Bug#395897: FTBFS: now: No such file or directory There were no tags set. Tags added: patch, fixed-upstream > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system adminis

Bug#395897: Patch for ktorrent FTBFS (#395897)

tags 395897 patch fixed-upstream stop Upstream removed the LDFLAGS in revision 594434 [1]. This patch removes all three instances of LDFLAGS from the source, equivalent to the upstream change. It fixed FTBFS on my powerpc machine and passed "program starts OK" testing. [1] Upstream revision 5944

Processed: [bugzilla #395094] bug only affects sarge now

Processing commands for [EMAIL PROTECTED]: > tags 395094 + sarge Bug#395094: CVE-2006-545[3-5]: Multiple security issues in bugzilla Tags were: confirmed security Tags added: sarge > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administra

Bug#396973: gdb: can not debug any program linked with pthread.

Package: gdb Version: 6.4.90.dfsg-1 Severity: grave Justification: renders package unusable Any program linked with "-lpthread" will make GDB unusable with the following error: Cannot find user-level thread for LWP 28988: generic error Here's an example: $ cat simple.c int main(void) {

Bug#395094: [bugzilla #395094] bug only affects sarge now

tags 395094 + sarge thanks I've just uploaded bugzilla 2.22.1 to sid, urgency set to high. That bug is now closed in sid. We can focus on the sarge patches now. -- Alexis Sukrieh <[EMAIL PROTECTED]> 0x1EE5DD34 Debian http://www.debian.org Ba

Bug#396702: marked as done (ikiwiki: FTBFS: Missing Build-Depends on 'perlmagick')

Your message dated Fri, 03 Nov 2006 15:47:28 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#396702: fixed in ikiwiki 1.32 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#380056: marked as done (python-tunepimp: missing library dependency)

Your message dated Fri, 03 Nov 2006 15:47:51 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#380056: fixed in libtunepimp 0.4.2-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 no

Bug#378091: marked as done (libtunepimp: buffer overflow)

Your message dated Fri, 03 Nov 2006 15:47:51 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#378091: fixed in libtunepimp 0.4.2-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 no

Bug#393149: marked as done (uae: cannot open display)

Your message dated Fri, 03 Nov 2006 15:49:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#393149: fixed in uae 0.8.25-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#395094: CVE-2006-545[3-5]: Multiple security issues in bugzilla

tags 395094 + confirmed thanks * Ben Hutchings ([EMAIL PROTECTED]) : > Upstream security advisory: http://www.bugzilla.org/security/2.18.5/ > > These are fixed in 2.22.1 which would be suitable for sid. I'm working on the packaging of that new upstream release. -- Alexis Sukrieh <[EMAIL PROTE

Bug#394626: closed by Steve Langasek <[EMAIL PROTECTED]> (Bug#394626: fixed in qdbm 1.8.70-1.1)

On Fri, Nov 03, 2006 at 03:03:36PM -0800, Steve Langasek wrote: > Sorry, it didn't occur to me that you would feel strongly about being > credited here. This doesn't mean that I don't appreciate your work, it just > means (in my case) that I didn't use your patch directly, but re-derived it > afte

Bug#391780: mell: fails to install

On October 12, 2006 at 10:42PM +0900, tats (at debian.org) wrote: > tags 391780 patch > thanks > > On October 11, 2006 at 11:21PM +0200, > allomber (at math.u-bordeaux.fr) wrote: [...] > > > > It was recorded today. > > The log seems that this bug

Processed: Re: Bug#395094: CVE-2006-545[3-5]: Multiple security issues in bugzilla

Processing commands for [EMAIL PROTECTED]: > tags 395094 + confirmed Bug#395094: CVE-2006-545[3-5]: Multiple security issues in bugzilla Tags were: security Tags added: confirmed > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrato

Bug#395094: CVE-2006-545[3-5]: Multiple security issues in bugzilla

* Ben Hutchings ([EMAIL PROTECTED]) : > Based on the advisory at http://www.bugzilla.org/security/2.18.5/ I > would say that: [...] Ben, thanks a lot for your work regarding that issue. If you have an alioth account, feel free to ask Sean Finney to add you to the webapps-common team, so you can co

Bug#395252: embedded code copies are not RC

On Fri, Nov 03, 2006 at 11:34:37PM +0100, Diego Biurrun wrote: > That benchmark was done on x86. But let's face it, it's the > architecture that counts. Mind that I am writing this from a PPC, which > is my main machine.. I disagree, amd64 would be the architecture which counts and amd64 has eno

Bug#394626: closed by Steve Langasek <[EMAIL PROTECTED]> (Bug#394626: fixed in qdbm 1.8.70-1.1)

On Fri, Nov 03, 2006 at 11:07:18AM +0100, Aurélien GÉRÔME wrote: > On Fri, Nov 03, 2006 at 12:49:35AM -0800, Debian Bug Tracking System wrote: > >* Use -O0 in CXXFLAGS in plus/Makefile.in instead of -O1, to avoid an > > ICE when building on alpha. Closes: #394626. > I thought people were

Bug#393149: uae: cannot open display

On Fri, Nov 03, 2006 at 10:18:59PM +0100, Stephan A Suerken wrote: > > pwd_optionsfile is declared as char*, then used via strcpy() without > > initialization. And conveniently, this is in the code related to retrieving > > $HOME from the environment. Looks like a broken Debian patch to me. > Ar

Bug#311188: debian-edu-config release critical bug

> What do you think? *I* do think that, if that bug is RC for debian-edu-config, then another one should be opened for localization-config, which does exactly the same (actually not in very good shape for etch as it basically does nothing). BTW, localization-config is maintained as part of debi

Processed: Foo

Processing commands for [EMAIL PROTECTED]: > found 396964 2.8.5-2sarge2.1 Bug#396964: lynx: uses .mime.types and .mailcap from the current directory (arbitrary shell code execution) Bug marked as found in version 2.8.5-2sarge2.1. > thanks Stopping processing here. Please contact me if you need

Processed: Re: /sbin/dmraid depends on /usr/lib/libz.so.1

Processing commands for [EMAIL PROTECTED]: > tags 396762 patch Bug#396762: /sbin/dmraid depends on /usr/lib/libz.so.1 There were no tags set. Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, D

Bug#395252: embedded code copies are not RC

On Tue, Oct 31, 2006 at 10:43:17PM +0100, Aurélien GÉRÔME wrote: > > On Tue, Oct 31, 2006 at 07:46:01PM +0100, Diego Biurrun wrote: > > Removing the embedded copies of FFmpeg libraries from MPlayer is a bad > > idea. > > For the workload on the security team and the overall quality of Debian > (a

Bug#396762: /sbin/dmraid depends on /usr/lib/libz.so.1

tags 396762 patch thanks FWIW, here's a patch to only link zlib statically to dmraid while linking dynamically to the other libs. Since crc32 is the only function used from zlib, the size difference is minimal. On i386, here's the before: $ du -sh debian/dmraid/sbin/dmraid 160Kdebian/dmrai

Bug#396880: dblatex: error in file dblatex/xsl/docbook.xsl

On Fri, 03 Nov 2006 13:55:36 PST Steve Langasek wrote: >Hi Andreas, > >On Fri, Nov 03, 2006 at 08:02:24PM +0100, Andreas Hoenen wrote: >> I'm currently working at high pressure on a debian release of dblatex >> 0.2 with this bug fix included. I hope to get someone to sponsor the >> new release qui

Processed: Foo

Processing commands for [EMAIL PROTECTED]: > clone 396949 -1 Bug#396949: lynx: uses .mime.types and .mailcap from the current directory (arbitrary shell code execution) Bug 396949 cloned as bug 396964. > reassign -1 lynx Bug#396964: lynx: uses .mime.types and .mailcap from the current directory

Processed: subversion Debian ci: r745 - trunk/debian

Processing commands for [EMAIL PROTECTED]: > tags 393414 pending Bug#393414: Source package contains non-free IETF RFC/I-D's Tags were: etch-ignore pending Tags added: pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Bug#395493: Can't send messages to list

(I am not subscribed to mailman-users; please CC me on replies. Please also keep the Debian bug entry in the CC list if appropriate.) (I'm one of the maintainers of the Mailman package in Debian, the OS - slash - "GNU/Linux distribution" that Lukasz is using.) Mark Sapiro wrote: >Lukasz Szybal

Bug#395094: CVE-2006-545[3-5]: Multiple security issues in bugzilla

Upstream security advisory: http://www.bugzilla.org/security/2.18.5/ These are fixed in 2.22.1 which would be suitable for sid. There is no upstream fix for the 2.16 series, as used in sarge. I am looking at the upstream fix for the 2.18 series to see whether it is applicable or easily adaptable

Bug#396880: dblatex: error in file dblatex/xsl/docbook.xsl

Hi Andreas, On Fri, Nov 03, 2006 at 08:02:24PM +0100, Andreas Hoenen wrote: > I'm currently working at high pressure on a debian release of dblatex > 0.2 with this bug fix included. I hope to get someone to sponsor the > new release quickly, thus hopefully this problem should be out of the > worl

Bug#396880: dblatex: error in file dblatex/xsl/docbook.xsl

On Fri, 03 Nov 2006 20:33:02 +0100 Sebastien Blondeel wrote: >On Fri, Nov 03, 2006 at 08:05:29PM +0100, Frank K=FCster wrote: >> Can you please provide an example document that shows this problem? >> Ideally a minimized one. > >I now have a better understanding of the problem. > >This works: >-=3D-

Bug#396961: binutils-h8300-hms: all symlinks point to /build/buildd/binutils-h8300-hms-2.16.1/debian/binutils-h8300-hms

Package: binutils-h8300-hms Version: 2.16.1-1 Severity: grave All is said in the subject. For example: /usr/h8300-hitachi-coff/bin/ld -> /build/buildd/binutils-h8300-hms-2.16.1/debian/binutils-h8300-hms/usr/bin/h8300-hitachi-coff-ld -- System Information: Debian Release: 4.0 APT prefers unst

Processed (with 1 errors): serious

Processing commands for [EMAIL PROTECTED]: > severity 389267 serious Bug#389267: CVE-2006-4294: Directory traversal vulnerability in TWiki Severity set to `serious' from `important' > thanks! Unknown command or malformed arguments to command. > -- Stopping processing here. Please contact me if

Bug#367973: Twiki - about to miss a release?

Amaya wrote: > I am looking at your last package. I am thinking of uploading it as it > closes several RC and security bugs. Can I add some patches here and > there (i10 mostly) so that Twiki releases with etch in good shape? I find your package fine, but i has several lintian warnings: ~/debian/1

Bug#367973: Twiki - about to miss a release?

Sven Dowideit wrote: > true, I don't do much, other than update the debian package at http:// > members.iinet.net.au/~spos once a month or two, and send it off to my > sponsor. May I ask who is your sponsor? Would you accept me as a backup sponsor? > As a TWiki developer, rather than a debian dev

Bug#396931: marked as done (http://people.debian.org/~joeyh/d-i/images/daily/hd-media/boot.img.gz makes usb-stick unusable)

Your message dated Fri, 3 Nov 2006 15:53:34 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#396931: http://people.debian.org/~joeyh/d-i/images/daily/hd-media/boot.img.gz makes usb-stick unusable has caused the attached Bug report to be marked as done. This means that you claim tha

Bug#396949: lynx: uses .mime.types and .mailcap from the current directory (arbitrary shell code execution)

Package: lynx-cur Version: 2.8.7dev1-1 Severity: grave Tags: security Justification: user security hole Lynx attempts to use the .mime.types and .mailcap files located in the current directory: $ strace lynx -dump 2>&1 | grep '^open("[^/]' open(".mailcap", O_RDONLY) = -1 ENOENT (No

Bug#393595: Not fixed

On Fri, Nov 03, 2006 at 01:49:42PM +0100, Carl =?UTF-8?Q?F=C3=BCrstenberg ?= wrote: > This bug is as per today, not fixed: Yes it is. > The following packages have unmet dependencies: > libapache2-mod-php5.1: Depends: apache2-common (>= 2.0.55-4) but it > is not installable That's not a Debian

Bug#395181: missing dependency on libdevmapper1.01

On Thu, 02 Nov 2006, Roland Stigge wrote: > Hi, > > you can either do this: > > === > diff -ruN initrd-tools-0.1.84.1.orig/mkinitrd initrd-tools-0.1.84.1/mkinitrd > --- initrd-tools-0.1.84.1.orig/mkinitrd 2006-04-24 01:08:14.000

Bug#395493: mailman: smtp-failure:timeout, bad file descriptor, set_debuglevel

Lionel Elie Mamane wrote: > I don't know. Mark Sapiro claims that smtplib debug info goes to > stderr, but it goes to stdout. Maybe this explains it. My mistake. In Python 2.4, smtplib.py debug output does go to stderr, but in Python 2.3 it goes to stdout. -- Mark Sapiro <[EMAIL PROTECTED]>

Bug#393149: uae: cannot open display

Steve Langasek <[EMAIL PROTECTED]> (Sat Oct 28 02:44:48 2006): > Let's go to the source instead. The following error appears in the build > log on i386: > > gcc-4.0 -I. -I../src/include/ -c -O2 -fomit-frame-pointer -Wall -Wno-unused > -Wno-format -W -Wmissing-prototypes -Wstrict-prototypes >

Bug#396862: libgtk-mozembed-ruby: FTBFS: checking for xulrunner-gtkmozembed... Ruby/GTK couldn't be initialized ('Cannot open display: ')

On Fri, Nov 03, 2006 at 12:30:59PM +, Dafydd Harries wrote: > Ar 03/11/2006 am 13:08, ysgrifennodd Andreas Jochens: > > Package: libgtk-mozembed-ruby > > Version: 0.3.1-6 > > Severity: serious > > When building 'libgtk-mozembed-ruby' in a clean unstable chroot, > > I get the following error:

Processed: reassign 396932 to ieee80211-source

Processing commands for [EMAIL PROTECTED]: > reassign 396932 ieee80211-source Bug#396932: module-assistant: Cannot build ieee80211 module Bug reassigned from package `module-assistant' to `ieee80211-source'. > End of message, stopping processing here. Please contact me if you need assistance. D

Bug#367973: Twiki - about to miss a release?

true, I don't do much, other than update the debian package at http:// members.iinet.net.au/~spos once a month or two, and send it off to my sponsor. As a TWiki developer, rather than a debian developer, I don't feel supported by you guys, just attacked, but none the less, I maintain what

Bug#396880: dblatex: error in file dblatex/xsl/docbook.xsl

On Fri, Nov 03, 2006 at 08:05:29PM +0100, Frank Küster wrote: > Can you please provide an example document that shows this problem? > Ideally a minimized one. I now have a better understanding of the problem. This works: -=-=-= http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd";> Welcome to

Bug#395382: giflib3g: Vulnerable to CVE-2005-2974 and CVE-2005-3350

Kevin B. McCarty wrote: > I noticed that it's non-trivial to install the libgif4 .deb at the > moment. It conflicts with libungif4g since the latter ships symlinks of > libgif.so.4 and libgif.so.4.1.4, and just about everything using > libungif.so.4 has a versioned dependency so the Provides doesn

Bug#396931: http://people.debian.org/~joeyh/d-i/images/daily/hd-media/boot.img.gz makes usb-stick unusable

Package: installation-report Version: 02-Nov-2006 16:06 15.0M Severity: grave Justification: renders package unusable I downloaded the usb-image from http://people.debian.org/~joeyh/d-i/images/daily/hd-media/ ie. the file boot.img.gz 02-Nov-2006 16:06 15.0M Before continuing I g

Bug#396932: module-assistant: Cannot build ieee80211 module

Package: module-assistantVersion: 0.10.7Severity: graveJustification: renders package unusable*** Please type your report below this line ***Cannot build ieee80211 module, this makes impossible to use the bcm43xx module for wifi cards.dh_gencontrol: command returned error code 65280- -- System Info

Bug#395493: [Pkg-mailman-hackers] Bug#395493: mailman: smtp-failure:timeout, bad file descriptor, set_debuglevel

I replaced these files and everything works again. I'll give it 24h and put the old files back and see if mailman works again.. Thank you very much. Lukasz for the record... Lukasz Szybalski wrote: /var/lib/mailman/Mailman/Handlers/SMTPDirect.py >That is the file i patched SMTPDirect.py > >

Bug#396880: dblatex: error in file dblatex/xsl/docbook.xsl

You're right, unfortunately dblatex has a problem that has been ignored by xsltproc before release 1.1.18-1. The problem has been discussed yesterday/today in the mailing list dblatex-devel [1] (although the mail thread does not seem to have hit the list archive yet), resulting in the following si

Bug#396880: dblatex: error in file dblatex/xsl/docbook.xsl

Sebastien Blondeel <[EMAIL PROTECTED]> wrote: > Subject: error in file dblatex/xsl/docbook.xsl > Package: dblatex > Version: 0.1.10-1 > Severity: grave > Justification: renders package unusable > > *** Please type your report below this line *** > > I am running Debian testing. > > Since I updated

Bug#395382: giflib3g: Vulnerable to CVE-2005-2974 and CVE-2005-3350

Daniel Baumann wrote: > giflib 4.x uploaded, replacing giflib 3.x. > Due to changed binary names, the package has to go through NEW. > > For the impatients, the package is also available at > http://archive.daniel-baumann.ch/debian/packages/giflib/ Hi Daniel, Do you plan to add dpatch patches 02

Bug#396875: emacs21-common: Must include a copy of the GFDL

On 2006-11-03 Sven Joachim <[EMAIL PROTECTED]> wrote: > Package: emacs21-common > Version: 21.4a+1-1 > Severity: serious > > The manpages for Emacs and Etags have the following license: > > Permission is granted to copy, distribute and/or modify this document > under the terms of the GNU Free D

Bug#396747: marked as forwarded (FTBFS (alpha): attempt to use output operater '<<' on va_list)

Your message dated Fri, 3 Nov 2006 18:17:36 + with message-id <[EMAIL PROTECTED]> has caused the Debian Bug report #396747, regarding FTBFS (alpha): attempt to use output operater '<<' on va_list to be marked as having been forwarded to the upstream software author(s) [EMAIL PROTECTED] (NB: If

Bug#391778: marked as done (xemacs21-mule: postinst fails if xemacs21-support is not yet configured)

Your message dated Fri, 03 Nov 2006 10:02:52 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#391778: fixed in xemacs21 21.4.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 is now

Bug#393049: Debian Etch freeze... pkg-kde-extras implications

Hi pkg-kde-extras, As you might of seen on debian-devel-announce, http://lists.debian.org/debian-devel-announce/2006/11/msg0.html. The freeze for etch has been put back a little, it was scheduled for 18 Oct, leading to a release of Etch on 4 Dec. What does this mean for pkg-kde-extras, wel

Bug#367973: Twiki - about to miss a release?

Hi. For what it's worth, I'd like to suggest some of you to have a look at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354759 in which I added a pointer to an unofficial package, which I think was made by the maintainer... IMHO, it's not obvious from what appears in bugs.debian.org that TWik

Bug#396903: marked as done (kpowersave: FTBFS: *** YOU'RE USING Autoconf version 2.13. *** KDE requires autoconf 2.53 or newer)

Your message dated Fri, 3 Nov 2006 18:42:41 +0100 with message-id <[EMAIL PROTECTED]> and subject line kpowersave,knetworkmanager: FTBFS:*** KDE requires autoconf 2.53 or newer has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with.

Bug#396911: marked as done (knetworkmanager: FTBFS: *** AUTOCONF NOT FOUND!. *** KDE requires autoconf 2.53 or newer)

Your message dated Fri, 3 Nov 2006 18:42:41 +0100 with message-id <[EMAIL PROTECTED]> and subject line kpowersave,knetworkmanager: FTBFS:*** KDE requires autoconf 2.53 or newer has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with.

Bug#367973: Twiki - about to miss a release?

Hi all, I am talking with my MIA-QA-hat on. Antony Gelberg wrote: > I haven't cc'd the bug 367973 that this comes from - Steve if you want > the background please see > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367973 and > http://bugs.debian.org/twiki. Heh, I think you have :) > Sven Do

Bug#396922: FTBFS: Missing Build Dependency on libgmp3-dev

Package: guile-1.8 Version: 1.8.1+1-1 Severity: serious Hi, guile-1.8 is failing to build during configure stage with this error: checking for __gmpz_init in -lgmp... no configure: error: GNU MP not found, see README make: *** [debian/stamp/config] Error 1 debuild: fatal error at line 1224: deb

Bug#367973: Twiki - about to miss a release?

I haven't cc'd the bug 367973 that this comes from - Steve if you want the background please see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367973 and http://bugs.debian.org/twiki. Sven Dowideit: its stuff like this that just keeps depressing me into not finishing the work i do packagin

Bug#395860: still here in 0.19-2

On Friday 03 November 2006 16:09, Florent Bayle took the opportunity to say: > It seems that this problem is still here in 0.19-2 : > > Automatic build of libmail-dkim-perl_0.19-2 on saturne by sbuild/amd64 85 > > Build started at 20061102-2213 > > **

Bug#396762: [Utnubu-maintainers] Bug#396762: /sbin/dmraid depends on /usr/lib/libz.so.1

CRC implementation in some lines of C: http://www.w3.org/TR/PNG/#D-CRCAppendix -- Loïc Minier <[EMAIL PROTECTED]>

Bug#396874: marked as done (gramps: FTBFS: Missing Build-Depends on 'gnome-doc-utils, libxml-parser-perl')

Your message dated Fri, 03 Nov 2006 08:32:26 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#396874: fixed in gramps 2.2.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 you

Bug#282147: #282147: update-inetd broken by user interaction

Frans Pop wrote: > Not sure why your previous version did not work, but I doubt it makes very > much sense to investigate that. > Hmm. I seem to remember that I _have_ seen something like this before (not > completely sure though): I had a privately built package installed before > a new version

Bug#396911: knetworkmanager: FTBFS: *** AUTOCONF NOT FOUND!. *** KDE requires autoconf 2.53 or newer

Package: knetworkmanager Version: 1:0.1-2 Severity: serious Justification: no longer builds from source Hello, There was a problem while autobuilding your package: > Automatic build of knetworkmanager_1:0.1-2 on saturne by sbuild/amd64 85 > Build started at 20061101-1355 > **

Bug#396903: kpowersave: FTBFS: *** YOU'RE USING Autoconf version 2.13. *** KDE requires autoconf 2.53 or newer

tags 396903 moreinfo unreproducible thanks Florent Bayle wrote: > Package: kpowersave > Version: 0.6.2-3 > Severity: serious > Justification: no longer builds from source > > Hello, > > There was a problem while autobuilding your package: > >> Automatic build of kpowersave_0.6.2-3 on saturne by

Processed: Re: Bug#396903: kpowersave: FTBFS: *** YOU'RE USING Autoconf version 2.13. *** KDE requires autoconf 2.53 or newer

Processing commands for [EMAIL PROTECTED]: > tags 396903 moreinfo unreproducible Bug#396903: kpowersave: FTBFS: *** YOU'RE USING Autoconf version 2.13. *** KDE requires autoconf 2.53 or newer There were no tags set. Tags added: moreinfo, unreproducible > thanks Stopping processing here. Please

  1   2   >