Bug#327023: marked as done (openalpp-cvs: FTBFS: invalid conversion from 'ALubyte*' to 'const ALchar*')

Your message dated Wed, 7 Sep 2005 08:25:52 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#327023: Duplicate report, sorry 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#285577: marked as done (blender: FTBFS (amd64/gcc-4.0): cast from 'void*' to 'unsigned int' loses precision)

Your message dated Tue, 06 Sep 2005 23:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#285577: fixed in blender 2.37a-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#298167: marked as done (blender: please revert writing quit.blend with O_EXCL and make U.tempdir default to a userdir instead)

Your message dated Tue, 06 Sep 2005 23:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#298167: fixed in blender 2.37a-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#304567: marked as done (package does not include blenderplayer)

Your message dated Tue, 06 Sep 2005 23:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#304567: fixed in blender 2.37a-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#313676: marked as done (blender: [INTL:de] German PO file corrections)

Your message dated Tue, 06 Sep 2005 23:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#313676: fixed in blender 2.37a-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#316524: marked as done (Blender 2.37 released)

Your message dated Tue, 06 Sep 2005 23:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#316524: fixed in blender 2.37a-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#319307: marked as done (FTBFS: conflicting declarations of BPy_CurNurb_methods)

Your message dated Tue, 06 Sep 2005 23:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#319307: fixed in blender 2.37a-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#327015: marked as done (Ooops in sysfs_read_file)

Your message dated Wed, 7 Sep 2005 14:57:47 +0900 with message-id <[EMAIL PROTECTED]> and subject line Bug#327015: Ooops in sysfs_read_file has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#326978: marked as done (php5-mysql dependency)

Your message dated Tue, 6 Sep 2005 22:59:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line [php-maint] Bug#326978: php5-mysql 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 it i

Bug#326863: marked as done (fail2ban: wrong message)

Your message dated Wed, 7 Sep 2005 01:37:59 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#326863: fail2ban: wrong message 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#321940: marked as done (linux-2.6: [powerpc] per flavour archs should have asm-ppc64 symlink too.)

Your message dated Wed, 7 Sep 2005 07:21:24 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#321940: Still an issue? 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 respons

Bug#319681: marked as done (aspell-bn: Needs repackaging for latest aspell)

Your message dated Tue, 06 Sep 2005 21:32:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#319681: fixed in aspell-bn 0.60.0.01.1.1-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#288513: marked as done (Blender hangs on tooltip display)

Your message dated Wed, 07 Sep 2005 13:20:19 +0900 with message-id <[EMAIL PROTECTED]> and subject line (no subject) 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 reo

Bug#190590: marked as done (blender: missing dependency on libstdc++)

Your message dated Wed, 07 Sep 2005 13:27:22 +0900 with message-id <[EMAIL PROTECTED]> and subject line (no subject) 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 reo

Bug#208055: marked as done (blender dependencies)

Your message dated Wed, 07 Sep 2005 13:27:22 +0900 with message-id <[EMAIL PROTECTED]> and subject line (no subject) 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 reo

Bug#266755: marked as done (mozilla: tab position not retained on BACK)

Your message dated Wed, 7 Sep 2005 00:26:42 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#266755: Fixed in Deerpark 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 respo

Bug#324392: marked as done (gnome-peercast: FTBFS on 64 bit arches: conflicting types for int64_t)

Your message dated Tue, 06 Sep 2005 20:32:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#324392: fixed in gnome-peercast 0.4.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#229535: marked as done (hostap-source: /proc/net/wireless not updating)

Your message dated Wed, 07 Sep 2005 05:44:17 +0300 with message-id <[EMAIL PROTECTED]> and subject line hostap-source: /proc/net/wireless not updating 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#157604: marked as done (liblingua-ispell-perl: debian/copyright problems)

Your message dated Tue, 06 Sep 2005 19:17:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#157604: fixed in liblingua-ispell-perl 0.07-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#325619: marked as done (gnome-schedule: commented sections in .desktop file prevent it from appearing in GNOME menus)

Your message dated Tue, 06 Sep 2005 19:17:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325619: fixed in gnome-schedule 0.9.0-5 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#325624: marked as done (gnome-schedule: NEWS.gz is an empty file)

