Bug#1012061: marked as done (coq breaks coquelicot autopkgtest: Compiled library Coquelicot.Rcomplements makes inconsistent assumptions over library Coq.Init.Ltac)

[Debian Bug Tracking System]

Your message dated Thu, 02 Jun 2022 05:37:58 +
with message-id 
and subject line Bug#1012061: fixed in coquelicot 3.2.0-4
has caused the Debian Bug report #1012061,
regarding coq breaks coquelicot autopkgtest: Compiled library 
Coquelicot.Rcomplements makes inconsistent assumptions over library 
Coq.Init.Ltac
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.)


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

Source: coq, coquelicot
Control: found -1 coq/8.15.1+dfsg-2
Control: found -1 coquelicot/3.2.0-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
coqfrom testing8.15.1+dfsg-2
coquelicot from testing3.2.0-2
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 coq 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=coq

https://ci.debian.net/data/autopkgtest/testing/amd64/c/coquelicot/22188156/log.gz

File "./BacS2013.v", line 24, characters 0-112:
Error:
Compiled library Coquelicot.Rcomplements (in file 
/usr/lib/ocaml/coq/user-contrib/Coquelicot/Rcomplements.vo) makes 
inconsistent assumptions over library Coq.Init.Ltac


autopkgtest [11:12:10]: test examples



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: coquelicot
Source-Version: 3.2.0-4
Done: Julien Puydt 

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated coquelicot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 Jun 2022 07:10:00 +0200
Source: coquelicot
Architecture: source
Version: 3.2.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Julien Puydt 
Closes: 1012061
Changes:
 coquelicot (3.2.0-4) unstable; urgency=medium
 .
   * Re-upload because of ABI breakage. (Closes: #1012061)
Checksums-Sha1:
 16c87168968764894d327b220b32ef4984b1a784 2048 coquelicot_3.2.0-4.dsc
 dbc551d3ab396f274458dc9bb95ff6b69e4a2e74 2244 coquelicot_3.2.0-4.debian.tar.xz
 75c6b2658f0b36c7072129d47a277e20afe4170e 6764 
coquelicot_3.2.0-4_source.buildinfo
Checksums-Sha256:
 66d93e47035a8510e7c074a193bfd606b4386c319adfb52e7a4be12e5805af80 2048 
coquelicot_3.2.0-4.dsc
 573d6f8731cd8dee3034c326aabf7687874df818842b9c15bbc62ae287697170 2244 
coquelicot_3.2.0-4.debian.tar.xz
 c81b61c8c23151c252aece20d9c3600c080960320335db2bd0cfb7cf500d5636 6764 
coquelicot_3.2.0-4_source.buildinfo
Files:
 06d03f3882b62fe64d01dd9ad5bb0d19 2048 ocaml optional coquelicot_3.2.0-4.dsc
 7c56151c47c25b5a6ad7829ff7fb64d4 2244 ocaml optional 
coquelicot_3.2.0-4.debian.tar.xz
 6a37c44936e4fc8e88fdde910cff2596 6764 ocaml optional 
coquelicot_3.2.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmKYRjwSHGpwdXlkdEBk
ZWJpYW4ub3JnAAoJEATFO9f+AwVRADMQAJZXX9y0fNtGlwGCkcJkBTn2eRrLf7c0
aKhp7F9caF14tXQV7coRK2KBinmrF0lxOwhjeOM8H5iPH9ieS4V7o8nBJTGq2SyH
/mDR/QwmoCyFh4E51kASptaXsO1GkFwLaOBdRrjvmDjzjqsEYJBVollTgTpNGt3t
eQP5fe/QBVqBO1zrXQevAZoogxQ1ceJvHadzF0jhu9hvaPiARqCawMbkm6ppxR/v
2z3Im5e6uQDGSwbRcuuz7W2eDCenzzq3B8thvvQsCKdiwUjbUMuSO3eCXGG+8owU

Bug#1012231: tinyows: FTBFS: problems with boolean types and constants

[Sebastiaan Couwenberg]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/MapServer/tinyows/issues/98

On 6/2/22 02:00, Andreas Beckmann wrote:

tinyows recently started to FTBFS after some build-dependency got
updated:


Thanks for reporting this issue, I've forwarded it upstream.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: Re: Bug#1012231: tinyows: FTBFS: problems with boolean types and constants

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #1012231 [src:tinyows] tinyows: FTBFS: problems with boolean types and 
constants
Added tag(s) upstream.
> forwarded -1 https://github.com/MapServer/tinyows/issues/98
Bug #1012231 [src:tinyows] tinyows: FTBFS: problems with boolean types and 
constants
Set Bug forwarded-to-address to 
'https://github.com/MapServer/tinyows/issues/98'.

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

Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies

[Andreas Beckmann]

On 27/05/2022 16.22, Andreas Beckmann wrote:
> On 27/05/2022 10.59, Paul Gevers wrote:
>>> My guess is that apt pinning comes into play here, installing
>>
>> That aligns with my suspicion that it's related to the mixing of
>> unstable and testing.
> 
> Uploaded a first attempt on the fix. Works for me, let's see how ci.d.o
> likes it. There are probably still corner cases to be handled ...

Looks not too bad.

Current problems:

lime-forensics: used dkms-autopkgtest manually, not via
  Testsuite: autopkgtest-pkg-dkms
merge-request !2
(only autopkgtest buggy, module builds fine)

r8125: bug #1012014 - r8125: fails to build module for Linux 5.17
(new upstream release available)

nvidia-graphics-drivers-tesla-470: fails on ppc64el due to transitive
GPL symbol usage, reported upstream

nvidia-graphics-drivers-tesla-510: improved version in experimental, but
has the same problem on ppc64el as 470 (not yet in sid due to moving a
package from nvidia-graphics-drivers to -tesla-510)
feel free to temporarily remove from testing

Since these bugs (modules failing to build) are already present in
testing and only exposed by the new dkms by making the autopkgtest run
no longer a no-op, perhaps you could just ignore the failing tests and
hint dkms into testing? (-tesla-510 would need some forced hint for
reintroduction into testing as well, since I don't think an upstream fix
for ppc64el will be available in time when I move
nvidia-graphics-drivers from 470 to 510 as default in sid)


Andreas

Bug#992786: passenger uses many vendored libraries

[Antonio Terceiro]

Control: severity -1 important

Hi,

On Mon, Aug 23, 2021 at 03:00:16PM +0300, Adrian Bunk wrote:
> Source: passenger
> Severity: serious
> 
> passenger-5.0.30/src/cxx_supportlib/vendor-copy:
> adhoc_lve.h  libcurl  libuv  nghttp2  utf8  utf8.h
> 
> passenger-5.0.30/src/cxx_supportlib/vendor-modified:
> SmallVector.h  jsoncpp  modp_b64.cpp  modp_b64_data.h
> boost  libevmodp_b64.hpsg_sysqueue.h
> 
> passenger-6.0.10/src/cxx_supportlib/vendor-copy:
> adhoc_lve.h  libuv  utf8  utf8.h  websocketpp
> 
> passenger-6.0.10/src/cxx_supportlib/vendor-modified:
> boostlibev modp_b64.h   modp_b64_strict_aliasing.cpp
> jsoncpp  modp_b64.cpp  modp_b64_data.h  psg_sysqueue.h
> 
> 
> The problem is that these vendored copies seem to actually be used.
> 
> Does for example CVE-2021-22918 in libuv1 need fixing in passenger?

6.0.13+ds-1 drops the embedded copies of both libuv and libev, who seem
to be the most high-profile libraries; and it's now actually possible to
build passenger against system-provided copies of those.

There is still an embeded copy of boost, but that's modified from
upstream boost in a way that the code does not build about system boost.

Ideally we would want to drop all of the other embeded copies, but
realistically that would involve a amount of work that is not available
at the moment.

Because this is still a relevant issue, but IMO not worth removing
passenger because of it, I am downgrading this bug to important.


signature.asc
Description: PGP signature

Bug#1012233: python3-ml-collections: overly generic python module name: /usr/lib/python3/dist-packages/docs/conf.py

[Andreas Beckmann]

Package: python3-ml-collections
Version: 0.1.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package uses a very generic
python module name that now clashes with other packages:

/usr/lib/python3/dist-packages/docs/conf.py


Andreas

Processed: Re: Bug#992786: passenger uses many vendored libraries

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #992786 [src:passenger] passenger uses many vendored libraries
Severity set to 'important' from 'serious'

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

Bug#1012232: freespace2: FTBFS: ./configure: line 17040: syntax error near unexpected token `ax_cxx_compile_cxx11_required=falsednl'

[Andreas Beckmann]

Source: freespace2
Version: 3.7.4+repack-1.1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source

Hi,

freespace2 recently started to FTBFS after some (transitive) build
dependency got updated:

[...]
checking how to hardcode library paths into programs... immediate
./configure: line 17040: syntax error near unexpected token 
`ax_cxx_compile_cxx11_required=falsednl'
./configure: line 17040: `ax_cxx_compile_cxx11_required=falsednl'
[...]


Andreas


freespace2_3.7.4+repack-1.1.log.gz
Description: application/gzip

Bug#1012231: tinyows: FTBFS: problems with boolean types and constants

[Andreas Beckmann]

Source: tinyows
Version: 1.2.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

tinyows recently started to FTBFS after some build-dependency got
updated:

   dh_auto_build
make -j3
make[1]: Entering directory '/build/tinyows-1.2.0'
gcc -g -O2 -ffile-prefix-map=/build/tinyows-1.2.0=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c99 -pedantic -Wall -I/usr/include/postgre
sql -I/usr/include/libxml2   src/fe/fe_comparison_ops.c src/fe/fe_error.c 
src/fe/fe_filter.c src/fe/fe_filter_capabilities.c src/fe/fe_function.c 
src/fe/fe_logical_ops.c src/fe/fe_spatial_ops.c src/mapfile/mapfile
.c src/ows/ows_bbox.c src/ows/ows.c src/ows/ows_config.c src/ows/ows_error.c 
src/ows/ows_geobbox.c src/ows/ows_get_capabilities.c src/ows/ows_layer.c 
src/ows/ows_metadata.c src/ows/ows_psql.c src/ows/ows_request.c
 src/ows/ows_srs.c src/ows/ows_storage.c src/ows/ows_version.c 
src/struct/alist.c src/struct/array.c src/struct/buffer.c 
src/struct/cgi_request.c src/struct/list.c src/struct/mlist.c 
src/struct/regexp.c src/wfs/wf
s_describe.c src/wfs/wfs_error.c src/wfs/wfs_get_capabilities.c 
src/wfs/wfs_get_feature.c src/wfs/wfs_request.c src/wfs/wfs_transaction.c 
src/ows/ows_libxml.c -o tinyows -lfl -L/usr/lib/x86_64-linux-gnu -lpq -lxml
2 -lfcgi
In file included from /usr/include/unicode/umachine.h:52,
 from /usr/include/unicode/utypes.h:38,
 from /usr/include/unicode/ucnv_err.h:88,
 from /usr/include/unicode/ucnv.h:51,
 from /usr/include/libxml2/libxml/encoding.h:31,
 from /usr/include/libxml2/libxml/parser.h:812,
 from /usr/include/libxml2/libxml/globals.h:18,
 from /usr/include/libxml2/libxml/threads.h:35,
 from /usr/include/libxml2/libxml/xmlmemory.h:218,
 from /usr/include/libxml2/libxml/tree.h:1307,
 from /usr/include/libxml2/libxml/xmlreader.h:14,
 from src/fe/../ows/ows.h:30,
 from src/fe/fe_comparison_ops.c:29:
src/fe/../ows/../ows_struct.h:33:3: error: expected identifier before numeric 
constant
   33 |   false,
  |   ^
src/fe/../ows/../ows_struct.h:37:19: error: two or more data types in 
declaration specifiers
   37 | typedef enum Bool bool;
  |   ^~~~
In file included from src/fe/../ows/ows.h:38,
 from src/fe/fe_comparison_ops.c:29:
src/fe/../ows/../ows_struct.h:37:14: warning: empty declaration with storage 
class specifier does not redeclare tag
   37 | typedef enum Bool bool;
  |  ^~~~
[...]


Andreas


tinyows_1.2.0-1.log.gz
Description: application/gzip

Processed: Re: [Debian Bug Tracking System] Bug#1011545 closed by Debian FTP Masters (reply to Anthony Fok ) (Bug#1011545: fixed in gh 2.4.0+dfsg1-3)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1011545 {Done: Anthony Fok } [gh] please version the 
Conflicts: with gitsome
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions gh/2.4.0+dfsg1-3.
> severity -1 important
Bug #1011545 [gh] please version the Conflicts: with gitsome
Severity set to 'important' from 'serious'

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

Bug#1011545: [Debian Bug Tracking System] Bug#1011545 closed by Debian FTP Masters (reply to Anthony Fok ) (Bug#1011545: fixed in gh 2.4.0+dfsg1-3)

[Anthony Fok]

Control: reopen -1
Control: severity -1 important

Hi Antoine!

Thank you for your quick response!

On Tue, May 31, 2022 at 9:58 AM Antoine Beaupré  wrote:
>
> Hum. Now I'm a little confused: why did you do this?
>
> * Add diversion for /usr/bin/gh to allow concurrent install with gitsome
>   and remove Conflicts with gitsome. This is inspired by the conflict
>   resolution between the moreutils and parallel packages where both
>   contain /usr/bin/parallel.  See discussions in #749355.

This is an idea that has been brewing in my mind some weeks ever since
I came to realize Debian has two "parallel" programs while working on
, and thought
to myself, if moreutils and (GNU) parallel can do it, why can't
gitsome and (GitHub's) gh?

But I was too busy with work, and also not sure how to break the file
conflict deadlock in #1005858 (especially with the manual block to
both packages), so I didn't act on it.
Many thanks to you for getting us out of that embarrassing situation!

So, as I was dealing with this new bug that you opened, my old idea
came back to me again, I decided to give it a try, for better or for
worse.  The changelog is a reflection of the Git commits that I made
in that order...  

> This seems like it's the opposite of what I was suggesting in the bug
> report (#1011545). And you even refer to that bug report in the
> changelog:
>
> * Limit "Conflicts: gitsome" to older (<< 0.8.0+ds-7.1) versions.
>   Thanks to Antoine Beaupre for the suggestion, and for resolving the
>   file conflict with gitsome (#1005858) so amicably! (Closes: #1011545)
>
> What actually happened, from what I can tell, is that you just removed
> the Conflicts... I don't think that's the right resolution here: gitsome
> has been fixed, in unstable, and gh doesn't need to go around with fancy
> diversion stuff, because we're *precisely* not in a situation like
> moreutils and parallel...

Thank you for clarifying to me that it is a different situation than
moreutils and parallel.

>From my understanding of the gitsome, the "gitsome" command itself is
mostly just a wrapper that calls xonsh, and gitsome's main
functionalities are actually in the "/usr/bin/gh" Python executable,
so perhaps removing /usr/bin/gh altogether in some sense cripples the
gitsome package, and a rename to /usr/bin/gh.gitsome or something else
would be more appropriate.

That said, I now agree with you that renaming gitsome's /usr/bin/gh
via dpkg-divert from GitHub CLI gh package is not the right way to go,
particularly because the /usr/bin/gh meaning different things
depending on which packages are installed (just gitsome or both
gitsome and gh) can be very confusing.)

> Could this change be reverted?

Yes, most definitely!  I will do it ASAP.

After that, I will probably try to work on the gitsome package too and
install its gh as /usr/bin/gh.gitsome and hopefully get its
command-line completion to work with the name change, but that's
unrelated to this particular bug report and to GitHub CLI gh.  Let's
keep this package clean and free of the fancy and confusing diversion
stuff.  :-)

Thanks again for writing to me and put some common sense back into me!

Cheers,

Anthony Fok


> --
> When I came back to the United States, I decided that if you could use
> propaganda for war, you could certainly use it for peace. And
> "propaganda" got to be a bad word because of the Germans using it, so
> what I did was to try and find some other words so we found the words
> "public relations".  - Edward Bernays
>
>
>
>
>
> -- Forwarded message --
> From: Debian Bug Tracking System 
> To: Antoine Beaupre 
> Cc:
> Bcc:
> Date: Tue, 31 May 2022 15:51:05 +
> Subject: Bug#1011545 closed by Debian FTP Masters 
>  (reply to Anthony Fok ) 
> (Bug#1011545: fixed in gh 2.4.0+dfsg1-3)
> This is an automatic notification regarding your Bug report
> which was filed against the gh package:
>
> #1011545: please version the Conflicts: with gitsome
>
> It has been closed by Debian FTP Masters  
> (reply to Anthony Fok ).
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters 
>  (reply to Anthony Fok ) by
> replying to this email.
>
>
> --
> 1011545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011545
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Debian FTP Masters 
> To: 1011545-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Tue, 31 May 2022 15:49:21 +
> Subject: Bug#1011545: fixed in gh 2.4.0+dfsg1-3
> Source: gh
> Source-Version: 2.4.0+dfsg1-3
> Done: Anthony Fok 
>
> We believe that the bug you reported is fixed in the latest version of
> gh, which is due to be installed in the Debian FTP archive.
>
> A summary of the 

Bug#1012018: texlive-bin: FTBFS during separate binary-indep build

[Hilmar Preuße]

Am 28.05.2022 um 21:53 teilte Andreas Beckmann mit:

Hi,


Looks like you need to move some bits that are irrelevant for the
binary-indep build to a override_dh_install-arch (or probably
better execute_after_dh_install-arch) target.

Our build system did not change between TL 2021 & 2022. The only 
difference is, that we introduced some transitional packages, which are 
of arch "all" and hence the sbuild is started for arch "all". Now the 
d/rules files makes some assumption about, which files are there after 
build, which differs between arch "any" and "all".
What would work is to convert the transitional packages into arch "any", 
but I'm pretty sure some people would not like the idea.


Hilmar
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1009430: marked as done (pyml: FTBFS: Test 'run file with filename' ... fails (?))

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 21:14:22 +
with message-id 
and subject line Bug#1009430: fixed in pyml 20220325-1
has caused the Debian Bug report #1009430,
regarding pyml: FTBFS: Test 'run file with filename' ... fails (?)
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dune runtest -p pyml
>  numpy_tests alias runtest
> Environment variables:
> PATH=/<>/_build/install/default/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> PYTHONHOME not set
> DYLD_LIBRARY_PATH not set
> DYLD_FALLBACK_LIBRARY_PATH not set
> Initializing library...
> Temporary set 
> PYTHONPATH=":/usr/lib/python310.zip:/usr/lib/python3.10:/usr/lib/python3.10/lib-dynload:/usr/local/lib/python3.10/dist-packages:/usr/lib/python3/dist-packages".
> Trying to load "/usr/lib/x86_64-linux-gnu/libpython3.10.so.1.0".
> Library "/usr/lib/x86_64-linux-gnu/libpython3.10.so.1.0" has been loaded.
> Not a debug build.
> Starting tests...
> Test 'of_bigarray' ... disabled: numpy is not available
> Test 'of_bigarray2' ... disabled: numpy is not available
> Test 'to_bigarray' ... disabled: numpy is not available
> Test 'to_bigarray2' ... disabled: numpy is not available
> Test 'to_bigarray invalid type' ... disabled: numpy is not available
>   pyml_tests alias runtest (got signal SEGV)
> (cd _build/default && ./pyml_tests.exe)
> Environment variables:
> PATH=/<>/_build/install/default/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> PYTHONHOME not set
> DYLD_LIBRARY_PATH not set
> DYLD_FALLBACK_LIBRARY_PATH not set
> Initializing library...
> Temporary set 
> PYTHONPATH=":/usr/lib/python310.zip:/usr/lib/python3.10:/usr/lib/python3.10/lib-dynload:/usr/local/lib/python3.10/dist-packages:/usr/lib/python3/dist-packages".
> Trying to load "/usr/lib/x86_64-linux-gnu/libpython3.10.so.1.0".
> Library "/usr/lib/x86_64-linux-gnu/libpython3.10.so.1.0" has been loaded.
> Not a debug build.
> Starting tests...
> Test 'version' ... Python version 3.10.4 (main, Apr  2 2022, 09:04:19) [GCC 
> 11.2.0]
> passed
> Test 'library version' ... Python library version 3.10.4 (main, Apr  2 2022, 
> 09:04:19) [GCC 11.2.0]
> passed
> Test 'hello world' ... passed
> Test 'class' ... passed
> Test 'empty tuple' ... passed
> Test 'make tuple' ... passed
> Test 'module get/set/remove' ... passed
> Test 'capsule' ... passed
> Test 'capsule-conversion-error' ... passed
> Test 'exception' ... passed
> Test 'ocaml exception' ... passed
> Test 'ocaml exception with traceback' ... passed
> Test 'restore with null' ... passed
> Test 'ocaml other exception' ... passed
> Test 'run file with filename' ... 
> make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/04/12/pyml_20211015-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220412=lu...@debian.org=1=1=1=1#results

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

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

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

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

Debian distribution maintenance software
pp.
Ralf Treinen  (supplier of updated pyml package)

(This message was 

Bug#1012226: unattended-upgrades: flaky autopkgtest: kernel-patterns seems to regularly get confused

[Paul Gevers]

Source: unattended-upgrades
Version: 2.8
Severity: serious

Dear maintainer,

unattended-upgrades showed up in the stable-proposed queue viewer [1]
because it appears to regress with the new xz-utils. However,
inspecing other failures in other suites, I think the test doesn't
behave well in archives where there are more than one version of
src:linux available. This happens regularly in pure unstable, in
unstable-to-testing and in stable-proposed-to-stable testing.

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

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

Paul 

[1] https://release.debian.org/proposed-updates/stable.html

Bug#1012018: texlive-bin: FTBFS during separate binary-indep build

[Hilmar Preuße]

Am 28.05.2022 um 21:53 teilte Andreas Beckmann mit:

Hi Andreas,


texlive-bin fails to build the arch-indep packages during a separate run
as would be done by the buildds.

Many thanks for the report! Unfortunately it came to me very late as the 
mailing list does not like large E-Mails containing build logs. Please 
avoid attaching large log files.


Hilmar
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:xwayland: fails to migrate to testing for too long: unresolved RC bug

[Debian Bug Tracking System]

Processing control commands:

> close -1 2:22.1.1-1
Bug #1012225 [src:xwayland] src:xwayland: fails to migrate to testing for too 
long: unresolved RC bug
Marked as fixed in versions xwayland/2:22.1.1-1.
Bug #1012225 [src:xwayland] src:xwayland: fails to migrate to testing for too 
long: unresolved RC bug
Marked Bug as done
> block -1 by 1008992
Bug #1012225 {Done: Paul Gevers } [src:xwayland] 
src:xwayland: fails to migrate to testing for too long: unresolved RC bug
1012225 was not blocked by any bugs.
1012225 was not blocking any bugs.
Added blocking bug(s) of 1012225: 1008992

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

Bug#1012225: src:xwayland: fails to migrate to testing for too long: unresolved RC bug

[Paul Gevers]

Source: xwayland
Version: 2:22.1.0-1
Severity: serious
Control: close -1 2:22.1.1-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1008992

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:xwayland has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. The migration of your package is 
blocked by an unresolved RC 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=xwayland



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1012215: gradle-debian-helper: unknown option --add-opens breaks OpenJDK 11 packages

[Markus Koschany]

Am Mittwoch, dem 01.06.2022 um 17:36 +0200 schrieb Emmanuel Bourg:
> gradle-debian-helper/2.2 already checks if the JDK supports modules before
> adding the --add-opens options, but it checks the default JDK and not the one
> specified by JAVA_HOME, that's why it fails when OpenJDK 8 is used.

ok, cool. Thanks for fixing it!


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

Bug#1012215: gradle-debian-helper: unknown option --add-opens breaks OpenJDK 11 packages

[Emmanuel Bourg]

gradle-debian-helper/2.2 already checks if the JDK supports modules before 
adding the --add-opens options, but it checks the default JDK and not the one 
specified by JAVA_HOME, that's why it fails when OpenJDK 8 is used.

Bug#1012077: add one riscv CPU info for linuxinfo package, T-HEAD XuanTie C910

[Helge Kreutzmann]

Hello all,
I'll work on this at the weekend, thanks for providing the
information, it is highly helpful!

Best greetings

 Helge



-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#1011458: marked as done (snowflake: CVE-2022-29222 - fails to reject untrustworthy client certificates due to missing checks on private key)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 18:19:18 +
with message-id 
and subject line Bug#1011458: fixed in snowflake 2.2.0-1
has caused the Debian Bug report #1011458,
regarding snowflake: CVE-2022-29222 - fails to reject untrustworthy client 
certificates due to missing checks on private key
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.)


-- 
1011458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: snowflake
Version: 1.1.0-2
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: codeh...@debian.org, Debian Security Team 


Hi,

The following vulnerability was published for snowflake.

CVE-2022-29222[0]:
| Pion DTLS is a Go implementation of Datagram Transport Layer Security.
| Prior to version 2.1.5, a DTLS Client could provide a Certificate that
| it doesn't posses the private key for and Pion DTLS wouldn't reject
| it. This issue affects users that are using Client certificates only.
| The connection itself is still secure. The Certificate provided by
| clients can't be trusted when using a Pion DTLS server prior to
| version 2.1.5. Users should upgrade to version 2.1.5 to receive a
| patch. There are currently no known workarounds.


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

For further information see:

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

Please adjust the affected versions in the BTS as needed.


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

Kernel: Linux 5.17.0-2-amd64 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: snowflake
Source-Version: 2.2.0-1
Done: Ruben Pollan 

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

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

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

Debian distribution maintenance software
pp.
Ruben Pollan  (supplier of updated snowflake package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 26 May 2022 15:50:00 +0200
Source: snowflake
Architecture: source
Version: 2.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers 

Changed-By: Ruben Pollan 
Closes: 1011457 1011458
Changes:
 snowflake (2.2.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Update vendored code solving CVE-2022-29189, CVE-2022-29190,
 CVE-2022-29222. (Closes: #1011458, #1011457)
   * Remove proxy patch included in upstream.
Checksums-Sha1:
 abe5c0a88a60b9599617396e6576f5796dae7c0c 2262 snowflake_2.2.0-1.dsc
 02a96ed5bc3b2055dc305956b70da7a1d683b8eb 148757 snowflake_2.2.0.orig.tar.gz
 71891af98715f691ec2265373aed701230be44a9 405248 snowflake_2.2.0-1.debian.tar.xz
 1c5346f7db3540a3bbc4abbb082a1f93b601e27c 8921 snowflake_2.2.0-1_amd64.buildinfo
Checksums-Sha256:
 8c7149c123f1054c25d3e6aeb5e16127aae172895cb1b2a0631fcd5bd64709ea 2262 
snowflake_2.2.0-1.dsc
 2310fc18fb5197007d9c49577604af5fad1b5e1826a8136aa7930dddace7860c 148757 
snowflake_2.2.0.orig.tar.gz
 cf6f3a4b4bab1be2b0f838ec1ad6ee3b9aa19713bb15b7220ede17db6014290d 405248 
snowflake_2.2.0-1.debian.tar.xz
 2123306ed636445962e5ff4a1cb62143ac9f5a1206e7aef2d9d3bfc6ebe40d05 8921 
snowflake_2.2.0-1_amd64.buildinfo
Files:
 cb188b23a637c0ad974aa384c79c7a6c 2262 golang optional snowflake_2.2.0-1.dsc
 d4f36bfb7ca2c5c1d8bf3475fc5b1bda 148757 golang optional 
snowflake_2.2.0.orig.tar.gz
 a06d081f22a22ec8920cc4ef364e520e 405248 golang optional 
snowflake_2.2.0-1.debian.tar.xz
 4d57acc2654c3a788fdef0295f9e3926 8921 golang optional 
snowflake_2.2.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAmKXp64ACgkQPqHd3bJh

Bug#1012224: python-tornado: autopkgtest regression in testing

[Graham Inggs]

Source: python-tornado
Version: 6.1.0-3
Severity: serious
Tags: ftbfs
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Sometime around 2022-05-08, python-tornado's autopkgtests regressed in
testing [1].
I've copied what I hope is the relevant part below.

The package also now FTBFS on reproducible builds [2] with the same error.

Regards
Graham


[1] https://ci.debian.net/packages/p/python-tornado/testing/amd64/
[2] https://tests.reproducible-builds.org/debian/rb-pkg/python-tornado.html


==
ERROR: test_multi_line_headers
(tornado.test.curl_httpclient_test.CurlHTTPClientCommonTestCase)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/tornado/testing.py", line 98, in __call__
result = self.orig_method(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/tornado/test/httpclient_test.py",
line 534, in test_multi_line_headers
resp = self.fetch("http://127.0.0.1:%d/; % port)
  File "/usr/lib/python3/dist-packages/tornado/testing.py", line 443, in fetch
return self.io_loop.run_sync(
  File "/usr/lib/python3/dist-packages/tornado/ioloop.py", line 530, in run_sync
return future_cell[0].result()
tornado.curl_httpclient.CurlError: HTTP 599: Header without colon

--
Ran 1167 tests in 16.585s

FAILED (errors=1, skipped=6)
Some tests were skipped because: Prevent internet access during build,
needs fix, no testable future imports, pycares module not present

Bug#1012125: marked as done (astroquery: Autopkgtests failure due to trying to write to /usr/lib)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 17:49:01 +
with message-id 
and subject line Bug#1012125: fixed in astroquery 0.4.6+dfsg-3
has caused the Debian Bug report #1012125,
regarding astroquery: Autopkgtests failure due to trying to write to /usr/lib
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.)


-- 
1012125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: astroquery
Version: 0.4.6+dfsg-2
Severity: serious
Justification: RT
X-Debbugs-Cc: simon.cho...@canonical.com

Hi,

The autopkgtests for 0.4.6+dfsg-2 fail with attempts to write to
locations in /usr/lib, preventing the package from migrating to testing.

>From 
>https://ci.debian.net/data/autopkgtest/unstable/amd64/a/astroquery/21778465/log.gz
> :

=== short test summary info 
FAILED 
../../../../usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py::TestESAHubble::test_download_product_by_calibration
FAILED 
../../../../usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py::TestESAHubble::test_download_product_by_product_type
FAILED 
../../../../usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py::TestESAHubble::test_get_postcard
FAILED 
../../../../usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py::TestESAHubble::test_cone_search
FAILED 
../../../../usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py::TestESAHubble::test_cone_search_coords
FAILED 
../../../../usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py::TestESAHubble::test_get_artifact
= 6 failed, 973 passed, 588 skipped, 2 xfailed, 150 warnings in 53.54s =

Details of the first failure:

__ TestESAHubble.test_download_product_by_calibration __

self = 

def test_download_product_by_calibration(self):
parameters = {'observation_id': "J6FL25S4Q",
  'cal_level': "RAW",
  'filename': "J6FL25S4Q.vot",
  'verbose': True}
ehst = ESAHubbleClass(self.get_dummy_tap_handler())
>   ehst.download_product(observation_id=parameters['observation_id'],
  calibration_level=parameters['cal_level'],
  filename=parameters['filename'],
  verbose=parameters['verbose'])

/usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py:101:
 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/astroquery/esa/hubble/core.py:106: in 
download_product
response = self._request('GET', self.data_url, save=True, cache=True,
/usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py:39:
 in get_mockreturn
shutil.copy(response + '.test', response)
/usr/lib/python3.10/shutil.py:417: in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

src = 
'/usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/data/J6FL25S4Q.vot.test'
dst = 
'/usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/data/J6FL25S4Q.vot'
[snip]
with open(src, 'rb') as fsrc:
try:
>   with open(dst, 'wb') as fdst:
E   PermissionError: [Errno 13] Permission denied: 
'/usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/data/J6FL25S4Q.vot'

/usr/lib/python3.10/shutil.py:256: PermissionError
--- End Message ---
--- Begin Message ---
Source: astroquery
Source-Version: 0.4.6+dfsg-3
Done: Vincent Prat 

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

Debian distribution maintenance software
pp.
Vincent Prat  (supplier of updated astroquery 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, 01 Jun 2022 19:26:18 +0200
Source: astroquery

Bug#1005650: squid: FTBFS with OpenSSL 3.0

[Nicholas Guriev]

Control: tags -1 patch

Hello everyone interested!

To fix FTBFS of the squid package, I offer to apply my changes with the
-Wno-error=deprecated-declarations flag and an original patch. This will
allow us to proceed with the OpenSSL transition.

See also my MR on Salsa.
https://salsa.debian.org/squid-team/squid/-/merge_requests/20

diff -Nru squid-5.5/debian/changelog squid-5.5/debian/changelog
--- squid-5.5/debian/changelog	2022-04-15 15:39:54.0 +0300
+++ squid-5.5/debian/changelog	2022-05-31 23:13:38.0 +0300
@@ -1,3 +1,23 @@
+squid (5.5-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Nicholas Guriev ]
+  * Fixing build against OpenSSL 3.0 (Closes: #1005650, LP: #1946205)
+
+  * debian/rules
+- Do not fail on errors about deprecated declarations from OpenSSL.
+- Remove -Wall in CFLAGS from the debian/rules file since upstream build
+  scripts already pass this flag.
+
+  * debian/patches/
+- New 0006-Fix-build-against-OpenSSL-3-0.patch
+
+  [ Simon Deziel ]
+  * apparmor: allow reading /etc/ssl/openssl.cnf
+
+ -- Nicholas Guriev   Tue, 31 May 2022 23:13:38 +0300
+
 squid (5.5-1) unstable; urgency=medium
 
   [ Amos Jeffries  ]
diff -Nru squid-5.5/debian/patches/0006-Fix-build-against-OpenSSL-3-0.patch squid-5.5/debian/patches/0006-Fix-build-against-OpenSSL-3-0.patch
--- squid-5.5/debian/patches/0006-Fix-build-against-OpenSSL-3-0.patch	1970-01-01 03:00:00.0 +0300
+++ squid-5.5/debian/patches/0006-Fix-build-against-OpenSSL-3-0.patch	2022-05-31 22:31:08.0 +0300
@@ -0,0 +1,210 @@
+From: Nicholas Guriev 
+Date: Tue, 31 May 2022 22:31:08 +0300
+Subject: Make build against OpenSSL-3.0 possible
+ In OpenSSL, the SSL_get_ex_new_index macro (substituted to
+ CRYPTO_get_ex_new_index) requires CRYPTO_EX_dup as the second callback. This
+ typedef, for some reason, has got an extra asterisk near void* within
+ arguments into the third version. Freely conversions from void* to void** is
+ okay in C but prohibited in C++. So I've updated the callback prototype to
+ match the last OpenSSL version.
+ .
+ OpenSSL pre-3.0 defined all of the SSL_OP_* macros with numeric hexadecimal
+ literals. However, the third version uses there casting expressions with
+ shifts which preprocessor is unable to compute. So I check only macros
+ existence, this lets Squid accept obsolete options. But it's nothing,
+ OpenSSL should ignore them anyway.
+
+---
+ acinclude/lib-checks.m4 |2 -
+ src/security/PeerOptions.cc |   50 ++--
+ src/ssl/support.cc  |2 -
+ 3 files changed, 27 insertions(+), 27 deletions(-)
+
+--- a/acinclude/lib-checks.m4
 b/acinclude/lib-checks.m4
+@@ -236,7 +236,7 @@ AC_DEFUN([SQUID_CHECK_OPENSSL_CONST_CRYP
+   AC_COMPILE_IFELSE([AC_LANG_PROGRAM([
+ #include 
+ 
+-int const_dup_func(CRYPTO_EX_DATA *, const CRYPTO_EX_DATA *, void *, int, long, void *) {
++int const_dup_func(CRYPTO_EX_DATA *, const CRYPTO_EX_DATA *, void **, int, long, void *) {
+ return 0;
+ }
+ ],[
+--- a/src/security/PeerOptions.cc
 b/src/security/PeerOptions.cc
+@@ -297,130 +297,130 @@ static struct ssl_option {
+ 
+ } ssl_options[] = {
+ 
+-#if SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG
++#ifdef SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG
+ {
+ "NETSCAPE_REUSE_CIPHER_CHANGE_BUG", SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG
+ },
+ #endif
+-#if SSL_OP_SSLREF2_REUSE_CERT_TYPE_BUG
++#ifdef SSL_OP_SSLREF2_REUSE_CERT_TYPE_BUG
+ {
+ "SSLREF2_REUSE_CERT_TYPE_BUG", SSL_OP_SSLREF2_REUSE_CERT_TYPE_BUG
+ },
+ #endif
+-#if SSL_OP_MICROSOFT_BIG_SSLV3_BUFFER
++#ifdef SSL_OP_MICROSOFT_BIG_SSLV3_BUFFER
+ {
+ "MICROSOFT_BIG_SSLV3_BUFFER", SSL_OP_MICROSOFT_BIG_SSLV3_BUFFER
+ },
+ #endif
+-#if SSL_OP_SSLEAY_080_CLIENT_DH_BUG
++#ifdef SSL_OP_SSLEAY_080_CLIENT_DH_BUG
+ {
+ "SSLEAY_080_CLIENT_DH_BUG", SSL_OP_SSLEAY_080_CLIENT_DH_BUG
+ },
+ #endif
+-#if SSL_OP_TLS_D5_BUG
++#ifdef SSL_OP_TLS_D5_BUG
+ {
+ "TLS_D5_BUG", SSL_OP_TLS_D5_BUG
+ },
+ #endif
+-#if SSL_OP_TLS_BLOCK_PADDING_BUG
++#ifdef SSL_OP_TLS_BLOCK_PADDING_BUG
+ {
+ "TLS_BLOCK_PADDING_BUG", SSL_OP_TLS_BLOCK_PADDING_BUG
+ },
+ #endif
+-#if SSL_OP_TLS_ROLLBACK_BUG
++#ifdef SSL_OP_TLS_ROLLBACK_BUG
+ {
+ "TLS_ROLLBACK_BUG", SSL_OP_TLS_ROLLBACK_BUG
+ },
+ #endif
+-#if SSL_OP_ALL
++#ifdef SSL_OP_ALL
+ {
+ "ALL", (long)SSL_OP_ALL
+ },
+ #endif
+-#if SSL_OP_SINGLE_DH_USE
++#ifdef SSL_OP_SINGLE_DH_USE
+ {
+ "SINGLE_DH_USE", SSL_OP_SINGLE_DH_USE
+ },
+ #endif
+-#if SSL_OP_EPHEMERAL_RSA
++#ifdef SSL_OP_EPHEMERAL_RSA
+ {
+ "EPHEMERAL_RSA", SSL_OP_EPHEMERAL_RSA
+ },
+ #endif
+-#if SSL_OP_PKCS1_CHECK_1
++#ifdef SSL_OP_PKCS1_CHECK_1
+ {
+ "PKCS1_CHECK_1", SSL_OP_PKCS1_CHECK_1
+ },
+ #endif
+-#if SSL_OP_PKCS1_CHECK_2
++#ifdef SSL_OP_PKCS1_CHECK_2
+ {
+ "PKCS1_CHECK_2", SSL_OP_PKCS1_CHECK_2
+ },
+ #endif
+-#if 

Processed: Re: squid: FTBFS with OpenSSL 3.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1005650 [src:squid] squid: FTBFS with OpenSSL 3.0
Added tag(s) patch.

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

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

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 17:11:15 +
with message-id 
and subject line Bug#1011891: fixed in node-immutable 4.0.0-4
has caused the Debian Bug report #1011891,
regarding node-immutable: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 1
to be marked as done.

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

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


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

Hi,

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


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

Bug#1009079: marked as done (mdtraj: autopkgtest timeout on arm64 (downloading pdb file?))

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 16:49:06 +
with message-id 
and subject line Bug#1009079: fixed in mdtraj 1.9.7-4
has caused the Debian Bug report #1009079,
regarding mdtraj: autopkgtest timeout on arm64 (downloading pdb file?)
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.)


-- 
1009079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mdtraj
Version: 1.9.7-2
Severity: important
X-Debbugs-Cc: stu...@debian.org

Dear Maintainer,

The autopkgtest tets for mdtraj attempts to download a pdb file and then use
that in calculations. This is failing (either all the time or intermittently)
with a timeout:

https://ci.debian.net/data/autopkgtest/unstable/arm64/m/mdtraj/20581005/log.gz

   except Empty:
>   raise Exception(
'Timeout (%.1f) when executing the following %s cell: "%s"' 
%
(TIMEOUT, cell.cell_type, cell.source.strip()))
E   Exception: Timeout (60.0) when executing the following code 
cell: "# pull a random protein from the PDB
E   # (The unitcell info happens to be wrong)
E   traj = md.load_pdb('http://www.rcsb.org/pdb/files/2MI7.pdb')
E   
E   # just for example, use the first frame as the 'native' 
conformation
E   q = best_hummer_q(traj, traj[0])"

rscb.org is not fast to serve up the pdb files, but I'm not sure if that is
the cause, whether the download is failing entirely, or whether the computation
that follows is just slow.

If this is an isolated use of a single pdb file in the tests, perhaps the
Debian package could carry that pdb file as some test data and patch the test
to use the local file instead.

An internest using test should also be marked as "needs-internet".

regards
Stuart
--- End Message ---
--- Begin Message ---
Source: mdtraj
Source-Version: 1.9.7-4
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated mdtraj 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, 01 Jun 2022 18:02:27 +0200
Source: mdtraj
Architecture: source
Version: 1.9.7-4
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Drew Parsons 
Closes: 1009079
Changes:
 mdtraj (1.9.7-4) unstable; urgency=medium
 .
   * debian/tests: add Restrictions: needs-internet
 (test_examples.py pulls a random PDB sample file from www.rcsb.org)
   * debian patch test_increase_timeout.patch increases TIMEOUT to
 180 sec in test_examples.py to allow for poor internet connections.
 Closes: #1009079.
   * Standards-Version: 4.6.1
Checksums-Sha1:
 559f78858b471735fe17b263e63c3d3291b4a5d6 2597 mdtraj_1.9.7-4.dsc
 3094912f23d87f6e99fa412f0161e0054569ff1d 299324 mdtraj_1.9.7-4.debian.tar.xz
Checksums-Sha256:
 c0532349b037525293715448027ef200b15a3f6e1eb633478efeeff125c00f07 2597 
mdtraj_1.9.7-4.dsc
 1c1d4e8c1cb12f9d39ad26f092fd3130b7f8fe16cd8b816344a7e7699613c5df 299324 
mdtraj_1.9.7-4.debian.tar.xz
Files:
 6d9979f167acfd2745e3b97702e96fa1 2597 python optional mdtraj_1.9.7-4.dsc
 c9b97788be223353f493d315cb85e19d 299324 python optional 
mdtraj_1.9.7-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmKXkvoACgkQVz7x5L1a
AfrwPw//afjm5QXTRHn9UgWUZxSfkNYJ3lrIV10I/5m119yBujo868Mtr5+I8bep
iBl0iIf19kmiWZPxhmgjas9vLamtHAeZCfUeXgnv4lW9DgFewU2tb/pVWiPIYyFn
w+c78dSqYXNwGZlfdNoSUtRDeiKjHWmPiTV5ncJdb5B41+DoIPUCg+F7wYU+3NfQ
ci7w0QpQur6P39yzywm/XhDVlGjTQ8vyJm+d/L9rRy98dO7VV83j5jWbADDW72sE
Li4uhFey1uAKDPIaKoOW8cP8I3U6T0x6kNX60ucxjwVu71xbEUFiM8FL94jTiAzB
mpxQWfvBoP3AKz84D9AHDumjOEQYq/EHLkYU3WQXdeusKpfZcnG1vc8KcGR73Bu+
9LDbs6cSFVZKpOTKTjQpfTHkP7gcNyQE01HUwot4gHM3NA3h3LMR+B/Ts4y2+2M/
w7jjQ9lG0o3hWSIX9p1ta59CfLjbD6e4i5XS5W8S4mjTlyRJ3Zd46fz84dS2Sibk
VQoqmNyI9zqnbBvGrPUd5znQNk5b3/9Zq/HJp/NrBpSwJIhZkF6N7g8MenC1xtgO
PrbT1PDJ+/ScNWerRBSOKvbr1WpoFvV43H5t2U8s4NwkXge2aeSuC/LkZ9ZK47MC

Bug#1012215: marked as done (gradle-debian-helper: unknown option --add-opens breaks OpenJDK 11 packages)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 16:34:39 +
with message-id 
and subject line Bug#1012215: fixed in gradle-debian-helper 2.3
has caused the Debian Bug report #1012215,
regarding gradle-debian-helper: unknown option --add-opens breaks OpenJDK 11 
packages
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.)


-- 
1012215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gradle-debian-helper
Version: 2.2
Severity: serious
X-Debbugs-Cc: a...@debian.org

Hi,

The newly added --add-opens option is only valid for OpenJDK 17. I
understand that we switch to it for Debian 12 but it currently breaks
all packages that are built with OpenJDK 11. I am currently in the
process to update gradle to a newer upstream release. We should try to
use a conditional clause depending on the JVM in use.

Markus
--- End Message ---
--- Begin Message ---
Source: gradle-debian-helper
Source-Version: 2.3
Done: Emmanuel Bourg 

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated gradle-debian-helper 
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, 01 Jun 2022 18:17:59 +0200
Source: gradle-debian-helper
Architecture: source
Version: 2.3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Closes: 1012215
Changes:
 gradle-debian-helper (2.3) unstable; urgency=medium
 .
   * Check the JDK specified by the JAVA_HOME environment variable before
 adding --add-opens option to the gradle command line (Closes: #1012215)
Checksums-Sha1:
 14bbcc9803ec505c0bccb1a2b36c70ed0f25 1821 gradle-debian-helper_2.3.dsc
 b47ef68784162411104f98e1d02f4d5071cc6d9c 15496 gradle-debian-helper_2.3.tar.xz
 baa46a78fb43f54997d380c8acd6c4c4cf53b14f 16733 
gradle-debian-helper_2.3_source.buildinfo
Checksums-Sha256:
 5d46acce03b03222fad288826af0edac4d6ff265a632c2f694ebe4f48f6f3cff 1821 
gradle-debian-helper_2.3.dsc
 80f3c1e09dac266be25dd94e8db187431fd1409586e0361e8703932cdf9a4a7c 15496 
gradle-debian-helper_2.3.tar.xz
 251dda9c0be3ddb965f359f97cd80aded1b63451debfffe8e51a3660a0583247 16733 
gradle-debian-helper_2.3_source.buildinfo
Files:
 9ca7864ac0cffabe3cd6a0565c2e6872 1821 java optional 
gradle-debian-helper_2.3.dsc
 ce7d6a73305efc08ec856cdd17bf07b2 15496 java optional 
gradle-debian-helper_2.3.tar.xz
 d7b33bac9cbeda3fe05416fbb04c4cc0 16733 java optional 
gradle-debian-helper_2.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAmKXkXUSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCs6eIQAJvUThTkBx94XYQTz8K+9oT5aI23kcBE
Cz70LW4AKh0AusO6bZ3/H0Y2Rm9RgC4Kh3dCwF9F8BJR1FUnXm3dZE/q5MZjk8Gr
8Wpv0pABlv0aTUS2k0qP1apOF4/Bwbw3fZS9rXE908iJ+HcgRuKAkc4ZxQ1TLPSv
fk0TWC7x3fryBUX0JT6h/EgeIVdIENOliU5wFPLqIvPz5aOvw8jaX8ed1IU/Cxck
1pNQiG0Z0rXp4APLETHYQytpb82o25aihhWR2qZA2ykDEaRMN3SxIrUAj5ysHyoN
BNA//oHXb2j/UiR/GneDwds3kQEGrVuQz/ktlBs8PiuQUnAhU5einRlvBNC1AC7w
SK3H0/UOTE3kqhhDoY7lPVebCSXHST0ryREtbH57Otp8ia/nnR8nv+JI3skVV1lN
VjnpG2CT9DP/8XrLza3yFyewNE0ezZK9/MJaXZXSJEGggrZZyb2wKwtWWpuKUTV2
efb1WMlXWfS8g/vuoxSKh+OEi9OUjb7LwL50acvL+WhTqOYkjLXNKQ8KL1Ojfpko
ntCAGWLTELpJmQYdWIa1g1O4LVdUR1FQnWToMmGT0q393b074gLnE+Uju4Dpv3Bw
VuZ2sVGFxkjMvRx31Lmd4ZQurMnsbpfh10FvlLwgvtoiTk0foWcHPy8hfT1HUbGp
SzPKG6QNkwgF
=mbiy
-END PGP SIGNATURE End Message ---

Bug#1012221: rust-stdweb-internal-macros (build-)depends on old version of rust-sha1.

[Peter Green]

Package: rust-stdweb-internal-macros
Version: 0.2.9-1
Severity: serious

rust-stdweb-internal-macros depends on version 0.6 of rust-sha1

As I understand it the new version of rust-sha1 is a completely different
code base with the old rust-sha1 having been renamed to sha1-smol

stdweb appears to be unmaintained upstream 
https://rustsec.org/advisories/RUSTSEC-2020-0056.html
and has an open soundness issue https://github.com/koute/stdweb/issues/411

No applications in Debian appear to use stdweb, Nevertheless this issue
is blocking the migration of the new version of rust-sha1 to testing.
Thanks to the use of collapse_features in instant and parking-lot it is also
making the build-dependencies of debcargo unsatisfiable.

Possible ways forward:

1. Attempt to port stdweb to the rustcrypto version of sha1
2. Introduce a sha1-0.6 package
3. Package sha1-smol and patch stdweb to use it
4. Remove the stdweb features in instant and parking-lot and allow stdweb to be 
removed from testing.

Given the lack of upstream maintinance of stdweb i'm inclined towards
option 4, does anyone else have any opinions before I go ahead and do it?

Processed: Bug#1012215 marked as pending in gradle-debian-helper

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1012215 [gradle-debian-helper] gradle-debian-helper: unknown option 
--add-opens breaks OpenJDK 11 packages
Added tag(s) pending.

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

Bug#1012215: marked as pending in gradle-debian-helper

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #1012215 in gradle-debian-helper 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/java-team/gradle-debian-helper/-/commit/5a3769b9bda5a581a38be6bdd694676bc24b83ed


Check the JDK specified by JAVA_HOME before adding --add-opens to the gradle 
command line (Closes: #1012215)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1012215

Bug#1012177: marked as done (apbs: vf2c [punc] uninit.c FTBFS on mips64el, mipsel)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 15:33:59 +
with message-id 
and subject line Bug#1012177: fixed in apbs 3.4.1-3
has caused the Debian Bug report #1012177,
regarding apbs: vf2c [punc] uninit.c FTBFS on mips64el, mipsel
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.)


-- 
1012177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apbs
Version: 3.4.1-2
Severity: serious
Justification: FTBFS
Control: forwarded -1 https://github.com/Electrostatics/FETK/issues/71

vf2c (punc component) is failing to build on MIPS architecture (specifically 
mip64el and 32-bit mipsel) on Debian Linux. The problem arises in uninit.c

There is a __mips section in uninit.c with

#ifdef __mips   /* must link with -lfpe */
#define IEEE0_done
/* code from Eric Grosse */
#include 
#include 
#include "/usr/include/sigfpe.h"/* full pathname for lcc -N */
#include "/usr/include/sys/fpu.h"

A standard build attempt fails since these header files don't exist (with gcc 
on linux). A full build log can be found here.

If I skip that section by patching to

#if defined (__mips) && !defined (__linux__)

then the build fails with

[  9%] Building C object 
_deps/fetk-build/punc/src/vf2c/CMakeFiles/vf2c.dir/uninit.c.o
cd /<>/obj-mips64el-linux-gnuabi64/_deps/fetk-build/punc/src/vf2c 
&& /usr/bin/cc -Dvf2c_EXPORTS 
-I/<>/debian/external_deps/fetk/punc/src/vf2c 
-I/<>/debian/external_deps/fetk/punc/src/vf2c/punc -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fcommon -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/tirpc -O2 -g -DNDEBUG -fPIC -fPIC -MD -MT 
_deps/fetk-build/punc/src/vf2c/CMakeFiles/vf2c.dir/uninit.c.o -MF 
CMakeFiles/vf2c.dir/uninit.c.o.d -o CMakeFiles/vf2c.dir/uninit.c.o -c 
/<>/debian/external_deps/fetk/punc/src/vf2c/uninit.c
/<>/debian/external_deps/fetk/punc/src/vf2c/uninit.c: In function 
‘ieee0’:
/<>/debian/external_deps/fetk/punc/src/vf2c/uninit.c:302:17: 
error: ‘_FPU_MASK_IM’ undeclared (first use in this function)
  302 | cw &= ~(_FPU_MASK_IM | _FPU_MASK_ZM | _FPU_MASK_OM);
  | ^~~~
/<>/debian/external_deps/fetk/punc/src/vf2c/uninit.c:302:17: note: 
each undeclared identifier is reported only once for each function it appears in
/<>/debian/external_deps/fetk/punc/src/vf2c/uninit.c:302:32: 
error: ‘_FPU_MASK_ZM’ undeclared (first use in this function)
  302 | cw &= ~(_FPU_MASK_IM | _FPU_MASK_ZM | _FPU_MASK_OM);
  |^~~~
/<>/debian/external_deps/fetk/punc/src/vf2c/uninit.c:302:47: 
error: ‘_FPU_MASK_OM’ undeclared (first use in this function)
  302 | cw &= ~(_FPU_MASK_IM | _FPU_MASK_ZM | _FPU_MASK_OM);
  |   ^~~~
make[3]: *** 
[_deps/fetk-build/punc/src/vf2c/CMakeFiles/vf2c.dir/build.make:331: 
_deps/fetk-build/punc/src/vf2c/CMakeFiles/vf2c.dir/uninit.c.o] Error 1
make[3]: Leaving directory '/<>/obj-mips64el-linux-gnuabi64'
make[2]: *** [CMakeFiles/Makefile2:764: 
_deps/fetk-build/punc/src/vf2c/CMakeFiles/vf2c.dir/all] Error 2

Full build log here. This error also occurs on riscv64.

mipsel (32-bit) gives the same build errors as mips64el.


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

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

Versions of packages apbs depends on:
ii  apbs-data3.4.1-2
ii  libamd2  1:5.12.0+dfsg-1
ii  libapbs3 3.4.1-2
ii  libarpack2   3.8.0-1
ii  libatlas3-base [libblas.so.3]3.10.3-12
ii  libblas3 [libblas.so.3]  3.10.1-2
ii  libblis3-openmp [libblas.so.3]   0.8.1-2
ii  libblis3-pthread [libblas.so.3]  0.8.1-2
ii  libc62.33-7
ii  libcamd2 1:5.12.0+dfsg-1
ii  libccolamd2  1:5.12.0+dfsg-1
ii  libcholmod3  1:5.12.0+dfsg-1
ii  libcolamd2   1:5.12.0+dfsg-1
ii  libfetk1.9   3.4.1-2
ii  libgomp1  

Processed: Bug#1012177 marked as pending in apbs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1012177 [apbs] apbs: vf2c [punc] uninit.c FTBFS on mips64el, mipsel
Added tag(s) pending.

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

Bug#1012177: marked as pending in apbs

[Drew Parsons]

Control: tag -1 pending

Hello,

Bug #1012177 in apbs 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/debichem-team/apbs/-/commit/28e3b1616e76f47afe20d29a2b99b51938f40bca


patch FETK punc component vf2c/uninit.c to use specific MIPS masks

fpu masks used with _FPU_SETCW.

Closes: #1012177.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1012177

Bug#1004285: davical: problems after upgrade to php 8, calendar clients reports "500"

[Tino Mettler]

Hi,

Maybe this helps: I recently upgraded to bullseye and my macOS calendar
(from macOS 12.2.1) still works fine with DAViCal.

I did not migrate DAViCal to the PostgreSQL 13 in bullseye yet, so I
still use PostgreSQL 11 for the DAViCal database.

Regards,
Tino

Bug#1004285: davical: problems after upgrade to php 8, calendar clients reports "500"

[Tino Mettler]

Hi,

Maybe this helps: I recently upgraded to bullseye and my macOS calendar
(from macOS 12.2.1) still works fine with DAViCal.

I did not migrate DAViCal to the PostgreSQL 13 in bullseye yet, so I
still use PostgreSQL 11 for the DAViCal database.

Regards,
Tino

Bug#1006562: Bug waiting on OpenSSL to migrate

[Thomas Goirand]

This bug will be fixed in Testing when OpenSSL migrates...

Cheers,

Thomas Goirand (zigo)

Bug#1011847: marked as done (node-d3-array: FTBFS: ReferenceError: it is not defined)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 13:50:00 +
with message-id 
and subject line Bug#1011847: fixed in node-d3-array 3.1.6+~cs5.0.6-1
has caused the Debian Bug report #1011847,
regarding node-d3-array: FTBFS: ReferenceError: it is not defined
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> Link node_modules/internmap -> ../internmap
> Link node_modules/@types/d3-array -> ../../types-d3-array
>dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/internmap/build
>   cd ./internmap && sh -ex ../debian/nodejs/internmap/build
> + rollup -c
> 
> src/index.js → dist/internmap.js...
> created dist/internmap.js in 45ms
> 
> src/index.js → dist/internmap.min.js...
> created dist/internmap.min.js in 361ms
> + mjs2cjs src/index.js
> 
> src/index.js → ./dist/index.cjs...
> created ./dist/index.cjs in 34ms
> No build command found, searching known files
> Found debian/nodejs/./build
>   cd ./. && sh -ex debian/nodejs/./build
> + rollup -c
> 
> src/index.js → dist/d3-array.js...
> created dist/d3-array.js in 407ms
> 
> src/index.js → dist/d3-array.min.js...
> created dist/d3-array.min.js in 995ms
> + mjs2cjs src/index.js
> 
> src/index.js → ./dist/index.cjs...
> created ./dist/index.cjs in 236ms
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/d3-array
>   /bin/sh -ex debian/tests/pkg-js/test
> + patch -R -p1
> patching file internmap/package.json
> patching file package.json
> + tape test/**/*-test.js
> file:///<>/test/ascending-test.js:4
> it("ascending(a, b) returns a negative number if a < b", () => {
> ^
> 
> ReferenceError: it is not defined
> at file:///<>/test/ascending-test.js:4:1
> at ModuleJob.run (node:internal/modules/esm/module_job:197:25)
> at async Promise.all (index 0)
> at async ESMLoader.import (node:internal/modules/esm/loader:337:24)
> at async importModuleDynamicallyWrapper (node:internal/vm/module:437:15)
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/node-d3-array_3.1.1+~cs5.0.5-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-d3-array 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

Bug#1012215: gradle-debian-helper: unknown option --add-opens breaks OpenJDK 11 packages

[Markus Koschany]

Am Mittwoch, dem 01.06.2022 um 15:03 +0200 schrieb Emmanuel Bourg:
> The --add-opens option was introduced in Java 9, so this shouldn't cause an
> issue with Java 11. What error did you get?


The compiler complains about "unknown option --add-opens" when I try to rebuild
kotlin in unstable. 

Starting process 'Gradle build daemon'. Working directory:
/<>/.gradle/daemon/4.4.1 Command: /usr/lib/jvm/java-11-openjdk-
amd64/bin/java -Xbootclasspath/a:/usr/share/java/gradle-helper-
hook.jar:/usr/share/java/maven-repo-helper.jar --add-opens
java.base/java.lang=ALL-UNNAMED -Dfile.encoding=UTF-8 -Duser.country -
Duser.language=en -Duser.variant -cp /usr/share/gradle/lib/gradle-launcher-
4.4.1.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.4.1

It might be related to the build-dependency on openjdk-8 but the command
mentions java-11 which is strange. In any case we should be more careful when
we force new options to all packages. A conditional is safer and prevents
regressions.



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

Processed: Bug#1011847 marked as pending in node-d3-array

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1011847 [src:node-d3-array] node-d3-array: FTBFS: ReferenceError: it is 
not defined
Added tag(s) pending.

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

Bug#1011847: marked as pending in node-d3-array

[Yadd]

Control: tag -1 pending

Hello,

Bug #1011847 in node-d3-array 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-d3-array/-/commit/ee040e17ed2135c0413b9353909a91a32b4b6716


Fix test

Closes: #1011847


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011847

Bug#1011953: marked as done (thinkfan FTBFS on riscv)

[Debian Bug Tracking System]

Your message dated Wed, 1 Jun 2022 09:37:00 -0400
with message-id 

and subject line Re: thinkfan FTBFS on riscv
has caused the Debian Bug report #1011953,
regarding thinkfan FTBFS on riscv
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.)


-- 
1011953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thinkfan
Version: 1.3.1-1
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: ab.bea...@gmail.com

Dear Maintainer,

The thinkfan package has a ftbfs issue on riscv64.

Full buildd log here: 
https://buildd.debian.org/status/fetch.php?pkg=thinkfan=riscv64=1.3.1-1=1649865911=0

I am including a patch which fixes the problem. Please consider applying it in 
the next upload. Thank you.

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

Kernel: Linux 5.18.0-starfive-5.18 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages thinkfan depends on:
ii  init-system-helpers  1.63
ii  libatasmart4 0.19-5
ii  libatomic1   12.1.0-2
ii  libc62.33-7
ii  libgcc-s112.1.0-2
ii  libstdc++6   12.1.0-2
ii  libyaml-cpp0.7   0.7.0+dfsg-8

thinkfan recommends no packages.

thinkfan suggests no packages.

-- no debconf information
fix ftbfs on riscv64

Alan Beadle 
--- thinkfan-1.3.1.orig/CMakeLists.txt
+++ thinkfan-1.3.1/CMakeLists.txt
@@ -8,6 +8,8 @@ cmake_minimum_required(VERSION 3.0)
 # Generate absolute paths or something
 cmake_policy(SET CMP0015 NEW)
 
+set(THREADS_PREFER_PTHREAD_FLAG ON)
+
 find_package(PkgConfig)
 find_package(Threads)
 pkg_check_modules(SYSTEMD "systemd")
--- End Message ---
--- Begin Message ---
I am closing this bug, because glibc 2.34 will break the above
solution (the cmake directive will be ignored in the future).

Instead this will probably have to be fixed at the compiler level,
when gcc adds inline support for subword atomics in riscv. This is
pending.

More information can be found at these links:
[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012058
[1] https://blog.jiejiss.com/A-RISC-V-gcc-pitfall-revealed-by-a-glibc-update/

-Alan Beadle--- End Message ---

Bug#1012060: marked as done (coq breaks coq-bignums autopkgtest: Compiled library Bignums.BigN.BigN makes inconsistent assumptions over library Coq.Init.Ltac)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 13:34:00 +
with message-id 
and subject line Bug#1012060: fixed in coq-bignums 8.15.0-3
has caused the Debian Bug report #1012060,
regarding coq breaks coq-bignums autopkgtest: Compiled library 
Bignums.BigN.BigN makes inconsistent assumptions over library Coq.Init.Ltac
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.)


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

Source: coq, coq-bignums
Control: found -1 coq/8.15.1+dfsg-2
Control: found -1 coq-bignums/8.15.0-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
coqfrom testing8.15.1+dfsg-2
coq-bignumsfrom testing8.15.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 coq 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=coq

https://ci.debian.net/data/autopkgtest/testing/amd64/c/coq-bignums/22188155/log.gz

make: Entering directory 
'/tmp/autopkgtest-lxc.1xnd4upm/downtmp/build.b30/src/tests'

coqc success/NumberScopes.v
File "./success/NumberScopes.v", line 7, characters 0-33:
Error:
Compiled library Bignums.BigN.BigN (in file 
/usr/lib/ocaml/coq/user-contrib/Bignums/BigN/BigN.vo) makes inconsistent 
assumptions over library Coq.Init.Ltac


make: *** [Makefile:10: success/NumberScopes.vo] Error 1
make: Leaving directory 
'/tmp/autopkgtest-lxc.1xnd4upm/downtmp/build.b30/src/tests'

autopkgtest [11:12:08]: test command1



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: coq-bignums
Source-Version: 8.15.0-3
Done: Julien Puydt 

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated coq-bignums 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, 01 Jun 2022 15:07:56 +0200
Source: coq-bignums
Architecture: source
Version: 8.15.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Julien Puydt 
Closes: 1012060
Changes:
 coq-bignums (8.15.0-3) unstable; urgency=medium
 .
   * Bump standards-version to 4.6.1.
   * Upload will fix ABI breakage. (Closes: #1012060)
Checksums-Sha1:
 3f3df1fa8f34290851f93292fa6a7ad840e78471 2188 coq-bignums_8.15.0-3.dsc
 4224f702671ead7e36d91a98cdf65f06e79c1b1a 1844 
coq-bignums_8.15.0-3.debian.tar.xz
 95b32356f7cb5e2abc83a635c5be588d2f1ac79c 6730 
coq-bignums_8.15.0-3_source.buildinfo
Checksums-Sha256:
 012c705a48514c5b398a7bac6644173277bc3d0bc215b0811849abc0a956ad42 2188 
coq-bignums_8.15.0-3.dsc
 0ab9add4884ce2cedf6e4eee484445258c69cfca7bd73a6430ed0d6c51982fc8 1844 
coq-bignums_8.15.0-3.debian.tar.xz
 2f62f8c8af0f15e8d9498ca7bec0039e73bab63cc111d57a7c912703f39bcdac 6730 
coq-bignums_8.15.0-3_source.buildinfo
Files:
 0ffaf398963e9f5430c7bdd3bdecd07d 2188 ocaml optional coq-bignums_8.15.0-3.dsc
 f971acc8efcfd3e5b5a88ae8a113abc1 1844 ocaml optional 
coq-bignums_8.15.0-3.debian.tar.xz
 815bdcb172af7c328cdbac5d4c4bc408 6730 ocaml optional 
coq-bignums_8.15.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmKXZWISHGpwdXlkdEBk

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

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 13:34:13 +
with message-id 
and subject line Bug#1011905: fixed in node-gulp-concat 
2.6.1+~0.0.15+git20190329.179bb8c+~1.0.3-5
has caused the Debian Bug report #1011905,
regarding node-gulp-concat: FTBFS: dh_auto_test: error: cd ./gulp-wrap && sh 
-ex ../debian/nodejs/gulp-wrap/test returned exit code 1
to be marked as done.

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

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


-- 
1011905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-gulp-concat
Version: 2.6.1+~0.0.15+git20190329.179bb8c+~1.0.3-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


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


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

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: node-gulp-concat
Source-Version: 2.6.1+~0.0.15+git20190329.179bb8c+~1.0.3-5
Done: Yadd 

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

A summary of the changes between this version and the 

Bug#1012215: gradle-debian-helper: unknown option --add-opens breaks OpenJDK 11 packages

[Emmanuel Bourg]

The --add-opens option was introduced in Java 9, so this shouldn't cause an 
issue with Java 11. What error did you get?

Bug#1011905: marked as pending in node-gulp-concat

[Yadd]

Control: tag -1 pending

Hello,

Bug #1011905 in node-gulp-concat 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-gulp-concat/-/commit/1ca89be5bb91921198eaade0142b6c0d68faa7a8


Fix test for nodejs >= 16

Closes: #1011905


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011905

Processed: Bug#1011905 marked as pending in node-gulp-concat

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1011905 [src:node-gulp-concat] node-gulp-concat: FTBFS: dh_auto_test: 
error: cd ./gulp-wrap && sh -ex ../debian/nodejs/gulp-wrap/test returned exit 
code 1
Added tag(s) pending.

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

Bug#1012077: add one riscv CPU info for linuxinfo package, T-HEAD XuanTie C910

[肖盛文]

Hi,

There is one riscv CPU info:

Name: T-HEAD XuanTie C910

Info: https://www.t-head.cn/product/C910

cat /proc/cpuinfo



   

processor   :
0   

  
 
hart    :
0   

  
 
isa :
rv64imafdcsu

  
 
mmu :
sv39

  
 
model name  : T-HEAD
C910

   
 
freq    :
1.2GHz  

  
 
icache  :
64kB

  
 
dcache  :
64kB

  
 
l2cache :
2MB 

  
 
tlb : 1024
4-ways  

 
 
cache line  :
64Bytes 

  
 
address sizes   : 40 bits physical, 39 bits
virtual 

 
vector version  : 0.7.1   

The board hardware info:
https://linux-hardware.org/?probe=bcb55ce8ce


I hope this CPU info add into linuxinfo package.

If need more infos about this CPU, please tell me.


Thanks!

在 2022/6/1 11:36, xiao sheng wen (肖盛文) 写道:
> Is there anybody use the riscv CPU other than sifive,u74-mc?
> Welcome to supply CPU info.
>
-- 
肖盛文 xiao sheng wen Faris Xiao 
微信(wechat)：atzlinux
《铜豌豆 Linux》https://www.atzlinux.com
基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
GnuPG Public Key: 0x00186602339240CB



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1012215: gradle-debian-helper: unknown option --add-opens breaks OpenJDK 11 packages

[Markus Koschany]

Package: gradle-debian-helper
Version: 2.2
Severity: serious
X-Debbugs-Cc: a...@debian.org

Hi,

The newly added --add-opens option is only valid for OpenJDK 17. I
understand that we switch to it for Debian 12 but it currently breaks
all packages that are built with OpenJDK 11. I am currently in the
process to update gradle to a newer upstream release. We should try to
use a conditional clause depending on the JVM in use.

Markus

Bug#1012214: gradle: unknown option --add-opens breaks OpenJDK 11 packages

[Markus Koschany]

Package: gradle
Version: 4.4.1-14
Severity: serious
X-Debbugs-Cc: a...@debian.org

Hi,

The newly added --add-opens option is only valid for OpenJDK 17. I
understand that we switch to it for Debian 12 but it currently breaks
all packages that are built with OpenJDK 11. I am currently in the
process to update gradle to a newer upstream release. We should try to
use a conditional clause depending on the JVM in use.

Markus

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

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 12:34:00 +
with message-id 
and subject line Bug#1011912: fixed in node-mimic-response 3.1.0-8
has caused the Debian Bug report #1011912,
regarding node-mimic-response: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 1
to be marked as done.

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

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


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

Hi,

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


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

Bug#1011912: marked as pending in node-mimic-response

[Yadd]

Control: tag -1 pending

Hello,

Bug #1011912 in node-mimic-response 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-mimic-response/-/commit/88dd177151462afa7ac2f2cc4cd574d860127df0


Fix test for opensll >= 3

Closes: #1011912


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011912

Processed: Bug#1011912 marked as pending in node-mimic-response

[Debian Bug Tracking System]

Processing control commands:

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

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

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

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 11:04:11 +
with message-id 
and subject line Bug#1011917: fixed in node-pbkdf2 3.1.2-3
has caused the Debian Bug report #1011917,
regarding node-pbkdf2: FTBFS: TypeError: Cannot read properties of undefined 
(reading 'toString')
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.)


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

Hi,

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


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

Processed: Bug#1011917 marked as pending in node-pbkdf2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1011917 [src:node-pbkdf2] node-pbkdf2: FTBFS: TypeError: Cannot read 
properties of undefined (reading 'toString')
Added tag(s) pending.

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

Bug#1011917: marked as pending in node-pbkdf2

[Yadd]

Control: tag -1 pending

Hello,

Bug #1011917 in node-pbkdf2 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-pbkdf2/-/commit/8567fad713e5dd29ef377bf3e80bf83abdced3e2


Drop ripemd160 test, not supported by OpenSSL 3

Closes: #1011917


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011917

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

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 10:50:13 +
with message-id 
and subject line Bug#1011806: fixed in node-livescript 1.6.1+dfsg-3
has caused the Debian Bug report #1011806,
regarding node-livescript: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 1
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> mkdir -p lib/
> /usr/bin/lsc --output lib --bare --compile "src/ast.ls"
> /usr/bin/lsc --output lib --bare --compile "src/browser.ls"
> /usr/bin/lsc --output lib --bare --compile "src/command.ls"
> /usr/bin/lsc --output lib --bare --compile "src/grammar.ls"
> /usr/bin/lsc --output lib --bare --compile "src/index.ls"
> /usr/bin/lsc --output lib --bare --compile "src/lang-ls.ls"
> /usr/bin/lsc --output lib --bare --compile "src/lexer.ls"
> /usr/bin/lsc --output lib --bare --compile "src/mode-ls.ls"
> /usr/bin/lsc --output lib --bare --compile "src/node.ls"
> /usr/bin/lsc --output lib --bare --compile "src/options.ls"
> /usr/bin/lsc --output lib --bare --compile "src/repl.ls"
> /usr/bin/lsc --output lib --bare --compile "src/util.ls"
> ./scripts/build-parser
> /usr/bin/lsc --compile package.json.ls
> make[2]: Leaving directory '/<>'
> help2man --no-info /usr/bin/lsc >lsc.1
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/livescript
>   /bin/sh -ex debian/tests/pkg-js/test
> + ./scripts/test
> Testing with async.
> Testing with async generators.
> test/accessor.ls
> test/assignment.ls
> test/async-generators.ls
> test/async.ls
> test/chaining.ls
> test/cli.ls
> test/comment.ls
> test/compilation.ls
> test/cs-classes.ls
> test/declaration.ls
> test/existence.ls
> test/function.ls
> test/generators.ls
> test/heredoc.ls
> test/if.ls
> test/label.ls
> test/lib.ls
> test/literal.ls
> test/loop.ls
> Expected values to be strictly equal:
> + actual - expected
> 
> + "Cannot read properties of null (reading 'length')"
> - "Cannot read property 'length' of null"
> at test/loop.ls:757:1
> 
> # Certain literals could result in illegal JavaScript if not carefully
> # handled. These are all nonsensical use cases and could just as easily
> # be LiveScript syntax errors. The thing to avoid is for them to be JavaScript
> # syntax errors; lsc should never produce illegal JavaScript on any input,
> # silly or otherwise.
> deep-equal [] [0 for x in 42]
> deep-equal [] [0 for x in -42]
> throws "Cannot read property 'length' of null" -> [0 for x in null]
> throws "Cannot read property 'length' of undefined" -> [0 for x in void]
> 
> # [LiveScript#1035](https://github.com/gkz/LiveScript/issues/1035)
> for [1 2 3] then 1 else 0
> 
> # [LiveScript#1039](https://github.com/gkz/LiveScript/issues/1039)
> arr = [3 2 1 0]
> x = for arr case .. in [1 2] => 1
> test/null.ls
> test/oo.ls
> test/operator.ls
> test/regex.ls
> test/repl.ls
> test/splat.ls
> test/string.ls
> test/switch.ls
> test/try.ls
> failed 1 and passed 2235 tests in 1.73 seconds
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/node-livescript_1.6.1+dfsg-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results

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

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

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

We believe that the bug you reported is fixed in the latest version of
node-livescript, 

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

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 10:50:19 +
with message-id 
and subject line Bug#1011850: fixed in node-sparkles 1.0.1-3
has caused the Debian Bug report #1011850,
regarding node-sparkles: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 1
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/sparkles
>   /bin/sh -ex debian/tests/pkg-js/test
> + jest --ci --testRegex test/.*\.js
> FAIL test/index.js
>   ● sparkles() › will attach the sparkles store namespace to global
> 
> TypeError: expect is not a function
> 
>   22 |
>   23 |   it('will attach the sparkles store namespace to global', 
> function(done) {
> > 24 | expect(global['store@sparkles']).toBeDefined();
>  | ^
>   25 | done();
>   26 |   });
>   27 |
> 
>   at Object. (test/index.js:24:5)
> 
>   ● sparkles() › will attach an event emitter to the sparkles store default 
> namespace
> 
> TypeError: expect is not a function
> 
>   27 |
>   28 |   it('will attach an event emitter to the sparkles store default 
> namespace', function(done) {
> > 29 | expect(global['store@sparkles']).toHaveProperty('default');
>  | ^
>   30 | done();
>   31 |   });
>   32 |
> 
>   at Object. (test/index.js:29:5)
> 
>   ● sparkles() › removes the event emitter from the store when remove is 
> called
> 
> TypeError: expect is not a function
> 
>   34 | ee.on('test', noop);
>   35 | ee.remove();
> > 36 | expect(global['store@sparkles']).not.toHaveProperty('default');
>  | ^
>   37 | done();
>   38 |   });
>   39 | });
> 
>   at Object. (test/index.js:36:5)
> 
> FAIL test/exists.js
>   ● sparkles.exists() › checks if a namespace has been defined
> 
> TypeError: expect is not a function
> 
>8 |
>9 |   it('checks if a namespace has been defined', function(done) {
> > 10 | expect(sparkles.exists('test')).toBe(false);
>  | ^
>   11 | var ee = sparkles('test');
>   12 | expect(sparkles.exists('test')).toBe(true);
>   13 | ee.remove();
> 
>   at Object. (test/exists.js:10:5)
> 
> FAIL test/namespace.js
>   ● namespace › should use an EE from sparkles namespace if it already exists
> 
> TypeError: expect is not a function
> 
>   23 | var sparkles = require('../')();
>   24 |
> > 25 | expect(sparkles.custom).toEqual('ee');
>  | ^
>   26 | done();
>   27 |   });
>   28 |
> 
>   at Object. (test/namespace.js:25:5)
> 
>   ● namespace › should allow custom namespaces
> 
> TypeError: expect is not a function
> 
>   33 | var sparkles = require('../')('customNamespace');
>   34 |
> > 35 | expect(sparkles.custom).toEqual(true);
>  | ^
>   36 | done();
>   37 |   });
>   38 | });
> 
>   at Object. (test/namespace.js:35:5)
> 
> Test Suites: 3 failed, 3 total
> Tests:   6 failed, 6 total
> Snapshots:   0 total
> Time:3.454 s
> Ran all test suites.
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1


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

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results

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

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

Bug#1011624: kdesu: kdesu fails to authenticate with sudo from testing/unstable

[Marc Haber]

On Wed, Jun 01, 2022 at 12:35:01PM +0200, Aurélien COUDERC wrote:
> Le 26/05/2022 à 16:09, Marc Haber a écrit :
> > On Wed, May 25, 2022 at 01:58:58PM +0100, Rik Mills wrote:
> > > The issue can be worked around by adding /etc/sudoers.d/kdesu with the
> > > contents
> > > 
> > > Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty
> > 
> > kdesu is cordially invited to ship that file in the package, fixing the
> > issue for everybody. Please add a comment with the reference to this bug
> > report and remove the file once kdesu was fixed upstream.
> 
> kdesu is now cordially shipping the file in the package. :-)

;-)

> Would you mind to comment why this is OK from a security perspective ?

There is a discussion in the KDE bug ticket that seems to make sense to
me. kdesu is exploiting a vulnerability in sudo that we fixed by forcing
the pty. If we don't want to lose kdesu's functionality, we need either
fixing kdesu so that is uses "legal" methods to use sudo, or we need to
re-open the vulnerability to allow unmodified kdesu to work.

This is kdesu's vulnerability now ;-)

I would love to see kdesu fixed in some future, so that the "insecure"
sudo rule can be removed. It would be an idea to ship the file with the
rule commented out by default so that every local admin can cause their
own vulnerability, but that'd probable cause a new avalanche of "kdesu
broken" bug reports.

> I’m no security expert at all but if I read the CVE description correctly,
> the issue is with the su'ed command being able to escape the su user
> session.
> Is it OK in this case because kdesu is used to gain root from non-root and
> so escaping the su session only gives you back the original non-root user
> rights ?

I hope that other people can comment on that, I would need to ponder
about that for some time.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1011624: kdesu: kdesu fails to authenticate with sudo from testing/unstable

[Aurélien COUDERC]

Dear Marc,

Le 26/05/2022 à 16:09, Marc Haber a écrit :

On Wed, May 25, 2022 at 01:58:58PM +0100, Rik Mills wrote:

The issue can be worked around by adding /etc/sudoers.d/kdesu with the
contents

Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty


kdesu is cordially invited to ship that file in the package, fixing the
issue for everybody. Please add a comment with the reference to this bug
report and remove the file once kdesu was fixed upstream.


kdesu is now cordially shipping the file in the package. :-)

Would you mind to comment why this is OK from a security perspective ?

I’m no security expert at all but if I read the CVE description 
correctly, the issue is with the su'ed command being able to escape the 
su user session.
Is it OK in this case because kdesu is used to gain root from non-root 
and so escaping the su session only gives you back the original non-root 
user rights ?



Thanks,
--
Aurélien

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

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 10:35:35 +
with message-id 
and subject line Bug#1011879: fixed in node-browserify-sign 4.2.1-3
has caused the Debian Bug report #1011879,
regarding node-browserify-sign: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 1
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/browserify-sign
>   /bin/sh -ex debian/tests/pkg-js/test
> + tape test/index.js
> TAP version 13
> # md5 with 1024 keys
> ok 1 correct length
> ok 2 equal sigs
> ok 3 compare to known
> ok 4 node validate node sig
> ok 5 node validate browser sig
> ok 6 browser validate node sig
> ok 7 browser validate browser sig
> # md5 with 1024 keys
> ok 8 correct length
> ok 9 equal sigs
> ok 10 compare to known
> ok 11 node validate node sig
> ok 12 node validate browser sig
> ok 13 browser validate node sig
> ok 14 browser validate browser sig
> # md5 with 2028 keys
> ok 15 correct length
> ok 16 equal sigs
> ok 17 compare to known
> ok 18 node validate node sig
> ok 19 node validate browser sig
> ok 20 browser validate node sig
> ok 21 browser validate browser sig
> # md5 with 1024 keys non-rsa key
> ok 22 correct length
> ok 23 equal sigs
> ok 24 compare to known
> ok 25 node validate node sig
> ok 26 node validate browser sig
> ok 27 browser validate node sig
> ok 28 browser validate browser sig
> # rmd160 with 2028 keys
> node:internal/crypto/hash:67
>   this[kHandle] = new _Hash(algorithm, xofLen);
>   ^
> 
> Error: error:0308010C:digital envelope routines::unsupported
> at new Hash (node:internal/crypto/hash:67:19)
> at createHash (node:crypto:130:10)
> at new Sign (/<>/browser/index.js:21:16)
> at Object.createSign (/<>/browser/index.js:80:10)
> at Test. (/<>/test/index.js:30:25)
> at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:99:32)
> at Test.run (/usr/share/nodejs/tape/lib/test.js:117:31)
> at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:99:32)
> at Immediate.next (/usr/share/nodejs/tape/lib/results.js:88:19)
> at processImmediate (node:internal/timers:466:21) {
>   opensslErrorStack: [ 'error:0386:digital envelope 
> routines::initialization error' ],
>   library: 'digital envelope routines',
>   reason: 'unsupported',
>   code: 'ERR_OSSL_EVP_UNSUPPORTED'
> }
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1


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

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated 

Processed: Bug#1011806 marked as pending in node-livescript

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#1011806: marked as pending in node-livescript

[Yadd]

Control: tag -1 pending

Hello,

Bug #1011806 in node-livescript 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-livescript/-/commit/d7d6b19a3d1b88d69939b2b7c1a77e49be947286


Fix test for nodejs >= 16

Closes: #1011806


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011806

Bug#1011861: marked as done (node-des.js: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 10)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 10:21:08 +
with message-id 
and subject line Bug#1011861: fixed in node-des.js 1.0.1-3
has caused the Debian Bug report #1011861,
regarding node-des.js: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 10
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/des.js
>   /bin/sh -ex debian/tests/pkg-js/test
> + mocha -R spec test/
> 
> 
>   DES-CBC
> encryption/decryption
>   1) should encrypt vector 0
>   2) should encrypt vector 1
>   3) should encrypt vector 2
>   4) should encrypt vector 3
>   5) should encrypt vector 4
> 
>   DES
> Key Derivation
>   undefined should derive proper keys
> encryption/decryption
>   6) should encrypt vector 0
>   7) should encrypt vector 1
>   8) should encrypt vector 2
>   9) should encrypt vector 3
>   10) should encrypt vector 4
>   undefined should buffer during encryption/decryption
> 
>   DES-EDE-CBC
> encryption/decryption
>   undefined should encrypt vector 0
>   undefined should encrypt vector 1
>   undefined should encrypt vector 2
>   undefined should encrypt vector 3
>   undefined should encrypt vector 4
> 
>   utils
> IP
>   undefined should permute properly
>   undefined should rev-permute properly
> PC1
>   undefined should permute properly
> r28shl
>   undefined should shl properly
> PC2
>   undefined should permute properly
> readUInt32BE
>   undefined should read number properly
> writeUInt32BE
>   undefined should read number properly
> expand
>   undefined should expand
>   undefined should expand with low 1
>   undefined should expand with low 1
> substitute
>   undefined should substitute
> permute
>   undefined should permute
> 
> 
>   19 passing (49ms)
>   10 failing
> 
>   1) DES-CBC
>encryption/decryption
>  should encrypt vector 0:
>  Error: error:0308010C:digital envelope routines::unsupported
>   at Cipheriv.createCipherBase (node:internal/crypto/cipher:116:19)
>   at Cipheriv.createCipherWithIV (node:internal/crypto/cipher:135:3)
>   at new Cipheriv (node:internal/crypto/cipher:243:3)
>   at Object.createCipheriv (node:crypto:138:10)
>   at Context. (test/cbc-test.js:58:29)
>   at callFn (/usr/share/nodejs/mocha/lib/runnable.js:366:21)
>   at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:354:5)
>   at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:678:10)
>   at /usr/share/nodejs/mocha/lib/runner.js:801:12
>   at next (/usr/share/nodejs/mocha/lib/runner.js:593:14)
>   at /usr/share/nodejs/mocha/lib/runner.js:603:7
>   at next (/usr/share/nodejs/mocha/lib/runner.js:486:14)
>   at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:571:5)
>   at processImmediate (node:internal/timers:466:21)
> 
>   2) DES-CBC
>encryption/decryption
>  should encrypt vector 1:
>  Error: error:0308010C:digital envelope routines::unsupported
>   at Cipheriv.createCipherBase (node:internal/crypto/cipher:116:19)
>   at Cipheriv.createCipherWithIV (node:internal/crypto/cipher:135:3)
>   at new Cipheriv (node:internal/crypto/cipher:243:3)
>   at Object.createCipheriv (node:crypto:138:10)
>   at Context. (test/cbc-test.js:58:29)
>   at callFn (/usr/share/nodejs/mocha/lib/runnable.js:366:21)
>   at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:354:5)
>   at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:678:10)
>   at /usr/share/nodejs/mocha/lib/runner.js:801:12
>   at next (/usr/share/nodejs/mocha/lib/runner.js:593:14)
>   at /usr/share/nodejs/mocha/lib/runner.js:603:7
>   at next 

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

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 10:06:44 +
with message-id 
and subject line Bug#1011851: fixed in node-dom-serializer 1.3.2-5
has caused the Debian Bug report #1011851,
regarding node-dom-serializer: FTBFS: 
node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 
'jest-matcher-utils' or its corresponding type declarations.
to be marked as done.

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

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


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

