From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 23C69139694 for ; Sun, 9 Apr 2017 23:16:02 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 091BF21C07B; Sun, 9 Apr 2017 23:15:53 +0000 (UTC) Received: from mail1.obsidian-studios.com (mail.obsidian-studios.com [173.230.135.215]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 96E4FE0D0A for ; Sun, 9 Apr 2017 23:15:52 +0000 (UTC) Received: (qmail 25546 invoked from network); 9 Apr 2017 23:15:51 -0000 Received: from unknown (HELO assp1.obsidian-studios.com) (wlt-ml@::ffff:127.0.0.1) by ::ffff:127.0.0.1 with ESMTPA; 9 Apr 2017 23:15:51 -0000 X-Assp-Version: 2.5.5(16366) on assp1.obsidian-studios.com X-Assp-ID: assp1.obsidian-studios.com m1-79751-06212 X-Assp-Session: 32A14263740 (mail 1) X-Assp-Envelope-From: wlt-ml@o-sinc.com X-Assp-Intended-For: gentoo-dev@lists.gentoo.org X-Assp-Server-TLS: yes Received: from unknown ([fdbe:bad:a55:0:1::211] helo=localhost) by assp1.obsidian-studios.com with SMTPSA(TLSv1_2 ECDHE-RSA-AES128-GCM-SHA256) (2.5.5); 9 Apr 2017 19:15:51 -0400 Date: Sun, 9 Apr 2017 19:15:50 -0400 From: "William L. Thomson Jr." To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Reverse use of Python/Ruby versions Message-ID: In-Reply-To: <20170409152002.550f3b4d.dolsen@gentoo.org> References: <20170409152002.550f3b4d.dolsen@gentoo.org> Organization: Obsidian-Studios, Inc. X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; 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_/=0E=dSFhM9a19wW2AWh3FpD"; protocol="application/pgp-signature" X-Archives-Salt: 971bfa06-b834-4f89-87b0-7010753aee5b X-Archives-Hash: 5f8b04d69dfbce7d284aef8d496e1daa --Sig_/=0E=dSFhM9a19wW2AWh3FpD Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sun, 9 Apr 2017 15:20:02 -0700 Brian Dolbec wrote: >=20 > This could be partially automated using buildbot. The easiest would > be for pkgs containing working test suites. Those that pass could be > auto-enabled with that python with ~arch keywords. I think if a > stable pkg is to be added the new python, it should be via a revision > bump and ~arch'ing the keywords. But we could enforce the bot to > rev-bump all ebuilds just as easily. =20 If the package failed, all that would need to be done kinda like now is a given variable modified in the ebuild. Just marking what ever it did not work with. As mentioned that could be done via my ebuild-batcher[1], though same functionality is easily replicated. I also have an ebuild-bumper[2], that could be made more advanced. I am aware of ebump, but ebuild-bumper is a bit different. It works with sets of ebuilds for bumps and cleaning. It can do individual as well but so can ebump. I plan to further automate ebuild-bumper with something that tracks upstream releases and attempts to automate bumps. Though even running it manually is not cumbersome. Just prefer zero day as much as possible. 1. https://github.com/Obsidian-StudiosInc/ebuild-batcher 2. https://github.com/Obsidian-StudiosInc/ebuild-bumper --=20 William L. Thomson Jr. --Sig_/=0E=dSFhM9a19wW2AWh3FpD Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTEeldqZjmVut8bVHJNcbKkg6ozUAUCWOrApgAKCRBNcbKkg6oz UJlMAJ4mzwfSfgVDPLUohqgkIHcSkqOQtwCgikezDXey/nfMmBoe6T08BwWiih0= =244H -----END PGP SIGNATURE----- --Sig_/=0E=dSFhM9a19wW2AWh3FpD--