Your message dated Tue, 06 Sep 2005 19:17:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325624: fixed in gnome-schedule 0.9.0-5 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#289575: marked as done (devhelp-book-autotools: Old documentation)

Your message dated Tue, 06 Sep 2005 22:28:56 -0300 with message-id <[EMAIL PROTECTED]> and subject line devhelp-books 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 responsibili

Bug#326951: marked as done (libofx2: installation failed)

Your message dated Tue, 06 Sep 2005 17:47:47 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326951: libofx2: installation failed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

Bug#326895: marked as done (konversation: needs to depend on kdelibs4c2)

Your message dated Tue, 6 Sep 2005 20:58:13 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#326895: konversation: needs to depend on kdelibs4c2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#307358: marked as done (ITA: grace6 -- An XY plotting tool)

Your message dated Tue, 06 Sep 2005 16:47:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#307358: fixed in grace6 5.99.0+final-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

Bug#326944: marked as done (sed: manual page title is awkward)

Your message dated Tue, 06 Sep 2005 16:47:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326944: fixed in sed 4.1.4-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#326973: marked as done (gimp: unfamiliar directory chooser interface)

Your message dated Tue, 06 Sep 2005 19:20:45 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#326973: gimp: unfamiliar directory chooser interface 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 t

Bug#326953: marked as done (gimp: shortcuts require ALT always)

Your message dated Tue, 06 Sep 2005 19:26:21 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#326953: gimp: shortcuts require ALT always 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#326955: marked as done (gimp: close toolbox and all of gimp dies)

Your message dated Tue, 06 Sep 2005 19:27:32 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#326955: gimp: close toolbox and all of gimp dies 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

Bug#319844: marked as done (gfontview(GNU/k*BSD): FTBFS: out of date config.sub/config.guess)

Your message dated Tue, 06 Sep 2005 16:02:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#319844: fixed in gfontview 0.5.0-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#326638: marked as done (kdesvn: useless Build-Depends on build-essential)

Your message dated Tue, 06 Sep 2005 15:32:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326638: fixed in kdesvn 0.5.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 now you

Bug#323240: marked as done (ITP: viruskiller -- Game about viruses invading your computer)

Your message dated Tue, 06 Sep 2005 15:25:39 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323240: fixed in viruskiller 1.0-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 no

Bug#326682: marked as done (www.debian.org: Patches to make files in MailingLists valid HTML)

Your message dated Wed, 7 Sep 2005 00:21:23 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#326682: www.debian.org: Patches to make files in MailingLists valid HTML has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt wi

Bug#322943: marked as done (ITP: easyh10 -- generates databases for the iRiver H10 music player)

Your message dated Tue, 06 Sep 2005 15:14:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#322943: fixed in easyh10 1.0b6-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#318875: marked as done (udpkg: Should merge translations by default)

Your message dated Wed, 07 Sep 2005 00:29:22 +0200 with message-id <[EMAIL PROTECTED]> and subject line udpkg: Should merge translations by default 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#179775: marked as done (partimage-server: impossible to stop daemon from keyboard)

Your message dated Tue, 06 Sep 2005 15:17:15 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#179775: fixed in partimage 0.6.4-13 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#159715: marked as done (ITP: enca -- Extremely Naive Charset Analyser)

Your message dated Tue, 06 Sep 2005 15:21:19 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#159715: fixed in enca 1.7-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your re

Bug#304708: marked as done (evolution: clicking on "Tasks" causes crash on ia64)

Your message dated Tue, 06 Sep 2005 15:17:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#304708: fixed in evolution 2.2.3-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#304827: marked as done (evolution: Exchange protocol missing after updated package.)

Your message dated Tue, 06 Sep 2005 15:17:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#304827: fixed in evolution 2.2.3-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#314119: marked as done (evolution: [INTL:de] German PO file corrections)

Your message dated Tue, 06 Sep 2005 15:17:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#314119: fixed in evolution 2.2.3-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#320892: marked as done (64-bit regression)

Your message dated Tue, 06 Sep 2005 15:17:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#320892: fixed in evolution 2.2.3-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#326965: marked as done (amarok: Fails to build my collection)

Your message dated Wed, 7 Sep 2005 00:15:18 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#326965: amarok: Fails to build my collection 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 i

