Bug#430047: debtags: symbol lookup error: /usr/lib/libept.so.0: undefined symbol: _ZN6Xapian13ExpandDeciderD2Ev

reassign 430047 libept0 forcemerge 430719 430047 thanks This bug was tracked down to libept0, and has been fixed in the most recent version. Merging with #430719. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it

Bug#429174: Japanese speaker needed for bug #429174/mecab

On Tue, Jul 03, 2007 at 12:12:09AM +0200, Moritz Muehlenhoff [EMAIL PROTECTED] wrote: If someone is able to read Japanese, please look into Bug 429174 for mecab and provide the necessary information what this issue is all about in the bug log. The only security item in the changelog is a

Processed: Re: debtags: symbol lookup error: /usr/lib/libept.so.0: undefined symbol: _ZN6Xapian13ExpandDeciderD2Ev

Processing commands for [EMAIL PROTECTED]: reassign 430047 libept0 Bug#430047: debtags: symbol lookup error: /usr/lib/libept.so.0: undefined symbol: _ZN6Xapian13ExpandDeciderD2Ev Bug reassigned from package `debtags' to `libept0'. forcemerge 430719 430047 Bug#430719: libept0: missing

Bug#430755: closed by Christian Perrier [EMAIL PROTECTED] (Bug#430755: fixed in samba 3.0.25b-1)

Quoting Steve Langasek ([EMAIL PROTECTED]): On Tue, Jul 03, 2007 at 01:39:21PM +1200, Centurion Computer Technology (2005) Ltd wrote: This bug still effects the current lenny version (3.0.25a2) Thanks for the reminder; I'll bump samba 3.0.25b into lenny with the next run. Well, I

Processed: tagging 423788, tagging 423455, tagging 424505, tagging 422661, tagging 423797, tagging 427312 ... ... ...

Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.4 tags 423788 lenny sid Bug#423788: FTBFS: checking for mxDateTime.h... configure: error: can't build without mx headers There were no tags set. Tags added: lenny, sid tags 423455

Bug#430755: closed by Christian Perrier [EMAIL PROTECTED] (Bug#430755: fixed in samba 3.0.25b-1)

On Tue, Jul 03, 2007 at 07:34:38AM +0200, Christian Perrier wrote: Quoting Steve Langasek ([EMAIL PROTECTED]): On Tue, Jul 03, 2007 at 01:39:21PM +1200, Centurion Computer Technology (2005) Ltd wrote: This bug still effects the current lenny version (3.0.25a2) Thanks for the reminder;

Processed: tagging 425213, tagging 421985, tagging 425919, tagging 419965, tagging 425921, tagging 420125 ... ... ... ... ... ...

Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.4 tags 425213 lenny sid Bug#425213: phpunit2: merging phpunit and phpunit2 Tags were: confirmed patch pending Tags added: lenny, sid tags 421985 lenny sid Bug#421985: FTBFS:

Processed: Re: FTBFS (alpha): libtool: link: cannot find the library `/usr/local/lib/libstdc++.la'

Processing commands for [EMAIL PROTECTED]: reopen 410565 Bug#410565: FTBFS (alpha): libtool: link: cannot find the library `/usr/local/lib/libstdc++.la' 'reopen' may be inappropriate when a bug has been closed with a version; you may need to use 'found' to remove fixed versions. Bug reopened,

Bug#410565: FTBFS (alpha): libtool: link: cannot find the library `/usr/local/lib/libstdc++.la'

reopen 410565 close 410565 quit This was never a sourceful bug in bmpx, and you made no changes in your package that addressed this bug. Please don't close bugs in your changelog that you haven't actually fixed -- the correct action here is an unversioned bug closure. The real bug here was a

Processed: tagging 422585, tagging 426012, tagging 424026, tagging 427316, tagging 429001, tagging 427201 ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...

Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.4 tags 422585 lenny sid Bug#422585: FTBFS: Numeric/arrayobject.h: No such file or directory There were no tags set. Tags added: lenny, sid tags 426012 sid Bug#426012: python-scipy:

Processed: tagging 424449, tagging 428997, tagging 402165, tagging 427308, tagging 422825, tagging 423962 ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...

Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.4 tags 424449 lenny sid Bug#424449: spfmilter - FTBFS: spfmilter.c:1261: undefined reference to `smfi_getpriv' Tags were: confirmed Tags added: lenny, sid tags 428997 lenny sid

Bug#430805: The problem is caused by Image::LibRSVG-isGzCompressionSupported

On Wed, Jun 27, 2007 at 12:03:20PM -0500, Gunnar Wolf wrote: ...I reproduced it - the problem is that $rsvg-loadImage with a svg.gz triggers a segfault, and all the tests from that point on don't get executed at all. Just to illustrate, from the source tree, just after the build died (hence

Bug#431510: missing dependency on adduser

Package: incron Version: 0.5.5-1 Severity: serious hi, while doing a archive wide piuparts run your package failed to install due to a missing dependency on adduser: Setting up incron (0.5.5-1) ... /var/lib/dpkg/info/incron.postinst: line 10: addgroup: command not found dpkg: error

Bug#431509: depends on non-essential package adduser in postrm

Package: icecc Version: 0.8.0-1 Severity: serious Tags: etch-ignore Usertags: postrm-depends-nonessential Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of adduser beeing unavailable during postrm: Removing

Bug#431511: depends on non-essential package adduser in postrm

Package: armagetronad-dedicated Version: 0.2.8.2.1-4 Severity: serious Usertags: postrm-depends-nonessential Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of adduser beeing unavailable during postrm:

Bug#431516: depends on non-essential package adduser in postrm

Package: greylistd Version: 0.8.3.5 Severity: serious Usertags: postrm-depends-nonessential User: [EMAIL PROTECTED] Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of adduser beeing unavailable during postrm:

Bug#431517: depends on non-essential package ucf in postrm

Package: nbd-server Version: 1:2.9.4-1 Severity: serious Usertags: postrm-depends-nonessential User: [EMAIL PROTECTED] Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of ucf beeing unavailable during postrm:

Bug#431514: depends on non-essential package adduser in postrm

Package: freewnn-cserver Version: 1.1.0+1.1.1-a021-1.1 Severity: serious Usertags: postrm-depends-nonessential User: [EMAIL PROTECTED] Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of adduser beeing unavailable

Bug#431518: depends on non-essential package ucf in postrm

Package: boxbackup-client Version: 0.10+chrismerge+r1706-1 Severity: serious Usertags: postrm-depends-nonessential User: [EMAIL PROTECTED] Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of ucf beeing unavailable

Bug#431520: depends on non-essential package ucf in postrm

Package: diogenes Version: 0.9.20-1.1 Severity: serious Usertags: postrm-depends-nonessential User: [EMAIL PROTECTED] Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of ucf beeing unavailable during postrm:

Bug#431522: depends on non-essential package ucf in postrm

Package: localepurge Version: 0.5.9 Severity: serious Usertags: postrm-depends-nonessential User: [EMAIL PROTECTED] Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of ucf beeing unavailable during postrm:

Bug#431519: depends on non-essential package ucf in postrm

Package: boxbackup-server Version: 0.10+chrismerge+r1706-1 Severity: serious Usertags: postrm-depends-nonessential User: [EMAIL PROTECTED] Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of ucf beeing unavailable

Bug#431521: depends on non-essential package ucf in postrm

Package: flyspray Version: 0.9.8-12 Severity: serious Usertags: postrm-depends-nonessential User: [EMAIL PROTECTED] Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of ucf beeing unavailable during postrm:

Bug#431523: depends on non-essential package ucf in postrm

Package: nagios-common Version: 2:1.4-3.1 Severity: serious Usertags: postrm-depends-nonessential User: [EMAIL PROTECTED] Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of ucf beeing unavailable during postrm:

Bug#431524: depends on non-essential package ucf in postrm

Package: python-poker-network Version: 1.0.37-1.1 Severity: serious Usertags: postrm-depends-nonessential User: [EMAIL PROTECTED] Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of ucf beeing unavailable during

Bug#431515: depends on non-essential package adduser in postrm

Package: freewnn-jserver Version: 1.1.0+1.1.1-a021-1.1 Severity: serious Usertags: postrm-depends-nonessential User: [EMAIL PROTECTED] Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of adduser beeing unavailable

