From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-admin/r10k/
Date: Tue, 1 Aug 2017 05:50:38 +0000 (UTC) [thread overview]
Message-ID: <1501562071.77d8fa9a9a8cc6ea182607d8bcb500a7403c1681.graaff@gentoo> (raw)
commit: 77d8fa9a9a8cc6ea182607d8bcb500a7403c1681
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Tue Aug 1 04:34:31 2017 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Tue Aug 1 04:34:31 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=77d8fa9a
app-admin/r10k: cleanup
Package-Manager: Portage-2.3.6, Repoman-2.3.2
app-admin/r10k/Manifest | 1 -
app-admin/r10k/r10k-1.1.3-r1.ebuild | 57 -------------------------------------
2 files changed, 58 deletions(-)
diff --git a/app-admin/r10k/Manifest b/app-admin/r10k/Manifest
index 015969f3755..bdc8d9d18cb 100644
--- a/app-admin/r10k/Manifest
+++ b/app-admin/r10k/Manifest
@@ -1,2 +1 @@
-DIST r10k-1.1.3.gem 30720 SHA256 4b4732046a7478f28668dd3db08ce2527bb45c6da83ec0c604f16d09fce9b91a SHA512 9ddb06c3535c4d5f4f0d8156ddf7671f248283874ef7fab4a2e9d00534e6d165e1b7a32937ecef8043a7fb8ff1143a9dd7bc388f0d7c810de86bc369a22fb502 WHIRLPOOL ea9b3a291cc581c719c2852a0d5f268be2389ed783368a0b20c6dc81b047d5725c60956de3282a353dfefd034a4be2eadaceba1a79ee9c0c16b3afaca3be2ac8
DIST r10k-1.5.1.gem 164864 SHA256 4dd4edfb1b69400324780784bf214a80bec3d0dbd46bc94113683904d503fdb0 SHA512 4440a893aaa6ec0337f9347b620f92afd93099465c148bfe90cd44c2c6fe29cc8411b8c225044a9547d24a8857b580dcf2ea190bf64fe9ba180d1c5c3832d1dd WHIRLPOOL b8a3a49857bc97e4b1529c4a8f33ace1e6c1cca270bd4be3669494568bbc9a0b85e15419103bbb63622aadd3ad1453e11ae63b85b9c86a67d013962f4d7b2761
diff --git a/app-admin/r10k/r10k-1.1.3-r1.ebuild b/app-admin/r10k/r10k-1.1.3-r1.ebuild
deleted file mode 100644
index 18a0bbfe90f..00000000000
--- a/app-admin/r10k/r10k-1.1.3-r1.ebuild
+++ /dev/null
@@ -1,57 +0,0 @@
-# Copyright 1999-2016 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=5
-
-USE_RUBY="ruby20 ruby21"
-
-RUBY_FAKEGEM_RECIPE_TEST="rspec"
-RUBY_FAKEGEM_TASK_DOC=""
-
-RUBY_FAKEGEM_GEMSPEC="${PN}.gemspec"
-
-inherit ruby-fakegem
-
-DESCRIPTION="Puppet environment and module deployment"
-HOMEPAGE="https://github.com/adrienthebo/r10k"
-
-LICENSE="Apache-2.0"
-SLOT="0"
-KEYWORDS="~amd64 ~x86"
-IUSE="+git"
-
-ruby_add_rdepend "
- >=dev-ruby/colored-1.2
- =dev-ruby/cri-2*
- >=dev-ruby/systemu-2.5.2
- >=dev-ruby/log4r-1.1.10
- dev-ruby/json"
-
-RDEPEND="${RDEPEND} git? ( >=dev-vcs/git-1.6.6 )"
-
-all_ruby_prepare() {
- sed -i -e 's/json_pure/json/' \
- -e '/cri/ s/2.4.0/2.4/' \
- -e '/systemu/ s/2.5.2/2.5/' \
- -e '/s.files/d' ${RUBY_FAKEGEM_GEMSPEC} || die
-}
-
-pkg_postinst() {
- ewarn
- ewarn "If you are upgrading from 1.1.0 and are using multiple sources, please read"
- ewarn "this. (If not, feel free to continue with your regularly scheduled day.)"
- ewarn
- ewarn "GH-48 (https://github.com/adrienthebo/r10k/issues/48) introduced the ability"
- ewarn "for environments to be prefixed with the source name so that multiple sources"
- ewarn "installed into the same directory would not overwrite each other. However"
- ewarn "prefixing was automatically enabled and would break existing setups where"
- ewarn "multiple sources were cloned into different directories."
- ewarn
- ewarn "Because this introduced a breaking change, SemVer dictates that the automatic"
- ewarn "prefixing has to be rolled back. Prefixing can be enabled but always defaults"
- ewarn "to off. If you are relying on this behavior you will need to update your r10k.yaml"
- ewarn "to enable prefixing on a per-source basis."
- ewarn
- ewarn "Please see the issue (https://github.com/adrienthebo/r10k/issues/48) for more"
- ewarn "information."
-}
next reply other threads:[~2017-08-01 5:50 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 5:50 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-18 6:24 [gentoo-commits] repo/gentoo:master commit in: app-admin/r10k/ Hans de Graaff
2024-05-03 5:49 Hans de Graaff
2024-05-03 5:49 Hans de Graaff
2024-04-05 9:42 Hans de Graaff
2023-12-09 9:11 Hans de Graaff
2023-12-09 9:11 Hans de Graaff
2023-09-09 7:10 Hans de Graaff
2023-08-19 8:03 Hans de Graaff
2023-08-19 8:03 Hans de Graaff
2023-06-25 13:53 Hans de Graaff
2022-12-17 8:37 Hans de Graaff
2022-07-20 6:01 Hans de Graaff
2022-06-18 8:40 Hans de Graaff
2020-11-21 7:36 Hans de Graaff
2020-11-21 7:33 Hans de Graaff
2020-11-20 8:04 Robin H. Johnson
2020-11-20 7:29 Robin H. Johnson
2020-09-15 6:57 Hans de Graaff
2020-07-20 6:55 Hans de Graaff
2020-04-01 16:37 Thomas Deutschmann
2020-03-08 6:38 Hans de Graaff
2020-02-14 7:18 Hans de Graaff
2020-01-23 19:13 Hans de Graaff
2019-10-09 5:47 Hans de Graaff
2019-08-23 15:35 Hans de Graaff
2019-07-13 6:14 Hans de Graaff
2019-07-13 6:14 Hans de Graaff
2019-05-30 18:05 Hans de Graaff
2019-05-01 5:31 Hans de Graaff
2019-02-10 7:25 Hans de Graaff
2019-02-09 10:44 Hans de Graaff
2018-05-06 6:37 Hans de Graaff
2018-01-22 20:34 Hans de Graaff
2017-12-21 4:53 Vikraman Choudhury
2017-09-08 19:35 Sven Wegener
2017-09-08 19:12 Sven Wegener
2017-08-05 18:49 Hans de Graaff
2017-08-01 5:50 Hans de Graaff
2017-08-01 5:50 Hans de Graaff
2016-04-10 0:18 Manuel Rüger
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=1501562071.77d8fa9a9a8cc6ea182607d8bcb500a7403c1681.graaff@gentoo \
--to=graaff@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