Bug#326807: marked as done (dh-make-perl: Check errors from the YAML module)

Your message dated Tue, 06 Sep 2005 15:02:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326807: fixed in dh-make-perl 0.19 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#326837: marked as done (leafnode: Unable to read config file after dpkg-reconfigure)

Your message dated Tue, 6 Sep 2005 22:56:01 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#326837: leafnode: Unable to read config file after dpkg-reconfigure has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#325415: marked as done (ITP: pida -- Python Integrated Development Application, a Python IDE.)

Your message dated Tue, 06 Sep 2005 14:48:56 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325415: fixed in pida 0.2.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 your

Bug#326937: marked as done (Can you compile kmymoney2 against libofx2 instead of libofx1c2 please ?)

Your message dated Tue, 06 Sep 2005 14:47:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326937: fixed in kmymoney2 0.8-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 yo

Bug#323143: marked as done (linux-2.6: CONFIG_ATM_CLIP should be configured as a module)

Your message dated Tue, 06 Sep 2005 14:17:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323143: fixed in linux-2.6 2.6.12-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#326946: marked as done (generates broken fetch script)

Your message dated Tue, 06 Sep 2005 14:02:03 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326946: fixed in apt-zip 0.13.4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#312386: marked as done (amarok: Collection keeps on being empty)

Your message dated Tue, 6 Sep 2005 23:11:48 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#312386: amarok: Collection is never built with upgraded 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

Bug#326562: marked as done (amarok: collection does not work with libsqlite3-0 >> 3.2.5)

Your message dated Tue, 6 Sep 2005 23:11:48 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#312386: amarok: Collection is never built with upgraded 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

Bug#303028: marked as done (yate: FTBFS (amd64/gcc-4.0): cast from 'MsgHolder*' to 'unsigned int' loses precision)

Your message dated Tue, 06 Sep 2005 13:47:41 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#303028: fixed in yate 0.8.7+cvs20050604-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#326588: marked as done (yate-openh323: uninstallable in sid: please rebuild for the C++ transition)

Your message dated Tue, 06 Sep 2005 13:47:41 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326588: fixed in yate 0.8.7+cvs20050604-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#326887: marked as done (yate-openh323: Several errors in package descriptions)

Your message dated Tue, 06 Sep 2005 13:47:41 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326887: fixed in yate 0.8.7+cvs20050604-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#326899: marked as done (shorewall: Providers file is missing)

Your message dated Tue, 06 Sep 2005 13:47:37 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326899: fixed in shorewall 2.4.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 now

Processed: Re: Bug#318094: marked as done (kwin: Xorg available in Sid, could we have kompmgr enabled ?)

Processing commands for [EMAIL PROTECTED]: > reopen 318094 Bug#318094: kwin: Xorg available in Sid, could we have kompmgr enabled ? Bug reopened, originator not changed. > close 318094 4:3.4.2-1 Bug#318094: kwin: Xorg available in Sid, could we have kompmgr enabled ? 'close' is deprecated; see ht

Bug#326070: marked as done (ncmpc: wrong charset in po/ru.po => unusable Russian translation)

Your message dated Tue, 06 Sep 2005 11:47:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326070: fixed in ncmpc 0.11.1-9 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#326910: marked as done (xlibmesa-glu-dev: libGLU.so is linking against old libstdc++.so.5)

Your message dated Tue, 6 Sep 2005 20:59:32 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#326910: xlibmesa-glu-dev: libGLU.so is linking against old libstdc++.so.5 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt w

Bug#318094: marked as done (kwin: Xorg available in Sid, could we have kompmgr enabled ?)

Your message dated Tue, 6 Sep 2005 14:33:55 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#318094: kwin: Xorg available in Sid, could we have kompmgr enabled ? has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with.

Bug#326920: marked as done (Endianess problem when running gtk programs over remote X)

Your message dated Tue, 06 Sep 2005 11:02:17 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326920: fixed in libcairo 1.0.0-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#325541: marked as done (register docs with docbase)

Your message dated Tue, 06 Sep 2005 11:02:17 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325541: fixed in libcairo 1.0.0-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#313571: marked as done (INTL:vi)

