Processed: src:rust-kvm-bindings: fails to migrate to testing for too long: FTBFS on i386
Processing control commands:
> close -1 0.5.0-1
Bug #1024868 [src:rust-kvm-bindings] src:rust-kvm-bindings: fails to migrate to
testing for too long: FTBFS on i386
Marked as fixed in versions rust-kvm-bindings/0.5.0-1.
Bug #1024868 [src:rust-kvm-bindings] src:rust-kvm-bindings: fails to migrate to
testing for too long: FTBFS on i386
Marked Bug as done
> block -1 by 1021316
Bug #1024868 {Done: Paul Gevers } [src:rust-kvm-bindings]
src:rust-kvm-bindings: fails to migrate to testing for too long: FTBFS on i386
1024868 was not blocked by any bugs.
1024868 was not blocking any bugs.
Added blocking bug(s) of 1024868: 1021316
--
1024868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1024868: src:rust-kvm-bindings: fails to migrate to testing for too long: FTBFS on i386
Source: rust-kvm-bindings Version: 0.1.1-1 Severity: serious Control: close -1 0.5.0-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1021316 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:rust-kvm-bindings has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package failed to build from source on i386, which was reported in bug 1021316. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=rust-kvm-bindings OpenPGP_signature Description: OpenPGP digital signature
Bug#1021831: marked as done (intel-ipsec-mb: FTBFS: dh_install: error: missing files, aborting)
Your message dated Sun, 27 Nov 2022 07:49:26 +0100 with message-id <692af4a9-aa8c-f53e-2886-e977b11bd...@debian.org> and subject line Re: intel-ipsec-mb: FTBFS: dh_install: error: missing files, aborting has caused the Debian Bug report #1021831, regarding intel-ipsec-mb: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1021831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: intel-ipsec-mb Version: 1.3-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=intel-ipsec-mb=amd64=1.3-1=1664293055=0 dh_install -a dh_install: warning: Cannot find (any matches for) "docs/ipsec-mb_8h.html" (tried in ., debian/tmp) dh_install: warning: libipsec-mb-dev missing files: docs/ipsec-mb_8h.html dh_install: warning: Cannot find (any matches for) "docs/ipsec-mb_8h.js" (tried in ., debian/tmp) dh_install: warning: libipsec-mb-dev missing files: docs/ipsec-mb_8h.js dh_install: warning: Cannot find (any matches for) "docs/ipsec-mb_8h_source.html" (tried in ., debian/tmp) dh_install: warning: libipsec-mb-dev missing files: docs/ipsec-mb_8h_source.html dh_install: error: missing files, aborting make: *** [debian/rules:54: binary-arch] Error 25 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Version: 1.3-2 Hi Sebastian, On Sat, 15 Oct 2022 18:23:39 +0200 Sebastian Ramacher wrote: Source: intel-ipsec-mb Version: 1.3-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Version 1.3-2 did successfully build. Paul OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#1020576: please update sage for pari 2.15.0 and gap 4.12.0
Hi Tobias and Bill, On Wed, 19 Oct 2022 01:05:44 +0200 Bill Allombert wrote: > On Mon, Oct 17, 2022 at 08:44:52AM +, Tobias Hansen wrote: > > Control: block -1 by 1020436 1020456 > > > > Before sagemath can be fixed, cypari2 and giac have to be built against > > pari 2.15. There's a new release of cypari2 2.1.3 which has fixes for both, tests with pari 2.15 and also python3.11 fix (Bug#1024064) atleast as per commit messages (the current version of cypari2 is compatible w/ pari2.15 anyway tho) > OK, is there someone taking care of giac ? giac has already been uploaded/taken care of[1], and it has built with pari 2.15 Tobias, since this is done, would you consider to check sagemath now and get the ball rolling? :-) [1]: https://tracker.debian.org/news/1388406/accepted-giac-19029dfsg2-1-source-into-unstable/ -- Best, Nilesh signature.asc Description: PGP signature
Bug#1024852: nvidia-driver in bullseye (470.141.03-1~deb11u1) and bullseye-backports (470.103.01-1~bpo11+1) do not support Linux kernel 6.0 or later
On Sat, 26 Nov 2022 12:43:12 -0800 Alex Relis wrote: Package: nvidia-driver Version: 470.103.01-1~bpo11+1 Severity: grave Justification: renders package unusable Dear Maintainer, About a week ago, linux-image-6.0.0-0.deb11.2-amd64 was introduced in bullseye-backports. The problem is that the nvidia-driver version in both bullseye (470.141.03-1~deb11u1) and bullseye-backports (470.103.01-1~bpo11+1) (for some reason, the version in bullseye is newer which is strange) DO NOT support Linux kernel 6.0. When a user who uses a backported linux kernel and nvidia-driver upgrades their system, they will get an error message that looks like this https://imgur.com/sEVx1vc (sorry if I couldn't give you the text output; I am reporting this on behalf of a friend) This issue is reproducable and happened on two of my friends' machines. We found a current workaround that involves booting to kernel 5.1x in the Grub menu, running sudo apt purge linux-image-6.0.0-0.deb11.2-amd64 && sudo apt install -t bullseye-backports nvidia-driver && sudo reboot now. So what is the proposal there? Just do not install 6.0 kernel from backports if you need nvidia driver? According to this Phoronix article ( https://www.phoronix.com/news/NVIDIA-515.76-Linux-Driver ), nvidia-driver 515.76 or newer support Linux kernel 6.0. I believe the solution is to upgrade nvidia-driver to 515.76 or newer in bullseye-backports so that users can use their graphics card on kernel 6.0. As you state yourself, this bug is already fixed in the more recent version of the package. Why are you a) filing a bug which is already fixed in Debian, and b) why are you filing it against the bpo version of the package? It is like installing this version of driver breaks system. (especially since apt will not install this version, since a more recent version is available in bullseye already). It is a very questionable bug report, and for me as a maintainer (not of this package though) it discourages me from doing more backports (just a personal opinion/feeling). /mjt
Bug#1024481: marked as done (fwknop: FTBFS against libgpgme-dev >= 1.18.0-2 [--with-gpgme was given, but test for gpgme failed])
Your message dated Sun, 27 Nov 2022 03:49:05 + with message-id and subject line Bug#1024481: fixed in fwknop 2.6.10-14 has caused the Debian Bug report #1024481, regarding fwknop: FTBFS against libgpgme-dev >= 1.18.0-2 [--with-gpgme was given, but test for gpgme failed] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1024481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024481 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fwknop Version: 2.6.10-13 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: pkg-gnupg-ma...@lists.alioth.debian.org Usertags: gpgme-config-transition fwknop ships an outdated version of gpgme.m4 in m4/ which cannot handle the transition from gpgme-config to gpgrt-config. Deleteing the outdated copy lets the build succeed. cu Andreas --- fwknop-2.6.10.orig/m4/gpgme.m4 +++ /dev/null @@ -1,307 +0,0 @@ -# gpgme.m4 - autoconf macro to detect GPGME. -# Copyright (C) 2002, 2003, 2004 g10 Code GmbH -# -# This file is free software; as a special exception the author gives -# unlimited permission to copy and/or distribute it, with or without -# modifications, as long as this notice is preserved. -# -# This file is distributed in the hope that it will be useful, but -# WITHOUT ANY WARRANTY, to the extent permitted by law; without even the -# implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. - - -AC_DEFUN([_AM_PATH_GPGME_CONFIG], -[ AC_ARG_WITH(gpgme-prefix, -AC_HELP_STRING([--with-gpgme-prefix=PFX], - [prefix where GPGME is installed (optional)]), - gpgme_config_prefix="$withval", gpgme_config_prefix="") - if test "x$gpgme_config_prefix" != x ; then - GPGME_CONFIG="$gpgme_config_prefix/bin/gpgme-config" - fi - AC_PATH_PROG(GPGME_CONFIG, gpgme-config, no) - - if test "$GPGME_CONFIG" != "no" ; then -gpgme_version=`$GPGME_CONFIG --version` - fi - gpgme_version_major=`echo $gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\1/'` - gpgme_version_minor=`echo $gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\2/'` - gpgme_version_micro=`echo $gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\3/'` -]) - -dnl AM_PATH_GPGME([MINIMUM-VERSION, -dnl [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND ]]]) -dnl Test for libgpgme and define GPGME_CFLAGS and GPGME_LIBS. -dnl -AC_DEFUN([AM_PATH_GPGME], -[ AC_REQUIRE([_AM_PATH_GPGME_CONFIG])dnl - tmp=ifelse([$1], ,1:0.4.2,$1) - if echo "$tmp" | grep ':' >/dev/null 2>/dev/null ; then - req_gpgme_api=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\1/'` - min_gpgme_version=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\2/'` - else - req_gpgme_api=0 - min_gpgme_version="$tmp" - fi - - AC_MSG_CHECKING(for GPGME - version >= $min_gpgme_version) - ok=no - if test "$GPGME_CONFIG" != "no" ; then -req_major=`echo $min_gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\1/'` -req_minor=`echo $min_gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\2/'` -req_micro=`echo $min_gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\3/'` -if test "$gpgme_version_major" -gt "$req_major"; then -ok=yes -else -if test "$gpgme_version_major" -eq "$req_major"; then -if test "$gpgme_version_minor" -gt "$req_minor"; then - ok=yes -else - if test "$gpgme_version_minor" -eq "$req_minor"; then - if test "$gpgme_version_micro" -ge "$req_micro"; then - ok=yes - fi - fi -fi -fi -fi - fi - if test $ok = yes; then - # If we have a recent GPGME, we should also check that the - # API is compatible. - if test "$req_gpgme_api" -gt 0 ; then -tmp=`$GPGME_CONFIG --api-version 2>/dev/null || echo 0` -if test "$tmp" -gt 0 ; then - if test "$req_gpgme_api" -ne "$tmp" ; then - ok=no - fi -fi - fi - fi - if test $ok = yes; then -GPGME_CFLAGS=`$GPGME_CONFIG --cflags` -GPGME_LIBS=`$GPGME_CONFIG --libs` -AC_MSG_RESULT(yes) -ifelse([$2], , :, [$2]) - else -GPGME_CFLAGS="" -GPGME_LIBS="" -AC_MSG_RESULT(no) -ifelse([$3], , :, [$3]) - fi - AC_SUBST(GPGME_CFLAGS) - AC_SUBST(GPGME_LIBS) -]) - -dnl AM_PATH_GPGME_PTH([MINIMUM-VERSION,
Bug#1024861: contextlib2: (autopkgtest) needs update for python3.11: 'mycontext' object does not support the context manager protocol
Source: contextlib2 Version: 0.6.0.post1-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of contextlib2 fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 contextlib2from testing0.6.0.post1-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/c/contextlib2/28706379/log.gz == ERROR: test_typo_enter (test_contextlib2.TestContextDecorator.test_typo_enter) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.rcsf_3a_/downtmp/autopkgtest_tmp/test_contextlib2.py", line 364, in test_typo_enter with mycontext(): TypeError: 'mycontext' object does not support the context manager protocol == ERROR: test_typo_exit (test_contextlib2.TestContextDecorator.test_typo_exit) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.rcsf_3a_/downtmp/autopkgtest_tmp/test_contextlib2.py", line 376, in test_typo_exit with mycontext(): TypeError: 'mycontext' object does not support the context manager protocol (missed __exit__ method) -- Ran 72 tests in 0.022s FAILED (errors=2) OpenPGP_signature Description: OpenPGP digital signature
Processed: contextlib2: (autopkgtest) needs update for python3.11: 'mycontext' object does not support the context manager protocol
Processing control commands: > affects -1 src:python3-defaults Bug #1024861 [src:contextlib2] contextlib2: (autopkgtest) needs update for python3.11: 'mycontext' object does not support the context manager protocol Added indication that 1024861 affects src:python3-defaults -- 1024861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024860: circuits: (autopkgtest) needs update for python3.11: cannot import name 'getargspec' from 'inspect'
Source: circuits Version: 3.1.0+ds1-3 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of circuits fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 circuits from testing3.1.0+ds1-3 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/c/circuits/28706378/log.gz Testing with python3.11: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/circuits/__init__.py", line 22, in from .core import Event File "/usr/lib/python3/dist-packages/circuits/core/__init__.py", line 12, in from .bridge import Bridge File "/usr/lib/python3/dist-packages/circuits/core/bridge.py", line 23, in from .handlers import handler File "/usr/lib/python3/dist-packages/circuits/core/handlers.py", line 9, in from inspect import getargspec ImportError: cannot import name 'getargspec' from 'inspect' (/usr/lib/python3.11/inspect.py) autopkgtest [14:13:56]: test autodep8-python3 OpenPGP_signature Description: OpenPGP digital signature
Processed: circuits: (autopkgtest) needs update for python3.11: cannot import name 'getargspec' from 'inspect'
Processing control commands: > affects -1 src:python3-defaults Bug #1024860 [src:circuits] circuits: (autopkgtest) needs update for python3.11: cannot import name 'getargspec' from 'inspect' Added indication that 1024860 affects src:python3-defaults -- 1024860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024860 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024859: cctbx: (autopkgtest) needs update for python3.11: initialization of scitbx_linalg_ext raised unreported exception
Source: cctbx
Version: 2022.9+ds2+~3.11.2+ds1-4
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
cctbx fails in testing when that autopkgtest is run with the binary
packages of python3-defaults from unstable. It passes when run with only
packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
cctbx from testing2022.9+ds2+~3.11.2+ds1-4
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/c/cctbx/28708326/log.gz
Testing cctbx with python3.11:
Discovering pytest tests for smtbx:
refinement/constraints/tests/test_disorder.py: 1
refinement/constraints/tests/test_occupancies.py: 1
refinement/constraints/tests/test_rigid.py: 9
refinement/constraints/tests/test_same_group.py: 2
ERRORS
___ ERROR collecting refinement/constraints/tests/test_direction.py
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
:1206: in _gcd_import
???
:1178: in _find_and_load
???
:1128: in _find_and_load_unlocked
???
:241: in _call_with_frames_removed
???
:1206: in _gcd_import
???
:1178: in _find_and_load
???
:1128: in _find_and_load_unlocked
???
:241: in _call_with_frames_removed
???
:1206: in _gcd_import
???
:1178: in _find_and_load
???
:1128: in _find_and_load_unlocked
???
:241: in _call_with_frames_removed
???
:1206: in _gcd_import
???
:1178: in _find_and_load
???
:1149: in _find_and_load_unlocked
???
:690: in _load_unlocked
???
:940: in exec_module
???
:241: in _call_with_frames_removed
???
/usr/lib/python3/dist-packages/smtbx/refinement/__init__.py:2: in
from cctbx import xray
/usr/lib/python3/dist-packages/cctbx/xray/__init__.py:4: in
from cctbx.xray.scatterer import *
/usr/lib/python3/dist-packages/cctbx/xray/scatterer.py:3: in
import cctbx.eltbx.xray_scattering
/usr/lib/python3/dist-packages/cctbx/eltbx/xray_scattering/__init__.py:2:
in
import scitbx.math.gaussian # base class for gaussian
/usr/lib/python3/dist-packages/scitbx/math/__init__.py:8: in
import scitbx.linalg.eigensystem
/usr/lib/python3/dist-packages/scitbx/linalg/__init__.py:2: in
from scitbx.linalg.ext import *
/usr/lib/python3/dist-packages/scitbx/linalg/ext.py:3: in
bp.import_ext("scitbx_linalg_ext")
/usr/lib/python3/dist-packages/boost_adaptbx/boost/python.py:22: in
import_ext
try: mod = __import__(name)
E SystemError: initialization of scitbx_linalg_ext raised unreported
exception
OpenPGP_signature
Description: OpenPGP digital signature
Processed: cctbx: (autopkgtest) needs update for python3.11: initialization of scitbx_linalg_ext raised unreported exception
Processing control commands: > affects -1 src:python3-defaults Bug #1024859 [src:cctbx] cctbx: (autopkgtest) needs update for python3.11: initialization of scitbx_linalg_ext raised unreported exception Added indication that 1024859 affects src:python3-defaults -- 1024859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024859 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: busco: (autopkgtest) needs update for python3.11: cannot import name '_aligners' from partially initialized module 'Bio.Align'
Processing control commands: > affects -1 src:python3-defaults Bug #1024858 [src:busco] busco: (autopkgtest) needs update for python3.11: cannot import name '_aligners' from partially initialized module 'Bio.Align' Added indication that 1024858 affects src:python3-defaults -- 1024858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024858: busco: (autopkgtest) needs update for python3.11: cannot import name '_aligners' from partially initialized module 'Bio.Align'
Source: busco Version: 5.4.3-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of busco fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 busco from testing5.4.3-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/b/busco/28706377/log.gz File series fully applied, ends at patch debian/patches/find-bbmap-instead-of-bbtools.patch Testing with python3.11 in /tmp/autopkgtest-lxc.firnv_xg/downtmp/autopkgtest_tmp: unittest_runner (unittest.loader._FailedTest.unittest_runner) ... ERROR == ERROR: unittest_runner (unittest.loader._FailedTest.unittest_runner) -- ImportError: Failed to import test module: unittest_runner Traceback (most recent call last): File "/usr/lib/python3.11/unittest/loader.py", line 154, in loadTestsFromName module = __import__(module_name) ^^^ File "/tmp/autopkgtest-lxc.firnv_xg/downtmp/autopkgtest_tmp/tests/unittest_runner.py", line 2, in from tests.unittests import run_BUSCO_unittests File "/tmp/autopkgtest-lxc.firnv_xg/downtmp/autopkgtest_tmp/tests/unittests/run_BUSCO_unittests.py", line 2, in from busco import run_BUSCO File "/usr/lib/python3/dist-packages/busco/run_BUSCO.py", line 25, in from busco.BuscoRunner import AnalysisRunner, BatchRunner, SingleRunner File "/usr/lib/python3/dist-packages/busco/BuscoRunner.py", line 2, in from busco.analysis.BuscoAnalysis import BuscoAnalysis File "/usr/lib/python3/dist-packages/busco/analysis/BuscoAnalysis.py", line 15, in from busco.busco_tools.hmmer import HMMERRunner File "/usr/lib/python3/dist-packages/busco/busco_tools/hmmer.py", line 7, in from Bio import SeqIO File "/usr/lib/python3/dist-packages/Bio/SeqIO/__init__.py", line 374, in from Bio.Align import MultipleSeqAlignment File "/usr/lib/python3/dist-packages/Bio/Align/__init__.py", line 18, in from Bio.Align import _aligners ImportError: cannot import name '_aligners' from partially initialized module 'Bio.Align' (most likely due to a circular import) (/usr/lib/python3/dist-packages/Bio/Align/__init__.py) -- Ran 1 test in 0.000s FAILED (errors=1) autopkgtest [14:14:42]: test run-unit-test OpenPGP_signature Description: OpenPGP digital signature
Bug#1024857: beaker: (autopkgtest) needs update for python3.11: python3.11: command not found
Source: beaker Version: 1.11.0-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of beaker fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 beaker from testing1.11.0-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. It seems that your tests tries to run against all supported python versions but doesn't secure that they are installed. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/b/beaker/28706376/log.gz [*] testing on python3.11: bash: line 1: python3.11: command not found autopkgtest [14:13:53]: test command1 OpenPGP_signature Description: OpenPGP digital signature
Processed: beaker: (autopkgtest) needs update for python3.11: python3.11: command not found
Processing control commands: > affects -1 src:python3-defaults Bug #1024857 [src:beaker] beaker: (autopkgtest) needs update for python3.11: python3.11: command not found Added indication that 1024857 affects src:python3-defaults -- 1024857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1023299
Processing commands for cont...@bugs.debian.org: > tags 1023299 + pending Bug #1023299 [ganeti-testsuite] ganeti-testsuite: yaml.load in testsuite needs to specify loader Bug #1022018 [ganeti-testsuite] ganeti: Uses deprecated yaml.load Added tag(s) pending. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1022018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022018 1023299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1021753
Processing commands for cont...@bugs.debian.org: > tags 1021753 + pending Bug #1021753 [src:ganeti] ganeti: conflicting curl build-depends Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1021753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021753 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024856: azure-cli: (autopkgtest) needs update for python3.11: conflicting subparser: configure
Source: azure-cli
Version: 2.42.0-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
azure-cli fails in testing when that autopkgtest is run with the binary
packages of python3-defaults from unstable. It passes when run with only
packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
azure-cli from testing2.42.0-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/a/azure-cli/28706375/log.gz
_ ERROR at teardown of
ConfigureGlobalDefaultsTest.test_configure_global_defaults _
self = testMethod=test_configure_global_defaults>
def tearDown(self):
self.cmd('configure --defaults global="" global2=""')
tests_core/test_configure.py:33: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/azure/cli/testsdk/base.py:170: in cmd
return execute(self.cli_ctx, command,
expect_failure=expect_failure).assert_with_checks(checks)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
self =
cli_ctx =
command = 'configure --defaults global="" global2=""', expect_failure =
False
def __init__(self, cli_ctx, command, expect_failure=False):
self.output = ''
self.applog = ''
self.command_coverage = {}
cli_ctx.data['_cache'] = None
if os.environ.get(ENV_COMMAND_COVERAGE, None):
with open(COVERAGE_FILE, 'a') as coverage_file:
if command.startswith('az '):
command = command[3:]
coverage_file.write(command + '\n')
self._in_process_execute(cli_ctx, command,
expect_failure=expect_failure)
log_val = ('Logging ' + self.applog) if self.applog else ''
if expect_failure and self.exit_code == 0:
logger.error('Command "%s" => %d. (It did not fail as
expected). %s\n', command,
self.exit_code, log_val)
raise AssertionError('The command did not fail as it was
expected.')
if not expect_failure and self.exit_code != 0:
logger.error('Command "%s" => %d. %s\n', command,
self.exit_code, log_val)
raise AssertionError('The command failed. Exit code:
{}'.format(self.exit_code))
E AssertionError: The command failed. Exit code: 1
/usr/lib/python3/dist-packages/azure/cli/testsdk/base.py:253: AssertionError
- Captured stderr call
-
To check existing issues, please visit:
https://github.com/Azure/azure-cli/issues
To open a new issue, please run `az feedback`
To check existing issues, please visit:
https://github.com/Azure/azure-cli/issues
To open a new issue, please run `az feedback`
-- Captured log call
---
INFO az_command_data_logger:azlogging.py:128 command args: configure
--defaults {}
ERRORcli.azure.cli.core.azclierror:azlogging.py:212 The command
failed with an unexpected error. Here is the traceback:
ERRORaz_command_data_logger:azlogging.py:213 The command failed with
an unexpected error. Here is the traceback:
ERRORcli.azure.cli.core.azclierror:azlogging.py:212 argument
_command_package: conflicting subparser: configure
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/knack/cli.py", line 233, in invoke
cmd_result = self.invocation.execute(args)
^
File
"/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py",
line 565, in execute
self.parser.load_command_table(self.commands_loader)
File "/usr/lib/python3/dist-packages/azure/cli/core/parser.py", line
100, in load_command_table
command_parser = subparser.add_parser(command_verb,
^^
File "/usr/lib/python3.11/argparse.py", line 1197, in add_parser
raise ArgumentError(self, _('conflicting subparser: %s') % name)
argparse.ArgumentError: argument _command_package: conflicting
Bug#1024855: augur: (autopkgtest) needs update for python3.11: cannot import name '_aligners' from partially
Source: augur Version: 18.1.2-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of augur fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 augur from testing18.1.2-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/a/augur/28706374/log.gz = test session starts == platform linux -- Python 3.11.0+, pytest-7.1.2, pluggy-1.0.0+repack -- /usr/bin/python3.11 cachedir: .pytest_cache rootdir: /tmp/autopkgtest-lxc.cskdmo0l/downtmp/build.nDH/src plugins: mock-3.8.2 collecting ... collected 10 items / 21 errors ERRORS _ ERROR collecting tests/test_align.py _ ImportError while importing test module '/tmp/autopkgtest-lxc.cskdmo0l/downtmp/build.nDH/src/tests/test_align.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.11/importlib/__init__.py:126: in import_module return _bootstrap._gcd_import(name[level:], package, level) tests/test_align.py:10: in from Bio import SeqIO /usr/lib/python3/dist-packages/Bio/SeqIO/__init__.py:374: in from Bio.Align import MultipleSeqAlignment /usr/lib/python3/dist-packages/Bio/Align/__init__.py:18: in from Bio.Align import _aligners E ImportError: cannot import name '_aligners' from partially initialized module 'Bio.Align' (most likely due to a circular import) (/usr/lib/python3/dist-packages/Bio/Align/__init__.py) ERROR collecting tests/test_clades.py _ ImportError while importing test module '/tmp/autopkgtest-lxc.cskdmo0l/downtmp/build.nDH/src/tests/test_clades.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.11/importlib/__init__.py:126: in import_module return _bootstrap._gcd_import(name[level:], package, level) tests/test_clades.py:6: in from augur.clades import read_in_clade_definitions augur/__init__.py:12: in from treetime import TreeTimeError, TreeTimeUnknownError /usr/lib/python3/dist-packages/treetime/__init__.py:32: in from .treeanc import TreeAnc /usr/lib/python3/dist-packages/treetime/treeanc.py:4: in from Bio import Phylo /usr/lib/python3/dist-packages/Bio/Phylo/__init__.py:14: in from Bio.Phylo._io import parse, read, write, convert /usr/lib/python3/dist-packages/Bio/Phylo/_io.py:16: in from Bio.Phylo import BaseTree, NewickIO, NexusIO, PhyloXMLIO, NeXMLIO /usr/lib/python3/dist-packages/Bio/Phylo/PhyloXMLIO.py:24: in from Bio.Phylo import PhyloXML as PX /usr/lib/python3/dist-packages/Bio/Phylo/PhyloXML.py:22: in from Bio.Align import MultipleSeqAlignment /usr/lib/python3/dist-packages/Bio/Align/__init__.py:18: in from Bio.Align import _aligners E ImportError: cannot import name '_aligners' from partially initialized module 'Bio.Align' (most likely due to a circular import) (/usr/lib/python3/dist-packages/Bio/Align/__init__.py) _ ERROR collecting tests/test_dates.py _ ImportError while importing test module '/tmp/autopkgtest-lxc.cskdmo0l/downtmp/build.nDH/src/tests/test_dates.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.11/importlib/__init__.py:126: in import_module return _bootstrap._gcd_import(name[level:], package, level) tests/test_dates.py:4: in from augur import dates augur/__init__.py:12: in from treetime import TreeTimeError, TreeTimeUnknownError /usr/lib/python3/dist-packages/treetime/__init__.py:32: in from .treeanc import TreeAnc /usr/lib/python3/dist-packages/treetime/treeanc.py:4: in from Bio import Phylo /usr/lib/python3/dist-packages/Bio/Phylo/__init__.py:14: in from Bio.Phylo._io import parse, read, write, convert
Processed: azure-cli: (autopkgtest) needs update for python3.11: conflicting subparser: configure
Processing control commands: > affects -1 src:python3-defaults Bug #1024856 [src:azure-cli] azure-cli: (autopkgtest) needs update for python3.11: conflicting subparser: configure Added indication that 1024856 affects src:python3-defaults -- 1024856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024856 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: augur: (autopkgtest) needs update for python3.11: cannot import name '_aligners' from partially
Processing control commands: > affects -1 src:python3-defaults Bug #1024855 [src:augur] augur: (autopkgtest) needs update for python3.11: cannot import name '_aligners' from partially Added indication that 1024855 affects src:python3-defaults -- 1024855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: aiotask-context: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'
Processing control commands: > affects -1 src:python3-defaults Bug #1024854 [src:aiotask-context] aiotask-context: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine' Added indication that 1024854 affects src:python3-defaults -- 1024854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024854: aiotask-context: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'
Source: aiotask-context Version: 0.6.1-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of aiotask-context fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 aiotask-contextfrom testing0.6.1-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. E.g.: """ Removed the @asyncio.coroutine() decorator enabling legacy generator-based coroutines to be compatible with async / await code. The function has been deprecated since Python 3.8 and the removal was initially scheduled for Python 3.10. Use async def instead. (Contributed by Illia Volochii in bpo-43216.) """ More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/a/aiotask-context/28706372/log.gz = test session starts == platform linux -- Python 3.11.0+, pytest-7.1.2, pluggy-1.0.0+repack -- /usr/bin/python3.11 cachedir: .pytest_cache rootdir: /tmp/autopkgtest-lxc.xpxnssx6/downtmp/autopkgtest_tmp collecting ... collected 0 items / 1 error ERRORS __ ERROR collecting tests/test_acceptance.py ___ tests/test_acceptance.py:11: in @asyncio.coroutine E AttributeError: module 'asyncio' has no attribute 'coroutine' === short test summary info ERROR tests/test_acceptance.py - AttributeError: module 'asyncio' has no attr... !! stopping after 1 failures !!! === 1 error in 0.02s === autopkgtest [14:13:59]: test run-tests OpenPGP_signature Description: OpenPGP digital signature
Processed: billiard migrated
Processing commands for cont...@bugs.debian.org: > # while the out-of-sync situation resolved itself somehow, for upgrades > # it's still nice to have the versioned breaks > severity 1024161 normal Bug #1024161 [src:billiard] src:billiard: please add a versioned Breaks on celery Severity set to 'normal' from 'serious' > user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was elb...@debian.org). > usertag 1024161 - out-of-sync Usertags were: out-of-sync. There are now no usertags set. > thanks Stopping processing here. Please contact me if you need assistance. -- 1024161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024161 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024852: nvidia-driver in bullseye (470.141.03-1~deb11u1) and bullseye-backports (470.103.01-1~bpo11+1) do not support Linux kernel 6.0 or later
Package: nvidia-driver Version: 470.103.01-1~bpo11+1 Severity: grave Justification: renders package unusable Dear Maintainer, About a week ago, linux-image-6.0.0-0.deb11.2-amd64 was introduced in bullseye-backports. The problem is that the nvidia-driver version in both bullseye (470.141.03-1~deb11u1) and bullseye-backports (470.103.01-1~bpo11+1) (for some reason, the version in bullseye is newer which is strange) DO NOT support Linux kernel 6.0. When a user who uses a backported linux kernel and nvidia-driver upgrades their system, they will get an error message that looks like this https://imgur.com/sEVx1vc (sorry if I couldn't give you the text output; I am reporting this on behalf of a friend) This issue is reproducable and happened on two of my friends' machines. We found a current workaround that involves booting to kernel 5.1x in the Grub menu, running sudo apt purge linux-image-6.0.0-0.deb11.2-amd64 && sudo apt install -t bullseye-backports nvidia-driver && sudo reboot now. According to this Phoronix article ( https://www.phoronix.com/news/NVIDIA-515.76-Linux-Driver ), nvidia-driver 515.76 or newer support Linux kernel 6.0. I believe the solution is to upgrade nvidia-driver to 515.76 or newer in bullseye-backports so that users can use their graphics card on kernel 6.0. Thank you for reading my bug report and I hope you guys have a great day! -- Alex Relis
Bug#1024831: Acknowledgement (xorg: xserver fails to resume after suspend-to-disk)
Hi, some additional information: This issue only happens only with linux-image-6.0.0-0.deb11.2-amd64 After I booted the old linux-image-5.19.0-0.deb11.2-amd64, the issue does not occur. Best regards, Klaus. -- Klaus Singvogel GnuPG-Key-ID: 1024R/5068792D 1994-06-27
Bug#1024828: marked as done (src:r-cran-igraph: fails to migrate to testing for too long: autopkgtest regression on i386)
Your message dated Sat, 26 Nov 2022 19:37:49 + with message-id and subject line Bug#1024828: fixed in r-cran-lexrankr 0.5.2-3 has caused the Debian Bug report #1024828, regarding src:r-cran-igraph: fails to migrate to testing for too long: autopkgtest regression on i386 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1024828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-igraph Version: 1.3.4-1 Severity: serious Control: close -1 1.3.5-1 Tags: sid bookworm 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 60 days as having a Release Critical bug in testing [1]. Your package src:r-cran-igraph has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package causes a regression in r-cran-lexrankr on i386. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=r-cran-igraph OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: r-cran-lexrankr Source-Version: 0.5.2-3 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of r-cran-lexrankr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-cran-lexrankr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 26 Nov 2022 20:13:58 +0100 Source: r-cran-lexrankr Architecture: source Version: 0.5.2-3 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Closes: 1024828 Changes: r-cran-lexrankr (0.5.2-3) unstable; urgency=medium . * Set tolerance for test Closes: #1024828 * Standards-Version: 4.6.1 (routine-update) * Reorder sequence of d/control fields by cme (routine-update) * Set upstream metadata fields: Bug-Database, Bug-Submit. * lintian-overrides (see lintian bug #1017966) Checksums-Sha1: 3bfa7a517b15d01cf1eee7cb84b748cac96acb41 2157 r-cran-lexrankr_0.5.2-3.dsc 0d5f9791fe59d973ea27e362e8e7f091694db988 3824 r-cran-lexrankr_0.5.2-3.debian.tar.xz 7c97bbcc89a6e15b583c48bcb088d4b3f37eea91 11131 r-cran-lexrankr_0.5.2-3_amd64.buildinfo Checksums-Sha256: e4b1e4bf841050a2ff98431bca6c19899f1909393855c983f25f67e3bcb8a1e4 2157 r-cran-lexrankr_0.5.2-3.dsc 3ca0a14f916c6a89d62a77dec2ec3e19a810d39f89b23ca8a0fcb834e30dd17f 3824 r-cran-lexrankr_0.5.2-3.debian.tar.xz 2c6d83b6a522dd0d5bb20b65d8a31b18afd2bc7cd6c84d36c55780092f4a9363 11131 r-cran-lexrankr_0.5.2-3_amd64.buildinfo Files: bbf2160ee450340a7fdde84f54e37f90 2157 gnu-r optional r-cran-lexrankr_0.5.2-3.dsc 9b9966e31cceba1f32cf1b33625ace84 3824 gnu-r optional r-cran-lexrankr_0.5.2-3.debian.tar.xz 95cfd1df97a97cf517fb692f94d0505f 11131 gnu-r optional r-cran-lexrankr_0.5.2-3_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#1008828: marked as pending in spf-engine
Control: tag -1 pending Hello, Bug #1008828 in spf-engine reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/spf-engine/-/commit/bbb3b8cfa4ffd883d47bfb29b9efb36b9681b369 Add d/p/0002-fix-leftover-import.patch from upstream to fix pyspf-milter failing to start due to an invalid import statement (Closes: #1008828) (this message was generated automatically) -- Greetings https://bugs.debian.org/1008828
Processed: Bug#1008828 marked as pending in spf-engine
Processing control commands: > tag -1 pending Bug #1008828 [python3-spf-engine] python3-spf-engine: fails with ImportError: cannot import name 'own_socketfile' from 'spf_engine.util' Added tag(s) pending. -- 1008828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1023025: marked as done (linux-image-6.0.0-2-686: kernel BUG at mm/memory.c:2660!)
Your message dated Sat, 26 Nov 2022 19:00:11 + with message-id and subject line Bug#1023025: fixed in linux 6.0.10-1 has caused the Debian Bug report #1023025, regarding linux-image-6.0.0-2-686: kernel BUG at mm/memory.c:2660! to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1023025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.0.3-1 Severity: grave Tags: a11y Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: ** Version: Linux version 6.0.0-2-686 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-5) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39) #1 SMP PREEMPT_DYNAMIC Debian 6.0.3-1 (2022-10-21) ** Command line: BOOT_IMAGE=/boot/vmlinuz-6.0.0-2-686 root=UUID=ae4affb9-b1b9-4ee7-89f9-f74034b3d28b ro single ** Not tainted ** Kernel log: Oct 29 11:33:39 [localhost] kernel: [ 77.829921] [ cut here ] Oct 29 11:33:39 [localhost] kernel: [ 77.829942] kernel BUG at mm/memory.c:2660! Oct 29 11:33:39 [localhost] kernel: [ 77.829961] invalid opcode: [#1] PREEMPT SMP Oct 29 11:33:39 [localhost] kernel: [ 77.829975] CPU: 0 PID: 649 Comm: Xorg Not tainted 6.0.0-2-686 #1 Debian 6.0.3-1 Oct 29 11:33:39 [localhost] kernel: [ 77.829989] Hardware name: Dell Inc. MM061 /0KD882, BIOS A17 06/13/2007 Oct 29 11:33:39 [localhost] kernel: [ 77.829998] EIP: __apply_to_page_range+0x370/0x470 Oct 29 11:33:39 [localhost] kernel: [ 77.830019] Code: 8b 7d cc 81 7d e4 e0 46 c4 cb 74 0e 89 c2 e9 71 ff ff ff 8d b4 26 00 00 00 00 8b 7d d8 89 c1 e9 3f fd ff ff 8d b6 00 00 00 00 <0f> 0b 8d b6 00 00 00 00 85 c0 0f 84 c3 00 00 00 89 f7 89 c2 c1 ef Oct 29 11:33:39 [localhost] kernel: [ 77.830032] EAX: 0001 EBX: a900 ECX: c2e13a8c EDX: 02a3 Oct 29 11:33:39 [localhost] kernel: [ 77.830043] ESI: a8f9 EDI: a97f EBP: c26b3dcc ESP: c26b3d90 Oct 29 11:33:39 [localhost] kernel: [ 77.830053] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 EFLAGS: 00210202 Oct 29 11:33:39 [localhost] kernel: [ 77.830066] CR0: 80050033 CR2: a8f9 CR3: 02e13000 CR4: 06d0 Oct 29 11:33:39 [localhost] kernel: [ 77.830077] Call Trace: Oct 29 11:33:39 [localhost] kernel: [ 77.830090] ? ktime_get_mono_fast_ns+0x3f/0xe0 Oct 29 11:33:39 [localhost] kernel: [ 77.830109] apply_to_page_range+0x15/0x20 Oct 29 11:33:39 [localhost] kernel: [ 77.830126] ? i915_memcpy_init_early+0x30/0x30 [i915] Oct 29 11:33:39 [localhost] kernel: [ 77.830394] remap_io_mapping+0x62/0xa0 [i915] Oct 29 11:33:39 [localhost] kernel: [ 77.830650] ? i915_memcpy_init_early+0x30/0x30 [i915] Oct 29 11:33:39 [localhost] kernel: [ 77.830910] vm_fault_gtt+0x2fb/0x750 [i915] Oct 29 11:33:39 [localhost] kernel: [ 77.831214] ? __mod_lruvec_state+0x29/0x30 Oct 29 11:33:39 [localhost] kernel: [ 77.831231] ? __mod_lruvec_page_state+0x69/0xb0 Oct 29 11:33:39 [localhost] kernel: [ 77.831247] __do_fault+0x2c/0x120 Oct 29 11:33:39 [localhost] kernel: [ 77.831261] handle_mm_fault+0xa59/0x1020 Oct 29 11:33:39 [localhost] kernel: [ 77.831284] do_user_addr_fault+0x18d/0x500 Oct 29 11:33:39 [localhost] kernel: [ 77.831301] exc_page_fault+0x51/0x160 Oct 29 11:33:39 [localhost] kernel: [ 77.831318] ? paravirt_BUG+0x10/0x10 Oct 29 11:33:39 [localhost] kernel: [ 77.831331] handle_exception+0x133/0x133 Oct 29 11:33:39 [localhost] kernel: [ 77.831346] EIP: 0xb6feff37 Oct 29 11:33:39 [localhost] kernel: [ 77.831358] Code: 83 c4 10 85 c0 0f 85 d8 00 00 00 8b 44 24 30 8b 74 24 0c 89 46 54 e9 02 ff ff ff 8d b4 26 00 00 00 00 90 8b 44 24 0c 8b 40 28 00 00 00 00 00 8b 44 24 10 8d 90 e0 23 00 00 8b 02 83 e8 01 89 Oct 29 11:33:39 [localhost] kernel: [ 77.831370] EAX: a8f9 EBX: b718f000 ECX: EDX: Oct 29 11:33:39 [localhost] kernel: [ 77.831380] ESI: 0263dd60 EDI: b718f000 EBP: b6739000 ESP: bfe81970 Oct 29 11:33:39 [localhost] kernel: [ 77.831391] DS: 007b ES: 007b FS: GS: 0033 SS: 007b EFLAGS: 00210246 Oct 29 11:33:39 [localhost] kernel: [ 77.831406] ? paravirt_BUG+0x10/0x10 Oct 29 11:33:39 [localhost] kernel: [ 77.831422] Modules linked
Bug#1024561: Unmaintained, keep out of stable
[1] RFC8482 responds to ANY in such as way as to not break Qmail On Sat, Nov 26, 2022 at 10:34 AM Sam Trenholme wrote: > > Upstream here again. I have released MaraDNS 3.5.0030 and 3.4.09 with > a security update: MaraDNS now fully supports RFC8482, which means > MaraDNS no longer supports ANY records. [1] While MaraDNS does not > have long packet support, this removes one possible denial of service > amplification path. > > If someone can not step up to plate to maintain MaraDNS for Debian, we > should deprecate and eventually remove the package. > > I may end up making my own .deb files for MaraDNS. > > -- Sam > > On Mon, Nov 21, 2022 at 5:03 AM Moritz Muehlenhoff wrote: > > > > Source: maradns > > Version: 2.0.13-1.4 > > Severity: serious > > > > The last maintainer upload was in 2015 and the version currently in the > > archive is way behind current upstream releases (which is at 3.4.07), > > we have plenty of maintained DNS servers, keep it out of testing ( > > and if noone picks it up, remove it from the archive). > >
Bug#1024561: Unmaintained, keep out of stable
Upstream here again. I have released MaraDNS 3.5.0030 and 3.4.09 with a security update: MaraDNS now fully supports RFC8482, which means MaraDNS no longer supports ANY records. [1] While MaraDNS does not have long packet support, this removes one possible denial of service amplification path. If someone can not step up to plate to maintain MaraDNS for Debian, we should deprecate and eventually remove the package. I may end up making my own .deb files for MaraDNS. -- Sam On Mon, Nov 21, 2022 at 5:03 AM Moritz Muehlenhoff wrote: > > Source: maradns > Version: 2.0.13-1.4 > Severity: serious > > The last maintainer upload was in 2015 and the version currently in the > archive is way behind current upstream releases (which is at 3.4.07), > we have plenty of maintained DNS servers, keep it out of testing ( > and if noone picks it up, remove it from the archive). >
Bug#1024773: libpresage-doc: missing Breaks+Replaces: libpresage-dev (<< 0.9.1-2.4)
Hi Andreas, On Thu, Nov 24, 2022 at 05:30:16PM +0100, Andreas Beckmann wrote: > Package: libpresage-doc > Version: 0.9.1-2.4 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'testing'. > It installed fine in 'testing', then the upgrade to 'sid' fails > because it tries to overwrite other packages files without declaring a > Breaks+Replaces relation. > > See policy 7.6 at > https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces > > >From the attached log (scroll to the bottom...): > > Selecting previously unselected package libpresage-dev:amd64. > Preparing to unpack .../libpresage-dev_0.9.1-2.3_amd64.deb ... > Unpacking libpresage-dev:amd64 (0.9.1-2.3) ... > dpkg: error processing archive > /var/cache/apt/archives/libpresage-dev_0.9.1-2.3_amd64.deb (--unpack): >trying to overwrite > '/usr/share/doc/libpresage-dev/getting_started.txt.gz', which is also in > package libpresage-doc 0.9.1-2.4 > Errors were encountered while processing: >/var/cache/apt/archives/libpresage-dev_0.9.1-2.3_amd64.deb I'll prepare another NMU to fix that. -- Guido > > > cheers, > > Andreas
Bug#1024395: CONFIG_INTEGRITY_PLATFORM_KEYRING was missing for mokutil --list-enrolled to work
CONFIG_INTEGRITY_PLATFORM_KEYRING=y But the bug is still there -- eric
Processed: Wrong soversion in libfm-qt11=1.2.0-1
Processing control commands: > severity -1 serious Bug #1024687 [libfm-qt11] libfm-qt11:amd64 1.1.0-3 -> 1.2.0-1 breaks some lxqt functionalities Severity set to 'serious' from 'normal' -- 1024687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 887834 in 0.23.3-1
Processing commands for cont...@bugs.debian.org:
> notfound 887834 0.23.3-1
Bug #887834 {Done: Florian Schlichting } [mpd] mpd
installation fails, cannot open /var/lib/mpd/tag_cache, /run/mpd/pid
No longer marked as found in versions mpd/0.23.3-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
887834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1024844: notary: FTBFS: cannot use _protobuf.Empty{} (value of type *empty.Empty) as type *emptypb.Empty in argument to s.client.ListFiles
Source: notary
Version: 0.7.0+ds1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
notary appears to be failing to build due to a protobuf-related
error. In a clean sid schroot:
> cd _build && go install -trimpath -v -p 16 -tags pkcs11
> github.com/theupdateframework/notary
> github.com/theupdateframework/notary/client
> github.com/theupdateframework/notary/client/changelist
> github.com/theupdateframework/notary/cmd/escrow
> github.com/theupdateframework/notary/cmd/notary
> github.com/theupdateframework/notary/cmd/notary-server
> github.com/theupdateframework/notary/cmd/notary-signer
> github.com/theupdateframework/notary/cryptoservice
> github.com/theupdateframework/notary/passphrase
> github.com/theupdateframework/notary/proto
> github.com/theupdateframework/notary/server
> github.com/theupdateframework/notary/server/errors
> github.com/theupdateframework/notary/server/handlers
> github.com/theupdateframework/notary/server/snapshot
> github.com/theupdateframework/notary/server/storage
> github.com/theupdateframework/notary/server/timestamp
> github.com/theupdateframework/notary/signer
> github.com/theupdateframework/notary/signer/api
> github.com/theupdateframework/notary/signer/client
> github.com/theupdateframework/notary/signer/keydbstore
> github.com/theupdateframework/notary/storage
> github.com/theupdateframework/notary/storage/rethinkdb
> github.com/theupdateframework/notary/trustmanager
> github.com/theupdateframework/notary/trustmanager/remoteks
> github.com/theupdateframework/notary/trustmanager/yubikey
> github.com/theupdateframework/notary/trustpinning
> github.com/theupdateframework/notary/tuf
> github.com/theupdateframework/notary/tuf/data
> github.com/theupdateframework/notary/tuf/signed
> github.com/theupdateframework/notary/tuf/testutils
> github.com/theupdateframework/notary/tuf/testutils/interfaces
> github.com/theupdateframework/notary/tuf/testutils/keys
> github.com/theupdateframework/notary/tuf/utils
> github.com/theupdateframework/notary/tuf/validation
> github.com/theupdateframework/notary/utils
> github.com/theupdateframework/notary/version
>
> [snip]
>
> # github.com/theupdateframework/notary/trustmanager/remoteks
> src/github.com/theupdateframework/notary/trustmanager/remoteks/client
> .go:105:37: cannot use _protobuf.Empty{} (value of type
> *empty.Empty) as type *emptypb.Empty in argument to
> s.client.ListFiles
signature.asc
Description: This is a digitally signed message part
Bug#1021060: apt-clone fails when the lsb_release Python module is not available
UPDATE to my 10/20/22 post. After a rebuild of my system a month after this post, it turns out (for me at least and may not be related), 2 things appeared to have happened. 1. It appears that almost all the apps to be installed using apt-clone restore, I am seeing broken packages shortly after starting the process. The "broken" apps appear to be better than 90% of all apps installed. Of course, the process never finishes correctly and the system runs fine both before and after since nothing was applied . 2. It appears that apt-clone overwrites the files that are patched - I wonder if this could have produced the issue above. I have tippled checked that patches are applied properly and simply running apt-clone without parms runs properly without issues (then again, it's not doing anything). I realize that trying an apt-clone after 30 days that packages may be out of sync from the archived file to what would be pulled down, but before this bug appeared, I don't recall having this issue going back in time even with more than 30 days since the last apt-clone restore. To date, I have not really found an efficient way to restore from something so I continue to keep an eye on this bug and have shelved Debian for now. -- Keep well, Chris <><
Bug#1005044: marked as done (python3-subnettree: package completely broken, module won't load)
Your message dated Sat, 26 Nov 2022 13:02:17 +
with message-id
and subject line Bug#1005044: fixed in pysubnettree 0.33-1+deb11u1
has caused the Debian Bug report #1005044,
regarding python3-subnettree: package completely broken, module won't load
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1005044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-subnettree
Version: 0.33-1+b3
Severity: grave
Justification: renders package unusable
Documentation says:
A simple example which associates CIDR prefixes with strings::
>>> import SubnetTree
>>> t = SubnetTree.SubnetTree()
>>> t["10.1.0.0/16"] = "Network 1"
>>> t["10.1.42.0/24"] = "Network 1, Subnet 42"
>>> print("10.1.42.1" in t)
True
But the version in bullseye (and 0.35 currently in unstable) produce:
Python 3.9.2 (default, Feb 28 2021, 17:03:44)
[GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import SubnetTree
>>> t = SubnetTree.SubnetTree()
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/SubnetTree.py", line 82, in __init__
_SubnetTree.SubnetTree_swiginit(self,
_SubnetTree.new_SubnetTree(binary_lookup_mode))
AttributeError: module '_SubnetTree' has no attribute 'SubnetTree_swiginit'
>>>
-- System Information:
Debian Release: 11.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-10-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-subnettree depends on:
ii libc6 2.31-13+deb11u2
ii libgcc-s1 10.2.1-6
ii libstdc++6 10.2.1-6
ii python3 3.9.2-3
python3-subnettree recommends no packages.
python3-subnettree suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pysubnettree
Source-Version: 0.33-1+deb11u1
Done: Scott Kitterman
We believe that the bug you reported is fixed in the latest version of
pysubnettree, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1005...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Scott Kitterman (supplier of updated pysubnettree package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 03 Nov 2022 16:09:00 -0400
Source: pysubnettree
Architecture: source
Version: 0.33-1+deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Scott Kitterman
Closes: 1005044
Changes:
pysubnettree (0.33-1+deb11u1) bullseye; urgency=medium
.
* Fix moving/copying files in debian/rules so as not to leave a mix of
rebuilt and non-rebuilt files in the binary and update clean rule
(Closes: #1005044)
Checksums-Sha1:
4135de96090202bc54b4ddf857f83e1d60c7c32f 2345 pysubnettree_0.33-1+deb11u1.dsc
db115eb8091cc1d82552e51a8dc19e3feb073385 12464
pysubnettree_0.33-1+deb11u1.debian.tar.xz
09dc1c74b455df25ade2f47a40ff93f1ed89757a 6494
pysubnettree_0.33-1+deb11u1_source.buildinfo
Checksums-Sha256:
49884fe6bfe620484d3d60bb56751aebb9b94157a16c028712d1004200c8df43 2345
pysubnettree_0.33-1+deb11u1.dsc
dbac9394957f1e604c096de66010e53a13a7a4c72de440a0065995f1bec9e0c2 12464
pysubnettree_0.33-1+deb11u1.debian.tar.xz
2cebc38b9eb3596160be5c940d02ce0ca472f1f6b19c28f132cfcdd7de561217 6494
pysubnettree_0.33-1+deb11u1_source.buildinfo
Files:
2bd5644b479787c69c83bc770de5b0b8 2345 python optional
pysubnettree_0.33-1+deb11u1.dsc
6438addc3163003882b8f01d1dc29799 12464 python optional
pysubnettree_0.33-1+deb11u1.debian.tar.xz
8bbf0cd0609a563dc6694975edf5147d 6494 python optional
pysubnettree_0.33-1+deb11u1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE53Kb/76FQA/u7iOxeNfe+5rVmvEFAmNkIE0ACgkQeNfe+5rV
mvGs/BAAsqVmO02LkLWPpMCU54nROu3UW98qV9uX3GM4dgRzU3PKk1tnWIPydbWO
Processed: Re: python3-biopython: incompatible with muscle >= 5
Processing control commands: > severity 1022307 normal Bug #1022307 [src:python-biopython] python-biopython: FTBFS: tests choke on t_coffee Severity set to 'normal' from 'serious' -- 1022307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022307: python3-biopython: incompatible with muscle >= 5
Control: severity 1022307 normal Hi Andreas, Andreas Tille, on 2022-11-25: > Am Thu, Nov 24, 2022 at 10:35:06PM +0100 schrieb Étienne Mollier: > > > > python-biopython 1.80 is uploaded to experimental and should > > build soon[1], if this is not the case already. I haven't had a > > lot of opportunities to extensively test interactions between > > muscle3 and 5; I guess the situation will be clearer when > > muscle3 makes it through NEW. It would be nice that people > > using biopython and muscle give this a try as early as possible. > > Thanks a lot for this. > > I've just reverted the version of t-coffee and have uploaded > t-coffee_13.45.0.4846264+really13.41.0.28bdc39+dfsg-1 - not proud about > this name, but well, it should do the trick without an epoch. > > Hope this will settle the situation with biopython soonish. Thanks, this should reduce the noise on the t_coffee front. Since python-biopython 1.79 doesn't fail to build from source anymore, I reduce the severity already. I don't close just yet to avoid forgetting to bring back t-coffee in the build time test dependencies when migrating biopython 1.80 to unstable. There is also a FIXME item related to muscle3 support, that can be brought back once muscle3 passes through the NEW queue. Speaking of biopython 1.80, pseudo-excuses are looking good[1]. I fixed the autopkgtest regression in python-faidx yesterday. When trying to rebuild reverse dependencies, I also noted an issue in python-pauvre[2], which I forwarded upstream, since it didn't look easy to fix on first sight. Once sorted, I suppose it would be feasible to upgrade biopython 1.80 in unstable. [1]: https://qa.debian.org/excuses.php?experimental=1=python-biopython [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024835 Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/3, please excuse my verbosity. On air: Chicago - Make Me Smile signature.asc Description: PGP signature
Bug#1024395: The mokutil --list-enrolled is due to kernel config or version
I tested with 6.0.0-4-amd kernel version, and there mokutil --list-enrolled works. So either it is a missing config item in my own generated kernel (what is needed beside all *EFI* config items, something in keyring or crypto algo?) or a kernel incompatibilty (5.10.155). But that has nothing to do with the grub bug it is just for the sake of completeness -- eric
Bug#1024780: msxpertsuite: FTBFS with new qcustomplot
Greetings, On Thu, Nov 24, 2022 at 09:06:31PM +0100, Sebastian Ramacher wrote: Source: msxpertsuite Version: 5.8.9-1 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org Yes, that was expected but I am planning to write to FTPMasters to remove that package since it is now fully superseded by the two massxpert/minexpert2 packages. I'll do that. Tank you for your *hardwork* on our distribution! Sincerely, Filippo -- ⢀⣴⠾⠻⢶⣦⠀ Filippo Rusconi, PhD ⣾⠁⢠⠒⠀⣿⡁ Research scientist at CNRS ⢿⡄⠘⠷⠚⠋⠀ Debian Developer ⠈⠳⣄ http://msxpertsuite.org http://www.debian.org
Bug#1024278: libgssglue: autopkgtest failure with pkgconf
Thanks, I have reported this to pkgconf upstream: https://github.com/pkgconf/pkgconf/issues/278 /Simon signature.asc Description: PGP signature
Bug#1020134: marked as done (python-aioinflux: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13)
Your message dated Sat, 26 Nov 2022 09:34:22 +
with message-id
and subject line Bug#1020134: fixed in python-aioinflux 0.9.0-5
has caused the Debian Bug report #1020134,
regarding python-aioinflux: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.10 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1020134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-aioinflux
Version: 0.9.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_aioinflux/build/aioinflux
> copying aioinflux/__init__.py ->
> /<>/.pybuild/cpython3_3.10_aioinflux/build/aioinflux
> copying aioinflux/iterutils.py ->
> /<>/.pybuild/cpython3_3.10_aioinflux/build/aioinflux
> copying aioinflux/client.py ->
> /<>/.pybuild/cpython3_3.10_aioinflux/build/aioinflux
> copying aioinflux/compat.py ->
> /<>/.pybuild/cpython3_3.10_aioinflux/build/aioinflux
> creating
> /<>/.pybuild/cpython3_3.10_aioinflux/build/aioinflux/serialization
> copying aioinflux/serialization/__init__.py ->
> /<>/.pybuild/cpython3_3.10_aioinflux/build/aioinflux/serialization
> copying aioinflux/serialization/mapping.py ->
> /<>/.pybuild/cpython3_3.10_aioinflux/build/aioinflux/serialization
> copying aioinflux/serialization/dataframe.py ->
> /<>/.pybuild/cpython3_3.10_aioinflux/build/aioinflux/serialization
> copying aioinflux/serialization/common.py ->
> /<>/.pybuild/cpython3_3.10_aioinflux/build/aioinflux/serialization
> copying aioinflux/serialization/usertype.py ->
> /<>/.pybuild/cpython3_3.10_aioinflux/build/aioinflux/serialization
> running egg_info
> creating aioinflux.egg-info
> writing aioinflux.egg-info/PKG-INFO
> writing dependency_links to aioinflux.egg-info/dependency_links.txt
> writing requirements to aioinflux.egg-info/requires.txt
> writing top-level names to aioinflux.egg-info/top_level.txt
> writing manifest file 'aioinflux.egg-info/SOURCES.txt'
> reading manifest file 'aioinflux.egg-info/SOURCES.txt'
> adding license file 'LICENSE'
> writing manifest file 'aioinflux.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild pybuild:300: mkdir -p /tmp/tmp.3TsrPHp5d4 ; sed
> "s%@TEMPDIR@%/tmp/tmp.3TsrPHp5d4%" debian/test.conf.in >
> /tmp/tmp.3TsrPHp5d4/influxdb.conf ; start-stop-daemon --start --background
> --pidfile /tmp/tmp.3TsrPHp5d4/influxdb.pid --exec /usr/bin/influxd -- -config
> /tmp/tmp.3TsrPHp5d4/influxdb.conf -pidfile /tmp/tmp.3TsrPHp5d4/influxdb.pid
> I: pybuild base:240: cd
> /<>/.pybuild/cpython3_3.10_aioinflux/build; python3.10 -m pytest
> --ignore=tests/test_dataframe.py
> = test session starts
> ==
> platform linux -- Python 3.10.7, pytest-7.1.2, pluggy-1.0.0+repack
> rootdir: /<>, configfile: pytest.ini
> plugins: asyncio-0.19.0
> asyncio: mode=strict
> collected 48 items
>
> tests/test_cache.py::test_cache SKIPPED (Redis dependencies not avai...) [
> 2%]
> tests/test_client.py::test_repr
> live log call
> -
> 2022-09-17 19:40:05 | aioinflux | INFO: 0x7f2dc73cfe40>
> PASSED [
> 4%]
> tests/test_client.py::test_ping
> live log setup
>
> 2022-09-17 19:40:05 | asyncio | DEBUG: Using selector: EpollSelector
> 2022-09-17 19:40:05 | asyncio | DEBUG: Using selector: EpollSelector
> FAILED [
> 6%]
> tests/test_client.py::test_write_simple FAILED [
> 8%]
> tests/test_client.py::test_write_string FAILED [
> 10%]
> tests/test_client.py::test_write_tagless FAILED [
> 12%]
> tests/test_client.py::test_write_special_values FAILED
Bug#1013498: marked as done (django-measurement: FTBFS: ImportError: cannot import name 'ugettext_lazy' from 'django.utils.translation' (/usr/lib/python3/dist-packages/django/utils/translation/__init_
Your message dated Sat, 26 Nov 2022 09:04:21 + with message-id and subject line Bug#1013498: fixed in django-measurement 3.2.4-1 has caused the Debian Bug report #1013498, regarding django-measurement: FTBFS: ImportError: cannot import name 'ugettext_lazy' from 'django.utils.translation' (/usr/lib/python3/dist-packages/django/utils/translation/__init__.py) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1013498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: django-measurement Version: 3.2.3-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220624 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:239: python3.9 setup.py config > running config > I: pybuild base:239: python3.10 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:239: /usr/bin/python3.9 setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython3_3.9_django-measurement/build/django_measurement > copying django_measurement/__init__.py -> > /<>/.pybuild/cpython3_3.9_django-measurement/build/django_measurement > copying django_measurement/models.py -> > /<>/.pybuild/cpython3_3.9_django-measurement/build/django_measurement > copying django_measurement/forms.py -> > /<>/.pybuild/cpython3_3.9_django-measurement/build/django_measurement > copying django_measurement/conf.py -> > /<>/.pybuild/cpython3_3.9_django-measurement/build/django_measurement > copying django_measurement/utils.py -> > /<>/.pybuild/cpython3_3.9_django-measurement/build/django_measurement > I: pybuild base:239: /usr/bin/python3 setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython3_3.10_django-measurement/build/django_measurement > copying django_measurement/__init__.py -> > /<>/.pybuild/cpython3_3.10_django-measurement/build/django_measurement > copying django_measurement/models.py -> > /<>/.pybuild/cpython3_3.10_django-measurement/build/django_measurement > copying django_measurement/forms.py -> > /<>/.pybuild/cpython3_3.10_django-measurement/build/django_measurement > copying django_measurement/conf.py -> > /<>/.pybuild/cpython3_3.10_django-measurement/build/django_measurement > copying django_measurement/utils.py -> > /<>/.pybuild/cpython3_3.10_django-measurement/build/django_measurement >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:239: cd > /<>/.pybuild/cpython3_3.9_django-measurement/build; python3.9 -m > pytest tests > Traceback (most recent call last): > File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main > return _run_code(code, main_globals, None, > File "/usr/lib/python3.9/runpy.py", line 87, in _run_code > exec(code, run_globals) > File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 5, in > > raise SystemExit(pytest.console_main()) > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 185, > in console_main > code = main() > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 143, > in main > config = _prepareconfig(args, plugins) > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 318, > in _prepareconfig > config = pluginmanager.hook.pytest_cmdline_parse( > File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265, in > __call__ > return self._hookexec(self.name, self.get_hookimpls(), kwargs, > firstresult) > File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80, in > _hookexec > return self._inner_hookexec(hook_name, methods, kwargs, firstresult) > File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 55, in > _multicall > gen.send(outcome) > File "/usr/lib/python3/dist-packages/_pytest/helpconfig.py", line 100, in > pytest_cmdline_parse > config: Config = outcome.get_result() > File "/usr/lib/python3/dist-packages/pluggy/_result.py", line 60, in > get_result > raise ex[1].with_traceback(ex[2]) > File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39, in > _multicall > res = hook_impl.function(*args) > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line
Bug#1024831: xorg: xserver fails to resume after suspend-to-disk
Package: xorg Version: 1:7.7+22 Severity: grave Justification: causes non-serious data loss Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Suspend-to-disk, resume and the screen keeps been blank * What exactly did you do (or not do) that was effective (or ineffective)? - acpitool -S - switch PC on - but ssh is working * What was the outcome of this action? The monitors keep being blank, they try to go into sleep mode, as they find no signal * What outcome did you expect instead? I want to see the old content on the monitor In the logfile Xorg.0.log I noticed many times the log message (but: (WW) AMDGPU(0): get vblank counter failed: Invalid argument Don't know, if related, but noticed this only after my Debian stable (bullseye) switched to linux kernel version 6.0.0: linux-image-6.0.0-0.deb11.2-amd64 suspend-to-ram is not affected, the wake up there is still working as expected. *** End of the template - remove these template lines *** -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 06:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c8) /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 0 /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 6.0.0-0.deb11.2-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PREEMPT_DYNAMIC Debian 6.0.3-1~bpo11+1 (2022-10-29) Xorg X server log files on system: -- -rw-r--r-- 1 root root 20794 Dec 12 2021 /var/log/Xorg.1.log -rw-r--r-- 1 root root 60759 Nov 26 09:37 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [40.971] X.Org X Server 1.20.11 X Protocol Version 11, Revision 0 [40.971] Build Operating System: linux Debian [40.971] Current Operating System: Linux dipper 6.0.0-0.deb11.2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.3-1~bpo11+1 (2022-10-29) x86_64 [40.971] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.0.0-0.deb11.2-amd64 root=UUID=ca445dcc-b878-4c62-939b-e40721fa00a0 ro quiet [40.971] Build Date: 11 November 2022 12:37:52PM [40.971] xorg-server 2:1.20.11-1+deb11u3 (https://www.debian.org/support) [40.971] Current version of pixman: 0.40.0 [40.971]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [40.971] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [40.971] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Nov 26 09:36:55 2022 [40.971] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [40.972] (==) No Layout section. Using the first Screen section. [40.972] (==) No screen section available. Using defaults. [40.972] (**) |-->Screen "Default Screen Section" (0) [40.972] (**) | |-->Monitor "" [40.972] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [40.972] (==) Automatically adding devices [40.972] (==) Automatically enabling devices [40.972] (==) Automatically adding GPU devices [40.972] (==) Max clients allowed: 256, resource mask: 0x1f [40.973] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [40.973]Entry deleted from font path. [40.974] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [40.974] (==) ModulePath set to "/usr/lib/xorg/modules" [40.974] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [40.974] (II) Loader magic: 0x55fd3c1e0e40 [40.974] (II) Module ABI versions: [40.974]X.Org ANSI C Emulation: 0.4 [40.974]X.Org Video Driver: 24.1 [40.974]X.Org XInput driver : 24.1 [40.974]X.Org Server Extension : 10.0 [40.974] (++) using VT number 7 [40.974] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [40.975] (II) xfree86: Adding drm device (/dev/dri/card0) [40.999]
