Processed: add upstream issue for omniauth 2.0 support

[Debian Bug Tracking System]

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

> forwarded 999713 https://github.com/tduehr/omniauth-cas3/issues/5
Bug #999713 [src:ruby-omniauth-cas3] ruby-omniauth-cas3: FTBFS with 
ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: 
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in 
activate_dependencies': Could not find 'omniauth' (~> 1.2) among 77 total 
gem(s) (Gem::MissingSpecError)
Set Bug forwarded-to-address to 
'https://github.com/tduehr/omniauth-cas3/issues/5'.
> thanks
Stopping processing here.

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

Bug#1008916: [gnome-online-accounts] invalidated credentials

[Lyndon Brown]

Package: gnome-online-accounts
Version: 3.44.0-1
Severity: serious

Please forgive me if I try to block the migration to testing
temporarily.

Some days ago when the big Gnome v42 update was pushed, for some reason
it invalidated the gmail credentials on both my machine and my mother's
(which I also have running Sid - please don't criticise). Whilst I was
able to log back into my own accounts, since I have 2FA and such
properly set up, my mother's primary account unfortunately was in a
much poorer state, and she is being blocked from regaining access to
her account by an impassible verification page, both in g-o-a and when
trying to alternatively log in via a web browser.

She is desperate to recover her gmail account and will be bringing her
computer over to me to look at within the next couple of days if things
go to plan. I intend to try downgrading g-o-a/evolution packages to
testing versions to see if the existing stored credentials will work
once more under those previous versions. If so then perhaps this may
help allow her to login through a webpage to set up better verification
info, or at least migrate the contents of her account to a new one.

Bug#1001661: Info received (Bug#1001661: Info received ((no subject)))

[nick black]

wait...even the most recent of these logs shows that it is
testing notcurses 3.0.4, which indeed had this timing problem on
input, which was fixed in notcurses 3.0.5:

Get:1 http://deb.debian.org/debian testing/main notcurses 3.0.4+dfsg.1-1 (dsc) 
[3,148 B]   

 
Get:2 http://deb.debian.org/debian testing/main notcurses 3.0.4+dfsg.1-1 (tar) 
[7,391 kB]  

 
Get:3 http://deb.debian.org/debian testing/main notcurses 3.0.4+dfsg.1-1 (asc) 
[833 B] 

 
Get:4 http://deb.debian.org/debian testing/main notcurses 3.0.4+dfsg.1-1 (diff) 
[17.1 kB] 

but apt-show-versions confirms only 3.0.7 in the archive:

[schwarzgerat](0) $ apt-show-versions -a notcurses-bin
notcurses-bin:amd64 3.0.7+dfsg.1-1 install ok installed
No stable version
No testing version
notcurses-bin:amd64 3.0.7+dfsg.1-1 unstable ftp.us.debian.org
No experimental version
notcurses-bin:amd64/unstable 3.0.7+dfsg.1-1 uptodate
[schwarzgerat](0) $

oh, i guess "No testing version" indicates it's gone from
testing. so why isn't 3.0.7 in unstable the candidate for
testing? 3.0.4 is definitely known to be bad.

Bug#1001661: Info received ((no subject))

[nick black]

i'm tracking this upstream at 
https://github.com/dankamongmen/notcurses/issues/2645

Bug#1001661: notcurses: flaky autopkgtests on armhf

[nick black]

i'm pretty sure raspberry pi is armhf, so i ought be able to dig
that one RPi4 i've got up and explore this. if we can reproduce
the problem interactively, it ought fall pretty quickly.

Bug#1001661: (no subject)

[nick black]

note that armhf is a 32-bit arm7 machine, unlike arm64 which is
arm8. might be time to revisit some assumptions unconsciously
made involving processor width.

Processed: tagging 1008641

[Debian Bug Tracking System]

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

> # Actually https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008641#10 was 
> not refering to upstream but to Ubuntu patches
> tags 1008641 - fixed-upstream + patch
Bug #1008641 [src:unbound] unbound: FTBFS: ./pythonmod/pythonmod.c:338: 
undefined reference to `_Py_fopen'
Bug #1008650 [src:unbound] python3-unbound: Cannot install because of Python 
dependencies
Removed tag(s) fixed-upstream.
Removed tag(s) fixed-upstream.
Bug #1008641 [src:unbound] unbound: FTBFS: ./pythonmod/pythonmod.c:338: 
undefined reference to `_Py_fopen'
Bug #1008650 [src:unbound] python3-unbound: Cannot install because of Python 
dependencies
Added tag(s) patch.
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: Re: gprbuild: FTBFS during binary-indep build

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + unreproducible
Bug #1008152 [src:gprbuild] gprbuild: FTBFS during binary-indep build
Added tag(s) unreproducible.

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

Bug#1008152: gprbuild: FTBFS during binary-indep build

[Nicolas Boulenguez]

Source: gprbuild
Followup-For: Bug #1008152
Control: tags -1 + unreproducible

Hello.
For unrelated reasons, I have updated gprbuild in experimental.
The -indep build seems to succeed on a build machine.
https://buildd.debian.org/status/fetch.php?pkg=gprbuild&arch=all&ver=2022.0.0-2&stamp=1648992585&raw=0
Until we find a way to reproduce the failure, I suggest to lower the
severity to important or normal.

Bug#1008905: marked as done (node-rollup-plugin-terser: autopkgtest regression in testing)

[Debian Bug Tracking System]

Your message dated Mon, 04 Apr 2022 04:33:47 +
with message-id 
and subject line Bug#1008908: fixed in node-p-locate 6.0.0-9
has caused the Debian Bug report #1008908,
regarding node-rollup-plugin-terser: autopkgtest regression in testing
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.)


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

Source: node-rollup-plugin-terser
Version: 7.0.2+~5.0.1-2
Severity: serious
Justification: autopkgtest regression

Dear maintainer,

Your package has an autopkgtest, great. However, it recently started
to fail in testing, I suspect since nodejs migrated.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-rollup-plugin-terser/20508689/log.gz

true both import and export can be overwritten
+ jest --ci --testTimeout 6 test/test.js
internal/modules/cjs/loader.js:1015
  throw new ERR_REQUIRE_ESM(filename, parentPath, packageJsonPath);
  ^

Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: 
/usr/share/nodejs/p-limit/index.js

require() of ES modules is not supported.
require() of /usr/share/nodejs/p-limit/index.js from 
/usr/share/nodejs/p-locate/index.js is an ES module file as it is a .js 
file whose nearest parent package.json contains "type": "module" which 
defines all .js files in that package scope as ES modules.
Instead rename /usr/share/nodejs/p-limit/index.js to end in .cjs, change 
the requiring code to use import(), or remove "type": "module" from 
/usr/share/nodejs/p-limit/package.json.


at Object.Module._extensions..js 
(internal/modules/cjs/loader.js:1015:13)

at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. (/usr/share/nodejs/p-locate/index.js:2:16)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions..js 
(internal/modules/cjs/loader.js:1027:10)

at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14) {
  code: 'ERR_REQUIRE_ESM'
}
autopkgtest [22:51:51]: test pkg-js-autopkgtest: ---]


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-p-locate
Source-Version: 6.0.0-9
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-p-locate 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, 04 Apr 2022 06:10:25 +0200
Source: node-p-locate
Architecture: source
Version: 6.0.0-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1008908
Changes:
 node-p-locate (6.0.0-9) unstable; urgency=medium
 .
   * Team upload
   * Build commonjs files (Closes: #1008908)
Checksums-Sha1: 
 c5fa7dcac1cc2b5423dc13c3b93b1299c043092f 2134 node-p-locate_6.0.0-9.dsc
 4c8f6f69e36236145329cd89399db7fa21eef895 81564 
node-p-locate_6.0.0-9.debian.tar.xz
Checksums-Sha256: 
 6b7a095066a83677ebfdc2cf1580eeef24891465d41b911d35a97671580382c5 2134 
node-p-locate_6.0.0-9.dsc
 c6104e212241917c91950fe744a591670a30751db49ff47375b96f2ac8958319 81564 
node-p-locate_6.0.0-9.debian.tar.xz
Files: 
 5ea443becb80ff5181d60c3b7c35f575 2134 javascript optional 
node-p-locate_6.0.0-9.dsc
 34ab576cb155d6a1f1e1de78e2be0746 81564 javascript optional 
node-p-locate_6.0.0-9.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmJKcBcACgkQ9tdMp8mZ
7uk0XA//Y403EZOBKdTjC05fJEuKK1SGxdhJQDafoENHedZPWDaPRbZNlcMw/qoV
IA6gtv3udlorNya88VOXpoEhXRCFtJVyvZhOtC2HcApz/deqZYtOJa/CwjVU+4Ua
FKHEgQ3/AzoE79b48EsVZNBk7VLCZ3eeu/Qr/7SABaoVy4LimlOp5UCJbDuUOl6O
rXgRtxya7fOX3rx7EjQ4/Fg0HRRyG79KUMWKntfRmtuxBAqwCEOyaPCJmG+QaS63
gLfA+aQcQcdqxNvQRoYue9KfEPmzZH

Bug#1008906: marked as done (node-keygrip: autopkgtest regression in testing)

[Debian Bug Tracking System]

Your message dated Mon, 04 Apr 2022 04:33:47 +
with message-id 
and subject line Bug#1008908: fixed in node-p-locate 6.0.0-9
has caused the Debian Bug report #1008908,
regarding node-keygrip: autopkgtest regression in testing
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.)


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

Source: node-keygrip
Version: 1.1.0-2
Severity: serious
Justification: autopkgtest regression

Dear maintainer,

Your package has an autopkgtest, great. However, it recently started
to fail in testing, I suspect since nodejs migrated.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-keygrip/20552579/log.gz

+ mocha --reporter spec test/
internal/modules/cjs/loader.js:1102
  throw new ERR_REQUIRE_ESM(filename, parentPath, packageJsonPath);
  ^

Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: 
/usr/share/nodejs/p-limit/index.js

require() of ES modules is not supported.
require() of /usr/share/nodejs/p-limit/index.js from 
/usr/share/nodejs/p-locate/index.js is an ES module file as it is a .js 
file whose nearest parent package.json contains "type": "module" which 
defines all .js files in that package scope as ES modules.
Instead rename /usr/share/nodejs/p-limit/index.js to end in .cjs, change 
the requiring code to use import(), or remove "type": "module" from 
/usr/share/nodejs/p-limit/package.json.


at new NodeError (internal/errors.js:322:7)
at Object.Module._extensions..js 
(internal/modules/cjs/loader.js:1102:13)

at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12)
at Module.require (internal/modules/cjs/loader.js:974:19)
at require (internal/modules/cjs/helpers.js:101:18)
at Object. (/usr/share/nodejs/p-locate/index.js:2:16)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js 
(internal/modules/cjs/loader.js:1114:10)

at Module.load (internal/modules/cjs/loader.js:950:32) {
  code: 'ERR_REQUIRE_ESM'
}
autopkgtest [04:12:55]: test pkg-js-autopkgtest: ---]


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-p-locate
Source-Version: 6.0.0-9
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-p-locate 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, 04 Apr 2022 06:10:25 +0200
Source: node-p-locate
Architecture: source
Version: 6.0.0-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1008908
Changes:
 node-p-locate (6.0.0-9) unstable; urgency=medium
 .
   * Team upload
   * Build commonjs files (Closes: #1008908)
Checksums-Sha1: 
 c5fa7dcac1cc2b5423dc13c3b93b1299c043092f 2134 node-p-locate_6.0.0-9.dsc
 4c8f6f69e36236145329cd89399db7fa21eef895 81564 
node-p-locate_6.0.0-9.debian.tar.xz
Checksums-Sha256: 
 6b7a095066a83677ebfdc2cf1580eeef24891465d41b911d35a97671580382c5 2134 
node-p-locate_6.0.0-9.dsc
 c6104e212241917c91950fe744a591670a30751db49ff47375b96f2ac8958319 81564 
node-p-locate_6.0.0-9.debian.tar.xz
Files: 
 5ea443becb80ff5181d60c3b7c35f575 2134 javascript optional 
node-p-locate_6.0.0-9.dsc
 34ab576cb155d6a1f1e1de78e2be0746 81564 javascript optional 
node-p-locate_6.0.0-9.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmJKcBcACgkQ9tdMp8mZ
7uk0XA//Y403EZOBKdTjC05fJEuKK1SGxdhJQDafoENHedZPWDaPRbZNlcMw/qoV
IA6gtv3udlorNya88VOXpoEhXRCFtJVyvZhOtC2HcApz/deqZYtOJa/CwjVU+4Ua
FKHEgQ3/AzoE79b48EsVZNBk7VLCZ3eeu/Qr/7SABaoVy4LimlOp5UCJbDuUOl6O
rXgRtxya7fOX3rx7EjQ4/Fg0HRRyG79KUMWKntfRmtuxBAqwCEOyaPCJmG+QaS63
gLfA+aQcQcdqxNvQRoYue9KfEPmzZHOFlUiFbGFtFETKmuFRTtyZfPUcYcWeq3Xv
vwbVTRFUreY1P/IfHFnRj61SoeNlVSBlu1t5AR5iRKiOQ0XAHCafSLJMr0MH4rCF
8t68JkZafc0580Jzt5j75JZ3bHv

Bug#1008903: marked as done (node-make-error: autopkgtest regression in testing)

[Debian Bug Tracking System]

Your message dated Mon, 04 Apr 2022 04:33:47 +
with message-id 
and subject line Bug#1008908: fixed in node-p-locate 6.0.0-9
has caused the Debian Bug report #1008908,
regarding node-make-error: autopkgtest regression in testing
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.)


-- 
1008908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-make-error
Version: 1.3.7-2
Severity: serious
Justification: autopkgtest regression

Dear maintainer,

Your package has an autopkgtest, great. However, it recently started
to fail in testing, I suspect since nodejs migrated.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-make-error/20508688/log.gz

autopkgtest [22:49:57]: test testsuite: [---
internal/modules/cjs/loader.js:1015
  throw new ERR_REQUIRE_ESM(filename, parentPath, packageJsonPath);
  ^

Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: 
/usr/share/nodejs/p-limit/index.js
require() of ES modules is not supported.
require() of /usr/share/nodejs/p-limit/index.js from 
/usr/share/nodejs/p-locate/index.js is an ES module file as it is a .js file 
whose nearest parent package.json contains "type": "module" which defines all 
.js files in that package scope as ES modules.
Instead rename /usr/share/nodejs/p-limit/index.js to end in .cjs, change the 
requiring code to use import(), or remove "type": "module" from 
/usr/share/nodejs/p-limit/package.json.

at Object.Module._extensions..js (internal/modules/cjs/loader.js:1015:13)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. (/usr/share/nodejs/p-locate/index.js:2:16)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14) {
  code: 'ERR_REQUIRE_ESM'
}
autopkgtest [22:49:57]: test testsuite: ---]
--- End Message ---
--- Begin Message ---
Source: node-p-locate
Source-Version: 6.0.0-9
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-p-locate 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, 04 Apr 2022 06:10:25 +0200
Source: node-p-locate
Architecture: source
Version: 6.0.0-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1008908
Changes:
 node-p-locate (6.0.0-9) unstable; urgency=medium
 .
   * Team upload
   * Build commonjs files (Closes: #1008908)
Checksums-Sha1: 
 c5fa7dcac1cc2b5423dc13c3b93b1299c043092f 2134 node-p-locate_6.0.0-9.dsc
 4c8f6f69e36236145329cd89399db7fa21eef895 81564 
node-p-locate_6.0.0-9.debian.tar.xz
Checksums-Sha256: 
 6b7a095066a83677ebfdc2cf1580eeef24891465d41b911d35a97671580382c5 2134 
node-p-locate_6.0.0-9.dsc
 c6104e212241917c91950fe744a591670a30751db49ff47375b96f2ac8958319 81564 
node-p-locate_6.0.0-9.debian.tar.xz
Files: 
 5ea443becb80ff5181d60c3b7c35f575 2134 javascript optional 
node-p-locate_6.0.0-9.dsc
 34ab576cb155d6a1f1e1de78e2be0746 81564 javascript optional 
node-p-locate_6.0.0-9.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmJKcBcACgkQ9tdMp8mZ
7uk0XA//Y403EZOBKdTjC05fJEuKK1SGxdhJQDafoENHedZPWDaPRbZNlcMw/qoV
IA6gtv3udlorNya88VOXpoEhXRCFtJVyvZhOtC2HcApz/deqZYtOJa/CwjVU+4Ua
FKHEgQ3/AzoE79b48EsVZNBk7VLCZ3eeu/Qr/7SABaoVy4LimlOp5UCJbDuUOl6O
rXgRtxya7fOX3rx7EjQ4/Fg0HRRyG79KUMWKntfRmtuxBAqwCEOyaPCJmG+QaS63
gLfA+aQcQcdqxNvQRoYue9KfEPmzZHOFlUiFbGFtFETKmuFRTtyZfPUcYcWeq3Xv
vwbVTRFUreY1P/IfHFnRj61SoeNlVSBlu1t5AR5iRKiOQ0XAHCafSLJMr0MH4rCF
8t68JkZafc0580Jzt5j75JZ3bHvM2zJq1fWzz4Z

Bug#1008908: marked as done (node-p-locate: please export as commonjs module)

[Debian Bug Tracking System]

Your message dated Mon, 04 Apr 2022 04:33:47 +
with message-id 
and subject line Bug#1008908: fixed in node-p-locate 6.0.0-9
has caused the Debian Bug report #1008908,
regarding node-p-locate: please export as commonjs module
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.)


-- 
1008908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-p-locate
Version: 6.0.0-8
Severity: serious
Justification: autopkgtest regressions

Hi,

this is the cause of several regressions.


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

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

Versions of packages node-p-locate depends on:
ii  node-p-limit  4.0.0+~cs4.0.0-3

node-p-locate recommends no packages.

node-p-locate suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: node-p-locate
Source-Version: 6.0.0-9
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-p-locate 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, 04 Apr 2022 06:10:25 +0200
Source: node-p-locate
Architecture: source
Version: 6.0.0-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1008908
Changes:
 node-p-locate (6.0.0-9) unstable; urgency=medium
 .
   * Team upload
   * Build commonjs files (Closes: #1008908)
Checksums-Sha1: 
 c5fa7dcac1cc2b5423dc13c3b93b1299c043092f 2134 node-p-locate_6.0.0-9.dsc
 4c8f6f69e36236145329cd89399db7fa21eef895 81564 
node-p-locate_6.0.0-9.debian.tar.xz
Checksums-Sha256: 
 6b7a095066a83677ebfdc2cf1580eeef24891465d41b911d35a97671580382c5 2134 
node-p-locate_6.0.0-9.dsc
 c6104e212241917c91950fe744a591670a30751db49ff47375b96f2ac8958319 81564 
node-p-locate_6.0.0-9.debian.tar.xz
Files: 
 5ea443becb80ff5181d60c3b7c35f575 2134 javascript optional 
node-p-locate_6.0.0-9.dsc
 34ab576cb155d6a1f1e1de78e2be0746 81564 javascript optional 
node-p-locate_6.0.0-9.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmJKcBcACgkQ9tdMp8mZ
7uk0XA//Y403EZOBKdTjC05fJEuKK1SGxdhJQDafoENHedZPWDaPRbZNlcMw/qoV
IA6gtv3udlorNya88VOXpoEhXRCFtJVyvZhOtC2HcApz/deqZYtOJa/CwjVU+4Ua
FKHEgQ3/AzoE79b48EsVZNBk7VLCZ3eeu/Qr/7SABaoVy4LimlOp5UCJbDuUOl6O
rXgRtxya7fOX3rx7EjQ4/Fg0HRRyG79KUMWKntfRmtuxBAqwCEOyaPCJmG+QaS63
gLfA+aQcQcdqxNvQRoYue9KfEPmzZHOFlUiFbGFtFETKmuFRTtyZfPUcYcWeq3Xv
vwbVTRFUreY1P/IfHFnRj61SoeNlVSBlu1t5AR5iRKiOQ0XAHCafSLJMr0MH4rCF
8t68JkZafc0580Jzt5j75JZ3bHvM2zJq1fWzz4Z+h0WeOUuZ3NTRk7eIow5kFIqu
tVEVeJpgrYONVxw3aNbZsgo6q5jWoTIV/qk7Y3B7VohA8ir7BeNSi0oqK27E9NYz
EZmkkqhFnbYTHh7rXPz72rz2uRFZidfzIJMlmkSArMVfQBNcvs8CSDLMwLnlcu/v
VzUJtkblEp9LNbjKAgfUrMbXOx4qJOuczOlYPUWG4rQXpE9v/02kgc5YAnrJi78u
Iu7tyko/jW3UprP6iBK8OJPtCLGCvQM/0MLr1UdZbvTFmJvtOwo=
=7Pn8
-END PGP SIGNATURE End Message ---

Bug#1008902: marked as done (node-puppeteer: autopkgtest regression in testing)

[Debian Bug Tracking System]

Your message dated Mon, 04 Apr 2022 04:33:47 +
with message-id 
and subject line Bug#1008908: fixed in node-p-locate 6.0.0-9
has caused the Debian Bug report #1008908,
regarding node-puppeteer: autopkgtest regression in testing
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.)


-- 
1008908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-puppeteer
Version: 13.4.1+dfsg-1
Severity: serious
Justification: autopkgtest regression

Dear maintainer,

Because your autopkgtest showed up as a blocker for chromium again (on
i386 and armhf), I just tried a reference run again on i386 and it
failed, while it succeeded not too long ago. (I suspect this is
related to the nodejs transition that just happened).

Anyways, your autopkgtest fails, please fix it.