Your message dated Tue, 06 Sep 2005 10:47:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#313571: fixed in dput 0.9.2.20 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#309934: marked as done (dput: [manual] Explain what happend if HOST parameter is not passed on command line)

Your message dated Tue, 06 Sep 2005 10:47:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#309934: fixed in dput 0.9.2.20 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#309975: marked as done (dput: [manual] dput.cf and multiple same entries are not mentioned in manual)

Your message dated Tue, 06 Sep 2005 10:47:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#309975: fixed in dput 0.9.2.20 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#315824: marked as done ([l10n] Initial Czech translation of dput debconf messages)

Your message dated Tue, 06 Sep 2005 10:47:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#315824: fixed in dput 0.9.2.20 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#324183: marked as done (dcut: makes wrong decision for secret key - should use debsign)

Your message dated Tue, 06 Sep 2005 10:47:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#324183: fixed in dput 0.9.2.20 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#306644: marked as done (dput: passive_ftp description: "0" => "1")

Your message dated Tue, 06 Sep 2005 19:07:07 +0200 with message-id <[EMAIL PROTECTED]> and subject line Upon inspection there seems to be no bug. 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 n

Bug#283963: marked as done (hpoj spams lpr.log and syslog when printer is not connected)

Your message dated Tue, 6 Sep 2005 18:03:42 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#283963: More info requested 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 res

Bug#304147: marked as done (kiconedit: crashes with SIGSEGV on start-up)

Your message dated Tue, 6 Sep 2005 17:45:37 +0100 with message-id <[EMAIL PROTECTED]> and subject line Close 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#318829: marked as done (subscriptions are not exported ordered)

Your message dated Tue, 06 Sep 2005 11:32:49 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#318829: Unable to reproduce 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 re

Bug#326793: marked as done (ldap-haskell: FTBFS: installed-pkg-config: No such file or directory)

Your message dated Tue, 06 Sep 2005 09:17:03 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326793: fixed in ldap-haskell 0.5.0 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#213742: marked as done (libssl is not thread-safe)

Your message dated Tue, 06 Sep 2005 18:29:13 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug only present in woody 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 responsi

Bug#285421: marked as done (liferea: Can't disable use of proxy setting)

Your message dated Tue, 06 Sep 2005 11:15:07 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#285421: 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 t

Bug#326795: marked as done (magic-haskell: FTBFS: installed-pkg-config: No such file or directory)

Your message dated Tue, 06 Sep 2005 09:02:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326795: fixed in magic-haskell 1.0.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 no

Bug#322342: marked as done (xmms-coverviewer: should build against libid3-3.8.3c2 (?))

Your message dated Tue, 06 Sep 2005 08:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#322342: fixed in xmms-coverviewer 0.11-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 i

Bug#326377: marked as done (please rebuild with libreadline5-dev as build dependency)

Your message dated Tue, 06 Sep 2005 08:32:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326377: fixed in cl-readline 0.2.0-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 no

Bug#182907: marked as done (binary-all packages built in binary-arch rules target)

Your message dated Tue, 06 Sep 2005 17:41:51 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#182907: binary-all packages built in binary-arch rules target 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#318001: marked as done (libssl-dev depends on =0.9.7g-1, 0.9.7g-2 is current in sid)

Your message dated Tue, 06 Sep 2005 17:23:37 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#318001: versions in archive agree has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#310502: marked as done (package libssl-dev package dependency broken on stable)

Your message dated Tue, 06 Sep 2005 17:25:17 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#310502: package libssl-dev package dependency broken on 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 th

Bug#304969: marked as done (note: Add "Suggested" Encryption Packages?)

Your message dated Tue, 06 Sep 2005 08:17:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#304969: fixed in note 1.3.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#302974: marked as done (note: Improper copyright file)

Your message dated Tue, 06 Sep 2005 08:17:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#302974: fixed in note 1.3.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#263814: marked as done (sumika: FTBFS with gcc-3.4: conflicting types for 'sumika_get_c_string')

Your message dated Tue, 06 Sep 2005 09:25:31 -0600 with message-id <[EMAIL PROTECTED]> and subject line closing 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 t

Bug#228050: marked as done (note: New upstream version available)

Your message dated Tue, 06 Sep 2005 08:17:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#228050: fixed in note 1.3.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#326900: marked as done (kdelibs-data: Trying to overwrite a openoffice.org-mimelnk file)

