Re: Some github projects aren't fetchable using commit hash

2017-09-04 Thread Kyle Evans
On Sep 4, 2017 00:29, "Shane Ambler" wrote: For a port the distinfo will detect a hash and size difference of the tarball and fail. Yeah, but in the more general sense from a GitHub consumer point of view, I may not notice immediately and if the build process hasn't

Re: Some github projects aren't fetchable using commit hash

2017-09-03 Thread Shane Ambler
On 02/09/2017 11:31, Kyle Evans wrote: On Sep 1, 2017 20:03, "Shane Ambler" wrote: 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

Re: Some github projects aren't fetchable using commit hash

2017-09-03 Thread Yuri
On 09/01/17 19:01, Kyle Evans wrote: To be honest, the failing seems like a little better behavior than suddenly swapping out the package I thought I was downloading with a newer version. It'd at least be a little more obvious and theoretically detectable if they respond properly. I suggested

Re: Some github projects aren't fetchable using commit hash

2017-09-01 Thread Kyle Evans
On Sep 1, 2017 20:03, "Shane Ambler" wrote: 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. To be honest, the failing

Re: Some github projects aren't fetchable using commit hash

2017-09-01 Thread Shane Ambler
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,

Re: Some github projects aren't fetchable using commit hash

2017-09-01 Thread Yuri
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

Re: Some github projects aren't fetchable using commit hash

2017-09-01 Thread Yuri
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. Using full hash is a workaround. Yuri ___ freebsd-ports@freebsd.org mailing list

Re: Some github projects aren't fetchable using commit hash

2017-09-01 Thread Tobias Kortkamp
On Fri, Sep 1, 2017, at 18:24, Yuri wrote: > FYI: > > > Some github URLs that ports framework uses to fetch by hash fail with no > apparent reason. Here are two examples: > > > https://codeload.github.com/grame-cncm/guidolib/tar.gz/2ec126d > >

Some github projects aren't fetchable using commit hash

2017-09-01 Thread Yuri
FYI: Some github URLs that ports framework uses to fetch by hash fail with no apparent reason. Here are two examples: https://codeload.github.com/grame-cncm/guidolib/tar.gz/2ec126d https://codeload.github.com/libretro/picodrive/tar.gz/40cd7bc I've contacted GitHub, they acknowledged the