Bug#392285: marked as done (partman-crypto: Installs wrong loop-aes module package)

Your message dated Thu, 12 Oct 2006 08:08:43 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#392285: partman-crypto: Fails to cause cryptomount to be loaded has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#366293: marked as done (bugzilla: With mysql5 queries do not work anymore)

Your message dated Thu, 12 Oct 2006 07:45:25 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug unreproducible has caused the attached Bug report to be 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#391963: marked as done (Does not find libz)

Your message dated Wed, 11 Oct 2006 22:02:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#391963: fixed in hardinfo 0.4.1-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#390587: marked as done (teatime: Typo in package description: "littel" -> "little")

Your message dated Wed, 11 Oct 2006 21:47:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#390587: fixed in teatime 2.6.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 yo

Bug#380913: marked as done (Python transition (#2): you are building a private python module !)

Your message dated Thu, 12 Oct 2006 06:34:12 +0200 with message-id <[EMAIL PROTECTED]> and subject line #380913: Python transition (#2): you are building a private python module ! has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt wi

Bug#387931: marked as done (please package new upstream version of OpenSceneGraph)

Your message dated Thu, 12 Oct 2006 06:04:46 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#387931: openscenegraph: package new 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 i

Bug#392406: marked as done (ships architecture-dependent files in /usr/share)

Your message dated Wed, 11 Oct 2006 20:47:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#392406: fixed in zh-autoconvert 0.3.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 i

Bug#234655: marked as done (nautilus: Nautilus window-size affects gnome-desktop size)

Your message dated Wed, 11 Oct 2006 20:17:22 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#234655: fixed in sawfish 1:1.3+cvs20061004-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Processed: Not a bug!

Processing commands for [EMAIL PROTECTED]: > close 392155 Bug#392155: unionfs: fails to execute programs 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Kapil Hari Paranjape <[EMAIL PROTECTED]> > thanks Stopping processing her

Bug#346429: marked as done (Please update to Kannel CVS)

Your message dated Wed, 11 Oct 2006 19:47:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#346429: fixed in kannel 1.4.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#383396: marked as done ([INTL:pt] Portuguese translation for xapian-bindings (debconf))

Your message dated Wed, 11 Oct 2006 19:02:10 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#383396: fixed in xapian-bindings 0.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 i

Bug#354017: marked as done (Please include "fixed" in xfonts-base package description)

Your message dated Thu, 12 Oct 2006 12:46:51 +1000 with message-id <[EMAIL PROTECTED]> and subject line Please include "fixed" in xfonts-base package description has caused the 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#382933: marked as done ([l10n] Czech translation for xapian-bindings)

Your message dated Wed, 11 Oct 2006 19:02:10 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#382933: fixed in xapian-bindings 0.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 i

Bug#387533: marked as done (xapian-bindings: [INTL:sv] Swedish debconf templates translation)

Your message dated Wed, 11 Oct 2006 19:02:10 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#387533: fixed in xapian-bindings 0.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 i

Bug#362101: marked as done (xfonts-100dpi: FTBFS with xutils 6.9.0)

Your message dated Thu, 12 Oct 2006 12:37:26 +1000 with message-id <[EMAIL PROTECTED]> and subject line xfonts-100dpi: FTBFS with xutils 6.9.0 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#367563: marked as done (xfonts-75dpi: wrong package description)

Your message dated Thu, 12 Oct 2006 12:41:22 +1000 with message-id <[EMAIL PROTECTED]> and subject line xfonts-75dpi: wrong package description has caused the attached Bug report to be 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#380341: marked as done (xapian-bindings: [INTL:fr] French debconf templates translation)

Your message dated Wed, 11 Oct 2006 19:02:10 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#380341: fixed in xapian-bindings 0.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 i

Bug#392496: marked as done (kpsk: Berkeley DB file in /usr/share violates FHS)

Your message dated Thu, 12 Oct 2006 03:49:10 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#392496: Acknowledgement (kpsk: Berkeley DB file in /usr/share violates FHS) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been deal

Bug#380372: marked as done (Uninstallable due to unmet dep on ntp-refclock)

