From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Vong Subject: Re: Needs enhancement: "is my guix current?" Date: Tue, 12 Dec 2017 18:56:53 +0800 Message-ID: <87tvwwqkne.fsf@gmail.com> References: Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35621) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eOiFP-0002Xa-Nm for guix-devel@gnu.org; Tue, 12 Dec 2017 05:57:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eOiFM-0007mY-KD for guix-devel@gnu.org; Tue, 12 Dec 2017 05:57:15 -0500 Received: from mail-pf0-x230.google.com ([2607:f8b0:400e:c00::230]:44547) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eOiFM-0007lT-E9 for guix-devel@gnu.org; Tue, 12 Dec 2017 05:57:12 -0500 Received: by mail-pf0-x230.google.com with SMTP id m26so13911656pfj.11 for ; Tue, 12 Dec 2017 02:57:11 -0800 (PST) In-Reply-To: (Hartmut Goebel's message of "Mon, 11 Dec 2017 13:20:43 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Hartmut Goebel Cc: guix-devel --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello, I think if you never run 'guix refresh', then the guix installed should always be newer than the guix known to guix. The argument is as followed: When you install guix, the guix known to guix is at least 1 commit older than the installed guix. When you run 'guix pull', the installed guix is updated to its latest version in master and the guix known to guix is also always at least 1 commit older than that latest version. (The reason for the >=3D 1 commit lag is because it takes 1 commit to update the hash for the guix known to guix.) To sum up, if you never run 'guix refresh', then the guix installed should always be newer than the guix known to guix. If you have run 'guix refresh', then we know nothing since 'guix refresh' only updates the guix known to guix (whch mess up the invariant). Hope this make sense! Hartmut Goebel writes: > Hi, > > on my effort to solve the problems when updating to guix 0.14.0, I > stepped over this simple question: > > Is the installed guix the current one, resp. the current one my guix > knows of? Is there anyway to find out whether 20170924.19 or > 0.13.0-6.a9468b4 is newer? > > guix installed: > > =C2=A0=C2=A0=C2=A0 # guix --version > =C2=A0 =C2=A0 guix (GNU Guix) 20170924.19 > > guix knows to my guix: > > =C2=A0=C2=A0=C2=A0 # guix package -A guix > =C2=A0=C2=A0=C2=A0 guix=C2=A0=C2=A0=C2=A0 0.13.0-6.a9468b4 > > > From the usability point of view, this information needs to be ovbiously > available. Users should easily be able to to determine which version is > the newer one. > > Since I do not know how these different version numbers are generated, I > can't make any suggestions, though. Sorry. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEdZDkzSn0Cycogr9IxYq4eRf1Ea4FAlovtfYACgkQxYq4eRf1 Ea4sdA//T7iYZsQo/A31JwAPaiToPpDXtjxjX5BIW7p12NEzpRSdk4owKxmGTAuY xVvV/TjFeizzInjv735GaAssxdsTG/A/AYgfdc5gnQtDvKU1LH8jY92/HAGLSHfs 3TGK2k15rYm9GG/kIsm193TmkkLv+hst1IpxxaJF6OwqSxwYFfHwvtKsB12xFwAh GvM7/muPLdEYxMx7YhbPGy+x82V12Zp8H3QcxMfBawM0K4RkshZUWsvGNKxc2pzq JPQeppayz31d/hZf0o5ymp0g4fMiWFBeNoUK+Nm+rTImcxl6xDzBWKkccrSb97+m eFf31kLSbXoB9bqjCwMtxxuMbGsgzCRX/aDhsblB9beG5LDEiJrQRIx3T3A+dXdM V/wS8cdA73d5Q4jpXm8uLiuqRPNPLq53kE9gv61eosrPv4UsCNdu5uHoOx16L3kK AwX/zIjps/xoQAFIr3lfojRXTpEJUNINE7LuxifASjX3NYREIRic7/q/ARR68WWh B2BeUIMQURvxqHHOfG0jq8ritRPVW7CyJi3RMVvRNQbT65ewJDy4dW7iorP4KMqQ cCK9wfSuSlPy3jHMJ3/9JJkKucnWzZEmDSapWjrJwCR60uatTJlITDnwcE22eiaZ cV45YfQ50LUVazttvYR3W+F7MYrsUTzhYh2vVxVxGqvMDBgzRDo= =5hiK -----END PGP SIGNATURE----- --=-=-=--