Your message dated Sun, 15 Apr 2007 15:47:13 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#418939: fixed in memtest86 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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: memtest86
Severity: wishlist

Hi,

there is a new upstream release available, 3.3 namely. Would be nice if
you can update your package to it.

Regards,
Daniel

-- 
Address:        Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:          [EMAIL PROTECTED]
Internet:       http://people.panthera-systems.net/~daniel-baumann/


--- End Message ---
--- Begin Message ---
Source: memtest86
Source-Version: 3.3-1

We believe that the bug you reported is fixed in the latest version of
memtest86, which is due to be installed in the Debian FTP archive:

memtest86_3.3-1.diff.gz
  to pool/main/m/memtest86/memtest86_3.3-1.diff.gz
memtest86_3.3-1.dsc
  to pool/main/m/memtest86/memtest86_3.3-1.dsc
memtest86_3.3-1_i386.deb
  to pool/main/m/memtest86/memtest86_3.3-1_i386.deb
memtest86_3.3.orig.tar.gz
  to pool/main/m/memtest86/memtest86_3.3.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yann Dirson <[EMAIL PROTECTED]> (supplier of updated memtest86 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 15 Apr 2007 17:23:13 +0200
Source: memtest86
Binary: memtest86
Architecture: source i386
Version: 3.3-1
Distribution: unstable
Urgency: low
Maintainer: Yann Dirson <[EMAIL PROTECTED]>
Changed-By: Yann Dirson <[EMAIL PROTECTED]>
Description: 
 memtest86  - thorough real-mode memory tester
Closes: 372570 377727 383635 418939
Changes: 
 memtest86 (3.3-1) unstable; urgency=low
 .
   * New upstream release (Closes: #418939).
   * Updated debian/watch for new website layout.
   * In non-interactive mode, don't ask the user whether to run lilo on
     update (Holger Mense - Closes: #383635).
   * Fixed typo in extended description (Adrian Knoth - Closes: #377727).
   * Reference memtester instead of sysutils in Suggests and extended
     description (Benjamin Mesing - Closes: #372570).
   * Rework extended description some more: memtest86+ is not any more
     "more actively maintained upstream", and probably noone cares about
     the old history of this package and memmxtest.
   * Sync packaging with memtest86+-1.70:
     * added note about assumed fs layout in grub conf example.
     * avoid non-portable "read -p" in postinst.
     * avoid non-portable "-o" in test(1) call in postinst.
     * use dh-buildinfo.
   * Remove build-dependency on gcc-3.2, build with current gcc.
   * Switch to debhelper v5 (no change).
   * Updated FSF address in debian/copyright.
   * Bumped Standards-Version to 3.7.2 (no change).
Files: 
 25aa3f310eec72ee003779fd4395b504 578 misc optional memtest86_3.3-1.dsc
 52e35228b60431ef474bbb5125ca1201 137922 misc optional memtest86_3.3.orig.tar.gz
 8ac1a662b7f0a1a52ec077304162f6e6 6055 misc optional memtest86_3.3-1.diff.gz
 7c2cdfe94950abcd32bcfb315113eb58 61682 misc optional memtest86_3.3-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGIkRkV1uVslwzwbgRAn+KAJ4okrEYYfYMfob27/YTVLojCFvQWwCffAa/
x2QlUSaUylKWQJNfhkgMVtM=
=Fy/9
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to