Bug#1044060: q2-quality-control: test failure with pandas 2.0

2024-02-19 Thread s3v
Hi,

According to [1]:

    Empty DataFrames/Series will now default to have a ``RangeIndex``
    ^

    Before, constructing an empty (where ``data`` is ``None`` or an empty 
list-like argument) :class:`Series` or :class:`DataFrame` without
    specifying the axes (``index=None``, ``columns=None``) would return the 
axes as empty :class:`Index` with object dtype.

    Now, the axes return an empty :class:`RangeIndex` (:issue:`49572`).

    *Previous behavior*:

    .. code-block:: ipython

    In [8]: pd.Series().index
    Out[8]:
    Index([], dtype='object')

    In [9] pd.DataFrame().axes
    Out[9]:
    [Index([], dtype='object'), Index([], dtype='object')]

    *New behavior*:

    .. ipython:: python

    pd.Series().index
    pd.DataFrame().axes

empty dataframes are not equals anymore with pandas > 2.0 in this case:

test.py
---

import pandas as pd
from pandas.testing import assert_frame_equal

df1 = pd.DataFrame(columns=['s1', 's2', 's3']).astype(float)  
df2 = pd.DataFrame(columns=['s1', 's2', 's3'], index=[]).astype(float)  

try:
   assert_frame_equal(df1, df2)
except AssertionError:
   raise

print('OK')


Output with pandas 2.1
--
> python3.11 test.py  
Traceback (most recent call last):
 File "/build/test.py", line 8, in 
   assert_frame_equal(df1,df2)
 File "/usr/lib/python3/dist-packages/pandas/_testing/asserters.py", line 1156, 
in assert_frame_equal
   assert_index_equal(
 File "/usr/lib/python3/dist-packages/pandas/_testing/asserters.py", line 260, 
in assert_index_equal
   _check_types(left, right, obj=obj)
 File "/usr/lib/python3/dist-packages/pandas/_testing/asserters.py", line 236, 
in _check_types
   assert_attr_equal("inferred_type", left, right, obj=obj)
 File "/usr/lib/python3/dist-packages/pandas/_testing/asserters.py", line 414, 
in assert_attr_equal
   raise_assert_detail(obj, msg, left_attr, right_attr)
 File "/usr/lib/python3/dist-packages/pandas/_testing/asserters.py", line 598, 
in raise_assert_detail
   raise AssertionError(msg)
AssertionError: DataFrame.index are different

Attribute "inferred_type" are different
[left]:  integer
[right]: empty


Output with pandas 1.5
--
> python3.11 test.py
OK

Please note the attached patch makes autopkgtestpass as well with
pandas 1.5.2.


On Sun, 18 Feb 2024 14:45:29 +0100 Andreas Tille  wrote:
> Hi again,
>
> Am Sun, Feb 18, 2024 at 12:25:49PM +0100 schrieb Andreas Tille:
> > I just realised that a new qiime version is out. I will upgrade
> > to latest upstream and see how this might affect this issue
>
> The new qiime upstream version does not change anything. After I
> switched q2-* packages to run autopkgtest for `py3versions -s` I
> realised the problem below exist in several of the q2-* packages so its
> rather no Pandas issue but a Python3.12 problem which in parallel to the
> Pandas migration showed up.
>
> If you might have any hint how to deal with these (no matter for the
> old or the new qiime package since I assume the patch will apply
> to both, it would be really appreciated.
>
> Kind regards
> Andreas.
>
> > Am Sun, Feb 18, 2024 at 12:11:04PM +0100 schrieb Andreas Tille:
> > > Control: tags -1 help
> > >
> > > Hi again,
> > >
> > > I hope to approach the last remaining Pandas issue for the qiime
> > > ecosystem. As it has become obvious in the q2-types package I'm now
> > > facing pretty similar errors when running the q2-quality-control
> > > package which can be seen in full length in Salsa-CI[3] and contains
> > > errors like:
> > >
> > > E AttributeError: 'ProvenancePath' object has no attribute '_drv'
> > > E AttributeError: 'ProvenancePath' object has no attribute '_raw_paths'
> > > E AttributeError: 'ProvenancePath' object has no attribute '_str'
> > > E AttributeError: 'OutPath' object has no attribute '_str'
> > >
> > > This all goes back to the qiime package but I admit I have no idea
> > > how to fix this.
> > >
> > > Kind regards
> > > Andreas.
> > >
> > >
> > > [3] 
> > > https://salsa.debian.org/med-team/q2-quality-control/-/jobs/5320775#L700
> > >
> > > Am Sat, Feb 17, 2024 at 11:36:41AM +0100 schrieb Andreas Tille:
> > > > Hi,
> > > >
> > > > as reported in a qiime2 issue[1] there is some problem with Python3.12
> > > > in the tests of the q2-* packages which are all using the qiime package.
> > > > This problem is currently hidden from the tests made by Python3.12
> > > > porters but it became obvious now on Salsa CI[2]. I tried to fiddle
> > > > around a bit 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
> > > >

I really don't know how to fix this issue with python 3.12, sorry :(
 
Kind Regards

[1] 

Bug#1053943: q2-taxa: test failure with pandas 2.1

2024-02-17 Thread s3v
Hi,

More immediate fix is attached but I guess there is a more elegant
way by changing the code in _ids_to_keep_from_taxonomy() function.

Please note I only ran pytest against q2_taxa/tests/test_methods.py
because q2-types are uninstallable ATM and the testing ops are a pain
after pandas added some breaks that heavy impact on qiime's plugin
dependency chain.
Reference link are below.

Thanks again for considering.

Kind Regards


[1] https://github.com/pandas-dev/pandas/issues/42825
[2] https://github.com/pandas-dev/pandas/pull/45052


On Sat, 17 Feb 2024 17:56:37 +0100 Andreas Tille  wrote:
> Control: tags -1 help
>
> Am Sat, Feb 17, 2024 at 06:35:41AM +0100 schrieb s3v:
> > Attached patch makes autopkg tests pass in unstable on a basis of
> > your work/references and [1] (iteritems() was deprecated since version
> > 1.5.0 in favor of items()).
>
> Cool. This is uploaded (but not yet in incoming due to some routing
> issue in Debian infrastructure.)
>
> > Please note that autopkg test fail with python 3.12 as default because
> > qiime2, I guess. (log attached).
>
> Thanks for the additional hint - I've forwarded the issue upstream.
>
> > Thanks for all your work!
>
> ... which is possible thanks to the help of kind people like you.
>
>
> The next problem is with q2-taxa, which throws some errors
>
> "Passing a set as an indexer is not supported. Use a list instead."
> E TypeError: Passing a set as an indexer is not supported. Use a list instead.
>
> Again I had some vague feeling what to do but failed finding an actual
> patch after poking around a bit.
>
> Any further help would be really great
> Andreas.
>
> --
> http://fam-tille.de
>
>
--- a/q2_taxa/_method.py
+++ b/q2_taxa/_method.py
@@ -79,7 +79,7 @@
 # becomes an issue, this is a target for refactoring.
 ids_to_keep -= set(taxonomy.get_ids(where=query))
 
-return ids_to_keep
+return list(ids_to_keep)
 
 
 def filter_table(table: pd.DataFrame, taxonomy: qiime2.Metadata,


Bug#1044068: q2templates: FTBFS with pandas 2.0

2024-02-16 Thread s3v
Hi,

sorry for writing again but, after removing override for auto_test in
d/rules and s/python3/python3-all in d/control for Build-Depends,
tests fail with Python 3.12:

dh_auto_clean
I: pybuild base:305: python3.12 setup.py clean
/build/q2templates-2023.9.0+ds/versioneer.py:422: SyntaxWarning: invalid escape 
sequence '\s'
  LONG_VERSION_PY['git'] = '''
Traceback (most recent call last):
  File "/build/q2templates-2023.9.0+ds/setup.py", line 14, in 
    version=versioneer.get_version(),
    
  File "/build/q2templates-2023.9.0+ds/versioneer.py", line 1481, in get_version
    return get_versions()["version"]
   ^^
  File "/build/q2templates-2023.9.0+ds/versioneer.py", line 1413, in 
get_versions
    cfg = get_config_from_root(root)
  ^^
  File "/build/q2templates-2023.9.0+ds/versioneer.py", line 343, in 
get_config_from_root
    parser = configparser.SafeConfigParser()
 ^
AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did 
you mean: 'RawConfigParser'?
E: pybuild pybuild:391: clean: plugin distutils failed with: exit code=1: 
python3.12 setup.py clean

Kind Regards



Bug#1044068: q2templates: FTBFS with pandas 2.0

2024-02-16 Thread s3v
Dear Maintainer,

According to [1][2]|

 Support for negative integer for :attr:`pd.options.display.max_colwidth`
 is deprecated in favor of using ``None`` (:issue:`31532`)|

I guess this line:

 with pd.option_context('display.max_colwidth', -1):

should be changed in:

 with pd.option_context('display.max_colwidth', None):

in [3].

I've not tested #1053942[4] disappears after this bug is fixed.

Kind Regards
 
[1] https://github.com/pandas-dev/pandas/pull/31569
[2] 
https://sources.debian.org/src/pandas/2.1.4%2Bdfsg-4/doc/source/whatsnew/v1.0.1.rst/#L46
[3] 
https://sources.debian.org/src/q2templates/2023.9.0%2Bds-1/q2templates/util.py/#L46
[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053942



Bug#1044079: augur: FTBFS with pandas 2.0

2024-02-14 Thread s3v
Dear Maintainer,

parse_time_string() function was renamed in parse_datetime_string_with_reso()
for better naming reasons [1]
Replacing this occurrence in augur/parse.py makes the package buildable.

I don't know if renaming is a drop-in replacement, I see this caveat:

    # NB: This will break with np.str_ (GH#45580) even though
    #  isinstance(npstrobj, str) evaluates to True, so caller must ensure
    #  the argument is *exactly* 'str'

Kind Regards

[1] https://github.com/pandas-dev/pandas/pull/50722



Bug#1056874: python-srsly: ftbfs with cython 3.0.x

2024-02-01 Thread s3v
Dear Maintainer,

Seems like python-catalogue 2.0.10 is newer than 2.1.0 :( [1]
After packaging python-catalogue 2.0.10 as 2.1.1+really2.0.10 (I didn't know how
to circumvent the version problem, sorry if this procedure is not appropriate!),
and cloning your git repo from salsa, tests still fail:

== short test 
summary info ==
FAILED 
srsly/tests/ruamel_yaml/test_anchor.py::TestDuplicateKeyThroughAnchor::test_duplicate_key_01
 - srsly.ruamel_yaml.constructor.ConstructorError: could not determine a 
constructor for the tag None
FAILED 
srsly/tests/ruamel_yaml/test_api_change.py::TestNewAPI::test_duplicate_keys_02 
- srsly.ruamel_yaml.constructor.ConstructorError: could not determine a 
constructor for the tag None
FAILED srsly/tests/ruamel_yaml/test_api_change.py::TestNewAPI::test_issue_135 - 
ruamel.yaml.emitter.EmitterError: expected SCALAR, SEQUENCE-START, 
MAPPING-START, or ALIAS
FAILED 
srsly/tests/ruamel_yaml/test_class_register.py::TestRegisterClass::test_register_0_safe
 - srsly.ruamel_yaml.constructor.ConstructorError: could not determine a 
constructor for the tag None
FAILED 
srsly/tests/ruamel_yaml/test_class_register.py::TestRegisterClass::test_register_0_unsafe
 - srsly.ruamel_yaml.constructor.ConstructorError: could not determine a 
constructor for the tag None
FAILED 
srsly/tests/ruamel_yaml/test_class_register.py::TestRegisterClass::test_register_1_safe
 - srsly.ruamel_yaml.constructor.ConstructorError: could not determine a 
constructor for the tag None
FAILED 
srsly/tests/ruamel_yaml/test_class_register.py::TestRegisterClass::test_register_1_unsafe
 - srsly.ruamel_yaml.constructor.ConstructorError: could not determine a 
constructor for the tag None
FAILED srsly/tests/ruamel_yaml/test_issues.py::TestIssues::test_issue_223 - 
srsly.ruamel_yaml.constructor.ConstructorError: could not determine a 
constructor for the tag None
FAILED srsly/tests/ruamel_yaml/test_issues.py::TestIssues::test_issue_245 - 
AssertionError: assert 'yes' is True
= 9 failed, 953 passed, 32 skipped, 
22 xfailed, 1 warning in 15.73s =

Failures above vanish after removing |python3-ruamel.yaml from build 
dependencies.

Kind Regards

[1] https://pypi.org/project/catalogue/#history
|



Bug#1058305: ipykernel: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-02-01 Thread s3v
Dear Maintainer,

This change from upstream [1] (ignore datetime.datetime.utcfromtimestamp()
DeprecationWarning), fixes this issue. I just verified the package builds
fine in a sid chroot environment and all tests pass.

Kind Regards

https://github.com/ipython/ipykernel/commit/de45c7a4#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711



Bug#1061229: numpydoc: Failing autopkgtest

2024-01-29 Thread s3v
Hi,

"-W" option in [1] leads to treat warnings as errors during
documentation build.
I guess is safe to remove this option for downstream users.

Thanks for your work.

Kind Regards

[1] 
https://sources.debian.org/src/numpydoc/1.6.0-1/numpydoc/tests/tinybuild/Makefile/#L8



Bug#1058335: python-apt: FTBFS: AssertionError: pyflakes failed with: 1

2024-01-28 Thread s3v
Hi,

I guess the change in pyflakes is intended, please see [1][2].

The FTBFS for src:python-apt 1.7.0 downloaded from shanpshot.d.o [3]
vanishes after rebuilding with this commit reverted [4] (attached
for saving your time and for double-checking purpose).

Kind Regards


[1] https://github.com/PyCQA/pyflakes/issues/747
[2] https://data.safetycli.com/packages/pypi/pyflakes/changelog
[3] https://snapshot.debian.org/package/python-apt/2.7.0/
[4] https://github.com/PyCQA/pyflakes/pull/684--- a/pyflakes/api.py
+++ b/pyflakes/api.py
@@ -44,7 +44,8 @@
 reporter.unexpectedError(filename, 'problem decoding source')
 return 1
 # Okay, it's syntactically valid.  Now check it.
-w = checker.Checker(tree, filename=filename)
+file_tokens = checker.make_tokens(codeString)
+w = checker.Checker(tree, file_tokens=file_tokens, filename=filename)
 w.messages.sort(key=lambda m: m.lineno)
 for warning in w.messages:
 reporter.flake(warning)
--- a/pyflakes/checker.py
+++ b/pyflakes/checker.py
@@ -15,6 +15,9 @@
 import re
 import string
 import sys
+import bisect
+import collections
+import tokenize
 import warnings
 
 from pyflakes import messages
@@ -66,6 +69,14 @@
 (isinstance(node, ast.Attribute) and node.attr == name)
 )
 
+# https://github.com/python/typed_ast/blob/1.4.0/ast27/Parser/tokenizer.c#L102-L104
+TYPE_COMMENT_RE = re.compile(r'^#\s*type:\s*')
+# https://github.com/python/typed_ast/blob/1.4.0/ast27/Parser/tokenizer.c#L1408-L1413
+ASCII_NON_ALNUM = ''.join([chr(i) for i in range(128) if not chr(i).isalnum()])
+TYPE_IGNORE_RE = re.compile(
+TYPE_COMMENT_RE.pattern + fr'ignore([{ASCII_NON_ALNUM}]|$)')
+# https://github.com/python/typed_ast/blob/1.4.0/ast27/Grammar/Grammar#L147
+TYPE_FUNC_RE = re.compile(r'^(\(.*?\))\s*->\s*(.*)$')
 
 MAPPING_KEY_RE = re.compile(r'\(([^()]*)\)')
 CONVERSION_FLAG_RE = re.compile('[#0+ -]*')
@@ -594,6 +605,11 @@
 class DoctestScope(ModuleScope):
 """Scope for a doctest."""
 
+class DummyNode:
+"""Used in place of an `ast.AST` to set error message positions"""
+def __init__(self, lineno, col_offset):
+self.lineno = lineno
+self.col_offset = col_offset
 
 class DetectClassScopedMagic:
 names = dir()
@@ -713,6 +729,60 @@
 return func(self, *args, **kwargs)
 return in_annotation_func
 
+def make_tokens(code):
+# PY3: tokenize.tokenize requires readline of bytes
+if not isinstance(code, bytes):
+code = code.encode('UTF-8')
+lines = iter(code.splitlines(True))
+# next(lines, b'') is to prevent an error in pypy3
+return tuple(tokenize.tokenize(lambda: next(lines, b'')))
+
+
+class _TypeableVisitor(ast.NodeVisitor):
+"""Collect the line number and nodes which are deemed typeable by
+PEP 484
+https://www.python.org/dev/peps/pep-0484/#type-comments
+"""
+def __init__(self):
+self.typeable_lines = []
+self.typeable_nodes = {}
+
+def _typeable(self, node):
+# if there is more than one typeable thing on a line last one wins
+self.typeable_lines.append(node.lineno)
+self.typeable_nodes[node.lineno] = node
+
+self.generic_visit(node)
+
+visit_Assign = visit_For = visit_FunctionDef = visit_With = _typeable
+visit_AsyncFor = visit_AsyncFunctionDef = visit_AsyncWith = _typeable
+
+
+def _collect_type_comments(tree, tokens):
+visitor = _TypeableVisitor()
+visitor.visit(tree)
+
+type_comments = collections.defaultdict(list)
+for tp, text, start, _, _ in tokens:
+if (
+tp != tokenize.COMMENT or  # skip non comments
+not TYPE_COMMENT_RE.match(text) or  # skip non-type comments
+TYPE_IGNORE_RE.match(text)  # skip ignores
+):
+continue
+
+# search for the typeable node at or before the line number of the
+# type comment.
+# if the bisection insertion point is before any nodes this is an
+# invalid type comment which is ignored.
+lineno, _ = start
+idx = bisect.bisect_right(visitor.typeable_lines, lineno)
+if idx == 0:
+continue
+node = visitor.typeable_nodes[visitor.typeable_lines[idx - 1]]
+type_comments[node].append((start, text))
+
+return type_comments
 
 class Checker:
 """I check the cleanliness and sanity of Python code."""
@@ -751,6 +821,7 @@
 self.withDoctest = withDoctest
 self.exceptHandlers = [()]
 self.root = tree
+self._type_comments = _collect_type_comments(tree, file_tokens)
 
 self.scopeStack = []
 try:
@@ -783,6 +854,25 @@
 """
 self._deferred.append((callable, self.scopeStack[:], self.offset))
 
+def _handle_type_comments(self, node):
+for (lineno, col_offset), comment in self._type_comments.get(node, ()):
+comment = comment.split(':', 1)[1].strip()
+func_match = TYPE_FUNC_RE.match(comment)
+

Bug#1056431: numpydoc's autopkg tests fail with Python 3.12

2024-01-26 Thread s3v
Control: reopen -1

Dear Maintainer,

autopkg tests still fail [1] with this error:

 49s = test session starts 
==
 49s platform linux -- Python 3.11.7, pytest-7.4.4, pluggy-1.3.0
 49s rootdir: /tmp/autopkgtest-lxc.4al_chdi/downtmp/build.77I/src
 49s configfile: pyproject.toml
 49s plugins: cov-4.1.0
 49s collected 286 items
 49s
 49s numpydoc/numpydoc.py .   [ 
 0%]
 49s numpydoc/validate.py .   [ 
 0%]
 49s numpydoc/tests/test_docscrape.py ... [ 
14%]
 49s .    [ 
21%]
 50s numpydoc/tests/test_full.py FF...    [ 
23%]
 50s numpydoc/tests/test_main.py ...  [ 
25%]
 51s numpydoc/tests/test_numpydoc.py .    [ 
30%]
 51s numpydoc/tests/test_validate.py  [ 
44%]
 51s x..x [ 
69%]
 51s ...  [ 
73%]
 51s numpydoc/tests/test_xref.py  [ 
88%]
 52s ...  [ 
95%]
 52s numpydoc/tests/hooks/test_utils.py . [ 
97%]
 52s numpydoc/tests/hooks/test_validate_hook.py   
[100%]
 52s
 52s === FAILURES 
===
 52s _ test_MyClass 
_
 52s
 52s sphinx_app = 
 52s
 52s def test_MyClass(sphinx_app):
 52s """Test that class documentation is reasonable."""
 52s src_dir, out_dir = sphinx_app.srcdir, sphinx_app.outdir
 52s class_rst = op.join(src_dir, "generated", 
"numpydoc_test_module.MyClass.rst")
 52s with open(class_rst) as fid:
 52s rst = fid.read()
 52s assert r"numpydoc\_test\_module" in rst  # properly escaped
 52s class_html = op.join(out_dir, "generated", 
"numpydoc_test_module.MyClass.html")
 52s with open(class_html) as fid:
 52s html = fid.read()
 52s # ensure that no autodoc weirdness ($) occurs
 52s assert "$self" not in html
 52s assert "/," not in html
 52s assert "__init__" in html  # inherited
 52s # escaped * chars should no longer be preceded by \'s,
 52s # if we see a \* in the output we know it's incorrect:
 52s assert r"\*" not in html
 52s # "self" should not be in the parameter list for the class:
 52s assert "self," not in html
 52s # check xref was embedded properly (dict should link using xref):
 52s >   assert "stdtypes.html#dict" in html
 52s E   assert 'stdtypes.html#dict' in '\n\n\n  \n    \n    Page 
source\n    \n\n    \n\n    \n  \n'
 52s
 52s class_html = 
'/tmp/pytest-of-debci/pytest-0/root/_build/html/generated/numpydoc_test_module.MyClass.html'
 52s class_rst  = 
'/tmp/pytest-of-debci/pytest-0/root/generated/numpydoc_test_module.MyClass.rst'
 52s fid    = <_io.TextIOWrapper 
name='/tmp/pytest-of-debci/pytest-0/root/_build/html/generated/numpydoc_test_module.MyClass.html'
 mode='r' encoding='UTF-8'>
 52s html   = '\n\n\n  \n    \n    Page
source\n    \n\n    \n\n    \n  \n'
 52s out_dir    = _StrPath('/tmp/pytest-of-debci/pytest-0/root/_build/html')
 52s rst    = 
'\ufeffnumpydoc\\_test\\_module.MyClass\n==\n\n.. 
currentmodule:: numpydoc_test_module\n\n...bric:: Methods\n\n   .. 
autosummary::\n   \n 
~MyClass.__init__\n  ~MyClass.example\n   \n   \n\n   \n   \n   '
 52s sphinx_app = 
 52s src_dir    = _StrPath('/tmp/pytest-of-debci/pytest-0/root')
 52s
 52s numpydoc/tests/test_full.py:62: AssertionError
 52s  Captured stdout setup 
-
 52s Running Sphinx v7.2.6
 52s making output directory... done
 52s loading intersphinx inventory from 
/usr/share/doc/python3/html/objects.inv...
 52s [autosummary] generating autosummary for: index.rst
 52s [autosummary] generating autosummary for: 
/tmp/pytest-of-debci/pytest-0/root/generated/numpydoc_test_module.MyClass.rst,
/tmp/pytest-of-debci/pytest-0/root/generated/numpydoc_test_module.my_function.rst
 52s building [mo]: targets for 0 po files that are out of date
 52s writing output... 
 52s building [html]: targets for 1 source files that are out 
of date
 52s updating environment: [new config] 3 added, 0 changed, 0 
removed
 52s reading sources... [ 33%] 
generated/numpydoc_test_module.MyClass
reading sources... 

Bug#1057576: mako: FTBFS: dh_sphinxdoc: error: debian/python-mako-doc/usr/share/doc/python-mako-doc/html/search.html top-level node does not have data-content_root attribute

2024-01-24 Thread s3v
Dear Maintainer,

Your package builds fine locally in a sid chroot environment, but I'm
able to reproduce the reported failure against zzzeeksphinx/1.4.0-1
from snapshot.debian.org [1].
Reported FTBFS log states:

  Get:98 http://deb.debian.org/debian sid/main amd64 python3-zzzeeksphinx all 
1.4.0-1 [80.8 kB]

I guess the bug is fixed in zzzeeksphinx/1.4.0-2 [2] currently in
unstable and trixie.

Kind Regards

[1] https://snapshot.debian.org/package/zzzeeksphinx/1.4.0-1/
[2] 
https://tracker.debian.org/news/1492136/accepted-zzzeeksphinx-140-2-source-into-unstable/



Bug#1058366: beaker: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-24 Thread s3v
Dear Maintainer,

This issue was fixed in cryptodrome [1] and I can build successfully your 
package
in a sid chroot environment for amd64 architecture.
I guess the failure still persists on armel and mips64el [2] (not verified).

  ∙ ∙ missing build on armel
  ∙ ∙ missing build on mips64el

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052336
[2] https://tracker.debian.org/pkg/pycryptodome



Bug#1058364: python-etcd: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-22 Thread s3v
Dear Maintainer,

Please find attached two patches that make your package buildable in my
sid chroot environment.
Please also refers to these commits [1][2] where patches come from.

Kind Regards

[1] 
https://github.com/jplana/python-etcd/commit/68d8d5dd4ae7ece6c63f446e3c38448998cde3e4
[2] 
https://github.com/jplana/python-etcd/commit/b8f3ad0d19626b21b08892ac910fc2e72e0001b6--- a/src/etcd/tests/unit/test_lock.py
+++ b/src/etcd/tests/unit/test_lock.py
@@ -90,8 +90,7 @@
 """
 self.locker._sequence = '4'
 retval = ('/_locks/test_lock/4', None)
-self.locker._get_locker = mock.MagicMock(
-spec=self.locker._get_locker, return_value=retval)
+self.locker._get_locker = mock.MagicMock(return_value=retval)
 self.assertTrue(self.locker._acquired())
 self.assertTrue(self.locker.is_taken)
 retval = ('/_locks/test_lock/1', '/_locks/test_lock/4')
@@ -112,8 +111,7 @@
 def side_effect():
 return returns.pop()
 
-self.locker._get_locker = mock.MagicMock(
-spec=self.locker._get_locker, side_effect=side_effect)
+self.locker._get_locker = mock.MagicMock(side_effect=side_effect)
 self.assertTrue(self.locker._acquired())
 
 def test_acquired_no_timeout(self):
--- a/src/etcd/tests/unit/test_lock.py
+++ b/src/etcd/tests/unit/test_lock.py
@@ -31,9 +31,9 @@
 """
 Verify the lock gets initialized correctly
 """
-self.assertEquals(self.locker.name, u'test_lock')
-self.assertEquals(self.locker.path, u'/_locks/test_lock')
-self.assertEquals(self.locker.is_taken, False)
+self.assertEqual(self.locker.name, u'test_lock')
+self.assertEqual(self.locker.path, u'/_locks/test_lock')
+self.assertEqual(self.locker.is_taken, False)
 
 def test_acquire(self):
 """
@@ -52,8 +52,8 @@
 }
 }
 self._mock_api(200, d)
-self.assertEquals(l.acquire(), True)
-self.assertEquals(l._sequence, '1')
+self.assertEqual(l.acquire(), True)
+self.assertEqual(l._sequence, '1')
 
 def test_is_acquired(self):
 """
@@ -70,7 +70,7 @@
 }
 self._mock_api(200, d)
 self.locker.is_taken = True
-self.assertEquals(self.locker.is_acquired, True)
+self.assertEqual(self.locker.is_acquired, True)
 
 def test_is_not_acquired(self):
 """
@@ -78,11 +78,11 @@
 """
 self.locker._sequence = '2'
 self.locker.is_taken = False
-self.assertEquals(self.locker.is_acquired, False)
+self.assertEqual(self.locker.is_acquired, False)
 self.locker.is_taken = True
 self._mock_exception(etcd.EtcdKeyNotFound, self.locker.lock_key)
-self.assertEquals(self.locker.is_acquired, False)
-self.assertEquals(self.locker.is_taken, False)
+self.assertEqual(self.locker.is_acquired, False)
+self.assertEqual(self.locker.is_taken, False)
 
 def test_acquired(self):
 """
@@ -147,11 +147,11 @@
 with self.assertRaises(ValueError):
 self.locker.lock_key
 self.locker._sequence = '5'
-self.assertEquals(u'/_locks/test_lock/5',self.locker.lock_key)
+self.assertEqual(u'/_locks/test_lock/5',self.locker.lock_key)
 
 def test_set_sequence(self):
 self.locker._set_sequence('/_locks/test_lock/10')
-self.assertEquals('10', self.locker._sequence)
+self.assertEqual('10', self.locker._sequence)
 
 def test_find_lock(self):
 d = {
@@ -171,11 +171,11 @@
 self.locker._sequence = None
 self.recursive_read()
 self.assertTrue(self.locker._find_lock())
-self.assertEquals(self.locker._sequence, '34')
+self.assertEqual(self.locker._sequence, '34')
 
 def test_get_locker(self):
 self.recursive_read()
-self.assertEquals((u'/_locks/test_lock/1', etcd.EtcdResult(node={'newKey': False, '_children': [], 'createdIndex': 33, 'modifiedIndex': 33, 'value': u'2qwwwq', 'expiration': None, 'key': u'/_locks/test_lock/1', 'ttl': None, 'action': None, 'dir': False})),
+self.assertEqual((u'/_locks/test_lock/1', etcd.EtcdResult(node={'newKey': False, '_children': [], 'createdIndex': 33, 'modifiedIndex': 33, 'value': u'2qwwwq', 'expiration': None, 'key': u'/_locks/test_lock/1', 'ttl': None, 'action': None, 'dir': False})),
   self.locker._get_locker())
 with self.assertRaises(etcd.EtcdLockExpired):
 self.locker._sequence = '35'
--- a/src/etcd/tests/unit/test_old_request.py
+++ b/src/etcd/tests/unit/test_old_request.py
@@ -42,7 +42,7 @@
 
 result = client.set('/testkey', 'test', ttl=19)
 
-self.assertEquals(
+self.assertEqual(
 etcd.EtcdResult(
 **{u'action': u'SET',
'node': {
@@ -67,7 +67,7 @@
   

Bug#1060997: khard: FTBFS: make[2]: *** [Makefile:20: html] Error 2

2024-01-21 Thread s3v
Dear Maintainer,

After sphinx-autoapi/3.0.0-0.1 entered in unstable [1], I'm able to
build successfully your package in a sid chroot environment.
I can reproduce the failure reported in this bug after building
against sphinx-autoapi/2.0.0-2 from snapshot.d.o [2].

Kind Regards

[1] 
https://tracker.debian.org/news/1496099/accepted-sphinx-autoapi-300-01-source-into-unstable
[2] https://snapshot.debian.org/package/sphinx-autoapi/2.0.0-2/



Bug#1051166: FTBFS with doxygen 1.9.8

2024-01-21 Thread s3v
Dear Maintainer,

After removing "-W" from [1], your package builds fine in a sid chroot
environment.
I guess is safe to stop treating sphinx warnings as errors.

Kind Regards

[1] https://sources.debian.org/src/breathe/4.35.0-2/documentation/Makefile/#L5



Bug#1058381: casa-formats-io: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-17 Thread s3v
Dear Maintainer,

>  ERRORS 
> 
> _ ERROR collecting 
> .pybuild/cpython3_3.12_casa-formats-io/build/casa_formats_io/glue_factory.py _
> /usr/lib/python3/dist-packages/_pytest/runner.py:341: in from_call
> result: Optional[TResult] = func()
> /usr/lib/python3/dist-packages/_pytest/runner.py:372: in 
> call = CallInfo.from_call(lambda: list(collector.collect()), "collect")
> /usr/lib/python3/dist-packages/pytest_doctestplus/plugin.py:250: in collect
> module = import_path(fspath, root=self.config.rootpath)
> /usr/lib/python3/dist-packages/_pytest/pathlib.py:567: in import_path
> importlib.import_module(module_name)
> /usr/lib/python3.12/importlib/__init__.py:90: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> :1387: in _gcd_import
> ???
> :1360: in _find_and_load
> ???
> :1331: in _find_and_load_unlocked
> ???
> :935: in _load_unlocked
> ???
> :994: in exec_module
> ???
> :488: in _call_with_frames_removed
> ???
> casa_formats_io/glue_factory.py:7: in 
> from glue.core import Data
> /usr/lib/python3/dist-packages/glue/__init__.py:22: in 
> from .config import load_configuration
> /usr/lib/python3/dist-packages/glue/config.py:2: in 
> import imp
> E   ModuleNotFoundError: No module named 'imp'
> === short test summary info 
> 
> ERROR casa_formats_io/glue_factory.py - ModuleNotFoundError: No module named 
> ...
>  Interrupted: 1 error during collection 
> 
> === 1 error in 1.37s 
> ===

The issue comes from glue's source code.
'imp' module was removed from Python 3.12 [1]

Kind Regards

[1] https://docs.python.org/3/whatsnew/3.12.html#imp



Bug#1058432: glyphslib: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-17 Thread s3v
Dear Maintainer,

> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>/.pybuild/cpython3_3.12/build
> configfile: pyproject.toml
> collected 0 items / 29 errors
> 
>  ERRORS 
> 
>  ERROR collecting tests/classes_test.py 
> 
> ImportError while importing test module 
> '/<>/.pybuild/cpython3_3.12/build/tests/classes_test.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.12/importlib/__init__.py:90: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/classes_test.py:23: in 
> from glyphsLib.classes import (
> glyphsLib/__init__.py:21: in 
> from glyphsLib.classes import GSFont, __all__ as __all_classes__
> glyphsLib/classes.py:26: in 
> import openstep_plist
> /usr/lib/python3/dist-packages/openstep_plist/__init__.py:1: in 
> from .parser import load, loads, ParseError
> E   ModuleNotFoundError: No module named 'openstep_plist.parser'
...
...


after python-openstep-plist/0.3.1-1 entered in unstable [1], your package
builds fine locally in a sid chroot environment and autopkg tests pass as well.
Please consider to close this bug when you are able to confirm that.

Kind Regards

[1] 
https://tracker.debian.org/media/packages/p/python-openstep-plist/changelog-0.3.1-1



Bug#1058388: fontmake: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-17 Thread s3v
Dear Maintainer,

> fontmake/font_project.py:946:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _
> fontmake/font_project.py:1006: in _run_from_designspace_static
> ufos.extend(
> fontmake/font_project.py:744: in interpolate_instance_ufos
> from glyphsLib.interpolation import apply_instance_data_to_ufo
> /usr/lib/python3/dist-packages/glyphsLib/__init__.py:21: in 
> from glyphsLib.classes import GSFont, __all__ as __all_classes__
> /usr/lib/python3/dist-packages/glyphsLib/classes.py:26: in 
> import openstep_plist
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _
>
> >   from .parser import load, loads, ParseError
> E   ModuleNotFoundError: No module named 'openstep_plist.parser'
>
> /usr/lib/python3/dist-packages/openstep_plist/__init__.py:1: 
> ModuleNotFoundError


after python-openstep-plist/0.3.1-1 entered in unstable [1], your package
builds fine locally in a sid chroot environment.
Please consider to close this bug when you are able to confirm that.

Kind Regards

[1] 
https://tracker.debian.org/media/packages/p/python-openstep-plist/changelog-0.3.1-1



Bug#1058027: pybj: FTBFS with Python 3.12

2024-01-12 Thread s3v
Dear Maintainer,

Python 3.12 changed recursion mechanism [1]

 sys.setrecursionlimit() and sys.getrecursionlimit(). The recursion limit
 now applies only to Python code. Builtin functions do not use the recursion
 limit, but are protected by a different mechanism that prevents recursion
 from causing a virtual machine crash.

so increasing recursion limit as py-ubjson did [2] makes your package
buildable.
E.g.

--- a/test/test.py
+++ b/test/test.py
@@ -477,10 +477,10 @@
 
 def test_recursion(self):
 old_limit = getrecursionlimit()
-    setrecursionlimit(200)
+    setrecursionlimit(100)
 try:
 obj = current = []
-    for _ in range(getrecursionlimit() * 2):
+    for _ in range(getrecursionlimit() * 30):
 new_list = []
 current.append(new_list)
 current = new_list
@@ -488,7 +488,7 @@
 with self.assert_raises_regex(RuntimeError, 'recursion'):
 self.bjddumpb(obj)
 
-    raw = ARRAY_START * (getrecursionlimit() * 2)
+    raw = ARRAY_START * (getrecursionlimit() * 30)
 with self.assert_raises_regex(RuntimeError, 'recursion'):
 self.bjdloadb(raw)
 finally:


Kind Regards

[1] https://docs.python.org/3/whatsnew/3.12.html#sys
[2] 
https://sources.debian.org/src/py-ubjson/0.16.1-3/debian/patches/py12_recursion_PR19.diff/



Bug#1056476: python-importlib-metadata's autopkg tests fail with Python 3.12

2024-01-12 Thread s3v
Dear Maintainer,

> 450s   File
> "/tmp/autopkgtest.5EvlHX/autopkgtest_tmp/tests/test_main.py", line 8, in
> 
> 450s import pyfakefs.fake_filesystem_unittest as ffs
> 450s   File
> "/usr/lib/python3/dist-packages/pyfakefs/fake_filesystem_unittest.py",
> line 72, in 
> 450s from pyfakefs import fake_pathlib
> 450s   File "/usr/lib/python3/dist-packages/pyfakefs/fake_pathlib.py",
> line 164, in 
> 450s flavour = pathlib._Flavour  # type: ignore [attr-defined]
> 450s   
> 450s AttributeError: module 'pathlib' has no attribute '_Flavour'

the failure was fixed in python-pyfakefs/5.3.2-1 [1] uploaded in unstable.
Your package builds fine now and all tests pass as well.

Kind Regards

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056524



Bug#1055718: python-openstep-plist ftbfs with Python 3.12

2024-01-12 Thread s3v
Dear Maintainer,

I was able to build successfully python-openstep-plist/0.3.1-1~exp1 in a sid 
chroot
environment for amd64 architecture.
0.3.1-1~exp1 landed in experimental for a while, Is there some concern that 
prevents
upload to unstable?
Please note that this issue affects (at least) fontmake [1] and glyphslib [2]

Kind Regards


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058388
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058432



Bug#1058321: python-loompy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-12 Thread s3v
Dear Maintainer,

> > E   If you are not working on Numba development, the original error was: 
> > 'cannot import name '_typeconv' from 'numba.core.typeconv' 
> > (/usr/lib/python3/dist-packages/numba/core/typeconv/__init__.py)'.
> > E   For help, please visit:
> > E   
> > E   
> > https://numba.readthedocs.io/en/stable/user/faq.html#numba-could-not-be-imported

This is issue was fixed in numba/0.58.1+dfsg-1 [1] actually in unstable and I've
verified your package builds fine locally and autopkg tests pass as well.

Kind Regards

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058301



Bug#1058301: resampy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-11 Thread s3v
Dear Maintainer,

> E   If you are not working on Numba development, the original error was: 
> 'cannot import name '_typeconv' from 'numba.core.typeconv' 
> (/usr/lib/python3/dist-packages/numba/core/typeconv/__init__.py)'.
> E   For help, please visit:
> E   
> E   
> https://numba.readthedocs.io/en/stable/user/faq.html#numba-could-not-be-imported

This is issue was fixed in numba/0.58.1+dfsg-1 [1] actually in unstable and I've
verified your package builds fine locally and autopkg tests pass as well.

Kind Regards

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058301



Bug#1058414: python-itsdangerous: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-11 Thread s3v
Dear Maintainer,

I've successfully built your package locally after commenting these lines [1].
I guess is safe to stop treating warning as errors for downstream users.

Kind Regards

[1] 
https://sources.debian.org/src/python-itsdangerous/2.1.2-3/setup.cfg/#L40-L41



Bug#1058031: pygame: FTBFS with Python 3.12

2024-01-10 Thread s3v
Dear Maintainer,

AssertionError comes from comparing '...' occurrences in
test result output with the number of ran tests.
I've added this code:

    with open('/tmp/debian-tmp', 'a') as f:
    import pprint, copy
    tmp_results = copy.deepcopy(results)
    for k, v in tmp_results.items():
    v['output'] = v['output'].split('\n')
    pprint.pprint(tmp_results, f, indent=2)

at line 292 in test/test_utils/run_tests.py [1]; two dicts and the diff
between Python 3.11 and 3.12 are attached. (Please note different values
for 'num_tests' keys).

Something has been changed in python 3.12 at presenting test results
when there are skipped tests:

(test.py)

import unittest

class FooTest(unittest.TestCase):
    @unittest.skip
    def test_foo(self):
    self.assertTrue(True)

    def test_bar(self):
    self.assertFalse(False)

if __name__ == '__main__':
    unittest.main()


$ python3.11 test.py
.s
--
Ran 2 tests in 0.000s

OK (skipped=1)


$ python3.12 test.py
.s
--
Ran 1 test in 0.000s

OK (skipped=1)


I don't know if this change is intended or it's a bug (I wasn't
able to find references in python 3.12 changelog).

Kind Regards

[1] 
https://sources.debian.org/src/pygame/2.5.2-1.1/test/test_utils/run_tests.py/#L292




3.11-results.tar.gz
Description: application/gzip


3.12-results.tar.gz
Description: application/gzip


diff-results.tar.gz
Description: application/gzip


Bug#1052800: parso: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2024-01-07 Thread s3v
Control: forwarded -1 https://github.com/davidhalter/parso/issues/222
thanks

Dear Maintainer,

After adding:

  export PYBUILD_BEFORE_TEST=cp conftest.py {build_dir}

in debian/rules, tests pass with Python 3.11 but still fail with
Python 3.12.
I've opened an issue upstream.


...
make[1]: Leaving directory '/build/parso-0.8.3'
   dh_auto_test -O--buildsystem=pybuild
I: pybuild pybuild:310: cp conftest.py 
/build/parso-0.8.3/.pybuild/cpython3_3.12_parso/build
I: pybuild base:305: cd /build/parso-0.8.3/.pybuild/cpython3_3.12_parso/build; 
python3.12 -m pytest test
 test 
session starts 

platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.3.0
rootdir: /build/parso-0.8.3/.pybuild/cpython3_3.12_parso/build
configfile: pytest.ini
collected 1348 items
    

test/test_cache.py .
  [  0%]
test/test_diff_parser.py 
..
   [  6%]
test/test_dump_tree.py ..   
  [  7%]
test/test_error_recovery.py .   
  [  8%]
test/test_file_python_errors.py .   
  [  8%]
test/test_fstring.py 
.   
 [ 13%]
test/test_get_code.py . 
  [ 14%]
test/test_grammar.py .  
  [ 14%]
test/test_load_grammar.py ...   
  [ 15%]
test/test_normalizer_issues_files.py .  
  [ 17%]
test/test_old_fast_parser.py ...
  [ 19%]
test/test_param_splitting.py ...
  [ 19%]
test/test_parser.py 
.
 [ 29%]
.   
  [ 30%]
test/test_parser_tree.py 
... 
 [ 35%]
test/test_pep8.py ...   
  [ 36%]
test/test_pgen2.py 
..
 [ 45%]
.
 [ 56%]
test/test_prefix.py ..  
  [ 57%]
test/test_python_errors.py 
...FF.
 [ 66%]
FF..FFF.F.F..
 [ 78%]
.
 [ 87%]
test/test_tokenize.py 
...
 [ 97%]
.   
  [ 97%]
test/test_utils.py ...  
  [100%]


Bug#1052844: deepdiff: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2024-01-07 Thread s3v
Dear Maintainer,

after adding:

  export PYBUILD_BEFORE_TEST=cp conftest.py {build_dir}

in debian/rules, I was able to build yout package in a sid
chroot environment.

Kind Regards



Bug#1056042: xrayutilities ftbfs with Python 3.12

2024-01-06 Thread s3v
Dear Maintainer,

After uncertainties/3.1.7 entered in unstable, your package builds fine
in my sid chroot environment and all tests pass.

Import that triggers the failure:

  from past.builtins import basestring

was turned in:

if sys.version_info < (3,):
 from past.builtins import basestring
else:
 # Avoid importing from past in Python 3 since it utilizes the builtin
 # 'imp' module, which is deprecated as of Python 3.4, see
 # https://docs.python.org/3/library/imp.html. The 2to3 tool replaces
 # basestring with str, so that's what we effectively do here as well:
 basestring = str


Kind Regards

[1] 
https://salsa.debian.org/debian/python-uncertainties/-/commit/f9951a9e9d708c8ec38d6a0488f865d8


On Thu, 16 Nov 2023 09:57:09 +0100 Matthias Klose  wrote:
> Package: src:xrayutilities
> Version: 1.7.4-1
> Severity: important
> Tags: sid trixie
> User: debian-pyt...@lists.debian.org
> Usertags: python3.12
>
> some tests fail with:
>
> [...]
> /usr/lib/python3.12/subprocess.py:571: CalledProcessError
> - Captured stderr call
> -
> Traceback (most recent call last):
> File
> "/<>/.pybuild/cpython3_3.12_xrayutilities/build/examples/simpack_xrr_SiO2_Ru_CoFe_IrMn_Al2O3.py",
> line 20, in 
> import lmfit
> File "/usr/lib/python3/dist-packages/lmfit/__init__.py", line 38, in
> 
> from .confidence import conf_interval, conf_interval2d
> File "/usr/lib/python3/dist-packages/lmfit/confidence.py", line 10,
> in 
> from .minimizer import MinimizerException
> File "/usr/lib/python3/dist-packages/lmfit/minimizer.py", line 41, in
> 
> from .parameter import Parameter, Parameters
> File "/usr/lib/python3/dist-packages/lmfit/parameter.py", line 10, in
> 
> from uncertainties import correlated_values, ufloat
> File "/usr/lib/python3/dist-packages/uncertainties/__init__.py", line
> 225, in 
> from .core import *
> File "/usr/lib/python3/dist-packages/uncertainties/core.py", line 22,
> in 
> from past.builtins import basestring
> File "/usr/lib/python3/dist-packages/past/builtins/__init__.py", line
> 54, in 
> from past.builtins.misc import (apply, chr, cmp, execfile, intern, oct,
> File "/usr/lib/python3/dist-packages/past/builtins/misc.py", line 45,
> in 
> from imp import reload
> ModuleNotFoundError: No module named 'imp'
>
> complete build log at
> https://launchpadlibrarian.net/697894338/buildlog_ubuntu-noble-amd64.xrayutilities_1.7.4-1build2_BUILDING.txt.gz
>
>



Bug#1056467: python-djangosaml2's autopkg tests fail with Python 3.12

2023-12-24 Thread s3v
Dear Maintainer,

This issue was fixed in the new upload of python3-xmlschema and autopkg tests
pass now.

Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058194

Kind Regards



Bug#1058194: python-djangosaml2: FTBFS: AttributeError: type object '_PurePosixPath' has no attribute '_from_parts'. Did you mean: '_load_parts'?

2023-12-24 Thread s3v
Dear Maintainer,

>   File "/usr/lib/python3/dist-packages/xmlschema/__init__.py", line 20, in 
>
> from .dataobjects import DataElement, DataElementConverter, 
>DataBindingConverter
>   File "/usr/lib/python3/dist-packages/xmlschema/dataobjects.py", line 27, in 
>
> from . import validators
>   File "/usr/lib/python3/dist-packages/xmlschema/validators/__init__.py", 
>line 38, in 
> from .schemas import XMLSchemaMeta, XMLSchemaBase, XMLSchema, 
>XMLSchema10, XMLSchema11
>   File "/usr/lib/python3/dist-packages/xmlschema/validators/schemas.py", line 
>2137, in 
> class XMLSchema10(XMLSchemaBase):
>   File "/usr/lib/python3/dist-packages/xmlschema/validators/schemas.py", line 
>148, in __new__
> meta_schema = meta_schema_class.create_meta_schema(meta_schema_file)
>   ^^
>   File "/usr/lib/python3/dist-packages/xmlschema/validators/schemas.py", line 
>763, in create_meta_schema
> meta_schema = meta_schema_class(source, XSD_NAMESPACE, 
>global_maps=global_maps,
>   
>^
>   File "/usr/lib/python3/dist-packages/xmlschema/validators/schemas.py", line 
>357, in __init__
> self.source = XMLResource(source, base_url, allow, defuse, timeout)
>   ^
>   File "/usr/lib/python3/dist-packages/xmlschema/resources.py", line 511, in 
>__init__
> self.parse(source, lazy)
>   File "/usr/lib/python3/dist-packages/xmlschema/resources.py", line 746, in 
>parse
> url = normalize_url(source, self._base_url)
>   ^
>   File "/usr/lib/python3/dist-packages/xmlschema/resources.py", line 188, in 
>normalize_url
> path = _PurePath.from_uri(url)
>    ^^^
>   File "/usr/lib/python3/dist-packages/xmlschema/resources.py", line 109, in 
>from_uri
> return cls(uri)
>    
>   File "/usr/lib/python3/dist-packages/xmlschema/resources.py", line 98, in 
>__new__
> return cast('_PurePath', cls._from_parts(args))

This issue has been fixed in python3-xmlschema/1.10.0-7 [1] and your package 
does build
fine now.

Kind Regards


[1] 
https://tracker.debian.org/news/1485130/accepted-python-xmlschema-1100-7-source-into-unstable/



Bug#1056421: loguru's autopkg tests fail with Python 3.12

2023-12-22 Thread s3v
Control: retitle -1 loguru's autopkg tests fail with Python 3.12

Dear Maintainer,

autopkg tests still fail due a missing dependency on python3-freezegun in
debian/tests/control [1]

 24s autopkgtest [05:10:53]: test run-unit-test: [---
 25s Testing with python3.11 in 
/tmp/autopkgtest-lxc.xz0y_xxw/downtmp/autopkgtest_tmp:
 25s ImportError while loading conftest 
'/tmp/autopkgtest-lxc.xz0y_xxw/downtmp/autopkgtest_tmp/tests/conftest.py'.
 25s tests/conftest.py:16: in 
 25s import freezegun
 25s E   ModuleNotFoundError: No module named 'freezegun'
 25s autopkgtest [05:10:54]: test run-unit-test: ---]

Kind regards

[1] https://tracker.debian.org/pkg/loguru



Bug#1056457: [Debichem-devel] Bug#1056457: python-ase's autopkg tests fail with Python 3.12

2023-12-21 Thread s3v
Hi,

On Thu, 21 Dec 2023 08:39:54 +0200 Andrius Merkys  wrote:
> Is there a way to ignore DeprecationWarnings, but leave them in to the
> output? They are quite helpful to see, but not worth failing the build
> at the time being.
>

You're right, deprecation outputs are useful.
I've just tried by commenting "error" in ase/test/pytest.ini for stop
treating warnings as errors. Outputs are in place and tests don't fail
as well.


= warnings 
summary ==
...
...
test_forcecurve.py::test_forcecurve
  /usr/lib/python3/dist-packages/dateutil/tz/tz.py:37: DeprecationWarning: 
datetime.datetime.utcfromtimestamp() is deprecated and scheduled for removal in 
a future version. Use timezone-aware objects
to represent datetimes in UTC: datetime.datetime.fromtimestamp(timestamp, 
datetime.UTC).
    EPOCH = datetime.datetime.utcfromtimestamp(0)

test_parsemath.py: 109 warnings
constraints/test_parameteric_constr.py: 66 warnings
fio/test_aims_io.py: 66 warnings
  
/build/python-ase-3.22.1/.pybuild/cpython3_3.12_ase/build/ase/utils/parsemath.py:146:
 DeprecationWarning: ast.Num is deprecated and will be removed in Python 3.14; 
use ast.Constant instead
    if isinstance(node, ast.Num):  # 

test_parsemath.py: 50 warnings
constraints/test_parameteric_constr.py: 64 warnings
fio/test_aims_io.py: 45 warnings
  
/build/python-ase-3.22.1/.pybuild/cpython3_3.12_ase/build/ase/utils/parsemath.py:147:
 DeprecationWarning: Attribute n is deprecated and will be removed in Python 
3.14; use value instead
    return node.n



Thanks for maintaining python-ase!



Bug#1056457: python-ase's autopkg tests fail with Python 3.12

2023-12-20 Thread s3v
Dear Maintainer,

After applying [1][2][3] from upstream and adding "-p no:warnings":

  addopts = -p no:cacheprovider -p no:warnings
 
in ase/test/pytest.ini (DeprecationWarnings from various packages make
tests fail), I was able to build your package in a sid chroot environment.

Kind Regards

[1] https://gitlab.com/ase/ase/-/commit/9c019c1782115343014691596514eb6d351e8e17
[2] https://gitlab.com/ase/ase/-/commit/f0932b3385fea739bc737e5aec1fc92960b0550c
[3] https://gitlab.com/ase/ase/-/merge_requests/3022



Bug#1054726: python-daemon: FTBFS: ValueError: ("Missing 'Version:' header and/or PKG-INFO file at path: /<>/python_daemon.egg-info/PKG-INFO", python-daemon [unknown version] (/<

2023-12-16 Thread s3v
Dear Maintainer,

I've just checked your package does build fine in a sid chroot environment and
reproducible-builds confirms that [1]

>From the log:
 
 >> Get:75 http://127.0.0.1:12990/debian sid/main amd64 dh-python all 
6.20231025 [107 kB]

it was built against dh-python/6.20231025 but the current version in sid is
dh-python/6.20231204. I can reproduce the failure with this commit reverted [2].

Kind Regards

[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-daemon.html
[2] 
https://salsa.debian.org/python-team/tools/dh-python/-/commit/31553e7169b1cd72f6



Bug#1058384: lazy-object-proxy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2023-12-13 Thread s3v
Control: forwarded -1 
https://github.com/ionelmc/python-lazy-object-proxy/pull/78

Dear Maintainer,
Root cause is that deprecations are treated as errors in pytest.ini [1]

Kind regards

[1] https://sources.debian.org/src/lazy-object-proxy/1.9.0-1/pytest.ini/#L35-L36



Bug#1054725: pacparser: FTBFS: IndexError: list index out of range

2023-12-13 Thread s3v
Dear Maintainer,

A possible fix should be [1], however the package is severely outdated
(v1.3.6 comes from 2015...).
Please package newer version (I'm attaching the output of `git diff HEAD`
between 1.3.6 and 1.4.2 as a possible starting point; I've also skipped
git from B-D for getting VERSION from d/rules).

With those changes I was able to build pacparser is a sid chroot
environment but I haven't tested pacparser functionality.

Kind Regards


[1] https://github.com/manugarg/pacparser/commit/36010edefaf87a82a389cdiff --git a/debian/compat b/debian/compat
deleted file mode 100644
index 7f8f011..000
--- a/debian/compat
+++ /dev/null
@@ -1 +0,0 @@
-7
diff --git a/debian/control b/debian/control
index 6a8a280..b5551d8 100644
--- a/debian/control
+++ b/debian/control
@@ -1,10 +1,14 @@
 Source: pacparser
 Section: libs
-Priority: extra
+Priority: optional
 Maintainer: Manu Garg 
 Uploaders: Andrew Pollock 
-Build-Depends: debhelper (>= 5), python3-all-dev, dh-python
-Standards-Version: 3.9.6
+Build-Depends: debhelper-compat (= 13),
+   dh-sequence-python3,
+   python3-all-dev
+Rules-Requires-Root: no
+Standards-Version: 4.6.2
+Homepage: https://github.com/manugarg/pacparser
 
 Package: libpacparser1
 Section: libs
diff --git a/debian/docs b/debian/docs
index e0d7d67..9df535e 100644
--- a/debian/docs
+++ b/debian/docs
@@ -1,2 +1,2 @@
 README.md
-README.win32
+#README.win32
diff --git a/debian/patches/0001-Fix-possible-memory-overwrite-vulnerability.-134.patch b/debian/patches/0001-Fix-possible-memory-overwrite-vulnerability.-134.patch
deleted file mode 100644
index e64cd6a..000
--- a/debian/patches/0001-Fix-possible-memory-overwrite-vulnerability.-134.patch
+++ /dev/null
@@ -1,30 +0,0 @@
-From 91a93b40f6b4e0a1a9ac497edfbc2a4b18196483 Mon Sep 17 00:00:00 2001
-From: Manu Garg 
-Date: Wed, 13 Apr 2022 14:30:07 -0700
-Subject: Fix possible memory overwrite vulnerability. (#134)
-

- src/pacparser.c | 4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/src/pacparser.c b/src/pacparser.c
-index cc70a64..5a37d09 100644
 a/src/pacparser.c
-+++ b/src/pacparser.c
-@@ -440,11 +440,11 @@ pacparser_find_proxy(const char *url, const char *host)
-   // Hostname shouldn't have single quotes in them
-   if (strchr(host, '\'')) {
- print_error("%s %s\n", error_prefix,
--  "Invalid hostname: hostname can't have single quotes.");
-+  "Invalid hostname: hostname can't have single quotes.");
- return NULL;
-   }
- 
--  script = (char*) malloc(32 + strlen(url) + strlen(host));
-+  script = (char*) malloc(32 + strlen(sanitized_url) + strlen(host));
-   script[0] = '\0';
-   strcat(script, "FindProxyForURL('");
-   strcat(script, sanitized_url);
--- 
-2.30.2
-
diff --git a/debian/patches/fix-build-error-if-git-not-installed.patch b/debian/patches/fix-build-error-if-git-not-installed.patch
new file mode 100644
index 000..46146ec
--- /dev/null
+++ b/debian/patches/fix-build-error-if-git-not-installed.patch
@@ -0,0 +1,15 @@
+--- a/src/pymod/setup.py
 b/src/pymod/setup.py
+@@ -67,9 +67,9 @@
+   ))
+ 
+ def pacparser_version():
+-  if subprocess.call('git rev-parse --git-dir'.split(' '),
+- stderr=subprocess.DEVNULL) == 0:
+-return git_version()
++  #if subprocess.call('git rev-parse --git-dir'.split(' '),
++  # stderr=subprocess.DEVNULL) == 0:
++  #return git_version()
+ 
+   # Check if we have version.mk. It's added in the manual release tarball.
+   version_file = os.path.join(setup_dir(), '..', 'version.mk')
diff --git a/debian/patches/py3only.patch b/debian/patches/py3only.patch
index 6a74db7..0a96294 100644
--- a/debian/patches/py3only.patch
+++ b/debian/patches/py3only.patch
@@ -6,12 +6,10 @@ Origin: vendor
 Forwarded: not-needed
 Last-Update: 2020-03-02
 
-Index: pacparser-1.3.6/src/Makefile
-===
 pacparser-1.3.6.orig/src/Makefile
-+++ pacparser-1.3.6/src/Makefile
-@@ -58,7 +58,7 @@ endif
- CFLAGS = -g -DXP_UNIX -Wall -DVERSION=$(VERSION)
+--- a/src/Makefile
 b/src/Makefile
+@@ -63,7 +63,7 @@
+ MAINT_CFLAGS := -g -DXP_UNIX -Wall -DVERSION=$(VERSION)
  
  ifndef PYTHON
 -  PYTHON = python
@@ -19,10 +17,3 @@ Index: pacparser-1.3.6/src/Makefile
  endif
  
  # Spidermonkey library.
-@@ -134,5 +134,5 @@ install-pymod: pymod
- 
- clean:
-   rm -f $(LIBRARY_LINK) $(LIBRARY) libjs.a pacparser.o pactester pymod/pacparser_o_buildstamp jsapi_buildstamp
--  cd pymod && python setup.py clean --all
-+  cd pymod && $(PYTHON) setup.py clean --all
-   cd spidermonkey && $(MAKE) clean
diff --git a/debian/patches/series b/debian/patches/series
index 0ca96d5..0f0855b 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,2 @@
 py3only.patch
-0001-Fix-possible-memory-overwrite-vulnerability.-134.patch
+fix-build-error-if-git-not-installed.patch
diff --git a/debian/rules b/debian/rules
index 117ed7c..e27e3c3 

Bug#1042610: behave: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting

2023-12-12 Thread s3v
On Tue, 12 Dec 2023 13:15:27 +0100 s3v  wrote:
> On Tue, 12 Dec 2023 12:41:11 +0100 s3v  wrote:
> >> python3-doc needs to be added to B-D.
>
> It's false. The package builds fine even without that.
>
> Kind Regards and sorry for the noise.
>
>

That's embarrassing..
I was looking the other way and the other package... I didn't notice
python3-doc was already installed on my system.
He needs to be a build-dependency.

Sorry again



Bug#1054974: behave: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-12-12 Thread s3v
Dear Maintainer,

please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042610
for a proposed patch.

Kind Regards



Bug#1042610: behave: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting

2023-12-12 Thread s3v
On Tue, 12 Dec 2023 12:41:11 +0100 s3v  wrote:
>> python3-doc needs to be added to B-D.

It's false. The package builds fine even without that.

Kind Regards and sorry for the noise.



Bug#1042610: behave: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting

2023-12-12 Thread s3v
Dear Maintainer,

Please find attached a patch to fix this issue and the next one:

...
Running Sphinx v7.2.6
making output directory... done
loading intersphinx inventory from https://docs.python.org/3/objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://docs.python.org/3/objects.inv' not fetchable due 
to : 
HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded
with url: /3/objects.inv (Caused by ProxyError('Cannot connect to proxy.', 
NewConnectionError(': Failed to establish a new connection:
[Errno 111] Connection refused')))
building [mo]: targets for 0 po files that are out of date
writing output...
building [html]: targets for 26 source files that are out of date
updating environment: [new config] 26 added, 0 changed, 0 removed
reading sources... [100%] usecase_flask
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
copying assets... copying static files... done
copying extra files... done
done
writing output... [100%] usecase_flask
generating indices... genindex done
writing additional pages... search done
copying images... [100%] _static/behave_logo1.png
dumping search index in English (code: en)... done
dumping object inventory... done
build succeeded, 1 warning.

The HTML pages are in ../.pybuild/docs/html.
rm -rf /build/behave-1.2.6/.pybuild/docs/html/.doctrees
make[1]: Leaving directory '/build/behave-1.2.6'
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:310: cd 
/build/behave-1.2.6/.pybuild/cpython3_3.12_behave/build; python3.12 -m pytest 
tests
 test 
session starts 

platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0
rootdir: /build/behave-1.2.6/.pybuild/cpython3_3.12_behave/build
configfile: pytest.ini
collected 208 items / 1 error   
    

== 
ERRORS 
===
_ ERROR collecting 
tests/unit/test_behave4cmd_command_shell_proc.py 
_
ImportError while importing test module 
'/build/behave-1.2.6/.pybuild/cpython3_3.12_behave/build/tests/unit/test_behave4cmd_command_shell_proc.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.12/importlib/__init__.py:90: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/unit/test_behave4cmd_command_shell_proc.py:16: in 
    from behave4cmd0.command_shell_proc import \
E   ModuleNotFoundError: No module named 'behave4cmd0'
= warnings 
summary ==
behave/matchers.py:267
  
/build/behave-1.2.6/.pybuild/cpython3_3.12_behave/build/behave/matchers.py:267: 
SyntaxWarning: invalid escape sequence '\d'
    """Registers a custom type that will be available to "parse"

behave/formatter/ansi_escapes.py:57
  
/build/behave-1.2.6/.pybuild/cpython3_3.12_behave/build/behave/formatter/ansi_escapes.py:57:
 SyntaxWarning: invalid escape sequence '\['
    _ANSI_ESCAPE_PATTERN = re.compile(u"\x1b\[\d+[mA]", re.UNICODE)

tests/unit/test_behave4cmd_command_shell_proc.py:2
  
/build/behave-1.2.6/.pybuild/cpython3_3.12_behave/build/tests/unit/test_behave4cmd_command_shell_proc.py:2:
 SyntaxWarning: invalid escape sequence '\.'
    """

tests/unit/test_behave4cmd_command_shell_proc.py:26
  
/build/behave-1.2.6/.pybuild/cpython3_3.12_behave/build/tests/unit/test_behave4cmd_command_shell_proc.py:26:
 SyntaxWarning: invalid escape sequence '\w'
    winpath_pattern = 
u"^([A-Za-z]:(\\[\w\.\-]+)+)|((\\[\w\.\-]+)*)|(\s[\w\.\-]+([\w\.\-]+)*)$"

tests/unit/test_behave4cmd_command_shell_proc.py:64
  
/build/behave-1.2.6/.pybuild/cpython3_3.12_behave/build/tests/unit/test_behave4cmd_command_shell_proc.py:64:
 SyntaxWarning: invalid escape sequence '\s'
    '^\s*File "(?P.*)", line \d+, in ',

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
== short test 
summary info ==
ERROR tests/unit/test_behave4cmd_command_shell_proc.py
!! Interrupted: 1 error 
during collection !!!
=== 5 warnings, 1 
error in 0.25s 
E: pybuild pybuild:395: test: 

Bug#1055547: urwid fails one test with Python 3.12

2023-12-09 Thread s3v
Dear Maintainer,

debian/patches/0002-Drop-deprecated-asyncio.coroutine.patch needs to be
slightly modified according to [1][2].
After applying these changes (attached), I was able to build your
package in a sid chroot environment.

Kind Regards

[1] https://github.com/penguinolog/urwid/commit/b593cf7645b6b9b53779
[2] 
https://github.com/penguinolog/urwid/commit/e2bfb61842563ec9dbc5#diff-660ea81515f75cc66aabab01f0921d66405493eb3ca8e5341a9971149af413cbFrom: Jochen Sprickerhof 
Date: Fri, 18 Nov 2022 11:48:06 +0100
Subject: Drop deprecated @asyncio.coroutine

Removed in Python 3.11:

https://github.com/python/cpython/issues/87382
---
 urwid/tests/test_event_loops.py | 1 - 
 1 file changed, 1 deletion(-)

--- a/urwid/tests/test_event_loops.py
+++ b/urwid/tests/test_event_loops.py
@@ -204,10 +204,9 @@
 def test_coroutine_error(self):
 evl = self.evl
 
-@asyncio.coroutine
-def error_coro():
+async def error_coro():
 result = 1 / 0 # Simulate error in coroutine
-yield result
+return result
 
 asyncio.ensure_future(error_coro())
 self.assertRaises(ZeroDivisionError, evl.run)


Bug#1055728: segyio ftbfs with Python 3.12

2023-12-07 Thread s3v
Control: forwarded -1 
https://github.com/equinor/segyio/commit/c549b796ebf49aa2e1ef6cee5d9cb8d658a23c07.patch


Dear Maintainer,
After applying aforementioned patch from upstream, I was able
to build your package in a sid chroot environment.

Kind Regards



Bug#1057312: linuxcnc-doc-es hardcodes description in Spanish language

2023-12-02 Thread s3v
Package: src:linuxcnc
Version: 2.9.0~pre1+git20230208.f1270d6ed7-1

Dear Maintainer,

Please fix hardcoded translation in Spanish for the description of the
linuxcnc-doc-es binary package.
Currently the package description states:

 Description: controlador de movimiento para máquinas CNC y robots (Español).
  LinuxCNC es EMC (controlador de máquina mejorado) que proporciona
  control de movimiento para máquinas herramientas CNC (fresado,
  torneado, ruteado, etc.) y aplicaciones de robótica.
  .
  Este paquete contiene la documentación en español.

Hardcoding translation makes translation effort harder (or impossible) for
translators on DDTP [1] which should be used to accomplish this task.

References to DDTSS (translation interface) in Spanish and related mailing
list are [2][3].

Thanks for considering.

Kind Regards


[1] ddtp.debian.org
[2] https://ddtp.debian.org/ddtss/index.cgi/es
[3] https://lists.debian.org/debian-i18n/



Bug#1054729: errbot: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-11-23 Thread s3v
Dear Maintainer,

After moving conftest.py from package root to tests/ (as upstream did), your
package builds fine in a sid chroot environment and all tests pass as well.

Kind Regards



Bug#1054372: python3-django-macaddress: incompatible with python3-django in bookworm

2023-11-20 Thread s3v
Dear Maintainer,

After enabling tests during build (minimal settings.py is needed) and applying 
upstream commit [1][2],
I was able to build your package in a sid chroot environment and all test pass 
as well.

Kind Regards

[1] 
https://github.com/django-macaddress/django-macaddress/pull/41/commits/a722016312a97
[2] https://github.com/django-macaddress/django-macaddress/pull/44diff -Nru --exclude changelog django-macaddress-1.5.0/debian/control django-macaddress-1.5.0/debian/control
--- django-macaddress-1.5.0/debian/control  2022-04-25 01:57:12.0 +
+++ django-macaddress-1.5.0/debian/control  2023-11-20 08:16:34.0 +
@@ -7,6 +7,10 @@
  debhelper-compat (= 12),
  dh-python,
  python3-all,
+ python3-django,
+ python3-netaddr,
+ python3-pytest,
+ python3-pytest-django,
  python3-setuptools,
 Standards-Version: 4.5.0
 Vcs-Git: https://salsa.debian.org/python-team/packages/django-macaddress.git
diff -Nru --exclude changelog django-macaddress-1.5.0/debian/patches/newdjango.patch django-macaddress-1.5.0/debian/patches/newdjango.patch
--- django-macaddress-1.5.0/debian/patches/newdjango.patch  1970-01-01 00:00:00.0 +
+++ django-macaddress-1.5.0/debian/patches/newdjango.patch  2023-11-20 08:16:20.0 +
@@ -0,0 +1,24 @@
+--- /dev/null
 b/macaddress/tests/settings.py
+@@ -0,0 +1,10 @@
++INSTALLED_APPS = [
++'macaddress',
++]
++
++DATABASES = {
++'default': {
++'ENGINE': 'django.db.backends.sqlite3',
++'NAME': 'mydatabase',
++}
++}
+--- a/macaddress/formfields.py
 b/macaddress/formfields.py
+@@ -1,6 +1,6 @@
++from django.core.validators import EMPTY_VALUES
+ from django.forms import Field
+-from django.forms.fields import EMPTY_VALUES
+-from django.utils.translation import ugettext_lazy as _
++from django.utils.translation import gettext_lazy as _
+ #"From Django 1.8: The django.forms.util module has been renamed. Use django.forms.utils instead."
+ try:
+ from django.forms.utils import ValidationError
diff -Nru --exclude changelog django-macaddress-1.5.0/debian/patches/series django-macaddress-1.5.0/debian/patches/series
--- django-macaddress-1.5.0/debian/patches/series   1970-01-01 00:00:00.0 +
+++ django-macaddress-1.5.0/debian/patches/series   2023-11-20 08:14:54.0 +
@@ -0,0 +1 @@
+newdjango.patch
diff -Nru --exclude changelog django-macaddress-1.5.0/debian/rules django-macaddress-1.5.0/debian/rules
--- django-macaddress-1.5.0/debian/rules2022-04-25 01:57:12.0 +
+++ django-macaddress-1.5.0/debian/rules2023-11-20 08:13:26.0 +
@@ -5,8 +5,7 @@
 #export DH_VERBOSE=1
 
 export PYBUILD_NAME=django-macaddress
-
-override_dh_auto_test:
+export DJANGO_SETTINGS_MODULE=macaddress.tests.settings
 
 %:
dh $@  --with python3 --buildsystem=pybuild


Bug#1042611: openshot-qt: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting

2023-11-11 Thread s3v
Dear Maintainer,

This issue was fixed by openshot-qt/3.1.1+dfsg1-1 uploaded in sid on
October, 11th.
This is the relevant upstream commit [1] that was merged in openshot-qt
3.1.0 and newer versions.

buildd confirms that your package builds fine [2]

Kind Regards

[1] https://github.com/OpenShot/openshot-qt/commit/8ce7e216eac7081
[2] https://buildd.debian.org/status/package.php?p=openshot-qt



Bug#1042642: ns3: FTBFS with Sphinx 7.1, docutils 0.20: make[6]: *** [Makefile:75: html] Error 2

2023-11-06 Thread s3v
Dear Maintainer,

Problematic lines seem to be [1][2][3].
After fixing all of them, I was able to build successfully your package in
a sid chroot environment.

Kind Regards

[1] 
https://sources.debian.org/src/ns3/3.40-1/ns-3.40/doc/models/source/conf.py/#L68
[2] 
https://sources.debian.org/src/ns3/3.40-1/ns-3.40/doc/manual/source/conf.py/#L68
[3] 
https://sources.debian.org/src/ns3/3.40-1/ns-3.40/doc/tutorial/source/conf.py/#L66



Bug#1042642: ns3: FTBFS with Sphinx 7.1, docutils 0.20: make[6]: *** [Makefile:75: html] Error 2

2023-11-06 Thread s3v
On Mon, 6 Nov 2023 11:53:25 +0100 s3v  wrote:
> Dear Maintainer,
>
> This upstream commit [1] solved the issue for sphinx 7.2.5 and newer.
> Reported bug report is for sphinx 7.1.1 but actually sid has sphinx 7.2.6.
> Please see [2] for reference.
>
> Kind Regards
>
>
> [1] https://github.com/sphinx-doc/sphinx/commit/2a631f97ef7f4b0edc247
> [2] https://bugs.debian.org/1042597
>

Forget about that...
Copyright is in the form [1]:

| copyright = u'2006-2019'

and not in a 4 digit only form.
I can reproduce the issue with ns3/3.4.0 in a sid chroot environment on amd64.

...
epstopdf lena-radio-link-failure-one-enb.eps
rescale-pdf.sh lena-radio-link-failure-one-enb.pdf to 10cm
epstopdf lena-radio-link-failure-two-enb.eps
Running Sphinx v7.2.6
WARNING: Invalid configuration value found: 'language = None'. Update your 
configuration to a valid language code. Falling back to 'en' (English).
making output directory... done

Extension error (sphinx.config):
Handler  for event 
'config-inited' threw an exception (exception: ||string index out of range||)
make[6]: *** [Makefile:628: html] Error 2
Running Sphinx v7.2.6
WARNING: Invalid configuration value found: 'language = None'. Update your 
configuration to a valid language code. Falling back to 'en' (English).
making output directory... done

Extension error (sphinx.config):
Handler  for event 
'config-inited' threw an exception (exception: string index out of range)
make[6]: *** [Makefile:638: singlehtml] Error 2
Running Sphinx v7.2.6
WARNING: Invalid configuration value found: 'language = None'. Update your 
configuration to a valid language code. Falling back to 'en' (English).
making output directory... done

Extension error (sphinx.config):
Handler  for event 
'config-inited' threw an exception (exception: string index out of range)
make[6]: *** [Makefile:689: latexpdf] Error 2
...

Please see [2][3]

Roughly adding trailing whitespace:
 
 ||copyright = u'2006-2019 '

makes "string index out of range" exception disappear but docs still fail to 
build on
my chroot.

||Sorry for the noise.

Kind Regards


[1] 
https://sources.debian.org/src/ns3/3.40-1/ns-3.40/doc/models/source/conf.py/#L68
[2] https://sources.debian.org/src/sphinx/7.2.6-2/sphinx/config.py/#L449-L453
[3] 
https://www.sphinx-doc.org/en/master/usage/configuration.html#confval-copyright


|



Bug#1042642: ns3: FTBFS with Sphinx 7.1, docutils 0.20: make[6]: *** [Makefile:75: html] Error 2

2023-11-06 Thread s3v
Dear Maintainer,

This upstream commit [1] solved the issue for sphinx 7.2.5 and newer.
Reported bug report is for sphinx 7.1.1 but actually sid has sphinx 7.2.6.
Please see [2] for reference.

Kind Regards


[1] https://github.com/sphinx-doc/sphinx/commit/2a631f97ef7f4b0edc247
[2] https://bugs.debian.org/1042597



Bug#1042597: python-amqp: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:20: override_dh_sphinxdoc] Error 2

2023-11-05 Thread s3v
Dear Maintainer,

I can reproduce this issue with python3-sphinx 7.2.3-1 from snapshots.d.o
but not with python3-sphinx 7.2.6-1 just uploaded in sid.
I guess this upstream commit [1] fixed reported issue.

Anyway your package still FTBFS with this message:

Exception occurred:
  File "/usr/lib/python3/dist-packages/sphinx/ext/extlinks.py", line 112, in 
role
    title = caption % part

This is caused by sphinx-celery not compatible with newer Sphinx.
Please see this commit that fixes the problem [2]

Kind Regards

[1] https://github.com/sphinx-doc/sphinx/commit/2a631f97ef7f4b0edc247
[2] https://github.com/celery/sphinx_celery/commit/e2f88da7ad7c400dc5



Bug#1052852: python-django-crispy-forms: FTBFS: make[1]: *** [debian/rules:17: override_dh_auto_test] Error 1

2023-11-04 Thread s3v
Dear Maintainer

After applying this commit [1], I was able to build successfully your
package in a sid chroot environment.
I've also tried to build against sphinx 7.2.6-1 + python-docutils
0.20.1+dfsg-1 in experimental and no problems were spotted.

Kind Regards

[1] https://github.com/django-crispy-forms/django-crispy-forms/pull/1257



Bug#1055106: Test failure prevents Django 4.x from entering in testing

2023-10-31 Thread s3v
Package: src:django-tables
Version: 2.6.0-1
Severity: grave
Tags: patch


Dear Maintainer,
Tests fail on Debian CI infrastructure [1] and on my local machine as well
(full log attached).
This failure prevents python-django (3:4.2.6-1) from entering in testing [2].

$> autopkgtest --no-built-binaries django-tables_2.6.0-1.dsc -- null
...
...

ImportError: cannot import name 'url' from 'django.conf.urls' 
(/usr/lib/python3/dist-packages/django/conf/urls/__init__.py)
autopkgtest [14:12:24]: test test-run-py3: ---]
autopkgtest [14:12:24]: test test-run-py3:  - - - - - - - - - - results - - - - 
- - - - - -
test-run-py3 FAIL non-zero exit status 1
autopkgtest [14:12:24]:  summary
command1 PASS
test-run-py3 FAIL non-zero exit status 1


The root cause is that url() function was deprecated since Django 3.1 [3]
and removed in Django 4.x
Attached patch addresses the failure.

Kind Regards


[1] 
https://ci.debian.net/data/autopkgtest/unstable/amd64/d/django-tables/39070283/log.gz
[2] https://qa.debian.org/excuses.php?package=python-django
[3] https://code.djangoproject.com/ticket/31534--- django-tables-2.6.0/debian/tests/test-run-py3   2023-05-25 15:35:19.0 +
+++ django-tables-2.6.0/debian/tests/test-run-py3-new   2023-10-31 14:37:50.661433357 +
@@ -45,14 +45,14 @@
 
 
 cat > testproject/urls.py << __EOF__
-from django.conf.urls import url
+from django.urls import re_path
 from django.contrib import admin
 
 from tutorial.views import people
 
 urlpatterns = [
-url(r'^admin/', admin.site.urls),
-url(r'^people/', people)
+re_path(r'^admin/', admin.site.urls),
+re_path(r'^people/', people)
 ]
 __EOF__
 


full_log.tar.gz
Description: application/gzip


Bug#1052818: djangorestframework-filters: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-10-28 Thread s3v
Dear Maintainer,

> >   from django.conf.urls import include, url
> E   ImportError: cannot import name 'url' from 'django.conf.urls' 
> (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py)


Since Django 4.x, url() function was removed and replaced by "re_path". Attached
patch fix the build failure.

Kind regards--- a/tests/testapp/urls.py
+++ b/tests/testapp/urls.py
@@ -1,5 +1,5 @@
 
-from django.conf.urls import include, url
+from django.urls import include, re_path
 from rest_framework import routers
 
 from . import views
@@ -15,5 +15,5 @@
 
 
 urlpatterns = [
-url(r'^', include(router.urls)),
+re_path(r'^', include(router.urls)),
 ]
--- a/tests/perf/urls.py
+++ b/tests/perf/urls.py
@@ -1,5 +1,5 @@
 
-from django.conf.urls import include, url
+from django.urls import include, re_path
 from rest_framework import routers
 
 from . import views
@@ -10,5 +10,5 @@
 
 
 urlpatterns = [
-url(r'^', include(router.urls)),
+re_path(r'^', include(router.urls)),
 ]


Bug#1032982: python-braintree 3.x discontinued, please package 4.x version

2023-03-15 Thread s3v
Source: python-braintree
Vesion: 3.57.1-1
Severity: important


Dear Maintainer,

The 3.x branch of the Braintree Python library was discontinued since March, 
2023 [1]
I don't have an account for the service so I can't check that the package 
currently
works.
Given the importance of the money secure transactions, please consider to 
package
4.x version.

Kind Regards

[1] https://github.com/braintree/braintree_python



Bug#1032902: genx won't start: TypeError: Pen(): arguments did not match any overloaded call

2023-03-13 Thread s3v
Package: python3-genx
Version: 3.0.2-2
Severity: serious


Dear Maintainer,

Genx won't start in a sid VirtualBox VM:

#:> apt install python3-genx
#:> exit
$:> genx
Traceback (most recent call last):
  File "/usr/bin/genx", line 3, in 
    import sys, os, appdirs, argparse
ModuleNotFoundError: No module named 'appdirs'


#:> apt install python3-appdirs
#:> exit
$:> genx
Traceback (most recent call last):
  File "/usr/bin/genx", line 14, in 
    from genx import version, model
  File "/usr/lib/python3/dist-packages/genx/model.py", line 14, in 
    import numpy as np
ModuleNotFoundError: No module named 'numpy'


#:> apt install python3-numpy
#:> exit
$:> genx
Traceback (most recent call last):
  File "/usr/bin/genx", line 423, in 
    start_interactive(args)
  File "/usr/bin/genx", line 31, in start_interactive
    from genx import genx_gui
  File "/usr/lib/python3/dist-packages/genx/genx_gui.py", line 10, in 
    import wx
ModuleNotFoundError: No module named 'wx'


#:> apt install python3-wxgtk4.0
#:> exit
$:> genx
Traceback (most recent call last):
  File "/usr/bin/genx", line 423, in 
    start_interactive(args)
  File "/usr/bin/genx", line 31, in start_interactive
    from genx import genx_gui
  File "/usr/lib/python3/dist-packages/genx/genx_gui.py", line 20, in 
    from genx import data, model, help
  File "/usr/lib/python3/dist-packages/genx/help.py", line 10, in 
    from . import event_handlers as eh
  File "/usr/lib/python3/dist-packages/genx/event_handlers.py", line 21, in 

    from . import solvergui, help
  File "/usr/lib/python3/dist-packages/genx/solvergui.py", line 13, in 
    from . import filehandling as io
  File "/usr/lib/python3/dist-packages/genx/filehandling.py", line 17, in 

    import h5py
ModuleNotFoundError: No module named 'h5py'


#:> apt install python3-h5py
#:> exit
$:> genx
Traceback (most recent call last):
  File "/usr/bin/genx", line 423, in 
    start_interactive(args)
  File "/usr/bin/genx", line 31, in start_interactive
    from genx import genx_gui
  File "/usr/lib/python3/dist-packages/genx/genx_gui.py", line 22, in 
    from genx import plotpanel, solvergui, parametergrid, datalist
  File "/usr/lib/python3/dist-packages/genx/plotpanel.py", line 6, in 
    import matplotlib
ModuleNotFoundError: No module named 'matplotlib'


#:> apt install python3-matplotlib
#:> exit
$:> genx
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/genx/genx_gui.py", line 854, in OnInit
    main_frame = MainFrame(self, None, -1, "")
 ^
  File "/usr/lib/python3/dist-packages/genx/genx_gui.py", line 244, in __init__
    self.data_list = datalist.DataListControl(self.data_notebook_data, 
wx.ID_ANY, self.config, status_text)
 
^^
  File "/usr/lib/python3/dist-packages/genx/datalist.py", line 798, in __init__
    self.list_ctrl = VirtualDataList(self, self.data_cont, config=config, 
status_text=status_text)
 
^
  File "/usr/lib/python3/dist-packages/genx/datalist.py", line 301, in __init__
    self._UpdateImageList()
  File "/usr/lib/python3/dist-packages/genx/datalist.py", line 373, in 
_UpdateImageList
    bmp = self._CreateBmpIcon(sim_color, data_color)
  ^^
  File "/usr/lib/python3/dist-packages/genx/datalist.py", line 350, in 
_CreateBmpIcon
    dc.SetPen(wx.Pen(color_data,0.0))
  ^^
TypeError: Pen(): arguments did not match any overloaded call:
  overload 1: too many arguments
  overload 2: argument 1 has unexpected type 'tuple'
  overload 3: argument 2 has unexpected type 'float'
  overload 4: argument 1 has unexpected type 'tuple'
OnInit returned false, exiting...


I don't know if this error is caused by additional missing dependencies that
need to be installed.
Unfortunately missing dependency chain affects also bullseye.

Kind Regards



Bug#1027954: cppad: binary-all FTBFS

2023-03-11 Thread s3v
Dear Maintainer,

I think debian/libcppad-doc.docs needs to be adjusted to reflect changes in
documentation file names:

- doc.omh was renamed to doc.xrst [1] which was then renamed tocppad.xrst [2] 
which
  was then renamed to user_guide.xrst [3]

- omh directory was renamed to xrst [1]

Kind Regards

[1] 
https://github.com/coin-or/CppAD/commit/f054e4abb22551dd3685f95e587137f78a5c9504
[2] 
https://github.com/coin-or/CppAD/commit/278d8dbf63b42130f25acf03d5dbefdf6200a107
[3] 
https://github.com/coin-or/CppAD/commit/5a139ae40b5ee0bde2474a5fc0c17ead3365effb



Bug#919058: its-tools: crashes when freeing xmlDocs

2023-03-11 Thread s3v
Dear Maintainer,

This issue fixed in libxml2 seems to be related [1]

Kind Regards

[1] https://gitlab.gnome.org/GNOME/libxml2/-/issues/64



Bug#1032444: plastex: FTBFS: tests fail with Jinja2 3.1

2023-03-06 Thread s3v
Package: plastex
Version: 2.1-3
Severity: serious
Tags: ftbfs
Control: forwarded -1 https://github.com/plastex/plastex/commit/d5144e16fcae42

Dear Maintainer,

Your package FTBFS because tests fail [1].
Previous successful build [2] had this warning:


=== warnings summary ===
plasTeX/Renderers/PageTemplate/__init__.py:35
  
/<>/.pybuild/cpython3_3.9_plastex/build/plasTeX/Renderers/PageTemplate/__init__.py:35:
 DeprecationWarning: 'contextfunction' is renamed to 'pass_context', the old 
name will be removed
in Jinja 3.1.
    def debug(context):


After Jinja2 3.1 entered in unstable [3], this warning
became an error making tests fail.
I've built your package without errors in a sid chroot
environment after applying upstream commit.

Kind Regards

[1] 
https://ci.debian.net/data/autopkgtest/testing/amd64/p/plastex/31984634/log.gz
[2] 
https://buildd.debian.org/status/fetch.php?pkg=plastex=all=2.1-3=1651705538=0
[3] 
https://tracker.debian.org/news/1423360/accepted-jinja2-312-1-source-into-unstable/



Bug#1032392: python3-scikit-rf: import fails: AttributeError: module 'collections' has no attribute 'Sequence'

2023-03-05 Thread s3v
Package: python3-scikit-rf
Version: 0.15.4-2
Severity: serious

Dear Maintainer,

This import fails in a sid chroot:

Python 3.11.2 (main, Feb 12 2023, 00:48:52) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from skrf import Network
Traceback (most recent call last):
 File "", line 1, in 
 File "/usr/lib/python3/dist-packages/skrf/__init__.py", line 14, in 
   from . import frequency
 File "/usr/lib/python3/dist-packages/skrf/frequency.py", line 39, in 
   from .util import slice_domain,find_nearest_index
 File "/usr/lib/python3/dist-packages/skrf/util.py", line 289, in 
   class HomoList(collections.Sequence):
  
AttributeError: module 'collections' has no attribute 'Sequence'

Kind Regards



Bug#1032380: arriero: AttributeError: module 'collections' has no attribute 'MutableSet'

2023-03-05 Thread s3v
Package: arriero
Version: 0.7~20161228-1.1
Severity: serious


Dear Maintainer,

This command fails:

$:> arriero --help
/usr/lib/python3/dist-packages/arriero/version.py:35: FutureWarning: Possible 
nested set at position 14
 vendor_re = re.compile(r'\d(?P[[:alpha:]]*)?[1-9][0-9.~]*$')
Traceback (most recent call last):
 File "/usr/bin/arriero", line 33, in 
   sys.exit(load_entry_point('Arriero==0.7', 'console_scripts', 'arriero')())
^^
 File "/usr/bin/arriero", line 25, in importlib_load_entry_point
   return next(matches).load()
  
 File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 202, in load
   module = import_module(match.group('module'))

 File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
   return _bootstrap._gcd_import(name[level:], package, level)
  
 File "", line 1206, in _gcd_import
 File "", line 1178, in _find_and_load
 File "", line 1128, in _find_and_load_unlocked
 File "", line 241, in _call_with_frames_removed
 File "", line 1206, in _gcd_import
 File "", line 1178, in _find_and_load
 File "", line 1149, in _find_and_load_unlocked
 File "", line 690, in _load_unlocked
 File "", line 940, in exec_module
 File "", line 241, in _call_with_frames_removed
 File "/usr/lib/python3/dist-packages/arriero/__init__.py", line 4, in 
   from .arriero import Arriero, main
 File "/usr/lib/python3/dist-packages/arriero/arriero.py", line 32, in 
   from . import util
 File "/usr/lib/python3/dist-packages/arriero/util.py", line 188, in 
   class OrderedSet(deb822.OrderedSet, collections.MutableSet):
   ^^
AttributeError: module 'collections' has no attribute 'MutableSet'

"arriero {build, clone, exec, list, pull, push, ...} foo" also fails.


Kind Regards



Bug#1032125: zeitgeist - import fails: AttributeError: module 'inspect' has no attribute 'getargspec'

2023-02-28 Thread s3v
Dear Maintainer,

As side note, this error is catched by tests:

#:> apt install python3-dbus
#:> ln -s python zeitgeist
#:> make test-dbus
...
./test/dbus/run-all-tests.py
Traceback (most recent call last):
  File "/build/zeitgeist-1.0.4/./test/dbus/run-all-tests.py", line 42, in 

    from testutils import RemoteTestCase
  File "/build/zeitgeist-1.0.4/test/dbus/testutils.py", line 42, in 
    from zeitgeist.client import ZeitgeistDBusInterface, ZeitgeistClient, \
  File "/build/zeitgeist-1.0.4/./test/dbus/../../zeitgeist/client.py", line 
1100, in 
    _FIND_EVENTS_FOR_TEMPLATES_ARGS = inspect.getargspec(
  ^^
AttributeError: module 'inspect' has no attribute 'getargspec'. Did you mean: 
'getargs'?
make: *** [Makefile:984: test-dbus] Error 1

Soft link is "documented" in ./test/dbus/run-all-tests.py

 if not os.path.isdir("zeitgeist"):
 print("*** If you get unexpected failures, " \
 "you may want to run: `ln -s python zeitgeist`", 
file=sys.stderr)

Kind Regards



Bug#1032125: zeitgeist - import fails: AttributeError: module 'inspect' has no attribute 'getargspec'

2023-02-28 Thread s3v
Package: zeitgeist
Version: 1.0.4-4
Severity: serious
Control: forwarded -1 
https://gitlab.freedesktop.org/zeitgeist/zeitgeist/-/issues/26

Dear Maintainer,

This import fails:

Python 3.11.2 (main, Feb 12 2023, 00:48:52) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from zeitgeist import client
Traceback (most recent call last):
 File "", line 1, in 
 File "/usr/lib/python3/dist-packages/zeitgeist/client.py", line 1100, in 

   _FIND_EVENTS_FOR_TEMPLATES_ARGS = inspect.getargspec(
 ^^
AttributeError: module 'inspect' has no attribute 'getargspec'. Did you mean: 
'getargs'?
>>>

After applying upstream commit:

Python 3.11.2 (main, Feb 12 2023, 00:48:52) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from zeitgeist import client
>>>


Kind Regards



Bug#1031974: python3-pydle: import fails: AttributeError: module 'asyncio' has no attribute 'coroutine'

2023-02-25 Thread s3v
Package: python3-pydle
Version: 0.9.4
Severity: serious

Dear Maintainer,

This import fails in a Sid chroot:

Python 3.11.2 (main, Feb 12 2023, 00:48:52) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pydle
Traceback (most recent call last):
  File "", line 1, in 
  File "/build/pydle-0.9.4/pydle/__init__.py", line 1, in 
    from . import connection, protocol, client, features
  File "/build/pydle-0.9.4/pydle/features/__init__.py", line 1, in 
    from . import rfc1459, account, ctcp, tls, isupport, whox, ircv3
  File "/build/pydle-0.9.4/pydle/features/account.py", line 6, in 
    class AccountSupport(rfc1459.RFC1459Support):
  File "/build/pydle-0.9.4/pydle/features/account.py", line 25, in 
AccountSupport
    @asyncio.coroutine
 ^
AttributeError: module 'asyncio' has no attribute 'coroutine'. Did you mean: 
'coroutines'?
>>>

Kind Regards



Bug#1031832: python3-vispy: import fails: AttributeError: module 'numpy' has no attribute 'bool'

2023-02-23 Thread s3v
Package: python3-vispy
Severity: serious


Dear Maintainer,

This import fails in a Sid chroot:

>>> from vispy.plot import Fig
/usr/lib/python3/dist-packages/vispy/gloo/program.py:113: FutureWarning: In the 
future `np.bool` will be defined as the corresponding NumPy scalar.
 'bvec2':    (np.bool,    2),
Traceback (most recent call last):
 File "", line 1, in 
 File "/usr/lib/python3/dist-packages/vispy/plot/__init__.py", line 34, in 

   from .fig import Fig  # noqa
   
 File "/usr/lib/python3/dist-packages/vispy/plot/fig.py", line 5, in 
   from ..scene import SceneCanvas
 File "/usr/lib/python3/dist-packages/vispy/scene/__init__.py", line 33, in 

   from .visuals import *  # noqa
   ^^
 File "/usr/lib/python3/dist-packages/vispy/scene/visuals.py", line 18, in 

   from .. import visuals
 File "/usr/lib/python3/dist-packages/vispy/visuals/__init__.py", line 14, in 

   from .axis import AxisVisual  # noqa
   
 File "/usr/lib/python3/dist-packages/vispy/visuals/axis.py", line 11, in 

   from .visual import CompoundVisual
 File "/usr/lib/python3/dist-packages/vispy/visuals/visual.py", line 90, in 

   from .. import gloo
 File "/usr/lib/python3/dist-packages/vispy/gloo/__init__.py", line 54, in 

   from .program import Program  # noqa
   
 File "/usr/lib/python3/dist-packages/vispy/gloo/program.py", line 74, in 

   class Program(GLObject):
 File "/usr/lib/python3/dist-packages/vispy/gloo/program.py", line 113, in 
Program
   'bvec2':    (np.bool,    2),
^^^
 File "/usr/lib/python3/dist-packages/numpy/__init__.py", line 305, in 
__getattr__
   raise AttributeError(__former_attrs__[attr])
AttributeError: module 'numpy' has no attribute 'bool'.
`np.bool` was a deprecated alias for the builtin `bool`. To avoid this error in 
existing code, use `bool` by itself. Doing this will not modify any behavior
and is safe. If you specifically wanted the numpy scalar type, use `np.bool_` 
here.
The aliases was originally deprecated in NumPy 1.20; for more details and 
guidance see the original release note at:
   https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations. Did you 
mean: 'bool_'?

Kind Regards



Bug#1031767: python-ooolib: FTBFS: dh_clean: error: Compatibility levels before 7 are no longer supported (level 5 requested)

2023-02-22 Thread s3v
Source: python-ooolib
Version: 0.0.22
Severity: important


Dear Maintainer,

I've tried to build your package in a sid chroot environment but I failed:

dpkg-buildpackage: info: source package python-ooolib
dpkg-buildpackage: info: source version 0.0.22-5
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Rene Engelhard 
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build .
 debian/rules clean
dh_testdir
dh_testroot
rm -rf build
rm -rf ooolib/__pycache__
rm -f build-stamp configure-stamp
dh_clean
dh_clean: error: Compatibility levels before 7 are no longer supported (level 5 
requested)
make: *** [debian/rules:30: clean] Error 255
dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2

caused by unsupported compatibility level requested via debian/compat file.

Kind Regards



Bug#1028743: python-bottle: FTBFS: AssertionError: b'OK' != "URLError(ConnectionRefusedError(111, 'Connection refused'))"

2023-02-19 Thread s3v
Dear Maintainer,

On Fri, 27 Jan 2023 21:44:04 +0100 s3v  wrote:
> Dear Maintainer,
>
> After adding:
>
>  override_dh_auto_test:
>    http_proxy='' dh_auto_test
>
> in debian/rules to allow internal server to work during tests, new test
> starting fail:
>
> ---
>
> ==
> FAIL: test_invalid (test.test_sendfile.TestSendFile.test_invalid)
> SendFile: Invalid requests
> --
> Traceback (most recent call last):
>   File "/root/build/python-bottle-0.12.23/test/test_sendfile.py", line 56, in 
>test_invalid
> self.assertEqual(403, static_file(fn, root='/').status_code)
> AssertionError: 403 != 200
>
> --
> Ran 333 tests in 4.737s
>
> FAILED (failures=1, skipped=1)
> ERROR: InvocationError for command 
> /root/build/python-bottle-0.12.23/.tox/py311/bin/python -m unittest discover 
> (exited with code 1)
>
> -
>
> After removing:
>
>    try:
>    fp, fn = tempfile.mkstemp()
>    os.chmod(fn, 0)
>    self.assertEqual(403, static_file(fn, root='/').status_code)
>    finally:
>    os.close(fp)
>    os.unlink(fn)
>
> in test/test_sendfile.py, all tests pass.
> Please note that aforementioned lines was removed upstream in master
> branch but I cannot identify the relative commit (this happened sometime
> between 2016 and 2018).
> Hope this helps.
>


Failing test is my fault. I did the building process as root... :|
All tests pass after building as normal user.

Kind Regards



Bug#1030906: taurus-pyqtgraph: FTBFS (failing tests)

2023-02-19 Thread s3v
Dear Maintainer,

taurus_pyqtgraph does not seem Qt6-ready. After forcing Qt5 API in pytest.ini 
[1], this error appears:


 test 
session starts 

platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack
PyQt5 5.15.9 -- Qt runtime 5.15.8 -- Qt compiled 5.15.8
rootdir: /home/s3v/taurus-pyqtgraph-0.5.9, configfile: pytest.ini
plugins: xvfb-2.0.0, qt-4.2.0+repack
collected 42 items  
    

tests/test_curveproperties.py ..
  [  4%]
tests/test_dateaxisitem.py F
  [ 45%]
tests/test_plot.py .
  [ 66%]
tests/test_taurus_pyqtgraph.py ..   
  [ 71%]
tests/test_trend.py F   
  [ 83%]
tests/test_util.py ..   
  [ 97%]
tests/test_y2axis.py .  
  [100%]

...
...
...

== short test 
summary info ==
FAILED tests/test_dateaxisitem.py::test_tickValues[val_range0-expected0] - 
AttributeError: 'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_dateaxisitem.py::test_tickValues[val_range1-expected1] - 
AttributeError: 'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_dateaxisitem.py::test_tickValues[val_range2-expected2] - 
AttributeError: 'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_dateaxisitem.py::test_tickValues[val_range3-expected3] - 
AttributeError: 'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_dateaxisitem.py::test_tickValues[val_range4-expected4] - 
AttributeError: 'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_dateaxisitem.py::test_tickValues[val_range5-expected5] - 
AttributeError: 'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_dateaxisitem.py::test_tickValues[val_range6-expected6] - 
AttributeError: 'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_dateaxisitem.py::test_tickValues[val_range7-expected7] - 
AttributeError: 'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_dateaxisitem.py::test_tickValues_overflow - AttributeError: 
'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_dateaxisitem.py::test_tickStrings[values0-expected0] - 
AttributeError: 'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_dateaxisitem.py::test_tickStrings[values1-expected1] - 
AttributeError: 'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_dateaxisitem.py::test_tickStrings[values2-expected2] - 
AttributeError: 'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_dateaxisitem.py::test_tickStrings[values3-expected3] - 
AttributeError: 'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_dateaxisitem.py::test_tickStrings[values4-expected4] - 
AttributeError: 'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_dateaxisitem.py::test_tickStrings_english[values0-expected0] 
- AttributeError: 'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_dateaxisitem.py::test_tickStrings_english[values1-expected1] 
- AttributeError: 'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_dateaxisitem.py::test_tickStrings_english[values2-expected2] 
- AttributeError: 'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_trend.py::test_trend_model_setting - AttributeError: 
'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_trend.py::test_modelchooser_config - AttributeError: 
'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_trend.py::test_curveproperties_configfile - AttributeError: 
'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests/test_trend.py::test_multiple_setModel - AttributeError: 
'WidgetGroup' object has no attribute 'setMaximumWidth'
FAILED tests

Bug#1028664: colord: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 3 returned exit code 1

2023-02-18 Thread s3v
Control: forwarded -1 https://github.com/mm2/Little-CMS/commit/93629504f817
thanks


Dear Maintainer,

After applying aforementioned commit, I was able to build your
package in a sid chroot environment. colord also builds without
errors and all tests pass.

Kind Regards



Bug#1030464: aiomysql: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 'unknown'

2023-02-17 Thread s3v
Dear Maintainer,

After adding python3-setuptools-scm to build depends, I was able to
build your package in a sid chroot environment.
Please note that the build creates a "aiomysql/_scm_version.py" file
which prevents the next build:


...
dpkg-source: info: using options from aiomysql-0.1.1/debian/source/options: 
--extend-diff-ignore=^[^/]*[.]egg-info/
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building aiomysql using existing ./aiomysql_0.1.1.orig.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: warning: ignoring deletion of file docs/make.bat, use 
--include-removal to override
dpkg-source: info: local changes detected, the modified files are:
 aiomysql-0.1.1/aiomysql/_scm_version.py
dpkg-source: info: Hint: make sure the version in debian/changelog matches the 
unpacked source tree
dpkg-source: info: you can integrate the local changes with dpkg-source --commit
dpkg-source: error: aborting due to unexpected upstream changes, see 
/tmp/aiomysql_0.1.1-3.diff.1zsVoB
dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2


To avoid this, I think the removal needs to be added to the other cleanups in 
debian/rules.

Kind Regards



Bug#1030174: iminuit FTBFS with scipy 1.10

2023-02-09 Thread s3v
Dear Maintainer,

Since debian/watch points to https://pypi.debian.net/iminuit, I've
packaged iminuit-2.18.0.tar.gz without issues (build is ok and all
tests pass).
I've also dropped longdouble.patch introduced to fix [1] (I'm not
able to make a build on i386 arch).

Kind Regards


[1] https://github.com/scikit-hep/iminuit/issues/753



Bug#1030175: libgetdata: FTBFS: dh_install: error: missing files, aborting

2023-02-05 Thread s3v
Dear Maintainer,

> dh_install: warning: Cannot find (any matches for) 
> "usr/local/lib/python3.10/dist-packages/*" (tried in ., debian/tmp)
>
> dh_install: warning: python3-pygetdata missing files: 
> usr/local/lib/python3.10/dist-packages/*
> dh_install: error: missing files, aborting
> make: *** [debian/rules:28: binary-arch] Error 25

this is caused by a reference to python 3.10 in this file [1]

Kind Regards

[1] 
https://sources.debian.org/src/libgetdata/0.11.0-5/debian/python3-pygetdata.install/



Bug#1028728: deap: FTBFS: AssertionError: CMA algorithm did not converged properly.

2023-02-04 Thread s3v
Control: forwarded -1 
https://github.com/DEAP/deap/commit/0453060f6d9fce4e712f0f3479733118b2655bb4
thanks

Dear Maintainer,

> ==
> ERROR: deap.tests.test_algorithms.test_nsga3
> --
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
> self.test(*self.arg)
>   File 
>"/<>/.pybuild/cpython3_3.10_deap/build/deap/tests/test_algorithms.py",
> line 213, in test_nsga3
> pop = toolbox.select(pop, len(pop))
>   File 
>"/<>/.pybuild/cpython3_3.10_deap/build/deap/tools/emo.py", line 
>554, in selNSGA3
> selected = niching(pareto_fronts[-1], n, niches[sel_count:], 
>dist[sel_count:], niche_counts)
>   File 
>"/<>/.pybuild/cpython3_3.10_deap/build/deap/tools/emo.py", line 
>624, in niching
> available = numpy.ones(len(individuals), dtype=numpy.bool)
>   File "/usr/lib/python3/dist-packages/numpy/__init__.py", line 284, in 
>__getattr__
> raise AttributeError("module {!r} has no attribute "
> AttributeError: module 'numpy' has no attribute 'bool'
>
> --
> Ran 27 tests in 0.754s
>
> FAILED (errors=1)

This issue was fixed upstream and I can confirm the build is fine and all
test pass after applying aforementioned commit.

Kind Regards



Bug#1026514: python-param: FTBFS: TypeError: The only supported seed types are: None,

2023-02-03 Thread s3v
Hi,

I've successfully rebuilt python3-param/1.12.3 with 
python3-pkg-resources/5.6.3-1 and
python3-setuptools/65.6.3-1 from snapshot.d.o [1]
I don't know this is a regression in setuptools (recently uploaded [2]) or a 
bug in the
package itself.

Thanks for your work in Debian.

Kind Regards

[1] https://snapshot.debian.org/package/setuptools/65.6.3-1/
[2] 
https://tracker.debian.org/news/1413979/accepted-setuptools-6611-1-source-into-unstable/



Bug#1028779: buildbot: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 --system=custom "--test-args=PYTHONPATH=pkg:{destdir}/{install_dir} PATH=\$PATH:{destdir}/usr/bin trial3 --

2023-02-01 Thread s3v
Dear maintainer,

Please find attached a patch to avoid deprecation warnings
causing tests to fail.

Kind Regards--- a/master/buildbot/test/__init__.py
+++ b/master/buildbot/test/__init__.py
@@ -143,3 +143,35 @@
 # use. See https://github.com/boto/botocore/issues/2744
 warnings.filterwarnings('ignore', ".*'urllib3.contrib.pyopenssl' module is deprecated",
 category=DeprecationWarning)
+
+warnings.filterwarnings(
+action="ignore",
+category=DeprecationWarning,
+message=(
+".*Deprecated API features detected! "
+"These feature\(s\) are not compatible with SQLAlchemy 2\.0"
+)
+)
+
+# locale.getdefaultlocale() is deprecated since Python 3.11
+warnings.filterwarnings(
+action='ignore',
+category=DeprecationWarning,
+message=".*Use setlocale\(\), getencoding\(\) and getlocale\(\) instead"
+)
+
+warnings.filterwarnings(
+action="ignore",
+category=DeprecationWarning,
+message=(
+".*twisted\.web\.resource\.NoResource was deprecated in Twisted NEXT: "
+"Use twisted\.web\.pages\.notFound instead, which properly escapes HTML"
+)
+)
+
+# "pipes" module is deprecated since Python 3.11
+warnings.filterwarnings(
+action="ignore",
+category=DeprecationWarning,
+message=".*'pipes' is deprecated and slated for removal in Python 3\.13"
+)


Bug#1028743: python-bottle: FTBFS: AssertionError: b'OK' != "URLError(ConnectionRefusedError(111, 'Connection refused'))"

2023-01-27 Thread s3v
Dear Maintainer,

After adding:

 override_dh_auto_test:
   http_proxy='' dh_auto_test

in debian/rules to allow internal server to work during tests, new test
starting fail:

---

==
FAIL: test_invalid (test.test_sendfile.TestSendFile.test_invalid)
SendFile: Invalid requests
--
Traceback (most recent call last):
  File "/root/build/python-bottle-0.12.23/test/test_sendfile.py", line 56, in 
test_invalid
    self.assertEqual(403, static_file(fn, root='/').status_code)
AssertionError: 403 != 200

--
Ran 333 tests in 4.737s

FAILED (failures=1, skipped=1)
ERROR: InvocationError for command 
/root/build/python-bottle-0.12.23/.tox/py311/bin/python -m unittest discover 
(exited with code 1)

-

After removing:

   try:
   fp, fn = tempfile.mkstemp()
   os.chmod(fn, 0)
   self.assertEqual(403, static_file(fn, root='/').status_code)
   finally:
   os.close(fp)
   os.unlink(fn)

in test/test_sendfile.py, all tests pass.
Please note that aforementioned lines was removed upstream in master
branch but I cannot identify the relative commit (this happened sometime
between 2016 and 2018).
Hope this helps.

Kind Regards



Bug#1028837: python-zstandard 0.19.0-1 possibly no more compatible with python3.10

2023-01-23 Thread s3v
On Mon, 23 Jan 2023 19:06:01 +0100 s3v  wrote:

>
> exceptiongroup module has been packaged in Debian [1]

Sorry for the mess, there is the link:

https://tracker.debian.org/pkg/python-exceptiongroup



Bug#1028837: python-zstandard 0.19.0-1 possibly no more compatible with python3.10

2023-01-23 Thread s3v
Hi,

On Sat, 21 Jan 2023 17:49:33 +0100 =?utf-8?Q?=C3=89tienne?= Mollier 
 wrote:
> Hello from Debian Med Sprint, I had a look at this bug because
> it flagged at least augur for autoremoval.
>
> The module caught by this exception looks to be only supported
> in python3.11:
> >> ModuleNotFoundError: No module named 'exceptiongroup'
>
> When searching for this module, there seems to be a backport
> available for older python3 versions[1], but it does not seem to
> be available in Debian yet. Easier fix might be to build only
> for the default python3 for the time being. I tried limiting
> the build dependencies to python3-dev and it "fixed" the test
> failure for me. I'm considering doing a team upload in hope
> this helps.
>
> [1]: https://pypi.org/project/exceptiongroup/
>
> Have a nice day, :)
> --
> Étienne Mollier 
> Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da
> Sent from my alarm clock.

exceptiongroup module has been packaged in Debian [1]
This missing leads rdeps tests to fail for Python 3.10, I guess.

Thanks for your work.

Kind Regards.

[1] https://tracker.debian.org/pkg/python-zstandard



Bug#1027198: einsteinpy: autopkgtest fail with numpy/1.24.1

2023-01-22 Thread s3v
Control: forwarded -1 
https://github.com/einsteinpy/einsteinpy/commit/cffc0cacd053481e56
thanks


Dear Maintainer,

FTBFS is caused by two test failing with numpy 1.24


=== FAILURES ===
__ test_fractal_shows_figure ___

mock_stdout = <_io.StringIO object at 0x7fc084fb1d80>
mock_show = 

   @mock.patch.object(go.Figure, "show")
   @mock.patch("sys.stdout", new_callable=StringIO)
   def test_fractal_shows_figure(mock_stdout, mock_show):
>   fig = fractal(divs=2, show=True)

einsteinpy/tests/test_plotting/test_fractal.py:12:  
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
 
einsteinpy/plotting/fractal.py:75: in fractal
   go.Heatmap(z=_fractal_img(angle=step, dims=(400, 400)), showscale=False)
einsteinpy/plotting/fractal.py:40: in _fractal_img
   _julia(A, c, zabs_max, i, j, dims, x_range, y_range, iter_max)
einsteinpy/plotting/fractal.py:20: in _julia
   z = np.complex((i / width) * xwidth + xmin + 1j * ((j / height) * ywidth + 
ymin))
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
 

attr = 'complex'

   def __getattr__(attr):
   # Warn for expired attributes, and return a dummy function
   # that always raises an exception.
   import warnings
   try:
   msg = __expired_functions__[attr]
   except KeyError:
   pass
   else:
   warnings.warn(msg, DeprecationWarning, stacklevel=2)

   def _expired(*args, **kwds):
   raise RuntimeError(msg)

   return _expired

   # Emit warnings for deprecated attributes
   try:
   val, msg = __deprecated_attrs__[attr]
   except KeyError:
   pass
   else:
   warnings.warn(msg, DeprecationWarning, stacklevel=2)
   return val

   if attr in __future_scalars__:
   # And future warnings for those that will change, but also give
   # the AttributeError
   warnings.warn(
   f"In the future `np.{attr}` will be defined as the "
   "corresponding NumPy scalar.  (This may have returned Python "
   "scalars in past versions.", FutureWarning, stacklevel=2)

   # Importing Tester requires importing all of UnitTest which is not a
   # cheap import Since it is mainly used in test suits, we lazy import it
   # here to save on the order of 10 ms of import time for most users
   #
   # The previous way Tester was imported also had a side effect of adding
   # the full `numpy.testing` namespace
   if attr == 'testing':
   import numpy.testing as testing
   return testing
   elif attr == 'Tester':
   from .testing import Tester
   return Tester

>   raise AttributeError("module {!r} has no attribute "
"{!r}".format(__name__, attr))
E   AttributeError: module 'numpy' has no attribute 'complex'

/usr/lib/python3/dist-packages/numpy/__init__.py:284: AttributeError
__ test_fractal_draws_figure ___

   def test_fractal_draws_figure():
>   fig = fractal(divs=2, show=False)

einsteinpy/tests/test_plotting/test_fractal.py:18:  
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
 
einsteinpy/plotting/fractal.py:75: in fractal
   go.Heatmap(z=_fractal_img(angle=step, dims=(400, 400)), showscale=False)
einsteinpy/plotting/fractal.py:40: in _fractal_img
   _julia(A, c, zabs_max, i, j, dims, x_range, y_range, iter_max)
einsteinpy/plotting/fractal.py:20: in _julia
   z = np.complex((i / width) * xwidth + xmin + 1j * ((j / height) * ywidth + 
ymin))
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
 

attr = 'complex'

   def __getattr__(attr):
   # Warn for expired attributes, and return a dummy function
   # that always raises an exception.
   import warnings
   try:
   msg = __expired_functions__[attr]
   except KeyError:
   pass
   else:
   warnings.warn(msg, DeprecationWarning, stacklevel=2)

   def _expired(*args, **kwds):
   raise RuntimeError(msg)

   return _expired

   # Emit warnings for deprecated attributes
   try:
   val, msg = __deprecated_attrs__[attr]
   except KeyError:
   pass
   else:
   warnings.warn(msg, DeprecationWarning, stacklevel=2)
   return val

   if attr in __future_scalars__:
   # And future warnings for those that will change, but also give
   # the AttributeError
   warnings.warn(
   f"In the future `np.{attr}` will be defined as the "
   "corresponding NumPy scalar.  (This may have returned Python "
   "scalars in past versions.", FutureWarning, stacklevel=2)

   # 

Bug#1026514: python-param: FTBFS: TypeError: The only supported seed types are: None,

2023-01-21 Thread s3v
Dear Maintainer,

After applying [1][2], I was able to build your package
in a sid chroot environment and all tests pass.

Kind Regards

[1] https://github.com/holoviz/param/pull/521/commits/356da9d
[2] https://github.com/holoviz/param/commit/2958f6327ad3a5222



Bug#1028750: python-makefun: FTBFS: make: *** [debian/rules:4: clean] Error 25

2023-01-19 Thread s3v
Dear Maintainer,

setuptools-scm added dependency on python3-tomli and your package builds
fine now in a sid chroot environment [1]


> setuptools-scm (7.1.0-2) unstable; urgency=medium
>
>   * Add an explicit Depends on python3-tomli, required while Python 3.10 is a
>     supported version. (Closes: #1027947)
>
>  -- Stefano Rivera   Sat, 14 Jan 2023 12:13:09 -0400


Kind Regards

[1] https://tracker.debian.org/media/packages/s/setuptools-scm/changelog-7.1.0-2



Bug#1028447: cdist: unusable with python 3.11

2023-01-15 Thread s3v
Dear Maintainer,

On Tue, 10 Jan 2023 21:45:19 -0800 Steve Langasek 
 wrote:

> It looks like this is easily fixable without regression by removing the
> first assignment to parser['scan'], but this seems like such an obvious bug
> that I don't know if I'm missing something with historical behavior of
> argparse handling multiple assignments?
>
> Anyway, this package has no maintainer and upstream has not fixed this, and
> there are no reverse-dependencies, so I would suggest the package should
> just be removed.
 
Unless I missed something, upstream fixed this issue in [1]
After applying this commit, I was able to build cdist in a sid
chroot environment.

Kind Regards

[1] https://code.ungleich.ch/ungleich-public/cdist/commit/b974969f28f4



Bug#1028826: herbstluftwm: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

2023-01-15 Thread s3v
Dear Maintainer,

Please see below the output of this command:

> cd obj-x86_64-linux-gnu
> PYTHONPATH=../python python3 -m pytest -x --pdb ../tests/test_rules.py

...

 test 
session starts 

platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack
rootdir: /build/herbstluftwm-0.9.5, configfile: tox.ini
plugins: xvfb-2.0.0, xdist-3.1.0
collected 193 items 
    

../tests/test_rules.py 
..
 [ 65%]
F
>> captured 
>> stdout 
>> >>
Running: Xvfb -nolisten tcp -screen 0 800x600x24 -noreset +extension RENDER 
-displayfd 19
Xvfb is using the display ":2"
hlwm started
Client command ['move_monitor', '', '500x520'] succeeded (no output)
Client command ['rule', 'floatplacement=smart', 'floating=on'] succeeded (no 
output)
>> captured 
>> stderr 
>> >>
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
EWMH: 0 desktops:
0 managed clients:
./src/xconnection.cpp: 227: compositing manager = 0
> traceback
>  
> >

hlwm = , x11 = , invisible_tag = False

    @pytest.mark.exclude_from_coverage(
    reason='This test does not verify functionality but only whether \
    creating lots of windows can be handled by the algorithm')
    @pytest.mark.parametrize('invisible_tag', [False, True])
    def test_floatplacement_smart_create_many(hlwm, x11, invisible_tag):
    hlwm.call('move_monitor "" 500x520')
    if invisible_tag:
    hlwm.call('add invisible_tag')
    hlwm.call('rule tag=invisible_tag')
    hlwm.call('rule floatplacement=smart floating=on')
    
    # create many clients with different sizes
    def index2geometry(i):
    # vary between 2 different widths and 3 different
    # heights to get a lot of combinations
    return (30, 40, (i % 2) * 110, (i % 3) * 120)
    
    for i in range(0, 50):
>   x11.create_client(geometry=index2geometry(i))

../tests/test_rules.py:867:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
../tests/conftest.py:822: in create_client
    self.display.sync()
/usr/lib/python3/dist-packages/Xlib/display.py:182: in sync
    self.get_pointer_control()
/usr/lib/python3/dist-packages/Xlib/display.py:833: in get_pointer_control
    return request.GetPointerControl(display = self.display)
/usr/lib/python3/dist-packages/Xlib/protocol/rq.py:1368: in __init__
    self.reply()
/usr/lib/python3/dist-packages/Xlib/protocol/rq.py:1380: in reply
    self._display.send_and_recv(request = self._serial)
/usr/lib/python3/dist-packages/Xlib/protocol/display.py:612: in send_and_recv
    gotreq = self.parse_response(request)
/usr/lib/python3/dist-packages/Xlib/protocol/display.py:719: in parse_response
    gotreq = self.parse_error_response(request) or gotreq
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = , request = 20

    def parse_error_response(self, request):
    # Code is second byte
    code = indexbytes(self.data_recv, 1)
    
    # Fetch error class
    estruct = self.error_classes.get(code, error.XError)
    
    e = estruct(self, self.data_recv[:32])
    self.data_recv = bytesview(self.data_recv, 32)
    
    # print 'recv Error:', e
    
>   req = self.get_waiting_request(e.sequence_number)
E   AttributeError: 'BadRRModeError' object has no attribute 
'sequence_number'


Bug#1028585: Wrong description for kernelshark

2023-01-13 Thread s3v
Source: kernelshark


Dear Maintainer,

I think description for kernelshark needs to be changed.
It currently states:

Description: Utility for retrieving and analyzing function tracing in the kernel
 This package contains the trace-cmd utility. Trace-cmd makes it easy to
 retrieve and analyze function traces from the Linux kernel while it is running.

as trace-cmd description does.

Kind Regards



Bug#1026711: libnvme: FTBFS: dh_install: error: missing files, aborting

2023-01-03 Thread s3v
Dear Maintainer,

This bug was fixed in meson/1.0.0-1.1 [1] and I've just checked that
your package builds fine in a sid chroot environment.

Kind Regards


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026312



Bug#1026602: python-unicodecsv: FTBFS: AssertionError: [['ab\x00c']] != None

2023-01-01 Thread s3v
Dear Maintainer,

Starting from python 3.11, csv module is able to handle
null characters [1].
I think is safe to drop the failing test as upstream did
for python 3.11 (if this version will be the default in
bookworm).

Kind Regards and Happy new Year :)

[1] https://github.com/python/cpython/commit/b454e8e4df73bc73



Bug#1026739: pytest-bdd: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" --system=custom "--test-args={interpreter} -m pytest -k 'not test_generate_with_quot

2023-01-01 Thread s3v
Dear Maintainer,

I think this is a bug in python3-glob2 that affects pytest-bdd.
After applying this commit [1], I was able to build your package
in a sid chroot environment against fixed python3-glob2.

Kind Regards

[1] https://github.com/miracle2k/python-glob2/commit/be6981ec1a3ec089a9



Bug#1026729: RC Bug #1026729: Forwarded to upstream PR

2022-12-31 Thread s3v
forwarded 1026729 https://github.com/opentracing/opentracing-python/pull/159
thanks



Bug#1026499: rows: FTBFS: AssertionError: Lists differ: [] != ['iso', '8859']

2022-12-29 Thread s3v
Dear Maintainer,

After adding python3-magic to B-D (and d/t/control Depends), your package
builds fine in my sid chroot environment.

Kind Regards



Bug#1026741: python-xsdata: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13

2022-12-26 Thread s3v
Control: forwarded -1 https://github.com/tefra/xsdata/commit/775be731
thanks

Dear Maintainer,
this is a bug in Python 3.11.1 that was fixed and backported to 3.11.2
(but not released yet).
Upstream skipped problematic test for the time being.

Kind Regards.

[1] 
https://github.com/python/cpython/commit/d4426c829565e3ef922c091ee9bd48bc556f2550
[2] https://docs.python.org/3/whatsnew/changelog.html#changelog [gh-100098]



Bug#1025106: python-icecream: (autopkgtest) needs update for python3.11: ValueError: not enough values to unpack (expected 2, got 1)

2022-12-22 Thread s3v
Dear Maintainer,

After upload of executing/1.2.0 to unstable, your package builds
fine and all tests pass (both with python3.10 and python3.11).
I've checked in a sid (not bookworm) chroot environment.

Kind Regards

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025030



Bug#1025238: python-uvicorn: FTBFS with python3.11

2022-12-05 Thread s3v
Dear Maintainer,

> /usr/lib/python3/dist-packages/httpx/_models.py:1: in 
> import cgi
> /usr/lib/python3.11/cgi.py:57: in 
> warnings._deprecated(__name__, remove=(3,13))
> /usr/lib/python3.11/warnings.py:514: in _deprecated
> warn(msg, DeprecationWarning, stacklevel=3)
> E   DeprecationWarning: 'cgi' is deprecated and slated for removal in Python 
> 3.13

This issue was fixed in httpx [1]

Kind Regards

[1] https://github.com/encode/httpx/pull/2309



Bug#1025367: Wrong description for phpmyadmin-shapefile

2022-12-03 Thread s3v
Source: phpmyadmin-shapefile


Dear Maintainer,

I think description for phpmyadmin-shapefile should be modified.
It currently states:

Description: translation API for PHP using Gettext MO files
 This library parses gettext binary .mo files and can mimic the native
 php gettext API. Unlike the native gettext API, this library can use .mo
 files for locales not installed in the system.

as phpmyadmin-motranslator description does.

Kind Regards



Bug#1024877: python-softlayer: tests fail with python 3.11

2022-11-27 Thread s3v
Source: python-softlayer
Severity: important
Control: forwarded -1 
https://github.com/softlayer/softlayer-python/commit/e2249f0e7


Dear Maintainer,

Tests start failing with python 3.11 as a supported Python
version [1][2].
I can reproduce this issue in a bookworm chroot environment
with python3-defaults from unstable.

After applying this commits from upstream, tests pass again
(both with python3.10 and python 3.11) and your package builds
fine as well.

Kind Regards

[1] https://qa.debian.org/excuses.php?package=python3-defaults
[2] 
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-softlayer/28712770/log.gz



Bug#1024566: aiosmtplib FTBFS: autopkgtests fail with python3.11

2022-11-21 Thread s3v
Source: aiosmtplib
Severity: important
Tags: ftbfs


Dear Maintainer,

your package FTBFS because autopkgtests start fail [1] with
python3.11 as supported version.
Please find attached the failure log.

After packaging 2.0.0 and adding some B-D

 - pybuild-plugin-pyproject
 - python3-poetry
 - python3-trustme

your package builds fine in a sid chroot environment and all
test pass.

Kind Regards

[1] 
https://ci.debian.net/data/autopkgtest/testing/amd64/a/aiosmtplib/28498087/log.gz
[2] https://qa.debian.org/excuses.php?package=python3-defaults

ftbfs.tar.gz
Description: application/gzip


Bug#1024564: django-assets FTBFS: re.error: global flags not at the start of the expression at position 6

2022-11-21 Thread s3v
Source: django-assets
Severity: important
Tags: ftbfs
forwarded -1 https://github.com/miracle2k/django-assets/pull/104


Dear Maintainer,

Your package FTBFS because autopkgtests start failing with python3.11 as 
supported
version.
I can see the failure in a sid chroot environment and reproducible-builds 
confirms
the problem [1]

After applying aforementioned PR, your package builds fine and all test pass.

Kind Regards


[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/django-assets.html



Bug#1022495: ufo-extractor: FTBFS: AttributeError: '_TTGlyphGlyf' object has no attribute '_glyph'

2022-11-20 Thread s3v
Control: forwarded -1 https://github.com/robotools/extractor/pull/52
thanks

Dear Maintainer,

after applying aforementioned commits, I was able to build your package
in a sid chroot environment.

Kind Regards



Bug#1024471: cloudpickle FTBFS: multiple tests fail

2022-11-19 Thread s3v
Source: cloudpickle
Severity: important
Tag: ftbfs


Dear Maintainer,
I've tried to build your package in a local sid chroot environment
but the process ends up in a failure (log attached).
After packaging 2.2.0 from pypi [1], most of autokgtest failures vanishe
and only two test still fail as reported upstream [2].
There is a opened PR to address those and I can confirm that it solves
the issue.

Side notes:

1) reproducible-builds doesn't catch yet full failures because the build
   happened before python3.11 [3]
2) Severity "important" since this issue is unconfirmed by others different
   than me


Kind Regards

[1] https://pypi.org/project/cloudpickle/
[2] https://github.com/cloudpipe/cloudpickle/pull/486
[3] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cloudpickle.html



ftbfs.log.tar.gz
Description: application/gzip


Bug#1019610: ruby-ahoy-email: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp (LoadError)

2022-11-10 Thread s3v
On Sun, 6 Nov 2022 20:31:39 +0200 Adrian Bunk  wrote:
> Is there a bug in rails?

https://github.com/rails/rails/pull/44083
seems relevant.

Kind Regards



Bug#1005434: ruby-typhoeus: FTBFS: ERROR: Test "ruby3.0" failed: Timeout::Error:

2022-11-03 Thread s3v
Dear Maintainer,

After applying the attached patch, I was able to build your package
in a sid chroot environment.
Please see [1] for more context.

Kind Regards

[1] https://bugs.ruby-lang.org/issues/14183--- a/spec/support/localhost_server.rb
+++ b/spec/support/localhost_server.rb
@@ -43,7 +43,7 @@
 # Use WEBrick since it's part of the ruby standard library and is available on all ruby interpreters.
 options = { :Port => port }
 options.merge!(:AccessLog => [], :Logger => WEBrick::BasicLog.new(StringIO.new)) unless ENV['VERBOSE_SERVER']
-Rack::Handler::WEBrick.run(Identify.new(@rack_app), options)
+Rack::Handler::WEBrick.run(Identify.new(@rack_app), **options)
   end
 
   def booted?


Bug#1019995: supercollider: FTBFS: sndfile.h:356:33: error: conflicting declaration ‘typedef struct sf_private_tag SNDFILE’

2022-10-31 Thread s3v
Control: forwarded -1 
https://github.com/supercollider/supercollider/commit/b9dd70c4c8d61c93d7a70645e0bd18fa76e6834e
thanks

Dear Maintainer,

After applying upstream commit, I was able to build your package in a sid 
chroot environment.

Kind Regards



  1   2   >