From: "Sven Vermeulen" <swift@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/hardened-refpolicy:swift commit in: gentoo/
Date: Sat, 10 Oct 2015 12:11:08 +0000 (UTC) [thread overview]
Message-ID: <1440703998.107c53784485e58d5f04a26e9cb462eaf7740865.swift@gentoo> (raw)
commit: 107c53784485e58d5f04a26e9cb462eaf7740865
Author: Jason Zaman <jason <AT> perfinion <DOT> com>
AuthorDate: Thu Aug 27 19:33:18 2015 +0000
Commit: Sven Vermeulen <swift <AT> gentoo <DOT> org>
CommitDate: Thu Aug 27 19:33:18 2015 +0000
URL: https://gitweb.gentoo.org/proj/hardened-refpolicy.git/commit/?id=107c5378
release-prepare.sh: update for cvs->git migration and sign tags
gentoo/release-prepare.sh | 16 +++++++++++-----
1 file changed, 11 insertions(+), 5 deletions(-)
diff --git a/gentoo/release-prepare.sh b/gentoo/release-prepare.sh
index efd5447..d88b7ba 100644
--- a/gentoo/release-prepare.sh
+++ b/gentoo/release-prepare.sh
@@ -98,8 +98,7 @@ createEbuilds() {
tagRelease() {
printf "Creating tag ${NEWVERSION} in our repository... ";
cd ${HARDENEDREFPOL};
- git tag -a ${NEWVERSION} -m "Release set of ${NEWVERSION}" > /dev/null 2>&1 || die "Failed to create tag";
- git push origin ${NEWVERSION} > /dev/null 2>&1 || die "Failed to push tag to origin repository";
+ git tag -a ${NEWVERSION} -m "Release set of ${NEWVERSION}" --sign > /dev/null 2>&1 || die "Failed to create tag";
printf "done\n";
};
@@ -128,14 +127,21 @@ cat << EOF
The release has now been prepared.
Please go do the following to finish up:
-- In ${GENTOOX86}/sec-policy go "cvs add" all the new ebuilds
-- In ${GENTOOX86}/sec-policy run "repoman manifest" and "repoman full"
+
+In ${GENTOOX86}/sec-policy:
+git add .
+repoman --digest=y full
Then, before finally committing - do a run yourself, ensuring that the right
version is deployed of course:
- "emerge -1 \$(qlist -IC sec-policy)"
-Only then do a 'repoman commit -m 'Release of ${NEWVERSION}''.
+Only then do:
+repoman commit -m 'sec-policy: Release of SELinux policies ${NEWVERSION}'
+git push --sign
+
+In ${HARDENEDREFPOL} do:
+git push origin --tags
EOF
cleanTmp;
next reply other threads:[~2015-10-10 12:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 12:11 Sven Vermeulen [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-18 16:15 [gentoo-commits] proj/hardened-refpolicy:swift commit in: gentoo/ Sven Vermeulen
2018-01-18 16:15 Sven Vermeulen
2017-05-18 17:03 [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen
2017-05-18 17:02 ` [gentoo-commits] proj/hardened-refpolicy:swift " Sven Vermeulen
2017-05-18 16:54 Sven Vermeulen
2017-05-18 16:54 Sven Vermeulen
2016-10-24 16:02 [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen
2016-10-24 16:02 ` [gentoo-commits] proj/hardened-refpolicy:swift " Sven Vermeulen
2016-10-24 15:45 Sven Vermeulen
2016-07-03 11:34 Sven Vermeulen
2016-07-03 11:34 Sven Vermeulen
2016-07-03 11:33 [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen
2016-07-03 11:34 ` [gentoo-commits] proj/hardened-refpolicy:swift " Sven Vermeulen
2015-12-02 15:45 Sven Vermeulen
2015-10-10 12:11 Sven Vermeulen
2015-10-10 12:11 Sven Vermeulen
2015-10-10 12:11 Sven Vermeulen
2015-06-09 13:34 Sven Vermeulen
2015-06-09 13:24 Sven Vermeulen
2015-06-09 13:24 Sven Vermeulen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1440703998.107c53784485e58d5f04a26e9cb462eaf7740865.swift@gentoo \
--to=swift@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox