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

Installed dump 0.4b6-1 (source i386)



Installed:
dump_0.4b6.orig.tar.gz
  to dists/potato/main/source/utils/dump_0.4b6.orig.tar.gz
  replacing dump_0.4b4.orig.tar.gz
dump_0.4b6-1.diff.gz
  to dists/potato/main/source/utils/dump_0.4b6-1.diff.gz
  replacing dump_0.4b4-13.diff.gz
dump_0.4b6-1.dsc
  to dists/potato/main/source/utils/dump_0.4b6-1.dsc
  replacing dump_0.4b4-13.dsc
dump_0.4b6-1_i386.deb
  to dists/potato/main/binary-i386/utils/dump_0.4b6-1.deb
  replacing dump_0.4b4-13.deb


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

Format: 1.6
Date: Sat,  2 Oct 1999 22:30:05 -0600
Source: dump
Binary: dump
Architecture: source i386
Version: 0.4b6-1
Distribution: unstable
Urgency: low
Maintainer: Bdale Garbee <bdale@gag.com>
Description: 
 dump       - 4.4bsd dump and restore for ext2 filesystems
Closes: 11904 29775 33818 38136 44061
Changes: 
 dump (0.4b6-1) unstable; urgency=low
 .
   * new upstream maintainer, new upstream version, closes: #44061
   * tweak rules file to achieve FHS compliance, lintian cleanliness
   * apply patch from Eirik Fuller <eirik@netcom.com> to allow dumping
     filesystems not listed in /etc/fstab, closes: #11904
   * apply patch from Abhijit Dasgupta <abhijit@ans.net> that prevents access
     to device nodes during restore, closes: #29775
   * apply patch from Eirik Fuller <eirik@netcom.com> relating to dumpdates.
     In 0.4b4-13, I patched dump to only read dumpdates if the 'u' flag was
     specified.  The goal was to avoid failing if dumpdates wasn't yet present
     during a level 0 dump.  The problem is that incrementals *must* read the
     dumpdates file regardless of the state of the 'u' flag, or they end up all
     looking like full dumps.  This new patch ignores the 'u' flag.  Instead,
     it always skips reading dumpdates for a level 0 dump, and requires a valid
     dumpdates be read for an incremental.  Closes: #38136, #33818
   * hard-code the --enable-dumpdates-patch stuff since the upstream configure
     gets it wrong, and we want the functionality.
Files: 
 51a98c0050328c894c05a1ec3030cdc9 541 admin optional dump_0.4b6-1.dsc
 fdc7112bba81fb2b72fce91f83979dab 135030 admin optional dump_0.4b6.orig.tar.gz
 4c5cddf827ba97ce0a676c0706c9fe04 7490 admin optional dump_0.4b6-1.diff.gz
 891fb7788c038714b7a50670c005ab01 64828 admin optional dump_0.4b6-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE39tz+ZKfAp/LPAagRAvatAJ46guu5ePC25t8O3EStpP9HAEs3dwCfZIii
/hPxgd0KQJbJLdgC8Yv+hC4=
=sGbi
-----END PGP SIGNATURE-----


Reply to: