Bug#1033816: marked as done (node-interpret: autopkgtest regression: Unable to use specified module loaders for ".babel.js".)
Your message dated Mon, 03 Apr 2023 04:33:57 + with message-id and subject line Bug#1033816: fixed in node-interpret 2.2.0-3 has caused the Debian Bug report #1033816, regarding node-interpret: autopkgtest regression: Unable to use specified module loaders for ".babel.js". 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.) -- 1033816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-interpret Version: 2.2.0-2 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it started to fail recently (October 2022). Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-interpret/32157176/log.gz 52 passing (2m) 2 pending 3 failing 1) interpret.extensions can require .babel.js using babel/register (3): Error: Unable to use specified module loaders for ".babel.js". at Object.exports.prepare (/usr/share/nodejs/rechoir/index.js:58:11) at Context. (test/index.js:158:15) at callFnAsync (/usr/share/nodejs/mocha/lib/runnable.js:394:21) at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:338:7) at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:666:10) at /usr/share/nodejs/mocha/lib/runner.js:789:12 at next (/usr/share/nodejs/mocha/lib/runner.js:581:14) at /usr/share/nodejs/mocha/lib/runner.js:591:7 at next (/usr/share/nodejs/mocha/lib/runner.js:474:14) at cbHookRun (/usr/share/nodejs/mocha/lib/runner.js:539:7) at done (/usr/share/nodejs/mocha/lib/runnable.js:310:5) at callFn (/usr/share/nodejs/mocha/lib/runnable.js:389:7) at Hook.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:354:5) at next (/usr/share/nodejs/mocha/lib/runner.js:498:10) at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:559:5) at processImmediate (node:internal/timers:471:21) 2) interpret.extensions can require .buble.js using buble/register (0): TypeError: Cannot read properties of undefined (reading 'line') at getSnippet (test/fixtures/buble.js/0/node_modules/buble/src/utils/getSnippet.js:13:29) at Object.transform (test/fixtures/buble.js/0/node_modules/buble/src/index.js:72:17) at Object.require.extensions..js (test/fixtures/buble.js/0/node_modules/buble/register.js:71:21) at Module.load (node:internal/modules/cjs/loader:1081:32) at Function.Module._load (node:internal/modules/cjs/loader:922:12) at Module.require (node:internal/modules/cjs/loader:1105:19) at require (node:internal/modules/cjs/helpers:103:18) at Context. (test/index.js:231:18) at callFnAsync (/usr/share/nodejs/mocha/lib/runnable.js:394:21) at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:338:7) at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:666:10) at /usr/share/nodejs/mocha/lib/runner.js:789:12 at next (/usr/share/nodejs/mocha/lib/runner.js:581:14) at /usr/share/nodejs/mocha/lib/runner.js:591:7 at next (/usr/share/nodejs/mocha/lib/runner.js:474:14) at cbHookRun (/usr/share/nodejs/mocha/lib/runner.js:539:7) at done (/usr/share/nodejs/mocha/lib/runnable.js:310:5) at callFn (/usr/share/nodejs/mocha/lib/runnable.js:389:7) at Hook.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:354:5) at next (/usr/share/nodejs/mocha/lib/runner.js:498:10) at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:559:5) at processImmediate (node:internal/timers:471:21) 3) interpret.extensions can require .jsx using babel/register (3): Error: Unable to use specified module loaders for ".jsx". at Object.exports.prepare (/usr/share/nodejs/rechoir/index.js:58:11) at Context. (test/index.js:158:15) at callFnAsync
Bug#1033816: marked as pending in node-interpret
Control: tag -1 pending Hello, Bug #1033816 in node-interpret 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/js-team/node-interpret/-/commit/e3c2f217fee13a70bdf942bd60e5620f65339c91 Drop test on deprecated transpilers Closes: #1033816 (this message was generated automatically) -- Greetings https://bugs.debian.org/1033816
Processed: Bug#1033816 marked as pending in node-interpret
Processing control commands: > tag -1 pending Bug #1033816 [src:node-interpret] node-interpret: autopkgtest regression: Unable to use specified module loaders for ".babel.js". Added tag(s) pending. -- 1033816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033833: unknown-horizons: Fails to start Couldn't open content/fonts/Unifont.ttf
On Sun, 2 Apr 2023 18:33:34 +0200 Tobias Frost wrote: > it seems so that the fonts package unifont dropped unifont.ttf in > 1:15.0.01-1: Yes, and upstream plans to drop ttf. So I do not want to revert this change in Debian package. > Unifont 15.0.01 installs OpenType fonts alongside the TrueType fonts > that are installed in Unifont 14.0.x and previous releases. > The current plan is for Unifont 16.0.01 to no longer install TrueType > fonts that have OpenType equivalents. This will allow a period of > approximately one year for Unifont users to switch from TrueType to > OpenType files. -- Hideki Yamane
Processed: Re: Bug#1033115: golang-github-go-macaron-csrf: CVE-2018-25060
Processing control commands: > clone -1 -2 Bug #1033115 [src:golang-github-go-macaron-csrf] golang-github-go-macaron-csrf: CVE-2018-25060 Bug 1033115 cloned as bug 1033865 > retitle -2 Don't release with bookworm Bug #1033865 [src:golang-github-go-macaron-csrf] golang-github-go-macaron-csrf: CVE-2018-25060 Changed Bug title to 'Don't release with bookworm' from 'golang-github-go-macaron-csrf: CVE-2018-25060'. > submitter -2 ! Bug #1033865 [src:golang-github-go-macaron-csrf] Don't release with bookworm Changed Bug submitter to 'Shengjing Zhu ' from 'Moritz Mühlenhoff '. > severity -2 serious Bug #1033865 [src:golang-github-go-macaron-csrf] Don't release with bookworm Severity set to 'serious' from 'important' -- 1033115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033115 1033865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1033753: golang-github-crewjam-saml: CVE-2023-28119
Processing control commands: > clone -1 -2 Bug #1033753 [src:golang-github-crewjam-saml] golang-github-crewjam-saml: CVE-2023-28119 Bug 1033753 cloned as bug 1033864 > retitle -2 Don't release with bookworm Bug #1033864 [src:golang-github-crewjam-saml] golang-github-crewjam-saml: CVE-2023-28119 Changed Bug title to 'Don't release with bookworm' from 'golang-github-crewjam-saml: CVE-2023-28119'. > submitter -2 ! Bug #1033864 [src:golang-github-crewjam-saml] Don't release with bookworm Changed Bug submitter to 'Shengjing Zhu ' from 'Salvatore Bonaccorso '. > severity -2 serious Bug #1033864 [src:golang-github-crewjam-saml] Don't release with bookworm Severity set to 'serious' from 'grave' -- 1033753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033753 1033864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033864 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033753: golang-github-crewjam-saml: CVE-2023-28119
Control: clone -1 -2 Control: retitle -2 Don't release with bookworm Control: submitter -2 ! Control: severity -2 serious On Sat, Apr 1, 2023 at 2:48 AM Salvatore Bonaccorso wrote: > > Source: golang-github-crewjam-saml > Version: 0.4.12-2 > Severity: grave > Tags: security upstream > Justification: user security hole > X-Debbugs-Cc: car...@debian.org, Debian Security Team > > > Hi, > > The following vulnerability was published for golang-github-crewjam-saml. > Strictly speaking might be disputed if it is RC level, but would be > good to have it fixed in bookworm before the release. > > CVE-2023-28119[0]: > Let's remove it from bookworm. No reverse dependency. -- Shengjing Zhu
Bug#1033818: marked as done (node-nock: autopkgtest regression: Accessing Object.prototype.__proto__ has been disallowed)
Your message dated Mon, 03 Apr 2023 04:05:13 + with message-id and subject line Bug#1033818: fixed in node-sinon 14.0.2+ds+~cs74.13.25-2 has caused the Debian Bug report #1033818, regarding node-nock: autopkgtest regression: Accessing Object.prototype.__proto__ has been disallowed 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.) -- 1033818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-nock Version: 13.2.9-3 Control: found -1 13.2.9-2 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it started to fail recently (October 2022). Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-nock/32235317/log.gz 525 passing (9s) 2 pending 1 failing 1) `replyWithFile()` reply with file with repeated: Error: Accessing Object.prototype.__proto__ has been disallowed with --disable-proto=throw at /usr/share/nodejs/sinon/lib/sinon/util/core/walk.js:20:17 at Array.forEach () at walkInternal (/usr/share/nodejs/sinon/lib/sinon/util/core/walk.js:19:5) at walkInternal (/usr/share/nodejs/sinon/lib/sinon/util/core/walk.js:33:9) at walk (/usr/share/nodejs/sinon/lib/sinon/util/core/walk.js:48:12) at walkObject (/usr/share/nodejs/sinon/lib/sinon/util/core/walk-object.js:18:5) at Function.spy (/usr/share/nodejs/sinon/lib/sinon/spy.js:170:16) at Sandbox.spy (/usr/share/nodejs/sinon/lib/sinon/sandbox.js:383:35) at Context. (tests/test_reply_with_file.js:45:11) at callFn (/usr/share/nodejs/mocha/lib/runnable.js:366:21) at Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:354:5) at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:666:10) at /usr/share/nodejs/mocha/lib/runner.js:789:12 at next (/usr/share/nodejs/mocha/lib/runner.js:581:14) at /usr/share/nodejs/mocha/lib/runner.js:591:7 at next (/usr/share/nodejs/mocha/lib/runner.js:474:14) at Immediate. (/usr/share/nodejs/mocha/lib/runner.js:559:5) at process.processImmediate (node:internal/timers:471:21) OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: node-sinon Source-Version: 14.0.2+ds+~cs74.13.25-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-sinon, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-sinon 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, 03 Apr 2023 07:26:51 +0400 Source: node-sinon Built-For-Profiles: nocheck Architecture: source Version: 14.0.2+ds+~cs74.13.25-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1033818 Changes: node-sinon (14.0.2+ds+~cs74.13.25-2) unstable; urgency=medium . * Team upload * Update lintian override info format in d/source/lintian-overrides on line 2-3 * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse * Update standards version to 4.6.2, no changes needed * Drop calls to __proto__ (Closes: #1033818) Checksums-Sha1: 807160cae4623fd68bb2b8b040fa1b70246a11bd 6712 node-sinon_14.0.2+ds+~cs74.13.25-2.dsc 400f8237297134b0c43b798ee5cf6298f9cb942b 60396
Bug#1033819: marked as done (node-prosemirror-schema-list: autopkgtest regression: Accessing Object.prototype.__proto__ has been disallowed with --disable-proto=throw)
Your message dated Mon, 03 Apr 2023 04:04:48 + with message-id and subject line Bug#1033819: fixed in node-prosemirror-transform 1.2.8-5 has caused the Debian Bug report #1033819, regarding node-prosemirror-schema-list: autopkgtest regression: Accessing Object.prototype.__proto__ has been disallowed with --disable-proto=throw 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.) -- 1033819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-prosemirror-schema-list Version: 1.1.6+~1.0.3-1 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it started to fail recently (October 2022). Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-prosemirror-schema-list/32244360/log.gz # Launch debian/tests/pkg-js/test with sh -ex + mocha Error: Accessing Object.prototype.__proto__ has been disallowed with --disable-proto=throw at /usr/share/nodejs/prosemirror-transform/dist/index.js:452:37 at Object. (/usr/share/nodejs/prosemirror-transform/dist/index.js:506:2) at Module._compile (node:internal/modules/cjs/loader:1218:14) at Module._extensions..js (node:internal/modules/cjs/loader:1272:10) at Module.load (node:internal/modules/cjs/loader:1081:32) at Module._load (node:internal/modules/cjs/loader:922:12) at Module.require (node:internal/modules/cjs/loader:1105:19) at require (node:internal/modules/cjs/helpers:103:18) at Object. (/usr/share/nodejs/prosemirror-state/dist/index.js:4:28) at Module._compile (node:internal/modules/cjs/loader:1218:14) at Module._extensions..js (node:internal/modules/cjs/loader:1272:10) at Module.load (node:internal/modules/cjs/loader:1081:32) at Module._load (node:internal/modules/cjs/loader:922:12) at Module.require (node:internal/modules/cjs/loader:1105:19) at require (node:internal/modules/cjs/helpers:103:18) at Object. (/tmp/autopkgtest-lxc.8gf317sm/downtmp/autopkgtest_tmp/smokeMJk9e2/test/test-commands.js:1:64) at Module._compile (node:internal/modules/cjs/loader:1218:14) at Module._extensions..js (node:internal/modules/cjs/loader:1272:10) at Module.load (node:internal/modules/cjs/loader:1081:32) at Module._load (node:internal/modules/cjs/loader:922:12) at ModuleWrap. (node:internal/modules/esm/translators:169:29) at ModuleJob.run (node:internal/modules/esm/module_job:194:25) OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: node-prosemirror-transform Source-Version: 1.2.8-5 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-prosemirror-transform, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-prosemirror-transform 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, 03 Apr 2023 07:31:35 +0400 Source: node-prosemirror-transform Architecture: source Version: 1.2.8-5 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1033819 Changes: node-prosemirror-transform (1.2.8-5) unstable; urgency=medium . * Team upload * Set upstream metadata fields: Repository. * Update standards version to 4.6.2, no changes needed. * Drop
Bug#1033818: marked as pending in node-sinon
Control: tag -1 pending Hello, Bug #1033818 in node-sinon 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/js-team/node-sinon/-/commit/834bfa7eeff16107a82e9a00b3f91930e449b82c Drop calls to __proto__ Closes: #1033818 (this message was generated automatically) -- Greetings https://bugs.debian.org/1033818
Processed: Bug#1033819 marked as pending in node-prosemirror-transform
Processing control commands: > tag -1 pending Bug #1033819 [node-prosemirror-transform] node-prosemirror-schema-list: autopkgtest regression: Accessing Object.prototype.__proto__ has been disallowed with --disable-proto=throw Added tag(s) pending. -- 1033819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1033818 marked as pending in node-sinon
Processing control commands: > tag -1 pending Bug #1033818 [node-sinon] node-nock: autopkgtest regression: Accessing Object.prototype.__proto__ has been disallowed Added tag(s) pending. -- 1033818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033819: marked as pending in node-prosemirror-transform
Control: tag -1 pending Hello, Bug #1033819 in node-prosemirror-transform 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/js-team/node-prosemirror-transform/-/commit/6b2aa07c199d9defe7a5ebe0456cb98e481b5a2a Drop access to __proto__ Closes: #1033819 (this message was generated automatically) -- Greetings https://bugs.debian.org/1033819
Bug#1033820: [Pkg-javascript-devel] Bug#1033820: node-snapdragon: autopkgtest regression: Cannot find module 'snapdragon-node'
Control: tags -1 + moreinfo On 4/2/23 12:05, Paul Gevers wrote: Source: node-snapdragon Version: 0.12.1+~cs1.2.1-2 Control: found -1 0.12.1+~cs1.2.1-1 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it started to fail at the beginning of 2022. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul Hi, I'm unable to reproduce this issue: there is a link that provides snapdragon-node inside snapdragon-capture-set: $ debc|grep '> ' lrwxrwxrwx root/root 0 2022-12-01 17:20 ./usr/share/nodejs/snapdragon-capture-set/node_modules -> ../snapdragon/node_modules and snamdragon has snapdragon/node_modules/snapdragon-node Cheers, Yadd
Processed: Re: [Pkg-javascript-devel] Bug#1033820: node-snapdragon: autopkgtest regression: Cannot find module 'snapdragon-node'
Processing control commands: > tags -1 + moreinfo Bug #1033820 [src:node-snapdragon] node-snapdragon: autopkgtest regression: Cannot find module 'snapdragon-node' Added tag(s) moreinfo. -- 1033820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1033818 to node-sinon, affects 1033818
Processing commands for cont...@bugs.debian.org: > reassign 1033818 node-sinon Bug #1033818 [src:node-nock] node-nock: autopkgtest regression: Accessing Object.prototype.__proto__ has been disallowed Bug reassigned from package 'src:node-nock' to 'node-sinon'. No longer marked as found in versions node-nock/13.2.9-3 and node-nock/13.2.9-2. Ignoring request to alter fixed versions of bug #1033818 to the same values previously set > affects 1033818 node-nock Bug #1033818 [node-sinon] node-nock: autopkgtest regression: Accessing Object.prototype.__proto__ has been disallowed Added indication that 1033818 affects node-nock > thanks Stopping processing here. Please contact me if you need assistance. -- 1033818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1033819 to node-prosemirror-transform, affects 1033819
Processing commands for cont...@bugs.debian.org: > reassign 1033819 node-prosemirror-transform Bug #1033819 [src:node-prosemirror-schema-list] node-prosemirror-schema-list: autopkgtest regression: Accessing Object.prototype.__proto__ has been disallowed with --disable-proto=throw Bug reassigned from package 'src:node-prosemirror-schema-list' to 'node-prosemirror-transform'. No longer marked as found in versions node-prosemirror-schema-list/1.1.6+~1.0.3-1. Ignoring request to alter fixed versions of bug #1033819 to the same values previously set > affects 1033819 node-prosemirror-schema-list Bug #1033819 [node-prosemirror-transform] node-prosemirror-schema-list: autopkgtest regression: Accessing Object.prototype.__proto__ has been disallowed with --disable-proto=throw Added indication that 1033819 affects node-prosemirror-schema-list > thanks Stopping processing here. Please contact me if you need assistance. -- 1033819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033607: [Pkg-sogo-maintainers] Bug#1033607: sogo: /usr/bin/sogo linked against wrong version of libgnustep-base
Thanks Jeroen, I've looped through all the libraries used by `sogod` and it seems like `libsope1` is the culprit. A lot of libraries in that package are linked to libgnustep-base.so.1.24, despite the package requiring 1.27: $ objdump -p /usr/local/lib/libSaxObjC.so.4.9 |grep NEEDED NEEDED libgnustep-base.so.1.24 > [...] same result for these files: > /usr/local/lib/libWEExtensions.so.4.9 > /usr/local/lib/libNGStreams.so > /usr/local/lib/libNGObjWeb.so and a few more. I've tried rebuilding the package from source, but no difference. On 01/04/2023 21.19, Jeroen Dekkers wrote: Hi Phil, On Sat, 01 Apr 2023 02:41:05 +0200, Phil Gruber wrote: Thanks for getting back to me. Here's what this looks like for me: $ /usr/sbin/sogod /usr/sbin/sogod: error while loading shared libraries: libgnustep-base.so.1.24: cannot open shared object file: No such file or directory $ ldd -r /usr/sbin/sogod | grep gnustep libgnustep-base.so.1.27 => /usr/lib/libgnustep-base.so.1.27 (0x7f6c6428f000) libgnustep-base.so.1.24 => not found libgnustep-base.so.1.24 => not found libgnustep-base.so.1.24 => not found libgnustep-base.so.1.24 => not found libgnustep-base.so.1.24 => not found libgnustep-base.so.1.24 => not found libgnustep-base.so.1.24 => not found libgnustep-base.so.1.24 => not found libgnustep-base.so.1.24 => not found I just removed and re-installed the sogo package, but it didn't make a difference. Can you use objdump to figure out which files have the dependency on libgnustep-base.so.1.24? objdump -p /usr/sbin/sogod | grep NEEDED If that doesn't list libgnustep-base.so.1.24 then try libSOGo.so.5 and all the other libraries listed by ldd. Kind regards, Jeroen Dekkers
Bug#1033862: nouveau: watchdog: BUG: soft lockup - CPU#0 stuck for 548s! [kscreenlocker_g:19260]
Package: src:linux Version: 6.1.20-1 Severity: critical File: nouveau Justification: breaks the whole system X-Debbugs-Cc: af...@comcast.net When the above message occurs, the system becomes totally unresponsive and the only way to recover is a hard power-off via the power button held for about 5 seconds. Upon boot, the sddm login screen appears but at 1024x768, which is much less than the monitor is capable of: 1920x1200. xrandr Screen 0: minimum 16 x 16, current 1024 x 768, maximum 32767 x 32767 XWAYLAND0 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 59.92*+ 800x600 59.86 640x480 59.38 320x240 59.52 720x480 59.71 640x400 59.95 320x200 58.96 1024x576 59.90 864x486 59.92 720x400 59.55 640x350 59.77 After login sometimes the screen goes blank (but the backlight remains on). Hard power off required. Sometimes the gear wheel stops turning and the system freezes. Hard power off required. I have tried to install the nvidia proprietary driver 304 (NVIDIA-Linux-x86_64-304.117.run) which is what this old chip needs but it fails to install. No matter what I do the nouveau driver is in use and cannot be removed. If it were possible for nouveau and/or X/Wayland to access the whole set of resolutions of the system without hard freezes, I'd be happy. Any tricks? Any specific things I could try to figure out the issue? Obviously, in this particular boot the hard freeze did not happen. These lines seem to be relevant (from the logs below): [ 47.892652] nouveau :00:0 d.0: bus: MMIO write of 00340001 FAULT at 00b000 [ 64.113759] nouveau :00:0d.0: bus: MMIO write of 00640001 FAULT at 00b010 [ 64.114792] nouveau :00:0d.0: bus: MMIO write of 00310001 FAULT at 00b020 [ 69.614326] nouveau :00:0d.0: bus: MMIO write of FAULT at 00b020 [ 69.614542] nouveau :00:0d.0: bus: MMIO write of 00640001 FAULT at 00b010 [ 69.615432] nouveau :00:0d.0: bus: MMIO write of 00310001 FAULT at 00b020 [ 70.336843] nouveau :00:0d.0: bus: MMIO write of FAULT at 00b020 [ 70.337057] nouveau :00:0d.0: bus: MMIO write of 00640001 FAULT at 00b010 [ 70.337684] nouveau :00:0d.0: bus: MMIO write of 00660001 FAULT at 00b020 [ 70.357387] nouveau :00:0d.0: bus: MMIO write of FAULT at 00b010 [ 89.666120] nouveau :00:0d.0: bus: MMIO write of 00ca0001 FAULT at 00b010 [ 97.330127] nouveau :00:0d.0: bus: MMIO write of FAULT at 00b010 [ 104.590842] traps: light-locker[4745] trap int3 ip:7f59b65be7d7 sp:7fff472f8690 error:0 in libglib-2.0.so.0.7400.6[7f59b658+8d000] -- Package-specific info: ** Version: Linux version 6.1.0-7-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-1 (2023-03-19) ** Command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-7-amd64 root=UUID=28bd15dd-cd17-45c8-93e0-65decc995980 ro quiet ** Not tainted ** Kernel log: [6.707012] systemd[1]: Starting systemd-journald.service - Journal Service... [6.760881] systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules... [6.762291] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... [6.763752] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... [6.766133] systemd[1]: Finished kmod-static-nodes.service - Create List of Static Device Nodes. [6.766733] systemd[1]: modprobe@configfs.service: Deactivated successfully. [6.766949] systemd[1]: Finished modprobe@configfs.service - Load Kernel Module configfs. [6.767339] systemd[1]: modprobe@drm.service: Deactivated successfully. [6.767583] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm. [6.769231] systemd[1]: Mounting sys-kernel-config.mount - Kernel Configuration File System... [6.778991] systemd[1]: modprobe@efi_pstore.service: Deactivated successfully. [6.779202] systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore. [6.791834] systemd[1]: Mounted dev-mqueue.mount - POSIX Message Queue File System. [6.792129] systemd[1]: Mounted sys-kernel-debug.mount - Kernel Debug File System. [6.792350] systemd[1]: Mounted sys-kernel-tracing.mount - Kernel Trace File System. [6.792608] systemd[1]: Mounted sys-kernel-config.mount - Kernel Configuration File System. [6.829931] systemd[1]: Mounted dev-hugepages.mount - Huge Pages File System. [6.853427] loop: module loaded [6.854583] systemd[1]: modprobe@loop.service: Deactivated successfully. [6.854794] systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop. [6.857921] fuse: init (API version 7.37) [6.858998] systemd[1]: modprobe@fuse.service: Deactivated successfully. [6.859199] systemd[1]:
Processed: forwarded
Processing commands for cont...@bugs.debian.org: > forwarded 1033851 https://github.com/rhattersley/pyepsg/issues/22 Bug #1033851 [src:python-pyepsg] python-pyepsg: autopkgtest regression: xml.etree.ElementTree.ParseError: not well-formed (invalid token) Set Bug forwarded-to-address to 'https://github.com/rhattersley/pyepsg/issues/22'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1033851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033850: marked as done (python-docx: autopkgtest regression: No module named 'pyparsing')
Your message dated Sun, 02 Apr 2023 20:49:15 + with message-id and subject line Bug#1033850: fixed in python-docx 0.8.11+dfsg1-5 has caused the Debian Bug report #1033850, regarding python-docx: autopkgtest regression: No module named 'pyparsing' 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.) -- 1033850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-docx Version: 0.8.11+dfsg1-4 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails since January 2023. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-docx/32174602/log.gz ERRORS ___ ERROR collecting tests/test_blkcntnr.py ImportError while importing test module '/tmp/autopkgtest-lxc.fuv79e8l/downtmp/build.YjC/src/tests/test_blkcntnr.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_blkcntnr.py:14: in from .unitutil.cxml import element, xml tests/unitutil/cxml.py:11: in from pyparsing import ( E ModuleNotFoundError: No module named 'pyparsing' ___ ERROR collecting tests/test_document.py ImportError while importing test module '/tmp/autopkgtest-lxc.fuv79e8l/downtmp/build.YjC/src/tests/test_document.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_document.py:23: in from .unitutil.cxml import element, xml tests/unitutil/cxml.py:11: in from pyparsing import ( E ModuleNotFoundError: No module named 'pyparsing' OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-docx Source-Version: 0.8.11+dfsg1-5 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of python-docx, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated python-docx 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: Sun, 02 Apr 2023 22:22:08 +0200 Source: python-docx Architecture: source Version: 0.8.11+dfsg1-5 Distribution: unstable Urgency: high Maintainer: Debian Python Team Changed-By: Bastian Germann Closes: 1033850 Changes: python-docx (0.8.11+dfsg1-5) unstable; urgency=high . * Team upload. * autopkgtest depends on pyparsing. (Closes: #1033850) Checksums-Sha1: 2a1f80ffdf5871f6da92d8fd673fe74e6639f88b 2213 python-docx_0.8.11+dfsg1-5.dsc efb83f761dca9fd7c7fac315d99f0693111c3b83 6836 python-docx_0.8.11+dfsg1-5.debian.tar.xz 160673e905e41e8529780e85751e9336a38547f1 6094 python-docx_0.8.11+dfsg1-5_source.buildinfo Checksums-Sha256: d70ec0a69bdb3185c8f0e550a70fb0e75e771d45049da5ebaa4ca3800378370c 2213 python-docx_0.8.11+dfsg1-5.dsc c474f27f147e5617f245f384fdb63afe2ab2c0297dccc24eff89c56fd9017d9a 6836 python-docx_0.8.11+dfsg1-5.debian.tar.xz b6bba5661635ce569b6bf69b7fb1e4511ba17c7d5113975b2b15a9753e486e9a 6094
Processed: Bug#1033850 marked as pending in python-docx
Processing control commands: > tag -1 pending Bug #1033850 [src:python-docx] python-docx: autopkgtest regression: No module named 'pyparsing' Added tag(s) pending. -- 1033850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033850: marked as pending in python-docx
Control: tag -1 pending Hello, Bug #1033850 in python-docx 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/python-docx/-/commit/ac5dc59abfe443dc89b93879698b8d13d58ec8e9 autopkgtest depends on pyparsing (Closes: #1033850) (this message was generated automatically) -- Greetings https://bugs.debian.org/1033850
Processed: Re: Bug#1033845: u-boot fails to boot on pinebook pro if installed on internal emmc
Processing control commands: > severity 1033845 important Bug #1033845 [u-boot-rockchip] u-boot fails to boot on pinebook pro if installed on internal emmc Severity set to 'important' from 'serious' -- 1033845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033845: u-boot fails to boot on pinebook pro if installed on internal emmc
Control: severity 1033845 important Given that this only affects a single platform, and there are other tested working boot options for this platform, I am downgrading the severity to important. On 2023-04-02, Wolf wrote: > If the u-boot is installed on the internal emmc then u-boot is failing as > follows: > U-Boot SPL 2023.01+dfsg-2 (Jan 18 2023 - 01:57:16 +) > Trying to boot from MMC1 > mmc fail to send stop cmd > mmc_load_image_raw_sector: mmc block read error > Trying to boot from MMC1 > mmc_load_image_raw_sector: mmc block read error > Trying to boot from SPI > Trying to boot from MMC2 > Card did not respond to voltage select! : -110 > spl: mmc init failed with error: -95 > SPL: failed to boot from all boot devices > ### ERROR ### Please RESET the board ### So far I have only ever tested booting from microSD... Did this work on previous versions? Does it work on the version in experimental (currently 2023.04~rc5*)? > The following patch in the configuration will fix that: > pinebook-pro-rk3399_defconfig: > --- pinebook-pro-rk3399_defconfig 2023-03-22 11:09:33.987508968 +0100 > +++ pinebook-pro-rk3399_defconfig 2023-03-22 12:56:41.773648426 +0100 > @@ -32,6 +32,7 @@ CONFIG_SPL_BSS_MAX_SIZE=0x2000 > CONFIG_SPL_STACK=0x40 > CONFIG_SPL_STACK_R=y > CONFIG_SPL_STACK_R_MALLOC_SIMPLE_LEN=0x1 > +CONFIG_SPL_MTD_SUPPORT=y > CONFIG_SPL_SPI_LOAD=y > CONFIG_TPL=y > CONFIG_CMD_BOOTZ=y > @@ -56,6 +57,8 @@ CONFIG_LED=y > CONFIG_LED_GPIO=y > CONFIG_MISC=y > CONFIG_ROCKCHIP_EFUSE=y > +CONFIG_MMC_HS200_SUPPORT=y > +CONFIG_SPL_MMC_HS200_SUPPORT=y > CONFIG_MMC_DW=y > CONFIG_MMC_DW_ROCKCHIP=y > CONFIG_MMC_SDHCI=y Would you consider submitting a patch upstream? live well, vagrant signature.asc Description: PGP signature
Bug#1033857: ruby-chromedriver-helper: autopkgtest regression: cannot load such file -- zip (LoadError)
Source: ruby-chromedriver-helper
Version: 2.1.0-7
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, it fails since January
2022. Can you please investigate the situation and fix it? I copied some
of the output at the bottom of this report.
The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing. [Release Team member hat on] Because
we're currently in the hard freeze for bookworm, I have marked this bug
as bookworm-ignore. Targeted fixes are still welcome.
More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html
https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-chromedriver-helper/32126583/log.gz
8<8<8<-
group :test do
gem "chromedriver-helper"
end
8<8<8<-
+ ruby -rbundler -e Bundler.require("test"); puts
Selenium::WebDriver::Chrome.driver_path
[DEPRECATED] This Gemfile does not include an explicit global source.
Not using an explicit global source may result in a different lockfile
being generated depending on the gems you have installed locally before
bundler is run. Instead, define a global source in your Gemfile like
this: source "https://rubygems.org;.
Resolving dependencies...
/usr/lib/ruby/vendor_ruby/selenium/webdriver/common/zipper.rb:20:in
`require': cannot load such file -- zip (LoadError)
from
/usr/lib/ruby/vendor_ruby/selenium/webdriver/common/zipper.rb:20:in
`'
from /usr/lib/ruby/vendor_ruby/selenium/webdriver/common.rb:30:in
`require'
from /usr/lib/ruby/vendor_ruby/selenium/webdriver/common.rb:30:in `(required)>'
from /usr/lib/ruby/vendor_ruby/selenium/webdriver.rb:29:in `require'
from /usr/lib/ruby/vendor_ruby/selenium/webdriver.rb:29:in `(required)>'
from /usr/lib/ruby/vendor_ruby/selenium-webdriver.rb:20:in `require'
from /usr/lib/ruby/vendor_ruby/selenium-webdriver.rb:20:in `(required)>'
from
/usr/share/rubygems-integration/all/gems/chromedriver-helper-2.1.0/lib/chromedriver-helper.rb:2:in
`require'
from
/usr/share/rubygems-integration/all/gems/chromedriver-helper-2.1.0/lib/chromedriver-helper.rb:2:in
`'
from
/usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/runtime.rb:60:in
`require'
from
/usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/runtime.rb:60:in
`block (2 levels) in require'
from
/usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/runtime.rb:55:in
`each'
from
/usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/runtime.rb:55:in
`block in require'
from
/usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/runtime.rb:44:in
`each'
from
/usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/runtime.rb:44:in
`require'
from
/usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler.rb:187:in
`require'
from -e:1:in `'
OpenPGP_signature
Description: OpenPGP digital signature
Processed: ruby-chromedriver-helper: autopkgtest regression: cannot load such file -- zip (LoadError)
Processing control commands: > tags -1 bookworm-ignore Bug #1033857 [src:ruby-chromedriver-helper] ruby-chromedriver-helper: autopkgtest regression: cannot load such file -- zip (LoadError) Added tag(s) bookworm-ignore. -- 1033857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re 1025045: r-bioc-structuralvariantannotation: Test failures in autopkgtest
Processing control commands: > severity -1 serious Bug #1025045 [src:r-bioc-structuralvariantannotation] r-bioc-structuralvariantannotation: Test failures in autopkgtest Severity set to 'serious' from 'normal' > tags -1 bookworm-ignore Bug #1025045 [src:r-bioc-structuralvariantannotation] r-bioc-structuralvariantannotation: Test failures in autopkgtest Added tag(s) bookworm-ignore. -- 1025045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: r-bioc-rwikipathways: autopkgtest regression: get WP2338 Xrefs
Processing control commands: > tags -1 bookworm-ignore Bug #1033855 [src:r-bioc-rwikipathways] r-bioc-rwikipathways: autopkgtest regression: get WP2338 Xrefs Added tag(s) bookworm-ignore. -- 1033855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033855: r-bioc-rwikipathways: autopkgtest regression: get WP2338 Xrefs
Source: r-bioc-rwikipathways
Version: 1.18.0+dfsg-1
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, it fails since February
2023. Can you please investigate the situation and fix it? I copied some
of the output at the bottom of this report.
The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing. [Release Team member hat on] Because
we're currently in the hard freeze for bookworm, I have marked this bug
as bookworm-ignore. Targeted fixes are still welcome.
More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-bioc-rwikipathways/32247692/log.gz
══ Failed tests
── Failure ('test-getXrefList.R:6'): get WP2338 Xrefs
──
"Q9UPY3" %in% xrefs is not TRUE
`actual`: FALSE
`expected`: TRUE
── Failure ('test-getXrefList.R:11'): get WP2338 (again)
───
"Q9UPY3" %in% xrefs is not TRUE
`actual`: FALSE
`expected`: TRUE
[ FAIL 2 | WARN 0 | SKIP 0 | PASS 25 ]
OpenPGP_signature
Description: OpenPGP digital signature
Processed: r-bioc-rhdf5lib: autopkgtest regression: Expected '1.10.7', got '1.10.8'
Processing control commands: > tags -1 bookworm-ignore Bug #1033854 [src:r-bioc-rhdf5lib] r-bioc-rhdf5lib: autopkgtest regression: Expected '1.10.7', got '1.10.8' Added tag(s) bookworm-ignore. -- 1033854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033854: r-bioc-rhdf5lib: autopkgtest regression: Expected '1.10.7', got '1.10.8'
Source: r-bioc-rhdf5lib Version: 1.20.0+dfsg-1 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails since around October 2022. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-bioc-rhdf5lib/32247729/log.gz - FAILED[data]: test_library_version.R<3--3> call| expect_identical(libver, "1.10.7") diff| Expected '1.10.7', got '1.10.8' Error: 1 out of 10 tests failed OpenPGP_signature Description: OpenPGP digital signature
Bug#1033853: r-bioc-megadepth: autopkgtest regression: different output
Source: r-bioc-megadepth
Version: 1.8.0+ds-1
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, it fails in testing
since March 2023. Can you please investigate the situation and fix it? I
copied some of the output at the bottom of this report.
The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing. [Release Team member hat on] Because
we're currently in the hard freeze for bookworm, I have marked this bug
as bookworm-ignore. Targeted fixes are still welcome.
More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-bioc-megadepth/32560589/log.gz
══ Failed tests
── Failure ('test-megadepth_main_tests.R:74'): test bigwig2mean on
remote bw ───
readLines(file.path(tempdir(), "bw2.remote.mean.annotation.tsv"))
(`actual`) not equal to
readLines("https://raw.githubusercontent.com/ChristopherWilks/megadepth/master/tests/testbw2.bed.mean;)
(`expected`).
actual | expected
- "chr10\t0\t10\t0.00" [1]
- "chr10\t8756697\t8756762\t15.85" [2]
- "chr10\t4359156\t4359188\t3.00"[3]
- "GL000219.1\t168500\t168620\t1.26" [4]
[ FAIL 1 | WARN 1 | SKIP 0 | PASS 129 ]
OpenPGP_signature
Description: OpenPGP digital signature
Processed: r-bioc-megadepth: autopkgtest regression: different output
Processing control commands: > tags -1 bookworm-ignore Bug #1033853 [src:r-bioc-megadepth] r-bioc-megadepth: autopkgtest regression: different output Added tag(s) bookworm-ignore. -- 1033853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033852: racket-mode: autopkgtest regression: Process *Racket REPL* connection broken by remote peer
Source: racket-mode
Version: 20210916git0-2
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, it fails since December
2022 in testing. Can you please investigate the situation and fix it? I
copied some of the output at the bottom of this report.
The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing. [Release Team member hat on] Because
we're currently in the hard freeze for bookworm, I have marked this bug
as bookworm-ignore. Targeted fixes are still welcome.
More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html
https://ci.debian.net/data/autopkgtest/testing/amd64/r/racket-mode/32133920/log.gz
racket-tests/repl
Indenting region...
Indenting region...done
Indenting region...
Indenting region...done
Indenting region...
Indenting region...done
Indenting region...
Indenting region...done
Indenting region...
Indenting region...done
Test racket-tests/repl backtrace:
signal(ert-test-failed (((should (racket-tests/see-back expected)) :
ert-fail(((should (racket-tests/see-back expected)) :form (racket-te
(if (unwind-protect (setq value-37 (apply fn-35 args-36)) (setq form
(let (form-description-39) (if (unwind-protect (setq value-37 (apply
(let ((value-37 'ert-form-evaluation-aborted-38)) (let (form-descrip
(let* ((fn-35 #'racket-tests/see-back) (args-36 (condition-case err
(closure ((expected . "(cond [(values 1) #t] [else #f])\n#t\n> ") (t
mapc((closure ((expected . "(cond [(values 1) #t] [else #f])\n#t\n>
(let ((typing "[cond [[values 1] #t] [else #f]]") (expected "(cond [
(closure (t) nil (let* ((fn-0 #'racket-tests/see-back-rx) (args-1 (c
racket--call-with-repl-buffer((closure (t) nil (let* ((fn-0 #'racket
(closure (t) nil (racket-repl) (racket-tests/call-until-true #'(lamb
funcall((closure (t) nil (racket-repl) (racket-tests/call-until-true
(unwind-protect (funcall thunk) (racket-stop-back-end))
(let ((racket-command-timeout racket-tests/timeout)) (unwind-protect
racket-tests/call-with-back-end-settings((closure (t) nil (racket-re
(let ((lexical-binding t)) (message "racket-tests/repl") (racket-tes
(closure (t) nil (let ((lexical-binding t)) (message "racket-tests/r
ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
ert-run-test(#s(ert-test :name racket-tests/repl :documentation "Sta
ert-run-or-rerun-test(#s(ert--stats :selector t :tests ... :test-map
ert-run-tests(t #f(compiled-function (event-type event-args) #
ert-run-tests-batch(nil)
ert-run-tests-batch-and-exit()
command-line-1(("-l" "package" "--eval" "(add-to-list 'package-direc
command-line()
normal-top-level()
Test racket-tests/repl condition:
(ert-test-failed
((should
(racket-tests/see-back expected))
:form
(racket-tests/see-back "(cond [(values 1) #t] [else #f])\n#t\n> ")
:value nil :explanation
(actual . "; \n; Welcome to Racket v8.7 [cs].\n; \n>
current-output-port\n#\n> (if 1\n
2\n 3)\n2\n> (cond [(values 1) #t] [else #f])\n#t\n> (cond [(values
1) #t] [else #f])\n#t\n> (cond [(values 1) #t] [else #f])\n")))
FAILED 10/12 racket-tests/repl (15.518214 sec)
racket-tests/run
run: current-repl-msg-chan was #f; current-session-id=#f
Test racket-tests/run backtrace:
signal(ert-test-failed (((should (racket-tests/see-back (concat "\n"
ert-fail(((should (racket-tests/see-back (concat "\n" name "> "))) :
(if (unwind-protect (setq value-72 (apply fn-70 args-71)) (setq form
(let (form-description-74) (if (unwind-protect (setq value-72 (apply
(let ((value-72 'ert-form-evaluation-aborted-73)) (let (form-descrip
(let* ((fn-70 #'racket-tests/see-back) (args-71 (condition-case err
(closure ((code . "#lang racket/base\n(define foobar 42)\nfoobar\n")
racket--call-with-repl-buffer((closure ((code . "#lang racket/base\n
(let* ((path (make-temp-file "test" nil ".rkt")) (name (file-name-no
(closure (t) nil (let* ((path (make-temp-file "test" nil ".rkt")) (n
funcall((closure (t) nil (let* ((path (make-temp-file "test" nil ".r
(unwind-protect (funcall thunk) (racket-stop-back-end))
(let ((racket-command-timeout racket-tests/timeout)) (unwind-protect
racket-tests/call-with-back-end-settings((closure (t) nil (let* ((pa
(let ((lexical-binding t)) (message "racket-tests/run") (racket-test
(closure (t) nil (let ((lexical-binding t)) (message "racket-tests/r
ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
ert-run-test(#s(ert-test :name racket-tests/run :documentation "Star
ert-run-or-rerun-test(#s(ert--stats :selector t :tests ... :test-map
ert-run-tests(t #f(compiled-function (event-type event-args) #
Processed: racket-mode: autopkgtest regression: Process *Racket REPL* connection broken by remote peer
Processing control commands: > tags -1 bookworm-ignore Bug #1033852 [src:racket-mode] racket-mode: autopkgtest regression: Process *Racket REPL* connection broken by remote peer Added tag(s) bookworm-ignore. -- 1033852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033851: python-pyepsg: autopkgtest regression: xml.etree.ElementTree.ParseError: not well-formed (invalid token)
Source: python-pyepsg
Version: 0.4.0-1
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, it fails since about
August 2022. Can you please investigate the situation and fix it? I
copied some of the output at the bottom of this report.
The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing. [Release Team member hat on] Because
we're currently in the hard freeze for bookworm, I have marked this bug
as bookworm-ignore. Targeted fixes are still welcome.
More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-pyepsg/32471275/log.gz
=== FAILURES
===
___ [doctest] pyepsg.CRS.as_esri_wkt
___
129
130 Return the ESRI WKT string which corresponds to the CRS.
131
132 For example::
133
134 >>> print(get(27700).as_esri_wkt()) # doctest: +ELLIPSIS
UNEXPECTED EXCEPTION: ParseError('not well-formed (invalid token): line
1, column 0')
Traceback (most recent call last):
File "/usr/lib/python3.11/doctest.py", line 1351, in __run
exec(compile(example.source, filename, "single",
File "", line 1, in
File "/usr/lib/python3/dist-packages/pyepsg.py", line 288, in get
root = ET.fromstring(xml)
^^
File "/usr/lib/python3.11/xml/etree/ElementTree.py", line 1338, in XML
parser.feed(text)
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line
1, column 0
/usr/lib/python3/dist-packages/pyepsg.py:134: UnexpectedException
OpenPGP_signature
Description: OpenPGP digital signature
Processed: python-pyepsg: autopkgtest regression: xml.etree.ElementTree.ParseError: not well-formed (invalid token)
Processing control commands: > tags -1 bookworm-ignore Bug #1033851 [src:python-pyepsg] python-pyepsg: autopkgtest regression: xml.etree.ElementTree.ParseError: not well-formed (invalid token) Added tag(s) bookworm-ignore. -- 1033851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033850: python-docx: autopkgtest regression: No module named 'pyparsing'
Source: python-docx Version: 0.8.11+dfsg1-4 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails since January 2023. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-docx/32174602/log.gz ERRORS ___ ERROR collecting tests/test_blkcntnr.py ImportError while importing test module '/tmp/autopkgtest-lxc.fuv79e8l/downtmp/build.YjC/src/tests/test_blkcntnr.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_blkcntnr.py:14: in from .unitutil.cxml import element, xml tests/unitutil/cxml.py:11: in from pyparsing import ( E ModuleNotFoundError: No module named 'pyparsing' ___ ERROR collecting tests/test_document.py ImportError while importing test module '/tmp/autopkgtest-lxc.fuv79e8l/downtmp/build.YjC/src/tests/test_document.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_document.py:23: in from .unitutil.cxml import element, xml tests/unitutil/cxml.py:11: in from pyparsing import ( E ModuleNotFoundError: No module named 'pyparsing' OpenPGP_signature Description: OpenPGP digital signature
Processed: python-docx: autopkgtest regression: No module named 'pyparsing'
Processing control commands: > tags -1 bookworm-ignore Bug #1033850 [src:python-docx] python-docx: autopkgtest regression: No module named 'pyparsing' Added tag(s) bookworm-ignore. -- 1033850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033824: marked as done (passwordsafe: autopkgtest regression: test dependencies transitioned)
Your message dated Sun, 02 Apr 2023 19:19:08 + with message-id and subject line Bug#1033824: fixed in passwordsafe 1.16.0+dfsg-2 has caused the Debian Bug report #1033824, regarding passwordsafe: autopkgtest regression: test dependencies transitioned 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.) -- 1033824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: passwordsafe Version: 1.16.0+dfsg-1 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it started to fail when we finished the wcwidgets3.0 -> wxwidgets3.2 transition in January 2023. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/p/passwordsafe/32250351/log.gz E: Unable to locate package libwxgtk3.0-gtk3-dev E: Unable to locate package wx3.0-headers OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: passwordsafe Source-Version: 1.16.0+dfsg-2 Done: William Blough We believe that the bug you reported is fixed in the latest version of passwordsafe, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. William Blough (supplier of updated passwordsafe 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: Sun, 02 Apr 2023 14:27:03 -0400 Source: passwordsafe Architecture: source Version: 1.16.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: William Blough Changed-By: William Blough Closes: 1033824 Changes: passwordsafe (1.16.0+dfsg-2) unstable; urgency=medium . * autopkgtest fixes: * Test binaries used by autopkgtest are now in subdir path named with host triplet * Update autopkgtest dependencies to use wx3.2 (Closes: 1033824) Checksums-Sha1: ebf332d19377cb12e7371ce1825eb1981570ff46 2542 passwordsafe_1.16.0+dfsg-2.dsc 0195a7783d01d3a79eeb01e32c0e718cd305ce1f 17928 passwordsafe_1.16.0+dfsg-2.debian.tar.xz d1c3bd35a1d22cae4533bd347f410e53d031f017 12828 passwordsafe_1.16.0+dfsg-2_amd64.buildinfo Checksums-Sha256: fb7a69c140d4f5f9742aa2b11975240c081af8cedd585bf2c513ef0d7d3d3751 2542 passwordsafe_1.16.0+dfsg-2.dsc e53814f3381d65c242677f137859020b6433f24db6f07eb2276c26510834afb2 17928 passwordsafe_1.16.0+dfsg-2.debian.tar.xz 1721832e3f8e4cfb16025c03a3073f776d9cf1df414ec38cb4029b96db063902 12828 passwordsafe_1.16.0+dfsg-2_amd64.buildinfo Files: 4e55737a7954861beeb6771c25c9d865 2542 utils optional passwordsafe_1.16.0+dfsg-2.dsc ce521563b095f3d64d7c7d677663c0f5 17928 utils optional passwordsafe_1.16.0+dfsg-2.debian.tar.xz 48481b4b26a79461b2f90e7c240a255a 12828 utils optional passwordsafe_1.16.0+dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKnBAEBCACRFiEEJXjSPd76bZ5rVv2gNeEe5JHS9UwFAmQpz59fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDI1 NzhEMjNEREVGQTZEOUU2QjU2RkRBMDM1RTExRUU0OTFEMkY1NEMTHGJibG91Z2hA ZGViaWFuLm9yZwAKCRA14R7kkdL1TMToD/9lKum9pOMCnlbe+Wk7SzuLUOkcA3cK f7B0AaEGfN4F1hW/pN4XrfD+RX7maZeBC74wFwJK6MkY6iLcJfLfcpfVMligtc0C jeb2tX0XoAQVVdUeiIhj4KzlQMoMnjGuttWcJkcuNsUDR0aNp4sSLQSa11G101s7 NSoNjoWHiAR+QCT/sQoOhPuwQvxQj+wYgs8rmfxUzSxxtx1ekEF2RYduipZSW9Fe SxpTjEaWtlcdcNcbCSH6hKB8xCjl7IHBgXTnEcNzyMQk/dJJ8gDtdF941+z9K7lt Qtv+OLq6F7aoqFaxzSAvast6bVy09bLbIGHQ6zRwX8yhAlDM57751oIioRrndOlP 2slW2RNkghh8TzL1kHjHYHvolPVsSlLUatPY8KDpRgBnS0esDzYhe0ACnMgbgJh8
Bug#1033806: marked as done (libntru: autopkgtest regression: undefined reference)
Your message dated Sun, 02 Apr 2023 19:18:52 + with message-id and subject line Bug#1033806: fixed in libntru 0.5-3 has caused the Debian Bug report #1033806, regarding libntru: autopkgtest regression: undefined reference 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.) -- 1033806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libntru Version: 0.5-2 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] I'm slightly worried that this test failure points at a real problem with the library, but because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. Please remove the bookworm-ignore tag if the library is broken as it is. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/libn/libntru/32095885/log.gz autopkgtest [16:23:12]: test benchmark: [--- /usr/bin/ld: /tmp/cc3rAheI.o: warning: relocation against `EES761EP1' in read-only section `.text.startup' /usr/bin/ld: /tmp/cc3rAheI.o: in function `main': bench.c:(.text.startup+0x39): undefined reference to `ntru_rand_default_init' /usr/bin/ld: bench.c:(.text.startup+0x40): undefined reference to `ntru_rand_default_generate' /usr/bin/ld: bench.c:(.text.startup+0x54): undefined reference to `EES401EP1' /usr/bin/ld: bench.c:(.text.startup+0x5c): undefined reference to `EES401EP1' /usr/bin/ld: bench.c:(.text.startup+0x63): undefined reference to `EES401EP1' /usr/bin/ld: bench.c:(.text.startup+0x6b): undefined reference to `EES449EP1' /usr/bin/ld: bench.c:(.text.startup+0x7a): undefined reference to `EES401EP1' /usr/bin/ld: bench.c:(.text.startup+0x89): undefined reference to `EES401EP1' /usr/bin/ld: bench.c:(.text.startup+0x98): undefined reference to `EES449EP1' /usr/bin/ld: bench.c:(.text.startup+0xa7): undefined reference to `EES449EP1' /usr/bin/ld: bench.c:(.text.startup+0xb5): undefined reference to `EES449EP1' /usr/bin/ld: bench.c:(.text.startup+0xc4): undefined reference to `EES449EP1' /usr/bin/ld: bench.c:(.text.startup+0xd3): undefined reference to `EES677EP1' /usr/bin/ld: bench.c:(.text.startup+0xe2): undefined reference to `EES677EP1' /usr/bin/ld: bench.c:(.text.startup+0xf0): undefined reference to `EES677EP1' /usr/bin/ld: bench.c:(.text.startup+0xff): undefined reference to `EES677EP1' /usr/bin/ld: bench.c:(.text.startup+0x10e): undefined reference to `EES677EP1' /usr/bin/ld: bench.c:(.text.startup+0x11d): undefined reference to `EES1087EP2' /usr/bin/ld: bench.c:(.text.startup+0x141): undefined reference to `EES1087EP2' /usr/bin/ld: bench.c:(.text.startup+0x149): undefined reference to `EES1087EP2' /usr/bin/ld: bench.c:(.text.startup+0x151): undefined reference to `EES1087EP2' /usr/bin/ld: bench.c:(.text.startup+0x158): undefined reference to `EES1087EP2' /usr/bin/ld: bench.c:(.text.startup+0x167): undefined reference to `EES541EP1' /usr/bin/ld: bench.c:(.text.startup+0x176): undefined reference to `EES541EP1' /usr/bin/ld: bench.c:(.text.startup+0x185): undefined reference to `EES541EP1' /usr/bin/ld: bench.c:(.text.startup+0x194): undefined reference to `EES541EP1' /usr/bin/ld: bench.c:(.text.startup+0x1a2): undefined reference to `EES541EP1' /usr/bin/ld: bench.c:(.text.startup+0x1b1): undefined reference to `EES613EP1' /usr/bin/ld: bench.c:(.text.startup+0x1c0): undefined reference to `EES613EP1' /usr/bin/ld: bench.c:(.text.startup+0x1cf): undefined reference to `EES613EP1' /usr/bin/ld: bench.c:(.text.startup+0x1dd): undefined reference to `EES613EP1' /usr/bin/ld: bench.c:(.text.startup+0x1ec): undefined reference to `EES613EP1' /usr/bin/ld: bench.c:(.text.startup+0x1fb): undefined reference to `EES887EP1' /usr/bin/ld: bench.c:(.text.startup+0x20a): undefined reference to `EES887EP1' /usr/bin/ld: bench.c:(.text.startup+0x22e): undefined reference to `EES887EP1' /usr/bin/ld: bench.c:(.text.startup+0x235): undefined
Bug#1033806: libntru: autopkgtest regression: undefined reference
Hi Paul, On 02-04-2023 19:35, Ying-Chun Liu (PaulLiu) wrote: I fixed this bug. The debdiff is as attachment. It is quite easy to fix. It is not related to the library but just the test itself. Should I upload it? Sounds like a plan. As libntru isn't a key package, a passing autopkgtest will enable the fix to migrate. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1033845: u-boot fails to boot on pinebook pro if installed on internal emmc
Package: u-boot-rockchip Version: 2023.01+dfsg-2 Severity: serious Tags: patch X-Debbugs-Cc: lxde...@zirdeon.com If the u-boot is installed on the internal emmc then u-boot is failing as follows: U-Boot SPL 2023.01+dfsg-2 (Jan 18 2023 - 01:57:16 +) Trying to boot from MMC1 mmc fail to send stop cmd mmc_load_image_raw_sector: mmc block read error Trying to boot from MMC1 mmc_load_image_raw_sector: mmc block read error Trying to boot from SPI Trying to boot from MMC2 Card did not respond to voltage select! : -110 spl: mmc init failed with error: -95 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### The following patch in the configuration will fix that: pinebook-pro-rk3399_defconfig: --- pinebook-pro-rk3399_defconfig 2023-03-22 11:09:33.987508968 +0100 +++ pinebook-pro-rk3399_defconfig 2023-03-22 12:56:41.773648426 +0100 @@ -32,6 +32,7 @@ CONFIG_SPL_BSS_MAX_SIZE=0x2000 CONFIG_SPL_STACK=0x40 CONFIG_SPL_STACK_R=y CONFIG_SPL_STACK_R_MALLOC_SIMPLE_LEN=0x1 +CONFIG_SPL_MTD_SUPPORT=y CONFIG_SPL_SPI_LOAD=y CONFIG_TPL=y CONFIG_CMD_BOOTZ=y @@ -56,6 +57,8 @@ CONFIG_LED=y CONFIG_LED_GPIO=y CONFIG_MISC=y CONFIG_ROCKCHIP_EFUSE=y +CONFIG_MMC_HS200_SUPPORT=y +CONFIG_SPL_MMC_HS200_SUPPORT=y CONFIG_MMC_DW=y CONFIG_MMC_DW_ROCKCHIP=y CONFIG_MMC_SDHCI=y -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 6.1.0-6-arm64 (SMP w/6 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled u-boot-rockchip depends on no packages. Versions of packages u-boot-rockchip recommends: ii python3 3.11.2-1 ii u-boot-tools 2023.01+dfsg-2 Versions of packages u-boot-rockchip suggests: ii arm-trusted-firmware 2.8.0+dfsg-1 -- no debconf information
Bug#1033806: libntru: autopkgtest regression: undefined reference
Hi Paul I fixed this bug. The debdiff is as attachment. It is quite easy to fix. It is not related to the library but just the test itself. Should I upload it? Yours, Paul On 2023/4/2 04:04, Paul Gevers wrote: Source: libntru Version: 0.5-2 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] I'm slightly worried that this test failure points at a real problem with the library, but because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. Please remove the bookworm-ignore tag if the library is broken as it is. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/libn/libntru/32095885/log.gz autopkgtest [16:23:12]: test benchmark: [--- /usr/bin/ld: /tmp/cc3rAheI.o: warning: relocation against `EES761EP1' in read-only section `.text.startup' /usr/bin/ld: /tmp/cc3rAheI.o: in function `main': bench.c:(.text.startup+0x39): undefined reference to `ntru_rand_default_init' /usr/bin/ld: bench.c:(.text.startup+0x40): undefined reference to `ntru_rand_default_generate' /usr/bin/ld: bench.c:(.text.startup+0x54): undefined reference to `EES401EP1' /usr/bin/ld: bench.c:(.text.startup+0x5c): undefined reference to `EES401EP1' /usr/bin/ld: bench.c:(.text.startup+0x63): undefined reference to `EES401EP1' /usr/bin/ld: bench.c:(.text.startup+0x6b): undefined reference to `EES449EP1' /usr/bin/ld: bench.c:(.text.startup+0x7a): undefined reference to `EES401EP1' /usr/bin/ld: bench.c:(.text.startup+0x89): undefined reference to `EES401EP1' /usr/bin/ld: bench.c:(.text.startup+0x98): undefined reference to `EES449EP1' /usr/bin/ld: bench.c:(.text.startup+0xa7): undefined reference to `EES449EP1' /usr/bin/ld: bench.c:(.text.startup+0xb5): undefined reference to `EES449EP1' /usr/bin/ld: bench.c:(.text.startup+0xc4): undefined reference to `EES449EP1' /usr/bin/ld: bench.c:(.text.startup+0xd3): undefined reference to `EES677EP1' /usr/bin/ld: bench.c:(.text.startup+0xe2): undefined reference to `EES677EP1' /usr/bin/ld: bench.c:(.text.startup+0xf0): undefined reference to `EES677EP1' /usr/bin/ld: bench.c:(.text.startup+0xff): undefined reference to `EES677EP1' /usr/bin/ld: bench.c:(.text.startup+0x10e): undefined reference to `EES677EP1' /usr/bin/ld: bench.c:(.text.startup+0x11d): undefined reference to `EES1087EP2' /usr/bin/ld: bench.c:(.text.startup+0x141): undefined reference to `EES1087EP2' /usr/bin/ld: bench.c:(.text.startup+0x149): undefined reference to `EES1087EP2' /usr/bin/ld: bench.c:(.text.startup+0x151): undefined reference to `EES1087EP2' /usr/bin/ld: bench.c:(.text.startup+0x158): undefined reference to `EES1087EP2' /usr/bin/ld: bench.c:(.text.startup+0x167): undefined reference to `EES541EP1' /usr/bin/ld: bench.c:(.text.startup+0x176): undefined reference to `EES541EP1' /usr/bin/ld: bench.c:(.text.startup+0x185): undefined reference to `EES541EP1' /usr/bin/ld: bench.c:(.text.startup+0x194): undefined reference to `EES541EP1' /usr/bin/ld: bench.c:(.text.startup+0x1a2): undefined reference to `EES541EP1' /usr/bin/ld: bench.c:(.text.startup+0x1b1): undefined reference to `EES613EP1' /usr/bin/ld: bench.c:(.text.startup+0x1c0): undefined reference to `EES613EP1' /usr/bin/ld: bench.c:(.text.startup+0x1cf): undefined reference to `EES613EP1' /usr/bin/ld: bench.c:(.text.startup+0x1dd): undefined reference to `EES613EP1' /usr/bin/ld: bench.c:(.text.startup+0x1ec): undefined reference to `EES613EP1' /usr/bin/ld: bench.c:(.text.startup+0x1fb): undefined reference to `EES887EP1' /usr/bin/ld: bench.c:(.text.startup+0x20a): undefined reference to `EES887EP1' /usr/bin/ld: bench.c:(.text.startup+0x22e): undefined reference to `EES887EP1' /usr/bin/ld: bench.c:(.text.startup+0x235): undefined reference to `EES887EP1' /usr/bin/ld: bench.c:(.text.startup+0x23d): undefined reference to `EES887EP1' /usr/bin/ld: bench.c:(.text.startup+0x245): undefined reference to `EES1171EP1' /usr/bin/ld: bench.c:(.text.startup+0x24d): undefined reference to `EES1171EP1' /usr/bin/ld: bench.c:(.text.startup+0x255): undefined reference to `EES1171EP1' /usr/bin/ld: bench.c:(.text.startup+0x264): undefined reference to `EES1171EP1' /usr/bin/ld: bench.c:(.text.startup+0x26b): undefined reference to `EES1171EP1' /usr/bin/ld: bench.c:(.text.startup+0x27a): undefined reference to `EES659EP1' /usr/bin/ld:
Processed: found
Processing commands for cont...@bugs.debian.org: > found 1032975 0.11-3 Bug #1032975 [igdiscover] igdiscover -- Broken, unusable package due to incomplete code in the binary package Marked as found in versions igdiscover/0.11-3. > stop Stopping processing here. Please contact me if you need assistance. -- 1032975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1033833: unknown-horizons: Fails to start Couldn't open content/fonts/Unifont.ttf
Processing control commands: > reassign -1 src:unifont Bug #1033833 [unknown-horizons] unknown-horizons: Fails to start Couldn't open content/fonts/Unifont.ttf Bug reassigned from package 'unknown-horizons' to 'src:unifont'. No longer marked as found in versions unknown-horizons/2019.1-5. Ignoring request to alter fixed versions of bug #1033833 to the same values previously set > retitle -1 src:unifont: Dropping of unifont.ttf breaks unknown-horizons Bug #1033833 [src:unifont] unknown-horizons: Fails to start Couldn't open content/fonts/Unifont.ttf Changed Bug title to 'src:unifont: Dropping of unifont.ttf breaks unknown-horizons' from 'unknown-horizons: Fails to start Couldn't open content/fonts/Unifont.ttf'. > found -1 1:15.0.01-1 Bug #1033833 [src:unifont] src:unifont: Dropping of unifont.ttf breaks unknown-horizons Marked as found in versions unifont/1:15.0.01-1. > affects -1 unknown-horizons Bug #1033833 [src:unifont] src:unifont: Dropping of unifont.ttf breaks unknown-horizons Added indication that 1033833 affects unknown-horizons -- 1033833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033833: unknown-horizons: Fails to start Couldn't open content/fonts/Unifont.ttf
Control: reassign -1 src:unifont Control: retitle -1 src:unifont: Dropping of unifont.ttf breaks unknown-horizons Control: found -1 1:15.0.01-1 Control: affects -1 unknown-horizons Hi Hans Joachim, thanks for the report! it seems so that the fonts package unifont dropped unifont.ttf in 1:15.0.01-1: https://salsa.debian.org/fonts-team/unifont/-/commit/94b9698e3809316cd0e942f24f5ecbd517424c98 https://salsa.debian.org/fonts-team/unifont/-/commit/ac9a662b71d20f54d82c666502192302a21aa13e and so broke this package. I'll reassign the bug to src:unifont and ask them to please revert the change. -- tobi On Sun, Apr 02, 2023 at 03:16:47PM +0200, Hans Joachim Desserud wrote: > Package: unknown-horizons > Version: 2019.1-5 > Severity: grave > > Dear Maintainer, > > When attempting to run uknown-horizons it fails with the following error > message: > $ unknown-horizons > Discovered old settings file, auto-upgrading: 1 -> 38 > Traceback (most recent call last): > File "/usr/games/unknown-horizons", line 381, in > main() > File "/usr/games/unknown-horizons", line 122, in main > ret = horizons.main.start(options) > > File "/usr/lib/python3/dist-packages/horizons/main.py", line 171, in start > horizons.globals.fife.init() > File "/usr/lib/python3/dist-packages/horizons/engine/engine.py", line 181, > in init > self._setting.apply() > File "/usr/lib/python3/dist-packages/horizons/engine/settings.py", line > 91, in apply > change_language(language) > File "/usr/lib/python3/dist-packages/horizons/i18n/__init__.py", line 163, > in change_language > horizons.globals.fife.pychan.loadFonts(fontdef) > File "/usr/lib/python3/dist-packages/fife/extensions/pychan/fonts.py", > line 98, in loadFonts > for font in Font.loadFromFile(filename): > ^^^ > File "/usr/lib/python3/dist-packages/fife/extensions/pychan/fonts.py", > line 82, in loadFromFile > fonts.append(Font(font, lambda key, default=None: fontXMLFile.get(font, > key, default))) > ^ > File "/usr/lib/python3/dist-packages/fife/extensions/pychan/fonts.py", > line 52, in __init__ > self.font = get_manager().createFont(self.source, self.size) > > File "/usr/lib/python3/dist-packages/fife/extensions/pychan/internal.py", > line 176, in createFont > return self.hook.create_font(path,size,glyphs) >^^^ > fife.fife.CannotOpenFile: _[CannotOpenFile]_ , File couldn't be opened :: > content/fonts/Unifont.ttf (Couldn't open content/fonts/Unifont.ttf) > > The root problem is a missing font or font format. I tried a simple rebuild > of the package, but it had no effect. Looks like the font path is part of > the source code, so might be more font references with similar issues. > > Also reported in Ubuntu as > https://bugs.launchpad.net/ubuntu/+source/unknown-horizons/+bug/2011358 > > > -- System Information: > Debian Release: 12.0 > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.1.0-7-amd64 (SMP w/3 CPU threads; PREEMPT) > 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 > > Versions of packages unknown-horizons depends on: > ii fonts-unifont 1:15.0.01-2 > ii python3 3.11.2-1 > ii python3-enet0.0~vcs.2022.12.26.git-0.2+b1 > ii python3-fife0.4.2-5+b1 > ii python3-future 0.18.2-6 > ii python3-yaml6.0-3+b2 > > unknown-horizons recommends no packages. > > unknown-horizons suggests no packages. > > -- no debconf information > > -- > mvh / best regards > Hans Joachim Desserud > http://desserud.org > signature.asc Description: PGP signature
Bug#1033732: [PATCH v2] x86/acpi/boot: Do not register processors that cannot be onlined for x2apic
On Sun, Apr 02, 2023 at 03:13:05PM +0200, Guy Durrieu wrote: > Yes it does. Thanks for testing. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette
Bug#1033832: marked as pending in php-db
Control: tag -1 pending Hello, Bug #1033832 in php-db 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/php-team/pear/php-db/-/commit/914a40f85eb535342c3dcd4a193ac25ff6d42315 Add a patch to fix test failures (Closes: #1033832) (this message was generated automatically) -- Greetings https://bugs.debian.org/1033832
Processed: Bug#1033832 marked as pending in php-db
Processing control commands: > tag -1 pending Bug #1033832 [src:php-db] php-db: autopkgtest regression: FAIL DB::DB_Error[DB-1.11.0/tests/db_error.phpt] Ignoring request to alter tags of bug #1033832 to the same tags previously set -- 1033832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 1033832 https://github.com/pear/DB/pull/12 Bug #1033832 [src:php-db] php-db: autopkgtest regression: FAIL DB::DB_Error[DB-1.11.0/tests/db_error.phpt] Set Bug forwarded-to-address to 'https://github.com/pear/DB/pull/12'. > forwarded 1033832 > https://salsa.debian.org/php-team/pear/php-db/-/merge_requests/1 Bug #1033832 [src:php-db] php-db: autopkgtest regression: FAIL DB::DB_Error[DB-1.11.0/tests/db_error.phpt] Changed Bug forwarded-to-address to 'https://salsa.debian.org/php-team/pear/php-db/-/merge_requests/1' from 'https://github.com/pear/DB/pull/12'. > tags 1033832 + pending Bug #1033832 [src:php-db] php-db: autopkgtest regression: FAIL DB::DB_Error[DB-1.11.0/tests/db_error.phpt] Added tag(s) pending. > stop Stopping processing here. Please contact me if you need assistance. -- 1033832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033827: Fix DEP8 test failures
The following salsa MP should fix the issue: https://salsa.debian.org/php-team/pear/php-dapphp-radius/-/merge_requests/4 -- Athos Ribeiro
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forcemerge 1030415 1033834 Bug #1030415 [src:php-log] php-log: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_test] Error 1 Bug #1030415 [src:php-log] php-log: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_test] Error 1 Added tag(s) bookworm-ignore. Bug #1033834 [src:php-log] php-log: autopkgtest regression: extract-zend2.2.phpt Owner recorded as William Desportes . Added tag(s) pending, ftbfs, bookworm, and sid. Merged 1030415 1033834 > stop Stopping processing here. Please contact me if you need assistance. -- 1030415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030415 1033834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033834 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033732: [PATCH v2] x86/acpi/boot: Do not register processors that cannot be onlined for x2apic
Hi Guy, On Sun, Apr 02, 2023 at 03:13:05PM +0200, Guy Durrieu wrote: > Le 02/04/2023 à 12:57, Borislav Petkov a écrit : > > > On April 2, 2023 12:41:46 PM GMT+02:00, Guy Durrieu > > wrote: > > > My system worked fine with kernel 6.1.15, but stopped booting after > > > upgrading to 6.1.20 and resulted in a kernel panic: > > Does this fix it: > > > > https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=x86/urgent > > > > Thx. > > > Yes it does. Thanks, the commit will be part of the next upload: https://salsa.debian.org/kernel-team/linux/-/merge_requests/692 Thanks for your time put in debugging the issue. Regards, Salvatore
Processed (with 1 error): merge with 1030415
Processing commands for cont...@bugs.debian.org: > forwarded 1033834 > https://salsa.debian.org/php-team/pear/php-log/-/commit/fb958bf2f197defd6abb780cccf10490938082e5 Bug #1033834 [src:php-log] php-log: autopkgtest regression: extract-zend2.2.phpt Set Bug forwarded-to-address to 'https://salsa.debian.org/php-team/pear/php-log/-/commit/fb958bf2f197defd6abb780cccf10490938082e5'. > merge 1030415 1033834 Bug #1030415 [src:php-log] php-log: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_test] Error 1 Unable to merge bugs because: owner of #1033834 is '' not 'William Desportes ' Failed to merge 1030415: Did not alter merged bugs. > stop Stopping processing here. Please contact me if you need assistance. -- 1030415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030415 1033834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033834 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033805: opendmarc: Segmentation fault with 3072-bit key signatures in ARC-Seal headers
I'm not running it myself. I thought people on postfix-users reported the problem with our package. If you're confident it's already addressed, please close the bug and sorry for the noise. Scott K On April 2, 2023 7:43:15 AM UTC, "David Bürgin" wrote: >Also note that we have been shipping the linked patch in Debian’s >opendmarc for a while now. It is included in stable, testing, unstable >as ‘arcseal-segfaults.patch’.
Processed: bug 1033732 is forwarded to https://lore.kernel.org/lkml/c02a2a2f-2b40-e13e-ac40-e5d19a66b...@cegetel.net/ ...
Processing commands for cont...@bugs.debian.org: > forwarded 1033732 > https://lore.kernel.org/lkml/c02a2a2f-2b40-e13e-ac40-e5d19a66b...@cegetel.net/ Bug #1033732 [src:linux] linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message Set Bug forwarded-to-address to 'https://lore.kernel.org/lkml/c02a2a2f-2b40-e13e-ac40-e5d19a66b...@cegetel.net/'. > severity 1033732 serious Bug #1033732 [src:linux] linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message Severity set to 'serious' from 'critical' > tags 1033732 + confirmed pending Bug #1033732 [src:linux] linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message Added tag(s) pending and confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1033732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: src:python-libzim: fails to migrate to testing for too long: FTBFS
Processing control commands:
> severity -1 important
Bug #1032568 {Done: Paul Gevers } [src:python-libzim]
src:python-libzim: fails to migrate to testing for too long: FTBFS
Severity set to 'important' from 'serious'
--
1032568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1032568: src:python-libzim: fails to migrate to testing for too long: FTBFS
Control: severity -1 important I am lowering the severity to prevent the auto-removal which would happen before zimlib v8.1.1-0.2 migrates. That version is compatible with python-libzim 2.1.0.
Processed: Re: pytest-salt-factories: autopkgtest failure with python3.10
Processing control commands: > severity -1 serious Bug #1009804 [src:pytest-salt-factories] pytest-salt-factories: autopkgtest failure with python3.10 Severity set to 'serious' from 'normal' > tags -1 bookworm-ignore Bug #1009804 [src:pytest-salt-factories] pytest-salt-factories: autopkgtest failure with python3.10 Added tag(s) bookworm-ignore. -- 1009804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033836: postgresql-mysql-fdw: autopkgtest regression: expected output changed
Source: postgresql-mysql-fdw Version: 2.8.0-3 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails since December 2022. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/p/postgresql-mysql-fdw/32436088/log.gz regression.diffs diff -U3 /tmp/autopkgtest-lxc.bpuoqtzm/downtmp/build.8FT/src/expected/dml.out /tmp/autopkgtest-lxc.bpuoqtzm/downtmp/build.8FT/src/results/dml.out --- /tmp/autopkgtest-lxc.bpuoqtzm/downtmp/build.8FT/src/expected/dml.out 2022-05-16 06:15:40.0 + +++ /tmp/autopkgtest-lxc.bpuoqtzm/downtmp/build.8FT/src/results/dml.out 2023-03-27 01:10:40.554906706 + @@ -92,7 +92,7 @@ $$ LANGUAGE plpgsql; NOTICE: failed to execute the MySQL query: -Unknown database 'public' +SELECT command denied to user 'edb'@'localhost' for table `public`.`student` -- Check with the same table name from different database. fdw126_ft3 is -- pointing to the mysql_fdw_regress1.numbers and not mysql_fdw_regress.numbers -- table. INSERT/UPDATE/DELETE should be failing. SELECT will return no rows. ### End 15 installcheck (FAILED with exit code 1) ### OpenPGP_signature Description: OpenPGP digital signature
Processed: polyml: autopkgtest regression: output on stderr
Processing control commands: > found -1 5.7.1-4 Bug #1033835 [src:polyml] polyml: autopkgtest regression: output on stderr Marked as found in versions polyml/5.7.1-4. > tags -1 bookworm-ignore Bug #1033835 [src:polyml] polyml: autopkgtest regression: output on stderr Added tag(s) bookworm-ignore. -- 1033835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: postgresql-mysql-fdw: autopkgtest regression: expected output changed
Processing control commands: > tags -1 bookworm-ignore Bug #1033836 [src:postgresql-mysql-fdw] postgresql-mysql-fdw: autopkgtest regression: expected output changed Added tag(s) bookworm-ignore. -- 1033836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033835: polyml: autopkgtest regression: output on stderr
Source: polyml Version: 5.7.1-5 Control: found -1 5.7.1-4 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails since July 2020. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The test itself seems to pass, but there's output on stderr, which without the allow-stderr restriction is considered a failure by autopkgtest. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/p/polyml/32128171/log.gz autopkgtest [19:23:44]: test upstream-polyc: [--- /usr/bin/ld: warning: /tmp/polyobj.2070.o: missing .note.GNU-stack section implies executable stack /usr/bin/ld: NOTE: This behaviour is deprecated and will be removed in a future version of the linker Test035.ML => Passed Test162.ML => Passed [...] Test026.ML => Passed autopkgtest [19:24:05]: test upstream-polyc: ---] autopkgtest [19:24:05]: test upstream-polyc: - - - - - - - - - - results - - - - - - - - - - upstream-polyc FAIL stderr: /usr/bin/ld: warning: /tmp/polyobj.2070.o: missing .note.GNU-stack section implies executable stack OpenPGP_signature Description: OpenPGP digital signature
Bug#1033834: php-log: autopkgtest regression: extract-zend2.2.phpt
Source: php-log Version: 1.13.2-1 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails since February 2023. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report (further info is lacking). The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-log/32117259/log.gz 1 FAILED TESTS: /tmp/autopkgtest-lxc.iockyhp3/downtmp/build.ww9/src/Log-1.13.2/tests/extract-zend2.2.phpt OpenPGP_signature Description: OpenPGP digital signature
Bug#1033833: unknown-horizons: Fails to start Couldn't open content/fonts/Unifont.ttf
Package: unknown-horizons Version: 2019.1-5 Severity: grave Dear Maintainer, When attempting to run uknown-horizons it fails with the following error message: $ unknown-horizons Discovered old settings file, auto-upgrading: 1 -> 38 Traceback (most recent call last): File "/usr/games/unknown-horizons", line 381, in main() File "/usr/games/unknown-horizons", line 122, in main ret = horizons.main.start(options) File "/usr/lib/python3/dist-packages/horizons/main.py", line 171, in start horizons.globals.fife.init() File "/usr/lib/python3/dist-packages/horizons/engine/engine.py", line 181, in init self._setting.apply() File "/usr/lib/python3/dist-packages/horizons/engine/settings.py", line 91, in apply change_language(language) File "/usr/lib/python3/dist-packages/horizons/i18n/__init__.py", line 163, in change_language horizons.globals.fife.pychan.loadFonts(fontdef) File "/usr/lib/python3/dist-packages/fife/extensions/pychan/fonts.py", line 98, in loadFonts for font in Font.loadFromFile(filename): ^^^ File "/usr/lib/python3/dist-packages/fife/extensions/pychan/fonts.py", line 82, in loadFromFile fonts.append(Font(font, lambda key, default=None: fontXMLFile.get(font, key, default))) ^ File "/usr/lib/python3/dist-packages/fife/extensions/pychan/fonts.py", line 52, in __init__ self.font = get_manager().createFont(self.source, self.size) File "/usr/lib/python3/dist-packages/fife/extensions/pychan/internal.py", line 176, in createFont return self.hook.create_font(path,size,glyphs) ^^^ fife.fife.CannotOpenFile: _[CannotOpenFile]_ , File couldn't be opened :: content/fonts/Unifont.ttf (Couldn't open content/fonts/Unifont.ttf) The root problem is a missing font or font format. I tried a simple rebuild of the package, but it had no effect. Looks like the font path is part of the source code, so might be more font references with similar issues. Also reported in Ubuntu as https://bugs.launchpad.net/ubuntu/+source/unknown-horizons/+bug/2011358 -- System Information: Debian Release: 12.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-7-amd64 (SMP w/3 CPU threads; PREEMPT) 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 Versions of packages unknown-horizons depends on: ii fonts-unifont 1:15.0.01-2 ii python3 3.11.2-1 ii python3-enet0.0~vcs.2022.12.26.git-0.2+b1 ii python3-fife0.4.2-5+b1 ii python3-future 0.18.2-6 ii python3-yaml6.0-3+b2 unknown-horizons recommends no packages. unknown-horizons suggests no packages. -- no debconf information -- mvh / best regards Hans Joachim Desserud http://desserud.org
Processed: php-log: autopkgtest regression: extract-zend2.2.phpt
Processing control commands: > tags -1 bookworm-ignore Bug #1033834 [src:php-log] php-log: autopkgtest regression: extract-zend2.2.phpt Added tag(s) bookworm-ignore. -- 1033834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033834 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033732: [PATCH v2] x86/acpi/boot: Do not register processors that cannot be onlined for x2apic
Le 02/04/2023 à 12:57, Borislav Petkov a écrit : On April 2, 2023 12:41:46 PM GMT+02:00, Guy Durrieu wrote: My system worked fine with kernel 6.1.15, but stopped booting after upgrading to 6.1.20 and resulted in a kernel panic: Does this fix it: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=x86/urgent Thx. Yes it does. Regards. -- Guy Durrieu
Bug#1033832: php-db: autopkgtest regression: FAIL DB::DB_Error[DB-1.11.0/tests/db_error.phpt]
Source: php-db Version: 1.11.0-0.2 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails since January 2022. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-db/32099485/log.gz autopkgtest [19:15:43]: test command1: [--- Running 5 tests FAIL DB::DB_Error[DB-1.11.0/tests/db_error.phpt] FAIL DB::Error 2[DB-1.11.0/tests/db_error2.phpt] PASS DB::factory[DB-1.11.0/tests/db_factory.phpt] PASS DB::isManip[DB-1.11.0/tests/db_ismanip.phpt] PASS DB::parseDSN[DB-1.11.0/tests/db_parsedsn.phpt] wrote log to "/tmp/autopkgtest-lxc.6vbl_673/downtmp/build.SoM/src/run-tests.log" TOTAL TIME: 00:00 3 PASSED TESTS 0 SKIPPED TESTS 2 FAILED TESTS: /tmp/autopkgtest-lxc.6vbl_673/downtmp/build.SoM/src/DB-1.11.0/tests/db_error.phpt /tmp/autopkgtest-lxc.6vbl_673/downtmp/build.SoM/src/DB-1.11.0/tests/db_error2.phpt Some tests failed autopkgtest [19:15:44]: test command1: ---] OpenPGP_signature Description: OpenPGP digital signature
Processed: php-db: autopkgtest regression: FAIL DB::DB_Error[DB-1.11.0/tests/db_error.phpt]
Processing control commands: > tags -1 bookworm-ignore Bug #1033832 [src:php-db] php-db: autopkgtest regression: FAIL DB::DB_Error[DB-1.11.0/tests/db_error.phpt] Added tag(s) bookworm-ignore. -- 1033832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
I sent the requested report. And indeed received a new patch to be tested. In progress... Le 02/04/2023 à 10:30, Diederik de Haas a écrit : On Sunday, 2 April 2023 00:24:26 CEST Diederik de Haas wrote: 2) The commit that Bjørn identified also contained a "Link:" tag: https://lore.kernel.org/r/20230105041059.39366-1-kvija...@amd.com The best thing to do is to respond to that thread and explain the issue you ran into. If you feel 'uncomfortable' or something like that, we can do this part too. If/when a new patch arrives, we will need your help in testing that though.
Bug#1033732: [PATCH v2] x86/acpi/boot: Do not register processors that cannot be onlined for x2apic
On April 2, 2023 12:41:46 PM GMT+02:00, Guy Durrieu wrote: >My system worked fine with kernel 6.1.15, but stopped booting after >upgrading to 6.1.20 and resulted in a kernel panic: Does this fix it: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=x86/urgent Thx. -- Sent from a small device: formatting sucks and brevity is inevitable.
Processed: php-dapphp-radius: autopkgtest regression: Class "Dapphp\Radius\Radius" not found
Processing control commands: > found -1 2.5.8-1 Bug #1033827 [src:php-dapphp-radius] php-dapphp-radius: autopkgtest regression: Class "Dapphp\Radius\Radius" not found Marked as found in versions php-dapphp-radius/2.5.8-1. > tags -1 bookworm-ignore Bug #1033827 [src:php-dapphp-radius] php-dapphp-radius: autopkgtest regression: Class "Dapphp\Radius\Radius" not found Added tag(s) bookworm-ignore. -- 1033827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033827: php-dapphp-radius: autopkgtest regression: Class "Dapphp\Radius\Radius" not found
Source: php-dapphp-radius Version: 2.5.8-2 Control: found -1 2.5.8-1 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it started to fail around May/June 2022. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-dapphp-radius/32131383/log.gz autopkgtest [22:22:18]: test command1: [--- PHPUnit 9.6.4 by Sebastian Bergmann and contributors. E.EES 13 / 13 (100%) Time: 00:00.003, Memory: 4.00 MB There were 11 errors: 1) ClientTest::testAttributes Error: Class "Dapphp\Radius\Radius" not found /tmp/autopkgtest-lxc.0c1uvl6j/downtmp/build.MSk/src/tests/ClientTest.php:12 2) ClientTest::testGetAttributes Error: Class "Dapphp\Radius\Radius" not found /tmp/autopkgtest-lxc.0c1uvl6j/downtmp/build.MSk/src/tests/ClientTest.php:39 3) ClientTest::testEncryptedPassword Error: Class "Dapphp\Radius\Radius" not found /tmp/autopkgtest-lxc.0c1uvl6j/downtmp/build.MSk/src/tests/ClientTest.php:75 4) ClientTest::testEncryptedPassword2 Error: Class "Dapphp\Radius\Radius" not found /tmp/autopkgtest-lxc.0c1uvl6j/downtmp/build.MSk/src/tests/ClientTest.php:88 5) ClientTest::testCryptCHAPMSv1 Error: Class "Crypt_CHAP_MSv1" not found /tmp/autopkgtest-lxc.0c1uvl6j/downtmp/build.MSk/src/tests/ClientTest.php:100 6) ClientTest::testCryptCHAPMSv1Indirect Error: Class "Dapphp\Radius\Radius" not found /tmp/autopkgtest-lxc.0c1uvl6j/downtmp/build.MSk/src/tests/ClientTest.php:116 7) ClientTest::testCryptCHAPMSv2 Error: Class "Crypt_CHAP_MSv2" not found /tmp/autopkgtest-lxc.0c1uvl6j/downtmp/build.MSk/src/tests/ClientTest.php:136 8) ClientTest::testAuthenticationPacket Error: Class "Dapphp\Radius\Radius" not found /tmp/autopkgtest-lxc.0c1uvl6j/downtmp/build.MSk/src/tests/ClientTest.php:156 9) ClientTest::testFramedAuthPacket Error: Class "Dapphp\Radius\Radius" not found /tmp/autopkgtest-lxc.0c1uvl6j/downtmp/build.MSk/src/tests/ClientTest.php:191 10) ClientTest::testMsChapV1Packet Error: Class "Dapphp\Radius\Radius" not found /tmp/autopkgtest-lxc.0c1uvl6j/downtmp/build.MSk/src/tests/ClientTest.php:230 11) ClientTest::testEapPacketBasic Error: Class "Dapphp\Radius\EAPPacket" not found /tmp/autopkgtest-lxc.0c1uvl6j/downtmp/build.MSk/src/tests/ClientTest.php:251 ERRORS! Tests: 13, Assertions: 1, Errors: 11, Skipped: 1. autopkgtest [22:22:19]: test command1: ---] OpenPGP_signature Description: OpenPGP digital signature
Bug#1033732: [PATCH v2] x86/acpi/boot: Do not register processors that cannot be onlined for x2apic
Le 05/01/2023 à 05:10, Kishon Vijay Abraham I a écrit :
Section 5.2.12.12 Processor Local x2APIC Structure in the ACPI v6.5
spec mandates that both "enabled" and "online capable" Local APIC Flags
should be used to determine if the processor is usable or not.
However, Linux doesn't use the "online capable" flag for x2APIC to
determine if the processor is usable. As a result, cpu_possible_mask has
incorrect value and results in more memory getting allocated for per_cpu
variables than it is going to be used.
Make sure Linux parses both "enabled" and "online capable" flags for
x2APIC to correctly determine if the processor is usable.
Fixes: aa06e20f1be6 ("x86/ACPI: Don't add CPUs that are not online capable")
Reviewed-by: Borislav Petkov (AMD)
Reported-by: Leo Duran
Signed-off-by: Kishon Vijay Abraham I
Hello everyone,
My system worked fine with kernel 6.1.15, but stopped booting after
upgrading to 6.1.20 and resulted in a kernel panic:
---
[ 0.117782] Kernel panic — not syncing: timer doesn’t work through
Interrupt-remapped IO-APIC
[ 0.117848] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-7-and64 #1 Debian
6.1.20-1
[ 0.117913] Hardware name: Gigabyte Technology Co., Ltd. ABS50M-Gaming
3/AB350M-Gaming 3-CF, BIOS F50d 07/02/2020
[ 0.117982] Call Trace:
[ 0.118634]
[ 0.118685] dump_stack_lvl+0x44/0x5c
[ 0.118143] panic+0x118/0x2ed
[ 0.118198] panic_if_irq_remap.cold+0x5/0x5
[ 0.118256] setup_I0_APIC+0x3db/0x64b
[ 0.118313] ? _raw_spin_unlock_irqrestore+0x23/0x40
[ 0.118372] ? clear_IO_APIC_pin+0x169/0x240
[ 0.118429] apic_intr_node_init+0x101/0x106
[ 0.118485] x86_late_time_init+0x20/0x34
[ 0.118542] start_kerne1+0x667/0x727
[ 0.118598] secondary_startup_64_no_verify+0xe5/0xeb
[ 0.118658]
[ 0.118711] ---[ end Kernel panic - not syncing: timer doesn’t work through
Interrupt-remapped IO-APIC J---
---
I tried an update of the BIOS up to F51h without any effect.
I sent a bug report to Debian Bug Tracking System. In reply Bjørn Mork
identified ce7d894bed1a539a8d6cff42f6f78f9db0c9c26b from the linux-6.1.y
branch as the likely culprit.
After building a 6.1.20 kernel with just that commit reverted, my system boots
normally again.
I reported that all tohttps://bugs.debian.org/1033732 and were asked to report
the issue 'upstream' (which is what that mail is).
Hope it will help!
Best regards.
-- Guy Durrieu
Processed: tagging 1030905
Processing commands for cont...@bugs.debian.org: > tags 1030905 + pending Bug #1030905 [src:sardana] sardana: FTBFS (cannot import name 'getargspec' from 'sphinx.util.inspect') Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1030905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1031479
Processing commands for cont...@bugs.debian.org: > tags 1031479 - bookworm Bug #1031479 [src:ruby-eye] ruby-eye: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'celluloid' (~> 0.16.0) among 108 total gem(s) (Gem::MissingSpecError) Removed tag(s) bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031479 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1031468
Processing commands for cont...@bugs.debian.org: > tags 1031468 - bookworm Bug #1031468 [src:ruby-rubydns] ruby-rubydns: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'celluloid' (= 0.16.0) among 111 total gem(s) (Gem::MissingSpecError) Removed tag(s) bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1001144
Processing commands for cont...@bugs.debian.org: > tags 1001144 - pending Bug #1001144 [odbc-mdbtools] odbc-mdbtools: Missing dependency on odbcinst Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1001144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 1031439 in 5
Processing commands for cont...@bugs.debian.org: > fixed 1031439 5 Bug #1031439 [src:gcc-sh-elf] gcc-sh-elf: FTBFS: make[6]: *** No rule to make target '../libsframe/libsframe.la', needed by 'libbfd.la'. Stop. Marked as fixed in versions gcc-sh-elf/5. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033433: marked as done (cfgrib: FTBFS in testing: make[1]: *** [debian/rules:21: override_dh_auto_test] Error 13)
Your message dated Sun, 02 Apr 2023 09:04:02 +
with message-id
and subject line Bug#1033433: fixed in cfgrib 0.9.10.3-2
has caused the Debian Bug report #1033433,
regarding cfgrib: FTBFS in testing: make[1]: *** [debian/rules:21:
override_dh_auto_test] Error 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.)
--
1033433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cfgrib
Version: 0.9.10.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230323 ftbfs-bookworm
Hi,
During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> for p in python3.11; do \
> PY3VERNUM=`echo $p | sed -e 's/python//' `; \
> pybuild --test --test-pytest -i $p -p $PY3VERNUM ; \
> done
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_cfgrib/build;
> python3.11 -m pytest tests
> = test session starts
> ==
> platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack
> rootdir: /<>, configfile: pyproject.toml
> collected 117 items / 1 skipped
>
> tests/test_10_cfunits.py . [
> 0%]
> tests/test_20_cfcoords.py . [
> 5%]
> tests/test_20_main.py . [
> 5%]
> tests/test_20_messages.py . [
> 13%]
> tests/test_25_cfmessage.py . [
> 17%]
> tests/test_30_dataset.py [
> 41%]
> tests/test_40_xarray_store.py .X.. [
> 48%]
> tests/test_40_xarray_to_grib_regular_ll.py . [
> 52%]
> tests/test_50_datamodels.py .. [
> 54%]
> tests/test_50_sample_data.py .X.x.FF.x.X.x.XX. [
> 86%]
> tests/test_50_xarray_getitem.py .. [
> 94%]
> tests/test_50_xarray_plugin.py ..
> [100%]
>
> === FAILURES
> ===
> test_canonical_dataset_to_grib[regular_gg_sfc]
>
>
> grib_name = 'regular_gg_sfc'
> tmpdir =
> local('/tmp/pytest-of-user42/pytest-5/test_canonical_dataset_to_grib5')
>
> @pytest.mark.parametrize(
> "grib_name",
> [
> pytest.param("era5-levels-members", marks=pytest.mark.xfail),
> "fields_with_missing_values",
> pytest.param("lambert_grid", marks=pytest.mark.xfail),
> "reduced_gg",
> "regular_gg_sfc",
> "regular_gg_pl",
> "regular_gg_ml",
> pytest.param("regular_gg_ml_g2", marks=pytest.mark.xfail),
> "regular_ll_sfc",
> pytest.param("regular_ll_msl", marks=pytest.mark.xfail),
> "scanning_mode_64",
> pytest.param("spherical_harmonics", marks=pytest.mark.xfail),
> "t_analysis_and_fc_0",
> ],
> )
> def test_canonical_dataset_to_grib(grib_name: str, tmpdir: py.path.local)
> -> None:
> grib_path = os.path.join(SAMPLE_DATA_FOLDER, grib_name + ".grib")
> out_path = str(tmpdir.join(grib_name + ".grib"))
>
> res = xarray_store.open_dataset(grib_path)
>
> with pytest.warns(FutureWarning):
> xarray_to_grib.canonical_dataset_to_grib(res, out_path)
> > reread = xarray_store.open_dataset(out_path)
>
> tests/test_50_sample_data.py:93:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> cfgrib/xarray_store.py:39: in open_dataset
> return xr.open_dataset(path, **kwargs) # type: ignore
> /usr/lib/python3/dist-packages/xarray/backends/api.py:541: in open_dataset
> backend_ds = backend.open_dataset(
> cfgrib/xarray_plugin.py:109: in open_dataset
> store = CfGribDataStore(
> cfgrib/xarray_plugin.py:40: in __init__
> self.ds = opener(filename, **backend_kwargs)
> cfgrib/dataset.py:780: in open_file
> return open_from_index(index, read_keys, time_dims, extra_coords,
> **kwargs)
> cfgrib/dataset.py:722: in open_from_index
> dimensions, variables, attributes, encoding = build_dataset_components(
> cfgrib/dataset.py:649: in
Bug#1033824: passwordsafe: autopkgtest regression: test dependencies transitioned
Source: passwordsafe Version: 1.16.0+dfsg-1 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it started to fail when we finished the wcwidgets3.0 -> wxwidgets3.2 transition in January 2023. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/p/passwordsafe/32250351/log.gz E: Unable to locate package libwxgtk3.0-gtk3-dev E: Unable to locate package wx3.0-headers OpenPGP_signature Description: OpenPGP digital signature
Processed: passwordsafe: autopkgtest regression: test dependencies transitioned
Processing control commands: > tags -1 bookworm-ignore Bug #1033824 [src:passwordsafe] passwordsafe: autopkgtest regression: test dependencies transitioned Added tag(s) bookworm-ignore. -- 1033824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
On Sunday, 2 April 2023 00:24:26 CEST Diederik de Haas wrote: > 2) The commit that Bjørn identified also contained a "Link:" tag: > https://lore.kernel.org/r/20230105041059.39366-1-kvija...@amd.com > > The best thing to do is to respond to that thread and explain the issue you > ran into. If you feel 'uncomfortable' or something like that, we can do this part too. If/when a new patch arrives, we will need your help in testing that though. signature.asc Description: This is a digitally signed message part.
Processed: osmo-iuh: autopkgtest regression: test dependency no longer in unstable/testing
Processing control commands: > tags -1 bookworm-ignore Bug #1033823 [src:osmo-iuh] osmo-iuh: autopkgtest regression: test dependency no longer in unstable/testing Added tag(s) bookworm-ignore. -- 1033823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033823: osmo-iuh: autopkgtest regression: test dependency no longer in unstable/testing
Source: osmo-iuh Version: 1.3.0+dfsg1-3 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it started failing in March 2022. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. It seems to me that the test is ment for a binary no longer build by this source (and not in the unstable/testing archive). The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/o/osmo-iuh/32120976/log.gz autopkgtest [13:22:14]: testing package osmo-iuh version 1.3.0+dfsg1-3 autopkgtest [13:22:14]: build not needed autopkgtest [13:22:15]: test can-show-help: preparing testbed Reading package lists... Building dependency tree... Reading state information... Correcting dependencies...Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) autopkgtest-satdep:amd64 < 0 @iU K Nb Ib > Broken autopkgtest-satdep:amd64 Depends on osmo-hnbgw:amd64 < none @un H > Removing autopkgtest-satdep:amd64 because I can't find osmo-hnbgw:amd64 OpenPGP_signature Description: OpenPGP digital signature
Processed: oscrypto: autopkgtest regression: certificate expired 2023-01-01 00:00:00Z
Processing control commands: > tags -1 bookworm-ignore Bug #1033822 [src:oscrypto] oscrypto: autopkgtest regression: certificate expired 2023-01-01 00:00:00Z Added tag(s) bookworm-ignore. -- 1033822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033822: oscrypto: autopkgtest regression: certificate expired 2023-01-01 00:00:00Z
Source: oscrypto Version: 1.3.0-1 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it started to fail on 2023-01-01. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/o/oscrypto/32095523/log.gz == ERROR: test_tls_connect_dh1024 (tests.test_tls.TLSTests.test_tls_connect_dh1024) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.a4kfr24h/downtmp/autopkgtest_tmp/tests/unittest_data.py", line 51, in generated_test_function original_function(self, *params) File "/tmp/autopkgtest-lxc.a4kfr24h/downtmp/autopkgtest_tmp/tests/test_tls.py", line 75, in wrapped f(*args) File "/tmp/autopkgtest-lxc.a4kfr24h/downtmp/autopkgtest_tmp/tests/test_tls.py", line 102, in tls_connect connection = tls.TLSSocket(hostname, port, session=session) ^^ File "/usr/lib/python3/dist-packages/oscrypto/_openssl/tls.py", line 456, in __init__ self._handshake() File "/usr/lib/python3/dist-packages/oscrypto/_openssl/tls.py", line 674, in _handshake raise_expired_not_yet_valid(cert) File "/usr/lib/python3/dist-packages/oscrypto/_tls.py", line 509, in raise_expired_not_yet_valid raise TLSVerificationError(message, certificate) oscrypto.errors.TLSVerificationError: Server certificate verification failed - certificate expired 2023-01-01 00:00:00Z OpenPGP_signature Description: OpenPGP digital signature
Bug#1033821: node-sockjs-client: autopkgtest regression: expected 1006 to equal 1000
Source: node-sockjs-client Version: 1.6.1+dfsg1-1 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it started to fail around October 2022. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/unstable/arm64/n/node-sockjs-client/31805805/log.gz 72 passing (2s) 9 pending 30 failing 1) Transports xhr-streaming same origin echo basic: Error: expected 1006 to equal 1000 at Assertion.assert (/usr/share/nodejs/expect.js/index.js:96:13) at Assertion.be.Assertion.equal (/usr/share/nodejs/expect.js/index.js:216:10) at sjs.onclose (tests/lib/echo-tests.js:46:27) at EventTarget.dispatchEvent (/usr/share/nodejs/sockjs-client/lib/event/eventtarget.js:51:20) at SockJS. (/usr/share/nodejs/sockjs-client/lib/main.js:363:10) at listOnTimeout (node:internal/timers:564:17) at process.processTimers (node:internal/timers:507:7) 2) Transports xhr-streaming same origin echo querystring: Error: expected 1006 to equal 1000 at Assertion.assert (/usr/share/nodejs/expect.js/index.js:96:13) at Assertion.be.Assertion.equal (/usr/share/nodejs/expect.js/index.js:216:10) at sjs.onclose (tests/lib/echo-tests.js:46:27) at EventTarget.dispatchEvent (/usr/share/nodejs/sockjs-client/lib/event/eventtarget.js:51:20) at SockJS. (/usr/share/nodejs/sockjs-client/lib/main.js:363:10) at listOnTimeout (node:internal/timers:564:17) at process.processTimers (node:internal/timers:507:7) OpenPGP_signature Description: OpenPGP digital signature
Processed: node-sockjs-client: autopkgtest regression: expected 1006 to equal 1000
Processing control commands: > tags -1 bookworm-ignore Bug #1033821 [src:node-sockjs-client] node-sockjs-client: autopkgtest regression: expected 1006 to equal 1000 Added tag(s) bookworm-ignore. -- 1033821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033821 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: node-snapdragon: autopkgtest regression: Cannot find module 'snapdragon-node'
Processing control commands: > found -1 0.12.1+~cs1.2.1-1 Bug #1033820 [src:node-snapdragon] node-snapdragon: autopkgtest regression: Cannot find module 'snapdragon-node' Marked as found in versions node-snapdragon/0.12.1+~cs1.2.1-1. > tags -1 bookworm-ignore Bug #1033820 [src:node-snapdragon] node-snapdragon: autopkgtest regression: Cannot find module 'snapdragon-node' Added tag(s) bookworm-ignore. -- 1033820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033820: node-snapdragon: autopkgtest regression: Cannot find module 'snapdragon-node'
Source: node-snapdragon
Version: 0.12.1+~cs1.2.1-2
Control: found -1 0.12.1+~cs1.2.1-1
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, it started to fail at
the beginning of 2022. Can you please investigate the situation and fix
it? I copied some of the output at the bottom of this report.
The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing. [Release Team member hat on] Because
we're currently in the hard freeze for bookworm, I have marked this bug
as bookworm-ignore. Targeted fixes are still welcome.
More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html
https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-snapdragon/32235297/log.gz
# Using ./package.(json|yaml)
# Node module name is snapdragon
# Test: require
# Testing snapdragon: ok
# Testing snapdragon-capture: ok
# Testing snapdragon-capture-set: node:internal/modules/cjs/loader:1042
throw err;
^
Error: Cannot find module 'snapdragon-node'
Require stack:
- /usr/share/nodejs/snapdragon-capture-set/index.js
- /tmp/autopkgtest-lxc.a182wk_7/downtmp/autopkgtest_tmp/[eval]
at Module._resolveFilename (node:internal/modules/cjs/loader:1039:15)
at Module._load (node:internal/modules/cjs/loader:885:27)
at Module.require (node:internal/modules/cjs/loader:1105:19)
at require (node:internal/modules/cjs/helpers:103:18)
at Object.
(/usr/share/nodejs/snapdragon-capture-set/index.js:3:12)
at Module._compile (node:internal/modules/cjs/loader:1218:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1272:10)
at Module.load (node:internal/modules/cjs/loader:1081:32)
at Module._load (node:internal/modules/cjs/loader:922:12)
at Module.require (node:internal/modules/cjs/loader:1105:19) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/usr/share/nodejs/snapdragon-capture-set/index.js',
'/tmp/autopkgtest-lxc.a182wk_7/downtmp/autopkgtest_tmp/[eval]'
]
}
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1033819: node-prosemirror-schema-list: autopkgtest regression: Accessing Object.prototype.__proto__ has been disallowed with --disable-proto=throw
Source: node-prosemirror-schema-list Version: 1.1.6+~1.0.3-1 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it started to fail recently (October 2022). Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-prosemirror-schema-list/32244360/log.gz # Launch debian/tests/pkg-js/test with sh -ex + mocha Error: Accessing Object.prototype.__proto__ has been disallowed with --disable-proto=throw at /usr/share/nodejs/prosemirror-transform/dist/index.js:452:37 at Object. (/usr/share/nodejs/prosemirror-transform/dist/index.js:506:2) at Module._compile (node:internal/modules/cjs/loader:1218:14) at Module._extensions..js (node:internal/modules/cjs/loader:1272:10) at Module.load (node:internal/modules/cjs/loader:1081:32) at Module._load (node:internal/modules/cjs/loader:922:12) at Module.require (node:internal/modules/cjs/loader:1105:19) at require (node:internal/modules/cjs/helpers:103:18) at Object. (/usr/share/nodejs/prosemirror-state/dist/index.js:4:28) at Module._compile (node:internal/modules/cjs/loader:1218:14) at Module._extensions..js (node:internal/modules/cjs/loader:1272:10) at Module.load (node:internal/modules/cjs/loader:1081:32) at Module._load (node:internal/modules/cjs/loader:922:12) at Module.require (node:internal/modules/cjs/loader:1105:19) at require (node:internal/modules/cjs/helpers:103:18) at Object. (/tmp/autopkgtest-lxc.8gf317sm/downtmp/autopkgtest_tmp/smokeMJk9e2/test/test-commands.js:1:64) at Module._compile (node:internal/modules/cjs/loader:1218:14) at Module._extensions..js (node:internal/modules/cjs/loader:1272:10) at Module.load (node:internal/modules/cjs/loader:1081:32) at Module._load (node:internal/modules/cjs/loader:922:12) at ModuleWrap. (node:internal/modules/esm/translators:169:29) at ModuleJob.run (node:internal/modules/esm/module_job:194:25) OpenPGP_signature Description: OpenPGP digital signature
Processed: node-prosemirror-schema-list: autopkgtest regression: Accessing Object.prototype.__proto__ has been disallowed with --disable-proto=throw
Processing control commands: > tags -1 bookworm-ignore Bug #1033819 [src:node-prosemirror-schema-list] node-prosemirror-schema-list: autopkgtest regression: Accessing Object.prototype.__proto__ has been disallowed with --disable-proto=throw Added tag(s) bookworm-ignore. -- 1033819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033818: node-nock: autopkgtest regression: Accessing Object.prototype.__proto__ has been disallowed
Source: node-nock Version: 13.2.9-3 Control: found -1 13.2.9-2 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it started to fail recently (October 2022). Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-nock/32235317/log.gz 525 passing (9s) 2 pending 1 failing 1) `replyWithFile()` reply with file with repeated: Error: Accessing Object.prototype.__proto__ has been disallowed with --disable-proto=throw at /usr/share/nodejs/sinon/lib/sinon/util/core/walk.js:20:17 at Array.forEach () at walkInternal (/usr/share/nodejs/sinon/lib/sinon/util/core/walk.js:19:5) at walkInternal (/usr/share/nodejs/sinon/lib/sinon/util/core/walk.js:33:9) at walk (/usr/share/nodejs/sinon/lib/sinon/util/core/walk.js:48:12) at walkObject (/usr/share/nodejs/sinon/lib/sinon/util/core/walk-object.js:18:5) at Function.spy (/usr/share/nodejs/sinon/lib/sinon/spy.js:170:16) at Sandbox.spy (/usr/share/nodejs/sinon/lib/sinon/sandbox.js:383:35) at Context. (tests/test_reply_with_file.js:45:11) at callFn (/usr/share/nodejs/mocha/lib/runnable.js:366:21) at Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:354:5) at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:666:10) at /usr/share/nodejs/mocha/lib/runner.js:789:12 at next (/usr/share/nodejs/mocha/lib/runner.js:581:14) at /usr/share/nodejs/mocha/lib/runner.js:591:7 at next (/usr/share/nodejs/mocha/lib/runner.js:474:14) at Immediate. (/usr/share/nodejs/mocha/lib/runner.js:559:5) at process.processImmediate (node:internal/timers:471:21) OpenPGP_signature Description: OpenPGP digital signature
Processed: node-nock: autopkgtest regression: Accessing Object.prototype.__proto__ has been disallowed
Processing control commands: > found -1 13.2.9-2 Bug #1033818 [src:node-nock] node-nock: autopkgtest regression: Accessing Object.prototype.__proto__ has been disallowed Marked as found in versions node-nock/13.2.9-2. > tags -1 bookworm-ignore Bug #1033818 [src:node-nock] node-nock: autopkgtest regression: Accessing Object.prototype.__proto__ has been disallowed Added tag(s) bookworm-ignore. -- 1033818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: node-mongodb: autopkgtest regression: warning on stderr
Processing control commands: > tags -1 bookworm-ignore Bug #1033817 [src:node-mongodb] node-mongodb: autopkgtest regression: warning on stderr Added tag(s) bookworm-ignore. -- 1033817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033805: opendmarc: Segmentation fault with 3072-bit key signatures in ARC-Seal headers
Also note that we have been shipping the linked patch in Debian’s opendmarc for a while now. It is included in stable, testing, unstable as ‘arcseal-segfaults.patch’.
Bug#1033817: node-mongodb: autopkgtest regression: warning on stderr
Source: node-mongodb Version: 3.6.4+~cs11.13.19-2 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-mongodb/32074441/log.gz autopkgtest [00:20:54]: test require: [--- (node:1580) Warning: Accessing non-existent property 'MongoError' of module exports inside circular dependency (Use `nodejs --trace-warnings ...` to show where the warning was created) autopkgtest [00:20:55]: test require: ---] OpenPGP_signature Description: OpenPGP digital signature
