Bug#1031447: marked as pending in ffmpeg

[Sebastian Ramacher]

Control: tag -1 pending

Hello,

Bug #1031447 in ffmpeg 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/multimedia-team/ffmpeg/-/commit/ad1140437d349749abfaec45ebb604642b9e81f2


Add upstream patch to fix FTBFS after vulkan changes

Closes: #1031447


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1031447

Processed: Bug#1031447 marked as pending in ffmpeg

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1031447 {Done: Sebastian Ramacher } [src:ffmpeg] 
ffmpeg: FTBFS: src/libavutil/hwcontext_vulkan.c:363:7: error: 
‘VK_EXT_VIDEO_DECODE_H264_EXTENSION_NAME’ undeclared here (not in a function); 
did you mean ‘VK_EXT_VIDEO_ENCODE_H264_EXTENSION_NAME’?
Added tag(s) pending.

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

Bug#1031447: marked as done (ffmpeg: FTBFS: src/libavutil/hwcontext_vulkan.c:363:7: error: ‘VK_EXT_VIDEO_DECODE_H264_EXTENSION_NAME’ undeclared here (not in a function); did you mean ‘VK_EXT_VIDEO_ENC

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2023 07:49:37 +
with message-id 
and subject line Bug#1031447: fixed in ffmpeg 7:5.1.2-3
has caused the Debian Bug report #1031447,
regarding ffmpeg: FTBFS: src/libavutil/hwcontext_vulkan.c:363:7: error: 
‘VK_EXT_VIDEO_DECODE_H264_EXTENSION_NAME’ undeclared here (not in a function); 
did you mean ‘VK_EXT_VIDEO_ENCODE_H264_EXTENSION_NAME’?
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.)


-- 
1031447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ffmpeg
Version: 7:5.1.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> gcc -I. -Isrc/ -Wdate-time -D_FORTIFY_SOURCE=2 -U_FORTIFY_SOURCE 
> -D_FORTIFY_SOURCE=2 -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC 
> -DZLIB_CONST -DHAVE_AV_CONFIG_H -DBUILDING_avutil -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-strict-overflow -fstack-protector-all -fPIE   
> -std=c11 -fomit-frame-pointer -fPIC -pthread  -I/usr/include/p11-kit-1  
> -I/usr/include/lilv-0 -I/usr/include/serd-0 -I/usr/include/sord-0 
> -I/usr/include/sratom-0 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/harfbuzz -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/fribidi 
> -I/usr/include/libxml2 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/bs2b-I/usr/include/libdrm -I/usr/include/freetype2 
> -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/fribidi  -DHWY_SHARED_DEFINE  -I/usr/include/mfx  
> -I/usr/include/openjpeg-2.5 -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/opus -I/usr/include/opus  -D_REENTRANT  -I/usr/include/rav1e  
> -I/usr/include/librsvg-2.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/x86_64-linux-gnu -pthread -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/srt 
> -I/usr/include/p11-kit-1 -I/usr/include/svt-av1 -DEB_DLL  
> -DX264_API_IMPORTS   -isystem /usr/include/mit-krb5 -I/usr/include/pgm-5.3 
> -I/usr/include/libxml2  -I/usr/include/libxml2  -I/usr/include/sphinxbase 
> -I/usr/include/pocketsphinx -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/x86_64-linux-gnu/sphinxbase-I/usr/include/libdrm 
> -g -Wdeclaration-after-statement -Wall -Wdisabled-optimization 
> -Wpointer-arith -Wredundant-decls -Wwrite-strings -Wtype-limits -Wundef 
> -Wmissing-prototypes -Wstrict-prototypes -Wempty-body -Wno-parentheses 
> -Wno-switch -Wno-format-zero-length -Wno-pointer-sign 
> -Wno-unused-const-variable -Wno-bool-operation -Wno-char-subscripts -O3 
> -fno-math-errno -fno-signed-zeros -fno-tree-vectorize -Werror=format-security 
> -Werror=implicit-function-declaration -Werror=missing-prototypes 
> -Werror=return-type -Werror=vla -Wformat -fdiagnostics-color=auto 
> -Wno-maybe-uninitialized -I/usr/include/SDL2 -D_REENTRANT   -MMD -MF 
> libavutil/imgutils.d -MT libavutil/imgutils.o -c -o libavutil/imgutils.o 
> src/libavutil/imgutils.c
> src/libavutil/hwcontext_vulkan.c:363:7: error: 
> ‘VK_EXT_VIDEO_DECODE_H264_EXTENSION_NAME’ undeclared here (not in a 
> function); did you mean ‘VK_EXT_VIDEO_ENCODE_H264_EXTENSION_NAME’?
>   363 | { VK_EXT_VIDEO_DECODE_H264_EXTENSION_NAME,
> FF_VK_EXT_NO_FLAG},
>   |   ^~~
>   |   VK_EXT_VIDEO_ENCODE_H264_EXTENSION_NAME
> src/libavutil/hwcontext_vulkan.c:364:7: error: 
> ‘VK_EXT_VIDEO_DECODE_H265_EXTENSION_NAME’ undeclared here (not in a 
> function); did you mean ‘VK_EXT_VIDEO_ENCODE_H265_EXTENSION_NAME’?
>   364 | { VK_EXT_VIDEO_DECODE_H265_EXTENSION_NAME,
> FF_VK_EXT_NO_FLAG},
>   |   ^~~
>   |   VK_EXT_VIDEO_ENCODE_H265_EXTENSION_NAME
> gcc -I. -Isrc/ -Wdate-time -D_FORTIFY_SOURCE=2 -U_FORTIFY_SOURCE 
> -D_FORTIFY_SOURCE=2 -D_ISOC99_SOURCE -D_FILE_O

Bug#1030697: libjs-bootstrap5: not co-installable with libjs-bootstrap4

[Damyan Ivanov]

Package: libjs-bootstrap5
Version: 5.2.3+dfsg-7
Followup-For: Bug #1030697

Control: found -1 5.2.3+dfsg-7

Still can't install the package with libjs-bootstrap4 installed:

 Preparing to unpack .../libjs-bootstrap5_5.2.3+dfsg-7_all.deb ...
 Unpacking libjs-bootstrap5 (5.2.3+dfsg-7) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libjs-bootstrap5_5.2.3+dfsg-7_all.deb (--unpack):
  trying to overwrite '/usr/share/nodejs/bootstrap/package.json', which is also 
in package libjs-bootstrap4 4.6.1+dfsg1-4
 Errors were encountered while processing:
  /var/cache/apt/archives/libjs-bootstrap5_5.2.3+dfsg-7_all.deb


-- Damyan

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-4-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libjs-bootstrap5 depends on:
ii  libjs-popper.js  1.16.1+ds-6

libjs-bootstrap5 recommends no packages.

Versions of packages libjs-bootstrap5 suggests:
ii  bootstrap-icons   1.10.3+dfsg-1
ii  libjs-bootstrap5-doc  5.2.3+dfsg-7

Processed: affects 1031486

[Debian Bug Tracking System]

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

> affects 1031486 ckeditor prettify.js jquery-i18n-properties dojo 
> datatables-extensions
Bug #1031486 [closure-compiler] ckeditor: FTBFS: make[1]: *** [debian/rules:24: 
debian/builddir/core/ckeditor_base.min.js] Error 254
Bug #1031452 [closure-compiler] prettify.js: FTBFS: 
java.util.MissingResourceException: Can't find bundle for base name 
com.google.javascript.rhino.head.resources.Messages, locale en
Bug #1031458 [closure-compiler] dojo: FTBFS: make[1]: *** [debian/rules:48: 
override_dh_auto_test] Error 1
Bug #1031470 [closure-compiler] jquery-i18n-properties: FTBFS: make[1]: *** 
[debian/rules:15: override_dh_auto_build] Error 254
Bug #1031474 [closure-compiler] datatables-extensions: FTBFS: make[1]: *** 
[debian/rules:10: override_dh_install] Error 254
Added indication that 1031486 affects ckeditor, prettify.js, 
jquery-i18n-properties, dojo, and datatables-extensions
Added indication that 1031452 affects ckeditor, prettify.js, 
jquery-i18n-properties, dojo, and datatables-extensions
Added indication that 1031458 affects ckeditor, prettify.js, 
jquery-i18n-properties, dojo, and datatables-extensions
Added indication that 1031470 affects ckeditor, prettify.js, 
jquery-i18n-properties, dojo, and datatables-extensions
Added indication that 1031474 affects ckeditor, prettify.js, 
jquery-i18n-properties, dojo, and datatables-extensions
> thanks
Stopping processing here.

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

Processed: reassign 1031432 to closure-compiler, affects 1031432

[Debian Bug Tracking System]

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

> reassign 1031432 closure-compiler
Bug #1031432 [src:mediaelement] mediaelement: FTBFS: FileNotFoundError: [Errno 
2] No such file or directory: '../build/mediaelement.min.js'
Bug reassigned from package 'src:mediaelement' to 'closure-compiler'.
No longer marked as found in versions mediaelement/2.15.1+dfsg-3.
Ignoring request to alter fixed versions of bug #1031432 to the same values 
previously set
> affects 1031432 mediaelement
Bug #1031432 [closure-compiler] mediaelement: FTBFS: FileNotFoundError: [Errno 
2] No such file or directory: '../build/mediaelement.min.js'
Added indication that 1031432 affects mediaelement
> thanks
Stopping processing here.

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

Processed: reassign 1031486 to closure-compiler, merging 1031486 1031452 1031470 1031458 1031474

[Debian Bug Tracking System]

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

> reassign 1031486 closure-compiler
Bug #1031486 [src:ckeditor] ckeditor: FTBFS: make[1]: *** [debian/rules:24: 
debian/builddir/core/ckeditor_base.min.js] Error 254
Bug reassigned from package 'src:ckeditor' to 'closure-compiler'.
No longer marked as found in versions ckeditor/4.19.1+dfsg-1.
Ignoring request to alter fixed versions of bug #1031486 to the same values 
previously set
> merge 1031486 1031452 1031470 1031458 1031474
Bug #1031486 [closure-compiler] ckeditor: FTBFS: make[1]: *** [debian/rules:24: 
debian/builddir/core/ckeditor_base.min.js] Error 254
Bug #1031452 [closure-compiler] prettify.js: FTBFS: 
java.util.MissingResourceException: Can't find bundle for base name 
com.google.javascript.rhino.head.resources.Messages, locale en
Bug #1031458 [closure-compiler] dojo: FTBFS: make[1]: *** [debian/rules:48: 
override_dh_auto_test] Error 1
Bug #1031470 [closure-compiler] jquery-i18n-properties: FTBFS: make[1]: *** 
[debian/rules:15: override_dh_auto_build] Error 254
Bug #1031474 [closure-compiler] datatables-extensions: FTBFS: make[1]: *** 
[debian/rules:10: override_dh_install] Error 254
Merged 1031452 1031458 1031470 1031474 1031486
> thanks
Stopping processing here.

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

Processed: Re: Bug#1031452: *: FTBFS: java.util.MissingResourceException: Can't find bundle for base name com.google.javascript.rhino.head.resources.Messages, locale en

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 closure-compiler
Bug #1031474 [src:datatables-extensions] datatables-extensions: FTBFS: make[1]: 
*** [debian/rules:10: override_dh_install] Error 254
Bug reassigned from package 'src:datatables-extensions' to 'closure-compiler'.
No longer marked as found in versions 
datatables-extensions/0.0+git20150910.28fd64e+dfsg-5.
Ignoring request to alter fixed versions of bug #1031474 to the same values 
previously set

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

Processed: Re: Bug#1031452: *: FTBFS: java.util.MissingResourceException: Can't find bundle for base name com.google.javascript.rhino.head.resources.Messages, locale en

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 closure-compiler
Bug #1031470 [src:jquery-i18n-properties] jquery-i18n-properties: FTBFS: 
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 254
Bug reassigned from package 'src:jquery-i18n-properties' to 'closure-compiler'.
No longer marked as found in versions jquery-i18n-properties/1.2.7+dfsg1-4.
Ignoring request to alter fixed versions of bug #1031470 to the same values 
previously set

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

Processed: Re: Bug#1031452: *: FTBFS: java.util.MissingResourceException: Can't find bundle for base name com.google.javascript.rhino.head.resources.Messages, locale en

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 closure-compiler
Bug #1031458 [src:dojo] dojo: FTBFS: make[1]: *** [debian/rules:48: 
override_dh_auto_test] Error 1
Bug reassigned from package 'src:dojo' to 'closure-compiler'.
No longer marked as found in versions dojo/1.17.2+dfsg1-2.
Ignoring request to alter fixed versions of bug #1031458 to the same values 
previously set

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

Bug#1031486: ckeditor: FTBFS: make[1]: *** [debian/rules:24: debian/builddir/core/ckeditor_base.min.js] Error 254

[Lucas Nussbaum]

Source: ckeditor
Version: 4.19.1+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir debian/builddir
> rsync -a . debian/builddir --exclude debian --exclude .git
> rm -f debian/builddir/ckeditor.js
> touch debian/builddir/build.stamp
> cd debian/builddir && closure-compiler --js core/ckeditor_base.js 
> --js_output_file core/ckeditor_base.min.js
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)
> make[1]: *** [debian/rules:24: debian/builddir/core/ckeditor_base.min.js] 
> Error 254


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/ckeditor_4.19.1+dfsg-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Processed: Re: Bug#1031452: *: FTBFS: java.util.MissingResourceException: Can't find bundle for base name com.google.javascript.rhino.head.resources.Messages, locale en

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 closure-compiler
Bug #1031452 [src:prettify.js] prettify.js: FTBFS: 
java.util.MissingResourceException: Can't find bundle for base name 
com.google.javascript.rhino.head.resources.Messages, locale en
Bug reassigned from package 'src:prettify.js' to 'closure-compiler'.
No longer marked as found in versions prettify.js/2015.12.04+dfsg-1.1.
Ignoring request to alter fixed versions of bug #1031452 to the same values 
previously set

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

Bug#1031487: devscripts: FTBFS: AssertionError: black found code that needs reformatting:

[Lucas Nussbaum]

Source: devscripts
Version: 2.23.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>/scripts'
> perl -I ../lib -c bts; \
> 
> perl -I ../lib -c build-rdeps; \
> 
> perl -I ../lib -c chdist; \
> 
> perl -I ../lib -c checkbashisms; \
> 
> perl -I ../lib -c cvs-debuild; \
> 
> perl -I ../lib -c dd-list; \
> 
> perl -I ../lib -c deb-why-removed; \
> 
> perl -I ../lib -c debc; \
> 
> cvs-debuild syntax OK
> perl -I ../lib -c debchange; \
> 
> build-rdeps syntax OK
> perl -I ../lib -c debcheckout; \
> 
> debc syntax OK
> perl -I ../lib -c debcommit; \
> 
> chdist syntax OK
> perl -I ../lib -c debdiff; \
> 
> deb-why-removed syntax OK
> perl -I ../lib -c debi; \
> 
> debcommit syntax OK
> perl -I ../lib -c debpkg; \
> 
> debchange syntax OK
> perl -I ../lib -c debrebuild; \
> 
> debpkg syntax OK
> perl -I ../lib -c debsnap; \
> 
> checkbashisms syntax OK
> perl -I ../lib -c debuild; \
> 
> debcheckout syntax OK
> perl -I ../lib -c dep3changelog; \
> 
> debdiff syntax OK
> debi syntax OK
> perl -I ../lib -c desktop2menu; \
> 
> perl -I ../lib -c dget; \
> 
> bts syntax OK
> perl -I ../lib -c dpkg-depcheck; \
> 
> dd-list syntax OK
> perl -I ../lib -c dscverify; \
> 
> dep3changelog syntax OK
> perl -I ../lib -c git-deborig; \
> 
> debsnap syntax OK
> perl -I ../lib -c grep-excuses; \
> 
> debuild syntax OK
> perl -I ../lib -c hardening-check; \
> 
> desktop2menu syntax OK
> perl -I ../lib -c mass-bug; \
> 
> grep-excuses syntax OK
> perl -I ../lib -c mk-build-deps; \
> 
> dget syntax OK
> dpkg-depcheck syntax OK
> perl -I ../lib -c mk-origtargz; \
> 
> mass-bug syntax OK
> perl -I ../lib -c namecheck; \
> 
> perl -I ../lib -c origtargz; \
> 
> dscverify syntax OK
> perl -I ../lib -c plotchangelog; \
> 
> hardening-check syntax OK
> perl -I ../lib -c rc-alert; \
> 
> git-deborig syntax OK
> perl -I ../lib -c rmadison; \
> 
> debrebuild syntax OK
> namecheck syntax OK
> perl -I ../lib -c salsa; \
> 
> perl -I ../lib -c svnpath; \
> 
> plotchangelog syntax OK
> perl -I ../lib -c tagpending; \
> 
> rmadison syntax OK
> perl -I ../lib -c transition-check; \
> 
> svnpath syntax OK
> perl -I ../lib -c uscan; \
> 
> origtargz syntax OK
> perl -I ../lib -c who-permits-upload; \
> 
> mk-build-deps syntax OK
> bash -n annotate-output
> bash -n archpath
> transition-check syntax OK
> bash -n cowpoke
> bash -n cvs-debi
> bash -n cvs-debrelease
> bash -n dcmd
> bash -n deb-reversion
> bash -n debclean
> bash -n debrelease
> bash -n debrepro
> bash -n debrsign
> bash -n debsign
> bash -n diff2patches
> bash -n dpkg-genbuilddeps
> bash -n dscextract
> bash -n edit-patch
> bash -n getbuildlog
> bash -n list-unreleased
> bash -n ltnu
> rc-alert syntax OK
> bash -n manpage-alert
> bash -n mergechanges
> tagpending syntax OK
> bash -n nmudiff
> bash -n pts-subscribe
> bash -n run_bisect
> bash -n run_bisect_qemu
> bash -n uupdate
> bash -n what-patch
> bash -n who-uploads
> bash -n whodepends
> bash -n wnpp-alert
> bash -n wnpp-check
> mk-origtargz syntax OK
> who-permits-upload syntax OK
> py3versions: no X-Python3-Version in control file, using supported versions
> python3.11 setup.py test
> salsa syntax OK
> uscan syntax OK
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> running egg_info
> creating devscripts.egg-info
> writing devscripts.egg-info/PKG-INFO
> writing dependency_links to devscripts.egg-info/dependency_links.txt
> writing top-level names to devscripts.egg-info/top_level.txt
> writing manifest file 'devscripts.egg-info/SOURCES.txt'
> reading manifest file 'devscripts.egg-info/SOURCES.txt'
> writing manifest file 'devscripts.egg-info/SOURCES.txt'
> running build_ext
> test_black (devscripts.test.test_black.BlackTestCase.test_black)
> Test: Run black code formatter on Python source code. ... Running following 
> command:
> black --check --diff debbisect debdiff-apply debootsnap deb-janitor 
> reproducible-check sadt suspicious-source wrap-and-sort devscripts setup.py
> FAIL
> test_flake8 (devscripts.test.test_flake8.Flake8TestCase.test_flake8)
> Test: Run flake8 on Python sou

Bug#1031452: *: FTBFS: java.util.MissingResourceException: Can't find bundle for base name com.google.javascript.rhino.head.resources.Messages, locale en

[Yadd]

Control: reassign -1 closure-compiler

On 2/17/23 10:49, Lucas Nussbaum wrote:

java.util.MissingResourceException: Can't find bundle for base name 
com.google.javascript.rhino.head.resources.Messages, locale en
at 
java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
at 
java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
at 
java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
at 
java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
at 
com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
at 
com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
at 
com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
at 
com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
at 
com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
at 
com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
at 
com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
at 
com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
at 
com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
at 
com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
at 
com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
at 
com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)


Same error displayed on 4 packages using closure-compiler, looks like a 
bug in closure-compiler itself

Bug#1031484: augur: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: augur
Version: 20.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/dates.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/frequencies.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/titer_model.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/__main__.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/errors.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/align.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/export.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/parse.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/refine.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/export_v1.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/argparse_.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/mask.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/clades.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/traits.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/sequence_traits.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/ancestral.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/index.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/tree.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/__version__.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/distance.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/validate_export.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/titers.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/translate.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/validate.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/filenames.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/export_v2.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/lbi.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/frequency_estimators.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/version.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/reconstruct_sequences.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/types.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/utils.py -> /<>/.pybuild/cpython3_3.11/build/augur
> creating /<>/.pybuild/cpython3_3.11/build/augur/filter
> copying augur/filter/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/filter
> copying augur/filter/include_exclude_rules.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/filter
> copying augur/filter/io.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/filter
> copying augur/filter/_run.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/filter
> copying augur/filter/subsample.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/filter
> copying augur/filter/validate_arguments.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/filter
> creating /<>/.pybuild/cpython3_3.11/build/augur/measurements
> copying augur/measurements/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/measurements
> copying augur/measurements/export.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/measurements
> copying augur/measurements/concat.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/measurements
> creating /<>/.pybuild/cpython3_3.11/build/augur/curate
> copying augur/curate/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/curate
> copying augur/curate/passthru.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/curate
> copying 

Bug#1031483: python-confluent-kafka: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: python-confluent-kafka
Version: 1.7.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>   pybuild --configure -i python{version} -p 3.11
> I: pybuild base:240: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
>   pybuild --build -i python{version} -p 3.11
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka
> copying src/confluent_kafka/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka
> copying src/confluent_kafka/serializing_producer.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka
> copying src/confluent_kafka/deserializing_consumer.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka
> copying src/confluent_kafka/error.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka
> creating 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/serialization
> copying src/confluent_kafka/serialization/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/serialization
> creating 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/admin
> copying src/confluent_kafka/admin/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/admin
> creating 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/avro
> copying src/confluent_kafka/avro/load.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/avro
> copying src/confluent_kafka/avro/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/avro
> copying src/confluent_kafka/avro/cached_schema_registry_client.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/avro
> copying src/confluent_kafka/avro/error.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/avro
> creating 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/schema_registry
> copying src/confluent_kafka/schema_registry/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/schema_registry
> copying src/confluent_kafka/schema_registry/protobuf.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/schema_registry
> copying src/confluent_kafka/schema_registry/schema_registry_client.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/schema_registry
> copying src/confluent_kafka/schema_registry/avro.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/schema_registry
> copying src/confluent_kafka/schema_registry/json_schema.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/schema_registry
> copying src/confluent_kafka/schema_registry/error.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/schema_registry
> creating 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/kafkatest
> copying src/confluent_kafka/kafkatest/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/kafkatest
> copying src/confluent_kafka/kafkatest/verifiable_consumer.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/kafkatest
> copying src/confluent_kafka/kafkatest/verifiable_producer.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/kafkatest
> copying src/confluent_kafka/kafkatest/verifiable_client.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/kafkatest
> creating 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/avro/serializer
> copying src/confluent_kafka/avro/serializer/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/avro/serializer
> copying src/confluent_kafka/avro/serializer/message_serializer.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/avro/serializer
> running build_ext
> building 'confluent_kafka.cimpl' extension
> creating build
> creating build/tem

Bug#1031477: python-oslo.concurrency: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpxztykbsm/tmpyb1wyys0/file-0'

[Lucas Nussbaum]

