Processed: tagging 962824

[Debian Bug Tracking System]

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

> tags 962824 + bullseye sid
Bug #962824 {Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= } 
[r-cran-v8] r-cran-v8: FTBFS against nodejs 12.18.0
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Processed: tagging 955566

[Debian Bug Tracking System]

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

> tags 955566 + bullseye sid
Bug #955566 {Done: michael.cru...@gmail.com (Michael R. Crusoe)} [src:khmer] 
khmer: autopkgtest regression: undefined references
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Bug#938234: marked as done (python-tz: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 10 Jul 2020 04:18:37 +
with message-id 
and subject line Bug#938234: fixed in python-tz 2020.1-2
has caused the Debian Bug report #938234,
regarding python-tz: Python2 removal in sid/bullseye
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.)


-- 
938234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-tz
Version: 2019.2-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:python-tz

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: python-tz
Source-Version: 2020.1-2
Done: Sandro Tosi 

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-tz 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: Fri, 10 Jul 2020 00:02:18 -0400
Source: python-tz
Architecture: source
Version: 2020.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 938234
Changes:
 python-tz (2020.1-2) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #938234
Checksums-Sha1:
 f865a8e4aaa9f9040a87384adff9961f567bec0c 2150 python-tz_2020.1-2.dsc
 98ee2352e96673c83e6d9ea4a9da77a6395d1fba 5700 python-tz_2020.1-2.debian.tar.xz
 ff396abdabd7b29a8b6be3e2d1bcfb3b650b0d95 6765 
python-tz_2020.1-2_source.buildinfo
Checksums-Sha256:
 b71597d7ddc73a4b0899e18caaca0596faaffb6ebade7e99ca3d83809ad71b52 2150 
python-tz_2020.1-2.dsc
 f17d82dfe61e6e2ceb30d93422e665354b4e2b65d890803e932d4f8c8b531178 5700 
python-tz_2020.1-2.debian.tar.xz
 b6ea9af465b0fff543d7a6475083db674a80a1eb6fc2332c27c63585468769aa 6765 
python-tz_2020.1-2_source.buildinfo
Files:
 dd48c74e2ad90713e3b35551987625a6 2150 python optional 

Processed: block 964601 with 959837

[Debian Bug Tracking System]

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

> block 964601 with 959837
Bug #964601 [src:google-oauth-client-java] google-oauth-client-java: FTBFS: 
[ERROR] Failed to execute goal on project google-oauth-client: Could not 
resolve dependencies for project 
com.google.oauth-client:google-oauth-client:jar:1.27.0: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
io.grpc:grpc-context:jar:debian has not been downloaded from it before. -> 
[Help 1]
964601 was not blocked by any bugs.
964601 was not blocking any bugs.
Added blocking bug(s) of 964601: 959837
> thanks
Stopping processing here.

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

Processed: block 964625 with 959837

[Debian Bug Tracking System]

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

> block 964625 with 959837
Bug #964625 [src:google-api-client-java] google-api-client-java: FTBFS: Failed 
to execute goal on project google-api-client: Could not resolve dependencies 
for project com.google.api-client:google-api-client:jar:1.27.1: Cannot access 
central (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
io.grpc:grpc-context:jar:debian has not been downloaded from it before. -> 
[Help 1]
964625 was not blocked by any bugs.
964625 was not blocking any bugs.
Added blocking bug(s) of 964625: 959837
> thanks
Stopping processing here.

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

Processed: py2removal bugs severity updates - 2020-07-10 03:34:38.560681+00:00

[Debian Bug Tracking System]

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # and https://lists.debian.org/debian-python/2020/03/msg00087.html
> # mail threads for more details on this severity update
> # python-tz is a module and has 0 external rdeps or not in testing
> severity 938234 serious
Bug #938234 [src:python-tz] python-tz: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#964678: marked as done (wml/slice must depend on wml package)

[Debian Bug Tracking System]

Your message dated Fri, 10 Jul 2020 00:48:30 +
with message-id 
and subject line Bug#964678: fixed in wml 2.28.0~ds1-2
has caused the Debian Bug report #964678,
regarding wml/slice must depend on wml package
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.)


