Bug#354288: README.Debian delete already, date exist in whitepaper_unicon.txt

[肖盛文]

Hi,

    README.Debian had deleted already in the current version 
unicon_3.0.4+dfsg1-1.


There are date describe  in whitepaper_unicon.txt.gz etc.

The date is write by Chinese:

    七月份，扩充了Unicon的显示字体。使其可以显示GB，GBK，BIG5，JIS，
KSCM。
    八月，便携了Unicon字体管理器。使系统可以在不同的TTY上显示不同的
字体。
    九月，编写了多语言输入法支持程序。并编写了配置工具。
    十月，Unicon3.0进入了测试阶段。
    十一月，发布Unicon3.0。

--
肖盛文 xiao sheng wen Faris Xiao
微信(wechat)：atzlinux
《铜豌豆 Linux》https://www.atzlinux.com
基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
GnuPG Public Key: 0x00186602339240CB



OpenPGP_0x00186602339240CB.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Bug#979481: pulseaudio: Long Beep before pulseaudio crashes, not sure if is related to new BIOS upgrade of LENOVO E485.

[DebianUser]

Package: pulseaudio
Version: 13.0-5
Severity: important
X-Debbugs-Cc: exam...@debian.org

Dear Maintainer,

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

   * What led up to the situation? booting kernel leds to beep.
   * What exactly did you do (or not do) that was effective (or
 ineffective)? I restarted pulseaudio and start beeping for like 10 seconds 
or sometimes it get stucked beeping.
   * What was the outcome of this action? 
   * What outcome did you expect instead? No beep just normal sound.

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


-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


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

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

Versions of packages pulseaudio depends on:
ii  adduser  3.118
ii  init-system-helpers  1.60
ii  libasound2   1.2.4-1
ii  libasound2-plugins   1.2.2-2
ii  libc62.31-6
ii  libcap2  1:2.44-1
ii  libdbus-1-3  1.12.20-1
ii  libgcc-s110.2.1-3
ii  libice6  2:1.0.10-1
ii  libltdl7 2.4.6-14
ii  liborc-0.4-0 1:0.4.32-1
ii  libpulse013.0-5
ii  libsm6   2:1.2.3-1
ii  libsndfile1  1.0.28-8
ii  libsoxr0 0.1.3-4
ii  libspeexdsp1 1.2~rc1.2-1.1
ii  libstdc++6   10.2.1-3
ii  libsystemd0  247.2-4
ii  libtdb1  1.4.3-1+b1
ii  libudev1 247.2-4
ii  libwebrtc-audio-processing1  0.3-1+b1
ii  libx11-6 2:1.6.12-1
ii  libx11-xcb1  2:1.6.12-1
ii  libxcb1  1.14-2.1
ii  libxtst6 2:1.2.3-1
ii  lsb-base 11.1.0
ii  pulseaudio-utils 13.0-5

Versions of packages pulseaudio recommends:
ii  dbus-user-session1.12.20-1
ii  libpam-systemd [logind]  247.2-4
ii  rtkit0.13-4

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  4.0-2
ii  pavumeter0.9.3-4+b3
ii  udev 247.2-4

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; 

Bug#979480: mpi4py: autopkgtest failure on arm64, armhf and ppc64el

[Graham Inggs]

Source: mpi4py
Version: 3.0.3-7
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
Tags: bullseye sid
User: debian...@lists.debian.org
Usertags: needs-update

Hi Maintainer

The autopkgtests of mpi4py have been failing since the upload of
openmpi 4.1.0-1 to unstable. I'm reporting this for arm64, armhf and
ppc64el, because amd64 and i386 fail in a different way due to
#979041.

I've copied what I hope is the relevant part of the log below.

I've also noticed that during the autopkgtest, there seem to be five
instances of pytest running in parallel and each test is run five
times.   Is this the correct way of testing this package?

autopkgtest [07:23:18]: test command1:
OMPI_MCA_rmaps_base_oversubscribe=yes mpiexec -n 5 pytest-3 --color=no
--verbose
autopkgtest [07:23:18]: test command1: [---
= test session starts ==
platform linux -- Python 3.9.1, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
-- /usr/bin/python3
cachedir: .pytest_cache
rootdir: /tmp/autopkgtest-lxc.llginr1y/downtmp/build.sWC/src, inifile:
setup.cfg, testpaths: test
collecting ... = test session starts
==
platform linux -- Python 3.9.1, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
-- /usr/bin/python3
cachedir: .pytest_cache
rootdir: /tmp/autopkgtest-lxc.llginr1y/downtmp/build.sWC/src, inifile:
setup.cfg, testpaths: test
collecting ... = test session starts
==
platform linux -- Python 3.9.1, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
-- /usr/bin/python3
cachedir: .pytest_cache
rootdir: /tmp/autopkgtest-lxc.llginr1y/downtmp/build.sWC/src, inifile:
setup.cfg, testpaths: test
collecting ... = test session starts
==
platform linux -- Python 3.9.1, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
-- /usr/bin/python3
cachedir: .pytest_cache
rootdir: /tmp/autopkgtest-lxc.llginr1y/downtmp/build.sWC/src, inifile:
setup.cfg, testpaths: test
collecting ... = test session starts
==
platform linux -- Python 3.9.1, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
-- /usr/bin/python3
cachedir: .pytest_cache
rootdir: /tmp/autopkgtest-lxc.llginr1y/downtmp/build.sWC/src, inifile:
setup.cfg, testpaths: test

Regards
Graham


=== FAILURES ===
_ TestGrequest.testAll _

self = 

def testAll(self):
ctx = GReqCtx()
greq = MPI.Grequest.Start(ctx.query, ctx.free, ctx.cancel)
>   self.assertFalse(greq.Test())
E   AssertionError: True is not false

test/test_grequest.py:30: AssertionError
 TestGrequest.testAll1 _


self = 

def testAll1(self):
ctx = GReqCtx()
greq = MPI.Grequest.Start(ctx.query, None, None)
>   self.assertFalse(greq.Test())
E   AssertionError: True is not false

test/test_grequest.py:50: AssertionError

 TestGrequest.testAll2 _

self = 

def testAll2(self):
greq = MPI.Grequest.Start(None, None, None)
>   self.assertFalse(greq.Test())
E   AssertionError: True is not false

test/test_grequest.py:63: AssertionError

...

=== 3 failed, 1109 passed, 30 skipped, 1 warnings in 143.17 seconds 

Bug#979474: dch: Cannot find debian directory!

[Adam D. Barratt]

Control: tags -1 - d-i

On Thu, 2021-01-07 at 06:03 +0100, Milchior wrote:
> I tried to follow 
> https://wiki.debian.org/Packaging/Intro?action=show=IntroDebianPackaging
> with the app (Anki) I would like to see updated in Debian and ubuntu.
> 
> For this, on a Debian distribution, I created an empty folder 
> /home/milchior/packaging/anki-2.1.38/debian
> and inside it then tried the command
> dch --create -v 2.1.28-1 --package anki
> 
> which led to the error message 
> > dch: fatal error at line 642:
> > Cannot find debian directory!
> > Are you in the correct directory?
> 
> So either the wiki should be corrected and the error message
> clarified, or there is a bug in this program. Maybe both

I'm not sure it's either, really.

The wiki page tells you to:

$ cd hithere-1.0
$ mkdir debian 

and then run "dch". So you'd be running dch from inside "hithere-1.0",
which has a "debian" subdirectory. It appears that you're running dch
instead from the debian subdirectory, which then obviously _doesn't_
have a debian subdirectory itself, so there is no way to create a
"debian/changelog" file in the directory you've run dch from.

I think both the wiki page and dch are correct here, and you've simply
misread the suggested flow.

Regards,

Adam

Bug#979145: RM: xfce4-equake-plugin/1.3.8.1-2+b2

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, 2021-01-06 at 17:30 -0800, Jeroen van Aart wrote:
> I am working on a fix, I hope to have it available soon.

Hi Jeroen, thanks and sorry for the rush on this. If you need some testing
don't hesitate to ask.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl/2tT8ACgkQ3rYcyPpX
RFtchgf+KKvM1U+OL/cx722qN5s9mcoLVWmI2l215/wQxbuy0U5FILwJIylii2qv
j3DHcILhjL8YzfGl7Mq2LbpYrkNGgUUU+qx6fjENrhpdX73oe18id8+QU0dZqT0R
Cr13+NUpkz32jBx1CxP50CZM3EFytcwrpXDXNWUFxrdExN60ohprRL560+Q2NpWl
6HLgTPOBjUPW52ZIHKQ8f4LRdg52rkcxmlU6LWFtrNxjny5bhLh/UlH3/ic8OBVV
8mu7FGvQy/Fwx34yZV/3uxyB5b0W2EQXdYiFMikc7Ptm91bU8d8JgPb7OhANZAbi
UlETsZak8PQHfDLbGeupw711JrGDGQ==
=DNMI
-END PGP SIGNATURE-

Bug#978550: pulseaudio: Pulseaudio do not detect HDMI output anymore after monitor power cycle

[Thomas Nemeth]

Workaround for now : in a terminal execute `pulseaudio -k -D` and it will 
rescan and detect the HDMI output.

Bug#979478: maven-debian-helper: generate d/watch with mode=svn for Subversion-distributed source packages

[Andrius Merkys]

Package: maven-debian-helper
Version: 2.4
Severity: wishlist

For Subversion-distributed source packages, mh_make generates
d/orig-tar.sh to download and clean up the upstream tarballs. Since
devscripts 2.20.1 uscan is capable to directly access Subversion
repositories using mode=svn (implemented similarly to mode=git).

It would be beneficial if mh_make could generate watch files with
mode=svn instead of d/orig-tar.sh as such watch files could be used by
qa.debian.org to automatically scan for new upstream releases. The sole
caveat, IMO, is the cleanup of upstream tarball, which is usually done
in generated d/orig-tar.sh:

tar -c -J -f $TAR --exclude '*.jar' --exclude '*.class' $DIR

However, I think the same could be achieved via Files-Excluded stanza in
d/copyright.

Andrius

Bug#961814: marked as pending in golang-google-protobuf

[Anthony Fok]

Hi Shengjing,

On Tue, Jan 5, 2021 at 8:42 AM Shengjing Zhu  wrote:
>
> Hi Anthony,

Thanks for writing to me!  Sorry for the late reply.
I was going to re-open this with the pseudo header "Control: reopen
-1" to keep this new version out of testing (buster), but then I
decided to study the issue further, I think we are safe to move
forward, allowing golang-google-protobuf to enter testing, while
keeping the old golang-goprotobuf 1.3.x if necessary.

> The reason that I haven't uploaded new version of this package, is
> that using golang-google-protobuf usually means using
> golang-goprotobuf 1.4+ as well.

Looks like that is not the case any more.
While golang-google-protobuf and protoc-gen-go v1.25.0 would still
pull in the old golang-goprotobuf 1.4+ package in the generated file,
apparently for backward compatibility during the 6-month transition
period that Joe Tsai @dsnet set:

import (
proto "github.com/golang/protobuf/proto"
...
)

Well, I think we have good news!

1.25.0+git20201208.160c747 doesn't do that any more.
The import proto "github.com/golang/protobuf/proto" line is gone;
the "const _ = proto.ProtoPackageIsVersion4" is also gone.

The latest golang-google-protobuf makes a clean break from the past.
It is now self-contained, and no longer pulls in the legacy golang-goprotobuf.
It is just like what you predicted: once GitHub issue #1077 is fixed,
we can move forward.

Thank you for your packaging of golang-google-protobuf which also
allows the clean separation with the old golang-goprotobuf ecosystem.

> However golang-goprotobuf 1.4+ breaks important packages like
> golang-gogottrpc and golang-gogoprotobuf.
> See that bugs on
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=golang-goprotobuf

Since golang-google-protobuf 1.25.0+git20201208.160c747 does not
require golang-goprotobuf 1.4+ any more, we can keep golang-goprotobuf
at 1.3.4-2 for buster to be safe.

I did try running ratt with a local test build of golang-goprotobuf
1.4.2, and was surprised that golang-gogottrpc built fine with it:

2021/01/05 18:14:30 PASSED: golang-gogottrpc

while golang-gogoprotobuf is not touched at all.  Am I missing something?

But yes, I'm sure you are much more familiar with golang-goprotobuf,
so if 1.4+ is indeed dangerous to other legacy packages, we'll just
have to make sure no one in the Go Team uploads golang-goprotobuf 1.4+
for buster.

Cheers,

Anthony

Bug#950782: closed by Debian FTP Masters (reply to Kartik Mistry ) (Bug#950782: fixed in recoll 1.28.3-1)

[Kartik Mistry]

reopen 950782
found 950782 1.28.3-1
thanks

On Wed, Jan 6, 2021 at 3:21 PM Marcus Frings
 wrote:
> Shouldn't it better suggest python3-py7zr instead of python3-lz4 as
> xiscu pointed out in the e-mail? (Many thanks to xiscu for spotting the
> solution!)

Correct! I'll fix this in the next upload!

-- 
Kartik Mistry | કાર્તિક મિસ્ત્રી
kartikm.wordpress.com

Bug#979477: pytest: please upgrade to the latest upstream version

[Sandro Tosi]

Source: pytest
Severity: important

Hello,
pytest 6.x has already been uploaded to unstable (triggering the migration), but
the version is not the latest one (currently 6.2.1).

Please package a later version; severity is set to important because the latest
version of tqdm requires at least pytest/6.1.1

Thanks,
Sandro

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

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#979476: ITP: dde -- meta package for Deepin Desktop Environment

[stan clay]

Package: wnpp
Severity: wishlist
Owner: clay stan 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: dde
  Version : 2020.08.13
  Upstream Author : linuxdeepin
* URL : https://github.com/linuxdeepin/dde
  License : GPL-2+
  Programming Lang:  -
  Description : meta package for Deepin Desktop Environment

This is a meta package depends Deepin New Desktop Envrionment.

Bug#979475: node-gyp-build: Keep out of testing

[Xavier Guimard]

Package: node-gyp-build
Severity: serious
Justification: Policy 2.1

node-gyp-rebuild replaces `node-gyp rebuild` using pre-compiled
binaries. This is useless in Debian.

I did an error when packaging it, this package should be removed from
Debian archive, shouldn't it?

Bug#979307: xfce4-battery-plugin: Always shows the "About xfce4-battery-plugin" dialog box on login

[David Haworth]

Hi,

the unexpected behavior appears to have gone away after a further upgrade
on 5th January.

Please close the ticket.

-- 
David Haworth   OS Kernel Developer  david.hawo...@elektrobit.com
Elektrobit Automotive GmbHTel: +49 9131 7701-6154
Am Wolfsmantel 46, 91058 Erlangen, GermanyFax: +49 9131 7701-6333
Geschäftsführer: Alexander Kocher  Amtsgericht Fürth HRB 4886

Bug#979474: dch: Cannot find debian directory!

[Milchior]

Package: devscripts
Version: 2.19.5+deb10u1
Severity: important
Tags: d-i

Dear Maintainer,

I tried to follow 
https://wiki.debian.org/Packaging/Intro?action=show=IntroDebianPackaging
with the app (Anki) I would like to see updated in Debian and ubuntu.

For this, on a Debian distribution, I created an empty folder 
/home/milchior/packaging/anki-2.1.38/debian
and inside it then tried the command
dch --create -v 2.1.28-1 --package anki

which led to the error message 
> dch: fatal error at line 642:
> Cannot find debian directory!
> Are you in the correct directory?

So either the wiki should be corrected and the error message clarified, or 
there is a bug in this program. Maybe both



-- Package-specific info:

--- /etc/devscripts.conf ---

--- ~/.devscripts ---
Not present

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

Kernel: Linux 4.19.0-13-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Ne peut initialiser 
LC_ALL à la locale par défaut: Aucun fichier ou dossier de ce type
UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=locale: Ne peut initialiser LC_ALL à la 
locale par défaut: Aucun fichier ou dossier de ce type
UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages devscripts depends on:
ii  dpkg-dev  1.19.7
ii  fakeroot  1.23-1
ii  file  1:5.35-4+deb10u1
ii  gnupg 2.2.12-1+deb10u1
ii  gpgv  2.2.12-1+deb10u1
ii  libc6 2.28-10
ii  libfile-homedir-perl  1.004-1
ii  libfile-which-perl1.23-1
ii  libipc-run-perl   20180523.0-1
ii  libmoo-perl   2.003004-2
ii  libwww-perl   6.36-2
ii  patchutils0.3.4-2
ii  perl  5.28.1-6+deb10u1
ii  python3   3.7.3-1
ii  sensible-utils0.0.12
ii  wdiff 1.2.2-2+b1

Versions of packages devscripts recommends:
ii  apt 1.8.2.2
ii  at  3.1.23-1
ii  dctrl-tools 2.24-3
ii  debian-keyring  2019.02.25
ii  dput1.0.3
ii  equivs  2.2.0
ii  libdistro-info-perl 0.21
ii  libdpkg-perl1.19.7
ii  libencode-locale-perl   1.05-1
ii  libgit-wrapper-perl 0.048-1
ii  libgitlab-api-v4-perl   0.16-1
ii  liblist-compare-perl0.53-1
ii  liblwp-protocol-https-perl  6.07-2
ii  libsoap-lite-perl   1.27-1
ii  libstring-shellquote-perl   1.04-1
ii  libtry-tiny-perl0.30-1
ii  liburi-perl 1.76-1
ii  licensecheck3.0.31-3
ii  lintian 2.15.0
ii  man-db  2.8.5-2
ii  patch   2.7.6-3+deb10u1
ii  python3-apt 1.8.4.3
ii  python3-debian  0.1.35
ii  python3-magic   2:0.4.15-2
ii  python3-requests2.21.0-1
ii  python3-unidiff 0.5.4-1
ii  python3-xdg 0.25-5
ii  strace  4.26-0.2
ii  unzip   6.0-23+deb10u1
ii  wget1.20.1-1.1
ii  xz-utils5.2.4-1

Versions of packages devscripts suggests:
pn  adequate 
pn  autopkgtest  
pn  bls-standalone   
ii  build-essential  12.6
pn  check-all-the-things 
pn  cvs-buildpackage 
ii  debhelper12.1.1
pn  devscripts-el
pn  diffoscope   
pn  disorderfs   
pn  dose-extra   
pn  duck 
pn  faketime 
pn  gnuplot  
pn  how-can-i-help   
ii  libauthen-sasl-perl  2.1600-1
pn  libdbd-pg-perl   
pn  libfile-desktopentry-perl
pn  libnet-smtps-perl
pn  libterm-size-perl
ii  libtimedate-perl 2.3000-2+deb10u1
pn  libyaml-syck-perl
ii  mailutils [mailx]1:3.5-4
pn  mozilla-devscripts   
pn  mutt 
ii  openssh-client [ssh-client]  1:7.9p1-10+deb10u2
pn  piuparts 
pn  postgresql-client
pn  quilt
pn  ratt 
pn  reprotest
pn  svn-buildpackage 
pn  w3m  

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "fr_FR.UTF-8",
LC_ALL = (unset),
LC_TIME = "de_DE.UTF-8",
LC_MONETARY = "de_DE.UTF-8",
LC_CTYPE = "C.UTF-8",
LC_ADDRESS = "de_DE.UTF-8",
LC_TELEPHONE = "de_DE.UTF-8",
LC_NAME = "de_DE.UTF-8",
LC_MEASUREMENT = "de_DE.UTF-8",
LC_IDENTIFICATION = "de_DE.UTF-8",
LC_NUMERIC = 

Bug#979473: ITP: golang-gitlab-gitlab-org-labkit -- A minimalist library to provide functionality for Go services at GitLab

[Vipul Kumar]

Package: wnpp
Severity: wishlist
Owner: Vipul Kumar 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: golang-gitlab-gitlab-org-labkit
  Version : 1.2.0-1
  Upstream Author : GitLab B.V.
* URL : https://gitlab.com/gitlab-org/labkit
* License : MIT License
  Programming Lang: Go
  Description : A minimalist library to provide functionality for Go 
services at GitLab.

LabKit is minimalist library to provide functionality for Go services at
GitLab. This library contains following packages:
.
  - Correlation
  Package correlation provides HTTP middlewares for general purpose use
  cases.
  - Log
  Package log provides sensible logging defaults for LabKit.
  - Mask
  Package mask offers the functionality for non-reversible masking of
  sensitive data in the GitLab application.
  - Metrics
  Package metrics is the primary entrypoint into LabKit's metrics
  utilities.
  - Monitoring
  Package monitoring provides a monitoring endpoint and Continuous
  Profiling for Go service processes.
.
LabKit and LabKit-Ruby are intended to provides similar functionality, but uses
the semantics of their respective languages, so they are not intended to
provide identical APIs.

Bug#943676: Re: Sponsor request for 'Open Surge'

[Bruno Kleinert]

Am Dienstag, dem 05.01.2021 um 14:14 -0300 schrieb Alexandre Martins:
> Hi,
> 
> The source code will be compatible with the libraries that are
> currently packaged in Debian.
> 
> We are including in the new version a file that specifies, in a clear
> and organized manner, the copyright information of the artwork
> (authors, licenses):
> 
> https://github.com/alemart/opensurge/blob/master/src/misc/copyright-artwork.csv
> 
> A few files have been changed since the latest release (mostly music),
> and a few more are expected to change in the coming days (mostly
> music). However, most files remain the same. This csv file may thus
> help you save some time.
> 
> Hopefully with these contributions Open Surge 0.5.2.0 can make it for 
> bullseye.
> 
> Alexandre

Hi Alexandre, hi Carlos,

I need to correct myself and unfortunately lower expectations:
opensurge will be a package newly introduced to Debian, so it has to
successfully go through the NEW queue [1] procedure which takes
additional time. I.e., chances are low Open Surge may make it into
bullseye, we need to see how slow or fast things will work out. My bad,
I'm not used to upload to the NEW queue.

@Carlos: I further cleaned up packaging and documented lintian
infos/warnings + according overrides. To save disk space in the
archive, I split opensurge into a small architecture dependent package
opensurge and an architecture independent package opensurge-data. This
should make ftpmasters' lives easier for a smooth NEW queue transition.
Please check the changes for any mistakes.

Cheers,
Bruno

[1] https://ftp-master.debian.org/new.html


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

Bug#978237: xfce4-equake-plugin: FTBFS: build-dependency not installable: xfce4-panel (= 4.14.4-1)

[Jeroen van Aart]

I am working on a fix and expect to release it soon.

Lucas Nussbaum wrote:

Source: xfce4-equake-plugin
Version: 1.3.8.1-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):

