Processed: RM: libepsilon -- ROM; Dead upstream, no longer used by gdal

2021-09-10 Thread Debian Bug Tracking System
Processing control commands:

> block -1 by 992527
Bug #994073 [ftp.debian.org] RM: libepsilon -- ROM; Dead upstream, no longer 
used by gdal
994073 was not blocked by any bugs.
994073 was not blocking any bugs.
Added blocking bug(s) of 994073: 992527

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



Bug#994062: Acknowledgement (gnome-shell-extension-tilix-dropdown: No JS module 'tweener' found in search path)

2021-09-10 Thread Ted To
After updating extension.js along the lines of
https://askubuntu.com/questions/1286212/no-js-module-tweener-found-in-search-path-gnome-shell-extension-error-on-ubun,
there is still an error with a "No property x_fill on StBin" error.



Bug#994062: gnome-shell-extension-tilix-dropdown: No JS module 'tweener' found in search path

2021-09-10 Thread Ted To
Package: gnome-shell-extension-tilix-dropdown
Version: 7-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
installed gnome-shell-extension-tilix-dropdown
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
attempted to enable extension
   * What was the outcome of this action?
extension not enabled with the error given in the subject line.
   * What outcome did you expect instead?
extension enabled

*** End of the template - remove these template lines ***


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

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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 gnome-shell-extension-tilix-dropdown depends on:
ii  gnome-shell  3.38.4-1
ii  tilix1.9.4-2

gnome-shell-extension-tilix-dropdown recommends no packages.

gnome-shell-extension-tilix-dropdown suggests no packages.

-- no debconf information



Bug#989305: marked as done (python3-djangorestframework-spectacular: Does not work, attempt to import unvailable dj_rest_auth module)

2021-09-10 Thread Debian Bug Tracking System
Your message dated Fri, 10 Sep 2021 22:18:37 +
with message-id 
and subject line Bug#989305: fixed in python-drf-spectacular 0.18.2-1
has caused the Debian Bug report #989305,
regarding python3-djangorestframework-spectacular: Does not work, attempt to 
import unvailable dj_rest_auth module
to be marked as done.

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

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


-- 
989305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-djangorestframework-spectacular
Version: 0.13.1-1
Severity: grave
Tags: patch
Justification: renders package unusable

Hello,

This package does not work at all, it attemps to import unavailable
dj_rest_auth module at runtime and this module is supposed to be an optional
dependency (which is not available in Debian archive).

I had a talk with upstream on Github:
https://github.com/tfranzel/drf-spectacular/issues/411

And it turned out upstream did some work to render optional modules really
optional in recent versions.

The import bug can actually be seen while building the package from a clean
chroot, Sphinx doc is not getting generated correctly (but does not crash build
for some reason):

WARNING: autodoc: failed to import module 'openapi' from module
'drf_spectacular'; the following exception was raised:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sphinx/ext/autodoc/importer.py", line
67, in import_module
return importlib.import_module(modname)
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1030, in _gcd_import
  File "", line 1007, in _find_and_load
  File "", line 986, in _find_and_load_unlocked
  File "", line 680, in _load_unlocked
  File "", line 790, in exec_module
  File "", line 228, in _call_with_frames_removed
  File "/tmp/python-drf-spectacular-0.13.1/drf_spectacular/openapi.py", line
21, in 
from drf_spectacular.contrib import *  # noqa: F403, F401
  File "/tmp/python-drf-
spectacular-0.13.1/drf_spectacular/contrib/rest_auth.py", line 3, in 
pytest.importorskip("dj_rest_auth")
  File "/usr/lib/python3/dist-packages/_pytest/outcomes.py", line 212, in
importorskip
raise Skipped(reason, allow_module_level=True) from None
Skipped: could not import 'dj_rest_auth': No module named 'dj_rest_auth'

My django application crashes with the same error message, it cannot start.

I updated the package on SALSA to latest upstream version:
https://salsa.debian.org/python-team/packages/python-drf-spectacular

And this one is building fine, unittests run successfully and my Django app is
working again.

I'm not sure if it's too late to be included in Debian 11, but imho, it's
better not to have it than having it in current state.

Best regards, Adam.

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

