On Thu, Jan 16, 2025 at 12:57:03PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the www.debian.org package:
>
> #1093205: Don't recomment debtags on /intro/help
>
> It has been closed by Thomas Lange .
>
> Their
Package: www.debian.org
Severity: normal
https://www.debian.org/intro/help suggests "Tag and categorize packages on the
Debtags website". The Debtags website is discontinued and shut down.
Source: py-libzfs
Version: 0.0+git20240510.5ae7d5e-1
Severity: serious
Control: block 1067200 by -1
Your package build-depends or depends on cython-legacy, which was
requested to be removed.
Please switch away from cython-legacy ASAP.
Note that cython-legacy is blocked from re-entering testing, s
Package: libn32gcc-14-dev
Version: 14.2.0-13
Unless I'm very confused, libn32gcc-14-dev is not installable on mips64el
and thus gcc-14-multilib -> gcc-multilib are not installable there either.
This can be seen on
https://buildd.debian.org/status/package.php?p=aflplusplus and I confirmed
this on t
Source: python-cymem
Version: 2.0.10-1
Severity: serious
https://ci.debian.net/packages/p/python-cymem/testing/amd64/56425584/
_ ERROR collecting cymem/tests/test_import.py
__
ImportError while importing test module '/tmp/autopkgtest-
lxc.jun1e344/downtmp/build.QsW
Source: pymatgen
Version: 2024.10.29+dfsg1-4
Severity: serious
Tags: ftbfs
When building in a local sbuild chroot:
reading sources... [ 10%] pymatgen.analysis
Matplotlib created a temporary cache directory at /tmp/matplotlib-1a_c8sx6
because the default path (/sbuild-nonexistent/.config/matplotli
Source: pymatgen
Version: 2024.10.29+dfsg1-4
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
https://ci.debian.net/packages/p/pymatgen/testing/amd64/56411098/
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-
On Mon, Jan 13, 2025 at 03:51:58PM +0100, Sven Eckelmann wrote:
> Control: reassign -1 agg 1:2.7.0.r145+dfsg-1
> Control: retitle -1 Linked packages depends on libagg2 (>= 2.6.0) but it is
> not installable
> Control: affects -1 exactimage
>
> On Monday, 13 January 202
Source: agg
Version: 1:2.7.0.r145+dfsg-1
Severity: minor
Vcs-* fields "indicate a publicly accessible repository where the Debian source
package is developed", while the ones in the package are either incorrect or
just point to the upstream repo that doesn't have packaging in it.
-- System Infor
Package: exactimage
Version: 1.0.2-12+b3
Severity: serious
Both exactimage and python3-exactimage depend on libagg2 while the library is
called libagg2t64.
I don't see any hardcoded deps so it could be caused by something in libagg-dev
(wrong shlibs file?).
-- System Information:
Debian Release
Source: invesalius
Version: 3.1.8-6
Severity: serious
https://ci.debian.net/packages/i/invesalius/testing/amd64/56355371/
I tried this locally, and after these two "Errno 2" lines instead of showing
help and segfaulting it produced the following traceback(s):
Traceback (most recent call last
Source: sssd
Version: 2.10.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=sssd&arch=s390x&ver=2.10.1-1&stamp=1736338545&raw=0
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-deb
Source: onboard
Version: 1.4.1-9
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=onboard&arch=riscv64&ver=1.4.1-9%2Bb1&stamp=1736401679&raw=0
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, '
On Sat, Jan 04, 2025 at 12:25:59PM +0100, Matthias Klose wrote:
> Checking for Python support:
> ** Python not found!
The expected Python versions are hardcoded, at least in "configure"
("SUPPYTHONLIBS") and don't include 3.13.
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: python3-skorch
Version: 1.0.0-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
https://ci.debian.net/packages/s/skorch/testing/amd64/56321425/
autopkgtest [09:12:00]: test command1: python3 debian/tests/example1.py
autopkgtest [09:12:00]: test command1: [
Package: xonsh
Version: 0.18.4+dfsg-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
https://ci.debian.net/packages/x/xonsh/testing/amd64/56320881/
Not sure what is the actual failure unless it fails on warnings.
-- System Information:
Debian Release: trixie/sid
A
Package: wireless-regdb
Version: 2024.10.07-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
https://ci.debian.net/packages/w/wireless-regdb/testing/amd64/56320878/
autopkgtest [09:10:13]: test check-signatures: [---
Exception ignored in: <_io.Buff
Package: python3-pytray
Version: 0.3.5-4
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
https://ci.debian.net/packages/p/python-pytray/testing/amd64/56320866/
Task was destroyed but it is pending!
source_traceback: Object created at (most recent call last):
File "/u
Source: python-cobra
Version: 0.29.1-1
Severity: serious
Tags: ftbfs
May or may not be related to default Python being changed to 3.13. Lots of
tests fail, the failures can be seen in the autopkgtest log at
https://ci.debian.net/packages/p/python-cobra/testing/amd64/56317676/ but the
build-time te
Package: pyspread
Version: 2.2.3-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
https://ci.debian.net/packages/p/pyspread/testing/amd64/56320860/
> csvreader = csv.reader(csvfile, dialect=dialect)
E ValueError: bad escapechar or quotechar value
-- Syst
Source: pymilter
Version: 1.0.6-1
Severity: serious
https://ci.debian.net/packages/p/pymilter/testing/amd64/56284590/
Traceback (most recent call last):
File "/tmp/autopkgtest-lxc.2_pc5alp/downtmp/build.zwc/src/test.py", line 23,
in
unittest.TextTestRunner().run(suite())
Source: pyspf
Version: 2.0.14-4
Severity: serious
https://ci.debian.net/packages/p/pyspf/testing/amd64/56284591/
Traceback (most recent call last):
File "/tmp/autopkgtest-lxc.19efqpiv/downtmp/build.e9d/src/test/testspf.py",
line 274, in
tc = suite()# all tests, including doctests
Fil
Package: python3-pygrace
Version: 0.6-4
Severity: serious
https://ci.debian.net/packages/p/pygrace/testing/amd64/56284588/
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'unstable'), (500, 'test
Source: postfix
Version: 3.9.1-9
Severity: serious
https://ci.debian.net/packages/p/postfix/testing/amd64/56317675/
Traceback (most recent call last):
File "/tmp/autopkgtest-lxc.j_99q3ge/downtmp/build.IAz/src/debian/tests/test-
postfix.py", line 42, in
import testlib
File "/tmp/autopkgte
Source: mosquitto
Version: 2.0.20-1
Severity: serious
https://ci.debian.net/packages/m/mosquitto/testing/amd64/56317666/
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate
verify failed: Basic Constraints of CA cert not marked critical (_ssl.c:1019)
-- System Information
Source: kineticstools
Version: 0.6.1+git20220223.1326a4d+dfsg-3
Severity: serious
https://ci.debian.net/packages/k/kineticstools/testing/amd64/56313367/
$ ipdSummary
usage: ipdSummary [-h] [--version] [--log-file LOG_FILE]
-[--log-level {DEBUG,INFO,WARNING,ERROR,CRITICAL
Source: dnarrange
Version: 1.5.3-1
Severity: serious
https://ci.debian.net/packages/d/dnarrange/testing/amd64/56310221/
I assume "/usr/bin/dnarrange:561: DeprecationWarning: 'maxsplit' is passed as
positional argument" is what causes the failure.
-- System Information:
Debian Release: trixie/si
Package: bpython
Version: 0.24-1
Severity: serious
https://ci.debian.net/packages/b/bpython/testing/amd64/56309710/
FAILED bpython/test/test_interpreter.py::TestInterpreter::test_syntaxerror -
...
FAILED bpython/test/test_interpreter.py::TestInterpreter::test_traceback -
As...
FAILED bpython/test
Source: sssd
Version: 2.10.1-1
Severity: serious
Tags: ftbfs
armel and riscv64 don't have valgrind and so sssd can no longer be built there.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'unsta
Source: obitools
Version: 3.0.1~b26+dfsg-4
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=obitools&arch=armel&ver=3.0.1%7Eb26%2Bdfsg-4&stamp=1736521923&raw=0
arm-linux-gnueabi-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall
-O3 -w -I src -I src/libecoPC
Source: nvidia-cuda-toolkit
Version: 12.2.1-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=nvidia-cuda-
toolkit&arch=arm64&ver=12.2.1-2%2Bb1&stamp=1736455273&raw=0
dpkg-shlibdeps: error: cannot find library libXfixes.so.3 needed by
debian/nsight-compute/usr/lib/nsi
New list, much shorter:
adios: cython3-legacy
astra-toolbox/contrib: cython3-legacy
basemap: cython3-legacy
chemps2: cython3-legacy
mlpy: cython3-legacy
pybik: cython3-legacy
pyfftw: cython3-legacy
pygccjit: cython3-legacy
pynfft: cython3-legacy
python-feather-format: cython3-legacy
python-libzim:
Source: breezy
Version: 3.3.9-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=breezy&arch=amd64&ver=3.3.9-1%2Bb2&stamp=1736258298&raw=0
Traceback (most recent call last):
File "/build/reproducible-
path/breezy-3.3.9/breezy/tests/test_symbol_versioning.py", line 10
Source: zeroc-ice
Version: 3.7.10-3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=zeroc-
ice&arch=amd64&ver=3.7.10-3%2Bb1&stamp=1736266983&raw=0
modules/IcePy/Types.cpp: In static member function ‘static void
IcePy::StreamUtil::setSlicedDataMember(PyObject*, const I
Source: libapache2-mod-python
Version: 3.5.0.1-3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=libapache2-mod-
python&arch=amd64&ver=3.5.0.1-3%2Bb2&stamp=1736260721&raw=0
/usr/share/apr-1.0/build/libtool --mode=compile --tag=disable-static
x86_64-linux-gnu-gcc -pre
On Mon, Jan 06, 2025 at 09:02:37PM +0100, Eduard Bloch wrote:
> On Mon, 30 Jun 2014 03:02:01 +0800 Paride Legovini
> wrote:
> > Package: pmount
> > Version: 0.9.23-3
> > Followup-For: Bug #596456
> >
> > Hi,
> >
> > is there any news about about this issue? I checked the Debian
> > Changelog fo
On Sat, Jan 04, 2025 at 09:20:17AM +0100, Matthias Klose wrote:
> saori/saori_python.cpp: In function ‘int py_saori_exist(const char*)’:
> saori/saori_python.cpp:145:28: error: ‘PyEval_CallObject’ was not declared
> in this scope; did you mean ‘PyObject_CallObject’?
Long dead upstream, wasn't inte
On Sat, Jan 04, 2025 at 09:21:53AM +0100, Matthias Klose wrote:
> ghmmwrapper_wrap.c: In function ‘PythonCallBack’:
> ghmmwrapper_wrap.c:3573:9: error: implicit declaration of function
> ‘PyEval_CallObject’; did you mean ‘PyObject_CallObject’?
Dead upstream.
The reason for the failure is https://g
On Sat, Jan 04, 2025 at 09:05:23AM +0100, Matthias Klose wrote:
> + py3versions -sv
> + P=.pybuild/cpython3_3.12_freesas/build
> + cp -r src/freesas/test .pybuild/cpython3_3.12_freesas/build/freesas/
> cp: cannot create directory '.pybuild/cpython3_3.12_freesas/build/freesas/':
> No such file or di
On Mon, Dec 30, 2024 at 09:10:27AM +0100, Florian Ernst wrote:
> @debian-python:
>
> However, AFAIK intersphinx will download things from the internet during
> build, which is not allowed by policy. So maybe just ripping out all
> intersphinx references from the conf.py would be more suitable. I t
Package: debootstrap
Version: 1.0.138
Severity: grave
usrmerge was removed from unstable yesterday. debootstrap tries to install usr-
is-merged and fails:
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
On Tue, Dec 24, 2024 at 12:59:46PM +0100, Alexandre Detiste wrote:
> Hi,
>
> I think I might remember that another RM bug
> involving samhain/sagan was dismissed because DSA
> uses it on Debian infrastructure itself...
>
> https://dsa.debian.org/ports/hardware-requirements/
Yes. That was #108280
On Wed, Dec 04, 2024 at 07:52:18PM -0100, Graham Inggs wrote:
> 168s E OSError:
> /usr/lib/python3/dist-packages/tomopy/util/extern/libtomo-accel.cpython-313-x86_64-linux-gnu.so:
> cannot open shared object file: No such file or directory
Looks like the package only builds for the default Python v
On Tue, Dec 10, 2024 at 11:18:01AM +0100, Andreas Tille wrote:
> Hi,
>
> CCing bug #1088768 since the description fits despite the bug itself is
> different - not sure whether reopen or new bug is the better option.
>
> It turns out that in debci there is a remaining test suite issue[1]:
> [1] h
Source: ironic-python-agent
Version: 9.14.0-1
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.13
=
Failures during discovery
=
--- import errors ---
Failed to import test module:
ironic_python_agent.tests.unit.ext
I tried to fix this by adapting
https://github.com/cloudpipe/cloudpickle/pull/534, but it looks like it
may depend on https://github.com/cloudpipe/cloudpickle/pull/524 which I'm
not going to touch. It would be better for the maintainer to do a new
upstream version upload at this point.
--
WBR, wR
Dead upstream, low popcon, only needed as a B-D for pagure which is
orphaned since June and not in testing since January.
--
WBR, wRAR
signature.asc
Description: PGP signature
Source: sasview
Version: 5.0.6-4
Severity: serious
Tags: ftbfs
ERROR collecting test/corfunc/utest_corfunc.py
ImportError while importing test module '/build/reproducible-
path/sasview-5.0.6/.pybuild/cpython3_3.12_sasview/build/test/corfunc/utest_corfunc.py'.
Hint
On Sun, Dec 01, 2024 at 09:44:17PM -0800, Otto Kekäläinen wrote:
> My intent here was to suggest specifically that the version of form
> 0.0~git20130606.b00ec39-1 would be elevated as the Policy recommended
> form, as it makes sense and is already most popular.
For the record, I assume it's most p
Source: python-voip-utils
Version: 0.2.0-1
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.13
__ ERROR collecting tests/test_sip.py
__
ImportError while importing test module '/build/reproducible-path/python-voip-
utils-0
Source: gpaw
Version: 24.6.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=gpaw&arch=amd64&ver=24.6.0-1%2Bb2&stamp=1732919872&raw=0
ImportError while importing test module
'/<>/.pybuild/cpython3_3.12/build/gpaw/defects/__init__.py'.
Hint: make sure your test modul
Package: freedombox
Version: 24.24
Severity: serious
https://ci.debian.net/packages/f/freedombox/testing/amd64/54950089/
288s plinth/modules/sso/privileged.py:78: in generate_ticket
288s return _create_ticket(pkey, uid, valid_until, tokens=tokens,
288s plinth/modules/sso/privileged.py:61: in
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: kv...@packages.debian.org
Control: affects -1 + src:kvirc
User: ftp.debian@packages.debian.org
Usertags: remove
On Wed, Nov 27, 2024 at 05:07:16PM -0800, Otto Kekäläinen wrote:
> > Please recommend only putting this information into the changelog entry.
> > It has no place in the version value.
>
> Sorry, I don't understand, can you elaborate?
>
> In the case of say for example canid 0.0~git20180613.007c9a
On Wed, Nov 27, 2024 at 01:11:14PM -0800, Otto Kekäläinen wrote:
> Package: debian-policy
> Found: 4.7.0.1
>
> I would like to suggest the Debian Policy to recommend a specific
> Debian package version string scheme in cases where upstream has no
> releases, but they do have git commit ids to refe
On Wed, Nov 20, 2024 at 02:56:11PM +0100, Alexandre Detiste wrote:
> Maybe not other completely useless modules. (pipes ?)
I think somebody (you?) recently want to vendor pipes to fix something, or
maybe it was fixed in a different way instead?
--
WBR, wRAR
signature.asc
Description: PGP signa
override_dh_auto_build:
$(HOME)/.cargo/bin/cargo build --release
To put it mildly, this is not permitted.
--
WBR, wRAR
signature.asc
Description: PGP signature
I checked the upstream and found that the packaged version already claims
to support 3.13, and they indeed run 3.13 tests on CI. So this is weird.
--
WBR, wRAR
signature.asc
Description: PGP signature
Source: silx
Version: 2.1.2+dfsg-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=silx&arch=mips64el&ver=2.1.2%2Bdfsg-1&stamp=1731840915&raw=0
FAILED silx/image/test/test_bilinear.py::TestBilinear::test_mask_grad -
Asser...
FAILED silx/math/test/test_combo.py::TestMi
Source: python-skbio
Version: 0.6.2-3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=python-
skbio&arch=amd64&ver=0.6.2-3%2Bb1&stamp=1731829305&raw=0
> self.assertEqual(SomethingToInterpolate.interpolate_me.__doc__,
"First line\n\n
Source: rapidfuzz
Version: 3.9.4+ds-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=rapidfuzz&arch=amd64&ver=3.9.4%2Bds-1%2Bb1&stamp=1731765262&raw=0
-- Using packaged version of Taskflow
CMake Error at CMakeLists.txt:102 (add_subdirectory):
add_subdirectory given
Source: python-pyspike
Version: 0.8.0+dfsg-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=python-
pyspike&arch=armhf&ver=0.8.0%2Bdfsg-2%2Bb3&stamp=1731767965&raw=0
I assume it's due to using cython-legacy.
-- System Information:
Debian Release: trixie/sid
APT p
Source: pybik
Version: 3.0-6
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=pybik&arch=armel&ver=3.0-6%2Bb4&stamp=1731766127&raw=0
generating build/temp.linux-arm-cpython-313/pybiklib/ext/_gldraw_es2.pxd.tmp
Traceback (most recent call last):
File "/<>/setup.py", l
Source: opendht
Version: 3.0.1-1.1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=opendht&arch=armhf&ver=3.0.1-1.1%2Bb5&stamp=1731706704&raw=0
!!!FAILURES!!!
Test Results:
Run: 21 Failures: 1 Errors: 0
1) test: test::DhtRunnerTester::testListen (F) line: 178
Source: thrift
Version: 0.19.0-2.1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=thrift&arch=ppc64el&ver=0.19.0-2.1%2Bb4&stamp=1731703163&raw=0
/usr/bin/go test github.com/apache/thrift/lib/go/thrift
--- FAIL: TestNoHangDuringStopFromClientNoDataSendDuringAcceptLoop
Source: mpi4py
Version: 4.0.0-9
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=mpi4py&arch=s390x&ver=4.0.0-9&stamp=1731108627&raw=0
testAcceptConnect (test_dynproc.TestDPM.testAcceptConnect) ... [sbuild:00240]
*** Process received signal ***
[sbuild:00240] Signal: Se
Source: pygame
Version: 2.6.0-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=pygame&arch=s390x&ver=2.6.0-2%2Bb1&stamp=1731707780&raw=0
==
FAIL: test_event_wait
(pygame.tests.event_test.EventModuleT
Source: jellyfish
Version: 2.3.1-3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=jellyfish&arch=ppc64el&ver=2.3.1-3%2Bb7&stamp=1731546977&raw=0
unit_tests/test_cooperative_pool2.cc:86: Failure
Value of: workers.check_print()
Actual: false
Expected: true
[ FAILED
Source: python-ptrace
Version: 0.9.9-0.1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=python-
ptrace&arch=riscv64&ver=0.9.9-0.1%2Bb2&stamp=1731547088&raw=0
It looks like there are two test failures caused by "OverflowError: Python int
too large to convert to C long
Source: sphinxbase
Version: 0.8+5prealpha+1-18
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=sphinxbase&arch=mips64el&ver=0.8%2B5prealpha%2B1-18%2Bb1&stamp=1731497702&raw=0
Sub-tests failed: WAVE2FEAT test
FAIL test-sphinx_fe-ctl.sh (exit status: 1)
-- System Info
Source: xmms2
Version: 0.8+dfsg-27
Severity: serious
The package FTBFS with modern cython so in #1056894 it was temporarily switched
to cython3-legacy a year ago. The time is now up and as cython3-legacy won't be
in trixie, xmms2 won't be in trixie either unless someone ports it or, if
that's poss
On Thu, Nov 14, 2024 at 10:31:42PM +0500, Andrey Rakhmatullin wrote:
> There is still no autoremoval because grpc is a key package but grcp that
> doesn't build-depend on cython3-legacy is already in unstable and should
> migrate in 3 days.
grpc now migrated and cython3-legacy with
An updated list, after many packages switch to cython3:
adios: cython3-legacy
astra-toolbox/contrib: cython3-legacy
basemap: cython3-legacy
chemps2: cython3-legacy
mayavi2: cython3-legacy
mlpy: cython3-legacy
obitools: cython3-legacy
pybik: cython3-legacy
pyfftw: cython3-legacy
pygccjit: cython3-l
Source: pyfribidi
Version: 0.12.0+repack-10
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=pyfribidi&arch=i386&ver=0.12.0%2Brepack-10%2Bb3&stamp=1731496296&raw=0
I: pybuild base:311: /usr/bin/python3.13 setup.py build
pyfribidi.c: In function ‘unicode_log2vis’:
pyfri
Control: tags -1 - patch
On Fri, Sep 27, 2024 at 09:08:04PM +0500, Andrey Rakhmatullin wrote:
> forwarded 1082217 https://github.com/serge-sans-paille/gast/issues/85
> tags 1082217 + upstream fixed-upstream patch
The patch unfortunately doesn't apply directly, because the upstream
On Thu, Sep 19, 2024 at 12:42:04PM +0200, Stefano Rivera wrote:
> Looks like this is resolved in 7.9.1, upstream.
7.9.1 is now in sid, though it needs at least numpy to be built.
--
WBR, wRAR
signature.asc
Description: PGP signature
Control: severity -1 serious
Control: tags -1 + wontfix
This was requested to be removed from Debian some months ago.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Mon, Oct 21, 2024 at 08:00:55PM -0300, Emmanuel Arias wrote:
> * scalene: patched-out
> https://tracker.debian.org/news/1578167/accepted-scalene-1545-2-source-into-unstable/
> * python-pdoc: New upstream release remove the dependency
> https://tracker.debian.org/news/1578652/accepted-python-pd
Package: python3-torch
Version: 2.5.0+dfsg-1
Severity: important
Control: clone -1 -2
Control: reassign -2 python3-torch-cuda 2.4.1-4
python3-astunparse is not going to support Python 3.13 and is not needed for
modern code and so we want to remove it from Debian. Please drop the dependency
on it b
gelog 2023-09-07 20:48:50.0 +0500
+++ ms-gsl-4.0.0/debian/changelog 2024-11-01 16:40:45.0 +0500
@@ -1,3 +1,10 @@
+ms-gsl (4.0.0-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix autopkgtests with clang 19 (Closes: #1085429).
+
+ -- Andrey Rakhmatullin Fri, 01 Nov
On Mon, Oct 28, 2024 at 10:50:27AM +0100, Bastian Venthur wrote:
> apparently, this bug will cause a lot of packages to be removed from testing
> due to the transitive reverse dependencies[1]. Is there any update on this
> bug?
The upstream bug looks bleak to me: open for 7 months, no upstream
co
On Sun, Oct 27, 2024 at 09:20:13PM -0500, Steven Robbins wrote:
> Certainly it would be nice to have C++ code build clean with every variation
> of compiler switches. But does that rise to the level of a *release
> critical*
> bug? Is there a rule - written or unwritten - that leads one to tha
On Sat, Oct 26, 2024 at 04:29:17PM -0500, Steven Robbins wrote:
> Hello,
>
> On Saturday, October 26, 2024 2:20:05 P.M. CDT Andrey Rakhmatullin wrote:
> > Control: reassign -1 libgtest-dev 1.15.2-1
> > Control: affects -1 libmsgsl-dev
>
> > That macro in libgtes
Control: reassign -1 libgtest-dev 1.15.2-1
Control: affects -1 libmsgsl-dev
On Sat, Oct 19, 2024 at 02:06:52PM +0200, Sebastian Ramacher wrote:
> /tmp/autopkgtest-lxc.8ydsgog3/downtmp/build.aB4/src/tests/notnull_tests.cpp:178:9:
> error: 'switch' missing 'default' label [-Werror,-Wswitch-default]
On Sat, Oct 19, 2024 at 09:08:15AM +0200, Andreas Tille wrote:
> Usually we file Intend To Salvage bugs[2] if we create a repository on
> Salsa if the package is not maintained in Vcs yet. However, given its
> importance I can't imagine that this package is not in some Git
> repository yet.
It ha
On Tue, Oct 15, 2024 at 05:31:23PM +0800, EiPiFun wrote:
> > I did, and at first I thought you are only looking at the top level
> > instead of looking at the module directory, but your PR edits a file
> > in there so I'm confused.
>
> Yeah, I forget to remind you that Google uses a large mono re
On Tue, Oct 15, 2024 at 04:27:27PM +0800, EiPiFun wrote:
> The problem is that its GitHub release does not contains all files.
> You can check the file:
> https://github.com/googleapis/google-cloud-python/archive/refs/tags/google-ai-generativelanguage-v0.6.10.tar.gz
I did, and at first I thought y
On Tue, Oct 15, 2024 at 03:15:50PM +0800, EiPiFun wrote:
> Hello, Mr.Phil Wyett!
>
> Thanks for your reminds.
>
> Its GitHub release lacks setup.py or pyproject.toml
It doesn't lack setup.py though?
> I start a small pull request to inform them they should add docs info.
>
> https://github.co
On Mon, Oct 07, 2024 at 12:16:52PM -0400, Louis-Philippe Véronneau wrote:
> xdrlib: larch/io/mda.py:14
The file was dropped upstream in 0.9.80:
https://github.com/xraypy/xraylarch/commit/1a40a51dced1e328f4d522dcf38c88c36ea8fdfe
--
WBR, wRAR
signature.asc
Description: PGP signature
Control: forwarded -1 https://github.com/ktbyers/netmiko/issues/3177
Control: tags -1 + upstream fixed-upstream
The upstream has vendored telnetlib in 4.4.0.
--
WBR, wRAR
signature.asc
Description: PGP signature
The upstream is dead (last commit 2021, last release 2020).
The only revdep besides med-bio-dev is sga, where according to the README
it's optional.
--
WBR, wRAR
signature.asc
Description: PGP signature
The upstream is dead, and "In theory, no current Python package supporting
Python since version 3.9 should be required to use this package, as the
functionality is available in the stdlib now".
Unfortunately,
Reverse-Depends
===
* psychopy
* python3-griffe
* python3-mdtraj [amd64 arm64
The upstream looks dead (last commit 2022, last release 2021). The
upstream bug about 3.13, open since 2023, suggests there is no solution in
sight.
Popcon 95, no revdeps.
--
WBR, wRAR
signature.asc
Description: PGP signature
Dead upstream (last commit 2020, last release 2019). Can be safely removed
if needed: no revdeps, popcon 15. It also B-D on python3-amqplib which is
also very dead, broken and not in testing since 2 weeks ago (#1077824),
though this dep looks optional.
--
WBR, wRAR
signature.asc
Description: P
On Thu, Sep 26, 2024 at 09:39:33PM +0500, Andrey Rakhmatullin wrote:
> Control: forwarded -1
> https://github.com/zopefoundation/zope.interface/issues/323
>
> On Sat, Sep 21, 2024 at 12:10:43AM +0500, Andrey Rakhmatullin wrote:
> > Not marking forwarded but this may be
>
On Mon, Sep 30, 2024 at 07:41:50AM +, Philipp Kern wrote:
> > Package: ftp.debian.org
> > Severity: normal
> > X-Debbugs-Cc: samh...@packages.debian.org
> > Control: affects -1 + src:samhain
> > User: ftp.debian@packages.debian.org
> > Usertags: remove
> >
> > Not in testing since Apr 2024
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: qiskit-ibmq-provi...@packages.debian.org
Control: affects -1 + src:qiskit-ibmq-provider
User: ftp.debian@packages.debian.org
Usertags: remove
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008627
https://bugs.debian.org/cgi-bin/bugrep
Please note that updating to a new upstream version requires packaging
mitmproxy_rs first.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Thu, Sep 26, 2024 at 10:05:11PM +0500, Andrey Rakhmatullin wrote:
> Dead upstream. Popcon 76. Only needed as a B-D of impacket, and that B-D
> likely is not needed anymore.
B-D in impacket was indeed unnecessary and is dropped in 0.12.0-2.
--
WBR, wRAR
signature.asc
Descriptio
On Thu, Mar 24, 2022 at 06:43:02PM -0400, Stefano Rivera wrote:
> Source: pcapy
> Version: 0.11.5-1
> Severity: normal
> Tags: upstream
>
> pcapy appears to be unmaintained, upstream contributions have moved to
> the pcapy-ng fork. The rename seems to only apply to the source, not the
> module, so
1 - 100 of 503 matches
Mail list logo
