Bug#326006: marked as done (kde-i18n: FTBFS: Missing Build-Depends on 'bzip2')

Your message dated Thu, 01 Sep 2005 23:32:39 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326006: fixed in kde-i18n 4:3.4.2-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#326082: marked as done (ipw2200-source: fail at compiling ipw2200 modules)

Your message dated Thu, 01 Sep 2005 23:17:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326082: fixed in ipw2200 1.0.6-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 yo

Bug#325559: marked as done (ipw2200-source: Add notice to readme about need to build ieee80211 before using m-a)

Your message dated Thu, 01 Sep 2005 23:17:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325559: fixed in ipw2200 1.0.6-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 yo

Bug#325523: marked as done (ipw2200: modules don't build with kernel 2.6.13)

Your message dated Thu, 01 Sep 2005 23:17:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325523: fixed in ipw2200 1.0.6-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 yo

Bug#323695: marked as done (ipw2200-source: change suggested firmware location to /lib/firmware)

Your message dated Thu, 01 Sep 2005 23:17:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323695: fixed in ipw2200 1.0.6-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 yo

Bug#326145: marked as done (ipw2200: [INTL:de] Translation po)

Your message dated Thu, 01 Sep 2005 23:17:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326145: fixed in ipw2200 1.0.6-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 yo

Bug#326160: marked as done (exim4: Warn when list processing stops)

Your message dated Fri, 2 Sep 2005 16:09:08 +1000 with message-id <[EMAIL PROTECTED]> and subject line Bug#326160: exim4: Warn when list processing stops 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#323531: marked as done ('man knocker' typo: "AVAILABILTY")

Your message dated Thu, 01 Sep 2005 23:02:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323531: fixed in knocker 0.7.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 yo

Bug#264548: marked as done (-nc and --no-colors doesn't works)

Your message dated Thu, 01 Sep 2005 23:02:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#264548: fixed in knocker 0.7.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 yo

Bug#323995: marked as done (knocker: /bin/)

Your message dated Thu, 01 Sep 2005 23:02:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323995: fixed in knocker 0.7.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 yo

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

Your message dated Thu, 01 Sep 2005 22:47:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325954: fixed in scummvm 0.7.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 yo

Bug#308158: marked as done (gallery: find_orphan.php does not work)

Your message dated Thu, 1 Sep 2005 22:35:41 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#308158: gallery: find_orphan.php does not 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

Bug#326118: marked as done (RM: bsmtpd -- RoM; RC bug, nobody wants to fix it)

Your message dated Thu, 01 Sep 2005 19:57:40 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326118: 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

Processed: closing 321895

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.4 > close 321895 Bug#321895: [EMAIL PROTECTED]: Changelog pages on debian.org] 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explana

Bug#325992: marked as done (RM: kcd -- RoM; buggy, dead upstream, redundant in KDE 3.4)

Your message dated Thu, 01 Sep 2005 19:42:40 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325992: 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#321763: marked as done (RM: epos-lpc, epos-ktd, epos-ptd -- ROM; obsoleted by free Epos voices)

Your message dated Thu, 01 Sep 2005 19:47:48 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#321763: 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#326086: marked as done (RM: kmerlin -- RoM; dead upstream, useless due to incompatibility with current MSN protocols, alternatives exist (kopte))

Your message dated Thu, 01 Sep 2005 19:45:01 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326086: 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#323800: marked as done (RM: libsnmpkit2c102 -- RoM; obsolete due to C++ transition)

Your message dated Fri, 2 Sep 2005 03:04:38 +0200 with message-id <[EMAIL PROTECTED]> and subject line ftp.debian.org: remove libsnmpkit2c102 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#321907: marked as done (RM: dhid -- RoM; dummy transitional package)

Your message dated Thu, 01 Sep 2005 17:56:41 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#321907: 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#323208: marked as done (RM: python-rrd -- RoM; obsolete; now included in rrdtool source)

Your message dated Thu, 01 Sep 2005 17:58:41 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323208: 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#323769: marked as done (RM: cfdisk-utf8 -- RoM; obsolete)

Your message dated Thu, 01 Sep 2005 18:00:46 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323769: 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#324343: marked as done (RM: icu28 -- RoM; superseded by icu)

