-
oneforall2
definitely does want to create the virtualenv 2.53.18.3
-
oneforall2
will compare this virtualenv.py against .2's
-
oneforall2
oh duh meant 2.53.19
-
oneforall2
lots of diff
-
frg_Away
-
frg_Away
...
-
frg_Away
It seems that the package that caused my issue was python3-setuptools.
-
frg_Away
After I have uninstalled python3-setuptools, build ran without problems, I just need to use
-
frg_Away
MACH_USE_SYSTEM_PYTHON=1, without which I had problems building zstandard
-
oneforall2
MACH_USE_SYSTEM_PYTHON=1 i have that
-
oneforall2
what version of python3-setuptools I have 75.1.0
-
frg_Away
oneforall2 python setuptools need to be deinstalled for now. Might be fixed in the latest tree but can't test
-
nsITobin
frg_Away: we have no real control which python is being executed
-
nsITobin
i literally cannot get the thing to execute with a specific python by any other means than running it with python
-
frg_Away
nsITobin this is poython setuptools not python
-
nsITobin
yeah but i can't run with anything but python3.6 because that is the designated system python
-
nsITobin
the result of calling python3
-
nsITobin
on here
-
nsITobin
its gonna be different for every system
-
nsITobin
he is likely getting conflicts with running it as a shell command is ALWAYS gonna run virtualenv OR "python3"
-
nsITobin
no env just whatever python3 is and PYTHON env var is ignore despite the fact that it has a bash stub header
-
frg_Away
In Rocky 8 sudo alternatives --remove python3 /usr/bin/python3
-
frg_Away
Not sure why it defaults to 3.6?
-
nsITobin
yeah well the build system should TRY from newest to oldest to find a working version of python it knows how to use.. rocky defaults to 3.6 because 3.6 IS the system python version needed for dnf mozilla patches assume you either have the correct system python or gonna be using the artifact version
-
frg_Away
As fas as I know support for 3.6 is gone from mozilla
-
nsITobin
when it was 2.7 it tried various bin names to find its self that should have been expanded when it was obvious every python 3 version is incompatible forwards and backwards with every other python 3 version
-
frg_Away
I updated 2.53 xyesterday with patvches stating 3.7
-
nsITobin
using 3.11 it fails for zstandard
-
frg_Away
Worked last time under Windows. Need to check
-
oneforall2
frg_Away yeah tried that and still fails internal was 49.x
-
nsITobin
oneforall2: use older python
-
nsITobin
remove python 3.11
-
nsITobin
i dunno
-
njsg
any chance a symlink along with PATH can affect this, or it's immune to such suggestions too?
-
nsITobin
i think the build system is fighting with its self
-
nsITobin
i am certainly fighting with it in ways I shouldn't be
-
njsg
e.g. mkdir $HOME/python-link && cd python-link && ln -s /usr/bin/python3runthis python3 , then PATH="$HOME/python-link:$PATH"
-
nsITobin
that's just plain unacceptable
-
njsg
need to read the bug, because this is quite bittle if the build system or python try to guess by themselves where the "right" python is
-
oneforall2
something in virtualenv.py breaks it cause 2.53.18.2 has no problem compiling
-
nsITobin
the build system needs eithe reverted back to its original 56 state and adapted properly or it needs to be replaced with a newer complete mozilla build system
-
nsITobin
because first and foremost the build system is needed to do anything else
-
oneforall2
I only have 1 python installed
-
nsITobin
and its the wrong python good job
-
oneforall2
well as said its seamonkey broke now since that last one compiles with 3.11.10
-
frg_Away
the build fixes in 2.53.19 are a bit half baked. 2.53.20 should be better. Not fully baked but ok. Will check 3.11 compile
-
oneforall2
python-zstandard-0.22.0 noticed it wanted old wheel etc so compiles the old waywith setup
-
oneforall2
unshare -n python3 setup.py install --root=$PKG
-
oneforall2
build --wheel etc needs a version bump :)
-
oneforall2
I meaqn in the zstandard src
-
frg_Away
nsITobin the current 2.53 source works for me in Rocky 8 with its python 3.11
-
oneforall2
frg_Away 253-nightly-source.tar.xz ?
-
frg_Away
yes
-
oneforall2
same problem
-
frg_Away
I used mach mach-create-mach-environment. Will retry with system pathon set to 1
-
frg_Away
Sorry can't reproduce in Rocky 8 with pytho 3.11.9
-
frg_Away
^python
-
oneforall2
added seed packages: pip==20.3.1, setuptools==51.0.0, wheel==0.36.1 notice its not using the system wheel setuptools pip
-
oneforall2
not finding --with-system-pip etc
-
frg_Away
As Myckel stated in the bug should eventually be fixed when we move mores stuff in. Linux ins unfortunately a pain with every distribution different.
-
oneforall2
not a fan of python :)
-
oneforall2
whats the url for this bug?
-
njsg
tobin: to paraphrase a trending DNS mantra out there: It is not the python version\nThere is no way it's the python version\nIt was the python version
-
njsg
oneforall2: probably
bugzil.la/1909061
-
oneforall2
hmm notice too the 253.18.2 is using setup.py that does make a diff
-
tomman
-
njsg
I'll check once social.sdf.org de-500s itself