Bug#326467: marked as done (lxr: lxr binary is installed inside /var/lib/lxr/bin instead of /usr/bin)

Your message dated Thu, 23 Feb 2006 23:17:06 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#326467: fixed in lxr-cvs 0.9.4-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#353395: marked as done (bridge-utils: Uninstallable on i386 because libsysfs2 is not installable)

Your message dated Fri, 24 Feb 2006 01:30:35 -0500 with message-id <[EMAIL PROTECTED]> and subject line 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 to reopen the

Bug#352243: marked as done (Uninstallable on i386/FTBFS elsewhere: depends on experimental libsysfs)

Your message dated Fri, 24 Feb 2006 01:30:35 -0500 with message-id <[EMAIL PROTECTED]> and subject line 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 to reopen the

Processed: Fixed in NMU of x11proto-damage 1.0.3-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed fixed-in-experimental Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in NMU of x11proto-dmx 2.2.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed fixed-in-experimental Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in NMU of x11proto-xf86bigfont 1.1.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed fixed-in-experimental Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in NMU of x11proto-xf86vidmode 2.2.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed fixed-in-experimental Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in NMU of x11proto-xf86dri 2.0.3-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed fixed-in-experimental Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in NMU of x11proto-fontcache 0.1.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed fixed-in-experimental Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in NMU of x11proto-composite 0.2.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed fixed-in-experimental Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in NMU of x11proto-video 2.2.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed fixed-in-experimental Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in NMU of x11proto-kb 1.0.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed fixed-in-experimental Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in NMU of x11proto-xf86misc 0.9.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed fixed-in-experimental Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in NMU of x11proto-evie 1:1.0.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian

Processed: Fixed in NMU of x11proto-render 2:0.9.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian

Processed: Fixed in NMU of x11proto-xf86dga 2.0.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed fixed-in-experimental Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in NMU of x11proto-input 1.3.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed fixed-in-experimental Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in NMU of x11proto-randr 1.1.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed fixed-in-experimental Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in NMU of x11proto-resource 1.0.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed fixed-in-experimental Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in NMU of x11proto-trap 3.4.3-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed fixed-in-experimental Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in NMU of x11proto-xext 7.0.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed fixed-in-experimental Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in NMU of x11proto-scrnsaver 1.0.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed fixed-in-experimental Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in NMU of x11proto-fonts 2.0.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed fixed-in-experimental Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in NMU of x11proto-xcmisc 1.1.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed-in-experimental fixed Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (

Processed: Fixed in upload of x11proto-gl 1.4.3-2 to experimental

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed-in-experimental Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed Tags added: fixed-in-experimental > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system admin

Processed: Fixed in NMU of x11proto-fixes 3.0.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian

Processed: Fixed in NMU of x11proto-record 1.13.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian

Processed: Fixed in NMU of x11proto-xinerama 1.1.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet Tags were: fixed Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian

Processed: Fixed in NMU of x11proto-bigreqs 1.0.2-2

Processing commands for [EMAIL PROTECTED]: > tag 351779 + fixed Bug#351779: x.org r6 and r7 don't play nice together yet There were no tags set. Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator,

Processed: Patch

Processing commands for [EMAIL PROTECTED]: > tag 352408 patch Bug#352408: cddb.bundle: FTBFS due to unmet build-dep libgnustep-base1.10-dev There were no tags set. Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administr

Bug#352408: Patch

tag 352408 patch thanks The attached patch makes the cddb.bundle source package build-depend on libgnustep-base1.11-dev instead of libgnustep-base1.10-dev and the binary package depend on libgnustep-base1.11 instead of libgnustep-base1.10. -- Matt diff -ru cddb.bundle-0.2-orig/debian/control cdd

Bug#211765: Are you ready for the summer?

Morning 211765, According to the BBC, am Eric an are seriously packing on the pds. do u fit this cat egory. If so, look at www.rwews.org/n2/. In Gaza, an Israeli airstrike before dawn killed three members of the Aksa Martyrs Brigades and wounded five, the Israelis said. The militant faction is p

Bug#354180: sylpheed-claws-gtk2: segfaults

Package: sylpheed-claws-gtk2 Version: 2.0.0-1 Severity: grave Justification: renders package unusable -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-

Bug#354105: marked as done (/etc/init.d/xprint sets "ulimit -n 1024")

Your message dated Thu, 23 Feb 2006 15:26:49 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#354105: /etc/init.d/xprint sets "ulimit -n 1024" 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 c

Processed: Re: Processed: Hmm... bug not merged

Processing commands for [EMAIL PROTECTED]: > block 272122 by 354120 Bug#272122: Broken KRGB 1.0 patch hoses IJS 1-bit monochrome printing Was blocked by: 267480 294430 303415 309847 354119 Blocking bugs added: 354120 > merge 354120 354119 Bug#354119: gs-esp: Some graphics in PDFs are printed as b

Processed: Hmm... bug not merged

Processing commands for [EMAIL PROTECTED]: > close 354120 Bug#354120: hpijs: Some graphics in PDFs are printed as black boxes 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to [EMAIL PROTECTED] > merge 354120 354119 Bug#354119: g

Processed: retitle 294430 to KRGB support in gs-gpl needs to be updated

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.15 > retitle 294430 KRGB support in gs-gpl needs to be updated Bug#294430: gs-gpl: New Upstream fixes IJS Segfault Changed Bug title. > End of message, stopping processing here. Please c

Bug#350744: gliv aborted

On Thu, Feb 23, 2006 at 11:16:59PM +0800, LUK ShunTim wrote: > Here's the backtrace with gdb after re-building with debug enabled. > > $ LD_LIBRARY_PATH=/usr/lib/debug gdb gliv > GNU gdb 6.4-debian > Copyright 2005 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General

Bug#352499: marked as done (sbm: FTBFS: Missing Build-Depends on 'texinfo')

Your message dated Thu, 23 Feb 2006 13:47:39 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#352499: fixed in sbm 3.7.1-8 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 r

Bug#326581: marked as done ([hppa] glibc-2.3.5 lets python FTBFS)

Your message dated Thu, 23 Feb 2006 14:02:15 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#326581: fixed in glibc 2.3.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

Bug#324575: marked as done (sbm: FTBFS: Undefined reference to MAJOR)

Your message dated Thu, 23 Feb 2006 13:47:38 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#324575: fixed in sbm 3.7.1-8 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 r

Processed: KRGB bug maintenance, part 2

Processing commands for [EMAIL PROTECTED]: > severity 354120 grave Bug#354120: hpijs: Some graphics in PDFs are printed as black boxes Severity set to `grave'. > reassign 354120 gs-esp Bug#354120: hpijs: Some graphics in PDFs are printed as black boxes Bug reassigned from package `hpijs' to `gs-e

Processed: [PATCH] KRGB 1.0 bug fix for gs-gpl

Processing commands for [EMAIL PROTECTED]: > severity 294430 grave Bug#294430: gs-gpl: New Upstream fixes IJS Segfault Severity set to `grave'. > found 294430 8.01-5 Bug#294430: gs-gpl: New Upstream fixes IJS Segfault Bug marked as found in version 8.01-5. > tags 294430 patch Bug#294430: gs-gpl:

Bug#309847: marked as done (printing gives me all-black instead of color shapes)

Your message dated Thu, 23 Feb 2006 18:22:59 -0300 with message-id <[EMAIL PROTECTED]> and subject line Closing these bugs, as the fixed KRGB patch was merged in 8.15rc2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#267480: marked as done (gs-esp: wrong printing of white text on black background)

Your message dated Thu, 23 Feb 2006 18:22:59 -0300 with message-id <[EMAIL PROTECTED]> and subject line Closing these bugs, as the fixed KRGB patch was merged in 8.15rc2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If thi

Processed: Re: libxext: FTBFS in experimental: Missing build dependency.

Processing commands for [EMAIL PROTECTED]: > reassign 354167 libx11-dev 1.0.0-1 Bug#354167: libxext: FTBFS in experimental: Missing build dependency. Bug reassigned from package `libxext' to `libx11-dev'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tr

Bug#354167: libxext: FTBFS in experimental: Missing build dependency.

reassign 354167 libx11-dev 1.0.0-1 thanks On Thu, Feb 23, 2006 at 09:49:42PM +0100, Kurt Roeckx wrote: > This seems to be a missing build dependency on > x11proto-input-dev. > > It also can't find the xdmcp.pc, which looks like a missing build > dependency on libxdmcp-dev, but please make sure it

Bug#353533: Empty /usr/share/doc/grep-dctrl directory

On 19/02/06 12:43, Antti-Juhani Kaijanaho wrote: >>grep-dctrl has an empty /usr/share/doc/grep-dctrl directory > > It's supposed to be a symbolic link to dctrl-tools' doc dir. > > I've seen this happen myself, but I don't know what causes it. Do you > have any theories? The problem is this (Poli

Bug#350874: marked as done (kmymoney2 - FTBFS: error: kmymoney/export.h: No such file or directory)

Your message dated Thu, 23 Feb 2006 21:00:20 + with message-id <[EMAIL PROTECTED]> and subject line FIxed in upload of 0.8.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 now your responsib

Processed: KRGB IJS Bug cleanup for gs-esp, step 1: merging

Processing commands for [EMAIL PROTECTED]: > severity 303415 grave Bug#303415: gs-esp: Parts of characters or lines missing Severity set to `grave'. > severity 309847 grave Bug#309847: printing gives me all-black instead of color shapes Severity set to `grave'. > severity 267480 grave Bug#267480

Bug#354165: x11proto-core-dev: Wrong version requirement for x11-common.

merge 351779 354165 thanks Looks like they're the same, and I seem to have picked the same random one as Frank to report it against. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#354167: libxext: FTBFS in experimental: Missing build dependency.

Package: libxext Version: 1:1.0.0-1 Severity: serious Tags: experimental Hi, Your package is failing to build with the following error: checking for XEXT... configure: error: Package requirements (xproto x11 xextproto xau) were not met: Package inputproto was not found in the pkg-config search p

Bug#354165: x11proto-core-dev: Wrong version requirement for x11-common.

Package: x11proto-core-dev Version: 7.0.4-1 Severity: serious Hi, You have a lot of packages with a Pre-Dependency on x11-common, but all with the wrong version. It says things like: Pre-Depends: x11-common (>= 0.99) Or: Pre-Depends: x11-common (>= 1.0) Which can be satisfied by 6.9.0.dfsg.1-4.

Bug#354161: libx11: FTBFS in experimental: Missing .pc files.

Package: libx11 Version: 2:1.0.0-1 Severity: serious Tags: experimental Hi, Your package is failing to build with the following error: checking for BIGREQS... yes checking for XPROTO... yes checking for X11... configure: error: Package requirements (xextproto xtrans xau xcmiscproto) were not met:

Bug#314344: marked as done (netperf: FTBFS (amd64/gcc-4.0): Failed to get size of sin_port in struct sockaddr_in.)

Your message dated Thu, 23 Feb 2006 21:08:36 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#314344: netperf: FTBFS (amd64/gcc-4.0): Failed to get size of sin_port in struct sockaddr_in. has caused the attached Bug report to be marked as done. This means that you claim that the pro

Processed: severity of 354146 is serious

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.11 > severity 354146 serious Bug#354146: x11-common: Cannot upgrade from sarge: file conflict with xfree86-common Severity set to `serious'. > End of message, stopping processing here.

Bug#354091: marked as done (tar: buffer overflow [CVE-2006-0300])

Your message dated Thu, 23 Feb 2006 11:32:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#354091: fixed in tar 1.15.1-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 now your

Bug#208198: proposed bug fix /3

I appreciate your help in this but I belive this is the wrong solution. What needs to happen is libGL.so when xlibmesa-gl-dev is installed must still point to the real libGL.so.1.2 which is now diverted to /usr/lib/nvidia. So in sense, libGL.so -> /usr/lib/nvidia/libGL.so.1.2.xlibmesa And on top

Bug#354146: x11-common: Cannot upgrade from sarge: file conflict with xfree86-common

Package: x11-common Version: 1:7.0.0 Severity: grave After login in a sarge chroot, I installed tetex-bin (probably that can be much minimized to only xfree86-common, but I don't have time for testing) and then changed sources.list to point to sid. After apt-get update, I get upon apt-get dist-up

Bug#354145: mindi: Cdrom not detected after cdrom boot

Package: mindi Version: 1.06-3 Severity: grave Justification: renders package unusable When booting from a cdrom burned with mondorescue.iso, the kernel and initrd are loaded without problems. But after that, when looking after the other files on the cdrom, the system ask for the floppies. I don

Bug#353922: Bug #353922: kdepim FTBFS on alpha

Thanks for the patch. Daniel, any plans for another kdepim upload in the near future? Cheers, Christopher Martin On Wednesday 22 February 2006 17:43, Falk Hueffner wrote: > this should fix it (haven't tested though). > > --- kdepim-3.5.1/kresources/groupwise/soap/stdsoap2.h~ 2005-09-10 > 10:23:

Bug#354073: marked as done (ktalkd always says the user is not logged in even when it is.)

Your message dated Thu, 23 Feb 2006 11:28:53 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug not found in present version 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 r

Bug#353314: marked as done (surfraw: FTBFS with new make)

Your message dated Thu, 23 Feb 2006 08:17:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#353314: fixed in surfraw 2.1.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#273071: marked as done (Not stable enough; don't propagate to testing)

Your message dated Thu, 23 Feb 2006 16:53:15 +0100 with message-id <[EMAIL PROTECTED]> and subject line Has been stable 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

Processed: Re: Bug#351409: qgis currently uninstallable in unstable; replacement library avail?

Processing commands for [EMAIL PROTECTED]: > tags 351409 +pending Bug#351409: qgis: FTBFS due to unmet build-dep on libgdal1-dev There were no tags set. Tags added: pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (adm

Processed: Re: Processed: May a package assume that builds are performed with root-like rights?

Processing commands for [EMAIL PROTECTED]: > reassign 354113 tex-common Bug#354113: jadetex: FTBFS: mktexdir failed Bug reassigned from package `jadetex' to `tex-common'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrat

Bug#354113: May a package assume that builds are performed with root-like rights? (was: jadetex: FTBFS: mktexdir failed)

Le Jeudi 23 Février 2006 16:37, Frank Küster a écrit : > So the current state is: If pbuilder runs all commands inside the > chroot, everything is fine, and AFAIK the same is true for the buildds. > But if you su to some user in the chroot, near to every package that > Build-depends on tetex-bin w

Bug#354113: May a package assume that builds are performed with root-like rights?

Hi, Frank Küster wrote: In short: May a package assume that package builds are performed with root-like rights, and thus use non-world-writable directories for caching purposes? Absolutely not. The only assumption you may make is that the binary* targets are called in a way that allows chown

Bug#354132: asterisk: Upgrading destroys astdb

Package: asterisk Version: 1:1.2.4.dfsg-6 Severity: grave Justification: causes non-serious data loss After upgrading from 1.2.1 to 1.2.4, all existing contents of the astdb appear to have been wiped out entirely. This is very bad, since we put a host of vital information in there. -- System Inf

Bug#351409: qgis currently uninstallable in unstable; replacement library avail?

tags 351409 +pending thanks On Thu, 2006-02-23 at 02:16 -0500, Chris Metzler wrote: > Package: qgis > Followup-For: Bug #351409 > > qgis is currently uninstallable in unstable, apparently for the same > reason: libgdal1c2a, which is no longer available, is specified as > a dependancy. This pack

Bug#354113: May a package assume that builds are performed with root-like rights? (was: jadetex: FTBFS: mktexdir failed)

reassing 354113 tex-common thanks I think this problem is of general interest, or at least I don't feel we (the TeX Task Force) cannot decide this on our own. In short: May a package assume that package builds are performed with root-like rights, and thus use non-world-writable directories for ca

Bug#354113: jadetex: FTBFS: mktexdir failed

Florent Rougon <[EMAIL PROTECTED]> wrote: > 1. Install tex-common and tetex-base, configure tex-common last (if > needed, use 'dpkg-reconfigure tex-common'). The permissions of > /var/cache/fonts are "drwxrwsr-t root:users" (I answer 'yes' to the > question "manage the cache permissio

Bug#354105: /etc/init.d/xprint sets "ulimit -n 1024"

Drew Parsons wrote: > > It sounds like your ant build is the real problem. You need the default > ulimit -n to be 1024 for everything else, but increase it only for the > shell running the build. > I forgot to mention, after /etc/init.d/xprint sets "ulimit -n 1024", i *cannot* increase the uli

Bug#354105: /etc/init.d/xprint sets "ulimit -n 1024"

Drew Parsons wrote: > On Thu, 2006-02-23 at 14:57 +0100, Christoffer Hammarström wrote: > >>Can you >> >>>really run ulimit -n 8192 after having removed xprint? >>> >> >>Yes, i can. This is because i've added the following lines to >>/etc/security/limits.conf: >> >>*softnofile

Bug#350744: gliv aborted

Steve Langasek wrote: > reopen 350744 > thanks > > Uh... whoops, sent to the wrong address. Let's reopen this... ShunTim, the > request still stands. :) > > Thanks, Here's the backtrace with gdb after re-building with debug enabled. $ LD_LIBRARY_PATH=/usr/lib/debug gdb gliv GNU gdb 6.4-debian

Bug#354113: jadetex: FTBFS: mktexdir failed

Le Jeudi 23 Février 2006 15:35, Frank Küster a écrit : > Daniel Schepler <[EMAIL PROTECTED]> wrote: > > Package: jadetex > > Version: 3.13-6 > > Severity: serious > > > > From my pbuilder build log: > > > > ... > > Transcript written on jadetex.log. > > make[1]: Leaving directory `/tmp/buildd/jadet

Bug#345631: marked as done (libaqbanking0c2a: aqhbci-qt3-wizard segfaults when creating user)

Your message dated Thu, 23 Feb 2006 15:34:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#345631: libaqbanking0c2a: aqhbci-qt3-wizard segfaults when creating user has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt w

Bug#354113: jadetex: FTBFS: mktexdir failed

Daniel Schepler <[EMAIL PROTECTED]> wrote: > Package: jadetex > Version: 3.13-6 > Severity: serious > > From my pbuilder build log: > > ... > Transcript written on jadetex.log. > make[1]: Leaving directory `/tmp/buildd/jadetex-3.13' > pdflatex '\nonstopmode\input{jadetex.dtx}' > latex.log > kpaths

Bug#354105: /etc/init.d/xprint sets "ulimit -n 1024"

On Thu, 2006-02-23 at 14:57 +0100, Christoffer Hammarström wrote: > Can you > > really run ulimit -n 8192 after having removed xprint? > > > > Yes, i can. This is because i've added the following lines to > /etc/security/limits.conf: > > *softnofile 8192 > *

Processed: correcting wrong bug number in control mail

Processing commands for [EMAIL PROTECTED]: > severity 347932 wishlist Bug#347932: bluez-pin: please include also bluez-noninteractive-pin in source package Severity set to `wishlist'. > retitle 347932 bluez-pin: please include also bluez-noninteractive-pin Bug#347932: bluez-pin: please include a

Processed: screwed up bug number

Processing commands for [EMAIL PROTECTED]: > severity 347932 wishlist Bug#347932: FTBFS: needs update for libsysfs transition Severity set to `wishlist'. > retitle 347932 bluez-pin: please include also bluez-noninteractive-pin in > source package Bug#347932: FTBFS: needs update for libsysfs tran

Bug#354113: jadetex: FTBFS: mktexdir failed

Hi, Daniel Schepler <[EMAIL PROTECTED]> wrote: > From my pbuilder build log: > > ... > Transcript written on jadetex.log. > make[1]: Leaving directory `/tmp/buildd/jadetex-3.13' > pdflatex '\nonstopmode\input{jadetex.dtx}' > latex.log > kpathsea: Running mktextfm ecrm1000 > mkdir: cannot create d

Processed: libsysfs-Transition

Processing commands for [EMAIL PROTECTED]: > severity 347932 serious Bug#347932: bluez-pin: please include also bluez-noninteractive-pin in source package Severity set to `serious'. > retitle 347932 FTBFS: needs update for libsysfs transition Bug#347932: bluez-pin: please include also bluez-noni

Bug#354105: /etc/init.d/xprint sets "ulimit -n 1024"

Drew Parsons wrote: > I'm not sure that I can see what the problem is. ulimit -n 8192 does > not run even when Xprt is not running, the limit it can be set to is -n > 512, though higher values can be set as su. As far as I can tell this > behaviour is system controlled somewhere, not related to X

Bug#354105: /etc/init.d/xprint sets "ulimit -n 1024"

On Thu, 2006-02-23 at 13:47 +0100, Christoffer Hammarström wrote: > > /etc/init.d/xprint sets "ulimit -n 1024". > > This makes other programs break with "too many open files", but more > importantly, > i can't set a higher ulimit in bash: > > $ ulimit -n 8192 > -bash: ulimit: open files: canno

Bug#354113: jadetex: FTBFS: mktexdir failed

Package: jadetex Version: 3.13-6 Severity: serious From my pbuilder build log: ... Transcript written on jadetex.log. make[1]: Leaving directory `/tmp/buildd/jadetex-3.13' pdflatex '\nonstopmode\input{jadetex.dtx}' > latex.log kpathsea: Running mktextfm ecrm1000 mkdir: cannot create directory `./

Bug#345604: License of the fontinst documentation

Dear fontinst maintenance team, upon verifying the license information for various packages on CTAN and in Debian's teTeX package, I found that the license information for fontinst is incomplete. Every source file contains a "LPPL version or later" statement, but the pure documentation files don

Bug#354105: /etc/init.d/xprint sets "ulimit -n 1024"

Package: xprint Version: 1:0.1.0.alpha1-13 Severity: critical Justification: breaks unrelated software /etc/init.d/xprint sets "ulimit -n 1024". This makes other programs break with "too many open files", but more importantly, i can't set a higher ulimit in bash: $ ulimit -n 8192 -bash: ulimit

Bug#345631: libaqbanking0c2a: aqhbci-qt3-wizard segfaults when creating user

Hello Micha. On Thursday 23 February 2006 04:06, Micha Lenk wrote: > The aqhbci-qt3-wizard has vanished and is from now on replaced by a > common wizard for all backends. Thus I propose to close this bug. > > Do you agree? Sure, thanks. Karsten -- fishfarm netsolutions - Karsten Dambekalns Hamb

Bug#346694: marked as done (geg: FTBFS: build-depends on removed xlibs-dev)

Your message dated Thu, 23 Feb 2006 04:32:03 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#346694: fixed in geg 1.0.2-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 your r

Bug#292231: Resolution of #292231 [Manpage of hasciicam]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Feb 22, 2006 at 02:03:57AM -0800, Don Armstrong wrote: > Greetings; I NMUed hasciicam to fix an RC bug that was holding up a > package transition in Debian. In the process of making this NMU, I > discovered that the package contained a GFDLed m

Bug#215664: marked as done (gaby: debhelper build dependency must be versioned)

Your message dated Thu, 23 Feb 2006 12:57:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line fixed in 2.0.2-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 your responsibility to

Bug#354099: xdm_1:1.0.1-1(sparc/experimental): FTBFS: configure error

Package: xdm Version: 1:1.0.1-1 Severity: serious Hi, your package failed to build from source. The cause are probably the missing epoches in the build-dependencies. | Automatic build of xdm_1:1.0.1-1 on odin by sbuild/sparc 79 | Build started at 20060223-0719

Bug#354098: twm_1:1.0.1-1(sparc/experimental): FTBFS: configure error

Package: twm Version: 1:1.0.1-1 Severity: serious Hi, your package failed to build from source. Maybe you need to version your build-dependencies? | Automatic build of twm_1:1.0.1-1 on odin by sbuild/sparc 79 | Build started at 20060223-0717

Bug#354093: libnss-ldap: getent segfault when reading large uid-/gidNumbers

Package: libnss-ldap Version: 238-1.1 Severity: grave Justification: renders package unusable There's a buffer overflow in the uid-/gidNumber handling code. It is limited to the length of uid_t (hard coded), but the ldap schema allows large integer numbers. Using long integer numbers causes a se

Bug#354091: tar: buffer overflow [CVE-2006-0300]

Package: tar Version: 1.15.1-2 Severity: critical Tags: security patch Hi! A while ago an exploitable buffer overflow was published in tar [1]. Unfortunately this got commonly known only recently. You can get the patch (which was extracted from upstream CVS) from [2]. Woody's version is not affe

Bug#350480: acknowledged by developer (Bug#352520: fixed in vnc4 4.1.1+X4.3.0-3)

Hi On Thu, Feb 23, 2006 at 10:58:14AM +0100, Laurent Bonnaud wrote: > > > > vnc4 (4.1.1+X4.3.0-3) unstable; urgency=low > > > . > > >* Made vnc.so optional for some architectures as it is only built > > > on some because of the X build configuration, closes: #352520. > > Thank you for

Processed: reopen 350480

Processing commands for [EMAIL PROTECTED]: > reopen 350480 Bug#350480: xvnc4viewer: FTBFS on amd64 Bug#350405: FTBFS: cast from 'void*' to 'CARD32' loses precision Bug#352520: vnc4 - FTBFS: mv: cannot stat `/build/buildd/vnc4-4.1.1+X4.3.0/debian/tmp/usr/X11R6/lib/modules/extensions/vnc.so': No s

Bug#350480: acknowledged by developer (Bug#352520: fixed in vnc4 4.1.1+X4.3.0-3)

> > vnc4 (4.1.1+X4.3.0-3) unstable; urgency=low > > . > >* Made vnc.so optional for some architectures as it is only built > > on some because of the X build configuration, closes: #352520. Thank you for the new version! However I still cannot build vnc4_4.1.1+X4.3.0-3.dsc on amd64:

Bug#208198: proposed bug fix /3

Hello Please excuse my typos / non-existent "postinst.in" above. Now I've a clean solution: In the file "debian/nvidia-glx.links.in" add the following line (and update "debian/nvidia-glx.links" of course): usr/lib/libGL.so.#VERSION# usr/lib/libGL.so.1.2 I really hope that it will fix this bug.

  1   2   >