Freshness check blocks upgrading

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

>

> Andreas

>

>

>

>

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

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

> Andreas Enge (2016-02-19 20:12 +0300) 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 totally agree with this! I didn't like it since the very beginning.

> Alex Kost <alezost@gmail.com> skribis:

>

>> Andreas Enge (2016-02-19 20:12 +0300) 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 totally agree with this! I didn't like it since the very beginning.

>

> I agree. I implemented it mostly for the fun of it and to demonstrate

> that we could possibly do “clever” things with access to high-level

> package objects (the command could automatically offer to use the new

> source instead of the old one), but in practice it’s been largely

> annoying.

>

> Ludo’, waiting for the patch that removes it. :-)

> Attached. I also removed 'check-package-freshness' from (gnu packages)

> as it is not used anywhere else, or should it be left?

> Attached. I also removed 'check-package-freshness' from (gnu packages)

> as it is not used anywhere else, or should it be left?

> From 1d6d4d0864672b0676f09eb6c8285684e5b8785c Mon Sep 17 00:00:00 2001

> From: Alex Kost <alezost@gmail.com>

> Date: Tue, 23 Feb 2016 11:38:00 +0300

> Subject: [PATCH] Do not check package freshness during upgrade.

>

> Fixes <http://bugs.gnu.org/22740>.

> Reported by Andreas Enge <andreas@enge.fr>.

>

> * gnu/packages.scm (waiting, ftp-open*, check-package-freshness): Remove.

> * guix/scripts/package.scm (options->installable): Adjust accordingly.

> * emacs/guix-main.scm (package->manifest-entry*): Likewise.

> On Tue, Feb 23, 2016 at 11:54:30AM +0300, Alex Kost wrote:

>> Attached. I also removed 'check-package-freshness' from (gnu packages)

>> as it is not used anywhere else, or should it be left?

>

> I think it is good, please push. (Assuming that "guix refresh" still

> works and none of the procedures you remove are still used.)

> Alex Kost <alezost@gmail.com> skribis:

>

>> Attached. I also removed 'check-package-freshness' from (gnu packages)

>> as it is not used anywhere else, or should it be left?

>

> It’s fine to remove it.