Package installs with only following files: - METADATA - RECORD - WHEEL - README.rst.bz2 And later on, while installing `dev-python/poetry-core-1.7.0`, I get this: >ModuleNotFoundError: No module named jsonschema_specifications
Please post your `emerge --info` and your build.log from the faulty merge.
AMD64 also affected.
Created attachment 875861 [details] emerge --info '=dev-python/poetry-core-1.7.0::gentoo'
Created attachment 875862 [details] /var/tmp/portage/dev-python/poetry-core-1.7.0/temp/build.log
Comment on attachment 875861 [details] emerge --info '=dev-python/poetry-core-1.7.0::gentoo' Faulty build.
Comment on attachment 875862 [details] /var/tmp/portage/dev-python/poetry-core-1.7.0/temp/build.log Faulty merge ^
Created attachment 875863 [details] /var/tmp/portage/dev-python/jsonschema-specifications-2023.7.1/temp/build.log Suspected culprit merge log ^
Created attachment 875864 [details] emerge --info '=dev-python/jsonschema-specifications-2023.7.1' Suspected culprit merge info ^
I cannot reproduce your merge results for jsonschema-specifications.
1. Please share the output of `env`. 2. Please try extract a stage3 to e.g. /tmp/ or /opt and chroot in, then emerge dev-python/jsonschema-specifications. Does it work? If not, try emulate your existing setup until it breaks.
Created attachment 875915 [details] git diff --no-index jsonschema-specifications-2023.7.1*/temp/environment I found this peculiarity in environment diff between the healthy system and my case.
>I found this peculiarity ... Updated both machines to have the same distutils-r1.eclass, but still issue happening only on one of them.
So far what I've found is that `gpep517 build-wheel ...` produces different wheel archive on healthy and affected machines. Is there a way to run it with verbose logging? ``` # pwd /var/tmp/portage/dev-python/jsonschema-specifications-2023.11.1/work/jsonschema_specifications-2023.11.1 # gpep517 build-wheel --prefix=/usr --backend hatchling.build --output-fd 0 --wheel-dir /var/tmp/portage/dev-python/jsonschema-specifications-2023.11.1/work/jsonschema_specifications-2023.11.1-python3_11/wheel 2023-11-30 13:41:53,140 gpep517 INFO Building wheel via backend hatchling.build 2023-11-30 13:41:53,219 gpep517 INFO The backend produced /var/tmp/portage/dev-python/jsonschema-specifications-2023.11.1/work/jsonschema_specifications-2023.11.1-python3_11/wheel/jsonschema_specifications-2023.11.1-py3-none-any.whl jsonschema_specifications-2023.11.1-py3-none-any.whl # unzip -l /var/tmp/portage/dev-python/jsonschema-specifications-2023.11.1/work/jsonschema_specifications-2023.11.1-python3_11/wheel/jsonschema_specifications-2023.11.1-py3-none-any.whl Archive: /var/tmp/portage/dev-python/jsonschema-specifications-2023.11.1/work/jsonschema_specifications-2023.11.1-python3_11/wheel/jsonschema_specifications-2023.11.1-py3-none-any.whl Length Date Time Name --------- ---------- ----- ---- 2800 02-02-2020 00:00 jsonschema_specifications-2023.11.1.dist-info/METADATA 87 02-02-2020 00:00 jsonschema_specifications-2023.11.1.dist-info/WHEEL 1057 02-02-2020 00:00 jsonschema_specifications-2023.11.1.dist-info/licenses/COPYING 391 02-02-2020 00:00 jsonschema_specifications-2023.11.1.dist-info/RECORD --------- ------- 4335 4 files ```
Could you try running `gpep517 build-wheel` with `--allow-compressed`? Is your /var/tmp/portage inside a git repository by any chance? Could you try upgrading hatch-vcs? Rebuilding hatchling, perhaps?
Please also answer my above questions.
>Could you try running `gpep517 build-wheel` with `--allow-compressed`? Nothing changes. >Is your /var/tmp/portage inside a git repository by any chance? I have following in root: ``` # ls -a | rg git _git .gitignore ``` Which I sometimes use with `GIT_DIR="_git" git ...`
(In reply to Sam James from comment #10) > 1. Please share the output of `env`. ``` # env COLORTERM=truecolor DISPLAY=:0 LANG=en_US.utf8 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/lib/llvm/16/bin TERM=alacritty PS1=%B%F{red}%1~ %(!.#.$)%b%f MAIL=/var/mail/root LOGNAME=root USER=root HOME=/root SHELL=/bin/zsh SUDO_COMMAND=/bin/su SUDO_USER=user SUDO_UID=1000 SUDO_GID=1000 SHLVL=1 PWD=/var/tmp/portage/dev-python/jsonschema-specifications-2023.11.1/work/jsonschema_specifications-2023.11.1 OLDPWD=/ GIT_DISCOVERY_ACROSS_FILESYSTEM=1 EDITOR=vim LESS=-iSXFR NUMCPUS=16 NUMCPUSPLUSONE=17 MAKEOPTS=-j17 -l16 EMERGE_DEFAULT_OPTS=--jobs=17 --load-average=16 _=/usr/bin/env ``` > 2. Please try extract a stage3 to e.g. /tmp/ or /opt and chroot in, then > emerge dev-python/jsonschema-specifications. Does it work? If not, try > emulate your existing setup until it breaks. Too cumbersome :) I have a machine which was built from recent (couple of weeks) stage3 and everything is fine there.
Could you try "hiding" (renaming/moving away) /.gitignore?
(In reply to Michał Górny from comment #18) > Could you try "hiding" (renaming/moving away) /.gitignore? Lol, thank you, man! ``` # mv {.,_}gitignore # pushd /var/tmp/portage/dev-python/jsonschema-specifications-2023.11.1/work/jsonschema_specifications-2023.11.1/ /var/tmp/portage/dev-python/jsonschema-specifications-2023.11.1/work/jsonschema_specifications-2023.11.1 / # gpep517 build-wheel --prefix=/usr --backend hatchling.build --output-fd 0 --wheel-dir /var/tmp/portage/dev-python/jsonschema-specifications-2023.11.1/work/jsonschema_specifications-2023.11.1-python3_11/wheel --allow-compressed 2023-11-30 16:55:27,917 gpep517 INFO Building wheel via backend hatchling.build 2023-11-30 16:55:27,996 gpep517 INFO The backend produced /var/tmp/portage/dev-python/jsonschema-specifications-2023.11.1/work/jsonschema_specifications-2023.11.1-python3_11/wheel/jsonschema_specifications-2023.11.1-py3-none-any.whl # unzip -l /var/tmp/portage/dev-python/jsonschema-specifications-2023.11.1/work/jsonschema_specifications-2023.11.1-python3_11/wheel/jsonschema_specifications-2023.11.1-py3-none-any.whl Archive: /var/tmp/portage/dev-python/jsonschema-specifications-2023.11.1/work/jsonschema_specifications-2023.11.1-python3_11/wheel/jsonschema_specifications-2023.11.1-py3-none-any.whl Length Date Time Name --------- ---------- ----- ---- 375 02-02-2020 00:00 jsonschema_specifications/__init__.py 958 02-02-2020 00:00 jsonschema_specifications/_core.py 1785 02-02-2020 00:00 jsonschema_specifications/schemas/draft201909/metaschema.json ```
I've filed an issue for hatch upstream but I can't promise they won't claim it "unsupported". In either case, I think this is not something we ought to "solve".
Sigh... yet again hatchling is broken beyond repair. .gitignore files even for a regular repo are supposed to list the files you *want* to distribute in built installations, but don't want to commit to git. This is totally backwards, but hatchling (by design) won't change.
