Re: wheel and pip with setuptools
Le 2022-10-30 00:39, Scott Kitterman a écrit :
Adding pybuild-plugin-pyproject to build-depends should solve it. It
looks like it is trying to do the new pyproject.toml style build
without all the necessary parts in place.
the package contain a pyproject.toml file and a setup.py one.
the build system in the pyproject file is setuptools.
[build-system]
requires = ["setuptools", "wheel", "numpy"]
build-backend = "setuptools.build_meta"
So I imagine that under the hood it use the setup.py file.
now it fails with this error message
adding 'xrayutilities-1.7.3.dist-info/top_level.txt'
adding 'xrayutilities-1.7.3.dist-info/RECORD'
removing build/bdist.linux-x86_64/wheel
* Building wheel...
Successfully built xrayutilities-1.7.3-cp310-cp310-linux_x86_64.whl
I: pybuild plugin_pyproject:118: Unpacking wheel built for python3.10
with "installer" module
E: pybuild pybuild:379: build: plugin pyproject failed with: File
already exists:
/<>/.pybuild/cpython3_3.10_xrayutilities/build/xrayutilities/VERSION
dh_auto_build: error: pybuild --build -i python{version} -p 3.10
returned exit code 13
make[1]: *** [debian/rules:20: override_dh_auto_build-arch] Error 25
this failure seems to come from the indep part
%:
dh $@ --buildsystem=pybuild
execute_after_dh_auto_clean:
rm -rf build
override_dh_auto_build-arch:
dh_auto_build
override_dh_auto_build-indep: override_dh_auto_build-arch
ifeq (,$(findstring nodoc, $(DEB_BUILD_OPTIONS)))
dh_auto_build -- -s custom --build-args="env
PYTHONPATH={build_dir} {interpreter} setup.py build_doc"
endif
since I make the indep part depends on the arch one, it build the
package a second time. and this is during this second reconstruction
that
it failes.
it seems that the arch rules does not gard from a second build, and it
is not indepotent...
Fred
Re: wheel and pip with setuptools
On October 29, 2022 10:07:13 PM UTC, picca wrote:
>Hello, I try to fix an FTBFS in the python-xrayutilities package.
>When I try to build it, I get this error message., I do not understand why I
>need to add a build dependency to python3-wheel.Is it something missing in the
>dependency of python3-setuptools or python3.10 ?
>
>thanks for your help
>
>Frederic
>
>
>
>dh clean --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
>install -d /<>/debian/.debhelper/generated/_source/home
>pybuild --clean -i python{version} -p 3.10
>I: pybuild base:240: python3.10 setup.py clean
>/usr/lib/python3/dist-packages/setuptools/installer.py:27:
>SetuptoolsDeprecationWarning: setuptools.installer is deprecated. Requirements
>should be satisfied by a PEP 517 installer.
>warnings.warn(
>WARNING: The wheel package is not available.
>/usr/bin/python3.10: No module named pip
>Traceback (most recent call last):
>File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 82, in
>fetch_build_egg
>subprocess.check_call(cmd)
>File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
>raise CalledProcessError(retcode, cmd)
>subprocess.CalledProcessError: Command '['/usr/bin/python3.10', '-m', 'pip',
>'--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpq9o0m_9e',
>'--quiet', 'h5py']' returned non-zero exit status 1.The above exception was
>the direct cause of the following exception:
>
Adding pybuild-plugin-pyproject to build-depends should solve it. It looks
like it is trying to do the new pyproject.toml style build without all the
necessary parts in place.
Scott K
wheel and pip with setuptools
Hello, I try to fix an FTBFS in the python-xrayutilities package.
When I try to build it, I get this error message., I do not understand
why I need to add a build dependency to python3-wheel.Is it something
missing in the dependency of python3-setuptools or python3.10 ?
thanks for your help
Frederic
dh clean --buildsystem=pybuild
dh_auto_clean -O--buildsystem=pybuild
install -d /<>/debian/.debhelper/generated/_source/home
pybuild --clean -i python{version} -p 3.10
I: pybuild base:240: python3.10 setup.py clean
/usr/lib/python3/dist-packages/setuptools/installer.py:27:
SetuptoolsDeprecationWarning: setuptools.installer is deprecated.
Requirements should be satisfied by a PEP 517 installer.
warnings.warn(
WARNING: The wheel package is not available.
/usr/bin/python3.10: No module named pip
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 82,
in fetch_build_egg
subprocess.check_call(cmd)
File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python3.10', '-m',
'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w',
'/tmp/tmpq9o0m_9e', '--quiet', 'h5py']' returned non-zero exit status
1.The above exception was the direct cause of the following exception:
Bug#1023014: ITP: securestring -- Clearing the contents of strings containing cryptographic material
Package: wnpp Severity: wishlist Owner: Joost van Baal-Ilić * Package name: securestring Version : 0.2 Upstream Author : András Veres-Szentkirályi, Lawrence Fan * URL : https://pypi.org/project/SecureString/, https://github.com/aznashwan/py-securestring * License : MIT Programming Lang: Python Description : Clearing the contents of strings containing cryptographic material Python wrapper around OPENSSL_cleanse() which fills a pointer with a string of 0's, typically used to clear the contents of strings containing cryptographic material. I am maintaining this package as part of the Python team, I am working in https://salsa.debian.org/python-team/packages/securestring . I plan to package "pwdsphinx" too ( https://salsa.debian.org/debian/pwdsphinx , https://github.com/stef/pwdsphinx , ITP will follow); pwdsphinx will depend upon python3-securestring. See also Bug#1022862: ITP: libsphinx and Bug#1021433: ITP: libequihash. The SPHINX project was funded through the NGI0 PET Fund, a fund established by NLnet with financial support from the European Commission's Next Generation Internet programme, under the aegis of DG Communications Networks, Content and Technology under grant agreement No 825310. Bye, Joost
Re: review for pipenv/2022.10.12-1
On Fri, 28 Oct 2022 16:46:51 +0300 Ileana Dumitrescu wrote: > > I did just notice the upstream release contains several other > > files worth considering for removal: a bunch of windows > > executables [1]. > > I agree and can remove those from the source tarball too. To do that > with the current upstream version in salsa though requires me to git > reset, re-import the 2022.10.25+ds upstream with updated > Files-Excluded, then add back the other commits. I have done that > locally but this requires a force push which is not allowed for the > debian branch since it is protected. You can avoid resetting or forcing anything by increasing the repacksuffix. As far as both git and the tooling are concerned, that makes it an all new upstream version without conflicts with the repo's current content, so pushing to git works just fine. First update the excluded files in d/copyright and commit that change, then run with the usual 'gbp import-orig --pristine-tar --uscan'. When gbp asks you for the upstream version, modify the +ds part to +ds2 and proceed with that. pgp2cYyiFNEPC.pgp Description: OpenPGP digital signature