Source: python-oslo.concurrency
Version: 5.0.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_install --no-py2 --in-tmp
> + PKGOS_IN_TMP=no
> + echo WARNING: --no-py2 is deprecated and always on.
> WARNING: --no-py2 is deprecated and always on.
> + shift
> + PKGOS_IN_TMP=yes
> + shift
> + dpkg-parsechangelog -SSource
> + SRC_PKG_NAME=python-oslo.concurrency
> + echo python-oslo.concurrency
> + sed s/python-//
> + PY_MODULE_NAME=oslo.concurrency
> + py3versions -vr
> + PYTHON3S=3.11
> + [ yes = yes ]
> + TARGET_DIR=tmp
> + pwd
> + python3.11 setup.py install --install-layout=deb --root 
> /<>/debian/tmp
> /usr/lib/python3/dist-packages/setuptools/command/easy_install.py:146: 
> EasyInstallDeprecationWarning: easy_install command is deprecated. Use build 
> and pip and other standards-based tools.
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and 
> pip and other standards-based tools.
>   warnings.warn(
> running install
> [pbr] Generating AUTHORS
> [pbr] AUTHORS complete (0.0s)
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/oslo_concurrency
> creating build/lib/oslo_concurrency/fixture
> copying oslo_concurrency/fixture/__init__.py -> 
> build/lib/oslo_concurrency/fixture
> copying oslo_concurrency/fixture/lockutils.py -> 
> build/lib/oslo_concurrency/fixture
> creating build/lib/oslo_concurrency/tests
> creating build/lib/oslo_concurrency/tests/unit
> copying oslo_concurrency/tests/unit/__init__.py -> 
> build/lib/oslo_concurrency/tests/unit
> copying oslo_concurrency/tests/unit/test_lockutils.py -> 
> build/lib/oslo_concurrency/tests/unit
> copying oslo_concurrency/tests/unit/test_lockutils_eventlet.py -> 
> build/lib/oslo_concurrency/tests/unit
> copying oslo_concurrency/tests/unit/test_processutils.py -> 
> build/lib/oslo_concurrency/tests/unit
> copying oslo_concurrency/tests/__init__.py -> build/lib/oslo_concurrency/tests
> copying oslo_concurrency/__init__.py -> build/lib/oslo_concurrency
> copying oslo_concurrency/lockutils.py -> build/lib/oslo_concurrency
> copying oslo_concurrency/prlimit.py -> build/lib/oslo_concurrency
> copying oslo_concurrency/opts.py -> build/lib/oslo_concurrency
> copying oslo_concurrency/processutils.py -> build/lib/oslo_concurrency
> copying oslo_concurrency/_i18n.py -> build/lib/oslo_concurrency
> copying oslo_concurrency/watchdog.py -> build/lib/oslo_concurrency
> copying oslo_concurrency/version.py -> build/lib/oslo_concurrency
> running egg_info
> creating oslo.concurrency.egg-info
> writing oslo.concurrency.egg-info/PKG-INFO
> writing dependency_links to oslo.concurrency.egg-info/dependency_links.txt
> writing entry points to oslo.concurrency.egg-info/entry_points.txt
> writing requirements to oslo.concurrency.egg-info/requires.txt
> writing top-level names to oslo.concurrency.egg-info/top_level.txt
> [pbr] Processing SOURCES.txt
> writing manifest file 'oslo.concurrency.egg-info/SOURCES.txt'
> warning: no files found matching 'AUTHORS'
> warning: no files found matching 'ChangeLog'
> warning: no previously-included files found matching '.gitignore'
> warning: no previously-included files found matching '.gitreview'
> warning: no previously-included files matching '*.pyc' found anywhere in 
> distribution
> adding license file 'LICENSE'
> writing manifest file 'oslo.concurrency.egg-info/SOURCES.txt'
> running install_lib
> creating /<>/debian/tmp
> creating /<>/debian/tmp/usr
> creating /<>/debian/tmp/usr/lib
> creating /<>/debian/tmp/usr/lib/python3
> creating /<>/debian/tmp/usr/lib/python3/dist-packages
> creating 
> /<>/debian/tmp/usr/lib/python3/dist-packages/oslo_concurrency
> copying build/lib/oslo_concurrency/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/oslo_concurrency
> copying build/lib/oslo_concurrency/lockutils.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/oslo_concurrency
> copying build/lib/oslo_concurrency/prlimit.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/oslo_concurrency
> copying build/lib/oslo_concurrency/opts.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/oslo_concurre

Bug#1031482: soundmanager2: FTBFS: make[1]: *** [debian/rules:8: override_dh_auto_build] Error 25

[Lucas Nussbaum]

Source: soundmanager2
Version: 2.97a.20150601+dfsg2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -- \
>   -Dmtasc=/bin/true \
>   -Dmxmlc=/bin/true \
>   -Dclosure-compiler.jar=/usr/share/java/closure-compiler.jar
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
>   ant -Duser.name debian -Dmtasc=/bin/true -Dmxmlc=/bin/true 
> -Dclosure-compiler.jar=/usr/share/java/closure-compiler.jar
> Buildfile: /<>/build.xml
>  [echo] /usr/share/java/closure-compiler.jar
> 
> build:
>  [echo] Removing existing JS builds...
>  [echo] Compressing minified JS...
> [mkdir] Created dir: /<>/tmp
> 
> BUILD FAILED
> /<>/build.xml:75: java.util.MissingResourceException: Can't find 
> bundle for base name com.google.javascript.rhino.head.resources.Messages, 
> locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:237)
>   at 
> com.google.javascript.jscomp.ant.CompileTask.createCompiler(CompileTask.java:459)
>   at 
> com.google.javascript.jscomp.ant.CompileTask.execute(CompileTask.java:283)
>   at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:299)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.base/java.lang.reflect.Method.invoke(Method.java:568)
>   at 
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
>   at org.apache.tools.ant.Task.perform(Task.java:350)
>   at org.apache.tools.ant.Target.execute(Target.java:449)
>   at org.apache.tools.ant.Target.performTasks(Target.java:470)
>   at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401)
>   at org.apache.tools.ant.Project.executeTarget(Project.java:1374)
>   at 
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>   at org.apache.tools.ant.Project.executeTargets(Project.java:1264)
>   at org.apache.tools.ant.Main.runBuild(Main.java:818)
>   at org.apache.tools.ant.Main.startAnt(Main.java:223)
>   at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
>   at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)
> 
> Total time: 0 seconds
> dh_auto_build: error: ant -Duser.name debian -Dmtasc=/bin/true 
> -Dmxmlc=/bin/true -Dclosure-compiler.jar=/usr/share/java/closure-compiler.jar 
> returned exit code 1
> make[1]: *** [debian/rules:8: override_dh_auto_build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/soundmanager2_2.97a.20150601+dfsg2-2_unstable.log

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

A list of current common problems and possible solutions

Bug#1031481: python-oslo.db: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

Source: python-oslo.db
Version: 12.1.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> oslo_db.tests.test_api.DBRetryRequestCase.test_retry_wrapper_succeeds
> oslo_db.tests.test_api.DBRetryRequestCase.test_retry_wrapper_succeeds ... ok
> oslo_db.tests.test_api.DBRetryRequestCase.test_wrap_db_retry_get_interval
> oslo_db.tests.test_api.DBRetryRequestCase.test_wrap_db_retry_get_interval ... 
> ok
> oslo_db.tests.test_concurrency.TpoolDbapiWrapperTestCase.test_db_api_common
> oslo_db.tests.test_concurrency.TpoolDbapiWrapperTestCase.test_db_api_common 
> ... ok
> oslo_db.tests.test_concurrency.TpoolDbapiWrapperTestCase.test_db_api_config_change
> oslo_db.tests.test_concurrency.TpoolDbapiWrapperTestCase.test_db_api_config_change
>  ... ok
>ERROR [oslo_db.concurrency] 'eventlet' is required for TpoolDbapiWrapper.
> Traceback (most recent call last):
>   File "/<>/oslo_db/concurrency.py", line 78, in _api
> from eventlet import tpool
> ModuleNotFoundError: import of eventlet halted; None in sys.modules
> oslo_db.tests.test_concurrency.TpoolDbapiWrapperTestCase.test_db_api_without_installed_eventlet
> oslo_db.tests.test_concurrency.TpoolDbapiWrapperTestCase.test_db_api_without_installed_eventlet
>  ... ok
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/python-oslo.db_12.1.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031480: libreflectasm-java: FTBFS: make: *** [debian/rules:4: binary] Error 25

[Lucas Nussbaum]

Source: libreflectasm-java
Version: 1.11.9+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with javahelper
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibreflectasm-java --debian-build --keep-pom-version 
> --maven-repo=/<>/libreflectasm-java-1.11.9\+dfsg/debian/maven-repo
>jh_linkjars
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<>/libreflectasm-java-1.11.9\+dfsg
>  -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml 
> -Ddebian.dir=/<>/libreflectasm-java-1.11.9\+dfsg/debian 
> -Dmaven.repo.local=/<>/libreflectasm-java-1.11.9\+dfsg/debian/maven-repo
>  --batch-mode package javadoc:jar javadoc:aggregate -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] --< com.esotericsoftware:reflectasm 
> >---
> [INFO] Building ReflectASM 1.11.9
> [INFO] ---[ bundle 
> ]---
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.10.1:compile (default-compile) @ 
> reflectasm ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 5 source files to /<>/target/classes
> Use of target 1.5 is no longer supported, switching to 7
> Use of source 1.5 is no longer supported, switching to 7
> [INFO] 
> /<>/src/com/esotericsoftware/reflectasm/ConstructorAccess.java: 
> Some input files use or override a deprecated API.
> [INFO] 
> /<>/src/com/esotericsoftware/reflectasm/ConstructorAccess.java: 
> Recompile with -Xlint:deprecation for details.
> [INFO] 
> /<>/src/com/esotericsoftware/reflectasm/AccessClassLoader.java: 
> Some input files use unchecked or unsafe operations.
> [INFO] 
> /<>/src/com/esotericsoftware/reflectasm/AccessClassLoader.java: 
> Recompile with -Xlint:unchecked for details.
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.10.1:testCompile (default-testCompile) @ 
> reflectasm ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 8 source files to /<>/target/test-classes
> Use of target 1.5 is no longer supported, switching to 7
> Use of source 1.5 is no longer supported, switching to 7
> [INFO] 
> /<>/test/com/esotericsoftware/reflectasm/MethodAccessTest.java: 
> Some input files use or override a deprecated API.
> [INFO] 
> /<>/test/com/esotericsoftware/reflectasm/MethodAccessTest.java: 
> Recompile with -Xlint:deprecation for details.
> [INFO] 
> /<>/test/com/esotericsoftware/reflectasm/benchmark/Benchmark.java:
>  Some input files use unchecked or unsafe operations.
> [INFO] 
> /<>/test/com/esotericsoftware/reflectasm/benchmark/Benchmark.java:
>  Recompile with -Xlint:unchecked for details.
> [INFO] 
> [INFO] --- maven-surefire-plugin:2.22.3:test (default-test) @ reflectasm ---
> [INFO] Tests are skipped.
> [INFO] 
> [INFO] --- maven-bundle-plugin:3.5.1:bundle (default-bundle) @ reflectasm ---
> [INFO] 
> [INFO] --- maven-javadoc-plugin:3.4.1:jar (default-cli) @ reflectasm ---
> [INFO] Adding the --ignore-source-errors option
> [INFO] No previous run data found, generating javadoc.
> [INFO] Building jar: /<>/target/reflectasm-1.11.9-javadoc.jar
> [INFO] 
> [INFO] --< com.esotericsoftware:reflectasm 
> >---
> [INFO] Building ReflectASM 1.11.9
> [INFO] ---[ bundle 
> ]---
> [INFO] 
> [INFO] >>> maven-javadoc-plugin:3.4.1:aggregate (default-cli) > compile @ 
> reflectasm >>>
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.10.1:compile (default-compile) @ 
> reflectasm ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 5 source files to /<>/target/classes
> Use of target 1.5 is no longer supported, switching to 7
> Use of source 1.5 is no longer supported, switching to 7
> [INFO] 
> /<>/src/com/esotericsoftware/reflectasm/ConstructorAccess.java: 
> Some input files use or override a deprecated API.
> [INFO] 
> /<>/src/com/esoter

Bug#1031479: ruby-eye: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'celluloid' (~> 0.16.

[Lucas Nussbaum]

