"Borgbackup" <borgbackup-bounces+heiko.helmle=horiba.com at python.org> wrote
on 10.02.2017 14:49:59:
> > this is a strange issue - i get this only on one system (yet). (SLES
12
> > SP2)
> How is that system different from your other systems (on which you use
> the same binary)?
this is the first SLES12SP2 System I tried. The others were CentOS, Ubuntu
and Debian.
> > I'm using borg 1.0.9, the "all in one" binary from the github page and
> > it seems to cut off the last letter from the hostname...
> Give the sha256sum of the binary you use, please.
# sha256sum /usr/local/bin/borg-linux64-1.0.9
9fa23310aa8b08a5d7427970250d9ec0f9512b03bbac32659079df8ae1031764
/usr/local/bin/borg-linux64-1.0.9
there's a symlink to this binary in /usr/local/bin/borg
> That might be a pyinstaller bootloader issue.
> Can you try 1.0.10rc1 ?
tried and that one's better:
# borg-linux64-1.0.10rc1 init ssh://testmachine
usage: borg-linux64-1.0.10rc1 init [-h] [--critical] [--error] [--warning]
[--info] [--debug] [--lock-wait N]
[--show-rc] [--no-files-cache] [--umask
M]
[--remote-path PATH]
[-e {none,keyfile,repokey}] [-a]
[REPOSITORY]
borg-linux64-1.0.10rc1 init: error: argument REPOSITORY: Invalid location
format: "ssh://testmachine"
> Try the normal linux64 binary as well as the pyi321-debug one.
The py321-debug one does it right too.
> > adding a space to the end fixes the name: (well obviously testname
> > doesn't exist, but it's looking up the right name now)
>
> Sounds like an off-by-one error. Just strange this did not surface
before.
Yes - I'm also confused - I used borg on quite a lot of systems and this
is the first that's having this problem. Maybe some environment variable
influencing this that's only set on this system? I didn't find a clue
yet...
Best Regards
Heiko Helmle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/borgbackup/attachments/20170210/814c21ae/attachment-0001.html>