Your message dated Thu, 01 Sep 2005 18:05:46 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#324343: 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#214928: marked as done (RM: pdfscreen -- RoQA; orphaned, no longer used by anything)

Your message dated Thu, 01 Sep 2005 17:09:30 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#214928: 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#264219: marked as done (RM: kernellab -- RoM; no upstream, doesn't work with current kernels)

Your message dated Thu, 01 Sep 2005 17:10:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#264219: 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#314675: marked as done (RM: openduke -- RoQA; orphaned, RC bugs, limited functionality, in contrib)

Your message dated Thu, 01 Sep 2005 17:12:02 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#314675: 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#293582: marked as done (kturtle: Compiler error messages have wrong line number)

Your message dated Thu, 01 Sep 2005 15:23:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#293582: fixed in kdeedu 4:3.4.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 y

Bug#129491: marked as done (ktouch: No manual level change possible)

Your message dated Thu, 01 Sep 2005 15:23:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#129491: fixed in kdeedu 4:3.4.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 y

Bug#301796: marked as done (kdeedu: FTBFS (amd64/gcc-4.0): Please do not use /lib64 on amd64 and ppc64)

Your message dated Thu, 01 Sep 2005 15:23:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#301796: fixed in kdeedu 4:3.4.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 y

Bug#325973: marked as done (qscintilla: rebuild for c++ transition [NMU prepared])

Your message dated Thu, 01 Sep 2005 15:24:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325973: fixed in qscintilla 1.6-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#305980: marked as done (keduca: include keduca-shrinker)

Your message dated Thu, 01 Sep 2005 15:23:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#305980: fixed in kdeedu 4:3.4.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 y

Bug#325108: marked as done (libcal3d10: gcc-4 ABI change)

Your message dated Thu, 01 Sep 2005 14:56:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325108: fixed in cal3d 0.10.0-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 you

Bug#318164: marked as done (CXX 4.0 transition)

Your message dated Thu, 01 Sep 2005 14:58:43 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#318164: fixed in hdf5 1.6.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 your

Bug#324592: marked as done (digikam: Libraries should be split in a lib and -dev package.)

Your message dated Thu, 01 Sep 2005 15:03:59 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#324592: fixed in digikam 0.7.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 yo

Bug#305198: marked as done (new snapshot available)

Your message dated Thu, 01 Sep 2005 14:54:22 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#305198: fixed in asterisk-chan-misdn 0.1.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

Bug#325370: marked as done (ITP: cowdancer -- a COW scratch filesystem implementation in userland)

Your message dated Thu, 01 Sep 2005 14:53:15 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325370: fixed in cowdancer 0.4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#323353: marked as done (ITP: jwm -- Extremely small and lightweight pure X11 window manager)

Your message dated Thu, 01 Sep 2005 14:38:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323353: fixed in jwm 0.23-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#325371: marked as done (ITP: binfmtc -- a binfmt_misc hook for running C programs as scripts)

Your message dated Thu, 01 Sep 2005 14:51:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325371: fixed in binfmtc 0.8-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#322513: marked as done (gnome-doc-utils: Please change dependency on libxml2-python2.3 to python2.3-libxml2)

Your message dated Thu, 01 Sep 2005 14:47:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#322513: fixed in gnome-doc-utils 0.3.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 i

Bug#321841: marked as done (since ksocrat-data will move to non-free, kscocrat needs to go to contrib)

Your message dated Thu, 01 Sep 2005 14:39:16 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#321841: fixed in ksocrat 3.2.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#311297: marked as done (ITP: fldiff -- Lightweight graphical program to show differences between files/directories)

Your message dated Thu, 01 Sep 2005 14:45:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#311297: fixed in fldiff 1.0-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#269557: marked as done (New upstream available)

Your message dated Thu, 01 Sep 2005 14:39:16 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#269557: fixed in ksocrat 3.2.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#226436: marked as done (ITP: imview -- Image viewing and analysis application)

Your message dated Thu, 01 Sep 2005 14:43:48 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#226436: fixed in imview 1.1.8-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 you

Bug#251234: marked as done (ksocrat: No menu item)

Your message dated Thu, 01 Sep 2005 14:39:16 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#251234: fixed in ksocrat 3.2.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#226906: marked as done (ksocrat: Russian writings are displayed as rectangles)

