Bug#1072597: marked as done (node-chownr: FTBFS: failing tests)
Your message dated Mon, 10 Jun 2024 13:49:18 + with message-id and subject line Bug#1072597: fixed in node-chownr 2.0.0-3 has caused the Debian Bug report #1072597, regarding node-chownr: FTBFS: failing tests 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.) -- 1072597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-chownr Version: 2.0.0-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure --buildsystem=nodejs dh_auto_build --buildsystem=nodejs No build command found, searching known files dh_auto_test --buildsystem=nodejs mkdir -p node_modules ln -s ../. node_modules/chownr /bin/sh -ex debian/tests/pkg-js/test + tap -R tap --no-cov test/concurrent-sync.js test/old-readdir.js TAP version 13 # Subtest: test/concurrent-sync.js # Subtest: get the ids to use 1..0 ok 1 - get the ids to use # time=26.223ms # Subtest: run test # Subtest: should complete successfully 1..0 ok 1 - should complete successfully # time=12.105ms # Subtest: verify ok 1 - should match pattern provided ok 2 - should match pattern provided ok 3 - d1 turned into a file ok 4 - should match pattern provided ok 5 - expected to throw ok 6 - expected to throw 1..6 ok 2 - verify # time=9.361ms # Subtest: verify a ok 1 - should match pattern provided ok 2 - should match pattern provided ok 3 - d1 turned into a file ok 4 - should match pattern provided ok 5 - expected to throw ok 6 - expected to throw 1..6 ok 3 - verify a # time=4.593ms # Subtest: verify a/b ok 1 - should match pattern provided ok 2 - should match pattern provided ok 3 - d1 turned into a file ok 4 - should match pattern provided ok 5 - expected to throw ok 6 - expected to throw 1..6 ok 4 - verify a/b # time=3.91ms # Subtest: verify a/b/c ok 1 - should match pattern provided ok 2 - should match pattern provided ok 3 - d1 turned into a file ok 4 - should match pattern provided ok 5 - expected to throw ok 6 - expected to throw 1..6 ok 5 - verify a/b/c # time=3.543ms # Subtest: verify d ok 1 - should match pattern provided ok 2 - should match pattern provided ok 3 - d1 turned into a file ok 4 - should match pattern provided ok 5 - expected to throw ok 6 - expected to throw 1..6 ok 6 - verify d # time=2.939ms # Subtest: verify d/e ok 1 - should match pattern provided ok 2 - should match pattern provided ok 3 - d1 turned into a file ok 4 - should match pattern provided ok 5 - expected to throw ok 6 - expected to throw 1..6 ok 7 - verify d/e # time=3.331ms # Subtest: verify d/e/f ok 1 - should match pattern provided ok 2 - should match pattern provided ok 3 - d1 turned into a file ok 4 - should match pattern provided ok 5 - expected to throw ok 6 - expected to throw 1..6 ok 8 - verify d/e/f # time=6.116ms # Subtest: verify g ok 1 - should match pattern provided ok 2 - should match pattern provided ok 3 - d1 turned into a file ok 4 - should match pattern provided ok 5 - expected to throw ok 6 - expected to throw 1..6 ok 9 - verify g # time=2.741ms # Subtest: verify g/h ok 1 - should match pattern provided ok 2 - should match pattern provided ok 3 - d1 turned into a file ok 4 - should match pattern provided ok 5 - expected to throw ok 6 - expected to throw 1..6 ok 10 - verify g/h
Bug#1072604: marked as done (node-stream-shift: FTBFS: failing tests)
Your message dated Mon, 10 Jun 2024 13:49:28 + with message-id and subject line Bug#1072604: fixed in node-stream-shift 1.0.3+~1.0.2-1 has caused the Debian Bug report #1072604, regarding node-stream-shift: FTBFS: failing tests 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.) -- 1072604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-stream-shift Version: 1.0.1+~1.0.0-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure --buildsystem=nodejs Link node_modules/@types/stream-shift -> ../../types-stream-shift dh_auto_build --buildsystem=nodejs No build command found, searching known files No build command found, searching known files dh_auto_test --buildsystem=nodejs ln -s ../. node_modules/stream-shift /bin/sh -ex debian/tests/pkg-js/test + tape test.js TAP version 13 # shifts next ok 1 should be deeply equivalent ok 2 should be deeply equivalent # shifts next with core ok 3 should be deeply equivalent /<>/index.js:16 return state.buffer[0].length ^ TypeError: Cannot read properties of null (reading 'length') at getStateLength (/<>/index.js:16:28) at shift (/<>/index.js:6:99) at Test. (/<>/test.js:24:10) at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17) at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28) at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17) at Immediate.next (/usr/share/nodejs/tape/lib/results.js:157:7) at process.processImmediate (node:internal/timers:478:21) Node.js v20.14.0 dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 make: *** [debian/rules:8: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202406/ About the archive rebuild: The build was made on virtual machines of type m6a.large and r6a.large from AWS, using sbuild and a reduced chroot with only build-essential packages. If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: node-stream-shift Source-Version: 1.0.3+~1.0.2-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-stream-shift, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-stream-shift 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, 10 Jun 2024 17:19:54 +0400 Source: node-stream-shift Architecture: source Version: 1.0.3+~1.0.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1072604 Changes: node-stream-shift (1.0.3+~1.0.2-1) unstable; urgency=medium . * Team upload * Update standards version to 4.6.2, no changes needed. * Declare compliance with policy 4.7.0 * New upstream version 1.0.3+~1.0.2 (Closes: #1072604) Checksums-Sha1: 2978f55712dc4c286e3ad396ff2e59c718afc0bf 2513 node-stream-shift_1.0.3+~1.0.2-1.dsc 56567b7f7fbeb48346d1c5114e7db4f43155564f 1605 node-stream-shift_1.0.3+~1.0.2.orig-types-stream-shift.tar.gz c31d9ea077f8ea6a8841e54d17292922f31985e7 2291 node-stream-shift_1.0.3+~1.0.2.orig.tar.gz 9a62fd1b57fce177bd
Bug#1068918: marked as done (node-zx: FTBFS test suite failure)
Your message dated Mon, 10 Jun 2024 17:32:34 +0400 with message-id and subject line Fixed elsewhere has caused the Debian Bug report #1068918, regarding node-zx: FTBFS test suite failure 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.) -- 1068918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-zx Version: 7.1.1+~cs6.7.23-2 Severity: serious Tags: ftbfs Justification: fails to build from source This package FTBFS in bookworm, even when using node-undici with fixed types. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- X-CrossAssassin-Score: 49590--- End Message ---
Processed: notfound 1068918 in node-zx/7.1.1+~cs6.7.23-2, notfound 1068918 in node-zx/7.1.1+~cs6.7.23-3
Processing commands for cont...@bugs.debian.org: > notfound 1068918 node-zx/7.1.1+~cs6.7.23-2 Bug #1068918 [src:node-zx] node-zx: FTBFS test suite failure No longer marked as found in versions node-zx/7.1.1+~cs6.7.23-2. > notfound 1068918 node-zx/7.1.1+~cs6.7.23-3 Bug #1068918 [src:node-zx] node-zx: FTBFS test suite failure No longer marked as found in versions node-zx/7.1.1+~cs6.7.23-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1068918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072603: marked as done (node-read-package-json: FTBFS: failing tests)
Your message dated Mon, 10 Jun 2024 12:19:44 + with message-id and subject line Bug#1072603: fixed in node-read-package-json 5.0.2+~2.0.0-2 has caused the Debian Bug report #1072603, regarding node-read-package-json: FTBFS: failing tests 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.) -- 1072603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-read-package-json Version: 5.0.2+~2.0.0-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure --buildsystem=nodejs Link node_modules/npm-normalize-package-bin -> ../npm-normalize-package-bin dh_auto_build --buildsystem=nodejs No build command found, searching known files No build command found, searching known files dh_auto_test --buildsystem=nodejs ln -s ../. node_modules/read-package-json /bin/sh -ex debian/tests/pkg-js/test + ls test/basic.js test/bin-non-string.js test/bin.js test/bom.js test/bundle.js test/fill-types.js test/git-head.js test/helpful.js test/indexjs.js test/main-non-string.js test/mans.js test/non-json.js test/readmes.js test/semver.js test/underscores.js + grep -v test/git-head.js + tap --no-cov test/basic.js test/bin-non-string.js test/bin.js test/bom.js test/bundle.js test/fill-types.js test/helpful.js test/indexjs.js test/main-non-string.js test/mans.js test/non-json.js test/readmes.js test/semver.js test/underscores.js TAP version 13 # Subtest: test/basic.js # Subtest: basic test ok 1 - expect truthy value ok 2 - should be equal ok 3 - should be equal ok 4 - should be equal ok 5 - type is object ok 6 - should be equal ok 7 - should be equivalent ok 8 - should be equal ok 9 - should be equal ok 10 - should be equivalent ok 11 - should contain all provided fields ok 12 - should be equivalent 1..12 ok 1 - basic test # time=73.281ms 1..1 # time=78.099ms ok 1 - test/basic.js # time=78.099ms # Subtest: test/bin-non-string.js # Subtest: non-string bin entries # ok 1 - no error from readJson ok 2 - should be equal 1..2 ok 1 - non-string bin entries # time=58.267ms 1..1 # time=65.274ms ok 2 - test/bin-non-string.js # time=65.274ms # Subtest: test/bin.js # Subtest: Bin test ok 1 - should be equal ok 2 - should be equivalent strictly 1..2 ok 1 - Bin test # time=41.372ms # Subtest: Bad bin test ok 1 - should be equal ok 2 - should be equal 1..2 ok 2 - Bad bin test # time=26.1ms # Subtest: Empty bin test ok 1 - should be equal ok 2 - no mapping to bin because object was empty 1..2 ok 3 - Empty bin test # time=11.034ms 1..3 # time=87.294ms ok 3 - test/bin.js # time=87.294ms # Subtest: test/bom.js # Subtest: BOM test ok 1 - should be equivalent 1..1 ok 1 - BOM test # time=57.377ms 1..1 # time=70.553ms ok 4 - test/bom.js # time=70.553ms # Subtest: test/bundle.js # Subtest: bundle-true ok 1 - should match pattern provided 1..1 ok 1 - bundle-true # time=68.833ms # Subtest: bundle-null ok 1 - no bundleDependencies ok 2 - no bundledDependencies 1..2 ok 2 - bundle-null # time=7.911ms # Subtest: bundle-array ok 1 - should match pattern provided 1..1 ok 3 - bundle-array # time=13.307ms # Subtest: bundle-false ok 1 - should match pattern provided 1..1 ok 4 - bundle-false # time=25.722ms 1..4 # time=127.224ms ok 5 - test/bundle.js # time=127.224ms # Subtest: test/fill-types.js # Subtest: adds types with a custom main field ok 1 - should match pattern provided 1..1 ok 1 - adds types with a custom main field # time=43.582ms # Subtest: handles the inferred index.js ok 1 - should match pattern provided 1..1 ok 2 - handles the inferred index.js # time=11.425ms # Subtest: handles subpaths and starting with ./ ok 1 - should match pattern provided 1..1 ok 3 - handles subpaths and starting with ./ # time=3.784ms # Subtest: hand
Bug#1072602: marked as done (node-parse-json: FTBFS: failing tests)
Your message dated Mon, 10 Jun 2024 12:19:37 +
with message-id
and subject line Bug#1072602: fixed in node-parse-json 5.2.0+~cs5.1.7-2
has caused the Debian Bug report #1072602,
regarding node-parse-json: FTBFS: failing tests
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.)
--
1072602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-parse-json
Version: 5.2.0+~cs5.1.7-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
dh_auto_configure --buildsystem=nodejs
Link ./node_modules/@types/mocha -> /usr/share/nodejs/@types/mocha
Link lines-and-columns/node_modules/assert -> /usr/share/nodejs/assert
Link lines-and-columns/node_modules/@types/mocha ->
/usr/share/nodejs/@types/mocha
Link node_modules/lines-and-columns -> ../lines-and-columns
Link node_modules/@types/parse-json -> ../../types-parse-json
dh_auto_build --buildsystem=nodejs
No build command found, searching known files
Found debian/nodejs/lines-and-columns/build
cd ./lines-and-columns && sh -ex
../debian/nodejs/lines-and-columns/build
+ tsc --build tsconfig.build.json
+ mv build/index.js build/index.mjs
+ babeljs -o build/index.js --presets @babel/preset-env build/index.mjs
No build command found, searching known files
dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/parse-json
/bin/sh -ex debian/tests/pkg-js/test
+ tape test.js
TAP version 13
# main
ok 1 should be truthy
ok 2 should throw
not ok 3 should throw
---
operator: throws
expected: |-
'/Unexpected token "?}"?.*in foo\\.json/'
actual: |-
ErrorEXError { name: 'JSONError', codeFrame: ' 1 | {\n 2 | \t"foo": true,\n> 3 | }\n| ^',
fileName: 'foo.json', message: 'Expected double-quoted property name in JSON at position 16 while parsing
\'{\t"foo": true,}\' in foo.json \n\n 1 | {\n 2 | \t"foo": true,\n> 3 | }\n| ^\n' }
at: Test. (/<>/test.js:15:4)
stack: |-
JSONError: Expected double-quoted property name in JSON at position 16 while
parsing '{ "foo": true,}' in foo.json
1 | {
2 | "foo": true,
> 3 | }
| ^
at parseJson (/<>/index.js:29:21)
at /<>/test.js:17:4
at Test.throws (/usr/share/nodejs/tape/lib/test.js:630:3)
at Test.bound [as throws] (/usr/share/nodejs/tape/lib/test.js:95:17)
at Test. (/<>/test.js:15:4)
at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28)
at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17)
at Immediate.next [as _onImmediate]
(/usr/share/nodejs/tape/lib/results.js:157:7)
at process.processImmediate (node:internal/timers:478:21)
...
not ok 4 should throw
---
operator: throws
expected: |-
'/Unexpected token "?}"?.*in foo\\.json/'
actual: |-
ErrorEXError { name: 'JSONError', fileName: 'foo.json', codeFrame: ' 1 | {\n 2 | \t"foo":
true,\n> 3 | }\n| ^', message: 'Expected double-quoted property name in JSON at position 16 while parsing
\'{\t"foo": true,}\' in foo.json \n\n 1 | {\n 2 | \t"foo": true,\n> 3 | }\n| ^\n' }
at: Test. (/<>/test.js:24:4)
stack: |-
JSONError: Expected double-quoted property name in JSON at position 16 while
parsing '{ "foo": true,}' in foo.json
1 | {
2 | "foo": true,
> 3 | }
| ^
at parseJson (/<>/index.js:29:21)
at /<>/test.js:25:3
at Test.throws (/usr/share/nodejs/tape/lib/test.js:630:3)
at Test.bound [as throws] (/usr/share/nodejs/tape/lib/test.js:95:17)
at Test. (/<>/test.js:24:4)
at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28)
at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17)
at Immediate.next [as _onImmediate]
(/usr/share/nodejs/tape/lib/results.js:157:7)
at process.processImmediate (nod
Bug#1072598: marked as done (node-decompress-response: FTBFS: failing tests)
Your message dated Mon, 10 Jun 2024 12:19:26 +
with message-id
and subject line Bug#1072598: fixed in node-decompress-response 6.0.0-3
has caused the Debian Bug report #1072598,
regarding node-decompress-response: FTBFS: failing tests
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.)
--
1072598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-decompress-response
Version: 6.0.0-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
dh_auto_configure --buildsystem=nodejs
dh_auto_build --buildsystem=nodejs
No build command found, searching known files
dh_auto_test --buildsystem=nodejs
mkdir -p node_modules
ln -s ../. node_modules/decompress-response
/bin/sh -ex debian/tests/pkg-js/test
+ tape test/test.js
TAP version 13
# decompress gzipped content
ok 1 should be truthy
ok 2 should be truthy
ok 3 should be truthy
ok 4 should be truthy
ok 5 should be truthy
ok 6 should be truthy
ok 7 should be truthy
ok 8 should be truthy
ok 9 should be truthy
ok 10 should be truthy
ok 11 should be truthy
ok 12 should be truthy
ok 13 should be strictly equal
ok 14 should be falsy
# decompress deflated content
node:events:497
throw er; // Unhandled 'error' event
^
Error: socket hang up
at Socket.socketOnEnd (node:_http_client:524:23)
at Socket.emit (node:events:531:35)
at endReadableNT (node:internal/streams/readable:1696:12)
at process.processTicksAndRejections
(node:internal/process/task_queues:82:21)
Emitted 'error' event on ClientRequest instance at:
at Socket.socketOnEnd (node:_http_client:524:9)
at Socket.emit (node:events:531:35)
at endReadableNT (node:internal/streams/readable:1696:12)
at process.processTicksAndRejections
(node:internal/process/task_queues:82:21) {
code: 'ECONNRESET'
}
Node.js v20.14.0
dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
make: *** [debian/rules:8: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202406/
About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: node-decompress-response
Source-Version: 6.0.0-3
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
node-decompress-response, 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 1072...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yadd (supplier of updated node-decompress-response 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, 10 Jun 2024 15:53:48 +0400
Source: node-decompress-response
Architecture: source
Version: 6.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Yadd
Closes: 1072598
Changes:
node-decompress-response (6.0.0-3) unstable; urgency=medium
.
* Team upload
.
[ Debian Janitor ]
* Apply multi-arch hints. + node-decompress-response: Add Multi-Arch:
foreign
.
[ Yadd ]
* Declare compliance with policy 4.7.0
* Fix test for nodejs 20 (Closes: #1072598)
Checksums-Sha1
Bug#1072600: marked as done (node-json-parse-better-errors: FTBFS: failing tests)
Your message dated Mon, 10 Jun 2024 12:05:54 +
with message-id
and subject line Bug#1072600: fixed in node-json-parse-better-errors
1.0.2+~cs3.3.1-3
has caused the Debian Bug report #1072600,
regarding node-json-parse-better-errors: FTBFS: failing tests
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.)
--
1072600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-json-parse-better-errors
Version: 1.0.2+~cs3.3.1-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
dh_auto_configure --buildsystem=nodejs
Link node_modules/json-parse-even-better-errors ->
../json-parse-even-better-errors
Link node_modules/@types/json-parse-better-errors ->
../../types-json-parse-better-errors
dh_auto_build --buildsystem=nodejs
No build command found, searching known files
No build command found, searching known files
No build command found, searching known files
dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/json-parse-better-errors
cd ./json-parse-even-better-errors && sh -ex
../debian/nodejs/json-parse-even-better-errors/test
+ tap -J test/index.js
TAP version 13
(node:186126) DeprecationWarning: deepEqual() is deprecated, use same() instead
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:186126) DeprecationWarning: isa() is deprecated, use type() instead
# Subtest: test/index.js
# Subtest: parses JSON
1..6
ok 1 - object
ok 2 - array
ok 3 - num
ok 4 - null
ok 5 - true
ok 6 - false
ok 1 - parses JSON # time=9.314ms
# Subtest: preserves indentation and newline styles
# Subtest: {"type":"object","newline":"\\n","indent":""}
ok 1 - preserved newline
ok 2 - preserved indent
1..2
ok 1 - {"type":"object","newline":"\\n","indent":""} # time=1.422ms
# Subtest: {"type":"array","newline":"\\n","indent":""}
ok 1 - preserved newline
ok 2 - preserved indent
1..2
ok 2 - {"type":"array","newline":"\\n","indent":""} # time=1.275ms
# Subtest: {"type":"object","newline":"\\n","indent":" "}
ok 1 - preserved newline
ok 2 - preserved indent
1..2
ok 3 - {"type":"object","newline":"\\n","indent":" "} # time=0.879ms
# Subtest: {"type":"array","newline":"\\n","indent":" "}
ok 1 - preserved newline
ok 2 - preserved indent
1..2
ok 4 - {"type":"array","newline":"\\n","indent":" "} # time=0.873ms
# Subtest: {"type":"object","newline":"\\n","indent":"\\t"}
ok 1 - preserved newline
ok 2 - preserved indent
1..2
ok 5 - {"type":"object","newline":"\\n","indent":"\\t"} # time=0.72ms
# Subtest: {"type":"array","newline":"\\n","indent":"\\t"}
ok 1 - preserved newline
ok 2 - preserved indent
1..2
ok 6 - {"type":"array","newline":"\\n","indent":"\\t"} # time=0.697ms
# Subtest: {"type":"object","newline":"\\n","indent":" \\t \\t "}
ok 1 - preserved newline
ok 2 - preserved indent
1..2
ok 7 - {"type":"object","newline":"\\n","indent":" \\t \\t "} #
time=0.591ms
# Subtest: {"type":"array",&q
Processed: Bug#1072602 marked as pending in node-parse-json
Processing control commands: > tag -1 pending Bug #1072602 [src:node-parse-json] node-parse-json: FTBFS: failing tests Added tag(s) pending. -- 1072602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072306: marked as done (src:r-cran-rcppparallel: fails to migrate to testing for too long: autopkgtest regression)
Your message dated Mon, 10 Jun 2024 12:06:30 + with message-id and subject line Bug#1072306: fixed in r-cran-rcppparallel 5.1.7+dfsg-5 has caused the Debian Bug report #1072306, regarding src:r-cran-rcppparallel: fails to migrate to testing for too long: autopkgtest regression 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.) -- 1072306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072306 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-rcppparallel Version: 5.1.7+dfsg-3 Severity: serious Control: close -1 5.1.7+dfsg-4 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:r-cran-rcppparallel has been trying to migrate for 38 days [2]. Hence, I am filing this bug. The version in unstable fails its own autopkgtest. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=r-cran-rcppparallel OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: r-cran-rcppparallel Source-Version: 5.1.7+dfsg-5 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of r-cran-rcppparallel, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-cran-rcppparallel 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, 10 Jun 2024 13:01:46 +0200 Source: r-cran-rcppparallel Architecture: source Version: 5.1.7+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Closes: 1072306 Changes: r-cran-rcppparallel (5.1.7+dfsg-5) unstable; urgency=medium . * Re-add r-base-dev to Test-Depends (seems dh-update-R removed it again) Closes: #1072306 Checksums-Sha1: 72d2be13e0916944f27c2e5b692194c0e1797315 2314 r-cran-rcppparallel_5.1.7+dfsg-5.dsc a136b96ecdc7d452f142d20f30edb6210dd5e03a 4844 r-cran-rcppparallel_5.1.7+dfsg-5.debian.tar.xz 11b8be02c01a9b2e750a552bbe0da5c4e3673382 11327 r-cran-rcppparallel_5.1.7+dfsg-5_amd64.buildinfo Checksums-Sha256: e665255faf807092a8eb1967a63ca74bc569b6b8c1cb15b23db59aa5226f6f97 2314 r-cran-rcppparallel_5.1.7+dfsg-5.dsc b12f7eef61910bcee7227348414c1a36029739c55f19d2ca778725a9b91e511c 4844 r-cran-rcppparallel_5.1.7+dfsg-5.debian.tar.xz 2ad160fb659c486656abe920f8bb731a446f7944119d14ed3d6c1eaa3e28807c 11327 r-cran-rcppparallel_5.1.7+dfsg-5_amd64.buildinfo Files: 5d7b9b045d309029ecad7ad2692f9579 2314 gnu-r optional r-cran-rcppparallel_5.1.7+dfsg-5.dsc 1737f31816dc6047dec0b48d17da24c0 4844 gnu-r optional r-cran-rcppparallel_5.1.7+dfsg-5.debian.tar.xz c2b85577579847e0563b11ddcba728b3 11327 gnu-r optional r-cran-rcppparallel_5.1.7+dfsg-5_amd64.buildinfo -BEGIN PGP SIGNATURE
Processed: Bug#1072603 marked as pending in node-read-package-json
Processing control commands: > tag -1 pending Bug #1072603 [src:node-read-package-json] node-read-package-json: FTBFS: failing tests Added tag(s) pending. -- 1072603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1072598 marked as pending in node-decompress-response
Processing control commands: > tag -1 pending Bug #1072598 [src:node-decompress-response] node-decompress-response: FTBFS: failing tests Added tag(s) pending. -- 1072598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1072600 marked as pending in node-json-parse-better-errors
Processing control commands: > tag -1 pending Bug #1072600 [src:node-json-parse-better-errors] node-json-parse-better-errors: FTBFS: failing tests Added tag(s) pending. -- 1072600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072835: marked as done (jpeg-xl: Failing autopkgtests)
Your message dated Mon, 10 Jun 2024 10:49:14 + with message-id and subject line Bug#1072835: fixed in jpeg-xl 0.9.2-6 has caused the Debian Bug report #1072835, regarding jpeg-xl: Failing autopkgtests 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.) -- 1072835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jpeg-xl Version: 0.9.2-5 Severity: serious Tags: experimental jpeg-xl in experimental has failing autopkgtests. https://release.debian.org/britney/pseudo-excuses-experimental.html#jpeg-xl https://ci.debian.net/packages/j/jpeg-xl/unstable/amd64/ autopkgtest log excerpt == md5sum: traffic_light-0-ec0.ppm: No such file or directory traffic_light-0-ec0.ppm: FAILED open or read traffic_light-0-ec1.pgm: FAILED open or read md5sum: traffic_light-0-ec1.pgm: No such file or directory md5sum: traffic_light-1-ec0.ppm: No such file or directory traffic_light-1-ec0.ppm: FAILED open or read md5sum: traffic_light-1-ec1.pgm: No such file or directory traffic_light-1-ec1.pgm: FAILED open or read md5sum: traffic_light-2-ec0.ppm: No such file or directory traffic_light-2-ec0.ppm: FAILED open or read md5sum: traffic_light-2-ec1.pgm: No such file or directory traffic_light-2-ec1.pgm: FAILED open or read md5sum: traffic_light-3-ec0.ppm: No such file or directory traffic_light-3-ec0.ppm: FAILED open or read md5sum: traffic_light-3-ec1.pgm: No such file or directory traffic_light-3-ec1.pgm: FAILED open or read md5sum: animation_patches-0-ec0.ppm: No such file or directory animation_patches-0-ec0.ppm: FAILED open or read md5sum: animation_patches-0-ec1.pgm: No such file or directory animation_patches-0-ec1.pgm: FAILED open or read md5sum: animation_patches-1-ec0.ppm: No such file or directory animation_patches-1-ec0.ppm: FAILED open or read md5sum: animation_patches-1-ec1.pgm: No such file or directory animation_patches-1-ec1.pgm: FAILED open or read pq_gradient.pgm: OK md5sum: WARNING: 12 listed files could not be read Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: jpeg-xl Source-Version: 0.9.2-6 Done: Mathieu Malaterre We believe that the bug you reported is fixed in the latest version of jpeg-xl, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Malaterre (supplier of updated jpeg-xl 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, 10 Jun 2024 12:33:42 +0200 Source: jpeg-xl Architecture: source Version: 0.9.2-6 Distribution: experimental Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Mathieu Malaterre Closes: 1072835 Changes: jpeg-xl (0.9.2-6) experimental; urgency=medium . * d/t/run-unit-test: Adapt test suite. Closes: #1072835 Checksums-Sha1: 1d4ba779d84f8f6af46e91caf7313132d5b6b1ce 3154 jpeg-xl_0.9.2-6.dsc 564b848bbbe8c4c45c545c5497ee34cb0620ae0a 20672 jpeg-xl_0.9.2-6.debian.tar.xz 54812979d74a739e050def23e2d9201e716e963a 15234 jpeg-xl_0.9.2-6_source.buildinfo Checksums-Sha256: 86342363f8f3f6bbf64dd5dacfabf6342ac91fbef4effdaf82b6882c9fa31b93 3154 jpeg-xl_0.9.2-6.dsc 60dd259d20c4fb4d6610be1c9b6162f569f659cdd911b3de230b362115fb6f84 20672 jpeg-xl_0.9.2-6.debian.tar.xz 1f303386f454b772d4a55766a409b6ed8e529a8f47a17b02e862a845b50934a3 15234 jpeg-xl_0.9.2-6_source.buildinfo Files: 9ef04676596f0ff1d141775a60df0ca4 3154 graphics optional jpeg-xl_0.9.2-6.dsc 7e03b2450c67fe79a43dc425e7598a65 20672 graphics optional jpeg-xl_0.9.2-6.debian.tar.xz ebc4027d457178bff0b6b291fa2e7d2e 15234 graphics optional jpeg-xl_0.9.2-6_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmZm1rkRHG1hbGF0QGRl Ymlhbi5vcmcACgkQAXHhgorgk0WzqBAAm6olVGAgoVy6bPOQZ39tngnQwpajvBLY eA/LUIOPbaYgdg/wQ/KUyS5y9ie5yrewLljqY7g1pLnxMb02eqo6Gk8iUVJYhPUa ++ETNc9RNgNx0pveybzyxFfUT2HLeAP+URV+247XI/RKqQBkeK4hE99XgHyB+kPf 6amAvxJJdsxlN7MaDBWhMzhulh9XnFw8BHj2fzKGo/tWWSopxDQ58nDejpXCDnv+ xa8zAjgW873pfZDorF+4Xoy4Illyflw0yecxIESO19j4hyureV3RA4PNo8jcyU+T cNas2lkR2EmEuDvaPyS7++9iZQMQuI+iUmVXQ5JRGUpkD
Processed: mythtv-status: diff for NMU version 1.1.0-1.1
Processing control commands: > tags 1052282 + patch Bug #1052282 [src:mythtv-status] mythtv-status FTBFS with nocheck profile Added tag(s) patch. > tags 1052282 + pending Bug #1052282 [src:mythtv-status] mythtv-status FTBFS with nocheck profile Added tag(s) pending. -- 1052282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052282 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: irker: diff for NMU version 2.23+dfsg-1.1
Processing control commands: > tags 1060467 + patch Bug #1060467 [src:irker] irker: Please switch Build-Depends to systemd-dev Added tag(s) patch. > tags 1060467 + pending Bug #1060467 [src:irker] irker: Please switch Build-Depends to systemd-dev Added tag(s) pending. -- 1060467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): file loss caused by systemd-dev missing
Processing commands for cont...@bugs.debian.org: > forcemerge 1060467 1072082 Bug #1060467 [src:irker] irker: Please switch Build-Depends to systemd-dev Unable to merge bugs because: package of #1072082 is 'irker' not 'src:irker' Failed to forcibly merge 1060467: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1060467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060467 1072082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072082 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072798: marked as done (nvidia-graphics-drivers-tesla-470: CVE-2024-0090, CVE-2024-0092)
Your message dated Mon, 10 Jun 2024 08:49:49 + with message-id and subject line Bug#1072798: fixed in nvidia-graphics-drivers-tesla-470 470.256.02-1 has caused the Debian Bug report #1072798, regarding nvidia-graphics-drivers-tesla-470: CVE-2024-0090, CVE-2024-0092 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.) -- 1072798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Severity: serious Tags: security upstream X-Debbugs-Cc: Debian Security Team Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2024-0090, CVE-2024-0092 Control: tag -2 + wontfix Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2024-0090, CVE-2024-0092 Control: tag -3 + wontfix Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2024-0090, CVE-2024-0092 Control: tag -4 + wontfix Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1 Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2024-0090, CVE-2024-0092 Control: tag -5 + wontfix Control: close -5 450.248.02-4 Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2024-0090, CVE-2024-0092 Control: tag -6 + wontfix Control: close -6 460.106.00-3 Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1 Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2024-0090, CVE-2024-0092 Control: reassign -8 src:nvidia-graphics-drivers-tesla 510.85.02-1 Control: retitle -8 nvidia-graphics-drivers-tesla: CVE-2024-0090, CVE-2024-0092 Control: found -8 515.48.07-1 Control: found -8 525.60.13-1 Control: tag -8 + wontfix Control: close -8 525.147.05-6 Control: reassign -9 src:nvidia-open-gpu-kernel-modules 515.43.04-1 Control: retitle -9 nvidia-open-gpu-kernel-modules: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092 Control: found -9 520.56.06-1 Control: found -9 525.85.12-1 Control: found -9 530.30.02-1 Control: found -9 535.43.02-1 Control: found -9 545.23.06-1 Control: found -9 550.40.07-1 Control: found -9 555.42.02-1 Control: found -1 340.24-1 Control: found -1 343.22-1 Control: found -1 396.18-1 Control: found -1 430.14-1 Control: found -1 455.23.04-1 Control: found -1 465.24.02-1 Control: found -1 495.44-1 Control: found -1 515.48.07-1 Control: found -1 520.56.06-1 Control: found -1 525.53-1 Control: found -1 530.30.02-1 Control: found -1 535.43.02-1 Control: found -1 545.23.06-1 Control: found -1 550.40.07-1 Control: found -1 555.42.02-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5551 CVE-2024-0090 NVIDIA GPU driver for Windows and Linux contains a vulnerability where a user can cause an out-of-bounds write. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. CVE-2024-0091 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability where a user can cause an untrusted pointer dereference by executing a driver API. A successful exploit of this vulnerability might lead to denial of service, information disclosure, and data tampering. CVE-2024-0092 NVIDIA GPU Driver for Windows and Linux contains a vulnerability where an improper check or improper handling of exception conditions might lead to denial of service. Linux Driver Branch CVE IDs Addressed R555, R550 CVE-2024-0090, CVE-2024-0091, CVE-2024-0092 R535, R470 CVE-2024-0090, CVE-2024-0092 Driver Branch Affected Driver VersionsUpdated Driver Version R555All driver versions prior to 555.52.04 555.52.04 R550All driver versions prior to 550.90.07 550.90.07 R535All driver versions prior to 535.183.01 535.183.01 R470All driver versions prior to 470.256.02 470.256.02 Andreas --- End Message --- --- Begin Message --- Source: nvidia-graphics-drivers-tesla-470 Source-Version: 470.256.02-1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers-tesla-470, 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
Bug#1064720: marked as done (ruby-capybara: FTBFS: ERROR: Test "ruby3.1" failed: NoMethodError:)
Your message dated Mon, 10 Jun 2024 08:36:03 + with message-id and subject line Bug#1064720: fixed in ruby-capybara 3.40.0+ds-1 has caused the Debian Bug report #1064720, regarding ruby-capybara: FTBFS: ERROR: Test "ruby3.1" failed: NoMethodError: 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.) -- 1064720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-capybara Version: 3.36.0+ds-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240224 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > NoMethodError: > undefined method `stdio' for Puma::Events:Class > > events = conf.options[:Silent] ? ::Puma::Events.strings : > ::Puma::Events.stdio > > ^^ > # /<>/lib/capybara/registrations/servers.rb:32:in `block > in ' > # /<>/lib/capybara.rb:252:in `run_default_server' > # /<>/lib/capybara/registrations/servers.rb:4:in `block in > ' > # /<>/lib/capybara/server.rb:77:in `block in boot' > > Finished in 52.8 seconds (files took 1.06 seconds to load) > 2512 examples, 36 failures, 6 pending > > Failed examples: > > rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:1]' # > Capybara::Session DSL #current_url, #current_path, #current_host is affected > by visiting a page directly > rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:2]' # > Capybara::Session DSL #current_url, #current_path, #current_host returns to > the app host when visiting a relative url > rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:3]' # > Capybara::Session DSL #current_url, #current_path, #current_host is affected > by setting Capybara.app_host > rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:4]' # > Capybara::Session DSL #current_url, #current_path, #current_host is > unaffected by following a relative link > rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:5]' # > Capybara::Session DSL #current_url, #current_path, #current_host is affected > by following an absolute link > rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:6]' # > Capybara::Session DSL #current_url, #current_path, #current_host is > unaffected by posting through a relative form > rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:7]' # > Capybara::Session DSL #current_url, #current_path, #current_host is affected > by posting through an absolute form > rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:8]' # > Capybara::Session DSL #current_url, #current_path, #current_host is affected > by following a redirect > rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:9]' # > Capybara::Session DSL #current_url, #current_path, #current_host maintains > fragment > rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:10]' # > Capybara::Session DSL #current_url, #current_path, #current_host redirects to > a fragment > rspec /<>/spec/dsl_spec.rb:165 # Capybara::DSL#current_session > should change with the current driver > rspec /<>/spec/dsl_spec.rb:171 # Capybara::DSL#current_session > should be persistent even across driver changes > rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:1]' # > Capybara::Session RackTest #current_url, #current_path, #current_host is > affected by visiting a page directly > rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:2]' # > Capybara::Session RackTest #current_url, #current_path, #current_host returns > to the app host when visiting a relative url > rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:3]' # > Capybara::Session RackTest #current_url, #current_path, #current_host is > affected by setting Capybara.app_host > rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:4]' # > Capybara::Session RackTest #current_url, #current_path, #current_host is > unaffected by following a relative link > rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:5]' # > Capybara::Session RackTest #current_url, #current_path, #current_host is > affected by following an absolute link > rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:6]' # > Cap
Processed: closing 1071309
Processing commands for cont...@bugs.debian.org: > close 1071309 1.8.4-4 Bug #1071309 [src:gajim] gajim: FTBFS: test_get_first_grapheme fails Marked as fixed in versions gajim/1.8.4-4. Bug #1071309 [src:gajim] gajim: FTBFS: test_get_first_grapheme fails Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1071309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071400: marked as done (src:specutils: unsatisfied build dependency in testing: python3-spectral-cube)
Your message dated Mon, 10 Jun 2024 09:48:15 +0200 with message-id and subject line Closing outdated bug has caused the Debian Bug report #1071400, regarding src:specutils: unsatisfied build dependency in testing: python3-spectral-cube 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.) -- 1071400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: specutils Version: 1.14.0-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- With the migration of specreduce, all build dependencies of specutils are now satisified again, and in https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html specutils doesn't appear anymore. Therefore this bug can be closed. Best Ole--- End Message ---
Processed: Bug#1064720 marked as pending in ruby-capybara
Processing control commands: > tag -1 pending Bug #1064720 [src:ruby-capybara] ruby-capybara: FTBFS: ERROR: Test "ruby3.1" failed: NoMethodError: Ignoring request to alter tags of bug #1064720 to the same tags previously set -- 1064720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1064720 marked as pending in ruby-capybara
Processing control commands: > tag -1 pending Bug #1064720 [src:ruby-capybara] ruby-capybara: FTBFS: ERROR: Test "ruby3.1" failed: NoMethodError: Ignoring request to alter tags of bug #1064720 to the same tags previously set -- 1064720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071902: marked as done (rust-event-listener: event-listener v5 is considered buggy)
Your message dated Mon, 10 Jun 2024 09:03:50 +0200 with message-id <171800303034.255930.17606408195508401...@auryn.jones.dk> and subject line Re: rust-event-listener: event-listener v5 is considered buggy has caused the Debian Bug report #1071902, regarding rust-event-listener: event-listener v5 is considered buggy 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.) -- 1071902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-event-listener Version: 2.5.3-4 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 rust-event-listener v5 is considered buggy upstream, and therefore unsuitable for a stable Debian release. Please do *not* release this to Debian unstable, as it will cause at least anything depending on async-lock to be impossible to resolve its dependency chain. https://github.com/smol-rs/async-lock/issues/81 -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmZSOQAACgkQLHwxRsGg ASHLRg/9GYKK/Ef2K9e3D/ARSiUVyMY08zIrWer4zlQ+y2jBTJzXxfJu/AIAmx+p fDbwOiVheuQ+OcTphy2gepYAaIUmyTVM7Y9LPgMqwDQ84wYTCUvR8Fd/UvZ32G93 Qtz/fYP37Xy9Cl0dNxEaun/6wysUkYAWrD/e+1zQsAwVrTqgGr4Ayx0XShP4IRG/ 27FQ2NLGs23sRZYQ7C45uJOdZiQHXXTpntN5LyWflHcbQwamB98yqF/9Ncs3EGJp 1JjJGpy2MkAjY9ic5Cqh5mmOyUjCCOnf7k4XIgUh6jhr6ler8Iv+KQ/1LNgQq8GV mVSrrBY6UaaNqJfGywYzpt/EZqi0qnZl5MhmCJeyWdWgFINk5z6njiTnsQF0bH5o V1/SxvKvxYkzyCsF5wqNUDJvUjNwzd4BDZWJuBnTHqYEZ+szm8aEpEenuG4ouLpu NDCj+CbG/b2/dV8Pzy+igUBuQH1BXyf4q9ghQ/qgRiGPbjoRHEgiFLLranRfx8yu vFCkqcnTf5vboXMwTbH5WFxd2goFRorVmrS6aq3pj2sz3FWalqr/i/b+w/znfA7n yGSm5+C6HmL7JPLuMzFEVjP/ICUgwzdCFKADKIaiE3SbKuOoQIXz5Ck4b13q7Zv9 Xvbh+BsA+zBqAdmBCcn1OXZJOSV8Ho13mxR2x3jxozBKvI0XyAQ= =LybZ -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Quoting Jonas Smedegaard (2024-05-25 21:16:18) > rust-event-listener v5 is considered buggy upstream, and therefore > unsuitable for a stable Debian release. > > Please do *not* release this to Debian unstable, as it will cause at > least anything depending on async-lock to be impossible to resolve its > dependency chain. > > https://github.com/smol-rs/async-lock/issues/81 The issue is resolved upstream by now. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature --- End Message ---
Bug#1072366: marked as done (libndp: CVE-2024-5564)
Your message dated Mon, 10 Jun 2024 07:02:27 + with message-id and subject line Bug#1072366: fixed in libndp 1.8-2 has caused the Debian Bug report #1072366, regarding libndp: CVE-2024-5564 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.) -- 1072366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libndp Version: 1.8-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 1.6-1 Hi, The following vulnerability was published for libndp. CVE-2024-5564[0]: | A vulnerability was found in libndp. This flaw allows a local | malicious user to cause a buffer overflow in NetworkManager, | triggered by sending a malformed IPv6 router advertisement packet. | This issue occurred as libndp was not correctly validating the route | length information. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-5564 https://www.cve.org/CVERecord?id=CVE-2024-5564 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: libndp Source-Version: 1.8-2 Done: Florian Ernst We believe that the bug you reported is fixed in the latest version of libndp, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Florian Ernst (supplier of updated libndp 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, 10 Jun 2024 08:11:09 +0200 Source: libndp Architecture: source Version: 1.8-2 Distribution: unstable Urgency: high Maintainer: Florian Ernst Changed-By: Florian Ernst Closes: 1072366 Changes: libndp (1.8-2) unstable; urgency=high . * [a6136d6] add debian/patches/CVE-2024-5564.patch from upstream fixing CVE-2024-5564 (Closes: #1072366) * [5119f5e] debian/rules: drop now-complete dh_strip --dbgsym-migration * [4d590c2] debian/copyright: update debian/ copyright years * [3d049d7] debian/control: Standards-Version 4.7.0 (no further changes required) Checksums-Sha1: 53da38f54a87fbb6acd3ee721436a46a265c9359 2027 libndp_1.8-2.dsc ec694003b9b75d7249e3c0654bf2c34b0db57d38 5236 libndp_1.8-2.debian.tar.xz 5480c76493d639d1bc7f7d81e50cfafe8b0fdbf2 7272 libndp_1.8-2_amd64.buildinfo Checksums-Sha256: 47cd371905286c289ed59678278ae434404a5b7869c4c50c82f58fc356e881b6 2027 libndp_1.8-2.dsc c2d3bb63291ff62a0368dcc23383018f18dce8aa873d478606676a50b19d0acb 5236 libndp_1.8-2.debian.tar.xz a54a0f9548ec007cbebcfba42dfa764c683017debc1a754d8bac3b5ef00afb61 7272 libndp_1.8-2_amd64.buildinfo Files: c6990674ad79a5ef8b725b8e112012d9 2027 net optional libndp_1.8-2.dsc bcfd4e207c3247dd18d4553db3e0e0d6 5236 net optional libndp_1.8-2.debian.tar.xz 180539840fff884bdcf4817f45bf4e99 7272 net optional libndp_1.8-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEBn03XtJwVyplJ26xBjdBuvXdHs4FAmZmmhgACgkQBjdBuvXd Hs5A0w//QGxcT2M9burngsEeVrMlswBGRvYECJKqWiAIL2kJlXwaBWyR7zQ5YY3N ox/n55qciX/P6jmmjoZlxxt4xS0nYe8znV7nPVSGjzLuR+YTWdGDifLXDYrN8HGY ZHR+Ty15xVJEFUJa+F6Kx/IVATfDOFb3326idv6S39rOFUVdtKjtwN3PjzZhDAMS 33qFYTB+L4ahjq7i2Y/oTfEsbPSSq28qRwilDwyTXGVN+rnU7Cc6F0O8P6QRW74y 6xN5Mju8hnIKSf14Cv90HPVh0vlDq7DCLd/3Z+LABxMaTTi5xd44rWhCJm2xBaLm 9soQDOuf8O8hwpZGicgfryIun8UTidI16zgpzBvl1rIsHS2R/E4snPYOnDXnJ2DU W1N1TUGz388mOE1id43LZb62+aZ+LZr81O4wvfw2rVZbCq29yZ3uJeEb6ecSouxj TIWBCxIMT7w6fBmzeWCeBNjATRLW9lcpbSa1U9HxQX2lJtfrI7Jgj32KzMjxchhX Nn7oRYEsnGZawB8MQWB7a/Pu9AMrxPqWyqEhupE+4ivyKAdQbJCRrUvO9pLKnMFF ub8yTpeck19Iq5bYHXHyDn2nkmr3MW0zysUjwHcrvgjMNBgjh6lmUmsyGHHrhcDz ZZVtHOjCJMPT5byhgLvoA2luun3Bs/ESVOpinkORGU+U7sO/SA8= =mR6v -END PGP SIGNATURE- pgpUH8QsjY2h6.pgp Description: PGP signature --- End Message ---
Bug#1063026: marked as done (Upcoming gtk update)
Your message dated Mon, 10 Jun 2024 07:02:18 + with message-id and subject line Bug#1063026: fixed in helvum 0.5.1+20240328-2 has caused the Debian Bug report #1063026, regarding Upcoming gtk update 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.) -- 1063026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: helvum Version: 0.5.1-1 Severity: normal X-Debbugs-Cc: werdah...@riseup.net -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, upstream released a new gtk-rs this weekend. I will upload it to experimental next weekend; once all affected source packages build fine with the newer gtk I will upload it to unstable. Since this is a a minor release patching should be possible; if this works a patch will reach you then. best, werdahias - -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-2-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: OpenRC (via /run/openrc), PID 1: init LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQJJBAEBCgAzFiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmW/m1cVHHdlcmRhaGlh c0ByaXNldXAubmV0AAoJEBi9EGs7bFR1l3YQALSdWXhQwqhU6pzYpxPf9pwfN9lR pM6Od9BxTZbHfJjOfkJ9vc10d1HSZrfE3mS526tbNmVrEtrXiSMsIvoVbNsI8AfS rpnbskvYv2WcHD2bLbyiw/nsvzsH5wySFCHMkIHF0pHzq1oDX3l3BhDlEM++6fdW y3UbYFTTD9NoN5XYpoTFlmFyKKXHC6P/DjUe0cqnOh1K0sTaOMkb6PHhoc6gCb52 FQ9KxC9jJEISUypzz94O7NviD6wzsU6rritMbYHp3jpNMc9gJX35zhf+epoRBtLD umpW6HrgkCJ58h2P+snP0edDfPtBZn93r/N1P83QZz9lQpnu7+2o/5AvCU1GAp50 g4ZxXn5cWPq52hPZ3dgp9eHwF5wIsegOOPx8aJ6yXsoM/8Uqhsd6Z0j6lvtYbOC9 A1ntKwpwGt/CrX+rF40oFAQDQvsz7ZW3Vzkjx8y/mgcYjybRuEbqBHg2X7/R7H/d 42xpXVJcsOh95Oh8ikNm3ROeZyhdlbty9YpMRZ/ZdgKFpY21gz8ljhvHiZkTUJUE JcYmO8sMVYsaZ7Y7nSO6LPzFPGMHDRQ4E06DLmX73uVHH8VPMd/MLrJ2mRYBmMWY KHU/bFZ4gRC8841Cz6ZN6jGHMT77o/gRpFgQi5xQ728zpzz8/7K5iMvyBPaiZbVR nA2nj8HsYZd7Jai4 =uARj -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: helvum Source-Version: 0.5.1+20240328-2 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of helvum, 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 1063...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated helvum 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, 10 Jun 2024 08:22:26 +0200 Source: helvum Architecture: source Version: 0.5.1+20240328-2 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 1063026 Changes: helvum (0.5.1+20240328-2) unstable; urgency=medium . * re-release targeted unstable; closes: bug#1063026, thanks to Jeremy Bícha * update copyright info: update coverage Checksums-Sha1: d5b2bbde52530a8a666f84ba3e3aba229c96edfe 2255 helvum_0.5.1+20240328-2.dsc 97f37d6107c8bfd2be6ede1603bf3d6dcc75fafc 19452 helvum_0.5.1+20240328-2.debian.tar.xz Checksums-Sha256: 558de77676a73908fa15ea5ce94fbb784da202f49f9aedb329b148feaae71ad5 2255 helvum_0.5.1+20240328-2.dsc 3db1e39945b1a492e800cfbe42322c39f9cf23d1023938bc1d7ea290fa61253f 19452 helvum_0.5.1+20240328-2.debian.tar.xz Files: 74f8df48f21f5afba68c04a1c10a44f7 2255 sound optional helvum_0.5.1+20240328-2.dsc 2f2e589bd237429c9bbb8880c31fcc95 19452 sound optional helvum_0.5.1+20240328-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmZmnxMACgkQLHwxRsGg ASEpvA//aZfZYgoxo8mw53rj6Xu+8CgBYvl7ZZ1HYfZFJPeS+T0T6JTtXNwR2OD9 5ehqK1WO1h/hwUPDBVEmASMeYb9cOuYUaFM4VOhn9SxIge+ioEAseg/OBjF8jJV7 0XUsFuFsTlolbyZZwj3CZqEluExpJhguAYaq/vk/sE4FP0Z7K5tHCE5ZLSw0/lwn jcZT3qUlT/gyPTGRFoWHap0pA8TCsDiO/gk5sORzAQB+nQdfGh+0U5GmgVqH+CjB pbu/1JyRzxbKrAR9ZK9Hbie2vMFgONT+NBUM3tEXF8LFhVwjglrMNhkhKDlUM7C/ DNn+5+ueCrTy/WhvEsO4X/ANPvJiHNiaIqvNfGvb2oXiaCIMpNHAX/Au5ojJcmNa kHSz5dC4MBgxKCxNk5RqBAbIFeQ3xase/Q/78rcSVE5IgdsNPxS9JwKU9gZQ65ar CATPQq+EgPa8bhaPr8
Processed: Re: Bug#1072682: luametatex: context 2024.04 and luametatex 2.11 no longer build PDF via Pandoc. (+ workaround)
Processing control commands: > reassign -1 context Bug #1072682 [luametatex] luametatex: context 2024.04 and luametatex 2.11 no longer build PDF via Pandoc. (+ workaround) Bug reassigned from package 'luametatex' to 'context'. No longer marked as found in versions luametatex/2.11.02+ds-4. Ignoring request to alter fixed versions of bug #1072682 to the same values previously set > severity -1 grave Bug #1072682 [context] luametatex: context 2024.04 and luametatex 2.11 no longer build PDF via Pandoc. (+ workaround) Severity set to 'grave' from 'important' -- 1072682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069532: marked as done (dune-istl: FTBFS on armhf: umfpack.hh:106:27: error: cannot convert ‘long int*’ to ‘const int64_t*’ {aka ‘const long long int*’})
Your message dated Mon, 10 Jun 2024 06:49:01 +
with message-id
and subject line Bug#1069532: fixed in dune-istl 2.9.0-3
has caused the Debian Bug report #1069532,
regarding dune-istl: FTBFS on armhf: umfpack.hh:106:27: error: cannot convert
‘long int*’ to ‘const int64_t*’ {aka ‘const long long int*’}
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.)
--
1069532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dune-istl
Version: 2.9.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf
Hi,
During a rebuild of all packages in sid, your package failed to build
on armhf.
Relevant part (hopefully):
> cd /<>/build/dune/istl/paamg/test && /usr/bin/c++ -DENABLE_MPI=1
> -DENABLE_SUITESPARSE=1 -DENABLE_SUPERLU=1 -DHAVE_CONFIG_H
> -DMYAMG="Dune::Amg::AMG" -I/<>/build
> -I/<> -isystem /usr/include/suitesparse -isystem
> /usr/include/superlu -isystem /usr/lib/arm-linux-gnueabihf/openmpi/include
> -isystem /usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi -std=c++17 -g
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time
> -D_FORTIFY_SOURCE=2 -fPIE -MD -MT
> dune/istl/paamg/test/CMakeFiles/pthreadamgtest.dir/pthreadamgtest.cc.o -MF
> CMakeFiles/pthreadamgtest.dir/pthreadamgtest.cc.o.d -o
> CMakeFiles/pthreadamgtest.dir/pthreadamgtest.cc.o -c
> /<>/dune/istl/paamg/test/pthreadamgtest.cc
> In file included from /<>/dune/istl/paamg/amg.hh:17,
> from
> /<>/dune/istl/paamg/test/pthreadamgtest.cc:24:
> /<>/dune/istl/umfpack.hh: In instantiation of ‘static void
> Dune::UMFPackMethodChooser::symbolic(A ...) [with A = {int, int, long
> int*, long int*, double*, void**, double*, double*}]’:
> /<>/dune/istl/umfpack.hh:545:23: required from ‘void
> Dune::UMFPack::decompose() [with M =
> Dune::BCRSMatrix >]’
> /<>/dune/istl/umfpack.hh:459:7: required from ‘void
> Dune::UMFPack::setMatrix(const Matrix&) [with M =
> Dune::BCRSMatrix >; Matrix =
> Dune::BCRSMatrix >]’
> /<>/dune/istl/umfpack.hh:270:7: required from
> ‘Dune::UMFPack::UMFPack(const Matrix&, int, bool) [with M =
> Dune::BCRSMatrix >; Matrix =
> Dune::BCRSMatrix >]’
> /<>/dune/istl/paamg/amg.hh:658:18: required from ‘static
> Dune::Amg::DirectSolverSelector::Solver Dune::Amg::DirectSolverSelector::umfpack>::type*
> Dune::Amg::DirectSolverSelector::Solver Dune::Amg::DirectSolverSelector::umfpack>::create(const M&,
> bool, bool) [with M = Dune::BCRSMatrix >;
> Matrix = Dune::BCRSMatrix >; Vector =
> Dune::BlockVector >; type =
> Dune::UMFPack > >]’
> /<>/dune/istl/paamg/amg.hh:683:40: required from ‘static
> Dune::Amg::DirectSolverSelector::DirectSolver*
> Dune::Amg::DirectSolverSelector::create(const Matrix&, bool,
> bool) [with Matrix = Dune::BCRSMatrix >;
> Vector = Dune::BlockVector >; DirectSolver =
> Dune::UMFPack > >]’
> /<>/dune/istl/paamg/amg.hh:745:51: required from ‘void
> Dune::Amg::AMG::createHierarchies(C&, const
> std::shared_ptr&, const PI&) [with C = const
> Dune::Amg::CoarsenCriterion 1, 1> >, Dune::Amg::FirstDiagonal> >; M =
> Dune::MatrixAdapter >,
> Dune::BlockVector >,
> Dune::BlockVector > >; X =
> Dune::BlockVector >; S =
> Dune::SeqSSOR >,
> Dune::BlockVector >,
> Dune::BlockVector > >; PI =
> Dune::Amg::SequentialInformation; A =
> std::allocator > >]’
> /<>/dune/istl/paamg/amg.hh:448:24: required from
> ‘Dune::Amg::AMG::AMG(const Operator&, const C&, const
> SmootherArgs&, const PI&) [with C =
> Dune::Amg::CoarsenCriterion 1, 1> >, Dune::Amg::FirstDiagonal> >; M =
> Dune::MatrixAdapter >,
> Dune::BlockVector >,
> Dune::BlockVector > >; X =
> Dune::BlockVector >; S =
> Dune::SeqSSOR >,
> Dune::BlockVector >,
> Dune::BlockVector > >; PI =
> Dune::Amg::SequentialInformation; A =
> std::allocator > >; Operator =
> Dune::MatrixAdapter >,
> D
Bug#1072763: marked as done (node-follow-redirects: FTBFS: autobuilder hangs)
Your message dated Mon, 10 Jun 2024 03:35:24 + with message-id and subject line Bug#1072763: fixed in node-follow-redirects 1.15.6+~1.14.4-2 has caused the Debian Bug report #1072763, regarding node-follow-redirects: FTBFS: autobuilder hangs 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.) -- 1072763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-follow-redirects Version: 1.15.6+~1.14.4-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure --buildsystem=nodejs Link node_modules/@types/follow-redirects -> ../../types-follow-redirects dh_auto_build --buildsystem=nodejs No build command found, searching known files No build command found, searching known files dh_auto_test --buildsystem=nodejs ln -s ../. node_modules/follow-redirects /bin/sh -ex debian/tests/pkg-js/test + mocha follow-redirects undefined http.get with string and callback - redirect (47ms) undefined http.get with URL object and callback - redirect undefined http.get with options object and callback - redirect undefined http.get with string and callback - no redirect undefined http.get with options object and callback - no redirect undefined http.get with host option and callback - redirect undefined http.get to IPv4 address undefined http.get to IPv6 address undefined http.get to bracketed IPv4 address undefined http.get to bracketed IPv4 address specified as host undefined http.get to bracketed IPv4 address specified as hostname undefined http.get to bracketed hostname undefined http.get redirecting to IPv4 address undefined http.get redirecting to IPv6 address undefined http.get redirecting to bracketed IPv4 address undefined http.get redirecting to bracketed hostname undefined http.get with response event undefined http.get with relative URL path undefined redirect to URL with fragment undefined should return with the original status code if the response does not contain a location header undefined should emit connection errors on the returned stream undefined should emit socket events on the returned stream undefined should emit connect events on the returned stream undefined emits an error on redirects with an invalid location undefined emits an error when the request fails for another reason undefined should destroy responses undefined should honor query params in redirects undefined should allow aborting undefined should provide connection undefined should provide flushHeaders undefined should provide getHeader undefined should provide removeHeader undefined should provide setHeader undefined should provide setNoDelay undefined should provide setSocketKeepAlive undefined should provide setTimeout undefined should provide socket undefined should wait for an explicit call to end undefined errors on write after end undefined should support writing into request stream without redirects undefined should support writing into request stream with redirects undefined should support piping into request stream without redirects undefined should support piping into request stream with redirects undefined should support piping into request stream with explicit Content-Length without redirects undefined should support piping into request stream with explicit Content-Length with redirects undefined keeps the header when redirected from HTTP to HTTPS undefined drops the header when redirected from HTTPS to HTTP Tue, 04 Jun 2024 11:17:38 GMT express deprecated res.redirect(url, status): Use res.redirect(status, url) instead at test/util.js:9:18 undefined passes the redirect status code to beforeRedirect undefined passes the request method to beforeRedirect undefined passes the request headers to beforeRedirect undefined passes the request URL to beforeRedirect undefined keeps the header when redirected from HTTP to HTTPS undefined drops the header when redirected from HTTPS to HTTP undefined passes the redirect status code to beforeRedirect undefined passes the request method to beforeRedirect undefined passes the request headers to beforeRedir
Processed: Bug#1072763 marked as pending in node-follow-redirects
Processing control commands: > tag -1 pending Bug #1072763 [src:node-follow-redirects] node-follow-redirects: FTBFS: autobuilder hangs Added tag(s) pending. -- 1072763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1072857: dput: Incorrect delayed argument: ValueError: delayed days value must be a decimal integer:
Processing control commands: > tags -1 confirmed Bug #1072857 [dput] dput: Incorrect delayed argument: ValueError: delayed days value must be a decimal integer: Added tag(s) confirmed. -- 1072857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072107: marked as done (libarchive: CVE-2024-26256)
Your message dated Sun, 09 Jun 2024 22:32:09 + with message-id and subject line Bug#1072107: fixed in libarchive 3.6.2-1+deb12u1 has caused the Debian Bug report #1072107, regarding libarchive: CVE-2024-26256 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.) -- 1072107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libarchive Version: 3.7.2-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 3.6.2-1 Hi, The following vulnerability was published for libarchive. CVE-2024-26256[0]: | libarchive Remote Code Execution Vulnerability If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-26256 https://www.cve.org/CVERecord?id=CVE-2024-26256 [1] https://github.com/advisories/GHSA-2jc9-36w4-pmqw [2] https://github.com/libarchive/libarchive/commit/eb7939b24a681a04648a59cdebd386b1e9dc9237 Regards, Salvatore --- End Message --- --- Begin Message --- Source: libarchive Source-Version: 3.6.2-1+deb12u1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of libarchive, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated libarchive 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 Jun 2024 16:38:00 +0200 Source: libarchive Architecture: source Version: 3.6.2-1+deb12u1 Distribution: bookworm-security Urgency: high Maintainer: Peter Pentchev Changed-By: Salvatore Bonaccorso Closes: 1068047 1072107 Changes: libarchive (3.6.2-1+deb12u1) bookworm-security; urgency=high . [ Peter Pentchev ] * Add the robust-error-reporting upstream patch. Closes: #1068047 . [ Salvatore Bonaccorso ] * fix: OOB in rar e8 filter (CVE-2024-26256) (Closes: #1072107) * fix: OOB in rar delta filter * fix: OOB in rar audio filter Checksums-Sha1: e6e5f6b4c5fed869bf40f1a0113cf5684c0b02c5 2695 libarchive_3.6.2-1+deb12u1.dsc 35c971132e4ecb1679418d1713e328e415aac569 5213196 libarchive_3.6.2.orig.tar.xz 9c5ae31f3a3850ea301c1db8ccbd312f01e572ff 659 libarchive_3.6.2.orig.tar.xz.asc 07d4afb2b8e42d113a1d2732ef81df40d949931b 26708 libarchive_3.6.2-1+deb12u1.debian.tar.xz Checksums-Sha256: 48516b52965a717d939b65493b7b148b1620045e4c69e4ace2caa199f9ec6b8d 2695 libarchive_3.6.2-1+deb12u1.dsc 9e2c1b80d5fbe59b61308fdfab6c79b5021d7ff4ff2489fb12daf0a96a83551d 5213196 libarchive_3.6.2.orig.tar.xz c6f1cdc29571dd6b09d3776ae98404a81b2dbe970a2bd9dc0bd9ed183ca49b71 659 libarchive_3.6.2.orig.tar.xz.asc 41de35dcf0e1b69654ecdb43de18d3f8ba531340b4a3e0ba2d822903623e 26708 libarchive_3.6.2-1+deb12u1.debian.tar.xz Files: 9ddad72db13414cb29f3b880e4514662 2695 libs optional libarchive_3.6.2-1+deb12u1.dsc 72cbb3c085624c825f627bfc8f52ce53 5213196 libs optional libarchive_3.6.2.orig.tar.xz fce14a9cae1725d38f714aa23a48e7da 659 libs optional libarchive_3.6.2.orig.tar.xz.asc 3b8b3bea2e56e1fe7d21e1083016d8f6 26708 libs optional libarchive_3.6.2-1+deb12u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmZchLFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EIxMQAIVQztvCD+HoX2yDSqSgxOXycQ+mm6TJ hAaY/9GgJOghFUY+riDwvUi8e0hTG1BDuuUPp6Qn1mGxWkR5+oS39Wvn/ecoZgA1 Sox5SiyUYZ6sjlL/mBLms+cRWrSoIsEKFxtZctWSgvTlB7Azkv4gF4fGYcsENJdq cgBmJoh7wGYquSMggkXxUoL+tfmWJlWe2CMhU+N7RvRqHhSeCn/zVycEDsH1VHgE 3/KbqAGdoqJ6jazFkou3J/DnZuZxX+CVDp6QFaKldmdD+A5fEsXT86lzDtM2y1LA J06SUDiENJ913kmYhH0k3qdkUnoOPKkJyLu5s4YZn4rd2KOsbRxwqeEMcRbe+oIK 0ktnTUDLRZfZpDClxY1jNPrxIh8IUJ0OWN6W1vIJhyzAQ0raj7qzAKLXc8aHyWv/ qh9JBtKsZWQh9Dx72LMiNt655M0z4fpi0aWuBa7r9VObXJcqvKLXdzN8eTAJd2SU Idy0qAUVdCpTVNrxONfysVxYEQV4/c+EQ18Yp
Bug#1072593: marked as done (appmenu-gtk-module: FTBFS: dh_install: error: missing files, aborting)
Your message dated Sun, 09 Jun 2024 20:49:11 + with message-id and subject line Bug#1072593: fixed in appmenu-gtk-module 24.05-1 has caused the Debian Bug report #1072593, regarding appmenu-gtk-module: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1072593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072593 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:appmenu-gtk-module Version: 24.02-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem=meson dh_update_autotools_config -O--buildsystem=meson dh_autoreconf -O--buildsystem=meson dh_auto_configure -O--buildsystem=meson cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 The Meson build system Version: 1.4.1 Source dir: /<> Build dir: /<>/obj-x86_64-linux-gnu Build type: native build Project name: appmenu-gtk-module Project version: 24.02 C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-25) 13.2.0") C linker for the host machine: cc ld.bfd 2.42 Host machine cpu family: x86_64 Host machine cpu: x86_64 Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1 Run-time dependency gio-unix-2.0 found: YES 2.80.2 Run-time dependency gtk+-2.0 found: YES 2.24.33 Run-time dependency gtk+-3.0 found: YES 3.24.42 Did not find CMake 'cmake' Found CMake: NO Run-time dependency systemd found: NO (tried pkgconfig and cmake) Configuring gtkdocentities.ent using configuration Build targets in project: 5 appmenu-gtk-module 24.02 User defined options buildtype : plain libdir: lib/x86_64-linux-gnu localstatedir : /var prefix: /usr sysconfdir: /etc wrap_mode : nodownload python.bytecompile: -1 Found ninja-1.12.1 at /usr/bin/ninja dh_auto_build -O--buildsystem=meson cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j2 -v [1/28] cc -Ilib/libappmenu-gtk2-parser.so.0.p -Ilib -I../lib -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/x86_64-linux-gnu -I/usr/include/webp -I/usr/include/atk-1.0 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu11 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ lib/libappmenu-gtk2-parser.so.0.p/unity-gtk-action.c.o -MF lib/libappmenu-gtk2-parser.so.0.p/unity-gtk-action.c.o.d -o lib/libappmenu-gtk2-parser.so.0.p/unity-gtk-action.c.o -c ../lib/unity-gtk-action.c In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37, from /usr/include/gtk-2.0/gtk/gtkwidget.h:36, from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35, from /usr/include/gtk-2.0/gtk/gtkbin.h:35, from /usr/include/gtk-2.0/gtk/gtkwindow.h:36, from /usr/include/gtk-2.0/gtk/gtkdialog.h:35, from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:33, from ../lib/unity-gtk-menu-item-private.h:23, from ../lib/unity-gtk-action-private.h:42, from ../lib/unity-gtk-action.c:20: /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is deprecated [-Wdeprecated-declarations] 236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags); | ^~~~ In file included from /usr/include/glib-2.0/gobject/gobject.h:26, from /usr/include/glib-2.0/gobject/gbinding.h:31, from /usr/include/glib-2.0/glib-object.h:24, from ../lib/unity-gtk-action-private.h:23: /usr/include/glib-2.0/gobject/gtype.h:725:1: note: declared he
Processed: Bug#1072593 marked as pending in appmenu-gtk-module
Processing control commands: > tag -1 pending Bug #1072593 [src:appmenu-gtk-module] appmenu-gtk-module: FTBFS: dh_install: error: missing files, aborting Added tag(s) pending. -- 1072593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072593 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066694: marked as done (netdiag: FTBFS: getservent.c:121:38: error: implicit declaration of function ‘atoi’ [-Werror=implicit-function-declaration])
Your message dated Sun, 09 Jun 2024 19:51:56 + with message-id and subject line Bug#1066694: fixed in netdiag 1.2-1.3 has caused the Debian Bug report #1066694, regarding netdiag: FTBFS: getservent.c:121:38: error: implicit declaration of function ‘atoi’ [-Werror=implicit-function-declaration] 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.) -- 1066694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netdiag Version: 1.2-1.2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wl,-z,relro -Wl,-z,now > -I/usr/include/ncurses -g -DSNVERSION=3.8 -Wdate-time -D_FORTIFY_SOURCE=2 -c > -o win_show_stat.o win_show_stat.c > tally_label.c:13:1: warning: return type defaults to ‘int’ [-Wimplicit-int] >13 | tally_label ( struct Tally *Now_ts, WINDOW *win, int width, int > height ) > | ^~~ > In file included from /usr/include/netdb.h:27, > from inetprivate.h:13, > from getservent.c:45: > getservent.c: In function ‘sn_getservent’: > getservent.c:121:38: error: implicit declaration of function ‘atoi’ > [-Werror=implicit-function-declaration] > 121 | serv.s_port = htons((u_short)atoi(p)); > | ^~~~ > gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wl,-z,relro -Wl,-z,now > -I/usr/include/ncurses -g -DSNVERSION=3.8 -Wdate-time -D_FORTIFY_SOURCE=2 -c > -o statnetd.o statnetd.c > gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wl,-z,relro -Wl,-z,now > -I/usr/include/ncurses -g -DSNVERSION=3.8 -Wdate-time -D_FORTIFY_SOURCE=2 -c > -o itstime.o itstime.c > statnet.c:102:8: warning: type defaults to ‘int’ in declaration of ‘gen_all’ > [-Wimplicit-int] > 102 | static gen_all, gen_eth, gen_plip, gen_slip, gen_ppp, gen_loop, > gen_802 = 0; > |^~~ > statnet.c:102:17: warning: type defaults to ‘int’ in declaration of ‘gen_eth’ > [-Wimplicit-int] > 102 | static gen_all, gen_eth, gen_plip, gen_slip, gen_ppp, gen_loop, > gen_802 = 0; > | ^~~ > statnet.c:102:26: warning: type defaults to ‘int’ in declaration of > ‘gen_plip’ [-Wimplicit-int] > 102 | static gen_all, gen_eth, gen_plip, gen_slip, gen_ppp, gen_loop, > gen_802 = 0; > | ^~~~ > statnet.c:102:36: warning: type defaults to ‘int’ in declaration of > ‘gen_slip’ [-Wimplicit-int] > 102 | static gen_all, gen_eth, gen_plip, gen_slip, gen_ppp, gen_loop, > gen_802 = 0; > |^~~~ > statnet.c:102:46: warning: type defaults to ‘int’ in declaration of ‘gen_ppp’ > [-Wimplicit-int] > 102 | static gen_all, gen_eth, gen_plip, gen_slip, gen_ppp, gen_loop, > gen_802 = 0; > | ^~~ > statnet.c:102:55: warning: type defaults to ‘int’ in declaration of > ‘gen_loop’ [-Wimplicit-int] > 102 | static gen_all, gen_eth, gen_plip, gen_slip, gen_ppp, gen_loop, > gen_802 = 0; > | ^~~~ > statnet.c:102:65: warning: type defaults to ‘int’ in declaration of ‘gen_802’ > [-Wimplicit-int] > 102 | static gen_all, gen_eth, gen_plip, gen_slip, gen_ppp, gen_loop, > gen_802 = 0; > | > ^~~ > statnet.c
Processed: Re: nocache: diff for NMU version 1.1-1.1
Processing control commands: > tags 918316 - pending Bug #918316 [src:nocache] nocache: FTBFS in sid Removed tag(s) pending. -- 918316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072119: marked as done (python-aiosmtpd: CVE-2024-34083)
Your message dated Sun, 09 Jun 2024 17:55:15 + with message-id and subject line Bug#1072119: fixed in python-aiosmtpd 1.4.6-1 has caused the Debian Bug report #1072119, regarding python-aiosmtpd: CVE-2024-34083 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.) -- 1072119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-aiosmtpd X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for python-aiosmtpd. CVE-2024-34083[0]: | aiosmptd is a reimplementation of the Python stdlib smtpd.py based | on asyncio. Prior to version 1.4.6, servers based on aiosmtpd accept | extra unencrypted commands after STARTTLS, treating them as if they | came from inside the encrypted connection. This could be exploited | by a man-in-the-middle attack. Version 1.4.6 contains a patch for | the issue. https://github.com/aio-libs/aiosmtpd/security/advisories/GHSA-wgjv-9j3q-jhg8 https://github.com/aio-libs/aiosmtpd/commit/b3a4a2c6ecfd228856a20d637dc383541fcdbfda (v1.4.6) If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-34083 https://www.cve.org/CVERecord?id=CVE-2024-34083 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: python-aiosmtpd Source-Version: 1.4.6-1 Done: Jakob Haufe We believe that the bug you reported is fixed in the latest version of python-aiosmtpd, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jakob Haufe (supplier of updated python-aiosmtpd 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, 09 Jun 2024 19:24:43 +0200 Source: python-aiosmtpd Architecture: source Version: 1.4.6-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Jakob Haufe Closes: 1066820 1072119 Changes: python-aiosmtpd (1.4.6-1) unstable; urgency=medium . [ Dale Richards ] * Team upload. * New upstream version 1.4.6 - CVE-2024-27305 - SMTP smuggling due to poor handling of non-standard line endings (Closes: #1066820) - CVE-2024-34083 - STARTTLS unencrypted command injection (Closes: #1072119) * d/watch: Update for new version format. * Update patch line offsets for new upstream version. * Add .gitattributes file to use CRLF line endings for aiosmtpd/tests/test_smtpsmuggling.py, so the checked out file matches the one in the upstream release tarball. * Bump Standards-Version to 4.7.0, no changes needed. Checksums-Sha1: 90e3401186c0cd0a417f33938cb96d3ea0bb588b 2252 python-aiosmtpd_1.4.6-1.dsc 3635c0bb5dd42c587753c7772a453977e7f643b7 153666 python-aiosmtpd_1.4.6.orig.tar.gz 40bb6ef9e9e8a4910c923c11e0837ac4658e06e2 6988 python-aiosmtpd_1.4.6-1.debian.tar.xz e135c2e5b99b03f0400a7cad6ce697e15c2bf6c0 7308 python-aiosmtpd_1.4.6-1_source.buildinfo Checksums-Sha256: bc94ce2679039eb6264cb0c7d15774f322a306db86544b0b979aacbef3cb6f33 2252 python-aiosmtpd_1.4.6-1.dsc 297d28b1b57da9debe5c0f8815fc153cd17605120a59f6200735a720445c5337 153666 python-aiosmtpd_1.4.6.orig.tar.gz 06b589629f1656b625ae19ba5861129abf97e92fd0643b4a83d9aad596e67dfa 6988 python-aiosmtpd_1.4.6-1.debian.tar.xz f3ceb954f351d2525a637b7f80a99dc9ee5191f8c5effa8c297ad2a51aae3739 7308 python-aiosmtpd_1.4.6-1_source.buildinfo Files: 883580e39e6c0957a3aa24826a0e2d93 2252 python optional python-aiosmtpd_1.4.6-1.dsc 6e8c6828395c3e5a37573e693d4c0e29 153666 python optional python-aiosmtpd_1.4.6.orig.tar.gz 0c6ea50cc2995c7e34042a6c064d11d7 6988 python optional python-aiosmtpd_1.4.6-1.debian.tar.xz 6ade3b26bd102fcffead9caa149696f7 7308 python optional python-aiosmtpd_1.4.6-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEe/X2rDZDH11A3BN6TPKyGPVNrj0FAmZl5aoRHHN1cjVyQGRl Ymlhbi5vcmcACgkQTPKyGPVNrj28QxAAr39as3Cw1yc2gIKYJbPdk+63ICAk
Processed: nocache: diff for NMU version 1.1-1.1
Processing control commands: > tags 918316 + patch pending Bug #918316 [src:nocache] nocache: FTBFS in sid Ignoring request to alter tags of bug #918316 to the same tags previously set -- 918316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1072857: dput: Incorrect delayed argument: ValueError: delayed days value must be a decimal integer:
Processing control commands: > severity -1 grave Bug #1072857 [dput] dput: Incorrect delayed argument: ValueError: delayed days value must be a decimal integer: Severity set to 'grave' from 'normal' -- 1072857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066560: marked as done (gmemusage: FTBFS: hash.c:42:13: error: implicit declaration of function ‘strcmp’ [-Werror=implicit-function-declaration])
Your message dated Sun, 09 Jun 2024 17:04:25 + with message-id and subject line Bug#1066560: fixed in gmemusage 0.2-11.1 has caused the Debian Bug report #1066560, regarding gmemusage: FTBFS: hash.c:42:13: error: implicit declaration of function ‘strcmp’ [-Werror=implicit-function-declaration] 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.) -- 1066560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gmemusage Version: 0.2-11 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -c -o hash.o hash.c > hash.c: In function ‘LookupProc’: > hash.c:42:13: error: implicit declaration of function ‘strcmp’ > [-Werror=implicit-function-declaration] >42 | if ( !strcmp ( pi -> procname , name ) ) > | ^~ > hash.c:12:1: note: include ‘’ or provide a declaration of ‘strcmp’ >11 | #include "common.h" > +++ |+#include >12 | > hash.c: In function ‘addProc’: > hash.c:70:10: error: implicit declaration of function ‘exit’ > [-Werror=implicit-function-declaration] >70 | exit ( 1 ) ; > | ^~~~ > hash.c:12:1: note: include ‘’ or provide a declaration of ‘exit’ >11 | #include "common.h" > +++ |+#include >12 | > hash.c:70:10: warning: incompatible implicit declaration of built-in function > ‘exit’ [-Wbuiltin-declaration-mismatch] >70 | exit ( 1 ) ; > | ^~~~ > hash.c:70:10: note: include ‘’ or provide a declaration of ‘exit’ > hash.c:74:7: error: implicit declaration of function ‘strcpy’ > [-Werror=implicit-function-declaration] >74 | strcpy ( thisproc -> procname , procname ) ; > | ^~ > hash.c:74:7: note: include ‘’ or provide a declaration of ‘strcpy’ > hash.c:74:7: warning: incompatible implicit declaration of built-in function > ‘strcpy’ [-Wbuiltin-declaration-mismatch] > hash.c:74:7: note: include ‘’ or provide a declaration of ‘strcpy’ > hash.c:96:13: warning: incompatible implicit declaration of built-in function > ‘exit’ [-Wbuiltin-declaration-mismatch] >96 | exit ( 1 ) ; > | ^~~~ > hash.c:96:13: note: include ‘’ or provide a declaration of ‘exit’ > hash.c:101:7: warning: incompatible implicit declaration of built-in function > ‘strcpy’ [-Wbuiltin-declaration-mismatch] > 101 | strcpy ( thisproc -> procname , procname ) ; > | ^~ > hash.c:101:7: note: include ‘’ or provide a declaration of ‘strcpy’ > cc1: some warnings being treated as errors > make[1]: *** [: hash.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/gmemusage_0.2-11_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: gmemusage Source-Version: 0.2-11.1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of gmemusage, 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
Processed: Re: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
Processing control commands: > reopen 1072733 = Bug #1072733 [sherlock,python3-sherlock] sherlock has an undeclared file conflict on /usr/lib/python3/dist-packages/sherlock/__init__.py Bug 1072733 is not marked as done; doing nothing. -- 1072733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
Processing control commands:
> reopen 1072733 =
Bug #1072733 {Done: Thomas Goirand }
[sherlock,python3-sherlock] sherlock has an undeclared file conflict on
/usr/lib/python3/dist-packages/sherlock/__init__.py
Bug reopened
Ignoring request to alter fixed versions of bug #1072733 to the same values
previously set
--
1071007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071007
1072733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#918316: nocache: FTBFS in sid
Processing commands for cont...@bugs.debian.org: > # FTBFS with systemd 256+ > # (unless system has several Gbytes of RAM) > severity 918316 serious Bug #918316 [src:nocache] nocache: FTBFS in sid Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 918316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070388: marked as done (jupyterhub: CVE-2024-28233)
Your message dated Sun, 09 Jun 2024 15:34:28 + with message-id and subject line Bug#1070388: fixed in jupyterhub 5.0.0+ds1-1 has caused the Debian Bug report #1070388, regarding jupyterhub: CVE-2024-28233 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.) -- 1070388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jupyterhub X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for jupyterhub. CVE-2024-28233[0]: | JupyterHub is an open source multi-user server for Jupyter | notebooks. By tricking a user into visiting a malicious subdomain, | the attacker can achieve an XSS directly affecting the former's | session. More precisely, in the context of JupyterHub, this XSS | could achieve full access to JupyterHub API and user's single-user | server. The affected configurations are single-origin JupyterHub | deployments and JupyterHub deployments with user-controlled | applications running on subdomains or peer subdomains of either the | Hub or a single-user server. This vulnerability is fixed in 4.1.0. https://github.com/jupyterhub/jupyterhub/security/advisories/GHSA-7r3h-4ph8-w38g https://github.com/jupyterhub/jupyterhub/commit/e2798a088f5ad45340fe79cdf1386198e664f77f If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-28233 https://www.cve.org/CVERecord?id=CVE-2024-28233 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: jupyterhub Source-Version: 5.0.0+ds1-1 Done: Roland Mas We believe that the bug you reported is fixed in the latest version of jupyterhub, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roland Mas (supplier of updated jupyterhub 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, 09 Jun 2024 17:00:34 +0200 Source: jupyterhub Architecture: source Version: 5.0.0+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Roland Mas Closes: 1070388 Changes: jupyterhub (5.0.0+ds1-1) unstable; urgency=medium . * New upstream release. * Includes fix for "CVE-2024-28233", thanks to Moritz Mühlenhoff (Closes: #1070388). Checksums-Sha1: 07dde73b9dc8d8ba8115bf8062ab92662e9194d8 2388 jupyterhub_5.0.0+ds1-1.dsc ea9048ae0da411d07d7a9852c9c6835c64dbe0fe 10795616 jupyterhub_5.0.0+ds1.orig.tar.xz 0a1472ba2db47e56824ae66f2f9ee901d91610c6 5532 jupyterhub_5.0.0+ds1-1.debian.tar.xz c50725456617874482e0c0cdedf4a1dbdd9cc445 8545 jupyterhub_5.0.0+ds1-1_source.buildinfo Checksums-Sha256: 5d1570bce6749c36335eb39885344ff9561c2d0f3fb1330b22528d07783d2af7 2388 jupyterhub_5.0.0+ds1-1.dsc 81cdf0fc20b67999326f8b26120e3578d0c73254b3f47a5c90eb379de7c0af28 10795616 jupyterhub_5.0.0+ds1.orig.tar.xz 4462c69d42a925a592009894858788c94a4a4325bc27bf78664156974e0cf52b 5532 jupyterhub_5.0.0+ds1-1.debian.tar.xz 237115e03942c4970ab570d9a65135d68e26fbc1bbaef971d28950569dd60b9c 8545 jupyterhub_5.0.0+ds1-1_source.buildinfo Files: 7ad0fe0d6bb1fff8f16c5579cbcd5fc7 2388 python optional jupyterhub_5.0.0+ds1-1.dsc 2604371ab871b758623155f1eb8eec36 10795616 python optional jupyterhub_5.0.0+ds1.orig.tar.xz abeb47bb8c931ae8092007d914de656d 5532 python optional jupyterhub_5.0.0+ds1-1.debian.tar.xz 71b542e2b19573222b6dd2ef19eacb4e 8545 python optional jupyterhub_5.0.0+ds1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEtBU2D1kett1zr/uD0w3s0lmTIvwFAmZlxlkACgkQ0w3s0lmT IvyvUQ//T8ydH+uewVoXVyQSMMs/exltX5S9zJPG5wnJunAfcFrSCYKwB6v4bJw6 TNPo4rDKE0mpRoGgjQP/5CWhpgFkZuKbV4GwIcSGRzdtWoQSW+pUXvb1CW+Uz9LT ubd9+ItLVruwdaMIpA5UuQxSgURDDXbe8zrrH5D095llCOZwwBJwN67T7SUiyqKM c0sw8x8QLkujqbcEQG2/HD89ADygtodHExhYOmDdWq1gu7yLVe9y+hDGRPoWyTAs YCqB2Gu9NARMT/R1jhcT71bp04wpaUafknkTWPZwOh8AuSDXBE33TLm7BoTEdd/l 3u69UptPiY2ubbY8Tv1PixqKifC
Bug#1071857: marked as done (src:python-watson-developer-cloud: fails to migrate to testing for too long: uploader built arch:all binary)
Your message dated Sun, 09 Jun 2024 15:25:54 + with message-id and subject line Bug#1071857: fixed in python-watson-developer-cloud 8.0.0-1.1 has caused the Debian Bug report #1071857, regarding src:python-watson-developer-cloud: fails to migrate to testing for too long: uploader built arch:all binary 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.) -- 1071857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-watson-developer-cloud Version: 7.0.0-1 Severity: serious Control: close -1 8.0.0-1 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:python-watson-developer-cloud has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=python-watson-developer-cloud OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-watson-developer-cloud Source-Version: 8.0.0-1.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of python-watson-developer-cloud, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated python-watson-developer-cloud package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 25 May 2024 16:21:42 +0200 Source: python-watson-developer-cloud Architecture: source Version: 8.0.0-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Paul Gevers Closes: 1071857 Changes: python-watson-developer-cloud (8.0.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #1071857) Checksums-Sha1: 985a94e45a31aceaffd7323aa3ab711be09c645a 2036 python-watson-developer-cloud_8.0.0-1.1.dsc ae85270381bfe138fc6d49ebd0a2cfaf8b7e71db 3500 python-watson-developer-cloud_8.0.0-1.1.debian.tar.xz Checksums-Sha256: 331c52b616c227f6fbcb915b968e2ba9d216910f106e83c3d99b6a0a58232e5f 2036 python-watson-developer-cloud_8.0.0-1.1.dsc d82c18fdb9be3ca4b1b3b52f3572f49f52f3b922fda3e8efa4d49ef0a8deed66 3500 python-watson-developer-cloud_8.0.0-1.1.debian.tar.xz Files: edda7806017963e7acbb1ff8f96ee569 2036 python optional python-watson-developer-cloud_8.0.0-1.1.dsc 5bbb9daa10004ea3c5512e770371f8f0 3500 python optional python-watson-developer-cloud_8.0.0-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmZR9B4ACgkQnFyZ6wW9 dQpeTQf
Processed: block 1071982 with 1052028
Processing commands for cont...@bugs.debian.org: > block 1071982 with 1052028 Bug #1071982 [src:jupyterhub] FTBFS: help2man fails 1071982 was not blocked by any bugs. 1071982 was not blocking any bugs. Added blocking bug(s) of 1071982: 1052028 > thanks Stopping processing here. Please contact me if you need assistance. -- 1071982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: add bug fwd info
Processing commands for cont...@bugs.debian.org:
> forwarded 1067083 https://github.com/tuomasjjrasanen/python-uinput/issues/52
Bug #1067083 [src:python-uinput] python-uinput: FTBFS on arm{el,hf}:
libsuinput/src/suinput.c:48:28: error: ‘struct input_event’ has no member named
‘time’
Set Bug forwarded-to-address to
'https://github.com/tuomasjjrasanen/python-uinput/issues/52'.
> tags 1067083 +upstream
Bug #1067083 [src:python-uinput] python-uinput: FTBFS on arm{el,hf}:
libsuinput/src/suinput.c:48:28: error: ‘struct input_event’ has no member named
‘time’
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1067083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1072821: marked as done (wireshark: binNMUs revert t64 transition)
Your message dated Sun, 09 Jun 2024 13:39:37 + with message-id and subject line Bug#1072821: fixed in wireshark 4.2.5-2 has caused the Debian Bug report #1072821, regarding wireshark: binNMUs revert t64 transition 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.) -- 1072821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072821 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wireshark Version: 4.2.4-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=wireshark=amd64=4.2.5-1%2Bb1=1717834351=0 ... Description: libwireshark-dev - network packet dissection library -- development files libwireshark17 - network packet dissection library -- shared library libwiretap-dev - network packet capture library -- development files libwiretap14 - network packet capture library -- shared library libwsutil-dev - network packet dissection utilities library -- development files libwsutil15 - network packet dissection utilities library -- shared library tshark - network traffic analyzer - console version wireshark - network traffic analyzer - graphical interface wireshark-common - network traffic analyzer - common files wireshark-dev - network traffic analyzer - development tools Changes: wireshark (4.2.5-1+b1) sid; urgency=low, binary-only=yes . * Binary-only non-maintainer upload for amd64; no source changes. * Rebuild against Qt 6.6.2. ... debian/rules: ... ifneq ($(filter noble unstable testing trixie UNRELEASED,$(DEB_DISTRIBUTION)),) sed "$(CONTROL_IN_SED_CMD)" debian/control.t64.in > debian/control else sed "$(CONTROL_IN_SED_CMD)" debian/control.in > debian/control ... sid != unstable --- End Message --- --- Begin Message --- Source: wireshark Source-Version: 4.2.5-2 Done: Balint Reczey We believe that the bug you reported is fixed in the latest version of wireshark, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Balint Reczey (supplier of updated wireshark 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, 09 Jun 2024 11:49:52 +0200 Source: wireshark Built-For-Profiles: noudeb Architecture: source Version: 4.2.5-2 Distribution: sid Urgency: medium Maintainer: Balint Reczey Changed-By: Balint Reczey Closes: 1072821 Changes: wireshark (4.2.5-2) sid; urgency=medium . * debian/rules: Keep the t64 transition when targeting sid or oracular (Closes: #1072821) Checksums-Sha1: 3cfe7b2db7929432cb85fc388858b050a11c82a4 3462 wireshark_4.2.5-2.dsc 3c5aea56a6a136529a7964155e77b9efd19b3f02 83160 wireshark_4.2.5-2.debian.tar.xz 07d41060fb2d8635ab97672e4e20a324b6fe29a4 23754 wireshark_4.2.5-2_source.buildinfo Checksums-Sha256: aa1f766de08e4ad6b9aeedfd2a9a558600b1384234661df3307b61a38616854d 3462 wireshark_4.2.5-2.dsc f151565b859acf4f16abd5cb5db5cc524b82c0a507a12d9b8da047cc107e2d61 83160 wireshark_4.2.5-2.debian.tar.xz d2dac80d6a7a963c83da58c1c521335dcbaba27dd6f884b027c0f42a05d1244e 23754 wireshark_4.2.5-2_source.buildinfo Files: d962dd8285cc4799f0686c334bf11bd8 3462 net optional wireshark_4.2.5-2.dsc 683647e781d8b84e1285f237e206ab1d 83160 net optional wireshark_4.2.5-2.debian.tar.xz a47b27158a3cbd0c2831fea567b561cc 23754 net optional wireshark_4.2.5-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEI/PvTgXX55rLQUfDg6KBkWslS0UFAmZle+oACgkQg6KBkWsl S0Wrpw//Yaid3VmXZOBZgxfRJD27aK/LKuHVevzIctgVTImK32DzoaflPB0bLWK3 tkbTSxitcoWCZU/ayuTYaQrGQoqZpefJizdLqET5WiSMnW7+stqGpJe14x5vtqK+ 6Qf0BYLZknmaNho+HFyaR5vsyLzKVv/VSOhHvTCb0k3z1nOJrGmLgV3HbeEzIGne 1be3c6EW5R9DN5uYWJpNZ277sbdWKm/xBQ116Q2VEVrv/GWNFetqhX8n5o02DqMO ZyApE7lvzQJZYX6lNS31nI8Lfq78LBJNxhb4ma9YRXC2QenEeLXU9fp87gszQLXm JiCNbIb1bmLtw1YhqRMCphEyvq7+BtSve9d4YsFTG6vSgkSF52mgQqdUCfV3qIkP Lvg8kOZZA5pYnsJ8z4KSb0Q7mQ03hPBPndOLACW8YalF41XsSZfhSJy6d0GNOJTD t8A3LR4jaSPKV1SCUFQP77BIAuFbYBMgEtXgGJ+llZmJfo4vFLEO1+6R/uyLrHMg /1ngKm0wybZwnwP3jkSJV3Xr41Q36CcN43Hv5d4cMaWkUKl0351Dk4JqENE8EbRZ D1JhhkQ0rKHYqu91/iXMr77tBoC06D0j2GzBPZuhffCAaoS9USHiGsX8hJqiJ2Ht ReDkQPTd/ExUA3Nd3zh
Bug#1072843: marked as done (poppler: stopped to build Qt6 lib on i386 without coordination with reverse dependencies)
Your message dated Sun, 9 Jun 2024 08:40:30 -0400 with message-id and subject line Re: Bug#1072843: poppler: stopped to build Qt6 lib on i386 without coordination with reverse dependencies has caused the Debian Bug report #1072843, regarding poppler: stopped to build Qt6 lib on i386 without coordination with reverse dependencies 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.) -- 1072843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: poppler Version: 24.02.0-5 Severity: serious X-Debbugs-Cc: sramac...@debian.org poppler (24.02.0-5) unstable; urgency=medium . * Team upload * Stop building Qt6 library on i386 vs dak rm -Rn -b libpoppler-qt6-3t64 libpoppler-qt6-dev -a i386 W: -a/--architecture implies -p/--partial. Will remove the following packages from unstable: libpoppler-qt6-3t64 | 24.02.0-4 | i386 libpoppler-qt6-dev | 24.02.0-4 | i386 Maintainer: Debian freedesktop.org maintainers --- Reason --- -- Checking reverse dependencies... # Broken Build-Depends: photoqt: libpoppler-qt6-dev qpdfview: libpoppler-qt6-dev texworks: libpoppler-qt6-dev This needs coordination with reverse dependencies. The decision is also somewhat inconsistent. Why is support only dropped on i386 and not the other 32 bit architectures? Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- On Sat, Jun 8, 2024 at 4:33 PM Sebastian Ramacher wrote: > dak rm -Rn -b libpoppler-qt6-3t64 libpoppler-qt6-dev -a i386 > W: -a/--architecture implies -p/--partial. > Will remove the following packages from unstable: > > libpoppler-qt6-3t64 | 24.02.0-4 | i386 > libpoppler-qt6-dev | 24.02.0-4 | i386 > > Maintainer: Debian freedesktop.org maintainers > > > --- Reason --- > > -- > > Checking reverse dependencies... > # Broken Build-Depends: > photoqt: libpoppler-qt6-dev > qpdfview: libpoppler-qt6-dev > texworks: libpoppler-qt6-dev > > > This needs coordination with reverse dependencies. This was coordinated with reverse dependencies. Those apps are already intentionally not available on i386 in Unstable and Testing. https://bugs.debian.org/1068672 (at that time, there was only one reverse dependency) https://bugs.debian.org/1071513 https://bugs.debian.org/1071514 > The decision is also somewhat inconsistent. Why is support only dropped > on i386 and not the other 32 bit architectures? It is allowed to drop i386 support for Trixie since it is planned for i386 to no longer be a directly installable architecture. One major point of keeping i386 binaries around is to run legacy apps but there aren't legacy Qt6 poppler apps. Legacy apps would use older versions of Qt. That was also the position of Ubuntu which is unwilling to build Qt6 for i386. Dropping i386 from Debian allows Debian and Ubuntu to more easily share packaging. I'll file the last removal bug for libpoppler-qt6-3t64 and libpoppler-qt6-dev on i386 now. Thank you for pointing out that I missed that step. I'll close this bug since I believe the poppler packaging is ok. If followup is needed, I guess you can use the removal bug that I'll CC you on. Jeremy Bícha--- End Message ---
Bug#1072762: marked as done (node-eventsource: FTBFS: failing tests)
Your message dated Sun, 09 Jun 2024 12:05:55 + with message-id and subject line Bug#1072762: fixed in node-eventsource 2.0.2+~1.1.10-2 has caused the Debian Bug report #1072762, regarding node-eventsource: FTBFS: failing tests 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.) -- 1072762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-eventsource Version: 2.0.2+~1.1.10-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure --buildsystem=nodejs Link node_modules/@types/eventsource -> ../../types-eventsource dh_auto_build --buildsystem=nodejs No build command found, searching known files No build command found, searching known files dh_auto_test --buildsystem=nodejs ln -s ../debian/tests/test_modules/buffer-from node_modules/buffer-from ln -s ../. node_modules/eventsource /bin/sh -ex debian/tests/pkg-js/test + mocha --exit Parser undefined parses multibyte characters undefined parses empty lines with multibyte characters undefined parses one one-line message in one chunk undefined ignores byte-order mark undefined parses one one-line message in two chunks undefined parses two one-line messages in one chunk undefined parses one two-line message in one chunk undefined parses chopped up unicode data undefined parses really chopped up unicode data undefined accepts CRLF as separator undefined accepts CR as separator undefined delivers message with explicit event undefined allows removal of event listeners undefined ignores comments undefined ignores empty comments undefined does not ignore multilines strings undefined does not ignore multilines strings even in data beginning undefined causes entire event to be ignored for empty event field undefined parses relatively huge messages efficiently undefined parses a relatively huge message across many chunks efficiently (76ms) HTTP Request 1) passes cache-control: no-cache to server 2) sets request headers 3) does not set request headers that don't have a value undefined follows http 301 redirect undefined follows http 301 redirects, drops sensitive headers on origin change undefined causes error event when response is 301 with missing location undefined follows http 302 redirect undefined follows http 302 redirects, drops sensitive headers on origin change undefined causes error event when response is 302 with missing location undefined follows http 307 redirect undefined follows http 307 redirects, drops sensitive headers on origin change undefined causes error event when response is 307 with missing location undefined causes error event when response status is 401 undefined causes error event when response status is 403 undefined checks createConnection option Reconnection undefined is attempted when server is down undefined continuing attempts when server is down undefined is attempted when server goes down after connection undefined is attempted when the server responds with a 500 undefined is stopped when server goes down and eventsource is being closed (103ms) undefined is not attempted when server responds with non-200 and non-500 (node:2252609) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [Server]. Use emitter.setMaxListeners() to increase limit (Use `node --trace-warnings ...` to show where the warning was created) 4) sends Last-Event-ID http header when it has previously been passed in an event from the server (node:2252609) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [Server]. Use emitter.setMaxListeners() to increase limit 5) sends correct Last-Event-ID http header when an initial Last-Event-ID header was specified in the constructor (node:2252609) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [Server]. Use emitter.setMaxListeners() to increase limit (node:2252609) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [Server]. Use emitter.setMaxListeners() to incre
Bug#1072733: marked as done (sherlock has an undeclared file conflict on /usr/lib/python3/dist-packages/sherlock/__init__.py)
Your message dated Sun, 9 Jun 2024 14:00:56 +0200 with message-id and subject line Re: python-Sherlock conflict sherlock has caused the Debian Bug report #1072733, regarding sherlock has an undeclared file conflict on /usr/lib/python3/dist-packages/sherlock/__init__.py to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1072733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sherlock Version: 0.14.4+git20240531.e5ad3c4-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + python3-sherlock sherlock has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/python3/dist-packages/sherlock/__init__.py is contained in the packages * python3-sherlock/0.4.1-2 as present in trixie|unstable * sherlock/0.14.4+git20240531.e5ad3c4-1 as present in unstable These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected file. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- On 6/7/24 14:05, Nilson Silva wrote: Hello Thomas Goirand! I am a maintainer of sherlock and you are the maintainer of python-sherlock. Our packages conflict when installed in the same environment. [...] Hi, I just saw that sherlock (the social networks package) moved its python files to /usr/share, instead of /usr/lib/python3/dist-packages. This was the sensible thing to do, as it doesn't really need to expose itself as Python module. Therefore, this bug can be closed, and there's IMO nothing more to do in the python-sherlock (the cluster lock package), as the conflict is now solved. Cheers, Thomas Goirand (zigo)--- End Message ---
Bug#1072758: marked as done (eslint: FTBFS: AssertionError [ERR_ASSERTION]: A fatal parsing error occurred: Parsing error: Unexpected token)
Your message dated Sun, 09 Jun 2024 10:06:14 +
with message-id
and subject line Bug#1072758: fixed in eslint 6.4.0~dfsg+~6.1.9-12
has caused the Debian Bug report #1072758,
regarding eslint: FTBFS: AssertionError [ERR_ASSERTION]: A fatal parsing error
occurred: Parsing error: Unexpected token
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.)
--
1072758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:eslint
Version: 6.4.0~dfsg+~6.1.9-11
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
cmark-gfm README.md > README.html
cmark-gfm --to plaintext README.md > README.txt
cmark-gfm CHANGELOG.md > CHANGELOG.html
cmark-gfm --to plaintext CHANGELOG.md > CHANGELOG.txt
mkdir --parents debian-man/
cp --force bin/eslint.js debian-man/eslint
NODE_PATH=lib help2man --name AST-based --name pattern --name checker --name
and --name linting --name utility --name for --name JavaScript --no-info
--output debian-man/eslint.1 debian-man/eslint || { NODE_PATH=lib
debian-man/eslint --help; false; }
dh override_dh_auto_build
[... snipped ...]
ruleId: 'id-match',
severity: 1,
message: "Identifier 'category_id' does not match the pattern '^[^_]+$'.",
line: 1,
column: 7,
nodeType: 'Identifier',
messageId: 'notMatch',
endLine: 1,
endColumn: 18
},
{
ruleId: 'id-match',
severity: 1,
message: "Identifier 'category_id' does not match the pattern '^[^_]+$'.",
line: 1,
column: 7,
nodeType: 'Identifier',
messageId: 'notMatch',
endLine: 1,
endColumn: 18
}
]
AssertionError [ERR_ASSERTION]: Should have 1 error but had 2: [
{
ruleId: 'id-match',
severity: 1,
message: "Identifier 'category_id' does not match the pattern '^[^_]+$'.",
line: 1,
column: 7,
nodeType: 'Identifier',
messageId: 'notMatch',
endLine: 1,
endColumn: 18
},
{
ruleId: 'id-match',
severity: 1,
message: "Identifier 'category_id' does not match the pattern '^[^_]+$'.",
line: 1,
column: 7,
nodeType: 'Identifier',
messageId: 'notMatch',
endLine: 1,
endColumn: 18
}
]
at testInvalidTemplate (lib/rule-tester/rule-tester.js:531:24)
at Context. (lib/rule-tester/rule-tester.js:658:25)
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:677:10)
at /usr/share/nodejs/mocha/lib/runner.js:800:12
at next (/usr/share/nodejs/mocha/lib/runner.js:592:14)
at /usr/share/nodejs/mocha/lib/runner.js:602:7
at next (/usr/share/nodejs/mocha/lib/runner.js:485:14)
at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:570:5)
at process.processImmediate (node:internal/timers:478:21)
# TODO: not ok 999 id-match invalid var { category_id = 1 } = query;
Should have 1 error but had 2: [
{
ruleId: 'id-match',
severity: 1,
message: "Identifier 'category_id' does not match the pattern '^[^_]+$'.",
line: 1,
column: 7,
nodeType: 'Identifier',
messageId: 'notMatch',
endLine: 1,
endColumn: 18
},
{
ruleId: 'id-match',
severity: 1,
message: "Identifier 'category_id' does not match the pattern '^[^_]+$'.",
line: 1,
column: 7,
nodeType: 'Identifier',
messageId: 'notMatch',
endLine: 1,
endColumn: 18
}
]
AssertionError [ERR_ASSERTION]: Should have 1 error but had 2: [
{
ruleId: 'id-match',
severity: 1,
message: "Identifier 'category_id' does not match the pattern '^[^_]+$'.",
line: 1,
column: 7,
nodeType: 'Identifier',
messageId: 'notMatch',
endLine: 1,
endColumn: 18
},
{
ruleId: 'id-match',
severity: 1,
message: "Identifier 'category_id' does not match the pattern '^[^_]+$'.",
line: 1,
column: 7,
nodeType: 'Identifier',
messageId: 'notMat
Processed: Bug#1072758 marked as pending in eslint
Processing control commands: > tag -1 pending Bug #1072758 [src:eslint] eslint: FTBFS: AssertionError [ERR_ASSERTION]: A fatal parsing error occurred: Parsing error: Unexpected token Added tag(s) pending. -- 1072758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1072823
Processing commands for cont...@bugs.debian.org: > close 1072823 3.8.0+repack1-10 Bug #1072823 [src:liggghts] liggghts FTBFS with VTK 9.3.0 Marked as fixed in versions liggghts/3.8.0+repack1-10. Bug #1072823 [src:liggghts] liggghts FTBFS with VTK 9.3.0 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1072823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1064694: marked as done (terminado: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)
Your message dated Sun, 09 Jun 2024 09:06:20 +
with message-id
and subject line Bug#1064694: fixed in terminado 0.18.1-1
has caused the Debian Bug report #1064694,
regarding terminado: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p 3.11 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1064694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: terminado
Version: 0.18.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.11 with "build"
> module
> I: pybuild base:305: python3.11 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.11_terminado
> * Building wheel...
> Successfully built terminado-0.18.0-py3-none-any.whl
> I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.11 with
> "installer" module
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd
> /<>/.pybuild/cpython3_3.11_terminado/build; python3.11 -m pytest
> tests
> [1m= test session starts
> ==[0m
> platform linux -- Python 3.11.8, pytest-7.4.4, pluggy-1.4.0
> rootdir: /<>/.pybuild/cpython3_3.11_terminado/build
> configfile: pyproject.toml
> plugins: timeout-2.2.0
> timeout: 300.0s
> timeout method: signal
> timeout func_only: False
> collected 9 items
>
> tests/basic_test.py
> [32m.[0m[32m.[0m[32m.[0m[31mF[0m[32m.[0m[32m.[0m[31mF[0m[32m.[0m[32m.[0m[31m
> [100%][0m
>
> === FAILURES
> ===
> [31m[1m NamedTermTests.test_namespace
> _[0m
>
> [37m@pytest[39;49;00m.hookimpl(hookwrapper=[94mTrue[39;49;00m,
> tryfirst=[94mTrue[39;49;00m)[90m[39;49;00m
> [94mdef[39;49;00m [92mpytest_runtest_call[39;49;00m() ->
> Generator[[94mNone[39;49;00m, [94mNone[39;49;00m,
> [94mNone[39;49;00m]:[90m[39;49;00m
> > [94myield from[39;49;00m
> > unraisable_exception_runtest_hook()[90m[39;49;00m
>
>
> [1m[31m/usr/lib/python3/dist-packages/_pytest/unraisableexception.py[0m:88:
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
>
> [94mdef[39;49;00m [92munraisable_exception_runtest_hook[39;49;00m()
> -> Generator[[94mNone[39;49;00m, [94mNone[39;49;00m,
> [94mNone[39;49;00m]:[90m[39;49;00m
> [94mwith[39;49;00m catch_unraisable_exception() [94mas[39;49;00m
> cm:[90m[39;49;00m
> [94myield[39;49;00m[90m[39;49;00m
> [94mif[39;49;00m cm.unraisable:[90m[39;49;00m
> [94mif[39;49;00m cm.unraisable.err_msg [95mis[39;49;00m
> [95mnot[39;49;00m [94mNone[39;49;00m:[90m[39;49;00m
> err_msg = cm.unraisable.err_msg[90m[39;49;00m
> [94melse[39;49;00m:[90m[39;49;00m
> err_msg = [33m"[39;49;00m[33mException ignored
> in[39;49;00m[33m"[39;49;00m[90m[39;49;00m
> msg =
> [33mf[39;49;00m[33m"[39;49;00m[33m{[39;49;00merr_msg[33m}[39;49;00m[33m:
>
> [39;49;00m[33m{[39;49;00mcm.unraisable.object[33m!r}[39;49;00m[33m\n[39;49;00m[33m\n[39;49;00m[33m"[39;49;00m[90m[39;49;00m
> msg +=
> [33m"[39;49;00m[33m"[39;49;00m.join([90m[39;49;00m
> traceback.format_exception([90m[39;49;00m
> cm.unraisable.exc_type,[90m[39;49;00m
> cm.unraisable.exc_value,[90m[39;49;00m
> cm.unraisable.exc_traceback,[90m[39;49;00m
>
Processed: Bug#1064694 marked as pending in terminado
Processing control commands:
> tag -1 pending
Bug #1064694 [src:terminado] terminado: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) pending.
--
1064694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Installs /usr/LICENSE
Processing control commands: > tags -1 patch Bug #1068500 [python3-xmlrunner] Installs /usr/LICENSE Ignoring request to alter tags of bug #1068500 to the same tags previously set -- 1068500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Installs /usr/LICENSE
Processing control commands: > tags -1 patch Bug #1068500 [python3-xmlrunner] Installs /usr/LICENSE Added tag(s) patch. -- 1068500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072732: marked as done (update-shells: duplicates entries when a package includes both aliased and canonical shells)
Your message dated Sun, 09 Jun 2024 07:48:58 + with message-id and subject line Bug#1072732: fixed in debianutils 5.19 has caused the Debian Bug report #1072732, regarding update-shells: duplicates entries when a package includes both aliased and canonical shells 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.) -- 1072732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debianutils Version: 5.17 Tags: patch X-Debbugs-Cc: jo...@debian.org User: helm...@debian.org Usertags: dep17 Hi, a longer while ago I added update-shells to debianutils as a way of managing /etc/shells using dpkg triggers. It took us a while to get the interactions with /usr-merge right and it seems we're not done yet. My recent bash upload changes it's shells.d snippet to include both aliased and canonical shells, which is right in principle, but it causes update-shells to duplicate /usr/bin/bash in /etc/shells. While that's not breaking anything yet, it's also not nice and kudos to Johannes for spotting it. It also is easy to fix with the attached patch. Would you kindly apply it? Helmut diff --minimal -Nru debianutils-5.17/debian/changelog debianutils-5.17+nmu1/debian/changelog --- debianutils-5.17/debian/changelog 2024-03-01 20:08:45.0 +0100 +++ debianutils-5.17+nmu1/debian/changelog 2024-06-07 09:50:16.0 +0200 @@ -1,3 +1,11 @@ +debianutils (5.17+nmu1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * update-shells: Avoid duplicate lines when package shells contain both +aliased and canonical shells. (Closes: #-1) + + -- Helmut Grohne Fri, 07 Jun 2024 09:50:16 +0200 + debianutils (5.17) unstable; urgency=medium [ Patrick Brünn ] diff --minimal -Nru debianutils-5.17/update-shells debianutils-5.17+nmu1/update-shells --- debianutils-5.17/update-shells 2024-02-28 21:00:25.0 +0100 +++ debianutils-5.17+nmu1/update-shells 2024-06-07 09:48:53.0 +0200 @@ -79,10 +79,12 @@ test -f "$f" || continue while IFS='#' read -r line _; do [ -n "$line" ] || continue - PKG_SHELLS="$PKG_SHELLS$line#" + if ! hashset_contains "$PKG_SHELLS" "$line"; then + PKG_SHELLS="$PKG_SHELLS$line#" + fi realshell=$(dpkg-realpath --root "$ROOT" "$(dirname "$line")")/$(basename "$line") - if [ "$line" != "$realshell" ]; then - PKG_SHELLS="$PKG_SHELLS$realshell#" + if ! hashset_contains "$PKG_SHELLS" "$realshell"; then + PKG_SHELLS="$PKG_SHELLS$realshell#" fi done < "$f" done --- End Message --- --- Begin Message --- Source: debianutils Source-Version: 5.19 Done: Niels Thykier We believe that the bug you reported is fixed in the latest version of debianutils, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Niels Thykier (supplier of updated debianutils 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, 09 Jun 2024 07:25:40 + Source: debianutils Architecture: source Version: 5.19 Distribution: unstable Urgency: medium Maintainer: Ileana Dumitrescu Changed-By: Niels Thykier Closes: 1072732 Changes: debianutils (5.19) unstable; urgency=medium . [ Helmut Grohne ] * update-shells: Avoid duplicate lines when package shells contain both aliased and canonical shells. (Closes: #1072732) Checksums-Sha1: 13f31ccac6ac4f13125719ae879d08c36dab57ef 1289 debianutils_5.19.dsc c0ec76f28d90ef805834f1422a31ee426e6c89d1 106276 debianutils_5.19.tar.xz d762482064a9ae740b46e8552aaf101ff092fc05 5358 debianutils_5.19_source.buildinfo Checksums-Sha256: 1b24cad834ba55af65e126c131d596ff5bc45e4110f4f76d72fa60383348fcaa 1289 debianutils_5.19.dsc 1f5552d3f7ecc811a37ba3a70a446bd988f
Bug#909352: marked as done (Is squeak-plugins-scratch still useful?)
Your message dated Sun, 09 Jun 2024 04:30:20 + with message-id and subject line Bug#1072784: Removed package(s) from unstable has caused the Debian Bug report #909352, regarding Is squeak-plugins-scratch still useful? 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.) -- 909352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: squeak-plugins-scratch Severity: serious Tags: buster sid Bernhard Übelacker noticed in #892016: <-- snip --> When just installing the packages the plugin so.CameraPlugin gets used from the package squeak-plugins-scratch. But a similar so.CameraPlugin is already packaged with squeak-vm. squeak-vm: /usr/lib/squeak/4.10.2.2614/so.CameraPlugin squeak-plugins-scratch: /usr/lib/scratch/plugins/so.CameraPlugin So this probably should be clarified if the plugins are really needed in both packages. <-- snip --> At first sight I would say that all plugins in squeak-plugins-scratch are already shipped by squeak-vm, but I might be missing something. --- End Message --- --- Begin Message --- Version: 1.4.0.2~svn.r83-3.1+rm Dear submitter, as the package squeak-plugins-scratch has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1072784 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1065944: marked as done (squeak-plugins-scratch: FTBFS on arm{el,hf}: WeDoLinux.c:175:9: error: implicit declaration of function ‘close’; did you mean ‘pclose’? [-Werror=implicit-function-declarat
Your message dated Sun, 09 Jun 2024 04:30:20 +
with message-id
and subject line Bug#1072784: Removed package(s) from unstable
has caused the Debian Bug report #1065944,
regarding squeak-plugins-scratch: FTBFS on arm{el,hf}: WeDoLinux.c:175:9:
error: implicit declaration of function ‘close’; did you mean ‘pclose’?
[-Werror=implicit-function-declaration]
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.)
--
1065944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: squeak-plugins-scratch
Version: 1.4.0.2~svn.r83-3.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=squeak-plugins-scratch=armel=1.4.0.2%7Esvn.r83-3.1%2Bb1=1710056636=0
cd wedo/ && \
arm-linux-gnueabi-gcc -std=gnu89 -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -g -fPIC -c *.c
WeDoLinux.c: In function ‘WeDoClosePort’:
WeDoLinux.c:175:9: error: implicit declaration of function ‘close’; did you
mean ‘pclose’? [-Werror=implicit-function-declaration]
175 | close(fdWeDo);
| ^
| pclose
cc1: some warnings being treated as errors
make: *** [debian/rules:31: build-stamp] Error 1
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Version: 1.4.0.2~svn.r83-3.1+rm
Dear submitter,
as the package squeak-plugins-scratch has just been removed from the Debian
archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1072784
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1042316: marked as done (python-efilter: FTBFS: make: *** [debian/rules:6: clean] Error 25)
Your message dated Sun, 09 Jun 2024 04:31:46 +
with message-id
and subject line Bug#1072788: Removed package(s) from unstable
has caused the Debian Bug report #1042316,
regarding python-efilter: FTBFS: make: *** [debian/rules:6: clean] Error 25
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.)
--
1042316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-efilter
Version: 1.5-2.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level
> 9 in use)
> I: pybuild base:240: python3.11 setup.py clean
> error in efilter setup command: 'install_requires' must be a string or list
> of strings containing valid project/version requirement specifiers; Expected
> end or semicolon (after version specifier)
> pytz >= 2011k
> ~~~^
> E: pybuild pybuild:388: clean: plugin distutils failed with: exit code=1:
> python3.11 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned
> exit code 13
> make: *** [debian/rules:6: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/07/26/python-efilter_1.5-2.1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 1.5-2.1+rm
Dear submitter,
as the package python-efilter has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1072788
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1071114: marked as done (plover: unhandled symlink to directory conversion: /usr/lib/python3/dist-packages/plover/assets -> ../../../../share/plover/assets)
Your message dated Sun, 09 Jun 2024 00:05:53 + with message-id and subject line Bug#1071114: fixed in plover 4.0.0~rc2-0.3 has caused the Debian Bug report #1071114, regarding plover: unhandled symlink to directory conversion: /usr/lib/python3/dist-packages/plover/assets -> ../../../../share/plover/assets 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.) -- 1071114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: plover Version: 4.0.0~rc2-0.2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: bookworm -> trixie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.maintscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. >From the attached log (scroll to the bottom...): 3m55.0s ERROR: installs objects over existing directory symlinks: /usr/lib/python3/dist-packages/plover/assets/american_english_words.txt (plover) != /usr/share/plover/assets/american_english_words.txt (?) /usr/lib/python3/dist-packages/plover/assets -> ../../../../share/plover/assets /usr/lib/python3/dist-packages/plover/assets/commands.json (plover) != /usr/share/plover/assets/commands.json (?) /usr/lib/python3/dist-packages/plover/assets -> ../../../../share/plover/assets /usr/lib/python3/dist-packages/plover/assets/main.json (plover) != /usr/share/plover/assets/main.json (?) /usr/lib/python3/dist-packages/plover/assets -> ../../../../share/plover/assets /usr/lib/python3/dist-packages/plover/assets/plover.png (plover) != /usr/share/plover/assets/plover.png (?) /usr/lib/python3/dist-packages/plover/assets -> ../../../../share/plover/assets /usr/lib/python3/dist-packages/plover/assets/user.json (plover) != /usr/share/plover/assets/user.json (?) /usr/lib/python3/dist-packages/plover/assets -> ../../../../share/plover/assets cheers, Andreas plover_4.0.0~rc2-0.2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: plover Source-Version: 4.0.0~rc2-0.3 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of plover, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated plover 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: Sat, 08 Jun 2024 19:40:06 -0400 Source: plover Architecture: source Version: 4.0.0~rc2-0.3 Distribution: unstable Urgency: medium Maintainer: Harlan Lieberman-Berg Changed-By: Boyuan Yang Closes: 1071114 Changes: plover (4.0.0~rc2-0.3) unstable; urgency=medium . * Non-maintainer upload. * debian/plover.maintscript: Add symlink_to_dir helper to fix unhandled conversion from symli
Processed: control
Processing commands for cont...@bugs.debian.org: > severity 1072126 important Bug #1072126 [src:frr] frr: CVE-2024-31948 Severity set to 'important' from 'grave' > quit Stopping processing here. Please contact me if you need assistance. -- 1072126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 1068929 with 1071902
Processing commands for cont...@bugs.debian.org: > block 1068929 with 1071902 Bug #1068929 [src:rust-async-lock] Please update for event-listener 5.x Bug #1072842 [src:rust-async-lock] rust-async-lock: please update to version 3.0+ 1068929 was not blocked by any bugs. 1068929 was not blocking any bugs. Added blocking bug(s) of 1068929: 1071902 1072842 was not blocked by any bugs. 1072842 was not blocking any bugs. Added blocking bug(s) of 1072842: 1071902 > thanks Stopping processing here. Please contact me if you need assistance. -- 1068929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068929 1072842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unblock 1071902 with 1068929
Processing commands for cont...@bugs.debian.org: > unblock 1071902 with 1068929 Bug #1071902 [src:rust-event-listener] rust-event-listener: event-listener v5 is considered buggy 1071902 was not blocked by any bugs. 1071902 was blocking: 1069575 Removed blocking bug(s) of 1071902: 1072842 and 1068929 > thanks Stopping processing here. Please contact me if you need assistance. -- 1071902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1072842: rust-async-lock: please update to version 3.0+
Processing control commands: > forcemerge -1 1068929 Bug #1072842 [src:rust-async-lock] rust-async-lock: please update to version 3.0+ Bug #1068929 [src:rust-async-lock] Please update for event-listener 5.x Severity set to 'wishlist' from 'normal' 1071902 was blocked by: 1068929 1071902 was blocking: 1069575 Removed blocking bug(s) of 1071902: 1068929 1068929 was blocked by: 1068930 1068929 was not blocking any bugs. Removed blocking bug(s) of 1068929: 1068930 Marked as found in versions rust-async-lock/2.6.0-4. Bug #1072842 [src:rust-async-lock] rust-async-lock: please update to version 3.0+ Marked as found in versions rust-async-lock/2.8.0-1. Added tag(s) patch. Merged 1068929 1072842 -- 1068929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068929 1071902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071902 1072842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 1071902 with 1068929
Processing commands for cont...@bugs.debian.org: > block 1071902 with 1068929 Bug #1071902 [src:rust-event-listener] rust-event-listener: event-listener v5 is considered buggy 1071902 was not blocked by any bugs. 1071902 was blocking: 1069575 Added blocking bug(s) of 1071902: 1068929 > thanks Stopping processing here. Please contact me if you need assistance. -- 1071902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072734: marked as done (prometheus-squid-exporter: autopkgtest dh-golang-autopkgtest is flaky)
Your message dated Sat, 08 Jun 2024 17:35:29 + with message-id and subject line Bug#1072734: fixed in prometheus-squid-exporter 1.11.0+ds-3 has caused the Debian Bug report #1072734, regarding prometheus-squid-exporter: autopkgtest dh-golang-autopkgtest is flaky 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.) -- 1072734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: prometheus-squid-exporter Severity: serious Justification: flaky debci is RC as per RT User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), The dh-golang-autopkgtest autopkgtest is flaky, and often fails and then passes upon reruns, independently of the reason why it was triggered. As per RT, this is an RC issue. Example: 98s === RUN TestReadFromSquid 98s panic: runtime error: invalid memory address or nil pointer dereference 98s [signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x653bf4] 98s 98s goroutine 7 [running]: 98s github.com/boynux/squid-exporter/collector.TestReadFromSquid.func1() 98s /tmp/autopkgtest-lxc.tnsof3vy/downtmp/autopkgtest_tmp/build/src/github.com/boynux/squid-exporter/collector/client_test.go:39 +0x44 98s created by github.com/boynux/squid-exporter/collector.TestReadFromSquid in goroutine 6 98s /tmp/autopkgtest-lxc.tnsof3vy/downtmp/autopkgtest_tmp/build/src/github.com/boynux/squid-exporter/collector/client_test.go:37 +0x70 98s FAIL github.com/boynux/squid-exporter/collector 0.010s https://ci.debian.net/packages/p/prometheus-squid-exporter/testing/arm64/47447211/ -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: prometheus-squid-exporter Source-Version: 1.11.0+ds-3 Done: Daniel Swarbrick We believe that the bug you reported is fixed in the latest version of prometheus-squid-exporter, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Swarbrick (supplier of updated prometheus-squid-exporter 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: Sat, 08 Jun 2024 17:15:51 + Source: prometheus-squid-exporter Architecture: source Version: 1.11.0+ds-3 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Daniel Swarbrick Closes: 1072734 Changes: prometheus-squid-exporter (1.11.0+ds-3) unstable; urgency=medium . * Add new 0004-Fix-racy-TestReadFromSquid.patch (Closes: #1072734) Checksums-Sha1: adaf26b917de109450a8fc66be92b0bb055a0c94 2481 prometheus-squid-exporter_1.11.0+ds-3.dsc f46fff215b179475c006cb0b6a1958c746bd107f 6636 prometheus-squid-exporter_1.11.0+ds-3.debian.tar.xz 3782142baee35d6cb6b2f112db4212f509436bb8 8467 prometheus-squid-exporter_1.11.0+ds-3_amd64.buildinfo Checksums-Sha256: 708aec7c6c888533e300ec8c03e52593d898c15b14a4622b82940b8272b0441b 2481 prometheus-squid-exporter_1.11.0+ds-3.dsc 5faedd8402839366f0224c541725a1d6b31fe70399fc60ac9f24d9ef10b311c0 6636 prometheus-squid-exporter_1.11.0+ds-3.debian.tar.xz efba94e6e512562a4c1c226b115cfa316aa34db121ea378661b2ae9568682508 8467 prometheus-squid-exporter_1.11.0+ds-3_amd64.buildinfo Files: 3074217dc74d4c37d62a163486f91f42 2481 net optional prometheus-squid-exporter_1.11.0+ds-3.dsc bcd5ad7a289a867eac56cd6a46664a9f 6636 net optional prometheus-squid-exporter_1.11.0+ds-3.debian.tar.xz 8671c0754c00eea128f705235b807629 8467 net optional prometheus-squid-exporter_1.11.0+ds-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEMD9oek78sa58GjWjtwAXP7uAWikFAmZkkpYWHGRzd2FyYnJp Y2tAZGViaWFuLm9yZwAKCRC3ABc/u4BaKaV2EACVRLBb0VrQXng+p8/00j7EifyV gECDkNU3KZzMPnzxRTx2AW/KrnIBugrGeZPNFVKzea/cUhRfDM7/qY3B+4jTjzT1 8G/9l0ePPQRIgo6Fde9wTXjdccNSHz82Ka30Bzniy1QyuljoZxJVHdPGPyNCiGQY VgTYDATnIAlO5F3dHY4Ga2CeLh5HFd64Yhq4BoqzQL6C13SS/iASWzBnSovLcOI0 OCjSG1xk9khwlHfl4dQmuQLk/GFh6nP63N0XtUaIiqaVCQ+Dnvtl6fz6v58eYUTu siENECebDwQYRUNLktt4cRRY3uIChZwfGnfVPYZLnkC8pOOCNdZgMRrvHEbORD4M pctg/n9Vi3mBAU
Processed: Bug#1072734 marked as pending in prometheus-squid-exporter
Processing control commands: > tag -1 pending Bug #1072734 [src:prometheus-squid-exporter] prometheus-squid-exporter: autopkgtest dh-golang-autopkgtest is flaky Added tag(s) pending. -- 1072734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: gertty: FTBFS with SQLAlchemy 2.x
Processing commands for cont...@bugs.debian.org: > tags 1069052 + ftbfs Bug #1069052 [src:gertty] FTBFS with SQLAlchemy 2.x Added tag(s) ftbfs. > retitle 1069052 gertty: FTBFS with SQLAlchemy 2.x Bug #1069052 [src:gertty] FTBFS with SQLAlchemy 2.x Changed Bug title to 'gertty: FTBFS with SQLAlchemy 2.x' from 'FTBFS with SQLAlchemy 2.x'. > severity 1069052 serious Bug #1069052 [src:gertty] gertty: FTBFS with SQLAlchemy 2.x Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1069052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: update-shells: duplicates entries when a package includes both aliased and canonical shells
Processing control commands: > severity -1 serious Bug #1072732 [debianutils] update-shells: duplicates entries when a package includes both aliased and canonical shells Severity set to 'serious' from 'normal' > affects -1 + mmdebstrap Bug #1072732 [debianutils] update-shells: duplicates entries when a package includes both aliased and canonical shells Added indication that 1072732 affects mmdebstrap -- 1072732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072642: marked as done (curl: FTBFS (TESTFAIL: These test cases failed: 241 507) (also applies to autopkgtest))
Your message dated Sat, 8 Jun 2024 16:46:46 +0200
with message-id
and subject line Re: Bug#1072642: curl: FTBFS (TESTFAIL: These test cases
failed: 241 507) (also applies to autopkgtest)
has caused the Debian Bug report #1072642,
regarding curl: FTBFS (TESTFAIL: These test cases failed: 241 507) (also
applies to autopkgtest)
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.)
--
1072642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: curl
Version: 8.8.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hello,
I did a local rebuild on sid which failed:
srcdir=. /usr/bin/perl -I. ./runtests.pl -a -p ~flaky ~timing-dependent -n -j35
~300 ~301 ~303 ~304 ~306 ~309 ~310 ~325 ~364 ~400 ~401 ~403 ~406 ~407 ~408 ~409
~410 ~414 ~417 ~560 ~678 ~987 ~988 ~989 ~1112 ~1272 ~1470 ~1561 ~1562 ~1630
~1631 ~1632 ~2034 ~2037 ~2041 ~3000 ~3001 ~3102
Using curl: ../src/curl
[...]
test 0241...[HTTP-IPv6 GET (using ip6-localhost)]
241: protocol FAILED!
There was no content at all in the file log/5/server.input.
Server glitch? Total curl failure? Returned: 7
== Contents of files in the log/5/ dir after test 241
=== Start of file http_ipv6_server.log
16:19:15.385882 Running HTTP IPv6 version on port 36339
16:19:15.385966 Wrote pid 68256 to log/5/server/http_ipv6_server.pid
16:19:15.385990 Wrote port 36339 to log/5/server/http_ipv6_server.port
16:19:16.348256 > Client connect
16:19:16.348285 accept_connection 3 returned 4
16:19:16.348310 accept_connection 3 returned 0
16:19:16.348377 Read 88 bytes
16:19:16.348397 Process 88 bytes request
16:19:16.348427 Got request: GET /verifiedserver HTTP/1.1
16:19:16.348443 Are-we-friendly question received
16:19:16.348471 Wrote request (88 bytes) input to log/5/server.input
16:19:16.348499 Identifying ourselves as friends
16:19:16.348570 Response sent (56 bytes) and written to log/5/server.response
16:19:16.348589 special request received, no persistency
16:19:16.348604 > Client disconnect 0
=== End of file http_ipv6_server.log
=== Start of file http_ipv6_verify.log
* Trying [::1]:36339...
* Connected to ::1 (::1) port 36339
> GET /verifiedserver HTTP/1.1
> Host: [::1]:36339
> User-Agent: curl/8.8.0
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 200 OK
< Content-Length: 17
<
{ [17 bytes data]
* Connection #0 to host ::1 left intact
=== End of file http_ipv6_verify.log
=== Start of file http_ipv6_verify.out
WE ROOLZ: 68256
=== End of file http_ipv6_verify.out
=== Start of file server.cmd
Testnum 241
=== End of file server.cmd
=== Start of file server.response
HTTP/1.1 200 OK
Content-Length: 17
WE ROOLZ: 68256
=== End of file server.response
=== Start of file stderr241
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to ip6-localhost port 36339 after 106 ms: Couldn't
connect to server
=== End of file stderr241
=== Start of file trace241
16:19:16.524170 == Info: Host ip6-localhost:36339 was resolved.
16:19:16.524215 == Info: IPv6: (none)
16:19:16.524217 == Info: IPv4: 31.15.64.248
16:19:16.524231 == Info: Trying 31.15.64.248:36339...
16:19:16.567508 == Info: connect to 31.15.64.248 port 36339 from
192.168.178.20 port 40168 failed: Connection refused
16:19:16.567523 == Info: Failed to connect to ip6-localhost port 36339 after
106 ms: Couldn't connect to server
16:19:16.567663 == Info: Closing connection
=== End of file trace241
[...]
test 0507...[multi interface get with non-existing host name]
lib507 returned 0, when expecting 6
507: exit FAILED
== Contents of files in the log/31/ dir after test 507
=== Start of file server.cmd
Testnum 507
=== End of file server.cmd
=== Start of file stderr507
URL: http://non-existing-host.haxx.se/
Test ended with result 0
=== End of file stderr507
=== Start of file stdout507
HTTP/1.1 200 OK
Date: Wed, 05 Jun 2024 16:19:18 GMT
Server: Apache/2.4.59 (Debian)
Last-Modified: Sun, 14 Feb 2016 17:00:04 GMT
ETag: "0-52bbdd4e2cd00"
Accept-Ranges: bytes
Content-Length: 0
Content-Type: text/html
=== End of file stdout507
[...]
2)
TESTDONE: 1700 tests were considered during 522 seconds.
TESTINFO: 195 te
Bug#1066606: marked as done (fteqcc: FTBFS: qccmain.c:3127:17: error: implicit declaration of function ‘PostCompile’ [-Werror=implicit-function-declaration])
Your message dated Sat, 08 Jun 2024 14:35:00 +
with message-id
and subject line Bug#1066606: fixed in fteqcc 3343+svn3400-5
has caused the Debian Bug report #1066606,
regarding fteqcc: FTBFS: qccmain.c:3127:17: error: implicit declaration of
function ‘PostCompile’ [-Werror=implicit-function-declaration]
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.)
--
1066606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fteqcc
Version: 3343+svn3400-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> gcc -Wall -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -c -o qcctui.o qcctui.c
> qcc_pr_lex.c: In function ‘ParsePrecompilerIf’:
> qcc_pr_lex.c:216:15: warning: unused variable ‘start’ [-Wunused-variable]
> 216 | char *start = pr_file_p;
> | ^
> qcc_pr_lex.c: In function ‘QCC_PR_Precompiler’:
> qcc_pr_lex.c:810:20: warning: unused variable ‘currentsourcefile’
> [-Wunused-variable]
> 810 | extern int currentsourcefile;
> |^
> qccmain.c: In function ‘QCC_WriteData’:
> qccmain.c:1116:40: warning: cast to pointer from integer of different size
> [-Wint-to-pointer-cast]
> 1116 | qcc_typeinfo[i].name = (char
> *)QCC_CopyDupBackString(qcc_typeinfo[i].name);
> |^
> qcd_main.c: In function ‘filefromprogs’:
> qcd_main.c:163:58: warning: logical not is only applied to the left hand side
> of comparison [-Wlogical-not-parentheses]
> 163 | if (!pr_progstate[prnum].progs->secondaryversion !=
> PROG_SECONDARYVERSION16 &&
> | ^~
> qcd_main.c:163:13: note: add parentheses around left hand side expression to
> silence this warning
> 163 | if (!pr_progstate[prnum].progs->secondaryversion !=
> PROG_SECONDARYVERSION16 &&
> | ^~~~
> | ( )
> qcd_main.c:164:62: warning: logical not is only applied to the left hand side
> of comparison [-Wlogical-not-parentheses]
> 164 | !pr_progstate[prnum].progs->secondaryversion !=
> PROG_SECONDARYVERSION32)
> | ^~
> qcd_main.c:164:17: note: add parentheses around left hand side expression to
> silence this warning
> 164 | !pr_progstate[prnum].progs->secondaryversion !=
> PROG_SECONDARYVERSION32)
> | ^~~~
> | ( )
> qccmain.c: In function ‘QCC_main’:
> qccmain.c:2734:19: warning: assignment to ‘void * (*)(hashtable_t *, char *)’
> {aka ‘void * (*)(struct hashtable_s *, char *)’} from incompatible pointer
> type ‘void * (*)(hashtable_t *, const char *)’ {aka ‘void * (*)(struct
> hashtable_s *, const char *)’} [-Wincompatible-pointer-types]
> 2734 | pHash_Get = _Get;
> | ^
> qccmain.c:2755:19: warning: pointer targets in assignment from ‘unsigned char
> *’ to ‘char *’ differ in signedness [-Wpointer-sign]
> 2755 | s = externs->ReadFile("qcc.cfg", s, p);
> | ^
> qccmain.c:2936:27: warning: assignment to ‘void * (*)(hashtable_t *, char *)’
> {aka ‘void * (*)(struct hashtable_s *, char *)’} from incompatible pointer
> type ‘void * (*)(hashtable_t *, const char *)’ {aka ‘void * (*)(struct
> hashtable_s *, const char *)’} [-Wincompatible-pointer-types]
> 2936 | pHash_Get = _GetInsensative;
> | ^
>
Processed: texlive-binaries upgrade breaks therion build
Processing control commands: > affects -1 src:therion Bug #1072828 [texlive-binaries] texlive-binaries upgrade breaks therion build Added indication that 1072828 affects src:therion -- 1072828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1066606 marked as pending in fteqcc
Processing control commands: > tag -1 pending Bug #1066606 [src:fteqcc] fteqcc: FTBFS: qccmain.c:3127:17: error: implicit declaration of function ‘PostCompile’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063407: marked as done (pybdsf fails to build with Python 3.12 as default)
Your message dated Sat, 08 Jun 2024 13:53:01 +
with message-id
and subject line Bug#1063407: fixed in pybdsf 1.10.3-3
has caused the Debian Bug report #1063407,
regarding pybdsf fails to build with Python 3.12 as default
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.)
--
1063407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pybdsf
Version: 1.10.3-2
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
Forwarded: https://github.com/lofar-astron/PyBDSF/issues/214
pybdsf fails to build with Python 3.12 as default, also the autopkg test
fails with:
290s autopkgtest [09:33:17]: test command1: [---
292s [31;1mWARNING[0m: Matplotlib pyplot could not be imported.
Plotting is disabled.
293s --> Loaded parameters from file 'tbdsf_process_image.in'.
293s Traceback (most recent call last):
293s File
"/tmp/autopkgtest.Z7dzWY/build.NDT/src/test/tbdsf_process_image.py",
line 5, in
293s img = bdsf.process_image('tbdsf_process_image.in', ncores=2)
293s ^^
293s File "/usr/lib/python3/dist-packages/bdsf/__init__.py", line 256,
in process_image
293s img.process(**kwargs)
293s File "/usr/lib/python3/dist-packages/bdsf/image.py", line 136, in
process
293s success = interface.process(self, **kwargs)
293s ^
293s File "/usr/lib/python3/dist-packages/bdsf/interface.py", line 66,
in process
293s _run_op_list(img, op_chain)
293s File "/usr/lib/python3/dist-packages/bdsf/__init__.py", line 155,
in _run_op_list
293s op(img)
293s File "/usr/lib/python3/dist-packages/bdsf/readimage.py", line 68,
in __call__
293s result = read_image_from_file(image_file, img, img.indir)
293s
293s File "/usr/lib/python3/dist-packages/bdsf/functions.py", line
1079, in read_image_from_file
293s from distutils.version import StrictVersion
293s ModuleNotFoundError: No module named 'distutils'
294s autopkgtest [09:33:21]: test command1: ---]
297s command1 FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: pybdsf
Source-Version: 1.10.3-3
Done: Ole Streicher
We believe that the bug you reported is fixed in the latest version of
pybdsf, 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 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher (supplier of updated pybdsf 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: Sat, 08 Jun 2024 15:06:52 +0200
Source: pybdsf
Architecture: source
Version: 1.10.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Maintainers
Changed-By: Ole Streicher
Closes: 1063407
Changes:
pybdsf (1.10.3-3) unstable; urgency=medium
.
* Fix python3.12 build (Closes: #1063407)
* Push Standards-Version to 4.7.0. No changes needed
Checksums-Sha1:
617301a47f4536c2a98881bcf50e20395ff6ac97 2098 pybdsf_1.10.3-3.dsc
62b1d63fd6ebdf4da1b10cc0b479c251d485a8ed 7752 pybdsf_1.10.3-3.debian.tar.xz
Checksums-Sha256:
d1248c0cde891b2ad772db7b8048994fc58be06a4d3206f038b27aafe45e1bb3 2098
pybdsf_1.10.3-3.dsc
73c90702d95fb212db4c4b88a89da528c6032326b8c7d1d848bba98a611f1e40 7752
pybdsf_1.10.3-3.debian.tar.xz
Files:
634167389287f0d7644af75f7d8b482f 2098 python optional pybdsf_1.10.3-3.dsc
eb293059f0f50f518713a1ff019c68a7 7752 python optional
pybdsf_1.10.3-3.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmZkXRgACgkQcRWv0HcQ
3Peo2Q//Zq700VglPmco98YKlJKnHEBzH8opFwHw6syDScNddNkfRLiL8HyCeMf5
00A1UeUugjd2XUmVt7UiltDUHbIyYLMJF92zLo2f5PPlkIXlrTXQfSDALnxHVG5G
mB03gSX+6BHH40O5WpJ9FAmsO8N4tOxtszS7o49uPLxoz9F7PYmZ5KW6b1x82ItV
C14Pu0UcUdukU5p26R8cpZP2lGMQfgvrw5r1RU4rO2KvUclhnYacpXbPPuopGpTd
Vg/XJVSb4Wuw8X5TmZbouc+kuDBkfWMT6jedOQdjCuLYqz9D0l444F54
Processed: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
Processing control commands: > tags 1072733 moreinfo Bug #1072733 [sherlock,python3-sherlock] sherlock has an undeclared file conflict on /usr/lib/python3/dist-packages/sherlock/__init__.py Ignoring request to alter tags of bug #1072733 to the same tags previously set > reopen 1071007 = Bug #1071007 [sherlock] sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py Bug 1071007 is not marked as done; doing nothing. -- 1071007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071007 1072733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
Processing control commands:
> tags 1072733 moreinfo
Bug #1072733 [sherlock,python3-sherlock] sherlock has an undeclared file
conflict on /usr/lib/python3/dist-packages/sherlock/__init__.py
Added tag(s) moreinfo.
> reopen 1071007 =
Bug #1071007 {Done: Josenilson Ferreira da Silva }
[sherlock] sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions sherlock/0.14.4+git20240531.e5ad3c4-1.
--
1071007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071007
1072733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1072594: marked as done (goobox: FTBFS: UTF-8 "xFC" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 114.)
Your message dated Sat, 08 Jun 2024 11:04:06 +
with message-id
and subject line Bug#1072594: fixed in goobox 3.6.0-12
has caused the Debian Bug report #1072594,
regarding goobox: FTBFS: UTF-8 "xFC" does not map to Unicode at
/usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 114.
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.)
--
1072594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:goobox
Version: 3.6.0-11
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build
dh_update_autotools_config
dh_autoreconf
dh_auto_configure
cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8
meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1
The Meson build system
Version: 1.4.1
Source dir: /<>
Build dir: /<>/obj-x86_64-linux-gnu
Build type: native build
Project name: goobox
Project version: 3.6.0
C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-25) 13.2.0")
C linker for the host machine: cc ld.bfd 2.42
Host machine cpu family: x86_64
Host machine cpu: x86_64
Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1
Run-time dependency libcoverart found: YES 1.0.0
Configuring config.h using configuration
Build-time dependency gio-2.0 found: YES 2.80.2
Program /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas found: YES
(/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas)
Configuring org.gnome.Goobox.desktop.in using configuration
Program msgfmt found: YES (/usr/bin/msgfmt)
Program itstool found: YES (/usr/bin/itstool)
Program msgmerge found: YES (/usr/bin/msgmerge)
Program msgfmt found: YES (/usr/bin/msgfmt)
Program msginit found: YES (/usr/bin/msginit)
Program msgmerge found: YES (/usr/bin/msgmerge)
Program xgettext found: YES (/usr/bin/xgettext)
Library m found: YES
Run-time dependency threads found: YES
Run-time dependency glib-2.0 found: YES 2.80.2
Run-time dependency gthread-2.0 found: YES 2.80.2
Run-time dependency gtk+-3.0 found: YES 3.24.42
Run-time dependency gstreamer-1.0 found: YES 1.24.4
Run-time dependency libbrasero-media3 found: YES 3.12.3
Run-time dependency libmusicbrainz5 found: YES 5.1.0
Run-time dependency libdiscid found: YES 0.6.4
Compiler for C supports arguments -Wall: YES
Dependency gio-2.0 found: YES 2.80.2 (cached)
Program /usr/bin/glib-compile-resources found: YES
(/usr/bin/glib-compile-resources)
Dependency glib-2.0 found: YES 2.80.2 (cached)
Program /usr/bin/glib-genmarshal found: YES (/usr/bin/glib-genmarshal)
Message: configuration summary:
project: goobox 3.6.0
prefix: /usr
libcoverart: true
Build targets in project: 95
NOTICE: Future-deprecated features used:
* 0.56.0: {'meson.source_root'}
goobox 3.6.0
User defined options
buildtype : plain
libdir: lib/x86_64-linux-gnu
localstatedir : /var
prefix: /usr
sysconfdir: /etc
wrap_mode : nodownload
python.bytecompile: -1
Found ninja-1.12.1 at /usr/bin/ninja
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j2 -v
[1/104] /usr/bin/glib-compile-resources ../src/goobox.gresource.xml --sourcedir
../src --c-name goo --internal --generate --target src/goo-resources.c
--dependency-file src/goo-resources.c.d
[2/104] /usr/bin/glib-compile-resources ../src/goobox.gresource.xml --sourcedir
../src --c-name goo --internal --generate --target src/goo-resources.h
[3/104] /usr/bin/msgfmt ../help/ca/ca.po -o help/ca/goobox-ca.gmo
[4/104] /usr/bin/msgfmt ../help/cs/cs.po -o help/cs/goobox-cs.gmo
[5/104] /usr/bin/msgfmt ../help/de/de.po -o help/de/goobox-de.gmo
[6/104] /usr/bin/msgfmt ../help/el/el.po -o help/el/goobox-el.gmo
[7/104] /usr/bin/msgfmt ../help/es/es.po -o help/es/goobox-es.gmo
[8/104] /usr/bin/glib-genmarshal --prefix goo_marshal --output
src/goo-marshal.h --header ../src/goo-marshal.list --pragma-once
INFO: Reading ../src/goo-marshal.list...
[9/104] /usr/bin/msgfmt ../help/fr/fr.po -o help/fr/goobox-fr.gmo
[10/104] /usr/bin/msgfmt ../help/oc/oc.po -o help/oc/goobox-oc.gmo
[11/104] /usr/bin/msgfmt ../help/pl/pl.po -o help/pl/g
Bug#1064760: marked as done (tailspin: FTBFS: dh_auto_test: error: env DEB_BUILDDIR= /<>/tailspin-3.0.0\+dfsg/debian/dh-cargo/bin/cargo test returned exit code 101)
Your message dated Sat, 08 Jun 2024 07:05:03 +
with message-id
and subject line Bug#1064760: fixed in tailspin 3.0.1+dfsg-1
has caused the Debian Bug report #1064760,
regarding tailspin: FTBFS: dh_auto_test: error: env DEB_BUILDDIR=
/<>/tailspin-3.0.0\+dfsg/debian/dh-cargo/bin/cargo test returned exit
code 101
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.)
--
1064760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tailspin
Version: 3.0.0+dfsg-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cmark-gfm README.md > README.html
> cmark-gfm --to plaintext README.md > README.txt
> cmark-gfm CHANGELOG.md > CHANGELOG.html
> cmark-gfm --to plaintext CHANGELOG.md > CHANGELOG.txt
> dh execute_after_dh_auto_build --buildsystem cargo
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: WARNING: falling back to simply calling upstream cargo,
> because CARGO_HOME does not end with debian/cargo_home:
> Use of uninitialized value in concatenation (.) or string at
> /<>/debian/dh-cargo/lib/Debian/Debhelper/Buildsystem/cargo.pm
> line 296, line 2.
> env DEB_BUILDDIR=
> /<>/tailspin-3.0.0\+dfsg/debian/dh-cargo/bin/cargo test
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=8'] []
> ['-j8'] 0
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose',
> '-j8', '--target', 'x86_64-unknown-linux-gnu', '--release'],) {}
>Fresh unicode-ident v1.0.12
>Fresh autocfg v1.1.0
>Fresh cfg-if v1.0.0
>Fresh once_cell v1.19.0
>Fresh pin-project-lite v0.2.13
>Fresh memchr v2.7.1
>Fresh tracing-core v0.1.32
>Fresh proc-macro2 v1.0.76
>Fresh crossbeam-utils v0.8.19
>Fresh libc v0.2.152
>Fresh bitflags v1.3.2
>Fresh lazy_static v1.4.0
>Fresh quote v1.0.35
>Fresh utf8parse v0.2.1
>Fresh sharded-slab v0.1.4
>Fresh cc v1.0.83
>Fresh thread_local v1.1.4
>Fresh syn v2.0.48
>Fresh anstyle-parse v0.2.1
>Fresh anstyle-query v1.0.0
>Fresh anstyle v1.0.4
>Fresh smallvec v1.11.2
>Fresh colorchoice v1.0.0
>Fresh serde_derive v1.0.195
>Fresh log v0.4.20
>Fresh scopeguard v1.1.0
>Fresh anstream v0.6.7
>Fresh parking_lot_core v0.9.9
>Fresh serde v1.0.195
>Fresh lock_api v0.4.11
>Fresh mio v0.8.10
>Fresh tracing-subscriber v0.3.18
> warning: method `bold` is never used
> -->
> /<>/debian/cargo_registry/tracing-subscriber-0.3.18/src/fmt/format/mod.rs:1403:8
> |
> 1398 | impl Style {
> | -- method in this implementation
> ...
> 1403 | fn bold(self) -> Self {
> |
> |
> note: the lint level is defined here
> -->
> /<>/debian/cargo_registry/tracing-subscriber-0.3.18/src/lib.rs:191:5
> |
> 191 | unused,
> | ^^
> = note: `#[warn(dead_code)]` implied by `#[warn(unused)]`
>
>Fresh crossbeam-epoch v0.9.18
>Fresh getrandom v0.2.10
>Fresh tracing v0.1.40
> warning: `tracing-subscriber` (lib) generated 1 warning
>Fresh inotify-sys v0.1.5
>Fresh adler v1.0.2
>Fresh strsim v0.10.0
>Fresh gimli v0.28.1
>Fresh heck v0.4.1
>Fresh linux-raw-sys v0.4.12
>Fresh clap_lex v0.6.0
>Fresh option-ext v0.2.0
>Fresh hashbrown v0.12.3
>Fresh bitflags v2.4.2
>Fresh same-file v1.0.6
>Fresh miniz_oxide v0.7.1
>Fresh inotify v0.9.6
>Fresh addr2line v0.21.0
>Fresh dirs-sys v0.4.1
>Fresh clap_builder v4.4.18
>Fresh indexmap v1.9.3
>Fresh rustix v0.38.30
>Fresh walkdir
Bug#1063601: marked as done (tailspin FTBFS error: environment variable `CARGO_CHANNEL` not defined at compile time)
Your message dated Sat, 08 Jun 2024 07:05:03 +
with message-id
and subject line Bug#1063601: fixed in tailspin 3.0.1+dfsg-1
has caused the Debian Bug report #1063601,
regarding tailspin FTBFS error: environment variable `CARGO_CHANNEL` not
defined at compile time
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.)
--
1063601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tailspin
Version: 3.0.0+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=tailspin=amd64=3.0.0%2Bdfsg-1=1706195420=0
Running
`/<>/target/release/build/eyre-15058028a1ebd405/build-script-build`
[eyre 0.6.8] error[E0407]: method `backtrace` is not a member of trait `Error`
[eyre 0.6.8] -->
/<>/target/x86_64-unknown-linux-gnu/release/build/eyre-eb1eb971e427fb49/out/probe.rs:19:9
[eyre 0.6.8]|
[eyre 0.6.8] 19 | / fn backtrace() -> Option<> {
[eyre 0.6.8] 20 | | let backtrace = Backtrace::capture();
[eyre 0.6.8] 21 | | match backtrace.status() {
[eyre 0.6.8] 22 | | BacktraceStatus::Captured |
BacktraceStatus::Disabled | _ => {}
[eyre 0.6.8] 23 | | }
[eyre 0.6.8] 24 | | unimplemented!()
[eyre 0.6.8] 25 | | }
[eyre 0.6.8]| |_^ not a member of trait `Error`
[eyre 0.6.8]
[eyre 0.6.8] error[E0554]: `#![feature]` may not be used on the stable release
channel
[eyre 0.6.8] -->
/<>/target/x86_64-unknown-linux-gnu/release/build/eyre-eb1eb971e427fb49/out/probe.rs:2:16
[eyre 0.6.8] |
[eyre 0.6.8] 2 | #![feature(backtrace)]
[eyre 0.6.8] |^
[eyre 0.6.8]
[eyre 0.6.8] warning: the feature `backtrace` has been stable since 1.65.0 and
no longer requires an attribute to enable
[eyre 0.6.8] -->
/<>/target/x86_64-unknown-linux-gnu/release/build/eyre-eb1eb971e427fb49/out/probe.rs:2:16
[eyre 0.6.8] |
[eyre 0.6.8] 2 | #![feature(backtrace)]
[eyre 0.6.8] |^
[eyre 0.6.8] |
[eyre 0.6.8] = note: `#[warn(stable_features)]` on by default
[eyre 0.6.8]
[eyre 0.6.8] error: aborting due to 2 previous errors; 1 warning emitted
[eyre 0.6.8]
[eyre 0.6.8] Some errors have detailed explanations: E0407, E0554.
[eyre 0.6.8] For more information about an error, try `rustc --explain E0407`.
[eyre 0.6.8] cargo:rustc-cfg=track_caller
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: tailspin
Source-Version: 3.0.1+dfsg-1
Done: Jonas Smedegaard
We believe that the bug you reported is fixed in the latest version of
tailspin, 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 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Smedegaard (supplier of updated tailspin 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: Sat, 08 Jun 2024 08:35:10 +0200
Source: tailspin
Architecture: source
Version: 3.0.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard
Changed-By: Jonas Smedegaard
Closes: 1063601 1064760
Changes:
tailspin (3.0.1+dfsg-1) unstable; urgency=medium
.
[ upstream ]
* new release
.
[ Jonas Smedegaard ]
* update copyright info: fix file path
* fix patch 2002;
closes: bug#1063601, #1064760,
thanks to Sebastian Ramacher and Lucas Nussbaum
* add patches 2001_* to accept older versions of crates
* explicitly build-depend on package for crate nu-ansi-term
* declare compliance with Debian Policy 4.7.0
Checksums-Sha1:
aed32144ace2a30635964752ed770d4864e933b5 2669 tailspin_3.0.1+dfsg-1.dsc
dabf90030f3f85e504b962004ad6e19f3543faf3 55420 tailspin_3.0.1+dfsg.orig.tar.xz
b5ad78556537ab81d26885eaa4e3f95481803431 16880
tailspin_3.0.1+dfsg-1.debian.tar.xz
6776c32ecd48f650be494a5ab529735369c28c87 20051
tailspin_3.0.1+dfsg-1_amd64.buildinfo
Checksums-Sha256:
e3dfa3d49a49a66d5dcf3197465a1913afffeadc74453d038a8
Processed: ipython: Ubuntu patch for pytest 8 support
Processing control commands: > tags -1 patch Bug #1063945 [ipython] ipython: autopkgtest regression with pytest 8 Added tag(s) patch. -- 1063945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063945 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: ipykernel: Ubuntu patch for pytest 8 support
Processing control commands: > tags -1 patch Bug #1070112 [src:ipykernel] ipykernel: nose-style setup/teardown is no longer supported in pytest 8 Ignoring request to alter tags of bug #1070112 to the same tags previously set -- 1070112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: protontricks: Forward pytest 8 support patch from Ubuntu
Processing control commands: > tags -1 patch Bug #1063967 [protontricks] protontricks: autopkgtest regression with pytest 8 Added tag(s) patch. -- 1063967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063967 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1072789 is forwarded to https://bugs.launchpad.net/netplan/+bug/1987842
Processing commands for cont...@bugs.debian.org: > forwarded 1072789 https://bugs.launchpad.net/netplan/+bug/1987842 Bug #1072789 [netplan.io] netplan.io: CVE-2022-4968 Changed Bug forwarded-to-address to 'https://bugs.launchpad.net/netplan/+bug/1987842' from 'https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2065738'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1072789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1072789 ..., tagging 1072791, found 1072791 in 1.2.31+ds2-1
Processing commands for cont...@bugs.debian.org: > tags 1072789 + upstream Bug #1072789 [netplan.io] netplan.io: CVE-2022-4968 Added tag(s) upstream. > forwarded 1072789 > https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2065738 Bug #1072789 [netplan.io] netplan.io: CVE-2022-4968 Set Bug forwarded-to-address to 'https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2065738'. > tags 1072791 + upstream Bug #1072791 [kanboard] kanboard: CVE-2024-36399 Added tag(s) upstream. > found 1072791 1.2.31+ds2-1 Bug #1072791 [kanboard] kanboard: CVE-2024-36399 Marked as found in versions kanboard/1.2.31+ds2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1072789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072789 1072791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1072784, found 1072752 in 0.11.0+5-1.1, tagging 1072615, tagging 1070693 ..., tagging 1000118 ...
=1072586 1072594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072594 1072597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072597 1072598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072598 1072600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072600 1072601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072601 1072602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072602 1072603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072603 1072604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072604 1072608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072608 1072615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072615 1072643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072643 1072752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072752 1072762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072762 1072764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072764 1072767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072767 1072784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: nvidia-graphics-drivers: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092
ers: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092 Marked as found in versions nvidia-graphics-drivers/525.53-1. > found -1 530.30.02-1 Bug #1072792 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092 Marked as found in versions nvidia-graphics-drivers/530.30.02-1. > found -1 535.43.02-1 Bug #1072792 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092 Marked as found in versions nvidia-graphics-drivers/535.43.02-1. > found -1 545.23.06-1 Bug #1072792 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092 Marked as found in versions nvidia-graphics-drivers/545.23.06-1. > found -1 550.40.07-1 Bug #1072792 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092 The source 'nvidia-graphics-drivers' and version '550.40.07-1' do not appear to match any binary packages Marked as found in versions nvidia-graphics-drivers/550.40.07-1. > found -1 555.42.02-1 Bug #1072792 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092 The source 'nvidia-graphics-drivers' and version '555.42.02-1' do not appear to match any binary packages Marked as found in versions nvidia-graphics-drivers/555.42.02-1. -- 1072792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072792 1072793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072793 1072794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072794 1072795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072795 1072796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072796 1072797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072797 1072798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072798 1072799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072799 1072800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072158: marked as done (manpages-dev: missing Breaks+Replaces: glibc-doc (<< 2.37-16))
Your message dated Fri, 07 Jun 2024 21:49:43 +
with message-id
and subject line Bug#1072158: fixed in manpages 6.8-2
has caused the Debian Bug report #1072158,
regarding manpages-dev: missing Breaks+Replaces: glibc-doc (<< 2.37-16)
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.)
--
1072158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: manpages-dev
Version: 6.8-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.
>From the attached log (scroll to the bottom...):
Preparing to unpack .../manpages-dev_6.8-1_all.deb ...
Unpacking manpages-dev (6.8-1) ...
dpkg: error processing archive
/var/cache/apt/archives/manpages-dev_6.8-1_all.deb (--unpack):
trying to overwrite '/usr/share/man/man3/pthread_atfork.3.gz', which is also
in package glibc-doc 2.36-9+deb12u4
Errors were encountered while processing:
/var/cache/apt/archives/manpages-dev_6.8-1_all.deb
The corresponding change in src:glibc was:
glibc (2.37-16) unstable; urgency=medium
...
* debian/debhelper.in/glibc-doc.{links,manpages},
debian/local/manpages/pthread_*: drop the man pages for libpthread
functions, as they are now included in manpages-dev. Closes: #1068188.
* debian/control.in/main: update glibc-doc description following the removal
of the pthread manpages.
...
-- Aurelien Jarno Wed, 10 Apr 2024 00:15:44 +0200
cheers,
Andreas
glibc-doc=2.36-9+deb12u4_manpages-dev=6.8-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: manpages
Source-Version: 6.8-2
Done: Dr. Tobias Quathamer
We believe that the bug you reported is fixed in the latest version of
manpages, 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 1072...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dr. Tobias Quathamer (supplier of updated manpages 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: Fri, 07 Jun 2024 23:16:21 +0200
Source: manpages
Architecture: source
Version: 6.8-2
Distribution: unstable
Urgency: medium
Maintainer: Dr. Tobias Quathamer
Changed-By: Dr. Tobias Quathamer
Closes: 1072158
Changes:
manpages (6.8-2) unstable; urgency=medium
.
* Remove packages from Build-Depends to allow migration to testing.
There's no clear explanation in d/changelog or the commit
messages as to why all those packages should be needed.
However, it hinders testing migration (currently due to the
dependency on iwyu).
* Use wrap-and-sort -at
* Add missing Breaks and Replaces glibc-doc (<< 2.37-16) for manpages-dev.
Thanks to Andreas Beckmann (Closes: #1072158)
Checksums-Sha1:
352fc3a991ebd3fa3745971bdcff6197491f4c19 1948 manpages_6.8-2.dsc
43360b545852e95a1d142a70c4f10c6f29ed64c7 55740 manpages_6.8-2.debian.tar.xz
b3962b1576a8486d841cbbae1564f2a7166ab7b9 6435 manpages_6.8-2_amd64.buildinfo
Checksums-Sha256:
eadd4393e692d1a50e968c5ec0ec9bd74b10331739b0fa2441754f2d8b43cf86 1948
manpages_6.8-2.dsc
ef0da4251a30dd4e58a0eacd6c6fbc65a06514aff36782ef47709cabd2ace6f3 55740
manpages_6.8-2.debian.tar.xz
97f17e34894ec65d8c41606e3fe369fc97488512bc30e9a952794ae5814a7b9a 6435
manpages_6.8-2_amd64.buildinfo
Files:
42ba0ca672e4c084e00474f3df5b9ff6 1948 doc standard manpages_6.8-2.dsc
288a607e945a18f1241dac5549bb3b49 55740 doc standard
manpages_6.8-2.debian.tar.xz
298e7e534dfc4fc08d0f497038405fc2 6435 doc standard
manpages_6.8-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAmZje48ACgkQ
Bug#1072767: marked as done (rust-shared-child: FTBFS: failing tests)
Your message dated Fri, 07 Jun 2024 21:35:51 +
with message-id
and subject line Bug#1072767: fixed in rust-shared-child 1.0.0-2
has caused the Debian Bug report #1072767,
regarding rust-shared-child: FTBFS: failing tests
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.)
--
1072767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rust-shared-child
Version: 1.0.0-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --buildsystem cargo
dh_update_autotools_config -O--buildsystem=cargo
dh_autoreconf -O--buildsystem=cargo
dh_auto_configure -O--buildsystem=cargo
debian cargo wrapper: options, profiles, parallel, lto: ['parallel=2'] []
['-j2'] 0
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into
/<>/debian/cargo_registry/
dh_auto_build -O--buildsystem=cargo
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
dh_auto_test -- test --all
debian cargo wrapper: options, profiles, parallel, lto: ['parallel=2'] []
['-j2'] 0
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose', '-j2',
'--target', 'x86_64-unknown-linux-gnu', '--all'],) {}
Compiling libc v0.2.155
Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build
CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/libc-0.2.155
CARGO_PKG_AUTHORS='The Rust Project Developers' CARGO_PKG_DESCRIPTION='Raw FFI bindings to
platform libraries like libc.
' CARGO_PKG_HOMEPAGE='https://github.com/rust-lang/libc' CARGO_PKG_LICENSE='MIT OR Apache-2.0' CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=libc
CARGO_PKG_README=README.md CARGO_PKG_REPOSITORY='https://github.com/rust-lang/libc' CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.2.155
CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=2 CARGO_PKG_VERSION_PATCH=155 CARGO_PKG_VERSION_PRE=''
LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc --crate-name build_script_build
/<>/debian/cargo_registry/libc-0.2.155/build.rs --error-format=json
--json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 --cfg
'feature="default"' --cfg 'feature="std"' -C metadata=7a2d83bb2c65f8a7 -C extra-filename=-7a2d83bb2c65f8a7 --out-dir
/<>/target/debug/build/libc-7a2d83bb2c65f8a7 -L dependency=/<>/target/debug/deps --cap-lints warn`
Running `CARGO=/usr/bin/cargo CARGO_CFG_PANIC=unwind CARGO_CFG_TARGET_ARCH=x86_64
CARGO_CFG_TARGET_ENDIAN=little CARGO_CFG_TARGET_ENV=gnu CARGO_CFG_TARGET_FAMILY=unix
CARGO_CFG_TARGET_FEATURE=fxsr,sse,sse2 CARGO_CFG_TARGET_HAS_ATOMIC=16,32,64,8,ptr CARGO_CFG_TARGET_OS=linux
CARGO_CFG_TARGET_POINTER_WIDTH=64 CARGO_CFG_TARGET_VENDOR=unknown CARGO_CFG_UNIX=''
CARGO_ENCODED_RUSTFLAGS='-Cdebuginfo=2--cap-lintswarn-Clinker=x86_64-linux-gnu-gcc-Clink-arg=-Wl,-z,relro--remap-path-prefix/<>=/usr/share/cargo/registry/shared-child-1.0.0--remap-path-prefix/<>/debian/cargo_registry=/usr/share/cargo/registry'
CARGO_FEATURE_DEFAULT=1 CARGO_FEATURE_STD=1
CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/libc-0.2.155 CARGO_PKG_AUTHORS='The Rust
Project Developers' CARGO_PKG_DESCRIPTION='Raw FFI bindings to platform libraries like libc.
' CARGO_PKG_HOMEPAGE='https://github.com/rust-lang/libc' CARGO_PKG_LICENSE='MIT OR Apache-2.0' CARGO_PKG_LICENSE_FILE=''
CARGO_PKG_NAME=libc CARGO_PKG_README=README.md CARGO_PKG_REPOSITORY='https://github.com/rust-lang/libc'
CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.2.155 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=2
CARGO_PKG_VERSION_PATCH=155 CARGO_PKG_VERSION_PRE='' DEBUG=true HOST=x86_64-unknown-linux-gnu
LD_LIBRARY_PATH='/<>/target/debug/deps:/<>/target/debug:/usr/lib/rustlib/x86_64-unknown-linux-gnu/lib'
NUM_JOBS=2 OPT_LEVEL=0
OUT_DIR=/<>/target/x86_64-unknown-linux-gnu/debug/build/libc-d21e4685ad86fcfe/out PROFILE=debug
RUSTC=rustc RUSTDOC=rustdoc TARGET=x86_64-unknown-linux-gnu
/<>/target/debug/build/libc-7a2d83bb2c65f8a7/build-script-build`
[libc 0.2.155] cargo:rerun-if-changed=build.rs
Processed: resend
Processing commands for cont...@bugs.debian.org: > clone 909352 -1 Bug #909352 [src:squeak-plugins-scratch] Is squeak-plugins-scratch still useful? Bug 909352 cloned as bug 1072784 > reassign -1 ftp.debian.org Bug #1072784 [src:squeak-plugins-scratch] Is squeak-plugins-scratch still useful? Bug reassigned from package 'src:squeak-plugins-scratch' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #1072784 to the same values previously set Ignoring request to alter fixed versions of bug #1072784 to the same values previously set > severity -1 normal Bug #1072784 [ftp.debian.org] Is squeak-plugins-scratch still useful? Severity set to 'normal' from 'serious' > retitle -1 RM: squeak-plugins-scratch -- RoQA; obsolete plugin Bug #1072784 [ftp.debian.org] Is squeak-plugins-scratch still useful? Changed Bug title to 'RM: squeak-plugins-scratch -- RoQA; obsolete plugin' from 'Is squeak-plugins-scratch still useful?'. > affects -1 src:squeak-plugins-scratch Bug #1072784 [ftp.debian.org] RM: squeak-plugins-scratch -- RoQA; obsolete plugin Added indication that 1072784 affects src:squeak-plugins-scratch > thanks Stopping processing here. Please contact me if you need assistance. -- 1072784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072784 909352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:aardvark-dns: fails to migrate to testing for too long: unstatifiable Depends on s390x
Processing control commands: > close -1 1.4.0-5.1 Bug #1072783 [src:aardvark-dns] src:aardvark-dns: fails to migrate to testing for too long: unstatifiable Depends on s390x Marked as fixed in versions aardvark-dns/1.4.0-5.1. Bug #1072783 [src:aardvark-dns] src:aardvark-dns: fails to migrate to testing for too long: unstatifiable Depends on s390x Marked Bug as done -- 1072783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: guacamole bugs fixed by NMU
Processing commands for cont...@bugs.debian.org: > fixed 1054082 guacd/1.3.0-1.3 Bug #1054082 [src:guacamole-server] guacd: installs guacd.service twice when dh_installsystemd installs units to /usr The source guacd and version 1.3.0-1.3 do not appear to match any binary packages Marked as fixed in versions guacd/1.3.0-1.3. > fixed 1065145 guacd/1.3.0-1.3 Bug #1065145 [guacd] guacd: internal aliasing conflict on guacd.service The source guacd and version 1.3.0-1.3 do not appear to match any binary packages Marked as fixed in versions guacd/1.3.0-1.3. > close 1065145 Bug #1065145 [guacd] guacd: internal aliasing conflict on guacd.service Marked Bug as done > close 1054082 Bug #1054082 [src:guacamole-server] guacd: installs guacd.service twice when dh_installsystemd installs units to /usr Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. -- 1054082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054082 1065145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:transaction: fails to migrate to testing for too long: uploader built arch:all binary
Processing control commands: > close -1 4.0-1 Bug #1072780 [src:transaction] src:transaction: fails to migrate to testing for too long: uploader built arch:all binary Marked as fixed in versions transaction/4.0-1. Bug #1072780 [src:transaction] src:transaction: fails to migrate to testing for too long: uploader built arch:all binary Marked Bug as done -- 1072780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072780 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:golang-golang-x-tools: fails to migrate to testing for too long: triggers autopkgtest issues
Processing control commands: > close -1 1:0.20.0+ds-1 Bug #1072779 [src:golang-golang-x-tools] src:golang-golang-x-tools: fails to migrate to testing for too long: triggers autopkgtest issues Marked as fixed in versions golang-golang-x-tools/1:0.20.0+ds-1. Bug #1072779 [src:golang-golang-x-tools] src:golang-golang-x-tools: fails to migrate to testing for too long: triggers autopkgtest issues Marked Bug as done -- 1072779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051615: marked as done (rust-minijinja: Uninstallable dependencies)
Your message dated Fri, 7 Jun 2024 14:44:37 -0400 with message-id and subject line Bug#1051615 closed by Debian FTP Masters (reply to Jelmer Vernooij ) (Bug#1051615: fixed in rust-minijinja 1.0.3-1 has caused the Debian Bug report #1051615, regarding rust-minijinja: Uninstallable dependencies 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.) -- 1051615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-minijinja Version: 0.34.0-1 Severity: serious rust-minijinja is uninstallable (and therefore unstable to migrate to Testing) because it depends on librust-aho-corasick-1-dev but aho-corasick is only at version 0.7.19 in Debian. It also depends on librust-v-htmlescape-0.15+default-dev but rust-v-htmlescape isn't available in Debian. Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Version: 1.0.3-1 Oops, I didn't see that you did an upload just minutes ago to fix this issue. Thank you, Jeremy Bícha--- End Message ---
Processed: Re: rust-minijinja: Uninstallable dependencies
Processing control commands:
> reopen -1
Bug #1051615 {Done: Jelmer Vernooij } [src:rust-minijinja]
rust-minijinja: Uninstallable dependencies
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions rust-minijinja/1.0.3-1.
--
1051615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1051615: marked as done (rust-minijinja: Uninstallable dependencies)
Your message dated Fri, 07 Jun 2024 18:22:53 + with message-id and subject line Bug#1051615: fixed in rust-minijinja 1.0.3-1 has caused the Debian Bug report #1051615, regarding rust-minijinja: Uninstallable dependencies 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.) -- 1051615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-minijinja Version: 0.34.0-1 Severity: serious rust-minijinja is uninstallable (and therefore unstable to migrate to Testing) because it depends on librust-aho-corasick-1-dev but aho-corasick is only at version 0.7.19 in Debian. It also depends on librust-v-htmlescape-0.15+default-dev but rust-v-htmlescape isn't available in Debian. Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: rust-minijinja Source-Version: 1.0.3-1 Done: Jelmer Vernooij We believe that the bug you reported is fixed in the latest version of rust-minijinja, 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 1051...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jelmer Vernooij (supplier of updated rust-minijinja 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: Fri, 07 Jun 2024 18:44:20 +0100 Source: rust-minijinja Architecture: source Version: 1.0.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Jelmer Vernooij Closes: 1051615 Changes: rust-minijinja (1.0.3-1) unstable; urgency=medium . * Package minijinja 1.0.3 from crates.io using debcargo 2.6.0. Closes: #1051615 Checksums-Sha1: 8e0fc6a0c0568d009584cb0b32ef660b108d94b6 2111 rust-minijinja_1.0.3-1.dsc 0e52e7aee93796bc3b9b8550c7d0d519d9482dd4 127652 rust-minijinja_1.0.3.orig.tar.gz 0e09a3267613c5b472db4ff3391fb9aba8e01b4b 3228 rust-minijinja_1.0.3-1.debian.tar.xz b94d20b793d874e7aece9683dd68ce56f228118c 8529 rust-minijinja_1.0.3-1_source.buildinfo Checksums-Sha256: 8db3b9e6e3ecfe45d8baf7f02b52d2a852bd8e148217e06cf1b9ed88df358ca9 2111 rust-minijinja_1.0.3-1.dsc f40870a194358132836de5c67e5038c279de3bff7a05f5da201ed13f6064b979 127652 rust-minijinja_1.0.3.orig.tar.gz 8664ef04f669a4327cc98a68e6b0b361c597de1efa337fb10bd3603d1ee4142d 3228 rust-minijinja_1.0.3-1.debian.tar.xz 3ab46981e7338597e926706de6fdbbdb6baae9ac5bf7a66012bbe9a3e7a0200f 8529 rust-minijinja_1.0.3-1_source.buildinfo Files: 71a7e8776a5c8363ef4f9313fcb95fa0 2111 rust optional rust-minijinja_1.0.3-1.dsc 6651a17cb96a1fdf5a6dc707948c22d5 127652 rust optional rust-minijinja_1.0.3.orig.tar.gz 87c0a8f89b18aa925c36e1ba5c87a52a 3228 rust optional rust-minijinja_1.0.3-1.debian.tar.xz f4ad1bab3156fd9782872c4271278fa2 8529 rust optional rust-minijinja_1.0.3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEgIoEfJX3ae+y722SMG8hYYBCUGYFAmZjRvgACgkQMG8hYYBC UGaqyAf+IBmXs7CobuyDsPnK9pkvPf/avs2ZJUsGmUQC6QBJ6xNrsWpkeJ9/Vwxo T1HZY136jfJRyQueOS6JXxLUdnvrSJXoxf7QoEe1YPW0CC2v/lcJMd3mI7PnhmVS AoYYEJxUKaHnInsfDRHOwRZXNS2pztnUZDv614CqHtSiy5ucP6TtoqhU910XJivz 11Zt4oaDkpUw+XbdHqAXUPgFwkesvjQzgU11EWFgfsCg/oK6MnaBy7oyrXQN8jui 1OAx4+KZNeBT/G5q4Z+C9c9BWCPTwwJRfD8EysGLGldZhcXdXO9nmRIbJYsbnnOa EO8pfY5P+9VQGmuUFe4IUplANifjjg== =vt4c -END PGP SIGNATURE- pgpMj0qHaUS0x.pgp Description: PGP signature --- End Message ---
Bug#1072347: marked as done (luajit2: should not be shipped with trixie)
Your message dated Fri, 07 Jun 2024 17:50:28 + with message-id and subject line Bug#1069780: Removed package(s) from unstable has caused the Debian Bug report #1072347, regarding luajit2: should not be shipped with trixie 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.) -- 1072347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: luajit2 Version: 2.1-20230410-1 Severity: serious src:luajit2 now duplicates src:luajit, see #1069780. As such it should not be part of trixie. --- End Message --- --- Begin Message --- Version: 2.1-20230410-1+rm Dear submitter, as the package luajit2 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1069780 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
