Date: Mon, 04 Feb 2013 11:41:45 -0500 From: Greg Larkin <glarkin@FreeBSD.org> To: Paul Schmehl <pschmehl_lists@tx.rr.com> Cc: FreeBSD Ports List <freebsd-ports@freebsd.org> Subject: Re: I need help with git Message-ID: <510FE4C9.2070003@FreeBSD.org> In-Reply-To: <39A84EC03A29CF90A1609C44@utd71538.campus.ad.utdallas.edu> References: <39A84EC03A29CF90A1609C44@utd71538.campus.ad.utdallas.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2/4/13 11:21 AM, Paul Schmehl wrote:
> I'm the maintainer for security/barnyard2. The software recently
> changed so that all distros are pulled from github. The developers
> made new commits, and now the port is broken, and I cannot figure
> out how to fix it.
>
> Here's the relevant code from the Makefile:
>
> PORTNAME= barnyard2 PORTVERSION= 1.11 CATEGORIES=
> security
>
> MAINTAINER= pauls@utdallas.edu COMMENT= Interpreter for
> Snort unified2 binary output files
>
> LICENSE= GPLv2
>
> USE_GITHUB= yes GH_ACCOUNT= firnsy GH_PROJECT=
> ${PORTNAME} GH_TAGNAME= master GH_COMMIT= 4dfdc80
>
> The master tagname apparently gets moved to the new commit every
> time the developers commit changes. This is NOT what I want. I
> want the port to stay at the release version until a new version is
> released.
>
> I've tried everything I can think of to get this port to pull the
> commit I want. It does not work. I've tried changing the tagname
> to v2-1.11, v2-${PORTVERSION}, stable, dev-next, etc., etc.
> Nothing works.
>
> Here's the git site:
> <https://github.com/firnsy/barnyard2/commits/master>;
>
> If I pull master, I get commit f57e464. That's not what I want.
> Why doesn't this thing pull the commit I'm telling it to pull?
>
> I'm so frustrated by this I'm about to drop this port. I do NOT
> want to have to update the port every time the developers commit
> more code. That is NOT how software should work.
>
> Is there anyone who can tell me how to fix this problem so the port
> will remain at the release version until the next version is
> released no matter how many commits the developers make?
>
Hi Paul,
I just changed this line:
GH_TAGNAME= master
to this:
GH_TAGNAME= v2-1.11
and it worked fine.
FWIW,
Greg
- --
Greg Larkin
http://www.FreeBSD.org/ - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/cpucycle/ - Follow you, follow me
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlEP5MkACgkQ0sRouByUApDsCwCePQYMCZ6/Avm0lUSbGazexoz5
kBkAnjLstH0h/pZ4y52BMZVgh9uFYFcv
=5E4Z
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?510FE4C9.2070003>