Bug#1011828: marked as done (node-domutils: FTBFS: node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations.)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Fri, 27 May 2022 06:34:09 +
with message-id 
and subject line Bug#1011828: fixed in node-domutils 3.0.1-3
has caused the Debian Bug report #1011828,
regarding node-domutils: FTBFS: node_modules/@types/jest/index.d.ts(503,30): 
error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type 
declarations.
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> Link ./node_modules/htmlparser2 -> /usr/share/nodejs/htmlparser2
> Link ./node_modules/pretty-format -> /usr/share/nodejs/pretty-format
> Link ./node_modules/ts-jest -> /usr/share/nodejs/ts-jest
> Copy /usr/share/nodejs/domhandler -> ./node_modules/
> Copy /usr/share/nodejs/dom-serializer -> ./node_modules/
> Copy /usr/share/nodejs/domelementtype -> ./node_modules/
> Copy /usr/share/nodejs/jest-diff -> ./node_modules/
> Copy /usr/share/nodejs/@types/jest -> ./node_modules/@types
> Copy /usr/share/nodejs/@types/node -> ./node_modules/@types
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> tsc
> node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 
> 'jest-matcher-utils' or its corresponding type declarations.
> make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/node-domutils_3.0.1-2_unstable.log

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

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

If you reassign this bug to another package, please 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-domutils
Source-Version: 3.0.1-3
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-domutils 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, 27 May 2022 08:10:07 +0200
Source: node-domutils
Architecture: source
Version: 3.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1011828
Changes:
 node-domutils (3.0.1-3) unstable; urgency=medium
 .
   * Team upload
   * Declare compliance with policy 4.6.1
   * Fix filenamemangle
   * Update build links (Closes: #1011828)
   * Fix test for jest >= 28
Checksums-Sha1: 
 3e2f9a5214540c6c7f095f2bbc4159c9c2c08029 2227 node-domutils_3.0.1-3.dsc
 f0b9df811a2b81b7c2c83ec5638e48b98a2d58d4 4340 
node-domutils_3.0.1-3.debian.tar.xz
Checksums-Sha256: 
 c688fbeb27ed2c9cecb9e5955540178705f77980825cfd9b385f93f93cef62ee 2227 
node-domutils_3.0.1-3.dsc
 cb6da934d63cb4eef8a4e8e8c20d1cc9455ce5880239df565068c1a49449fa5e 4340 
node-domutils_3.0.1-3.debian.tar.xz
Files: 
 e25da5d7efe0bc18ebb496186af688ea 2227 javascript optional 
node-domutils_3.0.1-3.dsc
 c7751509ee9db5d77070194b7799d82a 4340 javascript optional 
node-domutils_3.0.1-3.debian.tar.xz


Bug#1011817: marked as done (node-rollup-plugin-replace: FTBFS: dh_auto_test: error: cd ./legacy && sh -ex ../debian/nodejs/legacy/test returned exit code 1)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Fri, 27 May 2022 06:34:15 +
with message-id 
and subject line Bug#1011817: fixed in node-rollup-plugin-replace 
3.0.0+ds+~2.2.0-2
has caused the Debian Bug report #1011817,
regarding node-rollup-plugin-replace: FTBFS: dh_auto_test: error: cd ./legacy 
&& sh -ex ../debian/nodejs/legacy/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.)


-- 
1011817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-rollup-plugin-replace
Version: 3.0.0+ds+~2.2.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Build legacy module
> dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/legacy/build
>   cd ./legacy && sh -ex ../debian/nodejs/legacy/build
> + rollup -c
> 
> src/index.js → dist/rollup-plugin-replace.cjs.js, 
> dist/rollup-plugin-replace.es.js...
> (!) Entry module "src/index.js" is implicitly using "default" export 
> mode, which means for CommonJS output that its default export is assigned to 
> "module.exports". For many tools, such CommonJS output will not be 
> interchangeable with the original ES module. If this is intended, explicitly 
> set "output.exports" to either "auto" or "default", otherwise you might want 
> to consider changing the signature of "src/index.js" to use named exports 
> only.
> https://rollupjs.org/guide/en/#outputexports
> src/index.js
> created dist/rollup-plugin-replace.cjs.js, 
> dist/rollup-plugin-replace.es.js in 38ms
> # Build @rollup/plugin-replace
> cd packages/replace; if rollup -c; then \
>   echo "build succeeds"; \
> else \
>   echo "build failed, trying with legacy rollup plugins"; \
>   rollup -c ../../debian/rollup-legacy.config.js; \
> fi
> 
> src/index.js → dist/rollup-plugin-replace.cjs.js, 
> dist/rollup-plugin-replace.es.js...
> created dist/rollup-plugin-replace.cjs.js, 
> dist/rollup-plugin-replace.es.js in 46ms
> build succeeds
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules/\@rollup
>   ln -s ../../packages/replace node_modules/\@rollup/plugin-replace
>   cd ./legacy && sh -ex ../debian/nodejs/legacy/test
> + mocha
> 
> Error: Cannot find module 'locate-character'
> Require stack:
> - /<>/legacy/test/test.js
> at Function.Module._resolveFilename 
> (node:internal/modules/cjs/loader:933:15)
> at Function.Module._load (node:internal/modules/cjs/loader:778:27)
> at Module.require (node:internal/modules/cjs/loader:1005:19)
> at require (node:internal/modules/cjs/helpers:102:18)
> at Object. (/<>/legacy/test/test.js:9:24)
> at Module._compile (node:internal/modules/cjs/loader:1103:14)
> at Object.Module._extensions..js 
> (node:internal/modules/cjs/loader:1157:10)
> at Module.load (node:internal/modules/cjs/loader:981:32)
> at Function.Module._load (node:internal/modules/cjs/loader:822:12)
> at ModuleWrap. (node:internal/modules/esm/translators:161:29)
> at ModuleJob.run (node:internal/modules/esm/module_job:197:25)
> at processTicksAndRejections (node:internal/process/task_queues:96:5)
> at async Promise.all (index 0)
> at async ESMLoader.import (node:internal/modules/esm/loader:337:24)
> at async importModuleDynamicallyWrapper (node:internal/vm/module:437:15)
> at async formattedImport 
> (/usr/share/nodejs/mocha/lib/nodejs/esm-utils.js:7:14)
> at async Object.exports.requireOrImport 
> (/usr/share/nodejs/mocha/lib/nodejs/esm-utils.js:48:32)
> at async Object.exports.loadFilesAsync 
> (/usr/share/nodejs/mocha/lib/nodejs/esm-utils.js:103:20)
> at async singleRun (/usr/share/nodejs/mocha/lib/cli/run-helpers.js:125:3)
> at async Object.exports.handler 
> (/usr/share/nodejs/mocha/lib/cli/run.js:374:5)
> dh_auto_test: error: cd ./legacy && sh -ex ../debian/nodejs/legacy/test 
> returned exit code 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/node-rollup-plugin-replace_3.0.0+ds+~2.2.0-1_unstable.log

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

Processed: tagging 958853, tagging 1011900, tagging 1011875, tagging 1011869, tagging 1011816, tagging 1011811 ...

2022-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 958853 + sid bookworm
Bug #958853 [anki] anki: old version beginning to fail with newer Python 
releases
Bug #965258 [anki] anki: old version beginning to fail with newer Python 
releases
Added tag(s) bookworm and sid.
Added tag(s) sid and bookworm.
> tags 1011900 + experimental
Bug #1011900 [src:monkeysphere] monkeysphere: FTBFS: ...Could not chdir to home 
directory /home/user42: No such file or directory
Added tag(s) experimental.
> tags 1011875 - sid bookworm
Bug #1011875 [src:golang-github-opencontainers-runtime-tools] 
golang-github-opencontainers-runtime-tools: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
github.com/opencontainers/runtime-tools/api/socket 
github.com/opencontainers/runtime-tools/cgroups 
github.com/opencontainers/runtime-tools/error 
github.com/opencontainers/runtime-tools/filepath 
github.com/opencontainers/runtime-tools/generate 
github.com/opencontainers/runtime-tools/generate/seccomp 
github.com/opencontainers/runtime-tools/specerror 
github.com/opencontainers/runtime-tools/validate returned exit code 1
Removed tag(s) bookworm and sid.
> tags 1011869 - sid bookworm
Bug #1011869 [src:golang-github-containers-buildah] 
golang-github-containers-buildah: FTBFS: make[1]: *** [debian/rules:26: 
override_dh_auto_build] Error 25
Removed tag(s) bookworm and sid.
> tags 1011816 - sid bookworm
Bug #1011816 [src:node-terser] node-terser: FTBFS: undefined Should print 
supported options on invalid option syntax (264ms)
Removed tag(s) bookworm and sid.
> tags 1011811 - sid bookworm
Bug #1011811 [src:libpod] libpod: FTBFS: make[1]: *** [debian/rules:29: 
override_dh_auto_build] Error 25
Removed tag(s) bookworm and sid.
> severity 1011743 normal
Bug #1011743 [open-vm-tools] Please rebase open-vm-tools to release 12.0.5 on 
supported Debian releases 
Severity set to 'normal' from 'serious'
> merge 1011633 1011743
Bug #1011633 [open-vm-tools] Open-vm-tools 12.0.0 has been released
Bug #1011743 [open-vm-tools] Please rebase open-vm-tools to release 12.0.5 on 
supported Debian releases 
Merged 1011633 1011743
> reassign 1011633 src:open-vm-tools 2:12.0.0-1
Bug #1011633 [open-vm-tools] Open-vm-tools 12.0.0 has been released
Bug #1011743 [open-vm-tools] Please rebase open-vm-tools to release 12.0.5 on 
supported Debian releases 
Bug reassigned from package 'open-vm-tools' to 'src:open-vm-tools'.
Bug reassigned from package 'open-vm-tools' to 'src:open-vm-tools'.
No longer marked as found in versions 12.0.5.
No longer marked as found in versions 12.0.5.
Ignoring request to alter fixed versions of bug #1011633 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1011743 to the same values 
previously set
Bug #1011633 [src:open-vm-tools] Open-vm-tools 12.0.0 has been released
Bug #1011743 [src:open-vm-tools] Please rebase open-vm-tools to release 12.0.5 
on supported Debian releases 
Marked as found in versions open-vm-tools/2:12.0.0-1.
Marked as found in versions open-vm-tools/2:12.0.0-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1011633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011633
1011743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011743
1011811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011811
1011816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011816
1011869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011869
1011875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011875
1011900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011900
958853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958853
965258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Bug#1011817 marked as pending in node-rollup-plugin-replace

2022-05-26 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1011817 [src:node-rollup-plugin-replace] node-rollup-plugin-replace: 
FTBFS: dh_auto_test: error: cd ./legacy && sh -ex ../debian/nodejs/legacy/test 
returned exit code 1
Added tag(s) pending.

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



Bug#1011817: marked as pending in node-rollup-plugin-replace

2022-05-26 Thread Yadd
Control: tag -1 pending

Hello,

Bug #1011817 in node-rollup-plugin-replace 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-rollup-plugin-replace/-/commit/1812b352a6179fbeb3c06f17fd6d02eab20b1286


Add missing test dependency to node-locate-character

Closes: #1011817


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011817



Bug#1011871: marked as done (node-rollup-pluginutils: FTBFS: dh_auto_test: error: /bin/sh -ex debian/nodejs/test returned exit code 1)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Fri, 27 May 2022 06:18:48 +
with message-id 
and subject line Bug#1011871: fixed in node-rollup-pluginutils 4.2.1~ds+~2.8.2-3
has caused the Debian Bug report #1011871,
regarding node-rollup-pluginutils: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/nodejs/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.)


-- 
1011871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011871
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-rollup-pluginutils
Version: 4.2.1~ds+~2.8.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Build legacy module
> dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/legacy/build
>   cd ./legacy && sh -ex ../debian/nodejs/legacy/build
> + rollup -c
> 
> src/index.ts → dist/pluginutils.cjs.js, 
> dist/pluginutils.es.js...
> (!) Unresolved dependencies
> https://rollupjs.org/guide/en/#warning-treating-module-as-external-dependency
> micromatch (imported by src/createFilter.ts)
> created dist/pluginutils.cjs.js, dist/pluginutils.es.js in 
> 398ms
> + cp src/pluginutils.d.ts dist/pluginutils.d.ts
> # Build @rollup/pluginutils
> cd packages/pluginutils; if rollup -c; then \
>   echo "build succeeds"; \
> else \
>   echo "build failed, trying with legacy rollup plugins"; \
>   rollup -c ../../debian/rollup-legacy.config.js; \
> fi
> 
> src/index.ts → ./dist/cjs/index.js, 
> ./dist/es/index.js...
> (!) Plugin typescript: @rollup/plugin-typescript TS2307: Cannot find 
> module 'estree-walker' or its corresponding type declarations.
> src/attachScopes.ts: (4:22)
> 
> 4 import { walk } from 'estree-walker';
>    ~~~
> 
> (!) Plugin typescript: @rollup/plugin-typescript TS7006: Parameter 
> 'n' implicitly has an 'any' type.
> src/attachScopes.ts: (66:11)
> 
> 66 enter(n, parent) {
>      ~
> 
> src/attachScopes.ts: (135:11)
> 
> 135 leave(n) {
>       ~
> 
> (!) Plugin typescript: @rollup/plugin-typescript TS7006: Parameter 
> 'parent' implicitly has an 'any' type.
> src/attachScopes.ts: (66:14)
> 
> 66 enter(n, parent) {
>     ~~
> 
> (!) Plugin typescript: @rollup/plugin-typescript: Rollup 'sourcemap' 
> option must be set to generate source maps.
> (!) Unresolved dependencies
> https://rollupjs.org/guide/en/#warning-treating-module-as-external-dependency
> estree-walker (imported by src/attachScopes.ts)
> created ./dist/cjs/index.js, ./dist/es/index.js in 
> 1.2s
> build succeeds
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules/\@rollup
>   ln -s ../../packages/pluginutils node_modules/\@rollup/pluginutils
>   cd ./legacy && sh -ex ../debian/nodejs/legacy/test
> + ls test/addExtension.test.ts test/attachScopes.test.ts 
> test/createFilter.test.ts test/dataToEsm.test.ts 
> test/extractAssignedNames.test.ts test/makeLegalIdentifier.test.ts
> + grep -v attachScopes
> + grep -v createFilter
> + mocha test/addExtension.test.ts test/dataToEsm.test.ts 
> test/extractAssignedNames.test.ts test/makeLegalIdentifier.test.ts
> 
> 
>   addExtension
> undefined adds .js to an ID without an extension
> undefined ignores file with existing extension
> undefined ignores file with trailing dot
> undefined ignores leading .
> undefined adds a custom extension
> 
>   dataToEsm
> undefined outputs treeshakeable data
> undefined handles illegal identifiers, object shorthand, preferConst
> undefined supports non-JSON data
> undefined supports a compact argument
> undefined supports nested objects
> undefined supports nested arrays
> undefined serializes null
> undefined supports default only
> undefined exports default only for arrays
> undefined exports default only for null
> undefined exports default only for primitive values
> undefined supports empty

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

2022-05-26 Thread Debian Bug Tracking System
Your message dated Fri, 27 May 2022 06:18:52 +
with message-id 
and subject line Bug#1011812: fixed in node-worker-loader 3.0.8-2
has caused the Debian Bug report #1011812,
regarding node-worker-loader: 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.)


-- 
1011812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-worker-loader
Version: 3.0.8-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> babeljs src -d dist --ignore 'src/**/*.test.js' --copy-files
> Successfully compiled 6 files with Babel (620ms).
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/worker-loader
>   /bin/sh -ex debian/tests/pkg-js/test
> + NODE_ENV=test jest -u --ci test/sourceMapperRegexp.test.js test/cjs.test.js
> ● Multiple configurations found:
> 
> * /<>/jest.config.js
> * `jest` key in /<>/package.json
> 
>   Implicit config resolution does not allow multiple configuration files.
>   Either remove unused config files or select one explicitly with `--config`.
> 
>   Configuration Documentation:
>   https://jestjs.io/docs/configuration
> 
> 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/05/25/node-worker-loader_3.0.8-1_unstable.log

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

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

If you reassign this bug to another package, please 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-worker-loader
Source-Version: 3.0.8-2
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-worker-loader 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, 27 May 2022 07:52:13 +0200
Source: node-worker-loader
Architecture: source
Version: 3.0.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1011812
Changes:
 node-worker-loader (3.0.8-2) unstable; urgency=medium
 .
   * Team upload
   * Declare compliance with policy 4.6.1
   * Fix test: double jest configuration no more allowed (Closes: #1011812)
Checksums-Sha1: 
 82ad0160c961064103ce7073d7d8321615055c83 2194 node-worker-loader_3.0.8-2.dsc
 0ae81424b520a2e6b67cc75dd310cf60d7207dc2 3080 
node-worker-loader_3.0.8-2.debian.tar.xz
Checksums-Sha256: 
 a006511bc32dec204ef4b49ab72dc30c5b772bd547daeab065bef5ddc51f69c3 2194 
node-worker-loader_3.0.8-2.dsc
 64e1a14d1d09e1d0f27b650deb1a822d12b539349950cea509bebf41cbf19563 3080 
node-worker-loader_3.0.8-2.debian.tar.xz
Files: 
 cfdc04bd5353a2e57f1634607e312236 2194 javascript optional 
node-worker-loader_3.0.8-2.dsc
 f0305705e5cdc3af16572970d8133f76 3080 javascript optional 
node-worker-loader_3.0.8-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmKQZ74ACgkQ9tdMp8mZ
7um48g//VluMBIQ/jCCvpAq7PnwRh3

Processed: reassign 1007203 to src:php-symfony-polyfill, forcibly merging 1011786 1011786

2022-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1007203 src:php-symfony-polyfill
Bug #1007203 [php-symfony-polyfill] php-symfony-polyfill: Package FTBFS with 
libicu70
Bug reassigned from package 'php-symfony-polyfill' to 
'src:php-symfony-polyfill'.
Ignoring request to alter found versions of bug #1007203 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1007203 to the same values 
previously set
> forcemerge 1011786 1011786
Bug #1011786 [src:php-symfony-polyfill] php-symfony-polyfill: FTBFS: make[1]: 
*** [debian/rules:53: override_dh_auto_test] Error 1
Merged 1011786
> thanks
Stopping processing here.

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



Bug#1011871: marked as pending in node-rollup-pluginutils

2022-05-26 Thread Yadd
Control: tag -1 pending

Hello,

Bug #1011871 in node-rollup-pluginutils 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-rollup-pluginutils/-/commit/6b8809a0525e121b7a0e88ea2c3ee3206ab9f8c4


Link estree-walker for build

Closes: #1011871


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011871



Processed: Bug#1011871 marked as pending in node-rollup-pluginutils

2022-05-26 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1011871 [src:node-rollup-pluginutils] node-rollup-pluginutils: FTBFS: 
dh_auto_test: error: /bin/sh -ex debian/nodejs/test returned exit code 1
Added tag(s) pending.

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



Bug#1011894: marked as done (node-y18n: FTBFS: make[1]: *** [debian/rules:12: override_dh_auto_build] Error 1)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Fri, 27 May 2022 06:03:55 +
with message-id 
and subject line Bug#1011894: fixed in node-y18n 5.0.8+~5.0.0-2
has caused the Debian Bug report #1011894,
regarding node-y18n: FTBFS: make[1]: *** [debian/rules:12: 
override_dh_auto_build] Error 1
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> tsc
> rollup -c
> [!] Error: Cannot find module '@rollup/pluginutils'
> Require stack:
> - 
> /<>/debian/build_modules/@wessberg/rollup-plugin-ts/dist/cjs/index.js
> - /<>/rollup.config.js
> - /usr/share/nodejs/rollup/dist/shared/loadConfigFile.js
> - /usr/share/nodejs/rollup/dist/bin/rollup
> Error: Cannot find module '@rollup/pluginutils'
> Require stack:
> - 
> /<>/debian/build_modules/@wessberg/rollup-plugin-ts/dist/cjs/index.js
> - /<>/rollup.config.js
> - /usr/share/nodejs/rollup/dist/shared/loadConfigFile.js
> - /usr/share/nodejs/rollup/dist/bin/rollup
> at Function.Module._resolveFilename 
> (node:internal/modules/cjs/loader:933:15)
> at Function.Module._load (node:internal/modules/cjs/loader:778:27)
> at Module.require (node:internal/modules/cjs/loader:1005:19)
> at require (node:internal/modules/cjs/helpers:102:18)
> at Object. 
> (/<>/debian/build_modules/@wessberg/rollup-plugin-ts/dist/cjs/index.js:15:19)
> at Module._compile (node:internal/modules/cjs/loader:1103:14)
> at Module._extensions..js (node:internal/modules/cjs/loader:1157:10)
> at Object.require.extensions. [as .js] 
> (/usr/share/nodejs/rollup/dist/shared/loadConfigFile.js:617:17)
> at Module.load (node:internal/modules/cjs/loader:981:32)
> at Function.Module._load (node:internal/modules/cjs/loader:822:12)
> 
> make[1]: *** [debian/rules:12: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/node-y18n_5.0.8+~5.0.0-1_unstable.log

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

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

If you reassign this bug to another package, please 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-y18n
Source-Version: 5.0.8+~5.0.0-2
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-y18n 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, 27 May 2022 07:47:24 +0200
Source: node-y18n
Architecture: source
Version: 5.0.8+~5.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1011894
Changes:
 node-y18n (5.0.8+~5.0.0-2) unstable; urgency=medium
 .
   * Team upload
   * Declare compliance with policy 4.6.1
   * Fix build dependencies (Closes: #1011894)
Checksums-Sha1: 
 6e8f55eae1de9b348ad55f1ec129486616083843 2497 node-y18n_5.0.8+~5.0.0-2.dsc
 2a50048fcd284db73974970c5eb4d41bbd78958b 84432 
node-y18n_5.0.8+~5.0.0-2.debian.tar.xz
Checksums-

Bug#989409: nss-pam-ldapd's autopkgtest fails with OpenLDAP 2.5

2022-05-26 Thread Petter Reinholdtsen
[Salvatore Bonaccorso 2022-04-25]
> Are there any news on this bug? nss-pam-ldapd is currently hinted for
> removal from testing due to this bug (not happened yet though).

Today the debian-fbx and kwartz-client packages was removed from testing
because they depend on nss-pam-ldapd, due to the latters RC issue.  Any
hope to have a fixed version of nss-pam-ldapd in unstable soon?
-- 
Happy hacking
Petter Reinholdtsen



Bug#1011824: marked as done (vega.js: FTBFS: make[1]: *** [debian/rules:12: override_dh_auto_build] Error 1)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Fri, 27 May 2022 05:34:04 +
with message-id 
and subject line Bug#1011824: fixed in vega.js 5.22.1+ds+~3.1.0-2
has caused the Debian Bug report #1011824,
regarding vega.js: FTBFS: make[1]: *** [debian/rules:12: 
override_dh_auto_build] Error 1
to be marked as done.

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

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


-- 
1011824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vega.js
Version: 5.22.1+ds+~3.1.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build --buildsystem=nodejs
> ./lerna.json found
> 
> workspaces field found in package.json
> 
> Found debian/nodejs/topojson-client/build
>   cd ./topojson-client && sh -ex ../debian/nodejs/topojson-client/build
> + rollup -c
> 
> src/index.js → dist/topojson-client.js...
> created dist/topojson-client.js in 167ms
> 
> src/index.js → dist/topojson-client.min.js...
> created dist/topojson-client.min.js in 736ms
> No build command found, searching known files
> No build command found, searching known files
> set -e; \
> for PAC in `pkgjs-utils components_list 2>/dev/null`; do \
>   CMD=`pkgjs-pjson $PAC scripts build`; \
>   if test "$CMD" != ""; then \
>   (cd $PAC ln -s ../../node_modules && $CMD); \
>   fi; \
> done
> [!] Error: Cannot find module 'pretty-bytes'
> Require stack:
> - /<>/debian/build_modules/maxmin/index.js
> - /<>/debian/build_modules/rollup-plugin-bundle-size/index.js
> - /<>/packages/vega-canvas/rollup.config.js
> - /usr/share/nodejs/rollup/dist/shared/loadConfigFile.js
> - /usr/share/nodejs/rollup/dist/bin/rollup
> Error: Cannot find module 'pretty-bytes'
> Require stack:
> - /<>/debian/build_modules/maxmin/index.js
> - /<>/debian/build_modules/rollup-plugin-bundle-size/index.js
> - /<>/packages/vega-canvas/rollup.config.js
> - /usr/share/nodejs/rollup/dist/shared/loadConfigFile.js
> - /usr/share/nodejs/rollup/dist/bin/rollup
> at Function.Module._resolveFilename 
> (node:internal/modules/cjs/loader:933:15)
> at Function.Module._load (node:internal/modules/cjs/loader:778:27)
> at Module.require (node:internal/modules/cjs/loader:1005:19)
> at require (node:internal/modules/cjs/helpers:102:18)
> at Object. 
> (/<>/debian/build_modules/maxmin/index.js:3:19)
> at Module._compile (node:internal/modules/cjs/loader:1103:14)
> at Module._extensions..js (node:internal/modules/cjs/loader:1157:10)
> at Object.require.extensions. [as .js] 
> (/usr/share/nodejs/rollup/dist/shared/loadConfigFile.js:617:17)
> at Module.load (node:internal/modules/cjs/loader:981:32)
> at Function.Module._load (node:internal/modules/cjs/loader:822:12)
> 
> make[1]: *** [debian/rules:12: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/vega.js_5.22.1+ds+~3.1.0-1_unstable.log

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

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

If you reassign this bug to another package, please 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: vega.js
Source-Version: 5.22.1+ds+~3.1.0-2
Done: Yadd 

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

De

Bug#1011833: marked as done (node-yargs: FTBFS: make: *** [debian/rules:8: binary] Error 1)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Fri, 27 May 2022 05:33:50 +
with message-id 
and subject line Bug#1011833: fixed in node-yargs 16.2.0+~16.0.4-3
has caused the Debian Bug report #1011833,
regarding node-yargs: FTBFS: make: *** [debian/rules:8: binary] Error 1
to be marked as done.

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

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


-- 
1011833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-yargs
Version: 16.2.0+~16.0.4-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node
> Not found
> ### @types/yargs-parser is required by debian/nodejs/./extlinks but not 
> available
> # Typescript definition detected, Fallback to main module
> Not found
> ### yargs-parser isn't available too
> make: *** [debian/rules:8: binary] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/node-yargs_16.2.0+~16.0.4-2_unstable.log

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

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

If you reassign this bug to another package, please 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-yargs
Source-Version: 16.2.0+~16.0.4-3
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-yargs 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, 27 May 2022 07:19:25 +0200
Source: node-yargs
Built-For-Profiles: nocheck
Architecture: source
Version: 16.2.0+~16.0.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1011833
Changes:
 node-yargs (16.2.0+~16.0.4-3) unstable; urgency=medium
 .
   * Team upload
   * Fix build dependencies (Closes: #1011833)
Checksums-Sha1: 
 3e91377fc4a257703dcade6bec7de8f158fe9dbf 2586 node-yargs_16.2.0+~16.0.4-3.dsc
 16243a1c564f2e55634b64e7ce67a846c1dda8de 112992 
node-yargs_16.2.0+~16.0.4-3.debian.tar.xz
Checksums-Sha256: 
 359696200fff590ea3e3e860052abfa17c139d4bd763f00ae438c6c9723ebdab 2586 
node-yargs_16.2.0+~16.0.4-3.dsc
 41ae91a051e45171e1e4a94ab80f24f75f5ac564bc39baa3dd3a7b3ce6bbd1c0 112992 
node-yargs_16.2.0+~16.0.4-3.debian.tar.xz
Files: 
 22366f5e78f5fb0752c3b220a3b14a1d 2586 javascript optional 
node-yargs_16.2.0+~16.0.4-3.dsc
 cfcd7bd98fb918ef176d7853084cf28a 112992 javascript optional 
node-yargs_16.2.0+~16.0.4-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmKQYHcACgkQ9tdMp8mZ
7ultaQ/7Bch1q1w2KW6hN686sMs6okJSb1RS+ABj3ozl9vfDSPm+bkzxYdn390Mb
zazZZZvviTx09IQgygIdvlWs+bWr34Iiav853CkcYGdGZw/VDEkRK27RWvS7WDQE
b7MkYus0GF6OyjA3hP7SSZFhHrBPS4JT9nugdJ09H1gnCzmscgQlQ81DC0OUOw1C
E+2ddm6XXr7lG79spUWd3xMmEzIcgkAyap/se9v7/lzQYlmFjK0/3CbqE56VTwaU
t+WWR2eprqmRkYEq9cqLmpcohWDHraf4/SQZswJxNBpp2dOBGwpZ5hSrBlQhiEwm
Vr53BVo/Obt8f7kgzWjc3+AAQOhWNq5iHodzK4cC3R9u7WKmxtmR6rMrSsB01ocE
trLRmt4YX13lQ7XpEgnmLFM1PmBiA7JpsHraoi6kpOm6waTLNTR0rb7hxZJJDIhu
AMdy92MwWBenaASEeCAVoP4R3+Q1a1LJPYBwBoHGdVrwPQHPMOMFs2L4JYZ

Processed: Bug#1011828 marked as pending in node-domutils

2022-05-26 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1011828 [src:node-domutils] node-domutils: FTBFS: 
node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 
'jest-matcher-utils' or its corresponding type declarations.
Added tag(s) pending.

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



Bug#1011828: marked as pending in node-domutils

2022-05-26 Thread Yadd
Control: tag -1 pending

Hello,

Bug #1011828 in node-domutils 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-domutils/-/commit/93bd996dbfd035cb51e18fe245c90dd3873570a5


Update build links

Closes: #1011828


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011828



Processed: Bug#1011833 marked as pending in node-yargs

2022-05-26 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1011833 [src:node-yargs] node-yargs: FTBFS: make: *** [debian/rules:8: 
binary] Error 1
Added tag(s) pending.

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



Bug#1011833: marked as pending in node-yargs

2022-05-26 Thread Yadd
Control: tag -1 pending

Hello,

Bug #1011833 in node-yargs 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-yargs/-/commit/5ac04fb72cf829e0edbe1d861adeac37ef953a62


Fix build dependencies

Closes: #1011833


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011833



Bug#1011792: marked as done (ts-node: FTBFS: make[1]: *** [debian/rules:7: override_dh_auto_build] Error 2)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Fri, 27 May 2022 05:18:54 +
with message-id 
and subject line Bug#1011792: fixed in ts-node 10.7.0+~cs7.0.20-3
has caused the Debian Bug report #1011792,
regarding ts-node: FTBFS: make[1]: *** [debian/rules:7: override_dh_auto_build] 
Error 2
to be marked as done.

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

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


-- 
1011792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011792
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ts-node
Version: 10.7.0+~cs7.0.20-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> tsc
> src/child/spawn-child.ts(49,18): error TS2345: Argument of type 'number | 
> undefined' is not assignable to parameter of type 'number'.
>   Type 'undefined' is not assignable to type 'number'.
> make[1]: *** [debian/rules:7: override_dh_auto_build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/ts-node_10.7.0+~cs7.0.20-2_unstable.log

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

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

If you reassign this bug to another package, please 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: ts-node
Source-Version: 10.7.0+~cs7.0.20-3
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated ts-node 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, 27 May 2022 06:44:46 +0200
Source: ts-node
Built-For-Profiles: nocheck
Architecture: source
Version: 10.7.0+~cs7.0.20-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1011792
Changes:
 ts-node (10.7.0+~cs7.0.20-3) unstable; urgency=medium
 .
   * Team upload
   * Declare compliance with policy 4.6.1
   * Update tsc workarounds (Closes: #1011792)
Checksums-Sha1: 
 a4cada1e62655fbeba9129522373ee7de7ca5e34 4178 ts-node_10.7.0+~cs7.0.20-3.dsc
 436f5a8343fc5b0a311d5b464a2621460966cfb2 45496 
ts-node_10.7.0+~cs7.0.20-3.debian.tar.xz
Checksums-Sha256: 
 5771ae0aaa9376c2d80ad06e17b1d7b1ba0320bfa41dbbdc6dd985ea01bc1226 4178 
ts-node_10.7.0+~cs7.0.20-3.dsc
 16552155cb24606f98e9552e1c4d95b06a67f6de94f03bc91ca03170ae59c858 45496 
ts-node_10.7.0+~cs7.0.20-3.debian.tar.xz
Files: 
 64ea41800fbf1078721ef38fa4cd1592 4178 javascript optional 
ts-node_10.7.0+~cs7.0.20-3.dsc
 8a8bb95c6f04cde66ad05a80a5b10108 45496 javascript optional 
ts-node_10.7.0+~cs7.0.20-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmKQXCQACgkQ9tdMp8mZ
7unYpA/+L4vWCV95qAcNh8YXQ4G6iN/NH5TpTUXXtd5BSn8sMF7J6KijWynYiKwc
XPEDst5yF+fnkCbORuMpAXlRtUT6q0LYaJeSdahEtfAjA/PMmCjcK2OGixFEU3n3
k2vw7xQtnQqFok+SVDR3dGap7AJmh1f8ooQQJSzUhyz9Hs4pvgxV90NH+SOA0pCC
aW5FDDQY59N+Chl+um3iY2pwg62glEJ9N4SnGQbYruFD8/ynEIC04ZRQtbPiRxWL
PJPv2ReouzyfUJA7wh/iny/alORHGg+2MGoUPupfoSSAo73sJrQVoNvvZhU018rg
i4Emz5QnnrP9TteC73Z7T9c02ZltvHQRty58UkpoJWMWpkAxv1oMMrWP0W6Fq9zU
CpCVMoo+PmPKwbE0J4OwKGjRoguhl8MWDi57oeROf7ePsXTqMbTRgjZD51r5UG/I
PBySSZIzH517zbO42w5L9eyooH0PZQYAbCw3XThZX1ejb8ydmc6/pc7UK/fE+WYe
kuhLySxZ/QDCmgn5znXBd7JwIp+msV4oHubgTALO0ptD353OZ8scEonIDqmnoD+Y
0bolqfOYTaeChCMubD++Ly3/qoOoIsVbnLCcc7Fkk

Processed: Bug#1011792 marked as pending in ts-node

2022-05-26 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1011792 [src:ts-node] ts-node: FTBFS: make[1]: *** [debian/rules:7: 
override_dh_auto_build] Error 2
Added tag(s) pending.

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



Bug#1011792: marked as pending in ts-node

2022-05-26 Thread Yadd
Control: tag -1 pending

Hello,

Bug #1011792 in ts-node 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/ts-node/-/commit/4893ae65e290914f25fcda6abb5d3d9f990455d7


Update tsc workarounds

Closes: #1011792


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011792



Bug#1011863: guix: FTBFS: tests fail

2022-05-26 Thread Vagrant Cascadian
On 2022-05-26, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Thanks for doing the rebuild testing!


> Relevant part (hopefully):

Would it be at all possible to update your script to compress and attach
data over a certain size? This was well over 5 lines long, the vast
majority of which were actually tests that passed! It crashes and/or
hangs my mail client when I try to open the original mail in this bug
report, so it really is a practical problem for me!

I've manually trimmed the log to only include the actual failures:

>> PASS: tests/channels.scm - latest-channel-instances, missing introduction 
>> for 'guix' 
>> FAIL: tests/channels.scm - authenticate-channel, wrong first commit signer 
>> FAIL: tests/channels.scm - authenticate-channel, .guix-authorizations 
>> FAIL: tests/channels.scm - latest-channel-instances, authenticate dependency 
>> PASS: tests/combinators.scm - fold2, 1 list 
...
>> PASS: tests/git-authenticate.scm - unsigned commits 
>> FAIL: tests/git-authenticate.scm - signed commits, SHA1 signature 
>> FAIL: tests/git-authenticate.scm - signed commits, default authorizations 
>> FAIL: tests/git-authenticate.scm - signed commits, .guix-authorizations 
>> FAIL: tests/git-authenticate.scm - signed commits, .guix-authorizations, 
>> unauthorized merge 
>> FAIL: tests/git-authenticate.scm - signed commits, .guix-authorizations, 
>> authorized merge 
>> FAIL: tests/git-authenticate.scm - signed commits, .guix-authorizations 
>> removed 
>> PASS: tests/glob.scm - string->sglob, "foo" 
...
>> test-name: authenticate-channel, wrong first commit signer
>> location: /<>/tests/channels.scm:433
>> source:
>> + (test-equal
>> +   "authenticate-channel, wrong first commit signer"
>> +   #t
>> +   (with-fresh-gnupg-setup
>> + (list %ed25519-public-key-file
>> +   %ed25519-secret-key-file
>> +   %ed25519bis-public-key-file
>> +   %ed25519bis-secret-key-file)
>> + (with-temporary-git-repository
>> +   directory
>> +   `((add ".guix-channel"
>> +  ,(object->string
>> + '(channel
>> +(version 0)
>> +(keyring-reference "master"
>> + (add ".guix-authorizations"
>> +  ,(object->string
>> + `(authorizations
>> +(version 0)
>> +((,(key-fingerprint %ed25519-public-key-file)
>> +  (name "Charlie"))
>> + (add "signer.key"
>> +  ,(call-with-input-file
>> + %ed25519-public-key-file
>> + get-string-all))
>> + (commit
>> +   "first commit"
>> +   (signer
>> + ,(key-fingerprint %ed25519-public-key-file)))
>> + (add "random" ,(random-text))
>> + (commit
>> +   "second commit"
>> +   (signer
>> + ,(key-fingerprint %ed25519-public-key-file
>> +   (with-repository
>> + directory
>> + repository
>> + (let* ((commit1 (find-commit repository "first"))
>> +(commit2 (find-commit repository "second"))
>> +(intro (make-channel-introduction
>> + (commit-id-string commit1)
>> + (openpgp-public-key-fingerprint
>> +   (read-openpgp-packet
>> + %ed25519bis-public-key-file
>> +(channel
>> +  (channel
>> +(name 'example)
>> +(url (string-append "file://" directory))
>> +(introduction intro
>> +   (guard (c ((formatted-message? c)
>> +  (and (string-contains
>> + (formatted-message-string c)
>> + "initial commit")
>> +   (equal?
>> + (formatted-message-arguments c)
>> + (list (oid->string (commit-id commit1))
>> +   (key-fingerprint 
>> %ed25519-public-key-file)
>> +   (key-fingerprint
>> + %ed25519bis-public-key-file))
>> +  (authenticate-channel
>> +channel
>> +directory
>> +(commit-id-string commit2)
>> +#:keyring-reference-prefix
>> +"")
>> +  'failed))
>> expected-value: #t
>> actual-value: #f
>> actual-error:
>> + (%exception
>> +   #<&invoke-error program: "git" arguments: ("-C" 
>> "/tmp/guix-directory.cVtbFn" "commit" "-m" "first commit" "--gpg-sign=44D3 
>> 1E21 AF71 38F9 B632  280A 771F 49CB FAAE 072D") exit-status: 128 
>> term-signal: #f stop-signal: #f>)
>> result: FAIL
>> 
>> test-name: authenticate-channel, .guix-authorizations
>> location: /<>/tests/channels.scm:

Processed: Bug#1011824 marked as pending in vega.js

2022-05-26 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1011824 [src:vega.js] vega.js: FTBFS: make[1]: *** [debian/rules:12: 
override_dh_auto_build] Error 1
Added tag(s) pending.

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



Bug#1011824: marked as pending in vega.js

2022-05-26 Thread Yadd
Control: tag -1 pending

Hello,

Bug #1011824 in vega.js 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/vega.js/-/commit/44761582d96acbe46fbb9c5d24a39335a1d73dc8


Add missing build dependency to node-pretty-bytes

Closes: #1011824


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011824



Processed (with 1 error): block 929165 with 985212

2022-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 929165 with 985212
Bug #929165 [ubuntu-keyring] ubuntu-keyring removes configuration files without 
checking
No valid blocking bug(s) given; not doing anything
Failed to set blocking bugs of 929165: Unknown/archived blocking bug(s):985212.

> thanks
Stopping processing here.

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



Bug#1011769: marked as done (cups: CVE-2022-26691: authorization bypass when using "local" authorization)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 May 2022 23:32:06 + (UTC)
with message-id 

and subject line Bug#1011769: fixed in cups 2.4.2-1
has caused the Debian Bug report #1011769,
regarding cups: CVE-2022-26691: authorization bypass when using "local" 
authorization
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.)


-- 
1011769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011769
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cups
Version: 2.4.1op1-2
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 2.3.3op2-3+deb11u1
Control: found -1 2.3.3op2-3
Control: found -1 2.2.10-6+deb10u5
Control: found -1 2.2.10-6
Control: fixed -1 2.3.3op2-3+deb11u2
Control: fixed -1 2.2.10-6+deb10u6

Hi,

The following vulnerability was published for cups.

Thorsten, just filling for tracking in BTS.

CVE-2022-26691[0]:
| authorization bypass when using "local" authorization

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-26691
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-26691

Regards,
Salvatore
--- End Message ---
--- Begin Message ---

Source: cups
Source-Version: 2.4.2-1
Done: Thorsten Alteholz 

Manually closing this bug as the fix for this CVE was done in version 
2.4.2-1.


  Thorsten--- End Message ---


Bug#1011934: android-platform-system-tools-hidl build-depends on package that is not in testing and has an outstanding removal request for unstable.

2022-05-26 Thread peter green

Package: android-platform-system-tools-hidl
Severity: serious
Tags: bookworm, sid

android-platform-system-tools-hidl build-depends on android-libcrypto-utils-dev.
android-libcrypt-utils-dev is built from the android-platform-system-core source
package which was recently removed from testing at the maintainer's request and
also has a request outstanding for removal from unstable, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011210

That bug report says that android-platform-tools is the replacement for
android-platform-system-core, but I don't see an obvious equivilent library
built from that source package.



Processed: Clarify fixed package

2022-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 1009422 accountsservice/22.08.8-1
Bug #1009422 {Done: Gunnar Hjalmarsson } 
[src:accountsservice] accountsservice: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned 
exit code 10
Marked as fixed in versions accountsservice/22.08.8-1.
>
End of message, stopping processing here.

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



Bug#1009422: marked as done (accountsservice: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 10)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Fri, 27 May 2022 00:55:33 +0200
with message-id <16a3aa7e-d51a-b129-b891-3b0b4af08...@debian.org>
and subject line Re: Bug#1009422: accountsservice: FTBFS: dh_auto_test: error: 
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test 
returned exit code 10
has caused the Debian Bug report #1009422,
regarding accountsservice: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu 
&& LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 10
to be marked as done.

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

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


-- 
1009422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: accountsservice
Version: 22.07.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 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 -- \
>   -Ddocbook=true \
>   -Dgdmconffile=/etc/gdm3/daemon.conf \
>   -Dadmin_group=sudo \
>   -Dsystemdsystemunitdir=/lib/systemd/system \
>   -Dintrospection=true \
>   -Dgtk_doc=true
>   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 -Ddocbook=true 
> -Dgdmconffile=/etc/gdm3/daemon.conf -Dadmin_group=sudo 
> -Dsystemdsystemunitdir=/lib/systemd/system -Dintrospection=true -Dgtk_doc=true
> The Meson build system
> Version: 0.62.0
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> WARNING: You should add the boolean check kwarg to the run_command call.
>  It currently defaults to false,
>  but it will default to true in future releases of meson.
>  See also: https://github.com/mesonbuild/meson/issues/9300
> Project name: accountsservice
> Project version: 22.07.5
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-19) 
> 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
> Has header "paths.h" : YES 
> Has header "shadow.h" : YES 
> Has header "utmpx.h" : YES 
> Checking for function "getusershell" : YES 
> Checking for function "setutxdb" : NO 
> Checking for function "fgetpwent" : YES 
> Header  has symbol "WTMPX_FILENAME" : YES 
> Checking if "value of WTMPX_FILENAME" runs: YES
> Message: whether optimization is enabled: false
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency gio-2.0 found: YES 2.72.0
> Run-time dependency gio-unix-2.0 found: YES 2.72.0
> Run-time dependency glib-2.0 found: YES 2.72.0
> Run-time dependency polkit-gobject-1 found: YES 0.105
> Run-time dependency libxcrypt found: YES 4.4.27
> Run-time dependency dbus-1 found: YES 1.14.0
> Run-time dependency libsystemd found: YES 250
> Configuring org.freedesktop.Accounts.service using configuration
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Configuring accounts-daemon.service using configuration
> Program gdbus-codegen found: YES (/usr/bin/gdbus-codegen)
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Program gdbus-codegen found: YES (/usr/bin/gdbus-codegen)
> Program glib-mkenums found: YES (/usr/bin/glib-mkenums)
> Program glib-mkenums found: YES (/usr/bin/glib-mkenums)
> Compiler for C supports link arguments 
> -Wl,--version-script,/<>/src/libaccountsservice/symbol.map: YES 
> Run-time dependency gobject-introspection-1.0 found: YES 1.72.0
> Dependency gobject-introspection-1.0 found: YES 1.72.0 (cached)
> Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner)
> Dependency gobject-introspection-1.0 found: YES 1.72.0 (cached)
> Program g-ir-compiler found: YES (/usr/bin/g-ir-compiler)
> Program vapigen found: YES (/usr/bin/vapigen)
> Program msginit found: YES (/usr/bin/msginit)
> Program msgmerge found: YES (/usr/bin/msgmerge)
> Program xgettext found: YES (/usr/bin/xgettext)
> Program xsltproc found: YES (/usr/bin/xsltproc)
> Configuring AccountsService.xml using configuration
> Program xmlto found: YES (/usr/bin/xmlto)
> Program gtkdoc-scan found: YES (/usr/bin/gtkdoc-scan)
> Program gtkdoc-scangobj found: YES (/usr/bin/gtkdoc-scangobj)
> Program gtkdoc-mkdb found: YES (/usr/bin/gtkdoc-mkdb)
> Program gtkdoc-mkhtml found: YES (/usr/bin/gtkdoc-mkhtml)
> Program gtkdoc-fixxref found: YES (/usr/bin/gtkdoc-fixxref)
> Program python3 found: YES (/usr/bin/python3)
> Program unittest_inspector.py found: YES 
> (/<>/t

Bug#1011878: marked as done (rust-compiler-builtins: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 May 2022 22:36:46 +
with message-id 
and subject line Bug#1011878: fixed in rust-compiler-builtins 0.1.70-1
has caused the Debian Bug report #1011878,
regarding rust-compiler-builtins: FTBFS: dh_auto_test: error: 
/usr/share/cargo/bin/cargo build returned exit code 101
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.)


-- 
1011878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-compiler-builtins
Version: 0.1.52-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> export RUSTC_BOOTSTRAP=1; \
> dh_auto_test
> debian cargo wrapper: options, profiles, parallel: ['parallel=8'] [] ['-j8']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', 
> '-j8', '--target', 'x86_64-unknown-linux-gnu'],) {}
>Compiling compiler_builtins v0.1.52 (/<>)
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build 
> CARGO_MANIFEST_DIR=/<> CARGO_PKG_AUTHORS='Jorge Aparicio 
> ' CARGO_PKG_DESCRIPTION='Compiler intrinsics used by 
> the Rust compiler. Also available for other targets
> if necessary'\!'
> ' CARGO_PKG_HOMEPAGE='https://github.com/rust-lang/compiler-builtins' 
> CARGO_PKG_LICENSE=MIT/Apache-2.0 CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=compiler_builtins 
> CARGO_PKG_REPOSITORY='https://github.com/rust-lang/compiler-builtins' 
> CARGO_PKG_VERSION=0.1.52 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=1 
> CARGO_PKG_VERSION_PATCH=52 CARGO_PKG_VERSION_PRE='' CARGO_PRIMARY_PACKAGE=1 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name build_script_build build.rs --error-format=json 
> --json=diagnostic-rendered-ansi --crate-type bin --emit=dep-info,link -C 
> embed-bitcode=no -C debuginfo=2 --cfg 'feature="compiler-builtins"' --cfg 
> 'feature="default"' -C metadata=8edcd6ce0a677f8c -C 
> extra-filename=-8edcd6ce0a677f8c --out-dir 
> /<>/target/debug/build/compiler_builtins-8edcd6ce0a677f8c -C 
> incremental=/<>/target/debug/incremental -L 
> dependency=/<>/target/debug/deps`
>  Running 
> `/<>/target/debug/build/compiler_builtins-8edcd6ce0a677f8c/build-script-build`
> [compiler_builtins 0.1.52] cargo:rerun-if-changed=build.rs
> [compiler_builtins 0.1.52] cargo:compiler-rt=/<>/compiler-rt
> [compiler_builtins 0.1.52] cargo:rustc-cfg=feature="unstable"
> [compiler_builtins 0.1.52] cargo:rustc-cfg=feature="mem-unaligned"
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=compiler_builtins 
> CARGO_MANIFEST_DIR=/<> CARGO_PKG_AUTHORS='Jorge Aparicio 
> ' CARGO_PKG_DESCRIPTION='Compiler intrinsics used by 
> the Rust compiler. Also available for other targets
> if necessary'\!'
> ' CARGO_PKG_HOMEPAGE='https://github.com/rust-lang/compiler-builtins' 
> CARGO_PKG_LICENSE=MIT/Apache-2.0 CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=compiler_builtins 
> CARGO_PKG_REPOSITORY='https://github.com/rust-lang/compiler-builtins' 
> CARGO_PKG_VERSION=0.1.52 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=1 
> CARGO_PKG_VERSION_PATCH=52 CARGO_PKG_VERSION_PRE='' CARGO_PRIMARY_PACKAGE=1 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' 
> OUT_DIR=/<>/target/x86_64-unknown-linux-gnu/debug/build/compiler_builtins-db2cae2e3ff6555c/out
>  rustc --crate-name compiler_builtins src/lib.rs --error-format=json 
> --json=diagnostic-rendered-ansi --crate-type lib 
> --emit=dep-info,metadata,link -C panic=abort -C embed-bitcode=no -C 
> debuginfo=2 --cfg 'feature="compiler-builtins"' --cfg 'feature="default"' -C 
> metadata=8537f4da4e8a7096 -C extra-filename=-8537f4da4e8a7096 --out-dir 
> /<>/target/x86_64-unknown-linux-gnu/debug/deps --target 
> x86_64-unknown-linux-gnu -C 
> incremental=/<>/target/x86_64-unknown-linux-gnu/debug/incremental
>  -L dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L 
> dependency=/<>/target/debug/deps -C debuginfo=2 --cap-lints warn 
> -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix 
> /<>=/usr/share/cargo/registry/compiler-builtins-0.1.52 --cfg 
> 'feature="unstable"' --cfg 'feature="mem-unaligned"'`
> error: cannot find macro `asm` in this scope
>--> src/int/specialized_div_rem/mod.rs:187:9
> |
> 187 |  

Bug#1011895: marked as done (gnome-boxes: FTBFS: Package 'libpulse-simple', required by 'gvncpulse-1.0', not found)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 May 2022 21:43:07 +
with message-id 
and subject line Bug#1011895: fixed in gtk-vnc 1.3.0-3
has caused the Debian Bug report #1011895,
regarding gnome-boxes: FTBFS: Package 'libpulse-simple', required by 
'gvncpulse-1.0', not found
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.)


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

Hi,

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


Relevant part (hopefully):
>  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.62.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-boxes
> Project version: 42.0.1
> C compiler for the host machine: cc (gcc 11.3.0 "cc (Debian 11.3.0-3) 11.3.0")
> C linker for the host machine: cc ld.bfd 2.38
> Vala compiler for the host machine: valac (valac 0.56.1)
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency libarchive found: YES 3.6.0
> Library config found: YES
> Configuring config.h.in 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.Boxes.desktop.in using configuration
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Program desktop-file-validate found: YES (/usr/bin/desktop-file-validate)
> Configuring org.gnome.Boxes.service using configuration
> Configuring org.gnome.Boxes.SearchProvider.service using configuration
> Configuring org.gnome.Boxes.appdata.xml.in using configuration
> Program appstream-util found: YES (/usr/bin/appstream-util)
> Configuring org.gnome.boxes.gschema.xml using configuration
> Configuring org.gnome.Boxes.SearchProvider.ini using configuration
> Program itstool found: YES (/usr/bin/itstool)
> Program msgmerge found: YES (/usr/bin/msgmerge)
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Program msginit found: YES (/usr/bin/msginit)
> Program msgmerge found: YES (/usr/bin/msgmerge)
> Program xgettext found: YES (/usr/bin/xgettext)
> Run-time dependency gio-2.0 found: YES 2.72.1
> Run-time dependency glib-2.0 found: YES 2.72.1
> Run-time dependency gobject-2.0 found: YES 2.72.1
> Run-time dependency gtk+-3.0 found: YES 3.24.33
> Run-time dependency gtk-vnc-2.0 found: YES 1.3.0
> Did not find CMake 'cmake'
> Found CMake: NO
> Run-time dependency gvncpulse-1.0 found: NO 
> 
> ../src/meson.build:100:0: ERROR: Could not generate cargs for gvncpulse-1.0:
> Package libpulse-simple was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libpulse-simple.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'libpulse-simple', required by 'gvncpulse-1.0', not found
> 
> 
> 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-05-25T21:18:27.133837
> 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.62.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-boxes
> Project version: 42.0.1
> 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.3.0 "cc (Debian 11.3.0-3) 11.3.0")
> C linker for the host machine: cc ld.bfd 2.38
> Running compile:
> Working 

Bug#1011876: marked as done (gnome-connections: FTBFS: Package 'libpulse-simple', required by 'gvncpulse-1.0', not found)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 May 2022 21:43:07 +
with message-id 
and subject line Bug#1011876: fixed in gtk-vnc 1.3.0-3
has caused the Debian Bug report #1011876,
regarding gnome-connections: FTBFS: Package 'libpulse-simple', required by 
'gvncpulse-1.0', not found
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.)


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

Hi,

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


Relevant part (hopefully):
>  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.62.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-connections
> Project version: 42.1.2
> C compiler for the host machine: cc (gcc 11.3.0 "cc (Debian 11.3.0-3) 11.3.0")
> C linker for the host machine: cc ld.bfd 2.38
> Vala compiler for the host machine: valac (valac 0.56.1)
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Configuring config.h.in using configuration
> Configuring org.gnome.Connections.desktop.in using configuration
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Program desktop-file-validate found: YES (/usr/bin/desktop-file-validate)
> Program appstream-util found: YES (/usr/bin/appstream-util)
> Configuring org.gnome.Connections.service using configuration
> Program glib-compile-schemas found: YES (/usr/bin/glib-compile-schemas)
> Program itstool found: YES (/usr/bin/itstool)
> Program msgmerge found: YES (/usr/bin/msgmerge)
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Library config found: YES
> Library m found: YES
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency gio-2.0 found: YES 2.72.1
> Run-time dependency gtk+-3.0 found: YES 3.24.33
> Run-time dependency gtk-vnc-2.0 found: YES 1.3.0
> Did not find CMake 'cmake'
> Found CMake: NO
> Run-time dependency gvncpulse-1.0 found: NO 
> 
> ../src/meson.build:25:0: ERROR: Could not generate cargs for gvncpulse-1.0:
> Package libpulse-simple was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libpulse-simple.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'libpulse-simple', required by 'gvncpulse-1.0', not found
> 
> 
> 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-05-25T21:19:35.292065
> 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.62.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-connections
> Project version: 42.1.2
> 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.3.0 "cc (Debian 11.3.0-3) 11.3.0")
> C linker for the host machine: cc ld.bfd 2.38
> Running compile:
> Working directory:  /tmp/tmpy6rokg4t
> Command line:  valac /tmp/tmpy6rokg4t/testfile.vala -C 
> 
> Code:
>  class MesonSanityCheck : Object { }
> Compiler stdout:
>  
> Compiler stderr:
>  
> Vala compiler for the host machine: valac (valac 0.56.1)
> 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 

Bug#1005145: marked as done (oz: FTBFS against python 3.10)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 May 2022 21:43:28 +
with message-id 
and subject line Bug#1005145: fixed in oz 0.17.0-5.1
has caused the Debian Bug report #1005145,
regarding oz: FTBFS against python 3.10
to be marked as done.

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

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


-- 
1005145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: oz
Version: 0.17.0-4
Severity: normal
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy

Dear Maintainer,

This bug report was also filed in Ubuntu and can be found at
https://launchpad.net/bugs/1960273

When oz is triggered with python3.10 for autopkgtest, it will fail due to the
migration of some collections items to collections.abc.

See also the patch that I have sent upstream:
https://github.com/clalancette/oz/pull/292

-Dan
--- End Message ---
--- Begin Message ---
Source: oz
Source-Version: 0.17.0-5.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
oz, 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.
Adrian Bunk  (supplier of updated oz 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, 26 May 2022 18:24:14 +0300
Source: oz
Architecture: source
Version: 0.17.0-5.1
Distribution: unstable
Urgency: low
Maintainer: Simon Josefsson 
Changed-By: Adrian Bunk 
Closes: 1005145
Changes:
 oz (0.17.0-5.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Upload to unstable.
   * Add fix for Python 3.10 compatibility. (Closes: #1005145)
Checksums-Sha1:
 f91997395ca26e360062ab13c1ca566df610c8c1 1871 oz_0.17.0-5.1.dsc
 61fc3b45a07b13fa30fa5a8c11356b2e37d7a0e0 4776 oz_0.17.0-5.1.debian.tar.xz
Checksums-Sha256:
 6b7e8ffebe51cf0b161e050374e227fdc783c3034c128798b670060d93bcc2f5 1871 
oz_0.17.0-5.1.dsc
 4e7a4eacda0148f8caf0c836cc08c9beedf9dae8b987363663835c6601e1072f 4776 
oz_0.17.0-5.1.debian.tar.xz
Files:
 58f2def31db799fce3a4b949d1130e76 1871 python optional oz_0.17.0-5.1.dsc
 1b37285a8f26b58b5bd234a934fdd445 4776 python optional 
oz_0.17.0-5.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmKP3AgACgkQiNJCh6LY
mLHiSRAAqwm66t/GUPyfGuchC81mwmK15E7ewBBeINZxTOUugI3PYouvYCnrUqc9
PHeY0NxdXZ9Zlf/8G4cu0edcKx9yidBV0LISS53PWocyDE52/evp+hzUsF5NTjML
kQ96ZGId+SFvxZGwn6pBoYDK86pb8TUvHVPn1y3KEwwrzVK8uP0R3AUbUnRRUzg3
tXKcwlb4SqJYDIGAtgBzAraBsoE+y5j8MeWo7lMirAWDS9N8qst4w2Yk9VG2Dfxf
0CQKF5MusVTJC3DuLp5bOu44uJZrW0VCD6PtKVNmaU6OXFRL37pzx7pJ71ZIOFDJ
stVsWnqu2+9mpEFa4o2881ym5fCYIf4yxUTldQG/6O/2rgVJ5z0SLaAeUUYkogGs
NbMg/NvFQcdJaXa3dGoSfd+fdE1d6LIT8PtBhtWa8EGjT6yVqeZTcmP3vhAdS0pV
9T+ePVZoSUGog3hObKv6xwg2bRask7Glmd841OcmlIg86cU0kvVoLg373a3YvkIb
o9W0DAx9Jsu2yYrPTz/RjmjHQVIYtncrc/qLcKihDZDjzOLRWHS/rhMg5S1/p/Pw
k3M6ajlgN90Z82gYH0MANhmyn7AJDIQ0mcdQ1YzHWqyKVzUw2y8XftwWg5n3qs2d
hWNE6LXyj/s7fu+I7DCAEgMYzICL+pXpA7pcQz3N1FGsJflUe+s=
=SBt5
-END PGP SIGNATURE End Message ---


Bug#1011872: marked as done (libnet-server-mail-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 May 2022 21:43:20 +
with message-id 
and subject line Bug#1011872: fixed in libnet-server-mail-perl 0.28-2
has caused the Debian Bug report #1011872,
regarding libnet-server-mail-perl: FTBFS: dh_auto_test: error: make -j8 test 
TEST_VERBOSE=1 returned exit code 2
to be marked as done.

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

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


-- 
1011872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011872
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnet-server-mail-perl
Version: 0.28-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 
> 'blib/arch')" t/*.t
> t/esmtp.t . 
> 1..10
> ok 1 - use Net::Server::Mail::ESMTP;
> ok 2
> ok 3
> ok 4
> ok 5
> ok 6
> ok 7
> ok 8
> ok 9
> ok 10
> ok
> t/lmtp.t .. 
> 1..10
> ok 1 # skip You don't seem to have Net::LMTP installed on your system
> ok 2 # skip You don't seem to have Net::LMTP installed on your system
> ok 3 # skip You don't seem to have Net::LMTP installed on your system
> ok 4 # skip You don't seem to have Net::LMTP installed on your system
> ok 5 # skip You don't seem to have Net::LMTP installed on your system
> ok 6 # skip You don't seem to have Net::LMTP installed on your system
> ok 7 # skip You don't seem to have Net::LMTP installed on your system
> ok 8 # skip You don't seem to have Net::LMTP installed on your system
> ok 9 # skip You don't seem to have Net::LMTP installed on your system
> ok 10 # skip You don't seem to have Net::LMTP installed on your system
> ok
> t/smtp.t .. 
> 1..10
> ok 1 - use Net::Server::Mail::SMTP;
> ok 2
> ok 3
> ok 4
> ok 5
> ok 6
> ok 7
> ok 8
> ok 9
> ok 10
> ok
> # Error: Can't call method "peerhost" on an undefined value at t/starttls.t 
> line 131.
> # kill 9, 746980 (server)
> t/starttls.t .. 
> ok 1 - Accepted client for Test01: STARTTLS support
> ok 2 - Accepted client for Test02: STARTTLS invalid parameters
> ok 3 - Accepted client for Test03: STARTTLS handshake
> All 3 subtests passed 
> 
> Test Summary Report
> ---
> t/starttls.t (Wstat: 13 Tests: 3 Failed: 0)
>   Non-zero wait status: 13
>   Parse errors: No plan found in TAP output
> Files=4, Tests=33,  1 wallclock secs ( 0.01 usr  0.01 sys +  0.33 cusr  0.06 
> csys =  0.41 CPU)
> Result: FAIL
> Failed 1/4 test programs. 0/33 subtests failed.
> make[1]: *** [Makefile:861: test_dynamic] Error 255
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/libnet-server-mail-perl_0.28-1_unstable.log

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

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

If you reassign this bug to another package, please 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: libnet-server-mail-perl
Source-Version: 0.28-2
Done: gregor herrmann 

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libnet-server-mail-perl 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 ftpma

Bug#1005145: oz: diff for NMU version 0.17.0-5.1

2022-05-26 Thread Adrian Bunk
On Thu, May 26, 2022 at 10:13:03PM +0200, Simon Josefsson wrote:
> Thank you! Feel free to speed up if you want 

Thanks, rescheduled for immediate upload.

> /Simon

cu
Adrian



Processed: Re: reassign gtk-vnc bug

2022-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1011876 src:gtk-vnc 1.3.0-2
Bug #1011876 [gtk-vnc] gnome-connections: FTBFS: Package 'libpulse-simple', 
required by 'gvncpulse-1.0', not found
Bug reassigned from package 'gtk-vnc' to 'src:gtk-vnc'.
No longer marked as found in versions 1.3.0-3.
Ignoring request to alter fixed versions of bug #1011876 to the same values 
previously set
Bug #1011876 [src:gtk-vnc] gnome-connections: FTBFS: Package 'libpulse-simple', 
required by 'gvncpulse-1.0', not found
Marked as found in versions gtk-vnc/1.3.0-2.
> reassign 1011895 src:gtk-vnc 1.3.0-2
Bug #1011895 [gtk-vnc] gnome-boxes: FTBFS: Package 'libpulse-simple', required 
by 'gvncpulse-1.0', not found
Bug reassigned from package 'gtk-vnc' to 'src:gtk-vnc'.
No longer marked as found in versions 1.3.0-3.
Ignoring request to alter fixed versions of bug #1011895 to the same values 
previously set
Bug #1011895 [src:gtk-vnc] gnome-boxes: FTBFS: Package 'libpulse-simple', 
required by 'gvncpulse-1.0', not found
Marked as found in versions gtk-vnc/1.3.0-2.
>
End of message, stopping processing here.

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



Bug#1011872: marked as pending in libnet-server-mail-perl

2022-05-26 Thread gregor herrmann
Control: tag -1 pending

Hello,

Bug #1011872 in libnet-server-mail-perl reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/perl-team/modules/packages/libnet-server-mail-perl/-/commit/bfe1328485e5893f78fb4ba0bf10f443999ceaa8


Add another patch to work around a flaky SSL test.

Bug #917656 reappeared again; using Net::SMTP's quit() on top of the
original patch seems to make the issue more stable.

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


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011872



Processed: Bug#1011872 marked as pending in libnet-server-mail-perl

2022-05-26 Thread Debian Bug Tracking System
Processing control commands:

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

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



Bug#1011146: passwdqc is marked for autoremoval from testing

2022-05-26 Thread Dmitry V. Levin
On Thu, May 26, 2022 at 05:34:02AM +, Debian testing autoremoval watch 
wrote:
> passwdqc 2.0.2-1 is marked for autoremoval from testing on 2022-06-30
> 
> It (build-)depends on packages with these RC bugs:
> 1011146: nvidia-graphics-drivers-tesla-470: CVE-2022-28181, CVE-2022-28183, 
> CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192
>  https://bugs.debian.org/1011146
> 
> This mail is generated by:
> https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl
> 
> Autoremoval data is generated by:
> https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl

passwdqc has nothing to do with nvidia-graphics-drivers-tesla-470,
please fix these buggy autoremoval scripts.

Thanks,

-- 
ldv



Processed: retitle 958853 to anki: old version beginning to fail with newer Python releases

2022-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 958853 anki: old version beginning to fail with newer Python releases
Bug #958853 [anki] anki: Upstream new version
Bug #965258 [anki] anki: upgrade to newer version of Anki
Changed Bug title to 'anki: old version beginning to fail with newer Python 
releases' from 'anki: Upstream new version'.
Changed Bug title to 'anki: old version beginning to fail with newer Python 
releases' from 'anki: upgrade to newer version of Anki'.
> thanks
Stopping processing here.

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



Processed (with 2 errors): reassign gtk-vnc bug

2022-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1011876 gtk-vnc 1.3.0-3
Bug #1011876 [src:gnome-connections] gnome-connections: FTBFS: Package 
'libpulse-simple', required by 'gvncpulse-1.0', not found
Bug reassigned from package 'src:gnome-connections' to 'gtk-vnc'.
No longer marked as found in versions gnome-connections/42.1.2-1.
Ignoring request to alter fixed versions of bug #1011876 to the same values 
previously set
Bug #1011876 [gtk-vnc] gnome-connections: FTBFS: Package 'libpulse-simple', 
required by 'gvncpulse-1.0', not found
There is no source info for the package 'gtk-vnc' at version '1.3.0-3' with 
architecture ''
Unable to make a source version for version '1.3.0-3'
Marked as found in versions 1.3.0-3.
> affects 1011876 src:gnome-connections
Bug #1011876 [gtk-vnc] gnome-connections: FTBFS: Package 'libpulse-simple', 
required by 'gvncpulse-1.0', not found
Added indication that 1011876 affects src:gnome-connections
> reassign 1011895 gtk-vnc 1.3.0-3
Bug #1011895 [src:gnome-boxes] gnome-boxes: FTBFS: Package 'libpulse-simple', 
required by 'gvncpulse-1.0', not found
Bug reassigned from package 'src:gnome-boxes' to 'gtk-vnc'.
No longer marked as found in versions gnome-boxes/42.0.1-2.
Ignoring request to alter fixed versions of bug #1011895 to the same values 
previously set
Bug #1011895 [gtk-vnc] gnome-boxes: FTBFS: Package 'libpulse-simple', required 
by 'gvncpulse-1.0', not found
There is no source info for the package 'gtk-vnc' at version '1.3.0-3' with 
architecture ''
Unable to make a source version for version '1.3.0-3'
Marked as found in versions 1.3.0-3.
> affects 1011895 src:gnome-boxes
Bug #1011895 [gtk-vnc] gnome-boxes: FTBFS: Package 'libpulse-simple', required 
by 'gvncpulse-1.0', not found
Added indication that 1011895 affects src:gnome-boxes
> Thank you,
Unknown command or malformed arguments to command.
> Jeremy Bicha
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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



Processed (with 1 error): Re: Bug#958853: Updating Anki in Debian - current status

2022-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 958853 serious
Bug #958853 [anki] anki: Upstream new version
Bug #965258 [anki] anki: upgrade to newer version of Anki
Severity set to 'serious' from 'wishlist'
Severity set to 'serious' from 'wishlist'
> title 958853 anki: old version beginning to fail with newer Python releases
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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



Processed: limit source to php-symfony-polyfill, tagging 1011786

2022-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> limit source php-symfony-polyfill
Limiting to bugs with field 'source' containing at least one of 
'php-symfony-polyfill'
Limit currently set to 'source':'php-symfony-polyfill'

> tags 1011786 + pending
Bug #1011786 [src:php-symfony-polyfill] php-symfony-polyfill: FTBFS: make[1]: 
*** [debian/rules:53: override_dh_auto_test] Error 1
Added tag(s) pending.
> thanks
Stopping processing here.

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



Bug#995411: marked as done (ruby-omniauth-ultraauth: autopkgtest needs update for new version of ruby-omniauth-openid-connect: Could not find 'omniauth_openid_connect' (~> 0.3.0))

2022-05-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 May 2022 20:39:29 +
with message-id 
and subject line Bug#995411: fixed in ruby-omniauth-ultraauth 0.0.2-2
has caused the Debian Bug report #995411,
regarding ruby-omniauth-ultraauth: autopkgtest needs update for new version of 
ruby-omniauth-openid-connect: Could not find 'omniauth_openid_connect' (~> 
0.3.0)
to be marked as done.

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

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


-- 
995411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-omniauth-ultraauth
Version: 0.0.2-1.1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, 
ruby-omniauth-openid-conn...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:ruby-omniauth-openid-connect

Dear maintainer(s),

With a recent upload of ruby-omniauth-openid-connect the autopkgtest of
ruby-omniauth-ultraauth fails in testing when that autopkgtest is run
with the binary packages of ruby-omniauth-openid-connect from unstable.
It passes when run with only packages from testing. In tabular form:

 passfail
ruby-omniauth-openid-connect from testing0.4.0-2
ruby-omniauth-ultraauth  from testing0.0.2-1.1
all others   from testingfrom testing

I copied some of the output at the bottom of this report. It looks to me
that you have to make your package compatible with the next version of
ruby-omniauth-openid-connect.

Currently this regression is blocking the migration of
ruby-omniauth-openid-connect to testing [1]. Of course,
ruby-omniauth-openid-connect shouldn't just break your autopkgtest (or
even worse, your package), but it seems to me that the change in
ruby-omniauth-openid-connect was intended and your package needs to
update to the new situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from
ruby-omniauth-openid-connect should really add a versioned Breaks on the
unfixed version of (one of your) package(s). Note: the Breaks is nice
even if the issue is only in the autopkgtest as it helps the migration
software to figure out the right versions to combine in the tests.

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

Paul

[1] https://qa.debian.org/excuses.php?package=ruby-omniauth-openid-connect

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-omniauth-ultraauth/15624243/log.gz


┌──┐
│ Checking Rubygems dependency resolution on ruby2.7
   │
└──┘

GEM_PATH= ruby2.7 -e gem\ \"omniauth-ultraauth\"
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in
block in activate_dependencies': Could not find
'omniauth_openid_connect' (~> 0.3.0) among 90 total gem(s)
(Gem::MissingSpecError)
Checked in
'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
at:
/usr/share/rubygems-integration/all/specifications/omniauth-ultraauth-0.0.2.gemspec,
execute `gem env` for more information
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block
in activate_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in
`activate_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in 
`activate'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in
`block in gem'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in
`synchronize'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`gem'
from -e:1:in `'
/usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:311:in `to_specs':
Could not find 'omniauth_openid_connect' (~> 0.3.0) among 90 total
gem(s) (Gem::MissingSpecError)
Checked in
'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-

Bug#979748: marked as done (rio: FTBFS with glibc 2.32)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 May 2022 20:39:23 +
with message-id 
and subject line Bug#979748: fixed in rio 1.07-15
has caused the Debian Bug report #979748,
regarding rio: FTBFS with glibc 2.32
to be marked as done.

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

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


-- 
979748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rio
Version: 1.07-14
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com

Hi,

rio currently FTBFS against glibc 2.32, which is used in the
development release of Ubuntu (and should be in Debian soon).

This is because it uses sys_errlist instead of strerror(), which is also
supported in earlier versions of glibc.

In Ubuntu, the attached patch was applied to achieve the following:

  * std.h: Use strerror() instead of sys_errlist to fix FTBFS with glibc 2.32.

Thanks for considering the patch.

Logan
only in patch2:
unchanged:
--- rio-1.07.orig/std.h
+++ rio-1.07/std.h
@@ -31,7 +31,7 @@
 #endif
 
 #ifndefSZERROR
-#defineSZERROR 
sys_errlist[errno]
+#defineSZERROR 
strerror(errno)
 #endif
 
 typedef unsigned char UCHAR;
--- End Message ---
--- Begin Message ---
Source: rio
Source-Version: 1.07-15
Done: Adam Borowski 

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated rio 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, 26 May 2022 21:44:16 +0200
Source: rio
Architecture: source
Version: 1.07-15
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Closes: 979748 1007402
Changes:
 rio (1.07-15) unstable; urgency=medium
 .
   * QA upload.
   * Convert source to 3.0 format (closes: #1007402)
   * Fix FTBFS with glibc 2.32 (closes: #979748)
Checksums-Sha1:
 1ffdf0af8bea6e5140de17e1e9c4fa51360a7ee4 1702 rio_1.07-15.dsc
 8651279c5446f0e2e1e5dad65b65c1519a5ab0be 5680 rio_1.07-15.debian.tar.xz
 23feaa8991ecac16548335f2065eb015693d156e 5482 rio_1.07-15_source.buildinfo
Checksums-Sha256:
 66ac3a4f75f614f5f78f08b359ad59de1caa3b7cfc878ab6bac7e231cb2a2835 1702 
rio_1.07-15.dsc
 6e1b892db5501038f04b7e9ebbf96af6d3287cb915fd884182d55f4c63fc57c0 5680 
rio_1.07-15.debian.tar.xz
 c8c93b8b618391d3e65a2cab6f6f256e6e45d0a48bc9bdcf4fc2dc6228f9b3db 5482 
rio_1.07-15_source.buildinfo
Files:
 3a348fac56c4973450c495c2ce48e9fd 1702 sound optional rio_1.07-15.dsc
 290ed1308eefc41895023775da70e586 5680 sound optional rio_1.07-15.debian.tar.xz
 11874e26022efd707c108fc0a20ad7da 5482 sound optional 
rio_1.07-15_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmKP2bMACgkQweDZLphv
fH6lkg/9FM8wrc4d68IpMyBqpAFmkuzokOZrMUjhfSc8EVX/89MkMuRDd9QUR8ax
YKroH0DXy3uDPOdf8cLGQrOopzh+CSlDDEHIFwmZq+m4Twud25G38ERcnrhrO5P4
1NQ+vLjue8KoNdtS1LwkgiFM1+CDCNmgp3VzrCs7mEXXMEd9x1CwZHkr28ok5faR
O3XhYKmtY75MqAyIDI8jjrdM1eRHgVdhWBkaczh3mRqmV4gTRCGXBhn1BPvH5M40
u1LlGip5Kyy3x2za3R7tSi2U6immQQGivKIIPNwYR1WdXr860zzBrFUvlIQCieWT
+CJkKwsbZf04ZHh/HovbnD2+dykoMTbCQiHWWTRmp2JPzhlxJ4AWfy5DQiZnuZt4
FEJRNgj56L0c5qfaz/4qaKOhWcXhzEQU/MVberV/jwmn7fcMa8zEmZHXalsEV9Qw
EQeYTIJEQ5c3kJ3Z0FNewZb1CVAX3FCVJPOwQGG2GiYfHiAQAZ9U+JEiZEsLXlbF
Btw58zxcZ90OcjRHf3cBuQ0XkogRCXG7WUnuinuFfkqZwoTusa6lsfHhc8dx1O1N
qjf8lOSsajaEPq7vYBRrSTYYzF8vLfAU6MSl1st9mEk+bz8cUo9NoDhIoeJdLBYq
pdH817KZdb5ioD33C44WyTmJ7Kq/rP+uIX2stOv+75kRaNIsIhw=
=b5r8
-END PGP SIGNATURE End Message ---


Bug#1011899: marked as done (php-twig: FTBFS: make[1]: *** [debian/rules:92: override_dh_auto_test] Error 1)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 May 2022 20:39:11 +
with message-id 
and subject line Bug#1011899: fixed in php-twig 3.4.1-1
has caused the Debian Bug report #1011899,
regarding php-twig: FTBFS: make[1]: *** [debian/rules:92: 
override_dh_auto_test] Error 1
to be marked as done.

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

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


-- 
1011899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-twig
Version: 3.3.9-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> SYMFONY_DEPRECATIONS_HELPER=weak phpunit
> PHPUnit 9.5.16 by Sebastian Bergmann and contributors.
> 
> Testing 
> .   61 / 1649 (  
> 3%)
> .  122 / 1649 (  
> 7%)
> .  183 / 1649 ( 
> 11%)
> .  244 / 1649 ( 
> 14%)
> .  305 / 1649 ( 
> 18%)
> .  366 / 1649 ( 
> 22%)
> S  427 / 1649 ( 
> 25%)
> .  488 / 1649 ( 
> 29%)
> .  549 / 1649 ( 
> 33%)
> ..S..  610 / 1649 ( 
> 36%)
> .  671 / 1649 ( 
> 40%)
> .  732 / 1649 ( 
> 44%)
> ..S..  793 / 1649 ( 
> 48%)
> .  854 / 1649 ( 
> 51%)
> .  915 / 1649 ( 
> 55%)
> .  976 / 1649 ( 
> 59%)
> . 1037 / 1649 ( 
> 62%)
> . 1098 / 1649 ( 
> 66%)
> . 1159 / 1649 ( 
> 70%)
> . 1220 / 1649 ( 
> 73%)
> . 1281 / 1649 ( 
> 77%)
> . 1342 / 1649 ( 
> 81%)
> . 1403 / 1649 ( 
> 85%)
> . 1464 / 1649 ( 
> 88%)
> . 1525 / 1649 ( 
> 92%)
> . 1586 / 1649 ( 
> 96%)
> . 1647 / 1649 ( 
> 99%)
> ..1649 / 1649 
> (100%)
> 
> Time: 00:00.844, Memory: 38.00 MB
> 
> OK, but incomplete, skipped, or risky tests!
> Tests: 1649, Assertions: 4384, Skipped: 3.
> 
> Legacy deprecation notices (3)
> # testsuite for extra packages
> set -e; \
>  for package_info_file in $(find debian/packages_to_build/ -mindepth 1 
> -maxdepth 1 -type f); do \
>   . $package_info_file; \
>   if [ -f $src_path/phpunit.xml.dist ]; then \
>LC_ALL=en_US SYMFONY_DEPRECATIONS_HELPER=weak phpunit \
>--bootstrap vendor/autoload.php \
>--configuration $src_path/phpunit.xml.dist \
>$src_path; \
>   fi; \
>  done
> PHPUnit 9.5.16 by Sebastian Bergmann and contributors.
> 
> Warning:   Your XML configuration validates against a deprecated schema.
> Suggestion:Migrate your XML configuration using "--migrate-configuration"!
> 
> ..S 3 / 3 
> (100%)
> 
> Time: 00:00.035, Memory: 8.00 MB
> 
> OK, but incomplete, skipped, or risky tests!
> Tests: 3, Assertions: 4, Skipped: 1.
> PHPUnit 9.5.16 by Sebastian Bergmann and contributors.
> 
> Warning:   Your XML configuration validates against a deprecated schema.
> Suggestion:Migrate your XML configuration using "--migrate-configuration"!
> 
> ...S8 / 8 

Bug#1010526: marked as done (libxml2: CVE-2022-29824: integer overflows in xmlBuf and xmlBuffer)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 May 2022 20:33:08 +
with message-id 
and subject line Bug#1010526: fixed in libxml2 2.9.4+dfsg1-7+deb10u4
has caused the Debian Bug report #1010526,
regarding libxml2: CVE-2022-29824: integer overflows in xmlBuf and xmlBuffer
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.)


-- 
1010526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxml2
Version: 2.9.13+dfsg-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for libxml2.

CVE-2022-29824[0]:
| In libxml2 before 2.9.14, several buffer handling functions in buf.c
| (xmlBuf*) and tree.c (xmlBuffer*) don't check for integer overflows.
| This can result in out-of-bounds memory writes. Exploitation requires
| a victim to open a crafted, multi-gigabyte XML file. Other software
| using libxml2's buffer functions, for example libxslt through 1.1.35,
| is affected as well.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-29824
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29824
[1] 
https://gitlab.gnome.org/GNOME/libxml2/-/commit/2554a2408e09f13652049e5ffb0d26196b02ebab

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libxml2
Source-Version: 2.9.4+dfsg1-7+deb10u4
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated libxml2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 15 May 2022 16:13:21 +0200
Source: libxml2
Architecture: source
Version: 2.9.4+dfsg1-7+deb10u4
Distribution: buster-security
Urgency: high
Maintainer: Debian XML/SGML Group 
Changed-By: Salvatore Bonaccorso 
Closes: 1010526
Changes:
 libxml2 (2.9.4+dfsg1-7+deb10u4) buster-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Fix integer overflow in xmlBufferResize
   * Fix integer overflows in xmlBuf and xmlBuffer (CVE-2022-29824)
 (Closes: #1010526)
Checksums-Sha1: 
 4d87fc4fc52c540714d5e7754ed604e9c51cc7c9 3163 libxml2_2.9.4+dfsg1-7+deb10u4.dsc
 ca9a4f7f1eab2b69ead6174885a5e6b1629ec956 2446412 
libxml2_2.9.4+dfsg1.orig.tar.xz
 bdb8be2b5f6bddf8d392252f1cdd676d659a41a0 44728 
libxml2_2.9.4+dfsg1-7+deb10u4.debian.tar.xz
Checksums-Sha256: 
 76c5b2edeb11a39e261de86603c43ea0adc65948f04f54fbd7be39bc726655a6 3163 
libxml2_2.9.4+dfsg1-7+deb10u4.dsc
 a74ad55e346aa0b2b41903e66d21f8f3d2a736b3f41e32496376861ab484184e 2446412 
libxml2_2.9.4+dfsg1.orig.tar.xz
 68f97766c8c8b161bd99f372a4056fd8bcdabd6e54ed496409cf33d6b3a87d11 44728 
libxml2_2.9.4+dfsg1-7+deb10u4.debian.tar.xz
Files: 
 68375e62008b8e8ddd51b1e69ad2f495 3163 libs optional 
libxml2_2.9.4+dfsg1-7+deb10u4.dsc
 3ced197721416e7e2f13b0f4e0f1185b 2446412 libs optional 
libxml2_2.9.4+dfsg1.orig.tar.xz
 37aad19f71b4c7b8a64ba24f4d59f7c6 44728 libs optional 
libxml2_2.9.4+dfsg1-7+deb10u4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmKBC15fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E4LcQAJaL/MdkQTdQIMyIeQZBkGkDWhS3Y7Pe
ar6lBYA96QFhWA+ucMzHCX+54XcZQv3l0sysnXMu/YQU1qM43X0RCO35X2jitpxx
yHGdIpyh6sAiefLpZzWjDEzIUFi/6/0l/PRSY8AsolO8My4jWSjrvS4yJ9CaTmUE
CtRYo1doyOzllvePc2icmZVJSDhfTW9F5kOsFOQ0v+Q88w5fDbBp7f+HsnLb74pk
s/oJT0//klpD2j+jNGZqRvcCOYpZg+G5DgklE1hEhiBZ6Yj45ur9cCMPuXf39Rfg
wQLem199MRT1+KQMyFPwY2C29VeHPfKDF67Ug/wIKEO1JnKvDC2pEBsGBQwwNGtG
SPRYJM4FPiKNei3g9bLCgmQC+ZtG54PNJzB5jM2n7LmwF0RmqficMzU3XGJlZrtp
sZ3TJq3o3pnJYqEyy9cpM2+TjIrJpSUdfNBn/Txmhl9JsfLyhE2cdlWodUP9CONK
LaEWp5dfsN9O4S65a+2t3oSl0qU+QiW

Bug#1010526: marked as done (libxml2: CVE-2022-29824: integer overflows in xmlBuf and xmlBuffer)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 May 2022 20:32:12 +
with message-id 
and subject line Bug#1010526: fixed in libxml2 2.9.10+dfsg-6.7+deb11u2
has caused the Debian Bug report #1010526,
regarding libxml2: CVE-2022-29824: integer overflows in xmlBuf and xmlBuffer
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.)


-- 
1010526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxml2
Version: 2.9.13+dfsg-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for libxml2.

CVE-2022-29824[0]:
| In libxml2 before 2.9.14, several buffer handling functions in buf.c
| (xmlBuf*) and tree.c (xmlBuffer*) don't check for integer overflows.
| This can result in out-of-bounds memory writes. Exploitation requires
| a victim to open a crafted, multi-gigabyte XML file. Other software
| using libxml2's buffer functions, for example libxslt through 1.1.35,
| is affected as well.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-29824
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29824
[1] 
https://gitlab.gnome.org/GNOME/libxml2/-/commit/2554a2408e09f13652049e5ffb0d26196b02ebab

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libxml2
Source-Version: 2.9.10+dfsg-6.7+deb11u2
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated libxml2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 15 May 2022 15:58:46 +0200
Source: libxml2
Architecture: source
Version: 2.9.10+dfsg-6.7+deb11u2
Distribution: bullseye-security
Urgency: high
Maintainer: Debian XML/SGML Group 
Changed-By: Salvatore Bonaccorso 
Closes: 1010526
Changes:
 libxml2 (2.9.10+dfsg-6.7+deb11u2) bullseye-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Fix integer overflow in xmlBufferResize
   * Fix integer overflows in xmlBuf and xmlBuffer (CVE-2022-29824)
 (Closes: #1010526)
Checksums-Sha1: 
 40219fa9419ee3943645f9fc5bfefb81e1e37fbe 2859 
libxml2_2.9.10+dfsg-6.7+deb11u2.dsc
 2578c0817feae47d78c4f987c7a2a32f87d89517 2503560 
libxml2_2.9.10+dfsg.orig.tar.xz
 3c302997948f3789fc90f82a75404fa229eebbf9 36368 
libxml2_2.9.10+dfsg-6.7+deb11u2.debian.tar.xz
Checksums-Sha256: 
 f80a2929c91dc06cfa84e7e555d5d76c9b9df848d9b3e561e59f1338417feba3 2859 
libxml2_2.9.10+dfsg-6.7+deb11u2.dsc
 65ee7a2f5e100c64ddf7beb92297c9b2a30b994a76cd1fab67470cf22db6b7d0 2503560 
libxml2_2.9.10+dfsg.orig.tar.xz
 76bb4df309fbb02b26a6d5ab1bc32e158c709f0e7fb255ec734be5efe3cb78d5 36368 
libxml2_2.9.10+dfsg-6.7+deb11u2.debian.tar.xz
Files: 
 4b0bca460d95dc492e8d5a47f1fadf7f 2859 libs optional 
libxml2_2.9.10+dfsg-6.7+deb11u2.dsc
 4fb60521425df67f453b3c1ff0efbc1c 2503560 libs optional 
libxml2_2.9.10+dfsg.orig.tar.xz
 0a80fb4f837efc502ccae0024b3b3338 36368 libs optional 
libxml2_2.9.10+dfsg-6.7+deb11u2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmKBCChfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EeSsP/j1A3BTBAp1Q6DMpx5uyq2I9cwx2WGE8
GH3x6lCpKaVdlsj17nIlk5plNqlbLzfNaXGqyxk5U66E8dU0oF+zopqH5hI/sfZh
hOw/y9CW7eck8edgd6WH69HoG3a9o8taohKojjkrdCQHd+IHd4Fiat9ztDDjFnCE
Fk2IEgMV7y2LHUcbrJXXwAPD8NZJl7XdiV2UwUMkfNiAnLQkpJq91YHHhsot3Zh5
QwcVqNcZJiDtyGbn50hYRiSXdAPtrTtbpSmjbv+gFjM5o5RRWcNG0DPvnGLGq4vH
03ceb4vcLDe5thFSAmgVKOu7P6UoGnBaeWlz29IaMRUt5zTarR8eBCmdYkSr8Elw
+NYX8XopcnPkmoUPHseX9LSjx1O2TJY9W3vV8VqaXiyA0cTV4Wkq0p+GZVfXVqIj
RLiOMFQcaxYlHPiJZovh+AoVpnYopMeC6chPrbVrjj9DJFFGwXVYgZGNYpxbq8oj
8wIruJ

Bug#1011928: trilinos FTBFS: isinf was not defined in this scope

2022-05-26 Thread M. Zhou
Source: trilinos
Version: 13.2.0-1
Severity: serious

This is a side-product of a rebuild test against libtbb-dev/experimental

==> CMakeFiles/CMakeError.log <==   
   
Performing C++ SOURCE FILE Test FINITE_VALUE_HAVE_GLOBAL_ISNAN failed with the 
following output:   
Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp   
   


  
Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_c127c/fast && gmake[2]: 
Entering directory '/<>/obj-
x86_64-linux-gnu/CMakeFiles/CMakeTmp'   
/usr/bin/gmake  -f CMakeFiles/cmTC_c127c.dir/build.make 
CMakeFiles/cmTC_c127c.dir/build
gmake[3]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' 
  
Building CXX object CMakeFiles/cmTC_c127c.dir/src.cxx.o 
   
/usr/bin/mpicxx -DFINITE_VALUE_HAVE_GLOBAL_ISNAN  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -
Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=
2  -O3 -DNDEBUG -std=c++14 -o CMakeFiles/cmTC_c127c.dir/src.cxx.o -c 
/<>/obj-x86_64-linux-
gnu/CMakeFiles/CMakeTmp/src.cxx
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx: In function 
‘int main()’:   
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:6:3: error: 
‘isnan’ was not declared in this scope;
did you mean ‘std::isnan’?  
6 |   isnan(x); 
   
  |   ^ 
   
  |   std::isnan
   
In file included from 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:2:
 
/usr/include/c++/11/cmath:632:5: note: ‘std::isnan’ declared here   
   
  632 | isnan(_Tp __x)  
   
  | ^   
   
gmake[3]: *** [CMakeFiles/cmTC_c127c.dir/build.make:78: 
CMakeFiles/cmTC_c127c.dir/src.cxx.o] Error 1   
gmake[3]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' 
   
gmake[2]: *** [Makefile:127: cmTC_c127c/fast] Error 2   
   
gmake[2]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' 
   



Bug#1011828: [Pkg-javascript-devel] Bug#1011828: node-domutils: FTBFS: node_modules/@types/jest/index.d.ts(503, 30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type dec

2022-05-26 Thread Yadd

On 26/05/2022 20:52, Lucas Nussbaum wrote:

Source: node-domutils
Version: 3.0.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):

  debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
dh_auto_configure --buildsystem=nodejs
Link ./node_modules/htmlparser2 -> /usr/share/nodejs/htmlparser2
Link ./node_modules/pretty-format -> /usr/share/nodejs/pretty-format
Link ./node_modules/ts-jest -> /usr/share/nodejs/ts-jest
Copy /usr/share/nodejs/domhandler -> ./node_modules/
Copy /usr/share/nodejs/dom-serializer -> ./node_modules/
Copy /usr/share/nodejs/domelementtype -> ./node_modules/
Copy /usr/share/nodejs/jest-diff -> ./node_modules/
Copy /usr/share/nodejs/@types/jest -> ./node_modules/@types
Copy /usr/share/nodejs/@types/node -> ./node_modules/@types
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
tsc
node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 
'jest-matcher-utils' or its corresponding type declarations.
make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2


For all such bugs, just move @types/jest from debian/nodejs/extcopies 
into debian/nodejs/extlinks: nodejs has now node_modules links




Bug#1011926: pypy shouldn't be shipped in bookworm

2022-05-26 Thread Adrian Bunk
Package: pypy
Version: 7.3.9+dfsg-1
Severity: serious
Tags: bookworm sid
Control: block -1 by 983470 938168 937510 932820

After all the pain influcted on developers and users by pushing the
Python2 removal before bullseye, it feels absurd that we still ship
at least two Python2 interpreters in both bullseye and bookworm.

As indicated in #932820, the overdue removal of pypy was already
planned 3 years ago as part of the Python2 removal.



Processed: pypy shouldn't be shipped in bookworm

2022-05-26 Thread Debian Bug Tracking System
Processing control commands:

> block -1 by 983470 938168 937510 932820
Bug #1011926 [pypy] pypy shouldn't be shipped in bookworm
1011926 was not blocked by any bugs.
1011926 was not blocking any bugs.
Added blocking bug(s) of 1011926: 983470, 937510, 938168, and 932820

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



Processed: tagging 1006588

2022-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1006588 + fixed
Bug #1006588 {Done: Timo Lindfors } [src:tboot] tboot: 
FTBFS with OpenSSL 3.0
Added tag(s) fixed.
> thanks
Stopping processing here.

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



Processed: tagging 1010311

2022-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1010311 + ftbfs
Bug #1010311 [src:python-duniterpy, src:silkaj] python-duniterpy breaks silkaj 
autopkgtest: cannot import name 'BlockUID' from 'duniterpy.documents'
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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



Processed: oz: diff for NMU version 0.17.0-5.1

2022-05-26 Thread Debian Bug Tracking System
Processing control commands:

> tags 1005145 + patch
Bug #1005145 [oz] oz: FTBFS against python 3.10
Added tag(s) patch.
> tags 1005145 + pending
Bug #1005145 [oz] oz: FTBFS against python 3.10
Added tag(s) pending.

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



Bug#1005145: oz: diff for NMU version 0.17.0-5.1

2022-05-26 Thread Adrian Bunk
Control: tags 1005145 + patch
Control: tags 1005145 + pending

Dear maintainer,

I've prepared an NMU for oz (versioned as 0.17.0-5.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru oz-0.17.0/debian/changelog oz-0.17.0/debian/changelog
--- oz-0.17.0/debian/changelog	2021-08-11 19:06:44.0 +0300
+++ oz-0.17.0/debian/changelog	2022-05-26 18:24:14.0 +0300
@@ -1,3 +1,11 @@
+oz (0.17.0-5.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Upload to unstable.
+  * Add fix for Python 3.10 compatibility. (Closes: #1005145)
+
+ -- Adrian Bunk   Thu, 26 May 2022 18:24:14 +0300
+
 oz (0.17.0-5) experimental; urgency=medium
 
   * [f99cae8] Use Standards-Version: 4.5.1.
diff -Nru oz-0.17.0/debian/patches/0001-ozutil-collections-collections.abc.patch oz-0.17.0/debian/patches/0001-ozutil-collections-collections.abc.patch
--- oz-0.17.0/debian/patches/0001-ozutil-collections-collections.abc.patch	1970-01-01 02:00:00.0 +0200
+++ oz-0.17.0/debian/patches/0001-ozutil-collections-collections.abc.patch	2022-05-26 18:24:14.0 +0300
@@ -0,0 +1,37 @@
+From 2f81e48c478502eca3d228a67f51052201d80639 Mon Sep 17 00:00:00 2001
+From: Dan Bungert 
+Date: Mon, 7 Feb 2022 14:43:51 -0700
+Subject: ozutil: collections -> collections.abc
+
+For python 3.10, some items formerly from collections must now be
+obtained from collections.abc.  This should be backwards compatible.
+https://docs.python.org/3.5/library/collections.abc.html#collections.abc.Callable
+---
+ oz/ozutil.py | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/oz/ozutil.py b/oz/ozutil.py
+index 3a861be..328421b 100644
+--- a/oz/ozutil.py
 b/oz/ozutil.py
+@@ -19,7 +19,7 @@
+ Miscellaneous utility functions.
+ """
+ 
+-import collections
++import collections.abc
+ try:
+ import configparser
+ except ImportError:
+@@ -536,7 +536,7 @@ def copy_modify_file(inname, outname, subfunc):
+ raise Exception("output filename is None")
+ if subfunc is None:
+ raise Exception("subfunction is None")
+-if not isinstance(subfunc, collections.Callable):
++if not isinstance(subfunc, collections.abc.Callable):
+ raise Exception("subfunction is not callable")
+ 
+ infile = open(inname, 'r')
+-- 
+2.20.1
+
diff -Nru oz-0.17.0/debian/patches/series oz-0.17.0/debian/patches/series
--- oz-0.17.0/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ oz-0.17.0/debian/patches/series	2022-05-26 18:24:14.0 +0300
@@ -0,0 +1 @@
+0001-ozutil-collections-collections.abc.patch


Bug#1000612: marked as pending in python-cassandra-driver

2022-05-26 Thread Emmanuel Arias
Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-cassandra-driver/-/commit/416985108815fecff9835460a2ba9621fc6cd66b


d/patches/0005-Skip-test_multi_timer_validation-flaky-test.patch: Skip flaky 
test (Closes: #1000612).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1000612



Processed: Bug#1000612 marked as pending in python-cassandra-driver

2022-05-26 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1000612 [src:python-cassandra-driver] python-cassandra-driver: flaky test
Ignoring request to alter tags of bug #1000612 to the same tags previously set

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



Bug#1000861: marked as done (eggdrop: orig tarball doesn't match the attached upstream signature)

2022-05-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 May 2022 19:40:49 +
with message-id 
and subject line Bug#1000861: fixed in eggdrop 1.8.4+repack1-0.1
has caused the Debian Bug report #1000861,
regarding eggdrop: orig tarball doesn't match the attached upstream signature
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.)


-- 
1000861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eggdrop
Version: 1.8.4-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: simon.cho...@canonical.com

eggdrop_1.8.4.orig.tar.gz doesn't match the attached .asc file, which
causes dpkg-buildpackage to fail. When comparing with the upstream
tarball downloaded from Github (which matches the signature), the only
difference is in the metadata of the files: the upstream tarball records
the file owner as freeder(1002)/freeder(1002) whereas the
Debian-provided one records root(0)/root(0).

A simple workaround is to delete the signature file
'eggdrop_1.8.4.orig.tar.gz.asc', but that kind of defeats the purpose of
having the signature file in the first place ;-).

I'm guessing a 1.8.4+repack-1 version with the proper tarball would fix
things?

Cheers,
Simon

-- System Information:
Debian Release: 11.0
  APT prefers impish-updates
  APT policy: (500, 'impish-updates'), (500, 'impish-security'), (500, 
'impish-proposed'), (500, 'impish'), (100, 'impish-backports'), (90, 
'jammy-proposed'), (90, 'jammy')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.13.0-22-generic (SMP w/24 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: eggdrop
Source-Version: 1.8.4+repack1-0.1
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated eggdrop 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: Mon, 23 May 2022 15:04:58 -0400
Source: eggdrop
Architecture: source
Version: 1.8.4+repack1-0.1
Distribution: unstable
Urgency: high
Maintainer: Cédric Barboiron 
Changed-By: Boyuan Yang 
Closes: 1000861
Changes:
 eggdrop (1.8.4+repack1-0.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Repack upstream tarball with no file change. This solves the
 broken upstream tarball signature that causes FTBFS.
 (Closes: #1000861)
Checksums-Sha1:
 1ed7e03ca25ea0c951d5f6aba5c7409815d4dbe8 1961 eggdrop_1.8.4+repack1-0.1.dsc
 e1c344207b7bc2f8703f915a31d8135c016892f4 1766976 
eggdrop_1.8.4+repack1.orig.tar.gz
 0618b5bd04765707aee358172fb324831b0daaf2 15400 
eggdrop_1.8.4+repack1-0.1.debian.tar.xz
 a03bc8aa288fabb8660674ebb8fd226aa54985bb 6554 
eggdrop_1.8.4+repack1-0.1_amd64.buildinfo
Checksums-Sha256:
 11731183dcbb8d8552c2b84c56cca401c22fb0540c55000c18b59f6535a946e5 1961 
eggdrop_1.8.4+repack1-0.1.dsc
 715d50aeebf379a172c0572a1708b082654decd461f3c67c74142bdf8e880662 1766976 
eggdrop_1.8.4+repack1.orig.tar.gz
 61fbe3e41d3b57d52779babc0922b6bd7e8257f08e13edf1cdfe5a5d8f0ad554 15400 
eggdrop_1.8.4+repack1-0.1.debian.tar.xz
 7586137e4e79383454707585ee62fe4039b31f18d58fdda177084d3174648bc2 6554 
eggdrop_1.8.4+repack1-0.1_amd64.buildinfo
Files:
 0657ce3b42a72c4dec39bb74235385fe 1961 net optional 
eggdrop_1.8.4+repack1-0.1.dsc
 97dc7beb60f0442eda0a69262f75be64 1766976 net optional 
eggdrop_1.8.4+repack1.orig.tar.gz
 a13e27eface95e955529c2784ed3f02c 15400 net optional 
eggdrop_1.8.4+repack1-0.1.debian.tar.xz
 b6a8098f40bab7dea988fe4ce47b670a 6554 net optional 
eggdrop_1.8.4+repack1-0.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmKL20sACgkQwpPntGGC
Ws5vmBAAnoBfL1xd/KyLwjhK+LjNyLUfz7RqjxWflCRHxXvtLlsjlV8SnLR4Qxki
jYwr

Processed (with 1 error): tagging 1011786, forcibly merging 1011786 1007203

2022-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1011786 + patch
Bug #1011786 [src:php-symfony-polyfill] php-symfony-polyfill: FTBFS: make[1]: 
*** [debian/rules:53: override_dh_auto_test] Error 1
Added tag(s) patch.
> forcemerge 1011786 1007203
Bug #1011786 [src:php-symfony-polyfill] php-symfony-polyfill: FTBFS: make[1]: 
*** [debian/rules:53: override_dh_auto_test] Error 1
Unable to merge bugs because:
package of #1007203 is 'php-symfony-polyfill' not 'src:php-symfony-polyfill'
Failed to forcibly merge 1011786: Did not alter merged bugs.

> thanks
Stopping processing here.

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



Processed: limit source to php-twig, tagging 1011899

2022-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> limit source php-twig
Limiting to bugs with field 'source' containing at least one of 'php-twig'
Limit currently set to 'source':'php-twig'

> tags 1011899 + pending
Bug #1011899 [src:php-twig] php-twig: FTBFS: make[1]: *** [debian/rules:92: 
override_dh_auto_test] Error 1
Added tag(s) pending.
> thanks
Stopping processing here.

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



Processed: merging 1011897 1011754

2022-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> merge 1011897 1011754
Bug #1011897 [src:interimap] interimap: FTBFS: tests fail
Bug #1011754 [src:interimap] interimap: autopkgtest failure with openssl 3
Added tag(s) ftbfs.
Merged 1011754 1011897
> thanks
Stopping processing here.

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



Processed: forcibly merging 1010972 1011919

2022-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forcemerge 1010972 1011919
Bug #1010972 [src:libmojolicious-plugin-authentication-perl] 
libmojolicious-perl breaks libmojolicious-plugin-authentication-perl 
autopkgtest: Your secret passphrase needs to be changed
Bug #1011919 [src:libmojolicious-plugin-authentication-perl] 
libmojolicious-plugin-authentication-perl: FTBFS: dh_auto_test: error: make -j8 
test TEST_VERBOSE=1 returned exit code 2
Set Bug forwarded-to-address to 
'https://github.com/benvanstaveren/Mojolicious-Plugin-Authentication/issues/34'.
Added tag(s) confirmed and upstream.
Merged 1010972 1011919
> thanks
Stopping processing here.

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



Bug#1011918: ktimer: FTBFS: make: *** [debian/rules:6: binary] Error 2

2022-05-26 Thread Lucas Nussbaum
Source: ktimer
Version: 4:21.12.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with kf5
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=kf5
>   cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
> -DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DKDE_INSTALL_USE_QT_SYS_PATHS=ON ..
> -- The C compiler identification is GNU 11.3.0
> -- The CXX compiler identification is GNU 11.3.0
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Looking for __GLIBC__
> -- Looking for __GLIBC__ - found
> -- Performing Test _OFFT_IS_64BIT
> -- Performing Test _OFFT_IS_64BIT - Success
> -- Performing Test HAVE_DATE_TIME
> -- Performing Test HAVE_DATE_TIME - Success
> -- Performing Test BSYMBOLICFUNCTIONS_AVAILABLE
> -- Performing Test BSYMBOLICFUNCTIONS_AVAILABLE - Success
> CMake Error at /usr/share/ECM/kde-modules/KDEMetaInfoPlatformCheck.cmake:24 
> (file):
>   file STRINGS file "/<>/metainfo.yaml"
>   cannot be read.
> Call Stack (most recent call first):
>   /usr/share/ECM/kde-modules/KDEFrameworkCompilerSettings.cmake:71 (include)
>   CMakeLists.txt:16 (include)
> 
> 
> CMake Error at /usr/share/ECM/kde-modules/KDEMetaInfoPlatformCheck.cmake:69 
> (message):
>   Your current platform 'Linux' is not supported.  The list of supported
>   platorms is ''.If you think this is a mistake or you are working on
>   enabling the platform please build with the KF_IGNORE_PLATFORM_CHECK
>   variable set to true
> Call Stack (most recent call first):
>   /usr/share/ECM/kde-modules/KDEFrameworkCompilerSettings.cmake:71 (include)
>   CMakeLists.txt:16 (include)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt
> ==> CMakeCache.txt <==
> # This is the CMakeCache file.
> # For build in directory: /<>/obj-x86_64-linux-gnu
> # It was generated by CMake: /usr/bin/cmake
> # You can edit this file to change values found and used by cmake.
> # If you do not want to change any of the values, simply exit the editor.
> # If you do want to change a value, simply edit, save, and exit the editor.
> # The syntax for the file is as follows:
> # KEY:TYPE=VALUE
> # KEY is the name of a variable in the cache.
> # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
> # VALUE is the current value for the KEY.
> 
> 
> # EXTERNAL cache entries
> 
> 
> //Build the project with gcov support
> BUILD_COVERAGE:BOOL=OFF
> 
> //Build against Qt 6
> BUILD_WITH_QT6:BOOL=OFF
> 
> //Path to a program.
> CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line
> 
> //Path to a program.
> CMAKE_AR:FILEPATH=/usr/bin/ar
> 
> //Choose the type of build, options are: None Debug Release RelWithDebInfo
> // MinSizeRel ...
> CMAKE_BUILD_TYPE:STRING=Debian
> 
> //Enable/Disable color output during build.
> CMAKE_COLOR_MAKEFILE:BOOL=ON
> 
> //CXX compiler
> CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++
> 
> //A wrapper around 'ar' adding the appropriate '--plugin' option
> // for the GCC compiler
> CMAKE_CXX_COMPILER_AR:FILEPATH=/usr/bin/gcc-ar-11
> 
> //A wrapper around 'ranlib' adding the appropriate '--plugin' option
> // for the GCC compiler
> CMAKE_CXX_COMPILER_RANLIB:FILEPATH=/usr/bin/gcc-ranlib-11
> 
> //Flags used by the CXX compiler during all build types.
> CMAKE_CXX_FLAGS:STRING=-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2
> 
> //Flags used by the CXX compiler during DEBIAN builds.
> CMAKE_CXX_FLAGS_DEBIAN:STRING=
> 
> //Flags used by the CXX compiler during DEBUG builds.
> CMAKE_CXX_FLAGS_DEBUG:STRING=-g
> 
> //Flags used by the CXX compiler during MINSIZEREL builds.
> CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG
> 
> //Flags used by the CXX compiler during RELEASE builds.
> CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG
> 
> //Flags used by the CXX compiler

Bug#1011919: libmojolicious-plugin-authentication-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2

2022-05-26 Thread Lucas Nussbaum
Source: libmojolicious-plugin-authentication-perl
Version: 1.37-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 
> 'blib/arch')" t/*.t
> t/00-load.t . 
> 1..1
> ok 1 - use Mojolicious::Plugin::Authentication;
> ok
> # 
> # Versions for all modules listed in MYMETA.json (including optional ones):
> # 
> # === Configure Requires ===
> # 
> # Module  Want Have
> # ---  
> # ExtUtils::MakeMaker  any 7.62
> # 
> # === Build Requires ===
> # 
> # Module  Want Have
> # ---  
> # ExtUtils::MakeMaker  any 7.62
> # 
> # === Test Requires ===
> # 
> # Module  Want Have
> # ---  
> # ExtUtils::MakeMaker  any 7.62
> # File::Spec   any 3.80
> # Test::More  0.96 1.302183
> # 
> # === Test Recommends ===
> # 
> # Module Want Have
> # --  
> # CPAN::Meta 2.120900 2.150010
> # 
> # === Runtime Requires ===
> # 
> # Module  Want Have
> # ---  
> # Exporter any 5.76
> # Mojolicious  8.0 9.25
> # 
> t/00-report-prereqs.t ... 
> 1..1
> ok 1 - Reported prereqs
> ok
> [2022-05-25 21:25:23.78460] [983173] [trace] Your secret passphrase needs to 
> be changed
> [2022-05-25 21:25:23.78553] [983173] [trace] [lRDmb9s18kZA] GET "/"
> [2022-05-25 21:25:23.78580] [983173] [trace] [lRDmb9s18kZA] Routing to a 
> callback
> [2022-05-25 21:25:23.78599] [983173] [trace] [lRDmb9s18kZA] 200 OK (0.00045s, 
> .222/s)
> [2022-05-25 21:25:23.78839] [983173] [trace] [HycFDYGGLnUN] GET "/authonly"
> [2022-05-25 21:25:23.78861] [983173] [trace] [HycFDYGGLnUN] Routing to a 
> callback
> [2022-05-25 21:25:23.78875] [983173] [trace] [HycFDYGGLnUN] 200 OK 
> (0.000349s, 2865.330/s)
> [2022-05-25 21:25:23.79056] [983173] [trace] [xHCuGyN-pK7b] GET 
> "/condition/authonly"
> [2022-05-25 21:25:23.79173] [983173] [trace] [xHCuGyN-pK7b] Template 
> "not_found.development.html.ep" not found
> [2022-05-25 21:25:23.79186] [983173] [trace] [xHCuGyN-pK7b] Template 
> "not_found.html.ep" not found
> [2022-05-25 21:25:23.79194] [983173] [trace] [xHCuGyN-pK7b] Rendering 
> template "mojo/debug.html.ep"
> [2022-05-25 21:25:23.80357] [983173] [trace] [xHCuGyN-pK7b] 404 Not Found 
> (0.012993s, 76.965/s)
> [2022-05-25 21:25:23.80580] [983173] [trace] [cH_0LLtLvypC] POST "/login"
> [2022-05-25 21:25:23.80598] [983173] [trace] [cH_0LLtLvypC] Routing to a 
> callback
> [2022-05-25 21:25:23.80617] [983173] [trace] [cH_0LLtLvypC] 200 OK 
> (0.000358s, 2793.296/s)
> [2022-05-25 21:25:23.80808] [983173] [trace] [FyXD_XEEnvF6] GET "/authonly"
> [2022-05-25 21:25:23.80825] [983173] [trace] [FyXD_XEEnvF6] Routing to a 
> callback
> [2022-05-25 21:25:23.80837] [983173] [trace] [FyXD_XEEnvF6] 200 OK 
> (0.000284s, 3521.127/s)
> [2022-05-25 21:25:23.81005] [983173] [trace] [VUX2mXK_exbc] POST "/login"
> [2022-05-25 21:25:23.81021] [983173] [trace] [VUX2mXK_exbc] Routing to a 
> callback
> [2022-05-25 21:25:23.81041] [983173] [trace] [VUX2mXK_exbc] 200 OK 
> (0.000351s, 2849.003/s)
> [2022-05-25 21:25:23.81305] [983173] [trace] [aBpwSoyzPyhm] GET "/authonly"
> [2022-05-25 21:25:23.81322] [983173] [trace] [aBpwSoyzPyhm] Routing to a 
> callback
> [2022-05-25 21:25:23.81334] [983173] [trace] [aBpwSoyzPyhm] 200 OK 
> (0.000278s, 3597.122/s)
> [2022-05-25 21:25:23.81585] [983173] [trace] [HQI0nKFR06uu] GET 
> "/condition/authonly"
> [2022-05-25 21:25:23.81604] [983173] [trace] [HQI0nKFR06uu] Routing to a 
> callback
> [2022-05-25 21:25:23.81615] [983173] [trace] [HQI0nKFR06uu] 200 OK 
> (0.000289s, 3460.208/s)
> [2022-05-25 21:25:23.81844] [983173] [trace] [QlNtjbXtR5eD] GET "/logout"
> [2022-05-25 21:25:23.81861] [983173] [trace] [QlNtjbXtR5eD] Routing to a 
> callback
> [2022-05-25 21:25:23.81872] [983173] [trace] [QlNtjbXtR5eD] 200 OK 
> (0.000274s, 3649.635/s)
> [2022-05-25 21:25:23.82108] [983173] [trace] [GwtST8vGYoft] GET "/authonly"
> [2022-05-25 21:25:23.82123] [983173] [trace] [GwtST8vGYoft] Routing to a 
> callback
> [2022-05-25 21:25:23.82134] [983173] [trace] [GwtST8vGYoft] 200 OK (0.00026s, 
> 3846.154/s)
> [2022-05-25 21:25:23.82334] [983173] [trace] [2JwyP8NdR5xc] POST "/login2"
> [2022-05-25 21:25:23.82358] [983173] [trace] [2JwyP8NdR5xc] Routing to a 
> callback
> [2022-05-25 21:25:23.82383] [983173] [trace] [2JwyP8NdR5xc] 200 OK 
> (0.000489s, 2044.990/s)
> [2022-05-25 21:25:23.82609] [983173] [trace] [3QpsZommcfLf] GET "/authonly"
> [2022-05-25 21:25:23.82625] [983173] [trace] [3QpsZommcfLf] Routing to a 
> callb

Bug#1011917: node-pbkdf2: FTBFS: TypeError: Cannot read properties of undefined (reading 'toString')

2022-05-26 Thread Lucas Nussbaum
Source: node-pbkdf2
Version: 3.1.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> Link node_modules/@types/pbkdf2 -> ../../types-pbkdf2
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/pbkdf2
>   /bin/sh -ex debian/tests/pkg-js/test
> + tape test/index.js
> TAP version 13
> # JavaScript pbkdf2 defaults to sha1 and handles buffers
> ok 1 should be strictly equal
> ok 2 null
> ok 3 should be strictly equal
> # JavaScript pbkdf2 should throw if no callback is provided
> ok 4 should throw
> # JavaScript pbkdf2 should throw if the password is not a string or an 
> ArrayBuffer
> ok 5 should throw
> ok 6 should throw
> # JavaScript pbkdf2 should throw if the salt is not a string or an ArrayBuffer
> ok 7 should throw
> ok 8 should throw
> # JavaScript pbkdf2 async w/ sha1 encodes "password" (string) with salt 
> "salt" (string) with sha1 to 
> 0c60c80f961f0e71f3a9b524af6012062fe037a6e0f0eb94fe8fc46bdc637164
> ok 9 null
> ok 10 should be strictly equal
> # JavaScript pbkdf2sync w/ sha1 encodes "password" (string) with salt "salt" 
> (string) with sha1 to 
> 0c60c80f961f0e71f3a9b524af6012062fe037a6e0f0eb94fe8fc46bdc637164
> ok 11 should be strictly equal
> # JavaScript pbkdf2 async w/ sha1 encodes "password" (string) with salt 
> "salt" (string) with sha1 to 
> ea6c014dc72d6f8ccd1ed92ace1d41f0d8de8957cae93136266537a8d7bf4b76
> ok 12 null
> ok 13 should be strictly equal
> # JavaScript pbkdf2sync w/ sha1 encodes "password" (string) with salt "salt" 
> (string) with sha1 to 
> ea6c014dc72d6f8ccd1ed92ace1d41f0d8de8957cae93136266537a8d7bf4b76
> ok 14 should be strictly equal
> # JavaScript pbkdf2 async w/ sha1 encodes "password" (string) with salt 
> "salt" (string) with sha1 to 
> 0c60c80f961f0e71f3a9b524af6012062fe037a6e0f0eb94fe8fc46bdc637164ac2e7a8e3f9d2e83ace57e0d50e5e1071367c179bc86c767fc3f78ddb561363f
> ok 15 null
> ok 16 should be strictly equal
> # JavaScript pbkdf2sync w/ sha1 encodes "password" (string) with salt "salt" 
> (string) with sha1 to 
> 0c60c80f961f0e71f3a9b524af6012062fe037a6e0f0eb94fe8fc46bdc637164ac2e7a8e3f9d2e83ace57e0d50e5e1071367c179bc86c767fc3f78ddb561363f
> ok 17 should be strictly equal
> # JavaScript pbkdf2 async w/ sha1 encodes "password" (string) with salt 
> "salt" (string) with sha1 to 
> ea6c014dc72d6f8ccd1ed92ace1d41f0d8de8957cae93136266537a8d7bf4b76c51094cc1ae010b19923ddc4395cd064acb023ffd1edd5ef4be8ffe61426c28e
> ok 18 null
> ok 19 should be strictly equal
> # JavaScript pbkdf2sync w/ sha1 encodes "password" (string) with salt "salt" 
> (string) with sha1 to 
> ea6c014dc72d6f8ccd1ed92ace1d41f0d8de8957cae93136266537a8d7bf4b76c51094cc1ae010b19923ddc4395cd064acb023ffd1edd5ef4be8ffe61426c28e
> ok 20 should be strictly equal
> # JavaScript pbkdf2 async w/ sha1 encodes "password" (string) with salt 
> "salt" (string) with sha1 to 
> 4b007901b765489abead49d926f721d065a429c12e463f6c4cd79401085b03db
> ok 21 null
> ok 22 should be strictly equal
> # JavaScript pbkdf2sync w/ sha1 encodes "password" (string) with salt "salt" 
> (string) with sha1 to 
> 4b007901b765489abead49d926f721d065a429c12e463f6c4cd79401085b03db
> ok 23 should be strictly equal
> # JavaScript pbkdf2 async w/ sha1 encodes "passwordPASSWORDpassword" (string) 
> with salt "saltSALTsaltSALTsaltSALTsaltSALTsalt" (string) with sha1 to 
> 3d2eec4fe41c849b80c8d83662c0e44a8b291a964cf2f07038b6b89a48612c5a25284e6605e12329
> ok 24 null
> ok 25 should be strictly equal
> # JavaScript pbkdf2sync w/ sha1 encodes "passwordPASSWORDpassword" (string) 
> with salt "saltSALTsaltSALTsaltSALTsaltSALTsalt" (string) with sha1 to 
> 3d2eec4fe41c849b80c8d83662c0e44a8b291a964cf2f07038b6b89a48612c5a25284e6605e12329
> ok 26 should be strictly equal
> # JavaScript pbkdf2 async w/ sha1 encodes "pass0word" (string) with salt 
> "sa0lt" (string) with sha1 to 345cbad979dfccb90cac5257bea6ea46
> ok 27 null
> ok 28 should be strictly equal
> # JavaScript pbkdf2sync w/ sha1 encodes "pass0word" (string) with salt 
> "sa0lt" (string) with sha1 to 345cbad979dfccb90cac5257bea6ea46
> ok 29 should be strictly equal
> # JavaScript pbkdf2 async w/ sha1 encodes "c���̻�" (hex) with salt "salt" 
> (string) with sha1 to 
> f6635023b135a57fb8caa89ef8ad93a29d9debb1b011e6e88bffbb212de7c01c
> ok 30 null
> ok 31 should be strictly equal
> # JavaScript pbkdf2sync w/ sha1 encodes "c���̻�" (hex) with salt "salt" 
> (string) with sha1 to 
> f6635023b135a57fb8caa89ef8ad93a29d9debb1b011e6e88bffbb212de7c01c
> ok 32 should be strictly equal
> # JavaScript pbkdf2 async w/ sha1 encodes "abandon abandon a

Bug#1011916: poolcounter: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2

2022-05-26 Thread Lucas Nussbaum
Source: poolcounter
Version: 1.1.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> /usr/bin/pytest /usr/bin/pytest-3 -v
> = test session starts 
> ==
> platform linux -- Python 3.10.4, pytest-6.2.5, py-1.10.0, pluggy-1.0.0 -- 
> /usr/bin/python3
> cachedir: .pytest_cache
> rootdir: /usr/bin
> collecting ... ERROR: not found: /usr/bin/pytest-3
> (no name '/usr/bin/pytest-3' in any of [])
> 
> collected 0 items
> 
> === warnings summary 
> ===
> ../../../usr/lib/python3/dist-packages/_pytest/cacheprovider.py:428
>   /usr/lib/python3/dist-packages/_pytest/cacheprovider.py:428: 
> PytestCacheWarning: could not create cache path 
> /usr/bin/.pytest_cache/v/cache/nodeids
> config.cache.set("cache/nodeids", sorted(self.cached_nodeids))
> 
> ../../../usr/lib/python3/dist-packages/_pytest/stepwise.py:49
>   /usr/lib/python3/dist-packages/_pytest/stepwise.py:49: PytestCacheWarning: 
> could not create cache path /usr/bin/.pytest_cache/v/cache/stepwise
> session.config.cache.set(STEPWISE_CACHE_DIR, [])
> 
> -- Docs: https://docs.pytest.org/en/stable/warnings.html
> = 2 warnings in 0.00s 
> ==
> make[1]: *** [Makefile:28: test] Error 4
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j8 test returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/poolcounter_1.1.3-1_unstable.log

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

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

If you reassign this bug to another package, please 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.



Bug#1011915: haskell-pango: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25

2022-05-26 Thread Lucas Nussbaum
Source: haskell-pango
Version: 0.13.8.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-pango-doc.substvars
> dh_installdirs -plibghc-pango-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe; haddock_recipe; build_recipe; check_recipe'
> Running find . ! -newer /tmp/0A9vYeHDz8 -exec touch -d "1998-01-01 UTC" {} ;
> Running dh_listpackages
> libghc-pango-dev
> libghc-pango-prof
> libghc-pango-doc
> Running dh_listpackages
> libghc-pango-dev
> libghc-pango-prof
> libghc-pango-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/pango-0.13.8.1/ --datasubdir=pango 
> --htmldir=/usr/share/doc/libghc-pango-doc/html/ --enable-library-profiling
> Using Parsec parser
> Configuring pango-0.13.8.1...
> Flags chosen: new-exception=True
> Dependency array -any: using array-0.5.4.0
> Dependency base ==4.*: using base-4.13.0.0
> Dependency cairo >=0.13.0.0 && <0.14: using cairo-0.13.8.1
> Dependency containers -any: using containers-0.6.2.1
> Dependency directory -any: using directory-1.3.6.0
> Dependency glib >=0.13.0.0 && <0.14: using glib-0.13.8.1
> Dependency mtl -any: using mtl-2.2.2
> Dependency pretty -any: using pretty-1.1.3.6
> Dependency process -any: using process-1.6.9.0
> Dependency text >=0.11.0.6 && <1.3: using text-1.2.4.0
> Dependency cairo ==1.2.0 || >1.2.0: using version 1.16.0
> Dependency pangocairo ==1.10 || >1.10: using version 1.50.7
> Dependency pango ==1.0 || >1.0: using version 1.50.7
> Source component graph: component lib
> Configured component graph:
> component pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o
> include array-0.5.4.0
> include base-4.13.0.0
> include cairo-0.13.8.1-9ROOXD4as1uLn8sCpDXiTi
> include containers-0.6.2.1
> include directory-1.3.6.0
> include glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx
> include mtl-2.2.2
> include pretty-1.1.3.6
> include process-1.6.9.0
> include text-1.2.4.0
> Linked component graph:
> unit pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o
> include array-0.5.4.0
> include base-4.13.0.0
> include cairo-0.13.8.1-9ROOXD4as1uLn8sCpDXiTi
> include containers-0.6.2.1
> include directory-1.3.6.0
> include glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx
> include mtl-2.2.2
> include pretty-1.1.3.6
> include process-1.6.9.0
> include text-1.2.4.0
> 
> Graphics.Rendering.Pango=pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o:Graphics.Rendering.Pango,Graphics.Rendering.Pango.Attributes=pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o:Graphics.Rendering.Pango.Attributes,Graphics.Rendering.Pango.BasicTypes=pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o:Graphics.Rendering.Pango.BasicTypes,Graphics.Rendering.Pango.Cairo=pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o:Graphics.Rendering.Pango.Cairo,Graphics.Rendering.Pango.Context=pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o:Graphics.Rendering.Pango.Context,Graphics.Rendering.Pango.Enums=pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o:Graphics.Rendering.Pango.Enums,Graphics.Rendering.Pango.Font=pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o:Graphics.Rendering.Pango.Font,Graphics.Rendering.Pango.Layout=pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o:Graphics.Rendering.Pango.Layout,Graphics.Rendering.Pango.Markup=pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o:Graphics.Rendering.Pango.Markup,Graphics.Rendering.Pango.Rendering=pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o:Graphics.Rendering.Pango.Rendering,Graphics.Rendering.Pango.Structs=pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o:Graphics.Rendering.Pango.Structs,Graphics.Rendering.Pango.Types=pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o:Graphics.Rendering.Pango.Types
> Ready component graph:
> definite pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o
> depends array-0.5.4.0
> depends base-4.13.0.0
> depends cairo-0.13.8.1-9ROOXD4as1uLn8sCpDXiTi
> depends containers-0.6.2.1
> depends directory-1.3.6.0
> depends glib-0.13.8.1-CNR5m0

Bug#1011914: lsof: FTBFS: make[2]: *** [Makefile:28: all] Error 1

2022-05-26 Thread Lucas Nussbaum
Source: lsof
Version: 4.95.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/tests'
> `cat config.cc`  -I. -I.. `cat config.cflags` -c LTlib.c \
> -o LTlib.o
> `cat config.cc`  -I. -I.. `cat config.cflags` LTbasic.c \
> LTlib.o `cat config.xobj` -o LTbasic
> `cat config.cc`  -I. -I.. `cat config.cflags` LTnlink.c \
> LTlib.o `cat config.xobj` -o LTnlink
> `cat config.cc`  -I. -I.. `cat config.cflags` LTsock.c \
> LTlib.o `cat config.xobj` -o LTsock `cat config.ldflags`
> `cat config.cc`  -I. -I.. `cat config.cflags` LTszoff.c \
> LTlib.o `cat config.xobj` -o LTszoff
> `cat config.cc`  -I. -I.. `cat config.cflags` LTunix.c \
> LTlib.o `cat config.xobj` -o LTunix `cat config.ldflags`
> /<>/tests
> 
> Basic test:
> LTbasic ... OK
> 
> Standard tests:
> LTnlink ... OK
> LTsock ... ERROR!!!  can't get IP address for ip-10-84-234-90
>Errno 0: Success
> LTszoff ... OK
> LTunix ... OK
> Failed tests: 1
> 
> See 00FAQ and 00TEST for more information.
> make[2]: *** [Makefile:28: all] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/lsof_4.95.0-1_unstable.log

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

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

If you reassign this bug to another package, please 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.



Bug#1011913: haskell-swish: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25

2022-05-26 Thread Lucas Nussbaum
Source: haskell-swish
Version: 0.10.1.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-swish-doc.substvars
> dh_installdirs -plibghc-swish-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe; haddock_recipe; build_recipe; check_recipe'
> Running find . ! -newer /tmp/imU_Njjw2l -exec touch -d "1998-01-01 UTC" {} ;
> Running dh_listpackages
> swish
> libghc-swish-dev
> libghc-swish-doc
> libghc-swish-prof
> Running dh_listpackages
> swish
> libghc-swish-dev
> libghc-swish-doc
> libghc-swish-prof
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/swish-0.10.1.0/ --datasubdir=swish 
> --htmldir=/usr/share/doc/libghc-swish-doc/html/ --enable-library-profiling
> Using Parsec parser
> Configuring swish-0.10.1.0...
> Flags chosen: network-uri=True, w3ctests=False
> Dependency base >=4.8 && <4.17: using base-4.13.0.0
> Dependency containers >=0.5 && <0.7: using containers-0.6.2.1
> Dependency directory >=1.0 && <1.4: using directory-1.3.6.0
> Dependency filepath >=1.1 && <1.5: using filepath-1.4.2.1
> Dependency hashable ==1.1.* || >=1.2.0.6 && <1.5: using hashable-1.3.0.0
> Dependency intern >=0.8 && <1.0: using intern-0.9.4
> Dependency mtl ==2.*: using mtl-2.2.2
> Dependency network-uri >=2.6 && <2.8: using network-uri-2.6.3.0
> Dependency old-locale ==1.0.*: using old-locale-1.0.0.7
> Dependency polyparse >=1.6 && <1.14: using polyparse-1.13
> Dependency text >=0.11 && <2.1: using text-1.2.4.0
> Dependency time >=1.1 && <1.9 || >=1.9.1 && <1.14: using time-1.9.3
> Dependency base -any: using base-4.13.0.0
> Dependency swish -any: using swish-0.10.1.0
> Source component graph:
> component lib
> component exe:Swish dependency lib
> Configured component graph:
> component swish-0.10.1.0-Kawc1ubQ52B9qGYTs7vWTz
> include base-4.13.0.0
> include containers-0.6.2.1
> include directory-1.3.6.0
> include filepath-1.4.2.1
> include hashable-1.3.0.0-AOP4LTmShW4Dax9brHgY53
> include intern-0.9.4-m004RHcdtDDlNtFZdgm3E
> include mtl-2.2.2
> include network-uri-2.6.3.0-CPjS2hnZr1IIlGhZ1dITqG
> include old-locale-1.0.0.7-KOGgqu8HfWChZyQBUEp1c
> include polyparse-1.13-4iUooCvGMcnC0mPzTcZKJt
> include text-1.2.4.0
> include time-1.9.3
> component swish-0.10.1.0-ExQXwXGM3Nh5lYjcuuCptL-Swish
> include base-4.13.0.0
> include swish-0.10.1.0-Kawc1ubQ52B9qGYTs7vWTz
> Linked component graph:
> unit swish-0.10.1.0-Kawc1ubQ52B9qGYTs7vWTz
> include base-4.13.0.0
> include containers-0.6.2.1
> include directory-1.3.6.0
> include filepath-1.4.2.1
> include hashable-1.3.0.0-AOP4LTmShW4Dax9brHgY53
> include intern-0.9.4-m004RHcdtDDlNtFZdgm3E
> include mtl-2.2.2
> include network-uri-2.6.3.0-CPjS2hnZr1IIlGhZ1dITqG
> include old-locale-1.0.0.7-KOGgqu8HfWChZyQBUEp1c
> include polyparse-1.13-4iUooCvGMcnC0mPzTcZKJt
> include text-1.2.4.0
> include time-1.9.3
> 
> Data.Interned.URI=swish-0.10.1.0-Kawc1ubQ52B9qGYTs7vWTz:Data.Interned.URI,Data.Ord.Partial=swish-0.10.1.0-Kawc1ubQ52B9qGYTs7vWTz:Data.Ord.Partial,Data.String.ShowLines=swish-0.10.1.0-Kawc1ubQ52B9qGYTs7vWTz:Data.String.ShowLines,Network.URI.Ord=swish-0.10.1.0-Kawc1ubQ52B9qGYTs7vWTz:Network.URI.Ord,Swish=swish-0.10.1.0-Kawc1ubQ52B9qGYTs7vWTz:Swish,Swish.Commands=swish-0.10.1.0-Kawc1ubQ52B9qGYTs7vWTz:Swish.Commands,Swish.Datatype=swish-0.10.1.0-Kawc1ubQ52B9qGYTs7vWTz:Swish.Datatype,Swish.GraphClass=swish-0.10.1.0-Kawc1ubQ52B9qGYTs7vWTz:Swish.GraphClass,Swish.GraphMatch=swish-0.10.1.0-Kawc1ubQ52B9qGYTs7vWTz:Swish.GraphMatch,Swish.GraphMem=swish-0.10.1.0-Kawc1ubQ52B9qGYTs7vWTz:Swish.GraphMem,Swish.GraphPartition=swish-0.10.1.0-Kawc1ubQ52B9qGYTs7vWTz:Swish.GraphPartition,Swish.Monad=swish-0.10.1.0-Kawc1ubQ52B9qGYTs7vWTz:Swish.Monad,Swish.Namespace=swish-0.10.1.0-Kawc1ubQ52B9qGYTs7vWTz:Swish.Namespace,

Bug#1011912: node-mimic-response: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

2022-05-26 Thread Lucas Nussbaum
Source: node-mimic-response
Version: 3.1.0-7
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> Link ./node_modules/iconv -> /usr/lib/x86_64-linux-gnu/nodejs/iconv
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../debian/tests/test_modules/create-cert node_modules/create-cert
>   ln -s ../debian/tests/test_modules/create-test-server 
> node_modules/create-test-server
>   ln -s ../debian/tests/test_modules/es6-promisify 
> node_modules/es6-promisify
>   ln -s ../debian/tests/test_modules/p-event node_modules/p-event
>   ln -s ../debian/tests/test_modules/pem node_modules/pem
>   ln -s ../. node_modules/mimic-response
>   /bin/sh -ex debian/tests/pkg-js/test
> + NODE_PATH=node_modules jest --ci --testRegex test.js
> FAIL ./test.js
>   ● normal
> 
> RSA PRIVATE KEY not found from openssl output:
> ---stdout---
> -BEGIN PRIVATE KEY-
> MIIEvAIBADANBgkqhkiG9w0BAQEFAASCBKYwggSiAgEAAoIBAQDDyWaLW3EZC+f2
> veMpcy3UQFUzr5HXwRSZz2pa/2gGwo6b7e6XqVv0tXCOu46k/mXS0Me3xMcj4WsE
> TC0JwojputSl3rsZ6lBTTLpAw5X1NA5rrMrKbcuSJdUPG+wMKPuZf4pZk5HlmGPL
> P3MRQUZLTreOvvoXjrfKFk5/xV97EPUUMgEW83bwfnd2CFgckVEq64sx+I43kKA8
> c11WRq0QQlB+/aVEUUKSlq8yb4bYtt6aeYSnb0wSml+L30SrIJo0XR2MDA4a5tgA
> QIeFxoUx71rHuV2AiubG89cttOia3M7xbA8qRbhHnSVx/qo7bqdUwbZfAPMGBKqW
> ABX5vgqlAgMBAAECggEACWclTSEVo/HN8Kw6+jUlaNG0JdjTRMzpm995yKgGi3iR
> l8yMDm2cVHrYToqUdbkgE8liJiHFvKPpW1n7OcJFiBAogVTaoIp/1BhVw6GBFLcs
> 0CAK10EBq2G0w1aAdi8LsloNP3MWaTPx6wN/l78OTLSZnTnv0ezRR9vdZkaI6OSY
> gYQMrf8+foRxPti+J+sPI4QltVMm3/+q5v1aePTFGKIBSpCtF0s5iIl4aiDXhvTF
> 9dk29D0U07K/nOt2gzIfuDu4chhmq+WmlFuGeIxDB0qwaHKgeH/3U7vFWFq3c4sj
> 80cOmvv71pooQX9T74U50pT9wY6Pl/1ISmKUon+CQQKBgQDMvkglbEQoF9o+nn7Q
> k413C0Y6QngeS+z3QXjEQMQBnlplP3BC0XHbSzRv56XhIthVB6ysH/PZIMajCQLm
> UZ5DQUigh2L41cm4f1yLDtcHOdmOGgYCitlU0uVpWUiXG4gU8Pedkjj0u1oWoFtJ
> 8oK/2Vp4lIExsrDSP6kOv0fFRQKBgQD0zRrDypL2sv0jyyJ6gjTFIhprXxqXHISO
> xyXpYGZSBpO0DqHePfrJWMn+QdxXcUerPGiobHnwYVSV3RhbsYB50Bxxzx0/YH9L
> qtnAg+OxPv21Uwzzp54lMWpKMfPgvyvGc94ltKGzmXBALSHwGK1UhsO7U6TKbkzJ
> cH/bQr8V4QKBgDwR5+Dy7txEg0e0AMj5QZwXtrcJIWziIdg5YVFTHy7KYwMppao1
> AQ6x9eSPNl/jdU0dP1AQ395oe18CGdOxRpm84a4XirYvI0v6MhCqffQkyOukPvcn
> /bOhXKWYCHAtJ7PdLwkQCZ3kCf5xddcwS6Q2BREzoOQP5UkKXHNzM39xAoGAKdqr
> edA3wlAl8am4cmOyrAXBqJvxCucITvUDqVwfAmU3ebCKwlmseCJjHsKZ7qVikIda
> iXlKe+vYL2tGz96QTcNkKZ00rfJMsV47rqueEV7ot8jETSBabJd/ScIypTlqPZrv
> 31h70R4pz/8nb0p40BveeTe61BV5sXM3mQBXdWECgYAn9UJc6NCopa8AbgOH5eHE
> X1Q4OXaobRq67J/ylBNwjZg8kjnYq8Me/B2IsfiDcOOP4j7teNQ+MqES/yBFX81k
> hzekAHBiqqthXt4UFXenhe7HZ+BybDu6XjN8tBq5sDLlStA710yWMCNKk9ZEaIV4
> gz7kPgERmOXGpGlMuj9z9g==
> -END PRIVATE KEY-
> 
> ---stderr---
> 
> code: 0
> 
>   78 |   return callback(null, stdout.substring(start, end))
>   79 | } else {
> > 80 |   return callback(new Error(searchStr + ' not found from 
> openssl output:\n---stdout---\n' + stdout + '\n---stderr---\n' + stderr + 
> '\ncode: ' + code))
>  |   ^
>   81 | }
>   82 |   })
>   83 | }
> 
>   at callback (debian/tests/test_modules/pem/lib/openssl.js:80:23)
>   at finalCallback (debian/tests/test_modules/pem/lib/openssl.js:222:7)
>   at deleteSeries (debian/tests/test_modules/pem/lib/helper.js:130:14)
>   at Object.deleteTempFiles 
> (debian/tests/test_modules/pem/lib/helper.js:133:3)
>   at callback (debian/tests/test_modules/pem/lib/openssl.js:221:12)
>   at done (debian/tests/test_modules/pem/lib/openssl.js:160:18)
>   at ChildProcess. 
> (debian/tests/test_modules/pem/lib/openssl.js:175:7)
> 
>   ● do not overwrite prototype properties
> 
> RSA PRIVATE KEY not found from openssl output:
> ---stdout---
> -BEGIN PRIVATE KEY-
> MIIEvAIBADANBgkqhkiG9w0BAQEFAASCBKYwggSiAgEAAoIBAQDDyWaLW3EZC+f2
> veMpcy3UQFUzr5HXwRSZz2pa/2gGwo6b7e6XqVv0tXCOu46k/mXS0Me3xMcj4WsE
> TC0JwojputSl3rsZ6lBTTLpAw5X1NA5rrMrKbcuSJdUPG+wMKPuZf4pZk5HlmGPL
> P3MRQUZLTreOvvoXjrfKFk5/xV97EPUUMgEW83bwfnd2CFgckVEq64sx+I43kKA8
> c11WRq0QQlB+/aVEUUKSlq8yb4bYtt6aeYSnb0wSml+L30SrIJo0XR2MDA4a5tgA
> QIeFxoUx71rHuV2AiubG89cttOia3M7xbA8qRbhHnSVx/qo7bqdUwbZfAPMGBKqW
> ABX5vgqlAgMBAAECggEACWclTSEVo/HN8Kw6+jUlaNG0JdjTRMzpm995yKgGi3iR
> l8yMDm2cVHrYToqUdbkgE8liJiHFvKPpW1n7OcJFiBAogVTaoIp/1BhVw6GBFLcs
> 0CAK10EBq2G0w1aAdi8LsloNP3MWaTPx6wN/l78OTLSZnTnv0ezRR9vdZkaI6OSY
> gYQMrf8+foRxPti+J+sPI4QltVMm3/+q5v1aePTFGKIBSpCtF0s5iIl4aiDXhvTF
> 9dk29D0U07K/nOt2gzIfuDu4chhmq+WmlFuGeIxD

Bug#1011911: pkg-php-tools: FTBFS: testsuite/tests/101_dh_phppear_substvars.sh: 28: php-config: not found

2022-05-26 Thread Lucas Nussbaum
Source: pkg-php-tools
Version: 1.42
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> sh testsuite/runtests.sh
> Running test: 001_pkgtools_phppear_name.sh
> SUCCESS
> Running test: 002_pkgtools_phppear_packagetype.sh
> SUCCESS
> Running test: 003_pkgtools_phppear_channel.sh
> SUCCESS
> Running test: 004_pkgtools_phppear_summary.sh
> SUCCESS
> Running test: 005_pkgtools_phppear_description.sh
> SUCCESS
> Running test: 006_pkgtools_maintaners.sh
> SUCCESS
> Running test: 007_pkgtools_phppear_date.sh
> SUCCESS
> Running test: 008_pkgtools_phppear_version.sh
> SUCCESS
> Running test: 009_pkgtools_phppear_license.sh
> SUCCESS
> Running test: 010_pkgtools_phppear_changelog.sh
> SUCCESS
> Running test: 014_pkgtools_phppear_debianname.sh
> SUCCESS
> Running test: 015_pkgtools_phppear_debianversion.sh
> SUCCESS
> Running test: 016_pkgtools_phppearchannel_name.sh
> SUCCESS
> Running test: 017_pkgtools_phppearchannel_summary.sh
> SUCCESS
> Running test: 018_pkgtools_phppearchannel_suggestedalias.sh
> SUCCESS
> Running test: 101_dh_phppear_substvars.sh
> Use of uninitialized value $v in substitution (s///) at 
> /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 1767, <$fd> line 4.
> Use of uninitialized value $v in substitution (s///) at 
> /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 1768, <$fd> line 4.
> Override: require:pear-pear.phpunit.de/PHPUnit (>= 1.1, <= 1.9) -> 
> require:__override__/phpunit (>= 1.1, <= 1.9).
> Override: recommend:pear-pecl.php.net/mysqli -> 
> recommend:__override__/php-mysql.
> FAIL: cat 'debian/php-foo.substvars'
> --- Expected
> +++ Actual
> @@ -1,5 +1,7 @@
>  phppear:Debian-Depends=php-common, php-alpha (>= 1.0~a), php-alpha (<= 
> 2.0~alpha3), php-beta (>= 1.0~b2), php-beta (<< 2.0~beta4), php-rc (>= 
> 1.0~RC2), php-rc (<= 2.0~RC5), php-horde-alarm (>= 2.2.0), php-horde-alarm 
> (<< 3.0.0~alpha1), phpunit (>= 1.1), phpunit (<= 1.9)
>  phppear:Debian-Recommends=php-mysql
> +phppear:Debian-Suggests=
> +phppear:Debian-Breaks=
>  phppear:summary=this is a wrapper package for installing dependencies for 
> MyProject
>  phppear:description=${Newline}This is a 
> paragraph.${Newline}${Newline}Those are bullets:${Newline} * Number 
> one${Newline} * Number two${Newline}
>  phppear:channel=pear.php.net
> Use of uninitialized value $v in substitution (s///) at 
> /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 1767, <$fd> line 4.
> Use of uninitialized value $v in substitution (s///) at 
> /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 1768, <$fd> line 4.
> sh: 1: /usr/bin/php-config: not found
> testsuite/tests/101_dh_phppear_substvars.sh: 28: php-config: not found
> FAIL: cat 'debian/php-foo.substvars'
> --- Expected
> +++ Actual
> @@ -1,4 +1,7 @@
>  phppear:Debian-Depends=php-common, phpapi-
> +phppear:Debian-Recommends=
> +phppear:Debian-Suggests=
> +phppear:Debian-Breaks=
>  phppear:summary=this is a wrapper package for installing dependencies for 
> MyProject
>  phppear:description=
>  phppear:channel=pecl.php.net
> Use of uninitialized value $v in substitution (s///) at 
> /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 1767, <$fd> line 4.
> Use of uninitialized value $v in substitution (s///) at 
> /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 1768, <$fd> line 4.
> FAILED
> Running test: 151_dh_phpcomposer_substvars.sh
> Use of uninitialized value $v in substitution (s///) at 
> /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 1767, <$fd> line 4.
> Use of uninitialized value $v in substitution (s///) at 
> /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 1768, <$fd> line 4.
> Override: require:pear-pecl.php.net/spl -> require:__override__/builtin.
> Override: require:symfony/polyfill-intl-icu (>= 1.0, < 2~~) -> 
> require:__override__/php-intl.
> Override: require-dev:overrideme/overrideme-sub (>= 3.7, < 3.8~~) -> 
> require-dev:__override__/overrideme-sub (>= 3.7, < 3.8~~).
> Override: suggest:pear-pecl.php.net/apc -> suggest:__override__/php-apcu.
> Use of uninitialized value $v in substitution (s///) at 
> /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 1767, <$fd> line 4.
> Use of uninitialized value $v in substitution (s///) at 
> /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 1768, <$fd> line 4.
> OR-ed versions are not supported require:proj1/unsupported-or (>=1.0,<1.1 | 
> >=1.2) in file "/<>/testsuite/data/composerpkg2/composer.json".
> Branch alias mapped to "*" require:proj1/alias-dev-master (dev-master) in 
> file "/<>/testsuite/data/composerpkg2/composer.json".
> Branch alias mapped to "*" require:proj1/alias-inline (dev-bugfix as 
> 1.0.x-dev) in file 
> "/<>/testsuite/data/composerpkg2/composer.json".
> Unknown dependency: "lib-unknown".
> SUCCESS
> Running test: 201_Debian_Debhelper_Buildsystem_phppear.sh
>   cp package.xml .

Bug#1011910: haskell-warp: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25

2022-05-26 Thread Lucas Nussbaum
Source: haskell-warp
Version: 3.3.13-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-warp-doc.substvars
> dh_installdirs -plibghc-warp-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.lhs -o debian/hlibrary.setup
> [1 of 1] Compiling Main ( Setup.lhs, Setup.o )
> Linking debian/hlibrary.setup ...
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe; haddock_recipe; build_recipe; check_recipe'
> Running find . ! -newer /tmp/pGUCFlrhTF -exec touch -d "1998-01-01 UTC" {} ;
> Running dh_listpackages
> libghc-warp-dev
> libghc-warp-prof
> libghc-warp-doc
> Running dh_listpackages
> libghc-warp-dev
> libghc-warp-prof
> libghc-warp-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/warp-3.3.13/ --datasubdir=warp 
> --htmldir=/usr/share/doc/libghc-warp-doc/html/ --enable-library-profiling
> Using Parsec parser
> Configuring warp-3.3.13...
> Flags chosen: allow-sendfilefd=True, network-bytestring=False,
> warp-debug=False
> Dependency array -any: using array-0.5.4.0
> Dependency async -any: using async-2.2.2
> Dependency auto-update >=0.1.3 && <0.2: using auto-update-0.1.6
> Dependency base >=4.8 && <5: using base-4.13.0.0
> Dependency bsb-http-chunked <0.1: using bsb-http-chunked-0.0.0.4
> Dependency bytestring >=0.9.1.4: using bytestring-0.10.10.1
> Dependency case-insensitive >=0.2: using case-insensitive-1.2.1.0
> Dependency containers -any: using containers-0.6.2.1
> Dependency ghc-prim -any: using ghc-prim-0.5.3
> Dependency hashable -any: using hashable-1.3.0.0
> Dependency http-date -any: using http-date-0.0.8
> Dependency http-types >=0.12: using http-types-0.12.3
> Dependency http2 ==2.0.*: using http2-2.0.5
> Dependency iproute >=1.3.1: using iproute-1.7.9
> Dependency network >=2.3: using network-3.1.1.1
> Dependency simple-sendfile >=0.2.7 && <0.3: using simple-sendfile-0.2.30
> Dependency stm >=2.3: using stm-2.5.0.0
> Dependency streaming-commons >=0.1.10: using streaming-commons-0.2.2.1
> Dependency text -any: using text-1.2.4.0
> Dependency time-manager -any: using time-manager-0.0.0
> Dependency unix -any: using unix-2.7.2.2
> Dependency unix-compat >=0.2: using unix-compat-0.5.2
> Dependency vault >=0.3: using vault-0.3.1.4
> Dependency wai ==3.2.*: using wai-3.2.2.1
> Dependency word8 -any: using word8-0.1.3
> Dependency x509 -any: using x509-1.7.5
> Source component graph: component lib
> Configured component graph:
> component warp-3.3.13-6MSWKH0ouL0GKv61GzrS52
> include array-0.5.4.0
> include async-2.2.2-1jIe70QEPH1GVJJWPbuUZ4
> include auto-update-0.1.6-4jmXkPlBjcnF1FLsvY2uFl
> include base-4.13.0.0
> include bsb-http-chunked-0.0.0.4-HNDI4QbpW2z6EYJjxIg6vm
> include bytestring-0.10.10.1
> include case-insensitive-1.2.1.0-2DJgVsP1xD65aBTMRg5yb2
> include containers-0.6.2.1
> include ghc-prim-0.5.3
> include hashable-1.3.0.0-AOP4LTmShW4Dax9brHgY53
> include http-date-0.0.8-1AcsYWHJnUcFoTXwCJzq8e
> include http-types-0.12.3-3lJUcD0p9NA9DlzJlODIAk
> include http2-2.0.5-L08Kss3hpraJqsufQHiiCq
> include iproute-1.7.9-LqOnJHxV4881wCFZHy3B57
> include network-3.1.1.1-CtLURRWWFvn3QC3vC70cjB
> include simple-sendfile-0.2.30-5X28Hk3v9CxAtHZAbcwmvx
> include stm-2.5.0.0
> include streaming-commons-0.2.2.1-CRnmBxJ3GinBzZ40CTYCxG
> include text-1.2.4.0
> include time-manager-0.0.0-3Ybp1HkuigQ6mtOjkLo5zt
> include unix-2.7.2.2
> include unix-compat-0.5.2-1FQI6nqgJsoGP4VQqT0w3a
> include vault-0.3.1.4-5YyrDFZDpGlKOHltHNMaqs
> include wai-3.2.2.1-EjgFNYzvDpkBVcLk2innX
> include word8-0.1.3-DiaEiE1hk0kFbyxgoQOIG
> include x509-1.7.5-6C90JQFjjKNC9lQcytVvoI
> Linked component graph:
> unit warp-3.3.13-6MSWKH0ouL0GKv61GzrS52
> include array-0.5.4.0
> include async-2.2.2-1jIe70QEPH1GVJJWPbuUZ4
> include auto-update-0.1.6-4jmXkPlBjcnF1FLsvY2uFl
> include base-4.13.0.0
> include bsb-http-chunked-0.0.0.4-HNDI4QbpW2z6EYJjxIg6vm
> include bytestring-0.1

Bug#1011908: node-css-what: FTBFS: node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations.

2022-05-26 Thread Lucas Nussbaum
Source: node-css-what
Version: 5.1.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> Link ./node_modules/pretty-format -> /usr/share/nodejs/pretty-format
> Link ./node_modules/ts-jest -> /usr/share/nodejs/ts-jest
> Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node
> Copy /usr/share/nodejs/jest-diff -> ./node_modules/
> Copy /usr/share/nodejs/@types/jest -> ./node_modules/@types
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> tsc --lib es6
> node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 
> 'jest-matcher-utils' or its corresponding type declarations.
> make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/node-css-what_5.1.0-2_unstable.log

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

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

If you reassign this bug to another package, please 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.



Bug#1011906: node-glob-parent: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 15

2022-05-26 Thread Lucas Nussbaum
Source: node-glob-parent
Version: 6.0.2+~5.1.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> Link node_modules/@types/glob-parent -> ../../types-glob-parent
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/glob-parent
>   /bin/sh -ex debian/tests/pkg-js/test
> + mocha
> 
> 
>   glob-parent
> 1) should strip glob magic to return parent path
> 2) should respect escaped characters
> 3) should respect glob enclosures with embedded separators
> 4) should handle nested braces
> 5) should return parent dirname from non-glob paths
> 6) should respect disabled auto flip backslashes
> 
>   glob2base test patterns
> 7) should get a base name
> 8) should get a base name from a nested glob
> 9) should get a base name from a flat file
> 10) should get a base name from character class pattern
> 11) should get a base name from brace , expansion
> 12) should get a base name from brace .. expansion
> 13) should get a base name from extglob
> 14) should get a base name from a path with non-exglob parens
> 15) should get a base name from a complex brace glob
> undefined should not be susceptible to SNYK-JS-GLOBPARENT-1016905
> undefined should finish in reasonable time for '{' + '/'.repeat(n) 
> [CVE-2021-35065]
> undefined should finish in reasonable time for '{'.repeat(n)
> undefined should finish in reasonable time for '('.repeat(n)
> undefined should finish in reasonable time for '/('.repeat(n) + ')' (42ms)
> 
> 
>   5 passing (90ms)
>   15 failing
> 
>   1) glob-parent
>should strip glob magic to return parent path:
>  TypeError: expect is not a function
>   at Context. (test/index.test.js:9:5)
>   at callFnAsync (/usr/share/nodejs/mocha/lib/runnable.js:394:21)
>   at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:338:7)
>   at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:678:10)
>   at /usr/share/nodejs/mocha/lib/runner.js:801:12
>   at next (/usr/share/nodejs/mocha/lib/runner.js:593:14)
>   at /usr/share/nodejs/mocha/lib/runner.js:603:7
>   at next (/usr/share/nodejs/mocha/lib/runner.js:486:14)
>   at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:571:5)
>   at processImmediate (node:internal/timers:466:21)
> 
>   2) glob-parent
>should respect escaped characters:
>  TypeError: expect is not a function
>   at Context. (test/index.test.js:69:5)
>   at callFnAsync (/usr/share/nodejs/mocha/lib/runnable.js:394:21)
>   at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:338:7)
>   at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:678:10)
>   at /usr/share/nodejs/mocha/lib/runner.js:801:12
>   at next (/usr/share/nodejs/mocha/lib/runner.js:593:14)
>   at /usr/share/nodejs/mocha/lib/runner.js:603:7
>   at next (/usr/share/nodejs/mocha/lib/runner.js:486:14)
>   at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:571:5)
>   at processImmediate (node:internal/timers:466:21)
> 
>   3) glob-parent
>should respect glob enclosures with embedded separators:
>  TypeError: expect is not a function
>   at Context. (test/index.test.js:109:5)
>   at callFnAsync (/usr/share/nodejs/mocha/lib/runnable.js:394:21)
>   at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:338:7)
>   at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:678:10)
>   at /usr/share/nodejs/mocha/lib/runner.js:801:12
>   at next (/usr/share/nodejs/mocha/lib/runner.js:593:14)
>   at /usr/share/nodejs/mocha/lib/runner.js:603:7
>   at next (/usr/share/nodejs/mocha/lib/runner.js:486:14)
>   at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:571:5)
>   at processImmediate (node:internal/timers:466:21)
> 
>   4) glob-parent
>should handle nested braces:
>  TypeError: expect is not a function
>   at Context. (test/index.test.js:130:5)
>   at callFnAsync (/usr/share/nodejs/mocha/lib/runnable.js:394:21)
>   at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:338:7)
>   at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:678:10)
>   at /usr/share/nodejs/mocha/lib/runner.js:801:12
>   at next (/usr/share/nodejs/mocha/lib/runner.js:593:14)
>   at /usr/share/nodejs/mocha/lib/runner.js:603:7
>   at next (/usr/share/nodejs/mocha/lib/runner.js:486:14)
>   at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.j

Bug#1011904: networking-baremetal: FTBFS: KeyError: 'agent_type'

2022-05-26 Thread Lucas Nussbaum
Source: networking-baremetal
Version: 5.1.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> set -e ; for i in 3.9 3.10 ; do \
>   python$i setup.py install --install-layout=deb --root 
> /<>/debian/tmp ; \
> done
> /usr/lib/python3/dist-packages/setuptools/command/easy_install.py:158: 
> EasyInstallDeprecationWarning: easy_install command is deprecated. Use build 
> and pip and other standards-based tools.
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and 
> pip and other standards-based tools.
>   warnings.warn(
> running install
> [pbr] Generating AUTHORS
> [pbr] AUTHORS complete (0.0s)
> running build
> running build_py
> running egg_info
> writing networking_baremetal.egg-info/PKG-INFO
> writing dependency_links to networking_baremetal.egg-info/dependency_links.txt
> writing entry points to networking_baremetal.egg-info/entry_points.txt
> writing requirements to networking_baremetal.egg-info/requires.txt
> writing top-level names to networking_baremetal.egg-info/top_level.txt
> [pbr] Reusing existing SOURCES.txt
> running install_lib
> creating /<>/debian/tmp
> creating /<>/debian/tmp/usr
> creating /<>/debian/tmp/usr/lib
> creating /<>/debian/tmp/usr/lib/python3
> creating /<>/debian/tmp/usr/lib/python3/dist-packages
> creating 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal
> copying build/lib/networking_baremetal/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal
> creating 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/plugins
> copying build/lib/networking_baremetal/plugins/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/plugins
> creating 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/plugins/ml2
> copying build/lib/networking_baremetal/plugins/ml2/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/plugins/ml2
> copying build/lib/networking_baremetal/plugins/ml2/baremetal_mech.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/plugins/ml2
> creating 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/agent
> copying build/lib/networking_baremetal/agent/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/agent
> copying build/lib/networking_baremetal/agent/ironic_neutron_agent.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/agent
> copying build/lib/networking_baremetal/_i18n.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal
> copying build/lib/networking_baremetal/ironic_client.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal
> creating 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/tests
> copying build/lib/networking_baremetal/tests/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/tests
> creating 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/tests/unit
> copying build/lib/networking_baremetal/tests/unit/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/tests/unit
> creating 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/tests/unit/plugins
> copying build/lib/networking_baremetal/tests/unit/plugins/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/tests/unit/plugins
> creating 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/tests/unit/plugins/ml2
> copying build/lib/networking_baremetal/tests/unit/plugins/ml2/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/tests/unit/plugins/ml2
> copying 
> build/lib/networking_baremetal/tests/unit/plugins/ml2/test_baremetal_mech.py 
> -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/tests/unit/plugins/ml2
> copying build/lib/networking_baremetal/tests/unit/plugins/ml2/utils.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/tests/unit/plugins/ml2
> creating 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/tests/unit/ironic_agent
> copying build/lib/networking_baremetal/tests/unit/ironic_agent/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/tests/unit/ironic_agent
> copying 
> build/lib/networking_baremetal/tests/unit/ironic_agent/test_ironic_agent.py 
> -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/networking_baremetal/tests/unit/ironic_agent
> cop

Bug#1011905: node-gulp-concat: FTBFS: dh_auto_test: error: cd ./gulp-wrap && sh -ex ../debian/nodejs/gulp-wrap/test returned exit code 1

2022-05-26 Thread Lucas Nussbaum
Source: node-gulp-concat
Version: 2.6.1+~0.0.15+git20190329.179bb8c+~1.0.3-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> Link node_modules/gulp-wrap -> ../gulp-wrap
> Link node_modules/tryit -> ../tryit
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/gulp-concat
>   cd ./gulp-wrap && sh -ex ../debian/nodejs/gulp-wrap/test
> + mocha test
> 
> 
>   gulp-wrap
> undefined should pass an empty file as it is
> undefined should produce expected file via buffer
> undefined should produce expected file via stream
> undefined should error when no template is provided
> undefined should handle a template from a file
> undefined should handle a template from a function
> undefined should fail when it cannot read the template file.
> undefined should handle template data and options
> undefined should allow for dynamic options
> undefined should allow file props in the template data
> undefined should make data props override file data
> undefined should allow for dynamic data
> undefined should not pollute file data across multiple streams
> undefined should merge file.data property
> undefined should allow for expressions
> undefined should parse JSON files by default
> undefined should parse YAML files by default
> undefined option parse=false should disable file parsing
> undefined should throw exception object passed for template and no src 
> property is set
> undefined should throw exception if data file parse is invalid
> 1) should throw exception if template is invalid
> 
> 
>   20 passing (2s)
>   1 failing
> 
>   1) gulp-wrap
>should throw exception if template is invalid:
>  Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
> "done()" is called; if returning a Promise, ensure it resolves. 
> (/<>/gulp-wrap/test/test.js)
>   at createTimeoutError (/usr/share/nodejs/mocha/lib/errors.js:498:15)
>   at Test.Runnable._timeoutError 
> (/usr/share/nodejs/mocha/lib/runnable.js:431:10)
>   at Timeout. (/usr/share/nodejs/mocha/lib/runnable.js:246:24)
>   at listOnTimeout (node:internal/timers:559:17)
>   at processTimers (node:internal/timers:502:7)
> 
> 
> 
> dh_auto_test: error: cd ./gulp-wrap && sh -ex ../debian/nodejs/gulp-wrap/test 
> returned exit code 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/node-gulp-concat_2.6.1+~0.0.15+git20190329.179bb8c+~1.0.3-4_unstable.log

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

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

If you reassign this bug to another package, please 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.



Bug#1011903: node-rollup-plugin-commonjs: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

2022-05-26 Thread Lucas Nussbaum
Source: node-rollup-plugin-commonjs
Version: 21.0.1+repack-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd packages/commonjs && rollup -c
> 
> src/index.js → dist/index.es.js, dist/index.js...
> created dist/index.es.js, dist/index.js in 330ms
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules/\@rollup
>   ln -s ../../packages/commonjs node_modules/\@rollup/plugin-commonjs
>   /bin/sh -ex debian/tests/pkg-js/test
> + mkdir -p node_modules/@rollup
> + ln -s ../../packages/commonjs node_modules/@rollup/plugin-commonjs
> + tape packages/commonjs/test/test.js
> node:internal/modules/cjs/loader:936
>   throw err;
>   ^
> 
> Error: Cannot find module 'locate-character'
> Require stack:
> - /<>/packages/commonjs/test/test.js
> - /usr/share/nodejs/tape/bin/import-or-require.js
> - /usr/share/nodejs/tape/bin/tape
> at Function.Module._resolveFilename 
> (node:internal/modules/cjs/loader:933:15)
> at Function.Module._load (node:internal/modules/cjs/loader:778:27)
> at Module.require (node:internal/modules/cjs/loader:1005:19)
> at require (node:internal/modules/cjs/helpers:102:18)
> at Object. 
> (/<>/packages/commonjs/test/test.js:8:24)
> at Module._compile (node:internal/modules/cjs/loader:1103:14)
> at Object.Module._extensions..js 
> (node:internal/modules/cjs/loader:1157:10)
> at Module.load (node:internal/modules/cjs/loader:981:32)
> at Function.Module._load (node:internal/modules/cjs/loader:822:12)
> at Module.require (node:internal/modules/cjs/loader:1005:19) {
>   code: 'MODULE_NOT_FOUND',
>   requireStack: [
> '/<>/packages/commonjs/test/test.js',
> '/usr/share/nodejs/tape/bin/import-or-require.js',
> '/usr/share/nodejs/tape/bin/tape'
>   ]
> }
> 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/05/25/node-rollup-plugin-commonjs_21.0.1+repack-1_unstable.log

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

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

If you reassign this bug to another package, please 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.



Bug#1011902: libvirt-python: FTBFS: make: *** [debian/rules:12: build] Error 25

2022-05-26 Thread Lucas Nussbaum
Source: libvirt-python
Version: 8.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:239: python3.9 setup.py config 
> running config
> I: pybuild base:239: python3.10 setup.py config 
> /<>/setup.py:3: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.core import setup, Extension, Command
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:239: /usr/bin/python3.9 setup.py build 
> running build
> /usr/bin/pkg-config --print-errors --atleast-version=0.9.11 libvirt
> /usr/bin/python3.9 generator.py libvirt /usr/share/libvirt/api/libvirt-api.xml
> Found 493 functions in /usr/share/libvirt/api/libvirt-api.xml
> Found 0 functions in libvirt-override-api.xml
> Generated 404 wrapper functions
> /usr/bin/python3.9 generator.py libvirt-qemu 
> /usr/share/libvirt/api/libvirt-qemu-api.xml
> Found 6 functions in /usr/share/libvirt/api/libvirt-qemu-api.xml
> Found 0 functions in libvirt-qemu-override-api.xml
> Generated 3 wrapper functions
> Missing type converters: 
> int *:1 
> ERROR: failed virDomainQemuMonitorCommandWithFiles
> error: command '/usr/bin/python3.9' failed with exit code 1
> E: pybuild pybuild:369: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python3.9 setup.py build 
> I: pybuild base:239: /usr/bin/python3 setup.py build 
> /<>/setup.py:3: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.core import setup, Extension, Command
> running build
> /usr/bin/pkg-config --print-errors --atleast-version=0.9.11 libvirt
> /usr/bin/python3 generator.py libvirt /usr/share/libvirt/api/libvirt-api.xml
> Found 493 functions in /usr/share/libvirt/api/libvirt-api.xml
> Found 0 functions in libvirt-override-api.xml
> Generated 404 wrapper functions
> /usr/bin/python3 generator.py libvirt-qemu 
> /usr/share/libvirt/api/libvirt-qemu-api.xml
> Found 6 functions in /usr/share/libvirt/api/libvirt-qemu-api.xml
> Found 0 functions in libvirt-qemu-override-api.xml
> Generated 3 wrapper functions
> Missing type converters: 
> int *:1 
> ERROR: failed virDomainQemuMonitorCommandWithFiles
> error: command '/usr/bin/python3' failed with exit code 1
> E: pybuild pybuild:369: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python3 setup.py build 
> dh_auto_build: error: pybuild --build -i python{version} -p "3.9 3.10" 
> returned exit code 13
> make: *** [debian/rules:12: build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/libvirt-python_8.0.0-1_unstable.log

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

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

If you reassign this bug to another package, please 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.



Bug#1011901: prismatic-plumbing-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.

2022-05-26 Thread Lucas Nussbaum
Source: prismatic-plumbing-clojure
Version: 0.5.5-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> lein test
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> This could be due to a typo in :dependencies, file system permissions, or 
> network issues.
> If you are behind a proxy, try setting the 'http_proxy' environment variable.
> make[1]: *** [debian/rules:27: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/prismatic-plumbing-clojure_0.5.5-2_unstable.log

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

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

If you reassign this bug to another package, please 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.



Bug#1011897: interimap: FTBFS: tests fail

2022-05-26 Thread Lucas Nussbaum
Source: interimap
Version: 0.5.7-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> ./tests/certs/generate
> .+*...+...++*..+...+.+..++.+..+
> ..+.+..+.+.+..+...+*+++*+.+.+...+...++...+.+...+.+...+...+..+.+...+..+...+..+.++..+.+..+.+.+.+..++...+...+...+..+...+.+..++...+...+..+...+..+..+...+.+...+.++.+...+.++..++..+...+...+...+.+...+.+.+...+...+.+.+.+...+...++.+..++..+..+...++.+.+..+..+..+...+.+
> .+.+*..+...+..+.+..++...+*...+..+.+.+..+...+..+...+...+..++.++..+..+..+...+..+...+..+.+..+...++..+.+...+...+.+...++.++..+...++.+.+...+...+.+..+..+.+.+.+.+.+.+...+...+.+...+...++...+..+.+...+.+...+..+.+..++..+...+++...+.+..+...+..++..++...+..+...+...+...+...++...+.+...++.++...+..+...+...+..+++..+...+.+.+.+.+.+..+.+.+.+.+.+..+.++..+..+.+.+.+...+...+.+.+...+..+.+.+.++...+...+.+.+...+...+.+
> .+.+...+..+.++..+.+...+*...+...++.+.+.+.++++...+*...+..+.+.+
> .+..+.+...+.+...+*...+...+...+...+++...+..++*.+..+..+..+.++...+.+...+...+.+...+..+..+...+..+.+..+.++..+.+..+.+...+..+...+...+...+.+.+...+...+.+.+..+..+.+..+...+..+.+..+..+.+..+...+.+.+.+...+..+...+.+++.+
> .+.++*.+...+.+.+...+..+.+.+..+...+.+.+...++..+.+++...+..+.+...+..+.+..+...+...+...+..+.+.+.+.+*..+..+..+...++.++.+...+.+.+..+..+...++..+.++...++...+++...+..++...+...++..+
> INTERIMAP_I=./lib INTERIMAP_PATH=build ./tests/run-all interimap.list
> `interimap --watch` refuses to create the database... PASSED
> mutually exclusive DB access... PASSED
> DB schema upgrade (v0 -> v1):
> migrate... PASSED
> abort on hierarchy delimiter mismatch... PASSED
> abort on foreign key contraint violation... PASSED
> Mailbox deletion:
> nonexistent source (no-op)... PASSED
> mailbox with inferiors... PASSED
> INBOX (fail)... PASSED
> \Noinferiors mailbox... PASSED
> Mailbox renaming:
> abort if target exists in the DB... PASSED
> abort if target exists locally... PASSED
> abort if target exists remotely... PASSED
> non-existent source (no-op)... PASSED
> existin

Bug#1011899: php-twig: FTBFS: make[1]: *** [debian/rules:92: override_dh_auto_test] Error 1

2022-05-26 Thread Lucas Nussbaum
Source: php-twig
Version: 3.3.9-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> SYMFONY_DEPRECATIONS_HELPER=weak phpunit
> PHPUnit 9.5.16 by Sebastian Bergmann and contributors.
> 
> Testing 
> .   61 / 1649 (  
> 3%)
> .  122 / 1649 (  
> 7%)
> .  183 / 1649 ( 
> 11%)
> .  244 / 1649 ( 
> 14%)
> .  305 / 1649 ( 
> 18%)
> .  366 / 1649 ( 
> 22%)
> S  427 / 1649 ( 
> 25%)
> .  488 / 1649 ( 
> 29%)
> .  549 / 1649 ( 
> 33%)
> ..S..  610 / 1649 ( 
> 36%)
> .  671 / 1649 ( 
> 40%)
> .  732 / 1649 ( 
> 44%)
> ..S..  793 / 1649 ( 
> 48%)
> .  854 / 1649 ( 
> 51%)
> .  915 / 1649 ( 
> 55%)
> .  976 / 1649 ( 
> 59%)
> . 1037 / 1649 ( 
> 62%)
> . 1098 / 1649 ( 
> 66%)
> . 1159 / 1649 ( 
> 70%)
> . 1220 / 1649 ( 
> 73%)
> . 1281 / 1649 ( 
> 77%)
> . 1342 / 1649 ( 
> 81%)
> . 1403 / 1649 ( 
> 85%)
> . 1464 / 1649 ( 
> 88%)
> . 1525 / 1649 ( 
> 92%)
> . 1586 / 1649 ( 
> 96%)
> . 1647 / 1649 ( 
> 99%)
> ..1649 / 1649 
> (100%)
> 
> Time: 00:00.844, Memory: 38.00 MB
> 
> OK, but incomplete, skipped, or risky tests!
> Tests: 1649, Assertions: 4384, Skipped: 3.
> 
> Legacy deprecation notices (3)
> # testsuite for extra packages
> set -e; \
>  for package_info_file in $(find debian/packages_to_build/ -mindepth 1 
> -maxdepth 1 -type f); do \
>   . $package_info_file; \
>   if [ -f $src_path/phpunit.xml.dist ]; then \
>LC_ALL=en_US SYMFONY_DEPRECATIONS_HELPER=weak phpunit \
>--bootstrap vendor/autoload.php \
>--configuration $src_path/phpunit.xml.dist \
>$src_path; \
>   fi; \
>  done
> PHPUnit 9.5.16 by Sebastian Bergmann and contributors.
> 
> Warning:   Your XML configuration validates against a deprecated schema.
> Suggestion:Migrate your XML configuration using "--migrate-configuration"!
> 
> ..S 3 / 3 
> (100%)
> 
> Time: 00:00.035, Memory: 8.00 MB
> 
> OK, but incomplete, skipped, or risky tests!
> Tests: 3, Assertions: 4, Skipped: 1.
> PHPUnit 9.5.16 by Sebastian Bergmann and contributors.
> 
> Warning:   Your XML configuration validates against a deprecated schema.
> Suggestion:Migrate your XML configuration using "--migrate-configuration"!
> 
> ...S8 / 8 
> (100%)
> 
> Time: 00:00.020, Memory: 8.00 MB
> 
> OK, but incomplete, skipped, or risky tests!
> Tests: 8, Assertions: 14, Skipped: 1.
> PHPUnit 9.5.16 by Sebastian Bergmann and contributors.
> 
> Warning:   Your XML configuration validates against a deprecated schema.
> Suggestion:Migrate your XML configuration using "--migrate-configuration"!
> 
> S   5 / 5 
> (100%)
> 
> Time: 00:00.024, Memory: 10.00 MB
> 
> OK, but incomplete, skipped, or risky tests!
> Tests: 5, Assertions: 8, Skipped: 1.
> PHPUnit 9.5.16 by Sebastian Bergmann and contributors.
> 
> Warning:   Your XML configuration validates against a deprecated schema.
> Suggestion:Migrate your XML configuration using "--migrate-configuration"!
> 
> ..FCompiled templates that failed on case 1:

Bug#1011898: node-browserify-cipher: FTBFS: TypeError: Cannot read properties of undefined (reading 'update')

2022-05-26 Thread Lucas Nussbaum
Source: node-browserify-cipher
Version: 1.0.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/browserify-cipher
>   /bin/sh -ex debian/tests/pkg-js/test
> + nodejs test.js
> TAP version 13
> # mode: aes-128-ecb
> # run: 1
> ok 1 should be strictly equal
> ok 2 should be strictly equal
> # run: 2
> ok 3 should be strictly equal
> ok 4 should be strictly equal
> # run: 3
> ok 5 should be strictly equal
> ok 6 should be strictly equal
> # run: 4
> ok 7 should be strictly equal
> ok 8 should be strictly equal
> # run: 5
> ok 9 should be strictly equal
> ok 10 should be strictly equal
> # run: 6
> ok 11 should be strictly equal
> ok 12 should be strictly equal
> # run: 7
> ok 13 should be strictly equal
> ok 14 should be strictly equal
> # run: 8
> ok 15 should be strictly equal
> ok 16 should be strictly equal
> # run: 9
> ok 17 should be strictly equal
> ok 18 should be strictly equal
> # mode: aes-192-ecb
> # run: 1
> ok 19 should be strictly equal
> ok 20 should be strictly equal
> # run: 2
> ok 21 should be strictly equal
> ok 22 should be strictly equal
> # run: 3
> ok 23 should be strictly equal
> ok 24 should be strictly equal
> # run: 4
> ok 25 should be strictly equal
> ok 26 should be strictly equal
> # run: 5
> ok 27 should be strictly equal
> ok 28 should be strictly equal
> # run: 6
> ok 29 should be strictly equal
> ok 30 should be strictly equal
> # run: 7
> ok 31 should be strictly equal
> ok 32 should be strictly equal
> # run: 8
> ok 33 should be strictly equal
> ok 34 should be strictly equal
> # run: 9
> ok 35 should be strictly equal
> ok 36 should be strictly equal
> # mode: aes-256-ecb
> # run: 1
> ok 37 should be strictly equal
> ok 38 should be strictly equal
> # run: 2
> ok 39 should be strictly equal
> ok 40 should be strictly equal
> # run: 3
> ok 41 should be strictly equal
> ok 42 should be strictly equal
> # run: 4
> ok 43 should be strictly equal
> ok 44 should be strictly equal
> # run: 5
> ok 45 should be strictly equal
> ok 46 should be strictly equal
> # run: 6
> ok 47 should be strictly equal
> ok 48 should be strictly equal
> # run: 7
> ok 49 should be strictly equal
> ok 50 should be strictly equal
> # run: 8
> ok 51 should be strictly equal
> ok 52 should be strictly equal
> # run: 9
> ok 53 should be strictly equal
> ok 54 should be strictly equal
> # mode: aes-128-cbc
> # run: 1
> ok 55 should be strictly equal
> ok 56 should be strictly equal
> (node:802961) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
> security and usability issues. Please use the Buffer.alloc(), 
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> (Use `nodejs --trace-deprecation ...` to show where the warning was created)
> # run: 2
> ok 57 should be strictly equal
> ok 58 should be strictly equal
> # run: 3
> ok 59 should be strictly equal
> ok 60 should be strictly equal
> # run: 4
> ok 61 should be strictly equal
> ok 62 should be strictly equal
> # run: 5
> ok 63 should be strictly equal
> ok 64 should be strictly equal
> # run: 6
> ok 65 should be strictly equal
> ok 66 should be strictly equal
> # run: 7
> ok 67 should be strictly equal
> ok 68 should be strictly equal
> # run: 8
> ok 69 should be strictly equal
> ok 70 should be strictly equal
> # run: 9
> ok 71 should be strictly equal
> ok 72 should be strictly equal
> # mode: aes-192-cbc
> # run: 1
> ok 73 should be strictly equal
> ok 74 should be strictly equal
> # run: 2
> ok 75 should be strictly equal
> ok 76 should be strictly equal
> # run: 3
> ok 77 should be strictly equal
> ok 78 should be strictly equal
> # run: 4
> ok 79 should be strictly equal
> ok 80 should be strictly equal
> # run: 5
> ok 81 should be strictly equal
> ok 82 should be strictly equal
> # run: 6
> ok 83 should be strictly equal
> ok 84 should be strictly equal
> # run: 7
> ok 85 should be strictly equal
> ok 86 should be strictly equal
> # run: 8
> ok 87 should be strictly equal
> ok 88 should be strictly equal
> # run: 9
> ok 89 should be strictly equal
> ok 90 should be strictly equal
> # mode: aes-256-cbc
> # run: 1
> ok 91 should be strictly equal
> ok 92 should be strictly equal
> # run: 2
> ok 93 should be strictly equal
> ok 94 should be strictly equal
> # run: 3
> ok 95 should be strictly equal
> ok 96 should be strictly equal
> # run: 4
> ok 97 should be strictly equal
> ok 98 should be strictly equal
> # run: 5
> ok 99 should be strictly equal
> ok 100 should be strictly equal
> # run: 6
> ok 101 should be strictly

Bug#1011896: haskell-gtk3: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25

2022-05-26 Thread Lucas Nussbaum
Source: haskell-gtk3
Version: 0.15.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-gtk3-doc.substvars
> dh_installdirs -plibghc-gtk3-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe; haddock_recipe; build_recipe; check_recipe'
> Running find . ! -newer /tmp/OI6M8WPJlN -exec touch -d "1998-01-01 UTC" {} ;
> Running dh_listpackages
> libghc-gtk3-dev
> libghc-gtk3-prof
> libghc-gtk3-doc
> Running dh_listpackages
> libghc-gtk3-dev
> libghc-gtk3-prof
> libghc-gtk3-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/gtk3-0.15.5/ --datasubdir=gtk3 
> --htmldir=/usr/share/doc/libghc-gtk3-doc/html/ --enable-library-profiling
> Using Parsec parser
> Configuring gtk3-0.15.5...
> Flags chosen: build-demos=False, fmode-binary=True, have-gio=True
> Dependency array -any: using array-0.5.4.0
> Dependency base ==4.*: using base-4.13.0.0
> Dependency bytestring -any: using bytestring-0.10.10.1
> Dependency cairo >=0.13.0.0 && <0.14: using cairo-0.13.8.1
> Dependency containers -any: using containers-0.6.2.1
> Dependency gio >=0.13.0 && <0.14: using gio-0.13.8.1
> Dependency glib >=0.13.0.0 && <0.14: using glib-0.13.8.1
> Dependency mtl -any: using mtl-2.2.2
> Dependency pango >=0.13.0.0 && <0.14: using pango-0.13.8.1
> Dependency text >=0.11.0.6 && <1.3: using text-1.2.4.0
> Dependency gthread-2.0 -any: using version 2.72.1
> Dependency gtk+-3.0 -any: using version 3.24.33
> Source component graph: component lib
> Configured component graph:
> component gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH
> include array-0.5.4.0
> include base-4.13.0.0
> include bytestring-0.10.10.1
> include cairo-0.13.8.1-9ROOXD4as1uLn8sCpDXiTi
> include containers-0.6.2.1
> include gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W
> include glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx
> include mtl-2.2.2
> include pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o
> include text-1.2.4.0
> Linked component graph:
> unit gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH
> include array-0.5.4.0
> include base-4.13.0.0
> include bytestring-0.10.10.1
> include cairo-0.13.8.1-9ROOXD4as1uLn8sCpDXiTi
> include containers-0.6.2.1
> include gio-0.13.8.1-HiLx4rVjKnS7eInnEzgc9W
> include glib-0.13.8.1-CNR5m0GNdIe6FNxKsH4Wyx
> include mtl-2.2.2
> include pango-0.13.8.1-J6ZPsrZFOIY2Xy7NzhFm7o
> include text-1.2.4.0
> 
> Graphics.UI.Gtk=gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH:Graphics.UI.Gtk,Graphics.UI.Gtk.Abstract.Bin=gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH:Graphics.UI.Gtk.Abstract.Bin,Graphics.UI.Gtk.Abstract.Box=gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH:Graphics.UI.Gtk.Abstract.Box,Graphics.UI.Gtk.Abstract.ButtonBox=gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH:Graphics.UI.Gtk.Abstract.ButtonBox,Graphics.UI.Gtk.Abstract.Container=gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH:Graphics.UI.Gtk.Abstract.Container,Graphics.UI.Gtk.Abstract.IMContext=gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH:Graphics.UI.Gtk.Abstract.IMContext,Graphics.UI.Gtk.Abstract.Misc=gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH:Graphics.UI.Gtk.Abstract.Misc,Graphics.UI.Gtk.Abstract.Object=gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH:Graphics.UI.Gtk.Abstract.Object,Graphics.UI.Gtk.Abstract.Paned=gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH:Graphics.UI.Gtk.Abstract.Paned,Graphics.UI.Gtk.Abstract.Range=gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH:Graphics.UI.Gtk.Abstract.Range,Graphics.UI.Gtk.Abstract.Scale=gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH:Graphics.UI.Gtk.Abstract.Scale,Graphics.UI.Gtk.Abstract.Scrollbar=gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH:Graphics.UI.Gtk.Abstract.Scrollbar,Graphics.UI.Gtk.Abstract.Separator=gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH:Graphics.UI.Gtk.Abstract.Separator,Graphics.UI.Gtk.Abstract.Widget=gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH:Graphics.UI.Gtk.Abstract.Widget,Graphics.UI.Gtk.ActionMenuToolbar.Action=gtk3-0.15.5-7uv6caKJQrvHKk75JRMzUH:Graphics.UI.Gtk.ActionMenuToolbar.Action,Graphi

Bug#1011895: gnome-boxes: FTBFS: Package 'libpulse-simple', required by 'gvncpulse-1.0', not found

2022-05-26 Thread Lucas Nussbaum
Source: gnome-boxes
Version: 42.0.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  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.62.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-boxes
> Project version: 42.0.1
> C compiler for the host machine: cc (gcc 11.3.0 "cc (Debian 11.3.0-3) 11.3.0")
> C linker for the host machine: cc ld.bfd 2.38
> Vala compiler for the host machine: valac (valac 0.56.1)
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency libarchive found: YES 3.6.0
> Library config found: YES
> Configuring config.h.in 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.Boxes.desktop.in using configuration
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Program desktop-file-validate found: YES (/usr/bin/desktop-file-validate)
> Configuring org.gnome.Boxes.service using configuration
> Configuring org.gnome.Boxes.SearchProvider.service using configuration
> Configuring org.gnome.Boxes.appdata.xml.in using configuration
> Program appstream-util found: YES (/usr/bin/appstream-util)
> Configuring org.gnome.boxes.gschema.xml using configuration
> Configuring org.gnome.Boxes.SearchProvider.ini using configuration
> Program itstool found: YES (/usr/bin/itstool)
> Program msgmerge found: YES (/usr/bin/msgmerge)
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Program msginit found: YES (/usr/bin/msginit)
> Program msgmerge found: YES (/usr/bin/msgmerge)
> Program xgettext found: YES (/usr/bin/xgettext)
> Run-time dependency gio-2.0 found: YES 2.72.1
> Run-time dependency glib-2.0 found: YES 2.72.1
> Run-time dependency gobject-2.0 found: YES 2.72.1
> Run-time dependency gtk+-3.0 found: YES 3.24.33
> Run-time dependency gtk-vnc-2.0 found: YES 1.3.0
> Did not find CMake 'cmake'
> Found CMake: NO
> Run-time dependency gvncpulse-1.0 found: NO 
> 
> ../src/meson.build:100:0: ERROR: Could not generate cargs for gvncpulse-1.0:
> Package libpulse-simple was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libpulse-simple.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'libpulse-simple', required by 'gvncpulse-1.0', not found
> 
> 
> 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-05-25T21:18:27.133837
> 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.62.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-boxes
> Project version: 42.0.1
> 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.3.0 "cc (Debian 11.3.0-3) 11.3.0")
> C linker for the host machine: cc ld.bfd 2.38
> Running compile:
> Working directory:  /tmp/tmpcm3vu84b
> Command line:  valac /tmp/tmpcm3vu84b/testfile.vala -C 
> 
> Code:
>  class MesonSanityCheck : Object { }
> Compiler stdout:
>  
> Compiler stderr:
>  
> Vala compiler for the host machine: valac (valac 0.56.1)
> 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.3.0 "cc (Debian 11.3.0-3) 
> 11.3.0")
> C linker for the bu

Bug#1011894: node-y18n: FTBFS: make[1]: *** [debian/rules:12: override_dh_auto_build] Error 1

2022-05-26 Thread Lucas Nussbaum
Source: node-y18n
Version: 5.0.8+~5.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> tsc
> rollup -c
> [!] Error: Cannot find module '@rollup/pluginutils'
> Require stack:
> - 
> /<>/debian/build_modules/@wessberg/rollup-plugin-ts/dist/cjs/index.js
> - /<>/rollup.config.js
> - /usr/share/nodejs/rollup/dist/shared/loadConfigFile.js
> - /usr/share/nodejs/rollup/dist/bin/rollup
> Error: Cannot find module '@rollup/pluginutils'
> Require stack:
> - 
> /<>/debian/build_modules/@wessberg/rollup-plugin-ts/dist/cjs/index.js
> - /<>/rollup.config.js
> - /usr/share/nodejs/rollup/dist/shared/loadConfigFile.js
> - /usr/share/nodejs/rollup/dist/bin/rollup
> at Function.Module._resolveFilename 
> (node:internal/modules/cjs/loader:933:15)
> at Function.Module._load (node:internal/modules/cjs/loader:778:27)
> at Module.require (node:internal/modules/cjs/loader:1005:19)
> at require (node:internal/modules/cjs/helpers:102:18)
> at Object. 
> (/<>/debian/build_modules/@wessberg/rollup-plugin-ts/dist/cjs/index.js:15:19)
> at Module._compile (node:internal/modules/cjs/loader:1103:14)
> at Module._extensions..js (node:internal/modules/cjs/loader:1157:10)
> at Object.require.extensions. [as .js] 
> (/usr/share/nodejs/rollup/dist/shared/loadConfigFile.js:617:17)
> at Module.load (node:internal/modules/cjs/loader:981:32)
> at Function.Module._load (node:internal/modules/cjs/loader:822:12)
> 
> make[1]: *** [debian/rules:12: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/node-y18n_5.0.8+~5.0.0-1_unstable.log

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

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

If you reassign this bug to another package, please 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.



Bug#1011893: rbac-client-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.

2022-05-26 Thread Lucas Nussbaum
Source: rbac-client-clojure
Version: 0.9.4-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> lein test
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> This could be due to a typo in :dependencies, file system permissions, or 
> network issues.
> If you are behind a proxy, try setting the 'http_proxy' environment variable.
> make[1]: *** [debian/rules:25: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/rbac-client-clojure_0.9.4-2_unstable.log

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

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

If you reassign this bug to another package, please 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.



Processed: severity of 1002863 is serious

2022-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1002863 serious
Bug #1002863 [src:node-react-audio-player] node-react-audio-player: FTBFS with 
webpack5: Error: Invalid webpack options
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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



Processed: severity of 1002869 is serious

2022-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1002869 serious
Bug #1002869 [src:node-vue-resource] node-vue-resource: FTBFS with webpack5: 
Error: Invalid webpack options
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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



Processed: severity of 1002862 is serious

2022-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1002862 serious
Bug #1002862 [src:node-prop-types] node-prop-types: FTBFS with webpack5: Error: 
Invalid webpack options
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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



Bug#1011891: node-immutable: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

2022-05-26 Thread Lucas Nussbaum
Source: node-immutable
Version: 4.0.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rollup -c ./resources/rollup-config.js
> 
> /<>/src/Immutable.js → 
> dist/immutable.js...
> (!) Circular dependencies
> src/Seq.js -> src/Collection.js -> src/Seq.js
> src/Map.js -> src/Operations.js -> src/Map.js
> src/OrderedMap.js -> src/Map.js -> src/Operations.js -> src/OrderedMap.js
> ...and 6 more
> created dist/immutable.js in 3.2s
> rollup -c ./resources/rollup-config-es.js
> 
> /<>/src/Immutable.js → 
> dist/immutable.es.js...
> (!) Circular dependencies
> src/Seq.js -> src/Collection.js -> src/Seq.js
> src/Map.js -> src/Operations.js -> src/Map.js
> src/OrderedMap.js -> src/Map.js -> src/Operations.js -> src/OrderedMap.js
> ...and 6 more
> created dist/immutable.es.js in 1s
> cp type-definitions/immutable.* dist/
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   ln -s ../debian/tests/test_modules/jasmine-check 
> node_modules/jasmine-check
>   ln -s ../debian/tests/test_modules/make-synchronous 
> node_modules/make-synchronous
>   ln -s ../debian/tests/test_modules/subsume node_modules/subsume
>   ln -s ../debian/tests/test_modules/testcheck node_modules/testcheck
>   ln -s ../. node_modules/immutable
>   /bin/sh -ex debian/tests/pkg-js/test
> + [ -e node_modules/immutable ]
> + + grepls __tests__/ArraySeq.ts __tests__/Conversion.ts 
> __tests__/Equality.ts __tests__/IndexedSeq.ts __tests__/KeyedSeq.ts 
> __tests__/List.ts __tests__/Map.ts __tests__/ObjectSeq.ts 
> __tests__/OrderedMap.ts __tests__/OrderedSet.ts __tests__/Predicates.ts 
> __tests__/Range.ts __tests__/Record.ts __tests__/Repeat.ts __tests__/Seq.ts 
> __tests__/Set.ts __tests__/Stack.ts __tests__/concat.ts __tests__/count.ts 
> __tests__/find.ts __tests__/flatten.ts __tests__/fromJS.ts __tests__/get.ts 
> __tests__/getIn.ts __tests__/groupBy.ts __tests__/hasIn.ts __tests__/hash.ts 
> __tests__/interpose.ts __tests__/issues.ts __tests__/join.ts 
> __tests__/merge.ts __tests__/minmax.ts __tests__/slice.ts __tests__/sort.ts 
> __tests__/splice.ts __tests__/transformerProtocol.ts __tests__/updateIn.ts 
> __tests__/zip.ts
>  -v -f debian/tests/test_excluded
> + jest --ci -u __tests__/ArraySeq.ts __tests__/Conversion.ts 
> __tests__/Equality.ts __tests__/IndexedSeq.ts __tests__/KeyedSeq.ts 
> __tests__/ObjectSeq.ts __tests__/OrderedMap.ts __tests__/OrderedSet.ts 
> __tests__/Predicates.ts __tests__/Range.ts __tests__/Repeat.ts 
> __tests__/Stack.ts __tests__/concat.ts __tests__/count.ts __tests__/find.ts 
> __tests__/flatten.ts __tests__/get.ts __tests__/groupBy.ts __tests__/hash.ts 
> __tests__/interpose.ts __tests__/issues.ts __tests__/join.ts 
> __tests__/merge.ts __tests__/minmax.ts __tests__/slice.ts __tests__/sort.ts 
> __tests__/splice.ts __tests__/zip.ts
> ts-jest[config] (WARN) message TS151001: If you have issues 
> related to imports, you should consider setting `esModuleInterop` to `true` 
> in your TypeScript configuration file (usually `tsconfig.json`). See 
> https://blogs.msdn.microsoft.com/typescript/2018/01/31/announcing-typescript-2-7/#easier-ecmascript-module-interoperability
>  for more information.
> ts-jest[config] (WARN) message TS151001: If you have issues 
> related to imports, you should consider setting `esModuleInterop` to `true` 
> in your TypeScript configuration file (usually `tsconfig.json`). See 
> https://blogs.msdn.microsoft.com/typescript/2018/01/31/announcing-typescript-2-7/#easier-ecmascript-module-interoperability
>  for more information.
> ts-jest[config] (WARN) message TS151001: If you have issues 
> related to imports, you should consider setting `esModuleInterop` to `true` 
> in your TypeScript configuration file (usually `tsconfig.json`). See 
> https://blogs.msdn.microsoft.com/typescript/2018/01/31/announcing-typescript-2-7/#easier-ecmascript-module-interoperability
>  for more information.
> ts-jest[config] (WARN) message TS151001: If you have issues 
> related to imports, you should consider setting `esModuleInterop` to `true` 
> in your TypeScript configuration file (usually `tsconfig.json`). See 
> https://blogs.msdn.microsoft.com/typescript/2018/01/31/announcing-typescript-2-7/#easier-ecmascript-module-interoperability
>  for more information.
> ts-jest[config] (WARN) message TS151001: If you have issues 
> related to imports, you should consider setting `esModuleInterop` to `true` 
> in your TypeScript configuration file (usually `tsconfig.json`). See 
> https://blogs.msdn.microsoft.c

Bug#1011890: node-rollup-plugin-sass: FTBFS: node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations.

2022-05-26 Thread Lucas Nussbaum
Source: node-rollup-plugin-sass
Version: 1.2.6~dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> Link ./node_modules/pretty-format -> /usr/share/nodejs/pretty-format
> Link ./node_modules/rollup -> /usr/share/nodejs/rollup
> Link ./node_modules/ts-jest -> /usr/share/nodejs/ts-jest
> Link ./node_modules/@rollup/pluginutils -> 
> /usr/share/nodejs/@rollup/pluginutils
> Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node
> Link ./node_modules/@types/resolve -> /usr/share/nodejs/@types/resolve
> Link ./node_modules/@sinonjs/fake-timers -> 
> /usr/share/nodejs/@sinonjs/fake-timers
> Copy /usr/share/nodejs/jest-diff -> ./node_modules/
> Copy /usr/share/nodejs/@types/jest -> ./node_modules/@types
> Copy /usr/share/nodejs/@types/sinon -> ./node_modules/@types
> Link node_modules/@types/node-sass -> 
> ../../debian/build_modules/@types/node-sass
> Link node_modules/@types/sass -> ../../debian/build_modules/@types/sass
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> tsc
> node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 
> 'jest-matcher-utils' or its corresponding type declarations.
> make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/node-rollup-plugin-sass_1.2.6~dfsg-2_unstable.log

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

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

If you reassign this bug to another package, please 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.



Bug#1011889: haskell-tldr: FTBFS: make: *** [/usr/share/cdbs/1/rules/debhelper.mk:252: binary-install/libghc-tldr-doc] Error 25

2022-05-26 Thread Lucas Nussbaum
Source: haskell-tldr
Version: 0.6.4-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-tldr-doc.substvars
> dh_installdirs -plibghc-tldr-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe; haddock_recipe; build_recipe; check_recipe'
> Running find . ! -newer /tmp/uQrwkQAmnF -exec touch -d "1998-01-01 UTC" {} ;
> Running dh_listpackages
> libghc-tldr-dev
> libghc-tldr-prof
> libghc-tldr-doc
> tldr
> Running dh_listpackages
> libghc-tldr-dev
> libghc-tldr-prof
> libghc-tldr-doc
> tldr
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/tldr-0.6.4/ --datasubdir=tldr 
> --htmldir=/usr/share/doc/libghc-tldr-doc/html/ --enable-library-profiling
> Using Parsec parser
> Configuring tldr-0.6.4...
> Dependency ansi-terminal -any: using ansi-terminal-0.10.3
> Dependency base >=4.7 && <5: using base-4.13.0.0
> Dependency bytestring -any: using bytestring-0.10.10.1
> Dependency cmark -any: using cmark-0.6
> Dependency text -any: using text-1.2.4.0
> Dependency base -any: using base-4.13.0.0
> Dependency containers -any: using containers-0.6.2.1
> Dependency directory -any: using directory-1.3.6.0
> Dependency filepath -any: using filepath-1.4.2.1
> Dependency optparse-applicative -any: using optparse-applicative-0.15.1.0
> Dependency semigroups -any: using semigroups-0.19.1
> Dependency tldr -any: using tldr-0.6.4
> Dependency typed-process -any: using typed-process-0.2.6.0
> Source component graph:
> component lib
> component exe:tldr dependency lib
> Configured component graph:
> component tldr-0.6.4-AhmmP7VxCZp2l0XNdrEGdB
> include ansi-terminal-0.10.3-DS0jBrus2yKFjX9eUfmc3L
> include base-4.13.0.0
> include bytestring-0.10.10.1
> include cmark-0.6-60GhJwFkGY8112Jhy6cfyI
> include text-1.2.4.0
> component tldr-0.6.4-9kDqHmPjSlr7K1WcZsFaKh-tldr
> include base-4.13.0.0
> include containers-0.6.2.1
> include directory-1.3.6.0
> include filepath-1.4.2.1
> include optparse-applicative-0.15.1.0-GiY4uo4FBQRKuBqOktTXko
> include semigroups-0.19.1-LKdktuRRdRZ1yx9gBXzSbK
> include tldr-0.6.4-AhmmP7VxCZp2l0XNdrEGdB
> include typed-process-0.2.6.0-5au5NKOH3pCCyHyzwWiAiD
> Linked component graph:
> unit tldr-0.6.4-AhmmP7VxCZp2l0XNdrEGdB
> include ansi-terminal-0.10.3-DS0jBrus2yKFjX9eUfmc3L
> include base-4.13.0.0
> include bytestring-0.10.10.1
> include cmark-0.6-60GhJwFkGY8112Jhy6cfyI
> include text-1.2.4.0
> Tldr=tldr-0.6.4-AhmmP7VxCZp2l0XNdrEGdB:Tldr
> unit tldr-0.6.4-9kDqHmPjSlr7K1WcZsFaKh-tldr
> include base-4.13.0.0
> include containers-0.6.2.1
> include directory-1.3.6.0
> include filepath-1.4.2.1
> include optparse-applicative-0.15.1.0-GiY4uo4FBQRKuBqOktTXko
> include semigroups-0.19.1-LKdktuRRdRZ1yx9gBXzSbK
> include tldr-0.6.4-AhmmP7VxCZp2l0XNdrEGdB
> include typed-process-0.2.6.0-5au5NKOH3pCCyHyzwWiAiD
> Ready component graph:
> definite tldr-0.6.4-AhmmP7VxCZp2l0XNdrEGdB
> depends ansi-terminal-0.10.3-DS0jBrus2yKFjX9eUfmc3L
> depends base-4.13.0.0
> depends bytestring-0.10.10.1
> depends cmark-0.6-60GhJwFkGY8112Jhy6cfyI
> depends text-1.2.4.0
> definite tldr-0.6.4-9kDqHmPjSlr7K1WcZsFaKh-tldr
> depends base-4.13.0.0
> depends containers-0.6.2.1
> depends directory-1.3.6.0
> depends filepath-1.4.2.1
> depends optparse-applicative-0.15.1.0-GiY4uo4FBQRKuBqOktTXko
> depends semigroups-0.19.1-LKdktuRRdRZ1yx9gBXzSbK
> depends tldr-0.6.4-AhmmP7VxCZp2l0XNdrEGdB
> depends typed-process-0.2.6.0-5au5NKOH3pCCyHyzwWiAiD
> Using Cabal-3.0.1.0 compiled by ghc-8.8
> Using compiler: ghc-8.8.4
> Using install prefix: /usr
> Executables installed in: /usr/bin
> Libraries installed in:
> /usr/lib/haskell-packages/ghc/lib/x86_64-linux-gh

Bug#1011888: python-libzim: FTBFS: FAILED tests/test_libzim_creator.py::test_creator_metadata - RuntimeError: Im...

2022-05-26 Thread Lucas Nussbaum
Source: python-libzim
Version: 1.0.0+ds-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:239: python3.9 setup.py config 
> Using system installed library. We are assuming CFLAGS/LDFLAGS are correctly 
> set.
> Compiling libzim/libzim.pyx because it depends on 
> /usr/lib/python3/dist-packages/Cython/Includes/libcpp/utility.pxd.
> [1/1] Cythonizing libzim/libzim.pyx
> running config
> I: pybuild base:239: python3.10 setup.py config 
> Using system installed library. We are assuming CFLAGS/LDFLAGS are correctly 
> set.
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:239: /usr/bin/python3.9 setup.py build 
> Using system installed library. We are assuming CFLAGS/LDFLAGS are correctly 
> set.
> running build
> running build_py
> package init file 'libzim/__init__.py' not found (or not a regular file)
> running egg_info
> writing libzim.egg-info/PKG-INFO
> writing dependency_links to libzim.egg-info/dependency_links.txt
> writing top-level names to libzim.egg-info/top_level.txt
> reading manifest file 'libzim.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'lib/libzim.7.dylib'
> warning: no files found matching 'lib/libzim.so.7'
> warning: no files found matching 'libzim/*.cxx'
> warning: no files found matching 'libzim/*.py'
> warning: no previously-included files matching '__pycache__/*' found anywhere 
> in distribution
> adding license file 'LICENSE'
> writing manifest file 'libzim.egg-info/SOURCES.txt'
> creating /<>/.pybuild/cpython3_3.9_libzim/build/libzim
> copying libzim/libwrapper.cpp -> 
> /<>/.pybuild/cpython3_3.9_libzim/build/libzim
> copying libzim/libwrapper.h -> 
> /<>/.pybuild/cpython3_3.9_libzim/build/libzim
> copying libzim/libzim.cpp -> 
> /<>/.pybuild/cpython3_3.9_libzim/build/libzim
> copying libzim/libzim.h -> 
> /<>/.pybuild/cpython3_3.9_libzim/build/libzim
> copying libzim/libzim.pyx -> 
> /<>/.pybuild/cpython3_3.9_libzim/build/libzim
> copying libzim/libzim_api.h -> 
> /<>/.pybuild/cpython3_3.9_libzim/build/libzim
> copying libzim/zim.pxd -> 
> /<>/.pybuild/cpython3_3.9_libzim/build/libzim
> running build_ext
> building 'libzim' extension
> creating build
> creating build/temp.linux-x86_64-3.9
> creating build/temp.linux-x86_64-3.9/libzim
> x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat 
> -Werror=format-security -g -fwrapv -O2 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Ilibzim 
> -I/usr/include/python3.9 -c libzim/libwrapper.cpp -o 
> build/temp.linux-x86_64-3.9/libzim/libwrapper.o -std=c++11 -Wall -Wextra
> x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat 
> -Werror=format-security -g -fwrapv -O2 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Ilibzim 
> -I/usr/include/python3.9 -c libzim/libzim.cpp -o 
> build/temp.linux-x86_64-3.9/libzim/libzim.o -std=c++11 -Wall -Wextra
> x86_64-linux-gnu-g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g 
> -fwrapv -O2 -Wl,-z,relro -Wl,-z,now -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> build/temp.linux-x86_64-3.9/libzim/libwrapper.o 
> build/temp.linux-x86_64-3.9/libzim/libzim.o -lzim -o 
> /<>/.pybuild/cpython3_3.9_libzim/build/libzim.cpython-39-x86_64-linux-gnu.so
> I: pybuild base:239: /usr/bin/python3 setup.py build 
> Using system installed library. We are assuming CFLAGS/LDFLAGS are correctly 
> set.
> running build
> running build_py
> package init file 'libzim/__init__.py' not found (or not a regular file)
> running egg_info
> writing libzim.egg-info/PKG-INFO
> writing dependency_links to libzim.egg-info/dependency_links.txt
> writing top-level names to libzim.egg-info/top_level.txt
> reading manifest file 'libzim.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'lib/libzim.7.dylib'
> warning: no files found matching 'lib/libzim.so.7'
> warning: no files found matching 'libzim/*.cxx'
> warning: no files found matching 'libzim/*.py'
> warning: no previously-included files matching '__pycache__/*' found anywhere 
> in distribution
> adding license file 'LICENSE'
> writing manifest file 'libzim.egg-info/SOURCES.txt'
> creating /<>/.pybuild/cpython3_3.10_libz

Bug#1011886: orthanc-dicomweb: FTBFS: make[1]: *** [debian/rules:37: override_dh_auto_configure] Error 2

2022-05-26 Thread Lucas Nussbaum
Source: orthanc-dicomweb
Version: 1.7+dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cp /usr/share/javascript/jquery/jquery.min.js 
> Resources/Samples/JavaScript/jquery.min.js
> dh_auto_configure -- -DCMAKE_SKIP_RPATH:BOOL=ON -DSTATIC_BUILD:BOOL=OFF 
> -DORTHANC_FRAMEWORK_SOURCE:STRING=system 
> -DUSE_GOOGLE_TEST_DEBIAN_PACKAGE:BOOL=ON 
> -DORTHANC_FRAMEWORK_USE_SHARED:BOOL=OFF 
> "-DORTHANC_FRAMEWORK_ADDITIONAL_LIBRARIES=boost_filesystem boost_iostreams 
> boost_locale boost_regex boost_thread jsoncpp pugixml uuid sqlite3 dcmdata 
> dcmjpeg dcmjpls ofstd dcmimage" -DCMAKE_BUILD_TYPE=None  
>   cd Build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
> -DCMAKE_SKIP_RPATH:BOOL=ON -DSTATIC_BUILD:BOOL=OFF 
> -DORTHANC_FRAMEWORK_SOURCE:STRING=system 
> -DUSE_GOOGLE_TEST_DEBIAN_PACKAGE:BOOL=ON 
> -DORTHANC_FRAMEWORK_USE_SHARED:BOOL=OFF 
> "-DORTHANC_FRAMEWORK_ADDITIONAL_LIBRARIES=boost_filesystem boost_iostreams 
> boost_locale boost_regex boost_thread jsoncpp pugixml uuid sqlite3 dcmdata 
> dcmjpeg dcmjpls ofstd dcmimage" -DCMAKE_BUILD_TYPE=None ..
> CMake Deprecation Warning at CMakeLists.txt:20 (cmake_minimum_required):
>   Compatibility with CMake < 2.8.12 will be removed from a future version of
>   CMake.
> 
>   Update the VERSION argument  value or use a ... suffix to tell
>   CMake that the project does not need compatibility with older versions.
> 
> 
> -- The C compiler identification is GNU 11.3.0
> -- The CXX compiler identification is GNU 11.3.0
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Found PythonInterp: /usr/bin/python3.10 (found version "3.10.4") 
> JsonCpp include dir: /usr/include/jsoncpp
> -- Looking for C++ include /usr/include/jsoncpp/json/reader.h
> -- Looking for C++ include /usr/include/jsoncpp/json/reader.h - found
> JsonCpp major version: 1
> Switching to C++11 standard, as version of JsonCpp is >= 1.0.0
> Orthanc framework include dir: /usr/include/orthanc-framework
> Path to the Debian Google Test sources: /usr/src/gtest
> Path to the Debian Google Test includes: /usr/include/gtest
> CMake Error at debian/ThirdPartyDownloads/JavaScriptLibraries.cmake:10 (file):
>   file COPY cannot find "/usr/share/nodejs/axios/dist/axios.min.map": No such
>   file or directory.
> Call Stack (most recent call first):
>   CMakeLists.txt:93 (include)
> 
> 
> -- Looking for C++ include orthanc/OrthancCPlugin.h
> -- Looking for C++ include orthanc/OrthancCPlugin.h - found
> Setting the version of the library to 1.7
> -- Configuring incomplete, errors occurred!
> See also "/<>/Build/CMakeFiles/CMakeOutput.log".
>   cd Build && tail -v -n \+0 CMakeCache.txt
> ==> CMakeCache.txt <==
> # This is the CMakeCache file.
> # For build in directory: /<>/Build
> # It was generated by CMake: /usr/bin/cmake
> # You can edit this file to change values found and used by cmake.
> # If you do not want to change any of the values, simply exit the editor.
> # If you do want to change a value, simply edit, save, and exit the editor.
> # The syntax for the file is as follows:
> # KEY:TYPE=VALUE
> # KEY is the name of a variable in the cache.
> # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
> # VALUE is the current value for the KEY.
> 
> 
> # EXTERNAL cache entries
> 
> 
> //Allow CMake to download packages
> ALLOW_DOWNLOADS:BOOL=OFF
> 
> //Retrieve babel-polyfill from npm
> BUILD_BABEL_POLYFILL:BOOL=OFF
> 
> //Compile Bootstrap-Vue from sources
> BUILD_BOOTSTRAP_VUE:BOOL=OFF
> 
> //Path to a program.
> CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line
> 
> //Path to a program.
> CMAKE_AR:FILEPATH=/usr/bin/ar
> 
> //Choose the type of build, options are: None Debug Release RelWithDebInfo
> // MinSizeRel ...
> CMAKE_BUILD_TYPE:STRING=None
> 
> //Enable/Disable color output during build.
> CMAKE_COLOR_MAKEFILE:BOOL=ON
> 
> //CXX compiler
> CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++
> 
> //A wrapper around 'ar' adding the appropriate '--plugin' option
> // for the GCC compiler
> CMAKE_CXX_COMPILER_AR:FILEPATH=/usr/bin/gcc-ar-11
> 
> //A wrap

Bug#1011887: python-lunr: FTBFS: ModuleNotFoundError: No module named 'attr'

2022-05-26 Thread Lucas Nussbaum
Source: python-lunr
Version: 0.6.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYTHONPATH=. python3 -m sphinx -b html -N docs 
> /<>/debian/python-lunr-doc/usr/share/doc/python-lunr-doc/html
> Running Sphinx v4.5.0
> 
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/myst_parser/main.py", line 3, in 
> 
> import attr
> ModuleNotFoundError: No module named 'attr'
> The full traceback has been saved in /tmp/sphinx-err-2dh3fx_3.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> make[1]: *** [debian/rules:15: override_dh_sphinxdoc] Error 2


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/python-lunr_0.6.2-1_unstable.log

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

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

If you reassign this bug to another package, please 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.



Bug#1011885: node-define-lazy-prop: FTBFS: ReferenceError: require is not defined in ES module scope, you can use import instead

2022-05-26 Thread Lucas Nussbaum
Source: node-define-lazy-prop
Version: 3.0.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mjs2cjs -a
> Not found
> xo not found in nodejs directories
> Not found
> tsd not found in nodejs directories
> Not found
> ava not found in nodejs directories
> 
> ./index.js → ./dhnodejsBundle.cjs...
> (!) Entry module "index.js" is implicitly using "default" export 
> mode, which means for CommonJS output that its default export is assigned to 
> "module.exports". For many tools, such CommonJS output will not be 
> interchangeable with the original ES module. If this is intended, explicitly 
> set "output.exports" to either "auto" or "default", otherwise you might want 
> to consider changing the signature of "index.js" to use named exports 
> only.
> https://rollupjs.org/guide/en/#outputexports
> index.js
> created ./dhnodejsBundle.cjs in 20ms
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/define-lazy-prop
>   /bin/sh -ex debian/tests/pkg-js/test
> + tape test.js
> file:///<>/test.js:1
> const test = require('tape');
>  ^
> 
> ReferenceError: require is not defined in ES module scope, you can use import 
> instead
> This file is being treated as an ES module because it has a '.js' file 
> extension and '/<>/package.json' contains "type": "module". To 
> treat it as a CommonJS script, rename it to use the '.cjs' file extension.
> at file:///<>/test.js:1:14
> at ModuleJob.run (node:internal/modules/esm/module_job:197:25)
> at async Promise.all (index 0)
> at async ESMLoader.import (node:internal/modules/esm/loader:337:24)
> at async importModuleDynamicallyWrapper (node:internal/vm/module:437:15)
> 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/05/25/node-define-lazy-prop_3.0.0-4_unstable.log

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

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

If you reassign this bug to another package, please 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.



Bug#1011882: ordered-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.

2022-05-26 Thread Lucas Nussbaum
Source: ordered-clojure
Version: 1.5.9-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> lein test
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> This could be due to a typo in :dependencies, file system permissions, or 
> network issues.
> If you are behind a proxy, try setting the 'http_proxy' environment variable.
> make[1]: *** [debian/rules:23: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/ordered-clojure_1.5.9-3_unstable.log

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

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

If you reassign this bug to another package, please 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.



Bug#1011884: coffeescript: FTBFS: /bin/sh: 1: /usr/bin/licensecheck: not found

2022-05-26 Thread Lucas Nussbaum
Source: coffeescript
Version: 1.12.8~dfsg-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> CDBS WARNING:  copyright-check disabled - licensecheck is missing.
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> 
> Scanning upstream source for new/changed copyright notices...
> 
> set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive 
> --copyright --deb-fmt --ignore 
> '^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 -- * | 
> /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
> /bin/sh: 1: /usr/bin/licensecheck: not found
> 0 combinations of copyright and licensing found.
> No new copyright notices found - assuming no news is good news...
> touch debian/stamp-copyright-check
> mkdir -p "debian/upstream-cruft"
> cp -a "lib" "debian/upstream-cruft/lib";
> touch debian/stamp-upstream-cruft
> mkdir -p docs/v1/browser-compiler
> chmod +x bin/cake
> bin/cake build
> bin/cake build
> MINIFY=false bin/cake build:browser
> bin/cake test
> failed 1 and passed 855 tests in 1.87 seconds 
> 
>   reads history file 
>   TypeError: Cannot read properties of undefined (reading 'history')
> at /<>/test/repl.coffee:1:1
> at Function. (/<>/test/repl.coffee:1:1)
> at global.test (/<>/Cakefile:1:1)
> at testRepl (/<>/test/repl.coffee:1:1)
> at Object. (/<>/test/repl.coffee:1:1)
> at Object. (/<>/test/repl.coffee:1:1)
> at Module._compile (node:internal/modules/cjs/loader:1:1)
> at Object.exports.run 
> (/<>/lib/coffee-script/coffee-script.js:1:1)
> at runTests (/<>/Cakefile:1:1)
> at Object.action (/<>/Cakefile:1:1)
> at invoke (/<>/lib/coffee-script/cake.js:1:1)
> at Object.exports.run (/<>/lib/coffee-script/cake.js:1:1)
> at Object. (/<>/bin/cake:1:1)
> at Module._compile (node:internal/modules/cjs/loader:1:1)
> at Object.Module._extensions..js (node:internal/modules/cjs/loader:1:1)
> at Module.load (node:internal/modules/cjs/loader:1:1)
> at Function.Module._load (node:internal/modules/cjs/loader:1:1)
> at Function.executeUserEntryPoint [as runMain] 
> (node:internal/modules/run_main:1:1)
> at node:internal/main/run_main_module:1:1
>  
>   function() {
>   return fn(input, output, repl);
> }
> make: *** [debian/rules:37: debian/stamp-build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/coffeescript_1.12.8~dfsg-6_unstable.log

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

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

If you reassign this bug to another package, please 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.



Bug#1011883: haskell-wcwidth: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:188: install/libghc-wcwidth-doc] Error 25

2022-05-26 Thread Lucas Nussbaum
Source: haskell-wcwidth
Version: 0.0.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-wcwidth-doc.substvars
> dh_installdirs -plibghc-wcwidth-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe; haddock_recipe; build_recipe; check_recipe'
> Running find . ! -newer /tmp/uTagLh35uc -exec touch -d "1998-01-01 UTC" {} ;
> Running dh_listpackages
> libghc-wcwidth-dev
> libghc-wcwidth-prof
> libghc-wcwidth-doc
> Running dh_listpackages
> libghc-wcwidth-dev
> libghc-wcwidth-prof
> libghc-wcwidth-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro -Wl,-z,now
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --ghc-option=-optl-Wl,-z,now --haddockdir=/usr/lib/ghc-doc/haddock/wcwidth-/ 
> --datasubdir=wcwidth --htmldir=/usr/share/doc/libghc-wcwidth-doc/html/ 
> --enable-library-profiling
> Using Parsec parser
> Configuring wcwidth-0.0.2...
> Flags chosen: cli=False, split-base=True
> Dependency base ==4.*: using base-4.13.0.0
> Dependency containers -any: using containers-0.6.2.1
> Source component graph: component lib
> Configured component graph:
> component wcwidth-0.0.2-Dgss9EfJyRR4SDXGezAumY
> include base-4.13.0.0
> include containers-0.6.2.1
> Linked component graph:
> unit wcwidth-0.0.2-Dgss9EfJyRR4SDXGezAumY
> include base-4.13.0.0
> include containers-0.6.2.1
> 
> Data.Char.WCWidth=wcwidth-0.0.2-Dgss9EfJyRR4SDXGezAumY:Data.Char.WCWidth
> Ready component graph:
> definite wcwidth-0.0.2-Dgss9EfJyRR4SDXGezAumY
> depends base-4.13.0.0
> depends containers-0.6.2.1
> Using Cabal-3.0.1.0 compiled by ghc-8.8
> Using compiler: ghc-8.8.4
> Using install prefix: /usr
> Executables installed in: /usr/bin
> Libraries installed in:
> /usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/wcwidth-0.0.2-Dgss9EfJyRR4SDXGezAumY
> Dynamic Libraries installed in:
> /usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4
> Private executables installed in:
> /usr/lib/x86_64-linux-ghc-8.8.4/wcwidth-0.0.2
> Data files installed in: /usr/share/wcwidth
> Documentation installed in:
> /usr/share/doc/x86_64-linux-ghc-8.8.4/wcwidth-0.0.2
> Configuration files installed in: /usr/etc
> No alex found
> Using ar found on system at: /usr/bin/x86_64-linux-gnu-ar
> No c2hs found
> No cpphs found
> No doctest found
> Using gcc version 11 found on system at: /usr/bin/x86_64-linux-gnu-gcc
> Using ghc version 8.8.4 found on system at: /usr/bin/ghc
> Using ghc-pkg version 8.8.4 found on system at: /usr/bin/ghc-pkg
> No ghcjs found
> No ghcjs-pkg found
> No greencard found
> Using haddock version 2.23.0 found on system at: /usr/bin/haddock
> No happy found
> Using haskell-suite found on system at: haskell-suite-dummy-location
> Using haskell-suite-pkg found on system at: haskell-suite-pkg-dummy-location
> No hmake found
> Using hpc version 0.67 found on system at: /usr/bin/hpc
> Using hsc2hs version 0.68.7 found on system at: /usr/bin/hsc2hs
> No hscolour found
> No jhc found
> Using ld found on system at: /usr/bin/x86_64-linux-gnu-ld.gold
> No pkg-config found
> Using runghc version 8.8.4 found on system at: /usr/bin/runghc
> Using strip version 2.38 found on system at: /usr/bin/strip
> Using tar found on system at: /bin/tar
> No uhc found
> Running dh_listpackages
> libghc-wcwidth-dev
> libghc-wcwidth-prof
> libghc-wcwidth-doc
> Running debian/hlibrary.setup haddock --builddir=dist-ghc 
> --with-haddock=/usr/bin/haddock --with-ghc=ghc --verbose=2 --html --hoogle 
> --haddock-options="--mathjax=file:///usr/share/javascript/mathjax/MathJax.js" 
> --hyperlink-source
> /usr/bin/haddock --version
> /usr/bin/ghc --numeric-version
> /usr/bin/haddock --ghc-version 
> '--mathjax=file:///usr/share/javascript/mathjax/MathJax.js'
> /usr/bin/ghc --print-libdir
> /usr/bin/ghc-pkg init dist-ghc/package.conf.inplace
> creating dist-ghc/build
> creating dist-ghc/build/autogen
> creating dist-ghc/build/autogen
> Preprocessing library for wcwidth-0.0.2..
> Running Haddock on library for wcwidth-0.0.2..
> cre

  1   2   3   >