Your message dated Tue, 6 Sep 2005 16:50:42 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#326900: kdelibs-data: Trying to overwrite a openoffice.org-mimelnk file has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt wit

Bug#322607: marked as done (SECURITY: HTTP proxy responses with both Transfer-Encoding and Content-Length headers (CAN-2005-2088))

Your message dated Tue, 06 Sep 2005 07:47:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#322607: fixed in apache 1.3.33-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 yo

Bug#321727: marked as done (hal: wrong mount options for pluggable flash storage devices)

Your message dated Tue, 06 Sep 2005 07:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#321727: fixed in hal 0.4.8-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 r

Bug#322358: marked as done (libhal-dev does not depend on libpopt-dev)

Your message dated Tue, 06 Sep 2005 07:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#322358: fixed in hal 0.4.8-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 r

Bug#307072: marked as done (ITA: libmkdoc-xml-perl -- MKDoc XML Toolkit)

Your message dated Tue, 06 Sep 2005 07:02:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#307072: fixed in libmkdoc-xml-perl 0.75-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#307073: marked as done (ITA: libpetal-perl -- Perl Template Attribute Language - TAL for perl)

Your message dated Tue, 06 Sep 2005 07:17:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#307073: fixed in libpetal-perl 2.16-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 n

Bug#325939: marked as done (depends on a FLAC library no longer available in unstable)

Your message dated Tue, 06 Sep 2005 07:32:03 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325939: fixed in gnusound 0.7.4-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 y

Bug#325535: marked as done (mozilla: FTBFS: change in behavior of __attribute__((unused)))

Your message dated Tue, 06 Sep 2005 07:17:17 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325535: fixed in mozilla-firefox 1.0.6-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it i

Bug#244070: marked as done (octave2.1-emacsen: octave quits when working with popen)

Your message dated Tue, 6 Sep 2005 15:19:38 +0200 with message-id <[EMAIL PROTECTED]> and subject line Fixed in sarge since a while -> closing this bug report has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Processed: Re: Bug#326628: where's the pcre?

Processing commands for [EMAIL PROTECTED]: > clone 326628 -1 Bug#326628: gnumeric: Gnumeric embeds copy of vulnerable PCRE code Bug 326628 cloned as bug 326898. > close -1 1.5 Bug#326898: gnumeric: Gnumeric embeds copy of vulnerable PCRE code 'close' is deprecated; see http://www.debian.org/Bugs/

Bug#322147: marked as done (bsdiff: README violates copyright)

Your message dated Tue, 06 Sep 2005 06:02:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#322147: fixed in bsdiff 4.2-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#322613: marked as done (Processed: Apache 1.3 also vulnerable?)

Your message dated Tue, 06 Sep 2005 23:10:36 +1000 with message-id <[EMAIL PROTECTED]> and subject line Not vulnerable 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 r

Bug#323411: marked as done (doxymacs indirectly depends on emacs21)

Your message dated Tue, 06 Sep 2005 05:47:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323411: fixed in doxymacs 1.6.0-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#326834: marked as done (robotour(GNU/k*BSD): FTBFS: out of date config.sub/config.guess)

Your message dated Tue, 06 Sep 2005 05:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326834: fixed in robotour 3.1.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 y

Bug#326844: marked as done (robotour: FTBFS: Missing Build-Depends on 'xlibmesa-gl-dev, libglu1-xorg-dev')

Your message dated Tue, 06 Sep 2005 05:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326844: fixed in robotour 3.1.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 y

Bug#326787: marked as done (kdebluetooth should be compiled against KDE 3.4.2 (kdelibs4c2 package))

Your message dated Tue, 06 Sep 2005 05:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326787: fixed in kdebluetooth 0.99+1.0beta1-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

Bug#326218: marked as done (Dependency on xmms)

Your message dated Tue, 06 Sep 2005 05:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326218: fixed in kdebluetooth 0.99+1.0beta1-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

Bug#246548: marked as done (eog: interpolation option doesn't work)

Your message dated Tue, 6 Sep 2005 13:54:52 +0200 with message-id <[EMAIL PROTECTED]> and subject line eog: interpolation option doesn't work has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

  1   2   >