-- 
964678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dictionaries-common
Version: 1.28.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> slice -oUNDEF+I+IW+IA-A-H-W-AH:scripts/maintainer/config-ispell 
> scripts/maintainer/config.in
> Can't locate TheWML/Backends/Slice/Main.pm in @INC (you may need to install 
> the TheWML::Backends::Slice::Main module) (@INC contains: /usr/share/wml 
> /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.3 
> /usr/local/share/perl/5.30.3 /usr/lib/x86_64-linux-gnu/perl5/5.30 
> /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base 
> /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 
> /usr/local/lib/site_perl) at /usr/bin/slice line 10.
> BEGIN failed--compilation aborted at /usr/bin/slice line 10.
> make[1]: *** [Makefile:147: scripts/maintainer/config-ispell] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/dictionaries-common_1.28.1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: wml
Source-Version: 2.28.0~ds1-2
Done: Axel Beckert 

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated wml 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: Fri, 10 Jul 2020 02:16:00 +0200
Source: wml
Architecture: source
Version: 2.28.0~ds1-2
Distribution: unstable
Urgency: low
Maintainer: Axel Beckert 
Changed-By: Axel Beckert 
Closes: 964678
Changes:
 wml (2.28.0~ds1-2) unstable; urgency=low
 .
   * Retroactively mention #916519 in the 2.10.1~ds1-1 changelog entry.
   * Retroactively mention #928932 in the 2.12.2~ds1-3 changelog entry.
   * Drop debian/source/lintian-overrides now that #964281 is fixed.
   * Make slice work standalone again. (Closes: #964678)
 + Move /usr/share/wml/TheWML/Backends/Slice/ from wml to slice.
 + Move /usr/share/wml/TheWML/CmdLine/IO.pm from wml to slice.
 + Add according Breaks and Replaces headers.
 + Let slice depend on libpath-tiny-perl and libclass-xsaccessor-perl.
 + Drop dependency on libbit-vector-perl from wml.
Checksums-Sha1:
 c25a47f5c7fe60a3650853d4fd1acdc79265b261 2411 wml_2.28.0~ds1-2.dsc
 fc79a3201481b9e39ba2869bafde08ba37b152f8 28308 wml_2.28.0~ds1-2.debian.tar.xz
 50b1f006ae27daf333d2a62a37fc1857cc047176 10680 
wml_2.28.0~ds1-2_source.buildinfo
Checksums-Sha256:
 d3fbf33a43c62e9f679ca4f4ef0761a93dc1d605eac9cf85e36e35092859764e 2411 
wml_2.28.0~ds1-2.dsc
 bcde1555b4c38ba017cb391bf908aa6766ddf96739b8816a389c8a8f3cdae4a6 28308 
wml_2.28.0~ds1-2.debian.tar.xz
 0fa886704cdc0f19c5ce404bd20a22d4a714c949d60de02c2543011cf8b3ce9d 10680 
wml_2.28.0~ds1-2_source.buildinfo
Files:
 2828463e9610a9ad79098aadb67ce03e 2411 web optional wml_2.28.0~ds1-2.dsc
 2e9573430dea53cc48d250510a681c94 28308 web optional 
wml_2.28.0~ds1-2.debian.tar.xz
 ea7a49a8a61ef496f15ca6a871f83c2a 10680 web optional 
wml_2.28.0~ds1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERoyJeTtCmBnp12Ema+Zjx1o1yXUFAl8HtKwACgkQa+Zjx1o1
yXWkIA//fdfydceYzJAmXb

Bug#964678: marked as pending in wml

[Axel Beckert]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/wml/-/commit/d921e540cf7f70113152a0d031a074d1b695


Make slice work standalone again. (Closes: #964678)

* Move /usr/share/wml/TheWML/Backends/Slice/ from wml to slice.
* Move /usr/share/wml/TheWML/CmdLine/IO.pm from wml to slice.
* Add according Breaks and Replaces headers.
* Let slice depend on libpath-tiny-perl and libclass-xsaccessor-perl.
* Drop dependency on libbit-vector-perl from wml.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/964678

Processed: Bug#964678 marked as pending in wml

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #964678 [slice] wml/slice must depend on wml package
Added tag(s) pending.

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

Bug#964702: marked as done (pdfminer: FTBFS: /bin/sh: 1: rename.ul: not found)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 23:20:39 +
with message-id 
and subject line Bug#963521: fixed in pdfminer 20191020+dfsg-3
has caused the Debian Bug report #963521,
regarding pdfminer: FTBFS: /bin/sh: 1: rename.ul: not found
to be marked as done.

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

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


-- 
963521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pdfminer
Version: 20191020+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> pybuild --install -p 3
> I: pybuild base:217: /usr/bin/python3 setup.py install --root 
> /<>/debian/python3-pdfminer 
> running install
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/high_level.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/latin_enc.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/psparser.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/ccitt.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/__init__.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/image.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/pdftypes.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/pdfinterp.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/ascii85.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/pdfdocument.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/cmapdb.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/layout.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/pdfpage.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/lzw.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/encodingdb.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/pdffont.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/settings.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/glyphlist.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/pdfparser.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/pdfdevice.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/rijndael.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/fontmetrics.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/runlength.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/pdfcolor.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/utils.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/arcfour.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/converter.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> creating /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/UniJIS-UCS2-HW-H.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/Katakana-H.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/UniJIS-UTF8-H.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/to-unicode-Adobe-GB1.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/HKgccs-B5-H.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/NWP-H.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/CNS2-H.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer

Bug#963521: marked as done (pdfminer: please stop using rename.ul)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 23:20:39 +
with message-id 
and subject line Bug#963521: fixed in pdfminer 20191020+dfsg-3
has caused the Debian Bug report #963521,
regarding pdfminer: please stop using rename.ul
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.)


-- 
963521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pdfminer
Version: 20191020+dfsg-2

Dear Maintainer,

pdfminer's debian/rules uses the rename.ul binary from util-linux,
which will soon stop installing this binary. Please use another
tool, for example prename, instead.

Thanks,
Chris
--- End Message ---
--- Begin Message ---
Source: pdfminer
Source-Version: 20191020+dfsg-3
Done: Daniele Tricoli 

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

Debian distribution maintenance software
pp.
Daniele Tricoli  (supplier of updated pdfminer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Jul 2020 00:47:36 +0200
Source: pdfminer
Architecture: source
Version: 20191020+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Daniele Tricoli 
Closes: 963521
Changes:
 pdfminer (20191020+dfsg-3) unstable; urgency=medium
 .
   [ Emmanuel Arias ]
   * d/control: Bumps Standards-Version to 4.5.0.
   * Stop use rename.ul because binary.
 - Will stop install it on utils-linux.
 Use rename instead (Closes: #963521).
   * Run wrap-and-sort.
   * d/salsa-ci.yml: Enable salsa-ci.yml.
   * d/tests/python3-pdfminer: use py3versions -s instead of -i.
 .
   [ Daniele Tricoli ]
   * Bump debhelper-compat to 13.
Checksums-Sha1:
 00292fff9de2b22516aa8844e38e2ae913388a1d 2389 pdfminer_20191020+dfsg-3.dsc
 d3558f405621bcf44250cb5c14542c20c15f43a7 11404 
pdfminer_20191020+dfsg-3.debian.tar.xz
 f14a885265959f85b7f25a53eaec8845e4adc8c9 6749 
pdfminer_20191020+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 d25a95e0e91f07b02b84e2ab0e9dd21302e4a89404caa543d48f2c2340a74d01 2389 
pdfminer_20191020+dfsg-3.dsc
 db255b075cd8e4e64262e38a657144a76f9e30985450e5e71610b72e6f240576 11404 
pdfminer_20191020+dfsg-3.debian.tar.xz
 80d8234ab1af7258067e8472190a0bca1d3a529289c3da468bf0705570739ad0 6749 
pdfminer_20191020+dfsg-3_amd64.buildinfo
Files:
 bdd70277e97ee9a61713f10057e7a281 2389 python optional 
pdfminer_20191020+dfsg-3.dsc
 eaf5ea7b3b7cfa198465de8002adde06 11404 python optional 
pdfminer_20191020+dfsg-3.debian.tar.xz
 3432ed2a7065783fe7780709ac21ebae 6749 python optional 
pdfminer_20191020+dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEExlrvn+W/jMvW7bAZi69SLA1szt0FAl8Hn7oRHGVyaW9sQGRl
Ymlhbi5vcmcACgkQi69SLA1szt1YQRAAiyy1pr2ZBjBallA4q2kI3YIYl1SNYjXS
9PC/cHkE3aCAekEMRLnr1/zb5evI6WbLnzPfVj+BwIlyVV/4HHac+Gw+QhW4ZPwB
JUxMHOtV7d1J2o0fdeXtvnPfu2Ppd+9VjYgfZHejTuf1/BjFDC7XisGSnwWzlzde
xfHb7CwyhTx+FrNFbqeHpAJctjajeJ3EdvHn+8ElVNLPva4xtQ5IXdOq5OV0xXuB
cXes9H7WYgHMKbpe3gb7q4+ZFZvyGEwyi4fnaMq33VCdQ8XhKqHA+f+2gxwryVxo
zdn7c9bI9zhi2gTYdcVcLzAREnNEX6VTJhYKnol8x64OUlL0L24yQi5TMNJSDKxu
hyeR/K2vYdQk1KqPWZmygNj94b8jE94KimijvXtj5FpEgOIBpiM95gCaIVArV13j
jVjk5R3i7K2OMzP3pd+v590Atlbf1tR3V6S628mjxWxH9fQKGzjAlTBEtLdeURBr
PE81iYPa2EY4YqdRn8nGKa8hZW7mPxTm6WsMgTRfZ+Q/Z194BjYvF8zP1aEganY9
lGISP3Zh51CB3gIbIOeYGXN3iYmifEDIQZfvytNIFb+/aSGACNR1l9kY4yGw7yTB
qiwy1KXFVRVQhFF1KoN/HqlhwrnDEHn4Cjfpy/hblGCyUK5vWlzr80X3PBQ8pRXA
Ibrh8aDxONo=
=glru
-END PGP SIGNATURE End Message ---

Bug#964646: marked as done (oscar: FTBFS: ../../oscar/SleepLib/machine.h:162:61: error: ‘QString& QString::sprintf(const char*, ...)’ is deprecated: Use asprintf(), arg() or QTextStream instead [-Werr

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 22:19:41 +
with message-id 
and subject line Bug#964646: fixed in oscar 1.1.1-1
has caused the Debian Bug report #964646,
regarding oscar: FTBFS: ../../oscar/SleepLib/machine.h:162:61: error: ‘QString& 
QString::sprintf(const char*, ...)’ is deprecated: Use asprintf(), arg() or 
QTextStream instead [-Werror=deprecated-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.)


-- 
964646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: oscar
Version: 1.1.0-testing-3-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> g++ -c -pipe -Werror -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -std=gnu++11 -frtti -Wall -Wextra -D_REENTRANT -fPIC 
> -Dhelpless -DQT_DEPRECATED_WARNINGS -DNO_UPDATER -DLOCK_RESMED_SESSIONS 
> -D_TTY_POSIX_ -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_OPENGL_LIB 
> -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_XML_LIB 
> -DQT_SERIALPORT_LIB -DQT_CORE_LIB -I../../oscar -I. -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSerialPort -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -I. -I. 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o mainwindow.o 
> ../../oscar/mainwindow.cpp
> In file included from ../../oscar/SleepLib/profiles.h:19,
>  from ../../oscar/exportcsv.cpp:14:
> ../../oscar/SleepLib/machine.h: In member function ‘QString Machine::hexid()’:
> ../../oscar/SleepLib/machine.h:162:61: error: ‘QString& 
> QString::sprintf(const char*, ...)’ is deprecated: Use asprintf(), arg() or 
> QTextStream instead [-Werror=deprecated-declarations]
>   162 | QString hexid() { return QString().sprintf("%08lx", m_id); }
>   | ^
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qdir.h:43,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qfiledialog.h:44,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QFileDialog:1,
>  from ../../oscar/exportcsv.cpp:9:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:382:14: note: declared here
>   382 | QString (const char *format, ...) 
> Q_ATTRIBUTE_FORMAT_PRINTF(2, 3);
>   |  ^~~
> In file included from ../../oscar/SleepLib/profiles.h:19,
>  from ../../oscar/daily.h:25,
>  from ../../oscar/daily.cpp:26:
> ../../oscar/SleepLib/machine.h: In member function ‘QString Machine::hexid()’:
> ../../oscar/SleepLib/machine.h:162:61: error: ‘QString& 
> QString::sprintf(const char*, ...)’ is deprecated: Use asprintf(), arg() or 
> QTextStream instead [-Werror=deprecated-declarations]
>   162 | QString hexid() { return QString().sprintf("%08lx", m_id); }
>   | ^
> In file included from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qhashfunctions.h:44,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:47,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstringlist.h:41,
>  from /usr/include/x86_64-linux-gnu/qt5/QtGui/qcolor.h:46,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtGui/qtextformat.h:44,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtGui/QTextCharFormat:1,
>  from ../../oscar/daily.cpp:9:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:382:14: note: declared here
>   382 | QString (const char *format, ...) 
> Q_ATTRIBUTE_FORMAT_PRINTF(2, 3);
>   |  ^~~
> ../../oscar/exportcsv.cpp: In member function ‘void 
> ExportCSV::on_exportButton_clicked()’:
> ../../oscar/expor

Bug#964612: marked as done (node-base64url: FTBFS: src/base64url.ts(11,64): error TS2345: Argument of type 'string' is not assignable to parameter of type '"ascii" | "utf8" | "utf-8" | "utf16le" | "uc

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 21:59:25 +
with message-id 
and subject line Bug#964612: fixed in node-base64url 3.0.1-4
has caused the Debian Bug report #964612,
regarding node-base64url: FTBFS: src/base64url.ts(11,64): error TS2345: 
Argument of type 'string' is not assignable to parameter of type '"ascii" | 
"utf8" | "utf-8" | "utf16le" | "ucs2" | "ucs-2" | "base64" | "latin1" | 
"binary" | "hex" | undefined'.
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.)


-- 
964612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-base64url
Version: 3.0.1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> pandoc --from gfm-raw_html --to html --standalone --output readme.html 
> readme.md
> [WARNING] This document format requires a nonempty  element.
>   Please specify either 'title' or 'pagetitle' in the metadata,
>   e.g. by using --metadata pagetitle="..." on the command line.
>   Falling back to 'readme'
> pandoc --from gfm-raw_html --to plain --output readme.txt readme.md
> tsc
> src/base64url.ts(11,64): error TS2345: Argument of type 'string' is not 
> assignable to parameter of type '"ascii" | "utf8" | "utf-8" | "utf16le" | 
> "ucs2" | "ucs-2" | "base64" | "latin1" | "binary" | "hex" | undefined'.
> make[1]: *** [debian/rules:9: override_dh_auto_build] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/node-base64url_3.0.1-3_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: node-base64url
Source-Version: 3.0.1-4
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated node-base64url 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, 09 Jul 2020 23:34:15 +0200
Source: node-base64url
Architecture: source
Version: 3.0.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Closes: 964612
Changes:
 node-base64url (3.0.1-4) unstable; urgency=medium
 .
   * extend patch 1001 to also cover decode() (not only encode());
 closes: bug#964612, thanks to Lucas Nussbaum
   * use debhelper compatibility level 13 (not 12)
   * copyyright: extend coverage
   * add non-superficial autopkgtest
Checksums-Sha1:
 b315aeaed86f7c0c26c816d4deba2ab98bd93b9d 2134 node-base64url_3.0.1-4.dsc
 934d53f3f729fedecb37d80926176415081e3219 4408 
node-base64url_3.0.1-4.debian.tar.xz
 bf1d1156458180eda77958439fd1c2496da3a7bb 7168 
node-base64url_3.0.1-4_amd64.buildinfo
Checksums-Sha256:
 591f9f093a74fdefd683e9f81686af98a721e2f6cfc47966fffd7d5252725197 2134 
node-base64url_3.0.1-4.dsc
 0bbafd70a6d75203d680d387386366a9e0a5e4a63ae1ce5d88ffb06f6f403186 4408 
node-base64url_3.0.1-4.debian.tar.xz
 c550a1d86b0ca31e695a4d70fb4beee772411c55da8165f8933531745b1d0124 7168 
node-base64url_3.0.1-4_amd64.buildinfo
Files:
 b44ec750e73c1ef806384e38e1c17838 2134 javascript optional 
node-base64url_3.0.1-4.dsc
 3f1b3aeab3e4684d85c9e08d0ff0f371 4408 javascript optional 
node-base64url_3.0.1-4.debian.tar.xz
 10ec463ef01b6712a30b279ff57fd29a 7168 javascript option

Processed: reassign 964750 to src:hypercorn

[Debian Bug Tracking System]

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

> reassign 964750 src:hypercorn 0.9.4-1
Bug #964750 [hypercorn] hypercorn build-dependencies unsatisfiable in testing.
Bug reassigned from package 'hypercorn' to 'src:hypercorn'.
No longer marked as found in versions 0.9.4-1.
Ignoring request to alter fixed versions of bug #964750 to the same values 
previously set
Bug #964750 [src:hypercorn] hypercorn build-dependencies unsatisfiable in 
testing.
Marked as found in versions hypercorn/0.9.4-1.
> thanks
Stopping processing here.

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

Processed: tagging 964750

[Debian Bug Tracking System]

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

> tags 964750 + ftbfs
Bug #964750 [hypercorn] hypercorn build-dependencies unsatisfiable in testing.
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#964750: hypercorn build-dependencies unsatisfiable in testing.

[peter green]

Package: hypercorn
Version: 0.9.4-1
Severity: serious
Tags: patch
Justification: rc policy "packages must be buildable within the same release"

hypercorn build-depends on python3-asynctest, which is built from the 
python-asynctest source
package.

According to bug 954554 python3-asynctest is incompatible with the version of 
python3 currently
in testing/unstable. A patch exists but according to discussion in that bug 
report it has been
rejected by both the upstream and the Debian maintainers of python-asynctest.

As a result the python-asynctest and hypercorn source packages (and their 
corresponding binary
packages) were autoremoved from testing on the 1st of June.

Unfortunately, due to a bug in the testing migration scripts* hypercorn 
re-entered testing on the
26th of June.

Bug 954554 had a link to an upstream patch for hypercorn to stop using, I 
applied the relavent parts
of said upstream patch to the Debian hypercorn package, updated the 
build-dependencies accordingly
and was able to succesfully build the package.

Alternatively the upstream change seems to be included in the latest upstream 
release of hypercorn,
so uploading that would be another option.

A debdiff is attached, I may upload this later as a team upload (I don't see 
how this patch can
affect runtime functionality but I'd still rather get a sanity check from 
someone who actually.
uses the package).

* see https://lists.debian.org/debian-release/2020/06/msg00375.html
diff -Nru hypercorn-0.9.4/debian/changelog hypercorn-0.9.4/debian/changelog
--- hypercorn-0.9.4/debian/changelog2020-04-17 11:36:29.0 +
+++ hypercorn-0.9.4/debian/changelog2020-07-09 19:51:28.0 +
@@ -1,3 +1,13 @@
+hypercorn (0.9.4-2) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Apply upstream patch to move away from asynctest and move towards
+the testing functionality in the standard library.
+  * Update build-depenencies, remove build-dependency on python3-asynctest
+and add build-dependency on python3-all-dev (>= 3.8.2-3) | python3-mock
+
+ -- Peter Michael Green   Thu, 09 Jul 2020 19:51:28 +
+
 hypercorn (0.9.4-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru hypercorn-0.9.4/debian/control hypercorn-0.9.4/debian/control
--- hypercorn-0.9.4/debian/control  2020-04-17 11:36:29.0 +
+++ hypercorn-0.9.4/debian/control  2020-07-09 19:51:28.0 +
@@ -14,7 +14,7 @@
  python3-priority,
  python3-toml,
  python3-typing-extensions,
- python3-asynctest,
+ python3-all-dev (>= 3.8.2-3) | python3-mock,
  python3-hypothesis,
  python3-pytest,
  python3-pytest-asyncio,
diff -Nru hypercorn-0.9.4/debian/patches/series 
hypercorn-0.9.4/debian/patches/series
--- hypercorn-0.9.4/debian/patches/series   1970-01-01 00:00:00.0 
+
+++ hypercorn-0.9.4/debian/patches/series   2020-07-09 19:46:12.0 
+
@@ -0,0 +1 @@
+update-testing.patch
diff -Nru hypercorn-0.9.4/debian/patches/update-testing.patch 
hypercorn-0.9.4/debian/patches/update-testing.patch
--- hypercorn-0.9.4/debian/patches/update-testing.patch 1970-01-01 
00:00:00.0 +
+++ hypercorn-0.9.4/debian/patches/update-testing.patch 2020-07-09 
19:51:18.0 +
@@ -0,0 +1,274 @@
+This patch is based on the upstream commit detailed below and was
+adapted to apply to the Debian hypercorn package by Peter Michael
+Green
+
+Specifically  changes to tox.ini and .gitlab-ci.yml were removed
+from the patch as those files do not  seem to exist in the Debian
+Hypercorn 0.9.4 Package.
+
+
+commit 80e2ad5db107c42d42471ea64764d2b42202349c
+Author: pgjones 
+Date:   Sun May 31 18:53:02 2020 +0100
+
+Update testing
+
+Switch from asynctest to the stdlib (with a backport as AsyncMock was
+introduced in 3.8) and update the base python versions to 3.8.
+
+diff --git a/setup.cfg b/setup.cfg
+index 3e4a8f0..36c4ad2 100644
+--- a/setup.cfg
 b/setup.cfg
+@@ -21,9 +21,6 @@ ignore_missing_imports = True
+ [mypy-aioquic.*]
+ ignore_missing_imports = True
+ 
+-[mypy-asynctest.*]
+-ignore_missing_imports = True
+-
+ [mypy-cryptography.*]
+ ignore_missing_imports = True
+ 
+diff --git a/setup.py b/setup.py
+index 5e4e461..392ef5a 100644
+--- a/setup.py
 b/setup.py
+@@ -25,8 +25,8 @@ INSTALL_REQUIRES = [
+ ]
+ 
+ TESTS_REQUIRE = [
+-"asynctest",
+ "hypothesis",
++"mock",
+ "pytest",
+ "pytest-asyncio",
+ "pytest-cov",
+diff --git a/tests/protocol/test_h11.py b/tests/protocol/test_h11.py
+index 3a635fa..eaef1dd 100755
+--- a/tests/protocol/test_h11.py
 b/tests/protocol/test_h11.py
+@@ -1,13 +1,12 @@
+ import asyncio
+ from typing import Any
+-from unittest.mock import call
++from unittest.mock import call, Mock
+ 
+ import h11
+ import pytest
+ from _pytest.monkeypatch import MonkeyPatch
+ 
+ import hypercorn.protocol.h11
+-from asynctest.mock import CoroutineMock, Mock as AsyncMock
+ from hypercorn.asyncio.tcp_server import EventWrapper
+ from hypercorn.config 

Processed: Bug#964612 marked as pending in node-base64url

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #964612 [src:node-base64url] node-base64url: FTBFS: 
src/base64url.ts(11,64): error TS2345: Argument of type 'string' is not 
assignable to parameter of type '"ascii" | "utf8" | "utf-8" | "utf16le" | 
"ucs2" | "ucs-2" | "base64" | "latin1" | "binary" | "hex" | undefined'.
Added tag(s) pending.

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

Bug#964612: marked as pending in node-base64url

[Jonas Smedegaard]

Control: tag -1 pending

Hello,

Bug #964612 in node-base64url 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-base64url/-/commit/bee38409073efe10a77a231ddb98b0f984afd493


extend patch 1001 to also cover decode() (not only encode()); closes: 
bug#964612, thanks to Lucas Nussbaum


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/964612

Bug#954070: marked as done (fdroidserver: Incorrect Litecoin address validation)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 21:17:08 +
with message-id 
and subject line Bug#954070: fixed in fdroidserver 1.1.7-1~deb10u1
has caused the Debian Bug report #954070,
regarding fdroidserver: Incorrect Litecoin address validation
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.)


-- 
954070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fdroidserver
Version: 1.1.4-1~deb10u1
Severity: normal

Hello,

When using fdroid on the latest fdroiddata repository, I get this error:
CRITICAL: 'MTuf45ZvxhMWWo4v8YBbFDTLsFcGtpcPNT' is not a valid Litecoin address
in com.readrops.app. Regex pattern: ^L[a-zA-Z0-9]{33}$

But this Litecoin address is valid.

This has already been fixed upstream:
https://gitlab.com/fdroid/fdroidserver/-/merge_requests/644

Regards,



-- System Information:
Debian Release: 10.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-8-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), 
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fdroidserver depends on:
ii  androguard   3.3.3-1
ii  default-jdk-headless 2:1.11-71
ii  openjdk-11-jdk-headless  11.0.6+10-1~deb10u1
ii  python3  3.7.3-1
ii  python3-clint0.5.1-1
ii  python3-defusedxml   0.5.0-2
ii  python3-git  2.1.11-1
ii  python3-libcloud 2.4.0-1
ii  python3-mwclient 0.8.7-1
ii  python3-paramiko 2.6.0-1~bpo10+1
ii  python3-pil  5.4.1-2+deb10u1
ii  python3-pyasn1   0.4.2-3
ii  python3-pyasn1-modules   0.2.1-0.2
ii  python3-qrcode   6.1-1
ii  python3-requests 2.21.0-1
ii  python3-ruamel.yaml  0.15.34-1+b1
ii  python3-vagrant  0.5.15-2
ii  python3-yaml 3.13-2
ii  rsync3.1.3-6

Versions of packages fdroidserver recommends:
ii  android-sdk 25.0.0+11+deb10u1
ii  apksigner   0.8-2
ii  git 1:2.20.1-2+deb10u1
ii  gnupg   2.2.12-1+deb10u1
ii  opensc  0.19.0-1
ii  openssh-client  1:7.9p1-10+deb10u2
pn  s3cmd   
ii  wget1.20.1-1.1
ii  zipalign1:8.1.0+r23-2

Versions of packages fdroidserver suggests:
ii  gradle   4.4.1-6
pn  qemu-kvm 
ii  vagrant  2.2.3+dfsg-1
pn  vagrant-cachier  
ii  vagrant-libvirt  0.0.45-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fdroidserver
Source-Version: 1.1.7-1~deb10u1
Done: Hans-Christoph Steiner 

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

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated fdroidserver 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: Sat, 16 May 2020 22:15:14 +0200
Source: fdroidserver
Architecture: source
Version: 1.1.7-1~deb10u1
Distribution: buster
Urgency: medium
Maintainer: Hans-Christoph Steiner 
Changed-By: Hans-Christoph Steiner 
Closes: 954070
Changes:
 fdroidserver (1.1.7-1~deb10u1) buster; urgency=medium
 .
   * New upstream release targeted for Debian/buster (Closes: #954070)
   * Remove "Recommends" test, ci.debian.net do not support binfmt_misc:
 https://salsa.debian.org/ci-team/debian-ci-config/-/issues/1
Checksums-Sha1:
 4fb839850b41e1ae0852147e8c86588dc0361ac8 2047 fdroidserver_1.1.7-1~deb10u1.dsc
 0d053332974feb0d3e2e59ab9e7574496be8ea92 4125658 fdroidserver_1.1.7.orig.tar.gz
 fe1cbce4b0e507d8b24df9bab9f3b5b288061007 488 fdroidserver_1.1.7.orig.tar.gz.asc
 97425ab101f478640a2ef3ad22843a860ddc08a3 17644 
fdroidserver_1.1.7-1~deb10u1.debian.tar.xz
 3d8f845c3d1533ca5d839b6ad0bca270e15ed7b3 5770 
fdroidserver_1.1.7-1~deb10u1_source.buildinfo
Checksums-Sha256:
 

Processed: closing 964471

[Debian Bug Tracking System]

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

> close 964471 1:7.0.0~rc1-4
Bug #964471 [libreoffice-l10n-de,libreoffice-l10n-ru] libreoffice-l10n-ru: 
error when configuring: cp: cannot create regular file 
'/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
Bug #964505 [libreoffice-l10n-de,libreoffice-l10n-ru] Upgradin package from 
1:6.4.5~rc1-2 fails
Ignoring request to alter fixed versions of bug #964471 to the same values 
previously set
Ignoring request to alter fixed versions of bug #964505 to the same values 
previously set
Bug #964471 [libreoffice-l10n-de,libreoffice-l10n-ru] libreoffice-l10n-ru: 
error when configuring: cp: cannot create regular file 
'/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
Bug #964505 [libreoffice-l10n-de,libreoffice-l10n-ru] Upgradin package from 
1:6.4.5~rc1-2 fails
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#964508: marked as done (libextractor-plugins-all: not installable due to typo in Depends: libextractor-plugin-exiv[2])

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 21:06:10 +
with message-id 
and subject line Bug#964508: fixed in libextractor 1:1.10-1
has caused the Debian Bug report #964508,
regarding libextractor-plugins-all: not installable due to typo in Depends: 
libextractor-plugin-exiv[2]
to be marked as done.

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

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


-- 
964508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libextractor-plugins-all
Version: 1:1.9-4
Severity: serious

There is a typo in the Depends field, it should say
libextractor-plugin-exiv2 instead of libextractor-plugin-exiv.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: libextractor
Source-Version: 1:1.10-1
Done: Bertrand Marc 

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

Debian distribution maintenance software
pp.
Bertrand Marc  (supplier of updated libextractor 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, 08 Jul 2020 21:31:10 +0200
Source: libextractor
Architecture: source
Version: 1:1.10-1
Distribution: unstable
Urgency: medium
Maintainer: Bertrand Marc 
Changed-By: Bertrand Marc 
Closes: 964507 964508
Changes:
 libextractor (1:1.10-1) unstable; urgency=medium
 .
   * Make libextractor-plugins-all Architecture: all and Multi-arch:
 foreign.
   * Make libextractor-plugins-all depends on libextractor-plugin-exiv2
 (fix typo, Closes: #964508).
   * Fix typo in debian/tests/control: depend on libextractor-plugins-all
 (Closes: #964507).
   * Remove debian/patches/*, included upstream.
   * Add a patch to fix the soname.
   * Update years in debian/copyright.
   * Simplify debian/rules with execute_after_* rules.
   * Install the static libraries in libextractor-dev.
Checksums-Sha1:
 22b345690de5ac05363dd7b17159c2961b382c3d 4231 libextractor_1.10-1.dsc
 36721a2f2a7ff720204c9ee728e3cf0b7e6099ac 8376668 libextractor_1.10.orig.tar.gz
 a9851305de38989c58ea6243a0830a3a9fa23691 833 libextractor_1.10.orig.tar.gz.asc
 9d4978bd6010aaa28fe1fa54e93e69147dd588ea 18144 
libextractor_1.10-1.debian.tar.xz
 63896fdb9a8002603145b3b1b3dc7ec21e5da6c8 27025 
libextractor_1.10-1_amd64.buildinfo
Checksums-Sha256:
 1b4bbd3e6725b4096e74056482db981d6567e0351e4654416ce6d8d3b3067b6d 4231 
libextractor_1.10-1.dsc
 9eed11b5ddc7c929ba112c50de8cfaa379f1d99a0c8e064101775837cf432357 8376668 
libextractor_1.10.orig.tar.gz
 236ff050f1694fe8150f410518f37a5f2b119280d031c8bb712862757663595d 833 
libextractor_1.10.orig.tar.gz.asc
 c0f6573929690f6daa159acb94049951c113b7ba227388c9913351930fd56581 18144 
libextractor_1.10-1.debian.tar.xz
 975033fa6d3cb21004d337f9496f200a0e8ce6c6ecedfcf78cb6a3e6a85c2d90 27025 
libextractor_1.10-1_amd64.buildinfo
Files:
 81d4c3396c09c81f4b78bdfc7d297f64 4231 libs optional libextractor_1.10-1.dsc
 e937a97e0d34a7344af0e3a63e421e4b 8376668 libs optional 
libextractor_1.10.orig.tar.gz
 190ba76f88b5bc2497a7d1d0300b83dd 833 libs optional 
libextractor_1.10.orig.tar.gz.asc
 a26790a7451d7bfdfa0f09242a450aec 18144 libs optional 
libextractor_1.10-1.debian.tar.xz
 a8f57175fc5d74645862f56fd588d800 27025 libs optional 
libextractor_1.10-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEKUUr1GPOZwMj0JuIoEqzutviY+4FAl8Hf88RHGJtYXJjQGRl
Ymlhbi5vcmcACgkQoEqzutviY+57rhAAjT3H9fmaNA0glSOhi3lyFqkxGVZxzZKf
C0FxeyeLwBIMjFRfwOACSnO0K9AOhPQxUEVciTw5EjA2jvaBaRK0gCjgiJ25vEpA
Bf4EfCl44kY8HctTo/oLl4maJvTwiEvklNCbm4PNJyOpSiRlBlQIC4LItFC5tS3z
jFPZKnqlrnaal3dM6l1zm2J8sF++yTRvu6PecuYwYt5ohv7JEYhAZC3SGhiDsKeK
7OkolD3Diw1UXCN296K8wpG141uHUsPH//Duo3br3LZaNdaEAHnxiSA6uZgtat4g
rvBYCfQf1G4jEKjNeuz6y3mnfdOKUHacw88w8fzAj8ZZoEujKg7Sd9+wTGoZfLwJ
uskP4F2TtLmpbzV4urpC4sgmXycQlMi+AU22ZOb7Ov8Dq0bl3f9nCi+iVoRi7oAl
UeGZ4o1SHudRt45zL+yG2rniTY65LgEREvF5d1HW/2ahrRbYxdMFeso79uGAqzxO
i6wx2HD5wkRZH2XO/T8p66CBvWP3Krn0MPs22Hd7zcvxes/ezuc3FJltoetxOj+z
b/qaPwcn1U0rs/JHyWRVoSZHZ2vErLghrxaf9ycsBvZCWT2gvjc1bv3EVNXCgkrX

Bug#952655: marked as done (debian-ports-archive-keyring: Expired Debian Ports Archive Automatic Signing Key (2020))

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 21:02:07 +
with message-id 
and subject line Bug#952655: fixed in debian-ports-archive-keyring 
2019.11.05~deb10u1
has caused the Debian Bug report #952655,
regarding debian-ports-archive-keyring: Expired Debian Ports Archive Automatic 
Signing Key (2020)
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.)


-- 
952655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-ports-archive-keyring
Version: 2019.11.05
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Debian Ports Archive Automatic Signing Key (2020) seems to have expired on the 
31st of January,
according to 
http://gozer.rediris.es:11371/pks/lookup?search=0x84C573CD4E1AFD6C=vindex

Therefore, running apt-get update results in an error:
Get:1 http://ftp.ports.debian.org/debian-ports sid InRelease [55.3 kB]
Err:1 http://ftp.ports.debian.org/debian-ports sid InRelease
  The following signatures were invalid: EXPKEYSIG 84C573CD4E1AFD6C Debian 
Ports Archive Automatic Signing Key (2020) 

So I am unable to update my system.

Best wishes,
Prem

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)

Kernel: Linux 5.4.0-1-powerpc
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), 
LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: debian-ports-archive-keyring
Source-Version: 2019.11.05~deb10u1
Done: Aurelien Jarno 

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated 
debian-ports-archive-keyring 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, 09 Jul 2020 21:29:09 +0200
Source: debian-ports-archive-keyring
Architecture: source
Version: 2019.11.05~deb10u1
Distribution: buster
Urgency: medium
Maintainer: Aurelien Jarno 
Changed-By: Aurelien Jarno 
Closes: 952655
Changes:
 debian-ports-archive-keyring (2019.11.05~deb10u1) buster; urgency=medium
 .
   * Upload to buster.  Closes: #952655.
Checksums-Sha1:
 cedc9d0adb5a491a8350b7e10da3a71eed5a84aa 1684 
debian-ports-archive-keyring_2019.11.05~deb10u1.dsc
 b0acfeccb45fc88b0c8849594bcbbfe7d76fd59e 28836 
debian-ports-archive-keyring_2019.11.05~deb10u1.tar.xz
 e235308fab772bfacfa7e813ad916192e41aef80 11981 
debian-ports-archive-keyring_2019.11.05~deb10u1_source.buildinfo
Checksums-Sha256:
 26a3c85cd70917f3cb42f2ca6072f6d0ef55f22e51012d7fefe357d86464bc24 1684 
debian-ports-archive-keyring_2019.11.05~deb10u1.dsc
 8ecdcfe09c092000b8fd72f1c2eca9977758abfbc74dfd5648593bdf12428799 28836 
debian-ports-archive-keyring_2019.11.05~deb10u1.tar.xz
 d1431b9231a581b75d86d96c082ffb575a195c7474c4f67c1338d58580db6fda 11981 
debian-ports-archive-keyring_2019.11.05~deb10u1_source.buildinfo
Files:
 cce1808bcf1995b946e0d596c245108d 1684 misc optional 
debian-ports-archive-keyring_2019.11.05~deb10u1.dsc
 5fa603db427c6d3f2060f425331ac5d0 28836 misc optional 
debian-ports-archive-keyring_2019.11.05~deb10u1.tar.xz
 a440422ccac085f16f841835e66d3157 11981 misc optional 
debian-ports-archive-keyring_2019.11.05~deb10u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl8HcEgACgkQE4jA+Jno
M2s45A//bcIwbi3G7OmAemdGI2cxwnR8TV8Jf+jYpdH3FB00XZ3NDPi8W5QrfGsa
cRxld5D3N38V6pP569h0m6CLF8lYNpDQyVsKwVIwnhS7rNi2IgYR/PCWNzcPRpyR
SzWfnyFgkxEWi3hY+3Z/Esn41cEUAmP2ntlfXR3sXyJxikpfgtcGc1vlcf0VvXAD
sztBQeqTDCpRt9g8WT1WJDVbVVWmzuBC2OmQXJ4cA8mIk9GtQlfkmr658s4A+ZCb
/fu1xfwaCWqnuXFSYrLlbmOJgcS9X6veVtwWewAV5x2IYItb2irMWm1hhIVa/AQZ
I2PE0wDAtAaYqnuRnCuu7BPwfVzaUjkD+bHopAzhtj+bnG2aXIOJMRJL2bF1cdVh
8Z6Y9wlstaHunCJKmf48vO3gRVsq+S/3W9wn2I8dmld43F+Nrg7BVHJNSM2lUrEu

Bug#963275: rust-structopt-derive: FTBFS: build-dependency not installable: librust-proc-macro-error-1+default-dev

[Daniel Kahn Gillmor]

On Sun 2020-06-21 21:50:35 +0200, Lucas Nussbaum wrote:
> Source: rust-structopt-derive
> Version: 0.4.8-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200620 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

This was missing due to rust-proc-macro-error-attr being held in NEW,
which meant that rust-proc-macro-error could not be updated.

Now that r-p-m-e-attr is out of NEW, and rust-proc-macro-error 1.0.3 has
been uploaded to unstable, rust-structopt-derive should build fine.

 --dkg


signature.asc
Description: PGP signature

Bug#953621: Fix Python 3.8 file operations

[Eric Desrochers]

Dear maintainer,

May I suggest we (A) bump "sshuttle" to upstream release "1.0.2" and
take benefit of that to modernize the package to a let's say more modern dh
compat version, ... ?

Or at very least (B) cherry-pick the 3.8 fix[0] into Debian ?

This is highly impacting some Ubuntu users[1], and I'd like to see Debian
fixing it before I can proceed with Ubuntu.

Regards,
Eric

[0]-
https://github.com/sshuttle/sshuttle/commit/6c21addde97c4582b3dccb22bca64c33af3e5eff
[1] - https://launchpad.net/bugs/1873368

Processed: found 964471 in 1:7.0.0~alpha1-1, fixed 964471 in 1:7.0.0~rc1-4

[Debian Bug Tracking System]

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

> found 964471 1:7.0.0~alpha1-1
Bug #964471 {Done: Rene Engelhard } 
[libreoffice-l10n-de,libreoffice-l10n-ru] libreoffice-l10n-ru: error when 
configuring: cp: cannot create regular file 
'/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
Bug #964505 {Done: r...@rene-engelhard.de} 
[libreoffice-l10n-de,libreoffice-l10n-ru] Upgradin package from 1:6.4.5~rc1-2 
fails
There is no source info for the package 'libreoffice-l10n-de' at version 
'1:7.0.0~alpha1-1' with architecture ''
There is no source info for the package 'libreoffice-l10n-ru' at version 
'1:7.0.0~alpha1-1' with architecture ''
Unable to make a source version for version '1:7.0.0~alpha1-1'
Marked as found in versions 1:7.0.0~alpha1-1 and reopened.
Marked as found in versions 1:7.0.0~alpha1-1 and reopened.
> fixed 964471 1:7.0.0~rc1-4
Bug #964471 [libreoffice-l10n-de,libreoffice-l10n-ru] libreoffice-l10n-ru: 
error when configuring: cp: cannot create regular file 
'/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
Bug #964505 [libreoffice-l10n-de,libreoffice-l10n-ru] Upgradin package from 
1:6.4.5~rc1-2 fails
Marked as fixed in versions libreoffice/1:7.0.0~rc1-4.
Marked as fixed in versions libreoffice/1:7.0.0~rc1-4.
> thanks
Stopping processing here.

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

Processed: reassign 964471 to libreoffice-l10n-de,libreoffice-l10n-ru ..., forcibly merging 964471 964505

[Debian Bug Tracking System]

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

> reassign 964471 libreoffice-l10n-de,libreoffice-l10n-ru
Bug #964471 {Done: Rene Engelhard } [libreoffice-l10n-ru] 
libreoffice-l10n-ru: error when configuring: cp: cannot create regular file 
'/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
Bug reassigned from package 'libreoffice-l10n-ru' to 
'libreoffice-l10n-de,libreoffice-l10n-ru'.
No longer marked as found in versions libreoffice/1:7.0.0~rc1-1 and 
libreoffice/1:7.0.0~rc1-3.
No longer marked as fixed in versions libreoffice/1:7.0.0~rc1-4.
> reassign 964505 libreoffice-l10n-de,libreoffice-l10n-ru
Bug #964505 {Done: r...@rene-engelhard.de} [libreoffice-l10n-de] Upgradin 
package from 1:6.4.5~rc1-2 fails
Bug reassigned from package 'libreoffice-l10n-de' to 
'libreoffice-l10n-de,libreoffice-l10n-ru'.
No longer marked as found in versions libreoffice/1:7.0.0~rc1-3.
No longer marked as fixed in versions libreoffice/1:7.0.0~rc1-4.
> forcemerge 964471 964505
Bug #964471 {Done: Rene Engelhard } 
[libreoffice-l10n-de,libreoffice-l10n-ru] libreoffice-l10n-ru: error when 
configuring: cp: cannot create regular file 
'/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
Bug #964505 {Done: r...@rene-engelhard.de} 
[libreoffice-l10n-de,libreoffice-l10n-ru] Upgradin package from 1:6.4.5~rc1-2 
fails
Merged 964471 964505
> thanks
Stopping processing here.

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

Bug#964742: src:binutils-mingw-w64: FTBFS on s390x: FAIL: objcopy executable (pr25662)

[Stephen Kitt]

Package: src:binutils-mingw-w64
Version: 8.10
Severity: serious
Justification: ftbfs

Dear Maintainer,

binutils-mingw-w64 FTBFS on s390x and other big-endian architectures;
the test suite fails with

FAIL: objcopy executable (pr25662)

Regards,

The Maintainer

-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable'), 
(100, 'unstable-debug'), (100, 'testing-debug'), (100, 'unstable'), (100, 
'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-9-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#964318: gosa login broken with PHP 7.4

[Wolfgang Schweer]

On Mon, Jul 06, 2020 at 12:05:44PM +0200, Wolfgang Schweer wrote:
> In both encrypt and decrypt cases, the chosen cipher method seems to 
> return 0.

This is the case because the chosen method (aes-256-ecb) doesn't use an 
initialization vector ($iv) at all, causing its length ($ivlen) to be 0, 
see e.g. https://usr.ed48.com/php/ssl/?xf=7

So the encrypt/decrypt implementation seems to have been sort of wrong 
before (and only now with PHP 7.4 an error is thrown).

Please check and test the attached changes to 
/usr/share/gosa/include/functions.inc and 
/usr/sbin/gosa-encrypt-passwords; works for me, but then my skills are 
low level and this is a quite sensitive issue.

Wolfgang
diff -u a/functions.inc b/functions.inc
--- a/functions.inc	2020-04-20 07:32:48.0 +0200
+++ b/functions.inc	2020-07-09 21:09:16.311305601 +0200
@@ -3308,11 +3308,10 @@
 }
 
 
-function cred_encrypt($input, $password, $cipher = "aes-256-ecb") {
+function cred_encrypt($input, $password) {
+  $cipher = "aes-256-ecb";
   if (in_array($cipher, openssl_get_cipher_methods())) {
-$ivlen = openssl_cipher_iv_length($cipher);
-$iv = openssl_random_pseudo_bytes($ivlen);
-return bin2hex(openssl_encrypt($input, $cipher, $password, OPENSSL_RAW_DATA, $iv));
+return bin2hex(openssl_encrypt($input, $cipher, $password));
   }
 
   return null;
@@ -3320,9 +3319,7 @@
 
 function cred_decrypt($input, $password, $cipher = "aes-256-ecb") {
   if (in_array($cipher, openssl_get_cipher_methods())) {
-$ivlen = openssl_cipher_iv_length($cipher);
-$iv = openssl_random_pseudo_bytes($ivlen);
-return rtrim(openssl_decrypt(pack("H*", $input), $cipher, $password, OPENSSL_RAW_DATA, $iv ), "\0\3\4\n");
+return rtrim(openssl_decrypt(pack("H*", $input), $cipher, $password, $options=0, ), "\0\3\4\n");
   }
 
   return null;
diff -u a/gosa-encrypt-passwords b/gosa-encrypt-passwords
--- a/gosa-encrypt-passwords	2020-04-20 07:32:00.0 +0200
+++ b/gosa-encrypt-passwords	2020-07-09 21:07:27.143219922 +0200
@@ -1,11 +1,10 @@
 #!/usr/bin/php
 

signature.asc
Description: PGP signature

Bug#958578: marked as done (wav2cdr is broken on 64bit architectures other than amd64 and alpha)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 19:32:15 +
with message-id 
and subject line Bug#956927: fixed in wav2cdr 2.3.4-2+deb10u1
has caused the Debian Bug report #956927,
regarding wav2cdr is broken on 64bit architectures other than amd64 and alpha
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.)


-- 
956927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wav2cdr
Version: 2.3.4-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

With a recent upload of wav2cdr you added an autopkgtest, great. However
it fails on arm64. I copied some of the output at the bottom of this report.

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/arm64/w/wav2cdr/4822988/log.gz

autopkgtest [19:42:21]: test command3: wav2cdr debian/tests/silence.wav
$AUTOPKGTEST_TMP/silence.mp3
autopkgtest [19:42:21]: test command3: [---
wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed.
bash: line 1:   837 Aborted bash -ec 'wav2cdr
debian/tests/silence.wav $AUTOPKGTEST_TMP/silence.mp3' 2> >(tee -a
/tmp/autopkgtest-lxc.zdo4nd5f/downtmp/command3-stderr >&2) > >(tee -a
/tmp/autopkgtest-lxc.zdo4nd5f/downtmp/command3-stdout)
autopkgtest [19:42:21]: test command3: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: wav2cdr
Source-Version: 2.3.4-2+deb10u1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated wav2cdr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 05 Jul 2020 23:09:10 +0300
Source: wav2cdr
Architecture: source
Version: 2.3.4-2+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 956927
Changes:
 wav2cdr (2.3.4-2+deb10u1) buster; urgency=medium
 .
   * QA upload.
   * Use C99 fixed-size integer types to fix runtime assertion on
 64bit architectures other than amd64 and alpha. (Closes: #956927)
   * Stop linking to the dead Homepage.
Checksums-Sha1:
 7af5ece544e8f7c9b55823ab52037b5cbf50b58a 1716 wav2cdr_2.3.4-2+deb10u1.dsc
 79596e42f7831c6408db75c6ac92b90765b5442c 10608 
wav2cdr_2.3.4-2+deb10u1.debian.tar.xz
Checksums-Sha256:
 a1386c934afd54947296d25d6a10d9829dfb86b934e524d19d4b472e2ef97446 1716 
wav2cdr_2.3.4-2+deb10u1.dsc
 dcfd6fd4b270e15a8df49aa83b8623b02668b9b602a9da67f4a6d88e36e06e8f 10608 
wav2cdr_2.3.4-2+deb10u1.debian.tar.xz
Files:
 3ad4b96aab5b0b9578f5db5bdbf3563d 1716 sound optional 
wav2cdr_2.3.4-2+deb10u1.dsc
 374a0c4fa5973968ddf84c3edc7b1ce1 10608 sound optional 
wav2cdr_2.3.4-2+deb10u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl8CNbUACgkQiNJCh6LY
mLFetg/8CWaBqU6z+TcEykJbr2jgyRr5MvNM9Ejw7Jdcri4jDoGpN4XNeCy8bnmG
DOUZ+MWgpg48efDHFuDWo1n57HlACFgfl3gmdhAogGt4Ez8HrxcMFswQVKxwmvET
uoLbyhFZQcZrwhr67t283lNJWggZMDbQEIufY2ofzB1a4glcxpvec1ogx0BtyZ9A
U7hoPXUdOPxNKV3pOaohLOgC866txmljXmWIaTGkdr/Is1j+Q4V9OBIbqPdtLH32
4ZY7OKhx+CocM1oQ9yMOVHqjLrb9LjetDxqQW7/D4bQnNpKj2m1vflGAook9Y/Ky
a9ZXy/bUPF+EnG/85MGNtefkTxbiE1kxYglQyM4F4XvqYElMfOjTBFT5zTMgu3yc
EH4D9qwSxkSzbKhNUv+dgGBTvzSZHV7jnnrb2rJaIVbA4ey384VA/o/ENh69Syag
vqG/sr75VFyzpQJehJXrT1liTtPLHh8VgmQ3Tyi3nOz4MGJvja1RYx7cUOvOlzjf
BAlxcix4W0UkM98AWwaz0v4gzYDZT3VbAw1zHOuf3wPlpyoGeX9r84v4BP4Or9nQ
scEcEF+mAcKlwFACw8WotYcTx6FjqzQr5eJGBKbDygQFypnR1wb0eUspFM/l68Jv
Vj/4pN6CTYKsemgE5dtPiyjrLzOUkg95O4WYCLIdHBmaJuoZvuI=
=MJWC
-END PGP SIGNATURE End Message ---

Bug#961377: marked as done (raspi3-firmware: recent stable update causes non-booting systems)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 19:32:14 +
with message-id 
and subject line Bug#961377: fixed in raspi3-firmware 1.20190215-1+deb10u4
has caused the Debian Bug report #961377,
regarding raspi3-firmware: recent stable update causes non-booting systems
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.)


-- 
961377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: raspi3-firmware
Version: 1.20190215-1+deb10u3
Severity: critical
Tags: patch buster
Justification: breaks the whole system

/etc/kernel/postinst.d/z50-raspi3-firmware in +deb10u3 contains:

   67   for dtn in ${dtb_path}/bcm*.dtb; do
   68 [ -e "${dtb}" ] && cp "${dtb}" /boot/firmware/
   69   done

It’s hard to see, a typo, and not in unstable (where commit
165f43a6ca14d240f199e8ab8924e503ca5f427d got it right), but
commit fc3df0e8c64c2c62a54e0efcd226e36f28ccd3a4 uses “dtn”,
not “dtb”, as for variable, but refers to “dtb”.

This causes creation of systems that cannot boot (user error
description “[…] but when I install the SD card on the Pi and
boot it, I end up with this multicolored starting screen. It
does not go any further.”) which is really tricky to debug.

The following patch causes the four files…
-rwxr-xr-x 1 root root13593 May 23 20:53 bcm2837-rpi-3-a-plus.dtb
-rwxr-xr-x 1 root root13637 May 23 20:53 bcm2837-rpi-3-b-plus.dtb
-rwxr-xr-x 1 root root13445 May 23 20:53 bcm2837-rpi-3-b.dtb
-rwxr-xr-x 1 root root13433 May 23 20:53 bcm2837-rpi-cm3-io3.dtb
… to show up in /boot/firmware/ and should (I cannot boot-test
it currently) therefore fix this problem:


diff --git a/debian/kernel/postinst.d/z50-raspi3-firmware 
b/debian/kernel/postinst.d/z50-raspi3-firmware
index 5d3dd8e..04ebb1d 100755
--- a/debian/kernel/postinst.d/z50-raspi3-firmware
+++ b/debian/kernel/postinst.d/z50-raspi3-firmware
@@ -64,7 +64,7 @@ else
 fi
 
 if [ "$KERNEL" = "auto" ]; then
-  for dtn in ${dtb_path}/bcm*.dtb; do
+  for dtb in ${dtb_path}/bcm*.dtb; do
 [ -e "${dtb}" ] && cp "${dtb}" /boot/firmware/
   done
 


-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 5.5.0-1-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages raspi3-firmware depends on:
ii  dosfstools  4.1-2

raspi3-firmware recommends no packages.

raspi3-firmware suggests no packages.

-- Configuration Files:
/etc/default/raspi3-firmware changed:
CMA=128M


-- no debconf information
--- End Message ---
--- Begin Message ---
Source: raspi3-firmware
Source-Version: 1.20190215-1+deb10u4
Done: Gunnar Wolf 

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

Debian distribution maintenance software
pp.
Gunnar Wolf  (supplier of updated raspi3-firmware package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 May 2020 15:56:47 -0500
Source: raspi3-firmware
Architecture: source
Version: 1.20190215-1+deb10u4
Distribution: buster
Urgency: medium
Maintainer: pkg-raspi 
Changed-By: Gunnar Wolf 
Closes: 961377
Changes:
 raspi3-firmware (1.20190215-1+deb10u4) buster; urgency=medium
 .
   * Fixes ugly typo that _still_ caused unbootable systems :-( Thanks to
 Thorsten Glaser for a sharp set of eyes! (Closes: #961377)
   * Updated Vcs-Git, Vcs-Browser
Checksums-Sha1:
 44d39ffd790426983810d06601053f131bd6014e 1573 
raspi3-firmware_1.20190215-1+deb10u4.dsc
 de60241e2024a00b9e26f6dc659560e4e7e3ee28 23468 
raspi3-firmware_1.20190215-1+deb10u4.debian.tar.xz
 d8ab017154290f4c9944796298790197510bf1bc 6537 
raspi3-firmware_1.20190215-1+deb10u4_source.buildinfo
Checksums-Sha256:
 c5c7b8fdfb5c1ba75a2bcad3413b2c2ce7dbe57fba923744f6fa33442f03bd9f 1573 
raspi3-firmware_1.20190215-1+deb10u4.dsc
 

Bug#941926: marked as done (FTBFS: test failure in #238 EmbperlObject/epobase.htm)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 19:32:08 +
with message-id 
and subject line Bug#941926: fixed in libembperl-perl 2.5.0-12+deb10u1
has caused the Debian Bug report #941926,
regarding FTBFS: test failure in #238 EmbperlObject/epobase.htm
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.)


-- 
941926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libembperl-perl
Version: 2.5.0-12
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
Control: block 935737 with -1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The binNMUs for the perl 5.30 transition have shown that libembperl-perl
fails to build. The tests abort (both in testing with 5.28 and in
unstable with 5.30) with:

#238 EmbperlObject/epobase.htm... 
Error in Line 6
Is: >You don't have permission to access this resource.<
Should: >.*?You don't have permission to access 
/embperl/EmbperlObject/epobase.htm<
Input:  test/html/EmbperlObject/epobase.htm
Output: test/tmp/out.htm
Compared to:test/cmp/epobase.htm
Log:test/tmp/test.log
Testparameter:
  cgi = 0
  errors = 1
  offline = 0

 ERRORS detected! NOT all tests have been passed successfully


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl2bZq1fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZJ0BAAlB/vEqG1lAWJIPzgdhn3jlCxjKuXDgftihwgbgTpA0ED6PsZ0/BEk98u
cXOomE2L2TeyNpedspgz/wccPvDu2731Opw4XnA1SPcBHy1GDLtkPiV6jt4vyTA0
c8RcodPQo25ifvlLxetdrv5Cu4w9t0/Q/QRPHojbaIAIpu2GRMMi6MSHnh1AmqrP
BnAbffijjGb1x7gRQPupszRdIZPDzaJ5TdorIvkmRGyCukRxE2CoNPJcGogJvQ0q
4CmILlBMgJvzFWlGWXU7xGchiu3roK2jMgKGr09gtzkhhoAHqCVB59eLqRD+vE4x
mIZZ/M65zuiO/mZzUKeTWany4gy0PMHybsozw7uZaMvXDy7CQ4Nw0ihelBir7Nos
KcUD2Foql2eKQ5j+ukQtKMB0IEI/HVjlGIk4yIM5bPCCCGjnbkJBeGQzU3sF1hTP
COeQTZdVlTXRdxD+3QaZNAm2Lwh8Uclqy2p9RntOYeTxsST0+S5Iojm7+rzcwNkV
+y8KqhIp7OatQ4Ez74P3op7QzHoBTQajx94h4DJIO836T7cQQ4J/UbVJ0Tubn8Ha
rOBh7MiY7vNpVzbcrpN8TZhvpWO26Bby7PoGFIsp2n9ETywAzsHmJKvXihC4Idxm
EFWinLz30w0F/2Z4raF9eSEm1u392HyFCTeZtZ6AuZJU+qyckZo=
=V8Kh
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libembperl-perl
Source-Version: 2.5.0-12+deb10u1
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated libembperl-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Jul 2020 19:58:46 +0300
Source: libembperl-perl
Architecture: source
Version: 2.5.0-12+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Adrian Bunk 
Closes: 941926
Changes:
 libembperl-perl (2.5.0-12+deb10u1) buster; urgency=medium
 .
   * Non-maintainer upload.
   * Update debian/patches/apache2.4-compat.patch to work with Apache
 2.4.40+ error pages. (Closes: #941926)
Checksums-Sha1:
 670f18ab06dc1847d472a0ab883f81bf7954d085 2309 
libembperl-perl_2.5.0-12+deb10u1.dsc
 254080a8f3cbaf58c3998517e8f3d0d84813aa7f 30472 
libembperl-perl_2.5.0-12+deb10u1.debian.tar.xz
Checksums-Sha256:
 f3ffd24dc49bdf6a55d9d132b1d720b54cb15a9c1742a06961dbf65235af2c27 2309 
libembperl-perl_2.5.0-12+deb10u1.dsc
 4006b8beea77b3e0c27733242ee5b91bd5d636fbbb2e2f12bed3ecfd7d6224a5 30472 
libembperl-perl_2.5.0-12+deb10u1.debian.tar.xz
Files:
 b6369de510ca525a5bf69f7f9fc62edb 2309 perl optional 
libembperl-perl_2.5.0-12+deb10u1.dsc
 7bfd4d90a1cff919966d0ec9990acc1e 30472 perl optional 
libembperl-perl_2.5.0-12+deb10u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl8DZmMACgkQiNJCh6LY
mLGKuw/+NXgTJAYf61liHCwCHBBovB/qBwBKQBABob1Bsl1X0Ll+jGccyQGAdVSO
bm7f5H8GStLQDzqp/1Ts8MMhXO/pU+/E7OpzGWrgqoq0USGcc9eKXgkIYK/TYo38
F5PJ8CCLqJEjYwKgMjT6QSW7uLH8xbU2SssuSeujwGWhdC+hCfTMORyIVekGhK4j

Bug#956927: marked as done (wav2cdr is broken on 64bit architectures other than amd64 and alpha)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 19:32:15 +
with message-id 
and subject line Bug#956927: fixed in wav2cdr 2.3.4-2+deb10u1
has caused the Debian Bug report #956927,
regarding wav2cdr is broken on 64bit architectures other than amd64 and alpha
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.)


-- 
956927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wav2cdr
Version: 2.3.4-3
Severity: important

The new and first CI test[1] for wav2cdr fails in arm64[2]. Consequently,
the revision 2.3.4-3 will not migrate to testing.

[1] 
https://salsa.debian.org/debian/wav2cdr/-/blob/debian/master/debian/tests/control
[2] 
https://ci.debian.net/data/autopkgtest/testing/arm64/w/wav2cdr/4822988/log.gz

The significative output is:

autopkgtest [19:42:07]: test command1: wav2cdr -V | grep Version
autopkgtest [19:42:07]: test command1: [---
wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed.
autopkgtest [19:42:07]: test command1: ---]
autopkgtest [19:42:07]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL non-zero exit status 1
autopkgtest [19:42:07]: test command1:  - - - - - - - - - - stderr - - - - - - 
- - - -
wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed.
[...]
autopkgtest [19:42:16]: test command2: wav2cdr --help | grep describes
autopkgtest [19:42:16]: test command2: [---
wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed.
autopkgtest [19:42:16]: test command2: ---]
autopkgtest [19:42:16]: test command2:  - - - - - - - - - - results - - - - - - 
- - - -
command2 FAIL non-zero exit status 1
autopkgtest [19:42:17]: test command2:  - - - - - - - - - - stderr - - - - - - 
- - - -
wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed.
[...]
autopkgtest [19:42:21]: test command3: wav2cdr debian/tests/silence.wav 
$AUTOPKGTEST_TMP/silence.mp3
autopkgtest [19:42:21]: test command3: [---
wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed.
bash: line 1:   837 Aborted bash -ec 'wav2cdr 
debian/tests/silence.wav $AUTOPKGTEST_TMP/silence.mp3' 2> >(tee -a 
/tmp/autopkgtest-lxc.zdo4nd5f/downtmp/command3-stderr >&2) > >(tee -a 
/tmp/autopkgtest-lxc.zdo4nd5f/downtmp/command3-stdout)
autopkgtest [19:42:21]: test command3: ---]
autopkgtest [19:42:21]: test command3:  - - - - - - - - - - results - - - - - - 
- - - -
command3 FAIL non-zero exit status 134
autopkgtest [19:42:22]: test command3:  - - - - - - - - - - stderr - - - - - - 
- - - -
wav2cdr: wav2cdr.c:281: main: Assertion `sizeof(UINT32) == 4' failed.
autopkgtest [19:42:22]:  summary
command1 FAIL non-zero exit status 1
command2 FAIL non-zero exit status 1
command3 FAIL non-zero exit status 134


Eriberto
--- End Message ---
--- Begin Message ---
Source: wav2cdr
Source-Version: 2.3.4-2+deb10u1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated wav2cdr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 05 Jul 2020 23:09:10 +0300
Source: wav2cdr
Architecture: source
Version: 2.3.4-2+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 956927
Changes:
 wav2cdr (2.3.4-2+deb10u1) buster; urgency=medium
 .
   * QA upload.
   * Use C99 fixed-size integer types to fix runtime assertion on
 64bit architectures other than amd64 and alpha. (Closes: #956927)
   * Stop linking to the dead Homepage.
Checksums-Sha1:
 7af5ece544e8f7c9b55823ab52037b5cbf50b58a 1716 wav2cdr_2.3.4-2+deb10u1.dsc
 79596e42f7831c6408db75c6ac92b90765b5442c 10608 
wav2cdr_2.3.4-2+deb10u1.debian.tar.xz
Checksums-Sha256:
 

Bug#963761: [Pkg-javascript-devel] Bug#963761: node-node-sass: missing versioned dependency relation?: Sass could not find a binding for your current environment

[Jonas Smedegaard]

Quoting mer...@debian.org (2020-07-09 16:42:32)
> On Fri, 26 Jun 2020 18:27:30 +0200 Paul Gevers  wrote:
> > + grunt sass nodeunit
> > Loading "gruntfile.js" tasks...ERROR
> > >> Error: Missing binding
> >
> /usr/lib/x86_64-linux-gnu/nodejs/node-sass/vendor/linux-x64-72/binding.node
> > >> Node Sass could not find a binding for your current environment:
> > Linux 64-bit with Node.js 12.x
> > >>
> > >> Found bindings for the following environments:
> > >>   - Linux 64-bit with Node.js 10.x
> 
> It seems as if node-node-sass was built with libnode < 72, and is now 
> being executed on machine also having libnode72. While in principle 
> such situations are possible, more than one libnodeX package are very 
> unlikely to be present. It would probably be worth stripping the 
> /linux-x64-72/ part from 
> /usr/lib/x86_64-linux-gnu/nodejs/node-sass/vendor/linux-x64-72/binding.node 
> and disabling the resolving mechanism altogether.

Please, Andrius, think twice before repeating the discussion already had 
about node-iconv and node-expat.

I urge you to read through that previous thread (if you haven't 
already), and I recommend that you consider if it is really worth it to 
look at node-node-sass differently from those other packages.

If you find that it is sensible to follow the approach already taken by 
those other packages, but are uncertain how concretely to implement it, 
then I can suggest to look at the most recent git commits for the 
packaging of node-expat: I tried to isolate and minimize the changes 
made for each commit to hopefully be easy to follow.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#950300: marked as done (mod-gnutls: apache CVE-2019-10092 fix causes FTBFS)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 19:32:09 +
with message-id 
and subject line Bug#950300: fixed in mod-gnutls 0.9.0-1.1~deb10u1
has caused the Debian Bug report #950300,
regarding mod-gnutls: apache CVE-2019-10092 fix causes FTBFS
to be marked as done.

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

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


-- 
950300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mod-gnutls
Version: 0.8.2-3
Severity: serious
Tags: ftbfs

mod-gnutls appears to rely on the exact wording of apache
error messages, and these changed with CVE-2019-10092.

https://buildd.debian.org/status/package.php?p=mod-gnutls=stretch
https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/mod-gnutls.html

...
FAIL: test-18_client_verification_wrong_cert


TESTING: 18_client_verification_wrong_cert
Server version: Apache/2.4.38 (Debian)
Server built:   2019-10-15T19:53:42
Server's Module Magic Number: 20120211:84
Server loaded:  APR 1.6.5, APR-UTIL 1.6.1
Compiled using: APR 1.6.5, APR-UTIL 1.6.1
Architecture:   64-bit
Server MPM: worker
  threaded: yes (fixed thread count)
forked: yes (variable process count)
Server compiled with
 -D APR_HAS_SENDFILE
 -D APR_HAS_MMAP
 -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
 -D APR_USE_SYSVSEM_SERIALIZE
 -D APR_USE_PTHREAD_SERIALIZE
 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 -D APR_HAS_OTHER_CHILD
 -D AP_HAVE_RELIABLE_PIPED_LOGS
 -D DYNAMIC_MODULE_LIMIT=256
 -D HTTPD_ROOT="/etc/apache2"
 -D SUEXEC_BIN="/usr/lib/apache2/suexec"
 -D DEFAULT_PIDLOG="/var/run/apache2.pid"
 -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
 -D DEFAULT_ERRORLOG="logs/error_log"
 -D AP_TYPES_CONFIG_FILE="mime.types"
 -D SERVER_CONFIG_FILE="apache2.conf"
[Mon Jan 27 07:56:11.674982 2020] [gnutls:debug] [pid 45519:tid 
139910356628608] gnutls_cache.c(354): mgs_cache_inst_config: Socache 
'shmcb:cache/gnutls_cache_18_client_verification_wrong_cert(65536)' created.
AH00557: apache2: apr_sockaddr_info_get() failed for profitbricks-build11-amd64
AH00558: apache2: Could not reliably determine the server's fully qualified 
domain name, using 127.0.0.1. Set the 'ServerName' directive globally to 
suppress this message
flock: getting lock took 1.910177 seconds
flock: executing /usr/sbin/apache2
Processed 1 CA certificate(s).
Processed 1 client X.509 certificates...
Resolving 'localhost:9932'...
Connecting to '127.0.0.1:9932'...
- Successfully sent 1 certificate(s) to server.
- Server has requested a certificate.
- Certificate type: X.509
- Got a certificate list of 1 certificates.
- Certificate[0] info:
 - subject `CN=localhost', issuer `CN=Testing Authority', serial 0x22fff0d9, 
RSA key 3072 bits, signed using RSA-SHA256, activated `2020-01-27 19:56:05 
UTC', expires `2021-01-26 19:56:05 UTC', 
pin-sha256="ShqMB70z9iMRONejdL+6v98HfExpZp/aWi6nXzD6vJE="
Public Key ID:
sha1:7bb678f9fe68cd7ed0fd1df39e9aebad4eee2b94

sha256:4a1a8c07bd33f6231138d7a374bfbabfdf077c4c69669fda5a2ea75f30fabc91
Public Key PIN:
pin-sha256:ShqMB70z9iMRONejdL+6v98HfExpZp/aWi6nXzD6vJE=

- Status: The certificate is trusted. 
- Description: (TLS1.3)-(ECDHE-SECP256R1)-(RSA-PSS-RSAE-SHA256)-(AES-256-GCM)
- Options:
- Handshake was completed

- Simple Client Mode:

HTTP/1.1 403 Forbidden
Date: Mon, 27 Jan 2020 19:56:11 GMT
Server: Apache/2.4.38 (Debian) mod_gnutls/0.9.0 GnuTLS/3.6.7
Content-Length: 199
Connection: close
Content-Type: text/html; charset=iso-8859-1



403 Forbidden

Forbidden
You don't have permission to access this resource.

- Peer has closed the GnuTLS connection
  PID TTY  TIME CMD
45530 ?00:00:00 sleep
--- /build/mod-gnutls-0.9.0/test/tests/18_client_verification_wrong_cert/output 
2017-02-28 07:05:55.0 -1200
+++ /dev/fd/63  2020-01-27 07:56:11.809997988 -1200
@@ -1,7 +1,7 @@
+
+403 Forbidden
 
 Forbidden
-You don't have permission to access /test.txt
-on this server.
-
+You don't have permission to access this resource.
 
 - Peer has closed the GnuTLS connection
FAILURE: 18_client_verification_wrong_cert
[Mon Jan 27 07:56:11.869868 2020] [gnutls:debug] [pid 45630:tid 
139891390706816] gnutls_cache.c(354): mgs_cache_inst_config: Socache 
'shmcb:cache/gnutls_cache_18_client_verification_wrong_cert(65536)' created.
AH00557: apache2: apr_sockaddr_info_get() failed for profitbricks-build11-amd64
AH00558: apache2: Could not reliably determine the server's fully qualified 
domain name, using 127.0.0.1. Set the 'ServerName' directive 

Bug#962517: marked as done (CVE-2020-10759)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 19:17:31 +
with message-id 
and subject line Bug#962517: fixed in fwupd 1.2.13-1
has caused the Debian Bug report #962517,
regarding CVE-2020-10759
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.)


-- 
962517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fwupd
Severity: grave
Tags: security

https://github.com/justinsteven/advisories/blob/master/2020_fwupd_dangling_s3_bucket_and_CVE-2020-10759_signature_verification_bypass.md

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: fwupd
Source-Version: 1.2.13-1
Done: Mario Limonciello 

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

Debian distribution maintenance software
pp.
Mario Limonciello  (supplier of updated fwupd 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Jul 2020 23:13:40 -0500
Source: fwupd
Architecture: source
Version: 1.2.13-1
Distribution: stable
Urgency: medium
Maintainer: Debian EFI 
Changed-By: Mario Limonciello 
Closes: 946623 961490 962517
Changes:
 fwupd (1.2.13-1) stable; urgency=medium
 .
   * Update to 1.2.13 stable release.
 - Fixes issues on stable release (Closes: #961490)
 - Fixes vendor id hard requirement (Closes: #946623)
 - Fixes CVE-2020-10759 (Closes: #962517)
   * Add patch to revert new libxmlb requirement to allow working with libxmlb
   available in Buster.
   * debian/* changes backported from testing:
 - Refresh symbols
 - Install fwupdoffline binary
 - Install fwupd shutdown systemd unit
 - Refresh dependencies for modem manager plugin
 - Update copyright for new new contributors
 - Update watch file for correct upstream URL.
Checksums-Sha1:
 71b3188ec7c73c6efcd8caa583f15c54a6481bde 3685 fwupd_1.2.13-1.dsc
 1626d8b5793a28380345cb1535d5873d65fc59f4 1946644 fwupd_1.2.13.orig.tar.gz
 934fd18367b04f63c9286e72458972156afedfc4 19164 fwupd_1.2.13-1.debian.tar.xz
 7b2ede1e1ee2a3e7c6e34fb3befd234e89c6dcd1 14419 fwupd_1.2.13-1_source.buildinfo
Checksums-Sha256:
 0eb5fe27d62067cb617f99e4ec15987eb95f3a7169be67d3c9b7ed5c31cd3a81 3685 
fwupd_1.2.13-1.dsc
 38c8803640c5a8d194706373e7782c78c11d765a873123e630b96519400bfbf9 1946644 
fwupd_1.2.13.orig.tar.gz
 ef7000951c6256f57c69072a206b6fddd16c8345c649d6f025e235434e85c683 19164 
fwupd_1.2.13-1.debian.tar.xz
 01007c81db56a2d57dc436ac0ba8b73e69696f3c9097174ab2c6a4fd838f4640 14419 
fwupd_1.2.13-1_source.buildinfo
Files:
 f0c7b7d07afddd9d29b241f649fa4aec 3685 admin optional fwupd_1.2.13-1.dsc
 e205c79b43f343c56b340593f4d00c9f 1946644 admin optional 
fwupd_1.2.13.orig.tar.gz
 7f1f680ccc01a2ed005472c5e4a0963e 19164 admin optional 
fwupd_1.2.13-1.debian.tar.xz
 9d9487dc547346af3164babdae903248 14419 admin optional 
fwupd_1.2.13-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEzrtSMB1hfpEDkP4WWHl5VzRCaE4FAl8HA1MRHDkzc2FtQGRl
Ymlhbi5vcmcACgkQWHl5VzRCaE5H2RAAhWikrZZOQ8o56eK0gvseRFnBKmaHmQdr
jKFfkXiJIhAcXFNKE64sipuXwQJFMzvhnELC54O5UQdTDzhBLXzgOkEH9qos+soP
hw/BYpl9Q5PX25zRSH5SPRRx1EmF6Mb97KW5z/VZnIa8fcbvV9wn+aZ46u4kmrbR
uRD8XNY2/RwYatCD0+dWr/pOoVrtgvu3mue5SIbuKc+TWdwOZC5EYTZHAVKyCHze
nY0B8Zz/FHdcrpjjjeQO7TVrJWnwGenFTH2arpAFS+ohvXiPseCb7p1ZZOm6qHXJ
g88z/WRfbYSVl/HGIJIiAHF+Jp0lQ1y+ZTMQY5NYB5H+713dY26O2B4twnt1gNzO
SY0vWC6rJcSGthB6dqhkVW5J+e0GsJ6FJukuG8X04AXrWNkrkOmQ5sy+tKLjaQ0w
qokOb6J2hb+2/hnGnyYKfRGfWEzGJLi2o5WUoOAngxrwtT6TXwXxVRCq+j2UXhSo
mexxoeELBkn0fZKnlHCdWL0HGPIB2GeadNip3I8ayFl8by9/xW/tfhx7MympC3e+
GjY79Lo01uwj4YNk8lEubSS2V0EqudIXG6YKyRZkhIX/mXd0ZiqQbN1V4YvHr4EK
UmbAdjDHauwb9iyLwRutAwmjBYw7lvXpmZLUWUcQBJj18IWJU07PeoA4GMN6FP4e
EAFwyvnUgB0=
=xHAW
-END PGP SIGNATURE End Message ---

Bug#961490: marked as done (fwupd: version in stable too old, no updates possible)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 19:17:31 +
with message-id 
and subject line Bug#961490: fixed in fwupd 1.2.13-1
has caused the Debian Bug report #961490,
regarding fwupd: version in stable too old, no updates possible
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.)


-- 
961490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fwupd
Version: 1.2.5-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The version 1.2.5 of fwupd currently in Debian stable is useless and not able
to perform any firmware updates.
Whem trying to update via command line:

> fwupdmgr refresh && fwupdmgr get-updates

I get the following output:

 Metadaten werden abgerufen https://cdn.fwupd.org/downloads/firmware.xml.gz
 Herunterladen …  [***]
 Signatur wird abgerufen https://cdn.fwupd.org/downloads/firmware.xml.gz.asc

 Not compatible with org.freedesktop.fwupd version 1.2.5, requires >= 1.2.7

The "refresh" part still works, but the new firmware info requires a newer
version of fwupd than available in stable, so the "get-update" part fails.

I'm not sure how to best handle this situation. It's very unfortunate that
fwupd obviously breaks compatibility with older clients here...
Maybe a new version in backports would be possible?

Regards,
Steffen



-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages fwupd depends on:
ii  libarchive13   3.3.3-4+deb10u1
ii  libc6  2.28-10
ii  libefiboot137-2
ii  libefivar1 37-2
ii  libelf10.176-1.1
ii  libfwupd2  1.2.5-2
ii  libgcab-1.0-0  1.2-3~deb10u1
ii  libglib2.0-0   2.58.3-2+deb10u2
ii  libgnutls303.6.7-4+deb10u3
ii  libgpg-error0  1.35-1
ii  libgpgme11 1.12.0-6
ii  libgudev-1.0-0 232-2
ii  libgusb2   0.3.0-1
ii  libjson-glib-1.0-0 1.4.4-2
ii  libpolkit-gobject-1-0  0.105-25
ii  libsmbios-c2   2.4.1-1
ii  libsoup2.4-1   2.64.2-2
ii  libsqlite3-0   3.27.2-3
ii  libxmlb1   0.1.6-2
ii  shared-mime-info   1.10-1

Versions of packages fwupd recommends:
ii  bolt   0.7-2
ii  fwupd-amd64-signed [fwupd-signed]  1.2.5+2
ii  python33.7.3-1
ii  tpm2-abrmd 2.1.0-1
ii  tpm2-tools 3.1.3-2

fwupd suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fwupd
Source-Version: 1.2.13-1
Done: Mario Limonciello 

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

Debian distribution maintenance software
pp.
Mario Limonciello  (supplier of updated fwupd 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Jul 2020 23:13:40 -0500
Source: fwupd
Architecture: source
Version: 1.2.13-1
Distribution: stable
Urgency: medium
Maintainer: Debian EFI 
Changed-By: Mario Limonciello 
Closes: 946623 961490 962517
Changes:
 fwupd (1.2.13-1) stable; urgency=medium
 .
   * Update to 1.2.13 stable release.
 - Fixes issues on stable release (Closes: #961490)
 - Fixes vendor id hard requirement (Closes: #946623)
 - Fixes CVE-2020-10759 (Closes: #962517)
   * Add patch to revert new libxmlb requirement to allow working with libxmlb
   available in Buster.
   * debian/* changes backported from testing:
 - Refresh symbols
 - Install fwupdoffline binary
 

Bug#946623: marked as done (fwupd: vendor-id hard requirement coming in 6 months)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 19:17:31 +
with message-id 
and subject line Bug#946623: fixed in fwupd 1.2.13-1
has caused the Debian Bug report #946623,
regarding fwupd: vendor-id hard requirement coming in 6 months
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.)


-- 
946623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fwupd
Version: 1.2.5-2
Severity: important

Dear Maintainer,

I'm quoting from
https://blogs.gnome.org/hughsie/2019/12/11/improving-the-security-model-of-the-lvfs/

[...]
> Most people should be running fwupd 1.3.x, which is the latest and
> greatest branch of fwupd. I appreciate some LTS distros can’t rebase
> to a newer minor version, and so for old versions of fwupd I’ve
> backported the fix. These are the fixes you want if you’re running
> 0.9.x, 1.0.x, 1.1.x or 1.2.x[1].
>
> I’ll make the vendor-id a hard requirement for all vendors in about 6
> months time, so if you maintain a distro packaged version of fwupd you
> have that much time before some updates will stop working. If anyone
> has comments or concerns, please let me know.

It thus seems like it would be a good idea to prepare a stable update of
fwupd including (atleast):

[1]: 
https://github.com/fwupd/fwupd/commit/004a0624d05211e8436060bb7af6b0c6f2d805a3

Regards,
Andreas Henriksson
--- End Message ---
--- Begin Message ---
Source: fwupd
Source-Version: 1.2.13-1
Done: Mario Limonciello 

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

Debian distribution maintenance software
pp.
Mario Limonciello  (supplier of updated fwupd 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Jul 2020 23:13:40 -0500
Source: fwupd
Architecture: source
Version: 1.2.13-1
Distribution: stable
Urgency: medium
Maintainer: Debian EFI 
Changed-By: Mario Limonciello 
Closes: 946623 961490 962517
Changes:
 fwupd (1.2.13-1) stable; urgency=medium
 .
   * Update to 1.2.13 stable release.
 - Fixes issues on stable release (Closes: #961490)
 - Fixes vendor id hard requirement (Closes: #946623)
 - Fixes CVE-2020-10759 (Closes: #962517)
   * Add patch to revert new libxmlb requirement to allow working with libxmlb
   available in Buster.
   * debian/* changes backported from testing:
 - Refresh symbols
 - Install fwupdoffline binary
 - Install fwupd shutdown systemd unit
 - Refresh dependencies for modem manager plugin
 - Update copyright for new new contributors
 - Update watch file for correct upstream URL.
Checksums-Sha1:
 71b3188ec7c73c6efcd8caa583f15c54a6481bde 3685 fwupd_1.2.13-1.dsc
 1626d8b5793a28380345cb1535d5873d65fc59f4 1946644 fwupd_1.2.13.orig.tar.gz
 934fd18367b04f63c9286e72458972156afedfc4 19164 fwupd_1.2.13-1.debian.tar.xz
 7b2ede1e1ee2a3e7c6e34fb3befd234e89c6dcd1 14419 fwupd_1.2.13-1_source.buildinfo
Checksums-Sha256:
 0eb5fe27d62067cb617f99e4ec15987eb95f3a7169be67d3c9b7ed5c31cd3a81 3685 
fwupd_1.2.13-1.dsc
 38c8803640c5a8d194706373e7782c78c11d765a873123e630b96519400bfbf9 1946644 
fwupd_1.2.13.orig.tar.gz
 ef7000951c6256f57c69072a206b6fddd16c8345c649d6f025e235434e85c683 19164 
fwupd_1.2.13-1.debian.tar.xz
 01007c81db56a2d57dc436ac0ba8b73e69696f3c9097174ab2c6a4fd838f4640 14419 
fwupd_1.2.13-1_source.buildinfo
Files:
 f0c7b7d07afddd9d29b241f649fa4aec 3685 admin optional fwupd_1.2.13-1.dsc
 e205c79b43f343c56b340593f4d00c9f 1946644 admin optional 
fwupd_1.2.13.orig.tar.gz
 7f1f680ccc01a2ed005472c5e4a0963e 19164 admin optional 
fwupd_1.2.13-1.debian.tar.xz
 9d9487dc547346af3164babdae903248 14419 admin optional 
fwupd_1.2.13-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEzrtSMB1hfpEDkP4WWHl5VzRCaE4FAl8HA1MRHDkzc2FtQGRl
Ymlhbi5vcmcACgkQWHl5VzRCaE5H2RAAhWikrZZOQ8o56eK0gvseRFnBKmaHmQdr
jKFfkXiJIhAcXFNKE64sipuXwQJFMzvhnELC54O5UQdTDzhBLXzgOkEH9qos+soP
hw/BYpl9Q5PX25zRSH5SPRRx1EmF6Mb97KW5z/VZnIa8fcbvV9wn+aZ46u4kmrbR
uRD8XNY2/RwYatCD0+dWr/pOoVrtgvu3mue5SIbuKc+TWdwOZC5EYTZHAVKyCHze

Bug#952009: marked as done (c-icap-modules: FTBFS: clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 19:17:08 +
with message-id 
and subject line Bug#952009: fixed in c-icap-modules 1:0.5.3-1+deb10u1
has caused the Debian Bug report #952009,
regarding c-icap-modules: FTBFS: clamav_mod.c:108:13: error: expected 
identifier or ‘(’ before string constant
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.)


-- 
952009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: c-icap-modules
Version: 1:0.5.3-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> /bin/bash ../../libtool  --tag=CC   --mode=link gcc  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -fvisibility=hidden -DCI_BUILD_MODULE 
> -D_REENTRANT -g -O2 -fdebug-prefix-map=/build/c-icap-FHVm1G/c-icap-0.5.3=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wall 
> -D_FILE_OFFSET_BITS=64 -I/usr/include -I/usr/include/c_icap -module 
> -avoid-version -Wl,-z,relro -Wl,-z,now -o clamd_mod.la -rpath 
> /usr/lib/x86_64-linux-gnu/c_icap/ clamd_mod_la-clamd_mod.lo  
> libtool: link: gcc -shared  -fPIC -DPIC  .libs/clamd_mod_la-clamd_mod.o-g 
> -O2 -fstack-protector-strong -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro 
> -Wl,-z -Wl,now   -Wl,-soname -Wl,clamd_mod.so -o .libs/clamd_mod.so
> In file included from /usr/include/clamav.h:69,
>  from clamav_mod.c:27:
> clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant
>   108 | static char CLAMAV_VERSION[CLAMAV_VERSION_SIZE];
>   | ^~
> clamav_mod.c: In function ‘clamav_set_versions’:
> clamav_mod.c:645:6: warning: assignment of read-only location ‘"0.102.2"[63]’
>   645 |  CLAMAV_VERSION[CLAMAV_VERSION_SIZE - 1] = '\0';
>   |  ^~
> make[4]: *** [Makefile:512: clamav_mod_la-clamav_mod.lo] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/c-icap-modules_0.5.3-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: c-icap-modules
Source-Version: 1:0.5.3-1+deb10u1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated c-icap-modules package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Jul 2020 23:40:47 +0300
Source: c-icap-modules
Architecture: source
Version: 1:0.5.3-1+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Mathieu Parent 
Changed-By: Adrian Bunk 
Closes: 952009
Changes:
 c-icap-modules (1:0.5.3-1+deb10u1) buster; urgency=medium
 .
   * Non-maintainer upload.
   * Backport support for ClamAV 0.102. (Closes: #952009)
Checksums-Sha1:
 b3ac62d7618d0808b4543badde42fd81afdfec38 2238 
c-icap-modules_0.5.3-1+deb10u1.dsc
 2bcc1dc66435a673b675b010f062a480da56038d 6340 
c-icap-modules_0.5.3-1+deb10u1.debian.tar.xz
Checksums-Sha256:
 f1132600b2e6160707ffd5e9cd02794f155d5b157009f1a992cd0ec731e25adf 2238 
c-icap-modules_0.5.3-1+deb10u1.dsc
 fb4c54c1d95048abbceaab4761625c0cc91490dc4f42492b44ac8745c9901f62 6340 
c-icap-modules_0.5.3-1+deb10u1.debian.tar.xz
Files:
 3d8055f537a02ffd1edff17b78b19629 2238 net optional 
c-icap-modules_0.5.3-1+deb10u1.dsc
 6175fb3b3233e573b60e3f7376485dbc 6340 net optional 
c-icap-modules_0.5.3-1+deb10u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl8Dji4ACgkQiNJCh6LY

Bug#962517: marked as done (CVE-2020-10759)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 18:47:31 +
with message-id 
and subject line Bug#962517: fixed in fwupd 0.8.3-1
has caused the Debian Bug report #962517,
regarding CVE-2020-10759
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.)


-- 
962517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fwupd
Severity: grave
Tags: security

https://github.com/justinsteven/advisories/blob/master/2020_fwupd_dangling_s3_bucket_and_CVE-2020-10759_signature_verification_bypass.md

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: fwupd
Source-Version: 0.8.3-1
Done: Mario Limonciello 

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

Debian distribution maintenance software
pp.
Mario Limonciello  (supplier of updated fwupd 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Jul 2020 23:15:59 -0500
Source: fwupd
Binary: libfwupd1 libdfu1 fwupd fwupd-doc libfwupd-dev gir1.2-fwupd-1.0 
libdfu-dev
Architecture: source
Version: 0.8.3-1
Distribution: oldstable
Urgency: medium
Maintainer: Debian EFI 
Changed-By: Mario Limonciello 
Description:
 fwupd  - Firmware update daemon
 fwupd-doc  - Firmware update daemon documentation (HTML format)
 gir1.2-fwupd-1.0 - GObject introspection data for libfwupd
 libdfu-dev - development files for libdfu
 libdfu1- Firmware update daemon library for DFU support
 libfwupd-dev - development files for libfwupd
 libfwupd1  - Firmware update daemon library
Closes: 961490 962517
Changes:
 fwupd (0.8.3-1) oldstable; urgency=medium
 .
   * Update to 0.8.3 point release
 - Upstream no longer supports the 0.7.x series
   * Drop existing patches all merged into 0.8.3 release.
   * Drop no longer used libebitdo1 and libebitdo-dev packages
   * Refresh symbols
   * Backport series of commits to allow better longevity on 0.8.x
 - Use a CNAME to redirect to the correct CDN for metadata (Closes: #961490)
 - Do not abort startup if the XML metadata file is invalid
 - Add the Linux Foundation public GPG keys for firmware and metadata
 - Raise the metadata limit to 10Mb
 - Validate that gpgme_op_verify_result() returned at least one signature
   (Closes: #962517)
Checksums-Sha1:
 ed25811d2ed70573d32e3edfcfd5f530c5b54c49 3082 fwupd_0.8.3-1.dsc
 4188a585fc2baae3b8df280a18a24b9b94ec5759 1299619 fwupd_0.8.3.orig.tar.gz
 30d654f00f527ddea45b4b0ca418a63cfe3cb078 15640 fwupd_0.8.3-1.debian.tar.xz
 04c12e1d889f2ca142bd9f9191235d6296a89e2c 13819 fwupd_0.8.3-1_source.buildinfo
Checksums-Sha256:
 5f03ea5b04f6428ecdf7d39926af0d0f16c24301b0e7851db48790efb6b53c36 3082 
fwupd_0.8.3-1.dsc
 729536f9b5c531738e05c65bff562bd2f4f434191502952067f3817d4b75511a 1299619 
fwupd_0.8.3.orig.tar.gz
 3f70188e7de01a285e438d00e6f54d9fc7c1489510ed94dc497076c504909b7e 15640 
fwupd_0.8.3-1.debian.tar.xz
 8dce068002c4e9dd1e797605692b7f573902192918e78eb69f52b89f33164066 13819 
fwupd_0.8.3-1_source.buildinfo
Files:
 0e898d6d3def340d45ad85770c845abd 3082 admin optional fwupd_0.8.3-1.dsc
 fc9b209fb6ec6807e21f1a197e95dd82 1299619 admin optional fwupd_0.8.3.orig.tar.gz
 a10fc1c430e35a9fe7f66b842ecca76d 15640 admin optional 
fwupd_0.8.3-1.debian.tar.xz
 137f6fed7aa9812cb2ceaa04e0e67cfd 13819 admin optional 
fwupd_0.8.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEzrtSMB1hfpEDkP4WWHl5VzRCaE4FAl8HA04RHDkzc2FtQGRl
Ymlhbi5vcmcACgkQWHl5VzRCaE7x+A//WUwHWBDMZ2BPLXegYrsQzfrMJY/IaqEC
LRFHVInwIiKoNePR/9ctGwOVbEBCQQpWBrEcwk8LcE5/yEUtPKAfeB4q3KaedsCL
3x03i63bimdc2pUC/izm5sdRUYI7e2Pu+BRtWPvvQuthQik6395TiLf7fo+LYzTv
XLvq9VIIujNe0uMVoXjKHE73u0EgH6tJY7lbE0pfYcRwnmQVtCuzDZeUUln+Z08s
qwkgIO0TdlJz048Z98ZMj3fgdMO8q6aTfzHa51kcYLV7bJyRu36NgQ3wOzsaevNe
bBC74yb5PXnapSz0d8dZbKGS7g1/GKY0ah+TlJMOi68Hn/XGk1drbZhWMC9bxNrL
3T+QRHCH5c9b16CNv2+iXW9qnDv5dIO9EVhMd1SdZqKS0pMo5qN/rJkaDVDrfioF
WoTdIc1Jbvdt/jVvDJl/67r0S5VxThOCd9ZFg9V/EIXgkkmFeHX0kLhWHhLloF3z
iU9ZEh3sbwYwe4YQL/jrWp/xIG8APtYq/qB2mDH/JnGVwXlEFQLVGlbrpm3TCqxJ

Bug#961490: marked as done (fwupd: version in stable too old, no updates possible)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 18:47:31 +
with message-id 
and subject line Bug#961490: fixed in fwupd 0.8.3-1
has caused the Debian Bug report #961490,
regarding fwupd: version in stable too old, no updates possible
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.)


-- 
961490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fwupd
Version: 1.2.5-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The version 1.2.5 of fwupd currently in Debian stable is useless and not able
to perform any firmware updates.
Whem trying to update via command line:

> fwupdmgr refresh && fwupdmgr get-updates

I get the following output:

 Metadaten werden abgerufen https://cdn.fwupd.org/downloads/firmware.xml.gz
 Herunterladen …  [***]
 Signatur wird abgerufen https://cdn.fwupd.org/downloads/firmware.xml.gz.asc

 Not compatible with org.freedesktop.fwupd version 1.2.5, requires >= 1.2.7

The "refresh" part still works, but the new firmware info requires a newer
version of fwupd than available in stable, so the "get-update" part fails.

I'm not sure how to best handle this situation. It's very unfortunate that
fwupd obviously breaks compatibility with older clients here...
Maybe a new version in backports would be possible?

Regards,
Steffen



-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages fwupd depends on:
ii  libarchive13   3.3.3-4+deb10u1
ii  libc6  2.28-10
ii  libefiboot137-2
ii  libefivar1 37-2
ii  libelf10.176-1.1
ii  libfwupd2  1.2.5-2
ii  libgcab-1.0-0  1.2-3~deb10u1
ii  libglib2.0-0   2.58.3-2+deb10u2
ii  libgnutls303.6.7-4+deb10u3
ii  libgpg-error0  1.35-1
ii  libgpgme11 1.12.0-6
ii  libgudev-1.0-0 232-2
ii  libgusb2   0.3.0-1
ii  libjson-glib-1.0-0 1.4.4-2
ii  libpolkit-gobject-1-0  0.105-25
ii  libsmbios-c2   2.4.1-1
ii  libsoup2.4-1   2.64.2-2
ii  libsqlite3-0   3.27.2-3
ii  libxmlb1   0.1.6-2
ii  shared-mime-info   1.10-1

Versions of packages fwupd recommends:
ii  bolt   0.7-2
ii  fwupd-amd64-signed [fwupd-signed]  1.2.5+2
ii  python33.7.3-1
ii  tpm2-abrmd 2.1.0-1
ii  tpm2-tools 3.1.3-2

fwupd suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fwupd
Source-Version: 0.8.3-1
Done: Mario Limonciello 

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

Debian distribution maintenance software
pp.
Mario Limonciello  (supplier of updated fwupd 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Jul 2020 23:15:59 -0500
Source: fwupd
Binary: libfwupd1 libdfu1 fwupd fwupd-doc libfwupd-dev gir1.2-fwupd-1.0 
libdfu-dev
Architecture: source
Version: 0.8.3-1
Distribution: oldstable
Urgency: medium
Maintainer: Debian EFI 
Changed-By: Mario Limonciello 
Description:
 fwupd  - Firmware update daemon
 fwupd-doc  - Firmware update daemon documentation (HTML format)
 gir1.2-fwupd-1.0 - GObject introspection data for libfwupd
 libdfu-dev - development files for libdfu
 libdfu1- Firmware update daemon library for DFU support
 libfwupd-dev - development files for libfwupd
 libfwupd1  - Firmware update daemon library
Closes: 961490 962517
Changes:
 fwupd 

Bug#963548: Received signal 11 SEGV_MAPERR

[Andrey Gursky]

The bug has been reported upstream:

https://bugs.chromium.org/p/chromium/issues/detail?id=1102805



Forwarding good news from one of numerous dupes of this Debian bug, thanks Riku:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964451#25

On Thu, 9 Jul 2020 10:29:36 + Riku Voipio  wrote:
> This should fix it:
>
> https://salsa.debian.org/chromium-team/chromium/-/commit/b904fa41d40b967dcc8f6984db52f7a2f6a2c83d
>
> We are not building with GCC but this seems to be exactly the place where the 
> crash happens.
> chromium built with this patch has not crashed for the last few hours for me, 
> while before it would
> crash in a few minutes.
>
> Riku



Regards,

Andrey

Bug#952009: marked as done (c-icap-modules: FTBFS: clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 18:32:23 +
with message-id 
and subject line Bug#952009: fixed in c-icap-modules 1:0.4.4-1+deb9u2
has caused the Debian Bug report #952009,
regarding c-icap-modules: FTBFS: clamav_mod.c:108:13: error: expected 
identifier or ‘(’ before string constant
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.)


-- 
952009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: c-icap-modules
Version: 1:0.5.3-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> /bin/bash ../../libtool  --tag=CC   --mode=link gcc  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -fvisibility=hidden -DCI_BUILD_MODULE 
> -D_REENTRANT -g -O2 -fdebug-prefix-map=/build/c-icap-FHVm1G/c-icap-0.5.3=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wall 
> -D_FILE_OFFSET_BITS=64 -I/usr/include -I/usr/include/c_icap -module 
> -avoid-version -Wl,-z,relro -Wl,-z,now -o clamd_mod.la -rpath 
> /usr/lib/x86_64-linux-gnu/c_icap/ clamd_mod_la-clamd_mod.lo  
> libtool: link: gcc -shared  -fPIC -DPIC  .libs/clamd_mod_la-clamd_mod.o-g 
> -O2 -fstack-protector-strong -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro 
> -Wl,-z -Wl,now   -Wl,-soname -Wl,clamd_mod.so -o .libs/clamd_mod.so
> In file included from /usr/include/clamav.h:69,
>  from clamav_mod.c:27:
> clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant
>   108 | static char CLAMAV_VERSION[CLAMAV_VERSION_SIZE];
>   | ^~
> clamav_mod.c: In function ‘clamav_set_versions’:
> clamav_mod.c:645:6: warning: assignment of read-only location ‘"0.102.2"[63]’
>   645 |  CLAMAV_VERSION[CLAMAV_VERSION_SIZE - 1] = '\0';
>   |  ^~
> make[4]: *** [Makefile:512: clamav_mod_la-clamav_mod.lo] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/c-icap-modules_0.5.3-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: c-icap-modules
Source-Version: 1:0.4.4-1+deb9u2
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated c-icap-modules package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Jul 2020 23:32:58 +0300
Source: c-icap-modules
Binary: libc-icap-mod-virus-scan libc-icap-mod-clamav libc-icap-mod-urlcheck 
libc-icap-mod-contentfiltering
Architecture: source
Version: 1:0.4.4-1+deb9u2
Distribution: stretch
Urgency: medium
Maintainer: Mathieu Parent 
Changed-By: Adrian Bunk 
Description:
 libc-icap-mod-clamav - transitional dummy package
 libc-icap-mod-contentfiltering - Content filtering Service for c-icap
 libc-icap-mod-urlcheck - URL Check Service for c-icap
 libc-icap-mod-virus-scan - Antivirus Service for c-icap
Closes: 952009
Changes:
 c-icap-modules (1:0.4.4-1+deb9u2) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Backport support for ClamAV 0.102. (Closes: #952009)
Checksums-Sha1:
 c64331eab9c1345d1778a89af97ece38f7ce2ff2 2371 c-icap-modules_0.4.4-1+deb9u2.dsc
 a58bbaa92c46b45b576930bbec344c263788ef75 7228 
c-icap-modules_0.4.4-1+deb9u2.debian.tar.xz
Checksums-Sha256:
 aa0d196f25dfb7d61e97f5d172e0fb781ff5547758cc41d48332615e46015b3c 2371 
c-icap-modules_0.4.4-1+deb9u2.dsc
 8b65559eaf8dbf0106f3605068ac156e98233b53be5bfef7af2506c0fddeb1e6 7228 

Bug#893424: marked as done (Cannot uninstall package)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 18:32:26 +
with message-id 
and subject line Bug#893424: fixed in sendmail 8.15.2-8+deb9u1
has caused the Debian Bug report #893424,
regarding Cannot uninstall package
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.)


-- 
893424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sendmail-base
Version: 8.15.2-10
Severity: serious

Due to a bug in the maintainer script, sendmail-base cannot be uninstalled:

rak@zeta:~$ sudo apt-get remove sendmail-base
[sudo] password for rak:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  lockfile-progs
Use 'sudo apt autoremove' to remove it.
The following packages will be REMOVED:
  sendmail-base
0 upgraded, 0 newly installed, 1 to remove and 52 not upgraded.
After this operation, 867 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 388617 files and directories currently installed.)
Removing sendmail-base (8.15.2-10) ...
rm: cannot remove '/etc/mail/m4': Is a directory
dpkg: error processing package sendmail-base (--remove):
 installed sendmail-base package pre-removal script subprocess returned error 
exit status 123
Errors were encountered while processing:
 sendmail-base
E: Sub-process /usr/bin/dpkg returned an error code (1)
rak@zeta:~$ sudo apt-get purge sendmail-base
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  lockfile-progs
Use 'sudo apt autoremove' to remove it.
The following packages will be REMOVED:
  sendmail-base*
0 upgraded, 0 newly installed, 1 to remove and 52 not upgraded.
After this operation, 867 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 388617 files and directories currently installed.)
Removing sendmail-base (8.15.2-10) ...
rm: cannot remove '/etc/mail/m4': Is a directory
dpkg: error processing package sendmail-base (--remove):
 installed sendmail-base package pre-removal script subprocess returned error 
exit status 123
Errors were encountered while processing:
 sendmail-base
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- Package-specific info:
Output of /usr/share/bug/sendmail-base/script:

ls -alR /etc/mail:
/etc/mail:
total 24
drwxr-xr-x 1 root root   138 Mar 18 14:32 .
drwxr-xr-x 1 root root  5364 Mar 18 13:50 ..
-rw-r--r-- 1 root root   281 Jan 13 17:43 address.resolve
drwxr-xr-x 1 root root 0 Jan 13 17:43 m4
drwxr-xr-x 1 root root16 Mar 18 13:30 peers
-rw-r--r-- 1 root root 12235 Mar 18 13:33 sendmail.conf
-rw-r--r-- 1 root root   148 Jan 13 17:43 service.switch
-rw-r--r-- 1 root root   179 Jan 13 17:43 service.switch-nodns

/etc/mail/m4:
total 0
drwxr-xr-x 1 root root   0 Jan 13 17:43 .
drwxr-xr-x 1 root root 138 Mar 18 14:32 ..

/etc/mail/peers:
total 4
drwxr-xr-x 1 root root  16 Mar 18 13:30 .
drwxr-xr-x 1 root root 138 Mar 18 14:32 ..
-rw-r--r-- 1 root root 328 Jan 13 17:43 provider

sendmail.conf:
DAEMON_NETMODE="Static";
DAEMON_NETIF="eth0";
DAEMON_MODE="Daemon";
DAEMON_PARMS="";
DAEMON_HOSTSTATS="No";
DAEMON_MAILSTATS="No";
QUEUE_MODE="${DAEMON_MODE}";
QUEUE_INTERVAL="10m";
QUEUE_PARMS="";
MSP_MODE="Cron";
MSP_INTERVAL="20m";
MSP_PARMS="";
MSP_MAILSTATS="${DAEMON_MAILSTATS}";
MISC_PARMS="";
CRON_MAILTO="root";
CRON_PARMS="";
LOG_CMDS="No";
HANDS_OFF="No";
AGE_DATA="";
DAEMON_RUNASUSER="No";
DAEMON_STATS="${DAEMON_MAILSTATS}";
MSP_STATS="${MSP_MAILSTATS}";



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

Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_CA.UTF-8), LANGUAGE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_CA.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sendmail-base depends on:
ii  adduser 3.117
ii  lockfile-progs  0.1.17+b1
ii  m4  1.4.18-1
ii  make4.2.1-1
ii  netbase 5.4
ii  perl5.26.1-5

sendmail-base recommends no packages.

Versions of packages sendmail-base suggests:
ii  ca-certificates  20170717
pn  logcheck 
ii  logrotate3.11.0-0.1

Bug#950300: marked as done (mod-gnutls: apache CVE-2019-10092 fix causes FTBFS)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 18:32:24 +
with message-id 
and subject line Bug#950300: fixed in mod-gnutls 0.8.2-3+deb9u2
has caused the Debian Bug report #950300,
regarding mod-gnutls: apache CVE-2019-10092 fix causes FTBFS
to be marked as done.

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

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


-- 
950300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mod-gnutls
Version: 0.8.2-3
Severity: serious
Tags: ftbfs

mod-gnutls appears to rely on the exact wording of apache
error messages, and these changed with CVE-2019-10092.

https://buildd.debian.org/status/package.php?p=mod-gnutls=stretch
https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/mod-gnutls.html

...
FAIL: test-18_client_verification_wrong_cert


TESTING: 18_client_verification_wrong_cert
Server version: Apache/2.4.38 (Debian)
Server built:   2019-10-15T19:53:42
Server's Module Magic Number: 20120211:84
Server loaded:  APR 1.6.5, APR-UTIL 1.6.1
Compiled using: APR 1.6.5, APR-UTIL 1.6.1
Architecture:   64-bit
Server MPM: worker
  threaded: yes (fixed thread count)
forked: yes (variable process count)
Server compiled with
 -D APR_HAS_SENDFILE
 -D APR_HAS_MMAP
 -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
 -D APR_USE_SYSVSEM_SERIALIZE
 -D APR_USE_PTHREAD_SERIALIZE
 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 -D APR_HAS_OTHER_CHILD
 -D AP_HAVE_RELIABLE_PIPED_LOGS
 -D DYNAMIC_MODULE_LIMIT=256
 -D HTTPD_ROOT="/etc/apache2"
 -D SUEXEC_BIN="/usr/lib/apache2/suexec"
 -D DEFAULT_PIDLOG="/var/run/apache2.pid"
 -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
 -D DEFAULT_ERRORLOG="logs/error_log"
 -D AP_TYPES_CONFIG_FILE="mime.types"
 -D SERVER_CONFIG_FILE="apache2.conf"
[Mon Jan 27 07:56:11.674982 2020] [gnutls:debug] [pid 45519:tid 
139910356628608] gnutls_cache.c(354): mgs_cache_inst_config: Socache 
'shmcb:cache/gnutls_cache_18_client_verification_wrong_cert(65536)' created.
AH00557: apache2: apr_sockaddr_info_get() failed for profitbricks-build11-amd64
AH00558: apache2: Could not reliably determine the server's fully qualified 
domain name, using 127.0.0.1. Set the 'ServerName' directive globally to 
suppress this message
flock: getting lock took 1.910177 seconds
flock: executing /usr/sbin/apache2
Processed 1 CA certificate(s).
Processed 1 client X.509 certificates...
Resolving 'localhost:9932'...
Connecting to '127.0.0.1:9932'...
- Successfully sent 1 certificate(s) to server.
- Server has requested a certificate.
- Certificate type: X.509
- Got a certificate list of 1 certificates.
- Certificate[0] info:
 - subject `CN=localhost', issuer `CN=Testing Authority', serial 0x22fff0d9, 
RSA key 3072 bits, signed using RSA-SHA256, activated `2020-01-27 19:56:05 
UTC', expires `2021-01-26 19:56:05 UTC', 
pin-sha256="ShqMB70z9iMRONejdL+6v98HfExpZp/aWi6nXzD6vJE="
Public Key ID:
sha1:7bb678f9fe68cd7ed0fd1df39e9aebad4eee2b94

sha256:4a1a8c07bd33f6231138d7a374bfbabfdf077c4c69669fda5a2ea75f30fabc91
Public Key PIN:
pin-sha256:ShqMB70z9iMRONejdL+6v98HfExpZp/aWi6nXzD6vJE=

- Status: The certificate is trusted. 
- Description: (TLS1.3)-(ECDHE-SECP256R1)-(RSA-PSS-RSAE-SHA256)-(AES-256-GCM)
- Options:
- Handshake was completed

- Simple Client Mode:

HTTP/1.1 403 Forbidden
Date: Mon, 27 Jan 2020 19:56:11 GMT
Server: Apache/2.4.38 (Debian) mod_gnutls/0.9.0 GnuTLS/3.6.7
Content-Length: 199
Connection: close
Content-Type: text/html; charset=iso-8859-1



403 Forbidden

Forbidden
You don't have permission to access this resource.

- Peer has closed the GnuTLS connection
  PID TTY  TIME CMD
45530 ?00:00:00 sleep
--- /build/mod-gnutls-0.9.0/test/tests/18_client_verification_wrong_cert/output 
2017-02-28 07:05:55.0 -1200
+++ /dev/fd/63  2020-01-27 07:56:11.809997988 -1200
@@ -1,7 +1,7 @@
+
+403 Forbidden
 
 Forbidden
-You don't have permission to access /test.txt
-on this server.
-
+You don't have permission to access this resource.
 
 - Peer has closed the GnuTLS connection
FAILURE: 18_client_verification_wrong_cert
[Mon Jan 27 07:56:11.869868 2020] [gnutls:debug] [pid 45630:tid 
139891390706816] gnutls_cache.c(354): mgs_cache_inst_config: Socache 
'shmcb:cache/gnutls_cache_18_client_verification_wrong_cert(65536)' created.
AH00557: apache2: apr_sockaddr_info_get() failed for profitbricks-build11-amd64
AH00558: apache2: Could not reliably determine the server's fully qualified 
domain name, using 127.0.0.1. Set the 'ServerName' directive globally 

Bug#879170: marked as done (libswt-webkit-gtk-3-jni: Needs libwebkitgtk-1.0-0 dep)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 18:32:26 +
with message-id 
and subject line Bug#879170: fixed in swt-gtk 3.8.2-3+deb9u1
has caused the Debian Bug report #879170,
regarding libswt-webkit-gtk-3-jni: Needs libwebkitgtk-1.0-0 dep
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.)


-- 
879170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swt-gtk
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-1.0-0 webkit1

Hi,

swt-gtk Build-Depends on libwebkitgtk-dev, which is deprecated in favor of
libwebkit2gtk-4.0-dev (provided in Debian by webkit2gtk). Please drop
this Build-Depends so that we can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

The package does build successfully without the libwebkitgtk-dev
build-dependency.

It feels to me like the libswt-webkit-gtk-3-jni was already broken
since it doesn't have a dependency on any webkitgtk library (I think
the correct one would be libwebkitgtk-3.0-0 but that is still part of
the deprecated libraries which are being removed.)

If you have any question don't hesitate to ask.

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: swt-gtk
Source-Version: 3.8.2-3+deb9u1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated swt-gtk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 27 Feb 2018 20:33:20 +0200
Source: swt-gtk
Binary: libswt-gtk-3-java libswt-gtk-3-jni libswt-gnome-gtk-3-jni 
libswt-cairo-gtk-3-jni libswt-glx-gtk-3-jni libswt-webkit-gtk-3-jni 
libswt-gtk-3-java-gcj
Architecture: source
Version: 3.8.2-3+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Adrian Bunk 
Description:
 libswt-cairo-gtk-3-jni - Standard Widget Toolkit for GTK+ Cairo JNI library
 libswt-glx-gtk-3-jni - Standard Widget Toolkit for GTK+ GLX JNI library
 libswt-gnome-gtk-3-jni - Standard Widget Toolkit for GTK+ GNOME JNI library
 libswt-gtk-3-java - Standard Widget Toolkit for GTK+ Java library
 libswt-gtk-3-java-gcj - Standard Widget Toolkit for GTK+ native library
 libswt-gtk-3-jni - Standard Widget Toolkit for GTK+ JNI library
 libswt-webkit-gtk-3-jni - Standard Widget Toolkit for GTK+ WebKit JNI library
Closes: 879170
Changes:
 swt-gtk (3.8.2-3+deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * libswt-webkit-gtk-3-jni: Add the missing dependency
 on libwebkitgtk-1.0-0. (Closes: #879170)
Checksums-Sha1:
 bd6f585835193dde9760c1dfb563c137b33956ec 2793 swt-gtk_3.8.2-3+deb9u1.dsc
 2f7a336104cdbcab21af1e4b7887fb2c84b00348 263496 
swt-gtk_3.8.2-3+deb9u1.debian.tar.xz
Checksums-Sha256:
 c192d8c5eb1eeb595c955e3550b0b14b25f2d46af9da2a13074b1dff14bc30cf 2793 
swt-gtk_3.8.2-3+deb9u1.dsc
 2e91dbc8bc3ac038437df899b3214b6bd2c080deea79fb7a4e1cdedf43030872 263496 
swt-gtk_3.8.2-3+deb9u1.debian.tar.xz
Files:
 76061877418459efa2eac536eb2d3aa6 2793 libs optional swt-gtk_3.8.2-3+deb9u1.dsc
 db3867e817db9a3ca6f6d9eb0ed8bcf7 263496 libs optional 
swt-gtk_3.8.2-3+deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl8CWa0ACgkQiNJCh6LY
mLE6EQ//Z3b//XWzid5iSOemQRcrBh1ezSjl55eaLi60SQZ5a5nke0W91/+WwXi4
zV4V1+C2oh87opLW5LWEIg/Y7xksGzD4eAGguCG/urMxN6y10AFscdRqVhGf9Dcu
upv2pb17qb55LP/Adulxd6y6wvGGMCaRBfs9Xhrkhusu8QnzhyET/NqptINx8cnd
sA1G8guD//jRctPjCsl7C85K0OuYIP6ogAKjviBtLiESz3FYWvUC4foRVpJer2HW
WChzYWQUT93iRmxivhi9h3kGb6yoFb9q8IhnSmjuWuUNkWrXEqEBcUwEq0/7C2Rl
+7iWKsf8b5OYlRbaVWrP2CW3O/2N2xKH9og4pa5XUSey2eKM9FZ1Ryce77WHZcqQ
gmVJywImU3Iu8DwaI3FlK9Q+TCJqChTr6WTfUCEX5bk6r7Y8yrhocPamyV1WKo/w

Bug#941926: marked as done (FTBFS: test failure in #238 EmbperlObject/epobase.htm)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 18:32:24 +
with message-id 
and subject line Bug#941926: fixed in libembperl-perl 2.5.0-10+deb9u1
has caused the Debian Bug report #941926,
regarding FTBFS: test failure in #238 EmbperlObject/epobase.htm
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.)


-- 
941926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libembperl-perl
Version: 2.5.0-12
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
Control: block 935737 with -1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The binNMUs for the perl 5.30 transition have shown that libembperl-perl
fails to build. The tests abort (both in testing with 5.28 and in
unstable with 5.30) with:

#238 EmbperlObject/epobase.htm... 
Error in Line 6
Is: >You don't have permission to access this resource.<
Should: >.*?You don't have permission to access 
/embperl/EmbperlObject/epobase.htm<
Input:  test/html/EmbperlObject/epobase.htm
Output: test/tmp/out.htm
Compared to:test/cmp/epobase.htm
Log:test/tmp/test.log
Testparameter:
  cgi = 0
  errors = 1
  offline = 0

 ERRORS detected! NOT all tests have been passed successfully


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl2bZq1fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZJ0BAAlB/vEqG1lAWJIPzgdhn3jlCxjKuXDgftihwgbgTpA0ED6PsZ0/BEk98u
cXOomE2L2TeyNpedspgz/wccPvDu2731Opw4XnA1SPcBHy1GDLtkPiV6jt4vyTA0
c8RcodPQo25ifvlLxetdrv5Cu4w9t0/Q/QRPHojbaIAIpu2GRMMi6MSHnh1AmqrP
BnAbffijjGb1x7gRQPupszRdIZPDzaJ5TdorIvkmRGyCukRxE2CoNPJcGogJvQ0q
4CmILlBMgJvzFWlGWXU7xGchiu3roK2jMgKGr09gtzkhhoAHqCVB59eLqRD+vE4x
mIZZ/M65zuiO/mZzUKeTWany4gy0PMHybsozw7uZaMvXDy7CQ4Nw0ihelBir7Nos
KcUD2Foql2eKQ5j+ukQtKMB0IEI/HVjlGIk4yIM5bPCCCGjnbkJBeGQzU3sF1hTP
COeQTZdVlTXRdxD+3QaZNAm2Lwh8Uclqy2p9RntOYeTxsST0+S5Iojm7+rzcwNkV
+y8KqhIp7OatQ4Ez74P3op7QzHoBTQajx94h4DJIO836T7cQQ4J/UbVJ0Tubn8Ha
rOBh7MiY7vNpVzbcrpN8TZhvpWO26Bby7PoGFIsp2n9ETywAzsHmJKvXihC4Idxm
EFWinLz30w0F/2Z4raF9eSEm1u392HyFCTeZtZ6AuZJU+qyckZo=
=V8Kh
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libembperl-perl
Source-Version: 2.5.0-10+deb9u1
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated libembperl-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Jul 2020 16:04:21 +0300
Source: libembperl-perl
Binary: libembperl-perl
Architecture: source
Version: 2.5.0-10+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Adrian Bunk 
Description:
 libembperl-perl - system for building dynamic websites with Perl
Closes: 941926
Changes:
 libembperl-perl (2.5.0-10+deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Update debian/patches/apache2.4-compat.patch to work with Apache
 2.4.40+ error pages. (Closes: #941926)
Checksums-Sha1:
 bbbc5d3a635f2e11eef524e9a605923fe0a4a929 2311 
libembperl-perl_2.5.0-10+deb9u1.dsc
 2564c677347eb05c22babb79309778b89afe2056 27928 
libembperl-perl_2.5.0-10+deb9u1.debian.tar.xz
Checksums-Sha256:
 521fb3355fdea11524b6b1847363864626926e5fcc1dba55ecd074087dbedcf3 2311 
libembperl-perl_2.5.0-10+deb9u1.dsc
 4451b09b8838992e6b6afb2c383ac79b8f987d7233bf09068d47adfa6fb3309c 27928 
libembperl-perl_2.5.0-10+deb9u1.debian.tar.xz
Files:
 1b3f1a6f75e7541efee6fb955adcf141 2311 perl optional 
libembperl-perl_2.5.0-10+deb9u1.dsc
 57db99c58e32fec7b2c060dbc8f607d4 27928 perl optional 
libembperl-perl_2.5.0-10+deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl8DV8IACgkQiNJCh6LY
mLE/+xAAsK/KuAU/UHpiQJJIolxkJiinyXxa3eM6vFjyEOPs4HB3H55DEQZDjXbd

Bug#879224: marked as done (websockify: missing dependency on python-pkg-resources)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 18:32:27 +
with message-id 
and subject line Bug#879224: fixed in websockify 0.8.0+dfsg1-7+deb9u1
has caused the Debian Bug report #879224,
regarding websockify: missing dependency on python-pkg-resources
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.)


-- 
879224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: websockify
Version: 0.6.0+dfsg1-1
Severity: serious
Control: affects -1 python-websockify python3-websockify

$ websockify 
Traceback (most recent call last):
  File "/usr/bin/websockify", line 5, in 
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources
$ 
--- End Message ---
--- Begin Message ---
Source: websockify
Source-Version: 0.8.0+dfsg1-7+deb9u1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated websockify 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, 14 Mar 2018 18:36:35 +0200
Source: websockify
Binary: websockify-common python-websockify python3-websockify websockify
Architecture: source
Version: 0.8.0+dfsg1-7+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Adrian Bunk 
Description:
 python-websockify - WebSockets support for any application/server - Python 2
 python3-websockify - WebSockets support for any application/server - Python 3
 websockify - WebSockets support for any application/server
 websockify-common - WebSockets support for any application/server - shared 
files
Closes: 879224
Changes:
 websockify (0.8.0+dfsg1-7+deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Add runtime depends on python{3,}-pkg-resources (Closes: #879224).
Checksums-Sha1:
 7b68f9a4214cf1479951a4a9a39277077d1f4b23 2390 
websockify_0.8.0+dfsg1-7+deb9u1.dsc
 ae6e663e962e45d727253f174b8dda3ed15c4c24 11760 
websockify_0.8.0+dfsg1-7+deb9u1.debian.tar.xz
Checksums-Sha256:
 3a0eaf003204e9b7813428af9ef26545a2e0686f4dd530658cf7ff24c4335140 2390 
websockify_0.8.0+dfsg1-7+deb9u1.dsc
 303e75554d5d19bfc999d2aefe01ef3d670d7a94d80ad0db3c7e44ad40dd 11760 
websockify_0.8.0+dfsg1-7+deb9u1.debian.tar.xz
Files:
 033a6d9c013c7d760036ee8712f6f9ea 2390 python optional 
websockify_0.8.0+dfsg1-7+deb9u1.dsc
 e5b425b237da89392e58cc8ce59f40e4 11760 python optional 
websockify_0.8.0+dfsg1-7+deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl8CWbQACgkQiNJCh6LY
mLFrTxAAvraIuEKp6OHJR5vPOH56quDjSzfXRhIvt3yqyjWulK60lvLcxVgmWOOY
wEPHnFz8uFk/A4aKo7uV5PkZ82zq3z6/FfNwGJZp+FciJbj06EYJ8EyIGn9IrsX2
vO2D2m+psammCLDeElCgCgxeFSqG3TqcnghDvHKXy2+JVvlPVlafPcv3TP3005LO
kIknnW2QFj/d0pGhtdH/5YgYmm0lmHjSrRFayXFv7ALNOaIpwLCbN03RvHWSHLjR
DKSPrees4AJrhWU6vGabaQcaoBSS/GfV8rhOVU5+xyTyqQILjXnyT+aXQB9+dCRx
1SxY416M5gN1+dmU+rFapMAf415vL2rhALARDlCyPjVN7PJNLA75h8IV/5bmK5+t
fU40NjlCiYaAn4BJQFpvMd/ijc/9c9dIsTKgHvSYVn3VptVkmSquHkmf0dQEI43S
5JmNpAXFPp6sVfEp+DzmeR5M+VKFUICQKmax9a/4bHyCcdNqio3/7ac/eVc0T1Oh
vf9JiwQVaanz3mDlfu8wzSsIAu0Wp+omtAS80ZavPGW2hTPcXOg8mYbQTsKtYYj9
u+OOQVDaJgjwsGs6DuUo1L1T+OuFvV1vcZXVhW3DELEtTXJ2601MoxaX4djh2YGx
zRWAWuH9dlsSkiJoOrLvj7D77Pip83d0yW6tqX/SpOnf1PQ7sZQ=
=UMgi
-END PGP SIGNATURE End Message ---

Bug#873978: marked as done (sendmail-base: Please check for /usr/share/sendmail/dynamic before sourcing it)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 18:32:26 +
with message-id 
and subject line Bug#873978: fixed in sendmail 8.15.2-8+deb9u1
has caused the Debian Bug report #873978,
regarding sendmail-base: Please check for /usr/share/sendmail/dynamic before 
sourcing it
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.)


-- 
873978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873978
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sendmail-base
Version: 8.15.2-8
Severity: serious

I had sendmail installed. Then I removed it including sendmail-base. I
used "apt-get remove" instead of "purge" and this did not end well. The
log was quickly filled with this:

|Sep  1 21:28:02 debbuildd dhclient[3221]: DHCPREQUEST of 172.123.10.83 on eth0 
to 255.255.255.255 port 67
|Sep  1 21:28:02 debbuildd dhclient[3221]: DHCPOFFER of 172.123.10.83 from 
172.123.10.1
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPACK of 172.123.10.83 from 
172.123.10.1
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPDECLINE on eth0 to 
255.255.255.255 port 67
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPDISCOVER on eth0 to 
255.255.255.255 port 67 interval 5
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPREQUEST of 172.123.10.83 on eth0 
to 255.255.255.255 port 67
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPOFFER of 172.123.10.83 from 
172.123.10.1
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPACK of 172.123.10.83 from 
172.123.10.1
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPDECLINE on eth0 to 
255.255.255.255 port 67
 
The reason for the DHCPCELINE was:
|/sbin/dhclient-script: 28: . :Can't open /usr/share/sendmail/dynamic

Which could have been caused by
|/etc/network/if-up.d/sendmail:. /usr/share/sendmail/dynamic;
|/etc/network/if-post-down.d/sendmail:. /usr/share/sendmail/dynamic;
|/etc/network/if-down.d/sendmail:. /usr/share/sendmail/dynamic;
|/etc/dhcp/dhclient-exit-hooks.d/sendmail:. /usr/share/sendmail/dynamic;
|/etc/ppp/ip-up.d/sendmail:. /usr/share/sendmail/dynamic;
|/etc/ppp/ip-down.d/sendmail:. /usr/share/sendmail/dynamic;
|/etc/resolvconf/update-libc.d/sendmail:. /usr/share/sendmail/dynamic;

but in my case it was /etc/dhcp/dhclient-exit-hooks.d/sendmail.

Please either remove those files on remove or test for
"/usr/share/sendmail/dynamic" before the script sources the file.

This was a headless box so it took while to notice…

Sebastian
--- End Message ---
--- Begin Message ---
Source: sendmail
Source-Version: 8.15.2-8+deb9u1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated sendmail package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Aug 2019 20:07:11 +0200
Source: sendmail
Binary: sendmail-bin rmail sensible-mda libmilter1.0.1 libmilter-dev 
sendmail-doc sendmail sendmail-base sendmail-cf
Architecture: source
Version: 8.15.2-8+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 libmilter-dev - Sendmail Mail Filter API (Milter) (development files)
 libmilter1.0.1 - Sendmail Mail Filter API (Milter)
 rmail  - MTA->UUCP remote mail handler
 sendmail   - powerful, efficient, and scalable Mail Transport Agent (metapacka
 sendmail-base - powerful, efficient, and scalable Mail Transport Agent (arch 
inde
 sendmail-bin - powerful, efficient, and scalable Mail Transport Agent
 sendmail-cf - powerful, efficient, and scalable Mail Transport Agent (config ma
 sendmail-doc - powerful, efficient, and scalable Mail Transport Agent 
(documenta
 sensible-mda - Mail Delivery Agent wrapper
Closes: 863567 873978 887064 893424 894535
Changes:
 sendmail (8.15.2-8+deb9u1) stretch; urgency=medium
 .
   * QA upload.
   * rmail: Add exim4 to the list of conflicting MTAs.  (Closes: #863567)
   * Skip hook execution if /usr/share/sendmail/dynamic does not exist.
 (Closes: #873978)
   * debian/examples/network/if-post-down.d/sendmail: Generate during build.
   * 

Bug#867436: marked as done (python3-icalendar: missing dependencies)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 18:32:25 +
with message-id 
and subject line Bug#867436: fixed in python-icalendar 3.8-1+deb9u1
has caused the Debian Bug report #867436,
regarding python3-icalendar: missing dependencies
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.)


-- 
867436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-icalendar
Version: 3.8-1
Severity: serious
Tags: patch

Due to a cut'n'paste error some dependencies are missing.

Fix:

--- debian/control.old  2017-07-06 16:29:45.0 +
+++ debian/control  2017-07-06 16:29:54.0 +
@@ -50,7 +50,7 @@
 Architecture: all
 Depends: ${shlibs:Depends},
  ${misc:Depends},
- ${python:Depends},
+ ${python3:Depends},
  python3-tz,
  python3-dateutil
 Provides: ${python:Provides}
--- End Message ---
--- Begin Message ---
Source: python-icalendar
Source-Version: 3.8-1+deb9u1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated python-icalendar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Mar 2018 22:00:53 +0200
Source: python-icalendar
Binary: python-icalendar-doc python-icalendar python3-icalendar
Architecture: source
Version: 3.8-1+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Adrian Bunk 
Description:
 python-icalendar - parser/generator of iCalendar files for use with Python2
 python-icalendar-doc - parser/generator of iCalendar files for use with Python 
-- docs
 python3-icalendar - parser/generator of iCalendar files for use with Python3
Closes: 867436
Changes:
 python-icalendar (3.8-1+deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Fix the python3-icalendar dependencies. (Closes: #867436)
Checksums-Sha1:
 95067394373b50728e5b2f7a1158744c22e26de7 2288 python-icalendar_3.8-1+deb9u1.dsc
 2d604a05f84d18b18d039c9ab99413b0e34fd948 3252 
python-icalendar_3.8-1+deb9u1.debian.tar.xz
Checksums-Sha256:
 3e763c3057bb30fb38cd6d0aa156935bb2a44fbb791abd9dde03e1a8b8d14e97 2288 
python-icalendar_3.8-1+deb9u1.dsc
 46a99f717924205628d5cd5db4d970ed66108a1f29b1be191857b5ac592a4887 3252 
python-icalendar_3.8-1+deb9u1.debian.tar.xz
Files:
 c7787b02903e9eed93e60b5d241889a2 2288 python optional 
python-icalendar_3.8-1+deb9u1.dsc
 ee11bcfe2fe95e0745d8140429f62849 3252 python optional 
python-icalendar_3.8-1+deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl8CWboACgkQiNJCh6LY
mLF9kg//cQmk8d3ltwRJwnB3IOr6iQhBFYunSBHIeHX/izQqaykaLgETHbRRPMlV
sV6B8TO5ALumhJGu/dzHOx0jV8igR4LeSv4WeTj7Jk5+fL5Sl8zrPj5lVwAzhNVq
iFXoa3lzAs6Av4Qlcj+grRAuB8/s7x1ZailpFOAF9+VVUIuSZt3brTDf6TJ9X+wF
67v54oclV5wi1m5KrDSfPCjMGC3KgpmuJMgJQHldSoSSITPutXpTaQZvwA2M891I
q8Hb0Oc/ZH1o+UAAe0UMrIQONZrE2IJOL9Vrb1AhedbsNDqeoloDS9tx/qQs4S9Z
Y3bpuvRJzytFiPng2ZiQ7J91V/uzb3IkBY4Fs75FrKe7R+4DfJUAl/u7jgXE73mX
AMq5ULIr3VeF5Jk9MgU13ZSKNn91rUI0OJgtSOLPgQyega3tHxTcdZRmgrsMaHeS
9zR199OysYYJ5OAn9Y0iwvRcFR8x2pnEGOrVPGc73nApcpuSEF6Si8r3iR8tHbn7
tx1k5wc9ZimGz07XvrOAv2XHMil3tVEUfmTRIMrrqaofpPICuqIEvBsVtyiV8srE
84Obw4wv6AFsw6lOVL6xpSLOT90PKCVryLrv7FdxFXN+d81SlI/gkkg7Qsa5wGnV
nITzBSDSQi73b3RcqYba0WOa4ux8qvzPBB0Gcv0PAQDw3ZhES9U=
=5Vuy
-END PGP SIGNATURE End Message ---

Processed: [bts-link] source package src:kafkacat

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:kafkacat
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #963440 (http://bugs.debian.org/963440)
> # Bug title: kafkacat: FTBFS: dh_auto_configure: error: ./configure 
> --build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include 
> --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info 
> --sysconfdir=/etc --localstatedir=/var --disable-option-checking 
> --disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
> --libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
> --disable-dependency-tracking --enable-json --enable-avro --no-download 
> returned exit code 1
> #  * https://github.com/edenhill/mklove/issues/28
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 963440 + fixed-upstream
Bug #963440 [src:kafkacat] kafkacat: FTBFS: dh_auto_configure: error: 
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --enable-json --enable-avro --no-download 
returned exit code 1
Added tag(s) fixed-upstream.
> usertags 963440 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 963440 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:golang-golang-x-text

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:golang-golang-x-text
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #964272 (http://bugs.debian.org/964272)
> # Bug title: golang-golang-x-text: CVE-2020-14040
> #  * https://github.com/golang/go/issues/39491
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 964272 + fixed-upstream
Bug #964272 [src:golang-golang-x-text] golang-golang-x-text: CVE-2020-14040
Added tag(s) fixed-upstream.
> usertags 964272 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:golang-x-text

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:golang-x-text
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #964271 (http://bugs.debian.org/964271)
> # Bug title: golang-x-text: CVE-2020-14040
> #  * https://github.com/golang/go/issues/39491
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 964271 + fixed-upstream
Bug #964271 [src:golang-x-text] golang-x-text: CVE-2020-14040
Added tag(s) fixed-upstream.
> usertags 964271 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#916192: marked as done (foma ftbfs from source)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 17:06:54 +
with message-id 
and subject line Bug#916192: fixed in foma 1:0.9.18+r243-8
has caused the Debian Bug report #916192,
regarding foma ftbfs from source
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.)


-- 
916192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:defoma
Version: 1:0.9.18+r243-4
Severity: serious

defoma ftbfs from source, at least on armhf and s390x (also on amd64 and i386 in
Ubuntu with the same failure):

see https://buildd.debian.org/status/package.php?p=foma

gcc -g -O2 -fdebug-prefix-map=/<>/foma-0.9.18+r243=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall -D_GNU_SOURCE
-std=c99 -fvisibility=hidden -fPIC -Wl,-z,relro -c regex.c -o regex.o
gcc -g -O2 -fdebug-prefix-map=/<>/foma-0.9.18+r243=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall -D_GNU_SOURCE
-std=c99 -fvisibility=hidden -fPIC -Wl,-z,relro -c foma.c -o foma.o
regex.c: In function 'yyparse':
regex.c:2779:3: error: unterminated comment
   /* User semantic actions sometimes alter yychar, and that requires
   ^
regex.c:2778:5: error: expected declaration or statement at end of input
 }
 ^
regex.y:406:5: error: label 'yyerrorlab' used but not defined
 { if (($$ = function_apply(defined_nets, defined_funcs)) == NULL) YYERROR;}
 ^
regex.c:1950:5: error: label 'yyerrlab' used but not defined
 goto yyerrlab;
 ^~~~
regex.c:1874:5: error: label 'yyacceptlab' used but not defined
 YYACCEPT;
 ^~~~
regex.c:1868:9: error: label 'yyabortlab' used but not defined
 YYABORT;
 ^~~
regex.c:1849:11: error: label 'yyexhaustedlab' used but not defined
   goto yyexhaustedlab;
   ^~~~
regex.c:1746:7: warning: unused variable 'yyresult' [-Wunused-variable]
   int yyresult;
   ^~~~
regex.c:1741:13: warning: variable 'yyerror_range' set but not used
[-Wunused-but-set-variable]
 YYLTYPE yyerror_range[3];
 ^
regex.c:1711:9: warning: variable 'yynerrs' set but not used
[-Wunused-but-set-variable]
 int yynerrs;
 ^~~
regex.c:2778:5: warning: control reaches end of non-void function 
[-Wreturn-type]
 }
 ^
At top level:
regex.c:1666:1: warning: 'yydestruct' defined but not used [-Wunused-function]
 yydestruct (const char *yymsg, int yytype, YYSTYPE *yyvaluep, YYLTYPE
*yylocationp, void *scanner, struct defined_networks *defined_nets, struct
defined_functions *defined_funcs)
 ^~
regex.c:1147:27: warning: 'yyr1' defined but not used [-Wunused-const-variable=]
 static const yytype_uint8 yyr1[] =
   ^~~~
regex.c:1112:27: warning: 'yystos' defined but not used 
[-Wunused-const-variable=]
 static const yytype_uint8 yystos[] =
   ^~
regex.c:854:27: warning: 'yydefgoto' defined but not used 
[-Wunused-const-variable=]
 static const yytype_int16 yydefgoto[] =
   ^
regex.c:846:26: warning: 'yypgoto' defined but not used 
[-Wunused-const-variable=]
 static const yytype_int8 yypgoto[] =
  ^~~
make[1]: *** [Makefile:92: regex.o] Error 1
make[1]: *** Waiting for unfinished jobs
make[1]: Leaving directory '/<>/foma-0.9.18+r243'
dh_auto_build: make V=1 -j4 "INSTALL=install --strip-program=true" returned exit
code 2
make: *** [debian/rules:10: build-arch] Error 2
--- End Message ---
--- Begin Message ---
Source: foma
Source-Version: 1:0.9.18+r243-8
Done: Kartik Mistry 

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated foma 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, 09 Jul 2020 22:11:25 +0530
Source: foma
Architecture: source
Version: 1:0.9.18+r243-8
Distribution: unstable
Urgency: low
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Closes: 916192
Changes:
 foma (1:0.9.18+r243-8) 

Bug#964657: marked as done (nginx-confgen: FTBFS: Configuring nginx-confgen-1.2... Setup: Encountered missing or private dependencies: megaparsec ==7.*)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 16:33:31 +
with message-id 
and subject line Bug#964657: fixed in nginx-confgen 1.2-3
has caused the Debian Bug report #964657,
regarding nginx-confgen: FTBFS: Configuring nginx-confgen-1.2...  Setup: 
Encountered missing or private dependencies: megaparsec ==7.*
to be marked as done.

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

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


-- 
964657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nginx-confgen
Version: 1.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ghc --make Setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking Setup ...
> ./Setup configure
> Configuring nginx-confgen-1.2...
> Setup: Encountered missing or private dependencies:
> megaparsec ==7.*
> 
> make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/nginx-confgen_1.2-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: nginx-confgen
Source-Version: 1.2-3
Done: Jordi Mallach 

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

Debian distribution maintenance software
pp.
Jordi Mallach  (supplier of updated nginx-confgen 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, 09 Jul 2020 18:14:25 +0200
Source: nginx-confgen
Architecture: source
Version: 1.2-3
Distribution: unstable
Urgency: medium
Maintainer: Jordi Mallach 
Changed-By: Jordi Mallach 
Closes: 964657
Changes:
 nginx-confgen (1.2-3) unstable; urgency=medium
 .
   * Add patch to fix build with megaparsec 8.x (closes: #964657).
Checksums-Sha1:
 3185a01585889a808408d5cb11adc9fc2563774e 2160 nginx-confgen_1.2-3.dsc
 b3f5c5ac0053db8ba523366300b5737b8bda554d 4448 nginx-confgen_1.2-3.debian.tar.xz
 1f46dad2dbec5d16861b567b7b2d52799562bfea 7977 
nginx-confgen_1.2-3_amd64.buildinfo
Checksums-Sha256:
 e052ff08180823d0cd4c546cd61423c41f5e842fffbb68b549e1e3bb73bda8d6 2160 
nginx-confgen_1.2-3.dsc
 921848adf4cdf6bd95b3303d9fed4676bfed467b9613e1abfdba33bcbf85c069 4448 
nginx-confgen_1.2-3.debian.tar.xz
 50843f682df580aa08645b84c66372f2551d458980719ea2f12ea335f37c3741 7977 
nginx-confgen_1.2-3_amd64.buildinfo
Files:
 bf3953c2a136a26fb0b471842a2a3a99 2160 web optional nginx-confgen_1.2-3.dsc
 9b70b41e695a58a77ecf10c73a962ac2 4448 web optional 
nginx-confgen_1.2-3.debian.tar.xz
 8db419a488ef02b1dd536f3312afc359 7977 web optional 
nginx-confgen_1.2-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE6BdUhsApKYN8KGoWJVAvb8vjywQFAl8HQy8ACgkQJVAvb8vj
ywTa/hAAx3uaBwbD8v/G0Q34o3s9P0jvJ3FJgiWNrH1ap3DuEeb3lvxv1ZguCTpU
uo+76QFKXuyTS7nuJI1jGsF0B5qQrNxHXeC6qV7lXolcO9GKWEwDvpC4Uun0WWdp
Ga691gi8Y3OmG2rwv0EGKdo6ZIydiE84go6bYn5uAdGlIZDmmKN6fxhBuqXVbJ/A
Eq1DMLjxo24FP+Obt59JameUX2MAGL2lplmq545pHKuyE4/jF3hST6fcM2Kn4JWB
XcfoXa6QLGbI2AYkpFld0q4KW8MsE4FOsHORygWnQclS5RVCkfZnQhsR7m39bciM
hTcbT6vZ2hmy6lSaNQ/95o0cSZn57YnkbmzxIBUMf+AN2wtmUpzeecleF9oeUlOV
sH8bQqOaF3oU+wvpGbmPszbj1jQ2sm8NfW/cYUG/OzdYac0bGMfrRJuIzdaMhxAI
R75KJLnhCQQSGv9oZQt9miUN6y9pUMU63CcyvuCj7Z1lFXX5tcJu3ug3PqxRlRb4
HMyJcHivnUEhDr7fSaEkAAtdr3nNkwp+S1Yq38M3fNEy7DB25WyKKJs+PQ8obQN+
3OItskgXKveuPwOCpJbsM8KSOkEgv82h3Bf8mx56/xtN8r2weIWLZPQ+ayfQKUQz
PMLmyTQnXHRtNgF3lpl3P1rlJzH9hzD3exc6iIMGJLuuuSBfeZ8=
=ROAw
-END PGP SIGNATURE End Message ---

Bug#954590: marked as done (python-bayespy: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.7 3.8" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 16:04:50 +
with message-id 
and subject line Bug#954590: fixed in python-bayespy 0.5.18-3
has caused the Debian Bug report #954590,
regarding python-bayespy: FTBFS: dh_auto_test: error: pybuild --test 
--test-nose -i python{version} -p "3.7 3.8" returned exit code 13
to be marked as done.

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

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


-- 
954590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-bayespy
Version: 0.5.18-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> xvfb-run -a dh_auto_test
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.7_bayespy/build; 
> python3.7 -m nose -v 
> Test the creation of Bernoulli nodes. ... ok
> Test mixture of Bernoulli ... 
> /<>/.pybuild/cpython3_3.7_bayespy/build/bayespy/inference/vmp/nodes/categorical.py:43:
>  FutureWarning: Using a non-tuple sequence for multidimensional indexing is 
> deprecated; use `arr[tuple(seq)]` instead of `arr[seq]`. In the future this 
> will be interpreted as an array index, `arr[np.array(seq)]`, which will 
> result either in an error or a different result.
>   u0[[np.arange(np.size(x)), np.ravel(x)]] = 1
> ok
> Test the moments of Bernoulli nodes. ... ok
> Test observation of Bernoulli node ... ok
> Test random sampling in Bernoulli node ... ok
> Test the creation of beta nodes. ... ok
> Test the moments of beta nodes. ... ok
> Test random sampling of beta nodes. ... ok
> Test the creation of binomial nodes. ... ok
> Test binomial mixture ... ok
> Test the moments of binomial nodes. ... ok
> Test observation of Bernoulli node ... ok
> Test random sampling in Binomial node ... ok
> Test constant categorical nodes ... ok
> Check the Euclidean gradient of the categorical node ... ok
> Test the creation of categorical nodes. ... ok
> Test initialization of categorical nodes ... 
> /<>/.pybuild/cpython3_3.7_bayespy/build/bayespy/inference/vmp/nodes/categorical.py:43:
>  FutureWarning: Using a non-tuple sequence for multidimensional indexing is 
> deprecated; use `arr[tuple(seq)]` instead of `arr[seq]`. In the future this 
> will be interpreted as an array index, `arr[np.array(seq)]`, which will 
> result either in an error or a different result.
>   u0[[np.arange(np.size(x)), np.ravel(x)]] = 1
> ok
> Test the moments of categorical nodes. ... ok
> Test observed categorical nodes ... 
> /<>/.pybuild/cpython3_3.7_bayespy/build/bayespy/inference/vmp/nodes/categorical.py:107:
>  FutureWarning: Using a non-tuple sequence for multidimensional indexing is 
> deprecated; use `arr[tuple(seq)]` instead of `arr[seq]`. In the future this 
> will be interpreted as an array index, `arr[np.array(seq)]`, which will 
> result either in an error or a different result.
>   u0[[np.arange(np.size(x)), np.ravel(x)]] = 1
> ok
> Test the creation of CategoricalMarkovChain object ... ok
> Test the message of CategoricalMarkovChain to child ... ok
> Test random sampling of categorical Markov chain ... ok
> Test the creation of Concatenate node ... ok
> Test the mask handling in Concatenate node ... ok
> Test the message to child of Concatenate node. ... ok
> Test the message to parents of Concatenate node. ... ok
> Test the mask message to parent of Tile node. ... ok
> Test the moments of Tile node. ... ok
> Test the parent message of Tile node. ... ok
> Test the constant moments of Dirichlet nodes. ... ok
> Test the creation of Dirichlet nodes. ... ok
> Test the moments of Dirichlet nodes. ... ok
> Test the message from SumMultiply to its children. ... ok
> Test the message from SumMultiply node to its parents. ... ok
> Test that the parent nodes are validated properly in SumMultiply ... ok
> test_lower_bound_contribution 
> (bayespy.inference.vmp.nodes.tests.test_gamma.TestGamma) ... ok
> Test standard gradient of a Gamma node. ... ok
> Test Riemannian gradient of a Gamma node. ... ok
> Test the creation of Gate node ... 
> /<>/.pybuild/cpython3_3.7_bayespy/build/bayespy/inference/vmp/nodes/categorical.py:43:
>  FutureWarning: Using a non-tuple sequence for multidimensional indexing is 
> deprecated; use `arr[tuple(seq)]` instead of `arr[seq]`. In the future this 
> will be interpreted as an array index, `arr[np.array(seq)]`, which will 
> result either in an error or a different result.
>   u0[[np.arange(np.size(x)), np.ravel(x)]] = 1
> ok
> 

Processed: bug 964679 is forwarded to https://gitlab.gnome.org/GNOME/gtk/-/issues/2919, tagging 964679

[Debian Bug Tracking System]

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

> forwarded 964679 https://gitlab.gnome.org/GNOME/gtk/-/issues/2919
Bug #964679 [src:gtk+3.0] gtk+3.0: FTBFS: dpkg-gensymbols: error: some new 
symbols appeared in the symbols file: see diff output below
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/gtk/-/issues/2919'.
> # GLib behaviour change, see upstream issue and merge request
> tags 964679 + patch
Bug #964679 [src:gtk+3.0] gtk+3.0: FTBFS: dpkg-gensymbols: error: some new 
symbols appeared in the symbols file: see diff output below
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#964679: marked as pending in gtk+3.0

[Simon McVittie]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/gnome-team/gtk3/-/commit/df6191ce8af70e94235b96cc8a513c0a65a51b63


Add proposed patch to fix FTBFS with newer GLib versions

Closes: #964679


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/964679

Processed: Bug#964679 marked as pending in gtk+3.0

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #964679 [src:gtk+3.0] gtk+3.0: FTBFS: dpkg-gensymbols: error: some new 
symbols appeared in the symbols file: see diff output below
Added tag(s) pending.

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

Processed: your mail

[Debian Bug Tracking System]

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

> tags 962616 - unreproducible
Bug #962616 [src:webkit2gtk] webkit2gtk: FTBFS on mipsel
Removed tag(s) unreproducible.
> block 962616 by 964728
Bug #962616 [src:webkit2gtk] webkit2gtk: FTBFS on mipsel
962616 was not blocked by any bugs.
962616 was not blocking any bugs.
Added blocking bug(s) of 962616: 964728
> affects 964728 webkit2gtk
Bug #964728 [gtk-doc-tools] gtk-doc-tools: gtkdoc-scangobj fails in mipsel / 
Loongson when building webkit2gtk
Added indication that 964728 affects webkit2gtk
> thanks
Stopping processing here.

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

Bug#963299: marked as done (sniffles: FTBFS: BamParser.h:11:10: fatal error: api/BamMultiReader.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 15:34:36 +
with message-id 
and subject line Bug#963299: fixed in sniffles 1.0.11+ds-2
has caused the Debian Bug report #963299,
regarding sniffles: FTBFS: BamParser.h:11:10: fatal error: 
api/BamMultiReader.h: No such file or directory
to be marked as done.

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

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


-- 
963299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sniffles
Version: 1.0.11+ds-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++   
> -I/usr/include/bamtools: -I/<>/src/../lib/bamtools-2.3.0/src 
> -I/<>/src/../lib/tclap-1.2.1/include  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp   -o 
> CMakeFiles/sniffles.dir/Alignment.cpp.o -c /<>/src/Alignment.cpp
> In file included from /<>/src/BamParser.cpp:8:
> /<>/src/BamParser.h:11:10: fatal error: api/BamMultiReader.h: No 
> such file or directory
>11 | #include "api/BamMultiReader.h"
>   |  ^~
> compilation terminated.
> make[3]: *** [src/CMakeFiles/sniffles.dir/build.make:105: 
> src/CMakeFiles/sniffles.dir/BamParser.cpp.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/sniffles_1.0.11+ds-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: sniffles
Source-Version: 1.0.11+ds-2
Done: Pranav Ballaney 

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

Debian distribution maintenance software
pp.
Pranav Ballaney  (supplier of updated sniffles 
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: Fri, 03 Jul 2020 06:02:36 +0530
Source: sniffles
Architecture: source
Version: 1.0.11+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Pranav Ballaney 
Closes: 963299
Changes:
 sniffles (1.0.11+ds-2) unstable; urgency=medium
 .
   [ Afif Elghraoui ]
   * Remove myself from Uploaders
 .
   [ Steffen Moeller ]
   * d/u/metadata: yamllint
 .
   [ Steffen Möller ]
   * Update metadata with ref to conda
   * Update metadata / added ref to bio.tools
 .
   [ Pranav Ballaney ]
   * Fix INCLUDE_PATHS. Closes: #963299.
   * Add to Uploaders
   * Install examples and docs
 .
   [ Andreas Tille ]
   * Standards-Version: 4.5.0 (routine-update)
   * debhelper-compat 13 (routine-update)
   * Add salsa-ci file (routine-update)
   * Rules-Requires-Root: no (routine-update)
   * Set upstream metadata fields: Bug-Database, Bug-Submit.
Checksums-Sha1:
 41fbc994f670f1aa566614df4857e6d6c7b7357d 2070 sniffles_1.0.11+ds-2.dsc
 1d298f13931dfd322f8b4a8656cd9dac0a6174d3 5480 
sniffles_1.0.11+ds-2.debian.tar.xz
 3e029e9376b34fb7d3eb80b0db1bb0f18f550451 6940 
sniffles_1.0.11+ds-2_amd64.buildinfo
Checksums-Sha256:
 c55981531c4df263defeb8e88cc43bb51b14b19c23e941ea098ed8f31278b73d 2070 
sniffles_1.0.11+ds-2.dsc
 a526857878a0cb7d5ab880fa9ffa8bc4d38e7ff865550ca1f0849daeffef48f7 5480 
sniffles_1.0.11+ds-2.debian.tar.xz
 83bf54982ae15a32989f6d0877b327638ae732f97858c2c83f4081005b27aac2 6940 
sniffles_1.0.11+ds-2_amd64.buildinfo
Files:
 308f286eea05e7f2ab6336a79e6efc79 2070 science optional sniffles_1.0.11+ds-2.dsc
 9c8432f07169bf897553ccb277f3feee 5480 science optional 
sniffles_1.0.11+ds-2.debian.tar.xz
 a2535a11b0b37a4cbc81adad178aa490 6940 science optional 
sniffles_1.0.11+ds-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#964620: marked as done (binutils-mingw-w64: FTBFS: patching fails)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 15:18:26 +
with message-id 
and subject line Bug#964620: fixed in binutils-mingw-w64 8.10
has caused the Debian Bug report #964620,
regarding binutils-mingw-w64: FTBFS: patching 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.)


-- 
964620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: binutils-mingw-w64
Version: 8.9
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> tar xf /usr/src/binutils/binutils-2.34.90.tar.*
> rm -rf /<>/upstream
> mv binutils-* /<>/upstream
> patch -d /<>/upstream -R -p1 < 
> /usr/src/binutils/patches/001_ld_makefile_patch.patch
> patching file ld/Makefile.am
> patching file ld/Makefile.in
> Hunk #1 succeeded at 558 (offset 3 lines).
> QUILT_SERIES=debian/patches/series QUILT_PATCHES=debian/patches quilt push -a
> Applying patch debian/patches/testsuite-timeout.patch
> patching file upstream/gas/testsuite/lib/gas-defs.exp
> 
> Applying patch debian/patches/specify-timestamp.patch
> patching file upstream/bfd/peXXigen.c
> Hunk #2 FAILED at 879.
> 1 out of 2 hunks FAILED -- rejects in file upstream/bfd/peXXigen.c
> patching file upstream/ld/pe-dll.c
> Hunk #2 FAILED at 1213.
> 1 out of 2 hunks FAILED -- rejects in file upstream/ld/pe-dll.c
> patching file upstream/ld/emultempl/pe.em
> patching file upstream/ld/emultempl/pep.em
> Patch debian/patches/specify-timestamp.patch does not apply (enforce with -f)
> make[1]: *** [debian/rules:50: unpack-stamp] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/binutils-mingw-w64_8.9_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: binutils-mingw-w64
Source-Version: 8.10
Done: Stephen Kitt 

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated binutils-mingw-w64 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, 09 Jul 2020 14:11:33 +0200
Source: binutils-mingw-w64
Architecture: source
Version: 8.10
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Closes: 964620
Changes:
 binutils-mingw-w64 (8.10) unstable; urgency=medium
 .
   * Adjust to binutils 2.35 changes. Closes: #964620.
Checksums-Sha1:
 a9d1d53513ef7f5ebb9637a9f6464c7e0de195ec 1905 binutils-mingw-w64_8.10.dsc
 39db83eefd9a2b1140833d588e52f953eca97938 11324 binutils-mingw-w64_8.10.tar.xz
 a3c4f11755589b0dd6b004d0f4817d333f234c7e 7134 
binutils-mingw-w64_8.10_source.buildinfo
Checksums-Sha256:
 ea5caea8a88a64dce49c00cd42579b5903e7b1c33bbb4f4208a14cf56cc56069 1905 
binutils-mingw-w64_8.10.dsc
 2438fe11e6aaf17e1e3dc878e12fa35e5e43c07218abe320ef2e159de3ed297f 11324 
binutils-mingw-w64_8.10.tar.xz
 84ce8befd8d647860bb882f0ee8eecc6c768ac2bce7e30344c942b4045020571 7134 
binutils-mingw-w64_8.10_source.buildinfo
Files:
 55c4a7eec25c13450bfba65d892b2ee0 1905 devel optional 
binutils-mingw-w64_8.10.dsc
 34daebd1b5654a806909e93c2a421851 11324 devel optional 
binutils-mingw-w64_8.10.tar.xz
 9269bc2f28f795db8e239f0ebdf4ea12 7134 devel optional 
binutils-mingw-w64_8.10_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAl8HMJMACgkQgNMC9Yht
g5z2CA/+Krf3peSI8ZrJDcwIgz8lX/UaBEF08MeFo/PLJ

Bug#963010: roundcube-core: roundcube upgrade keeps breaking my instance due to automatic permission changes of config.inc.php

[Guilhem Moulin]

Hi,

On Thu, 09 Jul 2020 at 16:53:03 +0200, Mirko Vogt wrote:
> Can I do anything to push this being fixed or workaround this myself
> without weakening my setup security wise? Thanks!

The bug metadata say:

  Found in versions roundcube-core/1.2.3+dfsg.1-4+deb9u3, 
roundcube-core/1.3.13+dfsg.1-1~deb10u1, roundcube-core/1.3.10+dfsg.1-1~deb10u1
  Fixed in versions roundcube-core/1.4.3+dfsg.1-1

So right now versions in testing, sid, and buster-backports are
unaffected, while those in buster, buster-security and stretch and
stretch-security (or anything earlier) are affected.

Some work has been done in the postinst script in 1.4 so the fix doesn't
apply to 1.3.14+dfsg.1-1~deb10u1.  It might be possible to write a
targeted patch and convince the release team to accept it as a
stable-proposed-updates, but I personally don't plan to work on that.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#953205: Possibly fixed in Testing

[merkys]

On Fri, 15 May 2020 09:57:47 -0700 Soren Stoutner
 wrote:
> With the updates in Testing as of 5/15/20, this appears to no longer be 
> an issue (probably because of some updated dependency). Now it is the 
> opposite:  if `require "uri/generic"` is commented out, an error is 
> produced.  If it is not commented out, updates to Redmine work correctly.

So the issue seems to be caused by some dependency, not Redmine itself.
If so, could this issue be closed then?

Best,
Andrius

Processed: severity of 962952 is grave

[Debian Bug Tracking System]

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

> severity 962952 grave
Bug #962952 [azure-cli] azure-cli: exception when connecting to azure services
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#963010: [Pkg-roundcube-maintainers] Bug#963010: Acknowledgement (roundcube-core: roundcube upgrade keeps breaking my instance due to automatic permission changes of config.inc.php)

[Mirko Vogt]

On 6/17/20 5:23 PM, Guilhem Moulin wrote:
> On Wed, 17 Jun 2020 at 17:09:01 +0200, Mirko Vogt wrote:
> [..]
> (FWIW my “please use the Debian BTS” wasn't an invitation to file a bug
> in this case, but to query the BTS to check if the issue was already
> reported and/or fixed.)
> 

While I'm not interested in crashing another party without invitation:



The issue hit me once again tonight. Same result, same reason.




Can I do anything to push this being fixed or workaround this myself
without weakening my setup security wise? Thanks!

Bug#963761: node-node-sass: missing versioned dependency relation?: Sass could not find a binding for your current environment

[merkys]

On Fri, 26 Jun 2020 18:27:30 +0200 Paul Gevers  wrote:
> + grunt sass nodeunit
> Loading "gruntfile.js" tasks...ERROR
> >> Error: Missing binding
>
/usr/lib/x86_64-linux-gnu/nodejs/node-sass/vendor/linux-x64-72/binding.node
> >> Node Sass could not find a binding for your current environment:
> Linux 64-bit with Node.js 12.x
> >>
> >> Found bindings for the following environments:
> >>   - Linux 64-bit with Node.js 10.x

It seems as if node-node-sass was built with libnode < 72, and is now
being executed on machine also having libnode72. While in principle such
situations are possible, more than one libnodeX package are very
unlikely to be present. It would probably be worth stripping the
/linux-x64-72/ part from
/usr/lib/x86_64-linux-gnu/nodejs/node-sass/vendor/linux-x64-72/binding.node
and disabling the resolving mechanism altogether.

Best,
Andrius

Bug#964655: marked as done (healpy: FTBFS: healpy/src/_healpy_pixel_lib.cc:401:1: error: no matches converting function ‘ufunc_ang2pix’ to type ‘PyUFuncGenericFunction’ {aka ‘void (*)(char**, const lo

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 14:37:10 +
with message-id 
and subject line Bug#964655: fixed in healpy 1.13.0-2
has caused the Debian Bug report #964655,
regarding healpy: FTBFS: healpy/src/_healpy_pixel_lib.cc:401:1: error: no 
matches converting function ‘ufunc_ang2pix’ to type ‘PyUFuncGenericFunction’ 
{aka ‘void (*)(char**, const long int*, const long int*, void*)’}
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.)


-- 
964655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: healpy
Version: 1.13.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat 
> -Werror=format-security -g -fwrapv -O2 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/healpix_cxx -I/usr/include/python3.8 
> -I/usr/lib/python3/dist-packages/numpy/core/include -c 
> healpy/src/_healpy_pixel_lib.cc -o 
> build/temp.linux-x86_64-3.8/healpy/src/_healpy_pixel_lib.o -std=c++11 -fopenmp
> In file included from /usr/include/python3.8/numpy/ndarraytypes.h:1822,
>  from /usr/include/python3.8/numpy/ndarrayobject.h:12,
>  from /usr/include/python3.8/numpy/arrayobject.h:4,
>  from healpy/src/_healpy_pixel_lib.cc:34:
> /usr/include/python3.8/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning 
> "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API 
> NPY_1_7_API_VERSION" [-Wcpp]
>17 | #warning "Using deprecated NumPy API, disable it with " \
>   |  ^~~
> healpy/src/_healpy_pixel_lib.cc:401:1: error: no matches converting function 
> ‘ufunc_ang2pix’ to type ‘PyUFuncGenericFunction’ {aka ‘void (*)(char**, const 
> long int*, const long int*, void*)’}
>   401 | };
>   | ^
> healpy/src/_healpy_pixel_lib.cc:42:3: note: candidate is: 
> ‘template void ufunc_ang2pix(char**, 
> npy_intp*, npy_intp*, void*)’
>42 |   ufunc_ang2pix(char **args, npy_intp *dimensions, npy_intp *steps, 
> void *func)
>   |   ^
> healpy/src/_healpy_pixel_lib.cc:404:1: error: no matches converting function 
> ‘ufunc_ang2pix’ to type ‘PyUFuncGenericFunction’ {aka ‘void (*)(char**, const 
> long int*, const long int*, void*)’}
>   404 | };
>   | ^
> healpy/src/_healpy_pixel_lib.cc:42:3: note: candidate is: 
> ‘template void ufunc_ang2pix(char**, 
> npy_intp*, npy_intp*, void*)’
>42 |   ufunc_ang2pix(char **args, npy_intp *dimensions, npy_intp *steps, 
> void *func)
>   |   ^
> healpy/src/_healpy_pixel_lib.cc:407:1: error: no matches converting function 
> ‘ufunc_pix2ang’ to type ‘PyUFuncGenericFunction’ {aka ‘void (*)(char**, const 
> long int*, const long int*, void*)’}
>   407 | };
>   | ^
> healpy/src/_healpy_pixel_lib.cc:71:3: note: candidate is: 
> ‘template void ufunc_pix2ang(char**, 
> npy_intp*, npy_intp*, void*)’
>71 |   ufunc_pix2ang(char **args, npy_intp *dimensions, npy_intp *steps, 
> void *func)
>   |   ^
> healpy/src/_healpy_pixel_lib.cc:410:1: error: no matches converting function 
> ‘ufunc_pix2ang’ to type ‘PyUFuncGenericFunction’ {aka ‘void (*)(char**, const 
> long int*, const long int*, void*)’}
>   410 | };
>   | ^
> healpy/src/_healpy_pixel_lib.cc:71:3: note: candidate is: 
> ‘template void ufunc_pix2ang(char**, 
> npy_intp*, npy_intp*, void*)’
>71 |   ufunc_pix2ang(char **args, npy_intp *dimensions, npy_intp *steps, 
> void *func)
>   |   ^
> healpy/src/_healpy_pixel_lib.cc:413:1: error: no matches converting function 
> ‘ufunc_xyf2pix’ to type ‘PyUFuncGenericFunction’ {aka ‘void (*)(char**, const 
> long int*, const long int*, void*)’}
>   413 | };
>   | ^
> healpy/src/_healpy_pixel_lib.cc:100:3: note: candidate is: 
> ‘template void ufunc_xyf2pix(char**, 
> npy_intp*, npy_intp*, void*)’
>   100 |   ufunc_xyf2pix(char **args, npy_intp *dimensions, npy_intp *steps, 
> void *func)
>   |   ^
> healpy/src

Bug#962755: marked as done (exif: FTBFS on s390x: test failure)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 14:36:42 +
with message-id 
and subject line Bug#962755: fixed in exif 0.6.22-2
has caused the Debian Bug report #962755,
regarding exif: FTBFS on s390x: test failure
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.)


-- 
962755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: exif
Vresion: 0.6.22-1
Severity: serious
X-Debbugs-CC: hugh.mcmas...@outlook.com

Dear Debian exif package maintainers,

The new upload of exif/0.6.22-1 FTBFS on s390x architecture due to test
failure:

https://buildd.debian.org/status/fetch.php?pkg=exif=s390x=0.6.22-1=1591715266=0

PASS: check-create-tags.sh
PASS: check-help.sh
PASS: check-init-mandatory-tags.sh
FAIL: check-add-tags.sh
PASS: check-param-validity.sh
PASS: check-required-file.sh
PASS: check-show-description.sh
PASS: check-show-tag.sh
PASS: check-tag-description.sh
PASS: check-thumbnail.sh
PASS: check-version.sh
PASS: check-no-seek.sh

   libexif command line interface 0.6.22: test/test-suite.log


# TOTAL: 12
# PASS:  11
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

Can you examine it and eventually fix it, perhaps using a porterbox?

-- 
Regards,
Boyuan Yang



signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: exif
Source-Version: 0.6.22-2
Done: Hugh McMaster 

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

Debian distribution maintenance software
pp.
Hugh McMaster  (supplier of updated exif 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, 09 Jul 2020 20:58:17 +1000
Source: exif
Architecture: source
Version: 0.6.22-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Hugh McMaster 
Closes: 962755
Changes:
 exif (0.6.22-2) unstable; urgency=medium
 .
   * Add upstream patch to fix test failures on big endian systems
 (Closes: #962755).
Checksums-Sha1:
 318cf5564f4a3af98431269beb1afd820efa 1969 exif_0.6.22-2.dsc
 af221fc90c61540c5d16597fca22c75b75ffd735 6848 exif_0.6.22-2.debian.tar.xz
Checksums-Sha256:
 f274b271b81ead7ece4672e56e41782922cb72d60382c395ee306a7cdf65a859 1969 
exif_0.6.22-2.dsc
 d505f235a672cce442df47f199e6bc48240d8386fdd9e35ada6c84a6e6b35f65 6848 
exif_0.6.22-2.debian.tar.xz
Files:
 deba1d3010060b121b09389e2e585882 1969 graphics optional exif_0.6.22-2.dsc
 4eb8d42a29402df4b287f28db20ff4ab 6848 graphics optional 
exif_0.6.22-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZaEt9P4xrWusTXauM1X01jtYIcwFAl8HKiAACgkQM1X01jtY
IcwQNQ/8DQXBasCUdl5eKubObgm6luCT6YSs8ey3qp0hTRwDnNoMKgK4Ohp7rP9T
A1n7RhcAfk0LsTaJAX2hwfGzBl6U1ZfxF7BbLUeDKd+XHkQb0wJHTzW/YeOGX40v
x/E6aoW4PfrNeoUhS/tkbBJm1Dz2iw3jKeMAnMGDfZcZHuVwx441YiJXDmWt3swz
mCrXu7dxFNj9TocjPtTlqEatSnB9Qg4Scjaz1hQpVO19S2CW/dnuhrXCjzEceCw2
kjmpwG/dLvF5av/uZncPmhMif/8uzE1Co8c4bqBvAuthqvZh8AAM4rMAEkQ0vrGn
1f4mJn9jG1U4l2pj4hTLC7kNioR9fMujRspkUQidXL7YLf9o298v8Qq1Ee9g130I
QWq3M4Cpiu/KnBviqiL36Jlj60QZUMpQ5xCM42P5kKzq25zfl2LXgaUbSW7PHq0q
GM9+1Z4gFKs019PF7lMjGFYrhRzVSo3ed8Pdcu1q8vOWrQdq9rhoY/T4kPa5qV2D
uJZ6wu3Qp0H0EGoNBZ5e7URwclnYQUsR0SJJq54F502rSWYaAo1x1T9fgWoSrkQU
5rzclW8hCg+p4t7gZLTZffg9IhIwUaQqHvdSoTw1ZGC7Mo5+MPvSbnxyuWrBAfdR
jGzcR1o3FENp0nrk99jP8lxau8HSeqQ8QAigw7DLaKbSiiYDNqc=
=2P1h
-END PGP SIGNATURE End Message ---

Processed (with 2 errors): Merge duplicates and move to the correct packages

[Debian Bug Tracking System]

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

> reassign 961650 src:erlang-p1-eimp
Bug #961650 [erlang-p1-eimp] erlang-p1-eimp: FTBFS with Erlang 23
Bug reassigned from package 'erlang-p1-eimp' to 'src:erlang-p1-eimp'.
No longer marked as found in versions erlang-p1-eimp/1.0.14-1.
Ignoring request to alter fixed versions of bug #961650 to the same values 
previously set
> forcemerge 964615 961650
Bug #964615 [src:erlang-p1-eimp] erlang-p1-eimp: FTBFS: c_src/eimp.c:21:10: 
fatal error: erl_interface.h: No such file or directory
Bug #961650 [src:erlang-p1-eimp] erlang-p1-eimp: FTBFS with Erlang 23
Severity set to 'serious' from 'normal'
Marked as found in versions erlang-p1-eimp/1.0.14-1.
Added tag(s) bullseye, sid, and ftbfs.
Merged 961650 964615
> reassign 964618 ruby-aruba 1.0.2-1
Bug #964618 [src:ruby-mixlib-install] ruby-mixlib-install: FTBFS: ruby-aruba : 
Depends: ruby-thor (>= 1.0) but 0.20.3-2 is to be installed
Bug reassigned from package 'src:ruby-mixlib-install' to 'ruby-aruba'.
No longer marked as found in versions ruby-mixlib-install/3.11.7-1.
Ignoring request to alter fixed versions of bug #964618 to the same values 
previously set
Bug #964618 [ruby-aruba] ruby-mixlib-install: FTBFS: ruby-aruba : Depends: 
ruby-thor (>= 1.0) but 0.20.3-2 is to be installed
Marked as found in versions ruby-aruba/1.0.2-1.
> reassign 964629 ruby-aruba 1.0.2-1
Bug #964629 [src:ruby-cucumber-wire] ruby-cucumber-wire: FTBFS: ruby-aruba : 
Depends: ruby-thor (>= 1.0) but 0.20.3-2 is to be installed
Bug reassigned from package 'src:ruby-cucumber-wire' to 'ruby-aruba'.
No longer marked as found in versions ruby-cucumber-wire/0.0.1-3.
Ignoring request to alter fixed versions of bug #964629 to the same values 
previously set
Bug #964629 [ruby-aruba] ruby-cucumber-wire: FTBFS: ruby-aruba : Depends: 
ruby-thor (>= 1.0) but 0.20.3-2 is to be installed
Marked as found in versions ruby-aruba/1.0.2-1.
> reassign 964665 ruby-aruba 1.0.2-1
Bug #964665 [src:test-kitchen] test-kitchen: FTBFS: ruby-aruba : Depends: 
ruby-thor (>= 1.0) but 0.20.3-2 is to be installed
Bug reassigned from package 'src:test-kitchen' to 'ruby-aruba'.
No longer marked as found in versions test-kitchen/1.23.2-5.
Ignoring request to alter fixed versions of bug #964665 to the same values 
previously set
Bug #964665 [ruby-aruba] test-kitchen: FTBFS: ruby-aruba : Depends: ruby-thor 
(>= 1.0) but 0.20.3-2 is to be installed
Marked as found in versions ruby-aruba/1.0.2-1.
> reassign 964707 ruby-aruba 1.0.2-1
Bug #964707 [src:ruby-factory-girl] ruby-factory-girl: FTBFS: ruby-aruba : 
Depends: ruby-thor (>= 1.0) but 0.20.3-2 is to be installed
Bug reassigned from package 'src:ruby-factory-girl' to 'ruby-aruba'.
No longer marked as found in versions ruby-factory-girl/4.7.0-2.
Ignoring request to alter fixed versions of bug #964707 to the same values 
previously set
Bug #964707 [ruby-aruba] ruby-factory-girl: FTBFS: ruby-aruba : Depends: 
ruby-thor (>= 1.0) but 0.20.3-2 is to be installed
Marked as found in versions ruby-aruba/1.0.2-1.
> reassign 964708 ruby-aruba 1.0.2-1
Bug #964708 [src:ruby-rspec] ruby-rspec: FTBFS: ruby-aruba : Depends: ruby-thor 
(>= 1.0) but 0.20.3-2 is to be installed
Bug reassigned from package 'src:ruby-rspec' to 'ruby-aruba'.
No longer marked as found in versions ruby-rspec/3.9.0c1e0m1s2-1.
Ignoring request to alter fixed versions of bug #964708 to the same values 
previously set
Bug #964708 [ruby-aruba] ruby-rspec: FTBFS: ruby-aruba : Depends: ruby-thor (>= 
1.0) but 0.20.3-2 is to be installed
Marked as found in versions ruby-aruba/1.0.2-1.
> reassign 964709 ruby-aruba 1.0.2-1
Bug #964709 [src:ruby-appraisal] ruby-appraisal: FTBFS: ruby-aruba : Depends: 
ruby-thor (>= 1.0) but 0.20.3-2 is to be installed
Bug reassigned from package 'src:ruby-appraisal' to 'ruby-aruba'.
No longer marked as found in versions ruby-appraisal/0.5.1-2.
Ignoring request to alter fixed versions of bug #964709 to the same values 
previously set
Bug #964709 [ruby-aruba] ruby-appraisal: FTBFS: ruby-aruba : Depends: ruby-thor 
(>= 1.0) but 0.20.3-2 is to be installed
Marked as found in versions ruby-aruba/1.0.2-1.
> forcemerge 964618 964629 964665 964707 964708 964709
Bug #964618 [ruby-aruba] ruby-mixlib-install: FTBFS: ruby-aruba : Depends: 
ruby-thor (>= 1.0) but 0.20.3-2 is to be installed
Bug #964629 [ruby-aruba] ruby-cucumber-wire: FTBFS: ruby-aruba : Depends: 
ruby-thor (>= 1.0) but 0.20.3-2 is to be installed
Bug #964665 [ruby-aruba] test-kitchen: FTBFS: ruby-aruba : Depends: ruby-thor 
(>= 1.0) but 0.20.3-2 is to be installed
Bug #964707 [ruby-aruba] ruby-factory-girl: FTBFS: ruby-aruba : Depends: 
ruby-thor (>= 1.0) but 0.20.3-2 is to be installed
Bug #964708 [ruby-aruba] ruby-rspec: FTBFS: ruby-aruba : Depends: ruby-thor (>= 
1.0) but 0.20.3-2 is to be installed
Bug #964709 [ruby-aruba] ruby-appraisal: FTBFS: ruby-aruba : Depends: ruby-thor 
(>= 1.0) but 0.20.3-2 is to be installed
Merged 964618 964629 964665 964707 964708 964709
> retitle 964618 

Processed: affects 964678

[Debian Bug Tracking System]

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

> affects 964678 src:dictionaries-common
Bug #964678 [slice] wml/slice must depend on wml package
Added indication that 964678 affects src:dictionaries-common
> thanks
Stopping processing here.

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

Bug#964681: klibc: FTBFS: ld: cannot use executable file 'usr/klibc/libc.so' as input to a link (was Re: Bug#964681: klibc: FTBFS: ENOENT (2) => "No such file or directory")

[Thorsten Glaser]

retitle 964681 klibc: FTBFS: ld: cannot use executable file 'usr/klibc/libc.so' 
as input to a link
thanks

Lucas Nussbaum dixit:

>>   ld -m elf_x86_64 --build-id=sha1 -o usr/kinit/ipconfig/shared/ipconfig  -e 
>> main usr/klibc/interp.o --start-group  usr/kinit/ipconfig/main.o 
>> usr/kinit/ipconfig/netdev.o usr/kinit/ipconfig/packet.o 
>> usr/kinit/ipconfig/dhcp_proto.o usr/kinit/ipconfig/bootp_proto.o  -R 
>> usr/klibc/libc.so /usr/lib/gcc/x86_64-linux-gnu/9/libgcc.a --end-group ; cp 
>> -f usr/kinit/ipconfig/shared/ipconfig usr/kinit/ipconfig/shared/ipconfig.g ; 
>> true --strip-all -R .comment -R .note --strip-all -R .comment -R .note 
>> --strip-all -R .comment -R .note usr/kinit/ipconfig/shared/ipconfig
>> ld: cannot use executable file 'usr/klibc/libc.so' as input to a link

This seems to be the real error.

bye,
//mirabilos
-- 
 you introduced a merge commit│ % g rebase -i HEAD^^
 sorry, no idea and rebasing just fscked │ Segmentation
 should have cloned into a clean repo  │  fault (core dumped)
 if I rebase that now, it's really ugh │ wuahh

Processed: klibc: FTBFS: ld: cannot use executable file 'usr/klibc/libc.so' as input to a link (was Re: Bug#964681: klibc: FTBFS: ENOENT (2) => "No such file or directory")

[Debian Bug Tracking System]

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

> retitle 964681 klibc: FTBFS: ld: cannot use executable file 
> 'usr/klibc/libc.so' as input to a link
Bug #964681 [src:klibc] klibc: FTBFS: ENOENT (2) => "No such file or directory"
Changed Bug title to 'klibc: FTBFS: ld: cannot use executable file 
'usr/klibc/libc.so' as input to a link' from 'klibc: FTBFS: ENOENT (2) => "No 
such file or directory"'.
> thanks
Stopping processing here.

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

Bug#964334: crashes in latest chromium

[Riku Voipio]

This should fix it:

https://salsa.debian.org/chromium-team/chromium/-/commit/b904fa41d40b967dcc8f6984db52f7a2f6a2c83d

We are not building with GCC but this seems to be exactly the place where the 
crash happens.
chromium built with this patch has not crashed for the last few hours for me, 
while before it would
crash in a few minutes.

Riku

Processed: severity of 964038 is serious

[Debian Bug Tracking System]

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

> severity 964038 serious
Bug #964038 [rabbitmq-server] rabbitmq-server: Prometheus plugin doesn't 
support Erlang v23
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: Re: Bug#964641: musescore: FTBFS: qmetatype.h:818:16: error: ambiguous overload for ‘operator<<’ (operand types are ‘QDataStream’ and ‘const Ms::SessionStart’)

[Debian Bug Tracking System]

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

> tags 964641 + confirmed pending
Bug #964641 [src:musescore] musescore: FTBFS: qmetatype.h:818:16: error: 
ambiguous overload for ‘operator<<’ (operand types are ‘QDataStream’ and ‘const 
Ms::SessionStart’)
Added tag(s) pending and confirmed.
> thanks
Stopping processing here.

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

Bug#964641: musescore: FTBFS: qmetatype.h:818:16: error: ambiguous overload for ‘operator<<’ (operand types are ‘QDataStream’ and ‘const Ms::SessionStart’)

[Thorsten Glaser]

tags 964641 + confirmed pending
thanks

Lucas Nussbaum dixit:

>During a rebuild of all packages in sid, your package failed to build

Indeed, I’ve got patches for Qt 5.14 compatibility queued but hadn’t
had enough tuits to prepare an upload yet. I’ll do that soonish.

Thanks,
//mirabilos
-- 
15:39⎜«mika:#grml» mira|AO: "mit XFree86® wär’ das nicht passiert" - muhaha
15:48⎜ also warum machen die xorg Jungs eigentlich alles
kaputt? :)15:49⎜ thkoehler: weil sie als Kinder nie den
gebauten Turm selber umschmeissen durften?  -- ~/.Xmodmap wonders…

Bug#964591: kodi FTBFS with libmicrohttpd 0.9.71

[Vasyl Gello]

Control: owner -1 =

Hi Adrian!

This bug was already reported upstream by Gentoo maintainer Chris Andrews:

https://github.com/xbmc/xbmc/pull/18131

I will notify the upstream that Leia is also affected so once the fix is merged 
to master, there will be Leia backport closing this bug.

-- 
Vasyl Gello
==
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.ge...@gmail.com

Skype: vasek.gello
==
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

signature.asc
Description: PGP signature

Processed: Re: Bug#964678: dictionaries-common: FTBFS: Can't locate TheWML/Backends/Slice/Main.pm in @INC

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + dictionaries-common
Bug #964678 [slice] wml/slice must depend on wml package
Added indication that 964678 affects dictionaries-common

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

Bug#964678: dictionaries-common: FTBFS: Can't locate TheWML/Backends/Slice/Main.pm in @INC

[Axel Beckert]

Control: affects -1 + dictionaries-common

Hi,

Agustin Martin wrote:
> This seems due to new slice package built from wml missing a
> dependency on wml. Reassigning

Thanks for reassigning!

It probably is no missing dependency but not properly distributed
files over the two generated binary packages. Unfortunately I haven't
yet an autopkgtest which tests slice separately.

Will have a closer look later today and try to make a slice-only
autopkgtest, too.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: your mail

[Debian Bug Tracking System]

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

> affects 964309 - javahelper
Bug #964309 [bsdmainutils] bsdmainutils: FTBFS because of missing 
libncurses-dev dependency
Removed indication that 964309 affects javahelper
>
End of message, stopping processing here.

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

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> tag 964309  - javahelper
Unknown tag/s: javahelper.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore bookworm bookworm-ignore.

Bug #964309 [bsdmainutils] bsdmainutils: FTBFS because of missing 
libncurses-dev dependency
Requested to remove no tags; doing nothing.
>
End of message, stopping processing here.

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

Bug#963764: marked as done (node-node-sass: uses embedded old security-buggy libsass)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 12:34:07 +
with message-id 
and subject line Bug#963764: fixed in node-node-sass 
4.14.1+git20200512.e1fc158+dfsg-1
has caused the Debian Bug report #963764,
regarding node-node-sass: uses embedded old security-buggy libsass
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.)


-- 
963764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-node-sass
Version: 4.13.1-2
Severity: serious
Tags: security

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

node-node-sass ships with an old release of libsass.

Since Debian release 4.13.1-2 this is explicitly used
(uncertain if previously it might alos accidentally be used).

Libsass has a series of known security flaws:
https://security-tracker.debian.org/tracker/source-package/libsass

The Debian package libsass is itself badly maintained regarding these
seciruty issues, but at least it is kept up-to-date with upstream,
meaning that _maybe_ they fixed all the issues:
https://bugs.debian.org/921952

Knowingly using older releases of libsass is unacceptable, and should
not be included in a stable release of Debian.


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl72LQAACgkQLHwxRsGg
ASG/fQ//WyKH6E3fW9fAndVJxR/2OcmE30JdTQpk69558VM8Qs/Vdr9JqLDVKuw0
I+K8LSQmsL4d39WsSGrWkZeqGFGOeIyAJ2y9GZi1uskRpNnA8/gJs3ZmIUY7yEWe
NloVaQE2KPUq4EdJnPWtDNDkObmZgtk0H8WtSfr7IHL/CctTBYZ3VImEz2NDoLjn
5i2SjZV2ypdYzlMWDvG6tksDKu6Ttcmy6PH78ibTFPHcMMBtD6mZ8e8TQjPb50WI
+lt8slQIRN791iM6f+6FoFtPRPAN+kAA6QqM0XJr7jO3qIqPAXtJpQLaRPEHozMu
8UTosXk1tRfkqhixB7JBmwRpCvmC90FPCIeAyYKIEoHO6Q0qdQW7RbHfzoEQIRwz
kDzI6E3eUgxsk9UsIQ2xqHnxL+iun5qQC3jnwWQvZiqU4KUwxVB/kYk5FPSlOTmC
Jb1UpgO1g3rFc8xYTB1ZHCbkGKTru3GsrdmmUJiweMhpo1SRheRdLNiMy90T3AdA
tZ2EZA6+W69LHdKmBDbDT4aHhx7PzKYjHhZAhzUvCStqoH44HKbvf2voAP7AFppp
bf8JmZ0ACbIhlQxjHSsav9SeYc28/tj4B7CFIPHZ+dbX6USn/DSSkvWjGxH93huq
cSqeo8ssV8beQLpeBtwLqf5IVJ0Kp6iW9e2I3MsUyDN2k76ttxw=
=yvR9
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: node-node-sass
Source-Version: 4.14.1+git20200512.e1fc158+dfsg-1
Done: Andrius Merkys 

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

Debian distribution maintenance software
pp.
Andrius Merkys  (supplier of updated node-node-sass 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, 09 Jul 2020 08:14:41 -0400
Source: node-node-sass
Architecture: source
Version: 4.14.1+git20200512.e1fc158+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Andrius Merkys 
Closes: 963764
Changes:
 node-node-sass (4.14.1+git20200512.e1fc158+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Andrius Merkys ]
   * New upstream version 4.14.1+git20200512.e1fc158+dfsg
   * Excluding src/libsass, linking against system-provided libsass
 (Closes: #963764)
   * Ignoring failing test case
 .
   [ Nilesh Patra ]
   * Add compression parameter
Checksums-Sha1:
 abcf2558ac9f077cb6c5e6b71aff678b9993e2c0 6081 
node-node-sass_4.14.1+git20200512.e1fc158+dfsg-1.dsc
 f553376304548d0d0fa22b499db45b05a2a4a02c 4456 
node-node-sass_4.14.1+git20200512.e1fc158+dfsg.orig-async-foreach.tar.xz
 77600796d1d4c7f7ee5d4b8a2e3d0581c0a2345b 8416 
node-node-sass_4.14.1+git20200512.e1fc158+dfsg.orig-gaze.tar.xz
 39d50fddd9fd95e87c863bf931c67586c8a73e48 1020 
node-node-sass_4.14.1+git20200512.e1fc158+dfsg.orig-get-stdin.tar.xz
 1e304ec59d888eb1a4adbdc0d60b4fd641a632f4 34868 
node-node-sass_4.14.1+git20200512.e1fc158+dfsg.orig-js-base64.tar.xz
 ed9607fc2564da144b4f49d8544bbc873fcb3123 4992 
node-node-sass_4.14.1+git20200512.e1fc158+dfsg.orig-sass-graph.tar.xz
 1098ece6a9cc1c3740e5fcd9b0234ba5d65e9af8 884032 
node-node-sass_4.14.1+git20200512.e1fc158+dfsg.orig-sass-spec.tar.xz
 4ab0170821bed4a0f1e0cc3feb23481dd2e4b034 5920 
node-node-sass_4.14.1+git20200512.e1fc158+dfsg.orig-scss-tokenizer.tar.xz
 d49d514f186bc1cca52731e8faa0c5e259730823 2368 

Processed: Re: Bug#964678: dictionaries-common: FTBFS: Can't locate TheWML/Backends/Slice/Main.pm in @INC

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 slice
Bug #964678 [src:dictionaries-common] dictionaries-common: FTBFS: Can't locate 
TheWML/Backends/Slice/Main.pm in @INC
Bug reassigned from package 'src:dictionaries-common' to 'slice'.
No longer marked as found in versions dictionaries-common/1.28.1.
Ignoring request to alter fixed versions of bug #964678 to the same values 
previously set
> found -1 2.28.0~ds1-1
Bug #964678 [slice] dictionaries-common: FTBFS: Can't locate 
TheWML/Backends/Slice/Main.pm in @INC
Marked as found in versions wml/2.28.0~ds1-1.
> retitle -1 wml/slice must depend on wml package
Bug #964678 [slice] dictionaries-common: FTBFS: Can't locate 
TheWML/Backends/Slice/Main.pm in @INC
Changed Bug title to 'wml/slice must depend on wml package' from 
'dictionaries-common: FTBFS: Can't locate TheWML/Backends/Slice/Main.pm in 
@INC'.

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

Bug#964678: dictionaries-common: FTBFS: Can't locate TheWML/Backends/Slice/Main.pm in @INC

[Agustin Martin]

control: reassign -1 slice
control: found -1 2.28.0~ds1-1
control: retitle -1 wml/slice must depend on wml package

El jue., 9 jul. 2020 a las 13:36, Lucas Nussbaum () escribió:
>
> Source: dictionaries-common
> Version: 1.28.1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200709 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

This seems due to new slice package built from wml missing a
dependency on wml. Reassigning

> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > slice -oUNDEF+I+IW+IA-A-H-W-AH:scripts/maintainer/config-ispell 
> > scripts/maintainer/config.in
> > Can't locate TheWML/Backends/Slice/Main.pm in @INC (you may need to install 
> > the TheWML::Backends::Slice::Main module) (@INC contains: /usr/share/wml 
> > /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.3 
> > /usr/local/share/perl/5.30.3 /usr/lib/x86_64-linux-gnu/perl5/5.30 
> > /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base 
> > /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 
> > /usr/local/lib/site_perl) at /usr/bin/slice line 10.
> > BEGIN failed--compilation aborted at /usr/bin/slice line 10.
> > make[1]: *** [Makefile:147: scripts/maintainer/config-ispell] Error 2
>
> The full build log is available from:
>
> http://qa-logs.debian.net/2020/07/09/dictionaries-common_1.28.1_unstable.log
>
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.

Bug#964703: marked as done (libkiwix: FTBFS: ../src/server.cpp:248:29: error: invalid conversion from ‘int (*)(void*, MHD_Connection*, const char*, const char*, const char*, const char*, size_t*, void

[Debian Bug Tracking System]

Your message dated Thu, 9 Jul 2020 05:10:01 -0700
with message-id <7eb56057-1327-0166-74eb-9d35befa0...@debian.org>
and subject line Re: Bug#964703: libkiwix: FTBFS: ../src/server.cpp:248:29: 
error: invalid conversion from ‘int (*)(void*, MHD_Connection*, const char*, 
const char*, const char*, const char*, size_t*, void**)’ {aka ‘int (*)(void*, 
MHD_Connection*, const char*, const char*, const char*, const char*, long 
unsigned int*, void**)’} to ‘MHD_AccessHandlerCallback’ {aka ‘MHD_Result 
(*)(void*, MHD_Connection*, const char*, const char*, const char*, const char*, 
long unsigned int*, void**)’} [-fpermissive]
has caused the Debian Bug report #964703,
regarding libkiwix: FTBFS: ../src/server.cpp:248:29: error: invalid conversion 
from ‘int (*)(void*, MHD_Connection*, const char*, const char*, const char*, 
const char*, size_t*, void**)’ {aka ‘int (*)(void*, MHD_Connection*, const 
char*, const char*, const char*, const char*, long unsigned int*, void**)’} to 
‘MHD_AccessHandlerCallback’ {aka ‘MHD_Result (*)(void*, MHD_Connection*, const 
char*, const char*, const char*, const char*, long unsigned int*, void**)’} 
[-fpermissive]
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.)


-- 
964703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libkiwix
Version: 9.2.2+dfsg-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> c++ -Isrc/25a6634@@kiwix@sha -Isrc -I../src -Iinclude -I../include 
> -I/usr/include/kainjow -Istatic -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/p11-kit-1 -fdiagnostics-color=always -pipe 
> -D_FILE_OFFSET_BITS=64 -Werror -std=c++11 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD 
> -MQ 'src/25a6634@@kiwix@sha/server.cpp.o' -MF 
> 'src/25a6634@@kiwix@sha/server.cpp.o.d' -o 
> 'src/25a6634@@kiwix@sha/server.cpp.o' -c ../src/server.cpp
> ../src/server.cpp: In member function ‘bool kiwix::InternalServer::start()’:
> ../src/server.cpp:248:29: error: invalid conversion from ‘int (*)(void*, 
> MHD_Connection*, const char*, const char*, const char*, const char*, size_t*, 
> void**)’ {aka ‘int (*)(void*, MHD_Connection*, const char*, const char*, 
> const char*, const char*, long unsigned int*, void**)’} to 
> ‘MHD_AccessHandlerCallback’ {aka ‘MHD_Result (*)(void*, MHD_Connection*, 
> const char*, const char*, const char*, const char*, long unsigned int*, 
> void**)’} [-fpermissive]
>   248 | ,
>   | ^~
>   | |
>   | int (*)(void*, MHD_Connection*, const 
> char*, const char*, const char*, const char*, size_t*, void**) {aka int 
> (*)(void*, MHD_Connection*, const char*, const char*, const char*, const 
> char*, long unsigned int*, void**)}
> In file included from ../src/server.cpp:39:
> /usr/include/microhttpd.h:2428:45: note:   initializing argument 5 of 
> ‘MHD_Daemon* MHD_start_daemon(unsigned int, uint16_t, 
> MHD_AcceptPolicyCallback, void*, MHD_AccessHandlerCallback, void*, ...)’
>  2428 |   MHD_AccessHandlerCallback dh, void *dh_cls,
>   |   ~~^~
> [13/51] c++ -Isrc/25a6634@@kiwix@sha -Isrc -I../src -Iinclude -I../include 
> -I/usr/include/kainjow -Istatic -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/p11-kit-1 -fdiagnostics-color=always -pipe 
> -D_FILE_OFFSET_BITS=64 -Werror -std=c++11 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD 
> -MQ 'src/25a6634@@kiwix@sha/downloader.cpp.o' -MF 
> 'src/25a6634@@kiwix@sha/downloader.cpp.o.d' -o 
> 'src/25a6634@@kiwix@sha/downloader.cpp.o' -c ../src/downloader.cpp
> [14/51] c++ -Isrc/25a6634@@kiwix@sha -Isrc -I../src -Iinclude -I../include 
> -I/usr/include/kainjow -Istatic -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/p11-kit-1 -fdiagnostics-color=always -pipe 
> -D_FILE_OFFSET_BITS=64 -Werror -std=c++11 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOU

Processed: Re: Bug#964703: libkiwix: FTBFS: ../src/server.cpp:248:29: error: invalid conversion from ‘int (*)(void*, MHD_Connection*, const char*, const char*, const char*, const char*, size_t*, void*

[Debian Bug Tracking System]

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

> fixed 964703 9.3.0+dfsg-1
Bug #964703 [src:libkiwix] libkiwix: FTBFS: ../src/server.cpp:248:29: error: 
invalid conversion from ‘int (*)(void*, MHD_Connection*, const char*, const 
char*, const char*, const char*, size_t*, void**)’ {aka ‘int (*)(void*, 
MHD_Connection*, const char*, const char*, const char*, const char*, long 
unsigned int*, void**)’} to ‘MHD_AccessHandlerCallback’ {aka ‘MHD_Result 
(*)(void*, MHD_Connection*, const char*, const char*, const char*, const char*, 
long unsigned int*, void**)’} [-fpermissive]
Marked as fixed in versions libkiwix/9.3.0+dfsg-1.
> thanks
Stopping processing here.

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

Bug#947566: marked as done (FTBFS with scons 3.1.2-1)

[Debian Bug Tracking System]

Your message dated Thu, 9 Jul 2020 22:03:10 +1000
with message-id 

and subject line FTBFS with scons 3.1.2-1
has caused the Debian Bug report #947566,
regarding FTBFS with scons 3.1.2-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.)


-- 
947566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: klick
Version: 0.12.2-4
Severity: important
Usertags: scons_ftbfs


Hello, 

in the context of the change to Python3 also Scons was revised. With
the current version 3.1.2-1 from Experimental the changeover is
finished so far. 

However, an error occurred while building your package. The build log
is attached.

Please check it and fix the error.

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.

dpkg-checkbuilddeps: error: Unmet build dependencies: libboost-dev libjack-dev 
libsndfile1-dev (>= 1.0.18) libsamplerate0-dev liblo-dev librubberband-dev
W: Unmet build-dependency in source
dh clean
   debian/rules override_dh_auto_clean
make[1]: Entering directory 
'/data/entwicklung/linux/debian/trans_scons/klick-0.12.2'
[ !  -ne 1 ] || scons --warn=no-deprecated -c
/bin/sh: 1: [: Illegal number: !
scons: Reading SConscript files ...
NameError: name 'Options' is not defined:
  File "/data/entwicklung/linux/debian/trans_scons/klick-0.12.2/SConstruct", 
line 15:
opts = Options('scache.conf')
make[1]: *** [debian/rules:16: override_dh_auto_clean] Error 2
make[1]: Leaving directory 
'/data/entwicklung/linux/debian/trans_scons/klick-0.12.2'
make: *** [debian/rules:10: clean] Error 2


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Control: fixed -1 0.12.2-4.1

Thanks to:
- Reiner Herrmann for supplying a patch
- Matthias Klose for uploading the NMU.--- End Message ---

Processed: forcibly merging 964705 962886

[Debian Bug Tracking System]

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

> forcemerge 964705 962886
Bug #964705 [src:zoneminder] zoneminder: FTBFS: build-dependency not 
installable: fonts-glewlwyd
Bug #962886 [src:zoneminder] zoneminder: should depend on fonts-font-awesome 
and/or fonts-glyphicons-halflings (not fonts-glewlwyd)
962875 was blocked by: 962877 962887 962881 962886 962876 962885 962880 962882 
962884 962883 962878 962879
962875 was not blocking any bugs.
Removed blocking bug(s) of 962875: 962886
Added tag(s) ftbfs, sid, and bullseye.
Merged 962886 964705
> thanks
Stopping processing here.

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

Processed: Re: Bug#964318: gosa login broken with PHP 7.4

[Debian Bug Tracking System]

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

> severity 964318 grave
Bug #964318 [gosa] password encryption/decryption broken with PHP 7.4
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#964045: marked as done (golang-github-shirou-gopsutil: FTBFS: Test_Process_memory_maps failure)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jul 2020 11:48:34 +
with message-id 
and subject line Bug#964045: fixed in golang-github-shirou-gopsutil 2.19.11-2
has caused the Debian Bug report #964045,
regarding golang-github-shirou-gopsutil: FTBFS: Test_Process_memory_maps failure
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.)


-- 
964045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-shirou-gopsutil
Version: 2.19.11-1
Severity: serious
Tags: ftbfs

This package fails to build from source on current sid.

>From my build log:

   === RUN   Test_SendSignal
   --- PASS: Test_SendSignal (0.00s)
   === RUN   Test_Pids
   --- PASS: Test_Pids (0.00s)
   === RUN   Test_Pids_Fail
   Test_Pids_Fail: process_test.go:48: darwin only
   --- SKIP: Test_Pids_Fail (0.00s)
   === RUN   Test_Pid_exists
   --- PASS: Test_Pid_exists (0.00s)
   === RUN   Test_NewProcess
   --- PASS: Test_NewProcess (0.00s)
   === RUN   Test_Process_memory_maps
   Test_Process_memory_maps: process_test.go:114: memory map get error 
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
   Test_Process_memory_maps: process_test.go:114: memory map get error 
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
   Test_Process_memory_maps: process_test.go:114: memory map get error 
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
   Test_Process_memory_maps: process_test.go:114: memory map get error 
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
   Test_Process_memory_maps: process_test.go:114: memory map get error 
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
   Test_Process_memory_maps: process_test.go:114: memory map get error 
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
   Test_Process_memory_maps: process_test.go:114: memory map get error 
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
   Test_Process_memory_maps: process_test.go:114: memory map get error 
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
   Test_Process_memory_maps: process_test.go:114: memory map get error 
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
   Test_Process_memory_maps: process_test.go:114: memory map get error 
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
   Test_Process_memory_maps: process_test.go:114: memory map get error 
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
   Test_Process_memory_maps: process_test.go:114: memory map get error 
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
   Test_Process_memory_maps: process_test.go:114: memory map get error 
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
   Test_Process_memory_maps: process_test.go:114: memory map get error 
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
   Test_Process_memory_maps: process_test.go:114: memory map get error 
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
   Test_Process_memory_maps: process_test.go:114: memory map get error 
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
   Test_Process_memory_maps: process_test.go:114: memory map get error 

Bug#964708: ruby-rspec: FTBFS: ruby-aruba : Depends: ruby-thor (>= 1.0) but 0.20.3-2 is to be installed

[Lucas Nussbaum]

Source: ruby-rspec
Version: 3.9.0c1e0m1s2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: coderay, debhelper-compat (= 12), gem2deb (>= 1), git, 
> ruby-aruba, ruby-childprocess, ruby-diff-lcs, ruby-fakefs, ruby-flexmock, 
> ruby-json, ruby-minitest, ruby-mocha, ruby-nokogiri, ruby-rr, 
> ruby-thread-order, build-essential, fakeroot
> Filtered Build-Depends: coderay, debhelper-compat (= 12), gem2deb (>= 1), 
> git, ruby-aruba, ruby-childprocess, ruby-diff-lcs, ruby-fakefs, 
> ruby-flexmock, ruby-json, ruby-minitest, ruby-mocha, ruby-nokogiri, ruby-rr, 
> ruby-thread-order, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [458 B]
> Get:5 copy:/<>/apt_archive ./ Packages [544 B]
> Fetched 1959 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  ruby-aruba : Depends: ruby-thor (>= 1.0) but 0.20.3-2 is to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/ruby-rspec_3.9.0c1e0m1s2-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#964705: zoneminder: FTBFS: build-dependency not installable: fonts-glewlwyd

[Lucas Nussbaum]

Source: zoneminder
Version: 1.34.16-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 12), dh-linktree, apache2-dev, 
> cmake, default-libmysqlclient-dev, libavcodec-dev (>= 6:10~), libavdevice-dev 
> (>= 6:10~), libavformat-dev (>= 6:10~), libavresample-dev, libavutil-dev (>= 
> 6:10~), libbz2-dev, libcurl4-gnutls-dev, libdate-manip-perl, 
> libdbd-mysql-perl, libgcrypt-dev, libjpeg-dev, libjwt-gnutls-dev, 
> libpcre3-dev, libphp-serialization-perl, libpolkit-gobject-1-dev, 
> libswscale-dev (>= 6:10~), libsys-mmap-perl, libv4l-dev (>= 0.8.3), 
> libvlc-dev, libwww-perl, libx264-dev, python3-sphinx, fonts-glewlwyd, 
> build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 12), dh-linktree, apache2-dev, 
> cmake, default-libmysqlclient-dev, libavcodec-dev (>= 6:10~), libavdevice-dev 
> (>= 6:10~), libavformat-dev (>= 6:10~), libavresample-dev, libavutil-dev (>= 
> 6:10~), libbz2-dev, libcurl4-gnutls-dev, libdate-manip-perl, 
> libdbd-mysql-perl, libgcrypt-dev, libjpeg-dev, libjwt-gnutls-dev, 
> libpcre3-dev, libphp-serialization-perl, libpolkit-gobject-1-dev, 
> libswscale-dev (>= 6:10~), libsys-mmap-perl, libv4l-dev (>= 0.8.3), 
> libvlc-dev, libwww-perl, libx264-dev, python3-sphinx, fonts-glewlwyd, 
> build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [610 B]
> Get:5 copy:/<>/apt_archive ./ Packages [677 B]
> Fetched 2250 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: fonts-glewlwyd but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/zoneminder_1.34.16-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#964704: openjdk-11: FTBFS: tar: Cowardly refusing to create an empty archive

[Lucas Nussbaum]

Source: openjdk-11
Version: 11.0.7+10-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> BEGIN jtreg-summary-hotspot
> cat jtreg-test-output/jtreg-summary-hotspot.log
> --- jtreg console summary for hotspot ---
> Cannot determine JTREG_HOME; please set it explicitly
> [debian/tests/jtreg-autopkgtest.sh] nothing to cleanup
> [debian/tests/jtreg-autopkgtest.sh] nothing to cleanup
> Unable to compare jtreg results: no build jtreport found for hotspot/amd64.
> Reason: 
> '/usr/share/doc/openjdk-11-jre-headless//test-amd64/jtreport-hotspot.tar.gz' 
> does not exist.
> --- jtreg console summary for langtools ---
> Cannot determine JTREG_HOME; please set it explicitly
> [debian/tests/jtreg-autopkgtest.sh] nothing to cleanup
> [debian/tests/jtreg-autopkgtest.sh] nothing to cleanup
> Unable to compare jtreg results: no build jtreport found for hotspot/amd64.
> Reason: 
> '/usr/share/doc/openjdk-11-jre-headless//test-amd64/jtreport-hotspot.tar.gz' 
> does not exist.
> --- jtreg console summary for jaxp ---
> Cannot determine JTREG_HOME; please set it explicitly
> [debian/tests/jtreg-autopkgtest.sh] nothing to cleanup
> [debian/tests/jtreg-autopkgtest.sh] nothing to cleanup
> Unable to compare jtreg results: no build jtreport found for hotspot/amd64.
> Reason: 
> '/usr/share/doc/openjdk-11-jre-headless//test-amd64/jtreport-hotspot.tar.gz' 
> does not exist.
> --- jtreg console summary for jdk ---
> Cannot determine JTREG_HOME; please set it explicitly
> [debian/tests/jtreg-autopkgtest.sh] nothing to cleanup
> [debian/tests/jtreg-autopkgtest.sh] nothing to cleanup
> Unable to compare jtreg results: no build jtreport found for hotspot/amd64.
> Reason: 
> '/usr/share/doc/openjdk-11-jre-headless//test-amd64/jtreport-hotspot.tar.gz' 
> does not exist.
> END jtreg-summary-hotspot
> for i in hotspot langtools jaxp jdk; do \
>   find jtreg-test-output/$i/JTwork/ -name '*.jtr'; \
> done | sort -u > jtreg-test-output/failed_tests-hotspot.list; \
> GZIP=-9vn tar --ignore-failed-read -C . -c -z -f 
> jtreg-test-output/failed_tests-hotspot.tar.gz -T 
> jtreg-test-output/failed_tests-hotspot.list
> find: 'jtreg-test-output/hotspot/JTwork/': No such file or directory
> find: 'jtreg-test-output/langtools/JTwork/': No such file or directory
> find: 'jtreg-test-output/jaxp/JTwork/': No such file or directory
> find: 'jtreg-test-output/jdk/JTwork/': No such file or directory
> gzip: warning: GZIP environment variable is deprecated; use an alias or script
>  99.7%
> GZIP=-9vn tar -C . -c -z -f jtreg-test-output/jtreport-hotspot.tar.gz $(find 
> jtreg-test-output -name JTreport)
> tar: Cowardly refusing to create an empty archive
> Try 'tar --help' or 'tar --usage' for more information.
> make[1]: *** [debian/rules:1065: jtreg-run-check] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/openjdk-11_11.0.7+10-3_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#964703: libkiwix: FTBFS: ../src/server.cpp:248:29: error: invalid conversion from ‘int (*)(void*, MHD_Connection*, const char*, const char*, const char*, const char*, size_t*, void**)’ {aka ‘int (

[Lucas Nussbaum]

Source: libkiwix
Version: 9.2.2+dfsg-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> c++ -Isrc/25a6634@@kiwix@sha -Isrc -I../src -Iinclude -I../include 
> -I/usr/include/kainjow -Istatic -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/p11-kit-1 -fdiagnostics-color=always -pipe 
> -D_FILE_OFFSET_BITS=64 -Werror -std=c++11 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD 
> -MQ 'src/25a6634@@kiwix@sha/server.cpp.o' -MF 
> 'src/25a6634@@kiwix@sha/server.cpp.o.d' -o 
> 'src/25a6634@@kiwix@sha/server.cpp.o' -c ../src/server.cpp
> ../src/server.cpp: In member function ‘bool kiwix::InternalServer::start()’:
> ../src/server.cpp:248:29: error: invalid conversion from ‘int (*)(void*, 
> MHD_Connection*, const char*, const char*, const char*, const char*, size_t*, 
> void**)’ {aka ‘int (*)(void*, MHD_Connection*, const char*, const char*, 
> const char*, const char*, long unsigned int*, void**)’} to 
> ‘MHD_AccessHandlerCallback’ {aka ‘MHD_Result (*)(void*, MHD_Connection*, 
> const char*, const char*, const char*, const char*, long unsigned int*, 
> void**)’} [-fpermissive]
>   248 | ,
>   | ^~
>   | |
>   | int (*)(void*, MHD_Connection*, const 
> char*, const char*, const char*, const char*, size_t*, void**) {aka int 
> (*)(void*, MHD_Connection*, const char*, const char*, const char*, const 
> char*, long unsigned int*, void**)}
> In file included from ../src/server.cpp:39:
> /usr/include/microhttpd.h:2428:45: note:   initializing argument 5 of 
> ‘MHD_Daemon* MHD_start_daemon(unsigned int, uint16_t, 
> MHD_AcceptPolicyCallback, void*, MHD_AccessHandlerCallback, void*, ...)’
>  2428 |   MHD_AccessHandlerCallback dh, void *dh_cls,
>   |   ~~^~
> [13/51] c++ -Isrc/25a6634@@kiwix@sha -Isrc -I../src -Iinclude -I../include 
> -I/usr/include/kainjow -Istatic -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/p11-kit-1 -fdiagnostics-color=always -pipe 
> -D_FILE_OFFSET_BITS=64 -Werror -std=c++11 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD 
> -MQ 'src/25a6634@@kiwix@sha/downloader.cpp.o' -MF 
> 'src/25a6634@@kiwix@sha/downloader.cpp.o.d' -o 
> 'src/25a6634@@kiwix@sha/downloader.cpp.o' -c ../src/downloader.cpp
> [14/51] c++ -Isrc/25a6634@@kiwix@sha -Isrc -I../src -Iinclude -I../include 
> -I/usr/include/kainjow -Istatic -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/p11-kit-1 -fdiagnostics-color=always -pipe 
> -D_FILE_OFFSET_BITS=64 -Werror -std=c++11 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD 
> -MQ 'src/25a6634@@kiwix@sha/reader.cpp.o' -MF 
> 'src/25a6634@@kiwix@sha/reader.cpp.o.d' -o 
> 'src/25a6634@@kiwix@sha/reader.cpp.o' -c ../src/reader.cpp
> [15/51] c++ -Isrc/25a6634@@kiwix@sha -Isrc -I../src -Iinclude -I../include 
> -I/usr/include/kainjow -Istatic -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/p11-kit-1 -fdiagnostics-color=always -pipe 
> -D_FILE_OFFSET_BITS=64 -Werror -std=c++11 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD 
> -MQ 'src/25a6634@@kiwix@sha/library.cpp.o' -MF 
> 'src/25a6634@@kiwix@sha/library.cpp.o.d' -o 
> 'src/25a6634@@kiwix@sha/library.cpp.o' -c ../src/library.cpp
> ninja: build stopped: subcommand failed.
> dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v 
> returned exit code 1
> make: *** [debian/rules:5: binary] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/libkiwix_9.2.2+dfsg-3_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#964710: abinit: FTBFS: /usr/bin/env: ‘python’: No such file or directory

[Lucas Nussbaum]

Source: abinit
Version: 8.10.3-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build
>debian/rules override_dh_autoreconf
> make[1]: Entering directory '/<>'
> config/scripts/makemake
> /usr/bin/env: ‘python’: No such file or directory
> make[1]: *** [debian/rules:33: override_dh_autoreconf] Error 127

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/abinit_8.10.3-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#964707: ruby-factory-girl: FTBFS: ruby-aruba : Depends: ruby-thor (>= 1.0) but 0.20.3-2 is to be installed

[Lucas Nussbaum]

Source: ruby-factory-girl
Version: 4.7.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 11~), gem2deb, rake, ruby-activerecord, 
> ruby-activesupport, ruby-appraisal, ruby-aruba, ruby-bourne, ruby-rspec, 
> ruby-rspec-its, ruby-sqlite3, ruby-timecop, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 11~), gem2deb, rake, ruby-activerecord, 
> ruby-activesupport, ruby-appraisal, ruby-aruba, ruby-bourne, ruby-rspec, 
> ruby-rspec-its, ruby-sqlite3, ruby-timecop, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [437 B]
> Get:5 copy:/<>/apt_archive ./ Packages [519 B]
> Fetched 1913 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  ruby-aruba : Depends: ruby-thor (>= 1.0) but 0.20.3-2 is to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/ruby-factory-girl_4.7.0-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#964702: pdfminer: FTBFS: /bin/sh: 1: rename.ul: not found

[Lucas Nussbaum]

Source: pdfminer
Version: 20191020+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> pybuild --install -p 3
> I: pybuild base:217: /usr/bin/python3 setup.py install --root 
> /<>/debian/python3-pdfminer 
> running install
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/high_level.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/latin_enc.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/psparser.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/ccitt.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/__init__.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/image.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/pdftypes.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/pdfinterp.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/ascii85.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/pdfdocument.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/cmapdb.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/layout.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/pdfpage.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/lzw.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/encodingdb.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/pdffont.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/settings.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/glyphlist.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/pdfparser.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/pdfdevice.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/rijndael.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/fontmetrics.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/runlength.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/pdfcolor.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/utils.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/arcfour.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> copying pdfminer/converter.py -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer
> creating /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/UniJIS-UCS2-HW-H.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/Katakana-H.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/UniJIS-UTF8-H.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/to-unicode-Adobe-GB1.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/HKgccs-B5-H.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/NWP-H.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/CNS2-H.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/GBK-EUC-V.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/90ms-RKSJ-V.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/CNS-EUC-H.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/B5pc-V.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/UniGB-UCS2-V.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/UniJIS-UCS2-V.pickle.gz -> 
> /<>/.pybuild/cpython3_3_pdfminer/build/pdfminer/cmap
> copying pdfminer/cmap/UniJIS2004-UTF16-V.pickle.gz -> 
> /<>/.pybuild/cp

Bug#964709: ruby-appraisal: FTBFS: ruby-aruba : Depends: ruby-thor (>= 1.0) but 0.20.3-2 is to be installed

[Lucas Nussbaum]

Source: ruby-appraisal
Version: 0.5.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: bundler, debhelper (>= 9~), gem2deb, rake, ruby-aruba, 
> ruby-rspec, build-essential, fakeroot
> Filtered Build-Depends: bundler, debhelper (>= 9~), gem2deb, rake, 
> ruby-aruba, ruby-rspec, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [396 B]
> Get:5 copy:/<>/apt_archive ./ Packages [475 B]
> Fetched 1828 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  ruby-aruba : Depends: ruby-thor (>= 1.0) but 0.20.3-2 is to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/ruby-appraisal_0.5.1-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#964701: sssd: FTBFS: ../src/providers/ad/ad_gpo_ndr.c:108:13: error: implicit declaration of function ‘ndr_pull_get_switch_value’; did you mean ‘ndr_pull_set_switch_value’? [-Werror=implicit-funct

[Lucas Nussbaum]

Source: sssd
Version: 2.2.3-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /bin/bash ./libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
> -Wall -I.. -I../src/sss_client -I../src -I.  -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include-I/usr/include/libnl3  
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  
> -DLIBDIR=\"/usr/lib/x86_64-linux-gnu\" -DVARDIR=\"/var\" 
> -DSSS_STATEDIR=\"/var/lib/sss\" -DSYSCONFDIR=\"/etc\" -DSHLIBEXT=\"\" 
> -DSSSDDATADIR=\"/usr/share/sssd\" -DSSSD_LIBEXEC_PATH=\"/usr/libexec/sssd\" 
> -DSSSD_CONF_DIR=\"/etc/sssd\" -DSSS_NSS_MCACHE_DIR=\"/var/lib/sss/mc\" 
> -DSSS_NSS_SOCKET_NAME=\"/var/lib/sss/pipes/nss\" 
> -DSSS_PAM_SOCKET_NAME=\"/var/lib/sss/pipes/pam\" 
> -DSSS_PAC_SOCKET_NAME=\"/var/lib/sss/pipes/pac\" 
> -DSSS_PAM_PRIV_SOCKET_NAME=\"/var/lib/sss/pipes/private/pam\" 
> -DSSS_SEC_SOCKET_NAME=\"/run/secrets.socket\" 
> -DSSS_SUDO_SOCKET_NAME=\"/var/lib/sss/pipes/sudo\" 
> -DSSS_AUTOFS_SOCKET_NAME=\"/var/lib/sss/pipes/autofs\" 
> -DSSS_SSH_SOCKET_NAME=\"/var/lib/sss/pipes/ssh\" 
> -DLOCALEDIR=\"/usr/share/locale\" 
> -DBASE_FILE_STEM=\"libsss_ad_la-ad_subdomains\"  -Wdate-time 
> -D_FORTIFY_SOURCE=2  -Wall -Wshadow -Wstrict-prototypes -Wpointer-arith 
> -Wcast-qual -Wcast-align -Wwrite-strings -Wundef 
> -Werror-implicit-function-declaration -Winit-self -Wmissing-include-dirs 
> -fno-strict-aliasing -std=gnu99-isystem /usr/include/mit-krb5 
> -DHAVE_IMMEDIATE_STRUCTURES=1 -D_GNU_SOURCE=1 -DHAVE_IMMEDIATE_STRUCTURES=1 
> -D_GNU_SOURCE=1 -DHAVE_IMMEDIATE_STRUCTURES=1 -I/usr/include/samba-4.0 
> -DHAVE_IMMEDIATE_STRUCTURES=1 -D_GNU_SOURCE=1 -DHAVE_IMMEDIATE_STRUCTURES=1 
> -D_GNU_SOURCE=1 -DHAVE_IMMEDIATE_STRUCTURES=1 -D_GNU_SOURCE=1 
> -DHAVE_IMMEDIATE_STRUCTURES=1 -I/usr/include/samba-4.0 
> -I/usr/include/samba-4.0 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -I/usr/include/samba-4.0 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
> -D_LARGEFILE64_SOURCE -c -o src/providers/ad/libsss_ad_la-ad_subdomains.lo 
> `test -f 'src/providers/ad/ad_subdomains.c' || echo 
> '../'`src/providers/ad/ad_subdomains.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wall -I.. 
> -I../src/sss_client -I../src -I. -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/libnl3 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -DLIBDIR=\"/usr/lib/x86_64-linux-gnu\" -DVARDIR=\"/var\" 
> -DSSS_STATEDIR=\"/var/lib/sss\" -DSYSCONFDIR=\"/etc\" -DSHLIBEXT=\"\" 
> -DSSSDDATADIR=\"/usr/share/sssd\" -DSSSD_LIBEXEC_PATH=\"/usr/libexec/sssd\" 
> -DSSSD_CONF_DIR=\"/etc/sssd\" -DSSS_NSS_MCACHE_DIR=\"/var/lib/sss/mc\" 
> -DSSS_NSS_SOCKET_NAME=\"/var/lib/sss/pipes/nss\" 
> -DSSS_PAM_SOCKET_NAME=\"/var/lib/sss/pipes/pam\" 
> -DSSS_PAC_SOCKET_NAME=\"/var/lib/sss/pipes/pac\" 
> -DSSS_PAM_PRIV_SOCKET_NAME=\"/var/lib/sss/pipes/private/pam\" 
> -DSSS_SEC_SOCKET_NAME=\"/run/secrets.socket\" 
> -DSSS_SUDO_SOCKET_NAME=\"/var/lib/sss/pipes/sudo\" 
> -DSSS_AUTOFS_SOCKET_NAME=\"/var/lib/sss/pipes/autofs\" 
> -DSSS_SSH_SOCKET_NAME=\"/var/lib/sss/pipes/ssh\" 
> -DLOCALEDIR=\"/usr/share/locale\" -DBASE_FILE_STEM=\"libsss_ad_la-ad_gpo\" 
> -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wshadow -Wstrict-prototypes 
> -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wundef 
> -Werror-implicit-function-declaration -Winit-self -Wmissing-include-dirs 
> -fno-strict-aliasing -std=gnu99 -isystem /usr/include/mit-krb5 
> -DHAVE_IMMEDIATE_STRUCTURES=1 -D_GNU_SOURCE=1 -DHAVE_IMMEDIATE_STRUCTURES=1 
> -D_GNU_SOURCE=1 -DHAVE_IMMEDIATE_STRUCTURES=1 -I/usr/include/samba-4.0 
> -DHAVE_IMMEDIATE_STRUCTURES=1 -D_GNU_SOURCE=1 -DHAVE_IMMEDIATE_STRUCTURES=1 
> -D_GNU_SOURCE=1 -DHAVE_IMMEDIATE_STRUCTURES=1 -D_GNU_SOURCE=1 
> -DHAVE_IMMEDIATE_STRUCTURES=1 -I/usr/include/samba-4.0 
> -I/usr/include/samba-4.0 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -I/usr/include/samba-4.0 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
> -D_LARGEFILE64_SOURCE -c ../src/providers/ad/ad_gpo.c  -fPIC -DPIC -o 
> src/providers/ad/.libs/libsss_ad_la-ad_gpo.o
> libtool: 

Bug#964628: python3-stdlib-extensions: FTBFS: unsatisfiable build-dependencies: libpython3.9-dev, libpython3.9-dbg, python3.9-dev:any, python3.9-dbg:any

[Matthias Klose]

On 7/9/20 12:54 PM, Lucas Nussbaum wrote:
> Source: python3-stdlib-extensions
> Version: 3.8.4~rc1-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200709 ftbfs-bullseye
> 
>> The following packages have unmet dependencies:
>>  sbuild-build-depends-main-dummy : Depends: libpython3.9-dev but it is not 
>> installable
>>Depends: libpython3.9-dbg but it is not 
>> installable
>>Depends: python3.9-dev:any but it is not 
>> installable
>>Depends: python3.9-dbg:any but it is not 
>> installable

the packages are still in NEW.