Hi,

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


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


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/node-dom-serializer_1.3.2-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-dom-serializer 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, 01 Jun 2022 11:49:54 +0200
Source: node-dom-serializer
Built-For-Profiles: nocheck
Architecture: source
Version: 1.3.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1011851
Changes:
 node-dom-serializer (1.3.2-5) unstable; urgency=medium
 .
   * Team upload
   * Declare compliance with policy 4.6.1
   * Fix filenamemangle
   * Fix build links (Closes: #1011851)
Checksums-Sha1: 
 1d05f34491bc1b286731015a5a38bf756d55a971 2321 node-dom-serializer_1.3.2-5.dsc
 663082c8270890b71f32189c15e6e48b1bcb7653 3512 
node-dom-serializer_1.3.2-5.debian.tar.xz

Bug#1011861: marked as pending in node-des.js

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-des.js/-/commit/ebfe07566b0996dd5abc6834e7d1bb4017ca2c8f


Launch only test for protocols supported by OpenSSL 3

Closes: #1011861


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011861

Processed: Bug#1011861 marked as pending in node-des.js

[Debian Bug Tracking System]

Processing control commands:

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

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

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

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 10:06:35 +
with message-id 
and subject line Bug#1011852: fixed in node-browserify-des 1.0.2-6
has caused the Debian Bug report #1011852,
regarding node-browserify-cipher: FTBFS: TypeError: Cannot read properties of 
undefined (reading 'update')
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.)


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

