On 12/21/18 5:09 AM, Matt Darfeuille wrote: > Tom, the follow-on patch aims to address the following issue: > > $ ./release 5.2.2-Beta2 > [SNIP] > Creating tag 5.2.2-Beta2 in /home/matt/shorewall/trunk/.git... > Creating tag 5.2.2-Beta2 in /home/matt/shorewall/release/.git... > Pushing branch 5.2.2 from /home/matt/shorewall/trunk/.git to origin... > error: src refspec 5.2.2 does not match any. > error: failed to push some refs to > 'ssh://testbox01://srv/git/shorewall/trunk.git' > ERROR: Failed to push branch 5.2.2 from > /home/matt/shorewall/trunk/.git to origin.
Thanks, Matt. > > > Patch 2 will deprecate old build tools, your latest commit will stop > modifying the created patch files when building Shorewall. > Not modifying patch files sounds reasonable, 'cleanpatch.pl' is now > deprecated. > I'm incline to let 'cleanpatch.pl' in 'tools/build' for the moment, > that way, it will be easier in case of 'revert'? Yes -- I plan to modify cleanpatch.pl to generate a list of manpages whose only difference is in the generation date. That list can then be used to replace the newly-generated manpages with the old ones so point-release patches to manpages will apply cleanly. > > I'm also getting: > > trunk$ git tag -v 5.2.2-Beta1 > error: 5.2.2-Beta1: cannot verify a non-tag object of type commit. > Yep -- the tag isn't signed, as I did the release manually. -Tom -- Tom Eastep \ Q: What do you get when you cross a mobster with Shoreline, \ an international standard? Washington, USA \ A: Someone who makes you an offer you can't http://shorewall.org \ understand \_______________________________________________
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Shorewall-devel mailing list Shorewall-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-devel
