From owner-freebsd-ports@freebsd.org  Sat Sep  2 01:03:29 2017
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7D60DE1321F
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Sat,  2 Sep 2017 01:03:29 +0000 (UTC)
 (envelope-from FreeBSD@shaneware.biz)
Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3])
 by mx1.freebsd.org (Postfix) with ESMTP id 6A1F16B960
 for <freebsd-ports@freebsd.org>; Sat,  2 Sep 2017 01:03:29 +0000 (UTC)
 (envelope-from FreeBSD@shaneware.biz)
Received: by mailman.ysv.freebsd.org (Postfix)
 id 6966EE1321E; Sat,  2 Sep 2017 01:03:29 +0000 (UTC)
Delivered-To: ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68F7DE1321C
 for <ports@mailman.ysv.freebsd.org>; Sat,  2 Sep 2017 01:03:29 +0000 (UTC)
 (envelope-from FreeBSD@shaneware.biz)
Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net
 [150.101.137.145])
 by mx1.freebsd.org (Postfix) with ESMTP id CE7C16B95F;
 Sat,  2 Sep 2017 01:03:28 +0000 (UTC)
 (envelope-from FreeBSD@shaneware.biz)
Received: from 124-171-178-233.dyn.iinet.net.au (HELO leader.local)
 ([124.171.178.233])
 by ipmail06.adl6.internode.on.net with ESMTP; 02 Sep 2017 10:33:21 +0930
Subject: Re: Some github projects aren't fetchable using commit hash
To: Yuri <yuri@rawbw.com>, Tobias Kortkamp <tobik@freebsd.org>,
 ports@freebsd.org
References: <aa643aff-e842-b50e-5ae5-06e6c084ed5b@rawbw.com>
 <1504284830.794543.1092454472.7353C7D3@webmail.messagingengine.com>
 <4e2b7041-6ee3-6994-437d-39de395ffca3@rawbw.com>
From: Shane Ambler <FreeBSD@ShaneWare.Biz>
Message-ID: <c37d806c-f9d8-d0cb-4a55-5af9a0c5ea3b@ShaneWare.Biz>
Date: Sat, 2 Sep 2017 10:33:19 +0930
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <4e2b7041-6ee3-6994-437d-39de395ffca3@rawbw.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-AU
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Sep 2017 01:03:29 -0000

On 02/09/2017 02:29, Yuri wrote:
> On 09/01/17 09:53, Tobias Kortkamp wrote:
>> In libretro/picodrive there are two objects which have the same
>> abbreviated hash.  Probably best to use the full hash.
> 
> 
> Since another object with the same abbreviated hash can be committed 
> into the project any time, any port using such hash (which is a lot) can 
> break any time.

I thought the porters handbook specified using a 10 digit hash... at the
minimum you need a hash long enough that it is unique in that repo. If a
later commit breaks the uniqueness then a longer hash will be needed.

Respond to github support that an abbreviated hash with multiple matches
will fail. Under that condition, it may be desirable to respond with the
newest of the matches rather than a not found error.

-- 
FreeBSD - the place to B...Software Developing

Shane Ambler