Hi,

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


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

Bug#995242: marked as done (isc-dhcp-server: omshell returns inconsistent results or segfaults)

[Debian Bug Tracking System]

Your message dated Wed, 1 Jun 2022 12:06:10 +0200
with message-id 
and subject line Re: Bug#995242: isc-dhcp-server: omshell returns inconsistent 
results  or segfaults
has caused the Debian Bug report #995242,
regarding isc-dhcp-server: omshell returns inconsistent results or segfaults
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.)


-- 
995242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: isc-dhcp-server
Version: 4.4.1-2.3
Severity: grave
Justification: renders package unusable




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

Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) 
(ignored: LC_ALL set to C), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages isc-dhcp-server depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  debianutils4.11.2
ii  libc6  2.31-13
ii  libdns-export1110  1:9.11.19+dfsg-2.1
ii  libirs-export161   1:9.11.19+dfsg-2.1
ii  libisc-export1105  1:9.11.19+dfsg-2.1
ii  lsb-base   11.1.0

Versions of packages isc-dhcp-server recommends:
ii  isc-dhcp-common  4.4.1-2.3
ii  policycoreutils  3.1-3

Versions of packages isc-dhcp-server suggests:
pn  isc-dhcp-server-ldap  
pn  policykit-1   

-- Configuration Files:
/etc/dhcp/dhcpd.conf changed [not included]

-- debconf information excluded

-- To Reproduce --

Two DHCP servers need to be configured as failover peers.
Issue the following commands using omshell

# omshell
> server localhost
> port 7911
> key omapi_key 
> connect
Segmentation fault (core dumped)
Note, the connect works occasionally after a cold server restart, but
once the failure starts there is no recovery.  The connect does not
always result is a segfault.  Frequently the connect just hangs.

example from 'dmesg' output:
[Tue Sep 28 11:05:22 2021] omshell[4604]: segfault at 0 ip 55623cdd06dc sp 
7ffd5a2c7c78 error 4 in omshell[55623cd97000+45000]
--- End Message ---
--- Begin Message ---
Version: 4.4.3-1

On Wed, 18 May 2022 08:50:00 +0200 =?UTF-8?Q?Stefan_B=c3=bchler?= 
 wrote:
> Hi,
> 
> On Tue, 10 May 2022 10:13:11 +0200 Santiago Ruano =?iso-8859-1?Q?Rinc=F3n?= 
>  wrote:
> > Control: forwarded -1 https://gitlab.isc.org/isc-projects/dhcp/-/issues/167
> > 
> > On Mon, 7 Mar 2022 14:41:23 -0800 Harris Enniss  wrote:
> > > We encountered this as well. It seems to be an issue with the way debian's
> > > fork is linked against system bind libraries (i.e. libiscexport-1105);
> > > segfaults disappear once we link them statically, as the isc sources do.
> > 
> > The latest release (4.4.3-1) removed that bind against bind system
> > libraries. Are you able to confirm this bug disappeared with it?
> 
> I observed this issue as well (context: foreman, dhcp only used to
> deploy new systems, i.e. leases file usually empty).
> 
> omshell crashed in about 9 out of 10 times (in various stages) - can't
> be that hard to reproduce.
> 
> Installing the testing package on stable sucks, because it wants libc6
> from testing, so I "backported" it locally:
> 
>sbuild -d bullseye-backports -c bullseye-amd64-sbuild 
> --append-to-version='~bpo10+1' isc-dhcp_4.4.3-1.dsc -e 'me 
> ' -m 'me '
> 
> Worked fine so far - omshell seems to be fixed.
> 
> cheers,
> Stefan

