Bug#1006508: marked as done (m2crypto: FTBFS with OpenSSL 3.0)
Your message dated Tue, 21 Jun 2022 05:04:04 + with message-id and subject line Bug#1006508: fixed in m2crypto 0.38.0-3 has caused the Debian Bug report #1006508, regarding m2crypto: FTBFS with OpenSSL 3.0 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.) -- 1006508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006508 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: m2crypto Version: 0.38.0-2 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Your package is failing to build using OpenSSL 3.0 with the following error: | tests/test_authcookie.py ... [ 9%] | tests/test_bio.py Fatal Python error: Segmentation fault | | Current thread 0x7f810c326b80 (most recent call first): | File "/<>/.pybuild/cpython3_3.10_m2crypto/build/M2Crypto/BIO.py", line 61 in read | File "/<>/.pybuild/cpython3_3.10_m2crypto/build/tests/test_bio.py", line 57 in try_algo | File "/<>/.pybuild/cpython3_3.10_m2crypto/build/tests/test_bio.py", line 73 in test_algo | File "/usr/lib/python3/dist-packages/parameterized/parameterized.py", line 533 in standalone_func | File "/usr/lib/python3.10/unittest/case.py", line 549 in _callTestMethod | File "/usr/lib/python3.10/unittest/case.py", line 591 in run | File "/usr/lib/python3.10/unittest/case.py", line 650 in __call__ | File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 321 in runtest | File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 162 in pytest_runtest_call | File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in _multicall | File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in | File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in _hookexec | File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in __call__ | File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 255 in | File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 311 in from_call | File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 254 in call_runtest_hook | File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 215 in call_and_report | File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 126 in runtestprotocol | File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 109 in pytest_runtest_protocol | File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in _multicall | File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in | File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in _hookexec | File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in __call__ | File "/usr/lib/python3/dist-packages/_pytest/main.py", line 348 in pytest_runtestloop | File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in _multicall | File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in | File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in _hookexec | File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in __call__ | File "/usr/lib/python3/dist-packages/_pytest/main.py", line 323 in _main | File "/usr/lib/python3/dist-packages/_pytest/main.py", line 269 in wrap_session | File "/usr/lib/python3/dist-packages/_pytest/main.py", line 316 in pytest_cmdline_main | File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in _multicall | File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in | File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in _hookexec | File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in __call__ | File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 162 in main | File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 185 in console_main | File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 5 in | File "/usr/lib/python3.10/runpy.py", line 86 in _run_code | File "/usr/lib/python3.10/runpy.py", line 196 in _run_module_as_main | | Extension modules: _m2crypto, M2Crypto._m2crypto (total: 2) | Segmentation fault | E: pybuild pybuild:367: test: plugin distutils failed with: exit code=139: cd /<>/.pybuild/cpython3_3.10_m2crypto/build; python3.10 -m pytest --ignore tests/test_ssl.py | I: pybuild base:237: cd /<>/.pybuild/cpython3_3.9_m2crypto/build; python3.9 -m pytest --ignore tests/test_ssl.py | = test session starts
Bug#997472: marked as done (flask-script: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13)
Your message dated Tue, 21 Jun 2022 05:00:34 +
with message-id
and subject line Bug#1000556: Removed package(s) from unstable
has caused the Debian Bug report #997472,
regarding flask-script: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.9 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.)
--
997472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flask-script
Version: 2.0.6-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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:232: python3.9 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.9_flask-script/build/flask_script
> copying flask_script/cli.py ->
> /<>/.pybuild/cpython3_3.9_flask-script/build/flask_script
> copying flask_script/__init__.py ->
> /<>/.pybuild/cpython3_3.9_flask-script/build/flask_script
> copying flask_script/_compat.py ->
> /<>/.pybuild/cpython3_3.9_flask-script/build/flask_script
> copying flask_script/commands.py ->
> /<>/.pybuild/cpython3_3.9_flask-script/build/flask_script
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:232: cd
> /<>/.pybuild/cpython3_3.9_flask-script/build; python3.9 -m
> pytest "tests.py"
> = test session starts
> ==
> platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
> rootdir: /<>
> collected 0 items / 1 error
>
> ERRORS
>
> __ ERROR collecting .pybuild/cpython3_3.9_flask-script/build/tests.py
> __
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.9_flask-script/build/tests.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.9/importlib/__init__.py:127: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests.py:8: in
> from flask_script._compat import StringIO, text_type
> flask_script/__init__.py:15: in
> from flask._compat import text_type
> E ModuleNotFoundError: No module named 'flask._compat'
> === short test summary info
>
> ERROR tests.py
> Interrupted: 1 error during collection
>
> === 1 error in 0.22s
> ===
> E: pybuild pybuild:354: test: plugin distutils failed with: exit code=2: cd
> /<>/.pybuild/cpython3_3.9_flask-script/build; python3.9 -m
> pytest "tests.py"
> dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit
> code 13
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/flask-script_2.0.6-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 2.0.6-3+rm
Dear submitter,
as the package flask-script has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1000556
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution
Bug#1010764: marked as done (openafs-modules-dkms: module fails to build for kernel 5.17.0-1-amd64)
Your message dated Tue, 21 Jun 2022 00:04:25 + with message-id and subject line Bug#1010764: fixed in openafs 1.8.8.1-3 has caused the Debian Bug report #1010764, regarding openafs-modules-dkms: module fails to build for kernel 5.17.0-1-amd64 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.) -- 1010764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openafs-modules-dkms Version: 1.8.8.1-2 Severity: important Dear Maintainer, * What led up to the situation? - regular apt upgrade on testing * What exactly did you do that was effective? - switch to kernel 5.16.0-6-amd64 The module built fine for this slightly older kernel. * What was the outcome of this action? - I am unable to use openafs with kernel 5.17 * What outcome did you expect instead? - a working openafs module for kernel 5.17 /var/lib/dkms/openafs/1.8.8.1/build/make.log seems to indicate a problem with the function complete_and_exit() in afs_call_nfs.c : --- DKMS make.log for openafs-1.8.8.1 for kernel 5.17.0-1-amd64 (x86_64) Mon 9 May 17:10:20 CEST 2022 checking for gcc... gcc-11 (...) CC [M] /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.17.0-1-amd64-SP/osi_proc.o CC [M] /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.17.0-1-amd64-SP/osi_vnodeops.o /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.17.0-1-amd64-SP/osi_vnodeops.c: In function ‘afs_linux_can_bypass’: /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.17.0-1-amd64-SP/osi_vnodeops.c:2700:16: warning: this statement may fall through [-Wimplicit-fallthrough=] 2700 | if (i_size_read(ip) > cache_bypass_threshold) | ^ /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.17.0-1-amd64-SP/osi_vnodeops.c:2703:9: note: here 2703 | default: | ^~~ CC [M] /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.17.0-1-amd64-SP/osi_pagecopy.o CC [M] /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.17.0-1-amd64-SP/afs_nfsclnt.o CC [M] /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.17.0-1-amd64-SP/afs_nfsdisp.o CC [M] /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.17.0-1-amd64-SP/afs_call_nfs.o /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.17.0-1-amd64-SP/afs_call_nfs.c: In function ‘afsd_thread’: /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.17.0-1-amd64-SP/afs_call_nfs.c:331:9: error: implicit declaration of function ‘complete_and_exit’ [-Werror=implicit-function-declaration] 331 | complete_and_exit(0, 0); | ^ cc1: some warnings being treated as errors make[4]: *** [/usr/src/linux-headers-5.17.0-1-common/scripts/Makefile.build:293: /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.17.0-1-amd64-SP/afs_call_nfs.o] Error 1 make[3]: *** [/usr/src/linux-headers-5.17.0-1-common/Makefile:1855: /var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.17.0-1-amd64-SP] Error 2 make[3]: Leaving directory '/usr/src/linux-headers-5.17.0-1-amd64' FAILURE: make exit code 2 make[2]: *** [Makefile.afs:279: openafs.ko] Error 1 make[2]: Leaving directory '/var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-5.17.0-1-amd64-SP' make[1]: *** [Makefile:186: linux_compdirs] Error 2 make[1]: Leaving directory '/var/lib/dkms/openafs/1.8.8.1/build/src/libafs' make: *** [Makefile:15: all] Error 2 -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openafs-modules-dkms depends on: ii dkms 2.8.7-2 ii libc6-dev 2.33-7 ii perl 5.34.0-4 Versions of packages openafs-modules-dkms recommends: ii openafs-client 1.8.8.1-2 openafs-modules-dkms suggests no packages. -- no debconf information -- Kai-Martin Knaak kn...@iqo.uni-hannover.de Universität Hannover, Inst. für Quantenoptik tel: +49-511-762-2895 Welfengarten 1, 30167 Hannover fax: +49-511-762-2211 PGP-Key: https://keys.openpgp.org/search?q=kn...@iqo.uni-hannover.de pgpSu32fcmfBP.pgp Description: OpenPGP digital signature --- End
Bug#1009437: marked as done (ippsample: FTBFS: dh_auto_test: error: make -j8 test VERBOSE=1 returned exit code 2)
Your message dated Mon, 20 Jun 2022 22:04:33 +
with message-id
and subject line Bug#1009437: fixed in ippsample 0.0~git20220607.72f89b3-1
has caused the Debian Bug report #1009437,
regarding ippsample: FTBFS: dh_auto_test: error: make -j8 test VERBOSE=1
returned exit code 2
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.)
--
1009437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ippsample
Version: 0.0~git20220215.f365352-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/cups'
> make[2]: warning: -j8 forced in submake: resetting jobserver mode.
> Compiling testarray.c...
> Compiling testclient.c...
> Compiling testdest.c...
> Compiling testfile.c...
> Compiling testhttp.c...
> Compiling testi18n.c...
> Compiling testipp.c...
> Compiling testoptions.c...
> testfile.c: In function ‘main’:
> testfile.c:84:5: warning: ignoring return value of ‘pipe’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
>84 | pipe(fds);
> | ^
> Compiling testraster.c...
> Linking testarray...
> Linking testoptions...
> Linking testi18n...
> Linking testfile...
> Linking testipp...
> Linking testclient...
> Linking testhttp...
> Linking testdest...
> Linking testraster...
> Running unit tests...
>
> Running testarray...
> cupsArrayNew: PASS
> cupsArrayUserData: PASS
> cupsArrayAdd: PASS
> cupsArrayCount: PASS
> cupsArrayFirst: PASS
> cupsArrayNext: PASS
> cupsArrayLast: PASS
> cupsArrayPrev: PASS
> cupsArrayFind: PASS
> cupsArrayCurrent: PASS
> cupsArrayDup: PASS
> cupsArrayRemove: PASS
> cupsArrayClear: PASS
> Load unique words: 30719 words in 0.126 seconds (243471 words/sec), PASS
> Delete While Iterating: PASS
> cupsArraySave: PASS
> cupsArrayRestore: PASS
> _cupsArrayNewStrings(" \t\nfoo bar\tboo\nfar", ' '): PASS
> _cupsArrayAddStrings(array, "foo2,bar2", ','): PASS
>
> ALL TESTS PASSED!
>
> Running testclient...
>
> Running testdest...
>
> Running testfile...
> cupsFileOpen(write): PASS
> cupsFileCompression(): PASS
> cupsFilePuts(): PASS
> cupsFilePrintf(): PASS
> cupsFilePutChar(): PASS
> cupsFileWrite(): PASS
> cupsFilePuts("partial line"): PASS
> cupsFileTell(): PASS
> cupsFileClose(): PASS
>
> cupsFileOpen(read): PASS
> cupsFileGets(): PASS
> cupsFileCompression(): PASS
> cupsFileGetConf(): PASS
> cupsFileGetChar(): PASS
> cupsFileRead(): PASS
> cupsFileGetChar(partial line): PASS
> cupsFileTell(): PASS
> cupsFileClose(): PASS
>
> cupsFileOpen(write compressed): PASS
> cupsFileCompression(): PASS
> cupsFilePuts(): PASS
> cupsFilePrintf(): PASS
> cupsFilePutChar(): PASS
> cupsFileWrite(): PASS
> cupsFilePuts("partial line"): PASS
> cupsFileTell(): PASS
> cupsFileClose(): PASS
>
> cupsFileOpen(read): PASS
> cupsFileGets(): PASS
> cupsFileCompression(): PASS
> cupsFileGetConf(): PASS
> cupsFileGetChar(): PASS
> cupsFileRead(): PASS
> cupsFileGetChar(partial line): PASS
> cupsFileTell(): PASS
> cupsFileClose(): PASS
>
> cupsFileOpen(append 0): PASS
> cupsFileTell(): PASS
> cupsFileWrite(256 512-byte records): PASS
> cupsFileTell(): PASS
>
> cupsFileOpen(read 0): PASS
> cupsFileSeek(), cupsFileRead(): PASS
>
> cupsFileOpen(append 1): PASS
> cupsFileTell(): PASS
> cupsFileWrite(256 512-byte records): PASS
> cupsFileTell(): PASS
>
> cupsFileOpen(read 1): PASS
> cupsFileSeek(), cupsFileRead(): PASS
>
> cupsFileOpen(append 2): PASS
> cupsFileTell(): PASS
> cupsFileWrite(256 512-byte records): PASS
> cupsFileTell(): PASS
>
> cupsFileOpen(read 2): PASS
> cupsFileSeek(), cupsFileRead(): PASS
>
> cupsFileOpen(append 3): PASS
> cupsFileTell(): PASS
> cupsFileWrite(256 512-byte records): PASS
> cupsFileTell(): PASS
>
> cupsFileOpen(read 3): PASS
> cupsFileSeek(), cupsFileRead(): PASS
>
> cupsFileOpenFd(fd, "r"): PASS
> cupsFileClose(no read): PASS
>
> cupsFileOpen("testfile.txt", "r"): PASS
> cupsFileGets: PASS
> cupsFileRewind: PASS
> cupsFileGets: PASS
>
> cupsFileFind: PASS (/bin/cat)
>
> ALL TESTS PASSED!
>
> Running testhttp...
> httpGetDateString()/httpGetDateTime(): PASS
> httpDecode64_2()/httpEncode64_2(): PASS
> httpGetHostname(): PASS (ip-10-84-234-252)
> httpAddrGetList(ip-10-84-234-252): FAIL
> httpSeparateURI(): PASS (44 URIs tested)
> httpAssembleURI(): PASS (16 URIs tested)
> httpAssembleUUID: PASS (urn:uuid:54095e9c-ee9b-3a04-7566-1d3a6342da2c)
Processed: forcibly merging 1012127 1008220
Processing commands for cont...@bugs.debian.org: > forcemerge 1012127 1008220 Bug #1012127 [src:flexbar] flexbar: FTBFS with onetbb/2021.5.0-8 in experimental Bug #1012127 [src:flexbar] flexbar: FTBFS with onetbb/2021.5.0-8 in experimental The source flexbar and version 3.5.0-4 do not appear to match any binary packages Marked as found in versions flexbar/3.5.0-4. Bug #1008220 [src:flexbar] flexbar 3.5.0-4 FTBFS against libtbb-dev 2021.5.0-7 Severity set to 'serious' from 'important' The source flexbar and version 3.5.0-4 do not appear to match any binary packages Marked as found in versions flexbar/1:3.5.0-4. Added tag(s) ftbfs. Merged 1008220 1012127 > thanks Stopping processing here. Please contact me if you need assistance. -- 1008220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008220 1012127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012878: marked as done (pyside2: autopkgtest regression)
Hi Christian, After three NMUs, what do you think about adding yourself to Uploaders and making these changes directly? :) I'm part of the Qt/KDE Team, but don't maintain this package, and I've been importing your diffs with gbp import-dsc. Vcs-Git: https://salsa.debian.org/qt-kde-team/qt/pyside2.git Vcs-Browser: https://salsa.debian.org/qt-kde-team/qt/pyside2 Also, please note that Developer's Reference §7.4.3 states "always send a patch as a unified context diff (diff -u) detailing their changes to the Bug Tracking System". Regards, Nicholas signature.asc Description: PGP signature
Bug#997302: marked as done (django-pipeline: FTBFS: ImportError: cannot import name 'six' from 'django.utils' (/usr/lib/python3/dist-packages/django/utils/__init__.py))
Your message dated Mon, 20 Jun 2022 19:19:02 +
with message-id
and subject line Bug#997302: fixed in django-pipeline 1.6.14-5
has caused the Debian Bug report #997302,
regarding django-pipeline: FTBFS: ImportError: cannot import name 'six' from
'django.utils' (/usr/lib/python3/dist-packages/django/utils/__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.)
--
997302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-pipeline
Version: 1.6.14-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYTHONPATH=. /usr/bin/django-admin collectstatic --settings=tests.settings
> --noinput
> Traceback (most recent call last):
> File "/usr/bin/django-admin", line 33, in
> sys.exit(load_entry_point('Django==3.2.8', 'console_scripts',
> 'django-admin')())
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 419, in execute_from_command_line
> utility.execute()
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 395, in execute
> django.setup()
> File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in setup
> apps.populate(settings.INSTALLED_APPS)
> File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 91, in
> populate
> app_config = AppConfig.create(entry)
> File "/usr/lib/python3/dist-packages/django/apps/config.py", line 224, in
> create
> import_module(entry)
> File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> File "", line 1030, in _gcd_import
> File "", line 1007, in _find_and_load
> File "", line 986, in _find_and_load_unlocked
> File "", line 680, in _load_unlocked
> File "", line 850, in exec_module
> File "", line 228, in _call_with_frames_removed
> File "/<>/tests/tests/__init__.py", line 10, in
> from .test_collector import *
> File "/<>/tests/tests/test_collector.py", line 9, in
> from pipeline.collector import default_collector
> File "/<>/pipeline/collector.py", line 10, in
> from django.utils import six
> ImportError: cannot import name 'six' from 'django.utils'
> (/usr/lib/python3/dist-packages/django/utils/__init__.py)
> make[1]: *** [debian/rules:25: override_dh_auto_test] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/django-pipeline_1.6.14-3_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: django-pipeline
Source-Version: 1.6.14-5
Done: Sandro Tosi
We believe that the bug you reported is fixed in the latest version of
django-pipeline, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sandro Tosi (supplier of updated django-pipeline 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: Mon, 20 Jun 2022 15:04:59 -0400
Source: django-pipeline
Architecture: source
Version: 1.6.14-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Sandro Tosi
Closes: 997302
Changes:
django-pipeline (1.6.14-5) unstable; urgency=medium
.
* debian/patches/remove-broken-tests.patch
- make this prj compatible with modern Django and python; Closes: #997302
Checksums-Sha1:
61dc0a31f39491195e539bc43f791727e01c5fa5 2254 django-pipeline_1.6.14-5.dsc
7fa903a863501e256407f6be1c9199467d76db17 7916
Bug#997302: marked as pending in django-pipeline
Control: tag -1 pending Hello, Bug #997302 in django-pipeline 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/django-pipeline/-/commit/19e3a4b3601e8009e31a67fc7c442799ca9c043c make this prj compatible with modern Django and python; Closes: #997302 (this message was generated automatically) -- Greetings https://bugs.debian.org/997302
Processed: Bug#997302 marked as pending in django-pipeline
Processing control commands: > tag -1 pending Bug #997302 [src:django-pipeline] django-pipeline: FTBFS: ImportError: cannot import name 'six' from 'django.utils' (/usr/lib/python3/dist-packages/django/utils/__init__.py) Added tag(s) pending. -- 997302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service
On Mon, 2022-06-20 at 04:38 -0500, Daniel Lewart wrote: > Ben, > > > I wrote a script to check for short signatures (and other unexpected > > things) in detached signature files: > > https://salsa.debian.org/kernel-team/kernel-team/-/blob/master/scripts/benh/check-sig-params > > Thank you for your excellent detective work! > > I tried running your script, but it generates an error (see below). > What am I doing wrong? [...] I don't know, but I'm running it on unstable. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part
Bug#1013218: marked as done (rails: ftbfs SyntaxError: Unexpected token 'export')
Your message dated Mon, 20 Jun 2022 18:56:13 + with message-id and subject line Bug#1013218: fixed in rails 2:6.1.4.7+dfsg-1 has caused the Debian Bug report #1013218, regarding rails: ftbfs SyntaxError: Unexpected token 'export' 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.) -- 1013218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rails,node-babel7 Version: 2:6.1.4.6+dfsg-3 severity: serious Build fails with SyntaxError: Unexpected token 'export' at Object.compileFunction (node:vm:352:18) at wrapSafe (node:internal/modules/cjs/loader:1033:15) at Module._compile (node:internal/modules/cjs/loader:1069:27) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) at node:internal/main/run_main_module:17:47 full log attached This may be related to 1013189 (some binary packages were rearranged in node-babel7 and it may be causing the transpilation failure). sbuild (Debian sbuild) 0.81.2 (31 January 2021) on ilvala2 +==+ | rails 2:6.1.4.6+dfsg-3 (amd64) Sun, 19 Jun 2022 06:50:10 + | +==+ Package: rails Version: 2:6.1.4.6+dfsg-3 Source Version: 2:6.1.4.6+dfsg-3 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: binary I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-44afcdb8-d444-4c55-8510-08b668006dc5' with '<>' I: NOTICE: Log filtering will replace 'build/rails-Bm6vw6/resolver-MnuumW' with '<>' +--+ | Update chroot| +--+ Get:1 http://ftp.au.debian.org/debian unstable InRelease [165 kB] Get:2 http://ftp.au.debian.org/debian unstable/main Sources.diff/Index [63.6 kB] Get:3 http://ftp.au.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB] Get:4 http://ftp.au.debian.org/debian unstable/main Sources T-2022-06-19-0209.27-F-2022-06-17-2004.29.pdiff [54.4 kB] Get:4 http://ftp.au.debian.org/debian unstable/main Sources T-2022-06-19-0209.27-F-2022-06-17-2004.29.pdiff [54.4 kB] Get:5 http://ftp.au.debian.org/debian unstable/main amd64 Packages T-2022-06-19-0209.27-F-2022-06-17-2004.29.pdiff [62.6 kB] Get:5 http://ftp.au.debian.org/debian unstable/main amd64 Packages T-2022-06-19-0209.27-F-2022-06-17-2004.29.pdiff [62.6 kB] Fetched 410 kB in 5s (87.0 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... The following packages were automatically installed and are no longer required: cpp-10 fontconfig-config fonts-dejavu-core gcc-10 krb5-locales libbrotli1 libbsd0 libc-devtools libdeflate0 libexpat1 libfontconfig1 libfreetype6 libgcc-10-dev libgd3 libjbig0 libjpeg62-turbo liblerc3 libmd0 libnss-nis libnss-nisplus libpng16-16 libtiff5 libwebp7 libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxpm4 manpages manpages-dev sensible-utils ucf Use 'apt autoremove' to remove them. The following packages will be upgraded: libcap-ng0 libgnutls30 mawk 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 1532 kB of archives. After this operation, 48.1 kB of additional disk space will be used. Get:1 http://ftp.au.debian.org/debian unstable/main amd64 libcap-ng0 amd64 0.7.9-4 [15.1 kB] Get:2 http://ftp.au.debian.org/debian unstable/main amd64 libgnutls30 amd64 3.7.6-2 [1397 kB] Get:3 http://ftp.au.debian.org/debian unstable/main amd64 mawk amd64 1.3.4.20200120-3.1 [119 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 1532 kB in 0s (39.2 MB/s) (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading
Bug#966775: marked as done (postnews: Unversioned Python removal in sid/bullseye)
Your message dated Mon, 20 Jun 2022 18:00:39 + with message-id and subject line Bug#1008272: Removed package(s) from unstable has caused the Debian Bug report #937312, regarding postnews: Unversioned Python removal in sid/bullseye 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.) -- 937312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:postnews Version: 0.7-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.7-1+rm Dear submitter, as the package postnews has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1008272 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#937312: marked as done (postnews: Python2 removal in sid/bullseye)
Your message dated Mon, 20 Jun 2022 18:00:39 + with message-id and subject line Bug#1008272: Removed package(s) from unstable has caused the Debian Bug report #937312, regarding postnews: Python2 removal in sid/bullseye 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.) -- 937312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:postnews Version: 0.7-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:postnews If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.7-1+rm Dear submitter, as the package postnews has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1008272 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1010764: upstream fix
tags 1010764 upstream fixed-upstream pending thanks On Wed, May 18, 2022 at 01:55:00AM +, Jeremy Stanley wrote: > The fix for this appears to have merged upstream in January, so > could probably be backported in Salsa: > > https://gerrit.openafs.org/14882 Indeed, upstream has been getting the needed fixes for new linux versions into git, but getting them actually into a release has been "probably next week" for ... well, quite a few weeks. I will go ahead and just take the patches as debian patches for now, and my apologies for taking so long to get to it. -Ben
Processed: Re: Bug#1010764: upstream fix
Processing commands for cont...@bugs.debian.org: > tags 1010764 upstream fixed-upstream pending Bug #1010764 [openafs-modules-dkms] openafs-modules-dkms: module fails to build for kernel 5.17.0-1-amd64 Added tag(s) fixed-upstream, upstream, and pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1010764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013179: marked as done (likwid: ships /usr/lib//libhwloc.so{,.5})
Your message dated Mon, 20 Jun 2022 17:20:31 +
with message-id
and subject line Bug#1013179: fixed in likwid 5.2.1+dfsg1-3
has caused the Debian Bug report #1013179,
regarding likwid: ships /usr/lib//libhwloc.so{,.5}
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.)
--
1013179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: likwid
Version: 5.2.1+dfsg1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files:
Selecting previously unselected package likwid.
Preparing to unpack .../likwid_5.2.1+dfsg1-2_amd64.deb ...
Unpacking likwid (5.2.1+dfsg1-2) ...
dpkg: error processing archive
/var/cache/apt/archives/likwid_5.2.1+dfsg1-2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libhwloc.so', which is also
in package libhwloc-dev:amd64 2.7.1-1
Errors were encountered while processing:
/var/cache/apt/archives/likwid_5.2.1+dfsg1-2_amd64.deb
These hwloc symlinks don't belong into likwid.
Andreas
--- End Message ---
--- Begin Message ---
Source: likwid
Source-Version: 5.2.1+dfsg1-3
Done: Christoph Martin
We believe that the bug you reported is fixed in the latest version of
likwid, 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 1013...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christoph Martin (supplier of updated likwid 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: Mon, 20 Jun 2022 17:31:59 +0200
Source: likwid
Architecture: source
Version: 5.2.1+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Christoph Martin
Changed-By: Christoph Martin
Closes: 1013179
Changes:
likwid (5.2.1+dfsg1-3) unstable; urgency=medium
.
* remove obsolete symlink to custom hwloc lib (closes: 1013179)
* remove hwloc from lintian overrides
* update watch file src to https
* add python3 to deps
Checksums-Sha1:
7db92d4f09b2f11dcb36a78cc4e8f2453eecd544 1922 likwid_5.2.1+dfsg1-3.dsc
613ef412c7c43368ccafcb18a4d4b7b6771bc55a 1342176 likwid_5.2.1+dfsg1.orig.tar.xz
50dd877faac51c40999cad7a1b9d1116c86293f3 53756
likwid_5.2.1+dfsg1-3.debian.tar.xz
8a114b780708e56d89f3464218e3124474d10b6b 8047
likwid_5.2.1+dfsg1-3_amd64.buildinfo
Checksums-Sha256:
c261c3fefc17f6863ff95323d13a66ced604f97a05274e5a9880f80b3d5ea033 1922
likwid_5.2.1+dfsg1-3.dsc
de06d2c885cd553b343dc6e422afa7763f202a28a942670c31d741d1e9d66244 1342176
likwid_5.2.1+dfsg1.orig.tar.xz
cde379467bb41aa193d949b276830c227071172b05df6735880e6f398a97a943 53756
likwid_5.2.1+dfsg1-3.debian.tar.xz
7f10dc6d95a450e2c1e1e22968a3b6b3e51da2f77b7efee14379a860abfab086 8047
likwid_5.2.1+dfsg1-3_amd64.buildinfo
Files:
e7288f2dfbf3f71210afcc2a67559611 1922 misc optional likwid_5.2.1+dfsg1-3.dsc
4465ba6c2cd8515f96ec0ba68f6453d5 1342176 misc optional
likwid_5.2.1+dfsg1.orig.tar.xz
8397faea2a26ea6ebb8f1cbe8fe1ca78 53756 misc optional
likwid_5.2.1+dfsg1-3.debian.tar.xz
64c03a5831ddab0c4ca6724bbab4c9ff 8047 misc optional
likwid_5.2.1+dfsg1-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEienqSdlSvBRoCebg9oBraugTkrAFAmKwqR0ACgkQ9oBraugT
krCF5g/+I3/MD/vdwLpG4T0dnTZOyjljLkEPpwUMBNWECOk/xKRCrRq/35cFpLiE
wTr5strrZTZYiK/wB6dKnuzgHtQKb/UyMWLSdrmhnANLSbKhNCJ6xzjD0gnFh0gH
aLC/xi2enrB9IIfZYmp/YQXvBFApIJXXQRfJbY7EbwYvKFeM6VwCBFfgzKSp+Rt3
hCeJn1RoZoJTY3snQSbJV4bHCe1lDE9uM/Tr16eVTMnv8dPnA+fv9eUBLre8IDH4
dzuKBpYQypvuPxMH6WUotiVIdx8+65s8L9lOLwU2uia1olKLgz+2evjwP0FUYSNk
gfm7YwasVVUF1QDhr59OXV73WmdxAWW3FON1zxy09DyhWF/Q9Cw9ooX2lRPk1aPA
m8UQDvFktqC4/94XEGljfctYMalu3rpU3l9JjBWJ5SmGPoIC70+DI6jih9nhzbB/
lMgwNE55EVPac6pzmrUzmrDCGk5ZO+PUzhyIdtpm8cix4MFnRk47cAP+rHkRJGGv
udIfGIb5+U0iDesjAyEQAjzVIoQH5HaRwowE0I22Jd9pnWIBypqaFIUlBTTxJEZL
cp5I5rRqCFBLNKyU3yoVi6nMEL3+nFttUvH5LOUDxqxTdEBzy2vNlYCDC3YpC8Jk
+7SCUDPBgfLYlTs5B/v4vzX09IoxGhUCk+/pNVOV20Eg8hy4uzI=
=AUSy
-END PGP SIGNATURE End Message ---
Bug#1013281: libbatik-java: Running rasterizer fails with inability to load main class org.apache.batik.apps.rasterizer.Main
Package: libbatik-java Version: 1.12-4 Severity: grave Justification: renders package unusable Dear Maintainer, Been using this kind of call against a Jessie install of this package for years: java -jar /usr/share/java/batik-rasterizer.jar -m image/png -scriptSecurityOff -w 1920 /tmp/ramdisk/svgproc-b83e35c457f48904da8a39a01d230d48.svg After upgrading system to bullseye, the same call produces this error: Error: Could not find or load main class org.apache.batik.apps.rasterizer.Main Caused by: java.lang.ClassNotFoundException: org.apache.batik.apps.rasterizer.Main From what I can tell, this was repackaged from having the actual code inside to the jar to being references to other jars. However it looks as if all of the manifests now have a "lib/" prefixed to the classpaths and this causes java to fail at finding any usable source. As a test, I created a symlink called lib inside /usr/share/java/ that simply points back to the same directory. There were still some errors, but it looked like java could at least find some of the other jars it was looking at. This might turn out to be a repackaging problem since the source package on the Apache site does come with all the jars stored into a "lib" directory. -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-15-amd64 (SMP w/2 CPU threads) Locale: LANG=C, LC_CTYPE=C.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 libbatik-java depends on: ii java-wrappers 0.3 ii libjaxp1.3-java 1.3.05-6 ii libxalan2-java2.7.2-4 ii libxml-commons-external-java 1.4.01-5 ii libxmlgraphics-commons-java 2.4-2~deb11u1 Versions of packages libbatik-java recommends: ii default-jre 2:1.11-72 Versions of packages libbatik-java suggests: ii librhino-java 1.7.7.2-3 -- no debconf information
Bug#999768: marked as done (lintian: false report: adopted-extended-field XS-Autobuild)
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#999768: fixed in lintian 2.115.0
has caused the Debian Bug report #999768,
regarding lintian: false report: adopted-extended-field XS-Autobuild
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.)
--
999768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.112.0
Severity: serious
Lintian now reports
I: nvidia-graphics-drivers source: adopted-extended-field XS-Autobuild (in
section for source) [debian/control:26]
but that field is not usable as Autobuild, dpkg/sid does not accept it:
dpkg-gencontrol: warning: unknown information field 'Autobuild' in input data
in general section of control info file
dpkg-genchanges: warning: unknown information field 'Autobuild' in input data
in general section of control info file
dpkg-source: warning: unknown information field 'Autobuild' in input data in
general section of control info file
Andreas
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.115.0
Done: Axel Beckert
We believe that the bug you reported is fixed in the latest version of
lintian, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Axel Beckert (supplier of updated lintian 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: Mon, 20 Jun 2022 13:23:02 +0200
Source: lintian
Architecture: source
Version: 2.115.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers
Changed-By: Axel Beckert
Closes: 657390 932634 941656 963099 989381 995286 996740 999768 999810 1000234
1000977 1001655 1002828 1003131 1003272 1003353 1003456 1003668 1003817 1003913
1003941 1004231 1004239 1004240 1004660 1005046 1005184 1005762 1006390 1006859
1007140 1007257 1012090
Changes:
lintian (2.115.0) unstable; urgency=medium
.
The Lintian Resurrection Release.
.
* Summary of tag changes:
+ Added:
- alien-tag
- chown-with-dot
- conflicting-test-fields
- declare-python-versions-for-test
- drop-python-version-declaration
- invalid-override-restriction
- missing-prerequisite-for-pyproject-backend
- old-devhelp-standard
- stray-devhelp-documentation
- test-leaves-python-version-untested
- uses-poetry-cli
+ Removed:
- crossing-screens
- debhelper-compatibility-level-not-a-number
- debian-tests-control-and-control-autodep8
- exclusive-runtime-tests-field
- package-contains-devhelp-file-without-symlink
.
[ Axel Beckert ]
* Adopting Lintian. (Changes #1012289 from ITA to pure RFH.)
+ Remove Chris Lamb from Uploaders (see #1012289) and re-add myself.
* Workarounds until
https://github.com/Perl-Critic/Perl-Critic/issues/925 is fixed:
+ Replace all occurrences of "Copyright ©" with "Copyright (C)" again.
+ Remove unnecessary usage of UTF-8 from bin/lintian.
+ Replace UTF-8 characters in mostly Copyright comments.
+ Replace UTF-8 characters in code with \N{…}.
* Remove literal unicode character U+0334 COMBINING TILDE OVERLAY which
likely had been added accidentally. (Triggered by the symptoms of
https://github.com/Perl-Critic/Perl-Critic/issues/925, but permanent.)
* Update copyright years in debian/copyright.
* Run perltidy over lib, bin/lintian, private/refresh-perl-provides,
private/runtests and several files in t/scripts/.
* data/…/perl-provides updated by running "debian/rules
refresh-perl-provides".
* Add Felix Lechner to debian/copyright based on copyright statements
elsewhere. Thanks for all your contributions!
* Update t/recipes/README: "debian/rules runtests" → "private/runtests"
* Follow module renaming: Perl::Critic::Freenode → Perl::…::Community.
* t/s…/h…/tag-coverage.t: Replace "$ENV{'LINTIAN_BASE'}" with
"$ENV{'LINTIAN_BASE'} // '.'" to be able to run it with "prove -l".
* init.d-general check: Avoid relying on line
Bug#1003353: marked as done (lintian: Cannot use brackets in suppression rules?)
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1003353: fixed in lintian 2.115.0
has caused the Debian Bug report #1003353,
regarding lintian: Cannot use brackets in suppression rules?
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.)
--
1003353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.114.123
Severity: normal
Hello,
Seeing that qa.debian.org is using version 2.114.123 of lintian, I
upgraded my lintian from its git tree, only to find that it seems I
cannot update my suppression rule according to the new output:
W: libbrlapi-dev: bad-whatis-entry
[usr/share/man/man3/brlapi_authClientPacket_t.3.gz]
W: libbrlapi-dev: mismatched-override bad-whatis-entry
[usr/share/man/man3/brlapi_*] [usr/share/lintian/overrides/libbrlapi-dev:2]
I did have updated this rule to include brackets:
bad-whatis-entry [usr/share/man/man3/brlapi_*]
but that doesn't seem to be working. I also tried to use escaping (which
had fixed things for the ${} case), but to no avail:
bad-whatis-entry \[usr/share/man/man3/brlapi_*\]
Lintian has recently been annoying enough that I'm unsure I'd continue
monitoring its output any more.
Samuel
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500,
'proposed-updates-debug'), (500, 'proposed-updates'), (500,
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500,
'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'),
(500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages lintian depends on:
ii binutils2.37-10.1
ii bzip2 1.0.8-5
ii diffstat1.64-1
ii dpkg1.21.1
ii dpkg-dev1.21.1
ii file1:5.41-2
ii gettext 0.21-4
ii gpg 2.2.27-2
ii intltool-debian 0.35.0+20060710.5
ii iso-codes 4.8.0-1
ii libapt-pkg-perl 0.1.40
ii libarchive-zip-perl 1.68-1
ii libcapture-tiny-perl0.48-1
ii libclass-xsaccessor-perl1.19-3+b7
ii libclone-perl 0.45-1+b1
ii libconfig-tiny-perl 2.27-1
ii libconst-fast-perl 0.014-1.1
ii libcpanel-json-xs-perl 4.27-1
ii libdata-dpath-perl 0.58-1
ii libdata-validate-domain-perl0.10-1.1
ii libdata-validate-uri-perl 0.07-1
ii libdevel-size-perl 0.83-1+b2
pn libdigest-sha-perl
ii libdpkg-perl1.21.1
ii libemail-address-xs-perl1.04-1+b3
ii libencode-perl 3.16-1
ii libfile-basedir-perl0.09-1
ii libfile-find-rule-perl 0.34-1
ii libfont-ttf-perl1.06-1.1
ii libhtml-html5-entities-perl 0.004-1.1
ii libhtml-tokeparser-simple-perl 3.16-4
ii libio-interactive-perl 1.023-1
ii libio-prompt-tiny-perl 0.003-1
ii libipc-run3-perl0.048-2
ii libjson-maybexs-perl1.004003-1
ii liblist-compare-perl0.55-1
ii liblist-someutils-perl 0.58-1
ii liblist-utilsby-perl0.11-1
ii libmoo-perl 2.005004-3
ii libmoox-aliases-perl0.001006-1.1
ii libnamespace-clean-perl 0.27-1
ii libpath-tiny-perl 0.120-1
ii libperlio-gzip-perl 0.19-1+b7
ii libperlio-utf8-strict-perl 0.008-1+b1
ii libproc-processtable-perl 0.634-1
ii libsereal-decoder-perl 4.018+ds-1+b1
ii libsereal-encoder-perl 4.018+ds-1+b1
ii libsort-versions-perl 1.62-1
ii libsyntax-keyword-try-perl 0.26-1
ii libterm-readkey-perl2.38-1+b2
ii libtext-glob-perl 0.11-2
ii libtext-levenshteinxs-perl 0.03-4+b8
ii libtext-markdown-discount-perl 0.13-1
ii libtext-xslate-perl
Bug#1003272: marked as done (lintian: chokes on overrides with "(" but no ")")
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1003272: fixed in lintian 2.115.0
has caused the Debian Bug report #1003272,
regarding lintian: chokes on overrides with "(" but no ")"
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.)
--
1003272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.114.0
Severity: normal
Documentation seems to imply. that overrides only use * [1] and ? [2]
as wildcards.
However, if I have the following override:
solarpowerlog: skip-systemd-native-flag-missing-pre-depends (does not satisfy
init-system-helpers*
lintian breaks with:
Unmatched ( in regex; marked by <-- HERE in m/( <-- HERE does not satisfy
init-system-helpers.*/ at
/usr/share/lintian/bin/../lib/Lintian/Processable/Overrides.pm line 228.
Not sure if thi is just an documentation issue (is there intentional regexp
support?) or unintended behaviour.
[1] from: file:///usr/share/doc/lintian/lintian.html#overrides
Many tags can occur more than once (e.g. if the same error is found in more
than one file). You can override a tag either completely by specifying its name
(first line in the examples) or only one occurrence of it by specifying the
additional info, too (second line in the examples). If you add an asterisk (*)
in the additional info, this will match arbitrary strings similar to the shell
wildcard. For example:
[2] inconsitent/different from [1], additionally
https://lintian.debian.org/tags/mismatched-override?version=2.104.325 says
that:
"You can use wildcards, such as * or ? in the context to make a match more
likely."
--
tobi
-- System Information:
Debian Release: bookworm/sid
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.0-2-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 lintian depends on:
ii binutils2.37-10.1
ii bzip2 1.0.8-5
ii diffstat1.64-1
ii dpkg1.21.1
ii dpkg-dev1.21.1
ii file1:5.41-2
ii gettext 0.21-4
ii gpg 2.2.27-3
ii intltool-debian 0.35.0+20060710.5
ii libapt-pkg-perl 0.1.40
ii libarchive-zip-perl 1.68-1
ii libcapture-tiny-perl0.48-1
ii libclass-xsaccessor-perl1.19-3+b7
ii libclone-perl 0.45-1+b1
ii libconfig-tiny-perl 2.27-1
ii libconst-fast-perl 0.014-1.1
ii libcpanel-json-xs-perl 4.27-1
ii libdata-dpath-perl 0.58-1
ii libdata-validate-domain-perl0.10-1.1
ii libdata-validate-uri-perl 0.07-1
ii libdevel-size-perl 0.83-1+b2
pn libdigest-sha-perl
ii libdpkg-perl1.21.1
ii libemail-address-xs-perl1.04-1+b3
ii libfile-basedir-perl0.09-1
ii libfile-find-rule-perl 0.34-1
ii libfont-ttf-perl1.06-1.1
ii libhtml-html5-entities-perl 0.004-1.1
ii libio-interactive-perl 1.023-1
ii libio-prompt-tiny-perl 0.003-1
ii libipc-run3-perl0.048-2
ii libjson-maybexs-perl1.004003-1
ii liblist-compare-perl0.55-1
ii liblist-someutils-perl 0.58-1
ii liblist-utilsby-perl0.11-1
ii libmoo-perl 2.005004-3
ii libmoox-aliases-perl0.001006-1.1
ii libnamespace-clean-perl 0.27-1
ii libpath-tiny-perl 0.120-1
ii libperlio-gzip-perl 0.19-1+b7
ii libperlio-utf8-strict-perl 0.008-1+b1
ii libproc-processtable-perl 0.634-1
ii libsereal-decoder-perl 4.018+ds-1+b1
ii libsereal-encoder-perl 4.018+ds-1+b1
ii libsort-versions-perl 1.62-1
ii libsyntax-keyword-try-perl 0.26-1
ii libterm-readkey-perl2.38-1+b2
ii libtext-glob-perl 0.11-2
ii libtext-levenshteinxs-perl 0.03-4+b8
ii libtext-markdown-discount-perl 0.13-1
ii
Bug#1000234: marked as done (lintian: Compare Debhelper prerequisites accurately w/r/t multiarch acceptor)
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1000234: fixed in lintian 2.115.0
has caused the Debian Bug report #1000234,
regarding lintian: Compare Debhelper prerequisites accurately w/r/t multiarch
acceptor
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.)
--
1000234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.111.44
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainers,
lintian 2.111.44 flagged cmake with
E: missing-build-dependency-for-dh_-command dh_sphinxdoc => sphinx |
python-sphinx | python3-sphinx
However, cmake actually build-depends on dh-sequence-sphinxdoc, which
pulls in the required dependency.
Cheers
Timo
-BEGIN PGP SIGNATURE-
iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmGURu8ACgkQ+C8H+466
LVnLVQwAklzvY6HStcrjIiP2PzGHbnAGySarYWGW5ZfVSzMFXMb5a/kIOZh3fKNW
SljHl5zIupEhm4hZaWn0GHXQUgxpaMqywDbgA13NpF66l3pAzQLrQZSqilo+WUj6
ZOXyCgV1AhTSnM9YX/aJg8hcvObs+BH/SkFS2SpTqrd9xX3L4aE0jSL10Sxid3Hb
Hk7gdHpniWhGTZbkgOw27jlW/l5glRO4BMUYZjzFzj8IC7OXLeqIuoh61WnEMUWx
qNLe0mhG+Xx56Qtlcg3qHWBzqrMbejJ7ImlmclXyviD8zviFu5WozBP7o1dJHR4o
KFSfaBwubtrNR2bAdUZvcDjCQT2BK2YoJpI/gTsNedtQhWscGL2NCr1HZtvb/aLE
kFcJXZu6Zqz1mFa3R29nMIcHEXioTN+IVQDC7I2O2qAtaCUSpeGxPafeAn6ayK8f
ZvnDEJ5QFh0nZpz0snnr7ypTsF1Gab9MIMm25pNJbuE835vZf6bdNoYpifnHL6Zg
rzZtBYqP
=3pA1
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.115.0
Done: Axel Beckert
We believe that the bug you reported is fixed in the latest version of
lintian, 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 1000...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Axel Beckert (supplier of updated lintian 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: Mon, 20 Jun 2022 13:23:02 +0200
Source: lintian
Architecture: source
Version: 2.115.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers
Changed-By: Axel Beckert
Closes: 657390 932634 941656 963099 989381 995286 996740 999768 999810 1000234
1000977 1001655 1002828 1003131 1003272 1003353 1003456 1003668 1003817 1003913
1003941 1004231 1004239 1004240 1004660 1005046 1005184 1005762 1006390 1006859
1007140 1007257 1012090
Changes:
lintian (2.115.0) unstable; urgency=medium
.
The Lintian Resurrection Release.
.
* Summary of tag changes:
+ Added:
- alien-tag
- chown-with-dot
- conflicting-test-fields
- declare-python-versions-for-test
- drop-python-version-declaration
- invalid-override-restriction
- missing-prerequisite-for-pyproject-backend
- old-devhelp-standard
- stray-devhelp-documentation
- test-leaves-python-version-untested
- uses-poetry-cli
+ Removed:
- crossing-screens
- debhelper-compatibility-level-not-a-number
- debian-tests-control-and-control-autodep8
- exclusive-runtime-tests-field
- package-contains-devhelp-file-without-symlink
.
[ Axel Beckert ]
* Adopting Lintian. (Changes #1012289 from ITA to pure RFH.)
+ Remove Chris Lamb from Uploaders (see #1012289) and re-add myself.
* Workarounds until
https://github.com/Perl-Critic/Perl-Critic/issues/925 is fixed:
+ Replace all occurrences of "Copyright ©" with "Copyright (C)" again.
+ Remove unnecessary usage of UTF-8 from bin/lintian.
+ Replace UTF-8 characters in mostly Copyright comments.
+ Replace UTF-8 characters in code with \N{…}.
* Remove literal unicode character U+0334 COMBINING TILDE OVERLAY which
likely had been added accidentally. (Triggered by the symptoms of
https://github.com/Perl-Critic/Perl-Critic/issues/925, but permanent.)
* Update copyright years in debian/copyright.
* Run perltidy over lib, bin/lintian, private/refresh-perl-provides,
private/runtests and several files in t/scripts/.
* data/…/perl-provides updated by running "debian/rules
refresh-perl-provides".
* Add Felix
Processed: Bug#1003353 marked as pending in lintian
Processing control commands: > tag -1 pending Bug #1003353 [lintian] lintian: Cannot use brackets in suppression rules? Ignoring request to alter tags of bug #1003353 to the same tags previously set -- 1003353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003353: marked as pending in lintian
Control: tag -1 pending Hello, Bug #1003353 in lintian 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/lintian/lintian/-/commit/91b36bc14ea6d011b4107bb21b2a80c18aa0586f Replace unfitting Text::Glob with more flexible Regexp::Wildcards Write a match_glob() function which emulates Text::Glob's match_glob() preconfigured for Lintian's needs, put it into Lintian::Utils and allow to export it from there. The mentioned preconfiguration for just using the "Jokers" set of Regexp::Wildcards fixes the issues with brackets in overrides which Lintian had since the introduction of Text::Glob in commit 139009d5a54225ebff4509ec37b979cb898c17fe. Closes: #1003353 This also allows us to remove one item from the exception list for Perl::Critic's Variables::ProhibitPackageVars policy as we no more need to configure Text::Glob every time (!) when we call match_glob(). Also update the dependencies accordingly. (this message was generated automatically) -- Greetings https://bugs.debian.org/1003353
Processed: Re: guile-2.2: FTBFS due to web-server.test error
Processing control commands: > severity -1 important Bug #994930 [guile-2.2] guile-2.2: FTBFS due to web-server.test error Severity set to 'important' from 'serious' -- 994930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#994930: guile-2.2: FTBFS due to web-server.test error
Control: severity -1 important
On Thu, 23 Sep 2021 16:19:54 +0530 Vignesh Raman
wrote:
> Package: guile-2.2
> Version: 2.2.7+1-6
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: vignesh.ra...@collabora.com
>
> Dear Maintainer,
>
> When building the guile-2.2_2.2.7+1-6, it failed to build from the source for
> arm64.
>
> The below error was seen,
>
> Running web-server.test
> ERROR: web-server.test: GET / - arguments: ((system-error "connect" "~A"
> ("Connection refused") (111)))
> Running web-uri.test
> UNRESOLVED: web-uri.test: build-uri: http://ill\xe9gal.com
> UNRESOLVED: web-uri.test: string->uri: http://www.example.com (sv_SE)
>
> Totals for this test run:
> passes: 41898
> failures: 0
> unexpected passes: 0
> expected failures: 10
> unresolved test cases: 578
> untested test cases:1
> unsupported test cases: 1
> errors: 1
>
> FAIL: check-guile
> ==
> 1 of 1 test failed
>
> The failure is not always reproducible and looks to be an intermittent issue.
> Similar error is reported in https://bugs.gentoo.org/712362
>
> Please could you check this issue. Thanks.
>
> Regards,
> Vignesh
Thank you for the report, Vignesh.
As this issue is rather intermittent, and it has happened only once on
the Debian arm64 buildd for 2.2.3+1-2 back in 2018 (see
https://buildd.debian.org/status/logs.php?pkg=guile-2.2=arm64 ;
all other intermittent build errors were due to test-out-of-memory),
and since guile-2.2 has been building fine on all architectures, I am
hereby downgrading the severity from "serious" to "important".
Cheers,
Anthony Fok
Bug#1013258: marked as done (autoreconf: error: /usr/bin/autoconf failed with exit status: 1)
Your message dated Mon, 20 Jun 2022 14:00:32 +0200 with message-id and subject line Re: Bug#1013258: autoreconf: error: /usr/bin/autoconf failed with exit status: 1 has caused the Debian Bug report #1013258, regarding autoreconf: error: /usr/bin/autoconf failed with exit status: 1 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.) -- 1013258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openslide Severity: important Tags: ftbfs Dear Maintainer, It seems openslide does not build anymore. See for instance: * https://salsa.debian.org/med-team/openslide/-/jobs/2899560 -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-0.bpo.4-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Control: tags -1 wontfix On Mon, Jun 20, 2022 at 1:39 PM Andreas Tille wrote: > > Am Mon, Jun 20, 2022 at 10:38:12AM +0200 schrieb Mathieu Malaterre: > > Source: openslide > > Severity: important > > Tags: ftbfs > > > > Dear Maintainer, > > > > It seems openslide does not build anymore. See for instance: > > > > * https://salsa.debian.org/med-team/openslide/-/jobs/2899560 > > I wonder why you assume that this is an autoreconf issue after you > removed Build-Depends that are seeked for: Fixed: efaad2d. > configure.ac:PKG_CHECK_MODULES(GLIB2, [glib-2.0 >= 2.16, gthread-2.0, > gio-2.0, gobject-2.0]) I was expecting a line saying the opposite of: [...] checking for glib-2.0 >= 2.16, gthread-2.0, gio-2.0, gobject-2.0... yes [...] Anyway, point taken, I'll stay away from autotool and such in the future. Thanks,--- End Message ---
Bug#1013258: autoreconf: error: /usr/bin/autoconf failed with exit status: 1
Control: tags -1 wontfix On Mon, Jun 20, 2022 at 1:39 PM Andreas Tille wrote: > > Am Mon, Jun 20, 2022 at 10:38:12AM +0200 schrieb Mathieu Malaterre: > > Source: openslide > > Severity: important > > Tags: ftbfs > > > > Dear Maintainer, > > > > It seems openslide does not build anymore. See for instance: > > > > * https://salsa.debian.org/med-team/openslide/-/jobs/2899560 > > I wonder why you assume that this is an autoreconf issue after you > removed Build-Depends that are seeked for: Fixed: efaad2d. > configure.ac:PKG_CHECK_MODULES(GLIB2, [glib-2.0 >= 2.16, gthread-2.0, > gio-2.0, gobject-2.0]) I was expecting a line saying the opposite of: [...] checking for glib-2.0 >= 2.16, gthread-2.0, gio-2.0, gobject-2.0... yes [...] Anyway, point taken, I'll stay away from autotool and such in the future. Thanks,
Processed: Re: Bug#1013258: autoreconf: error: /usr/bin/autoconf failed with exit status: 1
Processing control commands: > tags -1 wontfix Bug #1013258 [src:openslide] autoreconf: error: /usr/bin/autoconf failed with exit status: 1 Added tag(s) wontfix. -- 1013258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013258: autoreconf: error: /usr/bin/autoconf failed with exit status: 1
Am Mon, Jun 20, 2022 at 10:38:12AM +0200 schrieb Mathieu Malaterre: > Source: openslide > Severity: important > Tags: ftbfs > > Dear Maintainer, > > It seems openslide does not build anymore. See for instance: > > * https://salsa.debian.org/med-team/openslide/-/jobs/2899560 I wonder why you assume that this is an autoreconf issue after you removed Build-Depends that are seeked for: configure.ac:PKG_CHECK_MODULES(GLIB2, [glib-2.0 >= 2.16, gthread-2.0, gio-2.0, gobject-2.0]) Kind regards Andreas. -- http://fam-tille.de
Bug#1003353: tagging 1012326, tagging 1012690, tagging 1012464, tagging 1001317, tagging 1012221, tagging 1011807 ...
Hi Andreas, Andreas Beckmann wrote: > On 19/06/2022 16.27, Axel Beckert wrote: > > please explain what makes you think that this issue is present in > > lintian 2.114.0 as currently in Debian Unstable. > > The BTS does not understand made up versions (i.e. versions not in the > archive), Yes, I'm aware of that. > so this bug shows up e.g. as a RC bug in stable. Ah! I wasn't aware of that. Thanks for the explanation. I mostly consider these non-official versions to be informational for humans. Didn't expect such an impact. > So limiting this bug with an incorrect version to sid+ was the > smaller lie ... Well, I prefer the tagging much more than the wrong version, even if it's the same lie. That way there's more information in there for us humans. And yes, that weird versioning the previous maintainers started and even claim that it is semantic versioning despite it's not semantic versioning (https://semver.org/) at all, will likely be killed, once I understand how lintian.d.o works (or not) nowadays. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#1004048: marked as done (golang-github-komkom-toml: autopkgtest regression on armhf/i386: -{"hex3":3735928559}, +{"hex3":-559038737})
Your message dated Mon, 20 Jun 2022 10:04:39 +
with message-id
and subject line Bug#1004048: fixed in golang-github-komkom-toml
0.0~git20211215.3c8ee9d-2
has caused the Debian Bug report #1004048,
regarding golang-github-komkom-toml: autopkgtest regression on armhf/i386:
-{"hex3":3735928559}, +{"hex3":-559038737}
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.)
--
1004048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-komkom-toml
Version: 0.0~git20211215.3c8ee9d-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of golang-github-komkom-toml the autopkgtest of
golang-github-komkom-toml fails in testing when that autopkgtest is run
with the binary packages of golang-github-komkom-toml from unstable on
armhf and i386. It passes when run with only packages from testing. In
tabular form:
passfail
golang-github-komkom-toml from testing0.0~git20211215.3c8ee9d-1
all othersfrom testingfrom testing
I copied some of the output at the bottom of this report. Seems like a
32 bit issue where some value overflows.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=golang-github-komkom-toml
https://ci.debian.net/data/autopkgtest/testing/armhf/g/golang-github-komkom-toml/18432554/log.gz
[info] Testing github.com/komkom/toml...
[info] Source code installed by binary package, overriding
dh_auto_configure...
dh build --builddirectory=_build --buildsystem=golang --with=golang
dh_update_autotools_config -O--builddirectory=_build
-O--buildsystem=golang
dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
debian/rules override_dh_auto_configure
make[1]: Entering directory
'/tmp/autopkgtest-lxc.qwkbqa0f/downtmp/autopkgtest_tmp'
mkdir -p "_build"
cp -a /usr/share/gocode/src "_build"
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.qwkbqa0f/downtmp/autopkgtest_tmp'
dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
cd _build && go install -trimpath -v -p 160 github.com/komkom/toml
github.com/komkom/toml/internal
unicode/utf8
internal/unsafeheader
internal/goexperiment
math/bits
runtime/internal/sys
internal/itoa
internal/race
internal/abi
internal/cpu
sync/atomic
unicode
runtime/internal/math
math
runtime/internal/atomic
internal/bytealg
runtime
internal/reflectlite
sync
internal/testlog
errors
sort
internal/oserror
path
io
strconv
syscall
bytes
strings
reflect
internal/syscall/execenv
internal/syscall/unix
time
io/fs
internal/poll
internal/fmtsort
os
fmt
github.com/pkg/errors
github.com/komkom/toml/internal
github.com/komkom/toml
dh_auto_test -O--builddirectory=_build -O--buildsystem=golang
cd _build && go test -vet=off -v -p 160 github.com/komkom/toml
github.com/komkom/toml/internal
=== RUN TestReader
reader_test.go:169: doc a."b".d=2
reader_test.go:169: doc a.'b.c.d'.d=2
a.b.c.d=2
reader_test.go:169: doc a."\u".c=1
reader_test.go:169: doc a."\UD7FF16".c=1
reader_test.go:169: doc key = """\u"""
reader_test.go:169: doc key = """\UD7FF16"""
reader_test.go:169: doc key = [0,1,2,3,4]
reader_test.go:169: doc key = [1,2,3,4,0]
reader_test.go:169: doc key={a=0}
reader_test.go:169: doc key-test=1
reader_test.go:169: doc k.e .y=1
reader_test.go:169: dock . e .y=1
reader_test.go:169: doc"k" . 'e' .y=1
reader_test.go:169: doc animal = { type.name = "pug"}
reader_test.go:169: doc key = {v.y=1}
reader_test.go:169: doc a = "\r"
reader_test.go:169: doc another = "# test"
reader_test.go:169: doc 'quoted "value"' = "value"
reader_test.go:169: doc hex3 = 0x123_123
reader_test.go:169: doc hex3 = 0xdead_beef
reader_test.go:184: Error Trace:reader_test.go:184
Error: Not equal: expected:
"{\"hex3\":3735928559}"
actual : "{\"hex3\":-559038737}"
Bug#1004048: marked as pending in golang-github-komkom-toml
Control: tag -1 pending Hello, Bug #1004048 in golang-github-komkom-toml 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/go-team/packages/golang-github-komkom-toml/-/commit/29928b19c53475f93d08882504b9722dda3a3b0a Fix failing tests on 32 bit architectures Closes: #1004048 Origin: upstream, https://github.com/komkom/toml/pull/6 Signed-off-by: Benjamin Drung (this message was generated automatically) -- Greetings https://bugs.debian.org/1004048
Processed: Bug#1004048 marked as pending in golang-github-komkom-toml
Processing control commands:
> tag -1 pending
Bug #1004048 [src:golang-github-komkom-toml] golang-github-komkom-toml:
autopkgtest regression on armhf/i386: -{"hex3":3735928559}, +{"hex3":-559038737}
Added tag(s) pending.
--
1004048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service
Ben,
> I wrote a script to check for short signatures (and other unexpected
> things) in detached signature files:
> https://salsa.debian.org/kernel-team/kernel-team/-/blob/master/scripts/benh/check-sig-params
Thank you for your excellent detective work!
I tried running your script, but it generates an error (see below).
What am I doing wrong?
Thank you again!
Dan
Urbana, Illinois
---
$ dpkg-query -f='${Package} ${Version}\n' -W python3 python3-asn1crypto
python3 3.9.2-3
python3-asn1crypto 1.4.0-1
$ check-sig-params /lib/modules/5.10.0-15-amd64/kernel/net/netfilter/xt_l2tp.ko
/lib/modules/5.10.0-15-amd64/kernel/net/netfilter/xt_l2tp.ko: Error
parsing asn1crypto.cms.ContentInfo - class should have been universal,
but application was found)
###
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 1013258 grave Bug #1013258 [src:openslide] autoreconf: error: /usr/bin/autoconf failed with exit status: 1 Severity set to 'grave' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 1013258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011540: burp: autopkgtest regression with openssl 3
I raised the issue to the upstream developer, and he is working on it: https://github.com/grke/burp/issues/904 He is very responsive and gentle. On Tue, 24 May 2022 20:53:39 +0200 Sebastian Ramacher wrote: > Source: burp > Version: 2.4.0-3 > Severity: serious > Tags: sid bookworm > > burp's autopkgtest fail with openssl 3: > > make[2]: Entering directory '/tmp/autopkgtest-lxc.lg0p9u2a/downtmp/build.c19/src' > FAIL: runner > > Testsuite summary for Burp 2.4.0 > > # TOTAL: 1 > # PASS: 0 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > See ./test-suite.log > Please report to https://github.com/grke/burp/issues > > make[2]: *** [Makefile:8640: test-suite.log] Error 1 > make[2]: Leaving directory '/tmp/autopkgtest-lxc.lg0p9u2a/downtmp/build.c19/src' > make[1]: *** [Makefile:8748: check-TESTS] Error 2 > make[1]: Leaving directory '/tmp/autopkgtest-lxc.lg0p9u2a/downtmp/build.c19/src' > make: *** [Makefile:8959: check-am] Error 2 > autopkgtest [09:14:37]: test burp-unit-test: ---] > > > See > https://ci.debian.net/data/autopkgtest/testing/amd64/b/burp/22058117/log.gz > > Cheers > -- > Sebastian Ramacher > >
Processed: reassign 1013211 to src:linux, reassign 1012797 to iptables, reassign 548074 to src:log4cxx ...
Processing commands for cont...@bugs.debian.org:
> reassign 1013211 src:linux
Bug #1013211 [kernel] System freeze followed by kernel panic or blank screen
Warning: Unknown package 'kernel'
Bug reassigned from package 'kernel' to 'src:linux'.
No longer marked as found in versions 5.16.0-0.bpo.4-amd64.
Ignoring request to alter fixed versions of bug #1013211 to the same values
previously set
> reassign 1012797 iptables 1.8.2-4
Bug #1012797 [iptables-1.8.2-4] iptables-1.8.2-4: Segmentation fault caused by
iptables with no matching rules.
Warning: Unknown package 'iptables-1.8.2-4'
Bug reassigned from package 'iptables-1.8.2-4' to 'iptables'.
Ignoring request to alter found versions of bug #1012797 to the same values
previously set
Ignoring request to alter fixed versions of bug #1012797 to the same values
previously set
Bug #1012797 [iptables] iptables-1.8.2-4: Segmentation fault caused by iptables
with no matching rules.
Marked as found in versions iptables/1.8.2-4.
> reassign 548074 src:log4cxx 0.10.0-1
Bug #548074 {Done: Tobias Frost } [liblog4cxx12] [liblog4cxx]
Inproper signal handling for spawned threads
Warning: Unknown package 'liblog4cxx12'
Bug reassigned from package 'liblog4cxx12' to 'src:log4cxx'.
Ignoring request to alter found versions of bug #548074 to the same values
previously set
No longer marked as fixed in versions log4cxx/0.13.0-1.
Bug #548074 {Done: Tobias Frost } [src:log4cxx] [liblog4cxx]
Inproper signal handling for spawned threads
Marked as found in versions log4cxx/0.10.0-1.
> fixed 548074 0.13.0-1
Bug #548074 {Done: Tobias Frost } [src:log4cxx] [liblog4cxx]
Inproper signal handling for spawned threads
Marked as fixed in versions log4cxx/0.13.0-1.
> tags 981224 + experimental
Bug #981224 [src:ruby-uglifier] ruby-uglifier: FTBFS: tests fail:
uglifier_spec.rb:383, uglifier_spec.rb:751
Added tag(s) experimental.
> found 1013218 3.7.2-3
Bug #1013218 [ruby-sprockets] rails: ftbfs SyntaxError: Unexpected token
'export'
Marked as found in versions ruby-sprockets/3.7.2-3.
> tags 1012774 - sid bookworm
Bug #1012774 {Done: Paul Gevers } [src:git] src:git: fails
to migrate to testing for too long: piuparts reports issue
Removed tag(s) bookworm and sid.
> notfound 1004701 1.4-1.2
Bug #1004701 {Done: Bastian Germann } [src:ima-evm-utils]
ima-evm-utils: Backport for bullseye
No longer marked as found in versions ima-evm-utils/1.4-1.2.
> fixed 1004701 1.4-1.2
Bug #1004701 {Done: Bastian Germann } [src:ima-evm-utils]
ima-evm-utils: Backport for bullseye
Marked as fixed in versions ima-evm-utils/1.4-1.2.
> reassign 1010888 node-dateformat 5.0.3-1
Bug #1010888 {Done: Pirate Praveen } [grunt] grunt:
autopkgtest failure with node-dateformat 5.0 in experimental - change the
require of dateformat.js to a dynamic import() which is available in all
CommonJS modules
Bug reassigned from package 'grunt' to 'node-dateformat'.
No longer marked as found in versions grunt/1.5.2-2.
No longer marked as fixed in versions node-dateformat/5.0.3-2.
Bug #1010888 {Done: Pirate Praveen } [node-dateformat]
grunt: autopkgtest failure with node-dateformat 5.0 in experimental - change
the require of dateformat.js to a dynamic import() which is available in all
CommonJS modules
There is no source info for the package 'node-dateformat' at version '5.0.3-1'
with architecture ''
Unable to make a source version for version '5.0.3-1'
Marked as found in versions 5.0.3-1.
> fixed 1010888 5.0.3-2
Bug #1010888 {Done: Pirate Praveen } [node-dateformat]
grunt: autopkgtest failure with node-dateformat 5.0 in experimental - change
the require of dateformat.js to a dynamic import() which is available in all
CommonJS modules
There is no source info for the package 'node-dateformat' at version '5.0.3-2'
with architecture ''
Unable to make a source version for version '5.0.3-2'
Marked as fixed in versions 5.0.3-2.
> affects 1010888 + src:grunt
Bug #1010888 {Done: Pirate Praveen } [node-dateformat]
grunt: autopkgtest failure with node-dateformat 5.0 in experimental - change
the require of dateformat.js to a dynamic import() which is available in all
CommonJS modules
Added indication that 1010888 affects src:grunt
> reassign 984794 calamares-settings-debian
Bug #984794 {Done: Jonathan Carter } [calamares] calamares:
use eatmydata to speed up last installation step (60remove-live-packages)
Bug reassigned from package 'calamares' to 'calamares-settings-debian'.
No longer marked as found in versions calamares/3.2.36-1.
No longer marked as fixed in versions calamares-settings-debian/12.0.1-1.
> fixed 984794 12.0.1-1
Bug #984794 {Done: Jonathan Carter }
[calamares-settings-debian] calamares: use eatmydata to speed up last
installation step (60remove-live-packages)
Marked as fixed in versions calamares-settings-debian/12.0.1-1.
> affects 984794 + src:calamares
Bug #984794 {Done: Jonathan Carter }
[calamares-settings-debian] calamares: use eatmydata to speed up last
installation step (60remove-live-packages)
Added
Bug#1012802: marked as done (python3-ipykernel: breaks jupyter notebook)
Your message dated Mon, 20 Jun 2022 09:18:43 +0200 with message-id <283db8a509c43c26e3a932be0193ebc06c6f0076.ca...@gmail.com> and subject line Fixed package migrated to testing: closing has caused the Debian Bug report #1012802, regarding python3-ipykernel: breaks jupyter notebook 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.) -- 1012802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-ipykernel Version: 6.13.1-1 Severity: serious Dear Debian Python Modules Team, trying to load a jupyter notebook fails with the message /usr/bin/python3: No module named ipykernel_launcher Indeed, in the package there is no file `/usr/lib/python3/dist-packages/ipykernel_launcher.py` any more. Not any file in `/usr/lib/`. Regards, Jörg. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.18.3 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages python3-ipykernel depends on: ii python33.9.8-1 ii python3-ipython7.31.1-1 ii python3-jupyter-client 7.3.4-1 ii python3-matplotlib-inline 0.1.3-1 ii python3-nest-asyncio 1.5.4-1 ii python3-packaging 21.3-1 ii python3-psutil 5.9.0-1 ii python3-tornado6.1.0-3 ii python3-traitlets 5.2.2-1 python3-ipykernel recommends no packages. python3-ipykernel suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Hi, since the fixed package migrated to testing already, this bug report can be closed. Cheers, J.Puydt--- End Message ---
Processed: Re: tagging 1012326, tagging 1012690, tagging 1012464, tagging 1001317, tagging 1012221, tagging 1011807 ...
Processing control commands: > tag -1 sid Bug #1003353 [lintian] lintian: Cannot use brackets in suppression rules? Added tag(s) sid. -- 1003353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003353: tagging 1012326, tagging 1012690, tagging 1012464, tagging 1001317, tagging 1012221, tagging 1011807 ...
Control: tag -1 sid On 19/06/2022 16.27, Axel Beckert wrote: please explain what makes you think that this issue is present in lintian 2.114.0 as currently in Debian Unstable. The BTS does not understand made up versions (i.e. versions not in the archive), so this bug shows up e.g. as a RC bug in stable. So limiting this bug with an incorrect version to sid+ was the smaller lie ... Andreas
