Bug#979634: marked as done (RFS: labgrid [ITP] -- Embedded board control program)

[Debian Bug Tracking System]

Your message dated Fri, 29 Jan 2021 08:49:37 +0100
with message-id <7baa0f33-94c7-a246-950a-7a91dfd3a...@fishpost.de>
and subject line Re: RFS: labgrid [ITP] -- Embedded board control programs
has caused the Debian Bug report #979634,
regarding RFS: labgrid [ITP] -- Embedded board control program
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.)


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

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "labgrid":

 * Package name: labgrid
   Version : 0.2.0+git20201216.c96120a-1
   Upstream Author : Pengutronix
 * URL : https://www.pengutronix.de/en/software/labgrid.html
 * License : BSD-2-Clause, LGPL-2.1+
 * Vcs : https://salsa.debian.org/python-team/packages/labgrid
   Section : python

It builds those binary packages:

  labgrid - Embedded board control programs
  python3-labgrid - Embedded board control library

To access further information about this package, please visit the 
following URL:


  https://mentors.debian.net/package/labgrid/

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/l/labgrid/labgrid_0.2.0+git20201216.c96120a-1.dsc


Changes for the initial release:

 labgrid (0.2.0+git20201216.c96120a-1) unstable; urgency=low
 .
   * Initial release. (Closes: #979511)

Regards,
Bastian
--- End Message ---
--- Begin Message ---

The package was uploaded to NEW.--- End Message ---

Processed: forcibly merging 981297 981298

[Debian Bug Tracking System]

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

> forcemerge 981297 981298
Bug #981297 {Done: Anton Gladky } [wnpp] ITP: smbus2 -- 
another pure Python implementation of the python-smbus package
Bug #981298 [wnpp] ITP: smbus2 -- another pure Python implementation of the 
python-smbus package
Marked Bug as done
Merged 981297 981298
> thanks
Stopping processing here.

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

Bug#981095: marked as done (Please support DT based proximity sensors)

[Debian Bug Tracking System]

Your message dated Fri, 29 Jan 2021 07:33:46 +
with message-id 
and subject line Bug#981095: fixed in iio-sensor-proxy 3.0-2
has caused the Debian Bug report #981095,
regarding Please support DT based proximity sensors
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.)


-- 
981095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iio-sensor-proxy
Version: 3.0-1
Severity: wishlist

Device tree based proximity sensors need a patch to read the near-level
information from DT that landed post 3.0. MR is at

https://salsa.debian.org/debian/iio-sensor-proxy/-/merge_requests/4

Cheers,
 -- Guido

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

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

Versions of packages iio-sensor-proxy depends on:
ii  libc6   2.31-4
ii  libglib2.0-02.66.2-1
ii  libgudev-1.0-0  234-1

iio-sensor-proxy recommends no packages.

Versions of packages iio-sensor-proxy suggests:
ii  systemd  246.6-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: iio-sensor-proxy
Source-Version: 3.0-2
Done: Ritesh Raj Sarraf 

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

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated iio-sensor-proxy 
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, 29 Jan 2021 12:35:45 +0530
Source: iio-sensor-proxy
Architecture: source
Version: 3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Ritesh Raj Sarraf 
Changed-By: Ritesh Raj Sarraf 
Closes: 981095
Changes:
 iio-sensor-proxy (3.0-2) unstable; urgency=medium
 .
   [ Ritesh Raj Sarraf ]
   * Shift override to binary package
   * Bump Standards Version to 4.5.1
 .
   [ Guido Günther ]
   * proximity: Get near-level from sysfs if available. This allows
 to use proximity sensors on device tree based devices like
 the Librem 5. (Closes: #981095)
Checksums-Sha1:
 23e6a0b40e16ee6583eb6f470788510edf2d19f4 2001 iio-sensor-proxy_3.0-2.dsc
 9827ee2f7193f5cec2e790f2382b37421af2a184 4436 
iio-sensor-proxy_3.0-2.debian.tar.xz
 b4e00a3c05aa8a2acf30ade5fa68bd2db07a94a0 6217 
iio-sensor-proxy_3.0-2_source.buildinfo
Checksums-Sha256:
 a9876ec0d1d10bd4cdc0be2c929f4b46cad8d5b4e5713435fb76aae61f31c3ac 2001 
iio-sensor-proxy_3.0-2.dsc
 30724d5750fd4df37e53ade81fd41155230399c751185c5384ae0401ec023eae 4436 
iio-sensor-proxy_3.0-2.debian.tar.xz
 7f77a81329d5d8a0b97423afd6d387019ed59423fd46e4d222ea68adaec91179 6217 
iio-sensor-proxy_3.0-2_source.buildinfo
Files:
 e75f5caa33344accf8fc4369aa4c6a41 2001 utils optional iio-sensor-proxy_3.0-2.dsc
 57c6c2654e9ed35ea4594a8cd797934a 4436 utils optional 
iio-sensor-proxy_3.0-2.debian.tar.xz
 69f0c482a64ba57fe01c25df8eb59108 6217 utils optional 
iio-sensor-proxy_3.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAmATt0EACgkQpjpYo/Lh
dWk4pw//YDKqsNtWfTELnKc2FY4SeswF/EiSzb9qkBV5hVQquLXMy83S/HtFvmlP
tE9TGttljDTCD4y/xUxzfmR2LRAwjtSYuFcGuozc8pZoGptC5EL8jKfcgQtzGA6Y
t98REVQ0c22fVmf129vW87PT5C6q/FlEqQOIEiQd4rTYcHNt4sUcBhgLtg7sjFlj
haOC2ploSji97nvglNXeCLuzwRoKZSwGAZlZwcro05sBeV/czLZxtecFOCqVggrk
9H7osI3vliALuG4xjHTWtJ8TcOuxx9DaQ/oTqbbuSAAMY11Ti6wKwxw1Qn8+vrG3
qwuby1eqBFhBXqOUdVjuqJU1ZqS/k4Grie+JNr59a9GQgVLdR1wx/rOzRBdtKaiy
sO0M+MdxVwVBjqtgz/mmGy+46C2NiW80Vbmm6oqurGX6XQqHBmOHDcjcgV+rOoVE
Hmcg6RbHJjOKTtcbJajoLNEyqZ8BEj5+s+fKN61BIKc1uvYG0qHDSn7VW/J25jKE
rPJRi1UrKC96Zfam660sIkViPHYTB2df1lPS87ZOMjt4oqGOWnaXGz/Epy8jBdhp
Je/uxMDOEkkvi3DXCwbMwl6ZGyS9lpvKPDp6QrKCSmS1uVUPxdDwLwizgwPZ6rnN
uSUGk7aHBdD8u/RTwONw46qONe5xKXngmyF8sFUBiYpK1vKvzwU=
=Q5ki

Bug#936421: marked as done (django-sortedm2m: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 23:57:31 -0700
with message-id <20210129065731.wbo6cs7czaebn...@haydn.kardiogramm.net>
and subject line Re: Bug#936421: Acknowledgement (django-sortedm2m: Python2 
removal in sid/bullseye)
has caused the Debian Bug report #936421,
regarding django-sortedm2m: 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.)


-- 
936421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:django-sortedm2m
Version: 1.2.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:django-sortedm2m

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 ---
Version: 2.0.0+dfsg.1-1

django-sortedm2m (2.0.0+dfsg.1-1) experimental; urgency=medium

  * New upstream version
  * d/control:
- Change maintainer to DPMT
- Change Vcs-* tags to DPMT
- Drop python2 package and build dependencies
- Remove X-Python3-Version, no longer needed
  * d/README.source: fix typo
  * d/rules: drop python2

 -- William Grzybowski   Wed, 18 Sep 2019 15:59:46 -0300--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> close #981317
Bug #981317 [wnpp] ITP: ruby-rdoc -- produces HTML and command-line 
documentation for Ruby
Marked Bug as done
>
End of message, stopping processing here.

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

Bug#977095: marked as done (sentry-python FTBFS with pytest 6)

[Debian Bug Tracking System]

Your message dated Fri, 29 Jan 2021 06:03:58 +
with message-id 
and subject line Bug#977095: fixed in sentry-python 0.13.2-1
has caused the Debian Bug report #977095,
regarding sentry-python FTBFS with pytest 6
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.)


-- 
977095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sentry-python
Version: 0.12.2-1
Severity: important
User: pyt...@packages.debian.org
Usertags: pytest-v6

Hi,

sentry-python FTBFS with pytest 6 in experimental because of changes to
the use of TerminalWriter. See

https://docs.pytest.org/en/stable/changelog.html#id60

The error log below has more details.

