Re: Python 3.13 and massive USE flag changes.
Michael <[email protected]> Sun, 07 Jun 2026 09:27:59 +0100
| Newsgroups | gmane.linux.gentoo.user |
|---|---|
| Message-ID | <[email protected]> |
--nextPartZ8YyVFmhRMeco7IJa60opA Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8"; protected-headers="v1" From: Michael <[email protected]> To: [email protected] Reply-To: [email protected] Subject: Re: [gentoo-user] Python 3.13 and massive USE flag changes. Date: Sun, 07 Jun 2026 09:27:59 +0100 Message-ID: <[email protected]> In-Reply-To: <[email protected]> MIME-Version: 1.0 On Sunday, 7 June 2026 09:00:46 British Summer Time Dale wrote: > On 6/6/26 5:06 AM, Dale wrote: > > If I read your reply correctly, that is what you are saying. I > > should be able to skip from current OS before the switch directly > > to new python after all stages of the upgrade path using binaries > > from the chroot. The key word being should of course. ;-) > > > > Dale > > > > :-) :-) > > Just in case someone else does their updates in a chroot or similar > environment. In the chroot, I did the complete safer upgrade process > in the news item, except --depclean. During that I had to remove > elogviewer as it doesn't seem to have python 3.14 support yet. I > then copied the binaries over to my main install and did a emerge > -aukDN world. I made sure it had all binaries available, total > packages and total binaries is the same. I did get a failure of > portage itself during the upgrade process. Was portage in the chroot system and the main OS in sync, or had you ran 'emerge --sync' at different times on each system? > I updated portage by > itself and it updated without error. I guess something was out of > sync during the upgrade so I'd recommend upgrading portage before > doing a emerge -aukDN world just to give it a jump start. Was portage updated successfully on the main OS using the chrooted binary, or was it built afresh from source? --nextPartZ8YyVFmhRMeco7IJa60opA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQJPBAABCAA5FiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmolK48bFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMiwyAAoJELHqqvbClWcZmvUP/iDXffZuEW8Pf36To12Z ko32aS5SwN0MOJyCk5qmwGREvC2/BkdJHHM3tgMmZuhf2X5A4mDxAQiQ2EZeLdya YIsu3mCFnwBZoWxzLigeCVik58U1K8eVMlrYeKkPHFATGqEh9VHrSLJYn18SKvhi 4/Uk9hZ/MEG6X8+62L+sYROplkzY48RM++hGTOHCggJwgNSRqs3qp3sVM93dzPuq x2uC2SnB3hcBLQiB4kmNbS7iQ7sL2IHYBGRBbciPM6CCBopdmZ/qadX8AzBODChL KkfBWxjizFbKroBpRHPvhjZMdsVmH94dZyLbOlG9yxwWYgjCYKjn5Mb81kPtoEEE lQojaikNj4uQMQljNCPrl2tM/Ox8UVxd+IGA067gN7DnUcf962dQ3ozTSHcvmm+A myVQfnQ6TrScHHEmJ74FBgezY5GSEd29F9gCl+7FmRn4R71rfhyE3YIGtZ0Cm0mR bPXt5m2ZQ2aLjRK0pzgFRn5+qrWcXwDKj0utGpiLq+wLd4SAdseu2hoYixxFIqpj OiQk1i2mNDMYNfKkQ41doEMlh0NboTFyaxt2iuK7sOalGUHkXziGDOPLMRLMmFTy D1VpbbdUjar1+/A9JL/LrPKfHZ/wZwglP8JgkvsSO2iP2S8QBNw8Mcz3OEA54eON EPTEk9Nc/73yZly/g7IY15qs =0p89 -----END PGP SIGNATURE----- --nextPartZ8YyVFmhRMeco7IJa60opA--