Re: Please cancel NMU of v-sim + help needed for autopkgtest of new upstream version

packaging > style, I think it's extra-important to double-check the result > (debdiff, lintian, looking for warnings in the build log, etc.) to make > sure nothing important was lost in that process. I fully subscribe this and thus I asked for help when I realised that not everything is wo

Re: Please cancel NMU of v-sim + help needed for autopkgtest of new upstream version

Hi, Am Thu, Feb 27, 2025 at 01:31:53PM +0100 schrieb Santiago Vila: > El 27/2/25 a las 12:15, Simon McVittie escribió: > > Please add "Build-Depends: dh-sequence-gir" [...] > I've pushed several commits for 3.8.0-1 and will tag & upload > if they pass CI tests. I'm super happy about Simon's and S

Re: Please cancel NMU of v-sim + help needed for autopkgtest of new upstream version

El 27/2/25 a las 12:15, Simon McVittie escribió: Please add "Build-Depends: dh-sequence-gir" [...] Thanks a lot. I confirm that this makes the autopkgtests to work again. Additionally, there was a wrong declaration which made the build for i386 to fail, but it was easy to fix. I've pushed se

Re: Bug#1075614: Please cancel NMU of v-sim + help needed for autopkgtest of new upstream version

* Alexandre Detiste [250227 12:39]: > I ve my own take on this: I would MBF the (expected few) remaining users of > /usr/share/cdbs/1/class/gnome.mk > and then get rid of this one cdbs module. > > I did similar analysis for the python3-distutils.mk (not sure about the > name) using Debian Code Se

Re: Please cancel NMU of v-sim + help needed for autopkgtest of new upstream version

On Thu, 27 Feb 2025 at 12:38:16 +0100, Alexandre Detiste wrote: > I ve my own take on this: I would MBF the (expected few) remaining users of > /usr/share/cdbs/1/class/gnome.mk > and then get rid of this one cdbs module. In general I'm in favour of conversion of packages from cdbs to dh, but if my

Re: Please cancel NMU of v-sim + help needed for autopkgtest of new upstream version

On Thu, 27 Feb 2025 at 11:02:46 +, Simon McVittie wrote: > On Thu, 27 Feb 2025 at 10:49:04 +0100, Andreas Tille wrote: > > gi.RepositoryError: Typelib file for namespace 'xlib', version '2.0' not > > found > > Is the new upstream version perhaps not generating that dependency? >From the buil

Re: Please cancel NMU of v-sim + help needed for autopkgtest of new upstream version

t would be a good bit of future-proofing to add them. You can ignore the part about if this is a package that is unlikely to be interesting to cross-compile. The typelib should ideally be installed into the multiarch directory, /usr/lib/${DEB_HOST_MULTIARCH}/girepository-1.0, instead of into th

Please cancel NMU of v-sim + help needed for autopkgtest of new upstream version

Hi Sudip, it seems I was to optimistic in fixing v-sim as quickly as expected so I'm not sure whether it will hit the archive before the NMU. To avoid changing the history in Git it would help if you would cancel the NMU. Unfortunately I observed in Salsa CI that the autopkgtest is fail

Help implementing this build speedup Re: Bug#1093869: pybuild setuptools: enable parallel building of extensions via DIST_EXTRA_CONFIG

Hello Debian Python people (especially Stefano Rivera), Where in dh-python should I add this trick to speed up building Python extensions? I would be happy to fix it myself and I think everyone will appreciate the speedups. https://bugs.debian.org/1093869 has the details Doing this technique

Re: Please help to remove python project on python-team/packages

On 2025-01-11 6 h 32 a.m., Bo YU wrote: Hi, Please help remove this invalid project[0] that I accidentally introduced by pressing the enter key when I want to create a new project. Thanks for your time and help. BR, Bo [0]: https://salsa.debian.org/python-team/packages/python Done

Please help to remove python project on python-team/packages

Hi, Please help remove this invalid project[0] that I accidentally introduced by pressing the enter key when I want to create a new project. Thanks for your time and help. BR, Bo [0]: https://salsa.debian.org/python-team/packages/python

Re: [Help] New package python-loky build time test times out

On Thu, Dec 26, 2024 at 08:48:54AM +, c.bu...@posteo.jp wrote: > > https://github.com/search?q=repo%3Acogent3%2Fcogent3%20loky&type=code > > Sending URLs only is quit annoying to all other list members and not an > answer. *shrug* > I know the details and that there are reasons why this pack

Re: [Help] New package python-loky build time test times out

Dear Andrey, Am 25.12.2024 20:56 schrieb Andrey Rakhmatullin: https://github.com/search?q=repo%3Acogent3%2Fcogent3%20loky&type=code Sending URLs only is quit annoying to all other list members and not an answer. I know the details and that there are reasons why this package depend on the o

Re: [Help] New package python-loky build time test times out

s could be a log buffering issue. The build log is not complete - sorry, forgot to add this information. > @Andreas Did you test the build process (as it's done by Salsa) in a local > chroot or build container? I asked for help since it does not finish in my local pbuilder chroot. >

Re: [Help] New package python-loky build time test times out

> > which times out[2]. Any help is welcome. > > Why do you think it's the build-time test? Since this is where I had to kill my local pbuilder. Kind regards Andreas. -- https://fam-tille.de

Re: [Help] New package python-loky build time test times out

the new version of python-cogent needs python-loky[1] which I tried to package. Unfortunately there is some issue with the build-time test which times out[2]. Any help is welcome. Why do you think it's the build-time test? The build output looks quite strange to me. It almost seems li

Re: [Help] New package python-loky build time test times out

On Wed, Dec 25, 2024 at 07:37:51PM +, c.bu...@posteo.jp wrote: > Hello, > > I am a Python developer and upstream maintainer. > I am not much experience when it comes to distro packaging. > This is just an example of a case I often do observe. And I always ask > myself why this happens. > > Am

Re: [Help] New package python-loky build time test times out

Hello, I am a Python developer and upstream maintainer. I am not much experience when it comes to distro packaging. This is just an example of a case I often do observe. And I always ask myself why this happens. Am 25.12.2024 18:47 schrieb Andreas Tille: the new version of python-cogent needs

Re: [Help] New package python-loky build time test times out

On Wed, Dec 25, 2024 at 06:47:01PM +0100, Andreas Tille wrote: > Hi, > > the new version of python-cogent needs python-loky[1] which I tried to > package. Unfortunately there is some issue with the build-time test > which times out[2]. Any help is welcome. Why do you think it&#

[Help] New package python-loky build time test times out

Hi, the new version of python-cogent needs python-loky[1] which I tried to package. Unfortunately there is some issue with the build-time test which times out[2]. Any help is welcome. Kind regards Andreas. [1] https://salsa.debian.org/python-team/packages/python-loky [2] https

Re: python-sigstore / python-tuf: request for packaging help

On Fri, Dec 06, 2024 at 04:50:07PM +0100, Simon Josefsson wrote: > See full log: > > https://salsa.debian.org/jas/python-tuf/-/jobs/6710680/viewer > > Several failures seems related to not being able to find some test file, > any ideas how to fix this further? examples/manual_repo/basic_repo.py?

Re: python-sigstore / python-tuf: request for packaging help

Andrey Rakhmatullin writes: > On Thu, Dec 05, 2024 at 11:39:24PM +0100, Simon Josefsson wrote: >> The self-tests tries seems to open some files which fails and I suspect >> it is because srcdir != builddir reasons, or something similar, see >> errors here: >> >> https://salsa.debian.org/jas/pyth

Bug#1089150: ITP: python-rich-argparse -- Rich help formatters for argparse and optparse

Package: wnpp Severity: wishlist X-Debbugs-Cc: debian-python@lists.debian.org, cru...@debian.org Subject: ITP: python-rich-argparse -- Rich help formatters for argparse and optparse Package: wnpp Owner: Michael R. Crusoe Severity: wishlist * Package name: python-rich-argparse Version

Re: python-sigstore / python-tuf: request for packaging help

On Thu, Dec 05, 2024 at 11:39:24PM +0100, Simon Josefsson wrote: > The self-tests tries seems to open some files which fails and I suspect > it is because srcdir != builddir reasons, or something similar, see > errors here: > > https://salsa.debian.org/jas/python-tuf/-/jobs/6707693 > > ==

python-sigstore / python-tuf: request for packaging help

Hi I am new to python debian packaging, and I'm looking for guidance and review my packaging. I'm happy to team-maintain these packages if someone can add me to the salsa group. Right now I am working on python-sigstore and my packaging is here: https://salsa.debian.org/jas/sigstore-python/ as

Re: Python 3.13 bugs filed - help needed

Hi debian-python (2024.09.20_07:27:25_+) > I've done a fairly large rebuild of Python packages with Python 3.13rc2 > available as a supported version on debusine.debian.net arm64 buliders. > > Results: > Success: 4605 > Failure: 545 > Error: 4 FWIW, those 4 errors are bigger failures, e

Python 3.13 bugs filed - help needed

TL;DR: Please help triage and forward 3.13 bugs. Help upstreams to port to 3.13. Python 3.13 is due to release at the start of October [0]. I think we'd like it to be the Python version in trixie. [0]: https://peps.python.org/pep-0719/ I've done a fairly large rebuild of Python pac

Re: Seeking help with packaging Home Assistant dependencies

Hi Edward, On 2024-07-23 13:25:53, Edward Betts wrote: I am proposing the addition of Home Assistant, a Python-based smart home platform, to Debian. Home Assistant requires extensive hardware integrations and thus has a significant number of Python module dependencies. Upon review, I've identif

Re: Seeking help with packaging Home Assistant dependencies

On 24/07/2024 00:34, Julian Gilbey wrote: > On Tue, Jul 23, 2024 at 04:38:47PM +0200, Salvo Tomaselli wrote: >> Is there no way, especially in the beginig, to patch out funcionality? >> >> Stuff like volvo on call doesn't seem very vital to run the thing. >> >> I'd focus on identifying the real dep

Re: Seeking help with packaging Home Assistant dependencies

On Tue, Jul 23, 2024 at 04:38:47PM +0200, Salvo Tomaselli wrote: > Is there no way, especially in the beginig, to patch out funcionality? > > Stuff like volvo on call doesn't seem very vital to run the thing. > > I'd focus on identifying the real dependencies and prioritize rest later on, > when

Seeking help with packaging Home Assistant dependencies

Hello, I am proposing the addition of Home Assistant, a Python-based smart home platform, to Debian. Home Assistant requires extensive hardware integrations and thus has a significant number of Python module dependencies. Upon review, I've identified 666 Python modules required by Home Assistant

Re: Docu: Need help to understand section about package creation

On 2024-03-29 15:34 weepingclown wrote: > As I understand it, the current > problem we have is more about the wiki being less organized than > there not being sufficient resources or them not being easily > accessible to everyone. Correct. The information is there. But the linkage between them is

Re: Docu: Need help to understand section about package creation

On 2024-03-29 14:48 Carsten Schoenert wrote: > BTW: I posted my way on how I created a new Python package for Debian > in the German Debian forum extensively and in length last year while > DC [1]. Because I also know were starters typically struggle with and > I was in the need to introduce a new

Re: Docu: Need help to understand section about package creation

Hi, As an addendum, there is also dedicated wiki pages[0] intended to be of help to newcomers. Not saying that solves everything mentioned before, but it does help quite a lot. As I understand it, the current problem we have is more about the wiki being less organized than there not being

Re: Docu: Need help to understand section about package creation

errors message was coming up and they did not know what to do and were to look. A good developer or engineer is always able to help themselves. Means he need to know how things work or at least were to look next to solve problems. [1] https://debianforum.de/forum/viewtopic.php?t=187764 -- Regards Carsten

Re: Docu: Need help to understand section about package creation

On Friday, 29 March 2024 09:52:14 CET Carsten Schoenert wrote: > > Starting with Debian packaging isn't a easy thing and there is *not* the > one way to do it right. And there are for sure hundreds of HowTos out > there. You will need to try a few of them and chose in the end the > workflow that f

Re: Docu: Need help to understand section about package creation

On 2024-03-29 09:52 Carsten Schoenert wrote: > New Maintainer Guide: > https://www.debian.org/doc/manuals/maint-guide/ That document itself points to a new rewritten "tutorial" in its first paragraph. I suggest to remove one of them

Re: Docu: Need help to understand section about package creation

Am 29.03.24 um 08:51 schrieb c.bu...@posteo.jp: This document is not Python related. The section about Python is empty. See section 15 at PDF page 65. This isn't really needed yet, packaging Debian packages is technically always the same. You seems to have a general problem to understand what

Re: Docu: Need help to understand section about package creation

Hello everyone, first some general information. As I understand the information from the python-team in the wiki is to inform special handlin here. Newcommers should first read the New Maintainer Guide and the Developer Reference You want a "complete" description about packaging also for new

Re: Docu: Need help to understand section about package creation

Dear Boyuan Yang, Thanks for your feedback. > I can see that > https://wiki.debian.org/Python/GitPackaging#Creating_a_new_package is > indeed poorly written: > > *) It still > [...] I agree to your list of aspects that need to be improved. It seems you really understood the "workflow" of a newb

Re: Docu: Need help to understand section about package creation

On 2024-03-29 07:48 Andreas Tille wrote: > Perhaps a hint to my Live packaging workshop > > https://debconf23.debconf.org/talks/34-live-packaging-workshop/ Also not Python (but Go?) related but I will check it out.

Re: Docu: Need help to understand section about package creation

Dear Metchtilde, Thanks for the reply. On 2024-03-29 08:28 Mechtilde wrote: > If some want to have more information you can read > > https://ddp-team.pages.debian.net/dpb/BuildWithGBP.pdf in German This document is not Python related. The section about Python is empty. See section 15 at PDF pa

Re: Docu: Need help to understand section about package creation

Hi, Am Thu, Mar 28, 2024 at 11:45:36PM -0400 schrieb Boyuan Yang: > > I don't have a good solution to Wiki pages yet since the article logic > needs some major editing. I can't provide any help for the Wiki page for DPMT. In Debian Med we provide some resources for newcome

Re: Re: Docu: Need help to understand section about package creation

Hi, (I am off debian-python mailing list -- please CC me. Also, I cannot include previous text in the threads because I don't have them in my mailbox. Sorry!) Reading https://lists.debian.org/debian-python/2024/03/msg00152.html and https://lists.debian.org/debian-python/2024/03/msg00151.html , I

Re: Docu: Need help to understand section about package creation

install pypi2deb` will give the py2dsp command and `py2dsp ` can give you a nifty initial template to start with. For more info you can try `py2dsp --help`. What I typically use when creating a new package is `py2dsp --profile dpt --distribution unstable --revision 1 --github `. No other

Re: Docu: Need help to understand section about package creation

g a new package" don't help me to fill it up. Thanks in advance, Christian Buhtz On 2024-03-20 22:32 wrote: > Hello, > > in order to improve the documentation I need to understand some parts. > But I am stuck. I don't get it what the authors trying to explain. > &

Re: Docu: Need help to understand section about package creation

On 2024-03-20 22:55 c.bu...@posteo.jp wrote: > Am 20.03.2024 22:43 schrieb Andrey Rakhmatullin: > > One should use git-buildpackage which > > is described on https://wiki.debian.org/PackagingWithGit. > > What is the difference to https://wiki.debian.org/Python/GitPackaging > ? I think this is a v

Re: Docu: Need help to understand section about package creation

Thanks for the reply. Am 20.03.2024 22:43 schrieb Andrey Rakhmatullin: As I said before, we no longer use git-dpm and git-dpm-specific documentation is no longer relevant. OK, then someone should remove it from the DPT packaging wiki page. One should use git-buildpackage which is described o

Re: Docu: Need help to understand section about package creation

On Wed, Mar 20, 2024 at 09:32:34PM +, c.bu...@posteo.jp wrote: > Hello, > > in order to improve the documentation I need to understand some parts. > But I am stuck. I don't get it what the authors trying to explain. > > It is about "Creating a new package" section: > https://wiki.debian.org/P

Docu: Need help to understand section about package creation

Hello, in order to improve the documentation I need to understand some parts. But I am stuck. I don't get it what the authors trying to explain. It is about "Creating a new package" section: https://wiki.debian.org/Python/GitPackaging#Creating_a_new_package The second paragraph points to dsc-fil

Re: Help with the Cython 3.0 failures in Ceph

On 3/3/24 21:08, Thomas Goirand wrote: Hi, I'm long overdue for an upload of Ceph 18.2.x in Unstable. I'm currently stuck with the below build failure: Error compiling Cython file: ...     """     name = cstr(name, 'name')

Help with the Cython 3.0 failures in Ceph

Hi, I'm long overdue for an upload of Ceph 18.2.x in Unstable. I'm currently stuck with the below build failure: Error compiling Cython file: ... """ name = cstr(name, 'name') cdef: rados_ioctx_t _

Re: Bug#1061765: Help needed to fix python-coverage-test-runner

Andreas Tille dijo [Fri, Feb 23, 2024 at 03:22:27PM +0100]: > HI Andrius, > > Am Fri, Feb 23, 2024 at 09:29:27AM +0200 schrieb Andrius Merkys: > > > ModuleNotFoundError: No module named 'imp' > > > > I had a similar problem. I worked it around by depending on > > python3-zombie-imp, the original

Re: Help needed to fix python-coverage-test-runner

HI Andrius, Am Fri, Feb 23, 2024 at 09:29:27AM +0200 schrieb Andrius Merkys: > > ModuleNotFoundError: No module named 'imp' > > I had a similar problem. I worked it around by depending on > python3-zombie-imp, the original code did not require any modifications. Nice hint - implemented. Thanks

Re: Help needed to fix python-coverage-test-runner

Hi Andreas, On 2024-02-23 09:15, Andreas Tille wrote: I've attempted to fix python-coverage-test-runner in Git since this package is finally responsible for the failure of vmdb2: File "/usr/lib/python3/dist-packages/CoverageTestRunner.py", line 22, in import imp ModuleNotFoundError: No

Help needed to fix python-coverage-test-runner

Control: tags -1 help Hi, I've attempted to fix python-coverage-test-runner in Git since this package is finally responsible for the failure of vmdb2: File "/usr/lib/python3/dist-packages/CoverageTestRunner.py", line 22, in import imp ModuleNotFoundError: No module name

Re: Help with a Python module package

Hi, [...] maybe you can help with an issue I can't fix. I am trying to package Awkward Array [1] and a preliminary repository can be found at [2]. Just to let you know that I managed to get it to work (using dh_python --no-ext-rename). Uploaded. Cheers Sascha OpenPGP_signatur

Help with a Python module package

Dear Python team, maybe you can help with an issue I can't fix. I am trying to package Awkward Array [1] and a preliminary repository can be found at [2]. What is special about this package is that two modules are required -- one with C++ native libraries, and a native Python one (s

Help needed to port qiime to Python3.12

with the qiime code but with no success at all. Any help would be welcome. Kind regards Andreas. [1] https://github.com/qiime2/qiime2/issues/751 [2] https://salsa.debian.org/med-team/q2-types/-/jobs/5313640#L900 -- http://fam-tille.de

Re: Spinx help needed

Hi Dmitry, thanks a lot and sorry for my naivity Andreas. Am Thu, Feb 15, 2024 at 09:54:55PM +0300 schrieb Dmitry Shachnev: > On Thu, Feb 15, 2024 at 07:15:18PM +0100, Andreas Tille wrote: > > Hi Dmitry, > > > > thanks a lot for this hint. > > > > I've created a quilt patch which replaces the

Re: Spinx help needed

On Thu, Feb 15, 2024 at 07:15:18PM +0100, Andreas Tille wrote: > Hi Dmitry, > > thanks a lot for this hint. > > I've created a quilt patch which replaces the vendored theme by the > sphinx13 one which is currently shipped in Debian. The patches by > upstream seem to be void now - at least none app

Re: Spinx help needed

Hi Dmitry, thanks a lot for this hint. Am Thu, Feb 15, 2024 at 11:46:45AM +0300 schrieb Dmitry Shachnev: > lmfit-py ships a vendored copy of sphinx13 theme [1], which was copied from > Sphinx source code with a minor modification in 2020 [2] and rebased in > January 2022 [3]. However, there were

Re: Spinx help needed

Hi Andreas! On Thu, Feb 15, 2024 at 08:37:38AM +0100, Andreas Tille wrote: > Control: tags -1 pending > > Hi, > > I pushed fixes for #1056419 and #1058311 to Git and I think should be > fixed as well. The only remaining build problem is new and caused by > sphinx[1]: > > dh_sphinxdoc -i -O--

Re: Spinx help needed

It is always hard to follow such threads. It is unclear if this message is about the Sphinx package itself or a package that do use Sphinx in its build process. There are two bug numbers in the CC fields. But the mail miss links to the bug reports or other information giving more context. Thi

Spinx help needed

Control: tags -1 pending Hi, I pushed fixes for #1056419 and #1058311 to Git and I think should be fixed as well. The only remaining build problem is new and caused by sphinx[1]: dh_sphinxdoc -i -O--buildsystem=pybuild dh_sphinxdoc: error: debian/python-lmfit-doc/usr/share/doc/python3-lmfit/

Re: [Help] Re: mlpy ftbfs with Python 3.12

Hi, I created a patch for ModuleNotFoundError with Python 3.12. I worked on it in a fork, and created MR [0]. I hope it fixes the issue with the build. [0] https://salsa.debian.org/science-team/mlpy/-/merge_requests/5 Cheers! Yogeswaran. signature.asc Description: PGP signature

[Help] Re: mlpy ftbfs with Python 3.12

Control: tags 1056819 pending Control: tags -1 help Hi, after applying the patch for the cython3 issue the build issues of this package are remaining. This is strange since the missing modules are provided inside the package. I wonder what trick I might need to do to convince the Python3

Re: [Help] Re: python-pkginfo: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

Hi Stefano, Am Thu, Jan 11, 2024 at 08:25:46PM + schrieb Stefano Rivera: > > The test is expecting the module to be installed in the test > environment. Either we could try harder to emulate that, or skip the > tests. I admit I tried to copy around the module before running the test with no

Re: [Help] Re: python-pkginfo: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

Hi Andreas (2024.01.11_17:48:43_+) > I've fixed the two other bugs in python-pkginfo and upgraded to latest > upstream. Unfortunately I have no clue about this issue. The test is expecting the module to be installed in the test environment. Either we could try harder to emulate that, or skip

[Help] Re: python-pkginfo: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

Control: tags -1 help Hi, I've fixed the two other bugs in python-pkginfo and upgraded to latest upstream. Unfortunately I have no clue about this issue. Any idea what might be wrong here? Kind regards Andreas. -- http://fam-tille.de

[Help] Re: python-srsly: ftbfs with cython 3.0.x

Control: tags -1 help Hi, when applying the patch (thanks for this, Bas) I learned that the package builds for other reasons. This is also true for the latest upstream version[1]. Any help to fix this would be welcome Andreas. [1] https://salsa.debian.org/python-team/packages/python-srsly

[Help] Re: python-stack-data: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

Control: tags -1 help Hi, I tried the suggested patch for the cython3 issue of bug #1056872 in the currently packaged version[1] as well also tried upgrading to latest upstream and tried building[2] which failed as well. I admit, I'm running out of ideas what to do next. Any help is we

Re: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

past modules to help 2-3 or 3-2 compatibility, and scripts to convert code: these would take more effort to remove than __future__ imports, and should probably be patched upstream (by removing support for Python 2 and older Python 3 versions) Cheers

Re: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

On 1/4/24 00:30, Alexandre Detiste wrote: Le lun. 11 déc. 2023 à 16:43, Andreas Tille a écrit : Control: tags -1 help [Bug #1056419 in CC since the issue seems to be caused by python-future] Hi Vincent, I tried to upgrade python-future to the latest upstream version in the hope that this

Re: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

on-modules/blob/master/policy.rst#id2 > > | Team in Uploaders is a weak statement of collaboration. Help in > maintaining the package is appreciated, > | commits to the Git repository are freely welcomed, but before > uploading, please contact the Maintainer for the green light. > &

Re: [Debian-pan-maintainers] [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

ask me the package is team maintained and a "Team upload" >> should be fine. > > Hi, I just try to follow the rules I agreed on last month. > > https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#id2 > >| Team in Uploaders is a weak

Re: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

the rules I agreed on last month. https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#id2 | Team in Uploaders is a weak statement of collaboration. Help in maintaining the package is appreciated, | commits to the Git repository are freely welcomed, but before uploadi

Re: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

Hi Alexandre, Am Thu, Jan 04, 2024 at 12:30:21AM +0100 schrieb Alexandre Detiste: > > There might be some nmu needed too if maintainers don't react. > > @Vincent: this one package "gtextfsm" is yours > do you green light an upload ? If you ask me the package is team maintained and a "Team uploa

Re: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

On 2024-01-04 00:30, Alexandre Detiste wrote: @Vincent: this one package "gtextfsm" is yours do you green light an upload ? Yes.

Re: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

Le lun. 11 déc. 2023 à 16:43, Andreas Tille a écrit : > Control: tags -1 help > > [Bug #1056419 in CC since the issue seems to be caused by python-future] > > Hi Vincent, > > I tried to upgrade python-future to the latest upstream version in the > hope that this would sol

Re: Bug#1056419: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

Hi Alexandre, Am Mon, Dec 11, 2023 at 09:18:16PM +0100 schrieb Alexandre Detiste: > > https://github.com/lebigot/uncertainties/releases/tag/3.1.7 > > +1 OK. > > Also we should probably get rid of python-future at some point. > > I removed it from three games this week-end > and filled 6 more

Re: Bug#1056419: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

Le lun. 11 déc. 2023 à 17:02, Jochen Sprickerhof a écrit : > I think the right thing here is to package the new uncertainties version > which drops the past import: > > https://github.com/lebigot/uncertainties/releases/tag/3.1.7 +1 > Also we should probably get rid of python-future at some point

Re: Bug#1056419: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

Hi Andreas, * Andreas Tille [2023-12-11 16:42]: Control: tags -1 help [Bug #1056419 in CC since the issue seems to be caused by python-future] Hi Vincent, I tried to upgrade python-future to the latest upstream version in the hope that this would solve the issue reported in bug #1042244

[Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

Control: tags -1 help [Bug #1056419 in CC since the issue seems to be caused by python-future] Hi Vincent, I tried to upgrade python-future to the latest upstream version in the hope that this would solve the issue reported in bug #1042244. Unfortunately this is not the case and now with

Re: help to fix ftbfs issue #1052815 for python-sparse

On Sun, Oct 29, 2023 at 1:25 AM Bo YU wrote: > > Hi, > > I am looking at the issue and trying to fix it. > > If upgrading to 0.14.0[0] directly does not fix the issue and it is in > complicated situation. So below I will explain what I do. > > First to fix #1052815[1], wo need to adjust pybuild wi

help to fix ftbfs issue #1052815 for python-sparse

Hi, I am looking at the issue and trying to fix it. If upgrading to 0.14.0[0] directly does not fix the issue and it is in complicated situation. So below I will explain what I do. First to fix #1052815[1], wo need to adjust pybuild with custom way: ``` PYBUILD_SYSTEM=custom \ PYBUILD_TEST_ARGS=

Re: Python module packaging request to help me maintain apt-listchanges

Hi Jonathan, * Jonathan Kamens [2023-10-23 06:00]: I'm writing to ask for your assistance in getting pytest-subprocess packaged into Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053360 As one of the uploaders for pytest, I am happy to sponsor you! Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭─

Re: Python module packaging request to help me maintain apt-listchanges

Pytest-subprocess looks interesting, I'd probably myself have done the mocks directly using pytest-mock but it's good to know this exists. On Mon, 23 Oct 2023, 12:49 Jonathan Kamens, wrote: > Hello all, > > I'm writing to ask for your assistance in getting pytest-subprocess > packaged into Debia

Python module packaging request to help me maintain apt-listchanges

Hello all, I'm writing to ask for your assistance in getting pytest-subprocess packaged into Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053360 The use case here is that I've taken over maintenance of apt-listchanges and added among other things a unit-test suite, and I want t

Re: Help with numpydoc needed (Was: Bug#1029245: nitime: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13)

Am Fri, Jan 20, 2023 at 04:24:07PM -0500 schrieb Éric Araujo: > Le 20/01/2023 à 16:21, FC Stegerman a écrit : > > Should that not use "func" instead of "inspect.getframeinfo"? > > Yes of course! I tested in a terminal to give valid code and forgot to > replace my example function with the origina

Re: Help with numpydoc needed (Was: Bug#1029245: nitime: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13)

Le 20/01/2023 à 16:21, FC Stegerman a écrit : Should that not use "func" instead of "inspect.getframeinfo"? Yes of course! I tested in a terminal to give valid code and forgot to replace my example function with the original variable name. Thanks!

Re: Help with numpydoc needed (Was: Bug#1029245: nitime: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13)

* Éric Araujo [2023-01-20 22:01]: > tl;dr: replace the body of the try block with this: > > argspec = inspect.signature(inspect.getframeinfo) > argspec = str(argspec).replace('*', '\\*') > signature = '%s%s' % (func_name, argspec) Should that not use "func" instead of "inspect.getfra

Re: Help with numpydoc needed (Was: Bug#1029245: nitime: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13)

Hello, Le 20/01/2023 à 15:33, Andreas Tille a écrit : I finally do not have an idea how to replace: Handler for event 'autodoc-process-docstring' threw an exception (exception: 'FullArgSpec' object has no attribute 'replace') which you can find in the latest build log in Salsa CI. t

Help with numpydoc needed (Was: Bug#1029245: nitime: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13)

Control: tags -1 help Hi, I think I have fixed the numpy 1.24 issues that were causing this build failure. Unfortunately there are also numpydoc issues and I did not found documentation about this when doing a web search. I failed finding something for inspect.formatargspec which I simply

Re: Help for python-pynndescent needed

x -- Python 3.10.9, pytest-7.2.1, pluggy-1.0.0+repack -- > /usr/bin/python3.10 > > and the upstream is running those tests with max 3.9 : > > platform linux -- Python 3.9.16, pytest-7.2.0, pluggy-1.0.0 -- > /opt/hostedtoolcache/Python/3.9.16/x64/bin/python Lowering the Python3 version

Re: Help for python-pynndescent needed

nndescent fails[1]? > > Any help would be welcome. > > Kind regards >Andreas. > > > [1] > https://salsa.debian.org/python-team/packages/python-pynndescent/-/jobs/3811021 > > -- > http://fam-tille.de > > -- Malik Mlitat

Help for python-pynndescent needed

Hi, any idea why the build-time test of python-pynndescent fails[1]? Any help would be welcome. Kind regards Andreas. [1] https://salsa.debian.org/python-team/packages/python-pynndescent/-/jobs/3811021 -- http://fam-tille.de

RE: Help to package xdoctest

The first time I had cases with binary multiples, I was a bit lost. But later, with the help of the staff, I managed to pack, I don't know if this is the same case as yours, but if so, you can follow this example here: https://salsa.debian.org/debian/sphinx-multiversion [

Re: Help to package xdoctest

Hi Bo (2022.12.26_07:01:29_+) > W: python3-xdoctest: no-manual-page [usr/bin/xdoctest] Yeah, applications *should* have manual pages, but it's not required. If you need more tooling to build the manpage, it can wait until those tools are available in Debian. > P: xdoctest source: very-long-li

Re: Help to package xdoctest

problem with the dependency[0] to use sphinx to generate html, especially since it needs ubelt, the xdoctest package itself to meet its dependencies. So what is the better way to solve the issue? BR, Bo [0]: https://salsa.debian.org/python-team/packages/xdoctest/-/blob/debian/main/docs/requiremen

  1   2   3   4   5   6   7   8   >