pkgsrc-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: changing default python version to 3.11?



Hej,

probably it’s just me with some weird production setup running.

> Am 24.07.2023 um 17:00 schrieb Greg Troxel <gdt%lexort.com@localhost>:
>
> Greg Troxel <gdt%lexort.com@localhost> writes on 29 June 2023:
>
>> Adam <adam%netbsd.org@localhost> writes:
>>
>>> By the way, maybe Python 3.11 should be the default from now on?
>>
>> So by the "really close to as many packages building" it seems that
>> moving to 3.11 is ok.
>>
>> Other thoughts?  (Especially anybody who sees trouble I missed!)
>
> There have been no comments objecting to moving the default to 3.11
> after 3.5 weeks and one positive comment.
I was fine with that expecting nothing serious.
But on the production machine i run i was updating perl to 5.8 and that hit me in the middle because some of the dependent packages (which seem to be essentially all ;-)) was dependent on some python stuff.  The production ran 3.9 since forever but the new default triggered some package builds with 311.  not a problem, i thought.

Until make update bailed out:
———

=> Tool dependency py311-packaging-[0-9]*: NOT found
=> Verifying update for ../../devel/py-packaging
===> Checking for vulnerabilities in py311-packaging-23.1
=> Bootstrap dependency digest> 211023: found digest-20220214
=> Bootstrap dependency wget-[0-9]*: found wget-1.21.4
=> Checksum BLAKE2s OK for packaging-23.1.tar.gz
=> Checksum SHA512 OK for packaging-23.1.tar.gz
===> Installing dependencies for py311-packaging-23.1
=========================================================================The following variables will affect the build process of this package,
py311-packaging-23.1.  Their current value is shown below:

       * PYTHON_VERSION_DEFAULT = 311

Based on these variables, the following variables have been set:

       * PYPACKAGE = python311

