Bug#316297: marked as done (Installation of qmail removes mailx)

Your message dated Fri, 20 Jan 2006 23:47:13 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#316297: fixed in mysql-dfsg-5.0 5.0.18-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#348854: marked as done (/usr/lib/libmysqlclient.so.15: no version information available)

Your message dated Fri, 20 Jan 2006 23:47:13 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#348854: fixed in mysql-dfsg-5.0 5.0.18-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#349101: marked as done (exim4-daemon-heavy: Does not start: libmysqlclient.so.15: no version information available)

Your message dated Fri, 20 Jan 2006 23:47:13 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#348854: fixed in mysql-dfsg-5.0 5.0.18-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#343047: marked as done (madwifi-source: Please include a README.Debian to outline build process)

Your message dated Sat, 21 Jan 2006 18:11:21 +1000 with message-id [EMAIL PROTECTED] and subject line Isn't a 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 now your responsibility to

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

Your message dated Sat, 21 Jan 2006 19:03:17 +1100 with message-id [EMAIL PROTECTED] and subject line Closing bug for removed package has caused the 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#327972: marked as done (klog: uninstallable; needs rebuild for the Qt/KDE transition)

Your message dated Sat, 21 Jan 2006 00:32:06 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#327972: fixed in klog 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 is now your

Bug#290288: marked as done (mozilla-firefox: View Page Source show the previous page)

Your message dated Sat, 21 Jan 2006 10:27:39 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#290288: mozilla-firefox: View Page Source show the previous page has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#349138: marked as done (localechooser: Uses non existing fi_FI.UTF-8 locale for Finnish)

Your message dated Sat, 21 Jan 2006 10:12:45 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#349138: localechooser: Uses non existing fi_FI.UTF-8 locale for Finnish has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt

Bug#302693: marked as done (sig2dot must not include external signatures if using a subset of your keyring)

Your message dated Sat, 21 Jan 2006 01:32:19 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#302693: fixed in sig2dot 0.36 has caused the 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#348783: marked as done (sig2dot: does not recognize trust signatures with a level =10)

Your message dated Sat, 21 Jan 2006 01:32:19 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#348783: fixed in sig2dot 0.36 has caused the 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#297302: marked as done (kbiff freezes very often)

Your message dated Sat, 21 Jan 2006 01:47:08 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#297302: fixed in kbiff 3.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#312381: marked as done (kbiff: imap4s support is buggy and leaky)

Your message dated Sat, 21 Jan 2006 01:47:08 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#312381: fixed in kbiff 3.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

Processed: Closing bugs

Processing commands for [EMAIL PROTECTED]: close 327958 Bug#327958: komba2: uninstallable; needs rebuild for the Qt/KDE transition 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Adeodato Simó [EMAIL PROTECTED] Removed

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

Your message dated Sat, 21 Jan 2006 01:47:08 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#314015: fixed in kbiff 3.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#343187: marked as done (new upstream version; please update your package)

Your message dated Sat, 21 Jan 2006 01:47:08 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#343187: fixed in kbiff 3.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

Processed: Re: Bug#301558 acknowledged by developer ()

Processing commands for [EMAIL PROTECTED]: close 301558 Bug#301558: warnings compiling expect 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Matthias Klose [EMAIL PROTECTED] thanks Stopping processing here. Please contact

Bug#295633: marked as done (expect_5.42.1-1.2(i386/unstable): FTBFS: really build-depends autoconf2.13)

Your message dated Sat, 21 Jan 2006 02:17:10 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#295633: fixed in expect 5.42.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 is now

Bug#301556: marked as done (tcl8.4 based expect doesn't deliver reliable test results on hppa)

Your message dated Sat, 21 Jan 2006 02:17:10 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#301556: fixed in expect 5.42.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 is now

Bug#197640: marked as done (expect: autoexpect doesn't accept options)

Your message dated Sat, 21 Jan 2006 02:17:10 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#197640: fixed in expect 5.42.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 is now

Bug#314224: marked as done (expect: Tcl8.4 link problem)

Your message dated Sat, 21 Jan 2006 02:17:10 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#314224: fixed in expect 5.42.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 is now

Bug#156815: marked as done (expect make check fails)

Your message dated Sat, 21 Jan 2006 02:17:10 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#156815: fixed in expect 5.42.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 is now

Bug#294092: marked as done (Eternal output bug in expect)

Your message dated Sat, 21 Jan 2006 02:17:10 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#294092: fixed in expect 5.42.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 is now