Your message dated Wed, 11 Oct 2006 18:02:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#380372: fixed in radioclk 1.0.ds1-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#380550: marked as done (radioclk: uninstallable, depends on ntp-refclock)

Your message dated Wed, 11 Oct 2006 18:02:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#380372: fixed in radioclk 1.0.ds1-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#381488: marked as done ([Intl:de] Partially translated german po files for man pages)

Your message dated Wed, 11 Oct 2006 17:32:23 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#381488: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#379798: marked as done ([Intl:de] Translated german po file for the man page dpkg-checkbuilddeps.1)

Your message dated Wed, 11 Oct 2006 17:32:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379798: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#378339: marked as done (dpkg: problem with tar and nul characters)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376724: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#375749: marked as done (tar: -: file name read contains nul character)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376351: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#361583: marked as done (FTBFS: too few arguments to function 'gsl_cdf_pascal_Q')

Your message dated Wed, 11 Oct 2006 17:32:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#361583: fixed in ocamlgsl 0.5.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 y

Bug#390875: marked as done (gs-gpl - ps2pdf segfaults with latex generated ps)

Your message dated Wed, 11 Oct 2006 17:47:23 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#390875: fixed in gs-gpl 8.54.dfsg.1-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 n

Bug#293189: marked as done (gs-gpl: fails to interpret certain eps files (Error: /rangecheck in --get--...))

Your message dated Thu, 12 Oct 2006 09:36:21 +0900 with message-id <[EMAIL PROTECTED]> and subject line (no subject) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reo

Bug#376351: marked as done (dpkg-deb: Problem with tar?)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376724: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#376724: marked as done (tar: -: file name read contains nul character)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376724: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#385675: marked as done (dpkg: [INTL:ja] Update Translated Japanese po files for the deb-control(5), dpkg-deb(1), install-info(8) and start-stop-daemon(8))

Your message dated Wed, 11 Oct 2006 17:32:23 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#385675: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#379286: marked as done ([Intl:de] Translated german po file for the man page dpkg.cfg.5)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379286: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#376351: marked as done (dpkg-deb: Problem with tar?)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#375749: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#380660: marked as done ([Intl:de] Translated german po file for the man page dpkg-divert.8)

Your message dated Wed, 11 Oct 2006 17:32:22 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#380660: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#305225: marked as done (gs-gpl: fails with "different polarity already set")

Your message dated Thu, 12 Oct 2006 09:33:49 +0900 with message-id <[EMAIL PROTECTED]> and subject line (no subject) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reo

Bug#375749: marked as done (tar: -: file name read contains nul character)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376724: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#380130: marked as done ([Intl:de] Translated german po file for the man page cleanup-info.8)

Your message dated Wed, 11 Oct 2006 17:32:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#380130: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#379433: marked as done ([Intl:de] Translated german po file for the man page deb-old.5)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379433: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#384163: marked as done (dh_builddeb: change argument order to "tar" call)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376724: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#383448: marked as done (Catalan translation review)

Your message dated Wed, 11 Oct 2006 17:32:23 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#383448: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#385275: marked as done (tar: -: file name contains nul character)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376724: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#374128: marked as done (ITA: trueprint -- pretty printing of source code)

Your message dated Wed, 11 Oct 2006 17:43:04 -0600 with message-id <[EMAIL PROTECTED]> and subject line (no subject) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reo

Bug#385275: marked as done (tar: -: file name contains nul character)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#377279: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#375703: marked as done (Parse, but reject, `Breaks' dependency field)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#375703: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#361635: marked as done (ocamlgsl: FTBFS on kfreebsd-amd64: kfreebsd-amd64 not in the architecture list)

Your message dated Wed, 11 Oct 2006 17:32:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#361635: fixed in ocamlgsl 0.5.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 y

Bug#378339: marked as done (dpkg: problem with tar and nul characters)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376351: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#387821: marked as done ([INTL:it] Typo in Italian translation)

Your message dated Wed, 11 Oct 2006 17:32:23 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#387821: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#380239: marked as done ([Intl:de] Translated german po file for the man page dpkg-name.1)

