Bug#973273: python-is-python2 misses Breaks+Replaces: python-minimal

[Helmut Grohne]

Package: python-is-python2
Version: 2.7.18-6
Severity: serious
Justifictaion: fails to install

Upgrading from "python" to "python-is-python" may fail:

| Unpacking python-is-python2 (2.7.18-6) ...
| dpkg: error processing archive 
/var/cache/apt/archives/python-is-python2_2.7.18-6_all.deb (--unpack):
|  trying to overwrite '/usr/bin/python', which is also in package 
python-minimal 2.7.17-2
| Errors were encountered while processing:
|  /var/cache/apt/archives/python-is-python2_2.7.18-6_all.deb
| E: Sub-process /usr/bin/dpkg returned an error code (1)

Please add Breaks+Replaces on python-minimal.

Helmut

Bug#973010: [pcp] Bug#973010: pcp is uninstallable on many architectures due to new bpftrace dependency

[Nathan Scott]

On Wed, Oct 28, 2020 at 7:56 AM Martin Pitt  wrote:
>
> Package: pcp
> Version: 5.2.1-1
> [...]
> But the "bpftrace" package only exists on a few architectures [1]. This is 
> what
> makes the package uninstallable and prevents testing migration [2].
>
> Please fix
> that at least by restricting the architectures, like so:

Thanks Martin - we'll tackle this in the next update (pcp-5.2.2,
couple weeks out).

>   Depends: ${shlibs:Depends}, ${misc:Depends}, gawk, procps, 
> libpcp-pmda-perl, python3-pcp, python3, bpftrace (>= 0.9.2) [amd64 arm64 
> ppc64 ppc64el], libpcp-web1
>
> Preferably you would also drop it to Recommends:, as hopefully bpftrace isn't
> an absolute requirement for running PCP? I.e.

It's not an absolute requirement - more of a Suggests: line entry, even.

cheers.

--
Nathan

Bug#973272: mathomatic FTCBFS: does not pass cross tools to make

[Helmut Grohne]

Source: mathomatic
Version: 16.0.5-3
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

mathomatic fails to cross build from source, because it does not pass
cross tools to make. The easiest way of doing so - using dh_auto_build -
makes mathomatic cross buildable. Please consider applying the attached
patch.

Helmut
diff --minimal -Nru mathomatic-16.0.5/debian/changelog 
mathomatic-16.0.5/debian/changelog
--- mathomatic-16.0.5/debian/changelog  2020-07-27 06:02:41.0 +0200
+++ mathomatic-16.0.5/debian/changelog  2020-10-27 15:24:16.0 +0100
@@ -1,3 +1,10 @@
+mathomatic (16.0.5-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 27 Oct 2020 15:24:16 +0100
+
 mathomatic (16.0.5-3) unstable; urgency=medium
 
   * Build with libedit instead of libeditline (Closes: #966331)
diff --minimal -Nru mathomatic-16.0.5/debian/rules 
mathomatic-16.0.5/debian/rules
--- mathomatic-16.0.5/debian/rules  2020-07-27 06:02:41.0 +0200
+++ mathomatic-16.0.5/debian/rules  2020-10-27 15:24:15.0 +0100
@@ -9,8 +9,8 @@
dh $@
 
 override_dh_auto_build:
-   CFLAGS="$(CFLAGS) -DEDITLINE" LDLIBS="-ledit" $(MAKE)
-   $(MAKE) -C primes
+   CFLAGS="$(CFLAGS) -DEDITLINE" LDLIBS="-ledit" dh_auto_build
+   dh_auto_build --sourcedirectory=primes
$(MAKE) pdf
 
 override_dh_auto_test:

Bug#973274: mp3gain FTCBFS: does not pass cross tools to make

[Helmut Grohne]

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

mp3gain fails to cross build from source, because it does not pass cross
tools to make. The easiest way of fixing that - using dh_auto_build -
makes mp3gain cross buildable. Please consider applying the attached
patch.

Helmut
diff --minimal -Nru mp3gain-1.6.2/debian/changelog 
mp3gain-1.6.2/debian/changelog
--- mp3gain-1.6.2/debian/changelog  2020-10-11 17:40:06.0 +0200
+++ mp3gain-1.6.2/debian/changelog  2020-10-28 06:28:42.0 +0100
@@ -1,3 +1,10 @@
+mp3gain (1.6.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 28 Oct 2020 06:28:42 +0100
+
 mp3gain (1.6.2-1) unstable; urgency=high
 
   [ Scott Hardin ]
diff --minimal -Nru mp3gain-1.6.2/debian/rules mp3gain-1.6.2/debian/rules
--- mp3gain-1.6.2/debian/rules  2020-06-21 10:45:06.0 +0200
+++ mp3gain-1.6.2/debian/rules  2020-10-28 06:28:41.0 +0100
@@ -26,7 +26,7 @@
 build-stamp:
dh_testdir
 
-   $(MAKE)
+   dh_auto_build
docbook-to-man  debian/mp3gain.sgml > debian/mp3gain.1
 
touch build-stamp

Bug#973269: Acknowledgement (openjdk-11-jdk-headless - upgrade to 11.0.9+11-1~deb10u1 removes default-jdk)

[McIntyre, Vincent (CASS, Marsfield)]

please close this duplicate of 973268. apologies for the resend.

Bug#973052: (unbound unaccountably crashes inside libevent (Assertion nread >= 0 failed in evmap_io_del_))

[Daniel Kahn Gillmor]

I've pushed the patch in #973052 to a new branch named bug-973052 in the
https://salsa.debian.org/dns-team/unbound repo (on top of
branches/1.9.0-2_deb10).

Hopefully one of the other DNS folks will review it and merge it if it
looks reasonable.  Not sure whether we should release a new version with
just this fix, but it might be worth proposing it.

  --dkg


signature.asc
Description: PGP signature

Bug#973270: RFP: qmidiplayer -- feature-rich Qt5 MIDI player

[Wang Gary]

package: wnpp
Severity: wishlist

*URL : https://cgit.chrisoft.org/QMidiPlayer.git/
*License : GPL-3.0
*Description : Feature-rich Qt5 MIDI player

QMidiPlayer is a cross-platform midi file player based on
libfluidsynth and Qt. Featuring on-the-fly channel parameters
and synthesizer effects editing plus two MIDI visualizations,
it's very similar to vanBasco's Karaoke Player but
cross-platform, and is also free and open source.

The OpenGL visualization can either visualize real-time MIDI
data using a pianoroll similar to Synthesia, MIDITrail and
MAMPlayer during playback, or render the visualization to a
video file.

Features:

* Channel mute/solo
* Editing channel parameters on-the-fly
* Playlists
* Editing synthesizer effects
* Rendering MIDI to wave file
* Visualization
* MIDI mapping (RtMidi and plugins)
* Plugin interface for extending the player easily

Bug#973269: openjdk-11-jdk-headless - upgrade to 11.0.9+11-1~deb10u1 removes default-jdk

[McIntyre, Vincent (CASS, Marsfield)]

Package: openjdk-11-jdk-headless
Version: 11.0.9+11-1~deb10u1
Severity: minor

This was a suprise, but perhaps it's intended behaviour.
Please close if so.

   * What led up to the situation?

These packages were waiting for upgrade
   openjdk-11-jre  11.0.8+10-1~deb10u1 -> 11.0.9+11-1~deb10u1
   openjdk-11-jdk-headless 11.0.8+10-1~deb10u1 -> 11.0.9+11-1~deb10u1
   openjdk-11-jre-headless 11.0.8+10-1~deb10u1 -> 11.0.9+11-1~deb10u1
but were being held back.

  * What exactly did you do (or not do)...

# apt full-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  default-jdk-headless
Use 'sudo apt autoremove' to remove it.
The following packages will be REMOVED:
  default-jdk openjdk-11-jdk
The following packages will be upgraded:
  openjdk-11-jdk-headless openjdk-11-jre openjdk-11-jre-headless
3 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
Need to get 254 MB of archives.
After this operation, 1,438 kB disk space will be freed.
Do you want to continue? [Y/n] y

   * What was the outcome of this action?

Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
(Reading database ... 272409 files and directories currently installed.)
Removing default-jdk (2:1.11-71) ...
Removing openjdk-11-jdk:amd64 (11.0.8+10-1~deb10u1) ...
(Reading database ... 272393 files and directories currently installed.)
Preparing to unpack .../openjdk-11-jre_11.0.9+11-1~deb10u1_amd64.deb ...
Unpacking openjdk-11-jre:amd64 (11.0.9+11-1~deb10u1) over (11.0.8+10-1~deb10u1) 
...
Preparing to unpack .../openjdk-11-jdk-headless_11.0.9+11-1~deb10u1_amd64.deb 
...
Unpacking openjdk-11-jdk-headless:amd64 (11.0.9+11-1~deb10u1) over 
(11.0.8+10-1~deb10u1) ...
Preparing to unpack .../openjdk-11-jre-headless_11.0.9+11-1~deb10u1_amd64.deb 
...
Unpacking openjdk-11-jre-headless:amd64 (11.0.9+11-1~deb10u1) over 
(11.0.8+10-1~deb10u1) ...
Setting up openjdk-11-jre-headless:amd64 (11.0.9+11-1~deb10u1) ...
Installing new version of config file /etc/java-11-openjdk/jfr/default.jfc ...
Installing new version of config file /etc/java-11-openjdk/jfr/profile.jfc ...
Installing new version of config file 
/etc/java-11-openjdk/security/blacklisted.certs ...
Installing new version of config file 
/etc/java-11-openjdk/security/java.security ...
Installing new version of config file 
/etc/java-11-openjdk/security/public_suffix_list.dat ...
Setting up openjdk-11-jre:amd64 (11.0.9+11-1~deb10u1) ...
Setting up openjdk-11-jdk-headless:amd64 (11.0.9+11-1~deb10u1) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for desktop-file-utils (0.23-4) ...

   * What outcome did you expect instead?

I wasn't expecting the default-* packages to be removed and I'm not quite
sure why they were, because they don't declare a versioned dependency on
the specific implementation, details below. It notice there is a versioned
Conflicts but it's unclear to me how that could be the problem.

$ apt-cache show default-jdk| egrep -e '(Ver|Dep)'
Version: 2:1.11-71
Depends: default-jre (= 2:1.11-71), default-jdk-headless (= 2:1.11-71), 
openjdk-11-jdk

$ apt-cache show default-jdk-headless | egrep -e '(Ver|Dep)'
Version: 2:1.11-71
Depends: default-jre-headless (= 2:1.11-71), openjdk-11-jdk-headless

$ apt-cache show default-jre-headless | egrep -e '(Ver|Dep)'
Version: 2:1.11-71
Depends: openjdk-11-jre-headless, java-common

$ apt-cache show openjdk-11-jdk | egrep -e '(Ver|Dep|Conf)'
Version: 11.0.9+11-1~deb10u1
Depends: openjdk-11-jre (= 11.0.9+11-1~deb10u1), openjdk-11-jdk-headless (= 
11.0.9+11-1~deb10u1), libc6 (>= 2.2.5), zlib1g (>= 1:1.1.4)
Conflicts: openjdk-11-jre-headless (<< 11~19-2)
Version: 11.0.8+10-1~deb10u1
Depends: openjdk-11-jre (= 11.0.8+10-1~deb10u1), openjdk-11-jdk-headless (= 
11.0.8+10-1~deb10u1), libc6 (>= 2.2.5), zlib1g (>= 1:1.1.4)
Conflicts: openjdk-11-jre-headless (<< 11~19-2)

$ apt-cache show openjdk-11-jre-headless | egrep -e '(Ver|Dep|Conf)'
Version: 11.0.9+11-1~deb10u1
Depends: ca-certificates-java (>= 20190405~), java-common (>= 0.28), libcups2, 
liblcms2-2 (>= 2.2+git20110628), libjpeg62-turbo (>= 1.3.1), libfontconfig1, 
libnss3 (>= 2:3.17.1), util-linux (>= 2.26.2-4), libasound2 (>= 1.0.16), libc6 
(>= 2.27), libfreetype6 (>= 2.3.5), libgcc1 (>= 1:3.4), libpcsclite1 (>= 
1.3.0), libstdc++6 (>= 4.1.1), libx11-6, libxext6, libxi6, libxrender1, 
libxtst6, zlib1g (>= 1:1.1.4)
Conflicts: openjdk-11-jdk-headless (<< 11~18-2), oracle-java11-installer
Version: 11.0.8+10-1~deb10u1
Depends: ca-certificates-java (>= 20190405~), java-common (>= 0.28), libcups2, 
liblcms2-2 (>= 2.2+git20110628), libjpeg62-turbo (>= 1.3.1), libfontconfig1, 
libnss3 (>= 2:3.17.1), util-linux (>= 2.26.2-4), libasound2 (>= 1.0.16), libc6 
(>= 2.27), libfreetype6 (>= 2.3.5), libgcc1 (>= 1:3.4), 

Bug#973241: network-manager: is crda still recommendable?

[Patrice Duroux]

In addition, it may be necessary to recommend wireless-regdb instead.
This package seems to contain some firmware files that may be
the ones cited in CRDA README.
 
Finally, note that currently, wireless-regdb suggests crda.

Bug#973268: openjdk-11-jdk-headless - upgrade to 11.0.9+11-1~deb10u1 removes default-jdk

[McIntyre, Vincent (CASS, Marsfield)]

Package: openjdk-11-jdk-headless
Version: 11.0.9+11-1~deb10u1
Severity: minor

This was a suprise but perhaps intended. Please close if so.

   * What led up to the situation?

These packages were waiting for upgrade
   openjdk-11-jre  11.0.8+10-1~deb10u1 -> 11.0.9+11-1~deb10u1
   openjdk-11-jdk-headless 11.0.8+10-1~deb10u1 -> 11.0.9+11-1~deb10u1
   openjdk-11-jre-headless 11.0.8+10-1~deb10u1 -> 11.0.9+11-1~deb10u1
but were being held back.

   * What exactly did you do (or not do)...

# apt full-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  default-jdk-headless
Use 'sudo apt autoremove' to remove it.
The following packages will be REMOVED:
  default-jdk openjdk-11-jdk
The following packages will be upgraded:
  openjdk-11-jdk-headless openjdk-11-jre openjdk-11-jre-headless
3 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
Need to get 254 MB of archives.
After this operation, 1,438 kB disk space will be freed.
Do you want to continue? [Y/n] y

   * What was the outcome of this action?

Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
(Reading database ... 272409 files and directories currently installed.)
Removing default-jdk (2:1.11-71) ...
Removing openjdk-11-jdk:amd64 (11.0.8+10-1~deb10u1) ...
(Reading database ... 272393 files and directories currently installed.)
Preparing to unpack .../openjdk-11-jre_11.0.9+11-1~deb10u1_amd64.deb ...
Unpacking openjdk-11-jre:amd64 (11.0.9+11-1~deb10u1) over (11.0.8+10-1~deb10u1) 
...
Preparing to unpack .../openjdk-11-jdk-headless_11.0.9+11-1~deb10u1_amd64.deb 
...
Unpacking openjdk-11-jdk-headless:amd64 (11.0.9+11-1~deb10u1) over 
(11.0.8+10-1~deb10u1) ...
Preparing to unpack .../openjdk-11-jre-headless_11.0.9+11-1~deb10u1_amd64.deb 
...
Unpacking openjdk-11-jre-headless:amd64 (11.0.9+11-1~deb10u1) over 
(11.0.8+10-1~deb10u1) ...
Setting up openjdk-11-jre-headless:amd64 (11.0.9+11-1~deb10u1) ...
Installing new version of config file /etc/java-11-openjdk/jfr/default.jfc ...
Installing new version of config file /etc/java-11-openjdk/jfr/profile.jfc ...
Installing new version of config file 
/etc/java-11-openjdk/security/blacklisted.certs ...
Installing new version of config file 
/etc/java-11-openjdk/security/java.security ...
Installing new version of config file 
/etc/java-11-openjdk/security/public_suffix_list.dat ...
Setting up openjdk-11-jre:amd64 (11.0.9+11-1~deb10u1) ...
Setting up openjdk-11-jdk-headless:amd64 (11.0.9+11-1~deb10u1) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for desktop-file-utils (0.23-4) ...

   * What outcome did you expect instead?

I wasn't expecting the default-* packages to be removed and I'm not
quite sure why they were, because they don't declare a versioned
dependency on the specific implementation, details below. I notice
there is a versioned Conflicts but it's unclear to me how that
could be the problem.

Kind regards

$ apt-cache show default-jdk| egrep -e '(Ver|Dep)'
Version: 2:1.11-71
Depends: default-jre (= 2:1.11-71), default-jdk-headless (= 2:1.11-71), 
openjdk-11-jdk

$ apt-cache show default-jdk-headless | egrep -e '(Ver|Dep)'
Version: 2:1.11-71
Depends: default-jre-headless (= 2:1.11-71), openjdk-11-jdk-headless

$ apt-cache show default-jre-headless | egrep -e '(Ver|Dep)'
Version: 2:1.11-71
Depends: openjdk-11-jre-headless, java-common

$ apt-cache show openjdk-11-jdk | egrep -e '(Ver|Dep|Conf)'
Version: 11.0.9+11-1~deb10u1
Depends: openjdk-11-jre (= 11.0.9+11-1~deb10u1), openjdk-11-jdk-headless (= 
11.0.9+11-1~deb10u1), libc6 (>= 2.2.5), zlib1g (>= 1:1.1.4)
Conflicts: openjdk-11-jre-headless (<< 11~19-2)
Version: 11.0.8+10-1~deb10u1
Depends: openjdk-11-jre (= 11.0.8+10-1~deb10u1), openjdk-11-jdk-headless (= 
11.0.8+10-1~deb10u1), libc6 (>= 2.2.5), zlib1g (>= 1:1.1.4)
Conflicts: openjdk-11-jre-headless (<< 11~19-2)

$ apt-cache show openjdk-11-jre-headless | egrep -e '(Ver|Dep|Conf)'
Version: 11.0.9+11-1~deb10u1
Depends: ca-certificates-java (>= 20190405~), java-common (>= 0.28), libcups2, 
liblcms2-2 (>= 2.2+git20110628), libjpeg62-turbo (>= 1.3.1), libfontconfig1, 
libnss3 (>= 2:3.17.1), util-linux (>= 2.26.2-4), libasound2 (>= 1.0.16), libc6 
(>= 2.27), libfreetype6 (>= 2.3.5), libgcc1 (>= 1:3.4), libpcsclite1 (>= 
1.3.0), libstdc++6 (>= 4.1.1), libx11-6, libxext6, libxi6, libxrender1, 
libxtst6, zlib1g (>= 1:1.1.4)
Conflicts: openjdk-11-jdk-headless (<< 11~18-2), oracle-java11-installer
Version: 11.0.8+10-1~deb10u1
Depends: ca-certificates-java (>= 20190405~), java-common (>= 0.28), libcups2, 
liblcms2-2 (>= 2.2+git20110628), libjpeg62-turbo (>= 1.3.1), libfontconfig1, 
libnss3 (>= 2:3.17.1), util-linux (>= 2.26.2-4), libasound2 (>= 1.0.16), libc6 
(>= 2.27), libfreetype6 (>= 2.3.5), libgcc1 (>= 1:3.4), 

Bug#592124: Dr

[wwwheadoffi...@gmail.com]

Bug#953529: Networking support in Keepassxc

[Andreas Kloeckner]

Hi there,

I'm writing to voice that I disagree with the premise of this bug
report. For instance, I find password autofill and automatic checking
against "Have I been Pwnd" valuable, and I wouldn't want to miss it.

So I would prefer that networking support is retained in KeepassXC, or
if it were to be disabled, I would prefer if it were done in a separate
package, e.g. keepassxc-nonetwork or some such.

Andreas



signature.asc
Description: PGP signature

Bug#966076: +1

[Andreas Kloeckner]

Hi there,

I'm just writing to say that I would also like this. And 2.6.2 was just
released upstream. Maybe that's a good enough excuse. :)

Just to be annoying, I created a zero-effort merge request:

https://salsa.debian.org/debian/keepassxc/-/merge_requests/7

Sorry,
Andreas



signature.asc
Description: PGP signature

Bug#973267: libtss2-dev: pkgconfig file included with libtss2-dev has invalid path

[Mario Limonciello]

Package: libtss2-dev
Version: 3.0.0-1
Severity: normal
X-Debbugs-Cc: mario.limoncie...@dell.com

Dear Maintainer,

The pkgconfig file included in libtss2-dev contains an invalid path:

Name: tss2-esys
Description: TPM2 Enhanced System API library.
URL: https://github.com/tpm2-software/tpm2-tss
Version: 3.0.1
Requires.private: tss2-mu tss2-sys
Cflags: -I${includedir} -I${includedir}/tss
Libs: -ltss2-esys -L${libdir}
Libs.private: -ldl   -lcrypto

The Cflags field includes /usr/include/tss, but the include files are actually
in /usr/include/tss2.

This causes build failures like this in fwupd:

cc -Iplugins/tpm-eventlog/libfu_plugin_tpm_eventlog.so.p -Iplugins/tpm-eventlog 
-I../plugins/tpm-eventlog -I. -I.. -Ilibfwupd -I../libfwupd -Ilibfwupdplugin 
-I../libfwupdplugin -I/usr/include/libxmlb-1 -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/gusb-1 -I/usr/include/libusb-1.0 -I/usr/include/libsoup-2.4 
-I/usr/include/libxml2 -I/usr/include/gudev-1.0 -I/usr/include/json-glib-1.0 
-I/usr/include/tss -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 
-Werror -std=c99 -Waggregate-return -Wunused -Warray-bounds -Wcast-align 
-Wclobbered -Wdeclaration-after-statement -Wdiscarded-qualifiers 
-Wduplicated-branches -Wduplicated-cond -Wempty-body -Wformat=2 
-Wformat-nonliteral -Wformat-security -Wformat-signedness -Wignored-qualifiers 
-Wimplicit-function-declaration -Winit-self -Wlogical-op -Wmaybe-uninitialized 
-Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs 
-Wmissing-noreturn -Wmissing-parameter-type -Wmissing-prototypes 
-Wnested-externs -Wno-cast-function-type -Wno-address-of-packed-member 
-Wno-unknown-pragmas -Wno-deprecated-declarations 
-Wno-missing-field-initializers -Wno-strict-aliasing 
-Wno-suggest-attribute=format -Wno-unused-parameter -Wold-style-definition 
-Woverride-init -Wpointer-arith -Wredundant-decls -Wreturn-type -Wshadow 
-Wsign-compare -Wstrict-aliasing -Wstrict-prototypes -Wswitch-default 
-Wtype-limits -Wundef -Wuninitialized -Wunused-but-set-variable 
-Wunused-variable -Wvla -Wwrite-strings -fstack-protector-strong 
-D_DEFAULT_SOURCE -DFWUPD_DISABLE_DEPRECATED -D_BSD_SOURCE -D_XOPEN_SOURCE=700 
-D_GNU_SOURCE -g -O2 -fdebug-prefix-map=/build/build=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
'-DG_LOG_DOMAIN="FuPluginTpmEventlog"' -MD -MQ 
plugins/tpm-eventlog/libfu_plugin_tpm_eventlog.so.p/fu-tpm-eventlog-common.c.o 
-MF 
plugins/tpm-eventlog/libfu_plugin_tpm_eventlog.so.p/fu-tpm-eventlog-common.c.o.d
 -o 
plugins/tpm-eventlog/libfu_plugin_tpm_eventlog.so.p/fu-tpm-eventlog-common.c.o 
-c ../plugins/tpm-eventlog/fu-tpm-eventlog-common.c
cc1: error: /usr/include/tss: No such file or directory 
[-Werror=missing-include-dirs]

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

Kernel: Linux 5.4.58-07649-ge120df5deade (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libtss2-dev depends on:
ii  libgcrypt20-dev  1.8.6-2
ii  libtss2-esys03.0.0-1

libtss2-dev recommends no packages.

libtss2-dev suggests no packages.

-- no debconf information

Bug#971892: linux: Please enable modules for HDMI audio

[Diederik de Haas]

On Fri, 9 Oct 2020 08:39:48 +0200 harr...@gmx.ph wrote:
> Please could you enable these modules:
> 
> CONFIG_SND_SUN4I_I2S=m   ("Allwinner A10 I2S Support")
> CONFIG_DRM_DW_HDMI_I2S_AUDIO=m   ("Synopsys Designware I2S Audio interface")

They are enabled in the 5.9.0-1-arm64 kernel, but noticed that you're using 
armhf. Can you check whether it's also enabled in 'your' kernel and if so, 
close this bug?

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

Bug#973266: ITP: python-moreorless -- wrapper for Python difflib with enhanced "No newline at eof" support

[Nicholas D Steeves]

Package: wnpp
Severity: wishlist
Owner: Nicholas D Steeves 
Control: block 941054 by -1

* Package name: python-moreorless
  Version : 0.3.0
  Upstream Author : Tim Hatch 
* URL : https://github.com/thatch/moreorless
* License : Expat
  Programming Lang: Python
  Description : wrapper for Python difflib with enhanced "No newline at 
eof" support

Moreorless is a thin wrapper around Python's difflib.unified_diff that
Does The Right Thing for "No newline at eof".  The arguments used when
calling moreorless' functions are simpler than difflib's.  Moreorless
also supports various other functions such as
`patch.apply_single_file` and `click.echo_color_unified_diff`.

I am packaging python-moreorless as a dependency of Bowler ≥ 0.9.0,
plan to maintain it on the Python Team, and will need a sponsor for
the initial upload.

Regards,
Nicholas

Bug#973136: delve: FTBFS: dh_auto_test: error

[Shengjing Zhu]

Control: severity -1 important
Control: tags -1 unreproducible

On Wed, Oct 28, 2020 at 1:46 AM Lucas Nussbaum  wrote:
>
> Source: delve
> Version: 1.5.0-4
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201027 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):

The relevant part is near "FAIL:"

=== RUN   TestIssue1374
   proc_test.go:112: failed assertion at proc_test.go:4211: Call -
could not restore registers: bad address
--- FAIL: TestIssue1374 (0.62s)


However as delve was just built by buildd 11hour ago, and on my
desktop. So this seems a corner case triggered by your environment.
Hence I downgrade the severity.

I guess the difference between buildd, my desktop and your env is real
hardware and VM.
Since delve is a debug tool, like gdb, probably the failed tests are
using some extreme methods which are restricted by VM.

-- 
Shengjing Zhu

Bug#953862: imaxima always gives "LaTeX error in:"

[Ilya Ryabinkin]

A preliminary patch is available here:
https://bugs.launchpad.net/ubuntu/+source/maxima/+bug/1877185/comments/4

Testing and improvements are welcome!

--
Ilya

Bug#973094: leiningen-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact commons-io:commons-io:jar:2.6 has not been downloaded from it before.

[Elana Hashman]

Thanks for the report.

Looks like libcommons-io-java has been updated to 2.8.0.[1] We'll need
to patch both the Debian build and send a PR upstream to get it on the
newer version.

- e

[1]: https://packages.debian.org/sid/libcommons-io-java


signature.asc
Description: PGP signature

Bug#962294: marked as done (RFS: btrfs-progs/5.7-1~bpo10+1 -- Checksumming Copy on Write Filesystem utilities)

[Nicholas D Steeves]

"Debian Bug Tracking System"  writes:

> Your message dated Wed, 21 Oct 2020 14:20:47 +0200
> with message-id <4ce39769-f1c3-68ad-3965-688d1f6c0...@debian.org>
> and subject line Re: Bug#962294: RFS: btrfs-progs/5.7-1~bpo10+1 -- 
> Checksumming Copy on Write Filesystem utilities
> has caused the Debian Bug report #962294,
> regarding RFS: btrfs-progs/5.7-1~bpo10+1 -- Checksumming Copy on Write 
> Filesystem utilities
> to be marked as done.
>

Thank you Gianfranco, much appreciated!  A number of our users on
upstream linux-btrfs have been recommended Fedora live media as the
easiest way to get a recent version of 'btrfs check' (fsck equivalent
for fs structures and metadata), so it's good to have an in-house
solution again.

Best,
Nicholas


signature.asc
Description: PGP signature

Bug#973265: pulseaudio: linux-image-4.19.0-12-amd64: load-module initialization failed

[Allan Wind]

Package: pulseaudio
Version: 12.2-4+deb10u1
Severity: important

Dear Maintainer,

It appears that when I upgraded from linux-image-4.19.0-10-amd64 to 
either 11 or 12 the customizations in default.pa fail to load (I 
need those to be able switch between headphone and speaker output, 
using a profile for this doesn't work for mono audio):


2020-10-27T06:26:23.198+00:00 vent pulseaudio[1494]: W: [alsa-sink-USB Audio] 
asyncq.c: q overrun, queuing locally
2020-10-27T06:26:23.198+00:00 vent pulseaudio[1494]: W: [alsa-sink-USB Audio] 
asyncq.c: q overrun, queuing locally
2020-10-27T06:29:02.199+00:00 vent systemd[1046]: pulseaudio.service: Succeeded.
2020-10-27T06:29:05.948+00:00 vent pulseaudio[1171]: E: [pulseaudio] module.c: Failed to load module "module-alsa-source" (argument: "device=hw:Pro70793162 name=raw_input source_name=raw_input channels=2 
channel_map=front-left,front-right"): initialization failed.

2020-10-27T06:29:05.948+00:00 vent pulseaudio[1171]: E: [pulseaudio] module.c: Failed to load 
module "module-alsa-sink" (argument: "device=hw:Pro70793162 name=raw sink_name=raw 
channels=12 channel_map=aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7,aux8,aux9,aux10,aux11"): 
initialization failed.
2020-10-27T06:29:05.948+00:00 vent pulseaudio[1171]: E: [pulseaudio] module-remap-sink.c: Master 
sink not found 2020-10-27T06:29:05.948+00:00 vent pulseaudio[1171]: E: [pulseaudio] module.c: 
Failed to load module "module-remap-sink" (argument: 
"sink_properties=device.description=Headphone sink_name=headphone master=raw channels=2 
master_channel_map=aux2,aux3 channel_map=front-left,front-right remix=no"): initialization 
failed.
2020-10-27T06:29:05.948+00:00 vent pulseaudio[1171]: E: [pulseaudio] module-remap-sink.c: Master sink not found 2020-10-27T06:29:05.948+00:00 vent pulseaudio[1171]: E: [pulseaudio] module.c: Failed to load module "module-remap-sink" (argument: "sink_properties=device.description=Speaker sink_name=speaker master=raw channels=2 master_channel_map=aux0,aux1 channel_map=front-left,front-right 
remix=no"): initialization failed.

2020-10-27T06:48:53.699+00:00 vent pulseaudio[1171]: W: [alsa-sink-USB Audio] 
alsa-util.c: Got POLLNVAL from ALSA 2020-10-27T06:48:53.699+00:00 vent 
pulseaudio[1171]: W: [alsa-sink-USB Audio] alsa-util.c: Could not recover from 
POLLERR|POLLNVAL|POLLHUP with snd_pcm_prepare(): No such device
2020-10-27T06:48:53.699+00:00 vent pulseaudio[1171]: W: [alsa-source-USB Audio] 
alsa-util.c: Got POLLNVAL from ALSA
2020-10-27T06:48:53.699+00:00 vent pulseaudio[1171]: W: [alsa-source-USB Audio] 
alsa-util.c: Could not recover from POLLERR|POLLNVAL|POLLHUP with 
snd_pcm_prepare(): No such device

root@vent:~# cat /proc/asound/cards 
0 [PCH]: HDA-Intel - HDA Intel PCH

 HDA Intel PCH at 0x2ff201 irq 148
1 [NVidia ]: HDA-Intel - HDA NVidia
 HDA NVidia at 0xec00 irq 17
2 [Pro70793162]: USB-Audio - Babyface Pro (70793162)
 RME Babyface Pro (70793162) at usb-:00:14.0-2.4.4.4, 
high speed
3 [Webcam ]: USB-Audio - C922 Pro Stream Webcam
 C922 Pro Stream Webcam at usb-:00:14.0-6, high speed

I get the same unhelpful error message when I load said modules with pactl
manually.  Not sure how to troubleshoot this.  This host runs stable, and
only security upgrades have been applied. I don't see any recent changes
related to pulseaudio so I suspect it's the kernel upgrade. It fails with both
-11 and -12.  I already purged -10, unfortunately, but this was the kernel I
ran when it last worked.


/Allan

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


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

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

Versions of packages pulseaudio depends on:
ii  adduser  3.118
ii  libasound2   1.1.8-1
ii  libasound2-plugins   1.1.8-1
ii  libc62.28-10
ii  libcap2  1:2.25-2
ii  libdbus-1-3  1.12.20-0+deb10u1
ii  libgcc-s1 [libgcc1]  10.1.0-1
ii  libgcc1  1:8.3.0-6
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-9
ii  liborc-0.4-0 1:0.4.28-3.1
ii  libpulse012.2-4+deb10u1
ii  libsm6   2:1.2.3-1
ii  libsndfile1  1.0.28-6
ii  libsoxr0 0.1.2-3
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   10.1.0-1
ii  libsystemd0  

Bug#973264: palisade: too much information given

[Kapil Paranjape]

Package: sgt-puzzles
Version: 20191231.79a5378-3
Severity: normal
X-Debbugs-Cc: kapil.paranj...@gmail.com

Dear Maintainer,

If one compares the puzzles set up by 'sgt-palisade' with those that are
on the main website, one sees that the former gives much more
information than the latter. *All* the squares have numbers in the
former! Even the manual page for 'sgt-palisade' says "You're given a
grid of squares, *some* of which contain numbers." (Emphasis mine.)

As a result the puzzles generated by 'sgt-palisade' are much too easy
to solve!

Please see if the puzzles generated by sgt-palisade can be made to be
similar to those on the website.

Regards,

Kapil.
--

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable')
Architecture: armhf (armv7l)

Kernel: Linux 4.19.151-10433-g001cdf76f178 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages sgt-puzzles depends on:
ii  libc62.31-4
ii  libcairo21.16.0-4
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-5
ii  libglib2.0-0 2.66.1-2
ii  libgtk-3-0   3.24.23-2
ii  libpango-1.0-0   1.46.2-1
ii  libpangocairo-1.0-0  1.46.2-1

Versions of packages sgt-puzzles recommends:
ii  firefox-esr [www-browser]  78.4.0esr-1~deb10u2
ii  w3m [www-browser]  0.5.3-38+b1
ii  xdg-utils  1.1.3-2

sgt-puzzles suggests no packages.

-- no debconf information

Bug#973255: arm-trusted-firmware: please enable amlogic g12a support

[Reco]

Source: arm-trusted-firmware
Severity: wishlist

Dear Maintainer,

I happen to have an Odroid N2 (amlogic g12a board) and would like to see
a proper Debian installed on it. Aside from the other things, it's my
understanding that certain changes are required for arm-trusted-firmware
sign already built u-boot for amlogic/g12a.

I beleive we've discussed this issue at debian-arm, [1].

Sincerely yours, Reco

[1] https://lists.debian.org/msgid-search/87v9evu2yt.fsf@yucca


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

Kernel: Linux 4.9.0-18-arm64 (SMP w/6 CPU cores; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Bug#973256: u-boot: Please enable amlogic_g12a support

[Reco]

Source: u-boot
Version: 2019.01+dfsg-7
Severity: wishlist

Dear Maintainer,

I happen to have an Odroid N2 (amlogic g12a board) and would like to see
a proper Debian installed on it. Aside from the other things, it's my
understanding that specially built u-boot is required for it, and
u-boot-amlogic in its current form is unsuitable for the task.

I beleive we've discussed this issue at debian-arm, [1].

Sincerely yours, Reco

[1] https://lists.debian.org/msgid-search/87v9evu2yt.fsf@yucca

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

Kernel: Linux 4.9.0-18-arm64 (SMP w/6 CPU cores; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Bug#973252: linux-image-5.9.0-1-amd64: microphone device is missing on Thinkpad T14 Gen1 AMD due to disabled kernel options

[feuerrot]

Package: src:linux
Version: 5.9.1-1
Severity: normal
X-Debbugs-Cc: debian-bugrep...@feuerrot.org

Dear Maintainer,

I'd like to use my devices microphone without having to build my own kernel, 
which I can't as it requires the following kernel options to be enabled:
> CONFIG_SND_SOC_AMD_ACP3x=m
> CONFIG_SND_SOC_AMD_RENOIR=m
> CONFIG_SND_SOC_AMD_RENOIR_MACH=m

Currently these options are disabled in the kernel configuration:
< # CONFIG_SND_SOC_AMD_ACP3x is not set
< # CONFIG_SND_SOC_AMD_RENOIR is not set

I verified that these options are the only missing ones by building two kernels 
using /boot/config-5.9.0-1-amd64 from linux-image-5.9.0-1-amd64 - the first one 
without any changes, the second one with the options enabled.


-- Package-specific info:
** Version:
Linux version 5.9.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.0-15) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 
5.9.1-1 (2020-10-17)

** Command line:
BOOT_IMAGE=/vmlinuz-5.9.0-1-amd64 root=/dev/mapper/vg_root-lv_root ro 
net.ifnames=0

** Tainted: OE (12288)
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
[   39.227146] EDAC amd64: Node 0: DRAM ECC disabled.
[   39.323897] EDAC amd64: F17h_M60h detected (node 0).
[   39.323950] EDAC amd64: Node 0: DRAM ECC disabled.
[   39.334180] iwlwifi :03:00.0: base HW address: a8:7e:ea:06:2d:27
[   39.355045] r8169 :05:00.0 eth0: Link is Down
[   39.355652] thermal thermal_zone0: failed to read out thermal zone (-61)
[   39.408297] EDAC amd64: F17h_M60h detected (node 0).
[   39.408364] EDAC amd64: Node 0: DRAM ECC disabled.
[   39.408508] input: ACPI Virtual Keyboard Device as 
/devices/virtual/input/input17
[   39.508187] EDAC amd64: F17h_M60h detected (node 0).
[   39.508265] EDAC amd64: Node 0: DRAM ECC disabled.
[   39.612632] EDAC amd64: F17h_M60h detected (node 0).
[   39.612713] EDAC amd64: Node 0: DRAM ECC disabled.
[   39.723630] EDAC amd64: F17h_M60h detected (node 0).
[   39.725802] EDAC amd64: Node 0: DRAM ECC disabled.
[   39.872221] EDAC amd64: F17h_M60h detected (node 0).
[   39.872296] EDAC amd64: Node 0: DRAM ECC disabled.
[   39.894772] mc: Linux media interface: v0.10
[   39.896824] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[   39.924214] videodev: Linux video capture interface: v2.00
[   39.998784] ucsi_acpi: probe of USBC000:00 failed with error -5
[   40.016185] EDAC amd64: F17h_M60h detected (node 0).
[   40.018272] EDAC amd64: Node 0: DRAM ECC disabled.
[   40.042904] Bluetooth: Core ver 2.22
[   40.043722] NET: Registered protocol family 31
[   40.044468] Bluetooth: HCI device and connection manager initialized
[   40.045224] Bluetooth: HCI socket layer initialized
[   40.045926] Bluetooth: L2CAP socket layer initialized
[   40.046616] Bluetooth: SCO socket layer initialized
[   40.070900] usb usb2: root hub lost power or was reset
[   40.073189] usb usb3: root hub lost power or was reset
[   40.075382] xhci_hcd :06:00.0: Zeroing 64bit base registers, expecting 
fault
[   40.152089] EDAC amd64: F17h_M60h detected (node 0).
[   40.153971] EDAC amd64: Node 0: DRAM ECC disabled.
[   40.197288] usbcore: registered new interface driver btusb
[   40.201013] Bluetooth: hci0: Firmware revision 0.0 build 121 week 36 2020
[   40.264467] EDAC amd64: F17h_M60h detected (node 0).
[   40.264473] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   40.266095] EDAC amd64: Node 0: DRAM ECC disabled.
[   40.267960] Bluetooth: BNEP filters: protocol multicast
[   40.271535] Bluetooth: BNEP socket layer initialized
[   40.368579] NET: Registered protocol family 38
[   40.368974] EDAC amd64: F17h_M60h detected (node 0).
[   40.369028] EDAC amd64: Node 0: DRAM ECC disabled.
[   40.455214] usb 2-2: reset high-speed USB device number 2 using xhci_hcd
[   40.471214] EDAC amd64: F17h_M60h detected (node 0).
[   40.471273] EDAC amd64: Node 0: DRAM ECC disabled.
[   40.474964] bridge: filtering via arp/ip/ip6tables is no longer available by 
default. Update your scripts to load br_netfilter if you need this.
[   40.484476] tun: Universal TUN/TAP device driver, 1.6
[   40.485377] virbr2: port 1(virbr2-nic) entered blocking state
[   40.485383] virbr2: port 1(virbr2-nic) entered disabled state
[   40.485474] device virbr2-nic entered promiscuous mode
[   40.552112] EDAC amd64: F17h_M60h detected (node 0).
[   40.552179] EDAC amd64: Node 0: DRAM ECC disabled.
[   40.613452] EDAC amd64: F17h_M60h detected (node 0).
[   40.613516] EDAC amd64: Node 0: DRAM ECC disabled.
[   40.618635] uvcvideo: Found UVC 1.10 device Integrated Camera (04f2:b6d0)
[   40.625107] uvcvideo 2-2:1.0: Entity type for entity Microsoft Extended 
Controls Uni was not initialized!
[   40.625114] uvcvideo 2-2:1.0: Entity type for entity Realtek Extended 
Controls Unit was not initialized!
[   40.625117] uvcvideo 2-2:1.0: Entity type for entity Extension 4 was not 
initialized!
[   40.625120] uvcvideo 2-2:1.0: Entity type for entity 

Bug#972898: hplip: no network scanner detection with 3.20.9

[Ahzo]

Oct 26, 2020, 14:58 by claremont...@gmail.com:

> Thank you for your report, Ahzo. I have forwarded it upstream. Please
> review what I have written and correct or add to it as you see fit.
>

Thanks for forwarding the report, as Lauchpad still doesn't work for me.
Your summary in the upstream report covers the main aspects of the problem.

Regards,
Ahzo

Bug#972200: Thunderbird Collects Data

[Flavio Veloso Soares]

Or uncheck the box "Allow Thunderbird to send technical and interaction
data to Mozilla" within the Edit - Preferences - Privacy & Security menu.


Shouldn't this be the default?

I was shockingly surprised to see this enabled after TB upgraded. If 
memory serves me, telemetry is always off by default in previous version 
of TB (and Firefox) shipped by Debian.


There are people in sensitive settings (i.e. government, highly 
regulated business) that simply cannot have ANY telemetry in their 
software, and they might be relying on Debian to provide this assurance 
as it had been done historically. Simply stating "just uncheck that 
option" to someone that has to manage thousands of machine doesn't sound 
right to me.


--
FVS

Bug#973170: node-formidable: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Xavier]

Control: reassign -1 node-fetch
Control: affects -1 node-formidable

Le 27/10/2020 à 18:07, Lucas Nussbaum a écrit :
> Source: node-formidable
> Version: 1.2.1+20200129git8231ea6-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201027 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Test works fine using node-fetch installed using npm (same version but
code differs).

Bug#973081: [Pkg-javascript-devel] Bug#973081: pdf.js: FTBFS: [12:18:32] TypeError: Cannot read property 'then' of undefined

[Xavier]

Control: reassign -1 webpack
Control: affects -1 src:pdf.js

Le 27/10/2020 à 18:09, Lucas Nussbaum a écrit :
> Source: pdf.js
> Version: 2.6.347+dfsg-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201027 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
>> make[1]: Entering directory '/<>'
>> gulp dist-pre
>> [12:18:24] Local gulp not found in /<>
>> [12:18:24] Try running: npm install gulp
>> [12:18:24] Using globally installed gulp
>> [12:18:24] Using gulpfile /<>/gulpfile.js
>> [12:18:24] Starting 'dist-pre'...
>> [12:18:24] Starting 'generic'...
>> [12:18:24] Starting 'buildnumber'...
>>
>> ### Getting extension build number
>> This is not a Git repository; using default build number.
>> Extension build number: 0
>> [12:18:24] Finished 'buildnumber' after 26 ms
>> [12:18:24] Starting 'default_preferences'...
>> [12:18:24] Starting 'default_preferences-pre'...
>>
>> ### Building `default_preferences.json`
>> Since Acorn 8.0.0, options.ecmaVersion is required.
>> Defaulting to 2020, but this will stop working in the future.
>> [12:18:25] Finished 'default_preferences-pre' after 425 ms
>> [12:18:25] Starting ''...
>> [12:18:25] Finished '' after 3.36 ms
>> [12:18:25] Finished 'default_preferences' after 429 ms
>> [12:18:25] Starting 'locale'...
>>
>> ### Building localization files
>> [12:18:25] Finished 'locale' after 145 ms
>> [12:18:25] Starting ''...
>>
>> ### Creating generic viewer
>> (node:27451) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
>> security and usability issues. Please use the Buffer.alloc(), 
>> Buffer.allocUnsafe(), or Buffer.from() methods instead.
>> [12:18:32] '' errored after 7.53 s
>> [12:18:32] TypeError: Cannot read property 'then' of undefined
>> at /usr/share/nodejs/webpack/lib/Compiler.js:493:44
> failed build was retried once to eliminate random failures.

Problem comes from mkdirp-1 patch

Bug#962459: unbound: constantly crashing after about 3 minutes since start

[Daniel Kahn Gillmor]

Control: forcemerge 973052 962459 

Hi Kebert--

On Mon 2020-06-08 12:28:46 +0200, Kebert Martin wrote:
> unbound constantly crashing with:
> [err] evmap.c:381: Assertion nread >= 0 failed in evmap_io_del_
>
> The issue is fixed in unbound 1.9.2 but this version is not available in 
> debian packages.
>
> As a workaround I had unbound from testing but it is not possible now,
> because currect testing version 1.10.1-1 relies on libpython3.8 which
> relies on libc6 >= 2.29 whereas stable libc6 is 2.28-10.

Thanks for this note!  sorry i missed it when reporting 973052, but it
looks like it's the same issue.  Would you be up for trying a version of
unbound that includes the patch from 973052 and letting me know whether
the crash is still happening?

I haven't seen "consistent" failures with the workload where i
encountered the bug, so it'd be great to hear whether the patch solves
the problem for you if you've got a repeatable workload.

If you don't know how to rebuild the package with the extra patch,
please respond here and maybe one of the debian packagers who is used to
working with unbound can offer a proposed update.

Regards,

--dkg


signature.asc
Description: PGP signature

Bug#973263: linux-image-5.9.0-1-amd64: 5.9.0-1 (5.9.1+1) hangs on shutdown or poweroff

[Jonathan Rubenstein]

Package: src:linux
Version: 5.9.1-1
Severity: important
X-Debbugs-Cc: jrub...@gmail.com

This kernel works mostly OK, but on my system, attempting to power off 
the system will hang after killing some programs, and it takes an 
extensively long time to kill the programs. Forcing reboot by pressing 
CTRL+ALT+DEL 7 times quickly does function to reboot the system.


As a side note, this kernel also interferes with libvirt, and I cannot 
connect to the qemu:///system daemon through any client (virsh or 
virt-manager)


Reverting to kernel 5.8.0-3 (5.8.14-1) resolves all of these issues.

I hesitated to mark this as grave as nobody else is reporting these 
kinds of issues. I believe it may have to do with my specific 
configuration, but I am not sure. Let me know if you need further details.


-- Package-specific info:
** Version:
Linux version 5.9.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-10 
(Debian 10.2.0-15) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 
SMP Debian 5.9.1-1 (2020-10-17)


** Command line:
BOOT_IMAGE=/vmlinuz-5.9.0-1-amd64 
root=/dev/mapper/Da--jonnys--box--of--fun--vg-root ro quiet splash 
amd_iommu=on iommu=pt
# as you can see I have some kernel flags for GPU passthrough and use 
plymouth


** Tainted: D (128)
 * kernel died recently, i.e. there was an OOPS or BUG

** Kernel log:
[8.477172] EDAC amd64: Node 0: DRAM ECC disabled.
[8.576844] EDAC amd64: F17h detected (node 0).
[8.576892] EDAC amd64: Node 0: DRAM ECC disabled.
[8.660615] EDAC amd64: F17h detected (node 0).
[8.660651] EDAC amd64: Node 0: DRAM ECC disabled.
[8.764529] EDAC amd64: F17h detected (node 0).
[8.764569] EDAC amd64: Node 0: DRAM ECC disabled.
[8.852753] EDAC amd64: F17h detected (node 0).
[8.852812] EDAC amd64: Node 0: DRAM ECC disabled.
[8.948905] EDAC amd64: F17h detected (node 0).
[8.948964] EDAC amd64: Node 0: DRAM ECC disabled.
[9.040574] EDAC amd64: F17h detected (node 0).
[9.040635] EDAC amd64: Node 0: DRAM ECC disabled.
[9.579274] r8169 :21:00.0: firmware: direct-loading firmware 
rtl_nic/rtl8168h-2.fw
[9.604059] Generic FE-GE Realtek PHY r8169-2100:00: attached PHY 
driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-2100:00, 
irq=IGNORE)

[9.812294] r8169 :21:00.0 enp33s0: Link is Down
[9.970411] amdgpu :26:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=io+mem
[9.970415] vfio-pci :27:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=none
[   11.413590] BUG: kernel NULL pointer dereference, address: 
0298

[   11.413594] #PF: supervisor read access in kernel mode
[   11.413595] #PF: error_code(0x) - not-present page
[   11.413596] PGD 0 P4D 0 [   11.413598] Oops:  [#1] SMP NOPTI
[   11.413601] CPU: 0 PID: 1191 Comm: daemon-init Not tainted 
5.9.0-1-amd64 #1 Debian 5.9.1-1
[   11.413602] Hardware name: Micro-Star International Co., Ltd. 
MS-7A33/X370 GAMING PLUS (MS-7A33), BIOS 5.H0 01/22/2019

[   11.413621] RIP: 0010:kvm_register_read+0xe/0x40 [kvm]
[   11.413624] Code: 00 f0 ff 87 b0 1b 00 00 f0 80 4f 3a 02 c3 66 66 2e 
0f 1f 84 00 00 00 00 00 0f 1f 00 83 fe 10 77 2d 55 89 f0 48 89 fd 53 89 
f3 <48> 0f a3 87 98 02 00 00 72 0c 48 8b 05 81 2f 08 00 e8 3c a1 62 c8

[   11.413625] RSP: 0018:a62ec14f3e18 EFLAGS: 00010246
[   11.413627] RAX: 0010 RBX: 0010 RCX: 
fffee635
[   11.413628] RDX: 0001 RSI: 0010 RDI: 

[   11.413629] RBP:  R08: c122599c R09: 
0010
[   11.413630] R10:  R11: 0021 R12: 
048b
[   11.413631] R13:  R14: 7fb111ffa458 R15: 

[   11.413632] FS:  7fb111ffb700() GS:96c8eec0() 
knlGS:

[   11.413634] CS:  0010 DS:  ES:  CR0: 80050033
[   11.413635] CR2: 0298 CR3: 0003ff8a8000 CR4: 
003506f0

[   11.413636] Call Trace:
[   11.413654]  kvm_msr_ignored_check+0x9e/0x100 [kvm]
[   11.413670]  do_get_msr_feature+0xa5/0xb0 [kvm]
[   11.413686]  ? kvm_msr_ignored_check+0x100/0x100 [kvm]
[   11.413702]  msr_io+0xaf/0x140 [kvm]
[   11.413719]  kvm_arch_dev_ioctl+0x5b/0x2f0 [kvm]
[   11.413723]  __x64_sys_ioctl+0x83/0xb0
[   11.413726]  do_syscall_64+0x33/0x80
[   11.413729]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   11.413731] RIP: 0033:0x7fb13de74c27
[   11.413733] Code: 00 00 00 48 8b 05 69 92 0c 00 64 c7 00 26 00 00 00 
48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 
05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 39 92 0c 00 f7 d8 64 89 01 48
[   11.413734] RSP: 002b:7fb111ffa438 EFLAGS: 0246 ORIG_RAX: 
0010
[   11.413736] RAX: ffda RBX: 7fb111ffa4c0 RCX: 
7fb13de74c27
[   11.413737] RDX: 7fb111ffa450 RSI: c008ae88 RDI: 
0021
[   11.413738] RBP: 7fb111ffa490 R08:  

Bug#973024: feature-check's autopkg tests are failing, blocking python3-defaults

[Peter Pentchev]

On Tue, Oct 27, 2020 at 01:05:32PM +0100, Matthias Klose wrote:
> Package: src:feature-check
> Version: 0.2.2-5
> Severity: serious
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: python3.9

This is the same as #972530, which was already fixed in 0.2.2-6 on
Monday, however the CI system has not run the tests yet.

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Bug#971515: Request for security team input on kubernetes TC bug

[Dmitry Smirnov]

On Wednesday, 28 October 2020 6:13:41 AM AEDT Moritz Mühlenhoff wrote:
> The bigger issue here (independent of the whole vendoring aspect) is
> how kubernetes can be supported in a stable release to begin with.
> This was raised by Shengjing Zhu in #959685 before.

If Kubernetes can be supported then such support will be done by upstream,
but with extraordinary amount of dependencies (and upstream reluctance to 
manage them), I have very low confidence and low expectations for quality
of such support. The problem primarily is that Kubernetes vendors hundreds
of dependencies representing a large support surface. Effectively it is
"#include world" (or vendor world) situation. And when it comes to problems
in 3rd party vendored libraries, it iw worth remembering that Kubernetes 
don't own them.


> This leaves Debian with two options:
> * Keep it out of a stable release and accept that it's good enough
>   if people just install whatever deb they currently find in testing/sid
>   (works out well enough for most given that blob nature of Go!)

IMHO this is the most reasonable option and perhaps the only viable one.


> * Follow a scheme similar to Firefox ESR where in case of a security
>   the update either happens to the latest minor release of
>   the current branch or if that has stopped, happens to the next
>   major release.

I think Kubernetes have many more vendored 3rd party libraries than Firefox.
IMHO we can not expect the same level of confidence for Kubernetes...

-- 
Best wishes,
 Dmitry Smirnov
 GPG key : 4096R/52B6BBD953968D1B

---

You have to start with the truth. The truth is the only way that we can
get anywhere. Because any decision-making that is based upon lies or
ignorance can't lead to a good conclusion.
-- Julian Assange, 2010


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

Bug#973062: Really an issue in cloud-init?

[Thomas Goirand]

Hi,

To me it looks like an issue in python-httpretty. I'll try to fix
httpretty and rebuild cloud-init, then probably close this bug.

Cheers,

Thomas Goirand (zigo)

Bug#972992: j4-dmenu-desktop: dmenu and i3-sensible-terminal missing

[Thierry B.]

For the second error, I missed the "--term=" option to chnage the
default terminal, so the issue is only :

running "j4-dmenu-desktop", "dmenu" is missing. So "suckless-tools"
should be a dependency

Bug#973227: dh-cmake: FTBFS: AttributeError: 'Changelog' object has no attribute 'get_version'

[Kyle Edwards]

Thanks. Looks like I was accidentally using an undocumented method from 
python3-debian that got renamed. I have a working and fix and will ask 
my sponsor to upload it.

Bug#969372: uwsgi-emperor: SysV init script does nothing

[Thomas Goirand]

Hi,

Vlastimil, did you actually try to put some ini file in the relevant
folder, ie: /etc/uwsgi-emperor/vassals/ ? How did you test to tell that
it didn't work?

Cheers,

Thomas Goirand (zigo)

Bug#973262: shared-mime-info package post-installation script subprocess returned error exit status 127 on mipsel platform

[James Lin]

Package: shared-mime-info
Version: 1.10-1

Installation failed for package shared-mime-info with below message:

Setting up shared-mime-info (1.10-1) ...
update-mime-database: symbol lookup error: 
/usr/lib/mipsel-linux-gnu/libicui18n.so.63: undefined symbol: 
u_caseInsensitivePrefixMatch_63
dpkg: error processing package shared-mime-info (--configure):
installed shared-mime-info package post-installation script subprocess returned 
error exit status 127
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-10) ...
Errors were encountered while processing:
shared-mime-info
E: Sub-process /usr/bin/dpkg returned an error code (1)

Below are versions for libicu package installed:

root@gnubee:~# apt-cache show libicu63
Package: libicu63
Source: icu
Version: 63.1-6+deb10u1
Installed-Size: 32264
Maintainer: Laszlo Boszormenyi (GCS) 
Architecture: mipsel

I’m on Debian buster 10.6. Found the issue while trying to install minidlna 
package.

Bug#959407: dh-python: pybuild without setup.py

[Nicholas D Steeves]

Hi Scott,

Scott Kitterman  writes:

> On May 2, 2020 4:17:20 AM UTC, Drew Parsons  wrote:
>>> pybuild will want to support it
>>
>>Some discussion has started on the mailing list,
>>
>>https://lists.debian.org/debian-python/2020/04/msg00061.html
>
> As mentioned in the thread, there's a pybuild plugin for packages that use 
> flit to build based on pyproject.toml.  It's in git, staged for the next 
> upload.  The pep517 package can also build packages using pyproject.toml, but 
> it isn't, IMO, suitable for integration with pybuild because it's to heavy 
> weight.
>

I've been thinking of the approach of using something like Dephell to
convert from any of these:
  https://dephell.readthedocs.io/cmd-deps-convert.html

to setup.py.  Assuming pyproject.toml becomes a widely adopted standard,
the future benefit for this package would become for Debianising
packages using less popular formats.

I'm not familiar with pep517, but Dephell (ITP #962574) also seems too
heavy weight for core usage like dh_python.  Increasingly upstreams
don't provide setup.py in their git repos, and PyPI releases often don't
have everything that is required to run autopkgtests, and I was forced
to choose the PyPI release with no autopkgtests.

While searching for info on if pep517 could be used to convert to
setup.py, I found pyproject2setuppy:
  
https://blogs.gentoo.org/mgorny/2019/12/24/handling-pep-517-pyproject-toml-packages-in-gentoo/

Something like this strikes me as a something that might meet our needs,
and it seems like a good opportunity for inter-distro collaboration!

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#973048: ardentryst: Missing dependency on python3-future

[Markus Koschany]

Control: tags -1 pending

Hi,

Am 27.10.20 um 16:30 schrieb Patrick Häcker:
> Package: ardentryst
> Version: 1.71-7
> Severity: normal
> 
> Dear Maintainer,
> 
> I cannot start ardentryst any more:
> 
> pat@mmm ~> cd /usr/share/games/ardentryst
>/usr/bin/python3 /usr/share/games/ardentryst/ardentryst.py
> pygame 1.9.6
> Hello from the pygame community. https://www.pygame.org/contribute.html
> Traceback (most recent call last):
>   File "/usr/share/games/ardentryst/ardentryst.py", line 26, in 
> from past.builtins import cmp
> ModuleNotFoundError: No module named 'past'
> 
> Installing the package python3-future fixes it. So ardentryst should depend
> on python3-future.

True. Thanks for reporting. This one will be fixed shortly.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#973261: libhdf5-openmpi-dev: installing requires /proc being mounted

[Johannes 'josch' Schauer]

Package: libhdf5-openmpi-dev
Version: 1.10.6+repack-2
Severity: wishlist

Hi,

when installing libhdf5-openmpi-dev in a chroot that doesn't have /proc
mounted, one will get the following error:

Setting up libhdf5-openmpi-dev (1.10.6+repack-2) ...
/var/lib/dpkg/info/libhdf5-openmpi-dev.postinst: line 56: /dev/fd/63: No such 
file or directory
dpkg: error processing package libhdf5-openmpi-dev (--configure):
 installed libhdf5-openmpi-dev package post-installation script subprocess 
returned error exit status 1

The problem is, that the postinst script uses the bash-feature to write:

while read x; do ... done < <(cmd2 args ...)

Fortunately, these instances can easily be rewritten as:

cmd2 args | while read x; do ... done

Please consider making this change.

Thanks!

cheers, josch

Bug#892052: Please add support for the flit build system

[Louis-Philippe Véronneau]

Scott (in CC) wrote a flit plugin for pybuild. Can this be closed?

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄



signature.asc
Description: OpenPGP digital signature

Bug#973190: geneweb: FTBFS: ocamlc.opt: OCaml has been configured with -force-safe-string: -unsafe-string is not available.

[Guillaume Brochu]

Dear Lucas,


Thank you for the report!

This is most likely related to the recent migration to OCAML 4.11 in
unstable:
[2020-10-12] Accepted ocaml 4.11.1-3 (source) into unstable

And I think I know what to do to fix it. See the commit messages in :

https://salsa.debian.org/GuillaumeBrochu-guest/geneweb/-/blob/master/debian/patches/0001-Makefile.debian.patch

https://github.com/geneweb/geneweb/commit/5fe0e0bccb33befd56471dd40eaf44ead2f6fb8a

I will try to fix this as soon as possible.

With best regards,


Guillaume

Le mar. 27 oct. 2020 à 13:51, Lucas Nussbaum  a écrit :

> Source: geneweb
> Version: 6.08+git20181019+dfsg-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201027 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > make[3]: Entering directory '/<>/wserver'
> > camlp5r pa_extend.cmo q_MLast.cmo -o pa_macro5.ppo pa_macro5.ml
> > ocamlc -c -I "`camlp5 -where`" -impl pa_macro5.ppo
> > camlp5r ../wserver/pa_macro5.cmo -DUNIX -o wserver.ppi wserver.mli
> > ocamlc.opt -unsafe-string  -I /usr/lib/ocaml/camlp5/ -c -intf wserver.ppi
> > ocamlc.opt: OCaml has been configured with -force-safe-string:
> -unsafe-string is not available.
>


> [...]
>


> The full build log is available from:
>
> http://qa-logs.debian.net/2020/10/27/geneweb_6.08+git20181019+dfsg-2_unstable.log
>
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.
>

Bug#957814: sma: diff for NMU version 1.4-3.1

[Sudip Mukherjee]

Control: tags 957814 + patch
Control: tags 957814 + pending
--

Dear maintainer,

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

--
Regards
Sudip

diff -Nru sma-1.4/debian/changelog sma-1.4/debian/changelog
--- sma-1.4/debian/changelog2014-05-26 02:48:38.0 +0100
+++ sma-1.4/debian/changelog2020-10-27 22:25:23.0 +
@@ -1,3 +1,10 @@
+sma (1.4-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957814)
+
+ -- Sudip Mukherjee   Tue, 27 Oct 2020 22:25:23 
+
+
 sma (1.4-3) unstable; urgency=low
 
   * debian/control: bumped Standards-Version (no changes)
diff -Nru sma-1.4/debian/patches/fix_gcc-10.patch 
sma-1.4/debian/patches/fix_gcc-10.patch
--- sma-1.4/debian/patches/fix_gcc-10.patch 1970-01-01 01:00:00.0 
+0100
+++ sma-1.4/debian/patches/fix_gcc-10.patch 2020-10-27 22:24:49.0 
+
@@ -0,0 +1,19 @@
+Description: Fix ftbfs with GCC-10
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/957814
+Forwarded: no
+
+---
+
+--- sma-1.4.orig/Makefile
 sma-1.4/Makefile
+@@ -7,7 +7,7 @@ MANDIR = /usr/man/man8
+ 
+ CC= gcc
+ # XPG3 regular expressions (GNU/BSD/SVR4)
+-CFLAGS= -Wall -O -DUSE_REGEXP
++CFLAGS= -Wall -O -DUSE_REGEXP -fcommon
+ # Others
+ #CFLAGS   = -Wall -O
+ 
diff -Nru sma-1.4/debian/patches/series sma-1.4/debian/patches/series
--- sma-1.4/debian/patches/series   2014-05-26 02:36:51.0 +0100
+++ sma-1.4/debian/patches/series   2020-10-27 21:25:49.0 +
@@ -1,3 +1,4 @@
 fhsify
 fix_manpage
 hardening
+fix_gcc-10.patch

Bug#973051: The generic bulseye image is configured without metadata list

[Bastian Blank]

On Tue, Oct 27, 2020 at 04:54:13PM +0100, Thomas Goirand wrote:
> Testing to start the OpenStack image (well, the "genericcloud" image), I
> couldn't login into it, because there isn't any metadata service configured
> in it.

This is incorrect.  The package uses
/lib/systemd/system-generators/cloud-init-generator to generate a
config.  This works in general:

| $ cat /run/cloud-init/cloud.cfg 
| datasource_list: [ Azure, None ]

So, please provide more information.

> After that, it appears that /etc/hosts wasn't configued at all with the
> hostname, therefore, the hostname couldn't be resolved even within the VM
> itself. I'm not sure if this is related or not, however.

Show logs?  /run/cloud-init/cloud-init-generator.log for example.

> IMO, this is of severity grave, because the image is not usable without a
> tweak (ie: impossible to login).

Severities have no real meaning for non-package resources.  And the same
mechanism clearly works on Azure and EC2 without problems, so it would
be only "important".

Bastian

-- 
No one wants war.
-- Kirk, "Errand of Mercy", stardate 3201.7

Bug#973260: apt --mark-auto build-dep hello sets packages as manually installed

[Jochen Sprickerhof]

Package: apt
Version: 2.1.11
Severity: normal

Hi,

doing apt --mark-auto build-dep hello I would expect all newly installed
packages to be marked as automatically installed. Instead I see even
some already installed packages marked manual:

(unstable-amd64-sbuild)root@fenchel:~# apt-mark showmanual
(unstable-amd64-sbuild)root@fenchel:~# apt --mark-auto build-dep hello
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  eatmydata fdisk g++-9 libapt-pkg5.0 libeatmydata1 libfdisk1 libffi6 
libhogweed5 libisl21 libnettle7 libstdc++-9-dev
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
  autoconf automake autopoint autotools-dev bsdextrautils debhelper 
dh-autoreconf dh-strip-nondeterminism dwz file gettext gettext-base groff-base 
intltool-debian libarchive-zip-perl libcroco3 libdebhelper-perl libelf1
  libfile-stripnondeterminism-perl libglib2.0-0 libicu67 libmagic-mgc libmagic1 
libpipeline1 libsigsegv2 libsub-override-perl libtool libuchardet0 libxml2 m4 
man-db po-debconf sensible-utils
0 upgraded, 33 newly installed, 0 to remove and 0 not upgraded.
Need to get 19.6 MB of archives.
After this operation, 71.8 MB of additional disk space will be used.
Do you want to continue? [Y/n]
[..]
(unstable-amd64-sbuild)root@fenchel:~# apt-mark showmanual
build-essential
debhelper

(build-essential was installed before, debhelper get's installed)

Would be great to have it fixed as I often install bulid-deps temporary
for debugging and then need to clean up again.


-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "false";
APT::Install-Suggests "false";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-.*-5\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-.*-5\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^gnumach-.*-5\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-modules-5\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-5\.9\.0-1-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-.*";
APT::VersionedKernelPackages:: "kfreebsd-.*";
APT::VersionedKernelPackages:: "gnumach-.*";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";
APT::AutoRemove "";
APT::AutoRemove::RecommendsImportant "false";
APT::AutoRemove::SuggestsImportant "false";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "0";
APT::Compressor::zstd "";
APT::Compressor::zstd::Name "zstd";
APT::Compressor::zstd::Extension ".zst";
APT::Compressor::zstd::Binary "false";
APT::Compressor::zstd::Cost "60";
APT::Compressor::lz4 "";
APT::Compressor::lz4::Name "lz4";
APT::Compressor::lz4::Extension ".lz4";
APT::Compressor::lz4::Binary "false";
APT::Compressor::lz4::Cost "50";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "100";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-6n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::xz "";
APT::Compressor::xz::Name "xz";
APT::Compressor::xz::Extension ".xz";
APT::Compressor::xz::Binary "xz";
APT::Compressor::xz::Cost "200";
APT::Compressor::xz::CompressArg "";
APT::Compressor::xz::CompressArg:: "-6";
APT::Compressor::xz::UncompressArg "";
APT::Compressor::xz::UncompressArg:: "-d";
APT::Compressor::bzip2 "";
APT::Compressor::bzip2::Name "bzip2";
APT::Compressor::bzip2::Extension ".bz2";
APT::Compressor::bzip2::Binary "bzip2";
APT::Compressor::bzip2::Cost "300";
APT::Compressor::bzip2::CompressArg "";
APT::Compressor::bzip2::CompressArg:: "-6";

Bug#973259: dpkg-scanpackages: local development repos fail due to missing sha512 hashes

[Nicholas D Steeves]

Package: dpkg-dev
Version: 1.20.5
Severity: important

Today while working on the autopkgtests of an ITP of mine I discovered
that apt fails to install packages from the local repo, seemingly
because of missing sha512 hashes.  Whether intentional or not, the
effect seems to be that apt is enforcing sha512, which isn't a bad
thing, hence this bug!

…
The following NEW packages will be installed:
  libexpat1 libpython3-stdlib libpython3.8-minimal libpython3.8-stdlib 
mime-support python3 python3-atomicwrites python3-attr
  python3-importlib-metadata python3-minimal python3-more-itertools 
python3-packaging python3-pkg-resources python3-pluggy
  python3-py python3-pyparsing python3-pytest python3-six python3-volatile 
python3-wcwidth python3-zipp python3.8
  python3.8-minimal
0 upgraded, 23 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/5889 kB of archives.
After this operation, 22.9 MB of additional disk space will be used.
Get:1 file:/usr/src/repo/amd64 ./ python3-volatile 2.1.0-1 [5356 B]
Err:1 file:/usr/src/repo/amd64 ./ python3-volatile 2.1.0-1
  Hash Sum mismatch
  Hashes of expected file:
   - SHA256:1210131215ad632c8eb4d09b0448ce680ca9805aaf4ec9b3b99ee2161537f93c
   - SHA1:fc1517b001fe9361d18a31f0d63daac366f93c8e [weak]
   - MD5Sum:e9c3ec5e3d437c610566fa2d24baee47 [weak]
   - Filesize:5356 [weak]
   - 
SHA512:779d3b466eb7cff946f6efebce7374803ec4afd6631ace49e02073d1da4fa98a4b1449e0e207dff6b32e11f735b29b04298a05632dcc077469ecfc674b0cab5d
  Hashes of received file:
   - 
SHA512:d2330098a34a54fe68a57ef12ce79260bb0eeddea3df251e9e4bbd1588dc0e46904ee89cc9e6bf44d8c0a910caedcc1b9c582066f7402ff264d7dc130d7f79c4
   - SHA256:1210131215ad632c8eb4d09b0448ce680ca9805aaf4ec9b3b99ee2161537f93c
   - SHA1:fc1517b001fe9361d18a31f0d63daac366f93c8e [weak]
   - MD5Sum:e9c3ec5e3d437c610566fa2d24baee47 [weak]
   - Filesize:5356 [weak]
  Last modification reported: Tue, 27 Oct 2020 21:23:22 +
W: Sources disagree on hashes for supposely identical version '2.1.0-1' of 
'python3-volatile:amd64'.
E: Failed to fetch 
file:/usr/src/repo/amd64/../pool/python3-volatile_2.1.0-1_all.deb  Hash Sum 
mismatch
   Hashes of expected file:
- SHA256:1210131215ad632c8eb4d09b0448ce680ca9805aaf4ec9b3b99ee2161537f93c
- SHA1:fc1517b001fe9361d18a31f0d63daac366f93c8e [weak]
- MD5Sum:e9c3ec5e3d437c610566fa2d24baee47 [weak]
- Filesize:5356 [weak]
- 
SHA512:779d3b466eb7cff946f6efebce7374803ec4afd6631ace49e02073d1da4fa98a4b1449e0e207dff6b32e11f735b29b04298a05632dcc077469ecfc674b0cab5d
   Hashes of received file:
- 
SHA512:d2330098a34a54fe68a57ef12ce79260bb0eeddea3df251e9e4bbd1588dc0e46904ee89cc9e6bf44d8c0a910caedcc1b9c582066f7402ff264d7dc130d7f79c4
- SHA256:1210131215ad632c8eb4d09b0448ce680ca9805aaf4ec9b3b99ee2161537f93c
- SHA1:fc1517b001fe9361d18a31f0d63daac366f93c8e [weak]
- MD5Sum:e9c3ec5e3d437c610566fa2d24baee47 [weak]
- Filesize:5356 [weak]
   Last modification reported: Tue, 27 Oct 2020 21:23:22 +
E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?
autopkgtest [18:15:29]: ERROR: testbed failure: apt repeatedly failed to 
download packages


Regards,
Nicholas

Bug#973253: apt: support installing/upgrading package and marking them as automatically installed

[Julian Andres Klode]

On Tue, Oct 27, 2020 at 11:15:47PM +0100, Ansgar wrote:
> Package: apt
> Severity: wishlist
> 
> aptitude allows to install/upgrade packages and mark them as
> automatically installed:
> 
>   aptitude install foo+M
> 
> I find this feature useful when asking to upgrade to a specific version
> of a package, but not wanting to have it marked as manually installed.
> A Cultist of the Cow has asked on IRC to file bugs for this.  Said
> Cultist of the Cow has also indicated that juliank might be pleased by
> this feature as well.

I am the cow bearer and I approve this message.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#973257: kde-spectacle: Spectacle doesn't show all installed video screen recorder

[Vincent-Xavier JUMEL]

Package: kde-spectacle
Version: 20.08.2-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?
   Normal spectacle usage

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   In the included screenshot, VokoScreen and OBS-studio appears
   unavalaible instead of usable.

   https://cloud.thetys-retz.net/index.php/s/k7JwceRm872yb89

   zsh 1040 % dpkg -l | grep obs-stu
   ii  obs-studio
   zsh 1041 % dpkg -l | grep voko   
   ii  vokoscreen-ng

   * What was the outcome of this action?
   * What outcome did you expect instead?

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


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

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

Versions of packages kde-spectacle depends on:
ii  kio5.75.0-1~np1
ii  libc6  2.31-4
ii  libkf5configcore5  5.75.0-1~np1
ii  libkf5configgui5   5.75.0-1~np1
ii  libkf5configwidgets5   5.75.0-1~np1
ii  libkf5coreaddons5  5.75.0-1~np1
ii  libkf5dbusaddons5  5.75.0-1~np1
ii  libkf5globalaccel-bin  5.75.0-1~np1
ii  libkf5globalaccel5 5.75.0-1~np1
ii  libkf5i18n55.75.0-1~np1
ii  libkf5kiocore5 5.75.0-1~np1
ii  libkf5kiowidgets5  5.75.0-1~np1
ii  libkf5kipi32.0.0   4:20.08.2-1~np1
ii  libkf5newstuff55.75.0-1~np1
ii  libkf5notifications5   5.75.0-1~np1
ii  libkf5purpose-bin  5.75.0-1~np1
ii  libkf5purpose5 5.75.0-1~np1
ii  libkf5service-bin  5.75.0-1~np1
ii  libkf5service5 5.75.0-1~np1
ii  libkf5waylandclient5   4:5.75.0-1~np1
ii  libkf5widgetsaddons5   5.75.0-1~np1
ii  libkf5windowsystem55.75.0-1~np1
ii  libkf5xmlgui5  5.75.0-1~np1
ii  libqt5core5a   5.14.2+dfsg-6
ii  libqt5dbus55.14.2+dfsg-6
ii  libqt5gui5 5.14.2+dfsg-6
ii  libqt5printsupport55.14.2+dfsg-6
ii  libqt5widgets5 5.14.2+dfsg-6
ii  libqt5x11extras5   5.14.2-2
ii  libstdc++6 10.2.0-15
ii  libxcb-cursor0 0.1.1-4
ii  libxcb-image0  0.4.0-1+b2
ii  libxcb-util0   0.3.8-3+b2
ii  libxcb-xfixes0 1.14-2
ii  libxcb11.14-2
ii  qdbus-qt5  5.14.2-3

kde-spectacle recommends no packages.

kde-spectacle suggests no packages.

-- no debconf information

-- 
Vincent-Xavier JUMEL Id: https://keybase.io/vincentxavier 
https://blog.thetys-retz.net

Société Libre, Logiciel Libre http://www.april.org/adherer
Parinux, logiciel libre à Paris : http://www.parinux.org

Bug#941197: linux-image-4.19.0-6-686: dmesg has error info:[drm:intel_cpu_fifo ... [i915]] *ERROR* CPU....underrun...

[marc]

Package: src:linux
Followup-For: Bug #941197
X-Debbugs-Cc: m...@gallifrey-blr.fr

Dear Maintainer,

I have the same issue on my laptop : Dell Latitude 7480 with i7 6600U.
Here the dmesg error :
[4.153948] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

-- Package-specific info:
** Version: linux-image-5.9.0-1-amd64/unstable,now 5.9.1-1 amd64  [installé,
automatique]



-- Package-specific info:
** Version:
Linux version 5.9.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.0-15) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 
5.9.1-1 (2020-10-17)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.9.0-1-amd64 
root=UUID=d23b375a-b50f-4aa4-a85f-a807fde4c138 ro quiet

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Dell Inc.
product_name: Latitude 7480
product_version: 
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: 1.14.1
board_vendor: Dell Inc.
board_name: 00F6D3
board_version: A00

** Loaded modules:
ctr
ccm
rfcomm
cmac
algif_hash
algif_skcipher
af_alg
bnep
btusb
btrtl
btbcm
btintel
bluetooth
x86_pkg_temp_thermal
intel_powerclamp
coretemp
jitterentropy_rng
kvm_intel
snd_hda_codec_hdmi
drbg
snd_soc_skl
kvm
irqbypass
snd_soc_hdac_hda
snd_hda_ext_core
snd_soc_sst_ipc
snd_hda_codec_realtek
snd_soc_sst_dsp
snd_soc_acpi_intel_match
aes_generic
ghash_clmulni_intel
snd_soc_acpi
snd_hda_codec_generic
ath10k_pci
snd_soc_core
ath10k_core
snd_compress
ath
dell_rbtn
snd_hda_intel
uvcvideo
mei_wdt
mac80211
snd_intel_dspcfg
dell_laptop
snd_hda_codec
aesni_intel
videobuf2_vmalloc
intel_rapl_msr
videobuf2_memops
ledtrig_audio
crypto_simd
snd_hda_core
rapl
videobuf2_v4l2
snd_hwdep
intel_cstate
videobuf2_common
cryptd
glue_helper
dell_smm_hwmon
snd_pcm
iTCO_wdt
intel_uncore
cfg80211
dell_wmi
ansi_cprng
dell_smbios
dcdbas
videodev
intel_pmc_bxt
snd_timer
iTCO_vendor_support
tpm_crb
intel_wmi_thunderbolt
ecdh_generic
wmi_bmof
dell_wmi_descriptor
snd
mc
ecc
pcspkr
serio_raw
mei_me
watchdog
rfkill
processor_thermal_device
soundcore
sg
libarc4
libaes
mei
intel_xhci_usb_role_switch
roles
joydev
tpm_tis
tpm_tis_core
intel_rapl_common
intel_soc_dts_iosf
intel_pch_thermal
tpm
int3403_thermal
int340x_thermal_zone
rng_core
int3400_thermal
intel_hid
evdev
acpi_pad
ac
acpi_thermal_rel
intel_pmc_core
sparse_keymap
parport_pc
ppdev
lp
parport
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
sd_mod
t10_pi
crc_t10dif
crct10dif_generic
hid_alps
hid_generic
i915
i2c_algo_bit
drm_kms_helper
rtsx_pci_sdmmc
mmc_core
cec
ahci
crct10dif_pclmul
crct10dif_common
libahci
crc32_pclmul
xhci_pci
crc32c_intel
drm
xhci_hcd
rtsx_pci
e1000e
libata
usbcore
ptp
scsi_mod
pps_core
i2c_i801
i2c_smbus
i2c_hid
intel_lpss_pci
usb_common
hid
wmi
battery
intel_lpss_acpi
intel_lpss
video
idma64
button

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th 
Gen Core Processor Host Bridge/DRAM Registers [8086:1904] (rev 08)
Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
Bridge/DRAM Registers [1028:07a0]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD 
Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller])
DeviceName:  Onboard IGD
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:07a0]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08)
Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor 
Thermal Subsystem [1028:07a0]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI])
Subsystem: Dell Sunrise Point-LP USB 3.0 xHCI Controller [1028:07a0]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP 
Thermal subsystem [8086:9d31] (rev 21)

Bug#973254: pacemaker: CVE-2020-25654

[Salvatore Bonaccorso]

Source: pacemaker
Version: 2.0.4-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 2.0.1-5

Hi,

The following vulnerability was published for pacemaker.

CVE-2020-25654[0]:
| ACL restrictions bypass

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-25654
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25654
[1] https://www.openwall.com/lists/oss-security/2020/10/27/1
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1888191

Regards,
Salvatore

Bug#973253: apt: support installing/upgrading package and marking them as automatically installed

[Ansgar]

Package: apt
Severity: wishlist

aptitude allows to install/upgrade packages and mark them as
automatically installed:

  aptitude install foo+M

I find this feature useful when asking to upgrade to a specific version
of a package, but not wanting to have it marked as manually installed.
A Cultist of the Cow has asked on IRC to file bugs for this.  Said
Cultist of the Cow has also indicated that juliank might be pleased by
this feature as well.

Ansgar

Bug#970176: aka new upstream release

[Theodore Y. Ts'o]

On Tue, Oct 27, 2020 at 12:24:51AM +0100, Diederik de Haas wrote:
> Package: f2fs-tools
> Version: 1.11.0-1.1
> Followup-For: Bug #970176
> 
> On salsa.d.o it looks like version 1.13 was ready to go, but it appears
> that it just never got uploaded to the archives/sid.
> It would be really welcome to have a more recent version of f2fs-tools
> in Bullseye and as 1.14 has been released/tagged upstream, it would be
> great to have that one. (But 1.13 would be an improvement as well)
> 
> The freeze is only a couple of months away...

Unfortunately, it can take **months** for the package to go throw the
NEW queue, since f2fs-tools is constantly making ABI-breaking changes
so we have to bump the shared library, causing it to have to go
through ftp-masters.

As such, the super-long latency is super-demotivating, so I've not
just bothered in a while.

I suspect what we should do is drop the shared libraries all together,
and just ship statically linked executables since the f2fs upstream is
constitutionally incapable of keeping shared library ABI's stable.

So it's on my todo list, but that's probably what needs to happen so
we can actually get something posted to sid without being stalled for
months and months in the NEW queue.

I'll try to get it at some point, but if someone else wants to work on
making the necessary changes to the package, help is welcome.  Things
are just a bit busy at the moment, and I've only been working on f2fs
for gce/kvm-xfstests, and testing f2fs hasn't been high on my priority
list.  If someone else wants to be a co-maintainer, that would be
great, since I was only stepping up because no one *else* was updating
f2fs-tools and f2fs-tools was super-out-of-date when I first uploaded
an f2fs-tools updates.

Cheers,

- Ted

Bug#973135: Help needed: Bug#973070: libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests because: 1 exceptions: [java.io.IOException: Unab

[Markus Koschany]

Hi,

This appears to be caused by the recent upgrade of Apache commons-io to
version 2.8.0 (we had 2.6), see also #973135. In version 2.7 they
removed a throws IOException in the method isSymlink()

https://issues.apache.org/jira/browse/IO-610

Could it be related to this change? It is probably necessary to update
the testcase or disable it for a quick workaround.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#972943: libtheora0: Too easy to enable "telemetry" (statistics capture) by mistake, causing poor performance

[Sebastian Ramacher]

Control: tags -1 - patch

On 2020-10-26 13:19:36 +, Simon McVittie wrote:
> Package: libtheora0
> Version: 1.1.1+dfsg.1-11
> Severity: normal
> Tags: patch fixed-upstream
> Forwarded: https://gitlab.xiph.org/xiph/theora/-/issues/2312
> 
> The latest version of Proton (Valve's branch of Wine, used to run Windows
> games under Steam) runs in a Debian 10-based container
> (Steam Runtime 2 'soldier'), instead of the Ubuntu 12.04-based
> LD_LIBRARY_PATH library bundle (Steam Runtime 1 'scout') that was used
> in previous releases.
> 
> During the move from Steam Runtime 1 to 2, Proton developers noticed
> a performance regression in their GStreamer-based video decoding,
> which they were able to track down to the theoradec plugin. This plugin
> uses libtheora, which has an optional feature called "telemetry" that
> records statistics. It can be enabled or disabled at build-time; if
> enabled at build-time, it is disabled by default at runtime. Activating
> it at runtime involves setting some options, and incurs a significant
> performance cost to convert each decoded frame from YUV to RGB for use
> by Cairo (30-40ms per frame for 1920x1080 video).
> 
> Note that despite its name, as far as I'm aware "telemetry" does not
> send the statistics anywhere, it just captures them - so it isn't a
> privacy problem, and is really just "-metry", with no "tele-" involved :-)
> 
> In Debian, the telemetry feature is enabled in libtheora at build-time
> since 1.1.1+dfsg.1-11, as requested in
> .
> 
> GStreamer's theoradec plugin attempts to set the telemetry options to
> user-specified values.  However, in released versions of libtheora,
> setting the telemetry options to any value - even 0 - is documented to
> have the side-effect of enabling the telemetry feature and triggering
> the performance regression.
> 
> This can be fixed in three ways:
> 
> 1. Disable telemetry at compile-time in libtheora.
>We did this in the Steam Runtime as a temporary solution, but it's a
>feature regression for libtheora, and the libtheora maintainers in
>Debian presumably don't want that, so let's discard this option.
> 
> 2. In GStreamer, if the telemetry options are set to 0, don't propagate
>that into libtheora so that the expensive YUV -> RGB conversion is
>not done, even with current releases of libtheora. This is
>
> 
>and I've filed a separate Debian bug for it. The patch has been merged
>upstream and was backported to 1.18.x (for 1.18.1, I think) in
>
> .
> 
> 3. In libtheora, if the telemetry options are all explicitly set to 0
>(for example by current versions of GStreamer), behave as though they
>had not been set at all, and therefore don't enable the expensive
>YUV -> RGB conversion. This is
> and
>, and is what
>this bug report represents. The patch has been merged upstream for
>v1.2.0, but there hasn't been an upstream release since 1.2.0 alpha 1
>(which doesn't have this change) in 2010, so it seems unlikely that
>there will be a release with this change any time soon.

FWIW, the upstream change does not apply to 1.1.1 and needs to be
adapted accordingly. th_decode_packetin seems to be sufficently
different that I leave that to someone with some deeper knowledge of the
code.

Cheers

> 
> Following the principle that bad interactions between two components are
> most robust if fixed on *both* sides, solutions 2 and 3 have both been
> accepted upstream, and I suggest that they should also happen in Debian.
> 
> The Steam Runtime maintainers will probably be doing a backport of this
> into 1.1.1, so I'll try to send a patch later.
> 
> Thanks,
> smcv
> 

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#973241: [Pkg-utopia-maintainers] Bug#973241: network-manager: is crda still recommendable?

[Ben Hutchings]

On Tue, 2020-10-27 at 20:58 +0100, Michael Biebl wrote:
> Hi
> 
> Am 27.10.20 um 19:48 schrieb Patrice Duroux:
> > Package: network-manager
> > Version: 1.27.91-1
> > Severity: minor
> > 
> > Dear Maintainer,
> > 
> > First I read this:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972994
> > 
> > Then I checked this:
> > https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/crda.git/tree/README
> > 
> > Finally I do this:
> > > LANG=C apt rdepends crda
> > crda
> > Reverse Depends:
> >Recommends: network-manager
> >  crda:i386
> >Suggests: wireless-regdb
> >  crda:i386
> > 
> > 
> > Stretch has Linux 4.9 < 4.15
> > Buster has Linux 4.19 > 4.15

It took some time for us to sort out signing and direct loading of the
regulatory database, so it is *not* enabled by the 4.19 kernel in
buster.

> > But network-manager does not have the same version for both.
> > So should the recommendation be deleted?
> 
> Bringing Ben into the loop who requested the addition of this Recommends 
> in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653706
> 
> Would be great to have your feedback here.

I think you can safely drop it for bullseye.  In addition to crda
itself, the package also contains a udev rule for setting the
regulatory domain that may still be useful, but it is not generally
needed.

Ben.

-- 
Ben Hutchings
All the simple programs have been written, and all the good names taken




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

Bug#973055: python3-ofxparse: Python 3.8+ DeprecationWarning

[tdi-odoo]

Package: python3-ofxparse
Version: 0.15+git20161013-1
Severity: normal

Dear Maintainer,

Using python3-ofxparse (be it with
buster,bullseye or sid)  with Python 3.8 or 3.9
yields the following warning:

ofxparse/ofxparse.py:40: DeprecationWarning: Using or importing the ABCs from
'collections'
instead of from 'collections.abc' is deprecated since Python 3.3, and in 3.9 it
will stop working
return isinstance(candidate, collections.Iterable)

This issue was already addressed and fixed here
https://github.com/jseutter/ofxparse/issues/155

Thanks in advance for your help,
Thomas



-- System Information:
Debian Release: buster/sid
  APT prefers bionic-updates
  APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 
'bionic'), (100, 'bionic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages python3-ofxparse depends on:
ii  python3   3.6.7-1~18.04
ii  python3-bs4   4.6.0-1
ii  python3-lxml  4.2.1-1ubuntu0.1
ii  python3-six   1.11.0-2

python3-ofxparse recommends no packages.

python3-ofxparse suggests no packages.

-- no debconf information

Bug#973112: libcxx-serial: FTBFS: make[5]: *** No rule to make target 'tests/gmock/libgmock.a', needed by 'devel/lib/cxx-serial/cxx-serial-test'. Stop.

[Alec Leamas]

On Tue, 27 Oct 2020 18:06:31 +0100 Lucas Nussbaum  wrote:
> Source: libcxx-serial
> Version: 1.2.1-3
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201027 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Ack, I can reproduce it. This might trigger a major update if I cannot
find a simple solution. Back later

Bug#973251: FTBFS: src/PdbMlFilePyWrap.C:7:10: fatal error: PdbMlFileUtil.h: No such file or directory

[Steve Langasek]

Package: librcsb-core-wrapper
Version: 1.005-8
Severity: normal
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch

Dear maintainers,

After applying the patch from bug #973249, librcsb-core-wrapper still fails
to build from source when trying to build the python3 wrapper, due to
problems with the include path:

[...]
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security 
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/tmp/librcsb-core-wrapper-1.005=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I../../include -I/usr/include/python3.9 -c 
src/PdbMlFilePyWrap.C -o build/temp.linux-x86_64-3.9/src/PdbMlFilePyWrap.o
src/PdbMlFilePyWrap.C:7:10: fatal error: PdbMlFileUtil.h: No such file or 
directory
7 | #include "PdbMlFileUtil.h"
  |  ^
compilation terminated.
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:352: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3.9 setup.py build 
[...]

I've tried without any success to resolve this include path error.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#973070: Help needed: Bug#973070: libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests because: 1 exceptions: [java.io.IOException: Unab

[Thorsten Glaser]

On Tue, 27 Oct 2020, Andreas Tille wrote:

> > > Caused by: java.io.IOException: Unable to delete file: 
> > > targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink
> > >   at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1425)
> > >   at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:338)
> > >   ... 4 more
> > > Caused by: java.nio.file.NoSuchFileException: 
> > > targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink

I read this “cannot delete a dangling link because it does not exist”.

Can you check (add debugging output, best shell out to 'ls -l', because
at this point I don’t trust the JRE!) whether


targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink

indeed exists at this point, and if so, is a symlink, and whether the
symlink target exists?

I saw an issue with symlinks in the Maven Resources Plugin recently
and now wonder whether this is not a JRE bug. Though we could probably
cobble up an MWE…

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

*

Mit unserem Consulting bieten wir Unternehmen maßgeschneiderte Angebote in
Form von Beratung, Trainings sowie Workshops in den Bereichen
Softwaretechnologie, IT Strategie und Architektur, Innovation und Umsetzung
sowie Agile Organisation.

Besuchen Sie uns auf https://www.tarent.de/consulting .
Wir freuen uns auf Ihren Kontakt.

*

Bug#973250: libpam-tacplus: CVE-2020-27743

[Salvatore Bonaccorso]

Source: libpam-tacplus
Version: 1.3.8-2
Severity: important
Tags: security upstream
Forwarded: https://github.com/kravietz/pam_tacplus/pull/163
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for libpam-tacplus.

CVE-2020-27743[0]:
| libtac in pam_tacplus through 1.5.1 lacks a check for a failure of
| RAND_bytes()/RAND_pseudo_bytes(). This could lead to use of a non-
| random/predictable session_id.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-27743
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27743
[1] https://github.com/kravietz/pam_tacplus/pull/163

Regards,
Salvatore

Bug#386755: [PATCH 1/2] ifdata: fail when -ph is given but no hwaddr is available (Closes: #386755)

[Nicolas Schier]

Exit ifdata with an error code if '-ph' (print hardware address) is
given but no hardware address is available for the given network device.
Previously, ifdata printed the invalid hardware address
00:00:00:00:00:00 in such cases and exited as if this was the real
hardware address.

Signed-off-by: Nicolas Schier 
---
 ifdata.c   | 7 +++
 ifdata.docbook | 5 -
 2 files changed, 11 insertions(+), 1 deletion(-)

diff --git a/ifdata.c b/ifdata.c
index 99f30e9..6e0bd0b 100644
--- a/ifdata.c
+++ b/ifdata.c
@@ -195,6 +195,13 @@ void if_hwaddr(const char *iface) {
return;
 
hwaddr = (unsigned char *)r.ifr_hwaddr.sa_data;
+
+   if (!hwaddr[0] && !hwaddr[1] && !hwaddr[2] &&
+   !hwaddr[3] && !hwaddr[4] && !hwaddr[5]) {
+   fprintf(stderr, "Error: %s: no hardware address\n", iface);
+   exit(1);
+   }
+
printf("%02X:%02X:%02X:%02X:%02X:%02X",
   hwaddr[0], hwaddr[1], hwaddr[2], hwaddr[3], hwaddr[4], 
hwaddr[5]);
 }
diff --git a/ifdata.docbook b/ifdata.docbook
index 47f4143..d2b3e10 100644
--- a/ifdata.docbook
+++ b/ifdata.docbook
@@ -155,7 +155,10 @@ with this program; if not, write to the Free Software 
Foundation, Inc.,
-ph

Prints the hardware address of the
-   interface.
+interface. Exit with a failure exit 
code
+if there is not hardware address for 
the
+given network interface.
+


 
-- 
2.25.0

Bug#973045:

[Sudip Mukherjee]

Control: unblock 973047 by -1
--

Turns out that this one is not needed for s2-geometry-library java
library and so unblocking #973047.
Its almost packaged in local system but I am not uploading since I
dont need it now. Keeping the ITP open, if anyone needs this package
then I can upload.


-- 
Regards
Sudip

Bug#973249: FTBFS: src/CifFilePyWrap.C:7:10: fatal error: CifFileUtil.h: No such file or directory

[Steve Langasek]

Package: librcsb-core-wrapper
Version: 1.005-8
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu  ubuntu-patch

Dear maintainers,

We've found that librcsb-core-wrapper fails to build from source in Ubuntu,
due to references to a generated header file that is renamed as part of the
build.

I don't understand why this wasn't an issue previously, since it seems
obvious that the .tab.c file is going to have references to .tab.h, but
regardless, the attached patch fixes the build failure on Ubuntu.  I have
not tested whether the build failure also affects Debian, but I imagine it
would; and in any case the patch should not break anything in Debian.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru librcsb-core-wrapper-1.005/debian/patches/generated-includes 
librcsb-core-wrapper-1.005/debian/patches/generated-includes
--- librcsb-core-wrapper-1.005/debian/patches/generated-includes
1969-12-31 16:00:00.0 -0800
+++ librcsb-core-wrapper-1.005/debian/patches/generated-includes
2020-10-27 12:06:49.0 -0700
@@ -0,0 +1,19 @@
+Author: Steve Langasek 
+Description: fix up include path for generated header file that's moved
+ The makefile renames the .tab.c and .tab.h files to .c and .h, but does 
+ not fix up references from the .tab.h header from within the .c file.  
+ I'm surprised this ever worked, but it doesn't work now.
+Last-Update: 2020-10-27
+
+Index: librcsb-core-wrapper-1.005/cif-parser/Makefile
+===
+--- librcsb-core-wrapper-1.005.orig/cif-parser/Makefile
 librcsb-core-wrapper-1.005/cif-parser/Makefile
+@@ -181,6 +181,7 @@
+   sh -c 'cd $(SRC_DIR); $(YACC) $(${^F:.y=_YACC_FLAGS}) ../$<'
+   mv $(^:.y=.tab.c) $(^:.y=.c)
+   mv $(^:.y=.tab.h) $(^:.y=.h)
++  sed -i -e's/\.tab\.h/\.h/' $(^:.y=.c)
+   libtool --mode=compile $(CC) $(CPPFLAGS) $(CFLAGS_NONANSI) -c 
$(^:.y=.c) -o obj/$(*)Parser.o
+ 
+ obj/%Scanner.o: $(SRC_DIR)/%Scanner.l $(OBJ_DIR)/%Parser.o 
$(SRC_DIR)/%Parser.h
diff -Nru librcsb-core-wrapper-1.005/debian/patches/series 
librcsb-core-wrapper-1.005/debian/patches/series
--- librcsb-core-wrapper-1.005/debian/patches/series2019-12-21 
10:36:10.0 -0800
+++ librcsb-core-wrapper-1.005/debian/patches/series2020-10-27 
12:06:59.0 -0700
@@ -16,3 +16,4 @@
 xerces32.patch
 gcc-8.patch
 python3.patch
+generated-includes

Bug#957138: directvnc: diff for NMU version 0.7.7-1.1

[Sudip Mukherjee]

Control: tags 957138 + patch
Control: tags 957138 + pending
--

Dear maintainer,

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

--
Regards
Sudip

diff -Nru directvnc-0.7.7/debian/changelog directvnc-0.7.7/debian/changelog
--- directvnc-0.7.7/debian/changelog2011-07-31 17:20:41.0 +0100
+++ directvnc-0.7.7/debian/changelog2020-10-27 19:25:19.0 +
@@ -1,3 +1,10 @@
+directvnc (0.7.7-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957138)
+
+ -- Sudip Mukherjee   Tue, 27 Oct 2020 19:25:19 
+
+
 directvnc (0.7.7-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru directvnc-0.7.7/debian/patches/fix_gcc-10.patch 
directvnc-0.7.7/debian/patches/fix_gcc-10.patch
--- directvnc-0.7.7/debian/patches/fix_gcc-10.patch 1970-01-01 
01:00:00.0 +0100
+++ directvnc-0.7.7/debian/patches/fix_gcc-10.patch 2020-10-27 
19:19:25.0 +
@@ -0,0 +1,44 @@
+Description: Fix ftbfs with GCC-10
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/957138
+Forwarded: no
+
+---
+
+--- directvnc-0.7.7.orig/src/directvnc.h
 directvnc-0.7.7/src/directvnc.h
+@@ -42,7 +42,7 @@
+Tight encoding assumes BUFFER_SIZE is at least 16384 bytes. */
+ 
+ #define BUFFER_SIZE (640*480) 
+-char buffer[BUFFER_SIZE];
++extern char buffer[BUFFER_SIZE];
+ 
+ #define MAX_ENCODINGS 10
+ 
+@@ -64,9 +64,9 @@ struct _mousestate
+unsigned int buttonmask;
+ };
+ 
+-struct _mousestate mousestate;
++extern struct _mousestate mousestate;
+ 
+-int sock;
++extern int sock;
+ 
+ /* rfb.c */
+ int rfb_connect_to_server (char *server, int display);
+--- directvnc-0.7.7.orig/src/main.c
 directvnc-0.7.7/src/main.c
+@@ -24,6 +24,10 @@
+ #include 
+ #include 
+ 
++struct _mousestate mousestate;
++int sock;
++char buffer[BUFFER_SIZE];
++
+ /* little convenience function */
+ static inline double get_time(void);
+ static inline void sig_handler(int foo) { exit(1); }
diff -Nru directvnc-0.7.7/debian/patches/series 
directvnc-0.7.7/debian/patches/series
--- directvnc-0.7.7/debian/patches/series   1970-01-01 01:00:00.0 
+0100
+++ directvnc-0.7.7/debian/patches/series   2020-10-27 18:52:57.0 
+
@@ -0,0 +1 @@
+fix_gcc-10.patch

Bug#973248: Deprecation warning in Ruby 2.7: $SAFE will become a normal global variable in Ruby 3.0

[Miquel van Smoorenburg]

Package: puppet
Version: 5.5.22-1

This is a similar but different bug as 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955532 .


I get this warning on a puppet run:

/usr/lib/ruby/vendor_ruby/puppet/file_system/uniquefile.rb:126: warning: 
$SAFE will become a normal global variable in Ruby 3.0


I tried fixing it by setting Warning[:deprecated] = false, but that does 
not work for this specific warning, weirdly enough.


So I tried another minimal approach. This fixes it for me, and it should 
also fix those other deprecation warnings from #955532, so that patch 
can be dropped if you want.


--- a/puppet 2020-10-25 18:04:24.0 +0100
+++ b/puppet 2020-10-27 19:45:13.784467214 +0100
@@ -1,5 +1,11 @@
 #!/usr/bin/ruby

+def Warning.warn(w)
+  if w !~ /warning: (URI.(un|)escape is obsolete|\$SAFE will become a 
normal global variable)/

+super w
+  end
+end
+
 begin
   require 'puppet/util/command_line'
   Puppet::Util::CommandLine.new.execute

Mike.

Bug#875306: python-debian: include a type for buildinfo files

[Holger Levsen]

Hi Stuart,

thank you very much for your work on adding .buildinfo support for
python-debian!

On Sun, Oct 25, 2020 at 05:32:19PM +1100, Stuart Prescott wrote:
> The .buildinfo files have two places where interpreting the values seems 
> worthwhile:
> 
>   Environment: split the lines and extract the key="value" data into a
>   dictionary in the same format as Python's normal `os.environ`. (Some
>   dequoting is needed but not currently implemented.)
> 
>   Installed-Build-Depends: use the standard package-relation code on this 
> to
>   return interpret the list of packages.

I believe there is a third place: changelog stanzas (aka Binary-Only-Changes:)
from binNMUs, like the one from
https://buildinfos.debian.net/ftp-master.debian.org/buildinfo/2020/10/27/dqlite_1.6.0-1+b1_amd64.buildinfo

Binary-Only-Changes:
 dqlite (1.6.0-1+b1) sid; urgency=low, binary-only=yes
 .
   * Binary-only non-maintainer upload for amd64; no source changes.
   * Rebuild on buildd
 .
  -- amd64 Build Daemon (x86-grnet-01) 
  Tue, 27 Oct 2020 16:00:36 +

 
> Are there additional data that would be nice to extract and interpret in a 
> structured way?

see above and very much so! 


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

Moral, truth, long term- and holistic thinking seem to mean nothing to us. The
emperors are naked. Every single one. It turns out our whole society is just
one big nudist party. (Greta Thunberg about the world reacting to the corona
crisis but not reacting appropriatly to the climate crisis.)


signature.asc
Description: PGP signature

Bug#973070: Help needed: Bug#973070: libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests because: 1 exceptions: [java.io.IOException: Unab

[Andreas Tille]

Control: tags -1 help

Hi,

I checked out the latest upstream commit and pushed it to Salsa.
Its the same with this.  Any idea why this test has worked before
but is failing now?

Kind regards

  Andreas.