Thank you for testing!

 -- Santiago


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

Bug#1011852: marked as done (node-browserify-des: FTBFS: TypeError: Cannot read properties of undefined (reading 'update'))

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 10:06:35 +
with message-id 
and subject line Bug#1011852: fixed in node-browserify-des 1.0.2-6
has caused the Debian Bug report #1011852,
regarding node-browserify-des: FTBFS: TypeError: Cannot read properties of 
undefined (reading 'update')
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/browserify-des
>   /bin/sh -ex debian/tests/pkg-js/test
> + tape test.js
> TAP version 13
> # des-ecb
> # run: 1
> not ok 1 Error: error:0308010C:digital envelope routines::unsupported at 
> Cipheriv.createCipherBase (node:internal/crypto/cipher:116:19) at 
> Cipheriv.createCipherWithIV (node:internal/crypto/cipher:135:3) at new 
> Cipheriv (node:internal/crypto/cipher:243:3) at Object.createCipheriv 
> (node:crypto:138:10) at Test. (/<>/test.js:30:32) at 
> Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:99:32) at Test.run 
> (/usr/share/nodejs/tape/lib/test.js:117:31) at Test.bound [as run] 
> (/usr/share/nodejs/tape/lib/test.js:99:32) at Test._end 
> (/usr/share/nodejs/tape/lib/test.js:220:11) at Test.bound [as _end] 
> (/usr/share/nodejs/tape/lib/test.js:99:32)
>   ---
> operator: notOk
> expected: |-
>   false
> actual: |-
>   { [Error: error:0308010C:digital envelope routines::unsupported] 
> library: 'digital envelope routines', reason: 'unsupported', code: 
> 'ERR_OSSL_EVP_UNSUPPORTED' }
> at: Test. (/<>/test.js:32:13)
> stack: |-
>   Error: error:0308010C:digital envelope routines::unsupported
>   at Cipheriv.createCipherBase (node:internal/crypto/cipher:116:19)
>   at Cipheriv.createCipherWithIV (node:internal/crypto/cipher:135:3)
>   at new Cipheriv (node:internal/crypto/cipher:243:3)
>   at Object.createCipheriv (node:crypto:138:10)
>   at Test. (/<>/test.js:30:32)
>   at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:99:32)
>   at Test.run (/usr/share/nodejs/tape/lib/test.js:117:31)
>   at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:99:32)
>   at Test._end (/usr/share/nodejs/tape/lib/test.js:220:11)
>   at Test.bound [as _end] (/usr/share/nodejs/tape/lib/test.js:99:32)
>   ...
> /<>/test.js:35
> var nodeCipherText = Buffer.concat([nodeEncrypt.update(text), 
> nodeEncrypt.final()])
> ^
> 
> TypeError: Cannot read properties of undefined (reading 'update')
> at Test. (/<>/test.js:35:57)
> at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:99:32)
> at Test.run (/usr/share/nodejs/tape/lib/test.js:117:31)
> at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:99:32)
> at Test._end (/usr/share/nodejs/tape/lib/test.js:220:11)
> at Test.bound [as _end] (/usr/share/nodejs/tape/lib/test.js:99:32)
> at Immediate. (/usr/share/nodejs/tape/lib/test.js:161:18)
> at processImmediate (node:internal/timers:466:21)
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/node-browserify-des_1.0.2-5_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1011624: marked as done (kdesu: kdesu fails to authenticate with sudo from testing/unstable)

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 10:05:05 +
with message-id 
and subject line Bug#1011624: fixed in kdesu 5.94.0-2
has caused the Debian Bug report #1011624,
regarding kdesu: kdesu fails to authenticate with sudo from testing/unstable
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.)


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

