Failing autopkgtest for jupyter-notebook
Hi, I decided to fix the jupyter-notebook packages ; on salsa I: - updated to a more recent upstream (but still in the same series to avoid breaking things) ; - unbroke the build by hand ; - unbroke the build in chroot. So far, so good, but I didn't unbreak the autopkg tests. Here is the relevant part of the log: autopkgtest [11:58:56]: test pytest: [--- = test session starts == platform linux -- Python 3.10.6, pytest-7.1.2, pluggy-1.0.0+repack rootdir: /tmp/autopkgtest.GZ5NTc/build.GPO/src collected 330 items / 38 errors / 5 deselected / 325 selected ERRORS _ ERROR collecting debian/python3-notebook/usr/lib/python3/dist- packages/notebook/auth/tests/test_login.py _ import file mismatch: imported module 'notebook.auth.tests.test_login' has this __file__ attribute: /tmp/autopkgtest.GZ5NTc/build.GPO/src/notebook/auth/tests/test_login.py which is not the same as the test file we want to collect: /tmp/autopkgtest.GZ5NTc/build.GPO/src/debian/python3- notebook/usr/lib/python3/dist- packages/notebook/auth/tests/test_login.py HINT: remove __pycache__ / .pyc files and/or use a unique basename for your test file modules _ ERROR collecting debian/python3-notebook/usr/lib/python3/dist- packages/notebook/auth/tests/test_security.py _ import file mismatch: imported module 'notebook.auth.tests.test_security' has this __file__ attribute: /tmp/autopkgtest.GZ5NTc/build.GPO/src/notebook/auth/tests/test_security .py which is not the same as the test file we want to collect: /tmp/autopkgtest.GZ5NTc/build.GPO/src/debian/python3- notebook/usr/lib/python3/dist- packages/notebook/auth/tests/test_security.py HINT: remove __pycache__ / .pyc files and/or use a unique basename for your test file modules I don't know how to do that -- the hints don't help me that much. Cheers, J.Puydt
Re: Failing autopkgtest for jupyter-notebook
Hi, On Aug/11/2022, julien.pu...@gmail.com wrote: > So far, so good, but I didn't unbreak the autopkg tests. Here is the > relevant part of the log: do you have a link to the full log on salsa and the repo? I'd like to verify something... Cheers, -- Carles Pina i Estany https://carles.pina.cat
Re: Fwd: Request to join the Python team
Hi Guilherme (2022.07.07_09:07:19_+) > I sent my request to join the team following the Wiki recommendations > ten days ago and so far I have not received a response. > I would like to know if there are any more steps to be taken? I'm afraid the admins were just busy. I've added you to the team, welcome! SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Request to join debian-python team on salsa
Hi Jérémy (2022.07.07_13:19:01_+) > I'd like to continue to maintain "gyp", > and possibly some other python packages in a near future. > > I am aware of python policy and documentation. Please state that you *agree* with the policy :) SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: joining the python team
Hi Étienne (2022.06.25_18:08:27_+) > I would be happy to join the team to help adding these packages and > maintain them on the long run. Sorry about the long delay, added. Welcome to the team. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Request to join the Debian Python Team
Hi Julien (2022.07.06_16:38:35_+) > I would like to join the Debian Python Team to package some of my > projects, mainly sphinx-lint [1], but maybe also pospell [2], pogrep > [3], and friends created while translating the Python documentation in > french. Sorry about the delay. Welcome to the team! SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Joining the team
Hi Matt (2022.07.17_23:21:03_+) > I am interested in joining the Python team, or at least helping out a > bit if I can. I work a lot with Python, and I'm currently maintaining > a tiny module (python-decouple) and working on a second (python- > public).. my non-Python experience in Debian includes a bunch of perl > in the latest adduser. :) Added, sorry about the delay. Welcome! SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Desire to join
Hi Felix (2022.08.03_19:57:26_+) > With this email, I am expressing my wish to join the team. Added. Welcome to the team! SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Request to join the Debian Python team
Hi Lena (2022.07.18_14:58:11_+) > I would like to join the Python team to help maintain various packages > mostly related to Django. Added. Welcome to the team. And sorry about the delay. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Request to join debian-python team on salsa
Le jeu. 11 août 2022 à 17:55, Stefano Rivera a écrit : > Hi Jérémy (2022.07.07_13:19:01_+) > > I'd like to continue to maintain "gyp", > > and possibly some other python packages in a near future. > > > > I am aware of python policy and documentation. > > Please state that you *agree* with the policy :) > Hi, Yes, of course, I agree with the python policy. Also mind that I don't plan to upload anything new without requesting review.
Re: Failing autopkgtest for jupyter-notebook
Le jeudi 11 août 2022 à 11:34 +0100, Carles Pina i Estany a écrit : > > Hi, > > On Aug/11/2022, julien.pu...@gmail.com wrote: > > > So far, so good, but I didn't unbreak the autopkg tests. Here is > > the > > relevant part of the log: > > do you have a link to the full log on salsa and the repo? > > I'd like to verify something... Well, the repo is salsa. For the full log, it's too big for paste.debian.net ; but from the repo you shouldn't have too hard a time replicating it. Cheers, J.Puydt
Re: Request to join debian-python team on salsa
Hi Jérémy (2022.08.11_17:58:33_+) > Yes, of course, I agree with the python policy. > Also mind that I don't plan to upload anything new without requesting > review. Added, welcome to the team. And sorry that took a while. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
pybuild pyproject.toml problem
Hi,
I have a package
https://salsa.debian.org/debian-astro-team/asdf-standard
that changed its build process to pyproject.toml. As hinted by pybuild,
I added pybuild-plugin-pyproject to the build dependencies; however it
still does not build properly. The build fails with the following
output:
---8<---
* Building wheel...
Successfully built UNKNOWN-1.0.3-py3-none-any.whl
I: pybuild plugin_pyproject:118: Unpacking wheel built for python3.10 with
"installer" module
E: pybuild pybuild:369: build: plugin pyproject failed with: UNKNOWN wheel
found: UNKNOWN-1.0.3-py3-none-any.whl. Does pyproject.toml specify a
build-backend?
dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned exit
code 13
make: *** [debian/rules:5: binary] Error 25
---8<---
which I do not understand. The build backend specified in pyproject.toml is
build-backend = "setuptools.build_meta"
What goes wrong here?
Full build log:
https://salsa.debian.org/debian-astro-team/asdf-standard/-/jobs/3095942
Cheers
Ole
Re: pybuild pyproject.toml problem
On Thu, 11 Aug 2022, Ole Streicher wrote:
Hi,
I have a package
https://salsa.debian.org/debian-astro-team/asdf-standard
that changed its build process to pyproject.toml. As hinted by pybuild,
I added pybuild-plugin-pyproject to the build dependencies; however it
still does not build properly. The build fails with the following
output:
---8<---
* Building wheel...
Successfully built UNKNOWN-1.0.3-py3-none-any.whl
I: pybuild plugin_pyproject:118: Unpacking wheel built for python3.10 with
"installer" module
E: pybuild pybuild:369: build: plugin pyproject failed with: UNKNOWN wheel
found: UNKNOWN-1.0.3-py3-none-any.whl. Does pyproject.toml specify a
build-backend?
dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned exit
code 13
make: *** [debian/rules:5: binary] Error 25
---8<---
which I do not understand. The build backend specified in pyproject.toml is
build-backend = "setuptools.build_meta"
What goes wrong here?
Full build log:
https://salsa.debian.org/debian-astro-team/asdf-standard/-/jobs/3095942
I *think* the issue might be that our setuptools is too old to understand
how to get project metadata from pyproject.toml (PEP 621). This seems to
indicate that it was added in setuptools 61.0.0:
https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html
As a workaround, you might try to patch the metadata back into setup.cfg?
Scott
