Processed: Segmentation fault in plink2 (Was: src:plink2: fails to migrate to testing for too long: autopkgtest regression)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1000782 [src:plink2] plink2: autopkgtest regression: Segmentation fault
Bug 1000782 is not marked as done; doing nothing.
> tags -1 confirmed
Bug #1000782 [src:plink2] plink2: autopkgtest regression: Segmentation fault
Added tag(s) confirmed.
> tags -1 upstream
Bug #1000782 [src:plink2] plink2: autopkgtest regression: Segmentation fault
Added tag(s) upstream.
> forwarded -1 Christopher Chang 
Bug #1000782 [src:plink2] plink2: autopkgtest regression: Segmentation fault
Set Bug forwarded-to-address to 'Christopher Chang 
'.

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

Bug#1005820: Seems better after kernel upgrade and reboot

[Erwan David]

Since I upgraded to kernel 5.16.0-1-amd64, I no longer have those 
segfault messages in the logs.  I do not known wether the kernel or the 
reboot is responsible for this

Bug#1004037: Segmentation fault in plink2 (Was: src:plink2: fails to migrate to testing for too long: autopkgtest regression)

[Andreas Tille]

PS to last mail:  Here

   https://salsa.debian.org/med-team/plink2/-/jobs/2479769

is a full test log in our Gitlab CI for the latest version which I just
injected into the packaging Git repository but did not upload yet.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#1004037: Segmentation fault in plink2 (Was: src:plink2: fails to migrate to testing for too long: autopkgtest regression)

[Andreas Tille]

Control: reopen -1
Control: tags -1 confirmed
Control: tags -1 upstream
Control: forwarded -1 Christopher Chang 

Hi Christopher (and Dylan),

I verified the latest version (29 Jan 2022) of plink2 with the same
result for the CI test we are doing in Debian (which was written by
Dylan):

$ plink2 --dummy 33 65537 0.1 dosage-freq=0.1 --out tmp_data
PLINK v2.00a3 SSE4.2 (29 Jan 2022) www.cog-genomics.org/plink/2.0/
(C) 2005-2022 Shaun Purcell, Christopher Chang   GNU General Public License v3
Logging to tmp_data.log.
Options in effect:
  --dummy 33 65537 0.1 dosage-freq=0.1
  --out tmp_data

Start time: Thu Feb 17 06:34:30 2022
31998 MiB RAM detected; reserving 15999 MiB for main workspace.
Using up to 4 compute threads.
Dummy data (33 samples, 65537 SNPs) written to tmp_data.pgen + tmp_data.pvar +
tmp_data.psam .
End time: Thu Feb 17 06:34:30 2022
/usr/bin/plink2: line 8:   156 Segmentation fault  "${cmd}" "$@"


Please note that for the build the Debian packaged zstd and libdeflate
are used.  This is the same result as for the version released at 11 Oct
2021 which is currently uploaded to Debian unstable.  There is a full
log of the CI test available[1].

Kind regards

  Andreas.


[1] 
https://ci.debian.net/data/autopkgtest/testing/amd64/p/plink2/1921/log.gz


-- 
http://fam-tille.de

Processed: Segmentation fault in plink2 (Was: src:plink2: fails to migrate to testing for too long: autopkgtest regression)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1004037 {Done: Paul Gevers } [src:plink2] src:plink2: 
fails to migrate to testing for too long: autopkgtest regression
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions plink2/2.00~a3-211011+dfsg-1.
> tags -1 confirmed
Bug #1004037 [src:plink2] src:plink2: fails to migrate to testing for too long: 
autopkgtest regression
Added tag(s) confirmed.
> tags -1 upstream
Bug #1004037 [src:plink2] src:plink2: fails to migrate to testing for too long: 
autopkgtest regression
Added tag(s) upstream.
> forwarded -1 Christopher Chang 
Bug #1004037 [src:plink2] src:plink2: fails to migrate to testing for too long: 
autopkgtest regression
Set Bug forwarded-to-address to 'Christopher Chang 
'.

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

Bug#1005593: marked as done (node-marked-man: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)

[Debian Bug Tracking System]

Your message dated Thu, 17 Feb 2022 06:04:07 +
with message-id 
and subject line Bug#1005593: fixed in node-marked-man 0.7.0+~0.7.0-2
has caused the Debian Bug report #1005593,
regarding node-marked-man: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 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.)


-- 
1005593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-marked-man
Version: 0.7.0+~0.7.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ./bin/marked-man --date="283996800" README.md > marked-man.1
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/marked-man
>   /bin/sh -ex debian/tests/pkg-js/test
> + nodejs test/compare.js
> troff: :173: warning [p 1, 2.0i, div '3tbd17,3', 0.0i]: 
> cannot adjust line
> troff: :272: warning [p 1, 2.0i, div '3tbd28,3', 0.2i]: 
> cannot adjust line
> troff: :671: warning [p 1, 2.0i, div '3tbd73,0', 0.0i]: 
> cannot adjust line
> 
> Test failure, result written in /<>/test/out/table.err
> Failed tests:  1
> Succeeded tests:  11
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1


The full build log is available from:
http://qa-logs.debian.net/2022/02/12/node-marked-man_0.7.0+~0.7.0-1_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: node-marked-man
Source-Version: 0.7.0+~0.7.0-2
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-marked-man package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 17 Feb 2022 06:44:16 +0100
Source: node-marked-man
Architecture: source
Version: 0.7.0+~0.7.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1005593
Changes:
 node-marked-man (0.7.0+~0.7.0-2) unstable; urgency=medium
 .
   * Team upload
   * Workaround test bug (Closes: #1005593)
Checksums-Sha1: 
 d7ca8a7faf479829036b08cc3617521dde2e4d80 2422 
node-marked-man_0.7.0+~0.7.0-2.dsc
 6f5290a64707617ddcaaa7bc3c83e2433faa706b 4128 
node-marked-man_0.7.0+~0.7.0-2.debian.tar.xz
Checksums-Sha256: 
 c685535beb08b7226090c313831b19b8badf9d179f8ae6c01c78ebf2ffba774b 2422 
node-marked-man_0.7.0+~0.7.0-2.dsc
 5d4f40c37fd72b6fe719c2ed15054fc91159ad0da958cb9a2e55eb76936d0d17 4128 
node-marked-man_0.7.0+~0.7.0-2.debian.tar.xz
Files: 
 fb9e9a50983c0d6cec441fb75c775dd5 2422 javascript optional 
node-marked-man_0.7.0+~0.7.0-2.dsc
 36a22a14407d6a6b5476ed51a9c40afc 4128 javascript optional 
node-marked-man_0.7.0+~0.7.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmIN4RsACgkQ9tdMp8mZ
7ul70g//dYr0xDcx2qixo0mpfhT3TKFol4wteVwDRu5d1tYMDfGBaQmypUs0eR62
1EzSIneiGfrXd5ZW72MCvRoUma1J8cWLURkNOX/JWWvjUMkAYG0RQD2ybHYvQHrm
RbFdd+WoJ9A/JXghpJ6ekgmFtelGydzQ4LB4DGyWvk9dgGgFRxR+bgGLqh5/jIBF
vb2PHdAPssK6nG8D8p6b5ewmKwCXOv+KQ3jsmJ59DiUbsVZznelgzPLaYBP/DCYq
3EwGs1dNNCvT4ZJoev112k3vdyft2ZOCfHAm+Pa9A+Y7JKSNjvSqaIEA7a2hF2ED
chX7WWKKO5nuHCiddIFlxs6R4s4W6wXonYN+w4Otd3P+HXE9qIt2hqzBrRBc98Ls
vhNo2l37Pgw6gzKCJImpT1hsfuE6QZue9rbwnepnmnvAIAOhH9XoJbNciP53fqrY
X7BVytxjCtFoaBEPWQYzngDWVmRDYVoB6D7vK82eKCLTekhnHFVs1zEpJK6UP4WG
zmM1lo+GTRjw1+0RyoCnv/vJJreWYf2u

Processed: Bug#1005593 marked as pending in node-marked-man

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1005593 [src:node-marked-man] node-marked-man: FTBFS: dh_auto_test: error: 
/bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Added tag(s) pending.

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

Bug#1005593: marked as pending in node-marked-man

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-marked-man/-/commit/84b811729ee31f21321cafb8577bf0e8bdc1dd20


Workaround test bug

Closes: #1005593


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1005593

Processed: severity of 1005895 is grave

[Debian Bug Tracking System]

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

> severity 1005895 grave
Bug #1005895 [src:expat] expat: CVE-2022-25236
Ignoring request to change severity of Bug 1005895 to the same value.
> thanks
Stopping processing here.

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

Bug#1004285: [DAViCal-devel] Bug#1004285: davical: problems after upgrade to php 8, calendar clients reports "500"

[Florian Schlichting]

Hi Benno,

> I have looked at the apache2 log files and checked the /etc/php and
> /etc/davical directories if there were any references to php7 instead
> of php/php8.  The apache2 log file reported
> 
> [Mon Jan 24 11:29:29.678647 2022] [php:notice] [pid 684] [client /IPv6 
> address/] davical: LOG: response:-->DAViCal Fatal Error

Andrew fixed many issues with PHP 8 over the last few days. Are you able
to test with git versions of AWL and DAViCal? Otherwise it would be
helpful if you can find a few more lines from your logs containing the
PHP backtrace identifying the exact place in the code where the fatal
error occurred, as well as the PHP error message.

Florian

Processed: tagging 1005449

[Debian Bug Tracking System]

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

> tags 1005449 + fixed-upstream
Bug #1005449 [src:awl] awl: FTBFS: TypeError: implode(): Argument #2 ($array) 
must be of type ?array, string given - in tests/myCalendarTest.php:61
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#1005449: [DAViCal-devel] Bug#1005449: awl: FTBFS: sh: 1: error: Problems running dot: exit code=127, command='dot', arguments='"/<>/docs/api/inherit_graph_10.dot" -Tpng -o "/<

[Florian Schlichting]

On Sun, Feb 13, 2022 at 08:00:15AM +0100, Lucas Nussbaum wrote:
> Source: awl
> Version: 0.62-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220212 ftbfs-bookworm
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.


> >dh_auto_test
> > make -j4 test
> > make[1]: Entering directory '/<>'
> > # simple php syntax check
> > OK (Syntax checked)
> > # run phpunit tests
> > PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:./vendor/bin/
> >  phpunit tests/
> > PHPUnit 9.5.13 by Sebastian Bergmann and contributors.
> > 
> > 
> > Warning:   Test case class not matching filename is deprecated
> >in /<>/tests/myComponentTest.php
> >Class name was 'vComponentTest', expected 'myComponentTest'
> > Warning:   Test case class not matching filename is deprecated
> >in /<>/tests/myPropertyTest.php
> >Class name was 'vPropertyTest', expected 'myPropertyTest'
> > 
> > RE...R... 41 / 41 
> > (100%)
> > 
> > Time: 00:00.007, Memory: 6.00 MB
> > 
> > There was 1 error:
> > 
> > 1) myCalendarTest::test2
> > TypeError: implode(): Argument #2 ($array) must be of type ?array, string 
> > given
> > 
> > /<>/tests/myCalendarTest.php:61
> > 
> > --
> > 
> > There were 2 risky tests:
> > 
> > 1) myCalendarTest::test1
> > This test did not perform any assertions
> > 
> > /<>/tests/myCalendarTest.php:27
> > 
> > 2) vComponentTest::testRenderNoChanges2
> > This test did not perform any assertions
> > 
> > /<>/tests/myComponentTest.php:420
> > 
> > ERRORS!
> > Tests: 41, Assertions: 104, Errors: 1, Risky: 2.
> > make[1]: *** [Makefile:52: test] Error 2

tests/myCalendarTest.php:61 was fixed by
https://gitlab.com/davical-project/awl/-/commit/45f2ee44f2458a8c4e514fdf5a7b3bc329c44b9a

Processed: retitle 1005449 to awl: FTBFS: TypeError: implode(): Argument #2 ($array) must be of type ?array, string given - in tests/myCalendarTest.php:61

[Debian Bug Tracking System]

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

> retitle 1005449 awl: FTBFS: TypeError: implode(): Argument #2 ($array) must 
> be of type ?array, string given - in tests/myCalendarTest.php:61
Bug #1005449 [src:awl] awl: FTBFS: sh: 1: error: Problems running dot: exit 
code=127, command='dot', 
arguments='"/<>/docs/api/inherit_graph_10.dot" -Tpng -o 
"/<>/docs/api/inherit_graph_10.png"'
Changed Bug title to 'awl: FTBFS: TypeError: implode(): Argument #2 ($array) 
must be of type ?array, string given - in tests/myCalendarTest.php:61' from 
'awl: FTBFS: sh: 1: error: Problems running dot: exit code=127, command='dot', 
arguments='"/<>/docs/api/inherit_graph_10.dot" -Tpng -o 
"/<>/docs/api/inherit_graph_10.png"''.
> thanks
Stopping processing here.

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

Bug#1005804: xserver-xorg-video-nvidia-legacy-390xx: does not depend on xorg-video-abi-25

[Vincent Lefevre]

On 2022-02-17 00:35:40 +0100, Andreas Beckmann wrote:
> On 16/02/2022 15.10, Vincent Lefevre wrote:
> > On 2022-02-15 13:06:57 +0100, Andreas Beckmann wrote:
> > > If you force the installation of the driver with the new X server, can you
> > > confirm that the driver works without complaining about an ABI mismatch?
> > 
> > This seems to work on my desktop machine at my lab.
> 
> Thanks for confirming. Enabled xorg-video-abi-25 on the package

FYI, this also works without any issue on my laptop, with 2 external
monitors.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1005902: xmms2: do not release with bookworm

[Sebastian Ramacher]

Source: xmms2
Version: 0.8+dfsg-22
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm

Upstream development of xmms2 has seized. There is no activity at
https://github.com/xmms2 and xmms2.org no longer exists. The last
upstream release was in 2011, so it's time to let it go.

Cheers



signature.asc
Description: PGP signature

Bug#1005804: xserver-xorg-video-nvidia-legacy-390xx: does not depend on xorg-video-abi-25

[Andreas Beckmann]

On 16/02/2022 15.10, Vincent Lefevre wrote:

On 2022-02-15 13:06:57 +0100, Andreas Beckmann wrote:

If you force the installation of the driver with the new X server, can you
confirm that the driver works without complaining about an ABI mismatch?


This seems to work on my desktop machine at my lab.


Thanks for confirming. Enabled xorg-video-abi-25 on the package

Now we just need someone confirming that for the Tesla 418/450/460 
drivers, too. 450 probably works, the other two probably don't.



Andreas

Bug#1005458: marked as done (spirv-llvm-translator: FTBFS: SPIRVOpCode.h:52:31: error: ‘OpConstFunctionPointerINTEL’ was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2022 22:49:44 +
with message-id 
and subject line Bug#1005458: fixed in spirv-llvm-translator 13.0.0-3
has caused the Debian Bug report #1005458,
regarding spirv-llvm-translator: FTBFS: SPIRVOpCode.h:52:31: error: 
‘OpConstFunctionPointerINTEL’ was not declared in this scope
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.)


-- 
1005458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spirv-llvm-translator
Version: 13.0.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> cd /<>/build/lib/SPIRV && /usr/bin/c++ -D__STDC_CONSTANT_MACROS 
> -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/usr/lib/llvm-13/include 
> -I/<>/include -I/usr/include/include 
> -I/<>/lib/SPIRV -I/<>/lib/SPIRV/libSPIRV 
> -I/<>/lib/SPIRV/Mangler -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time 
> -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual 
> -Wno-missing-field-initializers -Wimplicit-fallthrough -Wno-class-memaccess 
> -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type 
> -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment 
> -Wmisleading-indentation -ffunction-sections -fdata-sections -O3 -DNDEBUG 
> -fPIC  -fno-exceptions -std=gnu++14 -MD -MT 
> lib/SPIRV/CMakeFiles/LLVMSPIRVLib.dir/Mangler/ManglingUtils.cpp.o -MF 
> CMakeFiles/LLVMSPIRVLib.dir/Mangler/ManglingUtils.cpp.o.d -o 
> CMakeFiles/LLVMSPIRVLib.dir/Mangler/ManglingUtils.cpp.o -c 
> /<>/lib/SPIRV/Mangler/ManglingUtils.cpp
> [ 15%] Building CXX object 
> lib/SPIRV/CMakeFiles/LLVMSPIRVLib.dir/Mangler/ParameterType.cpp.o
> In file included from /<>/lib/SPIRV/libSPIRV/SPIRVEnum.h:44,
>  from /<>/lib/SPIRV/libSPIRV/SPIRVEntry.h:44,
>  from /<>/lib/SPIRV/libSPIRV/SPIRVModule.h:44,
>  from /<>/lib/SPIRV/LLVMToSPIRVDbgTran.h:42,
>  from /<>/lib/SPIRV/LLVMToSPIRVDbgTran.cpp:38:
> /<>/lib/SPIRV/libSPIRV/SPIRVOpCodeEnum.h: In member function 
> ‘void SPIRV::SPIRVMap::init() [with Ty1 = spv::Op; Ty2 
> = std::__cxx11::basic_string; Identifier = void]’:
> /<>/lib/SPIRV/libSPIRV/SPIRVOpCode.h:52:31: error: 
> ‘OpConstFunctionPointerINTEL’ was not declared in this scope
>52 | #define _SPIRV_OP(x, ...) add(Op##x, #x);
>   |   ^~
> /<>/lib/SPIRV/libSPIRV/SPIRVOpCodeEnum.h:347:1: note: in 
> expansion of macro ‘_SPIRV_OP’
>   347 | _SPIRV_OP(ConstFunctionPointerINTEL, 5600)
>   | ^
> cd /<>/build/lib/SPIRV && /usr/bin/c++ -D__STDC_CONSTANT_MACROS 
> -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/usr/lib/llvm-13/include 
> -I/<>/include -I/usr/include/include 
> -I/<>/lib/SPIRV -I/<>/lib/SPIRV/libSPIRV 
> -I/<>/lib/SPIRV/Mangler -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time 
> -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual 
> -Wno-missing-field-initializers -Wimplicit-fallthrough -Wno-class-memaccess 
> -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type 
> -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment 
> -Wmisleading-indentation -ffunction-sections -fdata-sections -O3 -DNDEBUG 
> -fPIC  -fno-exceptions -std=gnu++14 -MD -MT 
> lib/SPIRV/CMakeFiles/LLVMSPIRVLib.dir/Mangler/ParameterType.cpp.o -MF 
> CMakeFiles/LLVMSPIRVLib.dir/Mangler/ParameterType.cpp.o.d -o 
> CMakeFiles/LLVMSPIRVLib.dir/Mangler/ParameterType.cpp.o -c 
> /<>/lib/SPIRV/Mangler/ParameterType.cpp
> In file included from /<>/lib/SPIRV/libSPIRV/SPIRVEnum.h:44,
>  from /<>/lib/SPIRV/libSPIRV/SPIRVEntry.h:44,
>  from /<>/lib/SPIRV/libSPIRV/SPIRVModule.h:44,
>  from /<>/lib/SPIRV/LLVMToSPIRVDbgTran.h:42,
>  from /<>/lib/SPIRV/LLVMToSPIRVDbgTran.cpp:38:
> /<>/lib/SPIRV/libSPIRV/SPIRVOpCode.h: In function ‘bool 
> SPIRV::isConstantOpCode(spv::Op)’:
> /<>/lib/SPIRV/libSPIRV/SPIRVOpCode.h:229:47: error: 
> ‘OpConstFunctionPointerINTEL’ was not declared in this scope
>   229 |  OC == OpConstantPipeStorage || OC == 
> OpConstFunctionPointerINTEL;
>   |  

Processed: Re: Bug#1005881: runit-init: Not installable in bookworm.

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1005881 [runit-init] runit-init: Not installable in bookworm.
Severity set to 'important' from 'grave'

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

Bug#1005899: mplayer: should not release with bookworm

[Sebastian Ramacher]

Source: mplayer
Version: 2:1.4+ds1-3
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm

Let's stop pretending that mplayer is maintained. The upstream mailing
list infrastructure is gone and development has been minimal over the
last couple of months and years. So I think we should not include
mplayer in bookworm. mpv is a worthy replacement for mplayer.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1005852: marked as done (ssreflect doesn't migrate, still broken autopkg tests)

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2022 21:57:48 +
with message-id 
and subject line Bug#1005852: fixed in ssreflect 1.14.0-7
has caused the Debian Bug report #1005852,
regarding ssreflect doesn't migrate, still broken autopkg tests
to be marked as done.

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

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


-- 
1005852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ssreflect
Version: 1.14.0-6
Severity: serious
Tags: sid bookworm

the autopkg tests still fail:

[...]
Setting up gcc (4:11.2.0-2) ...
Processing triggers for libc-bin (2.33-5) ...
autopkgtest: WARNING: package libcoq-mathcomp-algebra is not installed though it
should be
autopkgtest: WARNING: package libcoq-mathcomp-character is not installed though
it should be
autopkgtest: WARNING: package libcoq-mathcomp-field is not installed though it
should be
autopkgtest: WARNING: package libcoq-mathcomp-fingroup is not installed though
it should be
autopkgtest: WARNING: package libcoq-mathcomp-solvable is not installed though
it should be
autopkgtest: WARNING: package libcoq-mathcomp-ssreflect is not installed though
it should be
autopkgtest: WARNING: package libcoq-mathcomp is not installed though it should 
be
autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt
pinning. Retrying with using all packages from unstable
Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies...Starting pkgProblemResolver with broken count: 6
Starting 2 pkgProblemResolver with broken count: 6
Investigating (0) libcoq-mathcomp-solvable:amd64 < none -> 1.14.0-6 @un uN Ib >
Broken libcoq-mathcomp-solvable:amd64 Breaks on libssreflect-coq:amd64 < none |
1.14.0-3 @un uH >
  Conflicts//Breaks against version 1.14.0-3 for libssreflect-coq but that is
not InstVer, ignoring
  Considering libcoq-mathcomp:amd64 -6 as a solution to
libcoq-mathcomp-solvable:amd64 4
  Added libcoq-mathcomp:amd64 to the remove list
  Fixing libcoq-mathcomp-solvable:amd64 via keep of libcoq-mathcomp:amd64
Investigating (0) autopkgtest-satdep:amd64 < 0 @iU K Nb Ib >
Broken autopkgtest-satdep:amd64 Depends on libcoq-mathcomp:amd64 < none |
1.14.0-6 @un uH >
  Considering libcoq-mathcomp:amd64 -6 as a solution to 
autopkgtest-satdep:amd64 -2
  Removing autopkgtest-satdep:amd64 rather than change libcoq-mathcomp:amd64
Done
 Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following packages will be REMOVED:
  autopkgtest-satdep
0 upgraded, 0 newly installed, 1 to remove and 15 not upgraded.
1 not fully installed or removed.[...]

[...]

Removing autopkgtest-satdep (0) ...
autopkgtest: WARNING: package libcoq-mathcomp-algebra is not installed though it
should be
autopkgtest: WARNING: package libcoq-mathcomp-character is not installed though
it should be
autopkgtest: WARNING: package libcoq-mathcomp-field is not installed though it
should be
autopkgtest: WARNING: package libcoq-mathcomp-fingroup is not installed though
it should be
autopkgtest: WARNING: package libcoq-mathcomp-solvable is not installed though
it should be
autopkgtest: WARNING: package libcoq-mathcomp-ssreflect is not installed though
it should be
autopkgtest: WARNING: package libcoq-mathcomp is not installed though it should 
be
autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install
on test deps directly for further data about failing dependencies in test logs
Reading package lists...
Building dependency tree...
Reading state information...
Starting pkgProblemResolver with broken count: 6
Starting 2 pkgProblemResolver with broken count: 6
Investigating (0) libcoq-mathcomp-solvable:amd64 < none -> 1.14.0-6 @un puN Ib >
Broken libcoq-mathcomp-solvable:amd64 Breaks on libssreflect-coq:amd64 < none
@un pH >
  Conflicts//Breaks against version 1.14.0-3 for libssreflect-coq but that is
not InstVer, ignoring
  Considering libcoq-mathcomp:amd64 9993 as a solution to
libcoq-mathcomp-solvable:amd64 10002
Investigating (0) libcoq-mathcomp-ssreflect:amd64 < none -> 1.14.0-6 @un puN Ib 
>
Broken libcoq-mathcomp-ssreflect:amd64 Breaks on libssreflect-coq:amd64 < none
@un pH >
  Conflicts//Breaks against version 1.14.0-3 for libssreflect-coq but that is
not InstVer, ignoring
  Considering libcoq-mathcomp:amd64 9993 as a solution to
libcoq-mathcomp-ssreflect:amd64 10002
Investigating (0) libcoq-mathcomp-algebra:amd64 < none -> 1.14.0-6 @un puN Ib >
Broken libcoq-mathcomp-algebra:amd64 Breaks on libssreflect-coq:amd64 < none @un
pH >
  Conflic

Processed: severity of 1005894 is grave

[Debian Bug Tracking System]

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

> severity 1005894 grave
Bug #1005894 [src:expat] expat: CVE-2022-25235
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1005895 is grave

[Debian Bug Tracking System]

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

> severity 1005895 grave
Bug #1005895 [src:expat] expat: CVE-2022-25236
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Processed: Bug#1005852 marked as pending in ssreflect

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1005852 [src:ssreflect] ssreflect doesn't migrate, still broken autopkg 
tests
Added tag(s) pending.

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

Bug#1005852: marked as pending in ssreflect

[Julien Puydt]

Control: tag -1 pending

Hello,

Bug #1005852 in ssreflect 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/ocaml-team/ssreflect/-/commit/ec4a6dfe346919f082e2621a58b58230e6d1ddf0


Better for for Breaks+Replaces (Closes: #1005852)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1005852

Bug#997120: [Debian-med-packaging] Bug#997120:

[Andreas Tille]

Am Wed, Feb 16, 2022 at 09:00:28PM +0100 schrieb Jose Luis Rivero:
> 
> No worries Emmanuel, thanks for your offer to help. I have not pinged the
> ftp-master team yet,
> so you are on time to help the poor Gazebo to go to testing :)

camitk was accepted and I have done a source-only upload.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#1005567: marked as done (gnome-screenshot: FTBFS: ../data/meson.build:3:0: ERROR: Function does not take positional arguments.)

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2022 20:39:03 +
with message-id 
and subject line Bug#1005567: fixed in gnome-screenshot 41.0-2
has caused the Debian Bug report #1005567,
regarding gnome-screenshot: FTBFS: ../data/meson.build:3:0: ERROR: Function 
does not take positional arguments.
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.)


