public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/grs:desktop-amd64-musl-hardened commit in: scripts/
Date: Wed,  1 Nov 2017 00:51:19 +0000 (UTC)	[thread overview]
Message-ID: <1509497472.75af27ac55753389da3edcf392cf0c924bd45bc2.blueness@gentoo> (raw)

commit:     75af27ac55753389da3edcf392cf0c924bd45bc2
Author:     Anthony G. Basile <blueness <AT> gentoo <DOT> org>
AuthorDate: Wed Nov  1 00:51:12 2017 +0000
Commit:     Anthony G. Basile <blueness <AT> gentoo <DOT> org>
CommitDate: Wed Nov  1 00:51:12 2017 +0000
URL:        https://gitweb.gentoo.org/proj/grs.git/commit/?id=75af27ac

scripts/cycle.1.sh: avoid a problem with emerging layman

 scripts/cycle.1.sh | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/scripts/cycle.1.sh b/scripts/cycle.1.sh
index 837a338..2a2a5d2 100644
--- a/scripts/cycle.1.sh
+++ b/scripts/cycle.1.sh
@@ -2,6 +2,11 @@
 
 source /etc/profile
 env-update
+
+# This is a workaround for now to avoid a problem
+# with dev-python/cryptography which depends on
+# >=dev-libs/openssl-1.0.2:0=[-bindist(-)]
+USE=-bindist emerge -1 --nodeps openssl openssh
 emerge -b1q layman
 layman -L
 


             reply	other threads:[~2017-11-01  0:51 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01  0:51 Anthony G. Basile [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-06 23:12 [gentoo-commits] proj/grs:desktop-amd64-musl-hardened commit in: scripts/ Anthony G. Basile
2022-07-20 18:24 Anthony G. Basile
2022-07-19 20:02 Anthony G. Basile
2022-07-18 23:58 Anthony G. Basile
2022-07-18 23:52 Anthony G. Basile
2022-07-18 23:28 Anthony G. Basile
2019-06-07 14:14 Anthony G. Basile
2019-06-06 15:45 Anthony G. Basile
2019-04-24  1:36 Anthony G. Basile
2019-04-24  1:36 Anthony G. Basile
2019-04-23 18:38 Anthony G. Basile
2019-04-19 11:34 Anthony G. Basile
2019-03-09 23:30 Anthony G. Basile
2019-03-09 16:54 Anthony G. Basile
2018-01-19  0:04 Anthony G. Basile
2017-12-06 19:33 Anthony G. Basile
2017-11-18 13:05 Anthony G. Basile
2017-11-13  5:03 Anthony G. Basile
2017-11-02 13:41 Anthony G. Basile
2017-10-30 23:00 Anthony G. Basile
2017-10-30 23:00 Anthony G. Basile
2017-10-30 23:00 Anthony G. Basile
2016-10-25 14:20 Anthony G. Basile
2016-10-21  6:30 Anthony G. Basile
2016-10-15 23:25 Anthony G. Basile
2016-10-15 13:42 Anthony G. Basile
2016-06-27  9:07 Anthony G. Basile
2016-05-28 10:40 Anthony G. Basile
2016-05-26 22:49 Anthony G. Basile
2016-05-24  9:11 Anthony G. Basile
2016-02-26 21:45 Anthony G. Basile
2016-02-21 20:05 Anthony G. Basile
2016-02-15 20:10 Anthony G. Basile
2016-01-09 14:59 Anthony G. Basile
2015-11-25 10:46 Anthony G. Basile
2015-11-23 21:33 Anthony G. Basile
2015-10-15  2:03 Anthony G. Basile
2015-10-08 18:07 Anthony G. Basile
2015-10-08 17:45 Anthony G. Basile
2015-09-27 13:19 Anthony G. Basile
2015-09-16  5:30 Anthony G. Basile
2015-08-10 12:20 Anthony G. Basile
2015-07-23  0:42 Anthony G. Basile
2015-07-23  0:18 Anthony G. Basile
2015-07-21 11:12 Anthony G. Basile
2015-07-21  0:15 Anthony G. Basile
2015-07-21  0:12 Anthony G. Basile
2015-07-15  0:28 Anthony G. Basile

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=1509497472.75af27ac55753389da3edcf392cf0c924bd45bc2.blueness@gentoo \
    --to=blueness@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