Bug#404499: marked as done ([l10n] Updated Czech translation of sitebar debconf messages)

Your message dated Mon, 08 Jan 2007 07:47:04 + with message-id [EMAIL PROTECTED] and subject line Bug#404499: fixed in sitebar 3.3.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

Bug#402135: marked as done (gnome-user-share: FTBFS on GNU/kFreeBSD (due to unsatisfied Build-Depends on libselinux-dev))

Your message dated Mon, 08 Jan 2007 07:47:02 + with message-id [EMAIL PROTECTED] and subject line Bug#402135: fixed in gnome-user-share 0.10-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

Bug#282906: marked as done (mc: rpm's are not shown correctly. Building and installing mc-4.6.0-333 Sourcecode from SuSE solves the issue.)

Your message dated Mon, 8 Jan 2007 09:30:57 +0100 with message-id [EMAIL PROTECTED] and subject line AW: works as expected has caused the attached Bug report to 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#405691: marked as done (wordpress: new upstream: 2.0.6)

Your message dated Mon, 08 Jan 2007 09:02:05 + with message-id [EMAIL PROTECTED] and subject line Bug#405691: fixed in wordpress 2.0.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

Bug#405299: marked as done (FrSIRT/ADV-2006-5191: WordPress get_file_description() Function Client-Side Cross Site Scripting Vulnerability)

Your message dated Mon, 08 Jan 2007 09:02:05 + with message-id [EMAIL PROTECTED] and subject line Bug#405299: fixed in wordpress 2.0.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

Bug#405944: marked as done (rhythmbox: locks up when a daap server goes away)

Your message dated Mon, 8 Jan 2007 10:23:14 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#405944: rhythmbox: locks up when a daap server goes away has caused the 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#405912: marked as done (puppetmaster: Puppetmaster's init.d script uses --exec when --startas is meant)

Your message dated Mon, 08 Jan 2007 09:32:20 + with message-id [EMAIL PROTECTED] and subject line Bug#405912: fixed in puppet 0.22.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

Bug#384363: marked as done (nautilus-python: FTBFS: change build-dep to libnautilus-extension-dev)

Your message dated Mon, 8 Jan 2007 10:52:35 +0100 with message-id [EMAIL PROTECTED] and subject line nautilus-python: FTBFS: change build-dep to libnautilus-extension-dev 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#404428: marked as done (htdig: [INTL:ru] Russian debconf templates translation update)

Your message dated Mon, 08 Jan 2007 10:02:14 + with message-id [EMAIL PROTECTED] and subject line Bug#404428: fixed in htdig 1:3.2.0b6-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#400009: marked as done (htdig: [INTL:ja] Updated Japanese po-debconf template translation (ja.po))

Your message dated Mon, 08 Jan 2007 10:02:14 + with message-id [EMAIL PROTECTED] and subject line Bug#49: fixed in htdig 1:3.2.0b6-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#400008: marked as done (htdig: [INTL:ja] Updated Japanese po-debconf template translation (ja.po))

Your message dated Mon, 08 Jan 2007 10:02:14 + with message-id [EMAIL PROTECTED] and subject line Bug#49: fixed in htdig 1:3.2.0b6-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#387047: marked as done (knetworkconf: please support debian etch 4.0 and debian unstable/experimental)

Your message dated Mon, 08 Jan 2007 10:17:03 + with message-id [EMAIL PROTECTED] and subject line Bug#387047: fixed in kdeadmin 4:3.5.5-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#401589: marked as done (htdig: formatting typo in htdig(1) manpage)

Your message dated Mon, 08 Jan 2007 10:02:14 + with message-id [EMAIL PROTECTED] and subject line Bug#401589: fixed in htdig 1:3.2.0b6-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#405696: marked as done (knetworkconf: Your Platform is Not Supported)

Your message dated Mon, 08 Jan 2007 10:17:03 + with message-id [EMAIL PROTECTED] and subject line Bug#405696: fixed in kdeadmin 4:3.5.5-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#308450: marked as done (startx -nolisten works only on :0)

Your message dated Mon, 8 Jan 2007 11:57:21 +0100 with message-id [EMAIL PROTECTED] and subject line startx -nolisten works only on :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 your

Bug#376916: marked as done (Recommends unavailable xfonts-base-transcoded)

Your message dated Mon, 8 Jan 2007 12:08:24 +0100 (CET) with message-id [EMAIL PROTECTED] and subject line Bug#376916: Recommends unavailable xfonts-base-transcoded has caused 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#355546: marked as done (solid-pop3d: homepage host not found)

Your message dated Mon, 08 Jan 2007 13:02:06 + with message-id [EMAIL PROTECTED] and subject line Bug#355546: fixed in solid-pop3d 0.15-18 has caused the attached Bug report to 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#381678: marked as done (solid-pop3d: [INTL:pt] Portuguese translation for debconf messages)

Your message dated Mon, 08 Jan 2007 13:02:05 + with message-id [EMAIL PROTECTED] and subject line Bug#381678: fixed in solid-pop3d 0.15-17 has caused the attached Bug report to 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#400722: marked as done (openoffice.org-calc: search function won't work with '+' character)

Your message dated Mon, 08 Jan 2007 14:05:42 +0100 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

Bug#327767: marked as done (man2html causes index++ to regularly eat very large amounts of RAM. Can be optimised?)

Your message dated Mon, 08 Jan 2007 13:02:03 + with message-id [EMAIL PROTECTED] and subject line Bug#327767: fixed in man2html 1.6c-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#352774: marked as done (swish++: index++ consumes unreasonable amount of memory while running)

Your message dated Mon, 08 Jan 2007 13:02:02 + with message-id [EMAIL PROTECTED] and subject line Bug#352774: fixed in dwww 1.10.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#233698: marked as done (xserver-xfree86: [mga] server partially hangs when Mozilla spawns less to view C source file on MGA G400 AGP rev 4)

Your message dated Mon, 8 Jan 2007 14:04:11 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#233698: xserver-xfree86: [mga] server partially hangs when Mozilla spawns less to view C source file on MGA G400 AGP rev 4 has caused the attached Bug report to be marked as done. This means

Bug#405375: marked as done (Add a warning when daemon is disabled by /etc/default/avahi-daemon)

Your message dated Mon, 08 Jan 2007 13:17:02 + with message-id [EMAIL PROTECTED] and subject line Bug#405375: fixed in avahi 0.6.16-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#386239: marked as done (continuously complains to syslog in 'recvmsg()')

Your message dated Mon, 08 Jan 2007 13:17:02 + with message-id [EMAIL PROTECTED] and subject line Bug#386239: fixed in avahi 0.6.16-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#405013: marked as done (z88dk - FTBFS: s390 is no 64bit architecture)

Your message dated Mon, 08 Jan 2007 13:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#405013: fixed in z88dk 1.6.ds1-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#405264: marked as done (z88dk_1.6.ds1-3 (s390/unstable): FTBFS: wrongly identifies s390 as 64bit)

Your message dated Mon, 08 Jan 2007 13:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#405264: fixed in z88dk 1.6.ds1-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#326735: marked as done (knode: crashes on change of language in the spellchecker dialog)

Your message dated Mon, 8 Jan 2007 14:58:30 +0100 with message-id [EMAIL PROTECTED] and subject line knode: crashes on change of language in the spellchecker dialog has caused 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#401540: marked as done (evolution: FTBFS on GNU/kFreeBSD (due to unsatisfied Build-Depends))

Your message dated Mon, 08 Jan 2007 14:47:04 + with message-id [EMAIL PROTECTED] and subject line Bug#401540: fixed in evolution 2.8.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

Processed: Re: Bug#405508: flyspell-buffer runs forever

