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`
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()).
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:
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
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
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:
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
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
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]
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:
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
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]
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]
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]
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
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:
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
>
>
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
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
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
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)
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
> >
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
>
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
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
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]:
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
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
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
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
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
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
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
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
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
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
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
Dear Maintainer,
please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042610
for a proposed patch.
Kind Regards
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.
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:
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]
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
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
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
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]
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]
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]
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
>
&g
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]
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
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]
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
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
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
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
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
Dear Maintainer,
This issue fixed in libxml2 seems to be related [1]
Kind Regards
[1] https://gitlab.gnome.org/GNOME/libxml2/-/issues/64
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
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
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
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
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
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
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':
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
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,
-- 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
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
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
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]
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:
Control: forwarded -1
https://github.com/DEAP/deap/commit/0453060f6d9fce4e712f0f3479733118b2655bb4
thanks
Dear Maintainer,
> ==
> ERROR: deap.tests.test_algorithms.test_nsga3
>
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]
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
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
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
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:
> >>
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 ===
__
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
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.
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
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
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
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
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]
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
forwarded 1026729 https://github.com/opentracing/opentracing-python/pull/159
thanks
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
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]
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
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
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
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
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
-
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
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
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
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
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
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 - 100 of 194 matches
Mail list logo
