I need help with git

[Micheas Herman]

On Monday, February 4, 2013, 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 at utdallas.edu
> COMMENT=        Interpreter for Snort unified2 binary output files
>
> LICENSE=        GPLv2
>
> USE_GITHUB=     yes
> GH_ACCOUNT=     firnsy
> GH_PROJECT=     ${PORTNAME}
> GH_TAGNAME=     master


You need to change th GH_TAGNAME to the release you want if you go to the
repository on github and you can find the tags that the maintainers have
added to the project.

If you want a snapshot in time that is not tagged you could either request
the authors tag it, or fork it on github tag it yourself and put your own
account as the GH_ACCOUNT.



> GH_COMMIT=      4dfdc80



Probably not needed if you specify a tag other than master.

>
> 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<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?
>
> --
> Paul Schmehl, Senior Infosec Analyst
> As if it wasn't already obvious, my opinions
> are my own and not those of my employer.
> *********************************************
> "It is as useless to argue with those who have
> renounced the use of reason as to administer
> medication to the dead." Thomas Jefferson
> "There are some ideas so wrong that only a very
> intelligent person could believe in them." George Orwell
>
> ______________________________**_________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/**mailman/listinfo/freebsd-ports<http://lists.freebsd.org/mailman/listinfo/freebsd-ports>
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
>