On Mon, 04 Feb 2013 10:21:35 -0600
Paul Schmehl <pschmehl_li...@tx.rr.com> 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= pa...@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,
Could you revisit what I write to you about this a couple of months ago?
I just tried changing GH_TAGNAME to v2-1.11 in Makefile and it just
worked fine (by the way, that's what I suggested back then, you should
never depend on "master", since it is a moving target)
USE_GITHUB= yes
GH_ACCOUNT= firnsy
GH_PROJECT= ${PORTNAME}
GH_TAGNAME= v2-1.11
GH_COMMIT= 4dfdc80
Are you sure there's nothing left in your build environment that stops
you from building the port successfully?
Cheers,
--
Michael Gmelin
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
