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 D95D8138334 for ; Sat, 21 Dec 2019 06:57:37 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 88149E08DA; Sat, 21 Dec 2019 06:57:33 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id AA25EE0897 for ; Sat, 21 Dec 2019 06:57:32 +0000 (UTC) Received: from a1i15 (a1i15.kph.uni-mainz.de [134.93.134.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: ulm) by smtp.gentoo.org (Postfix) with ESMTPSA id 2175834D4D8; Sat, 21 Dec 2019 06:57:30 +0000 (UTC) From: Ulrich Mueller To: Michael Orlitzky Cc: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [PATCH 0/3] elisp{,-common}.eclass update for emacs-vcs consolidation References: <3002c804-e70f-5b50-ee38-d91aa7e22fb0@gentoo.org> Date: Sat, 21 Dec 2019 07:57:22 +0100 In-Reply-To: (Michael Orlitzky's message of "Thu, 19 Dec 2019 20:19:46 -0500") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) 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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-Archives-Salt: 6d104210-25ea-4370-8bb9-0c74d26e2266 X-Archives-Hash: 417287cc6c73fd228cfcde553d756d1d --=-=-= Content-Type: text/plain >>>>> On Fri, 20 Dec 2019, Michael Orlitzky wrote: > Portage seems OK with the missing dependency, but for the overall plan > to work, you have to wait a long time before deleting virtual/emacs; > otherwise the upgrade path is broken. With virtual/emacs-26 installed > and "old" copies of the elisp ebuilds installed, you get unsatisfied > dependencies switching from emacs-vcs to a live slot of emacs. Everyone > in that situation must update to virtual/emacs-26-r1, which they can't > do after you delete it. > And of course you can't mask virtual/emacs in the meantime, because that > does kill the PM. I have no plans of masking the virtual. It will be simply removed, presumably after the app-editors/emacs-27.1 release (at which point any emacs-vcs-27.0* will be outdated, and be blocked against by the ebuild). > New revisions would still be the sane solution, now and in the future, > because they don't require investigative journalism to uncover exactly > what might go wrong when we bend the rules /this time/. They also don't > impose a cutoff date after which upgrading users are screwed. You just > automate the revbumps, commit them all at once, and make a pull request > against CI to verify that nothing is too borked. See? You say it yourself, with 400 revbumps there is quite some chance for breakage. Ulrich --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEZlHkP3TnuTbxrN0HwwkGhRxhwnMFAl39wlIACgkQwwkGhRxh wnPN0gf+OL3ASR9bXjtYFVFB8pisSNsiXZrTEffYzJjYowBguQeG2eK/5+OJ5yT1 fnPJKPzku6NftWyvsyvJUsLGX2IHZzldxy9IKZ6MG9xQKKoK+KwvHKafC23P8vT4 nxtJb0JyKIIxJsxkXI60g4mj/kWKcS3AOdTmjfc+WdB9M/pLVGV4t9I2kfFn2v4l p00bMKUYfrRru9clpd9wqXzo0akhcUAa+cT3uhAyrKjlNJXWjNROLWcmpnzwjxP2 OLZijGuLQfDPF7wCyWGiWpOCXWjAW9zibCHSLByVrL+jOFYKGvGsgJXS1xmAz4PU LW+32CT0YjSpNMxxJjQv1UZ74C/VUA== =6tAo -----END PGP SIGNATURE----- --=-=-=--