unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: HiPhish <hiphish@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: Borg takes forever to upgrade
Date: Mon, 22 Apr 2019 17:19:28 -0400	[thread overview]
Message-ID: <8736m9n3fj.fsf@dustycloud.org> (raw)
In-Reply-To: <67513244.nM5SvtCJyr@aleksandar-ixtreme-m5740>

HiPhish writes:

> On Thursday, 14 March 2019 21:31:15 CET you wrote:
>> 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.
> Sounds plausible. I'll just wait then, it's not like I need the update 
> urgently.
>
>> 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.
> Yes, sounds reasonable.

I'll note that I hit this problem today too.  I did a guix package
upgrade and came back about 6 hours later to see what packages had been
upgraded.  Sadly it had spent all day spinning its wheels on Borg. :(

  reply	other threads:[~2019-04-22 21:19 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 [this message]
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=8736m9n3fj.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --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).