Bug#968218: ndiswrapper-dkms: Fails to build for kernel 4.19 and 5.6

[Abigaile Johannesburg]

Package: ndiswrapper-dkms
Version: 1.60-8
Severity: normal

Dear Maintainer,

   * What led up to the situation?

 I was installing ndiswrapper as the last resort in order to use a Broadcom 
802.11ac wireless adapter BCM943460MC_3 rev 31.
  
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

 ndiswrapper-dkms failed to build with both kernel 4.19.10 and 5.6.

   * What was the outcome of this action?

 apt-get install spit out

Error! Bad return status for module build on kernel: 5.6.0-0.bpo.2-rt-amd64 
(x86_64)
Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information.
dpkg: error processing package ndiswrapper-dkms (--configure):
installed ndiswrapper-dkms package post-installation script subprocess returned 
error exit status 10
Errors were encountered while processing:
ndiswrapper-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

 The aforementioned make.log file complained about a missing struct member 
cpus_allowed.

In file included from /var/lib/dkms/ndiswrapper/1.60/build/crt.c:16:
/var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h: In function ‘raise_irql’:
In file included from /var/lib/dkms/ndiswrapper/1.60/build/hal.c:16:
/var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h: In function ‘raise_irql’:
/var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:112:40: error: ‘struct 
task_struct’ has no member named ‘cpus_allowed’; did you mean ‘nr_cpus_allowed’?
#define tsk_cpus_allowed(tsk) (&(tsk)->cpus_allowed)
    ^~~~
/var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:658:36: note: in expansion of 
macro ‘tsk_cpus_allowed’
  cpumask_copy(>cpus_allowed, tsk_cpus_allowed(current));
    ^~~~
/var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:112:40: error: ‘struct 
task_struct’ has no member named ‘cpus_allowed’; did you mean ‘nr_cpus_allowed’?
#define tsk_cpus_allowed(tsk) (&(tsk)->cpus_allowed)
    ^~~~
/var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:658:36: note: in expansion of 
macro ‘tsk_cpus_allowed’
  cpumask_copy(>cpus_allowed, tsk_cpus_allowed(current));
    ^~~~
In file included from /var/lib/dkms/ndiswrapper/1.60/build/ndis.h:19,
 from /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.h:19,
 from /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.c:28:
/var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h: In function ‘raise_irql’:
/var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:112:40: error: ‘struct 
task_struct’ has no member named ‘cpus_allowed’; did you mean ‘nr_cpus_allowed’?
#define tsk_cpus_allowed(tsk) (&(tsk)->cpus_allowed)
    ^~~~
/var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:658:36: note: in expansion of 
macro ‘tsk_cpus_allowed’
  cpumask_copy(>cpus_allowed, tsk_cpus_allowed(current));
    ^~~~
make[2]: *** 
[/usr/src/linux-headers-5.6.0-0.bpo.2-common-rt/scripts/Makefile.build:273: 
/var/lib/dkms/ndiswrapper/1.60/build/hal.o] Error 1
make[2]: *** Waiting for unfinished jobs
make[2]: *** 
[/usr/src/linux-headers-5.6.0-0.bpo.2-common-rt/scripts/Makefile.build:273: 
/var/lib/dkms/ndiswrapper/1.60/build/crt.o] Error 1
In file included from /var/lib/dkms/ndiswrapper/1.60/build/ndis.h:19,
 from /var/lib/dkms/ndiswrapper/1.60/build/loader.c:16:
/var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h: In function ‘raise_irql’:
/var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:112:40: error: ‘struct 
task_struct’ has no member named ‘cpus_allowed’; did you mean ‘nr_cpus_allowed’?
#define tsk_cpus_allowed(tsk) (&(tsk)->cpus_allowed)
    ^~~~
/var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:658:36: note: in expansion of 
macro ‘tsk_cpus_allowed’
  cpumask_copy(>cpus_allowed, tsk_cpus_allowed(current));
    ^~~~
/var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.c: In function 
‘set_ndis_auth_mode’:
/var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.c:702:25: warning: this statement 
may fall through [-Wimplicit-fallthrough=]
   wnd->iw_auth_key_mgmt = IW_AUTH_KEY_MGMT_PSK;
/var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.c:703:2: note: here
  case Ndis802_11AuthModeWPANone:
  ^~~~
make[2]: *** 
[/usr/src/linux-headers-5.6.0-0.bpo.2-common-rt/scripts/Makefile.build:273: 
/var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o] Error 1
make[2]: *** 
[/usr/src/linux-headers-5.6.0-0.bpo.2-common-rt/scripts/Makefile.build:273: 
/var/lib/dkms/ndiswrapper/1.60/build/loader.o] Error 1
make[1]: *** [/usr/src/linux-headers-5.6.0-0.bpo.2-common-rt/Makefile:1704: 
/var/lib/dkms/ndiswrapper/1.60/build] Error 2
make: *** [/usr/src/linux-headers-5.6.0-0.bpo.2-common-rt/Makefile:180: 
sub-make] Error 2

   * What outcome did you expect instead?

 Had it been a 

Bug#966929: Most likely fixed in sphinx (2.4.3-5)

[Sebastiaan Couwenberg]

A smiliar issue was reported for mapproxy in #966979, which was not an
issue in mapproxy but in sphinx, and fixed in sphinx (2.4.3-5).

I have not tested the build of this package, but the dh_sphinxdoc issue
is mostl likely fixed with sphinx (2.4.3-5) as well.

Kind Regards,

Bas

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

Bug#968223: libsimpleini successfully cross builds a package with the wrong multiarch libdir

[Helmut Grohne]

Source: libsimpleini
Version: 4.17+dfsg-6
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

libsimpleini successfully cross builds a package that uses the build
architecture multiarch libdir. This is due to dh_auto_install not
passing cross tools to make. Thus $(CC) --print-multiarch yields the
build architecture triplet. Please consider applying the attached patch
to fix that.

