Bug#334613: tetex-bin: same problem still exists

2005-11-08 Thread Frank Küster
Kenward Vaughan [EMAIL PROTECTED] wrote: I'm attaching the output of this and the others asked by Frank. I did include a listing of /etc/texmf as well (1st run wasn't recursive). Script started on Mon 07 Nov 2005 04:05:16 PM PST 04:05:16 daddy:~# ls -l /etc/texmf/updmap.d/ total 11

Bug#338115: mime-codecs: base64-decode fails to properly decode many valid base64-encoded files

2005-11-08 Thread Daniel Kahn Gillmor
Package: mime-codecs Version: 7.19-7 Severity: grave Tags: patch Justification: renders package unusable It appears that the buffering recently introduced to base64-decode has some major flaws in it that render of all base64-encoded files that are larger than the input buffer size (~36K)

Bug#338098: libextlib-ocaml-dev: is not installable in unstable

2005-11-08 Thread Stefano Zacchiroli
On Tue, Nov 08, 2005 at 12:10:17PM +0800, Paul Wise wrote: ocaml has been updated to a new upstream version. as a result, libextlib-ocaml-dev needs to be updated. I see a lot of your other packages are in the same situation. In order to ease migration into testing of the whole bunch of ocaml

Bug#338090: Broken python binding

2005-11-08 Thread Loic Minier
clone 338090 -1 reassign -1 python-gtk2-dev 2.8.0-1 retitle -1 pygtk-codegen-2.0 from 2.8's pygtk generates code incompatible with python 2.3 severity -1 important thanks Hi, On Mon, Nov 07, 2005, Manish Singh wrote: Due to a bug upstream

Processed: Re: Bug#338090: Broken python binding

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: clone 338090 -1 Bug#338090: Broken python binding Bug 338090 cloned as bug 338117. reassign -1 python-gtk2-dev 2.8.0-1 Bug#338117: Broken python binding Bug reassigned from package `python-vte' to `python-gtk2-dev'. retitle -1 pygtk-codegen-2.0 from

Processed: merging python-vte bindings bugs

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: reassign #334001 vte 1:0.11.15-1 Bug#334001: Importing vte in python doesn't work Bug#334668: ImportError while trying to import the vte module Bug reassigned from package `pygtk' to `vte'. reassign #338090 vte 1:0.11.15-1 Bug#338090: Broken python

Bug#334613: tetex-bin: same problem still exists

2005-11-08 Thread Frank Küster
clone 334613 -1 found -1 3.0-10.1 retitle -1 Should make sure the TEXFONTPATH setting is correct severity -1 normal submitter -1 Kenward Vaughan [EMAIL PROTECTED] stop Frank Küster [EMAIL PROTECTED] wrote: Kenward Vaughan [EMAIL PROTECTED] wrote: 04:06:19 daddy:~# kpsewhich --format=map

Bug#338090: Broken python binding

2005-11-08 Thread Loic Minier
On Tue, Nov 08, 2005, Loic Minier wrote: ... which suggest the problem will be fixed. I don't get the same import vte error, but it still fails: import vte Traceback (most recent call last): File stdin, line 1, in ? ImportError: could not import gtk._gtk (This is with

Bug#338030: yaird error: Could not read output for /sbin/lvdisplay -c (fatal)

2005-11-08 Thread Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 07 Nov 2005 21:43:34 -0600 Bill Gatliff [EMAIL PROTECTED] wrote: Alright. I'll send a report to lvm2. ...or this bugreport can be reasigned. I just wanted to make sure I didn't reassign if I somehow misunderstood. Tell me if you've

Processed: Re: Bug#330983: asterisk: Building chan_zap.so requires zaptel.h at the wrong place

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: severity 330983 serious Bug#330983: asterisk: Building chan_zap.so requires zaptel.h at the wrong place Severity set to `serious'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator

Bug#336324: marked as done (inkscape_0.42.2+0.43pre1-1(hppa/unstable): FTBFS: needs gcc-3.4 on some architectures)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Nov 2005 03:32:09 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#336324: fixed in inkscape 0.42.2+0.43pre2-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

Bug#338141: gnucash uninstallable in Unstable

2005-11-08 Thread Barrett Dillow
Subject: gnucash: Gnucash uninstallable in Unstable Package: gnucash Version: 1.8.10-19 Severity: grave Justification: renders package unusable *** Please type your report below this line *** Gnucash uninstallable on Debian unstable. It appears to stem from a conflict between slib and

Bug#338142: kdegraphics: FTBFS: missing declarations

2005-11-08 Thread Roland Stigge
Package: kdegraphics Version: 4:3.4.2-2 Severity: serious Tags: patch Hi, building the package kdegraphics in a clean sid build environment (with pbuilder) on i386 results in: = [...] make[5]: Entering directory

Bug#338147: pnetc: FTBFS: CC=cscc in configure

2005-11-08 Thread Roland Stigge
Package: pnetc Version: 0.6.12-1 Severity: serious Hi, building the package pnetc in a clean sid build environment (with pbuilder) on i386 results in: = [...] fi touch debian/stamp-autotools-files chmod a+x

Bug#338030: yaird error: Could not read output for /sbin/lvdisplay -c (fatal)

2005-11-08 Thread Bill Gatliff
Jonas: Jonas Smedegaard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 07 Nov 2005 21:43:34 -0600 Bill Gatliff [EMAIL PROTECTED] wrote: Alright. I'll send a report to lvm2. ...or this bugreport can be reasigned. I just wanted to make sure I didn't reassign if I

Bug#333795: marked as done (libwxgtk2.4-1-python - python-wxgtk2.4)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Nov 2005 05:17:05 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#333795: fixed in python-scipy 0.3.2-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

Bug#334691: marked as done (Loadkeys fails to recognise some keysyms)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Nov 2005 06:17:12 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#334691: fixed in console-tools 1:0.2.3dbs-58 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

Bug#338164: yacas: FTBFS: missing libs Xmu and Xt

2005-11-08 Thread Roland Stigge
Package: yacas Version: 1.0.57-2 Severity: serious Hi, building the package yacas in a clean sid build environment (with pbuilder) on i386 results in: = [...] mkdir .libs g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src

Bug#338030: yaird error: Could not read output for /sbin/lvdisplay -c (fatal)

2005-11-08 Thread Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 reassign 338030 lvm2 retitle 338030 lvdisplay checksum error thanks On Tue, 08 Nov 2005 07:15:41 -0600 Bill Gatliff [EMAIL PROTECTED] wrote: Jonas: Jonas Smedegaard wrote: On Mon, 07 Nov 2005 21:43:34 -0600 Bill Gatliff [EMAIL PROTECTED]

Processed: Re: Bug#338030: yaird error: Could not read output for /sbin/lvdisplay -c (fatal)

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: reassign 338030 lvm2 Bug#338030: yaird error: Could not read output for /sbin/lvdisplay -c (fatal) Bug reassigned from package `yaird' to `lvm2'. retitle 338030 lvdisplay checksum error Bug#338030: yaird error: Could not read output for

Processed: New upstream release packaged

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: tags 286191 patch Bug#286191: uae: new uptream version There were no tags set. Tags added: patch tags 271476 patch Bug#271476: uae: build dependency on xlibs-dev There were no tags set. Tags added: patch tags 238678 patch Bug#238678: uae: Unable to

Bug#297251: New upstream release packaged

2005-11-08 Thread Florian Ernst
tags 286191 patch tags 271476 patch tags 238678 patch tags 201563 patch tags 190258 patch tags 297251 patch thanks [EMAIL PROTECTED] BCC'd Hello *, FWIW, I've packaged the most recent upstream version. Please note that those packages greatly differ from previous versions, most notacibly only one

Bug#334954: make FTBFS: DVI cannot be opened

2005-11-08 Thread Roland Stigge
Hi, looks like a #322353 that hasn't been fixed. (I can reproduce the problem very well.) bye, Roland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#334954: make FTBFS: DVI cannot be opened

2005-11-08 Thread Roland Stigge
On Tue, 2005-11-08 at 16:46 +0100, Roland Stigge wrote: looks like a #322353 that hasn't been fixed. (I can reproduce the problem very well.) Sorry, should have been 334953. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#337524: libogre-dev works perfectly well here

2005-11-08 Thread Federico Di Gregorio
I don't know which mirror you exactly use but the current version of the ogre-plugins-cgprogrammanager package depends on libdevil1c2, not libdevil1c2. Also, libogre-dev works perfectly well with the last libopenexr-dev package in unstable. Can you please provide your /etc/apt/sources.list file

Bug#326507: marked as done (The plugin makes Firefox crash very often)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Nov 2005 07:47:14 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#326507: fixed in mplayerplug-in 3.15-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

Bug#338142: kdegraphics: FTBFS: missing declarations

2005-11-08 Thread Christopher Martin
tags 338142 pending stop On November 8, 2005 07:53, Roland Stigge wrote: building the package kdegraphics in a clean sid build environment (with pbuilder) on i386 results in: = [...] make[5]: Entering directory

Processed: Re: Bug#338142: kdegraphics: FTBFS: missing declarations

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: tags 338142 pending Bug#338142: kdegraphics: FTBFS: missing declarations Tags were: patch Tags added: pending stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian

Bug#338185: stay on 2.6.12 for now

2005-11-08 Thread dann frazier
Package: linux-2.6 Version: 2.6.14-2 Severity: critical ia64 users shouldn't upgrade to 2.6.14 yet - the ia64 kernel currently has problems footprinting initramfs, which means it can't work with either yaird or initramfs-tools. Monitor this bug for status info. -- dann frazier [EMAIL

Bug#338087: mpfr_2.2.0.dfsg.1-2_m68k: FTBFS: 2 of 117 tests failed

2005-11-08 Thread Laurent Fousse
Hello, * Aníbal Monsalve Salazar [2005-11-08]: There was an error while trying to autobuild your package: [...] Full build logs are available on buildd.debian.org. Please refer to the build log at:

Processed: found 333052 in 0-1

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.8 found 333052 0-1 Bug#333052: race in the modules loader? Bug#333522: udev: modules randomly aren't loaded at startup - Unknown symbol Bug marked as found in version 0-1. End of

Processed: About to be removed (#335488)

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: tag 298909 etch-ignore Bug#298909: zope-mysqlda: depends on zope and forgets about zope2.7 Tags were: wontfix Tags added: etch-ignore tag 337410 etch-ignore Bug#337410: zope-znavigator: Uninstallable due to zope transition Tags were: wontfix Tags

Processed: Tagging

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: severity 329041 important Bug#329041: valgrind: Valgrind is being compiled with SSE instruction set Severity set to `important'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator

Processed: Re: Processed: About to be removed (#335488)

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: # please *do* *not* set etch-ignore without explizit approval tag 298909 - etch-ignore Bug#298909: zope-mysqlda: depends on zope and forgets about zope2.7 Tags were: etch-ignore wontfix Tags removed: etch-ignore tag 337410 - etch-ignore Bug#337410:

Processed: Fixed in NMU of linux-patch-2.6-mips 2.6.12-3

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: tag 335967 + fixed Bug#335967: BBPFS (experimental): mips-tools doesn't include binary Tags were: experimental Tags added: fixed quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator

Bug#337869: marked as done (failed to rename /var/lib/aptitude/pkgstates to /var/lib/aptitude/pkgstates.old - save_selection_list (2 No such file or directory))

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Nov 2005 09:47:07 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#337869: fixed in aptitude 0.4.0-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

Bug#338093: marked as done (/var/lib/aptitude/pkgstates not created on new install)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Nov 2005 09:47:07 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#337869: fixed in aptitude 0.4.0-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

Bug#337820: marked as forwarded (tse3 - FTBFS: error: call of overloaded 'element(const char [9], size_t)' is ambiguous)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 8 Nov 2005 10:05:06 -0800 with message-id [EMAIL PROTECTED] has caused the Debian Bug report #337820, regarding tse3 - FTBFS: error: call of overloaded 'element(const char [9], size_t)' is ambiguous to be marked as having been forwarded to the upstream software author(s)

Bug#336114: Forwarded upstream

2005-11-08 Thread Matthias Klose
Nathanael Nerode writes: tags 336114 +upstream forwarded 336114 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24712 thanks Forwarded upstream as GCC bug number 24712. I think, that's not upstream. both changes were made between the 4.0.1 and the 4.0.2 release. Matthias -- To

Processed: Fixed in upload of liferea 0.9.7b+test1.0rc3-1 to experimental

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: tag 333103 + fixed-in-experimental Bug#333103: liferea: [gnome 2.12 transition] build-depend on dbus changes Tags were: experimental Tags added: fixed-in-experimental quit Stopping processing here. Please contact me if you need assistance. Debian

Bug#338197: ekg2_20051106+1657-1(sparc/experimental): FTBFS: tried to write outside build directory

2005-11-08 Thread Frank Lichtenheld
Package: ekg2 Version: 20051106+1657-1 Severity: serious Hi, your package failed to build: | Automatic build of ekg2_20051106+1657-1 on odin by sbuild/sparc 69 | Build started at 20051108-0726 | ** | Checking available

Bug#338202: installation error: rmdir: `/tmp/udev.LoQwmw': Directory not empty

2005-11-08 Thread Sean Finney
Package: udev Version: 0.071-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 mini-me[~]19:36:14$ sudo apt-get install udev Reading package lists... Done Building dependency tree... Done The following extra packages will be installed:

Bug#337791: librplay3-dev: should depend on libc6-dev

2005-11-08 Thread Branden Robinson
On Sun, Nov 06, 2005 at 04:18:11PM +0100, Frank Lichtenheld wrote: On Sun, Nov 06, 2005 at 09:55:07AM -0500, Branden Robinson wrote: Package: librplay3-dev Version: 3.3.2-9 Severity: serious File: /usr/include/rplay.h Per Policy §3.5, librplay3-dev should depend on libc6-dev |

Bug#338090: Broken python binding

2005-11-08 Thread Manish Singh
On Tue, Nov 08, 2005 at 11:42:24AM +0100, Loic Minier wrote: On Tue, Nov 08, 2005, Loic Minier wrote: ... which suggest the problem will be fixed. I don't get the same import vte error, but it still fails: import vte Traceback (most recent call last): File stdin, line 1,

Bug#338030: Processed: Re: Bug#338030: yaird error: Could not read output for /sbin/lvdisplay -c (fatal)

2005-11-08 Thread Bastian Blank
severity 338030 normal tags 338030 wontfix thanks lvm checks for several errors in the headers since some versions. Please use vgcfgbackup and vgcfgrestore to fix the errors, after you have checked that the backup is correct. Bastian -- We have phasers, I vote we blast 'em! --

Processed: Re: Processed: Re: Bug#338030: yaird error: Could not read output for /sbin/lvdisplay -c (fatal)

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: severity 338030 normal Bug#338030: lvdisplay checksum error Severity set to `normal'. tags 338030 wontfix Bug#338030: lvdisplay checksum error There were no tags set. Tags added: wontfix thanks Stopping processing here. Please contact me if you

Bug#335434: marked as done (FTBFS with recent l-k-h; should not use l-k-h)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Nov 2005 10:47:09 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#335434: fixed in dcgui 0.80-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#338202: marked as done (installation error: rmdir: `/tmp/udev.LoQwmw': Directory not empty)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 8 Nov 2005 19:57:34 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#338202: installation error: rmdir: `/tmp/udev.LoQwmw': Directory not empty has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt

Bug#337881: udev: post-inst still fails in 0.074-1

2005-11-08 Thread Vincent Bernat
Package: udev Version: 0.074-1 Followup-For: Bug #337881 reopen #337881 thanks This bug is still present in 0.074-1. The same work-around applies. -- Package-specific info: -- /etc/udev/rules.d/: /etc/udev/rules.d/: total 24 lrwxrwxrwx 1 root root 20 2005-04-10 14:12 020_permissions.rules -

Processed: udev: post-inst still fails in 0.074-1

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: Package: udev Unknown command or malformed arguments to command. Version: 0.074-1 Unknown command or malformed arguments to command. Followup-For: Bug #337881 Unknown command or malformed arguments to command. reopen #337881 Bug#337881: udev

Bug#338205: lucene: Change of distribution requires source-full upload with new version

2005-11-08 Thread Goswin Brederlow
Package: lucene Version: 1.4.3-8 Severity: serious Justification: missing sources in main Hi, your package lucene recently moved from contrib to main. Unfortunately the DAK is unable to handle two debian revisions of the same upstream version in different distributions (contrib vs. main) and the

Bug#338206: can't install, because of dependency?

2005-11-08 Thread Steffen Joeris
Package: libgnomeprint15 Severity: serious Hi I can't install the package libgnomeprint15, because it depends on a specific version of libgnomeprint-data, but the version of libgnomeprint-data in unstable is newer than the dependency. This makes libgnomeprint15 and other packages which are

Bug#338113: fwbuilder: FTBFS: needs new version of libfwbuilder

2005-11-08 Thread Jeremy T. Bouse
Please tell me you're not wasting my time with this while I'm working to get 2.0.9 packaged? Of course fwbuilder 2.0.7 is going to fail to build when I uploade 2.0.9 libfwbuilder. I have to get libfwbuilder into the mirror before I can upload fwbuilder 2.0.9 for this precise reason. Quit

Processed: tagging 335671

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.8 tags 335671 + pending Bug#335671: spamassassin: Missing depends on libio-socket-inet6-perl There were no tags set. Tags added: pending End of message, stopping processing here.

Bug#327736: This isn't tk8.4's fault

2005-11-08 Thread Wouter Verhelst
reassign 327746 tk8.4 severity 327746 grave reassign 327736 tk8.4 severity 327736 grave merge 327736 327746 retitle 327736 tk8.4: needs to be rebuilt on m68k tags 327736 + pending thanks Hi, It appears tk8.4 was built with binutils 2.16.1cvs20050902, which is utterly broken on m68k, in that it

Bug#336373: subversion: svn MKCOL ssl error

2005-11-08 Thread Thomas Petazzoni
Hi, On Sun, 6 Nov 2005 13:47:01 -0600 Peter Samuelson [EMAIL PROTECTED] wrote: Since you have a ready test case for this, can you try the neon package at http://www.barcikacomp.hu/deb/libneon25_0.25.4.dfsg-1_i386.deb, as mentioned in Bug #335574? With a Debian sid updated yesterday and your

Bug#337881: udev: post-inst still fails in 0.074-1

2005-11-08 Thread Marco d'Itri
On Nov 08, Vincent Bernat [EMAIL PROTECTED] wrote: This bug is still present in 0.074-1. The same work-around applies. I highly doubt this, considering that prerm does not use --stop --exec anymore. You problem was that when upgrading from the buggy releases the old prerm was used, I will add

Bug#338206: marked as done (can't install, because of dependency?)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Nov 2005 11:59:59 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#338206: can't install, because of dependency? 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

Bug#338205: lucene: Change of distribution requires source-full upload with new version

2005-11-08 Thread Michael Koch
On Tue, Nov 08, 2005 at 08:17:04PM +0100, Goswin Brederlow wrote: Package: lucene Version: 1.4.3-8 Severity: serious Justification: missing sources in main Hi, your package lucene recently moved from contrib to main. Unfortunately the DAK is unable to handle two debian revisions of the

Processed: Block no longer applies

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: unblock 335434 by 336577 Bug#335434: FTBFS with recent l-k-h; should not use l-k-h Was blocked by: 336577 Blocking bugs removed: 336577 unblock 335435 by 336577 Bug#335435: FTBFS with recent l-k-h; should not use l-k-h Was blocked by: 336577 Blocking

Processed: This isn't tk8.4's fault

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: reassign 327746 tk8.4 Bug#327746: ocaml: [m68k] FTBFS: Bug reassigned from package `ocaml' to `tk8.4'. severity 327746 grave Bug#327746: ocaml: [m68k] FTBFS: Severity set to `grave'. reassign 327736 tk8.4 Bug#327736: lablgl: FTBFS on m68k,

Bug#338215: maxima_5.9.2-2_hppa: FTBFS: ./maxima: No such file or directory

2005-11-08 Thread Aníbal Monsalve Salazar
Package: maxima Severity: serious Version: 5.9.2-2 Tags: sid Justification: fails to build from source There was an error while trying to autobuild your package: Automatic build of maxima_5.9.2-2 on sarti by sbuild/hppa 69 Build started at 20051108-1819 [...] ** Using build dependencies

Bug#336373: subversion: svn MKCOL ssl error

2005-11-08 Thread Peter Samuelson
[Thomas Petazzoni] Since you have a ready test case for this, can you try the neon package at http://www.barcikacomp.hu/deb/libneon25_0.25.4.dfsg-1_i386.deb, as mentioned in Bug #335574? With a Debian sid updated yesterday and your package, it still doesn't work: Oh, doh!

Processed: setting package to cmucl cmucl-clm cmucl-docs cmucl-source, tagging 337258

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.8 package cmucl cmucl-clm cmucl-docs cmucl-source Ignoring bugs not assigned to: cmucl-source cmucl-clm cmucl cmucl-docs tags 337258 + pending Bug#337258: cmucl: FTBFS with new

Bug#338202: installation error: rmdir: `/tmp/udev.LoQwmw': Directory not empty

2005-11-08 Thread Sean Finney
On Tue, Nov 08, 2005 at 07:57:34PM +0100, Marco d'Itri wrote: It's not obvious what is happening since you did not report the content of the directory. yes, i probably should have supplied that info... unfortunately, i've rebooted since then. fortunately, nothing evil seemd to happen on reboot

Bug#338220: asterisk_1:1.0.9.dfsg-6_mips: FTBFS: internal compiler error: Floating point exception

2005-11-08 Thread Aníbal Monsalve Salazar
Package: asterisk Severity: serious Version: 1:1.0.9.dfsg-6 Tags: sid Justification: fails to build from source There was an error while trying to autobuild your package: Automatic build of asterisk_1:1.0.9.dfsg-6 on ball by sbuild/mips 69 Build started at 20051108-1951 [...] ** Using build

Bug#338222: koffice_1:1.4.2-2_m68k: FTBFS: internal compiler error

2005-11-08 Thread Aníbal Monsalve Salazar
Package: koffice Severity: serious Version: 1:1.4.2-2 Tags: sid Justification: fails to build from source There was an error while trying to autobuild your package: Automatic build of koffice_1:1.4.2-2 on a4000t by sbuild/m68k 69 Build started at 20051107-2208 [...] ** Using build dependencies

Bug#338226: lirc-modules-source: does not build without kernel-source

2005-11-08 Thread Evgeni Dobrev
Package: lirc-modules-source Version: 0.7.1pre2-2 Severity: serious Justification: no longer builds from source Hi, the lirc-modules-source build process needs the kernel-sources. Trying to build using only the kernel-headers will fail with the following error: /usr/src/modules/lirc$

Bug#327746: This isn't tk8.4's fault

2005-11-08 Thread Sven Luther
On Tue, Nov 08, 2005 at 08:50:26PM +0100, Wouter Verhelst wrote: reassign 327746 tk8.4 severity 327746 grave reassign 327736 tk8.4 severity 327736 grave merge 327736 327746 retitle 327736 tk8.4: needs to be rebuilt on m68k tags 327736 + pending thanks Hi, It appears tk8.4 was built

Bug#330983: asterisk: Building chan_zap.so (and five other modules) requires zaptel.h at the wrong place

2005-11-08 Thread Andreas Barth
Hi, * Christoph Biedl ([EMAIL PROTECTED]) [051108 11:09]: ii zaptel-source1.0.7-4.1Zapata telephony interface (source code for kern In other words: To verify I've started with a fresh sarge installation today and built asterisk again. I tried now with pbuilder on sid; the

Processed: asterisk: block 338220 with 336167

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: block 338220 with 336167 Bug#338220: asterisk_1:1.0.9.dfsg-6_mips: FTBFS: internal compiler error: Floating point exception Was not blocked by any bugs. Blocking bugs added: 336167, 336463 thanks Stopping processing here. Please contact me if you

Processed: Fixed in NMU of aime 0.60.3-7.2

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: tag 292953 + fixed Bug#292953: aime: FTBFS (amd64/gcc-4.0): explicit specialization of 'LinkedNodeTYPE::LinkedNode(TYPE*)' must be introduced by 'template ' Tags were: patch Bug#334124: FTBFS on 64bit arches Tags added: fixed tag 334124 + fixed

Bug#338220: asterisk_1:1.0.9.dfsg-6_mips: FTBFS: internal compiler error: Floating point exception

2005-11-08 Thread Aníbal Monsalve Salazar
On Tue, Nov 08, 2005 at 02:19:02PM -0800, Steve Langasek wrote: This is bug #336463 in gcc-4.0; I knew that. That's why I blocked #338220 with #336167. it is not a bug in asterisk. It's still a bug in asterisk as it FTBFS. Aníbal Monsalve Salazar -- .''`. Debian GNU/Linux : :' : Free

Bug#334001: marked as done (Importing vte in python doesn't work)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Nov 2005 14:33:31 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#334001: fixed in vte 1:0.11.15-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

Bug#334001: marked as done (Importing vte in python doesn't work)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Nov 2005 14:33:31 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#334668: fixed in vte 1:0.11.15-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

Bug#338090: marked as done (Broken python binding)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Nov 2005 14:33:31 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#334001: fixed in vte 1:0.11.15-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

Bug#338090: marked as done (Broken python binding)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Nov 2005 14:33:31 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#334668: fixed in vte 1:0.11.15-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

Bug#337469: marked as done (xsupplicant: FTBFS with openssl 0.9.8: RC4_KEY undeclared)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Nov 2005 14:33:36 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#337469: fixed in xsupplicant 1.0.1-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#338090: marked as done (Broken python binding)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Nov 2005 14:33:31 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#338090: fixed in vte 1:0.11.15-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

Bug#334001: marked as done (Importing vte in python doesn't work)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Nov 2005 14:33:31 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#338090: fixed in vte 1:0.11.15-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

Bug#338220: marked as done (asterisk_1:1.0.9.dfsg-6_mips: FTBFS: internal compiler error: Floating point exception)

2005-11-08 Thread Debian Bug Tracking System
-Transfer-Encoding: quoted-printable Package: asterisk Severity: serious Version: 1:1.0.9.dfsg-6 Tags: sid Justification: fails to build from source There was an error while trying to autobuild your package: Automatic build of asterisk_1:1.0.9.dfsg-6 on ball by sbuild/mips 69 Build started at 20051108

Bug#330983: asterisk: Building chan_zap.so (and five other modules) requires zaptel.h at the wrong place

2005-11-08 Thread Mark Purcell
On Tuesday 08 November 2005 10:04, Christoph Biedl wrote: [...] I have been told the package was uploaded by the maintainer, not build on the Debian buildds. Which would also explain the bug report. [...] This is not for the i386 architecture. I admit that this build log looks fine for alpha

Bug#338243: vrms: uses diagnostics.pm, needs to depend on perl

2005-11-08 Thread Lars Wirzenius
Package: vrms Version: 1.10 Severity: serious Justification: package is uninstallable (unless you happen to have perl) vrms has no explicit dependencies, but it seems it tries to use the module diagnostics.pm, which is not included perl-base, so a dependency on perl would seem to be in order (or

Bug#320851: marked as done (usr/lib/gs-esp/8.15/X11.so: Shared library is not PIC)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Nov 2005 15:32:10 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#323688: fixed in gs-esp 8.15.1.dfsg.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

Bug#323688: marked as done (gs-esp: FTBFS: Not using -fPIC to build shared lib.)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Nov 2005 15:32:10 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#323688: fixed in gs-esp 8.15.1.dfsg.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

Bug#320851: marked as done (usr/lib/gs-esp/8.15/X11.so: Shared library is not PIC)

2005-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Nov 2005 15:32:10 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#320851: fixed in gs-esp 8.15.1.dfsg.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

Bug#338253: wims-common: postinst doesn't check errors, assumes wims user, and purge leaves cruft

2005-11-08 Thread Lars Wirzenius
Package: wims-common Version: 3.28-6.1 Severity: serious Justification: violates a must in policy When testing wims-common with piuparts, I see several problems. To begin with, it assumes that the wims user and group exists and is dedicated for its use, yet does not even try to create the user.

Bug#338255: wzdftpd: missing ucf dependency breaks upgrade from sarge

2005-11-08 Thread Lars Wirzenius
Package: wzdftpd Version: 0.5.5-3 Severity: serious Justification: breaks upgrades wzdftpd has one use of ucf in its maintainer scripts (postinst), so it should have a dependency on ucf. This comes up when testing upgrades from sarge to etch to sid (with piuparts), although the test only gets to

Bug#336373: subversion: svn MKCOL ssl error

2005-11-08 Thread Peter Samuelson
[Peter Samuelson] Oh, doh! /usr/bin/svn will not use libneon25, so that accomplished nothing. I'll build a new set of packages that use libneon25 instead Well, now I see why Debian ships both neon24 and neon25. subversion won't yet compile against neon25, and I don't have the time or

Bug#337047: gobby segfaults on the second running for me too.

2005-11-08 Thread Helen Faulkner
Package: gobby Version: 0.2.2-2 Followup-For: Bug #337047 Hi, I am also getting this bug. I ran gobby once the other day, and it worked fine. But now it segfaults. What information can I provide that might help? (Please give me specific instructions - I'm not very experienced with tracing

Bug#338113: fwbuilder: FTBFS: needs new version of libfwbuilder

2005-11-08 Thread Steve Langasek
On Tue, Nov 08, 2005 at 11:20:35AM -0800, Jeremy T. Bouse wrote: Please tell me you're not wasting my time with this while I'm working to get 2.0.9 packaged? Of course fwbuilder 2.0.7 is going to fail to build when I uploade 2.0.9 libfwbuilder. I have to get libfwbuilder into the mirror

Bug#338185: stay on 2.6.12 for now

2005-11-08 Thread Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 retitle 338185 ia64 has problems footprinting initramfs thanks ia64 users shouldn't upgrade to 2.6.14 yet - the ia64 kernel currently has problems footprinting initramfs, which means it can't work with either yaird or initramfs-tools. Monitor

Processed: Re: Bug#338185: stay on 2.6.12 for now

2005-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: retitle 338185 ia64 has problems footprinting initramfs Bug#338185: stay on 2.6.12 for now Changed Bug title. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian

Bug#332617: Services_Weather and the PHP License

2005-11-08 Thread Charles Fry
Hi, As you may already be aware, a Debian package of your PEAR Services_Weather module has been created for distribution as a part of Debian (and thereafter all of its derivatives). Unfortunately, it was discovered that the PHP License under which Services_Weather is released is problematic for

Bug#332618: XML_Parser and the PHP License

2005-11-08 Thread Charles Fry
Hi, As you may already be aware, a Debian package of your PEAR XML_Parser module has been created for distribution as a part of Debian (and thereafter all of its derivatives). Unfortunately, it was discovered that the PHP License under which XML_Parser is released is problematic for software

Bug#332608: DB and the PHP License

2005-11-08 Thread Charles Fry
Hi, As you may already be aware, a Debian package of your PEAR DB module has been created for distribution as a part of Debian (and thereafter all of its derivatives). Unfortunately, it was discovered that the PHP License under which DB is released is problematic for software other than PHP

Bug#332611: HTTP and the PHP License

2005-11-08 Thread Charles Fry
Hi, As you may already be aware, a Debian package of your PEAR HTTP module has been created for distribution as a part of Debian (and thereafter all of its derivatives). Unfortunately, it was discovered that the PHP License under which HTTP is released is problematic for software other than PHP

Bug#332613: Mail and the PHP License

2005-11-08 Thread Charles Fry
Hi, As you may already be aware, a Debian package of your PEAR Mail module has been created for distribution as a part of Debian (and thereafter all of its derivatives). Unfortunately, it was discovered that the PHP License under which Mail is released is problematic for software other than PHP

Bug#332609: File and the PHP License

2005-11-08 Thread Charles Fry
Hi, As you may already be aware, a Debian package of your PEAR File module has been created for distribution as a part of Debian (and thereafter all of its derivatives). Unfortunately, it was discovered that the PHP License under which File is released is problematic for software other than PHP

Bug#332616: Net_Socket and the PHP License

2005-11-08 Thread Charles Fry
Hi, As you may already be aware, a Debian package of your PEAR Net_Socket module has been created for distribution as a part of Debian (and thereafter all of its derivatives). Unfortunately, it was discovered that the PHP License under which Net_Socket is released is problematic for software

  1   2   >