On Sat, Sep 27, 2014, at 01:02 PM, Tom Eastep wrote: > you are building against 'master'.
yes > The build system can only build against the HEAD of a branch. It isn't > intended to be able to build against arbitrary tags. misunderstood that. Noted. git branch -a * master remotes/origin/4.4.22 ... remotes/origin/4.6.3 remotes/origin/HEAD -> origin/master remotes/origin/master > ls *.rpm > > '.rpms' is the plural of '.rpm'. cd ./release git checkout master Already on 'master' Your branch is up-to-date with 'origin/master'. git clean -xfd git reset --hard HEAD HEAD is now at caba6de Update release documents: find . -type f -name *rpm (empty) ls *.rpm ls: cannot access *.rpm: No such file or directory What obvious-ness am I missing here? I simply want to build master/HEAD, and have the build system find/name the rpms correctly. > > Is that only available after a specific build step, so that I have to exec > > a partial build, grab that version name/#, then exec build46 with that > > retrieved name/#? > > No. But you can only build rpms for the version specified in the .rpm > files in the ./release repository. If you want to build different rpms, > you must modify *.rpm to build that version. You can use the > 'setversion' program to do that. Note that 'setversion' creates a log > entry in each .rpm file. Noted. Thanks. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
