GNU bug report logs -
#22740
Freshness check blocks upgrading
Previous Next
Reported by: Andreas Enge <andreas <at> enge.fr>
Date: Fri, 19 Feb 2016 17:13:01 UTC
Severity: normal
Fixed in version 0.9.1
Done: ludo <at> gnu.org (Ludovic Courtès)
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 22740 in the body.
You can then email your comments to 22740 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#22740
; Package
guix
.
(Fri, 19 Feb 2016 17:13:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Andreas Enge <andreas <at> enge.fr>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Fri, 19 Feb 2016 17:13:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
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
Information forwarded
to
bug-guix <at> gnu.org
:
bug#22740
; Package
guix
.
(Sat, 20 Feb 2016 06:26:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 22740 <at> debbugs.gnu.org (full text, mbox):
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
>
>
>
>
Information forwarded
to
bug-guix <at> gnu.org
:
bug#22740
; Package
guix
.
(Sat, 20 Feb 2016 08:31:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 22740 <at> debbugs.gnu.org (full text, mbox):
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 think we update packages sufficiently often and the message is rather
> distracting.
--
Alex
Information forwarded
to
bug-guix <at> gnu.org
:
bug#22740
; Package
guix
.
(Sat, 20 Feb 2016 09:14:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 22740 <at> debbugs.gnu.org (full text, mbox):
Leo Famulari <leo <at> 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”.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#22740
; Package
guix
.
(Mon, 22 Feb 2016 21:17:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 22740 <at> debbugs.gnu.org (full text, mbox):
Alex Kost <alezost <at> 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. :-)
Information forwarded
to
bug-guix <at> gnu.org
:
bug#22740
; Package
guix
.
(Tue, 23 Feb 2016 08:55:01 GMT)
Full text and
rfc822 format available.
Message #20 received at 22740 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Ludovic Courtès (2016-02-23 00:16 +0300) wrote:
> Alex Kost <alezost <at> 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?
[0001-Do-not-check-package-freshness-during-upgrade.patch (text/x-patch, attachment)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#22740
; Package
guix
.
(Tue, 23 Feb 2016 09:19:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 22740 <at> debbugs.gnu.org (full text, mbox):
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.)
One of the procedures has the comment: "This has a noticeable impact when
doing "guix upgrade -u"." It looks like we are going way back into the
history of guix!
Andreas
Information forwarded
to
bug-guix <at> gnu.org
:
bug#22740
; Package
guix
.
(Tue, 23 Feb 2016 17:08:02 GMT)
Full text and
rfc822 format available.
Message #26 received at 22740 <at> debbugs.gnu.org (full text, mbox):
Alex Kost <alezost <at> 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.
> From 1d6d4d0864672b0676f09eb6c8285684e5b8785c Mon Sep 17 00:00:00 2001
> From: Alex Kost <alezost <at> 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 <at> 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.
OK, thanks!
Ludo’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#22740
; Package
guix
.
(Wed, 24 Feb 2016 16:00:02 GMT)
Full text and
rfc822 format available.
Message #29 received at 22740 <at> debbugs.gnu.org (full text, mbox):
Andreas Enge (2016-02-23 12:18 +0300) wrote:
> 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.)
Ludovic Courtès (2016-02-23 20:07 +0300) wrote:
> Alex Kost <alezost <at> 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.
The patch committed, thanks.
--
Alex
bug marked as fixed in version 0.9.1, send any further explanations to
22740 <at> debbugs.gnu.org and Andreas Enge <andreas <at> enge.fr>
Request was from
ludo <at> gnu.org (Ludovic Courtès)
to
control <at> debbugs.gnu.org
.
(Sun, 28 Feb 2016 20:03:01 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 28 Mar 2016 11:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 8 years and 2 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.