From mboxrd@z Thu Jan  1 00:00:00 1970
From: Roel Janssen <roel@gnu.org>
Subject: Re: Update the Guix package/version
Date: Wed, 25 Apr 2018 14:50:44 +0200
Message-ID: <8736zjwiv2.fsf@gnu.org>
References: <87muxu8fyf.fsf@gnu.org> <878t9dzzsr.fsf@gnu.org>
	<87604him12.fsf@gnu.org> <87wowvtrio.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:58567)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <roel@gnu.org>) id 1fBJsw-0005Nj-2S
	for guix-devel@gnu.org; Wed, 25 Apr 2018 08:51:02 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <roel@gnu.org>) id 1fBJsv-0004Fe-64
	for guix-devel@gnu.org; Wed, 25 Apr 2018 08:50:58 -0400
In-reply-to: <87wowvtrio.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Ludovic =?utf-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> Roel Janssen <roel@gnu.org> skribis:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>>> Hello,
>>>
>>> Roel Janssen <roel@gnu.org> skribis:
>>>
>>>> What's the decision process for updating the ‘guix’ package revision,
>>>> like in commit b1fb247b?
>>>
>>> There’s no real process, just do it when there’s a good reason to do it.
>>>
>>>> The reason I ask this is because I'd like to bump the revision so that
>>>> the changes from 5cefb13d to ‘guix-daemon’ are available when I install
>>>> ‘guix’ in a profile.
>>>
>>> Makes sense!
>>>
>>> Note that you can run “make update-guix-package” to do the work.  Be
>>> sure to do that from a commit that is available on Savannah.  And of
>>> course, make sure the package builds locally.  :-)
>>
>> Cool! I didn't know about this build step.  May I commit the change, so
>> that I won't end up with an ambiguous revision number later on?
>
> Sure if you have an update based on an upstream commit that builds,
> you’re welcome to push it.
>
> Perhaps you can also run “guix build -S guix --check” to be 100% sure
> that the commit and hash are correct.

I did:
$ git reset --hard
$ git pull
$ make update-guix-package
$ guix build -S guix --check
$ guix build guix

And after verifying that all went fine, I then pushed the change in
5b862761f.

Thanks!

Kind regards,
Roel Janssen