Processed: Bug#996335 marked as pending in pulseaudio

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #996335 [pulseaudio] pulseaudio FTBFS, doxygen not found.
Added tag(s) pending.

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

Bug#996335: marked as pending in pulseaudio

[Laurent Bigonville]

Control: tag -1 pending

Hello,

Bug #996335 in pulseaudio 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/pulseaudio-team/pulseaudio/-/commit/b1706f98d107aabc3f5ce372fe316f826e75a72f


debian/rules: Explicitly disable building doxygen documentation

Closes: #996335


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996335

Processed: severity of 996335 is serious

[Debian Bug Tracking System]

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

> severity 996335 serious
Bug #996335 [pulseaudio] pulseaudio FTBFS, doxygen not found.
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#1001718: marked as done (astroscrappy breaks ccdproc autopkgtest: detect_cosmics() got an unexpected keyword argument 'pssl')

[Debian Bug Tracking System]

Your message dated Wed, 15 Dec 2021 07:53:01 +0100
with message-id 
and subject line Re: astroscrappy breaks ccdproc autopkgtest: detect_cosmics() 
got an unexpected keyword argument 'pssl'
has caused the Debian Bug report #1001718,
regarding astroscrappy breaks ccdproc autopkgtest: detect_cosmics() got an 
unexpected keyword argument 'pssl'
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.)


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

Source: astroscrappy, ccdproc
Control: found -1 astroscrappy/1.1.0-1
Control: found -1 ccdproc/2.2.0-1
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 astroscrappy the autopkgtest of ccdproc fails in 
testing when that autopkgtest is run with the binary packages of 
astroscrappy from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
astroscrappy   from testing1.1.0-1
ccdprocfrom testing2.2.0-1
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 astroscrappy to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/c/ccdproc/17555299/log.gz


=== FAILURES 
===
 test_cosmicray_lacosmic_does_not_change_input 
_


def test_cosmicray_lacosmic_does_not_change_input():
ccd_data = ccd_data_func()
original = ccd_data.copy()
error = np.zeros_like(ccd_data)

  ccd = cosmicray_lacosmic(ccd_data)


/usr/lib/python3/dist-packages/ccdproc/tests/test_ccdproc.py:794: _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ /usr/lib/python3/dist-packages/ccdproc/core.py:1525: in cosmicray_lacosmic

crmask, cleanarr = detect_cosmics(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

  ???

E   TypeError: detect_cosmics() got an unexpected keyword argument 'pssl'

astroscrappy/astroscrappy.pyx:26: TypeError
___ test_cosmicray_lacosmic 



def test_cosmicray_lacosmic():
ccd_data = ccd_data_func(data_scale=DATA_SCALE)
threshold = 5
add_cosmicrays(ccd_data, DATA_SCALE, threshold, ncrays=NCRAYS)
noise = DATA_SCALE * np.ones_like(ccd_data.data)

  data, crarr = cosmicray_lacosmic(ccd_data.data, sigclip=5)


/usr/lib/python3/dist-packages/ccdproc/tests/test_cosmicray.py:38: _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ /usr/lib/python3/dist-packages/ccdproc/core.py:1491: in cosmicray_lacosmic

crmask, cleanarr = detect_cosmics(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

  ???

E   TypeError: detect_cosmics() got an unexpected keyword argument 'pssl'

astroscrappy/astroscrappy.pyx:26: TypeError
___ test_cosmicray_lacosmic_ccddata 



def test_cosmicray_lacosmic_ccddata():
ccd_data = ccd_data_func(data_scale=DATA_SCALE)
threshold = 5
add_cosmicrays(ccd_data, DATA_SCALE, threshold, ncrays=NCRAYS)
noise = DATA_SCALE * np.ones_like(ccd_data.data)
ccd_data.uncertainty = noise

  nccd_data = cosmicray_lacosmic(ccd_data, sigclip=5)


/usr/lib/python3/dist-packages/ccdproc/tests/test_cosmicray.py:52: _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ /usr/lib/python3/dist-packages/ccdproc/core.py:1525: in cosmicray_lacosmic

crmask, cleanarr = detect_cosmics(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

  ???

E   TypeError: detect_cosmics() got an unexpected keyword argument 'pssl'

astroscrappy/astroscrappy.pyx:26: TypeError
- Captured stdout call 
-
INFO: array provided for uncertainty; assuming it is a 

Bug#999127: marked as done (libpoe-component-client-ident-perl: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Wed, 15 Dec 2021 06:49:09 +
with message-id 
and subject line Bug#999127: fixed in libpoe-component-client-ident-perl 1.16-1
has caused the Debian Bug report #999127,
regarding libpoe-component-client-ident-perl: 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.)


-- 
999127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpoe-component-client-ident-perl
Version: 1.07-2.3
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: libpoe-component-client-ident-perl
Source-Version: 1.16-1
Done: Damyan Ivanov 

We believe that the bug you reported is fixed in the latest version of
libpoe-component-client-ident-perl, which is due to be installed in the Debian 
FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated 
libpoe-component-client-ident-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Dec 2021 06:35:06 +
Source: libpoe-component-client-ident-perl
Architecture: source
Version: 1.16-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Damyan Ivanov 
Closes: 965680 999127
Changes:
 libpoe-component-client-ident-perl (1.16-1) unstable; urgency=medium
 .
   * Take over for the Debian Perl Group
 .
   * debian/control: Added: Vcs-Git field (source stanza); Vcs-Browser
 field (source stanza); ${misc:Depends} to Depends: field. Changed:
 Maintainer set to Debian Perl Group  (was: Don Armstrong
 ); Don Armstrong  moved to
 Uploaders.
   * debian/watch: use metacpan-based URL.
   * use debhelper 13 sequencer, wrap-and-sort, add b-d for Module-Install
 (Closes: #999127 -- missing build-arch and build-indep targets in
 debian/rules)
 (Closes: #965680 -- deprecated debhelper compatibility levels)
   * restore Makefile.PL to version from upstream
   * declare debian source format to be '3.0 (quilt)'
   * shift binary package Priority from extra to optional
   * drop redundant Section/Priority headers
   * add myself to Uploaders
   * declare compatibility with Policy 4.6.0
   * bump watch version to 4
   * convert debian/copyright to machine-readable format; add myself
   * drop leading article from short description
   * add years to copyright notices
   * add Testsuite header
   * New upstream version 1.16
   * update debian/copyright
   * add libtest-poe-server-tcp-perl to build dependencies
   * add inc/Module/Install to debian/copyright
   * patch a spelling mistace in documentation
Checksums-Sha1: 
 e2a4fe162e3635755e8f806269b88dee4cd6a26b 2357 
libpoe-component-client-ident-perl_1.16-1.dsc
 10fdf2bc22ae8cdd8ec34c1fdeaddd1e3bccbc18 30205 
libpoe-component-client-ident-perl_1.16.orig.tar.gz
 a27197c174cbb1f66706021de3c7de138570b647 2996 
libpoe-component-client-ident-perl_1.16-1.debian.tar.xz
Checksums-Sha256: 
 3ea3af27ffe8e2e49349bd4e102c950a5ccd9044791d340b082ce80eccb98db8 2357 
libpoe-component-client-ident-perl_1.16-1.dsc
 2a5b1ce0b15fde4ca2167931d8c455330486044a32df3d91e582bc23b1a0fcb4 30205 
libpoe-component-client-ident-perl_1.16.orig.tar.gz
 917398a82f5074849dde09961fe2dcbf5e8e888364b16f5ca79ab6a2e636884c 2996 
libpoe-component-client-ident-perl_1.16-1.debian.tar.xz
Files: 
 

Processed: Bug#999127 marked as pending in libpoe-component-client-ident-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #999127 [src:libpoe-component-client-ident-perl] 
libpoe-component-client-ident-perl: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999127: marked as pending in libpoe-component-client-ident-perl

[Damyan Ivanov]

Control: tag -1 pending

Hello,

Bug #999127 in libpoe-component-client-ident-perl reported by you has been 
fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/perl-team/modules/packages/libpoe-component-client-ident-perl/-/commit/190f70d6901c1489947d7499599b3347437ff145


use debhelper 13 sequencer, wrap-and-sort, add b-d for Module-Install

Closes: #999127 -- missing build-arch and build-indep targets in
debian/rules


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/999127

Bug#1001729: apache-log4j2: CVE-2021-45046: Incomplete fix for CVE-2021-44228 in certain non-default configurations

[Salvatore Bonaccorso]

Hi Markus,

On Tue, Dec 14, 2021 at 11:45:20PM +0100, Markus Koschany wrote:
> Control: owner -1 !
> 
> Am Dienstag, dem 14.12.2021 um 21:37 +0100 schrieb Salvatore Bonaccorso:
> > Source: apache-log4j2
> > Version: 2.15.0-1
> > Severity: grave
> > Tags: security upstream
> > Justification: user security hole
> > Forwarded: https://issues.apache.org/jira/browse/LOG4J2-3221
> > X-Debbugs-Cc: car...@debian.org, Debian Security Team
> > 
> > Control: found -1 2.15.0-1~deb11u1
> > Control: found -1 2.15.0-1~deb10u1
> > 
> > Hi,
> > 
> > The following vulnerability was published for apache-log4j2. Strictly
> > speaking it's less severe as CVE-2021-44228 as it is an incomplete fix
> > for the former CVE in certain non-default configurations.
> 
> Hi Salvatore,
> 
> I believe Stretch is not vulnerable to CVE-2021-45046 because I have removed
> the JndiLookup class when I fixed CVE-2021-44228.

Oh, good in this case I would mark it with something along the lines:

[stretch] - apache-log4j2  (Incomplete fix for 
CVE-2021-44228 not applied; JndiLookup class removed as part of fix for 
CVE-2021-44228)

> Shall I release a new DSA for CVE-2021-45046 or a regression update for CVE-
> 2021-44228 because of the incomplete upstream fix?

You are right, it might be a bit borderline towards a "regression
update". But as it is considered both a CVE assigned because of an
incomplete fix, but still can be seen as own issue I would just
allocate a new DSA number for the update and make it a regular
security update. 

My reasoning here is is not, that the CVE-2021-44228 was thought to be
meant to be addressed remains unfixed, but some other edge  cases were
not covered, making the fix incomplete, but still beeing a  own
"issue".

So just allocate a new DSA for it covering the CVE-2021-45046 CVE.

Thanks for working on the update!

Regards,
Salvatore

Bug#1001735: marked as done (node-trust-keyto: autopkgtest regression: Cannot find module '@trust/keyto')

[Debian Bug Tracking System]

Your message dated Wed, 15 Dec 2021 05:49:18 +
with message-id 
and subject line Bug#1001735: fixed in node-trust-keyto 2.0.0~alpha1-2
has caused the Debian Bug report #1001735,
regarding node-trust-keyto: autopkgtest regression: Cannot find module 
'@trust/keyto'
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.)


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

Source: node-trust-keyto
Version: 2.0.0~alpha1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
node-trust-keyto   from testing2.0.0~alpha1-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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=node-trust-keyto

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-trust-keyto/17556375/log.gz

internal/modules/cjs/loader.js:818
  throw err;
  ^

Error: Cannot find module '@trust/keyto'
Require stack:
- /tmp/autopkgtest-lxc.wqzautxi/downtmp/build.Vrg/src/[eval]
at Function.Module._resolveFilename 
(internal/modules/cjs/loader.js:815:15)

at Function.Module._load (internal/modules/cjs/loader.js:667:27)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at [eval]:1:1
at Script.runInThisContext (vm.js:120:18)
at Object.runInThisContext (vm.js:309:38)
at Object. ([eval]-wrapper:10:26)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at evalScript (internal/process/execution.js:94:25) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ 
'/tmp/autopkgtest-lxc.wqzautxi/downtmp/build.Vrg/src/[eval]' ]

}
autopkgtest [06:13:32]: test command1



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-trust-keyto
Source-Version: 2.0.0~alpha1-2
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-trust-keyto package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Dec 2021 06:37:41 +0100
Source: node-trust-keyto
Architecture: source
Version: 2.0.0~alpha1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1001735
Changes:
 node-trust-keyto (2.0.0~alpha1-2) unstable; urgency=medium
 .
   * Team upload
   * Fix autopkgtest and mark it as superficial (Closes: #1001735)
Checksums-Sha1: 
 0b0ac25feea8ac1d25f126f19ca3a41bbd1b3e51 2238 
node-trust-keyto_2.0.0~alpha1-2.dsc
 9173eef6284fce76b46af55c78e16f9501c69f2d 4636 
node-trust-keyto_2.0.0~alpha1-2.debian.tar.xz
Checksums-Sha256: 
 63f26df5054ea5edce11adc688fbf5f3f1c54c47c2da4a38358b2bc8c6d57688 2238 
node-trust-keyto_2.0.0~alpha1-2.dsc
 afcdd8a17e5417ff3811d12def6b0e4da7f3fce608b477c267df3d15b249ccea 4636 
node-trust-keyto_2.0.0~alpha1-2.debian.tar.xz
Files: 
 f9d7d669ba645c6afac78be301277192 2238 javascript optional 
node-trust-keyto_2.0.0~alpha1-2.dsc
 ef74662e46d96bd64f05903bd452859f 4636 javascript optional 
node-trust-keyto_2.0.0~alpha1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmG5f3oACgkQ9tdMp8mZ
7un/7xAAneUkEAQtTXLmWIYaaIVw8hOyE/WHHRn5dV/EzqRX9Q7EUaDfTtQOeTfF

Bug#1001732: marked as done (node-n3: autopkgtest regression: Cannot find module 'readable-stream')

[Debian Bug Tracking System]

Your message dated Wed, 15 Dec 2021 05:49:08 +
with message-id 
and subject line Bug#1001732: fixed in node-n3 1.12.2+~1.2.3+~1.10.4-1
has caused the Debian Bug report #1001732,
regarding node-n3: autopkgtest regression: Cannot find module 'readable-stream'
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.)


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

Source: node-n3
Version: 1.12.1+~1.2.3-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
node-n3from testing1.12.1+~1.2.3-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Are you 
missing a (test) dependency?


Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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=node-n3

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

internal/modules/cjs/loader.js:818
  throw err;
  ^

Error: Cannot find module 'readable-stream'
Require stack:
- /usr/share/nodejs/n3/lib/N3Store.js
- /usr/share/nodejs/n3/lib/index.js
- /tmp/autopkgtest-lxc.abtfpkoq/downtmp/build.2gd/src/[eval]
at Function.Module._resolveFilename 
(internal/modules/cjs/loader.js:815:15)