Package: kdesu
Version: 5.93.0-1
Severity: serious

kdesu fails to authenticate with sudo from testing/unstable.

Examples: launching ksystemlog from the main menu, or trying to run 
krusader root mode option via its 'Tools > Start Krusader Root Mode' 
menu entry. Assuming that the current user is a member of the sudo group.


On entering the correct password authentication is refused, stating that 
possibly an incorrect password has been entered.


It appears that kdesu fails to cope with the sudo config CVE fix in this 
commit:


https://salsa.debian.org/sudo-team/sudo/-/commit/59db341d46aa4c26b54c1270e69f2562e7f3d751

KDE bug: https://bugs.kde.org/show_bug.cgi?id=452532

The issue can be worked around by adding /etc/sudoers.d/kdesu with the 
contents


Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty
--- End Message ---
--- Begin Message ---
Source: kdesu
Source-Version: 5.94.0-2
Done: Aurélien COUDERC 

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

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

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

Debian distribution maintenance software
pp.
Aurélien COUDERC  (supplier of updated kdesu 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, 01 Jun 2022 11:20:21 +0200
Source: kdesu
Architecture: source
Version: 5.94.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Aurélien COUDERC 
Closes: 1011624
Changes:
 kdesu (5.94.0-2) unstable; urgency=medium
 .
   [ Rik Mills ]
   * Disable use of sudo 'Defaults use_pty' for kdesu. (Closes: #1011624)
   * Improve short description for libkf5su5.
Checksums-Sha1:
 98d61d7d14b89beb010bcac45004a1cfa88ecf6f 2850 kdesu_5.94.0-2.dsc
 cb6241bd4787396ca351d940a5cd49ade6f96040 11812 kdesu_5.94.0-2.debian.tar.xz
 764073cb20419d429748c95e8c8b787eaf6f87a2 12966 kdesu_5.94.0-2_source.buildinfo
Checksums-Sha256:
 acadef19775fdcc9e867ba1fe51d213efdd34271669d37c219f9454f8d8f1463 2850 
kdesu_5.94.0-2.dsc
 f6858c2d3d475d61f2a33eb5c5a7a8eeb06e3ad87ef6b20ba77cd56e2b3e15e5 11812 
kdesu_5.94.0-2.debian.tar.xz
 409c65014cbf153b8de74f276d44b5fe55357e0c51e127cec48f87a406057bac 12966 
kdesu_5.94.0-2_source.buildinfo
Files:
 a8d44013d0331db34e35b57d570b648d 2850 libs optional kdesu_5.94.0-2.dsc
 2c673600b8f338359605a9e06554953d 11812 libs optional 
kdesu_5.94.0-2.debian.tar.xz
 178a55ace3d6c0270a6587b9b160a839 12966 libs optional 
kdesu_5.94.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAmKXMjUTHGNvdWNvdWZA
ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJC4GEACyBavTsVSERx021iHeksyPWjG17meY
682oPmZfv4ngZnUHCG0tsEUteb9HRyKuWv6u3p9ZjmSj90prQK2ljG6nJx65HRCh
7PqjclUsHfQcIy677FpnMWXmKoUiM5PPqFMXnjKvgBffXPK0AAhWMoTEInfhszE7
zRS8tRWEi1kLdW9XCyFYD09LsiTIs1pSSolNEKCUhI0Gs4knnNHh+l5YLKRtL6Zs
j5udG3+gERSOB5iLSfcz0pPc7mGinCRnrFL+0PrFef/D8xbGXBFSPfDsVBtF8i5f
Gwf/UhiD6XLYrj5pppTtLpw+4hatOpfL761+Z4vbCpNUzunioPHvAMnNEYPAdUb3
3AODVp6HYg8aHKrdjLPCgt/y/V5J2kujSHf4WJq1wFqNamvyPz4jAmwxO83iz2EJ
mZt0IQ92Fzb9YgFCGuWca5gYHcw255sN3lyja+k6BjH8CtU3AP8LWYnrtP5ncs4c
DAE5p8kBy4mkR7k3n1QaiTuwEVcFxeIscWLNMrB0L4au+TlGpgTJfwIQ6hFVHmhm
PG7Xn+3z0zxmjkKXUPJmd7t6JFHm0zpl3cEUytIL6IFSIr86b3GLbQUdM0V4BvWB
4gBw/TqaqHHZNElOzPu+USkzbTI/CiBa/jGFfgq3KwSwGMV1LaEaa8nGCcSTjClU
RXui+80swkuDuQ==
=WwbR
-END PGP SIGNATURE End Message ---

Processed: Re: MatIO test failures against HDF5 1.12.0

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 1011805 1010202
Bug #1011805 [src:libmatio] libmatio: FTBFS: dh_auto_test: error: make -j8 
check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Bug #1010202 [src:libmatio] libmatio: FTBFS against hdf5 1.12.0 currently in 
experimental - 3 failed tests
Severity set to 'serious' from 'important'
Added tag(s) sid and bookworm.
Merged 1010202 1011805

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

Bug#1012154: binfmt-support.service errors with "unable to close /proc/sys/fs/binfmt_misc/register: File exists"

[Michael Biebl]

Control: reassign -1 systemd
Control: severity -1 important
Control: affects -1 binfmt-support

Hi Facundo,

what you see here is a race condition between binfmt-support.service and 
systemd-binfmt.service.
E.g. qemu installs binfmt config files for both binfmt-support and 
systemd-binfmt leading to the issue you see.


I plan to add a
ConditionFileIsExecutable=!/usr/sbin/update-binfmts
to systemd-binfmt.service. This will disable systemd-binfmt.service when 
binfmt-support is installed and should mitigate this issue.

(thus reassigning to systemd)

Afaics binfmt-support has remained a Debian-only solution, so long-term 
I'd think it would be beneficial if we'd consider systemd-binfmt as a 
cross-distro solution.


There aren't that many packages installing config snippets in 
/usr/share/binfmts, so a transition seems reasonably doable.


Colin, what's your take on this?

Michael




On Mon, 30 May 2022 19:22:09 -0300 Facundo Gaich  
wrote:

Package: binfmt-support
Version: 2.2.1-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The binfmt-support service fails to start, with the following output:

systemd[1]: Starting Enable support for additional executable binary formats...
update-binfmts[536]: update-binfmts: warning: unable to close 
/proc/sys/fs/binfmt_misc/register: File exists
update-binfmts[536]: update-binfmts: warning: unable to close 
/proc/sys/fs/binfmt_misc/register: File exists
update-binfmts[536]: update-binfmts: warning: unable to close 
/proc/sys/fs/binfmt_misc/register: File exists
update-binfmts[536]: update-binfmts: exiting due to previous errors
systemd[1]: binfmt-support.service: Main process exited, code=exited, 
status=2/INVALIDARGUMENT
systemd[1]: binfmt-support.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Enable support for additional executable binary 
formats.

Best,
Facundo

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

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

Versions of packages binfmt-support depends on:
ii  libc6 2.33-7
ii  libpipeline1  1.5.6-1
ii  lsb-base  11.2

binfmt-support recommends no packages.

binfmt-support suggests no packages.

-- no debconf information




OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: binfmt-support.service errors with "unable to close /proc/sys/fs/binfmt_misc/register: File exists"

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 systemd
Bug #1012154 [binfmt-support] binfmt-support.service errors with "unable to 
close /proc/sys/fs/binfmt_misc/register: File exists"
Bug reassigned from package 'binfmt-support' to 'systemd'.
No longer marked as found in versions binfmt-support/2.2.1-2.
Ignoring request to alter fixed versions of bug #1012154 to the same values 
previously set
> severity -1 important
Bug #1012154 [systemd] binfmt-support.service errors with "unable to close 
/proc/sys/fs/binfmt_misc/register: File exists"
Severity set to 'important' from 'grave'
> affects -1 binfmt-support
Bug #1012154 [systemd] binfmt-support.service errors with "unable to close 
/proc/sys/fs/binfmt_misc/register: File exists"
Added indication that 1012154 affects binfmt-support

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

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

[Debian Bug Tracking System]

Your message dated Wed, 01 Jun 2022 09:19:22 +
with message-id 
and subject line Bug#1011802: fixed in node-crypto-browserify 3.12.0-6
has caused the Debian Bug report #1011802,
regarding node-crypto-browserify: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 1
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/crypto-browserify
>   /bin/sh -ex debian/tests/pkg-js/test
> + node test/index.js
> (node:866012) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
> security and usability issues. Please use the Buffer.alloc(), 
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> (Use `node --trace-deprecation ...` to show where the warning was created)
> TAP version 13
> # createHash in crypto-browserify test sha1 against test vectors
> # createHash in crypto-browserify test sha224 against test vectors
> # createHash in crypto-browserify test sha256 against test vectors
> # createHash in crypto-browserify test sha384 against test vectors
> # createHash in crypto-browserify test sha512 against test vectors
> # createHash in crypto-browserify test md5 against test vectors
> # createHash in crypto-browserify test rmd160 against test vectors
> node:internal/crypto/hash:67
>   this[kHandle] = new _Hash(algorithm, xofLen);
>   ^
> 
> Error: error:0308010C:digital envelope routines::unsupported
> at new Hash (node:internal/crypto/hash:67:19)
> at createHash (node:crypto:130:10)
> at run (/<>/test/create-hash.js:26:16)
> at Test. (/<>/test/create-hash.js:17:5)
> at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:99:32)
> at Test.run (/usr/share/nodejs/tape/lib/test.js:117:31)
> at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:99:32)
> at Immediate.next (/usr/share/nodejs/tape/lib/results.js:88:19)
> at processImmediate (node:internal/timers:466:21) {
>   opensslErrorStack: [ 'error:0386:digital envelope 
> routines::initialization error' ],
>   library: 'digital envelope routines',
>   reason: 'unsupported',
>   code: 'ERR_OSSL_EVP_UNSUPPORTED'
> }
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/node-crypto-browserify_3.12.0-5_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-crypto-browserify 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 

Processed: reassign 1011898 to src:node-browserify-des, forcibly merging 1011898 1011852

[Debian Bug Tracking System]

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

> reassign 1011898 src:node-browserify-des
Bug #1011898 [node-browserify-des] node-browserify-cipher: FTBFS: TypeError: 
Cannot read properties of undefined (reading 'update')
Bug reassigned from package 'node-browserify-des' to 'src:node-browserify-des'.
Ignoring request to alter found versions of bug #1011898 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1011898 to the same values 
previously set
> forcemerge 1011898 1011852
Bug #1011898 [src:node-browserify-des] node-browserify-cipher: FTBFS: 
TypeError: Cannot read properties of undefined (reading 'update')
Bug #1011852 [src:node-browserify-des] node-browserify-des: FTBFS: TypeError: 
Cannot read properties of undefined (reading 'update')
Added indication that 1011852 affects node-browserify-cipher
Bug #1011898 [src:node-browserify-des] node-browserify-cipher: FTBFS: 
TypeError: Cannot read properties of undefined (reading 'update')
Marked as found in versions node-browserify-des/1.0.2-5.
Merged 1011852 1011898
> thanks
Stopping processing here.

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

Processed: Bug#1011802 marked as pending in node-crypto-browserify

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#1011802: marked as pending in node-crypto-browserify

[Yadd]

Control: tag -1 pending

Hello,

Bug #1011802 in node-crypto-browserify 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-crypto-browserify/-/commit/0da91b563b364719e9299836e9148ae2d2704a2b


Disable RIPEMD-160 protocol

Closes: #1011802


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011802

Processed: forcibly merging 990447 968997

[Debian Bug Tracking System]

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

> forcemerge 990447 968997
Bug #990447 [shim] fwupdmgr: Unable to install new updates
Bug #968997 [shim] fwupdmgr: "Successfully" updates BIOS firmware, no effect on 
reboot
Severity set to 'serious' from 'wishlist'
There is no source info for the package 'shim' at version '15.4-7' with 
architecture ''
Unable to make a source version for version '15.4-7'
Marked as found in versions 15.4-7.
Merged 968997 990447
> thanks
Stopping processing here.

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

Processed: found 990447 in 15.4-7, severity of 990447 is serious

[Debian Bug Tracking System]

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

> found 990447 15.4-7
Bug #990447 [shim] fwupdmgr: Unable to install new updates
There is no source info for the package 'shim' at version '15.4-7' with 
architecture ''
Unable to make a source version for version '15.4-7'
Marked as found in versions 15.4-7.
> severity 990447 serious
Bug #990447 [shim] fwupdmgr: Unable to install new updates
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed (with 1 error): forcibly merging 1011898 1011852

[Debian Bug Tracking System]

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

> forcemerge 1011898 1011852
Bug #1011898 [node-browserify-des] node-browserify-cipher: FTBFS: TypeError: 
Cannot read properties of undefined (reading 'update')
Unable to merge bugs because:
package of #1011852 is 'src:node-browserify-des' not 'node-browserify-des'
Failed to forcibly merge 1011898: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: affects 1011898

[Debian Bug Tracking System]

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

> affects 1011898 node-browserify-cipher
Bug #1011898 [node-browserify-des] node-browserify-cipher: FTBFS: TypeError: 
Cannot read properties of undefined (reading 'update')
Added indication that 1011898 affects node-browserify-cipher
> thanks
Stopping processing here.

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

Processed: reassign 1011898 to node-browserify-des

[Debian Bug Tracking System]

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

> reassign 1011898 node-browserify-des
Bug #1011898 [src:node-browserify-cipher] node-browserify-cipher: FTBFS: 
TypeError: Cannot read properties of undefined (reading 'update')
Bug reassigned from package 'src:node-browserify-cipher' to 
'node-browserify-des'.
No longer marked as found in versions node-browserify-cipher/1.0.1-2.
Ignoring request to alter fixed versions of bug #1011898 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: Re: node-webpack-sources: autopkgtest failure TypeError: addMapping is not a function

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1012023 [pkg-js-tools] debian/tests/pkg-js/files not working for
Severity set to 'important' from 'serious'

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

Bug#1012024: marked as done (Please declare Breaks: dgit (<< 9.16~))

[Debian Bug Tracking System]

Your message dated Wed, 1 Jun 2022 09:37:40 +0200
with message-id 
and subject line Re: Bug#1012024: Please declare Breaks: dgit (<< 9.16~)
has caused the Debian Bug report #1012024,
regarding Please declare Breaks: dgit (<< 9.16~)
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.)


-- 
1012024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: git-buildpackage
Version: 0.9.26
Severity: serious

Hi.

With recent gbp pq (as of 0.9.26), dgit needs to pass new options
(well, actually, it does this via the config file so as to still work
with older gbp).  That's #1005873.

dgit 9.16 which I have just uploaded does this (again, sorry for the
delay).  It passes my formal autopkgtest with my sid chroot so I
expect it will be OK in ci.d.n.

As I wrote in another mail, I would appreciate it if you would
add to git-buildpackage:

  Breaks: dgit (<< 9.16~)

This will arrange that users will necessarily install the updates in
the correct order (and that partial updates will be correct).

I am filing this bug as "serious" not because I think it is RC, but
because if you agree with my suggestion, it would be good to prevent
gbp 0.9.26 migrating to testing, since it is that version that
presents the upgrade hazard, and instead migrate the updated version
with the Breaks (presumably 0.9.27).  That would avoid a window of
opportunity for lossage.

If you disagree with my choice of severity, do of course feel free to
downgrade it.

Regards,
Ian.

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
--- End Message ---
--- Begin Message ---
Version: git-buildpackage/0.9.27

Hi,
On Sat, May 28, 2022 at 10:58:34PM +0100, Ian Jackson wrote:
> Package: git-buildpackage
> Version: 0.9.26
> Severity: serious
> 
> Hi.
> 
> With recent gbp pq (as of 0.9.26), dgit needs to pass new options
> (well, actually, it does this via the config file so as to still work
> with older gbp).  That's #1005873.

This was fixed in 0.9.27. I just saw this bug by accident as I didn't
get the bug mail hence no closing via the changelog.
Cheers,
 -- Guido--- End Message ---

Bug#1012023: node-webpack-sources: autopkgtest failure TypeError: addMapping is not a function

[Yadd]

Control: severity -1 important

Decreasing severity since:
 * node-source-map 0.7 isn't published
 * workarounds exists

Processed: tagging 1009804

[Debian Bug Tracking System]

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

> tags 1009804 + pending
Bug #1009804 [src:pytest-salt-factories] pytest-salt-factories: autopkgtest 
failure with python3.10
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: limit source to pyml, tagging 1009430

[Debian Bug Tracking System]

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

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

> tags 1009430 + pending
Bug #1009430 [src:pyml] pyml: FTBFS: Test 'run file with filename' ... fails (?)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1012077: riscv64 usertags for #1012077, linuxinfo FTBFS on riscv64, other riscv CPU info?

[Tienhock Loh]

Hi, I have StarFive's VisionFive board. 

StarFive VisionFive board's cpu info:

# cat /proc/cpuinfo
processor   : 0
hart: 1
isa : rv64imafdc
mmu : sv39
uarch   : sifive,u74-mc

processor   : 1
hart: 0
isa : rv64imafdc
mmu : sv39
uarch   : sifive,u74-mc


> -Original Message-
> From: xiao sheng wen(肖盛文) 
> Sent: Wednesday, June 1, 2022 11:36 AM
> To: cont...@bugs.debian.org; 1012...@bugs.debian.org
> Cc: debian-ri...@lists.debian.org
> Subject: riscv64 usertags for #1012077, linuxinfo FTBFS on riscv64, other 
> riscv
> CPU info?
> 
> user debian-ri...@lists.debian.org
> usertag 1012077 + riscv64
> stop
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012077
> 
> Is there anybody use the riscv CPU other than sifive,u74-mc?
> Welcome to supply CPU info.
> 
> Please also sent to 1012...@bugs.debian.org.
> 
> --
> 肖盛文 xiao sheng wen Faris Xiao
> 微信(wechat)：atzlinux
> 《铜豌豆 Linux》https://www.atzlinux.com
> 基于 Debian 的 Linux 中文 桌面 操作系统
> Debian QA page:
> https://qa.debian.org/developer.php?login=atzlinux%40sina.com
> GnuPG Public Key: 0x00186602339240CB