Your message dated Sun, 05 Sep 2010 09:06:18 +0000
with message-id <[email protected]>
and subject line Bug#591865: fixed in minicom 2.4-3
has caused the Debian Bug report #591865,
regarding minicom: package purge (after dependencies removal) fails
to be 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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
591865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591865
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: minicom
Version: 2.4-2
Severity: serious
User: [email protected]
Usertags: instest-20100731 instest

Hi,

While testing the installation of all packages in unstable, I ran
into the following problem:

> -- Removing all dependencies: OK
> Reading package lists...
> Building dependency tree...
> Reading state information...
> The following packages will be REMOVED:
> lrzsz
> 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
> After this operation, 287kB disk space will be freed.
> (Reading database ... 9969 files and directories currently installed.)
> Removing lrzsz ...
> -- Purging package: FAILED
> (Reading database ... 9947 files and directories currently installed.)
> Removing minicom ...
> Purging configuration files for minicom ...
> /var/lib/dpkg/info/minicom.postrm: 92: cannot create /dev/tty: No such device 
> or address
> dpkg: error processing minicom (--purge):
> subprocess installed post-removal script returned error exit status 2
> Errors were encountered while processing:
> minicom

The full build log is available from:
 http://people.debian.org/~lucas/logs/2010/07/31/minicom.log

It is reproducible by installing your package in a clean chroot, using
the debconf Noninteractive frontend, and priority: critical.

This test was carried out using about 50 AMD64 nodes of the Grid'5000
platform.  Internet was not accessible from the nodes.

-- 
| Lucas Nussbaum
| [email protected]   http://www.lucas-nussbaum.net/ |
| jabber: [email protected]             GPG: 1024D/023B3F4F |



--- End Message ---
--- Begin Message ---
Source: minicom
Source-Version: 2.4-3

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

minicom_2.4-3.diff.gz
  to main/m/minicom/minicom_2.4-3.diff.gz
minicom_2.4-3.dsc
  to main/m/minicom/minicom_2.4-3.dsc
minicom_2.4-3_amd64.deb
  to main/m/minicom/minicom_2.4-3_amd64.deb



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.
Martin A. Godisch <[email protected]> (supplier of updated minicom 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.8
Date: Sun, 05 Sep 2010 10:30:00 +0200
Source: minicom
Binary: minicom
Architecture: source amd64
Version: 2.4-3
Distribution: unstable
Urgency: medium
Maintainer: Martin A. Godisch <[email protected]>
Changed-By: Martin A. Godisch <[email protected]>
Description: 
 minicom    - friendly menu driven serial communication program
Closes: 590900 591865
Changes: 
 minicom (2.4-3) unstable; urgency=medium
 .
   * Fixed failing package purge, closes: #591865.
     Thanks to Alexander Korsunsky.
   * Fixed setting localecho in config file (upstream backport),
     closes: #590900. Thanks to Peter De Wachter.
Checksums-Sha1: 
 7f8cb52ca20e40e3cdb4c722769cbc72ceb761f9 1002 minicom_2.4-3.dsc
 f2bbdbfcd8fed0c6914bfea3aaa2cef6ba320106 12066 minicom_2.4-3.diff.gz
 ff219a1b060d98842993eb36996b73cd573980c9 321392 minicom_2.4-3_amd64.deb
Checksums-Sha256: 
 2c4b4c4588d5ed1e23f0cea0f9ed1b8595eb1db5d96f397ae4193c266a3dcd2d 1002 
minicom_2.4-3.dsc
 5af47237b605842f79992a0d64f993b507c34dcbb348aa013d6995f2ab62add5 12066 
minicom_2.4-3.diff.gz
 dbcc5d5a4a00fdf4aae6f480a5afc0e1f4349bbec47b2fdd2abc758a562d910c 321392 
minicom_2.4-3_amd64.deb
Files: 
 32d624e5974c1f33c1dbf787e282943c 1002 comm optional minicom_2.4-3.dsc
 f01cf3e630775813dee29e3f06f750e0 12066 comm optional minicom_2.4-3.diff.gz
 83eb89736cc13b1d18855de847b4e859 321392 comm optional minicom_2.4-3_amd64.deb

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

iEYEARECAAYFAkyDVY8ACgkQhOZKoAn8AVwjVACgxg1xewZbGxgA1VASvhaNSDqb
fhwAnjo6BW5vOqSohurbKKVxmPUN5c7c
=+tTs
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to