[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Update the Guix package/version
From: |
Roel Janssen |
Subject: |
Re: Update the Guix package/version |
Date: |
Wed, 25 Apr 2018 14:50:44 +0200 |
User-agent: |
mu4e 1.0; emacs 25.3.1 |
Ludovic Courtès <address@hidden> writes:
> Roel Janssen <address@hidden> skribis:
>
>> Ludovic Courtès <address@hidden> writes:
>>
>>> Hello,
>>>
>>> Roel Janssen <address@hidden> 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