+--+
| Install package build dependencies   |
+--+


Setup apt archive
-

Merged Build-Depends: autotools-dev, debhelper (>= 9.0.0), intltool, 
libcurl4-gnutls-dev, libatk1.0-dev, libcairo2-dev, libfontconfig1-dev, 
libfreetype6-dev, libgdk-pixbuf2.0-dev, libglib2.0-dev, libgtk2.0-dev, 
libpango1.0-dev, libxfce4ui-1-dev, libxfce4util-dev, xfce4-panel-dev, 
build-essential, fakeroot
Filtered Build-Depends: autotools-dev, debhelper (>= 9.0.0), intltool, 
libcurl4-gnutls-dev, libatk1.0-dev, libcairo2-dev, libfontconfig1-dev, 
libfreetype6-dev, libgdk-pixbuf2.0-dev, libglib2.0-dev, libgtk2.0-dev, 
libpango1.0-dev, libxfce4ui-1-dev, libxfce4util-dev, xfce4-panel-dev, 
build-essential, fakeroot
dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
'/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
Ign:1 copy:/<>/apt_archive ./ InRelease
Get:2 copy:/<>/apt_archive ./ Release [957 B]
Ign:3 copy:/<>/apt_archive ./ Release.gpg
Get:4 copy:/<>/apt_archive ./ Sources [461 B]
Get:5 copy:/<>/apt_archive ./ Packages [552 B]
Fetched 1970 B in 0s (0 B/s)
Reading package lists...
Reading package lists...

Install main build dependencies (apt-based resolver)


Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xfce4-panel-dev : Depends: xfce4-panel (= 4.14.4-1) but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages.
apt-get failed.


The full build log is available from:
   
http://qa-logs.debian.net/2020/12/26/xfce4-equake-plugin_1.3.8.1-2_unstable.log

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

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.

Bug#979379: ITS: src:gnupg2

[NIIBE Yutaka]

Hello,

On 2021-01-05 +0100, Christoph Biedl  wrote:
> | missing upstream releases,
> 
> Several. Debian has 2.20, uploaded in March. Upstream is at 2.26.

FYI, I tried to build GnuPG 2.2.26-1-of-mine package:

https://salsa.debian.org/gniibe/gnupg2

I did:

  * fetch by 'git fetch '
  * import upstream tar balls by 'gbp import-orig'
  * refresh patches
  * add a line to debian/rules for Windows (building regexp.a).
  * follow the changes of upstream (gpgsplit and symcryptrun).
  * merge pull request for scdaemon configuration
  * add one patch of mine to fix #868550, #972525.

It builds well for me (and works for me).

I have no intention of NMU at all for this work.  As one of upstream
maintainers, I'd like to make sure Debian version of GnuPG works well.
Please note that the patch for #868550, #972525 is a backport from
master, which is only for Debian (it won't be in 2.2 series of
upstream).

I hope my changes above help Debian GnuPG packaging.
-- 

Bug#979392: RFS: libfilezilla/0.26.0-1 [Team] -- build high-performing platform-independent programs (runtime lib)

[Philip Wyett]

On Wed, 2021-01-06 at 13:27 +0100, Adam Borowski wrote:
> On Wed, Jan 06, 2021 at 04:15:28AM +, Philip Wyett wrote:
> >  * Package name: libfilezilla
> >Version : 0.26.0-1
> > 
> > It builds those binary packages:
> > 
> >   libfilezilla0 - build high-performing platform-independent
> > programs
> > (runtime lib)
> >   libfilezilla-dev - build high-performing platform-independent
> > programs (development)
> 
> The soname has changed, you'd need to rename the runtime package to
> libfilezilla1.
> 
> 
> Meow!

This should be corrected in the current upload.

Regards

Phil

-- 
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


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

Bug#922405: pocl : FTBFS on sid - testsuite has failed on ppc64el arch

[Andreas Beckmann]

On 12/21/20 12:12 PM, Michel Le Bihan wrote:
> Hello,
> 
> This might be fixed in upstream release 1.6:
> http://portablecl.org/pocl-1.6.html

The situation has improved, but the issue is not yet fixed:

Andreas

= 1.5-7 =
67% tests passed, 45 tests failed out of 137

Label Time Summary:
EinsteinToolkit=  26.19 sec*proc (2 tests)
cuda   =  46.80 sec*proc (50 tests)
hsa=   4.75 sec*proc (4 tests)
hsa-native = 170.08 sec*proc (88 tests)
internal   = 187.70 sec*proc (125 tests)
kernel = 115.75 sec*proc (35 tests)
matrix =   3.40 sec*proc (2 tests)
regression =  66.01 sec*proc (50 tests)
runtime=  17.52 sec*proc (21 tests)
tce=   9.61 sec*proc (9 tests)
workgroup  =  15.71 sec*proc (13 tests)

Total Test time (real) =  79.69 sec

The following tests FAILED:
  2 - kernel/test_as_type (Failed)
  3 - kernel/test_convert_type_1 (Failed)
  4 - kernel/test_convert_type_2 (Failed)
  5 - kernel/test_convert_type_4 (Failed)
  6 - kernel/test_convert_type_8 (Failed)
  7 - kernel/test_convert_type_16 (Failed)
  8 - kernel/test_bitselect (Failed)
  9 - kernel/test_hadd_loopvec (Failed)
 10 - kernel/test_hadd_loops (Failed)
 11 - kernel/test_min_max (Failed)
 12 - kernel/test_length_distance (Failed)
 13 - kernel/test_fmin_fmax_fma (Failed)
 14 - kernel/test_local_struct_array (Failed)
 15 - kernel/test_convert_sat_regression (Failed)
 16 - kernel/test_rotate (Failed)
 17 - kernel/test_fabs (Failed)
 18 - kernel/test_copy_signbit (Failed)
 19 - kernel/test_ilogb (Failed)
 20 - kernel/test_ldexp (Failed)
 21 - kernel/test_isnan (Failed)
 22 - kernel/test_short16 (Failed)
 23 - kernel/test_frexp_modf (Failed)
 24 - kernel/test_sampler_address_clamp (Failed)
 25 - kernel/test_image_query_funcs (Failed)
 26 - kernel/test_shuffle_char (Failed)
 27 - kernel/test_shuffle_short (Failed)
 28 - kernel/test_shuffle_ushort (Failed)
 29 - kernel/test_shuffle_int (Failed)
 30 - kernel/test_shuffle_uint (Failed)
 31 - kernel/test_shuffle_float (Failed)
 32 - kernel/test_shuffle_long (Failed)
 33 - kernel/test_shuffle_ulong (Failed)
 34 - kernel/test_printf (Failed)
 35 - kernel/test_sizeof_uint (Failed)
 36 - kernel/test_shuffle_double (Failed)
 38 - regression/test_issue_445 (Failed)
 81 - regression/clSetKernelArg_overwriting_the_previous_kernel's_args
(Failed)
 83 -
regression/case_with_multiple_variable_length_loops_and_a_barrier_in_one
(Failed)
 84 - regression/autolocals_in_constexprs (Failed)
 86 - regression/vector_kernel_arguments (Failed)
 92 - runtime/test_kernel_cache_includes (Failed)
 93 - runtime/clFinish (Failed)
100 - runtime/clSetEventCallback (Failed)
102 - runtime/clCreateKernelsInProgram (Failed)
103 - runtime/clCreateSubDevices (SEGFAULT)
==

= 1.6-3 =
84% tests passed, 23 tests failed out of 141

Label Time Summary:
EinsteinToolkit=  25.89 sec*proc (2 tests)
cuda   =  42.55 sec*proc (51 tests)
hsa=   4.34 sec*proc (4 tests)
hsa-native = 175.24 sec*proc (88 tests)
internal   = 194.46 sec*proc (128 tests)
kernel = 123.17 sec*proc (35 tests)
matrix =   4.99 sec*proc (2 tests)
regression =  62.54 sec*proc (51 tests)
runtime=  18.33 sec*proc (23 tests)
tce=   9.36 sec*proc (9 tests)
workgroup  =  13.94 sec*proc (13 tests)

Total Test time (real) =  81.37 sec

The following tests FAILED:
  4 - kernel/test_convert_type_2 (Failed)
  5 - kernel/test_convert_type_4 (Failed)
  8 - kernel/test_bitselect (Failed)
  9 - kernel/test_hadd_loopvec (Failed)
 10 - kernel/test_hadd_loops (Failed)
 16 - kernel/test_rotate (Failed)
 17 - kernel/test_fabs (Failed)
 18 - kernel/test_copy_signbit (Failed)
 19 - kernel/test_ilogb (Failed)
 20 - kernel/test_ldexp (Failed)
 21 - kernel/test_isnan (Failed)
 25 - kernel/test_image_query_funcs (Failed)
 26 - kernel/test_shuffle_char (Failed)
 27 - kernel/test_shuffle_short (Failed)
 28 - kernel/test_shuffle_ushort (Failed)
 29 - kernel/test_shuffle_int (Failed)
 30 - kernel/test_shuffle_uint (Failed)
 31 - kernel/test_shuffle_float (Failed)
 32 - kernel/test_shuffle_long (Failed)
 33 - kernel/test_shuffle_ulong (Failed)
 34 - kernel/test_printf (Failed)
 36 - kernel/test_shuffle_double (Failed)
 88 - regression/vector_kernel_arguments (Failed)
==

Andreas

Bug#979472: ITP: golang-github-chris-ramon-douceur -- A simple CSS parser and inliner in Go

[Federico Grau]

Package: wnpp
Severity: wishlist
Owner: Federico Grau 

* Package name: golang-github-chris-ramon-douceur
  Version : 0.2.0-1
  Upstream Author : Chris Ramón