Your message dated Thu, 01 Sep 2005 14:39:16 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#226906: fixed in ksocrat 3.2.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#317931: marked as done (gnome-doc-utils: New upstream version 0.3.1 available)

Your message dated Thu, 01 Sep 2005 14:47:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#317931: fixed in gnome-doc-utils 0.3.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 i

Bug#320121: marked as done (/usr/include/semaphore.h's use of the 'restrict' keyword)

Your message dated Thu, 01 Sep 2005 14:47:26 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#320121: fixed in hurd 20050513-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 yo

Bug#325202: marked as done (ITP: libsql-abstract-limit-perl -- portable LIMIT emulation)

Your message dated Thu, 01 Sep 2005 14:31:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325202: fixed in libsql-abstract-limit-perl 0.033-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 th

Bug#288163: marked as done (eog: incorrectly creates threads when loading images)

Your message dated Thu, 01 Sep 2005 14:32:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#288163: fixed in eog 2.10.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#287980: marked as done (eog: Incorrect error message when saving to an existing file name)

Your message dated Thu, 01 Sep 2005 14:32:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#287980: fixed in eog 2.10.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#325759: marked as done (digikam-doc: FTBFS: Missing Build-Depends on 'kdelibs4-dev')

Your message dated Thu, 01 Sep 2005 14:17:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325759: fixed in digikam-doc 0.7.4-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#315653: marked as done (ITP: fteqcc -- QuakeC compiler)

Your message dated Thu, 01 Sep 2005 14:14:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#315653: fixed in fteqcc 2352-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#325787: marked as done ([Fwd: Log for successful build of xjdic_24-5 (dist=unstable)])

Your message dated Thu, 01 Sep 2005 14:03:02 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325787: fixed in xjdic 24-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your re

Bug#321856: marked as done (icewm: normal users can't reboot anyway)

Your message dated Thu, 01 Sep 2005 14:02:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#321856: fixed in icewm 1.2.23-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 you

Bug#326020: marked as done (icewm: FTBFS (amd64): Missing Build-Depends on 'libxpm-dev, librandr-dev, libxinerama-dev')

Your message dated Thu, 01 Sep 2005 14:02:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326020: fixed in icewm 1.2.23-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 you

Bug#223795: marked as done (hpoj: ptal-init setup doesn't find HP usb printer)

Your message dated Thu, 01 Sep 2005 14:02:22 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#223795: fixed in hpoj 0.91-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#272221: marked as done (mp3rename: should be able to zero pad the track number so it sorts bett])

Your message dated Thu, 01 Sep 2005 14:02:47 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#272221: fixed in mp3rename 0.6-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 yo

Bug#319311: marked as done (icewm_1.2.22-2(alpha/unstable): broken upload)

Your message dated Thu, 01 Sep 2005 14:02:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#319311: fixed in icewm 1.2.23-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 you

Bug#326020: marked as done (icewm: FTBFS (amd64): Missing Build-Depends on 'libxpm-dev, librandr-dev, libxinerama-dev')

Your message dated Thu, 01 Sep 2005 14:02:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#319311: fixed in icewm 1.2.23-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 you

Bug#325393: marked as done (hpoj cannot start without "scanner" group existing)

Your message dated Thu, 01 Sep 2005 14:02:22 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325393: fixed in hpoj 0.91-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#325841: marked as done (ginac_1.3.2-1 (ia64/unstable): FTBFS: no matching function for call to 'GiNaC::registered_class_options::print_func(void (GiNaC::add::*)(const GiNaC::print_context&, unsigned int)const)')

Your message dated Thu, 01 Sep 2005 14:02:17 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325841: fixed in ginac 1.3.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#319311: marked as done (icewm_1.2.22-2(alpha/unstable): broken upload)

Your message dated Thu, 01 Sep 2005 14:02:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326020: fixed in icewm 1.2.23-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 you

Bug#310516: marked as done (gnugk: ftbfs [sparc] RasTbl.cxx:31:22: stl_supp.h: No such file or directory)

Your message dated Thu, 01 Sep 2005 21:57:05 +0100 with message-id <[EMAIL PROTECTED]> and subject line gnugk built for C++ migration. 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#236204: marked as done (openh323gk in stable drops calls)

