Uploaded dump 0.4b6-1 (alpha) to master
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.6
Date: Sat, 2 Oct 1999 22:30:05 -0600
Source: dump
Binary: dump
Architecture: alpha
Version: 0.4b6-1
Distribution: unstable
Urgency: low
Maintainer: AlphaBuildd/John Goerzen <buildd@complete.org>
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:
97ef2abf3536b5ca9ae1becd66807bde 90728 admin optional dump_0.4b6-1_alpha.deb
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQEVAwUBN/n57tYJEdzpssC9AQHV1wgApiaRy7KckMIXPSBwOBeJk2KRHevmILLr
pgQNYWQQ4DYDWW6ZpbbpUySqkg22u5hI/pWOgOdrTnmxiRkSuDEJKMbRuTwI+Ct+
DU8u4urM3OMQst0oS/loeyo1Ud5M1SLWcJrHYuZdC1jmqnLbLD/w67KcPVij89Tu
g6/GcHksLHchsbt9NtVJCDCH2a4/iFlKtwtGvRTYbeF7BY9JmlivtVRGDYLnrOI5
z18kG+Avvk+xdC6KkTfP1bJPT8jxv+JMw09+NukoCeGHDj9RHDMp8k+rdrl+NBqz
IatUPVbvWEXO47ICfywOB2m0ENj7QioHTKplDZMHAMGH1vrJkZJo+Q==
=C5LF
-----END PGP SIGNATURE-----
Reply to: