Date: Mon, 03 Jun 2024 10:07:04 -0400 From: Joseph Mingrone <jrm@FreeBSD.org> To: Baptiste Daroussin <bapt@freebsd.org> Cc: Ruslan Makhmatkhanov <rm@freebsd.org>, ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: 988da7290c99 - main - ./UPDATING: mention the python default version change Message-ID: <86frtu6rxz.fsf@phe.ftfl.ca> In-Reply-To: <pupckib4hcq2tiqesuyxfodzz7q6rcjnzn6625qhsazzehaotd@gxm54qjiyxuq> (Baptiste Daroussin's message of "Mon, 3 Jun 2024 15:45:05 %2B0200") References: <202405291420.44TEKdBd073352@gitrepo.freebsd.org> <pupckib4hcq2tiqesuyxfodzz7q6rcjnzn6625qhsazzehaotd@gxm54qjiyxuq>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-=-= Content-Type: text/plain On Mon, 2024-06-03 at 15:45, Baptiste Daroussin <bapt@freebsd.org> wrote: > On Wed 29 May 14:20, Ruslan Makhmatkhanov wrote: >> The branch main has been updated by rm: >> URL: https://cgit.FreeBSD.org/ports/commit/?id=988da7290c997a29581bb828bd59257060d8ddbc >> commit 988da7290c997a29581bb828bd59257060d8ddbc >> Author: Ruslan Makhmatkhanov <rm@FreeBSD.org> >> AuthorDate: 2024-05-29 14:20:07 +0000 >> Commit: Ruslan Makhmatkhanov <rm@FreeBSD.org> >> CommitDate: 2024-05-29 14:20:07 +0000 >> ./UPDATING: mention the python default version change >> --- >> UPDATING | 33 +++++++++++++++++++++++++++++++++ >> 1 file changed, 33 insertions(+) >> diff --git a/UPDATING b/UPDATING >> index 7a5fc11c35ec..f0077905cb2d 100644 >> --- a/UPDATING >> +++ b/UPDATING >> @@ -5,6 +5,39 @@ they are unavoidable. >> You should get into the habit of checking this file for changes each time >> you update your ports collection, before attempting any port upgrades. >> +20240529: >> + AFFECTS: users of python >> + AUTHOR: rm@FreeBSD.org >> + >> + The default version of python3 and python was switched to 3.11. >> + >> + For ports users wanting to keep version 3.9 as default, >> + add DEFAULT_VERSIONS+= python=3.9 python3=3.9 to make.conf >> + >> + Following procedures may ease the upgrade: >> + >> + For users of pre-build packages: >> + # sh >> + # for i in $(pkg query -g %n 'py39-*'); do pkg set -yn ${i}:py311-${i#py39-}; done > I don't think it is a good advice at all, pkg set should not be necessary at > all, what case are we trying to fix by providing this advice? A user has the package py39-blah, which was explicitly installed. Now, when the user does `pkg upgrade`, py311-blah won't replace py39-blah. IMO, that's a problem. We gave similar advice when the emacs ports had version information in the package name (other than PKGVERSION at the end). --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKkBAEBCgCOFiEEVbCTpybDiFVxIrrVNqQMg7DW754FAmZdzghfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDU1 QjA5M0E3MjZDMzg4NTU3MTIyQkFENTM2QTQwQzgzQjBENkVGOUUQHGpybUBmcmVl YnNkLm9yZwAKCRA2pAyDsNbvnhXJD/0fsbe4JIEFS/Gq+9aRTc4Sdzhh7niP/366 p4XMsu6A9+2lMiE0GNXOWh/czm+N8Zzmm4bYfWIk1uyljgjCKx8SxZAC8Uh3qhDG PK9sBzxIxSJ66e2UHTTZEtGnUcln4Aq0JEJVMudmErPOV+JZzymgK18Qzb3ZBcVG THsQev7X/V8WBRVXSf1NX1dQ06GUM99uaUuGAeUJyWs7El6Fc6FPgcvUYnyBzIG9 mmAAnuZqtxX1i1v94W+gGgP8fqjbrmHUBTrp3EBj23+9NkNaRD2KFFqJyQl3I4QZ nXU6aLGqd+VUtEtkZfvhX51Kf7CyRkB3hh0ZQEpHchu9n0J5mC4Uq8VjZAqQ1lrD eltDRtava+hLr1VYpS80AXSQYORX1+mIzBsWD8dSOZhxTG03ub2o716IyXd8ncED GiFfLSs0f9h49e5CbbZR1EjR51nB4/GILN011saxgpWvazdTsAjCuFnXWopGqQdm KL3oVBrzw+APEpPRlECOjk5yFe0gcFJEYQZu4ehpf/N0Q0yoE5gGTh30CHqt5g5N bF6qsZMOO+PXAcwN/NgdxvX97rTlgbUzKnr2BZTCHNvGh1O8uGnl/zbX8UXf5Vcd SHdg7av0p4UoKq07eg6A/nVU3jaUTf9oRzk33v1/8GyXUWYXiQ3akTJm/nzju97e bBplgOenTQ== =bOPV -----END PGP SIGNATURE----- --=-=-=--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86frtu6rxz.fsf>