Your message dated Sun, 17 Dec 2017 09:38:23 +0000
with message-id <[email protected]>
and subject line Bug#884581: Removed package(s) from unstable
has caused the Debian Bug report #676878,
regarding tutorial: please add a bit about backing up whole systems
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.)
--
676878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676878
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: obnam
Version: 1.0-1~squeeze1
Severity: wishlist
Hello,
thank you for obnam.
I've just spent some time trying to set up encrypted backup for my whole
system, and it wasn't so straightforward. Here's a list of gotchas:
- you need root, which means your usual keyring isn't accessible, and
gpg-agent likely won't work because it's been run as the user you use for
the X session, and obnam runs gpg in batch mode and won't give it a way to
ask for a passphrase. So you *need* a passphraseless key. Which in turn
needs to be encrypted with some password for storage elsewhere.
- backup is best done with specifying entire file systems, rather than dirs.
--one-file-system works there, but it's nice to show how one can backup
multiple file systems using --one-file-system, just by listing multiple
backup locations. That wasn't hard, I know, but you cannot be sure if obnam
behaves like tar until you try :)
- if I want to put my backup strategy entirely in the config file, there are
no examples of providing bool options there. "one-file-system = True" seems
to work.
- also, there is no documentation on how to provide multiple locations to
--root (thanks to your support on IRC, I now know it's a comma-separated
list)
My resulting .obnam.conf:
[config]
one-file-system = True
repository = /media/backups/HOSTNAME
log = /root/obnam.log
encrypt-with = KEYID
root = /home, /
I'm sorry I cannot offer to write the tutorial myself as I'm in the middle of
some disaster recovery after a laptop failure. Gotta back up the only remaining
copy of all my data before it's too late.
Ciao,
Enrico
-- System Information:
Debian Release: 6.0.5
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages obnam depends on:
ii libc6 2.13-30 Embedded GNU C Library: Shared lib
ii python 2.6.6-3+squeeze7 interactive high-level object-orie
ii python-cliapp 0.29-1~squeeze1 Python framework for Unix command
ii python-larch 1.20120527-1~squeeze1 B-tree library for Python
ii python-paramiko 1.7.6-5 Make ssh v2 connections with Pytho
ii python-tracing 0.6-2~bpo60+1 Python debug tracing helper
ii python-ttystatus 0.18-1~squeeze1 terminal progress bar and status o
ii python2.6 2.6.6-8+b1 An interactive high-level object-o
obnam recommends no packages.
obnam suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.22-1+rm
Dear submitter,
as the package obnam has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/884581
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)
--- End Message ---