Your message dated Wed, 11 Oct 2006 17:32:22 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#380239: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#391144: marked as done (Fake bug to collect dselect translation updates before the release)

Your message dated Wed, 11 Oct 2006 17:32:23 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#391144: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#381740: marked as done (dpkg: typo in german translation)

Your message dated Wed, 11 Oct 2006 17:32:23 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#381740: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#379985: marked as done ([Intl:de] Translated german po file for the man page dpkg-scansources.1)

Your message dated Wed, 11 Oct 2006 17:32:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379985: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#381047: marked as done ([Intl:de] Translated german po file for the man page dpkg.1)

Your message dated Wed, 11 Oct 2006 17:32:22 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#381047: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#377279: marked as done (dpkg-deb -b causes tar to emit warning)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#377279: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#377279: marked as done (dpkg-deb -b causes tar to emit warning)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#375749: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#382308: marked as done (dselect: bogus warning at start of helpmsgs.{cc,h})

Your message dated Wed, 11 Oct 2006 17:32:23 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#382308: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#377279: marked as done (dpkg-deb -b causes tar to emit warning)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376724: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#378339: marked as done (dpkg: problem with tar and nul characters)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#375749: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#376724: marked as done (tar: -: file name read contains nul character)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#375749: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#392361: marked as done (ocamlgsl: Please package new upstream version)

Your message dated Wed, 11 Oct 2006 17:32:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#392361: fixed in ocamlgsl 0.5.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 y

Bug#392402: marked as done (ships architecture-dependent files in /usr/share)

Your message dated Wed, 11 Oct 2006 16:47:48 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#392402: fixed in sufary 2.1.1-7.1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#379298: marked as done ([Intl:de] Translated german po file for the man page dselect.cfg.5)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379298: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#376724: marked as done (tar: -: file name read contains nul character)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#377279: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#375749: marked as done (tar: -: file name read contains nul character)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#377279: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#384163: marked as done (dh_builddeb: change argument order to "tar" call)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#377279: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#391143: marked as done (dpkg: Fake bug to collect last dpkg translation updates before the release)

Your message dated Wed, 11 Oct 2006 17:32:23 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#391143: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#376724: marked as done (tar: -: file name read contains nul character)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376351: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#379417: marked as done ([Intl:de] Translated german po file for the man page 822-date.1)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379417: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#384163: marked as done (dh_builddeb: change argument order to "tar" call)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#375749: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#385275: marked as done (tar: -: file name contains nul character)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376351: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#279403: marked as done (gs-gpl: Cannot open updated PDF files)

Your message dated Thu, 12 Oct 2006 09:37:00 +0900 with message-id <[EMAIL PROTECTED]> and subject line (no subject) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reo

Bug#381349: marked as done ([Intl:de] Translated german po file for the man page dpkg-architecture.1)

Your message dated Wed, 11 Oct 2006 17:32:23 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#381349: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#384768: marked as done (dpkg: [INTL:ja] Update Translated Japanese po files for the dpkg-divert(8) and dpkg-query(1))

Your message dated Wed, 11 Oct 2006 17:32:23 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#384768: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#379825: marked as done ([Intl:de] Translated german po file for the man page dpkg-scanpackages.1)

Your message dated Wed, 11 Oct 2006 17:32:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379825: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#263477: marked as done (gs-gpl: pngalpha not documented)

Your message dated Thu, 12 Oct 2006 09:53:53 +0900 with message-id <[EMAIL PROTECTED]> and subject line (no subject) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reo

Bug#380443: marked as done ([Intl:de] Translated german po file for the man page deb-control.5)

Your message dated Wed, 11 Oct 2006 17:32:22 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#380443: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#384163: marked as done (dh_builddeb: change argument order to "tar" call)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376351: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#377279: marked as done (dpkg-deb -b causes tar to emit warning)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376351: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#384843: marked as done ([Intl:de] dselect German translation update)

Your message dated Wed, 11 Oct 2006 17:32:23 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#384843: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#368773: marked as done (libocamlgsl-ocaml: ocaml package updated: please build a new binary package)

Your message dated Wed, 11 Oct 2006 17:32:32 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#368773: fixed in ocamlgsl 0.5.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 y

Bug#379661: marked as done ([Intl:de] Translated german po file for the man page deb.5)

Your message dated Wed, 11 Oct 2006 17:32:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379661: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#376351: marked as done (dpkg-deb: Problem with tar?)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#376351: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#375749: marked as done (tar: -: file name read contains nul character)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#375749: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#379030: marked as done (dpkg: German man pages are missing)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#379030: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#378339: marked as done (dpkg: problem with tar and nul characters)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#377279: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#385275: marked as done (tar: -: file name contains nul character)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#375749: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#380365: marked as done ([Intl:de] Translated german po file for the man page dpkg-statoverride.8)

Your message dated Wed, 11 Oct 2006 17:32:22 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#380365: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#376351: marked as done (dpkg-deb: Problem with tar?)

Your message dated Wed, 11 Oct 2006 17:32:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#377279: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#388837: marked as done (dpkg: [INTL:ja] Update Translated Japanese manpages)

Your message dated Wed, 11 Oct 2006 17:32:23 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#388837: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#381141: marked as done (dpkg: [INTL:ja] Update Translated Japanese po files for the 822-date(1), deb(5), deb-old(5) and dpkg-checkbuilddeps(1))

Your message dated Wed, 11 Oct 2006 17:32:22 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#381141: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#381865: marked as done (dpkg: [INTL:ja] Update Translated Japanese po files for the cleanup-info(8), dpkg-name(1), dpkg-scanpackages(1) and dpkg-statoverride(8))

Your message dated Wed, 11 Oct 2006 17:32:23 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#381865: fixed in dpkg 1.13.23 has caused the attached Bug report to be 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#262263: marked as done (discus: dies reading partition in unaccessable directory)

Your message dated Thu, 12 Oct 2006 01:10:14 +0200 with message-id <[EMAIL PROTECTED]> and subject line discus: Unable to verify bugs 262263 has caused the attached Bug report to be 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#392180: marked as done (FTBFS: ERROR: could not build a simple Qt program)

Your message dated Wed, 11 Oct 2006 16:32:58 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#392180: fixed in qbrew 0.3.9-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#387231: marked as done (libnss-mdns: Wrong sysconfdir(/usr/etc) and localstatedir(/usr/var))

Your message dated Wed, 11 Oct 2006 14:35:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#387231: fixed in nss-mdns 0.8-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 you

Bug#353131: marked as done (libnss-mdns shouldn't recommend zeroconf)

Your message dated Wed, 11 Oct 2006 14:35:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#353131: fixed in nss-mdns 0.8-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 you

Bug#390417: marked as done (can't play certain mp3 files if maxFrames is not determined)

Your message dated Wed, 11 Oct 2006 14:35:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#390417: fixed in mpd 0.12.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#357168: marked as done (libsqlite0: new upstream release available (2.8.17, 2005-Dec-19))

Your message dated Wed, 11 Oct 2006 14:36:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#357168: fixed in sqlite 2.8.17-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#351990: marked as done (mDNS should not be in /etc/nsswitch.conf by default)

Your message dated Wed, 11 Oct 2006 14:35:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#351990: fixed in nss-mdns 0.8-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 you

Bug#392001: marked as done (collatinus: Possible Depends on obsolete python-wxgtk2.4)

Your message dated Wed, 11 Oct 2006 14:32:40 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#392001: fixed in collatinus 7.14-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#388856: marked as done (please make list in description render nicely in aptitude)

Your message dated Wed, 11 Oct 2006 14:32:45 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#388856: fixed in devscripts 2.9.22 has caused the attached Bug report to be 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#389482: marked as done (devscripts: [dget] please add support for ~ in package version)

Your message dated Wed, 11 Oct 2006 14:32:45 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#389482: fixed in devscripts 2.9.22 has caused the attached Bug report to be 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#391995: marked as done (xkb-data: Please add quotes to us (alt-intl))

Your message dated Wed, 11 Oct 2006 15:03:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#391995: fixed in xkeyboard-config 0.9-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

  1   2   >