public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/prefix:master commit in: sys-apps/portage/
Date: Tue, 18 Jun 2019 14:01:45 +0000 (UTC)	[thread overview]
Message-ID: <1560866492.b64077d9e52a7cdd8fa2c28d6eb54d3e7db54183.grobian@gentoo> (raw)

commit:     b64077d9e52a7cdd8fa2c28d6eb54d3e7db54183
Author:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Tue Jun 18 13:59:07 2019 +0000
Commit:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Tue Jun 18 14:01:32 2019 +0000
URL:        https://gitweb.gentoo.org/repo/proj/prefix.git/commit/?id=b64077d9

sys-apps/portage: drop asyncio kludge for Darwin9, python was fixed

Bug: https://bugs.gentoo.org/656830
Package-Manager: Portage-2.3.67-prefix, Repoman-2.3.14
Signed-off-by: Fabian Groffen <grobian <AT> gentoo.org>

 sys-apps/portage/portage-2.3.67.ebuild | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/sys-apps/portage/portage-2.3.67.ebuild b/sys-apps/portage/portage-2.3.67.ebuild
index 1dbd5b1874..2adb83959c 100644
--- a/sys-apps/portage/portage-2.3.67.ebuild
+++ b/sys-apps/portage/portage-2.3.67.ebuild
@@ -166,13 +166,6 @@ python_prepare_all() {
 		einfo "Making absent gemato non-fatal"
 		sed -i -e '/exitcode = 127/d' \
 			lib/portage/sync/modules/rsync/rsync.py || die
-
-		if [[ ${CHOST} == powerpc*-darwin* ]] ; then
-			# asyncio triggers some python bug, not worth fixing on
-			# ppc-macos, bug #656830
-			sed -i -e '/^_asyncio_enabled/s/=.*$/= False/' \
-				lib/portage/util/_eventloop/global_event_loop.py || die
-		fi
 		# END PREFIX LOCAL
 	fi
 


             reply	other threads:[~2019-06-18 14:01 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18 14:01 Fabian Groffen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-25  9:54 [gentoo-commits] repo/proj/prefix:master commit in: sys-apps/portage/ Fabian Groffen
2024-01-14 10:19 Fabian Groffen
2024-01-14 10:17 Fabian Groffen
2023-12-03 10:19 Fabian Groffen
2023-11-25 19:14 Fabian Groffen
2023-11-25 18:46 Fabian Groffen
2023-06-22 11:11 Fabian Groffen
2023-06-17  9:06 Fabian Groffen
2023-02-01 20:08 Sam James
2022-07-26 19:46 Fabian Groffen
2022-07-24 19:38 Fabian Groffen
2022-07-03 19:06 Fabian Groffen
2022-01-16 10:05 Fabian Groffen
2022-01-14  7:50 Fabian Groffen
2021-07-06  7:35 Fabian Groffen
2021-04-16 13:13 Fabian Groffen
2021-04-10  7:06 Sam James
2021-01-24  9:42 Fabian Groffen
2021-01-04 12:12 Fabian Groffen
2021-01-04 11:00 Fabian Groffen
2021-01-04 10:53 Fabian Groffen
2020-12-27 11:07 Fabian Groffen
2020-12-22 21:30 Fabian Groffen
2020-11-28 20:06 Fabian Groffen
2020-11-23 10:27 Fabian Groffen
2020-11-22 11:30 Fabian Groffen
2020-09-26 11:37 Fabian Groffen
2020-06-08  8:20 Fabian Groffen
2020-06-06  8:09 Fabian Groffen
2020-01-08 19:22 Fabian Groffen
2019-07-01 13:28 Fabian Groffen
2019-05-30  9:27 Fabian Groffen
2019-05-30  9:16 Fabian Groffen
2019-02-28 12:50 Fabian Groffen
2019-01-12  9:13 Fabian Groffen
2019-01-11 10:43 Fabian Groffen
2019-01-07 10:36 Fabian Groffen
2019-01-07 10:36 Fabian Groffen
2018-12-23 20:04 Fabian Groffen
2018-06-17 14:54 Fabian Groffen
2018-05-29  9:04 Fabian Groffen
2018-05-28 15:34 Fabian Groffen
2018-05-25 20:06 Fabian Groffen
2018-01-18 12:16 Michael Haubenwallner
2017-12-12  9:14 Fabian Groffen
2017-10-29 15:07 Fabian Groffen
2017-10-03  7:41 Fabian Groffen
2017-09-22 10:38 Fabian Groffen
2017-08-21 13:33 Fabian Groffen
2017-08-13  7:44 Fabian Groffen
2017-08-13  7:44 Fabian Groffen
2017-08-13  7:44 Fabian Groffen
2016-04-03 18:09 Fabian Groffen
2016-03-20 20:02 Fabian Groffen
2016-02-29 18:32 Fabian Groffen
2016-02-21  9:10 Fabian Groffen
2016-01-21 12:11 Fabian Groffen

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=1560866492.b64077d9e52a7cdd8fa2c28d6eb54d3e7db54183.grobian@gentoo \
    --to=grobian@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