Centos Repo down?


$ yum install yum-plugin-copr
$ yum copr enable copart/restic
$ yum install restic

I used the above to install on CentOS 7
Today I got messages like;

https://copr-be.cloud.fedoraproject.org/results/copart/restic/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://copr-be.cloud.fedoraproject.org/results/copart/restic/epel-7-x86_64/repodata/repomd.xml: (28, ‘Connection timed out after 30002 milliseconds’)

Besides that it is a bit annoying while using yum, I hope this is being fixed since it’s the way to install restic on CentOS…


Network timeouts can happen from time to time. Simply try again later. If the issue still persists after a few hours you could reach out to the Fedora Infrastructure Team.

Please also note that the copr repo for restic is not official. In case of issues you’d better contact the maintainer.

If you need a quick way to install restic you can always download the official binary at Github, unpack and drop it into a folder in your $PATH (e.g. /usr/local/bin). That’s all that is needed to run restic.


Which binary from the official binary list should I use on CentOS?
I’m not sure which of the versions applies to this operating system…


Most likely the binary ending in restic_0.9.0_linux_amd64.bz2, you can check with uname -m:

  • x86_64 -> restic_0.9.0_linux_amd64
  • x86 -> restic_0.9.0_linux_386

I hope this helps!

If you have any idea how/whom to bug about the repo, please do that (or let us know)


Result: x86_64
So I guess restic_0.9.0_linux_amd64

I just download that file to my server, extract it, rename restic_0.9.0_linux_amd64 to restic. put it in /usr/bin/ resulting in /usr/bin/restic and everything should be fine?

restic 0.9.0 released

This seems to do the trick:

wget https://github.com/restic/restic/releases/download/v0.9.0/restic_0.9.0_linux_amd64.bz2
bzip2 -d restic_0.9.0_linux_amd64.bz2
yes | cp restic_0.9.0_linux_amd64 /usr/bin/restic

Version is now: restic 0.9.0 compiled with go1.10.2 on linux/amd64
Daily backup will run tonight, so hopefully all goes well


@MrMoronIV I just replied to your comment over here