* URL : https://github.com/chris-ramon/douceur
* License : MIT
  Programming Lang: Go
  Description : Simple CSS parser and inliner in Go

 Simple CSS parser and inliner in Golang.
 .
 Based on github-aymerick-douceur, adding column and line support.
 .
 Original parser is vaguely inspired by CSS Syntax Module Level 3
 (http://www.w3.org/TR/css3-syntax) and corresponding JS parser
 (https://github.com/tabatkins/parse-css).
 .
 Inliner only parses CSS defined in HTML document, it DOES NOT fetch
 external stylesheets (for now).
 .
 Inliner inserts additional attributes when possible, for example:



This package is a dependency to build golang-github-microcosm-cc-bluemonday
v1.0.4, which in turn is a dependency for pat (#877030).


signature.asc
Description: PGP signature

Bug#979441: digikam: Crashes when detecting faces

[Steven Robbins]

On Wednesday, January 6, 2021 12:43:52 P.M. CST R. Lemos wrote:
> Package: digikam
> Version: 4:7.1.0-1+b1
> Severity: normal
> 
> The program crashes with message
> 
> > digikam: symbol lookup error: /usr/lib/digikam/libdigikamcore.so.7.1.0:
> > undefined symbol: _ZN2cv3dnn14dnn4_v202009083NetC1Ev
> Steps to reproduce:

[  ]

Confirmed.  I can reproduce same crash with provided steps.
-Steve


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

Bug#979471: ITP: golang-github-aymerick-douceur -- Simple CSS parser and inliner in Go

[Federico Grau]

Package: wnpp
Severity: wishlist
Owner: Federico Grau 

* Package name: golang-github-aymerick-douceur
  Version : 0.2.0-1
  Upstream Author : Aymerick
* URL : https://github.com/aymerick/douceur
* License : MIT
  Programming Lang: Go
  Description : Simple CSS parser and inliner in Go

 Simple CSS parser and inliner in Golang.
 .
 Parser is vaguely inspired by CSS Syntax Module Level 3
 (http://www.w3.org/TR/css3-syntax) and corresponding JS parser
 (https://github.com/tabatkins/parse-css).
 .
 Inliner only parses CSS defined in an HTML document, it DOES NOT fetch
 external stylesheets (for now).
 .
 Inliner inserts additional attributes when possible.



This package is a dependency to build golang-github-chris-ramon-douceur, which
in an indirect dependency for pat (#877030).


signature.asc
Description: PGP signature

Bug#976113: P.S. Re: RFS Review for Hydrogen

[Nicholas D Steeves]

Hi Ross,

I just noticed that the package of mentors was out of date, so I have
built and uploaded as fresh copy.  When consulting git, please take care
to look at the rfs-976113-rebase branch.  The commit intended for
release is 3bbf783 on this branch, and intended version can be
identified on mentors with the changelog footer "Wed, 06 Jan 2021
21:17:22".

It may take a few minutes for mentors to pick up the new package, but we
should be good to go after that :-)

Thank you,
Nicholas


signature.asc
Description: PGP signature

Bug#972968: linux-image-5.9.0-1-amd64: Bluetooth stopped working

[Paul Wise]

On Mon, 26 Oct 2020 18:59:16 +0100 Christian Britz  wrote:

> after upgrading my Debian testing installation to kernel 5.9.1,
> my bluetooth mouse does not work anymore.

The patch fixing this will be released in v5.10.6 and v5.11-rc1,
see the upstream bug for details:

https://bugzilla.kernel.org/show_bug.cgi?id=210279

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#979470: ITP: eiskaltdcpp-web -- Simple Web UI for eiskaltdcpp-daemon

[Boris Pek]

Package: wnpp
Severity: wishlist
Owner: Boris Pek 
X-Debbugs-Cc: tehn...@debian.org

* Package name: eiskaltdcpp-web
  Version : 1.0.1
  Upstream Contact: Boris Pek 
* URL : https://github.com/eiskaltdcpp/eiskaltdcpp-web
* License : GPL-3+
  Programming Lang: JavaScript, HTML
  Description : EiskaltDC++ Web UI

Official Web User Interface for eiskaltdcpp-daemon. It is designed for using on
embedded devices (for example in NAS) in user home network.

Features:
* Searching of files and directories
* List of current/queued downloads
* Status of connected hubs and basic statistics

Deb packages:
https://github.com/eiskaltdcpp/eiskaltdcpp-web-devel-debian

Bug#979145: RM: xfce4-equake-plugin/1.3.8.1-2+b2

[Jeroen van Aart]

I am working on a fix, I hope to have it available soon.

Yves-Alexis Perez wrote:

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
X-Debbugs-Cc: andr...@e-quake.org

Hi,
xfce4-equake-plugin is not compatible with the 4.16 release of the Xfce
desktop environement, and thus FTBFS in unstable right now, and prevents
migration of the xfce4-panel package (and xfce4 metapckage). There's an
open bug about that (#978237) as well as a request for the package to be
ported to latest library (#977626) but the package seems unmaintained
upstream and in Debian (it's not under the pkg-xfce team umbrella).

Right now I think the most sensible decision would be to remove it from
testing and let xfce4-panel migrate. Maybe Jeroen could chime in but I'm
afraid he's not very active at the moment.

Regards,

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

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

Bug#979355: src:sphinx-rtd-theme: embeds several Sass libraries that should be packaged separately

[Jonas Smedegaard]

Quoting Dmitry Shachnev (2021-01-06 18:36:19)
> On Tue, Jan 05, 2021 at 09:01:40PM +0100, Jonas Smedegaard wrote:
> > > Yes, it cannot use the newer release because Wyrm is incompatible 
> > > with it:
> > >
> > > https://github.com/snide/wyrm/issues/12
> >
> > That one concretely seems easy fixable - but that's easy to say, I 
> > know :-)
> 
> I just noticed that you already packaged all three dependencies and 
> uploaded them to NEW. Thanks a lot for that — when you suggested me to 
> file RFPs I definitely did not expect such speed :)

That was the easy part.  Getting them into testing before the freeze is 
the next challenge, and finding time while busy with a pile of other 
freeze-related work to patch things up for sphinx-rtd-theme is the 
parder parts...


> Now, you say that it will be easy to port Wyrm to new Bourbon. 
> Actually the current construction is quite fragile because of 
> inter-dependencies: not only Wyrm needs to be switched to new Bourbon 
> or Neat, but also sphinx-rtd-theme itself at the same time.

Well, I only wrote that it _seems_ easy ;-)


> My knowledge of SCSS is minimal so I can only say that patches are 
> welcome.

I do have some experience with Sass (and even wrote a Sass library), but 
it might still not be sensible to patch things up for sphinx-rtd-theme - 
for now I am only preparing those packages for general use, I am still 
not sure they are suitable for sphinx-rtd-theme specifically.


 - Jonas

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

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

signature.asc
Description: signature

Bug#979180: Git twinkle compiles

[ael]

I have managed to compile the latest git version of twinkle by omitting
a few codecs. 

I used
cmake .. -DWITH_ALSA=On -DWITH_SPEEX=On -DWITH_ILBC=Off -DWITH_ZRTP=Off 
-DWITH_G729=Off -DWITH_QT5=On

This seems to have produced a working twinkle and so far there have been
no problems with ALSA. But I have done very little testing so far.

So it looks as if it should be possible to get a working version in
Debian.

Bug#973467: vmdb2 tries to install grub-pc or grub-efi-amd64 on arm64 and does not work on arm64

[Ryutaroh Matsumoto]

Hi Christian,
Thank you very much for your work!.

> The updated packaging is in my fork on Salsa:
> https://salsa.debian.org/ckk/vmdb2

I have sent an MR regarding
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975024

I have looked at
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=vmdb2;dist=unstable
but there seems no other bug that can be easily fixed by packaging...

> I'll try to get some tests done over the weekend. Ryutaroh, given your
> experience, if you get a chance to look at ARM side of this, too, I'd be
> immensely grateful :-)

I will see its behavior on building an arm image by the start of the next week.

Best regards, Ryutaroh

Bug#979326: ITP: crust -- SCP firmware for sunxi SoCs

[Jonas Smedegaard]

Hi Arnaud,

Quoting Arnaud Ferraris (2021-01-07 00:17:49)
> Le 05/01/2021 à 12:35, Jonas Smedegaard a écrit :
> > * Package name: crust
[...]
> > Personally I own an Olimex TERES-I DIY laptop
> > and several Olimex arm64 boards,
> > but would prefer to maintain this package as a team-effort
> > with owners of other Allwinner boards involved as well.
> 
> As I own (and develop for) a PinePhone and PineTab, I'll gladly 
> co-maintain this package with you.

Great!

I propose that we use the Tinker team as platform for this - if fine 
with you then please subscribe to the mailinglist and join the irc 
channel as listed at https://wiki.debian.org/Teams/Tinker :-)


 - Jonas

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

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

signature.asc
Description: signature

Bug#979469: missing dependency on (surprise!) golang-docker-credential-helpers, renders basic "pull" non-functional

[Yaroslav Halchenko]

Package: python3-docker
Version: 4.1.0-1.2
Severity: important

"minimal" example:

$> python3 -c 'import docker as d; c = d.from_env(); 
c.images.pull("debian:latest")'
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/docker/models/images.py", line 
444, in pull
pull_log = self.client.api.pull(
  File "/usr/lib/python3/dist-packages/docker/api/image.py", line 396, 
in pull
header = auth.get_config_header(self, registry)
  File "/usr/lib/python3/dist-packages/docker/auth.py", line 47, in 
get_config_header
authcfg = resolve_authconfig(
  File "/usr/lib/python3/dist-packages/docker/auth.py", line 324, in 
resolve_authconfig
return authconfig.resolve_authconfig(registry)
  File "/usr/lib/python3/dist-packages/docker/auth.py", line 235, in 
resolve_authconfig
cfg = self._resolve_authconfig_credstore(registry, store_name)
  File "/usr/lib/python3/dist-packages/docker/auth.py", line 262, in 
_resolve_authconfig_credstore
store = self._get_store_instance(credstore_name)
  File "/usr/lib/python3/dist-packages/docker/auth.py", line 286, in 
_get_store_instance
self._stores[name] = credentials.Store(
  File "/usr/lib/python3/dist-packages/docker/credentials/store.py", 
line 23, in __init__
raise errors.InitializationError(
docker.credentials.errors.InitializationError: 
docker-credential-secretservice not installed or not available in PATH

while image is "legit" and available:

$> docker pull debian:latest
latest: Pulling from library/debian
Digest: 
sha256:22d4552b9f96fd0ea943cb846d58b069d4df297673636055a3d984b3ccac6a28
Status: Downloaded newer image for debian:latest
docker.io/library/debian:latest

initially discovered while trying docker-compose up, e.g.:

$> git clone https://github.com/datalad/datalad-registry && cd 
datalad-registry && docker-compose up
Cloning into 'datalad-registry'...
remote: Enumerating objects: 368, done.
remote: Counting objects: 100% (368/368), done.
remote: Compressing objects: 100% (170/170), done.
remote: Total 368 (delta 223), reused 322 (delta 177), pack-reused 0
Receiving objects: 100% (368/368), 54.58 KiB | 1.76 MiB/s, done.
Resolving deltas: 100% (223/223), done.
COPYING  Dockerfile  README.md  datalad_registry/  
docker-compose.broker.yml  docker-compose.yml  docs/  flask*  pyproject.toml  
setup.cfg  setup.py  up*
Pulling broker (rabbitmq:3-alpine)...
Traceback (most recent call last):
  File "/usr/bin/docker-compose", line 11, in 
load_entry_point('docker-compose==1.25.0', 'console_scripts', 
'docker-compose')()
   trim 
  File "/usr/lib/python3/dist-packages/docker/auth.py", line 286, in 
_get_store_instance
self._stores[name] = credentials.Store(
  File "/usr/lib/python3/dist-packages/docker/credentials/store.py", 
line 23, in __init__
raise errors.InitializationError(
docker.credentials.errors.InitializationError: 
docker-credential-secretservice not installed or not available in PATH

after I found that docker-credential-secretservice  within
golang-docker-credential-helpers and apt-get installed that package, pull
seems to work:

$> python3 -c 'import docker as d; c = d.from_env(); 
print(c.images.pull("debian:latest"))' 



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 
'unstable-debug'), (100, 'stable-updates'), (100, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-4-amd64 (SMP w/12 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 python3-docker depends on:
ii  python33.9.0-4
ii  python3-distutils  3.8.6-1
ii  python3-requests   2.24.0+dfsg-1
ii  python3-six1.15.0-2
ii  python3-websocket  0.57.0-1

python3-docker recommends no packages.

python3-docker suggests no packages.

-- debconf-show failed

Bug#979468: RFS: gdu/2.2.0 [ITP]

[Daniel Milde]

Package: sponsorship-requests
Severity: normal

Dear developers,
I am looking for a sponsor for my package "gdu":

* Package name : gdu
Version : 2.2.0
Upstream Author : Daniel Milde 
* URL : https://github.com/dundee/gdu
* License : MIT
* Vcs : https://github.com/dundee/gdu.git
Section : Utilities

It builds those binary packages:

gdu - Pretty fast disk usage analyzer written in Go

It's a minimalist command line disk usage analyzer, heavily inspired by 
ncdu, but much faster, because it utilizes all CPU cores.


More info: https://github.com/dundee/gdu

You can download the source package from:

https://github.com/dundee/gdu/releases/download/v2.2.0/gdu_2.2.0-0.dsc
https://github.com/dundee/gdu/releases/download/v2.2.0/gdu_2.2.0-0.tar.gz

Best regards
Daniel

Bug#979213: raspi-firmware: Please add option to pin kernel/initramfs version

[Diederik de Haas]

Hi Gunnar,

On woensdag 6 januari 2021 20:53:57 CET Gunnar Wolf wrote:
> I understand the need for specifying a given kernel version. First of
> all, let me suggest looking into a more complete solution, like using
> u-boot as a second stage bootloader; IIRC, you can install the uboot
> package, and load it instead of jumping straight into Linux, allowing
> for much greater boot-time flexibility.

I have to learn more about u-boot myself as I do get the impression it's quite 
powerful.
I also think what I want should be doable without u-boot ...
 
> But, I think the bug should be trivially fixable as it is -- Or maybe
> I'm not understanding something right? /etc/default/raspi-firmware
> includes a KERNEL configuration key:
> ...
> #KERNEL="auto"
> 
> If you change it to any other filename existing under /boot/firmware,
> the generated config.txt file will specify it as the kernel instead of
> the latest Debian-packaged kernel.

I either overlooked that option or I didn't (really) understand it.
A quick test did indicate that it is what I was looking for, thanks!

But, the execution didn't go correctly or I don't understand how to use it 
correctly.

$ sudo vim /etc/default/raspi-firmware

$ sudo update-initramfs -u 
update-initramfs: Generating /boot/initrd.img-5.10.0-1-arm64
latest_kernel: '/boot/vmlinuz-5.10.0-1-arm64'
latest_initrd: '/boot/initrd.img-5.10.0-1-arm64'
DPKG_MAINTSCRIPT_ARCH: ''
arch: 'arm64'
$ cat /boot/firmware/config.txt 
# Switch the CPU from ARMv7 into ARMv8 (aarch64) mode
arm_64bit=1

enable_uart=1
upstream_kernel=1

kernel=vmlinuz-5.9.0-5-arm64
# For details on the initramfs directive, see
# https://www.raspberrypi.org/forums/viewtopic.php?f=63=10532
initramfs

Hmm initramfs parameter is specified, but has an empty value
/me finds out there's also and INITRAMFS parameter
$ sudo vim /etc/default/raspi-firmware

$ sudo update-initramfs -u 
update-initramfs: Generating /boot/initrd.img-5.10.0-1-arm64
latest_kernel: '/boot/vmlinuz-5.10.0-1-arm64'
latest_initrd: '/boot/initrd.img-5.10.0-1-arm64'
DPKG_MAINTSCRIPT_ARCH: ''
arch: 'arm64'
diederik@rpi-mpd:~$ grep 5.9.0-5-arm64 /etc/default/raspi-firmware 
KERNEL="vmlinuz-5.9.0-5-arm64"
INITRAMFS="initrd.img-5.9.0-5-arm64"
diederik@rpi-mpd:~$ cat /boot/firmware/config.txt 
# Switch the CPU from ARMv7 into ARMv8 (aarch64) mode
arm_64bit=1

enable_uart=1
upstream_kernel=1

kernel=vmlinuz-5.9.0-5-arm64
# For details on the initramfs directive, see
# https://www.raspberrypi.org/forums/viewtopic.php?f=63=10532
initramfs

initramfs parameter is still empty.
So either I didn't do it correctly, or there is a bug in its implementation

> I am tagging this bug as closed, as I believe this is a solution for
> your needs, but of course, feel free to reopen (just explain why! ;-) )
> in case you don't agree with my assessment.

It looks like the functionality is there, so your assessment seems correct.
But either the implementation of the 'INITRAMFS' parameter is incorrect or the 
help text/comments aren't clear enough. It may be helpful to also mention/
point to this parameter in the comments of the KERNEL parameter as I'm 
guessing 'my' use case would be the most used/obvious use case.

I haven't rebooted, but I'm guessing that booting would fail.

I'm not sure what to do with the bug status (reopen?/clone?/retitle?), so I'll 
leave it up to you to do what you think is best.

Cheers,
  Diederik

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

Bug#979462: aplus-fsf: FTBFS against glibc 2.32

[Neil Roeth]

On 1/6/21 5:11 PM, Logan Rosen wrote:

Package: aplus-fsf
Version: 4.22.1-10.1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com

Hi,

aplus-fsf currently FTBFS against glibc 2.32, which is used in the
development release of Ubuntu (and should be in Debian soon).

This is because it has some improperly guarded usage of sys_errlist
instead of strerror().

In Ubuntu, the attached patch was applied to achieve the following:

   * Fix FTBFS against glibc 2.32 by using strerror() instead of sys_errlist.

Thanks for considering the patch.

Logan


Thanks, Logan.

This works with glibc 2.31.  I will upload a new package once 2.32 is in 
Debian unstable.


Neil

Bug#979463: crash when run for remote DISPLAY

[Andreas Ronnquist]

On Wed, 6 Jan 2021 23:13:21 +0100 Eduard Bloch  wrote:
> Package: geeqie
> Version: 1:1.6-3
> Severity: important
> 
> Just what the description says. You start geeqie and the only
> parameter is a picture file (regular JPG).
> 
> Result: application crashes (SIGSEGV). gdb (with symbols loaded) does
> not reveal much:
> 

Thanks for your report. In this case I believe the fact that you are
running remote isn't a factor of the crash - the backtrace is identical
to what some people report in a upstream report with activity recently.

https://github.com/BestImageViewer/geeqie/issues/829

I have set this bug as forwarded to that upstream one. It looks like it
is a deal of reverting one commit, I'll see what upstream does, and
either get a new potential upstream or cherry-pick a patch when one
comes.

/Andreas Rönnquist
gus...@debian.org

Bug#973467: vmdb2 tries to install grub-pc or grub-efi-amd64 on arm64 and does not work on arm64

[Christian Kastner]

Hi Ryutaroh, Gunnar,

On 01.01.21 05:27, Ryutaroh Matsumoto wrote:
> I wonder if you have available time to package vmdb 0.21 for Debian Bullsyeye
> before its deadline.

I went ahead and took a stab at updating the package. There were some
minor tweaks to the build process, but the first result looks fine. I
did a simple test of basic functionality (create a simple image) and it
booted fine.

I did not yet test any advanced features; most importantly, I did not
yet test the features for the newly supported architectures.


The updated packaging is in my fork on Salsa:

https://salsa.debian.org/ckk/vmdb2

Gunnar, if you're satisfied with this, let me know and I'll file an MR
(or merge myself, if you prefer).


I uploaded a source package and amd64 binary package to my own personal
repo:

https://apt.kvr.at/debian/pool/main/v/vmdb2/

I'll try to get some tests done over the weekend. Ryutaroh, given your
experience, if you get a chance to look at ARM side of this, too, I'd be
immensely grateful :-)

Best,
Christian

Bug#979467: flightgear: new fgfs-compositor binary is not built

[Fox-Three]

Package: flightgear
Version: 1:2020.3.5+dfsg-1
Severity: normal
X-Debbugs-Cc: three@yandex.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***
Flightgear now includes a new Compositor for multi-pass rendering.
This is supposed to be used by running a fgfs-compositor binary.

It seems this is not built for the debian package (using flightgear 2020.3.5 on 
bullseye)


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

Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages flightgear depends on:
ii  flightgear-data-all 1:2020.3.4+dfsg-1
ii  libc6   2.31-6
ii  libcurl3-gnutls 7.72.0-1
ii  libdbus-1-3 1.12.20-1
ii  libexpat1   2.2.10-1
ii  libflite1   2.2-2
ii  libgcc-s1   10.2.1-3
ii  libgl1  1.3.2-1
ii  libgsm1 1.0.18-2
ii  libhtsengine1   1.10-4
ii  libopenal1  1:1.19.1-2
ii  libopenscenegraph1613.6.5+dfsg1-7+b1
ii  libopenthreads213.6.5+dfsg1-7+b1
ii  libplib11.8.5-8
ii  libqt5core5a5.15.2+dfsg-2
ii  libqt5gui5  5.15.2+dfsg-2
ii  libqt5network5  5.15.2+dfsg-2
ii  libqt5qml5  5.15.2+dfsg-2
ii  libqt5quick55.15.2+dfsg-2
ii  libqt5widgets5  5.15.2+dfsg-2
ii  libspeex1   1.2~rc1.2-1.1
ii  libspeexdsp11.2~rc1.2-1.1
ii  libsqlite3-03.34.0-1
ii  libstdc++6  10.2.1-3
ii  libudev1247.1-3+deb11u1
ii  libudns00.4-1+b1
ii  libx11-62:1.6.12-1
ii  qml-module-qtquick-window2  5.15.2+dfsg-2
ii  qml-module-qtquick2 5.15.2+dfsg-2
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages flightgear recommends:
ii  flightgear-phi  2018.1.1+dfsg1-1.1

flightgear suggests no packages.

-- no debconf information

Bug#979326: ITP: crust -- SCP firmware for sunxi SoCs

[Arnaud Ferraris]

Hi Jonas,

Le 05/01/2021 à 12:35, Jonas Smedegaard a écrit :

Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: crust
  Version : 0.3
  Upstream Author : Samuel Holland 
* URL : https://github.com/crust-firmware/crust
* License : BSD-1-clause and BSD-3-clause and Expat and GPL-2
  Programming Lang: C
  Description : SCP firmware for sunxi SoCs

 The crust is the lowest-level component of a delicious fruit pie.
 Similarly, Crust is the lowest-level firmware component
 that runs on $FRUIT (Banana, Orange, Lichee) Pi single-board computers
 and other Allwinner-based devices,
 such as the Pine64 Pinebook and PinePhone.
 .
 Crust improves battery life and thermal performance
 by implementing a deep sleep state.
 During deep sleep,
 the CPU cores, the DRAM controller, and most onboard peripherals
 are powered down, reducing power consumption by 80% or more
 compared to an idle device.
 On boards without a PMIC,
 Crust is also responsible
 for orderly power-off and power-on of the device.
 .
 For this to work,
 Crust runs outside the main CPU and DRAM,
 on a dedicated always-on microprocessor
 called a System Control Processor (SCP).
 Crust is designed to run on a specific SCP implementation,
 Allwinner's AR100.

This package requires a gcc cross-compiler for or1k (see bug#979323)
and may also require patches to linux and u-boot
(but possibly those are optional for an added power consumption).

Personally I own an Olimex TERES-I DIY laptop
and several Olimex arm64 boards,
but would prefer to maintain this package as a team-effort
with owners of other Allwinner boards involved as well.


As I own (and develop for) a PinePhone and PineTab, I'll gladly 
co-maintain this package with you.


Cheers,
Arnaud

Bug#979466: dh-sysuser: Creating user before "postinst" is executed?

[Lars Kruse]

Package: dh-sysuser
Version: 1.3.5
Severity: wishlist

Dear Maintainer,

I would like to use "dh-sysuser" in order to clean up my prerm/postinst
scripts.

But I am struggling to apply dh-sysuser in the context of the following
postinst script:
 
https://git.hack-hro.de/grouprise/grouprise/-/blob/master/debian/grouprise.postinst#L25

A few actions in that specific postinst script rely on the existence of
the user account (e.g. chown for directories).
Thus I would need to move the `#DEBHELPER#` marker to the top of the
postinst script.  But this would lead to related services being
restarted (via the other debhelper snippets) before the directory
permissions are configured.

Maybe it would be desirable to allow dh-sysuser to inject its snippet
into "preinst" instead of "postinst"?

Or maybe my postinst script is just not well designed?

Thank you for your time!

Cheers,
Lars

Bug#979180: Twinkle

[ael]

I have attempted to compile a newer version of twinkle, but
libzrtpccp has been removed from testing which is needed.
I hope that I can find or compile a version of that which will enable
further progress.

Bug#977993: Looking for a sponsor for sfizz

[Olivier Humbert]

Hi all

Just letting you know that I updated the package on mentors (see 
https://mentors.debian.net/package/sfizz/ ) with a working watch file 
now.


Hope it will retain the attention of a DD which will review it in order 
to ship sfizz in bullseye.


Cheers,
Olivier

Bug#979464: ITP: qbrz -- Qt frontend for breezy

[Jelmer Vernooij]

Package: wnpp
Severity: wishlist
Owner: Jelmer Vernooij 
X-Debbugs-Cc: debian-de...@lists.debian.org, breezy-c...@googlegroups.com

* Package name: qbrz
  Version : 0.1
  Upstream Author : RJL situp  and qbzr authors
* URL : https://launchpad.net/qbrz
* License : GPL
  Programming Lang: PYthon
  Description : Qt frontend for breezy

QBrz is a cross platform, Qt-based front-end for Breezy, providing GUI
applications for many core breezy commands. In addition, it provides several
special dialogs and helper commands. Equivalents for core breezy commands have
the same names as CLI commands but with a prefix of "q".

Bug#976112: Overwriting with random data message truncated

[Steve McIntyre]

Hi Matthew,

Thanks for the bug report!

On Sun, Nov 29, 2020 at 08:27:09PM +, Matthew Wilcox wrote:
>Package: debian-installer
>Version: 2020-11-23
>
>When installing on an NVMe device, the message
>
>"The installer is now overwriting /dev/nvme0n1p3 with random data to prevent 
>meta-information leaks from "
>
>is truncated in the graphical installer.
>
>I'd suggest just s/The installer is now o/O/

Nod, that would make sense I think. There's probably more effort in
co-ordinating updating translations. :-)

>Also, it takes a very long time to write a terabyte of random data.
>I suspect you can't do much about that though (... use RDRAND directly?).

And as we discussed later, there's a separate bug for the performance
issue. I'll look at that next.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"The problem with defending the purity of the English language is that
 English is about as pure as a cribhouse whore. We don't just borrow words; on
 occasion, English has pursued other languages down alleyways to beat them
 unconscious and rifle their pockets for new vocabulary."  -- James D. Nicoll

Bug#978107: gajim: Crashes when video preview is turned off in settings dialog window

[Martin]

Control: tags -1 + upstream

In the Gajim MUC, I was pointed to this bug report of 2020-06-29:
https://dev.gajim.org/gajim/gajim/-/issues/10158
Which again points to a MESA bug report one of 2020-05-22:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3029

Bug#966808: flightgear: new dependency: qml-module-qtqml

[Markus Wanner]

Control: tags -1 +moreinfo

Hi,

thanks for filing a bug report with the Debian flightgear package.

On 8/2/20 5:12 PM, attila wrote:

The GUI of the sim requires a new package called qml-module-qtqml, without it 
the interface/sim is unusable.
Please add it as dependency.


I suppose you mean the `fgfs --launcher` GUI.  Flightgear depends on the 
following two qml modules already:


 * qml-module-qtquick-window2
 * qml-module-qtquick2

I cannot find a package `qml-module-qtqml` nor can I reproduce the bug. 
 With 2020.3.5+dfsg-1, the launcher seems to work fine for me.


Can you provide more details, please?

Regards

Markus

Bug#977143: libtorrent-rasterbar10: Python argument types in torrent_handle.move_storage(torrent_handle, str) did not match C++ signature

[Braiam]

Package: python3-libtorrent
Version: 1.2.9-0.2+b2
Tags: patch

This also affects python3-libtorrent and therefore deluged.

There is a patch upstream already merged[1] which I include
a quilt patch of.

[1]: 
https://github.com/arvidn/libtorrent/commit/386596aa88a19dcba3d4f5925dbce3c517065ea2

-- 
Braiam
fix regression in python binding for move_storage()
--- a/bindings/python/src/converters.cpp
+++ b/bindings/python/src/converters.cpp
@@ -23,6 +23,7 @@
 #include "libtorrent/peer_class.hpp"
 #include "libtorrent/pex_flags.hpp"
 #include "libtorrent/string_view.hpp"
+#include "libtorrent/storage_defs.hpp"
 #include 
 #include 
 
@@ -342,6 +343,30 @@
 }
 };
 
+template
+struct to_enum_class
+{
+   using underlying_type = typename std::underlying_type::type;
+
+   to_enum_class()
+   {
+converter::registry::push_back(
+, , type_id()
+);
+}
+
+static void* convertible(PyObject* x)
+{
+return PyNumber_Check(x) ? x : nullptr;
+}
+
+static void construct(PyObject* x, converter::rvalue_from_python_stage1_data* data)
+{
+void* storage = ((converter::rvalue_from_python_storage*)data)->storage.bytes;
+data->convertible = new (storage) T(static_cast(static_cast(extract(object(borrowed(x));
+}
+};
+
 template
 struct from_bitfield_flag
 {
@@ -495,6 +520,7 @@
 to_strong_typedef();
 to_strong_typedef();
 to_strong_typedef();
+to_enum_class();
 to_bitfield_flag();
 to_bitfield_flag();
 to_bitfield_flag();

Bug#978107: gajim: Crashes when video preview is turned off in settings dialog window

[Martin]

Control: retitle -1 gajim: Crashes on wayland when video preview is turned off 
in settings dialog window

I just tried on sway and confirm the crash!

Bug#979463: crash when run for remote DISPLAY

[Eduard Bloch]

Package: geeqie
Version: 1:1.6-3
Severity: important

Just what the description says. You start geeqie and the only parameter
is a picture file (regular JPG).

Result: application crashes (SIGSEGV). gdb (with symbols loaded) does
not reveal much:

(gdb) bt
#0  0x7fc0596bec60 in  ()
#1  0x7fc0680c72a2 in XGetErrorText () at 
/usr/lib/x86_64-linux-gnu/libX11.so.6
#2  0x7fc068e89abf in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#3  0x7fc068e96f43 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#4  0x7fc0680e936b in _XError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
#5  0x7fc0680e6197 in  () at /usr/lib/x86_64-linux-gnu/libX11.so.6
#6  0x7fc0680e6235 in  () at /usr/lib/x86_64-linux-gnu/libX11.so.6
#7  0x7fc0680e6b7a in _XEventsQueued () at 
/usr/lib/x86_64-linux-gnu/libX11.so.6
#8  0x7fc0680e9a85 in _XGetRequest () at 
/usr/lib/x86_64-linux-gnu/libX11.so.6
#9  0x7fc0680c4a8a in XCreateColormap () at 
/usr/lib/x86_64-linux-gnu/libX11.so.6
#10 0x7fc068268cef in  () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
#11 0x7fc06826a3b8 in  () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
#12 0x7fc06821c85b in cogl_display_setup () at 
/usr/lib/x86_64-linux-gnu/libcogl.so.20
#13 0x7fc06821bb29 in cogl_renderer_check_onscreen_template () at 
/usr/lib/x86_64-linux-gnu/libcogl.so.20
#14 0x7fc0682ec65a in  () at /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
#15 0x7fc068316fb2 in  () at /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
#16 0x7fc0683307c3 in  () at /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
#17 0x7fc06834158a in  () at /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
#18 0x7fc0683417f8 in  () at /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
#19 0x7fc068970177 in g_option_context_parse () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x7fc06834274b in clutter_init () at 
/usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
#21 0x56283bed0229 in main (argc=, argv=) at 
main.c:961

The only special thing about this setup is that the shell is connected
via ssh and DISPLAY forwarding via -X parameter set. But various other
applications, even GTK based like vim-gtk, work just fine.

Best regards,
Eduard.

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

Kernel: Linux 5.10.4+ (SMP w/12 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages geeqie depends on:
ii  geeqie-common1:1.6-3
ii  libc62.31-6
ii  libcairo21.16.0-4
ii  libchamplain-0.12-0  0.12.20-1
ii  libchamplain-gtk-0.12-0  0.12.20-1
ii  libclutter-1.0-0 1.26.4+dfsg-2
ii  libclutter-gtk-1.0-0 1.8.4-4
ii  libcogl201.22.8-2
ii  libdjvulibre21   3.5.28-1
ii  libexiv2-27  0.27.3-3
ii  libffmpegthumbnailer4v5  1:2.2.2-dmo1
ii  libgcc-s110.2.1-3
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.4-1
ii  libgtk-3-0   3.24.24-1
ii  libheif1 1.10.0-1
ii  libjpeg62-turbo  1:2.0.5-1.1
ii  liblcms2-2   2.9-4+b1
ii  liblirc-client0  0.10.1-6.2+b1
ii  liblua5.1-0  5.1.5-8.1+b3
ii  libopenjp2-7 2.3.1-1
ii  libpango-1.0-0   1.46.2-3
ii  libpangocairo-1.0-0  1.46.2-3
ii  libpoppler-glib8 20.09.0-3
ii  libstdc++6   10.2.1-3
ii  libtiff5 4.2.0-1
ii  libwebp6 0.6.1-2+b1
ii  libx11-6 2:1.6.12-1
ii  sensible-utils   0.0.12+nmu1

Versions of packages geeqie recommends:
ii  cups-bsd [lpr]   2.3.3op1-4
ii  exiftran 2.10-4
ii  exiv20.27.3-3
ii  imagemagick  8:6.9.11.24+dfsg-1+b2
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.24+dfsg-1+b2
ii  librsvg2-common  2.50.2+dfsg-1
ii  ufraw-batch  0.22-4
ii  zenity   3.32.0-6

Versions of packages geeqie suggests:
pn  geeqie-dbg 
ii  gimp   2.10.22-2
ii  libjpeg-progs  1:9d-1
ii  ufraw  0.22-4
pn  xpaint 

-- no debconf information

--
Es ist auch so viel besser, daß man freundlich abrechnet, als daß man
sich immer einander anähnlichen will, und wenn das nicht reüssiert,
einander aus dem Wege geht.
-- Johann Wolfgang von Goethe (an Charlotte v. Stein, Febr. 
1789)

Bug#979462: aplus-fsf: FTBFS against glibc 2.32

[Logan Rosen]

Package: aplus-fsf
Version: 4.22.1-10.1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com

Hi,

aplus-fsf currently FTBFS against glibc 2.32, which is used in the
development release of Ubuntu (and should be in Debian soon).

This is because it has some improperly guarded usage of sys_errlist
instead of strerror().

In Ubuntu, the attached patch was applied to achieve the following:

  * Fix FTBFS against glibc 2.32 by using strerror() instead of sys_errlist.

Thanks for considering the patch.

Logan
only in patch2:
unchanged:
--- aplus-fsf-4.22.1.orig/src/MSIPC/MSProtocolConnection.C
+++ aplus-fsf-4.22.1/src/MSIPC/MSProtocolConnection.C
@@ -129,8 +129,13 @@
   if (getpeername(fd(),(struct sockaddr *),)) 
 #endif
{
+#if defined (HAVE_STRERROR)
+ char *errstr = strerror(errno);
+#else
+ char *errstr = (errno sys_nerr)
- str = "unknown error";
-   else
 #ifdef HAVE_STRERROR
-  str = strerror(errnum);
+str = strerror(errnum);
 #else
+if (errnum < 1 || errnum > sys_nerr)
+  str = "unknown error";
+else
  str = sys_errlist[errnum];
 #endif
for (z = str; *z != (char) NULL &&

Bug#979461: Updated Homepage: header?

[Moritz Muehlenhoff]

Package: cups
Severity: minor

Now that src:cups follows the openprinting fork, Homepage: should also point to
https://github.com/OpenPrinting/cups/ I suppose?

Cheers,
Moritz

Bug#979460: xfce4-panel: Multiple problems in Status Tray plugin (Xfce 4.16)

[Jens Arnold]

Package: xfce4-panel
Version: 4.16.0-1
Severity: important

Dear Maintainer,

   * What led up to the situation?

The situation started after upgrading to Xfce 4.16

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?

After upgrading, the Status tray extension (libstatustray.so) exhibits the
following problems:

1. For several programs which noprmally show their status using different icons
(e.g. Roger Router, Quasselclient) it always shows the same (last?) icon
instead of the proper icon depending on status. Roger router normally either
shows a green icon or an orange icon, depending on whether there was an
unanswered call. Now it always shows orange. Likewise, Quasselclient normally
shows a blue Q icon (blue ring with small globe in it). When someone pings you
in IRC, the ring turns red. Now it always shows red.

2. The sizes of several program icons are off, e.g. Quasselclient icon is much
too small.

3. (worst) Some programs cause the Systray to crash repeatedly (e.g. the (non-
opensource) Teamviewer). It can only be started again after closing the program
in question

   * What outcome did you expect instead?

I would expect the Systray to behave properly like it was in Xfce 4.14




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

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

Versions of packages xfce4-panel depends on:
ii  exo-utils4.16.0-1
ii  libatk1.0-0  2.36.0-2
ii  libc62.31-7
ii  libcairo21.16.0-5
ii  libdbusmenu-gtk3-4   18.10.20180917~bzr492+repack1-2
ii  libexo-2-0   4.16.0-1
ii  libgarcon-1-00.8.0-1
ii  libgarcon-gtk3-1-0   0.8.0-1
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.4-1
ii  libgtk-3-0   3.24.24-1
ii  libpango-1.0-0   1.46.2-3
ii  libpangocairo-1.0-0  1.46.2-3
ii  libwnck-3-0  3.36.0-1
ii  libx11-6 2:1.6.12-1
ii  libxext6 2:1.3.3-1.1
ii  libxfce4panel-2.0-4  4.16.0-1
ii  libxfce4ui-2-0   4.16.0-1
ii  libxfce4util74.16.0-1
ii  libxfconf-0-34.16.0-2

xfce4-panel recommends no packages.

xfce4-panel suggests no packages.

-- no debconf information

Bug#979459: jed: WARNING: tempfile is deprecated; consider using mktemp instead.

[Gabriele Stilli]

Package: jed
Version: 1:0.99.19-8

Hello,

during configuration, the package threw up this message:

Configurazione di jed (1:0.99.19-8)...
WARNING: tempfile is deprecated; consider using mktemp instead.

(Configurazione di = Configuring)

Regards,
Gabriele Stilli

Bug#979458: jed-common: WARNING: tempfile is deprecated; consider using mktemp instead.

[Gabriele Stilli]

Package: jed-common
Version: 1:0.99.19-8

Hello,

during configuration, the package threw up these messages:

Preparativi per estrarre .../13-jed-common_1%3a0.99.19-8_all.deb...
WARNING: tempfile is deprecated; consider using mktemp instead.

Configurazione di jed-common (1:0.99.19-8)...
WARNING: tempfile is deprecated; consider using mktemp instead.

(Preparativi per estrarre = Preparing to extract; Configurazione di =
Configuring)

Regards,
Gabriele Stilli

Bug#979457: RM: node-babel-preset-env -- ROM; Useless and replaced by node-babel7

[Xavier Guimard]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pkg-javascript-de...@lists.alioth.debian.org

Hi,

all reverse dependencies to node-babel-preset-env have been updated to
use node-babel7 (or virtual "node-babel-preset-env ≥ 7"), so this
package can now be safely removed from Debian archive.

Cheers,
Xavier

Bug#979453: kwallet-kf5: drop unused Build-Depends

[Helmut Grohne]

Source: kwallet-kf5
Version: 5.77.0-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

kwallet-kf5 somehow made it into the big set of packages relevant to
architecture bootstrap via some dependency cycle. Rather that work on
that hard problem, how about dropping entirely unused Build-Depends to
shrink the problem?

I couldn't find any use of either graphviz nor boost in kwallet-kf5.
Indeed building a modified kwallet-kf5 with graphviz and libboost-dev
turned into Build-Conflicts exactly reproduces the .debs when building
without this modification. Please consider applying the attached patch.

Helmut
diff --minimal -Nru kwallet-kf5-5.77.0/debian/changelog 
kwallet-kf5-5.77.0/debian/changelog
--- kwallet-kf5-5.77.0/debian/changelog 2020-12-22 02:33:36.0 +0100
+++ kwallet-kf5-5.77.0/debian/changelog 2021-01-06 17:28:34.0 +0100
@@ -1,3 +1,10 @@
+kwallet-kf5 (5.77.0-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop unused Build-Depends. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 06 Jan 2021 17:28:34 +0100
+
 kwallet-kf5 (5.77.0-2) unstable; urgency=medium
 
   * Release to unstable.
diff --minimal -Nru kwallet-kf5-5.77.0/debian/control 
kwallet-kf5-5.77.0/debian/control
--- kwallet-kf5-5.77.0/debian/control   2020-12-22 02:31:16.0 +0100
+++ kwallet-kf5-5.77.0/debian/control   2021-01-06 17:28:32.0 +0100
@@ -8,8 +8,6 @@
debhelper-compat (= 13),
doxygen,
extra-cmake-modules (>= 5.77.0~),
-   graphviz,
-   libboost-dev,
libgcrypt20-dev (>= 1.5.0~),
libgpgme-dev | libgpgme11-dev,
libgpgmepp-dev (>= 1.7.0~) | libgpgmepp6-dev,

Bug#979456: postgresql-13: reduce Build-Depends

[Helmut Grohne]

Source: postgresql-13
Version: 13.1-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

postgresql-13 is a central package with many dependencies. As such it is
involved in architecture bootstrap via dependency cycles. Rather than
working on such hard problems, I've looked into easily droppable
dependencies and postgresql-13 has two:

 * gdb is used in debian/rules in a nocheck-guarded section. Please
   annotate it . Such dependencies become irrelevant to
   bootstrapping.
 * docbook-xml is not used. There is a
   doc/src/sgml/standalone-install.xml file, but it is not built. As
   such the dependency is not needed.

Please consider applying the attached patch. I checked that a modified
postgresql-13 with these dependencies turned into Build-Conflicts
exactly reproduces the original .debs.

Helmut
--- postgresql-13-13.1/debian/changelog
+++ postgresql-13-13.1/debian/changelog
@@ -1,3 +1,12 @@
+postgresql-13 (13.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Reduce Build-Depends: (Closes: #-1)
++ docbook-xml is unused as standalone-install.xml is not built.
++ gdb is only used for testing.
+
+ -- Helmut Grohne   Wed, 06 Jan 2021 17:00:38 +0100
+
 postgresql-13 (13.1-1) unstable; urgency=medium
 
   * New upstream version.
--- postgresql-13-13.1/debian/control
+++ postgresql-13-13.1/debian/control
@@ -13,11 +13,10 @@
  clang-11 [!alpha !hppa !hurd-i386 !ia64 !kfreebsd-amd64 !kfreebsd-i386 !m68k 
!powerpc !riscv64 !sh4 !sparc64 !x32],
  debhelper-compat (= 13),
  dh-exec (>= 0.13~),
- docbook-xml,
  docbook-xsl (>= 1.77),
  dpkg-dev (>= 1.16.1~),
  flex,
- gdb,
+ gdb ,
  gettext,
  libicu-dev,
  libio-pty-perl,

Bug#979455: virtualjaguar FTCBFS: hard codes the build architecture pkg-config

[Helmut Grohne]

Source: virtualjaguar
Version: 2.1.3-2
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

virtualjaguar is a little difficult for cross compilation. While there
is explicit upstream support for it, it seems that this is limited to
windows hosts. This patch is not going to solve it all, but a major
sticking issue is the hard coding of the build architecture pkg-config.
This is done both in jaguarcore.mk and in virtualjaguar.pro. For
jaguarcore.mk I propose using the standard variable PKG_CONFIG and for
virtualjaguar.pro I propose using the standard pkg-config support
provided by qmake. On the qmake side, things become quite a little
simpler. Please consider applying the attached patch and close this bug
when doing so.

Helmut
--- virtualjaguar-2.1.3.orig/jaguarcore.mak
+++ virtualjaguar-2.1.3/jaguarcore.mak
@@ -27,8 +27,14 @@
 endif
 endif
 
+CC  := $(CROSS)gcc
+LD  := $(CROSS)gcc
+AR  := $(CROSS)ar
+PKG_CONFIG := $(CROSS)pkg-config
+ARFLAGS := -rs
+
 # Set vars for libcdio
-ifneq "$(shell pkg-config --silence-errors --libs libcdio)" ""
+ifneq "$(shell $(PKG_CONFIG) --silence-errors --libs libcdio)" ""
 HAVECDIO := -DHAVE_LIB_CDIO
 #This is the wrong place for this...
 #CDIOLIB  := -lcdio
@@ -37,11 +43,6 @@
 #CDIOLIB  :=
 endif
 
-CC  := $(CROSS)gcc
-LD  := $(CROSS)gcc
-AR  := $(CROSS)ar
-ARFLAGS := -rs
-
 SDL_CFLAGS = `$(CROSS)sdl-config --cflags`
 DEFINES = -D$(SYSTYPE) $(HAVECDIO)
 GCC_DEPS = -MMD
--- virtualjaguar-2.1.3.orig/Makefile
+++ virtualjaguar-2.1.3/Makefile
@@ -61,7 +61,7 @@
 
 virtualjaguar: sources libs makefile-qt
 	@echo -e "\033[01;33m***\033[00;32m Making Virtual Jaguar GUI...\033[00m"
-	$(Q)$(MAKE) -f makefile-qt CROSS=$(CROSS) V="$(V)" CDIO=libcdio
+	$(Q)$(MAKE) -f makefile-qt CROSS=$(CROSS) V="$(V)"
 
 makefile-qt: virtualjaguar.pro
 	@echo -e "\033[01;33m***\033[00;32m Creating Qt makefile...\033[00m"
--- virtualjaguar-2.1.3.orig/virtualjaguar.pro
+++ virtualjaguar-2.1.3/virtualjaguar.pro
@@ -36,11 +36,8 @@
 macx { LIBS += `sdl-config --static-libs` }
 else { LIBS += `$(CROSS)sdl-config --libs` }
 
-# libCDIO (may or may not be cross compatible, so we have this for now, just in
-# case we need it... (N.B.: the $(CDIO) is needed because under MXE, qmake
-# changes libcdio to -lcdio for some stupid reason...)
-macx { LIBS += `pkg-config --silence-errors --libs libcdio` }
-else { LIBS += `$(CROSS)pkg-config --silence-errors --libs $(CDIO)` }
+CONFIG += link_pkgconfig
+PKGCONFIG += libcdio
 
 # Icon on Win32, Mac
 #win32 { LIBS += res/vj-ico.o }

Bug#979454: knotifications: reduce Build-Depends

[Helmut Grohne]

Source: knotifications
Version: 5.77.0-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

knotifications plays a role in a pile of dependency cycles relevant to
architecture bootstrap. Rather than working on cycles directly, I looked
into easily droppable Build-Depends and noticed that knotifications has
some:

 * dbus-x11 is only used during the test suite. It can be tagged
   .
 * I couldn't find any usage of graphviz. I propose dropping it.
 * xauth and xvfb are used to wrap the test suite in debian rules. They
   can be tagged .

A nocheck build with these dependencies disabled produces exactly the
same .debs as a build containing them. Please consider applying the
attached patch.

Helmut
diff --minimal -Nru knotifications-5.77.0/debian/changelog 
knotifications-5.77.0/debian/changelog
--- knotifications-5.77.0/debian/changelog  2020-12-22 02:33:35.0 
+0100
+++ knotifications-5.77.0/debian/changelog  2021-01-06 18:57:03.0 
+0100
@@ -1,3 +1,10 @@
+knotifications (5.77.0-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Reduce Build-Depends. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 06 Jan 2021 18:57:03 +0100
+
 knotifications (5.77.0-2) unstable; urgency=medium
 
   * Release to unstable.
diff --minimal -Nru knotifications-5.77.0/debian/control 
knotifications-5.77.0/debian/control
--- knotifications-5.77.0/debian/control2020-12-22 02:31:16.0 
+0100
+++ knotifications-5.77.0/debian/control2021-01-06 18:56:49.0 
+0100
@@ -5,11 +5,10 @@
 Uploaders: Maximiliano Curia ,
Norbert Preining ,
 Build-Depends: cmake (>= 3.5~),
-   dbus-x11,
+   dbus-x11 ,
debhelper-compat (= 13),
doxygen,
extra-cmake-modules (>= 5.77.0~),
-   graphviz,
libdbusmenu-qt5-dev,
libkf5config-dev (>= 5.77.0~),
libkf5coreaddons-dev (>= 5.77.0~),
@@ -24,8 +23,8 @@
qtbase5-dev (>= 5.13.0~),
qttools5-dev (>= 5.4),
qttools5-dev-tools (>= 5.4),
-   xauth,
-   xvfb,
+   xauth ,
+   xvfb ,
 Standards-Version: 4.5.1
 Homepage: https://invent.kde.org/frameworks/knotifications
 Vcs-Browser: https://salsa.debian.org/qt-kde-team/kde/knotifications

Bug#979452: kconfigwidgets: reduce Build-Depends

[Helmut Grohne]

Source: kconfigwidgets
Version: 5.77.0-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

kconfigwidgets is part of a set of interconnected packages with
dependency cycles, which happen to be relevant to architecture
bootstrap. Instead of looking into difficult dependency cycles, I'm
after the low hanging fruit, which is easily droppable dependencies:

 * I couldn't find any use of graphviz and propose dropping it.
 * xauth and xvfb are used in override_dh_auto_test, which is skipped by
   debhelper when the nocheck option is active since compat level 13.
   These can thus be annotated .

I've attempted building kconfigwidgets with these dependencies replaced
with Build-Conflicts and the build result is bit-identical. Therefore,
please consider applying the attached patch.

Helmut
diff --minimal -Nru kconfigwidgets-5.77.0/debian/changelog 
kconfigwidgets-5.77.0/debian/changelog
--- kconfigwidgets-5.77.0/debian/changelog  2020-12-22 02:33:33.0 
+0100
+++ kconfigwidgets-5.77.0/debian/changelog  2021-01-06 20:13:07.0 
+0100
@@ -1,3 +1,10 @@
+kconfigwidgets (5.77.0-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Reduce Build-Depends. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 06 Jan 2021 20:13:07 +0100
+
 kconfigwidgets (5.77.0-2) unstable; urgency=medium
 
   * Release to unstable.
diff --minimal -Nru kconfigwidgets-5.77.0/debian/control 
kconfigwidgets-5.77.0/debian/control
--- kconfigwidgets-5.77.0/debian/control2020-12-22 02:31:15.0 
+0100
+++ kconfigwidgets-5.77.0/debian/control2021-01-06 20:13:05.0 
+0100
@@ -9,7 +9,6 @@
doxygen,
extra-cmake-modules (>= 5.77.0~),
gettext,
-   graphviz,
libkf5auth-dev (>= 5.77.0~),
libkf5codecs-dev (>= 5.77.0~),
libkf5config-dev (>= 5.77.0~),
@@ -23,8 +22,8 @@
qtbase5-dev (>= 5.13.0~),
qttools5-dev,
qttools5-dev-tools (>= 5.4),
-   xauth,
-   xvfb,
+   xauth ,
+   xvfb ,
 Standards-Version: 4.5.1
 Homepage: https://invent.kde.org/frameworks/kconfigwidgets
 Vcs-Browser: https://salsa.debian.org/qt-kde-team/kde/kconfigwidgets

Bug#979451: dtkgui FTCBFS: hard codes the build architecture pkg-config

[Helmut Grohne]

Source: dtkgui
Version: 5.2.2.4-1
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

dtkgui fails to cross build from source, because src/src.pro hard codes
the build architecture pkg-config. Please use the detected pkg-config
instead. I'm attaching a patch for your convenience.

Helmut
--- dtkgui-5.2.2.4.orig/src/src.pro
+++ dtkgui-5.2.2.4/src/src.pro
@@ -58,7 +58,7 @@
 
 linux* {
 # don't link library
-QMAKE_CXXFLAGS += $$system(pkg-config --cflags-only-I librsvg-2.0)
+QMAKE_CXXFLAGS += $$system($$pkgConfigExecutable() --cflags-only-I librsvg-2.0)
 
 HEADERS += \
 $$PWD/dregionmonitor.h

Bug#979000: Re: Bug#979000: libasound2: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all

[Maya]

If this is not the issue I've linked above, could you maybe point me to 
where to dig further?
I've already done quite some googleing on this and this was the closest 
I could get to a possible solution :-/

Bug#979450: booth: autopkgtest fails on ci-worker-ppc64el-01 (but apparently not on other ppc64el workers)

[Paul Gevers]

Source: booth
Version: 1.0-237-gdd88847-1
Severity: important
User: debian...@lists.debian.org
Usertags: flaky issue

Dear maintainers,

booth has an autopkgtest, great. However, today I noticed that booth
failed in the glibc test on ppc64el while most of the time it passes. I
found a pattern in the failures on ppc64el: it always happens on
ci-worker-ppc64el-01. This host is our first ppc64el host, and in
contrast to the other three host it has a spinning disk therefor has
slightly lower IO performance.

Apart from this delta in disk, I'm not aware of other changes between
our hosts. Do you have any idea why the test would only be failing on
this host?

Paul

https://ci.debian.net/data/autopkgtest/testing/ppc64el/b/booth/9384731/log.gz

autopkgtest [23:53:15]: test pacemaker: [---
=== config ===
authfile = /etc/booth/authkey
site = 127.0.0.1
ticket = "ticket-A"

=== cluster ===
Job for corosync.service failed because the control process exited with
error code.
See "systemctl status corosync.service" and "journalctl -xe" for details.
autopkgtest [23:53:41]: test pacemaker: ---]



OpenPGP_signature
Description: OpenPGP digital signature

Bug#979433: RFS: sabnzbdplus/3.1.1+dfsg-2 [RC] -- web-based binary newsreader with nzb support

[Jeroen Ploemen]

Package: sponsorship-requests
Severity: important

Dear mentors,

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

 * Package name: sabnzbdplus
   Version : 3.1.1+dfsg-2
   Upstream Author : The SABnzbd-Team 
 * URL : https://sabnzbd.org
 * License : GPL-2+ and others
 * Vcs : https://salsa.debian.org/python-team/packages/sabnzbdplus
   Section : contrib/net

It builds those binary packages:

  sabnzbdplus - web-based binary newsreader with nzb support

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/contrib/s/sabnzbdplus/sabnzbdplus_3.1.1+dfsg-2.dsc

Changes since the last upload:

 sabnzbdplus (3.1.1+dfsg-2) unstable; urgency=medium
 .
   [ JCF Ploemen (jcfp) ]
   * Tests: adjust syntax of pytest call. (Closes: #979300)
 .
   [ Sandro Tosi ]
   * Use the new Debian Python Team contact name and address


Thanks!


pgpBAOJldDDjC.pgp
Description: OpenPGP digital signature

Bug#979449: RM: moblin-cursor-theme -- ROM; dead upstream

[Ying-Chun Liu (PaulLiu)]

Package: ftp.debian.org
Severity: normal



Hi. The maintainer (Zhengpeng Hou) and I decided to remove this package
due to it is dead upstream.

Please see bug #979219

Yours,
Paul

Bug#979448: alsamixergui: FTBFS against glibc 2.32

[Logan Rosen]

Package: alsamixergui
Version: 0.9.0rc2-1-10
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com

Hi,

alsamixergui FTBFS against glibc 2.32, which is the version used in the
development version of Ubuntu (and probably will be in Debian soon as
well).

This is because it uses sys_siglist, which was removed in 2.32.

In Ubuntu, the attached patch was applied to achieve the following:

  * src/alsamixer.cxx: Fix FTBFS against glibc 2.32 by using strsignal()
instead of sys_siglist.

Thanks for considering the patch.

Logan
diff -u alsamixergui-0.9.0rc2-1/src/alsamixer.cxx 
alsamixergui-0.9.0rc2-1/src/alsamixer.cxx
--- alsamixergui-0.9.0rc2-1/src/alsamixer.cxx
+++ alsamixergui-0.9.0rc2-1/src/alsamixer.cxx
@@ -2086,7 +2086,7 @@
 mixer_signal_handler (int signal)
 {
   if (signal != SIGSEGV)
-mixer_abort (ERR_SIGNAL, sys_siglist[signal], 0);
+mixer_abort (ERR_SIGNAL, strsignal(signal), 0);
   else
 {
   fprintf (stderr, "\nSegmentation fault.\n");

Bug#979441: More information

[R. Lemos]

In /usr/lib/x86_64-linux-gnu/libopencv_dnn.so.4.5.1 I've found a
symbol `_ZN2cv3dnn14dnn4_v202011173NetC1Ev`. It differs from expected
`_ZN2cv3dnn14dnn4_v202009083NetC1Ev` on `...20201117...` (expected
`...20200908...`).

So maybe I need either a newer digikam or an older libopencv-dnn4.5.

Bug#975747: reopen the close to work around BTS bug

[Hans-Christoph Steiner]

Control: reopen -1

Bug#975007: src:xmds2: autopkgtest times out on ppc64el (and sometimes on amd64)

[Paul Gevers]

Hi Rafael,

On 18-11-2020 19:20, Paul Gevers wrote:
> On 18-11-2020 08:54, Rafael Laboissière wrote:
>>> Your package has an autopkgtest, great! However, it fails due to
>>> timeout on ppc64el (after 2:47 hours) and regularly on amd64 too. Can
>>> you please investigate and fix the situation?
>>>
>>> To avoid needlessly stress our infrastructure, I'll block this package
>>> on ppc64el until this bug is fixed.
>>
>> Thanks for the heads up, Paul.
>>
>> Since the xmds2 package has a huge amount of unit tests and since they
>> involve numerical computation of complicated problems (partial
>> differential equations), running the whole set of tests takes usually a
>> lot of time.
> 
> Is that really the problem? Is ppc64el so much slower than the other
> architectures (I didn't just now check the numbers, but thought they are
> regularly *much* lower)? Also, what makes the difference for the timing
> out ones on amd64? The load on the host?

I just noticed that all the tests that timed out on amd64 in the last
two months were done on ci-worker13. That is our most powerful host.
Maybe it's capable of a bit too much? Too much parallelism? Race conditions?

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#979441: Debugging information

[R. Lemos]

After installing digikam-private-libs-dbgsym and digikam-dbgsym

$ gdb digikam
(gdb) break _ZN2cv3dnn14dnn4_v202009083NetC1Ev
(gdb) run

Then after clicking "Scan collection for faces", gdb halted... then:

(gdb) bt
Thread 52 "Thread (pooled)" hit Breakpoint 1, 0x76bfc0d0 in
cv::dnn::dnn4_v20200908::Net::Net()@plt () from
/usr/lib/digikam/libdigikamcore.so.7.1.0
(gdb) bt
#0  0x76bfc0d0 in cv::dnn::dnn4_v20200908::Net::Net()@plt ()
at /usr/lib/digikam/libdigikamcore.so.7.1.0
#1  0x7724a15d in
Digikam::DNNFaceDetectorSSD::DNNFaceDetectorSSD()
(this=0x7fff70008810)
at ./core/libs/facesengine/detection/opencv-dnn/dnnfacedetectorssd.cpp:42
#2  0x77247c45 in
Digikam::OpenCVDNNFaceDetector::OpenCVDNNFaceDetector(Digikam::DetectorNNModel)
(this=0x7fff7000f4a0, model=)
at ./core/libs/facesengine/detection/opencv-dnn/opencvdnnfacedetector.cpp:54
#3  0x772384c4 in Digikam::FaceDetector::Private::backend()
(this=0x5d2f1a30) at
./core/libs/facesengine/detection/facedetector.cpp:85
#4  Digikam::FaceDetector::Private::applyParameters()
(this=0x5d2f1a30) at
./core/libs/facesengine/detection/facedetector.cpp:123
#5  Digikam::FaceDetector::setParameters(QMap
const&) (this=this@entry=0x5d27adf8, parameters=...)
at ./core/libs/facesengine/detection/facedetector.cpp:381
#6  0x77d32517 in
Digikam::DetectionWorker::setAccuracy(double) (this=0x5d27ade0,
accuracy=)
at ./core/utilities/facemanagement/workers/detectionworker.cpp:83
#7  0x75889f51 in QObject::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7631e15f in QApplicationPrivate::notify_helper(QObject*,
QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x7585df2a in QCoreApplication::notifyInternal2(QObject*,
QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x75860961 in
QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x758b5df3 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7fffe991ad3b in g_main_context_dispatch () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7fffe991afe8 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x7fffe991b09f in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x758b547f in
QEventDispatcherGlib::processEvents(QFlags)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7585c8eb in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x76e856fa in Digikam::WorkerObjectRunnable::run()
(this=0x5d431f70) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:121
#18 0x7567fe72 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7567cb81 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x73a29ea7 in start_thread (arg=) at
pthread_create.c:477
#21 0x752ffd8f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


Hope it helps.

Bug#979447: ganglia-monitor: init script badly interacting with systemd

[Vincent Danjean]

Package: ganglia-monitor
Version: 3.6.0-7+b2
Severity: important
Tags: patch

  Hi,

  After a long debug session, I realized that an administrator
cannot invoke directly the /etc/init.d/ganglia-monitor if he wants
systemd to be aware of the action.
  For example, gmond was started at boot, but it hungs due to the
reboot of the target machine (probably another bug).
  An admin types:
/etc/init.d/ganglia-monitor restart
  And then gmond have been restarted but systemd thinks the service is down.

Here is a trace illustrating what I say:

root@ge91097-vm1:/etc/ganglia# systemctl status ganglia-monitor
● ganglia-monitor.service
   Loaded: loaded (/etc/init.d/ganglia-monitor; generated)
  Drop-In: /etc/systemd/system/ganglia-monitor.service.d
   └─restart.conf
   Active: active (running) since Wed 2021-01-06 21:29:29 CET; 13s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 7134 ExecStart=/etc/init.d/ganglia-monitor start (code=exited, 
status=0/SUCCESS)
 Main PID: 7138 (gmond)
Tasks: 2 (limit: 4915)
   Memory: 1.8M
   CGroup: /system.slice/ganglia-monitor.service
   └─7138 /usr/sbin/gmond --pid-file /var/run/gmond.pid

janv. 06 21:29:29 ge91097-vm1 systemd[1]: ganglia-monitor.service: Scheduled 
restart job, restart counter is at 1.
janv. 06 21:29:29 ge91097-vm1 systemd[1]: Stopped ganglia-monitor.service.
janv. 06 21:29:29 ge91097-vm1 systemd[1]: Starting ganglia-monitor.service...
janv. 06 21:29:29 ge91097-vm1 ganglia-monitor[7134]: Starting Ganglia Monitor 
Daemon: gmond.
janv. 06 21:29:29 ge91097-vm1 systemd[1]: Started ganglia-monitor.service.
root@ge91097-vm1:/etc/ganglia# systemd-cgls -u  ganglia-monitor.service
Unit ganglia-monitor.service (/system.slice/ganglia-monitor.service):
└─7138 /usr/sbin/gmond --pid-file /var/run/gmond.pid
root@ge91097-vm1:/etc/ganglia# ps axf | grep gmon
 7171 pts/0S+ 0:00  |   \_ grep gmon
 7138 ?Ssl0:00 /usr/sbin/gmond --pid-file /var/run/gmond.pid
root@ge91097-vm1:/etc/ganglia# /etc/init.d/ganglia-monitor restart
Stopping Ganglia Monitor Daemon: gmond.
Starting Ganglia Monitor Daemon: gmond.
root@ge91097-vm1:/etc/ganglia# systemctl status ganglia-monitor
● ganglia-monitor.service
   Loaded: loaded (/etc/init.d/ganglia-monitor; generated)
  Drop-In: /etc/systemd/system/ganglia-monitor.service.d
   └─restart.conf
   Active: activating (auto-restart) since Wed 2021-01-06 21:30:20 CET; 5s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 7134 ExecStart=/etc/init.d/ganglia-monitor start (code=exited, 
status=0/SUCCESS)
  Process: 7176 ExecStop=/etc/init.d/ganglia-monitor stop (code=exited, 
status=0/SUCCESS)
 Main PID: 7138 (code=killed, signal=TERM)
root@ge91097-vm1:/etc/ganglia# systemd-cgls -u  ganglia-monitor.service
Unit ganglia-monitor.service not found.
Failed to list cgroup tree: No such file or directory
root@ge91097-vm1:/etc/ganglia# ps axf | grep gmon
 7189 pts/0S+ 0:00  |   \_ grep gmon
 7179 ?Ssl0:00 /usr/sbin/gmond --pid-file /var/run/gmond.pid

gmond restarted, but systemd is unaware of it.



  The fix is pretty simple: as (nearly all) other init script,
just add the following line at the begining (just after LSB header):
. /lib/lsb/init-functions
It will handle the synchronization with systemd (or other
init systems) for direct script invocation.

  Regards
Vincent

-- System Information:
Debian Release: bullseye/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel, mipsel

Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ganglia-monitor depends on:
ii  adduser  3.118
ii  init-system-helpers  1.60
ii  libapr1  1.7.0-4
ii  libc62.31-6
pn  libconfuse1  
pn  libconfuse2  
ii  libexpat12.2.10-1
pn  libganglia1  
ii  libpcre3 2:8.39-13
ii  lsb-base 11.1.0
ii  zlib1g   1:1.2.11.dfsg-2

ganglia-monitor recommends no packages.

ganglia-monitor suggests no packages.

Bug#972119: terminator: conflicts with icon-theme.cache on install

[Markus Frosch]

Source: terminator
Source-Version: 2.0.1+gittag-1~bpo10+1

Hey,

this is now fixed with the latest update to buster-backports.

Best Regards
Markus Frosch

Bug#975174: marked as pending in librtr

[Adrian Bunk]

On Thu, Dec 24, 2020 at 05:30:34AM +, Francisco Vilmar Cardoso Ruviaro 
wrote:
> Hello,
> 
> Bug #975174 in librtr 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/pkg-security-team/librtr/-/commit/e67dfd32e381239e7981d30b4a4fba3249e5070a
> 
> 
> Remove a symbol to fix a FTBFS
> (Closes: #975174)
> 
>...

This is unfortunately not the correct fix, the root problem is that 
librtr got built without libssh support with the new libssh.

For a better fix fix, please see
https://github.com/rtrlib/rtrlib/pull/260

cu
Adrian

Bug#978973: RFP: gnome-activity-journal -- Activity Journal for the GNOME desktop environment ( Powered by Zeitgeist 1.0.3 )

[Sudip Mukherjee]

Control: retitle -1 ITP: gnome-activity-journal -- Activity Journal for the 
GNOME desktop environment
Control: owner -1 !
--

Hi crvi,

On Fri, Jan 01, 2021 at 08:07:44PM +0530, crvi wrote:
> Package: wnpp
> Severity: wishlist
> X-Debbugs-Cc: crvi...@gmail.com
> 
> * Package name: gnome-activity-journal
>   Version : 1.0.0

It seems you have bumped the version but have not created any tag.
Can you please tag the version.

--
Regards
Sudip

Bug#979177: cups-filters-core-drivers: Adding a printer impossible because "driverless" is too slow

[Till Kamppeter]

The problem also got reported upstream:

https://github.com/OpenPrinting/cups/issues/65

Could you also see the discussion there and try what got suggested there?

I by myself am not able to reproduce it, so I need someone who can 
reproduce it to find out under which conditions it happens.


   Till

Bug#976928: spass: FTBFS on ppc64el: iascanner.l:50:10: fatal error: iaparser.h: No such file or directory

[Adrian Bunk]

Control: retitle -1 spass sometimes FTBFS due to race condition
Control: tags -1 patch

On Wed, Dec 09, 2020 at 09:42:01AM +0100, Lucas Nussbaum wrote:
>...
> > iascanner.l:50:10: fatal error: iaparser.h: No such file or directory
> >50 | #include "iaparser.h"
> >   |  ^~~~
> > compilation terminated.
> > make[1]: *** [makefile:239: iascanner.o] Error 1
>...

This is a race condition in parallel builds due to incomplete makefile
dependencies.

Workaroud:

--- debian/rules.old2021-01-06 16:50:16.958225516 +
+++ debian/rules2021-01-06 16:50:23.310221816 +
@@ -1,4 +1,4 @@
 #!/usr/bin/make -f
 
 %:
-   dh $@
+   dh $@ --no-parallel

Bug#979446: paraview: Lots of Git-LFS pointers in source tarball and Salsa Repository

[WANA]

Package: paraview
Version: 5.9.0~rc1-2
Severity: normal

Dear Maintainer,

the source tarball in Sid [1] and the current debian/latest branch in
the Salsa git repository [2] contain many Git-LFS pointers instead of
the binary files, e.g.:

$ grep -r -l 'https://git-lfs.github.com/spec/v1' paraview-5.9.0~rc1/

paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/sentinel-data
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/unstructured/simple_poly_bin.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/unstructured/simple_unstructured_bin.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/unstructured/empty_poly.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/unstructured/simple_poly_ascii.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/unstructured/simple_unstructured_ascii.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/unstructured/simple_unstructured_visit_ascii.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/unstructured/empty_unstructured.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/unstructured/ucd3d.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/unstructured/wedge_cells.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/curvilinear/simple_structured_ascii.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/curvilinear/simple_structured_bin.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/rectilinear/fusion.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/rectilinear/fishtank.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/rectilinear/magField.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/rectilinear/fishtank_double_ascii.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/rectilinear/fishtank_double_big_endian.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/rectilinear/DoubleGyre_0.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/rectilinear/simple_rectilinear1_ascii.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/rectilinear/DoubleGyre_5.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/rectilinear/simple_rectilinear2_ascii.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/rectilinear/noise.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/uniform/simple_structured_points_bin.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/uniform/simple_structured_points_visit_ascii.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/uniform/simple_structured_points_ascii.vtk
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/uniform/noise
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/data/uniform/noise.bov
paraview-5.9.0~rc1/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/README.md

Cloning the Salsa repository fails with:

$ git clone https://salsa.debian.org/science-team/paraview.git

Cloning into 'paraview'...
remote: Enumerating objects: 155527, done.
remote: Counting objects: 100% (155527/155527), done.
remote: Compressing objects: 100% (53101/53101), done.
remote: Total 155527 (delta 103049), reused 147848 (delta 95373), pack-reused 0
Receiving objects: 100% (155527/155527), 204.05 MiB | 5.44 MiB/s, done.
Resolving deltas: 100% (103049/103049), done.
[attr]our-c-style  whitespace=tab-in-indent,-blank-at-eol  format.clang-format 
not allowed: ThirdParty/QtTesting/vtkqttesting/.gitattributes:8
[attr]our-c-style  whitespace=tab-in-indent,-blank-at-eol  
format.clang-format=9 not allowed: 
ThirdParty/catalyst/vtkcatalyst/catalyst/.gitattributes:4
[attr]our-c-style  whitespace=tab-in-indent,-blank-at-eol  
format.clang-format=8 not allowed: VTK/.gitattributes:10
[attr]our-c-style   whitespace=tab-in-indent  format.clang-format=9 not 
allowed: VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/.gitattributes:2
Checking out files: 100% (30301/30301), done.
[attr]our-c-style  whitespace=tab-in-indent,-blank-at-eol  
format.clang-format=8 not allowed: VTK/.gitattributes:10
[attr]our-c-style   whitespace=tab-in-indent  format.clang-format=9 not 
allowed: VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/.gitattributes:2
Downloading VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/README.md (643 B)
Error downloading object: VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/README.md 
(b30a14a): Smudge error: Error downloading 
VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/README.md 
(b30a14a308f64c6fc2969e2b959d79dacdc5affda1d1c0e24f8e176304147146): 
[b30a14a308f64c6fc2969e2b959d79dacdc5affda1d1c0e24f8e176304147146] Object does 
not exist on the server or you don't have permissions to access it: [404] 
Object does not exist on the server or you don't have permissions to access it

Errors logged to /tmp/asd/paraview/.git/lfs/logs/20210106T212408.997564891.log
Use `git lfs logs last` to view the log.
error: external filter 'git-lfs 

Bug#979429: RFS: node-gulp-tsb/4.0.5-1 [ITP] -- node-gulp-tsb

[VIVEK K J]

Package: node-gulp-tsb
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-gulp-tsb":

* Package name : node-gulp-tsb
Version : 4.0.5-1
Upstream Author : Johannes Rieken 
* URL : https://github.com/jrieken/gulp-tsb
* License : Expat
* Vcs : https://salsa.debian.org/vivekkj/node-gulp-tsb
Section : Javascript

It builds those binary packages:

node-gulp-tsb

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

https://www.npmjs.com/package/gulp-tsb

This is a part of HedgeDoc packaging[1]

Regards,

Vivek K J

[1] - https://wiki.debian.org/Javascript/Nodejs/Tasks/HedgeDoc

Bug#979177: cups-filters-core-drivers: Adding a printer impossible because "driverless" is too slow

[Brian Potkin]

Any progress on this issue, Shai?

Cheers,

Brian.

Bug#969287: raspi-firmware: Dual HDMI support for RaspberryPI4

[Gunnar Wolf]

tags 969287 + moreinfo,help
thanks

Hello,

I am sorry for not answering to this bug report sooner; I cannot test
to reproduce what you say (I have only one MicroHDMI cable), and even
if I could, I really don't think I can do much to help. Your bug
report has a lot of interesting insight, but I will not say I am the
best equipped to make sense out of it.

The situation has evolved quite a bit since you filed the bug, and
having both newer firmware and kernel versions, I wouldn't be
surprised if this issue managed to fix itself. I understand (but don't
know for sure) advances have been made regarding vc4 support in
mainline Linux.

So, do you still have this behavior? Have you (or has anybody else)
been able to get dual-screen support on your RPi4? Or do you have any
promising pointers on this?

Thanks,

Bug#956958: simple-cdd on Bullseye gives reprepro error

[Jose Marinho]

Package: simple-cdd
Version: 0.6.7
Followup-For: Bug #956958
X-Debbugs-Cc: josemarinh...@gmail.com

Dear Maintainer,

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

   * What led up to the situation?
I was trying to create a custom cd of my installation
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I only follow the instructions from Debian Wiki page: 
https://wiki.debian.org/Simple-CDD/Howto

   * What was the outcome of this action?
jose@bullseye:~$ mkdir ~/simple-cdd
jose@bullseye:~$ cd simple-cdd/
jose@bullseye:~/simple-cdd$ build-simple-cdd
gpg: /home/jose/.gnupg/trustdb.gpg: creouse a base de datos de confianza
2021-01-06 20:26:25 ERROR reprepro: updating package lists exited with code 255
2021-01-06 20:26:25 ERROR Last 5 lines of standard error:
2021-01-06 20:26:25 ERROR reprepro: updating package lists: aptmethod error 
receiving 'http://security.debian.org/dists/bullseye/updates/Release.gpg':
2021-01-06 20:26:25 ERROR reprepro: updating package lists: '404  Not Found 
[IP: 151.101.134.132 80]'
2021-01-06 20:26:25 ERROR reprepro: updating package lists: aptmethod error 
receiving 'http://security.debian.org/dists/bullseye/updates/Release.gpg':
2021-01-06 20:26:25 ERROR reprepro: updating package lists: '404  Not Found 
[IP: 151.101.134.132 80]'
2021-01-06 20:26:25 ERROR reprepro: updating package lists: There have been 
errors!
2021-01-06 20:26:25 ERROR reprepro failed with exit code: 255

   * What outcome did you expect instead?
Build the iso as expect
*** End of the template - remove these template lines ***


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

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

Versions of packages simple-cdd depends on:
ii  dctrl-tools 2.24-3+b1
ii  debian-cd   3.1.31
ii  lsb-release 11.1.0
ii  python3 3.9.1-1
ii  python3-simple-cdd  0.6.7
ii  reprepro5.3.0-1.1
ii  rsync   3.2.3-3
ii  wget1.20.3-1+b3

Versions of packages simple-cdd recommends:
ii  dose-distcheck  5.0.1-15+b3

Versions of packages simple-cdd suggests:
ii  qemu-system-x86 [qemu-kvm]  1:5.2+dfsg-3

-- no debconf information

Bug#962038: raspi-firmware: Add Bluetooth firmware

[Gunnar Wolf]

tags 962038 + wontfix
thanks

Hello Bastian,

Thinking about this bug, I have decided to tag it "wontfix".

Of course, it does not mean it should not be fixed by alternate means
-- But I don't want to require following different sources for this
package. My aim with raspi-firmware is to allow a Raspberry to boot
into a clean, regular Debian system. There are several pieces of the
Raspberry that might require additional firmware; my suggestion is to
have them separately packaged, in what could probably be a
raspi-bluez-firmware package or something like that.

Greetings,

Bug#971884: raspi-firmware: could you enable dpkg-reconfigure raspi-firmware?

[Gunnar Wolf]

tags 971884 + unreproducible
thanks

Hello,

Going over our list of pending bugs, I found this report pending
action. Please confirm whether you consider this bug to be present
(and explain it further, as I requested in my November 19 reply!), or
confirm this bug can be closed now.

Thanks!

Bug#967987: fuzz: Removal of sys_errlist

[Logan Rosen]

Package: fuzz
Version: 0.6-19
Followup-For: Bug #967987
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com
Control: tags -1 patch

Hi,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/glibc-2.32.patch: Fix FTBFS against glibc 2.32 by using strerror()
instead of sys_errlist.

Thanks for considering the patch.

Logan
diff -Nru fuzz-0.6/debian/patches/glibc-2.32.patch 
fuzz-0.6/debian/patches/glibc-2.32.patch
--- fuzz-0.6/debian/patches/glibc-2.32.patch1969-12-31 19:00:00.0 
-0500
+++ fuzz-0.6/debian/patches/glibc-2.32.patch2021-01-06 14:49:40.0 
-0500
@@ -0,0 +1,11 @@
+--- a/fuzz.c
 b/fuzz.c
+@@ -814,7 +814,7 @@
+ 
+   execv(progname,arguments);
+   write(cpy_stderr,"Exec failed.\n",strlen("Exec failed.\n"));
+-  write(cpy_stderr,sys_errlist[errno],strlen(sys_errlist[errno]));
++  write(cpy_stderr,strerror(errno),strlen(strerror(errno)));
+   exit(CANT_FORK_EXIT);
+ }
+ 
diff -Nru fuzz-0.6/debian/patches/series fuzz-0.6/debian/patches/series
--- fuzz-0.6/debian/patches/series  2016-10-19 02:16:45.0 -0400
+++ fuzz-0.6/debian/patches/series  2021-01-06 14:48:17.0 -0500
@@ -1,3 +1,4 @@
 10-fuzz.1-manpage-fixes.patch
 10-fuzz.1-manpage-fixes=11-newlines.patch
 20-fuzz.c--option-chroot.patch
+glibc-2.32.patch

Bug#979444: ITP: go-dlib -- Go bindings for Deepin Desktop Environment (DDE).

[Arun Kumar Pariyar]

Package: wnpp
Severity: wishlist
Owner: Arun Kumar Pariyar 
X-Debbugs-Cc: debian-de...@lists.debian.org, 
pkg-deepin-de...@alioth-lists.debian.net


* Package name : go-dlib
Version : 5.5.0.13
Upstream Author : Deepin Technology Co., Ltd.
* URL : https://www.deepin.org/
* License : GPL-3+
Programming Lang: Golang
Description : Go bindings for Deepin Desktop Environment (DDE).

go-dlib is a set of go bindings for D-Bus, glib, gdkpixbuf, pulse and more.
This package provides set of golang bindings and libraries for DDE 
development.

This package is part of DDE (Deepin Desktop Environment).



OpenPGP_0x4B542AF704F74516.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Bug#979443: chromium: desktop GUI locks up as Xorg process goes to 100%

[Steve A.]

Package: chromium
Version: 87.0.4280.88-0.4~deb10u1
Severity: grave
Tags: a11y
Justification: renders package unusable

Dear Maintainer,

Subsequent to an upgrade from 83.0.4103.116-1~deb10u3 to 
87.0.4280.88-0.4~deb10u1, the desktop GUI randomly freezes, including 
the clock.  This occurred three times over the course of two days. 
Doing a ssh from another machine, and then running top, showed the Xorg 
process pegged at 100%.  Killing just the chromium process did not 
resolve the locking problem, and the only way to recover was to kill all 
processes for the GUI user.  Chromium was rolled back to 
83.0.4103.116-1~deb10u3 and there have been no freezes in over two days.



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

Kernel: Linux 4.19.0-13-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_WARN
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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common  87.0.4280.88-0.4~deb10u1
ii  libasound2   1.1.8-1
ii  libatk-bridge2.0-0   2.30.0-5
ii  libatk1.0-0  2.30.0-2
ii  libatspi2.0-02.30.0-7
ii  libavcodec58 7:4.1.6-1~deb10u1
ii  libavformat587:4.1.6-1~deb10u1
ii  libavutil56  7:4.1.6-1~deb10u1
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libcups2 2.2.10-6+deb10u4
ii  libdbus-1-3  1.12.20-0+deb10u1
ii  libdrm2  2.4.97-1
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.6-2+deb10u1
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3+deb10u2
ii  libgbm1  18.3.6-2+deb10u1
ii  libgcc1  1:8.3.0-6
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-2+deb10u2
ii  libgtk-3-0   3.24.5-1
ii  libharfbuzz0b2.3.1-1
ii  libicu63 63.1-6+deb10u1
ii  libjpeg62-turbo  1:1.5.2-2+deb10u1
ii  libjsoncpp1  1.7.4-3
ii  liblcms2-2   2.9-3
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.20-1
ii  libnss3  2:3.42.1-1+deb10u3
ii  libopenjp2-7 2.3.0-2+deb10u1
ii  libopus0 1.3-1
ii  libpango-1.0-0   1.42.4-8~deb10u1
ii  libpangocairo-1.0-0  1.42.4-8~deb10u1
ii  libpng16-16  1.6.36-6
ii  libpulse012.2-4+deb10u1
ii  libre2-5 20190101+dfsg-2
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.3.0-6
ii  libvpx5  1.7.0-3+deb10u1
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libx11-6 2:1.6.7-1+deb10u1
ii  libx11-xcb1  2:1.6.7-1+deb10u1
ii  libxcb-dri3-01.13.1-2
ii  libxcb1  1.13.1-2
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-2
ii  libxdamage1  1:1.1.4-3+b3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-7+deb10u1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.32-2.2~deb10u1
ii  libxss1  1:1.2.3-1
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages chromium recommends:
ii  chromium-sandbox  87.0.4280.88-0.4~deb10u1

Versions of packages chromium suggests:
pn  chromium-driver  
pn  chromium-l10n
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  x11-utils  7.7+4
ii  xdg-utils  1.1.3-1+deb10u1

Versions of packages chromium-common recommends:
ii  chromium-sandbox87.0.4280.88-0.4~deb10u1
ii  fonts-liberation1:1.07.4-9
ii  libgl1-mesa-dri 18.3.6-2+deb10u1
ii  libu2f-udev 1.1.9-1
ii  mate-notification-daemon [notification-daemon]  1.20.2-1
ii  notification-daemon 3.20.0-4
ii  upower  0.99.10-1

Versions of packages chromium-sandbox depends on:
ii  libc6  2.28-10

-- no debconf information

Bug#972767: frr ftbfs with python3.9

[s3v]

Dear Maintainer,

I can confirm that mentioned patch fixed FTBFS in my sid chroot environment.

Kind Regards.

Bug#979302: libgtkextra-3.0: ships libgtkextra-x11-3.0.so

[Georges Khaznadar]

Thank you for the bug report, Andreas!

So, as I understand it, the warnings reported by dh-missing were false
positives. I shall try to rebuild the package without the duplicate
installation of files, and a fresh build environment: I hope that the
last version of dh-missing will no longer prevent the build of the
package.

Best regards,   Georges.

Andreas Beckmann a écrit :
> Package: libgtkextra-3.0
> Version: 3.3.4-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package failed to install
> because it tries to overwrite other packages files.
> 
> >From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package libgtkextra-3.0.
>   Preparing to unpack .../61-libgtkextra-3.0_3.3.4-2_amd64.deb ...
>   Unpacking libgtkextra-3.0 (3.3.4-2) ...
>   Selecting previously unselected package libgtkextra-dev.
>   Preparing to unpack .../62-libgtkextra-dev_3.3.4-2_amd64.deb ...
>   Unpacking libgtkextra-dev (3.3.4-2) ...
>   dpkg: error processing archive 
> /tmp/apt-dpkg-install-gS1CgJ/62-libgtkextra-dev_3.3.4-2_amd64.deb (--unpack):
>trying to overwrite '/usr/lib/x86_64-linux-gnu/libgtkextra-x11-3.0.so', 
> which is also in package libgtkextra-3.0 3.3.4-2
>   Errors were encountered while processing:
>/tmp/apt-dpkg-install-gS1CgJ/62-libgtkextra-dev_3.3.4-2_amd64.deb
> 
> The .so symlink belongs into the -dev package, not into the package
> with the shared library. (Policy 8.4)
> 
> Looking at the changelog entry of the last upload I noticed
> 
> >   * modified debian/libgtkextra-3.0.install to include files
> > usr/lib/x86_64-linux-gnu/libgtkextra-x11-3.0.a and
> 
> The .a file belongs into the -dev package. (Policy 8.3)
> 
> > usr/lib/x86_64-linux-gnu/libgtkextra-x11-3.0.la in order to prevent
> 
> The .la file belongs into the trash bin.
> (https://wiki.debian.org/ReleaseGoals/LAFileRemoval)
> 
> > dh_missing's warning about files "not installed to anywhere"
> 
> 
> cheers,
> 
> Andreas



-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: PGP signature

Bug#979442: libdaemon: Please make autopkgtests cross-test-friendly

[Steve Langasek]

Package: libdaemon
Version: 0.14-7.1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch

Hi Michael,

In Ubuntu, we have moved the i386 architecture to a compatibility-only layer
on amd64, and therefore we are also moving our autopkgtest infrastructure to
test i386 binaries in a cross-environment.

This requires changes to some tests so that they are cross-aware and can do
the right thing.

The libdaemon tests currently fail in this environment, because there is a
build test that does not invoke the toolchain in a cross-aware manner.  I've
verified that the attached patch lets the tests successfully build i386
tests on an amd64 host.

Note that upstream autopkgtest doesn't currently set DEB_HOST_ARCH so this
is a complete no-op in Debian for the moment.  Support for cross-testing in
autopkgtest is currently awaiting review at
https://salsa.debian.org/ci-team/autopkgtest/merge_requests/69 and once
landed, will still have no effect unless autopkgtest is invoked with a '-a'
option.  So this change should be safe to land in your package despite this
not being upstream in autopkgtest.

Thanks for considering,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libdaemon-0.14/debian/tests/build libdaemon-0.14/debian/tests/build
--- libdaemon-0.14/debian/tests/build   2018-04-27 04:35:47.0 -0700
+++ libdaemon-0.14/debian/tests/build   2021-01-04 13:07:47.0 -0800
@@ -5,6 +5,14 @@
 
 cd "${AUTOPKGTEST_TMP:-"${ADTTMP}"}"
 
+if [ -n "${DEB_HOST_GNU_TYPE:-}" ]; then
+CC="$DEB_HOST_GNU_TYPE-gcc"
+PKGCONFIG="$DEB_HOST_GNU_TYPE-pkg-config"
+else
+CC=gcc
+PKGCONFIG=pkg-config
+fi
+
 cat > trivial.c <<'EOF'
 #include 
 
@@ -16,7 +24,7 @@
 }
 EOF
 
-gcc -o trivial trivial.c $(pkg-config --cflags --libs libdaemon)
+"$CC" -o trivial trivial.c $("$PKGCONFIG" --cflags --libs libdaemon)
 test -x trivial
 ./trivial
 echo "# everything seems OK"

Bug#979441: digikam: Crashes when detecting faces

[R. Lemos]

Package: digikam
Version: 4:7.1.0-1+b1
Severity: normal

The program crashes with message

> digikam: symbol lookup error: /usr/lib/digikam/libdigikamcore.so.7.1.0: 
> undefined symbol: _ZN2cv3dnn14dnn4_v202009083NetC1Ev

Steps to reproduce:
(photos already imported into database)

1. Menu Browse > People (Ctrl+Shift+F9)
2. (didn't touch anything here on "People" panel)
  Tags tree contains:
  - People
- Unconfirmed
- Unknown
  Workflow tab:
"Skip images already scanned" selected
"Detect faces" selected
  Search in / Albums tab:
"Whole albums collection" selected
  Search in / Tags tab:
"Whole tags collection" NOT selected
and "No Tag Selected"
  Settings tab:
Face Accuracy Sensitivity-Specificity: 70
"Work on all processor cores" NOT selected
3. Click "Scan collection for faces"
4. Program immediately crashes ("symbol lookup error..." on console)


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

Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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 digikam depends on:
ii  digikam-data  4:7.1.0-1
ii  digikam-private-libs  4:7.1.0-1+b1
ii  libc6 2.31-6
ii  libgcc-s1 10.2.1-3
ii  libkf5configcore5 5.77.0-2
ii  libkf5coreaddons5 5.77.0-2
ii  libkf5i18n5   5.77.0-2
ii  libmagick++-6.q16-8   8:6.9.11.24+dfsg-1+b2
ii  libqt5core5a  5.15.2+dfsg-2
ii  libqt5gui55.15.2+dfsg-2
ii  libqt5sql55.15.2+dfsg-2
ii  libqt5sql5-mysql  5.15.2+dfsg-2
ii  libqt5sql5-sqlite 5.15.2+dfsg-2
ii  libqt5widgets55.15.2+dfsg-2
ii  libstdc++610.2.1-3
ii  perl  5.32.0-6

Versions of packages digikam recommends:
ii  chromium [www-browser]  87.0.4280.88-0.4~deb10u1
ii  epiphany-browser [www-browser]  3.38.2-1
ii  ffmpegthumbs4:20.12.0-1
ii  firefox-esr [www-browser]   78.6.0esr-1
ii  google-chrome-stable [www-browser]  87.0.4280.88-1

Versions of packages digikam suggests:
pn  digikam-doc 
pn  systemsettings  

-- no debconf information

Bug#979440: Mnemosyne dependency issue

[Lingyu Zhou]

Package: mnemosyne
Version: 2.7.3+ds1-1

Description:
In debian testing (bullseye), after installing mnemosyne using `sudo apt
install mnemosyne`, mnemosyne could not be launch normally, because of lack
of dependencies.
Detailed error message and system info are below.

Suggested fix:
Add `python3-gtts` as a dependency to mnemosyne.



-START OF ERROR MESSAGE
$ mnemosyne
Warning: Could not import OpenGL. Might cause a black screen on some
Linux distributions. Try installing python3-opengl in that case.
Log body:
 An unexpected error has occurred.
Please forward the following info to the developers:

Traceback (innermost last):
  File "/usr/bin/mnemosyne", line 277, in 
mnemosyne.initialise(data_dir=data_dir, filename=filename,
  File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py",
line 400, in initialise
self.register_components()
  File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py",
line 465, in register_components
importlib.import_module(module_name), class_name)
  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 
"/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/pronouncers/google_pronouncer.py",
line 5, in 
from gtts import gTTS
 ModuleNotFoundError: No module named 'gtts'

An unexpected error has occurred.
Please forward the following info to the developers:

Traceback (innermost last):
  File "/usr/bin/mnemosyne", line 277, in 
mnemosyne.initialise(data_dir=data_dir, filename=filename,
  File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py",
line 400, in initialise
self.register_components()
  File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py",
line 465, in register_components
importlib.import_module(module_name), class_name)
  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 
"/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/pronouncers/google_pronouncer.py",
line 5, in 
from gtts import gTTS
 ModuleNotFoundError: No module named 'gtts'
An unexpected error has occurred.
Please forward the following info to the developers:

Traceback (innermost last):
  File "/usr/bin/mnemosyne", line 277, in 
mnemosyne.initialise(data_dir=data_dir, filename=filename,
  File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py",
line 400, in initialise
self.register_components()
  File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py",
line 465, in register_components
importlib.import_module(module_name), class_name)
  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 
"/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/pronouncers/google_pronouncer.py",
line 5, in 
from gtts import gTTS
 ModuleNotFoundError: No module named 'gtts'

-END OF ERROR MESSAGE


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

Kernel: Linux 5.9.0-5-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 mnemosyne depends on:
ii  libjs-sphinxdoc 3.3.1-1
ii  libqt5sql5-sqlite   5.15.2+dfsg-2
ii  python3 3.9.1-1
ii  python3-cheroot 8.5.1+ds1-1
ii  python3-cherrypy3   8.9.1-7
ii  python3-matplotlib  3.3.2-2+b1
ii  python3-pil 8.0.1-1+b1
ii  python3-pyqt5   5.15.2+dfsg-1+b1
ii  python3-pyqt5.qtsql 5.15.2+dfsg-1+b1
ii  python3-pyqt5.qtwebchannel  5.15.2+dfsg-1+b1
ii  python3-pyqt5.qtwebengine   5.15.2-1
ii  python3-webob   1:1.8.6-1.1

mnemosyne recommends no packages.

mnemosyne suggests no packages.

-END OF SYSTEM 

Bug#979416: remove test to see if systemd-resolved is running

[積丹尼 Dan Jacobson]

We note in #979417 they also say

MB> Please use resolvectl instead of systemd-resolve. The latter is a
MB> compat symlink which is scheduled to go away.

anyway.

P.S., if systemd-resolved is running,
and usepeerdns writes in /etc/resolv.conf, we now get
$ resolvectl dns
Global: 168.95.192.1 168.95.1.1
Link 2 (enp1s0):
Link 3 (wlp2s0b1):
Link 4 (ppp0):

I.e., please don't test at all if systemd-resolved is running.
It doesn't conflict with usepeerdns writing in /etc/resolv.conf at all:

SYSTEMD-RESOLVED.SERVICE(8) man page says:

   •   Alternatively, /etc/resolv.conf may be managed by other packages,
   in which case systemd-resolved will read it for DNS configuration
   data. In this mode of operation systemd-resolved is consumer rather
   than provider of this configuration file.

   Note that the selected mode of operation for this file is detected
   fully automatically, depending on whether /etc/resolv.conf is a symlink
   to /run/systemd/resolve/resolv.conf or lists 127.0.0.53 as DNS server.

Bug#979439: hunspell-it: Italian spell check cannot recognize simple words

[Alessio Paonessa]

Package: hunspell-it
Version: 1:7.1.0~rc1-1
Severity: normal
X-Debbugs-Cc: livm...@hotmail.com

Dear Maintainer,

the Italian spell check is broken and cannot recognize common words like "di"
or "è" and other terms with apostrophe or accent.

It is possible to notice the problem simply copying the text of the Universal
Declaration of Human Rights in Italian and trying a spell check on it. It will
highlight in applications like LibreOffice or Gedit some part of the text even
if it is right.

Normally I should expect no mistake in the Declaration.

If I try to use aspell-it in Gedit, the terms are correctly checked. Also the
AppImage version of LibreOffice is not affected. My Debian version is Bullseye
freshly updated.

Thank you in advance,

Best Regards



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

Kernel: Linux 5.9.0-5-amd64 (SMP w/12 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 hunspell-it depends on:
ii  dictionaries-common  1.28.3

hunspell-it recommends no packages.

Versions of packages hunspell-it suggests:
ii  hunspell1.7.0-3
ii  libreoffice-writer  1:7.1.0~rc1-1

-- no debconf information

Bug#979438: gnome-passwordsafe: many SyntaxError messages during installation

[Patrice Duroux]

Package: gnome-passwordsafe
Version: 4.1-1
Severity: normal

Hi,

Here they are:

# apt install gnome-passwordsafe
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  gnome-passwordsafe
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 366 kB of archives.
After this operation, 1 298 kB of additional disk space will be used.
Get:1 https://deb.debian.org/debian sid/main amd64 gnome-passwordsafe all 4.1-1
[366 kB]
Fetched 366 kB in 0s (942 kB/s)
Selecting previously unselected package gnome-passwordsafe.
(Reading database ... 401455 files and directories currently installed.)
Preparing to unpack .../gnome-passwordsafe_4.1-1_all.deb ...
Unpacking gnome-passwordsafe (4.1-1) ...
Setting up gnome-passwordsafe (4.1-1) ...
Failed to byte-compile /usr/lib/python3/dist-
packages/passwordsafe/color_widget.py:   File "/usr/lib/python3/dist-
packages/passwordsafe/color_widget.py", line 2
from __future__ import annotations
^
SyntaxError: future feature annotations is not defined

Failed to byte-compile /usr/lib/python3/dist-
packages/passwordsafe/custom_keypress_handler.py:   File
"/usr/lib/python3/dist-packages/passwordsafe/custom_keypress_handler.py"
, line 2
from __future__ import annotations
^
SyntaxError: future feature annotations is not defined

Failed to byte-compile /usr/lib/python3/dist-
packages/passwordsafe/database_settings_dialog.py:   File
"/usr/lib/python3/dist-packages/passwordsafe/database_settings_dialog.p
y", line 2
from __future__ import annotations
^
SyntaxError: future feature annotations is not defined

Failed to byte-compile /usr/lib/python3/dist-
packages/passwordsafe/entry_page.py:   File "/usr/lib/python3/dist-
packages/passwordsafe/entry_page.py", line 2
from __future__ import annotations
^
SyntaxError: future feature annotations is not defined

Failed to byte-compile /usr/lib/python3/dist-
packages/passwordsafe/entry_row.py:   File "/usr/lib/python3/dist-
packages/passwordsafe/entry_row.py", line 2
from __future__ import annotations
^
SyntaxError: future feature annotations is not defined

Failed to byte-compile /usr/lib/python3/dist-
packages/passwordsafe/group_row.py:   File "/usr/lib/python3/dist-
packages/passwordsafe/group_row.py", line 2
from __future__ import annotations
^
SyntaxError: future feature annotations is not defined

Failed to byte-compile /usr/lib/python3/dist-
packages/passwordsafe/notes_dialog.py:   File "/usr/lib/python3/dist-
packages/passwordsafe/notes_dialog.py", line 2
from __future__ import annotations
^
SyntaxError: future feature annotations is not defined

Failed to byte-compile /usr/lib/python3/dist-
packages/passwordsafe/password_entry_row.py:   File "/usr/lib/python3/dist-
packages/passwordsafe/password_entry_row.py", line 2
from __future__ import annotations
^
SyntaxError: future feature annotations is not defined

Failed to byte-compile /usr/lib/python3/dist-
packages/passwordsafe/password_generator_popover.py:   File
"/usr/lib/python3/dist-packages/passwordsafe/password_generator_popov
er.py", line 2
from __future__ import annotations
^
SyntaxError: future feature annotations is not defined

Failed to byte-compile /usr/lib/python3/dist-
packages/passwordsafe/properties_dialog.py:   File "/usr/lib/python3/dist-
packages/passwordsafe/properties_dialog.py", line 3
from __future__ import annotations
^
SyntaxError: future feature annotations is not defined

Failed to byte-compile /usr/lib/python3/dist-
packages/passwordsafe/references_dialog.py:   File "/usr/lib/python3/dist-
packages/passwordsafe/references_dialog.py", line 2
from __future__ import annotations
^
SyntaxError: future feature annotations is not defined

Failed to byte-compile /usr/lib/python3/dist-packages/passwordsafe/search.py:
File "/usr/lib/python3/dist-packages/passwordsafe/search.py", line 2
from __future__ import annotations
^
SyntaxError: future feature annotations is not defined

Failed to byte-compile /usr/lib/python3/dist-
packages/passwordsafe/selection_ui.py:   File "/usr/lib/python3/dist-
packages/passwordsafe/selection_ui.py", line 2
from __future__ import annotations
^
SyntaxError: future feature annotations is not defined

Failed to byte-compile /usr/lib/python3/dist-
packages/passwordsafe/unlocked_database.py:   File "/usr/lib/python3/dist-
packages/passwordsafe/unlocked_database.py", line 3
from __future__ import annotations
^
SyntaxError: future feature annotations is not defined



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

Kernel: Linux 5.10.0-1-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set

Bug#979378: [Pkg-utopia-maintainers] Bug#979378: network-manager should drop unused Build-Depends

[Michael Biebl]

Hi Helmut,

thanks a lot for the patch

Am 05.01.21 um 22:56 schrieb Helmut Grohne:

Source: network-manager
Version: 1.28.0-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

network-manager has a number of Build-Depends and is involved in
dependency cycles relevant to architecture bootstrap. Instead of looking
into such cycles, a simpler measure is looking into entirely unused
Build-Depends. As it happens, network-manager has those.

According to debian/changelog, libyaml-perl was added to build the
documentation. At this point nothing in the source mentions it in any
way. I think it can be safely dropped.


I guess libyaml-perl and perl can be dropped safely.


The NEWS file kindly explains that since version 1.24,
libpolkit-agent-1-dev and libpolkit-gobject-1-dev are no longer needed.
While meson.build and configure.ac still check for polkit-agent, they're
completely unused otherwise and network-manager now interacts with
polkit via dbus and its own abstraction only.



libpolkit-gobject-1-dev is no longer needed and can be dropped safely. 
libpolkit-agent-1-dev is still used to get the polkit package prefix:


POLKIT_PACKAGE_PREFIX=`$PKG_CONFIG --variable=prefix polkit-agent-1`

which is later used in

clients/common/nm-polkit-listener.c:POLKIT_PACKAGE_PREFIX 
"/lib/polkit-1/polkit-agent-helper-1",


There is a hard-coded fallback, but I'd rather keep the 
libpolkit-agent-1-dev Build-Depends.


Regards,
Michael



OpenPGP_signature
Description: OpenPGP digital signature

Bug#971309: ansible: diff for NMU version 2.9.16+dfsg-1.1

[Lee Garrett]

Hi Sebastian,

thanks, I acknowledge the NMU. I'm in the process of packaging ansible
2.10.x which will already contain the fix. So feel free to consider this
bug closed.

Regards,
Lee

On Wed, 6 Jan 2021 12:07:18 +0100 Sebastian Ramacher
 wrote:
> Control: tags 971309 + patch
> Control: tags 971309 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for ansible (versioned as 2.9.16+dfsg-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
> 
> Cheers
> -- 
> Sebastian Ramacher

Bug#979429: RFS: node-gulp-tsb/4.0.5-1 [ITP] -- node-gulp-tsb

[Andrei POPESCU]

Control: reassign -1 sponsorship-requests

On Mi, 06 ian 21, 16:17:38, VIVEK K J wrote:
> Package: node-gulp-tsb
> Severity: wishlist
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "node-gulp-tsb":
> 
> * Package name : node-gulp-tsb
> Version : 4.0.5-1
> Upstream Author : Johannes Rieken 
> * URL : https://github.com/jrieken/gulp-tsb
> * License : Expat
> * Vcs : https://salsa.debian.org/vivekkj/node-gulp-tsb
> Section : Javascript
> 
> It builds those binary packages:
> 
> node-gulp-tsb
> 
> To access further information about this package, please visit the following 
> URL:
> 
> https://www.npmjs.com/package/gulp-tsb
> 
> This is a part of HedgeDoc packaging[1]
> 
> Regards,
> 
> Vivek K J
> 
> [1] - https://wiki.debian.org/Javascript/Nodejs/Tasks/HedgeDoc

Reassigning to correct (pseudo-)package.

Kind regards,
Andrei
-- 
Looking after bugs assigned to unknown or inexistent packages


signature.asc
Description: PGP signature

Bug#979312: vokoscreen-ng: Segmentation fault when screenAdded

[Thiago Andrade]

severity 979312 important
retitle 979312 vokoscreen-ng: Segmentation fault when install qt5dxcb-plugin
forwarded 979312 https://github.com/vkohaupt/vokoscreenNG/issues/129

thanks

The bug is really from vokoscreen-ng and has already been forwarded to 
the upstream.
As it does not affect the entire functioning of the program, I down the 
severity to important.

Thanks.


--
...
⢀⣴⠾⠻⢶⣦⠀ Thiago Andrade Marques
⣾⠁⢰⠒⠀⣿⡁ GPG: 4096R/F8CDB08B
⢿⡄⠘⠷⠚⠋⠀ GPG Fingerprint: 1D38 EE3C 624F 955C E1FA  3C85 5A30 3591 F8CD B08B
⠈⠳⣄

Bug#979437: zfsutils-linux: please install zpool and zfs binaries in [/usr]/bin instead of /sbin

[Andrei POPESCU]

Package: zfsutils-linux
Version: 0.8.6-1
Severity: wishlist
X-Debbugs-Cc: andreimpope...@gmail.com

Hello,

Various 'zpool' and 'zfs' sub-commands seem to work fine also for 
regular users (e.g. 'zpool status' and zpool/zfs 'get', list', etc.)

It would be nice to have them in the user's default path though (same as 
e.g. systemctl), probably in /usr/bin (due to the merged /usr 
transition).


Kind regards,
Andrei


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 5.9.0-5-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CRAP, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.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 zfsutils-linux depends on:
ii  libblkid12.36.1-4
ii  libc62.31-9
ii  libnvpair1linux  0.8.6-1
ii  libuuid1 2.36.1-4
ii  libuutil1linux   0.8.6-1
ii  libzfs2linux 0.8.6-1
ii  libzpool2linux   0.8.6-1
ii  python3  3.9.1-1

Versions of packages zfsutils-linux recommends:
ii  lsb-base11.1.0
ii  zfs-dkms [zfs-modules]  0.8.6-1
pn  zfs-zed 

Versions of packages zfsutils-linux suggests:
ii  nfs-kernel-server   1:1.3.4-4
pn  samba-common-bin
pn  zfs-initramfs | zfs-dracut  

-- Configuration Files:
/etc/sudoers.d/zfs [Errno 13] Permission denied: '/etc/sudoers.d/zfs'

-- no debconf information

Bug#979355: src:sphinx-rtd-theme: embeds several Sass libraries that should be packaged separately

[Dmitry Shachnev]

Control: block -1 by 979404

Hi again Jonas!

On Tue, Jan 05, 2021 at 09:01:40PM +0100, Jonas Smedegaard wrote:
> > Yes, it cannot use the newer release because Wyrm is incompatible with 
> > it:
> >
> > https://github.com/snide/wyrm/issues/12
>
> That one concretely seems easy fixable - but that's easy to say, I know
> :-)

I just noticed that you already packaged all three dependencies and uploaded
them to NEW. Thanks a lot for that — when you suggested me to file RFPs
I definitely did not expect such speed :)

Now, you say that it will be easy to port Wyrm to new Bourbon. Actually the
current construction is quite fragile because of inter-dependencies: not only
Wyrm needs to be switched to new Bourbon or Neat, but also sphinx-rtd-theme
itself at the same time.

My knowledge of SCSS is minimal so I can only say that patches are welcome.

--
Dmitry Shachnev


signature.asc
Description: PGP signature