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

[Jonas Smedegaard]

Quoting Yadd (2023-02-17 08:21:59)
> 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

closure-compiler is known for years to be heavily outdated.

Unless those tools depend on *specific* features of closure-compiler
(e.g. some ancient form of what is nowadays called "tree-shaking"),
then I strongly recommend to patch those tools to instead use uglifyjs.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

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

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2023 10:07:55 +0100
with message-id <2fe674d6-4b4a-d7f7-7b86-51538d2f1...@debian.org>
and subject line Could not reproduce
has caused the Debian Bug report #1031477,
regarding python-oslo.concurrency: FTBFS: FileNotFoundError: [Errno 2] No such 
file or directory: '/tmp/tmpxztykbsm/tmpyb1wyys0/file-0'
to be marked as done.

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

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


-- 
1031477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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/t

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

[Thomas Goirand]

Hi Laszlo!

On 2/16/23 20:25, László Böszörményi (GCS) wrote:

Control: tags -1 +moreinfo

Dear Thomas,

On Thu, Feb 16, 2023 at 1:51 PM Thomas Goirand  wrote:

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.

  Isn't that because the upgrade path is not correct? New Ceph binaries
should handle this path.


Nop, CEPH-OSD before your patch couldn't load the .so, and printed a big 
warning in its logs because of it. I don't think that's related to a 
PATH thing.



  I'm quite surprised this was realized so late. You are probably not
the only person using Ceph. How others can use, how they upgraded
their Ceph clusters?


I well know others are using Ceph in Debian, but I don't think that 
there's so many that do so using Sid/Testing.


As we were working toward Puppet 7 in Debian, I had the whole end of 
Bookworm cycle broken, and couldn't do any type of setup until a 3 weeks 
before the actual freeze. This explains why I couldn't do many tests, as 
manual setup of whole clusters (made with 38 virtual machines in my full 
test env...) takes too much time. I'm currently unstacking problems as I 
fix them. :/


Thanks a lot for your prompt fix, this is very much appreciated!

Cheers,

Thomas Goirand (zigo)

Bug#1030941: marked as done (librsb: build-depends unsatisfiable on armhf)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2023 09:49:56 +
with message-id 
and subject line Bug#1030941: fixed in librsb 1.3.0.2+dfsg-2
has caused the Debian Bug report #1030941,
regarding librsb: build-depends unsatisfiable on armhf
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.)


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

Package: librsb
Version: 1.3.0.2+dfsg-1
Tags: bookworm, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable

librsb build-depends on coccinelle which appears to have been removed
on armhf, presumablly because it fails to build with an out of memory
error. This leaves your package in violation of the rc policy.

In general in cases like this there are three possible ways forward,
in roughly descending order of preference.

1. Fix the package you depend on so that it once again builds on
   all release architectures.
2. Modify your package to eliminate the build-dependency in question
   on architectures where it is not available.
3. Decide it is not reasonable to support your package on armhf and
   file a removal request with the ftp team.

I do not know enough about your individual package to say which are
feasible in your particular case.
--- End Message ---
--- Begin Message ---
Source: librsb
Source-Version: 1.3.0.2+dfsg-2
Done: Rafael Laboissière 

We believe that the bug you reported is fixed in the latest version of
librsb, 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.
Rafael Laboissière  (supplier of updated librsb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 16 Feb 2023 09:33:44 -0300
Source: librsb
Architecture: source
Version: 1.3.0.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Rafael Laboissière 
Closes: 1030941
Changes:
 librsb (1.3.0.2+dfsg-2) unstable; urgency=medium
 .
   * Drop coccinelle from Build-Depends list.
 Build-dependency on coccinelle was only necessary when compiling with
 gcc-11, which generated buggy code when option -O3 was used.
 Futhermore, to avoid inadvertently building on an out to date
 environment, build-dependency on gcc >= 12 is added and option
 --disable-extra-patches is now explicitly passed to the configure
 script. This change prevents FTBFS on amrhf, on which coccinelle has
 been removed. (Closes: #1030941)
   * d/control: Bump Standards-Version to 4.6.2 (no changes needed)
Checksums-Sha1:
 525a6b341f609de53e830817a564ac1dc64ce2c8 2459 librsb_1.3.0.2+dfsg-2.dsc
 c258c38dfe4ec3cc90d7410c9e9003ea04bfa90a 11176 
librsb_1.3.0.2+dfsg-2.debian.tar.xz
Checksums-Sha256:
 4779b5942969142b81a59ea27841e9f62156ee336ad9f188c50e7853d613bb9f 2459 
librsb_1.3.0.2+dfsg-2.dsc
 c6bd6501e48d8ac9ed53c8b3e5990ca4e1fe24c8ebbc4614b6e7e24e997574a2 11176 
librsb_1.3.0.2+dfsg-2.debian.tar.xz
Files:
 d645f9a76a90dcc3ba95c9a0138a45ba 2459 libs optional librsb_1.3.0.2+dfsg-2.dsc
 b8da3d688aa8260e00264cd9ec614c41 11176 libs optional 
librsb_1.3.0.2+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAmPvSWsSHHJhZmFlbEBk
ZWJpYW4ub3JnAAoJECEkqhmDeFyQdPUP/itxdEL0q3ivnnIdRrRxGoc/aqmmcLYd
Pmnx9laZ+2dwWglw75EIqtQPacl1t8X1+qs0C726XNWfEnif3qkQtKcooS0fAyJ5
Dd1m8R9fQy0d0BEV314Pfm1jz01ECF4AMmcwE3Adz259PkfUq4gXiFgBeQvCfub1
bjo7vrsLw7g0TcBEALBOdmWw6ZFb4RyUEXVYQ538LYcatP+NyL4FJRYksrp4QKT7
hAcCHnL/pc1SlVtBsQgJ7bnEZcBvgs4SOTfGVro2JRqMxwCBumQKBCFPllLLMTNz
RrmWHQQE5WIkcK60kjPPUbGTgUN3DeNByTwWXeEsLg3EFTTowKHD8ijaJDNLtZud
9IBmqSk73eE81+vfAzfPkZTNGLIh+CTaH4T4aUabn6U4y2S+CFK8OkE5p6LZ9qwN
rDfO0HvLr26GpublAx0Gotz2Wkwcd/56vkMKqM2zozcb8WtCT5uXxN3Z0GpAmG3O
99KKjeg9vgzZRxZhu2kwRGCbYn1vwdlMQiW3Cul6U/UK+zQ5fLYvhqOiz8GQ69s+
GksTwluZMWTbOQEf5Gw2xnOIKWJeRBAPFrmSNznN5FfPvt1GNx4lskj0JNzVC311
PEdHPW3bRoSJhJebBIhnmyLG/2QDkfUKY0RTuIhuRNkqQxc4YHIjHEB7RKRD5hvW
40jHrLBgh8MV
=I/YS
-END PGP SIGNATURE End Message ---

Processed: numerical differences in x87 fpu code generated by clang-14 and clang-15

[Debian Bug Tracking System]

Processing control commands:

> block 1031414 with -1
Bug #1031414 [src:pocl,src:libgpuarray] libgpuarray: i386 test fail with new 
pocl
1031414 was not blocked by any bugs.
1031414 was not blocking any bugs.
Added blocking bug(s) of 1031414: 1031500

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

Processed: Forward poliastro bug

[Debian Bug Tracking System]

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

> forwarded 1031451 https://github.com/poliastro/poliastro/issues/1614
Bug #1031451 [src:poliastro] poliastro: FTBFS: make[1]: *** [debian/rules:9: 
override_dh_auto_test] Error 1
Set Bug forwarded-to-address to 
'https://github.com/poliastro/poliastro/issues/1614'.
> thanks
Stopping processing here.

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

Bug#1031445: [Pkg-electronics-devel] Bug#1031445: camv-rnd: FTBFS: build-dependency not installable: librnd4-dev (>= 3.2.0)

[Bdale Garbee]

Lucas Nussbaum  writes:

> 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.

Sadly, librnd v4 is stuck in experimental, denied a transition slot
until trixie is opened.  All ringdove applications including pcb-rnd,
camv-rnd, and sch-rnd will be unbuildable until it migrates to unstable.

Bdale


signature.asc
Description: PGP signature

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

[Yavor Doganov]

Lucas Nussbaum wrote:
> Source: gnustep-base
> Version: 1.28.1+really1.28.0-5
> Severity: serious
> Justification: FTBFS

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

Thanks for the report; I believe this is due to tzdata #1031395.  I
cannot reproduce with tzdata/2022g-6 where the removal of
/etc/timezone has been reverted.

I'm unsure whether to reassign this bug or just close it when
tzdata/2022g-6 migrates to testing.

Processed: tagging 1001537, tagging 1027680, tagging 1031394, tagging 1031379 ..., tagging 1031346 ...

[Debian Bug Tracking System]

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

> tags 1001537 - sid bookworm
Bug #1001537 {Done: Yavor Doganov } [libgnustep-gui0.29] Cleanup 
in NSPopUpButtonCell -dealloc crashes gtamsanalyzer.app
Removed tag(s) sid and bookworm.
> tags 1027680 - sid bookworm
Bug #1027680 {Done: Simon McVittie } [src:gtk4] gtk4: FTBFS on 
some systems (with non-UTF-8 locale?)
Removed tag(s) bookworm and sid.
> tags 1031394 + sid bookworm
Bug #1031394 {Done: Laszlo Boszormenyi (GCS) } [libsnappy1v5] 
Please re-enable RTTI support in Sid/Bookworm, needed by at least Ceph
Added tag(s) sid and bookworm.
> tags 1031379 + sid bookworm
Bug #1031379 [kaffeine] (no subject)
Added tag(s) bookworm and sid.
> retitle 1031379 kaffeine: does not work
Bug #1031379 [kaffeine] (no subject)
Changed Bug title to 'kaffeine: does not work' from '(no subject)'.
> tags 1031346 + sid bookworm
Bug #1031346 [gr-dab] gr-dab not installable due to dependency on outdated 
gnuradio 3.8 (current is 3.10)
Added tag(s) sid and bookworm.
> tags 1031442 - sid bookworm
Bug #1031442 [src:gnustep-base] gnustep-base: FTBFS: dh_auto_test: error: make 
-j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 messages=yes returned exit 
code 2
Removed tag(s) sid and bookworm.
> tags 1031439 - sid bookworm
Bug #1031439 [src:gcc-sh-elf] gcc-sh-elf: FTBFS: make[6]: *** No rule to make 
target '../libsframe/libsframe.la', needed by 'libbfd.la'.  Stop.
Removed tag(s) sid and bookworm.
> reassign 1031490 ca-certificates
Bug #1031490 [nume_pachet] [INTL:ro] Romanian debconf templates translation of 
ca-certificates
Warning: Unknown package 'nume_pachet'
Bug reassigned from package 'nume_pachet' to 'ca-certificates'.
Ignoring request to alter found versions of bug #1031490 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1031490 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1001537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001537
1027680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027680
1031346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031346
1031379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031379
1031394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031394
1031439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031439
1031442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031442
1031490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#979090: Legally problematic GPL-3+ readline dependency

[Gregor Riepl]

Is anybody already working on this?

I will attempt to fix d/copyright and submit a patch or MR for review 
otherwise.

Processed: forcibly merging 1031302 1031487

[Debian Bug Tracking System]

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

> forcemerge 1031302 1031487
Bug #1031302 [src:devscripts] devscripts FTBFS with black 23.1.0
Bug #1031302 [src:devscripts] devscripts FTBFS with black 23.1.0
Added tag(s) sid and bookworm.
Bug #1031487 [src:devscripts] devscripts: FTBFS: AssertionError: black found 
code that needs reformatting:
Merged 1031302 1031487
> thanks
Stopping processing here.

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

Processed: Re: NVIDIA 340.108 driver gives Segmentation fault at launch all Qt software

[Debian Bug Tracking System]

Processing control commands:

> merge -1 1031489
Bug #1031488 [qt] NVIDIA 340.108 driver gives Segmentation fault at launch all 
Qt software
Warning: Unknown package 'qt'
Bug #1031489 [qt] NVIDIA 340.108 driver gives Segmentation fault at launch all 
Qt software
Merged 1031488 1031489
Warning: Unknown package 'qt'
> reassign -1 nvidia-legacy-340xx-driver 340.108-17
Bug #1031488 [qt] NVIDIA 340.108 driver gives Segmentation fault at launch all 
Qt software
Bug #1031489 [qt] NVIDIA 340.108 driver gives Segmentation fault at launch all 
Qt software
Warning: Unknown package 'qt'
Bug reassigned from package 'qt' to 'nvidia-legacy-340xx-driver'.
Bug reassigned from package 'qt' to 'nvidia-legacy-340xx-driver'.
Ignoring request to alter found versions of bug #1031488 to the same values 
previously set
Ignoring request to alter found versions of bug #1031489 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1031488 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1031489 to the same values 
previously set
Bug #1031488 [nvidia-legacy-340xx-driver] NVIDIA 340.108 driver gives 
Segmentation fault at launch all Qt software
Bug #1031489 [nvidia-legacy-340xx-driver] NVIDIA 340.108 driver gives 
Segmentation fault at launch all Qt software
Marked as found in versions nvidia-graphics-drivers-legacy-340xx/340.108-17.
Marked as found in versions nvidia-graphics-drivers-legacy-340xx/340.108-17.
> severity -1 serious
Bug #1031488 [nvidia-legacy-340xx-driver] NVIDIA 340.108 driver gives 
Segmentation fault at launch all Qt software
Bug #1031489 [nvidia-legacy-340xx-driver] NVIDIA 340.108 driver gives 
Segmentation fault at launch all Qt software
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> tag -1 upstream wontfix
Bug #1031488 [nvidia-legacy-340xx-driver] NVIDIA 340.108 driver gives 
Segmentation fault at launch all Qt software
Bug #1031489 [nvidia-legacy-340xx-driver] NVIDIA 340.108 driver gives 
Segmentation fault at launch all Qt software
Added tag(s) wontfix and upstream.
Added tag(s) upstream and wontfix.

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

Bug#1031462: marked as pending in libmemcached-libmemcached-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #1031462 in libmemcached-libmemcached-perl 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/perl-team/modules/packages/libmemcached-libmemcached-perl/-/commit/62573721de3ccafcdee9d5a595b6bc597f31e3b2


Add patch to mark version check in test as TODO.

The test compares the versions of Memcached::libmemcached and libmemcached;
in Debian we are building against the packaged libmemcached, which might
have a different (typically higher) version.

Thanks: Lucas Nussbaum for the bug report.
Closes: #1031462


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1031462

Processed: Bug#1031462 marked as pending in libmemcached-libmemcached-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1031462 [src:libmemcached-libmemcached-perl] 
libmemcached-libmemcached-perl: FTBFS: dh_auto_test: error: make -j8 test 
TEST_VERBOSE=1 returned exit code 2
Added tag(s) pending.

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

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

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2023 11:34:16 +
with message-id 
and subject line Bug#1031462: fixed in libmemcached-libmemcached-perl 
1.001801+dfsg-4
has caused the Debian Bug report #1031462,
regarding libmemcached-libmemcached-perl: FTBFS: dh_auto_test: error: make -j8 
test TEST_VERBOSE=1 returned exit code 2
to be marked as done.

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

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


-- 
1031462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 - &Memcached::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 

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

[Debian Bug Tracking System]

 .. .. .. 78% 97.4M 0s
>   6950K .. .. .. .. .. 79%  221M 0s
>   7000K .. .. .. .. .. 79%  137M 0s
>   7050K .. .. .. .. .. 80%  121M 0s
>   7100K .. .. .. .. .. 80%  121M 0s
>   7150K .. .. .. .. .. 81%  161M 0s
>   7200K .. .. .. .. .. 82%  123M 0s
>   7250K .. .. .. .. .. 82%  108M 0s
>   7300K .. .. .. .. .. 83%  123M 0s
>   7350K .. .. .. .. .. 83%  107M 0s
>   7400K .. .. .. .. .. 84%  104M 0s
>   7450K .. .. .. .. .. 84%  140M 0s
>   7500K .. .. .. .. .. 85% 92.6M 0s
>   7550K .. .. .. .. .. 86%  121M 0s
>   7600K .. .. .. .. .. 86%  164M 0s
>   7650K .. .. .. .. .. 87% 92.4M 0s
>   7700K .. .. .. .. .. 87%  144M 0s
>   7750K .. .. .. .. .. 88%  124M 0s
>   7800K .. .. .. .. .. 88% 95.7M 0s
>   7850K .. .. .. .. .. 89%  137M 0s
>   7900K .. .. .. .. .. 90%  107M 0s
>   7950K .. .. .. .. .. 90%  121M 0s
>   8000K .. .. .. .. .. 91%  107M 0s
>   8050K .. .. .. .. .. 91%  103M 0s
>   8100K .. .. .. .. .. 92%  212M 0s
>   8150K .. .. .. .. .. 92%  106M 0s
>   8200K .. .. .. .. .. 93%  144M 0s
>   8250K .. .. .. .. .. 94%  137M 0s
>   8300K .. .. .. .. .. 94%  116M 0s
>   8350K .. .. .. .. .. 95%  120M 0s
>   8400K .. .. .. .. .. 95%  110M 0s
>   8450K .. .. .. .. .. 96% 97.6M 0s
>   8500K .. .. .. .. .. 96%  133M 0s
>   8550K .. .. .. .. .. 97%  141M 0s
>   8600K .. .. .. .. .. 97%  114M 0s
>   8650K .. .. .. .. .. 98%  122M 0s
>   8700K .. .. .. .. .. 99%  122M 0s
>   8750K .. .. .. .. .. 99%  141M 0s
>   8800K .. .. 100% 92.4M=0.1s
> 
> 2023-02-17 01:24:16 (73.3 MB/s) - ‘amd64.Packages.xz’ saved [9040064/9040064]
> 
> amd64.Packages.xz: OK
> Building 20220917, but bookworm has 20230207, failing the build
> Version not found in bookworm, no fallback defined
> make[1]: *** [debian/rules:20: get-images-amd64] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/debian-installer-netboot-images_20220917+rebuild1_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&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230216&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 20230217

Hi Lucas,

Lucas Nussbaum  (2023-02-17):
> 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
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

It'd be great to skip debian-installer and debian-installer-netboot-images
for those automated bug reports. The former depends on the contents of the
archive, and we need it to release; it can't be missed. The latter also
depends on the contents of the archive, and goes with the former on each
d-i release.

Having those bugs filed means having to remember to copy-paste bug numbers,
possibly miss a dinstall or britney run when we're in the thick of it.

That's not really helping, quite the opposite…


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature
--- End Message ---

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

[Lucas Nussbaum]

Hi,

On 17/02/23 at 13:07 +0100, Cyril Brulebois wrote:
> Version: 20230217
> 
> Hi Lucas,
> 
> Lucas Nussbaum  (2023-02-17):
> > 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
> > 
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> 
> It'd be great to skip debian-installer and debian-installer-netboot-images
> for those automated bug reports. The former depends on the contents of the
> archive, and we need it to release; it can't be missed. The latter also
> depends on the contents of the archive, and goes with the former on each
> d-i release.
> 
> Having those bugs filed means having to remember to copy-paste bug numbers,
> possibly miss a dinstall or britney run when we're in the thick of it.
> 
> That's not really helping, quite the opposite…

OK, I remembered about skipping debian-installer, but wasn't sure about
debian-installer-netboot-images

Lucas

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

[Cyril Brulebois]

Lucas Nussbaum  (2023-02-17):
> OK, I remembered about skipping debian-installer, but wasn't sure about
> debian-installer-netboot-images

Thanks and sorry for being a pain, I know we're the usual ugly duckling
in the project…


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1031396: Unable to upgrade to *gnome* 1:43+1 with `apt full-upgrade`

[Dylan Aïssi]

Hi,

This seems to be solved by adding pulseaudio-module-bluetooth in Conflicts and
Replaces of pipewire-audio. pipewire-audio already conflicts and replaces
pulseaudio for some reasons, but looks like it is not enough.

Best regards,
Dylan

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

[James Addison]

Source: python-zstandard
Followup-For: Bug #1031443
Control: reassign -1 python3-zstandard 0.19.0-3
Control: affects -1 + src:python-zstandard
Control: merge -1 1031293

Processed (with 1 error): Re: python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 105

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3-zstandard 0.19.0-3
Bug #1031443 [src:python-zstandard] 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 zstd 
headers, 10502 hardcoded in the cext)
Bug reassigned from package 'src:python-zstandard' to 'python3-zstandard'.
No longer marked as found in versions python-zstandard/0.19.0-3.
Ignoring request to alter fixed versions of bug #1031443 to the same values 
previously set
Bug #1031443 [python3-zstandard] 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 zstd 
headers, 10502 hardcoded in the cext)
Marked as found in versions python-zstandard/0.19.0-3.
> affects -1 + src:python-zstandard
Bug #1031443 [python3-zstandard] 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 zstd 
headers, 10502 hardcoded in the cext)
Added indication that 1031443 affects src:python-zstandard
> merge -1 1031293
Bug #1031443 [python3-zstandard] 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 zstd 
headers, 10502 hardcoded in the cext)
Unable to merge bugs because:
affects of #1031293 is 'src:rpmlint,src:libzstd' not 'src:python-zstandard'
Failed to merge 1031443: Did not alter merged bugs.


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

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

