[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#379676: marked as done (ITP: vbindiff -- visual binary diff, visually compare binary files)



Your message dated Thu, 27 Jul 2006 06:11:32 -0700
with message-id <E1G65eG-00031H-Fa@spohr.debian.org>
and subject line Bug#379676: fixed in vbindiff 3.0-beta1-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: wnpp
Severity: wishlist
Owner: Miriam Ruiz <little_miry@yahoo.es>


* Package name    : vbindiff
  Version         : 3.0 beta 1
  Upstream Author : Christopher J. Madsen <cjm@pobox.com>
* URL             : http://home.comcast.net/~chris-madsen/vbindiff/
* License         : GPL
  Programming Lang: C
  Description     : visual binary diff, visually compare binary files

 Visual Binary Diff (VBinDiff) displays files in hexadecimal and ASCII (or
 EBCDIC). It can also display two files at once, and highlight the
 differences between them. Unlike diff, it works well with large files (up
 to 4 GB)

 VBinDiff was inspired by the Compare Files function of the ProSel utilities
 by Glen Bredon, for the Apple II. The single-file mode was inspired by the
 LIST utility of 4DOS and friends.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)


--- End Message ---
--- Begin Message ---
Source: vbindiff
Source-Version: 3.0-beta1-1

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

vbindiff_3.0-beta1-1.diff.gz
  to pool/main/v/vbindiff/vbindiff_3.0-beta1-1.diff.gz
vbindiff_3.0-beta1-1.dsc
  to pool/main/v/vbindiff/vbindiff_3.0-beta1-1.dsc
vbindiff_3.0-beta1-1_i386.deb
  to pool/main/v/vbindiff/vbindiff_3.0-beta1-1_i386.deb
vbindiff_3.0-beta1.orig.tar.gz
  to pool/main/v/vbindiff/vbindiff_3.0-beta1.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 379676@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Miriam Ruiz <little_miry@yahoo.es> (supplier of updated vbindiff 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 ftpmaster@debian.org)


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

Format: 1.7
Date: Tue, 25 Jul 2006 00:07:15 +0200
Source: vbindiff
Binary: vbindiff
Architecture: source i386
Version: 3.0-beta1-1
Distribution: unstable
Urgency: low
Maintainer: Miriam Ruiz <little_miry@yahoo.es>
Changed-By: Miriam Ruiz <little_miry@yahoo.es>
Description: 
 vbindiff   - visual binary diff, visually compare binary files
Closes: 379676
Changes: 
 vbindiff (3.0-beta1-1) unstable; urgency=low
 .
   * Initial release (Closes: #379676)
Files: 
 a78d748de3927b62ad736ff7aa6e6a07 606 utils optional vbindiff_3.0-beta1-1.dsc
 a003ab76c596f47ea14d9e8ec82e5ad9 106317 utils optional vbindiff_3.0-beta1.orig.tar.gz
 62e705a72ab4210da5a1b0e0b87ae711 2255 utils optional vbindiff_3.0-beta1-1.diff.gz
 28f8e72fae0f6c8e5cbe197615636aa9 25782 utils optional vbindiff_3.0-beta1-1_i386.deb

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

iD8DBQFExirXxRSvjkukAcMRAqAJAJ9o75o/I9IDsekzSx4cbLFpwckUygCgvx8Q
GKOBd6Xl3qBQqgf0UcU8z94=
=Z6Xy
-----END PGP SIGNATURE-----


--- End Message ---

Reply to: