public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sven Vermeulen" <swift@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/hardened-refpolicy:next commit in: gentoo/
Date: Fri, 28 Nov 2014 10:04:03 +0000 (UTC)	[thread overview]
Message-ID: <1416824109.88326fb9c8a25da67709418ca5f328261defce23.swift@gentoo> (raw)

commit:     88326fb9c8a25da67709418ca5f328261defce23
Author:     Jason Zaman <jason <AT> perfinion <DOT> com>
AuthorDate: Mon Nov 24 10:12:14 2014 +0000
Commit:     Sven Vermeulen <swift <AT> gentoo <DOT> org>
CommitDate: Mon Nov 24 10:15:09 2014 +0000
URL:        http://sources.gentoo.org/gitweb/?p=proj/hardened-refpolicy.git;a=commit;h=88326fb9

make the gentoo release script a little more user-agnostic

---
 gentoo/release-prepare.sh | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/gentoo/release-prepare.sh b/gentoo/release-prepare.sh
index 073ff58..afeed8f 100644
--- a/gentoo/release-prepare.sh
+++ b/gentoo/release-prepare.sh
@@ -7,7 +7,8 @@
 
 TRANSLATE="s:\(${HARDENEDREFPOL}\|${REFPOLRELEASE}\):refpolicy/:g";
 NEWVERSION="${1}";
-REMOTELOCATION="swift@dev.gentoo.org:public_html/patches/selinux-base-policy";
+# If remote requires a different username, it should be set in ~/.ssh/config
+REMOTELOCATION="dev.gentoo.org:/home/swift/public_html/patches/selinux-base-policy";
 
 usage() {
   echo "Usage: $0 <newversion>";
@@ -20,12 +21,12 @@ usage() {
   echo "The following environment variables must be declared correctly for the script";
   echo "to function properly:";
   echo "  - GENTOOX86 should point to the gentoo-x86 checkout";
-  echo "    E.g. export GENTOOX86=\"/home/user/dev/gentoo-x86\"";
+  echo "    E.g. export GENTOOX86=\"/home/user/dev/gentoo-x86/\"";
   echo "  - HARDENEDREFPOL should point to the hardened-refpolicy.git checkout";
-  echo "    E.g. export HARDENEDREFPOL=\"/home/user/dev/hardened-refpolicy\"";
+  echo "    E.g. export HARDENEDREFPOL=\"/home/user/dev/hardened-refpolicy/\"";
   echo "  - REFPOLRELEASE should point to the current latest /release/ of the reference"
   echo "    policy (so NOT to a checkout), extracted somewhere on the file system."
-  echo "    E.g. export REFPOLRELEASE=\"/home/user/local/refpolicy-20130424\"";
+  echo "    E.g. export REFPOLRELEASE=\"/home/user/local/refpolicy-20130424/\"";
 }
 
 assertDirEnvVar() {
@@ -98,7 +99,7 @@ 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 "Faield to push tag to origin repository";
+  git push origin ${NEWVERSION} > /dev/null 2>&1 || die "Failed to push tag to origin repository";
   printf "done\n";
 };
 


             reply	other threads:[~2014-11-28 10:04 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-28 10:04 Sven Vermeulen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-02-24 17:11 [gentoo-commits] proj/hardened-refpolicy:next commit in: gentoo/ Jason Zaman
2015-02-24 17:11 Jason Zaman
2015-03-25 16:01 Jason Zaman
2015-06-09 13:24 [gentoo-commits] proj/hardened-refpolicy:swift " Sven Vermeulen
2015-06-07  9:09 ` [gentoo-commits] proj/hardened-refpolicy:next " Sven Vermeulen
2015-08-02 19:26 Jason Zaman
2015-08-27 19:11 Jason Zaman
2015-08-27 19:34 Jason Zaman
2015-09-06 11:25 Jason Zaman
2015-10-11 10:48 Jason Zaman
2015-10-13 14:50 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman
2015-10-14 18:36 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman
2015-10-26  5:36 Jason Zaman
2016-08-13 18:32 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman
2016-08-13 18:35 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman
2016-08-17 16:59 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman
2016-08-17 16:59 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman
2016-10-03  6:20 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman
2016-10-03  6:26 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman
2016-10-24 16:02 [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen
2016-10-24 16:03 ` [gentoo-commits] proj/hardened-refpolicy:next " Sven Vermeulen
2016-12-06 14:25 Jason Zaman
2016-12-08  5:03 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman
2016-12-08  5:03 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman
2017-01-01 16:36 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman
2017-01-01 16:37 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman
2017-02-17  8:44 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman
2017-02-17  8:50 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman
2017-02-25 14:59 Jason Zaman
2017-02-25 16:58 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman
2017-02-25 16:58 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman
2017-02-27 10:50 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman
2017-02-27 11:40 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman
2017-03-30 17:09 Jason Zaman
2017-04-30  9:40 Jason Zaman
2017-05-07 16:09 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman
2017-05-07 17:47 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman
2017-05-25 16:43 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman
2017-05-25 17:08 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman
2017-07-22 12:41 Jason Zaman
2017-09-10 14:03 Jason Zaman

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=1416824109.88326fb9c8a25da67709418ca5f328261defce23.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