From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 790DE138247 for ; Sat, 2 Nov 2013 13:52:15 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3C59DE0B0A; Sat, 2 Nov 2013 13:52:07 +0000 (UTC) Received: from jacques.telenet-ops.be (jacques.telenet-ops.be [195.130.132.50]) by pigeon.gentoo.org (Postfix) with ESMTP id 137B6E0B01 for ; Sat, 2 Nov 2013 13:52:05 +0000 (UTC) Received: from TOMWIJ-GENTOO ([94.226.55.127]) by jacques.telenet-ops.be with bizsmtp id kds51m0082khLEN0Jds5Nx; Sat, 02 Nov 2013 14:52:05 +0100 Date: Sat, 2 Nov 2013 14:51:26 +0100 From: Tom Wijsman To: mgorny@gentoo.org Cc: python@gentoo.org, gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Releng breakage with respect to move from dev-python/python-exec to dev-lang/python-exec Message-ID: <20131102145126.3c1f6cd7@TOMWIJ-GENTOO> In-Reply-To: <5274FB3D.8080508@gentoo.org> References: <5274FB3D.8080508@gentoo.org> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.17; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/Kz=bSx0aNrxMnczd5ARnL5g"; protocol="application/pgp-signature" X-Archives-Salt: 1d8b9149-cb01-441d-9225-cf6b40904eb1 X-Archives-Hash: 81f96921d1717c464b0023e9c509e123 --Sig_/Kz=bSx0aNrxMnczd5ARnL5g Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 02 Nov 2013 09:16:45 -0400 "Anthony G. Basile" wrote: > This is a followup to a discussion on IRC yesterday regarding > breakage that's occurring to catalyst builds as a result of the > recent move from dev-python/python-exec to dev-lang/python-exec. This has been happening to users as well, for example: http://forums.gentoo.org/viewtopic-t-973998.html http://forums.gentoo.org/viewtopic-t-974412.html To move forward and get this resolved, some questions: 1. Has this been resolved for users? Do they just need to sync? 2. If not resolved for users, what is the best temporary workaround? 3. Are you able to fix this? Do you need help to fix this? 4. Depending on the nature of the fix: Would a news item be needed? =46rom what I heard so far this isn't reproducible by the committer; so, is anyone else being able to reproduce this? I didn't experience this either; so, maybe this is only reproducible on a stable system? --=20 With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : TomWij@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D --Sig_/Kz=bSx0aNrxMnczd5ARnL5g Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJSdQNjAAoJEJWyH81tNOV9GTUH/RqOvSkzPsssRSWCQL9jMpO1 S/s3pURn9w9mt14lzPVt5mZfNW50agotYM4RRXl7v+OG8NIZYCM2j6PeI177Q9M8 640dnZ0GFD56qMEipWJZjvbDSbtIXfD4C5vVJs4iXIh5sLfzZeRN9Y1xuEQ2A6qC BjnsyhdsrdDRo+f5T1a3OKXHsR4LzEcfQcFSjQ6p9UejpxblgAdLFizMy1LKRpUg mZTldTpgNZhfXRe2LoeAo2O6NOk80DwTo3WlxI2gYlKSutPiLG6I2e61LphwgwoT +AIkjlqZvyd4DgO5uCmM31dBTr3tvXxddL2Xm4SRmBq2N+4IjAO8M/Ur+0TEP5A= =/cs8 -----END PGP SIGNATURE----- --Sig_/Kz=bSx0aNrxMnczd5ARnL5g--