Processing commands for [EMAIL PROTECTED]: reassign 405508 emacs-snapshot Bug#405508: flyspell-buffer runs forever Bug reassigned from package `aspell' to `emacs-snapshot'. close405508 1:20061027-1 Bug#405508: flyspell-buffer runs forever 'close' is deprecated; see

Processed: close this report as the requested feature is already implemented

Processing commands for [EMAIL PROTECTED]: package reprepro Ignoring bugs not assigned to: reprepro close 406023 1.3.0-1 Bug#406023: reprepro: please include gpg-verification mechanism for include commands 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as

Bug#399254: marked as done (ITA: libclass-contract-perl -- Design-by-Contract OO in Perl)

Your message dated Mon, 08 Jan 2007 15:32:04 + with message-id [EMAIL PROTECTED] and subject line Bug#399254: fixed in libclass-contract-perl 1.14-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

Bug#403381: marked as done (Cannot start eclipse: java-gcj-compatible complains missing NS_InitEmbedding)

Your message dated Mon, 8 Jan 2007 17:14:51 +0100 with message-id [EMAIL PROTECTED] and subject line Cannot start eclipse has caused the attached Bug report to 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#337860: marked as done (w3m-el: Can't be installed with emacs-snapshot-nox)

Your message dated Mon, 08 Jan 2007 16:17:06 + with message-id [EMAIL PROTECTED] and subject line Bug#321995: fixed in w3m-el 1.4.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#352542: marked as done (O: sfront -- MPEG 4 Structured Audio decoder)

Your message dated Mon, 08 Jan 2007 16:02:04 + with message-id [EMAIL PROTECTED] and subject line Bug#352542: fixed in sfront 0.87-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#214662: marked as done (openoffice.org: Fonts in the Help Browser are too small.)

Your message dated Mon, 8 Jan 2007 17:00:01 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#214662: Should be closed has caused the attached Bug report to 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#392464: marked as done (kernel-patch-exec-shield: Needs to be updated for 2.6.18)

Your message dated Mon, 08 Jan 2007 16:17:04 + with message-id [EMAIL PROTECTED] and subject line Bug#392464: fixed in kernel-patch-exec-shield 1:2.6.18-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

Bug#403324: marked as done (vde2: wirefilter manpage contains mistakes)

Your message dated Mon, 08 Jan 2007 16:32:04 + with message-id [EMAIL PROTECTED] and subject line Bug#403324: fixed in vde2 2.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 your

Bug#402929: marked as done (New upstream release available)

Your message dated Mon, 08 Jan 2007 17:02:06 + with message-id [EMAIL PROTECTED] and subject line Bug#402929: fixed in wifi-radar 1.9.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

Bug#405280: marked as done (kmail: Crashes with IMAP)

Your message dated Mon, 08 Jan 2007 16:47:10 + with message-id [EMAIL PROTECTED] and subject line Bug#405280: fixed in kdepim 4:3.5.5.dfsg.1-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#402049: marked as done (namazu --charset)

Your message dated Mon, 08 Jan 2007 17:02:06 + with message-id [EMAIL PROTECTED] and subject line Bug#402049: fixed in wifi-radar 1.9.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

Bug#405990: marked as done (lua-curl: FTBFS: app.c: test.lua:1: attempt to index global 'curl' (a nil value))

Your message dated Mon, 08 Jan 2007 16:47:11 + with message-id [EMAIL PROTECTED] and subject line Bug#405990: fixed in lua-expat 1.0.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#405997: marked as done (azureus: should not prompt the user about updates)

Your message dated Mon, 8 Jan 2007 09:35:33 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#405997: azureus: should not prompt the user about updates has caused 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#403292: marked as done (vde2: getpeerby[newaddr,id] return implicitly converted to int)

Your message dated Mon, 08 Jan 2007 16:32:04 + with message-id [EMAIL PROTECTED] and subject line Bug#403292: fixed in vde2 2.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 your

Bug#405595: marked as done (Initial nb translation of kdepim debconf messages)

Your message dated Mon, 08 Jan 2007 16:47:10 + with message-id [EMAIL PROTECTED] and subject line Bug#405595: fixed in kdepim 4:3.5.5.dfsg.1-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#406005: marked as done (kdepim FTBFS)

Your message dated Mon, 08 Jan 2007 16:47:10 + with message-id [EMAIL PROTECTED] and subject line Bug#406005: fixed in kdepim 4:3.5.5.dfsg.1-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#405589: marked as done (kalarm manpages out of date)

Your message dated Mon, 08 Jan 2007 16:47:10 + with message-id [EMAIL PROTECTED] and subject line Bug#405589: fixed in kdepim 4:3.5.5.dfsg.1-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#405992: marked as done (lua-posix: FTBFS: app.c: test.lua:23: attempt to index global 'ox' (a nil value))

Your message dated Mon, 08 Jan 2007 16:47:12 + with message-id [EMAIL PROTECTED] and subject line Bug#405992: fixed in lua-posix 1.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#404157: marked as done (FTBFS: detect-autoconf.pl can't find autom4te, causes ./admin/cvs.sh: line 33: --version: command not found)

Your message dated Mon, 08 Jan 2007 16:47:10 + with message-id [EMAIL PROTECTED] and subject line Bug#404157: fixed in kdepim 4:3.5.5.dfsg.1-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#403022: marked as done (Non-existent vlcintf.xpt file!)

Your message dated Mon, 08 Jan 2007 17:32:09 + with message-id [EMAIL PROTECTED] and subject line Bug#403022: fixed in vlc 0.8.6-svn20061012.debian-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

Bug#399713: marked as done (vlc: FTBFS on GNU/kFreeBSD)

Your message dated Mon, 08 Jan 2007 17:32:09 + with message-id [EMAIL PROTECTED] and subject line Bug#399713: fixed in vlc 0.8.6-svn20061012.debian-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

Bug#189919: marked as done (dvipdfm: remove script issue with dpkg-divert)

Your message dated Mon, 8 Jan 2007 18:55:19 +0100 with message-id [EMAIL PROTECTED] and subject line packaging 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#405425: marked as done (FrSIRT/ADV-2007-0026: vlc: cdio_log_handler() and vcd_log_handler() Format String Vulnerabilities)

Your message dated Mon, 08 Jan 2007 17:32:09 + with message-id [EMAIL PROTECTED] and subject line Bug#405425: fixed in vlc 0.8.6-svn20061012.debian-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

Bug#400720: marked as done (mozilla-plugin-vlc: vlc plugin broken: (no video))

Your message dated Mon, 08 Jan 2007 17:32:09 + with message-id [EMAIL PROTECTED] and subject line Bug#400720: fixed in vlc 0.8.6-svn20061012.debian-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

Bug#405921: marked as done (gonzui: FTBFS: flex: Command not found)

Your message dated Mon, 08 Jan 2007 18:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#405921: fixed in gonzui 1.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 your

Bug#341561: marked as done (RFP: amportal -- asterisk management portal)

Your message dated Mon, 08 Jan 2007 12:00:04 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#344802: marked as done (RFP: gnickr -- GNOME application that manages photos on one's Flickr site as if they are local files on one's system)

Your message dated Mon, 08 Jan 2007 12:00:04 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#345784: marked as done (RFP: klear -- DVB TV application and harddisk-recorder whit timeshifting, EPG with connection to the recording system and many more)

Your message dated Mon, 08 Jan 2007 12:00:06 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#346318: marked as done (RFP: smoothslidesaver -- KDE screensaver using OpenGL that pans and zooms photos with a Ken Burns effect)

Your message dated Mon, 08 Jan 2007 12:00:09 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#344809: marked as done (RFP: prelaunch -- relaunch is a utility written in C and GTK designed to reduce significantly the time needed to launch applications)

Your message dated Mon, 08 Jan 2007 12:00:05 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#339755: marked as done (ITP: mozilla-thunderbird-mailinglistheader -- Display mailing list header fields (RFC 2369) in Thunderbird)

Your message dated Mon, 08 Jan 2007 11:59:46 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#346336: marked as done (ITP: cereal -- a simulator for the Intel 8051 microcontroller)

Your message dated Mon, 08 Jan 2007 11:59:47 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#345959: marked as done (RFP: rnv -- Relax NG Compact Syntax Validator in C)

Your message dated Mon, 08 Jan 2007 12:00:08 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#345813: marked as done (RFP: njbstack -- gnome-vfs module for creative nomad players)

Your message dated Mon, 08 Jan 2007 12:00:08 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#344807: marked as done (RFP: pymou -- A udev specific partition mounter meant for easy mounting of partitions written in python and pygtk)

Your message dated Mon, 08 Jan 2007 12:00:05 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#282538: marked as done (RFP: fixsrcip -- binds local outgoint TCP/UDP sockets to IP addresses)

Your message dated Mon, 08 Jan 2007 12:00:03 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#345977: marked as done (ITP: polld -- Polling demon)

Your message dated Mon, 08 Jan 2007 11:59:47 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#344897: marked as done (RFP: uni-vga -- Unicode VGA font)

Your message dated Mon, 08 Jan 2007 12:00:05 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#344772: marked as done (ITP: qcake -- programming environment and scene editor for 3D games)

Your message dated Mon, 08 Jan 2007 11:59:47 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#280179: marked as done (RFP: simscan -- A simple program that enables qmail-smtpd to reject viruses, spam and block attachments)

Your message dated Mon, 08 Jan 2007 12:00:03 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#331079: marked as done (ITP: hscurses -- Haskell binding to the ncurses library)

Your message dated Mon, 08 Jan 2007 11:59:46 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#344417: marked as done (ITP: freebsd6-buildutils -- Utilities for building FreeBSD 6.x sources)

Your message dated Mon, 08 Jan 2007 11:59:47 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#343729: marked as done (ITP: libjingle -- components to interoperate with Google Talk's P2P and voice calling capabilities)

Your message dated Mon, 08 Jan 2007 11:59:47 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#315229: marked as done (ITP: nautilus-share -- Nautilus Share allows you to quickly share a folder from the GNOME Nautilus file manager without requiring root access)

Your message dated Mon, 08 Jan 2007 11:59:46 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#326797: marked as done (ITP: pentagram -- Engine for Ultima VIII: Pagan)

Your message dated Mon, 08 Jan 2007 11:59:46 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#333718: marked as done (ITP: riot -- information organisation tool)

Your message dated Mon, 08 Jan 2007 11:59:46 -0700 with message-id [EMAIL PROTECTED] and subject line WNPP bug 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

Bug#371066: marked as done (vide: Puts binary in Xorg-7 incompatible directory)

Your message dated Mon, 8 Jan 2007 20:38:51 +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 the

Bug#323609: marked as done (pyne 1.1 (GTK2) is available)

Your message dated Mon, 8 Jan 2007 20:35:27 +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 the

Bug#398153: marked as done (Microtek2: Missing error handler can cause segfaults)

Your message dated Mon, 08 Jan 2007 19:32:04 + with message-id [EMAIL PROTECTED] and subject line Bug#398153: fixed in sane-backends 1.0.18-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#307301: marked as done (Missing manpage)

Your message dated Mon, 8 Jan 2007 20:21:58 +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 the

Bug#329808: marked as done (Couldn't download libgcrypt7)

Your message dated Mon, 8 Jan 2007 20:36:17 +0100 with message-id [EMAIL PROTECTED] and subject line Couldn't download libgcrypt7 has caused the attached Bug report to 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#307302: marked as done (Missing manpage)

Your message dated Mon, 8 Jan 2007 20:22:24 +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 the

Bug#323536: marked as done ('man gtkgraph' typo: documenation)

