On 9/27/2014 10:56 PM, PGNd wrote:
> Notice that for a 'setversion'-specified version
>
> SW_BUILD_VER=4.6.4.X
> cd /usr/local/src/shorewall-build/release
> setversion ${SW_BUILD_VER}
> git commit -a -m "test"
>
> using otherwise UNmodified *spec files
>
> cd /usr/local/src/shorewall-build/BUILD/${SW_BUILD_VER}
> touch shorewall-pkg.config
> /usr/local/src/shorewall-build/tools/build/build46 -tr -cil6Ls
> ${SW_BUILD_VER}
>
> The tarballs are named with the specified SW_BUILD_VER, "4.6.4.X"
>
> ls -1 *tgz
> shorewall-4.6.4.X.tgz
> shorewall6-4.6.4.X.tgz
> shorewall6-lite-4.6.4.X.tgz
> shorewall-core-4.6.4.X.tgz
> shorewall-init-4.6.4.X.tgz
> shorewall-lite-4.6.4.X.tgz
>
> but the rpms are named with "4.6.4-X", not "4.6.4.X"
>
> cd /usr/src/packages/RPMS/noarch/
> ls -1 shorewall*rpm
> shorewall-4.6.4-X.noarch.rpm
> shorewall6-4.6.4-X.noarch.rpm
> shorewall6-lite-4.6.4-X.noarch.rpm
> shorewall-core-4.6.4-X.noarch.rpm
> shorewall-init-4.6.4-X.noarch.rpm
> shorewall-lite-4.6.4-X.noarch.rpm
>
> Trivial to override locally, but is it intended? Should those not be
> consistently numbered by the packaging script?That's intended. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ 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
