From mboxrd@z Thu Jan  1 00:00:00 1970
From: Julien Lepiller <julien@lepiller.eu>
Subject: Re: Best course for recently fixed packages?
Date: Wed, 12 Jun 2019 09:11:34 +0200
Message-ID: <72266BA8-732D-4369-B2B7-F9F07B3BEDF1@lepiller.eu>
References: <20190611231530.572b0e37@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:42588)
 by lists.gnu.org with esmtp (Exim 4.86_2)
 (envelope-from <julien@lepiller.eu>) id 1haxPt-0000eu-A6
 for help-guix@gnu.org; Wed, 12 Jun 2019 03:11:30 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <julien@lepiller.eu>) id 1haxPs-0000HQ-8l
 for help-guix@gnu.org; Wed, 12 Jun 2019 03:11:29 -0400
Received: from lepiller.eu ([2a00:5884:8208::1]:52506)
 by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
 (Exim 4.71) (envelope-from <julien@lepiller.eu>) id 1haxPs-0000Gv-0C
 for help-guix@gnu.org; Wed, 12 Jun 2019 03:11:28 -0400
In-Reply-To: <20190611231530.572b0e37@gmail.com>
List-Id: <help-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/help-guix>,
 <mailto:help-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/help-guix>
List-Post: <mailto:help-guix@gnu.org>
List-Help: <mailto:help-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/help-guix>,
 <mailto:help-guix-request@gnu.org?subject=subscribe>
Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org
Sender: "Help-Guix" <help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org>
To: help-guix@gnu.org, Jesse Gibbons <jgibbons2357@gmail.com>

Le 12 juin 2019 07:15:30 GMT+02:00, Jesse Gibbons <jgibbons2357@gmail=2Ecom=
> a =C3=A9crit :
>There is a package I am defining that I want to push to the repository=2E
>On github, its most recent release fails to build because it needs a
>dependency that no longer exists=2E This was fixed in the master branch=
=2E
>What should I specify as the commit?
>
>Since I don't know when master will next be updated (it was last
>updated 22 hours before when I decided to ask this and appears to be
>updated almost daily) and each commit is likely to change the package's
>sha256 hash, it does not make sense to specify that the commit is
>"master"=2E Should I instead specify master's current commit hash until
>the project's next release? Or should I specify the most recent release
>and specify a patch with the changes that fixed it? Or would it be best
>for me to place this package on hold until the next release?
>
>Thanks for the advice,
>-Jesse

It's usually better to use the latest release with a patch=2E If that's no=
t possible, then you can indeed specify a commit hash that corresponds to m=
aster until the next release=2E Thanks!