[James Addison]

Package: python3-zstandard
Followup-For: Bug #1031293
Control: affects -1 + src:libzstd src:python-scrapy src:rpmlint

Processed: Re: python3-zstandard 0.19.0-3 supports only libzstd 1.5.2

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:libzstd src:python-scrapy src:rpmlint
Bug #1031293 [python3-zstandard] python3-zstandard 0.19.0-3 supports only 
libzstd 1.5.2
Added indication that 1031293 affects src:python-scrapy

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

Processed (with 1 error): Re: python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 105

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:libzstd src:python-scrapy src:rpmlint
Bug #1031443 [python3-zstandard] 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 zstd 
headers, 10502 hardcoded in the cext)
Added indication that 1031443 affects src:libzstd, src:python-scrapy, and 
src:rpmlint
> merge -1 1031293
Bug #1031443 [python3-zstandard] 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 zstd 
headers, 10502 hardcoded in the cext)
Unable to merge bugs because:
affects of #1031293 is 'src:libzstd,src:python-scrapy,src:rpmlint' not 
'src:python-zstandard,src:libzstd,src:rpmlint,src:python-scrapy'
Failed to merge 1031443: Did not alter merged bugs.


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

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

[James Addison]

Source: python-scrapy
Followup-For: Bug #1031449
Control: package -1 python3-zstandard 0.19.0-3
Control: affects -1 + src:libzstd src:python-scrapy src:rpmlint
Control: merge -1 1031293

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

[James Addison]

Package: python3-zstandard
Followup-For: Bug #1031443
Control: affects -1 + src:libzstd src:python-scrapy src:rpmlint
Control: merge -1 1031293

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

[James Addison]

Package: python3-zstandard
Followup-For: Bug #1031293
Control: affects -1 + src:python-zstandard

Processed: Re: python3-zstandard 0.19.0-3 supports only libzstd 1.5.2

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:python-zstandard
Bug #1031293 [python3-zstandard] python3-zstandard 0.19.0-3 supports only 
libzstd 1.5.2
Added indication that 1031293 affects src:python-zstandard

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

Bug#1031195: marked as done (os-autoinst: FTBFS on several release architectures)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2023 13:19:17 +
with message-id 
and subject line Bug#1031195: fixed in os-autoinst 4.6.1674476646.0798a03c-2
has caused the Debian Bug report #1031195,
regarding os-autoinst: FTBFS on several release architectures
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.)


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

Package: src:os-autoinst
Version: 4.6.1674476646.0798a03c-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-arch
dh binary-arch --buildsystem=cmake+ninja --builddirectory=build
   dh_update_autotools_config -a -O--buildsystem=cmake\+ninja 
-O--builddirectory=build
   dh_autoreconf -a -O--buildsystem=cmake\+ninja -O--builddirectory=build
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
cp -a /<>/isotovideo /<>/isotovideo.orig
sed -i 's/my $thisversion =.*/my $thisversion = "4.6.1674476646.0798a03c-1";/' 
/<>/isotovideo
# Following opensuse .spec : don't require qemu and exclude known flaky tests
cd t && rm -f 02-test_ocr.t 07-commands.t 13-osutils.t 14-isotovideo.t 
18-qemu-options.t 18-backend-qemu.t 28-signalblocker.t 99-full-stack.t
# Philip Hands's Laptop seems unable to deal with these tests, so kludge around 
them
if [ "rummy.hk.hands.com" = "" ] || true ; then cd t ; rm -f 
20-openqa-isotovideo-utils.t 21-needle-downloader.t 27-consoles-vnc.t 27-consoles-local_xvnc.t 
27-consoles-vmware.t 29-backend-ipmi.t 30-mmapi.t 30-make.t ; fi
rm -f xt/30-make.t
dh_auto_configure -- -DOS_AUTOINST_DOC_DIR=/usr/share/doc/os-autoinst \

[... snipped ...]

