From: Leo Famulari <leo@famulari.name>
To: HiPhish <hiphish@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: Borg takes forever to upgrade
Date: Thu, 14 Mar 2019 16:31:15 -0400 [thread overview]
Message-ID: <20190314203115.GA20373@jasmine.lan> (raw)
In-Reply-To: <3878643.TA5XZMSakg@aleksandar-ixtreme-m5740>
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
On Thu, Mar 14, 2019 at 09:12:58PM +0100, HiPhish wrote:
> 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.
It's probably stuck in the tests:
https://github.com/borgbackup/borg/issues/4350
Whether or not it gets stuck seems host-specific. It works on some
machines and not others. I recommend just waiting a while for a
substitute to become available.
I don't want to disable the tests here until we understand what's going
on — otherwise we might miss some real issue in how the software is
being built on the machines where the tests get stuck.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
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 [this message]
2019-03-14 22:09 ` HiPhish
2019-04-22 21:19 ` Christopher Lemmer Webber
2019-03-14 20:39 ` Tobias Geerinckx-Rice
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
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=20190314203115.GA20373@jasmine.lan \
--to=leo@famulari.name \
--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.
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).