From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Benjamin Slade <beoram@gmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: backup questions
Date: Mon, 20 Aug 2018 00:53:56 +0200 [thread overview]
Message-ID: <20180820005356.611d1605@alma-ubu> (raw)
In-Reply-To: <20180807015708.222ae182@alma-ubu>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
Hi Ben,
On Tue, 7 Aug 2018 01:57:08 +0200
Björn Höfling <bjoern.hoefling@bjoernhoefling.de> wrote:
> Hi Ben,
>
> On Mon, 06 Aug 2018 16:05:28 -0600
> Benjamin Slade <beoram@gmail.com> wrote:
>
> > Two question relating to backup:
> >
>
> [..]
>
> > 2) I don't seem to be able to install `libchip` (for chop-backup).
> > It seems to have no substitute binaries and the local build fails.
> > I've fallen back to using Borg backup for now (which seems good,
> > but more fragile than I'd like, especially in terms of setting up
> > automated bash scripts).
>
>
> This build fails since nearly two years! It seams like nobody is using
> (and thus complaining) this software:
>
>
> https://hydra.gnu.org/job/gnu/master/libchop-0.5.2.x86_64-linux/all
>
> I opened a bug for this:
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32382
>
> Thanks for reporting. Do you have an idea on how to fix it?
>
> Björn
Ludovic fixed the package, so if you do a
guix pull && guix package -i libchop
it should be working now.
But he also wrote that libchop is unmaintained (and what I didn't know:
he's the author :-)).
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-08-19 22:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 22:05 backup questions Benjamin Slade
2018-08-06 22:59 ` Pierre Neidhardt
2018-08-06 23:15 ` Benjamin Slade
2018-08-06 23:57 ` Björn Höfling
2018-08-19 22:53 ` Björn Höfling [this message]
2018-08-21 4:09 ` Benjamin Slade
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180820005356.611d1605@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=beoram@gmail.com \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).