Bug#431513: depends on non-essential package adduser in postrm

Package: crywrap Version: 0.2.1-4.2 Severity: serious Usertags: postrm-depends-nonessential User: [EMAIL PROTECTED] Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of adduser beeing unavailable during postrm:

Bug#423962: marked as done (tcm: FTBFS: /usr/include/X11/VendorP.h:87: error: previous declaration of 'VendorShellClassRec vendorShellClassRec' with 'C++' linkage)

Your message dated Tue, 3 Jul 2007 10:19:28 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#423962: tcm: FTBFS: /usr/include/X11/VendorP.h:87: error: previous declaration of 'VendorShellClassRec vendorShellClassRec' with 'C++' linkage has caused the attached Bug report to be marked

Bug#431525: depends on non-essential package update-inetd in postrm

Package: uw-imapd Version: 7:2002edebian1-13.2 Severity: serious User: [EMAIL PROTECTED] Usertags: postrm-depends-nonessential Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of update-inetd beeing unavailable

Bug#431526: depends on non-essential package update-inetd in postrm

Package: gnats Version: 4.1.0-0.2 Severity: serious User: [EMAIL PROTECTED] Usertags: postrm-depends-nonessential Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of update-inetd beeing unavailable during postrm:

Bug#431527: depends on non-essential package update-inetd in postrm

Package: ipopd Version: 7:2002edebian1-13.2 Severity: serious User: [EMAIL PROTECTED] Usertags: postrm-depends-nonessential Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of update-inetd beeing unavailable

Bug#431531: depends on non-essential package wwwconfig-common in postrm

Package: opendb Version: 0.81p20-1.1 Severity: serious Usertags: postrm-depends-nonessential User: [EMAIL PROTECTED] Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of wwwconfig-common beeing unavailable during

Bug#431529: missing dependency on adduser

Package: memlockd Version: 0.03 Severity: serious Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on install because of adduser beeing unavailable during postrm: Setting up memlockd (0.03) ...

Bug#431530: depends on non-essential package adduser in postrm

Package: munge Version: 0.5.8-4 Severity: serious Usertags: postrm-depends-nonessential User: [EMAIL PROTECTED] Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of adduser beeing unavailable during postrm:

Bug#431528: depends on non-essential package adduser in postrm

Package: lyskom-server Version: 2.1.2-6 Severity: serious Usertags: postrm-depends-nonessential User: [EMAIL PROTECTED] Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of adduser beeing unavailable during postrm:

Bug#431532: depends on non-essential package adduser in postrm

Package: tinyerp-server Version: 4.0.3-1 Severity: serious Usertags: postrm-depends-nonessential User: [EMAIL PROTECTED] Justification: Policy violation, see section 7.2 hi, while running archive wide piuparts tests your package failed on purge because of adduser beeing unavailable during

Processed: Re: Bug#431104: libgsf-1-114: Bug in libgsf : segfault.

Processing commands for [EMAIL PROTECTED]: severity 431104 serious Bug#431104: libgsf-1-114: Bug in libgsf : segfault. Severity set to `serious' from `important' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator

Bug#431532: marked as done (depends on non-essential package adduser in postrm)

Your message dated Tue, 03 Jul 2007 09:17:03 + with message-id [EMAIL PROTECTED] and subject line Bug#431532: fixed in tinyerp-server 4.0.3-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

Bug#431481: marked as done (git-gui: Missing a replace for the moved tcl files)

Your message dated Tue, 03 Jul 2007 09:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#431481: fixed in git-core 1:1.5.2.3-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Processed: Remove plus sign from versions

Processing commands for [EMAIL PROTECTED]: notfound 430785 +1.6.dfsg.1-4 Bug#430785: CVE-2007-2798: kadmind vulnerable to buffer overflow Bug marked as not found in version +1.6.dfsg.1-4. (By the way, this Bug is currently marked as done.) notfound 430785 +1.4.4-7etch1 Bug#430785:

Bug#431541: license does not permit modification

Package: tct Version: 1.11-6.3 Severity: serious Redistribution and use in source and binary forms are permitted provided that this entire copyright notice is duplicated in all such copies. Doesn't say anywhere that modification is permitted. Since there are a few

Bug#431530: depends on non-essential package adduser in postrm

