date:20231108

Processed: retitle 1054814 to criu: FTBFS: bad install directory or PYTHONPATH, tagging 1054814

2023-11-08 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> retitle 1054814 criu: FTBFS: bad install directory or PYTHONPATH
Bug #1054814 [src:criu] criu: FTBFS: make[2]: git: No such file or directory
Changed Bug title to 'criu: FTBFS: bad install directory or PYTHONPATH' from 
'criu: FTBFS: make[2]: git: No such file or directory'.
> tags 1054814 + confirmed
Bug #1054814 [src:criu] criu: FTBFS: bad install directory or PYTHONPATH
Added tag(s) confirmed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1054814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1054853: marked as done (node-postcss-loader: update to 7.3.3 broke the package)

2023-11-08 Thread Debian Bug Tracking System

Your message dated Thu, 09 Nov 2023 06:04:04 +
with message-id 
and subject line Bug#1054853: fixed in node-postcss-loader 7.3.3+really+7.0.2-1
has caused the Debian Bug report #1054853,
regarding node-postcss-loader: update to 7.3.3 broke the package
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.)


-- 
1054853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-katex
Version: 0.16.4+~cs6.1.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> Link ./node_modules/type-fest -> /usr/share/nodejs/type-fest
> Link ./node_modules/@types/babel__core -> /usr/share/nodejs/@types/babel__core
> Link ./node_modules/@types/jest -> /usr/share/nodejs/@types/jest
> Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node
> Link ./node_modules/@types/require-from-string -> 
> /usr/share/nodejs/@types/require-from-string
> Link node_modules/babel-plugin-preval -> ../babel-plugin-preval
> Link node_modules/babel-plugin-version-inline -> 
> ../babel-plugin-version-inline
> Link node_modules/@types/babel-plugin-macros -> 
> ../../debian/build_modules/@types/babel-plugin-macros
> Link node_modules/@types/babel-plugin-tester -> 
> ../../debian/build_modules/@types/babel-plugin-tester
> Link node_modules/babel-plugin-macros -> 
> ../debian/build_modules/babel-plugin-macros
> Link node_modules/babel-plugin-transform-react-remove-prop-types -> 
> ../debian/build_modules/babel-plugin-transform-react-remove-prop-types
> Link node_modules/kcd-scripts -> ../debian/build_modules/kcd-scripts
>dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/babel-plugin-version-inline/build
>   cd ./babel-plugin-version-inline && sh -ex 
> ../debian/nodejs/babel-plugin-version-inline/build
> + babeljs src -d lib
> Successfully compiled 1 file with Babel (459ms).
> Found debian/nodejs/babel-plugin-preval/build
>   cd ./babel-plugin-preval && sh -ex 
> ../debian/nodejs/babel-plugin-preval/build
> + mkdir -p node_modules
> + cp -a ../debian/build_modules/kcd-scripts node_modules/
> + ./node_modules/kcd-scripts/dist/index.js build
> Successfully compiled 4 files with Babel (666ms).
> Generating TypeScript definitions
> TypeScript definitions generated
> Found debian/nodejs/./build
>   cd ./. && sh -ex debian/nodejs/./build
> + rollup -c
> [36m
> [1m./katex.js[22m → [1mdist/katex.mjs[22m...[39m
> [32mcreated [1mdist/katex.mjs[22m in [1m4.5s[22m[39m
> [36m
> [1m./contrib/auto-render/auto-render.js[22m → 
> [1mdist/contrib/auto-render.mjs[22m...[39m
> [32mcreated [1mdist/contrib/auto-render.mjs[22m in [1m62ms[22m[39m
> [36m
> [1m./contrib/mhchem/mhchem.js[22m → [1mdist/contrib/mhchem.mjs[22m...[39m
> [32mcreated [1mdist/contrib/mhchem.mjs[22m in [1m336ms[22m[39m
> [36m
> [1m./contrib/copy-tex/copy-tex.js[22m → 
> [1mdist/contrib/copy-tex.mjs[22m...[39m
> [32mcreated [1mdist/contrib/copy-tex.mjs[22m in [1m37ms[22m[39m
> [36m
> [1m./contrib/mathtex-script-type/mathtex-script-type.js[22m → 
> [1mdist/contrib/mathtex-script-type.mjs[22m...[39m
> [32mcreated [1mdist/contrib/mathtex-script-type.mjs[22m in 
> [1m13ms[22m[39m
> [36m
> [1m./contrib/render-a11y-string/render-a11y-string.js[22m → 
> [1mdist/contrib/render-a11y-string.mjs[22m...[39m
> [32mcreated [1mdist/contrib/render-a11y-string.mjs[22m in 
> [1m68ms[22m[39m
> + webpack
> assets by status 271 KiB [1m[32m[cached][39m[22m 1 asset
> orphan modules 623 KiB [1m[33m[orphan][39m[22m 87 modules
> runtime modules 416 bytes 2 modules
> cacheable modules 624 KiB
>   [1m./katex.webpack.js + 86 modules[39m[22m 624 KiB 
> [1m[33m[built][39m[22m [1m[33m[code generated][39m[22m
>   [1m./src/katex.less[39m[22m 39 bytes [1m[33m[built][39m[22m 
> [1m[33m[code generated][39m[22m [1m[31m[1 error][39m[22m
> 
> [1m[31mERROR[39m[22m in [1m./src/katex.less[39m[22m 
> (./src/katex.less.webpack[javascript/auto]!=!../../../usr/share/nodejs/css-loader/dist/cjs.js??ruleSet[1].rules[2].use[1]!../../../usr/share/nodejs/postcss-loader/dist/cjs.js??ruleSet[1].rules[2].use[2]!../../../usr/share/nodejs/less-loader/dist/cjs.js??ruleSet[1].rules[2].use[3]!./src/katex.less)
> [1mModule build

Processed: Bug#1054853 marked as pending in node-postcss-loader

2023-11-08 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #1054853 [node-postcss-loader] node-postcss-loader: update to 7.3.3 broke 
the package
Ignoring request to alter tags of bug #1054853 to the same tags previously set

-- 
1054853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#1054853 marked as pending in node-postcss-loader

2023-11-08 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #1054853 [node-postcss-loader] node-postcss-loader: update to 7.3.3 broke 
the package
Added tag(s) pending.

-- 
1054853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1054853: marked as pending in node-postcss-loader

2023-11-08 Thread Yadd

Control: tag -1 pending

Hello,

Bug #1054853 in node-postcss-loader reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/js-team/node-postcss-loader/-/commit/cc70989581f22e6ada291473a9992aede786348e


Revert update to 7.3.3 (Closes: #1054853)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1054853

Bug#1054853: marked as pending in node-postcss-loader

2023-11-08 Thread Yadd

Control: tag -1 pending

Hello,

Bug #1054853 in node-postcss-loader reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/js-team/node-postcss-loader/-/commit/cc70989581f22e6ada291473a9992aede786348e


Revert update to 7.3.3 (Closes: #1054853)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1054853

Bug#1055510: Best way to coordinate this fix

2023-11-08 Thread Helmut Grohne

Hi Francois,

On Wed, Nov 08, 2023 at 01:00:33PM -0800, Francois Marier wrote:
> If anybody would like to double-check (or test) the package I've prepared,
> it's in salsa right now.

Thank you. I suggest going via experimental first.
https://wiki.debian.org/UsrMerge recommends uploading to experimental
when moving files from / to /usr. This allows some qa already and in
particular dumat will have a second look at it. That look is fairly
limited at this time, because systemd conflicts with molly-guard now,
but I can locally make it pretend it would not and feed back the result
to you. Alternatively, Luca can perform another experimental upload of
systemd adding a version constraint to the conflict for molly-guard.
Does that extra detour make sense to you?

Helmut

Bug#1054689: therion: FTBFS: utest-proj.cxx:1:10: fatal error: catch2/catch.hpp: No such file or directory

2023-11-08 Thread Wookey

On 2023-11-08 20:10 +0100, Martin Budaj wrote:
> On Tue, Nov 7, 2023 at 4:25 PM Wookey  wrote:
> 
> > It looks like moving to catch3 and adding:
> > target_link_libraries(test PRIVATE Catch2::Catch2WithMain)
> > in the test targets should do the trick.
> >
> 
> Hi,
> 
> as we still need to maintain Catch2 v2 API compatibility to run CI tests
> and builds on older Ubuntu images, we can't simply migrate to v3.

Who is building 'latest' Therion on old Ubuntu? And are they getting
their sources from the Debian unstable package? Or from Upstream?

> For now, I'll just enable using the bundled Catch2 instead of v3 installed
> in the system.

That's not the right approach for the Debian package, and this bug is about the 
debian package.
Debian unstable has catch 3 in it. We should use it, not an old bundled catch2 
copy.

Upstream builds and Ubuntu builds can do something different if need
be but that's not a good reason for the Debian package not to
DTRT. And in general I'd expect current Ubuntu to have catch3 too so
using the system version will be appropriate there too.

Wookey
-- 
Principal hats:  Debian, Wookware, ARM
http://wookware.org/

signature.asc
Description: PGP signature

Bug#1042697: marked as done (groonga: FTBFS with Sphinx 7.1, docutils 0.20: /usr/bin/install: cannot stat './html/_static/underscore.js': No such file or directory)

2023-11-08 Thread Debian Bug Tracking System

Your message dated Thu, 9 Nov 2023 09:53:18 +0900
with message-id <20231109095318.4ac41c0f@jet>
and subject line Re: Your mail
has caused the Debian Bug report #1042697,
regarding groonga: FTBFS with Sphinx 7.1, docutils 0.20: /usr/bin/install: 
cannot stat './html/_static/underscore.js': No such file or directory
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.)


-- 
1042697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: groonga
Version: 13.0.1+dfsg-1
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

groonga fails to build with Sphinx 7.1 and docutils 0.20, both of which
are currently available in experimental.

Relevant part (hopefully):
> make[8]: Entering directory '/<>/doc/locale/en'
> make[8]: Nothing to be done for 'install-exec-am'.
>  /bin/mkdir -p '/<>/debian/tmp/usr/share/doc/groonga/en'
>  /bin/mkdir -p 
> '/<>/debian/tmp/usr/share/doc/groonga/en/html/reference/commands'
>  /usr/bin/install -c -m 644  html/reference/commands/cache_limit.html 
> html/reference/commands/check.html html/reference/commands/clearlock.html 
> html/reference/commands/column_copy.html 
> html/reference/commands/column_create.html 
> html/reference/commands/column_list.html 
> html/reference/commands/column_remove.html 
> html/reference/commands/column_rename.html 
> html/reference/commands/config_delete.html 
> html/reference/commands/config_get.html 
> html/reference/commands/config_set.html 
> html/reference/commands/database_unmap.html 
> html/reference/commands/define_selector.html 
> html/reference/commands/defrag.html html/reference/commands/delete.html 
> html/reference/commands/dump.html 
> html/reference/commands/index_column_diff.html 
> html/reference/commands/io_flush.html html/reference/commands/load.html 
> html/reference/commands/lock_acquire.html 
> html/reference/commands/lock_clear.html 
> html/reference/commands/lock_release.html 
> html/reference/commands/log_level.html html/reference/commands/log_put.html 
> html/reference/commands/log_reopen.html 
> html/reference/commands/logical_count.html 
> html/reference/commands/logical_parameters.html 
> html/reference/commands/logical_range_filter.html 
> html/reference/commands/logical_select.html 
> html/reference/commands/logical_shard_list.html 
> html/reference/commands/logical_table_remove.html 
> html/reference/commands/normalize.html 
> html/reference/commands/normalizer_list.html 
> html/reference/commands/object_exist.html 
> html/reference/commands/object_inspect.html 
> html/reference/commands/object_list.html 
> html/reference/commands/object_remove.html 
> html/reference/commands/plugin_register.html 
> html/reference/commands/plugin_unregister.html 
> html/reference/commands/query_expand.html 
> '/<>/debian/tmp/usr/share/doc/groonga/en/html/reference/commands'
>  /bin/mkdir -p 
> '/<>/debian/tmp/usr/share/doc/groonga/en/html/development'
>  /usr/bin/install -c -m 644  html/development/travis-ci.html 
> '/<>/debian/tmp/usr/share/doc/groonga/en/html/development'
>  /bin/mkdir -p 
> '/<>/debian/tmp/usr/share/doc/groonga/en/html/_static/vendor/fontawesome/5.13.0/css'
>  /usr/bin/install -c -m 644  
> html/_static/vendor/fontawesome/5.13.0/css/all.min.css 
> '/<>/debian/tmp/usr/share/doc/groonga/en/html/_static/vendor/fontawesome/5.13.0/css'
>  /bin/mkdir -p 
> '/<>/debian/tmp/usr/share/doc/groonga/en/html/spec'
>  /usr/bin/install -c -m 644  html/spec/gqtp.html html/spec/search.html 
> '/<>/debian/tmp/usr/share/doc/groonga/en/html/spec'
>  /bin/mkdir -p 
> '/<>/debian/tmp/usr/share/doc/groonga/en/html/tutorial'
>  /usr/bin/install -c -m 644  html/tutorial/data.html 
> html/tutorial/drilldown.html html/tutorial/index.html 
> html/tutorial/introduction.html html/tutorial/lexicon.html 
> html/tutorial/match_columns.html html/tutorial/micro_blog.html 
> html/tutorial/network.html html/tutorial/patricia_trie.html 
> html/tutorial/query_expansion.html html/tutorial/search.html 
> '/<>/debian/tmp/usr/share/doc/groonga/en/html/tutorial'
>  /bin/mkdir -p 
> '/<>/debian/tmp/usr/share/doc/groonga/en/html/reference/normalizers'
>  /usr/bin/install -c -m 644  html/reference/normalizers/normalizer_auto.html 
> html/reference/normalizers/normalizer_nfkc100.html 
> html/reference/normalizers/normalizer_nfkc121.html 
> html/reference/normalizers/normalizer_nfkc130.html 
> html/reference/normalizers/normalizer_nfkc150.html 
> html/reference/normalizers/normalizer_nfkc51.html 
>

Bug#1055510: Best way to coordinate this fix

2023-11-08 Thread Simó Albert i Beltran





On Thu, Nov 9 2023 at 12:13:25 AM +01:00:00, Simó Albert i Beltran 
 wrote:
Please take a look at 
https://salsa.debian.org/debian/molly-guard/-/commit/c1120c0c3602955abe02d4d810985ad13d02cdba




Sorry, I meant 
https://salsa.debian.org/debian/molly-guard/-/commit/c1120c0c3602955abe02d4d810985ad13d02cdba#note_440065

Bug#1055510: Best way to coordinate this fix

2023-11-08 Thread Simó Albert i Beltran

Please take a look at 
https://salsa.debian.org/debian/molly-guard/-/commit/c1120c0c3602955abe02d4d810985ad13d02cdba

Bug#1055475: marked as done (tilix: FTBFS with ldc 1.35.0)

2023-11-08 Thread Debian Bug Tracking System

Your message dated Wed, 08 Nov 2023 22:35:06 +
with message-id 
and subject line Bug#1055475: fixed in tilix 1.9.6-1
has caused the Debian Bug report #1055475,
regarding tilix: FTBFS with ldc 1.35.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1055475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tilix
Version: 1.9.5-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=tilix=amd64=1.9.5-2%2Bb1=1699272176=0

FAILED: tilix.p/source_gx_tilix_prefeditor_prefdialog.d.o 
ldc2 -I=tilix.p -I=. -I=.. -I=../source -I=data -I/usr/include/d/gtkd-3/ 
-I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/x86_64-linux-gnu -I/usr/include/webp -I/usr/include/gio-unix-2.0 
-I/usr/include/cloudproviders -I/usr/include/atk-1.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/librsvg-2.0 -I/usr/include/vte-2.91 -I/usr/include/libsecret-1 
-enable-color -wi -O -g -release -wi -vcolumns -d-version=StdLoggerDisableTrace 
-makedeps=tilix.p/source_gx_tilix_prefeditor_prefdialog.d.o.deps 
-of=tilix.p/source_gx_tilix_prefeditor_prefdialog.d.o -c 
../source/gx/tilix/prefeditor/prefdialog.d
../source/gx/tilix/prefeditor/prefdialog.d(960,16): Error: unable to read 
module `xml`
../source/gx/tilix/prefeditor/prefdialog.d(960,16):Expected 'std/xml.d' 
or 'std/xml/package.d' in one of the following import paths:
import path[0] = tilix.p
import path[1] = .
import path[2] = ..
import path[3] = ../source
import path[4] = data
import path[5] = /usr/include/d/gtkd-3/
import path[6] = /usr/include/gtk-3.0
import path[7] = /usr/include/pango-1.0
import path[8] = /usr/include/glib-2.0
import path[9] = /usr/lib/x86_64-linux-gnu/glib-2.0/include
import path[10] = /usr/include/harfbuzz
import path[11] = /usr/include/freetype2
import path[12] = /usr/include/libpng16
import path[13] = /usr/include/libmount
import path[14] = /usr/include/blkid
import path[15] = /usr/include/fribidi
import path[16] = /usr/include/cairo
import path[17] = /usr/include/pixman-1
import path[18] = /usr/include/gdk-pixbuf-2.0
import path[19] = /usr/include/x86_64-linux-gnu
import path[20] = /usr/include/webp
import path[21] = /usr/include/gio-unix-2.0
import path[22] = /usr/include/cloudproviders
import path[23] = /usr/include/atk-1.0
import path[24] = /usr/include/at-spi2-atk/2.0
import path[25] = /usr/include/at-spi-2.0
import path[26] = /usr/include/dbus-1.0
import path[27] = /usr/lib/x86_64-linux-gnu/dbus-1.0/include
import path[28] = /usr/include/librsvg-2.0
import path[29] = /usr/include/vte-2.91
import path[30] = /usr/include/libsecret-1
import path[31] = /usr/lib/ldc/x86_64-linux-gnu/include/d
import path[32] = /usr/include/d

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: tilix
Source-Version: 1.9.6-1
Done: Matthias Klumpp 

We believe that the bug you reported is fixed in the latest version of
tilix, 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 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated tilix package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 08 Nov 2023 22:48:18 +0100
Source: tilix
Architecture: source
Version: 1.9.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Matthias Klumpp 
Closes: 940849 1055475
Changes:
 tilix (1.9.6-1) unstable; urgency=medium
 .
   * New upstream release: 1.9.6
 - Builds with recent D toolchain (Closes: #1055475, #940849)
   * Drop all patches: Applied upstream
   * Bump standards

Bug#1054546: marked as done (openssl: The engine interface seems to be broken.)

2023-11-08 Thread Debian Bug Tracking System

Your message dated Wed, 08 Nov 2023 21:21:39 +
with message-id 
and subject line Bug#1054546: fixed in openssl 3.0.12-2
has caused the Debian Bug report #1054546,
regarding openssl: The engine interface seems to be broken.
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.)


-- 
1054546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openssl
Version: 3.0.12-1
Severity: serious
Control: affects -1 + src:libp11
Control: forwarded -1 https://github.com/openssl/openssl/issues/22508

At least for libp11 the engine interface seems to be broken.

Sebastian
--- End Message ---
--- Begin Message ---
Source: openssl
Source-Version: 3.0.12-2
Done: Sebastian Andrzej Siewior 

We believe that the bug you reported is fixed in the latest version of
openssl, 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 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Andrzej Siewior  (supplier of updated 
openssl 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: Wed, 08 Nov 2023 21:48:52 +0100
Source: openssl
Architecture: source
Version: 3.0.12-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenSSL Team 
Changed-By: Sebastian Andrzej Siewior 
Closes: 1054546 1055473
Changes:
 openssl (3.0.12-2) unstable; urgency=medium
 .
   * Invoke clean up from the openssl binary as a temporary workaround to avoid
 a crash in libp11/SoftHSM engine (Closes: #1054546).
   * CVE-2023-5678 (Excessive time spent in DH check / generation with large Q
 parameter value) (Closes: #1055473).
Checksums-Sha1:
 9bd4dcb6468607965cfd176b3d1221558ad09525 2461 openssl_3.0.12-2.dsc
 e282e4606f6cbba6aa849c0e6dacc68d5b997228 71192 openssl_3.0.12-2.debian.tar.xz
Checksums-Sha256:
 9546286c5694130215ea568f41a26868545b83d5cda40d463f30e4c6d5f5fa14 2461 
openssl_3.0.12-2.dsc
 3041a9794ea45d9c5e88233af8a1751b185511fe505495f487c5b854c2b06ba5 71192 
openssl_3.0.12-2.debian.tar.xz
Files:
 1c8724e8ced94cc5dbe7e3cf35e161be 2461 utils optional openssl_3.0.12-2.dsc
 438d431d1db1d810d53cc17c65e4d89f 71192 utils optional 
openssl_3.0.12-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEV4kucFIzBRM39v3RBWQfF1cS+lsFAmVL9Y0ACgkQBWQfF1cS
+ls7xAv/fIujc4S2FTXXtHesttsBY1EUneFYxu/CnlELg/xNyFAYQWweT+XwmG7C
qeCWOwK4HmeuCNhJVZ3Rb3nosaqPQhiuOnwFwJHWfyJd+xdw0sN9xxqB5HBODJb6
sVVGzZCPZpFP9YnBRV+t3HCMV/m7GhLGYqmRFFYC2C/PbFmDa/MV/cVnDvjBZNUV
CCjLddypo2UsIdO6+dZJCg43Y+KuzhR0gyhr3ji3oKJlzvFX2wweDWntK2y4arpV
Il1TvJa+p2k54Xyj4blUQIyXkX2UjKByjl61ihHJyecGAJxGe2J3hgMYzaK/gYD9
BEWnxsx/h3/Qwvj7FVNPnaiCxsQfTydZk0e3z+86glrPg4g4vkz1RBMiTauCs90X
P5WqbXrK+8UT3keOntYbXf7Mw6C5WjgZoF4zgcHIZ+QavrRKjJyOAySyo1Ef8olx
MxzI11qcS/rBIBWmlR7T3dqIejzqAJ8eIJ3oR+NERwdkIwB6FKVChWIsfCm10ANK
Ploh3Q3/
=lkmf
-END PGP SIGNATURE End Message ---

Bug#1055264: marked as done (mongo-c-driver FTBFS on 32bit)

2023-11-08 Thread Debian Bug Tracking System

Your message dated Wed, 08 Nov 2023 21:20:51 +
with message-id 
and subject line Bug#1055264: fixed in mongo-c-driver 1.25.1-1
has caused the Debian Bug report #1055264,
regarding mongo-c-driver FTBFS on 32bit
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.)


-- 
1055264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mongo-c-driver
Version: 1.25.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=mongo-c-driver=1.25.0-1

...
In file included from 
/<>/src/libmongoc/src/mongoc/mongoc-linux-distro-scanner.c:28:
/<>/src/libmongoc/src/mongoc/mongoc-linux-distro-scanner.c: In 
function ‘_fgets_wrapper’:
/<>/src/libmongoc/src/mongoc/mongoc-trace-private.h:39:22: error: 
format ‘%ld’ expects argument of type ‘long int’, but argument 6 has type 
‘size_t’ {aka ‘unsigned int’} [-Werror=format=]
   39 |  "TRACE: %s():%d " msg,  \
  |  ^
/<>/src/libmongoc/src/mongoc/mongoc-linux-distro-scanner.c:70:7: 
note: in expansion of macro ‘TRACE’
   70 |   TRACE ("Found line of length %ld, bailing out", len);
  |   ^
...
--- End Message ---
--- Begin Message ---
Source: mongo-c-driver
Source-Version: 1.25.1-1
Done: Kyle Kloberdanz 

We believe that the bug you reported is fixed in the latest version of
mongo-c-driver, 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 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kyle Kloberdanz  (supplier of updated 
mongo-c-driver 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: Wed, 08 Nov 2023 14:32:27 -0600
Source: mongo-c-driver
Architecture: source
Version: 1.25.1-1
Distribution: unstable
Urgency: medium
Maintainer: Mongo C Driver Team 
Changed-By: Kyle Kloberdanz 
Closes: 1055264
Changes:
 mongo-c-driver (1.25.1-1) unstable; urgency=medium
 .
   * New upstream release
   * Fix 32 bit builds (Closes: #1055264)
Checksums-Sha1:
 69a9117a67347d6c6f68519cc3b9e12b5d39ccdf 2706 mongo-c-driver_1.25.1-1.dsc
 bbd3c2b49299394112e06c2ab63b8ebf3ee2226d 6724245 
mongo-c-driver_1.25.1.orig.tar.gz
 b9da9983870fe05a6e2ef5cd3bf639c1c0975ef0 12904 
mongo-c-driver_1.25.1-1.debian.tar.xz
 b87b37d5e4b1d6b4b60c380216238a47181c5ff5 10591 
mongo-c-driver_1.25.1-1_amd64.buildinfo
Checksums-Sha256:
 71a8fd837d234125ed94f1ef9f73f1f30f4c0e843bd03b9034bf6ea26f6ea1bb 2706 
mongo-c-driver_1.25.1-1.dsc
 dd4a9089342778b662b0931cda2d37068b01acfb717d5f2f192c06482b05dd58 6724245 
mongo-c-driver_1.25.1.orig.tar.gz
 c662c1d5cef5e03f22361b67b6dbf17480e8ce29b1e65b4f37aeb0c15ade51be 12904 
mongo-c-driver_1.25.1-1.debian.tar.xz
 84fdbc1a4f38ced4cd37c6dfd15012b3854a3bdd9c866d3759b61f0b1812ca5c 10591 
mongo-c-driver_1.25.1-1_amd64.buildinfo
Files:
 0f38634ba037a5c57ff3e445034c12cd 2706 libs optional mongo-c-driver_1.25.1-1.dsc
 9405f1b8a87191a00990ec80a584fa8b 6724245 libs optional 
mongo-c-driver_1.25.1.orig.tar.gz
 0a832cca4ae499bcd01aa2fd649403aa 12904 libs optional 
mongo-c-driver_1.25.1-1.debian.tar.xz
 c0a8a59e04e8c6c5c2f4a1716a63579d 10591 libs optional 
mongo-c-driver_1.25.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEIYZ1DR4ae5UL01q7ldFmTdL1kUIFAmVL+AsACgkQldFmTdL1
kUKHpBAAt1Cbe4f+7Li4fv9n0owvj1DjpIM0C5QCV3GmjCzxwH6F1+SyJZlNCfgg
F6n7hSacVXCEcZX+gbTMFyPtqH+GalbL25NtNyUOPQoQAeLFGI10xIbHqiufqPPt
hVABHobHxZnVnsGo2B88MhO3dKE+otskiLnjVrzxCU0BcureprCTcISXh8+yENq0
iM2Tm24wd4K9pSlSf5NtBCjxQWVj/2uKnYDYE6i+YYNyzaP8Q1qnZyktO5OTdSJE
Q7EfjOctnMmyoamYyqZO+QW8cydiklgqosvoDbgmqAdFQdsj4BA6spNEwdoYiZDA
km8cyQdlKJMxYm/npp3bgUgQGkX7A1hcwTwoivNVOUxGJsuICVhG7pTT2w849FQL
zEJvmesLjPvBhTGQBw7AmZfKqdpf+Gd9Jna6zb76NF4lqfc5aOm+yCwvM72H5jgm
GTvFEkK5sbOUGP4PnZEpBZ/LsAExZ6nFBQ/mmYlWF8tUw8FftpPqoyTScC4VHt9x
A21aBg8dvCLbq+BldaOv3QX/+oSDcYl8D+nxk5R8WTsvMC4QcWsuk4tTrj44WG88
l1nbr3B+f64R+hwFx+SL9nXTaddbPs0rX2Lho52KXKFLEK1sbv1wO11qSo0O6yky
0uGsQohKmi6yHkQEv7S2q667XPNjHIh4rrxA+uX0VylYVBeAgEs=
=E8C8
-END PGP SIGNATURE End Message ---

Processed: retitle 1054853 to node-postcss-loader: update to 7.3.3 broke the package

2023-11-08 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> retitle 1054853 node-postcss-loader: update to 7.3.3 broke the package
Bug #1054853 [node-postcss-loader] node-katex: FTBFS: TypeError: Cannot read 
properties of undefined (reading '.cjs')
Changed Bug title to 'node-postcss-loader: update to 7.3.3 broke the package' 
from 'node-katex: FTBFS: TypeError: Cannot read properties of undefined 
(reading '.cjs')'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1054853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055510: Best way to coordinate this fix

2023-11-08 Thread Francois Marier

If anybody would like to double-check (or test) the package I've prepared,
it's in salsa right now.

Francois

Bug#1042654: marked as done (python-babel: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting)

2023-11-08 Thread Debian Bug Tracking System

Your message dated Wed, 08 Nov 2023 20:36:42 +
with message-id 
and subject line Bug#1042654: fixed in python-babel 2.10.3-3
has caused the Debian Bug report #1042654,
regarding python-babel: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not 
all arguments converted during string formatting
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.)


-- 
1042654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-babel
Version: 2.10.3-1
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

python-babel fails to build with Sphinx 7.1 and docutils 0.20, both of which
are currently available in experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 -m sphinx docs docs/_build
> Running Sphinx v7.1.1
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [html]: targets for 27 source files that are out of date
> updating environment: [new config] 27 added, 0 changed, 0 removed
> [2Kreading sources... [  4%] api/core
> [2Kreading sources... [  7%] api/dates
> [2Kreading sources... [ 11%] api/index
> [2Kreading sources... [ 15%] api/languages
> [2Kreading sources... [ 19%] api/lists
> [2Kreading sources... [ 22%] api/messages/catalog
> [2Kreading sources... [ 26%] api/messages/extract
> [2Kreading sources... [ 30%] api/messages/index
> [2Kreading sources... [ 33%] api/messages/mofile
> [2Kreading sources... [ 37%] api/messages/pofile
> [2Kreading sources... [ 41%] api/numbers
> [2Kreading sources... [ 44%] api/plural
> [2Kreading sources... [ 48%] api/support
> [2Kreading sources... [ 52%] api/units
> [2Kreading sources... [ 56%] changelog
> 
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/sphinx/ext/extlinks.py", line 103, in 
> role
> title = caption % part
> ^~
> TypeError: not all arguments converted during string formatting
> The full traceback has been saved in /tmp/sphinx-err-04lkbo82.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> make[1]: *** [debian/rules:33: override_dh_installdocs] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/python-babel_2.10.3-1_unstable_sphinx-exp.log

Please see [1] for Sphinx changelog and [2] for Docutils changelog.

Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.

Some notable changes in Sphinx 6 and Sphinx 7:

- Sphinx no longer includes jquery.js and underscore.js by default.
  Please use python3-sphinxcontrib.jquery package if you are using a custom
  template and it still needs jquery.

- The setup.py build_sphinx command was removed. Please instead call
  sphinx-build or "python3 -m sphinx" directly.

- For packages using the extlinks extension, the caption should contain
  exactly one "%s" placeholder (if caption is not None).

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]: 
https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt
[3]: 
https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=sphinx7.1=python-modules-t...@lists.alioth.debian.org=1=1=1=1#results

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
--- End Message ---
--- Begin Message ---
Source: python-babel
Source-Version: 2.10.3-3
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
python-babel, 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 1042...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of

Bug#1054689: therion: FTBFS: utest-proj.cxx:1:10: fatal error: catch2/catch.hpp: No such file or directory

2023-11-08 Thread Olly Betts

On Wed, Nov 08, 2023 at 08:10:26PM +0100, Martin Budaj wrote:
> On Tue, Nov 7, 2023 at 4:25 PM Wookey  wrote:
> 
> > It looks like moving to catch3 and adding:
> > target_link_libraries(test PRIVATE Catch2::Catch2WithMain)
> > in the test targets should do the trick.

> as we still need to maintain Catch2 v2 API compatibility to run CI tests
> and builds on older Ubuntu images, we can't simply migrate to v3.
> 
> For now, I'll just enable using the bundled Catch2 instead of v3 installed
> in the system.

Note that doing so violates a "should" in Debian Policy:

4.13. Embedded code copies
==

Some software packages include in their distribution convenience
copies of code from other software packages, generally so that users
compiling from source don’t have to download multiple packages. Debian
packages should not make use of these convenience copies unless the
included package is explicitly intended to be used in this way.  [17]
If the included code is already in the Debian archive in the form of a
library, the Debian packaging should ensure that binary packages
reference the libraries already in Debian and the convenience copy is
not used. If the included code is not already in Debian, it should be
packaged separately as a prerequisite if possible.  [18]

If you (as upstream) are going to have a bundled code copy of catch, you
could just bundle catch3 instead.

Cheers,
Olly

Bug#1042654: marked as pending in python-babel

2023-11-08 Thread Nilesh Patra

Control: tag -1 pending

Hello,

Bug #1042654 in python-babel reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/python-babel/-/commit/eac13fb166e705f164592a9712c3f28797207afc


Add patch to fix FTBFS with sphinx7.1 (Closes: #1042654)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042654

Processed: Bug#1042654 marked as pending in python-babel

2023-11-08 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #1042654 [src:python-babel] python-babel: FTBFS with Sphinx 7.1, docutils 
0.20: TypeError: not all arguments converted during string formatting
Added tag(s) pending.

-- 
1042654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1042698: marked as done (python-vispy: FTBFS with Sphinx 7.1, docutils 0.20: AttributeError: 'container' object has no attribute 'html5tagname')

2023-11-08 Thread Debian Bug Tracking System

Your message dated Thu, 9 Nov 2023 01:19:59 +0530
with message-id <20231108194959.glwuwpb6od6ht...@office.mailbox.org>
and subject line Re: python-vispy: FTBFS with Sphinx 7.1, docutils 0.20: 
AttributeError: 'container' object has no attribute 'html5tagname'
has caused the Debian Bug report #1042698,
regarding python-vispy: FTBFS with Sphinx 7.1, docutils 0.20: AttributeError: 
'container' object has no attribute 'html5tagname'
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.)


-- 
1042698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-vispy
Version: 0.6.6-3
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

python-vispy fails to build with Sphinx 7.1 and docutils 0.20, both of which
are currently available in experimental.

Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> sphinx-build -b html -d _build/doctrees   . _build/html
> Running Sphinx v7.1.1
> making output directory... done
> WARNING: The pre-Sphinx 1.0 'intersphinx_mapping' format is deprecated and 
> will be removed in Sphinx 8. Update to the current format as described in the 
> documentation. Hint: "intersphinx_mapping = {'': 
> ('https://docs.python.org/3.6', 
> None)}".https://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html#confval-intersphinx_mapping
> WARNING: The pre-Sphinx 1.0 'intersphinx_mapping' format is deprecated and 
> will be removed in Sphinx 8. Update to the current format as described in the 
> documentation. Hint: "intersphinx_mapping = {'': 
> ('https://docs.scipy.org/doc/numpy', 
> None)}".https://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html#confval-intersphinx_mapping
> WARNING: The pre-Sphinx 1.0 'intersphinx_mapping' format is deprecated and 
> will be removed in Sphinx 8. Update to the current format as described in the 
> documentation. Hint: "intersphinx_mapping = {'': 
> ('https://docs.scipy.org/doc/scipy/reference', 
> None)}".https://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html#confval-intersphinx_mapping
> WARNING: The pre-Sphinx 1.0 'intersphinx_mapping' format is deprecated and 
> will be removed in Sphinx 8. Update to the current format as described in the 
> documentation. Hint: "intersphinx_mapping = {'': 
> ('https://vispy.github.io', 
> None)}".https://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html#confval-intersphinx_mapping
> [autosummary] generating autosummary for: README.rst, app.rst, color.rst, 
> community.rst, documentation.rst, gallery.rst, geometry.rst, gl.rst, 
> gloo.glir.rst, gloo.rst, ..., io.rst, modern-gl.rst, news.rst, plot.rst, 
> raspberry.rst, resources.rst, scene.rst, util.rst, vispy.rst, visuals.rst
> WARNING: Could not load OpenGL library.
> loading intersphinx inventory from https://docs.python.org/3.6/objects.inv...
> loading intersphinx inventory from 
> https://docs.scipy.org/doc/numpy/objects.inv...
> loading intersphinx inventory from 
> https://docs.scipy.org/doc/scipy/reference/objects.inv...
> loading intersphinx inventory from https://vispy.github.io/objects.inv...
> intersphinx inventory has moved: https://vispy.github.io/objects.inv -> 
> https://vispy.org/objects.inv
> intersphinx inventory has moved: 
> https://docs.scipy.org/doc/scipy/reference/objects.inv -> 
> https://docs.scipy.org/doc/scipy/objects.inv
> intersphinx inventory has moved: https://docs.scipy.org/doc/numpy/objects.inv 
> -> https://numpy.org/doc/stable/objects.inv
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [html]: targets for 22 source files that are out of date
> updating environment: [new config] 22 added, 0 changed, 0 removed
> [2Kreading sources... [  5%] README
> [2Kreading sources... [  9%] app
> [2Kreading sources... [ 14%] color
> [2Kreading sources... [ 18%] community
> [2Kreading sources... [ 23%] documentation
> [2Kreading sources... [ 27%] gallery
> [2Kreading sources... [ 32%] geometry
> [2Kreading sources... [ 36%] gl
> [2Kreading sources... [ 41%] gloo
> [2Kreading sources... [ 45%] gloo.glir
> [2Kreading sources... [ 50%] index
> [2Kreading sources... [ 55%] installation
> [2Kreading sources... [ 59%] io
> [2Kreading sources... [ 64%] modern-gl
> [2Kreading sources... [ 68%] news
> [2Kreading sources... [ 73%] plot
> [2Kreading sources... [ 77%] raspberry
> [2Kreading sources... [ 82%] resources
> [2Kreading sources... [ 86%] scene
>

Bug#1055509: bfh-container: diversions need to be updated to deal with DEP17 P3

2023-11-08 Thread Helmut Grohne

On Tue, Nov 07, 2023 at 03:37:46PM +, Luca Boccassi wrote:
> systemd-sysv 255~rc1-3, currently in experimental, moves
> halt/poweroff/reboot/shutdown from /sbin/ to /usr/sbin/, and thus
> diversions employed by this package fall afoul of DEP17 P3. Please
> update the diversions as needed. For now, systemd-sysv has an
> unversioned conflict to avoid data losses. This will be uploaded to
> unstable this week. As soon as a fixed version of this package is
> uploaded, the conflict will be changed to versioned.

I'm proposing the attached patch to implement DEP17 mitigation M18. I
caution that the patch is untested, because piuparts failed for
unrelated reasons. open-infrastructure-compute-tools.postinst and
sudo.prerm fail inside piuparts. So consider this a starting point.

Helmut
diff --minimal -Nru bfh-metapackages-20211009/debian/bfh-container.postrm 
bfh-metapackages-20211009/debian/bfh-container.postrm
--- bfh-metapackages-20211009/debian/bfh-container.postrm   2023-08-14 
09:07:46.0 +0200
+++ bfh-metapackages-20211009/debian/bfh-container.postrm   2023-11-08 
16:43:38.0 +0100
@@ -6,12 +6,13 @@
remove)
for FILE in halt poweroff reboot shutdown coldreboot
do
-   dpkg-divert --package bfh-container --quiet --remove 
--rename --divert /lib/container/divert/${FILE}.orig /sbin/${FILE}
+   dpkg-divert --package bfh-container --quiet --remove 
--rename --divert "/usr/lib/container/divert/${FILE}.orig" "/usr/sbin/${FILE}"
+   dpkg-divert --package bfh-container --quiet --remove 
--rename --divert "/lib/container/divert/${FILE}.orig" /sbin/${FILE}
done
 
for FILE in pm-hibernate pm-suspend pm-suspend-hybrid
do
-   dpkg-divert --package bfh-container --quiet --remove 
--rename --divert /lib/container/divert/${FILE}.orig /usr/sbin/${FILE}
+   dpkg-divert --package bfh-container --quiet --remove 
--rename --divert "/usr/lib/container/divert/${FILE}.orig" "/usr/sbin/${FILE}"
done
;;
 
diff --minimal -Nru bfh-metapackages-20211009/debian/bfh-container.preinst 
bfh-metapackages-20211009/debian/bfh-container.preinst
--- bfh-metapackages-20211009/debian/bfh-container.preinst  2023-08-14 
09:07:46.0 +0200
+++ bfh-metapackages-20211009/debian/bfh-container.preinst  2023-11-08 
16:48:30.0 +0100
@@ -4,16 +4,26 @@
 
 case "${1}" in
install|upgrade)
-   mkdir -p /lib/container/divert
+   mkdir -p /usr/lib/container/divert /lib/container/divert
 
for FILE in halt poweroff reboot shutdown coldreboot
do
-   dpkg-divert --package bfh-container --quiet --add 
--rename --divert /lib/container/divert/${FILE}.orig /sbin/${FILE}
+   dpkg-divert --package bfh-container --quiet --add 
--rename --divert "/usr/lib/container/divert/${FILE}.orig" "/usr/sbin/${FILE}"
+   # DEP17 M18 duplicated diversion. Can be removed after 
trixie.
+   dpkg-divert --package bfh-container --quiet --add 
--rename --divert "/lib/container/divert/${FILE}.orig" "/sbin/${FILE}"
done
 
for FILE in pm-hibernate pm-suspend pm-suspend-hybrid
do
-   dpkg-divert --package bfh-container --quiet --add 
--rename --divert /lib/container/divert/${FILE}.orig /usr/sbin/${FILE}
+   if test "$(dpkg-divert --truename "/usr/sbin/${FILE}")" 
= "/lib/container/divert/${FILE}.orig"; then
+   dpkg-divert --package bfh-container --quiet 
--remove --no-rename --divert /lib/container/divert/${FILE}.orig 
/usr/sbin/${FILE}
+   dpkg-divert --package bfh-container --quiet 
--add --no-rename --divert /usr/lib/container/divert/${FILE}.orig 
/usr/sbin/${FILE}
+   if test -e "/lib/container/divert/${FILE}.orig" 
&& ! test -e "/usr/lib/container/divert/${FILE}.orig"; then
+   mv "/lib/container/divert/${FILE}.orig" 
"/usr/lib/container/divert/${FILE}.orig"
+   fi
+   else
+   dpkg-divert --package bfh-container --quiet 
--add --rename --divert /usr/lib/container/divert/${FILE}.orig /usr/sbin/${FILE}
+   fi
done
;;
 
diff --minimal -Nru bfh-metapackages-20211009/debian/changelog 
bfh-metapackages-20211009/debian/changelog
--- bfh-metapackages-20211009/debian/changelog  2023-10-11 11:26:46.0 
+0200
+++ bfh-metapackages-20211009/debian/changelog  2023-11-08 16:49:07.0 
+0100
@@ -1,3 +1,11 @@
+bfh-metapackages (20211009-21.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Duplicate diversions for DEP17 M18. (Closes: #-1)
+  *

Bug#1055511: progress-linux-container: diversions need to be updated to deal with DEP17 P3

2023-11-08 Thread Helmut Grohne

On Tue, Nov 07, 2023 at 03:38:56PM +, Luca Boccassi wrote:
> systemd-sysv 255~rc1-3, currently in experimental, moves
> halt/poweroff/reboot/shutdown from /sbin/ to /usr/sbin/, and thus
> diversions employed by this package fall afoul of DEP17 P3. Please
> update the diversions as needed. For now, systemd-sysv has an
> unversioned conflict to avoid data losses. This will be uploaded to
> unstable this week. As soon as a fixed version of this package is
> uploaded, the conflict will be changed to versioned.

I'm attaching a patch. I don't have high confidence, because it fails
piuparts with left-over files. Given the mess in piuparts, I have no
intentions to further test this. You may use the patch as a starting
point.

Helmut

Bug#1054689: marked as done (therion: FTBFS: utest-proj.cxx:1:10: fatal error: catch2/catch.hpp: No such file or directory)

2023-11-08 Thread Debian Bug Tracking System

Your message dated Wed, 08 Nov 2023 19:37:53 +
with message-id 
and subject line Bug#1054689: fixed in therion 6.1.8-2
has caused the Debian Bug report #1054689,
regarding therion: FTBFS: utest-proj.cxx:1:10: fatal error: catch2/catch.hpp: 
No such file or directory
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.)


-- 
1054689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: therion
Version: 6.1.8-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> /usr/bin/c++ -DFMT_SHARED -DIMG_API_VERSION=1 -DPROJ_VER=9 -DTHLINUX 
> -I/<>/build -I/<> -isystem /usr/include/webp 
> -isystem /<>/extern/quickhull -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -Wall -Wextra -MD -MT 
> CMakeFiles/utest.dir/utest-proj.cxx.o -MF 
> CMakeFiles/utest.dir/utest-proj.cxx.o.d -o 
> CMakeFiles/utest.dir/utest-proj.cxx.o -c /<>/utest-proj.cxx
> /<>/utest-proj.cxx:1:10: fatal error: catch2/catch.hpp: No such 
> file or directory
> 1 | #include 
>   |  ^~
> compilation terminated.
> [113/168] /usr/bin/c++ -DFMT_SHARED -DIMG_API_VERSION=1 -DPROJ_VER=9 
> -DTHLINUX -I/<>/build -I/<> -isystem 
> /usr/include/webp -isystem /<>/extern/quickhull -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -Wall -Wextra -MD -MT 
> CMakeFiles/therion-common.dir/thwarppt.cxx.o -MF 
> CMakeFiles/therion-common.dir/thwarppt.cxx.o.d -o 
> CMakeFiles/therion-common.dir/thwarppt.cxx.o -c /<>/thwarppt.cxx
> [114/168] /usr/bin/c++ -DFMT_SHARED -DIMG_API_VERSION=1 -DPROJ_VER=9 
> -DTHLINUX -I/<>/build -I/<> -isystem 
> /usr/include/webp -isystem /<>/extern/quickhull -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -Wall -Wextra -MD -MT 
> CMakeFiles/therion.dir/therion-main.cxx.o -MF 
> CMakeFiles/therion.dir/therion-main.cxx.o.d -o 
> CMakeFiles/therion.dir/therion-main.cxx.o -c /<>/therion-main.cxx
> [115/168] /usr/bin/c++ -DFMT_SHARED -DIMG_API_VERSION=1 -DPROJ_VER=9 
> -DTHLINUX -I/<>/build -I/<> -isystem 
> /usr/include/webp -isystem /<>/extern/quickhull -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -Wall -Wextra -MD -MT 
> CMakeFiles/therion-common.dir/thsvg.cxx.o -MF 
> CMakeFiles/therion-common.dir/thsvg.cxx.o.d -o 
> CMakeFiles/therion-common.dir/thsvg.cxx.o -c /<>/thsvg.cxx
> [116/168] /usr/bin/c++ -DFMT_SHARED -DIMG_API_VERSION=1 -DPROJ_VER=9 
> -DTHLINUX -I/<>/build -I/<> -isystem 
> /usr/include/webp -isystem /<>/extern/quickhull -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -Wall -Wextra -MD -MT 
> CMakeFiles/therion-common.dir/thtexfonts.cxx.o -MF 
> CMakeFiles/therion-common.dir/thtexfonts.cxx.o.d -o 
> CMakeFiles/therion-common.dir/thtexfonts.cxx.o -c 
> /<>/thtexfonts.cxx
> [117/168] /usr/bin/c++ -DFMT_SHARED -DIMG_API_VERSION=1 -DPROJ_VER=9 
> -DTHLINUX -I/<>/build -I/<> -isystem 
> /usr/include/webp -isystem /<>/extern/quickhull -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -Wall -Wextra -MD -MT 
> CMakeFiles/therion-common.dir/thpdf.cxx.o -MF 
> CMakeFiles/therion-common.dir/thpdf.cxx.o.d -o 
> CMakeFiles/therion-common.dir/thpdf.cxx.o -c /<>/thpdf.cxx
> [118/168] /usr/bin/c++ -DFMT_SHARED -DIMG_API_VERSION=1 -DPROJ_VER=9 
> -DTHLINUX -I/<>/build -I/<> -isystem 
> /usr/include/webp -isystem /<>/extern/quickhull -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -Wall -Wextra -MD -MT 
> CMakeFiles/therion-common.dir/thwarpp.cxx.o -MF 
> CMakeFiles/therion-common.dir/thwarpp.cxx.o.d -o 
>

Bug#1055598: oscrypto: FTBFS in bookworm (Error detecting the version of libcrypto)

2023-11-08 Thread Paul Gevers


Hi,

On 08-11-2023 18:02, Santiago Vila wrote:

Question for Paul Gevers:

When we make an upload for bookworm to fix a FTBFS bug,
should we also try to fix autopkgtests when they fail in stable?


You are welcome to fix autopkgtest issues in stable, provided that the 
upload meets the requirements for stable. In other words (I'm not a 
Stable Release Manager), if the changes are targeted, reviewable and 
worth the risk, time and effort, than they are appreciated. But in the 
way we use "should" in documentation, the word "should" is (still, may 
change in the future) too strong for "fix autopkgtest if they fail in 
stable".


See for an example: https://bugs.debian.org/1054488

Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1054689: therion: FTBFS: utest-proj.cxx:1:10: fatal error: catch2/catch.hpp: No such file or directory

2023-11-08 Thread Martin Budaj

On Tue, Nov 7, 2023 at 4:25 PM Wookey  wrote:

> It looks like moving to catch3 and adding:
> target_link_libraries(test PRIVATE Catch2::Catch2WithMain)
> in the test targets should do the trick.
>

Hi,

as we still need to maintain Catch2 v2 API compatibility to run CI tests
and builds on older Ubuntu images, we can't simply migrate to v3.

For now, I'll just enable using the bundled Catch2 instead of v3 installed
in the system.

Martin

Bug#1055598: oscrypto: FTBFS in bookworm (Error detecting the version of libcrypto)

2023-11-08 Thread Bastian Germann


Am 08.11.23 um 17:47 schrieb Santiago Vila:

Note: I joined the Python team recently to fix bugs
like this in stable, so I'd just need the confirmation
that the above is actually what we need to do.


Confirmed.

Bug#1055598: oscrypto: FTBFS in bookworm (Error detecting the version of libcrypto)

2023-11-08 Thread Santiago Vila


Note: I've asked Paul Gevers if it's desirable/recommended to fix
autopkgtests in stable when fixing FTBFS bugs in stable.
If yes, we should include the changes in -2 too.

Thanks.

Bug#1055598: oscrypto: FTBFS in bookworm (Error detecting the version of libcrypto)

2023-11-08 Thread Santiago Vila


Package: src:oscrypto
Version: 1.3.0-1
Severity: serious
Tags: ftbfs
Control: close -1 1.3.0-4

Hello. This package currently FTBFS in bookworm:

[...]
oscrypto.errors.LibraryNotFoundError: Error detecting the version of libcrypto
[...]

Full log here:

https://tests.reproducible-builds.org/debian/rbuild/bookworm/amd64/oscrypto_1.3.0-1.rbuild.log.gz

but I see that the source package in unstable builds ok in bookworm.

Since packages in stable must build in stable, we should
make an upload for bookworm to fix this.

I believe the relevant changes are all that show
when we do this:

git diff debian/1.3.0-2 debian/1.3.0-4

i.e. these three additional patches:

--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,4 @@
 do_not_put_LICENSE_in_egg_info.patch
+libcrypto_ctypes_regex.patch
+openssl_3.0.10.patch
+Make_OpenSSL_version_regexes_more_robust.patch

Note: I joined the Python team recently to fix bugs
like this in stable, so I'd just need the confirmation
that the above is actually what we need to do.

(Unless somebody else wants to take care of this, of course)

Thanks.

Processed: oscrypto: FTBFS in bookworm (Error detecting the version of libcrypto)

2023-11-08 Thread Debian Bug Tracking System

Processing control commands:

> close -1 1.3.0-4
Bug #1055598 [src:oscrypto] oscrypto: FTBFS in bookworm (Error detecting the 
version of libcrypto)
Marked as fixed in versions oscrypto/1.3.0-4.
Bug #1055598 [src:oscrypto] oscrypto: FTBFS in bookworm (Error detecting the 
version of libcrypto)
Marked Bug as done

-- 
1055598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055597: FTBFS: test failure with Mail-Message 3.014

2023-11-08 Thread gregor herrmann

Source: libmail-box-perl
Version: 3.010-1
Severity: serious
Tags: upstream ftbfs trixie sid
Justification: fails to build from source
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=150141

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As seen on ci.debian.net, e.g.
https://ci.debian.net/data/autopkgtest/testing/amd64/libm/libmail-box-perl/39681951/log.gz
and also upstream at https://rt.cpan.org/Public/Bug/Display.html?id=150141
- --> 
https://www.cpantesters.org/cpan/report/4063279a-6e7d-11ee-a059-85ce9d387f07
libmail-box-perl's t/505parser-bodymp.t fails with
libmail-message-perl_3.014-1

#   Failed test '1 lines 0'
#   at t/505parser-bodymp.t line 68.
#  got: 22
# expected: 21
   
#   Failed test '1 lines 1'
#   at t/505parser-bodymp.t line 68.
#  got: 83
# expected: 82

#   Failed test '1 lines 2'
#   at t/505parser-bodymp.t line 68.
#  got: 35
# expected: 34
# Looks like you failed 3 tests of 313.
t/505parser-bodymp.t .
1..313
ok 1 - creation of parser
ok 2 - 1 from 0
ok 3 - 1 head count
ok 4 - 1 from 0
ok 5 - 1 head count
ok 6 - 1 from 0
ok 7 - 1 head count
ok 8 - 1 from 0
ok 9 - 1 head count
ok 10 - 1 from 0
ok 11 - 1 head count
ok 12 - 1 from 0
ok 13 - 1 head count
ok 14 - 1 from 0
ok 15 - 1 head count
ok 16 - 1 from 0
ok 17 - 1 head count
ok 18 - 1 from 0
ok 19 - 1 head count
ok 20 - 1 from 0
ok 21 - 1 head count
ok 22 - 1 from 0
ok 23 - 1 head count
ok 24 - 1 from 0
ok 25 - 1 head count
ok 26 - 1 from 0
ok 27 - 1 head count
ok 28 - 1 from 0
ok 29 - 1 head count
ok 30 - 1 from 0
ok 31 - 1 head count
ok 32 - 1 from 0
ok 33 - 1 head count
ok 34 - 1 from 0
ok 35 - 1 head count
ok 36 - 1 from 0
ok 37 - 1 head count
ok 38 - 1 from 0
ok 39 - 1 head count
ok 40 - 1 from 0
ok 41 - 1 head count
ok 42 - 1 from 0
ok 43 - 1 head count
ok 44 - 1 body 0
not ok 45 - 1 lines 0
ok 46 - 1 size 0
ok 47 - 1 from 1
ok 48 - 1 head count
ok 49 - 1 from 1
ok 50 - 1 head count
ok 51 - 1 from 1
ok 52 - 1 head count
ok 53 - 1 from 1
ok 54 - 1 head count
ok 55 - 1 from 1
ok 56 - 1 head count
ok 57 - 1 body 1
not ok 58 - 1 lines 1
ok 59 - 1 size 1
ok 60 - 1 from 2
ok 61 - 1 head count
ok 62 - 1 from 2
ok 63 - 1 head count
ok 64 - 1 body 2
not ok 65 - 1 lines 2
ok 66 - 1 size 2
ok 67 - 1 from 3
ok 68 - 1 head count
ok 69 - 1 from 3
ok 70 - 1 head count
ok 71 - 1 from 3
ok 72 - 1 head count
ok 73 - 1 from 3
ok 74 - 1 head count
ok 75 - 1 from 3
ok 76 - 1 head count
ok 77 - 1 from 3
ok 78 - 1 head count
ok 79 - 1 from 3
ok 80 - 1 head count
ok 81 - 1 from 3
ok 82 - 1 head count
ok 83 - 1 from 3
ok 84 - 1 head count
ok 85 - 1 from 3
ok 86 - 1 head count
ok 87 - 1 from 3
ok 88 - 1 head count
ok 89 - 1 from 3
ok 90 - 1 head count
ok 91 - 1 from 3
ok 92 - 1 head count
ok 93 - 1 from 3
ok 94 - 1 head count
ok 95 - 1 from 3
ok 96 - 1 head count
ok 97 - 1 from 3
ok 98 - 1 head count
ok 99 - 1 from 3
ok 100 - 1 head count
ok 101
ok 102 - 2 from 0
ok 103 - 2 head 0
ok 104 - 2 from 0
ok 105 - 2 head 0
ok 106 - 2 from 0
ok 107 - 2 head 0
ok 108 - 2 from 0
ok 109 - 2 head 0
ok 110 - 2 from 0
ok 111 - 2 head 0
ok 112 - 2 from 0
ok 113 - 2 head 0
ok 114 - 2 from 0
ok 115 - 2 head 0
ok 116 - 2 from 0
ok 117 - 2 head 0
ok 118 - 2 from 0
ok 119 - 2 head 0
ok 120 - 2 from 0
ok 121 - 2 head 0
ok 122 - 2 from 0
ok 123 - 2 head 0
ok 124 - 2 from 0
ok 125 - 2 head 0
ok 126 - 2 from 0
ok 127 - 2 head 0
ok 128 - 2 from 0
ok 129 - 2 head 0
ok 130 - 2 from 0
ok 131 - 2 head 0
ok 132 - 2 from 0
ok 133 - 2 head 0
ok 134 - 2 from 0
ok 135 - 2 head 0
ok 136 - 2 from 0
ok 137 - 2 head 0
ok 138 - 2 from 0
ok 139 - 2 head 0
ok 140 - 2 from 0
ok 141 - 2 head 0
ok 142 - 2 from 0
ok 143 - 2 head 0
ok 144 - 2 body 0
ok 145 - 2 size 0
ok 146 - 2 lines 0
ok 147 - 2 names 0
ok 148 - 2 sep 0
ok 149 - 2 from 1
ok 150 - 2 head 1
ok 151 - 2 from 1
ok 152 - 2 head 1
ok 153 - 2 from 1
ok 154 - 2 head 1
ok 155 - 2 from 1
ok 156 - 2 head 1
ok 157 - 2 from 1
ok 158 - 2 head 1
ok 159 - 2 body 1
ok 160 - 2 size 1
ok 161 - 2 lines 1
ok 162 - 2 subject 1
ok 163 - 2 names 1
ok 164 - 2 sep 1
ok 165 - 2 from 2
ok 166 - 2 head 2
ok 167 - 2 from 2
ok 168 - 2 head 2
ok 169 - 2 body 2
ok 170 - 2 size 2
ok 171 - 2 lines 2
ok 172 - 2 names 2
ok 173 - 2 sep 2
ok 174 - 2 from 3
ok 175 - 2 head 3
ok 176 - 2 from 3
ok 177 - 2 head 3
ok 178 - 2 from 3
ok 179 - 2 head 3
ok 180 - 2 from 3
ok 181 - 2 head 3
ok 182 - 2 from 3
ok 183 - 2 head 3
ok 184 - 2 from 3
ok 185 - 2 head 3
ok 186 - 2 from 3
ok 187 - 2 head 3
ok 188 - 2 from 3
ok 189 - 2 head 3
ok 190 - 2 from 3
ok 191 - 2 head 3
ok 192 - 2 from 3
ok 193 - 2 head 3
ok 194 - 2 from 3
ok 195 - 2 head 3
ok 196 - 2 from 3
ok 197 - 2 head 3
ok 198 - 2 from 3
ok 199 - 2 head 3
ok 200 - 2 from 3
ok 201 - 2 head 3
ok 202 - 2 from 3
ok 203 - 2 head 3
ok 204 - 2 from 3
ok 205 - 2 head 3
ok 206 - 2 from 3
ok 207 - 2 head 3
ok 208 - 3 From 0
ok 209 - 3 Head 0
ok 210 - 3 From 0
ok 211 - 3 Head 0
ok 212 - 3 From 0
ok 213 - 3 Head 0
ok 214 - 3 From 0
ok 215 - 3 Head 0
ok 216 - 3 From 0
ok 217 - 3 Head 0

Bug#1055510: Best way to coordinate this fix

2023-11-08 Thread Helmut Grohne

Control: tags -1 + patch

On Tue, Nov 07, 2023 at 09:35:54PM +0100, Helmut Grohne wrote:
> On Tue, Nov 07, 2023 at 08:11:19PM +, Luca Boccassi wrote:
> > On Tue, 7 Nov 2023 at 20:04, Francois Marier  wrote:
> > > What's the best way to coordinate a fix for this?
> > >
> > > I assume that we shouldn't upload a new molly-guard packages until the 
> > > files
> > > have actually moved in the systemd package?
> > >
> > > Should we wait until systemd is in unstable to push a new molly-guard out?
> 
> If the workaround is correctly implemented, it can go to unstable
> directly. Note that it's not simply changing the diversions from the old
> location to the new location. The workaround is duplicating them. At
> that point, you can no longer use --rename and have to do the renaming
> by hand. I'm happy to review a patch. For opensysusers I sent one, but I
> haven't gotten down to molly-guard yet.

Proposed patch attached.

Helmut
diff --minimal -Nru molly-guard-0.7.2/Makefile molly-guard-0.7.2+nmu1/Makefile
--- molly-guard-0.7.2/Makefile  2019-07-09 18:50:53.0 +0200
+++ molly-guard-0.7.2+nmu1/Makefile 2023-11-08 14:16:52.0 +0100
@@ -1,7 +1,7 @@
 PREFIX?=/usr
 cfgdir?=/etc/molly-guard
-libdir?=/lib
-sbindir?=/sbin
+libdir?=$(PREFIX)/lib
+sbindir?=$(PREFIX)/sbin
 REALPATH?=$(libdir)/molly-guard
 
 all: molly-guard.8 shutdown
diff --minimal -Nru molly-guard-0.7.2/debian/changelog 
molly-guard-0.7.2+nmu1/debian/changelog
--- molly-guard-0.7.2/debian/changelog  2019-07-09 18:50:53.0 +0200
+++ molly-guard-0.7.2+nmu1/debian/changelog 2023-11-08 14:47:40.0 
+0100
@@ -1,3 +1,11 @@
+molly-guard (0.7.2+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Duplicate aliased diversions for DEP17 M18. (Closes: #-1)
+  * Move all files to /usr.
+
+ -- Helmut Grohne   Wed, 08 Nov 2023 14:47:40 +0100
+
 molly-guard (0.7.2) unstable; urgency=medium
 
   * upload to unstable
diff --minimal -Nru molly-guard-0.7.2/debian/molly-guard.lintian-overrides 
molly-guard-0.7.2+nmu1/debian/molly-guard.lintian-overrides
--- molly-guard-0.7.2/debian/molly-guard.lintian-overrides  2019-07-09 
18:50:53.0 +0200
+++ molly-guard-0.7.2+nmu1/debian/molly-guard.lintian-overrides 2023-11-08 
14:47:40.0 +0100
@@ -1,9 +1,9 @@
-molly-guard: binary-without-manpage sbin/coldreboot
-molly-guard: binary-without-manpage sbin/halt
-molly-guard: binary-without-manpage sbin/pm-hibernate
-molly-guard: binary-without-manpage sbin/pm-suspend
-molly-guard: binary-without-manpage sbin/pm-suspend-hybrid
-molly-guard: binary-without-manpage sbin/poweroff
-molly-guard: binary-without-manpage sbin/reboot
-molly-guard: binary-without-manpage sbin/shutdown
-molly-guard: diversion-for-unknown-file usr/sbin/* preinst:29
+molly-guard: no-manual-page [usr/sbin/coldreboot]
+molly-guard: no-manual-page [usr/sbin/halt]
+molly-guard: no-manual-page [usr/sbin/pm-hibernate]
+molly-guard: no-manual-page [usr/sbin/pm-suspend]
+molly-guard: no-manual-page [usr/sbin/pm-suspend-hybrid]
+molly-guard: no-manual-page [usr/sbin/poweroff]
+molly-guard: no-manual-page [usr/sbin/reboot]
+molly-guard: no-manual-page [usr/sbin/shutdown]
+molly-guard: diversion-for-unknown-file sbin/* preinst:*
diff --minimal -Nru molly-guard-0.7.2/debian/molly-guard.postrm 
molly-guard-0.7.2+nmu1/debian/molly-guard.postrm
--- molly-guard-0.7.2/debian/molly-guard.postrm 2019-07-09 18:50:53.0 
+0200
+++ molly-guard-0.7.2+nmu1/debian/molly-guard.postrm2023-11-08 
14:47:40.0 +0100
@@ -20,7 +20,11 @@
 case "$1" in
 remove)
 for cmd in halt poweroff reboot shutdown coldreboot ; do
-dpkg-divert --package molly-guard --rename --remove /sbin/$cmd
+dpkg-divert --package molly-guard --no-rename --remove /sbin/$cmd
+dpkg-divert --package molly-guard --no-rename --remove 
"/usr/sbin/$cmd"
+   if test -e "/usr/lib/molly-guard/$cmd"; then
+mv "/usr/lib/molly-guard/$cmd" "/usr/sbin/$cmd"
+fi
 done
 
 for cmd in pm-hibernate pm-suspend pm-suspend-hybrid ; do
diff --minimal -Nru molly-guard-0.7.2/debian/molly-guard.preinst 
molly-guard-0.7.2+nmu1/debian/molly-guard.preinst
--- molly-guard-0.7.2/debian/molly-guard.preinst2019-07-09 
18:50:53.0 +0200
+++ molly-guard-0.7.2+nmu1/debian/molly-guard.preinst   2023-11-08 
14:47:40.0 +0100
@@ -14,7 +14,7 @@
 
 case "$1" in
 install|upgrade)
-mkdir -p /lib/molly-guard
+mkdir -p /usr/lib/molly-guard
 
 # Cleanup erroneous diversions added in 0.6.0
 for cmd in pm-hibernate pm-suspend pm-suspend-hybrid ; do
@@ -22,11 +22,27 @@
 done
 
 for cmd in halt poweroff reboot shutdown coldreboot ; do
-dpkg-divert --package molly-guard --divert /lib/molly-guard/$cmd 
--rename /sbin/$cmd
+dpkg-divert --package molly-guard --divert 
"/usr/lib/molly-guard/$cmd" --no-rename --add "/usr/sbin/$cmd"
+#

Processed: Re: Best way to coordinate this fix

2023-11-08 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 + patch
Bug #1055510 [molly-guard] molly-guard: diversions need to be updated to deal 
with DEP17 P3
Added tag(s) patch.

-- 
1055510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1054005 is important

2023-11-08 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> severity 1054005 important
Bug #1054005 [src:linux] linux-image-6.5.0-1-amd64: System freeze when suspend 
or hybrid-suspend or hibernate
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1054005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055580: dlt-daemon: Runs daemon as user nobody with owned files on fsys

2023-11-08 Thread Guillem Jover

Package: dlt-daemon
Version: 2.18.0-1
Severity: serious
Tags: security

Hi!

This daemon runs as user nobody, while creating multiple files on the
filesystem owned by the same user, which are used as part of its
security protection. This is a security issue, given that other
daemons on the system might be running as the same user, and worse
when dlt-daemon is writing and parsing files from hardcoded paths
under /tmp.

From base-passwd/users-and-groups.txt.gz:

  ,---
nobody, nogroup
  Daemons that need not own any files sometimes run as
  user nobody and group nogroup, although using a
  dedicated user is far preferable. Thus, no files on a
  system should be owned by this user or group.

  (Technically speaking, it does no harm for a file to be
  owned by group nogroup as long as the ownership confers
  no additional privileges, that is if the group and other
  permission bits are equal. However, this is sloppy
  practice and should be avoided.)

  If root-squashing is in use over NFS, root access from
  the client is performed as user nobody on the server.
  `---

If you are going to fix this by using a dedicated user/group, please
make sure to namespace them with «_» to distinguish them as system
users and avoid unnecessary collisions with non-system, users. (Such
as _dlt or similar.)

[ The version I used is the earliest I found with the same issue from
  the tracker.d.o page, earlier version might be affected too, dunno. ]

Thanks,
Guillem

Processed: Re: Your mail

2023-11-08 Thread Debian Bug Tracking System

Processing control commands:

> fixed -1 13.0.9+dfsg-1
Bug #1042697 [src:groonga] groonga: FTBFS with Sphinx 7.1, docutils 0.20: 
/usr/bin/install: cannot stat './html/_static/underscore.js': No such file or 
directory
The source 'groonga' and version '13.0.9+dfsg-1' do not appear to match any 
binary packages
Marked as fixed in versions groonga/13.0.9+dfsg-1.

-- 
1042697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1042697: Your mail

2023-11-08 Thread Kentaro HAYASHI

Control: fixed -1 13.0.9+dfsg-1

I've forgot to close with uploaded version.


On Sat, 5 Aug 2023 15:14:10 +0900 Kentaro HAYASHI
 wrote:
> NOTE for sphinx 7 when it is landed into sid:
> 
> * doc/files.am should be patched to eliminate jquery.js and
>   underscore.js dependency or use  python3-sphinxcontrib.jquery and so
>   on.
> * debian/control
>   * add missing libjs-sphixdoc dependency.
> * debian/groonga-doc.links should be updated.
>   * drop jquery and underscore 
>   * add other searchtools language_data sphihx_highlight doctools

Bug#1051155: needs fixing for Python 3.12 as supported Python version

2023-11-08 Thread Matthias Klose


needs fixing for Python 3.12 as supported Python version

Processed: closing 1042642

2023-11-08 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> close 1042642 3.40-2
Bug #1042642 [src:ns3] ns3: FTBFS with Sphinx 7.1, docutils 0.20: make[6]: *** 
[Makefile:75: html] Error 2
Marked as fixed in versions ns3/3.40-2.
Bug #1042642 [src:ns3] ns3: FTBFS with Sphinx 7.1, docutils 0.20: make[6]: *** 
[Makefile:75: html] Error 2
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1042642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: closing 1054905

2023-11-08 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> close 1054905 2.9.1-2
Bug #1054905 [src:linuxcnc] linuxcnc: binary-any FTBFS
Bug #1054934 [src:linuxcnc] linuxcnc: FTBFS: dh_install: error: missing files, 
aborting
Marked as fixed in versions linuxcnc/2.9.1-2.
Marked as fixed in versions linuxcnc/2.9.1-2.
Bug #1054905 [src:linuxcnc] linuxcnc: binary-any FTBFS
Bug #1054934 [src:linuxcnc] linuxcnc: FTBFS: dh_install: error: missing files, 
aborting
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1054905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054905
1054934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: forcibly merging 1054905 1054934

2023-11-08 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> forcemerge 1054905 1054934
Bug #1054905 [src:linuxcnc] linuxcnc: binary-any FTBFS
Bug #1054905 [src:linuxcnc] linuxcnc: binary-any FTBFS
Added tag(s) sid and trixie.
Bug #1054934 [src:linuxcnc] linuxcnc: FTBFS: dh_install: error: missing files, 
aborting
Merged 1054905 1054934
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1054905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054905
1054934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055447: marked as done (htsjdk: FTBFS: 35741 tests completed, 9 failed, 10 skipped)

2023-11-08 Thread Debian Bug Tracking System

Your message dated Wed, 08 Nov 2023 10:50:55 +
with message-id 
and subject line Bug#1055447: fixed in htsjdk 3.0.5+dfsg-2
has caused the Debian Bug report #1055447,
regarding htsjdk: FTBFS: 35741 tests completed, 9 failed, 10 skipped
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.)


-- 
1055447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: htsjdk
Version: 3.0.5+dfsg-1
Severity: serious
Justification: FTBFS
Tags: sid ftbfs

Hi,

I noticed htsjdk FTBFS in sid:

Gradle Test Executor 1 finished executing tests.
Results: FAILURE (35741 tests, 35722 successes, 9 failures, 10 skipped)

35741 tests completed, 9 failed, 10 skipped
Finished generating test XML results (0.354 secs) into: 
/home/merkys/htsjdk-3.0.5+dfsg/build/test-results/testWithDefaultReference

Generating HTML test report...
Finished generating test html results (0.42 secs) into: 
/home/merkys/htsjdk-3.0.5+dfsg/build/reports/tests/testWithDefaultReference

:testWithDefaultReference FAILED
:testWithDefaultReference (Thread[Task worker for ':' Thread 2,5,main]) 
completed. Took 11 mins 7.989 secs.


FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':testWithDefaultReference'.
> There were failing tests. See the report at: 
file:///home/merkys/htsjdk-3.0.5+dfsg/build/reports/tests/testWithDefaultReference/index.html


Andrius
--- End Message ---
--- Begin Message ---
Source: htsjdk
Source-Version: 3.0.5+dfsg-2
Done: Pierre Gruet 

We believe that the bug you reported is fixed in the latest version of
htsjdk, 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 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pierre Gruet  (supplier of updated htsjdk 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: Wed, 08 Nov 2023 10:13:12 +0100
Source: htsjdk
Architecture: source
Version: 3.0.5+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Pierre Gruet 
Closes: 1055447
Changes:
 htsjdk (3.0.5+dfsg-2) unstable; urgency=medium
 .
   * Ensuring directories exist before the unit tests attempt to create files
 inside (Closes: #1055447)
Checksums-Sha1:
 389529f65f907428ae9d2e2008454ad598dbe41c 2649 htsjdk_3.0.5+dfsg-2.dsc
 ee60b5b118533db023aca7e81d6ea6d65d4d997e 34420 
htsjdk_3.0.5+dfsg-2.debian.tar.xz
 477523ddd02ff698c6bfb1fbd763a01b83f6dd7f 17250 
htsjdk_3.0.5+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 3a1d02f071f94b2dbcff95e8d7e70f424bc21d2ea46e25ed1e7985857bb6274c 2649 
htsjdk_3.0.5+dfsg-2.dsc
 fa7eae3210a403e689d01557415df274b5e78324ed41fbdf4670ce5d64d59431 34420 
htsjdk_3.0.5+dfsg-2.debian.tar.xz
 d361d63d95c2d01cf7624b113fff0a49bf05e8564bfb3e5f62f35a4e3eaf5c9a 17250 
htsjdk_3.0.5+dfsg-2_amd64.buildinfo
Files:
 cb99ab3ef39a1bdae782778fbdcf5761 2649 science optional htsjdk_3.0.5+dfsg-2.dsc
 ff64addd4d8f2870f42749588c21f9db 34420 science optional 
htsjdk_3.0.5+dfsg-2.debian.tar.xz
 da93318c5c3180045a852a2f9d2bf635 17250 science optional 
htsjdk_3.0.5+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEM8soQxPpC9J9y0UjYAMWptwndHYFAmVLY0kACgkQYAMWptwn
dHYRmxAAqNChu8XHdaKrT1t2lQGYjkCTWvpyID48kkH9LfIjk8rQCYhElFco9VaG
YP3eGdlzAPIoLNiDBJm+9GkODC0VTZ9n1prwNOH9rdjKdPHVWq+vfFZjdDDiBVPx
YDIg1yNsOTMtpXfZky9H+d0BDdeEBaPp/Jonp3a54fS0QvHGouymX0d8owbV5asa
PNEPzf/htZm2B684sTZcvEofETmLciYhOr4kVdT4D4rT2+NG6ReNU7wQ3ha2ZGIQ
DJNWRDzG8qu7dlCVNyn1iFMaRkxN4B+QvehCNfPj9Z/aYP0ZeJ+QadufjThso2Hr
xGOEr31e+KUYjZ7Vfvqa9HMBnP1xUPWiBZ9o4WXHZt+IMlg/Naj/t3dLeI9n76Vf
IXLM7e9TN1saRxvQu2Bs63JF7dNuP+2EHE6xR+KwSDRsizRFChhG1bTsFLDnoYGQ
WQfd/AOuWmxcR/Ak6rLpVC9eFueaQWMtJB5DYSWMqbn4IiF7/rA2tFch7N2yQQ6M
b6tXbkFSoV+mXhXFNv1ef5i8qJcnzSL/74QbStk7XRe7izOKUUE5mgXeXi+iJvwM
uJi2LOWzjb3YQolKk++Z9gaZiuSrzNW1xQezQg96Dr1Dn/Y/zQ/d5U0laJUYTRHb
4PGZkjH0hPwIFLa/YKFjbX9DI5izrY3+ZKuhzOYPCFTn2fF9tbU=
=4+T4
-END PGP SIGNATURE End Message ---

Bug#1055447: htsjdk: FTBFS: 35741 tests completed, 9 failed, 10 skipped

2023-11-08 Thread Andrius Merkys


Hi Pierre,

On 2023-11-08 12:14, Pierre Gruet wrote:

Thanks for the bug report. It was not easy to reproduce this one!


Interesting, I ran rebuild two times and both times it failed :) I 
spotted this issue during ratt-rebuild of a bunch of other packages, did 
not really give a decent look.


I found out some the failing tests were trying to create temporary files 
in directories that did not exist, possibly they rely on other tests to 
create them and tests are not run in the same order in every build? I am 
unsure how to address the test order so that it is always the same.


Anyway, I added a check of the existence of directories before 
attempting to put anything inside them.


Great, thanks!

Best wishes,
Andrius

Processed: tagging 1055447

2023-11-08 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> tags 1055447 + pending
Bug #1055447 [src:htsjdk] htsjdk: FTBFS: 35741 tests completed, 9 failed, 10 
skipped
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055447: htsjdk: FTBFS: 35741 tests completed, 9 failed, 10 skipped

2023-11-08 Thread Pierre Gruet


Control: targs -1 pending

Hi Andrius,

Thanks for the bug report. It was not easy to reproduce this one!

On Mon, 6 Nov 2023 14:35:05 +0200 Andrius Merkys  wrote:
> Source: htsjdk
> Version: 3.0.5+dfsg-1
> Severity: serious
> Justification: FTBFS
> Tags: sid ftbfs
>
> Hi,
>
> I noticed htsjdk FTBFS in sid:
>
> Gradle Test Executor 1 finished executing tests.
> Results: FAILURE (35741 tests, 35722 successes, 9 failures, 10 skipped)
>
> 35741 tests completed, 9 failed, 10 skipped
> Finished generating test XML results (0.354 secs) into:
> 
/home/merkys/htsjdk-3.0.5+dfsg/build/test-results/testWithDefaultReference

> Generating HTML test report...
> Finished generating test html results (0.42 secs) into:
> 
/home/merkys/htsjdk-3.0.5+dfsg/build/reports/tests/testWithDefaultReference

> :testWithDefaultReference FAILED
> :testWithDefaultReference (Thread[Task worker for ':' Thread 2,5,main])
> completed. Took 11 mins 7.989 secs.
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':testWithDefaultReference'.
> > There were failing tests. See the report at:
> 
file:///home/merkys/htsjdk-3.0.5+dfsg/build/reports/tests/testWithDefaultReference/index.html


I found out some the failing tests were trying to create temporary files 
in directories that did not exist, possibly they rely on other tests to 
create them and tests are not run in the same order in every build? I am 
unsure how to address the test order so that it is always the same.


Anyway, I added a check of the existence of directories before 
attempting to put anything inside them.


>
> Andrius
>
>

Best,

--
Pierre


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#1055514: opensysusers: ineffective diversion of /bin/systemd-sysusers due to /usr-merge and DEP17

2023-11-08 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 normal
Bug #1055514 [opensysusers] opensysusers: ineffective diversion of 
/bin/systemd-sysusers due to /usr-merge and DEP17
Severity set to 'normal' from 'serious'

-- 
1055514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055514: opensysusers: ineffective diversion of /bin/systemd-sysusers due to /usr-merge and DEP17

2023-11-08 Thread Helmut Grohne

Control: severity -1 normal

On Tue, Nov 07, 2023 at 10:40:46PM +0100, Andrea Pappacoda wrote:
> I do agree with this reasoning. As mentioned in one of the old threads about
> this, in my opinion it would've been better to have a general, more
> restricted "sysusers" alternative command which could've been provided by
> opensysusers and systemd-sysusers, and would be used by things like
> dh_installsysusers and the like. Stepping into the "systemd-" namespace
> without actually supporting all the features *and* closely following new
> feature additions is asking for trouble. And, since the upstream developers
> (i.e. the Artix Linux maintainers) stopped development in favour of
> systemd-standalone-sysusers[1], I'm now more inclined to change approach and
> drop diversions.

The second of my patches implements this.

> > A possible compromise could be that opensysusers stops diverting
> > systemd-sysusers and installs the symbolic link without diversion such
> > that systemd becomes the preferred provider when coinstalled. It could
> > detect removal of systemd using file triggers and then reinstate the
> > link. Such a setup also requires little cooperation from systemd
> > maintainers, but it relies on an symbolic link that is completely
> > untracked by dpkg, so there is some fragility to be found here whereas
> > the conflict is conceptually simpler.
> 
> I'm not sure I follow, but choosing an approach which isn't tracked by dpkg
> doesn't sound right to me.

There is prior art for this approach. For instance, some packages
required compatibility symlinks for tools moved from /bin to /usr/bin.
Such symlinks could not added to data.tar as they would break on
merged-/usr instances. Therefore these were managed as untracked files
using maintainer scripts. This is not nice, but technically feasible.
It was not my preferred option and hence there is no patch for this.

In any case the goal of that approach would be providing the
systemd-sysusers command from a systemd or systemd-standalone-sysusers
happens to be installed and providing it from opensysuser whenever
neither of them is installed.

> I want to fix this too, and I really thank you for the help. I'm inclined to
> drop the diversions, but I'd first like to fully understand the consequences
> (e.g. would something break for someone?).

What do you need to know to gain this understanding? I suppose you want
to talk to Thomas here. I respectfully disagree with Thomas, so I am
probably not well suited to represent his view.

Given that systemd conflicts with opensysusers in experimental, we could
also just close this bug. The /usr-merge related bug arises from the
coinstallability that has now been revoked. You only need to do
something if you want coinstallability back or clean up (now) unused
diversions.

Helmut

Bug#1054813: python-dmidecode: FTBFS: make[2]: *** [Makefile:4: test] Error 1

2023-11-08 Thread Matthias Klose


there are several issues here, starting with python called, not python3.

the build log although doesn't show any compilation issue.

Bug#1055559: marked as done (python3-ruff: Missing dependency on ruff)

2023-11-08 Thread Debian Bug Tracking System

Your message dated Wed, 08 Nov 2023 09:50:44 +
with message-id 
and subject line Bug#109: fixed in ruff 0.0.291+dfsg1-2
has caused the Debian Bug report #109,
regarding python3-ruff: Missing dependency on ruff
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.)


-- 
109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-ruff
Severity: serious
Version: 0.0.291+dfsg1-1
Control: block 1054205 by -1

The Python library is entirely useless without the binary, thus there
needs to be a strong dependency between them.

-- 
Arto Jantunen
--- End Message ---
--- Begin Message ---
Source: ruff
Source-Version: 0.0.291+dfsg1-2
Done: Jelmer Vernooĳ 

We believe that the bug you reported is fixed in the latest version of
ruff, 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 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jelmer Vernooĳ  (supplier of updated ruff 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: Wed, 08 Nov 2023 09:31:58 +
Source: ruff
Architecture: source
Version: 0.0.291+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Jelmer Vernooĳ 
Changed-By: Jelmer Vernooĳ 
Closes: 109
Changes:
 ruff (0.0.291+dfsg1-2) unstable; urgency=medium
 .
   * python3-ruff: Add dependency on ruff itself. Closes: #109
Checksums-Sha1:
 6e243c1325f425f002f88429c654f0566bdd818c 2807 ruff_0.0.291+dfsg1-2.dsc
 3e4be706e76509011658680f5253c30d4c951b35 5980 
ruff_0.0.291+dfsg1-2.debian.tar.xz
 1f4d9f110b64a017964ffac35b747bb4b3266188 33066 
ruff_0.0.291+dfsg1-2_source.buildinfo
Checksums-Sha256:
 99b0e3f419a9f2dad7d734dd7535b97d563fb0952940a739ea94300ab2d34964 2807 
ruff_0.0.291+dfsg1-2.dsc
 8f76ce485638c2552ef9656e7efca38b588b685eb87269bb7c77d63770ed10f9 5980 
ruff_0.0.291+dfsg1-2.debian.tar.xz
 fe84e59dd52c14629df8f6fb7edf623304f0c3d9d621e1dd83920608d2d59dae 33066 
ruff_0.0.291+dfsg1-2_source.buildinfo
Files:
 9c94edc7ca07a64be4d4843bb3870bf8 2807 python optional ruff_0.0.291+dfsg1-2.dsc
 0f4e3e888b11c94c9a8c8f261f61cf94 5980 python optional 
ruff_0.0.291+dfsg1-2.debian.tar.xz
 3c364178c343f9f8dc2a019e864e3da5 33066 python optional 
ruff_0.0.291+dfsg1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEgIoEfJX3ae+y722SMG8hYYBCUGYFAmVLVoQACgkQMG8hYYBC
UGae4Af/dGbGUKMRMONO1EfF72olivE7oSDk4ndFhgVK7onLtK3a3y2pBfYI2bFr
pKNR/l3z1U3+UwJ6Anm0+SJSoiis/1VLlVfmzrtbrKqrsC+UCPCra9SVWQdAKavi
mYKarH3G/lnY38qeLgERc24mJDbeusHwzDZm/Y2s0cWb3uN0MHPSTxFSxselD/of
BoslMqH9Vu9tn8rG/SkieSaIXHPn8Z0wK42q81Brlm1SlXt1uL3d168vZMFBM1kw
B4nKlVjOvMQhmjUYYresmXxCcFvJdMM77Fc5OSu2PfUEr7aqBfjBjrDNo9CbxVv6
8G8KDaRGlGametLhNQOWdc7J2CtABw==
=Xv0V
-END PGP SIGNATURE End Message ---

Processed: Re: does not conform to the standards for library packaging

2023-11-08 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 important
Bug #1055237 [src:catch2] does not conform to the standards for library 
packaging
Severity set to 'important' from 'serious'

-- 
1055237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055237: does not conform to the standards for library packaging

2023-11-08 Thread Pierre Gruet


Control: severity -1 important

Hi,

Thanks Andrius for the advice given here.

On Wed, 8 Nov 2023 09:44:58 +0200 Andrius Merkys  wrote:
> Hello,
>
> On Thu, 02 Nov 2023 18:10:19 +0100 Pierre Gruet  wrote:
> > Recently catch2/3.4.0-1 was uploaded to Debian, great. Yet the 
binary packages
> > do not follow the layout for libraries that is described in Policy 
Section 8.
> > For instance I think we should provide a shared library and if 
there are enough
> > reasons not to do so (see Policy 8.3), at least the binary package 
name should

> > be changed to libcatch2-dev.
> >
> > Also this is not a header-only library anymore, the description of 
the package

> > should be changed.
>
> I agree, binary package could be renamed and descriptions should be
> adapted as well. I am not sure about shared library, though.
>
> First, upstream uses full source package version for soversion. This
> means a transition for even a patch level upstream release. I maintain a
> couple of packages like this and it is tiring.
>
> Second, I do not expect any real binary package depending on catch2
> shared library as only test objects are linked with it. But I may be
> wrong here.

This seems like a good reason to keep a static library, at least for the 
moment.


If there remains only the renaming of the package and its description to 
be changed, then downgrading the severity looks sensible.


>
> > As a side note, the upload of the major version 3.x came out with 
many breaking
> > interface changes giving rise to RC bugs in e.g. genomicsdb, 
netgen, spdlog,
> > therion just to name a few, also to failing autopkgtests in many 
rdeps. I would
> > have been more comfortable with such a huge version change being 
advertised and
> > more prepared, with some kind of a library transition process for 
instance.

>
> Right. Such changes should be announced beforehand since catch2 is used
> widely in the archive. Transition would have been nice indeed.

If you, Mathieu, have some insight into the best ways to transition 
reverse dependencies, I think giving it in the related bug reports would 
be very helpful.


>
> > In any case, thanks for your work on catch2,
>
> Seconded - thanks for maintaining this package.
>
> Best wishes,
> Andrius
>
>

Have a great day,

--
Pierre


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1052829: marked as done (parmed: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

2023-11-08 Thread Debian Bug Tracking System

Your message dated Wed, 08 Nov 2023 08:37:28 +
with message-id 
and subject line Bug#1052829: fixed in parmed 4.2.2+dfsg-1
has caused the Debian Bug report #1052829,
regarding parmed: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p 3.11 returned exit code 13
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1052829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: parmed
Version: 4.1.0+dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> === short test summary info 
> 
> FAILED test/test_openmm_amber.py::TestAmberParm::test_nbfix - 
> AssertionError:...
> = 1 failed, 843 passed, 70 skipped, 1 xfailed, 12027 warnings in 319.48s 
> (0:05:19) =
> E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/cpython3_3.11_parmed/build; python3.11 -m pytest 
> test
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 
> returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2023/09/25/parmed_4.1.0+dfsg-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: parmed
Source-Version: 4.2.2+dfsg-1
Done: Andrius Merkys 

We believe that the bug you reported is fixed in the latest version of
parmed, 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 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrius Merkys  (supplier of updated parmed 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: Wed, 08 Nov 2023 02:51:38 -0500
Source: parmed
Architecture: source
Version: 4.2.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Andrius Merkys 
Closes: 1052829
Changes:
 parmed (4.2.2+dfsg-1) unstable; urgency=medium
 .
   * New upstream release 4.2.2+dfsg (Closes: #1052829)
Checksums-Sha1:
 82e665a45c30f39ced876e1143df0a14509f754d 2336 parmed_4.2.2+dfsg-1.dsc
 6398b59c467ccca5bbbeab53a13358678842e900 48367212 parmed_4.2.2+dfsg.orig.tar.xz
 62c1b4658aaa9b7495f9e53d21b6078b93d1bfdb 7304 parmed_4.2.2+dfsg-1.debian.tar.xz
 1d37c67d693452d32a9fd5196f76f2fbce357039 9448 
parmed_4.2.2+dfsg-1_source.buildinfo
Checksums-Sha256:
 8d2ac3f2b7614a9365e3223af3bb6457535309f37a278cc085d9011da731a9dc 2336 
parmed_4.2.2+dfsg-1.dsc
 c55603d6009344c4162dc2bc92868f3c2c91857d8a087451f24a6bdd7a47184d 48367212 
parmed_4.2.2+dfsg.orig.tar.xz
 ed64cf71827c902b2ad1370507bd40f78843fa569a5c80c4f73b9f7319298735 7304 
parmed_4.2.2+dfsg-1.debian.tar.xz
 737f56c64ab64a5d63f701b1cf1dd5cfc7711f02d96eb6d8db3332d12bfe0228 9448 
parmed_4.2.2+dfsg-1_source.buildinfo
Files:
 ca70861a75ffa40c23d1722e65fb90bd 2336 science optional parmed_4.2.2+dfsg-1.dsc
 3ffcb5278586f208c107e663f44c1cbc 48367212 science optional 
parmed_4.2.2+dfsg.orig.tar.xz
 7a28bc6e610b92ab72e45b59c12aa241 7304 science optional 
parmed_4.2.2+dfsg-1.debian.tar.xz
 b9a867ddd58224f935b32c1d5d691e14 9448 science optional 
parmed_4.2.2+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmVLQ3cSHG1lcmt5c0Bk
ZWJpYW4ub3JnAAoJEOX0P5wnNPKHf+IP/1hdNXpyxLPHLtFQgpmq0B+d9DynMZie

Bug#1055514: opensysusers: ineffective diversion of /bin/systemd-sysusers due to /usr-merge and DEP17

2023-11-08 Thread Thomas Goirand


Hi Helmut,

Thanks for following-up in this bug, and thanks for your patience.

Helmut Grohne :
> The diversion setup bears a significant downside: While the API
> existing API of the sysusers interface is relatively stable, systemd
> keeps adding features and when systemd calls systemd-sysusers it wants
> to be able to rely on its latest features. A diverted systemd-sysusers
> may not provide what is needed here.

I've read this argument countless times. Here's my remarks.

If the API of this systemd component changes all the time, when it's 
supposed to be used by our packages, then we'd better avoid 
systemd-sysusers at all costs, and declare it as not useable in the long 
run, because constantly changing. This would be a strong case for using 
only opensysusers.


Lucky, that's as much as I know, *NOT* the case, and what you're 
describing is hopefully just FUD. If that's not, please be explicit 
explaining which part of the API of systemd-sysusers changed, or what 
feature was added: I'd be very curious to know, and it'd be nice to be 
able to add the missing feature in opensysusers.


If you cannot explain what's not stable in this API, or what feature was 
added recently that is missing from opensysusers, then I would strongly 
suggest stopping spreading this kind of fake news, and let other people 
re-implement parts of systemd if they feel like it.


If this is only a theoretical point, that systemd-sysusers *MAY* one day 
implement a new feature, then the thing that counts is if opensysusers 
is able to implement it as well, in a timely manner, to be able to stay 
compatible. If that's the case, then there's nothing to be afraid of.


So please care to explain...

That being said, I agree (and always did) that dpkg-divert was, and is 
(still) wrong, and should be replaced by a better solution. That was my 
point of view in the first place, and what I wrote to the tech-committee 
a few years ago.


> A possible compromise could be that opensysusers stops diverting
> systemd-sysusers and installs the symbolic link without diversion such
> that systemd becomes the preferred provider when coinstalled.

I don't understand why we're not then using update-alternatives. It has 
always been my idea to do so, and have systemd-sysuser having a higher 
priority over opensysusers... What's the blocker? You wrote it has 
issues with /usr-merge, why would it be the case, if we only do stuff in 
/usr/bin?


Andrea Pappacoda :
> since the upstream developers (i.e. the Artix Linux maintainers)
> stopped development in favour of systemd-standalone-sysusers[

I wouldn't be scared of upstream being gone in the case of opensysusers, 
as this is a quite simple component to maintain. Though it's entirely 
your call.




Cheers,

Thomas Goirand (zigo)

Processed: block 1055484 with 1055562

2023-11-08 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> block 1055484 with 1055562
Bug #1055484 [libpam-elogind-compat] libpam-elogind-compat has ineffective 
replaces for libpam-systemd due to /usr-merge
1055484 was not blocked by any bugs.
1055484 was blocking: 1055485
Added blocking bug(s) of 1055484: 1055562
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055484: libpam-elogind-compat has ineffective replaces for libpam-systemd due to /usr-merge

2023-11-08 Thread Mark Hindley

Control: block -1  1055562

Helmut,

On Tue, Nov 07, 2023 at 08:39:23AM +, Mark Hindley wrote:
> I think all suitable dependencies now use default-logind | logind. I will
> check that is correct. If it is, libpam-elogind-compat could just be
> removed. It was never available outside experimental.

AFAICS, all supported cases now use Depends: default-logind | logind or have
demoted the Depends to Recommends.

I have filed a RM request[1].

Mark

[1]  https://bugs.debian.org/1055562

55 matches

Mail list logo