Bug#471347: aptitude-create-state-bundle should tolerate missing $HOME/.aptitude directory
Package: aptitude Version: 0.4.10-1 Severity: wishlist Hi Daniel When running chrooted $HOME/.aptitude may not exist. aptitude-create-state-bundle shouldn't fail in that case. Thanks Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#471347: aptitude-create-state-bundle should tolerate missing $HOME/.aptitude directory
Hi Daniel On Tuesday 18 March 2008 14:19, Daniel Burrows wrote: When running chrooted $HOME/.aptitude may not exist. aptitude-create-state-bundle shouldn't fail in that case. I agree. Could you please describe how it's failing? I just created a test state bundle on a system where I had moved $HOME/.aptitude out of the way. Thanks, Daniel # aptitude-create-state-bundle /tmp/aptitude-state-bundle tar: .//home/andrew/.aptitude: Cannot stat: No such file or directory tar: Error exit delayed from previous errors Hmm. I originally interpreted that error output as meaning that tar had aborted. It has actually succeeded. (I never bothered to look at the output file, just mkdir -p /home/andrew/.aptitude and reran aptitude-create-state-bundle.) Sorry for the noise. Please consider this a wishlist to either validate the existence of paths before passing them to tar, or to swallow the error output from tar. Alternatively just close the bug. Thanks Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#471347: aptitude-create-state-bundle should tolerate missing $HOME/.aptitude directory
On Tue, Mar 18, 2008 at 02:45:50AM +1100, Andrew Vaughan [EMAIL PROTECTED] was heard to say: Package: aptitude Version: 0.4.10-1 Severity: wishlist Hi Daniel When running chrooted $HOME/.aptitude may not exist. aptitude-create-state-bundle shouldn't fail in that case. I agree. Could you please describe how it's failing? I just created a test state bundle on a system where I had moved $HOME/.aptitude out of the way. Thanks, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