Thanks for the information, bug will be solved in the next release. -- Gennaro Oliva -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#431519: marked as done (depends on non-essential package ucf in postrm)

Your message dated Tue, 03 Jul 2007 11:17:02 + with message-id [EMAIL PROTECTED] and subject line Bug#431519: fixed in boxbackup 0.10+really0.10-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#431518: marked as done (depends on non-essential package ucf in postrm)

Your message dated Tue, 03 Jul 2007 11:17:02 + with message-id [EMAIL PROTECTED] and subject line Bug#431518: fixed in boxbackup 0.10+really0.10-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Processed: 431010

Processing commands for [EMAIL PROTECTED]: package cryptcat Ignoring bugs not assigned to: cryptcat tags 431010 lenny sid Bug#431010: cryptcat: segfault in listen mode There were no tags set. Tags added: lenny, sid thanks Stopping processing here. Please contact me if you need assistance.

Bug#431541: timeout.c

Actually, just rewrote it. I also added a useful feature the original doesn't have (--status). -- Robert Millan /* * timeout.c -- run commands with a specified timeout * Copyright (C) 2007 Robert Millan [EMAIL PROTECTED] * * GRUB is free software; you can redistribute it and/or modify

Bug#431541: timeout is already free according to author

Hi, Doesn't say anywhere that modification is permitted. Since there are a few packages that depend on timeout, and this program is in fact very small, I'd gladly provide a rewrite if needed. secvpn,timeout podracer,timeout netatalk,timeout gnokii,timeout Actually for another

Bug#430833: [Pkg-alsa-devel] Bug#430833: sweep problem due to libasound2.

Hi, I noticed that the sweep problem is caused by libasound2 error. What's the status of libasound2 update? Waiting for upload [1] Elimar [1] http://svn.debian.org/wsvn/pkg-alsa/trunk/alsa-lib/debian/changelog?op=filerev=0sc=1 I thought we're kind of trying to get this package

Bug#431510: marked as done (missing dependency on adduser)

Your message dated Tue, 03 Jul 2007 12:47:07 + with message-id [EMAIL PROTECTED] and subject line Bug#431510: fixed in incron 0.5.5-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Processed: FTBFS/uninstallable is RC

Processing commands for [EMAIL PROTECTED]: severity 427806 serious Bug#427806: referencer: Uninstallable in unstable (needs poppler patch/recompile) Severity set to `serious' from `important' -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system

Bug#422605: marked as done (FTBFS: debian/make-libnbio.sh: line 78: /usr/bin/gcjh: No such file or directory)

Your message dated Tue, 3 Jul 2007 16:08:29 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#423325: marked as done (libapache2-mod-ifier: should this package be removed?)

Your message dated Tue, 3 Jul 2007 16:10:51 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#423333: marked as done (libnewt-perl: should this package be removed?)

Your message dated Tue, 3 Jul 2007 16:08:00 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#423328: marked as done (libnet-ftpserver-perl: should this package be removed?)

Your message dated Tue, 3 Jul 2007 16:08:48 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#398936: marked as done (libapache2-mod-ifier: The module breaks POST processing)

Your message dated Tue, 3 Jul 2007 16:10:51 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#429091: marked as done (please update/request removal of your package)

Your message dated Tue, 3 Jul 2007 16:11:47 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#382849: marked as done (RC bug filed to keep mlmmjadmd out of testing for the time being)

Your message dated Tue, 3 Jul 2007 16:21:51 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#414292: marked as done (list: postinst failure because of improper group creation)

Your message dated Tue, 3 Jul 2007 16:17:50 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#418285: marked as done (f-prot-installer: Update failed: No such directory `pub/linux'.)

Your message dated Tue, 3 Jul 2007 16:17:18 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#423347: marked as done (mozilla-locale-lt: should this package be removed?)

Your message dated Tue, 3 Jul 2007 16:26:50 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#420684: marked as done (BIND 8 not suitable for release in Lenny)

Your message dated Tue, 3 Jul 2007 16:22:20 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#401425: marked as done (obsolete package)

Your message dated Tue, 3 Jul 2007 16:16:32 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#395917: marked as done (babygimp doesn't start)

Your message dated Tue, 3 Jul 2007 16:16:50 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#423346: marked as done (mozilla-locale-ko: should this package be removed?)

Your message dated Tue, 3 Jul 2007 16:26:50 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#395918: marked as done (babygimp: apparently doesn't work with current version of perl-tk)

Your message dated Tue, 3 Jul 2007 16:16:50 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#396095: marked as done (Source package contains non-free IETF RFC)

Your message dated Tue, 3 Jul 2007 16:25:48 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#405478: marked as done (lukemftp has been replaced by tnftp)

Your message dated Tue, 3 Jul 2007 16:23:53 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#413901: marked as done (SORRY [...] Please uninstall the LiSt client.)

Your message dated Tue, 3 Jul 2007 16:17:50 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#408135: marked as done (f-prot-installer: ftp.f-prot.com no longer available -- installation fails)

Your message dated Tue, 3 Jul 2007 16:17:18 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#411469: marked as done (f-prot-installer: virus updates not longer downloadable; deb package available)

Your message dated Tue, 3 Jul 2007 16:17:18 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#333915: marked as done (Unsatisfiable build dep on librrd0-dev)

Your message dated Tue, 3 Jul 2007 16:29:42 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#422658: marked as done (FTBFS: ../src/drip.h:198: error: previous declaration of 'drip_config Config' with 'C++' linkage)

Your message dated Tue, 3 Jul 2007 16:18:14 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#321944: marked as done (nagat: doesn't support cfg_dir)

Your message dated Tue, 3 Jul 2007 16:15:55 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#388209: marked as done (daemon binary missing on !i386)

Your message dated Tue, 3 Jul 2007 16:29:42 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#427249: marked as done (libsasl2-krb4-mit: depends on removed dummy package libsasl2)

Your message dated Tue, 3 Jul 2007 16:25:48 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#341172: marked as done (Please port to the experimental pilot-link 0.12 API)

Your message dated Tue, 03 Jul 2007 16:30:37 +0200 with message-id [EMAIL PROTECTED] and subject line evolution has long been ported to the pilot-link 0.12 API has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#431367: marked as done (aptitude waste 4min to return an answer)

Your message dated Tue, 03 Jul 2007 06:51:22 -0700 with message-id [EMAIL PROTECTED] and subject line Fixed in experimental 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

Bug#423345: marked as done (mozilla-locale-ja: should this package be removed?)

Your message dated Tue, 3 Jul 2007 16:26:50 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#431123: marked as done (aptitude: Initializing package states takes very much longer than before +b1)

Your message dated Tue, 03 Jul 2007 06:51:22 -0700 with message-id [EMAIL PROTECTED] and subject line Fixed in experimental 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

Bug#385883: marked as done (orca: needs to be ported to the current tinysnmp API)

Your message dated Tue, 3 Jul 2007 16:29:42 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#303672: marked as done (orca: build-depends on tinysnmp-manager-dev, which is not in testing)

Your message dated Tue, 3 Jul 2007 16:29:42 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#391417: marked as done (exscalibar shouldn't enter tetsing)

Your message dated Tue, 3 Jul 2007 16:29:22 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#431407: marked as done (aptitude: since upgrade to 0.4.4-4+b1 (together with apt 0.7) loading cache is horrible slow)

Your message dated Tue, 03 Jul 2007 06:51:22 -0700 with message-id [EMAIL PROTECTED] and subject line Fixed in experimental 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

Bug#423343: marked as done (mozilla-locale-eu: should this package be removed?)

Your message dated Tue, 3 Jul 2007 16:26:50 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#381034: marked as done (orca: Missing dependency librrd0)

Your message dated Tue, 3 Jul 2007 16:29:42 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#424832: marked as done (nagat: affected by php4-removal)

Your message dated Tue, 3 Jul 2007 16:15:55 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Processed: fixing versioning

Processing commands for [EMAIL PROTECTED]: reassign 417656 evolution-data-server Bug#417656: evolution: Crashes when run Bug reassigned from package `evolution' to `evolution-data-server'. found 417656 evolution-data-server/1.8.2-2 Bug#417656: evolution: Crashes when run Bug marked as found in

Bug#417656: fixing versioning