You may want to abort the process now with CTRL-C and change the value
of variables in the first group before continuing.  Be sure to run
`/usr/bin/make clean' after the changes.
==========================================================================> Tool dependency py311-setuptools-[0-9]*: NOT found
=> Verifying update for ../../devel/py-setuptools
===> Checking for vulnerabilities in py311-setuptools-68.0.0
=> Bootstrap dependency digest> 211023: found digest-20220214
===> Checking for vulnerabilities in py311-setuptools-68.0.0
===> Building for py311-setuptools-68.0.0
/usr/bin/env USETOOLS=no PTHREAD_CFLAGS=\ -pthread\  PTHREAD_LDFLAGS=\ -pthread PTHREAD_LIBS= PTHREADBASE=/usr DL_CFLAGS=\ -pthread\  DL_LDFLAGS=\ -pthread DL_LIBS= PYTHON=/usr/pkg/bin/python3.11 CC=gcc CFLAGS=-O2\ -I/usr/include CPPFLAGS=-I/usr/include CXX=c++ CXXFLAGS=-O2\ -I/usr/include COMPILER_RPATH_FLAG=-Wl,-R F77=gfortran FC=gfortran FFLAGS=-O LANG=C LC_ALL=C LC_COLLATE=C LC_CTYPE=C LC_MESSAGES=C LC_MONETARY=C LC_NUMERIC=C LC_TIME=C LDFLAGS=-Wl,-zrelro\ -L/usr/lib\ -Wl,-R/usr/lib\ -Wl,-R/usr/pkg/lib LINKER_RPATH_FLAG=-R PATH=/usr/pbulk/devel/py-setuptools/work/.cwrapper/bin:/usr/pbulk/devel/py-setuptools/work/.buildlink/bin:/usr/pbulk/devel/py-setuptools/work/.gcc/bin:/usr/pbulk/devel/py-setuptools/work/.tools/bin:/usr/pkg/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/pkg/sbin:/usr/pkg/bin:/usr/X11R7/bin:/usr/local/sbin:/usr/local/bin:/usr/pkg/bin:/usr/pkg/bin PREFIX=/usr/pkg MAKELEVEL=0 CONFIG_SITE= PKG_SYSCONFDIR=/usr/pkg/etc CXXCPP=cpp HOME=/usr/pbulk/devel/py-setuptools/work/.home CWRAPPERS_CONFIG_DIR=/usr/pbulk/devel/py-setuptools/work/.cwrapper/config CPP=cpp LOCALBASE=/usr/pkg X11BASE=/usr/pkg PKGMANDIR=man PKGINFODIR=info PKGGNUDIR=gnu/ MAKECONF=/dev/null OBJECT_FMT=ELF USETOOLS=no BSD_INSTALL_PROGRAM=/usr/bin/install\ -c\ -s\ -o\ root\ -g\ wheel\ -m\ 755 BSD_INSTALL_SCRIPT=/usr/bin/install\ -c\ -o\ root\ -g\ wheel\ -m\ 755 BSD_INSTALL_LIB=/usr/bin/install\ -c\ -o\ root\ -g\ wheel\ -m\ 755 BSD_INSTALL_DATA=/usr/bin/install\ -c\ -o\ root\ -g\ wheel\ -m\ 644 BSD_INSTALL_MAN=/usr/bin/install\ -c\ -o\ root\ -g\ wheel\ -m\ 644 BSD_INSTALL=/usr/bin/install BSD_INSTALL_PROGRAM_DIR=/usr/bin/install\ -d\ -o\ root\ -g\ wheel\ -m\ 755 BSD_INSTALL_SCRIPT_DIR=/usr/bin/install\ -d\ -o\ root\ -g\ wheel\ -m\ 755 BSD_INSTALL_LIB_DIR=/usr/bin/install\ -d\ -o\ root\ -g\ wheel\ -m\ 755 BSD_INSTALL_DATA_DIR=/usr/bin/install\ -d\ -o\ root\ -g\ wheel\ -m\ 755 BSD_INSTALL_MAN_DIR=/usr/bin/install\ -d\ -o\ root\ -g\ wheel\ -m\ 755 BSD_INSTALL_GAME=/usr/bin/install\ -c\ -s\ -o\ root\ -g\ wheel\ -m\ 2555 BSD_INSTALL_GAME_DATA=/usr/bin/install\ -c\ -o\ root\ -g\ wheel\ -m\ 664 BSD_INSTALL_GAME_DIR=/usr/bin/install\ -d\ -o\ root\ -g\ wheel\ -m\ 775 INSTALL_INFO= MAKEINFO=/usr/pbulk/devel/py-setuptools/work/.tools/bin/makeinfo FLEX= BISON= TARGET_ARCH= ITSTOOL=/usr/pbulk/devel/py-setuptools/work/.tools/bin/itstool GDBUS_CODEGEN=/usr/pbulk/devel/py-setuptools/work/.tools/bin/gdbus-codegen PKG_CONFIG=/usr/pbulk/devel/py-setuptools/work/.tools/bin/pkg-config PKG_CONFIG_LIBDIR=/usr/pbulk/devel/py-setuptools/work/.buildlink/lib/pkgconfig:/usr/pbulk/devel/py-setuptools/work/.buildlink/share/pkgconfig PKG_CONFIG_LOG=/usr/pbulk/devel/py-setuptools/work/.pkg-config.log PKG_CONFIG_PATH= CWRAPPERS_CONFIG_DIR=/usr/pbulk/devel/py-setuptools/work/.cwrapper/config /usr/pkg/bin/python3.11 -m ensurepip --user
env: /usr/pkg/bin/python3.11: No such file or directory
*** Error code 127
——

This is quite reasonable, in that pyhon311 is not installed.  But shouldn’t it be installed if something needs it, like a python311-package?
And yes, this can be fixed manually.  And yes, I am to blame because i did not fix pyhton39 as the default for this machine…

Cheers
	Oskar

Attachment: smime.p7s
Description: S/MIME cryptographic signature



Home | Main Index | Thread Index | Old Index