at Function.Module._load (internal/modules/cjs/loader.js:667:27)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. (/usr/share/nodejs/n3/lib/N3Store.js:10:23)
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)
at Module.require (internal/modules/cjs/loader.js:887:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
'/usr/share/nodejs/n3/lib/N3Store.js',
'/usr/share/nodejs/n3/lib/index.js',
'/tmp/autopkgtest-lxc.abtfpkoq/downtmp/build.2gd/src/[eval]'
  ]
}
autopkgtest [06:12:50]: test command1



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-n3
Source-Version: 1.12.2+~1.2.3+~1.10.4-1
Done: Yadd 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Dec 2021 06:30:38 +0100
Source: node-n3
Architecture: source
Version: 1.12.2+~1.2.3+~1.10.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1001732
Changes:
 node-n3 (1.12.2+~1.2.3+~1.10.4-1) unstable; urgency=medium
 .
   * Team upload
   * Embed typescript declarations
   * New upstream version 1.12.2+~1.2.3+~1.10.4
   * Add dependency to node-readable-stream (Closes: #1001732)
   * Drop nodejs dependency
Checksums-Sha1: 
 78c98416ef0d6f40573329aa3b21a2bc90e70cf7 2823 
node-n3_1.12.2+~1.2.3+~1.10.4-1.dsc
 043f779c8babb8fc2c8b40cb397ade1b2cebb9eb 4353 
node-n3_1.12.2+~1.2.3+~1.10.4.orig-Xqueue.tar.gz
 fd23d15fd7e47cf6d199d1f44ac5d6930cc50905 4281 
node-n3_1.12.2+~1.2.3+~1.10.4.orig-types-n3.tar.gz
 1c903e01709a7d85c684252e94da94026017525e 205234 
node-n3_1.12.2+~1.2.3+~1.10.4.orig.tar.gz
 27623764f319cf4e701e5a8216ba6b4c768369e9 5264 
node-n3_1.12.2+~1.2.3+~1.10.4-1.debian.tar.xz
Checksums-Sha256: 

Bug#1001732: marked as pending in node-n3

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-n3/-/commit/deb50e56f880db37eab6e83ac1d280fd72d2220b


Add dependency to node-readable-stream

Closes: #1001732


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1001732

Processed: Bug#1001732 marked as pending in node-n3

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1001732 [src:node-n3] node-n3: autopkgtest regression: Cannot find module 
'readable-stream'
Added tag(s) pending.

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

Bug#1001681: sight: FTBFS in unstable

[Pierre Gruet]

Hello,

On Tue, 14 Dec 2021 17:51:06 +0100 Flavien Bridault 
 wrote:

> Understood, I just wanted to avoid any overlap. I'll have a look asap. :)
>
>
> *Dr. Flavien BRIDAULT*
> Director of Software Development
> IRCAD France & IRCAD Africa
>
> flavien.brida...@ircad.fr 
> Tél. : +33 (0)3 88 119 201
> IRCAD France
> http://www.ircad.fr/
> http://www.ircad.africa/ 
>
> Suivez l'IRCAD sur Facebook
> 
>
> *IRCAD France*
> Hôpitaux Universitaires - 1, place de l'Hôpital - 67091 Strasbourg Cedex
> - FRANCE
>
> Le 14/12/2021 à 17:49, Andreas Tille a écrit :
> > Hi Flavien,
> >
> > Am Tue, Dec 14, 2021 at 04:13:26PM +0100 schrieb Flavien Bridault:
> >> Thanks for the notice.
> >>
> >> This comes from DCMTK. Maybe an API change or a move of a header. 
Do you

> >> want me to have a look ?
> > I guess Steve will be very happy if you can have a look. As far as
> > I know he is not a medical imaging expert and has no interest in
> > debugging DCMTK.
> >
> > Thanks a lot for checking
> >
> > Andreas.
> >

I found the issue, which is OFIterator shall now be instantiated as 
OFListIterator(T). With this change, the package builds.


Unless you ask me otherwise, I shall make an upload with this change 
tonight.



Best wishes,

--
Pierre

Bug#1001744: cura: Cura does not start

[Sebastián Lacuesta]

Package: cura
Version: 4.8-5
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: sebastianlacue...@gmail.com

Program does not start. Message in console is:

Traceback (most recent call last):
  File "/usr/bin/cura", line 32, in 
from cura.CrashHandler import CrashHandler
  File "/usr/lib/python3/dist-packages/cura/CrashHandler.py", line 27, in

from UM.Application import Application
  File "/usr/lib/python3/dist-packages/UM/Application.py", line 9, in 
from UM.Controller import Controller
  File "/usr/lib/python3/dist-packages/UM/Controller.py", line 3, in 
from UM.Scene.Iterator.DepthFirstIterator import DepthFirstIterator
  File "/usr/lib/python3/dist-
packages/UM/Scene/Iterator/DepthFirstIterator.py", line 3, in 
from UM.Scene.SceneNode import SceneNode
  File "/usr/lib/python3/dist-packages/UM/Scene/SceneNode.py", line 14, in

from UM.Mesh.MeshBuilder import MeshBuilder
  File "/usr/lib/python3/dist-packages/UM/Mesh/MeshBuilder.py", line 4, in

from UM.Mesh.MeshData import MeshData
  File "/usr/lib/python3/dist-packages/UM/Mesh/MeshData.py", line 16, in

import scipy.spatial
  File "/usr/lib/python3/dist-packages/scipy/spatial/__init__.py", line 96, in

from .kdtree import *
  File "/usr/lib/python3/dist-packages/scipy/spatial/kdtree.py", line 5, in

from .ckdtree import cKDTree, cKDTreeNode
  File "ckdtree.pyx", line 1, in init scipy.spatial.ckdtree
ValueError: numpy.ndarray size changed, may indicate binary incompatibility.
Expected 88 from C header, got 80 from PyObject


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (700, 'testing'), (699, 'unstable'), (698, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-2-amd64 (SMP w/16 CPU threads)
Locale: LANG=es_UY.UTF-8, LC_CTYPE=es_UY.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_UY:es
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cura depends on:
ii  cura-engine 1:4.8-1
ii  fdm-materials   4.8-1
ii  fonts-open-sans 1.11-2
ii  python3 3.9.8-1
ii  python3-certifi 2020.6.20-1
ii  python3-charon  4.8-1
ii  python3-cryptography3.4.8-1
ii  python3-pynest2d4.8.0-2+b1
ii  python3-pyqt5   5.15.6+dfsg-1+b1
ii  python3-pyqt5.qtopengl  5.15.6+dfsg-1+b1
ii  python3-requests2.25.1+dfsg-2
ii  python3-savitar 4.8-1+b2
ii  python3-serial  3.5~b0-1
ii  python3-shapely 1.8.0-1+b1
ii  python3-uranium 4.8-1
ii  qml-module-qt-labs-folderlistmodel  5.15.2+dfsg-8
ii  qml-module-qt-labs-settings 5.15.2+dfsg-8
ii  qml-module-qtqml-models25.15.2+dfsg-8
ii  qml-module-qtquick-controls 5.15.2-2
ii  qml-module-qtquick-controls25.15.2+dfsg-4
ii  qml-module-qtquick-dialogs  5.15.2-2
ii  uranium-plugins 4.8-1

Versions of packages cura recommends:
ii  python3-zeroconf  0.37.0-1

cura suggests no packages.

-- no debconf information

Bug#1001681: Fix coming soon

[Pierre Gruet]

Control: tags -1 pending

Hi,

OFIterator shall now be instantiated as OFListIterator(T), as stated 
in /usr/include/dcmtk/ofstd/oflist.h shipped by libdcmtk-dev.


Upload coming soon.

Cheers,

--
Pierre

Processed: Fix coming soon

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #1001681 [src:sight] sight: FTBFS in unstable
Added tag(s) pending.

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

Bug#1001729: marked as done (apache-log4j2: CVE-2021-45046: Incomplete fix for CVE-2021-44228 in certain non-default configurations)

[Debian Bug Tracking System]

Your message dated Wed, 15 Dec 2021 02:33:37 +
with message-id 
and subject line Bug#1001729: fixed in apache-log4j2 2.16.0-1
has caused the Debian Bug report #1001729,
regarding apache-log4j2: CVE-2021-45046: Incomplete fix for CVE-2021-44228 in 
certain non-default configurations
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.)


-- 
1001729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apache-log4j2
Version: 2.15.0-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://issues.apache.org/jira/browse/LOG4J2-3221
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 2.15.0-1~deb11u1
Control: found -1 2.15.0-1~deb10u1

Hi,

The following vulnerability was published for apache-log4j2. Strictly
speaking it's less severe as CVE-2021-44228 as it is an incomplete fix
for the former CVE in certain non-default configurations.

CVE-2021-45046[0]:
| It was found that the fix to address CVE-2021-44228 in Apache Log4j
| 2.15.0 was incomplete in certain non-default configurations. This
| could allows attackers with control over Thread Context Map (MDC)
| input data when the logging configuration uses a non-default Pattern
| Layout with either a Context Lookup (for example, $${ctx:loginId}) or
| a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious
| input data using a JNDI Lookup pattern resulting in a denial of
| service (DOS) attack. Log4j 2.15.0 restricts JNDI LDAP lookups to
| localhost by default. Note that previous mitigations involving
| configuration such as to set the system property
| `log4j2.noFormatMsgLookup` to `true` do NOT mitigate this specific
| vulnerability. Log4j 2.16.0 fixes this issue by removing support for
| message lookup patterns and disabling JNDI functionality by default.
| This issue can be mitigated in prior releases (2.16.0) by removing
| the JndiLookup class from the classpath (example: zip -q -d
| log4j-core-*.jar
| org/apache/logging/log4j/core/lookup/JndiLookup.class).


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-45046
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046
[1] https://issues.apache.org/jira/browse/LOG4J2-3221
[2] https://logging.apache.org/log4j/2.x/security.html#CVE-2021-45046
[3] https://www.openwall.com/lists/oss-security/2021/12/14/4

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: apache-log4j2
Source-Version: 2.16.0-1
Done: Markus Koschany 

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated apache-log4j2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Dec 2021 02:38:06 +0100
Source: apache-log4j2
Architecture: source
Version: 2.16.0-1
Distribution: unstable
Urgency: high
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Closes: 1001729
Changes:
 apache-log4j2 (2.16.0-1) unstable; urgency=high
 .
   * Team upload.
   * New upstream version 2.16.0.
 - Fix CVE-2021-45046:
   It was found that the fix to address CVE-2021-44228 in Apache Log4j
   2.15.0 was incomplete in certain non-default configurations. This could
   allow attackers with control over Thread Context Map (MDC) input data
   when the logging configuration uses a non-default Pattern Layout with
   either a Context Lookup (for example, $${ctx:loginId}) or a Thread
   Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data
   using a JNDI Lookup pattern resulting in a denial of service (DOS)
   attack.
   Thanks to Salvatore Bonaccorso for the report. (Closes: #1001729)
Checksums-Sha1:
 84452ae9920e07498d190f23dbb352de07cec021 3019 apache-log4j2_2.16.0-1.dsc
 

Bug#999041: libimage-base-bundle-perl: diff for NMU version 1.0.7-3.3

[Don Armstrong]

On Mon, 13 Dec 2021, gregor herrmann wrote:
> I've prepared an NMU for libimage-base-bundle-perl (versioned as 1.0.7-3.3) 
> and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.

Feel free to upload right away; thanks for fixing it. [I'm also happy if
the perl team takes over that package too.]

-- 
Don Armstrong  https://www.donarmstrong.com

Bug#998058: intel-compute-runtime: FTBFS due to 2 failing tests

[Andreas Beckmann]

Followup-For: Bug #998058

This is actually caused by the (transitive) B-D using different LLVM
versions: intel-graphics-compiler is built against llvm-12, while
intel-opencl-clang and spirv-llvm-translator are built against llvm-13.

This combination "only" causes some tests to fail, while other
combinations (e.g. using a intel-opencl-clang rebuilt with llvm-12) can
cause some compilation step to fail with "Aborted".

I'm working on updating the packaging of the whole stack s.t. the
dependencies only allow for a consistent llvm usage ;-)


Andreas

Bug#1001736: marked as done (typedload: autopkgtest regression: Library stubs not installed for "attr._make" (or incompatible with Python 3.7))

[Debian Bug Tracking System]

Your message dated Wed, 15 Dec 2021 00:08:00 +
with message-id 
and subject line Bug#1001736: fixed in typedload 2.14-2
has caused the Debian Bug report #1001736,
regarding typedload: autopkgtest regression: Library stubs not installed for 
"attr._make" (or incompatible with Python 3.7)
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.)


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

Source: typedload
Version: 2.14-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
typedload  from testing2.14-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Are you really 
trying to test with python3.7?


Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

https://ci.debian.net/data/autopkgtest/testing/amd64/t/typedload/17556987/log.gz

mypy --python-version=3.7 --config-file mypy.conf typedload
typedload/dataloader.py:683: error: Library stubs not installed for 
"attr._make" (or incompatible with Python 3.7)
typedload/dataloader.py:683: note: Hint: "python3 -m pip install 
types-attrs"
typedload/dataloader.py:683: note: (or run "mypy --install-types" to 
install all missing stub packages)
typedload/dataloader.py:683: note: See 
https://mypy.readthedocs.io/en/stable/running_mypy.html#missing-imports

Found 1 error in 1 file (checked 6 source files)
make: *** [Makefile:12: mypy] Error 1
autopkgtest [07:11:50]: test command1



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: typedload
Source-Version: 2.14-2
Done: Salvo 'LtWorf' Tomaselli 

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

