unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Leo Famulari <leo@famulari.name>
Cc: 22740@debbugs.gnu.org
Subject: bug#22740: Freshness check blocks upgrading
Date: Sat, 20 Feb 2016 10:13:14 +0100	[thread overview]
Message-ID: <87y4af4udx.fsf@mdc-berlin.de> (raw)
In-Reply-To: <20160220062505.GA14544@jasmine>


Leo Famulari <leo@famulari.name> writes:

> On Fri, Feb 19, 2016 at 06:12:09PM +0100, Andreas Enge wrote:
>> Hello,
>> 
>> when upgrading packages, there is a check for new GNU releases.
>> In the presence of network problems preventing to reach the corresponding
>> servers, the command "guix package -u" hangs indefinitely.
>> 
>> It would be nice to add a (short) time-out to the procedure looking
>> for updates, or better yet, to add a command line flag to turn it off:
>> Even when the servers are reachable, checking for new versions takes
>> a considerable amount of time that can be saved in many circumstances.
>> 
>> Personally, I would not even mind turning this feature off completely;
>> I think we update packages sufficiently often and the message is rather
>> distracting.
>
> It does seem out of place while upgrading. It could be considered
> extraneous to the features of `guix refresh`.

I agree.  It seems to better fit with “guix refresh”.

  reply	other threads:[~2016-02-20  9:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19 17:12 bug#22740: Freshness check blocks upgrading Andreas Enge
2016-02-20  6:25 ` Leo Famulari
2016-02-20  9:13   ` Ricardo Wurmus [this message]
2016-02-20  8:30 ` Alex Kost
2016-02-22 21:16   ` Ludovic Courtès
2016-02-23  8:54     ` Alex Kost
2016-02-23  9:18       ` Andreas Enge
2016-02-24 15:59         ` Alex Kost
2016-02-23 17:07       ` Ludovic Courtès

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=87y4af4udx.fsf@mdc-berlin.de \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=22740@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).