3: ok 14 - Call ret_hash() in ARRAY context
3: ok 15 - Expected call parameters!
3: ok 16 - Call ret_hash_empty() in SCALAR context
3: ok 17 - Call ret_hash_empty() in ARRAY context
3: ok 18 - Expected call parameters!
3: ok 19 - Call ret_hash_ref() in SCALAR context
3: ok 20 - Call ret_hash_ref() in ARRAY context
3: ok 21 - Expected call parameters!
3: ok 22 - Call ret_hash_ref_empty() in SCALAR context
3: ok 23 - Call ret_hash_ref_empty() in ARRAY context
3: ok 24 - Expected call parameters!
3: ok 25 - Call ret_scalar() in SCALAR context
3: ok 26 - Call ret_scalar() in ARRAY context
3: ok 27 - Expected call parameters!
3: ok 28 - Call ret_undef() in SCALAR context
3: ok 29 - Call ret_undef() in ARRAY context
3: ok 30 - Expected call parameters!
3: ok 31 - Call ret_list() in SCALAR context
3: ok 32 - Call ret_list() in ARRAY context
3: ok 33 - Expected call parameters!
3: ok 34 - Call ret_list_empty() in SCALAR context
3: ok 35 - Call ret_list_empty() in ARRAY context
3: ok 36 - Expected call parameters!
3: ok 37 - Exception forwarded
3: ok 38 - Exception was JSON encoded
3: ok 39 - Got expected () arguments
3: ok 40 - Call without arguments
3: ok 41 - Got expected (a,b,c,d,e) arguments
3: ok 42 - Call with 5 arguments
3: ok 43 - Got expected (foo,bar) arguments
3: ok 44 - Call with hash as argument
3: 1..44
3: ok 2 - testapi::console() => backend::console_proxy => 
backend::baseclass::proxy_console_call()
3: ok 3 - no (unexpected) warnings (via done_testing)
3: 1..3
3: ok
3: 
./t/33-vagrant.t
 ...
3: # Subtest: Vagrantfile for the libvirt provider
3: ok 1 - Backend variable matches box_name class variable
3: ok 2 - Backend variable matches provider class variable
3: 1..2
3: ok 1 - Vagrantfile for the libvirt provider
3: # Subtest: Vagrantfile for the virtualbox provider
3: ok 1 - Backend variable matches box_name class variable
3: ok 2 - Backend variable matches provider class variable
3: 1..2
3: ok 2 - Vagrantfile for the virtualbox provider
3: # Subtest: Vagrantfile with a box url
3: ok 1 - Backend variable matches box_name class variable
3: ok 2 - Backend variable matches provider class variable
3: ok 3 - Backend variable matches box_url class variable
3: 1..3
3: ok 3 - Vagrantfile with a box url
3: # Subtest: backend creation dies when VAGRANT_ASSETDIR cannot be opened
3: ok 1 - opendir error message is present in the output
3: 1..1
3: ok 4 - backend creation dies when VAGRANT_ASSETDIR cannot 

Processed (with 1 error): Re: 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

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3-zstandard 0.19.0-3
Bug #1031449 [src:python-scrapy] 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 headers, 10502 
hardcoded in the cext)
Bug reassigned from package 'src:python-scrapy' to 'python3-zstandard'.
No longer marked as found in versions python-scrapy/2.8.0-1.
Ignoring request to alter fixed versions of bug #1031449 to the same values 
previously set
Bug #1031449 [python3-zstandard] 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 headers, 10502 
hardcoded in the cext)
Marked as found in versions python-zstandard/0.19.0-3.
> affects -1 + src:libzstd src:python-scrapy src:python-zstandard src:rpmlint
Bug #1031449 [python3-zstandard] 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 headers, 10502 
hardcoded in the cext)
Added indication that 1031449 affects src:libzstd, src:python-scrapy, 
src:python-zstandard, and src:rpmlint
> merge -1 1031293
Bug #1031449 [python3-zstandard] 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 headers, 10502 
hardcoded in the cext)
Unable to merge bugs because:
affects of #1031293 is 
'src:python-scrapy,src:python-zstandard,src:rpmlint,src:libzstd' not 
'src:python-zstandard,src:libzstd,src:python-scrapy,src:rpmlint'
Failed to merge 1031449: Did not alter merged bugs.


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

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

[James Addison]

Source: python-scrapy
Followup-For: Bug #1031449
Control: reassign -1 python3-zstandard 0.19.0-3
Control: affects -1 + src:libzstd src:python-scrapy src:python-zstandard 
src:rpmlint
Control: merge -1 1031293

Bug#1031396: Unable to upgrade to *gnome* 1:43+1 with `apt full-upgrade`

[Simon McVittie]

Control: reassign -1 pipewire
Control: affects -1 = gnome src:meta-gnome3

On Fri, 17 Feb 2023 at 13:25:47 +0100, Dylan Aïssi wrote:
> This seems to be solved by adding pulseaudio-module-bluetooth in Conflicts and
> Replaces of pipewire-audio. pipewire-audio already conflicts and replaces
> pulseaudio for some reasons, but looks like it is not enough.

Thanks for identifying that solution. Please could you make that change
in the next pipewire upload? (Note that this is currently marked as RC.)
I don't think this is likely to be addressable from the meta-gnome3 side,
so I'm reassigning this.

As far as I can see, that wouldn't regress co-installability, because
pipewire-audio and pulseaudio-module-bluetooth are already not
co-installable (pipewire-audio Conflicts pulseaudio,
pulseaudio-module-bluetooth Depends pulseaudio)

Adding technically-unnecessary Conflicts/Replaces or Breaks/Replaces is
sometimes necessary to hint apt's heuristics for "should I be willing to
remove package A to get package B upgraded?" into doing what we consider
to be the right thing.

smcv