reassign 417656 evolution-data-server found 417656 evolution-data-server/1.8.2-2 close 417656 1.8.2-3 thanks Heya, The versioning information for this bug was broken, so I'm fixing it now :) Marc -- Fachbegriffe der Informatik - Einfach erklärt 134: Benutzerfreundlichkeit Der Benutzer

Bug#425066: NMU uploaded

Hi, I uploaded an NMU of your package. Please see this as help to get the package into a releaseable condition again. Please find the used diff below. Cheers, Andi diff -u abiword-2.4.6/debian/changelog abiword-2.4.6/debian/changelog --- abiword-2.4.6/debian/changelog +++

Bug#425066: marked as done (abiword: FTBFS with new libpoppler)

Your message dated Tue, 03 Jul 2007 15:02:56 + with message-id [EMAIL PROTECTED] and subject line Bug#425066: fixed in abiword 2.4.6-2.1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#431572: openoffice.org: Ooo crashed when i try to sort a sheet

Package: openoffice.org Version: 2.2.1-4 Severity: critical Justification: breaks unrelated software soffice *** glibc detected *** /usr/lib/openoffice/program/soffice.bin: double free or corruption (out): 0x08585ba0 *** === Backtrace: = /lib/libc.so.6[0xb6cc0b74]

Bug#422395: lilypond: FTBFS: ! I can't find file `lcircle10'.

tag 422395 patch thanks On Sat, May 05, 2007 at 05:35:59PM +0200, Lucas Nussbaum wrote: Package: lilypond Version: 2.8.7-3 Severity: serious Justification: FTBFS on i386, very likely to fail everywhere else User: [EMAIL PROTECTED] Usertags: builddep-tetex-ftbfs Hi, During a rebuild of

Processed: Re: Bug#422395: lilypond: FTBFS: ! I can't find file `lcircle10'.

Processing commands for [EMAIL PROTECTED]: tag 422395 patch Bug#422395: lilypond: FTBFS: ! I can't find file `lcircle10'. Tags were: sid lenny Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator,

Bug#431123: aptitude: Initializing package states takes very much longer than before +b1

On Mon, Jul 02, 2007 at 10:00:53PM -0700, Nathaniel Smith [EMAIL PROTECTED] was heard to say: On Sun, Jul 01, 2007 at 06:12:11PM -0700, Daniel Burrows wrote: Does installing the version in experimental fix the problem for you? Yes, the aptitude in experimental (0.4.4-5~2, which appears to

Bug#431572: openoffice.org: Ooo crashed when i try to sort a sheet

severity 431572 important thanks Michael Ott wrote: Package: openoffice.org Version: 2.2.1-4 Severity: critical Justification: breaks unrelated software Suure. Which unrelated software? OpenOffice.org breaking itself? This is ridiculous. Neither does it fullfill the breaks the whole system

Processed: Re: Bug#431090: libnetaddr-ip-perl: Includes non-free RFC documentation

Processing commands for [EMAIL PROTECTED]: tags 431090 + upstream Bug#431090: libnetaddr-ip-perl: Includes non-free RFC documentation There were no tags set. Tags added: upstream thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system

Bug#421566: marked as done (vdrift: wrong architecture limitations in debian/control (alpha))

Your message dated Tue, 3 Jul 2007 17:33:36 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#431090: libnetaddr-ip-perl: Includes non-free RFC documentation

tags 431090 + upstream thanks Reported as upstream bug #27941 in the CPAN RT: http://rt.cpan.org/Ticket/Display.html?id=27941 Damyan Ivanov dijo [Mon, Jul 02, 2007 at 11:35:10AM +0300]: This package's orig.tar.gz includes NetAddr-IP-4.007/docs/rfc1884.txt, which is non-free Isn't this

Bug#422837: marked as done (gst-plugins0.8: FTBFS: error: expected specifier-qualifier-list before 'WavpackStream')

Your message dated Tue, 3 Jul 2007 17:35:42 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#415050: marked as done (thinkpad-source: Undefined symbols inter_module_register and inter_module_unregister in 2.6.18)

Your message dated Tue, 3 Jul 2007 17:36:20 +0200 with message-id [EMAIL PROTECTED] and subject line Removed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

  1   2   >