[ports]: GH_TAGNAME: how to figure out this tagname on downloadable archives?

O. Hartmann o.hartmann at walstatt.org
Mon Oct 16 05:07:37 UTC 2017

On Mon, 16 Oct 2017 04:19:24 +0000
blubee blubeeme <gurenchan at gmail.com> wrote:

> I just ran into this issue yesterday myself.
> To find the tagname I went to the project in githib, looked at their
> committed files and found the one with the latest date.
> Click on that file, then you'll see three buttons in the upper right hand
> side;
> raw, blame, history.
> Click on history and you'll see the tagnames on the right have column.
> Copy that to your GH_TAGNAME in the makefile and you should be fine.
> There are ways to get the tagname from git but that's if you've cloned the
> repo locally which I didn't want to bother doing.
> Best

All right, thanks a lot for the hint,

but it doesn't solve the problem for me. I think I was in a kind of panic mode
yesterday when I realised that some ports I'm named as the maintainer has been

Port devel/opencl is "tagged" as PORTVERSION=2.1 and HEADER_TAG=2d06e09.

If looking at github
you'll realise, that with 16th of May 2017, OpenCL 2.2 and the precedesors has
been altered to have the header files in a new subfolder, CL, beneath its
main folder. this is the very same for the older header files of OpenCL.

If proceeding as described, I find that the latest commit on opencl.h in
OpenCL22/CL/ has the tag number 2d4cc61 - as Yuri mentioned before, a 7
digit/alphanum number. I copied that into the Makefile (following the simple
logic stupidly now knowing how the tarball is created at all ...). Altering the
port's version to 2.2 - also simply following a simple logic, results then in
the following (PORTVERSION=2.2; HEADER_TAG=2d4cc61):

# make distclean makesum
=> KhronosGroup-OpenCL-Headers-2.2-2d4cc61_GH0.tar.gz doesn't seem to exist
in /usr/ports/distfiles/.
=> Attempting to fetch
Certificate verification failed for /C=US/O=DigiCert
Inc/OU=www.digicert.com/CN=DigiCert SHA2 High Assurance Server CA
34374640024:error:14090086:SSL routines:ssl3_get_server_certificate:certificate
verify failed:/usr/src/crypto/openssl/ssl/s3_clnt.c:1269:
Authentication error
=> Attempting to fetch
Not Found
=> Couldn't fetch it - please try to retrieve this
=> port manually into /usr/ports/distfiles/ and try again.
*** Error code 1

make: stopped in /usr/ports/devel/opencl

This attempt is from  12-CURRENT system at the bureau, another box, at the
lab's, proceeds successfully and I can retrieve the *_GH0.tar.gz tarball. I
found this out this morning. What is that creepy authentication error?

My confusion has its roots in the fact that with the old scheme the retrieved
files expand in ./work/ in a different way prior to 16th May 2017 - I guess.

Now I have to check why the same alerations to the Makefile of port
devel/opencl work from one 12-CURRENT box (attached to a network from another
provider, FreeBSD 12.0-CURRENT #356 r324638: Sun Oct 15 21:46:03 CEST 2017
amd64) and on the other one not (12-CURRENT also, but last compiled on Friday,
FreeBSD 12.0-CURRENT #59 r324593: Fri Oct 13 14:25:15 CEST 2017 amd64) :-(

Thank you all very much, kind regards


> On Mon, Oct 16, 2017, 04:58 Yuri <yuri at rawbw.com> wrote:
> > On 10/15/17 12:47, O. Hartmann wrote:  
> > > all right, that is what I picked up from the porter's handbook, but I  
> > must have  
> > > overlooked the note (if there is anything like that) regarding the  
> > sufficient first 7  
> > > digits.  
> >
> > If you look at other ports, most use 7 digits.
> >  
> > > I tried this earlier (yes, and I do also a make makesum ;-))), but I get  
> > a complete  
> > > different "structure" right now - no tarball which contains exactly  
> > OpenCL 2.1 or OpenCL  
> > > 2.2 (the one I'd like to download), but a complete hierarchie of the CL  
> > sources, starting  
> > > from OpenCL 1.0 to OpenCL 2.2. Either, there has been a change in the  
> > way OpenCL headers  
> > > are provided, or there is a magic trick to download, depending on the  
> > GH_TAGNAME, a  
> > > tarball ending in "*_GH0.tar.xz"  
> >
> >
> > The version downloaded using GH_TAGNAME should have the same structure
> > as releases, unless the project structure itself has been radically
> > changed between releases. The top folder name is going to be different
> > for GH_TAGNAME. A release is just an alpa-numeric tag in a sequence of
> > commits, nothing more.
> >
> >
> > Yuri
> >
> > _______________________________________________
> > freebsd-ports at freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
> >  

More information about the freebsd-ports mailing list