Your message dated Tue, 22 Nov 2016 22:11:32 -0600
with message-id <87fumi4yyz....@trouble.defaultvalue.org>
and subject line Re: Bug#844324: bup: bup join produces invalid tar output
has caused the Debian Bug report #844324,
regarding bup: bup join produces invalid tar output
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 ow...@bugs.debian.org
immediately.)
--
844324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bup
Version: 0.25-1
Severity: serious
Dear Maintainer,
Here's a transcript of a session to illustrate the problem:
renn:/tmp$ mkdir test
renn:/tmp$ echo xxx>test/xxx
renn:/tmp$ bup -d test.bup init
Initialized empty Git repository in /tmp/test.bup/
renn:/tmp$ bup -d test.bup index /tmp/test
Indexing: 2, done.
renn:/tmp$ bup -d test.bup save -n t1 /tmp/test
Reading index: 2, done.
Saving: 100.00% (4/4k, 2/2 files), done.
bloom: creating from 1 file (8 objects).
renn:/tmp$ bup -d test.bup ls
t1/
renn:/tmp$ bup -d test.bup ls t1
2016-11-14-132249@ latest@
renn:/tmp$ bup -d test.bup join t1 | tar tf -
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
The command `bup -d test.bup join t1` should send a tar file to stdout;
what is being sent looks a bit like one, but obviously isn't quite.
I have marked this as "serious" because I believe this is the only way
to directly restore a remote backup.
-- System Information:
Debian Release: 8.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages bup depends on:
ii git 1:2.1.4-2.1+deb8u2
ii libc6 2.19-18+deb8u6
ii par2 0.6.11-1
ii python 2.7.9-1
ii python-pylibacl 0.5.2-1
ii python-pyxattr 0.5.3-1
ii python2.7 2.7.9-2+deb8u1
pn python:any <none>
Versions of packages bup recommends:
ii bup-doc 0.25-1
ii python-fuse 2:0.2.1-10
ii python-tornado 4.2.0-1~bpo8+1
bup suggests no packages.
-- no debconf information
--
John
--- End Message ---
--- Begin Message ---
John Kozak <j...@thameslighter.net> writes:
> The command `bup -d test.bup join t1` should send a tar file to stdout;
Hmm, bup doesn't yet have support for tar output, though I do have an
experimental branch supporting "bup export-tar". And while remote
restore is certainly high on the to-do list, it's not implemented yet,
either for saves from a remote to the local filesystem, or the reverse.
Further, "bup split " and "bup join" are currently, completely
incompatible with "bup save" and "bup restore". They're doing two
different things. If you want join to produce a tar file, then you'll
have to save that tar file via split. See the EXAMPLES in the split and
join manpages.
Finally, join doesn't currently understand VFS save names. It accepts
git references, not VFS paths.
Hope this helps.
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
--- End Message ---
