Your message dated Thu, 11 Jan 2024 07:49:26 +
with message-id
and subject line Bug#1060176: fixed in dipy 1.8.0-1
has caused the Debian Bug report #1060176,
regarding dipy: FTBFS on ppc64el: FAILED
dipy/segment/tests/test_mrf.py::test_icm_square - AssertionError
to be marked as done.
This
Your message dated Thu, 11 Jan 2024 07:34:35 +
with message-id
and subject line Bug#1058106: fixed in python-ml-collections 0.1.1-3
has caused the Debian Bug report #1058106,
regarding python-ml-collections: FTBFS: ModuleNotFoundError: No module named
'imp'
to be marked as done.
This means
Processing control commands:
> reassign -1 python-django-solo
Bug #1060429 [solo1-cli] solo1-cli has an undeclared file conflict on
/usr/lib/python3/dist-packages/solo/__init__.py
Bug reassigned from package 'solo1-cli' to 'python-django-solo'.
No longer marked as found in versions
Control: reassign -1 python-django-solo
Hi Helmut,
thanks for the bug report, but I guess you missed that solo1-cli.ships this
file for years (in stable, testing, unstable) while python-django-solo was
just uploaded yesterday. So I think the bug is in python-django-solo actually.
Best,
Package: solo1-cli
Version: 0.1.1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + python3-django-solo
solo1-cli has an undeclared file conflict. This may result in an unpack
error from dpkg.
The file
There's no _cairo.cpython-312-x86_64-linux-gnu.so in python3-cairo
because pycairo no longer builds extensions for all supported Python
versions, see #1055488.
Processing control commands:
> affects -1 + python3-django-solo
Bug #1060429 [solo1-cli] solo1-cli has an undeclared file conflict on
/usr/lib/python3/dist-packages/solo/__init__.py
Added indication that 1060429 affects python3-django-solo
--
1060429:
Package: python3-appdirs
Version: 1.4.4-4
Severity: serious
Justification: maintainer determination
This is dead upstream and easily replacable with platformdirs. Rather
than release trixie with appdirs, remaining users should port to
platformdirs instead.
Scott K
Your message dated Thu, 11 Jan 2024 03:27:35 +
with message-id
and subject line Bug#1056471: fixed in python-fabio 2023.6.0-3.1
has caused the Debian Bug report #1056471,
regarding python-fabio's autopkg tests fail with Python 3.12
to be marked as done.
This means that you claim that the
Thanks. Just done that. Hopefully it’ll work this time.
Hao
From: "Shepherd, Lori"
Date: Wednesday, January 10, 2024 at 8:30 PM
To: "Wu, Hao" , Andreas Tille , Harry Feng
Cc: "1058...@bugs.debian.org" <1058...@bugs.debian.org>, Debian R
, Bioconductor Package Maintainer
Subject: Re:
Hello,
I've just uploaded the patch. Thanks Yogeswaran!
Please consider merge this MR [0]
[0] https://salsa.debian.org/science-team/python-fabio/-/merge_requests/1
cheers,
Emmanuel Arias
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ eam...@debian.org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: FA9DEC5DE11C63F1
⠈⠳⣄
Processing commands for cont...@bugs.debian.org:
> found 770171 1.0.2-2
Bug #770171 {Done: Sylvestre Ledru } [fail2ban] sshd jail
fails when system solely relies on systemd journal for logging
Marked as found in versions fail2ban/1.0.2-2.
> tags 770171 + upstream
Bug #770171 {Done: Sylvestre
found 770171 1.0.2-2
tags 770171 + upstream
forwarded 770171 https://github.com/fail2ban/fail2ban/issues/1372
user l...@pca.it
usertags 770171 + pca.it-security
thanks
Hi there,
I just got hit by this as well, plus the nftables issue:
Processing commands for cont...@bugs.debian.org:
> found 813861 0.12.0-6
Bug #813861 [phpdox] Useless in Debian
Marked as found in versions phpdox/0.12.0-6.
> notfound 813861 0.8.1.1-1
Bug #813861 [phpdox] Useless in Debian
No longer marked as found in versions phpdox/0.8.1.1-1.
> thanks
Stopping
Processing commands for cont...@bugs.debian.org:
> unarchive 813861
Bug #813861 {Done: David Prévot } [phpdox] Useless in Debian
Unarchived Bug 813861
> # phpdox does not seem that useful five years later
> reopen 813861
Bug #813861 {Done: David Prévot } [phpdox] Useless in Debian
Bug reopened
Source: libextractor
Version: 1:1.11-8
Severity: serious
Control: close -1 1:1.13-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than
Processing control commands:
> close -1 1:1.13-1
Bug #1060414 [src:libextractor] src:libextractor: fails to migrate to testing
for too long: FTBFS on s390x
Marked as fixed in versions libextractor/1:1.13-1.
Bug #1060414 [src:libextractor] src:libextractor: fails to migrate to testing
for too
Processing control commands:
> close -1 1.4.2-1
Bug #1060413 [src:emacs-posframe] src:emacs-posframe: fails to migrate to
testing for too long: uploader built arch:all binary
Marked as fixed in versions emacs-posframe/1.4.2-1.
Bug #1060413 [src:emacs-posframe] src:emacs-posframe: fails to
Source: emacs-posframe
Version: 1.1.7-3
Severity: serious
Control: close -1 1.4.2-1
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more
Source: emacs-wgrep
Version: 3.0.0-1
Severity: serious
Control: close -1 3.0.0-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days
Processing control commands:
> close -1 3.0.0-2
Bug #1060412 [src:emacs-wgrep] src:emacs-wgrep: fails to migrate to testing for
too long: autopkgtest regression
Marked as fixed in versions emacs-wgrep/3.0.0-2.
Bug #1060412 [src:emacs-wgrep] src:emacs-wgrep: fails to migrate to testing for
too
Your message dated Wed, 10 Jan 2024 20:46:14 +
with message-id
and subject line Bug#1059487: fixed in django-oauth-toolkit 2.3.0-2.1
has caused the Debian Bug report #1059487,
regarding src:django-oauth-toolkit: fails to migrate to testing for too long:
uploader built arch:all binaries
to be
Your message dated Wed, 10 Jan 2024 20:36:33 +
with message-id
and subject line Bug#1058276: fixed in bart-view 0.3.00-1
has caused the Debian Bug report #1058276,
regarding bart-view: FTBFS: (.text+0xa4e): undefined reference to
`shared_obj_destroy'
to be marked as done.
This means that
Processing commands for cont...@bugs.debian.org:
> tags 1060407 + upstream
Bug #1060407 [src:gtkwave] Multiple security issues
Added tag(s) upstream.
> found 1060407 3.3.116-1
Bug #1060407 [src:gtkwave] Multiple security issues
Ignoring request to alter found versions of bug #1060407 to the same
Source: gpac
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerabilities were published for gpac.
CVE-2024-0321[0]:
| Stack-based Buffer Overflow in GitHub repository gpac/gpac prior to
| 2.3-DEV.
Source: gtkwave
Version: 3.3.116-1
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team
A very thorough security audit of gtkwave unveiled a total of 82 security
issues in gtkwave, all fixed in 3.3.118:
CVE-2023-32650 CVE-2023-34087 CVE-2023-34436 CVE-2023-35004
CVE-2023-35057
Processing commands for cont...@bugs.debian.org:
> tags 1058103 + fixed-upstream
Bug #1058103 [src:astroid] astroid: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Hi Aurélien,
On 08/01/2024 21:18, Aurelien Jarno wrote:
> On riscv64, mptcpd fails to build from source with a segmentation fault
> in the test-mptcpwrap test:
(...)
> Investigation shows that 3 conditions are needed to trigger this issue:
> - A recent kernel that supports mptcp, to be checked
Your message dated Wed, 10 Jan 2024 13:05:40 -0500
with message-id
and subject line Re: rust-just: Build-Depends: rust-strum 0.24 but 0.25 is
available
has caused the Debian Bug report #1060350,
regarding rust-just: Build-Depends: rust-strum 0.24 but 0.25 is available
to be marked as done.
Your message dated Wed, 10 Jan 2024 18:01:37 +
with message-id
and subject line Bug#1058298: fixed in pyee 11.1.0-1
has caused the Debian Bug report #1058298,
regarding pyee: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.12 3.11" returned exit code 13
to
Processing control commands:
> tags -1 help
Bug #1056874 [src:python-srsly] python-srsly: ftbfs with cython 3.0.x
Added tag(s) help.
--
1056874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 help
Hi,
when applying the patch (thanks for this, Bas) I learned that the
package builds for other reasons. This is also true for the latest
upstream version[1].
Any help to fix this would be welcome
Andreas.
[1]
On Tue, 09 Jan 2024 17:58:57 +0200, Niko Tyni wrote:
> the libosp-dev package in sid is missing a dependency on libosp5,
> leaving /usr/lib/libosp.so a dangling symlink and making at least
> libsgml-parser-opensp-perl (and probably other packages build-depending
> on libosp-dev) fail to build.
A
Processing control commands:
> tags -1 help
Bug #1058400 [src:python-stack-data] python-stack-data: FTBFS: dh_auto_test:
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned
exit code 13
Added tag(s) help.
--
1058400:
Control: tags -1 help
Hi,
I tried the suggested patch for the cython3 issue of bug #1056872
in the currently packaged version[1] as well also tried upgrading
to latest upstream and tried building[2] which failed as well.
I admit, I'm running out of ideas what to do next.
Any help is welcome
Am Mittwoch, dem 10.01.2024 um 08:16 +0100 schrieb Andreas Tille:
> Hi Martin,
>
> I tried to open an issue upstream but it seems the repository does not
> feature submitting issues. Can you have a look please?
>
> Kind regards
> Andreas.
>
Hi Andreas,
I just tagged a new upstream
Your message dated Wed, 10 Jan 2024 17:22:50 +
with message-id
and subject line Bug#1052942: fixed in insserv 1.24.0-2
has caused the Debian Bug report #1052942,
regarding Upstream testsuite fails to produce deterministic results
to be marked as done.
This means that you claim that the
Your message dated Wed, 10 Jan 2024 17:02:43 +
with message-id
and subject line Bug#1056858: fixed in python-hidapi 0.9.0.post3-5
has caused the Debian Bug report #1056858,
regarding python-hidapi: ftbfs with cython 3.0.x
to be marked as done.
This means that you claim that the problem has
Control: tags -1 upstream
Control: forwarded -1 https://github.com/NightTsarina/python-rocksdb/issues/22
--
http://fam-tille.de
Processing control commands:
> tags -1 upstream
Bug #1012074 [src:python-rocksdb] python-rocksdb: FTBFS with rocksdb 7.2+
Ignoring request to alter tags of bug #1012074 to the same tags previously set
> forwarded -1 https://github.com/NightTsarina/python-rocksdb/issues/22
Bug #1012074
Your message dated Wed, 10 Jan 2024 16:10:11 +
with message-id
and subject line Bug#1058494: fixed in wayfire 0.8.0+git20240110-1
has caused the Debian Bug report #1058494,
regarding wayfire: Please update to wlroots 0.17
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 10 Jan 2024 15:11:09 +
with message-id
and subject line Bug#1056833: fixed in pybik 3.0-6
has caused the Debian Bug report #1056833,
regarding pybik: ftbfs with cython 3.0.x
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
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
Processing commands for cont...@bugs.debian.org:
> tags 1058298 + pending
Bug #1058298 [src:pyee] pyee: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if
Your message dated Wed, 10 Jan 2024 14:39:15 +
with message-id
and subject line Bug#1056816: fixed in mayavi2 4.8.1-3
has caused the Debian Bug report #1056816,
regarding mayavi2: ftbfs with cython 3.0.x
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 10 Jan 2024 13:34:14 +
with message-id
and subject line Bug#1056241: fixed in dials 3.17.0+dfsg3-1
has caused the Debian Bug report #1056241,
regarding dials autopkg tests fail with Python 3.12
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 10 Jan 2024 13:34:14 +
with message-id
and subject line Bug#1059175: fixed in dials 3.17.0+dfsg3-1
has caused the Debian Bug report #1059175,
regarding dials: FTBFS: Imported target "DXTBX::DXTBX" includes non-existent
path
to be marked as done.
This means that you
Your message dated Wed, 10 Jan 2024 13:24:12 +
with message-id
and subject line Bug#1058133: fixed in python-numpy-groupies 0.10.2-1
has caused the Debian Bug report #1058133,
regarding python-numpy-groupies: FTBFS: AttributeError: module 'configparser'
has no attribute 'SafeConfigParser'.
Your message dated Wed, 10 Jan 2024 13:24:01 +
with message-id
and subject line Bug#1052430: fixed in pastedeploy 3.1-1
has caused the Debian Bug report #1052430,
regarding pastedeploy: FTBFS against dh-python 6.20230825
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 10 Jan 2024 13:02:32 +
with message-id
and subject line Bug#1054663: fixed in telegram-send 0.37-2
has caused the Debian Bug report #1054663,
regarding telegram-send: Fails to run
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 10 Jan 2024 12:59:38 +
with message-id
and subject line Bug#1060307: fixed in open3d 0.18.0+ds-2
has caused the Debian Bug report #1060307,
regarding open3d-viewer: missing Breaks+Replaces: open3d-gui (<< 0.18)
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> tags 1060323 + ftbfs
Bug #1060323 [libosp-dev] libosp-dev: missing dependency on libosp5
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1060323:
Two points:
1. You need a valid version bump for it to propagate on Bioconductor
systems. so it devel you would need to push a bump to 1.51.1
2. There are always two active branches in Bioconductor. devel and the
current release found currently on branch RELEASE_3_18. You would have to
Your message dated Wed, 10 Jan 2024 12:14:23 +
with message-id
and subject line Bug#1058243: fixed in python-aiomeasures 0.5.14-6
has caused the Debian Bug report #1058243,
regarding python-aiomeasures: FTBFS: AttributeError: module 'configparser' has
no attribute 'SafeConfigParser'. Did you
Processing commands for cont...@bugs.debian.org:
> # wlroots 0.17 is now in sid
> severity 1058497 serious
Bug #1058497 [reform-firedecor] reform-firedecor: Please update to wlroots 0.17
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.
Please contact me if you need
Processing commands for cont...@bugs.debian.org:
> # wlroots 0.17 is now in sid
> severity 1058495 serious
Bug #1058495 [cage] cage: Please update to wlroots 0.17
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1058495:
Processing commands for cont...@bugs.debian.org:
> # wlroots 0.17 is now in sid
> severity 1058493 serious
Bug #1058493 [gamescope] gamescope: Please update to wlroots 0.17
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing commands for cont...@bugs.debian.org:
> # wlroots 0.17 is now in sid
> severity 1058494 serious
Bug #1058494 [wayfire] wayfire: Please update to wlroots 0.17
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Your message dated Wed, 10 Jan 2024 11:34:30 +
with message-id
and subject line Bug#1052737: fixed in autoradio 3.6.4-1
has caused the Debian Bug report #1052737,
regarding autoradio: FTBFS: ImportError: cannot import name 'ugettext_lazy'
from 'django.utils.translation'
Your message dated Wed, 10 Jan 2024 11:28:30 +
with message-id
and subject line Bug#1058174: fixed in translation-finder 1.0-3
has caused the Debian Bug report #1058174,
regarding translation-finder: FTBFS: AttributeError: 'RawConfigParser' object
has no attribute 'readfp'. Did you mean:
Your message dated Wed, 10 Jan 2024 10:34:37 +
with message-id
and subject line Bug#1058206: fixed in constantly 23.10.4-1
has caused the Debian Bug report #1058206,
regarding constantly: FTBFS: AttributeError: module 'configparser' has no
attribute 'SafeConfigParser'. Did you mean:
Your message dated Wed, 10 Jan 2024 10:22:19 +
with message-id
and subject line Bug#1058149: fixed in python-stdlib-list 0.10.0-1
has caused the Debian Bug report #1058149,
regarding python-stdlib-list: FTBFS: AttributeError: module 'configparser' has
no attribute 'SafeConfigParser'. Did you
Your message dated Wed, 10 Jan 2024 10:22:38 +
with message-id
and subject line Bug#1058139: fixed in txacme 0.9.3-3
has caused the Debian Bug report #1058139,
regarding txacme: FTBFS: AttributeError: module 'configparser' has no attribute
'SafeConfigParser'. Did you mean: 'RawConfigParser'?
Your message dated Wed, 10 Jan 2024 10:22:10 +
with message-id
and subject line Bug#1058137: fixed in python-msmb-theme 1.2.0-4
has caused the Debian Bug report #1058137,
regarding python-msmb-theme: FTBFS: AttributeError: module 'configparser' has
no attribute 'SafeConfigParser'. Did you
Your message dated Wed, 10 Jan 2024 09:34:27 +
with message-id
and subject line Bug#1058135: fixed in bumblebee-status 2.2.0-1
has caused the Debian Bug report #1058135,
regarding bumblebee-status: FTBFS: AttributeError: module 'configparser' has no
attribute 'SafeConfigParser'. Did you
Your message dated Wed, 10 Jan 2024 09:17:10 +
with message-id
and subject line Bug#1058110: fixed in python-eliot 1.14.0-1
has caused the Debian Bug report #1058110,
regarding python-eliot: FTBFS: AttributeError: module 'configparser' has no
attribute 'SafeConfigParser'. Did you mean:
Your message dated Wed, 10 Jan 2024 09:18:11 +
with message-id
and subject line Bug#1059978: fixed in rosegarden 1:22.12.1-2
has caused the Debian Bug report #1059978,
regarding rosegarden: Please move from liblircclient-dev to liblirc-dev
to be marked as done.
This means that you claim that
Your message dated Wed, 10 Jan 2024 09:16:52 +
with message-id
and subject line Bug#1058430: fixed in optlang 1.8.1-1
has caused the Debian Bug report #1058430,
regarding optlang: FTBFS: AttributeError: module 'configparser' has no
attribute 'SafeConfigParser'. Did you mean:
Your message dated Wed, 10 Jan 2024 09:17:00 +
with message-id
and subject line Bug#1058203: fixed in python-depinfo 2.2.0-2
has caused the Debian Bug report #1058203,
regarding python-depinfo: FTBFS: AttributeError: module 'configparser' has no
attribute 'SafeConfigParser'. Did you mean:
Package: nut-modbus
Version: 2.8.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + nut-server
nut-modbus has an undeclared file conflict. This may result in an unpack
error from dpkg.
The file /lib/nut/apc_modbus is contained in the packages
*
Processing control commands:
> affects -1 + nut-server
Bug #1060377 [nut-modbus] nut-modbus has an undeclared file conflict on
/lib/nut/apc_modbus
Added indication that 1060377 affects nut-server
--
1060377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060377
Debian Bug Tracking System
Your message dated Wed, 10 Jan 2024 09:15:56 +
with message-id
and subject line Bug#1058098: fixed in crochet 2.1.1-2
has caused the Debian Bug report #1058098,
regarding crochet: FTBFS: AttributeError: module 'configparser' has no
attribute 'SafeConfigParser'. Did you mean:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 1 Jan 2024 11:31:38 +0100 Paul Gevers wrote:
> Source: xfce4-power-manager
> Version: 4.18.2-1
> Severity: serious
> Control: close -1 4.18.3-1
> Tags: sid trixie
> User: release.debian@packages.debian.org
> Usertags: out-of-sync
>
>
Hi Andreas,
thanks. I missed this. I will look at this tomorrow.
Martin
Am Mittwoch, dem 10.01.2024 um 08:16 +0100 schrieb Andreas Tille:
> Hi Martin,
>
> I tried to open an issue upstream but it seems the repository does not
> feature submitting issues. Can you have a look please?
>
>
74 matches
Mail list logo