Your message dated Thu, 01 Sep 2005 21:19:52 +0100 with message-id <[EMAIL PROTECTED]> and subject line closing since sarge released 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#322933: marked as done (po-debconf: Creates invalid po files for some reason)

Your message dated Thu, 1 Sep 2005 22:38:56 +0200 with message-id <[EMAIL PROTECTED]> and subject line po-debconf: Creates invalid po files for some reason 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 ca

Bug#325998: marked as done (balsa: please update to gtkhtml3.6)

Your message dated Thu, 1 Sep 2005 13:45:41 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325999: mysql-query-browser: please rebuild against gtkhtml3.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 thi

Bug#325999: marked as done (mysql-query-browser: please rebuild against gtkhtml3.6)

Your message dated Thu, 1 Sep 2005 13:45:41 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325999: mysql-query-browser: please rebuild against gtkhtml3.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 thi

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

Your message dated Thu, 01 Sep 2005 11:32:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325951: fixed in libtunepimp 0.3.0-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 no

Bug#311683: marked as done (xscreensaver: under some circumstances KDE screensaver can show porn)

Your message dated Thu, 01 Sep 2005 11:02:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#311683: fixed in kdeartwork 4:3.4.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 n

Bug#316900: marked as done (Varning should be included for the Webcollage screensaver)

Your message dated Thu, 01 Sep 2005 11:02:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#316900: fixed in kdeartwork 4:3.4.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 n

Bug#311683: marked as done (xscreensaver: under some circumstances KDE screensaver can show porn)

Your message dated Thu, 01 Sep 2005 11:02:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#316900: fixed in kdeartwork 4:3.4.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 n

Bug#322008: marked as done (kdeartwork-theme-desktop: Dummy package still needed?)

Your message dated Thu, 01 Sep 2005 11:02:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#322008: fixed in kdeartwork 4:3.4.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 n

Bug#271640: marked as done (gtklp fails to start gtklpq)

Your message dated Thu, 01 Sep 2005 11:02:15 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#271640: fixed in gtklp 1.0rel+1.0g-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#278263: marked as done (please split GL desktop files into a separate package)

Your message dated Thu, 01 Sep 2005 11:02:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#278263: fixed in kdeartwork 4:3.4.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 n

Bug#310866: marked as done (kscreensaver-xsavers: missing screensaver 'pinion')

Your message dated Thu, 01 Sep 2005 11:02:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#310866: fixed in kdeartwork 4:3.4.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 n

Bug#316900: marked as done (Varning should be included for the Webcollage screensaver)

Your message dated Thu, 01 Sep 2005 11:02:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#311683: fixed in kdeartwork 4:3.4.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 n

Bug#317202: marked as done (libjack0.80.0-0 removed from unstable; rebuild required)

Your message dated Thu, 01 Sep 2005 11:02:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#317202: fixed in kdeartwork 4:3.4.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 n

Bug#319347: marked as done (gtklp: Browser command ought to be sensible-browser)

Your message dated Thu, 01 Sep 2005 11:02:15 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#319347: fixed in gtklp 1.0rel+1.0g-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#326055: marked as done (bts: block command doesn't work as documented)

Your message dated Thu, 1 Sep 2005 18:52:14 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#326055: bts: block command doesn't work as documented 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#325897: marked as done (Dependencies: RT2500STA.dat conflicts with standard debian settings)

Your message dated Thu, 01 Sep 2005 10:32:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325897: fixed in rt2500 1.1.0+cvs20050819-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 i

Bug#325850: marked as done (post-install fails because of absence of "mlton" doc control file)

Your message dated Thu, 1 Sep 2005 10:41:58 -0700 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 reop

Bug#325848: marked as done (sdcc: Useless files in /usr/share/sdcc/lib/?/)

Your message dated Thu, 01 Sep 2005 10:32:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325848: fixed in sdcc 2.5.0-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#325914: marked as done (cannot validate HTML 4.01 Frameset)

Your message dated Thu, 01 Sep 2005 10:32:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325914: fixed in wdg-html-validator 1.6.2-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 i

Bug#323278: marked as done (vim: crypt_autosign crypt_autoencrypt and xterm_set_titles not highlighted in .muttrc)