Debian distribution maintenance software
pp.
Salvo 'LtWorf' Tomaselli  (supplier of updated typedload 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Dec 2021 00:37:30 +0100
Source: typedload
Architecture: source
Version: 2.14-2
Distribution: unstable
Urgency: high
Maintainer: Salvo 'LtWorf' Tomaselli 
Changed-By: Salvo 'LtWorf' Tomaselli 
Closes: 1001736
Changes:
 typedload (2.14-2) unstable; urgency=high
 .
   * Remove mypy tests since they periodically fail (Closes: #1001736)
Checksums-Sha1:
 9a5abd821ade3cf1eac88df53f8790b88a4b698d 2209 typedload_2.14-2.dsc
 aedb2055529f391a9e05609f17a460cd97a29511 13476 typedload_2.14-2.debian.tar.xz
 3005e3df81ee087c886102df3a68f1d39eb9c5d8 7098 typedload_2.14-2_amd64.buildinfo
Checksums-Sha256:
 0ec12004d83451e51e864219415650ce6f0f80ef1559ccd5810c4fd93bcdd9d4 2209 
typedload_2.14-2.dsc
 ea5548bf8c91d955044bba41049f36c9d94279892a609ff9301130cf94762444 13476 
typedload_2.14-2.debian.tar.xz
 8c5c4b8b75099838ac948216af13e7709fe019c8617ea2b4ccc62b0d17e00356 7098 
typedload_2.14-2_amd64.buildinfo
Files:
 03dd0c5b5607b809ef082167e3a7f74c 2209 python optional typedload_2.14-2.dsc
 9aac0f1037e90b628a8bb4ca7d45104b 13476 python optional 
typedload_2.14-2.debian.tar.xz
 21910c0ca2406a76b6bb3c36f2af7d3e 7098 python optional 
typedload_2.14-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEQnSLnnbYmXmeH74Us6fPDIAYhs8FAmG5LM4UHHRpcG9zY2hp
QHRpc2NhbGkuaXQACgkQs6fPDIAYhs+NeA//XwQh5TM+WaFwdjTTtUPU8PHao13B
TdocEhsuS40X/cM9MKzVlN6S/0oCkGcbk/2YEABMR/MP60WL/3f9BHul4bsa+V4g
c0TnAwPd5qmBG/U9RuqDORzM4BYUWyeTRPqlMHCAeQHyS9iFQtl2zAzK66NiAFUz

Bug#998255: marked as done (fbzx: FTBFS with GCC 11: error: reference to 'byte' is ambiguous)

[Debian Bug Tracking System]

Your message dated Tue, 14 Dec 2021 23:33:31 +
with message-id 
and subject line Bug#998255: fixed in fbzx 4.3.1-1
has caused the Debian Bug report #998255,
regarding fbzx: FTBFS with GCC 11: error: reference to 'byte' is ambiguous
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.)


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

Hi,

fbzx FTBFS with GCC 11 which defaults to -std=c++17:

g++ -c -O2 -Wdate-time -D_FORTIFY_SOURCE=2 `pkg-config --cflags sdl 
libpulse-simple alsa` -D D_SOUND_PULSE -D D_SOUND_ALSA -D D_SOUND_OSS -o 
cargador.o cargador.cpp
In file included from emulator.hh:22,
 from tape.hh:35,
 from computer.hh:26,
 from cargador.hh:20,
 from cargador.cpp:20:
z80free/Z80free.h:56:17: error: reference to 'byte' is ambiguous
   56 | byte F,A, C,B, E,D, L,H, IXl,IXh, IYl,IYh, P,S;
  | ^~~~
In file included from /usr/include/c++/11/bits/stl_algobase.h:61,
 from /usr/include/c++/11/bits/char_traits.h:39,
 from /usr/include/c++/11/string:40,
 from tape.hh:30,
 from computer.hh:26,
 from cargador.hh:20,
 from cargador.cpp:20:
/usr/include/c++/11/bits/cpp_type_traits.h:404:30: note: candidates are: 'enum 
class std::byte'
  404 |   enum class byte : unsigned char;
  |  ^~~~
In file included from emulator.hh:22,
 from tape.hh:35,
 from computer.hh:26,
 from cargador.hh:20,
 from cargador.cpp:20:
z80free/Z80free.h:28:23: note: 'typedef unsigned char byte'
   28 | typedef unsigned char byte;
  |   ^~~~
z80free/Z80free.h:75:9: error: reference to 'byte' is ambiguous
   75 | byteR;  /* Refresh */
  | ^~~~
In file included from /usr/include/c++/11/bits/stl_algobase.h:61,
 from /usr/include/c++/11/bits/char_traits.h:39,
 from /usr/include/c++/11/string:40,
 from tape.hh:30,
 from computer.hh:26,
 from cargador.hh:20,
 from cargador.cpp:20:
/usr/include/c++/11/bits/cpp_type_traits.h:404:30: note: candidates are: 'enum 
class std::byte'
  404 |   enum class byte : unsigned char;
  |  ^~~~
In file included from emulator.hh:22,
 from tape.hh:35,
 from computer.hh:26,
 from cargador.hh:20,
 from cargador.cpp:20:
z80free/Z80free.h:28:23: note: 'typedef unsigned char byte'
   28 | typedef unsigned char byte;
  |   ^~~~
[...]

Andreas


fbzx_3.1.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: fbzx
Source-Version: 4.3.1-1
Done: Santiago Vila 

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

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated fbzx 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: Tue, 14 Dec 2021 23:20:00 +0100
Source: fbzx
Architecture: source
Version: 4.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila 
Changed-By: Santiago Vila 
Closes: 978424 998255
Changes:
 fbzx (4.3.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * Update Homepage. Closes: #978424.
   * Should now build with GCC 11. Closes: #998255.
   * Add "Rules-Requires-Root: no".
   * Update debhelper compatibility version.
   * Standards-Version: 4.5.1 (no special changes for this).
Checksums-Sha1:
 b32e756c1e1448e0f25ea66652e29b5d78afd317 1459 fbzx_4.3.1-1.dsc
 99bac6b7c951cf36ab17b0c9e91b5d3df510435a 159216 

Bug#999082: offering to help with checksecurity

[Richard Lewis]

Hi,

I don't know how much attention this package gets, but i still use it

The repository at https://salsa.debian.org/rpil2/checksecurity/

includes a 'modernised' 3-line debian/rules (plus other things) that
would, i think, fix this bug.

That repository includes all the history that git-buildpackage could
import, and makes various other changes - i really wanted to fix
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994707 but . I ended
up doing more, including rewriting the main perl script in bash and
fixing some other inconsistencies and logfile locations - so you might
not want all of what is in there, but perhaps it is helpful.

If there is another/better way to help keep this package in Debian do
let me know -  as ever, i find myself not really sure how to help.

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Dec 2021 22:48:45 +
with message-id 
and subject line Bug#999105: fixed in xless 1.7-14.4
has caused the Debian Bug report #999105,
regarding xless: 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.)


-- 
999105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xless
Version: 1.7-14.3
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: xless
Source-Version: 1.7-14.4
Done: Bill Allombert 

We believe that the bug you reported is fixed in the latest version of
xless, 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.
Bill Allombert  (supplier of updated xless 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: Tue, 14 Dec 2021 22:13:04 +0100
Source: xless
Architecture: source
Version: 1.7-14.4
Distribution: unstable
Urgency: medium
Maintainer: Felipe Augusto van de Wiel (faw) 
Changed-By: Bill Allombert 
Closes: 965907 999105
Changes:
 xless (1.7-14.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/rules: Add missing targets (Closes: #999105)
   * debian/control: Depends on debhelper-compat (= 13) (Closes: #965907)
   * debian/compat: removed
Checksums-Sha1:
 ff5ba9a4ec5088d5195f079178a120628f072443 1788 xless_1.7-14.4.dsc
 5de3ec800260ed7e373bfd68914806d7e76ee4fd 6937 xless_1.7-14.4.diff.gz
 bf5bace15830a1f204afbb0d1756710d36d430ba 5430 xless_1.7-14.4_source.buildinfo
Checksums-Sha256:
 3147b162c730ba6b6b989ad3786251c4be49586ee1c35ed8a2181da047c2a88a 1788 
xless_1.7-14.4.dsc
 bac73c414097d50b23a011474326a8e01a234a7e079abdab8872ef4865fc4cc8 6937 
xless_1.7-14.4.diff.gz
 1a000d4958cc75173ec6733008c6f1749de23484449a0353e186b55f870b329d 5430 
xless_1.7-14.4_source.buildinfo
Files:
 b1e3c964b6563e9c97244b4d039ad8f9 1788 text optional xless_1.7-14.4.dsc
 e45b2ca60f582b0ede41a4213623cf76 6937 text optional xless_1.7-14.4.diff.gz
 2d75a65ef9a4e72543d69c45a1a2cfd4 5430 text optional 
xless_1.7-14.4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQgKOpASi6dgKxFMUjw58K0Ui44cFAmG5Gn8ACgkQjw58K0Ui
44fUVQ/9FALqx1Zj8lJ/tdvSS1Gc2NZKNC8CdApHdoNgObatrJJ9OhcZ4r7rJREN
s4OeCiZkrmUES6AsJ1E8MDsPDkaDXx3yTePfhZi4Iy22YYc33x3hCXzz5sU+Vq5y
UHmRBKxtdcPgNwwb2sxSH7bA5i6/nH3y9LKoxWCDVQZEBffuRm7cNl+Awf9GuGMd
Kt9Dtgiene6CgvS2IQHc1k11ehK+dAFZVVrN36BpAX7TH5TS8rq0HHmpzDUZxYJx
NyQM9yB/jqIULVc9FI1yAKqGG6u00YagTnw816+nnDOE1ZaT8zdOAD6CP1MMyyDl
nWkV82Y//T7nHgYoR3xUpJSQ40d4HSJUzAPUni4a0XvRvcljvnr7ifj5VBRjf/6v
UDIZmBMQ2CJ+pIgBGO6fQnoWgtMHnjkMtILnnzFqN/RyXYZ2awWCB0EvHasig/51
D03ZH+v744uIHSL4pu/NhKc4Q7or1z+A/zdfsX5d6FNdY8cQWZZbF3NiAAecaJyp
4RuIdMFL5K7EUF+e2w4ZDlCeQOy62Fh0jUWU2uJh/lcikzAozHFIseDN+vLeNXv8
SV97UuHzaZhRipgsK+uxPeznWRrfAsSIt4FfbZipLgX26L5St0vx4DCdxMOcMylr
KYSX+/hr7mSiW3rxHn2MYUTpX9LiIhz8FKdWu5mobe0SwzUWAr8=
=Z/NE
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#1001729: apache-log4j2: CVE-2021-45046: Incomplete fix for CVE-2021-44228 in certain non-default configurations

[Debian Bug Tracking System]

Processing control commands:

> owner -1 !
Bug #1001729 [src:apache-log4j2] apache-log4j2: CVE-2021-45046: Incomplete fix 
for CVE-2021-44228 in certain non-default configurations
Owner recorded as Markus Koschany .

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

Bug#1001729: apache-log4j2: CVE-2021-45046: Incomplete fix for CVE-2021-44228 in certain non-default configurations

[Markus Koschany]

Control: owner -1 !

Am Dienstag, dem 14.12.2021 um 21:37 +0100 schrieb Salvatore Bonaccorso:
> Source: apache-log4j2
> Version: 2.15.0-1
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> Forwarded: https://issues.apache.org/jira/browse/LOG4J2-3221
> X-Debbugs-Cc: car...@debian.org, Debian Security Team
> 
> Control: found -1 2.15.0-1~deb11u1
> Control: found -1 2.15.0-1~deb10u1
> 
> Hi,
> 
> The following vulnerability was published for apache-log4j2. Strictly
> speaking it's less severe as CVE-2021-44228 as it is an incomplete fix
> for the former CVE in certain non-default configurations.

Hi Salvatore,

I believe Stretch is not vulnerable to CVE-2021-45046 because I have removed
the JndiLookup class when I fixed CVE-2021-44228.

Shall I release a new DSA for CVE-2021-45046 or a regression update for CVE-
2021-44228 because of the incomplete upstream fix?

Regards,

Markus



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

Processed: Re: Ball fails its autopkgtest - how to properly deal with sip files?

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - pending
Bug #1001657 [src:ball] ball: binary-any FTBFS
Removed tag(s) pending.
> tags -1 + help
Bug #1001657 [src:ball] ball: binary-any FTBFS
Added tag(s) help.

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

Bug#998441: marked as done (reprozip: FTBFS on 2nd reproducible build)

[Debian Bug Tracking System]

Your message dated Tue, 14 Dec 2021 21:51:09 +
with message-id 
and subject line Bug#998441: fixed in reprozip 1.1-2
has caused the Debian Bug report #998441,
regarding reprozip: FTBFS on 2nd reproducible build
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.)


-- 
998441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: reprozip
Version: 1.0.16-1
Severity: normal
Tags: ftbfs bookworm sid
User: debian-pyt...@lists.debian.org
Usertags: python3.10

Hi Maintainer

As can be seen on reproducible builds [1], the second builds of
reprozip always fail.  I've copied what I hope is the relevant part of
the log below.

I've set the severity to normal for now, but it will be raised if the
failure happens on the buildds as well.

Regards
Graham


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


==
FAIL: test_get_files (test_reprozip.TestFiles)
--
Traceback (most recent call last):
  File "/build/2/reprozip-1.0.16/2nd/debian/tests/test_reprozip.py",
line 277, in test_get_files
self.assertEqualPaths(expected,
  File "/build/2/reprozip-1.0.16/2nd/debian/tests/test_reprozip.py",
line 255, in assertEqualPaths
self.assertEqual(self.make_paths(objs), second)
AssertionError: Items in the second set but not the first:
Path(b'/usr/lib64/ld-linux-x86-64.so.2')
Path(b'/usr/lib/x86_64-linux-gnu/ld-2.32.so')

==
FAIL: test_multiple_runs (test_reprozip.TestFiles)
--
Traceback (most recent call last):
  File "/build/2/reprozip-1.0.16/2nd/debian/tests/test_reprozip.py",
line 309, in test_multiple_runs
self.assertEqualPaths(expected,
  File "/build/2/reprozip-1.0.16/2nd/debian/tests/test_reprozip.py",
line 255, in assertEqualPaths
self.assertEqual(self.make_paths(objs), second)
AssertionError: Items in the second set but not the first:
Path(b'/usr/lib64/ld-linux-x86-64.so.2')
Path(b'/usr/lib/x86_64-linux-gnu/ld-2.32.so')

--
Ran 8 tests in 0.229s

FAILED (failures=2)
--- End Message ---
--- Begin Message ---
Source: reprozip
Source-Version: 1.1-2
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated reprozip 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: Tue, 14 Dec 2021 16:27:05 -0500
Source: reprozip
Architecture: source
Version: 1.1-2
Distribution: unstable
Urgency: high
Maintainer: Debian Science Maintainers 

Changed-By: Boyuan Yang 
Closes: 998441
Changes:
 reprozip (1.1-2) unstable; urgency=high
 .
   * Team upload.
   * debian/tests/test_reprozip.py: Tweak testsuite as suggested
 by upstream (Closes: #998441).
 + The divergence of testsuite needs more work, including
   unifying src:reprozip, src:reprounzip, etc.
Checksums-Sha1:
 46c9fdba8abe96157ac2b07423d94cb4c7116603 2201 reprozip_1.1-2.dsc
 1fbd38acc2fc4d31e7a40f230e53f8ae4d11cbe8 55060 reprozip_1.1.orig.tar.gz
 e64bd50655a300d8d74aff40065a4cec77e7dd95 7976 reprozip_1.1-2.debian.tar.xz
 50c6e2da57b636d6a6e68616807bc472bbc51dea 7960 reprozip_1.1-2_amd64.buildinfo
Checksums-Sha256:
 6514c13bc52424803ea4e9feb18b2fe2108c319fff0878081f268be21fe5650b 2201 
reprozip_1.1-2.dsc
 876801836ad8beb09aaf707cbb2a74d6b3eef72077a27c0cb04ba1f20a3fb26a 55060 
reprozip_1.1.orig.tar.gz
 78d0c77fcf1104eec180bff2f164d6b411ade2416d06b38061436ea39bf6279d 7976 
reprozip_1.1-2.debian.tar.xz
 4b073e15f97ddd8d8d433b601f7f20e7ad7493ff78da2176bb11e9913dfb54c6 7960 
reprozip_1.1-2_amd64.buildinfo
Files:
 d8aa896de8f8820c5369e4e16667c02c 2201 science optional reprozip_1.1-2.dsc
 680cf545209397a5a1da366c853541f5 55060 science optional 
reprozip_1.1.orig.tar.gz
 

Bug#997845: Your mail

[nick black]

ought i upload a -4 with a changelog entry marking the bug
closed? i didn't mark it closed in the changelog because i
explicitly wanted the bug left open.

sorry for any confusion -- i'm certainly not trying to work
around this issue in the long term by reducing testing =]. i
just know that it's not going to be fixed until growlight 1.2.38
moves to unstable from experimental, which requires notcurses3,
which is in the NEW queue awaiting FTPteam approval.

at that point, i'll be reenabling the test. so i don't consider
1.2.37-3 as having "closed" the bug whatsoever. but it ought be
closed shortly after notcurses3 hits unstable =].

Processed: bug 997189 is forwarded to https://github.com/octo/liboping/issues/62

[Debian Bug Tracking System]

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

> forwarded 997189 https://github.com/octo/liboping/issues/62
Bug #997189 [src:liboping] liboping: FTBFS: oping.c:1159:25: error: format not 
a string literal and no format arguments [-Werror=format-security]
Set Bug forwarded-to-address to 'https://github.com/octo/liboping/issues/62'.
> thanks
Stopping processing here.

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

Bug#997845: Your mail

[nick black]

you are correct in all of your assumptions =].


signature.asc
Description: PGP signature

Processed: Re: Bug#999320: libwww-indexparser-perl: missing required debian/rules targets build-arch and/or build-indep

[Debian Bug Tracking System]

Processing control commands:

> tags 999320 pending
Bug #999320 [src:libwww-indexparser-perl] libwww-indexparser-perl: missing 
required debian/rules targets build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999320: libwww-indexparser-perl: missing required debian/rules targets build-arch and/or build-indep

[Christoph Biedl]

Control: tags 999320 pending

> 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

After a brief exchange with James Bromberger: I will take over
maintainership for this package. Upload will take a few days, please be
patient.

Christoph


signature.asc
Description: PGP signature

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Dec 2021 21:22:22 +
with message-id 
and subject line Bug#998914: fixed in lostirc 0.4.6-4.3
has caused the Debian Bug report #998914,
regarding lostirc: 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.)


-- 
998914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lostirc
Version: 0.4.6-4.2
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: lostirc
Source-Version: 0.4.6-4.3
Done: Bill Allombert 

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

Debian distribution maintenance software
pp.
Bill Allombert  (supplier of updated lostirc 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, 15 Nov 2021 23:40:00 +0100
Source: lostirc
Architecture: source
Version: 0.4.6-4.3
Distribution: unstable
Urgency: medium
Maintainer: Martin Braure de Calignon 
Changed-By: Bill Allombert 
Closes: 998914
Changes:
 lostirc (0.4.6-4.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: switch to debhelper-compat (= 13)
   * debian/compat: removed
   * debian/rules: add missing targets (Closes: #998914)
Checksums-Sha1:
 8f91ef92410c66c70ce0e6def6556c047ea64943 1888 lostirc_0.4.6-4.3.dsc
 c968011762aa39cd1366784be5469ab5960018d7 12782 lostirc_0.4.6-4.3.diff.gz
 ea465d517e275162dd899a85951d088ff3dd5b18 5951 
lostirc_0.4.6-4.3_source.buildinfo
Checksums-Sha256:
 343bdf55ae118295867e5c2c0ea39cac805de13f5f2cdfb3c24822dbe7e78b73 1888 
lostirc_0.4.6-4.3.dsc
 e1e4c5e9d8992c5ae3af6324e157a9c46c8ed161b39e9419623df22a91f90269 12782 
lostirc_0.4.6-4.3.diff.gz
 4dda01a22b400fa9341eee14e1d3f1f764ae51284a250dd6137cf6458ea43050 5951 
lostirc_0.4.6-4.3_source.buildinfo
Files:
 84052c7e8f24595f399c8e504572199a 1888 net optional lostirc_0.4.6-4.3.dsc
 adb6c67c93bdd1c522a490483d18e6af 12782 net optional lostirc_0.4.6-4.3.diff.gz
 9b0532bbb2bdd7debcc360c34a0d0412 5951 net optional 
lostirc_0.4.6-4.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQgKOpASi6dgKxFMUjw58K0Ui44cFAmG5Br0ACgkQjw58K0Ui
44cTbQ//ehJowEIqd4M+42nXDxyIu1ctQFI+0+DnlbmOttpOw6dT6me6yc9SxYky
583hvkgGanjCFJpbFpBqeeEpacz5djBWda3W/rpscjP5Za4bj7JcsVXfD0eFfsYr
1dTze7D06zdmLnUPN9eY2M5qN0l5A6oF4ZMxd50kwWYpMhsMpghlZbKagvb6rha+
iSm+ovgSdsNs/TsiXhAbaVFcvXDplygVmNDgLidfm0oYwjCMhh1UUAoYxzaxPHHd
snUE8mdkTzpqs8D66Xm+uGvTMZjQthDkQ7/lrleZDquuI3bgOnIsByxGvgQi7XxX
bBhmj/3OX5wJpN8K+RmzwS0wSI3OX0cZz+VSvxlsVeUNH3/942tANp34gJP9/9lc
tyP4+ZVnI1CEsLO0shS76vgSiqWXljgka2nXJqEAyQx7uugEew2TYfcKH0DpyVGo
8+DFy7xqlEw7EI/R15d/ck74/xnKWgpEC/M5KbK90tnZLH8PBnd3zijvlyJGZQub
vJWuQLbnscV7rEYO6/nR5hjREWbKF4g70K0NHRVgqHq9bK6EUsJLzf7z9wrDeN3n
H58+5yXW0fKE95VtMs439DRHErca0mZ14GdmhLuiIj8HKn84AowDLJeBE91EjF+Y
BDnCsesJCok4kDtUZPKTBQbycSFWxCfeVLdBuRzNA62uQCcOQSA=
=5+B0
-END PGP SIGNATURE End Message ---

Bug#997845: Your mail

[Paul Gevers]

Control: fixed -1 1.2.37-3

Hi Nick

On Mon, 25 Oct 2021 22:43:44 -0400 nick black  
wrote:

i'm not sure whether the "forwarded" tag applies in this case,
but i've created an upstream bug (i am the upstream author) at
https://github.com/dankamongmen/growlight/issues/153.


I understand you uploaded -3 without the test to have it not removed 
from testing. For the migration to happen, this bug should not cause 
regressions in testing and as such, the version you want to migrate 
should be marked as fixed (doing so now). I'm *not* closing the bug as I 
assume you want to track adding the test back and properly close it with 
the version that fixes the bug.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Your mail

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.2.37-3
Bug #997845 [src:growlight] growlight: autopkgtest regression: log repeats 
until it times out
Marked as fixed in versions growlight/1.2.37-3.

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

Bug#1001736: typedload: autopkgtest regression: Library stubs not installed for "attr._make" (or incompatible with Python 3.7)

[Paul Gevers]

Source: typedload
Version: 2.14-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
typedload  from testing2.14-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Are you really 
trying to test with python3.7?


Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

https://ci.debian.net/data/autopkgtest/testing/amd64/t/typedload/17556987/log.gz

mypy --python-version=3.7 --config-file mypy.conf typedload
typedload/dataloader.py:683: error: Library stubs not installed for 
"attr._make" (or incompatible with Python 3.7)
typedload/dataloader.py:683: note: Hint: "python3 -m pip install 
types-attrs"
typedload/dataloader.py:683: note: (or run "mypy --install-types" to 
install all missing stub packages)
typedload/dataloader.py:683: note: See 
https://mypy.readthedocs.io/en/stable/running_mypy.html#missing-imports

Found 1 error in 1 file (checked 6 source files)
make: *** [Makefile:12: mypy] Error 1
autopkgtest [07:11:50]: test command1



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1001735: node-trust-keyto: autopkgtest regression: Cannot find module '@trust/keyto'

[Paul Gevers]

Source: node-trust-keyto
Version: 2.0.0~alpha1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
node-trust-keyto   from testing2.0.0~alpha1-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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=node-trust-keyto

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-trust-keyto/17556375/log.gz

internal/modules/cjs/loader.js:818
  throw err;
  ^

Error: Cannot find module '@trust/keyto'
Require stack:
- /tmp/autopkgtest-lxc.wqzautxi/downtmp/build.Vrg/src/[eval]
at Function.Module._resolveFilename 
(internal/modules/cjs/loader.js:815:15)

at Function.Module._load (internal/modules/cjs/loader.js:667:27)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at [eval]:1:1
at Script.runInThisContext (vm.js:120:18)
at Object.runInThisContext (vm.js:309:38)
at Object. ([eval]-wrapper:10:26)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at evalScript (internal/process/execution.js:94:25) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ 
'/tmp/autopkgtest-lxc.wqzautxi/downtmp/build.Vrg/src/[eval]' ]

}
autopkgtest [06:13:32]: test command1



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1001734: golang-github-rogpeppe-go-internal: autopkgtest regression: Reversed (or previously applied) patch detected!

[Paul Gevers]

Source: golang-github-rogpeppe-go-internal
Version: 1.8.0-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of golang-github-rogpeppe-go-internal the 
autopkgtest of golang-github-rogpeppe-go-internal fails in testing when 
that autopkgtest is run with the binary packages of 
golang-github-rogpeppe-go-internal from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
golang-github-rogpeppe-go-internal from testing1.8.0-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 to testing [1]. Can 
you please investigate the situation and fix it?


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=golang-github-rogpeppe-go-internal


https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-rogpeppe-go-internal/17556363/log.gz

   debian/rules override_dh_auto_test
make[1]: Entering directory 
'/tmp/autopkgtest-lxc.k67h7x0n/downtmp/autopkgtest_tmp'

patch -N -p1 -i debian/0001-Allow-TestSimple-cover-to-PASS.patch
patching file 
_build/src/github.com/rogpeppe/go-internal/testscript/testscript.go

Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file 
_build/src/github.com/rogpeppe/go-internal/testscript/testscript.go.rej
make[1]: Leaving directory 
'/tmp/autopkgtest-lxc.k67h7x0n/downtmp/autopkgtest_tmp'

make[1]: *** [debian/rules:9: override_dh_auto_test] Error 1
make: *** [debian/rules:4: build] Error 2
autopkgtest [06:12:32]: test dh-golang-autopkgtest



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1001733: dh-sysuser: autopkgtest failure: FAILED: user _runit-log exists after purge or environment is not clean

[Paul Gevers]

Source: dh-sysuser
Version: 1.3.6+really1.4.0
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package dh-sysuser, great. 
However, it fails. Currently this failure is blocking the migration to 
testing [1]. Can you please investigate the situation and fix it?


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

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=dh-sysuser

https://ci.debian.net/data/autopkgtest/testing/amd64/d/dh-sysuser/17221501/log.gz

OK: user libvirtdbus succesfully created
Reading package lists...
Building dependency tree...
Reading state information...
Package 'libvirt-dbus' is not installed, so not removed
The following packages were automatically installed and are no longer 
required:
  adwaita-icon-theme alsa-topology-conf alsa-ucm-conf at-spi2-core 
bsd-mailx

  dconf-gsettings-backend dconf-service dmeventd dns-root-data dnsmasq-base
  exim4-base exim4-config exim4-daemon-light fontconfig fontconfig-config
  fonts-dejavu-core gettext-base glib-networking glib-networking-common
  glib-networking-services gsettings-desktop-schemas gstreamer1.0-libav
  gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-x
  gtk-update-icon-cache hicolor-icon-theme i965-va-driver ibverbs-providers
  intel-media-va-driver iptables ipxe-qemu iso-codes libaa1 libaacs0 
libaio1

  libaom3 libasound2 libasound2-data libass9 libasyncns0 libatk-bridge2.0-0
  libatk1.0-0 libatk1.0-data libatspi2.0-0 libavahi-client3
  libavahi-common-data libavahi-common3 libavc1394-0 libavcodec58 
libavfilter7

  libavformat58 libavutil56 libbdplus0 libblas3 libbluray2
  libboost-iostreams1.74.0 libboost-thread1.74.0 libbrlapi0.8 libbs2b0
  libcaca0 libcacard0 libcairo-gobject2 libcairo2 libcapstone4 
libcdparanoia0

  libchromaprint1 libcodec2-0.9 libcolord2 libcups2 libdatrie1 libdav1d5
  libdaxctl1 libdconf1 libdecor-0-0 libdecor-0-plugin-1-cairo libdeflate0
  libdevmapper-event1.02.1 libdrm-amdgpu1 libdrm-common libdrm-intel1
  libdrm-nouveau2 libdrm-radeon1 libdrm2 libdv4 libdw1 libepoxy0
  libevent-2.1-7 libexecs0 libfdt1 libflac8 libflite1 libfontconfig1
  libfreetype6 libfribidi0 libfuse2 libfuse3-3 libgbm1 libgdk-pixbuf-2.0-0
  libgdk-pixbuf2.0-bin libgdk-pixbuf2.0-common libgfapi0 libgfortran5
  libgfrpc0 libgfxdr0 libgl1 libgl1-mesa-dri libglapi-mesa libglusterfs0
  libglvnd0 libglx-mesa0 libglx0 libgme0 libgnutls-dane0 libgomp1
  libgraphite2-3 libgsm1 libgstreamer-plugins-base1.0-0 libgstreamer1.0-0
  libgtk-3-0 libgtk-3-bin libgtk-3-common libgudev-1.0-0 libharfbuzz0b
  libibverbs1 libidn12 libiec61883-0 libigdgmm11 libip6tc2 libiscsi7
  libjack-jackd2-0 libjansson4 libjbig0 libjpeg62-turbo liblapack3 
liblcms2-2

  liblilv-0-0 libllvm12 liblockfile-bin liblockfile1 liblvm2cmd2.03 libmfx1
  libmp3lame0 libmpg123-0 libmysofa1 libndctl6 libnetfilter-conntrack3
  libnfnetlink0 libnfs13 libnftables1 libnftnl11 libnl-3-200 
libnl-route-3-200
  libnorm1 libnspr4 libnss3 libnuma1 libogg0 libopenjp2-7 libopenmpt0 
libopus0
  liborc-0.4-0 libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 
libpcap0.8
  libpciaccess0 libpcsclite1 libpgm-5.3-0 libpixman-1-0 libpmem1 
libpng16-16
  libpocketsphinx3 libpopt0 libpostproc55 libproxy1v5 libpulse0 
libquadmath0

  librabbitmq4 librados2 libraw1394-11 librbd1 librdmacm1 librsvg2-2
  librsvg2-common librubberband2 libsamplerate0 libsdl2-2.0-0
  libsensors-config libsensors5 libserd-0-0 libshine3 libshout3 libslang2
  libslirp0 libsnappy1v5 libsndfile1 libsodium23 libsord-0-0 libsoup2.4-1
  libsoxr0 libspeex1 libsphinxbase3 libspice-server1 libsratom-0-0
  libsrt1.4-gnutls libssh-4 libssh-gcrypt-4 libswresample3 libswscale5
  libtag1v5 libtag1v5-vanilla libthai-data libthai0 libtheora0 libtiff5
  libtwolame0 libudfread0 libunbound8 libunwind8 liburing1 libusb-1.0-0
  libusbredirparser1 libv4l-0 libv4lconvert0 libva-drm2 libva-x11-2 libva2
  libvdeplug2 libvdpau-va-gl1 libvdpau1 libvidstab1.1 libvirglrenderer1
  libvirt-clients libvirt-daemon libvirt-daemon-config-network
  libvirt-daemon-config-nwfilter libvirt-daemon-driver-lxc
  libvirt-daemon-driver-qemu libvirt-daemon-driver-vbox
  libvirt-daemon-driver-xen libvirt-daemon-system
  libvirt-daemon-system-systemd libvirt-glib-1.0-0 libvirt-glib-1.0-data
  libvirt0 libvisual-0.4-0 libvorbis0a libvorbisenc2 libvorbisfile3 libvpx7
  libvte-2.91-0 libvte-2.91-common libvulkan1 libwavpack1 
libwayland-client0
  libwayland-cursor0 libwayland-egl1 libwayland-server0 libwebp6 
libwebpmux3

  libx11-6 libx11-data libx11-xcb1 libx264-160 libx265-199 libxau6
  libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0 libxcb-present0 libxcb-randr0
  libxcb-render0 libxcb-shm0 libxcb-sync1 libxcb-xfixes0 libxcb1
  libxcomposite1 libxcursor1 libxdamage1 

Bug#1001657: Ball fails its autopkgtest - how to properly deal with sip files?

[Andreas Tille]

Control: tags -1 pending

I've fixed the dh_installdocs issue in Git[1] but wanted to solve
the autopkgtest issue as well.  At first I provided the proper
module name[2] which brought me back to the old discussion here:

Am Thu, Sep 23, 2021 at 11:59:50PM +0200 schrieb Étienne Mollier:
> Hi Nilesh,
> 
> Nilesh Patra, on 2021-09-23:
> > The problems that I see on a quick look are:
> > 1) the import name is wrong, it should be BALL instead of ball
> > this is trivial to fix
> > 2) This is the bigger problem. python3-ball is broken, it needed to compile
> > the .sip files, to make an so lib
> > and import that. This is not happening. Probably fixing this is also not
> > hard, just passing SIP_LIBRARY with cmake
> > might do the trick, but again no time.
> > 
> > Also, my understanding is that it was always broken, and has got barely
> > anything to do with my bug fix.
> > Since I am very very short on time, @Etienne, could you please fix this and
> > dput?
> 
> Thanks for drawing my attention on this!  I can have a look,
> sure, although I don't guarantee this will be solved this
> evening; it looks like quite the machine cycles hog.  It is the
> first time I hear about sip, it looks kinda similar to swig.
> Will run an overnight build to see if I can manage to do
> something with the SIP_LIBRARY environment variable; thanks for
> the tip!

For whatever reason python3-sip did not ended up in the package
dependencies. Thus I added it explicitly[3].  But the autopkg issue
remains[4]:

autopkgtest [17:09:54]: test autodep8-python3: [---
Testing with python3.9:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/BALL.py", line 5, in 
from BALLCore import *
ModuleNotFoundError: No module named 'BALLCore'
autopkgtest [17:09:55]: test autodep8-python3: ---]

and we have the sip file 

   /usr/lib/python3/dist-packages/BALL/BALLCore.sip

I have no idea why this is not found.

Kind regards

   Andreas.


[1] 
https://salsa.debian.org/med-team/ball/-/commit/451bb880214e04c1042fabd19acef30fbf1ede78
[2] 
https://salsa.debian.org/med-team/ball/-/commit/129417031797d553a3f87a9de5abfd05d6e848c0
[3] 
https://salsa.debian.org/med-team/ball/-/commit/df9bd210dd6c172563583bc14278cf3bbc0f047b
[4] https://salsa.debian.org/med-team/ball/-/jobs/2278393

-- 
http://fam-tille.de

Processed: Re: Ball fails its autopkgtest - how to properly deal with sip files?

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #1001657 [src:ball] ball: binary-any FTBFS
Added tag(s) pending.

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

Bug#1001732: node-n3: autopkgtest regression: Cannot find module 'readable-stream'

[Paul Gevers]

Source: node-n3
Version: 1.12.1+~1.2.3-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
node-n3from testing1.12.1+~1.2.3-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Are you 
missing a (test) dependency?


Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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=node-n3

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

internal/modules/cjs/loader.js:818
  throw err;
  ^

Error: Cannot find module 'readable-stream'
Require stack:
- /usr/share/nodejs/n3/lib/N3Store.js
- /usr/share/nodejs/n3/lib/index.js
- /tmp/autopkgtest-lxc.abtfpkoq/downtmp/build.2gd/src/[eval]
at Function.Module._resolveFilename 
(internal/modules/cjs/loader.js:815:15)

at Function.Module._load (internal/modules/cjs/loader.js:667:27)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. (/usr/share/nodejs/n3/lib/N3Store.js:10:23)
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)
at Module.require (internal/modules/cjs/loader.js:887:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
'/usr/share/nodejs/n3/lib/N3Store.js',
'/usr/share/nodejs/n3/lib/index.js',
'/tmp/autopkgtest-lxc.abtfpkoq/downtmp/build.2gd/src/[eval]'
  ]
}
autopkgtest [06:12:50]: test command1



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1001729: apache-log4j2: CVE-2021-45046: Incomplete fix for CVE-2021-44228 in certain non-default configurations

[Salvatore Bonaccorso]

Source: apache-log4j2
Version: 2.15.0-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://issues.apache.org/jira/browse/LOG4J2-3221
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 2.15.0-1~deb11u1
Control: found -1 2.15.0-1~deb10u1

Hi,

The following vulnerability was published for apache-log4j2. Strictly
speaking it's less severe as CVE-2021-44228 as it is an incomplete fix
for the former CVE in certain non-default configurations.

CVE-2021-45046[0]:
| It was found that the fix to address CVE-2021-44228 in Apache Log4j
| 2.15.0 was incomplete in certain non-default configurations. This
| could allows attackers with control over Thread Context Map (MDC)
| input data when the logging configuration uses a non-default Pattern
| Layout with either a Context Lookup (for example, $${ctx:loginId}) or
| a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious
| input data using a JNDI Lookup pattern resulting in a denial of
| service (DOS) attack. Log4j 2.15.0 restricts JNDI LDAP lookups to
| localhost by default. Note that previous mitigations involving
| configuration such as to set the system property
| `log4j2.noFormatMsgLookup` to `true` do NOT mitigate this specific
| vulnerability. Log4j 2.16.0 fixes this issue by removing support for
| message lookup patterns and disabling JNDI functionality by default.
| This issue can be mitigated in prior releases (2.16.0) by removing
| the JndiLookup class from the classpath (example: zip -q -d
| log4j-core-*.jar
| org/apache/logging/log4j/core/lookup/JndiLookup.class).


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-45046
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046
[1] https://issues.apache.org/jira/browse/LOG4J2-3221
[2] https://logging.apache.org/log4j/2.x/security.html#CVE-2021-45046
[3] https://www.openwall.com/lists/oss-security/2021/12/14/4

Regards,
Salvatore

Bug#1001728: python-aiohttp breaks dask autopkgtest: 'async_timeout' has no attribute 'Timeout'

[Paul Gevers]

Source: python-aiohttp
Control: found -1 python-aiohttp/3.8.1-3
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks

Dear maintainer(s),

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


   passfail
python-aiohttp from testing3.8.1-3
dask   from testing2021.09.1+dfsg-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. To me it looks 
like this is all python-aiohttp code path, so I *suspect* the issue is 
with python-aiohttp itself.


Currently this regression is blocking the migration of python-aiohttp to 
testing [1].


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=python-aiohttp

https://ci.debian.net/data/autopkgtest/testing/amd64/d/dask/17553992/log.gz

Testing with python3.9:
= test session starts 
==
platform linux -- Python 3.9.9, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 
-- /usr/bin/python3.9

cachedir: .pytest_cache
rootdir: /tmp/autopkgtest-lxc.eom7aakg/downtmp/autopkgtest_tmp
collecting ... collected 9095 items / 1 error / 3 deselected / 21 
skipped / 9070 selected


 ERRORS 

__ ERROR collecting bytes/tests/test_http.py 
___

/usr/lib/python3/dist-packages/dask/bytes/tests/test_http.py:18: in 
aiohttp = pytest.importorskip("aiohttp")
/usr/lib/python3/dist-packages/aiohttp/__init__.py:6: in 
from .client import (
/usr/lib/python3/dist-packages/aiohttp/client.py:36: in 
from . import hdrs, http, payload
/usr/lib/python3/dist-packages/aiohttp/http.py:7: in 
from .http_parser import (
/usr/lib/python3/dist-packages/aiohttp/http_parser.py:29: in 
from .helpers import NO_EXTENSIONS, BaseTimerContext
/usr/lib/python3/dist-packages/aiohttp/helpers.py:732: in 
def ceil_timeout(delay: Optional[float]) -> async_timeout.Timeout:
E   AttributeError: module 'async_timeout' has no attribute 'Timeout'


OpenPGP_signature
Description: OpenPGP digital signature

Processed: python-aiohttp breaks dask autopkgtest: 'async_timeout' has no attribute 'Timeout'

[Debian Bug Tracking System]

Processing control commands:

> found -1 python-aiohttp/3.8.1-3
Bug #1001728 [src:python-aiohttp] python-aiohttp breaks dask autopkgtest: 
'async_timeout' has no attribute 'Timeout'
Marked as found in versions python-aiohttp/3.8.1-3.

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

Processed: apache-log4j2: CVE-2021-45046: Incomplete fix for CVE-2021-44228 in certain non-default configurations

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.15.0-1~deb11u1
Bug #1001729 [src:apache-log4j2] apache-log4j2: CVE-2021-45046: Incomplete fix 
for CVE-2021-44228 in certain non-default configurations
Marked as found in versions apache-log4j2/2.15.0-1~deb11u1.
> found -1 2.15.0-1~deb10u1
Bug #1001729 [src:apache-log4j2] apache-log4j2: CVE-2021-45046: Incomplete fix 
for CVE-2021-44228 in certain non-default configurations
Marked as found in versions apache-log4j2/2.15.0-1~deb10u1.

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

Processed: python-aiohttp breaks postfix-mta-sts-resolver autopkgtest: Job for postfix-mta-sts-resolver.service failed

[Debian Bug Tracking System]

Processing control commands:

> found -1 python-aiohttp/3.8.1-3
Bug #1001727 [src:python-aiohttp, src:postfix-mta-sts-resolver] python-aiohttp 
breaks postfix-mta-sts-resolver autopkgtest: Job for 
postfix-mta-sts-resolver.service failed
Marked as found in versions python-aiohttp/3.8.1-3.
> found -1 postfix-mta-sts-resolver/1.0.0-4
Bug #1001727 [src:python-aiohttp, src:postfix-mta-sts-resolver] python-aiohttp 
breaks postfix-mta-sts-resolver autopkgtest: Job for 
postfix-mta-sts-resolver.service failed
Marked as found in versions postfix-mta-sts-resolver/1.0.0-4.

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

Bug#1001614: odil: FTBFS on armhf: 91 - MoveSCU_Move (Failed)

[Andreas Tille]

Hi Julien,

Am Tue, Dec 14, 2021 at 07:02:40PM +0100 schrieb Julien Lamy:
> Hi list,
> I tried to solve #1001614 but I can't reproduce the error: on an armhf box,
> sbuild environment targeting sid, no error occurs. Since the build error is
> supposed to happen during network-related unit tests in which I'm starting a
> server listening on a fixed port of the loopback interface, I'm suspecting
> that something specific to the build environment interferes.
> 
> I can think of three possible ways to go:
> 1. Skip all network-related tests. The networking tests are run during CI
> upstream, but on x86 only.

This is definitely a valid way to go.

> 2. Have the server listen on a random port. The error may however pop back
> randomly.
> 3. Restrict the architectures to avoid armhf.

I personally think that this software is not used on armhf.  Well,
sometimes those rarely used architectures are some means to detect
some hidden issues.  But if you can be sure that's not the case
the solution is also valid in my eyes.
 
> Which one would you advise? Is there a fourth one, since none of those seem
> good?

May be I did not understood 2. correctly but 1. and 3. are fine for
me.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#1000169: marked as done (gufw: Does not start)

[Debian Bug Tracking System]

Your message dated Tue, 14 Dec 2021 20:34:11 +
with message-id 
and subject line Bug#1000169: fixed in gui-ufw 20.04.1-3
has caused the Debian Bug report #1000169,
regarding gufw: Does not start
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.)


-- 
1000169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gufw
Version: 20.04.1-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: witold.bary...@gmail.com

It is broken:

root@debian:~# gufw
/usr/bin/gufw: line 2: [: =: unary operator expected
ls: cannot access '/usr/lib/python*/site-packages/gufw/gufw.py': No such file 
or directory
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: 
assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_modifier_mask: 
assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: 
assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:3421888): Gtk-CRITICAL **: 21:47:05.154: 
_gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: 
assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_modifier_mask: 
assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: 
assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:3421888): Gtk-CRITICAL **: 21:47:05.154: 
_gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: 
assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_modifier_mask: 
assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: 
assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:3421888): Gtk-CRITICAL **: 21:47:05.154: 
_gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: 
assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_modifier_mask: 
assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: 
assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:3421888): Gtk-CRITICAL **: 21:47:05.154: 
_gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: 
assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_modifier_mask: 
assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: 
assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:3421888): Gtk-CRITICAL **: 21:47:05.154: 
_gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: 
assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_modifier_mask: 
assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: 
assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:3421888): Gtk-CRITICAL **: 21:47:05.154: 
_gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: 
assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_modifier_mask: 
assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: 
assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:3421888): Gtk-CRITICAL **: 21:47:05.154: 
_gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: 
assertion 'GDK_IS_DISPLAY (display)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_modifier_mask: 
assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3421888): Gdk-CRITICAL **: 

Bug#1001727: python-aiohttp breaks postfix-mta-sts-resolver autopkgtest: Job for postfix-mta-sts-resolver.service failed

[Paul Gevers]

Source: python-aiohttp, postfix-mta-sts-resolver
Control: found -1 python-aiohttp/3.8.1-3
Control: found -1 postfix-mta-sts-resolver/1.0.0-4
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 python-aiohttp the autopkgtest of 
postfix-mta-sts-resolver fails in testing when that autopkgtest is run 
with the binary packages of python-aiohttp from unstable. It passes when 
run with only packages from testing. In tabular form:


 passfail
python-aiohttp   from testing3.8.1-3
postfix-mta-sts-resolver from testing1.0.0-4
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 python-aiohttp to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


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

Paul

[1] https://qa.debian.org/excuses.php?package=python-aiohttp

https://ci.debian.net/data/autopkgtest/testing/amd64/p/postfix-mta-sts-resolver/17553994/log.gz

Updating certificates in /etc/ssl/certs...
1 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Job for postfix-mta-sts-resolver.service failed because the control 
process exited with error code.
See "systemctl status postfix-mta-sts-resolver.service" and "journalctl 
-xeu postfix-mta-sts-resolver.service" for details.

Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.e660v08n/downtmp/build.EcE/src/debian/tests/run", 
line 75, in 

main()
  File 
"/tmp/autopkgtest-lxc.e660v08n/downtmp/build.EcE/src/debian/tests/run", 
line 62, in main

set_up()
  File 
"/tmp/autopkgtest-lxc.e660v08n/downtmp/build.EcE/src/debian/tests/run", 
line 11, in set_up

proc.check_returncode()
  File "/usr/lib/python3.9/subprocess.py", line 460, in check_returncode
raise CalledProcessError(self.returncode, self.args, self.stdout,
subprocess.CalledProcessError: Command '['tests/install.debian.sh']' 
returned non-zero exit status 1.

autopkgtest [04:02:53]: test run



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1001726: node-mqtt-packet breaks node-mqtt-connection autopkgtest: Invalid header flag bits, must be 0x2 for pubrel

[Paul Gevers]

Source: node-mqtt-packet, node-mqtt-connection
Control: found -1 node-mqtt-packet/7.1.1-1
Control: found -1 node-mqtt-connection/4.1.0-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 node-mqtt-packet the autopkgtest of 
node-mqtt-connection fails in testing when that autopkgtest is run with 
the binary packages of node-mqtt-packet from unstable. It passes when 
run with only packages from testing. In tabular form:


   passfail
node-mqtt-packet   from testing7.1.1-1
node-mqtt-connection   from testing4.1.0-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 node-mqtt-packet 
to testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


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

Paul

[1] https://qa.debian.org/excuses.php?package=node-mqtt-packet

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-mqtt-connection/17553966/log.gz

# Using package.json
# Node module name is mqtt-connection
# Build files found: # Test files found: test
# Files/dir to be installed from source: test # Copy test files
# Copy debian/tests/pkg-js content
'debian/tests/pkg-js' -> 
'/tmp/autopkgtest-lxc.is20x5x_/downtmp/autopkgtest_tmp/smokegz7eSX/debian/tests/pkg-js'
'debian/tests/pkg-js/test' -> 
'/tmp/autopkgtest-lxc.is20x5x_/downtmp/autopkgtest_tmp/smokegz7eSX/debian/tests/pkg-js/test'

# Searching module in /usr/lib/nodejs/mqtt-connection
# Searching module in /usr/lib/*/nodejs/mqtt-connection
# Searching module in /usr/share/nodejs/mqtt-connection
# Found /usr/share/nodejs/mqtt-connection
# Searching files to link in /usr/share/nodejs/mqtt-connection
'./connection.js' -> '/usr/share/nodejs/mqtt-connection/connection.js'
'./lib' -> '/usr/share/nodejs/mqtt-connection/lib'
'./package.json' -> '/usr/share/nodejs/mqtt-connection/package.json'
# Launch debian/tests/pkg-js/test with sh -ex
+ mocha test/


  Connection-v5
undefined should start piping in the next tick
transmission-v5
  #subscribe-5.0
undefined should send a 5.0 subscribe packet (single) (50ms)

  Connection
undefined should start piping in the next tick
parsing
  connect
undefined should fire a connect event (minimal)
undefined should fire a connect event (maximal)
parse errors
  undefined should say protocol not parseable
  connack
undefined should fire a connack event (rc = 0)
undefined should fire a connack event (rc = 5)
  publish
undefined should fire a publish event (minimal)
undefined should fire a publish event with 2KB payload
undefined should fire a publish event with 2MB payload
undefined should fire a publish event (maximal)
undefined should fire an empty publish
undefined should parse a splitted publish
  puback
undefined should fire a puback event
  pubrec
undefined should fire a pubrec event
  pubrel
1) should fire a pubrel event
  pubcomp