Source: ruby-eye
Version: 0.7-5.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block 
> in activate_dependencies': Could not find 'celluloid' (~> 0.16.0) among 108 
> total gem(s) (Gem::MissingSpecError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-eye/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0'
>  at: 
> /<>/debian/ruby-eye/usr/share/rubygems-integration/all/specifications/eye-0.7.gemspec,
>  execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not 
> find 'celluloid' (~> 0.16.0) - did find: [celluloid-0.18.0] 
> (Gem::MissingSpecVersionError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-eye/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0'
>  , execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> abbrev (default: 0.1.0)
> base64 (default: 0.1.1)
> benchmark (default: 0.2.0)
> bigdecimal (default: 3.1.1)
> bundler (2.3.15, default: 2.3.7)
> celluloid (0.18.0)
> celluloid-essentials (0.20.5)
> celluloid-extras (0.20.5)
> celluloid-fsm (0.20.5)
> celluloid-io (0.16.2)
> celluloid-pool (0.20.5)
> celluloid-supervision (0.20.5)
> cgi (default: 0.3.5)
> csv (default: 3.2.2)
> date (default: 3.2.2)
> debug (1.4.0)
> delegate (default: 0.2.0)
> did_you_mean (default: 1.6.1)
> digest (default: 3.1.0)
> dotenv (2.4.0)
> drb (default: 2.1.0)
> english (default: 0.7.1)
> erb (default: 2.2.3)
> error_highlight (default: 0.3.0)
> etc (default: 1.3.0)
> fcntl (default: 1.0.1)
> fiddle (default: 1.1.0)
> fileutils (default: 1.6.0)
> find (default: 0.1.1)
> forwardable (default: 1.3.2)
> getoptlong (default: 0.1.1)
> hitimes (1.3.1)
> io-console (default: 0.5.11)
> io-nonblock (default: 0.1.0)
> io-wait (default: 0.2.1)
> ipaddr (default: 1.2.4)
> irb (default: 1.4.1)
> json (default: 2.6.1)
> logger (default: 1.5.0)
> matrix (0.4.2)
> minitest (5.15.0)
> mutex_m (default: 0.1.1)
> nenv (0.3.0)
> net-ftp (0.1.3)
> net-http (default: 0.2.0)
> net-imap (0.2.3)
> net-pop (0.1.1)
> net-protocol (default: 0.1.2)
> net-smtp (0.3.1)
> net-telnet (0.2.0)
> nio4r (2.5.8)
> nkf (default: 0.1.1)
> observer (default: 0.1.1)
> open-uri (default: 0.2.0)
> open3 (default: 0.1.1)
> openssl (default: 3.0.0)
> optparse (default: 0.2.0)
> ostruct (default: 0.5.2)
> pathname (default: 0.2.0)
> power_assert (2.0.1)
> pp (default: 0.3.0)
> prettyprint (default: 0.1.1)
> prime (0.1.2)
> pstore (default: 0.1.1)
> psych (default: 4.0.3)
> racc (default: 1.6.0)
> rake (13.0.6)
> rbs (2.1.0)
> rdoc (default: 6.4.0)
> readline (default: 0.0.3)
> readline-ext (default: 0.1.4)
> reline (default: 0.3

Bug#1031478: nrepl-clojure: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

Source: nrepl-clojure
Version: 1.0.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> Clojure 1.11.1
> OpenJDK 64-Bit Server VM 17.0.6+10-Debian-1
> Interrupt: Control+C
> Exit:  Control+D or (exit) or (quit)
> 
> lein test nrepl.cmdline-tty-test
> 
> lein test nrepl.core-test
> 
> lein test :only nrepl.core-test/dynamic-middleware+sideloading-interleaved
> 
> FAIL in (dynamic-middleware+sideloading-interleaved) (core_test.clj:1066)
> bencode transport sideloader state persists across middleware changes
> expected: (= [:added-middleware :provided-ns :provided-ns [:eval-ok 
> "\"Hello!\""]] (reduce (fn [result {:keys [id status type name value], :as 
> msg}] (cond (status? :unexpected-provide status) (throw (ex-info "Unexpected 
> provide" msg)) (and (= name (str "foo/" ns ".clj")) (status? 
> :sideloader-lookup status) (not (some #{:added-middleware} result))) (do 
> (send {:id 3, :op "add-middleware", :session sl-session, :middleware []}) 
> (conj result :added-middleware)) (or (and (= 3 id) (status? :done status)) 
> (and (= name (str "foo/" ns ".clj")) (status? :sideloader-lookup status))) 
> (do (send {:session sl-session, :id 1, :op "sideloader-provide", :content 
> (string->content (str "(prn 'xx) (ns foo." ns ") (prn 'yy) (defn hello [] 
> \"Hello!\")")), :type "resource", :name (str "foo/" ns ".clj")}) (conj result 
> :provided-ns)) (status? :sideloader-lookup status) (do (send {:session 
> sl-session, :id 1, :op "sideloader-provide", :content "", :type type, :name 
> name}) result) (and (= 2 id) (status? :done status)) (do (send {:id 4, :op 
> "eval", :session sl-session, :code (str "(foo." ns "/hello)")}) result) (and 
> (= 4 id) value) (conj result [:eval-ok value]) (and (= 4 id) (status? :done 
> status)) (reduced result) :else result)) [] res))
>   actual: (not (= [:added-middleware :provided-ns :provided-ns [:eval-ok 
> "\"Hello!\""]] []))
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/nrepl-clojure_1.0.0-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031474: datatables-extensions: FTBFS: make[1]: *** [debian/rules:10: override_dh_install] Error 254

[Lucas Nussbaum]

Source: datatables-extensions
Version: 0.0+git20150910.28fd64e+dfsg-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install
> for min in `find debian -name "*.min.js"` ; do \
> closure-compiler --language_in ECMASCRIPT5 --charset 'utf-8' --js `echo 
> ${min} | sed 's/\.min//'` --js_output_file ${min} ; \
> done
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.

Bug#1031476: ruby-celluloid-io: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error:

[Lucas Nussbaum]

Source: ruby-celluloid-io
Version: 0.16.2-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> Failure/Error:
>   class Mailbox < Celluloid::EventedMailbox
> def initialize
>   super(Reactor)
> end
> 
> NameError:
>   uninitialized constant Celluloid::EventedMailbox
> 
>   class Mailbox < Celluloid::EventedMailbox
>
> # ./lib/celluloid/io/mailbox.rb:4:in `'
> # ./lib/celluloid/io/mailbox.rb:2:in `'
> # ./lib/celluloid/io/mailbox.rb:1:in `'
> # ./lib/celluloid/io.rb:5:in `'
> # ./spec/spec_helper.rb:1:in `'
> # ./spec/celluloid/io_spec.rb:1:in `'
> # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/configuration.rb:2117:in
>  `load'
> # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/configuration.rb:2117:in
>  `load_file_handling_errors'
> # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/configuration.rb:1617:in
>  `block in load_spec_files'
> # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/configuration.rb:1615:in
>  `each'
> # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/configuration.rb:1615:in
>  `load_spec_files'
> # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/runner.rb:102:in
>  `setup'
> # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/runner.rb:86:in
>  `run'
> # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/runner.rb:71:in
>  `run'
> # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/runner.rb:45:in
>  `invoke'
> # /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec:4:in 
> `'
> No examples found.
> 
> Finished in 0.4 seconds (files took 0.1943 seconds to load)
> 0 examples, 0 failures, 8 errors occurred outside of examples
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> ./spec/celluloid/io/actor_spec.rb ./spec/celluloid/io/dns_resolver_spec.rb 
> ./spec/celluloid/io/ssl_server_spec.rb ./spec/celluloid/io/ssl_socket_spec.rb 
> ./spec/celluloid/io/tcp_server_spec.rb ./spec/celluloid/io/udp_socket_spec.rb 
> ./spec/celluloid/io/unix_server_spec.rb ./spec/celluloid/io_spec.rb --format 
> documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/ruby-celluloid-io_0.16.2-5_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031475: conda-package-streaming: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: conda-package-streaming
Version: 0.7.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:107: Building wheel for python3.11 with "build" 
> module
> I: pybuild base:240: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.11 
> * Building wheel...
> Successfully built conda_package_streaming-0.7.0-py3-none-any.whl
> I: pybuild plugin_pyproject:119: Unpacking wheel built for python3.11 with 
> "installer" module
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; 
> python3.11 -m pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack
> rootdir: /<>, configfile: pyproject.toml
> plugins: mock-3.8.2, cov-4.0.0
> collected 15 items / 1 error
> 
>  ERRORS 
> 
>  ERROR collecting .pybuild/cpython3_3.11/build/tests/test_transmute.py 
> _
> ImportError while importing test module 
> '/<>/.pybuild/cpython3_3.11/build/tests/test_transmute.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/test_transmute.py:14: in 
> from conda_package_streaming.transmute import transmute, transmute_tar_bz2
> conda_package_streaming/transmute.py:23: in 
> import zstandard
> /usr/lib/python3/dist-packages/zstandard/__init__.py:39: in 
> from .backend_c import *  # type: ignore
> E   ImportError: zstd C API versions mismatch; Python bindings were not 
> compiled/linked against expected zstd version (10504 returned by the lib, 
> 10502 hardcoded in zstd headers, 10502 hardcoded in the cext)
> === warnings summary 
> ===
> ../../../../../../usr/lib/python3/dist-packages/bottle.py:38
>   /usr/lib/python3/dist-packages/bottle.py:38: DeprecationWarning: 'cgi' is 
> deprecated and slated for removal in Python 3.13
> import base64, cgi, email.utils, functools, hmac, itertools, mimetypes,\
> 
> conda_package_streaming/package_streaming.py:19
>   
> /<>/.pybuild/cpython3_3.11/build/conda_package_streaming/package_streaming.py:19:
>  UserWarning: zstandard could not be imported. Running without .conda support.
> warnings.warn("zstandard could not be imported. Running without .conda 
> support.")
> 
> -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
> 
> -- coverage: platform linux, python 3.11.2-final-0 ---
> Name   Stmts   Miss  Cover
> --
> conda_package_streaming/__init__.py1  0   100%
> conda_package_streaming/exceptions.py  9  456%
> conda_package_streaming/extract.py42 3224%
> conda_package_streaming/lazy_wheel.py131 9131%
> conda_package_streaming/package_streaming.py  47 2547%
> conda_package_streaming/s3.py 39 1854%
> conda_package_streaming/transmute.py  52 4415%
> conda_package_streaming/url.py39 2536%
> --
> TOTAL36023934%
> 
> === short test summary info 
> 
> ERROR tests/test_transmute.py
>  Interrupted: 1 error during collection 
> 
> = 2 warnings, 1 error in 0.37s 
> =
> E: pybuild pybuild:388: test: plugin pyproject failed with: exit code=2: cd 
> /<>/.pybuild/cpython3_3.11/build; python3.11 -m pytest tests
> 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/02/16/conda-package-streaming_0.7.0-4_unstable.log

All

Bug#1031472: ruby-omniauth-facebook: FTBFS: ERROR: Test "ruby3.1" failed.

[Lucas Nussbaum]

Source: ruby-omniauth-facebook
Version: 4.0.0-2.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-omniauth-facebook/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -e gem\ \"omniauth-facebook\"
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rb 
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-omniauth-facebook/usr/lib/ruby/vendor_ruby:.
>  
> GEM_PATH=/<>/debian/ruby-omniauth-facebook/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 debian/ruby-tests.rb
> mv example/Gemfile.lock example/.gem2deb.Gemfile.lock
> Mocha deprecation warning at 
> :160:in
>  `require': Require 'mocha/test_unit', 'mocha/minitest' or 'mocha/api' 
> instead of 'mocha/setup'.
> Run options: --seed 19466
> 
> # Running:
> 
> EE...E..DEPRECATED: Use assert_nil if expecting nil 
> from /<>/test/strategy_test.rb:455. This will fail in Minitest 6.
> .EE.E
> 
> Finished in 0.091243s, 800.0599 runs/s, 1183.6503 assertions/s.
> 
>   1) Error:
> SignedRequestTests::CookiePresentTest#test_parses_the_access_code_out_from_the_cookie:
> NameError: uninitialized constant SignedRequestHelpers::MultiJson
> 
> encoded_payload = base64_encode_url(MultiJson.encode(payload))
> ^
> Did you mean?  MultiXml
> /<>/test/strategy_test.rb:396:in `signed_request'
> /<>/test/strategy_test.rb:435:in `setup'
> 
>   2) Error:
> SignedRequestTests::CookiePresentTest#test_throws_an_error_if_the_algorithm_is_unknown:
> NameError: uninitialized constant SignedRequestHelpers::MultiJson
> 
> encoded_payload = base64_encode_url(MultiJson.encode(payload))
> ^
> Did you mean?  MultiXml
> /<>/test/strategy_test.rb:396:in `signed_request'
> /<>/test/strategy_test.rb:435:in `setup'
> 
>   3) Error:
> SignedRequestTests::MissingCodeInCookieRequestTest#test_calls_fail!_when_a_code_is_not_included_in_the_cookie:
> NameError: uninitialized constant SignedRequestHelpers::MultiJson
> 
> encoded_payload = base64_encode_url(MultiJson.encode(payload))
> ^
> Did you mean?  MultiXml
> /<>/test/strategy_test.rb:396:in `signed_request'
> /<>/test/strategy_test.rb:481:in `setup'
> 
>   4) Error:
> SignedRequestTest#test_signed_request_parse:
> NameError: uninitialized constant SignedRequestTest::MultiJson
> 
> @expected_payload = MultiJson.decode(fixture('payload.json'))
> ^
> Did you mean?  MultiXml
> /<>/test/signed_request_test.rb:8:in `setup'
> 
>   5) Error:
> SignedRequestTest#test_signed_request_payload:
> NameError: uninitialized constant SignedRequestTest::MultiJson
> 
> @expected_payload = MultiJson.decode(fixture('payload.json'))
> ^
> Did you mean?  MultiXml
> /<>/test/signed_request_test.rb:8:in `setup'
> 
>   6) Error:
> SignedRequestTests::UnknownAlgorithmInCookieRequestTest#test_calls_fail!_when_an_algorithm_is_unknown:
> NameError: uninitialized constant SignedRequestHelpers::MultiJson
> 
> encoded_payload = base64_encode_url(MultiJson.encode(payload))
> ^
> Did you mean?  MultiXml
> /<>/test/strategy_test.rb:396:in `signed_request'
> /<>/test/strategy_test.rb:500:in `setup'
> 
> 73 runs, 108 assertions, 0 failures, 6 errors, 0 skips
> mv example/.gem2deb.

Bug#1031473: freebayes: FTBFS: Variant.h:36:10: fatal error: wavefront/wfa.hpp: No such file or directory

[Lucas Nussbaum]

Source: freebayes
Version: 1.3.6-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> c++ -Ilibfreebayes_common.a.p -I. -I.. -I../src -I../ttmath 
> -I/usr/include/vcflib -I/usr/include/smithwaterman -I/usr/include/fastahack 
> -I/usr/include/SeqLib -I/usr/include/jsoncpp -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c++14 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
> -fpermissive -Wno-reorder -Wno-sign-compare -Wno-unused-variable 
> -Wno-unused-but-set-variable -MD -MQ 
> libfreebayes_common.a.p/src_DataLikelihood.cpp.o -MF 
> libfreebayes_common.a.p/src_DataLikelihood.cpp.o.d -o 
> libfreebayes_common.a.p/src_DataLikelihood.cpp.o -c ../src/DataLikelihood.cpp
> In file included from ../src/AlleleParser.h:32,
>  from ../src/DataLikelihood.h:20,
>  from ../src/DataLikelihood.cpp:1:
> /usr/include/vcflib/Variant.h:36:10: fatal error: wavefront/wfa.hpp: No such 
> file or directory
>36 | #include "wavefront/wfa.hpp"
>   |  ^~~
> compilation terminated.
> [2/27] c++ -Ilibfreebayes_common.a.p -I. -I.. -I../src -I../ttmath 
> -I/usr/include/vcflib -I/usr/include/smithwaterman -I/usr/include/fastahack 
> -I/usr/include/SeqLib -I/usr/include/jsoncpp -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c++14 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
> -fpermissive -Wno-reorder -Wno-sign-compare -Wno-unused-variable 
> -Wno-unused-but-set-variable -MD -MQ 
> libfreebayes_common.a.p/src_AlleleParser.cpp.o -MF 
> libfreebayes_common.a.p/src_AlleleParser.cpp.o.d -o 
> libfreebayes_common.a.p/src_AlleleParser.cpp.o -c ../src/AlleleParser.cpp
> FAILED: libfreebayes_common.a.p/src_AlleleParser.cpp.o 
> c++ -Ilibfreebayes_common.a.p -I. -I.. -I../src -I../ttmath 
> -I/usr/include/vcflib -I/usr/include/smithwaterman -I/usr/include/fastahack 
> -I/usr/include/SeqLib -I/usr/include/jsoncpp -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c++14 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
> -fpermissive -Wno-reorder -Wno-sign-compare -Wno-unused-variable 
> -Wno-unused-but-set-variable -MD -MQ 
> libfreebayes_common.a.p/src_AlleleParser.cpp.o -MF 
> libfreebayes_common.a.p/src_AlleleParser.cpp.o.d -o 
> libfreebayes_common.a.p/src_AlleleParser.cpp.o -c ../src/AlleleParser.cpp
> In file included from ../src/AlleleParser.h:32,
>  from ../src/AlleleParser.cpp:1:
> /usr/include/vcflib/Variant.h:36:10: fatal error: wavefront/wfa.hpp: No such 
> file or directory
>36 | #include "wavefront/wfa.hpp"
>   |  ^~~
> compilation terminated.
> [3/27] c++ -Ilibfreebayes_common.a.p -I. -I.. -I../src -I../ttmath 
> -I/usr/include/vcflib -I/usr/include/smithwaterman -I/usr/include/fastahack 
> -I/usr/include/SeqLib -I/usr/include/jsoncpp -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c++14 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
> -fpermissive -Wno-reorder -Wno-sign-compare -Wno-unused-variable 
> -Wno-unused-but-set-variable -MD -MQ 
> libfreebayes_common.a.p/src_Contamination.cpp.o -MF 
> libfreebayes_common.a.p/src_Contamination.cpp.o.d -o 
> libfreebayes_common.a.p/src_Contamination.cpp.o -c ../src/Contamination.cpp
> [4/27] c++ -Ilibfreebayes_common.a.p -I. -I.. -I../src -I../ttmath 
> -I/usr/include/vcflib -I/usr/include/smithwaterman -I/usr/include/fastahack 
> -I/usr/include/SeqLib -I/usr/include/jsoncpp -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c++14 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
> -fpermissive -Wno-reorder -Wno-sign-compare -Wno-unused-variable 
> -Wno-unused-but-set-variable -MD -MQ libfreebayes_common.a.p/src_Bias.cpp.o 
> -MF libfreebayes_common.a.p/src_Bias.cpp.o.d -o 
> libfreebayes_common.a.p/src_Bias.cpp.o -c ../src/Bias.cpp
> [5/27] c++ -Ilibfreebayes_common.a.p -I. -I.. -I../src -I../ttmath 
> -I/usr/include/vcflib -I/usr/include/smithwaterman -I/usr/include/fastahack 
> -I/usr/include/SeqLib -I/usr/includ

Bug#1031470: jquery-i18n-properties: FTBFS: make[1]: *** [debian/rules:15: override_dh_auto_build] Error 254

[Lucas Nussbaum]

Source: jquery-i18n-properties
Version: 1.2.7+dfsg1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> closure-compiler --js jquery.i18n.properties.js --js_output_file 
> jquery.i18n.properties-min.js
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)
> make[1]: *** [debian/rules:15: override_dh_auto_build] Error 254


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/jquery-i18n-properties_1.2.7+dfsg1-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031471: guestfs-tools: FTBFS: make[5]: *** [Makefile:1073: test-suite.log] Error 1

[Lucas Nussbaum]

Source: guestfs-tools
Version: 1.48.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[5]: Entering directory '/<>/resize'
> SKIP: rhbz1285847.sh
> PASS: test-virt-resize-docs.sh
> FAIL: test-virt-resize.pl
> 
> Testsuite summary for guestfs-tools 1.48.3
> 
> # TOTAL: 3
> # PASS:  1
> # SKIP:  1
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See resize/test-suite.log
> 
> make[5]: *** [Makefile:1073: test-suite.log] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/guestfs-tools_1.48.3-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031469: botch: FTBFS: make[2]: *** [Makefile:339: test-python] Error 1

[Lucas Nussbaum]

Source: botch
Version: 0.24-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> # FIXME: add more tests
> #./tests.py
> #OCAMLPATH=/<>/dose/_build ocamlbuild -classic-display 
> -use-ocamlfind -cflags "-w +a-4-9-24" tests.native
> #./tests.native
> pyflakes3 tools/*.py
> # E402 is triggered by the sys.path.append() statement in front of import of 
> utils
> # see https://github.com/PyCQA/pycodestyle/issues/264
> # W503 is not PEP8 compliant
> # E203 is not PEP8 compliant
> pycodestyle --max-line-length=88 --ignore=E402,E203,W503 tools/*.py
> black --check tools/*.py
> would reformat tools/packages-diff.py
> 
> Oh no!   
> 1 file would be reformatted, 38 files would be left unchanged.
> make[2]: *** [Makefile:339: test-python] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/botch_0.24-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031468: ruby-rubydns: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'celluloid' (= 0.

[Lucas Nussbaum]

Source: ruby-rubydns
Version: 1.0.3-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block 
> in activate_dependencies': Could not find 'celluloid' (= 0.16.0) among 111 
> total gem(s) (Gem::MissingSpecError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-rubydns/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0'
>  at: 
> /<>/debian/ruby-rubydns/usr/share/rubygems-integration/all/specifications/rubydns-1.0.3.gemspec,
>  execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not 
> find 'celluloid' (= 0.16.0) - did find: [celluloid-0.18.0] 
> (Gem::MissingSpecVersionError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-rubydns/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0'
>  , execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> abbrev (default: 0.1.0)
> base64 (default: 0.1.1)
> benchmark (default: 0.2.0)
> bigdecimal (default: 3.1.1)
> bundler (2.3.15, default: 2.3.7)
> celluloid (0.18.0)
> celluloid-essentials (0.20.5)
> celluloid-extras (0.20.5)
> celluloid-fsm (0.20.5)
> celluloid-io (0.16.2)
> celluloid-pool (0.20.5)
> celluloid-supervision (0.20.5)
> cgi (default: 0.3.5)
> csv (default: 3.2.2)
> date (default: 3.2.2)
> debug (1.4.0)
> delegate (default: 0.2.0)
> did_you_mean (default: 1.6.1)
> diff-lcs (1.5.0)
> digest (default: 3.1.0)
> dotenv (2.4.0)
> drb (default: 2.1.0)
> english (default: 0.7.1)
> erb (default: 2.2.3)
> error_highlight (default: 0.3.0)
> etc (default: 1.3.0)
> fcntl (default: 1.0.1)
> fiddle (default: 1.1.0)
> fileutils (default: 1.6.0)
> find (default: 0.1.1)
> forwardable (default: 1.3.2)
> getoptlong (default: 0.1.1)
> hitimes (1.3.1)
> io-console (default: 0.5.11)
> io-nonblock (default: 0.1.0)
> io-wait (default: 0.2.1)
> ipaddr (default: 1.2.4)
> irb (default: 1.4.1)
> json (default: 2.6.1)
> logger (default: 1.5.0)
> matrix (0.4.2)
> minitest (5.15.0)
> mutex_m (default: 0.1.1)
> nenv (0.3.0)
> net-ftp (0.1.3)
> net-http (default: 0.2.0)
> net-imap (0.2.3)
> net-pop (0.1.1)
> net-protocol (default: 0.1.2)
> net-smtp (0.3.1)
> net-telnet (0.2.0)
> nio4r (2.5.8)
> nkf (default: 0.1.1)
> observer (default: 0.1.1)
> open-uri (default: 0.2.0)
> open3 (default: 0.1.1)
> openssl (default: 3.0.0)
> optparse (default: 0.2.0)
> ostruct (default: 0.5.2)
> pathname (default: 0.2.0)
> power_assert (2.0.1)
> pp (default: 0.3.0)
> prettyprint (default: 0.1.1)
> prime (0.1.2)
> pstore (default: 0.1.1)
> psych (default: 4.0.3)
> racc (default: 1.6.0)
> rake (13.0.6)
> rbs (2.1.0)
> rdoc (default: 6.4.0)
> readline (default: 0.0.3)
> readline-ext (defaul

Bug#1031467: eclipse-collections: FTBFS: build-dependency not installable: libeclipse-osgi-util-java

[Lucas Nussbaum]

Source: eclipse-collections
Version: 11.0.0.M3-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), junit4, 
> libmaven-dependency-plugin-java, libmaven-jar-plugin-java, 
> libmaven-javadoc-plugin-java, libmaven-shade-plugin-java, 
> libmaven3-core-java, libslf4j-java, libstringtemplate4-java, libtycho-java, 
> maven-debian-helper, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), junit4, 
> libmaven-dependency-plugin-java, libmaven-jar-plugin-java, 
> libmaven-javadoc-plugin-java, libmaven-shade-plugin-java, 
> libmaven3-core-java, libslf4j-java, libstringtemplate4-java, libtycho-java, 
> maven-debian-helper, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [451 B]
> Get:5 copy:/<>/apt_archive ./ Packages [533 B]
> Fetched 1941 B in 0s (145 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libtycho-java : Depends: libeclipse-osgi-util-java but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/eclipse-collections_11.0.0.M3-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031465: snippy: FTBFS: make[2]: *** [Makefile:32: S1/snps.tab] Error 2

[Lucas Nussbaum]

Source: snippy
Version: 4.6.0+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/test'
> mkdir -p S1
> wgsim -S 1 \
>-h -r 0.005 -N 12000 -1 100 -2 100 -d 200 \
>example.fna S1/R2.fq S1/R1.fq > S1/dwgsim.tab
> [wgsim] seed = 1
> [wgsim_core] calculating the total length of the reference sequence...
> [wgsim_core] 3 sequences, total length: 317336
> mkdir -p S2
> wgsim -S 2 \
>-h -r 0.005 -N 12000 -1 100 -2 100 -d 200 \
>example.fna S2/R2.fq S2/R1.fq > S2/dwgsim.tab
> [wgsim] seed = 2
> [wgsim_core] calculating the total length of the reference sequence...
> [wgsim_core] 3 sequences, total length: 317336
> mkdir -p S3
> wgsim -S 3 \
>-h -r 0.005 -N 12000 -1 100 -2 100 -d 200 \
>example.fna S3/R2.fq S3/R1.fq > S3/dwgsim.tab
> [wgsim] seed = 3
> [wgsim_core] calculating the total length of the reference sequence...
> [wgsim_core] 3 sequences, total length: 317336
> mkdir -p S4
> wgsim -S 4 \
>-h -r 0.005 -N 12000 -1 100 -2 100 -d 200 \
>example.fna S4/R2.fq S4/R1.fq > S4/dwgsim.tab
> [wgsim] seed = 4
> [wgsim_core] calculating the total length of the reference sequence...
> [wgsim_core] 3 sequences, total length: 317336
> ../bin/snippy --cpus 2 --ram 2 --force --ref example.fna --outdir S1 --R1 
> S1/R1.fq --R2 S1/R2.fq
> [01:21:32] This is snippy 4.6.0
> [01:21:32] Written by Torsten Seemann
> [01:21:32] Obtained from https://github.com/tseemann/snippy
> [01:21:32] Detected operating system: linux
> [01:21:32] Enabling bundled linux tools.
> [01:21:32] Found bwa - /usr/bin/bwa
> [01:21:32] Found bcftools - /usr/bin/bcftools
> [01:21:32] Found samtools - /usr/bin/samtools
> [01:21:32] Found java - /usr/bin/java
> [01:21:32] Found snpEff - /usr/bin/snpEff
> [01:21:32] Found samclip - /usr/bin/samclip
> [01:21:32] Found seqtk - /usr/bin/seqtk
> [01:21:32] Found parallel - /usr/bin/parallel
> [01:21:32] Found freebayes - /usr/bin/freebayes
> [01:21:32] Found freebayes-parallel - 
> /usr/share/freebayes/scripts/freebayes-parallel
> [01:21:32] Found fasta_generate_regions.py - 
> /usr/share/freebayes/scripts/fasta_generate_regions.py
> [01:21:32] Found vcfstreamsort - /usr/bin/vcfstreamsort
> [01:21:32] Found vcfuniq - /usr/bin/vcfuniq
> [01:21:32] Found vcffirstheader - /usr/share/freebayes/scripts/vcffirstheader
> [01:21:32] Found gzip - /bin/gzip
> [01:21:32] Found vt - /usr/bin/vt
> [01:21:32] Found snippy-vcf_to_tab - /<>/bin/snippy-vcf_to_tab
> [01:21:32] Found snippy-vcf_report - /<>/bin/snippy-vcf_report
> [01:21:32] Checking version: samtools --version is >= 1.7 - ok, have 1.16
> [01:21:32] Checking version: bcftools --version is >= 1.7 - ok, have 1.16
> [01:21:32] Need freebayes --version >= 1.1 but you have 0 - please upgrade it.
> make[2]: *** [Makefile:32: S1/snps.tab] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/snippy_4.6.0+dfsg-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031466: grml2usb: FTBFS: make[2]: *** [Makefile:44: codecheck] Error 1

[Lucas Nussbaum]

Source: grml2usb
Version: 0.19.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> flake8 grml2usb
> isort --check-only grml2usb
> black --check grml2usb
> would reformat grml2usb
> 
> Oh no!   
> 1 file would be reformatted.
> make[2]: *** [Makefile:44: codecheck] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/grml2usb_0.19.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031462: libmemcached-libmemcached-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: libmemcached-libmemcached-perl
Version: 1.001801+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> "/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- libmemcached.bs 
> blib/arch/auto/Memcached/libmemcached/libmemcached.bs 644
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 
> 'blib/arch')" t/*.t
> # Testing Memcached::libmemcached 1.001801, Perl 5.036000, linux, 
> /usr/bin/perl
> 
> #   Failed test '1.001801 should be 1.0103 with two digits appended'
> #   at t/00-load.t line 27.
> #   '1.001801'
> # doesn't match '(?^:^1\.0103\d\d)'
> # Looks like you failed 1 test of 5.
> t/00-load.t .. 
> 1..5
> ok 1 - use Memcached::libmemcached;
> ok 2 - $Memcached::libmemcached::VERSION should be defined
> ok 3 - ::libmemcached::memcached_lib_version should be defined
> ok 4
> not ok 5 - 1.001801 should be 1.0103 with two digits appended
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/5 subtests 
> t/01-import.t  
> 1..16
> ok 1 - use Memcached::libmemcached;
> ok 2 - should not import func by default
> ok 3 - should import func on demand
> ok 4 - should not import MEMCACHED_SUCCESS by default
> ok 5 - should not import MEMCACHED_FAILURE by default
> ok 6 - should import MEMCACHED_SUCCESS on demand
> ok 7 - should not import MEMCACHED_FAILURE when importing MEMCACHED_SUCCESSi
> ok 8
> ok 9 - should not import MEMCACHED_HASH_MD5 by default
> ok 10 - should not import MEMCACHED_HASH_CRC by default
> ok 11 - should import MEMCACHED_HASH_MD5 by :memcached_hash tag
> ok 12 - should import MEMCACHED_HASH_CRC by :memcached_hash tag
> ok 13
> ok 14
> ok 15
> ok 16
> ok
> t/02-create.t  
> 1..5
> ok 1 - use Memcached::libmemcached;
> ok 2
> ok 3
> ok 4
> duplicate memcached_free
> ok 5
> ok
> t/02-subclass.t .. 
> 1..6
> ok 1 - use Memcached::libmemcached;
> ok 2
> ok 3
> ok 4
> ok 5
> ok 6
> ok
> t/03-servers.t ... 
> 1..10
> ok 1 - use Memcached::libmemcached;
> ok 2
> ok 3 - should have 0 elements
> ok 4
> ok 5 - should have 1 element
> ok 6
> ok 7 - should have 2 elements
> ok 8
> ok 9 - should have 3 elements
> ok 10
> ok
> t/04-strerror.t .. 
> 1..6
> ok 1
> ok 2
> ok 3 - rc should not be defined
> ok 4 - should be MEMCACHED_INVALID_ARGUMENTS integer in numeric context
> ok 5 - should be "INVALID ARGUMENTS" string in string context
> ok 6
> ok
> t/05-behavior.t .. 
> 1..6
> ok 1
> ok 2
> ok 3
> ok 4
> ok 5
> ok 6
> ok
> t/06-verbosity.t . 
> 1..1
> ok 1
> ok
> # Testing using memcached version 1.6.18
> t/10-set-get.t ... 
> 1..14
> ok 1 - should not exist yet and so should return undef
> ok 2
> ok 3
> ok 4
> ok 5
> ok 6 - flags should be unchanged
> ok 7
> ok 8
> ok 9
> ok 10
> ok 11 - utf8 arg length should not be altered
> ok 12 - utf8 arg should not be altered
> ok 13
> ok 14 - no inbuilt utf8 support # TODO support utf8
> # 
> ok
> t/11-set-get-by-key.t  
> 1..13
> memcached_get the not yet stored value
> ok 1 - should not exist yet and so should return undef
> ok 2
> ok 3
> ok 4
> ok 5 - flags should be unchanged
> ok 6
> ok 7
> ok 8
> ok 9
> ok 10 - utf8 arg length should not be altered
> ok 11 - utf8 arg should not be altered
> ok 12
> ok 13 - no inbuilt utf8 support # TODO support utf8
> # 
> ok
> t/12-set-get-binary.t  
> 1..5
> ok 1
> ok 2
> ok 3
> ok 4
> ok 5
> ok
> t/15-auto.t .. 
> 1..9
> memcached_increment the not yet stored value
> ok 1 - should not exist yet and so should return false
> ok 2 - should not exist yet and so should return false but defined
> memcached_set
> ok 3
> memcached_increment the just stored value
> ok 4 - should increment existing value
> ok 5
> ok 6 - should increment existing value
> ok 7
> ok 8 - should increment existing value
> ok 9
> ok
> t/20-set.t ... 
> 1..1
> ok 1
> ok
> t/21-set-by-key.t  
> 1..1
> ok 1
> ok
> t/25-get.t ... 
> 1..66
> ok 1
> ok 2
> ok 3
> ok 4
> ok

Bug#1031464: python-schema-salad: FTBFS: schema_salad/ref_resolver.py:845: error: Unused "type: ignore" comment

[Lucas Nussbaum]

Source: python-schema-salad
Version: 8.4.20230201194352-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild plugin_pyproject:107: Building wheel for python3.11 with "build" 
> module
> I: pybuild base:240: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.11_schema-salad 
> * Building wheel...
> schema_salad/ref_resolver.py:845: error: Unused "type: ignore" comment
> elif isinstance(document, (list, dict)):  # type: 
> ignore[unreachable]
> 
> ^~~~
> 
> ERROR Backend subprocess exited when trying to invoke build_wheel
> E: pybuild pybuild:388: build: plugin pyproject failed with: exit code=1: 
> python3.11 -m build --skip-dependency-check --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.11_schema-salad 
> dh_auto_build: error: pybuild --build -i python{version} -p 3.11 returned 
> exit code 13
> make[1]: *** [debian/rules:16: override_dh_auto_build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/python-schema-salad_8.4.20230201194352-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031463: golang-github-prometheus-exporter-toolkit: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/prometheus/exporter-toolkit/web github.com/prometheus/exporter-tool

[Lucas Nussbaum]

Source: golang-github-prometheus-exporter-toolkit
Version: 0.8.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=golang --builddirectory=_build
>dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=_build
>dh_autoreconf -O--buildsystem=golang -O--builddirectory=_build
>dh_auto_configure -O--buildsystem=golang -O--builddirectory=_build
>dh_auto_build -O--buildsystem=golang -O--builddirectory=_build
>   cd _build && go install -trimpath -v -p 8 
> github.com/prometheus/exporter-toolkit/web 
> github.com/prometheus/exporter-toolkit/web/kingpinflag
> internal/goarch
> internal/goos
> internal/unsafeheader
> internal/goexperiment
> internal/race
> internal/cpu
> runtime/internal/syscall
> runtime/internal/atomic
> sync/atomic
> unicode
> unicode/utf8
> internal/abi
> runtime/internal/math
> runtime/internal/sys
> container/list
> internal/itoa
> internal/bytealg
> math/bits
> crypto/internal/subtle
> crypto/subtle
> crypto/internal/boring/sig
> unicode/utf16
> vendor/golang.org/x/crypto/cryptobyte/asn1
> internal/nettrace
> vendor/golang.org/x/crypto/internal/subtle
> encoding
> math
> google.golang.org/protobuf/internal/flags
> google.golang.org/protobuf/internal/set
> runtime
> runtime/metrics
> sync
> internal/reflectlite
> internal/testlog
> math/rand
> internal/singleflight
> google.golang.org/protobuf/internal/pragma
> runtime/cgo
> errors
> sort
> io
> internal/oserror
> strconv
> path
> internal/safefilepath
> crypto/internal/nistec/fiat
> syscall
> vendor/golang.org/x/net/dns/dnsmessage
> github.com/beorn7/perks/quantile
> hash
> bytes
> strings
> crypto/internal/randutil
> hash/crc32
> vendor/golang.org/x/text/transform
> hash/fnv
> bufio
> crypto
> reflect
> crypto/rc4
> regexp/syntax
> net/http/internal/ascii
> github.com/prometheus/common/internal/bitbucket.org/ww/goautoneg
> html
> text/tabwriter
> golang.org/x/text/transform
> golang.org/x/crypto/blowfish
> internal/syscall/execenv
> internal/syscall/unix
> time
> regexp
> context
> io/fs
> github.com/jpillora/backoff
> internal/poll
> embed
> os
> internal/fmtsort
> encoding/binary
> crypto/cipher
> crypto/internal/edwards25519/field
> crypto/internal/nistec
> crypto/md5
> encoding/base64
> vendor/golang.org/x/crypto/internal/poly1305
> vendor/golang.org/x/crypto/curve25519/internal/field
> encoding/pem
> fmt
> internal/godebug
> internal/intern
> path/filepath
> crypto/internal/boring
> crypto/des
> crypto/internal/edwards25519
> vendor/golang.org/x/crypto/chacha20
> crypto/aes
> crypto/sha512
> crypto/hmac
> crypto/sha1
> crypto/sha256
> net/netip
> io/ioutil
> vendor/golang.org/x/sys/cpu
> vendor/golang.org/x/crypto/hkdf
> github.com/cespare/xxhash
> google.golang.org/protobuf/internal/detrand
> github.com/prometheus/procfs/internal/util
> golang.org/x/sys/unix
> internal/lazyregexp
> vendor/golang.org/x/crypto/chacha20poly1305
> net/url
> encoding/hex
> math/big
> vendor/golang.org/x/crypto/curve25519
> encoding/json
> github.com/go-logfmt/logfmt
> log
> net
> compress/flate
> vendor/golang.org/x/text/unicode/bidi
> vendor/golang.org/x/text/unicode/norm
> vendor/golang.org/x/net/http2/hpack
> mime
> compress/gzip
> github.com/go-kit/log
> vendor/golang.org/x/text/secure/bidirule
> mime/quotedprintable
> net/http/internal
> github.com/golang/protobuf/proto
> github.com/prometheus/common/model
> google.golang.org/protobuf/internal/errors
> github.com/go-kit/log/level
> google.golang.org/protobuf/encoding/protowire
> vendor/golang.org/x/net/idna
> crypto/elliptic
> crypto/internal/boring/bbig
> encoding/asn1
> crypto/rand
> crypto/dsa
> google.golang.org/protobuf/reflect/protoreflect
> crypto/ed25519
> crypto/rsa
> go/token
> google.golang.org/protobuf/internal/version
> github.com/prometheus/procfs/internal/fs
> runtime/debug
> golang.org/x/net/internal/timeseries
> text/template/parse
> vendor/golang.org/x/crypto/cryptobyte
> crypto/x509/pkix
> golang.org/x/text/unicode/bidi
> golang.org/x/text/unicode/norm
> google.golang.org/protobuf/internal/descfmt
> google.golang.org/protobuf/internal/descopts
> google.golang.org/protobuf/internal/strs
> crypto/ecdsa
> google.golang.org/protobuf/internal/encoding/messageset
> google.golang.org/protobuf/internal/encoding/text
&

Bug#1031460: enlighten: FTBFS: AssertionError: '1.00[31 chars]0.00 s/B | 128.00 KiB | 896.00 KiB | 512.00 K[105 chars] s/B' != '1.00[31 chars]0.00 s/B | 128.00 KiB | 896.00 KiB | 512.00 Ki[101 chars]

[Lucas Nussbaum]

Source: enlighten
Version: 1.11.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:515: 
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use 
> license_files instead.
>   warnings.warn(msg, warning_class)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/counter.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/manager.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_counter.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_basemanager.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_statusbar.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_basecounter.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_util.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_notebook_manager.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_manager.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> PYTHONPATH=. python3 -m sphinx -N -bhtml doc/ build/html # HTML generator
> Running Sphinx v5.3.0
> Initializing Spelling Checker 7.7.0
> making output directory... done
> loading intersphinx inventory from https://docs.python.org/3/objects.inv...
> loading intersphinx inventory from 
> https://prefixed.readthedocs.io/en/stable/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'https://docs.python.org/3/objects.inv' not fetchable 
> due to : 
> HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded 
> with url: /3/objects.inv (Caused by ProxyError('Cannot connect to proxy.', 
> NewConnectionError(' 0x7f8203179b50>: Failed to establish a new connection: [Errno 111] Connection 
> refused')))
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'https://prefixed.readthedocs.io/en/stable/objects.inv' 
> not fetchable due to : 
> HTTPSConnectionPool(host='prefixed.readthedocs.io', port=443): Max retries 
> exceeded with url: /en/stable/objects.inv (Caused by ProxyError('Cannot 
> connect to proxy.', NewConnectionError(' object at 0x7f820317a190>: Failed to establish a new connection: [Errno 111] 
> Connection refused')))
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 6 source files that are out of date
> updating environment: [new config] 6 added, 0 changed, 0 removed
> reading sources... [ 16%] api
> direct use of the spelling directive is deprecated, replace ".. spelling::" 
> with ".. spelling:word-list::"
> reading sources... [ 33%] examples
> reading sources... [ 50%] faq
> direct use of the spelling directive is deprecated, replace ".. spelling::" 
> with ".. spelling:word-list::"
> reading sources... [ 66%] index
> reading sources... [ 83%] install
> reading sources... [100%] patterns
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 16%] api
> writing output... [ 33%] examples
> writing output... [ 50%] faq
> writing output... [ 66%] index
> writing output... [ 83%] install
> writing output... [100%] patterns
> 
> /<>/enlighten/_manager.py:docstring of 
> enlighten._manager.Manager:1: WARNING: term not in glossary: 'file object'
> /<>/enlighten/_manager.py:docstring of 
> enlighten._manager.Manager:1: WARNING: term not in glossary: 'class'
> /<>/enlighten/_manager.py:docstring of 
> enlighten._manager.Manager:2: WARNING: term not in glossary: 'class'
> /<>/enlighten/_manager.py:docstring of 
> enlighten._manager.Manager:7: WARNING: term not in glossary: 'file object'
> /<>/enlighten/_manager.py:docstring of 
> enlighten._manager.Manager:17: WARNING: term not in glossary: 'keyword 
> argument'
> /<>/enlighten/_manager.py:docstring of 
> enlighten._manager.Manager:30: WARNING: term not in glossary: 'file object'
> /<>/enlighten/_manager.py:docstring of 
> enlighten._manager

Bug#1031461: django-axes: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: django-axes
Version: 5.39.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom \
> PYBUILD_TEST_ARGS="py.test-3" \
> PYTHONPATH=. dh_auto_test
>   pybuild --test --test-pytest -i python{version} -p 3.11
> I: pybuild base:240: py.test-3
> = test session starts 
> ==
> platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack
> django: settings: tests.settings (from ini)
> rootdir: /<>, configfile: pyproject.toml, testpaths: tests
> plugins: django-4.5.2, cov-4.0.0
> collected 293 items
> 
> tests/test_admin.py ..   [  
> 0%]
> tests/test_attempts.py . [  
> 7%]
> tests/test_backends.py ..[  
> 8%]
> tests/test_checks.py .   [ 
> 11%]
> tests/test_decorators.py [ 
> 12%]
> tests/test_failures.py ..[ 
> 13%]
> tests/test_handlers.py . [ 
> 30%]
> .[ 
> 32%]
> tests/test_helpers.py .. [ 
> 49%]
> ..   [ 
> 56%]
> tests/test_logging.py ...F   [ 
> 60%]
> tests/test_login.py  [ 
> 78%]
> ...  [ 
> 93%]
> tests/test_management.py ... [ 
> 96%]
> tests/test_middleware.py [ 
> 98%]
> tests/test_models.py [ 
> 99%]
> tests/test_signals.py .  
> [100%]
> 
> === FAILURES 
> ===
> __ AccessLogTestCase.test_log_data_truncated 
> ___
> 
> self =  testMethod=test_log_data_truncated>
> 
> def test_log_data_truncated(self):
> """
> Test that get_query_str properly truncates data to the max_length 
> (default 1024).
> """
> 
> # An impossibly large post dict
> extra_data = {"a" * x: x for x in range(1024)}
> self.login(**extra_data)
> >   self.assertEqual(len(AccessAttempt.objects.latest("id").post_data), 
> > 1024)
> 
> tests/test_logging.py:80: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> /usr/lib/python3/dist-packages/django/db/models/manager.py:85: in 
> manager_method
> return getattr(self.get_queryset(), name)(*args, **kwargs)
> /usr/lib/python3/dist-packages/django/db/models/query.py:670: in latest
> return self.reverse()._earliest(*fields)
> /usr/lib/python3/dist-packages/django/db/models/query.py:664: in _earliest
> return obj.get()
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> self = , args = (), kwargs = {}, clone = , limit = 
> 21
> num = 0
> 
> def get(self, *args, **kwargs):
> """
> Perform the query and return a single object matching the given
> keyword arguments.
> """
> if self.query.combinator and (args or kwargs):
> raise NotSupportedError(
> 'Calling QuerySet.get(...) with filters after %s() is not '
> 'supported.' % self.query.combinator
> )
> clone = self._chain() if self.query.combinator else 
> self.filter(*args, **kwargs)
> if self.query.can_filter() and not self.query.distinct_fields:
> clone = clone.order_by()
> limit = None
> if not clone.query.select_for_update or 
> connections[clone.db].features.supports_select_for_update_with_limit:
> limit = MAX_GET_RESULTS
> clone.query.set_limits(high=limit)
> num = len(clone)
> if num == 1:
> return clone._result_cache[0]
> if not num:
> >   raise self.model.DoesNotExist(
>

Bug#1031459: pcb-rnd: FTBFS: unsatisfiable build-dependencies: librnd4-dev, librnd4-cloud, librnd4-lib-gui

[Lucas Nussbaum]

Source: pcb-rnd
Version: 3.1.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 11), librnd4-dev, librnd4-cloud, 
> librnd4-lib-gui, imagemagick, libgd-dev, libgtkglext1-dev, libmotif-dev, 
> libstroke0-dev, libxml2-dev, libgenht1-dev, libfungw-dev, build-essential, 
> fakeroot
> Filtered Build-Depends: debhelper (>= 11), librnd4-dev, librnd4-cloud, 
> librnd4-lib-gui, imagemagick, libgd-dev, libgtkglext1-dev, libmotif-dev, 
> libstroke0-dev, libxml2-dev, libgenht1-dev, libfungw-dev, build-essential, 
> fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [433 B]
> Get:5 copy:/<>/apt_archive ./ Packages [515 B]
> Fetched 1905 B in 0s (154 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: librnd4-dev but it is not 
> installable
>Depends: librnd4-cloud but it is not 
> installable
>Depends: librnd4-lib-gui but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/pcb-rnd_3.1.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031458: dojo: FTBFS: make[1]: *** [debian/rules:48: override_dh_auto_test] Error 1

[Lucas Nussbaum]

Source: dojo
Version: 1.17.2+dfsg1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd util/shrinksafe/tests && ./runner.sh
> Exception in thread "main" java.util.MissingResourceException: Can't find 
> bundle for base name org.mozilla.javascript.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> org.mozilla.javascript.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> org.mozilla.javascript.ScriptRuntime.getMessageById(ScriptRuntime.java:4505)
>   at 
> org.mozilla.javascript.ScriptRuntime.notFoundError(ScriptRuntime.java:4631)
>   at 
> org.mozilla.javascript.ScriptRuntime.nameOrFunction(ScriptRuntime.java:2019)
>   at org.mozilla.javascript.ScriptRuntime.name(ScriptRuntime.java:1957)
>   at 
> org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:1972)
>   at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:1053)
>   at 
> org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:90)
>   at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
>   at 
> org.mozilla.javascript.gen.__dojo_dojo_js_1._c_anonymous_13(Unknown 
> Source)
>   at org.mozilla.javascript.gen.__dojo_dojo_js_1.call(Unknown Source)
>   at 
> org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:1871)
>   at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:1053)
>   at 
> org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:90)
>   at 
> org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2766)
>   at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:327)
>   at 
> org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:100)
>   at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:46)
>   at 
> org.mozilla.javascript.gen.__dojo_dojo_js_1._c_anonymous_68(Unknown 
> Source)
>   at org.mozilla.javascript.gen.__dojo_dojo_js_1.call(Unknown Source)
>   at 
> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:59)
>   at 
> org.mozilla.javascript.gen.__dojo_dojo_js_1._c_anonymous_75(Unknown 
> Source)
>   at org.mozilla.javascript.gen.__dojo_dojo_js_1.call(Unknown Source)
>   at 
> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:59)
>   at 
> org.mozilla.javascript.gen.__dojo_dojo_js_1._c_anonymous_75(Unknown 
> Source)
>   at org.mozilla.javascript.gen.__dojo_dojo_js_1.call(Unknown Source)
>   at 
> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:59)
>   at 
> org.mozilla.javascript.gen.__dojo_dojo_js_1._c_anonymous_75(Unknown 
> Source)
>   at org.mozilla.javascript.gen.__dojo_dojo_js_1.call(Unknown Source)
>   at 
> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:59)
>   at 
> org.mozilla.javascript.gen.__dojo_dojo_js_1._c_anonymous_45(Unknown 
> Source)
>   at org.mozilla.javascript.gen.__dojo_dojo_js_1.call(Unknown Source)
>   at 
> org.mozilla.javascript.optimizer.OptRuntime.callName0(OptRuntime.java:66)
>   at 
> org.mozilla.javascript.gen.__dojo_dojo_js_1._c_anonymous_76(Unknown 
> Source)
>   at org.mozilla.javascript.gen.__dojo_dojo_js_1.call(Unknown Source)
>   at 
> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:59)
>   at 
> org.mozilla.javascript.gen.__dojo_dojo_js_1._c_anonymous_44(Unknown 
> Source)
>   at org.mozilla.javascript.gen.__dojo_dojo_js_1.call(Unknown Source)
>   at 
> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:59)
>   at 
> org.mozilla.javascript.gen.__dojo_dojo_js_1._c_anonymous_12(Unknown 
> Source)
>   at org.mozilla.javascript.gen.__dojo_dojo_js_1.call(Unknown Source)
>   at 
> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:59)
>   at 
> org.mozilla.javascript.ge

Bug#1031457: ruby-redis: FTBFS: ERROR: Test "ruby3.1" failed.

[Lucas Nussbaum]

Source: ruby-redis
Version: 4.8.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-redis/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -e gem\ \"redis\"
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=. 
> GEM_PATH=/<>/debian/ruby-redis/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -S rake -f debian/ruby-tests.rake
> /<>/lib/redis/client.rb:398:in `rescue in establish_connection': 
> Error connecting to Redis on 127.0.0.1:7000 (Errno::ECONNREFUSED) 
> (Redis::CannotConnectError)
>   from /<>/lib/redis/client.rb:379:in `establish_connection'
>   from /<>/lib/redis/client.rb:115:in `block in connect'
>   from /<>/lib/redis/client.rb:344:in `with_reconnect'
>   from /<>/lib/redis/client.rb:114:in `connect'
>   from /<>/lib/redis/client.rb:417:in `ensure_connected'
>   from /<>/lib/redis/client.rb:269:in `block in process'
>   from /<>/lib/redis/client.rb:356:in `logging'
>   from /<>/lib/redis/client.rb:268:in `process'
>   from /<>/lib/redis/client.rb:161:in `call'
>   from /<>/lib/redis.rb:270:in `block in send_command'
>   from /<>/lib/redis.rb:269:in `synchronize'
>   from /<>/lib/redis.rb:269:in `send_command'
>   from /<>/lib/redis/commands/server.rb:68:in `flushall'
>   from /<>/test/support/cluster/orchestrator.rb:112:in 
> `block in flush_all_data'
>   from /<>/test/support/cluster/orchestrator.rb:110:in `each'
>   from /<>/test/support/cluster/orchestrator.rb:110:in 
> `flush_all_data'
>   from /<>/test/support/cluster/orchestrator.rb:26:in 
> `rebuild'
>   from bin/cluster_creator:10:in `'
> /usr/lib/ruby/3.1.0/socket.rb:1214:in `__connect_nonblock': Connection 
> refused - connect(2) for 127.0.0.1:7000 (Errno::ECONNREFUSED)
>   from /usr/lib/ruby/3.1.0/socket.rb:1214:in `connect_nonblock'
>   from /<>/lib/redis/connection/ruby.rb:163:in `rescue in 
> connect_addrinfo'
>   from /<>/lib/redis/connection/ruby.rb:157:in 
> `connect_addrinfo'
>   from /<>/lib/redis/connection/ruby.rb:196:in `block in 
> connect'
>   from /<>/lib/redis/connection/ruby.rb:194:in `each'
>   from /<>/lib/redis/connection/ruby.rb:194:in 
> `each_with_index'
>   from /<>/lib/redis/connection/ruby.rb:194:in `connect'
>   from /<>/lib/redis/connection/ruby.rb:308:in `connect'
>   from /<>/lib/redis/client.rb:385:in `establish_connection'
>   from /<>/lib/redis/client.rb:115:in `block in connect'
>   from /<>/lib/redis/client.rb:344:in `with_reconnect'
>   from /<>/lib/redis/client.rb:114:in `connect'
>   from /<>/lib/redis/client.rb:417:in `ensure_connected'
>   from /<>/lib/redis/client.rb:269:in `block in process'
>   from /<>/lib/redis/client.rb:356:in `logging'
>   from /<>/lib/redis/client.rb:268:in `process'
>   from /<>/lib/redis/client.rb:161:in `call'
>   from /<>/lib/redis.rb:270:in `block in send_command'
>   from /<>/lib/redis.rb:269:in `synchronize'
>   from /<>/lib/redis.rb:269:in `send_command'
>   from /<>/lib/redis/commands/server.rb:68:in `flushall'
>   from /<>/test/support/cluster/orchestrator.rb:112:in 
> `b

Bug#1031456: r-cran-shiny: FTBFS: make[1]: *** [debian/rules:28: override_dh_install] Error 254

[Lucas Nussbaum]

Source: r-cran-shiny
Version: 1.7.4+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install
> find debian -name "LICENSE*" -delete
> rm -rf 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/showdown/license.txt
> mkdir -p 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/bootstrap/shim
> cp -a debian/missing-sources/respond/respond.min.js 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/bootstrap/shim/
> mkdir -p 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/strftime
> cp -a debian/missing-sources/strftime/strftime.min.js 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/strftime
> # this fails: yui-compressor 
> debian/missing-sources/babel-polyfill/babel-polyfill.js > 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/babel-polyfill.min.js
> # see https://lists.debian.org/debian-mentors/2016/11/msg00102.html
> cp -a debian/missing-sources/babel-polyfill/babel-polyfill.min.js 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/babel-polyfill.min.js
> # see debian/README.source
> mkdir -p 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/selectize/js/
> cp -a debian/missing-sources/selectize-0.12.1/selectize.min.shiny.js 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/selectize/js/selectize.min.js
> # For some very strange reason a symlink leads to unexpected results in shiny 
> apps.
> # Thus a real copy of font-awesome.min.css from fonts-font-awesome package is 
> created.
> mkdir -p 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/font-awesome/css/
> cp -a /usr/share/fonts-font-awesome/css/font-awesome.min.css 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/font-awesome/css/
> # datepicker is only non-minimized.  Do the minimisation here
> mkdir -p 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/datepicker/js
> closure-compiler  --charset 'utf-8' --js 
> /usr/share/javascript/bootstrap/files/js/bootstrap-datepicker.js 
> --js_output_file 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/datepicker/js/bootstrap-datepicker.min.js
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)
> make[1]: *** [debian/rules:28: override_dh_install] Error 254


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/r-cran-shiny_1.7.4+dfsg-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
o

Bug#1031455: charliecloud: FTBFS: config.h:38: error: "PACKAGE_VERSION" redefined [-Werror]

[Lucas Nussbaum]

Source: charliecloud
Version: 0.31-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -std=c99 -Wall -Werror -c -o ch-ssh.o ch-ssh.c
> rm -f ch-run-oci
> sed -E 's|%PYTHON_SHEBANG%|/usr/bin/env python3|' < ch-run-oci.py.in > 
> ch-run-oci
> chmod +rx,-w ch-run-oci  # respects umask
> rm -f ch-image
> sed -E 's|%PYTHON_SHEBANG%|/usr/bin/env python3|' < ch-image.py.in > ch-image
> chmod +rx,-w ch-image  # respects umask
> In file included from ch_fuse.c:33:
> config.h:38: error: "PACKAGE_VERSION" redefined [-Werror]
>38 | #define PACKAGE_VERSION "0.31"
>   | 
> In file included from /usr/include/fuse3/fuse_common.h:17,
>  from /usr/include/fuse3/fuse_lowlevel.h:25,
>  from /usr/include/squashfuse/ll.h:31,
>  from ch_fuse.c:31:
> /usr/include/fuse3/fuse_config.h:42: note: this is the location of the 
> previous definition
>42 | #define PACKAGE_VERSION "3.13.1"
>   | 
> cc1: all warnings being treated as errors
> make[3]: *** [Makefile:638: ch_run-ch_fuse.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/charliecloud_0.31-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031453: sane-frontends: FTBFS: dh_install: error: missing files, aborting

[Lucas Nussbaum]

Source: sane-frontends
Version: 1.0.14-16
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

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
> autoreconf: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> aclocal: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> acinclude.m4:13: warning: underquoted definition of AM_PATH_GTK
> acinclude.m4:13:   run info Automake 'Extending aclocal'
> acinclude.m4:13:   or see 
> https://www.gnu.org/software/automake/manual/automake.html#Extending-aclocal
> configure.in:3: warning: The macro `AC_CONFIG_HEADER' is obsolete.
> configure.in:3: You should run autoupdate.
> ./lib/autoconf/status.m4:719: AC_CONFIG_HEADER is expanded from...
> configure.in:3: the top level
> configure.in:53: warning: The macro `AC_AIX' is obsolete.
> configure.in:53: You should run autoupdate.
> ./lib/autoconf/specific.m4:540: AC_AIX is expanded from...
> configure.in:53: the top level
> configure.in:54: warning: The macro `AC_MINIX' is obsolete.
> configure.in:54: You should run autoupdate.
> ./lib/autoconf/specific.m4:545: AC_MINIX is expanded from...
> configure.in:54: the top level
> configure.in:55: warning: The macro `AC_ISC_POSIX' is obsolete.
> configure.in:55: You should run autoupdate.
> ./lib/autoconf/specific.m4:550: AC_ISC_POSIX is expanded from...
> configure.in:55: the top level
> configure.in:56: warning: 'AM_PROG_CC_STDC': this macro is obsolete.
> configure.in:56: You should simply use the 'AC_PROG_CC' macro instead.
> configure.in:56: Also, your code should no longer depend upon 
> 'am_cv_prog_cc_stdc',
> configure.in:56: but upon 'ac_cv_prog_cc_stdc'.
> ./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from...
> aclocal.m4:746: AM_PROG_CC_STDC is expanded from...
> configure.in:56: the top level
> configure.in:64: warning: The macro `ac_cv_prog_gcc' is obsolete.
> configure.in:64: You should run autoupdate.
> ./lib/autoconf/c.m4:440: ac_cv_prog_gcc is expanded from...
> configure.in:64: the top level
> configure.in:77: warning: The macro `AC_HEADER_STDC' is obsolete.
> configure.in:77: You should run autoupdate.
> ./lib/autoconf/headers.m4:704: AC_HEADER_STDC is expanded from...
> configure.in:77: the top level
> configure.in:83: warning: The macro `AC_TYPE_SIGNAL' is obsolete.
> configure.in:83: You should run autoupdate.
> ./lib/autoconf/types.m4:776: AC_TYPE_SIGNAL is expanded from...
> configure.in:83: the top level
> configure.in:138: warning: The macro `AC_TRY_RUN' is obsolete.
> configure.in:138: You should run autoupdate.
> ./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
> aclocal.m4:207: AM_PATH_GTK_2_0 is expanded from...
> configure.in:138: the top level
> configure.in:138: warning: The macro `AC_TRY_LINK' is obsolete.
> configure.in:138: You should run autoupdate.
> ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
> aclocal.m4:207: AM_PATH_GTK_2_0 is expanded from...
> configure.in:138: the top level
> configure.in:150: warning: The macro `AC_TRY_RUN' is obsolete.
> configure.in:150: You should run autoupdate.
> ./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
> acinclude.m4:13: AM_PATH_GTK is expanded from...
> configure.in:150: the top level
> configure.in:150: warning: The macro `AC_TRY_LINK' is obsolete.
> configure.in:150: You should run autoupdate.
> ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
> acinclude.m4:13: AM_PATH_GTK is expanded from...
> configure.in:150: the top level
> configure.in:154: warning: The macro `AC_TRY_RUN' is obsolete.
> configure.in:154: You should run autoupdate.
> ./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
> acinclude.m4:185: AM_PATH_GIMP is expanded from...
> configure.in:154: the top level
> configure.in:154: warning: The macro `AC_TRY_LINK' is obsolete.
> configure.in:154: You should run autoupdate.
> ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
> acinclude.m4:185: AM_PATH_GIMP is expanded from...
> configure.in:154: the top level
> configure.in:161: warning: The macro `AC_TRY_RUN' is obsolete.
> configure.in:161: You should run autoupdate.
> ./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
> aclocal.m4:22: AM_PATH_GIMP_2_0 is expanded from...
> configure.in:161: the top level
> configure.in:161: warning: The macro `AC_TRY_LINK' is obsolete.
> configure.in:161: You should run autoupdate.
> ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
> aclocal.m4:2

Bug#1031454: r-cran-pander: FTBFS: make[1]: *** [debian/rules:9: override_dh_auto_build] Error 254

[Lucas Nussbaum]

Source: r-cran-pander
Version: 0.6.5+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> closure-compiler  --charset 'utf-8' --js 
> debian/missing-sources/jcaption/jcaption.js --js_output_file 
> debian/missing-sources/jcaption/jcaption.min.js
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)
> make[1]: *** [debian/rules:9: override_dh_auto_build] Error 254


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/r-cran-pander_0.6.5+dfsg-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Adrian Bunk]

On Thu, Feb 16, 2023 at 03:05:06PM -0800, Russ Allbery wrote:
>...
> Each time you change the defaults in a way that could be
> backward-incompatible, you could capture those new defaults in a
> permanently-fixed label of, say, 20230616, which is the defaults on that
> date.  Probably in the default /etc/mke2fs.conf.  I don't expect you to
> care about what systems they work with, what distributions they work with,
> or anything else other than the timeline of when you decided to change the
> defaults, something you're presumably already doing as a maintainer.  The
> only additional work would be to update these labels with the settings
> required to make mke2fs with its current defaults behave compatibly with
> whatever the defaults had been at each of those captured points in time.
> 
> (And obviously eventually you could drop the really old ones if it made no
> sense to keep supporting them, or have some single really-ancient fallback
> for really old systems, etc.)
> 
> Then, image creators can look in /etc/mke2fs.conf for the timestamp that
> most closely aligns with the target system they want to create and use
> that group of settings.  If that turns out to be inadequate, they can go
> back to a previous date.

The image creators could just set the features they enable to what they 
copied from /etc/mke2fs.conf from the target distribution, a label with 
a timestamp wouldn'tbring much benefit here.

We are talking about tools for creating filesystems and their authors,
users of these tools don't have to know anything about all that.

> Some work on their part is still required, but
> from their perspective I think this would have the advantage of not having
> to do research to reconstruct what all the options could be and how they
> changed and which ones were potentially backward-incompatible, which are
> all things you would generally already know and have in mind when you
> changed the defaults and thus could capture for them.
>...

Image creators usually support several different filesystems.

There is also the point that a tool in bookworm that supports creating 
bullseye images will also support creating bookworm images, so when 
there is a difference in the settings for bullseye and bookworm images
it should anyway be updated for the difference. Setting a new default
for bookworm or disabling a new feature for <= bullseye, the work is
trivial in any case and the hard part is all image creators being aware
that there is a difference.

cu
Adrian

Bug#1031452: prettify.js: FTBFS: java.util.MissingResourceException: Can't find bundle for base name com.google.javascript.rhino.head.resources.Messages, locale en

[Lucas Nussbaum]

Source: prettify.js
Version: 2015.12.04+dfsg-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> Compiling
> 1570 src/prettify.css
>  675 distrib/google-code-prettify/prettify.css
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)
> make[2]: *** [Makefile:40: distrib.tstamp] Error 254


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/prettify.js_2015.12.04+dfsg-1.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031451: poliastro: FTBFS: make[1]: *** [debian/rules:9: override_dh_auto_test] Error 1

[Lucas Nussbaum]

Source: poliastro
Version: 0.17.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> === FAILURES 
> ===
> __ test_maneuver_constructor_raises_error_if_invalid_delta_v 
> ___
> 
> def test_maneuver_constructor_raises_error_if_invalid_delta_v():
> dv1 = np.zeros(3) * u.km / u.s
> dv2 = np.ones(2) * u.km / u.s  # Incorrect dv
> with pytest.raises(ValueError) as excinfo:
> with warnings.catch_warnings():
> # Different length numpy arrays generate a deprecation 
> warning.
> warnings.simplefilter(
> "ignore", category=np.VisibleDeprecationWarning
> )
> Maneuver((0 * u.s, dv1), (2 * u.s, dv2))
> >   assert "Delta-V must be three dimensions vectors" in excinfo.exconly()
> E   AssertionError: assert 'Delta-V must be three dimensions vectors' in 
> 'ValueError: setting an array element with a sequence. The requested array 
> has an inhomogeneous shape after 1 dimensions. The detected shape was (2,) + 
> inhomogeneous part.'
> E+  where 'ValueError: setting an array element with a sequence. The 
> requested array has an inhomogeneous shape after 1 dimensions. The detected 
> shape was (2,) + inhomogeneous part.' =  of  requested array has an inhomogeneous shape after 1 dimensions. The detected 
> shape was (2,) + inhomogeneous part.') tblen=4>>()
> E+where  ValueError('setting an array element with a sequence. The requested array has 
> an inhomogeneous shape after 1 dimensions. The detected shape was (2,) + 
> inhomogeneous part.') tblen=4>> =  element with a sequence. The requested array has an inhomogeneous shape after 
> 1 dimensions. The detected shape was (2,) + inhomogeneous part.') 
> tblen=4>.exconly
> 
> tests/test_maneuver.py:26: AssertionError
> __ test_stumpff_functions_above_zero 
> ___
> 
> def test_stumpff_functions_above_zero():
> psi = 3.0
> expected_c2 = (1 - cos(psi**0.5)) / psi
> expected_c3 = (psi**0.5 - sin(psi**0.5)) / psi**1.5
> 
> assert_equal(c2(psi), expected_c2)
> >   assert_equal(c3(psi), expected_c3)
> E   AssertionError: 
> E   Items are not equal:
> EACTUAL: 0.143379966939162
> EDESIRED: 0.14337996693916197
> 
> tests/test_stumpff.py:22: AssertionError
> __ test_stumpff_functions_under_zero 
> ___
> 
> def test_stumpff_functions_under_zero():
> psi = -3.0
> expected_c2 = (cosh((-psi) ** 0.5) - 1) / (-psi)
> expected_c3 = (sinh((-psi) ** 0.5) - (-psi) ** 0.5) / (-psi) ** 1.5
> 
> >   assert_equal(c2(psi), expected_c2)
> E   AssertionError: 
> E   Items are not equal:
> EACTUAL: 0.6381924800586426
> EDESIRED: 0.6381924800586427
> 
> tests/test_stumpff.py:30: AssertionError
> === warnings summary 
> ===
> ../../../usr/lib/python3/dist-packages/llvmlite/binding/ffi.py:159
>   /usr/lib/python3/dist-packages/llvmlite/binding/ffi.py:159: 
> DeprecationWarning: path is deprecated. Use files() instead. Refer to 
> https://importlib-resources.readthedocs.io/en/latest/using.html#migrating-from-legacy
>  for migration advice.
> _lib_handle = importlib.resources.path(pkgname, _lib_name)
> 
> tests/test_frames.py::test_round_trip_from_GeocentricSolarEcliptic_gives_same_results
> tests/test_frames.py::test_GeocentricSolarEcliptic_against_data
>   /<>/src/poliastro/frames/ecliptic.py:78: 
> AstropyDeprecationWarning: The matrix_product function is deprecated and may 
> be removed in a future version.
>   Use @ instead.
> return matrix_product(rot_matrix, _earth_detilt_matrix)
> 
> tests/test_maneuver.py::test_hohmann_maneuver[nu0]
>   /<>/src/poliastro/core/maneuver.py:49: 
> NumbaPerformanceWarning: '@' is faster on contiguous arrays, called on 
> (array(float64, 1d, A), array(float64, 1d, A))
> r_i = norm(r_i)
> 
> tests/tests_plotting/test_gabbard.py::test_static_gabbard_plotting
>   /usr/lib/python3/dist-packages/_pytest/python.py:199: 
> PytestReturnNotNoneWarning:
>   
>   Expected None, but 
> tests/tests_plotting/test_gabbard.py::test_static_gabbard_plotting returned 
> , which will be an error in a future 
> version of pytest.  Did you mean to use `assert` i

Bug#1031450: gearmand: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so: undefined reference to `memcached_server_minor_version'

[Lucas Nussbaum]

Source: gearmand
Version: 1.1.19.1+ds-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /bin/bash ./libtool  --tag=CXX   --mode=link c++  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wno-unknown-pragmas -Wno-pragmas -Wall -Wextra 
> -Wno-attributes -Wvarargs -Waddress -Warray-bounds -Wchar-subscripts 
> -Wcomment -Wctor-dtor-privacy -Wfloat-equal -Wformat=2 -Wformat-y2k 
> -Wmaybe-uninitialized -Wmissing-field-initializers -Wlogical-op 
> -Wnon-virtual-dtor -Wnormalized=id -Woverloaded-virtual -Wpointer-arith 
> -Wredundant-decls -Wshadow -Wsign-compare -Wstrict-overflow=1 -Wswitch-enum 
> -Wtrampolines -Wundef -funsafe-loop-optimizations -Wc++11-compat -Wclobbered 
> -Wunused -Wunused-result -Wunused-variable -Wunused-parameter 
> -Wunused-local-typedefs -Wwrite-strings -Wformat-security -fwrapv -pipe -fPIE 
> -pie -Wsizeof-pointer-memaccess -Wpacked -std=c++0x  -Wl,-z,relro -Wl,-z,now 
> -Wl,--as-needed -o t/httpd tests/httpd_test.o libgearman/libgearman.la 
> libtest/libtest.la tests/libstartworker.la 
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_server_minor_version'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_server_instance_by_position'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_behavior_set'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_set_sasl_auth_data'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_free'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_flush'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_clone'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_server_major_version'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_version'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_behavior_get'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_server_micro_version'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_server_cursor'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_server_error_return'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_stat_free'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_server_error'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_create'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_stat'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_server_add'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/gearmand_1.1.19.1+ds-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031449: python-scrapy: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10502 hardcoded in zstd

[Lucas Nussbaum]

Source: python-scrapy
Version: 2.8.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> === FAILURES 
> ===
>  ProxyConnectTestCase.test_https_connect_tunnel 
> 
> 
> self =  testMethod=test_https_connect_tunnel>
> 
> def setUp(self):
> try:
> import mitmproxy  # noqa: F401
> except ImportError:
> self.skipTest("mitmproxy is not installed")
> 
> self.mockserver = MockServer()
> self.mockserver.__enter__()
> self._oldenv = os.environ.copy()
> 
> self._proxy = MitmProxy()
> >   proxy_url = self._proxy.start()
> 
> /<>/.pybuild/cpython3_3.11_scrapy/build/tests/test_proxy_connect.py:79:
>  
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> self = 
> 
> def start(self):
> from scrapy.utils.test import get_testenv
> 
> script = """
> import sys
> from mitmproxy.tools.main import mitmdump
> sys.argv[0] = "mitmdump"
> sys.exit(mitmdump())
> """
> cert_path = Path(__file__).parent.resolve() / "keys" / 
> "mitmproxy-ca.pem"
> self.proc = Popen(
> [
> sys.executable,
> "-c",
> script,
> "--listen-host",
> "127.0.0.1",
> "--listen-port",
> "0",
> "--proxyauth",
> f"{self.auth_user}:{self.auth_pass}",
> "--certs",
> str(cert_path),
> "--ssl-insecure",
> ],
> stdout=PIPE,
> env=get_testenv(),
> )
> line = self.proc.stdout.readline().decode("utf-8")
> >   host_port = re.search(r"listening at http://([^:]+:\d+)", 
> > line).group(1)
> E   AttributeError: 'NoneType' object has no attribute 'group'
> 
> /<>/.pybuild/cpython3_3.11_scrapy/build/tests/test_proxy_connect.py:52:
>  AttributeError
> - Captured stderr call 
> -
> Traceback (most recent call last):
>   File "", line 3, in 
>   File "/usr/lib/python3/dist-packages/mitmproxy/tools/main.py", line 9, in 
> 
> from mitmproxy import exceptions, master
>   File "/usr/lib/python3/dist-packages/mitmproxy/master.py", line 7, in 
> 
> from mitmproxy import eventsequence
>   File "/usr/lib/python3/dist-packages/mitmproxy/eventsequence.py", line 6, 
> in 
> from mitmproxy import http
>   File "/usr/lib/python3/dist-packages/mitmproxy/http.py", line 26, in 
> 
> from mitmproxy.net import encoding
>   File "/usr/lib/python3/dist-packages/mitmproxy/net/encoding.py", line 13, 
> in 
> import zstandard as zstd
>   File "/usr/lib/python3/dist-packages/zstandard/__init__.py", line 39, in 
> 
> from .backend_c import *  # type: ignore
> 
> ImportError: zstd C API versions mismatch; Python bindings were not 
> compiled/linked against expected zstd version (10504 returned by the lib, 
> 10502 hardcoded in zstd headers, 10502 hardcoded in the cext)
> __ ProxyConnectTestCase.test_https_tunnel_auth_error 
> ___
> 
> self =  testMethod=test_https_tunnel_auth_error>
> 
> def setUp(self):
> try:
> import mitmproxy  # noqa: F401
> except ImportError:
> self.skipTest("mitmproxy is not installed")
> 
> self.mockserver = MockServer()
> self.mockserver.__enter__()
> self._oldenv = os.environ.copy()
> 
> self._proxy = MitmProxy()
> >   proxy_url = self._proxy.start()
> 
> /<>/.pybuild/cpython3_3.11_scrapy/build/tests/test_proxy_connect.py:79:
>  
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> self = 
> 
> def start(self):
> from scrapy.utils.test import get_testenv
> 
> script = """
> import sys
&

Bug#1031448: fwupd: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmp7p7957mh/./obj-x86_64-linux-gnu/meson-private/tmp7p7957mh/testfile.c:17: undefined reference to `gcab_cabinet_add_allowed_compression

[Lucas Nussbaum]

Source: fwupd
Version: 1.8.10-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  /usr/bin/ld: /tmp/ccLdacAo.o: in function `main':
> ./obj-x86_64-linux-gnu/meson-private/tmp7p7957mh/./obj-x86_64-linux-gnu/meson-private/tmp7p7957mh/testfile.c:17:
>  undefined reference to `gcab_cabinet_add_allowed_compression'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/fwupd_1.8.10-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031447: ffmpeg: FTBFS: src/libavutil/hwcontext_vulkan.c:363:7: error: ‘VK_EXT_VIDEO_DECODE_H264_EXTENSION_NAME’ undeclared here (not in a function); did you mean ‘VK_EXT_VIDEO_ENCODE_H264_EXTENSI

[Lucas Nussbaum]

Source: ffmpeg
Version: 7:5.1.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> gcc -I. -Isrc/ -Wdate-time -D_FORTIFY_SOURCE=2 -U_FORTIFY_SOURCE 
> -D_FORTIFY_SOURCE=2 -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC 
> -DZLIB_CONST -DHAVE_AV_CONFIG_H -DBUILDING_avutil -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-strict-overflow -fstack-protector-all -fPIE   
> -std=c11 -fomit-frame-pointer -fPIC -pthread  -I/usr/include/p11-kit-1  
> -I/usr/include/lilv-0 -I/usr/include/serd-0 -I/usr/include/sord-0 
> -I/usr/include/sratom-0 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/harfbuzz -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/fribidi 
> -I/usr/include/libxml2 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/bs2b-I/usr/include/libdrm -I/usr/include/freetype2 
> -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/fribidi  -DHWY_SHARED_DEFINE  -I/usr/include/mfx  
> -I/usr/include/openjpeg-2.5 -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/opus -I/usr/include/opus  -D_REENTRANT  -I/usr/include/rav1e  
> -I/usr/include/librsvg-2.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/x86_64-linux-gnu -pthread -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/srt 
> -I/usr/include/p11-kit-1 -I/usr/include/svt-av1 -DEB_DLL  
> -DX264_API_IMPORTS   -isystem /usr/include/mit-krb5 -I/usr/include/pgm-5.3 
> -I/usr/include/libxml2  -I/usr/include/libxml2  -I/usr/include/sphinxbase 
> -I/usr/include/pocketsphinx -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/x86_64-linux-gnu/sphinxbase-I/usr/include/libdrm 
> -g -Wdeclaration-after-statement -Wall -Wdisabled-optimization 
> -Wpointer-arith -Wredundant-decls -Wwrite-strings -Wtype-limits -Wundef 
> -Wmissing-prototypes -Wstrict-prototypes -Wempty-body -Wno-parentheses 
> -Wno-switch -Wno-format-zero-length -Wno-pointer-sign 
> -Wno-unused-const-variable -Wno-bool-operation -Wno-char-subscripts -O3 
> -fno-math-errno -fno-signed-zeros -fno-tree-vectorize -Werror=format-security 
> -Werror=implicit-function-declaration -Werror=missing-prototypes 
> -Werror=return-type -Werror=vla -Wformat -fdiagnostics-color=auto 
> -Wno-maybe-uninitialized -I/usr/include/SDL2 -D_REENTRANT   -MMD -MF 
> libavutil/imgutils.d -MT libavutil/imgutils.o -c -o libavutil/imgutils.o 
> src/libavutil/imgutils.c
> src/libavutil/hwcontext_vulkan.c:363:7: error: 
> ‘VK_EXT_VIDEO_DECODE_H264_EXTENSION_NAME’ undeclared here (not in a 
> function); did you mean ‘VK_EXT_VIDEO_ENCODE_H264_EXTENSION_NAME’?
>   363 | { VK_EXT_VIDEO_DECODE_H264_EXTENSION_NAME,
> FF_VK_EXT_NO_FLAG},
>   |   ^~~
>   |   VK_EXT_VIDEO_ENCODE_H264_EXTENSION_NAME
> src/libavutil/hwcontext_vulkan.c:364:7: error: 
> ‘VK_EXT_VIDEO_DECODE_H265_EXTENSION_NAME’ undeclared here (not in a 
> function); did you mean ‘VK_EXT_VIDEO_ENCODE_H265_EXTENSION_NAME’?
>   364 | { VK_EXT_VIDEO_DECODE_H265_EXTENSION_NAME,
> FF_VK_EXT_NO_FLAG},
>   |   ^~~
>   |   VK_EXT_VIDEO_ENCODE_H265_EXTENSION_NAME
> gcc -I. -Isrc/ -Wdate-time -D_FORTIFY_SOURCE=2 -U_FORTIFY_SOURCE 
> -D_FORTIFY_SOURCE=2 -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC 
> -DZLIB_CONST -DHAVE_AV_CONFIG_H -DBUILDING_avutil -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-strict-overflow -fstack-protector-all -fPIE   
> -std=c11 -fomit-frame-pointer -fPIC -pthread  -I/usr/include/p11-kit-1  
> -I/usr/include/lilv-0 -I/usr/include/serd-0 -I/usr/include/sord-0 
> -I/usr/include/sratom-0 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/harfbuzz -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/fribidi 
> -I/usr/include/libxml2 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/bs2b-I/usr/include/libdrm -I/usr/include/freetype2 
> -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/fribidi  -DHWY_SHARED_DEFINE  -I/usr/include/mfx  
>

Bug#1031443: python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10504 hardcoded in z

[Lucas Nussbaum]

Source: python-zstandard
Version: 0.19.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd docs; LC_ALL=C.UTF-8 LANGUAGE=C.UTF-8 sphinx-build -bhtml . _build/html
> Running Sphinx v5.3.0
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 14 source files that are out of date
> updating environment: [new config] 14 added, 0 changed, 0 removed
> reading sources... [  7%] api_usage
> reading sources... [ 14%] buffer
> reading sources... [ 21%] compression_parameters
> reading sources... [ 28%] compressor
> reading sources... [ 35%] concepts
> reading sources... [ 42%] contributing
> reading sources... [ 50%] decompressor
> reading sources... [ 57%] dictionaries
> reading sources... [ 64%] index
> reading sources... [ 71%] installing
> reading sources... [ 78%] misc_apis
> reading sources... [ 85%] multithreaded
> reading sources... [ 92%] news
> reading sources... [100%] projectinfo
> 
> WARNING: autodoc: failed to import class 'BufferSegment' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'BufferSegments' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'BufferWithSegments' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'BufferWithSegmentsCollection' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionParameters' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressor' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionWriter' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionReader' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionObj' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionChunker' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdDecompressor' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdDecompressionWriter' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdDecompressionReader' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdDecompressionObj' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionDict' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'train_dictionary' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'get_frame_parameters' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'frame_header_size' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'frame_content_size' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'FrameParameters' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 
> 'estimate_decompression_context_size' from module 'zstandard'; the following 
> exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'open' from module 'zstandard'; 
> the following exception was raised:
> No module named 

Bug#1031446: lomiri-ui-toolkit: FTBFS: QWARN : components::UnknownTestFunc() file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtTest/SignalSpy.qml:258: Error: Invalid write to global property "qtest_count"

[Lucas Nussbaum]

Source: lomiri-ui-toolkit
Version: 1.3.5000+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> Creating QML component for Lomiri.Metrics
> Failed to load Lomiri.Metrics
> import QtQuick 2.0
> import Lomiri.Metrics 0.1 as ALomiri_Metrics_0_1
> QtObject { }
> 
> file:///<>/qml/Lomiri/Metrics/qmldir:2:1: plugin cannot be 
> loaded for module "Lomiri.Metrics": Cannot protect module Lomiri.Metrics 0 as 
> it was never registered
> make[3]: *** [Makefile:745: check] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/lomiri-ui-toolkit_1.3.5000+dfsg-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031445: camv-rnd: FTBFS: build-dependency not installable: librnd4-dev (>= 3.2.0)

[Lucas Nussbaum]

Source: camv-rnd
Version: 1.1.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 11), librnd4-dev (>= 3.2.0), libgd-dev, 
> libgtkglext1-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 11), librnd4-dev (>= 3.2.0), libgd-dev, 
> libgtkglext1-dev, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [394 B]
> Get:5 copy:/<>/apt_archive ./ Packages [474 B]
> Fetched 1825 B in 0s (139 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: librnd4-dev (>= 3.2.0) but it is 
> not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/camv-rnd_1.1.1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031444: poetry: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: poetry
Version: 1.3.2+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:107: Building wheel for python3.11 with "build" 
> module
> I: pybuild base:240: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.11_poetry 
> * Building wheel...
> Successfully built poetry-1.3.2-py3-none-any.whl
> I: pybuild plugin_pyproject:119: Unpacking wheel built for python3.11 with 
> "installer" module
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_poetry/build; 
> python3.11 -m pytest --ignore=tests/console/commands/env/test_list.py 
> --ignore=tests/console/commands/env/test_remove.py 
> --ignore=tests/console/commands/env/test_use.py 
> --ignore=tests/utils/test_env.py --ignore=tests/config/test_config.py 
> --ignore=tests/utils/test_helpers.py -k 'not 
> test_self_update_should_install_all_necessary_elements and not 
> test_add_file_constraint_sdist and not 
> test_add_file_constraint_sdist_old_installer and not test_publish_dry_run and 
> not test_info_from_sdist and not 
> test_installer_can_install_dependencies_from_forced_source and not 
> test_search_for_file_sdist and not test_search_for_file_sdist_with_extras and 
> not test_solver_can_resolve_sdist_dependencies and not 
> test_solver_can_resolve_sdist_dependencies_with_extras and not 
> test_solver_chooses_from_correct_repository_if_forced and not 
> test_solver_chooses_from_correct_repository_if_forced_and_transitive_dependency
>  and not test_solver_does_not_choose_from_secondary_repository_by_default and 
> not test_solver_chooses_from_secondary_if_explicit and not 
> test_get_package_information_fallback_read_setup and not 
> test_get_package_information_skips_dependencies_with_invalid_constraints and 
> not test_get_package_retrieves_packages_with_no_hashes and not 
> test_fallback_can_read_setup_to_get_dependencies and not 
> test_exporter_can_export_requirements_txt_with_file_packages and not 
> test_exporter_can_export_requirements_txt_with_file_packages_and_markers and 
> not test_lock_no_update and not 
> test_locker_dumps_dependency_information_correctly and not 
> test_package_partial_yank and not 
> test_run_installs_with_same_version_url_files and not 
> test_env_info_displays_complete_info and not test_skip_existing_output and 
> not 
> test_installer_should_use_the_locked_version_of_git_dependencies_with_extras 
> and not 
> test_installer_should_use_the_locked_version_of_git_dependencies_without_reference
>  and not test_installer_uses_prereleases_if_they_are_compatible and not 
> test_requirement_git_subdirectory and not test_check_valid and not 
> test_check_invalid and not test_packages_property_returns_empty_list and not 
> test_parse_dependency_specification and not 
> test_info_setup_missing_mandatory_should_trigger_pep517 and not 
> test_uninstall_git_package_nspkg_pth_cleanup and not 
> test_executor_should_write_pep610_url_references_for_directories and not 
> test_executor_should_write_pep610_url_references_for_git and not 
> test_executor_should_write_pep610_url_references_for_git_with_subdirectories'
> = test session starts 
> ==
> platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack
> rootdir: /<>, configfile: pyproject.toml
> plugins: xdist-3.1.0, mock-3.8.2
> gw0 I / gw1 I / gw2 I / gw3 I / gw4 I / gw5 I / gw6 I / gw7 I
> gw0 [1051] / gw1 [1051] / gw2 [1051] / gw3 [1051] / gw4 [1051] / gw5 [1051] / 
> gw6 [1051] / gw7 [1051]
> 
>  [  
> 6%]
>  [ 
> 13%]
> . [ 
> 20%]
> s [ 
> 27%]
>  [ 
> 34%]
> ..F.. [ 
> 41%]
> ..s. [ 
> 48%]
> ...

Bug#1031438: qca2: FTBFS: dh_auto_test: error: cd build && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2

[Lucas Nussbaum]

Source: qca2
Version: 2.3.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/build'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process --verbose -j8
> UpdateCTestConfiguration  from :/<>/build/DartConfiguration.tcl
> UpdateCTestConfiguration  from :/<>/build/DartConfiguration.tcl
> Test project /<>/build
> Constructing a list of tests
> Done constructing a list of tests
> Updating test list for fixtures
> Added 0 tests to meet fixture requirements
> Checking test dependency graph...
> Checking test dependency graph end
> test 1
>   Start  1: Base64
> 
> 1: Test command: /<>/build/bin/base64unittest
> 1: Working Directory: /<>/build/bin
> 1: Test timeout computed to be: 1000
> test 2
>   Start  2: BigInteger
> 
> 2: Test command: /<>/build/bin/bigintunittest
> 2: Working Directory: /<>/build/bin
> 2: Test timeout computed to be: 1000
> test 3
>   Start  3: Certificate
> 
> 3: Test command: /<>/build/bin/certunittest
> 3: Working Directory: /<>/build/bin
> 3: Test timeout computed to be: 1000
> test 4
>   Start  4: SymmetricCipher
> 
> 4: Test command: /<>/build/bin/cipherunittest
> 4: Working Directory: /<>/build/bin
> 4: Test timeout computed to be: 1000
> test 5
>   Start  5: ClientSidePlugin
> 
> 5: Test command: /<>/build/bin/clientplugin
> 5: Working Directory: /<>/build/bin
> 5: Test timeout computed to be: 1000
> test 6
>   Start  6: DigitalSignatureAlgorithm
> 
> 6: Test command: /<>/build/bin/dsaunittest
> 6: Working Directory: /<>/build/bin
> 6: Test timeout computed to be: 1000
> test 7
>   Start  7: FileWatch
> 
> 7: Test command: /<>/build/bin/filewatchunittest
> 7: Working Directory: /<>/build/bin
> 7: Test timeout computed to be: 1000
> test 8
>   Start  8: Hashing
> 
> 8: Test command: /<>/build/bin/hashunittest
> 8: Working Directory: /<>/build/bin
> 8: Test timeout computed to be: 1000
> 1: * Start testing of Base64UnitTest *
> 1: Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 12.2.0), debian unknown
> 1: PASS   : Base64UnitTest::initTestCase()
> 1: PASS   : Base64UnitTest::test1(31)
> 1: PASS   : Base64UnitTest::test1(235c91)
> 1: PASS   : Base64UnitTest::test1(414)
> 1: PASS   : Base64UnitTest::test1(241)
> 1: PASS   : Base64UnitTest::test1(313)
> 1: PASS   : Base64UnitTest::test1(60e)
> 1: PASS   : Base64UnitTest::test1(3134)
> 1: PASS   : Base64UnitTest::test2(www.python.org)
> 1: PASS   : Base64UnitTest::test2(a)
> 1: PASS   : Base64UnitTest::test2(ab)
> 1: PASS   : Base64UnitTest::test2(abc)
> 1: PASS   : Base64UnitTest::test2(empty)
> 1: PASS   : Base64UnitTest::test2(a-Z)
> 1: PASS   : Base64UnitTest::test2(31)
> 1: PASS   : Base64UnitTest::test2(QCA_2.0)
> 1: PASS   : Base64UnitTest::test2(j-0)
> 1: PASS   : Base64UnitTest::cleanupTestCase()
> 1: Totals: 18 passed, 0 failed, 0 skipped, 0 blacklisted, 1ms
> 1: * Finished testing of Base64UnitTest *
> 2: * Start testing of BigIntUnitTest *
> 2: Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 12.2.0), debian unknown
> 2: PASS   : BigIntUnitTest::initTestCase()
> 3: * Start testing of CertUnitTest *
> 3: Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 12.2.0), debian unknown
> 3: PASS   : CertUnitTest::initTestCase()
> 4: * Start testing of CipherUnitTest *
> 4: Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 12.2.0), debian unknown
> 4: PASS   : CipherUnitTest::initTestCase()
> 5: * Start testing of ClientPlugin *
> 5: Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 12.2.0), debian unknown
> 5: PASS   : ClientPlugin::initTestCase()
> 5: PASS   : ClientPlugin::testInsertRemovePlugin()
> 5: PASS   : ClientPlugin::cleanupTestCase()
> 6: * Start testing of DSAUnitTest *
> 6: Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 12.2.0), debian unknown
> 6: PASS   : DSAUnitTest::initTestCase()
>

Bug#1031442: gnustep-base: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 messages=yes returned exit code 2

[Lucas Nussbaum]

Source: gnustep-base
Version: 1.28.1+really1.28.0-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>/Tests'
> (\
> GNUSTEP_LOCAL_ADDITIONAL_MAKEFILES="/<>/base.make";\
> ADDITIONAL_INCLUDE_DIRS="-I/<>/Headers 
> -I/<>/Source/.";\
> ADDITIONAL_LIB_DIRS="-L/<>/Source/./obj";\
> ADDITIONAL_LDFLAGS="-Wl,-rpath,/<>/Source/./obj";\
> LD_LIBRARY_PATH="/<>/Source/./obj:";\
> PATH="/<>/Tools/./obj:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games";\
> export GNUSTEP_LOCAL_ADDITIONAL_MAKEFILES;\
> export ADDITIONAL_INCLUDE_DIRS;\
> export ADDITIONAL_LDFLAGS;\
> export ADDITIONAL_LIB_DIRS;\
> export LD_LIBRARY_PATH;\
> export PATH;\
> if [ "no" = "yes" ]; then \
>   gnustep-tests --debug 'base/';\
> else \
>   gnustep-tests 'base/';\
> fi; \
> )
> --- Running tests in base/Functions ---
> --- Running tests in base/GSMime ---
> --- Running tests in base/GSTLS ---
> --- Running tests in base/GSXML ---
> --- Running tests in base/GarbageCollection ---
> --- Running tests in base/KVC ---
> --- Running tests in base/NSAffineTransform ---
> --- Running tests in base/NSArchiver ---
> --- Running tests in base/NSArray ---
> 
> base/NSArray/basic.m:
> Skipped set:   basic.m 46 ... No collection subscripting support in the 
> compiler.
> 
> base/NSArray/blocks.m:
> Skipped set:   blocks.m 76 ... No Blocks support in the compiler.
> --- Running tests in base/NSAttributedString ---
> --- Running tests in base/NSAutoreleasePool ---
> --- Running tests in base/NSBundle ---
> 
> base/NSBundle/general.m:
> Skipped set: general.m 25 ... it looks like GNUstep-base is not yet 
> installed
> 
> base/NSBundle/resources.m:
> Skipped set:   resources.m 48 ... it looks like GNUstep-base is not yet 
> installed
> --- Running tests in base/NSCache ---
> --- Running tests in base/NSCalendar ---
> --- Running tests in base/NSCalendarDate ---
> 
> base/NSCalendarDate/test00.m:
> Failed file: test00.m aborted without running all tests!
> --- Running tests in base/NSCharacterSet ---
> --- Running tests in base/NSConnection ---
> --- Running tests in base/NSCountedSet ---
> --- Running tests in base/NSData ---
> 
> base/NSData/general.m:
> Skipped set:   general.m 128 ... No Blocks support in the compiler.
> --- Running tests in base/NSDate ---
> --- Running tests in base/NSDateFormatter ---
> --- Running tests in base/NSDictionary ---
> 
> base/NSDictionary/basic.m:
> Skipped set:   basic.m 41 ... No dictionary subscripting support in the 
> compiler.
> 
> base/NSDictionary/blocks.m:
> Skipped set:   blocks.m 49 ... No Blocks support in the compiler.
> 
> base/NSDictionary/sort.m:
> Skipped set:   sort.m 54 ... No Blocks support in the compiler.
> --- Running tests in base/NSDistributedLock ---
> --- Running tests in base/NSException ---
> --- Running tests in base/NSFileHandle ---
> --- Running tests in base/NSFileManager ---
> --- Running tests in base/NSHTTPCookie ---
> --- Running tests in base/NSHashTable ---
> 
> base/NSHashTable/weakObjects.m:
> Skipped set:   weakObjects.m 15 ... ARC support unavailable
> --- Running tests in base/NSHost ---
> --- Running tests in base/NSIndexPath ---
> --- Running tests in base/NSInvocation ---
> --- Running tests in base/NSInvocationOperation ---
> --- Running tests in base/NSJSONSerialization ---
> --- Running tests in base/NSKeyedArchiver ---
> --- Running tests in base/NSLocale ---
> --- Running tests in base/NSLock ---
> --- Running tests in base/NSMapTable ---
> 
> base/NSMapTable/weakObjects.m:
> Skipped set:   weakObjects.m 15 ... ARC support unavailable
> --- Running tests in base/NSMethodSignature ---
> --- Running tests in base/NSMutableArray ---
> --- Running tests in base/NSMutableAttributedString ---
> --- Running tests in base/NSMutableCharacterSet ---
> --- Running tests in base/NSMutableData ---
> --- Running tests in base/NSMutableDictionary ---
> --- Running tests in base/NSMutableIndexSet ---
> 
> base/NSMutableIndexSet/blocks.m:
> Skipped set:   blocks.m 83 ... No Blocks support in the compiler.
> --- Running tests in base/NSMutableSet ---
> --- Running tests in base/NSMutableString ---
> --- Running tests in base/NSNotification ---
> --- Running tests in base/NSNumber ---
> --- Running tests in base/NSNumberFormatter -

Bug#1031441: ruby-github-api: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'oauth2' (~> 1

[Lucas Nussbaum]

Source: ruby-github-api
Version: 0.19.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block 
> in activate_dependencies': Could not find 'oauth2' (~> 1.0) among 106 total 
> gem(s) (Gem::MissingSpecError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-github-api/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0'
>  at: 
> /<>/debian/ruby-github-api/usr/share/rubygems-integration/all/specifications/github_api-0.19.0.gemspec,
>  execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not 
> find 'oauth2' (~> 1.0) - did find: [oauth2-2.0.7] 
> (Gem::MissingSpecVersionError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-github-api/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0'
>  , execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> abbrev (default: 0.1.0)
> addressable (2.8.1)
> atomic (1.1.16)
> base64 (default: 0.1.1)
> benchmark (default: 0.2.0)
> bigdecimal (default: 3.1.1)
> bundler (default: 2.3.7)
> cgi (default: 0.3.5)
> csv (default: 3.2.2)
> date (default: 3.2.2)
> debug (1.4.0)
> delegate (default: 0.2.0)
> descendants_tracker (0.0.4)
> did_you_mean (default: 1.6.1)
> digest (default: 3.1.0)
> drb (default: 2.1.0)
> english (default: 0.7.1)
> erb (default: 2.2.3)
> error_highlight (default: 0.3.0)
> etc (default: 1.3.0)
> faraday (1.1.0)
> fcntl (default: 1.0.1)
> fiddle (default: 1.1.0)
> fileutils (default: 1.6.0)
> find (default: 0.1.1)
> forwardable (default: 1.3.2)
> getoptlong (default: 0.1.1)
> hashie (5.0.0)
> io-console (default: 0.5.11)
> io-nonblock (default: 0.1.0)
> io-wait (default: 0.2.1)
> ipaddr (default: 1.2.4)
> irb (default: 1.4.1)
> json (default: 2.6.1)
> jwt (2.5.0)
> logger (default: 1.5.0)
> matrix (0.4.2)
> minitest (5.15.0)
> multi_json (1.14.1)
> multi_xml (0.6.0)
> multipart-post (2.0.0)
> mutex_m (default: 0.1.1)
> net-ftp (0.1.3)
> net-http (default: 0.2.0)
> net-imap (0.2.3)
> net-pop (0.1.1)
> net-protocol (default: 0.1.2)
> net-smtp (0.3.1)
> net-telnet (0.2.0)
> nkf (default: 0.1.1)
> oauth2 (2.0.7)
> observer (default: 0.1.1)
> open-uri (default: 0.2.0)
> open3 (default: 0.1.1)
> openssl (default: 3.0.0)
> optparse (default: 0.2.0)
> ostruct (default: 0.5.2)
> pathname (default: 0.2.0)
> power_assert (2.0.1)
> pp (default: 0.3.0)
> prettyprint (default: 0.1.1)
> prime (0.1.2)
> pstore (default: 0.1.1)
> psych (default: 4.0.3)
> public_suffix (4.0.6)
> racc (default: 1.

Bug#1031440: open-vm-tools: FTBFS: fuse_config.h:42: error: "PACKAGE_VERSION" redefined [-Werror]

[Lucas Nussbaum]

Source: open-vm-tools
Version: 2:12.1.5-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> gcc -DPACKAGE_NAME=\"open-vm-tools\" -DPACKAGE_TARNAME=\"open-vm-tools\" 
> -DPACKAGE_VERSION=\"12.1.5\" -DPACKAGE_STRING=\"open-vm-tools\ 12.1.5\" 
> -DPACKAGE_BUGREPORT=\"open-vm-tools-de...@lists.sourceforge.net\" 
> -DPACKAGE_URL=\"\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_TIME_H=1 -DSTDC_HEADERS=1 
> -DPACKAGE=\"open-vm-tools\" -DVERSION=\"12.1.5\" -DHAVE_DLFCN_H=1 
> -DLT_OBJDIR=\".libs/\" -DHAVE_FUSE3=1 -DFUSE_USE_VERSION=35 
> -DHAVE_X11_SM_SMLIB_H=1 -DHAVE_X11_ICE_ICELIB_H=1 
> -DHAVE_X11_EXTENSIONS_XCOMPOSITE_H=1 -DHAVE_DLOPEN=1 -DHAVE_ECVT=1 
> -DHAVE_FCVT=1 -DNO_DNET=1 -DHAVE_CRYPT_H=1 -DHAVE_INTTYPES_H=1 
> -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_WCHAR_H=1 -DHAVE_SYS_IO_H=1 
> -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_SYSINFO_H=1 -DHAVE_SYS_TYPES_H=1 
> -DHAVE_SYS_USER_H=1 -DHAVE_SYS_VFS_H=1 -DHAVE_UNWIND_H=1 -DHAVE__BOOL=1 
> -DHAVE_STDBOOL_H=1 -DHAVE_STRUCT_STAT_ST_RDEV=1 -DTIME_WITH_SYS_TIME=1 -I.   
> -I/<>/open-vm-tools/lib/include 
> -I/<>/open-vm-tools/lib/include -Wdate-time -D_FORTIFY_SOURCE=2 
> -DUSING_AUTOCONF=1 -DOPEN_VM_TOOLS -DUSE_VGAUTH  -DNO_ICU -DVMX86_TOOLS 
> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_XOPEN_SOURCE=500 
> -D_BSD_SOURCE -D_SVID_SOURCE -D_DEFAULT_SOURCE -DENABLE_RESOLUTIONKMS 
> -Dvmblock_fuse -U_XOPEN_SOURCE -D_XOPEN_SOURCE=600 -DUSERLEVEL 
> -D_FILE_OFFSET_BITS=64 -I/usr/include/fuse3  -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I../modules/shared/vmblock -I. 
> -fPIC -Wno-error=deprecated-declarations -Wno-error=address-of-packed-member 
> -Wno-nonnull -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror 
> -Wno-pointer-sign -Wno-unused-value -fno-strict-aliasing -Wno-unknown-pragmas 
> -Wno-uninitialized -Wno-deprecated-declarations -Wno-unused-const-variable 
> -Wno-unused-but-set-variable -c -o stubs.o `test -f 
> '../modules/shared/vmblock/stubs.c' || echo 
> './'`../modules/shared/vmblock/stubs.c
> In file included from /usr/include/fuse3/fuse_common.h:17,
>  from /usr/include/fuse3/fuse.h:19,
>  from fsops.h:46,
>  from main.c:28:
> /usr/include/fuse3/fuse_config.h:42: error: "PACKAGE_VERSION" redefined 
> [-Werror]
>42 | #define PACKAGE_VERSION "3.13.1"
>   | 
> : note: this is the location of the previous definition
> cc1: all warnings being treated as errors
> make[2]: *** [Makefile:582: main.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/open-vm-tools_12.1.5-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031439: gcc-sh-elf: FTBFS: make[6]: *** No rule to make target '../libsframe/libsframe.la', needed by 'libbfd.la'. Stop.

[Lucas Nussbaum]

Source: gcc-sh-elf
Version: 4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[6]: Entering directory '/<>/bld/bfd/po'
> make[6]: Nothing to be done for 'all'.
> make[6]: Leaving directory '/<>/bld/bfd/po'
> /bin/sh ./libtool --tag=CC --tag=disable-static  --mode=link 
> x86_64-linux-gnu-gcc -Wall -fcf-protection -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wc,-static-libgcc  -module -avoid-version -bindir /usr/libexec/gcc/sh-elf/12 
> -Wl,--version-script=../../src/lto-plugin/lto-plugin.map-Xcompiler 
> '-static-libstdc++' -Xcompiler '-static-libgcc' '-Wl,-z,relro' '-Wl,-z,now' 
> -o liblto_plugin.la -rpath /usr/libexec/gcc/sh-elf/12 lto-plugin.lo  
> -Wc,../libiberty/pic/libiberty.a 
> yes
> checking whether the compiler supports the __inline keyword... make[6]: 
> Entering directory '/<>/bld/bfd'
> rm -f bfd-tmp.h
> cp bfd-in3.h bfd-tmp.h
> /bin/sh ../../src/bfd/../move-if-change bfd-tmp.h bfd.h
> rm -f bfd-tmp.h
> touch stmp-bfd-h
> rm -f tofiles
> make[6]: *** No rule to make target '../libsframe/libsframe.la', needed by 
> 'libbfd.la'.  Stop.
> make[6]: *** Waiting for unfinished jobs
> f=""; \
> for i in elf32-sh.lo elf-vxworks.lo elf32.lo elf.lo elflink.lo elf-attrs.lo 
> elf-strtab.lo elf-eh-frame.lo elf-sframe.lo dwarf1.lo dwarf2.lo coff-sh.lo 
> cofflink.lo coffgen.lo elf32-gen.lo plugin.lo cpu-sh.lo  archive64.lo ; do \
>   case " $f " in \
> *" $i "*) ;; \
> *) f="$f $i" ;; \
>   esac ; \
> done ; \
> echo $f > tofiles
> /bin/sh ../../src/bfd/../move-if-change tofiles ofiles
> libtool: link: x86_64-linux-gnu-gcc -shared  -fPIC -DPIC  .libs/lto-plugin.o  
>   -static-libgcc -Wl,--version-script=../../src/lto-plugin/lto-plugin.map 
> -static-libstdc++ -static-libgcc -Wl,-z -Wl,relro -Wl,-z -Wl,now 
> ../libiberty/pic/libiberty.a   -Wl,-soname -Wl,liblto_plugin.so -o 
> .libs/liblto_plugin.so
> touch stamp-ofiles
> rm -f libcpp.a
> make[6]: Leaving directory '/<>/bld/bfd'
> x86_64-linux-gnu-ar cru libcpp.a charset.o directives.o errors.o expr.o 
> files.o identifiers.o init.o lex.o line-map.o macro.o mkdeps.o pch.o symtab.o 
> traditional.o
> make[5]: *** [Makefile:1955: all-recursive] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/gcc-sh-elf_4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=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.

Bug#1031433: diffoscope: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: diffoscope
Version: 235
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> { cat diffoscope.h2m.0; cat ../README.rst | \
>   sed -e '/^\.\. raw:: /d' -e '/^\.\. image:: /d' -e '/ :target: /d' | tee 
> out.txt | \
>   rst2man -q --no-doc-title | \
>   sed -e 's,^ \\- ,,' -e 's,^\[,\\[char91],g' -e 's,\.TH *"" "" "",,g' \
>   -e 's,bin/diffoscope,diffoscope,g' \
>   -e 's,\.SH \(.*\),[\1],g' -e 's,\[diffoscope\],[DESCRIPTION],gi'; } > 
> "diffoscope.h2m"
> help2man --version-string=$(cd .. && python3 setup.py -V) ../bin/diffoscope 
> -N --include="diffoscope.h2m" | \
>   sed -e '/end_of_description_header/,/positional arguments/{d}' > 
> "diffoscope.1"
> make[2]: Leaving directory '/<>/doc'
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild pybuild:307: flake8 --config=/dev/null --select=F821
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; 
> python3.11 -m pytest -vv -r sxX -l --cov=diffoscope --cov-report=term-missing 
> --cov-report=html
> = test session starts 
> ==
> platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack -- 
> /usr/bin/python3.11
> cachedir: .pytest_cache
> rootdir: /<>, configfile: pytest.ini
> plugins: cov-4.0.0
> collecting ... collected 711 items / 1 skipped
> 
> tests/test_diff_mask.py::test_none PASSED[  
> 0%]
> tests/test_diff_mask.py::test_all PASSED [  
> 0%]
> tests/test_diff_mask.py::test_specific PASSED[  
> 0%]
> tests/test_difference.py::test_too_much_input_for_diff PASSED[  
> 0%]
> tests/test_difference.py::test_too_long_diff_block_lines PASSED  [  
> 0%]
> tests/test_difference.py::test_size_updates PASSED   [  
> 0%]
> tests/test_difference.py::test_traverse_heapq PASSED [  
> 0%]
> tests/test_difference.py::test_non_str_arguments_to_source1_source2 PASSED [  
> 1%]
> tests/test_difference.py::test_adjust_diff_context PASSED[  
> 1%]
> tests/test_excludes.py::test_none PASSED [  
> 1%]
> tests/test_excludes.py::test_all PASSED  [  
> 1%]
> tests/test_excludes.py::test_specific PASSED [  
> 1%]
> tests/test_excludes.py::test_specific_case PASSED[  
> 1%]
> tests/test_excludes.py::test_multiple PASSED [  
> 1%]
> tests/test_excludes.py::test_nomatch PASSED  [  
> 2%]
> tests/test_excludes.py::test_wildcard PASSED [  
> 2%]
> tests/test_main.py::test_non_existing_files PASSED   [  
> 2%]
> tests/test_main.py::test_non_existing_left_with_new_file PASSED  [  
> 2%]
> tests/test_main.py::test_non_existing_right_with_new_file PASSED [  
> 2%]
> tests/test_main.py::test_non_existing_files_with_new_file PASSED [  
> 2%]
> tests/test_main.py::test_remove_temp_files_on_sigterm PASSED [  
> 2%]
> tests/test_main.py::test_ctrl_c_handling PASSED  [  
> 3%]
> tests/test_main.py::test_no_differences PASSED   [  
> 3%]
> tests/test_main.py::test_no_differences_directories PASSED   [  
> 3%]
> tests/test_main.py::test_list_tools PASSED   [  
> 3%]
> tests/test_main.py::test_list_missing_tools PASSED   [  
> 3%]
> tests/test_main.py::test_profiling PASSED[  
> 3%]
> tests/test_main.py::test_non_unicode_filename PASSED [  
> 3%]
> tests/test_main.py::test_help PASSED [  
> 4%]
> tests/test_main.py::test_usage PASSED[  
> 4%]
> tests/test_presenters.py::test_text_option_is_default PASSED [  
> 4%]
> tests/test_presenters.py::test_text_proper_indentation PASSED[  
> 4%]
> tests/test_presenters.py::test_text_option_color PASSED  [  
> 4%]
> tests/test_presenters.py::test_text_option_with_file PASSED  [  
> 4%]
> tests/test_presenters.py::test_text_option_with_stdout PASSED[  
> 4%]
> tests/test_presenters.py::

Bug#1031437: pandas: FTBFS: /usr/lib/python3/dist-packages/dateutil/zoneinfo/__init__.py:26: UserWarning: I/O error(2): No such file or directory

[Lucas Nussbaum]

Source: pandas
Version: 1.5.3+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> _ test_expanding_apply_consistency_sum_nans[all_data17-2-sum] 
> __
> request =  test_expanding_apply_consistency_sum_nans[all_data17-2-sum]>>
> all_data =  0
> 0  NaN
> 1  1.0
> 2  NaN
> 3  3.0
> 4  2.0, min_periods = 2
> f = 
> 
> @pytest.mark.parametrize("f", [lambda v: Series(v).sum(), np.nansum, 
> np.sum])
> def test_expanding_apply_consistency_sum_nans(request, all_data, 
> min_periods, f):
> if f is np.sum:
> if not no_nans(all_data) and not (
> all_na(all_data) and not all_data.empty and min_periods > 0
> ):
> request.node.add_marker(
> pytest.mark.xfail(reason="np.sum has different behavior 
> with NaNs")
> )
> expanding_f_result = all_data.expanding(min_periods=min_periods).sum()
> expanding_apply_f_result = 
> all_data.expanding(min_periods=min_periods).apply(
> func=f, raw=True
> )
> >   tm.assert_equal(expanding_f_result, expanding_apply_f_result)
> 
> pandas/tests/window/moments/test_moments_consistency_expanding.py:29: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> pandas/_libs/testing.pyx:52: in pandas._libs.testing.assert_almost_equal
> cpdef assert_almost_equal(a, b,
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> >   raise_assert_detail(obj, msg, lobj, robj, index_values=index_values)
> E   AssertionError: DataFrame.iloc[:, 0] (column name="0") are different
> E   
> E   DataFrame.iloc[:, 0] (column name="0") values are different (40.0 %)
> E   [index]: [0, 1, 2, 3, 4]
> E   [left]:  [nan, nan, nan, 4.0, 6.0]
> E   [right]: [nan, nan, nan, nan, nan]
> 
> pandas/_libs/testing.pyx:167: AssertionError
> - generated xml file: 
> /<>/.pybuild/cpython3_3.11/build/test-data.xml -
> = slowest 30 durations 
> =
> 0.69s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_center_reindex_frame[False]
> 0.32s call 
> .pybuild/cpython3_3.11/build/pandas/tests/groupby/test_timegrouper.py::TestGroupBy::test_timegrouper_with_reg_groups
> 0.24s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_time_rule_frame[False]
> 0.18s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_frame[False]
> 0.12s call 
> .pybuild/cpython3_3.11/build/pandas/tests/groupby/test_timegrouper.py::TestGroupBy::test_groupby_with_timegrouper
> 0.07s call 
> .pybuild/cpython3_3.11/build/pandas/tests/groupby/test_timegrouper.py::TestGroupBy::test_groupby_apply_timegrouper_with_nat_apply_squeeze
> 0.07s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_center_reindex_series[False]
> 0.06s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_min_periods[False-None-0]
> 0.06s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_min_periods[False-1-0]
> 0.05s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_nans[False]
> 0.04s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_time_rule_frame[True]
> 0.04s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_center_reindex_frame[True]
> 0.04s call 
> .pybuild/cpython3_3.11/build/pandas/tests/groupby/test_timegrouper.py::TestGroupBy::test_timegrouper_get_group
> 0.03s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_min_periods[False-2-0]
> 0.03s call 
> .pybuild/cpython3_3.11/build/pandas/tests/groupby/test_timegrouper.py::TestGroupBy::test_timegrouper_with_reg_groups_freq[A]
> 0.03s call 
> .pybuild/cpython3_3.11/build/pandas/tests/groupby/test_timegrouper.py::TestGroupBy::test_timegrouper_with_reg_groups_freq[D]
> 0.03s call 
> .pybuild/cpython3_3.11/build/pandas/tests/groupby/test_timegrouper.py::TestGroupBy::test_timegrouper_with_reg_groups_freq[M]
> 0.03s call 
> .pybuild/cpython3_3.11/build/pandas/tests/groupby/test_timegrouper.py::TestGroupBy::test_groupby_groups_datetimeindex_tz
> 0.03s setup
> .pybuild/cpython3_3.11/build/pandas/tests/groupby/test_timegrouper.py::TestGroupBy::test_groupby_apply_timegrouper_with_nat_dict_returns
> 0.03s cal

Bug#1031436: ubuntu-dev-tools: FTBFS: make[1]: *** [debian/rules:10: override_dh_auto_test] Error 1

[Lucas Nussbaum]

Source: ubuntu-dev-tools
Version: 0.192
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ./run-linters
> Running black...
> --- build/scripts-3.11/grep-merges2023-02-17 01:30:48.860507 +
> +++ build/scripts-3.11/grep-merges2023-02-17 01:30:49.805230 +
> @@ -52,11 +52,10 @@
>  "universe",
>  "universe-manual",
>  "multiverse",
>  "multiverse-manual",
>  ):
> -
>  url = f"https://merges.ubuntu.com/{component}.json;
>  try:
>  headers, page = Http().request(url)
>  except HttpLib2Error as e:
>  Logger.exception(e)
> would reformat build/scripts-3.11/grep-merges
> --- /<>/ubuntutools/misc.py  2023-02-01 11:45:15 +
> +++ /<>/ubuntutools/misc.py  2023-02-17 01:30:49.837949 +
> @@ -242,11 +242,11 @@
>  filesize = path.stat().st_size
>  if size and size != filesize:
>  Logger.error("File %s incorrect size, got %s expected %s", path, 
> filesize, size)
>  return False
>  
> -for (alg, checksum) in checksums.items():
> +for alg, checksum in checksums.items():
>  hash_ = hashlib.new(alg)
>  with path.open("rb") as f:
>  while True:
>  block = f.read(hash_.block_size)
>  if len(block) == 0:
> would reformat /<>/ubuntutools/misc.py
> --- grep-merges   2023-02-01 11:45:15 +
> +++ grep-merges   2023-02-17 01:30:50.160956 +
> @@ -52,11 +52,10 @@
>  "universe",
>  "universe-manual",
>  "multiverse",
>  "multiverse-manual",
>  ):
> -
>  url = f"https://merges.ubuntu.com/{component}.json;
>  try:
>  headers, page = Http().request(url)
>  except HttpLib2Error as e:
>  Logger.exception(e)
> would reformat grep-merges
> --- build/scripts-3.11/ubuntu-upload-permission   2023-02-17 
> 01:30:48.864507 +
> +++ build/scripts-3.11/ubuntu-upload-permission   2023-02-17 
> 01:30:50.219040 +
> @@ -89,11 +89,10 @@
>  component = spph.getComponent()
>  if args.list_uploaders and (
>  pocket != "Release"
>  or series.status in ("Experimental", "Active Development", 
> "Pre-release Freeze")
>  ):
> -
>  component_uploader = 
> archive.getUploadersForComponent(component_name=component)[0]
>  Logger.info("All upload permissions for %s:", args.package)
>  Logger.info("")
>  Logger.info("Component (%s)", component)
>  Logger.info("%s", "=" * len(component))
> would reformat build/scripts-3.11/ubuntu-upload-permission
> --- ubuntu-upload-permission  2023-02-01 11:45:15 +
> +++ ubuntu-upload-permission  2023-02-17 01:30:50.476410 +
> @@ -89,11 +89,10 @@
>  component = spph.getComponent()
>  if args.list_uploaders and (
>  pocket != "Release"
>  or series.status in ("Experimental", "Active Development", 
> "Pre-release Freeze")
>  ):
> -
>  component_uploader = 
> archive.getUploadersForComponent(component_name=component)[0]
>  Logger.info("All upload permissions for %s:", args.package)
>  Logger.info("")
>  Logger.info("Component (%s)", component)
>  Logger.info("%s", "=" * len(component))
> would reformat ubuntu-upload-permission
> --- /<>/ubuntutools/lp/lpapicache.py 2023-02-01 11:45:15 
> +
> +++ /<>/ubuntutools/lp/lpapicache.py 2023-02-17 
> 01:30:50.905615 +
> @@ -410,11 +410,11 @@
>  def binaryFileProperties(self, filename_or_url):
>  if not self._binary_prop_dict:
>  urls = self.binaryFileUrls()
>  props = self.getBinaryProperties()
>  self._binary_prop_dict = dict(zip(urls, props))
> -for (key, value) in copy(self._binary_prop_dict).items():
> +for key, value in copy(self._binary_prop_dict).items():
>      filename = os.path.basename(urlparse(key).path)
>  self._binary_prop_dict[filename] = value
>  return self._binary_prop_dict.get(filename_or_url, {})
>  
>  
> w

Bug#1031435: python-inotify: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: python-inotify
Version: 0.2.10-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify
> copying inotify/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify
> copying inotify/test_support.py -> 
> /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify
> copying inotify/adapters.py -> 
> /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify
> copying inotify/constants.py -> 
> /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify
> copying inotify/library.py -> 
> /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify
> copying inotify/calls.py -> 
> /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify
> running egg_info
> creating inotify.egg-info
> writing inotify.egg-info/PKG-INFO
> writing dependency_links to inotify.egg-info/dependency_links.txt
> writing top-level names to inotify.egg-info/top_level.txt
> writing manifest file 'inotify.egg-info/SOURCES.txt'
> reading manifest file 'inotify.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> writing manifest file 'inotify.egg-info/SOURCES.txt'
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:202: 
> SetuptoolsDeprecationWarning: Installing 'inotify.resources' as data is 
> deprecated, please list it in `packages`.
> !!
> 
> 
> 
> # Package would be ignored #
> 
> Python recognizes 'inotify.resources' as an importable package,
> but it is not listed in the `packages` configuration of setuptools.
> 
> 'inotify.resources' has been automatically added to the distribution only
> because it may contain data files, but this behavior is likely to change
> in future versions of setuptools (and therefore is considered deprecated).
> 
> Please make sure that 'inotify.resources' is included as a package by 
> using
> the `packages` configuration field or the proper discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
> 
> You can read more about "package discovery" and "data files" on setuptools
> documentation page.
> 
> 
> !!
> 
>   check.warn(importable)
> creating 
> /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify/resources
> copying inotify/resources/README.rst -> 
> /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify/resources
> copying inotify/resources/requirements.txt -> 
> /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify/resources
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd 
> /<>/.pybuild/cpython3_3.11_python-inotify/build; python3.11 -m 
> pytest -k 'not test__cycle' --reruns 3 --reruns-delay 1
> = test session starts 
> ==
> platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack
> rootdir: /<>
> plugins: rerunfailures-10.2
> collected 9 items / 3 deselected / 6 selected
> 
> tests/test_inotify.py .s...R 
> [100%]R [100%]R [100%]F [100%]
> 
> === FAILURES 
> ===
>  TestInotifyTree.test__renames 
> _
> 
> self = 
> 
> def test__renames(self):
> 
> # Since we're not reading the events one at a time in a loop and
> # removing or renaming folders will flush any queued events, we have 
> to
> # group things in order to check things first before such operations.
> 
> with inotify.test_support.temp_path() as path:
> i = inotify.adapters.InotifyTree(path)
> 
> old_path = os.path.join(path, 'old_folder')
> new_path = os.path.join(path, 'new_folder')
> 
> os.mkdir(old_path)
> 
> events1 = self.__rea

Bug#1031434: conda-package-handling: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: conda-package-handling
Version: 2.0.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/tarball.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/cli.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/__main__.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/api.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/interface.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/exceptions.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/conda_fmt.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/validate.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/streaming.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/utils.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; 
> python3.11 -m pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack
> rootdir: /<>, configfile: setup.cfg
> plugins: mock-3.8.2
> collected 39 items / 1 error
> 
>  ERRORS 
> 
>  ERROR collecting .pybuild/cpython3_3.11/build/tests/test_interface.py 
> _
> ImportError while importing test module 
> '/<>/.pybuild/cpython3_3.11/build/tests/test_interface.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/test_interface.py:12: in 
> from conda_package_handling.conda_fmt import CondaFormat_v2
> conda_package_handling/conda_fmt.py:15: in 
> import zstandard
> /usr/lib/python3/dist-packages/zstandard/__init__.py:39: in 
> from .backend_c import *  # type: ignore
> E   ImportError: zstd C API versions mismatch; Python bindings were not 
> compiled/linked against expected zstd version (10504 returned by the lib, 
> 10502 hardcoded in zstd headers, 10502 hardcoded in the cext)
> === warnings summary 
> ===
> ../../../../../../usr/lib/python3/dist-packages/_pytest/config/__init__.py:1294
>   /usr/lib/python3/dist-packages/_pytest/config/__init__.py:1294: 
> PytestConfigWarning: Unknown config option: env
>   
> self._warn_or_fail_if_strict(f"Unknown config option: {key}\n")
> 
> ../../../../../../usr/lib/python3/dist-packages/conda_package_streaming/package_streaming.py:19
>   
> /usr/lib/python3/dist-packages/conda_package_streaming/package_streaming.py:19:
>  UserWarning: zstandard could not be imported. Running without .conda support.
> warnings.warn("zstandard could not be imported. Running without .conda 
> support.")
> 
> conda_package_handling/api.py:29
>   
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling/api.py:29:
>  UserWarning: Install zstandard Python bindings for .conda support
> _warnings.warn("Install zstandard Python bindings for .conda support")
> 
> -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
> - generated xml file: /<>/.pybuild/cpython3_3.11/build/junit.xml 
> -
> === short test summary info 
> =

Bug#1031431: debian-installer-netboot-images: FTBFS: Building 20220917, but bookworm has 20230207, failing the build

[Lucas Nussbaum]

Source: debian-installer-netboot-images
Version: 20220917+rebuild1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> if ! ./get-images.sh amd64; then \
>   if [ -n "" ]; then \
>   echo; echo; echo; \
>   echo "Version not found in bookworm, falling back to "; \
>   echo; echo; echo; \
>   sleep 5; \
>   DISTRIBUTION= ./get-images.sh amd64; \
>   else \
>   echo "Version not found in bookworm, no fallback defined"; \
>   exit 1; \
>   fi \
> fi
> --2023-02-17 01:24:15--  
> http://127.0.0.1:12990/debian/dists/bookworm/Release.gpg
> Connecting to 127.0.0.1:12990... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 1601 (1.6K) [text/plain]
> Saving to: ‘/<>/Release.gpg’
> 
>  0K . 100%  177M=0s
> 
> 2023-02-17 01:24:15 (177 MB/s) - ‘/<>/Release.gpg’ saved 
> [1601/1601]
> 
> --2023-02-17 01:24:15--  http://127.0.0.1:12990/debian/dists/bookworm/Release
> Connecting to 127.0.0.1:12990... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 171552 (168K) [text/plain]
> Saving to: ‘/<>/Release’
> 
>  0K .. .. .. .. .. 29%  329M 0s
> 50K .. .. .. .. .. 59%  276M 0s
>100K .. .. .. .. .. 89% 60.2M 0s
>150K .. ...100% 
> 13.9M=0.002s
> 
> 2023-02-17 01:24:15 (69.1 MB/s) - ‘/<>/Release’ saved 
> [171552/171552]
> 
> gpgv: Signature made Thu Feb 16 20:13:29 2023 UTC
> gpgv:using RSA key 0146DC6D4A0B2914BDED34DB648ACFD622F3D138
> gpgv: Good signature from "Debian Archive Automatic Signing Key (10/buster) 
> "
> gpgv: Signature made Thu Feb 16 20:14:07 2023 UTC
> gpgv:using RSA key A7236886F3CCCAAD148A27F80E98404D386FA1D9
> gpgv: Good signature from "Debian Archive Automatic Signing Key (11/bullseye) 
> "
> --2023-02-17 01:24:15--  
> http://127.0.0.1:12990/debian/dists/bookworm/main/binary-amd64/Packages.xz
> Connecting to 127.0.0.1:12990... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 9040064 (8.6M) [text/plain]
> Saving to: ‘amd64.Packages.xz’
> 
>  0K .. .. .. .. ..  0%  191M 0s
> 50K .. .. .. .. ..  1% 83.8M 0s
>100K .. .. .. .. ..  1%  109M 0s
>150K .. .. .. .. ..  2% 21.6M 0s
>200K .. .. .. .. ..  2% 51.3M 0s
>250K .. .. .. .. ..  3%  110M 0s
>300K .. .. .. .. ..  3%  113M 0s
>350K .. .. .. .. ..  4%  114M 0s
>400K .. .. .. .. ..  5%  100M 0s
>450K .. .. .. .. ..  5% 89.4M 0s
>500K .. .. .. .. ..  6% 99.9M 0s
>550K .. .. .. .. ..  6% 73.4M 0s
>600K .. .. .. .. ..  7%  174M 0s
>650K .. .. .. .. ..  7%  120M 0s
>700K .. .. .. .. ..  8%  133M 0s
>750K .. .. .. .. ..  9% 13.4M 0s
>800K .. .. .. .. ..  9%  102M 0s
>850K .. .. .. .. .. 10%  141M 0s
>900K .. .. .. .. .. 10%  106M 0s
>950K .. .. .. .. .. 11%  161M 0s
>   1000K .. .. .. .. .. 11% 47.5M 0s
>   1050K .. .. .. .. .. 12%  132M 0s
>   1100K .. .. .. .. .. 13% 23.4M 0s
>   1150K .. .. .. .. .. 13%  118M 0s
>   1200K .. .. .. .. .. 14%  124M 0s
>   1250K .. .. .. .. .. 14% 36.5M 0s
>   1300K .. .. .. .. .. 15% 29.8

Bug#1031432: mediaelement: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '../build/mediaelement.min.js'

[Lucas Nussbaum]

Source: mediaelement
Version: 2.15.1+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd /<>/src && python3 ./Builder.py
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)
> building MediaElement.js
> building MediaElementPlayer.js
> Minifying JavaScript
> Traceback (most recent call last):
>   File "/<>/src/./Builder.py", line 101, in 
> addHeader('js/me-header.js', '../build/' + me_filename + '.min.js')
>   File "/<>/src/./Builder.py", line 89, in addHeader
> tmp_file = open(filename)
>^^
> FileNotFoundError: [Errno 2] No such file or directory: 
> '../build/mediaelement.min.js'
> make[1]: *** [debian/rules:6: execute_before_dh_auto_build] Error

Processed: severity of 1030869 is important

[Debian Bug Tracking System]

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

> severity 1030869 important
Bug #1030869 {Done: Markus Koschany } [tomcat10] tomcat10: 
Catalina won't deploy applications missing class 
jakarta.websocket.DeploymentException
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Adrian Bunk]

On Thu, Feb 16, 2023 at 05:24:04PM -0500, Theodore Ts'o wrote:
>...
> and that moving forward, we make it the image building tools
> problem if they want to support this highly dubious practice of using
> Debian N+X's mkfs to build images for Debian N.
>...

That's what they already have to do for many years.

But it is also our problem when we ship these image building tools,
to ensure that there are bugs against all of them that get fixed
before the release where the change is present.

> Best release engineering practice is that you use a known, controlled
> build environment, and not whatever random package versions might be
> on your desktop.  While that might be "inconvenient" when building
> packages, we've learned to live with it.  I use sbuild; others might
> use pbuild, or their own custom schroot setup.  But I dare say all
> responsible people doing release engineering use a known build
> environment.  Why should this be any different if you are building
> images --- especially images that you expect *your* users or customers
> to be depending on?
>...

controlled != identical to the target

There are different approaches to this problem with different advantages 
and disadvantages.

It is not unreasonable for an image building tool we ship in bookworm to 
use the host tools of a bookworm x86 server to create a Debian image for 
a buster ARM target.

>   - Ted

cu
Adrian

Bug#1031271: marked as done (glib2.0 [experimental]: 2.75.3 FTBFS on big-endian)

[Debian Bug Tracking System]

Your message dated Thu, 16 Feb 2023 23:20:04 +
with message-id 
and subject line Bug#1031271: fixed in glib2.0 2.75.3-2
has caused the Debian Bug report #1031271,
regarding glib2.0 [experimental]: 2.75.3 FTBFS on big-endian
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.)


-- 
1031271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glib2.0
Version: 2.75.3-1
Severity: serious
Tags: ftbfs upstream pending
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://gitlab.gnome.org/GNOME/glib/-/issues/2918

See . I'm testing a
solution.

smcv
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.75.3-2
Done: Jeremy Bicha 

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated glib2.0 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: Thu, 16 Feb 2023 17:58:48 -0500
Source: glib2.0
Built-For-Profiles: noudeb
Architecture: source
Version: 2.75.3-2
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Closes: 1031271
Changes:
 glib2.0 (2.75.3-2) experimental; urgency=medium
 .
   [ Simon McVittie ]
   * d/p/array-test-Don-t-rely-on-endianness-of-multi-byte-numbers.patch:
 Add proposed patch to fix FTBFS on big-endian architectures
 (Closes: #1031271)
 .
   [ Jeremy Bicha ]
   * Cherry-pick an implicit conversion change fix
Checksums-Sha1:
 c4d15355eba03235ec94b259fdf4ebd2883e8765 3659 glib2.0_2.75.3-2.dsc
 bdf3f89c51714b419d6a37616d3b619816ee52fb 116844 glib2.0_2.75.3-2.debian.tar.xz
 721e698544983e917141740b62706a9c9a1a7ec0 11458 
glib2.0_2.75.3-2_source.buildinfo
Checksums-Sha256:
 b3aa285cbfde32a75e4364e995091ac12cdcbff8e2fdcc2067f2e0e9610c 3659 
glib2.0_2.75.3-2.dsc
 6e56c0912744603b78ff6c18a629fe5a10b8a48d0f0b6835afb8e7df96651a3a 116844 
glib2.0_2.75.3-2.debian.tar.xz
 70e95728bad2ea8e1e555829993c73b19f4a65b3f4230e3dc0a6ce38ebb213a6 11458 
glib2.0_2.75.3-2_source.buildinfo
Files:
 671dab336ea750e1e38f82a852a5bdc1 3659 libs optional glib2.0_2.75.3-2.dsc
 dca36feb292eee8be70615a4bc8848d2 116844 libs optional 
glib2.0_2.75.3-2.debian.tar.xz
 685a87459e6e8bc3400ed791a21703b0 11458 libs optional 
glib2.0_2.75.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmPutWUACgkQ5mx3Wuv+
bH1Slw//S3XEdyPkh5YWPe13WX78vbt5WHc7UP+I5LUJcfHYBQzuFSBbj49piIH1
EKAJx6epq7DKETAIGaAOHXYsXh1OdFTU8Xn/gZn81W5eC6w+++wXTcWxQ4625570
UT/7Hg6tSB9I83u+ochwdAw1yJgzpd9jhu06M+acy7k1VnHn+uTo+W4T18ERhNLu
vdG1TJ/31J1BjqvqIboY+vYufHpNOFtI0k4NuQcomls9KhuEa7V6oW8oq5SCPJJk
DenwzpdRld4OVRANw2ZfUqQVu5rq7ZSLkhHAKcyW3NvbGFQ0Hhhivbv8zsWutrAu
VIrXXW/9mj1FeQam/iUYlds88FBDSsehj+IF3OlzkUYHeFQaM6/ejdgvbWQ6exzD
hmMTDQicMv5cheQfUdZmggwx8yihwQQppY9rk88VguiCq0q8TXvvwpQILIbmcldq
l+7WEJUmJpoeZcmj/Riq3x0wkjIJQopbyoo0bHvUSLjKw9gjkzfaIKjzw8ENfVrl
J2b3W1INScSeVd9lYP0oQZj5y4ULtCuReXOkRcKnhxmwqzug398mOnuYHZYhZVki
fMxGk5Cyxckb+wjQ0YhZb5HoUo5eZpHwKpUwd5HuPd2Jh9KFpl8R+sOvG5qr0cuL
rm3KGB54VUlb+vp+l4JQeWk/5XkqyRgRyKC4Z6er+nMQrQvf7wE=
=Vqcb
-END PGP SIGNATURE End Message ---

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Russ Allbery]

"Theodore Ts'o"  writes:

> As a long-term solution, one could image changing the various image
> creation tools to do something like "mfks.ext4 -T grub2_dumbdown
> /dev/XXX", and then have something like the following in
> /etc/mke2fs.conf:

> [fs_types]
> grub2_dumbdown = {
> features = ^metadata_csum_seed,^casefold
> }

This is considerably more specific than what I had in mind, but maybe I'm
misunderstanding the problem.  Here's a slightly more fleshed out version
of what I was thinking:

mke2fs when run without any options has some default upstream-shipped set
of options that it enables (possibly via the upstream-shipped mke2fs.conf,
possibly in the binary, however it works).  Those defaults presumably work
with the kernel and other system tools shipped at the time, due to the
normal compatibility due diligence that you'd naturally do while doing
file system development.

When you make changes to the *defaults* (not just the addition of any
options in general), this presumably is also aligned with what you think
is generally supported by other system tools at the time.

Each time you change the defaults in a way that could be
backward-incompatible, you could capture those new defaults in a
permanently-fixed label of, say, 20230616, which is the defaults on that
date.  Probably in the default /etc/mke2fs.conf.  I don't expect you to
care about what systems they work with, what distributions they work with,
or anything else other than the timeline of when you decided to change the
defaults, something you're presumably already doing as a maintainer.  The
only additional work would be to update these labels with the settings
required to make mke2fs with its current defaults behave compatibly with
whatever the defaults had been at each of those captured points in time.

(And obviously eventually you could drop the really old ones if it made no
sense to keep supporting them, or have some single really-ancient fallback
for really old systems, etc.)

Then, image creators can look in /etc/mke2fs.conf for the timestamp that
most closely aligns with the target system they want to create and use
that group of settings.  If that turns out to be inadequate, they can go
back to a previous date.  Some work on their part is still required, but
from their perspective I think this would have the advantage of not having
to do research to reconstruct what all the options could be and how they
changed and which ones were potentially backward-incompatible, which are
all things you would generally already know and have in mind when you
changed the defaults and thus could capture for them.

That said, this is an architectural stab in the dark and I obviously don't
work on file system development, so maybe this isn't viable for some
reason that I'm not seeing.

-- 
Russ Allbery (r...@debian.org)  

Bug#972146: /usr/share/applications/mono-runtime-common.desktop: should not handle MIME type by executing arbitrary code

[Gabriel Corona]

Hi,

Thanks for the patch!

This has been fixed in Debian testing and sid. However, stable is still 
affected. I believe it would make sense to port the patch to stable and 
allocate a CVE for this.


Regards,

Gabriel

Processed: Re: clinfo breaks libgpuarray autopkgtest on i386: numerical deltas

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/pocl/pocl/issues/1176
Bug #1031414 [src:pocl,src:libgpuarray] libgpuarray: i386 test fail with new 
pocl
Set Bug forwarded-to-address to 'https://github.com/pocl/pocl/issues/1176'.

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

Bug#1031414: clinfo breaks libgpuarray autopkgtest on i386: numerical deltas

[Andreas Beckmann]

Control: forwarded -1 https://github.com/pocl/pocl/issues/1176

@elbrus: Why does britney try to migrate clinfo together with pocl?
IMO clinfo should be able to migrate on its own without causing new 
regressions in testing. It does not have any (transitive) dependency on 
pocl.


On Thu, 16 Feb 2023 21:46:31 + "Rebecca N. Palmer" 
 wrote:
The trigger is probably pocl, not clinfo.  I don't yet know whether the 
bug is in pocl or libgpuarray.

or llvm-15

pocl/sid is built against llvm-15, pocl/testing against llvm-14

This also causes a test regression in pyopencl due to numerical 
differences (#1030298). This was attempted to be fixed in pyopencl 
upstream by requiring the numerical difference to be below some 
tolerance level instead of requiring equality, but the numerical delta 
is too large to hide behind that ...


I'm currently trying to debug the code generation delta between llvm-14 
and llvm-15 ...


There could still be a bug in libgpuarray if the failing test is too 
strict by requiring equality of some floating point computations. (Not 
checked.)


Andreas

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Theodore Ts'o]

On Thu, Feb 16, 2023 at 11:45:23AM -0800, Russ Allbery wrote:
> 
> Yes, I'm probably understating the difficulty of making this change in
> practice inside image building software as it's currently constructed.
> 
> My concern about changing mkfs options is that I worry that this would be
> a constantly-changing target that has to be synchronized across multiple
> pieces of software that are not currently well-aligned with file system
> development.  One thing that would make this much easier would be for mkfs
> to support some sort of compatibility level flag that sets all of the
> options, whatever they may be, to their defaults as of some point in the
> past.  Image building software could then pick a conservative default set
> point when building images for older distributions.  That change still has
> to be added to all of the image building software, but it might be easier
> than building a local chroot of the target distribution before using it to
> build the file system the actual installation is going into.

As a long-term solution, one could image changing the various image
creation tools to do something like "mfks.ext4 -T grub2_dumbdown
/dev/XXX", and then have something like the following in
/etc/mke2fs.conf:

[fs_types]
grub2_dumbdown = {
features = ^metadata_csum_seed,^casefold
}

If you care about being able to run fsck.ext4 on really old
distributions, one could even add things like

[fs_types]
jessie_dumbdown = {
features = ^metadata_csum_seed,^metadata_csum
}

etc.

Maintaining this would be a nightmare, and I'd want to ask for help,
since this would be change if we also want to add dumbdown file system
usage types for Ubuntu, and potentially, other Debian derivitives.

Even if we stick with grub2_dumbdown, again, how far back do we go?
Some people have said, "just one release", but I bet there will be
people wanting to create Stretch installer images using a sid
userspace.  So I'd want to have some kind of formal understanding
about what it is that we feel obliged to support.

Given the number of users of the iamge building tools, it's a pretty
specialized use case with not a lot of users, and they can also just
edit /etc/mke2fs.conf to have their favored default.  From my
e2fsprogs maintainers hat on, that's my position --- I interpret
"users" in the Debian Social Contract for the general users, and not
necessarily something that needs to work for every single exotic use
case, especially if they tend to be more of the power users.

If we're not allowed to inconvenience *any* users, then it's hard to
make forward progress.  Certainly some people (including myself) were
inconvenienced for things like /usr-unification and the transition to
systemd.  We went ahead with the transition even though some users
were inconvenienced.  And quite honestly, if a few power users need to
edit /etc/mke2fs.conf to remove metadata_csum_seed because they want
to do something which is *REALLY* not a good idea (using Debian M to
build a file system meant for use on Debian M-X) --- for *ALL* file
systems, not just ext4.  It may be that some users have gotten lucky,
and it mostly works.  But it's a bad idea, and encouraging this bad
practice is eventually going to lead to tears.

But, if the Debian Release team would like to override my position, my
suggestion would be to just change the default for /etc/mke2fs.conf
for *everyone* running Debian bookworm, and with the understanding
that this will be reverted in Debian testing after the next stable
release, and that moving forward, we make it the image building tools
problem if they want to support this highly dubious practice of using
Debian N+X's mkfs to build images for Debian N.  I would strongly
suggest that they figure out which file system features they need to
explicitly turn off for ext4, xfs, btrfs, etc., if they want to build
old distro versions using whatever random software they have installed
on their desktop.

Best release engineering practice is that you use a known, controlled
build environment, and not whatever random package versions might be
on your desktop.  While that might be "inconvenient" when building
packages, we've learned to live with it.  I use sbuild; others might
use pbuild, or their own custom schroot setup.  But I dare say all
responsible people doing release engineering use a known build
environment.  Why should this be any different if you are building
images --- especially images that you expect *your* users or customers
to be depending on?  What are your responsibilities to them?  (Whether
or not the Debian Social contract applies to them or not.)

- Ted

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Sebastian Ramacher]

On 2023-02-16 11:44:25 -0700, Sam Hartman wrote:
> > "Adrian" == Adrian Bunk  writes:
> 
> Adrian> On Thu, Feb 16, 2023 at 05:48:22PM +0100, Daniel Leidert wrote:
> >> Am Donnerstag, dem 16.02.2023 um 18:37 +0200 schrieb Adrian Bunk:
> >> > On Wed, Feb 15, 2023 at 12:05:41AM +0100, Daniel Leidert wrote:
> >> > > ...  > > Reasons: > > ...  > > - - the change makes it
> >> impossible to create filesystems with this version of > >  
> >> e2fsprogs and then run a grub-install from a target system that
> >> does not cope > >   with that feature; basically breaking the
> >> debootstrap method of installing > >   Debian or Ubuntu onto a
> >> server (violating #4 of the Debian social contract) > > ...  > >
> >> Instead, turning on this feature should be postponed for the next
> >> release cycle > > where a proper transition can be done.  > > ...
> >> > 
> >> > Daniel, you are contradicting yourself when claiming that a
> >> change that > would allegedly violate the Debian social contract
> >> could be done in the > next release cycle.
> >> 
> >> Actually, I'm not.  ...
> 
> Adrian> If not being able to install bullseye from bookworm is a
> Adrian> violation of the Debian social contract, then the same
> Adrian> rationale applies to not being able to install bullseye from
> Adrian> trixie being a violation of the Debian social contract.
> 
> I don't think that arguing about whether this is a social contract
> violation makes a lot of sense.
> It seems fairly clear there is not a consensus about that.
> 
> But if we're going to do that, I suggest that Adrian is putting words
> into Daniel's mouth a bit.
> Daniel has said he believes this situation violates the Social Contract
> #4, but has not explained why.
> Adrian has taken one interpretation.
> I'll propose another: "This violates the social contract because we are
> not prioritizing our users.  Prioritizing users requires that we give
> them notice of incompatible changes."
> I personally think that prioritizing users requires no such thing, and
> that this change is not a violation of the SC.
> But you don't need to take the straw man position Adrian is assuming
> Daniel implies to believe this is a SC violation.
> 
> But seriously, let's give up the whole is this an SC violation part of
> the discussion and move on with constructive aspects:
> 
> * The RT has asked to understand the impact of the change.
> 
> * Several people have proposed better documentation because it's clear
>   that user (and image builder) expectations are not aligned with
>   filesystem maintainer expectations.
> 
> * Anyone could prepare patches to image building software to use mkfs
>   options that will work with bullseye.  You could also try to prepare
>   patches to run mkfs out of a chroot or container of the guest OS for
>   the image.  I appreciate Russ strongly favors this solution, but as
>   someone who has dug into image building tools a fair bit over the
>   years, I think there are significant complexity and performance
>   downsides to that approach.  I also think that changing the mkfs
>   options is more likely to get an unblock than changing the structure
>   of how the tool works.
>   
>   
>   
> * People could try to judge consensus on debian-devel or debian-policy
>   about whether we want a stability guarantee ?+/- 1 release on issues
>   like this.  My suspicion is that you will not find a consensus, and
>   that if the RT decides they don't want this change in bookworm, Ted
>   will change the defaults, and if the RT is unwilling to block, we're
>   left with documentation.
> 
> I think all the above is more productive than arguing about whether this
> is or is not an SC violation.

Thanks for this mail. The discussion on SC#4 is not helping us to reach
a decission on this issue.

Cheers
-- 
Sebastian Ramacher

Bug#1030767: marked as done (imagemagick: CVE-2022-44267 CVE-2022-44268)

[Debian Bug Tracking System]

Your message dated Thu, 16 Feb 2023 21:35:48 +
with message-id 
and subject line Bug#1030767: fixed in imagemagick 8:6.9.11.60+dfsg-1.6
has caused the Debian Bug report #1030767,
regarding imagemagick: CVE-2022-44267 CVE-2022-44268
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.)


-- 
1030767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: imagemagick
Version: 8:6.9.11.60+dfsg-1.3
Severity: important
Tags: security
X-Debbugs-Cc: gli...@gmail.com, Debian Security Team 




-- Package-specific info:
ImageMagick program version
---
animate:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
compare:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
convert:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
composite:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
conjure:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
display:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
identify:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
import:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
mogrify:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
montage:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
stream:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org

-- System Information:
Debian Release: 11.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-52-generic (SMP w/2 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages imagemagick depends on:
ii  imagemagick-6.q16  8:6.9.11.60+dfsg-1.3

imagemagick recommends no packages.

imagemagick suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.9.11.60+dfsg-1.6
Done: Jeremy Bicha 

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated imagemagick 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: Thu, 16 Feb 2023 16:06:07 -0500
Source: imagemagick
Built-For-Profiles: noudeb
Architecture: source
Version: 8:6.9.11.60+dfsg-1.6
Distribution: unstable
Urgency: high
Maintainer: ImageMagick Packaging Team 

Changed-By: Jeremy Bicha 
Closes: 1030767
Launchpad-Bugs-Fixed: 2004580
Changes:
 imagemagick (8:6.9.11.60+dfsg-1.6) unstable; urgency=high
 .
   * Non-maintainer upload
 .
   [ Moritz Mühlenhoff ]
   * Fix CVE-2022-44267 / CVE-2022-44268 (Closes: #1030767) (LP: #2004580)
Checksums-Sha1:
 b0f5fd11d51400c7ebdac026f0b948eeb9d8ad65 5074 
imagemagick_6.9.11.60+dfsg-1.6.dsc
 44b6a8f8540e6e31e1621bb53ecaeb4496c3027b 253928 
imagemagick_6.9.11.60+dfsg-1.6.debian.tar.xz
 60689009905cbddb97414ec49fe4f33bc47ce34e 12237 
imagemagick_6.9.11.60+dfsg-1.6_source.buildinfo
Checksums-Sha256:
 3e8af11649b1711480ed49e2896d4df034b5a7b505dbad88b1c0b3d5347193df 5074 
imagemagick_6.9.11.60+dfsg-1.6.dsc
 f63bfbe6e513d42ce88578435eade5979c22ca15a5771e5a76a74e29d44bf41f 253928 
imagemagick_6.9.11.60+dfsg-1.6.debian.tar.xz
 28bb43da67634ed8b4cdb95aceac708f454e56584d066378063f010f25c6dfab 12237 
imagemagick_6.9.11.60+dfsg-1.6_source.buildinfo
Files:
 c3d94b1a1c81ec0cf6351ef5d92e4b12 5074 graphics optional 
imagemagick_6.9.11.60+dfsg-1.6.dsc
 c7c14d0ac4cbb512d2bfdf47e35b0223 253928 graphics optional 
imagemagick_6.9.11.60+dfsg-1.6.debian.tar.xz
 178d9a199675268124cb522f2d4dca4a 12237 graphics optional 
imagemagick_6.9.11.60+dfsg-1.6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmPum8kACgkQ5mx3Wuv+
bH0MZxAAuYvHFlW9nDcvKUYyZ2e4fzxzyT3mDbu8ZlHvlzJOZ8KAVSh0wla9u7VV

Processed: Re: clinfo breaks libgpuarray autopkgtest on i386: numerical deltas

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:pocl,src:libgpuarray
Bug #1031414 [src:clinfo, src:libgpuarray] clinfo breaks libgpuarray 
autopkgtest on i386: numerical deltas
Bug reassigned from package 'src:clinfo, src:libgpuarray' to 
'src:pocl,src:libgpuarray'.
No longer marked as found in versions clinfo/3.0.23.01.25-1 and 
libgpuarray/0.7.6-13.
Ignoring request to alter fixed versions of bug #1031414 to the same values 
previously set
> found -1 pocl/3.1-3
Bug #1031414 [src:pocl,src:libgpuarray] clinfo breaks libgpuarray autopkgtest 
on i386: numerical deltas
Marked as found in versions pocl/3.1-3.
> found -1 libgpuarray/0.7.6-13
Bug #1031414 [src:pocl,src:libgpuarray] clinfo breaks libgpuarray autopkgtest 
on i386: numerical deltas
Marked as found in versions libgpuarray/0.7.6-13.
> retitle -1 libgpuarray: i386 test fail with new pocl
Bug #1031414 [src:pocl,src:libgpuarray] clinfo breaks libgpuarray autopkgtest 
on i386: numerical deltas
Changed Bug title to 'libgpuarray: i386 test fail with new pocl' from 'clinfo 
breaks libgpuarray autopkgtest on i386: numerical deltas'.

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

Bug#1031395: marked as done (tzdata 2022g-3 removes /etc/timezone while other packages depend on it, breaking these packages)

[Debian Bug Tracking System]

Your message dated Thu, 16 Feb 2023 21:49:40 +
with message-id 
and subject line Bug#1031395: fixed in tzdata 2022g-6
has caused the Debian Bug report #1031395,
regarding tzdata 2022g-3 removes /etc/timezone while other packages depend on 
it, breaking these packages
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.)


-- 
1031395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031395
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tzdata
Version: 2022g-3
Severity: critical

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

in version 2022g-3, the /etc/timezone file has been removed and gets purged
from user's computers. This makes unrelated software break that relies on this
file. Examples are samizdat and ruby-et-orbi. But codesearch.d.o shows more
code-snippets that rely on the existence of that file. There hasn't been any
announcement, any transition, nor any mass-bug filing, leaving multiple
packages broken at this stage. I reported that issue to the release team as
#1031376 and have been asked to open a bug report against tzdata.

Regards, Daniel

- -- System Information:
Debian Release: bookworm/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-4-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tzdata depends on:
ii  debconf [debconf-2.0]  1.5.82

tzdata recommends no packages.

tzdata suggests no packages.

- -- debconf information excluded

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPuJ/gACgkQS80FZ8KW
0F2CPQ/+M+A8ok4famSAdTA6Tpjw+ydaYGO2E4+NoQy/diq8KKhFMiOOdduiQji4
6J8no1J7K00eEPgqBko3lQXDJByDuRKHWXD3NFmQJme/pL9Wf4yc7+Zx4QhaBI96
UuUV4M8khv89bA9Bb6TWGUD0OkEOgpze7HAZAQqc8gnaGA2yRkh3JC9DmHe9boQJ
ywODuoFmlPIgyv+Jx8KlXgGdZWWoJpQtm8ol21WeYRtAWxPL+b/FbC1rTrSSEgka
wmw+pa4VbKC8sQIyGQPbJJk0q3PTIqKu1ia59KGKSrCox4cfAvV3EccgyH1xYliI
BRrlSEG1mau1O8jz4fq7oqMVs6W/KMRuj+pSI4n5DEFU9tEJ2G3trysusnS531tj
L++pD/aWISx76rpVzizVQjw1J63pr9sK8sh9/s/jz4s3Ddwiij/HVMaA6t7X+2DU
I3O8jgUq4N6taWw7NcBLDSyFRESqc0BcZYwfsvD7DD0UHSUeZmE5PnetHVWLwqeg
O/ljWDNuIiB61DfVWJr5nfhKXOZYFWXJEOOwDQ5zxWviHlahEGsu3wOQLGW7OA9E
bKUO2IpAOMHX0Oxx752t9eParFqs2yfAX338PGC73w7dCIB5bVowD9SHRCJi6FRX
8HhD5hgq8SsuJEej0eBS63QqN3uqxZKbZsoQgA5aS3eMffxEPRM=
=i0wy
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: tzdata
Source-Version: 2022g-6
Done: Benjamin Drung 

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

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated tzdata 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: Thu, 16 Feb 2023 21:54:13 +0100
Source: tzdata
Built-For-Profiles: noudeb
Architecture: source
Version: 2022g-6
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Benjamin Drung 
Closes: 1031211 1031376 1031395
Changes:
 tzdata (2022g-6) unstable; urgency=medium
 .
   * Restore generating /etc/timezone again. The removal of /etc/timezone
 will be done in Debian 13 "Trixie". (Closes: #1031376, #1031395)
   * Update Turkish debconf translation.
 Thanks to Atila KOÇ  (Closes: #1031211)
Checksums-Sha1:
 967c91766e4f35ec94fa32a7ebfffd3c91583e02 2332 tzdata_2022g-6.dsc
 ad872e46cc7d1901a0ea3445cde462287f470adb 116988 tzdata_2022g-6.debian.tar.xz
 3fa33f03cd3f5fcd0b6ecb3b34b963f22f896dd5 7316 tzdata_2022g-6_source.buildinfo
Checksums-Sha256:
 2b07aa4e69fbbfba51b0da5b5ad508a12117b6d116f0b18a47acfc78fb10a591 2332 
tzdata_2022g-6.dsc
 319448a7f371c60e334d7aed1897fd2f323f47a6655d8f67750af1927926856f 116988 
tzdata_2022g-6.debian.tar.xz
 a25ae3ba9dc490824605e8b255bafc47431c6f178ecac092045f1d38869d008f 7316 

Bug#1031414: clinfo breaks libgpuarray autopkgtest on i386: numerical deltas

[Rebecca N. Palmer]

Control: reassign -1 src:pocl,src:libgpuarray
Control: found -1 pocl/3.1-3
Control: found -1 libgpuarray/0.7.6-13
Control: retitle -1 libgpuarray: i386 test fail with new pocl

The trigger is probably pocl, not clinfo.  I don't yet know whether the 
bug is in pocl or libgpuarray.

Bug#1031293: python3-zstandard 0.19.0-3 supports only libzstd 1.5.2

[James Addison]

Package: python3-zstandard
Followup-For: Bug #1031293
X-Debbugs-Cc: b...@debian.org, gregory.sz...@gmail.com

Hi Adrian, Gregory,

Reading the comment above the version check, it seems to indicate that Gregory
isn't particularly enthusiastic to provide support for environments where
there's a mismatch between the python-zstandard module and an unbundled system
zstd library.

Although it 'might work' in practice -- and even though users may be careful
enough to figure out the correct place to complain to even if problems did
occur -- I reckon we should default to upstream's preferences unless there are
good reasons not to (and there might be; they're just not clear to me, if so).

(not only could complaints cause nuisance for upstream, but divergence could,
in my opinion, mean that Debian maintainers would take on more responsibility;
again fine if it makes sense to do that, but it might be helpful to agree why)

Thanks,
James

Bug#1031395: marked as pending in tzdata

[Benjamin Drung]

Control: tag -1 pending

Hello,

Bug #1031395 in tzdata 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/glibc-team/tzdata/-/commit/0a5dcdee0e45c5eb9276112925b3e5c89d829b1b


Restore generating /etc/timezone again

In version 2022g-3, the /etc/timezone file has been removed and gets
purged from user's computers. This makes unrelated software break that
relies on this file. Examples are samizdat and ruby-et-orbi.

Restore generating /etc/timezone again for the Debian 12 "Bookworm"
release. Defer the removal to after the bookworm release for the Debian
13 "Trixie" release. Then there will be enough time for mass-bug filing
and fixing the consumers.

This reverts commit 3edcce5955de5ed7b7072402e7565945bc84aea8 ("Remove
/etc/timezone on upgrades as a one-time action").

Closes: #1031376, #1031395
Signed-off-by: Benjamin Drung 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1031395

Processed: Bug#1031395 marked as pending in tzdata

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1031395 [tzdata] tzdata 2022g-3 removes /etc/timezone while other packages 
depend on it, breaking these packages
Added tag(s) pending.

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

Processed: Re: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #1030939 [e2fsprogs] e2fsprogs: generates filesystems that grub-install 
doesn't recognize
Bug 1030939 cloned as bug 1031415
> reassign -2 fai 6.0
Bug #1031415 [e2fsprogs] e2fsprogs: generates filesystems that grub-install 
doesn't recognize
Bug reassigned from package 'e2fsprogs' to 'fai'.
No longer marked as found in versions e2fsprogs/1.47.0-1.
Ignoring request to alter fixed versions of bug #1031415 to the same values 
previously set
Bug #1031415 [fai] e2fsprogs: generates filesystems that grub-install doesn't 
recognize
There is no source info for the package 'fai' at version '6.0' with 
architecture ''
Unable to make a source version for version '6.0'
Marked as found in versions 6.0.
> clone -1 -3
Bug #1030939 [e2fsprogs] e2fsprogs: generates filesystems that grub-install 
doesn't recognize
Bug 1030939 cloned as bug 1031416
> reassign -3 grml-debootstrap 0.102
Bug #1031416 [e2fsprogs] e2fsprogs: generates filesystems that grub-install 
doesn't recognize
Bug reassigned from package 'e2fsprogs' to 'grml-debootstrap'.
No longer marked as found in versions e2fsprogs/1.47.0-1.
Ignoring request to alter fixed versions of bug #1031416 to the same values 
previously set
Bug #1031416 [grml-debootstrap] e2fsprogs: generates filesystems that 
grub-install doesn't recognize
Marked as found in versions grml-debootstrap/0.102.

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

Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Sebastian Ramacher]

Control: clone -1 -2
Control: reassign -2 fai 6.0
Control: clone -1 -3
Control: reassign -3 grml-debootstrap 0.102

On 2023-02-15 21:04:36 +0100, Sebastian Ramacher wrote:
> Control: clone -1 -2
> Control: reassign -2 vmdb2 0.26-2
> 
> On 2023-02-14 01:01:38 +0100, Daniel Leidert wrote:
> > Hi Steve,
> > 
> > I believe that your fix to grub2 in Sid is not enough to handle
> > #1030939/#1030846.
> > 
> > This problem breaks e.g. vmdb2. I can no longer create a Bullseye
> > system image with vmdb2 on Sid, because the grub-install step in the
> > Bullseye chroot now fails, because the created filesystem (created with
> > e2fsprogs on Sid) cannot be recognized by grub. I have to downgrade
> > e2fsprogs to the version in Testing to get the build going again. It
> > also means that a Bookworm system can never be used to format and
> > debootstrap a Bullseye or Buster system that requires a grub
> > installation.
> > 
> > I guess that the fix applied to grub2 in Sid would have to be applied
> > to grub2 in Bullseye as well (and basically to any grub2 package in any
> > Debian or Ubuntu or Raspbian release supported by debootstrap).
> > 
> > This situation is really messy. It breaks basically all my image builds
> > with vmdb2.
> 
> Regardless of the outcome of #1031325, this issue will need to be fixed
> in vmdb2 eventually. vmdb2, similar to other bootstraping tools, has to
> account for the feature and disable it if necessary for older
> distributions.
> 
> Cloning and reassign to vmdb2.

Based on more feedback from #10313225, I am also cloning and reassigning
this issue to fai and grml-debootstrap. Dear maintainers, please check
whether this issue is relevant for your packages.

Cheers
-- 
Sebastian Ramacher

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Sebastian Ramacher]

On 2023-02-16 07:54:52 -0700, Sam Hartman wrote:
> > "Sebastian" == Sebastian Ramacher  writes:
> 
> Sebastian> To better understand the impact of this change, I was
> Sebastian> wondering which tools / image builders in the archive
> Sebastian> would be affected by this change.  I've cloned the bug to
> Sebastian> vmdb2, but what about others?
> 
> It will affect fai-diskimage in the fai package..
> I believe that's used by the cloud team (or was) to create cloud images;
> I don't know if their use case is affected, because I don't know what OS
> they use to create what images.

Also cloned/reassigned the bug to fai, thanks.

Cheers
-- 
Sebastian Ramacher

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Sebastian Ramacher]

On 2023-02-16 12:24:01 +0100, Michael Prokop wrote:
> * Sebastian Ramacher [Thu Feb 16, 2023 at 09:09:08AM +0100]:
> > On 2023-02-15 13:17:38 -0700, Sam Hartman wrote:
> 
> > > But for example you're not leaving a lot of time for asking programs
> > > like vmdb2 or fai-diskimage to adjust how they call fsck.
> > > If you made this change a few months ago, it would be reasonable to file
> > > bugs against those packages and ask them to adjust how they call
> > > mkfs.ext4.
> 
> > To better understand the impact of this change, I was wondering which
> > tools / image builders in the archive would be affected by this change.
> > I've cloned the bug to vmdb2, but what about others?
> 
> I didn't verify it yet, but AFAICT grml-debootstrap is affected as
> well, since it supports installing older Debian releases from within
> more recent Debian/Grml environments and uses mkfs.ext4 as default.

Thanks, cloned/reassigned the bug also to grml-debootstrap to check
whether it's an issue.

Cheers

> 
> BTW, we had a similar situation already in the past when mkfs.ext4
> of e2fsprogs >=1.43~WIP.2015.05.18-1 enabled the "metadata_csum"
> feature, while this was unsupported on jessie and older releases.
> (grml-debootstrap provides a workaround for this.)
> 
> regards
> -mika-



-- 
Sebastian Ramacher

Bug#1031414: clinfo breaks libgpuarray autopkgtest on i386: numerical deltas

[Paul Gevers]

Source: clinfo, libgpuarray
Control: found -1 clinfo/3.0.23.01.25-1
Control: found -1 libgpuarray/0.7.6-13
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of clinfo the autopkgtest of libgpuarray fails in 
testing when that autopkgtest is run with the binary packages of clinfo 
from unstable. It passes when run with only packages from testing. In 
tabular form:


   passfail
clinfo from testing3.0.23.01.25-1
libgpuarrayfrom testing0.7.6-13
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of clinfo to testing 
[1]. Due to the nature of this issue, I filed this bug report against 
both packages. Can you please investigate the situation and reassign the 
bug to the right package?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log 
file quoted below. The migration software adds source package from 
unstable to the list if they are needed to install packages from 
clinfo/3.0.23.01.25-1. I.e. due to versioned dependencies or 
breaks/conflicts.

[1] https://qa.debian.org/excuses.php?package=clinfo

https://ci.debian.net/data/autopkgtest/testing/i386/libg/libgpuarray/31439784/log.gz

=== FAILURES 
===
__ test_ielemwise2_ops_mixed 
___


def test_ielemwise2_ops_mixed():
for op in ioperators2:
for dtype in dtypes_test:
for elem in elems:

  ielemwise2_ops_mixed(op, dtype, (50,), elem)


/usr/lib/python3/dist-packages/pygpu/tests/test_elemwise.py:173: _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/pygpu/tests/support.py:44: in f

func(*args, **kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

op = , dtype = 'float32', shape = (50,), elem = 0.3

@guard_devsup
def ielemwise2_ops_mixed(op, dtype, shape, elem):
incr = 0
if op == operator.isub and dtype[0] == 'u':
# array elements are smaller than 10 by default, so we 
avoid underflow

incr = 10
c, g = gen_gpuarray(shape, dtype, incr=incr, ctx=context,
cls=elemary)
try:
out_c = op(c, elem)
except TypeError:
# TODO: currently, we use old Numpy semantic and tolerate 
more case.

# So we can't test that we raise the same error
return
out_g = op(g, elem)
assert out_g is g
assert out_c.shape == out_g.shape
assert out_c.dtype == out_g.dtype

  assert numpy.allclose(out_c, numpy.asarray(out_g))

E   assert False
E+  where False = 0xf3ad35c8>(array([0.16798985, 0.10199559, 0.00094628, 0.284034  , 
0.00356799,\n   0.18276209, 0.06017095, 0.12363595, 0.14555043, 
0.06383288,\n   0.27849692, 0.23479545, 0.1120947 , 0.03348678, 
0.17435497,\n   0.10784233, 0.15038443, 0.08132076, 0.26949704, 
0.28150958,\n   0.08847237, 0.07874835, 0.14240652, 0.22457486, 
0.02050698,\n   0.24944574, 0.29784787, 0.03708786, 0.23751181, 
0.26554942,\n   0.26809436, 0.02403933, 0.23044948, 0.13133025, 
0.29589295,\n   0.05166197, 0.07869713, 0.10319626, 0.07735932, 
0.241211  ,\n   0.27668405, 0.16557133, 0.26950228, 0.230201  , 
0.2993518 ,\n   0.0713675 , 0.02841425, 0.04263723, 0.194592  , 
0.2564727 ],\n  dtype=float32), array([0.16798979, 0.10199571, 
0.00094652, 0.28403443, 0.00356805,\n   0.1827622 , 0.06017077, 
0.12363613, 0.14555037, 0.063833  ,\n   0.2784968 , 0.23479551, 
0.11209452, 0.03348672, 0.17435497,\n   0.10784221, 0.1503846 , 
0.08132076, 0.26949698, 0.28150946,\n   0.08847237, 0.07874823, 
0.14240658, 0.22457486, 0.0205071 ,\n   0.24944574, 0.29784793, 
0.0370878 , 0.2375117 , 0.26554942,\n   0.26809436, 0.02403933, 
0.23044948, 0.13133001, 0.29589337,\n   0.05166197, 0.07869713, 
0.10319638, 0.07735932, 0.24121124,\n   0.276684  , 0.16557115, 
0.26950234, 0.230201  , 0.29935163,\n   0.07136726, 0.02841425, 
0.04263711, 0.19459194, 0.25647253],\n  dtype=float32))

E+where  = numpy.allclose
E+and   array([0.16798979, 0.10199571, 0.00094652, 
0.28403443, 0.00356805,\n   0.1827622 , 0.06017077, 0.12363613, 
0.14555037, 0.063833  ,\n   0.2784968 , 0.23479551, 0.11209452, 
0.03348672, 0.17435497,\n   0.10784221, 0.1503846 , 0.08132076, 
0.26949698, 0.28150946,\n   0.08847237, 0.07874823, 

Processed: clinfo breaks libgpuarray autopkgtest on i386: numerical deltas

[Debian Bug Tracking System]

Processing control commands:

> found -1 clinfo/3.0.23.01.25-1
Bug #1031414 [src:clinfo, src:libgpuarray] clinfo breaks libgpuarray 
autopkgtest on i386: numerical deltas
Marked as found in versions clinfo/3.0.23.01.25-1.
> found -1 libgpuarray/0.7.6-13
Bug #1031414 [src:clinfo, src:libgpuarray] clinfo breaks libgpuarray 
autopkgtest on i386: numerical deltas
Marked as found in versions libgpuarray/0.7.6-13.

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

Bug#982864: More info

[Dima Kogan]

The issue is a failing test in test/run_tests.bash:

  head fish1.png > ${tmpdir}/fake.png
  "$pdiff" --verbose fish1.png ${tmpdir}/fake.png 2>&1 | grep -q 'Failed to 
load'
  rm -f ${tmpdir}/fake.png

Here it's making sure that we are able to detect a corrupt .png file,
and to throw an error. The actual image load is being done by
libfreeimage. For whatever reason, on amd64 (and other non-breaking
platforms) FreeImage_Load() returns NULL when given this corrupt file,
which is what the test expects. But on the failing platforms it throws a
c++ exception instead. The test doesn't catch this exception and
crashes, causing this FTBFS.

I tried to catch this exception nicely with the attached patch, but for
some reason it doesn't work. Since this problem isn't in the main part
of the library, we should simply disable this particular test to resolve
the FTBFS and this RC bug.

If I don't hear back in a few days, I'm going to do an NMU with this
patch.

Thanks.

diff --git a/rgba_image.cpp b/rgba_image.cpp
index 2ba9a67..b91407c 100644
--- a/rgba_image.cpp
+++ b/rgba_image.cpp
@@ -147,10 +147,17 @@ namespace pdiff
 }
 
 FIBITMAP *free_image = nullptr;
-if (auto temporary = FreeImage_Load(file_type, filename.c_str(), 0))
+try
 {
-free_image = FreeImage_ConvertTo32Bits(temporary);
-FreeImage_Unload(temporary);
+if (auto temporary = FreeImage_Load(file_type, filename.c_str(), 0))
+{
+free_image = FreeImage_ConvertTo32Bits(temporary);
+FreeImage_Unload(temporary);
+}
+}
+catch (...)
+{
+throw RGBImageException("Failed to load the image " + filename);
 }
 if (not free_image)
 {
diff --git a/test/run_tests.bash b/test/run_tests.bash
index 757a164..2b25c29 100755
--- a/test/run_tests.bash
+++ b/test/run_tests.bash
@@ -84,10 +84,6 @@ rm -f diff.png
 ls ${tmpdir}/diff.png
 rm -f ${tmpdir}/diff.png
 
-head fish1.png > ${tmpdir}/fake.png
-"$pdiff" --verbose fish1.png ${tmpdir}/fake.png 2>&1 | grep -q 'Failed to load'
-rm -f ${tmpdir}/fake.png
-
 mkdir -p ${tmpdir}/unwritable.png
 "$pdiff" --output ${tmpdir}/unwritable.png --verbose fish{1,2}.png 2>&1 | grep -q 'Failed to save'
 rmdir ${tmpdir}/unwritable.png

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Adrian Bunk]

On Wed, Feb 15, 2023 at 12:05:41AM +0100, Daniel Leidert wrote:
>...
> Instead, turning on this feature should be postponed for the next release 
> cycle
> where a proper transition can be done.
>...

On Thu, Feb 16, 2023 at 08:02:11PM +0100, Daniel Leidert wrote:
>...
> You completely miss the point here. It would lead to exactly the same
> situation if 2.07 would be the *first* to support it and could be
> shipped with Bookworm as long as e2fsprogs makes this breaking change
> now. But it makes a huge difference if 2.07 with a fix is released in
> around the same time as Bookworm and can spread until Trixie is
> prepared and the breaking change is postponed to Trixie.
>...

You are contradicting yourself by first unconditionally approving making 
the change in trixie, but later trying to make this conditional on grub 
making a new upstream release around the same time as Bookworm.

We can only control what is in Debian releases, we cannot be waiting
for godot^Wgrub making a new release before making a change in Debian.

The best default assumption when discussing whether the change should be 
made in bookworm or trixie is that there will be no new grub release 
during the next 2 years - it's only 2 years since the latest release
and there was even a 5 year gap between 2.00 and 2.02.

> Daniel

cu
Adrian

Bug#1031399: rsyslog: Log rotation broken on non-systemd systems

[Michael Biebl]

Control: severity -1 wishlist
Control: retitle -1 document log rotation on non-default inits

Am 16.02.23 um 15:41 schrieb Matthew Vernon:

Package: rsyslog
Version: 8.2212.0-1
Severity: serious

Hi,

When removing the systemv init scripts from rsyslog (which can be
managed by orphan-sysvinit-scripts), the following was also removed from
/usr/lib/rsyslog/rsyslog-rotate:

else
 invoke-rc.d rsyslog rotate > /dev/null

This means on non-systemd systems logrotate tries but fails to tell
rsyslog to rotate its logs.

Could you restore this, please? 


I don't plan to re-add this (btw, this would break if 
orphan-sysvinit-scripts is not installed).


I'll add a note to README.Debian to the logrotate section though, what 
users of non-default inits need to consider.


Michael


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1031394: marked as done (Please re-enable RTTI support in Sid/Bookworm, needed by at least Ceph)

[Debian Bug Tracking System]

Your message dated Thu, 16 Feb 2023 20:42:52 +
with message-id 
and subject line Bug#1031394: fixed in snappy 1.1.9-3
has caused the Debian Bug report #1031394,
regarding Please re-enable RTTI support in Sid/Bookworm, needed by at least Ceph
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.)


-- 
1031394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsnappy1v5
Version: 1.1.8-1
Severity: grave
Tags: patch

Dear Laszlo,

During my tests with Ceph, I noticed a grave regression: Ceph OSD (the process
that does the actual storage for Ceph) cannot use Snappy anymore, because it
can't find one symbole related to RTTI.

The consequence is that it cannot load and use Snappy. This may be ok for newer
clusters, but when upgrading from a cluster let's say in Bullseye, this may be
desastrous: data wont be able to be unpacked, which means data loss.

Please find attached a very small patch to re-enable RTTI support in Ceph.

Note related upstream bug in Ceph:
https://tracker.ceph.com/issues/53060

Moving forward, what I propose is probably the easiest way forward, at least
for Ceph. Doing extra patching of the Ceph would be a way more hazardous.

Your thoughts?

Cheers,

Thomas Goirand (zigo)
diff -Nru snappy-1.1.9/debian/changelog snappy-1.1.9/debian/changelog
--- snappy-1.1.9/debian/changelog   2022-05-08 18:26:22.0 +
+++ snappy-1.1.9/debian/changelog   2023-02-16 12:37:39.0 +
@@ -1,3 +1,10 @@
+snappy (1.1.9-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Re-enable RTTI support.
+
+ -- Thomas Goirand   Thu, 16 Feb 2023 12:37:39 +
+
 snappy (1.1.9-2) unstable; urgency=medium
 
   * Upload to Sid.
diff -Nru snappy-1.1.9/debian/patches/re-enable-rtti-support.patch 
snappy-1.1.9/debian/patches/re-enable-rtti-support.patch
--- snappy-1.1.9/debian/patches/re-enable-rtti-support.patch1970-01-01 
00:00:00.0 +
+++ snappy-1.1.9/debian/patches/re-enable-rtti-support.patch2023-02-16 
12:37:39.0 +
@@ -0,0 +1,29 @@
+Description: Re-enable RTTI support
+Author: Thomas Goirand 
+Forwarded: no
+Last-Update: 2023-02-16
+
+--- snappy-1.1.9.orig/CMakeLists.txt
 snappy-1.1.9/CMakeLists.txt
+@@ -51,10 +51,6 @@ if(CMAKE_CXX_COMPILER_ID STREQUAL "MSVC"
+   string(REGEX REPLACE "/EH[a-z]+" "" CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS}")
+   set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} /EHs-c-")
+   add_definitions(-D_HAS_EXCEPTIONS=0)
+-
+-  # Disable RTTI.
+-  string(REGEX REPLACE "/GR" "" CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS}")
+-  set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} /GR-")
+ else(CMAKE_CXX_COMPILER_ID STREQUAL "MSVC")
+   # Use -Wall for clang and gcc.
+   if(NOT CMAKE_CXX_FLAGS MATCHES "-Wall")
+@@ -76,10 +72,6 @@ else(CMAKE_CXX_COMPILER_ID STREQUAL "MSV
+   # Disable C++ exceptions.
+   string(REGEX REPLACE "-fexceptions" "" CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS}")
+   set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fno-exceptions")
+-
+-  # Disable RTTI.
+-  string(REGEX REPLACE "-frtti" "" CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS}")
+-  set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fno-rtti")
+ endif(CMAKE_CXX_COMPILER_ID STREQUAL "MSVC")
+ 
+ # BUILD_SHARED_LIBS is a standard CMake variable, but we declare it here to 
make
diff -Nru snappy-1.1.9/debian/patches/series snappy-1.1.9/debian/patches/series
--- snappy-1.1.9/debian/patches/series  2021-12-04 18:21:57.0 +
+++ snappy-1.1.9/debian/patches/series  2023-02-16 12:37:39.0 +
@@ -4,3 +4,4 @@
 0001-Add-inline-with-SNAPPY_ATTRIBUTE_ALWAYS_INLINE.patch
 use_packaged_testing.patch
 correct_testing_link.patch
+re-enable-rtti-support.patch
--- End Message ---
--- Begin Message ---
Source: snappy
Source-Version: 1.1.9-3
Done: Laszlo Boszormenyi (GCS) 

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated snappy 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

Processed: Re: Bug#1031399: rsyslog: Log rotation broken on non-systemd systems

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #1031399 [rsyslog] rsyslog: Log rotation broken on non-systemd systems
Severity set to 'wishlist' from 'serious'
> retitle -1 document log rotation on non-default inits
Bug #1031399 [rsyslog] rsyslog: Log rotation broken on non-systemd systems
Changed Bug title to 'document log rotation on non-default inits' from 
'rsyslog: Log rotation broken on non-systemd systems'.

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

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Sam Hartman]

> "Adrian" == Adrian Bunk  writes:

Adrian> Below is my attempt to give an overview of the situation,
Adrian> feel free to amend/correct if anything is missing or wrong.


I believe your summary is correct and includes the issues I am aware of.
I believe I am following things enough that I have confidence in that
conclusion.

Thanks much.


signature.asc
Description: PGP signature

Bug#1031388: icingaweb2-module-pdfexport: server software depending on chromium?

[Steve Langasek]

On Thu, Feb 16, 2023 at 12:45:20PM +0100, David Kunz wrote:

> > The current version of icingaweb2-module-pdfexport depends on chromium.
> All versions are like thes.

icingaweb2-module-pdfexport 0.9.1-2 did not have such a dependency.

> > icingaweb2 is a web service.  Depending on a graphical browser in a web
> > server component is not at all reasonable.
> I know, but upstream considers this to be the best possible way to solve
> this problem.

> Now we can provide this package as it is or no package exist and all
> packages that depends to it are unusable.

Ok, well, you can do as you wish in Debian.  This dependency is
unsatisfiable in Ubuntu because chromium is not available as a .deb package
in recent releases of Ubuntu, therefore this package will be removed there
as unsupportable.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Sam Hartman]

Replying off list, because I don't think it matters much for the RT
discussion.

> "Russ" == Russ Allbery  writes:
Russ> Yes, I'm probably understating the difficulty of making this
Russ> change in practice inside image building software as it's
Russ> currently constructed.

Russ> My concern about changing mkfs options is that I worry that
Russ> this would be a constantly-changing target that has to be
Russ> synchronized across multiple pieces of software that are not
Russ> currently well-aligned with file system development.

Sadly, supporting a new distribution in image building software is a
constantly changing target that requires small tweaks all the time.


Carthage has a function debian_container_to_vm that uses FAI  to turn a
directory tree into a VM image.
For bookworm, we end up needing to deal with systemd-resolved getting
split.
There was also some change in recent memory related to
apt-transport-https and when it was needed.

It's mostly small stuff, but you end up having a series of tweaks for
the guest system, no matter how much you wish you didn't.

There are similar tweaks at the debootstrap level, at the FAI level, and
even in the container frontends to a small extent.

I absolutely agree mkfs compatibility options would be great, but
chasing down how to call mkfs is par for the course.

I haven't looked much at vmdb2 because I disagree with the design
philosophy, but I think it has tweaks too.

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Adrian Bunk]

Disclaimer:
Like everyone else except Sebastian who commented in this bug so far,
I am not a member of the release team.

Below is my attempt to give an overview of the situation,
feel free to amend/correct if anything is missing or wrong.


1. Image creation tools need special cases for older distibutions

Image creation tools that support installing older/other
distributions must be able to handle such differences in general
(e.g. debootstrap has code to handle apt-transport-https being
required in some older releases), and have to add the (trivial)
support for this difference.

Sebastian has already created #1031364 for the original vmdb2 problem.


2. How many packages are affected?

There are to at least two classes of affected packages:
- Bootloaders that can read (or even write) ext4.
- Image creation tools in bookworm that can create < bookworm images

For both classes it is unclear how many packages still require fixing.

This is a major unclear question.


3. Image creation versus target usage

The original #1030846 was from Debian Installer developers,
and everything discussed there is around image creation.

The original discussion was about installing bookworm from bookworm.

Daniel is discussing installing older/other distributions from bookworm.

Noone seems to have discussed on-target usage, e.g. when arguing in 
#1030846 why there would not be a need for
   Breaks: grub2-common (<< 2.06-8~)
in e2fsprogs.

The version of e2fsprogs currently in bookworm is in bullseye-backports,
if the version with the new default goes into bookworm and unchanged
into bullseye-backports it's pretty obvious how this could screw
on-target users ("target" might also be called "desktop" or "server")
when creating new bootable partitions.


4. e2fsprogs should add Breaks on non-fixed versions of packages

For e2fsprogs in bullseye-backports such Breaks might only be a reminder 
that both the Breaks and the changed default should be reverted there, 
but in bookworm it would ensure that users don't end up with an 
incompatible combination of packages (e.g. if an older version of
grub or an image creation tool is pinned in apt).


5. Combination/Mix of packages from two adjacent Debian releases should work

A rule of thumb is that any combination/mix of packages permitted by the 
package manager from two adjacent Debian releases should work whenever 
reasonably possible, since this reduces problems for our users during an 
upgrade, when using backports, or when temporarily going back to the 
version of a package from the previous stable due to a regression.

The normal case (e.g. shared library linking) is that package 
dependencies ensure that package managers will only permit working 
combinations of packages.

Do we have any case where mixing bullseye and bookworm would not work 
with Breaks on all unfixed versions of bootloaders and image creation tools?


6. Any data/experience from metadata_csum enabled by default in stretch?

There seems to have been a similar situation with metadata_csum being 
enabled by default in stretch.

What data/experience exists about required fixes and problems from
that change?


7. It is late in the release cycle for such a change

The answer to point 2 is relevant whether it might be too late.


8. User documentation should document such incompatible changes

In whatever release this feature gets enabled by default,
a fresh bug against the release-notes pseudo-package with text
describing the incompatibility and possible workarounds should
be filed (Ted has already provided a draft text[1]).


9.There seems to be a similar situation with XFS bigtime

XFS is a less common filesystem, but what is discussed above
might also apply there.


10. Documentation for installing Debian from other distributions

Instructions for installing Debian from other distributions
need updating in any case.

Anything like [2] in the Bullseye Installation Guide will
be broken as soon as a different distribution changes the
default and needs updating, no matter what Debian does
in bookworm.


cu
Adrian

[1] https://lists.debian.org/debian-release/2023/02/msg00250.html
[2] https://www.debian.org/releases/stable/amd64/apds03.en.html