Kernel: Linux 5.10.0-6-amd64 (SMP w/32 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: python-drf-spectacular
Source-Version: 0.18.2-1
Done: Michael Fladischer 

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

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated 
python-drf-spectacular package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Sep 2021 21:54:42 +
Source: python-drf-spectacular
Architecture: source
Version: 0.18.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Michael Fladischer 
Closes: 989305
Changes:
 python-drf-spectacular (0.18.2-1) unstable; urgency=medium
 .
   [ Adam Cecile ]
   * New upstream release (Closes: #989305).
 .
   [ Michael Fladischer ]
  

Bug#993090: marked as done (mplayer FTBFS: error: 'AVStream' has no member named 'info')

2021-09-10 Thread Debian Bug Tracking System
Your message dated Fri, 10 Sep 2021 22:05:53 +
with message-id 
and subject line Bug#993090: fixed in mplayer 2:1.4+ds1-2
has caused the Debian Bug report #993090,
regarding mplayer FTBFS: error: 'AVStream' has no member named 'info'
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.)


-- 
993090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mplayer
Version: 2:1.4+ds1-1
Severity: serious
Tags: ftbfs bookworm sid

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

...
libmpcodecs/ad_spdif.c:303:43: error: 'AVStream' has no member named 'info'
  303 | av_freep(&lavf_ctx->streams[0]->info);
  |   ^~
make[2]: *** [Makefile:726: libmpcodecs/ad_spdif.o] Error 1
--- End Message ---
--- Begin Message ---
Source: mplayer
Source-Version: 2:1.4+ds1-2
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated mplayer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 09 Sep 2021 23:07:45 +0200
Source: mplayer
Architecture: source
Version: 2:1.4+ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Closes: 958879 993090 994002
Changes:
 mplayer (2:1.4+ds1-2) unstable; urgency=medium
 .
   * Team upload
   * debian/control:
 - Fix Homepage (Closes: #958879)
 - Bump Standards-Version
   * debian/patches: Apply upstream patch to fix build with ffmpeg 4.4 (Closes:
 #994002, #993090)
Checksums-Sha1:
 6c990a6a3adee27a6df4808fe3f92fae9e5aed08 3233 mplayer_1.4+ds1-2.dsc
 3d166857dcd08072ef2c12c0b9ae0816358e0157 32880 mplayer_1.4+ds1-2.debian.tar.xz
Checksums-Sha256:
 75904f1101774a3400f9eedda6302085051709da6ffc195711b028fe4cb0cff8 3233 
mplayer_1.4+ds1-2.dsc
 e4ce407ead5c31b676a4c5d058d4c68fb558a51d1c00d1c0a6d225cd2713ae05 32880 
mplayer_1.4+ds1-2.debian.tar.xz
Files:
 9ff3c4e277881dc5edf699a33318b5ea 3233 video optional mplayer_1.4+ds1-2.dsc
 f670ff09c3f52affc27aa57393481034 32880 video optional 
mplayer_1.4+ds1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmE6eUgACgkQafL8UW6n
GZPTaA//TGOQ4a/mJnIss4qfftCYzqhyU8sojAEGyaCJqynBaZfk2owmX7mvOOwi
YGMkcj2zlUxt2mZ3jMNZUfz42a27m13dKg0lU2vyx9kEyRAzBBNqpazVECMXJjHX
fAQYohW/uCiKVIufOI/yKjMM0H+hdBj+OKm464Z5G3mi0m5dtF+158hW1p2AxDsW
4CtPq1H3CP2vlVJXIaccr/qTORHAOlX3wSF9oOvgGCRdEYzSfRjEaPbcO+T0ftPC
C4Izz1CfAUVCwWO/Ua7KcXaq28/Qfj9lfGiCGoxqfqnJXB+HbupVp+ftwIim62Op
t8KeU5gbkrWd8kdRTJF751qDYwQUDin6nR5k3aSFTFaT53FwKlkQuzBGJ0oIpj/U
ZkYDiXDHgclq9nCmTrcf3TsZGTYWxZcPq8nrYMHtiJZonWwyP183ukLUpDXjC6NM
G4aOfM5WIkXU/CY8H1llv7Xzmer3vvX2Yz9ezZE/ECjyAGaDuOu2YnXsxzLFzbOi
qw2ZqyorRD1gD6P3xu8A36DWaldwL+0+xWLZCdOwWRDVQ1+8wPIarYLyEFJBSaPm
c3vzC0CtmUfM7yh47VP2EmQngwZySpbpqeyoGl1+c1QTBzk7I7IjGSA0j3c3yj7S
EVdkQVa4UG5EBFpjjWuZ83LNA+RqhHzFP52iPu4361F50wL1QLY=
=Ogle
-END PGP SIGNATURE End Message ---


Bug#994033: marked as done (mpd: Fails to find ldd libraries from libraspberrypi0 that have moved)

2021-09-10 Thread Debian Bug Tracking System
Your message dated Fri, 10 Sep 2021 22:37:38 +0200
with message-id 
and subject line Re: Bug#994033: mpd: Fails to find ldd libraries from 
libraspberrypi0 that have moved
has caused the Debian Bug report #994033,
regarding mpd: Fails to find ldd libraries from libraspberrypi0 that have moved
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.)


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

Dear Maintainer,
AN upgrade to rasbian stable ahs moved some ldd files included in the 
libraspberrypi0 packages and now mpd fails to start.

OK# ldd /usr/bin/mpd | grep -w not | cat
libvchiq_arm.so => not found
libvcos.so => not found
libmmal_core.so => not found
libmmal_util.so => not found
libmmal_vc_client.so => not found
libbcm_host.so => not found
libvcsm.so => not found


-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 11 (bullseye)
Release:11
Codename:   bullseye
Architecture: armv6l

Kernel: Linux 5.10.60+
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mpd depends on:
ii  adduser   3.118
ii  init-system-helpers   1.60
ii  libadplug-2.3.3-0 2.3.3+dfsg-2
ii  libao41.2.2+20180113-1.1
ii  libasound21.2.4-1.1+rpt1
ii  libaudiofile1 0.3.6-5
ii  libavahi-client3  0.8-5
ii  libavahi-common3  0.8-5
ii  libavcodec58  7:4.3.2-0+rpt1+deb11u2
ii  libavformat58 7:4.3.2-0+rpt1+deb11u2
ii  libavutil56   7:4.3.2-0+rpt1+deb11u2
ii  libbz2-1.01.0.8-4
ii  libc6 2.31-13+rpt2+rpi1
ii  libcdio-cdda2 10.2+2.0.0-1+b1
ii  libcdio-paranoia2 10.2+2.0.0-1+b1
ii  libcdio19 2.1.0-2
ii  libchromaprint1   1.5.0-2
ii  libcurl3-gnutls   7.74.0-1.3
ii  libdbus-1-3   1.12.20-2
ii  libexpat1 2.2.10-2
ii  libfaad2  2.10.0-1
ii  libflac8  1.3.3-2
ii  libfluidsynth22.1.7-1.1
ii  libgcc-s1 10.2.1-6+rpi1
ii  libgme0   0.6.3-2
ii  libicu67  67.1-7
ii  libid3tag00.15.1b-14
ii  libiso9660-11 2.1.0-2
ii  libixml10 1:1.8.4-2
ii  libjack-jackd2-0 [libjack-0.125]  1.9.17~dfsg-1
ii  libjs-sphinxdoc   3.4.3-2
ii  libmad0   0.15.1b-10
ii  libmikmod33.3.11.1-6
ii  libmms0   0.6.4-3
ii  libmodplug1   1:0.8.9.0-3
ii  libmp3lame0   3.100-3
ii  libmpcdec62:0.1~r495-2
ii  libmpdclient2 2.19-1
ii  libmpg123-0   1.26.4-1
ii  libnfs13  4.0.0-1
ii  libogg0   1.3.4-0.1
ii  libopenal11:1.19.1-2
ii  libopus0  1.3.1-0.1
ii  libpcre3  2:8.39-13
ii  libpulse0 14.2-2+rpi1
ii  libsamplerate00.2.1+ds0-1
ii  libshout3 2.4.5-1
ii  libsidplayfp5 2.0.5-2
ii  libsmbclient  2:4.13.5+dfsg-2
ii  libsndfile1   1.0.31-2
ii  libsndio7.0   1.5.0-3
ii  libsoxr0  0.1.3-4+rpi1
ii  libsqlite3-0  3.34.1-3
ii  libstdc++610.2.1-6+rpi1
ii  libsystemd0   247.3-6+rpi1
ii  libupnp13 1:1.8.4-2
ii  liburing1 0.7-3
ii  libvorbis0a   1.3.7-1
ii  libvorbisenc2 1.3.7-1
ii  libwavpack1   5.4.0-1
ii  libwildmidi2  0.4.3-1
ii  libyajl2  2.1.0-3
ii  libzzip-0-13  0.13.62-3.3
ii  lsb-base  11.1.0+rpi1
ii  zlib1g1:1.2.11.dfsg-2

mpd recommends no packages.

Processed: src:ensmallen: fails to migrate to testing for too long: autopkgtest failure

2021-09-10 Thread Debian Bug Tracking System
Processing control commands:

> close -1 2.17.0-2
Bug #994063 [src:ensmallen] src:ensmallen: fails to migrate to testing for too 
long: autopkgtest failure
Marked as fixed in versions ensmallen/2.17.0-2.
Bug #994063 [src:ensmallen] src:ensmallen: fails to migrate to testing for too 
long: autopkgtest failure
Marked Bug as done
> block -1 by 993043
Bug #994063 {Done: Paul Gevers } [src:ensmallen] 
src:ensmallen: fails to migrate to testing for too long: autopkgtest failure
994063 was not blocked by any bugs.
994063 was not blocking any bugs.
Added blocking bug(s) of 994063: 993043

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



Bug#994063: src:ensmallen: fails to migrate to testing for too long: autopkgtest failure

2021-09-10 Thread Paul Gevers
Source: ensmallen
Version: 2.16.2-2
Severity: serious
Control: close -1 2.17.0-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 993043

Dear maintainer(s),

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

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

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

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

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

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature


Bug#994057: libegl-mesa0: 21.2.1-2 with intel graphic card produces artifact on firefox-esr

2021-09-10 Thread Sylvain Tgz
Package: libegl-mesa0
Version: 21.2.1-2
Severity: serious
Justification: unknow
X-Debbugs-Cc: tarjaiz...@gmail.com

Dear Maintainer,

After upgraded libegl-mesa0 libgbm1 libgl1-mesa-dri libglapi-mesa libglx-mesa0 
libllvm11 to 21.2.1-2, I have artifacts with firefox-esr. For example, with 
right click on a tab, I can see artifact. 
For the moment, I have not seen any problem with other software.

If I downgrade to 20.3.5-1, the problem is no longer present.

I use Intel graphic card (UHD Graphics 630), lightdm and i3.
On another system, nvidia card is used, 21.2.1-2 has no problems. (lightdm and 
i3 are also used)

I think it is related to mesa but I am not sure.
Am I the only one in this case?

Thanks

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation CoffeeLake-H GT2 
[UHD Graphics 630] [8086:3e9b] (rev 02)

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
-
total 0

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 5.10.0-8-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP 
Debian 5.10.46-4 (2021-08-03)

DRM Information from dmesg:
---


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

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

Versions of packages libegl-mesa0 depends on:
ii  libc6   2.32-2
ii  libdrm2 2.4.107-2
ii  libexpat1   2.4.1-2
ii  libgbm1 21.2.1-2
ii  libgcc-s1   11.2.0-5
ii  libglapi-mesa   21.2.1-2
ii  libwayland-client0  1.19.0-2
ii  libwayland-server0  1.19.0-2
ii  libx11-xcb1 2:1.7.2-1
ii  libxcb-dri2-0   1.14-3
ii  libxcb-dri3-0   1.14-3
ii  libxcb-present0 1.14-3
ii  libxcb-sync11.14-3
ii  libxcb-xfixes0  1.14-3
ii  libxcb1 1.14-3
ii  libxshmfence1   1.3-1

libegl-mesa0 recommends no packages.

libegl-mesa0 suggests no packages.

Versions of packages xserver-xorg depends on:
ii  x11-xkb-utils   7.7+5
ii  xkb-data2.33-1
ii  xorgxrdp [xorg-driver-video]1:0.2.15-1
ii  xserver-xorg-core   2:1.20.11-1
ii  xserver-xorg-input-all  1:7.7+23
ii  xserver-xorg-input-libinput [xorg-driver-input  1.1.0-1
ii  xserver-xorg-input-wacom [xorg-driver-input]0.34.99.1-1+b1
ii  xserver-xorg-video-all  1:7.7+23
ii  xserver-xorg-video-amdgpu [xorg-driver-video]   19.1.0-2
ii  xserver-xorg-video-ati [xorg-driver-video]  1:19.1.0-2
ii  xserver-xorg-video-fbdev [xorg-driver-video]1:0.5.0-1
ii  xserver-xorg-video-intel [xorg-driver-video]2:2.99.917+git20200714-1+b1
ii  xserver-xorg-video-nouveau [xorg-driver-video]  1:1.0.17-1
ii  xserver-xorg-video-qxl [xorg-driver-video]  0.1.5+git20200331-1
ii  xserver-xorg-video-radeon [xorg-driver-video]   1:19.1.0-2
ii  xserver-xorg-video-vesa [xorg-driver-video] 1:2.5.0-1
ii  xserver-xorg-video-vmware [xorg-driver-video]   1:13.3.0-3

Versions of packages xserver-xorg recommends:
ii  libgl1-mesa-dri  21.2.1-2
ii  xserver-xorg-legacy  2:1.20.11-1

Versions of packages xserver-xorg-core depends on:
ii  keyboard-configuration  1.205
ii  libaudit1   1:3.0.5-1
ii  libbsd0 0.11.3-1
ii  libc6   2.32-2
ii  libdbus-1-3 1.12.20-2
ii  libdrm2 2.4.107-2
ii  libegl1 1.3.4-1
ii  libepoxy0   1.5.8-1
ii  libgbm1 21.2.1-2
ii  libgcrypt20 1.9.4-2
ii  libgl1  1.3.4-1
ii  libpciaccess0   0.16-1
ii  libpixman-1-0   0.40.0-1
ii  libselinux1 3.1-3
ii  libsystemd0 247.9-1
ii  libudev1247.9-1
ii  libunwind8  1.3.2-2
ii  libxau6 1:1.0.9-1
ii  libxdmcp6   1:1.1.2-3
ii  libxfont2   1:2.0.4-1
ii  libxshmfence1   1.3-1
ii  udev247.9-1
ii  xserver-common  2:1.20.11-1

Versions of packages xserver-xorg-core recommends:
ii  libgl1-mesa-dri  21.2.1-2
ii  libpam-systemd [logind]  247.9-1

Versions of packages xserver-xorg-core suggests:
ii  xfonts-100dpi1:1.0.4+nmu1.1
ii  xfonts-75dpi 1:1.0.4+nmu1.1
ii  xfonts-scalable  1:1.0.3-1.2



Bug#994055: cunit: FTBFS: format not a string literal and no format arguments [-Werror=format-security]

2021-09-10 Thread Sven Joachim
Source: cunit
Version: 2.1-3-dfsg-2.3
Severity: serious
Tags: ftbfs bookworm sid

Your package FTBFS with libncurses-dev 6.2+20210905-1, as several
mvwprintw() calls now trigger format warnings from gcc which
dpkg-buildflags turns into errors thanks to -Werror=format-security:

,
| Curses.c: In function 'show_suite_level_help':
| Curses.c:955:37: error: format not a string literal and no format arguments 
[-Werror=format-security]
|   955 |   mvwprintw(details_pad.pPad, 0, 0, szTemp);
|   | ^~
| Curses.c:959:37: error: format not a string literal and no format arguments 
[-Werror=format-security]
|   959 |   mvwprintw(details_pad.pPad, 2, 0, szTemp);
|   | ^~
| Curses.c: In function 'list_tests':
| Curses.c:1071:37: error: format not a string literal and no format arguments 
[-Werror=format-security]
|  1071 |   mvwprintw(details_pad.pPad, 0, 0, szTemp);
|   | ^~
| Curses.c:1078:37: error: format not a string literal and no format arguments 
[-Werror=format-security]
|  1078 |   mvwprintw(details_pad.pPad, 1, 0, szTemp);
|   | ^~
| Curses.c: In function 'curses_set_options_run':
| Curses.c:1161:39: error: format not a string literal and no format arguments 
[-Werror=format-security]
|  1161 | mvwprintw(details_pad.pPad, 2, 0, szTemp);
|   |   ^~
| cc1: some warnings being treated as errors
`

A full build log is at [1].

See #993179 for the change in ncurses which lead to these new errors.


1. https://ci.debian.net/data/autopkgtest/testing/amd64/c/cunit/15168126/log.gz



Bug#994011: marked as done (ghostscript: CVE-2021-3781)

2021-09-10 Thread Debian Bug Tracking System
Your message dated Fri, 10 Sep 2021 16:02:07 +
with message-id 
and subject line Bug#994011: fixed in ghostscript 9.53.3~dfsg-7+deb11u1
has caused the Debian Bug report #994011,
regarding ghostscript: CVE-2021-3781
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.)


-- 
994011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ghostscript
Version: 9.53.3~dfsg-7
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=704342
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for ghostscript.

CVE-2021-3781[0].

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-3781
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3781
[1] https://bugs.ghostscript.com/show_bug.cgi?id=704342 (not public yet)
[2] https://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=a9bd3dec9fde

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: ghostscript
Source-Version: 9.53.3~dfsg-7+deb11u1
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated ghostscript 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 09 Sep 2021 19:23:11 +0200
Source: ghostscript
Architecture: source
Version: 9.53.3~dfsg-7+deb11u1
Distribution: bullseye-security
Urgency: high
Maintainer: Debian Printing Team 
Changed-By: Salvatore Bonaccorso 
Closes: 994011
Changes:
 ghostscript (9.53.3~dfsg-7+deb11u1) bullseye-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Include device specifier strings in access validation (CVE-2021-3781)
 (Closes: #994011)
Checksums-Sha1: 
 4737cfd35503a61ffdad3ee475ce2df32efaae9d 2864 
ghostscript_9.53.3~dfsg-7+deb11u1.dsc
 9ce4415e5f37d858b5eb4d11040cf4079f2129c6 23948068 
ghostscript_9.53.3~dfsg.orig.tar.xz
 6e303c9863d23dce0cfdcd70b4149ed958714aba 120292 
ghostscript_9.53.3~dfsg-7+deb11u1.debian.tar.xz
Checksums-Sha256: 
 701551ac2ffaa9763f4e90d2f0d58719fd59708604f1204506ed258149da09ff 2864 
ghostscript_9.53.3~dfsg-7+deb11u1.dsc
 678f99fc6cca9a224f49891b8db5d9a325b8b3fbbffa9f29d44bac9f54603f3d 23948068 
ghostscript_9.53.3~dfsg.orig.tar.xz
 b08c4a40ee3731b0d94cf21bcb1bc49bd76818b71ee63c91cab9d34f0b03a021 120292 
ghostscript_9.53.3~dfsg-7+deb11u1.debian.tar.xz
Files: 
 48775e509741196d9267f98382d49371 2864 text optional 
ghostscript_9.53.3~dfsg-7+deb11u1.dsc
 653da2a0bebf9949634c137da72d1e26 23948068 text optional 
ghostscript_9.53.3~dfsg.orig.tar.xz
 e097902e2b65b9f238c43c41ec5b564b 120292 text optional 
ghostscript_9.53.3~dfsg-7+deb11u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmE6RLJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EbhMP/1LHmXAGw3LM40A6FQ9DLMeVKe3w+vEM
gMPWJo2jhqMu0Ga9V7FVgfw3cbpScQ7G3e1e0q+sFUNQMYIT+eWs+y0oSbfvOfwd
3KzRhXklc/lR/1Q55/zkYu4wVuM0lrEFPBo7r5dXDSHgm6aP4t+fXA0xLaDs0e3G
Yq27HOqOMvST2mQSCVfX1VVzAlfuRAOrgMbNnNaCZK/aPELuvW6OihiMzP23eMhY
a8pJL3LJgjARq5ODtEL0xOU3bKKDFiIk/L07jGZwQ8df05YhxteggEhIGic6cVIG
BiIQ963fZuNLV5+x18DMacnLY4GSLmM+ZNcLwYKakvOORZTDPc60X8rd631JMcv3
xxYeoBafirITnAqkpEG/JpiBz/YCzuPiry8IsXWnjXEoocykApE34gGHRFcwtnmm
FDFmAX/wf3paNtnFQZWFItk3HAC7w1sPUUKmzoHqJ4329bAsBKAqUwmjvw2lc2pz
UWR63biKtiax9THOF/AZJNeD6PFG53BWhKuufwtWjMBXPln1DgVyRJYyDjyy8atC
PDquAfH7uSNv6SKyG+W2LIXNe4c7NjixXMVlHQostQx20NU4hFMgd44tfTpOta/U
WxPF1LswJI456y0z6GFS//MVbUOM/m8BLs7H0ADNgy3C99oM9IpQPYmGBbzgSXXZ
s2kJHv7FcjNa
=NcKb
-END PGP SIGNATURE End Message ---


Bug#994033: mpd: Fails to find ldd libraries from libraspberrypi0 that have moved

2021-09-10 Thread kaliko

Hi Tim

Max Kellermann wrote :

On 2021/09/10 11:43, Tim Phipps  wrote:

AN upgrade to rasbian stable ahs moved some ldd files included in the 
libraspberrypi0 packages and now mpd fails to start.


MPD doesn't use any of these libraries.  These are indirect
dependencies, maybe via FFmpeg?  In any case, this is not a MPD
packaging problem.


Did you mixed Debian/bullseye repositories with Raspbian|Raspberry Pi 
OS/bullseye?
These are not compatible, especially for non architecture independent package 
like MPD.
libmmal_core.so is provided by libraspberrypi0 package which is not in Debian 
repositories.

This issue is not Debian related IMHO.

By the way, I believe rasbian stable is still based on buster, not bullseye.

Cheers
k



OpenPGP_signature
Description: OpenPGP digital signature


Bug#993037: Acknowledgement (nextcloud-desktop: Stop working since 3.3.1 release.)

2021-09-10 Thread Christian Marillat
tags 993037 fixed-upstream
thanks

Hi,

This bug has been fixed by upstream author in version 3.3.3

Christian



Processed: Re: Bug#993037: Acknowledgement (nextcloud-desktop: Stop working since 3.3.1 release.)

2021-09-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 993037 fixed-upstream
Bug #993037 [nextcloud-desktop] nextcloud-desktop: Stop working since 3.3.1 
release.
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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



Processed: your mail

2021-09-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reopen 987816
Bug #987816 {Done: Adrian Bunk } [src:dask.distributed] 
dask.distributed: FTBFS due to a build-time test failure
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions dask.distributed/2021.01.0+ds.1-2.1.
> #When building dask.distributed/2021.01.0+ds.1-2 package, the build-time 
> tests fails. 
> https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/dask.distributed.html
> thanks
Stopping processing here.

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



Processed: your mail

2021-09-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> unarchive 987816
Bug #987816 {Done: Adrian Bunk } [src:dask.distributed] 
dask.distributed: FTBFS due to a build-time test failure
Unarchived Bug 987816
> thanks
Stopping processing here.

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



Bug#994011: ghostscript: CVE-2021-3781

2021-09-10 Thread Salvatore Bonaccorso
Hi Jonas,

On Thu, Sep 09, 2021 at 09:16:22PM +0200, Jonas Smedegaard wrote:
> Quoting Salvatore Bonaccorso (2021-09-09 20:43:30)
> > Hi Jonas,
> > 
> > On Thu, Sep 09, 2021 at 08:09:42PM +0200, Jonas Smedegaard wrote:
> > > Hi Salvatore,
> > > 
> > > Quoting Salvatore Bonaccorso (2021-09-09 19:20:08)
> > > > The following vulnerability was published for ghostscript.
> > > > 
> > > > CVE-2021-3781[0].
> > > 
> > > I have prepared a package fixing this issue, available at 
> > > https://salsa.debian.org/printing-team/ghostscript/-/tree/debian/bullseye
> > > 
> > > Please tell how I should proceed with it - or feel free to proceed 
> > > yourself from here.
> > 
> > I did actually already uploaded earlier today to the embargoed queues,
> > waiting for the builds of mips64el and s390x yet, but then hope to
> > release the DSA soon.
> 
> Excellent!

DSA 4972-1 released for it.

Regards,
Salvatore



Bug#978832: marked as done (gupnp-av: ftbfs with autoconf 2.70)

2021-09-10 Thread Debian Bug Tracking System
Your message dated Fri, 10 Sep 2021 11:49:08 +
with message-id 
and subject line Bug#978832: fixed in gupnp-av 0.12.11-3
has caused the Debian Bug report #978832,
regarding gupnp-av: ftbfs with autoconf 2.70
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.)


-- 
978832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gupnp-av
Version: 0.12.11-2
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270

[This bug report is not targeted to the upcoming bullseye release]

The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/gupnp-av_0.12.11-2_unstable_ac270.log
The last lines of the build log are at the end of this report.

To build with autoconf 2.70, please install the autoconf package from
experimental:  apt-get -t=experimental install autoconf 

[...]

Check disk space


Sufficient free space for build

User Environment


APT_CONFIG=/var/lib/sbuild/apt.conf
HOME=/sbuild-nonexistent
LANG=C.UTF-8
LC_ALL=C.UTF-8
LOGNAME=user42
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=unstable
SCHROOT_CHROOT_NAME=sid-amd64-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=1001
SCHROOT_GROUP=user42
SCHROOT_SESSION_ID=sid-amd64-sbuild-ffedfcb0-27e7-4a10-869c-c3e1ec93586a
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42

dpkg-buildpackage
-

Command: dpkg-buildpackage -us -uc -sa -rfakeroot
dpkg-buildpackage: info: source package gupnp-av
dpkg-buildpackage: info: source version 0.12.11-2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Jeremy Bicha 
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean --with gnome,gir
   dh_gnome_clean
   dh_clean
 dpkg-source -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building gupnp-av using existing 
./gupnp-av_0.12.11.orig.tar.xz
dpkg-source: info: building gupnp-av in gupnp-av_0.12.11-2.debian.tar.xz
dpkg-source: info: building gupnp-av in gupnp-av_0.12.11-2.dsc
 debian/rules build
dh build --with gnome,gir
   dh_update_autotools_config
   dh_autoreconf
configure.ac:25: warning: The macro `AC_HEADER_STDC' is obsolete.
configure.ac:25: You should run autoupdate.
./lib/autoconf/headers.m4:657: AC_HEADER_STDC is expanded from...
configure.ac:25: the top level
configure.ac:25: warning: The macro `AC_HEADER_STDC' is obsolete.
configure.ac:25: You should run autoupdate.
./lib/autoconf/headers.m4:657: AC_HEADER_STDC is expanded from...
configure.ac:25: the top level
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
Can't exec "gtkdocize": No such file or directory at 
/usr/share/autoconf/Autom4te/FileUtils.pm line 293.
autoreconf: error: gtkdocize failed with exit status: 2
dh_autoreconf: error: autoreconf -f -i returned exit code 2
make: *** [debian/rules:7: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: gupnp-av
Source-Version: 0.12.11-3
Done: Jeremy Bicha 

We believe that the bug you reported is fixed in the latest version of
gupnp-av, 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.
Jeremy Bicha  (supplier of updated gupnp-av package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Sep 2021 07:

Processed: Bug#978832 marked as pending in gupnp-av

2021-09-10 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #978832 [src:gupnp-av] gupnp-av: ftbfs with autoconf 2.70
Ignoring request to alter tags of bug #978832 to the same tags previously set

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



Bug#978832: marked as pending in gupnp-av

2021-09-10 Thread Jeremy Bicha
Control: tag -1 pending

Hello,

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

https://salsa.debian.org/gnome-team/gupnp-av/-/commit/084f45cb644ad363d7b813a9dd1b6f63be65fb67


debian/control{,in}: Add missing build-dependency gtk-doc-tools

Closes: #978832


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/978832



Bug#993713: marked as done (golang-github-xenolf-lego accesses the internet during the build)

2021-09-10 Thread Debian Bug Tracking System
Your message dated Fri, 10 Sep 2021 11:18:44 +
with message-id 
and subject line Bug#993713: fixed in golang-github-xenolf-lego 4.1.3-3
has caused the Debian Bug report #993713,
regarding golang-github-xenolf-lego accesses the internet 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.)


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

https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd64/golang-github-xenolf-lego.html

...
edgedns_test.go:207: 
Error Trace:edgedns_test.go:207
Error:  Received unexpected error:
could not find the start of authority for 
bar.com.: dial udp: lookup google-public-dns-b.google.com on [::1]:53: read udp 
[::1]:40563->[::1]:53: read: connection refused
Test:   
TestDNSProvider_findZone/Extract_root_record_name
=== CONT  TestDNSProvider_findZone/Extract_sub_record_name
edgedns_test.go:207: 
Error Trace:edgedns_test.go:207
Error:  Received unexpected error:
could not find the start of authority for 
foo.bar.com.: dial udp: lookup google-public-dns-b.google.com on [::1]:53: read 
udp [::1]:37392->[::1]:53: read: connection refused
Test:   TestDNSProvider_findZone/Extract_sub_record_name
--- FAIL: TestDNSProvider_findZone (0.00s)
...


https://buildd.debian.org/status/fetch.php?pkg=golang-github-xenolf-lego&arch=all&ver=4.1.3-2&stamp=1630837084&raw=0

...
client_test.go:19: 
Error Trace:client_test.go:19
Error:  Received unexpected error:
Get 
"https://api.reg.ru/api/regru2/zone/remove_record?input_data=%7B%22username%22%3A%22test%22%2C%22password%22%3A%22test%22%2C%22domains%22%3A%5B%7B%22dname%22%3A%22test.ru%22%7D%5D%2C%22subdomain%22%3A%22_acme-challenge%22%2C%22content%22%3A%22txttxttxt%22%2C%22record_type%22%3A%22TXT%22%2C%22output_content_type%22%3A%22plain%22%7D&input_format=json":
 dial tcp 194.58.116.30:443: connect: network is unreachable
Test:   TestRemoveRecord
--- FAIL: TestRemoveRecord (0.13s)
...
--- End Message ---
--- Begin Message ---
Source: golang-github-xenolf-lego
Source-Version: 4.1.3-3
Done: Félix Sipma 

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

Debian distribution maintenance software
pp.
Félix Sipma  (supplier of updated golang-github-xenolf-lego 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Sep 2021 11:42:24 +0200
Source: golang-github-xenolf-lego
Architecture: source
Version: 4.1.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Félix Sipma 
Closes: 993713
Changes:
 golang-github-xenolf-lego (4.1.3-3) unstable; urgency=medium
 .
   * add patch to skip tests which need network access (Closes: #993713)
Checksums-Sha1:
 0a8696bafb160d3896c754a489e702a7ff0eb21b 2506 
golang-github-xenolf-lego_4.1.3-3.dsc
 b6673c6b2675ba171dc91968c532badcf73dc2b1 5572 
golang-github-xenolf-lego_4.1.3-3.debian.tar.xz
Checksums-Sha256:
 d08f9ab77edc55e8444c452bad2e7077556defe85fd6e20ce052c94ab5df9408 2506 
golang-github-xenolf-lego_4.1.3-3.dsc
 2824d41c657d8e6eee980fa4a06727d13e99ea06fde99f73e44ec1ad45c392f1 5572 
golang-github-xenolf-lego_4.1.3-3.debian.tar.xz
Files:
 dd3ced99f4e8cb0369e38a681bd9d2f4 2506 golang optional 
golang-github-xenolf-lego_4.1.3-3.dsc
 29d6a7f037ac88770dae71cba9124ac7 5572 golang optional 
golang-github-xenolf-lego_4.1.3-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQR6zeIsS8L0XLQfqiQBpfxHUdFE8AUCYTs3IAAKCRABpfxHUdFE
8GkHAQDXo1zp+GDhs1JiJjgK4cVeDb4DF2V7Hg6D57GiyYrs8QD7Bot9ZRWjZOej
A5Fxo8K5bGRvhPcmuxJsdI5WnKh2aA0=
=vmRb
-END PGP SIGNATURE End Message ---


Bug#994033: mpd: Fails to find ldd libraries from libraspberrypi0 that have moved

2021-09-10 Thread Max Kellermann
On 2021/09/10 11:43, Tim Phipps  wrote:
> AN upgrade to rasbian stable ahs moved some ldd files included in the 
> libraspberrypi0 packages and now mpd fails to start.

MPD doesn't use any of these libraries.  These are indirect
dependencies, maybe via FFmpeg?  In any case, this is not a MPD
packaging problem.



Bug#988386: marked as done (ntfs-3g: CVE-2021-33285 CVE-2021-35269 CVE-2021-35268 CVE-2021-33289 CVE-2021-33286 CVE-2021-35266 CVE-2021-33287 CVE-2021-35267 CVE-2021-39251 CVE-2021-39252 CVE-2021-3925

2021-09-10 Thread Debian Bug Tracking System
Your message dated Fri, 10 Sep 2021 10:48:50 +
with message-id 
and subject line Bug#988386: fixed in ntfs-3g 1:2017.3.23AR.3-3+deb10u1
has caused the Debian Bug report #988386,
regarding ntfs-3g: CVE-2021-33285 CVE-2021-35269 CVE-2021-35268 CVE-2021-33289 
CVE-2021-33286 CVE-2021-35266 CVE-2021-33287 CVE-2021-35267 CVE-2021-39251 
CVE-2021-39252 CVE-2021-39253 CVE-2021-39254 CVE-2021-39255 CVE-2021-39256 
CVE-2021-39257 CVE-2021-39258 CVE-2021-39259 CVE-2021-39260 CVE-2021-39261 
CVE-2021-39262 CVE-2021-39263
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.)


-- 
988386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ntfs-3g
Version: 2017.3.23AR.3

For CVE's pending from upstream, is everything already mirrored so upstream
fixes are applied in the next release? I'm asking because the upstream
maintainers are trying to identify how soon their fixes will be applied to
your packages.

Thanks,




-- 

*Jeremy Galindo* Associate Mgr., Offensive Security
Datto, Inc. Direct Line www.datto.com


Join the conversation! [image: Facebook] 
[image: Twitter]  [image: LinkedIn]
  [image: Blog RSS]
 [image: Slideshare]
  [image: Spiceworks]

--- End Message ---
--- Begin Message ---
Source: ntfs-3g
Source-Version: 1:2017.3.23AR.3-3+deb10u1
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated ntfs-3g package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 05 Sep 2021 14:53:02 +0200
Source: ntfs-3g
Architecture: source
Version: 1:2017.3.23AR.3-3+deb10u1
Distribution: buster-security
Urgency: high
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Salvatore Bonaccorso 
Closes: 988386
Changes:
 ntfs-3g (1:2017.3.23AR.3-3+deb10u1) buster-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Fixed an endianness error in ntfscp
   * Checked the locations of MFT and MFTMirr at startup
   * Fix multiple buffer overflows.
 CVE-2021-33285, CVE-2021-35269, CVE-2021-35268, CVE-2021-33289,
 CVE-2021-33286, CVE-2021-35266, CVE-2021-33287, CVE-2021-35267,
 CVE-2021-39251, CVE-2021-39252, CVE-2021-39253, CVE-2021-39254,
 CVE-2021-39255, CVE-2021-39256, CVE-2021-39257, CVE-2021-39258,
 CVE-2021-39259, CVE-2021-39260, CVE-2021-39261, CVE-2021-39262,
 CVE-2021-39263. (Closes: #988386)
Checksums-Sha1: 
 4c9b98ac5aba5635d06fdfd59e070c11b06145b2 2363 
ntfs-3g_2017.3.23AR.3-3+deb10u1.dsc
 7da89778338c57bc3326107c3413d36883496f39 34876 
ntfs-3g_2017.3.23AR.3-3+deb10u1.debian.tar.xz
Checksums-Sha256: 
 a36b939deba2bf22a98ee6d340162b2bfb103d65c13daeffb10fd3a49dcd6b5e 2363 
ntfs-3g_2017.3.23AR.3-3+deb10u1.dsc
 35def7823d7690c9d54496a145fb11107ccb0f6073e35f06e4cad5d1e73a0fae 34876 
ntfs-3g_2017.3.23AR.3-3+deb10u1.debian.tar.xz
Files: 
 321f8a585f4202d4c699eb6dc92011d3 2363 otherosfs optional 
ntfs-3g_2017.3.23AR.3-3+deb10u1.dsc
 08b36230b5ab1d9a4ea53417fcfdbd38 34876 otherosfs optional 
ntfs-3g_2017.3.23AR.3-3+deb10u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmE0ygRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89Ems4P/jyNLRN6ZY6m4d83JPIMTZOY8x9yLB0E
cXPMs1DPhYz+l32WkWgsqB7ZYJmhQNiDcSoSJ7Srh9EVV9xeBpmKkgXg4K0G6nqs
pUxKJj0iySEqI15EbmzzYPgrEzHudFVRNruFi74aaiIkb2Gov315K0e+MUH2qvBG
ZRv0nrXuGVtwCRSPVeB0J6dUGJl+GCWMv7c6dH9SrrhbUhf1QGqGgJFQzFZ8L/L/
5269eEmStLvWy2ZuaNizfRmA3cpYKiiSIsniyrHNox0AZhn6+vZcCKFYjWsAYi5L
tgDhOinHeAp2Y3k7k2ef1cJ1qokcNKxa6Fk2/IYyEwAy7hW/OuF+EorhguCD9LF2
i8NemPr1dUhhrszfyqs5jOBSb/orvXjzrzYlizDnse4

Bug#988386: marked as done (ntfs-3g: CVE-2021-33285 CVE-2021-35269 CVE-2021-35268 CVE-2021-33289 CVE-2021-33286 CVE-2021-35266 CVE-2021-33287 CVE-2021-35267 CVE-2021-39251 CVE-2021-39252 CVE-2021-3925

2021-09-10 Thread Debian Bug Tracking System
Your message dated Fri, 10 Sep 2021 10:47:45 +
with message-id 
and subject line Bug#988386: fixed in ntfs-3g 1:2017.3.23AR.3-4+deb11u1
has caused the Debian Bug report #988386,
regarding ntfs-3g: CVE-2021-33285 CVE-2021-35269 CVE-2021-35268 CVE-2021-33289 
CVE-2021-33286 CVE-2021-35266 CVE-2021-33287 CVE-2021-35267 CVE-2021-39251 
CVE-2021-39252 CVE-2021-39253 CVE-2021-39254 CVE-2021-39255 CVE-2021-39256 
CVE-2021-39257 CVE-2021-39258 CVE-2021-39259 CVE-2021-39260 CVE-2021-39261 
CVE-2021-39262 CVE-2021-39263
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.)


-- 
988386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ntfs-3g
Version: 2017.3.23AR.3

For CVE's pending from upstream, is everything already mirrored so upstream
fixes are applied in the next release? I'm asking because the upstream
maintainers are trying to identify how soon their fixes will be applied to
your packages.

Thanks,




-- 

*Jeremy Galindo* Associate Mgr., Offensive Security
Datto, Inc. Direct Line www.datto.com


Join the conversation! [image: Facebook] 
[image: Twitter]  [image: LinkedIn]
  [image: Blog RSS]
 [image: Slideshare]
  [image: Spiceworks]

--- End Message ---
--- Begin Message ---
Source: ntfs-3g
Source-Version: 1:2017.3.23AR.3-4+deb11u1
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated ntfs-3g package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 05 Sep 2021 14:50:38 +0200
Source: ntfs-3g
Architecture: source
Version: 1:2017.3.23AR.3-4+deb11u1
Distribution: bullseye-security
Urgency: high
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Salvatore Bonaccorso 
Closes: 988386
Changes:
 ntfs-3g (1:2017.3.23AR.3-4+deb11u1) bullseye-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Fixed an endianness error in ntfscp
   * Checked the locations of MFT and MFTMirr at startup
   * Fix multiple buffer overflows.
 CVE-2021-33285, CVE-2021-35269, CVE-2021-35268, CVE-2021-33289,
 CVE-2021-33286, CVE-2021-35266, CVE-2021-33287, CVE-2021-35267,
 CVE-2021-39251, CVE-2021-39252, CVE-2021-39253, CVE-2021-39254,
 CVE-2021-39255, CVE-2021-39256, CVE-2021-39257, CVE-2021-39258,
 CVE-2021-39259, CVE-2021-39260, CVE-2021-39261, CVE-2021-39262,
 CVE-2021-39263. (Closes: #988386)
Checksums-Sha1: 
 78fea16aae37f144a4cc06c4e3af5e4c386fcb05 2369 
ntfs-3g_2017.3.23AR.3-4+deb11u1.dsc
 18a483bb91cb5cb532454ae5c4f18d71e5cd9b80 1277609 
ntfs-3g_2017.3.23AR.3.orig.tar.gz
 8b1c7734a2fbe740d3e9de4d77e421498acece81 34860 
ntfs-3g_2017.3.23AR.3-4+deb11u1.debian.tar.xz
Checksums-Sha256: 
 715b6fd6aaf2ecb26bc0d734bce34e3f66ede437431b217b0d5164f2d7797f72 2369 
ntfs-3g_2017.3.23AR.3-4+deb11u1.dsc
 a83fbd533259abd5b73dc37635cc003a697248375702ddcc39af129957a7564b 1277609 
ntfs-3g_2017.3.23AR.3.orig.tar.gz
 482ae83729b3b0df0ad8d678cd6c72ee93d5033bd06bae81b98abd5cdd97650e 34860 
ntfs-3g_2017.3.23AR.3-4+deb11u1.debian.tar.xz
Files: 
 22917eed6b5ceaf761d8fa81a022669c 2369 otherosfs optional 
ntfs-3g_2017.3.23AR.3-4+deb11u1.dsc
 5202fb9d41b0db673b73da4ca9bb88b5 1277609 otherosfs optional 
ntfs-3g_2017.3.23AR.3.orig.tar.gz
 3fe14d3806a99104faa2286d431a58fb 34860 otherosfs optional 
ntfs-3g_2017.3.23AR.3-4+deb11u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmE0wctfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EUZ0P/AhE3ULpPg3WeJN7dAreQtWPIKUZssVI
9beZQ4/kRPlws52Q+8NEdKXylxry2Tf8ZV7SW8z8kM55BDBChk8h3CcKQmvTL0M4
RIZ4FTsXU

Bug#993713: marked as pending in golang-github-xenolf-lego

2021-09-10 Thread Félix Sipma
Control: tag -1 pending

Hello,

Bug #993713 in golang-github-xenolf-lego reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/packages/golang-github-xenolf-lego/-/commit/8e77b4332e238d6d713ca9e9d9770be8680b5bc1


add patch to skip tests which need network access (Closes: #993713)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/993713



Processed: Bug#993713 marked as pending in golang-github-xenolf-lego

2021-09-10 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #993713 [src:golang-github-xenolf-lego] golang-github-xenolf-lego accesses 
the internet during the build
Added tag(s) pending.

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



Bug#994033: mpd: Fails to find ldd libraries from libraspberrypi0 that have moved

2021-09-10 Thread Tim Phipps
Package: mpd
Version: 0.22.6-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,
AN upgrade to rasbian stable ahs moved some ldd files included in the 
libraspberrypi0 packages and now mpd fails to start.

OK# ldd /usr/bin/mpd | grep -w not | cat
libvchiq_arm.so => not found
libvcos.so => not found
libmmal_core.so => not found
libmmal_util.so => not found
libmmal_vc_client.so => not found
libbcm_host.so => not found
libvcsm.so => not found


-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 11 (bullseye)
Release:11
Codename:   bullseye
Architecture: armv6l

Kernel: Linux 5.10.60+
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mpd depends on:
ii  adduser   3.118
ii  init-system-helpers   1.60
ii  libadplug-2.3.3-0 2.3.3+dfsg-2
ii  libao41.2.2+20180113-1.1
ii  libasound21.2.4-1.1+rpt1
ii  libaudiofile1 0.3.6-5
ii  libavahi-client3  0.8-5
ii  libavahi-common3  0.8-5
ii  libavcodec58  7:4.3.2-0+rpt1+deb11u2
ii  libavformat58 7:4.3.2-0+rpt1+deb11u2
ii  libavutil56   7:4.3.2-0+rpt1+deb11u2
ii  libbz2-1.01.0.8-4
ii  libc6 2.31-13+rpt2+rpi1
ii  libcdio-cdda2 10.2+2.0.0-1+b1
ii  libcdio-paranoia2 10.2+2.0.0-1+b1
ii  libcdio19 2.1.0-2
ii  libchromaprint1   1.5.0-2
ii  libcurl3-gnutls   7.74.0-1.3
ii  libdbus-1-3   1.12.20-2
ii  libexpat1 2.2.10-2
ii  libfaad2  2.10.0-1
ii  libflac8  1.3.3-2
ii  libfluidsynth22.1.7-1.1
ii  libgcc-s1 10.2.1-6+rpi1
ii  libgme0   0.6.3-2
ii  libicu67  67.1-7
ii  libid3tag00.15.1b-14
ii  libiso9660-11 2.1.0-2
ii  libixml10 1:1.8.4-2
ii  libjack-jackd2-0 [libjack-0.125]  1.9.17~dfsg-1
ii  libjs-sphinxdoc   3.4.3-2
ii  libmad0   0.15.1b-10
ii  libmikmod33.3.11.1-6
ii  libmms0   0.6.4-3
ii  libmodplug1   1:0.8.9.0-3
ii  libmp3lame0   3.100-3
ii  libmpcdec62:0.1~r495-2
ii  libmpdclient2 2.19-1
ii  libmpg123-0   1.26.4-1
ii  libnfs13  4.0.0-1
ii  libogg0   1.3.4-0.1
ii  libopenal11:1.19.1-2
ii  libopus0  1.3.1-0.1
ii  libpcre3  2:8.39-13
ii  libpulse0 14.2-2+rpi1
ii  libsamplerate00.2.1+ds0-1
ii  libshout3 2.4.5-1
ii  libsidplayfp5 2.0.5-2
ii  libsmbclient  2:4.13.5+dfsg-2
ii  libsndfile1   1.0.31-2
ii  libsndio7.0   1.5.0-3
ii  libsoxr0  0.1.3-4+rpi1
ii  libsqlite3-0  3.34.1-3
ii  libstdc++610.2.1-6+rpi1
ii  libsystemd0   247.3-6+rpi1
ii  libupnp13 1:1.8.4-2
ii  liburing1 0.7-3
ii  libvorbis0a   1.3.7-1
ii  libvorbisenc2 1.3.7-1
ii  libwavpack1   5.4.0-1
ii  libwildmidi2  0.4.3-1
ii  libyajl2  2.1.0-3
ii  libzzip-0-13  0.13.62-3.3
ii  lsb-base  11.1.0+rpi1
ii  zlib1g1:1.2.11.dfsg-2

mpd recommends no packages.

Versions of packages mpd suggests:
ii  avahi-daemon  0.8-5
pn  icecast2  
ii  mpc [mpd-client]  0.33-1
ii  ncmpcpp [mpd-client]  0.9.2-1
pn  pulseaudio

-- Configuration Files:
/etc/mpd.conf changed:
user "mpd"
bind_to_address "any"
zeroconf_enabled "yes"
zeroconf_name "Music Player @ %h"
password "JukeBox@read,add,control,admin"
default_permissions "read"
music_directory "nfs://mpd/home/av/Music"
database {
  plugin "proxy"
  host "mpd"
  port "6601"
}
input_cache {
  size "1 GB"
}
state_file "/var/lib/mpd/state"
sticker_file "/var/lib/mpd/sticker.sql"
playlist_directory "/var/lib/mpd/playlists"
max_output_buffer_size "65536"
audio_output_format "44100:16:1"
audio_output {
 type "alsa"
 name "Allo Mini Boss"
 device "hw:BossDAC"
 mixer_type "software"
}
replaygain "auto"
replaygain_missing_preamp "-10"
filesystem_charset "UTF-8"


--

Bug#993207: regression: constant ~20% CPU usage + crackling sound since 15.0+dfsg1-2

2021-09-10 Thread Igor Kovalenko
On Sat, 28 Aug 2021 16:58:48 +0200 Christoph Anton Mitterer
 wrote:
> Since upgrading to 15.0+dfsg1-2, the pulseaudio daemon runs constantly at 
> around ~20% CPU
> on my system (even when no sound is played).
>
> If sound is played it's constantly crackling.
>
> Downgrading to the previous 14.2-2 from testing (and restarting the daemon) 
> fixes the issue.
>
> Any ideas?
>

Hi Chris,

You attached files for 14.2, could you please attach pa-info output from 15.0?
Please also have a look in the system journal, if there are any errors
from pulseaudio please provide these as well.

Thank you!



Bug#993011: pulseaudio-module-bluetooth: no longer detects bluetooth headphones

2021-09-10 Thread Igor Kovalenko
On Fri, Sep 10, 2021 at 12:37 PM Vincent Lefevre  wrote:
> I could eventually solve the problem, which was apparently caused by
> some other Bluetooth audio device. Some details below...
>
> [skip]
>
> What I did first is to upgrade again to pulseaudio 15.0+dfsg1-2, then
> reboot. With my settings, I automatically connect to 7C:96:D2:4E:98:41
> after logging in. As before, I could then connect to the headset with
>
>   bluetoothctl connect 38:18:4C:4B:AC:93
>
> which succeeded, but the headset wasn't recognized by PulseAudio 15.
> I had to disconnect from both devices with 2 "bluetoothctl disconnect"
> commands, then connect to the headset *alone* so that it could get
> recognized by PulseAudio 15.

This looks very much like an issue with bluez side caching of available
device profiles, this was being worked on in subsequent bluez releases.



Bug#993011: pulseaudio-module-bluetooth: no longer detects bluetooth headphones

2021-09-10 Thread Vincent Lefevre
On 2021-09-10 09:12:48 +0300, Igor Kovalenko wrote:
> If your headphones support both HSP (Headset) and HFP (Handsfree)
> profiles, pulseaudio will now prefer HFP by default.
> This usually works fine unless bluez does not want to connect
> headphones with HFP profile for some reason.

I could eventually solve the problem, which was apparently caused by
some other Bluetooth audio device. Some details below...

> Please attach 'bluetoothctl info' for your headset,

zira:~> bluetoothctl devices
Device 7C:96:D2:4E:98:41 EDIFIER Luna Eclipse HD
Device 38:18:4C:4B:AC:93 WH-1000XM3

zira:~> bluetoothctl info 7C:96:D2:4E:98:41
Device 7C:96:D2:4E:98:41 (public)
Name: EDIFIER Luna Eclipse HD
Alias: EDIFIER Luna Eclipse HD
Class: 0x00240428
Icon: audio-card
Paired: yes
Trusted: no
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)

zira:~> bluetoothctl info 38:18:4C:4B:AC:93
Device 38:18:4C:4B:AC:93 (public)
Name: WH-1000XM3
Alias: WH-1000XM3
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Vendor specific   (-deca-fade-deca-deafdecacaff)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: Amazon.com Services, Inc. (fe03--1000-8000-00805f9b34fb)
[Vendor specific UUIDs]
Modalias: usb:v054Cp0CD3d0452

What I did first is to upgrade again to pulseaudio 15.0+dfsg1-2, then
reboot. With my settings, I automatically connect to 7C:96:D2:4E:98:41
after logging in. As before, I could then connect to the headset with

  bluetoothctl connect 38:18:4C:4B:AC:93

which succeeded, but the headset wasn't recognized by PulseAudio 15.
I had to disconnect from both devices with 2 "bluetoothctl disconnect"
commands, then connect to the headset *alone* so that it could get
recognized by PulseAudio 15.

Now everything is OK, even after reboot with my usual settings.
I suppose that there was old or incomplete information for the
headphones. I wonder whether PulseAudio could have done something
to avoid this issue, or whether this is worth an announce (if this
is a known issue that may affect other users).

Note: With PulseAudio 15, I can now have both devices with the
A2DP Sink profile (this was not possible with PulseAudio 14, as
I could still check before upgrading again to PulseAudio 15).

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



Processed: autopkgtests test packages from boost1.71

2021-09-10 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #992223 [src:boost1.74] autopkgtests test packages from boost1.71
Severity set to 'serious' from 'normal'

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