undefined should fire a pubcomp event
  subscribe
undefined should fire a subscribe event (1 topic)
undefined should fire a subscribe event (3 topic)
  suback
2) should fire a suback event
  unsubscribe
undefined should fire an unsubscribe event
  unsuback
undefined should fire a unsuback event
  pingreq
undefined should fire a pingreq event
  pingresp
undefined should fire a pingresp event
  disconnect
undefined should fire a disconnect event
  reserverd (15)
undefined should emit an error
  reserverd (0)
undefined should emit an error
transmission
  #connect
undefined should send a connect packet (minimal)
undefined should send a connect packet (maximal)
undefined should send a connect packet with binary 
username/password

undefined should send a connect packet with binary will payload
undefined should send a connect packet with unicode will payload
invalid options
  protocol id
undefined should reject non-string
  protocol version
undefined should reject non-number
undefined should reject >255
undefined should reject <0
  client id
undefined should reject non-present
undefined should reject empty
undefined should reject non-string
  keepalive
undefined should reject non-number
undefined should 

Processed: node-mqtt-packet breaks node-mqtt-connection autopkgtest: Invalid header flag bits, must be 0x2 for pubrel

[Debian Bug Tracking System]

Processing control commands:

> found -1 node-mqtt-packet/7.1.1-1
Bug #1001726 [src:node-mqtt-packet, src:node-mqtt-connection] node-mqtt-packet 
breaks node-mqtt-connection autopkgtest: Invalid header flag bits, must be 0x2 
for pubrel
Marked as found in versions node-mqtt-packet/7.1.1-1.
> found -1 node-mqtt-connection/4.1.0-3
Bug #1001726 [src:node-mqtt-packet, src:node-mqtt-connection] node-mqtt-packet 
breaks node-mqtt-connection autopkgtest: Invalid header flag bits, must be 0x2 
for pubrel
Marked as found in versions node-mqtt-connection/4.1.0-3.

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

Processed: python3.10: autopkgtest needs update for new version of setuptools: deprecation warning on stderr

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:setuptools
Bug #1001722 [src:python3.10] python3.10: autopkgtest needs update for new 
version of setuptools: deprecation warning on stderr
Added indication that 1001722 affects src:setuptools

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

Bug#1001722: python3.10: autopkgtest needs update for new version of setuptools: deprecation warning on stderr

[Paul Gevers]

Source: python3.10
Version: 3.10.1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, setupto...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:setuptools

Dear maintainer(s),

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


   passfail
setuptools from testing59.4.0-1
python3.10 from testing3.10.1-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. The test fails 
because there is a deprecation warning on stderr and the allow-stderr 
restriction is not set on the autopkgtest.


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


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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python3.10/17559467/log.gz

testFibPy
running install
/usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build 
and pip and other standards-based tools.

  warnings.warn(
/usr/lib/python3/dist-packages/setuptools/command/easy_install.py:158: 
EasyInstallDeprecationWarning: easy_install command is deprecated. Use 
build and pip and other standards-based tools.

  warnings.warn(
running bdist_egg
running egg_info
creating fibpy.egg-info
writing fibpy.egg-info/PKG-INFO
writing dependency_links to fibpy.egg-info/dependency_links.txt
writing top-level names to fibpy.egg-info/top_level.txt
writing manifest file 'fibpy.egg-info/SOURCES.txt'
reading manifest file 'fibpy.egg-info/SOURCES.txt'
writing manifest file 'fibpy.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
creating build
creating build/lib
copying fibpy.py -> build/lib
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/egg
copying build/lib/fibpy.py -> build/bdist.linux-x86_64/egg
byte-compiling build/bdist.linux-x86_64/egg/fibpy.py to 
fibpy.cpython-310.pyc

creating build/bdist.linux-x86_64/egg/EGG-INFO
copying fibpy.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying fibpy.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying fibpy.egg-info/dependency_links.txt -> 
build/bdist.linux-x86_64/egg/EGG-INFO
copying fibpy.egg-info/top_level.txt -> 
build/bdist.linux-x86_64/egg/EGG-INFO

copying fibpy.egg-info/zip-safe -> build/bdist.linux-x86_64/egg/EGG-INFO
creating dist
creating 'dist/fibpy-42.0.0-py3.10.egg' and adding 
'build/bdist.linux-x86_64/egg' to it

removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing fibpy-42.0.0-py3.10.egg
Copying fibpy-42.0.0-py3.10.egg to /usr/lib/python3.10/dist-packages
Adding fibpy 42.0.0 to easy-install.pth file



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1001721: pypy3: autopkgtest needs update for new version of setuptools: deprecation warning on stderr

[Paul Gevers]

Source: pypy3
Version: 7.3.7+dfsg-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, setupto...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:setuptools

Dear maintainer(s),

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


   passfail
setuptools from testing59.4.0-1
pypy3  from testing7.3.7+dfsg-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. The test fails 
because there is a deprecation warning on stderr and the allow-stderr 
restriction is not set on the autopkgtest.


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


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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pypy3/17554112/log.gz

Installed /usr/local/lib/pypy3.7/dist-packages/fibpy-42.0.0-py3.7.egg
Processing dependencies for fibpy==42.0.0
Finished processing dependencies for fibpy==42.0.0
/usr/lib/python3/dist-packages/setuptools/command/install.py:37: 
SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build 
and pip and other standards-based tools.

  setuptools.SetuptoolsDeprecationWarning,
/usr/lib/python3/dist-packages/setuptools/command/easy_install.py:161: 
EasyInstallDeprecationWarning: easy_install command is deprecated. Use 
build and pip and other standards-based tools.

  EasyInstallDeprecationWarning,
testFibC
running install
running bdist_egg
running egg_info
creating fibc.egg-info
writing fibc.egg-info/PKG-INFO
writing dependency_links to fibc.egg-info/dependency_links.txt
writing top-level names to fibc.egg-info/top_level.txt
writing manifest file 'fibc.egg-info/SOURCES.txt'
reading manifest file 'fibc.egg-info/SOURCES.txt'
writing manifest file 'fibc.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_ext
building 'fibc' extension
creating build
creating build/temp.linux-x86_64-3.7
gcc -pthread -DNDEBUG -O2 -fPIC -I/usr/lib/pypy3/include -c fibc.c -o 
build/temp.linux-x86_64-3.7/fibc.o

creating build/lib.linux-x86_64-3.7
gcc -pthread -shared build/temp.linux-x86_64-3.7/fibc.o -o 
build/lib.linux-x86_64-3.7/fibc.pypy37-pp73-x86_64-linux-gnu.so

creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/egg
copying build/lib.linux-x86_64-3.7/fibc.pypy37-pp73-x86_64-linux-gnu.so 
-> build/bdist.linux-x86_64/egg

creating stub loader for fibc.pypy37-pp73-x86_64-linux-gnu.so
byte-compiling build/bdist.linux-x86_64/egg/fibc.py to fibc.pypy37.pyc
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying fibc.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying fibc.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying fibc.egg-info/dependency_links.txt -> 
build/bdist.linux-x86_64/egg/EGG-INFO

copying fibc.egg-info/not-zip-safe -> build/bdist.linux-x86_64/egg/EGG-INFO
copying fibc.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
writing build/bdist.linux-x86_64/egg/EGG-INFO/native_libs.txt
creating dist
creating 'dist/fibc-42.0.0-py3.7-linux-x86_64.egg' and adding 
'build/bdist.linux-x86_64/egg' to it

removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing fibc-42.0.0-py3.7-linux-x86_64.egg
creating 
/usr/local/lib/pypy3.7/dist-packages/fibc-42.0.0-py3.7-linux-x86_64.egg
Extracting fibc-42.0.0-py3.7-linux-x86_64.egg to 
/usr/local/lib/pypy3.7/dist-packages

Adding fibc 42.0.0 to easy-install.pth file



OpenPGP_signature
Description: OpenPGP digital signature

Processed: pypy3: autopkgtest needs update for new version of setuptools: deprecation warning on stderr

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:setuptools
Bug #1001721 [src:pypy3] pypy3: autopkgtest needs update for new version of 
setuptools: deprecation warning on stderr
Added indication that 1001721 affects src:setuptools

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

Processed: bug 1001711 is forwarded to https://github.com/TokTok/c-toxcore/pull/1718

[Debian Bug Tracking System]

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

> forwarded 1001711 https://github.com/TokTok/c-toxcore/pull/1718
Bug #1001711 [libtoxcore2] libtoxcore2: Stack-based buffer overflow 
vulnerability in UDP packet handling in Toxcore (CVE-2021-44847)
Set Bug forwarded-to-address to 'https://github.com/TokTok/c-toxcore/pull/1718'.
> thanks
Stopping processing here.

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

Bug#1001719: jenkins-job-builder: autopkgtest needs update for new version of setuptools: deprecation warning on stderr

[Paul Gevers]

Source: jenkins-job-builder
Version: 3.11.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, setupto...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:setuptools

Dear maintainer(s),

With a recent upload of setuptools the autopkgtest of 
jenkins-job-builder fails in testing when that autopkgtest is run with 
the binary packages of setuptools from unstable. It passes when run with 
only packages from testing. In tabular form:


   passfail
setuptools from testing59.4.0-1
jenkins-job-builderfrom testing3.11.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. The test fails 
because there is a deprecation warning on stderr and the allow-stderr 
restriction is not set on the autopkgtest.


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


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

https://ci.debian.net/data/autopkgtest/testing/amd64/j/jenkins-job-builder/17554110/log.gz

Testing with python3.9:
{3} 
tests.cachestorage.test_cachestorage.TestCaseJobCache.test_save_on_exit 
[0.004601s] ... ok
{3} 
tests.jenkins_manager.test_manager.TestCaseTestJenkinsManager.test_get_plugins_info_handles_connectionrefused_errors 
[0.004442s] ... ok
{6} 
tests.parallel.test_parallel.TestCaseParallel.test_parallel_single_thread [0.001632s] 
... ok
{6} 
tests.xml_config.test_xml_config.TestXmlJobGeneratorExceptions.test_incorrect_template_params 
[0.026831s] ... ok
{4} 
tests.cmd.subcommands.test_update.UpdateTests.test_update_timeout_set 
... SKIPPED: TODO: Develop actual update timeout test approach.
/usr/lib/python3/dist-packages/pkg_resources/__init__.py:116: 
PkgResourcesDeprecationWarning: 1.0a.preview is an invalid version and 
will not be supported in a future release

  warnings.warn(


OpenPGP_signature
Description: OpenPGP digital signature

Processed: jenkins-job-builder: autopkgtest needs update for new version of setuptools: deprecation warning on stderr

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:setuptools
Bug #1001719 [src:jenkins-job-builder] jenkins-job-builder: autopkgtest needs 
update for new version of setuptools: deprecation warning on stderr
Added indication that 1001719 affects src:setuptools

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

Bug#1001718: astroscrappy breaks ccdproc autopkgtest: detect_cosmics() got an unexpected keyword argument 'pssl'

[Paul Gevers]

Source: astroscrappy, ccdproc
Control: found -1 astroscrappy/1.1.0-1
Control: found -1 ccdproc/2.2.0-1
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 astroscrappy the autopkgtest of ccdproc fails in 
testing when that autopkgtest is run with the binary packages of 
astroscrappy from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
astroscrappy   from testing1.1.0-1
ccdprocfrom testing2.2.0-1
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 astroscrappy to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/c/ccdproc/17555299/log.gz


=== FAILURES 
===
 test_cosmicray_lacosmic_does_not_change_input 
_


def test_cosmicray_lacosmic_does_not_change_input():
ccd_data = ccd_data_func()
original = ccd_data.copy()
error = np.zeros_like(ccd_data)

  ccd = cosmicray_lacosmic(ccd_data)


/usr/lib/python3/dist-packages/ccdproc/tests/test_ccdproc.py:794: _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ /usr/lib/python3/dist-packages/ccdproc/core.py:1525: in cosmicray_lacosmic

crmask, cleanarr = detect_cosmics(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

  ???

E   TypeError: detect_cosmics() got an unexpected keyword argument 'pssl'

astroscrappy/astroscrappy.pyx:26: TypeError
___ test_cosmicray_lacosmic 



def test_cosmicray_lacosmic():
ccd_data = ccd_data_func(data_scale=DATA_SCALE)
threshold = 5
add_cosmicrays(ccd_data, DATA_SCALE, threshold, ncrays=NCRAYS)
noise = DATA_SCALE * np.ones_like(ccd_data.data)

  data, crarr = cosmicray_lacosmic(ccd_data.data, sigclip=5)


/usr/lib/python3/dist-packages/ccdproc/tests/test_cosmicray.py:38: _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ /usr/lib/python3/dist-packages/ccdproc/core.py:1491: in cosmicray_lacosmic

crmask, cleanarr = detect_cosmics(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

  ???

E   TypeError: detect_cosmics() got an unexpected keyword argument 'pssl'

astroscrappy/astroscrappy.pyx:26: TypeError
___ test_cosmicray_lacosmic_ccddata 



def test_cosmicray_lacosmic_ccddata():
ccd_data = ccd_data_func(data_scale=DATA_SCALE)
threshold = 5
add_cosmicrays(ccd_data, DATA_SCALE, threshold, ncrays=NCRAYS)
noise = DATA_SCALE * np.ones_like(ccd_data.data)
ccd_data.uncertainty = noise

  nccd_data = cosmicray_lacosmic(ccd_data, sigclip=5)


/usr/lib/python3/dist-packages/ccdproc/tests/test_cosmicray.py:52: _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ /usr/lib/python3/dist-packages/ccdproc/core.py:1525: in cosmicray_lacosmic

crmask, cleanarr = detect_cosmics(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

  ???

E   TypeError: detect_cosmics() got an unexpected keyword argument 'pssl'

astroscrappy/astroscrappy.pyx:26: TypeError
- Captured stdout call 
-
INFO: array provided for uncertainty; assuming it is a 
StdDevUncertainty. [astropy.nddata.ccddata]
-- Captured log call 
---
INFO astropy:ccddata.py:263 array provided for uncertainty; assuming 
it is a StdDevUncertainty.
 test_cosmicray_gain_correct[True-True] 



array_input = True, gain_correct_data = True

@pytest.mark.parametrize('array_input', [True, False])
@pytest.mark.parametrize('gain_correct_data', [True, False])
def test_cosmicray_gain_correct(array_input, gain_correct_data):
# Add regression check for #705 and for the new gain_correct
# argument.
# The issue is that cosmicray_lacosmic gain-corrects the
# data and returns that gain corrected data. That is not the
# intent...
ccd_data = ccd_data_func(data_scale=DATA_SCALE)
threshold = 5
add_cosmicrays(ccd_data, DATA_SCALE, threshold, 

Processed: astroscrappy breaks ccdproc autopkgtest: detect_cosmics() got an unexpected keyword argument 'pssl'

[Debian Bug Tracking System]

Processing control commands:

> found -1 astroscrappy/1.1.0-1
Bug #1001718 [src:astroscrappy, src:ccdproc] astroscrappy breaks ccdproc 
autopkgtest: detect_cosmics() got an unexpected keyword argument 'pssl'
Marked as found in versions astroscrappy/1.1.0-1.
> found -1 ccdproc/2.2.0-1
Bug #1001718 [src:astroscrappy, src:ccdproc] astroscrappy breaks ccdproc 
autopkgtest: detect_cosmics() got an unexpected keyword argument 'pssl'
Marked as found in versions ccdproc/2.2.0-1.

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

Processed: src:minimap2: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.22+dfsg-3
Bug #1001716 [src:minimap2] src:minimap2: fails to migrate to testing for too 
long: autopkgtest regression
Marked as fixed in versions minimap2/2.22+dfsg-3.
Bug #1001716 [src:minimap2] src:minimap2: fails to migrate to testing for too 
long: autopkgtest regression
Marked Bug as done

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

Bug#1001716: src:minimap2: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: minimap2
Version: 2.17+dfsg-12
Severity: serious
Control: close -1 2.22+dfsg-3
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

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:minimap2 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=minimap2



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1000169: marked as pending in gui-ufw

[Stefano Rivera]

Control: tag -1 pending

Hello,

Bug #1000169 in gui-ufw 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/gui-ufw/-/commit/45aeeed62778a59aeb80ccd22356aba62dcfc021


d/patches: add an upstream patch to avoid crash on start

Closes: #1000169


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1000169

Processed: Bug#1000169 marked as pending in gui-ufw

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1000169 [gufw] gufw: Does not start
Added tag(s) pending.

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

Bug#1001709: amule-daemon: amuled crashes with segmentation fault on startup

[Sven Geuer]

Further observations:

Setting ConnectToKad=0 in ~/.aMule/amule.conf lets amuled start up as
expected, but of course without connecting to the Kademlia network.

Activating Kademlia later on via amulegui > Preferences > Connection >
Networks and bootstraping from known clients makes amuled crash again.

-- 
GPG Fingerprint
3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585


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

Bug#999282: spell: diff for NMU version 1.0-24.1

[gregor herrmann]

Control: tags 999282 + patch
Control: tags 999282 + pending


Dear maintainer,

I've prepared an NMU for spell (versioned as 1.0-24.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Michèle Sammarcelli: n/a
diff -u spell-1.0/debian/rules spell-1.0/debian/rules
--- spell-1.0/debian/rules
+++ spell-1.0/debian/rules
@@ -25,7 +25,8 @@
 
 	CFLAGS="$(CFLAGS)" ./configure $(CROSS) --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info
 
-build: build-stamp
+build: build-arch
+build-arch: build-stamp
 build-stamp: config.status
 	dh_testdir
 
@@ -33,6 +34,8 @@
 
 	touch build-stamp
 
+build-indep:
+
 install: build
 	dh_testdir
 	dh_testroot
@@ -63,4 +66,4 @@
 
 binary-indep:
 
-.PHONY: clean build install binary binary-arch binary-indep
+.PHONY: clean build build-arch build-indep install binary binary-arch binary-indep
diff -u spell-1.0/debian/changelog spell-1.0/debian/changelog
--- spell-1.0/debian/changelog
+++ spell-1.0/debian/changelog
@@ -1,3 +1,12 @@
+spell (1.0-24.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "missing required debian/rules targets build-arch and/or build-
+indep": add targets to debian/rules.
+(Closes: #999282)
+
+ -- gregor herrmann   Tue, 14 Dec 2021 19:11:57 +0100
+
 spell (1.0-24) unstable; urgency=low
 
   * Support also aspell (Closes: #381511)


signature.asc
Description: Digital Signature

Bug#1001711: libtoxcore2: Stack-based buffer overflow vulnerability in UDP packet handling in Toxcore (CVE-2021-44847)

[Vincas Dargis]

Package: libtoxcore2
Version: 0.2.12-1+b1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: Debian Security Team 

Dear Maintainer,

libtoxcore has CVE-2021-44847:

https://blog.tox.chat/2021/12/stack-based-buffer-overflow-vulnerability-in-udp-packet-handling-in-toxcore-cve-2021-44847/

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44847

Workaround is to disable UDP support in settings.

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

Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8), LANGUAGE=lt
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libtoxcore2 depends on:
ii  libc62.33-1
ii  libopus0 1.3.1-0.1
ii  libsodium23  1.0.18-1
ii  libvpx7  1.11.0-2

libtoxcore2 recommends no packages.

libtoxcore2 suggests no packages.

-- no debconf information

Processed: spell: diff for NMU version 1.0-24.1

[Debian Bug Tracking System]

Processing control commands:

> tags 999282 + patch
Bug #999282 [src:spell] spell: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) patch.
> tags 999282 + pending
Bug #999282 [src:spell] spell: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) pending.

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

Bug#1000768: marked as done (krb5: FTBFS due to missing dependency on tex-gyre)

[Debian Bug Tracking System]

Your message dated Tue, 14 Dec 2021 18:03:59 +
with message-id 
and subject line Bug#997407: fixed in krb5 1.19.2-1
has caused the Debian Bug report #997407,
regarding krb5: FTBFS due to missing dependency on tex-gyre
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.)


-- 
997407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: krb5
Severity: serious
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Between September and October, something changed in krb5's build
dependencies that triggers a build failure:

  https://tests.reproducible-builds.org/debian/history/amd64/krb5.html

You can pick from a few failing build logs at:

  https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/krb5.html

Except from a failing build:

  (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def))
  (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf))

  ! LaTeX Error: File `tgtermes.sty' not found.

  Type X to quit or  to proceed,
  or enter new name. (Default extension: sty)

  Enter file name:
  ! Emergency stop.
  

  l.37 \usepackage
  {tgheros}^^M
  !  ==> Fatal error occurred, no output PDF file produced!

I'm not sure the exact cause of the changes, but adding tex-gyre to
Build-Depends-Indep appears to fix this issue.


Thanks for maintaining krb5!


live well,
  vagrant
From ba098c18c519c9275eafeac18983e5974a8714af Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sun, 28 Nov 2021 18:56:56 +
Subject: [PATCH] debian/control: Add Build-Depends-Indep on tex-gyre.

---
 debian/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index bd78bbe11..973f11b64 100644
--- a/debian/control
+++ b/debian/control
@@ -6,7 +6,7 @@ Build-Depends: debhelper-compat (= 13), byacc | bison,
  libkeyutils-dev [linux-any], libldap2-dev , libsasl2-dev ,
  libssl-dev,  ss-dev,
  libverto-dev (>= 0.2.4), pkg-config
-Build-Depends-Indep: python3, python3-cheetah, python3-lxml, python3-sphinx, doxygen, doxygen-latex
+Build-Depends-Indep: python3, python3-cheetah, python3-lxml, python3-sphinx, doxygen, doxygen-latex, tex-gyre
 Standards-Version: 4.5.0
 Maintainer: Sam Hartman 
 Uploaders: Russ Allbery , Benjamin Kaduk 
-- 
2.30.2



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: krb5
Source-Version: 1.19.2-1
Done: Sam Hartman 

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

Debian distribution maintenance software
pp.
Sam Hartman  (supplier of updated krb5 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 27 Oct 2021 14:04:42 -0600
Source: krb5
Architecture: source
Version: 1.19.2-1
Distribution: experimental
Urgency: medium
Maintainer: Sam Hartman 
Changed-By: Sam Hartman 
Closes: 995152 997407
Changes:
 krb5 (1.19.2-1) experimental; urgency=medium
 .
   * New Upstream version
   * Include patch to work with OpenSSL 3.0, Closes: #995152
   * Depend on tex-gyre, Closes: #997407
Checksums-Sha1:
 d19900f7c6b002eba42d9064f6d272b7750a5b34 3170 krb5_1.19.2-1.dsc
 f6980dafd31eac22a047ad34a2b918e4d12a8be5 8741053 krb5_1.19.2.orig.tar.gz
 ddef8f2ac764ab5375289c3f18b9587384162c15 833 krb5_1.19.2.orig.tar.gz.asc
 7645c7b0af26d1dde24c4d9e60355e897a6a3600 106728 krb5_1.19.2-1.debian.tar.xz
 11827dcb91fdee9cd7e4cb3a0927ef1d30296419 5000 krb5_1.19.2-1_source.buildinfo
Checksums-Sha256:
 fcfef6e08b9817012758c0eaf932c3f2f9c7067f8f19f8881200148c0145c520 3170 
krb5_1.19.2-1.dsc
 10453fee4e3a8f8ce6129059e5c050b8a65dab1c257df68b99b3112eaa0cdf6a 8741053 
krb5_1.19.2.orig.tar.gz
 afaa581a1551eba22c1f193c04f913193785e2dce12677ff2aed80503a99a8f8 833 
krb5_1.19.2.orig.tar.gz.asc
 8e802d95fded30feca741da6b7abd535bb2bf3cdd748fdc6378588702d714b47 106728 
krb5_1.19.2-1.debian.tar.xz
 d78260ce1696bc203712b4bf2562b75d167727f80012349fc179bd4e95761f3d 5000 

Bug#1001709: amule-daemon: amuled crashes with segmentation fault on startup

[Sven Geuer]

Package: amule-daemon
Version: 1:2.3.3-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: debma...@g-e-u-e-r.de

Dear Maintainer,

amuled crashes on startup since my recent system upgrade.

Here's what gdb reveals.

(gdb) run   
Starting program: /usr/bin/amuled 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after vfork from child process 3950]
 2021-12-14 18:42:31: Initialising aMuleD 2.3.3 compiled with wxBase(GTK2) 
v3.0.5 and Boost 1.74
 2021-12-14 18:42:31: Checking if there is an instance already running...
 2021-12-14 18:42:31: No other instances are running.
[Detaching after vfork from child process 3952]
[Detaching after vfork from child process 3954]
[Detaching after vfork from child process 3956]
[Detaching after vfork from child process 3958]
[Detaching after vfork from child process 3960]
[Detaching after vfork from child process 3965]
[Detaching after vfork from child process 3970]
[Detaching after vfork from child process 3975]
 2021-12-14 18:42:33: ListenSocket: Ok.
[New Thread 0x7721e640 (LWP 3980)]
[New Thread 0x76a1d640 (LWP 3981)]
[New Thread 0x7621c640 (LWP 3982)]
[New Thread 0x75a1b640 (LWP 3983)]
[New Thread 0x7521a640 (LWP 3984)]
[New Thread 0x74a19640 (LWP 3985)]
 2021-12-14 18:42:33: Loading temp files from /home/sg/.aMule/Temp.
 2021-12-14 18:42:33: All PartFiles Loaded.
 2021-12-14 18:42:33: amuled: OnInit - starting timer
[New Thread 0x7fffd640 (LWP 3986)]
 2021-12-14 18:42:33: Asio thread 1 started
 2021-12-14 18:42:33: Asio thread 2 started
 2021-12-14 18:42:33: Asio thread 3 started
 2021-12-14 18:42:33: Asio thread 4 started
[Thread 0x74a19640 (LWP 3985) exited]
[Detaching after fork from child process 3987]

Thread 1 "amuled" received signal SIGSEGV, Segmentation fault.
0x55679781 in Kademlia::CKademlia::ProcessPacket (
data=0x7fff8d10 
"\344!\004\016\376TN\346\377\003\355j\261\245\006e:\003\331\"\241\311NU\001x\207\031\323\061\037\374\367@\217",
 
lenData=lenData@entry=35, ip=ip@entry=1564980350, port=port@entry=51663, 
validReceiverKey=true, senderKey=...)
at ../../src/kademlia/kademlia/Kademlia.cpp:303
303 ../../src/kademlia/kademlia/Kademlia.cpp: No such file or directory.


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

Kernel: Linux 5.15.0-2-amd64 (SMP w/2 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages amule-daemon depends on:
ii  amule-common  1:2.3.3-2
ii  libc6 2.32-5
ii  libcrypto++8  8.6.0-2
ii  libgcc-s1 11.2.0-12
ii  libixml10 1:1.8.4-2
ii  libpng16-16   1.6.37-3
ii  libreadline8  8.1-2
ii  libstdc++611.2.0-12
ii  libupnp13 1:1.8.4-2
ii  libwxbase3.0-0v5  3.0.5.1+dfsg-2+b1
ii  lsb-base  11.1.0
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages amule-daemon recommends:
ii  amule-utils  1:2.3.3-2
ii  unzip6.0-26

amule-daemon suggests no packages.

-- Configuration Files:
/etc/default/amule-daemon changed [not included]

-- no debconf information

Processed: libdigest-whirlpool-perl: diff for NMU version 1.09-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 998961 + patch
Bug #998961 [src:libdigest-whirlpool-perl] libdigest-whirlpool-perl: missing 
required debian/rules targets build-arch and/or build-indep
Added tag(s) patch.
> tags 998961 + pending
Bug #998961 [src:libdigest-whirlpool-perl] libdigest-whirlpool-perl: missing 
required debian/rules targets build-arch and/or build-indep
Added tag(s) pending.

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

Bug#998961: libdigest-whirlpool-perl: diff for NMU version 1.09-1.2

[gregor herrmann]

Control: tags 998961 + patch
Control: tags 998961 + pending


Dear maintainer,

I've prepared an NMU for libdigest-whirlpool-perl (versioned as 1.09-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Michèle Sammarcelli: n/a
diff -u libdigest-whirlpool-perl-1.09/debian/changelog libdigest-whirlpool-perl-1.09/debian/changelog
--- libdigest-whirlpool-perl-1.09/debian/changelog
+++ libdigest-whirlpool-perl-1.09/debian/changelog
@@ -1,3 +1,12 @@
+libdigest-whirlpool-perl (1.09-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "missing required debian/rules targets build-arch and/or build-
+indep": add targets to debian/rules.
+(Closes: #998961)
+
+ -- gregor herrmann   Tue, 14 Dec 2021 18:59:32 +0100
+
 libdigest-whirlpool-perl (1.09-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u libdigest-whirlpool-perl-1.09/debian/rules libdigest-whirlpool-perl-1.09/debian/rules
--- libdigest-whirlpool-perl-1.09/debian/rules
+++ libdigest-whirlpool-perl-1.09/debian/rules
@@ -24,7 +24,9 @@
 CFLAGS += -O2
 endif
 
-build: build-stamp
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 build-stamp:
 	dh_testdir
 	# Add commands to compile the package here
@@ -73,4 +75,4 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install
+.PHONY: build-indep build-arch build clean binary-indep binary-arch binary install


signature.asc
Description: Digital Signature

Processed: libemail-foldertype-perl: diff for NMU version 0.813-1.4

[Debian Bug Tracking System]

Processing control commands:

> tags 999078 + patch
Bug #999078 [src:libemail-foldertype-perl] libemail-foldertype-perl: missing 
required debian/rules targets build-arch and/or build-indep
Added tag(s) patch.
> tags 999078 + pending
Bug #999078 [src:libemail-foldertype-perl] libemail-foldertype-perl: missing 
required debian/rules targets build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999078: libemail-foldertype-perl: diff for NMU version 0.813-1.4

[gregor herrmann]

Control: tags 999078 + patch
Control: tags 999078 + pending


Dear maintainer,

I've prepared an NMU for libemail-foldertype-perl (versioned as 0.813-1.4) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Michèle Sammarcelli: n/a
diff -u libemail-foldertype-perl-0.813/debian/changelog libemail-foldertype-perl-0.813/debian/changelog
--- libemail-foldertype-perl-0.813/debian/changelog
+++ libemail-foldertype-perl-0.813/debian/changelog
@@ -1,3 +1,14 @@
+libemail-foldertype-perl (0.813-1.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "missing required debian/rules targets build-arch and/or build-
+indep": use dh(1) in debian/rules.
+(Closes: #999078)
+  * Additionally add libmodule-pluggable-perl to Build-Depends-Indep,
+as the tests are not skipped anymore.
+
+ -- gregor herrmann   Tue, 14 Dec 2021 18:49:33 +0100
+
 libemail-foldertype-perl (0.813-1.3) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -u libemail-foldertype-perl-0.813/debian/control libemail-foldertype-perl-0.813/debian/control
--- libemail-foldertype-perl-0.813/debian/control
+++ libemail-foldertype-perl-0.813/debian/control
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Michael Ablassmeier  
 Build-Depends: debhelper (>= 9)
-Build-Depends-Indep: perl (>= 5.6.0-16)
+Build-Depends-Indep: perl (>= 5.6.0-16), libmodule-pluggable-perl
 Standards-Version: 3.7.2 
 
 Package: libemail-foldertype-perl
diff -u libemail-foldertype-perl-0.813/debian/rules libemail-foldertype-perl-0.813/debian/rules
--- libemail-foldertype-perl-0.813/debian/rules
+++ libemail-foldertype-perl-0.813/debian/rules
@@ -5,54 +5,5 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-ifndef PERL
-	PERL = /usr/bin/perl
-endif
-
-package = libemail-foldertype-perl
-
-build: build-stamp
-build-stamp:
-	dh_testdir
-
-	perl Makefile.PL INSTALLDIRS=vendor
-	$(MAKE) OPTIMIZE="-O2 -g -Wall"
-
-	touch build-stamp
-
-clean:
-	dh_testdir
-	dh_testroot
-	rm -f build-stamp configure-stamp
-
-	-$(MAKE) realclean
-
-	dh_clean
-
-install: build
-	dh_testdir
-	dh_testroot
-	dh_clean -k
-	dh_installdirs
-
-	$(MAKE) install DESTDIR=$(CURDIR)/debian/$(package)
-	-rmdir --ignore-fail-on-non-empty -p $(CURDIR)/debian/$(package)/usr/lib/perl5
-
-
-binary-arch: build install
-
-binary-indep: build install
-	dh_testdir
-	dh_testroot
-	dh_installdocs
-	dh_installchangelogs Changes
-	dh_compress
-	dh_fixperms
-	dh_installdeb
-	dh_perl
-	dh_gencontrol
-	dh_md5sums
-	dh_builddeb
-
-binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install
+%:
+	dh $@


signature.asc
Description: Digital Signature

Bug#1001675: marked as done (libgcrypt20 FTBFS on armhf: error: ‘asm’ operand has impossible constraints)

[Debian Bug Tracking System]

Your message dated Tue, 14 Dec 2021 17:48:43 +
with message-id 
and subject line Bug#1001675: fixed in libgcrypt20 1.9.4-5
has caused the Debian Bug report #1001675,
regarding libgcrypt20 FTBFS on armhf: error: ‘asm’ operand has impossible 
constraints
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.)


-- 
1001675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgcrypt20
Version: 1.9.4-4
Severity: serious
Tags: ftbfs

Likely, you already know, but I'd it would help to have a bug number
here to track things: libgcrypt20 fails to build from source on armhf on
the buildds. The relevant excerpt is:

| ../../cipher/poly1305.c: In function ‘poly1305_blocks’:
| ../../cipher/poly1305.c:302:7: error: ‘asm’ operand has impossible constraints
|   302 |   __asm__ ("adds %0, %0, %5\n" \
|   |   ^~~
| ../../cipher/poly1305.c:425:7: note: in expansion of macro ‘ADD_1305_32’
|   425 |   ADD_1305_32(h4, h3, h2, h1, h0, m4, m3, m2, m1, m0);
|   |   ^~~

Helmut
--- End Message ---
--- Begin Message ---
Source: libgcrypt20
Source-Version: 1.9.4-5
Done: Andreas Metzler 

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

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated libgcrypt20 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: Tue, 14 Dec 2021 17:56:04 +0100
Source: libgcrypt20
Architecture: source
Version: 1.9.4-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuTLS Maintainers 
Changed-By: Andreas Metzler 
Closes: 1001675
Changes:
 libgcrypt20 (1.9.4-5) unstable; urgency=medium
 .
   * Pull 30_01-poly1305-fix-building-with-arm-linux-gnueabihf-gcc-1.patch from
 upstream GIT master branch, fixing FTBFS on armhf. Closes: #1001675
Checksums-Sha1: 
 4ddce2735fa9a220a5232bd7d1f94391436886bb 2800 libgcrypt20_1.9.4-5.dsc
 9bd152043bcf1b1cecdcf577a79d01d9c5fd0200 35768 
libgcrypt20_1.9.4-5.debian.tar.xz
Checksums-Sha256: 
 809342159731b6fd7921ee576a0e836a10760703ac07b363bce05bbb188c8484 2800 
libgcrypt20_1.9.4-5.dsc
 f03349a3eb9940fc45419da0a5a2ff49ee78bdaa7e79a8fcf403cd1d3a611f36 35768 
libgcrypt20_1.9.4-5.debian.tar.xz
Files: 
 945cb2b55b97212e4bddd1760a80bd90 2800 libs optional libgcrypt20_1.9.4-5.dsc
 edaf1d4edc78788529b95bd42ddbb6b5 35768 libs optional 
libgcrypt20_1.9.4-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmG40hwACgkQpU8BhUOC
FISQSQ/9F7mD/aqqksKHNijaWwCAaJ1bdyGI5JJlulcJHi1Xfnwz1K/JD/tmKXKP
Lv04JA4IWUSPYvldMpPvwXY4ec9SXWOMPwe6ntNh5Zn4viF6br70XKOgt0xJy0Mq
DlrARaohZTNpFQWIOIVOX+VkvncgtXZw0wSsErLCEGZlGrDLDh/KA1cgIMD6AVVG
v3IZqWWTEsbvNh/tvTcS5kuyxxAX2JIk16mvuEz98uxYevcYMqqj7BkB3lpgy6BC
uqDTXVoupQQTRAi7lZjhgySxRDnRonnGRD990kDOTozJyWAy2+5sgV/jm7fXjJiY
J3AlAMMsw9jFC3YokVbgITvfEsOQYzZMeyPyBiCTP/XE/cn9x7NrkN8ljtpar6Ni
Rqf/RnoSdyW0YXeQV7J6wVTmErHR077d4ywmY/8V9Jqbe9mTUUe5q6qqoa5xgUj+
thyUQctU7pRZRnXgK+mBO58+GVHvLgtj4xG1DZSfv1nBA/YyUybGBPo9qJYGZ204
kXdAUw78htxTKZ8MOb95FVvcNBIR7yofAM+L/fZ686N8y7TPwz0scM396pN6iPDy
22LeAluOsVrR+AWDw+HRlpz3dX7HELQZJ9AfopGpxokGtM3Hftjs0OaUuHOwxrvq
ILeDs9BLQ32b/uHRRAcwq8VngGdvTIIUgayzseJtLtLaYN9dq8o=
=AbYP
-END PGP SIGNATURE End Message ---

Bug#978911: transmission: diff for NMU version 3.00-1.1

[Sandro Tosi]

> It's been another 2 weeks and this RC bug is still open. In total this RC bug
> has lasted for almost a year. This doesn't look well.

false. the bug has been open since a year, it has become RC since Aug 2021 only.

> I know that the proposed patch is not elegant at all (really hacky in terms of
> macro processing), and I understand that upstream will be moving away from
> autotools in future releases thus applying this patch might not be the ideal
> choice. However, having this package FTBFS in the archive forever is
> definitely not a good choice either. For example, such FTBFS might block any
> future transition in the near future (e.g., openssl-3.0 as in
> https://release.debian.org/transitions/html/auto-openssl.html ). I don't see
> any benefit with procrastination on it.

so, what's exactly broken that you're pestering so much to get it
addressed this urgently?

transmission works fine, it's not at risk of being removed from
testing, i'll deal with it in due corse.

thanks for your concern, but take it easy

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Processed: forcibly merging 997407 1000768

[Debian Bug Tracking System]

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

> forcemerge 997407 1000768
Bug #997407 [src:krb5] krb5: FTBFS: ! LaTeX Error: File `tgtermes.sty' not 
found.
Bug #1000768 [src:krb5] krb5: FTBFS due to missing dependency on tex-gyre
Added tag(s) ftbfs, pending, sid, and bookworm.
Bug #997407 [src:krb5] krb5: FTBFS: ! LaTeX Error: File `tgtermes.sty' not 
found.
Added tag(s) patch.
Merged 997407 1000768
> thanks
Stopping processing here.

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

Processed: libxml-rss-feed-perl: diff for NMU version 2.212-1.3

[Debian Bug Tracking System]

Processing control commands:

> tags 993335 + patch
Bug #993335 [src:libxml-rss-feed-perl] libxml-rss-feed-perl: FTBFS with Perl 
5.34: t/010_deprecated_methods.t failure
Ignoring request to alter tags of bug #993335 to the same tags previously set
> tags 993335 + pending
Bug #993335 [src:libxml-rss-feed-perl] libxml-rss-feed-perl: FTBFS with Perl 
5.34: t/010_deprecated_methods.t failure
Ignoring request to alter tags of bug #993335 to the same tags previously set
> tags 999215 + patch
Bug #999215 [src:libxml-rss-feed-perl] libxml-rss-feed-perl: missing required 
debian/rules targets build-arch and/or build-indep
Ignoring request to alter tags of bug #999215 to the same tags previously set
> tags 999215 + pending
Bug #999215 [src:libxml-rss-feed-perl] libxml-rss-feed-perl: missing required 
debian/rules targets build-arch and/or build-indep
Ignoring request to alter tags of bug #999215 to the same tags previously set

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

Bug#999215: libxml-rss-feed-perl: diff for NMU version 2.212-1.3

[gregor herrmann]

Control: tags 993335 + patch
Control: tags 993335 + pending
Control: tags 999215 + patch
Control: tags 999215 + pending


Dear maintainer,

I've prepared an NMU for libxml-rss-feed-perl (versioned as 2.212-1.3) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Michèle Sammarcelli: n/a
diff -u libxml-rss-feed-perl-2.212/debian/changelog libxml-rss-feed-perl-2.212/debian/changelog
--- libxml-rss-feed-perl-2.212/debian/changelog
+++ libxml-rss-feed-perl-2.212/debian/changelog
@@ -1,3 +1,15 @@
+libxml-rss-feed-perl (2.212-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "missing required debian/rules targets build-arch and/or build-
+indep": add missing targets to debian/rules.
+(Closes: #999215)
+  * Fix "FTBFS with Perl 5.34: t/010_deprecated_methods.t failure":
+take fixed test from upstream 2.4 release.
+(Closes: #993335)
+
+ -- gregor herrmann   Tue, 14 Dec 2021 18:41:00 +0100
+
 libxml-rss-feed-perl (2.212-1.2) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -u libxml-rss-feed-perl-2.212/debian/rules libxml-rss-feed-perl-2.212/debian/rules
--- libxml-rss-feed-perl-2.212/debian/rules
+++ libxml-rss-feed-perl-2.212/debian/rules
@@ -11,6 +11,8 @@
 PACKAGE=`pwd | sed -e "s/.*\/\\(.*\\)-.*/\\1/"`
 
 
+build-arch: build
+build-indep: build
 build:
 	dh_testdir
 	# Add here commands to compile the package.
@@ -54,4 +56,4 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+.PHONY: build-indep build-arch build clean binary-indep binary-arch binary install configure
only in patch2:
unchanged:
--- libxml-rss-feed-perl-2.212.orig/t/010_deprecated_methods.t
+++ libxml-rss-feed-perl-2.212/t/010_deprecated_methods.t
@@ -1,6 +1,7 @@
 #!/usr/bin/perl
-
-use Test::More tests => 8;
+use strict;
+use warnings;
+use Test::More tests => 4;
 
 BEGIN { use_ok('XML::RSS::Feed') }
 
@@ -10,14 +11,9 @@
 );
 isa_ok( $feed, 'XML::RSS::Feed' );
 
-$SIG{__WARN__} = build_warn("deprecated");
-cmp_ok( $feed->failed_to_fetch, 'eq', "",
-"Verify that failed_to_fetch returns ''" );
-cmp_ok( $feed->failed_to_parse, 'eq', "",
-"Verify that failed_to_parse returns ''" );
-
-sub build_warn {
-my @args = @_;
-return sub { my ($warn) = @_; like( $warn, qr/$_/i, $_ ) for @args };
+{
+local $SIG{'__WARN__'} = sub {};
+cmp_ok( $feed->failed_to_fetch, 'eq', "", "Verify that failed_to_fetch returns ''" );
+cmp_ok( $feed->failed_to_parse, 'eq', "", "Verify that failed_to_parse returns ''" );
 }
 


signature.asc
Description: Digital Signature

Processed: libxml-rss-feed-perl: diff for NMU version 2.212-1.3

[Debian Bug Tracking System]

Processing control commands:

> tags 993335 + patch
Bug #993335 [src:libxml-rss-feed-perl] libxml-rss-feed-perl: FTBFS with Perl 
5.34: t/010_deprecated_methods.t failure
Added tag(s) patch.
> tags 993335 + pending
Bug #993335 [src:libxml-rss-feed-perl] libxml-rss-feed-perl: FTBFS with Perl 
5.34: t/010_deprecated_methods.t failure
Added tag(s) pending.
> tags 999215 + patch
Bug #999215 [src:libxml-rss-feed-perl] libxml-rss-feed-perl: missing required 
debian/rules targets build-arch and/or build-indep
Added tag(s) patch.
> tags 999215 + pending
Bug #999215 [src:libxml-rss-feed-perl] libxml-rss-feed-perl: missing required 
debian/rules targets build-arch and/or build-indep
Added tag(s) pending.

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

Bug#978911: transmission: diff for NMU version 3.00-1.1

[Boyuan Yang]

X-Debbugs-CC: mo...@debian.org cost...@debian.org

Hi,

On Wed, 01 Dec 2021 00:12:42 -0500 Boyuan Yang  wrote:
> Control: tags -1 -pending
> 
> Hi,
> 
> 在 2021-11-30星期二的 18:09 -0500，Sandro Tosi写道：
> > > I've prepared an NMU for transmission (versioned as 3.00-1.1) and
> > > uploaded it to DELAYED/5. Please feel free to tell me if I
> > > should delay it longer.
> > 
> > please remove it from the delayed queue, there's no need for a nmu here
> 
> I have cancelled the upload and removed it from the delayed queue. Since
this
> will leave this RC bug open, may I ask how will it be fixed then?

It's been another 2 weeks and this RC bug is still open. In total this RC bug
has lasted for almost a year. This doesn't look well.

I know that the proposed patch is not elegant at all (really hacky in terms of
macro processing), and I understand that upstream will be moving away from
autotools in future releases thus applying this patch might not be the ideal
choice. However, having this package FTBFS in the archive forever is
definitely not a good choice either. For example, such FTBFS might block any
future transition in the near future (e.g., openssl-3.0 as in
https://release.debian.org/transitions/html/auto-openssl.html ). I don't see
any benefit with procrastination on it.

Thanks,
Boyuan Yang


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

Bug#984049: enblend-enfuse: ftbfs with GCC-11

[Heinz Repp]

/usr/include/vigra/separableconvolution.hxx:1413:13: error: ISO C++17 does not 
allow dynamic exception specifications
/usr/include/vigra/stdconvolution.hxx:796:13: error: ISO C++17 does not allow 
dynamic exception specifications


For those two errors I propose the first patch (c++17conf, in 
include/vigra): The original code had conditional compilation in place: 
all non Microsoft compilers got a pre-C++11 and C++17-forbidden 
construct, and Microsoft Visual C++ 2014 and up got a C++11-introduced 
and C++17-conformant construct. I removed the condition and left only 
the latter - this means you need at least GCC 4.8.1 to compile this (or 
MSC 2014/201).



Then I found another syntax error in Python code - Python 3.10 requires 
parentheses around multiple except-clauses (pythonexcept, in vigranumpy).


With those two patches it compiles, but then 22 tests fail, all with the 
same error in C++ template syntax I am not familiar with. They all fail 
because of a single discrepancy between Python and C++ representation of 
the constructArrayFromAxistags function:



Boost.Python.ArgumentError: Python argument types in
vigra.vigranumpycore.constructArrayFromAxistags(type, tuple, 
numpy.dtype[float32], AxisTags, bool)
did not match C++ signature:
constructArrayFromAxistags(boost::python::api::object, vigra::ArrayVector >, NPY_TYPES, vigra::AxisTags, bool)



Maybe someone can figure out what's wrong there.

Greetings

Heinz Reppdiff -Naur a/separableconvolution.hxx b/separableconvolution.hxx
--- a/separableconvolution.hxx	2021-12-14 12:47:58.561112628 +0100
+++ b/separableconvolution.hxx	2021-12-14 12:41:47.490153379 +0100
@@ -1409,11 +1409,7 @@
 {}
 
 ~InitProxy()
-#ifndef _MSC_VER
-throw(PreconditionViolation)
-#elif _MSC_VER >= 1900
 noexcept(false)
-#endif
 {
 vigra_precondition(count_ == 1 || count_ == sum_,
   "Kernel1D::initExplicitly(): "
diff -Naur a/stdconvolution.hxx b/stdconvolution.hxx
--- a/stdconvolution.hxx	2021-12-14 12:47:58.561112628 +0100
+++ b/stdconvolution.hxx	2021-12-14 12:43:12.728503532 +0100
@@ -792,11 +792,7 @@
 {}
 
 ~InitProxy()
-#ifndef _MSC_VER
-throw(PreconditionViolation)
-#elif _MSC_VER >= 1900
 noexcept(false)
-#endif
 {
 vigra_precondition(count_ == 1 || count_ == sum_,
"Kernel2D::initExplicitly(): "
diff -Naur a/conf.py.cmake2.in b/conf.py.cmake2.in
--- a/conf.py.cmake2.in	2021-12-14 12:38:10.0 +0100
+++ b/conf.py.cmake2.in	2021-12-14 14:13:42.030342506 +0100
@@ -23,7 +23,7 @@
 def _getargspec_workaround(*args, **kw):
 try:
 return _original_getargspec(*args, **kw)
-except TypeError, e:
+except (TypeError, e):
 if str(e).startswith('arg is not a Python function'):
 return inspect.ArgSpec([], None, None, None)
 else:
diff -Naur a/conf.py.in b/conf.py.in
--- a/conf.py.in	2021-12-14 12:38:10.0 +0100
+++ b/conf.py.in	2021-12-14 14:14:07.576442837 +0100
@@ -22,7 +22,7 @@
 def _getargspec_workaround(*args, **kw):
 try:
 return _original_getargspec(*args, **kw)
-except TypeError, e:
+except (TypeError, e):
 if str(e).startswith('arg is not a Python function'):
 return inspect.ArgSpec([], None, None, None)
 else:

Bug#1001681: sight: FTBFS in unstable

[Flavien Bridault]

Understood, I just wanted to avoid any overlap. I'll have a look asap. :)


*Dr. Flavien BRIDAULT*
Director of Software Development
IRCAD France & IRCAD Africa

flavien.brida...@ircad.fr 
Tél. : +33 (0)3 88 119 201
IRCAD France
http://www.ircad.fr/
http://www.ircad.africa/ 

Suivez l'IRCAD sur Facebook 



*IRCAD France*
Hôpitaux Universitaires - 1, place de l'Hôpital - 67091 Strasbourg Cedex 
- FRANCE


Le 14/12/2021 à 17:49, Andreas Tille a écrit :

Hi Flavien,

Am Tue, Dec 14, 2021 at 04:13:26PM +0100 schrieb Flavien Bridault:

Thanks for the notice.

This comes from DCMTK. Maybe an API change or a move of a header. Do you
want me to have a look ?

I guess Steve will be very happy if you can have a look.  As far as
I know he is not a medical imaging expert and has no interest in
debugging DCMTK.

Thanks a lot for checking

   Andreas.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1001681: sight: FTBFS in unstable

[Andreas Tille]

Hi Flavien,

Am Tue, Dec 14, 2021 at 04:13:26PM +0100 schrieb Flavien Bridault:
> Thanks for the notice.
> 
> This comes from DCMTK. Maybe an API change or a move of a header. Do you
> want me to have a look ?

I guess Steve will be very happy if you can have a look.  As far as
I know he is not a medical imaging expert and has no interest in
debugging DCMTK.

Thanks a lot for checking

  Andreas.

-- 
http://fam-tille.de

Bug#1000726: marked as done (cfgrib: FTBFS with pandas 1.3: datetime64/timedelta64 must have a unit specified)

[Debian Bug Tracking System]

Your message dated Tue, 14 Dec 2021 16:03:32 +
with message-id 
and subject line Bug#1000726: fixed in cfgrib 0.9.9.1-2
has caused the Debian Bug report #1000726,
regarding cfgrib: FTBFS with pandas 1.3: datetime64/timedelta64 must have a 
unit specified
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.)


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

Package: python3-cfgrib
Version: 0.9.9.1-1
Severity: important
Control: tags -1 upstream
Control: block 999415 by -1

test_translate_coords(_errors) try to convert a list of integers 
https://sources.debian.org/src/cfgrib/0.9.9.1-1/tests/test_20_cfcoords.py/#L66 
to a timedelta xarray without specifying their unit, which is no longer 
allowed in pandas 1.3.


Upstream look like they still have this issue (though I haven't actually 
tested that) and don't know about it.
--- End Message ---
--- Begin Message ---
Source: cfgrib
Source-Version: 0.9.9.1-2
Done: Alastair McKinstry 

We believe that the bug you reported is fixed in the latest version of
cfgrib, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1000...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated cfgrib 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: Tue, 14 Dec 2021 15:37:37 +
Source: cfgrib
Architecture: source
Version: 0.9.9.1-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 973821 1000726
Changes:
 cfgrib (0.9.9.1-2) unstable; urgency=medium
 .
   * Fix for pandas > 1.3. Closes: #973821, #1000726
Checksums-Sha1:
 e2a043f11a44d21ab69d2e832272cb3b14aaafb8 2116 cfgrib_0.9.9.1-2.dsc
 80e24479430262fb06bf9aba2d6d680c701b5908 8552 cfgrib_0.9.9.1-2.debian.tar.xz
Checksums-Sha256:
 4c6a0b34b36715889a6b617647202f85a27d86a885f15a84baad18f8928f00a8 2116 
cfgrib_0.9.9.1-2.dsc
 11beff4b19f57eb8c470d51164d1e7d278cedd1f3eb6c88d89c547634e95ec64 8552 
cfgrib_0.9.9.1-2.debian.tar.xz
Files:
 d7895f5aabb834dea52d2a777166f16d 2116 python optional cfgrib_0.9.9.1-2.dsc
 6c46663ff2abc763409470d17a5bee6c 8552 python optional 
cfgrib_0.9.9.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmG4vHkACgkQy+a7Tl2a
06X9Wg//cq1JcehlkOkXfkh+9VZqGpIxwKHEpFHYr0Po2GM7FhvgSZK4JvMSfYap
X9GU7b6MrWUAdabSv8RLTYyGuXV7PXvdAMXGpAfckWLT7dxqYrz0DY9ZEi+QgXrF
DFsC/ep9ol+XIwCZx5HbXtZkRKbFAPylxneVadO36NwucqfX2cJqU9Ksffe4rtUd
N1oc72Ca2o3pWA74oMLwDN2u65w1MTTpBYFsIqGYN63gMJBDkPsOrycs26t3me79
erSfuyAb7E38duqpJmlcek8PG4ahynAAteXtfkJmX3CBSppYFQJ+n73swe0qaRxx
4JL2Ecp5W1MDb1lVQGhRFqaCX1q0YzZ50CnTKbKKSHk6eYHWOz9rS8qIrEGno4WV
A3V2GGjzbUUTCryHMKIgsc3fWxSoZQE4cS7Q9iGMJ+BQPH4NwCJfIolQeAli63X0
afXUOzZDYm0kUIudE21oOdC4mFNmZSjq1LxvkC+qG/5GoOyLP84rmcil3YkDOCOy
RYvuCDDdwieOMFLjbxBdk0uSmDC8MT6Rq5QhDLKEnPjr/24tMC2UvuQesV+e78rF
v/7aaEezaa9GwaVcsqOFciGz6Y7Xyxbe+GaRVVRw961BumPPvaarVNPwt3xlotRA
43OEhWdlb3qNuG3tmX69ZiHRCxBWH1V6h2POycQHhRcTARswXRs=
=XGeD
-END PGP SIGNATURE End Message ---

Bug#1001681: sight: FTBFS in unstable

[Flavien Bridault]

Hello Steve,

Thanks for the notice.

This comes from DCMTK. Maybe an API change or a move of a header. Do you 
want me to have a look ?


Cheers,


*Dr. Flavien BRIDAULT*
Director of Software Development
IRCAD France & IRCAD Africa

flavien.brida...@ircad.fr 
Tél. : +33 (0)3 88 119 201
IRCAD France
http://www.ircad.fr/
http://www.ircad.africa/ 

Suivez l'IRCAD sur Facebook 



*IRCAD France*
Hôpitaux Universitaires - 1, place de l'Hôpital - 67091 Strasbourg Cedex 
- FRANCE


Le 14/12/2021 à 08:37, Steve Langasek a écrit :

Source: sight
Version: 21.0.0-2
Severity: serious
User:ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy

Hi Flavien,

sight is failing to build in unstable right now with the following error:


cd /tmp/sight-21.0.0/obj-x86_64-linux-gnu/libs/io/dimse && /usr/bin/c++ 
-DBOOST_ALL_DYN_LINK -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_CHRONO_DYN_LINK 
-DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK 
-DBOOST_LOG_DYN_LINK -DBOOST_LOG_SETUP_DYN_LINK -DBOOST_REGEX_DYN_LINK 
-DBOOST_SPIRIT_USE_PHOENIX_V3 -DBOOST_THREAD_DONT_PROVIDE_DEPRECATED_FEATURES_SINCE_V3_0_0 
-DBOOST_THREAD_DYN_LINK -DBOOST_THREAD_PROVIDES_FUTURE -DBOOST_THREAD_VERSION=2 
-DIO_DIMSE_EXPORTS -Dio_dimse_EXPORTS 
-I/tmp/sight-21.0.0/obj-x86_64-linux-gnu/libs/io/dimse/include -I/tmp/sight-21.0.0/libs 
-I/tmp/sight-21.0.0/libs/core 
-I/tmp/sight-21.0.0/obj-x86_64-linux-gnu/libs/core/pch/pchData/include/pchData 
-I/tmp/sight-21.0.0/obj-x86_64-linux-gnu/libs/core/core/include -I/usr/include/libxml2 
-I/tmp/sight-21.0.0/obj-x86_64-linux-gnu/libs/core/data/include -g -O2 
-ffile-prefix-map=/tmp/sight-21.0.0=. -fstack-protector-strong -Wformat -Werror=format-security 
-Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC -fvisibility=hidden 
-fvisibility-inlines-hidden -march=sandybridge -mtune=generic -mfpmath=sse -fvisibility=hidden 
-fvisibility-inlines-hidden -Wall -Wextra -Wconversion -Wno-unused-parameter 
-Wno-ignored-qualifiers -std=gnu++17 -include "pch.hpp"  -Winvalid-pch -MD -MT 
libs/io/dimse/CMakeFiles/io_dimse.dir/SeriesEnquirer.cpp.o -MF 
CMakeFiles/io_dimse.dir/SeriesEnquirer.cpp.o.d -o CMakeFiles/io_dimse.dir/SeriesEnquirer.cpp.o -c 
/tmp/sight-21.0.0/libs/io/dimse/SeriesEnquirer.cpp
/tmp/sight-21.0.0/libs/io/dimse/SeriesEnquirer.cpp: In member function 'std::string 
sight::io::dimse::SeriesEnquirer::findSOPInstanceUID(const string&, unsigned 
int)':
/tmp/sight-21.0.0/libs/io/dimse/SeriesEnquirer.cpp:748:5: error: 'OFIterator' 
was not declared in this scope; did you mean 'OF_error'?
   748 | OFIterator it= responses.begin();
   | ^~
   | OF_error
/tmp/sight-21.0.0/libs/io/dimse/SeriesEnquirer.cpp:748:26: error: expected 
primary-expression before '*' token
   748 | OFIterator it= responses.begin();
   |  ^
/tmp/sight-21.0.0/libs/io/dimse/SeriesEnquirer.cpp:748:27: error: expected 
primary-expression before '>' token
   748 | OFIterator it= responses.begin();
   |   ^
/tmp/sight-21.0.0/libs/io/dimse/SeriesEnquirer.cpp:748:29: error: 'it' was not 
declared in this scope; did you mean 'io'?
   748 | OFIterator it= responses.begin();
   | ^~
   | io


I don't know where OFIterator is supposed to come from, but clearly
something has changed.

Cheers,

___
Debian-med-packaging mailing list
debian-med-packag...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging


OpenPGP_signature
Description: OpenPGP digital signature

Bug#999040: myspell-fa: missing required debian/rules targets build-arch and/or build-indep

[Salman Mohammadi]

On Tue, 09 Nov 2021 22:28:16 +0100 Lucas Nussbaum  
wrote:> Source: myspell-fa

> Version: 0.20070816-3.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
>
>


Hey Lucas,

The package is not in Salsa but is there a way that I can help keeping 
this package?



Cheers, Salman

Bug#997614: marked as done (python-parse-type: FTBFS: error in parse_type setup command: use_2to3 is invalid.)

[Debian Bug Tracking System]

Your message dated Tue, 14 Dec 2021 11:04:36 +
with message-id 
and subject line Bug#997614: fixed in python-parse-type 0.5.6-1
has caused the Debian Bug report #997614,
regarding python-parse-type: FTBFS: error in parse_type setup command: use_2to3 
is invalid.
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.)


-- 
997614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-parse-type
Version: 0.3.4-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:232: python3.9 setup.py clean 
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'upload-dir' will not be supported in future versions. Please 
> use the underscore name 'upload_dir' instead
>   warnings.warn(
> error in parse_type setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean --test-pytest -i python{version} -p 3.9 
> returned exit code 13
> make: *** [debian/rules:6: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-parse-type_0.3.4-3_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-parse-type
Source-Version: 0.5.6-1
Done: Christoph Berg 

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated python-parse-type 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: Tue, 14 Dec 2021 11:54:59 +0100
Source: python-parse-type
Architecture: source
Version: 0.5.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Christoph Berg 
Closes: 997614
Changes:
 python-parse-type (0.5.6-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 9 to 12.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Remove constraints unnecessary since stretch:
 + Build-Depends: Drop versioned constraint on dh-python.
 .
   [ Edward Betts ]
   * Correct github URLs in debian/control and debian/copyright
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Christoph Berg ]
   * New upstream version 0.5.6.
   * Remove obsolete use_2to3 marker. (Closes: #997614)
   * Bump python3-parse dependency to 1.19.0.
Checksums-Sha1:
 a7f0d992e4a0a3816bafe1174ec11e88c189be0b 2135 python-parse-type_0.5.6-1.dsc
 5b0f20408bdfb8d689faf12f9a1962eace9b81cf 270970 
python-parse-type_0.5.6.orig.tar.gz
 5999cc23e6ce546f569767b7826b01dae23ab619 3660 
python-parse-type_0.5.6-1.debian.tar.xz
Checksums-Sha256:
 d5577f804acaa38880081ce5c386f6a6f379f3bcdb9726b47dd9bc74d60449e3 2135 
python-parse-type_0.5.6-1.dsc
 12b75aa048595457fa5d15558c1a49a688ad4a585d5d1378b1aff4d99fb532ae 270970 

Processed: Bug#997614 marked as pending in python-parse-type

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997614 [src:python-parse-type] python-parse-type: FTBFS: error in 
parse_type setup command: use_2to3 is invalid.
Added tag(s) pending.

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

Bug#997614: marked as pending in python-parse-type

[Christoph Berg]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-parse-type/-/commit/f84cbe916839895c0db4d9610340bc33718527ef


New upstream version 0.5.6.

* Remove obsolete use_2to3 marker. (Closes: #997614)
* Bump python3-parse dependency to 1.19.0.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997614

Bug#1001643: Acknowledgement (sdaps: fails to setup a project with texlive-latex-extra/unstable (2021.2021127-1))

[Vincent-Xavier JUMEL]

In the comment https://github.com/sdaps/sdaps/issues/
238#issuecomment-993392198[1], sdaps author and maintener states that the 
package 
should not ship anymore these files

> Yes. The package should add a dependency to the LaTeX class. And then stop 
> setting --
build-tex and --install-tex in debian/rules.
> This was set earlier (in my own packages too), because TeXLive had a bug and 
> was 
missing a file.

-- 
Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net

Société Libre, Logiciel Libre http://www.april.org/adherer
Parinux, logiciel libre à Paris : http://www.parinux.org



[1] https://github.com/sdaps/sdaps/issues/238#issuecomment-993392198

Bug#991223: marked as done (modemmanager: missing policykit-1 in Depends or Recommends)

[Debian Bug Tracking System]

Your message dated Tue, 14 Dec 2021 10:04:33 +
with message-id 
and subject line Bug#991223: fixed in modemmanager 1.18.4-1
has caused the Debian Bug report #991223,
regarding modemmanager: missing policykit-1 in Depends or Recommends
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.)


-- 
991223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: modemmanager
Version: 1.10.0-1
Severity: serious
Justification: missing dependency

Hi,

A basic modemmanager installation doesn't result in a functional mmcli
command. The following might work (e.g. after a reboot, to make sure the
modem detection is fine):

# mmcli -L
/org/freedesktop/ModemManager1/Modem/0 [QUALCOMM INCORPORATED] QUECTEL 
Mobile Broadband Module

But trying to force a scan (e.g. before or instead of rebooting)
doesn't:

# mmcli -S
error: couldn't request to scan devices: 
'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Failed: PolicyKit 
authorization failed: 'GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: 
The name org.freedesktop.PolicyKit1 was not provided by any .service files''

Trying to establish a connection doesn't work either:

# mmcli -m 0 --simple-connect apn=orange
error: couldn't connect the modem: 
'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Failed: PolicyKit 
authorization failed: 'GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: 
The name org.freedesktop.PolicyKit1 was not provided by any .service files''

Given the error message, it's pretty clear the problem is at the D-Bus
level, so isn't actually limited to mmcli: trying to toy with the modem
over D-Bus directly (e.g. using Python bindings) would result in the
same problems.


It looks to me policykit-1 should be at least in Recommends, possibly in
Depends. This might have been unreported until since end users are
likely using NetworkManager from a desktop environment, and
network-manager does list policykit-1 in Depends.


I've double checked those findings with buster myself, but I'm told the
same happens with bullseye as well, which would be consistent with the
facts Depends/Recommends didn't change between buster's version and
bullseye's.

This would seem worth fixing in both distributions.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
--- End Message ---
--- Begin Message ---
Source: modemmanager
Source-Version: 1.18.4-1
Done: Arnaud Ferraris 

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

Debian distribution maintenance software
pp.
Arnaud Ferraris  (supplier of updated modemmanager 
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: Tue, 14 Dec 2021 10:09:29 +0100
Source: modemmanager
Architecture: source
Version: 1.18.4-1
Distribution: unstable
Urgency: medium
Maintainer: DebianOnMobile Maintainers 

Changed-By: Arnaud Ferraris 
Closes: 991223
Changes:
 modemmanager (1.18.4-1) unstable; urgency=medium
 .
   [ Cyril Brulebois ]
   * Fix missing dependency on policykit-1 (Closes: #991223).
 Without it, a lot of operations would result in the following error at
 the D-Bus level:
 The name org.freedesktop.PolicyKit1 was not provided by any .service 
files
 In bullseye, ModemManager.service wouldn't even start, because of the
 missing polkit.service dependency at the systemd level.
 .
   [ Arnaud Ferraris ]
   * New upstream version 1.18.4
   * d/copyright: fix wrong path for libqcdm
 `libqcdm` was previously `libwmc`, but the corresponding copyright entry
 wasn't updated when the folder was renamed.
   * d/control: update packages descriptions.
 As it was pointed out, ModemManager now supports 5G modems, make sure
 the packages descriptions reflect that.
   * debian: address lintian issues.
 This commit addresses multiple issues reported by lintian:
 - doc installed into `/usr/share/gtk-doc` instead 

Bug#995212: ungoogled-chromium? [was: Re: Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)]

[Jeff Blake]

On Tue, 7 Dec 2021 19:43:10 +0100 Tomas Pospisek  wrote:
> On 06.12.21 20:43, Noah Meyerhans wrote:
> > On Sun, Dec 05, 2021 at 07:58:17PM +0300, Dmitry Alexandrov wrote:
>  So what's happening with chromium in both sid and stable? I saw on 
>  d-release that it was removed from testing (#998676 and #998732), with a 
>   discussion about ending security support for it in stable.
> >>>
> >>> The problem really is lack of maintenance. In my opinion, chromium 
> >>> deserves an active *team* to support it in Debian.  <...>  The security 
> >>> team doesn't have the bandwidth to do it themselves, they need a team to 
> >>> help them.
> >>
> >> Sorry for a silly question, but whatʼs so wrong with the build done by 
> >> linuxmint.com [1], so Debian needs a whole team to duplicate their effort? 
> >>  Itʼs for Debian 10 (i. e. oldstable) as of now, but works fine at Sid in 
> >> my (limited) experience.
> >>
> > 
> > Well, you can start with the fact that the Mint chromium source packages
> > don't even include the chromium source, let alone the sources for all
> > the other things they build (NodeJS, and more).
> > 
> > The biggest difficulty, as far as I can tell from my look at Chromium
> > from several months ago, is that our patch set [1] needs a lot of
> > attention with every chromium release.  Mint doesn't apply any patches
> > at all to the source, at least none of any real complexity.
> > 
> > One lesson we may take from Mint, though, is that it's not worth trying
> > to patch Chromium as much as we'd like.  Anything that we can do to
> > simplify the Chromium packaging will help us keep the package
> > up-to-date, which in turn will help us keep our users safer.  In my
> > opinion, we should be pretty aggressive about dropping as many of the
> > Chromium patches as possible, even if that means we link against
> > bundled/vendored dependencies.
> > 
> > Legal/licensing considerations are still important and I don't know if
> > we actually *can* ship builds based on the bundled stuff.  But based on
> > the number of patches we have to disable various things [2] or build
> > against system dependencies [3], I can't help but think we'd have an
> > easier time keeping this package fresh if we could drop some of those.
> > 
> > noah
> > 
> > 1. 
> > https://salsa.debian.org/chromium-team/chromium/-/blob/master/debian/patches/series
> > 2. 
> > https://salsa.debian.org/chromium-team/chromium/-/tree/master/debian/patches/disable
> > 3. 
> > https://salsa.debian.org/chromium-team/chromium/-/tree/master/debian/patches/system
> 
> I'd also like to point out, that the ungoogled-chromium project has some 
> overlap in goals with Debian and it'd possibly be interessing to join 
> forces:
> 
> https://github.com/ungoogled-software/ungoogled-chromium-debian
> 
> (I have been running an ungoogled-chromium for a while (ca. a year 
> ago?), however at that time their chrome wasn't extremely stable so I 
> gave up again. Does anybody have experience using it recently?)
> *t
> 
> 
> 


I have recently forked the debian version of ungoogled chromium [1] [2] [3] to 
(amongst other reasons) re-incorporate many of the previous debian patches and 
features [4].

I haven't had any of the major problems which have blocked the main upstream 
version of it 
over the last couple of release, and the latest chromium version builds and 
runs on both 
unstable and stable.

Most of the debian patches aren't too much bother to update, and are mainly 
context changes. 
Many of them seem worth having, but several are problematic, and if anyone 
wants to make 
maintenance easier then the low hanging fruit to delete for enhanced 
maintainability is as 
follows.


## Plainly not a good idea
debianization/optimization.patch
system/use-desktop-gl-as-default.patch

## Too complex or not worth the trouble to maintain
fixes/inspector.patch
fixes/widevine-revision.patch
system/convertutf.patch

## GCC specific
fixes/gnu-as.patch
warnings/int-in-bool-context.patch
warnings/stringop-overflow.patch

# System lib replacements which are too changeable and/or incompatible between 
stable/unstable
bullseye/ffmpeg.patch
bullseye/icu-types.patch
system/clang-format.patch
system/ffmpeg.patch
system/harfbuzz.patch


Upstream is better placed to judge optimisation levels per build target, and 
all you'll 
achieve with a flat '-O2 everywhere' is a slower binary. With upstream bundled 
clang 
(discussed below) dpkg buildflags doesn't appear to be picked up by the build 
system anyway.

The desktop gl patch is questionable since it can be set as a runtime flag in 
the existing 
debian/etc/default-flags file.

Inspector and convertutf are the worst offenders in terms of being unnecessary 
and complex. 
The disable/catapult.patch could also be dropped, since profiling might be 
desirable to some 
users.

Using gcc to build chromium was dropped by debian ages ago and is not supported 
upstream, so 
I don't see the point in patching gcc-related build 

Processed: severity of 946412 is important

[Debian Bug Tracking System]

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

> severity 946412 important
Bug #946412 [src:janus] janus-gateway: upstream does not support stable releases
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: severity of 999172 is important

[Debian Bug Tracking System]

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

> severity 999172 important
Bug #999172 [src:toppler] toppler: missing required debian/rules targets 
build-arch and/or build-indep
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: binstats: diff for NMU version 1.08-9.1

[Debian Bug Tracking System]

Processing control commands:

> tags 999022 + patch
Bug #999022 [src:binstats] binstats: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 999022 + pending
Bug #999022 [src:binstats] binstats: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999022: binstats: diff for NMU version 1.08-9.1

[Stephen Kitt]

Control: tags 999022 + patch
Control: tags 999022 + pending

Dear maintainer,

I've prepared an NMU for binstats (versioned as 1.08-9.1) and
uploaded it to DELAYED/15. Please feel free to tell me if I
should delay it longer; you can of course also replace this with your
own upload.

Regards,

Stephen
diff -u binstats-1.08/debian/changelog binstats-1.08/debian/changelog
--- binstats-1.08/debian/changelog
+++ binstats-1.08/debian/changelog
@@ -1,3 +1,10 @@
+binstats (1.08-9.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch to short dh rules. Closes: #999022.
+
+ -- Stephen Kitt   Tue, 14 Dec 2021 08:56:38 +0100
+
 binstats (1.08-9) unstable; urgency=low
 
   * Acknowledge NMU
diff -u binstats-1.08/debian/rules binstats-1.08/debian/rules
--- binstats-1.08/debian/rules
+++ binstats-1.08/debian/rules
@@ -1,53 +1,10 @@
 #! /usr/bin/make -f
 
-export CFLAGS="-O2 -g -Wall"
-export LDFLAGS=""
+%:
+	dh $@
 
-clean:
-	dh_testdir
-	dh_testroot
-	dh_clean
-	make clean
+# We only ship the shell script, there's nothing to build
+override_dh_auto_build:
 
-build:
-	make 
-
-binary:  binary-indep
-
-binary-indep: 
-	dh_testdir 
-	dh_testroot
-	dh_clean 
-	dh_installdirs  usr/bin 
-	cp -p binstats debian/binstats/usr/bin
-	dh_installdocs README
-	dh_installman binstats.1
-	dh_installchangelogs
-	dh_strip
-	dh_compress
-	dh_fixperms
-	dh_installdeb
-	dh_gencontrol
-	dh_md5sums
-	dh_builddeb
-
-binary-arch: build
-	dh_testdir 
-	dh_testroot
-	dh_clean 
-	dh_installdirs  usr/bin usr/share/man/man1
-	make install DESTBIN=`pwd`/debian/binstats/usr/bin \
-	   	 DESTMAN=`pwd`/debian/binstats/usr/share/man/man1
-	cp -p binstats debian/binstats/usr/bin
-	dh_installdocs README
-	dh_installman binstats.1
-	dh_installchangelogs
-	dh_strip
-	dh_compress
-	dh_fixperms
-	dh_installdeb
-	dh_gencontrol
-	dh_md5sums
-	dh_builddeb
-
-.PHONY: clean build binary binary-arch binary-indep
+# Everything is installed through debhelper
+override_dh_auto_install:
reverted:
--- binstats-1.08/debian/rules.tiny
+++ binstats-1.08.orig/debian/rules.tiny
@@ -1,3 +0,0 @@
-#!/usr/bin/make -f
-%:
-	dh $@
only in patch2:
unchanged:
--- binstats-1.08.orig/debian/docs
+++ binstats-1.08/debian/docs
@@ -0,0 +1 @@
+README
only in patch2:
unchanged:
--- binstats-1.08.orig/debian/install
+++ binstats-1.08/debian/install
@@ -0,0 +1 @@
+binstats /usr/bin
only in patch2:
unchanged:
--- binstats-1.08.orig/debian/manpages
+++ binstats-1.08/debian/manpages
@@ -0,0 +1 @@
+binstats.1


signature.asc
Description: PGP signature