On Tue, Oct 27, 2020 at 06:06:55PM +0100, Lucas Nussbaum wrote:
> Source: libsis-base-java
> Version: 18.09~pre1+git20180827.fe4953e+dfsg-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201027 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > dh_auto_test -a
> > mkdir test ; cp -r source/java/ch test ; cp -r sourceTest/java/ch test
> > jh_build sis-base-test.jar test
> > warning: [options] bootstrap class path not set in conjunction with -source 
> > 7
> > 1 warning
> > test/ch/systemsx/cisd/base/mdarray/MDAbstractArray.java:354: warning - 
> > invalid usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDAbstractArray.java:393: warning - 
> > invalid usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDArray.java:47: warning - invalid usage 
> > of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDArray.java:87: warning - invalid usage 
> > of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDByteArray.java:47: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDByteArray.java:87: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDDoubleArray.java:47: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDDoubleArray.java:87: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDFloatArray.java:47: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDFloatArray.java:87: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDIntArray.java:47: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDIntArray.java:87: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDLongArray.java:47: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDLongArray.java:87: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDShortArray.java:47: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/mdarray/MDShortArray.java:87: warning - invalid 
> > usage of tag >
> > test/ch/systemsx/cisd/base/utilities/NativeLibraryUtilities.java:105: 
> > warning - Tag @link: reference not found: System#loadLibrary()
> > 17 warnings
> > LC_ALL=C java -Djava.library.path=source/c/.libs -classpath 
> > sis-base-test.jar ch.systemsx.cisd.base.AllTests
> > Application: base
> > Version: UNKNOWN*
> > Java VM: OpenJDK 64-Bit Server VM (v11.0.9+11-post-Debian-1)
> > CPU Architecture: amd64
> > OS: Linux (v4.19.0-6-cloud-amd64)
> > Test class: NativeDataTests
> > 
> > Running testIntToByteToInt
> >  Arguments: [0, 0]
> >  Arguments: [0, 1]
> >  Arguments: [0, 2]
> >  Arguments: [0, 3]
> >  Arguments: [1, 0]
> >  Arguments: [1, 1]
> >  Arguments: [1, 2]
> >  Arguments: [1, 3]
> >  Arguments: [2, 0]
> >  Arguments: [2, 1]
> >  Arguments: [2, 2]
> >  Arguments: [2, 3]
> >  Arguments: [3, 0]
> >  Arguments: [3, 1]
> >  Arguments: [3, 2]
> >  Arguments: [3, 3]
> > Running testIntChangeByteOrderAndBack
> > Running testShortChangeByteOrderAndBack
> > Running testCharChangeByteOrderAndBack
> > Running testLongChangeByteOrderAndBack
> > Running testFloatChangeByteOrderAndBack
> > Running testDoubleChangeByteOrderAndBack
> > Running testLongToByteToLong
> >  Arguments: [0, 0]
> >  Arguments: [0, 1]
> >  Arguments: [0, 2]
> >  Arguments: [0, 3]
> >  Arguments: [1, 0]
> >  Arguments: [1, 1]
> >  Arguments: [1, 2]
> >  Arguments: [1, 3]
> >  Arguments: [2, 0]
> >  Arguments: [2, 1]
> >  Arguments: [2, 2]
> >  Arguments: [2, 3]
> >  Arguments: [3, 0]
> >  Arguments: [3, 1]
> >  Arguments: [3, 2]
> >  Arguments: [3, 3]
> > Running testShortToByteToShort
> >  Arguments: [0, 0]
> >  Arguments: [0, 1]
> >  Arguments: [0, 2]
> >  Arguments: [0, 3]
> >  Arguments: [1, 0]
> >  Arguments: [1, 1]
> >  Arguments: [1, 2]
> >  Arguments: [1, 3]
> >  Arguments: [2, 0]
> >  Arguments: [2, 1]
> >  Arguments: [2,

Bug#973247: python-cryptography: CVE-2020-25659: Bleichenbacher timing oracle attack against RSA decryption

[Salvatore Bonaccorso]

Source: python-cryptography
Version: 3.1-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 2.6.1-3+deb10u2
Control: found -1 2.6.1-3

Hi,

The following vulnerability was published for python-cryptography.

CVE-2020-25659[0]:
| bleichenbacher timing oracle attack against RSA decryption

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-25659
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25659
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1889988
[2] 
https://github.com/pyca/cryptography/commit/58494b41d6ecb0f56b7c5f05d5f5e3ca0320d494
[3] https://github.com/pyca/cryptography/security/advisories/GHSA-hggm-jpg3-v476

Regards,
Salvatore

Bug#922232: src:distro-info: Please take over distro info from python-apt

[Julian Andres Klode]

Control: reassign -1 distro-info-data

On Wed, Feb 13, 2019 at 02:56:39PM +0100, Julian Andres Klode wrote:
> Package: src:distro-info
> Severity: wishlist
> 
> This is for bullseye, but filing it now, so we can do it at the
> start of the quarter
> 
> python-apt currently ships various data files detailing the available
> distributions:
> 
>   https://salsa.debian.org/apt-team/python-apt/tree/master/data/templates
> 
> The .info.in are templates that get translations merged in at build-time.
> 
> I'd like to drop those files from python-apt to reduce the number of
> packages that need an update for a new release, and I think it makes
> sense to ship them in distro-info, somewhere, likely in distro-info-data.
> 
> This info also includes mirror lists, which need occasional updates, and
> having that in distro-info-data certainly makes it easier to update those
> lists more frequently, as it's kind of a waste to do a python-apt update
> just for that.

I've now made python-apt fill in most stuff from the csv files in
distro-info-data in 

https://salsa.debian.org/apt-team/python-apt/-/merge_requests/52/

so it does not need updates for new releases anymore. That said, getting
rid of that logic in there and moving that data to distro-info-data is
still welcome.

That said, we do want the mirror lists to move out of the package and
into dists/ at some point too, so there won't be much stuff that needs
updates.

Reassigning to proper package.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#973241: [Pkg-utopia-maintainers] Bug#973241: network-manager: is crda still recommendable?

[Michael Biebl]

Hi

Am 27.10.20 um 19:48 schrieb Patrice Duroux:

Package: network-manager
Version: 1.27.91-1
Severity: minor

Dear Maintainer,

First I read this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972994

Then I checked this:
https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/crda.git/tree/README

Finally I do this:

LANG=C apt rdepends crda

crda
Reverse Depends:
   Recommends: network-manager
 crda:i386
   Suggests: wireless-regdb
 crda:i386


Stretch has Linux 4.9 < 4.15
Buster has Linux 4.19 > 4.15

But network-manager does not have the same version for both.
So should the recommendation be deleted?


Bringing Ben into the loop who requested the addition of this Recommends 
in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653706


Would be great to have your feedback here.

Regards,
Michael



OpenPGP_signature
Description: OpenPGP digital signature

Bug#973244: ITP: python-mediafile -- read and write audio files' tags in Python

[Louis-Philippe Véronneau]

Package: wnpp
Severity: wishlist
Owner: po...@debian.org

* Package name : python-mediafile
  Version : 0.6.0
  Upstream Author : Adrian Sampson 
* URL : https://github.com/beetbox/mediafile
* License : Expat
  Programming Lang: Python
  Description : read and write audio files' tags in Python

MediaFile is a simple interface to the metadata tags for many audio file
formats. It wraps Mutagen, a high-quality library for low-level tag
manipulation, with a high-level, format-independent interface for a
common set of tags.

This library will be needed to package supysonic in the future. I
intend to maintain it in the Debian Python Team.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄



signature.asc
Description: OpenPGP digital signature

Bug#973245: openrc: CVE-2018-21269: checkpath root privilege escalation following non-terminal symlinks

[Salvatore Bonaccorso]

Source: openrc
Version: 0.42-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/OpenRC/openrc/issues/201
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 0.40.3-1

Hi,

The following vulnerability was published for openrc.

CVE-2018-21269[0]:
| checkpath in OpenRC through 0.42.1 might allow local users to take
| ownership of arbitrary files because a non-terminal path component can
| be a symlink.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-21269
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21269
[1] https://github.com/OpenRC/openrc/issues/201
[2] http://michael.orlitzky.com/cves/cve-2018-21269.xhtml

Regards,
Salvatore

Bug#973246: opentmpfiles: CVE-2017-18188

[Salvatore Bonaccorso]

Source: opentmpfiles
Version: 0.2+2019.05.21.git.44a55796ba-2
Severity: important
Tags: security upstream
Forwarded: https://github.com/OpenRC/opentmpfiles/issues/3
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for opentmpfiles.

CVE-2017-18188[0]:
| OpenRC opentmpfiles through 0.1.3, when the fs.protected_hardlinks
| sysctl is turned off, allows local users to obtain ownership of
| arbitrary files by creating a hard link inside a directory on which
| "chown -R" will be run.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-18188
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-18188
[1] https://github.com/OpenRC/opentmpfiles/issues/3

Regards,
Salvatore

Bug#973177: python-geojson: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13

[Sebastiaan Couwenberg]

Control: tags -1 upstream pending

This is fixed upstream, the commit in question will be included as a patch.

Kind Regards,

Bas

Bug#973243: libprelude: mark additional template symbols optional for Ubuntu/s390x

[Steve Langasek]

Package: libprelude
Version: 5.1.1-6
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu  ubuntu-patch

Hi Pierre,

In Ubuntu, libprelude has started failing to build from source on s390x due
to some toolchain changes that now hide some additional template symbols
that are not currently marked as optional.  Please consider the attached
patch which marks these additional symbols.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libprelude-5.1.1/debian/libpreludecpp12.symbols 
libprelude-5.1.1/debian/libpreludecpp12.symbols
--- libprelude-5.1.1/debian/libpreludecpp12.symbols 2020-04-17 
17:07:24.0 -0700
+++ libprelude-5.1.1/debian/libpreludecpp12.symbols 2020-10-27 
11:48:43.0 -0700
@@ -358,17 +358,17 @@
  _ZNK7Prelude9IDMEFTimeneERKS0_@Base 4.1
  
(optional)_ZNSt12_Vector_baseIN7Prelude10IDMEFClass14IDMEFClassElemESaIS2_EED1Ev@Base
 5.1.1
  
(optional)_ZNSt12_Vector_baseIN7Prelude10IDMEFClass14IDMEFClassElemESaIS2_EED2Ev@Base
 5.1.1
- 
_ZNSt6vectorIN7Prelude10ConnectionESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 4.1
- 
_ZNSt6vectorIN7Prelude10IDMEFClass14IDMEFClassElemESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 4.1
+ 
(optional)_ZNSt6vectorIN7Prelude10ConnectionESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 4.1
+ 
(optional)_ZNSt6vectorIN7Prelude10IDMEFClass14IDMEFClassElemESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 4.1
  
(optional)_ZNSt6vectorIN7Prelude10IDMEFClass14IDMEFClassElemESaIS2_EEaSERKS4_@Base
 4.1
- 
_ZNSt6vectorIN7Prelude10IDMEFValueESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 4.1
- 
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 4.1
+ 
(optional)_ZNSt6vectorIN7Prelude10IDMEFValueESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 4.1
+ 
(optional)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 4.1
  
(optional)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base
 4.1
  _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 5.0.0
  _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 5.0.0
  _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED2Ev@Base 5.0.0
  
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOS5_EESJ_IJESt17_Rb_tree_iteratorIS8_ESt23_Rb_tree_const_iteratorIS8_EDpOT_@Base
 5.0.0
- 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base
 5.0.0
+ 
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base
 5.0.0
  
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base
 5.0.0
  
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base
 5.0.0
  _ZTIN7Prelude12PreludeErrorE@Base 4.1

Bug#963930: Abandoned ITA?

[Francisco M Neto]

Greetings,

I've been following this ITA for sometime, mostly because earlier this
year I was using starfighter as a case study for debian packaging.

I noticed that it has not seen activity in a while, and the Freeze is
getting closer. So I'd like to check if this package is still being
worked on.

I'd like to take over adoption for package starfighter. I'm going to
wait another 3 days for a reply, and after that I'll take ownership if
no reply is given.

Cheers

-- 
[]'s,

Francisco M Neto 
www.fmneto.com

3E58 1655 9A3D 5D78 9F90
CFF1 D30B 1694 D692 FBF0


0xD30B1694D692FBF0.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Bug#971515: Request for security team input on kubernetes TC bug

[Moritz Mühlenhoff]

On Wed, Oct 21, 2020 at 08:22:11AM -0700, Sean Whitton wrote:
> Hello security team,
> 
> The TC are being asked about src:kubernetes, and it would be good to
> hear from you about whether and how security support is a relevant
> consideration in determining whether the level of vendoring in that
> package is acceptable.  Could you take a look at #971515 and perhaps
> give us some input, please?

I don't currently have the time to read through all the discussion backlog,
but let me try to "zoom out a bit":

The bigger issue here (independent of the whole vendoring aspect) is
how kubernetes can be supported in a stable release to begin with.
This was raised by Shengjing Zhu in #959685 before.

Upstream support only lasts for up to a year and it would be
presumptuous to pretend that we can seriously commit to fix
security issues in k8s for longer than upstream.

This leaves Debian with two options:
* Keep it out of a stable release and accept that it's good enough
  if people just install whatever deb they currently find in testing/sid
  (works out well enough for most given that blob nature of Go!)
* Follow a scheme similar to Firefox ESR where in case of a security
  the update either happens to the latest minor release of
  the current branch or if that has stopped, happens to the next
  major release. To map this to specific k8s releases: Let's assume bullseye
  were already stable and would ship 19.3. In three months a security issue
  arises which is severe enough to warrant an update and we ship 19.5
  in a DSA. Fast forward 6 months and 19.x is EOLed, but some severe
  security issue needs to be fixed; then the bullseye update would move
  to 20.1 or so. That sounds unusual for a Debian release, but it's
  the status quo for _any_ Kubernetes user after all (whether deployed
  on premises or at some "cloud vendor").

If we follow the latter approach, then the current way k8s is packaged
is the only viable option (as otherwise the run time deps shipped
for 19.x would be incompatible with 20.x etc.)

Cheers,
Moritz

Bug#938351: marked as pending in renpy

[Markus Koschany]

Am 27.10.20 um 20:10 schrieb Gregor Riepl:
>> https://salsa.debian.org/games-team/renpy/commit/fc29ebfe106238b590a7896450a5d1ad1f94f84e
>>
>> 
>> Switch to python3.
>>
>> Closes: #938351
>> 
> 
> I'm confused.
> Does that mean upstream has completed the port to Python 3?

No.

> Last I checked, the bug was still wide open:
> https://github.com/renpy/renpy/issues/1098

Just the dependencies were switched to Python 3 and the Git hook sent an
automatic email to the BTS.



signature.asc
Description: OpenPGP digital signature

Bug#938351: marked as pending in renpy

[Gregor Riepl]

> https://salsa.debian.org/games-team/renpy/commit/fc29ebfe106238b590a7896450a5d1ad1f94f84e
> 
> 
> Switch to python3.
> 
> Closes: #938351
> 

I'm confused.
Does that mean upstream has completed the port to Python 3?

Last I checked, the bug was still wide open:
https://github.com/renpy/renpy/issues/1098

Bug#973034: supysonic's autopkg tests are failing with python3.9

[Louis-Philippe Véronneau]

tags -1 fixed
block 973034 by 972717
thanks

This has been fixed in the VCS already [1], but a new revision can't be
uploaded since this package FTBFS with python3.9

[1]:
https://salsa.debian.org/python-team/packages/supysonic/-/commit/e187fd03c2c22939778f870f07fbfada50b9ada7

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄



signature.asc
Description: OpenPGP digital signature

Bug#973046: ITP: ayatana-indicator-bluetooth -- Ayatana Bluetooth System Indicator

[Mike Gabriel]

Package: wnpp
Severity: wishlist
Owner: Mike Gabriel 

* Package name: ayatana-indicator-bluetooth
  Version : 0.8.0
  Upstream Author : Marius Gripsgard 
Robert Tari 
Mike Gabriel 
* URL : 
https://github.com/AyatanaIndicators/ayatana-indicator-bluetooth/
* License : GPL-3
  Programming Lang: Vala
  Description : Ayatana Bluetooth System Indicator

 This Ayatana Indicator exposes bluetooth functionality via the system
 indicator API and provides fast user controls for Bluetooth devices.
 .
 This package will be maintained under the umbrellas of the Debian Ayatana
 Developers and the Debian UBports Packaging Team.

Bug#973242: CVE-2017-18925

[Moritz Muehlenhoff]

Package: opentmpfiles
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

This was assigned CVE-2017-18925:
https://github.com/OpenRC/opentmpfiles/issues/4

Cheers,
Moritz

Bug#973222: python-smoke-zephyr: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13

[Lucas Nussbaum]

Source: python-smoke-zephyr
Version: 2.0.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package python-smoke-zephyr
> dpkg-buildpackage: info: source version 2.0.0-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Samuel Henrique 
> 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.9_smoke-zephyr/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
> I: pybuild base:217: python3.8 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.8_smoke-zephyr/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-smoke-zephyr using existing 
> ./python-smoke-zephyr_2.0.0.orig.tar.gz
> dpkg-source: info: building python-smoke-zephyr in 
> python-smoke-zephyr_2.0.0-1.debian.tar.xz
> dpkg-source: info: building python-smoke-zephyr in 
> python-smoke-zephyr_2.0.0-1.dsc
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/configuration.py -> 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/utilities.py -> 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/argparse_types.py -> 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/job.py -> 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/requirements.py -> 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build/smoke_zephyr
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/configuration.py -> 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/utilities.py -> 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/argparse_types.py -> 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/job.py -> 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
> copying smoke_zephyr/requirements.py -> 
> /<>/.pybuild/cpython3_3.8_smoke-zephyr/build/smoke_zephyr
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd 
> /<>/.pybuild/cpython3_3.9_smoke-zephyr/build; python3.9 -m 
> unittest discover -v -s /<>/tests -p "[a-z]*.py"
> test_bin_b64_type (argparse_types.ArgparseTypeTests) ... ok
> test_bin_hex_type (argparse_types.ArgparseTypeTests) ... ok
> test_dir_type (argparse_types.ArgparseTypeTests) ... ok
> test_log_level_type (argparse_types.ArgparseTypeTests) ... ok
> test_port_type (argparse_types.ArgparseTypeTests) ... ok
> test_timespan_type (argparse_types.ArgparseTypeTests) ... ok
> test_job_add (job.JobManagerTests) ... ok
> test_job_delete (job.JobManagerTests) ... ok
> test_job_disable (job.JobManagerTests) ... ok
> test_job_init (job.JobManagerTests) ... ok
> test_job_request_delete (job.JobManagerTests) ... ok
> test_job_run (job.JobManagerTest

Bug#973217: python-fedora: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13

[Lucas Nussbaum]

Source: python-fedora
Version: 0.10.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> file flask_fas.py (for module flask_fas) not found
> copying flask_fas_openid.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build
> creating /<>/.pybuild/cpython3_3.9_fedora/build/tests
> copying tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/tests
> copying tests/test_urlutils.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/tests
> creating /<>/.pybuild/cpython3_3.9_fedora/build/fedora
> copying fedora/iterutils.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora
> copying fedora/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora
> copying fedora/urlutils.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora
> copying fedora/textutils.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora
> copying fedora/release.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora
> creating /<>/.pybuild/cpython3_3.9_fedora/build/tests/functional
> copying tests/functional/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/tests/functional
> copying tests/functional/test_openidbaseclient.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/tests/functional
> copying tests/functional/functional_test_utils.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/tests/functional
> creating /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg2
> copying fedora/tg2/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg2
> copying fedora/tg2/utils.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg2
> creating /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/openidproxyclient.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/baseclient.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/openidbaseclient.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/proxyclient.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/bodhi.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/fas2.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/fasproxy.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/wiki.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/openidcclient.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> creating /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/tg1utils.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/controllers.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/tg2utils.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/widgets.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/json.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/util.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/client.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/utils.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> creating /<>/.pybuild/cpython3_3.9_fedora/build/fedora/wsgi
> copying fedora/wsgi/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/wsgi
> copying fedora/wsgi/csrf.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/wsgi
> creating /<>/.pybuild/cpython3_3.9_fedora/build/fedora/django
> copying fedora/django/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/django
> creating 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg2/templates
> copying fedora/tg2/templates/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg2/templates
> creating 
> /<>/.pybuild/cpython3_3.9

Bug#973236: neo: FTBFS: AttributeError: 'NoneType' object has no attribute 'supported_objects'

[Lucas Nussbaum]

Source: neo
Version: 0.7.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> py3versions: no X-Python3-Version in control file, using supported versions
> set -e; for PY in python3.9 python3.8; do \
> [ ${PY#*.} -ge 7 ] || { echo "Skipping $PY - absent support in neo's 
> tests"; continue; }; \
> echo "I: Running Neo unittests using $PY"; \
> NOSETESTS_NO_NETWORK=1 $PY -m nose -s -v neo ;\
> done
> I: Running Neo unittests using python3.9
> /<>/neo/rawio/tdtrawio.py:117: SyntaxWarning: "is not" with a 
> literal. Did you mean "!="?
>   if self.sortname is not '':
> test_read_all (neo.rawio.tests.test_axographrawio.TestAxographRawIO) ... 
> SKIP: Requires download of data from the web
> test_read_all (neo.rawio.tests.test_axonrawio.TestAxonRawIO) ... SKIP: 
> Requires download of data from the web
> test_read_raw_protocol (neo.rawio.tests.test_axonrawio.TestAxonRawIO) ... 
> SKIP: Requires download of data from the web
> test_read_all (neo.rawio.tests.test_bci2000rawio.TestBCI2000RawIO) ... SKIP: 
> Requires download of data from the web
> This test compares the output of ReachGraspIO.read_block() with the ... SKIP: 
> requires scipy
> This test compares the output of ReachGraspIO.read_block() with the ... SKIP: 
> requires scipy
> test_read_all (neo.rawio.tests.test_blackrockrawio.TestBlackrockRawIO) ... 
> SKIP: Requires download of data from the web
> test_read_all (neo.rawio.tests.test_brainvisionrawio.TestBrainVisionRawIO) 
> ... SKIP: Requires download of data from the web
> test_read_all (neo.rawio.tests.test_elanrawio.TestElanRawIO) ... SKIP: 
> Requires download of data from the web
> test_read_all (neo.rawio.tests.test_examplerawio.TestExampleRawIO) ... SKIP: 
> Requires download of data from the web
> test_read_all (neo.rawio.tests.test_intanrawio.TestIntanRawIO) ... SKIP: 
> Requires download of data from the web
> test_read_all (neo.rawio.tests.test_micromedrawio.TestMicromedRawIO) ... 
> SKIP: Requires download of data from the web
> test_read_all (neo.rawio.tests.test_neuralynxrawio.TestNeuralynxRawIO) ... 
> SKIP: Requires download of data from the web
> test_read_all 
> (neo.rawio.tests.test_neuroexplorerrawio.TestNeuroExplorerRawIO) ... SKIP: 
> Requires download of data from the web
> test_read_all (neo.rawio.tests.test_neuroscoperawio.TestNeuroScopeRawIO) ... 
> SKIP: Requires download of data from the web
> test_read_all (neo.rawio.tests.test_nixrawio.TestNixRawIO) ... SKIP: Requires 
> download of data from the web
> test_raise_error_if_discontinuous_files 
> (neo.rawio.tests.test_openephysrawio.TestOpenEphysRawIO) ... SKIP: Requires 
> download of data from the web
> test_raise_error_if_strange_timestamps 
> (neo.rawio.tests.test_openephysrawio.TestOpenEphysRawIO) ... SKIP: Requires 
> download of data from the web
> test_read_all (neo.rawio.tests.test_openephysrawio.TestOpenEphysRawIO) ... 
> SKIP: Requires download of data from the web
> test_read_all (neo.rawio.tests.test_plexonrawio.TestPlexonRawIO) ... SKIP: 
> Requires download of data from the web
> test_read_all 
> (neo.rawio.tests.test_rawbinarysignalrawio.TestRawBinarySignalRawIO) ... 
> SKIP: Requires download of data from the web
> test_read_all (neo.rawio.tests.test_rawmcsrawio.TestRawMCSRawIO) ... SKIP: 
> Requires download of data from the web
> test_read_all (neo.rawio.tests.test_spike2rawio.TestSpike2RawIO) ... SKIP: 
> Requires download of data from the web
> test_read_all (neo.rawio.tests.test_tdtrawio.TestTdtRawIO) ... SKIP: Requires 
> download of data from the web
> test_read_all (neo.rawio.tests.test_winedrrawio.TestWinEdrRawIO) ... SKIP: 
> Requires download of data from the web
> test_read_all (neo.rawio.tests.test_winwcprawio.TestWinWcpRawIO) ... SKIP: 
> Requires download of data from the web
> test_assert_readed_neo_object_is_compliant 
> (neo.test.iotest.test_alphaomegaio.TestAlphaOmegaIO) ... SKIP: Requires 
> download of data from the web
> test_load_lazy_objects (neo.test.iotest.test_alphaomegaio.TestAlphaOmegaIO) 
> ... SKIP: Requires download of data from the web
> test_read_then_write (neo.test.iotest.test_alphaomegaio.TestAlphaOmegaIO) ... 
> SKIP: Requires download of data from the web
> test_readed_with_lazy_is_compliant 
> (neo.test.iotest.test_alphaomegaio.TestAlphaOmegaIO) ... SKIP: Requires 
> download of data from the web
> test_write_then_read (neo.test.iotest.test_alphaomegaio.TestAlphaOmegaIO) ... 
> SKIP: Requires download of data from the web
> test_assert_

Bug#973223: ktorrent: FTBFS: ./obj-x86_64-linux-gnu/plugins/mediaplayer/./plugins/mediaplayer/playlist.cpp:153: undefined reference to `TagLib::String::~String()'

[Lucas Nussbaum]

Source: ktorrent
Version: 5.2.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /usr/bin/ld: CMakeFiles/ktorrent_mediaplayer.dir/playlist.cpp.o: in function 
> `kt::PlayList::data(QModelIndex const&, int) const':
> ./obj-x86_64-linux-gnu/plugins/mediaplayer/./plugins/mediaplayer/playlist.cpp:153:
>  undefined reference to `TagLib::String::~String()'
> /usr/bin/ld: 
> ./obj-x86_64-linux-gnu/plugins/mediaplayer/./plugins/mediaplayer/playlist.cpp:122:
>  undefined reference to `TagLib::String::~String()'
> /usr/bin/ld: 
> ./obj-x86_64-linux-gnu/plugins/mediaplayer/./plugins/mediaplayer/playlist.cpp:154:
>  undefined reference to `TagLib::String::~String()'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/ktorrent_5.2.0-1_unstable.log

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

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

Bug#973240: chromium: APNGs flicker

[Nick Lewycky]

Package: chromium
Version: 83.0.4103.116-3.1
Severity: normal

See upstream bug: 
https://bugs.chromium.org/p/chromium/issues/detail?id=1142228 .


This does not occur with Google Chrome, but it does occur with Debian's 
Chromium.


Also tested the version in experimental which has the same problem. This 
is not a new problem for me, I'm only finally getting around to filing bugs.


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

Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-3-amd64 (SMP w/24 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: default

Versions of packages chromium depends on:
ii  chromium-common  83.0.4103.116-3.1
ii  libasound2   1.2.3.2-1
ii  libatk-bridge2.0-0   2.38.0-1
ii  libatk1.0-0  2.36.0-2
ii  libatspi2.0-0    2.38.0-2
ii  libavcodec58 7:4.3.1-5
ii  libavformat58    7:4.3.1-5
ii  libavutil56  7:4.3.1-5
ii  libc6    2.31-4
ii  libcairo2    1.16.0-4
ii  libcups2 2.3.3-3
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  libexpat1    2.2.10-1
ii  libflac8 1.3.3-1
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.2+dfsg-4
ii  libgbm1  20.2.1-1
ii  libgcc-s1    10.2.0-15
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-5
ii  libglib2.0-0 2.66.1-2
ii  libgtk-3-0   3.24.23-2
ii  libharfbuzz0b    2.6.7-1
ii  libicu67 67.1-4
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.29-1
ii  libnss3  2:3.58-1
ii  libopenjp2-7 2.3.1-1
ii  libopus0 1.3.1-0.1
ii  libpango-1.0-0   1.46.2-1
ii  libpangocairo-1.0-0  1.46.2-1
ii  libpng16-16  1.6.37-3
ii  libpulse0    13.0-5
ii  libre2-8 20201001+dfsg-1
ii  libsnappy1v5 1.1.8-1
ii  libstdc++6   10.2.0-15
ii  libvpx6  1.8.2-1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux2    0.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libx11-6 2:1.6.12-1
ii  libx11-xcb1  2:1.6.12-1
ii  libxcb-dri3-0    1.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-6.1
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.1

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

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

Versions of packages chromium-common recommends:
ii  chromium-sandbox   83.0.4103.116-3.1
ii  fonts-liberation   1:1.07.4-11
ii  gnome-flashback [notification-daemon]  3.38.0-1
ii  libgl1-mesa-dri    20.2.1-1
ii  libu2f-udev    1.1.10-1.1
ii  notification-daemon    3.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-4

-- no debconf information

Bug#973219: python-murano-pkg-check: FTBFS: make[1]: pyversions: No such file or directory

[Lucas Nussbaum]

Source: python-murano-pkg-check
Version: 0.3.0-6
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_test --no-py2
> + PKGOS_USE_PY2=yes
> + PKGOS_USE_PY3=yes
> + PKGOS_TEST_PARALLEL=yes
> + PKGOS_TEST_SERIAL=no
> + PYTHONS=disabled
> + PYTHON3S=disabled
> + TEST_PARALLEL_OPT=--parallel
> + TEST_SERIAL_OPT=
> + PKGOS_USE_PY2=no
> + shift
> + [ no = yes ]
> + [ yes = yes ]
> + py3versions -vr
> + PYTHON3S=3.9 3.8
> + [ yes = no ]
> + [ no = yes ]
> + [ disabled = disabled ]
> + continue
> + [ 3.9 = disabled ]
> + echo 3.9
> + cut -d. -f1
> + PYMAJOR=3
> + echo ===> Testing with python (python3)
> ===> Testing with python (python3)
> + [ 3 = 3 ]
> + pwd
> + [ -d /<>/debian/tmp/usr/lib/python3/dist-packages ]
> + [ -e .stestr.conf ]
> + [ -e .testr.conf ]
> + [ -x /usr/bin/testr-python3 ]
> + TESTR=testr
> + rm -rf .testrepository
> + testr init
> + mktemp -t
> + TEMP_REZ=/tmp/tmp.SLqI2h7pqi
> + PYTHON=python3.9 testr run --parallel --subunit
> + tee /tmp/tmp.SLqI2h7pqi
> + subunit2pyunit
> /<>/muranopkgcheck/tests/functional/test_cases.py:79: 
> YAMLLoadWarning: calling yaml.load_all() without Loader=... is deprecated, as 
> the default Loader is unsafe. Please read https://msg.pyyaml.org/load for 
> full details.
>   cases.extend(list(yaml.load_all(f)))
> Non-zero exit code (2) from test listing.
> running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
> OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
> OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-60} \
> ${PYTHON:-python} -m subunit.run discover -t ./ . --list 
> --- import errors ---
> Failed to import test module: muranopkgcheck.tests.test_error
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
> _find_test_path
> module = self._get_module_from_name(name)
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/muranopkgcheck/tests/test_error.py", line 15, in 
> 
> import mock
> ModuleNotFoundError: No module named 'mock'
> 
> Failed to import test module: muranopkgcheck.tests.test_log
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
> _find_test_path
> module = self._get_module_from_name(name)
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/muranopkgcheck/tests/test_log.py", line 15, in 
> 
> import mock
> ModuleNotFoundError: No module named 'mock'
> 
> Failed to import test module: muranopkgcheck.tests.test_manager
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
> _find_test_path
> module = self._get_module_from_name(name)
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/muranopkgcheck/tests/test_manager.py", line 15, in 
> 
> import mock
> ModuleNotFoundError: No module named 'mock'
> 
> Failed to import test module: muranopkgcheck.tests.test_manifest_validator
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
> _find_test_path
> module = self._get_module_from_name(name)
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/muranopkgcheck/tests/test_manifest_validator.py", 
> line 16, in 
> import mock
> ModuleNotFoundError: No module named 'mock'
> 
> Failed to import test module: muranopkgcheck.tests.test_muranopl_validator
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
> _find_test_path
> module = self._get_module_from_name(name)
>   File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/muranopkgcheck/tests/test_muranopl_validator.py", 
> line 16, in 
> import mock
> ModuleNotFoundError: No modu

Bug#973228: websploit: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13

[Lucas Nussbaum]

Source: websploit
Version: 4.0.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package websploit
> dpkg-buildpackage: info: source version 4.0.4-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by SZ Lin (林上智) 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.9_websploit/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
> I: pybuild base:217: python3.8 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.8_websploit/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building websploit using existing 
> ./websploit_4.0.4.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building websploit in websploit_4.0.4-1.debian.tar.xz
> dpkg-source: info: building websploit in websploit_4.0.4-1.dsc
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_websploit/build/websploit
> copying websploit/websploit.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit
> copying websploit/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit
> creating 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/ezcolor
> copying websploit/ezcolor/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/ezcolor
> creating 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/modules
> copying websploit/modules/wifi_fap.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/modules
> copying websploit/modules/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/modules
> copying websploit/modules/wifi_fap_spam.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/modules
> copying websploit/modules/http_sniffer.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/modules
> copying websploit/modules/scan_network.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/modules
> copying websploit/modules/wifi_deauth.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/modules
> copying websploit/modules/scan_wifi.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/modules
> copying websploit/modules/arp_spoof.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/modules
> creating /<>/.pybuild/cpython3_3.9_websploit/build/websploit/core
> copying websploit/core/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/core
> creating 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/core/base
> copying websploit/core/base/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/core/base
> copying websploit/core/base/Base.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/core/base
> creating 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/core/utils
> copying websploit/core/utils/output.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/core/utils
> copying websploit/core/utils/about.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/core/utils
> copying websploit/core/utils/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_websploit/build/websploit/core/utils
> copying websploit/core/utils/version.py -

Bug#973216: kio-extras: FTBFS: ld: CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:(.data.rel.ro._ZTIN6TagLib4RIFF4AIFF7FileExtE[_ZTIN6TagLib4RIFF4AIFF7FileExtE]+0x10): undefined reference to `typein

[Lucas Nussbaum]

Source: kio-extras
Version: 4:19.12.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /usr/bin/ld: 
> CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:/usr/include/c++/10/bits/stl_function.h:386:
>  more undefined references to 
> `TagLib::ByteVector::operator<(TagLib::ByteVector const&) const' follow
> /usr/bin/ld: 
> CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:(.data.rel.ro._ZTIN6TagLib4RIFF4AIFF7FileExtE[_ZTIN6TagLib4RIFF4AIFF7FileExtE]+0x10):
>  undefined reference to `typeinfo for TagLib::RIFF::AIFF::File'
> /usr/bin/ld: 
> CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:(.data.rel.ro._ZTVN6TagLib4RIFF4AIFF7FileExtE[_ZTVN6TagLib4RIFF4AIFF7FileExtE]+0x20):
>  undefined reference to `TagLib::RIFF::AIFF::File::tag() const'
> /usr/bin/ld: 
> CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:(.data.rel.ro._ZTVN6TagLib4RIFF4AIFF7FileExtE[_ZTVN6TagLib4RIFF4AIFF7FileExtE]+0x28):
>  undefined reference to `TagLib::RIFF::AIFF::File::audioProperties() const'
> /usr/bin/ld: 
> CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:(.data.rel.ro._ZTVN6TagLib4RIFF4AIFF7FileExtE[_ZTVN6TagLib4RIFF4AIFF7FileExtE]+0x30):
>  undefined reference to `TagLib::RIFF::AIFF::File::save()'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/kio-extras_19.12.3-1_unstable.log

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

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

Bug#973234: weechat-el: FTBFS: Symbol’s function definition is void: rx-form

[Lucas Nussbaum]

Source: weechat-el
Version: 0.5.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> sed -e s/@VERSION@/0.5.0/ weechat-pkg.el.in > weechat-pkg.el
> Creating documentation: README.html
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> Package cl is deprecated
> Creating package tarball weechat-0.5.0.tar
> weechat Version: 0.5.0
> make[2]: Leaving directory '/<>'
> make[1]: Leaving directory '/<>'
>dh_elpa_test
>   emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list 
> \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list 
> 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f 
> package-initialize -L . -l weechat-test.el --eval 
> \(ert-run-tests-batch-and-exit\)
> Symbol’s function definition is void: rx-form
> dh_elpa_test: error: emacs -batch -Q -l package --eval "(add-to-list 
> 'package-directory-list \"/usr/share/emacs/site-lisp/elpa\")" --eval 
> "(add-to-list 'package-directory-list 
> \"/usr/share/emacs/site-lisp/elpa-src\")" -f package-initialize -L . -l 
> weechat-test.el --eval \(ert-run-tests-batch-and-exit\) returned exit code 255
> make: *** [debian/rules:5: build] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/weechat-el_0.5.0-3_unstable.log

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

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

Bug#973226: python-django-celery-beat: FTBFS: ModuleNotFoundError: No module named 'celery.five'

[Lucas Nussbaum]

Source: python-django-celery-beat
Version: 1.1.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/apps.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/models.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/schedulers.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/managers.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/admin.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/utils.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> creating 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0003_auto_20161209_0049.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0006_auto_20180210_1226.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0004_auto_20170221_.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying 
> django_celery_beat/migrations/0005_add_solarschedule_events_choices.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0002_auto_20161118_0346.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0001_initial.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/apps.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/models.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/schedulers.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/managers.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/admin.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/utils.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat
> creating 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0003_auto_20161209_0049.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0006_auto_20180210_1226.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0004_auto_20170221_.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat/migrations
> copying 
> django_celery_beat/migrations/0005_add_solarschedule_events_choices.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0002_auto_20161118_0346.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-beat/build/django_celery_beat/migrations
> copying django_c

Bug#973230: cura: FTBFS: plugins/Toolbox/src/AuthorsModel.py:71: error: Argument "key" to "sort" of "list" has incompatible type "Callable[[Dict[str, Union[str, List[str], int, None]]], Union[str, Lis

[Lucas Nussbaum]

Source: cura
Version: 4.7.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process -j4
> Test project /<>/obj-x86_64-linux-gnu
>   Start  1: invalid-imports
>   Start  2: pytest-main
>   Start  3: pytest-FirmwareUpdateChecker
>   Start  4: pytest-LegacyProfileReader
>  1/14 Test  #1: invalid-imports ..   Passed0.13 sec
>   Start  5: pytest-PostProcessingPlugin
>  2/14 Test  #3: pytest-FirmwareUpdateChecker .   Passed0.69 sec
>   Start  6: pytest-VersionUpgrade25to26
>  3/14 Test  #4: pytest-LegacyProfileReader ...   Passed0.73 sec
>   Start  7: pytest-VersionUpgrade26to27
>  4/14 Test  #6: pytest-VersionUpgrade25to26 ..   Passed0.29 sec
>   Start  8: pytest-VersionUpgrade27to30
>  5/14 Test  #7: pytest-VersionUpgrade26to27 ..   Passed0.27 sec
>   Start  9: pytest-VersionUpgrade34to35
>  6/14 Test  #8: pytest-VersionUpgrade27to30 ..   Passed0.29 sec
>   Start 10: pytest-VersionUpgrade43to44
>  7/14 Test  #9: pytest-VersionUpgrade34to35 ..   Passed0.26 sec
>   Start 11: pytest-VersionUpgrade44to45
>  8/14 Test  #5: pytest-PostProcessingPlugin ..   Passed1.17 sec
>   Start 12: pytest-XmlMaterialProfile
>  9/14 Test #10: pytest-VersionUpgrade43to44 ..   Passed0.26 sec
>   Start 13: code-style
> 10/14 Test #11: pytest-VersionUpgrade44to45 ..   Passed0.28 sec
>   Start 14: shortcut-keys
> 11/14 Test #14: shortcut-keys    Passed0.26 sec
> 12/14 Test #12: pytest-XmlMaterialProfile    Passed1.18 sec
> 13/14 Test #13: code-style ...***Failed   21.02 sec
> Success: no issues found in 4 source files
> Success: no issues found in 162 source files
> Success: no issues found in 2 source files
> Success: no issues found in 3 source files
> Success: no issues found in 7 source files
> Success: no issues found in 2 source files
> Success: no issues found in 5 source files
> Success: no issues found in 2 source files
> Success: no issues found in 7 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 5 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 3 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 5 source files
> Success: no issues found in 3 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 6 source files
> Success: no issues found in 5 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> plugins/Toolbox/src/AuthorsModel.py:71: error: Argument "key" to "sort" of 
> "list" has incompatible type "Callable[[Dict[str, Union[str, List[str], int, 
> None]]], Union[str, List[str], int, None]]"; expected "Callable[[Dict[str, 
> Union[str, List[str], int, None]]], _SupportsLessThan]"
> plugins/Toolbox/src/AuthorsModel.py:71: error: Incompatible return value type 
> (got "Union[str, List[str], int, None]", expected "_SupportsLessThan")
> Success: no issues found in 2 source files
> Found 2 errors in 1 file (checked 17 source files)
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 53 source files
> Success: no issues found in 10 source files
> Success: no issues found in 3 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 5 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no issues found in 2 source files
> Success: no is

Bug#973227: dh-cmake: FTBFS: AttributeError: 'Changelog' object has no attribute 'get_version'

[Lucas Nussbaum]

Source: dh-cmake
Version: 0.6
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package dh-cmake
> dpkg-buildpackage: info: source version 0.6
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Alastair McKinstry 
> 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean  --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py clean 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 28, in 
> version=debian_version_to_python_version(get_current_version()),
>   File "/<>/setup.py", line 17, in get_current_version
> return str(changelog.get_version())
> AttributeError: 'Changelog' object has no attribute 'get_version'
> E: pybuild pybuild:352: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.9 3.8" 
> returned exit code 13
> make: *** [debian/rules:6: clean] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/dh-cmake_0.6_unstable.log

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

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

Bug#973241: network-manager: is crda still recommendable?

[Patrice Duroux]

Package: network-manager
Version: 1.27.91-1
Severity: minor

Dear Maintainer,

First I read this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972994

Then I checked this:
https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/crda.git/tree/README

Finally I do this:
> LANG=C apt rdepends crda
crda
Reverse Depends:
  Recommends: network-manager
crda:i386
  Suggests: wireless-regdb
crda:i386


Stretch has Linux 4.9 < 4.15
Buster has Linux 4.19 > 4.15

But network-manager does not have the same version for both.
So should the recommendation be deleted?

I hope this is not a fake notification. ;-)

Best,
Patrice



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

Kernel: Linux 5.9.0-1-amd64 (SMP w/12 CPU threads)
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 network-manager depends on:
ii  adduser  3.118
ii  dbus 1.12.20-1
ii  libaudit11:2.8.5-3.1
ii  libbluetooth35.55-1
ii  libc62.31-4
ii  libcurl3-gnutls  7.72.0-1
ii  libglib2.0-0 2.66.1-2
ii  libgnutls30  3.6.15-4
ii  libjansson4  2.13.1-1
ii  libmm-glib0  1.14.6-0.1
ii  libndp0  1.6-1+b1
ii  libnewt0.52  0.52.21-4+b2
ii  libnm0   1.27.91-1
ii  libpam-systemd   246.6-2
ii  libpsl5  0.21.0-1.1
ii  libreadline8 8.0-4
ii  libselinux1  3.1-2+b1
ii  libsystemd0  246.6-2
ii  libteamdctl0 1.31-1
ii  libudev1 246.6-2
ii  libuuid1 2.36-3+b1
ii  policykit-1  0.105-29
ii  udev 246.6-2
ii  wpasupplicant2:2.9.0-15

Versions of packages network-manager recommends:
pn  crda 
ii  dnsmasq-base [dnsmasq-base]  2.82-1
ii  iptables 1.8.5-3
ii  modemmanager 1.14.6-0.1
ii  ppp  2.4.7-2+4.1+deb10u1+b1

Versions of packages network-manager suggests:
ii  isc-dhcp-client  4.4.1-2.1+b2
pn  libteam-utils

-- no debconf information

Bug#973232: minexpert2: FTBFS: ProgramWindow.cpp:2318:58: error: no matching function for call to ‘pappso::ColorMapPlotConfig::ColorMapPlotConfig(pappso::DataKind&, pappso::DataKind, std::size_t, std:

[Lucas Nussbaum]

Source: minexpert2
Version: 7.2.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> cd /<>/debian/build/src && /usr/bin/c++ 
> -DQCUSTOMPLOT_USE_LIBRARY -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG 
> -DQT_NO_DEBUG_OUTPUT -DQT_PRINTSUPPORT_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB 
> -DQT_XML_LIB -I/<>/debian/build/src -I/<>/src 
> -I/<>/debian/build/src/minexpert2_autogen/include 
> -I/<>/debian/build -I/<> -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
> /usr/include/IsoSpec++ -isystem /usr/include/pappsomspp -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fopenmp -O3 -DNDEBUG   -Wno-unknown-pragmas -Wall 
> -pedantic -Wextra -fPIC -std=gnu++17 -o 
> CMakeFiles/minexpert2.dir/gui/ProgramWindow.cpp.o -c 
> /<>/src/gui/ProgramWindow.cpp
> /<>/src/gui/ProgramWindow.cpp: In member function ‘void 
> msxps::minexpert::ProgramWindow::finishedIntegratingQualifiedMassSpectrumVectorToDtRtMz(msxps::minexpert::QualifiedMassSpectrumVectorMassDataIntegrator*)’:
> /<>/src/gui/ProgramWindow.cpp:2318:58: error: no matching 
> function for call to 
> ‘pappso::ColorMapPlotConfig::ColorMapPlotConfig(pappso::DataKind&, 
> pappso::DataKind, std::size_t, std::size_t, double, double, double, double)’
>  2318 | qualified_mass_spectra_integrator->getColorMapMaxMz());
>   |  ^
> In file included from /<>/src/gui/BaseColorMapPlotWnd.hpp:44,
>  from 
> /<>/src/gui/DriftSpecMassSpecColorMapWnd.hpp:46,
>  from /<>/src/gui/ProgramWindow.hpp:71,
>  from /<>/src/gui/ProgramWindow.cpp:63:
> /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:42:3: note: 
> candidate: ‘pappso::ColorMapPlotConfig::ColorMapPlotConfig(pappso::DataKind, 
> pappso::DataKind, pappso::AxisScale, pappso::AxisScale, pappso::AxisScale, 
> std::size_t, std::size_t, double, double, double, double)’
>42 |   ColorMapPlotConfig(DataKind x_axis_data_kind,
>   |   ^~
> /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:42:3: note:   
> candidate expects 11 arguments, 8 provided
> /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:40:3: note: 
> candidate: ‘pappso::ColorMapPlotConfig::ColorMapPlotConfig()’
>40 |   ColorMapPlotConfig();
>   |   ^~
> /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:40:3: note:   
> candidate expects 0 arguments, 8 provided
> /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:22:23: note: 
> candidate: ‘constexpr pappso::ColorMapPlotConfig::ColorMapPlotConfig(const 
> pappso::ColorMapPlotConfig&)’
>22 | struct PMSPP_LIB_DECL ColorMapPlotConfig
>   |   ^~
> /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:22:23: note:   
> candidate expects 1 argument, 8 provided
> /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:22:23: note: 
> candidate: ‘constexpr 
> pappso::ColorMapPlotConfig::ColorMapPlotConfig(pappso::ColorMapPlotConfig&&)’
> /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:22:23: note:   
> candidate expects 1 argument, 8 provided
> /<>/src/gui/ProgramWindow.cpp: In member function ‘void 
> msxps::minexpert::ProgramWindow::finishedIntegratingQualifiedMassSpectrumVectorToRtDt(msxps::minexpert::QualifiedMassSpectrumVectorMassDataIntegrator*)’:
> /<>/src/gui/ProgramWindow.cpp:2571:58: error: no matching 
> function for call to 
> ‘pappso::ColorMapPlotConfig::ColorMapPlotConfig(pappso::DataKind&, 
> pappso::DataKind, std::size_t, std::size_t, double, double, double, double)’
>  2571 | qualified_mass_spectra_integrator->getColorMapMaxMz());
>   |  ^
> In file included from /<>/src/gui/BaseColorMapPlotWnd.hpp:44,
>  from 
> /<>/src/gui/DriftSpecMassSpecColorMapWnd.hpp:46,
>  from /<>/src/gui/ProgramWindow.hpp:71,
>  from /<>/src/gui/Progr

Bug#973238: typedload: FTBFS: typedload/datadumper.py:159: error: NotImplemented? not callable

[Lucas Nussbaum]

Source: typedload
Version: 2.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> mypy --config-file mypy.conf typedload
> typedload/datadumper.py:159: error: NotImplemented? not callable
> Found 1 error in 1 file (checked 5 source files)
> make[2]: *** [Makefile:9: mypy] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/typedload_2.2-1_unstable.log

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

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

Bug#973220: node-libnpx: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 123

[Lucas Nussbaum]

Source: node-libnpx
Version: 10.2.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> tail -n +2 README.md | marked-man --manual 'User Commands' --version 
> libnpx@$(dpkg-parsechangelog -S version) > libnpx.1
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/libnpx
>   /bin/sh -ex debian/tests/pkg-js/test
> + export LANG=C
> + export NODE_PATH=node_modules
> + pwd
> + export HOME=/<>
> + ls test/auto-fallback.js test/child.js test/get-prefix.js 
> test/guess-command-name.js test/index.js test/parse-args.js test/util.js
> + grep -v test/auto-fallback.js
> + xargs tap
> TAP version 13
> # Subtest: test/child.js
> # Subtest: escapeArg on *nix
> ok 1 - standard arg left intact
> ok 2 - '-escaped on *nix
> ok 3 - paths escaped as usual
> 1..3
> ok 1 - escapeArg on *nix # time=4.407ms
> 
> # Subtest: escapeArg on win32
> ok 1 - standard arg escaped
> ok 2 - "-escaped on win32
> ok 3 - paths escaped as usual
> 1..3
> ok 2 - escapeArg on win32 # time=1.253ms
> 
> # Subtest: exec
> ok 1 - command string concatenated
> ok 2 - options received!
> ok 3 - unix-style escapes
> ok 4 - win32-style escapes
> ok 5 - got error
> 1..5
> ok 3 - exec # time=11.291ms
> 
> # Subtest: exec (integration)
> ok 1 - node ran successfully
> ok 2 - got the exit code from subproc
> 1..2
> ok 4 - exec (integration) # time=149.221ms
> 
> # Subtest: spawn
> ok 1 - should be equivalent
> ok 2 - got the exit code from
> 1..2
> ok 5 - spawn # time=174.839ms
> 
> # Subtest: runCommand with command arg
> ok 1 - should be equivalent
> ok 2 - got the exit code from subproc
> ok 3 - error message reports ENOENT
> ok 4 - "not found" has code 127
> 1..4
> ok 6 - runCommand with command arg # time=152.75ms
> 
> # Subtest: runCommand with opts.command
> ok 1 - should be equivalent
> 1..1
> ok 7 - runCommand with opts.command # time=85.887ms
> 
> # Subtest: runCommand with opts.call and opts.shell
> ok 1 - should be equivalent
> 1..1
> ok 8 - runCommand with opts.call and opts.shell # time=68.64ms
> 
> 1..8
> # time=657.906ms
> ok 1 - test/child.js # time=828.454ms
> 
> # Subtest: test/get-prefix.js
> /usr/share/nodejs/tap/lib/extra-from-error.js:6
> if (!(k in set) && !/^tapChild/.test(k))
> ^
> 
> TypeError: Cannot use 'in' operator to search for 'name' in uncaughtException
> at /usr/share/nodejs/tap/lib/extra-from-error.js:6:13
> at Array.reduce ()
> at module.exports (/usr/share/nodejs/tap/lib/extra-from-error.js:5:38)
> at TAP.threw (/usr/share/nodejs/tap/lib/test.js:658:15)
> at process.emit (events.js:326:22)
> at process.emit 
> (/usr/share/nodejs/source-map-support/source-map-support.js:495:21)
> at processEmit [as emit] (/usr/share/nodejs/signal-exit/index.js:161:32)
> at process._fatalException (internal/process/execution.js:165:25)
> 1..0 # no tests found
> not ok 2 - test/get-prefix.js # time=190.364ms
>   ---
>   timeout: 3
>   file: test/get-prefix.js
>   command: /usr/bin/node
>   args:
> - test/get-prefix.js
>   stdio:
> - 0
> - pipe
> - 2
>   cwd: /<>
>   exitCode: 7
>   ...
> 
> # Subtest: test/guess-command-name.js
> # Subtest: guesses unscoped registry binaries
> ok 1 - should be equal
> 1..1
> ok 1 - guesses unscoped registry binaries # time=24.712ms
> 
> # Subtest: guesses scoped registry binaries
> ok 1 - should be equal
> 1..1
> ok 2 - guesses scoped registry binaries # time=0.911ms
> 
> # Subtest: guesses hosted git binaries
> ok 1 - should be equal
> ok 2 - should be equal
> 1..2
> ok 3 - guesses hosted git binaries # time=5.405ms
> 
> # Subtest: guesses git binaries
> ok 1 - should be equal
> ok 2 - should be equal
> 1..2
> ok 4 - guesses git binaries # time=1.544ms
> 
> # Subtest: leaves local directory/file commands intact
> ok 1 - should be equal
> ok 2 - should be

Bug#973221: soundkonverter: FTBFS: MetaReplayGain.h:25:10: fatal error: fileref.h: No such file or directory

[Lucas Nussbaum]

Source: soundkonverter
Version: 3.0.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/plugins/soundkonverter_codec_lame && 
> /usr/bin/c++ -DKCOREADDONS_LIB -DKGUIADDONS_LIB -DQT_CONCURRENT_LIB 
> -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_GUI_LIB 
> -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB 
> -DQT_XML_LIB -DSOUNDKONVERTER_KF5_BUILD -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
> -Dsoundkonverter_codec_lame_EXPORTS 
> -I/<>/obj-x86_64-linux-gnu/plugins/soundkonverter_codec_lame 
> -I/<>/src/plugins/soundkonverter_codec_lame 
> -I/<>/obj-x86_64-linux-gnu/plugins/soundkonverter_codec_lame/soundkonverter_codec_lame_autogen/include
>  -I/<>/obj-x86_64-linux-gnu -I/<>/src -isystem 
> /usr/include/KF5/KWidgetsAddons -isystem /usr/include/KF5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
> /usr/include/KF5/KIOFileWidgets -isystem /usr/include/KF5/KIOWidgets -isystem 
> /usr/include/KF5/KIOGui -isystem /usr/include/KF5/KIOCore -isystem 
> /usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KService -isystem 
> /usr/include/KF5/KConfigCore -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
> /usr/include/KF5/KWindowSystem -isystem /usr/include/KF5/KJobWidgets -isystem 
> /usr/include/KF5/KCompletion -isystem /usr/include/KF5/KBookmarks -isystem 
> /usr/include/KF5/KItemViews -isystem /usr/include/KF5/KXmlGui -isystem 
> /usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs -isystem 
> /usr/include/KF5/KConfigGui -isystem /usr/include/KF5/KAuth -isystem 
> /usr/include/KF5/Solid -isystem /usr/include/KF5/KDELibs4Support -isystem 
> /usr/include/KF5/KDELibs4Support/KDE -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
> /usr/include/KF5/KCrash -isystem /usr/include/KF5/KI18n -isystem 
> /usr/include/KF5/KNotifications -isystem /usr/include/KF5/KIconThemes 
> -isystem /usr/include/KF5/KGuiAddons -isystem 
> /usr/include/KF5/KUnitConversion -isystem /usr/include/KF5/KTextWidgets 
> -isystem /usr/include/KF5/SonnetUi -isystem /usr/include/KF5/KParts -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pedantic 
> -Wno-deprecated-declarations -fno-operator-names -fno-exceptions -Wall 
> -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long 
> -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
> -Werror=return-type -Wvla -Wdate-time -Wsuggest-override -Wlogical-op -fPIC 
> -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=gnu++11 -o 
> CMakeFiles/soundkonverter_codec_lame.dir/lameconversionoptions.cpp.o -c 
> /<>/src/plugins/soundkonverter_codec_lame/lameconversionoptions.cpp
> In file included from /<>/src/configdialog/../pluginloader.h:15,
>  from /<>/src/configdialog/../config.h:10,
>  from 
> /<>/src/configdialog/configcoverartpage.cpp:4:
> /<>/src/configdialog/../core/codecplugin.h:36:21: warning: 
> ‘virtual QString CodecPlugin::type() const’ can be marked override 
> [-Wsuggest-override]
>36 | virtual QString type() const;
>   | ^~~~
> In file included from /<>/src/configdialog/../pluginloader.h:16,
>  from /<>/src/configdialog/../config.h:10,
>  from 
> /<>/src/configdialog/configcoverartpage.cpp:4:
> /<>/src/configdialog/../core/filterplugin.h:42:21: warning: 
> ‘virtual QString FilterPlugin::type() const’ can be marked override 
> [-Wsuggest-override]
>42 | virtual QString type() const;
>   | ^~~~
> In file included from /<>/src/configdialog/../pluginloader.h:17,
>  from /<>/src/configdialog/../config.h:10,
>  from 
> /<>/src/configdialog/configcoverartpage.cpp:4:
> /<>/src/configdialog/../core/replaygainplugin.h:57:21: warning: 
> ‘virtual QString ReplayGainPlugin::type() const’ can be marked override 
> [-Wsuggest-override]
>57 | virtual QString type() const;
>   | ^~~~
&