Helmut
diff --minimal -Nru libsimpleini-4.17+dfsg/debian/changelog 
libsimpleini-4.17+dfsg/debian/changelog
--- libsimpleini-4.17+dfsg/debian/changelog 2020-07-17 18:41:12.0 
+0200
+++ libsimpleini-4.17+dfsg/debian/changelog 2020-08-11 07:16:26.0 
+0200
@@ -1,3 +1,10 @@
+libsimpleini (4.17+dfsg-6.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix cross misbuild: use correct multiarch libdir. (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 11 Aug 2020 07:16:26 +0200
+
 libsimpleini (4.17+dfsg-6) unstable; urgency=medium
 
   * Add build libicu-dev for libsimpleini-dev
diff --minimal -Nru libsimpleini-4.17+dfsg/debian/rules 
libsimpleini-4.17+dfsg/debian/rules
--- libsimpleini-4.17+dfsg/debian/rules 2020-07-17 18:41:12.0 +0200
+++ libsimpleini-4.17+dfsg/debian/rules 2020-08-11 07:16:24.0 +0200
@@ -7,6 +7,7 @@
 export DEB_CFLAGS_MAINT_APPEND  = -Wall -pedantic
 export DEB_LDFLAGS_MAINT_APPEND =
 
+include /usr/share/dpkg/architecture.mk
 include /usr/share/dpkg/pkg-info.mk
 
 export VERSION = $(shell echo $(DEB_VERSION_UPSTREAM) | sed 's/+[a-z]*//')
@@ -14,3 +15,6 @@
 
 %:
dh $@ --with pkgkde-symbolshelper
+
+override_dh_auto_install:
+   dh_auto_install -- MULTIARCH=$(DEB_HOST_MULTIARCH)

Bug#968217: python is priority:standard but not installable

[Matthias Klose]

On 8/11/20 2:04 AM, Johannes 'josch' Schauer wrote:
> Package: python
> Version: 2.7.17-2
> Severity: grave
> Justification: renders package unusable
> 
> Hi,
> 
> the python package is currently uninstallable in Debian unstable:

yes

> Maybe this is intentional because of the imminent removal of python 2.
> What is problematic here is, that python is also priority:standard. My
> package mmdebstrap is a debootstrap replacement and in addition to being
> able to install packages with priorities required and important, it can
> also install all packages with priority standard. If a package from the
> priority:standard set is not installable, then this also breaks the unit
> tests and autopkgtest of mmdebstrap and thus, python not being
> installable is currently blocking my mmdebstrap development. I see
> several ways to resolve this:
> 
>  - fix the installability problem (there seems to be a version mismatch)

no, you can't fix that in buster.

>  - remove the python package

yes, that's the goal. However filing an RC bug report prevents migration of this
package once it's migratable.

>  - adjust the priority to something less important than "standard"

you should file a bug report for the override, not the package.

>  - add a rule to mmdebstrap to ignore a package named python

I don't know mmdebstrap. But if you can work around that, please do.

> Since the uninstallability has now been a thing for over a week, I'm
> filing this bug to inquire about the best way forward.

yes, and always RC severity in the first place...

Bug#968221: rsyslog: Enable clickhouse module

[Nathan McSween]

Package: rsyslog
Version: 8.1901.0-1
Severity: wishlist

Dear Maintainer,

Please enable clickhouse support, this could be bunched into the other
modules that require libcurl as well.

Bug#968220: apt: 'apt source' fails: Data left in buffer

[Piotr Engelking]

Package: apt
Version: 2.1.9
Severity: normal

The 'apt source' command fails to download package sources:

$ apt source hello
Reading package lists... Done
Need to get 733 kB of source archives.
Get:1 https://ftp.icm.edu.pl/packages/linux-debian bullseye/main hello
2.10-2 (dsc) [1335 B]
Err:1 https://ftp.icm.edu.pl/packages/linux-debian bullseye/main hello
2.10-2 (dsc)
  Data left in buffer [IP: 193.219.28.2 443]
Get:2 https://ftp.icm.edu.pl/packages/linux-debian bullseye/main hello
2.10-2 (tar) [726 kB]
Get:3 https://ftp.icm.edu.pl/packages/linux-debian bullseye/main hello
2.10-2 (diff) [6132 B]
Err:3 https://ftp.icm.edu.pl/packages/linux-debian bullseye/main hello
2.10-2 (diff)
  Data left in buffer [IP: 193.219.28.2 443]
Fetched 726 kB in 1s (505 kB/s)
E: Failed to fetch
https://ftp.icm.edu.pl/packages/linux-debian/pool/main/h/hello/hello_2.10-2.dsc
 Data left in buffer [IP: 193.219.28.2 443]
E: Failed to fetch
https://ftp.icm.edu.pl/packages/linux-debian/pool/main/h/hello/hello_2.10-2.debian.tar.xz
 Data left in buffer [IP: 193.219.28.2 443]
E: Failed to fetch some archives.
$ ls -log hello_*
-rw-r--r-- 1  0 May 13  2019 hello_2.10-2.debian.tar.xz
-rw-r--r-- 1  0 May 13  2019 hello_2.10-2.dsc
-rw-r--r-- 1 725946 Mar 22  2015 hello_2.10.orig.tar.gz
$

Using the '-o Acquire::https::Pipeline-Depth=0' option makes no difference.

Other programs download the files successfully without a complaint.


-- Package-specific info:

-- /etc/apt/sources.list.d/debian.sources --

Types: deb deb-src
URIs: https://ftp.icm.edu.pl/packages/linux-debian/
Suites: bullseye sid experimental
Components: main contrib non-free
Signed-By: /etc/apt/trusted.gpg.d/debian-archive-buster-automatic.gpg
Description: Debian

Types: deb deb-src
URIs: https://deb.debian.org/debian-security/
Suites: bullseye-security
Components: main contrib non-free
Signed-By: /etc/apt/trusted.gpg.d/debian-archive-buster-security-automatic.gpg
Description: Debian security updates


-- /etc/apt/sources.list.d/local.sources --

Types: deb
URIs: file:/usr/src/deb/
Suites: /
Trusted: yes
Description: local


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

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

Versions of packages apt depends on:
ii  adduser 3.118
ii  debian-archive-keyring  2019.1
ii  gpgv2.2.20-1
ii  libapt-pkg6.0   2.1.9
ii  libc6   2.31-2
ii  libgcc-s1   10.1.0-6
ii  libgnutls30 3.6.14-2+b1
ii  libseccomp2 2.4.3-1+b1
ii  libstdc++6  10.1.0-6
ii  libsystemd0 246-2

Versions of packages apt recommends:
ii  ca-certificates  20200601

Versions of packages apt suggests:
ii  apt-doc  2.1.9
pn  aptitude | synaptic | wajig  
ii  dpkg-dev 1.20.5
ii  gnupg2.2.20-1
pn  powermgmt-base   

-- no debconf information

Bug#967143: Python3 update

[Francisco M Neto]

I have reached out to the gnumeric folks; they say a new version
including python3 support should be out in a couple of months. See 
https://gitlab.gnome.org/GNOME/gnumeric/-/issues/419


[]'s,
Francisco M Neto


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

Bug#968219: ITP: openpbs -- An HPC workload manager and job scheduler for desktops, clusters, and clouds.

[Mo Zhou]

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

* Package name: openpbs
  Version : 20.0.1
  Upstream Author : Name 
* URL : http://www.example.org/
* License : AGPL-3
  Programming Lang: C, python, shell
  Description : An HPC workload manager and job scheduler for desktops, 
clusters, and clouds.


I'm wondering why it is absent in debian.

Bug#791676: libmpich-dev 3.4~a2+really3.3.2-2 has broken Fortran due to gfortran-10 specific flags

[Drew Parsons]

On 2020-08-11 09:46, Drew Parsons wrote:

Thanks Jed.  I think you're replying here in response to discussion
raised elsewhere.  Could you provide a url link if its publicly
accessible so we can catch the rest of the context?


Oh wait, I'm wrong aren't I?  Your reply is to Christian Engwer's 
question in Debian Bug#791676 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791676)


The glitch with mpifort a.f90 and gfortran-10/gfortran-9 might be a 
temporary problem.  We're still in the transition from gcc-9 to gcc-10.  
"mpifort a.f90" succeeds in debian unstable.  The problem here is that 
the gfortran package is 1.185.1 (defaulting to gcc-9) in debian testing, 
but 1.188 (gcc-10) in debian unstable.  The transition is held up by 
seqan, which is failing tests (see 
https://tracker.debian.org/pkg/gcc-defaults)


Since our default MPI is OpenMPI, we didn't catch the inconsistency in 
mpich soon enough. mpich 3.4~a2+really3.3.2-2 was recently built against 
gcc-10, but its gfortran dependency was not strict and so it migrated 
into debian testing ahead of gfortran (with the gfortran-10 default).


Drew

Bug#791676: libmpich-dev 3.4~a2+really3.3.2-2 has broken Fortran due to gfortran-10 specific flags

[Drew Parsons]

Thanks Jed.  I think you're replying here in response to discussion 
raised elsewhere.  Could you provide a url link if its publicly 
accessible so we can catch the rest of the context?


Drew


On 2020-08-11 06:43, Jed Brown wrote:
I'm replying here because I think it's part of this bug, but more 
severe

in practice.  It was evidently built with gfortran-10, but depends on
gfortran-9, which doesn't recognize these arguments.

$ cat > a.f90
program main
end
^D
$ mpifort a.f90
f95: error: unrecognized command line option ‘-fallow-invalid-boz’
f95: error: unrecognized command line option
‘-fallow-argument-mismatch’; did you mean ‘-Wno-argument-mismatch’?

This can be worked around if one has gfortran-10 installed:

$ MPICH_CC=gfortran-10 mpifort a.f90
$


$ mpifort -show
f95 -O2
-fdebug-prefix-map=/build/mpich-Aiaw9P/mpich-3.4~a2+really3.3.2=.
-fstack-protector-strong -fallow-invalid-boz -fallow-argument-mismatch
-Wl,-z,relro -I/usr/include/x86_64-linux-gnu/mpich
-I/usr/include/x86_64-linux-gnu/mpich -L/usr/lib/x86_64-linux-gnu
-lmpichfort -lmpich

Bug#968200: missing files for bblxml features

[Norbert Preining]

Hi Hilmar,

On Mon, 10 Aug 2020, Hilmar Preuße wrote:
> It is contained in the orig.tar.gz one gets from github.
> 
> @Norbert: I guess you us the file from CTAN, where the file is missing.
> Correct?

No, I am using the releas tarballs from sourceforge.

The problem with the github packages is that they cannot be used for
building as is AFAIR, the release tarball preparation requires a few
more steps it seems.

We need to report upstream. I am currently travelling will try to do the
next days.

For now we can include it using a debian/patch I guess.

Best

Norbert

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

Bug#968210: statsmodels: arm* test failures/crashes

[Rebecca N. Palmer]

Package: python3-statsmodels
Version: 0.11.1-4
Severity: serious

arm64 fail in TestZeroInflatedModel_probit.test_fit_regularized:

https://buildd.debian.org/status/fetch.php?pkg=statsmodels=arm64=0.11.1-4=1597051632=0
https://ci.debian.net/packages/s/statsmodels/testing/arm64/

From the CI results, this started failing with scipy 1.5.  It also 
fails in Ubuntu -proposed.


I don't yet know if this is an actual problem for users, or a test 
that's too strict to be reliable.  It hasn't obviously been noticed or 
fixed upstream, but I haven't actually tested whether upstream is affected.


armel test crash:

https://buildd.debian.org/status/fetch.php?pkg=statsmodels=armel=0.11.1-4=1597055709=0

This doesn't crash when just that test file is run in statsmodels 
0.11.1-3 qemu-armel, but this isn't 100% proof that -4 (rather than a 
dependency) caused it.

Bug#968208: pandas: TestMoments.test_rolling_quantile_interpolation_options fails on i386 - rounding issue

[Rebecca N. Palmer]

Package: python3-pandas
Version: 0.25.3+dfsg2-4
Severity: serious

One test fails on i386 with a 1-in-last-place difference, probably due 
to different rounding (x87 extra precision?).


https://buildd.debian.org/status/fetch.php?pkg=pandas=i386=0.25.3%2Bdfsg2-4=1597048961=0

Bug#968217: python is priority:standard but not installable

[Johannes 'josch' Schauer]

Package: python
Version: 2.7.17-2
Severity: grave
Justification: renders package unusable

Hi,

the python package is currently uninstallable in Debian unstable:

output-version: 1.2
report:
 -
  package: python
  version: 2.7.17-2
  architecture: amd64
  status: broken
  reasons:
   -
missing:
 pkg:
  package: libpython-stdlib
  version: 2.7.17-2
  architecture: amd64
  unsat-dependency: libpython2-stdlib (= 2.7.17-2)
 depchains:
  -
   depchain:
-
 package: python
 version: 2.7.17-2
 architecture: amd64
 depends: libpython-stdlib (= 2.7.17-2)

Maybe this is intentional because of the imminent removal of python 2.
What is problematic here is, that python is also priority:standard. My
package mmdebstrap is a debootstrap replacement and in addition to being
able to install packages with priorities required and important, it can
also install all packages with priority standard. If a package from the
priority:standard set is not installable, then this also breaks the unit
tests and autopkgtest of mmdebstrap and thus, python not being
installable is currently blocking my mmdebstrap development. I see
several ways to resolve this:

 - fix the installability problem (there seems to be a version mismatch)
 - remove the python package
 - adjust the priority to something less important than "standard"
 - add a rule to mmdebstrap to ignore a package named python

Since the uninstallability has now been a thing for over a week, I'm
filing this bug to inquire about the best way forward.

Thanks!

cheers, josch

Bug#966416: RM: argyll -- ROM; RC-buggy; abandoned upstream

[Sean Whitton]

Hello Jörg,

On Fri 07 Aug 2020 at 12:21PM +02, Jörg Frings-Fürst wrote:

> the Upstream Release 2.1.2 has the same errors. Buildlog is attached.

Thanks for confirming.

Please remove the 'moreinfo' tag once there are no more reverse
dependencies.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#968216: roundcube: CVE-2020-16145: XSS vulnerability via HTML messages with malicious svg or math content

[Guilhem Moulin]

Source: roundcube
Severity: important
Tags: security
Control: found -1 1.4.7+dfsg.2-1
Control: found -1 1.3.14+dfsg.1-1~deb10u1
Control: found -1 1.2.3+dfsg.1-4+deb9u5

In a recent post roundcube webmail upstream has announced the following
security fix:

Cross-site scripting (XSS) via HTML messages with malicious svg
or math content (CVE-2020-16145)

1.2.x, 1.3.x and 1.4.x branches are affected.  Upstream fix:

1.4.x 
https://github.com/roundcube/roundcubemail/commit/a71bf2e8d4a64ff2c83fdabc1e8cb0c045a41ef4
1.3.x 
https://github.com/roundcube/roundcubemail/commit/d44ca2308a96576b88d6bf27528964d4fe1a6b8b
1.2.x 
https://github.com/roundcube/roundcubemail/commit/589d36010048300ed39f4887aab1afd3ae98d00e

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#791676: libmpich-dev 3.4~a2+really3.3.2-2 has broken Fortran due to gfortran-10 specific flags

[Jed Brown]

I'm replying here because I think it's part of this bug, but more severe
in practice.  It was evidently built with gfortran-10, but depends on
gfortran-9, which doesn't recognize these arguments.

$ cat > a.f90
program main
end
^D
$ mpifort a.f90 
f95: error: unrecognized command line option ‘-fallow-invalid-boz’
f95: error: unrecognized command line option ‘-fallow-argument-mismatch’; did 
you mean ‘-Wno-argument-mismatch’?

This can be worked around if one has gfortran-10 installed:

$ MPICH_CC=gfortran-10 mpifort a.f90
$


$ mpifort -show
f95 -O2 -fdebug-prefix-map=/build/mpich-Aiaw9P/mpich-3.4~a2+really3.3.2=. 
-fstack-protector-strong -fallow-invalid-boz -fallow-argument-mismatch 
-Wl,-z,relro -I/usr/include/x86_64-linux-gnu/mpich 
-I/usr/include/x86_64-linux-gnu/mpich -L/usr/lib/x86_64-linux-gnu -lmpichfort 
-lmpich

Bug#968215: chromium: first installation, error sites and configuration.

[Edwin Carrillo]

Package: chromium
Version: 83.0.4103.116-3+b1
Severity: important
X-Debbugs-Cc: nmochil...@gmail.com

Dear Maintainer,
after new install on 08/10/2020, Debian Testing, 5.7.0-2-686-pae # 1 SMP Debian
5.7.10-1 (2020-07-26) i686. After installing Chromium, it does not allow access
to any site or settings, Internet access is normal. It shows error code 256.




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

Kernel: Linux 5.7.0-2-686-pae (SMP w/2 CPU threads)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en
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  83.0.4103.116-3+b1
ii  libasound2   1.2.2-2.3
ii  libatk-bridge2.0-0   2.34.1-3
ii  libatk1.0-0  2.36.0-2
ii  libatomic1   10.1.0-6
ii  libatspi2.0-02.36.0-3
ii  libavcodec58 10:4.3.1-dmo2
ii  libavformat5810:4.3.1-dmo2
ii  libavutil56  10:4.3.1-dmo2
ii  libc62.31-2
ii  libcairo21.16.0-4
ii  libcups2 2.3.3-2
ii  libdbus-1-3  1.12.20-1
ii  libdrm2  2.4.102-1
ii  libevent-2.1-7   2.1.12-stable-1
ii  libexpat12.2.9-1
ii  libflac8 1.3.3-1
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.2+dfsg-3
ii  libgbm1  20.1.4-1
ii  libgcc-s110.1.0-6
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-5
ii  libglib2.0-0 2.64.4-1
ii  libgtk-3-0   3.24.20-1
ii  libharfbuzz0b2.6.4-1+b1
ii  libicu67 67.1-3
ii  libjpeg62-turbo  1:2.0.5-1.1
ii  libjsoncpp1  1.7.4-3.1
ii  liblcms2-2   2.9-4+b1
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.27-1
ii  libnss3  2:3.55-1
ii  libopenjp2-7 2.3.1-1
ii  libopus0 1.3-1+b1
ii  libpango-1.0-0   1.44.7-4
ii  libpangocairo-1.0-0  1.44.7-4
ii  libpng16-16  1.6.37-2
ii  libpulse013.0-5
ii  libre2-8 20200801+dfsg-1
ii  libsnappy1v5 1.1.8-1
ii  libstdc++6   10.1.0-6
ii  libvpx6  1.9.0-dmo1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libx11-6 2:1.6.10-3
ii  libx11-xcb1  2:1.6.10-3
ii  libxcb-dri3-01.14-2
ii  libxcb1  1.14-2
ii  libxcomposite1   1:0.4.5-1
ii  libxcursor1  1:1.2.0-2
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-2
ii  libxi6   2:1.7.10-1
ii  libxml2  2.9.10+dfsg-5+b1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.34-4
ii  libxss1  1:1.2.3-1
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  83.0.4103.116-3+b1

Versions of packages chromium suggests:
pn  chromium-driver  
ii  chromium-l10n83.0.4103.116-3
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  x11-utils  7.7+5
ii  xdg-utils  1.1.3-2

Versions of packages chromium-common recommends:
ii  chromium-sandbox   83.0.4103.116-3+b1
ii  fonts-liberation   1:1.07.4-11
ii  gnome-shell [notification-daemon]  3.36.4-1
ii  libgl1-mesa-dri20.1.4-1
ii  libu2f-udev1.1.10-1
ii  notification-daemon3.20.0-4
ii  system-config-printer  1.5.12-1
ii  upower 0.99.11-2

Versions of packages chromium-sandbox depends on:
ii  libc6  2.31-2

-- no debconf information

Bug#967143: Upstream has moved to python3.

[Francisco M Neto]

Upstream has moved to python3 in commit 8e2f442e[1]. This should be
just a matter of updating the packaging and dependencies, but I'm not
familiar with the package itself (although I'm a regular user of
gnumeric). I'd be willing to help if needed.

[1] 
https://gitlab.gnome.org/GNOME/gnumeric/-/commit/8e2f442e88a82f3a639f7b0ee5cd8760db20b172

[]'s,
Francisco


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

Bug#966470: [Debian-med-packaging] Bug#966470: fix for #966470: biobambam2 autopkgtest failures

[Étienne Mollier]

Control: tags -1 pending

Greetings,

I verified it is safe to remove zlib1g-dev from the biobambam2
package dependencies by running the autopkgtest suite with the
patched libmaus2, which now pulls zlib1g as dependency of
libmaus2-2.  The routine-update also pulled the libmaus patch
level 2.0.743.  The new revision of this library is available on
Salsa:

https://salsa.debian.org/med-team/libmaus2

Thanks John for having brought up the patch and forwarded the
issue upstream.

Kind Regards,
-- 
Étienne Mollier 
Old rsa/3072: 5ab1 4edf 63bb ccff 8b54  2fa9 59da 56fe fff3 882d
New rsa/4096: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/8, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#968212: scheme48 misses source for S48_DETERMINE_BITS_PER_BYTE

[Helmut Grohne]

Source: scheme48
Version: 1.9.2-1
Severity: serious
Justification: missing source

While looking into a build issue with scheme48, I was looking for the
source of S48_DETERMINE_BITS_PER_BYTE as referenced in configure.in.
Unfortunately, I couldn't find the relevant source. Am I missing
something?

Helmut

Bug#968213: pybuild: computed _PYTHON_SYSCONFIGDATA_NAME does not work for -dbg packages

[Helmut Grohne]

Package: dh-python
Version: 4.20200804
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:libpillowfight

Unfortunately, _PYTHON_SYSCONFIGDATA_NAME is wrong again. This time, the
relevant .py file is provided under both locations for the regular
libpython. Unfortunately, this does not cover the libpythonX.Y-dbg
variant.

$ apt-file search _sysconfigdata
libpython2.7-dbg: /usr/lib/python2.7/plat-x86_64-linux-gnu/_sysconfigdata_d.py
libpython2.7-minimal: /usr/lib/python2.7/_sysconfigdata.py
libpython2.7-minimal: 
/usr/lib/python2.7/plat-x86_64-linux-gnu/_sysconfigdata_nd.py
libpython3.8-dbg: /usr/lib/python3.8/_sysconfigdata_d_x86_64-linux-gnu.py
libpython3.8-minimal: /usr/lib/python3.8/_sysconfigdata__x86_64-linux-gnu.py
libpython3.8-stdlib: 
/usr/lib/python3.8/_sysconfigdata__linux_x86_64-linux-gnu.py
libpython3.9-dbg: /usr/lib/python3.9/_sysconfigdata_d_x86_64-linux-gnu.py
libpython3.9-minimal: /usr/lib/python3.9/_sysconfigdata__x86_64-linux-gnu.py
libpython3.9-stdlib: 
/usr/lib/python3.9/_sysconfigdata__linux_x86_64-linux-gnu.py
pypy-lib: /usr/lib/pypy/lib_pypy/_sysconfigdata.py
pypy3-lib: /usr/lib/pypy3/lib_pypy/_sysconfigdata.py
$

As you can see, it is provided as
_sysconfigdata__{DEB_HOST_ARCH_OS}_{DEB_HOST_MULTIARCH} and as
_sysconfigdata__{DEB_HOST_MULTIARCH} for the non-debug variant, but only
the latter for the debug variant.

Therefore, we need to change the computation again. I don't think adding
backwards compatibility for older releases of Python is useful. So I'm
just attaching the patch to make this happen. Please consider applying
it.

Helmut
diff --minimal -Nru dh-python-4.20200804/debian/changelog 
dh-python-4.20200804+nmu1/debian/changelog
--- dh-python-4.20200804/debian/changelog   2020-08-04 10:10:12.0 
+0200
+++ dh-python-4.20200804+nmu1/debian/changelog  2020-08-10 23:37:36.0 
+0200
@@ -1,3 +1,10 @@
+dh-python (4.20200804+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix _PYTHON_SYSCONFIGDATA_NAME again. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 10 Aug 2020 23:37:36 +0200
+
 dh-python (4.20200804) unstable; urgency=medium
 
   [ Scott Kitterman ]
diff --minimal -Nru dh-python-4.20200804/pybuild 
dh-python-4.20200804+nmu1/pybuild
--- dh-python-4.20200804/pybuild2020-03-15 21:00:31.0 +0100
+++ dh-python-4.20200804+nmu1/pybuild   2020-08-10 23:37:27.0 +0200
@@ -81,8 +81,7 @@
 if arch_data['DEB_BUILD_ARCH'] != arch_data['DEB_HOST_ARCH']:
 # support cross compiling Python 3.X extensions, see #892931
 env.setdefault('_PYTHON_SYSCONFIGDATA_NAME',
-   ('_sysconfigdata__{DEB_HOST_ARCH_OS}'
-'_{DEB_HOST_MULTIARCH}').format(**arch_data))
+   '_sysconfigdata__' + 
arch_data["DEB_HOST_MULTIARCH"])
 
 if cfg.system:
 certainty = 99

Bug#968214: ultracopier FTCBFS: missing Build-Depends: qt5-qmake:native for lrelease

[Helmut Grohne]

Source: ultracopier
Version: 1.6.1.3-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

ultracopier fails to cross build from source, because it runs lrelease
on a .pro file without the relevant build dependency on
qt5-qmake:native. Please consider applying the attached patch.

Helmut
diff --minimal -Nru ultracopier-1.6.1.3/debian/changelog 
ultracopier-1.6.1.3/debian/changelog
--- ultracopier-1.6.1.3/debian/changelog2019-02-03 22:37:22.0 
+0100
+++ ultracopier-1.6.1.3/debian/changelog2020-08-10 20:25:23.0 
+0200
@@ -1,3 +1,11 @@
+ultracopier (1.6.1.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Add missing Build-Depends: qt5-qmake:native for lrelease.
+(Closes: #-1)
+
+ -- Helmut Grohne   Mon, 10 Aug 2020 20:25:23 +0200
+
 ultracopier (1.6.1.3-1) unstable; urgency=medium
 
   * New upstream release.
diff --minimal -Nru ultracopier-1.6.1.3/debian/control 
ultracopier-1.6.1.3/debian/control
--- ultracopier-1.6.1.3/debian/control  2019-02-03 22:37:22.0 +0100
+++ ultracopier-1.6.1.3/debian/control  2020-08-10 20:25:22.0 +0200
@@ -2,7 +2,7 @@
 Section: utils
 Priority: optional
 Maintainer: Thomas Preud'homme 
-Build-Depends: debhelper (>= 11), qtbase5-dev, qt5-qmake,
+Build-Depends: debhelper (>= 11), qtbase5-dev, qt5-qmake, qt5-qmake:native,
qttools5-dev-tools
 Standards-Version: 4.3.0
 Homepage: http://ultracopier.first-world.info/

Bug#968211: Update to 0.90.0

[Sebastien Bacher]

Package: libhandy
Version: 0.0.13-2

Hey,

Upstream has some new versions available on
https://ftp.acc.umu.se/pub/GNOME/sources/libhandy/

Could you package 0.90.0 (at least in experimental)?

it's going to be needed for some GNOME 3.38 components


Thanks,

Bug#968209: gnome-shell crashes randomly when closing evince

[Benedikt Ahrens]

I followed the helpful instructions given in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800951#15 and will
post more information when the bug occurs next time.

Bug#968209: gnome-shell crashes randomly when closing evince

[Benedikt Ahrens]

I am sending attached an excerpt of the journal that documents the crash.

-- Logs begin at Mon 2020-08-10 10:53:26 EDT, end at Mon 2020-08-10 16:50:12 
EDT. --
[...]
Aug 10 13:17:01 al2o3 CRON[7660]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
Aug 10 13:17:01 al2o3 CRON[7659]: pam_unix(cron:session): session closed for 
user root
Aug 10 13:17:01 al2o3 gnome-shell[1959]: The program 'gnome-shell' received an 
X Window System error.
 This probably reflects a bug in the 
program.
 The error was 'BadWindow (invalid 
Window parameter)'.
   (Details: serial 25017 error_code 3 
request_code 18 (core protocol) minor_code 0)
   (Note to programmers: normally, X 
errors are reported asynchronously;
that is, you will receive the error 
a while after causing it.
To debug your program, run it with 
the GDK_SYNCHRONIZE environment
variable to change this behavior. 
You can then get a meaningful
backtrace from your debugger if you 
break on the gdk_x_error() function.)
Aug 10 13:17:01 al2o3 org.gnome.Shell.desktop[1959]: == Stack trace for context 
0x558f6ba32230 ==
Aug 10 13:17:01 al2o3 evince[5888]: Error reading events from display: Broken 
pipe
Aug 10 13:17:01 al2o3 solaar[2204]: Error reading events from display: Broken 
pipe
Aug 10 13:17:01 al2o3 evolution-alarm[2193]: Error reading events from display: 
Broken pipe
Aug 10 13:17:02 al2o3 isenkramd[2211]: Error reading events from display: 
Broken pipe
Aug 10 13:17:02 al2o3 evince[7538]: Error flushing display: Broken pipe
Aug 10 13:17:02 al2o3 thunderbird.desktop[1959]: xcb_connection_has_error() 
returned true
Aug 10 13:17:02 al2o3 gnome-session[1928]: gnome-session-binary[1928]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 5
Aug 10 13:17:02 al2o3 pulseaudio[2003]: ICE default IO error handler doing an 
exit(), pid = 2003, errno = 11
Aug 10 13:17:02 al2o3 org.gnome.Shell.desktop[1959]: (EE) failed to read 
Wayland events: Broken pipe
Aug 10 13:17:02 al2o3 gnome-session-binary[1928]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 5
Aug 10 13:17:02 al2o3 org.gnome.SettingsDaemon.Power.desktop[2072]: 
xcb_connection_has_error() returned true
Aug 10 13:17:02 al2o3 gnome-terminal-[3569]: Error reading events from display: 
Broken pipe
Aug 10 13:17:02 al2o3 thunderbird.desktop[1959]: xcb_connection_has_error() 
returned true
Aug 10 13:17:02 al2o3 bluetoothd[942]: Endpoint unregistered: sender=:1.287 
path=/MediaEndpoint/A2DPSource
Aug 10 13:17:02 al2o3 gnome-session-binary[1928]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
Aug 10 13:17:02 al2o3 bluetoothd[942]: Endpoint unregistered: sender=:1.287 
path=/MediaEndpoint/A2DPSink
Aug 10 13:17:02 al2o3 systemd[1907]: pulseaudio.service: Main process exited, 
code=exited, status=1/FAILURE
Aug 10 13:17:02 al2o3 polkitd(authority=local)[840]: Unregistered 
Authentication Agent for unix-session:2 (system bus name :1.214, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8) 
(disconnected from bus)
Aug 10 13:17:02 al2o3 systemd[1907]: pulseaudio.service: Failed with result 
'exit-code'.
Aug 10 13:17:02 al2o3 gsd-media-keys[2118]: gsd-media-keys: Fatal IO error 11 
(Resource temporarily unavailable) on X server :0.
Aug 10 13:17:02 al2o3 firefox-esr[4743]: firefox-esr: Fatal IO error 104 
(Connection reset by peer) on X server :0.
Aug 10 13:17:02 al2o3 gsd-keyboard[2114]: gsd-keyboard: Fatal IO error 11 
(Resource temporarily unavailable) on X server :0.
Aug 10 13:17:02 al2o3 gsd-clipboard[2109]: gsd-clipboard: Fatal IO error 11 
(Resource temporarily unavailable) on X server :0.
Aug 10 13:17:02 al2o3 gsd-color[2108]: gsd-color: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
Aug 10 13:17:02 al2o3 gsd-xsettings[2098]: gsd-xsettings: Fatal IO error 104 
(Connection reset by peer) on X server :0.
Aug 10 13:17:02 al2o3 at-spi-bus-launcher[1992]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
Aug 10 13:17:02 al2o3 at-spi-bus-launcher[1992]:   after 5875 requests 
(5875 known processed) with 0 events remaining.
Aug 10 13:17:02 al2o3 gsd-wacom[2093]: gsd-wacom: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
Aug 10 13:17:02 al2o3 thunderbird[2598]: thunderbird: Fatal IO error 104 
(Connection reset by peer) on X server :0.
Aug 10 13:17:02 al2o3 unknown[2477]: gpaste-daemon: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
Aug 10 13:17:02 al2o3 systemd[1907]: org.gnome.GPaste.service: Main process 
exited, code=exited, status=1/FAILURE
Aug 10 13:17:02 al2o3 systemd[1907]: org.gnome.GPaste.service: 

Bug#924172: www.debian.org: differences under english/ between builds in stretch and buster

[Laura Arjona Reina]

Hi all
Sorry for the long delay to come back to this.

I have tested the workaround proposed by Cyril:

https://salsa.debian.org/webmaster-team/webwml/-/tree/pu/partial-workaround-924172

and arrived to the same conclusions:

* It makes no difference (and thus no harm) when applied in stretch
* In buster, it builds correctly the sitemaps, with no references to
"../english" paths (I tested Spanish and English, and the Spanish
translation seemed also to be complete).

OTOH, now that wml 2.28.0 is packaged in testing (thanks Axel and
Shlomi!), I have installed wml and slice from testing in my buster box,
and tried to build, and found that sitemap.en.html cannot be built (See
error below. But just for the curious, because I think our way to go is
to integrate Cyril's workaround, and with the patch, the files build
correctly with wml 2.28.0).

So I think it's good to accept it and unblock this way the upgrade to
buster of www-master. Later we can file bugs for the not-complete
translations.

Kind regards,
-- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona


--- Error when building sitemap.en.html in a buster machine, but with
wml and slice 2.28.0 (from testing) -- Just for the record, because
we'll use another workaround



wml -q -D CUR_YEAR=2020 -o UNDEFuEN:sitemap.en.html@g+w   -D
CUR_LANG=English -D CUR_ISO_LANG=en -D CUR_LOCALE=en_US.UTF-8 -D
CHARSET=utf-8 \
  ../english/sitemap.wml
ePerl:Error: Perl runtime error (interpreter rc=2)

 Contents of STDERR channel: -
couldn't open ./../index.wml or
/home/larjona/Documentos/debian/www/webwml/english/../index.wml: No such
file or directory
Died at /tmp/0uDhaUPMnJ/wml.tmp1 line 750.
--
** WML:Break: Error in Pass 3 (rc=1).
Died at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 402.

TheWML::Frontends::Wml::Runner::_run_pass(TheWML::Frontends::Wml::Runner=HASH(0x563974ead458),
3, SCALAR(0x56397544aaf0), REF(0x56397544aac0), REF(0x56397544aad8))
called at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 440

TheWML::Frontends::Wml::Runner::_passes_loop(TheWML::Frontends::Wml::Runner=HASH(0x563974ead458))
called at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 727

TheWML::Frontends::Wml::Runner::_output_and_cleanup(TheWML::Frontends::Wml::Runner=HASH(0x563974ead458))
called at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 932

TheWML::Frontends::Wml::Runner::run_with_ARGV(TheWML::Frontends::Wml::Runner=HASH(0x563974ead458),
HASH(0x56397543aed0)) called at /usr/bin/wml line 47
make: *** [Makefile:56: sitemap.en.html] Error 2

Bug#968209: gnome-shell crashes randomly when closing evince

[Benedikt Ahrens]

Package: gnome-shell
Version: 3.30.2-11~deb10u1
Severity: normal

Dear Maintainer,


   * What led up to the situation?

 Closing evince windows randomly makes gnome-shell crash. There is no 
pattern to this behaviour that I have observed.
   
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

 Closing evince windows. It is possible that it is closing the *last* 
evince window (when having multiple evince windows open) that triggers the 
crash.



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

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  evolution-data-server3.30.5-1+deb10u1
ii  gir1.2-accountsservice-1.0   0.6.45-2
ii  gir1.2-atspi-2.0 2.30.0-7
ii  gir1.2-freedesktop   1.58.3-2
ii  gir1.2-gcr-3 3.28.1-1
ii  gir1.2-gdesktopenums-3.0 3.28.1-1
ii  gir1.2-gdm-1.0   3.30.2-3
ii  gir1.2-geoclue-2.0   2.5.2-1
ii  gir1.2-glib-2.0  1.58.3-2
ii  gir1.2-gnomebluetooth-1.03.28.2-4~deb10u1
ii  gir1.2-gnomedesktop-3.0  3.30.2.1-2
ii  gir1.2-gtk-3.0   3.24.5-1
ii  gir1.2-gweather-3.0  3.28.2-2
ii  gir1.2-ibus-1.0  1.5.19-4+deb10u1
ii  gir1.2-mutter-3  3.30.2-9~deb10u1
ii  gir1.2-nm-1.01.14.6-2+deb10u1
ii  gir1.2-nma-1.0   1.8.20-1.1
ii  gir1.2-pango-1.0 1.42.4-8~deb10u1
ii  gir1.2-polkit-1.00.105-25
ii  gir1.2-rsvg-2.0  2.44.10-2.1
ii  gir1.2-soup-2.4  2.64.2-2
ii  gir1.2-upowerglib-1.00.99.10-1
ii  gjs  1.54.3-1
ii  gnome-backgrounds3.30.0-1
ii  gnome-settings-daemon3.30.2-3
ii  gnome-shell-common   3.30.2-11~deb10u1
ii  gsettings-desktop-schemas3.28.1-1
ii  libatk-bridge2.0-0   2.30.0-5
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libcanberra-gtk3-0   0.30-7
ii  libcanberra0 0.30-7
ii  libcroco30.6.12-3
ii  libecal-1.2-19   3.30.5-1+deb10u1
ii  libedataserver-1.2-233.30.5-1+deb10u1
ii  libgcr-base-3-1  3.28.1-1
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libgirepository-1.0-11.58.3-2
ii  libgjs0g 1.54.3-1
ii  libglib2.0-0 2.58.3-2+deb10u2
ii  libglib2.0-bin   2.58.3-2+deb10u2
ii  libgstreamer1.0-01.14.4-1
ii  libgtk-3-0   3.24.5-1
ii  libical3 3.0.4-3
ii  libjson-glib-1.0-0   1.4.4-2
ii  libmutter-3-03.30.2-9~deb10u1
ii  libnm0   1.14.6-2+deb10u1
ii  libpango-1.0-0   1.42.4-8~deb10u1
ii  libpangocairo-1.0-0  1.42.4-8~deb10u1
ii  libpolkit-agent-1-0  0.105-25
ii  libpolkit-gobject-1-00.105-25
ii  libpulse-mainloop-glib0  12.2-4+deb10u1
ii  libpulse012.2-4+deb10u1
ii  libsecret-1-00.18.7-1
ii  libstartup-notification0 0.12-6
ii  libsystemd0  241-7~deb10u4
ii  libx11-6 2:1.6.7-1
ii  libxfixes3   1:5.0.3-1
ii  mutter   3.30.2-9~deb10u1
ii  python3  3.7.3-1

Versions of packages gnome-shell recommends:
ii  bolt  0.7-2
ii  chrome-gnome-shell10.1-5
ii  gdm3  3.30.2-3
ii  gkbd-capplet  3.26.1-1
ii  gnome-control-center  1:3.30.3-2~deb10u1
ii  gnome-user-docs 

Bug#924172: www.debian.org: differences under english/ between builds in stretch and buster

[Laura Arjona Reina]

El 10/8/20 a las 22:47, Laura Arjona Reina escribió:

> 
> So I think it's good to accept it and unblock this way the upgrade to
> buster of www-master. Later we can file bugs for the not-complete
> translations.
> 

This has been done in MR #524:

https://salsa.debian.org/webmaster-team/webwml/-/merge_requests/524

(main commit 83f7cae0178074e5e4f913168b4b42c7be90af13)

Kind regards,
-- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona

Bug#963807: ntp: CVE-2020-15025

[Sorokin Aleksandr]

Please add the following useful information for the vulnerability:

Bug description: https://bugs.ntp.org/show_bug.cgi?id=3661
Patch changeset: 
http://bk.ntp.org/ntp-stable/?PAGE=patch=5e84aa07N2NcL4sE_0dW35Tizc74SA

Regards,
Alexander

Bug#954189: Upload approval for acmetool 0.2 in buster-backports

[Ralph Giles]

On Sun, 2020-08-09 at 20:22 -0400, Peter Colberg wrote:

> Please feel free to go ahead with backporting acmetool and needed
> golang dependencies to buster.

Thanks for the approval, Peter! We'll backport and follow-up with the
go-team if there are issues.

Cheers,
Ralph


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

Bug#966846: Kernel panic (4.19.0-10): RIP __cgroup_bpf_run_filter_skb

[Shane Frasier]

On Mon, 3 Aug 2020 09:55:28 +0200 =?UTF-8?Q?C=c3=a9dric_Dufour?= <
cedric.duf...@ced-network.net> wrote:
> Package: linux-source-4.19
> Version: 4.19.132-1
> Severity: important
>
> Hello,
>
> Since linux-image-4.19.0-10-amd64, I'm facing regular Kernel panics -
"RIP: 0010:__cgroup_bpf_run_filter_skb+0x26d/0x3d0" - resulting in full
(file) *server freeze*.
>
> The issue is pretty well described and summarized in
https://forum.proxmox.com/threads/kernel-5-4-44-causes-system-freeze-on-hp-microserver-gen8.72050/page-2#post-323498
>
> The "culprit" commit - "netprio_cgroup: Fix unlimited memory leak of v2
cgroups" - is indeed included in Debian kernel (4.19) since changelog entry
4.19.131-1
>
> It *seems* there is already a patch proposed upstream (although here for
kernel 4.9): https://lkml.org/lkml/2020/7/20/883
>
> Best regards,
>
> Cédric
>
> --
> Cédric Dufour
>
>

FWIW, I am seeing a very similar issue.  Some Debian 10 AWS instances used
to run Guacamole via Docker recently started randomly freezing up on me.  I
enabled kernel dumps and finally caught one of the machines misbehaving.
Looking at the kdump I see this:
  KERNEL: /usr/lib/debug/vmlinux-4.19.0-10-cloud-amd64
DUMPFILE: dump.202008101612  [PARTIAL DUMP]
CPUS: 2
DATE: Mon Aug 10 16:11:47 2020
  UPTIME: 00:05:44
LOAD AVERAGE: 0.21, 0.11, 0.04
   TASKS: 261
NODENAME: guac.env0.staging.cool.cyber.dhs.gov
 RELEASE: 4.19.0-10-cloud-amd64
 VERSION: #1 SMP Debian 4.19.132-1 (2020-07-24)
 MACHINE: x86_64  (2499 Mhz)
  MEMORY: 4 GB
   PANIC: "BUG: unable to handle kernel NULL pointer dereference at
0010"
 PID: 1453
 COMMAND: "sshd"
TASK: 8a3f695115c0  [THREAD_INFO: 8a3f695115c0]
 CPU: 0
   STATE: TASK_RUNNING (PANIC)

crash> bt
PID: 1453   TASK: 8a3f695115c0  CPU: 0   COMMAND: "sshd"
 #0 [b37740c77800] machine_kexec at 97a4b297
 #1 [b37740c77858] __crash_kexec at 97b0e7dd
 #2 [b37740c77920] crash_kexec at 97b0f62d
 #3 [b37740c77938] oops_end at 97a2907d
 #4 [b37740c77958] no_context at 97a5858e
 #5 [b37740c779b0] __do_page_fault at 97a58c42
 #6 [b37740c77a20] async_page_fault at 982010be
[exception RIP: __cgroup_bpf_run_filter_skb+189]
RIP: 97b94ffd  RSP: b37740c77ad0  RFLAGS: 00010286
RAX:   RBX: 8a3ff55e5ee8  RCX: 
RDX: 0001  RSI: 8a3ff3d49800  RDI: 8a3ff52fd500
RBP: 8a3ff52fd500   R8: 8a3ff55e5ee8   R9: 0001
R10: 0001  R11: 8a3ef6dd7500  R12: 
R13:   R14: 8a3ff52fd840  R15: 8a3ff55e5ee8
ORIG_RAX:   CS: 0010  SS: 0018
 #7 [b37740c77b30] ip_finish_output at 97f65988
 #8 [b37740c77b68] ip_output at 97f6640c
 #9 [b37740c77bc0] __ip_queue_xmit at 97f65e6d
#10 [b37740c77c18] __tcp_transmit_skb at 97f80557
#11 [b37740c77c88] tcp_write_xmit at 97f81e34
#12 [b37740c77cf0] __tcp_push_pending_frames at 97f82ae1
#13 [b37740c77d00] tcp_sendmsg_locked at 97f733ac
#14 [b37740c77da8] tcp_sendmsg at 97f73507
#15 [b37740c77dc8] sock_sendmsg at 97ee8aa6
#16 [b37740c77de0] sock_write_iter at 97ee8b47
#17 [b37740c77e50] new_sync_write at 97c49bfb
#18 [b37740c77ed0] vfs_write at 97c4c7d5
#19 [b37740c77f00] ksys_write at 97c4ca77
#20 [b37740c77f38] do_syscall_64 at 97a04140
#21 [b37740c77f50] entry_SYSCALL_64_after_hwframe at 98200088
RIP: 7fd74beba504  RSP: 7ffc1d456638  RFLAGS: 0246
RAX: ffda  RBX: 0084  RCX: 7fd74beba504
RDX: 0084  RSI: 55785f33bb90  RDI: 0003
RBP: 55785f31d630   R8:    R9: 1000
R10: 0008  R11: 0246  R12: 01dd
R13: 55785ddc9b00  R14: 0003  R15: 7ffc1d4566e0
ORIG_RAX: 0001  CS: 0033  SS: 002b

crash> sym 97b94ffd
97b94ffd (T) __cgroup_bpf_run_filter_skb+189
./debian/build/build_amd64_none_cloud-amd64/./kernel/bpf/cgroup.c: 539

crash> log
[0.00] Linux version 4.19.0-10-cloud-amd64 (
debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP
Debian 4.19.132-1 (2020-07-24)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-10-cloud-amd64
root=UUID=9ac8f5bd-5b64-48cd-9efd-2b2d35a30500 ro console=tty0
console=ttyS0,115200 earlyprintk=ttyS0,115200 nmi_watchdog=1 elevator=noop
scsi_mod.use_blk_mq=Y crashkernel=384M-:128M

[  478.686368] BUG: unable to handle kernel NULL pointer dereference at
0010
[  478.693551] PGD 0 P4D 0
[  478.696291] Oops:  [#1] SMP PTI
[  478.699431] CPU: 0 PID: 1453 Comm: sshd Kdump: loaded Not tainted

Bug#966653: See if the same error comes with gitlab 13.2.3 which I just uploaded

[Pirate Praveen]

On Sun, Aug 9, 2020 at 23:54, Pirate Praveen  
wrote:
 From the previous comment on this bug, it appears to be caused by 
ruby-google-protobuf and ruby-grpc.


Can you try the new gitlab version I just uploaded?


I can also reproduce the crash now. Try with older protobuf/grpc as a 
workaround for now till we fix this properly.

Bug#800951: gnome-shell crashing when closing evince, without accessibility zoom

[Simon McVittie]

On Mon, 10 Aug 2020 at 13:23:10 -0400, Benedikt Ahrens wrote:
> I am seeing gnome-shell crashing *sometimes* when closing an evince
> window. It does not happen every time I close evince. It only happens
> with evince windows, not with windows of other applications.
> I do not have accessibility zoom enabled.

It's probably best if you open a separate bug for this, preferably
using the reportbug tool to give us full version information. We have
an infinite number of bug numbers available, and merging two bugs if
they turn out to have the same root cause is much, much easier than
disentangling two separate root causes that were discussed on the same
bug number.

Bugs that aren't reliably reproducible are hard to fix, but if you
can get more information about the crash by looking at the system log
(systemd Journal or /var/log/syslog), that would be a useful step towards
figuring out what is going on. Please send that information to the new
bug report rather than in a reply to this mail.

Another useful thing you could do to give developers more information
would be to get a backtrace. If you're using the default systemd init
system, then the easiest way to do that is to install the systemd-coredump
and gdb packages, and continue to use your system as usual. When the crash
happens again, a crash dump will be stored, from which you can provide more
information about the crash that will help us to work out what is happening.
(There's more background about this on
https://wiki.debian.org/HowToGetABacktrace but for now, the important thing
is to install systemd-coredump - when you have collected a crash dump,
someone can talk you through how to get more information out of it.)

If you're not using systemd, the corekeeper package is an alternative to
systemd-coredump.

Thanks,
smcv

Bug#968207: podman: Breaks docker

[Jan Hudec]

Package: podman
Version: 2.0.4+dfsg2-1
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

   * What led up to the situation?

Installing podman or upgrading from 2.0.2+dfsg1-3 to 2.0.3+dfsg1-1
(transcript below, re-testing with 2.0.4

   * What was the outcome of this action?

docker stopped working, in two ways:

 - Users in docker group are no longer able to run docker (permission
   denied).
 - The configured images and containers are no longer available. If they were
   running, they still are, but cannot be controlled any more.

This is because /var/run/docker.sock gets unconditionally redirected to
/run/podman/podman.sock.

   * What outcome did you expect instead?

Since docker.io is not mentioned in Breaks: and since the packages are not
fundamentally inconsistent, I expect them to work together. This is needed at
least to smoothly transition all configured workloads from one to the other.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Workaround is:

$ sudo dpkg-divert --local --rename --add /usr/lib/tmpfiles.d/podman.conf
$ sudo rm /run/docker.sock
$ sudo systemctl restart docker

Disadvantage is that this restarts any running containers, which might be
undesired at the time.

I suggest creating a podman-docker-compat or similar package with that link,
and also linking /usr/bin/docker to /usr/bin/podman, and breaking docker.io.

-- Transcript:

$ docker ps -a
CONTAINER IDIMAGE COMMAND  CREATED  
   STATUS   PORTS   NAMES
7d5e9d7bf3fdmbsync:latest "mbsync -a -q"   21 
months ago   Exited (1) 3 minutes ago mbsync
$ sudo aptitude install podman  
The following NEW packages will be installed:
  conmon{a} containernetworking-plugins{a} golang-github-containers-common{a} 
podman slirp4netns{a} 
0 packages upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 19.2 MB of archives. After unpacking 93.8 MB will be used.
Do you want to continue? [Y/n/?] 
[…snip install log…]
$ docker ps -a
Got permission denied while trying to connect to the Docker daemon socket at 
unix:///var/run/docker.sock: Get 
"http://%2Fvar%2Frun%2Fdocker.sock/v1.40/containers/json?all=1": dial unix 
/var/run/docker.sock: connect: permission denied
$ echo $?
1
$ ls -l /run/docker.* 
-rw-r--r-- 1 root root  4 Aug 10 07:01 /run/docker.pid
lrwxrwxrwx 1 root root 23 Aug 10 18:54 /run/docker.sock -> 
/run/podman/podman.sock=

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

Kernel: Linux 5.7.0-2-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_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages podman depends on:
ii  conmon   2.0.18-1
ii  containernetworking-plugins  0.8.6-2
ii  crun 0.14.1+dfsg-1
ii  golang-github-containers-common  0.14.6+ds1-1
ii  init-system-helpers  1.58
ii  libc62.31-2
ii  libdevmapper1.02.1   2:1.02.171-2
ii  libgpgme11   1.13.1-9
ii  libseccomp2  2.4.3-1+b1
ii  runc 1.0.0~rc10+dfsg2-1

Versions of packages podman recommends:
ii  buildah 1.15.0-6
ii  fuse-overlayfs  1.0.0-1
ii  slirp4netns 1.0.1-1
ii  tini0.18.0-1+b1
ii  uidmap  1:4.8.1-1

Versions of packages podman suggests:
ii  containers-storage  1.21.2+dfsg1-1

-- no debconf information

Bug#966470: fix for #966470: biobambam2 autopkgtest failures

[Étienne Mollier]

Hi John,

John Marshall, on 2020-08-10 11:04:05 +:
> Étienne Mollier wrote:
> > After appending the zlib1g-dev package to dependencies of the
> > biobambam2 package,
> 
> It is in fact libmaus2 that is dlopening "libz.so", so it would be better to 
> add to the dependencies of that package, which is a prerequisite of 
> biobambam2.
> 
> However this is really a bug in libmaus2, as it is incorrect to use that file 
> with that name at runtime [1].
[...]
> [1] https://gitlab.com/german.tischler/libmaus2/-/issues/31

Many thanks for having investigated this issue much further.
Your approach looks much cleaner indeed.  I must admit having a
binary package depending on a header package feels odd.  I set
the bug entry accordingly.

Thank you,
-- 
Étienne Mollier 
Old rsa/3072: 5ab1 4edf 63bb ccff 8b54  2fa9 59da 56fe fff3 882d
New rsa/4096: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/5, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#957761: restartd: diff for NMU version 0.2.3-1.1

[Sudip Mukherjee]

Control: tags 957761 + patch
Control: tags 957761 + pending

Dear maintainer,

I've prepared an NMU for restartd (versioned as 0.2.3-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.

--
Regards
Sudip

diff -Nru restartd-0.2.3/debian/changelog restartd-0.2.3/debian/changelog
--- restartd-0.2.3/debian/changelog 2013-01-13 02:52:37.0 +
+++ restartd-0.2.3/debian/changelog 2020-08-10 19:43:26.0 +0100
@@ -1,3 +1,10 @@
+restartd (0.2.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957761)
+
+ -- Sudip Mukherjee   Mon, 10 Aug 2020 19:43:26 
+0100
+
 restartd (0.2.3-1) unstable; urgency=low
 
   * Project moved out of Debian as the scope is now broader.
diff -Nru restartd-0.2.3/debian/patches/fix_ftbfs.patch 
restartd-0.2.3/debian/patches/fix_ftbfs.patch
--- restartd-0.2.3/debian/patches/fix_ftbfs.patch   1970-01-01 
01:00:00.0 +0100
+++ restartd-0.2.3/debian/patches/fix_ftbfs.patch   2020-08-10 
19:42:50.0 +0100
@@ -0,0 +1,45 @@
+Description: Fix ftbfs with GCC-10
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/957761
+Forwarded: https://github.com/ajraymond/restartd/pull/7
+
+---
+
+--- restartd-0.2.3.orig/config.h
 restartd-0.2.3/config.h
+@@ -33,12 +33,12 @@
+ 
+ #define DEFAULT_CONFIG "/etc/restartd.conf"
+ 
+-int debug;  // Debug
+-int config_process_number;
+-int check_interval;
+-int foreground;
+-struct config_process_type *config_process;
+-char *config_file;
++extern int debug;  // Debug
++extern int config_process_number;
++extern int check_interval;
++extern int foreground;
++extern struct config_process_type *config_process;
++extern char *config_file;
+ 
+ typedef struct config_process_type {
+   char name[64];
+--- restartd-0.2.3.orig/main.c
 restartd-0.2.3/main.c
+@@ -35,6 +35,13 @@
+ 
+ #include "config.h"
+ 
++int debug;  // Debug
++int config_process_number;
++int check_interval;
++int foreground;
++struct config_process_type *config_process;
++char *config_file;
++
+ // SIGTERM & SIGHUP handler
+ void got_signal(int sig)
+ {
diff -Nru restartd-0.2.3/debian/patches/series 
restartd-0.2.3/debian/patches/series
--- restartd-0.2.3/debian/patches/series1970-01-01 01:00:00.0 
+0100
+++ restartd-0.2.3/debian/patches/series2020-08-10 19:25:48.0 
+0100
@@ -0,0 +1 @@
+fix_ftbfs.patch

Bug#968200: missing files for bblxml features

[Hilmar Preuße]

Am 10.08.2020 um 16:02 teilte Ryan Kavanagh mit:

Hi,

> I'm trying to generate bblxml output. Unfortunately, the bblxml perl
> modules seem to be missing.
> 
It is contained in the orig.tar.gz one gets from github.

@Norbert: I guess you us the file from CTAN, where the file is missing.
Correct?

Hilmar
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Bug#968190: gnome-terminal is not listed by firefox when it wants to share a screen

[Simon McVittie]

On Mon, 10 Aug 2020 at 11:20:33 +, Marcin Szamotulski wrote:
>Trying to share a gnome-terminal window in firefox (firefox-79.0, but
>also in previous versions of firefox).

If you're in the default (Wayland) GNOME session, gnome-terminal doesn't
have any X11 windows. I suspect Firefox can only share X11 windows.

Please try this workaround (this assumes you are using gdm, other display
managers will probably have a similar flow):

- save documents, etc.
- log out
- choose/enter your username
- before typing your password, click the gear-wheel icon and select
  session type "GNOME on Xorg"
- finish logging back in

If that is successful, then my guess about the cause was probably correct.

The long-term solution to window and desktop sharing in GNOME Wayland
sessions is to use Pipewire, but the version of Pipewire currently in
Debian is too old (#954022) and Firefox doesn't support it yet anyway
(https://bugzilla.mozilla.org/show_bug.cgi?id=1430775).

smcv

Bug#968206: does not work with lts-15.3

[Joey Hess]

Package: haskell-stack
Version: 1.9.3.1-1
Severity: normal

lts-15.3 and lts-16.8 both fail with a http error.
Looks like the file it expects to find is not there.

Probably there is a new upstream version that changes the url in some
way, I see 2.3.3 is available upsteam but have not tried it.

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

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

Versions of packages haskell-stack depends on:
ii  ca-certificates  20200601
ii  gcc  4:9.2.1-3.1
ii  libatomic1   10.1.0-4
ii  libc62.30-8
ii  libffi7  3.3-4
ii  libgmp-dev   2:6.2.0+dfsg-6
ii  libgmp10 2:6.2.0+dfsg-6
ii  libsqlite3-0 3.32.3-1
ii  libyaml-0-2  0.2.2-1
ii  make 4.3-3
ii  xz-utils 5.2.4-1+b1
ii  zlib1g   1:1.2.11.dfsg-2

haskell-stack recommends no packages.

haskell-stack suggests no packages.

-- no debconf information

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#968205: tumbler: Tumbler daemon (tumblerd) using 100% CPU (single thread)

[Anon1336]

Package: tumbler
Version: 0.2.3-1
Severity: important
Tags: lfs upstream

Dear Maintainer,

The tumbler daemon uses massive amounts of CPU (90-100%) on a single thread 
sporadically. Once it does, even closing all applications does not work and the 
process requires manual termination. I believe it relates to lfs owing to bugs 
788271 and 827427, _however_ the issue persists even _after_ closing large 
files or copy-completion, leaving termination. So, while triggered by large 
files, there is a secondary bug (IDK if I should report it separately).
This is very an upstream problem since I've found serveral cases of it across 
multiple distributions (at least on GNU/LINUX, I've not seen mention on other 
systems) while browsing (it is good to check other distros when reporting 
problems).

Possible diagnostics/fixes:
1) I believe there is a missing (or incorrectly implemented) sleep in the 
source which causes it to scan on a near (or full) per-clock cycle. Where 
sleeping for a few hundred ms or even a second would cause a "blink" for the 
user (depending, < 500ms is unotticeable), I believe it's a fair trade-off.
2) I would suggest that a files be checked for being "in use" and that if true, 
to continue using the already-cached thumbnail until released. This is the most 
elegant solution (and it would prevent, but not fix, the secondary bug).
3) As for the secondary problem, i.e. needing manual termination, the best 
"quick hack" is for it simply to check its resource use (yes it would kill 
itself under certain conditions, however there is no reason a calling process 
cannot exist to monitor it, killing and restarting as needed). It's a dirty-ish 
hack but would be a good temporary cure while the underlying code is being 
fixed.

I hope this is of use. I realise that the maintainer(s) is/are not technically 
responsible, but this seems like a better way to get the upstream developer(s) 
to get something done (I saw a similar behaviour complaint dating back 5 years).

Kind Regards,
Jason

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

Kernel: Linux 5.4.0-0.bpo.4-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_ZA:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tumbler depends on:
ii  libc6   2.28-10
ii  libcairo2   1.16.0-4
ii  libfreetype62.9.1-3+deb10u1
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libglib2.0-02.58.3-2+deb10u2
ii  libgstreamer-plugins-base1.0-0  1.14.4-2
ii  libgstreamer1.0-0   1.14.4-1
ii  libjpeg62-turbo 1:1.5.2-2+b1
ii  libpng16-16 1.6.36-6
ii  libpoppler-glib80.71.0-5
ii  libtumbler-1-0  0.2.3-1
ii  tumbler-common  0.2.3-1
ii  zlib1g  1:1.2.11.dfsg-1

tumbler recommends no packages.

Versions of packages tumbler suggests:
pn  tumbler-plugins-extra  

-- no debconf information

Bug#968074: (no subject)

[Antti Kultanen]

Package: dkms
Version: 2.8.3-3
Followup-For: Bug #968074

I also get the exact same error, no systemd installed.

-8<-
Setting up nvidia-kernel-dkms (440.100-2) ...
Removing old nvidia-current-440.100 DKMS files...
/usr/sbin/dkms: line 247: /dev/fd/62: No such file or directory
Loading new nvidia-current-440.100 DKMS files...
Error! DKMS tree already contains: nvidia-current-440.100
You cannot add the same module/version combo more than once.
dpkg: error processing package nvidia-kernel-dkms (--configure):
 installed nvidia-kernel-dkms package post-installation script subprocess 
returned error exit status 3
dpkg: dependency problems prevent configuration of nvidia-driver:
 nvidia-driver depends on nvidia-kernel-dkms (= 440.100-2) | 
nvidia-kernel-440.100; however:
  Package nvidia-kernel-dkms is not configured yet.
  Package nvidia-kernel-440.100 is not installed.
  Package nvidia-kernel-dkms which provides nvidia-kernel-440.100 is not 
configured yet.

dpkg: error processing package nvidia-driver (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 nvidia-kernel-dkms
 nvidia-driver
E: Sub-process /usr/bin/dpkg returned an error code (1)
-8<-

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

Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=fi_FI (charmap=ISO-8859-1), LANGUAGE not set
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages dkms depends on:
ii  build-essential   12.8
ii  coreutils 8.32-3
ii  dpkg-dev  1.20.5
ii  gcc [c-compiler]  4:10.1.0-1
ii  gcc-10 [c-compiler]   10.2.0-5
ii  gcc-3.3 [c-compiler]  1:3.3.6-15
ii  gcc-3.4 [c-compiler]  3.4.6-10
ii  gcc-5 [c-compiler]5.5.0-12
ii  gcc-6 [c-compiler]6.5.0-2
ii  gcc-9 [c-compiler]9.3.0-17
ii  kmod  27+20200310-2
ii  lsb-release   11.1.0
ii  make  4.3-4
ii  patch 2.7.6-6

Versions of packages dkms recommends:
ii  fakeroot 1.24-1
ii  linux-headers-amd64  5.7.10-1
ii  sudo 1.9.1-2

Versions of packages dkms suggests:
ii  e2fsprogs  1.45.6-1
ii  menu   2.1.47+b1

-- no debconf information

Bug#800951: gnome-shell crashing when closing evince, without accessibility zoom

[Benedikt Ahrens]

I am seeing gnome-shell crashing *sometimes* when closing an evince
window. It does not happen every time I close evince. It only happens
with evince windows, not with windows of other applications.
I do not have accessibility zoom enabled.

This behaviour only started recently, maybe 2 months ago. I cannot tie
the beginning to a specific event, like an update of software.

gnome-shell: 3.30.2-11~deb10u1
evince: 3.30.2-3+deb10u1

Best,
Benedikt

Bug#966804: Also happens with wine apps

[cacatoes]

Not so surprisingly, same problem when running a wine game.

Sorry for the noise here, I'm unsure how to move this bug to its right
place.

Bug#968202: preseed: Checks only BOOTP filename and not DHCP option 67, "bootfile-name"

[Geert Stappers]

On Mon, Aug 10, 2020 at 05:00:31PM +0100, Bob Ham wrote:
> 
> The dhcp_preseed_url function in preseed.sh, part of preseed:
> 
> https://salsa.debian.org/installer-team/preseed/-/blob/399d9e8d56d64161449e9415cc8fe33ae88711f2/preseed.sh#L173
> 
> only checks for the "filename" entry in DHCP lease files.
> The "filename" entry is a holdover from the BOOTP protocol.

Yes, DHCP is EEE of BOOTP


> Some DHCP
> servers don't allow setting the filename at all.  OpenWRT's odhcpd,
> doesn't allow setting the filename in DHCP responses for classified
> clients, such as clients with a vendor class containing "d-i", it only
> allows setting DHCP options.

Server side stuff is not client side stuff ...


> It would be good if dhcp_preseed_url could take advantage of the
> DHCP "bootfile-name" option and not just the BOOTP filename.
 
It will require reseach on how the various DHCP clients in  d-i
write down "filename" in their lease file.


Regards
Geert Stappers
Who provides the preseed URL as kernel command line option during netboot
-- 
EEE = https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish

Bug#968166: apt-listbugs: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.

[Francesco Poli]

On Sun, 9 Aug 2020 19:50:17 -0700 Francois Marier wrote:

[...]
> I see the following in my logs once a day:
> 
>   Aug  9 06:43:56 hostname systemd[1]: 
> /lib/systemd/system/apt-listbugs.service:30: Standard output type syslog is 
> obsolete, automatically updating to journal. Please update your unit file, 
> and consider removing
> the setting altogether.
>   Aug  9 06:43:56 hostname systemd[1]: 
> /lib/systemd/system/apt-listbugs.service:31: Standard output type syslog is 
> obsolete, automatically updating to journal. Please update your unit file, 
> and consider removing
> the setting altogether.

Hello Francois,
thanks for your kind bug report!

Now that you pointed it out, I see that I have the same exact messages
on my box. This began with the upgrade to systemd/246-2 ...

And, indeed, /usr/share/doc/systemd/NEWS.gz now states, in part:

[...]
| CHANGES WITH 246:
[...]
| * StandardError= and StandardOutput= in unit files no longer support
|   the "syslog" and "syslog-console" switches. They were long removed
|   from the documentation, but will now result in warnings when used,
|   and be converted to "journal" and "journal+console" automatically.
[...]

Mmmmh, I think I'll soon try to set

StandardOutput=journal
StandardError=journal

in /lib/systemd/system/apt-listbugs.service (or maybe remove those two
directive altogether, so that the default kicks in) and see what
happens!



BTW, I see the same messages for smartmontools, maybe it should be
reported... oh, you have already done so in [#968168]... Nice job,
thanks!   ;-)

[#968168]: 


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpfUvPrUH_gC.pgp
Description: PGP signature

Bug#968204: RM: gkrellmoon -- ROM; outdated, uses outdated libs, not used any more

[Martin Zobel-Helas]

Package: ftp.debian.org
Severity: normal

Please remove gkrellmoon.

Thanks,
Martin
-- 
 Martin Zobel-Helas Debian System Administrator
 Debian & GNU/Linux Developer   Debian Listmaster
 http://about.me/zobel   Debian Webmaster
 GPG Fingerprint:  6B18 5642 8E41 EC89 3D5D  BDBB 53B1 AC6D B11B 627B 

Bug#968203: ruby2.7: ftbfs when building on buster <#> expected but was

[Pirate Praveen]

Package: ruby2.7
Version: 2.7.1-3

This was working earlier, but now with rubygems-integration minimum 
version set to 1.17.1 one test is failing


1) Failure:
URI::TestGeneric#test_find_proxy_no_proxy 
[/<>/test/uri/test_generic.rb:902]:

<#http://127.0.0.1:8080>> expected but was
.

Finished tests in 606.833867s, 34.5910 tests/s, 4484.9507 assertions/s.
20991 tests, 2721620 assertions, 1 failures, 0 errors, 108 skips

Initially I thought a public ipv6 address was causing the issue, but 
the same issue was therewith a scope link ipv6 address too.


Probably I will disable the test for fasttrack, but wanted to document 
it here.

Bug#968195: keyboard-configuration: cannot set specific layout Français (Bépo, ergonomique, façon Dvorak, AFNOR) for tty console

[Jean-Louis Biasini]

Package: keyboard-configuration
Version: 1.196
Severity: important

Dear Maintainer,

* What exactly did you do (or not do) that was effective (or
ineffective)?
console tty:
$ sudo dpkg-reconfigure keyboard-configuration
choosing Français (Bépo, ergonomique, façon Dvorak, AFNOR)
$ sudo systemctl restart keyboard-setup
* What was the outcome of this action?
still in en us

* Additional info:
- settings any other layout works (included other bépo variants)
therefore not #955215
- this specific layout works fine in X

thanks for your work :)



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

Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_USER
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 keyboard-configuration depends on:
ii debconf 1.5.74
ii liblocale-gettext-perl 1.07-4

keyboard-configuration recommends no packages.

keyboard-configuration suggests no packages.

Versions of packages console-setup depends on:
ii console-setup-linux 1.196
ii debconf 1.5.74
ii xkb-data 2.29-2

Versions of packages console-setup suggests:
ii locales 2.31-2
ii lsb-base 11.1.0

Versions of packages console-setup-linux depends on:
ii init-system-helpers 1.58
ii kbd 2.0.4-4

Versions of packages console-setup-linux suggests:
ii console-setup 1.196

Versions of packages keyboard-configuration is related to:
pn console-common 
ii console-data 2:1.12-8
pn console-tools 
pn gnome-control-center 
ii kbd 2.0.4-4
ii systemd 246-2

-- debconf information:
console-setup/guess_font:
* keyboard-configuration/toggle: No toggling
* keyboard-configuration/switch: No temporary switch
* keyboard-configuration/compose: No compose key
console-setup/store_defaults_in_debconf_db: true
* keyboard-configuration/other:
* keyboard-configuration/store_defaults_in_debconf_db: true
keyboard-configuration/unsupported_config_options: true
* console-setup/fontsize-fb47: 8x16
* console-setup/codeset47: Guess optimal character set
console-setup/use_system_font:
* keyboard-configuration/xkb-keymap: fr(bepo_afnor)
* keyboard-configuration/variant: Français - Français (Bépo,
ergonomique, façon Dvorak, AFNOR)
keyboard-configuration/unsupported_layout: true
* keyboard-configuration/ctrl_alt_bksp: true
keyboard-configuration/unsupported_config_layout: true
* keyboard-configuration/altgr: The default for the keyboard layout
keyboard-configuration/unsupported_options: true
debian-installer/console-setup-udeb/title:
* keyboard-configuration/modelcode: tm2030USB
* keyboard-configuration/layoutcode: fr
console-setup/fontsize: 8x16
* keyboard-configuration/optionscode: terminate:ctrl_alt_bksp
* keyboard-configuration/layout: Français
* console-setup/fontface47: Fixed
console-setup/fontsize-text47: 8x16
* console-setup/charmap47: UTF-8
* keyboard-configuration/variantcode: bepo_afnor
console-setup/framebuffer_only:
console-setup/codesetcode: guess
* keyboard-configuration/model: TypeMatrix EZ-Reach 2030 USB

Bug#966386: cppcheck: crashes with --clang option (.c)

[Joachim Reichel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 09.08.20 20:15, John Scott wrote:
> Sorry for the noise, I spoke too soon. Their main page says it normally
> takes days to get an account which must be requested over IRC [1]. For a
> one-time comment that's a big leap to take.

Right, I forgot about that. I'll try to relay further input to the upstream
bug tracker.
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErX6NzLwwsr4xjsEVuPr/HEOIZ3EFAl8xeWYACgkQuPr/HEOI
Z3GVchAA3DIxpEqS9zpNEJO0Nu+Pn9L/Vk5Gs8Biqs+egyeGr93jJ3Msiz0HndJy
5MdQUXWn+y3QLkSMlRWJNyNTEHoNEiqgFnzr07wkgR7mrdyPIOssROGodr0ybKVt
L+1trN+DTxWcxRjDlRB1vtzUrqptLV9k38R0o0BQNwR3MH9JmqHH8rSZjAIkMYJe
qs6x1pVY5l4S1uf+w9W7+G2FQm68FsieDx5NfoQ42V6lwdIGCTlZjxNWX5+M0xTj
P081lPtSnYv7lJ4ZydUL2p5MJJQbKoZPMGc3HFpk8w+CtlQEu8RJeKOdG+N/3anm
PcdDKcl6tkuAYLJ6H2lrYlqCdlbGbKoq8IT33WGiUgOUn1MN9CZ5sFHw3+vJBS5F
GUOA/+FQiorImPkj04BBR2519isfSnyc77H3+Ml2pemih7JXlMqhzU02jFvtYDk5
+I9yD+w/K0A2aPV57GPulKZgSiomwy3aMPn1ra+jv7Gedck8TvXNUtGgy2aLdwD4
zdhKMe5IIneY5FAkqrddEW5jK6DLw9f0aCuYMt0QmUzRJNy69G15PFGHBXk/m7kA
+MElU8o8pInYDVNmRSSYlgbMYMQe9zc7hfwiH0SX+NuG2RaN9k0gn5Zcw2w6rWjV
54PC2jNJbClqTkHfpmNAtQJhaB7DmlIHsVXs2O2ZA31R8e8OG7g=
=cYnU
-END PGP SIGNATURE-

Bug#968163: apt: 'apt update' repeats the same progress line many times

[Piotr Engelking]

Julian Andres Klode :

> Heh, I've only ever seen it with the same number. But this is not
> a progress logging issue, it means there's a problem with the
> connection and it's reconnecting, and it does so potentially endlessly
> because the code misses a continue.

Thanks for the quick fix, I'll try to test it. How about the

  Get:2 file:/usr/src/deb  Release [858 B]

line, though? It is just a local file, no networking involved.

Bug#966186: u-boot-omap: Unusable on BeagleBone Black

[rah+debianbts]

On 25/07/2020 00:00, rah+debian...@settrans.net wrote:
> On 24/07/2020 20:50, Vagrant Cascadian wrote:

>> If so, you may have to wipe the environment from the media

> Regardless, where is the environment being read from?  How can one wipe it?

I've written all zeroes to /dev/mmcblk1 (eMMC) and also used a different
SD card but the environment still has `board_name=BBG1`.  Are you aware
of where this environment variable is coming from?

Bug#968192: xkb-data: bepo_afnor missing eszett character

[Jean-Louis Biasini]

Package: xkb-data
Version: 2.29-2
Severity: normal
Tags: patch

Dear Maintainer,

the french bepo variant afnor contains an error which prevent the user from
typing german eszett caracter ß (code ssharp)

The error is easily spotable in /usr/share/X11/xkb/symbols/fr since the
same
mapping already exist and is correctly mapped on other variant of the
bepo (see patch).

thanks for your work,

jean-louis

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

Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_USER
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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

-- no debconf information

--- /usr/share/X11/xkb/symbols/fr	2020-02-29 13:32:57.0 +0200
+++ /usr/share/X11/xkb/symbols/fr	2020-08-10 14:51:26.985791752 +0300
@@ -640,7 +640,7 @@
 	key  { type[group1] = "FOUR_LEVEL", [ comma, semicolon, apostrophe, dead_belowcomma ] }; // , ; ' ,
 	key  { type[group1] = "FOUR_LEVEL_SEMIALPHABETIC", [ c, C, dead_cedilla, copyright ] }; // c C ¸ ©
 	key  { type[group1] = "FOUR_LEVEL_SEMIALPHABETIC", [ t, T, UFDD5, trademark ] }; // t T ᵉ ™
-	key  { type[group1] = "FOUR_LEVEL_SEMIALPHABETIC", [ s, S, UFDD4, U017F ] }; // s S ß ſ
+	key  { type[group1] = "FOUR_LEVEL_SEMIALPHABETIC", [ s, S, ssharp, U017F ] }; // s S ß ſ
 	key  { type[group1] = "FOUR_LEVEL_SEMIALPHABETIC", [ r, R, dead_breve, registered ] }; // r R ˘ ®
 	key  { type[group1] = "FOUR_LEVEL_SEMIALPHABETIC", [ n, N, dead_tilde, U2693 ] }; // n N ~ ⚓
 	key  { type[group1] = "FOUR_LEVEL_SEMIALPHABETIC", [ m, M, dead_macron, U26FD ] }; // m M ¯ ⛽

Bug#968202: preseed: Checks only BOOTP filename and not DHCP option 67, "bootfile-name"

[Bob Ham]

Package: debian-installer
Severity: normal

The dhcp_preseed_url function in preseed.sh, part of preseed:

https://salsa.debian.org/installer-team/preseed/-/blob/399d9e8d56d64161449e9415cc8fe33ae88711f2/preseed.sh#L173

only checks for the "filename" entry in DHCP lease files.  The
"filename" entry is a holdover from the BOOTP protocol.  Some DHCP
servers don't allow setting the filename at all.  OpenWRT's odhcpd,
doesn't allow setting the filename in DHCP responses for classified
clients, such as clients with a vendor class containing "d-i", it only
allows setting DHCP options.

It would be good if dhcp_preseed_url could take advantage of the
DHCP "bootfile-name" option and not just the BOOTP filename.


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

Kernel: Linux 5.6.0-linux-latest-32 (SMP w/16 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#961229: libnfc: New upstream version: 1.7.2

[Ludovic Rousseau]

New version is uploaded.
libnfc6 is a new package so in the NEW queue. We have to wait for a manual 
intervention.

https://ftp-master.debian.org/new/libnfc_1.8.0-1.html

--
Dr. Ludovic Rousseau

Bug#968178: please reassign to other package

[Wolfgang Rohdewald]

Kajongg is written in Python, it cannot cause a segementation error by itself.

The faulty package might be python3-pyqt5, please reassign your bug report to 
that package.

Somebody might want to make kajongg run with pyside instead of pyqt5 but
I currently have no time to do that.

-- 
Wolfgang

Bug#318884: xfig: Xfig draws a figure 5 times on start-up

[Roland Rosenfeld]

Hi Greg!

On Di, 04 Aug 2020, G Kochanski wrote:

> Well, that's a blast from the past!
> I think the originally reported problem seems to have gone away over the
> last 15 years.  But there seem to be some serious X-windows bugs remaining,
> notably some big grey areas.   I've attached one of the files if you want
> to see for yourself.

Could you please provide a screenshot of what you are talking about.
I don't notice "big grey areas" or don't understand what you mean.

Greetings

Roland


signature.asc
Description: PGP signature

Bug#959865: [Pkg-mozext-maintainers] Bug#959865: New version fixes this issue

[Martina Ferrari]

Hi,

On 09/08/2020 01:47, Ximin Luo wrote:

> I am in the process of updating this package. However, the curretn
verison 3.4.7-1 works for me with firefox 79 in sid. So I don't know why
it's not working for you. Therefore I don't feel right to close this bug
when updating to the new version.

So I tested this, with the version of Firefox I had installed (76), and
it still did not work. But after upgrading Firefox to current sid, it
works again.

-- 
Martina Ferrari (Tina)

Bug#967564: [Pkg-pascal-devel] Bug#967564: lazarus: depends on deprecated GTK 2

[Abou Al Montacir]

Hi Peter,
On Mon, 2020-08-10 at 14:54 +0100, Peter wrote:
> Hi,
> I'm wondering, would it be possible to enable the GTK3 widget set in Lazarus
> 2.0.10?Do the uncomment here?https://wiki.freepascal.org/GTK3_Interface
The wiki article is talking about 1.1, so we need to check is 1.0.x got this
support. 
> so folks can get started without having to rebuild the whole of Lazarus
> themselves.
At a certain moment we will migrate to GTK3, but I don't expect this to be an
easy task, we will probably need support from upstream.
> Maybe there's more to it!
Who know, maybe it is easier than I expect.
-- 
Cheers,
Abou Al Montacir




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

Bug#968190: gnome-terminal is not listed by firefox when it wants to share a screen

[Marcin Szamotulski]

Package: gnome-terminal
Version: 3.36.2-1
Severity: normal
X-Debbugs-Cc: profunc...@pm.me

Dear Maintainer,

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

   * What led up to the situation?

   Trying to share a gnome-terminal window in firefox (firefox-79.0, but
   also in previous versions of firefox).

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



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

Kernel: Linux 5.7.10-fozzie (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-terminal depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.20-1
ii  dbus-x11 [dbus-session-bus]   1.12.20-1
ii  dconf-gsettings-backend [gsettings-backend]   0.36.0-1
ii  gnome-terminal-data   3.36.2-1
ii  gsettings-desktop-schemas 3.36.1-1
ii  libatk1.0-0   2.36.0-2
ii  libc6 2.31-3
ii  libdconf1 0.36.0-1
ii  libglib2.0-0  2.64.4-1
ii  libgtk-3-03.24.20-1
ii  libpango-1.0-01.44.7-5
ii  libuuid1  2.36-2
ii  libvte-2.91-0 0.60.3-1
ii  libx11-6  2:1.6.10-3

Versions of packages gnome-terminal recommends:
ii  gvfs   1.44.1-1
ii  nautilus-extension-gnome-terminal  3.36.2-1
ii  yelp   3.36.0-1

gnome-terminal suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature


signature.asc
Description: OpenPGP digital signature

Bug#966655: Orthanc and all its plugins are getting removed from testing

[Sébastien Jodogne]

As suggested by Andreas, I've been in touch with the FTP team.

Following this discussion, I've uploaded orthanc-1.7.2+dfsg-3 to 
unstable, that doesn't contain the NEW changes.


For reference, here are the two changesets to revert once 
"liborthancframework-dev" and "liborthancframework1" subpackages get 
accepted:


https://salsa.debian.org/med-team/orthanc/-/commit/014c050762fa3804448142968ce63325745d9035
https://salsa.debian.org/med-team/orthanc/-/commit/9a5b353bbd085b5ae2e376d543a11912b55c5d6e

Sébastien-




Because of the bug #966655 [1], and because of the fact that
orthanc-1.7.2+dfsg-2 is pending in the NEW queue [2], I cannot commit
the fix regarding the missing build dependency on tzdata until the NEW
packages get accepted.

But, as #966655 is tagged as serious, the entire Orthanc ecosystem was
removed from Debian testing during this week-end.

Is there anything I can do to prevent this?

Many thanks in advance for your help,
Sébastien-


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966655
[2]
https://alioth-lists.debian.net/pipermail/debian-med-packaging/2020-July/082973.html

Bug#968200: missing files for bblxml features

[Ryan Kavanagh]

Package: biber
Version: 2.14-1
Severity: normal
X-Debbugs-Cc: 

I'm trying to generate bblxml output. Unfortunately, the bblxml perl
modules seem to be missing.

-8<---
$ biber --help | grep output-format
--output-format=dot|bibtex|biblatexml|bbl|bblxml
$ biber --output-format=bblxml main
INFO - This is Biber 2.14 (beta)
INFO - Logfile is 'main.blg'
ERROR - Error loading data source package 'Biber::Output::bblxml': Can't locate 
Biber/Output/bblxml.pm in @INC (you may need to install the 
Biber::Output::bblxml module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.30.3 /usr/local/share/perl/5.30.3 
/usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.30 
/usr/share/perl/5.30 /usr/local/lib/site_perl) at (eval 393) line 1.

INFO - ERRORS: 1
-8<---

I was going to submit a packaging patch, but the files seem to be
missing from the source package as well: there is no bblxml.pm in
lib/Biber/Output.

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

Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_CA.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages biber depends on:
ii  libautovivification-perl  0.18-1+b2
ii  libbusiness-isbn-perl 3.005-1
ii  libbusiness-ismn-perl 1.201-1
ii  libbusiness-issn-perl 1.004-1
ii  libclass-accessor-perl0.51-1
ii  libdata-compare-perl  1.27-1
ii  libdata-dump-perl 1.23-1
ii  libdata-uniqid-perl   0.12-1
ii  libdate-simple-perl   3.0300-3
ii  libdatetime-calendar-julian-perl  0.102-1
ii  libdatetime-format-builder-perl   0.8200-1
ii  libdatetime-perl  2:1.52-1
ii  libencode-eucjpms-perl0.07-3+b8
ii  libencode-hanextra-perl   0.23-5+b2
ii  libencode-jis2k-perl  0.03-1+b6
ii  libfile-slurper-perl  0.012-1
ii  libipc-run3-perl  0.048-2
ii  liblingua-translit-perl   0.28-1
ii  liblist-allutils-perl 0.16-1
ii  liblist-moreutils-perl0.416-1+b5
ii  liblog-log4perl-perl  1.50-1
ii  liblwp-protocol-https-perl6.09-1
ii  libparse-recdescent-perl  1.967015+dfsg-2
ii  libreadonly-perl  2.050-2
ii  libregexp-common-perl 2017060201-1
ii  libsort-key-perl  1.33-2+b2
ii  libtext-bibtex-perl   0.88-3+b1
ii  libtext-csv-perl  2.00-1
ii  libtext-csv-xs-perl   1.44-1
ii  libtext-roman-perl3.5-2
ii  libunicode-collate-perl   1.27-1+b1
ii  libunicode-linebreak-perl 0.0.20190101-1+b2
ii  liburi-perl   1.76-2
ii  libwww-perl   6.46-1
ii  libxml-libxml-simple-perl 1.01-1
ii  libxml-libxslt-perl   1.99-1
ii  libxml-writer-perl0.625-1
ii  perl [libunicode-collate-perl]5.30.3-4
it  tex-common6.15

Versions of packages biber recommends:
iu  texlive-bibtex-extra  2020.20200804-1

biber suggests no packages.

-- no debconf information

-- 
|)|/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac |  BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Bug#967564: lazarus: depends on deprecated GTK 2

[Peter]

Hi,

I'm wondering, would it be possible to enable the GTK3 widget set in Lazarus 
2.0.10?
Do the uncomment here?
https://wiki.freepascal.org/GTK3_Interface

so folks can get started without having to rebuild the whole of Lazarus 
themselves.

Maybe there's more to it!


Regards,
Peter B

Bug#968199: Set up /dev/stdin and others

[Matti Palmström]

Package: sysvinit-core
Severity: wishlist
Version: 2.96-3

Heya

Since udev don't set up /dev/stdin and others any longer
https://github.com/systemd/systemd/commit/6b2229c6c60d0486 could this be
moved to sysvinit-core (or similar package widely used) for those of us who
don't use systemd?

Regards
Matti

Bug#968198: ITP: c2x -- converter between DFT electronic structure codes formats

[merkys]

Package: wnpp
Owner: Andrius Merkys 
Severity: wishlist

* Package name: c2x
  Version : 2.34d
  Upstream Author : M. J. Rutter 
* URL : https://www.c2x.org.uk
* License : GPL-3
  Programming Lang: C
  Description : converter between DFT electronic structure codes formats
 This program should convert CASTEP's .check, .castep_bin, orbitals and
.cell
 to various other formats, particularly so that they can be visualised with
 Jmol, XCrysDen, gnuplot and other programs. It can extract change and spin
 densities, wavefunctions, symmetry operations, and much else besides.
It also
 interfaces with VASP, Siesta, and other electronic structure codes.
 .
 The code can also manipulate .cell and .pdb files, building supercells
 or performing shifts.

Remark: This package is to be maintained with Debichem Team at
   https://salsa.debian.org/debichem-team/c2x

Bug#944744: bitcoind: Status of the Bitcoin Core package in Debian

[Vincas Dargis]

On Thu, 14 Nov 2019 20:14:10 +0100 Jonas Smedegaard  wrote:
What I expect to be realistic is including e.g. 0.20.0 shortly before 
freeze of bullseye, have it included when bullseye becomes stable 3-6 
months later, and then when 0.20.1 comes out...


Ping. 0.20.1 is now available.

Bug#920903: [Openjdk] Bug#920903: openjdk-11-jdk-headless: ships documentation for JDK 8, not JDK 11

[Etienne Dysli Metref]

On 10.08.20 14:17, Matthias Klose wrote:
>> Is there any hope this could be fixed in a
>> future OpenJDK 11 release?
> 
> if somebody updates those for 11 ...

I'd happily file an upstream bug to prod them, but I can't get the form
at https://bugreport.java.com/bugreport/start_form.do to work... :(

  Etienne



signature.asc
Description: OpenPGP digital signature

Bug#959875: Acknowledgement (RFS: redmine-plugin-apijs/6.1.0-4 [ITP] -- Redmine plugin to display gallery from attachments)

[Fabrice Creuzot]

Hi, I uploaded a new release.

Bug#968197: node-d3-contour: short description of package is truncated

[Daniele Forsi]

Package: node-d3-contour
Severity: normal

Dear Maintainer,

the short description of node-d3-contour is truncated and continues to the 
first line of the long description.
For example see:
https://packages.debian.org/sid/node-d3-contour

or:
$ apt-cache show node-d3-contour
[...]
Description-en: Computes contour polygons by applying marching
 squares to a rectangular array.
 .
 Computes contour polygons by applying marching squares to a
 rectangular array of numeric values.
[...]

I think that the description line should end without a full stop like the 
majority of short descriptions):
Description-en: computes contour polygons by applying marching squares to a 
rectangular array

$ grep "^Description-en: .*\\.$" 
/var/lib/apt/lists/ftp.it.debian.org_debian_dists_testing_main_i18n_Translation-en
 | wc -l
306

The majority of descriptions start with a capital letter but this includes also 
proper nouns
$ grep "^Description-en: [A-Z]" 
/var/lib/apt/lists/ftp.it.debian.org_debian_dists_testing_main_i18n_Translation-en
 | wc -l
35889
$ grep "^Description-en: [a-z]" 
/var/lib/apt/lists/ftp.it.debian.org_debian_dists_testing_main_i18n_Translation-en
 | wc -l
19066
$ grep "^Description-en: " 
/var/lib/apt/lists/ftp.it.debian.org_debian_dists_testing_main_i18n_Translation-en
 | wc -l
55263


Thank you for your work in Debian,
Daniele

Bug#968196: fping: postinst fails when dpkg-statoverride is already used

[Paul Slootman]

Package: fping
Version: 4.2-3
Severity: normal

Setting up fping (4.2-3) ...
Failed to set capabilities on file `/usr/bin/fping' (Operation not supported)
The value of the capability argument is not permitted for a file. Or the file 
is not a regular (non-symlink) file
WARNING: 'setcap cap_net_raw+ep /usr/bin/fping' failed.
/usr/bin/fping is already setuid root. Not trying to fix anything.
WARNING: Making /usr/bin/fping setuid instead. Use dpkg-statoverride(1) to 
change that if you're unhappy with it.
dpkg-statoverride: error: an override for '/usr/bin/fping' already exists; 
aborting
dpkg: error processing package fping (--configure):
 installed fping package post-installation script subprocess returned error 
exit status 2
Errors were encountered while processing:
 fping
E: Sub-process /usr/bin/dpkg returned an error code (1)

The script first says "Not trying to fix anything" and then goes on
and tries to fix something.

The problem is that there is an "else" missing:

--- fping.postinst.orig 2020-08-10 14:41:18.835956683 +0200
+++ fping.postinst  2020-08-10 12:20:13.191669951 +0200
@@ -14,9 +14,10 @@
 else
 echo "A local statoverride for /usr/bin/fping already 
exists. Not trying to fix anything." 1>&2
 fi
+   else
+echo "WARNING: Making /usr/bin/fping setuid instead. Use 
dpkg-statoverride(1) to change that if you're unhappy with it." 1>&2
+dpkg-statoverride --update --add root root 4755 
/usr/bin/fping
 fi
-echo "WARNING: Making /usr/bin/fping setuid instead. Use 
dpkg-statoverride(1) to change that if you're unhappy with it." 1>&2
-dpkg-statoverride --update --add root root 4755 /usr/bin/fping
 fi
 fi
 ;;


-- Package-specific info:
-rwxr-xr-x 1 root root 48032 Apr 27 15:37 /usr/bin/fping
lrwxrwxrwx 1 root root 5 Apr 27 15:37 /usr/bin/fping6 -> fping

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

Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages fping depends on:
ii  libc62.30-4
ii  libcap2-bin  1:2.33-1
ii  netbase  6.1

fping recommends no packages.

fping suggests no packages.

-- no debconf information

Bug#968177: RFP: venom — A Vala/Gtk+ client for Tox.

[Marek Ľach]

Package: venomRFPSeverity: wishlistA modern Vala/Gtk+ client for Tox on 
Linux.License: GPLSource: https://github.com/naxuroqa/VenomIt'd be great, to 
have this also packaged for aarch64. Sincere thanks!

Bug#968184: autopkgtest is infinitely outputting "ERROR: not valid"

[Iain Lane]

Control: severity -1 serious

On Mon, Aug 10, 2020 at 11:32:42AM +0100, Iain Lane wrote:
> I've pinged the Debian CI people, will report back & upgrade the 
> severity if they confirm it is happening on Debian too.

Yeah, same here

  
https://ci.debian.net/data/autopkgtest/testing/arm64/c/calculix-cgx/6606733/log.gz

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

Bug#920903: [Openjdk] Bug#920903: Bug#920903: openjdk-11-jdk-headless: ships documentation for JDK 8, not JDK 11

[Matthias Klose]

On 8/10/20 2:11 PM, Etienne Dysli Metref wrote:
> On 10.08.20 13:17, Matthias Klose wrote:
>>> Is this a Debian packaging problem or does upstream provide the wrong
>>> documentation?
>>
>> that's the documentation provided by upstream.
> 
> Thank you for the fast answer Matthias. :)
> Would https://bugs.openjdk.java.net/browse/JDK-8225134 be the
> corresponding upstream issue?

That's the issue for 13, not 11.

> Is there any hope this could be fixed in a
> future OpenJDK 11 release?

if somebody updates those for 11 ...

Bug#968193: dh-python autopkg tests fail

[Matthias Klose]

Package: src:dh-python
Version: 4.20200804
Severity: serious
Tags: sid bullseye patch

The dh-python autopkg tests fail, still needing the unversioned python binary.
Please adjust those, or disable those as done already by Stefano.

patch at
https://patches.ubuntu.com/d/dh-python/dh-python_4.20200804ubuntu1.patch

Bug#968194: Depends on non-existent python version?

[積丹尼 Dan Jacobson]

Package: getmail
Version: 5.13-1

Aptitude says:
The following packages will be upgraded:
  libpython2-stdlib  python2  python2-minimal
3 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

The following packages have unmet dependencies:
 python : Depends: python2 (= 2.7.17-2) but 2.7.18-2 is to be installed
 libpython-stdlib : Depends: libpython2-stdlib (= 2.7.17-2) but 2.7.18-2 is to 
be installed
 python-minimal : Depends: python2-minimal (= 2.7.17-2) but 2.7.18-2 is to be 
installed
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) libpython2-stdlib [2.7.17-2 (now)]
2) python2 [2.7.17-2 (now)]
3) python2-minimal [2.7.17-2 (now)]

Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

  Remove the following packages:
1)  getmail [5.13-1 (now, unstable)]

Bug#920903: [Openjdk] Bug#920903: openjdk-11-jdk-headless: ships documentation for JDK 8, not JDK 11

[Etienne Dysli Metref]

On 10.08.20 13:17, Matthias Klose wrote:
>> Is this a Debian packaging problem or does upstream provide the wrong
>> documentation?
> 
> that's the documentation provided by upstream.

Thank you for the fast answer Matthias. :)
Would https://bugs.openjdk.java.net/browse/JDK-8225134 be the
corresponding upstream issue? Is there any hope this could be fixed in a
future OpenJDK 11 release?

  Etienne



signature.asc
Description: OpenPGP digital signature

Bug#968046: dh-python: missing Breaks+Replaces: python2 (<< 2.7.18)

[Matthias Klose]

Control: tags -1 + patch

the break against python is wrong, or at least unnecessary. The files shipped in
python2 in buster.

diff -Nru dh-python-4.20200804/debian/changelog 
dh-python-4.20200804.1/debian/changelog
--- dh-python-4.20200804/debian/changelog   2020-08-04 10:10:12.0 
+0200
+++ dh-python-4.20200804.1/debian/changelog 2020-08-10 14:08:27.0 
+0200
@@ -1,3 +1,9 @@
+dh-python (4.20200804.1) UNRELEASED; urgency=medium
+
+  * 
+
+ -- Matthias Klose   Mon, 10 Aug 2020 14:08:27 +0200
+
 dh-python (4.20200804) unstable; urgency=medium
 
   [ Scott Kitterman ]
diff -Nru dh-python-4.20200804/debian/control 
dh-python-4.20200804.1/debian/control
--- dh-python-4.20200804/debian/control 2020-08-04 10:10:12.0 +0200
+++ dh-python-4.20200804.1/debian/control   2020-08-10 14:08:19.0 
+0200
@@ -26,8 +26,8 @@
 # due to /usr/bin/dh_python3 and debhelper files
  python3 (<< 3.3.2-4~),
 # due to /usr/bin/dh_python2 and debhelper files
- python
-Replaces: python3 (<< 3.3.2-4~)
+ python2 (<< 2.7.18-2)
+Replaces: python3 (<< 3.3.2-4~), python2 (<< 2.7.18-2)
 Description: Debian helper tools for packaging Python libraries and 
applications
  This package contains:
   * pybuild - invokes various build systems for requested Python versions in

Bug#932659: [Pkg-javascript-devel] Bug#932659: node: modules are not getting detected in a fresh sid chroot environment

[Jérémy Lal]

Severity: important
Tags: moreinfo

Le mar. 17 mars 2020 à 14:45, Josh de Kock  a écrit :

>
> Hi,
>
> This still occurs for me. I have a armhf chroot of Sid. It seems to be
> using a node path relative to the current directory (as far as I can
> tell). These paths should probably be /usr prefixed (and not relative to
> cwd), but I wouldn't know where to begin fixing this.
>

Yes, they should.
I don't understand how this chroot ends up with those paths either.
How did you set it up ?

I tried a buster armhf chroot:
- nodejs 10.21.0
- npm 5.8.0+ds6-4+deb10u1

a sid ppc64el chroot:
- nodejs 12.18.3
- npm 6.14.6+ds-1

in both cases, i got correct resolve paths, and this works:
node -e "require('y18n');"

Since most of the report talk about node-y18n i suppose it was this module
that was affected during a transition of /usr/lib/nodejs to
/usr/share/nodejs.

To keep things simple i'll leave it here open (without reassigning) for a
while,
unless someone reproduces it again.

Jérémy

Bug#968191: ITP: damapper -- long read to reference genome mapping tool

[Shayan Doust]

Package: wnpp
Severity: wishlist

Subject: ITP: damapper -- long read to reference genome mapping tool
Package: wnpp
Owner: Shayan Doust 
Severity: wishlist

* Package name: damapper
  Version : 0.0+git20200322.b2c9d7f
  Upstream Author : Dr. Eugene W. Myers
* URL : https://github.com/thegenemyers/DAMAPPER
* License : BSD-3-Clause
  Programming Lang: C
  Description : long read to reference genome mapping tool
 Recognised as the Damapper Library, this is a long read to reference
 genome mapping command line tool.

Remark: This package is maintained by Debian Med Packaging Team at
   https://salsa.debian.org/med-team/damapper

Bug#966470: fix for #966470: biobambam2 autopkgtest failures

[John Marshall]

Étienne Mollier wrote:
> I had a look at the autopkgtest failure affecting biobambam2,
> and since these segmentation faults were showing up only in my
> autopkgtest environment, and not when using the package directly
> on my system, it felt like a missing dependency.  So I trapped
> system calls issued by the `bamsormadup` command using `strace`
> within the run-unit-test script, and it turned out the program
> was searching for a libz.so library.
> 
> After appending the zlib1g-dev package to dependencies of the
> biobambam2 package,

It is in fact libmaus2 that is dlopening "libz.so", so it would be better to 
add to the dependencies of that package, which is a prerequisite of biobambam2.

However this is really a bug in libmaus2, as it is incorrect to use that file 
with that name at runtime [1]. So the better fix would be to patch libmaus2 to 
use the runtime filename ("libz.so.1") that is provided by Debian's zlib1g (and 
ensure that libmaus2 depends on zlib1g -- without ‑dev) in anticipation of 
upstream libmaus2 making a similar fix.

Thus (as Debian controls exactly the libz.so.1 filename, unlike for the 
upstream patch):

+++ b/src/libmaus2/lz/ZlibInterface.hpp
@@ -53,7 +53,7 @@ namespace libmaus2
static std::string getDefaultZLibName() {
return

"../lib/libz_cf.so\ti386:sse4_2,i386:pclmulqdq\n"
-   "libz.so\t\n";
+   "libz.so.1\t\n";
}

John


[1] https://gitlab.com/german.tischler/libmaus2/-/issues/31

Bug#968173: A new upstream version is available: 4.2.0

[Corey Minyard]

On Mon, Aug 10, 2020 at 09:25:12AM +0200, Marc Haber wrote:
> Package: ser2net
> Version: 3.5-2
> Severity: wishlist
> 
> A new upstream version 4.2.0 is available, I should consider packaging it.
> 
> Will do.

Current version is 4.2.1.  I split out the I/O handling to a separate
library named gensio (available at the same place), if you use the 4.x
versions of ser2net, you will need to package gensio, too.

Bug#967949: ITP: ipqalc -- graphical utility for IPv4 subnet calculation

[Fabio Augusto De Muzio Tobich]

Em 10/08/2020 04:05, Wouter Verhelst escreveu:

On Wed, Aug 05, 2020 at 12:03:12PM -0300, Fabio Augusto De Muzio Tobich wrote:

Package: wnpp
Severity: wishlist
Owner: Fabio Augusto De Muzio Tobich 
X-Debbugs-Cc: debian-de...@lists.debian.org, ftob...@gmail.com

* Package name: ipqalc
   Version : 1.5.3
   Upstream Author : Alexander Danilov 
* URL : https://bitbucket.org/admsasha/ipqalc
* License : GPL-3+
   Programming Lang: C++
   Description : graphical utility for IPv4 subnet calculation

Small utility for IP address calculations including broadcast and network
addresses as well as Cisco wildcard mask.

>From a given IPv4 address calculates broadcast, network, Cisco wildcard mask,
and host range. It can also be used as a teaching tool and presents the
results in binary, and hex, values.


How does it differ from sipcalc?

(not that I want to say you shouldn't upload this, just interested)



Hi,

So, basically ipqalc is a graphical interface tool while sipcalc is 
command line only. Sipcalc used to have a cgi interface but it was 
removed a long time ago.


Another point is that sipcalc does not seem to be actively maintained 
upstream anymore (latest version is from 2012).

Ipqalc has an active and very receptive upstream and can still evolve a lot.

Cheers.

Bug#968177: RFP: venom — A Vala/Gtk+ client for Tox.

[Andrei POPESCU]

Control: reassign -1 wnpp
Control: severity -1 wishlist

On Lu, 10 aug 20, 10:52:44, Marek Ľach wrote:
> Package: venomRFPSeverity: wishlistA modern Vala/Gtk+ client for Tox on 
> Linux.License: GPLSource: https://github.com/naxuroqa/VenomIt'd be great, to 
> have this also packaged for aarch64. Sincere thanks!

-- 
Looking after bugs filled against unknown packages


signature.asc
Description: PGP signature

Bug#920903: [Openjdk] Bug#920903: openjdk-11-jdk-headless: ships documentation for JDK 8, not JDK 11

[Matthias Klose]

On 8/10/20 12:49 PM, Etienne Dysli Metref wrote:
> Hi there!
> 
> As a Java developer, I'm very much interested in having this bug
> fixed. It has already caused me to give wrong information to other
> people... :/ For example: the java(1) man page lists the option
> `-XX:+HeapDumpOnOutOfMemory`, but this option has been renamed to
> `-XX:+HeapDumpOnOutOfMemoryError` in Java 11.
> 
> Is this a Debian packaging problem or does upstream provide the wrong
> documentation?

that's the documentation provided by upstream.

Bug#968189: muroar: non-deterministically FTBFS (or not reproducible)

[Chris Lamb]

Source: muroar
Version: 0.1.13-5
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0] I noticed that
muroar could not be reliably built. For example, sometimes it does
not build the muroar shared library at the right time (?) so the
linker fails.

It will usually build for me, but it also will not build
reproducibility.

I don't know whether this is CPU-level parallelism or filesystem
ordering, but setting --no-parallel appears to make it build 10s of
time in a row.

Patch attached, but I suspect the real bug is in the upstream Makefile.

 [0] https://reproducible-builds.org/


Regards,

--
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   ` a/debian/rules  2020-08-10 11:23:24.213660005 +0100
--- b/debian/rules  2020-08-10 12:08:02.032238882 +0100
@@ -17,6 +17,9 @@
 override_dh_auto_configure:
./configure $(DEB_CONFIGURE_EXTRA_FLAGS)
 
+override_dh_auto_build:
+   dh_auto_build --no-parallel
+
 override_dh_install:
mkdir -p $(CURDIR)/debian/tmp/usr/share/bash-completion/completions/
cp -f bash_completion 
$(CURDIR)/debian/tmp/usr/share/bash-completion/completions/muroar

Bug#968188: linux-image-5.7.0-2-arm64: 4K display resolution is not recognized with Raspberry Pi 4B

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.7.10-1
Severity: important


Dear Maintainer,

My display has 3840x2160 resulution.
The kernel from Raspberry Pi Foundation can use 3840x2160.

But the debian kernel can only use 1920×1280.

By the lack of DRM reported at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968181
I can only use fbdev_backend in weston/wayland and
xserver-xorg-video-fbdev.

They only recognize 1920×1280. Relevant Debian kernel log is

[0.920977] simple-framebuffer 3e267000.framebuffer: framebuffer at 
0x3e267000, 0x96 bytes, mapped to 0x(ptrval)
[0.921003] simple-framebuffer 3e267000.framebuffer: format=a8r8g8b8, 
mode=1920x1280x32, linelength=7680
[0.946638] Console: switching to colour frame buffer device 240x80
[0.971786] simple-framebuffer 3e267000.framebuffer: fb0: simplefb 
registered!

Best regards, Ryutaroh Matsumoto

-- Package-specific info:
** Version:
Linux version 5.7.0-2-arm64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 
(Debian 9.3.0-15), GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 
5.7.10-1 (2020-07-26)

** Command line:
video=HDMI-A-1:3840x2160M@30,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48
 dma.dmachans=0x71f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=tty0 
console=ttyS1,115200 root=/dev/mmcblk1p2 rw elevator=bfq fsck.repair=yes 
net.ifnames=0  rootwait systemd.unified_cgroup_hierarchy=1

** Tainted: C (1024)
 * staging driver was loaded

** Kernel log:
Unable to read kernel log; any relevant messages should be attached
dmesg output is below:

[0.00] Booting Linux on physical CPU 0x00 [0x410fd083]
[0.00] Linux version 5.7.0-2-arm64 (debian-ker...@lists.debian.org) 
(gcc version 9.3.0 (Debian 9.3.0-15), GNU ld (GNU Binutils for Debian) 2.35) #1 
SMP Debian 5.7.10-1 (2020-07-26)
[0.00] Machine model: Raspberry Pi 4 Model B Rev 1.4
[0.00] efi: UEFI not found.
[0.00] Reserved memory: created CMA memory pool at 0x2900, 
size 64 MiB
[0.00] OF: reserved mem: initialized node linux,cma, compatible id 
shared-dma-pool
[0.00] NUMA: No NUMA configuration found
[0.00] NUMA: Faking a node at [mem 
0x-0x0001]
[0.00] NUMA: NODE_DATA [mem 0x1ff0730c0-0x1ff074fff]
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x-0x3fff]
[0.00]   DMA32[mem 0x4000-0x]
[0.00]   Normal   [mem 0x0001-0x0001]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x2fff]
[0.00]   node   0: [mem 0x4000-0xfbff]
[0.00]   node   0: [mem 0x0001-0x0001]
[0.00] Initmem setup node 0 [mem 0x-0x0001]
[0.00] On node 0 totalpages: 2015232
[0.00]   DMA zone: 3072 pages used for memmap
[0.00]   DMA zone: 0 pages reserved
[0.00]   DMA zone: 196608 pages, LIFO batch:63
[0.00]   DMA32 zone: 12288 pages used for memmap
[0.00]   DMA32 zone: 770048 pages, LIFO batch:63
[0.00]   Normal zone: 16384 pages used for memmap
[0.00]   Normal zone: 1048576 pages, LIFO batch:63
[0.00] percpu: Embedded 32 pages/cpu s93720 r8192 d29160 u131072
[0.00] pcpu-alloc: s93720 r8192 d29160 u131072 alloc=32*4096
[0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[0.00] Detected PIPT I-cache on CPU0
[0.00] CPU features: detected: EL2 vector hardening
[0.00] CPU features: kernel page table isolation forced ON by KASLR
[0.00] CPU features: detected: Kernel page table isolation (KPTI)
[0.00] ARM_SMCCC_ARCH_WORKAROUND_1 missing from firmware
[0.00] CPU features: detected: ARM erratum 1319367
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 1983488
[0.00] Policy zone: Normal
[0.00] Kernel command line: 
video=HDMI-A-1:3840x2160M@30,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48
 dma.dmachans=0x71f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=tty0 
console=ttyS1,115200 root=/dev/mmcblk1p2 rw elevator=bfq fsck.repair=yes 
net.ifnames=0  rootwait systemd.unified_cgroup_hierarchy=1
[0.00] Kernel parameter elevator= does not have any effect anymore.
   Please use sysfs to set IO scheduler for individual devices.
[0.00] Dentry cache hash table entries: 1048576 (order: 11, 8388608 
bytes, linear)
[

Bug#920903: openjdk-11-jdk-headless: ships documentation for JDK 8, not JDK 11

[Etienne Dysli Metref]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi there!

As a Java developer, I'm very much interested in having this bug
fixed. It has already caused me to give wrong information to other
people... :/ For example: the java(1) man page lists the option
`-XX:+HeapDumpOnOutOfMemory`, but this option has been renamed to
`-XX:+HeapDumpOnOutOfMemoryError` in Java 11.

Is this a Debian packaging problem or does upstream provide the wrong
documentation?

Let me know if I can help fix this, I know Debian packaging a bit.

Cheers,
  Etienne
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEELcQv7Fsn8jFmeD9mw2QssxGaOsAFAl8xJi8ACgkQw2QssxGa
OsCBwA//e9Wwt81bhEkr1dgUG6i60H4Ufe163Tzlp18LZKqk+mSV7zvHiFhSmNAv
QPsE151rkLcC6G7bXNCCOfgr9NasS499btW+4qSrm8Yw7gDN6O8SHrpCV0Yigrun
2+CDmHYyBzN9J/OgoFGA4YYeYwukP6BZxDK8gdGLMcAfqmOiKwncILBpM8HVyKBD
xf8WQcj6YZiTrPLSdYzZJ2Y+bupHia50y8EEjeottiQropbV/9l+Q40Zt1sFtzP/
/fchNJ9IC03Fep2808nla8zSE4k9bnp/EmWBOrm3mlVN377Mko2aZOkflcr+Hdl5
kCQ1WNyFvvVAsZPK2Ihs4v2WmE7Eoo4VCbmdGJgNvKNDMiSTYnZHJZy5oNOcecTO
WO5LVFPWYEPNIWQa37QQTmv8sbf83mS8jChp+g740LVD3BafRrQpujeD/KgxZJbn
wlwyYEU0vMG39wBjUebD1/6mSohRtI5AcqOPwW7VpyRvhyYTfqGEDv2xfqomTuHe
WeaSB+914cuEomfwd4OiySio0yuVmTzXvdNv08LPme6QDecs/PkkuzYS2LRO+oZx
iysJNCyq5DgHv7DJKbzUQPEzwxtfrPK2Y13BLMOB/wiSct0Mdt28juGLyuM4PmPB
/o6sG7im9qxHO/eaaLRRF4CFyhW2PyVqpVuJZ9e96gIzF7ZZ8FM=
=cGxs
-END PGP SIGNATURE-

Bug#968187: dh_missing: please make the examples from dh_missing reproducible

[Chris Lamb]

Source: debhelper
Version: 13.2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: filesystem toolchain
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0] I noticed that
dh_missing was choosing example files in a non-deterministic manner:

  As an example, perhaps you want to replace:
  -* muroarstream.1
  +* muroar_write.3
  with:
  -* usr/share/man/man1/muroarstream.1
  +* usr/share/man/man3/muroar_write.3
  in a file in debian/ or as argument to one of the dh_* tools called 
from debian/rules.

To be clear, this does not affect the reproducibility of packages that
use dh_missing, but it does introduce unnecessary noise between two
build logs. (I use these often when diagnosing reproducibility
issues.)

Patch attached. An alternative might be to use the preprocess part of
File::Find, but just throwing a sort in here is a bit shorter.

  [0] https://reproducible-builds.org/


Regards,

--
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-diff --git a/dh_missing b/dh_missing
index f5e7c78..af30543 100755
--- a/dh_missing
+++ b/dh_missing
@@ -198,7 +198,7 @@ if (@missing) {
my %seen_basename = map { basename($_) => $_ } @installed;
my $multiarch = dpkg_architecture_value("DEB_HOST_MULTIARCH");
my $seen_ma_value = 0;
-   for my $file (@missing) {
+   for my $file (sort @missing) {
my $basename = basename($file);
if (exists($seen_basename{$basename})) {
my $alt_source = $seen_basename{$basename};

Bug#968185: pixelmed-codec: please make the build reproducible

[Chris Lamb]

Source: pixelmed-codec
Version: 20200328-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0] we noticed that
pixelmed-codec could not be built reproducibly.

This is because recently (?) upstream generated a new imageio .jar
file and my previous patch to ensure that the BUILDDATE file needed to
be updated.

Patch attached that abstracts out the generation and uses it two
places.

 [0] https://reproducible-builds.org/


Regards,

--
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   ` a/Makefile  2020-08-10 11:23:34.813798287 +0100
--- b/Makefile  2020-08-10 11:44:43.921980734 +0100
@@ -65,20 +65,21 @@
rm -f META-INF/services/javax.imageio.spi.ImageReaderSpi
echo >META-INF/services/javax.imageio.spi.ImageReaderSpi 
"com.pixelmed.imageio.JPEGLosslessImageReaderSpi"
 
-pixelmed_codec.jar:
-   (cd com/pixelmed/codec/jpeg; make all)
+BUILDDATE:
 ifdef SOURCE_DATE_EPOCH
-   LC_ALL=C date --utc --date="@$$SOURCE_DATE_EPOCH" >BUILDDATE
+   LC_ALL=C date --utc --date="@$$SOURCE_DATE_EPOCH" >$@
 else
-   date >BUILDDATE
+   date >$@
 endif
+
+pixelmed_codec.jar: BUILDDATE
+   (cd com/pixelmed/codec/jpeg; make all)
jar -cvf $@ BUILDDATE COPYRIGHT \
com/pixelmed/codec/jpeg/*.class
 
-pixelmed_imageio.jar:  metainf
+pixelmed_imageio.jar: metainf BUILDDATE
(cd com/pixelmed/codec/jpeg; make all)
(cd com/pixelmed/imageio; make all)
-   date >BUILDDATE
jar -cvf $@ BUILDDATE COPYRIGHT \
META-INF/services/javax.imageio.spi.ImageReaderSpi \
com/pixelmed/codec/jpeg/*.class \
--- a/debian/patches/reproducible_build.patch   2020-08-10 11:23:34.817798340 
+0100
--- b/debian/patches/reproducible_build.patch   2020-08-10 11:44:51.858080884 
+0100
@@ -3,17 +3,31 @@
 Last-Update: 2016-08-11
 Bug-Debian: https://bugs.debian.org/834052
 
 a/Makefile
-+++ b/Makefile
-@@ -67,7 +67,11 @@ metainf:
+--- pixelmed-codec-20200328.orig/Makefile
 pixelmed-codec-20200328/Makefile
+@@ -65,16 +65,21 @@ metainf:
+   rm -f META-INF/services/javax.imageio.spi.ImageReaderSpi
+   echo >META-INF/services/javax.imageio.spi.ImageReaderSpi 
"com.pixelmed.imageio.JPEGLosslessImageReaderSpi"
  
- pixelmed_codec.jar:
-   (cd com/pixelmed/codec/jpeg; make all)
+-pixelmed_codec.jar:
++BUILDDATE:
 +ifdef SOURCE_DATE_EPOCH
-+  LC_ALL=C date --utc --date="@$$SOURCE_DATE_EPOCH" >BUILDDATE
++  LC_ALL=C date --utc --date="@$$SOURCE_DATE_EPOCH" >$@
 +else
-   date >BUILDDATE
++  date >$@
 +endif
++
++pixelmed_codec.jar: BUILDDATE
+   (cd com/pixelmed/codec/jpeg; make all)
+-  date >BUILDDATE
jar -cvf $@ BUILDDATE COPYRIGHT \
com/pixelmed/codec/jpeg/*.class
  
+-pixelmed_imageio.jar: metainf
++pixelmed_imageio.jar: metainf BUILDDATE
+   (cd com/pixelmed/codec/jpeg; make all)
+   (cd com/pixelmed/imageio; make all)
+-  date >BUILDDATE
+   jar -cvf $@ BUILDDATE COPYRIGHT \
+   META-INF/services/javax.imageio.spi.ImageReaderSpi \
+   com/pixelmed/codec/jpeg/*.class \

Bug#968186: python3-rgain3: API is potentially about to break

[Simon McVittie]

Package: python3-rgain3
Version: 1.0.0-1
Severity: serious
Justification: maintainer says so
Tags: upstream
Forwarded: https://github.com/chaudum/rgain/issues/29

Upstream changes in rgain3 have broken the import ABI. This doesn't mean
anything for the replaygain and collectiongain CLI tools, but would break
compatibility if we had packages in Debian that imported it as a library.

I've asked for clarification on whether this was intentional, but until I
get an answer, this library probably shouldn't migrate.

smcv

Bug#965352: libopenmpi3: breaks tests in client programs

[Drew Parsons]

Package: libopenmpi3
Followup-For: Bug #965352

mpi4py upstream (Lisandro Dalcin) suggests in the short term to skip
the failing mpi4py tests for openmpi 4.0.4 (the failing tests are in
test_rma.py and test_rma_nb.py, and also one in test_win.py)

Lisandro suggests also it could be helpful for catching these problems
if OpenMPI upstream included an mpi4py test in its CI testing. Would
you be able to convince OpenMPI upstream to do this?
(I'll mention the idea to yosefe in the UCX bug report).

I've added a patch to skip the problematic tests in mpi4py 3.0.3-6.

I'll leave it to you to judge whether that's enough to close this
libopenmpi3 bug, or whether we should keep it open (and downgrade
severity).

Drew

Bug#968184: autopkgtest is infinitely outputting "ERROR: not valid"

[Iain Lane]

Package: src:calcluix-cgx
Version: 2.17+dfsg-1
Severity: normal

I just noticed on the Ubuntu autopkgtest runners that our disk had
filled up. When investigating the cause, it turns out that calculix-cgx
autopkgtest runs of version 2.17+dfsg-1 have been (apparently)
infinitely spamming "ERROR:^@ not valid". The biggest such log that I
noticed was 37G!

It looks like

autopkgtest [07:05:15]: test build1: [---
on a Linux machine, nodename autopkgtest, release 5.4.0-42-generic, version 
#46-Ubuntu SMP Fri Jul 10 00:22:04 UTC 2020, machine ppc64le 
 The HOME was detected:/home/ubuntu
parameters:3 arguments:2

send.fbl opened
 reading file
 WARNING: Found a 'sys' command (a system call):
sys rm -f *.flm *.rad *.msh *.bou *.equ
 Since a system call can be dangerous You have to chose now between stop (s), 
continue (c) or enable (e). If you chose 'e' the 'sys' command will be 
un-locked by creating or extending your personal config file 
'/home/ubuntu/.cgx' with the un-lock command ALLOW_SYS. You may delete this 
command from your '.cgx' file to lock the 'sys' command again.
 Waiting for user input. Please type into the terminal either s,c or e (the 
terminal has to be the active window!):
 ERROR:^@ not valid
 ERROR:^@ not valid
 ERROR:^@ not valid
 ... (forever)

I've pinged the Debian CI people, will report back & upgrade the severity if
they confirm it is happening on Debian too.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

Bug#966998: lxc: FTBFS: lsm/selinux.c:35:2: error: ‘security_context_t’ is deprecated [-Werror=deprecated-declarations]

[Harald Dunkel]

AFAICT lxc-4.0.4 got rid of security_context_t:


commit 15d82dfe4f7900be54e06b6ca0a79321ee2a9b34
Author: Christian Brauner 
Date:   Sat Jul 25 11:36:46 2020 +0200

selinux: remove security_context_t usage as it's deprecated

Link: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1888705
Signed-off-by: Christian Brauner 


I would suggest to use upstream's new version.

Regards
Harri

Bug#961584: lxc-stop fails with exit code 1

[Harald Dunkel]

I am using LXC 4.0.2 on about 25 systems without problems. None of these
hosts does nested virtualization, though.

Nested virtualization and cgroups vs cgroups2 is a *highly* complex issue.
Can you reproduce this problem outside of your Docker setup? I wouldn't
like to see LXC dropped for Bullseye, just due to some hiccup thats is
not relevant for anybody except the few guys running LXC within Docker.


Regards
Harri

Bug#968183: chirp: please make the build reproducible

[Chris Lamb]

Source: chirp
Version: 1:20200227+py3+20200213-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0] we noticed that
chirp could not be built reproducibly.

This is because it shipped a debug.log file that contained non-
deterministic data like timestamps, etc.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/rules  2020-08-10 11:23:56.302078294 +0100
--- b/debian/rules  2020-08-10 11:27:44.805034313 +0100
@@ -5,3 +5,4 @@
 
 execute_after_dh_auto_install:
mv debian/chirp/usr/bin/chirpwx.py debian/chirp/usr/bin/chirpw
+   find debian/chirp/usr/lib -type f -name debug.log -delete

Bug#957063: calculix-cgx: ftbfs with GCC-10

[Gianfranco Costamagna]

control: fixed -1 2.17+dfsg-1
control: close -1

We can consider it "fixed" in the new release

G.

On Fri, 17 Apr 2020 10:57:34 + Matthias Klose  wrote:
> Package: src:calculix-cgx
> Version: 2.11+dfsg-1
> Severity: normal
> Tags: sid bullseye
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-10
> 
> Please keep this issue open in the bug tracker for the package it
> was filed for.  If a fix in another package is required, please
> file a bug for the other package (or clone), and add a block in this
> package. Please keep the issue open until the package can be built in
> a follow-up test rebuild.
> 
> The package fails to build in a test rebuild on at least amd64 with
> gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
> severity of this report will be raised before the bullseye release,
> so nothing has to be done for the buster release.
> 
> The full build log can be found at:
> http://people.debian.org/~doko/logs/gcc10-20200225/calculix-cgx_2.11+dfsg-1_unstable_gcc10.log
> The last lines of the build log are at the end of this report.
> 
> To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
> or install the gcc, g++, gfortran, ... packages from experimental.
> 
>   apt-get -t=experimental install g++ 
> 
> Common build failures are new warnings resulting in build failures with
> -Werror turned on, or new/dropped symbols in Debian symbols files.
> For other C/C++ related build failures see the porting guide at
> http://gcc.gnu.org/gcc-10/porting_to.html
> 
> [...]
> generateTet.cpp:402:10: warning: deprecated conversion from string constant 
> to ‘char*’ [-Wwrite-strings]
>   402 |   delSet("+snodSet");
>   |  ^~
> generateTet.cpp:403:10: warning: deprecated conversion from string constant 
> to ‘char*’ [-Wwrite-strings]
>   403 |   delSet("+velemSet");
>   |  ^~~
> generateTet.cpp:404:20: warning: deprecated conversion from string constant 
> to ‘char*’ [-Wwrite-strings]
>   404 |   snodSet=pre_seta("+snodSet","i",0);
>   |^~
> generateTet.cpp:404:31: warning: deprecated conversion from string constant 
> to ‘char*’ [-Wwrite-strings]
>   404 |   snodSet=pre_seta("+snodSet","i",0);
>   |   ^~~
> generateTet.cpp:405:18: warning: deprecated conversion from string constant 
> to ‘char*’ [-Wwrite-strings]
>   405 |   setNr=pre_seta("+velemSet","i",0);
>   |  ^~~
> generateTet.cpp:405:30: warning: deprecated conversion from string constant 
> to ‘char*’ [-Wwrite-strings]
>   405 |   setNr=pre_seta("+velemSet","i",0);
>   |  ^~~
> generateTet.cpp:419:39: warning: deprecated conversion from string constant 
> to ‘char*’ [-Wwrite-strings]
>   419 |   for(k=0; k<3; k++) 
> seta(snodSet,"n",e_enqire[surf[s].elem[i]].nod[k]);
>   |   ^~~
> generateTet.cpp:439:14: warning: deprecated conversion from string constant 
> to ‘char*’ [-Wwrite-strings]
>   439 | { errMsg("ERROR: realloc failure in generateTet\n"); return(0); }
>   |  ^
> generateTet.cpp:500:19: warning: deprecated conversion from string constant 
> to ‘char*’ [-Wwrite-strings]
>   500 |   if ( (  readNG( "test.vol", anz_ng, , _ng, _ng, 
> NULL)) == -1)
>   |   ^~

Bug#957660: [Re] paraview: ftbfs with GCC-10

[Jakob Meng]

A fix for compiling paraview 5.7.0-4 with gcc10 can be found in bug
#959387 [1], esp. [2].

Ref.:
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959387
[2]
https://git.inf.h-brs.de/jmeng2m/debian-package-paraview/-/commit/35d8cae30d4e9d1c6da980f2b359b428a5beea89




signature.asc
Description: OpenPGP digital signature

Bug#968182: mocha: fails at runtime: Error: Cannot find module 'strip-json-comments'

[Jonas Smedegaard]

Package: mocha
Version: 7.0.1+ds1-2
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

running mocha for recent releases of project domino fails:

NODE_ENV=test mocha --reporter tap --no-timeout test/domino.js test/index.js 
test/parsing.js test/xss.js
/usr/share/nodejs/mocha/lib/cli/config.js:84
throw new Error(`failed to parse config "${filepath}": ${err}`);
^

Error: failed to parse config "/build/node-domino-2.1.6~ds/.mocharc.json": 
Error: Cannot find module 'strip-json-comments'

It seems that the mere existence of a JSON-based config file
makes mocha require strip-json-comments.

Mocha should depend on (or at least recommend) node-strip-json-comments.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl8xHKIACgkQLHwxRsGg
ASEOpA//XjynHjnQRbf9RKT3B5EernM/LySGlxavrhs5i5AxTHxHomUgSImmg6ZE
sM5SkMeFWoP54M9+4Xaewa15lxyzNsXYabSSSVx8kp5kNHEi/Bdr8y49c4sbIE1m
oWqtwrC0Z95gqwzz/0qDObq4xTYG2swpRgrWqxH1tY2IcDWJxGNxwdX48Sgd79N9
JQyn9EUaOPnLjfOQ6eKdU5zP4PBteOKcNZnVzCNG7JkwfDKO6sS7NU0y1q28sp5G
zw9xBuFzyAaZh5RRCCt9l35nDrYXTLcltJ6I7P+EjSdDlnOQvXj//8t2NS4Oy4AF
za0EfZ/laozlzyyaZBm+5gLaPtGlDm6QSTyG6fCQ/eEIKlsCVrJG6WSY7vlL5ZgH
UiQ9JIgBW1+PojWiSkGS/rspIwms63Xv7mtJ4TtMVpfm0oz0g6y9msvGXSWIicCT
oI6jZXkQSeTjLd+YayEvMA/aqbj1z8QPnpohcPpTaXoI8eeeOJSTqUDkBvSq4LKU
JPGhv4lJvcQll9lYcjBcDDNZR1IWJLMGNixPFwYIg3WtQE7RkPw87MaTVoi2yJmq
dE2BQrqtcyvVsQm0RzIgW3nHyJiuJjC2MlFNSF2CpuiNbFtcuKbkeeA8ahw3eK5k
VnuUqjs1DRbDzqXe4O7iffLqZBCi2rdspPlmcnrfbO90adzw39c=
=dIa7
-END PGP SIGNATURE-

Bug#968181: linux-image-5.7.0-2-arm64: DRM unavailable on Rapsberry Pi 4B

[Ryutaroh Matsumoto]

Package: src:linux
Version: 5.7.10-1
Severity: normal

Dear Maintainer,

DRM is unavailable on Raspberry Pi 4B (board revision 1.4).
Lack of DRM prevents drm_backend in weston/wayland.
X server does not start without installation of xserver-xorg-video-fbdev.

In contrast to the Debian kernel, the kernel from Raspbian Foundation
allows drm_backend in weston, and it does not need xserver-xorg-video-fbdev.

Best regards, Ryutaroh Matsumoto


-- Package-specific info:
** Version:
Linux version 5.7.0-2-arm64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 
(Debian 9.3.0-15), GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 
5.7.10-1 (2020-07-26)

** Command line:
video=HDMI-A-1:3840x2160M@30,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48
 dma.dmachans=0x71f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=tty0 
console=ttyS1,115200 root=/dev/mmcblk1p2 rw elevator=bfq fsck.repair=yes 
net.ifnames=0  rootwait systemd.unified_cgroup_hierarchy=1

** Tainted: C (1024)
 * staging driver was loaded

** Kernel log:
Unable to read kernel log; any relevant messages should be attached
dmesg out put is included here:


[0.00] Booting Linux on physical CPU 0x00 [0x410fd083]
[0.00] Linux version 5.7.0-2-arm64 (debian-ker...@lists.debian.org) 
(gcc version 9.3.0 (Debian 9.3.0-15), GNU ld (GNU Binutils for Debian) 2.35) #1 
SMP Debian 5.7.10-1 (2020-07-26)
[0.00] Machine model: Raspberry Pi 4 Model B Rev 1.4
[0.00] efi: UEFI not found.
[0.00] Reserved memory: created CMA memory pool at 0x2900, 
size 64 MiB
[0.00] OF: reserved mem: initialized node linux,cma, compatible id 
shared-dma-pool
[0.00] NUMA: No NUMA configuration found
[0.00] NUMA: Faking a node at [mem 
0x-0x0001]
[0.00] NUMA: NODE_DATA [mem 0x1ff0730c0-0x1ff074fff]
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x-0x3fff]
[0.00]   DMA32[mem 0x4000-0x]
[0.00]   Normal   [mem 0x0001-0x0001]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x2fff]
[0.00]   node   0: [mem 0x4000-0xfbff]
[0.00]   node   0: [mem 0x0001-0x0001]
[0.00] Initmem setup node 0 [mem 0x-0x0001]
[0.00] On node 0 totalpages: 2015232
[0.00]   DMA zone: 3072 pages used for memmap
[0.00]   DMA zone: 0 pages reserved
[0.00]   DMA zone: 196608 pages, LIFO batch:63
[0.00]   DMA32 zone: 12288 pages used for memmap
[0.00]   DMA32 zone: 770048 pages, LIFO batch:63
[0.00]   Normal zone: 16384 pages used for memmap
[0.00]   Normal zone: 1048576 pages, LIFO batch:63
[0.00] percpu: Embedded 32 pages/cpu s93720 r8192 d29160 u131072
[0.00] pcpu-alloc: s93720 r8192 d29160 u131072 alloc=32*4096
[0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[0.00] Detected PIPT I-cache on CPU0
[0.00] CPU features: detected: EL2 vector hardening
[0.00] CPU features: kernel page table isolation forced ON by KASLR
[0.00] CPU features: detected: Kernel page table isolation (KPTI)
[0.00] ARM_SMCCC_ARCH_WORKAROUND_1 missing from firmware
[0.00] CPU features: detected: ARM erratum 1319367
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 1983488
[0.00] Policy zone: Normal
[0.00] Kernel command line: 
video=HDMI-A-1:3840x2160M@30,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48
 dma.dmachans=0x71f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=tty0 
console=ttyS1,115200 root=/dev/mmcblk1p2 rw elevator=bfq fsck.repair=yes 
net.ifnames=0  rootwait systemd.unified_cgroup_hierarchy=1
[0.00] Kernel parameter elevator= does not have any effect anymore.
   Please use sysfs to set IO scheduler for individual devices.
[0.00] Dentry cache hash table entries: 1048576 (order: 11, 8388608 
bytes, linear)
[0.00] Inode-cache hash table entries: 524288 (order: 10, 4194304 
bytes, linear)
[0.00] mem auto-init: stack:off, heap alloc:off, heap free:off
[0.00] software IO TLB: mapped [mem 0x2500-0x2900] (64MB)
[0.00] Memory: 4732836K/8060928K available (10684K kernel code, 1848K 
rwdata, 3808K rodata, 5184K init, 561K bss, 277044K reserved, 65536K 
cma-reserved)
[0.00] random: 

Bug#959387: [Re] paraview-dev: missing cmake vtk modules in the dev package, cannot use

[Jakob Meng]

PPS: Binary packages can be downloaded here:

http://home.infcs.de/~jmeng2m/debian-package-paraview/

They were build using my university's GitLab CI instance and the
official debian/buildd:sid docker image.

CI file:
https://git.inf.h-brs.de/jmeng2m/debian-package-paraview/-/blob/gitlab-ci/.gitlab-ci.yml

Build log:
https://git.inf.h-brs.de/jmeng2m/debian-package-paraview/-/jobs/421




signature.asc
Description: OpenPGP digital signature