Branch: refs/heads/master Home: https://github.com/fabbione/kronosnet Commit: b1794141d9cfedb01c6679bbf35189a7be9f4479 https://github.com/fabbione/kronosnet/commit/b1794141d9cfedb01c6679bbf35189… Author: Jan Pokorný <jpokorny(a)redhat.com> Date: 2017-07-28 (Fri, 28 Jul 2017) Changed paths: M build-aux/release.mk Log Message: ----------- [build] release.mk: simplify/generalize GPG signing rule ...especially in case we want to easily switch to signing also particular archives, which may be a reasonable expectation from some downstream/distro maintainers (as demonstrated with the libqb's example[1] where this changeset was picked from a followup PR[2], respectively its adaptation for fence-agents[3]). Since this commit, such a change is a matter of only swapping a prerequisities specification for "sign" target per the commented out suggestion. For that to work reliably even after such a change, for the complete dependency backtrack, though, a pre-existing issue with parallelized work on the prerequisites needs to be fixed first. The (currently hypothetical) problem is "tarballs" (phony) target missing in the linearized supply chain for the signed tarballs, as opposed to supply chain for the checksums file that can be worked on in an (unordered!) interleave with the work on these signed tarballs. Hence fix this (currently hypothetical) race condition by stretching "tarballs" target as progress barrier (using it as a prerequisite) uniformly for all the deliverables that are going to be signed (as opposed to the currently only "sha256" target). And when at it, make "deliverables" variable list them conveniently (along with reformatting definitions of other variables for uniformity). [1] https://github.com/ClusterLabs/libqb/issues/145#issuecomment-306640694 [2] https://github.com/ClusterLabs/libqb/pull/260 [3] https://github.com/ClusterLabs/fence-agents/pull/123 Signed-off-by: Jan Pokorný <jpokorny(a)redhat.com> Commit: 56f470871c4f54f278dd154d86a74abfeb3cf1fc https://github.com/fabbione/kronosnet/commit/56f470871c4f54f278dd154d86a74a… Author: Jan Pokorný <jpokorny(a)redhat.com> Date: 2017-07-28 (Fri, 28 Jul 2017) Changed paths: M .gitignore M build-aux/release.mk Log Message: ----------- [build] release.mk: fix no-release conflict (implied-required version) Previously, generating custom versioned tarballs without requiring a "release" (which comprises also tagging hence in turn making the implied version match the required one as desired) would not allow to test the release routines thoroughly incl. GPG signing. Unfortunately, allowing for a temporary tag is prone to accidentally slipping it to the distributed tree, so that should rather be avoided Now it can. Another step to blur the boundaries between whether "release" is specified or not is to make checksums file generated unconditionally. Also both pre-existing and the newly created (per the above scenario) "overhead" files arising from make/release.mk are git-ignored properly. Signed-off-by: Jan Pokorný <jpokorny(a)redhat.com> Commit: 9d62b36f092d0a1d312e65e1f3a8d585390022e6 https://github.com/fabbione/kronosnet/commit/9d62b36f092d0a1d312e65e1f3a8d5… Author: Jan Pokorný <jpokorny(a)redhat.com> Date: 2017-07-28 (Fri, 28 Jul 2017) Changed paths: M build-aux/release.mk Log Message: ----------- [build] release.mk: move soft guard for no GPG key up the supply chain It also means the missing key specification is now a hard error when ASCII armored files are to be created (directly or by other rules). Leveraging the previous commit, it is now unnecessary to guard against release mode not being requested, so this guard is dropped completely in the transition, allowing for the full-fledged (incl. GPG signing) release delivery testing without mangling with in-tree tags. To allow "sign" target to (possibly eventually) become the implicit goal even if "gpgsignkey" variable is explicitly unspecified, make it depend on $(deliverables). Signed-off-by: Jan Pokorný <jpokorny(a)redhat.com> Commit: 4b683cd9d181aa4d4dcb3fb07eacc547bdf416d0 https://github.com/fabbione/kronosnet/commit/4b683cd9d181aa4d4dcb3fb07eacc5… Author: Jan Pokorný <jpokorny(a)redhat.com> Date: 2017-07-28 (Fri, 28 Jul 2017) Changed paths: M build-aux/release.mk Log Message: ----------- [build] release.mk: simplify the default goal, declare .PHONY targets The default goal line now serves mainly the documentation purpose, otherwise it could be squashed down to "sign" target. Signed-off-by: Jan Pokorný <jpokorny(a)redhat.com> Commit: c9f1b40a7200f0a713b07b556d58964a9bc5de27 https://github.com/fabbione/kronosnet/commit/c9f1b40a7200f0a713b07b556d5896… Author: Jan Pokorný <jpokorny(a)redhat.com> Date: 2017-07-28 (Fri, 28 Jul 2017) Changed paths: M build-aux/release.mk Log Message: ----------- [build] release.mk: reflect current release publishing practice Core author(s) had previous affiliation with project hosting on fedorahosted.org, but since the sunset of that hosting[1], it's no longer an option. Unfortunately, publish-by-scp convenience of fedorahosted.org won't fly with GitHub that insists on the (primarily REST) API to get things automated, so update "publish" recipe to that effect, providing some hints on possible adaption of the process. Also, turn "git push --tags" to a bit safer "git push --follow-tags" for good measure. [1] https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.… Signed-off-by: Jan Pokorný <jpokorny(a)redhat.com> Commit: 28260ba89d58a5fde1b9ff7f0b37f97b7aae52c6 https://github.com/fabbione/kronosnet/commit/28260ba89d58a5fde1b9ff7f0b37f9… Author: Fabio M. Di Nitto <fdinitto(a)redhat.com> Date: 2017-07-28 (Fri, 28 Jul 2017) Changed paths: M .gitignore M build-aux/release.mk Log Message: ----------- Merge pull request #46 from jnpkrn/build-release.mk [build] release.mk: adapt recent changes from libqb (fence-agents) Compare: https://github.com/fabbione/kronosnet/compare/b0c82f3e7640...28260ba89d58