Processed: Re: Bug#1031396: Unable to upgrade to *gnome* 1:43+1 with `apt full-upgrade`

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 pipewire
Bug #1031396 [gnome] Unable to upgrade to *gnome* 1:43+1 with `apt full-upgrade`
Bug reassigned from package 'gnome' to 'pipewire'.
No longer marked as found in versions meta-gnome3/1:43+1.
Ignoring request to alter fixed versions of bug #1031396 to the same values 
previously set
> affects -1 = gnome src:meta-gnome3
Bug #1031396 [pipewire] Unable to upgrade to *gnome* 1:43+1 with `apt 
full-upgrade`
Removed indication that 1031396 affects src:pipewire
Added indication that 1031396 affects src:meta-gnome3 and gnome

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

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

[James Addison]

Package: python3-zstandard
Followup-For: Bug #1031443
Control: affects -1 - src:python-scrapy src:rpmlint
Control: affects -1 + src:python-scrapy src:rpmlint
Control: merge -1 1031293

Processed (with 1 error): Re: python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 105

[Debian Bug Tracking System]

Processing control commands:

> affects -1 - src:python-scrapy src:rpmlint
Bug #1031443 [python3-zstandard] 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 zstd 
headers, 10502 hardcoded in the cext)
Removed indication that 1031443 affects src:python-scrapy and src:rpmlint
> affects -1 + src:python-scrapy src:rpmlint
Bug #1031443 [python3-zstandard] 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 zstd 
headers, 10502 hardcoded in the cext)
Added indication that 1031443 affects src:python-scrapy and src:rpmlint
> merge -1 1031293
Bug #1031443 [python3-zstandard] 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 zstd 
headers, 10502 hardcoded in the cext)
Unable to merge bugs because:
affects of #1031293 is 
'src:python-scrapy,src:python-zstandard,src:rpmlint,src:libzstd' not 
'src:python-scrapy,src:python-zstandard,src:libzstd,src:rpmlint'
Failed to merge 1031443: Did not alter merged bugs.


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

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

[Shengjing Zhu]

On Thu, 16 Feb 2023 12:45:20 +0100 David Kunz  wrote:
>
> > The current version of icingaweb2-module-pdfexport depends on chromium.
> All versions are like thes.
>
> > 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.

You can demote chromium to Recommends. There are multiple benefits:
+ Users can use proprietary version of chrome from Google
+ Users can use snap/flatpak to install the latest chromium.
+ Users can use remote chromium as documented here:
https://github.com/Icinga/icingaweb2-module-pdfexport/blob/master/doc/02-Installation.md#using-a-remote-chromechromium

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

[James Addison]

Package: python3-zstandard
Followup-For: Bug #1031449
Control: affects -1 - src:rpmlint src:python-zstandard src:python-scrapy
Control: affects -1 + src:rpmlint src:python-scrapy src:python-zstandard
Control: merge -1 1031293

Processed (with 1 error): Re: 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

[Debian Bug Tracking System]

Processing control commands:

> affects -1 - src:rpmlint src:python-zstandard src:python-scrapy
Bug #1031449 [python3-zstandard] 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 headers, 10502 
hardcoded in the cext)
Removed indication that 1031449 affects src:rpmlint, src:python-zstandard, and 
src:python-scrapy
> affects -1 + src:rpmlint src:python-scrapy src:python-zstandard
Bug #1031449 [python3-zstandard] 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 headers, 10502 
hardcoded in the cext)
Added indication that 1031449 affects src:rpmlint, src:python-scrapy, and 
src:python-zstandard
> merge -1 1031293
Bug #1031449 [python3-zstandard] 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 headers, 10502 
hardcoded in the cext)
Unable to merge bugs because:
affects of #1031293 is 
'src:python-scrapy,src:python-zstandard,src:rpmlint,src:libzstd' not 
'src:python-scrapy,src:rpmlint,src:libzstd,src:python-zstandard'
Failed to merge 1031449: Did not alter merged bugs.


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

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

[James Addison]

Package: python3-zstandard
Followup-For: Bug #1031443
Control: affects -1 - src:rpmlint
Control: affects -1 + src:rpmlint
Control: merge -1 1031293

Processed (with 1 error): Re: python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 105

[Debian Bug Tracking System]

Processing control commands:

> affects -1 - src:rpmlint
Bug #1031443 [python3-zstandard] 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 zstd 
headers, 10502 hardcoded in the cext)
Removed indication that 1031443 affects src:rpmlint
> affects -1 + src:rpmlint
Bug #1031443 [python3-zstandard] 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 zstd 
headers, 10502 hardcoded in the cext)
Added indication that 1031443 affects src:rpmlint
> merge -1 1031293
Bug #1031443 [python3-zstandard] 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 zstd 
headers, 10502 hardcoded in the cext)
Unable to merge bugs because:
affects of #1031293 is 
'src:python-scrapy,src:python-zstandard,src:rpmlint,src:libzstd' not 
'src:rpmlint,src:python-zstandard,src:python-scrapy,src:libzstd'
Failed to merge 1031443: Did not alter merged bugs.


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

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

[FC Stegerman]

Should be fixed by [1]

- FC

[1] https://salsa.debian.org/reproducible-builds/diffoscope/-/merge_requests/126

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

[James Addison]

Package: python3-zstandard
Followup-For: Bug #1031443
Control: affects -1 = src:python-scrapy src:libzstd src:rpmlint 
src:python-zstandard
Control: merge -1 1031293

Processed (with 1 error): Re: python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 105

[Debian Bug Tracking System]

Processing control commands:

> affects -1 = src:python-scrapy src:libzstd src:rpmlint src:python-zstandard
Bug #1031443 [python3-zstandard] 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 zstd 
headers, 10502 hardcoded in the cext)
Added indication that 1031443 affects src:python-scrapy, src:rpmlint, 
src:python-zstandard, and src:libzstd
> merge -1 1031293
Bug #1031443 [python3-zstandard] 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 zstd 
headers, 10502 hardcoded in the cext)
Unable to merge bugs because:
affects of #1031293 is 
'src:python-scrapy,src:python-zstandard,src:rpmlint,src:libzstd' not 
'src:rpmlint,src:python-scrapy,src:python-zstandard,src:libzstd'
Failed to merge 1031443: Did not alter merged bugs.


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

Processed: Bug#1031396 marked as pending in pipewire

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1031396 [pipewire] Unable to upgrade to *gnome* 1:43+1 with `apt 
full-upgrade`
Added tag(s) pending.

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

Bug#1031396: marked as pending in pipewire

[Dylan Aïssi]

Control: tag -1 pending

Hello,

Bug #1031396 in pipewire 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/utopia-team/pipewire/-/commit/cdd78bc461a98e96ac8a96d6fcb95bef807c5805


pipewire-audio: add pulseaudio-module-bluetooth in Conflicts+Replaces (Closes: 
#1031396)

Signed-off-by: Dylan Aïssi 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1031396

Processed: Bug#1027870 marked as pending in dm-writeboost

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1027870 [src:dm-writeboost] dm-writeboost: please switch to B-D: 
dh-sequence-dkms (or dh-dkms)
Added tag(s) pending.

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

Bug#1027870: marked as pending in dm-writeboost

[Andreas Beckmann]

Control: tag -1 pending

Hello,

Bug #1027870 in dm-writeboost 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/debian/dm-writeboost/-/commit/3415bc8e6372b6bf3b3aa39bcee9827727d27e7e


Switch to dh-sequence-dkms.

Closes: #1027870


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1027870

Processed: Re: dm-writeboost-dkms: module fails to build for Linux 6.1: error: ‘struct dm_io_request’ has no member named ‘bi_op’

[Debian Bug Tracking System]

Processing control commands:

> tag -1 fixed-upstream pending
Bug #1029261 [dm-writeboost-dkms] dm-writeboost-dkms: module fails to build for 
Linux 6.1: error: ‘struct dm_io_request’ has no member named ‘bi_op’
Added tag(s) fixed-upstream and pending.
> tag 1027870 pending
Bug #1027870 [src:dm-writeboost] dm-writeboost: please switch to B-D: 
dh-sequence-dkms (or dh-dkms)
Ignoring request to alter tags of bug #1027870 to the same tags previously set

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

Bug#1029261: dm-writeboost-dkms: module fails to build for Linux 6.1: error: ‘struct dm_io_request’ has no member named ‘bi_op’

[Andreas Beckmann]

Control: tag -1 fixed-upstream pending
Control: tag 1027870 pending

On Fri, 20 Jan 2023 13:37:01 +0100 Andreas Beckmann  wrote:

/var/lib/dkms/dm-writeboost/2.2.15/build/dm-writeboost.h:506:46: error: ‘struct 
dm_io_request’ has no member named ‘bi_op’; did you mean ‘bi_opf’?


This is fixed in a new upstream release which I've NMUed to DELAYED/5.
The changes can be found in branch 2.2.16 on salsa.


Andreas

Bug#1030967: marked as done (vip-manager2: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2023 14:38:35 +
with message-id 
and subject line Bug#1030967: fixed in vip-manager2 2.1.0-4
has caused the Debian Bug report #1030967,
regarding vip-manager2: autopkgtest failure
to be marked as done.

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

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


-- 
1030967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vip-manager2
Version: 2.1.0-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/v/vip-manager2/31169753/log.gz

...
autopkgtest [15:34:34]: test cacert_test: [---
dpkg-architecture: warning: cannot determine CC system type, falling back to 
default (native compilation)
2023-02-08 15:34:34.852072 W | pkg/flags: unrecognized environment variable 
ETCD_UNSUPPORTED_ARCH=
[WARNING] Deprecated '--logger=capnslog' flag is set; use '--logger=zap' flag 
instead
2023-02-08 15:34:34.852125 I | etcdmain: etcd Version: 3.4.23
2023-02-08 15:34:34.852128 I | etcdmain: Git SHA: Not provided (use ./build 
instead of go build)
2023-02-08 15:34:34.852130 I | etcdmain: Go Version: go1.19.4
2023-02-08 15:34:34.852132 I | etcdmain: Go OS/Arch: linux/amd64
2023-02-08 15:34:34.852136 I | etcdmain: setting maximum number of CPUs to 64, 
total number of available CPUs is 64
2023-02-08 15:34:34.852140 W | etcdmain: no data-dir provided, using default 
data-dir ./default.etcd
[WARNING] Deprecated '--logger=capnslog' flag is set; use '--logger=zap' flag 
instead
2023-02-08 15:34:34.852454 C | etcdmain: listen tcp 127.0.0.1:2380: bind: 
address already in use
Ncat: Version 7.93 ( https://nmap.org/ncat )
Ncat: Listening on 0.0.0.0:12345
{"level":"warn","ts":"2023-02-08T15:34:41.855Z","caller":"clientv3/retry_interceptor.go:62","msg":"retrying
 of unary invoker 
failed","target":"endpoint://client-42f26925-0cba-4cc3-b014-8c4d184782bc/127.0.0.1:2379","attempt":0,"error":"rpc
 error: code = DeadlineExceeded desc = latest balancer error: all SubConns are 
in TransientFailure"}
Error: context deadline exceeded
{"level":"warn","ts":"2023-02-08T15:34:48.868Z","caller":"clientv3/retry_interceptor.go:62","msg":"retrying
 of unary invoker 
failed","target":"endpoint://client-285abd0a-edf8-4146-a93d-ee1dc21cf16b/127.0.0.1:2379","attempt":0,"error":"rpc
 error: code = DeadlineExceeded desc = latest balancer error: all SubConns are 
in TransientFailure"}
Error: context deadline exceeded
### Some tests failed! ###
autopkgtest [15:34:49]: test cacert_test: ---]
autopkgtest [15:34:49]: test cacert_test:  - - - - - - - - - - results - - - - 
- - - - - -
cacert_test  FAIL non-zero exit status 1
autopkgtest [15:34:49]: test clientcert_test: preparing testbed
Reading package lists...
Building dependency tree...
Reading state information...
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up autopkgtest-satdep (0) ...
(Reading database ... 12989 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [15:34:51]: test clientcert_test: [---
dpkg-architecture: warning: cannot determine CC system type, falling back to 
default (native compilation)
2023-02-08 15:34:51.513732 W | pkg/flags: unrecognized environment variable 
ETCD_UNSUPPORTED_ARCH=
[WARNING] Deprecated '--logger=capnslog' flag is set; use '--logger=zap' flag 
instead
2023-02-08 15:34:51.513777 I | etcdmain: etcd Version: 3.4.23
2023-02-08 15:34:51.513781 I | etcdmain: Git SHA: Not provided (use ./build 
instead of go build)
2023-02-08 15:34:51.513783 I | etcdmain: Go Version: go1.19.4
2023-02-08 15:34:51.513787 I | etcdmain: Go OS/Arch: linux/amd64
2023-02-08 15:34:51.513789 I | etcdmain: setting maximum number of CPUs to 64, 
total number of available CPUs is 64
2023-02-08 15:34:51.513793 W | etcdmain: no data-dir provided, using default 
data-dir ./default.etcd
[WARNING] Deprecated '--logger=capnslog' flag is set; use '--logger=zap' flag 
instead
2023-02-08 15:34:51.514308 C | etcdmain: listen tcp 127.0.0.1:2380: bind: 
address already in use
Ncat: Version 7.93 ( https://nmap.org/ncat )
Ncat: Listening on 0.0.0.0:12345
{"level":"warn","ts":"2023-02-08T15:34:58.517Z","caller":"clientv3/retry_interceptor.go:62","msg":"retrying
 of unary invoker 
failed","target":"endpoint://client-06e11fbd-d9ed-4e1b-9c26-fe8524214f9a/127.0.0.1:2379","attempt"

Bug#1031512: docbook-defguide: non-free GFDL-licensed files

[Bastian Germann]

Source: docbook-defguide
Severity: serious
Version: 2.0.17+svn9912-2

Some files in the package are licensed under the non-free variant of the GFDL 
with explicit Invariant Section.
Please repack to remove them.

Bug#1031513: clamav: new upstream security release, CVE-2023-20032

[Joost van Baal-Ilić]

Package: clamav
Severity: grave

Hi,

As you'll likely know there is
https://security-tracker.debian.org/tracker/CVE-2023-20032 and
https://blog.clamav.net/2023/02/clamav-01038-01052-and-101-patch.html

"CVE-2023-20032: Fixed a possible remote code execution vulnerability in the
HFS+ file parser. The issue affects versions 1.0.0 and earlier, 0.105.1 and
earlier, and 0.103.7 and earlier. Thank you to Simon Scannell for reporting
this issue."

Upstream released fixed tarballs for all their supported branches.  I've
managed to build 0.103.8+dfsg-0+deb10u1~uvt0 for Debian 10/buster from that,
it's available from https://non-gnu.uvt.nl/debian/buster/clamav/ (including
sources).

We are now running this build on the Tilburg University mail infrastructure,
it might work for others too.

Anybody working on a proper Debian supplied fix: feel free to contact me (via
IRC, e.g.)

HTH, Bye,

Joost

-- 
Joost van Baal-Ilić   http://abramowitz.uvt.nl/
 Tilburg University
mailto:joostvb.uvt.nl   The Netherlands


signature.asc
Description: PGP signature

Bug#1031396: marked as done (Unable to upgrade to *gnome* 1:43+1 with `apt full-upgrade`)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2023 15:56:00 +
with message-id 
and subject line Bug#1031396: fixed in pipewire 0.3.65-3
has caused the Debian Bug report #1031396,
regarding Unable to upgrade to *gnome* 1:43+1 with `apt full-upgrade`
to be marked as done.

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

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


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

Package: gnome
Version: 1:43+1
Severity: normal


Dear Debian folks,


On Debian sid/unstable trying to upgrade *gnome{,-core}*, in this case 
from 1:42+8 to 1:43+1, does not work with `apt upgrade`, pt 
full-upgrade` or `apt-get dist-upgrade`. The packages are kept back.


$ sudo apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  gnome gnome-core
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

`apt install gnome` is able to find a way for some reason.

$ sudo apt install gnome
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  gnome-core pipewire-alsa pipewire-audio
Suggested packages:
  alacarte empathy firefox-esr-l10n-all | firefox-l10n-all goobox | 
sound-juicer polari vinagre

  webext-ublock-origin-firefox | webext-ublock-origin-chromium
The following packages will be REMOVED:
  pulseaudio pulseaudio-module-bluetooth
The following NEW packages will be installed:
  pipewire-alsa pipewire-audio
The following packages will be upgraded:
  gnome gnome-core
2 upgraded, 2 newly installed, 2 to remove and 0 not upgraded.
Need to get 81.1 kB of archives.
After this operation, 6,798 kB disk space will be freed.
Do you want to continue? [Y/n]


Kind regards,

Paul
--- End Message ---
--- Begin Message ---
Source: pipewire
Source-Version: 0.3.65-3
Done: Dylan Aïssi 