Paul
--- End Message ---
--- Begin Message ---
Source: node-p-locate
Source-Version: 6.0.0-9
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-p-locate 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, 04 Apr 2022 06:10:25 +0200
Source: node-p-locate
Architecture: source
Version: 6.0.0-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1008908
Changes:
 node-p-locate (6.0.0-9) unstable; urgency=medium
 .
   * Team upload
   * Build commonjs files (Closes: #1008908)
Checksums-Sha1: 
 c5fa7dcac1cc2b5423dc13c3b93b1299c043092f 2134 node-p-locate_6.0.0-9.dsc
 4c8f6f69e36236145329cd89399db7fa21eef895 81564 
node-p-locate_6.0.0-9.debian.tar.xz
Checksums-Sha256: 
 6b7a095066a83677ebfdc2cf1580eeef24891465d41b911d35a97671580382c5 2134 
node-p-locate_6.0.0-9.dsc
 c6104e212241917c91950fe744a591670a30751db49ff47375b96f2ac8958319 81564 
node-p-locate_6.0.0-9.debian.tar.xz
Files: 
 5ea443becb80ff5181d60c3b7c35f575 2134 javascript optional 
node-p-locate_6.0.0-9.dsc
 34ab576cb155d6a1f1e1de78e2be0746 81564 javascript optional 
node-p-locate_6.0.0-9.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmJKcBcACgkQ9tdMp8mZ
7uk0XA//Y403EZOBKdTjC05fJEuKK1SGxdhJQDafoENHedZPWDaPRbZNlcMw/qoV
IA6gtv3udlorNya88VOXpoEhXRCFtJVyvZhOtC2HcApz/deqZYtOJa/CwjVU+4Ua
FKHEgQ3/AzoE79b48EsVZNBk7VLCZ3eeu/Qr/7SABaoVy4LimlOp5UCJbDuUOl6O
rXgRtxya7fOX3rx7EjQ4/Fg0HRRyG79KUMWKntfRmtuxBAqwCEOyaPCJmG+QaS63
gLfA+aQcQcdqxNvQRoYue9KfEPmzZHOFlUiFbGFtFETKmuFRTtyZfPUcYcWeq3Xv
vwbVTRFUreY1P/IfHFnRj61SoeNlVSBlu1t5AR5iRKiOQ0XAHCafSLJMr0MH4rCF
8t68JkZafc0580Jzt5j75JZ3bHvM2zJq1fWzz4Z+h0WeOUuZ3NTRk7eIow5kFIqu
tVEVeJpgrYONVxw3aNbZsgo6q5jWoTIV/qk7Y3B7VohA8ir7BeNSi0oqK27E9NYz
EZmkkqhFnbYTHh7rXPz72rz2uRFZidfzIJMlmkSArMVfQBNcvs8CSDLMwLnlcu/v
VzUJtkblEp9LNbjKAgfUrMbXOx4qJOuczOlYPUWG4rQXpE9v/02kgc5YAnrJi78u
Iu7tyko/jW3UprP6iBK8OJPtCLGCvQM/0MLr1UdZbvTFmJvtOwo=
=7Pn8
-END PGP SIGNATURE End Message ---

Processed: affects 1008903

[Debian Bug Tracking System]

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

> affects 1008903 node-make-error node-rollup-plugin-terser node-keygrip
Bug #1008903 {Done: Yadd } [node-p-limit] node-make-error: 
autopkgtest regression in testing
Bug #1008902 {Done: Yadd } [node-p-limit] node-puppeteer: 
autopkgtest regression in testing
Bug #1008905 {Done: Yadd } [node-p-limit] 
node-rollup-plugin-terser: autopkgtest regression in testing
Bug #1008906 {Done: Yadd } [node-p-limit] node-keygrip: 
autopkgtest regression in testing
Bug #1008908 {Done: Yadd } [node-p-limit] node-p-locate: 
please export as commonjs module
Added indication that 1008903 affects node-make-error, 
node-rollup-plugin-terser, and node-keygrip
Added indication that 1008902 affects node-make-error, 
node-rollup-plugin-terser, and node-keygrip
Added indication that 1008905 affects node-make-error, 
node-rollup-plugin-terser, and node-keygrip
Added indication that 1008906 affects node-make-error, 
node-rollup-plugin-terser, and node-keygrip
Added indication that 1008908 affects node-make-error, 
node-rollup-plugin-terser, and node-keygrip
> thanks
Stopping processing here.

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

Processed: reassign 1008903 to node-p-limit, reassign 1008905 to node-p-limit, reassign 1008906 to node-p-limit ...

[Debian Bug Tracking System]

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

> reassign 1008903 node-p-limit
Bug #1008903 [node-p-locate] node-make-error: autopkgtest regression in testing
Bug #1008902 [node-p-locate] node-puppeteer: autopkgtest regression in testing
Bug #1008905 [node-p-locate] node-rollup-plugin-terser: autopkgtest regression 
in testing
Bug #1008906 [node-p-locate] node-keygrip: autopkgtest regression in testing
Bug #1008908 [node-p-locate] node-p-locate: please export as commonjs module
Bug reassigned from package 'node-p-locate' to 'node-p-limit'.
Bug reassigned from package 'node-p-locate' to 'node-p-limit'.
Bug reassigned from package 'node-p-locate' to 'node-p-limit'.
Bug reassigned from package 'node-p-locate' to 'node-p-limit'.
Bug reassigned from package 'node-p-locate' to 'node-p-limit'.
No longer marked as found in versions node-p-locate/6.0.0-8.
No longer marked as found in versions node-p-locate/6.0.0-8.
No longer marked as found in versions node-p-locate/6.0.0-8.
No longer marked as found in versions node-p-locate/6.0.0-8.
No longer marked as found in versions node-p-locate/6.0.0-8.
Ignoring request to alter fixed versions of bug #1008903 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1008902 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1008905 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1008906 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1008908 to the same values 
previously set
> reassign 1008905 node-p-limit
Bug #1008905 [node-p-limit] node-rollup-plugin-terser: autopkgtest regression 
in testing
Bug #1008902 [node-p-limit] node-puppeteer: autopkgtest regression in testing
Bug #1008903 [node-p-limit] node-make-error: autopkgtest regression in testing
Bug #1008906 [node-p-limit] node-keygrip: autopkgtest regression in testing
Bug #1008908 [node-p-limit] node-p-locate: please export as commonjs module
Ignoring request to reassign bug #1008905 to the same package
Ignoring request to reassign bug #1008902 to the same package
Ignoring request to reassign bug #1008903 to the same package
Ignoring request to reassign bug #1008906 to the same package
Ignoring request to reassign bug #1008908 to the same package
> reassign 1008906 node-p-limit
Bug #1008906 [node-p-limit] node-keygrip: autopkgtest regression in testing
Bug #1008902 [node-p-limit] node-puppeteer: autopkgtest regression in testing
Bug #1008903 [node-p-limit] node-make-error: autopkgtest regression in testing
Bug #1008905 [node-p-limit] node-rollup-plugin-terser: autopkgtest regression 
in testing
Bug #1008908 [node-p-limit] node-p-locate: please export as commonjs module
Ignoring request to reassign bug #1008906 to the same package
Ignoring request to reassign bug #1008902 to the same package
Ignoring request to reassign bug #1008903 to the same package
Ignoring request to reassign bug #1008905 to the same package
Ignoring request to reassign bug #1008908 to the same package
> forcemerge 1008903 1008905 1008906
Bug #1008903 [node-p-limit] node-make-error: autopkgtest regression in testing
Bug #1008902 [node-p-limit] node-puppeteer: autopkgtest regression in testing
Bug #1008905 [node-p-limit] node-rollup-plugin-terser: autopkgtest regression 
in testing
Bug #1008906 [node-p-limit] node-keygrip: autopkgtest regression in testing
Bug #1008908 [node-p-limit] node-p-locate: please export as commonjs module
Bug #1008902 [node-p-limit] node-puppeteer: autopkgtest regression in testing
Bug #1008905 [node-p-limit] node-rollup-plugin-terser: autopkgtest regression 
in testing
Bug #1008906 [node-p-limit] node-keygrip: autopkgtest regression in testing
Bug #1008908 [node-p-limit] node-p-locate: please export as commonjs module
Merged 1008902 1008903 1008905 1008906 1008908
> fixed 1008903 4.0.0+~cs4.0.0-3
Bug #1008903 [node-p-limit] node-make-error: autopkgtest regression in testing
Bug #1008902 [node-p-limit] node-puppeteer: autopkgtest regression in testing
Bug #1008905 [node-p-limit] node-rollup-plugin-terser: autopkgtest regression 
in testing
Bug #1008906 [node-p-limit] node-keygrip: autopkgtest regression in testing
Bug #1008908 [node-p-limit] node-p-locate: please export as commonjs module
Marked as fixed in versions node-p-limit/4.0.0+~cs4.0.0-3.
Marked as fixed in versions node-p-limit/4.0.0+~cs4.0.0-3.
Marked as fixed in versions node-p-limit/4.0.0+~cs4.0.0-3.
Marked as fixed in versions node-p-limit/4.0.0+~cs4.0.0-3.
Marked as fixed in versions node-p-limit/4.0.0+~cs4.0.0-3.
> close 1008903
Bug #1008903 [node-p-limit] node-make-error: autopkgtest regression in testing
Bug #1008902 [node-p-limit] node-puppeteer: autopkgtest regression in testing
Bug #1008905 [node-p-limit] node-rollup-plugin-terser: autopkgtest regression 
in testing
Bug #1008906 [node-p-limit] node-keygrip: autopkgtest regression in testing
Bug #1008908 [node-p-limit] node-p-locate: please export as commonjs module
Marked

Bug#1008801: marked as done (gnucash: FTBFS on armhf when built on 64bit hardware)

[Debian Bug Tracking System]

Your message dated Mon, 04 Apr 2022 01:48:53 +
with message-id 
and subject line Bug#1008801: fixed in gnucash 1:4.10-2
has caused the Debian Bug report #1008801,
regarding gnucash: FTBFS on armhf when built on 64bit hardware
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.)


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

gnucash FTBFS on armel:

 56/118 Test  #56: test-gnc-numeric .   Passed0.01 sec
Start  57: test-gnc-timezone
 57/118 Test  #57: test-gnc-timezone Bus error***Exception:   
0.01 sec
Start  58: test-gnc-datetime
 58/118 Test  #58: test-gnc-datetime Bus error***Exception:   
0.01 sec
Start  59: test-import-map

…

The following tests FAILED:
 57 - test-gnc-timezone (Bus error)
 58 - test-gnc-datetime (Bus error)
Errors while running CTest
Output from these tests are in: 
/<>/.build/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
make[5]: *** [CMakeFiles/check.dir/build.make:73: CMakeFiles/check] Error 8

See
https://buildd.debian.org/status/fetch.php?pkg=gnucash&arch=armhf&ver=1%3A4.10-1&stamp=1648644190&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: gnucash
Source-Version: 1:4.10-2
Done: Dmitry Smirnov 

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated gnucash package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Apr 2022 11:25:03 +1000
Source: gnucash
Architecture: source
Version: 1:4.10-2
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Closes: 1008801
Changes:
 gnucash (1:4.10-2) unstable; urgency=medium
 .
   * New upstream patch to fix test failure on armhf (Closes: #1008801)
 Thanks, Adrian Bunk, John Ralls.
Checksums-Sha1:
 63b8d94c0ed354a820c65a88276ca1dd0fa8335b 2378 gnucash_4.10-2.dsc
 a3365990ba81951b2fe2de50fe4b2e5fd29b47b3 37072 gnucash_4.10-2.debian.tar.xz
 61340dd13670fe736905dc01608d2d4dc9a25ea3 24826 gnucash_4.10-2_amd64.buildinfo
Checksums-Sha256:
 81e2d57c6858f457db4f8bd6adaa3841a02500ef21c11a00300760d1315adf03 2378 
gnucash_4.10-2.dsc
 b21e2f4997240f2df9efb3b3f14d1d6efcbc31b01c616d1df24decfb9a809650 37072 
gnucash_4.10-2.debian.tar.xz
 f03047038449ee7172b301aac2188b1e692484f3f1bc97ab10360e27dc12 24826 
gnucash_4.10-2_amd64.buildinfo
Files:
 d5f36e364662f34eb3f085f7e5fbf85e 2378 gnome optional gnucash_4.10-2.dsc
 b7703271060ef191c9284fc655294ce3 37072 gnome optional 
gnucash_4.10-2.debian.tar.xz
 a5c0ec3c47a98d6ab35f55930eb8f9a3 24826 gnome optional 
gnucash_4.10-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAmJKSt8ACgkQUra72VOW
jRsZBA//QxQfDSpUvRVRR0J+lt0hN9JLAS52bOL9mxa4mca/gUfg9WC4t37/R6zH
VsGK3Na3FnU+tPnA7M8lAi51DTrSryMIbdJ5e17hVDt6X4qb9G1RddFjdmQt5qeJ
0/hoK+Ru4QY8q/5eGTRHOkxn7idlGbxJVfMF9dYAB6k5gsI+3MvWYNUNfNPRsJXr
/IMbqwgDMId7cg3yqt0LwuaX7WuwO/zxfSGZLSiQLAYFh+11NWTwxUFnu9g1lNnp
gTe9taQYk7qvZ+pbuc8g8ZAcsqYKavmdMBx9jI62VxW9XtDnNl37bM6LpsqMtjbQ
I1bzkWYEjxlBUmFJNzJi7nnoq2djJjb/VRMgRjyX+xeLroYP2PGICzQg7ajijgsh
5bEqYxUrJ1W4yycTpW8fSRUKt9+BMWYOOZmR1MRFA+a0lZS7l1Cl4rH924bktruS
kYLDdU3VIJ4Z8H3vacn++ypzoJ96DiN4diCFO1yuefBrvvWfN+r2hCUp1YR/y7zX
u/xyFqXOhygYCUUY6oWd8tqEGP2JgxlCxjLKI1a9vpleUGYZL4MBSkrRgedTwyLW
E0hEwvJT7QFis5g2Sd0RJ2IE5i+maCjEtDrq/FEv2J+uewjO6tF7nEax/y00FOKP
+95JeCp9Lz2/l96XkBnMWM5laqK5wJ0+dlO0h7YsLBOXzXBHezg=
=7gb2
-END PGP SIGNATURE End Message ---

Bug#1008817: libphonenumber8:amd64 8.12.46-2 fixed evolution

[Vincent Batts]

Tony, thanks. I must have caught it in a mid-state. It does build
through for me now. (previously it failed on email-engine)

vb

On Sun, 2022-04-03 at 17:58 -0700, tony mancill wrote:
> On Sun, Apr 03, 2022 at 07:52:45PM -0400, Vincent Batts wrote:
> > Today's build of libphonenumber8:amd64 8.12.46-2 fixed the
> > undefined
> > symbol for evolution.
> > 
> > Separate issue: evolution still fails to build from scratch (FTBFS)
> 
> Hi Vincent,
> 
> evolution builds successfully for me using sbuild in a clean sid
> chroot.
> I just built it again to be sure that it's pulling the package from
> the
> repository.
> 
> What build failure are you seeing?
> 
> Cheers,
> tony
> 
> +
> --+
> > Summary
> >   |
> +
> --+
> 
> Build Architecture: amd64
> Build Type: full
> Build-Space: 867692
> Build-Time: 343
> Distribution: unstable
> Host Architecture: amd64
> Install-Time: 43
> Job: /data/debian/sponsor/evolution/build-area/evolution_3.44.0-2.dsc
> Machine Architecture: amd64
> Package: evolution
> Package-Time: 389
> Source-Version: 3.44.0-2
> Space: 867692
> Status: successful
> Version: 3.44.0-2
> -
> ---
> Finished at 2022-04-04T00:55:58Z
> Build needed 00:06:29, 867692k disk space
> 
> 

Processed: Bug#994619 marked as pending in xpra

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #994619 [xpra] xpra: recommends gir1.2-appindicator3-0.1 which is no longer 
available
Added tag(s) pending.

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

Bug#994619: marked as pending in xpra

[Dmitry Smirnov]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/xpra/-/commit/9192807bdd034ab2c78369351ae9c13183ea256d


Removed obsolete "gir1.2-appindicator3-0.1" from Recommends (Closes: #994619)

 Thanks, Stephen Kitt, Vincent Lefevre.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/994619

Processed: Bug#1008801 marked as pending in gnucash

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1008801 [src:gnucash] gnucash: FTBFS on armhf when built on 64bit hardware
Added tag(s) pending.

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

Bug#1008801: marked as pending in gnucash

[Dmitry Smirnov]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/gnucash/-/commit/ca99eb18f7c96f6634bde039263a164da34f268b


New upstream patch to fix test failure on armhf (Closes: #1008801)

Thanks, Adrian Bunk, John Ralls.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1008801

Bug#1008817: libphonenumber8:amd64 8.12.46-2 fixed evolution

[tony mancill]

On Sun, Apr 03, 2022 at 07:52:45PM -0400, Vincent Batts wrote:
> Today's build of libphonenumber8:amd64 8.12.46-2 fixed the undefined
> symbol for evolution.
> 
> Separate issue: evolution still fails to build from scratch (FTBFS)

Hi Vincent,

evolution builds successfully for me using sbuild in a clean sid chroot.
I just built it again to be sure that it's pulling the package from the
repository.

What build failure are you seeing?

Cheers,
tony

+--+
| Summary  |
+--+

Build Architecture: amd64
Build Type: full
Build-Space: 867692
Build-Time: 343
Distribution: unstable
Host Architecture: amd64
Install-Time: 43
Job: /data/debian/sponsor/evolution/build-area/evolution_3.44.0-2.dsc
Machine Architecture: amd64
Package: evolution
Package-Time: 389
Source-Version: 3.44.0-2
Space: 867692
Status: successful
Version: 3.44.0-2

Finished at 2022-04-04T00:55:58Z
Build needed 00:06:29, 867692k disk space




signature.asc
Description: PGP signature

Bug#1008680: marked as done (scipy: FTBFS with Python 3.10 as default)

[Debian Bug Tracking System]

Your message dated Mon, 04 Apr 2022 00:49:24 +
with message-id 
and subject line Bug#1008680: fixed in pydata-sphinx-theme 0.7.2-2
has caused the Debian Bug report #1008680,
regarding scipy: FTBFS with Python 3.10 as default
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.)


-- 
1008680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scipy
Version: 1.7.3-2
Severity: serious
Tags: ftbfs patch
User: debian-pyt...@lists.debian.org
Usertags: python3.10

Hi Maintainer

As can be seen on reproducible builds [1], scipy FTBFS with Python
3.10 as the default version.  I've copied what I hope is the relevant
part of the log below.

I've also attached a patch against scipy 1.8.0-1exp2 that works for me.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/scipy.html


LANG=C python3 -msphinx -b html -d build/doctrees   source build/html
Running Sphinx v4.3.2

Exception occurred:
  File "/usr/lib/python3.10/distutils/__init__.py", line 19, in 
warnings.warn(_DEPRECATION_MESSAGE,
DeprecationWarning: The distutils package is deprecated and slated for
removal in Python 3.12. Use setuptools or check PEP 632 for potential
alternatives
The full traceback has been saved in /tmp/sphinx-err-9djw0js6.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!
SciPy (VERSION 1.7.3)
make[2]: *** [Makefile:122: html-build] Error 2
Description: Ignore distutils deprecation warnings in doc build
Author: Graham Inggs 
Last-Update: 2022-03-30

--- a/doc/source/conf.py
+++ b/doc/source/conf.py
@@ -149,6 +149,7 @@
 r"OpenSSL\.rand is deprecated",  # OpenSSL package in linkcheck
 r"Using or importing the ABCs from",  # 3.5 importlib._bootstrap
 r"'contextfunction' is renamed to 'pass_context'",  # Jinja
+r"distutils package is deprecated",
 ):
 warnings.filterwarnings(  # deal with other modules having bad imports
 'ignore', message=".*" + key, category=DeprecationWarning)
--- End Message ---
--- Begin Message ---
Source: pydata-sphinx-theme
Source-Version: 0.7.2-2
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated pydata-sphinx-theme 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Apr 2022 02:18:28 +0200
Source: pydata-sphinx-theme
Architecture: source
Version: 0.7.2-2
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Drew Parsons 
Closes: 1008680
Changes:
 pydata-sphinx-theme (0.7.2-2) unstable; urgency=medium
 .
   * Team upload.
   * debian patch distutils_deprecated_PR590.patch adapts upstream
 PR#590 to replace deprecated distutils, otherwise the
 DeprecationWarning with python3.10 causes an error in sphinx.
 Depends: python3-packaging.  Closes: #1008680.
   * Standards-Version: 4.6.0
Checksums-Sha1:
 42f1db6f7623f014d9b39cd6a1ceb4eff473033a 2373 pydata-sphinx-theme_0.7.2-2.dsc
 d06d00c50ad1eeb925c6c53706c59ae1e235a7aa 34940 
pydata-sphinx-theme_0.7.2-2.debian.tar.xz
Checksums-Sha256:
 2e1974148fbec67ff3b98773019145077b40916a5d41652a2ee4f99493b5119e 2373 
pydata-sphinx-theme_0.7.2-2.dsc
 9ed9ecc9696c19d075e7b6d0d02ea329fa2ff9a802f1f9c2adbffbc7186dd738 34940 
pydata-sphinx-theme_0.7.2-2.debian.tar.xz
Files:
 4cf6bbad2c2ac4d4746f50e9f0c6f088 2373 python optional 
pydata-sphinx-theme_0.7.2-2.dsc
 b2d68ca344b0fccb8bf6cd3ba5c8ce07 34940 python optional 
pydata-sphinx-theme_0.7.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmJKOxYACgkQVz7x5L1a
AfrRJg//RlAzIWoR6GqDegZLVZHrhRNtl6weezErf3cHoVQSQ0swoMilU7T/PFH+
Fa1nU0S/J6xx9I8g105EHdAFiT4NBz83mHkYg7ETNVTAu85b6cm61XW0zQu8M5Wn
vDC/g3fD4hL8UnXQ3RUtqdHg9Xl

Bug#1008680: marked as pending in pydata-sphinx-theme

[Drew Parsons]

Control: tag -1 pending

Hello,

Bug #1008680 in pydata-sphinx-theme 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/pydata-sphinx-theme/-/commit/b2b587a0f5db45f88e53366f345efd1a473c939a


add debian patch distutils_deprecated_PR590.patch

adapts upstream PR#590 to replace deprecated distutils

otherwise the DeprecationWarning with python3.10 causes an error in
sphinx (causing the scipy doc build to fail)

Depends: python3-packaging.

Closes: #1008680.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1008680

Processed: Bug#1008680 marked as pending in pydata-sphinx-theme

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1008680 [python3-pydata-sphinx-theme] scipy: FTBFS with Python 3.10 as 
default
Added tag(s) pending.

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

Bug#1008680: scipy: FTBFS with Python 3.10 as default

[Drew Parsons]

Source: scipy
Followup-For: Bug #1008680

The error on distutils is clouding the issue. 

distutils is deprecated, packages need to update their code. scipy and
sphinx are both aware about it and are dealing with it.

But scipy uses distutils in its own build, and the deprecation warning
is not triggering error there.

sphinx does not usually treat a warning as an error, and the -W flag
has not been invoked here.

The problem is in the fine print.  The sphinx error refers to a log
file.  Reading the log points the finger at pydata_sphinx_theme:

  File "/usr/lib/python3/dist-packages/pydata_sphinx_theme/__init__.py", line 
14, in 
from .bootstrap_html_translator import BootstrapHTML5Translator
  File 
"/usr/lib/python3/dist-packages/pydata_sphinx_theme/bootstrap_html_translator.py",
 line 3, in 
from distutils.version import LooseVersion
  File "/usr/lib/python3.10/distutils/__init__.py", line 19, in 
warnings.warn(_DEPRECATION_MESSAGE,
DeprecationWarning: The distutils package is deprecated and slated for removal 
in Python 3.12. Use setuptools or check PEP 632 for potential alternatives


So even though sphinx is not supposed to treat warnings as errors,
apparently this is happening with sphinx themes, or at least with
pydata_sphinx_theme.

The solution is either to instruct scipy to not use
pydata_sphinx_theme for its docs, or patch pydata_sphinx_theme. The
first might cause a growing snowball of problems depending on how
scipy is using the pydata theme.

pydata_sphinx_theme has a simple patch already at
https://github.com/pydata/pydata-sphinx-theme/pull/590
Probably this is the best solution.

Bug#1008817: libphonenumber8:amd64 8.12.46-2 fixed evolution

[Vincent Batts]

Today's build of libphonenumber8:amd64 8.12.46-2 fixed the undefined
symbol for evolution. 


Separate issue: evolution still fails to build from scratch (FTBFS)


signature.asc
Description: PGP signature

Processed: scipy docs

[Debian Bug Tracking System]

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

> reassign 1008680 python3-pydata-sphinx-theme
Bug #1008680 [src:scipy] scipy: FTBFS with Python 3.10 as default
Bug reassigned from package 'src:scipy' to 'python3-pydata-sphinx-theme'.
No longer marked as found in versions scipy/1.7.3-2.
Ignoring request to alter fixed versions of bug #1008680 to the same values 
previously set
> affects 1008680 src:scipy
Bug #1008680 [python3-pydata-sphinx-theme] scipy: FTBFS with Python 3.10 as 
default
Added indication that 1008680 affects src:scipy
> thanks
Stopping processing here.

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

Bug#1008680: scipy: FTBFS with Python 3.10 as default

[Drew Parsons]

Source: scipy
Followup-For: Bug #1008680

It's in the doc build, the error message refers to sphinx.
Is the bug in sphinx, not in scipy?

Bug#1008680: scipy: FTBFS with Python 3.10 as default

[Drew Parsons]

Source: scipy
Followup-For: Bug #1008680

Yes, looks to me the problem is the one discussed at
https://github.com/sphinx-doc/sphinx/issues/9595
https://github.com/sphinx-doc/sphinx/issues/9820

Bug#994619: xpra: recommends gir1.2-appindicator3-0.1 which is no longer available

[Vincent Lefevre]

On 2022-03-11 03:24:25 +0100, Vincent Lefevre wrote:
> On 2021-09-18 19:08:35 +0200, Stephen Kitt wrote:
> > xpra recommends gir1.2-appindicator3-0.1 but the latter is no longer
> > available.
> 
> Raising the severity, because this now blocks the upgrade of
> libayatana-appindicator3-1 with aptitude in an obscure way
> (it took me some time to find that xpra was the culprit).
> 
> Basically, libayatana-appindicator3-1 0.5.90-6 now breaks
> libappindicator3-1, and gir1.2-appindicator3-0.1 depends on
> this package.

This was actually an error in libayatana-appindicator3-1 0.5.90-6;
the upgrade to the new libayatana-appindicator3-1 0.5.90-8 version
is fine (libayatana-appindicator3-1 now provides libappindicator3-1).

But anyway, this Recommends may still be an issue for future upgrades
if it is not removed, because it would be unsatisfied.

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

Bug#1008680: scipy: FTBFS with Python 3.10 as default

[Drew Parsons]

Source: scipy
Version: 1.7.3-2
Followup-For: Bug #1008680

However, likely addressed by scipy upstream at
https://github.com/scipy/scipy/commit/60d5ee3955bd3ff5982a08e8d64ec8b5f5f62dc9

Bug#1008739: python-pyaudio: diff for NMU version 0.2.11-1.4

[Stefano Rivera]

Control: tags 1008739 + pending

Dear maintainer,

I've forwarded the patch upstream, and I've prepared an NMU for
python-pyaudio (versioned as 0.2.11-1.4) and uploaded it to DELAYED/5.
Please feel free to tell me if I should delay it longer.

Regards,

SR
diff -Nru python-pyaudio-0.2.11/debian/changelog python-pyaudio-0.2.11/debian/changelog
--- python-pyaudio-0.2.11/debian/changelog	2020-10-29 12:05:20.0 -0400
+++ python-pyaudio-0.2.11/debian/changelog	2022-04-03 18:12:25.0 -0400
@@ -1,3 +1,10 @@
+python-pyaudio (0.2.11-1.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Python 3.10 support. (Closes: #1008739)
+
+ -- Stefano Rivera   Sun, 03 Apr 2022 18:12:25 -0400
+
 python-pyaudio (0.2.11-1.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru python-pyaudio-0.2.11/debian/patches/python3.10.patch python-pyaudio-0.2.11/debian/patches/python3.10.patch
--- python-pyaudio-0.2.11/debian/patches/python3.10.patch	1969-12-31 20:00:00.0 -0400
+++ python-pyaudio-0.2.11/debian/patches/python3.10.patch	2022-04-03 18:12:24.0 -0400
@@ -0,0 +1,19 @@
+Description: Adjust Makefile for Python 3.10
+ import get_platform() from sysconfig instead of distutils
+ support Python with 2-digit minor version
+Author: Graham Inggs 
+Last-Update: 2022-03-31
+Bug-Debian: https://bugs.debian.org/1008739
+Forwarded: by email, 2022-04-03
+
+--- a/Makefile
 b/Makefile
+@@ -7,7 +7,7 @@
+ BUILD_ARGS ?=
+ SPHINX ?= sphinx-build
+ DOCS_OUTPUT=docs/
+-PYTHON_BUILD_DIR:=$(shell $(PYTHON) -c "import distutils.util; import sys; print(distutils.util.get_platform() + '-' + sys.version[0:3])")
++PYTHON_BUILD_DIR:=$(shell $(PYTHON) -c "import sysconfig; import sys; print(sysconfig.get_platform() + '-' + ('%d.%d' % sys.version_info[:2]))")
+ BUILD_DIR:=lib.$(PYTHON_BUILD_DIR)
+ BUILD_STAMP:=$(BUILD_DIR)/build
+ SRCFILES := src/*.c src/*.h src/*.py
diff -Nru python-pyaudio-0.2.11/debian/patches/series python-pyaudio-0.2.11/debian/patches/series
--- python-pyaudio-0.2.11/debian/patches/series	2020-10-21 16:53:42.0 -0400
+++ python-pyaudio-0.2.11/debian/patches/series	2022-04-03 17:53:21.0 -0400
@@ -1 +1,2 @@
 Use-Python3-in-Makefile.patch
+python3.10.patch

Processed: python-pyaudio: diff for NMU version 0.2.11-1.4

[Debian Bug Tracking System]

Processing control commands:

> tags 1008739 + pending
Bug #1008739 [src:python-pyaudio] python-pyaudio: FTBFS with Python 3.10 as 
default
Added tag(s) pending.

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

Bug#965459: marked as done (coinor-ipopt: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Sun, 03 Apr 2022 21:48:45 +
with message-id 
and subject line Bug#965459: fixed in coinor-ipopt 3.11.9-2.3
has caused the Debian Bug report #965459,
regarding coinor-ipopt: Removal of obsolete debhelper compat 5 and 6 in bookworm
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.)


-- 
965459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: coinor-ipopt
Version: 3.11.9-2.2
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package coinor-ipopt uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: coinor-ipopt
Source-Version: 3.11.9-2.3
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated coinor-ipopt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 17 Mar 2022 23:41:30 +0200
Source: coinor-ipopt
Architecture: source
Version: 3.11.9-2.3
Distribution: unstable
Urgency: low
Maintainer: Greg Horn 
Changed-By: Adrian Bunk 
Closes: 965459
Changes:
 coinor-ipopt (3.11.9-2.3) unstable; urgency=low
 .
   * Non-maintainer upload.
   * debian/compat: 5 -> 7. (Closes: #965459)
Checksums-Sha1:
 0dfc420274eb4d6bfd97c1a32ef3a6ddd0e03e61 2249 coinor-ipopt_3.11.9-2.3.dsc
 2206438bfc0679f797c45eb0944d412809b7654a 10480 
coinor-ipopt_3.11.9-2.3.debian.tar.xz
Checksums-Sha256:
 320faecba422c49dfbc86d1bbd9118377365ef443dae1ad77ba94d95768aa77e 2249 
coinor-ipopt_3.11.9-2.3.dsc
 ffbb7a4b2295af0d183f31d440483118b7a49871df9626cd3b12f29aca445b6b 10480 
coinor-ipopt_3.11.9-2.3.debian.tar.xz
Files:
 14ebb478d179f4b15b0dfa496968dfad 2249 science optional 
coinor-ipopt_3.11.9-2.3.dsc
 d88b39efec593f27b1fb2573bd3acf94 10480 science optional 
coinor-ipopt_3.11.9-2.3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmIzrbsACgkQiNJCh6LY
mLF8ixAAjOofL5p+YcgEBmkmf+WTzCBet3FmCP3dHnhOqh8tEjzKjQUC5P+Djcga
GnROQYKq1gFHcmBQoVPbGcAj48RnwOH7cq/qbdGy4moRZ61zpLUh3NkP2smYuiYn
D198v6qAglQeQJWGUUzCzmYDOyXehMqB6KqqtUPFKXys+sLSUw69V8WmOcrDikDg
9mSnXaSE/zUN0p/y1CUGZB0Qc1z5K9/GQEvj6AXgcJxptTVTVXJMHjEN69FZX7D7
uR3sNhEYh5MnPABT1D5+Id3YkRYDaDLZq6lXgHzHZOXqBAf7/FFp0UeeJY5GHNFT
BnZUb819sbYnItMMI05Eg6mnFx7ztJiE4p1x4XyOCj4PN229PtoGUYOXrmjLfzMz
F1tCZ8MfO0N2c/ltbU/ygDxRVOT7TAesF2FCX3ibCNtFVF0PM9gRXgQeiJz77I5v
EIQ8aqNOCPLcHz56hnJcCUkE3ZrFNvV6+ZHbXGfnKVoHvRsTzDBMlJ3HBUjfzajS
uFQu461R/5pRcmKH3NB2LU1/CGVyh5EAy0ufu8twTboyaHrUUJkIK2kdlyYZWc3W
4Y0rJx+kUVVFHMF+4wIIqfsmF0I3iHlrN7AxJdLM9ZZwk8+muwC9g6QPA6rvkvjg
Pq8XLh67dUa0k0WmxrSn2QvTUn2cW7OBwn6kUJyCiU8hRHf5nQ4=
=pNtT
-END PGP SIGNATURE End Message ---

Bug#1008810: thrift: FTBFS with Python 3.10

[stefanor]

Hi László (2022.04.03_06:25:52_+)
>  With all due respect, it's a Golang FTBFS and not a Python one.

Thanks. I think there is a Python 3.10 issue entangled in here, but it's
fixed in 0.16.0:

https://github.com/apache/thrift/commit/b724787d373de99feeab0eb2e052f8c8d3ed

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1007789 src:golang-github-matryer-try
Bug #1007789 [golang-github-matryer-try] golang-github-matryer-try: FTBFS with 
Go 1.18
Bug reassigned from package 'golang-github-matryer-try' to 
'src:golang-github-matryer-try'.
Ignoring request to alter found versions of bug #1007789 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1007789 to the same values 
previously set
> tags 1008418 patch
Bug #1008418 [src:golang-github-matryer-try] golang-github-matryer-try: FTBFS: 
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
github.com/matryer/try returned exit code 2
Added tag(s) patch.
> forcemerge 1008418 1007789
Bug #1008418 [src:golang-github-matryer-try] golang-github-matryer-try: FTBFS: 
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
github.com/matryer/try returned exit code 2
Bug #1007789 [src:golang-github-matryer-try] golang-github-matryer-try: FTBFS 
with Go 1.18
Severity set to 'serious' from 'normal'
Marked as found in versions 
golang-github-matryer-try/1+git20161228.6.9ac251b-2.1.
Added tag(s) bookworm, sid, and ftbfs.
Merged 1007789 1008418
> thanks
Stopping processing here.

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

Bug#1008547: marked as done (gnome-shell-extension-freon: does not declare compatibility with GNOME Shell 42)

[Debian Bug Tracking System]

Your message dated Sun, 03 Apr 2022 20:39:52 +
with message-id 
and subject line Bug#1008547: fixed in gnome-shell-extension-freon 45+dfsg-3
has caused the Debian Bug report #1008547,
regarding gnome-shell-extension-freon: does not declare compatibility with 
GNOME Shell 42
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.)


-- 
1008547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-freon
Version: 45+dfsg-1
Severity: normal
Tags: bookworm sid fixed-upstream
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-42

The metadata.json for this extension doesn't declare compatibility with
GNOME 42. This seems to have been fixed in upstream git (not tested).

gnome-shell 42 is in experimental and will be entering unstable soon,
at which point this will become a RC bug.

To keep better track of which extensions have and haven't been updated for
each new GNOME version, it would be useful if this extension had a
dependency of the form

gnome-shell (>= x), gnome-shell (<< y)

where x is the oldest version in metadata.json, and y is the next major
version after the newest version in metadata.json (at the moment y = 43).
See g-s-e-caffeine for an example of this setup.

During the GNOME Shell 42 transition, this extension will be removed from
testing if it continues to be incompatible.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-freon
Source-Version: 45+dfsg-3
Done: Matteo F. Vescovi 

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

Debian distribution maintenance software
pp.
Matteo F. Vescovi  (supplier of updated 
gnome-shell-extension-freon 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, 03 Apr 2022 21:54:27 +0200
Source: gnome-shell-extension-freon
Architecture: source
Version: 45+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Matteo F. Vescovi 
Closes: 1008547
Changes:
 gnome-shell-extension-freon (45+dfsg-3) unstable; urgency=medium
 .
   * debian/control: limit gnome-shell version (Closes: #1008547)
Checksums-Sha1:
 c4fa50df74c84ea801cca26777d6c875d09b2773 2367 
gnome-shell-extension-freon_45+dfsg-3.dsc
 5af1a338966ba3dd50beb8aeb6453aa195a7 4504 
gnome-shell-extension-freon_45+dfsg-3.debian.tar.xz
 6530db8570c2d043a0f7f63ea9adf15409879403 6228 
gnome-shell-extension-freon_45+dfsg-3_source.buildinfo
Checksums-Sha256:
 9f9f78ef537d99a63a5835189fea65c0c3c2897bf806a2986d995d3bfda7d6ca 2367 
gnome-shell-extension-freon_45+dfsg-3.dsc
 7f0aed9c730c2d56772e4ce02bc716dbe2a9318fbd3da8bc64c286ffc4c662d5 4504 
gnome-shell-extension-freon_45+dfsg-3.debian.tar.xz
 87a2e41b3a7adba023983ba77cc0f51296d650182674cdf65abba12dae843713 6228 
gnome-shell-extension-freon_45+dfsg-3_source.buildinfo
Files:
 a2e2c63e13bca31922d2347fa7c64bbb 2367 gnome optional 
gnome-shell-extension-freon_45+dfsg-3.dsc
 987767d80a03429efab6a8d6b641a7b6 4504 gnome optional 
gnome-shell-extension-freon_45+dfsg-3.debian.tar.xz
 44a2c8c1432e3454ed528bbde99c5d7d 6228 gnome optional 
gnome-shell-extension-freon_45+dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Debian powered!

iQKTBAEBCgB9FiEE890J+NqH0d9QRsmbBhL0lE7NzVoFAmJJ+4tfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYz
REQwOUY4REE4N0QxREY1MDQ2Qzk5QjA2MTJGNDk0NEVDRENENUEACgkQBhL0lE7N
zVoxfw/+IhrNZxeF85Ct6BWGYtFcwPChareqrJUPcFFm4EcRZ3QHedE/13x3WDx+
DNaqlaGSRewZ0ZQgkvoJV6QFYhY/g24TQKwCXdS5yrm7ekGBT5EEeT8MOUdcMZ/2
OaItexDB66VvvEZw15rDTh22VrBBgMS6mJkeKzqnKOQA+D71xCmtH0yAbXHUk5cp
Y41A/4c2gFlCrEmdBk+CfwHYwBwEj3aRc3ykHNWxuXwqdGxiSuJok6SlgNzp0MJA
2ZYBKgh+KUVlej7QixCLf3kZKeS3t+dZhUHxGj7EBXzNQxGaVWqjKDrWWKJrRCCm
1N4tdYFe8CIMyZQeEjUGredmOVdHRFUaKGMQMUW5rrMqTNEkrs1l4aTJCwXRMNR0
B/D4HDpuE48AlO25n/mRrX04Fy0EQPMHNOg3IwARfHJmJkMYPzXIKw8TOUnUoxJk
MG+qI6CoW5D1OK+IUJrRjrAMRYkumoj5qlvzXGgFAXaT/fj5fMX+gf0quCyxNT2P
xCBm2vsm6qh7CDGZshC2JRc6Sz03

Bug#1008561: marked as done (gnome-shell-extension-volume-mixer: does not declare compatibility with GNOME Shell 42)

[Debian Bug Tracking System]

Your message dated Sun, 03 Apr 2022 20:39:59 +
with message-id 
and subject line Bug#1008561: fixed in gnome-shell-extension-volume-mixer 
41.1+dfsg-2
has caused the Debian Bug report #1008561,
regarding gnome-shell-extension-volume-mixer: does not declare compatibility 
with GNOME Shell 42
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.)


-- 
1008561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-volume-mixer
Version: 41.1+dfsg-1
Severity: normal
Tags: bookworm sid upstream
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-42

The metadata.json for this extension doesn't declare compatibility with
GNOME 42. I don't know whether actual code changes will be necessary.

gnome-shell 42 is in experimental and will be entering unstable soon,
at which point this will become a RC bug.

During the GNOME Shell 42 transition, this extension will be removed from
testing if it continues to be incompatible.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-volume-mixer
Source-Version: 41.1+dfsg-2
Done: Matteo F. Vescovi 

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

Debian distribution maintenance software
pp.
Matteo F. Vescovi  (supplier of updated 
gnome-shell-extension-volume-mixer 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, 03 Apr 2022 22:12:42 +0200
Source: gnome-shell-extension-volume-mixer
Architecture: source
Version: 41.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Matteo F. Vescovi 
Closes: 1008561
Changes:
 gnome-shell-extension-volume-mixer (41.1+dfsg-2) unstable; urgency=medium
 .
   * debian/patches/: patchset updated
 - 0002-Extend_supported_g-s_versions.patch added (Closes: #1008561)
   * debian/control: extend maximum gnome-shell version supported
Checksums-Sha1:
 1b29b4b37654f6f037ccfcca74c8cf4c8be32f90 2457 
gnome-shell-extension-volume-mixer_41.1+dfsg-2.dsc
 4b02d1fbf0683e9af9f7e9c351332b986aad3d09 2732 
gnome-shell-extension-volume-mixer_41.1+dfsg-2.debian.tar.xz
 aa9b14a5e704973f8611cd9eab566fd3e33e0a83 6784 
gnome-shell-extension-volume-mixer_41.1+dfsg-2_source.buildinfo
Checksums-Sha256:
 74ee46acadfebdf39401917368f94df492b5aa2a47b9a367c347293eef55ee2e 2457 
gnome-shell-extension-volume-mixer_41.1+dfsg-2.dsc
 d1779182ca46376ec77bdfd6bc2a20816eacb3d195c02973114c999008922ce6 2732 
gnome-shell-extension-volume-mixer_41.1+dfsg-2.debian.tar.xz
 88b69a1514d9d8174c2b59885cbef529007838ede0aab0b3f31add08a315f9e8 6784 
gnome-shell-extension-volume-mixer_41.1+dfsg-2_source.buildinfo
Files:
 6605c5132a2399134bb05643037d0af9 2457 gnome optional 
gnome-shell-extension-volume-mixer_41.1+dfsg-2.dsc
 ad62e8b85f93b529d7ddb28477d2b00a 2732 gnome optional 
gnome-shell-extension-volume-mixer_41.1+dfsg-2.debian.tar.xz
 785114880189ad2f7fc5a5d2e44b3754 6784 gnome optional 
gnome-shell-extension-volume-mixer_41.1+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Debian powered!

iQKTBAEBCgB9FiEE890J+NqH0d9QRsmbBhL0lE7NzVoFAmJJ/8NfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYz
REQwOUY4REE4N0QxREY1MDQ2Qzk5QjA2MTJGNDk0NEVDRENENUEACgkQBhL0lE7N
zVoO2Q/9HB/5ZDoc892hO9yQA30iIrR87KoK8taCg8gkRJQ2yUTCVZengsB7m82j
bVFLstry+ZHJBzH8yE/HZcBs4E4eKTXxH/4tWoA+Wr6zmcySN3jWiKD5kRPI1Dcy
eihte+TUtQkgxt9wat5EwVHVNgHuy6yFj6GAxP9Cf0lpMaTYQ9w/UdGon8/ZJAXl
tehz/r4TOjMl4ImP0CDVY08ihFkVyEUKMvYyuBuqytKd9n6Nn/JiBlInOfNLXh8t
fZESrFQ/ga3QGTKu6yM/AVOhfeID/HZ39sQLWmERIT7/HtSI9KxPX1cCJDXIE0IJ
cXdys2X9EFZtLPC5AXTQ7AbRwlEkrfLEnbku0p7Q9fZukZuTN9I0Glws4ttDlSov
pTGFK20wAn6psrST1Udg9gw9/O5BBEME6u6WAJynfSJTJYbD1Q5leqxi1jKLvjWt
0nauUXWHcFxTrIre7cJ5YDypcwGlcpeTTqfxYkaSju/8lqEIHP778M3LYKRK9EFf
0kgbKNhGROEXPhZ8bjBeaW+fdtrvjlU+8LLDJu/pVIjpSmdhyAie56mzzOjB21X9
nm2ZKRPtncDJ2o4HE7obCnQfcT5cv3XWTPX4nhJnJlMQRxz1C1dHZqaVpGGSYKVU
9XSFGgqfKHWaubWl2JYn+Sljhq7PbdwP4UO2gBgaQHMkKgJsnb

Bug#1008745: marked as done (pybuild: Handle 2-digit minor versions in --interpreter python3.10)

[Debian Bug Tracking System]

Your message dated Sun, 03 Apr 2022 20:35:34 +
with message-id 
and subject line Bug#1008745: fixed in dh-python 5.20220403
has caused the Debian Bug report #1008745,
regarding pybuild: Handle 2-digit minor versions in --interpreter python3.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.)


-- 
1008745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nipy
Version: 0.5.0-2
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10

Hi Maintainer

As can be seen on reproducible builds [1], nipy FTBFS with Python 3.10
as the default version.  I've copied what I hope is the relevant part
of the log below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/nipy.html


: # I: Generate documentation
PYTHONPATH=`pybuild --print build_dir --interpreter python3.10` \
  http_proxy='127.0.0.1:9' \
  PATH=/build/1st/nipy-0.5.0/debian/tmp/usr/bin/:$PATH \
  HOME=/build/1st/nipy-0.5.0/build \
  /usr/bin/make -C doc html PYTHON=python3.10
E: pybuild pybuild:143: interpreter python3.10 not supported by
BuildSystem(distutils)
make[2]: Entering directory '/build/1st/nipy-0.5.0/doc'
python3.10 ../tools/build_modref_templates.py
Traceback (most recent call last):
  File "/build/1st/nipy-0.5.0/doc/../tools/build_modref_templates.py",
line 18, in 
docwriter = ApiDocWriter(package)
  File "/build/1st/nipy-0.5.0/tools/apigen.py", line 73, in __init__
self.package_name = package_name
  File "/build/1st/nipy-0.5.0/tools/apigen.py", line 95, in set_package_name
self.root_module = __import__(package_name)
ModuleNotFoundError: No module named 'nipy'
make[2]: *** [Makefile:62: api] Error 1
--- End Message ---
--- Begin Message ---
Source: dh-python
Source-Version: 5.20220403
Done: Stefano Rivera 

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated dh-python 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, 03 Apr 2022 15:45:19 -0400
Source: dh-python
Architecture: source
Version: 5.20220403
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski 
Changed-By: Stefano Rivera 
Closes: 1008745
Changes:
 dh-python (5.20220403) unstable; urgency=medium
 .
   * Refresh pydist.
   * Replace which with command -v in autoscripts, thanks Diederik de Haas.
   * Add support for --test-custom/PYBUILD_TEST_CUSTOM. Thanks, Antonio
 Terceiro!
   * Correctly handle --interpreter python3.10 (2-digit minor version).
 (closes: 1008745)
Checksums-Sha1:
 6053759a0b871526b895027f2efaa923d65d46e2 1552 dh-python_5.20220403.dsc
 c4922a3d805a43ecce390e675601696903706fe8 116236 dh-python_5.20220403.tar.xz
 1cb45012763067e39b10eb4ab69f7ee3af58e771 6464 
dh-python_5.20220403_source.buildinfo
Checksums-Sha256:
 bca907667cef09348712cba17eabc71064024fab122b89386ff5b503d41f553c 1552 
dh-python_5.20220403.dsc
 bce2822710a3aa42c016d14c6815df6d9b6b24f5b66bf1ad9c70b47c211eee6a 116236 
dh-python_5.20220403.tar.xz
 60a6c19a15b73133e119b37533b0e81407f8e2195ee0f92c9d0398246ee9f618 6464 
dh-python_5.20220403_source.buildinfo
Files:
 7060e40fb161e3ca3deb7cd5541ef507 1552 python optional dh-python_5.20220403.dsc
 85ef9038cc9070c3e549d15df914c8bc 116236 python optional 
dh-python_5.20220403.tar.xz
 5917d1ddb1e5785a94d42194d014aaeb 6464 python optional 
dh-python_5.20220403_source.buildinfo

-BEGIN PGP SIGNATURE-

iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYkn5bBQcc3RlZmFub3JA
ZGViaWFuLm9yZwAKCRBHew2wJjpU2Nf4APsFIUd6BDI5knhByeeuX++NLA9CH0HZ
VCY+i+WXLVjj4gEAvJmjMhfTM9t3/HYX+1ImjuM0PkarI08hFigM4OEnQwE=
=jnmw
-END PGP SIGNATURE End Message ---

Processed: merging 1008908 1008905 1008902 1008903 1008906

[Debian Bug Tracking System]

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

> merge 1008908 1008905 1008902 1008903 1008906
Bug #1008908 [node-p-locate] node-p-locate: please export as commonjs module
Bug #1008905 [node-p-locate] node-rollup-plugin-terser: autopkgtest regression 
in testing
Marked as found in versions node-p-locate/6.0.0-8.
Bug #1008902 [node-p-locate] node-puppeteer: autopkgtest regression in testing
Marked as found in versions node-p-locate/6.0.0-8.
Bug #1008903 [node-p-locate] node-make-error: autopkgtest regression in testing
Marked as found in versions node-p-locate/6.0.0-8.
Bug #1008906 [node-p-locate] node-keygrip: autopkgtest regression in testing
Marked as found in versions node-p-locate/6.0.0-8.
Merged 1008902 1008903 1008905 1008906 1008908
> thanks
Stopping processing here.

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

Processed: reassign 1008905 to node-p-locate, reassign 1008902 to node-p-locate ...

[Debian Bug Tracking System]

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

> reassign 1008905 node-p-locate
Bug #1008905 [src:node-rollup-plugin-terser] node-rollup-plugin-terser: 
autopkgtest regression in testing
Bug reassigned from package 'src:node-rollup-plugin-terser' to 'node-p-locate'.
No longer marked as found in versions node-rollup-plugin-terser/7.0.2+~5.0.1-2.
Ignoring request to alter fixed versions of bug #1008905 to the same values 
previously set
> reassign 1008902 node-p-locate
Bug #1008902 [src:node-puppeteer] node-puppeteer: autopkgtest regression in 
testing
Bug reassigned from package 'src:node-puppeteer' to 'node-p-locate'.
No longer marked as found in versions node-puppeteer/13.4.1+dfsg-1.
Ignoring request to alter fixed versions of bug #1008902 to the same values 
previously set
> reassign 1008903 node-p-locate
Bug #1008903 [src:node-make-error] node-make-error: autopkgtest regression in 
testing
Bug reassigned from package 'src:node-make-error' to 'node-p-locate'.
No longer marked as found in versions node-make-error/1.3.7-2.
Ignoring request to alter fixed versions of bug #1008903 to the same values 
previously set
> reassign 1008906 node-p-locate
Bug #1008906 [src:node-keygrip] node-keygrip: autopkgtest regression in testing
Bug reassigned from package 'src:node-keygrip' to 'node-p-locate'.
No longer marked as found in versions node-keygrip/1.1.0-2.
Ignoring request to alter fixed versions of bug #1008906 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1008908: node-p-locate: please export as commonjs module

[Jérémy Lal]

Package: node-p-locate
Version: 6.0.0-8
Severity: serious
Justification: autopkgtest regressions

Hi,

this is the cause of several regressions.


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

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

Versions of packages node-p-locate depends on:
ii  node-p-limit  4.0.0+~cs4.0.0-3

node-p-locate recommends no packages.

node-p-locate suggests no packages.

-- no debconf information

Bug#1008907: backtrace

[Gert van de Kraats]

Reading symbols from /usr/bin/pipewire...
(No debugging symbols found in /usr/bin/pipewire)

warning: Can't open file /memfd:pipewire-memfd (deleted) during 
file-backed mapping note processing

[New LWP 1511]
[New LWP 1515]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/pipewire'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0xb59e85da in ?? () from 
/usr/lib/i386-linux-gnu/spa-0.2/alsa/libspa-alsa.so

[Current thread is 1 (Thread 0xb7bf9700 (LWP 1511))]
(gdb) bt
#0  0xb59e85da in ?? () from 
/usr/lib/i386-linux-gnu/spa-0.2/alsa/libspa-alsa.so
#1  0xb59f0637 in ?? () from 
/usr/lib/i386-linux-gnu/spa-0.2/alsa/libspa-alsa.so
#2  0xb59d9cf1 in ?? () from 
/usr/lib/i386-linux-gnu/spa-0.2/alsa/libspa-alsa.so
#3  0xb4f3d125 in ?? () from 
/usr/lib/i386-linux-gnu/spa-0.2/audioconvert/libspa-audioconvert.so
#4  0xb4f3f5e8 in ?? () from 
/usr/lib/i386-linux-gnu/spa-0.2/audioconvert/libspa-audioconvert.so
#5  0xb7e69285 in pw_impl_node_for_each_param () from 
/lib/i386-linux-gnu/libpipewire-0.3.so.0

#6  0xb7e69976 in ?? () from /lib/i386-linux-gnu/libpipewire-0.3.so.0
#7  0xb736d9f8 in ?? () from 
/usr/lib/i386-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so
#8  0xb7369019 in ?? () from 
/usr/lib/i386-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so
#9  0xb7369227 in ?? () from 
/usr/lib/i386-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so
#10 0xb77648a5 in ?? () from 
/usr/lib/i386-linux-gnu/spa-0.2/support/libspa-support.so
#11 0xb7766c36 in ?? () from 
/usr/lib/i386-linux-gnu/spa-0.2/support/libspa-support.so
#12 0xb7e5dbaa in pw_main_loop_run () from 
/lib/i386-linux-gnu/libpipewire-0.3.so.0

#13 0x004164b1 in ?? ()
#14 0xb7c1c905 in __libc_start_main (main=0x4161c0, argc=1, 
argv=0xbfa91a04, init=0x4167c0, fini=0x416820,
    rtld_fini=0xb7f0f480 <_dl_fini>, stack_end=0xbfa919fc) at 
../csu/libc-start.c:332

#15 0x00416691 in ?? ()

Processed: plplot: diff for NMU version 5.15.0+dfsg-24.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1008470 + patch
Bug #1008470 [libplplot-dev] libplplot-dev: Uninstallable since libltdl-dev 
stopped providing libltdl3-dev with its 2.4.7-2 upload
Added tag(s) patch.
> tags 1008470 + pending
Bug #1008470 [libplplot-dev] libplplot-dev: Uninstallable since libltdl-dev 
stopped providing libltdl3-dev with its 2.4.7-2 upload
Added tag(s) pending.

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

Bug#1008470: plplot: diff for NMU version 5.15.0+dfsg-24.1

[Sebastian Ramacher]

Control: tags 1008470 + patch
Control: tags 1008470 + pending

Dear maintainer,

as this issue blocks the python3.10-default transition, I've prepared an
NMU for plplot (versioned as 5.15.0+dfsg-24.1) and uploaded it to
DELAYED/2. Please feel free to tell me if I should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru plplot-5.15.0+dfsg/debian/changelog plplot-5.15.0+dfsg/debian/changelog
--- plplot-5.15.0+dfsg/debian/changelog	2021-11-16 08:24:57.0 +0100
+++ plplot-5.15.0+dfsg/debian/changelog	2022-04-03 21:49:36.0 +0200
@@ -1,3 +1,10 @@
+plplot (5.15.0+dfsg-24.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Switch libltdl3-dev to libltdl-dev. (Closes: #1008470)
+
+ -- Sebastian Ramacher   Sun, 03 Apr 2022 21:49:36 +0200
+
 plplot (5.15.0+dfsg-24) unstable; urgency=medium
 
   * d/t/control: Make the unit test plplot-test depend on ccache
diff -Nru plplot-5.15.0+dfsg/debian/control plplot-5.15.0+dfsg/debian/control
--- plplot-5.15.0+dfsg/debian/control	2021-11-16 08:24:57.0 +0100
+++ plplot-5.15.0+dfsg/debian/control	2022-04-03 21:47:24.0 +0200
@@ -20,7 +20,7 @@
javahelper,
libgl1-mesa-dri,
libhpdf-dev,
-   libltdl3-dev,
+   libltdl-dev,
liblua5.1-0-dev,
libpango1.0-dev,
libqhull-dev (>= 2003.1-8),
@@ -74,7 +74,7 @@
 pkg-config
 Suggests: plplot-doc, plplot-examples
 Depends: libfreetype6-dev,
- libltdl3-dev,
+ libltdl-dev,
  libcsironn0 (= ${binary:Version}),
  libcsirocsa0 (= ${binary:Version}),
  libplplot17 (= ${binary:Version}),
@@ -512,7 +512,7 @@
 Depends: gnat,
  gnat-10,
  libfreetype6-dev,
- libltdl3-dev,
+ libltdl-dev,
  libplplot17 (= ${binary:Version}),
  libplplotada4.1 (= ${binary:Version}),
  libqhull-dev,


signature.asc
Description: PGP signature

Bug#1008907: pipewire: Pipewire.service dump at start, status=11/SEGV after upgrade 0.3.49-1

[Gert van de Kraats]

Package: pipewire
Version: 0.3.49-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

2022-04-03 13:26:47 upgrade pipewire:i386 0.3.48-1 0.3.49-1

No sound and no speaker symbol visible.

Apr 3 14:02:25 debian wireplumber[755]: Failed to set scheduler settings:
Operation not permitted
Apr 3 14:02:27 debian dbus-daemon[763]: [session uid=117 pid=763] 
Successfully

activated service 'org.gtk.vfs.Daemon'
Apr 3 14:02:27 debian systemd[672]: Started Virtual filesystem service.
Apr 3 14:02:27 debian bluetoothd[531]: Player registered: sender=:1.33
path=/media_player0
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/ldac
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSink/aptx_hd
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/aptx_hd
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSink/aptx
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/aptx
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSink/sbc
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/sbc
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSink/sbc_xq
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/sbc_xq
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/aptx_ll_1
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/aptx_ll_0
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/faststream
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/faststream_duplex
Apr 3 14:02:30 debian rtkit-daemon[785]: Supervising 5 threads of 3 
processes

of 1 users.
Apr 3 14:02:30 debian rtkit-daemon[785]: Successfully made thread 1070 of
process 753 owned by '117' RT at priority 5.
Apr 3 14:02:30 debian rtkit-daemon[785]: Supervising 6 threads of 3 
processes

of 1 users.
Apr 3 14:02:30 debian rtkit-daemon[785]: Supervising 6 threads of 3 
processes

of 1 users.
Apr 3 14:02:30 debian rtkit-daemon[785]: Successfully made thread 1071 of
process 753 owned by '117' RT at priority 5.
Apr 3 14:02:30 debian rtkit-daemon[785]: Supervising 7 threads of 3 
processes

of 1 users.
Apr 3 14:02:31 debian systemd[672]: Started Sound Service.
Apr 3 14:02:32 debian gnome-session[1046]: gnome-session-binary[1046]: GLib-
GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL'
failed
Apr 3 14:02:32 debian gnome-session[1046]: gnome-session-binary[1046]: GLib-
GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL'
failed
Apr 3 14:02:32 debian gnome-session-binary[1046]: GLib-GIO-CRITICAL:
g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Apr 3 14:02:32 debian gnome-session-binary[1046]: GLib-GIO-CRITICAL:
g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Apr 3 14:02:35 debian bluetoothd[531]: src/profile.c:record_cb() Unable 
to get

Hands-Free Voice gateway SDP record: Host is down
Apr 3 14:02:38 debian kernel: [ 92.842352] pipewire[752]: segfault at 1 ip
b5aaf5da sp bfdedb30 error 4 in libspa-alsa.so[b5a7d000+7d000]
Apr 3 14:02:38 debian kernel: [ 92.842386] Code: 47 0c 83 c0 08 89 47 0c 8b
47 14 85 c0 74 0b 90 83 00 08 8b 40 08 85 c0 75 f6 89 f3 8b 03 89 44 24 
08 85
c0 0f 84 34 23 00 00 <0f> b6 00 88 44 24 1b 3c 3f 0f 84 87 16 00 00 83 
c3 04 31

d2 89 54
Apr 3 14:02:38 debian bluetoothd[531]: Endpoint unregistered: sender=:1.33
path=/MediaEndpoint/A2DPSource/ldac
Apr 3 14:02:38 debian [755]: 0xf9feb0: leaked proxy 0x10fa2e0 id:4
Apr 3 14:02:38 debian bluetoothd[531]: Endpoint unregistered: sender=:1.33
path=/MediaEndpoint/A2DPSink/aptx_hd
Apr 3 14:02:38 debian [755]:  sync error: core disconnected
Apr 3 14:02:38 debian bluetoothd[531]: Endpoint unregistered: sender=:1.33
path=/MediaEndpoint/A2DPSource/aptx_hd
Apr 3 14:02:38 debian [755]:  core sync error: core
disconnected
Apr 3 14:02:38 debian bluetoothd[531]: Endpoint unregistered: sender=:1.33
path=/MediaEndpoint/A2DPSink/aptx
Apr 3 14:02:38 debian [755]:  sync error: core disconnected
Apr 3 14:02:38 debian bluetoothd[531]: Endpoint unregistered: sender=:1.33
path=/MediaEndpoint/A2DPSource/aptx
Apr 3 14:02:38 debian [755]:  core sync error: core
disconnected
Apr 3 14:02:38 debian bluetoothd[531]: Endpoint unregistered: sender=:1.33

Bug#1008906: node-keygrip: autopkgtest regression in testing

[Paul Gevers]

Source: node-keygrip
Version: 1.1.0-2
Severity: serious
Justification: autopkgtest regression

Dear maintainer,

Your package has an autopkgtest, great. However, it recently started
to fail in testing, I suspect since nodejs migrated.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-keygrip/20552579/log.gz

+ mocha --reporter spec test/
internal/modules/cjs/loader.js:1102
  throw new ERR_REQUIRE_ESM(filename, parentPath, packageJsonPath);
  ^

Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: 
/usr/share/nodejs/p-limit/index.js

require() of ES modules is not supported.
require() of /usr/share/nodejs/p-limit/index.js from 
/usr/share/nodejs/p-locate/index.js is an ES module file as it is a .js 
file whose nearest parent package.json contains "type": "module" which 
defines all .js files in that package scope as ES modules.
Instead rename /usr/share/nodejs/p-limit/index.js to end in .cjs, change 
the requiring code to use import(), or remove "type": "module" from 
/usr/share/nodejs/p-limit/package.json.


at new NodeError (internal/errors.js:322:7)
at Object.Module._extensions..js 
(internal/modules/cjs/loader.js:1102:13)

at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12)
at Module.require (internal/modules/cjs/loader.js:974:19)
at require (internal/modules/cjs/helpers.js:101:18)
at Object. (/usr/share/nodejs/p-locate/index.js:2:16)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js 
(internal/modules/cjs/loader.js:1114:10)

at Module.load (internal/modules/cjs/loader.js:950:32) {
  code: 'ERR_REQUIRE_ESM'
}
autopkgtest [04:12:55]: test pkg-js-autopkgtest: ---]


OpenPGP_signature
Description: OpenPGP digital signature

Processed: found 1008745 in dh-python/5.20220215

[Debian Bug Tracking System]

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

> found 1008745 dh-python/5.20220215
Bug #1008745 [dh-python] pybuild: Handle 2-digit minor versions in 
--interpreter python3.10
Marked as found in versions dh-python/5.20220215.
> thanks
Stopping processing here.

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

Bug#1008905: node-rollup-plugin-terser: autopkgtest regression in testing

[Paul Gevers]

Source: node-rollup-plugin-terser
Version: 7.0.2+~5.0.1-2
Severity: serious
Justification: autopkgtest regression

Dear maintainer,

Your package has an autopkgtest, great. However, it recently started
to fail in testing, I suspect since nodejs migrated.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-rollup-plugin-terser/20508689/log.gz

true both import and export can be overwritten
+ jest --ci --testTimeout 6 test/test.js
internal/modules/cjs/loader.js:1015
  throw new ERR_REQUIRE_ESM(filename, parentPath, packageJsonPath);
  ^

Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: 
/usr/share/nodejs/p-limit/index.js

require() of ES modules is not supported.
require() of /usr/share/nodejs/p-limit/index.js from 
/usr/share/nodejs/p-locate/index.js is an ES module file as it is a .js 
file whose nearest parent package.json contains "type": "module" which 
defines all .js files in that package scope as ES modules.
Instead rename /usr/share/nodejs/p-limit/index.js to end in .cjs, change 
the requiring code to use import(), or remove "type": "module" from 
/usr/share/nodejs/p-limit/package.json.


at Object.Module._extensions..js 
(internal/modules/cjs/loader.js:1015:13)

at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. (/usr/share/nodejs/p-locate/index.js:2:16)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions..js 
(internal/modules/cjs/loader.js:1027:10)

at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14) {
  code: 'ERR_REQUIRE_ESM'
}
autopkgtest [22:51:51]: test pkg-js-autopkgtest: ---]


OpenPGP_signature
Description: OpenPGP digital signature

Processed: click: autopkgtest failure

[Debian Bug Tracking System]

Processing control commands:

> block 1006117 by -1
Bug #1006117 {Done: Paul Gevers } [src:lomiri-app-launch] 
src:lomiri-app-launch: fails to migrate to testing for too long: depends on new 
non-migrating package
1006117 was not blocked by any bugs.
1006117 was not blocking any bugs.
Added blocking bug(s) of 1006117: 1008904

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

Bug#1008904: click: autopkgtest failure

[Adrian Bunk]

Source: click
Version: 0.5.0-5
Severity: serious
Control: block 1006117 by -1

https://ci.debian.net/data/autopkgtest/testing/amd64/c/click/18881997/log.gz

...
==
ERROR: test_debsig_install_valid_signature 
(click_package.tests.integration.test_signatures.TestSignatureVerification)
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.s_fybmd3/downtmp/build.yqQ/src/click_package/tests/integration/test_signatures.py",
 line 208, in test_debsig_install_valid_signature
subprocess.check_call(
  File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', 
'--user=root', '/tmp/tmpfmnii6m2/org.example.debsig-valid-sig_1.0_all.click']' 
returned non-zero exit status 1.

--
Ran 19 tests in 21.496s

FAILED (errors=1, skipped=3)
autopkgtest [15:11:19]: test run-tests.sh: ---]
autopkgtest [15:11:19]: test run-tests.sh:  - - - - - - - - - - results - - - - 
- - - - - -
run-tests.sh FAIL non-zero exit status 1

Processed: Re: Bug#1008745: nipy: FTBFS with Python 3.10 as default

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 dh-python
Bug #1008745 [src:nipy] nipy: FTBFS with Python 3.10 as default
Bug reassigned from package 'src:nipy' to 'dh-python'.
No longer marked as found in versions nipy/0.5.0-2.
Ignoring request to alter fixed versions of bug #1008745 to the same values 
previously set
> retitle -1 pybuild: Handle 2-digit minor versions in --interpreter python3.10
Bug #1008745 [dh-python] nipy: FTBFS with Python 3.10 as default
Changed Bug title to 'pybuild: Handle 2-digit minor versions in --interpreter 
python3.10' from 'nipy: FTBFS with Python 3.10 as default'.
> affects -1 nipy
Bug #1008745 [dh-python] pybuild: Handle 2-digit minor versions in 
--interpreter python3.10
Added indication that 1008745 affects nipy

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

Bug#1008745: nipy: FTBFS with Python 3.10 as default

[Stefano Rivera]

Control: reassign -1 dh-python
Control: retitle -1 pybuild: Handle 2-digit minor versions in --interpreter 
python3.10
Control: affects -1 nipy

This is a dh-python bug around 2-digit minor versions in the
pybuild --interpreter command line argument:

$ pybuild --print build_dir --interpreter python3.10
E: pybuild pybuild:143: interpreter python3.10 not supported by 
BuildSystem(distutils)
$ pybuild --print build_dir --interpreter python3.10 -s custom
/tmp/nipy-0.5.0/.pybuild/cpython3_3.1/build

Both of those are problematic.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#1008903: node-make-error: autopkgtest regression in testing

[Paul Gevers]

Source: node-make-error
Version: 1.3.7-2
Severity: serious
Justification: autopkgtest regression

Dear maintainer,

Your package has an autopkgtest, great. However, it recently started
to fail in testing, I suspect since nodejs migrated.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-make-error/20508688/log.gz

autopkgtest [22:49:57]: test testsuite: [---
internal/modules/cjs/loader.js:1015
  throw new ERR_REQUIRE_ESM(filename, parentPath, packageJsonPath);
  ^

Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: 
/usr/share/nodejs/p-limit/index.js
require() of ES modules is not supported.
require() of /usr/share/nodejs/p-limit/index.js from 
/usr/share/nodejs/p-locate/index.js is an ES module file as it is a .js file 
whose nearest parent package.json contains "type": "module" which defines all 
.js files in that package scope as ES modules.
Instead rename /usr/share/nodejs/p-limit/index.js to end in .cjs, change the 
requiring code to use import(), or remove "type": "module" from 
/usr/share/nodejs/p-limit/package.json.

at Object.Module._extensions..js (internal/modules/cjs/loader.js:1015:13)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. (/usr/share/nodejs/p-locate/index.js:2:16)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14) {
  code: 'ERR_REQUIRE_ESM'
}
autopkgtest [22:49:57]: test testsuite: ---]

Bug#1008902: node-puppeteer: autopkgtest regression in testing

[Paul Gevers]

Source: node-puppeteer
Version: 13.4.1+dfsg-1
Severity: serious
Justification: autopkgtest regression

Dear maintainer,

Because your autopkgtest showed up as a blocker for chromium again (on
i386 and armhf), I just tried a reference run again on i386 and it
failed, while it succeeded not too long ago. (I suspect this is
related to the nodejs transition that just happened).

Anyways, your autopkgtest fails, please fix it.

Paul

Processed: Upstream version 0.3.0 supports Ruby 3.0

[Debian Bug Tracking System]

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

> tags 1006031 fixed-upstream
Bug #1006031 [src:ruby-diaspora-federation] ruby-diaspora-federation: FTBFS: 
ERROR:  Error installing 
/tmp/d20220218-85959-ao9ro1/diaspora_federation-0.2.7.gem: 
diaspora_federation-0.2.7 requires Ruby version ~> 2.1. The current ruby 
version is 3.0.2.107.
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#1008459: marked as done (qiskit-terra: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sun, 3 Apr 2022 18:56:24 +
with message-id <20220403185624.2ll76kc5z76xa...@emissary.chronitis.net>
and subject line fixed in nbclient
has caused the Debian Bug report #1008376,
regarding qiskit-terra: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.10 3.9" returned exit code 13
to be marked as done.

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

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


-- 
1008376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qiskit-terra
Version: 0.12.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 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
>   install -d /<>/debian/.debhelper/generated/_source/home
>   pybuild --configure -i python{version} -p "3.10 3.9"
> I: pybuild base:237: python3.10 setup.py config 
> running config
> I: pybuild base:237: python3.9 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
>   pybuild --build -i python{version} -p "3.10 3.9"
> I: pybuild base:237: /usr/bin/python3.10 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10/build/qiskit
> copying qiskit/__init__.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit
> copying qiskit/util.py -> /<>/.pybuild/cpython3_3.10/build/qiskit
> copying qiskit/user_config.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit
> copying qiskit/exceptions.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit
> copying qiskit/execute.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit
> copying qiskit/version.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit
> creating /<>/.pybuild/cpython3_3.10/build/qiskit/qobj
> copying qiskit/qobj/__init__.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/qobj
> copying qiskit/qobj/qobj.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/qobj
> copying qiskit/qobj/utils.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/qobj
> creating /<>/.pybuild/cpython3_3.10/build/qiskit/tools
> copying qiskit/tools/__init__.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/tools
> copying qiskit/tools/parallel.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/tools
> copying qiskit/tools/visualization.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/tools
> creating /<>/.pybuild/cpython3_3.10/build/qiskit/quantum_info
> copying qiskit/quantum_info/__init__.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/quantum_info
> creating /<>/.pybuild/cpython3_3.10/build/qiskit/test
> copying qiskit/test/__init__.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/test
> copying qiskit/test/decorators.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/test
> copying qiskit/test/base.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/test
> copying qiskit/test/testing_options.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/test
> copying qiskit/test/reference_circuits.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/test
> copying qiskit/test/ibmq_mock.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/test
> copying qiskit/test/utils.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/test
> creating /<>/.pybuild/cpython3_3.10/build/qiskit/compiler
> copying qiskit/compiler/__init__.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/compiler
> copying qiskit/compiler/schedule.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/compiler
> copying qiskit/compiler/assemble.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/compiler
> copying qiskit/compiler/transpile.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/compiler
> creating /<>/.pybuild/cpython3_3.10/build/qiskit/extensions
> copying qiskit/extensions/__init__.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/extensions
> copying qiskit/extensions/exceptions.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/extensions
> copying qiskit/extensions/unitary.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/extensions
> creating /<>/.pybuild/cpython3_3.10/build/qiskit/qasm
> copying qiskit/qasm/__init__.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/qasm
> copying qiskit/qasm/exceptions.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/qasm
> copying qiskit/qasm/qasmparser.py -> 
> /<>/.pybuild/cpython3_3.10/build/qiskit/qasm
> copying qiskit/qasm/qasmlexer.py -> 
> /<>/.pybuild/cpython3_3.10/build/q

Bug#1008376: marked as done (nbconvert: FTBFS: ModuleNotFoundError: No module named 'ipython_genutils')

[Debian Bug Tracking System]

Your message dated Sun, 3 Apr 2022 18:56:24 +
with message-id <20220403185624.2ll76kc5z76xa...@emissary.chronitis.net>
and subject line fixed in nbclient
has caused the Debian Bug report #1008376,
regarding nbconvert: FTBFS: ModuleNotFoundError: No module named 
'ipython_genutils'
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.)


-- 
1008376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nbconvert
Version: 6.4.4-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 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 docs/source 
> debian/python-nbconvert-doc/usr/share/doc/python-nbconvert-doc/html
> Running Sphinx v4.3.2
> 
> Configuration error:
> There is a programmable error in your configuration file:
> 
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/sphinx/config.py", line 329, in 
> eval_config_file
> exec(code, namespace)
>   File "/<>/docs/source/conf.py", line 25, in 
> exec(compile(f.read(), 'autogen_config.py', 'exec'), {})
>   File "autogen_config.py", line 11, in 
>   File "/<>/nbconvert/__init__.py", line 4, in 
> from .exporters import *
>   File "/<>/nbconvert/exporters/__init__.py", line 4, in 
> from .slides import SlidesExporter
>   File "/<>/nbconvert/exporters/slides.py", line 12, in 
> from ..preprocessors.base import Preprocessor
>   File "/<>/nbconvert/preprocessors/__init__.py", line 10, in 
> 
> from .execute import ExecutePreprocessor
>   File "/<>/nbconvert/preprocessors/execute.py", line 8, in 
> 
> from nbclient import NotebookClient, execute as _execute
>   File "/usr/lib/python3/dist-packages/nbclient/__init__.py", line 5, in 
> 
> from .client import NotebookClient, execute  # noqa: F401
>   File "/usr/lib/python3/dist-packages/nbclient/client.py", line 35, in 
> 
> from .output_widget import OutputWidget
>   File "/usr/lib/python3/dist-packages/nbclient/output_widget.py", line 6, in 
> 
> from .jsonutil import json_clean
>   File "/usr/lib/python3/dist-packages/nbclient/jsonutil.py", line 16, in 
> 
> from ipython_genutils import py3compat
> ModuleNotFoundError: No module named 'ipython_genutils'
> 
> make[1]: *** [debian/rules:26: override_dh_sphinxdoc] Error 2


The full build log is available from:
http://qa-logs.debian.net/2022/03/26/nbconvert_6.4.4-1_unstable.log

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

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

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

Bug#1006002: marked as done (pyparsing breaks cwltool autopkgtest: assert main(["--debug", "--print-dot", cwl_path], stdout=stdout) == 0)

[Debian Bug Tracking System]

Your message dated Sun, 3 Apr 2022 22:02:32 +0300
with message-id <20220403190232.GA13543@localhost>
and subject line Re: Bug#1006002: pyparsing breaks cwltool autopkgtest: assert 
main(["--debug", "--print-dot", cwl_path], stdout=stdout) == 0
has caused the Debian Bug report #1006002,
regarding pyparsing breaks cwltool autopkgtest: assert main(["--debug", 
"--print-dot", cwl_path], stdout=stdout) == 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.)


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

Source: pyparsing, cwltool
Control: found -1 pyparsing/3.0.7-1
Control: found -1 cwltool/3.1.20211104071347-3
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
pyparsing  from testing3.0.7-1
cwltoolfrom testing3.1.20211104071347-3
all others from testingfrom testing

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

Currently this regression is blocking the migration of pyparsing to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package? I note that cwltool is newer in 
unstable. I haven't tested if that "solves" the issue as the package is 
blocked from migrating currently.


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=pyparsing

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cwltool/19310147/log.gz

=== FAILURES 
===
 test_print_dot 


[gw14] linux -- Python 3.9.10 /usr/bin/python3

def test_print_dot() -> None:
# print Workflow
cwl_path = get_data("tests/wf/revsort.cwl")
cwl_posix_path = Path(cwl_path).as_posix()
expected_dot = pydot.graph_from_dot_data(
"""
digraph {{
graph [bgcolor="#ee",
clusterrank=local,
labeljust=right,
labelloc=bottom
];
subgraph cluster_inputs {{
graph [label="Workflow Inputs",
rank=same,
style=dashed
];
"file://{cwl_posix_path}#workflow_input" 
[fillcolor="#94DDF4",

label=workflow_input,
style=filled];
"file://{cwl_posix_path}#reverse_sort" 
[fillcolor="#94DDF4",

label=reverse_sort,
style=filled];
}}
subgraph cluster_outputs {{
graph [label="Workflow Outputs",
labelloc=b,
rank=same,
style=dashed
];
"file://{cwl_posix_path}#sorted_output" 
[fillcolor="#94DDF4",

label=sorted_output,
style=filled];
}}
"file://{cwl_posix_path}#rev" [fillcolor=lightgoldenrodyellow,
label=rev,
style=filled];
"file://{cwl_posix_path}#sorted" 
[fillcolor=lightgoldenrodyellow,

label=sorted,
style=filled];
"file://{cwl_posix_path}#rev" -> 
"file://{cwl_posix_path}#sorted";
"file://{cwl_posix_path}#sorted" -> 
"file://{cwl_posix_path}#sorted_output";
"file://{cwl_posix_path}#workflow_input" -> 
"file://{cwl_posix_path}#rev";
"file://{cwl_posix_path}#reverse_sort" -> 
"file://{cwl_posix_path}#sorted";

}}
""".format(
cwl_posix_path=cwl_posix_path
)
)[0]
stdout = StringIO()

  assert main(["--debug", "--print-dot", cwl_path], stdout=stdout) == 0

E   AssertionError: assert 1 == 0
E+  where 1 = main(['--debug', '--print-dot

Processed: block 1006667 with 1003933

[Debian Bug Tracking System]

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

> block 1006667 with 1003933
Bug #1006667 {Done: Étienne Mollier } 
[src:python-biopython] python-biopython - build-dependencies unsatisfiable on 
most architectures.
1006667 was not blocked by any bugs.
1006667 was not blocking any bugs.
Added blocking bug(s) of 1006667: 1003933
> thanks
Stopping processing here.

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

Bug#1008847: rust-atk-sys (autopkgtest failure with new atk)

[Samuel Thibault]

Peter Michael Green, le dim. 03 avril 2022 19:29:46 +0100, a ecrit:
> I'm more inclined towards simply ignoring this failure,

I'm fine with that as well, since your proposed changed is aligned with
upstream just dropping the value in 22f00076493c.

Thanks!
Samuel

Bug#1008901: gnss-sdr FTBFS: Missing #include

[Adrian Bunk]

Source: gnss-sdr
Version: 0.0.16-1
Severity: serious
Tags: ftbfs patch
Forwarded: https://github.com/gnss-sdr/gnss-sdr/pull/593

https://buildd.debian.org/status/logs.php?pkg=gnss-sdr&ver=0.0.16-1%2Bb2

...
/<>/src/algorithms/signal_source/adapters/limesdr_signal_source.cc:
 In constructor ‘LimesdrSignalSource::LimesdrSignalSource(const 
ConfigurationInterface*, const string&, unsigned int, unsigned int, 
Concurrent_Queue >*)’:
/<>/src/algorithms/signal_source/adapters/limesdr_signal_source.cc:100:67:
 error: ‘diagnostic_information’ is not a member of ‘boost’
  100 | LOG(WARNING) << "Boost exception: " << 
boost::diagnostic_information(e);
  |   
^~
...

Bug#999194: marked as done (mathtex: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Sun, 03 Apr 2022 18:34:46 +
with message-id 
and subject line Bug#999194: fixed in mathtex 1.03-1.1
has caused the Debian Bug report #999194,
regarding mathtex: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
999194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mathtex
Version: 1.03-1
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: mathtex
Source-Version: 1.03-1.1
Done: Marcos Talau 

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

Debian distribution maintenance software
pp.
Marcos Talau  (supplier of updated mathtex 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, 31 Mar 2022 22:07:51 -0300
Source: mathtex
Architecture: source
Version: 1.03-1.1
Distribution: unstable
Urgency: medium
Maintainer: Johan Henriksson 
Changed-By: Marcos Talau 
Closes: 620375 999194
Changes:
 mathtex (1.03-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add patch to fix a hang due to use of strcpy() on overlapping region.
 Thanks to Steven McDonald. Closes: #620375.
   * debian/rules: Add build-{arch,indep} (Closes: #999194).
Checksums-Sha1:
 cd1201a7ede03268398e71bfadeb2812b3731646 1713 mathtex_1.03-1.1.dsc
 3e95480dee051e922482b9d726430ff5a720b66b 4009 mathtex_1.03-1.1.diff.gz
 3bc6f573d46d9ebfd511055231d0ecb3961bcfd1 5807 mathtex_1.03-1.1_source.buildinfo
Checksums-Sha256:
 cb8b1e74ee94caf82a6146ff6aba2b5db6bcc8072034c0c2f58de070a3e127f8 1713 
mathtex_1.03-1.1.dsc
 02b93371a9cc1593d7ec62c682932887d5c8349e81dcaaf1bff3bda1309e6b74 4009 
mathtex_1.03-1.1.diff.gz
 f1dc24bfd9590365805515d50600a36c79225885a6ddf9f8be82f8c82ce9ccdb 5807 
mathtex_1.03-1.1_source.buildinfo
Files:
 57b883f3c173bc11f811098f925b46e0 1713 graphics optional mathtex_1.03-1.1.dsc
 0ea42bd49c621edf6c4524d1fa727d36 4009 graphics optional 
mathtex_1.03-1.1.diff.gz
 509eebbebfe540a4f9ffd0dd60f8f20f 5807 graphics optional 
mathtex_1.03-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJHPLwACgkQ3mO5xwTr
6e+YZhAAiyiF548+Wx4Baa7H9JUL8RQYwWv7uQvaSZTGn6GBx/Knd8sa1yMMhRxO
o9eLyCFalOSGD6xq6GfbtZuuD73ijcM0Jdog+DDcn5zVqny5IeLHoekSPqUk9R2B
NJ6LeSpHuUj0T4dYtF4Aw8JI7Ic56ghClSgbWdEw5jz8/NYSR3e1311iM03+f8WI
Dm22rFxvyKyHyvGzv2p9hWdPD58vcPSPHNaBdn2MCT7wqfX6HHDRxHcIqtxweuAQ
4YvkUWmKI9EqgWqmIbPTEKDg+UX7vzM7rB60l71EOH0gv64qFHn7B17bWRMkEIer
D2UvWQ28SMLIc3Af2xKO5B3JsbxqprFFqQoYdc9VPQX1b/Zvd8eCC+tL+Tlt5gWc
Xf81PaQce5Lo1RfZE1aK5o8A1HLv9o9o+JYWWqXrwxvhhPW1F0wtvtaLQdwRBhBY
+y4A6UgMhcUqwxFr4uC32mZK4fp3X3VB0SFafXD3LmPx1obte7e7k7Fj5eTC2VBM
k3T6qw3I3hp0xdxTBmfURKTJtQ/R6RX/CdszD78safsy9R4uc9qU8DY3SotNAZ+Q
3jAECuQbzBjpSwN3SAZBnOIy6sP/zU09GhnrmtI05Jh10XtbO3HQM61R18KhsVpn
Vrw5OK+ZGl5dM+tZQ12PnVehjQwDxZzTGRPBLglvaSdpGOcDrUQ=
=X3GE
-END PGP SIGNATURE End Message ---

Bug#620375: marked as done (mathtex: may hang due to use of strcpy() on overlapping region)

[Debian Bug Tracking System]

Your message dated Sun, 03 Apr 2022 18:34:46 +
with message-id 
and subject line Bug#620375: fixed in mathtex 1.03-1.1
has caused the Debian Bug report #620375,
regarding mathtex: may hang due to use of strcpy() on overlapping region
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.)


-- 
620375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mathtex
Version: 1.03-1
Severity: important

Here is a patch for mathtex 1.03:

root@ct101:/home/latex/public_html/mathtex/123# diff -u mathtex.c patched.c
--- mathtex.c   2010-06-11 23:34:25.0 +
+++ patched.c   2011-04-01 14:28:44.0 +
@@ -3630,7 +3630,7 @@
 shift from left or right to accommodate replacement of its nfirst chars by to
 -- */
 if ( tolen < nfirst )  /* shift left is easy */
-  strcpy(from,from+nshift);/* because memory doesn't overlap */
+  memmove(from,from+nshift,strlen(from+nshift)+1);
 if ( tolen > nfirst )  /* need more room at start of from */
  { char *pfrom = from+strlen(from);   /* ptr to null terminating from */
for ( ; pfrom>=from; pfrom-- ) /* shift all chars including null */


What regards this line:
-  strcpy(from,from+nshift);/* because memory doesn't overlap */

The memory overlaps, indeed. Strings `from` and `from+nshift` shares
strlen(from) - nshift common bytes!
Sometimes it may work (it worked on my Debian Lenny), but on Debian
Squeeze amd64 it produces malformed string as a result.

Using memmove fixes this problem.
+  memmove(from,from+nshift,strlen(from+nshift)+1);


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

Kernel: Linux 2.6.32-5-openvz-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages mathtex depends on:
ii  dvipng1.13-1 convert DVI files to PNG graphics
ii  libc6 2.11.2-10  Embedded GNU C Library: Shared lib
ii  texlive   2009-11TeX Live: A decent selection of th

mathtex recommends no packages.

mathtex suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: mathtex
Source-Version: 1.03-1.1
Done: Marcos Talau 

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

Debian distribution maintenance software
pp.
Marcos Talau  (supplier of updated mathtex 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, 31 Mar 2022 22:07:51 -0300
Source: mathtex
Architecture: source
Version: 1.03-1.1
Distribution: unstable
Urgency: medium
Maintainer: Johan Henriksson 
Changed-By: Marcos Talau 
Closes: 620375 999194
Changes:
 mathtex (1.03-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add patch to fix a hang due to use of strcpy() on overlapping region.
 Thanks to Steven McDonald. Closes: #620375.
   * debian/rules: Add build-{arch,indep} (Closes: #999194).
Checksums-Sha1:
 cd1201a7ede03268398e71bfadeb2812b3731646 1713 mathtex_1.03-1.1.dsc
 3e95480dee051e922482b9d726430ff5a720b66b 4009 mathtex_1.03-1.1.diff.gz
 3bc6f573d46d9ebfd511055231d0ecb3961bcfd1 5807 mathtex_1.03-1.1_source.buildinfo
Checksums-Sha256:
 cb8b1e74ee94caf82a6146ff6aba2b5db6bcc8072034c0c2f58de070a3e127f8 1713 
mathtex_1.03-1.1.dsc
 02b93371a9cc1593d7ec62c682932887d5c8349e81dcaaf1bff3bda1309e6b74 4009 
mathtex_1.03-1.1.diff.gz
 f1dc24bfd9590365805515d50600a36c79225885a6ddf9f8be82f8c82ce9ccdb 5807 
mathtex_1.03-1.1_source.buildinfo
Files:
 57b883f3c173bc11f811098f925b46e0 1713 graphics optional mathtex_1.03-1.1.dsc
 0ea42bd49c621edf6c4524d1fa727d36 4009 graphics optional 
mathtex_1.03-1.1.diff.gz
 509eebbebfe540a4f9ffd0dd60f8f20f 5807 graphics optional 
mathtex_1.03-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwT

Bug#1008847: rust-atk-sys (autopkgtest failure with new atk)

[Peter Michael Green]

Thanks for the bug report, but i'm not convinced your patch is a good 
solution.


First off afaict your patch will break the tests with the old version of 
atk, which

may create some chicken and egg issues with getting it into testing.

There are  ways around that with extra dependenices, breaks etc
but i'm not convinced it's worth it for a constant that doesn't seem to
actually be used by any rust applications (in Debian or otherwise)
and that upstream has shown they are prepared to change without
bumping the soversion (so user code needs to cope with the case
where the value of the constant the user code was built against is
different from the one atk was built against).

Secondly I don't think adding new constants is something we should
be doing in Debian patches.

I'm more inclined towards simply ignoring this failure, the situation 
doesn't

seem any different from the case where an application is compiled against
one version of atk and run against another and as I mentioned no rust code
seems to actually use the constant in question.

I've whipped up a patch to do that, anyone else have any thoughts before
I upload?

Description: allow increase in c value of ATK_STATE_LAST_DEFINED
 The new version of atk increased the value of ATK_STATE_LAST_DEFINED,
 upstream did not bump the soversion, so clearly they do not consider
 this a change that is likely to break downstream applictions.

 Futhermore the only code I can find that actually uses the constant
 in question is some code in rust-atk that translates it to an enum
 the corresponding enum value doesn't seem to actually be used for
 anything.

Author: Peter Michael Green 

--- rust-atk-sys-0.14.0.orig/tests/abi.rs
+++ rust-atk-sys-0.14.0/tests/abi.rs
@@ -134,6 +134,14 @@ fn cross_validate_constants_with_c() {
 continue;
 }
 
+if *rust_name == "(gint) ATK_STATE_LAST_DEFINED" {
+// ATK_STATE_LAST_DEFINED may increase in newer versions of the atk library.
+if c_value.parse::().unwrap_or(0) > rust_value.parse::().unwrap_or(i32::MAX) {
+results.record_passed();
+continue;
+}
+}
+
 if rust_value != c_value {
 results.record_failed();
 eprintln!(

Bug#1008350: marked as done (cage: FTBFS: ../view.c:238:57: error: ‘struct wlr_surface’ has no member named ‘subsurfaces_below’)

[Debian Bug Tracking System]

Your message dated Sun, 03 Apr 2022 18:19:15 +
with message-id 
and subject line Bug#1008350: fixed in cage 0.1.4-3
has caused the Debian Bug report #1008350,
regarding cage: FTBFS: ../view.c:238:57: error: ‘struct wlr_surface’ has no 
member named ‘subsurfaces_below’
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> cc -Icage.p -I. -I.. -I/usr/include/libdrm -I/usr/include/pixman-1 
> -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra 
> -Wpedantic -std=c11 -O0 -DWLR_USE_UNSTABLE -Wall -Wundef 
> -Wno-unused-parameter -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -MD -MQ cage.p/view.c.o -MF cage.p/view.c.o.d -o 
> cage.p/view.c.o -c ../view.c
> In file included from ../view.c:15:
> /usr/include/wlr/types/wlr_box.h:4:2: warning: #warning "wlr_box has been 
> moved to wlr/util/box.h" [-Wcpp]
> 4 | #warning "wlr_box has been moved to wlr/util/box.h"
>   |  ^~~
> In file included from /usr/include/wayland-server-core.h:32,
>  from ../view.c:14:
> ../view.c: In function ‘view_map’:
> ../view.c:238:57: error: ‘struct wlr_surface’ has no member named 
> ‘subsurfaces_below’
>   238 | wl_list_for_each (subsurface, 
> &view->wlr_surface->subsurfaces_below, parent_link) {
>   | ^~
> In file included from /usr/include/sched.h:29,
>  from /usr/include/pthread.h:22,
>  from /usr/include/xcb/xcb.h:43,
>  from /usr/include/wlr/xwayland.h:17,
>  from ../server.h:12,
>  from ../output.h:8,
>  from ../view.c:19:
> ../view.c:238:9: error: ‘struct wlr_subsurface’ has no member named 
> ‘parent_link’
>   238 | wl_list_for_each (subsurface, 
> &view->wlr_surface->subsurfaces_below, parent_link) {
>   | ^~~~
> In file included from /usr/include/wayland-server-core.h:32,
>  from ../view.c:14:
> ../view.c:238:9: error: ‘struct wlr_subsurface’ has no member named 
> ‘parent_link’
>   238 | wl_list_for_each (subsurface, 
> &view->wlr_surface->subsurfaces_below, parent_link) {
>   | ^~~~
> ../view.c:238:57: error: ‘struct wlr_surface’ has no member named 
> ‘subsurfaces_below’
>   238 | wl_list_for_each (subsurface, 
> &view->wlr_surface->subsurfaces_below, parent_link) {
>   | ^~
> ../view.c:238:9: error: ‘struct wlr_subsurface’ has no member named 
> ‘parent_link’
>   238 | wl_list_for_each (subsurface, 
> &view->wlr_surface->subsurfaces_below, parent_link) {
>   | ^~~~
> In file included from /usr/include/sched.h:29,
>  from /usr/include/pthread.h:22,
>  from /usr/include/xcb/xcb.h:43,
>  from /usr/include/wlr/xwayland.h:17,
>  from ../server.h:12,
>  from ../output.h:8,
>  from ../view.c:19:
> ../view.c:238:9: error: ‘struct wlr_subsurface’ has no member named 
> ‘parent_link’
>   238 | wl_list_for_each (subsurface, 
> &view->wlr_surface->subsurfaces_below, parent_link) {
>   | ^~~~
> In file included from /usr/include/wayland-server-core.h:32,
>  from ../view.c:14:
> ../view.c:241:57: error: ‘struct wlr_surface’ has no member named 
> ‘subsurfaces_above’
>   241 | wl_list_for_each (subsurface, 
> &view->wlr_surface->subsurfaces_above, parent_link) {
>   | ^~
> In file included from /usr/include/sched.h:29,
>  from /usr/include/pthread.h:22,
>  from /usr/include/xcb/xcb.h:43,
>  from /usr/include/wlr/xwayland.h:17,
>  from ../server.h:12,
>  from ../output.h:8,
>  from ../view.c:19:
> ../view.c:241:9: error: ‘struct wlr_subsurface’ has no member named 
> ‘parent_link’
>   241 | wl_list_for_each (subsurface, 
> &view->wlr_surface->subsurfaces_abo

Bug#1008312: clementine doesn't start

[Florian Ernst]

Hello scorpion2185,

thanks for your report. Please bear with me, as I am not the package
maintainer but just stumbled over this report.

On Sat, Mar 26, 2022 at 05:55:26PM +0100, realroot wrote:
> clementine doesn't start:
> 
> -
> clementine
> 17:53:14.456 WARN  unknown  QSqlDatabase: QSQLITE 
> driver not loaded
> 17:53:14.456 WARN  unknown  QSqlDatabase: available 
> drivers:
> [...]

Do you have the package "libqt5sql5-sqlite" installed? If not please
install it and retry.

This package normally is installed on KDE-based systems, but it seems
clementine is not explicitly forcing its installation via declaring a
Depends, so it could happen that this package is missing even though
clementine needs it.

@Thomas, I confirmed that clementine in current Bullseye behaves just
like reported if that package is missing, and the reported empty list of
available drivers indicates this is indeed the culprit. Once confirmed
by the submitter clementine will need to add an explicit Depends on that
package, both in Sid and in Bullseye (in Buster, too? I haven't checked
...).

Best regards,
Flo


signature.asc
Description: PGP signature

Bug#1008280: pstoedit: silently fails with success return for some purifyeps use cases

[Thorsten Glaser]

Hi Wolfgang,

> The issue is caused because pdftops creates a PostScript file which
> contains the whole drawing as a single bitmap image (don't know why).

Oh, ouch. So, bug in poppler after all?

>> $ pdf2ps test1.pdf test4-1.ps
>> $ ps2eps test4-1.ps

Hm, not just poppler? test4-1.ps has a large encoded blob I think is
a bitmap as well… so ghostscript does the same.

> And bitmap images are not supported by pstoedit for the mpost format.

Right, of course.

> Yes - pstoedit handles PDF nicely because GhostScript handles them like
> PostScript file. Well - at least up to version 9.55. From version 9.56
> on, the default handling of PDF files in GhostScript changes to use a

Ah, ouch, so the workaround will work on bullseye and older only.

I need to convert to PS first, but all PDF to PS converters introduce
this bug (bitmap present).

Hrm… it appears that, for those files whose source is SVG (not PDF,
we do have several of that as well), I might be able to export PS
from Inkscape. Or do the stable-and-older workaround, first.

Do the poppler and/or ghostscript maintainers perhaps have an insight
in why this PDF is converted to PS with embedded bitmap?

(Even adding -dLanguageLevel=3 to pdf2ps does not make it better.)

bye,
//mirabilos
-- 
Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht damit
gerechnet, darum bin ich blutverschmiert… wer konnte ahnen, daß SIE so
reagier’n… gestern Nacht ist mein IRC-Netzwerk explodiert~~~
(as of 2021-06-15 The MirOS Project temporarily reconvenes on OFTC)

Bug#1006788: [Debichem-devel] Bug#1006788: Bug#1006788: bagel: autopkgtest failure with new mpich.

[Michael Banck]

Hi,

On Sun, Apr 03, 2022 at 02:30:14PM +0200, Michael Banck wrote:
> On Fri, Mar 04, 2022 at 11:36:24PM +, peter green wrote:
> > Package: bagel
> > Version: 1.2.2-3
> > Severity: serious
> > x-debbugs-cc: mp...@packages.debian.org
> > 
> > bagel's autopkgtest is failing on amd64 with mpich 4.0.1-1 and hence
> > blocking it's migration to testing and hence blocking the finalisation
> > of the slurm-wlm transition.
> > 
> > https://ci.debian.net/data/autopkgtest/testing/amd64/b/bagel/19726694/log.gz
> > 
> > > running test case 'he3_svp_asd-dmrg'... FAILED.
> 
> For the record, the error in the .out file is:
> 
> |  ERROR: EXCEPTION RAISED:  dsyev/pdsyevd failed in Matrix

Hrm, it seems that test case passed now on the latest upload:
https://ci.debian.net/data/autopkgtest/unstable/amd64/b/bagel/20573831/log.gz

|Get:14 http://deb.debian.org/debian unstable/main amd64 libmpich12 amd64 
4.0.1-1 [4,924 kB]
[...]
|running test case 'he3_svp_asd-dmrg'... PASSED.

So I'm a bit at a loss about what's going on here, perhaps that test
case really is just flakey.


Michael

Processed: limit source to portaudio19, tagging 985041, tagging 997360, tagging 718221, tagging 861236 ...

[Debian Bug Tracking System]

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

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

> tags 985041 + pending
Bug #985041 [src:portaudio19] portaudio19: Outdated package git repository
Added tag(s) pending.
> tags 997360 + pending
Bug #997360 [src:portaudio19] portaudio19: FTBFS: configure: error: cannot find 
required auxiliary files: ltmain.sh compile missing
Added tag(s) pending.
> tags 718221 + pending
Bug #718221 [portaudio19-dev] portaudio19-dev: portaudio19 headers removes 
audio packages and their dependencies
Added tag(s) pending.
> tags 861236 + pending
Bug #861236 [src:portaudio19] portaudio19 should build-depend on pkg-config
Added tag(s) pending.
> tags 862625 + pending
Bug #862625 [src:portaudio19] Updating the portaudio19 Uploaders list
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#926689: cryptsetup-initramfs: config lines in grub.cfg for cryptodisk/luks and other modules missing

[Kyle Rose]

Package: grub-common
Version: 2.06-2
Followup-For: Bug #926689

Dear Maintainer,

I want to second OP's report, and add a related issue.

I have run into two problems with grub 2.06-2:

* LUKS2 metadata support is not compiled in. This is a simple fix,
  simply requiring that luks2 be added to GRUB_MODULES in
  debian/build-efi-images.

* grub-install installs the modular EFI image into the EFI system
  partition. This image lacks the modules required for
  GRUB_ENABLE_CRYPTODISK=y support to work, so the user is dumped into
  the rescue shell. Whatever logic that previously resulted in the
  monolithic image being installed is broken.

-- Package-specific info:

*** BEGIN /proc/mounts
/dev/mapper/nausicaamain-root / ext4 rw,relatime,errors=remount-ro 0 0
/dev/nvme0n1p2 /boot/efi vfat 
rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
 0 0
/dev/mapper/nausicaamain-home /home ext4 rw,relatime 0 0
/dev/mapper/nausicaawork /work ext4 rw,relatime,stripe=256 0 0
/dev/mapper/nausicaawork /home/krose/work ext4 rw,relatime,stripe=256 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

terminal_input console
terminal_output console
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu 
--class os $menuentry_id_option 
'gnulinux-simple-5ff05376-4105-4d5a-9d08-3c19a187bf5f' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod lvm
insmod ext2
set 
root='lvmid/CHS1Km-Ej3O-BzCE-jjRr-FTAW-z7Z1-fxfjQO/OLHIBB-fUee-zo0b-AJY9-fxrl-1qT1-H9TOZU'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root 
--hint='lvmid/CHS1Km-Ej3O-BzCE-jjRr-FTAW-z7Z1-fxfjQO/OLHIBB-fUee-zo0b-AJY9-fxrl-1qT1-H9TOZU'
  5ff05376-4105-4d5a-9d08-3c19a187bf5f
else
  search --no-floppy --fs-uuid --set=root 
5ff05376-4105-4d5a-9d08-3c19a187bf5f
fi
echo'Loading Linux 5.16.0-5-amd64 ...'
linux   /boot/vmlinuz-5.16.0-5-amd64 root=/dev/mapper/nausicaamain-root 
ro  cryptdevice=UUID=5bc07e8a-6a75-4d68-925b-8c107abf2ed0:lvm mitigations=off 
ip=192.168.32.7::192.168.32.1:255.255.255.0::enp6s0:off noirqdebug 
add_efi_memmap
echo'Loading initial ramdisk ...'
initrd  /boot/initrd.img-5.16.0-5-amd64
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 
'gnulinux-advanced-5ff05376-4105-4d5a-9d08-3c19a187bf5f' {
menuentry 'Debian GNU/Linux, with Linux 5.16.0-5-amd64' --class debian 
--class gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-5.16.0-5-amd64-advanced-5ff05376-4105-4d5a-9d08-3c19a187bf5f' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; 
fi
insmod lvm
insmod ext2
set 
root='lvmid/CHS1Km-Ej3O-BzCE-jjRr-FTAW-z7Z1-fxfjQO/OLHIBB-fUee-zo0b-AJY9-fxrl-1qT1-H9TOZU'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root 
--hint='lvmid/CHS1Km-Ej3O-BzCE-jjRr-FTAW-z7Z1-fxfjQO/OLHIBB-fUee-zo0b-AJY9-fxrl-1qT1-H9TOZU'
  5ff05376-4105-4d5a-9d08-3c19a187bf5f
  

Bug#1008817: marked as done (libphonenumber8: breaks evolution)

[Debian Bug Tracking System]

Your message dated Sun, 03 Apr 2022 17:20:38 +
with message-id 
and subject line Bug#1008817: fixed in libphonenumber 8.12.46-2
has caused the Debian Bug report #1008817,
regarding libphonenumber8: breaks evolution
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.)


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


Hi.

8.12.46-1 causes evolution to fail:
$ evolution
evolution: symbol lookup error: /usr/lib/x86_64-linux-gnu/libphonenumber.so.8: 
undefined symbol: _ZN4absl7debian213hash_internal9HashState5kSeedE

Downgrading to 8.12.44-1 fixes the issue.

Cheers,
Chris.



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

Kernel: Linux 5.16.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libphonenumber8 depends on:
ii  libabsl20210324  0~20210324.2-2
ii  libc62.33-7
ii  libgcc-s112-20220319-1
ii  libicu67 67.1-7
ii  libprotobuf233.12.4-1+b3
ii  libstdc++6   12-20220319-1

libphonenumber8 recommends no packages.

libphonenumber8 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libphonenumber
Source-Version: 8.12.46-2
Done: tony mancill 

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated libphonenumber 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: Sat, 02 Apr 2022 10:43:51 -0700
Source: libphonenumber
Architecture: source
Version: 8.12.46-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 1008817
Changes:
 libphonenumber (8.12.46-2) unstable; urgency=medium
 .
   * Team upload.
   * Add patch to resolve FTBFS for reverse build-deps (Closes: #1008817)
 - Thank you to Adrian Bunk and Christoph Anton Mitterer.
Checksums-Sha1:
 10f81d4221902822eda4f451c28ebbff99b1481e 2707 libphonenumber_8.12.46-2.dsc
 23a81995cd3b06ab54acf5c6188a92a83088079c 12212 
libphonenumber_8.12.46-2.debian.tar.xz
 a7195c9d9e9bfe20719fd9341d9cba118ecf11a8 16383 
libphonenumber_8.12.46-2_amd64.buildinfo
Checksums-Sha256:
 4ba2463b1c91d3ced74eb3c55a5969dda44fb11cd8f52e71fe0f18c96bcb9311 2707 
libphonenumber_8.12.46-2.dsc
 01d3411aba3bf2dcb98f01398203622652e8bc8af808f370ed74eb0a0e937a54 12212 
libphonenumber_8.12.46-2.debian.tar.xz
 14d33fb06ddac1093bab026c4818a18264a1717c074b0c4a433c5bb860faa8f3 16383 
libphonenumber_8.12.46-2_amd64.buildinfo
Files:
 ca3635b4cc7732adcc1eb3efdb50ba00 2707 libs optional 
libphonenumber_8.12.46-2.dsc
 afe43a232bc8b6f59c11d5ac6302159f 12212 libs optional 
libphonenumber_8.12.46-2.debian.tar.xz
 ce3fa2ac9266a2a0f48489e4595749ac 16383 libs optional 
libphonenumber_8.12.46-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmJJ0iQUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpaplRAAnU4nSy8VTM2nTk1mUdXUZ+ow6gf9
EWXDh+6mr9D4xDaxYtP4A5oUbX3TZx+02CNZWeXT2uqJIU1OfviP89iVWAHBe4im
FGOOqNED549Q8upQs7LhvSR4a8tk+HC8LxyHEtK1KCPBKEJuX0LqY9fuxLHcxrcm
YCZV9EbuFzCOT827QoC/EKFabSAwb+w3mwm+Wg0ffUas0QK3yj9y8rXICtiOROWX
3FXoNwLpXuVkhy562qB5SKVCSM9Q36RCIK+HKxWTTft4ghpSwyD3fcBn0Wb9KQ6J
VOwJwuam8MafCGeqNrLvQaV7xsIhy+IZ+Dh0SSReW3zJ4CUvH/lg2U8Kg3uOtRed
3vdw6JCZ7OU/pskoGdhoEJ5F8DFsHfEWuI7tB2NmTma9+USG8uDwBcbgNqi7tJwH
NWk+7cVBAKBT2dXQsAMg0qqVFaRShIg6QGojH4b1N5dkcYzJQUG8Gm2IkEwnU3mQ
XoYGWCXnDcA2DIJ/vQJVdWHUJ0Mjr+tY7s6S9FR8cWuj5rr2MP8QoFx8sFiRio1D
DllAQorFYkpcc0mMObwsRRaJ7YvuZEGg77jYwTnEpONcq//V/2NFhxgXx7c+DbJR
4T3RfiAdSFiEiwbV0C0swtyrq8AJKYvQgBpgd27embB2HVBeBWuNxlK3

Bug#1008225: marked as done (dolfin: autopkgtest failure: timeout)

[Debian Bug Tracking System]

Your message dated Sun, 03 Apr 2022 16:49:03 +
with message-id 
and subject line Bug#1008225: fixed in dolfin 2019.2.0~git20210928.3eacdb4-4
has caused the Debian Bug report #1008225,
regarding dolfin: autopkgtest failure: timeout
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.)


-- 
1008225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dolfin
Version: 2019.2.0~git20210928.3eacdb4-3
Severity: serious
Tags: sid bookworm

dolfin's autopkgtest fail with a timeout:

python/demo/test.py::test_demos[path45-demo_meshview-3D1D.py] autopkgtest 
[15:52:40]: ERROR: timed out on command "su -s /bin/bash debci -c set -e; 
export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true;  . ~/.profile 
>/dev/null 2>&1 || true; 
buildtree="/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/build.bBU/src"; mkdir -p -m 
1777 -- 
"/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/test-dolfin-python-demo-artifacts"; 
export 
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/test-dolfin-python-demo-artifacts";
 export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 
"/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/autopkgtest_tmp"; export 
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/autopkgtest_tmp"; export 
ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export 
LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=56; unset LANGUAGE LC_CTYPE 
LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME 
LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f 
/tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set 
+C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd 
"$buildtree"; chmod +x 
/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/build.bBU/src/debian/tests/test-dolfin-python-demo;
 touch /tmp/autopkgtest-lxc.1ddrdd8w/downtmp/test-dolfin-python-demo-stdout 
/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/test-dolfin-python-demo-stderr; 
/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/build.bBU/src/debian/tests/test-dolfin-python-demo
 2> >(tee -a 
/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/test-dolfin-python-demo-stderr >&2) > 
>(tee -a 
/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/test-dolfin-python-demo-stdout);" (kind: 
test)
autopkgtest [15:52:40]: test test-dolfin-python-demo: ---]
autopkgtest [15:52:40]: test test-dolfin-python-demo:  - - - - - - - - - - 
results - - - - - - - - - -
test-dolfin-python-demo FAIL timed out


See
https://ci.debian.net/data/autopkgtest/testing/amd64/d/dolfin/20301057/log.gz

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: dolfin
Source-Version: 2019.2.0~git20210928.3eacdb4-4
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated dolfin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 03 Apr 2022 15:48:51 +0200
Source: dolfin
Architecture: source
Version: 2019.2.0~git20210928.3eacdb4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Drew Parsons 
Closes: 1008225
Changes:
 dolfin (2019.2.0~git20210928.3eacdb4-4) unstable; urgency=medium
 .
   * skip test_function.py, test_function_assigner.py, and test_mesh.py
 test_shared_entities[shared_vertex-mesh_factory8] in MPI python
 unit tests (debian/tests for autopkgtest). Closes: #1008225.
Checksums-Sha1:
 04e36a4e307eaebf11c93dcd5658493d396a3693 3804 
dolfin_2019.2.0~git20210928.3eacdb4-4.dsc
 18597d7a937c8e5f026239b575014b0e5fd0871a 39160 
dolfin_2019.2.0~git20210928.3eacdb4-4.debian.tar.xz
Checksums-Sha256:
 12ba6bccd84341f8bebf5e87a099eaf9c9731159bc38e9b0fd4c3650d2ad8bcd 3804 
dolfin_2019.2.0~git20210928.3eacdb4-4.dsc
 63a61b33250fa2d9d7dcd9a5a7d8f2aa0c4a5e0c6a1eade0aae8819340425bc0 39160 
dolfin_2019.2.0~git20210928.3eacdb4-4.debian.tar.xz
Files:
 d50dcd87ed0b97548c105552c4bfa2a6 3804 math optional 
dolfin_2019.2.0~git20210928.3eacdb4-4.dsc
 061e

Bug#1008894: marked as done (gr-osmosdr cannot be installed in sid: failed dependency python3 (<< 3.10))

[Debian Bug Tracking System]

Your message dated Sun, 03 Apr 2022 16:19:07 +
with message-id 
and subject line Bug#1008865: fixed in gr-osmosdr 0.2.3-6
has caused the Debian Bug report #1008865,
regarding gr-osmosdr cannot be installed in sid: failed dependency python3 (<< 
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.)


-- 
1008865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gr-osmosdr
Version: 0.2.3-5
Severity: normal
X-Debbugs-Cc: re...@cs.unibo.it

Dear Maintainer,

   * What led up to the situation?
 python update to 3.10

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

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

Versions of packages gr-osmosdr depends on:
ii  libc6   2.33-7
ii  libgcc-s1   12-20220319-1
pn  libgnuradio-osmosdr0.2.0
pn  libgnuradio-runtime3.10.1   
ii  libstdc++6  12-20220319-1
ii  python3 3.10.4-1
ii  python3-numpy [python3-numpy-abi9]  1:1.21.5-1

Versions of packages gr-osmosdr recommends:
ii  gnuradio3.10.2.0~rc1-2
pn  gr-fosphor  

gr-osmosdr suggests no packages.
--- End Message ---
--- Begin Message ---
Source: gr-osmosdr
Source-Version: 0.2.3-6
Done: A. Maitland Bottoms 

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated gr-osmosdr 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 03 Apr 2022 10:52:14 -0400
Source: gr-osmosdr
Architecture: source
Version: 0.2.3-6
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Closes: 1004526 1008865
Changes:
 gr-osmosdr (0.2.3-6) unstable; urgency=medium
 .
   * clarify FreeSRP namespace scope (Closes: #1008865)
   * apps/osmocom_fft qtgui: Replace pyqwidget() with qwidget()
 (Closes: #1004526)
   * enable XTRX SDR support
Checksums-Sha1:
 e466193811a90d656f55e9670555ab672ed48b97 2551 gr-osmosdr_0.2.3-6.dsc
 8c19520bd1c2451c5db05457049ac8838880df43 29260 gr-osmosdr_0.2.3-6.debian.tar.xz
 792b710dd74a545c5959b7c2fad8b06f1ecc0da0 20491 
gr-osmosdr_0.2.3-6_amd64.buildinfo
Checksums-Sha256:
 a1083d9a6742e9f0bfb2ee69b5be2ccdd2bc608e3ae2f36047c8e82d39bb99c8 2551 
gr-osmosdr_0.2.3-6.dsc
 e4d49b49f27a0de662c9d7c99a8c07634d83a5470784c3b4ce7f7e5d12300509 29260 
gr-osmosdr_0.2.3-6.debian.tar.xz
 06297868a994f1633bbb7a01e3e792dfc2a890739612d7aab3040655301518fb 20491 
gr-osmosdr_0.2.3-6_amd64.buildinfo
Files:
 bdbbd96a6f92b7b63f7449cb66af20d8 2551 libdevel optional gr-osmosdr_0.2.3-6.dsc
 2e54975a3a7c68b8f0f969b7875b126e 29260 libdevel optional 
gr-osmosdr_0.2.3-6.debian.tar.xz
 8ca2c23de066f1537551c5b8c0f5bd33 20491 libdevel optional 
gr-osmosdr_0.2.3-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAmJJw3IACgkQUEHxiR9E
4JAbThAA1LxpnRswk5XMDaN3TmCK8SudDeP8/7gGqFwOzwlVdI+YZgM8GxcUMbl/
Q0xdCGrSm1hpYc9japp9m9UuzPUMPDolHNKOuv3mcv0yz9hYv3QtbHF7mIZasP2B
4HjiOwi8CwjW/mJs8ONn5KitVU5Ki4D3zRE0ycttt3MBuIbMY0xWBoXC8LBwlX/B
ErvWqVeZSdqVnLzUVHnPW4M78Z26a9fZ3p4VWxZwPoNIfOw9Yg1MJDz9NUUu5xXy
ONpkWl7NdPiiN1o6TbdatzEgh7k/QSokJSHhFPJXtDbdmq/U+FgOJwDku3Vc8vPd
uUjloxy8+94oMLXS4J9tnCODJK8F3PgyZWyxv2AbWrvrcYN4UIVx6ispugEySdW8
uY1s6CD5/zDv38ubYwAwuW7/dX6raNWrZ/JdxGzuNs9bBCAgKRDdmxHHvJntlEom
1GEBAf1wUIJR7iC/6pGJLLiQcsLNDRwHf2YaqaebhbGyAZFjioIBeeilS4zIZpaL
bN0a9jH7rKLV9jY7/vS4zIWz9w9N6XB1GmxjmZd8M+yrbUgIwITLpnFoj5YeEVMN
/ImpC9x9VlLKhOhJ/xwY/buQV6Ejz90NJiTPVJN/FcWiywr4DHUDbg5g6gHR/Lqu
KySWQN51Ao5S7yD1xIjAOmZ02U5iyvY0Cc6Mngc53S3uhhhLVfQ=
=RNtA
-END PGP SIG

Bug#1008865: marked as done (gr-osmosdr FTBFS)

[Debian Bug Tracking System]

Your message dated Sun, 03 Apr 2022 16:19:07 +
with message-id 
and subject line Bug#1008865: fixed in gr-osmosdr 0.2.3-6
has caused the Debian Bug report #1008865,
regarding gr-osmosdr FTBFS
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.)


-- 
1008865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gr-osmosdr
Version: 0.2.3-5
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=gr-osmosdr&ver=0.2.3-5%2Bb3

...
/<>/lib/freesrp/freesrp_source_c.cc:60:63: error: template 
argument 1 is invalid
   60 | void freesrp_source_c::freesrp_rx_callback(const vector 
&samples)
  |   ^
/<>/lib/freesrp/freesrp_source_c.cc:60:63: error: template 
argument 2 is invalid
/<>/lib/freesrp/freesrp_source_c.cc:60:63: error: template 
argument 1 is invalid
/<>/lib/freesrp/freesrp_source_c.cc:60:63: error: template 
argument 2 is invalid
/<>/lib/freesrp/freesrp_source_c.cc:60:63: error: template 
argument 1 is invalid
/<>/lib/freesrp/freesrp_source_c.cc:60:63: error: template 
argument 2 is invalid
/<>/lib/freesrp/freesrp_source_c.cc:60:50: error: invalid 
template-id
   60 | void freesrp_source_c::freesrp_rx_callback(const vector 
&samples)
  |  ^~
/<>/lib/freesrp/freesrp_source_c.cc:60:6: error: variable or field 
‘freesrp_rx_callback’ declared void
   60 | void freesrp_source_c::freesrp_rx_callback(const vector 
&samples)
  |  ^~~~
/<>/lib/freesrp/freesrp_source_c.cc:60:44: error: expected 
primary-expression before ‘const’
   60 | void freesrp_source_c::freesrp_rx_callback(const vector 
&samples)
  |^
/<>/lib/freesrp/freesrp_source_c.cc: In member function ‘virtual 
int freesrp_source_c::work(int, gr_vector_const_void_star&, 
gr_vector_void_star&)’:
/<>/lib/freesrp/freesrp_source_c.cc:101:9: error: reference to 
‘sample’ is ambiguous
  101 | sample s;
  | ^~
In file included from /usr/include/c++/11/functional:65,
 from /usr/include/boost/system/error_code.hpp:19,
 from /usr/include/boost/system/system_error.hpp:11,
 from /usr/include/boost/thread/exceptions.hpp:22,
 from /usr/include/boost/thread/pthread/mutex.hpp:14,
 from /usr/include/boost/thread/mutex.hpp:16,
 from /usr/include/boost/thread/barrier.hpp:16,
 from /usr/include/gnuradio/thread/thread.h:15,
 from /<>/lib/freesrp/freesrp_source_c.h:24,
 from /<>/lib/freesrp/freesrp_source_c.cc:1:
/usr/include/c++/11/bits/stl_algo.h:5845:5: note: candidates are: 
‘template _SampleIterator 
std::sample(_PopulationIterator, _PopulationIterator, _SampleIterator, 
_Distance, _UniformRandomBitGenerator&&)’
 5845 | sample(_PopulationIterator __first, _PopulationIterator __last,
  | ^~
In file included from /<>/lib/freesrp/freesrp_common.h:10,
 from /<>/lib/freesrp/freesrp_source_c.h:31,
 from /<>/lib/freesrp/freesrp_source_c.cc:1:
/usr/include/freesrp.hpp:72:12: note: ‘struct FreeSRP::sample’
   72 | struct sample
  |^~
/<>/lib/freesrp/freesrp_source_c.cc:102:36: error: ‘s’ was not 
declared in this scope
  102 | if(!_buf_queue.try_dequeue(s))
  |^
/<>/lib/freesrp/freesrp_source_c.cc:112:38: error: ‘s’ was not 
declared in this scope
  112 | out[i] = gr_complex(((float) s.i) / 2048.0f, ((float) s.q) / 
2048.0f);
  |  ^
make[3]: *** [lib/CMakeFiles/gnuradio-osmosdr.dir/build.make:471: 
lib/CMakeFiles/gnuradio-osmosdr.dir/freesrp/freesrp_source_c.cc.o] Error 1
make[3]: *** Waiting for unfinished jobs
/<>/lib/freesrp/freesrp_sink_c.cc:54:55: error: template argument 
1 is invalid
   54 | void freesrp_sink_c::freesrp_tx_callback(vector& samples)
  |   ^
/<>/lib/freesrp/freesrp_sink_c.cc:54:55: error: template argument 
2 is invalid
/<>/lib/freesrp/freesrp_sink_c.cc:54:55: error: template argument 
1 is invalid
/<>/lib/freesrp/freesrp_sink_c.cc:54:55: error: template argument 
2 is invalid
/<>/lib/freesrp/freesrp_sink_c.cc:54:55: error: template argument 
1 is invalid
/<>/lib/freesrp/freesrp_sink_c.cc:54:55: error: template argument 
2 is invalid
/<>/lib/freesrp/freesrp_sink_c.cc:54:42:

Bug#1008817: libphonenumber8: breaks evolution

[tony mancill]

On Sun, Apr 03, 2022 at 09:48:57AM +0300, Adrian Bunk wrote:
> On Sat, Apr 02, 2022 at 10:29:05AM -0700, tony mancill wrote:
> > On Sat, Apr 02, 2022 at 08:11:39PM +0300, Adrian Bunk wrote:
> > > On Sat, Apr 02, 2022 at 10:39:13AM -0600, Neil Mayhew wrote:
> > > > On 2022-04-02 09:14, tony mancill wrote:
> > > > > I will work on patching 8.12.46 and also mention this upstream. The
> > > > > changelogs for 8.12.45 and 8.12.46 only reference metadata updates.
> > > > 
> > > > If there was a non-metadata change that wasn't mentioned in the 
> > > > changelog,
> > > > it will be the second time this has happened in a fairly short period. 
> > > > The
> > > > other one was https://github.com/google/libphonenumber/pull/2698 which 
> > > > was
> > > > merged on Jan 7.
> > > 
> > > The problem is 
> > > https://github.com/google/libphonenumber/commit/5719f3a724d254b21196393d952b71ec3052e6a3
> > > 
> > > I have an approximate fix I can polish later this evening,
> > > unless Tony already has something similar.
> > 
> > Hi Adrian,
> 
> Hi Tony,
> 
> > Thank you for the pointer.  I started picking through the delta between
> > 8.12.44 and 8.12.46 and it appears that libphonenumber needs to ensure
> > that absl/hash/internal/hash.cc is linked.  I won't have a chance to
> > work on patch until later in my day (GMT-7) and so would be glad to
> > receive yours.  Otherwise, I will work on it tonight.
> 
> sorry, I didn't get to it yesterday evening.
> 
> In case you don't already have something similar, my fix is:
> https://github.com/AdrianBunk/libphonenumber/commit/a7337f0072293ae07431d5efe7d2f9efa54bfd2d

Hi Adrian,

Thank you for the patch.  I running the build for the other r-deps now.

Here is a list of the affected packages - that is, failures for builds
against the 8.12.46-1 upload due to undefined references to absl:

abiword_3.0.5~dfsg-1
chatty_0.6.3-1
evolution_3.44.0-2
evolution-data-server_3.44.0-3
evolution-ews_3.44.0-1
eweouz_0.12
folks_0.15.5-2
glabels_3.4.1-3
gnome-calls_42.0-1
gnome-contacts_41.0-2
kitinerary_21.12.3-2
mmsd-tng_1.9-1
vvmd_0.7-1
vvmplayer_1.4-1

Assuming no surprises during the rebuild, I will upload today.

Thank you all for you help.
tony

Processed: affects 1008470

[Debian Bug Tracking System]

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

> affects 1008470 src:gnudatalanguage
Bug #1008470 [libplplot-dev] libplplot-dev: Uninstallable since libltdl-dev 
stopped providing libltdl3-dev with its 2.4.7-2 upload
Added indication that 1008470 affects src:gnudatalanguage
> thanks
Stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1008894 src:gr-osmosdr
Bug #1008894 [gr-osmosdr] gr-osmosdr cannot be installed in sid: failed 
dependency python3 (<< 3.10)
Bug reassigned from package 'gr-osmosdr' to 'src:gr-osmosdr'.
No longer marked as found in versions gr-osmosdr/0.2.3-5.
Ignoring request to alter fixed versions of bug #1008894 to the same values 
previously set
> forcemerge 1008865 1008894
Bug #1008865 [src:gr-osmosdr] gr-osmosdr FTBFS
Bug #1008894 [src:gr-osmosdr] gr-osmosdr cannot be installed in sid: failed 
dependency python3 (<< 3.10)
Severity set to 'serious' from 'normal'
Marked as found in versions gr-osmosdr/0.2.3-5.
Added tag(s) ftbfs.
Merged 1008865 1008894
> affects 1008865 gr-osmosdr
Bug #1008865 [src:gr-osmosdr] gr-osmosdr FTBFS
Bug #1008894 [src:gr-osmosdr] gr-osmosdr cannot be installed in sid: failed 
dependency python3 (<< 3.10)
Added indication that 1008865 affects gr-osmosdr
Added indication that 1008894 affects gr-osmosdr
> thanks
Stopping processing here.

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

Bug#1008864: marked as done (gr-radar FTBFS with Python 3.10 as default)

[Debian Bug Tracking System]

Your message dated Sun, 03 Apr 2022 14:36:15 +
with message-id 
and subject line Bug#1008864: fixed in gr-radar 0.0.0.20180308-6
has caused the Debian Bug report #1008864,
regarding gr-radar FTBFS with Python 3.10 as default
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.)


-- 
1008864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008864
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gr-radar
Version: 0.0.0.20180308-5
Severity: serious
Tags: ftbfs patch

https://buildd.debian.org/status/logs.php?pkg=gr-radar&ver=0.0.0.20180308-5%2Bb1

...
   debian/rules override_dh_install-arch
make[1]: Entering directory '/<>'
install -d debian/tmp/usr/lib/python3
mv debian/tmp/usr/lib/python3.9/site-packages 
debian/tmp/usr/lib/python3/dist-packages
mv: cannot stat 'debian/tmp/usr/lib/python3.9/site-packages': No such file or 
directory
make[1]: *** [debian/rules:21: override_dh_install-arch] Error 1


Fix:

--- debian/rules.old2022-04-03 06:55:42.623265558 +
+++ debian/rules2022-04-03 06:55:52.167245501 +
@@ -18,7 +18,7 @@
 
 override_dh_install-arch:
install -d debian/tmp/usr/lib/python3
-   mv debian/tmp/usr/lib/python3.9/site-packages 
debian/tmp/usr/lib/python3/dist-packages
+   mv debian/tmp/usr/lib/python3.*/site-packages 
debian/tmp/usr/lib/python3/dist-packages
dh_install --arch
rm -f debian/tmp/usr/lib/python3/dist-packages/radar/*.pyc
rm -f debian/tmp/usr/lib/python3/dist-packages/radar/*.pyo
--- End Message ---
--- Begin Message ---
Source: gr-radar
Source-Version: 0.0.0.20180308-6
Done: A. Maitland Bottoms 

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated gr-radar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 03 Apr 2022 07:28:38 -0400
Source: gr-radar
Architecture: source
Version: 0.0.0.20180308-6
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Closes: 966034 1008864
Changes:
 gr-radar (0.0.0.20180308-6) unstable; urgency=medium
 .
   * refactor to build with Python 3.10 (Closes: #1008864)
   * remove obsolete generated file in examples (Closes: #966034)
Checksums-Sha1:
 eabe22d7a709b4265b27b5ba7eae19328bd9720f 2351 gr-radar_0.0.0.20180308-6.dsc
 c81618034dd325f8a02b0eca2dbf55e8962ed22b 199596 
gr-radar_0.0.0.20180308-6.debian.tar.xz
 b24baf0b377b0b237853d2d675f6c88c4514ecea 22935 
gr-radar_0.0.0.20180308-6_amd64.buildinfo
Checksums-Sha256:
 679a5b3dd97190c96883195721ab344d0824d6030d4ed1bfb7a75dd742c20d35 2351 
gr-radar_0.0.0.20180308-6.dsc
 f6097d9362508c754f4f27a3238ec5c670d86eb1274c2731acaae76941b30a53 199596 
gr-radar_0.0.0.20180308-6.debian.tar.xz
 14efde33fa014cd6192ca0cbfe174d0b64eea1c3e59f88a44ace597c2dc57693 22935 
gr-radar_0.0.0.20180308-6_amd64.buildinfo
Files:
 58b49d3f7398a38a786d1caff6bface4 2351 libdevel optional 
gr-radar_0.0.0.20180308-6.dsc
 d84b53d25caf697c0a8a73340b953c0a 199596 libdevel optional 
gr-radar_0.0.0.20180308-6.debian.tar.xz
 c476c82e0bcc8d7e872732ce543ab48c 22935 libdevel optional 
gr-radar_0.0.0.20180308-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAmJJqUIACgkQUEHxiR9E
4JDKIg/8DMeiYeXtwHxn8GlyzxPrCWVeDRscdnpKQycMY6wrNFfVRuNDQtZjBLoy
1qEsnIosbJGTbYKtfiBMskcps/y0UPE+6QDRy5KKq8+OtLUk6NJC7p4aDCesCqtm
iXzul12+FtS8NIBBT6hDskxcc2Grp1VY1SxdtZYflvaTp5ZhV5vtYKMp+3Fx+iWj
sS0N5UnFZulEjvBQ89NgihDt1++Fm/p3lbx/l/5siBGFD+qksAF0f7ou+9BWfDrc
YTkBcP0bQ3bjOKbLoOtQoSTlooFwy5T+VDaSeqL9u7UwdcVC5Dm2nJRdg/lvrIVo
1uvBGOLzxNrY2lOZ3SllO4CcQzpDP4ySyanOjk/oRsrn2fvKzxgN39ZdHA4wq6zr
eR74UM6sznPVe75TG16iCULffHrFAT3rZ5owcZKUQsqMgapAUC/p9UJ6O+dK1RH1
WS+rucKyumby3+0mspCUnxDIo2yyiFISOed7UnKAFkr23tqccaYuZzY33tdWDfeW
ucVPuJPRtWe8DdzAfh/hXjdhLL6rwEIY5sCYAeXLGBxwisJ1AqsseoH5vPfXKMkh
TatPIHytcUdpCMh1JxkcYTLfHNu8ii4uyid+nKS/iVBOmSN1G5J5MDr6b35zCAvk
i7cmRQ5c63bSrn4f57WmCyMRZdcekS0NVZvdEFma9+pB7X+so/I=
=+17P
-END PGP SIGNATURE End Me

Processed: tagging 1008641

[Debian Bug Tracking System]

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

> # According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008641#10 
> this is very likely fixed upstream
> tags 1008641 + fixed-upstream
Bug #1008641 [src:unbound] unbound: FTBFS: ./pythonmod/pythonmod.c:338: 
undefined reference to `_Py_fopen'
Bug #1008650 [src:unbound] python3-unbound: Cannot install because of Python 
dependencies
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#1008225: dolfin: autopkgtest failure: timeout

[Drew Parsons]

Source: dolfin
Followup-For: Bug #1008225

There is also an error in
test_mesh.py test_shared_entities[shared_vertex-mesh_factory8]

>   assert num_entities_global ==  mesh.num_entities_global(shared_dim)
../../../../../../usr/lib/python3/dist-packages/dolfin_utils/test/fixtures.py:96
E   assert 56.0 == 48
E +56.0

Reported upstream at
https://bitbucket.org/fenics-project/dolfin/issues/1131

It looks like a different class of error from the test_function
problem (it fails in the usual way, doesn't hand). But it's still a
test failure that will block debci, so I'll configure tests to skip it
alongside test_function.

Bug#1008466: marked as done (python-pint: FTBFS: Could not import extension nbsphinx (exception: No module named 'ipython_genutils'))

[Debian Bug Tracking System]

Your message dated Sun, 3 Apr 2022 14:51:48 +0200
with message-id <62499865.1c69fb81.7155a.0...@mx.google.com>
and subject line Re: Bug#1008466: python-pint: FTBFS: Could not import 
extension nbsphinx (exception: No module named 'ipython_genutils')
has caused the Debian Bug report #1008466,
regarding python-pint: FTBFS: Could not import extension nbsphinx (exception: 
No module named 'ipython_genutils')
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.)


-- 
1008466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pint
Version: 0.18-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 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 docs 
> debian/python-pint-doc/usr/share/doc/python-pint-doc/html
> Running Sphinx v4.3.2
> Matplotlib created a temporary config/cache directory at 
> /tmp/matplotlib-961tpbkp because the default path 
> (/sbuild-nonexistent/.config/matplotlib) is not a writable directory; it is 
> highly recommended to set the MPLCONFIGDIR environment variable to a writable 
> directory, in particular to speed up the import of Matplotlib and to better 
> support multiprocessing.
> 
> Extension error:
> Could not import extension nbsphinx (exception: No module named 
> 'ipython_genutils')
> make[1]: *** [debian/rules:13: override_dh_sphinxdoc] Error 2


The full build log is available from:
http://qa-logs.debian.net/2022/03/26/python-pint_0.18-1_unstable.log

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

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

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

On Sat, Mar 26, 2022 at 10:57:48PM +0100, Lucas Nussbaum wrote:
> Source: python-pint
> Version: 0.18-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220326 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 docs 
> > debian/python-pint-doc/usr/share/doc/python-pint-doc/html
> > Running Sphinx v4.3.2
> > Matplotlib created a temporary config/cache directory at 
> > /tmp/matplotlib-961tpbkp because the default path 
> > (/sbuild-nonexistent/.config/matplotlib) is not a writable directory; it is 
> > highly recommended to set the MPLCONFIGDIR environment variable to a 
> > writable directory, in particular to speed up the import of Matplotlib and 
> > to better support multiprocessing.
> > 
> > Extension error:
> > Could not import extension nbsphinx (exception: No module named 
> > 'ipython_genutils')
> > make[1]: *** [debian/rules:13: override_dh_sphinxdoc] Error 2

I just tried a rebuild in an unstable chroot, and it did not fail for
me, so closing this. Please reopen if you can still reproduce it.


Michael--- End Message ---

Bug#1008889: FTBFS: Build-depends libltdl3-dev which is no longer available

[Mark Hindley]

Package: cluster-glue
Version: 1.0.12-20
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

src:cluster-glue FTBFS in unstable as the build dependency on libltdl3-dev is no
longer available.

Thanks.

Mark

-- System Information:
Debian Release: bookworm/sid
Architecture: amd64 (x86_64)

Kernel: Linux 5.16.0-4-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages cluster-glue depends on:
ii  adduser  3.121
ii  bzip21.0.8-5
ii  init-system-helpers  1.62devuan1
ii  libbz2-1.0   1.0.8-5
ii  libc62.33-7
ii  libcurl4 7.82.0-2
ii  libglib2.0-0 2.72.0-1
pn  liblrm2  
pn  libopenhpi3  
pn  libopenipmi0 
pn  libpils2 
pn  libplumb2
pn  libplumbgpl2 
ii  libsnmp405.9.1+dfsg-1+b1
pn  libstonith1  
ii  libtimedate-perl 2.3300-2
ii  libxml2  2.9.13+dfsg-1
ii  lsb-base 11.1.0
ii  perl 5.34.0-3
ii  python3  3.9.8-1
ii  python3.93.9.12-1
ii  zlib1g   1:1.2.11.dfsg-4

cluster-glue recommends no packages.

Versions of packages cluster-glue suggests:
pn  ipmitool  

Bug#1006788: [Debichem-devel] Bug#1006788: bagel: autopkgtest failure with new mpich.

[Michael Banck]

On Fri, Mar 04, 2022 at 11:36:24PM +, peter green wrote:
> Package: bagel
> Version: 1.2.2-3
> Severity: serious
> x-debbugs-cc: mp...@packages.debian.org
> 
> bagel's autopkgtest is failing on amd64 with mpich 4.0.1-1 and hence
> blocking it's migration to testing and hence blocking the finalisation
> of the slurm-wlm transition.
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/b/bagel/19726694/log.gz
> 
> > running test case 'he3_svp_asd-dmrg'... FAILED.

For the record, the error in the .out file is:

|  ERROR: EXCEPTION RAISED:  dsyev/pdsyevd failed in Matrix


Michael

Processed: bug 1008638 is forwarded to https://github.com/NLnetLabs/ldns/pull/133

[Debian Bug Tracking System]

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

> forwarded 1008638 https://github.com/NLnetLabs/ldns/pull/133
Bug #1008638 [src:ldns] ldns: FTBFS: checking for the distutils Python 
package... no
Set Bug forwarded-to-address to 'https://github.com/NLnetLabs/ldns/pull/133'.
> thanks
Stopping processing here.

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

Bug#1008402: khmer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

[stefanor]

Hi Andreas (2022.04.03_08:15:43_+)
> Thanks a lot for the patch.  Do you mean by "it isn't complete yet" the
> issue that the build now fails with
> 
>FileNotFoundError: [Errno 2] No such file or directory: ''
> 
> as per Salsa CI[1]?

Exactly. That filename could be special cased (maybe in an except branch
catching ENOENT). But it feels like I've missed something higher-level
that should have avoided it trying to inspect the file more in the first
place.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#1008886: python-demgengeo build depends on the removed libltdl7-dev provides

[Adrian Bunk]

Source: python-demgengeo
Version: 1.4-4
Severity: serious
Tags: ftbfs

The following packages have unmet dependencies:
 builddeps:python-demgengeo : Depends: libltdl7-dev

This was provides dropped by libtool, changing the build dependency
to libltdl-dev fixes the build.

Processed: Re: Bug#1008802: chemps2: FTBFS on armel

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1008802 [src:chemps2] chemps2: FTBFS on armel
Severity set to 'important' from 'serious'

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

Bug#1008802: chemps2: FTBFS on armel

[Adrian Bunk]

Control: severity -1 important

On Fri, Apr 01, 2022 at 08:55:58PM +0200, Sebastian Ramacher wrote:
> Source: chemps2
> Version: 1.8.11-1
> Severity: serious
> Tags: ftbfs sid bookworm
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org
> 
> chemps2 FTBFS on armel:
> 
> 
> cd obj-arm-linux-gnueabi/ && ctest -R "^test3|^test5|^test8"
> Test project /<>/obj-arm-linux-gnueabi
> Start 3: test3
> 1/3 Test #3: test3 ***Exception: SegFault 14.74 
> sec
> Start 5: test5
> 2/3 Test #5: test5    Passed   31.19 sec
> Start 8: test8
> 3/3 Test #8: test8    Passed   15.10 sec
> 
> 67% tests passed, 1 tests failed out of 3
> 
> Total Test time (real) =  61.05 sec
> 
> The following tests FAILED:
> 3 - test3 (SEGFAULT)
> Errors while running CTest
> Output from these tests are in: 
> /<>/obj-arm-linux-gnueabi/Testing/Temporary/LastTest.log
> 
> 
> See
> https://buildd.debian.org/status/fetch.php?pkg=chemps2&arch=armel&ver=1.8.11-1%2Bb1&stamp=1648469570&raw=0

It built for me on the porterbox abel (which is the same hardware as the 
buildds where it failed), and it also built on a buildd after a give-back.

I am lowering the severity since there is no way to debug this problem 
when it is no longer reproducible.

> Cheers

cu
Adrian

Processed: Re: dolfin: autopkgtest failure: timeout

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bitbucket.org/fenics-project/dolfin/issues/1130
Bug #1008225 [src:dolfin] dolfin: autopkgtest failure: timeout
Set Bug forwarded-to-address to 
'https://bitbucket.org/fenics-project/dolfin/issues/1130'.

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

Bug#1008225: dolfin: autopkgtest failure: timeout

[Drew Parsons]

Source: dolfin
Version: 2019.2.0~git20210928.3eacdb4-3
Followup-For: Bug #1008225
Control: forwarded -1 https://bitbucket.org/fenics-project/dolfin/issues/1130

I can reproduce the error locally. Verbose flag exposes the specific
failing tests:

$ mpirun -n 3 pytest-3 -v test_function.py 
===
 test session starts 
===
platform linux -- Python 3.10.4, pytest-6.2.5, py-1.10.0, pluggy-1.0.0 -- 
/usr/bin/python3
===
 test session starts 
===
platform linux -- Python 3.10.4, pytest-6.2.5, py-1.10.0, pluggy-1.0.0 -- 
/usr/bin/python3
===
 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
hypothesis profile 'default' -> 
database=DirectoryBasedExampleDatabase('/build/tests/output/.hypothesis/examples')
rootdir: /build/tests/output
plugins: asyncio-0.18.2, xvfb-2.0.0, arraydiff-0.5.0, cov-3.0.0, 
hypothesis-6.36.0, flaky-3.7.0, astropy-header-0.2.1, remotedata-0.3.3, 
filter-subpackage-0.1.1, doctestplus-0.12.0, mpi-0.6, openfiles-0.5.0, 
mock-3.6.1
asyncio: mode=legacy
collecting ... cachedir: .pytest_cache
hypothesis profile 'default' -> 
database=DirectoryBasedExampleDatabase('/build/tests/output/.hypothesis/examples')
rootdir: /build/tests/output
plugins: asyncio-0.18.2, xvfb-2.0.0, arraydiff-0.5.0, cov-3.0.0, 
hypothesis-6.36.0, flaky-3.7.0, astropy-header-0.2.1, remotedata-0.3.3, 
filter-subpackage-0.1.1, doctestplus-0.12.0, mpi-0.6, openfiles-0.5.0, 
mock-3.6.1
asyncio: mode=legacy
collecting ... cachedir: .pytest_cache
hypothesis profile 'default' -> 
database=DirectoryBasedExampleDatabase('/build/tests/output/.hypothesis/examples')
rootdir: /build/tests/output
plugins: asyncio-0.18.2, xvfb-2.0.0, arraydiff-0.5.0, cov-3.0.0, 
hypothesis-6.36.0, flaky-3.7.0, astropy-header-0.2.1, remotedata-0.3.3, 
filter-subpackage-0.1.1, doctestplus-0.12.0, mpi-0.6, openfiles-0.5.0, 
mock-3.6.1
asyncio: mode=legacy
collected 19 items  

  

collected 19 items  

  
collected 19 items  

  

test_function.py::test_name_argument 
test_function.py::test_name_argument PASSED 

[  5%]PASSED

 [  5%]PASSED   

  [  5%]
test_function.py::test_in_function_space 

test_function.py::test_in_function_space 
test_function.py::test_in_function_space PASSED 

[ 10%]
test_function.py::test_compute_vertex_values PASSED 

[ 10%]PASSED

 [ 10%]
test_function.py::test_compute_vertex_values 
test_function.py::test_compute_vertex_values PASSED 

[ 15%]PASSED

 [ 15%]PASSED   

  [ 15%]
test

Processed: src:python-xarray: fails to migrate to testing for too long: unresolved RC bugs (autopkgtest regression)

[Debian Bug Tracking System]

Processing control commands:

> close -1 2022.03.0-2
Bug #1008871 [src:python-xarray] src:python-xarray: fails to migrate to testing 
for too long: unresolved RC bugs (autopkgtest regression)
Marked as fixed in versions python-xarray/2022.03.0-2.
Bug #1008871 [src:python-xarray] src:python-xarray: fails to migrate to testing 
for too long: unresolved RC bugs (autopkgtest regression)
Marked Bug as done
> block -1 by 1004870
Bug #1008871 {Done: Paul Gevers } [src:python-xarray] 
src:python-xarray: fails to migrate to testing for too long: unresolved RC bugs 
(autopkgtest regression)
1008871 was not blocked by any bugs.
1008871 was not blocking any bugs.
Added blocking bug(s) of 1008871: 1004870
> block -1 by 1004869
Bug #1008871 {Done: Paul Gevers } [src:python-xarray] 
src:python-xarray: fails to migrate to testing for too long: unresolved RC bugs 
(autopkgtest regression)
1008871 was blocked by: 1004870
1008871 was not blocking any bugs.
Added blocking bug(s) of 1008871: 1004869

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

Bug#1008871: src:python-xarray: fails to migrate to testing for too long: unresolved RC bugs (autopkgtest regression)

[Paul Gevers]

Source: python-xarray
Version: 0.20.2-1
Severity: serious
Control: close -1 2022.03.0-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1004870
Control: block -1 by 1004869

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:python-xarray has been trying to migrate 
for 61 days [2]. Hence, I am filing this bug.


While inspecting the blocking bugs, it turns out that python-xarray has 
already regressed on all architectures in testing. In stead of changing 
the version of those existing bugs (the error is different, at least for 
s390x) and starting the autoremoval counter immediately, I filed this 
bug which is part of my workflow anyways, giving you some more days to 
figure it all out.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=python-xarray


OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:gcc-11-cross-ports: fails to migrate to testing for too long: FTBFS

[Debian Bug Tracking System]

Processing control commands:

> close -1 8
Bug #1008869 [src:gcc-11-cross-ports] src:gcc-11-cross-ports: fails to migrate 
to testing for too long: FTBFS
The source 'gcc-11-cross-ports' and version '8' do not appear to match any 
binary packages
Marked as fixed in versions gcc-11-cross-ports/8.
Bug #1008869 [src:gcc-11-cross-ports] src:gcc-11-cross-ports: fails to migrate 
to testing for too long: FTBFS
Marked Bug as done
> block -1 by 1005473
Bug #1008869 {Done: Paul Gevers } [src:gcc-11-cross-ports] 
src:gcc-11-cross-ports: fails to migrate to testing for too long: FTBFS
1008869 was not blocked by any bugs.
1008869 was not blocking any bugs.
Added blocking bug(s) of 1008869: 1005473

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

Bug#1008869: src:gcc-11-cross-ports: fails to migrate to testing for too long: FTBFS

[Paul Gevers]

Source: gcc-11-cross-ports
Version: 7
Severity: serious
Control: close -1 8
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1005473

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:gcc-11-cross-ports has been trying to 
migrate for 61 days [2]. Hence, I am filing this bug.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=gcc-11-cross-ports



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008722: Possible bugfix

[Sudip Mukherjee]

On Thu, Mar 31, 2022 at 5:48 PM Moessbauer, Felix
 wrote:
>
> Hi,
>
> I debugged this further and found that the problem is a partially-written 
> tracefs-sqlhist.o file.
> With the patch in [1] I can no longer reproduce the bug.

Thanks for the patch Felix.
Will upload today with this patch added.

>
> Still, I don't fully understand why it is required to explicitly mention the 
> dependency to tracefs-sqlhist.c.

I have informed Steve (upstream) about this. Hopefully he will have
some explanation.


-- 
Regards
Sudip

Bug#1008444: marked as done (libstatgen: FTBFS: ar: ../libStatGen_debug.a: file format not recognized)

[Debian Bug Tracking System]

Your message dated Sun, 03 Apr 2022 08:34:34 +
with message-id 
and subject line Bug#1008444: fixed in libstatgen 1.0.15-5
has caused the Debian Bug report #1008444,
regarding libstatgen: FTBFS: ar: ../libStatGen_debug.a: file format not 
recognized
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.)


-- 
1008444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libstatgen
Version: 1.0.15-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 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 '/<>/vcf'
> rm -f  ../include/FastQFile.h ../include/BaseCount.h 
> ../include/BaseComposition.h ../include/FastQStatus.h
> rm -f  ../include/VcfFile.h ../include/VcfFileReader.h 
> ../include/VcfFileWriter.h ../include/VcfGenotypeField.h 
> ../include/VcfGenotypeFormat.h ../include/VcfGenotypeSample.h 
> ../include/VcfHeader.h ../include/VcfHelper.h ../include/VcfRecord.h 
> ../include/VcfRecordField.h ../include/VcfRecordFilter.h 
> ../include/VcfRecordGenotype.h ../include/VcfRecordInfo.h 
> ../include/VcfSubsetSamples.h ../include/VcfRecordDiscardRules.h
> rm -f  ../include/GlfException.h ../include/GlfFile.h ../include/GlfHeader.h 
> ../include/GlfRecord.h ../include/GlfRefSection.h ../include/GlfStatus.h
> ar d ../libStatGen.a obj/FastQFile.o obj/BaseCount.o obj/BaseComposition.o 
> obj/FastQStatus.o
> ar d ../libStatGen.a obj/VcfFile.o obj/VcfFileReader.o obj/VcfFileWriter.o 
> obj/VcfGenotypeField.o obj/VcfGenotypeFormat.o obj/VcfGenotypeSample.o 
> obj/VcfHeader.o obj/VcfHelper.o obj/VcfRecord.o obj/VcfRecordField.o 
> obj/VcfRecordFilter.o obj/VcfRecordGenotype.o obj/VcfRecordInfo.o 
> obj/VcfSubsetSamples.o obj/VcfRecordDiscardRules.o
> ar d ../libStatGen.a obj/GlfException.o obj/GlfFile.o obj/GlfHeader.o 
> obj/GlfRecord.o obj/GlfRefSection.o obj/GlfStatus.o
> ranlib ../libStatGen.a
> rm -f  ../include/SamFileHeader.h ../include/SamFile.h 
> ../include/GenericSamInterface.h ../include/SamInterface.h 
> ../include/BamInterface.h ../include/SamRecord.h ../include/BamIndex.h 
> ../include/SamHeaderHD.h ../include/SamHeaderPG.h 
> ../include/SamHeaderRecord.h ../include/SamHeaderSQ.h 
> ../include/SamHeaderRG.h ../include/SamHeaderTag.h ../include/SamValidation.h 
> ../include/SamStatistics.h ../include/SamQuerySeqWithRefHelper.h 
> ../include/SamFilter.h ../include/PileupElement.h 
> ../include/PileupElementBaseQual.h ../include/SamReferenceInfo.h 
> ../include/SamTags.h ../include/PosList.h ../include/CigarHelper.h 
> ../include/SamRecordPool.h ../include/SamCoordOutput.h 
> ../include/SamRecordHelper.h ../include/Pileup.h ../include/SamHelper.h 
> ../include/SamFlag.h ../include/SamStatus.h
> ranlib ../libStatGen.a
> ranlib ../libStatGen.a
> ar d ../libStatGen_debug.a obj/debug/FastQFile.o obj/debug/BaseCount.o 
> obj/debug/BaseComposition.o obj/debug/FastQStatus.o
> ar d ../libStatGen.a obj/SamFileHeader.o obj/SamFile.o 
> obj/GenericSamInterface.o obj/SamInterface.o obj/BamInterface.o 
> obj/SamRecord.o obj/BamIndex.o obj/SamHeaderHD.o obj/SamHeaderPG.o 
> obj/SamHeaderRecord.o obj/SamHeaderSQ.o obj/SamHeaderRG.o obj/SamHeaderTag.o 
> obj/SamValidation.o obj/SamStatistics.o obj/SamQuerySeqWithRefHelper.o 
> obj/SamFilter.o obj/PileupElement.o obj/PileupElementBaseQual.o 
> obj/SamReferenceInfo.o obj/SamTags.o obj/PosList.o obj/CigarHelper.o 
> obj/SamRecordPool.o obj/SamCoordOutput.o obj/SamRecordHelper.o
> ar d ../libStatGen_debug.a obj/debug/VcfFile.o obj/debug/VcfFileReader.o 
> obj/debug/VcfFileWriter.o obj/debug/VcfGenotypeField.o 
> obj/debug/VcfGenotypeFormat.o obj/debug/VcfGenotypeSample.o 
> obj/debug/VcfHeader.o obj/debug/VcfHelper.o obj/debug/VcfRecord.o 
> obj/debug/VcfRecordField.o obj/debug/VcfRecordFilter.o 
> obj/debug/VcfRecordGenotype.o obj/debug/VcfRecordInfo.o 
> obj/debug/VcfSubsetSamples.o obj/debug/VcfRecordDiscardRules.o
> ranlib ../libStatGen_debug.a
> ranlib ../libStatGen.a
> ar d ../libStatGen_debug.a obj/debug/GlfException.o obj/debug/GlfFile.o 
> obj/debug/GlfHeader.o obj/debug/GlfRecord.o obj/debug/GlfRefSection.o 
> obj/debug/GlfStatus.o
> ranlib ../libStatGen_debug.a
> ar d ../libStatGen_profile.a obj/profile/FastQFile.o obj/profile/BaseCount.o 
> obj/profile/BaseComposition.o obj/profile/FastQStatus.o
> ar d ../libStatGen_debug.a obj/debug/SamFileHeader.o obj/debug/SamFile.o 
> obj/debug/GenericSamInterface.o obj/debug/SamInterf

Processed: affects 1008817

[Debian Bug Tracking System]

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

> affects 1008817 evolution
Bug #1008817 [libphonenumber8] libphonenumber8: breaks evolution
Added indication that 1008817 affects evolution
> thanks
Stopping processing here.

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