> ___ ERROR at teardown of test_flush_disabled 
> ___
> tests/conftest.py:109: in _capture_internal_warnings
> raise AssertionError(warning)
> E   AssertionError: {message : PytestDeprecationWarning('The 
> TerminalReporter.writer attribute is deprecated, use TerminalReporter._tw 
> instead at your own risk.\nSee 
> https://docs.pytest.org/en/stable/deprecations.html#terminalreporter-writer 
> for more information.'), category : 'PytestDeprecationWarning', filename : 
> '/usr/lib/python3/dist-packages/_pytest/compat.py', lineno : 340, line : None}
>  ERROR at teardown of test_subprocess_basic[True-None-as_iterator-True] 
> 
> tests/conftest.py:109: in _capture_internal_warnings
> raise AssertionError(warning)
> E   AssertionError: {message : PytestDeprecationWarning('The 
> TerminalReporter.writer attribute is deprecated, use TerminalReporter._tw 
> instead at your own risk.\nSee 
> https://docs.pytest.org/en/stable/deprecations.html#terminalreporter-writer 
> for more information.'), category : 'PytestDeprecationWarning', filename : 
> '/usr/lib/python3/dist-packages/_pytest/compat.py', lineno : 340, line : None}
> ___ ERROR at teardown of test_subprocess_basic[True-None-as_iterator-False] 
> 
> tests/conftest.py:109: in _capture_internal_warnings
> raise AssertionError(warning)
> E   AssertionError: {message : PytestDeprecationWarning('The 
> TerminalReporter.writer attribute is deprecated, use TerminalReporter._tw 
> instead at your own risk.\nSee 
> https://docs.pytest.org/en/stable/deprecations.html#terminalreporter-writer 
> for more information.'), category : 'PytestDeprecationWarning', filename : 
> '/usr/lib/python3/dist-packages/_pytest/compat.py', lineno : 340, line : None}
> __ ERROR at teardown of test_subprocess_basic[True-None-as_list-True] 
> __
> tests/conftest.py:109: in _capture_internal_warnings
> raise AssertionError(warning)
> E   AssertionError: {message : PytestDeprecationWarning('The 
> TerminalReporter.writer attribute is deprecated, use TerminalReporter._tw 
> instead at your own risk.\nSee 
> https://docs.pytest.org/en/stable/deprecations.html#terminalreporter-writer 
> for more information.'), category : 'PytestDeprecationWarning', filename : 
> '/usr/lib/python3/dist-packages/_pytest/compat.py', lineno : 340, line : None}
> _ ERROR at teardown of test_subprocess_basic[True-None-as_list-False] 
> __
> tests/conftest.py:109: in _capture_internal_warnings
> raise AssertionError(warning)
> E   AssertionError: {message : PytestDeprecationWarning('The 
> TerminalReporter.writer attribute is deprecated, use TerminalReporter._tw 
> instead at your own risk.\nSee 
> https://docs.pytest.org/en/stable/deprecations.html#terminalreporter-writer 
> for more information.'), category : 'PytestDeprecationWarning', filename : 
> '/usr/lib/python3/dist-packages/_pytest/compat.py', lineno : 340, line : None}
> _ ERROR at teardown of 
> test_subprocess_basic[True-env_mapping1-as_iterator-True] _
> tests/conftest.py:109: in _capture_internal_warnings
> raise AssertionError(warning)
> E   AssertionError: {message : PytestDeprecationWarning('The 
> TerminalReporter.writer attribute is deprecated, use TerminalReporter._tw 
> instead at your own risk.\nSee 
> https://docs.pytest.org/en/stable/deprecations.html#terminalreporter-writer 
> for more information.'), category : 'PytestDeprecationWarning', filename : 
> '/usr/lib/python3/dist-packages/_pytest/compat.py', lineno : 340, line : None}
> _ ERROR at teardown of 
> test_subprocess_basic[True-env_mapping1-as_iterator-False] _
> tests/conftest.py:109: in _capture_internal_warnings
> raise AssertionError(warning)
> E   AssertionError: {message : PytestDeprecationWarning('The 
> TerminalReporter.writer attribute is deprecated, use TerminalReporter._tw 
> instead 

Bug#979778: marked as done (node-ws: Please remove deprecated node-typescript-types dependency)

[Debian Bug Tracking System]

Your message dated Fri, 29 Jan 2021 05:33:35 +
with message-id 
and subject line Bug#979778: fixed in node-ws 7.4.2+~cs18.0.8-1
has caused the Debian Bug report #979778,
regarding node-ws: Please remove deprecated node-typescript-types dependency
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.)


-- 
979778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-ws
Severity: important

node-ws (build?) depends on transitional package node-typescript-types.

It should instead depend explicitly on packages corresponding with each
required Node.js module.

Severity raised in the hope that we can drop node-typescript-types soon.
--- End Message ---
--- Begin Message ---
Source: node-ws
Source-Version: 7.4.2+~cs18.0.8-1
Done: Xavier Guimard 

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

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

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-ws 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, 29 Jan 2021 06:04:52 +0100
Source: node-ws
Architecture: source
Version: 7.4.2+~cs18.0.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 979778
Changes:
 node-ws (7.4.2+~cs18.0.8-1) unstable; urgency=medium
 .
   * Team upload
   * Replace deprecated node-typescript-types by node-types-node
 (Closes: #979778)
   * New upstream version 7.4.2+~cs18.0.8
Checksums-Sha1: 
 73fa8395d7e52c0e248e6d230e15c1d51d44565b 3646 node-ws_7.4.2+~cs18.0.8-1.dsc
 17d88300a75ef161f81af86a1e6eb13d92b97fc6 4783 
node-ws_7.4.2+~cs18.0.8.orig-bufferutil.tar.gz
 92c09483724a7102c64e60479a3a704d69914515 11010 
node-ws_7.4.2+~cs18.0.8.orig-https-proxy-agent.tar.gz
 3ee66e312355ec1f6cbecfcc0122d45b3b8161c4 5152 
node-ws_7.4.2+~cs18.0.8.orig-utf-8-validate.tar.gz
 2d63c16d10f9344c2aa6507b7cabcfe6ebdd921d 4767 
node-ws_7.4.2+~cs18.0.8.orig-wscat.tar.gz
 16623e4659be389c5f8a41b831dbecd696c33d02 65736 
node-ws_7.4.2+~cs18.0.8.orig.tar.gz
 56246327e873ca01ce4b05a14f3aff137ae6c46f 5068 
node-ws_7.4.2+~cs18.0.8-1.debian.tar.xz
Checksums-Sha256: 
 804c831c1f72cf08ff06bb85b2186730b957c7e8d04dbece024b278414c5912b 3646 
node-ws_7.4.2+~cs18.0.8-1.dsc
 ff191c254f8a9e7f7e9d450b0942803a72d9692fd8a3df57dbb3938c0d186d37 4783 
node-ws_7.4.2+~cs18.0.8.orig-bufferutil.tar.gz
 2dbd9b7d861c4798234ecccb7a535a2817b6c6a94a3b2767ecc382989c872a4f 11010 
node-ws_7.4.2+~cs18.0.8.orig-https-proxy-agent.tar.gz
 cb30aca15b8e03d18ef3f8e2de07a90ff46674bb8ae89618b3ad767ab854ddec 5152 
node-ws_7.4.2+~cs18.0.8.orig-utf-8-validate.tar.gz
 e0eab9db7a1606aab5991bb7d63f2ecb2c49163f819f98c0f2f3388859f9 4767 
node-ws_7.4.2+~cs18.0.8.orig-wscat.tar.gz
 ecc095c4e14503d581449340b6466012343e658d720553274953380f34d1a209 65736 
node-ws_7.4.2+~cs18.0.8.orig.tar.gz
 5fae5fad54240301744070e7de00babd0ad226ad3d0d29686146f97de72dae87 5068 
node-ws_7.4.2+~cs18.0.8-1.debian.tar.xz
Files: 
 799045619125f8b4bf2ea3ac8cdfb0e2 3646 javascript optional 
node-ws_7.4.2+~cs18.0.8-1.dsc
 c91f33305e312a8957340738a5d3 4783 javascript optional 
node-ws_7.4.2+~cs18.0.8.orig-bufferutil.tar.gz
 78c7e9f5e3aeaa4e18ab2ac22a3903d5 11010 javascript optional 
node-ws_7.4.2+~cs18.0.8.orig-https-proxy-agent.tar.gz
 849d9ad252b1c298117583c3dfeac248 5152 javascript optional 
node-ws_7.4.2+~cs18.0.8.orig-utf-8-validate.tar.gz
 294d1ab55e2c2419761c6fe8cbfdde1e 4767 javascript optional 
node-ws_7.4.2+~cs18.0.8.orig-wscat.tar.gz
 5fbc8e8ecb89ee7204cd9e5c4229eb0e 65736 javascript optional 
node-ws_7.4.2+~cs18.0.8.orig.tar.gz
 d42b96a9c55d392af12a900db17d25c3 5068 javascript optional 
node-ws_7.4.2+~cs18.0.8-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmATl+EACgkQ9tdMp8mZ
7unuGQ//aCV+45cOLySOpvUhh/DdlJdaAQ8Py3xbsJrLDclaa46iy95E2b4NnlV2
97BRiKl3yNNaVb7dj3M7pG7n22rvVINPUoQ5nHthYM8adgMebAu8cCEFCoya6/hm
l5rF756cpcYIjMqLDeQ3mom2Vej9/kjcw1xyFOdkoJNvQQB5kaxZiFILbYEPFWel

Bug#950040: marked as done (pysdl2 FTBFS with libsdl2 2.0.10+dfsg1-1)

[Debian Bug Tracking System]

Your message dated Fri, 29 Jan 2021 02:48:28 +
with message-id 
and subject line Bug#950040: fixed in pysdl2 0.9.7+dfsg1-1
has caused the Debian Bug report #950040,
regarding pysdl2 FTBFS with libsdl2 2.0.10+dfsg1-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.)


-- 
950040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pysdl2
Version: 0.9.6+dfsg1-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pysdl2.html

...
=== FAILURES ===
_ SDL2ExtFontTest.test_FontManager_add _

self = 

def test_FontManager_add(self):
fm = sdl2ext.FontManager(RESOURCES.get_path("tuffy.ttf"))
self.assertIn("tuffy", fm.aliases)
self.assertIn("tuffy", fm.fonts)
self.assertIn(16, fm.fonts["tuffy"])
self.assertIsInstance(fm.fonts["tuffy"][16].contents, sdlttf.TTF_Font)

# Do some metrics tests
font = fm.fonts["tuffy"][16]
>   self.assertEqual(16, sdlttf.TTF_FontAscent(font))
E   AssertionError: 16 != 13

sdl2/test/sdl2ext_font_test.py:107: AssertionError
 SDLSurfaceTest.test_SDL_ConvertSurface 

self = 

def test_SDL_ConvertSurface(self):
for idx in pixels.ALL_PIXELFORMATS:
if pixels.SDL_ISPIXELFORMAT_FOURCC(idx):
continue
pfmt = pixels.SDL_AllocFormat(idx)
for fmt in pixels.ALL_PIXELFORMATS:
if pixels.SDL_ISPIXELFORMAT_FOURCC(fmt):
continue
bpp = c_int()
rmask, gmask, bmask, amask = Uint32(), Uint32(), Uint32(), 
Uint32()
ret = pixels.SDL_PixelFormatEnumToMasks(fmt, byref(bpp),
byref(rmask), 
byref(gmask),
byref(bmask), 
byref(amask))
self.assertEqual(ret, SDL_TRUE)
sf = surface.SDL_CreateRGBSurface(0, 10, 20, bpp, rmask, gmask,
  bmask, amask)
self.assertIsInstance(sf.contents, surface.SDL_Surface)
csf = surface.SDL_ConvertSurface(sf, pfmt, 0)
>   self.assertTrue(csf, error.SDL_GetError())
E   AssertionError:  is not true : b'Blit combination not supported'

sdl2/test/surface_test.py:103: AssertionError
_ SDLSurfaceTest.test_SDL_ConvertSurfaceFormat _

self = 

def test_SDL_ConvertSurfaceFormat(self):
for pfmt in pixels.ALL_PIXELFORMATS:
if pixels.SDL_ISPIXELFORMAT_FOURCC(pfmt):
continue
for fmt in pixels.ALL_PIXELFORMATS:
if pixels.SDL_ISPIXELFORMAT_FOURCC(fmt):
continue
bpp = c_int()
rmask, gmask, bmask, amask = Uint32(), Uint32(), Uint32(), 
Uint32()
ret = pixels.SDL_PixelFormatEnumToMasks(fmt, byref(bpp),
byref(rmask), 
byref(gmask),
byref(bmask), 
byref(amask))
self.assertEqual(ret, SDL_TRUE)
sf = surface.SDL_CreateRGBSurface(0, 10, 20, bpp, rmask, gmask,
  bmask, amask)
self.assertIsInstance(sf.contents, surface.SDL_Surface)
csf = surface.SDL_ConvertSurfaceFormat(sf, pfmt, 0)
>   self.assertTrue(csf, error.SDL_GetError())
E   AssertionError:  is not true : b'Blit combination not supported'

sdl2/test/surface_test.py:145: AssertionError
=== warnings summary ===
...
--- End Message ---
--- Begin Message ---
Source: pysdl2
Source-Version: 0.9.7+dfsg1-1
Done: Håvard Flaget Aasen 

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

Debian distribution maintenance software
pp.
Håvard Flaget Aasen  (supplier of updated pysdl2 
package)

(This message was generated 

Bug#981073: marked as done (dolphin: Dolphin uses 100% CPU)

[Debian Bug Tracking System]

Your message dated Fri, 29 Jan 2021 11:32:18 +0900
with message-id 
and subject line Re: Bug#981073: dolphin: Dolphin uses 100% CPU
has caused the Debian Bug report #981073,
regarding dolphin: Dolphin uses 100% CPU
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.)


-- 
981073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dolphin
Version: 4:20.12.1-2
Severity: important
X-Debbugs-Cc: steve.russe...@mail.com

Dear Maintainer,

After upgrading from buster to bullseye, Dolphin now uses 100% CPU
whenever it is running.

When I first start Dolphin, the CPU usage is minimal. But after
clicking a few different folders the CPU ramps up to 100% and stays
there regardless of what I do in dolphin. This occurs every time I run
Dolphin. Once the CPU usage hits 100% it never drops. I have left my
machine for a few hours and come back to see dolphin is still using
100% CPU.


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

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

Versions of packages dolphin depends on:
ii  baloo-kf5 5.78.0-2
ii  kinit 5.78.0-2
ii  kio   5.78.0-2
ii  libc6 2.31-9
ii  libdolphinvcs54:20.12.1-2
ii  libkf5activities5 5.78.0-2
ii  libkf5baloo5  5.78.0-2
ii  libkf5baloowidgets5   4:20.12.0-1
ii  libkf5bookmarks5  5.78.0-2
ii  libkf5codecs5 5.78.0-2
ii  libkf5completion5 5.78.0-2
ii  libkf5configcore5 5.78.0-3
ii  libkf5configgui5  5.78.0-3
ii  libkf5configwidgets5  5.78.0-2
ii  libkf5coreaddons5 5.78.0-2
ii  libkf5crash5  5.78.0-3
ii  libkf5dbusaddons5 5.78.0-2
ii  libkf5filemetadata3   5.78.0-2
ii  libkf5i18n5   5.78.0-2
ii  libkf5iconthemes5 5.78.0-2
ii  libkf5itemviews5  5.78.0-2
ii  libkf5jobwidgets5 5.78.0-2
ii  libkf5kcmutils5   5.78.0-3
ii  libkf5kiocore55.78.0-2
ii  libkf5kiofilewidgets5 5.78.0-2
ii  libkf5kiogui5 5.78.0-2
ii  libkf5kiowidgets5 5.78.0-2
ii  libkf5newstuff5   5.78.0-2
ii  libkf5notifications5  5.78.0-2
ii  libkf5parts5  5.78.0-2
ii  libkf5service-bin 5.78.0-2
ii  libkf5service55.78.0-2
ii  libkf5solid5  5.78.0-2
ii  libkf5textwidgets55.78.0-2
ii  libkf5widgetsaddons5  5.78.0-2
ii  libkf5windowsystem5   5.78.0-2
ii  libkf5xmlgui5 5.78.0-2
ii  libkuserfeedbackcore1 1.0.0-3
ii  libkuserfeedbackwidgets1  1.0.0-3
ii  libpackagekitqt5-11.0.2-1
ii  libphonon4qt5-4   4:4.11.1-3
ii  libqt5core5a  5.15.2+dfsg-2
ii  libqt5dbus5   5.15.2+dfsg-2
ii  libqt5gui55.15.2+dfsg-2
ii  libqt5widgets55.15.2+dfsg-2
ii  libqt5xml55.15.2+dfsg-2
ii  libstdc++610.2.1-6
ii  phonon4qt54:4.11.1-3

Versions of packages dolphin recommends:
ii  kimageformat-plugins  5.78.0-4
ii  kio-extras4:20.12.0-1

Versions of packages dolphin suggests:
pn  dolphin-plugins  

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Steve,

thanks and good to hear the problem is gone. Closing this bug.

Best

Norbert

On Thu, 28 Jan 2021, Steve Russell wrote:
> I have multiple 8TB disks with a lot of files. I did some more testing and 
> interestingly I can no longer reproduce the problem no matter how hard I try. 
> I did do multiple tests before filing the bug to confirm it was consistently 
> reproducible. So I'm not sure if an update or something else has changed. I 
> have no objections to closing the bug as it is no longer an issue for me.

--
PREINING Norbert  https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13--- End Message ---

Bug#979118: marked as done (python3-sgp4: Please update sgp4 to its latest release)

[Debian Bug Tracking System]

Your message dated Fri, 29 Jan 2021 02:33:31 +
with message-id 
and subject line Bug#979118: fixed in sgp4 2.15-0.1
has caused the Debian Bug report #979118,
regarding python3-sgp4: Please update sgp4 to its latest release
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.)


-- 
979118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-sgp4
Version: 1.4-1.1
Severity: wishlist

Dear Maintainer,

Please update sgp4 to its latest upstream release (2.14)

This version is needed for packaging the latest release of orbit-predictor. 

Cheers,

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

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

Versions of packages python3-sgp4 depends on:
ii  python3  3.9.1-1

python3-sgp4 recommends no packages.

python3-sgp4 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sgp4
Source-Version: 2.15-0.1
Done: Josue Ortega 

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

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

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated sgp4 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, 28 Jan 2021 20:00:22 -0600
Source: sgp4
Architecture: source
Version: 2.15-0.1
Distribution: unstable
Urgency: medium
Maintainer: Ulises Vitulli 
Changed-By: Josue Ortega 
Closes: 979118
Changes:
 sgp4 (2.15-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release (2.15-0.1). Closes: #979118
   * debian/control:
 + Add Vcs-* fields
   * Update package to use debhelper-compat (= 13)
   * Add debian/watch file
   * Bump Standards-Version to 4.5.1:
 + debian/copyright: Update URL to use https version
 + debian/control: Document field Rules-Requires-Root as 'no'
   * Add salsa-ci configuration file
   * Remove trailing whitespaces from d/changelog and d/control
   * Add autopkgtest suite
   * debian/control: Update package to be arch dependendent
   * debian/rules: Add bindnow linker flag to DEB_BUILD_MAINT_OPTIONS
Checksums-Sha1:
 e7596fa9d4f1b44a437cf2b4757049114bf13bd3 1900 sgp4_2.15-0.1.dsc
 5a81a9266ea9d0382831eca7fd1ecc0eaa2376e4 154431 sgp4_2.15.orig.tar.gz
 3512aeb7420a89be282c414abe30f8d336aba728 3100 sgp4_2.15-0.1.debian.tar.xz
 77ba334ae5b1091c4980d9a4572052691e1fa4bc 6258 sgp4_2.15-0.1_amd64.buildinfo
Checksums-Sha256:
 f28f0d15dbe048cff3cafc72040207a8a4091397b5373e8dbe200f79f52310f8 1900 
sgp4_2.15-0.1.dsc
 fdfff689ae7c0d230e5db5e00c2b258dcce326341ccefa7ec5b3a8458f537398 154431 
sgp4_2.15.orig.tar.gz
 f47dde9f434d618b0557bd58972fad85dd2e86fd7c53166eb18339a9bcc2618a 3100 
sgp4_2.15-0.1.debian.tar.xz
 629869eb35230d0633344f2df1afe0efe39c77332530f06ebd63fd5c195dca9e 6258 
sgp4_2.15-0.1_amd64.buildinfo
Files:
 b1d5ad62537fe3b098482246fc19ffd9 1900 python optional sgp4_2.15-0.1.dsc
 d695e9fe3b8039547155faea14a796ad 154431 python optional sgp4_2.15.orig.tar.gz
 5fa9c31fd15293baa71e0656928ec248 3100 python optional 
sgp4_2.15-0.1.debian.tar.xz
 af3cdb0631b17e6795904dfec975c057 6258 python optional 
sgp4_2.15-0.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAmATb3ERHGpvc3VlQGRl
Ymlhbi5vcmcACgkQAVCdXKtK/T+fng/9GemWDYgW0IhtQ9FWqCwrXeYeUB4g71yd
BVPb/lPbVjh4rhhsmCdIP+NP3QrMvPy0U+zFf6+tU+GfeBXPMxx2DRTJMhQuEZMy
f4X1Y9EGcifmb8JATi+jweG6N0XUMncpDvH74nW/N0risxao1m6C/pjHl2BO2DoI
uvvQ++Toaps8HwkNYJLVXXeL1M6chAZQvsWQspA020ptLWT8RX0O1lcoxKnHgwlU
UNVt8o14yR1hgGtwxh8zjPSzopnSqL0B1WJ6kpi2kpe/9b/0AeiI66TPefOYNexa
Tas8vSv+lX8huu1UPn5sdOj2yJGj6+pSNHyszC+xL0O+Kz+vCJAILCm63nYKgWZi
pW0A09tTDQdWQmsJKfC/A9UaFOuS7g6FwTiMdfVFCB4JH29DZ1emFKshclDg01Ol
cIS7ktps0qBXkOfiDV9PH0Jd23/qZ4qd94eJZr5352JsB1F+Oh3C3bql5w1GZQVQ

Bug#976577: marked as done (librsvg: FTBFS: panicked at 'attempted to leave type `linked_hash_map::Node, object::Object>` uninitialized, which is invalid')

[Debian Bug Tracking System]

Your message dated Fri, 29 Jan 2021 02:21:12 +
with message-id 
and subject line Bug#976577: fixed in librsvg 2.50.3+dfsg-1
has caused the Debian Bug report #976577,
regarding librsvg: FTBFS: panicked at 'attempted to leave type 
`linked_hash_map::Node, object::Object>` uninitialized, which 
is invalid'
to be marked as done.

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

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


-- 
976577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: librsvg
Version: 2.50.2+dfsg-1
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> make[5]: Entering directory '/<>'
> cd . &&   \
> CARGO_TARGET_DIR=/<>/target  \
> LIBRSVG_BUILD_DIR=/<>\
> OUT_DIR=/<>/tests/output \
> cargo --locked test --verbose  --release
>Fresh autocfg v1.0.1
>Fresh pkg-config v0.3.19
>Fresh unicode-xid v0.2.1
>Fresh lazy_static v1.4.0
>Fresh cfg-if v0.1.10
>Fresh ppv-lite86 v0.2.10
>Fresh siphasher v0.3.3
>Fresh itoa v0.4.6
>Fresh cfg-if v1.0.0
>Fresh futures-core v0.3.8
>Fresh once_cell v1.5.2
>Fresh slab v0.4.2
>Fresh pin-utils v0.1.0
>Fresh encoding_index_tests v0.1.4
>Fresh semver-parser v0.7.0
>Fresh scopeguard v1.1.0
>Fresh matches v0.1.8
>Fresh either v1.6.1
>Fresh regex-syntax v0.6.21
>Fresh new_debug_unreachable v1.0.4
>Fresh dtoa v0.4.6
>Fresh precomputed-hash v0.1.1
>Fresh mac v0.1.1
>Fresh tinyvec_macros v0.1.0
>Compiling cairo-rs v0.8.1
>Fresh utf-8 v0.7.5
>Fresh stable_deref_trait v1.2.0
>Fresh nodrop v0.1.14
>  Running `rustc --crate-name build_script_build 
> /<>/vendor/cairo-rs/build.rs --error-format=json 
> --json=diagnostic-rendered-ansi --crate-type bin --emit=dep-info,link -C 
> opt-level=3 -C debuginfo=2 --cfg 'feature="default"' --cfg 'feature="glib"' 
> --cfg 'feature="glib-sys"' --cfg 'feature="gobject-sys"' --cfg 
> 'feature="pdf"' --cfg 'feature="png"' --cfg 'feature="svg"' --cfg 
> 'feature="use_glib"' --cfg 'feature="v1_14"' --cfg 'feature="v1_16"' -C 
> metadata=7732b959fd6bfce5 -C extra-filename=-7732b959fd6bfce5 --out-dir 
> /<>/target/release/build/cairo-rs-7732b959fd6bfce5 -L 
> dependency=/<>/target/release/deps --cap-lints allow`
>Fresh smallvec v1.5.0
>Fresh percent-encoding v2.1.0
>Fresh rawpointer v0.2.1
>Fresh futures-io v0.3.8
>Fresh bytemuck v1.4.1
>Fresh thin-slice v0.1.1
>Fresh language-tags v0.2.2
>Fresh rctree v0.3.3
>Fresh tinyvec v0.3.4
>Compiling unicode-width v0.1.8
>Compiling crc32fast v1.2.1
>Compiling same-file v1.0.6
>  Running `rustc --crate-name unicode_width 
> /<>/vendor/unicode-width/src/lib.rs --error-format=json 
> --json=diagnostic-rendered-ansi,artifacts --crate-type lib 
> --emit=dep-info,metadata,link -C opt-level=3 -C debuginfo=2 --cfg 
> 'feature="default"' -C metadata=baa187aee56baaa8 -C 
> extra-filename=-baa187aee56baaa8 --out-dir 
> /<>/target/release/deps -L 
> dependency=/<>/target/release/deps --cap-lints allow`
>  Running `rustc --crate-name build_script_build 
> /<>/vendor/crc32fast/build.rs --error-format=json 
> --json=diagnostic-rendered-ansi --crate-type bin --emit=dep-info,link -C 
> opt-level=3 -C debuginfo=2 --cfg 'feature="default"' --cfg 'feature="std"' -C 
> metadata=d06cbec07760c52c -C extra-filename=-d06cbec07760c52c --out-dir 
> /<>/target/release/build/crc32fast-d06cbec07760c52c -L 
> dependency=/<>/target/release/deps --cap-lints allow`
>  Running `rustc --crate-name same_file --edition=2018 
> /<>/vendor/same-file/src/lib.rs --error-format=json 
> --json=diagnostic-rendered-ansi,artifacts --crate-type lib 
> --emit=dep-info,metadata,link -C opt-level=3 -C debuginfo=2 -C 
> metadata=d9e013598eb9c474 -C extra-filename=-d9e013598eb9c474 --out-dir 
> /<>/target/release/deps -L 
> dependency=/<>/target/release/deps --cap-lints allow`
>Compiling half v1.6.0
>  Running `rustc --crate-name half --edition=2018 
> /<>/vendor/half/src/lib.rs --error-format=json 
> --json=diagnostic-rendered-ansi,artifacts --crate-type lib 
> --emit=dep-info,metadata,link -C opt-level=3 -C debuginfo=2 -C 
> metadata=89226c78ecf8fc8b -C 

Bug#976270: marked as done (ruby-puppet-forge: autopkgtest/ftbfs with ruby-faraday-middleware 1.x)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 23:35:50 +
with message-id 
and subject line Bug#976270: fixed in ruby-puppet-forge 3.0.0-1
has caused the Debian Bug report #976270,
regarding ruby-puppet-forge: autopkgtest/ftbfs with ruby-faraday-middleware 1.x
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.)


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

Package: ruby-puppet-forge
Version: 2.3.2-1
Severity: serious

autopkgtest is failing with ruby-faraday-middleware 1.0.

/usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not 
find 'faraday_middleware' (< 0.14.0, >= 0.9.0) - did find: 
[faraday_middleware-1.0.0] (Gem::MissingSpecVersionError)


Full log 
https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-puppet-forge/8564808/log.gz


I can see there is already a patch for relaxing faraday.

https://salsa.debian.org/puppet-team/ruby-puppet-forge/-/blob/master/debian/patches/002_loosen_deps.patch

This will need to be extended to cover ruby-faraday-middleware as well.
--- End Message ---
--- Begin Message ---
Source: ruby-puppet-forge
Source-Version: 3.0.0-1
Done: Sebastien Badia 

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

Debian distribution maintenance software
pp.
Sebastien Badia  (supplier of updated ruby-puppet-forge 
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, 29 Jan 2021 00:13:44 +0100
Source: ruby-puppet-forge
Architecture: source
Version: 3.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers 

Changed-By: Sebastien Badia 
Closes: 976270
Changes:
 ruby-puppet-forge (3.0.0-1) unstable; urgency=medium
 .
   [ Utkarsh Gupta ]
   * Tighten dependency on ruby-faraday*.
 .
   [ Sebastien Badia ]
   * New upstream version 3.0.0, fix for ruby-faraday* > 1.x (Closes: #976270)
   * d/upstream: Fix missing-bug-tracking
   * d/patches: Refresh patchs, and add DEP-3 headers
 + Bump debhelper compat to 13
 + Bump Standards-Versions to 4.5.1 (no changes)
Checksums-Sha1:
 8a557f1fc42d53cb54bade4e0e78e09bd2be7017 2264 ruby-puppet-forge_3.0.0-1.dsc
 872468f7ea73ee4ecdac82c5cafb58780af5a5f6 773210 
ruby-puppet-forge_3.0.0.orig.tar.gz
 9f46e20e626dafad0d4f20d5914b91b8b15fb510 3808 
ruby-puppet-forge_3.0.0-1.debian.tar.xz
 ede062c3b5258a71a24b50c107cb109775f458a6 12344 
ruby-puppet-forge_3.0.0-1_source.buildinfo
Checksums-Sha256:
 7c4a9b93bb6b9dd11ff9b3c264fb6f83c2ad1901e57c201f607e9c9a49bebd79 2264 
ruby-puppet-forge_3.0.0-1.dsc
 ba8cca7bae8495e702ca73f830d5ea0a02b24f32aab72a953d2a764793d86aaa 773210 
ruby-puppet-forge_3.0.0.orig.tar.gz
 cada5b45b6dd0db81d622f018ba1cd7bf74b75844a6409c70e619ff9f57361fa 3808 
ruby-puppet-forge_3.0.0-1.debian.tar.xz
 c66b56e78d1c5302bedb6202a34e107d6cea37142c14f9c766e81255bd898994 12344 
ruby-puppet-forge_3.0.0-1_source.buildinfo
Files:
 8749bc4e03e7df527f10198e02a56d41 2264 ruby optional 
ruby-puppet-forge_3.0.0-1.dsc
 d7e522ef25d16f3108f3fd247c66ccca 773210 ruby optional 
ruby-puppet-forge_3.0.0.orig.tar.gz
 7f7d0fdae47dca51c70eb4fb68ac8aa4 3808 ruby optional 
ruby-puppet-forge_3.0.0-1.debian.tar.xz
 5cd8725aa1af0cb0cb830eb56dfda09d 12344 ruby optional 
ruby-puppet-forge_3.0.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfkPprL9yerPPCIUzhxbORhSkUtgFAmATRxgACgkQhxbORhSk
UtjREg/+I7Cj07Uf9BmC0cXyrm3p6WDUfRqfMGLlD6306fwPMhKWns3Wn6/TXvEH
+6sd5eXdyFd27JqT+qUtj7Li+e0tg1VJqVoCSu2khxvt+L8U99T31nN3c4FQhlNM
uhjiwWeogMY8xu8P3+wR01e3yimvg/DRxfZe+N9YwiCbCde0FOz6D+TiQQiQ9pb2
twp7QhAm+MUfrMn+SkXfjJEpQiJsJWAyMzkoTg+GI+YLtWkkzfLBvnqeOPQYRnGJ
lv2rRx8XMaopm5/3XrazE5HztQpXECxkYcmdwT636/nSE3T5vjMYhoHx8eQ2bzBI
6q/r/4XeA5q9dlPq1D/ZnpfvFHkRwFK6vKpyBSSBtvTDz5Eh8T3dvRbl7QicpHpU
gBtv6LcNpPmpGen92Py02qRdD1LZj3TvI/BKdPd02gOnZQG/cf1eF9ahlT/+FFSg
xUGu+PnIUid5cHb8G+avLhm+MXsTlhVwbF9EUc6cySo3AIzqNfCxuEq00L4BvX5v
hHfTc8qj4yqIXFDr0ZdxiXrFlhieabLd7XUqINcc7moTJp5MCBWjX83cv0qRIrEb
Y7q7iB+SV2Z0w960LWFEJcVyMSEoo6gt8+URggGVzrG45fX9G06Y6njuezc6ywaQ

Bug#969480: marked as done (prometheus-blackbox-exporter: [INTL:fr] French debconf templates translation)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 23:35:28 +
with message-id 
and subject line Bug#969480: fixed in prometheus-blackbox-exporter 0.18.0+ds-2
has caused the Debian Bug report #969480,
regarding prometheus-blackbox-exporter: [INTL:fr] French debconf templates 
translation
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.)


-- 
969480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: prometheus-blackbox-exporter
Severity: wishlist
Tags: patch l10n

Hi!

Please find attached the french debconf templates translation, proofread
by the debian-l10n-french mailing list contributors.

This file should be put as debian/po/fr.po in your package build tree.

Kind Regards

Jean-Pierre Giraud


fr.po.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: prometheus-blackbox-exporter
Source-Version: 0.18.0+ds-2
Done: Guillem Jover 

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated 
prometheus-blackbox-exporter 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, 29 Jan 2021 00:27:44 +0100
Source: prometheus-blackbox-exporter
Architecture: source
Version: 0.18.0+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Guillem Jover 
Closes: 968856 968857 969342 969480
Changes:
 prometheus-blackbox-exporter (0.18.0+ds-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Daniel Swarbrick ]
   * Bump Standards-Version to 4.5.1 (no changes).
   * d/po/de.po: remove obsolete FIXME comment
 .
   [ Frans Spiesschaert ]
   * Add initial Dutch debconf translation (Closes: #969342).
 .
   [ Jean-Pierre Giraud ]
   * Add initial French debconf translation (Closes: #969480).
 .
   [ Helge Kreutzmann ]
   * Minor grammar fix in debian/templates (Closes: #968857).
   * Add initial German debconf translation (Closes: #968856).
 .
   [ Guillem Jover ]
   * Switch to debian/watch format version 4
   * Indent debian/watch opts contents
   * Decapitalize synopsis first word
   * Move note about license location on Debian systems into a Comment field
   * Update gitlab-ci.yml from latest upstream version
   * Use $(BUILDDIR) uniformly instead of the literal build/
   * Update version.BuildUser to match the Maintainer address
   * Remove nocheck handling from override_dh_auto_test
   * Change systemd service Restart directive from always to on-failure
   * Add man:prometheus-blackbox-exporter(1) to systemd unit Documentation field
   * Use '' instead of `' in text
   * Use $() instead of `` in init script
   * Remove $syslog dependency from init script
   * Switch from /var/run to /run
   * Add missing dependency on adduser
   * Rewrite init script using start-stop-daemon
   * Unify log files removal during purge into a single entry
   * Add missing CFGFILE variable to fix init script config check
   * Remove error suppression from postinst
   * Run adduser unconditionally
   * Do not change pathname metadata if there are dpkg statoverrides in place
   * Update copyright claims
   * Update gitignore entries
Checksums-Sha1:
 1a30a564d8f44e8a0fe3690e64e6bd4af69dab07 2637 
prometheus-blackbox-exporter_0.18.0+ds-2.dsc
 62bb0b0ef60e360d88f3f1f17fe288cb18c02ed8 9804 
prometheus-blackbox-exporter_0.18.0+ds-2.debian.tar.xz
 a723495a6dfeeba08651d25ee7f8f05ecc25c497 8681 
prometheus-blackbox-exporter_0.18.0+ds-2_amd64.buildinfo
Checksums-Sha256:
 093d635c3addd8087131581e937b708e440ba6d952243a5a8793eea8e7fc246d 2637 
prometheus-blackbox-exporter_0.18.0+ds-2.dsc
 41aefd6022f2bd24fb0a2b931252bad3d8a600c26c8092111b19b9c9ec17806c 9804 
prometheus-blackbox-exporter_0.18.0+ds-2.debian.tar.xz
 6f5b35b8809f7ea4dcd1f9ce7f90b977737c47f7dc6bce5894c23d91d37acd26 8681 
prometheus-blackbox-exporter_0.18.0+ds-2_amd64.buildinfo
Files:
 7b7f690997a42e118a792b7ab145a65d 2637 net optional 
prometheus-blackbox-exporter_0.18.0+ds-2.dsc
 

Bug#969342: marked as done (prometheus-blackbox-exporter: [INTL:nl] Dutch translation of debconf messages)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 23:35:28 +
with message-id 
and subject line Bug#969342: fixed in prometheus-blackbox-exporter 0.18.0+ds-2
has caused the Debian Bug report #969342,
regarding prometheus-blackbox-exporter: [INTL:nl] Dutch translation of debconf 
messages
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.)


-- 
969342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
 
 
Package: prometheus-blackbox-exporter 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached the Dutch translation of prometheus-blackbox-
exporter debconf messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
 

-- 
Kind regards,
Frans Spiesschaert



nl.po.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: prometheus-blackbox-exporter
Source-Version: 0.18.0+ds-2
Done: Guillem Jover 

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated 
prometheus-blackbox-exporter 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, 29 Jan 2021 00:27:44 +0100
Source: prometheus-blackbox-exporter
Architecture: source
Version: 0.18.0+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Guillem Jover 
Closes: 968856 968857 969342 969480
Changes:
 prometheus-blackbox-exporter (0.18.0+ds-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Daniel Swarbrick ]
   * Bump Standards-Version to 4.5.1 (no changes).
   * d/po/de.po: remove obsolete FIXME comment
 .
   [ Frans Spiesschaert ]
   * Add initial Dutch debconf translation (Closes: #969342).
 .
   [ Jean-Pierre Giraud ]
   * Add initial French debconf translation (Closes: #969480).
 .
   [ Helge Kreutzmann ]
   * Minor grammar fix in debian/templates (Closes: #968857).
   * Add initial German debconf translation (Closes: #968856).
 .
   [ Guillem Jover ]
   * Switch to debian/watch format version 4
   * Indent debian/watch opts contents
   * Decapitalize synopsis first word
   * Move note about license location on Debian systems into a Comment field
   * Update gitlab-ci.yml from latest upstream version
   * Use $(BUILDDIR) uniformly instead of the literal build/
   * Update version.BuildUser to match the Maintainer address
   * Remove nocheck handling from override_dh_auto_test
   * Change systemd service Restart directive from always to on-failure
   * Add man:prometheus-blackbox-exporter(1) to systemd unit Documentation field
   * Use '' instead of `' in text
   * Use $() instead of `` in init script
   * Remove $syslog dependency from init script
   * Switch from /var/run to /run
   * Add missing dependency on adduser
   * Rewrite init script using start-stop-daemon
   * Unify log files removal during purge into a single entry
   * Add missing CFGFILE variable to fix init script config check
   * Remove error suppression from postinst
   * Run adduser unconditionally
   * Do not change pathname metadata if there are dpkg statoverrides in place
   * Update copyright claims
   * Update gitignore entries
Checksums-Sha1:
 1a30a564d8f44e8a0fe3690e64e6bd4af69dab07 2637 
prometheus-blackbox-exporter_0.18.0+ds-2.dsc
 62bb0b0ef60e360d88f3f1f17fe288cb18c02ed8 9804 
prometheus-blackbox-exporter_0.18.0+ds-2.debian.tar.xz
 a723495a6dfeeba08651d25ee7f8f05ecc25c497 8681 
prometheus-blackbox-exporter_0.18.0+ds-2_amd64.buildinfo
Checksums-Sha256:
 093d635c3addd8087131581e937b708e440ba6d952243a5a8793eea8e7fc246d 2637 
prometheus-blackbox-exporter_0.18.0+ds-2.dsc
 41aefd6022f2bd24fb0a2b931252bad3d8a600c26c8092111b19b9c9ec17806c 9804 
prometheus-blackbox-exporter_0.18.0+ds-2.debian.tar.xz
 6f5b35b8809f7ea4dcd1f9ce7f90b977737c47f7dc6bce5894c23d91d37acd26 8681 

Bug#968856: marked as done (prometheus-blackbox-exporter: [INTL:de] initial German debconf translation)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 23:35:28 +
with message-id 
and subject line Bug#968856: fixed in prometheus-blackbox-exporter 0.18.0+ds-2
has caused the Debian Bug report #968856,
regarding prometheus-blackbox-exporter: [INTL:de] initial German debconf 
translation
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.)


-- 
968856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: prometheus-blackbox-exporter
Version: 0.17.0+ds-1
Severity: wishlist
Tags: patch l10n

Please find the initial German debconf translation for 
prometheus-blackbox-exporter
attached.

Please place this file in debian/po/ as de.po for your next upload.

If you update your template, please use 
'msgfmt --statistics '
to check the po-files for fuzzy or untranslated strings.

If there are such strings, please contact me so I can update the 
German translation.

Greetings
Helge
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the 
prometheus-blackbox-exporter package.
# Helge Kreutzmann , 2020.
#
msgid ""
msgstr ""
"Project-Id-Version: prometheus-blackbox-exporter 0.17.0+ds-1\n"
"Report-Msgid-Bugs-To: prometheus-blackbox-expor...@packages.debian.org\n"
"POT-Creation-Date: 2020-07-25 19:32+0200\n"
"PO-Revision-Date: 2020-08-22 14:54+0200\n"
"Last-Translator: Helge Kreutzmann \n"
"Language-Team: German \n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Enable additional network privileges for ICMP probing?"
msgstr "Zusätzliche Netzwerkprivilegien für ICMP-Untersuchungen aktivieren?"

# FIXME capabilities → capability
#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"/usr/bin/prometheus-blackbox-exporter requires CAP_NET_RAW capabilities to "
"be able to send out crafted packets to targets for ICMP probing."
msgstr ""
"/usr/bin/prometheus-blackbox-exporter benötigt die Capability CAP_NET_RAW, "
"um in der Lage zu sein, handgefertigte Pakete zur ICMP-Untersuchung an Ziele "
"zu senden."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"ICMP probing will not work unless this option is enabled, or prometheus-"
"blackbox-exporter runs as root."
msgstr ""
"ICMP-Untersuchungen werden nicht funktionieren, außer diese Option ist "
"aktiviert oder prometheus-blackbox-exporter läuft als root."
--- End Message ---
--- Begin Message ---
Source: prometheus-blackbox-exporter
Source-Version: 0.18.0+ds-2
Done: Guillem Jover 

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated 
prometheus-blackbox-exporter 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, 29 Jan 2021 00:27:44 +0100
Source: prometheus-blackbox-exporter
Architecture: source
Version: 0.18.0+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Guillem Jover 
Closes: 968856 968857 969342 969480
Changes:
 prometheus-blackbox-exporter (0.18.0+ds-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Daniel Swarbrick ]
   * Bump Standards-Version to 4.5.1 (no changes).
   * d/po/de.po: remove obsolete FIXME comment
 .
   [ Frans Spiesschaert ]
   * Add initial Dutch debconf translation (Closes: #969342).
 .
   [ Jean-Pierre Giraud ]
   * Add initial French debconf translation (Closes: #969480).
 .
   [ Helge Kreutzmann ]
   * Minor grammar fix in debian/templates (Closes: #968857).
   * Add initial German debconf translation (Closes: #968856).
 .
   [ Guillem Jover ]
   * Switch to debian/watch format version 4
   * Indent debian/watch opts contents
   * Decapitalize synopsis first word
   * Move note about license location on Debian systems into a Comment field
   * Update gitlab-ci.yml from latest upstream version
   * Use $(BUILDDIR) 

Bug#968857: marked as done (prometheus-blackbox-exporter: Typo in Debconf template)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 23:35:28 +
with message-id 
and subject line Bug#968857: fixed in prometheus-blackbox-exporter 0.18.0+ds-2
has caused the Debian Bug report #968857,
regarding prometheus-blackbox-exporter: Typo in Debconf template
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.)


-- 
968857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: prometheus-blackbox-exporter
Version: 0.17.0+ds-1
Severity: minor
Tags: patch

--- templates.orig  2020-08-22 15:05:28.838843532 +0200
+++ templates   2020-08-22 15:05:48.026936411 +0200
@@ -2,7 +2,7 @@
 Type: boolean
 Default: false
 _Description: Enable additional network privileges for ICMP probing?
- /usr/bin/prometheus-blackbox-exporter requires CAP_NET_RAW capabilities to be
+ /usr/bin/prometheus-blackbox-exporter requires the CAP_NET_RAW capability to 
be
  able to send out crafted packets to targets for ICMP probing.
  .
  ICMP probing will not work unless this option is enabled, or


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

Kernel: Linux 5.7.4 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages prometheus-blackbox-exporter depends on:
ii  debconf [debconf-2.0]  1.5.74
ii  init-system-helpers1.58
ii  libc6  2.31-3
ii  libcap2-bin1:2.42-2

prometheus-blackbox-exporter recommends no packages.

prometheus-blackbox-exporter suggests no packages.

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: prometheus-blackbox-exporter
Source-Version: 0.18.0+ds-2
Done: Guillem Jover 

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated 
prometheus-blackbox-exporter 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, 29 Jan 2021 00:27:44 +0100
Source: prometheus-blackbox-exporter
Architecture: source
Version: 0.18.0+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Guillem Jover 
Closes: 968856 968857 969342 969480
Changes:
 prometheus-blackbox-exporter (0.18.0+ds-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Daniel Swarbrick ]
   * Bump Standards-Version to 4.5.1 (no changes).
   * d/po/de.po: remove obsolete FIXME comment
 .
   [ Frans Spiesschaert ]
   * Add initial Dutch debconf translation (Closes: #969342).
 .
   [ Jean-Pierre Giraud ]
   * Add initial French debconf translation (Closes: #969480).
 .
   [ Helge Kreutzmann ]
   * Minor grammar fix in debian/templates (Closes: #968857).
   * Add initial German debconf translation (Closes: #968856).
 .
   [ Guillem Jover ]
   * Switch to debian/watch format version 4
   * Indent debian/watch opts contents
   * Decapitalize synopsis first word
   * Move note about license location on Debian systems into a Comment field
   * Update gitlab-ci.yml from latest upstream version
   * Use $(BUILDDIR) uniformly instead of the literal build/
   * Update version.BuildUser to match the Maintainer address
   * Remove nocheck handling from override_dh_auto_test
   * Change systemd service Restart directive from always to on-failure
   * Add man:prometheus-blackbox-exporter(1) to systemd unit Documentation field
   * Use '' instead of `' in text
   * Use $() instead of `` in init script
   * Remove $syslog 

Bug#942871: marked as done (prometheus-mongodb-exporter: segfaults with mongodb 4.2)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 23:19:19 +
with message-id 
and subject line Bug#942871: fixed in prometheus-mongodb-exporter 
1.0.0+git20180522.e755a44-3
has caused the Debian Bug report #942871,
regarding prometheus-mongodb-exporter: segfaults with mongodb 4.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.)


-- 
942871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942871
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: prometheus-mongodb-exporter
Version: 1.0.0+git20180522.e755a44-1
Severity: important
Tags: patch

Dear maintainer:

On a replica set where mongodb 4.0 and prometheus-mongodb-exporter used
to work ok, an upgrade to mongodb 4.2 makes prometheus-mongodb-exporter
to crash as soon as a request from prometheus is received:

prometheus-mongodb-exporter.service: Main process exited, code=exited, 
status=2/INVALIDARGUMENT
prometheus-mongodb-exporter.service: Unit entered failed state.
prometheus-mongodb-exporter.service: Failed with result 'exit-code'.
prometheus-mongodb-exporter.service: Service hold-off time over, scheduling 
restart.

My /etc/default/prometheus-mongodb-exporter is like this:

ARGS='-mongodb.uri="mongodb://user:password@localhost:27017" -log_dir 
/var/log/prometheus -web.listen-address :9201'

And this is what I do to trigger a segfault:

curl localhost:9201/metrics


I found a solution here:

https://www.bountysource.com/issues/65886524-nil-pointer-panic-when-monitoring-a-mongodb-with-no-username-and-password-set

The attached patch, based on the post above, solves the problem for
me, and I believe it is otherwise harmless for anybody who does not
have the problem. I tested it by applying the patch to the package in
stretch-backports.

Maybe another option would be to switch to this upstream which is said
to be more up-to-date:

https://github.com/percona/mongodb_exporter

but I have not tested it.

Thanks.--- a/collector/metrics.go
+++ b/collector/metrics.go
@@ -349,7 +349,9 @@ func (replStats *ReplStats) Export(ch chan<- 
prometheus.Metric) {
replStats.Apply.Export(ch)
replStats.Buffer.Export(ch)
replStats.Network.Export(ch)
-   replStats.PreloadStats.Export(ch)
+   if replStats.PreloadStats != nil {
+   replStats.PreloadStats.Export(ch)
+   }
 }
 
 // PreloadStats are the stats associated with preload operation.
--- End Message ---
--- Begin Message ---
Source: prometheus-mongodb-exporter
Source-Version: 1.0.0+git20180522.e755a44-3
Done: Martina Ferrari 

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

Debian distribution maintenance software
pp.
Martina Ferrari  (supplier of updated 
prometheus-mongodb-exporter 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, 28 Jan 2021 22:56:24 +
Source: prometheus-mongodb-exporter
Architecture: source
Version: 1.0.0+git20180522.e755a44-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Martina Ferrari 
Closes: 942871
Changes:
 prometheus-mongodb-exporter (1.0.0+git20180522.e755a44-3) unstable; 
urgency=medium
 .
   * Add patch to avoid a panic with newer versions of MongoDB.
 Closes: #942871
   * debian/control: Update S-V to 4.5.1 with no changes.
Checksums-Sha1:
 42ee658a9ab2397c3601536c7bc42da67ec64a32 2477 
prometheus-mongodb-exporter_1.0.0+git20180522.e755a44-3.dsc
 8ba57177ad4dcd07b03662f133cc5f89d71c3637 12004 
prometheus-mongodb-exporter_1.0.0+git20180522.e755a44-3.debian.tar.xz
 1a9b8842e8a189bb9fde0fe46cb4af1ed65cab26 9094 
prometheus-mongodb-exporter_1.0.0+git20180522.e755a44-3_amd64.buildinfo
Checksums-Sha256:
 c16514a391a0b75e5fc0e8b29815e22c527af453b4544ab1464be9edb7eb5121 2477 
prometheus-mongodb-exporter_1.0.0+git20180522.e755a44-3.dsc
 78c9cd4e9e29472e240cb120e1b43de4a35b3106004aff33ce163d8e5efff7e3 12004 
prometheus-mongodb-exporter_1.0.0+git20180522.e755a44-3.debian.tar.xz
 c43b7317978ad4051c053fc50a002bbda99eab15337465b7f54f9db33ea5428b 9094 

Processed: RFS: tinymux/2.12.0.10-1 -- text-based multi-user virtual world server

[Debian Bug Tracking System]

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

> close 968153
Bug #968153 [sponsorship-requests] RFS: tinymux/2.12.0.10-1 -- text-based 
multi-user virtual world server
Marked Bug as done
> stop
Stopping processing here.

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

Processed: RFS: libxau/1:1.0.9-1 [QA] -- X11 authorisation library (development headers)

[Debian Bug Tracking System]

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

> close 979527
Bug #979527 [sponsorship-requests] RFS: libxau/1:1.0.9-1 [QA] -- X11 
authorisation library (development headers)
Marked Bug as done
> stop
Stopping processing here.

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

Bug#859450: marked as done (reportbug: first reportbug with package after fresh install crashes)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 23:00:37 +0100
with message-id <98a9d049-e4b0-893c-7245-495436c5f...@web.de>
and subject line Re: reportbug: first reportbug with package after fresh 
install crashes
has caused the Debian Bug report #859450,
regarding reportbug: first reportbug with package after fresh install crashes
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.)


-- 
859450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 6.6.3
Severity: normal

Dear Maintainer,

   * What led up to the situation?
netboot test install (minimal testing)
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
aptitude install reportbug
reportbug installation-reports
   * What was the outcome of this action?
crash during bug submission (SMTP)
   * What outcome did you expect instead?
success or error

if reportbug is run without a package name and the initial questions are 
answerd first the problem goes away.

-- Package-specific info:
** Environment settings:
INTERFACE="text"

** /home/ben/.reportbugrc:
reportbug_version "6.6.3"
mode standard
ui text
realname "ben hildred"
email "426...@gmail.com"
no-cc
header "X-Debbugs-CC: 426...@gmail.com"
smtphost reportbug.debian.org

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages reportbug depends on:
ii  apt   1.0.9.8.4
ii  python2.7.9-1
ii  python-reportbug  6.6.3
pn  python:any

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail   
pn  debconf-utils
pn  debsums  
pn  dlocate  
pn  emacs23-bin-common | emacs24-bin-common  
ii  file 1:5.22+15-2+deb8u3
ii  gnupg1.4.18-7+deb8u3
pn  postfix | exim4 | mail-transport-agent   
pn  python-gtk2  
pn  python-gtkspell  
pn  python-urwid 
pn  python-vte   
pn  xdg-utils

Versions of packages python-reportbug depends on:
ii  apt   1.0.9.8.4
ii  python-debian 0.1.27
ii  python-debianbts  1.12
pn  python:any

python-reportbug suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 7.9.0

On 03 Apr 2017 ben hildred wrote:
> Package: reportbug
> Version: 6.6.3
> Severity: normal
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> netboot test install (minimal testing)
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> aptitude install reportbug
> reportbug installation-reports
>* What was the outcome of this action?
> crash during bug submission (SMTP)
>* What outcome did you expect instead?
> success or error

There are several things contributing:
1. No MTA installed or MTA only configured for local delivery
2. reportbug using the MTA by default if unconfigured
3. reportbug not detecting the 'missing MTA' case.

When a user reports a bug on reportbug, they are presented a list of
"common issues" which mentions the local delivery thing at the very top,
so I don't think this report is meant to reiterate this. I interpret it
as more likely referring to the third part, which has been fixed in
reportbug 7.9.0.--- End Message ---

Bug#981001: marked as done (hot-attach fails for qcow files with backing chain)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 22:03:58 +
with message-id 
and subject line Bug#981001: fixed in libvirt 7.0.0-1
has caused the Debian Bug report #981001,
regarding hot-attach fails for qcow files with backing chain
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.)


-- 
981001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvirt
Version: 6.9.0-4

Hi,
as reported to upstream in [1] use cases with snapshots or base-images
that use qcow files
with a backing chain will fail to hot attach e.g. via `virsh
attach-device`. Details and steps to reproduce in [1].

The reason is that apparmor in libvirt does not iterate over those
backing chains which was fixed in [2]. I'd ask to fix/avoid this issue
by applying that change for the most recent Debian version.

[1]: https://gitlab.com/libvirt/libvirt/-/issues/118
[2]: 
https://gitlab.com/libvirt/libvirt/-/commit/d51ad0008dc2df0257f69e767ab3e3c5fd1457ff

-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
--- End Message ---
--- Begin Message ---
Source: libvirt
Source-Version: 7.0.0-1
Done: Andrea Bolognani 

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

Debian distribution maintenance software
pp.
Andrea Bolognani  (supplier of updated libvirt 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, 28 Jan 2021 22:06:43 +0100
Source: libvirt
Architecture: source
Version: 7.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Libvirt Maintainers 

Changed-By: Andrea Bolognani 
Closes: 980334 981001
Changes:
 libvirt (7.0.0-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Andrea Bolognani ]
   * [561e347] libvirt-daemon-config-nwfilter: Install new nwfilters
   * [56231e3] patches: Add backport/meson-Fix-cross-building-[...].patch
 - Closes: #980334
 .
   [ Christian Ehrhardt ]
   * [6568c68] apparmor: allow hot-plug for qcow backing chains
 - Closes: #981001
   * [8173ce4] libvirt-daemon-config-*: reload libvirtd before restart
   * [dc21d88] systemd: Drop libvirtd dep from virt-guest-shutdown.target
 - Avoids reintroducing: #955216
Checksums-Sha1:
 fa5e7fc16b6a1f59c5c1056fc3c5c60a3cec6141 5646 libvirt_7.0.0-1.dsc
 c09839d3f74384d481f5ba3e90bdfe2192cff6ff 8567648 libvirt_7.0.0.orig.tar.xz
 9db3b67eeb02e04cd1936de86a44fa06ec56e5e1 833 libvirt_7.0.0.orig.tar.xz.asc
 4347c11ef2b8c820fcd9888db5988e5702a1a7f5 79448 libvirt_7.0.0-1.debian.tar.xz
 d81797cac98257ee2f3eb13883d2a1ba8932f6b6 13104 libvirt_7.0.0-1_source.buildinfo
Checksums-Sha256:
 1473e952bdde82450c1f37f7855670a529c81c2002e45d6be848714057bff25f 5646 
libvirt_7.0.0-1.dsc
 ca3833844d08c22867f1d1a46edc36bda7d6fe1a4f267e7d77100b79fc9ddd89 8567648 
libvirt_7.0.0.orig.tar.xz
 fb273c1bb38d29b7e40f0e34f1d6a7b3e1b6c30b91a37785450af524d0757819 833 
libvirt_7.0.0.orig.tar.xz.asc
 dd84cb55e012be7fe2cbcca991c2511ab439b63f0b19a8cd35098235d31303c0 79448 
libvirt_7.0.0-1.debian.tar.xz
 a073fb499634aaa8f87f64b6b8e0650f692017724cf675386a659707a62a575c 13104 
libvirt_7.0.0-1_source.buildinfo
Files:
 b0c160598548a3b160aa941cb652d0e6 5646 libs optional libvirt_7.0.0-1.dsc
 bceeaff5fc2660ce01fc64636e67263a 8567648 libs optional 
libvirt_7.0.0.orig.tar.xz
 fd3ac288bb6e7812751d33d5c5724e45 833 libs optional 
libvirt_7.0.0.orig.tar.xz.asc
 30c41d20b9aeb90a9401953af5a3f8f8 79448 libs optional 
libvirt_7.0.0-1.debian.tar.xz
 6d7ceeba5e5a5d229009f6484b1dd552 13104 libs optional 
libvirt_7.0.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEO48t9niVypx3EjLf954fxUKFg6wFAmATMosPHGVvZkBraXl1
a28ub3JnAAoJEPeeH8VChYOsdyUP/2RTWkFkI4EsriYUbQCjErQ/9lJ3dYSip5VQ
2Ed0zp7Y8+tloWun4lnhdCiv+33X+A1VbG+1iM99OWU7ztr9OpGT5IBfViWhfeCI
n8KS9qOoy+xZ0QnfUCZUUXZpbUI82m50pATUegNHtnk++r3OMGiIQmwf8ptT/Op/
IiYnj4zbE6c0edqtqsqYNKrUC0zs9QxxbQked8GR6mQ5oUS76AIfk6UmGf6NGvRF
5Bv2jFrEsbYz9hNqOoKAkL7qpmgVVRroH0oKlNcsSFkYm5vvOXqmfIBh2CNBe9Fv
0Qj8wES64YVDJs+1ihBwUB8Bx5IHg07qSfy+dEYnhPflcluh4edxULVyFIJMQ8Fu

Bug#980334: marked as done (libvirt FTCBFS: uses the build architecture compiler via dtrace)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 22:03:58 +
with message-id 
and subject line Bug#980334: fixed in libvirt 7.0.0-1
has caused the Debian Bug report #980334,
regarding libvirt FTCBFS: uses the build architecture compiler via dtrace
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.)


-- 
980334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvirt
Version: 6.9.0-1
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

We're getting closer to making libvirt cross buildable. A lot of
libvirt's dependencies have been fixed. One aspect that resides in
libvirt is dtrace. dtrace runs a compiler and defaults to the build
architecture compiler. As such it'll fail finding host architecture
headers and that happens to break the build. When running dtrace, one
must export the CC variable with a suitable value. Implementing this
with meson is not entirely trivial due to
https://github.com/mesonbuild/meson/issues/266. The attached patch
therefore implements the suggested workaround. Please consider applying
it to bring libvirt one step closer to being cross buildable.

Helmut
--- libvirt-6.9.0.orig/meson.build
+++ libvirt-6.9.0/meson.build
@@ -2063,6 +2063,7 @@
   if dtrace_prog.found()
 conf.set('WITH_DTRACE_PROBES', 1)
   endif
+  dtrace_command = [ 'env', 'CC=' + ' '.join(meson.get_compiler('c').cmd_array()), dtrace_prog ]
 endif
 
 if not get_option('host_validate').disabled() and host_machine.system() != 'windows'
--- libvirt-6.9.0.orig/src/meson.build
+++ libvirt-6.9.0/src/meson.build
@@ -60,14 +60,14 @@
 out_h,
 input: infile,
 output: out_h,
-command: [ dtrace_prog, '-o', '@OUTPUT@', '-h', '-s', '@INPUT@' ],
+command: dtrace_command + [ '-o', '@OUTPUT@', '-h', '-s', '@INPUT@' ],
   )
 
   dtrace_gen_objects += custom_target(
 out_o,
 input: infile,
 output: out_o,
-command: [ dtrace_prog, '-o', '@OUTPUT@', '-G', '-s', '@INPUT@' ],
+command: dtrace_command + [ '-o', '@OUTPUT@', '-G', '-s', '@INPUT@' ],
   )
 
   custom_target(
--- libvirt-6.9.0.orig/src/qemu/meson.build
+++ libvirt-6.9.0/src/qemu/meson.build
@@ -56,14 +56,14 @@
 out_h,
 input: infile,
 output: out_h,
-command: [ dtrace_prog, '-o', '@OUTPUT@', '-h', '-s', '@INPUT@' ],
+command: dtrace_command + [ '-o', '@OUTPUT@', '-h', '-s', '@INPUT@' ],
   )
 
   qemu_dtrace_gen_objects += custom_target(
 out_o,
 input: infile,
 output: out_o,
-command: [ dtrace_prog, '-o', '@OUTPUT@', '-G', '-s', '@INPUT@' ],
+command: dtrace_command + [ '-o', '@OUTPUT@', '-G', '-s', '@INPUT@' ],
   )
 
   qemu_dtrace_gen_stp = custom_target(
--- End Message ---
--- Begin Message ---
Source: libvirt
Source-Version: 7.0.0-1
Done: Andrea Bolognani 

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

Debian distribution maintenance software
pp.
Andrea Bolognani  (supplier of updated libvirt 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, 28 Jan 2021 22:06:43 +0100
Source: libvirt
Architecture: source
Version: 7.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Libvirt Maintainers 

Changed-By: Andrea Bolognani 
Closes: 980334 981001
Changes:
 libvirt (7.0.0-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Andrea Bolognani ]
   * [561e347] libvirt-daemon-config-nwfilter: Install new nwfilters
   * [56231e3] patches: Add backport/meson-Fix-cross-building-[...].patch
 - Closes: #980334
 .
   [ Christian Ehrhardt ]
   * [6568c68] apparmor: allow hot-plug for qcow backing chains
 - Closes: #981001
   * [8173ce4] libvirt-daemon-config-*: reload libvirtd before restart
   * [dc21d88] systemd: Drop libvirtd dep from virt-guest-shutdown.target
 - Avoids reintroducing: #955216
Checksums-Sha1:
 fa5e7fc16b6a1f59c5c1056fc3c5c60a3cec6141 5646 libvirt_7.0.0-1.dsc
 c09839d3f74384d481f5ba3e90bdfe2192cff6ff 8567648 libvirt_7.0.0.orig.tar.xz
 9db3b67eeb02e04cd1936de86a44fa06ec56e5e1 833 libvirt_7.0.0.orig.tar.xz.asc

Bug#971637: marked as done (prometheus-alertmanager: generate-ui.sh throws "ERROR: invalid option")

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 22:04:07 +
with message-id 
and subject line Bug#971637: fixed in prometheus-alertmanager 0.21.0+ds-3
has caused the Debian Bug report #971637,
regarding prometheus-alertmanager: generate-ui.sh throws "ERROR: invalid option"
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.)


-- 
971637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: prometheus-alertmanager
Version: 0.21.0+ds-2
Severity: normal
X-Debbugs-Cc: li...@d.sb

Dear Maintainer,

When I run /usr/share/prometheus/alertmanager/generate-ui.sh to install the web 
UI, the following error occurs:

Optimising source code...
ERROR: invalid option --output=/tmp/tmp.zMO98JwUjl/script.js

Changing line 26 from:

--mangle --output=$TMPDIR/script.js

to:

--mangle --output $TMPDIR/script.js

seems to fix the issue (that is, removing the `=` after `--output`).

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

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

Versions of packages prometheus-alertmanager depends on:
ii  init-system-helpers  1.58
ii  libc62.31-3
ii  systemd-sysv 246.4-1

prometheus-alertmanager recommends no packages.

prometheus-alertmanager suggests no packages.

-- Configuration Files:
/etc/prometheus/alertmanager.yml changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: prometheus-alertmanager
Source-Version: 0.21.0+ds-3
Done: Guillem Jover 

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated prometheus-alertmanager 
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, 28 Jan 2021 22:27:17 +0100
Source: prometheus-alertmanager
Architecture: source
Version: 0.21.0+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Guillem Jover 
Closes: 971637
Changes:
 prometheus-alertmanager (0.21.0+ds-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Daniel Swarbrick ]
   * Fix invocation of uglifyjs in maintainer-provided generate-ui.sh script.
 Reported by Daniel Lo Nigro. Closes: #971637.
 .
   [ Guillem Jover ]
   * Switch to debian/watch version 4
   * Indent debian/watch file
   * Do not enable DH_VERBOSE by default
   * Update version.BuildUser to match the Maintainer address
   * Use $(BUILDDIR) uniformly instead of the literal build/
   * Switch to dh-sequence-bash-completion
   * Remove nocheck handling from override_dh_auto_test
   * Mark -dev package as Multi-Arch:foreign
   * Use '' instead of `' in text
   * Switch from /var/run to /run
   * Move note about license location on Debian systems into a Comment field
   * Replace out-of-date Comment field about vendoring with Files-Excluded field
   * Set -dev package Section to golang
   * Switch to Standards-Version 4.5.1 (no changes needed)
   * Decapitalize synopsis first word
   * Add missing Depends on adduser in prometheus-alertmanager
   * Remove error suppression from postinst
   * Use $() instead of `` in init script
   * Remove unnecessary error suppression from init script
   * Run adduser unconditionally
   * Remove $syslog dependency from init script
   * Change systemd service Restart directive from always to on-failure
   * Fix NAME variable value in sysvinit init script
   * Rewrite init script using start-stop-daemon
   * Do not change pathname metadata if there are dpkg statoverrides in place
   * Update gitignore entries
   * Use execute_after_dh_auto_test instead of override_ and an explicit call
   * Remove unused adduser from Build-Depends
   * Remove unnecessary DH_GOPKG variable from 

Bug#816903: marked as done (reportbug: package dependencies listed as but they are installed)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 22:43:55 +0100
with message-id <1697fa0c-dbbd-6ede-cfee-659d3a72c...@web.de>
and subject line Re: reportbug: package dependencies listed as  but they 
are installed
has caused the Debian Bug report #816903,
regarding reportbug: package dependencies listed as  but they are 
installed
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.)


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


Package: reportbug
Version: 6.6.6
Severity: normal


i notice that many packages used with reportbug show dependencies listed as
 but they are installed

i.e. all 3 below report not installed

Package: debsums
State: installed
Automatically installed: no
Version: 2.1.2

Package: python-gtk2
State: installed
Automatically installed: no
Version: 2.24.0-4

but

$ aptitude show dlocate
No current or candidate version found for dlocate
Package: dlocate
State: not a real package

not consistent ...

?



-- Package-specific info:
** Environment settings:
INTERFACE="gtk2"

** /home/fulano/.reportbugrc:
reportbug_version "6.6.6"
mode standard
ui gtk2
offline
realname "Fulano Diego Perez"
email "fulanope...@cryptolab.net"
smtphost "mail.autistici.org"
smtpuser "fulanope...@cryptolab.net"
smtptls
http_proxy "http://127.0.0.1:8118;

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

Kernel: Linux 4.3.0-1-amd64
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages reportbug depends on:
ii  apt   1.2.3
ii  python-reportbug  6.6.6
pn  python:any

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
pn  debconf-utils  
pn  debsums
pn  dlocate
pn  emacs23-bin-common | emacs24-bin-common
ii  exim4  4.86-7
ii  exim4-daemon-light [mail-transport-agent]  4.86-7+b2
ii  file   1:5.25-2
ii  gnupg  1.4.20-4
pn  python-gtk2
pn  python-gtkspellcheck   
ii  python-urwid   1.3.1-2
ii  python-vte 1:0.28.2-5+b1
pn  xdg-utils  

Versions of packages python-reportbug depends on:
ii  apt   1.2.3
ii  file  1:5.25-2
ii  python-debian 0.1.27
ii  python-debianbts  2.6.0
pn  python:any

python-reportbug suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On 7 Mar 2016 Fulano Diego Perez wrote:
> 
> Package: reportbug
> Version: 6.6.6
> Severity: normal
> 
> 
> i notice that many packages used with reportbug show dependencies listed as
>  but they are installed
> 
> i.e. all 3 below report not installed
> 
> Package: debsums
> State: installed
> Automatically installed: no
> Version: 2.1.2
> 
> Package: python-gtk2
> State: installed
> Automatically installed: no
> Version: 2.24.0-4
> 
> but
> 
> $ aptitude show dlocate
> No current or candidate version found for dlocate
> Package: dlocate
> State: not a real package
> 
> not consistent ...
> 
> ?

There have been multiple related fixes in the five years since this bug
was reported, including recognition of held packages and coping properly
with arch qualifiers. Therefore I'm now assuming that this bug was quite
likely fixed some time ago and am closing it.

Thank you for the report. Please file a new one if you happen to run
into similar issues again; then we can have a closer look while the
problem is still fresh and reproducible.--- End Message ---

Bug#981084: marked as done (dh-elpa should provide dh-sequence-elpa)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 21:03:23 +
with message-id 
and subject line Bug#981084: fixed in dh-elpa 2.0.8
has caused the Debian Bug report #981084,
regarding dh-elpa should provide dh-sequence-elpa
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.)


-- 
981084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-elpa
Version: 2.0.6
Tags: patch

Please provide dh-sequence-elpa. Doing so allows using it declaratively.
Instead of adding "--with elpa" to the dh invocation, one can then add
dh-sequence-elpa to Build-Depends. Using the dependency technique, use
of the addon can be restricted to indep-only builds by moving it to
Build-Depends-Indep. Also the sequence can be conditionalized using
build profiles. (Though using build profiles requires fixing #981014.)

--- a/debian/control
+++ b/debian/control
@@ -27,6 +27,7 @@
  libtext-glob-perl,
  ${misc:Depends},
  ${perl:Depends},
+Provides: dh-sequence-elpa
 Description: Debian helper tools for packaging emacs lisp extensions
  This package provides a helper for packaging emacs lisp extensions
  in a way compatible with the GNU Emacs 'elpa' package repository.

Helmut
--- End Message ---
--- Begin Message ---
Source: dh-elpa
Source-Version: 2.0.8
Done: Sean Whitton 

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated dh-elpa 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, 28 Jan 2021 13:40:23 -0700
Source: dh-elpa
Architecture: source
Version: 2.0.8
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: Sean Whitton 
Closes: 981084
Changes:
 dh-elpa (2.0.8) unstable; urgency=medium
 .
   * Retry upload interrupted by Emacs crash.
 .
 dh-elpa (2.0.7) unstable; urgency=medium
 .
   * Mark dh-elpa as providing dh-sequence-elpa, for use in
 Build-Depends{,-Indep}, to enable implicit "--with elpa" rules
 (Closes: #981084).
 Thanks to Olivier Tilloy for the patch and others for discussion.
Checksums-Sha1:
 28cc3c21edc73c0c4c824643664f1b199493b7e5 1828 dh-elpa_2.0.8.dsc
 95fb8ba8246d75da672ca8cee9b92208c764bf77 22864 dh-elpa_2.0.8.tar.xz
Checksums-Sha256:
 d06da5ad7e7b9e1a3be3702d7b548f3da5567d0673b397f47435d5bd4a31d5eb 1828 
dh-elpa_2.0.8.dsc
 b656ff025a26d52fb56a6777b85218138b5f6e2687cbc979aa65ddadc113e014 22864 
dh-elpa_2.0.8.tar.xz
Files:
 df85d7b023784a825d242c906ad78642 1828 devel optional dh-elpa_2.0.8.dsc
 dcf48feaae22a37c7f48ea5cb3c3ef47 22864 devel optional dh-elpa_2.0.8.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmATIVAACgkQaVt65L8G
YkA0Qw/8CuiVcTBxRGyU/F/Ss4hdLQ3a4MqLwxiSXZR7dyMzLtCS51G15Hxsj28Y
cstoL8s+LxQ7H8YUIDwag91v/PIr9nT8jHuaIAr8Gun3N9/FeUKyMKbBF7mP7p7s
+PzqFU+rnqvCbediNHTrBuMSqE/xuaEt8MPNTNZwufapkVf2H3N/Z2hBdY7/04rE
ECdrFnKY14aYq9sPNOP0bieeGZq468FJ6bD+skSTFwYZSA4rRO6M+dDREbAtvDx9
DWWfcw+eNVDnC6QVEw1yvTHAC3Jr5l2abdoWXNul/IhwmwvPYL2QCIFp/tCFyM2d
dJKiursl6LFX6rmcvxJbc5vwYTJndOQkdCfVpfkUHnoF0CC/vzQEshiET6V9lpW9
rj0gqwpY+V2khvAbGhEk+wB6hDeuX1Xjjkg1mWnOehJDNCou4TNyB1SDbNUdZA6l
kCWTRXGVHqdyoBOYbrH+gCCl1SylHP6akCOlduqHbmu2lv3F6deldg/0531nxGnM
802VYD2kVlLJi2rFpXD56W6ePv/M7rgZy1Vtjh59MMB0oGQkxuFdPaUvgb5j1vJo
1kLLFPX3Zf3gls8pywSJPraPLIak9r6qwUYRxCYSo+O4bia6F750dkWZA7AFKXS+
d2Xv9rbX9HcfeKJfw1AkJC8hHJ1xuMmN76G+XQioJmVqy9v/gNQ=
=88O7
-END PGP SIGNATURE End Message ---

Bug#712415: marked as done (reportbug: doesn't notice installed foreign-architecture packages)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 21:46:46 +0100
with message-id <0dcf6aa4-f6ba-9e65-5929-a1cb46861...@web.de>
and subject line Re: reportbug don't find package in multiarch
has caused the Debian Bug report #712415,
regarding reportbug: doesn't notice installed foreign-architecture packages
to be marked as done.

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

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


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

Dear Maintainer,
When i want to write a reportbug for an packet it does not find the packet on
my system Sid AMD64
for sample i want to report a bug on the packet libkrb5-3 it say that the
packet is not on my system :
an  dpkg -l|grep libkrb5-3 give
rc  ia32-libkrb5-31.7dfsg~beta3-1~22
amd64MIT Kerberos runtime libraries
hi  libkrb5-3:amd64   1.10.1+dfsg-5
amd64MIT Kerberos runtime libraries
hi  libkrb5-3:i3861.10.1+dfsg-5
i386 MIT Kerberos runtime libraries
I think its a problem with multiarch.
Regards.
Philippe Merlin



-- Package-specific info:
** Environment settings:
INTERFACE="gtk2"

** /root/.reportbugrc:
reportbug_version "4.9"
mode standard
ui urwid
realname "merlin"
email "phil-deb1.mer...@laposte.net"
no-check-uid
smtphost "smtp.free.fr"

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages reportbug depends on:
ii  apt   0.9.8.2
ii  python2.7.5-2
ii  python-reportbug  6.4.4

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
pn  debconf-utils  
ii  debsums2.0.52
pn  dlocate
ii  emacs23-bin-common 23.4+1-4
ii  exim4-daemon-light [mail-transport-agent]  4.80-7
ii  file   1:5.14-2
ii  gnupg  1.4.12-7
ii  python-gtk22.24.0-3+b1
ii  python-gtkspell2.25.3-13
ii  python-urwid   1.1.1-1
ii  python-vte 1:0.28.2-5
ii  xdg-utils  1.1.0~rc1+git20111210-7

Versions of packages python-reportbug depends on:
ii  apt   0.9.8.2
ii  python2.7.5-2
ii  python-debian 0.1.21+nmu2
ii  python-debianbts  1.11
ii  python-support1.0.15

python-reportbug suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 7.6.0

On 15 Jun 2013 merlin wrote:
> Package: reportbug
> Version: 6.4.4
> Severity: important
> 
> Dear Maintainer,
> When i want to write a reportbug for an packet it does not find the packet on
> my system Sid AMD64
> for sample i want to report a bug on the packet libkrb5-3 it say that the
> packet is not on my system :
> an  dpkg -l|grep libkrb5-3 give
> rc  ia32-libkrb5-31.7dfsg~beta3-1~22
> amd64MIT Kerberos runtime libraries
> hi  libkrb5-3:amd64   1.10.1+dfsg-5
> amd64MIT Kerberos runtime libraries
> hi  libkrb5-3:i3861.10.1+dfsg-5
> i386 MIT Kerberos runtime libraries
> I think its a problem with multiarch.

I believe this was fixed in the meantime by two changes:
 - recognition of held packages as installed (in 7.5.1)
 - dpkg query with unambiguous package name (in 7.6.0)--- End Message ---

Bug#981297: marked as done (ITP: smbus2 -- another pure Python implementation of the python-smbus package)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 21:49:45 +0100
with message-id 

and subject line 
has caused the Debian Bug report #981297,
regarding ITP: smbus2 -- another pure Python implementation of the python-smbus 
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.)


-- 
981297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Anton Gladky 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: smbus2
  Version : 0.4.1
  Upstream Author : Karl-Petter Lindegaard
* URL : https://github.com/kplindegaard/smbus2
* License : MIT
  Programming Lang: Python
  Description : another pure Python implementation of the python-smbus
package

another pure Python implementation of the python-smbus package
Currently supported features are:
 Get i2c capabilities (I2C_FUNCS)
 SMBus Packet Error Checking (PEC) support
 read_byte
 write_byte
 read_byte_data
 write_byte_data
 read_word_data
 write_word_data
 read_i2c_block_data
 write_i2c_block_data
 write_quick
 process_call
 read_block_data
 write_block_data
 block_process_call
 i2c_rdwr - combined write/read transactions with repeated start
--- End Message ---
--- Begin Message ---
Anton
--- End Message ---

Bug#981084: marked as done (dh-elpa should provide dh-sequence-elpa)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 20:49:27 +
with message-id 
and subject line Bug#981084: fixed in dh-elpa 2.0.7
has caused the Debian Bug report #981084,
regarding dh-elpa should provide dh-sequence-elpa
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.)


-- 
981084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-elpa
Version: 2.0.6
Tags: patch

Please provide dh-sequence-elpa. Doing so allows using it declaratively.
Instead of adding "--with elpa" to the dh invocation, one can then add
dh-sequence-elpa to Build-Depends. Using the dependency technique, use
of the addon can be restricted to indep-only builds by moving it to
Build-Depends-Indep. Also the sequence can be conditionalized using
build profiles. (Though using build profiles requires fixing #981014.)

--- a/debian/control
+++ b/debian/control
@@ -27,6 +27,7 @@
  libtext-glob-perl,
  ${misc:Depends},
  ${perl:Depends},
+Provides: dh-sequence-elpa
 Description: Debian helper tools for packaging emacs lisp extensions
  This package provides a helper for packaging emacs lisp extensions
  in a way compatible with the GNU Emacs 'elpa' package repository.

Helmut
--- End Message ---
--- Begin Message ---
Source: dh-elpa
Source-Version: 2.0.7
Done: Sean Whitton 

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated dh-elpa 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, 28 Jan 2021 13:28:45 -0700
Source: dh-elpa
Architecture: source
Version: 2.0.7
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: Sean Whitton 
Closes: 981084
Changes:
 dh-elpa (2.0.7) unstable; urgency=medium
 .
   * Mark dh-elpa as providing dh-sequence-elpa, for use in
 Build-Depends{,-Indep}, to enable implicit "--with elpa" rules
 (Closes: #981084).
 Thanks to Olivier Tilloy for the patch and others for discussion.
Checksums-Sha1:
 0239506e6aa86246d79b38fa01d517fe2253459f 1828 dh-elpa_2.0.7.dsc
 595560617a75a432e587983204369e809011d52c 22832 dh-elpa_2.0.7.tar.xz
Checksums-Sha256:
 d55436fd5c341f97f25191be1b2e894b6d220a8893f3f3ffba6d0c1993c6cb6e 1828 
dh-elpa_2.0.7.dsc
 5f86caff06ba4a4eec2aa9ad50ff2a94372d3f15c07a87dd7f7aed7bf8c7c9b9 22832 
dh-elpa_2.0.7.tar.xz
Files:
 64cfd813724579a882804aa873f2ebe8 1828 devel optional dh-elpa_2.0.7.dsc
 e6984d6c26f19c92df716c2e935d6ed5 22832 devel optional dh-elpa_2.0.7.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmATH8AACgkQaVt65L8G
YkASaRAAqTMLC873eVb01usjof8o7qfIMnzSihPCnx7aUhSHFvDWYx+6eHJmvx1J
C2h2NIFqLmHv7e3gxu35zPJkXkBLFN1wUbJPKgRZF94lBOoIBhfupv6EQ/gr1Dau
wzhYWH+/eZjhrtkKtyQX+PW2YtoptaO06QsjjbdWHlzdDsSQbusmRGXyGax+Ed6N
E3hktBcBqUA3ZCWQRV0Lt37hXq1NBf7jTRTaKrgOqV7qTJfVwyLOfRp/cIA1CweY
S7fz2l7xZsA7Sw/pOdc0+UlEKNUhNq+RmQgAEJb+3EGlDPUxUAud/5SPkhaKkiSt
ra/Ol+XFEy+qt/pQmHvhM69jEVwiggn1CPN1nNhed+qlxTQxX5xhyvlxBYnrdXDV
tG+GEmeWl0UyalQwIinT8RJYHxzrofQWLdHPiXtnaaDCz9kiJUyzXeacoYB/ql8C
HeMtkIozOK8Vfr7DTOoWWfnBIGxyXZ00CIb2/QDGTjBdBbWkyNXc2vL8jzZjhrol
k0RuoLsxFib6Uwrtfk19GRPCVVWjit1kTw/lMGmtU0oGsBtkHPqxf7sP+663x0G7
J1FWfHLiaWTfaA4KZ4uXneuFhIPMWykLnSx9bldkV2NAjNu0VHGuk9/dW5Km0H0K
eKh3uuNyhCuZan71AN0bxwiU7xmIlEe8OPVjOlQCBMeGbueQKHk=
=OPUp
-END PGP SIGNATURE End Message ---

Bug#960436: marked as done (pyopencl: test need unavailable module pygpu_ndarray)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 21:47:28 +0100
with message-id 
and subject line build-time tests are now running
has caused the Debian Bug report #960436,
regarding pyopencl: test need unavailable module pygpu_ndarray
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.)


-- 
960436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyopencl
Version: 2019.1.1-1
Severity: important

Hi,

I tried enabling running the test suite at build time via pocl
(see attached patch), but the tests require an unavailable module
pygpu_ndarray: 

   dh_auto_test -O--buildsystem=pybuild
pybuild --test -i python{version} -p 3.8
D: pybuild pybuild:560: version: 4.20200315
D: pybuild pybuild:561: ['/usr/bin/pybuild', '--test', '-i', 'python{version}', 
'-p', '3.8']
D: pybuild pybuild:36: cfg: Namespace(after_build=None, after_clean=None, 
after_configure=None, after_install=None, after_test=None, before_build=None, 
before_clean=None, before_configure=None, before_install=None, 
before_test=None, build_args=None, build_only=False, clean_args=None, 
clean_only=False, configure_args=None, configure_only=False, 
custom_tests=False, destdir='debian/tmp', detect_only=False, 
dir='/build/pyopencl-2019.1.1', disable=None, ext_destdir=None, 
ext_pattern='\\.so(\\.[^/]*)?$', ext_sub_pattern=None, ext_sub_repl=None, 
install_args=None, install_dir=None, install_only=False, 
interpreter=['python{version}'], list_systems=False, name=None, 
print_args=None, quiet=False, really_quiet=False, system=None, test_args=None, 
test_nose=False, test_nose2=False, test_only=True, test_pytest=False, 
test_tox=False, verbose=True, versions=['3.8'])
D: pybuild tools:232: invoking: /usr/bin/dpkg-architecture
D: pybuild pybuild:131: detected build system: distutils (certainty: 61%)
I: pybuild base:217: cd /build/pyopencl-2019.1.1/.pybuild/cpython3_3.8/build; 
python3.8 -m unittest discover -v 
D: pybuild tools:232: invoking: cd 
/build/pyopencl-2019.1.1/.pybuild/cpython3_3.8/build; python3.8 -m unittest 
discover -v 
pyopencl.compyte.ndarray.test_gpu_elemwise (unittest.loader._FailedTest) ... 
ERROR
pyopencl.compyte.ndarray.test_gpu_ndarray (unittest.loader._FailedTest) ... 
ERROR

==
ERROR: pyopencl.compyte.ndarray.test_gpu_elemwise (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: 
pyopencl.compyte.ndarray.test_gpu_elemwise
Traceback (most recent call last):
  File "/usr/lib/python3.8/unittest/loader.py", line 436, in _find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python3.8/unittest/loader.py", line 377, in 
_get_module_from_name
__import__(name)
  File 
"/build/pyopencl-2019.1.1/.pybuild/cpython3_3.8/build/pyopencl/compyte/ndarray/test_gpu_elemwise.py",
 line 6, in 
import pygpu_ndarray as gpu_ndarray
ModuleNotFoundError: No module named 'pygpu_ndarray'


==
ERROR: pyopencl.compyte.ndarray.test_gpu_ndarray (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: 
pyopencl.compyte.ndarray.test_gpu_ndarray
Traceback (most recent call last):
  File "/usr/lib/python3.8/unittest/loader.py", line 436, in _find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python3.8/unittest/loader.py", line 377, in 
_get_module_from_name
__import__(name)
  File 
"/build/pyopencl-2019.1.1/.pybuild/cpython3_3.8/build/pyopencl/compyte/ndarray/test_gpu_ndarray.py",
 line 7, in 
import pygpu_ndarray as gpu_ndarray
ModuleNotFoundError: No module named 'pygpu_ndarray'


--
Ran 2 tests in 0.000s

FAILED (errors=2)
E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1: cd 
/build/pyopencl-2019.1.1/.pybuild/cpython3_3.8/build; python3.8 -m unittest 
discover -v 


Andreas
>From 0f38742a66c287556f14ecb074a435d1571416ea Mon Sep 17 00:00:00 2001
From: Andreas Beckmann 
Date: Tue, 12 May 2020 15:49:02 +0200
Subject: [PATCH] run tests using pocl

---
 debian/changelog | 1 +
 debian/control   | 3 +++
 debian/rules | 3 ---
 3 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 9f910a6..598232b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -9,6 +9,7 @@ pyopencl (2019.1.1-2) 

Processed: src:metastudent-data: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.0.1-5
Bug #981294 [src:metastudent-data] src:metastudent-data: fails to migrate to 
testing for too long: autopkgtest regression
Marked as fixed in versions metastudent-data/2.0.1-5.
Bug #981294 [src:metastudent-data] src:metastudent-data: fails to migrate to 
testing for too long: autopkgtest regression
Marked Bug as done
> block -1 by 981293
Bug #981294 {Done: Paul Gevers } [src:metastudent-data] 
src:metastudent-data: fails to migrate to testing for too long: autopkgtest 
regression
981294 was not blocked by any bugs.
981294 was not blocking any bugs.
Added blocking bug(s) of 981294: 981293

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

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

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 19:49:08 +
with message-id 
and subject line Bug#980667: fixed in node-d3-transition 1.3.2-2
has caused the Debian Bug report #980667,
regarding node-d3-transition: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 1
to be marked as done.

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

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


-- 
980667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-d3-transition
Version: 1.3.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 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 '/<>'
> rollup -c
> 
> src/index.js → dist/d3-transition.js...
> created dist/d3-transition.js in 143ms
> 
> src/index.js → dist/d3-transition.min.js...
> created dist/d3-transition.min.js in 681ms
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/d3-transition
>   /bin/sh -ex debian/tests/pkg-js/test
> + tape test/**/*-test.js
> TAP version 13
> # d3.active(node) returns null if the specified node has no active transition 
> with the null name
> ok 1 should be equal
> ok 2 should be equal
> ok 3 should be equal
> ok 4 should be equal
> # d3.active(node, null) returns null if the specified node has no active 
> transition with the null name
> ok 5 should be equal
> ok 6 should be equal
> ok 7 should be equal
> ok 8 should be equal
> # d3.active(node, undefined) returns null if the specified node has no active 
> transition with the null name
> ok 9 should be equal
> ok 10 should be equal
> ok 11 should be equal
> ok 12 should be equal
> # d3.active(node, name) returns null if the specified node has no active 
> transition with the specified name
> ok 13 should be equal
> ok 14 should be equal
> ok 15 should be equal
> ok 16 should be equal
> ok 17 should be equal
> # d3.active(node) returns the active transition on the specified node with 
> the null name
> ok 18 should be equivalent
> ok 19 should be equivalent
> ok 20 should be equal
> ok 21 should be equal
> ok 22 should be equivalent
> ok 23 should be equivalent
> ok 24 should be equal
> ok 25 should be equal
> ok 26 should be equivalent
> ok 27 should be equivalent
> ok 28 should be equal
> ok 29 should be equal
> ok 30 should be equivalent
> ok 31 should be equivalent
> ok 32 should be equal
> ok 33 should be equal
> # d3.active(node, name) returns the active transition on the specified node 
> with the specified name
> ok 34 should be equivalent
> ok 35 should be equivalent
> ok 36 should be equal
> ok 37 should be equal
> ok 38 should be equivalent
> ok 39 should be equivalent
> ok 40 should be equal
> ok 41 should be equal
> ok 42 should be equivalent
> ok 43 should be equivalent
> ok 44 should be equal
> ok 45 should be equal
> ok 46 should be equivalent
> ok 47 should be equivalent
> ok 48 should be equal
> ok 49 should be equal
> # transition.on("start", error) terminates the transition
> ok 50 should be equal
> # transition.on("start", error) with delay terminates the transition
> ok 51 should be equal
> # transition.tween("foo", error) terminates the transition
> ok 52 should be equal
> # transition.tween("foo", error) with delay terminates the transition
> ok 53 should be equal
> # transition.tween("foo", deferredError) terminates the transition
> ok 54 should be equal
> # transition.on("end", error) terminates the transition
> ok 55 should be equal
> # d3.interrupt(node) cancels any pending transitions on the specified node
> ok 56 should be equal
> ok 57 should be equal
> ok 58 should be equal
> # selection.interrupt(name) only cancels pending transitions with the 
> specified name
> ok 59 should be equal
> ok 60 should be equal
> ok 61 should be equal
> ok 62 should be equal
> # selection.interrupt() returns the selection
> ok 63 should be equal
> # selection.interrupt() cancels any pending transitions on the selected 
> elements
> ok 64 should be equal
> ok 65 should be equal
> ok 66 should be equal
> ok 67 should be equal
> # selection.interrupt() only cancels pending transitions with the null name
> ok 68 should be equal
> ok 69 should be equal
> ok 70 should be equal
> ok 71 should be equal
> ok 72 should be equal
> # selection.interrupt(null) only cancels pending transitions with the null 
> name
> ok 73 should be equal
> ok 74 should be equal
> ok 75 should be equal
> ok 76 should be 

Bug#974839: marked as done (q2-feature-classifier: unsatisfiable build-dependency)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 19:49:16 +
with message-id 
and subject line Bug#974839: fixed in q2-feature-classifier 2020.11.1-1
has caused the Debian Bug report #974839,
regarding q2-feature-classifier: unsatisfiable build-dependency
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.)


-- 
974839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: q2-feature-classifier
Version: 2019.4.0-1
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

q2-feature-classifier build-depends both on python3-pandas
(indirectly, via a dependency of qiime), and on q2-types.

python3-pandas version 1.1.4+dfsg-1 Breaks q2-types (<< 2019.10.0-1.1~).
However, the only version of q2-types in the archive is 2019.10.0-1.

-Ralf.
--- End Message ---
--- Begin Message ---
Source: q2-feature-classifier
Source-Version: 2020.11.1-1
Done: Étienne Mollier 

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated 
q2-feature-classifier 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, 28 Jan 2021 20:24:05 +0100
Source: q2-feature-classifier
Architecture: source
Version: 2020.11.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 974839
Changes:
 q2-feature-classifier (2020.11.1-1) unstable; urgency=medium
 .
   [ Liubov Chuprikova ]
   * New upstream version
   * Respect DEB_BUILD_OPTIONS in override_dh_auto_test target
   * Add new (Build-)Depends
 .
   [ Andreas Tille ]
   * Standards-Version: 4.5.1 (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, Repository,
 Repository-Browse.
   * Build-Depends: q2-taxa
 Closes: #974839
 .
   [ Étienne Mollier ]
   * Add build directory to PYTHONPATH for dh_auto_test.
   * Add vsearch.patch to fix --search_exact invalid options.
   * Update versioned dependencies and dropped redundant ones.
   * Add myself to uploaders.
Checksums-Sha1:
 b351bc5758f27c1709f38ad610a20a835eb2e11e 2395 
q2-feature-classifier_2020.11.1-1.dsc
 7cfb67ef3de45972143e24a712a0366ba03dc175 397708 
q2-feature-classifier_2020.11.1.orig.tar.gz
 273b7a0b8c820ee9bdf36fb1232a530a1092bb0a 5800 
q2-feature-classifier_2020.11.1-1.debian.tar.xz
 187c8273b5b3f9dcdfda7f0a97d0669e2dd193b5 13065 
q2-feature-classifier_2020.11.1-1_amd64.buildinfo
Checksums-Sha256:
 fba9bfa030ed64bf6cb2178a44cdb1b02635a9ed70df77fc0aa26e08d685e902 2395 
q2-feature-classifier_2020.11.1-1.dsc
 d8009259e9abe4d346338d34753187ab3a45317efdeffbcddf11b5d356e3cbef 397708 
q2-feature-classifier_2020.11.1.orig.tar.gz
 14bc69bd87d8c433500ecf04e67d426846306e3f68881d07c69c963819919207 5800 
q2-feature-classifier_2020.11.1-1.debian.tar.xz
 3f10a030afc98f6b53cc1f708b30f0efba03e75644b9009c02035dc91477c651 13065 
q2-feature-classifier_2020.11.1-1_amd64.buildinfo
Files:
 2f59a7da526e0453ba18eb2b3c3afb25 2395 science optional 
q2-feature-classifier_2020.11.1-1.dsc
 172a36c58bc2ade785b553cd8d0c8dda 397708 science optional 
q2-feature-classifier_2020.11.1.orig.tar.gz
 0d71568c24b7b2d5ee160ed8217fa726 5800 science optional 
q2-feature-classifier_2020.11.1-1.debian.tar.xz
 a84c11a01867f1d9f605a9503b1ba927 13065 science optional 
q2-feature-classifier_2020.11.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmATEZ4ACgkQeTz2fo8N
EdrsVRAAtEWYjpWEmb1Yv24vvEZ3nBWL3mWZ5yZqAjkKfMo4a3vufXUAeWT2cNpZ
tl+EQV2NftyRZIVAPrBD4CIIKnPNMi8O96x+Tf9whRl9KlQP2rojawQm5n64vRBW
UB9xCzyNyvYYbPifVq17T3Cqylm67+C63WSTQOt59lL5lWAd0AUAWcIUgD/BZEtF
SAgShdmdKC42N5XZJtPHHNciQXcoqt1L9sFyl3aEt+Vey/QjHVGXhnwx+WjxJJKs
sZMSVDcDtm6LbKH5W++C1nprksatHvOJ5OUUWALC1a8K2tIvQoCRGi0C82yJ0W8X
Vxx8AQdqTgXHe9eP0/EQSYiqiDbzkL0UXT0XPRprF/pMAtQnYcY71BHYdsFqdBsP

Bug#981286: marked as done (node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv')

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 19:37:01 +
with message-id 
and subject line Bug#981286: fixed in node-mimic-response 3.1.0-3
has caused the Debian Bug report #981286,
regarding node-mimic-response: autopkgtest regression on !amd64: Cannot find 
module 'iconv'
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.)


-- 
981286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-mimic-response
Version: 3.1.0-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
node-mimic-responsefrom testing3.1.0-2
all others from testingfrom testing

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

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/arm64/n/node-mimic-response/10071183/log.gz

autopkgtest [16:14:29]: test pkg-js-autopkgtest: [---
# Using package.json
# Node module name is mimic-response
# Build files found:
# Test files found: test.js
# Files/dir to be installed from source: test.js
# Copy test files
# Copy debian/tests/pkg-js content
'debian/tests/pkg-js' ->
'/tmp/autopkgtest-lxc.ahpnqplz/downtmp/autopkgtest_tmp/smokeVIaf0R/debian/tests/pkg-js'
'debian/tests/pkg-js/test' ->
'/tmp/autopkgtest-lxc.ahpnqplz/downtmp/autopkgtest_tmp/smokeVIaf0R/debian/tests/pkg-js/test'
# Found debian/tests/test_modules directory, let's copy it
'/tmp/autopkgtest-lxc.ahpnqplz/downtmp/autopkgtest_tmp/smokeVIaf0R/node_modules/create-cert'
-> '../debian/tests/test_modules/create-cert'
'/tmp/autopkgtest-lxc.ahpnqplz/downtmp/autopkgtest_tmp/smokeVIaf0R/node_modules/create-test-server'
-> '../debian/tests/test_modules/create-test-server'
'/tmp/autopkgtest-lxc.ahpnqplz/downtmp/autopkgtest_tmp/smokeVIaf0R/node_modules/es6-promisify'
-> '../debian/tests/test_modules/es6-promisify'
'/tmp/autopkgtest-lxc.ahpnqplz/downtmp/autopkgtest_tmp/smokeVIaf0R/node_modules/p-event'
-> '../debian/tests/test_modules/p-event'
'/tmp/autopkgtest-lxc.ahpnqplz/downtmp/autopkgtest_tmp/smokeVIaf0R/node_modules/pem'
-> '../debian/tests/test_modules/pem'
# Searching module in /usr/lib/nodejs/mimic-response
# Searching module in /usr/lib/*/nodejs/mimic-response
# Searching module in /usr/share/nodejs/mimic-response
# Found /usr/share/nodejs/mimic-response
# Searching files to link in /usr/share/nodejs/mimic-response
'./index.d.ts' -> '/usr/share/nodejs/mimic-response/index.d.ts'
'./index.js' -> '/usr/share/nodejs/mimic-response/index.js'
'./package.json' -> '/usr/share/nodejs/mimic-response/package.json'
# Launch debian/tests/pkg-js/test with sh -ex
+ jest --ci --testRegex test.js
FAIL ./test.js
  ● Test suite failed to run

Cannot find module 'iconv' from
'../../../../../usr/share/nodejs/raw-body/index.js'

Require stack:
  /usr/share/nodejs/raw-body/index.js
  /usr/share/nodejs/body-parser/lib/read.js
  /usr/share/nodejs/body-parser/lib/types/json.js
  /usr/share/nodejs/body-parser/index.js
  /usr/share/nodejs/express/lib/express.js
  /usr/share/nodejs/express/index.js
  debian/tests/test_modules/create-test-server/src/index.js
  test.js

  235 |
  236 | const relativePath = (0,
_slash().default)(path().relative(this._options.rootDir, from)) || '.';
> 237 | throw new _ModuleNotFoundError.default(`Cannot find
module '${moduleName}' from '${relativePath}'`, moduleName);
  |   ^
  238 |   }
  239 |
  240 |   _isAliasModule(moduleName) {

  at Resolver.resolveModule
(../../../../../usr/share/nodejs/jest-resolve/build/index.js:237:11)
  at Object.
(../../../../../usr/share/nodejs/raw-body/index.js:17:13)

Test Suites: 1 failed, 1 total
Tests:   0 total
Snapshots:   0 total
Time:4.099 s
Ran all test suites.
autopkgtest [16:14:35]: test pkg-js-autopkgtest: ---]



OpenPGP_signature

Bug#981134: marked as done (hwloc: reduce Build-Depends)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 19:36:55 +
with message-id 
and subject line Bug#981134: fixed in hwloc 2.4.1~rc1+dfsg-1
has caused the Debian Bug report #981134,
regarding hwloc: reduce Build-Depends
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.)


-- 
981134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hwloc
Version: 2.4.0+dfsg-3
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

hwloc participates in dependency loops relevant to architecture
bootstrap. Rather than work on such a difficult problem, I looked for
easily droppable dependencies. It turns out that on glibc systems, hwloc
prefers dlopen over ltdl, so we can restrict the dependency to !glibc
systems. The libxml2-utils dependency is used for xmllint, which is used
for tests. It can be annotated . Finally, the documentation is
not rebuilt during package build. As a result, doxygen-latex, transfig
and w3m are unused and can be dropped. Please consider applying the
attached patch. Alternatively, consider actually rebuilding the
documentation during package build.

Helmut
diff --minimal -Nru hwloc-2.4.0+dfsg/debian/changelog 
hwloc-2.4.0+dfsg/debian/changelog
--- hwloc-2.4.0+dfsg/debian/changelog   2020-12-31 15:21:52.0 +0100
+++ hwloc-2.4.0+dfsg/debian/changelog   2021-01-26 14:20:03.0 +0100
@@ -1,3 +1,15 @@
+hwloc (2.4.0+dfsg-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Reduce Build-Depends: (Closes: #-1)
++ Restrict libltdl-dev dependency to !glibc systems as hwloc prefers
+  dlopen for glibc.
++ Annotate test dependency libxml2-utils .
++ Drop dependencies doxygen-latex, transfig and w3m as the documentation
+  is not rebuilt during package build anyway.
+
+ -- Helmut Grohne   Tue, 26 Jan 2021 14:20:03 +0100
+
 hwloc (2.4.0+dfsg-3) unstable; urgency=medium
 
   * control: Update packaging URL.
diff --minimal -Nru hwloc-2.4.0+dfsg/debian/control 
hwloc-2.4.0+dfsg/debian/control
--- hwloc-2.4.0+dfsg/debian/control 2020-12-31 14:41:28.0 +0100
+++ hwloc-2.4.0+dfsg/debian/control 2021-01-26 14:20:03.0 +0100
@@ -1,16 +1,15 @@
 Source: hwloc
 Priority: optional
 Maintainer: Samuel Thibault 
-Build-Depends: debhelper-compat (= 12), dh-exec, libltdl-dev,
+Build-Depends: debhelper-compat (= 12), dh-exec, libltdl-dev [!gnu-any-any],
   valgrind [amd64 arm64 armhf i386 mips64el mipsel ppc64el s390x powerpc 
ppc64],
-  libcairo2-dev, libx11-dev, libxml2-dev, libxml2-utils, libncurses5-dev,
+  libcairo2-dev, libx11-dev, libxml2-dev, libxml2-utils , 
libncurses5-dev,
   libnuma-dev [linux-any],
   libxnvctrl-dev,
   libpciaccess-dev, libudev-dev [linux-any], pkg-config,
   ocl-icd-opencl-dev [!hurd-i386] | opencl-dev, opencl-headers,
-  autoconf (>= 2.63), w3m,
+  autoconf (>= 2.63),
   dpkg-dev (>= 1.16)
-Build-Depends-Indep: doxygen-latex, transfig
 Build-Conflicts: autoconf2.13
 Standards-Version: 4.5.0
 Section: libs
--- End Message ---
--- Begin Message ---
Source: hwloc
Source-Version: 2.4.1~rc1+dfsg-1
Done: Samuel Thibault 

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated hwloc 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, 28 Jan 2021 20:27:41 +0100
Source: hwloc
Binary: hwloc hwloc-dbgsym hwloc-nox hwloc-nox-dbgsym libhwloc-common 
libhwloc-dev libhwloc-doc libhwloc-plugins libhwloc-plugins-dbgsym libhwloc15 
libhwloc15-dbgsym
Architecture: source
Version: 2.4.1~rc1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Samuel Thibault 
Changed-By: Samuel Thibault 
Description:
 hwloc  - Hierarchical view of the machine - utilities
 hwloc-nox  - Hierarchical view of the machine - non-X version of utilities
 libhwloc-common - Hierarchical view of the machine - common files
 libhwloc-dev - Hierarchical view of the machine - static libs and headers
 libhwloc-doc - Hierarchical view of the machine - 

Bug#980712: marked as done (golang-github-dvsekhvalnov-jose2go: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/dvsekhvalnov/jose2go github.com/dvsekhvalnov/

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 18:37:45 +
with message-id 
and subject line Bug#980712: fixed in golang-github-dvsekhvalnov-jose2go 1.5-1
has caused the Debian Bug report #980712,
regarding golang-github-dvsekhvalnov-jose2go: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/dvsekhvalnov/jose2go github.com/dvsekhvalnov/jose2go/aes 
github.com/dvsekhvalnov/jose2go/arrays 
github.com/dvsekhvalnov/jose2go/base64url 
github.com/dvsekhvalnov/jose2go/compact github.com/dvsekhvalnov/jose2go/kdf 
github.com/dvsekhvalnov/jose2go/keys/ecc 
github.com/dvsekhvalnov/jose2go/keys/rsa 
github.com/dvsekhvalnov/jose2go/padding returned exit code 1
to be marked as done.

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

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


-- 
980712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-dvsekhvalnov-jose2go
Version: 1.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 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 --buildsystem=golang --with=golang
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
>dh_auto_build -O--buildsystem=golang
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 
> github.com/dvsekhvalnov/jose2go github.com/dvsekhvalnov/jose2go/aes 
> github.com/dvsekhvalnov/jose2go/arrays 
> github.com/dvsekhvalnov/jose2go/base64url 
> github.com/dvsekhvalnov/jose2go/compact github.com/dvsekhvalnov/jose2go/kdf 
> github.com/dvsekhvalnov/jose2go/keys/ecc 
> github.com/dvsekhvalnov/jose2go/keys/rsa 
> github.com/dvsekhvalnov/jose2go/padding
> internal/unsafeheader
> internal/cpu
> internal/bytealg
> runtime/internal/atomic
> runtime/internal/sys
> runtime/internal/math
> runtime
> internal/reflectlite
> errors
> internal/race
> sync/atomic
> sync
> io
> unicode
> unicode/utf8
> bytes
> strings
> bufio
> math/bits
> math
> strconv
> reflect
> sort
> internal/fmtsort
> internal/oserror
> syscall
> internal/syscall/unix
> time
> internal/poll
> internal/syscall/execenv
> internal/testlog
> os
> fmt
> compress/flate
> hash
> crypto
> crypto/internal/subtle
> crypto/subtle
> encoding/binary
> crypto/cipher
> crypto/aes
> math/rand
> math/big
> crypto/elliptic
> crypto/internal/randutil
> crypto/sha512
> unicode/utf16
> encoding/asn1
> vendor/golang.org/x/crypto/cryptobyte/asn1
> vendor/golang.org/x/crypto/cryptobyte
> crypto/ecdsa
> crypto/hmac
> crypto/rand
> crypto/rsa
> crypto/sha1
> crypto/sha256
> encoding
> encoding/base64
> encoding/json
> github.com/dvsekhvalnov/jose2go/base64url
> github.com/dvsekhvalnov/jose2go/arrays
> github.com/dvsekhvalnov/jose2go/aes
> github.com/dvsekhvalnov/jose2go/compact
> github.com/dvsekhvalnov/jose2go/kdf
> crypto/des
> crypto/dsa
> crypto/ed25519/internal/edwards25519
> crypto/ed25519
> crypto/md5
> encoding/hex
> crypto/x509/pkix
> encoding/pem
> path/filepath
> io/ioutil
> context
> vendor/golang.org/x/net/dns/dnsmessage
> internal/nettrace
> internal/singleflight
> runtime/cgo
> net
> net/url
> crypto/x509
> github.com/dvsekhvalnov/jose2go/keys/ecc
> github.com/dvsekhvalnov/jose2go/padding
> github.com/dvsekhvalnov/jose2go
> github.com/dvsekhvalnov/jose2go/keys/rsa
>dh_auto_test -O--buildsystem=golang
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 
> in use)
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
> github.com/dvsekhvalnov/jose2go github.com/dvsekhvalnov/jose2go/aes 
> github.com/dvsekhvalnov/jose2go/arrays 
> github.com/dvsekhvalnov/jose2go/base64url 
> github.com/dvsekhvalnov/jose2go/compact github.com/dvsekhvalnov/jose2go/kdf 
> github.com/dvsekhvalnov/jose2go/keys/ecc 
> github.com/dvsekhvalnov/jose2go/keys/rsa 
> github.com/dvsekhvalnov/jose2go/padding
> === RUN   Test
> 
> invalid sign 'alg' header err= jwt.Decode(): required 'alg' header is missing 
> or of invalid type
> 
> missing sign 'alg' header err= jwt.Decode(): required 'alg' header is missing 
> or of invalid type
> 
> two phased err= Test error
> 
> invalid encrypt 'alg' header err= jwt.Decode(): required 'alg' header is 
> missing or of invalid type
> 

Bug#975389: marked as done (RFS: dpf-plugins/1.4-1 [ITP] -- Audio plugin collection from DISTRHO (metapackage))

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 19:12:32 +0100
with message-id 
and subject line Closing RFS for dpf-plugins
has caused the Debian Bug report #975389,
regarding RFS: dpf-plugins/1.4-1 [ITP] -- Audio plugin collection from DISTRHO 
(metapackage)
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.)


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

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "dpf-plugins":

* Package name : dpf-plugins
Version : 1.3+git8ae021b-1
Upstream Author : Filipe Coelho
* URL : https://github.com/falkTX/DPF-Plugins
* License : GPL-2+, LGPL-3+, LGPL-2.1+, ZLIB, ISC, MIT, bitstream-vera, 
GPL-3+

* Vcs : https://salsa.debian.org/multimedia-team/dpf-plugins
Section : sound

It builds those binary packages:

dpf-plugins-dssi - Audio plugin collection from DISTRHO (DSSI plugins)
dpf-plugins-vst - Audio plugin collection from DISTRHO (VST2 plugins)
dpf-plugins-lv2 - Audio plugin collection from DISTRHO (LV2 plugins)
dpf-plugins-ladspa - Audio plugin collection from DISTRHO (LADSPA plugins)
dpf-plugins-common - Audio plugin collection from DISTRHO (common files)
dpf-plugins - Audio plugin collection from DISTRHO (metapackage)

To access further information about this package, please visit the 
following URL:


https://mentors.debian.net/package/dpf-plugins/

Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/d/dpf-plugins/dpf-plugins_1.3+git8ae021b-1.dsc


Changes for the initial release:

dpf-plugins (1.3+git8ae021b-1) unstable; urgency=medium
..
* Initial debian release (Closes: #953129)
+ Merge with 1.3+git8ae021b-0ubuntu1 release
+ Use dh-compat instead of debian/compat and bump to 13
+ Change Maintainer to Debian Multimedia Maintainers
+ Remove XSBC-Original-Maintainer field, not needed for debian
+ Remove unused ${shlibs:Depends} from the dpf-plugins package
+ Add Vcs-Git & Vcs-Browser fields
+ Add myself as an uploader
+ Bump S-V to 4.5.1
+ Set RRR: no
+ Fix description of dpf-plugins-vst
+ Update the license texts for the *gpl* licenses in d/copyright
+ Fix misspellings of the path names in d/copyright
+ Add myself to the d/ section of d/copyright
+ Add lintian-overrides
+ d/rules: Add DEB_BUILD_MAINT_OPTIONS for hardening
+ d/rules: Fix stripping
+ Add d/upstream/metadata
+ Fix d/watch file

Regards,
Dennis
--- End Message ---
--- Begin Message ---
Hi Dennis,

I just uploaded dpf-plugins. I am closing the RFS bug manually because
the package might sit in the NEW queue for a while.

Thanks for packaging dpf-plugins. I will take a look at your other
multimedia packages with RFS bugs in the coming days.

-- 
Regards,

Ross Gammon
FBEE 0190 904F 1EA0 BA6A  300E 53FE 7BBD A689 10FC



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#450736: marked as done (psi: Sending GPG-encrypted messages is delayed by 4 seconds)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 21:15:27 +0300
with message-id <539521611857...@mail.yandex.ru>
and subject line Outdated
has caused the Debian Bug report #450736,
regarding psi: Sending GPG-encrypted messages is delayed by 4 seconds
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.)


-- 
450736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: psi
Version: 0.11-1
Severity: normal

When enabling GPG encryption and sending a message it takes 4 seconds
until the message gets sent. During that time the program is
unresponsive. This does not happen when sending messages without
encryption. This also did not happen with Psi 0.10.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-2-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages psi depends on:
ii  libaspell15 0.60.5-1 GNU Aspell spell-checker runtime l
ii  libc6   2.6.1-6  GNU C Library: Shared libraries
ii  libgcc1 1:4.2.2-3GCC support library
ii  libqt4-core 4.3.2-1  Qt 4 core non-GUI functionality ru
ii  libqt4-gui  4.3.2-1  Qt 4 core GUI functionality runtim
ii  libqt4-qt3support   4.3.2-1  Qt 3 compatibility library for Qt 
ii  libssl0.9.8 0.9.8g-2 SSL shared libraries
ii  libstdc++6  4.2.2-3  The GNU Standard C++ Library v3
ii  libx11-62:1.0.3-7X11 client-side library
ii  libxext61:1.0.3-2X11 miscellaneous extension librar
ii  libxss1 1:1.1.2-1X11 Screen Saver extension library
ii  zlib1g  1:1.2.3.3.dfsg-7 compression library - runtime

Versions of packages psi recommends:
ii  libqca2-plugin-ossl   0.1~20070904-3 QCA OSSL plugin for libqca2
ii  sox   14.0.0-5   Swiss army knife of sound processi

-- debconf-show failed


--- End Message ---
--- Begin Message ---
.--- End Message ---

Bug#198577: marked as done (psi: multiple groups per user)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 21:14:12 +0300
with message-id <551021611857...@mail.yandex.ru>
and subject line Done
has caused the Debian Bug report #198577,
regarding psi: multiple groups per user
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.)


-- 
198577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=198577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: psi
Version: 0.8.7-4
Severity: wishlist


Hello,

I'd like it if I could add each user to multiple groups.  I'm not sure
if this is just that there needs to be UI added, or if this will mean
changing some user/group data structures and/or roster behavior.

Vineet


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux wingnut 2.4.20-1-686 #1 Sat Mar 22 13:16:21 EST 2003 i686
Locale: LANG=en_US.UTF-8, LC_CTYPE=ja_JP.UTF-8

Versions of packages psi depends on:
ii  libc6 2.3.1-16   GNU C Library: Shared libraries an
ii  libgcc1   1:3.3-2GCC support library
ii  libqt3c102-mt 3:3.1.1-8  Qt GUI Library (Threaded runtime v
ii  libstdc++51:3.3-2The GNU Standard C++ Library v3
ii  xlibs 4.2.1-6X Window System client libraries
ii  zlib1g1:1.1.4-12 compression library - runtime

-- no debconf information


--- End Message ---
--- Begin Message ---
Fixed in upstream long time ago.--- End Message ---

Bug#498357: marked as done (please patch psi dbus remote control)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 21:12:28 +0300
with message-id <580931611857...@mail.yandex.ru>
and subject line Outdated
has caused the Debian Bug report #498357,
regarding please patch psi dbus remote control
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.)


-- 
498357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: psi
Version: 0.12-2
Severity: wishlist
Tags: patch

The psi developers seem to be only using long running machines or
eventually windows or mac (where this problem doesn't occur). They seem
to not care about any method to use psi with suspend to disk (on linux)
or any other remote control with reasonings like "for other operating
systems there are interfaces for that, so we wait for linux to come up
with one, too". While this seems valid it is heavily breaking the
usability of psi. Many users (me being an example) would be almost happy
with any kind of remote control such as dbus. Fortunately psi uses dbus
now, so it is kind of easy to extend that interface with status
functions. So please patch the Debian psi version until upstream
understands the importance of this matter. The patch is to be applied to
src/dbus.cpp and does nothing except extending the dbus interface by six
functions. While it might be^W^Wis cleaner to use one function for this
using 6 functions avoids parsing a string to an enum.

Helmut

--- dbus.cpp.orig   2007-12-10 21:44:47.0 +0100
+++ dbus.cpp2008-09-09 13:43:29.0 +0200
@@ -27,6 +27,13 @@
 public Q_SLOTS:
 // void openURI(QString uri);
void raise();
+   void setstatusonline(const QString );
+   void setstatusaway(const QString );
+   void setstatusffc(const QString );
+   void setstatusxa(const QString );
+   void setstatusdnd(const QString );
+   void setstatusoffline(const QString );
+
 /*Q_SIGNALS:
void psi_pong();
 */
@@ -54,9 +61,41 @@
 {
psicon->raiseMainwin();
 }
+void PsiConAdapter::setstatusonline(const QString )
+{
+   Status s(Status::Online, message);
+   psicon->setGlobalStatus(s);
+}  
 
+void PsiConAdapter::setstatusaway(const QString )
+{
+   Status s(Status::Away, message);
+   psicon->setGlobalStatus(s);
+}  
 
+void PsiConAdapter::setstatusffc(const QString )
+{
+   Status s(Status::FFC, message);
+   psicon->setGlobalStatus(s);
+}  
 
+void PsiConAdapter::setstatusxa(const QString )
+{
+   Status s(Status::XA, message);
+   psicon->setGlobalStatus(s);
+}  
+
+void PsiConAdapter::setstatusdnd(const QString )
+{
+   Status s(Status::DND, message);
+   psicon->setGlobalStatus(s);
+}  
+
+void PsiConAdapter::setstatusoffline(const QString )
+{
+   Status s(Status::Offline, message);
+   psicon->setGlobalStatus(s);
+}  
 
 void addPsiConAdapter(PsiCon *psicon)
 {


--- End Message ---
--- Begin Message ---
.--- End Message ---

Bug#174681: marked as done (psi uses too much memory)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 21:06:54 +0300
with message-id <73691611857...@mail.yandex.ru>
and subject line Wontfix
has caused the Debian Bug report #174681,
regarding psi uses too much memory
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.)


-- 
174681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=174681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: psi
Version: 0.8.7-2
Severity: normal

Psi uses way too much memory. Here are the relavent lines from top's
output:

  PID USER PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
 1543 jcollins   9   0 11692  11M  7532 S 0.0  1.5   0:00 psi
 1554 jcollins   9   0 11692  11M  7532 S 0.0  1.5   0:00 psi
  
As you can see Psi is using ~11 Meg.  This is quite a bit.  Tkabber uses
significantly less memory:

 1909 jcollins  10   0  6932 6932  2380 S 0.0  0.8   0:02 wish
 /usr/share/tkabber/tkabber.tcl -na
 
A similar bug report has been filed on the Psi forums:

   http://psi.affinix.com/forums/viewtopic.php?t=129

-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux odin 2.4.19-k7 #1 Tue Nov 19 03:01:13 EST 2002 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages psi depends on:
ii  libc62.3.1-8 GNU C Library: Shared libraries an
ii  libqt3-mt2:3.0.5-4   Qt GUI Library (Threaded runtime v
ii  libstdc++2.10-glibc2.2   1:2.95.4-15 The GNU stdc++ library
ii  xlibs4.2.1-3 X Window System client libraries
ii  zlib1g   1:1.1.4-6   compression library - runtime


--- End Message ---
--- Begin Message ---
.--- End Message ---

Bug#978279: marked as done (afew: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 16:18:42 +
with message-id 
and subject line Bug#978279: fixed in afew 3.0.1-1
has caused the Debian Bug report #978279,
regarding afew: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess 
returned exit status 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.)


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

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:232: python3.9 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.9/build' (and everything under 
> it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
>dh_clean -O--buildsystem=pybuild
> dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in 
> use)
>  dpkg-source -b .
> dpkg-source: info: using options from afew-1.3.0/debian/source/options: 
> --extend-diff-ignore=^\.travis\.yml$
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building afew using existing ./afew_1.3.0.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
>  afew-1.3.0/afew/version.py
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/afew_1.3.0-1.diff.E1nTb8
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2020-12-26T18:43:43Z

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/afew_1.3.0-1_unstable.log

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

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

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

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: afew
Source-Version: 3.0.1-1
Done: Håvard Flaget Aasen 

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

Debian distribution maintenance software
pp.
Håvard Flaget Aasen  (supplier of updated afew 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, 28 Jan 2021 16:46:42 +0100
Source: afew
Architecture: source
Version: 3.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Håvard Flaget Aasen 
Closes: 915403 966690 978279
Changes:
 afew (3.0.1-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/watch: Use https protocol
   * Use debhelper-compat instead of debian/compat.
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Debian Janitor ]
   * debian/copyright: use spaces rather than tabs to start continuation
 lines.
   * Bump debhelper from old 9 to 12.
   * Set upstream 

Bug#966690: marked as done (afew: Package is outdated. )

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 16:18:42 +
with message-id 
and subject line Bug#966690: fixed in afew 3.0.1-1
has caused the Debian Bug report #966690,
regarding afew: Package is outdated. 
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.)


-- 
966690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: afew: Package is outdated.
Package: afew
X-Debbugs-Cc: deb...@fritzreichwald.de
Version: 1.3.0-1
Severity: normal
Tags: patch

Dear Maintainer,

I just recognized that afew is outdated in debian.
So i prepared
https://salsa.debian.org/python-team/modules/afew/-/merge_requests/2 to
fix this.

Please contact me if there is something I should fix before you can
merge it.

Thanks!

Best regards Fritz (fiete in IRC)
--- End Message ---
--- Begin Message ---
Source: afew
Source-Version: 3.0.1-1
Done: Håvard Flaget Aasen 

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

Debian distribution maintenance software
pp.
Håvard Flaget Aasen  (supplier of updated afew 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, 28 Jan 2021 16:46:42 +0100
Source: afew
Architecture: source
Version: 3.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Håvard Flaget Aasen 
Closes: 915403 966690 978279
Changes:
 afew (3.0.1-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/watch: Use https protocol
   * Use debhelper-compat instead of debian/compat.
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Debian Janitor ]
   * debian/copyright: use spaces rather than tabs to start continuation
 lines.
   * Bump debhelper from old 9 to 12.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Add missing build dependency on python3-dnspython (>= 1.16.0).
 .
   [ Håvard Flaget Aasen ]
   * Remove regenerated file by scm. Closes: #978279
   * New upstream version Closes: #966690
 - Version also support quotes properly Closes: #915403
   * d/control:
 - Added build-dependencies to continue test the package
 - Add Rules-Requires-root
 - Bump debhelper to 13
 - Remove old version restrictions
 - Update Standards-Version to 4.5.1
 - Add myself in uploaders field
   * d/watch: Bump version to 4
   * d/rules: Include upstream changelog
   * d/source/options: Exclude *.egg-info files
   * d/copyright: Updated with more Files paragraphs
Checksums-Sha1:
 34e1bb6be8a0882de011033c379a4eaf2102d120 1530 afew_3.0.1-1.dsc
 855590e36ab567478ee71adbe9d3284430a11318 38150 afew_3.0.1.orig.tar.gz
 d82a6be0ad5c8764373655a63372f91ee60cca71 3168 afew_3.0.1-1.debian.tar.xz
 9efeed947d77e148f36779b8d289dd50f7478fb3 7440 afew_3.0.1-1_amd64.buildinfo
Checksums-Sha256:
 7a51cbc1d1ff3abb6ba80d2523bedae0516ae3596689311f775628c8e65559eb 1530 
afew_3.0.1-1.dsc
 2aa23c0ee41acba06ed594f05a8f73a2788d06265468da96e21c080b0d5515ad 38150 
afew_3.0.1.orig.tar.gz
 756206de80f0a5cff2ff468f619395d0afaa96dad32c52e770d9c1da1a7d66a4 3168 
afew_3.0.1-1.debian.tar.xz
 e219edb5544760d0d876038c195346d0fa5530dfc48c6dbc698c41853490fb5d 7440 
afew_3.0.1-1_amd64.buildinfo
Files:
 498011130ee97871e62623aaf0420407 1530 python optional afew_3.0.1-1.dsc
 12dc2f4fdc882d1dd123a501d0f58609 38150 python optional afew_3.0.1.orig.tar.gz
 d862df472fc1099dfa04e671a8952eda 3168 python optional 
afew_3.0.1-1.debian.tar.xz
 02ae9e0db98188c1106be344c4449cf8 7440 python optional 
afew_3.0.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iI0EARYKADUWIQRlk5EXUZxDorKy9cv5N3WY8EyDCgUCYBLeuBccaGFhdmFyZF9h
YXNlbkB5YWhvby5ubwAKCRD5N3WY8EyDCv0cAQC2lx42+m2vggtyJMnt7HREOiOW
pNJzRwLezli26cqJ4QEA3peVASCoobNYwAlaQl/wKE2MEZ+LezX7XS/zrAgvZg8=
=X4nY
-END PGP SIGNATURE End Message ---

Bug#968002: marked as done (Missing ssl certificates)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 16:17:07 +
with message-id 
and subject line Bug#968002: fixed in ca-certificates 20200601~deb10u2
has caused the Debian Bug report #968002,
regarding Missing ssl certificates
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.)


-- 
968002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ca-certificates
Version: 20200601~deb10u1

Some certificates seem to be missing in 20200601~deb10u1. The following
command works in version 20190110 but stopped working in 20200601~deb10u1 .

curl https://static.gc.apple.com/public-key/3rd-party-auth-prod-19824d.cer

This gives the output:

curl: (60) SSL certificate problem: unable to get issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
--- End Message ---
--- Begin Message ---
Source: ca-certificates
Source-Version: 20200601~deb10u2
Done: Julien Cristau 

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated ca-certificates 
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, 28 Jan 2021 13:01:43 +0100
Source: ca-certificates
Architecture: source
Version: 20200601~deb10u2
Distribution: buster
Urgency: medium
Maintainer: Julien Cristau 
Changed-By: Julien Cristau 
Closes: 962596 968002
Changes:
 ca-certificates (20200601~deb10u2) buster; urgency=medium
 .
   [ Julien Cristau ]
   * New maintainer (see #976406)
 .
   [ Michael Shuler ]
   * mozilla/blacklist:
 Revert Symantec CA blacklist (#911289). Closes: #962596, #968002.
 The following root certificates were added back (+):
 + "GeoTrust Global CA"
 + "GeoTrust Primary Certification Authority"
 + "GeoTrust Primary Certification Authority - G2"
 + "GeoTrust Primary Certification Authority - G3"
 + "GeoTrust Universal CA"
 + "thawte Primary Root CA"
 + "thawte Primary Root CA - G2"
 + "thawte Primary Root CA - G3"
 + "VeriSign Class 3 Public Primary Certification Authority - G4"
 + "VeriSign Class 3 Public Primary Certification Authority - G5"
 + "VeriSign Universal Root Certification Authority"
 .
   Note: due to bug #743339, CA certificates added back in this version
   won't automatically be trusted again on upgrade.  Affected users may
   need to reconfigure the package to restore the desired state.
Checksums-Sha1:
 e9b49bb650b83b4ec6e51bbebdbd21eeeac1c678 1907 
ca-certificates_20200601~deb10u2.dsc
 6835c04ff1238e63ca05f3966f7c60fa215efe36 245804 
ca-certificates_20200601~deb10u2.tar.xz
Checksums-Sha256:
 b89cbd8c235e131ee10cb85a9bd4b3e429874c1e0577c5ed35121f8590d4d029 1907 
ca-certificates_20200601~deb10u2.dsc
 13ffd04d36230309ff383ad4ccbefb1852b1483f0ac3da75b4979906933ba5e8 245804 
ca-certificates_20200601~deb10u2.tar.xz
Files:
 aa78b8e34193eb326ba9e80b75b9611a 1907 misc optional 
ca-certificates_20200601~deb10u2.dsc
 3429d27944a83aeed05219eecbb59e51 245804 misc optional 
ca-certificates_20200601~deb10u2.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAmASxjMUHGpjcmlzdGF1
QGRlYmlhbi5vcmcACgkQnbAjVVb4z60/8w//fhhts0MwF8mxtoUFrJxtsm/3904m
MbXlfiYdMaIQCavlr/W2KqunGpg0KDyk+fLVAfRChpsDk7a2LVW2CS8VlxkEOuKy
mms2r1JDl49TiXf2Kyj1oNbvEINchT8eld2bYNQP4BX2F8Ew0QJVNXLzgyz9RYBJ
wO0aW8yTe6+agWHmjCDkw+wdO8B600/Q1YpUNjIvPImvFaAzd3sjWv9aczf6FFty
HBB2Of+teMP8vPi38/TsvgP3zvtVdgK77Vzzdqfh+xox025LFKwL40326xhBRy/+
FNRTOKRYX6kxrAFDwxjujDXpsSIcI984U7QKbJlHhH6NbY0nEkmDn7avzFyoSRqK
mTbxJ6P6NWv+icWGcqZZ5ZMP5bBgGA/iJ1fQ1PZxqCed7ae/PXzZIhHSjRwPTWc/
FIRiPpXBeJwsHlEQHMN0XkowqybS2ekYKpyT+LlYwPhTpyogdFASt3Q58MUebE8D
6TVVUNpTEJ7sSO72IeN1j9gPpaqZxEgYCNPWCU0Ec5KiFZj89H4BHU1d9oGAPb0i
7ya0tVT+ayzhMhFYa2bqMUdp3YJ3X8SPretTykKjF7OnMi5x7Bbn0IbSUJeq+E/8

Bug#962596: marked as done (ca-certificates: Removal of GeoTrust Global CA requires investigation)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 16:17:07 +
with message-id 
and subject line Bug#962596: fixed in ca-certificates 20200601~deb10u2
has caused the Debian Bug report #962596,
regarding ca-certificates: Removal of GeoTrust Global CA requires investigation
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.)


-- 
962596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ca-certificates
Version: 20200601
Severity: normal

Dear Maintainer,

Since the update of ca-certificates to version 20200601 I can no longer access
webkit.org websites.

$ gnutls-cli webkit.org
Processed 114 CA certificate(s).
Resolving 'webkit.org:443'...
Connecting to '54.190.50.171:443'...
- Certificate type: X.509
- Got a certificate list of 3 certificates.
- Certificate[0] info:
 - subject `C=US,ST=California,O=Apple
Inc.,OU=management:idms.group.764034,CN=www.webkit.org', issuer `C=US,O=Apple
Inc.,OU=Certification Authority,CN=Apple IST CA 2 - G1', serial
0x56bad882747e779b546f5fe1f1728a4b, RSA key 2048 bits, signed using RSA-SHA256,
activated `2019-03-14 16:13:54 UTC', expires `2021-04-12 16:13:54 UTC', pin-
sha256="wn1o7E4lMWKKBJYbeB8g/ZdNmeyrdOBvFA9yxI9H+Kk="
Public Key ID:
sha1:1020bd7159d9a3bb418ff02ee22f968359843074
sha256:c27d68ec4e2531628a04961b781f20fd974d99ecab74e06f140f72c48f47f8a9
Public Key PIN:
pin-sha256:wn1o7E4lMWKKBJYbeB8g/ZdNmeyrdOBvFA9yxI9H+Kk=

- Certificate[1] info:
 - subject `C=US,O=Apple Inc.,OU=Certification Authority,CN=Apple IST CA 2 -
G1', issuer `CN=GeoTrust Global CA,O=GeoTrust Inc.,C=US', serial 0x023a74, RSA
key 2048 bits, signed using RSA-SHA256, activated `2014-06-16 15:42:02 UTC',
expires `2022-05-20 15:42:02 UTC', pin-
sha256="tc+C1H75gj+ap48SMYbFLoh56oSw+CLJHYPgQnm3j9U="
- Certificate[2] info:
 - subject `CN=GeoTrust Global CA,O=GeoTrust Inc.,C=US', issuer `CN=GeoTrust
Global CA,O=GeoTrust Inc.,C=US', serial 0x023456, RSA key 2048 bits, signed
using RSA-SHA1 (broken!), activated `2002-05-21 04:00:00 UTC', expires
`2022-05-21 04:00:00 UTC', pin-
sha256="h6801m+z8v3zbgkRHpq6L29Esgfzhj89C1SyUCOQmqU="
- Status: The certificate is NOT trusted. The certificate issuer is unknown.
*** PKI verification of server certificate failed...
*** Fatal error: Error in the certificate.



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.6.0-2-amd64 (SMP w/24 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ca-certificates depends on:
ii  debconf [debconf-2.0]  1.5.74
ii  openssl1.1.1g-1

ca-certificates recommends no packages.

ca-certificates suggests no packages.

-- debconf information:
* ca-certificates/enable_crts: extra/mitmproxy-ca-cert.crt, 
mozilla/ACCVRAIZ1.crt, mozilla/AC_RAIZ_FNMT-RCM.crt, 
mozilla/Actalis_Authentication_Root_CA.crt, mozilla/AffirmTrust_Commercial.crt, 
mozilla/AffirmTrust_Networking.crt, mozilla/AffirmTrust_Premium.crt, 
mozilla/AffirmTrust_Premium_ECC.crt, mozilla/Amazon_Root_CA_1.crt, 
mozilla/Amazon_Root_CA_2.crt, mozilla/Amazon_Root_CA_3.crt, 
mozilla/Amazon_Root_CA_4.crt, mozilla/Atos_TrustedRoot_2011.crt, 
mozilla/Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.crt, 
mozilla/Baltimore_CyberTrust_Root.crt, mozilla/Buypass_Class_2_Root_CA.crt, 
mozilla/Buypass_Class_3_Root_CA.crt, mozilla/CA_Disig_Root_R2.crt, 
mozilla/Certigna.crt, mozilla/certSIGN_ROOT_CA.crt, 
mozilla/Certum_Trusted_Network_CA_2.crt, mozilla/Certum_Trusted_Network_CA.crt, 
mozilla/CFCA_EV_ROOT.crt, mozilla/Chambers_of_Commerce_Root_-_2008.crt, 
mozilla/Comodo_AAA_Services_root.crt, 
mozilla/COMODO_Certification_Authority.crt, 
mozilla/COMODO_ECC_Certification_Authority.crt, 
mozilla/COMODO_RSA_Certification_Authority.crt, 
mozilla/Cybertrust_Global_Root.crt, mozilla/DigiCert_Assured_ID_Root_CA.crt, 
mozilla/DigiCert_Assured_ID_Root_G2.crt, 
mozilla/DigiCert_Assured_ID_Root_G3.crt, mozilla/DigiCert_Global_Root_CA.crt, 
mozilla/DigiCert_Global_Root_G2.crt, mozilla/DigiCert_Global_Root_G3.crt, 
mozilla/DigiCert_High_Assurance_EV_Root_CA.crt, 
mozilla/DigiCert_Trusted_Root_G4.crt, mozilla/DST_Root_CA_X3.crt, 
mozilla/D-TRUST_Root_Class_3_CA_2_2009.crt, 
mozilla/D-TRUST_Root_Class_3_CA_2_EV_2009.crt, 

Bug#915403: marked as done (afew: afew can't handle messages with double quotes in message ids)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 16:18:42 +
with message-id 
and subject line Bug#915403: fixed in afew 3.0.1-1
has caused the Debian Bug report #915403,
regarding afew: afew can't handle messages with double quotes in message ids
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.)


-- 
915403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: afew
Version: 1.3.0-1
Severity: normal
Tags: patch

Dear Maintainer,

If a message has double quotes in its message id (it's weird, I know),

Message-Id: <"foo"@bar>

afew can't tag it properly and the message remains tagged as new. This
has been fixed upstream[1]. Please backport the patch.

[1] 
https://github.com/afewmail/afew/commit/950bda7cd517c767d6c8cbc7d00ff2df6d7b6d94

-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: armel, arm64

Kernel: Linux 4.9.0-6-amd64 (SMP w/8 CPU cores)
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)

Versions of packages afew depends on:
ii  python3  3.5.3-1
ii  python3-chardet  2.3.0-2
ii  python3-dkim 0.8.1-1~bpo90+1
ii  python3-notmuch  0.28-2~bpo9+1

afew recommends no packages.

afew suggests no packages.

-- no debconf information

-- 
Łukasz Stelmach
Samsung R Institute Poland
Samsung Electronics


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: afew
Source-Version: 3.0.1-1
Done: Håvard Flaget Aasen 

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

Debian distribution maintenance software
pp.
Håvard Flaget Aasen  (supplier of updated afew 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, 28 Jan 2021 16:46:42 +0100
Source: afew
Architecture: source
Version: 3.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Håvard Flaget Aasen 
Closes: 915403 966690 978279
Changes:
 afew (3.0.1-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/watch: Use https protocol
   * Use debhelper-compat instead of debian/compat.
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Debian Janitor ]
   * debian/copyright: use spaces rather than tabs to start continuation
 lines.
   * Bump debhelper from old 9 to 12.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Add missing build dependency on python3-dnspython (>= 1.16.0).
 .
   [ Håvard Flaget Aasen ]
   * Remove regenerated file by scm. Closes: #978279
   * New upstream version Closes: #966690
 - Version also support quotes properly Closes: #915403
   * d/control:
 - Added build-dependencies to continue test the package
 - Add Rules-Requires-root
 - Bump debhelper to 13
 - Remove old version restrictions
 - Update Standards-Version to 4.5.1
 - Add myself in uploaders field
   * d/watch: Bump version to 4
   * d/rules: Include upstream changelog
   * d/source/options: Exclude *.egg-info files
   * d/copyright: Updated with more Files paragraphs
Checksums-Sha1:
 34e1bb6be8a0882de011033c379a4eaf2102d120 1530 afew_3.0.1-1.dsc
 855590e36ab567478ee71adbe9d3284430a11318 38150 afew_3.0.1.orig.tar.gz
 d82a6be0ad5c8764373655a63372f91ee60cca71 3168 afew_3.0.1-1.debian.tar.xz
 9efeed947d77e148f36779b8d289dd50f7478fb3 7440 afew_3.0.1-1_amd64.buildinfo
Checksums-Sha256:
 7a51cbc1d1ff3abb6ba80d2523bedae0516ae3596689311f775628c8e65559eb 1530 
afew_3.0.1-1.dsc
 2aa23c0ee41acba06ed594f05a8f73a2788d06265468da96e21c080b0d5515ad 38150 
afew_3.0.1.orig.tar.gz
 

Bug#981167: marked as done (RM: edtsurf [i386] -- ROM; Not built on i386 but still in unstable)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 16:03:40 +
with message-id 
and subject line Bug#980441: fixed in edtsurf 0.2009-10
has caused the Debian Bug report #980441,
regarding RM: edtsurf [i386] -- ROM; Not built on i386 but still in unstable
to be marked as done.

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

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


-- 
980441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: 980...@bugs.debian.org

Hi ftpmasters,

as reported in bug #980415 edtsurf is not build any more but the old
package in unstable is blocking testing migration.  So please remove
edtsurf from unstable for i386 architecture.

Thanks a lot for your work as ftpmaster
   Andreas.
--- End Message ---
--- Begin Message ---
Source: edtsurf
Source-Version: 0.2009-10
Done: Michael R. Crusoe 

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated edtsurf 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, 28 Jan 2021 16:50:25 +0100
Source: edtsurf
Architecture: source
Version: 0.2009-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 980441
Changes:
 edtsurf (0.2009-10) unstable; urgency=medium
 .
   * Team upload.
   * debian/rules: for i386 compile with -ffloat-store. Closes: #980441
   * debian/test/run-unit-test: run all tests on i386
   * Standards-Version: 4.5.1 (routine-update)
Checksums-Sha1:
 d7fd22a0011372a4076de7eaa9c49bad6f0ffe0b 2026 edtsurf_0.2009-10.dsc
 100acdf1684c739328ce1e8d5b9f08c7f2b4b20e 99696 edtsurf_0.2009-10.debian.tar.xz
 67e6a6372fdbf32fa2bafda53c2e353164a0a8dc 5902 
edtsurf_0.2009-10_source.buildinfo
Checksums-Sha256:
 db9066be394b82a780489ff8523e1009875dff42df4d2bb648462c4d4bd70203 2026 
edtsurf_0.2009-10.dsc
 6dca4d8a84aa7dcac0d5c012f3554625e3623a397bca41b65119cbaa33d9f53c 99696 
edtsurf_0.2009-10.debian.tar.xz
 3ada4db92aea9c16f7892cb5b0cf04e1bff2a6968420f9168fd057e31b29c31e 5902 
edtsurf_0.2009-10_source.buildinfo
Files:
 89ef4e7e9f9d4eb6257c7734f161d948 2026 science optional edtsurf_0.2009-10.dsc
 1daf6b5792c18b2a8e895bddc5176969 99696 science optional 
edtsurf_0.2009-10.debian.tar.xz
 63895b96062bbf748b7f8b309187f40c 5902 science optional 
edtsurf_0.2009-10_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmAS3bIACgkQPCZ2P2xn
5uLkrw/+P53LYcIp2jFBKyWmO+nOo/cV1luDQmEjn/olXMyY3ibMsO7ICkKpcQ4r
HoT7N3Q8+dne2K3dwrjDRlP2nGDhEzL/v98oZ0r4RH5XDIgMM/UNTLCGmBb0RPFQ
mBO0lavx8KFdN3bpX0V5I+1uvIYSaC5tG1ME3sfLxykRl8PoLceLpSLYn0PbiAsD
ZNcFNLmW4xW2jaFm1mnXyDMsNtwqWV0n20LHOcLYJTe8XOHupqJprh8lrJ93lH23
sFAVm9D7hJbCnlhKVibPgMkP5rVMVSqpVFBq5hbXL9NiNGo2d/C6XKS5c/ncJoRb
GEmIPn5iPWQvGI+JxOzGmew6aY3S8QfrjjF3964ff27bIO4HoXfJ4E5uJemSeFK9
Kpo3lETsjNytK08iCUL7fpfa+ZQPXDaXHZrG8/z/5tx+EgATQ0kbAMdtOIZKYKX8
l+bV920e/+Yft/ZSqf5aopD9Q3l6YYDrcYpTwol7vMSauS7Ql2xNvciiMvvAZ9WN
7zuBhD4vX3ZT1F4sUWMUTfIX/rCMBFF0ZY1iogcXXgvf1uoftfFuLFNz+tyW7X4w
awM1YF7mw8plJPoZlHe9iB1+9UtK88kNoQ7wA8x/Zx5mV6ZxzS97CNbeFd6NqNjo
7j8tc9HJ1kncUvGduUvOMfM87bB2e1SCfMN8Dy3g828BeScyGAM=
=sQ+c
-END PGP SIGNATURE End Message ---

Bug#980441: marked as done (RM: edtsurf [i386] -- RoQA; i386 excluded due to test failures)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 16:03:40 +
with message-id 
and subject line Bug#980441: fixed in edtsurf 0.2009-10
has caused the Debian Bug report #980441,
regarding RM: edtsurf [i386] -- RoQA; i386 excluded due to test failures
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.)


-- 
980441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: edts...@packages.debian.org

Dear FTP masters,

Please remove edtsurf for the i386 architecture.
This is holding back testing migration for this package (#980415).

The latest changelog entry explains:

  * Exclude i386 from supported architectures since it fails even the
simplest test
Closes: #974555



Thanks,
Juhani Numminen
--- End Message ---
--- Begin Message ---
Source: edtsurf
Source-Version: 0.2009-10
Done: Michael R. Crusoe 

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated edtsurf 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, 28 Jan 2021 16:50:25 +0100
Source: edtsurf
Architecture: source
Version: 0.2009-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 980441
Changes:
 edtsurf (0.2009-10) unstable; urgency=medium
 .
   * Team upload.
   * debian/rules: for i386 compile with -ffloat-store. Closes: #980441
   * debian/test/run-unit-test: run all tests on i386
   * Standards-Version: 4.5.1 (routine-update)
Checksums-Sha1:
 d7fd22a0011372a4076de7eaa9c49bad6f0ffe0b 2026 edtsurf_0.2009-10.dsc
 100acdf1684c739328ce1e8d5b9f08c7f2b4b20e 99696 edtsurf_0.2009-10.debian.tar.xz
 67e6a6372fdbf32fa2bafda53c2e353164a0a8dc 5902 
edtsurf_0.2009-10_source.buildinfo
Checksums-Sha256:
 db9066be394b82a780489ff8523e1009875dff42df4d2bb648462c4d4bd70203 2026 
edtsurf_0.2009-10.dsc
 6dca4d8a84aa7dcac0d5c012f3554625e3623a397bca41b65119cbaa33d9f53c 99696 
edtsurf_0.2009-10.debian.tar.xz
 3ada4db92aea9c16f7892cb5b0cf04e1bff2a6968420f9168fd057e31b29c31e 5902 
edtsurf_0.2009-10_source.buildinfo
Files:
 89ef4e7e9f9d4eb6257c7734f161d948 2026 science optional edtsurf_0.2009-10.dsc
 1daf6b5792c18b2a8e895bddc5176969 99696 science optional 
edtsurf_0.2009-10.debian.tar.xz
 63895b96062bbf748b7f8b309187f40c 5902 science optional 
edtsurf_0.2009-10_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmAS3bIACgkQPCZ2P2xn
5uLkrw/+P53LYcIp2jFBKyWmO+nOo/cV1luDQmEjn/olXMyY3ibMsO7ICkKpcQ4r
HoT7N3Q8+dne2K3dwrjDRlP2nGDhEzL/v98oZ0r4RH5XDIgMM/UNTLCGmBb0RPFQ
mBO0lavx8KFdN3bpX0V5I+1uvIYSaC5tG1ME3sfLxykRl8PoLceLpSLYn0PbiAsD
ZNcFNLmW4xW2jaFm1mnXyDMsNtwqWV0n20LHOcLYJTe8XOHupqJprh8lrJ93lH23
sFAVm9D7hJbCnlhKVibPgMkP5rVMVSqpVFBq5hbXL9NiNGo2d/C6XKS5c/ncJoRb
GEmIPn5iPWQvGI+JxOzGmew6aY3S8QfrjjF3964ff27bIO4HoXfJ4E5uJemSeFK9
Kpo3lETsjNytK08iCUL7fpfa+ZQPXDaXHZrG8/z/5tx+EgATQ0kbAMdtOIZKYKX8
l+bV920e/+Yft/ZSqf5aopD9Q3l6YYDrcYpTwol7vMSauS7Ql2xNvciiMvvAZ9WN
7zuBhD4vX3ZT1F4sUWMUTfIX/rCMBFF0ZY1iogcXXgvf1uoftfFuLFNz+tyW7X4w
awM1YF7mw8plJPoZlHe9iB1+9UtK88kNoQ7wA8x/Zx5mV6ZxzS97CNbeFd6NqNjo
7j8tc9HJ1kncUvGduUvOMfM87bB2e1SCfMN8Dy3g828BeScyGAM=
=sQ+c
-END PGP SIGNATURE End Message ---

Bug#871854: marked as done (geronimo-osgi-support: Please update the Uploaders list)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 15:18:57 +
with message-id 
and subject line Bug#871854: fixed in geronimo-osgi-support 1.1-2
has caused the Debian Bug report #871854,
regarding geronimo-osgi-support: Please update the Uploaders list
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.)


-- 
871854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:geronimo-osgi-support
Severity: minor
Tags: pending
User: nomad...@debian.org
Usertags: cleanup

As title says.

I haven't been involved in the maintenance of this package since several
years ago. I originally packaged this as B-D of libspring-java package.

I intend to keep an eye on this package for the current oldstable and
stable release lifecycles. However, it's very unlikely I'll be involved
in its current development cycle (buster).

I removed myself from uploaders list and prepared a tentative QA upload
but I didn't upload it to the archive since the resulting package would
be in violation of Debian Policy (§3.3 and §5.6.3). I'd appreciate if
somebody else can step in as maintainer.

Cheers,
Miguel.


-- System Information:
Debian Release: 8.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: geronimo-osgi-support
Source-Version: 1.1-2
Done: Emmanuel Bourg 

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated geronimo-osgi-support 
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, 28 Jan 2021 15:59:28 +0100
Source: geronimo-osgi-support
Architecture: source
Version: 1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Closes: 871854
Changes:
 geronimo-osgi-support (1.1-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Miguel Landaeta ]
   * Remove myself from uploaders list. (Closes: #871854)
   * Update Vcs-Git field to use HTTPS in URL.
   * Bump Standards-Version to 3.9.8. No changes were required.
   * Update copyright info.
   * Wrap and sort dependency lists.
 .
   [ Emmanuel Bourg ]
   * Build with Maven instead of jh_build
   * Removed the -java-doc package
   * Standards-Version updated to 4.5.1
   * Switch to debhelper level 13
   * Use salsa.debian.org Vcs-* URLs
   * Removed debian/orig-tar.sh
   * Fixed the description of the package
   * Use secure URLs
Checksums-Sha1:
 10efb78cea1abc821acc409a42b7c4fe06c29ccd 2131 geronimo-osgi-support_1.1-2.dsc
 4f0ba0821b30c5aee16ac78cdfdedcc122585038 3296 
geronimo-osgi-support_1.1-2.debian.tar.xz
 44340ceec52ab8ff049dae1760673f911935956e 15229 
geronimo-osgi-support_1.1-2_source.buildinfo
Checksums-Sha256:
 86e4bac7cbd3f041adf7ed24e0f0c89a077850e8cee73e2cc09dac354a893037 2131 
geronimo-osgi-support_1.1-2.dsc
 1a7c78ddd2037ab44f9290dadb581f96ca065fd2ca6d440b793c971f2a06c43d 3296 
geronimo-osgi-support_1.1-2.debian.tar.xz
 6b41f3a3f3a0727acf614e57159d52ffd5bd11d568430fa51da98d25dbc3603e 15229 
geronimo-osgi-support_1.1-2_source.buildinfo
Files:
 9b002f6c9154938029a4902f9859c8ca 2131 java optional 
geronimo-osgi-support_1.1-2.dsc
 a6ac203309222e1cad99cdcaea8e0a4b 3296 java optional 
geronimo-osgi-support_1.1-2.debian.tar.xz
 ce15639034cadee853f3f1d26ea4a995 15229 java optional 
geronimo-osgi-support_1.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAmAS0ZQSHGVib3VyZ0Bh

Bug#980775: marked as done (yarnpkg is not compatible with node-uuid 7.0.0+)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 15:04:32 +
with message-id 
and subject line Bug#980775: fixed in node-yarnpkg 1.22.10+~cs22.25.14-2
has caused the Debian Bug report #980775,
regarding yarnpkg is not compatible with node-uuid 7.0.0+
to be marked as done.

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

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


-- 
980775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: yarnpkg
Version: 1.22.10+~cs22.25.14-1

>From https://www.npmjs.com/package/uuid/v/7.0.1#default-export-removed:

> Default Export Removed
>
> uuid@3 was exporting the Version 4 UUID method as a default export:
> 
> const uuid = require('uuid'); // <== REMOVED!
> 
> This usage pattern was already discouraged in uuid@3 and has been removed in 
> uuid@7.

But yarnpkg uses that pattern in src/resolvers/exotics/file-resolver.js,
src/cli/commands/install.js, and src/cli/commands/import.js.

This results in failures at runtime, for example

  $ mkdir -p /tmp/test/foo
  $ cd /tmp/test
  $ yes '' | yarn init
  yarn init v1.22.10
  question name (test): 
  question version (1.0.0): 
  question description: 
  question entry point (index.js): 
  question repository url: 
  question author: 
  question license (MIT): 
  question private: 
  success Saved package.json
  Done in 0.14s.
  $ yarn add file:foo
  yarn add v1.22.10
  info No lockfile found.
  [1/4] Resolving packages...
  error An unexpected error occurred: "Cannot read property 'v4' of undefined".
  info If you think this is a bug, please open a bug report with the 
information provided in "/tmp/test/yarn-error.log".
  info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this 
command.
--- End Message ---
--- Begin Message ---
Source: node-yarnpkg
Source-Version: 1.22.10+~cs22.25.14-2
Done: Paolo Greppi 

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

Debian distribution maintenance software
pp.
Paolo Greppi  (supplier of updated node-yarnpkg 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, 28 Jan 2021 11:42:25 +0100
Source: node-yarnpkg
Architecture: source
Version: 1.22.10+~cs22.25.14-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Paolo Greppi 
Closes: 980775
Changes:
 node-yarnpkg (1.22.10+~cs22.25.14-2) unstable; urgency=medium
 .
   * Fix date and version in manpage
   * Fix uuid import so that it works with recent versions (Closes: #980775)
   * Depend on node-babel7-runtime rather than node-babel7
Checksums-Sha1:
 9a256646c4a89cddfd4afad2019683a7d177ffe5 8177 
node-yarnpkg_1.22.10+~cs22.25.14-2.dsc
 f759e9afdb4aa2827cedd89f261035b3c14de848 13896 
node-yarnpkg_1.22.10+~cs22.25.14-2.debian.tar.xz
 b0c781728331dc9c895ef653ec36f875103a6c00 22687 
node-yarnpkg_1.22.10+~cs22.25.14-2_source.buildinfo
Checksums-Sha256:
 0ea725276df731c2e877710f5b70c0fe27930c9a00d466ca89886070ca2ee086 8177 
node-yarnpkg_1.22.10+~cs22.25.14-2.dsc
 5d45b39dcab32d2b3ea21f47efe3ff15276a4f81ed9ec49e145573fa32cf5a4e 13896 
node-yarnpkg_1.22.10+~cs22.25.14-2.debian.tar.xz
 d5e2e6a9333da4b2ae6aa3dc743d6cdf8d01e157793c6a211af68885138c714d 22687 
node-yarnpkg_1.22.10+~cs22.25.14-2_source.buildinfo
Files:
 8d133543e862a8a6b8c1fde4da032060 8177 javascript optional 
node-yarnpkg_1.22.10+~cs22.25.14-2.dsc
 85aca1500cb7993b647c8116cdfdebc2 13896 javascript optional 
node-yarnpkg_1.22.10+~cs22.25.14-2.debian.tar.xz
 d245d5b11dbc1261dd91fa453b7ab325 22687 javascript optional 
node-yarnpkg_1.22.10+~cs22.25.14-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJLBAEBCgA1FiEEyTpTRBhTUv5T0mHqIjkMJVxGBPQFAmASxb4XHHBhb2xvLmdy
ZXBwaUBsaWJwZi5jb20ACgkQIjkMJVxGBPSjxRAAvmsDsgKvMJAM5SKR09P8YwPH
4hAv7g2bhivOCSbdC7ZfzJAKq9LyLT90k2OS9iMYKZfKMSgRGJf2nZqUy9uZtzlE
CrWElVWE6Essb/Slvl2WxT5CIcwlgmlhmL5mhQ6BRQepFdda73NnyEBwbJy4Vtpd
Kb65a+APtOgoIADTfgdw10DuZHuhnG9XK7NFs/RCDAI4t7ePXZHWmIv+lq5G2hFr
6aMCPsAVS+ngv/je8/9u7FIk7wZMS+AyWmRhcCf707+XSWgkI7QkqlqE6At2s9YY
KBa7JaanN6uuwxXzEIf1Ws5davpytGzNhiAqeFKZ5zE5T3n35xq6bX2T5GXyumYo

Bug#972420: marked as done (Adios FTBFS with python3.9 due to cython)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 14:22:24 +
with message-id 
and subject line Bug#972420: fixed in adios 1.13.1-27
has caused the Debian Bug report #972420,
regarding Adios FTBFS with python3.9 due to cython
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.)


-- 
972420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:adios
Version: 1.13.1-26
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

adios ignores errors in its packaging in the shell snippets

  for p in $(PY3VERS) ; do

and in this case ftbfs with python3.9. Please fix both of these issues.

The python3.9 issue is likely a cython file which is not re-generated during the
build.
--- End Message ---
--- Begin Message ---
Source: adios
Source-Version: 1.13.1-27
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated adios 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, 28 Jan 2021 13:27:55 +
Source: adios
Architecture: source
Version: 1.13.1-27
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 972420
Changes:
 adios (1.13.1-27) unstable; urgency=medium
 .
   * Fix build with cython3. Closes: #972420
   * Change default branch to debian/latest in d/control
   * Add 'set -e' to trap shell errors in debian/rules
   * Standards-Version: 4.5.1
Checksums-Sha1:
 03d81b075effc331f0e4519b8ca2b9cf4e6f9e32 3066 adios_1.13.1-27.dsc
 20e3d203111d82782773e1dfb8a5f4cb056e2dca 23808 adios_1.13.1-27.debian.tar.xz
Checksums-Sha256:
 7409a20b4d1d92c7492e582a4a6dc56da4d4997787860676364bf4914c6ab8bf 3066 
adios_1.13.1-27.dsc
 ace406a33c5aecabd106697ac2cdca1125c5f8908af543eadb65de24a332c882 23808 
adios_1.13.1-27.debian.tar.xz
Files:
 3721f77c8a799ed93a88214d9b7147ca 3066 science optional adios_1.13.1-27.dsc
 ebaa5cf23ac27819ed652bd0457f301d 23808 science optional 
adios_1.13.1-27.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmASvt4ACgkQy+a7Tl2a
06VsNQ//a8pGX9zJ7U0wXBuJ07esv6PsBTJ7tuh6uDBiZzQxvYLC7Q6dPBX+LeW3
PLfvz1lMGbB3+Xp4ojrk34meVmMxdq7CwfO3sPiyTMmX07aAPRqxBB1Cx+XnJI5E
QNCoI5W7PwdQ1dU57zoDgPuVKapV1HdGZlUVjNOiFstFrjtcD54BmNrEuhCtEJM0
oiV3JkJaPOprQUAnME0ietQx7j7dZYZeIm220Cee0wTdM0y8IfA6zhhpwHSkViFw
H5ASgMsh0jtZxrJf6C8wI+fMyetVHYxOhV16z64FOBshdxex53oLwAz614Cbjx+8
2VZheYG/2frAV0ZdJEB0OuR3PQrPPjwVcU3Lxc9uBMmPsREmAyKC/kHmelKDfe4Q
egWlBjnPUVIHpY5sv7kEbx9cE/5uwQP2oTC7LHNRRew5CgDV54V1oLGeLyzk0fb9
yvX5S/bNIln53SGm6+eUrBEGDCuOo+k5ImTs/LYfRFLmY74Tk0zNg+y8e5oH1zvZ
vmR5ZZfTML64XCNABOA5LQ/l44kuegSTWXhPk1vfoRUXB+RZ/Dw/ps/uHcf+9E5F
mcJErxK6lB6ZcE4yQs+XPdGIR+J0pSNHC+zm9I0ohRM06Sz4Y9orp08Mwg/m2wRQ
FiRCwvRf1WrUC+gkZcFdg2BfbyQ+F07y5LpO5P/Ay5mlQlog/zQ=
=z/6E
-END PGP SIGNATURE End Message ---

Bug#871853: marked as done (geronimo-jpa-2.0-spec: Please update the Uploaders list)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 14:22:35 +
with message-id 
and subject line Bug#871853: fixed in geronimo-jpa-2.0-spec 1.1-4
has caused the Debian Bug report #871853,
regarding geronimo-jpa-2.0-spec: Please update the Uploaders list
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.)


-- 
871853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:geronimo-jpa-2.0-spec
Severity: minor
Tags: pending
User: nomad...@debian.org
Usertags: cleanup

As title says.

I haven't been involved in the maintenance of this package since several
years ago. I originally packaged this as B-D of libspring-java package.

I intend to keep an eye on this package for the current oldstable and
stable release lifecycles. However, it's very unlikely I'll be involved
in its current development cycle (buster).

I removed myself from uploaders list and prepared a tentative QA upload
but I didn't upload it to the archive since the resulting package would
be in violation of Debian Policy (§3.3 and §5.6.3). I'd appreciate if
somebody else can step in as maintainer.

Cheers,
Miguel.


-- System Information:
Debian Release: 8.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: geronimo-jpa-2.0-spec
Source-Version: 1.1-4
Done: Emmanuel Bourg 

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated geronimo-jpa-2.0-spec 
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, 28 Jan 2021 14:43:41 +0100
Source: geronimo-jpa-2.0-spec
Architecture: source
Version: 1.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Closes: 871853
Changes:
 geronimo-jpa-2.0-spec (1.1-4) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Miguel Landaeta ]
   * Remove myself from uploaders list. (Closes: #871853)
   * Wrap and sort dependency lists.
   * Update copyright information.
 .
   [ Emmanuel Bourg ]
   * Removed the -java-doc package
   * Standards-Version updated to 4.5.1
   * Switch to debhelper level 13
   * Use salsa.debian.org Vcs-* URLs
   * Removed debian/orig-tar.sh
Checksums-Sha1:
 057010126ed0c9b855446e25c489b3e0d7146309 2124 geronimo-jpa-2.0-spec_1.1-4.dsc
 b0d24e89a7184691ccd667337dec15c056336731 3272 
geronimo-jpa-2.0-spec_1.1-4.debian.tar.xz
 a830b2290b19528754a1d53295727e3dcef437c9 15229 
geronimo-jpa-2.0-spec_1.1-4_source.buildinfo
Checksums-Sha256:
 e28bd98b871e925b30e3bbf290a3092f53476b4a7e7b97ba3712ce84402e2ec4 2124 
geronimo-jpa-2.0-spec_1.1-4.dsc
 5fc0c9b719209efe67976dcaf46914a158eef8fbda624a401d69f686d1c30c6a 3272 
geronimo-jpa-2.0-spec_1.1-4.debian.tar.xz
 d62e82240310496445a61d7cfd5d9ae0ceb7314542c886fe365219ddfeada375 15229 
geronimo-jpa-2.0-spec_1.1-4_source.buildinfo
Files:
 9b32adbf856865666f53edda2787e7ed 2124 java optional 
geronimo-jpa-2.0-spec_1.1-4.dsc
 6ae21afb63f8f82182ea434da5a0bb22 3272 java optional 
geronimo-jpa-2.0-spec_1.1-4.debian.tar.xz
 8b92f10388f386b2ecee14378f012147 15229 java optional 
geronimo-jpa-2.0-spec_1.1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAmASw54SHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCs8jgP+wYajruVsifd/NXsiDSIadLfcfmTnSPW
HzdJN8BYfq+O0s8jBzFkuwSDJLKkxQ2BKD/VSjii7peqLu//cyNJdXwIeJK0qERJ
XIzdN4rm32P4vIAfEH3gR8eulK3KSZpQWTi3GGJsImquqy34MnqvMZVVqMf1DHuj

Processed: closing 648669

[Debian Bug Tracking System]

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

> close 648669
Bug #648669 [libosgi-compendium-java] libgeronimo-jpa-2.0-spec-java: triangular 
dependency
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#980223: marked as done (RM: r-bioc-glmgampoi [i386] -- ROM; Unsupported)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 13:48:49 +
with message-id 
and subject line Bug#980223: fixed in r-bioc-glmgampoi 1.2.0+dfsg-6
has caused the Debian Bug report #980223,
regarding RM: r-bioc-glmgampoi [i386] -- ROM; Unsupported
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

r-bioc-glmgampoi doesn't seem to work on i386, so lets remove it for
now.


-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmAC5cYSHGNydXNvZUBk
ZWJpYW4ub3JnAAoJEDwmdj9sZ+biNmwQALm0nFJUwfYYLVi4IFpEp2BqLoEtgWaI
GaILdG0nnI69UTPKy1Yg+T21ycyj73j/xy3z+p1ZE/0Js3OkRhGUS2aLCj6/rhiV
UAFWxZY6LbakJ0WU5iPdLItY1p9heuuz8JC9gfJhoREZiJEEQuFtp6CfW3P9tlqL
/KMZPlfi2HoM4FEq28aM72USUU2VV4xvkcCyTQYUaumUE9Dv+okKsrcwo59qlWUg
iSDGqPKKYZ8wnftGqxqWMLSGJmaNSpeZrJs5fjRTg8xKEj3RCpzCe9kkRNz/IGDp
3L/xVVwrBAAWL7KTRuZV+EB6lrh6Nrmr7BNP4//7U5R3DUJ6/LvPHcggPEil0HpQ
dd/vOarZRus5ERGZQOC8kZAg0l9pacMxpBvNW4F47212b2R6V8kHNSlJkeLi2ohb
0LAMs1girInKcxkSiUqwhfZX0W//yphN9UqZVGA2chKqdioG6wqGCXJDzbSRE0kt
ceCOdCDypIM+WbFnedufKPccZiEkZFSiRiPqO7FZn0ppbc+fUKag7pCsJ7VG+4gT
2ghTBaeuqBaZhGHsom+i2n+5td1UDSR02hgtT8S7fsfuCjbpHbRgYI5Y30APwKTM
zdFKHlIGRsBQh360w66SfWiPqYEQtCfaxptEgNK1RwwR4IMhUsWhmskcswxCBX0Q
poQXBEbwepIa
=i19p
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: r-bioc-glmgampoi
Source-Version: 1.2.0+dfsg-6
Done: Michael R. Crusoe 

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated r-bioc-glmgampoi 
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, 28 Jan 2021 14:22:18 +0100
Source: r-bioc-glmgampoi
Architecture: source
Version: 1.2.0+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Michael R. Crusoe 
Closes: 980223
Changes:
 r-bioc-glmgampoi (1.2.0+dfsg-6) unstable; urgency=medium
 .
   * Add patch to fix tests on i386/i686. Closes: #980223
Checksums-Sha1:
 a0b51d92ea70d63b4192029941e413f46501e2ad 2383 r-bioc-glmgampoi_1.2.0+dfsg-6.dsc
 02f4227c31599387e0bcdf3cd6f565bcdf4906fd 3060 
r-bioc-glmgampoi_1.2.0+dfsg-6.debian.tar.xz
 41a63b016c495029de994751c5123818718f9fcf 10709 
r-bioc-glmgampoi_1.2.0+dfsg-6_source.buildinfo
Checksums-Sha256:
 b10af7f849e2bb898fa5d2614cc9310a73144ce78c9c7ca7f408bb1bf79b9417 2383 
r-bioc-glmgampoi_1.2.0+dfsg-6.dsc
 91369a504d5451fddf87c21f3b8cbd90a6ba88ae4c3f43d27cd7bee79979e74a 3060 
r-bioc-glmgampoi_1.2.0+dfsg-6.debian.tar.xz
 87eeb79228fbe12bc1fb96ed2a8e0b1ebd45a54c42d2bbe84d540fdd3fc5a570 10709 
r-bioc-glmgampoi_1.2.0+dfsg-6_source.buildinfo
Files:
 8bfc998ad3c43b29e2e091f25dbe2012 2383 gnu-r optional 
r-bioc-glmgampoi_1.2.0+dfsg-6.dsc
 a1dbc0e3d42fcb08b1aa346470490c2d 3060 gnu-r optional 
r-bioc-glmgampoi_1.2.0+dfsg-6.debian.tar.xz
 b0454a99173f23c47735c73e1eabca47 10709 gnu-r optional 
r-bioc-glmgampoi_1.2.0+dfsg-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmASu1wACgkQPCZ2P2xn
5uJ8Bw/9GJo4AlG3VADeG3ysrP0yLgfyGik3IwneHaiop1WgAutm6vdFIT3BgylU
HMCfBbM4yNOJSD+ya7NT/UvY9czPUr/CmJKCwLLqgAgHC0OtW/rUnNuAmCd2q+Ze
hbM8egvLqIg0j2BRSljU/+/IDDnZ4CYTg18V20s+VEmFNb4GN661BJfsGwcwlf3g
zP4NZHDAY6XZNmddaht07SD0H9304nZoB2otzYHexuJWQQjTVBPpSnKCAqslhhDJ
kmBK4cUnIbA1b3+wyudPWSM3y8EpbdpDxZhcFcEua8QBEekRcQ5GGAYuPpoKDJt8
1TXZSq4OPx8RKCUkO1ntd1kghpnsbszUV0jx6VFYTYcINDeK64VdsFgidTlkBUl0
Rxq0O7p4JVGU1d0s4rhxHv9Ee4UmRKC8OuieUVJfI3laMGpq2wu1AVjXs///HdUU
6a9sTOa62fAecPzJLiw69+b7xyMv9ZvZv8EDonvIgyWn20N3pyEJ8B9gEkUMSkJV
OHVc09Q2pbVIDiiJJREwoBNaRzrBJp1y02ocFBRPRyoFPqVS/hzWcs+EpIIBZEDX
fnvtIfP7TwepxM3kXHuc4ZUyua/POHt+k+2ohdAmjdRLw/a5hc5JzfSsLO+rHbj8
5HXa3o4t/yDQIGVcNOnKWoheNLGrx558zyNxy+uqd6zp+bAoarA=
=ZznB
-END PGP SIGNATURE End Message ---

Bug#981209: marked as done (intel-mediasdk: drop unused Build-Depends: libpciaccess-dev)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 13:33:27 +
with message-id 
and subject line Bug#981209: fixed in intel-mediasdk 21.1.0-1
has caused the Debian Bug report #981209,
regarding intel-mediasdk: drop unused Build-Depends: libpciaccess-dev
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.)


-- 
981209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: intel-mediasdk
Version: 20.3.0-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

intel-mediasdk participates in dependency loops relevant to architecture
bootstrap. Rather than look into such a difficult problem, I looked into
easily droppable dependencies. It turns out that libpciaccess-dev is
practically unused. It is required for building the sample test_monitor.
When libpciaccess-dev goes missing, this sample is not built. As it
happens, it also is not installed and not run during tests. As such,
libpciaccess-dev can be dropped without replacement. Please consider
applying the attached patch. Alternatively, consider annotating it with
.

Helmut
diff --minimal -Nru intel-mediasdk-20.3.0/debian/changelog 
intel-mediasdk-20.3.0/debian/changelog
--- intel-mediasdk-20.3.0/debian/changelog  2020-10-16 10:17:36.0 
+0200
+++ intel-mediasdk-20.3.0/debian/changelog  2021-01-27 17:35:17.0 
+0100
@@ -1,3 +1,10 @@
+intel-mediasdk (20.3.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop unused Build-Depends: libpciaccess-dev.
+
+ -- Helmut Grohne   Wed, 27 Jan 2021 17:35:17 +0100
+
 intel-mediasdk (20.3.0-1) unstable; urgency=medium
 
   * New upstream release.
diff --minimal -Nru intel-mediasdk-20.3.0/debian/control 
intel-mediasdk-20.3.0/debian/control
--- intel-mediasdk-20.3.0/debian/control2020-10-16 09:54:42.0 
+0200
+++ intel-mediasdk-20.3.0/debian/control2021-01-27 17:25:50.0 
+0100
@@ -7,7 +7,6 @@
  libdrm-dev,
  libgmock-dev,
  libgtest-dev,
- libpciaccess-dev,
  libva-dev,
  libx11-dev,
  libx11-xcb-dev,
--- End Message ---
--- Begin Message ---
Source: intel-mediasdk
Source-Version: 21.1.0-1
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated intel-mediasdk 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, 28 Jan 2021 15:23:06 +0200
Source: intel-mediasdk
Architecture: source
Version: 21.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Timo Aaltonen 
Changed-By: Timo Aaltonen 
Closes: 981209
Changes:
 intel-mediasdk (21.1.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Drop unused Build-Depends: libpciaccess-dev. (Closes: #981209)
Checksums-Sha1:
 9a95b08cd389fdccc87312d7aae888077cce5e31 2154 intel-mediasdk_21.1.0-1.dsc
 ceb77f79cd4695cab699bdd5bf8183cc259a2938 11786504 
intel-mediasdk_21.1.0.orig.tar.gz
 3fcb00f8a12c6b089b1555e8048b7e23edfd7764 5072 
intel-mediasdk_21.1.0-1.debian.tar.xz
 f358193442b2b233ab09fe19d80d9d767fc5a1ae 9042 
intel-mediasdk_21.1.0-1_source.buildinfo
Checksums-Sha256:
 063287167635e215b28dbd4a954da2510492a496a8f6545b5ba59c55c1100d4b 2154 
intel-mediasdk_21.1.0-1.dsc
 4e92a9eb8a6e020304736eb5f51c8a7849a6f6021ac06fcb7e6285118248c206 11786504 
intel-mediasdk_21.1.0.orig.tar.gz
 bc201d41e8dbf42e7e4c1d6e2f9a6b47d37a5242543d40b3a80a6cf94ec7bf99 5072 
intel-mediasdk_21.1.0-1.debian.tar.xz
 94719e8f78e22d8dc9fc0541698c36aec72b1e58eb46adecba9a6c3972e8aa87 9042 
intel-mediasdk_21.1.0-1_source.buildinfo
Files:
 4a2eb531784b7b8d978f4a994465fc8d 2154 libs optional intel-mediasdk_21.1.0-1.dsc
 adbee0bc8951b148a91f12bb2ebab0bf 11786504 libs optional 
intel-mediasdk_21.1.0.orig.tar.gz
 0d351631c40a5b9fa21326099ec817e6 5072 libs optional 
intel-mediasdk_21.1.0-1.debian.tar.xz
 5ce37d34ea4a4e5eff5f156eab2bb323 9042 libs optional 
intel-mediasdk_21.1.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmASusgACgkQy3AxZaiJ

Bug#538189: marked as done ([dovecot-antispam] incompatibility with dbox mail storage backend)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 14:31:26 +0100
with message-id <4f33554cb0e05e0901430bbe40f0bf1e812ad0dc.ca...@debian.org>
and subject line Re:  [dovecot-antispam] incompatibility with dbox mail storage 
 backend
has caused the Debian Bug report #538189,
regarding [dovecot-antispam] incompatibility with dbox mail storage backend
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.)


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

Package: dovecot-antispam
Version: 1.2+20090702-0.2
Severity: serious

--- Please enter the report below this line. ---
It has been verified by Timo Sirainen that dovecot-antispam is  
incompatible with dovecot's dbox storage backend at the moment. Server  
crashes when I try to move a message into spam folder. Please find the  
backtrace attached to this message.


--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.30-1-686

Debian Release: squeeze/sid
  500 unstablewww.debian-multimedia.org
  500 unstabledebian.org.ua
  500 unstabledebian.ejohansson.se
  500 unstabledeb.opera.com
  500 testing security.debian.org

--- Package information. ---
Depends(Version) | Installed
-+-===
libc6   (>= 2.3) | 2.9-21
dovecot-imapd| 1:1.2.1-hg9236


--
Eugene Paskevich |   *==)---   | Plug me into
eug...@raptor.kiev.ua|   ---(==*   |  The Matrix

dovecot.trace
Description: Binary data
--- End Message ---
--- Begin Message ---
On Sun, 03 Jun 2018 00:55:09 +0900 =?UTF-8?Q?Marc_Dequ=C3=A8nes_=28duck=29?= 
 wrote:
> Quack,
> 
> While browsing dovecot-antispam's bugs I stumbled upon this one and 
> thought I might give some feedback.
> 
> We are using dovecot-antispam 2.0+20170109-1 with dovecot 
> 1:2.2.27-3+deb9u2 with a spool2dir configuration. The configuration is 
> the following:
> plugin {
>    antispam_backend = spool2dir
>    antispam_signature = X-DSPAM-Signature
>    antispam_signature_missing = move
> 
>    antispam_spam = Junk
>    antispam_trash_pattern_ignorecase = trash;Deleted *
> 
>    antispam_spool2dir_spam    = 
> /var/spool/dovecot-antispam/%%020lu-%u-%%05lu.spam
>    antispam_spool2dir_notspam = 
> /var/spool/dovecot-antispam/%%020lu-%u-%%05lu.ham
> }
> 
> We just completed a migration to mdbox and see no such problems. So I 
> guess this br could be closed.

Thanks for the feedback. I guess it is safe to close this >10y open bug then;
in case, it can always be reopened.

--
tobi--- End Message ---

Processed: closing 957365

[Debian Bug Tracking System]

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

> close 957365
Bug #957365 [src:intel-mediasdk] intel-mediasdk: ftbfs with GCC-10
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 963982

[Debian Bug Tracking System]

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

> close 963982
Bug #963982 [src:intel-mediasdk] intel-mediasdk: Please upload 20.1.0 to 
unstable
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
963982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963982
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:

> close 980239
Bug #980239 [chromium] chromium not installable / upgradeable due to wrong 
dependencies
Marked Bug as done
>
End of message, stopping processing here.

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

Processed: RFS: igmpproxy/0.3-1 -- IGMP multicast routing daemon

[Debian Bug Tracking System]

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

> close 979265
Bug #979265 [sponsorship-requests] RFS: igmpproxy/0.3-1 -- IGMP multicast 
routing daemon
Marked Bug as done
> stop
Stopping processing here.

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

Processed: RFS: udftools/2.3-1 -- tools for UDF filesystems and DVD/CD-R(W) drives

[Debian Bug Tracking System]

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

> close 979249
Bug #979249 [sponsorship-requests] RFS: udftools/2.3-1 -- tools for UDF 
filesystems and DVD/CD-R(W) drives
Marked Bug as done
> stop
Stopping processing here.

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

Bug#511059: marked as done (udftools: cdrwtool -d /dev/hdc -q fails)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 12:21:53 +
with message-id 
and subject line Bug#511059: fixed in udftools 2.3-1
has caused the Debian Bug report #511059,
regarding udftools: cdrwtool -d /dev/hdc -q 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.)


-- 
511059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udftools
Version: 1.0.0b3-14
Severity: normal


$ cdrwtool -d /dev/hdc -q

Output of command:

using device /dev/hdc
870KB internal buffer
setting write speed to 12x
wait_cmd: Bad address
Command failed: bb 00 ff ff 08 40 00 00 00 00 00 00 - sense 00.00.00
set speed
can't unlock door




-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages udftools depends on:
ii  libc6 2.7-16 GNU C Library: Shared libraries
ii  libncurses5   5.7+20081213-1 shared libraries for terminal hand
ii  libreadline5  5.2-3  GNU readline and history libraries

Versions of packages udftools recommends:
ii  udev  0.125-7/dev/ and hotplug management daemo

Versions of packages udftools suggests:
ii  dvd+rw-tools  7.1-3  DVD+-RW/R tools
pn  pmount (no description available)

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: udftools
Source-Version: 2.3-1
Done: Pali Rohár 

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

Debian distribution maintenance software
pp.
Pali Rohár  (supplier of updated udftools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 Jan 2021 18:02:50 +0100
Source: udftools
Architecture: source
Version: 2.3-1
Distribution: unstable
Urgency: medium
Maintainer: Pali Rohár 
Changed-By: Pali Rohár 
Closes: 288455 511059
Changes:
 udftools (2.3-1) unstable; urgency=medium
 .
   * New upstream release
   * cdrwtool format CD-RW according to MMC-6 standard (Closes: #511059)
   * pktsetup is not called for unsupported medias (Closes: #288455)
Checksums-Sha1:
 0d6d12591e57fd4f074674bcaf38c00e38e49387 1745 udftools_2.3-1.dsc
 3eb111de212be510f0bad8d81b8c2a02c339e5b3 581756 udftools_2.3.orig.tar.gz
 b6df41216ad39887fd44d735c4e696fe59403a5a 8184 udftools_2.3-1.debian.tar.xz
 27a8915dcbf9187c7278f067e0f4978d8a4f1c4a 5802 udftools_2.3-1_source.buildinfo
Checksums-Sha256:
 32e867afec1fff629be578e4901e483a162fb4c16b6125557c38b3cbedbbfcb4 1745 
udftools_2.3-1.dsc
 750dcf5c797765eb42265e0a56d1a99f97f94b7f6f4534263a5410503f0caf59 581756 
udftools_2.3.orig.tar.gz
 a50066877b5640e746af07ff063d178572e4ad9c7a819c443abe41875d199353 8184 
udftools_2.3-1.debian.tar.xz
 a110104f1e54ef80ccf0dcdc834285fc27c222d7264304979c98a223e7e59fbc 5802 
udftools_2.3-1_source.buildinfo
Files:
 00738ce07b99712b968a1148ca1ea3f2 1745 otherosfs optional udftools_2.3-1.dsc
 eada8dd40a675763ec71c35655cfd85e 581756 otherosfs optional 
udftools_2.3.orig.tar.gz
 285c6184211b2594b265e2275b786727 8184 otherosfs optional 
udftools_2.3-1.debian.tar.xz
 cd4249ec4cf6b482aa932623305aeb49 5802 otherosfs optional 
udftools_2.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmASp78ACgkQweDZLphv
fH56Aw//XDiLOIXRRRzsdOBvjsRc7Mn8zjHNbI0o9+Fu4K1C6I8OEgztIpMan+2Z
asPcmLzkLG6PC8090d0vC0B0Z6M5uMGpOMXDOz3/emQRCD9V/fyDUM6TnpIpj2fw
6VRnHLlYqMUvqP+oNdys0MOnBQ/lg34ZuVwDYeqVe+QhlSWRlrJ9Qs3NNU/cwWUJ
uo6GjFjHrCKTBym4LZ9qaCmA0Adx5EZ+of+/jpUB7QNkSxjPOgn+LCcKBucpdy+l
y3ACvxnUELbkZG02kpCDtYJT/AH4MMvNRIGG7dtaZWpgZVYfqNZ2DvNekPT9Z2GV
46l0hkjmtvozMhNMytVLQeUglfXRVrwZADD/dRIgGlyh0Nu7/ClUcKB7qjhOa1Kt
u+CHObn71+YUYqOvZADlpa944G761Q2vmMUUtxBP+t99IdhTjpsnCcV/qBDwApaO
8/n3wdfIHqbrzmJ2rBVun4ciQiAZQkmo5NcbIRmCrCRcSYi0pkr/zaxe2JCMFMce

Bug#288455: marked as done (udftools: can't eject iso cdrom (programmatically or manually))

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 12:21:53 +
with message-id 
and subject line Bug#288455: fixed in udftools 2.3-1
has caused the Debian Bug report #288455,
regarding udftools: can't eject iso cdrom (programmatically or manually)
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.)


-- 
288455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=288455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udftools
Version: 1.0.0b3-8
Severity: normal


When cdrom device is setup for packet writing (with "pktsetup 0 /dev/cdrom"),
ordinary iso disks can not be ejected. Command "eject /cdrom" returns the
following error: "eject: unable to eject, last error: Invalid argument". The
CD can not be ejected with button as well. After executing "pktsetup -d 0"
disk can be ejected without problems. In case it does matter, I have Hitachi-LG
combo (exact model is GCC-4120B).

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-grunt
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages udftools depends on:
ii  debconf 1.4.30.11Debian configuration management sy
ii  libc6   2.3.2.ds1-18 GNU C Library: Shared libraries an
ii  libreadline44.3-11   GNU readline and history libraries
ii  makedev 2.3.1-75 Creates device files in /dev

-- debconf information:
  udftools/makedev-ask: Create device files

--- End Message ---
--- Begin Message ---
Source: udftools
Source-Version: 2.3-1
Done: Pali Rohár 

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

Debian distribution maintenance software
pp.
Pali Rohár  (supplier of updated udftools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 Jan 2021 18:02:50 +0100
Source: udftools
Architecture: source
Version: 2.3-1
Distribution: unstable
Urgency: medium
Maintainer: Pali Rohár 
Changed-By: Pali Rohár 
Closes: 288455 511059
Changes:
 udftools (2.3-1) unstable; urgency=medium
 .
   * New upstream release
   * cdrwtool format CD-RW according to MMC-6 standard (Closes: #511059)
   * pktsetup is not called for unsupported medias (Closes: #288455)
Checksums-Sha1:
 0d6d12591e57fd4f074674bcaf38c00e38e49387 1745 udftools_2.3-1.dsc
 3eb111de212be510f0bad8d81b8c2a02c339e5b3 581756 udftools_2.3.orig.tar.gz
 b6df41216ad39887fd44d735c4e696fe59403a5a 8184 udftools_2.3-1.debian.tar.xz
 27a8915dcbf9187c7278f067e0f4978d8a4f1c4a 5802 udftools_2.3-1_source.buildinfo
Checksums-Sha256:
 32e867afec1fff629be578e4901e483a162fb4c16b6125557c38b3cbedbbfcb4 1745 
udftools_2.3-1.dsc
 750dcf5c797765eb42265e0a56d1a99f97f94b7f6f4534263a5410503f0caf59 581756 
udftools_2.3.orig.tar.gz
 a50066877b5640e746af07ff063d178572e4ad9c7a819c443abe41875d199353 8184 
udftools_2.3-1.debian.tar.xz
 a110104f1e54ef80ccf0dcdc834285fc27c222d7264304979c98a223e7e59fbc 5802 
udftools_2.3-1_source.buildinfo
Files:
 00738ce07b99712b968a1148ca1ea3f2 1745 otherosfs optional udftools_2.3-1.dsc
 eada8dd40a675763ec71c35655cfd85e 581756 otherosfs optional 
udftools_2.3.orig.tar.gz
 285c6184211b2594b265e2275b786727 8184 otherosfs optional 
udftools_2.3-1.debian.tar.xz
 cd4249ec4cf6b482aa932623305aeb49 5802 otherosfs optional 
udftools_2.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmASp78ACgkQweDZLphv
fH56Aw//XDiLOIXRRRzsdOBvjsRc7Mn8zjHNbI0o9+Fu4K1C6I8OEgztIpMan+2Z
asPcmLzkLG6PC8090d0vC0B0Z6M5uMGpOMXDOz3/emQRCD9V/fyDUM6TnpIpj2fw
6VRnHLlYqMUvqP+oNdys0MOnBQ/lg34ZuVwDYeqVe+QhlSWRlrJ9Qs3NNU/cwWUJ
uo6GjFjHrCKTBym4LZ9qaCmA0Adx5EZ+of+/jpUB7QNkSxjPOgn+LCcKBucpdy+l
y3ACvxnUELbkZG02kpCDtYJT/AH4MMvNRIGG7dtaZWpgZVYfqNZ2DvNekPT9Z2GV
46l0hkjmtvozMhNMytVLQeUglfXRVrwZADD/dRIgGlyh0Nu7/ClUcKB7qjhOa1Kt
u+CHObn71+YUYqOvZADlpa944G761Q2vmMUUtxBP+t99IdhTjpsnCcV/qBDwApaO
8/n3wdfIHqbrzmJ2rBVun4ciQiAZQkmo5NcbIRmCrCRcSYi0pkr/zaxe2JCMFMce
9LgxHOdxL/MuPiU8AQSnPQXg97ykl2YTn5fkKSwXh6dXnbqM5su5z+Zer5cAIdde

Bug#895836: marked as done (libapache2-mod-auth-gssapi is broken if libfl-dev is installed during the build)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 12:19:25 +
with message-id 
and subject line Bug#895836: fixed in libapache2-mod-auth-gssapi 1.6.3-1
has caused the Debian Bug report #895836,
regarding libapache2-mod-auth-gssapi is broken if libfl-dev is installed during 
the build
to be marked as done.

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

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


-- 
895836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: flex
Version: 2.6.4-6
Severity: important

Dear Maintainer,

After upgrading the version of flex, mod_auth_gssapi (in Debian,
libapache2-mod-auth-gssapi) can no longer be used.  In particular,
apache fails with:

apache2: Syntax error on line 78 of 
/root/mod_auth_gssapi/testsdir/httpd/httpd.conf: Cannot load 
./mod_auth_gssapi.so into server: /usr/lib/x86_64-linux-gnu/libfl.so.2: 
undefined symbol: yylex

Thanks!

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages flex depends on:
ii  debconf [debconf-2.0]  1.5.66
ii  libc6  2.27-3
ii  m4 1.4.18-1

Versions of packages flex recommends:
ii  gcc [c-compiler]4:7.3.0-3
ii  gcc-6 [c-compiler]  6.4.0-16
ii  gcc-7 [c-compiler]  7.3.0-16
ii  libfl-dev   2.6.4-6

Versions of packages flex suggests:
ii  bison2:3.0.4.dfsg-1+b1
ii  build-essential  12.4
pn  flex-doc 

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libapache2-mod-auth-gssapi
Source-Version: 1.6.3-1
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated 
libapache2-mod-auth-gssapi 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, 28 Jan 2021 14:08:14 +0200
Source: libapache2-mod-auth-gssapi
Architecture: source
Version: 1.6.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Closes: 895836
Changes:
 libapache2-mod-auth-gssapi (1.6.3-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #895836)
   * control: Use debhelper-compat, bump to 12.
   * control: Add apache2-bin to build-depends.
   * control: Bump policy to 4.5.1.
Checksums-Sha1:
 fdbb5de36c44c9c2894b84741a913d3e0c0f1d50 2226 
libapache2-mod-auth-gssapi_1.6.3-1.dsc
 88801f89543cc825757c2a9730e01f20e9fcf24a 121840 
libapache2-mod-auth-gssapi_1.6.3.orig.tar.gz
 96ef8b13257b0b078f78e9ca4e46cf579787ed6c 2460 
libapache2-mod-auth-gssapi_1.6.3-1.debian.tar.xz
 a5c250b7229389c6be954dfb40045dcc6604d32f 8740 
libapache2-mod-auth-gssapi_1.6.3-1_source.buildinfo
Checksums-Sha256:
 d72b4ef6b89b2aafd0be36bae2023546a5a74a99c3f840532cb55889c28bddeb 2226 
libapache2-mod-auth-gssapi_1.6.3-1.dsc
 6172cf77a8531c7cdef93a2c66a95f70c06115a2a0d55c359e9bfc783c87af60 121840 
libapache2-mod-auth-gssapi_1.6.3.orig.tar.gz
 987f587c58a6bf03ffe83ac28801811ed497ef729f3d7d6426b73007dba73a7f 2460 
libapache2-mod-auth-gssapi_1.6.3-1.debian.tar.xz
 f1c1ab609e83b5de789d747f18621599db6fae1398eeb2a269b156365c8e37a2 8740 
libapache2-mod-auth-gssapi_1.6.3-1_source.buildinfo
Files:
 c1cee0eef3bb14da0a7c878b6b35f4f5 2226 web optional 
libapache2-mod-auth-gssapi_1.6.3-1.dsc
 685cde219039e2873ec82373de5be066 121840 web optional 
libapache2-mod-auth-gssapi_1.6.3.orig.tar.gz
 1d604e1b1fe5d68706ccbf318f45702c 2460 web optional 
libapache2-mod-auth-gssapi_1.6.3-1.debian.tar.xz
 bafd60f95bd3bdd3887a5ae4a14ac01e 8740 web optional 
libapache2-mod-auth-gssapi_1.6.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmASqUIACgkQy3AxZaiJ

Bug#981250: marked as done (texlive: Update of texlive is extremely slow)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 21:02:32 +0900
with message-id 
and subject line Re: Bug#981250: texlive: Update of texlive is extremely slow
has caused the Debian Bug report #981250,
regarding texlive: Update of texlive is extremely slow
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.)


-- 
981250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive
Version: 2020.20200925-1
Severity: normal

Dear Maintainer,

today the update uf texlive is again extremely slow. Some packages need more
than 3 minutes to update, e.g. texlive-lang-english or texlive-plan-generic

"apt upgrade" for the texlive pakages took from 9:44 to 10:26 = 42 minutes ???

> /var/log$ egrep "upgrade|unpacked" dpkg.log | grep texlive
2021-01-28 09:44:58 upgrade texlive-binaries:amd64 2020.20200327.54578-5
2020.20200327.54578-6
2021-01-28 09:44:58 status unpacked texlive-binaries:amd64
2020.20200327.54578-5
2021-01-28 09:45:07 status unpacked texlive-binaries:amd64
2020.20200327.54578-6
2021-01-28 09:45:12 upgrade texlive-xetex:all 2020.20200925-1 2020.20210113-1
2021-01-28 09:45:12 status unpacked texlive-xetex:all 2020.20200925-1
2021-01-28 09:45:22 status unpacked texlive-xetex:all 2020.20210113-1
2021-01-28 09:45:23 upgrade texlive-lang-german:all 2020.20200925-2
2020.20210113-1
2021-01-28 09:45:23 status unpacked texlive-lang-german:all 2020.20200925-2
2021-01-28 09:45:35 status unpacked texlive-lang-german:all 2020.20210113-1
2021-01-28 09:45:35 upgrade texlive-pstricks:all 2020.20200925-1
2020.20210113-1
2021-01-28 09:45:35 status unpacked texlive-pstricks:all 2020.20200925-1
2021-01-28 09:45:48 status unpacked texlive-pstricks:all 2020.20210113-1
2021-01-28 09:45:49 upgrade texlive-pictures-doc:all 2020.20200925-1
2020.20210113-1
2021-01-28 09:45:49 status unpacked texlive-pictures-doc:all 2020.20200925-1
2021-01-28 09:46:56 status unpacked texlive-pictures-doc:all 2020.20210113-1
2021-01-28 09:46:56 upgrade texlive-pictures:all 2020.20200925-1
2020.20210113-1
2021-01-28 09:46:56 status unpacked texlive-pictures:all 2020.20200925-1
2021-01-28 09:47:56 status unpacked texlive-pictures:all 2020.20210113-1
2021-01-28 09:47:57 upgrade texlive-science-doc:all 2020.20200925-1
2020.20210113-1
2021-01-28 09:47:57 status unpacked texlive-science-doc:all 2020.20200925-1
2021-01-28 09:48:22 status unpacked texlive-science-doc:all 2020.20210113-1
2021-01-28 09:48:23 upgrade texlive-pstricks-doc:all 2020.20200925-1
2020.20210113-1
2021-01-28 09:48:23 status unpacked texlive-pstricks-doc:all 2020.20200925-1
2021-01-28 09:49:13 status unpacked texlive-pstricks-doc:all 2020.20210113-1
2021-01-28 09:49:14 upgrade texlive-latex-extra-doc:all 2020.20200925-1
2020.20210113-1
2021-01-28 09:49:14 status unpacked texlive-latex-extra-doc:all 2020.20200925-1
2021-01-28 09:52:26 status unpacked texlive-latex-extra-doc:all 2020.20210113-1
2021-01-28 09:52:27 upgrade texlive-latex-base-doc:all 2020.20200925-1
2020.20210113-1
2021-01-28 09:52:27 status unpacked texlive-latex-base-doc:all 2020.20200925-1
2021-01-28 09:52:43 status unpacked texlive-latex-base-doc:all 2020.20210113-1
2021-01-28 09:52:44 upgrade texlive-latex-recommended-doc:all 2020.20200925-1
2020.20210113-1
2021-01-28 09:52:44 status unpacked texlive-latex-recommended-doc:all
2020.20200925-1
2021-01-28 09:52:57 status unpacked texlive-latex-recommended-doc:all
2020.20210113-1
2021-01-28 09:52:57 upgrade texlive-formats-extra:all 2020.20200925-1
2020.20210113-1
2021-01-28 09:52:57 status unpacked texlive-formats-extra:all 2020.20200925-1
2021-01-28 09:53:12 status unpacked texlive-formats-extra:all 2020.20210113-1
2021-01-28 09:53:13 upgrade texlive-latex-base:all 2020.20200925-1
2020.20210113-1
2021-01-28 09:53:13 status unpacked texlive-latex-base:all 2020.20200925-1
2021-01-28 09:53:40 status unpacked texlive-latex-base:all 2020.20210113-1
2021-01-28 09:53:40 upgrade texlive-latex-recommended:all 2020.20200925-1
2020.20210113-1
2021-01-28 09:53:40 status unpacked texlive-latex-recommended:all
2020.20200925-1
2021-01-28 09:54:10 status unpacked texlive-latex-recommended:all
2020.20210113-1
2021-01-28 09:54:11 upgrade texlive-bibtex-extra:all 2020.20200925-1
2020.20210113-1
2021-01-28 09:54:11 status unpacked texlive-bibtex-extra:all 2020.20200925-1
2021-01-28 09:55:00 status unpacked texlive-bibtex-extra:all 2020.20210113-1
2021-01-28 09:55:01 upgrade texlive-luatex:all 2020.20200925-1 2020.20210113-1
2021-01-28 09:55:01 status unpacked texlive-luatex:all 2020.20200925-1
2021-01-28 09:55:18 status unpacked 

Processed: Re: 5.9.15 Debian kernel stopped booting on raspi 4 with Elecom USB MSD 056e:6a13

[Debian Bug Tracking System]

Processing control commands:

> close -1 5.10.9-1
Bug #979187 [src:linux] 5.9.15 Debian kernel stopped booting on raspi 4 with 
Elecom USB MSD 056e:6a13
Marked as fixed in versions linux/5.10.9-1.
Bug #979187 [src:linux] 5.9.15 Debian kernel stopped booting on raspi 4 with 
Elecom USB MSD 056e:6a13
Marked Bug as done

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

Bug#981192: marked as done (js2-mode: NMU, moved VCS to emacsen-team ?)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 11:50:01 +
with message-id 
and subject line Bug#981192: fixed in js2-mode 0~20201220-1
has caused the Debian Bug report #981192,
regarding js2-mode: NMU, moved VCS to emacsen-team ?
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.)


-- 
981192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: js2-mode
Version: 0~20180301-1
Severity: normal
X-Debbugs-Cc: debian-emac...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Vincent;

I just NMUed js2-mode (delayed/2). Since the old VCS was gone, I also set up 

  https://salsa.debian.org/emacsen-team/js2-mode

I propose we move the package to the debian emacsen team
umbrella. I've invited you to the team on salsa, so you could continue
staying involved to the degree you want to.

If you prefer to continue maintaining it yourself, then just close
this bug with your next upload (presumably also updating Vcs-*)

I NMUed a new upstream version as the simplest way of fixing the
FTBFS.  Please see the above repo for the NMU diff; there are pretty
extensive upstream changes.



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

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmARbAcACgkQA0U5G1Wq
FSHLHw/+NxPoek+Awr3T4IpX/mXkDr6msVaqxoqj1q9fo723OZbfPW0fO/iAmHk1
qGFOWFLlaRKwuoTbGqjEPyz0kfEg/jeGlq6AZkIhKbl/8XAwmCx3RQgDWnVODxSG
GSglXV2EvVGr4aln1GaK2e0fjSMF39BhtStBYoe+xnSkh5dB5hBDeealJfC19i1J
XUmhPLoBAraKOlin7NJc7u8s6Z9MOztbX62mjzP1elUq99Mrl94DtKa3NmznNO2T
ySYNyTywz+9uTsAqZOaytbDrllInliN6t9cqhNqheIxdjoaV/9PIyu5BVkyBoE0b
8V6QVvbvE7qbu5B22lITuGIWtMfi8V1Z6tPD4nmwtFMZVbV13qfVQSoCgTdq52iN
qADqKY3Xuu1xQIncsASl1hS+5iug7b4l1X9CwtmnVfzZY4sVkBkNhCFFm+wQREnw
Z9DdJv0WPQNC10L6i1A2HQJRazSAfC6d+SniqIeOc+7sQ8ZdqAEuuXqrsFtpIL4Y
AjK1s2H9EDFEvg+x9eLqSNjdUY2ZddJW7nVNrV+DbVuehmBG7/L7K+BITHp/c23P
6NGZyc/1s5xmmHN8E418/zKIkRzcWiLN8BWGKDQEiNxcz2ZQM1cDt9tqgeEa/O0x
U4/WLEjT/w8ES6XgZ0skUK9YsSazSOkaBb1LBkeduKh1vitDaPU=
=vsFq
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: js2-mode
Source-Version: 0~20201220-1
Done: David Bremner 

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

Debian distribution maintenance software
pp.
David Bremner  (supplier of updated js2-mode 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, 28 Jan 2021 07:19:08 -0400
Source: js2-mode
Architecture: source
Version: 0~20201220-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: David Bremner 
Closes: 981192
Changes:
 js2-mode (0~20201220-1) unstable; urgency=medium
 .
   * Adopt package for Debian Emacsen team (Closes: #981192).
   * Bump debhelper compat level to 12
   * Install NEWS.md
   * Assert compliance with policy 4.5.1
Checksums-Sha1:
 081c20b0633c470db1c0266e2996f44ca58aa132 2137 js2-mode_0~20201220-1.dsc
 edfe759cf05d81fa401caeb41270ae3aeb83 3664 
js2-mode_0~20201220-1.debian.tar.xz
Checksums-Sha256:
 ee62a044ce94f6f87b414e2466d37036bc746391b7f011f54741782c6da927d4 2137 
js2-mode_0~20201220-1.dsc
 0cb43e364608b432490c92b7ecf71a4477081b612cad49f6d31e21f3d3cacbbc 3664 
js2-mode_0~20201220-1.debian.tar.xz
Files:
 a189aa6b029a8fe4b4c90f6969417524 2137 editors optional 
js2-mode_0~20201220-1.dsc
 17ac83150dd19504c41fcc6708033c28 3664 editors optional 
js2-mode_0~20201220-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmASn7wACgkQA0U5G1Wq
FSG58g/+ISxmDeGYkQ91gbNQh7Hebj3hmITCSyV9d5DE+SdskEKr9Fhu4j3l+JJp

Bug#980487: marked as done (pipewire: multiarch for pipewire-audio-client-libraries)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 12:21:37 +0100
with message-id 
and subject line Re: Bug#980487: pipewire: multiarch for 
pipewire-audio-client-libraries
has caused the Debian Bug report #980487,
regarding pipewire: multiarch for pipewire-audio-client-libraries
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.)


-- 
980487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pipewire-audio-client-libraries
Version: 0.3.19-2
Severity: wishlist

Hi,

the pipewire-audio-client-libraries package currently ships libraries like:
 /usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_ctl_pipewire.so
 /usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_pipewire.so
 /usr/lib/x86_64-linux-gnu/pipewire-0.3/jack/libjack.so.0.319.0
 /usr/lib/x86_64-linux-gnu/pipewire-0.3/jack/libjacknet.so.0.319.0
 /usr/lib/x86_64-linux-gnu/pipewire-0.3/jack/libjackserver.so.0.319.0

It would nice if the package was multiarch-installable, so that it's
possible to install the i386 versions of these libraries as well
(to use pipewire with i386 binaries playing sound via alsa).
This is currently not possible because of /usr/bin/pw-jack.
Could this binary maybe also be moved to pipewire-bin?

Kind regards,
  Reiner


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi Simon,

On Thu, Jan 28, 2021 at 11:12:33AM +, Simon McVittie wrote:
> On Tue, 19 Jan 2021 at 18:38:57 +0100, Reiner Herrmann wrote:
> > It would nice if the package was multiarch-installable, so that it's
> > possible to install the i386 versions of these libraries
> 
> It should already be multiarch co-installable?
> 
> > This is currently not possible because of /usr/bin/pw-jack.
> 
> It's possible, because pw-jack is a shell script that is identical across
> all architectures (I contributed a patch upstream to make this possible).

I just tried installing it again and it was succeeding now.
The problem was probably because of manually built packages that I had
installed with some local modifications. When I upgraded to your 0.3.19
packages it complained about conflicts in pw-jack.
But upgrading to them now from a clean state worked fine.

Sorry for the noise!

Kind regards,
  Reiner


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

Bug#981168: marked as done (apt: autoremove does not remove dependencies)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 11:31:39 +0100
with message-id <20210128112819.ga1566...@debian.org>
and subject line Re: Bug#981168: apt: autoremove does not remove dependencies
has caused the Debian Bug report #981168,
regarding apt: autoremove does not remove 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.)


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

Dear Maintainer,

I am having some difficulty with apt's autoremove command. In order to get a
clean reproduction, I installed Debian in a fresh virtual machine from the
debian-10.7.0-amd64-netinst.iso that I downloaded this evening.

I ran the following sequence of commands:

# apt update; apt upgrade
# apt install exim4  # 24 packages are installed
# apt remove exim4  # only exim4 is removed, as expected
# apt autoremove  # no other packages are removed!

I would have expected the 23 other packages installed by the install command
would be removed by the subsequent autoremove. Why is this not happening? Is
this a misconfiguration, a bug, or a misunderstanding on my part?

Thank you,
Scott Colby

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-4\.19\.0-13-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.19\.0-13-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.19\.0-13-amd64$";
APT::NeverAutoRemove:: "^linux-modules-4\.19\.0-13-amd64$";
APT::NeverAutoRemove:: "^linux-modules-extra-4\.19\.0-13-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.19\.0-13-amd64$";
APT::NeverAutoRemove:: "^linux-image-unsigned-4\.19\.0-13-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.19\.0-13-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.19\.0-13-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.19\.0-13-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.19\.0-13-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.19\.0-13-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.19\.0-13-amd64$";
APT::NeverAutoRemove:: "^linux-modules-.*-4\.19\.0-13-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.19\.0-13-amd64$";
APT::NeverAutoRemove:: "^linux-cloud-tools-4\.19\.0-13-amd64$";
APT::NeverAutoRemove:: "^linux-buildinfo-4\.19\.0-13-amd64$";
APT::NeverAutoRemove:: "^linux-source-4\.19\.0-13-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-modules";
APT::VersionedKernelPackages:: "linux-modules-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "linux-image-unsigned";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::VersionedKernelPackages:: "linux-cloud-tools";
APT::VersionedKernelPackages:: "linux-buildinfo";
APT::VersionedKernelPackages:: "linux-source";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Compressor "";

Processed: Re: autopkgtest-virt-qemu assumes child qemu-system-* is quiet to stdout

[Debian Bug Tracking System]

Processing control commands:

> close -1 5.16
Bug #975392 [autopkgtest] autopkgtest-virt-qemu assumes child qemu-system-* is 
quiet to stdout
Marked as fixed in versions autopkgtest/5.16.
Bug #975392 [autopkgtest] autopkgtest-virt-qemu assumes child qemu-system-* is 
quiet to stdout
Marked Bug as done

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

Bug#981226: marked as done (redis: New systemd integration breaks replicaof handling)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 10:18:47 +
with message-id 
and subject line Bug#981226: fixed in redis 5:6.0.9-4
has caused the Debian Bug report #981226,
regarding redis: New systemd integration breaks replicaof handling
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.)


-- 
981226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981226
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: redis
Source-Version: 5:6.0.9-3
Severity: important
Tags: upstream patch
Forwarded: https://github.com/redis/redis/pull/8409

[ This might be worth being serious, but I'm not sure this falls under
  uncommon usage or similar, or not, so please bump if you agree. :) ]

Hi!

While preparing to switch to bullseye, we noticed that the new systemd
integration breaks with replicaof handling.

I've submitted this upstream, but it would be nice to fix in Debian
even if upstream does not apply this in time for the freeze.

The github PR and the attached patch against the version in Debian,
describe the problem in further detail.

Thanks,
Guillem
From f9505104123664c45b762b8a7bb15406c205c01d Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Tue, 19 Jan 2021 00:34:59 +0100
Subject: [PATCH] Send the readiness notification when we are ready to accept
 connections

On a replica we do accept connections, even though commands accessing
the database will operate in read-only mode. But the server is still
already operational and processing commands.

Not sending the readiness notification means that on a HA setup where
the nodes all start as replicas (with replicaof in the config) with
a replica that cannot connect to the master server and which might not
come back in a predictable amount of time or at all, the service
supervisor will end up timing out the service and terminating it, with
no option to promote it to be the main instance. This seems counter to
what the readiness notification is supposed to be signaling.

Instead send the readiness notification when we start accepting
commands, and then send the various server status changes as that.

Fixes: commit 641c64ada10404356fc76c0b56a69b32c76f253c
Fixes: commit dfb598cf3304818e608ceb6b5d9529a293345c4a
---
 src/replication.c |6 ++
 src/server.c  |4 ++--
 2 files changed, 4 insertions(+), 6 deletions(-)

--- a/src/replication.c
+++ b/src/replication.c
@@ -1832,8 +1832,7 @@ void readSyncBulkPayload(connection *con
 serverLog(LL_NOTICE, "MASTER <-> REPLICA sync: Finished with success");
 
 if (server.supervised_mode == SUPERVISED_SYSTEMD) {
-redisCommunicateSystemd("STATUS=MASTER <-> REPLICA sync: Finished with success. Ready to accept connections.\n");
-redisCommunicateSystemd("READY=1\n");
+redisCommunicateSystemd("STATUS=MASTER <-> REPLICA sync: Finished with success. Ready to accept connections in read-write mode.\n");
 }
 
 /* Restart the AOF subsystem now that we finished the sync. This
@@ -2340,8 +2339,7 @@ void syncWithMaster(connection *conn) {
 if (psync_result == PSYNC_CONTINUE) {
 serverLog(LL_NOTICE, "MASTER <-> REPLICA sync: Master accepted a Partial Resynchronization.");
 if (server.supervised_mode == SUPERVISED_SYSTEMD) {
-redisCommunicateSystemd("STATUS=MASTER <-> REPLICA sync: Partial Resynchronization accepted. Ready to accept connections.\n");
-redisCommunicateSystemd("READY=1\n");
+redisCommunicateSystemd("STATUS=MASTER <-> REPLICA sync: Partial Resynchronization accepted. Ready to accept connections in read-write mode.\n");
 }
 return;
 }
--- a/src/server.c
+++ b/src/server.c
@@ -5324,10 +5324,10 @@ int main(int argc, char **argv) {
 if (server.supervised_mode == SUPERVISED_SYSTEMD) {
 if (!server.masterhost) {
 redisCommunicateSystemd("STATUS=Ready to accept connections\n");
-redisCommunicateSystemd("READY=1\n");
 } else {
-redisCommunicateSystemd("STATUS=Waiting for MASTER <-> REPLICA sync\n");
+redisCommunicateSystemd("STATUS=Ready to accept connections in read-only mode. Waiting for MASTER <-> REPLICA sync\n");
 }
+redisCommunicateSystemd("READY=1\n");
 }
 } else {
 InitServerLast();
--- End Message ---
--- Begin Message ---
Source: redis
Source-Version: 5:6.0.9-4
Done: Chris Lamb 

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

A summary of the changes between this version and 

Bug#980980: marked as done (linux-image-5.10.0-2-arm64-unsigned: flood of false udev messages make udisks2 eat CPU usage on usb-booted raspi4)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 19:04:07 +0900 (JST)
with message-id <20210128.190407.234019808762749623.ryuta...@ict.e.titech.ac.jp>
and subject line Re: linux-image-5.10.0-2-arm64-unsigned: flood of false udev 
messages make udisks2 eat CPU usage on usb-booted raspi4
has caused the Debian Bug report #980980,
regarding linux-image-5.10.0-2-arm64-unsigned: flood of false udev messages 
make udisks2 eat CPU usage on usb-booted raspi4
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.)


-- 
980980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.10.9-1
Severity: important
Tags: upstream bullseye
Control: block -1 by 977694

Dear Maintainer,

After booting raspi 4b from USB MSDand installation of
udisks2 2.9.1-3 by
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977694#56

udev starts giving flood of false messages like below,
and the udisks2, udev and dbus daemons eat nearly 100% of CPU
in total. The flood of false messages disappears by removing udisks2
package.

This symptom is also observed with the vanilla upstream kernel.

Best regards, Ryutaroh Matsumoto


monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[1532.887313] change   
/devices/platform/emmc2bus/fe34.emmc2/mmc_host/mmc1/mmc1:0007/block/mmcblk1 
(block)
KERNEL[1532.887432] change   
/devices/platform/emmc2bus/fe34.emmc2/mmc_host/mmc1/mmc1:0007/block/mmcblk1/mmcblk1p1
 (block)
KERNEL[1532.887485] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda
 (block)
KERNEL[1532.887537] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1
 (block)
KERNEL[1532.887588] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
KERNEL[1532.887640] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda3
 (block)
UDEV  [1532.929456] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda
 (block)
UDEV  [1532.938261] change   
/devices/platform/emmc2bus/fe34.emmc2/mmc_host/mmc1/mmc1:0007/block/mmcblk1 
(block)
UDEV  [1532.945960] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1
 (block)
UDEV  [1532.961346] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
UDEV  [1532.966981] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda3
 (block)
UDEV  [1532.999693] change   
/devices/platform/emmc2bus/fe34.emmc2/mmc_host/mmc1/mmc1:0007/block/mmcblk1/mmcblk1p1
 (block)
KERNEL[1535.645238] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
UDEV  [1535.656113] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
KERNEL[1535.667023] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
UDEV  [1535.677595] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
KERNEL[1535.699075] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
UDEV  [1535.711964] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
KERNEL[1535.750938] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
UDEV  [1535.762856] change   
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2
 (block)
KERNEL[1535.807667] change   

Bug#971182: marked as done (go-mtpfs: FTBFS: src/github.com/hanwen/go-mtpfs/main.go:68:11: undefined: fuse.NewLockingRawFileSystem)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 09:48:24 +
with message-id 
and subject line Bug#971182: fixed in go-mtpfs 1.0.0-1
has caused the Debian Bug report #971182,
regarding go-mtpfs: FTBFS: src/github.com/hanwen/go-mtpfs/main.go:68:11: 
undefined: fuse.NewLockingRawFileSystem
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.)


-- 
971182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: go-mtpfs
Version: 0.0~git20180209.d6f8f3c-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 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 --buildsystem=golang --with=golang
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
>dh_auto_build -O--buildsystem=golang
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 
> github.com/hanwen/go-mtpfs github.com/hanwen/go-mtpfs/fs 
> github.com/hanwen/go-mtpfs/mtp
> internal/unsafeheader
> internal/cpu
> internal/bytealg
> runtime/internal/atomic
> runtime/internal/sys
> runtime/internal/math
> runtime
> internal/reflectlite
> errors
> math/bits
> math
> unicode/utf8
> strconv
> internal/race
> sync/atomic
> sync
> unicode
> reflect
> sort
> internal/fmtsort
> io
> internal/oserror
> syscall
> internal/syscall/unix
> time
> internal/poll
> internal/syscall/execenv
> internal/testlog
> os
> fmt
> strings
> flag
> bytes
> context
> path/filepath
> io/ioutil
> log
> github.com/hanwen/go-fuse/splice
> encoding/binary
> golang.org/x/sys/internal/unsafeheader
> golang.org/x/sys/unix
> os/exec
> path
> github.com/hanwen/go-fuse/fuse
> github.com/hanwen/go-fuse/fuse/nodefs
> runtime/cgo
> github.com/hanwen/usb
> # github.com/hanwen/usb
> cgo-gcc-prolog: In function ‘_cgo_afe072e410cc_Cfunc_libusb_set_debug’:
> cgo-gcc-prolog:662:2: warning: ‘libusb_set_debug’ is deprecated: Use 
> libusb_set_option instead [-Wdeprecated-declarations]
> In file included from src/github.com/hanwen/usb/usb.go:8:
> /usr/include/libusb-1.0/libusb.h:1325:18: note: declared here
>  1325 | void LIBUSB_CALL libusb_set_debug(libusb_context *ctx, int level);
>   |  ^~~~
> math/rand
> regexp/syntax
> regexp
> github.com/hanwen/go-mtpfs/mtp
> github.com/hanwen/go-mtpfs/fs
> github.com/hanwen/go-mtpfs
> # github.com/hanwen/go-mtpfs
> src/github.com/hanwen/go-mtpfs/main.go:68:11: undefined: 
> fuse.NewLockingRawFileSystem
> dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 
> github.com/hanwen/go-mtpfs github.com/hanwen/go-mtpfs/fs 
> github.com/hanwen/go-mtpfs/mtp returned exit code 2
> make: *** [debian/rules:6: build] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/09/26/go-mtpfs_0.0~git20180209.d6f8f3c-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: go-mtpfs
Source-Version: 1.0.0-1
Done: Julian Gilbey 

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

Debian distribution maintenance software
pp.
Julian Gilbey  (supplier of updated go-mtpfs 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, 28 Jan 2021 09:21:04 +
Source: go-mtpfs
Architecture: source
Version: 1.0.0-1
Distribution: unstable
Urgency: medium

Bug#962843: marked as done (please package new upstream version 1.0.0 or later)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 09:48:24 +
with message-id 
and subject line Bug#962843: fixed in go-mtpfs 1.0.0-1
has caused the Debian Bug report #962843,
regarding please package new upstream version 1.0.0 or later
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.)


-- 
962843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: go-mtpfs
Severity: normal

Hi,

Upstream released v1.0.0 several months ago.  Please package this version or 
newer.

Thanks!
Nicholas

P.S. My old died, and the replacement doesn't support MSC, which is why I'm 
reviewing the available options for MTP support in Debian.
--- End Message ---
--- Begin Message ---
Source: go-mtpfs
Source-Version: 1.0.0-1
Done: Julian Gilbey 

We believe that the bug you reported is fixed in the latest version of
go-mtpfs, 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.
Julian Gilbey  (supplier of updated go-mtpfs 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, 28 Jan 2021 09:21:04 +
Source: go-mtpfs
Architecture: source
Version: 1.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Julian Gilbey 
Closes: 962843 971182
Changes:
 go-mtpfs (1.0.0-1) unstable; urgency=medium
 .
   * New upstream release (closes: #962843, #971182)
   * Update team email address
   * Bump Standards-Version and debhelper-compat
   * Add manpage
Checksums-Sha1:
 c9b4b259554781d9f88d31c7ac5712bcc236c17e 2130 go-mtpfs_1.0.0-1.dsc
 5e011eaab33317e9704f1058aaca08518ddbcb70 44589 go-mtpfs_1.0.0.orig.tar.gz
 8eb2a64b01ee16abf637071f4a800354fc15f73d 4712 go-mtpfs_1.0.0-1.debian.tar.xz
 2e7e10c840c586b1fff9337c6861d92235241203 6131 go-mtpfs_1.0.0-1_amd64.buildinfo
Checksums-Sha256:
 c1397717e2a916aa24cf1f1f604c72c3973031be8bbf812e53b253cb34879ea6 2130 
go-mtpfs_1.0.0-1.dsc
 47060acf74c9f7a612f492c041c9463efb37eab4f9a74eca96686ed61bbbe7ec 44589 
go-mtpfs_1.0.0.orig.tar.gz
 ec2aa850e6d4022014811adc3fdd46cfe8e81e58756354721b905dffade5a8a5 4712 
go-mtpfs_1.0.0-1.debian.tar.xz
 102a9f55e40c78f669e89af17b7f8e4e590b8a53bd7003ef6d440e9305cbc4d4 6131 
go-mtpfs_1.0.0-1_amd64.buildinfo
Files:
 fc2f608b5c53e66fce98f16aec8e7855 2130 devel optional go-mtpfs_1.0.0-1.dsc
 91167ffb362e5fae096c1e50cf90674c 44589 devel optional 
go-mtpfs_1.0.0.orig.tar.gz
 3421726d41d95f647449d5c7d5e319e9 4712 devel optional 
go-mtpfs_1.0.0-1.debian.tar.xz
 45046458b2fefb9d1244dfc784e64be9 6131 devel optional 
go-mtpfs_1.0.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEEfhrD+iemSShMMj72aVxCkxbAe/4FAmASgycPHGpkZ0BkZWJp
YW4ub3JnAAoJEGlcQpMWwHv+mVsP/1oUa8FkD92iNTSzY6iClCZ7NPlCN6iOggOQ
VmkpVT+Iiwjb5eaHmjVbzUTwqpuLK3sIMGd+Ns0ekDWfAuZv47vcc2J9qPmnUJi+
nCscKw4/c6zg0EFLsoSgg50BOiLedlQQle49TgvOMx5aOisFBvq9EI874Z/nNrRc
Mz1VuZL0FA9b90z71NGpDcsmN72ChKmnYA5lT2RsYkdX2FUGytiymzQzuxAays5v
o3PPzCYCWbSZa4zwy3xC2EQ88B3cOai0YkgppvPixngEPT9feDEByU/eEmewQ38F
9P2gCK+2AINrlMYrMv2YqNejLUqrmhzSZ3wx2jLEkZqn11HyDuz2wPq6SjQHDAT0
OkBnF3jGR6BeWxw5SEwAH2PjvjF9V28AMCD9z37SnvHRJMasiCSDUL0abjOulch7
b83QDXxIyKb6esUNpzWpES/vlsE3pv4XsmyZxLBEPcqryLIX+XItL2+68FwAawdc
8eOkZq4McWix+ekSfw43qs9OB97pn0Ic4chnJKVzZKSCSGGmHnESslyxaYll1gqw
QQWA8UmcY6GRBThFriasxYoiUt+RJsAXG5MvzGHOI578sg5cVnCdOM9SjdRd1Y/z
X7hXRo999g3gHHVnKODKyYuuM94Ir29lajdl0XCt2dZj1plEpjSAojYOH6LsVIU1
1hIhj5Cg
=jeoX
-END PGP SIGNATURE End Message ---

Bug#980803: marked as done (The examples don't show up in Qt Creator)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 12:44:18 +0300
with message-id 
and subject line Re: Bug#980803: Solved
has caused the Debian Bug report #980803,
regarding The examples don't show up in Qt Creator
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.)


-- 
980803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qtbase5-examples
Version: 5.15.2+dfsg-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Qt Creator 4.14.0 doesn't show the examples after installing the package
qtbase5-examples. Trying workarounds that are circulating on the internet
also don't work, like installing the additional following packages:
qtbase5-doc-html, qt5-doc and qt5-doc-html.


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

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

Versions of packages qtbase5-examples depends on:
ii  libc6 2.31-9
ii  libgcc-s1 10.2.1-6
ii  libgl11.3.2-1
ii  libqt5concurrent5 5.15.2+dfsg-2
ii  libqt5core5a [qtbase-abi-5-15-2]  5.15.2+dfsg-2
ii  libqt5dbus5   5.15.2+dfsg-2
ii  libqt5gui55.15.2+dfsg-2
ii  libqt5network55.15.2+dfsg-2
ii  libqt5opengl5 5.15.2+dfsg-2
ii  libqt5printsupport5   5.15.2+dfsg-2
ii  libqt5sql55.15.2+dfsg-2
ii  libqt5test5   5.15.2+dfsg-2
ii  libqt5widgets55.15.2+dfsg-2
ii  libqt5xml55.15.2+dfsg-2
ii  libstdc++610.2.1-6

qtbase5-examples recommends no packages.

qtbase5-examples suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, Jan 27, 2021 at 06:38:03PM -0300, Limon Kiwi wrote:
> Well, I configured a kit to build projects and the examples appeared. So, I
> don't know if this is the way it should work, but I solved it. Thanks for
> your response!

Thanks for the follow up, I am closing the bug then.

If the same happens again, please file a bug against Qt Creator:
“qmake -query QT_INSTALL_EXAMPLES” reports the correct path, so Qt Creator
should find the examples there.

--
Dmitry Shachnev


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

Bug#978198: marked as done (r-cran-rstan: FTBFS: Eigen_NumTraits.hpp:200:77: error: wrong number of template arguments (8, should be 9))

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 10:45:07 +0100
with message-id <20210128094507.ga11...@xanadu.blop.info>
and subject line Re: Bug#978198: r-cran-rstan: FTBFS: 
Eigen_NumTraits.hpp:200:77: error: wrong number of template arguments (8, 
should be 9)
has caused the Debian Bug report #978198,
regarding r-cran-rstan: FTBFS: Eigen_NumTraits.hpp:200:77: error: wrong number 
of template arguments (8, should be 9)
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.)


-- 
978198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-rstan
Version: 2.21.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> g++ -std=gnu++14 -I"/usr/share/R/include" -DNDEBUG -I"../inst/include" 
> -I"../inst/include/boost_not_in_BH" -I"." -DBOOST_DISABLE_ASSERTS 
> -DBOOST_PHOENIX_NO_VARIADIC_EXPRESSION -DBOOST_NO_AUTO_PTR -D_REENTRANT 
> -DSTAN_THREADS   -I'/usr/lib/R/site-library/Rcpp/include' 
> -I'/usr/lib/R/site-library/RcppEigen/include' 
> -I'/usr/lib/R/site-library/BH/include' 
> -I'/usr/lib/R/site-library/StanHeaders/include' 
> -I'/usr/lib/R/site-library/RcppParallel/include'-fpic  -g -O2 
> -fdebug-prefix-map=/build/r-base-oKyfjH/r-base-4.0.3=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g  -c Module.cpp -o Module.o
> In file included from 
> /usr/lib/R/site-library/RcppEigen/include/Eigen/Core:397,
>  from /usr/lib/R/site-library/RcppEigen/include/Eigen/Dense:1,
>  from 
> /usr/lib/R/site-library/StanHeaders/include/stan/math/prim/mat/fun/Eigen.hpp:13,
>  from 
> /usr/lib/R/site-library/StanHeaders/include/stan/math/prim/mat/meta/append_return_type.hpp:4,
>  from 
> /usr/lib/R/site-library/StanHeaders/include/stan/math/prim/meta.hpp:9,
>  from 
> /usr/lib/R/site-library/StanHeaders/include/stan/math/memory/stack_alloc.hpp:7,
>  from 
> /usr/lib/R/site-library/StanHeaders/include/stan/math/rev/core/autodiffstackstorage.hpp:4,
>  from 
> /usr/lib/R/site-library/StanHeaders/include/stan/math/rev/core.hpp:4,
>  from ./stan/model/model_base.hpp:5,
>  from Module.cpp:2:
> /usr/lib/R/site-library/RcppEigen/include/Eigen/src/Core/arch/SSE/PacketMath.h:60:39:
>  warning: ignoring attributes on template argument ‘__m128’ 
> [-Wignored-attributes]
>60 | template<> struct is_arithmetic<__m128>  { enum { value = true }; };
>   |   ^
> /usr/lib/R/site-library/RcppEigen/include/Eigen/src/Core/arch/SSE/PacketMath.h:61:40:
>  warning: ignoring attributes on template argument ‘__m128i’ 
> [-Wignored-attributes]
>61 | template<> struct is_arithmetic<__m128i> { enum { value = true }; };
>   |^
> /usr/lib/R/site-library/RcppEigen/include/Eigen/src/Core/arch/SSE/PacketMath.h:62:40:
>  warning: ignoring attributes on template argument ‘__m128d’ 
> [-Wignored-attributes]
>62 | template<> struct is_arithmetic<__m128d> { enum { value = true }; };
>   |^
> /usr/lib/R/site-library/RcppEigen/include/Eigen/src/Core/arch/SSE/PacketMath.h:161:43:
>  warning: ignoring attributes on template argument 
> ‘Eigen::internal::Packet4f’ {aka ‘__m128’} [-Wignored-attributes]
>   161 | template<> struct unpacket_traits { typedef float  type; 
> enum {size=4, alignment=Aligned16}; typedef Packet4f half; };
>   |   ^
> /usr/lib/R/site-library/RcppEigen/include/Eigen/src/Core/arch/SSE/PacketMath.h:162:43:
>  warning: ignoring attributes on template argument 
> ‘Eigen::internal::Packet2d’ {aka ‘__m128d’} [-Wignored-attributes]
>   162 | template<> struct unpacket_traits { typedef double type; 
> enum {size=2, alignment=Aligned16}; typedef Packet2d half; };
>   |   ^
> /usr/lib/R/site-library/RcppEigen/include/Eigen/src/Core/arch/SSE/PacketMath.h:163:43:
>  warning: ignoring attributes on template argument 
> ‘Eigen::internal::Packet4i’ {aka ‘__m128i’} [-Wignored-attributes]
>   163 | template<> struct unpacket_traits { typedef inttype; 
> enum {size=4, alignment=Aligned16}; typedef Packet4i half; };
>   |   ^
> 

Processed: Re: Bug#981241: tracker.debian.org: please update uscan

[Debian Bug Tracking System]

Processing control commands:

> close -1
Bug #981241 [tracker.debian.org] tracker.debian.org: please update uscan
Marked Bug as done

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

Bug#981152: marked as done (ncmpc: Assertion failed: i < filelist->size() during "Browse" while another client is repeatedly clearing the playlist queue)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 10:02:29 +0100
with message-id <1b8f31ff-b22a-416e-9394-ce0027aee...@azylum.org>
and subject line Re: Bug#981152: ncmpc: Assertion failed: i < filelist->size() 
during "Browse" while another client is repeatedly clearing the playlist queue
has caused the Debian Bug report #981152,
regarding ncmpc: Assertion failed: i < filelist->size() during "Browse" while 
another client is repeatedly clearing the playlist queue
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.)


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

running ncmpc to connect to an mpd server, i get a crash with a
warning about "Assertion failed:

ncmpc: ../src/FileListPage.cxx:492: virtual void 
FileListPage::PaintListItem(WINDOW*, unsigned int, unsigned int, unsigned int, 
bool) const: Assertion `i < filelist->size()' failed.
 Aborted

I get this warning by going into the "Browse" view (hitting '3') and
then navigating to any of the listed folders by hitting enter.  It
seems to do this when viewing any of the subfolders i investigate
using "Browse".

Below is a backtrace from such an assertion:

#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x77ae8537 in __GI_abort () at abort.c:79
#2  0x77ae840f in __assert_fail_base (fmt=0x77c51128 "%s%s%s:%u: 
%s%sAssertion `%s' failed.\n%n", assertion=0x55593307 "i < 
filelist->size()", file=0x5559320b "../src/FileListPage.cxx", line=492, 
function=) at assert.c:92
#3  0x77af7662 in __GI___assert_fail 
(assertion=assertion@entry=0x55593307 "i < filelist->size()", 
file=file@entry=0x5559320b "../src/FileListPage.cxx", line=line@entry=492, 
function=function@entry=0x55593420 "virtual void 
FileListPage::PaintListItem(WINDOW*, unsigned int, unsigned int, unsigned int, 
bool) const") at assert.c:101
#4  0x55573070 in FileListPage::PaintListItem (this=, 
w=, i=, y=1, width=, 
selected=) at ../src/FileListPage.cxx:492
#5  0x5557497d in ListWindow::Paint (this=0x55608798, renderer=...) 
at ../src/ListWindow.cxx:56
#6  0x5556eaa7 in ScreenManager::Paint (this=0x7fffe0a8, 
main_dirty=) at ../src/screen_paint.cxx:51
#7  0x5556dd18 in ScreenManager::Update (this=, c=..., 
seek=...) at ../src/screen.cxx:226
#8  0x5556496e in mpdclient_idle_callback (events=) at 
../src/Main.cxx:193
#9  0x555676c8 in mpdclient::OnIdle (this=0x7fffdeb0, 
_events=) at ../src/mpdclient.cxx:72
#10 0x55565c8c in mpdclient::GetConnection 
(this=this@entry=0x7fffdeb0) at ../src/mpdclient.cxx:471
#11 0x55573321 in screen_file_load_list (filelist=..., 
current_path=0x556087f8 "cd-tracks", c=0x7fffdeb0) at 
../src/FileBrowserPage.cxx:92
#12 FileBrowserPage::Reload (this=this@entry=0x55608780, c=...) at 
../src/FileBrowserPage.cxx:111
#13 0x55573465 in FileBrowserPage::ChangeDirectory 
(this=this@entry=0x55608780, c=..., new_path=...) at 
../src/FileBrowserPage.cxx:123
#14 0x555736fd in FileBrowserPage::ChangeToEntry (this=0x55608780, 
c=..., entry=...) at ../src/FileBrowserPage.cxx:163
#15 0x55573c25 in FileBrowserPage::HandleEnter (this=0x55608780, 
c=...) at ../src/FileBrowserPage.cxx:196
#16 0x55572c11 in FileListPage::OnCommand (cmd=Command::PLAY, c=..., 
this=0x55608780) at ../src/FileListPage.cxx:431
#17 FileListPage::OnCommand (this=this@entry=0x55608780, c=..., 
cmd=cmd@entry=Command::PLAY) at ../src/FileListPage.cxx:372
#18 0x55573cdd in FileBrowserPage::OnCommand (this=0x55608780, 
c=..., cmd=Command::PLAY) at ../src/FileBrowserPage.cxx:350
#19 0x5556e338 in ScreenManager::OnCommand (this=0x7fffe0a8, c=..., 
seek=..., cmd=cmd@entry=Command::PLAY) at ../src/screen.cxx:232
#20 0x55564558 in do_input_event (event_loop=..., 
cmd=cmd@entry=Command::PLAY) at ../src/Main.cxx:231
#21 0x5556b89a in AsyncUserInput::OnSocketReady (this=0x7fffe360) 
at ../src/event/SocketEvent.hxx:94
#22 0x5558dc79 in EventLoop::Run (this=this@entry=0x7fffde50) at 
../src/event/Loop.cxx:332
#23 0x55564a54 in Instance::Run (this=this@entry=0x7fffde50) at 
../src/Instance.cxx:100
#24 0x5556385c in main (argc=-8624, argv=0x7fffe4b8) at 
../src/Main.cxx:351

One thing to note: i only see this behavior when the same mpd server
has another client connected to it that is 

Bug#977182: marked as done (xpdf: Switch to xpopple as new upstream for Debian's xpdf?)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 08:20:00 +
with message-id 
and subject line Bug#977182: fixed in xpdf 3.04+git20210103-1
has caused the Debian Bug report #977182,
regarding xpdf: Switch to xpopple as new upstream for Debian's xpdf?
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.)


-- 
977182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xpdf
Version: 3.04-14
Severity: important
X-Debbugs-Cc: Gianfranco Costamagna ,GOTO Masanori 
,Sebastien Bacher ,Iain Lane 


Dear people interested in Debian's xpdf,

looking at how things went with Debian's xpdf since Micheal orphaned the
package in 2016, I'm doubtful how long this is still feasible. In fact,
I thought it was already dead, when I found the xpopple repository,
which already contained all that was necessary to adapt to current
poppler (which still took several hours fighting or rather hand-patching).

I think if we want to continue to have a motif and poppler based xpdf in
Debian, we should switch to using xpopple as upstream. To this end I
wrote the below email (but failed to properly involve the bts).

This also relates to the question raised in #873951 whether we shouldn't
follow xpdf 4.x's switch to QT and related development, but given that
they're not using poppler, IMHO this is only going to be even more
complicated that continuing as before.

Florian

-

From: Florian Schlichting 
To: Adam Sampson 
Date: Fri, 11 Dec 2020 11:18:48 +0100
Subject: xpopple as new upstream for Debian's xpdf?

Hi Adam,

the other day, when I looked into the build failures that have kept
Debian's xpdf package out of the upcoming release for several months, I
happened upon your xpopple project (http://offog.org/code/xpopple/),
which I hadn't been aware of before. It seems that since 2014, you've
been doing right what we've struggled to do in Debian: deleting obsolete
code, moving files for good instead of just for the build, applying
patches instead of fighting with an unwieldy quilt queue, and most of
all: following poppler development closely, updating xpdf accordingly
while cleaning up some legacy code. This has been enormously helpful
for my recent upload, thanks a ton!

>From my position it looks like Debian should stop what it's been
increasingly unable to accomplish properly, and instead switch over to
xpopple as its upstream source for the xpdf package.

Do you think xpopple is ready for that? Are there areas where xpopple
does not provide any features that Debian's xpdf currently offers? (I
notice you're based off xpdf 3.03, but am unable to judge which parts if
any of the 3.04 changelog apply to the part that we're still using; the
new text extractor seems to be patched out again?)

And: Are you interested to act as upstream developer for what may be a
substantial user base, which can come up with all kinds of problems and
suggestions not related to your personal use case?

(Cc the Debian bug tracker so that other people interested in xpdf can
know what's going on; I might be able to help with packaging and bug
triaging, but I've never found the time to familiarize myself with
poppler enough to know what's going on)

Looking forward to hear from you!
Florian
--- End Message ---
--- Begin Message ---
Source: xpdf
Source-Version: 3.04+git20210103-1
Done: Florian Schlichting 

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

Debian distribution maintenance software
pp.
Florian Schlichting  (supplier of updated xpdf 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, 28 Jan 2021 15:58:32 +0800
Source: xpdf
Architecture: source
Version: 3.04+git20210103-1
Distribution: unstable
Urgency: medium
Maintainer: Florian Schlichting 
Changed-By: Florian Schlichting 
Closes: 606885 848631 863382 942086 945188 968354 971805 977182
Changes:
 xpdf (3.04+git20210103-1) unstable; urgency=medium
 .
   * Import new upstream version 3.04+git20210103
 + switch to 

Bug#971805: marked as done (Configuration file keyword 'textEncoding' not recognised)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 08:20:00 +
with message-id 
and subject line Bug#971805: fixed in xpdf 3.04+git20210103-1
has caused the Debian Bug report #971805,
regarding Configuration file keyword 'textEncoding' not recognised
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.)


-- 
971805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xpdf
Version: 3.04-13

Like described in #863382 for a different config file command, xpdf reports

Config Error: Unknown config file command 'textEncoding' 
(/etc/xpdf/xpdfrc:)

when the config file contains it. However, xpdfrc(5) lists this option as 
valid.

I assume this needs to be fixed upstream - either in the code, or in the 
manpage.
--- End Message ---
--- Begin Message ---
Source: xpdf
Source-Version: 3.04+git20210103-1
Done: Florian Schlichting 

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

Debian distribution maintenance software
pp.
Florian Schlichting  (supplier of updated xpdf 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, 28 Jan 2021 15:58:32 +0800
Source: xpdf
Architecture: source
Version: 3.04+git20210103-1
Distribution: unstable
Urgency: medium
Maintainer: Florian Schlichting 
Changed-By: Florian Schlichting 
Closes: 606885 848631 863382 942086 945188 968354 971805 977182
Changes:
 xpdf (3.04+git20210103-1) unstable; urgency=medium
 .
   * Import new upstream version 3.04+git20210103
 + switch to xpopple as new upstream (closes: #977182)
 + fix obvious memory leaks (closes: #945188, #942086)
 + no longer crash on empty documents (closes: #968354)
 + properly ask for passwords (closes: #606885)
 + correctly recognize working and document obsolete config file commands
   (closes: #971805, #863382)
   * Drop patches, all applied in (or obsoleted by) xpopple upstream
   * Bump dh compat to level 13
   * Greatly simplify d/rules (but keep linking to libpaper)
   * Keep installing our xpdf wrapper script
   * Ensure wrapper script correctly handles all xpdf options
   * Add wrapper script options back to xpdf manpage
   * Drop obsolete language support files and infrastructure
   * Mention new upstream in relevant places, drop d/watch
   * Adopt xpdf (closes: #848631)
   * Ship TODO in docs
   * Add Rules-Requires-Root: no
   * Declare compliance with Debian Policy 4.5.1
Checksums-Sha1:
 40e2a06d4197afe5c59194743175ed5cb76bce55 1954 xpdf_3.04+git20210103-1.dsc
 c49eefa7d8a2359fa6f75d97753547340fe1158a 123005 
xpdf_3.04+git20210103.orig.tar.gz
 4b83474cdabc693f1bdf1f7c1c778c0446157781 23668 
xpdf_3.04+git20210103-1.debian.tar.xz
 9cad89f4b3518e7f8d6e58980da150431e24b8e0 8092 
xpdf_3.04+git20210103-1_amd64.buildinfo
Checksums-Sha256:
 3e47cdedacae84aee3ec1cbf3151698afe3a2ca83bd0aaa4611dbaf0487968e5 1954 
xpdf_3.04+git20210103-1.dsc
 8c00465f2e362377459ec6d82c0bfe2df9b80ddd98d602e08f41c988efa56fc0 123005 
xpdf_3.04+git20210103.orig.tar.gz
 6504e23ca0ce5e8a91b17973d6fc5e73aefe0ccadba73707a1de4721d2f2ecce 23668 
xpdf_3.04+git20210103-1.debian.tar.xz
 bfc3e2a91a4a4df46f6aca43efbafdbd6b91350dbb0928ab31fdab3059e503cc 8092 
xpdf_3.04+git20210103-1_amd64.buildinfo
Files:
 b38ab56c1cc5eeef1ece34a05a280648 1954 text optional xpdf_3.04+git20210103-1.dsc
 80eaa44277edac0f6de780f13e1bb350 123005 text optional 
xpdf_3.04+git20210103.orig.tar.gz
 0662269a02ad92d16e0d2fced32301e5 23668 text optional 
xpdf_3.04+git20210103-1.debian.tar.xz
 e61a6d01cc94f6b03260a1c1a09f2f78 8092 text optional 
xpdf_3.04+git20210103-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEMLI8i05qOwnqprZSEpc7bnLcB7UFAmAScC8ACgkQEpc7bnLc
B7UsmBAAlXvbdIpZNFC4+ul+d2U8NvxmKburY+iS7pG0OzUSmfXjsGeiXDSuVlBk
wMI4pWlGFfLE86/nJKC0Ik7anG23GmBHdPrUeowyxFpEHPyoP23IBgu4xX7Jry4t
R7mSAV96vE62HKOabjas65oaKTEp8y1iXiJaqa0HB5YUvZUahtChGjQvvTry3mop
fa0EIF5BHYr7f0iNcHJy7GJwI6fZVVctHoqLCvKRU1eNj4jsUU2Ab/ddVff7OZfj
1R7vjEJz3MxhTwFCeYjY54rPwHOt2mS0l7/+FmAF531//sY1w9n9SFiIapu6fwYA

Bug#968354: marked as done (xpdf crash with empty document)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 08:19:59 +
with message-id 
and subject line Bug#968354: fixed in xpdf 3.04+git20210103-1
has caused the Debian Bug report #968354,
regarding xpdf crash with empty document
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.)


-- 
968354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xpdf
Version: 3.04-13
Severity: normal
Tag: security

On Debian Bullseye this crashes xpdf with coredump:

touch x.pdf; xpdf x.pdf

Funny, after a 2-byte Virtualbox (and now qemu) crash, this is 
the shortest input for a DoS-bug I have seen so far :-)

For xpdf this bug itself is not really a security risk: an attacker
could also send a white page document or no document at all if
he wants the victim not to see a document. Still someone familiar
with the code should look at it, maybe some half-broken document
could turn the NULL-dereference into something more useful.

rax0x0 0

   0x5556e6d0 <+16>:je 0x5556e6e0 

   0x5556e6d2 <+18>:mov%ebp,%eax
   0x5556e6d4 <+20>:pop%rbx
   0x5556e6d5 <+21>:pop%rbp
   0x5556e6d6 <+22>:pop%r12
   0x5556e6d8 <+24>:retq   
   0x5556e6d9 <+25>:nopl   0x0(%rax)
   0x5556e6e0 <+32>:mov0x8(%rbx),%rax
=> 0x5556e6e4 <+36>:mov(%rax),%rax   (doc is null)
   0x5556e6e7 <+39>:mov(%rax),%rdi 
   0x5556e6ea <+42>:callq  0x5557d730 


Relevant source:

int XPDFCore::loadFile(const GString *fileName, GString *ownerPassword,
   GString *userPassword) {
  int err;

  err = PDFCore::loadFile(fileName, ownerPassword, userPassword);
  if (err == errNone) {
// save the modification time
modTime = getModTime(doc->getFileName()->getCString());

// update the parent window
if (updateCbk) {
  (*updateCbk)(updateCbkData, doc->getFileName(), -1,
   doc->getNumPages(), NULL);
}
  }
  return err;
}

(gdb) print doc
$1 = (PDFDoc *) 0x0

If understand correctly, "PDFCore::loadFile" does not return
an error when processing an empty file, but also does not set
static variable "doc". This seems to be due to "xpdf/PDFCore.cc":

int PDFCore::loadFile2(PDFDoc *newDoc) {
  int err;
  double w, h, t;
  int i;

  // open the PDF file
  if (!newDoc->isOk()) {
err = newDoc->getErrorCode();
delete newDoc;
return err;
  }

...

The PDFDoc seems to come from "libpoppler.so.82" already and
detects the problem:

Syntax Error: Document stream is empty

On a quick glance I could not see this may result in !isOk()
but also "err" not set correctly. If error should be in libpoppler,
then this is the relevant version:

ii  libpoppler82:amd64   0.71.0-6
amd64PDF rendering library
--- End Message ---
--- Begin Message ---
Source: xpdf
Source-Version: 3.04+git20210103-1
Done: Florian Schlichting 

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

Debian distribution maintenance software
pp.
Florian Schlichting  (supplier of updated xpdf 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, 28 Jan 2021 15:58:32 +0800
Source: xpdf
Architecture: source
Version: 3.04+git20210103-1
Distribution: unstable
Urgency: medium
Maintainer: Florian Schlichting 
Changed-By: Florian Schlichting 
Closes: 606885 848631 863382 942086 945188 968354 971805 977182
Changes:
 xpdf (3.04+git20210103-1) unstable; urgency=medium
 .
   * Import new upstream version 3.04+git20210103
 + switch to xpopple as new upstream (closes: #977182)
 + fix obvious memory leaks (closes: #945188, #942086)
 + no longer crash on empty documents (closes: #968354)
 + properly ask for passwords (closes: #606885)
 + correctly recognize working and document obsolete config file commands
   (closes: #971805, #863382)
   * Drop patches, all applied in (or obsoleted 

Bug#945188: marked as done (xpdf: memory leak when changing page)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 08:19:59 +
with message-id 
and subject line Bug#945188: fixed in xpdf 3.04+git20210103-1
has caused the Debian Bug report #945188,
regarding xpdf: memory leak when changing page
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.)


-- 
945188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xpdf
Version: 3.04-13
Severity: important

When one changes the displayed page (e.g. with PageDown or PageUp),
xpdf takes more memory, even if the page has already been displayed
(thus this is not due to caching).

For instance, consider /usr/share/pari/doc/users.pdf from pari-doc.
It starts with 32 MB. And each time I do a PageDown or PageUp, it
takes an additional 16 MB.

One can easily end up filling the memory of the machine. This happened
to me several times, with my machine completely freezing for several
minutes, until I found out that xpdf was the main cause.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xpdf depends on:
ii  libc6 2.29-3
ii  libgcc1   1:9.2.1-19
ii  libpaper1 1.1.28+b1
ii  libpoppler82  0.71.0-6
ii  libstdc++69.2.1-19
ii  libx11-6  2:1.6.8-1
ii  libxm42.3.8-2
ii  libxt61:1.1.5-1+b3

Versions of packages xpdf recommends:
ii  cups-bsd2.3.0-7
ii  gsfonts-x11 0.27
ii  poppler-data0.4.9-2
ii  poppler-utils   0.71.0-6
ii  sensible-utils  0.0.12

xpdf suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: xpdf
Source-Version: 3.04+git20210103-1
Done: Florian Schlichting 

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

Debian distribution maintenance software
pp.
Florian Schlichting  (supplier of updated xpdf 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, 28 Jan 2021 15:58:32 +0800
Source: xpdf
Architecture: source
Version: 3.04+git20210103-1
Distribution: unstable
Urgency: medium
Maintainer: Florian Schlichting 
Changed-By: Florian Schlichting 
Closes: 606885 848631 863382 942086 945188 968354 971805 977182
Changes:
 xpdf (3.04+git20210103-1) unstable; urgency=medium
 .
   * Import new upstream version 3.04+git20210103
 + switch to xpopple as new upstream (closes: #977182)
 + fix obvious memory leaks (closes: #945188, #942086)
 + no longer crash on empty documents (closes: #968354)
 + properly ask for passwords (closes: #606885)
 + correctly recognize working and document obsolete config file commands
   (closes: #971805, #863382)
   * Drop patches, all applied in (or obsoleted by) xpopple upstream
   * Bump dh compat to level 13
   * Greatly simplify d/rules (but keep linking to libpaper)
   * Keep installing our xpdf wrapper script
   * Ensure wrapper script correctly handles all xpdf options
   * Add wrapper script options back to xpdf manpage
   * Drop obsolete language support files and infrastructure
   * Mention new upstream in relevant places, drop d/watch
   * Adopt xpdf (closes: #848631)
   * Ship TODO in docs
   * Add Rules-Requires-Root: no
   * Declare compliance with Debian Policy 4.5.1
Checksums-Sha1:
 40e2a06d4197afe5c59194743175ed5cb76bce55 1954 xpdf_3.04+git20210103-1.dsc
 c49eefa7d8a2359fa6f75d97753547340fe1158a 123005 
xpdf_3.04+git20210103.orig.tar.gz
 4b83474cdabc693f1bdf1f7c1c778c0446157781 23668 

Bug#942086: marked as done (xpdf: Memory leak on large document (even w/ continuousView turned off))

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 08:19:59 +
with message-id 
and subject line Bug#942086: fixed in xpdf 3.04+git20210103-1
has caused the Debian Bug report #942086,
regarding xpdf: Memory leak on large document (even w/ continuousView turned 
off)
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.)


-- 
942086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xpdf
Version: 3.04-13
Severity: important

I have a PDF document which seems to cause xpdf to leak memory as I
advance through its pages.  The severity of the leak seems to scale
with the window size of xpdf, at least to some extent.

I don't think this is the same bug as #926501, because I experience
this with continuousView turned off.  I checked /etc/xpdf/xpdfrc and
~/.xpdfrc and didn't find continuousView listed in either file.  I
verified that it seems to be disabled for me (to ensure it's not
enabled by default) by checking the scrollbar: the scrollbar
represents only the current page.

In a 1276x2113 pixel window, xpdf starts by using 43752 KiB RSS while
displaying the first page.  If I advance through all pages of this
document until I get to the end, RSS climbs to 2052816 KiB (2.0 GiB).

In a 3840x2117 pixel window, xpdf starts on the same document using
55936 KiB RSS.  After advancing to the end, it finishes using 3309660
KiB (3.2 GiB) RSS.

I prefer xpdf because it's responsive and, until now, been very
lightweight in my experience.  However, this bug led me to compare
xpdf's memory utilization performance to that of evince.  On the same
document, in a 3840x2117 pixel window, evince version 3.30.2-3 starts
at 147144 KiB RSS.  After advancing to the end (and allowing enough
time for each page to render as I do so), evince finishes at 215876
KiB (211 MiB) RSS.

I configured both xpdf and evince to scale each page to fit the
window.

The document I'm experiencing this is with
https://www.andersonpower.com/content/dam/app/ecommerce/product-pdfs/CAT-PPMP.pdf
.  The version currently published there has these attributes:

  Size: 13529602 B (12.9 MiB)
  SHA256: 64079ffb140cca6c8747e9b0c9d88864098093b49e34a0e35399282467b09d73
  HTTP Last-Modified: Tue, 10 Sep 2019 15:46:50 GMT
  PDF ModDate: Tue Sep  4 12:29:21 2018 PDT
  Page count: 124

I've made sure that this version of the document is available at the
Internet Archive Wayback Machine at this URL:
https://web.archive.org/web/20191010060834/https://www.andersonpower.com/content/dam/app/ecommerce/product-pdfs/CAT-PPMP.pdf

I chose severity "important" because this is bad enough for me to stop
using xpdf until the bug can be addressed.  I lost 20 minutes to my
system thrashing in swap (with xpdf alongside other big RAM users
too).

Thanks,
-Jean-Paul

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

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

Versions of packages xpdf depends on:
ii  libc6 2.28-10
ii  libgcc1   1:8.3.0-6
ii  libpaper1 1.1.28
ii  libpoppler82  0.71.0-5
ii  libstdc++68.3.0-6
ii  libx11-6  2:1.6.7-1
ii  libxm42.3.8-2
ii  libxt61:1.1.5-1+b3

Versions of packages xpdf recommends:
ii  cups-bsd2.2.10-6+deb10u1
ii  gsfonts-x11 0.26
ii  poppler-data0.4.9-2
ii  poppler-utils   0.71.0-5
ii  sensible-utils  0.0.12

xpdf suggests no packages.

-- no debconf information

-- 
J.P. Larocque 
--- End Message ---
--- Begin Message ---
Source: xpdf
Source-Version: 3.04+git20210103-1
Done: Florian Schlichting 

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

Debian distribution maintenance software
pp.
Florian Schlichting  (supplier of updated xpdf 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)

Bug#863382: marked as done (xpdf: Config Error: Unknown config file command 'errQuiet')

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 08:19:59 +
with message-id 
and subject line Bug#863382: fixed in xpdf 3.04+git20210103-1
has caused the Debian Bug report #863382,
regarding xpdf: Config Error: Unknown config file command 'errQuiet'
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.)


-- 
863382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xpdf
Version: 3.04-4
Severity: normal

Starting xpdf from a command line throws the error "Config Error: Unknown 
config file command 'errQuiet' (/home/user/.xpdfrc:3) 
According to the xpdfrc manpage, if errQuiet is set to yes it should suppress 
all warning and error messages.  The .xpdfrc file contains:

include /etc/xpdf/xpdfrc
urlCommand  "firefox-esr -new-tab '%s'"
errQuietyes

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

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xpdf depends on:
ii  libc6 2.24-10
ii  libgcc1   1:6.3.0-18
ii  libpoppler64  0.48.0-2
ii  libstdc++66.3.0-18
ii  libx11-6  2:1.6.4-3
ii  libxm42.3.4-13
ii  libxt61:1.1.5-1

Versions of packages xpdf recommends:
ii  cups-bsd   2.2.1-8
ii  gsfonts-x110.24
ii  poppler-data   0.4.7-8
ii  poppler-utils  0.48.0-2

xpdf suggests no packages.

-- Configuration Files:
/etc/xpdf/xpdfrc changed:
psFile  "|lpr"
urlCommand  "sensible-browser '%s'"
unbind down any
unbind right any
unbind up any
unbind left any
bind down window scrollDown(16) 
bind right window scrollRight(16)
bind up window scrollUp(16)
bind left window scrollLeft(16)
bind down fullScreen nextPage
bind right fullScreen nextPage
bind up fullScreen prevPage
bind left fullScreen prevPage


-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xpdf
Source-Version: 3.04+git20210103-1
Done: Florian Schlichting 

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

Debian distribution maintenance software
pp.
Florian Schlichting  (supplier of updated xpdf 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, 28 Jan 2021 15:58:32 +0800
Source: xpdf
Architecture: source
Version: 3.04+git20210103-1
Distribution: unstable
Urgency: medium
Maintainer: Florian Schlichting 
Changed-By: Florian Schlichting 
Closes: 606885 848631 863382 942086 945188 968354 971805 977182
Changes:
 xpdf (3.04+git20210103-1) unstable; urgency=medium
 .
   * Import new upstream version 3.04+git20210103
 + switch to xpopple as new upstream (closes: #977182)
 + fix obvious memory leaks (closes: #945188, #942086)
 + no longer crash on empty documents (closes: #968354)
 + properly ask for passwords (closes: #606885)
 + correctly recognize working and document obsolete config file commands
   (closes: #971805, #863382)
   * Drop patches, all applied in (or obsoleted by) xpopple upstream
   * Bump dh compat to level 13
   * Greatly simplify d/rules (but keep linking to libpaper)
   * Keep installing our xpdf wrapper script
   * Ensure wrapper script correctly handles all xpdf options
   * Add wrapper script options back to xpdf manpage
   * Drop obsolete language support files and infrastructure
   * Mention new upstream in relevant places, drop d/watch
   * Adopt xpdf (closes: #848631)
   * Ship TODO in docs
   * Add Rules-Requires-Root: no
   * Declare compliance with Debian Policy 4.5.1
Checksums-Sha1:
 40e2a06d4197afe5c59194743175ed5cb76bce55 1954 xpdf_3.04+git20210103-1.dsc
 c49eefa7d8a2359fa6f75d97753547340fe1158a 123005 
xpdf_3.04+git20210103.orig.tar.gz
 4b83474cdabc693f1bdf1f7c1c778c0446157781 23668 
xpdf_3.04+git20210103-1.debian.tar.xz
 9cad89f4b3518e7f8d6e58980da150431e24b8e0 8092 
xpdf_3.04+git20210103-1_amd64.buildinfo
Checksums-Sha256:
 

Bug#848631: marked as done (ITA: xpdf -- Portable Document Format (PDF) reader)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 08:19:59 +
with message-id 
and subject line Bug#848631: fixed in xpdf 3.04+git20210103-1
has caused the Debian Bug report #848631,
regarding ITA: xpdf -- Portable Document Format (PDF) reader
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.)


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

I don't have as much interest in xpdf as I used to, so I'm giving it
up to the next loving home.  I'll still try to help out if I find
myself with free time and motivation, or if there are hard problems.

Best wishes,
Mike
--- End Message ---
--- Begin Message ---
Source: xpdf
Source-Version: 3.04+git20210103-1
Done: Florian Schlichting 

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

Debian distribution maintenance software
pp.
Florian Schlichting  (supplier of updated xpdf 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, 28 Jan 2021 15:58:32 +0800
Source: xpdf
Architecture: source
Version: 3.04+git20210103-1
Distribution: unstable
Urgency: medium
Maintainer: Florian Schlichting 
Changed-By: Florian Schlichting 
Closes: 606885 848631 863382 942086 945188 968354 971805 977182
Changes:
 xpdf (3.04+git20210103-1) unstable; urgency=medium
 .
   * Import new upstream version 3.04+git20210103
 + switch to xpopple as new upstream (closes: #977182)
 + fix obvious memory leaks (closes: #945188, #942086)
 + no longer crash on empty documents (closes: #968354)
 + properly ask for passwords (closes: #606885)
 + correctly recognize working and document obsolete config file commands
   (closes: #971805, #863382)
   * Drop patches, all applied in (or obsoleted by) xpopple upstream
   * Bump dh compat to level 13
   * Greatly simplify d/rules (but keep linking to libpaper)
   * Keep installing our xpdf wrapper script
   * Ensure wrapper script correctly handles all xpdf options
   * Add wrapper script options back to xpdf manpage
   * Drop obsolete language support files and infrastructure
   * Mention new upstream in relevant places, drop d/watch
   * Adopt xpdf (closes: #848631)
   * Ship TODO in docs
   * Add Rules-Requires-Root: no
   * Declare compliance with Debian Policy 4.5.1
Checksums-Sha1:
 40e2a06d4197afe5c59194743175ed5cb76bce55 1954 xpdf_3.04+git20210103-1.dsc
 c49eefa7d8a2359fa6f75d97753547340fe1158a 123005 
xpdf_3.04+git20210103.orig.tar.gz
 4b83474cdabc693f1bdf1f7c1c778c0446157781 23668 
xpdf_3.04+git20210103-1.debian.tar.xz
 9cad89f4b3518e7f8d6e58980da150431e24b8e0 8092 
xpdf_3.04+git20210103-1_amd64.buildinfo
Checksums-Sha256:
 3e47cdedacae84aee3ec1cbf3151698afe3a2ca83bd0aaa4611dbaf0487968e5 1954 
xpdf_3.04+git20210103-1.dsc
 8c00465f2e362377459ec6d82c0bfe2df9b80ddd98d602e08f41c988efa56fc0 123005 
xpdf_3.04+git20210103.orig.tar.gz
 6504e23ca0ce5e8a91b17973d6fc5e73aefe0ccadba73707a1de4721d2f2ecce 23668 
xpdf_3.04+git20210103-1.debian.tar.xz
 bfc3e2a91a4a4df46f6aca43efbafdbd6b91350dbb0928ab31fdab3059e503cc 8092 
xpdf_3.04+git20210103-1_amd64.buildinfo
Files:
 b38ab56c1cc5eeef1ece34a05a280648 1954 text optional xpdf_3.04+git20210103-1.dsc
 80eaa44277edac0f6de780f13e1bb350 123005 text optional 
xpdf_3.04+git20210103.orig.tar.gz
 0662269a02ad92d16e0d2fced32301e5 23668 text optional 
xpdf_3.04+git20210103-1.debian.tar.xz
 e61a6d01cc94f6b03260a1c1a09f2f78 8092 text optional 
xpdf_3.04+git20210103-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEMLI8i05qOwnqprZSEpc7bnLcB7UFAmAScC8ACgkQEpc7bnLc
B7UsmBAAlXvbdIpZNFC4+ul+d2U8NvxmKburY+iS7pG0OzUSmfXjsGeiXDSuVlBk
wMI4pWlGFfLE86/nJKC0Ik7anG23GmBHdPrUeowyxFpEHPyoP23IBgu4xX7Jry4t
R7mSAV96vE62HKOabjas65oaKTEp8y1iXiJaqa0HB5YUvZUahtChGjQvvTry3mop
fa0EIF5BHYr7f0iNcHJy7GJwI6fZVVctHoqLCvKRU1eNj4jsUU2Ab/ddVff7OZfj
1R7vjEJz3MxhTwFCeYjY54rPwHOt2mS0l7/+FmAF531//sY1w9n9SFiIapu6fwYA
oz45ahF4DjvF1nR9WnAwkgWhrJEhcYsYK20M6G2IvJzKPNsnLC3MB7d3dptB6xyH
1bTOs09wAz1ZMOS5+GNHot9+uX8dgnDSmQX2sZ2hcB9RMq1tf3WSlO/eWA+TgTEY

Bug#606885: marked as done (xpdf: no longer asks for password in dialog window)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2021 08:19:59 +
with message-id 
and subject line Bug#606885: fixed in xpdf 3.04+git20210103-1
has caused the Debian Bug report #606885,
regarding xpdf: no longer asks for password in dialog window
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.)


-- 
606885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xpdf
Version: 3.02-11
Severity: normal
Tags: security


Hi Debian xpdf maintainers!
Thanks a lot for maintaining my favorite PDF viewer!

I noticed a little regression (probably introduced during the
conversion into a libpoppler front-end).

In the past, xpdf used to pop up a useful dialog window to ask
the user for a password, when dealing with password-protected PDF
files. After typing the password in, the user was able to view
the contents of the password-protected PDF file.

Nowadays, when the user attempts to view a password-protected PDF
file, no dialog window is shown and xpdf exits immediately with
the following error:

  $ xpdf protected_file.pdf
  Error: Incorrect password
  $ echo $?
  1

On the other hand, if the user provides the correct password
through the command-line option:

  $ xpdf -upw my_secret_password protected_file.pdf

everything works fine and the file contents are correctly visualized.

Of course, requiring the user to provide a password on the command
line is not a good idea, from a security point of view: the password
(in clear) is visible to anyone who takes a look at the screen, it's 
saved in the shell history, and so forth.

As a consequence, I miss the old "insert password" dialog window!
Could this feature be restored, please?

Thanks for your time!


N.B.:
Before filing this bug report, I took a look at the already filed ones
and noticed bug #601375. I thought it could be the same issue, but it
probably isn't, since the file mentioned in that bug report gives me
a different error message:

  $ xpdf HTUSA-EBU4-3.pdf 
  Error: Weird encryption info
  Error: Incorrect password



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

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xpdf depends on:
ii  lesstif2  1:0.95.2-1 OSF/Motif 2.1 implementation relea
ii  libc6 2.11.2-7   Embedded GNU C Library: Shared lib
ii  libgcc1   1:4.4.5-8  GCC support library
ii  libpoppler5   0.12.4-1.2 PDF rendering library
ii  libstdc++64.4.5-8The GNU Standard C++ Library v3
ii  libx11-6  2:1.3.3-4  X11 client-side library
ii  libxt61:1.0.7-1  X11 toolkit intrinsics library

Versions of packages xpdf recommends:
ii  gsfonts-x11   0.21   Make Ghostscript fonts available t
ii  poppler-data  0.4.3-1Encoding data for the poppler PDF 
ii  poppler-utils 0.12.4-1.2 PDF utilitites (based on libpopple

xpdf suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: xpdf
Source-Version: 3.04+git20210103-1
Done: Florian Schlichting 

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

Debian distribution maintenance software
pp.
Florian Schlichting  (supplier of updated xpdf 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, 28 Jan 2021 15:58:32 +0800
Source: xpdf
Architecture: source
Version: 3.04+git20210103-1
Distribution: unstable
Urgency: medium
Maintainer: Florian Schlichting 
Changed-By: Florian Schlichting 
Closes: 606885 848631 863382 942086 945188 968354 971805 977182
Changes:
 xpdf (3.04+git20210103-1) unstable; urgency=medium
 .
   * Import new upstream version 3.04+git20210103
 + switch to xpopple as new upstream (closes: #977182)