Re: python3.10

On Sun, Mar 16, 2025 at 09:58:45AM +0100, Jerome Kieffer wrote: Hi, I am a python software developper and having pyenv as part of debian would be interesting for my job where I switch python version several times a day (and venv several times an hour). For now, I use conda instead but it is slow

Re: pybuild autopkgtest

On Fri, Mar 14, 2025 at 12:08:43PM +0100, PICCA Frederic-Emmanuel wrote: pybuild-autopkgtest(1) has an example of this. sorry for the noise This way it would be possible to deal with the Dependencies on our own and avoid the problem of missing dependencies due to these @builddep@, variables.

Re: pybuild autopkgtest

On Fri, Mar 14, 2025 at 04:20:18PM +0100, PICCA Frederic-Emmanuel wrote: You said "I want to check during the autopkgtest that the runtime dependencies are well defines in the package" and for that you shouldn't have any additional packages installed, but to run tests you normally need additional

Re: pybuild autopkgtest

On Fri, Mar 14, 2025 at 04:27:28PM +0100, PICCA Frederic-Emmanuel wrote: Runtime sure, and we already use that. Do you have a pointer to this logic, /usr/share/dh-python/dhpython/pydist.py but usualy we do not tag with the runtime dependecies in the B-D field. I do. Do we need to hav

Re: pybuild autopkgtest

On Fri, Mar 14, 2025 at 03:24:09PM +0100, PICCA Frederic-Emmanuel wrote: Using @builddep@ is mostly not useful for testing Python packages. does the python tools provide a way to get the runtime dependencies or the test dependencies of a package ? Runtime sure, and we already use that. Test

Re: pybuild autopkgtest

On Fri, Mar 14, 2025 at 01:17:24PM +0100, PICCA Frederic-Emmanuel wrote: But also you should understand that what you want to do is very different from running the test suite, as you explicitly don't want to install deps needed for running it. I want to run the same test suite (which is most of

Re: pybuild autopkgtest

On Fri, Mar 14, 2025 at 12:42:54PM +0100, PICCA Frederic-Emmanuel wrote: This sounds like a job for a custom autopkgtest, not for one that runs build-time tests. In that case what is the purpose of pybuild-autopkgtest ? Making sure the installed code works. But also you should understand that

Re: pybuild autopkgtest

On Fri, Mar 14, 2025 at 11:53:09AM +0100, picca wrote: Is it possible instead of using pybuild-plugin-autopkgtest during the build, to call the same logic from d/t/control. something like Test-Command: pybuild-autopkgtest-run pybuild-autopkgtest(1) has an example of this. This way it would

Re: python3.10

On Mon, Mar 10, 2025 at 07:06:57PM +0100, Christian BAYLE wrote: was wondering why there is no python3.10 in debian Every stable Debian release only contains one Python version, normally the newest one at the time when the release was made. Testing and unstable can contain two versions during

Re: python3.10

On Mon, Mar 10, 2025 at 08:12:25PM +0100, Christian BAYLE wrote: I was surprised that python3.10 compiling from upstream tarball was so easy, but it's maybe i was lucky It being easy is one of the reasons pyenv should be used. -- WBR, wRAR signature.asc Description: PGP signature

Re: elasticsearch8 in Debian

On Mon, Mar 03, 2025 at 10:06:08AM +, Schöke, Karsten wrote: I need help with the following problem: elasticsearch distributes its python lib in pypi with the addition of the main version, e.g. https://pypi.org/project/elasticsearch/ also as https://pypi.org/project/elasticsearch8/ How do

Re: missing pkg_resources dependencies

On Sun, Feb 16, 2025 at 06:35:04PM +0100, Mathias Behrle wrote: > > I'm worried that a lot of undeclared dependencies on > > python3-pkg-resources will creep up in Trixie > > and none of us will notice because we all have python3-setuptools > > installed somehow. > > AFAIS no package should depend

Re: New python3-defaults uploaded making Python 3.13 default

On Fri, Jan 10, 2025 at 02:05:06PM +, Julian Gilbey wrote: > Hi all, > > Just to let you know that Matthias and Stefano upload python3-defaults > 3.13.1 to unstable earlier this week, making Python 3.13 the default. > I just got a FTBFS bug report which turned out to be because the build > use

Re: Package builds on pbuilder but not on the autobuilders

On Thu, Jan 02, 2025 at 03:17:20PM +0100, Elena ``of Valhalla'' Grandi wrote: > Hello > > I'm trying to understand what's happening to fpdf2: > > https://tracker.debian.org/fpdf2 > > Before the upload I've built it with ``gbp buildpackage --git-pbuilder`` > and a freshly updated sid image, and t

Re: Stop recommending PyPi as upstream for Debian Python packages?

On Thu, Jan 02, 2025 at 09:51:45AM +0100, Simon Josefsson wrote: > Context: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091506#27 > > Helmut Grohne writes: > > > Hi Simon, > > > > On Sat, Dec 28, 2024 at 10:33:28AM +0100, Simon Josefsson wrote: > >> Thank you - I agree and hope to convinc

Re: Stop recommending PyPi as upstream for Debian Python packages?

On Thu, Jan 02, 2025 at 10:03:59AM +0100, Dominik George wrote: > >> Everyone has their own kink. I ignore Python modules that are not in > >> Debian and others ignore Python modules not on PyPI. > >> > >> My reasons for ignoring PyPI: > >> [long list of arguments] > > I somehow don't get the poin

Re: Bug#1090126: pyte: FTBFS: ERROR: Invalid value `None` in intersphinx_mapping['http://docs.python.org/']. Expected a two-element tuple or list.

On Mon, Dec 30, 2024 at 09:10:27AM +0100, Florian Ernst wrote: > @debian-python: > > However, AFAIK intersphinx will download things from the internet during > build, which is not allowed by policy. So maybe just ripping out all > intersphinx references from the conf.py would be more suitable. I t

Re: Bug#1091506: ITP: python-unshare -- extension for C unshare() call

On Sat, Dec 28, 2024 at 11:41:19AM +0100, Simon Josefsson wrote: > >> Hi. Asking for some advice here, in python-netfilterqueue there is now: > >> > >> export PYBUILD_TEST_ARGS=--ignore tests/conftest.py > > > > conftest.py is not a file with test cases, it's a "config" file for all > > tests, ig

Re: Bug#1091506: ITP: python-unshare -- extension for C unshare() call

On Sat, Dec 28, 2024 at 03:34:07PM +0500, Andrey Rakhmatullin wrote: > On Sat, Dec 28, 2024 at 11:21:11AM +0100, Simon Josefsson wrote: > > Hi. Asking for some advice here, in python-netfilterqueue there is now: > > > > export PYBUILD_TEST_ARGS=--ignore tests/conftest.py &g

Re: Bug#1091506: ITP: python-unshare -- extension for C unshare() call

On Sat, Dec 28, 2024 at 11:21:11AM +0100, Simon Josefsson wrote: > Hi. Asking for some advice here, in python-netfilterqueue there is now: > > export PYBUILD_TEST_ARGS=--ignore tests/conftest.py conftest.py is not a file with test cases, it's a "config" file for all tests, ignoring it doesn't ma

Re: Bug#1091197: ITP: python-genson -- user-friendly JSON Schema generator

On Thu, Dec 26, 2024 at 12:03:51PM +0100, Simon Josefsson wrote: > Andrey Rakhmatullin writes: > > > Wasn't the proposed fix "export PYBUILD_NAME as the docs say"? I see you > > are not doing this. > > Thanks for reply! I added that but commented o

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: Bug#1091197: ITP: python-genson -- user-friendly JSON Schema generator

Wasn't the proposed fix "export PYBUILD_NAME as the docs say"? I see you are not doing this. -- WBR, wRAR signature.asc Description: PGP signature

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

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's the build-time t

Re: dh_auto_configure: error: unable to load build system class 'python_distutils'

On Tue, Dec 17, 2024 at 11:55:48PM +, Stefano Rivera wrote: > Hi Santiago (2024.12.17_23:46:03_+) > > If you were still relying on python_distutils, you were doing something > horribly wrong. It has never supported Python 3. > > You want to use pybuild instead. > > > Normally this kind o

Re: pypandoc: autopkgtest failure with Python 3.13

On Tue, Dec 10, 2024 at 11:18:01AM +0100, Andreas Tille wrote: > Hi, > > CCing bug #1088768 since the description fits despite the bug itself is > different - not sure whether reopen or new bug is the better option. > > It turns out that in debci there is a remaining test suite issue[1]: > [1] h

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

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 > > ==

Re: Dependency on pkg-resources

On Tue, Dec 03, 2024 at 01:17:17PM +0100, Elena ``of Valhalla'' Grandi wrote: > * python3-setuptools is in Build-Depends, again probably not relevant; > * setuptools is mentioned in setup.py *and* setup.cfg, but in both cases > it is listed as an install_requires, not a requires. > > Anybody has

Re: ERROR Backend subprocess exited when trying to invoke build_wheel

On Sun, Dec 01, 2024 at 07:30:09PM +0100, Jerome BENOIT wrote: > Hi, > > I am trying to package the last version cysignal, I get the error message > > ERROR Backend subprocess exited when trying to invoke build_wheel > E: pybuild pybuild:389: build: plugin pyproject failed with: exit code=1: > p

Re: Bug#1087932: ITP: python-deadlib -- Python dead batteries

On Wed, Nov 20, 2024 at 02:56:11PM +0100, Alexandre Detiste wrote: > Maybe not other completely useless modules. (pipes ?) I think somebody (you?) recently want to vendor pipes to fix something, or maybe it was fixed in a different way instead? -- WBR, wRAR signature.asc Description: PGP signa

Re: LICENSES folder in /usr/share/doc/ ?

On Mon, Nov 18, 2024 at 03:57:49PM +, c.bu...@posteo.jp wrote: > > > To my understand the "copyright" file is something Debian specific. > > > This does not exist in my upstream project but is "generated" by my > > > Debian > > > Package Maintainer. > > > > Correct. Which is what you were aski

Re: f2py problem with Multi-Python (and Ninja)

On Mon, Nov 18, 2024 at 04:07:32PM +0100, Ole Streicher wrote: > >>Build log is f.e. > >>https://salsa.debian.org/debian-astro-team/pybdsf/-/jobs/6612895 > > The problem is most likely caused by "find_package(F2PY)", which does > > not take different Python versions into account [1]. > > This is i

Re: LICENSES folder in /usr/share/doc/ ?

On Mon, Nov 18, 2024 at 01:41:34PM +, c.bu...@posteo.jp wrote: > > > To my understanding of the policy the license file of package should > > > be > > > installed into > > > > > > /usr/share/doc//LICENSE > > > > It's spelled: /usr/share/doc//copyright > > To my understand the "copyright"

Re: pybuild: Build-testing with the package installed

On Thu, Nov 14, 2024 at 01:38:29PM +0100, Matthias Urlichs wrote: > Hi, > > I'm trying to locally build a fixed version of a buggy package which happens > to be installed on the system. > > "debuild -b -us -uc" reports: > > Successfully built moat_lib_codec-0.2.2-py3-none-any.whl > I: pybuild pl

Re: Python 3.13 addition as a supported Python version started

On Wed, Nov 13, 2024 at 11:46:21AM +0100, PICCA Frederic-Emmanuel wrote: > > this is the same as we did for the Python 3.12 transition. Please note > > that we don't enable any of the experimental features in Python 3.12 (no > > GIL, JIT compilation), so assuming there are currently no other RC >

Re: Testsuite: autopkgtest-pkg-pybuild: weird behavior in my uploaded package

On Fri, Nov 08, 2024 at 10:03:18AM +0100, Roland Mas wrote: > You need to list the files required for testing in debian/pybuild.testfiles. > Then both dh_auto_test and autopkgtest-pkg-pybuild do the right thing. This is the thing I didn't want to suggest, because dh_auto_test already works. -- W

Re: Testsuite: autopkgtest-pkg-pybuild: weird behavior in my uploaded package

On Thu, Nov 07, 2024 at 08:34:29PM -0500, Boyuan Yang wrote: > According to pybuild-autopkgtest(1) [1], it seems that Python packages that > uses Testsuite: autopkgtest-pkg-build will "run the tests in the same way as > pybuild ... exception that tests are not run in the build directory". I have >

Re: Unable to set custom test command for pybuild

On Thu, Oct 31, 2024 at 07:08:20PM +0100, John Paul Adrian Glaubitz wrote: > > > (Please CC me as I'm not subscribed to this list) > > > > > > Hello, > > > > > > I need to override the standard test for pybuild and according to the > > > manpage [1] > > > this is achieved by passing "--test-cust

Re: electrum: How to enable autopkgtest?

On Wed, Oct 30, 2024 at 12:28:27AM -0700, Soren Stoutner wrote: > > > If I disable it in debian/rules using the following command the test no > > > longer runs during build. > > > > > > export PYBUILD_TEST_ARGS=-k 'not test_qml_types.py’ > > > > The correct way is --ignore tests/test_qml_types.py

Re: electrum: How to enable autopkgtest?

On Wed, Oct 30, 2024 at 12:06:32AM -0700, Soren Stoutner wrote: > If I disable it in debian/rules using the following command the test no > longer > runs during build. > > export PYBUILD_TEST_ARGS=-k 'not test_qml_types.py’ The correct way is --ignore tests/test_qml_types.py -- WBR, wRAR

Re: electrum: How to enable autopkgtest?

On Tue, Oct 29, 2024 at 11:11:44PM -0700, Soren Stoutner wrote: > > > I added a Build-Depend on "python3-pytest ” and added > > > “Testsuite: > > > autopkgtest-pkg-pybuild” to debian/control. This enables the tests during > > > build time, but I receive the following error during autopkgtest: > >

Re: electrum: How to enable autopkgtest?

On Tue, Oct 29, 2024 at 01:43:50PM -0700, Soren Stoutner wrote: > I added a Build-Depend on "python3-pytest ” and added “Testsuite: > autopkgtest-pkg-pybuild” to debian/control. This enables the tests during > build time, but I receive the following error during autopkgtest: > > E ModuleNotFo

Re: python-trezor: assistance with disabling or modifying a build test that requires network access

On Mon, Sep 30, 2024 at 08:50:27AM -0700, Soren Stoutner wrote: > On Friday, September 27, 2024 4:48:58 PM MST Soren Stoutner wrote: > > 1. Just exclude this test from autopkgtests and go on with my life (I > assume > > autopkgtest-pkg-pybuild has an easy way to do this). There are 111 other > >

Re: pytorch: FTBFS on ppc64el

On Sat, Sep 28, 2024 at 02:30:08AM +0530, Aditi Mishra wrote: > > Source: pytorch > Version: 2.1.2+dfsg-4 > Severity: serious > Tags: ftbfs > > Hello, > > pytorch FTBFS on ppc64el: Open > bughttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071655 > > This regression is still seeing more than

Re: python-trezor: assistance with disabling or modifying a build test that requires network access

On Thu, Sep 26, 2024 at 01:02:14PM -0700, Soren Stoutner wrote: > I am in the process of adopting and updating python-trezor. Upstream now > contains a test that involves downloading a binary firmware package from the > internet [1]. > > This test causes the build to fail with the following err

Re: dh_python for single python scripts?

On Fri, Aug 16, 2024 at 11:02:18PM +0200, Philippe Cerfon wrote: > Hey again > > On Fri, Aug 16, 2024 at 6:26 PM Philippe Cerfon wrote: > > Still I fail to understand, where that auto-completed my-script-file > > comes from in ptpython. > > Any ideas what I'm doing wrong? > > Maybe it's not me d

Re: dh_python for single python scripts?

On Fri, Aug 16, 2024 at 02:52:25AM +0200, Philippe Cerfon wrote: > Hey. > > I'm already using dh_python for (Python) packages where I have a > pyproject.toml with some [project.scripts] section and use > python3-setuptools for building, which works quite nicely. > > > Now I do have some standalo

Re: Debian Python Team Sprint

On Sat, Aug 03, 2024 at 01:49:25AM -0300, Emmanuel Arias wrote: > The other point we need to decide is if we should have an approach of free > bugs fixing, > or if it's better to create a list of goals for the sprint. I prefer the last > idea, as > it will help us keep metrics on the work done du

Re: autopkgtest and conda meta.yaml files

On Fri, Aug 02, 2024 at 01:29:14PM +0200, PICCA Frederic-Emmanuel wrote: > Hello, > > > do you know if it exist a tool which automatically produce autopkgtest test > snipset from a conda meta.yaml file ? > > since plenty of upstream are writing these kind of scripts, it would be > great to ex

Re: Alternative libraries for PEP-594

On Fri, Aug 02, 2024 at 02:11:41PM +0200, Salvo Tomaselli wrote: > > If we end up packaging these libraries, I think it should be clear that > > they won't be available for Forky (Debian 14). The last thing we want is > > to maintain some deprecated zombie-libraries forever in Debian :( > > The al

Re: Policy Change Proposal: Running the upstream test suite

On Tue, Jul 30, 2024 at 10:47:59AM +0200, PICCA Frederic-Emmanuel wrote: > Yes, I want to be sure that all the runtime dependencies are rightfully > declared in the Depends of the python module package. Depending on what do you mean by "all" this is not always what we want. We often don't put all

Re: Policy Change Proposal: Running the upstream test suite

On Tue, Jul 30, 2024 at 03:59:04PM +0100, Julian Gilbey wrote: > > > Maybe we should install only the python binaries and the dependencies > > > marked . > > > > In a typical simple case all B-Ds except sphinx stuff will be > > as you don't need anything beyond the build system to "build" a pur

Re: Policy Change Proposal: Running the upstream test suite

On Wed, Jul 31, 2024 at 09:46:27AM +0100, Simon McVittie wrote: > > > My use case, is to check that all the Dependencies computer by dh_python3 > > > from the build tools are indeed listed in the Depends of the binary > > > package. > > > > Maybe we indeed want a "minimal" autopkgtest environmen

Re: Policy Change Proposal: Running the upstream test suite

On Mon, Jul 29, 2024 at 05:14:33PM +0200, PICCA Frederic-Emmanuel wrote: > > Maybe we indeed want a "minimal" autopkgtest environment, but many > > upstream tests will fail in those and I don't see an automatic way to test > > a random package in this way. > > Even if not minimal, at least corresp

Re: Policy Change Proposal: Running the upstream test suite

On Mon, Jul 29, 2024 at 03:30:39PM +0200, PICCA Frederic-Emmanuel wrote: > My use case, is to check that all the Dependencies computer by dh_python3 > from the build tools are indeed listed in the Depends of the binary package. Maybe we indeed want a "minimal" autopkgtest environment, but many up

Re: mkdocs and tracking

On Sun, Jul 14, 2024 at 02:07:59PM +0200, Salvo Tomaselli wrote: > > dh_mkdocs supports replacing highlight.js from cloudflare with the packaged > > version [1]. Perhaps you can make it replace more libraries the same way. > > I was aware of it but it doesn't really help me if I'm generating html

Re: mkdocs and tracking

On Sun, Jul 14, 2024 at 12:19:43AM +0200, Salvo Tomaselli wrote: > Sorry for the OT, but should we consider patching mkdocs themes to stop > linking to external websites (mostly cloudflare) for static assets? > > This has been used to create security vulnerabilities recently (see for the > polyf

Re: Request for Python Team assistance in Debian Mentors

On Thu, Jun 13, 2024 at 07:28:32AM +0100, Phil Wyett wrote: > Dear Python Team Members, > > At present we have a number of Python related packages[1] within Debian > Mentors[2]. Would it be possible for team members/DD's to offer their expert > assistance to these submitters and their packages wit

Re: Contacting DPT

On Thu, Jun 06, 2024 at 05:40:15PM +0200, Andreas Tille wrote: > I'd like to officially contact all our teams to learn about potential > issues that might affect your work. I would love to learn how you > organise / share your workload. I don't think we do, I think it's all ad-hoc. There are some

Re: python devs complaining about debian packaging

I'll just say that the equal amount of FUD and ranting can be easily generated abotu Debian or even just about Debian Python packaging. -- WBR, wRAR signature.asc Description: PGP signature

Re: zlib missing issue - bookworm

On Fri, May 10, 2024 at 11:59:32AM -0400, mike wrote: > Anyone know how to fix this. I have tried purging and reinstalling python3, > no luck with that. This isn't a good place for asking about locally-built Python installations. > File "/usr/local/lib/python3.7/runpy.py", line 193, in _run_mo

Re: Request to join the Debian Python Team

On Wed, Apr 03, 2024 at 05:21:15PM +0200, Paul Boddie wrote: > I was just looking at the Wiki documentation for this and I think there might > need to be some updates and clarifications. For example, on this page: > > https://wiki.debian.org/Teams/PythonTeam/HowToJoin > > Here, it mentions the M

Re: Request to join the Debian Python Team

On Wed, Apr 03, 2024 at 04:48:44PM +0200, Paul Boddie wrote: > On Wednesday, 3 April 2024 16:25:10 CEST Andrey Rakhmatullin wrote: > > On Wed, Apr 03, 2024 at 04:21:05PM +0200, Paul Boddie wrote: > > > > > > Many thanks for giving me access! Would it make sense to move

Re: Request to join the Debian Python Team

On Wed, Apr 03, 2024 at 04:21:05PM +0200, Paul Boddie wrote: > On Wednesday, 3 April 2024 15:56:48 CEST Pierre-Elliott Bécue wrote: > > > > I've granted you developer access to the package subgroup. You can > > create a shedskin project here if you want. > > Many thanks for giving me access! Woul

Re: Uscan: watch and changelog

On Fri, Mar 29, 2024 at 02:05:41PM +, c.bu...@posteo.jp wrote: > The Wiki page is not up-2-date What's wrong with it? -- WBR, wRAR signature.asc Description: PGP signature

Re: Uscan: watch and changelog

On Fri, Mar 29, 2024 at 07:21:48PM +0500, Andrey Rakhmatullin wrote: > > I assume I have not yet understood the purpose of the changelog in > > context of uscan. What do I miss? > It needs debian/changelog to know the current upstream version of the > package. (also this is answ

Re: Uscan: watch and changelog

On Fri, Mar 29, 2024 at 02:05:41PM +, c.bu...@posteo.jp wrote: > X-Post: > > Hi, > > try to get uscan working with an upstream repo hosted at Codeberg.org > (Forgejo based). > > The Wiki page is not

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

Re: matplotlib

On Wed, Mar 20, 2024 at 10:32:04AM +0900, ciel wrote: > Alexandre-san, > > Sorry, it seems like I cannot contribute this because (at least) I'm > pretty not sure if I can transplant this line properly: > > ``` > ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS))) > echo "backend : TkAgg" > ma

Re: morph's abandoned packages (list)

I'm interested in helping with cryptography and pyopenssl, though I haven't looked at these packages before. -- WBR, wRAR signature.asc Description: PGP signature

Re: Feature Request (docu): Define "dsc-file"

On Fri, Mar 15, 2024 at 07:39:39AM +, c.bu...@posteo.jp wrote: > Hi, > > this is a feature request to someone who has access and the knowledge to > improve. > > Description of the problem: > > The second paragraph in > tell

RFS: dateparser [RC]

Hello! My key in the keyring is temporarily expired so can please someone upload dateparser 1.2.0-2? It's tagged in salsa.

Re: cython 3.x (for Python 3.12)

On Sun, Dec 10, 2023 at 09:30:03PM +0100, Andrey Rakhmatullin wrote: > > I find that there's also a significant issue with relying on > > cython3-legacy: it conflicts with cython3, meaning that it will be > > impossible to simultaneously install packages depending on cython3

Re: cython 3.x (for Python 3.12)

On Sun, Dec 10, 2023 at 08:12:40PM +, Julian Gilbey wrote: > On Sat, Nov 25, 2023 at 04:23:46PM +, Stefano Rivera wrote: > > As part of preparing for Python 3.12 in Debian, I've uploaded cython 3 > > to experimental. > > [...] > > > > So, that's 71 regressions with cython3. dd-list below.

Re: Recommended way of installing system-wide python application and libraries

On Tue, Dec 05, 2023 at 02:10:01AM -0800, Ivan Perez wrote: > Hi everyone! > > I'm currently trying to bring a tool we have at NASA Ames up to speed: > https://github.com/NASA-SW-VnV/ikos > > IKOS is a static analyzer for C. I'm really hoping that IKOS can be > included in Debian in the near futu

Re: Wiki: How to discuss problems and improvements

On Thu, Nov 02, 2023 at 03:02:48AM +, c.bu...@posteo.jp wrote: > to me it is not clear how to discuss problems and improvements of the wiki. > There is no dedicated mailing list to that topic. I don't think it makes sense to bundle discussions of all wiki pages together. Or do you mean problems

Re: Wiki "LibraryStyleGuide": pyproject.toml not mentioned

On Thu, Nov 02, 2023 at 03:10:15AM +, c.bu...@posteo.jp wrote: > Hello, > > related to https://wiki.debian.org/Python/LibraryStyleGuide > > The "pyproject.toml" file is not mentioned here. But it is current > recommended way (and central file) to do python packaging. If it is not > possible t

Re: Do unit tests on Debian Servers/Build system?

On Thu, Nov 02, 2023 at 02:53:48AM +, c.bu...@posteo.jp wrote: > Hello, > > I try to understand some basics about debian packaging Python applications > and the upload and test process. > My question in short: When (at which time point in the process of packaging > python applications for Debi

Re: non-working debian/watch: create new version of package or not

On Wed, Oct 25, 2023 at 12:10:43PM +0100, Carles Pina i Estany wrote: > I recently uploaded (via sponsor) python-ping3. > > The file debian/watch works locally but not in: > https://qa.debian.org/cgi-bin/watch?pkg=python-ping3 > > The reason seems to be that the uscan version in the server is dif

Re: first package questions (salsa repo in personal or team, debian/control maintainers, expected failing unit tests)

On Wed, Oct 04, 2023 at 07:58:11AM +0100, Carles Pina i Estany wrote: > Recap: pytest executed from "pybuild-autopkgtest", in the > python-cloudscraper package, would use the src cloudscrapper instead of > the installed one. > > So, to make sure that pytest uses the installed one, I added in > deb

Re: first package questions (salsa repo in personal or team, debian/control maintainers, expected failing unit tests)

On Tue, Oct 03, 2023 at 11:52:58PM +0100, Carles Pina i Estany wrote: > > upstream tests. Though I think it won't see your explicit `pytest -k` and > > you should replace the override with a PYBUILD_TEST_ARGS var. > > Done this way: > https://salsa.debian.org/python-team/packages/python-cloudscrap

Re: first package questions (salsa repo in personal or team, debian/control maintainers, expected failing unit tests)

On Mon, Oct 02, 2023 at 11:32:31PM +0100, Carles Pina i Estany wrote: > I will create a new version of the package and upload it into > mentors.debian.net when I finish this email. For reference: it will be > the version 1.2.69-3. Note that the usual practice is not bumping Debian versions for pack

Re: Bug#1052028: please update to pydantic 2.x

On Sun, Sep 24, 2023 at 11:25:09AM +0200, Salvo Tomaselli wrote: > Wouldn't it be better to package it as python3-pydantic2 directly? To avoid > breaking every software that uses it. > > In that way they could just coexist and packages depending on the old one > wouldn't all suddenly break. We d

Re: debian/watch: How to watch version tags and what to capture?

On Sun, Sep 17, 2023 at 06:56:58AM +, c.bu...@posteo.jp wrote: > I assume I'm not the first one encountered it. Is there a bug tracker I > can check or report that Issue? The footer of every tracker page says "Report problems to the tracker.debian.org pseudo-package in the Debian BTS."

Re: debian/watch: How to watch version tags and what to capture?

On Sun, Sep 17, 2023 at 11:32:31AM +, c.bu...@posteo.jp wrote: > > i get your point that you want the information fast, but it seems you > > are just using some arbitrary constraint that fits your personal need. > > it appears that for "most" Debian maintainers a lag of "1 or 2 days" > > I'm

Re: Package testing with Salsa CI for new packages

On Fri, Aug 18, 2023 at 07:19:18PM +0200, Paul Boddie wrote: > > > Here, it would seem that the most prudent approach is to use the Salsa CI > > > service instead of trying to get the test suite to run during the package > > > build process. > > > > You should do both if possible, assuming that by

Re: Package testing with Salsa CI for new packages

On Thu, Aug 17, 2023 at 05:10:08PM +0200, Paul Boddie wrote: > Here, it would seem that the most prudent approach is to use the Salsa CI > service instead of trying to get the test suite to run during the package > build process. You should do both if possible, assuming that by "Salsa CI service"

Re: [backintime] Switch the maintainer to "Debian Python Team (DPT)"

On Fri, Jul 28, 2023 at 11:08:38AM +, c.bu...@posteo.jp wrote: > So it is possible to have packages in the debian repo that don't run any > tests? I wasn't expecting this. Many packages don't have tests at all. For many of them tests are not possible or don't make much sense.

Re: How to realize different test categories?

On Fri, Jul 28, 2023 at 12:14:33PM +, c.bu...@posteo.jp wrote: > Hello, > > I'm upstream maintainer (but not founder) of "backintime". > > I realized that most of the tests in my test suite are integration or system > tests which are impossible to handle by Debians build server and testing >

Re: how to properly split up into python3-foo and foo-util package?

On Mon, Jul 17, 2023 at 10:53:58PM +0200, Christoph Anton Mitterer wrote: > > >a) Why does it work to use just usr/... and not > > debian/tmp/usr/... ? > > > Actually, both seems to work, which confuses me even more ^^ > > You can check the search logic in dh_install(1). > > Well I have

Re: how to properly split up into python3-foo and foo-util package?

On Wed, Jul 12, 2023 at 11:56:05AM +, c.bu...@posteo.jp wrote: > > > You build two Debian packages (deb-files) out of one source tarball? > > > Interesting to know that this is possible. > > It's definitely possible and I would expect any good guide to mention > > this. > > I really need to se

Re: how to properly split up into python3-foo and foo-util package?

On Wed, Jul 12, 2023 at 11:16:28AM +0100, Simon McVittie wrote: > On Wed, 12 Jul 2023 at 11:19:07 +0200, Andrey Rakhmatullin wrote: > > I don't think "usr/bin stuff should likely go > > in the other". Many Python module packages ship executables, especially > >

Re: how to properly split up into python3-foo and foo-util package?

On Wed, Jul 12, 2023 at 12:16:51PM +0200, Gregor Riepl wrote: > > > 5) Not really 100% Debian related, but in the Python sdist,... should > > > that contain the debian/*? > > No, and the upstream source shouldn't contain debian/ anyway, as the life > > cycles of packaging and upstream sources s

Re: how to properly split up into python3-foo and foo-util package?

On Wed, Jul 12, 2023 at 11:05:57AM +, c.bu...@posteo.jp wrote: > What do you mean by the terms "simple Python package" and "two packages"? > These terms do not exists in Python context. These are Debian terms. > Python do differentiate between > "Distribution Package" (the name you would find

Re: how to properly split up into python3-foo and foo-util package?

On Wed, Jul 12, 2023 at 02:21:48AM +0200, Christoph Anton Mitterer wrote: > When I run debuild -us -uc on that, it generates: > debian/tmp/... > debian/tmp/usr/bin/ > debian/tmp/usr/lib/python3.11/dist-packages/foo > debian/tmp/usr/lib/python3.11/dist-packages/foo-1.0.0.dist-info > debi

Re: python2:any dependency

On Sun, Jul 02, 2023 at 08:10:15PM +0200, PICCA Frederic-Emmanuel wrote: > I: dh_python3 tools:114: replacing shebang in > debian/pymca/usr/bin/edfviewerD: dh_python3 fs:400: package pymca details = > {'requires.txt': set(), 'egg-info': set(), 'dist-info': set(), 'nsp.txt': > set(), 'shebangs':

Re: Siging up for the Contribution on Python Packaging for Debian

On Thu, May 25, 2023 at 12:19:00PM +, TopologicRose wrote: > Hi, > want to contribute a Python package which called pyvis > (https://pyvis.readthedocs.io/en/latest/index.html) for APT. > A friend of mine works with it and wants it as a Debian package instead of > pip. Start at https://mentors

Re: Unittests writing to HOME (backintime)

On Wed, Mar 29, 2023 at 10:03:31AM +, c.bu...@posteo.jp wrote: > > The usual solution is AFAIK to set a temporary $HOME inside d/rules > > though. > > I was looking into > https://salsa.debian.org/jmw/pkg-backintime/-/blob/debian/debian/rules > > I don't see creation of a HOME or deactivation

  1   2   >