From: Tobias Geerinckx-Rice <me@tobias.gr>
To: HiPhish <hiphish@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: Borg takes forever to upgrade
Date: Thu, 14 Mar 2019 21:39:06 +0100 [thread overview]
Message-ID: <87pnqt9onp.fsf@nckx> (raw)
In-Reply-To: <3878643.TA5XZMSakg@aleksandar-ixtreme-m5740>
HiPhish,
HiPhish wrote:
> Hello everyone,
>
> I was trying to upgrade my packages and Borg (the backup
> program) has been
> taking over an hour already.
[…]
> I have eventually decided to cancel the upgrade
> process and tried upgrading all packages except Borg. The
> upgrade process
> finished without problems in a reasonable amount of time, so it
> is definitely
> Borg where things get stuck.
Interrupting after an hour is a bit too soon to say it's stuck.
Just from experience, many backup programmes tend to have long
test suites (a trait which they share with many databases and
compressors, probably because they're a bit of both). The build
was chugging along. What did the log say was happening?
What is strange here is that you didn't get a substitute for Borg.
I did[0]. Are you deliberately building Borg locally?
Kind regards,
T G-R
[0]: For
/gnu/store/qplgyx9h65k509l02bfc4cz9dlid00ck-borg-1.1.9.drv
→ /gnu/store/5fazf5kwalvv3r4bin74fzgxp8hmfdha-borg-1.1.9
which is a graft of
/gnu/store/pgib6ji5792y739jwv90zk679jqxji1q-borg-1.1.9
next prev parent reply other threads:[~2019-03-14 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 20:12 Borg takes forever to upgrade HiPhish
2019-03-14 20:31 ` Leo Famulari
2019-03-14 22:09 ` HiPhish
2019-04-22 21:19 ` Christopher Lemmer Webber
2019-03-14 20:39 ` Tobias Geerinckx-Rice [this message]
2019-03-14 22:15 ` HiPhish
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnqt9onp.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=hiphish@posteo.de \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.