Processed: Re: Bug#277350 acknowledged by developer ()

Processing commands for [EMAIL PROTECTED]: close 277350 Bug#277350: expect: Needs more recent config.guess and config.sub for k*BSD 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Santiago Vila [EMAIL PROTECTED] thanks

Bug#335745: marked as done (sextractor: New upstream release)

Your message dated Sat, 21 Jan 2006 03:47:06 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#335745: fixed in sextractor 2.4.4-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#337281: marked as done (sextractor: Provide: sextractor-doc)

Your message dated Sat, 21 Jan 2006 03:47:06 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#337281: fixed in sextractor 2.4.4-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#347997: marked as done (cairo-ocaml - FTBFS: cp: cannot stat `debian/tmp/usr/lib/ocaml/3.09.0/cairo/dllmlcairo.so': No such file or directory)

Your message dated Sat, 21 Jan 2006 04:02:06 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#347997: fixed in cairo-ocaml 20060107-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#279220: marked as done (sound is pure static)

Your message dated Sat, 21 Jan 2006 08:28:46 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#279220: sound is pure static has caused the 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#348005: marked as done (tuxpaint (--sound) refuses to quit when /dev/sequencer cannot be found)

Your message dated Sat, 21 Jan 2006 08:20:18 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#348005: tuxpaint (--sound) refuses to quit when /dev/sequencer cannot be found has caused the attached Bug report to be marked as done. This means that you claim that the problem has been

Bug#339472: marked as done (sextractor: New upstream release)

Your message dated Sat, 21 Jan 2006 03:47:06 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#335745: fixed in sextractor 2.4.4-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#349160: marked as done (libogg-dev: ${shlibs:Depends} not correctly expanded when libogg is needed)

Your message dated Sat, 21 Jan 2006 14:04:22 +0100 with message-id [EMAIL PROTECTED] and subject line libogg-dev:${shlibs:Depends} not correctly expanded when libogg is needed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with.

Bug#97442: marked as done (eterm: vim (X11 enabled) does not respond to mouse clicks when TERM=Eterm)

Your message dated Sat, 21 Jan 2006 14:33:07 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#97442: eterm: vim (X11 enabled) does not respond to mouse clicks when TERM=Eterm has caused the attached Bug report to be marked as done. This means that you claim that the problem has been

Processed: Let's give proper version information

Processing commands for [EMAIL PROTECTED]: reopen 349160 Bug#349160: libogg-dev: ${shlibs:Depends} not correctly expanded when libogg is needed Bug reopened, originator not changed. notfound 349160 1.1.2-1 Bug#349160: libogg-dev: ${shlibs:Depends} not correctly expanded when libogg is needed

Bug#304144: marked as done (kvim: removing diversion fails)

Your message dated Sat, 21 Jan 2006 14:36:47 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#304144: Problems while removing kvim has caused the 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#349183: marked as done (diff for 3.1-6.1 NMU)

Your message dated Sat, 21 Jan 2006 14:48:39 +0100 with message-id [EMAIL PROTECTED] and subject line diff for 3.1-6.1 NMU has caused the 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

Bug#144846: marked as done (auctex: Please support XEmacs21 )

Your message dated Sat, 21 Jan 2006 15:12:54 +0100 with message-id [EMAIL PROTECTED] and subject line preview-latex merged with auctex has caused the 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#344285: marked as done (misleading README.Debian)

Your message dated Sat, 21 Jan 2006 15:13:35 +0100 with message-id [EMAIL PROTECTED] and subject line No longer applies has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#329061: marked as done (emacs21: Package update fails)

Your message dated Sat, 21 Jan 2006 15:13:04 +0100 with message-id [EMAIL PROTECTED] and subject line No longer applies. has caused the 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

Bug#341213: marked as done (auctex: Problem while parsing maths)

Your message dated Sat, 21 Jan 2006 15:13:27 +0100 with message-id [EMAIL PROTECTED] and subject line Submitter states this is no longer a 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

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

Your message dated Sat, 21 Jan 2006 06:02:13 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#347070: fixed in vstream 0.4.5-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

Processed: Re: /usr/share/vim/vim61/doc directory changes when :help syntax is invoked

Processing commands for [EMAIL PROTECTED]: close 295186 6.2 Bug#295186: /usr/share/vim/vim61/doc directory changes when :help syntax is invoked 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 6.2, send any further explanations to [EMAIL

Bug#190511: marked as done (randtype: FTBFS: Missing Build-Depends)