-- 
1005567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-screenshot
Version: 41.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-screenshot
> Project version: 41.0
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Library m found: YES
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency x11 found: YES 1.7.2
> Run-time dependency xext found: YES 1.3.4
> Run-time dependency glib-2.0 found: YES 2.70.3
> Run-time dependency gtk+-3.0 found: YES 3.24.31
> Run-time dependency libhandy-1 found: YES 1.5.90
> Has header "X11/extensions/shape.h" : YES 
> Configuring config.h using configuration
> 
> ../data/meson.build:3:0: ERROR: Function does not take positional arguments.
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2022-02-12T22:48:12.251179
> Main binary: /usr/bin/python3
> Build Options: -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu 
> -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain 
> -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-screenshot
> Project version: 41.0
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs
> Sanity check compile stdout:
> 
> -
> Sanity check compile stderr:
> 
> -
> Running test binary command: 
> /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs
> Sanity check compile stdout:
> 
> -
> Sanity check compile stderr:
> 
> -
> Running test binary command: 
> /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe
> C compiler for the build machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the build machine: cc ld.bfd 2.38
> Build machine cpu family: x86_64
> Build machine cpu: x86_64
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Target machine cpu family: x86_64
> Target machine cpu: x86_64
> Running compile:
> Working directory:  
> /<>/obj-x86_64-linux-gnu/meson-private/tmp2oxmuceg
> Command line:  cc 
> /<>/obj-x86_64-linux-gnu/meson-private/tmp2oxmuceg/testfile.c -o 
> /<>/obj-x86_64-linux-gnu/meson-private/tmp2oxmuceg/output.exe -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -D_FILE_OFFSET_BITS=64 -O0 -Wl,--start-group -lm -Wl,--end-group 
> -Wl,--allow-shlib-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs 
> 
> Code:
>  int main(void) { return 0; }
> 
> Compiler stdout:
> 

Bug#1005544: marked as done (polari: FTBFS: ../data/appdata/meson.build:2:0: ERROR: Function does not take positional arguments.)

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2022 20:40:30 +
with message-id 
and subject line Bug#1005544: fixed in polari 41.0-3
has caused the Debian Bug report #1005544,
regarding polari: FTBFS: ../data/appdata/meson.build:2:0: ERROR: Function does 
not take positional arguments.
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: polari
> Project version: 41.0
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Program js78 found: YES (/usr/bin/js78)
> Program desktop-file-validate found: YES (/usr/bin/desktop-file-validate)
> Program json-glib-validate found: YES (/usr/bin/json-glib-validate)
> Program appstream-util found: YES (/usr/bin/appstream-util)
> Program meson/check-version.py found: YES 
> (/<>/meson/check-version.py)
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency gio-2.0 found: YES 2.70.3
> Run-time dependency telepathy-glib found: YES 0.24.1
> Run-time dependency gobject-introspection-1.0 found: YES 1.70.0
> Run-time dependency gjs-1.0 found: YES 1.70.1
> Checking for function "strcasestr" : YES 
> Configuring config.h using configuration
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources)
> Configuring org.gnome.Polari.src.gresource.xml using configuration
> Configuring config.js.in using configuration
> Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources)
> Dependency gobject-introspection-1.0 found: YES 1.70.0 (cached)
> Dependency gobject-introspection-1.0 found: YES 1.70.0 (cached)
> Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner)
> Dependency gobject-introspection-1.0 found: YES 1.70.0 (cached)
> Program g-ir-compiler found: YES (/usr/bin/g-ir-compiler)
> 
> ../data/appdata/meson.build:2:0: ERROR: Function does not take positional 
> arguments.
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2022-02-12T22:48:58.039134
> Main binary: /usr/bin/python3
> Build Options: -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu 
> -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain 
> -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: polari
> Project version: 41.0
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-z,defs
> Sanity check compile stdout:
> 
> -
> Sanity check compile stderr:
> 
> -
> Running test binary command: 
> /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-z,defs
> Sanity check compile stdout:
> 
> -
> Sanity check compile stderr:
> 
> -
> Running test binary command: 
> /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe
> C compiler for the build machine: cc

Bug#1005885: marked as done (missing entries in debian/copyright)

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2022 20:34:54 +
with message-id 
and subject line Bug#1005885: fixed in camitk 5.0.2-2
has caused the Debian Bug report #1005885,
regarding missing entries in debian/copyright
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.)


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

Package: camitk
Severity: serious
Usertags: ftp
User: alteh...@debian.org
thanks

Hi,

please also mention at least:
  CamiTK-5.0.2/python_sdk/pyside_global.h
  Insight Consortium
in your debian/coypright.

Thanks!
  Thorsten
--- End Message ---
--- Begin Message ---
Source: camitk
Source-Version: 5.0.2-2
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated camitk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 16 Feb 2022 19:21:57 +0100
Source: camitk
Architecture: source
Version: 5.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1005885
Changes:
 camitk (5.0.2-2) unstable; urgency=medium
 .
   * Add missing Copyright entry
 Closes: #1005885
Checksums-Sha1:
 b47dbe0a906ec93845337203880ce7d72b7b5273 2834 camitk_5.0.2-2.dsc
 65bb7330d4583edce5df8b4095de46bb52a131b7 56356 camitk_5.0.2-2.debian.tar.xz
 6b876cf42ee6644edffca395a67aef1ee0d774b8 28297 camitk_5.0.2-2_amd64.buildinfo
Checksums-Sha256:
 345de084038ed406008a4df1f75a6b5bdb2e40a18177c76bc9bcbb09b013bc02 2834 
camitk_5.0.2-2.dsc
 62201acad244144d81f254adef6c94413eeb7d7be628d6e2f114c82b52488eef 56356 
camitk_5.0.2-2.debian.tar.xz
 aff1308ec9cc4d324e0022c46f3c843364c5e4d8448decfd5d99e50b17990943 28297 
camitk_5.0.2-2_amd64.buildinfo
Files:
 927250791e9eda5d2ce216ab28c5c3e7 2834 science optional camitk_5.0.2-2.dsc
 99b74ea58a055db1a6831b1f3b478d19 56356 science optional 
camitk_5.0.2-2.debian.tar.xz
 fffb06fbb092126955b50757332fcd82 28297 science optional 
camitk_5.0.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmINU3MRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHd1w/8CjyZdtd/TnDmMcaMD11xdUJ7aT06LVf0
6SmTxUTyzQvyEqsZHLq44LYQrE4aV2KthT13FEIli378XruLwRV1GKmbIr/uh0TH
urgGShR9U70cMxQoAJ75eHHpPEuiySnwEDcR56auAQXcVDpAHX7/yWxUDhL7/8GK
pzAASXMTCIsvoCPRAok3F/0nvSCf6JzBdDE5G2u736II0Dng8j7yJsipYFTYsC36
n9cUWI20zhiLSoXzS3LvsZG79R2kGTXRu6PjG5i7da9keRM5pSzGArUUMUY7EYAf
UV/2m4C938dgqH3q4P2w8flWrsV5N5C+N8IvyZtrwOplbNydlWJe4WIq55ll8EEC
d441SxGxECI7orsBCV7QZlq0/ZX2r23hqEioyibqU5MCSohbw/caoVadMeT+4okM
DiAFH8jeydwX2D8ntCEo6xd1mB8JTw6RVwCkCXlO5rYv8yxOzzNicB2RrDcLJ6K/
2VsEmQYrlNPQJfBlqWfk1/AUoqvtYZkYS1/bAu+3OdAcROwQJB+d7uRaEwoAttPs
0yD0kEToxr4ZQuyvFsbuwJpH5TT95QZs19FVkhtxNZixXgU3Zer6uvMI7O3YuoVl
DA4iOy6QQweO4+g5y/ZxRpd959KbuC7UE14xkEaX4mRzcTj8tG2qy9/g+T2+h1Dj
6XjZ9xwnnxk=
=4Z5W
-END PGP SIGNATURE End Message ---

Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers

[Paul Gevers]

Source: runc
Version: 1.1.0+ds1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package on amd64
because with a recent upload of glibc the autopkgtest of runc
fails in testing. Recently (mid January) your packages started to fail 
regularly and it seems to me that the failures are related to the

worker that the test runs on. ci-worker13 fails, while the other workers
are OK. Obviously I'm not sure it's related, but this particular host is 
extremely powerful, 256 GB RAM and 48 cores.


Don't hesitate to contact us at debian...@lists.debian.org if you need
help debugging this issue.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/r/runc/18799590/log.gz

ok  github.com/opencontainers/runc/libcontainer/utils   0.005s
?   github.com/opencontainers/runc/types[no test files]
FAIL
dh_auto_test: error: cd _build && go test -vet=off -v -p 48 -tags 
seccomp github.com/opencontainers/runc 
github.com/opencontainers/runc/libcontainer 
github.com/opencontainers/runc/libcontainer/apparmor 
github.com/opencontainers/runc/libcontainer/capabilities 
github.com/opencontainers/runc/libcontainer/cgroups 
github.com/opencontainers/runc/libcontainer/cgroups/devices 
github.com/opencontainers/runc/libcontainer/cgroups/ebpf 
github.com/opencontainers/runc/libcontainer/cgroups/ebpf/devicefilter 
github.com/opencontainers/runc/libcontainer/cgroups/fs 
github.com/opencontainers/runc/libcontainer/cgroups/fs2 
github.com/opencontainers/runc/libcontainer/cgroups/fscommon 
github.com/opencontainers/runc/libcontainer/cgroups/systemd 
github.com/opencontainers/runc/libcontainer/configs 
github.com/opencontainers/runc/libcontainer/configs/validate 
github.com/opencontainers/runc/libcontainer/devices 
github.com/opencontainers/runc/libcontainer/intelrdt 
github.com/opencontainers/runc/libcontainer/keys 
github.com/opencontainers/runc/libcontainer/logs 
github.com/opencontainers/runc/libcontainer/nsenter 
github.com/opencontainers/runc/libcontainer/nsenter/test 
github.com/opencontainers/runc/libcontainer/seccomp 
github.com/opencontainers/runc/libcontainer/seccomp/patchbpf 
github.com/opencontainers/runc/libcontainer/specconv 
github.com/opencontainers/runc/libcontainer/stacktrace 
github.com/opencontainers/runc/libcontainer/system 
github.com/opencontainers/runc/libcontainer/user 
github.com/opencontainers/runc/libcontainer/userns 
github.com/opencontainers/runc/libcontainer/utils 
github.com/opencontainers/runc/types returned exit code 1
make[1]: Leaving directory 
'/tmp/autopkgtest-lxc.v97d589s/downtmp/autopkgtest_tmp'

make[1]: *** [debian/rules:24: override_dh_auto_test] Error 25
make: *** [debian/rules:11: build] Error 2
autopkgtest [13:11:41]: test dh-golang-autopkgtest: ---]


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1005890: gsocket: flaky autopkgtest

[Paul Gevers]

Source: gsocket
Version: 1.4.33-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package on armhf 
because it was showing up as a regression for the upload of glibc. I 
noticed that the test regularly fails on all architectures.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/data/autopkgtest/testing/armhf/g/gsocket/19250005/log.gz

autopkgtest [07:10:23]: test upstream-tests: [---
Running: netcat #6.1 (stdin, 
1MB).[FAILED]-1

autopkgtest [07:10:25]: test upstream-tests: ---]


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1005889: dbus: flaky autopkgtest on ppc64el: dbus/integration/transient-services.sh.test

[Paul Gevers]

Source: dbus
Version: 1.12.20-3
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package on ppc64el 
because it was showing up as a regression for the upload of glibc. I 
noticed that the test regularly fails since the beginning of February 
this year. The failure is always the same (so far), and it happens on 
multiple of our hosts.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/packages/d/dbus/testing/ppc64el/

https://ci.debian.net/data/autopkgtest/testing/ppc64el/d/dbus/18861487/log.gz

Running test: 
dbus-debug-build/integration/transient-services.sh_with_config.test

1..2
Bail out! /run/user/1000/dbus-1/services is not a directory
FAIL: 
dbus-debug-build/integration/transient-services.sh_with_config.test 
(Child process exited with code 1)


[...]

SUMMARY: total=88; passed=87; skipped=0; failed=1; user=81.8s; 
system=55.2s; maxrss=23680
FAIL: 
dbus-debug-build/integration/transient-services.sh_with_config.test 
(Child process exited with code 1)


OpenPGP_signature
Description: OpenPGP digital signature

Bug#997120: [Debian-med-packaging] Bug#997120:

[Jose Luis Rivero]

On Wed, Feb 16, 2022 at 8:32 AM Emmanuel Promayon <
emmanuel.proma...@univ-grenoble-alpes.fr> wrote:

> Dear Jose and Andreas,
>
> On 14/02/2022 17:02, Andreas Tille wrote:
>
> Am Mon, Feb 14, 2022 at 12:18:47AM +0100 schrieb Jose Luis Rivero:
>
> You are welcome. This bug is preventing one of my packages (Gazebo) from
> being
> migrated to testing. Could we please upload a revision bump of the current
> version to solve this issue while we work on 5.0.2?
>
> Hmmm, that's a bit tricky now.  I've uploaded 5.0.2 to new[1].  May be
> pinging #debian-ftp could help?  (I'm hesitating a bit to do so myself
> since I used that option recently a bit frequently.)
>
> Sorry about that: I did not notice that bug 997120 was blocking gazebo
> (should there did not be a flag or message somewhere to alert about that?
> Being quite inexperienced I might well as missed it...)
> Let me know if (and how!) I can help with asking the ftpmaster team.
>

No worries Emmanuel, thanks for your offer to help. I have not pinged the
ftp-master team yet,
so you are on time to help the poor Gazebo to go to testing :)

Thanks!

>

Processed: Bug#1005567 marked as pending in gnome-screenshot

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1005567 [src:gnome-screenshot] gnome-screenshot: FTBFS: 
../data/meson.build:3:0: ERROR: Function does not take positional arguments.
Added tag(s) pending.

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

Bug#1005567: marked as pending in gnome-screenshot

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #1005567 in gnome-screenshot 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/gnome-team/gnome-screenshot/-/commit/f0e131842adf8ea65ca3c3cfe70efeed6e9fe2b5