We believe that the bug you reported is fixed in the latest version of
pipewire, 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.
Dylan Aïssi  (supplier of updated pipewire package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 17 Feb 2023 16:10:28 +0100
Source: pipewire
Architecture: source
Version: 0.3.65-3
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Dylan Aïssi 
Closes: 1031396
Changes:
 pipewire (0.3.65-3) unstable; urgency=medium
 .
   * pipewire-audio: add pulseaudio-module-bluetooth in Conflicts+Replaces
   to help apt make a choice (Closes: #1031396)
Checksums-Sha1:
 1a37d2f3ef6a8ac26e5c59887051baeb6d04de11 4431 pipewire_0.3.65-3.dsc
 fd7fa28d69a7583c4e1008befbc5c3d4949154ad 24552 pipewire_0.3.65-3.debian.tar.xz
 6ea582692e60f0d88e77903706ec6fee8f9ddf72 25403 
pipewire_0.3.65-3_amd64.buildinfo
Checksums-Sha256:
 6e78ee7d907aabd1a6eefaeec253247fdf9c0df0c2fefb716b1f6da42b2e4b3e 4431 
pipewire_0.3.65-3.dsc
 f5df7803387957064a605d8cc1212bdc8740e3be045b348fd1011cd09e75d20e 24552 
pipewire_0.3.65-3.debian.tar.xz
 96f673caa44ce3685c2cc3fc931f38fba70ba9b97be9184d1cbcb77e294f1867 25403 
pipewire_0.3.65-3_amd64.buildinfo
Files:
 5a31909216ea9bfb2c62e6bfe66cb94a 4431 libs optional pipewire_0.3.65-3.dsc
 b0304ab73d26f5810c96c73e011b1fa1 24552 libs optional 
pipewire_0.3.65-3.debian.tar.xz
 2b52bda59e656f7846b3fbaee35d05f7 25403 libs optional 
pipewire_0.3.65-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAmPvmj0ACgkQYS7xYT4F
D1TyhA//a/YPnugoA+3dK9ehnlq4Fu8kpv15gT3qli9MN2IwQnih3KlUOzUUW9+K
//1bjcmo7HyXXnQ4NwrMDAXXeN3QWQsVq4kmSSPToDH9u2wpabcOC3Kzy+TOqSDR
i9afD8heXB5glUAib1T0XK7F/g/pZENOig0HmSPA2hOJdcFkMf5roSJD+kuNV524
9y4q4p1qyne1aVU1+GBww967DyOF/n+rgOou9i9wxRGDKlk5bNVAqR+kKjBJN042
pCMIB7TEx7ZK3vmyT3Td3/o/0l3+ldk+qMUO8oQls8ml6tkRrNcFdxs+dr0p+YA5
B+++F9iWuuHDJ1DXd/qb8Fp9WVX6skQuPIXF5goNNaGosFkkiHIfudA3lQkilswC
2ki+8sUljiP9ojZXvLL6a56plAjaaXZ4/SwF

Processed (with 1 error): merging 1031509 1031513

[Debian Bug Tracking System]

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

> merge 1031509 1031513
Bug #1031509 [clamav] clamav: 2 RCE bugs in ClamAV 0.103 (+ 1.0.0), 
CVE-2023-20032/CVE-2023-20052
Unable to merge bugs because:
severity of #1031513 is 'grave' not 'important'
Failed to merge 1031509: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1031509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031509
1031513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031513
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

[Russ Allbery]

Adrian Bunk  writes:

> 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.

That's a very good point and I'm embarrassed it wasn't immediately obvious
to me.  Sorry about the noise.

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

Bug#1030174: marked as done (iminuit FTBFS with scipy 1.10)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2023 16:57:47 +
with message-id 
and subject line Bug#1030174: fixed in iminuit 2.11.2-4
has caused the Debian Bug report #1030174,
regarding iminuit FTBFS with scipy 1.10
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.)


-- 
1030174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: iminuit
Version: 2.11.2-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=iminuit&arch=amd64&ver=2.11.2-3%2Bb1&stamp=1675110798&raw=0

=== short test summary info 
SKIPPED [1] tests/test_tabulate.py:4: could not import 'tabulate': No module 
named 'tabulate'
SKIPPED [1] tests/test_core.py:124: could not import 'numba': No module named 
'numba'
SKIPPED [1] tests/test_minuit.py:1348: could not import 'numba': No module 
named 'numba'
SKIPPED [1] tests/test_util.py:335: could not import 'numba': No module named 
'numba'
SKIPPED [1] tests/test_util.py:361: could not import 'numba': No module named 
'numba'
FAILED tests/test_scipy.py::test_scipy_method[TNC-False-False] - DeprecationW...
FAILED tests/test_scipy.py::test_scipy_method[TNC-False-True] - DeprecationWa...
FAILED tests/test_scipy.py::test_scipy_method[TNC-True-False] - DeprecationWa...
FAILED tests/test_scipy.py::test_scipy_method[TNC-True-True] - DeprecationWar...
FAILED tests/test_scipy.py::test_scipy_constraints_2[True] - ValueError: outp...
5 failed, 427 passed, 5 skipped in 8.22s
E: pybuild pybuild:388: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.11_iminuit/build; python3.11 -m pytest 
tests
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 
returned exit code 13
make: *** [debian/rules:16: binary-arch] Error 25

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: iminuit
Source-Version: 2.11.2-4
Done: Ole Streicher 

We believe that the bug you reported is fixed in the latest version of
iminuit, 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.
Ole Streicher  (supplier of updated iminuit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 17 Feb 2023 17:02:03 +0100
Source: iminuit
Architecture: source
Version: 2.11.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ole Streicher 
Closes: 1030174
Changes:
 iminuit (2.11.2-4) unstable; urgency=medium
 .
   * Team upload
 .
   [ Andreas Tille ]
   * Build-Depends: python3-tabulate
   * Add salsa-ci.yml
   * Update standards version to 4.6.2, no changes needed.
   * No need for debhelper if debhelper-compat is specified
 .
   [ Ole Streicher ]
   * Fix for newer scipy 1.10 (Closes: #1030174)
   * Add autopkgtests
   * Update changelog for 2.11.2-3 release
   * Mark test_matrix as xfail
Checksums-Sha1:
 f1a9e081452f411721b47b77a4d9b008b23062a8 2193 iminuit_2.11.2-4.dsc
 db64689c4b332904091f116af89ba6a9993ac5d6 5648 iminuit_2.11.2-4.debian.tar.xz
Checksums-Sha256:
 c9500e784e707d711780513b233c3bcbbf9bbfab9a54e2d670fe4b3b40f93429 2193 
iminuit_2.11.2-4.dsc
 8dc7c11c6c51f61c8d79b88d1da760f8cc8a310f1d64a0004d51e3d8fbbd48dc 5648 
iminuit_2.11.2-4.debian.tar.xz
Files:
 71bce5aee7728fcd03372113e5ae24f5 2193 science optional iminuit_2.11.2-4.dsc
 ef96a53bc6ac73d79700f09b848b5730 5648 science optional 
iminuit_2.11.2-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmPvpvUACgkQcRWv0HcQ
3Pflmw/+L46qMFxhFhwUXeU9+2zgErUea8GUKcfqEgGSpWL4V/RpiGBjY5b8wypC
1hKepN7fZ2TUbiSUiUcukCgpcf9jnsYMshyvNyOvbxZ/PpD56FOtZtph0FzGAyvc
JKTVl0ph24kyS3DCjj/QPbQKfbSDIOoX2y2f3F7XGMs70BANlSL8X7TgZo4VMj0Q
Y3xvFZeZWMZK+W3hKSj72Q66CtneUEHxyiRagnoSW4PID0hupOdpEcHkZmSPCLR2
wpN4BYnAg1XMHSPpAG03zqCEnAhawVeBZDFuCcIpTFro7QKXpl0RutGc5Hkimf1q
Y2+I7zStMJjkG9Q2cgV+qE+mdKEN0MDA0Nf53xmnDdBacWpEuIXyJJwJlfvcJ27E
Ja1Aq8IPtGjWQMTLXzfqF0YcEIBFGYT0VmA3poKIoLxna4PXdLRXo/iVHauumQXw
OEbZqFok

Processed: tagging 1022015

[Debian Bug Tracking System]

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

> tags 1022015 + patch
Bug #1022015 [src:elasticsearch-curator] elasticsearch-curator: Uses deprecated 
yaml.load
Bug #1026566 [src:elasticsearch-curator] elasticsearch-curator: FTBFS: 
TypeError: load() missing 1 required positional argument: 'Loader'
Added tag(s) patch.
Added tag(s) patch.
> thanks
Stopping processing here.

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

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

[Peter Wienemann]

Control: reassign -1 src:fuse3
Control: found -1 3.13.1-1
Control: forwarded -1 https://github.com/libfuse/libfuse/issues/729
Control: tags -1 + fixed-upstream
Control: affects -1 src:charliecloud

Dear Lucas,

thanks for reporting this problem. It seems that the root cause of this 
FTBFS issue is a problem which was introduced by fuse3 3.13.1. A fix has 
been provided by upstream:


https://github.com/libfuse/libfuse/commit/d7560cc9916b086bfe5d86459cc9f04033edd904

Best regards,

Peter

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

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:fuse3
Bug #1031455 [src:charliecloud] charliecloud: FTBFS: config.h:38: error: 
"PACKAGE_VERSION" redefined [-Werror]
Bug reassigned from package 'src:charliecloud' to 'src:fuse3'.
No longer marked as found in versions charliecloud/0.31-1.
Ignoring request to alter fixed versions of bug #1031455 to the same values 
previously set
> found -1 3.13.1-1
Bug #1031455 [src:fuse3] charliecloud: FTBFS: config.h:38: error: 
"PACKAGE_VERSION" redefined [-Werror]
Marked as found in versions fuse3/3.13.1-1.
> forwarded -1 https://github.com/libfuse/libfuse/issues/729
Bug #1031455 [src:fuse3] charliecloud: FTBFS: config.h:38: error: 
"PACKAGE_VERSION" redefined [-Werror]
Set Bug forwarded-to-address to 'https://github.com/libfuse/libfuse/issues/729'.
> tags -1 + fixed-upstream
Bug #1031455 [src:fuse3] charliecloud: FTBFS: config.h:38: error: 
"PACKAGE_VERSION" redefined [-Werror]
Added tag(s) fixed-upstream.
> affects -1 src:charliecloud
Bug #1031455 [src:fuse3] charliecloud: FTBFS: config.h:38: error: 
"PACKAGE_VERSION" redefined [-Werror]
Added indication that 1031455 affects src:charliecloud

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

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

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2023 17:19:48 +
with message-id 
and subject line Bug#1031433: fixed in diffoscope 236
has caused the Debian Bug report #1031433,
regarding diffoscope: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p 3.11 returned exit code 13
to be marked as done.

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

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


-- 
1031433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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

Bug#1030464: aiomysql: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 'unknown'

[s3v]

Dear Maintainer,

After adding python3-setuptools-scm to build depends, I was able to
build your package in a sid chroot environment.
Please note that the build creates a "aiomysql/_scm_version.py" file
which prevents the next build:


...
dpkg-source: info: using options from aiomysql-0.1.1/debian/source/options: 
--extend-diff-ignore=^[^/]*[.]egg-info/
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building aiomysql using existing ./aiomysql_0.1.1.orig.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: warning: ignoring deletion of file docs/make.bat, use 
--include-removal to override
dpkg-source: info: local changes detected, the modified files are:
 aiomysql-0.1.1/aiomysql/_scm_version.py
dpkg-source: info: Hint: make sure the version in debian/changelog matches the 
unpacked source tree
dpkg-source: info: you can integrate the local changes with dpkg-source --commit
dpkg-source: error: aborting due to unexpected upstream changes, see 
/tmp/aiomysql_0.1.1-3.diff.1zsVoB
dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2


To avoid this, I think the removal needs to be added to the other cleanups in 
debian/rules.

Kind Regards

Processed: tagging 982123

[Debian Bug Tracking System]

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

> tags 982123 + buster
Bug #982123 [src:librsvg] librsvg: FTBFS on ppc64el in buster
Added tag(s) buster.
> thanks
Stopping processing here.

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

Bug#1031379: kaffeine: does not work

[Marco Mattiolo]

Hi,

I am not the package maintainer, but this bug report is almost useless.

What's the issue? Is kaffeine not starting? Is it crashing? Or is just 
not showing what you expect?


Which kind of DVB device are you using? Have you checked the device to 
work with other apps?


Before flagging this bug report as "grave" (i.e. unusable app), have you 
checked if kaffeine is able to play local media? Imo, this is more 
"important" severity...


Kind regards

Marco

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

[James Addison]

Package: python3-zstandard
Followup-For: Bug #1031443
Control: forcemerge -1 1031293 1031449

Processed: Re: 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

[Debian Bug Tracking System]

Processing control commands:

> forcemerge -1 1031293 1031449
Bug #1031443 [python3-zstandard] 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 zstd 
headers, 10502 hardcoded in the cext)
Bug #1031449 [python3-zstandard] 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 headers, 10502 
hardcoded in the cext)
Removed indication that 1031449 affects src:libzstd, src:rpmlint, 
src:python-zstandard, and src:python-scrapy
Added indication that 1031449 affects 
src:rpmlint,src:python-scrapy,src:python-zstandard,src:libzstd
Bug #1031293 [python3-zstandard] python3-zstandard 0.19.0-3 supports only 
libzstd 1.5.2
Removed indication that 1031293 affects src:python-scrapy, src:libzstd, 
src:rpmlint, and src:python-zstandard
Added indication that 1031293 affects 
src:rpmlint,src:python-scrapy,src:python-zstandard,src:libzstd
Added tag(s) sid, ftbfs, and bookworm.
Merged 1031293 1031443 1031449

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

Processed: RC Bug #1031460: forward to upstream fix

[Debian Bug Tracking System]

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

> forwarded 1031460 
> https://github.com/Rockhopper-Technologies/enlighten/commit/1ede6ff4
Bug #1031460 [src:enlighten] 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] s/B'
Set Bug forwarded-to-address to 
'https://github.com/Rockhopper-Technologies/enlighten/commit/1ede6ff4'.
> thanks
Stopping processing here.

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

Bug#1028840: marked as done (weather-util: FTBFS: ValueError: invalid mode: 'rUb')

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2023 18:08:08 +
with message-id 
and subject line Bug#1028840: fixed in weather-util 2.4.4-1
has caused the Debian Bug report #1028840,
regarding weather-util: FTBFS: ValueError: invalid mode: 'rUb'
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.)


