public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Matt Thode" <prometheanfire@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/releng:master commit in: tools-musl/
Date: Mon,  2 Jan 2017 04:21:14 +0000 (UTC)	[thread overview]
Message-ID: <1483330718.dd3a001c4d35ff97e0056bd79a6ec0763f2c6f05.prometheanfire@gentoo> (raw)

commit:     dd3a001c4d35ff97e0056bd79a6ec0763f2c6f05
Author:     Matthew Thode <mthode <AT> mthode <DOT> org>
AuthorDate: Mon Jan  2 04:18:38 2017 +0000
Commit:     Matt Thode <prometheanfire <AT> gentoo <DOT> org>
CommitDate: Mon Jan  2 04:18:38 2017 +0000
URL:        https://gitweb.gentoo.org/proj/releng.git/commit/?id=dd3a001c

remove stage4/unmerge

seems that it causes issues on rebuilds, if the kernel is cached it will
not emerge some packages (like kernels)

WARNING: A requested package will not be merged because it is listed in
package.provided:

  hardened-sources pulled in by 'args'

 tools-musl/stage4-hardened-amd64.spec | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/tools-musl/stage4-hardened-amd64.spec b/tools-musl/stage4-hardened-amd64.spec
index 92d85b9..6cab281 100644
--- a/tools-musl/stage4-hardened-amd64.spec
+++ b/tools-musl/stage4-hardened-amd64.spec
@@ -54,10 +54,6 @@ boot/kernel/gentoo/config: @REPO_DIR@/../releases/weekly/kconfig/amd64/admincd-4
 boot/kernel/gentoo/extraversion: openstack
 boot/kernel/gentoo/gk_kernargs: --all-ramdisk-modules --makeopts=-j4
 
-# all of the cleanup...
-stage4/unmerge:
-	sys-kernel/hardened-sources
-
 stage4/empty:
 	/root/.ccache
 	/tmp


             reply	other threads:[~2017-01-02  4:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-02  4:21 Matt Thode [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-01-14 19:11 [gentoo-commits] proj/releng:master commit in: tools-musl/ Anthony G. Basile
2019-05-24  3:50 Matthew Thode
2019-04-13 10:54 Anthony G. Basile
2019-04-11  1:37 Anthony G. Basile
2018-03-02 16:25 Anthony G. Basile
2017-01-05  5:41 Matt Thode
2017-01-03  3:01 Matt Thode
2017-01-02 23:59 Matt Thode
2017-01-02  4:30 Matt Thode
2017-01-02  4:08 Matt Thode
2016-06-04 16:07 Anthony G. Basile
2015-12-07  0:54 Anthony G. Basile
2015-06-14 21:32 Anthony G. Basile
2015-06-14 21:01 Anthony G. Basile
2015-01-20 23:38 Anthony G. Basile
2014-08-18 21:59 Robin H. Johnson
2014-08-18 21:59 Robin H. Johnson
2014-08-13 14:28 Anthony G. Basile
2014-08-11 22:43 Anthony G. Basile
2014-06-28 10:43 Anthony G. Basile
2014-06-18 11:14 Anthony G. Basile
2014-02-18 21:04 Anthony G. Basile
2014-02-06 13:06 Anthony G. Basile
2014-02-05 20:13 Anthony G. Basile
2014-02-05 20:11 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=1483330718.dd3a001c4d35ff97e0056bd79a6ec0763f2c6f05.prometheanfire@gentoo \
    --to=prometheanfire@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