public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Zac Medico" <zmedico@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: pym/portage/tests/emerge/, bin/
Date: Wed,  7 Sep 2011 17:50:01 +0000 (UTC)	[thread overview]
Message-ID: <5e1f136ba4c4f31dd5540594f48dc42f62ee09d9.zmedico@gentoo> (raw)

commit:     5e1f136ba4c4f31dd5540594f48dc42f62ee09d9
Author:     Zac Medico <zmedico <AT> gentoo <DOT> org>
AuthorDate: Wed Sep  7 17:49:46 2011 +0000
Commit:     Zac Medico <zmedico <AT> gentoo <DOT> org>
CommitDate: Wed Sep  7 17:49:46 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=5e1f136b

egencache: remove metadata-transfer warning

It should be enough that the automatic use of metadata-transfer is
documented in the man page, and allows us to avoid showing a useless
warning in common usage scenarios.

---
 bin/egencache                           |    3 ---
 pym/portage/tests/emerge/test_simple.py |    1 -
 2 files changed, 0 insertions(+), 4 deletions(-)

diff --git a/bin/egencache b/bin/egencache
index 66854e1..6229ed6 100755
--- a/bin/egencache
+++ b/bin/egencache
@@ -816,9 +816,6 @@ def egencache_main(args):
 		return 1
 
 	if options.update and 'metadata-transfer' not in settings.features:
-		writemsg_level("ecachegen: warning: " + \
-			"automatically enabling FEATURES=metadata-transfer\n",
-			level=logging.WARNING, noiselevel=-1)
 		settings.features.add('metadata-transfer')
 
 	if options.update:

diff --git a/pym/portage/tests/emerge/test_simple.py b/pym/portage/tests/emerge/test_simple.py
index f3c9320..6810d05 100644
--- a/pym/portage/tests/emerge/test_simple.py
+++ b/pym/portage/tests/emerge/test_simple.py
@@ -190,7 +190,6 @@ src_install() {
 		var_cache_edb = os.path.join(eprefix, "var", "cache", "edb")
 
 		features = []
-		features.append("metadata-transfer")
 		if not portage.process.sandbox_capable:
 			features.append("-sandbox")
 



             reply	other threads:[~2011-09-07 17:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-07 17:50 Zac Medico [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-01 23:50 [gentoo-commits] proj/portage:master commit in: pym/portage/tests/emerge/, bin/ Zac Medico
2018-05-01 18:15 Zac Medico
2014-11-14 17:29 Zac Medico
2013-03-21  0:38 Zac Medico
2013-02-10 20:14 Zac Medico
2011-09-05 22:36 Zac Medico

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=5e1f136ba4c4f31dd5540594f48dc42f62ee09d9.zmedico@gentoo \
    --to=zmedico@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