public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Thomas Sachau" <tommy@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/multilib-portage:master commit in: profiles/base/
Date: Sat, 24 Mar 2012 16:35:25 +0000 (UTC)	[thread overview]
Message-ID: <1332606868.644a7034306ac907d3ee6e5dca403b7dd5a113c7.tommy@gentoo> (raw)

commit:     644a7034306ac907d3ee6e5dca403b7dd5a113c7
Author:     Thomas Sachau <tommy <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 18 15:10:55 2012 +0000
Commit:     Thomas Sachau <tommy <AT> gentoo <DOT> org>
CommitDate: Sat Mar 24 16:34:28 2012 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/multilib-portage.git;a=commit;h=644a7034

wrapped corutils cause failure of pkg_preinst of sys-libs/glibc, so dont wrap them

---
 profiles/base/make.defaults |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/profiles/base/make.defaults b/profiles/base/make.defaults
index 791047b..87a1b5a 100644
--- a/profiles/base/make.defaults
+++ b/profiles/base/make.defaults
@@ -12,7 +12,9 @@ MULTILIB_BINARIES="dev-lang/perl dev-lang/python dev-lang/ruby dev-libs/gobject-
 	net-libs/courier-authlib x11-libs/qt-core x11-libs/qt-gui media-libs/fontconfig www-servers/apache \
 	x11-libs/pango x11-libs/gtk+"
 
-RESTRICT_MULTILIB_BINARIES="sys-apps/abi-wrapper dev-vcs/git"
+#git fails to run as wrapped binary
+#wrapped coreutils result in failing pkg_preinst phase for sys-libs/glibc
+RESTRICT_MULTILIB_BINARIES="dev-vcs/git sys-apps/abi-wrapper sys-apps/coreutils"
 
 USE="${USE} multilib"
 



             reply	other threads:[~2012-03-24 16:37 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-24 16:35 Thomas Sachau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-20 13:10 [gentoo-commits] proj/multilib-portage:master commit in: profiles/base/ Thomas Sachau
2021-09-18  6:34 Thomas Sachau
2021-09-18  6:34 Thomas Sachau
2021-04-03  8:42 Thomas Sachau
2017-12-28 11:51 Thomas Sachau
2017-12-26 14:03 Thomas Sachau
2017-12-25 14:23 Thomas Sachau
2014-04-13 16:51 Thomas Sachau
2014-04-10 23:39 Thomas Sachau
2014-03-01 11:22 Thomas Sachau
2014-03-01 11:21 Thomas Sachau
2014-03-01 11:20 Thomas Sachau
2013-10-05 11:42 Thomas Sachau
2013-10-05 11:38 Thomas Sachau
2013-09-21 12:33 Thomas Sachau
2013-09-15 11:37 Thomas Sachau
2013-09-15 11:37 Thomas Sachau
2013-03-31 11:54 Thomas Sachau
2013-03-24 12:28 Thomas Sachau
2013-03-23 16:10 Thomas Sachau
2013-03-06 19:54 Thomas Sachau
2013-03-06 19:48 Thomas Sachau
2013-03-06 19:48 Thomas Sachau
2013-03-06 19:42 Thomas Sachau
2013-03-06 19:41 Thomas Sachau
2013-03-03 15:18 Thomas Sachau
2013-03-03 15:18 Thomas Sachau
2012-11-17 19:44 Nathan Phillip Brink
2012-07-24  6:08 Nathan Phillip Brink
2012-05-26 18:07 Thomas Sachau
2012-05-01 14:35 Thomas Sachau
2012-05-01 14:35 Thomas Sachau
2012-04-29 12:40 Thomas Sachau
2012-04-29 12:36 Thomas Sachau
2012-04-18 17:35 Thomas Sachau
2012-04-04 16:22 Thomas Sachau
2012-04-04 16:18 Thomas Sachau
2012-04-04 10:16 Thomas Sachau
2012-04-02 19:52 Thomas Sachau
2012-04-01 23:00 Thomas Sachau
2012-04-01 16:54 Thomas Sachau
2012-04-01  0:08 Thomas Sachau
2012-03-31 23:42 Thomas Sachau
2012-03-31 23:11 Thomas Sachau
2012-03-29 19:02 Thomas Sachau
2012-03-29 18:25 Thomas Sachau
2012-03-26 15:36 Nathan Phillip Brink
2012-03-24 18:45 Nathan Phillip Brink
2012-03-24 16:35 Thomas Sachau
2012-03-24 16:35 Thomas Sachau
2012-03-24 16:35 Thomas Sachau
2012-03-24 16:35 Thomas Sachau
2012-03-24 16:35 Thomas Sachau
2012-03-24 16:35 Thomas Sachau
2012-03-14 21:38 Nathan Phillip Brink
2012-03-12 22:34 Nathan Phillip Brink
2012-03-12 18:00 Nathan Phillip Brink
2012-03-07 19:54 Thomas Sachau
2012-03-07 19:54 Thomas Sachau

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=1332606868.644a7034306ac907d3ee6e5dca403b7dd5a113c7.tommy@gentoo \
    --to=tommy@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