> > I dont think it's a problem per se, but i also want to understand if
> > the time debian-python@ dedicates to solve your issues is well spent.
>
> I'd say it is well spent.
>
> Andreas is herding a lot of cattle for Debian (as in
> packages, or people, or mentees). He's inventor of Debian
>
Hi,
I'd like to use the chance to express that I'm really thankful for every
helpful response I received here on this list. My work in Debian
touches a lot of techniques and I can't gather expertise in every single
one. It also happens that web searches I'm doing are not always as
successful as
Am Thu, Mar 17, 2022 at 01:00:40PM -0400 schrieb Sandro Tosi:
> since it's not the first time you write to this list with a traceback
> or error, asking for help, and the answer from here is generally
> pretty straight-forward, i'm wondering why you were not able to find
> the solution directly?
Andreas,
> > Any hint would be welcome
>
> See: https://github.com/explosion/catalogue/issues/27
>
> TLDR: skip that test on Python 3.10 for now.
this seemed an easy enough issue that, with some common and expected
due diligence, you could have figured it out yourself: checking
upstream issue
On Thu, 17 Mar 2022, Andreas Tille wrote:
Hi,
I intend to package python-catalogue[1] but there is a test suite
issue (see salsa-ci for complete log[2]):
platform linux -- Python 3.10.3, pytest-6.2.5, py-1.10.0, pluggy-1.0.0
rootdir:
Hi,
I intend to package python-catalogue[1] but there is a test suite
issue (see salsa-ci for complete log[2]):
platform linux -- Python 3.10.3, pytest-6.2.5, py-1.10.0, pluggy-1.0.0
rootdir: /builds/python-team/packages/python-catalogue/debian/output/source_dir
collected 8 items
6 matches
Mail list logo
