Bug#1021032: vlc: playing mp4 videos results in a black screen
On Mon, 03 Oct 2022 03:07:30 +0100 Lyndon Brown wrote: > I have no idea at this time what the relevant difference is between > them that's causing this. Update. So first of all I wondered whether differences in configure options could be relevant. Before, I'd just used --disable-skins2. So I rebuilt the upstream codebase with the following to duplicate much of the debian package config: ../configure --disable-skins2 --config-cache -- disable-update-check --enable-fast-install --enable-a52 --enable-aa -- enable-aribsub --enable-avahi --enable-bluray --enable-caca --enable- chromaprint --enable-chromecast --enable-dav1d --enable-dbus --enable- dca --enable-dvbpsi --enable-dvdnav --enable-faad --enable-flac -- enable-fluidsynth --enable-freetype --enable-fribidi --enable-gles2 -- enable-gnutls --enable-harfbuzz --enable-jack --enable-kate --enable- libass --enable-libmpeg2 --enable-libxml2 --enable-lirc --enable-mad -- enable-matroska --enable-mod --enable-mpc --enable-mpg123 --enable-mtp --enable-ncurses --enable-notify --enable-ogg --enable-opus --enable- pulse --enable-qt --enable-realrtsp --enable-samplerate --enable-sdl- image --enable-sftp --enable-shine --enable-shout --enable-skins2 -- enable-sndio --enable-soxr --enable-spatialaudio --enable-speex -- enable-srt --enable-svg --enable-svgdec --enable-taglib --enable-theora --enable-twolame --enable-upnp --enable-vdpau --enable-vnc --enable- vorbis --enable-x264 --enable-x265 --enable-zvbi --disable-aom -- disable-crystalhd --disable-d3d11va --disable-decklink --disable- directx --disable-dsm --disable-dxva2 --disable-fdkaac --disable- fluidlite --disable-freerdp --disable-goom --disable-gst-decode -- disable-libtar --disable-libva --disable-live555 --disable-macosx -- disable-macosx-avfoundation --disable-macosx-qtkit --disable-mfx -- disable-microdns --disable-opencv --disable-projectm --disable- schroedinger --disable-sparkle --disable-telx --disable-vpx --disable- vsxu --disable-wasapi This made no difference; it still worked fine unlike the debian package rebuild. So then I wondered about the possible affect of old artefacts within the build directory of the upstream code build. (It wasn't clean, since I'd previously used it for VLC dev work). Interestingly, deleting the build directory to create a fresh start DID make a difference. Using the same big configure command as above I now encounter the same issue as the debian package. This obviously might suggest that the "dirty" build directory contained a plugin binary from a previous build and this was causing some difference. I wondered about your use of --disable-libva and so with that removed from the above configure command, it was back to working again. So long story short, the problem would seem to be connected somehow to your use of --disable-libva.
Bug#1021153: marked as done (node-schema-utils: ftbfs due to changed output formatting/escaping)
Your message dated Mon, 03 Oct 2022 04:49:37 +
with message-id
and subject line Bug#1021153: fixed in node-schema-utils 3.1.1~ds-2
has caused the Debian Bug report #1021153,
regarding node-schema-utils: ftbfs due to changed output formatting/escaping
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.)
--
1021153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-schema-utils
Version: 3.1.1~ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Control: found -1 4.0.0~ds-1
Hi,
node-schema-utils recently started to FTBFS in sid (but not yet in
testing):
dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/schema-utils
/bin/sh -ex debian/tests/pkg-js/test
+ jest --ci test/
PASS test/range.test.js
PASS test/hints.test.js
PASS test/api.test.js
FAIL test/index.test.js (6.825 s)
● Validation › should fail validation for postFormatter #1
expect(received).toMatchSnapshot()
Snapshot name: `Validation should fail validation for postFormatter #1 1`
- Snapshot - 1
+ Received + 1
@@ -5,11 +5,11 @@
For loader options: webpack >= v2.0.0 no longer allows custom
properties in configuration.
Loaders should be updated to allow passing options via loader
options in module.rules.
Until loaders are updated one can use the LoaderOptionsPlugin to
pass these options to the loader:
plugins: [
new webpack.LoaderOptionsPlugin({
- // test: /\\.xxx$/, // may apply this only for some modules
+ // test: /\.xxx$/, // may apply this only for some modules
options: {
minify: …
}
})
]"
413 | minify: true,
414 | },
> 415 | (msg) => expect(msg).toMatchSnapshot(),
| ^
416 | {
417 | name: "Webpack",
418 | baseDataPath: "configuration",
at fn (test/index.test.js:415:26)
at Object. (test/index.test.js:45:9)
● Validation › should fail validation for postFormatter #2
expect(received).toMatchSnapshot()
Snapshot name: `Validation should fail validation for postFormatter #2 1`
- Snapshot - 1
+ Received + 1
"Invalid configuration object. Webpack has been initialized using a
configuration object that does not match the API schema.
- - configuration.output.filename: A relative path is expected. However,
the provided value \"/bar\" is an absolute path!
+ - configuration.output.filename: A relative path is expected. However,
the provided value "/bar" is an absolute path!
Please use output.path to specify absolute path and output.filename
for the file name."
453 | },
454 | },
> 455 | (msg) => expect(msg).toMatchSnapshot(),
| ^
456 | {
457 | name: "Webpack",
458 | baseDataPath: "configuration",
at fn (test/index.test.js:455:26)
at Object. (test/index.test.js:45:9)
● Validation › should fail validation for ! in path
expect(received).toMatchSnapshot()
Snapshot name: `Validation should fail validation for ! in path 1`
- Snapshot - 1
+ Received + 1
"Invalid configuration object. Object has been initialized using a
configuration object that does not match the API schema.
- - configuration.output.path: The provided value \"/somepath/!test\"
contains exclamation mark (!) which is not allowed because it's reserved for
loader syntax.
+ - configuration.output.path: The provided value "/somepath/!test"
contains exclamation mark (!) which is not allowed because it's reserved for
loader syntax.
-> The output directory as **absolute path** (required)."
609 | },
610 | },
> 611 | (msg) => expect(msg).toMatchSnapshot()
| ^
612 | );
613 |
614 | createFailedTestCase(
at fn (test/index.test.js:611:26)
at Object. (test/index.test.js:45:9)
...
Some output formatting (escaping) seems to have changed.
Andreas
node-schema-utils.sid.build.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: node-schema-utils
Source-Version: 3.1.1~ds-2
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
node-schema-utils, which is due to be installed in the Debian FTP archive.
A summary of the
Bug#1020024: marked as pending in pydoctor
Control: tag -1 pending Hello, Bug #1020024 in pydoctor reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/pydoctor/-/commit/10fcac04892784c9b8d8e7ddb51ae37400ecbf20 Depend on python3-filelock rather than python3-lockfile, following python3-cachecontrol. Closes: #1020024 (this message was generated automatically) -- Greetings https://bugs.debian.org/1020024
Processed: Bug#1020024 marked as pending in pydoctor
Processing control commands: > tag -1 pending Bug #1020024 [src:pydoctor] git-buildpackage: FTBFS: ModuleNotFoundError: No module named 'filelock' Added tag(s) pending. -- 1020024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020024 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021032: vlc: playing mp4 videos results in a black screen
On Mon, 03 Oct 2022 00:52:41 +0100 Lyndon Brown wrote: > On Mon, 2022-10-03 at 01:24 +0200, Sebastian Ramacher wrote: > > On 2022-10-03 00:09:25 +0100, Lyndon Brown wrote: > > > As you can see, mostly minor Qt updates. > > > > But those are the only packages relevant for vlc in your upgrade. So > > it's probably Qt breaking vlc … and my test with 3.0.18 rc2 just > > worked > > as I built it with the current Qt version in unstable. > > > > Cheers > > Indeed, that's what I'm wondering. > > Note that in the Ubuntu bug report > (https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1991418) Remi said > that he could see the problem in Sid, but failed to reproduce with a > custom rebuild of VLC. > > I haven't tried a local package rebuild just yet to see if that's all > that's needed. I may try one shortly unless you beat me to it. Will be > great if so. Hmm, so firstly I started with the upstream 3.0.x branch, at the 3.0.17.3 tagged commit 426513d88e3e3dc671434db8e724ee5d1b7e1038 (not finding a 3.0.17.4 tag). I cherry-picked two build fixes, 2202c892c8dc1381b596c53c2ebd3ca680061f95 (dav1d) and b689202d9f1621e82acb0976b6bb31455735a535 (caca). I compiled this successfully, and it just works, indicating that indeed just a rebuild is needed. However, I then rebuilt the debian package itself, and installed all of the rebuilt versions of every vlc package I had installed, and it still exhibits the issue. (I used these instructions: https://www.ducea.com/2008/03/06/howto-recompile-debian-packages/). I have no idea at this time what the relevant difference is between them that's causing this.
Bug#1021032: vlc: playing mp4 videos results in a black screen
On Mon, 2022-10-03 at 01:24 +0200, Sebastian Ramacher wrote: > On 2022-10-03 00:09:25 +0100, Lyndon Brown wrote: > > As you can see, mostly minor Qt updates. > > But those are the only packages relevant for vlc in your upgrade. So > it's probably Qt breaking vlc … and my test with 3.0.18 rc2 just > worked > as I built it with the current Qt version in unstable. > > Cheers Indeed, that's what I'm wondering. Note that in the Ubuntu bug report (https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1991418) Remi said that he could see the problem in Sid, but failed to reproduce with a custom rebuild of VLC. I haven't tried a local package rebuild just yet to see if that's all that's needed. I may try one shortly unless you beat me to it. Will be great if so.
Bug#1021032: vlc: playing mp4 videos results in a black screen
On 2022-10-03 00:09:25 +0100, Lyndon Brown wrote: > Control: retitle -1 vlc: playing videos results in a black screen > Control: severity -1 grave > > Ran into this today after installing daily Sid updates. Was fine > yesterday. I think that some updates from yesterday, or perhaps the day > before may have been delayed until today due to a dependency issue, so > that may explain why I've only just experienced this. > > This is not limited to mp4, I've also tried avi & mpg. > > Logs indicate video format conversion failure, as per the original > reporter's logs. > > >From my apt log, these are the package updates that were installed > today: > > - autoconf-archive:amd64 (20220903-1, 20220903-2) > - chromium:amd64 (106.0.5249.61-1, 106.0.5249.91-1) > - chromium-common:amd64 (106.0.5249.61-1, 106.0.5249.91-1) > - chromium-sandbox:amd64 (106.0.5249.61-1, 106.0.5249.91-1) > - flex:amd64 (2.6.4-8, 2.6.4-8.1) > - libexempi8:amd64 (2.6.2-1, 2.6.2-2) > - libfido2-1:amd64 (1.11.0-1+b1, 1.12.0-1) > - libfl2:amd64 (2.6.4-8, 2.6.4-8.1) > - libfl-dev:amd64 (2.6.4-8, 2.6.4-8.1) > - libmediastreamer11:amd64 (1:5.0.37+dfsg-4, 1:5.0.37+dfsg-4+b1) > - libopenmpt0:amd64 (0.6.5-1, 0.6.6-1) > - libopenmpt-dev:amd64 (0.6.5-1, 0.6.6-1) > - libpixie-java:amd64 (1:1.1.6-4, 1:1.1.6-5) > - libqpdf29:amd64 (11.1.0-1, 11.1.1-1) > - libqt5concurrent5:amd64 (5.15.4+dfsg-5, 5.15.6+dfsg-2) > - libqt5core5a:amd64 (5.15.4+dfsg-5, 5.15.6+dfsg-2) > - libqt5dbus5:amd64 (5.15.4+dfsg-5, 5.15.6+dfsg-2) > - libqt5designer5:amd64 (5.15.4-2+b1, 5.15.6-2) > - libqt5gui5:amd64 (5.15.4+dfsg-5, 5.15.6+dfsg-2) > - libqt5multimedia5:amd64 (5.15.4-2, 5.15.6-2) > - libqt5multimediagsttools5:amd64 (5.15.4-2, 5.15.6-2) > - libqt5multimediaquick5:amd64 (5.15.4-2, 5.15.6-2) > - libqt5multimediawidgets5:amd64 (5.15.4-2, 5.15.6-2) > - libqt5network5:amd64 (5.15.4+dfsg-5, 5.15.6+dfsg-2) > - libqt5opengl5:amd64 (5.15.4+dfsg-5, 5.15.6+dfsg-2) > - libqt5opengl5-dev:amd64 (5.15.4+dfsg-5, 5.15.6+dfsg-2) > - libqt5printsupport5:amd64 (5.15.4+dfsg-5, 5.15.6+dfsg-2) > - libqt5qml5:amd64 (5.15.4+dfsg-4, 5.15.6+dfsg-2) > - libqt5qmlmodels5:amd64 (5.15.4+dfsg-4, 5.15.6+dfsg-2) > - libqt5qmlworkerscript5:amd64 (5.15.4+dfsg-4, 5.15.6+dfsg-2) > - libqt5quick5:amd64 (5.15.4+dfsg-4, 5.15.6+dfsg-2) > - libqt5quickcontrols2-5:amd64 (5.15.4+dfsg-2, 5.15.6+dfsg-2) > - libqt5quickparticles5:amd64 (5.15.4+dfsg-4, 5.15.6+dfsg-2) > - libqt5quickshapes5:amd64 (5.15.4+dfsg-4, 5.15.6+dfsg-2) > - libqt5quicktemplates2-5:amd64 (5.15.4+dfsg-2, 5.15.6+dfsg-2) > - libqt5quicktest5:amd64 (5.15.4+dfsg-4, 5.15.6+dfsg-2) > - libqt5quickwidgets5:amd64 (5.15.4+dfsg-4, 5.15.6+dfsg-2) > - libqt5sql5:amd64 (5.15.4+dfsg-5, 5.15.6+dfsg-2) > - libqt5sql5-sqlite:amd64 (5.15.4+dfsg-5, 5.15.6+dfsg-2) > - libqt5svg5:amd64 (5.15.4-2, 5.15.6-2) > - libqt5svg5-dev:amd64 (5.15.4-2, 5.15.6-2) > - libqt5test5:amd64 (5.15.4+dfsg-5, 5.15.6+dfsg-2) > - libqt5texttospeech5:amd64 (5.15.4-2, 5.15.6-2) > - libqt5waylandclient5:amd64 (5.15.4-2, 5.15.6-2) > - libqt5waylandclient5-dev:amd64 (5.15.4-2, 5.15.6-2) > - libqt5waylandcompositor5:amd64 (5.15.4-2, 5.15.6-2) > - libqt5waylandcompositor5-dev:amd64 (5.15.4-2, 5.15.6-2) > - libqt5widgets5:amd64 (5.15.4+dfsg-5, 5.15.6+dfsg-2) > - libqt5x11extras5:amd64 (5.15.4-2, 5.15.6-2) > - libqt5x11extras5-dev:amd64 (5.15.4-2, 5.15.6-2) > - libqt5xml5:amd64 (5.15.4+dfsg-5, 5.15.6+dfsg-2) > - libqt6concurrent6:amd64 (6.3.1+dfsg-9, 6.3.1+dfsg-10) > - libqt6core6:amd64 (6.3.1+dfsg-9, 6.3.1+dfsg-10) > - libqt6dbus6:amd64 (6.3.1+dfsg-9, 6.3.1+dfsg-10) > - libqt6gui6:amd64 (6.3.1+dfsg-9, 6.3.1+dfsg-10) > - libqt6network6:amd64 (6.3.1+dfsg-9, 6.3.1+dfsg-10) > - libqt6opengl6:amd64 (6.3.1+dfsg-9, 6.3.1+dfsg-10) > - libqt6openglwidgets6:amd64 (6.3.1+dfsg-9, 6.3.1+dfsg-10) > - libqt6printsupport6:amd64 (6.3.1+dfsg-9, 6.3.1+dfsg-10) > - libqt6shadertools6:amd64 (6.3.1-2, 6.3.1-3) > - libqt6sql6:amd64 (6.3.1+dfsg-9, 6.3.1+dfsg-10) > - libqt6sql6-sqlite:amd64 (6.3.1+dfsg-9, 6.3.1+dfsg-10) > - libqt6test6:amd64 (6.3.1+dfsg-9, 6.3.1+dfsg-10) > - libqt6widgets6:amd64 (6.3.1+dfsg-9, 6.3.1+dfsg-10) > - libqt6xml6:amd64 (6.3.1+dfsg-9, 6.3.1+dfsg-10) > - linphone-desktop:amd64 (4.3.2-2, 4.3.2-2+b1) > - qml:amd64 (5.15.4+dfsg-4, 5.15.6+dfsg-2) > - qml-module-qtgraphicaleffects:amd64 (5.15.4-2, 5.15.6-2) > - qml-module-qt-labs-platform:amd64 (5.15.4+dfsg-2, 5.15.6+dfsg-2) > - qml-module-qtmultimedia:amd64 (5.15.4-2, 5.15.6-2) > - qml-module-qtqml:amd64 (5.15.4+dfsg-4, 5.15.6+dfsg-2) > - qml-module-qtquick2:amd64 (5.15.4+dfsg-4, 5.15.6+dfsg-2) > - qml-module-qtquick-controls2:amd64 (5.15.4+dfsg-2, 5.15.6+dfsg-2) > - qml-module-qtquick-controls:amd64 (5.15.4-2, 5.15.6-2) > - qml-module-qtquick-dialogs:amd64 (5.15.4-2, 5.15.6-2) > - qml-module-qtquick-extras:amd64 (5.15.4-2, 5.15.6-2) > - qml-module-qtquick-layouts:amd64 (5.15.4+dfsg-4, 5.15.6+dfsg-2) > - qml-module-qtquick-privatewidgets:amd64 (5.15.4-2, 5.15.6-2) > -
Processed: Re: Bug#1021032: vlc: playing mp4 videos results in a black screen
Processing control commands: > retitle -1 vlc: playing videos results in a black screen Bug #1021032 [vlc] vlc: playing mp4 videos results in a black screen Changed Bug title to 'vlc: playing videos results in a black screen' from 'vlc: playing mp4 videos results in a black screen'. > severity -1 grave Bug #1021032 [vlc] vlc: playing videos results in a black screen Severity set to 'grave' from 'important' -- 1021032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021153: node-schema-utils: ftbfs due to changed output formatting/escaping
Package: node-schema-utils
Version: 3.1.1~ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Control: found -1 4.0.0~ds-1
Hi,
node-schema-utils recently started to FTBFS in sid (but not yet in
testing):
dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/schema-utils
/bin/sh -ex debian/tests/pkg-js/test
+ jest --ci test/
PASS test/range.test.js
PASS test/hints.test.js
PASS test/api.test.js
FAIL test/index.test.js (6.825 s)
● Validation › should fail validation for postFormatter #1
expect(received).toMatchSnapshot()
Snapshot name: `Validation should fail validation for postFormatter #1 1`
- Snapshot - 1
+ Received + 1
@@ -5,11 +5,11 @@
For loader options: webpack >= v2.0.0 no longer allows custom
properties in configuration.
Loaders should be updated to allow passing options via loader
options in module.rules.
Until loaders are updated one can use the LoaderOptionsPlugin to
pass these options to the loader:
plugins: [
new webpack.LoaderOptionsPlugin({
- // test: /\\.xxx$/, // may apply this only for some modules
+ // test: /\.xxx$/, // may apply this only for some modules
options: {
minify: …
}
})
]"
413 | minify: true,
414 | },
> 415 | (msg) => expect(msg).toMatchSnapshot(),
| ^
416 | {
417 | name: "Webpack",
418 | baseDataPath: "configuration",
at fn (test/index.test.js:415:26)
at Object. (test/index.test.js:45:9)
● Validation › should fail validation for postFormatter #2
expect(received).toMatchSnapshot()
Snapshot name: `Validation should fail validation for postFormatter #2 1`
- Snapshot - 1
+ Received + 1
"Invalid configuration object. Webpack has been initialized using a
configuration object that does not match the API schema.
- - configuration.output.filename: A relative path is expected. However,
the provided value \"/bar\" is an absolute path!
+ - configuration.output.filename: A relative path is expected. However,
the provided value "/bar" is an absolute path!
Please use output.path to specify absolute path and output.filename
for the file name."
453 | },
454 | },
> 455 | (msg) => expect(msg).toMatchSnapshot(),
| ^
456 | {
457 | name: "Webpack",
458 | baseDataPath: "configuration",
at fn (test/index.test.js:455:26)
at Object. (test/index.test.js:45:9)
● Validation › should fail validation for ! in path
expect(received).toMatchSnapshot()
Snapshot name: `Validation should fail validation for ! in path 1`
- Snapshot - 1
+ Received + 1
"Invalid configuration object. Object has been initialized using a
configuration object that does not match the API schema.
- - configuration.output.path: The provided value \"/somepath/!test\"
contains exclamation mark (!) which is not allowed because it's reserved for
loader syntax.
+ - configuration.output.path: The provided value "/somepath/!test"
contains exclamation mark (!) which is not allowed because it's reserved for
loader syntax.
-> The output directory as **absolute path** (required)."
609 | },
610 | },
> 611 | (msg) => expect(msg).toMatchSnapshot()
| ^
612 | );
613 |
614 | createFailedTestCase(
at fn (test/index.test.js:611:26)
at Object. (test/index.test.js:45:9)
...
Some output formatting (escaping) seems to have changed.
Andreas
node-schema-utils.sid.build.gz
Description: application/gzip
Processed: node-schema-utils: ftbfs due to changed output formatting/escaping
Processing control commands: > found -1 4.0.0~ds-1 Bug #1021153 [node-schema-utils] node-schema-utils: ftbfs due to changed output formatting/escaping Marked as found in versions node-schema-utils/4.0.0~ds-1. -- 1021153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1021117: Acknowledgement (llvm-15-dev: cmake fails on missing /usr/lib/llvm-15/bin/mlir-tblgen)
Processing control commands: > severity -1 important Bug #1021117 [llvm-15-dev] llvm-15-dev: cmake fails on missing /usr/lib/llvm-15/bin/mlir-tblgen Severity set to 'important' from 'serious' > tag -1 unreproducible Bug #1021117 [llvm-15-dev] llvm-15-dev: cmake fails on missing /usr/lib/llvm-15/bin/mlir-tblgen Added tag(s) unreproducible. -- 1021117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021117: Acknowledgement (llvm-15-dev: cmake fails on missing /usr/lib/llvm-15/bin/mlir-tblgen)
Control: severity -1 important Control: tag -1 unreproducible A few hours later I cannot reproduce that any more. Something must have been upgraded inbetween. But I noticed a similar error with spirv-llvm-translator-14 on x32: https://buildd.debian.org/status/fetch.php?pkg=spirv-llvm-translator-14=x32=14.0.0-2=1664557744=0 CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 (message): The imported target "mlir-tblgen" references the file "/usr/lib/llvm-14/bin/mlir-tblgen" but this file does not exist. Possible reasons include: A new build is pending ... Andreas
Bug#983206: [libupnp13] Please update for CVE-2020-12695 & fixes
ping.
Bug#1012993: marked as done (lomiri-thumbnailer: ftbfs with GCC-12)
Your message dated Sun, 02 Oct 2022 22:14:15 + with message-id and subject line Bug#1012993: fixed in lomiri-thumbnailer 3.0.0-3 has caused the Debian Bug report #1012993, regarding lomiri-thumbnailer: ftbfs with GCC-12 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.) -- 1012993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lomiri-thumbnailer Version: 3.0.0-2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/lomiri-thumbnailer_3.0.0-2_unstable_gcc12.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] cd /<>/obj-x86_64-linux-gnu/tests/image && /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_REGEX_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DGTEST_VERSION_MAJOR=1 -DGTEST_VERSION_MINOR=11 -DGTEST_VERSION_PATCH=0 -DQT_CORE_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_NO_KEYWORDS -DSLOW_TESTS=1 -I/<>/obj-x86_64-linux-gnu/tests/image -I/<>/tests/image -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/taglib -I/<>/include -I/<>/obj-x86_64-linux-gnu/include -I/<>/tests -I/<>/obj-x86_64-linux-gnu/tests -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/lib/x86_64-linux-gnu/q t5/mkspecs/linux-g++ -isystem /usr/src/googletest/googletest/include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 --std=c++11 -Wall -pedantic -Wextra -fvisibility=hidden -Wcast-align -Wcast-qual -Wformat -Wredundant-decls -Wswitch-default -Wnon-virtual-dtor -Wctor-dtor-privacy -Wold-style-cast -fPIC -MD -MT tests/image/CMakeFiles/image_test.dir/image_test.cpp.o -MF CMakeFiles/image_test.dir/image_test.cpp.o.d -o CMakeFiles/image_test.dir/image_test.cpp.o -c /<>/tests/image/image_test.cpp make -f tests/recovery/CMakeFiles/recovery_test.dir/build.make tests/recovery/CMakeFiles/recovery_test.dir/depend make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/tests/recovery /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/tests/recovery /<>/obj-x86_64-linux-gnu/tests/recovery/CMakeFiles/recovery_test.dir/DependInfo.cmake --color= make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f tests/recovery/CMakeFiles/recovery_test.dir/build.make tests/recovery/CMakeFiles/recovery_test.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 66%] Building CXX object tests/recovery/CMakeFiles/recovery_test.dir/recovery_test.cpp.o cd /<>/obj-x86_64-linux-gnu/tests/recovery && /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_REGEX_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DGTEST_VERSION_MAJOR=1 -DGTEST_VERSION_MINOR=11 -DGTEST_VERSION_PATCH=0 -DQT_CORE_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_NO_KEYWORDS -DSLOW_TESTS=1
Bug#1021152: audacity: FTBFS on armel, s390x
Source: audacity Version: 3.2.0+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, audacity 3.2.0+dfsg-1 FTBFS on armel and s390x. Tail of log for audacity on armel: /usr/include/c++/12/bits/stl_vector.h:1287:28: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator >’ changed in GCC 7.1 1287 | _M_realloc_insert(end(), __x); | ~^~~~ In member function ‘void std::vector<_Tp, _Alloc>::push_back(const value_type&) [with _Tp = LabelStruct; _Alloc = std::allocator]’, inlined from ‘void LabelTrack::Import(wxTextFile&)’ at /<>/src/LabelTrack.cpp:592:27: /usr/include/c++/12/bits/stl_vector.h:1287:28: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator >’ changed in GCC 7.1 1287 | _M_realloc_insert(end(), __x); | ~^~~~ make[3]: Leaving directory '/<>/obj-arm-linux-gnueabi' make[2]: *** [CMakeFiles/Makefile2:1922: src/CMakeFiles/Audacity.dir/all] Error 2 make[2]: Leaving directory '/<>/obj-arm-linux-gnueabi' make[1]: *** [Makefile:159: all] Error 2 make[1]: Leaving directory '/<>/obj-arm-linux-gnueabi' dh_auto_build: error: cd obj-arm-linux-gnueabi && make -j8 "INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2 make: *** [debian/rules:47: binary-arch] Error 25 Tail of log for audacity on s390x: [ 65%] Building CXX object src/CMakeFiles/Audacity.dir/SseMathFuncs.cpp.o cd /<>/obj-s390x-linux-gnu/src && /usr/bin/c++ -DAUDACITY_DLL_API="" -DAUDIO_DEVICES_API="" -DAUDIO_GRAPH_API="" -DAudacity_EXPORTS -DBASIC_UI_API="" -DBUILDING_AUDACITY -DCMAKE -DCOMPONENTS_API="" -DEXCEPTIONS_API="" -DEXPERIMENTAL_CRASH_REPORT -DEXPERIMENTAL_DRAGGABLE_PLAY_HEAD -DEXPERIMENTAL_FULL_WASAPI -DEXPERIMENTAL_HALF_WAVE -DEXPERIMENTAL_KEY_VIEW -DEXPERIMENTAL_MIDI_OUT -DEXPERIMENTAL_MODULE_PREFS -DEXPERIMENTAL_NOISE_REDUCTION -DEXPERIMENTAL_NOTETRACK_OVERLAY -DEXPERIMENTAL_NYQUIST_SPLIT_CONTROL -DEXPERIMENTAL_PUNCH_AND_ROLL -DEXPERIMENTAL_SCIENCE_FILTERS -DEXPERIMENTAL_SCROLLING_LIMITS -DEXPERIMENTAL_SCRUBBING_SCROLL_WHEEL -DEXPERIMENTAL_SCRUBBING_SUPPORT -DEXPERIMENTAL_SPECTRAL_EDITING -DEXPERIMENTAL_SYNC_LOCK -DEXPERIMENTAL_THEMING -DEXPERIMENTAL_TWO_TONE_TIME_RULER -DEXPERIMENTAL_ZOOM_TOGGLE_BUTTON -DFFMPEG_SUPPORT_API="" -DFILES_API="" -DGRAPHICS_API="" -DHAVE_LRINT -DHAVE_LRINTF -DHAVE_MLOCK -DIPC_API="" -DMATH_API="" -DMODULE_MANAGER_API="" -DPREFERENCES_API="" -DPROJECT_API="" -DPROJECT_HISTORY_API="" -DPROJECT_RATE_API="" -DREGISTRIES_API="" -DSAMPLE_TRACK_API="" -DSCREEN_GEOMETRY_API="" -DSTRINGS_API="" -DSTRING_UTILS_API="" -DTHEME_API="" -DTHEME_RESOURCES_API="" -DTRACK_API="" -DTRANSACTIONS_API="" -DUSE_FFMPEG -DUSE_NYQUIST=1 -DUSE_PORTMIXER=1 -DUTILITY_API="" -DUUID_API="" -DWXUSINGDLL -DXML_API="" -D_FILE_OFFSET_BITS=64 -D__WXGTK__ -I/<>/obj-s390x-linux-gnu/src/private -I/<>/include -I/<>/src -I/<>/libraries/lib-string-utils -I/<>/libraries/lib-uuid -I/<>/libraries/lib-project-rate -I/<>/libraries/lib-project -I/<>/libraries/lib-registries -I/<>/libraries/lib-preferences -I/<>/libraries/lib-utility -I/<>/libraries/lib-basic-ui -I/<>/libraries/lib-strings -I/<>/libraries/lib-components -I/<>/libraries/lib-exceptions -I/<>/libraries/lib-xml -I/<>/libraries/lib-files -I/<>/libraries/lib-audio-devices -I/<>/lib-src/portmixer/include -I/<>/libraries/lib-math -I/<>/libraries/lib-theme-resources -I/<>/libraries/lib-theme -I/<>/libraries/lib-sample-track -I/<>/libraries/lib-audio-graph -I/<>/libraries/lib-track -I/<>/libraries/lib-module-manager -I/<>/libraries/lib-ipc -I/<>/libraries/lib-project-history -I/<>/libraries/lib-screen-geometry -I/<>/libraries/lib-transactions -I/<>/libraries/lib-graphics -I/<>/libraries/lib-ffmpeg-support -I/<>/libraries/lib-sentry-reporting -I/<>/lib-src/libnyquist -isystem /usr/lib/s390x-linux-gnu/wx/include/gtk3-unicode-3.2 -isystem /usr/include/wx-3.2 -isystem /usr/include/lame -isystem /usr/include/lilv-0 -isystem /usr/include/sratom-0 -isystem /usr/include/sord-0 -isystem /usr/include/serd-0 -isystem /usr/include/suil-0 -isystem /usr/include/portSMF -isystem /usr/include/soundtouch -isystem /usr/include/glib-2.0 -isystem /usr/lib/s390x-linux-gnu/glib-2.0/include -isystem /usr/include/gtk-3.0 -isystem /usr/include/at-spi2-atk/2.0 -isystem /usr/include/at-spi-2.0 -isystem /usr/include/dbus-1.0 -isystem /usr/lib/s390x-linux-gnu/dbus-1.0/include -isystem /usr/include/gio-unix-2.0 -isystem /usr/include/cairo -isystem /usr/include/pango-1.0 -isystem /usr/include/harfbuzz -isystem /usr/include/fribidi -isystem /usr/include/atk-1.0 -isystem /usr/include/pixman-1 -isystem /usr/include/uuid -isystem /usr/include/freetype2 -isystem /usr/include/gdk-pixbuf-2.0 -isystem /usr/include/libpng16 -isystem /usr/include/libmount -isystem /usr/include/blkid -g -O2 -ffile-prefix-map=/<>=.
Bug#1012993: marked as pending in lomiri-thumbnailer
Control: tag -1 pending Hello, Bug #1012993 in lomiri-thumbnailer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ubports-team/lomiri-thumbnailer/-/commit/451c874dfb0cfa2f2f51f7e188b10d255ab3b259 Add missing header. (Closes: #1012993) (this message was generated automatically) -- Greetings https://bugs.debian.org/1012993
Processed: Bug#1012993 marked as pending in lomiri-thumbnailer
Processing control commands: > tag -1 pending Bug #1012993 [src:lomiri-thumbnailer] lomiri-thumbnailer: ftbfs with GCC-12 Added tag(s) pending. -- 1012993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964654:
Processed: closing 1020844
Processing commands for cont...@bugs.debian.org: > close 1020844 0.0.5-2 Bug #1020844 [src:haskell-gi-harfbuzz] haskell-gi-harfbuzz FTBFS: error: Could not find module ‘GI.Freetype2.Structs.Face’ The source 'haskell-gi-harfbuzz' and version '0.0.5-2' do not appear to match any binary packages Marked as fixed in versions haskell-gi-harfbuzz/0.0.5-2. Bug #1020844 [src:haskell-gi-harfbuzz] haskell-gi-harfbuzz FTBFS: error: Could not find module ‘GI.Freetype2.Structs.Face’ Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1020844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1021133, found 1021133 in 14.4.2+git20190427-3 ..., tagging 1021134 ..., tagging 1021135 ...
Processing commands for cont...@bugs.debian.org: > tags 1021133 + upstream Bug #1021133 [src:sox] sox: CVE-2021-23159 Added tag(s) upstream. > found 1021133 14.4.2+git20190427-3 Bug #1021133 [src:sox] sox: CVE-2021-23159 Marked as found in versions sox/14.4.2+git20190427-3. > forwarded 1021133 https://sourceforge.net/p/sox/bugs/352/ Bug #1021133 [src:sox] sox: CVE-2021-23159 Set Bug forwarded-to-address to 'https://sourceforge.net/p/sox/bugs/352/'. > tags 1021134 + upstream Bug #1021134 [src:sox] sox: CVE-2021-23172 Added tag(s) upstream. > found 1021134 14.4.2+git20190427-3 Bug #1021134 [src:sox] sox: CVE-2021-23172 Marked as found in versions sox/14.4.2+git20190427-3. > forwarded 1021134 https://sourceforge.net/p/sox/bugs/350/ Bug #1021134 [src:sox] sox: CVE-2021-23172 Set Bug forwarded-to-address to 'https://sourceforge.net/p/sox/bugs/350/'. > tags 1021135 + upstream Bug #1021135 [src:sox] sox: CVE-2021-33844 Added tag(s) upstream. > found 1021135 14.4.2+git20190427-3 Bug #1021135 [src:sox] sox: CVE-2021-33844 Marked as found in versions sox/14.4.2+git20190427-3. > forwarded 1021135 https://sourceforge.net/p/sox/bugs/349/ Bug #1021135 [src:sox] sox: CVE-2021-33844 Set Bug forwarded-to-address to 'https://sourceforge.net/p/sox/bugs/349/'. > tags 1021136 + upstream Bug #1021136 [node-matrix-js-sdk] node-matrix-js-sdk: CVE-2022-39236 CVE-2022-39249 CVE-2022-39251 Added tag(s) upstream. > tags 1021137 + upstream Bug #1021137 [src:modsecurity-crs] modsecurity-crs: CVE-2022-39955 CVE-2022-39956 CVE-2022-39957 CVE-2022-39958 Added tag(s) upstream. > tags 1021138 + upstream Bug #1021138 [src:php8.1] php8.1: CVE-2022-31628 CVE-2022-31629 Added tag(s) upstream. > found 1021138 8.1.7-1 Bug #1021138 [src:php8.1] php8.1: CVE-2022-31628 CVE-2022-31629 Marked as found in versions php8.1/8.1.7-1. > tags 1021139 + upstream Bug #1021139 [src:barbican] barbican: CVE-2022-3100 Added tag(s) upstream. > tags 1021141 + upstream Bug #1021141 [src:imagemagick] imagemagick: CVE-2022-3213 Added tag(s) upstream. > found 1021141 8:6.9.11.60+dfsg-1.3 Bug #1021141 [src:imagemagick] imagemagick: CVE-2022-3213 Marked as found in versions imagemagick/8:6.9.11.60+dfsg-1.3. > tags 1021142 + upstream Bug #1021142 [src:cargo] cargo: CVE-2022-36113 CVE-2022-36114 Added tag(s) upstream. > found 1021142 0.57.0-7 Bug #1021142 [src:cargo] cargo: CVE-2022-36113 CVE-2022-36114 Marked as found in versions cargo/0.57.0-7. > tags 1021143 + upstream Bug #1021143 [src:rust-cargo] rust-cargo: CVE-2022-36113 CVE-2022-36114 Added tag(s) upstream. > found 1021143 0.57.0-1 Bug #1021143 [src:rust-cargo] rust-cargo: CVE-2022-36113 CVE-2022-36114 Marked as found in versions rust-cargo/0.57.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1021133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021133 1021134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021134 1021135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021135 1021136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021136 1021137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021137 1021138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021138 1021139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021139 1021141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021141 1021142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021142 1021143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020077: marked as done (debspawn: FTBFS: ValueError: invalid pyproject.toml config: `project.license`.)
Your message dated Sun, 02 Oct 2022 18:22:10 +
with message-id
and subject line Bug#1020077: fixed in debspawn 0.6.0-1
has caused the Debian Bug report #1020077,
regarding debspawn: FTBFS: ValueError: invalid pyproject.toml config:
`project.license`.
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.)
--
1020077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debspawn
Version: 0.5.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py clean
> configuration error: `project.license` must be valid exactly by one
> definition (2 matches found):
>
> - keys:
> 'file': {type: string}
> required: ['file']
> - keys:
> 'text': {type: string}
> required: ['text']
>
> DESCRIPTION:
> `Project license `_.
>
> GIVEN VALUE:
> "LGPL-3.0-or-later"
>
> OFFENDING RULE: 'oneOf'
>
> DEFINITION:
> {
> "oneOf": [
> {
> "properties": {
> "file": {
> "type": "string",
> "$$description": [
> "Relative path to the file (UTF-8) which contains
> the license for the",
> "project."
> ]
> }
> },
> "required": [
> "file"
> ]
> },
> {
> "properties": {
> "text": {
> "type": "string",
> "$$description": [
> "The license of the project whose meaning is that
> of the",
> "`License field from the core metadata",
>
> "`_."
> ]
> }
> },
> "required": [
> "text"
> ]
> }
> ]
> }
> Traceback (most recent call last):
> File "/<>/setup.py", line 104, in
> setup(
> File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in
> setup
> return distutils.core.setup(**attrs)
> File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
> 159, in setup
> dist.parse_config_files()
> File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 868, in
> parse_config_files
> pyprojecttoml.apply_configuration(self, filename, ignore_option_errors)
> File "/usr/lib/python3/dist-packages/setuptools/config/pyprojecttoml.py",
> line 62, in apply_configuration
> config = read_configuration(filepath, True, ignore_option_errors, dist)
> File "/usr/lib/python3/dist-packages/setuptools/config/pyprojecttoml.py",
> line 126, in read_configuration
> validate(subset, filepath)
> File "/usr/lib/python3/dist-packages/setuptools/config/pyprojecttoml.py",
> line 51, in validate
> raise ValueError(f"{error}\n{summary}") from None
> ValueError: invalid pyproject.toml config: `project.license`.
> configuration error: `project.license` must be valid exactly by one
> definition (2 matches found):
>
> - keys:
> 'file': {type: string}
> required: ['file']
> - keys:
> 'text': {type: string}
> required: ['text']
>
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1:
> python3.10 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned
> exit code 13
> make: *** [debian/rules:6: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2022/09/17/debspawn_0.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-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220917=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
Processed: retitle 1021136 to node-matrix-js-sdk: CVE-2022-39236 CVE-2022-39249 CVE-2022-39251
Processing commands for cont...@bugs.debian.org: > retitle 1021136 node-matrix-js-sdk: CVE-2022-39236 CVE-2022-39249 > CVE-2022-39251 Bug #1021136 [node-matrix-js-sdk] sox: CVE-2022-39236 CVE-2022-39249 CVE-2022-39251 Changed Bug title to 'node-matrix-js-sdk: CVE-2022-39236 CVE-2022-39249 CVE-2022-39251' from 'sox: CVE-2022-39236 CVE-2022-39249 CVE-2022-39251'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1021136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1021136 to node-matrix-js-sdk
Processing commands for cont...@bugs.debian.org: > reassign 1021136 node-matrix-js-sdk Bug #1021136 [src:sox] sox: CVE-2022-39236 CVE-2022-39249 CVE-2022-39251 Bug reassigned from package 'src:sox' to 'node-matrix-js-sdk'. Ignoring request to alter found versions of bug #1021136 to the same values previously set Ignoring request to alter fixed versions of bug #1021136 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1021136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021138: php8.1: CVE-2022-31628 CVE-2022-31629
Source: php8.1 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for php8.1. CVE-2022-31628[0]: | In PHP versions before 7.4.31, 8.0.24 and 8.1.11, the phar | uncompressor code would recursively uncompress "quines" gzip files, | resulting in an infinite loop. PHP Bug: https://bugs.php.net/bug.php?id=81726 https://github.com/php/php-src/commit/404e8bdb68350931176a5bdc86fc417b34fb583d https://github.com/php/php-src/commit/432bf196d59bcb661fcf9cb7029cea9b43f490af CVE-2022-31629[1]: | In PHP versions before 7.4.31, 8.0.24 and 8.1.11, the vulnerability | enables network and same-site attackers to set a standard insecure | cookie in the victim's browser which is treated as a `__Host-` or | `__Secure-` cookie by PHP applications. PHP Bug: https://bugs.php.net/bug.php?id=81727 https://github.com/php/php-src/commit/0611be4e82887cee0de6c4cbae320d34eec946ca If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-31628 https://www.cve.org/CVERecord?id=CVE-2022-31628 [1] https://security-tracker.debian.org/tracker/CVE-2022-31629 https://www.cve.org/CVERecord?id=CVE-2022-31629 Please adjust the affected versions in the BTS as needed.
Bug#1021139: barbican: CVE-2022-3100
Source: barbican X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for barbican. CVE-2022-3100[0]: access policy bypass via query string injection Only reference so far is Red Hat Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2125404 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-2022-3100 https://www.cve.org/CVERecord?id=CVE-2022-3100 Please adjust the affected versions in the BTS as needed.
Bug#1021136: sox: CVE-2022-39236 CVE-2022-39249 CVE-2022-39251
Source: sox X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for sox. CVE-2022-39236[0]: | Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. | Starting with version 17.1.0-rc.1, improperly formed beacon events can | disrupt or impede the matrix-js-sdk from functioning properly, | potentially impacting the consumer's ability to process data safely. | Note that the matrix-js-sdk can appear to be operating normally but be | excluding or corrupting runtime data presented to the consumer. This | is patched in matrix-js-sdk v19.7.0. Redacting applicable events, | waiting for the sync processor to store data, and restarting the | client are possible workarounds. Alternatively, redacting the | applicable events and clearing all storage will fix the further | perceived issues. Downgrading to an unaffected version, noting that | such a version may be subject to other vulnerabilities, will | additionally resolve the issue. https://github.com/matrix-org/matrix-js-sdk/security/advisories/GHSA-hvv8-5v86-r45x https://github.com/matrix-org/matrix-js-sdk/commit/a587d7c36026fe1fcf93dfff63588abee359be76 https://github.com/matrix-org/matrix-spec-proposals/pull/3488 CVE-2022-39249[1]: | Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. | Prior to version 19.7.0, an attacker cooperating with a malicious | homeserver can construct messages appearing to have come from another | person. Such messages will be marked with a grey shield on some | platforms, but this may be missing in others. This attack is possible | due to the matrix-js-sdk implementing a too permissive key forwarding | strategy on the receiving end. Starting with version 19.7.0, the | default policy for accepting key forwards has been made more strict in | the matrix-js-sdk. matrix-js-sdk will now only accept forwarded keys | in response to previously issued requests and only from own, verified | devices. The SDK now sets a `trusted` flag on the decrypted message | upon decryption, based on whether the key used to decrypt the message | was received from a trusted source. Clients need to ensure that | messages decrypted with a key with `trusted = false` are decorated | appropriately, for example, by showing a warning for such messages. | This attack requires coordination between a malicious homeserver and | an attacker, and those who trust your homeservers do not need a | workaround. https://github.com/matrix-org/matrix-js-sdk/security/advisories/GHSA-6263-x97c-c4gg https://github.com/matrix-org/matrix-js-sdk/commit/a587d7c36026fe1fcf93dfff63588abee359be76 https://github.com/matrix-org/matrix-spec-proposals/pull/3061 https://matrix.org/blog/2022/09/28/upgrade-now-to-address-encryption-vulns-in-matrix-sdks-and-clients CVE-2022-39251[2]: | Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. | Prior to version 19.7.0, an attacker cooperating with a malicious | homeserver can construct messages that legitimately appear to have | come from another person, without any indication such as a grey | shield. Additionally, a sophisticated attacker cooperating with a | malicious homeserver could employ this vulnerability to perform a | targeted attack in order to send fake to-device messages appearing to | originate from another user. This can allow, for example, to inject | the key backup secret during a self-verification, to make a targeted | device start using a malicious key backup spoofed by the homeserver. | These attacks are possible due to a protocol confusion vulnerability | that accepts to-device messages encrypted with Megolm instead of Olm. | Starting with version 19.7.0, matrix-js-sdk has been modified to only | accept Olm-encrypted to-device messages. Out of caution, several other | checks have been audited or added. This attack requires coordination | between a malicious home server and an attacker, so those who trust | their home servers do not need a workaround. https://github.com/matrix-org/matrix-js-sdk/security/advisories/GHSA-r48r-j8fx-mq2c https://github.com/matrix-org/matrix-js-sdk/commit/a587d7c36026fe1fcf93dfff63588abee359be76 https://matrix.org/blog/2022/09/28/upgrade-now-to-address-encryption-vulns-in-matrix-sdks-and-clients If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-39236 https://www.cve.org/CVERecord?id=CVE-2022-39236 [1] https://security-tracker.debian.org/tracker/CVE-2022-39249 https://www.cve.org/CVERecord?id=CVE-2022-39249 [2] https://security-tracker.debian.org/tracker/CVE-2022-39251 https://www.cve.org/CVERecord?id=CVE-2022-39251 Please adjust the affected versions in the BTS as needed.
Bug#1017979: marked as done (mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc.)
Your message dated Sun, 02 Oct 2022 17:32:32 + with message-id and subject line Bug#1016878: Removed package(s) from unstable has caused the Debian Bug report #1017979, regarding mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc. 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.) -- 1017979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mozjs91 Version: 91.10.0-1 Severity: serious Tags: ftbfs help X-Debbugs-Cc: debian-...@lists.debian.org Control: block 1017961 by -1 Versions of mozjs91 newer than 91.10.0-1 failed to build on the armel buildds. I tried building 91.10.0-1 in an armel chroot on amdahl, and that also fails, which makes me think that the root cause for the build failure is the upgrade from gcc 11 to 12 as default compiler. The final link fails with multiple definitions of the various atomic builtins: > /usr/bin/arm-linux-gnueabi-g++ -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 > -fstack-protector-strong -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wempty-body > -Wignored-qualifiers -Wpointer-arith -Wsign-compare -Wtype-limits > -Wunreachable-code -Wno-invalid-offsetof -Wc++2a-compat -Wduplicated-cond > -Wimplicit-fallthrough -Wno-error=maybe-uninitialized > -Wno-error=deprecated-declarations -Wno-error=array-bounds > -Wno-error=coverage-mismatch -Wno-error=free-nonheap-object > -Wno-multistatement-macros -Wno-error=class-memaccess > -Wno-error=deprecated-copy -Wno-error=unused-but-set-variable -Wformat > -Wformat-overflow=2 -Wno-psabi -fno-sized-deallocation -fno-aligned-new -g > -O2 -ffile-prefix-map=/home/smcv/mozjs91-armel=. -fstack-protector-strong > -Wformat -Werror=format-security -fPIC -fno-rtti -ffunction-sections > -fdata-sections -fno-exceptions -fno-math-errno -pthread -pipe -g > -freorder-blocks -O3 -fomit-frame-pointer -funwind-tables -shared > -Wl,-z,defs -Wl,--gc-sections -Wl,-h,libmozjs-91.so -o libmozjs-91.so > /home/smcv/mozjs91-armel/debian/build/js/src/build/libmozjs-91_so.list > -lpthread -Wl,-z,relro -Wl,-z,noexecstack -Wl,-z,text -Wl,-z,relro > -Wl,-z,nocopyreloc -Wl,-Bsymbolic-functions -Wl,--build-id=sha1 > -fstack-protector-strong > -Wl,-rpath-link,/home/smcv/mozjs91-armel/debian/build/dist/bin > -Wl,-rpath-link,/usr/lib > /home/smcv/mozjs91-armel/debian/build/armv5te-unknown-linux-gnueabi/release/libjsrust.a > -Wl,--version-script,symverscript -Wl,-soname,libmozjs-91.so.0 -lm > -latomic -lz -lm -ldl > /usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/12/libgcc.a(linux-atomic.o): in > function `__sync_fetch_and_add_4': > (.text+0x0): multiple definition of `__sync_fetch_and_add_4'; > /home/smcv/mozjs91-armel/debian/build/armv5te-unknown-linux-gnueabi/release/libjsrust.a(compiler_builtins-23c2fc8f8ef06d87.compiler_builtins.bdb7b41d-cgu.153.rcgu.o):/usr/src/rustc-1.59.0/vendor/compiler_builtins/src/arm_linux.rs:94: > first defined here > /usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/12/libgcc.a(linux-atomic.o): in > function `__sync_fetch_and_sub_4': > (.text+0x38): multiple definition of `__sync_fetch_and_sub_4'; > /home/smcv/mozjs91-armel/debian/build/armv5te-unknown-linux-gnueabi/release/libjsrust.a(compiler_builtins-23c2fc8f8ef06d87.compiler_builtins.bdb7b41d-cgu.153.rcgu.o):/usr/src/rustc-1.59.0/vendor/compiler_builtins/src/arm_linux.rs:94: > first defined here (etc.) An example build log: https://buildd.debian.org/status/fetch.php?pkg=mozjs91=armel=91.13.0-1=1661218081=0 The same failure mode occurred when I tried to build mozjs102 with ARMv7 inline assembler disabled for #1017961. (For completeness: 91.10.0-1 and 91.12.0-1 have an additional failure reason involving undefined references to std::type_info::operator==(std::type_info const&) const, but I believe that was fixed in 91.12.0-2 by removing an obsolete patch. The latest mozjs91 and mozjs102 do not have the obsolete patch and do not exhibit the std::type_info errors.) Assistance from fans of armel would be much appreciated. If we cannot get mozjs102 to compile on armel, then gjs and the GNOME stack in general will probably have to be removed from armel, similar to the way we temporarily removed them from s390x between mid 2019 and mid 2020. smcv --- End Message --- --- Begin Message --- Version: 91.13.0-1+rm Dear submitter, as the package mozjs91 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
Bug#999057: marked as done (gcc-m68hc1x: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Sun, 02 Oct 2022 17:26:54 + with message-id and subject line Bug#1021026: Removed package(s) from unstable has caused the Debian Bug report #999057, regarding gcc-m68hc1x: missing required debian/rules targets build-arch and/or build-indep 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.) -- 999057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-m68hc1x Version: 1:3.3.6+3.1+dfsg-3.1 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Version: 1:3.3.6+3.1+dfsg-3.1+rm Dear submitter, as the package gcc-m68hc1x 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/1021026 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#965542: marked as done (gcc-m68hc1x: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Sun, 02 Oct 2022 17:26:54 + with message-id and subject line Bug#1021026: Removed package(s) from unstable has caused the Debian Bug report #965542, regarding gcc-m68hc1x: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-m68hc1x Version: 1:3.3.6+3.1+dfsg-3.1 Severity: normal Usertags: compat-5-6-removal Hi, The package gcc-m68hc1x uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Version: 1:3.3.6+3.1+dfsg-3.1+rm Dear submitter, as the package gcc-m68hc1x 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/1021026 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#982703: marked as done (gcc-m68hc1x: FTBFS: ../../src/gcc/config/m68hc11/larith.asm:108: Error: attempt to store non-zero value in section `.softregs')
Your message dated Sun, 02 Oct 2022 17:26:54 + with message-id and subject line Bug#1021026: Removed package(s) from unstable has caused the Debian Bug report #982703, regarding gcc-m68hc1x: FTBFS: ../../src/gcc/config/m68hc11/larith.asm:108: Error: attempt to store non-zero value in section `.softregs' 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.) -- 982703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-m68hc1x Version: 1:3.3.6+3.1+dfsg-3.1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210213 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /<>/build/gcc/xgcc -B/<>/build/gcc/ > -B/usr/m68hc11/bin/ -B/usr/m68hc11/lib/ -isystem /usr/m68hc11/include -Os > -mrelax -DUSE_GAS -DIN_GCC -g -DIN_LIBGCC2 -I. -I. -I../../src/gcc > -I../../src/gcc/. -I../../src/gcc/config -I../../src/gcc/../include > -DL_regs_min -xassembler-with-cpp -c ../../src/gcc/config/m68hc11/larith.asm > -o libgcc/./_regs_min.o > ../../src/gcc/config/m68hc11/larith.asm: Assembler messages: > ../../src/gcc/config/m68hc11/larith.asm:108: Error: attempt to store non-zero > value in section `.softregs' > ../../src/gcc/config/m68hc11/larith.asm:109: Error: attempt to store non-zero > value in section `.softregs' > ../../src/gcc/config/m68hc11/larith.asm:110: Error: attempt to store non-zero > value in section `.softregs' > make[3]: *** [libgcc.mk:392: libgcc/./_regs_min.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/02/13/gcc-m68hc1x_3.3.6+3.1+dfsg-3.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Version: 1:3.3.6+3.1+dfsg-3.1+rm Dear submitter, as the package gcc-m68hc1x 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/1021026 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1017449: marked as done (nautilus-image-converter: Incompatible with Nautilus 43)
Your message dated Sun, 02 Oct 2022 17:23:48 + with message-id and subject line Bug#1017449: fixed in nautilus-image-converter 0.4.0-2 has caused the Debian Bug report #1017449, regarding nautilus-image-converter: Incompatible with Nautilus 43 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.) -- 1017449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nautilus-image-converter Severity: serious Version: 0.3.1~git20110416-2 Tags: sid bookworm nautilus-image-converter is incompatible with Nautilus 43. It would need to be converted to GTK4 to continue to work. Thank you, Jeremy Bicha --- End Message --- --- Begin Message --- Source: nautilus-image-converter Source-Version: 0.4.0-2 Done: Jeremy Bicha We believe that the bug you reported is fixed in the latest version of nautilus-image-converter, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bicha (supplier of updated nautilus-image-converter 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 Oct 2022 12:45:02 -0400 Source: nautilus-image-converter Built-For-Profiles: noudeb Architecture: source Version: 0.4.0-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Jeremy Bicha Closes: 829873 1017449 Changes: nautilus-image-converter (0.4.0-2) unstable; urgency=medium . * QA upload * Release to unstable . nautilus-image-converter (0.4.0-1) experimental; urgency=medium . * QA upload * New upstream release compatible with Nautilus 43 (Closes: #1017449) * Update debian/watch and Homepage for new upstream * Build with meson (Closes: #829873) * Update packaging for current best practices * Depend on nautilus 43 Checksums-Sha1: 087d6d56dd50de75da873fbc71e24c3fbc84e399 2121 nautilus-image-converter_0.4.0-2.dsc 180c9016b72134236dc68efc2ba0a728a2419fe7 7116 nautilus-image-converter_0.4.0-2.debian.tar.xz 7a424964adea152a182e51e30f87c28253bd7062 15706 nautilus-image-converter_0.4.0-2_source.buildinfo Checksums-Sha256: 93eebdf2c6b2e921e6a9746a60cb46a966c3d952c0b33de6be459c995c6bec4e 2121 nautilus-image-converter_0.4.0-2.dsc d4847326cc06770d79cfb27d5b64cbda3395a705f199fa1e44776b3c6ef6edfd 7116 nautilus-image-converter_0.4.0-2.debian.tar.xz 5b8a179c4982a7186328fba418516273fe726d4438b422cc403abb07366961ca 15706 nautilus-image-converter_0.4.0-2_source.buildinfo Files: f45f4e68e50eb641da51e0d63421637d 2121 gnome optional nautilus-image-converter_0.4.0-2.dsc f78fd40e9d90ab297773eff5a646c049 7116 gnome optional nautilus-image-converter_0.4.0-2.debian.tar.xz eb69566bb9345a8f7e73a9d82a12171a 15706 gnome optional nautilus-image-converter_0.4.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmM5wDsACgkQ5mx3Wuv+ bH2xzhAArrAdhmYoBcC04WGsqmlehubkT8jXASq7jqWZ7XQTX70W4VOL+9/+uZyN 2vQR5dVbTsbGc0yWmpulH9KXUUPoIXCE42EM4GgZDhX8n8zcH5lbdXtQA8ZfwxEF 5qo7Rma5d+RrOv1jm+3lgDr4IDeC/637958TGiaR8wbz7MJNwDEkIqpVwEzHkDH4 Kzi+fg8PuhC34jrnFWopBmHZqfFuboOYIJ3OG573qxphJPsUI87ro+bW7bvSeOC5 f8lUXZEQVt6arHAcqGieElqrqi+ZeZwJ3gkv75u5yO69IIKK3HT5P3G2pXU3PeOp 5tot5Na/+jzzLXwtg8NRZ/Yghcfc9B6ZI/6BBwaOtYHhv/dMWtkqEG8PgE9Y0ATa y7dspPNwma14TpCLgVc/eodT0x9uq+fpdfAxG56okMGvUlpGq3Qf740RCBxgcqIu a3/E+89TfRbGR9d2UAb1WMztI6gmZpYPti6ar+E1r20BDD4U5qEklcE0j0gtJvDr vRVZ8mQudE3er4OoqMKFhL4ESJbPrdLfssFYobQpntjQWKN3sZFpT4QVAA4uB6WH ceyKKeKeYWOgVrb1ZAus6G5XNT7/GTrcMMBGVBj+PuOOXOwRVGUnVukPFH/ixiEZ s5ZC2aUr/m3+3c2nGwtxHKyU1pQvyesPJ1Qfnwz4joh+Bz0Lvog= =p7S7 -END PGP SIGNATURE End Message ---
Bug#1017013: marked as done (Removal notice: obsolete)
Your message dated Sun, 02 Oct 2022 17:18:29 + with message-id and subject line Bug#1021064: Removed package(s) from unstable has caused the Debian Bug report #1017013, regarding Removal notice: obsolete 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.) -- 1017013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017013 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-bindings-sane Version: 0.0.1-13 Severity: serious I intend to remove this package: * It has no rev dependencies * Seems unmaintained; Home page doesn't work * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 0.0.1-13+rm Dear submitter, as the package haskell-bindings-sane 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/1021064 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1017012: marked as done (Removal notice: obsolete)
Your message dated Sun, 02 Oct 2022 17:19:03 + with message-id and subject line Bug#1021063: Removed package(s) from unstable has caused the Debian Bug report #1017012, regarding Removal notice: obsolete 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.) -- 1017012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-bindings-nettle Version: 0.4-3 Severity: serious I intend to remove this package: * It has no rev dependencies * Seems unmaintained; Home page doesn't work * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 0.4-3+rm Dear submitter, as the package haskell-bindings-nettle 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/1021063 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#935669: marked as done (assaultcube-data: Outdated version makes assaultcube uninstallable)
Your message dated Sun, 02 Oct 2022 17:16:09 + with message-id and subject line Bug#1021101: Removed package(s) from unstable has caused the Debian Bug report #935669, regarding assaultcube-data: Outdated version makes assaultcube uninstallable 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.) -- 935669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: assaultcube-data Version: 1.1.0.4+repack1-2.1 Severity: serious Hi! The assaultcube package got updated to version 1.2.0.2.1-1, but the matching assaultcube-data package has not been uploaded which makes the former to be currently uninstallable in unstable. Thanks, Guillem --- End Message --- --- Begin Message --- Version: 1.2.0.2.1-3+rm Dear submitter, as the package assaultcube-data 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/1021101 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#912924: marked as done (classy-prelude-yesod: not worth maintenance burden?)
Your message dated Sun, 02 Oct 2022 17:16:53 + with message-id and subject line Bug#1021069: Removed package(s) from unstable has caused the Debian Bug report #912924, regarding classy-prelude-yesod: not worth maintenance burden? 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.) -- 912924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: classy-prelude-yesod Version: 1.4.0-1 Severity: serious classy-prelude-yesod is not currently needed and may not be worth the maintenance burden. Please close this bug if you disagree. --- End Message --- --- Begin Message --- Version: 1.5.0-1+rm Dear submitter, as the package haskell-classy-prelude-yesod 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/1021069 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1018969: marked as done (assaultcube-data: difficult copyright situation)
Your message dated Sun, 02 Oct 2022 17:16:09 + with message-id and subject line Bug#1021101: Removed package(s) from unstable has caused the Debian Bug report #1018969, regarding assaultcube-data: difficult copyright situation 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.) -- 1018969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- X-Debbugs-CC: 935...@bugs.debian.org Package: assaultcube-data Version: 1.2.0.2.1-3 Severity: serious Justification: Policy 2.2.3 Control: affects -1 assaultcube When I was looking into updating assaultcube to the new upstream release, I was prompted by #935669#57 to look into the copyright situation.. Before diving into it, I'd like to state that I believe upstream that hey have done their due diligence to ensure that they are able to redistribute their package. Upstream tells on their license site [1[ that it is ok to distribute the package unmodified. they gave Debian specic license to repack where appropiate, but only to make packaging easier. [2] [3] however they reserve the right revoke that license *at any time*; even if they try to find a resolution before, but they explictily reserve the right to revoke. Additionally, looking in the assaultcube data files package, there are several files with unclear copyright status or file origin, a few are just "all rights reserved". I fear that above puts a risk on Debian that I'm not sure if we should take this. My proposal to resolve would be to modify assaultcube-data, so that it will directly download and install the *data* files needed to play assaultcube. (The package assaultcube -- without -data is the game engine and licensed under a zlib-like license. This engine package is not a problem at all to have in Debian) [1] https://assault.cubers.net/docs/license.html [2] https://salsa.debian.org/games-team/assaultcube-data/-/blob/master/debian/copyright#L119 [3] http://forum.cubers.net/thread-4150.html -- tobi --- End Message --- --- Begin Message --- Version: 1.2.0.2.1-3+rm Dear submitter, as the package assaultcube-data 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/1021101 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1017019: marked as done (Removal notice: obsolete)
Your message dated Sun, 02 Oct 2022 17:17:24 + with message-id and subject line Bug#1021066: Removed package(s) from unstable has caused the Debian Bug report #1017019, regarding Removal notice: obsolete 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.) -- 1017019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-bytestring-mmap Version: 0.2.2-13 Severity: serious I intend to remove this package: * It has no rev dependencies * Seems unmaintained; Home page doesn't work * Seems unmaintained; Last upload more than 5 years ago If you believe we should keep this package in Debian, please close this bug report. -- Ilias --- End Message --- --- Begin Message --- Version: 0.2.2-13+rm Dear submitter, as the package haskell-bytestring-mmap 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/1021066 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Processed: nmu: grpc_1.44.0-3
Processing control commands: > block 1021113 by -1 Bug #1021113 [libgrpc22] libgrpc22 in experimental needs a rebuild with newer libabsl 1021113 was not blocked by any bugs. 1021113 was not blocking any bugs. Added blocking bug(s) of 1021113: 1021128 -- 1021113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021113 1021128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020793: marked as done (gmap: FTBFS on avx512 host in buster)
Your message dated Sun, 02 Oct 2022 16:55:08 +
with message-id
and subject line Bug#1020793: fixed in gmap 2021-12-17+ds-2
has caused the Debian Bug report #1020793,
regarding gmap: FTBFS on avx512 host in buster
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.)
--
1020793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gmap
Version: 2019-01-24-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Control: fixed -1 2021-02-22+ds-1
Hi,
during a local rebuild of all contrib and non-free packages I noticed
that gmap/buster did FTBFS while it succeeded two years ago.
Comparing the build logs I noticed that the new build targted avx512
while the old build targeted sse42. (The old machine has been
decommissioned inbetween ...)
I cannot reproduce this with the versions found in stretch or bullseye.
gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread
-DTARGET=\"x86_64-pc-linux-gnu\" -DGMAPDB=\"/var/cache/gmap\"
-DMAX_STACK_READLENGTH=300 -DGSNAP=1 -DLARGE_GENOMES=1 -mpopcnt -DHAVE_SSE2=1
-DHAVE_SSSE3=1 -DHAVE_SSE4_1=1 -DHAVE_SSE4_2=1 -DHAVE_AVX2=1 -DHAVE_AVX512=1
-msse2 -mssse3 -msse4.1 -msse4.2 -mavx2 -mbmi2 -mavx512f -mavx512cd -g -O2
-fdebug-prefix-map=/build/gmap-2019-01-24=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o gsnapl_avx512-merge-uint8.o `test -f
'merge-uint8.c' || echo './'`merge-uint8.c
merge-uint8.c: In function 'merge_4x4':
merge-uint8.c:72:29: error: incompatible type for argument 1 of '_mm_max_epu64'
*vMergedB = _mm_max_epu64(vTmp, vMax);
^~~~
In file included from /usr/lib/gcc/x86_64-linux-gnu/8/include/immintrin.h:53,
from merge-uint8.c:15:
/usr/lib/gcc/x86_64-linux-gnu/8/include/avx512vlintrin.h:8037:24: note:
expected '__m128i' {aka '__vector(2) long long int'} but argument is of type
'__m256i' {aka '__vector(4) long long int'}
_mm_max_epu64 (__m128i __A, __m128i __B)
^~~
merge-uint8.c:72:35: error: incompatible type for argument 2 of '_mm_max_epu64'
*vMergedB = _mm_max_epu64(vTmp, vMax);
^~~~
In file included from /usr/lib/gcc/x86_64-linux-gnu/8/include/immintrin.h:53,
from merge-uint8.c:15:
/usr/lib/gcc/x86_64-linux-gnu/8/include/avx512vlintrin.h:8037:37: note:
expected '__m128i' {aka '__vector(2) long long int'} but argument is of type
'__m256i' {aka '__vector(4) long long int'}
_mm_max_epu64 (__m128i __A, __m128i __B)
^~~
make[3]: *** [Makefile:35387: gsnapl_avx512-merge-uint8.o] Error 1
BTW, the package content should not depend on the build host cpu.
The sid package currently has avx2 binaries, if I rebuild it it gets
avx512 binaries, who knows what happens after a binNMU? This can easily
lead to significant performance regressions for some users.
As there seems to be some kind of runtime cpu detection, perhaps a
bigger list of cpu targets could be built and shipped (even targets
not supported by the buildd cpu). For correctness validation,
a separate package containing the tests (if any) could be provided...
Andreas
PS: I have no clue what this package is good for :-)
--- End Message ---
--- Begin Message ---
Source: gmap
Source-Version: 2021-12-17+ds-2
Done: Étienne Mollier
We believe that the bug you reported is fixed in the latest version of
gmap, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Étienne Mollier (supplier of updated gmap 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 Oct 2022 18:00:07 +0200
Source: gmap
Architecture: source
Version: 2021-12-17+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Étienne Mollier
Closes: 1020793
Changes:
gmap (2021-12-17+ds-2) unstable; urgency=medium
.
[ Nilesh Patra ]
* [skip ci] Remove myself from uploaders
.
[ Étienne Mollier ]
* d/rules: enforce a
Bug#1021115: unifrac-tools: Baseline violation on x86 and FTBFS everywhere else
Adrian Bunk, on 2022-10-02: > I was talking about a different change that would have been wrong: > > -ifeq ($(PERFORMING_CONDA_BUILD),True) > CPPFLAGS += -mtune=generic > -else > -CPPFLAGS += -mfma -march=native > -endif > > > This would have fixed the baseline violation, > but broken the build on non-x86 in a different way. Right, I see your point. True the -mtune= options are not valid on several architectures. Thanks for the clarification! Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. signature.asc Description: PGP signature
Bug#1021127: geany-plugins FTBFS with libgit2 1.5.0
Source: geany-plugins
Version: 1.38+dfsg-1
Severity: serious
Tags: ftbfs
Forwarded: https://github.com/geany/geany-plugins/issues/1164
https://buildd.debian.org/status/logs.php?pkg=geany-plugins=1.38%2Bdfsg-1%2Bb2
...
gcb-plugin.c: In function ‘gcb_git_buf_grow’:
gcb-plugin.c:219:12: error: ‘git_buf’ has no member named ‘asize’; did you mean
‘size’?
219 | if (buf->asize == 0) {
|^
|size
gcb-plugin.c: In function ‘buf_zero’:
gcb-plugin.c:237:10: error: ‘git_buf’ has no member named ‘asize’; did you mean
‘size’?
237 | buf->asize = 0;
| ^
| size
...
Processed: severity of 1020632 is serious
Processing commands for cont...@bugs.debian.org: > severity 1020632 serious Bug #1020632 [src:ruby-rugged] ruby-rugged: please update to version 1.5.0.1 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1020632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020898: marked as done (Uninstallable due to file conflict A37F26876B58371B70EDD889AD69F064C90AC2C6)
Your message dated Sun, 02 Oct 2022 16:22:47 + with message-id and subject line Bug#1020898: fixed in raku-readline 0.1.6-3 has caused the Debian Bug report #1020898, regarding Uninstallable due to file conflict A37F26876B58371B70EDD889AD69F064C90AC2C6 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.) -- 1020898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: perl6-readline,raku-file-which,raku-librarycheck,raku-readline Severity: serious Hi! [ Filing against all affected packages because it's not clear to me which one needs to be fixed. ] These packages all contain (at least) these same filenames: ,--- perl6-readline: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6 perl6-readline: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6.repo-id raku-file-which: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6 raku-file-which: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6.repo-id raku-librarycheck: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6 raku-librarycheck: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6.repo-id raku-readline: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6 raku-readline: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6.repo-id `--- which cause the installation to fail: ,--- Preparing to unpack .../raku-file-which_1.0.1-3+b1_amd64.deb ... Unpacking raku-file-which (1.0.1-3+b1) over (1.0.1-3) ... dpkg: error processing archive /var/cache/apt/archives/raku-file-which_1.0.1-3+b1_amd64.deb (--unpack): trying to overwrite '/usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6', which is also in package raku-readline:amd64 0.1.6-2+b1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../raku-librarycheck_0.0.10-3_amd64.deb ... Unpacking raku-librarycheck (0.0.10-3) over (0.0.10-2) ... dpkg: error processing archive /var/cache/apt/archives/raku-librarycheck_0.0.10-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6', which is also in package raku-readline:amd64 0.1.6-2+b1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/raku-file-which_1.0.1-3+b1_amd64.deb /var/cache/apt/archives/raku-librarycheck_0.0.10-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) `--- while perl6-readline and raku-readline can be installed to replace one another, they cannot be installed alongside the others AFAICS. Thanks, Guillem --- End Message --- --- Begin Message --- Source: raku-readline Source-Version: 0.1.6-3 Done: Dominique Dumont We believe that the bug you reported is fixed in the latest version of raku-readline, 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 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominique Dumont (supplier of updated raku-readline 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 Oct 2022 18:03:20 +0200 Source: raku-readline Architecture: source Version: 0.1.6-3 Distribution: unstable Urgency: medium Maintainer: Debian Rakudo Maintainers Changed-By: Dominique Dumont Closes: 1020898 Changes: raku-readline (0.1.6-3) unstable; urgency=medium . * control: remove build-dep on prove6 * control: depends on rakudo (>= 2022.07-2) (Closes: #1020898) Checksums-Sha1:
Bug#1020898: marked as done (Uninstallable due to file conflict A37F26876B58371B70EDD889AD69F064C90AC2C6)
Your message dated Sun, 02 Oct 2022 16:22:39 + with message-id and subject line Bug#1020898: fixed in raku-librarycheck 0.0.10-4 has caused the Debian Bug report #1020898, regarding Uninstallable due to file conflict A37F26876B58371B70EDD889AD69F064C90AC2C6 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.) -- 1020898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: perl6-readline,raku-file-which,raku-librarycheck,raku-readline Severity: serious Hi! [ Filing against all affected packages because it's not clear to me which one needs to be fixed. ] These packages all contain (at least) these same filenames: ,--- perl6-readline: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6 perl6-readline: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6.repo-id raku-file-which: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6 raku-file-which: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6.repo-id raku-librarycheck: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6 raku-librarycheck: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6.repo-id raku-readline: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6 raku-readline: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6.repo-id `--- which cause the installation to fail: ,--- Preparing to unpack .../raku-file-which_1.0.1-3+b1_amd64.deb ... Unpacking raku-file-which (1.0.1-3+b1) over (1.0.1-3) ... dpkg: error processing archive /var/cache/apt/archives/raku-file-which_1.0.1-3+b1_amd64.deb (--unpack): trying to overwrite '/usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6', which is also in package raku-readline:amd64 0.1.6-2+b1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../raku-librarycheck_0.0.10-3_amd64.deb ... Unpacking raku-librarycheck (0.0.10-3) over (0.0.10-2) ... dpkg: error processing archive /var/cache/apt/archives/raku-librarycheck_0.0.10-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6', which is also in package raku-readline:amd64 0.1.6-2+b1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/raku-file-which_1.0.1-3+b1_amd64.deb /var/cache/apt/archives/raku-librarycheck_0.0.10-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) `--- while perl6-readline and raku-readline can be installed to replace one another, they cannot be installed alongside the others AFAICS. Thanks, Guillem --- End Message --- --- Begin Message --- Source: raku-librarycheck Source-Version: 0.0.10-4 Done: Dominique Dumont We believe that the bug you reported is fixed in the latest version of raku-librarycheck, 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 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominique Dumont (supplier of updated raku-librarycheck 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 Oct 2022 18:00:58 +0200 Source: raku-librarycheck Architecture: source Version: 0.0.10-4 Distribution: unstable Urgency: medium Maintainer: Debian Rakudo Maintainers Changed-By: Dominique Dumont Closes: 1020898 Changes: raku-librarycheck (0.0.10-4) unstable; urgency=medium . * control: declare compliance with policy 4.6.1 * control: depends on rakudo (>= 2022.07-2)
Bug#1020898: marked as done (Uninstallable due to file conflict A37F26876B58371B70EDD889AD69F064C90AC2C6)
Your message dated Sun, 02 Oct 2022 16:22:32 + with message-id and subject line Bug#1020898: fixed in raku-file-which 1.0.1-4 has caused the Debian Bug report #1020898, regarding Uninstallable due to file conflict A37F26876B58371B70EDD889AD69F064C90AC2C6 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.) -- 1020898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: perl6-readline,raku-file-which,raku-librarycheck,raku-readline Severity: serious Hi! [ Filing against all affected packages because it's not clear to me which one needs to be fixed. ] These packages all contain (at least) these same filenames: ,--- perl6-readline: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6 perl6-readline: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6.repo-id raku-file-which: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6 raku-file-which: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6.repo-id raku-librarycheck: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6 raku-librarycheck: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6.repo-id raku-readline: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6 raku-readline: /usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6.repo-id `--- which cause the installation to fail: ,--- Preparing to unpack .../raku-file-which_1.0.1-3+b1_amd64.deb ... Unpacking raku-file-which (1.0.1-3+b1) over (1.0.1-3) ... dpkg: error processing archive /var/cache/apt/archives/raku-file-which_1.0.1-3+b1_amd64.deb (--unpack): trying to overwrite '/usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6', which is also in package raku-readline:amd64 0.1.6-2+b1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../raku-librarycheck_0.0.10-3_amd64.deb ... Unpacking raku-librarycheck (0.0.10-3) over (0.0.10-2) ... dpkg: error processing archive /var/cache/apt/archives/raku-librarycheck_0.0.10-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/perl6/vendor/precomp/DA3B96DAB7BC165C334BF96F9941B4C9DBA4BAE7/A3/A37F26876B58371B70EDD889AD69F064C90AC2C6', which is also in package raku-readline:amd64 0.1.6-2+b1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/raku-file-which_1.0.1-3+b1_amd64.deb /var/cache/apt/archives/raku-librarycheck_0.0.10-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) `--- while perl6-readline and raku-readline can be installed to replace one another, they cannot be installed alongside the others AFAICS. Thanks, Guillem --- End Message --- --- Begin Message --- Source: raku-file-which Source-Version: 1.0.1-4 Done: Dominique Dumont We believe that the bug you reported is fixed in the latest version of raku-file-which, 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 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominique Dumont (supplier of updated raku-file-which 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 Oct 2022 18:08:52 +0200 Source: raku-file-which Architecture: source Version: 1.0.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Rakudo Maintainers Changed-By: Dominique Dumont Closes: 1020898 Changes: raku-file-which (1.0.1-4) unstable; urgency=medium . * control: remove build-dep on prove6 * control: declare compliance with policy 4.6.1 * control: depends on
Bug#1021115: unifrac-tools: Baseline violation on x86 and FTBFS everywhere else
On Sun, Oct 02, 2022 at 05:13:33PM +0200, Étienne Mollier wrote: > Hi Adrian, > > Adrian Bunk, on 2022-10-02: > > src/Makefile: > > ... > > ifeq ($(PERFORMING_CONDA_BUILD),True) > > CPPFLAGS += -mtune=generic > > else > > CPPFLAGS += -mfma -march=native > > endif > > ... > > > > > > > > Please remove this block, it is a baseline violation on x86 > > and causes FTBFS everywhere else. > > > > Please don't use the PERFORMING_CONDA_BUILD case instead: > > -mtune=generic is already the Debian default on x86, > > but it is not supported on some/all(?) other architectures. > > Done, the PERFORMING_CONDA_BUILD variable is specific to conda > distribution and normally not related to enabling SIMD support. > Touching it on the debian package end would also enable a lot of > other bits which we probably don't need or want. I was talking about a different change that would have been wrong: -ifeq ($(PERFORMING_CONDA_BUILD),True) CPPFLAGS += -mtune=generic -else -CPPFLAGS += -mfma -march=native -endif This would have fixed the baseline violation, but broken the build on non-x86 in a different way. > Thanks for your report! > > Have a nice day, :) cu Adrian
Processed: commands
Processing commands for cont...@bugs.debian.org: > clone 1021043 -1 Bug #1021043 [src:linphone] linphone: std::logic_error in src/account/account.cpp:LinphonePrivate::Account::notifyPublishStateChanged() Bug 1021043 cloned as bug 1021125 > reassign -1 src:soci 4.0.3-1 Bug #1021125 [src:linphone] linphone: std::logic_error in src/account/account.cpp:LinphonePrivate::Account::notifyPublishStateChanged() Bug reassigned from package 'src:linphone' to 'src:soci'. No longer marked as found in versions linphone/5.0.37-5. Ignoring request to alter fixed versions of bug #1021125 to the same values previously set Bug #1021125 [src:soci] linphone: std::logic_error in src/account/account.cpp:LinphonePrivate::Account::notifyPublishStateChanged() Marked as found in versions soci/4.0.3-1. > retitle -1 soci: ABI break in soci::session causes crashes in Linphone Bug #1021125 [src:soci] linphone: std::logic_error in src/account/account.cpp:LinphonePrivate::Account::notifyPublishStateChanged() Changed Bug title to 'soci: ABI break in soci::session causes crashes in Linphone' from 'linphone: std::logic_error in src/account/account.cpp:LinphonePrivate::Account::notifyPublishStateChanged()'. > summary -1 Upstream commit 1b1b5621f5abc40bd76a54a779455e8b9c0892ff changed > the layout of several classes. Summary recorded from message bug 1021125 message > thanks Stopping processing here. Please contact me if you need assistance. -- 1021043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021043 1021125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1020793 marked as pending in gmap
Processing control commands: > tag -1 pending Bug #1020793 [src:gmap] gmap: FTBFS on avx512 host in buster Added tag(s) pending. -- 1020793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020793: marked as pending in gmap
Control: tag -1 pending Hello, Bug #1020793 in gmap reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/gmap/-/commit/0f26d2e5d8c8f9d129489b613b6ecdb0a588a350 d/rules: disable simd on non-amd64 and limit to sse2 on amd64. Closes: #1020793 (this message was generated automatically) -- Greetings https://bugs.debian.org/1020793
Bug#1017449: marked as done (nautilus-image-converter: Incompatible with Nautilus 43)
Your message dated Sun, 02 Oct 2022 16:00:11 + with message-id and subject line Bug#1017449: fixed in nautilus-image-converter 0.4.0-1 has caused the Debian Bug report #1017449, regarding nautilus-image-converter: Incompatible with Nautilus 43 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.) -- 1017449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nautilus-image-converter Severity: serious Version: 0.3.1~git20110416-2 Tags: sid bookworm nautilus-image-converter is incompatible with Nautilus 43. It would need to be converted to GTK4 to continue to work. Thank you, Jeremy Bicha --- End Message --- --- Begin Message --- Source: nautilus-image-converter Source-Version: 0.4.0-1 Done: Jeremy Bicha We believe that the bug you reported is fixed in the latest version of nautilus-image-converter, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bicha (supplier of updated nautilus-image-converter 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: Tue, 13 Sep 2022 15:21:24 -0400 Source: nautilus-image-converter Binary: nautilus-image-converter nautilus-image-converter-dbgsym Architecture: source amd64 Version: 0.4.0-1 Distribution: experimental Urgency: medium Maintainer: Debian QA Group Changed-By: Jeremy Bicha Description: nautilus-image-converter - nautilus extension to mass resize or rotate images Closes: 829873 1017449 Changes: nautilus-image-converter (0.4.0-1) experimental; urgency=medium . * QA upload * New upstream release compatible with Nautilus 43 (Closes: #1017449) * Update debian/watch and Homepage for new upstream * Build with meson (Closes: #829873) * Update packaging for current best practices * Depend on nautilus 43 Checksums-Sha1: 990beba758ea9f68812869b5659ba24da722d982 2121 nautilus-image-converter_0.4.0-1.dsc e84149d06c6378f2701d192566d0eb1bd1bf0e71 28805 nautilus-image-converter_0.4.0.orig.tar.bz2 b52f4088cbbc18db03fb02e96780bfd4a6db83ba 7108 nautilus-image-converter_0.4.0-1.debian.tar.xz 5533e60625dcc7600c483d210e072e2774da12d5 28248 nautilus-image-converter-dbgsym_0.4.0-1_amd64.deb 89c8526778ff89048af66aa7cd744c6fc8a92ea9 13698 nautilus-image-converter_0.4.0-1_amd64.buildinfo 0dd996261d2e631b32724fddb5c2a9bc5fefb35a 24180 nautilus-image-converter_0.4.0-1_amd64.deb Checksums-Sha256: 2d1fb50c69de9c797f7808985eae2c2d47a9ed17ebab286a9aa8c0667bd1e3d2 2121 nautilus-image-converter_0.4.0-1.dsc b191702f02120da9dd7afe296d390521c9308d17e3bcf4df744e6146af15b123 28805 nautilus-image-converter_0.4.0.orig.tar.bz2 bdedf5bf29ecf986aa4dc8f1245ca9d21b9b159f59928e65f06b16596eb233fe 7108 nautilus-image-converter_0.4.0-1.debian.tar.xz 989db236a0bf9ede9261e33e803d087dbc5e06db76e91ba4890ad3f539db8f81 28248 nautilus-image-converter-dbgsym_0.4.0-1_amd64.deb a684099b5957cff15666fdff8349410731fd0da46a32c1c95a435fd112575566 13698 nautilus-image-converter_0.4.0-1_amd64.buildinfo 1f28881e3fdd583d95b8ff4c1cbd866c98a1f785f20a88cc3d848fda313c0373 24180 nautilus-image-converter_0.4.0-1_amd64.deb Files: 8b3bc89c6d9f9766d73b37c02a578d03 2121 gnome optional nautilus-image-converter_0.4.0-1.dsc 73d24b5f6b502956793ace5f4a26e6a1 28805 gnome optional nautilus-image-converter_0.4.0.orig.tar.bz2 69c84e2493626e4c8d34771a9e52f2ed 7108 gnome optional nautilus-image-converter_0.4.0-1.debian.tar.xz f688fce1fab74abb1bc191ac8173046b 28248 debug optional nautilus-image-converter-dbgsym_0.4.0-1_amd64.deb 69d2fc3212886575b89b545a2143fea5 13698 gnome optional nautilus-image-converter_0.4.0-1_amd64.buildinfo a1045fff307b3c5c8424cef24edee36b 24180 gnome optional nautilus-image-converter_0.4.0-1_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmMg3PkACgkQ5mx3Wuv+ bH3D1RAAn2BPBvigPP+JraJgVtSW/r8gck/JlBzITGSjpOzxwJArvq90+PNrveGX yick+xZs0hJK9FSTK9KWu2S9CQrsry70d6LxV7fHzSrFHAyrljwbhTMkp4WjMR35 byr3wXO2JB4moNu3emATIKt2qjBdPLuenK/ZtuL2eecROhHIToPJPo3G0mCeEe4U
Processed: cloning 1020898, reassign -1 to perl6-readline
Processing commands for cont...@bugs.debian.org: > clone 1020898 -1 Bug #1020898 [perl6-readline,raku-file-which,raku-librarycheck,raku-readline] Uninstallable due to file conflict A37F26876B58371B70EDD889AD69F064C90AC2C6 Bug 1020898 cloned as bug 1021124 > reassign -1 perl6-readline Bug #1021124 [perl6-readline,raku-file-which,raku-librarycheck,raku-readline] Uninstallable due to file conflict A37F26876B58371B70EDD889AD69F064C90AC2C6 Bug reassigned from package 'perl6-readline,raku-file-which,raku-librarycheck,raku-readline' to 'perl6-readline'. Ignoring request to alter found versions of bug #1021124 to the same values previously set Ignoring request to alter fixed versions of bug #1021124 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1020898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020898 1021124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020898: Uninstallable due to file conflict A37F26876B58371B70EDD889AD69F064C90AC2C6
On Wed, 28 Sep 2022 12:17:48 +0200 Dominique Dumont wrote: > I'll have to reach out to upstream to investigate. I've a fix from upstream for rakudo package. The fix is added in rakudo 2020.07-2 I need to re-upload the affected module packages to depend on that version of rakudo (so the package is rebuilt without the conflicting file). I will not upload a new version of perl6-readline. This package is replaced by raku-readline and has a RM bug filed. All the best Dod
Bug#1021076: marked as done (pdfarranger: version 1.8.2 incompatible with pikepdf 6 - please upgrade)
Your message dated Sun, 02 Oct 2022 15:21:36 + with message-id and subject line Bug#1020639: fixed in pdfarranger 1.9.1-1 has caused the Debian Bug report #1020639, regarding pdfarranger: version 1.8.2 incompatible with pikepdf 6 - please upgrade 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.) -- 1020639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pdfarranger Version: 1.8.2-1 Severity: important Hi, when trying to save the pdf, it shows: "Use pikepdf.pdf.pages interface to copy pages from one PDF to another" This is already known: https://github.com/pdfarranger/pdfarranger/issues/716 and latest pdfarranger version has fixed it. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-2-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 Versions of packages pdfarranger depends on: ii gir1.2-glib-2.01.74.0-2 ii gir1.2-gtk-3.0 3.24.34-3 ii gir1.2-poppler-0.1822.08.0-2.1 ii python33.10.6-1 ii python3-cairo 1.20.1-3+b1 ii python3-dateutil 2.8.1-6 ii python3-gi 3.42.2-2 ii python3-gi-cairo 3.42.2-2 ii python3-pikepdf6.0.0+dfsg-1 ii python3-pkg-resources 65.3.0-1.1 Versions of packages pdfarranger recommends: ii python3-img2pdf 0.4.4-2 pdfarranger suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: pdfarranger Source-Version: 1.9.1-1 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of pdfarranger, 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 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated pdfarranger 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 Oct 2022 16:49:46 +0200 Source: pdfarranger Architecture: source Version: 1.9.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Jérémy Lal Closes: 1020639 Changes: pdfarranger (1.9.1-1) unstable; urgency=medium . * Team upload. * New upstream version 1.9.1 (Closes: #1020639). * Fix debian/watch Checksums-Sha1: 0ef43b7fb0b120d011ff7fdcaa03630f8c360db9 2142 pdfarranger_1.9.1-1.dsc 028379e1a54073ecb9efc51ba2cd6c697a0d37fb 279138 pdfarranger_1.9.1.orig.tar.gz 3be8cf64b2d8a0e49091b4e5168c107407b1d8a1 4804 pdfarranger_1.9.1-1.debian.tar.xz 641a28438250124dc32e87a9f81c2bb1cbfbe9b5 8073 pdfarranger_1.9.1-1_source.buildinfo Checksums-Sha256: 059a34c155d798f007893a56447a6bb8d2c06a37591b498de560733c9d1034ee 2142 pdfarranger_1.9.1-1.dsc a0d91226d19977c5e12fdaac5c1e65dbd0685ef75d1be545f1a595bf020c9894 279138 pdfarranger_1.9.1.orig.tar.gz e1c0735d1950a2746b5531d592fab633fa5418c10b7737bcf6c8fe6b66411f41 4804 pdfarranger_1.9.1-1.debian.tar.xz 4e3514282c1a6910d48698dd0a674512806e427586057ee4b4a2d2f3710f8857 8073 pdfarranger_1.9.1-1_source.buildinfo Files: 8aef8c07a78c5ebe583b20a1dd6b6775 2142 graphics optional pdfarranger_1.9.1-1.dsc 91f5c1c85da9d603b6ebb6936311d77e 279138 graphics optional pdfarranger_1.9.1.orig.tar.gz 95e0eea0e906f927b2d32d4d1f767d93 4804 graphics optional pdfarranger_1.9.1-1.debian.tar.xz 3a5608cbc43125027b25497382367b90 8073 graphics optional pdfarranger_1.9.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmM5pR0SHGthcG91ZXJA bWVsaXgub3JnAAoJEGYRwF7dOfN0EOYQAKOF9D7uoLC+1822y7h5ljUhn//3gOcS FVIZEHDVUhcE/+eZo9b0oASXddZxdKulM7hrh2zE1BMqwAfu4kayIJdkBbrWeQrP UflPN5s2OzLZYp7xW8/y6KPNTO+l7rLvhMF61i11TmArlxGHHs6wWlCZwc6xoLqY MYxNytD2F7LEiddekgSQlrns79zILPKlxjRqrNNpP+JTIIgix6Bo5FbpvAZhPrl8 Rh0W0rp5qWz+AdusqkRlsftJW7VMBllmJFwW9JaTmApmeypKzsNVqh+P+Us5o4u/ 2DE7DbSAamwzPE1D27dIdgVWrRWnffYFk2+hJbb1oBjZG2pjiM0Q9sOnmdeLQ3jE
Bug#1020639: marked as done (pdfarranger: libqpdf 11 require pdfarranger 1.9.1)
Your message dated Sun, 02 Oct 2022 15:21:36 + with message-id and subject line Bug#1020639: fixed in pdfarranger 1.9.1-1 has caused the Debian Bug report #1020639, regarding pdfarranger: libqpdf 11 require pdfarranger 1.9.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1020639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pdfarranger Version: 1.8.2-1 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: jeromerob...@gmx.com Dear Maintainer, pdfarranger depends on pikepdf. pikepdf 5.1.1 FTBS with libqpdf 11: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019694 According to Salsa pikepdf 6 is about to be uploaded. Once done pdfarranger will stop working because of: https://github.com/pdfarranger/pdfarranger/issues/716 So pdfarranger should be updated to 1.9.1. Tagging as grave because pdfarranger has already been removed from testing because pikepdf was removed from testing because of 1019694. Once pikepdf will be back in version 6 pdfarranger will be unusable. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pdfarranger depends on: ii gir1.2-glib-2.01.73.0+ds-1 ii gir1.2-gtk-3.0 3.24.34-3 ii gir1.2-poppler-0.1822.08.0-2.1 ii python33.10.6-1 ii python3-cairo 1.20.1-3+b1 ii python3-dateutil 2.8.1-6 ii python3-gi 3.42.2-2 ii python3-gi-cairo 3.42.2-2 ii python3-pikepdf5.1.1+dfsg-1+b1 ii python3-pkg-resources 65.3.0-1.1 Versions of packages pdfarranger recommends: ii python3-img2pdf 0.4.4-2 pdfarranger suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: pdfarranger Source-Version: 1.9.1-1 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of pdfarranger, 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 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated pdfarranger 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 Oct 2022 16:49:46 +0200 Source: pdfarranger Architecture: source Version: 1.9.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Jérémy Lal Closes: 1020639 Changes: pdfarranger (1.9.1-1) unstable; urgency=medium . * Team upload. * New upstream version 1.9.1 (Closes: #1020639). * Fix debian/watch Checksums-Sha1: 0ef43b7fb0b120d011ff7fdcaa03630f8c360db9 2142 pdfarranger_1.9.1-1.dsc 028379e1a54073ecb9efc51ba2cd6c697a0d37fb 279138 pdfarranger_1.9.1.orig.tar.gz 3be8cf64b2d8a0e49091b4e5168c107407b1d8a1 4804 pdfarranger_1.9.1-1.debian.tar.xz 641a28438250124dc32e87a9f81c2bb1cbfbe9b5 8073 pdfarranger_1.9.1-1_source.buildinfo Checksums-Sha256: 059a34c155d798f007893a56447a6bb8d2c06a37591b498de560733c9d1034ee 2142 pdfarranger_1.9.1-1.dsc a0d91226d19977c5e12fdaac5c1e65dbd0685ef75d1be545f1a595bf020c9894 279138 pdfarranger_1.9.1.orig.tar.gz e1c0735d1950a2746b5531d592fab633fa5418c10b7737bcf6c8fe6b66411f41 4804 pdfarranger_1.9.1-1.debian.tar.xz 4e3514282c1a6910d48698dd0a674512806e427586057ee4b4a2d2f3710f8857 8073 pdfarranger_1.9.1-1_source.buildinfo Files: 8aef8c07a78c5ebe583b20a1dd6b6775 2142 graphics optional pdfarranger_1.9.1-1.dsc 91f5c1c85da9d603b6ebb6936311d77e 279138 graphics optional pdfarranger_1.9.1.orig.tar.gz 95e0eea0e906f927b2d32d4d1f767d93 4804 graphics optional pdfarranger_1.9.1-1.debian.tar.xz 3a5608cbc43125027b25497382367b90 8073 graphics optional pdfarranger_1.9.1-1_source.buildinfo -BEGIN PGP SIGNATURE-
Bug#1021115: unifrac-tools: Baseline violation on x86 and FTBFS everywhere else
Hi Adrian, Adrian Bunk, on 2022-10-02: > src/Makefile: > ... > ifeq ($(PERFORMING_CONDA_BUILD),True) > CPPFLAGS += -mtune=generic > else > CPPFLAGS += -mfma -march=native > endif > ... > > > > Please remove this block, it is a baseline violation on x86 > and causes FTBFS everywhere else. > > Please don't use the PERFORMING_CONDA_BUILD case instead: > -mtune=generic is already the Debian default on x86, > but it is not supported on some/all(?) other architectures. Done, the PERFORMING_CONDA_BUILD variable is specific to conda distribution and normally not related to enabling SIMD support. Touching it on the debian package end would also enable a lot of other bits which we probably don't need or want. Thanks for your report! Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. On air: Life Line Project - The King - Doom signature.asc Description: PGP signature
Bug#1021123: libgdbm-compat-dev: missing dependency on libgdbm-dev
Package: libgdbm-compat-dev Version: 1.23-2 Severity: serious Justification: Policy 3.5 The header files in libgdbm-compat-dev (dbm.h, gdbm-ndbm.h, and ndbm.h) all have "#include ". libgdbm-compat-dev therefore needs to depend on libgdbm-dev so that this #include can be resolved. (Noticed while improving man-db's upstream CI jobs.) Thanks, -- Colin Watson (he/him) [cjwat...@debian.org]
Bug#1021121: not installable due to new python3-matrix-nio
Package: python3-pantalaimon Version: 0.10.4-2 Severity: grave Tags: fixed-upstream Hi, I've uploaded python3-matrix-nio 0.20.0 to unstable to close a security issue. Sadly python3-pantalaimon has a versioned dependency making it now uninstallable: python3-matrix-nio (<< 0.20). There is a new upstream version (0.10.5) bumping just this dependency so I would propose to rather drop the version locking. I'm filling this bug instead as the package is already in the group. Cheers Jochen
Processed: commands
Processing commands for cont...@bugs.debian.org: > reassign 1021043 src:linphone 5.0.37-5 Bug #1021043 [linphone] linphone: std::logic_error in src/account/account.cpp:LinphonePrivate::Account::notifyPublishStateChanged() Bug reassigned from package 'linphone' to 'src:linphone'. No longer marked as found in versions 5.0.37-5. Ignoring request to alter fixed versions of bug #1021043 to the same values previously set Bug #1021043 [src:linphone] linphone: std::logic_error in src/account/account.cpp:LinphonePrivate::Account::notifyPublishStateChanged() Marked as found in versions linphone/5.0.37-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 1021043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021115: marked as done (unifrac-tools: Baseline violation on x86 and FTBFS everywhere else)
Your message dated Sun, 02 Oct 2022 14:44:06 + with message-id and subject line Bug#1021115: fixed in unifrac-tools 1.1.1-3 has caused the Debian Bug report #1021115, regarding unifrac-tools: Baseline violation on x86 and FTBFS everywhere else 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.) -- 1021115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: unifrac-tools Version: 1.1.1-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: Debian Med Packaging Team , Étienne Mollier https://buildd.debian.org/status/fetch.php?pkg=unifrac-tools=armel=1.1.1-1=1664713094=0 ... h5c++ -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp -mfma -march=native -Wextra -Wno-unused-parameter -Wall -std=c++11 -pedantic -I. -O4 -fPIC -L/<>/debian/tmp/usr/lib -c tree.cpp -o tree.o arm-linux-gnueabi-g++: error: unrecognized command-line option ‘-mfma’ ... https://buildd.debian.org/status/fetch.php?pkg=unifrac-tools=amd64=1.1.1-2=1664716667=0 ... h5c++ -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp -mfma -march=native -Wextra -Wno-unused-parameter -Wall -std=c++11 -pedantic -I. -O4 -fPIC -L/<>/debian/tmp/usr/lib -c tree.cpp -o tree.o ... src/Makefile: ... ifeq ($(PERFORMING_CONDA_BUILD),True) CPPFLAGS += -mtune=generic else CPPFLAGS += -mfma -march=native endif ... Please remove this block, it is a baseline violation on x86 and causes FTBFS everywhere else. Please don't use the PERFORMING_CONDA_BUILD case instead: -mtune=generic is already the Debian default on x86, but it is not supported on some/all(?) other architectures. --- End Message --- --- Begin Message --- Source: unifrac-tools Source-Version: 1.1.1-3 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of unifrac-tools, 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 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated unifrac-tools 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 Oct 2022 15:31:39 +0200 Source: unifrac-tools Architecture: source Version: 1.1.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1021115 Changes: unifrac-tools (1.1.1-3) unstable; urgency=medium . * baseline.patch: fix baseline violation and ftbfs on non-amd64. (Closes: #1021115) Checksums-Sha1: 721e05321b94fe6748c1651ade686e10a3a53371 2281 unifrac-tools_1.1.1-3.dsc 34efa430fe51dbe97944e339aeeb9491b9d450d8 7236 unifrac-tools_1.1.1-3.debian.tar.xz e0f9f3635ac90904b25f36ef617df566d50baad9 8759 unifrac-tools_1.1.1-3_amd64.buildinfo Checksums-Sha256: beb7d0ddbaff153030b3e3e2ec5768d3cef83659e9d997ae4bdf50d33285c15a 2281 unifrac-tools_1.1.1-3.dsc f23db4f1a11aeae8f0bf6c5a81adc11f7734a6430c706b3687c2b18c991d2088 7236 unifrac-tools_1.1.1-3.debian.tar.xz 0f5cc57bc23f95d832be0436aac419b1abd60e481a20e97e64dd63cb4704e406 8759 unifrac-tools_1.1.1-3_amd64.buildinfo Files: cbfecf7a66a32705ddec3b7a7719be11 2281 science optional unifrac-tools_1.1.1-3.dsc a28c6dd12fa4abe23c7656841c6a2dd9 7236 science optional unifrac-tools_1.1.1-3.debian.tar.xz 88ee5c90ce56b9ec9366fa06c4b1e134 8759 science optional unifrac-tools_1.1.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmM5nwMUHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdryWw//U6AwH3N+3KM8HXNJ8W6Lqsjm11c2 Piw7Y7Z0ammBC3y5NuOV8RJHBwovE4WWdrA1rCXOFreZ3ty8sPgo1meBcmPL8twr 8fnmLDnRjzjLaB0lwCvU8/BAcp/90AenJ876WUQ20LNiUz40mDv0LMTSvopyMMDm 4ZE4a5PW4EMuSPdkAPD2IiNqLQOtnJ3p1QVQ7NREXJt6y2vIz4bqo+rCQ3DAuEhE BrI/onaQrl3g0x4+YQfkx0BaXG6ZwWXETMnmR4wUFYiMTD5qwqQP04PYSknLLECl 3liQbI1S+zuxbEFRkL/rD8vRzzx8vucqkimYHWJEgcMT2LlKM8pux+I6rUae3kOq pVBOAow6w06ouT6sZ399jYYkPxQVnyyReLA2HyU97VjTnmlPWUDRUZ+ZbbO/hm7Z Ts+AMewia0GqisXlCBVe1jqWWSwjZLKPwovPO+p0LIntI3SIMpSl0zPuJa7d5DN5 ANlVpOwwB23htgd/Lx0sK1inWWkxd3GMqAYQivK9MFA6hljk/1DVF8ozbEItduQ7 QJijnrSEpgYFBSz3Ml7m6PbNDAUulWKpyjJIg8cSW4ms+ahs3aTfVjeEGakIpIPg
Bug#1020211: version in bookworm is not affected
Grmml On 02-10-2022 16:31, Paul Gevers wrote: # this should prevent autoremoval for now notfound 1020211 53.0+dfsg-1 Of course that didn't work. Because now the BTS treats all previous versions as affected. It doesn't matter, let's keep this on our radar and ping the bug as long as the solution is unclear but testing is unaffected. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: version in bookworm is not affected
Processing commands for cont...@bugs.debian.org: > # instead of marking the bug as affecting sid only (which may become > # outdated when emacs migrates) let's assume this bug wasn't found to be > # affecting 53.0+dfsg-1 (which is *currently* true) > # this should prevent autoremoval for now > notfound 1020211 53.0+dfsg-1 Bug #1020211 [src:emacspeak] emacspeak: FTBFS: make[4]: *** [Makefile:322: emacspeak-loaddefs.el] Error 255 No longer marked as found in versions emacspeak/53.0+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1020211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020211 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020211: emacspeak: FTBFS: make[4]: *** [Makefile:322: emacspeak-loaddefs.el] Error 255
Control: fixed -1 53.0+dfsg-2 Hi, On Sun, 18 Sep 2022 08:52:28 +0200 Lucas Nussbaum wrote: During a rebuild of all packages in sid, your package failed to build on amd64. While this is worked around in the version in unstable, the underlying problem isn't. The problem is that emacs 28 has a new feature called native compilation. It's currently being investigated by the emacs toolchain maintainers how to work around properties of native compilation in the context of a distribution (e.g. on IRC in #d-emacs). Until that's done, emacs 28 will not migrate to testing, hence this issue (and the failure to install emacspeak in unstable, which is currently blocking migration of emacspeak itself) is not affecting testing (yet). As emacspeak isn't using the default tool (dh-elpa) yet, we may have to fix the code that runs during installation ourselves, but until the emacs maintainers have figured out what's best in general, I propose to wait with fixing it in emacspeak. Migrating to use dh-elpa will probably mean we don't need to do anything in emacspeak to fix the native compilation problem ourselves, but last time I looked into that, it didn't look trivial for emacspeak. If anybody wants to invest their time into the dh-elpa migration, I would applaud that. For now, keep an eye on it, prevent removal of emacspeak from testing, and how we don't have to do too much to fix the situation once emacs is ready to migrate. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: emacspeak: FTBFS: make[4]: *** [Makefile:322: emacspeak-loaddefs.el] Error 255
Processing control commands: > fixed -1 53.0+dfsg-2 Bug #1020211 [src:emacspeak] emacspeak: FTBFS: make[4]: *** [Makefile:322: emacspeak-loaddefs.el] Error 255 Marked as fixed in versions emacspeak/53.0+dfsg-2. -- 1020211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020211 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020639: pdfarranger: libqpdf 11 require pdfarranger 1.9.1
On Sun, Oct 2, 2022 at 8:15 AM Jérémy Lal wrote: > i've prepared and pushed an update to salsa. > > I can upload it, if no one is planning to do it. Go ahead. Thank you, Jeremy Bicha
Bug#1021117: llvm-15-dev: cmake fails on missing /usr/lib/llvm-15/bin/mlir-tblgen
Package: llvm-15-dev
Version: 1:15.0.1-1~exp2
Severity: serious
Hi,
while trying to package spirv-llvm-translator-15, I encountred the
following cmake error:
dh_auto_configure -- \
-DCMAKE_SKIP_RPATH=ON \
-DLLVM_EXTERNAL_SPIRV_HEADERS_SOURCE_DIR=/usr/include \
-DBUILD_SHARED_LIBS=ON \
-DLLVM_SPIRV_INCLUDE_TESTS=ON \
-DLLVM_EXTERNAL_LIT=/usr/lib/llvm-15/build/utils/lit/lit.py \
-Wno-dev
cd build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON
-DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles"
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu
-DCMAKE_SKIP_RPATH=ON -DLLVM_EXTERNAL_SPIRV_HEADERS_SOURCE_DIR=/usr/include
-DBUILD_SHARED_LIBS=ON -DLLVM_SPIRV_INCLUDE_TESTS=ON
-DLLVM_EXTERNAL_LIT=/usr/lib/llvm-15/build/utils/lit/lit.py -Wno-dev ..
-- Found PkgConfig: /usr/bin/pkg-config (found version "1.8.0")
-- Using SPIR-V Headers from
/usr/include
-- The CXX compiler identification is GNU 12.2.0
-- The C compiler identification is GNU 12.2.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Performing Test HAVE_FFI_CALL
-- Performing Test HAVE_FFI_CALL - Success
-- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so
-- Performing Test Terminfo_LINKABLE
-- Performing Test Terminfo_LINKABLE - Success
-- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so
-- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR)
-- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version "2.9.14")
CMake Error at /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake:1634 (message):
The imported target "mlir-tblgen" references the file
"/usr/lib/llvm-15/bin/mlir-tblgen"
but this file does not exist. Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
"/usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake"
but not all the files it references.
Call Stack (most recent call first):
/usr/lib/llvm-15/cmake/LLVMConfig.cmake:329 (include)
CMakeLists.txt:82 (find_package)
-- Configuring incomplete, errors occurred!
The corresponding find_package() call is
...
if(NOT DEFINED BASE_LLVM_VERSION)
set (BASE_LLVM_VERSION 15.0.0)
endif(NOT DEFINED BASE_LLVM_VERSION)
...
if(LLVM_SPIRV_INCLUDE_TESTS)
set(LLVM_TEST_COMPONENTS
llvm-as
llvm-dis
)
endif(LLVM_SPIRV_INCLUDE_TESTS)
find_package(LLVM ${BASE_LLVM_VERSION} REQUIRED
COMPONENTS
Analysis
BitReader
BitWriter
CodeGen
Core
Passes
Support
TransformUtils
${LLVM_TEST_COMPONENTS}
)
...
This works fine with llvm-14 and spirv-llvm-translator-14.
If I work around this by adding a B-D: mlir-15-tools, the next problem is
CMake Error at /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake:1634 (message):
The imported target "MLIRSupportIndentedOstream" references the file
"/usr/lib/llvm-15/lib/libMLIRSupportIndentedOstream.a"
but this file does not exist. Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
"/usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake"
but not all the files it references.
Call Stack (most recent call first):
/usr/lib/llvm-15/cmake/LLVMConfig.cmake:329 (include)
CMakeLists.txt:82 (find_package)
-- Configuring incomplete, errors occurred!
Next one is
CMake Error at /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake:1634 (message):
The imported target "sancov" references the file
"/usr/lib/llvm-15/bin/sancov"
but this file does not exist. Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
"/usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake"
but not all the files it references.
Call Stack (most recent call first):
/usr/lib/llvm-15/cmake/LLVMConfig.cmake:329 (include)
CMakeLists.txt:82 (find_package)
-- Configuring incomplete, errors occurred!
and now I'm stopping chasing missing
Bug#1021115: marked as pending in unifrac-tools
Control: tag -1 pending Hello, Bug #1021115 in unifrac-tools reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/unifrac-tools/-/commit/7c843f12740a6a262b756196e5535db4ddb6ed8b baseline.patch: fix baseline violation and ftbfs on non-amd64. Closes: #1021115 (this message was generated automatically) -- Greetings https://bugs.debian.org/1021115
Processed: Bug#1021115 marked as pending in unifrac-tools
Processing control commands: > tag -1 pending Bug #1021115 [src:unifrac-tools] unifrac-tools: Baseline violation on x86 and FTBFS everywhere else Warning: Unknown package 'src:unifrac-tools' Added tag(s) pending. Warning: Unknown package 'src:unifrac-tools' -- 1021115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021115: unifrac-tools: Baseline violation on x86 and FTBFS everywhere else
Source: unifrac-tools Version: 1.1.1-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: Debian Med Packaging Team , Étienne Mollier https://buildd.debian.org/status/fetch.php?pkg=unifrac-tools=armel=1.1.1-1=1664713094=0 ... h5c++ -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp -mfma -march=native -Wextra -Wno-unused-parameter -Wall -std=c++11 -pedantic -I. -O4 -fPIC -L/<>/debian/tmp/usr/lib -c tree.cpp -o tree.o arm-linux-gnueabi-g++: error: unrecognized command-line option ‘-mfma’ ... https://buildd.debian.org/status/fetch.php?pkg=unifrac-tools=amd64=1.1.1-2=1664716667=0 ... h5c++ -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp -mfma -march=native -Wextra -Wno-unused-parameter -Wall -std=c++11 -pedantic -I. -O4 -fPIC -L/<>/debian/tmp/usr/lib -c tree.cpp -o tree.o ... src/Makefile: ... ifeq ($(PERFORMING_CONDA_BUILD),True) CPPFLAGS += -mtune=generic else CPPFLAGS += -mfma -march=native endif ... Please remove this block, it is a baseline violation on x86 and causes FTBFS everywhere else. Please don't use the PERFORMING_CONDA_BUILD case instead: -mtune=generic is already the Debian default on x86, but it is not supported on some/all(?) other architectures.
Bug#1020190: marked as done (shut-up: FTBFS: make: *** [debian/rules:4: build] Error 25)
Your message dated Sun, 02 Oct 2022 13:19:11 +
with message-id
and subject line Bug#1020190: fixed in shut-up 0.3.3-4
has caused the Debian Bug report #1020190,
regarding shut-up: FTBFS: make: *** [debian/rules:4: build] 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.)
--
1020190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shut-up
Version: 0.3.3-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> /bin/true
> make[1]: Leaving directory '/<>'
>dh_elpa_test
> emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list
> \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list
> 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f
> package-initialize -L . -L test -l test/shut-up-test.el --eval
> \(ert-run-tests-batch-and-exit\)
> Running 7 tests (2022-09-17 20:06:11+, selector ‘t’)
> Test shut-up/binds-the-sink-buffer-in-body backtrace:
> error("Cannot find suitable directory for output in `nati...")
> comp-trampoline-compile(load)
> comp-subr-trampoline-install(load)
> fset(load #)
> (unwind-protect (progn (fset 'load #'shut-up-load) (fset 'write-regi
> (let* ((vnew #'(lambda (char) (shut-up-insert-to-buffer char shut-up
> (unwind-protect (let* ((vnew #'(lambda (char) (shut-up-insert-to-buf
> (if shut-up-ignore (progn (let* ((fn-0 #'bufferp) (args-1 (condition
> (let* ((--cl-shut-up-current-output-- #'(lambda nil (or (shut-up-buf
> (let ((shut-up-sink (generate-new-buffer " *shutup*")) (inhibit-mess
> (let ((lexical-binding t)) (let ((shut-up-sink (generate-new-buffer
> (closure (t) nil (let ((lexical-binding t)) (let ((shut-up-sink (gen
> ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
> ert-run-test(#s(ert-test :name shut-up/binds-the-sink-buffer-in-body
> ert-run-or-rerun-test(#s(ert--stats :selector t :tests [#s(ert-test
> ert-run-tests(t #f(compiled-function (event-type event-args) #
> ert-run-tests-batch(nil)
> ert-run-tests-batch-and-exit()
> command-line-1(("-l" "package" "--eval" "(add-to-list 'package-direc
> command-line()
> normal-top-level()
> Test shut-up/binds-the-sink-buffer-in-body condition:
> (error "Cannot find suitable directory for output in
> ‘native-comp-eln-load-path’")
>FAILED 1/7 shut-up/binds-the-sink-buffer-in-body (0.038730 sec)
> Test shut-up/handles-message-with-nil-argument backtrace:
> error("Cannot find suitable directory for output in `nati...")
> comp-trampoline-compile(load)
> comp-subr-trampoline-install(load)
> fset(load #)
> (unwind-protect (progn (fset 'load #'shut-up-load) (fset 'write-regi
> (let* ((vnew #'(lambda (char) (shut-up-insert-to-buffer char shut-up
> (unwind-protect (let* ((vnew #'(lambda (char) (shut-up-insert-to-buf
> (if shut-up-ignore (progn (message nil) (let* ((fn-40 #'s-blank\?) (
> (let* ((--cl-shut-up-current-output-- #'(lambda nil (or (shut-up-buf
> (let ((shut-up-sink (generate-new-buffer " *shutup*")) (inhibit-mess
> (let ((lexical-binding t)) (let ((shut-up-sink (generate-new-buffer
> (closure (t) nil (let ((lexical-binding t)) (let ((shut-up-sink (gen
> ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
> ert-run-test(#s(ert-test :name shut-up/handles-message-with-nil-argu
> ert-run-or-rerun-test(#s(ert--stats :selector t :tests [... ... ...
> ert-run-tests(t #f(compiled-function (event-type event-args) #
> ert-run-tests-batch(nil)
> ert-run-tests-batch-and-exit()
> command-line-1(("-l" "package" "--eval" "(add-to-list 'package-direc
> command-line()
> normal-top-level()
> Test shut-up/handles-message-with-nil-argument condition:
> (error "Cannot find suitable directory for output in
> ‘native-comp-eln-load-path’")
>FAILED 2/7 shut-up/handles-message-with-nil-argument (0.000802 sec)
> Test shut-up/ignore backtrace:
> error("Cannot find suitable directory for output in `nati...")
> comp-trampoline-compile(load)
> comp-subr-trampoline-install(load)
> fset(load #)
> (unwind-protect (progn (fset 'load #'shut-up-load) (fset 'write-regi
> (let* ((vnew #'(lambda (char) (shut-up-insert-to-buffer char shut-up
> (unwind-protect (let* ((vnew #'(lambda (char) (shut-up-insert-to-buf
> (if shut-up-ignore (progn
Bug#1021113: libgrpc22 in experimental needs a rebuild with newer libabsl
Package: libgrpc22 Severity: serious Version: 1.44.0-3 Setting up sbuild-build-depends-dose3-dummy (0.invalid.0) ... (I)Doseparse: Parsing and normalizing... (I)Dose_deb: Parsing Packages file -... (I)Dose_common: total packages 69949 (I)Dose_applications: Cudf Universe: 69949 packages (I)Dose_applications: --checkonly specified, consider all packages as background packages (I)Dose_applications: Solving... output-version: 1.2 native-architecture: amd64 report: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 status: broken reasons: - missing: pkg: package: libgrpc22 version: 1.44.0-3 architecture: amd64 unsat-dependency: libabsl20210324:amd64 (>= 0~20210324.2-1) depchains: - depchain: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 depends: ruby-grpc:amd64 (>= 1.42~) - package: ruby-grpc version: 1.44.0-3 architecture: amd64 depends: libgrpc22:amd64 (>= 1.44.0) background-packages: 69948 foreground-packages: 1 total-packages: 69949
Bug#1020189: helpful-el: FTBFS: make: *** [debian/rules:4: binary] Error 25
Lucas Nussbaum writes: > Source: helpful-el > Version: 0.19-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220917 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. this seems unrelated to native compilation, probably needs an upstream fix for emacs 28
Bug#1020639: pdfarranger: libqpdf 11 require pdfarranger 1.9.1
Package: pdfarranger Followup-For: Bug #1020639 Hi, i've prepared and pushed an update to salsa. I can upload it, if no one is planning to do it. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-2-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 Versions of packages pdfarranger depends on: ii gir1.2-glib-2.01.74.0-2 ii gir1.2-gtk-3.0 3.24.34-3 ii gir1.2-poppler-0.1822.08.0-2.1 ii python33.10.6-1 ii python3-cairo 1.20.1-3+b1 ii python3-dateutil 2.8.1-6 ii python3-gi 3.42.2-2 ii python3-gi-cairo 3.42.2-2 ii python3-pikepdf6.0.0+dfsg-1 ii python3-pkg-resources 65.3.0-1.1 Versions of packages pdfarranger recommends: ii python3-img2pdf 0.4.4-2 pdfarranger suggests no packages. -- no debconf information
Bug#1013034: marked as done (sane-backends: ftbfs with GCC-12)
Your message dated Sun, 02 Oct 2022 12:04:03 + with message-id and subject line Bug#1013034: fixed in sane-backends 1.1.1-6 has caused the Debian Bug report #1013034, regarding sane-backends: ftbfs with GCC-12 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.) -- 1013034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sane-backends Version: 1.1.1-5 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/sane-backends_1.1.1-5_unstable_gcc12.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] 109 | operator<<(basic_ostream<_CharT, _Traits>& __os, _Setiosflags __f) | ^~~~ /usr/include/c++/12/iomanip:109:5: note: template argument deduction/substitution failed: minigtest.h:43:29: note: cannot convert ‘t’ (type ‘const std::vector’) to type ‘std::_Setiosflags’ 43 | std::cerr << " :\n" << t << " != " << u << "\n\n"; | ^~~~ /usr/include/c++/12/iomanip:143:5: note: candidate: ‘template std::basic_ostream<_CharT, _Traits>& std::operator<<(basic_ostream<_CharT, _Traits>&, _Setbase)’ 143 | operator<<(basic_ostream<_CharT, _Traits>& __os, _Setbase __f) | ^~~~ /usr/include/c++/12/iomanip:143:5: note: template argument deduction/substitution failed: minigtest.h:43:29: note: cannot convert ‘t’ (type ‘const std::vector’) to type ‘std::_Setbase’ 43 | std::cerr << " :\n" << t << " != " << u << "\n\n"; | ^~~~ /usr/include/c++/12/iomanip:178:5: note: candidate: ‘template std::basic_ostream<_CharT, _Traits>& std::operator<<(basic_ostream<_CharT, _Traits>&, _Setfill<_CharT>)’ 178 | operator<<(basic_ostream<_CharT, _Traits>& __os, _Setfill<_CharT> __f) | ^~~~ /usr/include/c++/12/iomanip:178:5: note: template argument deduction/substitution failed: minigtest.h:43:29: note: ‘std::vector’ is not derived from ‘std::_Setfill<_CharT>’ 43 | std::cerr << " :\n" << t << " != " << u << "\n\n"; | ^~~~ /usr/include/c++/12/iomanip:208:5: note: candidate: ‘template std::basic_ostream<_CharT, _Traits>& std::operator<<(basic_ostream<_CharT, _Traits>&, _Setprecision)’ 208 | operator<<(basic_ostream<_CharT, _Traits>& __os, _Setprecision __f) | ^~~~ /usr/include/c++/12/iomanip:208:5: note: template argument deduction/substitution failed: minigtest.h:43:29: note: cannot convert ‘t’ (type ‘const std::vector’) to type ‘std::_Setprecision’ 43 | std::cerr << " :\n" << t << " != " << u << "\n\n"; | ^~~~ /usr/include/c++/12/iomanip:238:5: note: candidate: ‘template std::basic_ostream<_CharT, _Traits>& std::operator<<(basic_ostream<_CharT, _Traits>&, _Setw)’ 238 | operator<<(basic_ostream<_CharT, _Traits>& __os, _Setw __f) | ^~~~ /usr/include/c++/12/iomanip:238:5: note: template argument deduction/substitution failed: minigtest.h:43:29: note: cannot convert ‘t’ (type ‘const std::vector’) to type ‘std::_Setw’ 43 | std::cerr << " :\n" << t << " != " << u << "\n\n"; | ^~~~
Bug#1015055: marked as done (ayatana-indicator-power: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2)
Your message dated Sun, 02 Oct 2022 11:34:01 + with message-id and subject line Bug#1015055: fixed in ayatana-indicator-power 22.9.0-1 has caused the Debian Bug report #1015055, regarding ayatana-indicator-power: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1015055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ayatana-indicator-power Version: 22.2.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>/obj-x86_64-linux-gnu' > Running tests... > /usr/bin/ctest --force-new-ctest-process --verbose -j8 > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > Test project /<>/obj-x86_64-linux-gnu > Constructing a list of tests > Done constructing a list of tests > Updating test list for fixtures > Added 0 tests to meet fixture requirements > Checking test dependency graph... > Checking test dependency graph end > test 1 > Start 1: test-notify > > 1: Test command: /<>/obj-x86_64-linux-gnu/tests/test-notify > 1: Test timeout computed to be: 1000 > test 2 > Start 2: dear-reader-the-next-test-takes-80-seconds > > 2: Test command: /bin/true > 2: Test timeout computed to be: 1000 > test 3 > Start 3: test-device > > 3: Test command: /<>/obj-x86_64-linux-gnu/tests/test-device > 3: Test timeout computed to be: 1000 > 1: Running main() from gmock_main.cc > 1: [==] Running 4 tests from 1 test suite. > 1: [--] Global test environment set-up. > 1: [--] 4 tests from NotifyFixture > 1: [ RUN ] NotifyFixture.HelloWorld > 1: DBus daemon: > unix:abstract=/tmp/dbus-oKhHvWeLED,guid=b0f46843047fef16a54131de62d24f3d > 1/3 Test #2: dear-reader-the-next-test-takes-80-seconds ... Passed0.01 > sec > 1: DBusMock: Started with PID: 4156436 > 3: Running main() from gmock_main.cc > 3: [==] Running 9 tests from 1 test suite. > 3: [--] Global test environment set-up. > 3: [--] 9 tests from DeviceTest > 3: [ RUN ] DeviceTest.GObjectNew > 3: [ OK ] DeviceTest.GObjectNew (0 ms) > 3: [ RUN ] DeviceTest.Properties > 3: [ OK ] DeviceTest.Properties (0 ms) > 3: [ RUN ] DeviceTest.New > 3: [ OK ] DeviceTest.New (0 ms) > 3: [ RUN ] DeviceTest.NewFromVariant > 3: [ OK ] DeviceTest.NewFromVariant (0 ms) > 3: [ RUN ] DeviceTest.BadAccessors > 3: [ OK ] DeviceTest.BadAccessors (0 ms) > 3: [ RUN ] DeviceTest.IconNames > 3: [ OK ] DeviceTest.IconNames (0 ms) > 3: [ RUN ] DeviceTest.Labels > 3: > 3: (process:4156429): GLib-GObject-WARNING **: 05:40:13.605: invalid cast > from 'GCancellable' to 'IndicatorPowerDevice' > 3: [ OK ] DeviceTest.Labels (4 ms) > 3: [ RUN ] DeviceTest.Inestimable___this_takes_80_seconds > 1: DBusMock: Shutting down > 1: DBus daemon: Shutdown > 1: [ OK ] NotifyFixture.HelloWorld (5091 ms) > 1: [ RUN ] NotifyFixture.PercentageToLevel > 1: DBus daemon: > unix:abstract=/tmp/dbus-HFROzDifJr,guid=46ce16859acc90bafffbef4d62d24f42 > 1: DBusMock-1: Started with PID: 4156445 > 1: > 1: (process:4156427): GLib-GIO-CRITICAL **: 05:40:18.669: Error while sending > AddMatch() message: The connection is closed > 1: > 1: (process:4156427): GLib-GIO-CRITICAL **: 05:40:18.669: Error while sending > AddMatch() message: The connection is closed > 1: > 1: (process:4156427): libdbustest-CRITICAL **: 05:40:18.669: Unable to build > proxy to DBusMock: The connection is closed > 1: DBusMock-1: Shutting down > 1: DBus daemon: Shutdown > 1: [ OK ] NotifyFixture.PercentageToLevel (5014 ms) > 1: [ RUN ] NotifyFixture.LevelsDuringBatteryDrain > 1: DBus daemon: > unix:abstract=/tmp/dbus-QXXGMf2bJc,guid=3fc18470e277a409cf05c80162d24f47 > 1: DBusMock-2: Started with PID: 4156454 > 1: > 1: (process:4156427): GLib-GIO-CRITICAL **: 05:40:23.685: Error while sending > AddMatch() message: The connection is closed > 1: > 1: (process:4156427): GLib-GIO-CRITICAL **: 05:40:23.685: Error while sending > AddMatch() message: The connection is closed > 1: > 1: (process:4156427): libdbustest-CRITICAL **: 05:40:23.685: Unable to
Bug#1011716: marked as done (libbluray: FTBFS: [javac] /<>/src/libbluray/bdj/java-j2se/java/io/BDFileSystemImpl.java:21: error: BDFileSystemImpl is not abstract and does not override
Your message dated Sun, 02 Oct 2022 11:17:08 + with message-id and subject line Bug#1011716: fixed in libbluray 1:1.2.1-4+deb11u2 has caused the Debian Bug report #1011716, regarding libbluray: FTBFS: [javac] /<>/src/libbluray/bdj/java-j2se/java/io/BDFileSystemImpl.java:21: error: BDFileSystemImpl is not abstract and does not override abstract method isInvalid(File) in FileSystem 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.) -- 1011716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbluray Version: 1:1.3.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > rm -rf doc/doxygen > SRCDIR='.' PROJECT='libbluray' DOCDIR='doc/doxygen' VERSION='1.3.1' > PERL_PATH='/usr/bin/perl' HAVE_DOT='NO' GENERATE_MAN='NO' GENERATE_RTF='NO' > GENERATE_XML='NO' GENERATE_HTMLHELP='NO' GENERATE_CHI='NO' > GENERATE_HTML='YES' GENERATE_LATEX='NO' /usr/bin/doxygen ./doc/doxygen-config > warning: Tag 'TCL_SUBST' at line 237 of file './doc/doxygen-config' has > become obsolete. > To avoid this warning please remove this line from your > configuration file or upgrade it using "doxygen -u" > warning: Tag 'COLS_IN_ALPHA_INDEX' at line 1055 of file > './doc/doxygen-config' has become obsolete. > To avoid this warning please remove this line from your > configuration file or upgrade it using "doxygen -u" > warning: Tag 'PERL_PATH' at line 2120 of file './doc/doxygen-config' has > become obsolete. > To avoid this warning please remove this line from your > configuration file or upgrade it using "doxygen -u" > warning: Tag 'MSCGEN_PATH' at line 2142 of file './doc/doxygen-config' has > become obsolete. > To avoid this warning please remove this line from your > configuration file or upgrade it using "doxygen -u" > warning: doxygen no longer ships with the FreeSans font. > You may want to clear or change DOT_FONTNAME. > Otherwise you run the risk that the wrong font is being used for dot > generated graphs. > /<>/src/libbluray/bluray.h:810: warning: Compound BD_EVENT is > not documented. > /<>/src/libbluray/bluray.h:69: warning: Compound > BLURAY_DISC_INFO is not documented. > /<>/src/libbluray/bluray.h:59: warning: Compound BLURAY_TITLE is > not documented. > /<>/src/libbluray/bluray.h:258: warning: Compound bd_chapter is > not documented. > /<>/src/libbluray/bluray.h:235: warning: Compound bd_clip is not > documented. > /<>/src/libbluray/bluray.h:266: warning: Compound bd_mark is not > documented. > /<>/src/libbluray/bluray.h:294: warning: Compound > bd_sound_effect is not documented. > /<>/src/libbluray/bluray.h:224: warning: Compound bd_stream_info > is not documented. > /<>/src/libbluray/bluray.h:275: warning: Compound bd_title_info > is not documented. > /<>/src/libbluray/bluray.h:51: warning: Member > BD_AACS_CORRUPTED_DISC (macro definition) of file bluray.h is not documented. > /<>/src/libbluray/bluray.h:52: warning: Member BD_AACS_NO_CONFIG > (macro definition) of file bluray.h is not documented. > /<>/src/libbluray/bluray.h:53: warning: Member BD_AACS_NO_PK > (macro definition) of file bluray.h is not documented. > /<>/src/libbluray/bluray.h:54: warning: Member BD_AACS_NO_CERT > (macro definition) of file bluray.h is not documented. > /<>/src/libbluray/bluray.h:55: warning: Member > BD_AACS_CERT_REVOKED (macro definition) of file bluray.h is not documented. > /<>/src/libbluray/bluray.h:56: warning: Member > BD_AACS_MMC_FAILED (macro definition) of file bluray.h is not documented. > /<>/src/libbluray/bluray.h:601: warning: Member > BLURAY_PG_TEXTST_STREAM (macro definition) of file bluray.h is not documented. > /<>/src/libbluray/bluray.h:816: warning: Member BD_ERROR_HDMV > (macro definition) of file bluray.h is not documented. > /<>/src/libbluray/bluray.h:817: warning: Member BD_ERROR_BDJ > (macro definition) of file bluray.h is not documented. > /<>/src/libbluray/bluray.h:820: warning: Member BD_ERROR_AACS > (macro definition) of file bluray.h is not documented. > /<>/src/libbluray/bluray.h:821: warning: Member BD_ERROR_BDPLUS > (macro definition) of file bluray.h is not documented. > /<>/src/libbluray/bluray.h:824: warning: Member > BLURAY_TITLE_FIRST_PLAY (macro definition) of file bluray.h is not documented. >
Bug#1020192: cycle-quotes: FTBFS: make: *** [debian/rules:4: build] Error 25
Lucas Nussbaum writes: > Source: cycle-quotes > Version: 0.1-4 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220917 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > this seems unrelated to native compilation. It probably needs an upstream fix for emacs 28. Unfortunately upstream seems dead / static.
Bug#1020143: yasnippet: FTBFS: make[1]: *** [debian/rules:7: override_dh_auto_build] Error 255
Lucas Nussbaum writes: > Source: yasnippet > Version: 0.14.0+git20200603.5cbdbf0d-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220917 ftbfs-bookworm > This seems unrelated to native compilation. At a guess, it is because emacs now includes a new enough org-mode to trigger the previous bug that caused someone to add a Build-Conflicts with elpa-org.
Bug#1020197: marked as done (key-chord-el: FTBFS: make: *** [debian/rules:7: binary] Error 25)
Your message dated Sun, 02 Oct 2022 11:05:07 +
with message-id
and subject line Bug#1020197: fixed in key-chord-el 0.6-6
has caused the Debian Bug report #1020197,
regarding key-chord-el: FTBFS: make: *** [debian/rules:7: binary] 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.)
--
1020197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: key-chord-el
Version: 0.6-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules binary
> dh binary --with elpa
>dh_testroot
>dh_prep
>dh_auto_install --destdir=debian/elpa-key-chord/
>dh_elpa
> dh_elpa: error: emacs -batch -Q -l package --eval (add-to-list
> 'package-directory-list "/usr/share/emacs/site-lisp/elpa") --eval
> (add-to-list 'package-directory-list "/usr/share/emacs/site-lisp/elpa-src")
> -f package-initialize -l dh-elpa.el -f dhelpa-batch-install-file
> debian/elpa-key-chord//usr/share/emacs/site-lisp/elpa-src ./key-chord.el
> /<>/debian/.debhelper/elpa 1611574558 returned exit code 255
> Debugger entered--Lisp error: (error "Invalid version syntax: ‘0.6
> (2012-10-23)’")
> error("Invalid version syntax: `%s'" "0.6 (2012-10-23)")
> version-to-list("0.6 (2012-10-23)")
> package-strip-rcs-id("0.6 (2012-10-23)")
> (or (package-strip-rcs-id (lm-header "package-version"))
> (package-strip-rcs-id (lm-header "version")) (dhelpa-getenv-version))
> (let* ((requires-str (lm-header "package-requires")) (pkg-version (or
> (package-strip-rcs-id (lm-header "package-version")) (package-strip-rcs-id
> (lm-header "version")) (dhelpa-getenv-version))) (homepage (lm-homepage)))
> (if pkg-version nil (error "Package lacks a \"Version\" or
> \"Package-Version\"\nhea...")) (package-desc-from-define file-name
> pkg-version desc (if requires-str (package--prepare-dependencies
> (package-read-from-string requires-str))) :kind 'single :url homepage))
> (let ((file-name (match-string-no-properties 1)) (desc
> (match-string-no-properties 2)) (start (line-beginning-position))) (if
> (search-forward (concat ";;; " file-name ".el ends here")) nil (error
> "Package lacks a terminating comment")) (forward-line) (narrow-to-region
> start (point)) (require 'lisp-mnt) (let* ((requires-str (lm-header
> "package-requires")) (pkg-version (or (package-strip-rcs-id (lm-header
> "package-version")) (package-strip-rcs-id (lm-header "version"))
> (dhelpa-getenv-version))) (homepage (lm-homepage))) (if pkg-version nil
> (error "Package lacks a \"Version\" or \"Package-Version\"\nhea..."))
> (package-desc-from-define file-name pkg-version desc (if requires-str
> (package--prepare-dependencies (package-read-from-string requires-str)))
> :kind 'single :url homepage)))
> dhelpa-buffer-info()
> (if (derived-mode-p 'tar-mode) (package-tar-file-info) (dhelpa-buffer-info))
> (let ((pkg-desc (if (derived-mode-p 'tar-mode) (package-tar-file-info)
> (dhelpa-buffer-info (dhelpa-unpack pkg-desc destdir epoch-time) pkg-desc)
> dhelpa-install-from-buffer("/<>/debian..." "1611574558")
> (let ((desc (dhelpa-install-from-buffer (expand-file-name dest)
> epoch-time))) (if desc-dir (progn (dhelpa-write-desc desc desc-dir
> (progn (insert-file-contents-literally el-file) (if (string-match
> "\\.tar\\'" el-file) (progn (tar-mode))) (let ((desc
> (dhelpa-install-from-buffer (expand-file-name dest) epoch-time))) (if
> desc-dir (progn (dhelpa-write-desc desc desc-dir)
> (unwind-protect (progn (insert-file-contents-literally el-file) (if
> (string-match "\\.tar\\'" el-file) (progn (tar-mode))) (let ((desc
> (dhelpa-install-from-buffer (expand-file-name dest) epoch-time))) (if
> desc-dir (progn (dhelpa-write-desc desc desc-dir) (and (buffer-name
> temp-buffer) (kill-buffer temp-buffer)))
> (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn
> (insert-file-contents-literally el-file) (if (string-match "\\.tar\\'"
> el-file) (progn (tar-mode))) (let ((desc (dhelpa-install-from-buffer
> (expand-file-name dest) epoch-time))) (if desc-dir (progn (dhelpa-write-desc
> desc desc-dir) (and (buffer-name temp-buffer) (kill-buffer temp-buffer
> (let ((temp-buffer (generate-new-buffer " *temp*" t))) (save-current-buffer
> (set-buffer temp-buffer) (unwind-protect (progn
> (insert-file-contents-literally el-file)
Bug#975490: u-boot-sunxi: A64-Olinuxino-eMMC boot stuck at "Starting kernel ..."
Hi, I can troubleshoot once I'm back home in ~10 days, I do have that board at home. I'm pretty sure it worked fine last time I tried. Best, Philip signature.asc Description: PGP signature
Bug#1019865: Hangs and goes to 100% CPU usage on compose
On Fri, 30 Sep 2022 20:53:22 +0200 Tim Dengel wrote: > I am observing the same behaviour, but only when I click the request > read receipt option. Do you guys maybe have the option to always > request a read receipt turned on? > > Yes, if I turn off this option problem is gone. (If I turned on again, the problem is appear.) -- pp
Bug#1020987: barrier FTBFS with nocheck: missing gtest
Hi Helmut, all, On 30-09-2022 06:27, Helmut Grohne wrote: Justification: last RT meeting, elbrus and ginggs said nocheck FTBFS should be serious To be fair, we (at least I) also said, after the bookworm release. barrier fails to build from source when enabling the nocheck build profile. On reproducible builds [1] it also fails with !nocheck on amd64 and i386 since end 2021 on sid and bookworm. The cmake stuff fails hard when it misses gtest, which happens to be annotated . There probably is some flag involved for actually removing this requirement. Failing that, the annotation on gtest should be reverted. Maybe worth checking if the errors are similar or different. Anyways, it appears the build might be worth checking. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: bts
Processing commands for cont...@bugs.debian.org:
> close 1019891 1.26.1-2
Bug #1019891 {Done: Daniel Baumann } [mycli]
mycli: Always crashes at runtime because the module 'sqlglot' is missing
Marked as fixed in versions mycli/1.26.1-2.
Bug #1019891 {Done: Daniel Baumann } [mycli]
mycli: Always crashes at runtime because the module 'sqlglot' is missing
Bug 1019891 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1019891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1020193: pcre2el: FTBFS: make: *** [debian/rules:4: binary] Error 25
Lucas Nussbaum writes: > Source: pcre2el > Version: 1.8-4 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220917 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > This bug seems unrelated to native compilation, consider checking for an emacs 28 related fix upstream. d
Processed: tagging 1020195
Processing commands for cont...@bugs.debian.org: > tags 1020195 - bookworm Bug #1020195 [src:elisp-bug-hunter] elisp-bug-hunter: FTBFS: make: *** [debian/rules:4: binary] Error 25 Removed tag(s) bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1020195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020195: elisp-bug-hunter: FTBFS: make: *** [debian/rules:4: binary] Error 25
Lucas Nussbaum writes: > Source: elisp-bug-hunter > Version: 1.3.1+repack-5 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220917 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. This bug seems unrelated to native compilation, probably an API change in emacs28. Consider checking for an upstream fix... d
Processed: tagging 1020029
Processing commands for cont...@bugs.debian.org: > tags 1020029 - bookworm Bug #1020029 [src:emacs-deferred] emacs-deferred: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Removed tag(s) bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1020029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020029: emacs-deferred: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Lucas Nussbaum writes: > Source: emacs-deferred > Version: 0.5.1-4 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220917 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > This bug seems unrelated to native compilation. Most likely some API change in emacs 28. Perhaps check for a fix upstream? d
Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org: > merge 1020639 1021076 Bug #1020639 [pdfarranger] pdfarranger: libqpdf 11 require pdfarranger 1.9.1 Bug #1021076 [pdfarranger] pdfarranger: version 1.8.2 incompatible with pikepdf 6 - please upgrade Added tag(s) upstream. Merged 1020639 1021076 > severity 1020639 grave Bug #1020639 [pdfarranger] pdfarranger: libqpdf 11 require pdfarranger 1.9.1 Bug #1021076 [pdfarranger] pdfarranger: version 1.8.2 incompatible with pikepdf 6 - please upgrade Severity set to 'grave' from 'important' Severity set to 'grave' from 'important' > Raising severity has PDF Arranger is now unusable Unknown command or malformed arguments to command. > End of message, stopping processing here. Please contact me if you need assistance. -- 1020639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020639 1021076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017216: marked as done (gcc-12-cross: FTBFS: unsatisfiable build-dependencies: libc6-dev-amd64-cross (= 2.33-1cross1), libc6-dev-amd64-cross (= 2.33-1cross1), libc6-dev-amd64-cross (>= 2.32))
Your message dated Sun, 2 Oct 2022 11:14:47 +0200 with message-id and subject line fixed has caused the Debian Bug report #1017216, regarding gcc-12-cross: FTBFS: unsatisfiable build-dependencies: libc6-dev-amd64-cross (= 2.33-1cross1), libc6-dev-amd64-cross (= 2.33-1cross1), libc6-dev-amd64-cross (>= 2.32) 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.) -- 1017216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-12-cross Version: 7 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: gcc-12-source (>= 12.1.0-7~), gcc-12-base (>= > 12.1.0-7~), binutils-multiarch (>= 2.37-5), autoconf2.69, bison (>= 1:2.3), > chrpath, debhelper (>= 9), dpkg-dev (>= 1.14.15), flex, gawk, gettext, gperf > (>= 3.0.1), binutils-x86-64-linux-gnu (>= 2.37-5), binutils-s390x-linux-gnu > (>= 2.37-5), binutils-powerpc64le-linux-gnu (>= 2.37-5), > binutils-aarch64-linux-gnu (>= 2.37-5), binutils-arm-linux-gnueabihf (>= > 2.37-5), binutils-arm-linux-gnueabi (>= 2.37-5), binutils-i686-linux-gnu (>= > 2.37-5), libc6-dev-amd64-cross (>= 2.32), libc6-dev-s390x-cross (>= 2.32), > libc6-dev-ppc64el-cross (>= 2.32), libc6-dev-arm64-cross (>= 2.32), > libc6-dev-armhf-cross (>= 2.32), libc6-dev-armel-cross (>= 2.32), > libc6-dev-i386-cross (>= 2.32), libc6-dev-i386-amd64-cross, > libc6-dev-x32-amd64-cross, libc6-dev-amd64-i386-cross, > libc6-dev-x32-i386-cross, libc6-dev-s390-s390x-cross, > linux-libc-dev-amd64-cross, linux-libc-dev-s390x-cross, > linux-libc-dev-ppc64el-cross, linux-libc-dev-arm64-cross, > linux-libc-dev-armhf-cross, linux-libc-dev-armel-cross, > linux-libc-dev-i386-cross, libisl-dev (>= 0.22.1-1~), libmpc-dev, libmpfr-dev > (>= 2.3.0), libtool, lsb-release, m4, make (>= 3.81), dwz, pkg-config, > libgc-dev, patchutils, procps, quilt, coreutils (>= 2.26) | realpath (>= > 1.9.12), sharutils, texinfo (>= 4.3), g++-12, gccgo-12, gdc-12, gm2-12, > gnat-12, xz-utils, zlib1g-dev, libzstd-dev, python3, time, build-essential, > fakeroot > Merged Build-Conflicts: gcc-multilib, libc6-i386, libc6-x32 > Filtered Build-Depends: gcc-12-source (>= 12.1.0-7~), gcc-12-base (>= > 12.1.0-7~), binutils-multiarch (>= 2.37-5), autoconf2.69, bison (>= 1:2.3), > chrpath, debhelper (>= 9), dpkg-dev (>= 1.14.15), flex, gawk, gettext, gperf > (>= 3.0.1), binutils-x86-64-linux-gnu (>= 2.37-5), binutils-s390x-linux-gnu > (>= 2.37-5), binutils-powerpc64le-linux-gnu (>= 2.37-5), > binutils-aarch64-linux-gnu (>= 2.37-5), binutils-arm-linux-gnueabihf (>= > 2.37-5), binutils-arm-linux-gnueabi (>= 2.37-5), binutils-i686-linux-gnu (>= > 2.37-5), libc6-dev-amd64-cross (>= 2.32), libc6-dev-s390x-cross (>= 2.32), > libc6-dev-ppc64el-cross (>= 2.32), libc6-dev-arm64-cross (>= 2.32), > libc6-dev-armhf-cross (>= 2.32), libc6-dev-armel-cross (>= 2.32), > libc6-dev-i386-cross (>= 2.32), libc6-dev-i386-amd64-cross, > libc6-dev-x32-amd64-cross, libc6-dev-amd64-i386-cross, > libc6-dev-x32-i386-cross, libc6-dev-s390-s390x-cross, > linux-libc-dev-amd64-cross, linux-libc-dev-s390x-cross, > linux-libc-dev-ppc64el-cross, linux-libc-dev-arm64-cross, > linux-libc-dev-armhf-cross, linux-libc-dev-armel-cross, > linux-libc-dev-i386-cross, libisl-dev (>= 0.22.1-1~), libmpc-dev, libmpfr-dev > (>= 2.3.0), libtool, lsb-release, m4, make (>= 3.81), dwz, pkg-config, > libgc-dev, patchutils, procps, quilt, coreutils (>= 2.26), sharutils, texinfo > (>= 4.3), g++-12, gccgo-12, gdc-12, gm2-12, gnat-12, xz-utils, zlib1g-dev, > libzstd-dev, python3, time, build-essential, fakeroot > Filtered Build-Conflicts: gcc-multilib, libc6-i386, libc6-x32 > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [945 B] > Get:5 copy:/<>/apt_archive ./ Packages [885 B] > Fetched 2793 B in 0s (253 kB/s) > Reading package lists... > Reading
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 1014750 experimental Bug #1014750 [src:xfce4-notes-plugin] xfce4-notes-plugin: fails to build twice in a row Added tag(s) experimental. > End of message, stopping processing here. Please contact me if you need assistance. -- 1014750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1021062: libc6: nonexistent locale crashes programs (for example, bash, gdb, ...)
Processing control commands: > clone 1021062 -1 Bug #1021062 [libreadline8] bash: non existent locale crashes bash Bug 1021062 cloned as bug 1021109 > reassign -1 bash Bug #1021109 [libreadline8] bash: non existent locale crashes bash Bug reassigned from package 'libreadline8' to 'bash'. No longer marked as found in versions libreadline8/8.2-1. Ignoring request to alter fixed versions of bug #1021109 to the same values previously set > found -1 bash/5.2-1 Bug #1021109 [bash] bash: non existent locale crashes bash Marked as found in versions bash/5.2-1. -- 1021062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021062 1021109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021062: libc6: nonexistent locale crashes programs (for example, bash, gdb, ...)
control: clone 1021062 -1 control: reassign -1 bash control: found -1 bash/5.2-1 Hi, On 2022-10-02 07:27, Kan-Ru Chen wrote: > reassign 1021062 libreadline8 > found 1021062 libreadline8/8.2-1 > thanks > > On Sun, Oct 2, 2022, at 1:56 AM, Aurelien Jarno wrote: > > control: reassign -1 bash > > control: found -1 bash/5.2-1 > > > > Hi, > > > > On 2022-10-01 21:01, Kan-Ru Chen wrote: > >> Package: libc6 > >> Version: 2.35-1 > >> Severity: grave > >> Justification: renders package unusable > >> X-Debbugs-Cc: kos...@debian.org > >> > >> Dear maintainer, > >> > >> After upgrading to libc6 2.35-1 (or 2.36-1 in experimental), nonexistent > >> locale setting > >> starts to crash the system. > >> > >> This is dangerous because a remote system might not always have the same > >> locale installed. > >> An auto update will soft-brick the system unless the sysadmin knows to set > >> their LC_ALL=POSIX > >> before attempting to ssh. > >> > >> Steps to reproduce: > >> > >> >From a clean installed Debian sid, upgrade to libc6 2.35-1. > >> Only install C locale and en_US.UTF-8. > >> > >> $ LC_ALL=ja_JP.UTF-8 bash > >> bash: warning: setlocale: LC_ALL: cannot change locale (ja_JP.UTF-8) > >> Segmentation fault (core dumped) > >> > >> $ LC_ALL=ja_JP.UTF-8 gdb bash > >> > >> Fatal signal: Segmentation fault > >> - Backtrace - > >> 0x55ed3e1e8dcf ??? > >> 0x55ed3e2df312 ??? > >> 0x55ed3e2df488 ??? > >> 0x7f0b4a39ba9f ??? > >> 0x7f0b4b412204 _rl_init_locale > >> 0x7f0b4b4122f1 _rl_init_eightbit > >> 0x7f0b4b3f10f2 rl_initialize > >> ... snip ... > > > > FYI, this is the full backtrace with the debug packages installed: > > > > #0 0x7f8079d0ccc7 in __GI_kill () at > > ../sysdeps/unix/syscall-template.S:120 > > #1 0x559be26519c9 in termsig_handler (sig=11) at .././sig.c:625 > > #2 0x559be2651c21 in termsig_handler (sig=) at > > .././sig.c:492 > > #3 termsig_sighandler (sig=) at .././sig.c:547 > > #4 > > #5 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 > > #6 0x559be26b8682 in _rl_init_locale () at > > ../../.././lib/readline/nls.c:150 > > #7 0x559be26b8772 in _rl_init_eightbit () at > > ../../.././lib/readline/nls.c:227 > > #8 0x559be269766e in readline_initialize_everything () at > > ../../.././lib/readline/readline.c:1292 > > #9 rl_initialize () at ../../.././lib/readline/readline.c:1183 > > #10 0x559be2662b05 in initialize_readline () at .././bashline.c:522 > > #11 0x559be26040a5 in yy_readline_get () at > > /usr/local/src/chet/src/bash/src/parse.y:1514 > > #12 0x559be2606aa1 in yy_getc () at > > /usr/local/src/chet/src/bash/src/parse.y:1462 > > #13 shell_getc (remove_quoted_newline=remove_quoted_newline@entry=1) at > > /usr/local/src/chet/src/bash/src/parse.y:2393 > > #14 0x559be2608eeb in read_token (command=0) at > > /usr/local/src/chet/src/bash/src/parse.y:3400 > > #15 0x559be260d05b in yylex () at > > /usr/local/src/chet/src/bash/src/parse.y:2890 > > #16 yyparse () at ./build-bash/y.tab.c:1854 > > #17 0x559be2603586 in parse_command () at .././eval.c:348 > > #18 0x559be2603714 in read_command () at .././eval.c:392 > > #19 0x559be26038c6 in reader_loop () at .././eval.c:139 > > #20 0x559be26023b5 in main (argc=1, argv=0x7ffe3da22078, > > env=0x7ffe3da22088) at .././shell.c:833 > > > > So the problem is that _rl_init_locale (from bash) calls strlen(NULL). > > > >> Downgrade to 2.34-8 seems also don't fix the issue, probably some locale > >> state was invalidated when upgrading. > > > > This is because you upgraded other packages than glibc (here bash), and the > > bug > > is not in glibc. Downgrading bash fixes the issue. Reassigning the bug. > > Thanks! > > That explains why not all programs crash like this. The common library they > used is > libreadline and I confirmed downgrade libreadline8 to 8.2~rc2-2 fixed the > issue. > Reassigning to libreadline8. I did the test of downgrading bash yesterday (i.e. without downgrading libreadline8), and it fixes the issue you reported with bash. It appears that bash has an embedded copy of readline, hence the issue with both. I am therefore cloning the bug to bash. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Processed: retitle 1019974 to uim: FTBFS on armel/armhf: [Makefile:871: installed-modules.scm] Segmentation fault
Processing commands for cont...@bugs.debian.org: > retitle 1019974 uim: FTBFS on armel/armhf: [Makefile:871: > installed-modules.scm] Segmentation fault Bug #1019974 [src:uim] uim: FTBFS on armhf: [Makefile:871: installed-modules.scm] Segmentation fault Changed Bug title to 'uim: FTBFS on armel/armhf: [Makefile:871: installed-modules.scm] Segmentation fault' from 'uim: FTBFS on armhf: [Makefile:871: installed-modules.scm] Segmentation fault'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1019974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
