From mboxrd@z Thu Jan  1 00:00:00 1970
From: myglc2 <myglc2@gmail.com>
Subject: bug#25852: Users not updating their installations of Guix
Date: Fri, 12 May 2017 13:10:42 -0400
Message-ID: <86shkac86l.fsf@gmail.com>
References: <20170223211156.GA24382@jasmine> <877f429kju.fsf@gnu.org>
	<87wpc1k0e5.fsf@netris.org> <87efy9gyr5.fsf@gnu.org>
	<87k27wporb.fsf@netris.org> <877f1oua8u.fsf@gnu.org>
	<86vap8yf36.fsf@gmail.com> <878tm4sc0l.fsf@gnu.org>
	<87lgq2sj5z.fsf@elephly.net> <874lwqtr53.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51253)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1d9E5r-0002lI-3E
	for bug-guix@gnu.org; Fri, 12 May 2017 13:11:08 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1d9E5n-0002fh-16
	for bug-guix@gnu.org; Fri, 12 May 2017 13:11:07 -0400
Received: from debbugs.gnu.org ([208.118.235.43]:38505)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1d9E5m-0002fS-PT
	for bug-guix@gnu.org; Fri, 12 May 2017 13:11:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1d9E5m-0006Uq-CC
	for bug-guix@gnu.org; Fri, 12 May 2017 13:11:02 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.25852.D25852.149460905124956@debbugs.gnu.org>
In-Reply-To: <874lwqtr53.fsf@gnu.org> ("Ludovic
	\=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\=
	\=\?utf-8\?Q\?s\?\= message of "Fri, 12 May 2017 10:29:12 +0200")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: 25852-done@debbugs.gnu.org

On 05/12/2017 at 10:29 Ludovic Court=C3=A8s writes:

> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> Ludovic Court=C3=A8s <ludo@gnu.org> writes:
>>
>>> myglc2 <myglc2@gmail.com> skribis:
>>>
>>>> How about extending this ...
>>>>
>>>>> +      (warning (G_ "Your Guix installation is getting old.  Consider
>>>>> +running 'guix pull' followed by '~a' to get up-to-date
>>>>> +packages and security updates.\n")
>>>>
>>>> ... to inform the user how old the installation is?
>>>
>>> Good idea.  I did that and pushed as
>>> 7fd952e05203d975fcb6cdabd2f742ade1b31b66.
>>
>> Does this do the right thing when .config/guix/latest points at a git
>> checkout?
>
> No it doesn=E2=80=99t, but I would argue that it unsupported.  ;-)
>
>> The mtime of the =E2=80=9C.config/guix/latest=E2=80=9D link on one of my=
 machines is
>> from 2016, so Guix says it is too old, but it points to a git
>> checkout, which is recent.
>
> I would suggest:
>
>   export GUIX_DISTRO_AGE_WARNING=3D1000m
>
> as a workaround.  WDYT?

This alters guix's stock behavior if/when one switches back to using
'guix pull'. Maybe a better thing to do is the following each time you
update guix from a git checkout ...

ln -f -s -T ~/src/guix/ ~/.config/guix/latest
sudo ln -f -s -T ~/src/guix/ /root/.config/guix/latest