Your message dated Mon, 8 Jan 2007 20:49:38 +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 the

Bug#356646: marked as done (FTBFS with G++ 4.1: ... was not declared in this scope)

Your message dated Mon, 08 Jan 2007 19:47:02 + with message-id [EMAIL PROTECTED] and subject line Bug#356646: fixed in eboard 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 now your

Bug#373763: marked as done (xserver-xfree86-dbg: Radeon X600 Pro on ChainTech VNF4 PCIE x16 slot not recognised)

Your message dated Mon, 08 Jan 2007 21:00:59 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#373763: xserver-xfree86-dbg: Radeon X600 Pro on ChainTech VNF4 PCIE x16 slot not recognised has caused the attached Bug report to be marked as done. This means that you claim that the

Bug#405991: marked as done (lua-expat: FTBFS: app.c: tests/test.lua:10: attempt to index global 'lxp' (a nil value))

Your message dated Mon, 8 Jan 2007 21:00:10 +0100 with message-id [EMAIL PROTECTED] and subject line Fixed in the just uploaded 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#311241: marked as done ('man btoa' typo: recognices)

Your message dated Mon, 8 Jan 2007 20:48:14 +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 the

Bug#290516: marked as done (webmin-cluster-useradmin: RPC error trying to add a new server)

Your message dated Mon, 8 Jan 2007 20:47:21 +0100 with message-id [EMAIL PROTECTED] and subject line wontfix has caused the attached Bug report to 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#323877: marked as done (tcl-sql automatically removed?)

Your message dated Mon, 8 Jan 2007 20:31:59 +0100 with message-id [EMAIL PROTECTED] and subject line tcl-sql automatically 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

Bug#318895: marked as done (new version available upstream)

Your message dated Mon, 8 Jan 2007 20:28:47 +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 the

Bug#254306: marked as done (eboard: Missing Suggested package: eboard-extras)

Your message dated Mon, 08 Jan 2007 19:47:02 + with message-id [EMAIL PROTECTED] and subject line Bug#254306: fixed in eboard 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 now your

Bug#391464: marked as done (configuration: dim 7 jan 2007 is week 1, according to http://en.wikipedia.org/wiki/Week#Week_number)

Your message dated Mon, 8 Jan 2007 20:40:10 +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 the

Bug#385817: marked as done (other: freenet can't open libc)

Your message dated Mon, 8 Jan 2007 20:39:56 +0100 with message-id [EMAIL PROTECTED] and subject line not in Debian has caused the attached Bug report to 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#141187: marked as done (cupsys-pstoraster: pstoraster dumps stack and aborts)

Your message dated Mon, 8 Jan 2007 20:47:21 +0100 with message-id [EMAIL PROTECTED] and subject line wontfix has caused the attached Bug report to 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#295436: marked as done (cdindex-client: missing man page)

Your message dated Mon, 8 Jan 2007 20:47:51 +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 the

Bug#311346: marked as done (illegal as prefix to (null) (not declared at same block level))

Your message dated Mon, 8 Jan 2007 20:26:40 +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 the

Bug#307636: marked as done (python-tal: dependency on python 2.2 should be on python2.2)

Your message dated Mon, 8 Jan 2007 20:24:02 +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 the

Bug#307304: marked as done (Missing manpage)

Your message dated Mon, 8 Jan 2007 20:23:30 +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 the

Bug#119542: marked as done (libqt-gl-dev: libqt-gl.so is not acceptable)

Your message dated Mon, 8 Jan 2007 20:47:21 +0100 with message-id [EMAIL PROTECTED] and subject line wontfix has caused the attached Bug report to 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#308957: marked as done (Crillee font leaves detritus in current user dictionary)

Your message dated Mon, 8 Jan 2007 20:24:34 +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 the

Bug#253006: marked as done (libkonq3: Uninstallable with apt-get/kpackage)

Your message dated Mon, 8 Jan 2007 20:45:46 +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 the

  1   2   >