Your message dated Thu, 01 Sep 2005 10:17:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323278: fixed in vim 1:6.3-086+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#322254: marked as done (vim: typo in doc/editing.txt)

Your message dated Thu, 01 Sep 2005 10:17:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#322254: fixed in vim 1:6.3-086+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#321119: marked as done (vim-common: syn keyword sshconfigKeyword HashKnownHosts)

Your message dated Thu, 01 Sep 2005 10:17:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#321119: fixed in vim 1:6.3-086+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#320602: marked as done (Conformance with menu policy)

Your message dated Thu, 01 Sep 2005 10:17:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#320602: fixed in vim 1:6.3-086+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#314595: marked as done (vim-common: typo (maybe copy'n'paste error) in /usr/share/vim/vim63/doc/filetype.txt)

Your message dated Thu, 01 Sep 2005 10:17:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#314595: fixed in vim 1:6.3-086+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#308947: marked as done (vim-common: Syntax highlighting for sources.list)

Your message dated Thu, 01 Sep 2005 10:17:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#308947: fixed in vim 1:6.3-086+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#307946: marked as done (add muttng to filetype.vim for mail syntax highlighting)

Your message dated Thu, 01 Sep 2005 10:17:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#307946: fixed in vim 1:6.3-086+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#311007: marked as done (filetypes for zope filesystem types)

Your message dated Thu, 01 Sep 2005 10:17:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#311007: fixed in vim 1:6.3-086+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#311081: marked as done (debian-testing-i386-businesscard.iso)

Your message dated Thu, 01 Sep 2005 10:17:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#311081: fixed in vim 1:6.3-086+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#316184: marked as done (vim-common: incomplet bibtex syntax file)

Your message dated Thu, 01 Sep 2005 10:17:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#316184: fixed in vim 1:6.3-086+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#322355: marked as done (vim-common: syn keyword xmodmapKeySym XF86_ClearGrab)

Your message dated Thu, 01 Sep 2005 10:17:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#322355: fixed in vim 1:6.3-086+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#325982: marked as done (sip4-qt3: rebuild for c++ transition (NMU))

Your message dated Thu, 01 Sep 2005 10:02:28 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#325982: fixed in sip4-qt3 4.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 now you

Bug#321666: marked as done (hpoj: can't talk to printer)

Your message dated Thu, 01 Sep 2005 17:49:23 +0100 with message-id <[EMAIL PROTECTED]> and subject line fixed in hpoj-0.91-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibilit

Bug#322877: marked as done (doc-linux: copyright misleading about Clone-HOWTO's license (not GPL))

Os and FAQs in HTML format doc-linux-text - Linux HOWTOs and FAQs in ASCII format Closes: 201102 316163 322877 Changes: doc-linux (2005.09-1) unstable; urgency=low . * new upstream release (20050901) * Removed HOWTOs: Laptop-HOWTO GTEK-BBS-550 * Removing the Laptop-HOWTO closes: #20

Bug#201102: marked as done (doc-linux: Linux Laptop HOWTO is now called the "Linux-Mobile-Guide")

text - Linux HOWTOs and FAQs in ASCII format Closes: 201102 316163 322877 Changes: doc-linux (2005.09-1) unstable; urgency=low . * new upstream release (20050901) * Removed HOWTOs: Laptop-HOWTO GTEK-BBS-550 * Removing the Laptop-HOWTO closes: #201102 * Added HOWTOs: Oracle-9i-F

Bug#316163: marked as done (doc-linux-text: HOWTO-HOWTO includes an old url)

gt; Description: doc-linux-html - Linux HOWTOs and FAQs in HTML format doc-linux-text - Linux HOWTOs and FAQs in ASCII format Closes: 201102 316163 322877 Changes: doc-linux (2005.09-1) unstable; urgency=low . * new upstream release (20050901) * Removed HOWTOs: Laptop-HOWTO GTEK-BBS

Bug#311699: marked as done ([l10n] Czech translation for smsclient)

Your message dated Thu, 01 Sep 2005 09:17:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#311699: fixed in smsclient 2.0.8z-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 now

Bug#274899: marked as done ([INTL:nl] new dutch po-debconf translation)

Your message dated Thu, 01 Sep 2005 09:17:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#274899: fixed in smsclient 2.0.8z-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 now

  1   2   >