Cherry-pick patch to fix build with latest meson

Closes: #1005567


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1005567

Bug#1005544: marked as pending in polari

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #1005544 in polari 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/gnome-team/polari/-/commit/febd3be4618ec83e8db776c1ed6d5dbeec7f6e2d


Cherry-pick patch to fix build with latest meson

Closes: #1005544


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1005544

Processed: Bug#1005544 marked as pending in polari

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1005544 [src:polari] polari: FTBFS: ../data/appdata/meson.build:2:0: 
ERROR: Function does not take positional arguments.
Added tag(s) pending.

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

Bug#1005645: marked as done (googletest: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2022 20:27:43 +0100
with message-id 
and subject line Re: Processed: Re: Bug#984366: thin-provisioning-tools: ftbfs 
with GCC-11
has caused the Debian Bug report #1005645,
regarding googletest: ftbfs with GCC-11
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.)


-- 
1005645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:thin-provisioning-tools
Version: 0.9.0-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/thin-provisioning-tools_0.9.0-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
  | ^~~
In file included from 
/usr/src/googletest/googlemock/include/gmock/gmock-function-mocker.h:42,
 from /usr/src/googletest/googlemock/include/gmock/gmock.h:61,
 from unit-tests/copier_t.cc:19:
/usr/src/googletest/googlemock/include/gmock/gmock-spec-builders.h:2021:37: 
error: expression cannot be used as a function
 2021 |  nullptr)   
\
  | ^
/usr/src/googletest/googlemock/include/gmock/gmock-spec-builders.h:2028:3: 
note: in expansion of macro ‘GMOCK_ON_CALL_IMPL_’
 2028 |   GMOCK_ON_CALL_IMPL_(obj, InternalExpectedAt, call)
  |   ^~~
unit-tests/copier_t.cc:220:9: note: in expansion of macro ‘EXPECT_CALL’
  220 | EXPECT_CALL(engine_, wait()).
  | ^~~
unit-tests/copier_t.cc: In member function ‘virtual void 
CopierTests_wait_can_timeout_Test::TestBody()’:
/usr/src/googletest/googlemock/include/gmock/gmock-spec-builders.h:2021:37: 
error: expression cannot be used as a function
 2021 |  nullptr)   
\
  | ^
/usr/src/googletest/googlemock/include/gmock/gmock-spec-builders.h:2028:3: 
note: in expansion of macro ‘GMOCK_ON_CALL_IMPL_’
 2028 |   GMOCK_ON_CALL_IMPL_(obj, InternalExpectedAt, call)
  |   ^~~
unit-tests/copier_t.cc:260:9: note: in expansion of macro ‘EXPECT_CALL’
  260 | EXPECT_CALL(engine_, wait(micro)).
  | ^~~
unit-tests/copier_t.cc:261:33: error: ‘make_wr’ was not declared in this scope
  261 | WillOnce(Return(make_wr(true, 0u)));
  | ^~~
In file included from 
/usr/src/googletest/googlemock/include/gmock/gmock-function-mocker.h:42,
 from /usr/src/googletest/googlemock/include/gmock/gmock.h:61,
 from unit-tests/copier_t.cc:19:
/usr/src/googletest/googlemock/include/gmock/gmock-spec-builders.h:2021:37: 
error: expression cannot be used as a function
 2021 |  nullptr)   
\
  | ^
/usr/src/googletest/googlemock/include/gmock/gmock-spec-builders.h:2028:3: 
note: in expansion of macro ‘GMOCK_ON_CALL_IMPL_’
 2028 |   GMOCK_ON_CALL_IMPL_(obj, InternalExpectedAt, call)
  |   ^~~
unit-tests/copier_t.cc:267:9

Processed: update bts with new meta info

[Debian Bug Tracking System]

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

> reassign 1003562 src:patroni 2.1.2-2
Bug #1003562 {Done: Michael Banck } 
[src:python-psutil, src:patroni] python-psutil breaks patroni autopkgtest: 
psutil.Error: 
Bug reassigned from package 'src:python-psutil, src:patroni' to 'src:patroni'.
No longer marked as found in versions patroni/2.1.2-2 and python-psutil/5.9.0-1.
No longer marked as fixed in versions patroni/2.1.2-3.
Bug #1003562 {Done: Michael Banck } [src:patroni] 
python-psutil breaks patroni autopkgtest: psutil.Error: 
Marked as found in versions patroni/2.1.2-2.
> fixed 1003562 2.1.2-3
Bug #1003562 {Done: Michael Banck } [src:patroni] 
python-psutil breaks patroni autopkgtest: psutil.Error: 
Marked as fixed in versions patroni/2.1.2-3.
> affects 1003562 src:python-psutil
Bug #1003562 {Done: Michael Banck } [src:patroni] 
python-psutil breaks patroni autopkgtest: psutil.Error: 
Added indication that 1003562 affects src:python-psutil
> thanks
Stopping processing here.

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

Bug#1005132: marked as done (drf-yasg-nonfree: File conflicts between two different 1.20.1-1 versions)

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2022 19:47:29 +0100
with message-id 
and subject line Re: Bug#1005132: drf-yasg-nonfree: File conflicts between two 
different 1.20.1-1 versions
has caused the Debian Bug report #1005132,
regarding drf-yasg-nonfree: File conflicts between two different 1.20.1-1 
versions
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.)


-- 
1005132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: drf-yasg-nonfree
Version: 1.20.1-1
Severity: serious
User: de...@kali.org
Usertags: origin-kali

drf-yasg-nonfree 1.20.1-1 was uploaded as source only on January 23th,
the lack of binaries ended up in the package being removed by dak's 
auto-cruft. Then the maintainer rebuilt a new source package while keeping
the 1.20.1-1 version and uploaded it again.

deb.debian.org is a CDN and keeps in cache the package files for a very
long time because they are supposed to be immutable so if you try to
download drf-yasg-nonfree from deb.debian.org you get the first version
of the package while the metadata refers to the second version and as
such you get a checksum error (as I did in Kali, while trying to mirror
bookworm):

Wrong checksum during receive of
'http://deb.debian.org/debian/pool/non-free/d/drf-yasg-nonfree/drf-yasg-nonfree_1.20.1-1.dsc':
md5 expected: 5c87ae878afc6adf6708439e2a0b4e97, got: 
63c6925011f77e02306f451036181a13
sha256 expected: 
2b3265636ef93b490b633cee9897c8462fb1cb42d1fb65226fb5a8601631ecd9, got:
834fa39b7b970704f936fc2a293ca47f9efc1939a62f5a33fcd0cea4e4a0767c
size expected: 2467, got: 2434

This bug is just a request to upload 1.20.1-2 to get rid of this
inconsistency that will last in deb.debian.org for as long as we don't
upload a new version.

The package has been temporarily removed from testing by Julien Cristau
to make sure that mirroring bookworm out of deb.debian.org will work
again shortly.

-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'oldoldstable'), (500, 
'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-3-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 1.20.1-2

Hello Raphaël,

Am Mon, Feb 07, 2022 at 06:23:20PM +0100 schrieb Raphaël Hertzog:

> drf-yasg-nonfree 1.20.1-1 was uploaded as source only on January 23th,
> the lack of binaries ended up in the package being removed by dak's 
> auto-cruft. Then the maintainer rebuilt a new source package while keeping
> the 1.20.1-1 version and uploaded it again.
> 
> deb.debian.org is a CDN and keeps in cache the package files for a very
> long time because they are supposed to be immutable so if you try to
> download drf-yasg-nonfree from deb.debian.org you get the first version
> of the package while the metadata refers to the second version and as
> such you get a checksum error (as I did in Kali, while trying to mirror
> bookworm):

... 

I've uploaded a new version -2 to get a higher version into the archive,
as also suggested from you by the direct email exchange.
This did make DAK happy again so I'll close this issue by this email.

Of course there was no intention behind the second upload to confuse
DAK, sorry for the mess and thank you for getting in contact with me!

Regards
Carsten--- End Message ---

Bug#997120: marked as done (camitk: FTBFS: ld: cannot find CMakeFiles/application-config.dir/CommandLineOptions.ixx.o: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2022 18:00:11 +
with message-id 
and subject line Bug#997120: fixed in camitk 5.0.2-1
has caused the Debian Bug report #997120,
regarding camitk: FTBFS: ld: cannot find 
CMakeFiles/application-config.dir/CommandLineOptions.ixx.o: No such file or 
directory
to be marked as done.

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

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


-- 
997120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: camitk
Version: 4.1.2-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed  -rdynamic 
> CMakeFiles/application-config.dir/application-config_autogen/mocs_compilation.cpp.o
>  CMakeFiles/application-config.dir/main.cpp.o 
> CMakeFiles/application-config.dir/CommandLineOptions.cxx.o 
> CMakeFiles/application-config.dir/CommandLineOptions.ixx.o -o 
> ../../../bin/camitk-config   -L/<>/camitk-build/lib/camitk-4.1  
> -L/<>/camitk-build/lib  -L/<>/camitk-build/bin  
> -L/sbuild-nonexistent/.config/CamiTK/lib/camitk-4.1  
> -L/sbuild-nonexistent/.config/CamiTK/lib  
> -L/sbuild-nonexistent/.config/CamiTK/bin  
> -L/<>/camitk-build/lib/camitk-4.1/components  
> -L/<>/camitk-build/lib/camitk-4.1/actions  
> -L/sbuild-nonexistent/.config/CamiTK/lib/camitk-4.1/components  
> -L/sbuild-nonexistent/.config/CamiTK/lib/camitk-4.1/actions  
> /usr/lib/x86_64-linux-gnu/libQt5Xml.so.5.15.2 
> /usr/lib/x86_64-linux-gnu/libQt5XmlPatterns.so.5.15.2 
> /usr/lib/x86_64-linux-gnu/libQt5Help.so.5.15.2 
> /usr/lib/x86_64-linux-gnu/libQt5UiTools.a 
> /usr/lib/x86_64-linux-gnu/libQt5OpenGL.so.5.15.2 
> /usr/lib/x86_64-linux-gnu/libQt5OpenGLExtensions.a 
> /usr/lib/x86_64-linux-gnu/libQt5Test.so.5.15.2 -lcamitkcore -lfreetype -lz 
> -lexpat /usr/lib/x86_64-linux-gnu/libvtkDomainsChemistryOpenGL2-7.1.so.7.1p.1 
> -ljpeg -lpng -ltiff 
> /usr/lib/x86_64-linux-gnu/libvtkFiltersGeneric-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkFiltersHyperTree-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkFiltersParallelDIY2-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkFiltersParallelFlowPaths-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkFiltersParallelGeometry-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkFiltersParallelImaging-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkFiltersParallelMPI-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkFiltersParallelStatistics-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkFiltersPoints-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkFiltersProgrammable-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkFiltersPython-7.1.so.7.1p.1 -lpython3.9 
> /usr/lib/libvtkWrappingTools-7.1.a 
> /usr/lib/x86_64-linux-gnu/libvtkFiltersReebGraph-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkFiltersSMP-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkFiltersSelection-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkFiltersTexture-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkFiltersVerdict-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkverdict-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkGUISupportQt-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkGUISupportQtSQL-7.1.so.7.1p.1 -lsqlite3 
> /usr/lib/x86_64-linux-gnu/libvtkIOAMR-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/hdf5/openmpi/libhdf5.so -lsz -ldl -lm 
> /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so 
> /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so 
> /usr/lib/x86_64-linux-gnu/hdf5/openmpi/libhdf5_hl.so 
> /usr/lib/x86_64-linux-gnu/libvtkIOEnSight-7.1.so.7.1p.1 -lnetcdf_c++ -lnetcdf 
> /usr/lib/x86_64-linux-gnu/libvtkIOExport-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkRenderingGL2PSOpenGL2-7.1.so.7.1p.1 -lgl2ps 
> /usr/lib/x86_64-linux-gnu/libvtkIOFFMPEG-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkIOMovie-7.1.so.7.1p.1 -ltheoraenc -ltheoradec 
> -logg /usr/lib/x86_64-linux-gnu/libvtkIOGDAL-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkIOGeoJSON-7.1.so.7.1p.1 -ljsoncpp 
> /usr/lib/x86_64-linux-gnu/libvtkIOImport-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkIOInfovis-7.1.so.7.1p.1 -lxml2 
> /usr/lib/x86_64-linux-gnu/libvtkIOMINC-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkIOMPIImage-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkIOMPIParallel-7.1.so.7.1p.1 
> /usr/lib/x86_64-linux-gnu/libvtkIOParallel-7.1.so.7.1p.1 
> /usr/lib/x86_

Bug#1005886: additional info

[Tony Power]

I've tried all amd64 ISO-CD installers available here:
https://cdimage.debian.org/cdimage/daily-builds/daily/

The computer is:
Lenovo X1 Carbon Gen 6
Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
Intel Dual Band Wireless-AC 8265 (iwlwifi loads fine, during installation)
Intel Ethernet Connection (4) I219-LM
Samsung Electronics NVMe SSD Controller SM981/PM981/PM983

Everything is currently working fine with Debian bullseye, therefore,
it shouldn't be an hardware problem.

Processed: Re: Bug#1005885: missing entries in debian/copyright

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #1005885 [camitk] missing entries in debian/copyright
Added tag(s) pending.

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

Bug#1005885: missing entries in debian/copyright

[Andreas Tille]

Control: tags -1 pending

Am Wed, Feb 16, 2022 at 05:30:01PM + schrieb Thorsten Alteholz:
> please also mention at least:
>   CamiTK-5.0.2/python_sdk/pyside_global.h
>   Insight Consortium
> in your debian/coypright.

Thanks for spotting this and filing this bug report which is
fixed in Git now.  It will be closed with the source-only upload
after clearing new queue.

Kind regards

Andreas. 

-- 
http://fam-tille.de

Bug#1005886: cdimage.debian.org: bookworm net-install CD hangs on "Detecting Network Hardware"

[Tony Power]

Package: cdimage.debian.org
Severity: grave
Tags: d-i
Justification: renders package unusable
X-Debbugs-Cc: powe...@gmail.com

Dear Maintainer,

For a few days I've been trying to install Debian bookworm using the 
net-install ISO (e.g., all of today's). All of them hang when it reaches the 
"Detecting Network Hardware". I'm able to switch to the log console, and 
everything seems to be fine, however, that step doesn't work. If I go to the 
disk partitioning step, I have the same problem.

It feels that the options are not displayed.

Cheers,
Tony

Bug#1005622: marked as done (libblockdev: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2022 17:33:47 +
with message-id 
and subject line Bug#1005622: fixed in dmraid 1.0.0.rc16-11
has caused the Debian Bug report #1005622,
regarding libblockdev: FTBFS: dpkg-gensymbols: error: some new symbols appeared 
in the symbols file: see diff output below
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.)


-- 
1005622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libblockdev
Version: 2.26-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 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_makeshlibs -- -c4
> dpkg-gensymbols: error: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: warning: debian/libblockdev-dm2/DEBIAN/symbols doesn't match 
> completely debian/libblockdev-dm2.symbols
> --- debian/libblockdev-dm2.symbols (libblockdev-dm2_2.26-1_amd64)
> +++ dpkg-gensymbolsnjXTfu 2022-02-12 22:44:06.350039704 +
> @@ -1,5 +1,23 @@
>  libbd_dm.so.2 libblockdev-dm2 #MINVER#
>  * Build-Depends-Package: libblockdev-dm-dev
> + _dbg_free@Base 2.26-1
> + _dbg_malloc@Base 2.26-1
> + _dbg_realloc@Base 2.26-1
> + _dbg_strdup@Base 2.26-1
> + _dbg_strndup@Base 2.26-1
> + _rebuild_raidset@Base 2.26-1
> + add_delimiter@Base 2.26-1
> + add_dev_to_array@Base 2.26-1
> + add_dev_to_set@Base 2.26-1
> + add_spare_dev_to_array@Base 2.26-1
> + alloc_dev_info@Base 2.26-1
> + alloc_lib_context@Base 2.26-1
> + alloc_meta_areas@Base 2.26-1
> + alloc_private@Base 2.26-1
> + alloc_private_and_read@Base 2.26-1
> + alloc_raid_dev@Base 2.26-1
> + alloc_raid_set@Base 2.26-1
> + base_partitioned_set@Base 2.26-1
>   bd_dm_activate_raid_set@Base 2.14
>   bd_dm_check_deps@Base 2.14
>   bd_dm_close@Base 2.14
> @@ -15,3 +33,150 @@
>   bd_dm_name_from_node@Base 2.14
>   bd_dm_node_from_name@Base 2.14
>   bd_dm_remove@Base 2.14
> + change_set@Base 2.26-1
> + check_busy_disk@Base 2.26-1
> + check_raid_set@Base 2.26-1
> + check_valid_format@Base 2.26-1
> + count_devices@Base 2.26-1
> + count_devs@Base 2.26-1
> + count_sets@Base 2.26-1
> + create_raidset@Base 2.26-1
> + ddf1_beginning@Base 2.26-1
> + ddf1_check_all_crcs@Base 2.26-1
> + ddf1_cr_off_maxpds_helper@Base 2.26-1
> + ddf1_cvt_adapter@Base 2.26-1
> + ddf1_cvt_all@Base 2.26-1
> + ddf1_cvt_config_record@Base 2.26-1
> + ddf1_cvt_disk_data@Base 2.26-1
> + ddf1_cvt_header@Base 2.26-1
> + ddf1_cvt_phys_drive@Base 2.26-1
> + ddf1_cvt_phys_drive_header@Base 2.26-1
> + ddf1_cvt_records@Base 2.26-1
> + ddf1_cvt_spare_record@Base 2.26-1
> + ddf1_cvt_virt_drive@Base 2.26-1
> + ddf1_cvt_virt_drive_header@Base 2.26-1
> + ddf1_dump_all@Base 2.26-1
> + ddf1_endianness@Base 2.26-1
> + ddf1_process_records@Base 2.26-1
> + ddf1_update_all_crcs@Base 2.26-1
> + del_dev_in_set@Base 2.26-1
> + delete_error_target@Base 2.26-1
> + delete_raidsets@Base 2.26-1
> + discover_devices@Base 2.26-1
> + discover_partitions@Base 2.26-1
> + discover_raid_devices@Base 2.26-1
> + discover_raid_devices_spares@Base 2.26-1
> + display_devices@Base 2.26-1
> + display_set@Base 2.26-1
> + display_table@Base 2.26-1
> + dm_create@Base 2.26-1
> + dm_reload@Base 2.26-1
> + dm_remove@Base 2.26-1
> + dm_resume@Base 2.26-1
> + dm_status@Base 2.26-1
> + dm_suspend@Base 2.26-1
> + dm_version@Base 2.26-1
> + dso@Base 2.26-1
> + dso_end_rebuild@Base 2.26-1
> + dso_get_members@Base 2.26-1
> + end_log@Base 2.26-1
> + erase_metadata@Base 2.26-1
> + file_dev_size@Base 2.26-1
> + file_metadata@Base 2.26-1
> + find_disk@Base 2.26-1
> + find_group@Base 2.26-1
> + find_or_alloc_raid_set@Base 2.26-1
> + find_raiddev@Base 2.26-1
> + find_set@Base 2.26-1
> + find_set_inconsistent@Base 2.26-1
> + find_spare@Base 2.26-1
> + format_error@Base 2.26-1
> + free_dev_info@Base 2.26-1
> + free_format_caps@Base 2.26-1
> + free_lib_context@Base 2.26-1
> + free_raid_dev@Base 2.26-1
> + free_raid_set@Base 2.26-1
> + free_string@Base 2.26-1
> + get_ata_serial@Base 2.26-1
> + get_basename@Base 2.26-1
> + get_dirname@Base 2.26-1
> + get_dm_type@Base 2.26-1
> + get_format@Base 2.26-1
> + get_format_caps@Base 2.26-1
> + get_raid_set@Base 2.26-1
> + get_scsi_id@Base 2.26-1
> + get_scsi_serial@Base 2.26-1
> + get_set_name@Base 2.26-1
> + get_set_type@Base 2.26-1
> + get_status@Base 2.26-1
> + get_type@Base 2.26-1
> + group_set@Base 2.26-1
> + hot_spare_add@Base 2.26-1
> + init_fn@Base 2.26-1
> + init_locking@Base 2.26-1
> + init_

Bug#1005885: missing entries in debian/copyright

[Thorsten Alteholz]

Package: camitk
Severity: serious
Usertags: ftp
User: alteh...@debian.org
thanks

Hi,

please also mention at least:
  CamiTK-5.0.2/python_sdk/pyside_global.h
  Insight Consortium
in your debian/coypright.

Thanks!
  Thorsten

Bug#1005622: [Pkg-utopia-maintainers] Bug#1005622: libblockdev: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below

[GCS]

Hi,

Sorry for the symlink breakage.

On Mon, Feb 14, 2022 at 6:54 PM Michael Biebl  wrote:
> While speaking of getting rid off unnecessary complexity: Is the
> separate udeb build still needed?
 This is what I sometimes decide to evaluate, but then time goes on
something else. :(
Now I'm going to upload Helmut's fix, thanks for that!

Regards,
Laszlo/GCS

Bug#1005669: binutils-or1k-elf: FTBFS: autoreconf2.69: 'configure.ac' or 'configure.in' is required

[Nicolas Boulenguez]

Source: binutils-or1k-elf
Followup-For: Bug #1005669

> > Apparently, a configure.ac has been forgotten alongside the generated
> > configure.
> > Commit dd96117a5e1da80ad1f977ea8abe39acc9f7e7cb works around the
> > issue.

> Hmm - I don't see the commit you mention above - did you perhaps forget
> to push?  Otherwise please provide me a URI so I know exactly what you
> are talking about.

I don’t know what is wrong. I can see it at:
https://salsa.debian.org/debian/binutils-or1k-elf/-/commit/dd96117a5e1da80ad1f977ea8abe39acc9f7e7cb

I am attaching the patch just in case.

> Also, I can suggest that you post the information to
> 1005...@bugs.debian.org instead of discretely here.

You are right, of course. Done.

Thanks.
>From dd96117a5e1da80ad1f977ea8abe39acc9f7e7cb Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Sun, 13 Feb 2022 19:07:19 +0100
Subject: debian/autoreconf: skip etc/ in 2.38-1, configure.ac is missing


diff --git a/debian/autoreconf b/debian/autoreconf
index f2daa59..88e8205 100755
--- a/debian/autoreconf
+++ b/debian/autoreconf
@@ -12,6 +12,9 @@ set -C -e -u
 # Exclude zlib, which fails (binutils/2.35.2 autoconf/2.71).
 # It is ignored in favor of the Debian package anyway.
 
+# Exclude etc, which contains etc/configure but not its source
+# (since 2.38-1).
+
 echo src
 
-dirname src/*/configure | grep -v -e zlib -e libiberty
+dirname src/*/configure | grep -v -e zlib -e libiberty -e etc

Bug#1005517: marked as done (gnome-mines: FTBFS: ../data/meson.build:18:0: ERROR: Function does not take positional arguments.)

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2022 16:49:34 +
with message-id 
and subject line Bug#1005517: fixed in gnome-mines 1:40.0-2
has caused the Debian Bug report #1005517,
regarding gnome-mines: FTBFS: ../data/meson.build:18:0: ERROR: Function does 
not take positional arguments.
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.)


-- 
1005517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-mines
Version: 1:40.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 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_configure -- --bindir=games
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu --bindir=games
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-mines
> Project version: 40.0
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Vala compiler for the host machine: valac (valac 0.54.6)
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency glib-2.0 found: YES 2.70.3
> Run-time dependency gee-0.8 found: YES 0.20.5
> Run-time dependency gtk+-3.0 found: YES 3.24.31
> Run-time dependency librsvg-2.0 found: YES 2.52.5
> Run-time dependency libgnome-games-support-1 found: YES 1.8.2
> Library m found: YES
> 
> ../data/meson.build:18:0: ERROR: Function does not take positional arguments.
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2022-02-12T22:47:49.837682
> Main binary: /usr/bin/python3
> Build Options: -Dprefix=/usr -Dbindir=games -Dlibdir=lib/x86_64-linux-gnu 
> -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain 
> -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-mines
> Project version: 40.0
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs
> Sanity check compile stdout:
> 
> -
> Sanity check compile stderr:
> 
> -
> Running test binary command: 
> /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Running compile:
> Working directory:  /tmp/tmpqtthjodt
> Command line:  valac /tmp/tmpqtthjodt/testfile.vala -C 
> 
> Code:
>  class MesonSanityCheck : Object { }
> Compiler stdout:
>  
> Compiler stderr:
>  
> Vala compiler for the host machine: valac (valac 0.54.6)
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs
> Sanity check compile stdout:
> 
> -
> Sanity check compile stderr:
> 
> -
> Running test binary command: 
> /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe
> C compiler for the build machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the build machine: cc ld.bfd 2.38
> Using cached compile:
> Cached command line:   
> 
> Code:
>  class MesonSanityCheck : Object { }
> Cached compiler stdout:
>  
> Cached compiler stderr:
>  
> Vala compiler for the build machine: valac (valac 0.54.6)
> Build machine cpu family: x86_64
> Build machine cpu: x86_64
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Target machine cpu family: x86_64
> Target machine cpu: x86_64
> Pkg-config binary for 1 is not cached.
> Pkg-config binary missing from cross or native file, or env var undefined.
> Tr

Bug#1005620: marked as done (node-css-tree: FTBFS: SyntaxError: Expect `]`)

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2022 16:35:26 +
with message-id 
and subject line Bug#1005620: fixed in node-css-tree 2.0.4-3
has caused the Debian Bug report #1005620,
regarding node-css-tree: FTBFS: SyntaxError: Expect `]`
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.)


-- 
1005620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-css-tree
Version: 2.0.4-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 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 '/<>'
> node scripts/bundle
> 
> internal/process/esm_loader.js:74
> internalBinding('errors').triggerUncaughtException(
>   ^
> SyntaxError: Expect `]`
> at Tokenizer.error 
> (file:///<>/lib/definition-syntax/tokenizer.js:50:15)
> at Tokenizer.eat 
> (file:///<>/lib/definition-syntax/tokenizer.js:41:18)
> at readGroup 
> (file:///<>/lib/definition-syntax/parse.js:435:15)
> at peek (file:///<>/lib/definition-syntax/parse.js:460:47)
> at readImplicitGroup 
> (file:///<>/lib/definition-syntax/parse.js:391:20)
> at parse (file:///<>/lib/definition-syntax/parse.js:545:20)
> at Object.get [as syntax] 
> (file:///<>/lib/lexer/Lexer.js:170:36)
> at dumpAtruleMapSyntax (file:///<>/lib/lexer/Lexer.js:37:47) 
> {
>   message: 'Expect `]`\n' +
> '  [ # | ?\n' +
> '-^',
>   input: '[ # | ?',
>   offset: 31,
>   rawMessage: 'Expect `]`'
> }
> make[1]: *** [debian/rules:7: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/02/12/node-css-tree_2.0.4-2_unstable.log

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

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

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

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-css-tree package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 16 Feb 2022 17:16:08 +0100
Source: node-css-tree
Architecture: source
Version: 2.0.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1005620
Changes:
 node-css-tree (2.0.4-3) unstable; urgency=medium
 .
   * Team upload
   * Add temporary patch to fix mdn-data (Closes: #1005620)
Checksums-Sha1: 
 17caddffb86f5e62c135ccc2431f19463d496c51 2121 node-css-tree_2.0.4-3.dsc
 5fdd0c6683f7478a90281ad00ab4727c8817b57a 28228 
node-css-tree_2.0.4-3.debian.tar.xz
Checksums-Sha256: 
 6a14230d01e0092e14ec5f12ee2ba94690cd1d7dc8410605f82288ad292c79aa 2121 
node-css-tree_2.0.4-3.dsc
 ebbc3f7fd68d8afb87850e7a8f470911774cb0771aa3132436acff486bc68257 28228 
node-css-tree_2.0.4-3.debian.tar.xz
Files: 
 bd048c7492768ac6198470800e440f0f 2121 javascript optional 
node-css-tree_2.0.4-3.dsc
 8216145a35b1e0fad1e6396c9e2d4011 28228 javascript optional 
node-css-tree_2.0.4-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmINI54ACgkQ9tdMp8mZ
7ul00Q//XqyW+bm3Zs58qHF0hvhjUzG1pF3RMW041cm+pdWQ6+QR4JpEB2N3Y9Ua
+SiCLbtbbgZr61Kbj7ENv8eU1QmoHOHtx6yy18iWQ7+6x1N3NiOC9A4BBxZGNAf3
D6RvdvIK81rgBAAOvXOWbijVMFfOHh8tyPIvk/J57lJXllSmk7Gm5rILxqs4Pi34
exHcm1kMyODQlAi6VH6ul8FEOlUisFk60dd8pPdptltI+CD6ashPmIjE18bgFIK9
8IKoriq31EI3Delc4OF7bP2eSwyr14ZvZFbJUrRkKj37uhTdT307PC+WMdC2x4xs
rjrBAiPzwbJsUzKgbFurVMO0lFMTscz/F3sl+Nt9L/hZDyXt4ow

Bug#1005517: marked as pending in gnome-mines

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #1005517 in gnome-mines 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/gnome-team/gnome-mines/-/commit/6eeaba777c9bb65f3d8ee460ca45a6cd0891514c


Cherry-pick patch to fix build with latest meson

Closes: #1005517


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1005517

Processed: Bug#1005517 marked as pending in gnome-mines

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1005517 [src:gnome-mines] gnome-mines: FTBFS: ../data/meson.build:18:0: 
ERROR: Function does not take positional arguments.
Added tag(s) pending.

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

Bug#1005004: marked as done (lots of missing entries in debian/copyright)

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2022 16:18:40 +
with message-id 
and subject line Bug#1005004: fixed in cockpit 263-1
has caused the Debian Bug report #1005004,
regarding lots of missing entries in debian/copyright
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.)


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

Package: cockpit
Severity: serious
Usertags: ftp
thanks

Hi,

please rework your debian/copyright. Especially everything from 
node_modules seems to be missing. Please also check other releases.


Thanks!
  Thorsten
--- End Message ---
--- Begin Message ---
Source: cockpit
Source-Version: 263-1
Done: Martin Pitt 

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

Debian distribution maintenance software
pp.
Martin Pitt  (supplier of updated cockpit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 16 Feb 2022 16:54:51 +0100
Source: cockpit
Architecture: source
Version: 263-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Martin Pitt 
Closes: 1005004
Changes:
 cockpit (263-1) unstable; urgency=medium
 .
   * New upstream release:
 - Shell: Fix browser history
 - Cockpit-Client: Enable forward/back button
 - debian/copyright: Add node_modules/ (Closes: #1005004)
Checksums-Sha1:
 81e4d71956191ac1b25b56d9160a59890544de73 2985 cockpit_263-1.dsc
 ace90af278ee844eb845a157afa20219bde7a0d7 8714548 cockpit_263.orig.tar.xz
 7869f2a15ef834bcce1cb384129bbcfbcf5743c3 18240 cockpit_263-1.debian.tar.xz
 fe1238d922f8dee3a33f714672d7552bec561a0d 6018 cockpit_263-1_source.buildinfo
Checksums-Sha256:
 5cbdcfb7b24e1412d18afd080c69f9b826a0b5e7e306c30deb558a438e3a3e10 2985 
cockpit_263-1.dsc
 e82366f446122d99b4e8dcc7510ffe7be9a8c5ca216b9d027ef989ba46452bd9 8714548 
cockpit_263.orig.tar.xz
 0e2cb00f217238fa9a60d7bb7589a48782c6a3c1fe4e1bf0dd6a289b8ed06b8a 18240 
cockpit_263-1.debian.tar.xz
 ddfbf665de316e22d82ec53c004e033510bf11dabacc9896dfda9a6927789aba 6018 
cockpit_263-1_source.buildinfo
Files:
 bad76acb39e9dcb26d825a0844f3f17b 2985 admin optional cockpit_263-1.dsc
 754cd1980d3d90c4dfed75eff394599e 8714548 admin optional cockpit_263.orig.tar.xz
 700f103e15aace77c94990772173ec04 18240 admin optional 
cockpit_263-1.debian.tar.xz
 c540f3773cc2ef9092c6d450da5b6cd4 6018 admin optional 
cockpit_263-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPbRrVe+lnUDmIyFI0U7xXa/hE0cFAmINHwAACgkQ0U7xXa/h
E0dkQA//bxeK5/+cPkY1Z8duG4rt0vFgEWAyo6EEindO6NkwobRrmbsGeHAnq0yk
fRFlZ8Q1Biyd9KvupNENE08AZaId6Vq8sMupqzv1lp8jumC8UDBiJHbk/RAe5bDe
ngawkkFz81SpzzCn+mTg6TtmLazy1aRZ71DQ7fcFf45aS0i1mTXG1MdseDfZ9loQ
KkJZevDsK1wkLlJHlE/D3qQN0zYSgaQ29Ikf9URdZDYU9LtS4wWpOwa8tqornkbR
WMrGtuWno98sqfRO66uH54YCsY5LlLOfsf9n2USDUBUHE5qmVSC7j2vcQShKHfEJ
vbeVjNN+4JixS5pLyXdHYYPKF164GnUiphFwoak6g31R/KZesCUA1M5pIRY5+T/J
P5VU9zd+iSS56bOEtQizaD3Y0Yn7qmfSw4B7hQ/XkrHuhk43dKMc3CALJsZQQOWG
PR6+UfK69OksIQ3LFYYnz5pvudj7SdnyhDy+Iq7PSUCQsM8lCIawD+KgpTe111dD
X/2SkLo/idMl6kfqnYy5+dxZO9TeLQ10dARSbi1HBtlk3bcP9uXvHfb2hW0TckpV
Fg0GWtylz3NgvuE+IpmODVpa9JY3R3mKWOx6RTI+MOhcPz3iRkq7ZfwMK0Rra282
VRJqyeKH6TPl7goxz9vnDYbnfDNXne14RkXSzqqNxNBJ9r1zCag=
=iR9/
-END PGP SIGNATURE End Message ---

Bug#1005620: marked as pending in node-css-tree

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-css-tree/-/commit/3d37b5deefe3430f1dbda9138fd3258c649adb53


Add patch to fix mdn-data

Closes: #1005620


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1005620

Processed: Bug#1005620 marked as pending in node-css-tree

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1005620 [src:node-css-tree] node-css-tree: FTBFS: SyntaxError: Expect `]`
Added tag(s) pending.

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

Bug#1005881: runit-init: Not installable in bookworm.

[David Essam]

Package: runit-init
Severity: grave
Justification: renders package unusable

Dear maintainer,

I just tried to switch to runit-init on bookworm, as I have done many times on 
installs of stable (bullseye).

On a new install with only standard system utilities I executed "apt-get 
install runit init"
What I expected to happen was for apt to complain & to have to repeat the 
command with 
--allow-remove-essential specified, watch it install, then reboot to a system 
using runit-init as pid 1.

What happened:
Apt still refused to install it, citing init pre-depends on systemd-sysv or 
sysvinit-core and that neither are installable.
Which is funny given currently apt-cache policy systemd-sysv shows version 
250.3-2 installed, the very thing I wish to switch
away from.

What I expected to happen, is for it to install, then to reboot into a system 
using runit-init & configure from there
just as I can when running stable. Even if I had to specify 
--allow-remove-essential. However, neither that nor even
--force-yes would cause runit-init to be installed.

I also tried with runit & runit-run installed, just to see if having those 
present already helped, it didn't.

The attempt did leave my system broken though I had to apt-get install 
--reinstall systemd-sysv then 
apt-get remove runit* before it would behave again.

I iaso tried switching to sysvinit-core first, that switch went well, but the 
attempt to switch to runit-init
had a very similar outcome, namely I couldn't find any way to install the 
package.

Currently I can see no method available to get this package installed.

It's possible of course that this is a bug in apt & needs reassigning, that 
however, is beyond my pay-grade to decide.


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

Kernel: Linux 5.16.0-1-amd64 (SMP w/2 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 runit-init depends on:
pn  getty-run
pn  initscripts  
pn  insserv  
ii  runit2.1.2-44

runit-init recommends no packages.

runit-init suggests no packages.

Bug#1005011: Please fix capnproto in unstable as well (Was: Re: Bug#1005011: fixed in capnproto 0.9.1-2)

[tony mancill]

On Wed, Feb 16, 2022 at 05:01:49PM +0530, Nilesh Patra wrote:
> 
> Tony/Tom, Can you do corresponding fixes for unstable too,
> or otherwise move experimental release to unstable?
> 
> Otherwise this bug is causing a un-warranted-for autorm, for example in 
> parsnp[1]
 
Hi Nilesh,

Thanks for the reminder; this work is already underway.  It's not as
simple as merely copying the changes made in 0.9.1 to the version in
unstable because they are different sources.

For what it's worth (nothing, I suppose), this is why I questioned the
severity of the filed bug in the first place.  I maintain that there are
many packages in Debian that don't have the copyright for every single
file in the source distribution correctly attributed in
debian/copyright, and yet don't have RC bugs file against them.

Thanks,
tony


signature.asc
Description: PGP signature

Bug#1005804: xserver-xorg-video-nvidia-legacy-390xx: does not depend on xorg-video-abi-25

[Vincent Lefevre]

On 2022-02-15 13:06:57 +0100, Andreas Beckmann wrote:
> If you force the installation of the driver with the new X server, can you
> confirm that the driver works without complaining about an ABI mismatch?

This seems to work on my desktop machine at my lab.

cventin:~> dpkg -l | grep -E '390xx|xserver'
ii  libegl-nvidia-legacy-390xx0:amd64390.147-1+b1   
 amd64NVIDIA binary EGL library (390xx legacy version)
ii  libgl1-nvidia-legacy-390xx-glvnd-glx:amd64   390.147-1+b1   
 amd64NVIDIA binary OpenGL/GLX library (GLVND variant) (390xx 
legacy version)
ii  libglx-nvidia-legacy-390xx0:amd64390.147-1+b1   
 amd64NVIDIA binary GLX library (390xx legacy version)
ii  libglx-nvidia-legacy-390xx0:i386 390.147-1+b1   
 i386 NVIDIA binary GLX library (390xx legacy version)
ii  libnvidia-legacy-390xx-cfg1:amd64390.147-1+b1   
 amd64NVIDIA binary OpenGL/GLX configuration library (390xx legacy 
version)
ii  libnvidia-legacy-390xx-cfg1:i386 390.147-1+b1   
 i386 NVIDIA binary OpenGL/GLX configuration library (390xx legacy 
version)
ii  libnvidia-legacy-390xx-cuda1:amd64   390.147-1+b1   
 amd64NVIDIA CUDA Driver Library (390xx legacy version)
ii  libnvidia-legacy-390xx-cuda1:i386390.147-1+b1   
 i386 NVIDIA CUDA Driver Library (390xx legacy version)
ii  libnvidia-legacy-390xx-cuda1-i386:i386   390.147-1+b1   
 i386 NVIDIA CUDA 32-bit runtime library (390xx legacy version)
ii  libnvidia-legacy-390xx-eglcore:amd64 390.147-1+b1   
 amd64NVIDIA binary EGL core libraries (390xx legacy version)
ii  libnvidia-legacy-390xx-fatbinaryloader:amd64 390.147-1+b1   
 amd64NVIDIA FAT binary loader (390xx legacy version)
ii  libnvidia-legacy-390xx-fatbinaryloader:i386  390.147-1+b1   
 i386 NVIDIA FAT binary loader (390xx legacy version)
ii  libnvidia-legacy-390xx-glcore:amd64  390.147-1+b1   
 amd64NVIDIA binary OpenGL/GLX core libraries (390xx legacy version)
ii  libnvidia-legacy-390xx-glcore:i386   390.147-1+b1   
 i386 NVIDIA binary OpenGL/GLX core libraries (390xx legacy version)
ii  libnvidia-legacy-390xx-ml1:amd64 390.147-1+b1   
 amd64NVIDIA Management Library (NVML) runtime library (390xx 
legacy version)
ii  libnvidia-legacy-390xx-ml1:i386  390.147-1+b1   
 i386 NVIDIA Management Library (NVML) runtime library (390xx 
legacy version)
ii  libnvidia-legacy-390xx-ptxjitcompiler1:amd64 390.147-1+b1   
 amd64NVIDIA PTX JIT Compiler library (390xx legacy version)
ii  libnvidia-legacy-390xx-ptxjitcompiler1:i386  390.147-1+b1   
 i386 NVIDIA PTX JIT Compiler library (390xx legacy version)
ii  nvidia-legacy-390xx-alternative  390.147-1+b1   
 amd64allows the selection of NVIDIA as GLX provider (390xx legacy 
version)
ii  nvidia-legacy-390xx-driver   390.147-1+b1   
 amd64NVIDIA metapackage (390xx legacy version)
ii  nvidia-legacy-390xx-driver-bin   390.147-1+b1   
 amd64NVIDIA driver support binaries (390xx legacy version)
ii  nvidia-legacy-390xx-driver-libs:amd64390.147-1+b1   
 amd64NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries) (390xx 
legacy version)
ii  nvidia-legacy-390xx-egl-icd:amd64390.147-1+b1   
 amd64NVIDIA EGL installable client driver (ICD)
ii  nvidia-legacy-390xx-kernel-dkms  390.147-1+b1   
 amd64NVIDIA binary kernel module DKMS source (390xx legacy version)
ii  nvidia-legacy-390xx-kernel-support   390.147-1+b1   
 amd64NVIDIA binary kernel module support files (390xx legacy 
version)
ii  nvidia-legacy-390xx-smi:i386 390.147-1+b1   
 i386 NVIDIA System Management Interface (390xx legacy version)
ii  nvidia-legacy-390xx-vdpau-driver:amd64   390.147-1+b1   
 amd64Video Decode and Presentation API for Unix - NVIDIA driver 
(390xx legacy)
ii  nvidia-legacy-390xx-vulkan-icd:amd64 390.147-1+b1   
 amd64NVIDIA Vulkan installable client driver (ICD) (390xx legacy 
version)
ii  nvidia-legacy-390xx-vulkan-icd:i386  390.147-1+b1   
 i386 NVIDIA Vulkan installable client driver (ICD) (390xx legacy 
version)
ii  nvidia-settings-legacy-390xx 390.147-1  
 

Bug#997746: marked as done (node-gulp-tsb: FTBFS: Error: Cannot find module './lib-prebuild')

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2022 13:49:31 +0100
with message-id 
and subject line Fixed
has caused the Debian Bug report #997746,
regarding node-gulp-tsb: FTBFS: Error: Cannot find module './lib-prebuild'
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.)


-- 
997746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-gulp-tsb
Version: 4.0.5+~cs7.0.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> gulp build
> [06:32:22] Local gulp not found in /<>
> [06:32:22] Try running: npm install gulp
> [06:32:22] Using globally installed gulp
> "No inputs were found in config file 'tsconfig.json'. Specified 'include' 
> paths were '[\"src\"]' and 'exclude' paths were '[\"lib/\"]'."
> [06:32:22] Using gulpfile /<>/gulpfile.js
> [06:32:22] Starting 'build'...
> [06:32:22] Starting 'pre-build'...
> [06:32:22] Finished 'pre-build' after 8.19 ms
> [06:32:22] Starting 'buildWithPreBuild'...
> [06:32:22] 'buildWithPreBuild' errored after 967 μs
> [06:32:22] Error: Cannot find module './lib-prebuild'
> Require stack:
> - /<>/gulpfile.js
> - /usr/share/nodejs/gulp-cli/lib/versioned/^4.0.0/index.js
> - /usr/share/nodejs/gulp-cli/index.js
> - /usr/share/nodejs/gulp/bin/gulp.js
> at Function.Module._resolveFilename 
> (internal/modules/cjs/loader.js:815:15)
> at Function.resolve (internal/modules/cjs/helpers.js:80:19)
> at reload (/<>/gulpfile.js:62:22)
> at buildWithPreBuild (/<>/gulpfile.js:28:15)
> at bound (domain.js:427:14)
> at runBound (domain.js:440:12)
> at asyncRunner 
> (/usr/share/nodejs/gulp/node_modules/async-done/index.js:55:18)
> at processTicksAndRejections (internal/process/task_queues.js:79:11)
> [06:32:22] 'build' errored after 11 ms
> make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/node-gulp-tsb_4.0.5+~cs7.0.2-2_unstable.log

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

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

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

Problem was elsewhere and is now fixed--- End Message ---

Bug#1005845: marked as done (raspi-firmware: keep 1.20220120+ds-1 out of testing a bit longer)

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2022 13:18:45 +0100
with message-id <18082961.OrvFop5N7Y@bagend>
and subject line Re: raspi-firmware: keep 1.20220120+ds-1 out of testing a bit 
longer
has caused the Debian Bug report #1005845,
regarding raspi-firmware: keep 1.20220120+ds-1 out of testing a bit longer
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.)


-- 
1005845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: raspi-firmware
Version: 1.20220120+ds-1
Severity: grave

Hi,

This is a 'dummy' RC bug to prevent version 1.20220120+ds-1 from transitioning 
to testing. Just now on IRC we identified a bug which I don't consider RC in 
itself, but the upstream issue tracker indicate various issue with the latest 
firmware, especially https://github.com/raspberrypi/firmware/issues/1688

https://github.com/raspberrypi/firmware/commit/
9c04ed2c1ad06a615d8e6479806ab252dbbeb95a could be a potential fix.

Once we're confident enough that it should work, this bug can be closed so that 
the package can transition to testing.

Cheers,
  Diederik

signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
On 16 Feb 2022 00:16:23 +0100 Diederik de Haas  wrote:
> Package: raspi-firmware
> Version: 1.20220120+ds-1
> Severity: grave
> 
> This is a 'dummy' RC bug to prevent version 1.20220120+ds-1 from
> transitioning to testing.

It looks like I was too late as it did transition to testing, so closing this 
bug again.
The bug I mentioned earlier was bug #1005846 and that bug mentions an upstream 
commit which fixed the reported issue, so a new upstream version should fix 
that.

Cheers,
  Diederik

signature.asc
Description: This is a digitally signed message part.
--- End Message ---

Bug#1003165: scikit-learn in unstable FTBFS on arm64, armel, armhf, i386, ppc64el and s390x

[Christian Kastner]

Hi,

On 2022-02-16 11:57, John Paul Adrian Glaubitz wrote:
> Hello!
> 
> On 2/16/22 11:36, Graham Inggs wrote:
>> Is anyone able to help with the bus error on armhf please?
> 
> Bus errors are normally easy to spot. Just run the code in question through
> GDB and see where it crashes. Then look at the backtrace with the debug
> symbols installed.
> 
> Usually it's a result of bad pointer arithmetics which should definitely be
> fixed as such operations usually violate the C/C++ standards.
> 
> I can have quick look.

one of these errors has been reported in the past, and I already did
some analysis way back then:

https://github.com/scikit-learn/scikit-learn/issues/16443

Check the last comment. The relevant Cython code doesn't look wrong, so
I guess the problem is with the binary result produced during build, as
you point out.

Best,
Christian

Bug#1005755: marked as done (debian/copyright missing GPL-3+ copyright statements)

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2022 11:49:37 +
with message-id 
and subject line Bug#1005755: fixed in gnome-control-center 1:41.4-1
has caused the Debian Bug report #1005755,
regarding debian/copyright missing GPL-3+ copyright statements
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.)


-- 
1005755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-control-center
Version: 1:41.2-2
Severity: serious

Hi,

  gnome-control-center has several files that are stated as GPL-3+ in
their source headers

for example -

panels/applications/search.h
panels/applications/cc-applications-panel.h
panels/network/cc-qr-code.h

In the package, debian/copyright GPL-3+ isn't explicitly stated for these files.

The reason for raising this is that budgie-desktop has forked
gnome-control-center and we have used much of the packaging from
G-C-C.

ftp-master (Thorsten Alteholz) has rejected this package with the reason

"please mention the files licensed under GPL-3+ in your debian/copyright."

I've also stated "serious" since according to this bug-report this is
a Debian policy violation

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005011

thanks

David
--- End Message ---
--- Begin Message ---
Source: gnome-control-center
Source-Version: 1:41.4-1
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gnome-control-center 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 16 Feb 2022 10:54:42 +
Source: gnome-control-center
Architecture: source
Version: 1:41.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1005755
Changes:
 gnome-control-center (1:41.4-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream release
 - Only show network configuration button for active/connecting
   connections
 - Fix error cancelling PPD dialog
 - Translation updates
 - Other changes were already included in 1:41.2-2
   * Drop patches that came from upstream
   * d/copyright: Update
 - Document that some files are now GPL-3+ (Closes: #1005755)
   * Mark a Debian-specific patch as deliberately not forwarded
   * Standards-Version: 4.6.0 (no changes required)
   * Silence some Lintian tags
Checksums-Sha1:
 9d694335f2079f443358403b6150903941e9aab2 3887 gnome-control-center_41.4-1.dsc
 a9c49d3303d7002e3906736456fdb872666b622c 6616908 
gnome-control-center_41.4.orig.tar.xz
 80f289f921a2994e92382dfc85b02464c832a335 41728 
gnome-control-center_41.4-1.debian.tar.xz
 97162227217b60e318c6b0f3443dfb8bb637126e 29987 
gnome-control-center_41.4-1_source.buildinfo
Checksums-Sha256:
 d3f13c143b95ccbebe9a1e0b22f838db6831b642052b248b9bb8e9c6aba64f22 3887 
gnome-control-center_41.4-1.dsc
 d6db0c4cb70857becf48ac5007f12b5f63b9d5d7e80ea7ee57d3be512669f7c9 6616908 
gnome-control-center_41.4.orig.tar.xz
 f99557cff182246bd5a6a541614347d3472076102bbc891a60f9dc3f56f58d89 41728 
gnome-control-center_41.4-1.debian.tar.xz
 8eb29afe797f5c5bfb7fa504042476a9012d314fe72e265a13fee5f74252c3f8 29987 
gnome-control-center_41.4-1_source.buildinfo
Files:
 89faf4ac1a491d5caab5ecc5ca9ced26 3887 gnome optional 
gnome-control-center_41.4-1.dsc
 4543d5dbee3229ce0579afc547679f46 6616908 gnome optional 
gnome-control-center_41.4.orig.tar.xz
 9e41f7fdcbf4deda05c5fb3721d623da 41728 gnome optional 
gnome-control-center_41.4-1.debian.tar.xz
 45bdd70def5836970ead2c8e28a81072 29987 gnome optional 
gnome-control-center_41.4-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmIM314ACgkQ4FrhR4+B
TE8SMBAAr8+V4+CVSPMnXqY8Z1LfLepF2JUVnyUJuSqBaikhsaDB1SDgJd4GMgMM
WOtark81CFOTM6QCfTFnj5OiCZA8uTHnUX6XAVQ26sa5RlYFpBHvHC5KFteHaTFu
N4WANTvwIqpKE+3kyapbIyAUzeQL5Qh15vTViR/LZZUEN/qkvMLhxkD4fkLdb56S
dVQN3VqSIBz2MgWcZNeer/PrxWaKl8Stlo4ckfvJO0aNqRjDqfkD0w5J/pcqExd6
DJm47MNqRdr1YZ

Bug#1005011: Please fix capnproto in unstable as well (Was: Re: Bug#1005011: fixed in capnproto 0.9.1-2)

[Nilesh Patra]

Tony/Tom, Can you do corresponding fixes for unstable too,
or otherwise move experimental release to unstable?

Otherwise this bug is causing a un-warranted-for autorm, for example in 
parsnp[1]

[1]: https://tracker.debian.org/pkg/parsnp

Regards,
Nilesh

On Sat, 12 Feb 2022 16:03:40 + Debian FTP Masters 
 wrote:
> Source: capnproto
> Source-Version: 0.9.1-2
> Done: Tom Lee 
> 
> We believe that the bug you reported is fixed in the latest version of
> capnproto, 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 1005...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Tom Lee  (supplier of updated capnproto 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, 11 Feb 2022 23:13:08 -0800
> Source: capnproto
> Architecture: source
> Version: 0.9.1-2
> Distribution: experimental
> Urgency: medium
> Maintainer: Tom Lee 
> Changed-By: Tom Lee 
> Closes: 1005011 1005066
> Changes:
>  capnproto (0.9.1-2) experimental; urgency=medium
>  .
>* Add libatomic check for armel (Closes: #1005066)
>* Add tests for atomics via kj::AtomicRefcounted
>* Trap EXIT in build-tests
>* Update debian/copyright (Closes: #1005011)
> Checksums-Sha1:
>  048c37bf847a62dd0d5e7b1b7b93c959520c5a38 2208 capnproto_0.9.1-2.dsc
>  bfdfa1f247ec7a1a3d1f751c3b8379dfb23355dd 13348 
> capnproto_0.9.1-2.debian.tar.xz
>  714c942c03d50716259304d49c9e57817dad25a6 8669 
> capnproto_0.9.1-2_amd64.buildinfo
> Checksums-Sha256:
>  7f23faed577bad8c34bf051fad2454a04fd74e32264ee61133fe1f7ebf19a21f 2208 
> capnproto_0.9.1-2.dsc
>  8930e1fa00fd93452c11f190d483f58a89a5fae32cc62125f4dd0ac4f524cca1 13348 
> capnproto_0.9.1-2.debian.tar.xz
>  945b964ec4c8f361fdf097e530fdc4e7ab1bea806a01f62c455166d8e7039483 8669 
> capnproto_0.9.1-2_amd64.buildinfo
> Files:
>  a8e725bc828e9c193685fe116d87c283 2208 devel optional capnproto_0.9.1-2.dsc
>  4afead208a6ef546301ebe02f49bf2d4 13348 devel optional 
> capnproto_0.9.1-2.debian.tar.xz
>  e54174fb36145c15185763525f688d6d 8669 devel optional 
> capnproto_0.9.1-2_amd64.buildinfo
> 
> -BEGIN PGP SIGNATURE-
> 
> iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmIH2BQUHHRtYW5jaWxs
> QGRlYmlhbi5vcmcACgkQIdIFiZdLPpb9NRAAyK/0wM1MBJ0ocb9frgqxRpECNRF4


signature.asc
Description: PGP signature

Processed: Bug#1005755 marked as pending in gnome-control-center

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1005755 [gnome-control-center] debian/copyright missing GPL-3+ copyright 
statements
Added tag(s) pending.

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

Bug#1005755: marked as pending in gnome-control-center

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #1005755 in gnome-control-center 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/gnome-team/gnome-control-center/-/commit/2e7a469a5960232a15785b53eb546dc373355794


d/copyright: Update

- Document that some files are now GPL-3+ (Closes: #1005755)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1005755

Bug#1003165: scikit-learn in unstable FTBFS on arm64, armel, armhf, i386, ppc64el and s390x

[John Paul Adrian Glaubitz]

Hi Christian!

On 2/16/22 12:33, Christian Kastner wrote:
>> Bus errors are normally easy to spot. Just run the code in question through
>> GDB and see where it crashes. Then look at the backtrace with the debug
>> symbols installed.
>>
>> Usually it's a result of bad pointer arithmetics which should definitely be
>> fixed as such operations usually violate the C/C++ standards.
>>
>> I can have quick look.
> 
> one of these errors has been reported in the past, and I already did
> some analysis way back then:
> 
> https://github.com/scikit-learn/scikit-learn/issues/16443
> 
> Check the last comment. The relevant Cython code doesn't look wrong, so
> I guess the problem is with the binary result produced during build, as
> you point out.

I'm happy to look at this issue but first the baseline issue must be fixed
as this is a Debian Policy violation.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#1005518: marked as done (frogr: FTBFS: ../data/meson.build:32:5: ERROR: Function does not take positional arguments.)

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2022 11:18:57 +
with message-id 
and subject line Bug#1005518: fixed in frogr 1.7-1
has caused the Debian Bug report #1005518,
regarding frogr: FTBFS: ../data/meson.build:32:5: ERROR: Function does not take 
positional arguments.
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.)


-- 
1005518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: frogr
Version: 1.6-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: frogr
> Project version: 1.6
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency glib-2.0 found: YES 2.70.3
> Run-time dependency gtk+-3.0 found: YES 3.24.31
> Run-time dependency libsoup-2.4 found: YES 2.74.2
> Run-time dependency libexif found: YES 0.6.24
> Run-time dependency libxml-2.0 found: YES 2.9.12
> Run-time dependency json-glib-1.0 found: YES 1.6.6
> Run-time dependency libgcrypt found: YES 1.9.4
> Run-time dependency gstreamer-1.0 found: YES 1.20.0
> Configuring config.h using configuration
> Configuring org.gnome.frogr.desktop.in using configuration
> 
> ../data/meson.build:32:5: ERROR: Function does not take positional arguments.
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2022-02-12T22:47:15.256185
> Main binary: /usr/bin/python3
> Build Options: -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu 
> -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain 
> -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: frogr
> Project version: 1.6
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now
> Sanity check compile stdout:
> 
> -
> Sanity check compile stderr:
> 
> -
> Running test binary command: 
> /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now
> Sanity check compile stdout:
> 
> -
> Sanity check compile stderr:
> 
> -
> Running test binary command: 
> /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe
> C compiler for the build machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the build machine: cc ld.bfd 2.38
> Build machine cpu family: x86_64
> Build machine cpu: x86_64
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Target machine cpu family: x86_64
> Target machine cpu: x86_64
> Pkg-config binary for 1 is not cached.
> Pkg-config binary missing from cross or native file, or env var undefined.
> Trying a default Pkg-config fallback at pkg-config
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Determining dependency 'glib-2.0' with pkg-config executable 
> '/usr/bin/pkg-config'
> env[PKG_CONFIG_PATH]: 
> Called `/usr/bin/pkg-config --modversion glib-2.0` -> 0
> 2.70.3
> env[PKG_CONFIG_PATH]: 
> Called `/usr/bin/pkg-config --cflags glib-2.0` -> 0
> -I/usr/include/glib-2.0 -I/usr/lib/x86_6

Bug#1003165: scikit-learn in unstable FTBFS on arm64, armel, armhf, i386, ppc64el and s390x

[John Paul Adrian Glaubitz]

HellO!

On 2/16/22 11:57, John Paul Adrian Glaubitz wrote:
> On 2/16/22 11:36, Graham Inggs wrote:
>> Is anyone able to help with the bus error on armhf please?
> 
> Bus errors are normally easy to spot. Just run the code in question through
> GDB and see where it crashes. Then look at the backtrace with the debug
> symbols installed.
> 
> Usually it's a result of bad pointer arithmetics which should definitely be
> fixed as such operations usually violate the C/C++ standards.

So, I have skimmed over the build logs and one of the main issues is the use of
-march flags to enforce a certain baseline [1]:

powerpc64le-linux-gnu-gcc: error: unrecognized command-line option 
‘-march=native’; did you mean ‘-mcpu=native’?

This is a policy violation and must be fixed in any case. Blacklisting 
architectures
is not enough in this case as forcing the baseline of the buildds can lead to 
code
that won't run on the user's machines.

Adrian

> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=scikit-learn&arch=ppc64el&ver=1.0.2-1&stamp=1644956229&raw=0

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#1001595: src:gcc-defaults-mipsen: fails to migrate to testing for too long

[YunQiang Su]

Graham Inggs  于2022年2月16日周三 18:57写道：
>
> Dear MIPS Porters
>
> Could somebody take a look a this issue please?
>

Thank you. I will take care about it.

>
> > Hi YunQiang,
> >
> > On Sun, 12 Dec 2021 21:51:28 +0100 Paul Gevers  wrote:
> > > Your package src:gcc-defaults-mipsen has been trying to
> > > migrate for 62 days [2]. Hence, I am filing this bug.
> >
> > Any progress? It has been 1.5 months and I haven't seen anything
> > happening. This is NOK. gcc-defaults-mipsen is a key package, so I can't
> > just remove it. Please ensure the package can migrate. It seems to me
> > that your failing to build all kind of required packages, although it's
> > not clear if those should come from e.g. gcc-11 (which apparently
> > started to build again itself on mipsel and mips64el. I'm not versed
> > enough in how this piece of toolchain should work. If you need my help
> > as a Release Team member, don't hesitate to reach out, but I don't want
> > to spend time on reverse engineering this *.
> >
> > Paul
>


-- 
YunQiang Su

Bug#1003165: scikit-learn in unstable FTBFS on arm64, armel, armhf, i386, ppc64el and s390x

[John Paul Adrian Glaubitz]

Hello!

On 2/16/22 11:36, Graham Inggs wrote:
> Is anyone able to help with the bus error on armhf please?

Bus errors are normally easy to spot. Just run the code in question through
GDB and see where it crashes. Then look at the backtrace with the debug
symbols installed.

Usually it's a result of bad pointer arithmetics which should definitely be
fixed as such operations usually violate the C/C++ standards.

I can have quick look.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#1004870: python-xarray: autopkgtest regression on s390x

[Graham Inggs]

Hi Rajendra

Thanks for taking a look!

Unfortunately, that cannot be the solution, as that commit is already
present in the version of pandas in the archive [1].

Regards
Graham


[1] 
https://salsa.debian.org/science-team/pandas/-/blob/debian/pandas/core/arrays/datetimelike.py#L462


On Sun, 13 Feb 2022 at 15:14, Rajendra Kharat1  wrote:
>
> Hi Graham,
>
> This issue is again specific to no proper handling for bug endian environment.
>
> There is a fix from pandas library maintainers for this issue.
>
> https://github.com/pandas-dev/pandas/pull/40116
>
> Please find the link above and check if this resolves your issue.
>
> Thanks,
> Rajendra
>
>
> - Original message -
> From: Rajendra Kharat1/India/Contr/IBM
> To: gin...@debian.org, 1004...@bugs.debian.org
> Cc: sub...@bugs.debian.org
> Subject: Re: [EXTERNAL] Bug#1004870: python-xarray: autopkgtest regression on 
> s390x
> Date: Thu, Feb 3, 2022 3:34 PM
>
> We are having a look. Will check and update.
>
> Thanks,
> Rajendra

Bug#1005867: node-sanitize-html: Broken by node-htmlparser2 >=7

[Yadd]

Package: node-sanitize-html
Version: 2.6.1-1
Severity: serious
Justification: ftbfs

node-sanitize-html depends on htmlparser2 6 but Debian/testing has
htmlParser2 >=7. Enabling test proves that package is broken.

Bug#1001595: src:gcc-defaults-mipsen: fails to migrate to testing for too long

[Graham Inggs]

Dear MIPS Porters

Could somebody take a look a this issue please?


> Hi YunQiang,
>
> On Sun, 12 Dec 2021 21:51:28 +0100 Paul Gevers  wrote:
> > Your package src:gcc-defaults-mipsen has been trying to
> > migrate for 62 days [2]. Hence, I am filing this bug.
>
> Any progress? It has been 1.5 months and I haven't seen anything
> happening. This is NOK. gcc-defaults-mipsen is a key package, so I can't
> just remove it. Please ensure the package can migrate. It seems to me
> that your failing to build all kind of required packages, although it's
> not clear if those should come from e.g. gcc-11 (which apparently
> started to build again itself on mipsel and mips64el. I'm not versed
> enough in how this piece of toolchain should work. If you need my help
> as a Release Team member, don't hesitate to reach out, but I don't want
> to spend time on reverse engineering this *.
>
> Paul

Bug#1004855: python3-ipykernel: missing dependency on debugpy

[Jörg-Volker Peetz]

Hi,

in the upstream GitHub of ipykernel there's this advice concerning the
dependency on debugpy:

https://github.com/ipython/ipykernel/pull/767#issuecomment-916913893

  "No, it shouldn't be removed in this repo. If a downstream packager wants
  to split this dependency, it may, but at the same time, it should also make
  sure to patch the package metadata when doing so to remove the dependency
  and satisfy pip check."

Regards,
Jörg.

Bug#1003165: scikit-learn in unstable FTBFS on arm64, armel, armhf, i386, ppc64el and s390x

[Graham Inggs]

Dear Arm Porters

Is anyone able to help with the bus error on armhf please?


On Wed, 16 Feb 2022 at 09:33, Andreas Tille  wrote:
>
> Control: tags -1 upstream
> Control: forwarded -1 
> https://github.com/scikit-learn/scikit-learn/issues/22503
>  also sent another bug report 
> https://github.com/scikit-learn/scikit-learn/issues/22504
>
> Hi,
>
> as I explained to Debian Science list[1] I'd recommend to drop armel and
> armhf architectures.  I checked the build logs and noticed that these
> architectures are failing with "Bus error".  While I subscribe to the
> reasoning that this could be caused by some coding bug which hides
> somewhere and is not detected on other architectures I think we should
> draw some line here.  Obviously we do not have the power to maintain
> this code for all architectures neither do I expect that there is any
> honest user of this code on the said architectures.  So I would simply
> exclude these from the list of architectures.
>
> For the other architectures I opened two different issues upstream:
>
>   Test suite failure for arm64, ppc64el, s390x, ppc64 and risc64[2]
>
> and
>
>   Second build failure for s390x and ppc64[3]
>
> Kind regards
>
>   Andreas.
>
> PS: Volunteers to sort out the Bus error on the 32 bit arm architectures
> are welcome.
>
> [1] https://lists.debian.org/debian-science/2022/02/msg00029.html
> [2] https://github.com/scikit-learn/scikit-learn/issues/22503
> [3] https://github.com/scikit-learn/scikit-learn/issues/22504
>
> --
> http://fam-tille.de

Bug#995242: isc-dhcp-server: omshell returns inconsistent results or segfaults

[Andrea Turbiglio]

Nearly all crashes for omshell happen at an instruction pointer ending with 
...6dc.
Therefore I guess all crashes happen at the same source code location.
Unfortunately with just the segfault line it is difficult to find out this 
source code line.
Therefore the kernel emits one line below the segfault line a line showing the
surrounding bytes of the crashing instruction (at amd64).
Having this line too it is likely possible to find the exact source code line. 
[1]
Example:
 [13092.694183] omshell[11741]: segfault at ...
 [13092.694202] Code: 64 ff ff ff c6 05 15 2f 00 ...
So maybe you could at least retrieve from the log
one "segfault" line with following "Code:" line?
Even better would be to get a backtrace of the crash.
If this system is systemd based, the simplest might be to install 
systemd-coredump.
With this package such a backtrace is written directly to the journal.
Otherwise there are other core-dump-handler available, but the
core has to be analyzed separately.
Kind regards,
Bernhard


Thanks for the reply.

The problem now is that those systems are not available anymore.

I had this issue only on production.
When I was testing Debian 11 with DHCPD on a small testing environment (with 
few dhcp clients) everything was fine.

So to recreate the issue, I should clone one of our 2 DHCPDs (that now are 
running fine from ISC source), remove the source package and reconfigure the 
Debian package version... and then redeploy one of them on production.
And then hope that the other server (the one running with the SRC-pkg version) 
will be able to do all the work, when the other dhcpd will crash because of 
omshell.

I had a snapshot of the servers with the Debian-dhcpd-pkg, kept for testing 
purposes, but I had to delete them for disk space management (I kept them for a 
while, but 6 monts has passed from the issue's opening).

I'll try to recreate a similar environment, but I don't know when I will be 
able to.


Thanks for your support.

Regards

--
__
Andrea Turbiglio
Università degli Studi dell’Insubria
Centro Sistemi Informativi e Comunicazione
Servizio Telecomunicazioni - Gestione Rete Dati di Ateneo

Via Valleggio, 11
22100 - COMO
tel. +39 031 238 9784
fax +39 031 238 9709
webwww.uninsubria.it
mailandrea.turbig...@uninsubria.it
mailnetw...@uninsubria.it