-- 
1028840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: weather-util
Version: 2.4.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 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
> python3 ./weather --build-sets
> Reading 2019_Gaz_counties_national.zip:2019_Gaz_counties_national.txt...done 
> (3220 lines).
> Reading 2019_Gaz_cousubs_national.zip:2019_Gaz_cousubs_national.txt...done 
> (36622 lines).
> Reading 2019_Gaz_place_national.zip:2019_Gaz_place_national.txt...done (29574 
> lines).
> Reading slist...Traceback (most recent call last):
>   File "/<>/./weather", line 32, in 
> weather.correlate()
>   File "/<>/weather.py", line 1389, in correlate
> slist = codecs.open(slist_fn, "rU", "utf-8")
> 
>   File "", line 906, in open
> ValueError: invalid mode: 'rUb'
> make[1]: *** [debian/rules:10: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/01/13/weather-util_2.4.1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230113;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230113&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: weather-util
Source-Version: 2.4.4-1
Done: Jeremy Stanley 

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

Debian distribution maintenance software
pp.
Jeremy Stanley  (supplier of updated weather-util package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 17 Feb 2023 14:22:01 +
Source: weather-util
Binary: weather-util weather-util-data
Architecture: source all
Version: 2.4.4-1
Distribution: unstable
Urgency: low
Maintainer: Jeremy Stanley 
Changed-By: Jeremy Stanley 
Description:
 weather-util - command-line tool to obtain weather conditions and forecasts
 weather-util-data - optional correlation data for weather-util search feature
Closes: 1028840
Changes:
 weather-util (2.4.4-1) unstable; urgency=low
 .
   * New upstream release (closes: #1028840)
   * Refreshed upstream signing key with a current selfsig
   * Switched upstream URLs from HTTP to HTTPS
   * Updated standards version from 4.5.0 to 4.6.2
   * Updated debian/copyright dates and file globs
   * Removed VCS fields from debian/control since they incorrectly
 pointed at upstream source revision control and the packaging
 data is not yet kept in a VCS
Checksums-Sha1:
 4e22453fb64b5fb56fa54532f26e730e9cd25b1c 1777 weather-util_2.4.4-1.dsc
 86c9c420076165b0bf0efb5b0a837e7a9b33ba69 8770188 weather-util_2.4.4.orig.tar.xz
 e08b5322acd8f565c5ab1c315201330ef354aa31 963 weather-util_2.4.4.orig.tar.xz.asc
 607c3c8f4e033ddafab1be9d4f2b8931788d3da0 13004 
weather-util_2.4.4-1.debian.tar.xz
 da532eb998c566015ac1258cd2dd13c56f9c 3478712 
weather-util-data_2.4.4-1_all.deb
 94a327

Bug#1031522: yt-dlp: Unable to extract uploader id

[Peter Wienemann]

Package: yt-dlp
Version: 2023.01.06-1
Severity: grave
Tags: fixed-upstream
Justification: renders package unusable

Dear Maintainer,

it seems that version 2023.01.06-1 of yt-dlp suffers from the issue
described in:

https://github.com/yt-dlp/yt-dlp/issues/6247

Upstream has provided a fix for this issue:

https://github.com/yt-dlp/yt-dlp/commit/149eb0bbf34fa8fdf8d1e2aa28e17479d099e26b

Best regards,

Peter

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

Kernel: Linux 6.1.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 yt-dlp depends on:
ii  python33.11.1-3
ii  python3-brotli 1.0.9-2+b6
ii  python3-certifi2022.9.24-1
ii  python3-mutagen1.46.0-1
ii  python3-pkg-resources  66.1.1-1
ii  python3-pycryptodome   3.11.0+dfsg1-4
ii  python3-websockets 10.4-1

Versions of packages yt-dlp recommends:
ii  ca-certificates  20211016
ii  curl 7.87.0-2
ii  ffmpeg   7:5.1.2-2
ii  python3-pyxattr  0.8.0-1+b1
ii  rtmpdump 2.4+20151223.gitfa8646d.1-2+b2
ii  wget 1.21.3-1+b2

Versions of packages yt-dlp suggests:
pn  libfribidi-bin | bidiv  
ii  mpv 0.35.1-1
pn  phantomjs   

-- no debconf information

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 Fri, Feb 17, 2023 at 08:51:33AM -0800, Russ Allbery wrote:
> Adrian Bunk  writes:
> 
> > 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.
> 
> That's a very good point and I'm embarrassed it wasn't immediately obvious
> to me.  Sorry about the noise.

One other thing I woud add here is (a) this whole discussion of
mke2fs.conf only helps for ext4, and the general problem is something
that extends to all file system.  The immediate question may be ext4
specific, but as I mentioned earlier, XFS is enabling the "bigtime"
feature for the first time in Bookworm.  So enabling what may be
convenient, but ultimately an anti-pattern is something that hopefully
in the long-term Debian should be striving towards.  Yes, it's
annoying and and extra work.  So is using build chroots if we are
building packages for a older Distro versions.  But it's the right
thing to do.

Secondly, (b) there may be a misapprehension that it is possible to
get an identical file system just by controlling the contents of
mke2fs and/or specifying the file system features on the command line.
While this is mostly true, it is not the whole story.  For example,
the size and location of the journal is determined hueristically, and
in the past, this has changed as we have discovered that (for example)
making the default journal size larger would result in better
performance.  The location of the journal has also changed from the
beginning of storage device (low-numbered LBA's) to the middle of the
device.

So just as a binary compiled using the default gcc on Buster might be
different from a binary build using Sid, even if you you force the use
of older glibc shared libraries at link time or use -static to
statically link with the glibc installed in your random desktop
environment, the results from using mke2fs on Debian N may be
different from using mke2fs on Debian M, even if you control for thea
file system features.  (And other things which _are_ controllable on
mke2fs.conf, but which go beyond mke file system features.  For
example, in Bookworm starting with e2fsprogs 1.46.4, the default inode
size is forced to always be 256 bytes, even for small file systems.
This was not true in Buster and older Debian distributions.)

So if you want a bootable image that is identical to what would be
created by using the Buster or Bullseye debian-interaller, you
*really* want to use the mkfs that was supplied by Buster or Bullseye,
and that means running the mkfs from a chroot.

Best regards,

- Ted

Processed: Re: [Pkg-clamav-devel] Processed (with 1 error): merging 1031509 1031513

[Debian Bug Tracking System]

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

> forcemerge 1031509 1031513
Bug #1031509 [clamav] clamav: 2 RCE bugs in ClamAV 0.103 (+ 1.0.0), 
CVE-2023-20032/CVE-2023-20052
Bug #1031513 [clamav] clamav: new upstream security release, CVE-2023-20032
Severity set to 'important' from 'grave'
Marked as found in versions clamav/0.103.7+dfsg-0+deb11u1.
Merged 1031509 1031513
> severity 1031509 serious
Bug #1031509 [clamav] clamav: 2 RCE bugs in ClamAV 0.103 (+ 1.0.0), 
CVE-2023-20032/CVE-2023-20052
Bug #1031513 [clamav] clamav: new upstream security release, CVE-2023-20032
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> found 1031509 1.0.0+dfsg-6
Bug #1031509 [clamav] clamav: 2 RCE bugs in ClamAV 0.103 (+ 1.0.0), 
CVE-2023-20032/CVE-2023-20052
Bug #1031513 [clamav] clamav: new upstream security release, CVE-2023-20032
Marked as found in versions clamav/1.0.0+dfsg-6.
Marked as found in versions clamav/1.0.0+dfsg-6.
>
End of message, stopping processing here.

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

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

[Timo Röhling]

Control: tags -1 + moreinfo

Hi Lucas,

this seems to be bug #1030493 again.

On Fri, 17 Feb 2023 07:50:37 +0100 Lucas Nussbaum  wrote:

> E   -   '')]
> E   ?  ^
> E   
> E   +   ''),

> E   ?  ^
> E   
> E   +  (_INOTIFY_EVENT(wd=1, mask=1073742336, cookie=0, len=16),

> E   +   ['IN_DELETE', 'IN_ISDIR'],
> E   +   '/tmp/tmpmmbhfdhl',
> E   +   'new_folder')]


Apparently, the returned order of INOTIFY_EVENTS is different with
your builds than it is on the buildds, my machine, and Bastian's
machine. Neither Bastian nor I could reproduce the bug. Initially, I
assumed this is some sort of flakiness and added test retries, but
it looks like your build system always returns events in a
different order (or at least often enough so two retries are not
sufficient).

I suspect that you are using a different filesystem, which processes
changes differently and thus makes the inotify API return events in
a different order, but I don't know for sure.

Can you help us track down the underlying cause, so we can reproduce
the failure and then think of an appropriate way to work around it?


Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #1031435 [src:python-inotify] python-inotify: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) moreinfo.

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

Processed: cloud-initramfs-growroot: Initramfs hook does not include `flock` command

[Debian Bug Tracking System]

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

> severity 1014662 serious
Bug #1014662 [cloud-initramfs-growroot] cloud-initramfs-growroot: Initramfs 
hook does not include `flock` command
Severity set to 'serious' from 'important'
> tags 1014662 + patch
Bug #1014662 [cloud-initramfs-growroot] cloud-initramfs-growroot: Initramfs 
hook does not include `flock` command
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1031455: marked as done (charliecloud: FTBFS: config.h:38: error: "PACKAGE_VERSION" redefined [-Werror])

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2023 19:19:56 +
with message-id 
and subject line Bug#1031455: fixed in fuse3 3.14.0-1
has caused the Debian Bug report #1031455,
regarding charliecloud: FTBFS: config.h:38: error: "PACKAGE_VERSION" redefined 
[-Werror]
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.)


-- 
1031455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230216&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: fuse3
Source-Version: 3.14.0-1
Done: Laszlo Boszormenyi (GCS) 

We believe that the bug you reported is fixed in the latest version of
fuse3, 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 fuse3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 17 Feb 2023 19:50:40 +0100
Source: fuse3
Architecture: source
Version: 3.14.0-1
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 1031455
Changes:
 fuse3 (3.14.0-1) unstable; urgency=medium
 .
   * New upstream release:
 - fix header installation issue (closes: #1031455).
Checksums-Sha1:
 352a5509a4a8c82b901f93cf5d4a54172b9d3230 2390 fuse3_3.14.0-1.dsc
 3820905cd399fe9350285e76e72ceace656a761f 4351852 fuse3_3.14.0.orig.tar.xz
 8addaabc30aa4b6a86f580248ae31e9788d8918c 1012 fuse3_3.14.0.orig.tar.xz.asc
 0f44ab7730b5acb2c6dbe917bd4611222e8b 12812 fuse3_3.14.0-1.debian.tar.xz
Checksums-Sha256:
 211ffc02a56c7f3163f76a57917fe37da72924c5d9591d2b983db5fc277fe6cc 2390 
fuse3_3.14.0-1.dsc
 96115b2a8ff34bd1e0c7b00c5dfd8297571d7e165042b94498c9a26356a9a70a 4351852 
fuse3_3.14.0.orig.tar.xz
 246ae20731da98c5f5a5cf6cdf8d10aa54ea986b4e71fe24805154b186ad30d0 1012 
fuse3_3.1

Bug#1031469: marked as done (botch: FTBFS: make[2]: *** [Makefile:339: test-python] Error 1)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2023 19:19:34 +
with message-id 
and subject line Bug#1031469: fixed in botch 0.24-2
has caused the Debian Bug report #1031469,
regarding botch: FTBFS: make[2]: *** [Makefile:339: test-python] Error 1
to be marked as done.

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

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


-- 
1031469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230216&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: botch
Source-Version: 0.24-2
Done: Johannes Schauer Marin Rodrigues 

We believe that the bug you reported is fixed in the latest version of
botch, 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.
Johannes Schauer Marin Rodrigues  (supplier of updated botch 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 17 Feb 2023 15:49:11 +0100
Source: botch
Architecture: source
Version: 0.24-2
Distribution: unstable
Urgency: medium
Maintainer: Johannes Schauer Marin Rodrigues 
Changed-By: Johannes Schauer Marin Rodrigues 
Closes: 1031469
Changes:
 botch (0.24-2) unstable; urgency=medium
 .
   * add patch to make tests work with black 23.1.0 (closes: #1031469)
Checksums-Sha1:
 4adc3a8677ac84803f47d2fcdeb8a5fe943301de 3014 botch_0.24-2.dsc
 46335dbb0705f15c1cb6b0f6a3e3a4dafe35f046 19472 botch_0.24-2.debian.tar.xz
Checksums-Sha256:
 88eee19ba49f719c8501e28e9f8934165785be6b0fbc41f110a5a14949017a9e 3014 
botch_0.24-2.dsc
 cedfe7aa81b5f6ca2755ddfa443a6a1c80949a97c20de02d37e70e927d92cee0 19472 
botch_0.24-2.debian.tar.xz
Files:
 faa3d34bd2aa173bdb8b8ab8f52115d4 3014 utils optional botch_0.24-2.dsc
 1168cca210ce8c643cb4e02182281093 19472 utils optional 
botch_0.24-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmPv0GIACgkQ8sulx4+9
g+F8IA//Yp0UAi2jjTXL4lZ8kfOSUAUS/ywwWcLQPxlzckVqsH3Hgy/ieamhoC6Q
9pIFVUeVrgcqf8CW55cpO9t1TSERaJWcorUjKDnZ6ccPA+PpxuNHHBYpWJxkpRsH
Gnoxn1KQmMinyQ0LUFiaWhcjriMcd1436/XrlyO0CP3QrTmpJTm3gemPeJ3mxcpl
FqspdvzjQ1tt6ZiOU0gR0S5b+aiMWJLjFOe5+Yp86yxxUWzQ6mEVYqcuSqlxkPTZ
mcF4C4AVAP982ngbMb4DOM4JZC3JXfjFuKPCBUpuaDQT6vDJ3O9iXyZqJ9I9s9Aq
AnV1EkVM17r66DkgFyTOHDYm2iTP/02DvIRZW/QhNYd4B939xIfjKWRxOigNYrfi
KZV02PDGVu/KiPU

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 Fri, Feb 17, 2023 at 02:08:28PM -0500, Theodore Ts'o wrote:
> So enabling what may be
> convenient, but ultimately an anti-pattern is something that hopefully
> in the long-term Debian should be striving towards.

Sigh, I managed to invert the sense of what I was trying to say.  This
should have read:

So enabling what may be convenient, but ultimately an anti-pattern is
something that hopefully in the long-term Debian should be trying to
*avoid*.

- 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

[Sam Hartman]

> "Theodore" == Theodore Ts'o  writes:


Theodore> So enabling what may be convenient, but ultimately an
Theodore> anti-pattern is something that hopefully in the long-term
Theodore> Debian should be trying to *avoid*.

That's certainly true.
I am not entirely convinced that using current rather than guest tools
for image building is an anti-pattern.
You've been working on filesystems for a long time; I've been working on
various image building projects since my first watchmaker project at
MIT.

I can understand the arguments about why it's an anti-patern, but I can
also understand why it may be the correct answer.
I'd love to have that discussion with you some time, although preferably
not on a bug like this, and I'm not entirely sure my thoughts are
organized enough for a large mailing list discussion.

I think that discussion is clearly well beyond the scope of what the RT
needs to make an immediate decision here.


signature.asc
Description: PGP signature

Bug#1031509: marked as done (clamav: 2 RCE bugs in ClamAV 0.103 (+ 1.0.0), CVE-2023-20032/CVE-2023-20052)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2023 19:49:38 +
with message-id 
and subject line Bug#1031509: fixed in clamav 1.0.1+dfsg-1
has caused the Debian Bug report #1031509,
regarding clamav: 2 RCE bugs in ClamAV 0.103 (+ 1.0.0), 
CVE-2023-20032/CVE-2023-20052
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.)


-- 
1031509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clamav
Version: 0.103.7+dfsg-0+deb11u1
Severity: important

Dear Maintainer,

ClamAV/Cisco have released a security advisory concerning 2 potential-RCE
bugs in ClamAV:
https://blog.clamav.net/2023/02/clamav-01038-01052-and-101-patch.html

According to the the security tracker, all versions currently in Debian
are vulnerable:
https://security-tracker.debian.org/tracker/CVE-2023-20032
https://security-tracker.debian.org/tracker/CVE-2023-20052

Please consider an update. Currently, ClamAV is not suitable for use in a
(quite common) email-scanning setup like with Amavis, but can still be
used (with appropriate care) directly. Thus I think Severity: important fits.

Kind regards,
Robert

-- Package-specific info:
--- configuration ---
# Automatically created by the clamav-freshclam postinst
# Comments will get lost when you reconfigure the clamav-freshclam package

DatabaseOwner clamav
UpdateLogFile /var/log/clamav/freshclam.log
LogVerbose false
LogSyslog false
LogFacility LOG_LOCAL6
LogFileMaxSize 0
LogRotate true
LogTime true
Foreground false
Debug false
MaxAttempts 5
DatabaseDirectory /var/lib/clamav
DNSDatabaseInfo current.cvd.clamav.net
ConnectTimeout 30
ReceiveTimeout 0
TestDatabases yes
ScriptedUpdates yes
CompressLocalDatabase no
Bytecode true
NotifyClamd /etc/clamav/clamd.conf
# Check for new database 24 times a day
Checks 24
DatabaseMirror db.local.clamav.net
DatabaseMirror database.clamav.net

--- data dir ---
total 226104
-rw-r--r-- 1 clamav clamav293670 Feb 17 14:46 bytecode.cvd
-rw-r--r-- 1 clamav clamav  60744631 Feb 17 14:44 daily.cvd
-rw-r--r-- 1 clamav clamav69 Feb 17 14:43 freshclam.dat
-rw-r--r-- 1 clamav clamav 170479789 Feb 17 14:46 main.cvd

-- System Information:
Debian Release: 11.6
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-0.deb11.4-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages clamav depends on:
ii  clamav-freshclam [clamav-data]  0.103.7+dfsg-0+deb11u1
ii  libc6   2.31-13+deb11u5
ii  libclamav9  0.103.7+dfsg-0+deb11u1
ii  libcurl47.74.0-1.3+deb11u3
ii  libjson-c5  0.15-2
ii  libssl1.1   1.1.1n-0+deb11u3
ii  zlib1g  1:1.2.11.dfsg-2+deb11u2

Versions of packages clamav recommends:
ii  clamav-base  0.103.7+dfsg-0+deb11u1

Versions of packages clamav suggests:
pn  clamav-docs   
pn  libclamunrar  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: clamav
Source-Version: 1.0.1+dfsg-1
Done: Sebastian Andrzej Siewior 

We believe that the bug you reported is fixed in the latest version of
clamav, 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.
Sebastian Andrzej Siewior  (supplier of updated clamav 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 17 Feb 2023 20:29:05 +0100
Source: clamav
Architecture: source
Version: 1.0.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: ClamAV Team 
Changed-By: Sebastian Andrzej Siewior 
Closes: 1031509
Changes:
 clamav (1.0.1+dfsg-1) unstable; urgency=medium
 .
   * Import 1.0.1 (Closes: #1031509)
 - CVE-2023-

Bug#1031513: marked as done (clamav: new upstream security release, CVE-2023-20032)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2023 19:49:38 +
with message-id 
and subject line Bug#1031509: fixed in clamav 1.0.1+dfsg-1
has caused the Debian Bug report #1031509,
regarding clamav: new upstream security release, CVE-2023-20032
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.)


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

Hi,

As you'll likely know there is
https://security-tracker.debian.org/tracker/CVE-2023-20032 and
https://blog.clamav.net/2023/02/clamav-01038-01052-and-101-patch.html

"CVE-2023-20032: Fixed a possible remote code execution vulnerability in the
HFS+ file parser. The issue affects versions 1.0.0 and earlier, 0.105.1 and
earlier, and 0.103.7 and earlier. Thank you to Simon Scannell for reporting
this issue."

Upstream released fixed tarballs for all their supported branches.  I've
managed to build 0.103.8+dfsg-0+deb10u1~uvt0 for Debian 10/buster from that,
it's available from https://non-gnu.uvt.nl/debian/buster/clamav/ (including
sources).

We are now running this build on the Tilburg University mail infrastructure,
it might work for others too.

Anybody working on a proper Debian supplied fix: feel free to contact me (via
IRC, e.g.)

HTH, Bye,

Joost

-- 
Joost van Baal-Ilić   http://abramowitz.uvt.nl/
 Tilburg University
mailto:joostvb.uvt.nl   The Netherlands


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: clamav
Source-Version: 1.0.1+dfsg-1
Done: Sebastian Andrzej Siewior 

We believe that the bug you reported is fixed in the latest version of
clamav, 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.
Sebastian Andrzej Siewior  (supplier of updated clamav 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 17 Feb 2023 20:29:05 +0100
Source: clamav
Architecture: source
Version: 1.0.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: ClamAV Team 
Changed-By: Sebastian Andrzej Siewior 
Closes: 1031509
Changes:
 clamav (1.0.1+dfsg-1) unstable; urgency=medium
 .
   * Import 1.0.1 (Closes: #1031509)
 - CVE-2023-20032 (Possible RCE in the HFS+ file parser).
 - CVE-2023-20052 (Possible information leak in the DMG file parser).
Checksums-Sha1:
 fec345e5820bc6ea8c8b15a41cf1234e2320ff0e 2829 clamav_1.0.1+dfsg-1.dsc
 fe18edded75204a2b4b4ec0c73c22da14e5235c2 14132600 clamav_1.0.1+dfsg.orig.tar.xz
 2271488d1efe0e9dfb402630c520c36a46af34a8 222848 
clamav_1.0.1+dfsg-1.debian.tar.xz
Checksums-Sha256:
 6263eb81b8cdabc605bac140742ba31907a4025a3a4d65ea82e4992aba5486fc 2829 
clamav_1.0.1+dfsg-1.dsc
 0f19b43ec26395bb921a03a77a17138b92fde4ddbcee33804da7075e5d709c90 14132600 
clamav_1.0.1+dfsg.orig.tar.xz
 4aa0a1529b35cfd795905815ac959b9d717054e35968dfcf1a88ed0cef2d787d 222848 
clamav_1.0.1+dfsg-1.debian.tar.xz
Files:
 b3f25cf5947cc8d612a5bf677bfae921 2829 utils optional clamav_1.0.1+dfsg-1.dsc
 5dae77cb4de79e4ead9275f75c90bd20 14132600 utils optional 
clamav_1.0.1+dfsg.orig.tar.xz
 5d68b02434a4dcb01ed33089f5cdecf1 222848 utils optional 
clamav_1.0.1+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEV4kucFIzBRM39v3RBWQfF1cS+lsFAmPv1d0ACgkQBWQfF1cS
+lv1OQv+PZ78Ke84bICNkMqTqVyN1RAxtF8v6u58hbDwnqjhp1cD2PuHuX67nSMx
WTZgTH4IqzMGfPnPQR7HPXiSFmd0GQt/2LqNy/WKr4C3yeHG0I4I2nHOBxyQRbG1
YZ7WAz8RXbU9gJWcEFZTQZBwcYy+D4ts1Sm67XbIz8WytIaXbl4lM/QCEMuX7Mqn
qyL+utgOW8V575QJo7BwYHIgyvOAWkHqprCGTgX8/PttxzdDxm+jwdH0E/qROCQM
2MpWuD7V87rzyQJZ3amYVXpuCRfaECoWiNb8LEZznMlx10+HzYtJjuJeC1N84JSm
+YyspwtrqiBBUWYVsx/RSp8emfyq7qy8RU1fmR2nEqVtQqwsXstWdZvpO69fBRmV
A+PX9Lp2i8WsX4378NgcLrtbAmxvMHjFXRZRJo76IaXKNZGb/DBgwgE9es0gpPbG
j5D1hW8KwT7WJ55SmgE7yPw6s+i4KLvgdSxviSP/lItdbfgNDpqHGwpVXCuVNFoz
VDYQwsDt
=0Fl8
-END PGP SIGNATURE End Message ---

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

[Paul Gevers]

Hi,

On 16-02-2023 23:34, Andreas Beckmann wrote:

@elbrus: Why does britney try to migrate clinfo together with pocl?


Honestly, I don't know. The logic that does that *is* rather greedy as 
often it helps (but not always).


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.


I have scheduled the job with only clinfo from unstable and the test 
passed. So I think clinfo can just migrate after the information becomes 
available.


Thanks.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: tagging 1031509

[Debian Bug Tracking System]

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

> tags 1031509 + security upstream fixed-upstream
Bug #1031509 {Done: Sebastian Andrzej Siewior } 
[clamav] clamav: 2 RCE bugs in ClamAV 0.103 (+ 1.0.0), 
CVE-2023-20032/CVE-2023-20052
Bug #1031513 {Done: Sebastian Andrzej Siewior } 
[clamav] clamav: new upstream security release, CVE-2023-20032
Added tag(s) fixed-upstream, upstream, and security.
Added tag(s) fixed-upstream, upstream, and security.
> thanks
Stopping processing here.

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

Bug#1031315: libjpeg9: libjpeg.so.9* missing

[Bill Allombert]

On Wed, Feb 15, 2023 at 05:45:26AM +0800, Roy Clark (kralcyor) wrote:
> Package: libjpeg9
> Version: 1:9d-1.1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> /usr/lib/*/{libjpeg.so.9,libjpeg.so.9.4.0} are missing in the package, making 
> it completely unusable:
> $ dpkg -L libjpeg9 
> /.
> /usr
> /usr/share
> /usr/share/doc
> /usr/share/doc/libjpeg9
> /usr/share/doc/libjpeg9/README.gz
> /usr/share/doc/libjpeg9/changelog.Debian.gz
> /usr/share/doc/libjpeg9/changelog.gz
> /usr/share/doc/libjpeg9/copyright
> 
> This issue may related to changes in the build system. While libjpeg.so.9* 
> appear in the old version 1:9d-1, a rebuilt package of version 1:9d-1 on a 
> latest unstable Debian system also lacks libjpeg.so.9*.

Ah thanks. I should have checked that the NMU was correct.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#1031524: fuse3: setxattr is broken

[Graham Inggs]

Source: fuse3
Version: 3.13.0-1
Severity: serious
Forwarded: https://github.com/libfuse/libfuse/issues/730
Control: affects -1 src:ostree

Hi Maintainer

Since the upload of 3.13.0-1, the 'name' string passed to
fs->op.setxattr has the first 8 characters missing.

Steps to reproduce:

$ dget https://deb.debian.org/debian/pool/main/f/fuse3/fuse3_3.14.0-1.dsc
$ cd fuse3-3.14.0/
$ debuild -us -uc
$ cd obj-x86_64-linux-gnu/example/
$ mkdir mnt/
$ ./passthrough mnt/
$ touch mnt/tmp/anewfile-for-fuse
$ setfattr -n user.foo -v bar mnt/tmp/anewfile-for-fuse
setfattr: mnt/tmp/anewfile-for-fuse: Numerical result out of range

Now try setfattr again with 8 dummy characters in front of the name string:

$ setfattr -n 12345678user.foo -v bar mnt/tmp/anewfile-for-fuse
$ getfattr -d -m . mnt/tmp/anewfile-for-fuse
# file: mnt/tmp/anewfile-for-fuse
user.foo="bar"

$ umount mnt/
$ rmdir mnt/

Regards
Graham

Processed: fuse3: setxattr is broken

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:ostree
Bug #1031524 [src:fuse3] fuse3: setxattr is broken
Added indication that 1031524 affects src:ostree

-- 
1031524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031524
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 Fri, Feb 17, 2023 at 02:08:28PM -0500, Theodore Ts'o wrote:
>...
> So enabling what may be
> convenient, but ultimately an anti-pattern is something that hopefully
> in the long-term Debian should be striving towards.  Yes, it's
> annoying and and extra work.  So is using build chroots if we are
> building packages for a older Distro versions.  But it's the right
> thing to do.

Don't assume "host = target" would always be possible.

Your proposed solution only works for the trivial
"building Debian on Debian" case.

The same general problem applies in various "building non-Debian 
embedded Linux filesystem on Debian" situations where the target
chroot does not contain mkfs.ext4.

Or if it is present, it would be a chroot for the target architecture 
where you might have to run mkfs.ext4 under qemu.

All image building tools that support bookworm (including all image 
building tools we ship in bookworm) have to ensure that what they
produce works on the intended target. There is no general solution
*how* to do that that could be applied in all cases.

> Secondly, (b) there may be a misapprehension that it is possible to
> get an identical file system just by controlling the contents of
> mke2fs and/or specifying the file system features on the command line.
>...

It is clear that different versions of tools like mkfs.ext4 or gzip 
might produce different output.

If identical results matter, you can just define $distribution as
build environment and then expect that for example the host tools
from Debian bookworm will always create the same output when building
a Yocto distribution.

> Best regards,
> 
>   - Ted

cu
Adrian

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]

Hi,

On 17/02/23 at 20:17 +0100, Timo Röhling wrote:
> Control: tags -1 + moreinfo
> 
> Hi Lucas,
> 
> this seems to be bug #1030493 again.
> 
> On Fri, 17 Feb 2023 07:50:37 +0100 Lucas Nussbaum  wrote:
> > > E   -   '')]
> > > E   ?  ^
> > > E   > E   +   ''),
> > > E   ?  ^
> > > E   > E   +  (_INOTIFY_EVENT(wd=1, mask=1073742336,
> > cookie=0, len=16),
> > > E   +   ['IN_DELETE', 'IN_ISDIR'],
> > > E   +   '/tmp/tmpmmbhfdhl',
> > > E   +   'new_folder')]
> 
> Apparently, the returned order of INOTIFY_EVENTS is different with
> your builds than it is on the buildds, my machine, and Bastian's
> machine. Neither Bastian nor I could reproduce the bug. Initially, I
> assumed this is some sort of flakiness and added test retries, but
> it looks like your build system always returns events in a
> different order (or at least often enough so two retries are not
> sufficient).
> 
> I suspect that you are using a different filesystem, which processes
> changes differently and thus makes the inotify API return events in
> a different order, but I don't know for sure.

I'm using ext4, so this is unlikely.

> Can you help us track down the underlying cause, so we can reproduce
> the failure and then think of an appropriate way to work around it?

Sure. I took a look, and it seems that the different behaviour is caused
by me running an old stable kernel, rather than the latest one.

With:
Linux 5.10.0-9-cloud-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) amd64 (x86_64)
it fails consistently.
With:
Linux 5.10.0-21-cloud-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) amd64 (x86_64)
It works consistently.


Just upgrading the kernel makes the problem disappear for me. So you
should be able to reproduce the problem by downgrading the kernel (using
snapshot.d.o).

I had not updated the image (AWS AMI) I am using for the rebuilds for a
long time. Sorry about that.

Lucas

Bug#1014662: cloud-initramfs-growroot: Initramfs hook does not include `flock` command

[Santiago Vila]

After applying the suggested patch, the reported error
does not show anymore.

Instead, I get this:

/scripts/local-bottom/growroot: line 97: wait-for-root: not found

Where does this "wait-for-root" come from?
I can't find it in any package.

Thanks.

Bug#1029260: vice: missing font license in d/copyright

[GCS]

Control: found -1 2.1.dfsg-1
Control: severity -1 important

On Sun, Jan 29, 2023 at 4:03 PM Bastian Germann  wrote:
> So if that font is not GPL-compibly licensed, CBM cannot be GPL licensed.
 It's mentioned as '100% free' and was added to the VICE project in
its 1.22.9 release. The first package version uploaded with it is
2.1.dfsg-1 from March, 2009.

Cheers,
Laszlo/GCS

Processed: Re: Bug#1029260: vice: missing font license in d/copyright

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.1.dfsg-1
Bug #1029260 [src:vice] vice: missing font license in d/copyright
Marked as found in versions vice/2.1.dfsg-1.
> severity -1 important
Bug #1029260 [src:vice] vice: missing font license in d/copyright
Severity set to 'important' from 'serious'

-- 
1029260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029260
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

[Theodore Ts'o]

On Fri, Feb 17, 2023 at 12:43:01PM -0700, Sam Hartman wrote:
> 
> I am not entirely convinced that using current rather than guest
> tools for image building is an anti-pattern.  You've been working on
> filesystems for a long time; I've been working on various image
> building projects since my first watchmaker project at MIT.

For what it's worth, I've been building test appliances[1] for the
purposes of file system testing since 2013 (initially just for Qemu,
but now for Cloud[2] environments as well as Android[3]).  Admittedly,
I haven't been doing this as long as you, but I'm not unfamiliar with
building appliance images using debootstrap, and I've *always* built
my KVM/Qemu images using a build chroot[4], including the mkfs and
debootstrap steps.

[1] https://github.com/tytso/xfstests-bld/blob/master/test-appliance/gen-image
[2] https://thunk.org/gce-xfstests
[3] https://thunk.org/android-xfstests
[4] https://github.com/tytso/xfstests-bld/blob/master/setup-buildchroot

So I'm happy to talk to you off-line about best practices for building
images, but this is something that I do *regularly*, since there are
weekly updates from upstream xfstests.  Thus, I have personal
experience that using a build chroot for image creation really is
*not* *that* *hard*.  For that matter, when I'm doing test appliance
development, I'm running regression tests[5] several times a day which
build images in a chroot.

[5] https://github.com/tytso/xfstests-bld/blob/master/selftests/appliance

Everything is automated.  No fuss, no muss, no dirty dishes.  :-)
Futher, it provides better build reproducibility, no matter who is
building the image, and it also makes full GPL compliance (if you are
publishing the test appliances) much, *much* easier --- I can provide
an exhaustive list of all components (including mkfs.ext4!) and control
scripts involved with the creation of the image.

Cheers,

- Ted

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

[Salvatore Bonaccorso]

Hi Gabriel,

On Thu, Feb 16, 2023 at 11:37:57PM +0100, Gabriel Corona wrote:
> Hi,
> 
> Thanks for the patch!

Thanks for staying on top of the issue!
> 
> 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.

The last upload to unstable as NMU was for me personally to near to
the point release before christmas. A while has passed, and have now
proposed the same change for bullseye as well, cf. #1031527. Thanks
for pinging again on it, much appreciated! So the issue will/should be
fixed as well with the upcoming point release.

There is no CVE assigned, if you feel strong about it, can you try to
get one allocated by MITRE via the cveform? I think we won't go trough
the needed workflow to assign a Debian specific CVE id for it. But we
will see what MITRE will respond on the request.

Regards,
Salvatore

Bug#1031529: bcalm B-D on libgatbcore-dev which doesn't exist on several architectures

[Sergio Durigan Junior]

Source: bcalm
Version: 2.2.3-3
Severity: serious

Hi,

bcalm build-depends on libgatbcore-dev, but gatb-core has been recently
patched and stopped building on several architectures, including
e.g. s390x, armhf, etc.  bcalm's build will FTBFS on those
architectures.

Thank you,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Bug#1031530: discosnp B-D on libgatbcore-dev which doesn't exist on several architectures

[Sergio Durigan Junior]

Source: discosnp
Version: 1:2.6.2-1
Severity: serious

Hi,

discosnp build-depends on libgatbcore-dev, but gatb-core has been
recently patched and stopped building on several architectures,
including e.g. s390x, armhf, etc.  bcalm's build will FTBFS on those
architectures.

Thank you,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Bug#1031531: mindthegap B-D on libgatbcore-dev which doesn't exist on several architectures

[Sergio Durigan Junior]

Source: mindthegap
Version: 2.3.0-1
Severity: serious

Hi,

mindthegap build-depends on libgatbcore-dev, but gatb-core has been
recently patched and stopped building on several architectures,
including e.g. s390x, armhf, etc.  bcalm's build will FTBFS on those
architectures.

Thank you,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Bug#1031532: minia B-D on libgatbcore-dev which doesn't exist on several architectures

[Sergio Durigan Junior]

Source: minia
Version: 3.2.6-2
Severity: serious

Hi,

minia build-depends on libgatbcore-dev, but gatb-core has been recently
patched and stopped building on several architectures, including
e.g. s390x, armhf, etc.  bcalm's build will FTBFS on those
architectures.

Thank you,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Bug#1031533: simka B-D on libgatbcore-dev which doesn't exist on s390x

[Sergio Durigan Junior]

Source: simka
Version: 1.5.3-6
Severity: serious

Hi,

simka build-depends on libgatbcore-dev, but gatb-core has been recently
patched and stopped building on several architectures, including s390x.
simka's build will FTBFS on those architectures.

Thank you,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Bug#1031480: marked as done (libreflectasm-java: FTBFS: make: *** [debian/rules:4: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2023 21:49:48 +
with message-id 
and subject line Bug#1031480: fixed in libreflectasm-java 1.11.9+dfsg-4
has caused the Debian Bug report #1031480,
regarding libreflectasm-java: FTBFS: make: *** [debian/rules:4: binary] Error 25
to be marked as done.

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

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


-- 
1031480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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-

Bug#1031534: firmware-linux-nonfree: Package removed from sid and bookworm

[Gregor Riepl]

Package: firmware-linux-nonfree
Version: 20221214-3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: onit...@gmail.com

Dear Maintainer,

With the recent upgrade to version 20230210 (or 20230117 on testing), the
package has vanished from the apt cache of two of my bookworm/sid
installations.

apt policy reports that firmware-linux-nonfree is stuck at version 20221214-3
on my systems, with the only available version being the one that is locally
installed. According to https://tracker.debian.org/pkg/firmware-nonfree
everything seems to be fine, but I simply don't see any available upgrades.

Opening https://packages.debian.org/source/unstable/firmware-nonfree reports:

"Package not available in this suite."

Were these packages renamed, or what exactly is going on here?


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (300, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firmware-linux-nonfree depends on:
ii  firmware-amd-graphics  20221214-3
ii  firmware-misc-nonfree  20221214-3

Versions of packages firmware-linux-nonfree recommends:
ii  amd64-microcode  3.20220411.1
ii  intel-microcode  3.20221108.1

firmware-linux-nonfree suggests no packages.

-- no debconf information

Bug#1014662: cloud-initramfs-growroot: Initramfs hook does not include `flock` command

[undef]

Given that upstream changes to this package haven't been integrated in 
years and this bug being pretty limiting to users, Mobian moved to 
systemd-repart. If it's possible for you I might recommend the same 
solution.


Our experience has been that once implemented it is far more reliable. 
The switch can be seen at 
https://salsa.debian.org/Mobian-team/mobian-recipes/-/merge_requests/67/diffs


Key parts:

1. Partitions need to be GPT

2. Partitions being resized need a specific "parttype" UUID configured 
on them.


3. A simple config file needs to be installed in /etc/repart.d.

Bug#1014662: cloud-initramfs-growroot: Initramfs hook does not include `flock` command

[Ross Vandegrift]

On Fri, Feb 17, 2023 at 09:54:08PM +0100, Santiago Vila wrote:
> After applying the suggested patch, the reported error
> does not show anymore.
> 
> Instead, I get this:
> 
> /scripts/local-bottom/growroot: line 97: wait-for-root: not found
> 
> Where does this "wait-for-root" come from?
> I can't find it in any package.

There's a relevant MR in salsa:
https://salsa.debian.org/cloud-team/cloud-initramfs-tools/-/merge_requests/2

Would you mind testing the patch there?  I don't know how widely used
this package is.

Thanks,
Ross