Your message dated Sat, 21 Jan 2006 06:47:19 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#190511: fixed in randtype 1.13-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#347099: marked as done (wmgtemp: FTBFS: build-depends on removed xlibs-dev)

Your message dated Sat, 21 Jan 2006 06:32:11 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#347099: fixed in wmgtemp 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 is now your

Bug#300933: marked as done (preview-latex: clean target does not really clean)

Your message dated Sat, 21 Jan 2006 16:18:25 +0100 with message-id [EMAIL PROTECTED] and subject line Closed by 11.81-1 (released version 11.81-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#318114: marked as done (preview-latex-style: Wrong equation numbers with option auctex)

Your message dated Sat, 21 Jan 2006 16:18:25 +0100 with message-id [EMAIL PROTECTED] and subject line Closed by 11.81-1 (released version 11.81-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#277885: marked as done (preview-latex: Customise screens incorrectly parented)

Your message dated Sat, 21 Jan 2006 16:18:25 +0100 with message-id [EMAIL PROTECTED] and subject line Closed by 11.81-1 (released version 11.81-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#347472: marked as done (auctex: update-auctex-elisp calls rm with a too long list of files)

Your message dated Sat, 21 Jan 2006 07:02:04 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#347472: fixed in auctex 11.81-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#331751: marked as done (auctex depends on debconf without | debconf-2.0 alternate; blocks cdebconf transition)

Your message dated Sat, 21 Jan 2006 16:18:25 +0100 with message-id [EMAIL PROTECTED] and subject line Closed by 11.81-1 (released version 11.81-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#349169: marked as done (diff for 8.14-3.1 NMU)

Your message dated Sat, 21 Jan 2006 16:09:50 +0100 with message-id [EMAIL PROTECTED] and subject line diff for 8.14-3.1 NMU has caused the 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#348792: marked as done (libgcj6: string-to-double conversion can throw NullPointerException)

with gcj libgcj6-jar - Java runtime library for use with gcj (jar files) libgcj6-src - libgcj java sources for use in eclipse Closes: 348792 Changes: gcj-4.0 (4.0.2-7j1) unstable; urgency=low . * Update to SVN 20060121, taken from the gcc-4_0-branch. - Fix PR classpath/23863, string

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

Your message dated Sat, 21 Jan 2006 08:17:07 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#346687: fixed in baken 0.5.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 your

Bug#347679: marked as done (emacs-dl-wnn: Depends on libwnn6, which is uninstallable)

Your message dated Sat, 21 Jan 2006 17:12:07 +0100 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

Bug#320216: marked as done (logwatch: pb with compressed samba logfiles)

Your message dated Sat, 21 Jan 2006 17:19:08 +0100 with message-id [EMAIL PROTECTED] and subject line fixed in unstable has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#338006: marked as done (libssl0.9.8: bad record mac because of wrong SSL_OP_TLS_BLOCK_PADDING_BUG handling)

Your message dated Sat, 21 Jan 2006 08:32:13 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#338006: fixed in openssl 0.9.8a-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#349044: marked as done (Please default the encrypt passwords settings in default smb.conf)

Your message dated Sat, 21 Jan 2006 17:09:21 +0100 with message-id [EMAIL PROTECTED] and subject line Suggestion about adding encrypted passwords to smb.conf has caused the 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#343260: marked as done (Grub: After installing linux-image-2.6.14-2-k7 grub had wrong entries)

Your message dated Sat, 21 Jan 2006 18:03:53 +0100 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

Bug#345516: marked as done (needs to support an environment file in cluster conf dir)

Your message dated Sat, 21 Jan 2006 09:02:09 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#345516: fixed in postgresql-common 40 has caused the 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#346442: marked as done (Typo in /usr/share/doc/postgresql-common/README.Debian.gz: detailled)

Your message dated Sat, 21 Jan 2006 09:02:09 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#346442: fixed in postgresql-common 40 has caused the 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#348447: marked as done (/etc/postgresql-common/user_clusters not available)

Your message dated Sat, 21 Jan 2006 09:02:09 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#348447: fixed in postgresql-common 40 has caused the 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#348875: marked as done (postgresql-common: possible port conflict with pgpool)

Your message dated Sat, 21 Jan 2006 09:02:09 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#348875: fixed in postgresql-common 40 has caused the 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#343021: marked as done (Package explicitely build-depends on g++-3.4)

Your message dated Sat, 21 Jan 2006 09:17:11 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#343021: fixed in socketapi 1.7.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

Bug#337846: marked as done (Should -DRUNTIME_CPUDETECT to enable runtime CPU detection)

Your message dated Sat, 21 Jan 2006 09:47:10 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#337846: fixed in ffmpeg 0.cvs20050918-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

Bug#338895: marked as done (ffmpeg: debian/rules does not respect DEB_BUILD_OPTIONS=nostrip noopt debug)

Your message dated Sat, 21 Jan 2006 09:47:10 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#338895: fixed in ffmpeg 0.cvs20050918-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

Bug#342207: marked as done (ffmpeg: Exploitable heap overflow in libavcodec's image handling)

Your message dated Sat, 21 Jan 2006 09:47:10 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#342207: fixed in ffmpeg 0.cvs20050918-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

Bug#349217: marked as done (libgtk2-gladexml-perl missing method signal_connect_after)

Your message dated Sat, 21 Jan 2006 18:53:47 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#349217: libgtk2-gladexml-perl missing method signal_connect_after has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#255376: marked as done (amavisd-new reload kills daemon)

Your message dated Sat, 21 Jan 2006 10:02:08 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#255376: fixed in amavisd-new 1:2.3.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

Bug#348439: marked as done (amavisd-new: wrong libcompress-zlib-perl dependency version)

Your message dated Sat, 21 Jan 2006 10:02:08 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#348439: fixed in amavisd-new 1:2.3.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

Bug#348990: marked as done ([config] missing defaults for local_domain_maps disable functionality)

Your message dated Sat, 21 Jan 2006 10:02:08 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#348990: fixed in amavisd-new 1:2.3.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

Bug#303131: marked as done (1.29 contains officially required boilerplates)

Your message dated Sat, 21 Jan 2006 19:33:39 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#303131: 1.29 contains officially required boilerplates has caused the 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#346650: marked as done (baycomepp: FTBFS: build-depends on removed xlibs-dev)

Your message dated Sat, 21 Jan 2006 10:47:05 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#346650: fixed in baycomepp 0.10-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

Bug#255376: marked as done (amavisd-new reload kills daemon)

Your message dated Sat, 21 Jan 2006 17:08:47 -0200 with message-id [EMAIL PROTECTED] and subject line Fixed in amavisd-new 1:2.3.3-3bpo1 (source all i386) has caused the 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#348439: marked as done (amavisd-new: wrong libcompress-zlib-perl dependency version)

Your message dated Sat, 21 Jan 2006 17:08:47 -0200 with message-id [EMAIL PROTECTED] and subject line Fixed in amavisd-new 1:2.3.3-3bpo1 (source all i386) has caused the 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#348990: marked as done ([config] missing defaults for local_domain_maps disable functionality)

Your message dated Sat, 21 Jan 2006 17:08:47 -0200 with message-id [EMAIL PROTECTED] and subject line Fixed in amavisd-new 1:2.3.3-3bpo1 (source all i386) has caused the 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#346624: marked as done (grig: FTBFS: build-depends on removed xlibs-dev)

Your message dated Sat, 21 Jan 2006 11:02:07 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#346624: fixed in grig 0.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 your

Bug#336907: marked as done (openssl: sha512 regresstion test failed on hppa.)

Your message dated Sat, 21 Jan 2006 20:32:48 +0100 with message-id [EMAIL PROTECTED] and subject line openssl: sha512 regresstion test failed on hppa. has caused the 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#334803: marked as done (login: suspend command from su shell doesn't work again)

Your message dated Sat, 21 Jan 2006 19:25:31 + with message-id [EMAIL PROTECTED] and subject line Bug#334803: [Pkg-shadow-devel] Bug#334803: login: suspend command from su shell doesn't work again has caused the attached Bug report to be marked as done. This means that you claim that the

Bug#348114: marked as done (happydigger: [INTL:sv] Swedish PO translation)

Your message dated Sat, 21 Jan 2006 11:32:10 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#348114: fixed in happydigger 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

Bug#342072: marked as done (happydigger: [INTL:tl] Tagalog program translation file)

Your message dated Sat, 21 Jan 2006 11:32:10 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#342072: fixed in happydigger 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

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

Your message dated Sat, 21 Jan 2006 11:32:17 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#346976: fixed in vkeybd 1:0.1.17-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#221270: marked as done (oneko: Segfault on excessive command line argument.)

Your message dated Sat, 21 Jan 2006 21:07:30 +0100 with message-id [EMAIL PROTECTED] and subject line Fixed in oneko 1.2.sakura.6-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#286533: marked as done (kplot: FTBFS: not using -fPIC to make shared lib.)

Your message dated Sat, 21 Jan 2006 20:58:21 +0100 with message-id [EMAIL PROTECTED] and subject line Fixed in kmatplot 0.4-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

Bug#300867: marked as done (kmatplot: FTBFS (amd64/gcc-4.0): invalid cast from type 'double' to type 'QSGFill::Style')

Your message dated Sat, 21 Jan 2006 20:58:21 +0100 with message-id [EMAIL PROTECTED] and subject line Fixed in kmatplot 0.4-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

Bug#236804: marked as done (wmitime needs rebuild for prelinking)

Your message dated Sat, 21 Jan 2006 21:05:06 +0100 with message-id [EMAIL PROTECTED] and subject line Fixed in wmitime 0.3-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

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

Your message dated Sat, 21 Jan 2006 20:58:21 +0100 with message-id [EMAIL PROTECTED] and subject line Fixed in kmatplot 0.4-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

Bug#327980: marked as done (kmatplot: uninstallable; needs rebuild for the Qt/KDE transition)

Your message dated Sat, 21 Jan 2006 20:58:21 +0100 with message-id [EMAIL PROTECTED] and subject line Fixed in kmatplot 0.4-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

Bug#343669: marked as done (tlf: several valgrind hits at startup (may result in crash))

Your message dated Sat, 21 Jan 2006 11:47:30 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#343669: fixed in tlf 0.9.27-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#346822: marked as done (xmailbox: FTBFS: build-depends on removed xlibs-dev)

Your message dated Sat, 21 Jan 2006 21:00:51 +0100 with message-id [EMAIL PROTECTED] and subject line Fixed in xmailbox 2.5-10 has caused the 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#346825: marked as done (xmem: FTBFS: build-depends on removed xlibs-dev)

Your message dated Sat, 21 Jan 2006 21:02:40 +0100 with message-id [EMAIL PROTECTED] and subject line Fixed in xmem 1.20-21 has caused the 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#347120: marked as done (wmitime: FTBFS: build-depends on removed xlibs-dev)

Your message dated Sat, 21 Jan 2006 21:05:06 +0100 with message-id [EMAIL PROTECTED] and subject line Fixed in wmitime 0.3-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

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

Your message dated Sat, 21 Jan 2006 21:07:30 +0100 with message-id [EMAIL PROTECTED] and subject line Fixed in oneko 1.2.sakura.6-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Processed: closing 348979

Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.10 close 348979 1.4.1-1 Bug#348979: pgadmin3: Please package newer version 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 1.4.1-1,

Bug#281853: marked as done (pgadmin3: support local connection?)

Your message dated Sat, 21 Jan 2006 23:10:28 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#281853 pgadmin3: support local connection? has caused the 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#340063: marked as done (nullmailer: ipv6 support not enabled)

Your message dated Sat, 21 Jan 2006 14:03:20 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#340063: fixed in nullmailer 1:1.02-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#345140: marked as done ([l10n] Czech translation for kernel-patch-grsecurity2)

Your message dated Sat, 21 Jan 2006 14:03:12 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#345140: fixed in kernel-patch-grsecurity2 2.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

Bug#348798: marked as done (nullmailer: New upstream release)

Your message dated Sat, 21 Jan 2006 14:03:20 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#348798: fixed in nullmailer 1:1.02-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#348983: marked as done (New version 0.9.12 available)

Your message dated Sat, 21 Jan 2006 14:03:28 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#348983: fixed in re2c 0.9.12-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#348989: marked as done (pybliographer: New upstream version 1.2.7)

Your message dated Sat, 21 Jan 2006 14:03:26 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#348989: fixed in pybliographer 1.2.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

Bug#349246: marked as done (GRSecurity Elevated Service Privileges Weakness)

Your message dated Sat, 21 Jan 2006 14:03:12 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#349246: fixed in kernel-patch-grsecurity2 2.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

Bug#275247: marked as done (phpsysinfo: add info for hddtemp)

Your message dated Sat, 21 Jan 2006 23:39:04 +0100 with message-id [EMAIL PROTECTED] and subject line phpsysinfo: add info for hddtemp has caused the 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#349059: marked as done (egroupware postgresql backend not working properly)

Your message dated Sat, 21 Jan 2006 23:27:56 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#349059: egroupware postgresql backend not working properly has caused 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#85437: marked as done (kdoc: missing subroutine called)

Your message dated Sat, 21 Jan 2006 23:36:56 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#85437: fixed in current 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

  1   2   >