Bug#931729: apt-mirror: Use of uninitialized value $lines{"Files:"} in split at /usr/bin/apt-mirror line 829

[Philipp Hahn]

The real problem here is that process_index() assumes that "Files:" is
still used. According to Debian Policy 4.5.0.3

and 
"Files:" is still "mandatory, but reality looks different:

> $ curl -s 
> http://ftp.de.debian.org/debian/dists/buster-updates/main/source/Sources.xz | 
> xz -d | grep-dctrl -S tzdata
> Package: tzdata
> Binary: tzdata
> Version: 2019c-0+deb10u1
> Maintainer: GNU Libc Maintainers 
> Uploaders: Clint Adams , Aurelien Jarno 
> , Adam Conrad 
> Build-Depends: debhelper (>= 9)
> Build-Depends-Indep: po-debconf, rdfind, symlinks
> Architecture: all
> Standards-Version: 4.2.1
> Format: 3.0 (quilt)
> Vcs-Browser: https://salsa.debian.org/glibc-team/tzdata
> Vcs-Git: https://salsa.debian.org/glibc-team/tzdata.git
> Checksums-Sha256:
>  983c27d24d78c52d8f213b1b5800aaa90a171a4f805451b0845752f97c6f924b 2264 
> tzdata_2019c-0+deb10u1.dsc
>  79c7806dab09072308da0e3d22c37d3b245015a591891ea147d3b133b60ffc7c 392087 
> tzdata_2019c.orig.tar.gz
>  cd31deaeee229d45e4f4b973441189e7619ef81679359e9c8b47b2a87aaf6a07 833 
> tzdata_2019c.orig.tar.gz.asc
>  fa8071037767a7dfa054c26621c5079809ee038eddb32a58814faf3541d52d5a 104932 
> tzdata_2019c-0+deb10u1.debian.tar.xz
> Homepage: https://www.iana.org/time-zones
> Package-List: 
>  tzdata deb localization required arch=all
> Directory: pool/main/t/tzdata
> Priority: source
> Section: localization

As this example lacks the "Files:" entry, it is not mirrored by
"apt-mirror".

The real fix is to try "Checksums-Sha256", "Checksum-Sha1" and "Files:"
in that order and use the first existing one.

Philipp
-- 
Philipp Hahn
Open Source Software Engineer

Univention GmbH
be open.
Mary-Somerville-Str. 1
D-28359 Bremen

📞 +49-421-22232-57
🖶 +49-421-22232-99

✉️ h...@univention.de
🌐 https://www.univention.de/

Geschäftsführer: Peter H. Ganten
HRB 20755 Amtsgericht Bremen
Steuer-Nr.: 71-597-02876
From 2988f8d91dfbd97667be4224004deea85f888e66 Mon Sep 17 00:00:00 2001
Message-Id: 
<2988f8d91dfbd97667be4224004deea85f888e66.1601439012.git.h...@univention.de>
In-Reply-To: 

References: 

From: Philipp Hahn 
Date: Tue, 29 Sep 2020 12:40:43 +0200
Subject: Support SHA{1,256,512} for Sources too (closes #931729)

The real problem here is that process_index() assumes that "Files:" still used.
According to Debian Policy 4.5.0.3

and  "Files:" is
still "mandatory, but reality looks different:

> $ curl -s 
> http://ftp.de.debian.org/debian/dists/buster-updates/main/source/Sources.xz | 
> xz -d | grep-dctrl -S tzdata
> Package: tzdata
...
> Version: 2019c-0+deb10u1
...
> Standards-Version: 4.2.1
...
> Checksums-Sha256:
>  983c27d24d78c52d8f213b1b5800aaa90a171a4f805451b0845752f97c6f924b 2264 
> tzdata_2019c-0+deb10u1.dsc
>  79c7806dab09072308da0e3d22c37d3b245015a591891ea147d3b133b60ffc7c 392087 
> tzdata_2019c.orig.tar.gz
>  cd31deaeee229d45e4f4b973441189e7619ef81679359e9c8b47b2a87aaf6a07 833 
> tzdata_2019c.orig.tar.gz.asc
>  fa8071037767a7dfa054c26621c5079809ee038eddb32a58814faf3541d52d5a 104932 
> tzdata_2019c-0+deb10u1.debian.tar.xz
...

As this example lacks the "Files:" entry, it is not mirrored by "apt-mirror".

The real fix is to try "Checksums-Sha256", "Checksum-Sha1" and "Files:" in that
order and use the first existing one.
---
 apt-mirror | 76 ++
 1 file changed, 48 insertions(+), 28 deletions(-)

diff --git a/apt-mirror b/apt-mirror
index 16c2118..5d81fcf 100755
--- a/apt-mirror
+++ b/apt-mirror
@@ -720,11 +720,21 @@ foreach ( keys %urls_to_download )
 
 %urls_to_download = ();
 
-open FILES_ALL, ">" . get_variable("var_path") . "/ALL" or die("apt-mirror: 
can't write to intermediate file (ALL)");
-open FILES_NEW, ">" . get_variable("var_path") . "/NEW" or die("apt-mirror: 
can't write to intermediate file (NEW)");
-open FILES_MD5, ">" . get_variable("var_path") . "/MD5" or die("apt-mirror: 
can't write to intermediate file (MD5)");
-open FILES_SHA1, ">" . get_variable("var_path") . "/SHA1" or die("apt-mirror: 
can't write to intermediate file (SHA1)");
-open FILES_SHA256, ">" . get_variable("var_path") . "/SHA256" or 
die("apt-mirror: can't write to intermediate file (SHA256)");
+open my $FILES_ALL, ">" . get_variable("var_path") . "/ALL" or 
die("apt-mirror: can't write to intermediate file (ALL)");
+open my $FILES_NEW, ">" . get_variable("var_path") . "/NEW" or 
die("apt-mirror: can't write to intermediate file (NEW)");
+open my $FILES_MD5, ">" . get_variable("var_path") . "/MD5" or 
die("apt-mirror: can't write to intermediate file (MD5)");
+open my $FILES_SHA1, ">" . get_variable("var_path") . "/SHA1" or 
die("apt-mirror: can't write to intermediate file (SHA1)");
+open my $FILES_SHA256, ">" . get_variable("var_p

Bug#971015: RFS: vim-ultisnips/3.1-3.1 [NMU] [RC] -- snippet solution for Vim

[Tobias Frost]

Control: tags -1 moreinfo

On Sat, 26 Sep 2020 11:38:49 +0300 Nicholas Guriev  wrote:
> Package: sponsorship-requests
> Severity: important
> Control: block 938777 by -1
> X-Debbugs-CC: Debian Vim Maintainers 
> X-Debbugs-CC: Michael Fladischer 
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "vim-ultisnips":
> 
>  * Package name: vim-ultisnips
>Version : 3.1-3.1
>Upstream Author : Holger Rapp 
>  * URL : https://github.com/SirVer/ultisnips
>  * License : GPL-3+
>  * Vcs : https://salsa.debian.org/vim-team/vim-ultisnips
>Section : editors
> 
> It builds those binary packages:
> 
>   vim-ultisnips - snippet solution for Vim
> 
> To access further information about this package, please visit the following
URL:
> 
>   https://mentors.debian.net/package/vim-ultisnips/
> 
> Alternatively, one can download the package with dget using this command:
> 
>   dget -x 
https://mentors.debian.net/debian/pool/main/v/vim-ultisnips/vim-ultisnips_3.1-3.1.dsc
> 
> Or you can see diff in recently imported Git project at salsa.d.o:
> 
>   
https://salsa.debian.org/vim-team/vim-ultisnips/-/commit/01d9924e156a02d3d43d1997055a53b7405fed93
> 
> Changes since the last upload:
> 
>  vim-ultisnips (3.1-3.1) unstable; urgency=medium
>  .
(...) 
>* Move packaging repository to a new GitLab instance at salsa.debian.org.

Did you talk with the maintainer about that change and he ACKED it?

Otherwise it is inappropiate. For once, it was collab-maint before, so it should
be the Debian namespace. Also, Michael is not member of the new
repo, so he would loose access.

If you want to have it in the vim team, you need to either an ACK by Michael or
do an ITS.

-- 
tobi

Bug#942884: Bug#971395: RFS: zipios++/2.2.5.0-1 -- small C++ library for reading zip files (documents)

[Tobias Frost]

Control: reopen 942884
Control: forcemerge 942884 971395
Control: tags -1 moreinfo
# please do not reopen new bugs if the old one was not sponsored.
# -- otherwise context is lost.

On Tue, Sep 29, 2020 at 10:17:31PM +0200, François Mazen wrote:
> Changes since the last upload:
> 
>  zipios++ (2.2.5.0-1) unstable; urgency=high
(...)  .
>* Rename library package from libzipios++0v5 to libzipios2

This starts a library transision:
You need to upload it to experimental first.
See: https://wiki.debian.org/Teams/ReleaseTeam/Transitions

(Did not check the package otherwise)

--
tobi

Bug#971401: texlive-binaries: triggers update-alternatives warning for bibtex

[Hilmar Preuße]

Am 30.09.2020 um 00:09 teilte Gabriele Stilli mit:

Hi,


while configuring texlive-binaries, the following warning appeared:

update-alternatives: warning: forcing reinstallation of alternative
/usr/bin/bibtex.original because link group bibtex is broken
update-alternatives: warning: not replacing
/usr/share/man/man1/bibtex.1.gz with a link


Which version of texlive-base do you have installed?

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#971414: pcp: Error in install-docs for /usr/share/doc-base/pcp-doc

[Achim Schaefer]

Package: pcp
Version: 5.2.1-1
Severity: normal

Dear Maintainer,

during install there is an error:
LANG=C install-docs --verbose --check /usr/share/doc-base/pcp-doc
Warning in `/usr/share/doc-base/pcp-doc', line 9: file 
`/usr/share/doc/pcp-doc/html/index.html' does not exist.
Error in `/usr/share/doc-base/pcp-doc', line 9: all `Format' sections are 
invalid.
/usr/share/doc-base/pcp-doc: Fatal error found, the file won't be registered.

Thanks

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

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

Versions of packages pcp depends on:
ii  bpftrace  0.11.0-1
ii  gawk  1:5.0.1+dfsg-1
ii  libc6 2.31-3
ii  libncurses6   6.2+20200918-1
ii  libpcp-gui2   5.2.1-1
ii  libpcp-import15.2.1-1
ii  libpcp-mmv1   5.2.1-1
ii  libpcp-pmda-perl  5.2.1-1
ii  libpcp-pmda3  5.2.1-1
ii  libpcp-trace2 5.2.1-1
ii  libpcp-web1   5.2.1-1
ii  libpcp3   5.2.1-1
ii  libpfm4   4.10.1+git44-ga2909cd-1
ii  libreadline8  8.0-4
ii  libssl1.1 1.1.1g-1
hi  libsystemd0   245.7-1
ii  libtinfo6 6.2+20200918-1
ii  libuv11.39.0-1
ii  procps2:3.3.16-5
ii  python3   3.8.2-3
ii  python3-pcp   5.2.1-1

pcp recommends no packages.

Versions of packages pcp suggests:
pn  libpcp-import-perl  
pn  pcp-gui 

-- no debconf information

Bug#971409: ITP: node-prosemirror-schema-basic -- defines a basic reusable ProseMirror document schema

[Abraham Raji]

Package: wnpp
Severity: wishlist
Owner: Abraham Raji 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name    : node-prosemirror-schema-basic
  Version : 1.1.2
  Upstream Author : 2015-2017 by Marijn Haverbeke  and others
* URL : https://github.com/prosemirror/prosemirror-schema-basic
* License : Expat
  Programming Lang: JavaScript
  Description : defines a basic reusable ProseMirror document schema
This is a schema module for ProseMirror. ProseMirror is a well-behaved rich
semantic content editor based on contentEditable, with support for
collaborative editing and custom document schemas.
This module defines a basic ProseMirror document schema, whose elements can be
reused in other schemas.
.
Node.js is an event-based server-side JavaScript engine.

This package is necessary to enable tests for other existing ProseMirror
modules such as node-prosemirror-state, prosemirror-model,
prosemirror-transform etc.

I am part of the Debian JS team and with their help I will maintain this package
myself.

Abraham Raji
-- 
Mea navis aëricumbens anguillis abundant.

Bug#920365: [debian-mysql] Bug#920365: Bug#920365: mariadb_config: improve cross compilation support

[Helmut Grohne]

Hi Otto,

On Wed, Sep 30, 2020 at 12:14:20AM +0300, Otto Kekäläinen wrote:
> If I move just the header file but not all of
> /usr/include/mariadb/server, will there be issues with paths at some
> point?

Likely yes. For using these headers, you specify a custo -I flag (that
likely comes from pkg-config or something similar). You'd need to insert
another -I flag into every consumer.

> I don't have any sample program to build and test against
> libmariadbd-dev and I am not a C/C++ coder so this starts to be beyond
> my level.

You'd likely have to test this with every reverse dependency of which
there seem to be around 200.

Keep in mind however what the goal is. Whenever you think about
multiarching a -dev package, the only use case is cross building. But
most of the time, cross building never requires marking -dev packages
multiarch. It just makes it more convenient for developers. So really,
removing the M-A is a simple stop gap solution that works for 90% of the
cases.

Please spend your precious time elsewhere if possible and just drop the
M-A:same.

Helmut

Bug#933063: [debian-mysql] Bug#933063: character_set_client: latin1?

[Georg Richter]

Hi Otto,

you're right - looks like it was forgotten to add this option when building
C/C as a sunproject inside server. I fixed that now:

diff --git a/CMakeLists.txt b/CMakeLists.txt
index c85baf2..4045491 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -25,7 +25,7 @@ get_directory_property(IS_SUBPROJECT PARENT_DIRECTORY)
 SET_PROPERTY(DIRECTORY PROPERTY INCLUDE_DIRECTORIES)
 FOREACH(V WITH_MYSQLCOMPAT WITH_MSI WITH_SIGNCODE WITH_RTC WITH_UNIT_TESTS
 WITH_DYNCOL WITH_EXTERNAL_ZLIB WITH_CURL WITH_SQLITE WITH_SSL
WITH_ICONV
-INSTALL_LAYOUT WITH_TEST_SRCPKG)
+DEFAULT_CHARSET INSTALL_LAYOUT WITH_TEST_SRCPKG)
   SET(${V} ${${OPT}${V}})
 ENDFOREACH()

With this patch you should be able to specify the character set in server
build with
cmake -DCONC_DEFAULT_CHARSET=utf8mb4

/Georg

On Tue, Sep 29, 2020 at 10:41 PM Otto Kekäläinen  wrote:

> I tested this but it did not at least directly work:
>
> commit b8e537d55b467eb285a82842e73bb22732ef9ad6 (HEAD -> master-next)
> Author: Otto Kekäläinen 
> Date:   Tue Sep 29 21:27:02 2020 +0300
>
> Use build flag to enforce default charset as utf8mb4 (Closes: ##933063)
>
> diff --git a/debian/rules b/debian/rules
> index 819ac6ea0..12b162002 100755
> --- a/debian/rules
> +++ b/debian/rules
> @@ -101,6 +101,7 @@ endif
> -DSYSTEM_TYPE="debian-$(DEB_HOST_GNU_SYSTEM)" \
> -DBUILD_CONFIG=mysql_release \
> -DWITH_SSL=bundled \
> +  -DDEFAULT_CHARSET=utf8mb4 \
> -DPLUGIN_TOKUDB=NO \
> -DPLUGIN_CASSANDRA=NO \
> -DPLUGIN_AWS_KEY_MANAGEMENT=NO \
>
>
> --->
>
>
> MariaDB [(none)]> status
> --
> mariadb  Ver 15.1 Distrib 10.5.5-MariaDB, for debian-linux-gnu
> (x86_64) using readline 5.2
>
> Connection id: 76
> Current database:
> Current user: root@localhost
> SSL: Not in use
> Current pager: stdout
> Using outfile: ''
> Using delimiter: ;
> Server: MariaDB
> Server version: 10.5.5-MariaDB-2-debug Debian 10
> Protocol version: 10
> Connection: Localhost via UNIX socket
> Server characterset: utf8mb4
> Db characterset: utf8mb4
> Client characterset: latin1
> Conn.  characterset: latin1
> UNIX socket: /run/mysqld/mysqld.sock
> Uptime: 27 sec
>
> Threads: 22  Questions: 674  Slow queries: 0  Opens: 199  Open tables:
> 37  Queries per second avg: 24.962
> --
>


-- 
Georg Richter, Senior Software Engineer
MariaDB Corporation Ab

Bug#586415: ITA: tightvnc-java -- TightVNC java applet and command line program

[Ola Lundqvist]

Yay. Please go ahead.

Den tis 29 sep. 2020 20:56Mike Gabriel 
skrev:

> On  Di 29 Sep 2020 20:46:17 CEST, Sven Geuer wrote:
>
> > owner -1 debma...@g-e-u-e-r.de
> > retitle -1 ITA: tightvnc-java -- TightVNC java applet and cli program
>
> > [ ... @Ola ...]
>
> > Hi Mike,
> >
> > I'd like to maintain tightvnc-java under the umbrella of the Debian
> > Remote Packaging Team as I already do for tightvnc. Please add the
> > tightvnc-java project to the team repository as soon as Ola gave his
> > OK.
>
> Awesome! And yes, will do.
>
> > [1] https://salsa.debian.org/sven-geuer-guest/tightvnc-java
>
> Mike
>
> --
>
> DAS-NETZWERKTEAM
> c\o Technik- und Ökologiezentrum Eckernförde
> Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
> mobile: +49 (1520) 1976 148
> landline: +49 (4351) 850 8940
>
> GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
> mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
>
>

Bug#971412: libdcmtk-dev: undeclared conflict with libcharls-dev

[Steve M. Robbins]

Package: libdcmtk-dev
Version: 3.6.4-2.1+b1
Severity: normal

Dear Maintainer,

I just attempted to install libcharls-dev, which failed:

  E: /var/cache/apt/archives/libcharls-dev_2.1.0+dfsg-1_amd64.deb: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/libcharls.so', which is also in package 
libdcmtk-dev 3.6.4-2.1+b1

I would guess that libcharls-dev has a better claim to this file than 
libdcmtk-dev.  


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

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

Versions of packages libdcmtk-dev depends on:
ii  libcharls-dev  2.0.0+dfsg-1+b1
ii  libdcmtk14 3.6.4-2.1+b1
ii  libpng-dev 1.6.37-3
ii  libssl-dev 1.1.1g-1
ii  libtiff-dev4.1.0+git191117-2
ii  libwrap0-dev   7.6.q-30
ii  libxml2-dev2.9.10+dfsg-6

libdcmtk-dev recommends no packages.

Versions of packages libdcmtk-dev suggests:
pn  dcmtk-doc  

-- no debconf information

Bug#971411: libopencv-objdetect4.2: LLVM ERROR: inconsistency; Option 'polly' registered more than once!

[Chris Ruehl]

Package: libopencv-objdetect4.2
Version: 4.2.0+dfsg-6+b4
Severity: important
X-Debbugs-Cc: j...@gtsys.com.hk

Hi,
using bullseye on an arm64 to build a opencv test program for HoG the 
application
failed with following error message:

: CommandLine Error: Option 'polly' registered more than once!
LLVM ERROR: inconsistency in registered CommandLine options

code-triggers the error:
HOGDescriptor hog;
hog.winSize = _pos_image_size;
  hog.setSVMDetector(get_svm_detector(svm));
hog.save(_obj_det_filename);


I checked for this message and found some other projects hit same
problem,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965310

report is for amd64 builds, this might be duplicate but I want to
raise your attention.

Regards
Chris

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

Kernel: Linux 5.4.66-rt38 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=en_HK.UTF-8, LC_CTYPE=en_HK.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libopencv-objdetect4.2 depends on:
ii  libc6 2.31-3
ii  libgcc-s1 10.2.0-9
ii  libopencv-calib3d4.2  4.2.0+dfsg-6+b4
ii  libopencv-core4.2 4.2.0+dfsg-6+b4
ii  libopencv-highgui4.2  4.2.0+dfsg-6+b4
ii  libopencv-imgproc4.2  4.2.0+dfsg-6+b4
ii  libopencv-ml4.2   4.2.0+dfsg-6+b4
ii  libstdc++610.2.0-9

libopencv-objdetect4.2 recommends no packages.

libopencv-objdetect4.2 suggests no packages.

-- no debconf information

Bug#971027: gcc-10: regression in 10.2.0-9 causes segmentation fault in vlc

[Ahzo]

Sep 29, 2020, 07:14 by rguent...@suse.de:

> I've filed > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97236
>
> Someone needs to create a testcase or provide instructions how to
> reproduce the bug.
>

Thanks for taking care of this issue upstream.

Sep 29, 2020, 15:18 by d...@debian.org:

> On 9/29/20 12:30 PM, Matthias Klose wrote:
> upstream now has a reduced test case.
>
> 10.2.0-12 is uploaded, reverting that commit for now.
>
Thanks for the quick upload. This should prevent further fallout, until 
upstream finds a better solution.

Regards,
Ahzo

Bug#970638: FIXED: jag: cannot upgrade from 0.3.6-1 to 0.3.8-1

[Carlos Donizete Froes]

Hi Andreas,

Added in debian/control: Breaks+Replaces on jag-data.

+ Breaks: jag-data (<< 0.3.8)
+ Replaces: jag-data (<< 0.3.8)

Thanks!

-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ Debian Wiki: https://wiki.debian.org/coringao
⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
⠈⠳⣄⠀⠀⠀  2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780


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

Bug#844025: sslscan: static build

[Paul Wise]

On Sat, 2020-09-26 at 06:57 +0800, Paul Wise wrote:
> On Fri, 11 Nov 2016 22:38:31 +0100 Stefan Pietsch wrote:
> 
> > sslscan in Debian unstable does not support SSLv2 and v3.
> 
> sslscan just re-entered Debian, could you re-check this?

FTR: all of the email addresses I can find for Stefan Pietsch are no
longer valid or no longer accept email.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#971343: Animated background/wallpaper (changing over time) causes system freeze on Nouveau

[Leandro Cunha]

>
> Control: found -1 3.36.6-1
> Control: found -1 3.38.0-2
>
> This is on a GT218M GPU, which is a Tesla 2.0 device from 2007.
> https://www.notebookcheck.net/NVIDIA-GeForce-310M.22439.0.html suggests
> that this is comparable in performance to Intel integrated graphics from
> the Ivybridge (2012) generation, but probably with a much higher power
> consumption.
>
> I don't think we can necessarily treat GNOME freezing on
> more-than-10-year-old hardware as release-critical, particularly since
> there's a workaround (not using the animated background).

Gnome works well on this hardware that was on the market for years,
devices from 2011 and 2012 were still sold with this hardware is the
case with mine. Who still likes it and who knows even the rest of the
laptop. The problem may be occurring for several reasons that may not
be related to the age of the hardware. This problem only occurs in the
latest versions of Gnome.

> Some other questions I should have asked:
>
> * Are you using any GNOME Shell extensions? (If yes, please try
>   disabling them all and see whether the problem persists.)

The problem still persists.

> * Is this a new installation, or have you been using this hardware with
>   Linux for a while? If you've been using it previously, have you had
>   other graphics- or freeze-related issues with it?

Only in version 3.36.3 onwards, if I'm not mistaken. But it is the first time.

> * Has the animated/changing background worked in earlier versions of
>   Debian and/or GNOME, or is 3.36 the oldest version you've tried?

All previous versions work normally.

> * Are you able to do an installation of the Debian 10 'buster' stable
>   release on this hardware, if you haven't already tried that? That would
>   give us a baseline for whether this is a situation that has been there
>   for a while.

In the Buster (stable current) version it works normally.

> On Tue, 29 Sep 2020 at 16:48:21 -0300, Leandro Cunha wrote:
> > Graphics:
> >   Device-1: NVIDIA GT218M [GeForce 310M] driver: nouveau v: kernel
> >   Device-2: Suyin type: USB driver: uvcvideo
>
> Is this Suyin USB device an input (camera), or an output (display)?
> Is it part of the laptop, or a removable device?

I have no idea what this is.

> If it's a removable output device, please check whether this issue still
> occurs with the USB device disconnected and just the NVIDIA graphics
> device, to keep things as simple as possible.

There is only one mouse and one USB network adapter.

> Also, if you have external screens attached, please check whether it
> still occurs with just the laptop's built-in screen, again to try to
> keep things as simple as possible.
>
> > Sep 29 10:50:17 debian-pc kernel: [   60.247471] nouveau :01:00.0: 
> > firmware: failed to load nouveau/nva8_fuc084 (-2)
> > Sep 29 10:50:17 debian-pc kernel: [   60.247475] firmware_class: See 
> > https://wiki.debian.org/Firmware for information about missing firmware
> > Sep 29 10:50:17 debian-pc kernel: [   60.247478] nouveau :01:00.0: 
> > Direct firmware load for nouveau/nva8_fuc084 failed with error -2
> > Sep 29 10:50:17 debian-pc kernel: [   60.247492] nouveau :01:00.0: 
> > firmware: failed to load nouveau/nva8_fuc084d (-2)
> > Sep 29 10:50:17 debian-pc kernel: [   60.247494] nouveau :01:00.0: 
> > Direct firmware load for nouveau/nva8_fuc084d failed with error -2
> > Sep 29 10:50:17 debian-pc kernel: [   60.247497] nouveau :01:00.0: 
> > msvld: unable to load firmware data
> > Sep 29 10:50:17 debian-pc kernel: [   60.247499] nouveau :01:00.0: 
> > msvld: init failed, -19
>
> This firmware blob is not available in Debian (it seems we cannot legally
> distribute it, even in non-free, although it can be extracted from
> proprietary NVIDIA drivers) but apparently it's for 2D video encoder/decoder
> acceleration (VDPAU) rather than anything GNOME Shell would need, so this
> warning is probably harmless?

Even without it it still occurs.

> > Sep 29 10:54:53 debian-pc gnome-shell[1633]: 0xa000f6: frame_complete 
> > callback never occurred for frame 3729
> > Sep 29 10:54:54 debian-pc gnome-shell[1633]: 0xa000f6: frame_complete 
> > callback never occurred for frame 3735
> > Sep 29 10:55:01 debian-pc gnome-shell[1633]: 0xa000f6: frame_complete 
> > callback never occurred for frame 3766
>
> (and lots more)
>
> This is maybe interesting. If the Shell isn't reliably getting frame
> completion notifications back from the driver or hardaware, that might be
> related to the display freezing.
>
> > With Wayland it completely crashed and got no response to force the
> > boot and had to use the on and off button. In Xorg I was able to
> > restart with keyboard via tty, but after locking it would only start
> > if I restored the original system settings and this is necessary for
> > both. Now I am with wayland.
>
> What do you mean by "restored the original system settings"?

I delete the configuration file.

> What do you mean by "it would only start if [

Bug#971408: simde: FTBFS when dpkg-buildflags passes -ffile-prefix-map

[Vagrant Cascadian]

Package: simde
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: fixfilepath ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

When run with DEB_BUILD_OPTIONS=reproducible=+fixfilepath, simde FTBFS:

  clang: error: unknown argument: '-ffile-prefix-map=/<>=.'

This is because clang 10 is the first version to support
-ffile-prefix-map, and simde is building with the default clang version
9.

The attached patch updates to clang-10 to fix this issue.

Alternately, you could stick with the default gcc, setting in
debian/rules:

  # Remove when switching to clang 10 or newer.
  export DEB_BUILD_MAINT_OPTIONS=reproducible=-fixfilepath+fixdebugpath


The "fixfilepath" feature is not yet enabled by default in
dpkg-buildflags, but it is used in the tests.reproducible-builds.org
infrastructure for unstable and experimental, and might be enabled by
default for dpkg-buildflags in the future.


Thanks for maintaining simde!


live well,
  vagrant
From ee5ce7156a2918a44cd37268ccc149873b481a49 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Wed, 30 Sep 2020 00:55:25 +
Subject: [PATCH] Update to clang-10 to add support for -ffile-prefix-map.

Setting the DEB_BUILD_OPTIONS=reproducible=+fixfilepath adds
-ffile-prefix-map from dpkg-buildflags to default compiler
arguments. This feature is not currently enabled by default in
dpkg-buildflags, but is enabled for parts of the
tests.reproducible-builds.org infrastructure to solve some
reproducibility issues.
---
 debian/control | 2 +-
 debian/rules   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 2588a77..312644a 100644
--- a/debian/control
+++ b/debian/control
@@ -5,7 +5,7 @@ Maintainer: Debian Med Packaging Team 
 Build-Depends: debhelper-compat (= 13),
cmake,
-   clang [!alpha !hppa !ia64 !m68k !sh4 !x32] 
+   clang-10 [!alpha !hppa !ia64 !m68k !sh4 !x32] 
 Standards-Version: 4.5.0
 Vcs-Browser: https://salsa.debian.org/med-team/simde
 Vcs-Git: https://salsa.debian.org/med-team/simde.git
diff --git a/debian/rules b/debian/rules
index abd2908..9b525bc 100755
--- a/debian/rules
+++ b/debian/rules
@@ -19,7 +19,7 @@ endif
 override_dh_auto_configure:
 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
   ifeq (,$(filter $(DEB_HOST_ARCH),$(CLANG_SKIP)))
-	CC=clang CXX=clang++ dh_auto_configure --builddirectory=clang_test --sourcedirectory=test
+	CC=clang-10 CXX=clang++-10 dh_auto_configure --builddirectory=clang_test --sourcedirectory=test
   endif
 # According to https://wiki.debian.org/ArchitectureSpecificsMemo#Architecture_baselines
 # It is odd that gcc doesn't include this automatically, but clang does
-- 
2.28.0



signature.asc
Description: PGP signature

Bug#969477: zfs-dkms fails to compile with 5.7.0-3 kernel blocking kernel upgrade

[Mo Zhou]

Control: severity -1 important
Control: tag -1 +moreinfo

I cannot reproduce this with either linux 5.7 or linux 5.8 on sid.

Bug#919485: closing

[Mo Zhou]

Control: close -1

the upstream just resurrected

Bug#971402: vboot-utils: FTBFS when fixfilepath is enabled from dpkg-buildflags

[Vagrant Cascadian]

On 2020-09-29, Vagrant Cascadian wrote:
> When the dpkg-buildflags "fixfilepath" is enabled, vboot-utils FTBFS, as
> clang does not support the -ffile-prefix-map argument:
>
>   clang: clang: error: error: unknown argument: 
> '-ffile-prefix-map=/<>=.'unknown argument: 
> '-ffile-prefix-map=/<>=.'

This is actually supported in clang-10, and appears to build fine with
clang-10.

New patch attached which switches to clang-10.

live well,
  vagrant
From f39dec30b7ac4c5356473a0ac0489b85974db22c Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Wed, 30 Sep 2020 00:26:00 +
Subject: [PATCH 6/6] Switch to clang-10 to support -ffile-prefix-map (Closes:
 #971402).

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

diff --git a/debian/control b/debian/control
index ed101bf..3605c05 100644
--- a/debian/control
+++ b/debian/control
@@ -4,8 +4,8 @@ Priority: optional
 Maintainer: Sophie Brun 
 Uploaders: Raphaël Hertzog 
 Build-Depends: debhelper-compat (= 12),
-   clang-9,
-   libfuzzer-9-dev,
+   clang-10,
+   libfuzzer-10-dev,
liblzma-dev,
libssl-dev,
libyaml-dev,
diff --git a/debian/rules b/debian/rules
index 90bf280..277142b 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,7 +1,7 @@
 #!/usr/bin/make -f
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
-export CC = clang-9
+export CC = clang-10
 
 override_dh_auto_build:
 	dh_auto_build -- V=1
-- 
2.20.1



signature.asc
Description: PGP signature

Bug#966315: (Requesting sponsorship) Re: Bug#966315: ITP: age -- simple, modern and secure encryption tool

[Johan Fleury]

> Only thing I could find was this blog entry:
> https://neilmadden.blog/2019/12/30/a-few-comments-on-age/
>
> (After that I'm not really sure if age is ready for Debian…)
>

Filippo Valsorda replied to this post [^1] and while I’m not a security expert 
at all, I feel the main issue is not on age’s robustness, but more on what it 
should do or not do as a tool (e.g. providing sender authentication).

> Are there other reviews on age?

I’m not aware of any reviews/audit on age’s encryption.


[^1]: https://groups.google.com/forum/#!msg/age-dev/r-gwwcN3L-0/EhEvUbG5AwAJ

--
Johan Fleury

signature.asc
Description: OpenPGP digital signature

Bug#954794: New packages must not declare themselves Essential

[jrnieder]

Hi,

Josh Triplett wrote:

> Over the years, "Essential" has made it difficult to reduce installation
> size, to reduce chroot/container size, or to coordinate various
> transitions. Removing something from the Essential set requires tracking
> down every package using it, adding a dependency, carefully managing a
> transition across Debian releases, and risking breakage of third-party
> packages outside Debian.

Interesting.  On the other side if we were to eliminate Essential
would be bloat in the Packages file from e.g. ~every package needing
Pre-Depends on a shell.

[...]
> This change does not propose eliminating the concept of Essential, nor
> does it propose that any specific package become non-Essential.

I think I'd be more supportive of this change if it did.  Freezing the
current essential set in time feels oddly unpragmatic.  If we had a
plan, even one that would take a while, to shrink the essential set,
then it would be more likely to feel worth the cognitive load.

I think there is still a problem to solve here --- e.g. maybe there is
some definition of essential that we may want to move to that would
include things like base-files but wouldn't include things like dpkg
(to take an extreme example) but I don't think we've found it yet.

So even though I'm a fan of the intent here, I agree with the
consensus that we should close this until we have a more specific
proposal.

Thanks,
Jonathan

Bug#971251: dpkg: Accept maintainer's config file if all changes are commented

[Guillem Jover]

Hi!

On Mon, 2020-09-28 at 01:51:51 -0400, hyiltiz wrote:
> Package: dpkg
> Version: 1.20.5
> Severity: normal
> X-Debbugs-Cc: hyil...@gmail.com

> Some packages prompt for whether to accept the package manager's config file 
> or
> keep the one in the system (like the one shown below). It is quite common (as
> was the case shown below) that the new config file is in fact just contains 
> some
> more documentation or commented out lines. I propose that, if all the lines 
> that
> changed are commented (either from ours or from maintainer), dpkg should *not*
> prompt for the choice, but instead simply merge the new 
> documentation/commented
> out available options.
> 
> Configuration file '/etc/bluetooth/main.conf'
>  ==> Modified (by you or by a script) since installation.
>  ==> Package distributor has shipped an updated version.
>What would you like to do about it ?  Your options are:
> Y or I  : install the package maintainer's version
> N or O  : keep your currently-installed version
>   D : show the differences between the versions
>   Z : start a shell to examine the situation
>  The default action is to keep your current version.
> *** main.conf (Y/I/N/O/D/Z) [default=N] ? y
> 
> A possible complication for this is that if the package maintainer or the
> sysadmin of the system decides to re-arrange the order of the config option
> lines, then simply merging might further complicate the issue, and result in a
> convoluted file with the same options showing up at multiple places, which is
> undesirable even though all of those duplicated lines were commented. But I am
> sure we can discuss and find a reasonable merge strategy to adopt that would
> a) allow not having to deal with the choice if everything changed was just
>comments
> b) automatic action wouldn't ultimately lead to complex/broken config files if
>some common editing actions such as swapping chucks of lines were performed

As stated, I don't think this report is actionable. The main problem
is that what constitutes a comment or not depends on each individual
file format, which is something dpkg cannot ever assume. This would
need semantic parsing. The automatic merging part would already be
covered by one of the pre-existing bug requests asking for that.

I guess the only way this could be implemented is if the package
itself provided (or depended on) a configuration file parser
(something like libconfig-model-perl and cme) that could be hooked
into dpkg somehow to perform a semantic merging or similar, but I
don't really see this happening TBH.

I'm inclined to defer the merging part to the pre-existing reports,
where if such a generic semantic parser and merger was to appear could
be configured by the admin to be used during conffile merge prompts or
similar, and otherwise close this report in a bit.

Thanks,
Guillem

Bug#971397: dpkg-dev: dpkg-buildpackage -P option behavior change in update

[Guillem Jover]

Control: tags -1 unreproducible moreinfo

On Tue, 2020-09-29 at 13:10:21 -0700, Elliott Mitchell wrote:
> Package: dpkg-dev
> Version: 1.19.7
> Severity: important

> Between versions 1.19.6 and 1.19.7 the behavior of the -P option for
> dpkg-buildpackage changed.  At 1.19.6 if there was no string directly on
> the -P option, the following argument would be interpreted as the
> profiles to set.  At 1.19.7 the string MUST be part of the same argument.
> 
> ie at 1.19.6, `dpkg-buildpackage -a arm64 -P cross` worked, while
> 1.19.7 *requires* `dpkg-buildpackage -a arm64 -Pcross` (the latter may
> have worked with 1.19.6, but the former worked with 1.19.6)

There's been no changes to dpkg-buildpackage nor any other used
modules in that version.

In addition dpkg-buildpackage has never supported specifying the
build-profiles as non-bundled arguments, since the option got
introduced, so I'm rather puzzled by this report.

Thanks,
Guillem

Bug#971391: gnome-core: version number is confusing

[Simon McVittie]

On Tue, 29 Sep 2020 at 16:29:04 -0300, David Bremner wrote:
> According to https://wiki.debian.org/Gnome?action=show&redirect=GNOME,
> gnome is currently 3.36.4 in unstable.

That's both false (we're halfway through a transition to 3.38.x)
and unrealistically precise. I've replaced that with details of
the major version we expect to ship in bullseye, and a note that for
testing/unstable it's better to look at individual packages, in the
hope that by giving less precise information the wiki page won't be
perpetually outdated.

gnome-shell is probably the best "core" package to use as a marker for
how new the desktop generally is, and it's also responsible for the
main thing that GNOME users see when they log in.

I also removed some other outdated information from the Gnome wiki page
(gnome-dbg was most recently shipped in jessie, gconftool2 hasn't been a
way to configure GNOME for years, etc.), but I'm sure there's plenty more.

smcv

Bug#970909: gnome-authenticator does not start up

[Jeremy Bicha]

Does gnome-authenticator 3.32.2+dfsg1-2 fix your issue?

Thanks,
Jeremy Bicha

Bug#971403: geeqie: fails to start with X error

[Lionel Élie Mamane]

found 971403 1:1.5.1+git20200723-1
found 971403 1:1.5.1+git20200723-2
fixed 971403 1.5.1-11
thanks

Reproduced with 1:1.5.1+git20200723-1 and 1:1.5.1+git20200723-2

Not reproduced with 1.5.1-11

Binaries of versions 1:1.5.1+git20200708-1 and 1:1.5.1+git20200708-1
are not available on snapshot.debian.org, so didn't test them.

On Wed, Sep 30, 2020 at 12:33:23AM +0200, Lionel Elie Mamane wrote:
> Package: geeqie
> Version: 1:1.5.1+git20200808-2a27c9ab-1
> Severity: grave
> Justification: renders package unusable
> 
> Seems to be since upgrade from 1:1.5.1-9 to 1:1.5.1+git20200808-2a27c9ab-1
> 
> $ geeqie 
> 
> (geeqie:26619): Gdk-ERROR **: 00:31:08.776: The program 'geeqie' received an 
> X Window System error.
> This probably reflects a bug in the program.
> The error was 'GLXBadContext'.
>   (Details: serial 185 error_code 161 request_code 152 (GLX) minor_code 6)
>   (Note to programmers: normally, X errors are reported asynchronously;
>that is, you will receive the error a while after causing it.
>To debug your program, run it with the GDK_SYNCHRONIZE environment
>variable to change this behavior. You can then get a meaningful
>backtrace from your debugger if you break on the gdk_x_error() function.)
> Trace/breakpoint trap
> 
> -- System Information:
> Debian Release: 10.6
>   APT prefers stable
>   APT policy: (500, 'stable'), (400, 'testing'), (200, 'unstable'), (1, 
> 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.19.0-9-amd64 (SMP w/8 CPU cores)
> Locale: LANG=fr_LU.UTF-8, LC_CTYPE=fr_LU.UTF-8 (charmap=UTF-8), 
> LANGUAGE=fr_LU.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages geeqie depends on:
> ii  geeqie-common1:1.5.1+git20200808-2a27c9ab-1
> ii  libc62.31-3
> ii  libcairo21.16.0-4
> ii  libchamplain-0.12-0  0.12.16-3
> ii  libchamplain-gtk-0.12-0  0.12.16-3
> ii  libclutter-1.0-0 1.26.2+dfsg-10
> ii  libclutter-gtk-1.0-0 1.8.4-4
> ii  libcogl201.22.2-6
> ii  libdjvulibre21   3.5.27.1-10
> ii  libexiv2-27  0.27.3-3
> ii  libffmpegthumbnailer4v5  2.1.1-0.2+b1
> ii  libgcc-s110.2.0-7
> ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
> ii  libglib2.0-0 2.66.0-2
> ii  libgtk-3-0   3.24.5-1
> ii  libheif1 1.8.0-1
> ii  libjpeg62-turbo  1:1.5.2-2+b1
> ii  liblcms2-2   2.9-3
> ii  liblirc-client0  0.10.1-6.2~deb10u1
> ii  liblua5.1-0  5.1.5-8.1+b2
> ii  libopenjp2-7 2.3.0-2+deb10u1
> ii  libpango-1.0-0   1.42.4-8~deb10u1
> ii  libpangocairo-1.0-0  1.42.4-8~deb10u1
> ii  libpoppler-glib8 0.71.0-5
> ii  libstdc++6   10.2.0-7
> ii  libtiff5 4.1.0+git191117-2~deb10u1
> ii  libwebp6 0.6.1-2
> ii  libx11-6 2:1.6.7-1
> ii  sensible-utils   0.0.12
> 
> Versions of packages geeqie recommends:
> ii  cups-bsd [lpr]   2.2.10-6+deb10u3
> ii  exiftran 2.10-3
> ii  exiv20.25-4+deb10u1
> ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.23+dfsg-2.1+deb10u1
> ii  librsvg2-common  2.44.10-2.1
> ii  ufraw-batch  0.22-4
> ii  zenity   3.30.0-2
> 
> Versions of packages geeqie suggests:
> pn  geeqie-dbg   
> ii  gimp 2.10.18-1+b1
> ii  libjpeg-turbo-progs [libjpeg-progs]  1:1.5.2-2+b1
> ii  ufraw0.22-4
> ii  xpaint   2.9.1.4-3.2+b1
> 
> -- no debconf information
> 

Bug#971403: geeqie: fails to start with X error

[Lionel Élie Mamane]

On Wed, Sep 30, 2020 at 01:14:59AM +0200, Andreas Ronnquist wrote:
> On Wed, 30 Sep 2020 00:33:23 +0200
> Lionel Elie Mamane  wrote:

>> $ geeqie 

>> (geeqie:26619): Gdk-ERROR **: 00:31:08.776: The program 'geeqie'
>> received an X Window System error. This probably reflects a bug in the
>> program. The error was 'GLXBadContext'.

> Could you please try to start it with

> geeqie --disable-clutter

> - and report back if it works with this.

It starts. The subwindows are of very wrong sizes, and there is no
menu. Resizing the subwindows makes stuff show approximately usably,
and makes a menu appear.

The file list (and the whole left pane) misbehaves if it is made "too
narrow". But the minimal width is wants (which seems to be the width
of the menu) is far too wide for my habits.

> If it does, go to Edit -> Preferences - Image - And there change the
> checkbox "Use GPU acceleration via Clutter library (Requires
> restart)"

That checkbox is greyed out.

Bug#971407: ITP: whitakers-words -- latin parser and translation aid

[Calum McConnell]

Package: wnpp
Severity: wishlist
Owner: Calum McConnell 
X-Debbugs-Cc: debian-de...@lists.debian.org, calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: whitakers-words
  Version : 0~20.6.7
  Upstream Author : Martin Keegan 
* URL : http://mk270.github.io/whitakers-words/index.html
* License : Public Domain
  Programming Lang: Ada
  Description : latin parser and translation aid

Whittakers Words is a program that takes in words in latin,
and analyzes them to determine the stems, case, form,  and any
possible  translations.  It can also provide latin words with
a given translation, going from latin to english.  It is
an invaluble tool for latin users, be they experts or
new learners.

Words was created by Willam Whitaker (1936-2010) as a
curiosity that demonstrated his new programming language,
Ada.  It was since improved and iterated on, ported away
from is DOS roots, and given an online access point. 

- 

This package, as mentioned above, is increadibly useful for
working with latin texts.  As such, most latin teachers
and students will use it often: I certainly have.  I
am not aware with any other packaged program with the
same functionality, and while there do exist other, similar
programs, they are comparativly inaccurate and weak.  

I plan on maintaining it mostly on my own, with aid from
upstream.  I *will* need a sponsor to upload it, and if
anyone is intrested in co-maintaing I would be happy for
the help.  A mentor would probably also be needed,
as I have never actually made a package from scratch
before.

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAl9zwDodHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzJAZxAAv+5wkUJ4VPgrui1g
r7UGjKPBtkYqLw/aH/IXqPvdqhnPdl37GZWFeMpaA01WwmDFEq55aul/L3HFzyfD
XVbESeh6XUQ4y9zHmkyb5SGffTK0/htG4xbrCtOIBuo24jwwl/+L4SI0M/rmtis7
hu9gMr63hJS7Gf3nDf1yHCvezMv9KVDry2/RhUpQo5QFJmYoOXFiFU4dxIddaesj
VVtiv0yJhLNBBGmh409yhM4gMAKjW5xow02tu8yX8rq4M9eOH7/B67ffX9/0FEB0
e7i24jMQ50J90qAy0wrOme4Szlo3gJxXt73ankpZS1uc4RNYdhdkhIorZX8hCoSr
uQsjZ0hJIfv3RzPmSuF5P8JkLH5WdS3tPn4P/F/MfE/ssn5xmfXrYlXVZZ0baRhR
LQ08q44v7ZtxK158N+GUoQx6LQ+LZDxgEXABQPDl+9Ozr2wzUxQIbP6lYWKVzBmw
V6XdIX3rcsbMGa1BAfFiWP/YsbzXvpqbai1Lci/z5Xlje9yIrvoJn/xFxTZIt5Ne
jOY6kI68P2Sbh7mYczyn6wsEMzpt92MZ35Z+sj6YtZWuRWaxF1XGBTVy+ZfczoFH
Auo3UXqjhIiT6yhsjLx7dUzrBZp/dMAWr14OzmpoFTRIE7usDemPzkVqDxA+VFg0
imqfgp4qhbvAR9FxW9um11ybmPQ=
=5EAO
-END PGP SIGNATURE-

Bug#971403: geeqie: fails to start with X error

[Andreas Ronnquist]

On Wed, 30 Sep 2020 00:33:23 +0200
Lionel Elie Mamane  wrote:

>Package: geeqie
>Version: 1:1.5.1+git20200808-2a27c9ab-1
>Severity: grave
>Justification: renders package unusable
>
>Seems to be since upgrade from 1:1.5.1-9 to
>1:1.5.1+git20200808-2a27c9ab-1
>
>$ geeqie 
>
>(geeqie:26619): Gdk-ERROR **: 00:31:08.776: The program 'geeqie'
>received an X Window System error. This probably reflects a bug in the
>program. The error was 'GLXBadContext'.
>  (Details: serial 185 error_code 161 request_code 152 (GLX)
> minor_code 6) (Note to programmers: normally, X errors are reported
> asynchronously; that is, you will receive the error a while after
> causing it. To debug your program, run it with the GDK_SYNCHRONIZE
> environment variable to change this behavior. You can then get a
> meaningful backtrace from your debugger if you break on the
> gdk_x_error() function.)
>Trace/breakpoint trap
>

Could you please try to start it with 

geeqie --disable-clutter

- and report back if it works with this. If it does, go to Edit ->
Preferences - Image - And there change the checkbox "Use GPU
acceleration via Clutter library (Requires restart)"

Please report back if this fixes the problem.

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

Bug#971343: Animated background/wallpaper (changing over time) causes system freeze on Nouveau

[Simon McVittie]

Control: found -1 3.36.6-1
Control: found -1 3.38.0-2

This is on a GT218M GPU, which is a Tesla 2.0 device from 2007.
https://www.notebookcheck.net/NVIDIA-GeForce-310M.22439.0.html suggests
that this is comparable in performance to Intel integrated graphics from
the Ivybridge (2012) generation, but probably with a much higher power
consumption.

I don't think we can necessarily treat GNOME freezing on
more-than-10-year-old hardware as release-critical, particularly since
there's a workaround (not using the animated background).

Some other questions I should have asked:

* Are you using any GNOME Shell extensions? (If yes, please try
  disabling them all and see whether the problem persists.)

* Is this a new installation, or have you been using this hardware with
  Linux for a while? If you've been using it previously, have you had
  other graphics- or freeze-related issues with it?

* Has the animated/changing background worked in earlier versions of
  Debian and/or GNOME, or is 3.36 the oldest version you've tried?

* Are you able to do an installation of the Debian 10 'buster' stable
  release on this hardware, if you haven't already tried that? That would
  give us a baseline for whether this is a situation that has been there
  for a while.

On Tue, 29 Sep 2020 at 16:48:21 -0300, Leandro Cunha wrote:
> Graphics:
>   Device-1: NVIDIA GT218M [GeForce 310M] driver: nouveau v: kernel
>   Device-2: Suyin type: USB driver: uvcvideo

Is this Suyin USB device an input (camera), or an output (display)?
Is it part of the laptop, or a removable device?

If it's a removable output device, please check whether this issue still
occurs with the USB device disconnected and just the NVIDIA graphics
device, to keep things as simple as possible.

Also, if you have external screens attached, please check whether it
still occurs with just the laptop's built-in screen, again to try to
keep things as simple as possible.

> Sep 29 10:50:17 debian-pc kernel: [   60.247471] nouveau :01:00.0: 
> firmware: failed to load nouveau/nva8_fuc084 (-2)
> Sep 29 10:50:17 debian-pc kernel: [   60.247475] firmware_class: See 
> https://wiki.debian.org/Firmware for information about missing firmware
> Sep 29 10:50:17 debian-pc kernel: [   60.247478] nouveau :01:00.0: Direct 
> firmware load for nouveau/nva8_fuc084 failed with error -2
> Sep 29 10:50:17 debian-pc kernel: [   60.247492] nouveau :01:00.0: 
> firmware: failed to load nouveau/nva8_fuc084d (-2)
> Sep 29 10:50:17 debian-pc kernel: [   60.247494] nouveau :01:00.0: Direct 
> firmware load for nouveau/nva8_fuc084d failed with error -2
> Sep 29 10:50:17 debian-pc kernel: [   60.247497] nouveau :01:00.0: msvld: 
> unable to load firmware data
> Sep 29 10:50:17 debian-pc kernel: [   60.247499] nouveau :01:00.0: msvld: 
> init failed, -19

This firmware blob is not available in Debian (it seems we cannot legally
distribute it, even in non-free, although it can be extracted from
proprietary NVIDIA drivers) but apparently it's for 2D video encoder/decoder
acceleration (VDPAU) rather than anything GNOME Shell would need, so this
warning is probably harmless?

> Sep 29 10:54:53 debian-pc gnome-shell[1633]: 0xa000f6: frame_complete 
> callback never occurred for frame 3729
> Sep 29 10:54:54 debian-pc gnome-shell[1633]: 0xa000f6: frame_complete 
> callback never occurred for frame 3735
> Sep 29 10:55:01 debian-pc gnome-shell[1633]: 0xa000f6: frame_complete 
> callback never occurred for frame 3766

(and lots more)

This is maybe interesting. If the Shell isn't reliably getting frame
completion notifications back from the driver or hardaware, that might be
related to the display freezing.

> With Wayland it completely crashed and got no response to force the
> boot and had to use the on and off button. In Xorg I was able to
> restart with keyboard via tty, but after locking it would only start
> if I restored the original system settings and this is necessary for
> both. Now I am with wayland.

What do you mean by "restored the original system settings"?

What do you mean by "it would only start if [...]"? GNOME would only
start if you did that? The laptop would only boot up if you did that?
Something else?

> > If Ctrl+Alt+Delete doesn't work, does the system respond to
> > the "magic sysrq key" sequences, in particular AltGr+SysRq+o
> > (immediate power off) and AltGr+SysRq+b (immediate reboot)? (See
> > https://en.wikipedia.org/wiki/Magic_SysRq_key for more details)
>
> I manage to force the shutdown that way.

OK, so the kernel is still working to at least some extent, otherwise
those key sequences wouldn't work. The problem could be in (from highest
to lowest level) GNOME Shell; libmutter or some other library it uses;
the Mesa user-space graphics driver; or the Nouveau kernel-side graphics
driver.

> Log attached, after the problem occurs this log.

You opened a gnome-terminal at 12:44 and the Nautilus file manager at
12:46, a block of zero bytes was written at 

Bug#971406: gnome-control-center: cannot set external display only, freezes

[tom]

Package: gnome-control-center
Version: 1:3.30.3-2~deb10u1
Severity: important

Gnome-conrol-center > devices > displays > external monitor set
to primary in 'join displays'> 'single display'
turns off both LVDS and external monitor, freezes keyboard and 
mouse control, hard reboot only solution.

If 'mirror' is used, the external monitor is available, but only at
the resolution of the LVDS or lower. 

I expected it was possible to have just the external monitor, and LVDS 
off.

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

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

Versions of packages gnome-control-center depends on:
ii  accountsservice0.6.45-2
ii  apg2.2.3.dfsg.1-5
ii  colord 1.4.3-4
ii  desktop-base   10.0.2
ii  desktop-file-utils 0.23-4
ii  gnome-control-center-data  1:3.30.3-2~deb10u1
ii  gnome-desktop3-data3.30.2.1-2
ii  gnome-settings-daemon  3.30.2-3
ii  gsettings-desktop-schemas  3.28.1-1
ii  libaccountsservice00.6.45-2
ii  libatk1.0-02.30.0-2
ii  libc6  2.28-10
ii  libcairo-gobject2  1.16.0-4
ii  libcairo2  1.16.0-4
ii  libcanberra-gtk3-0 0.30-7
ii  libcanberra0   0.30-7
ii  libcheese-gtk253.31.90-1
ii  libcheese8 3.31.90-1
ii  libclutter-1.0-0   1.26.2+dfsg-10
ii  libclutter-gtk-1.0-0   1.8.4-4
ii  libcolord-gtk1 0.1.26-2
ii  libcolord2 1.4.3-4
ii  libcups2   2.2.10-6+deb10u3
ii  libfontconfig1 2.13.1-2
ii  libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii  libglib2.0-0   2.58.3-2+deb10u2
ii  libgnome-bluetooth13   3.28.2-4~deb10u1
ii  libgnome-desktop-3-17  3.30.2.1-2
ii  libgoa-1.0-0b  3.30.1-2
ii  libgoa-backend-1.0-1   3.30.1-2
ii  libgrilo-0.3-0 0.3.7-1
ii  libgtk-3-0 3.24.5-1
ii  libgtop-2.0-11 2.38.0-4
ii  libgudev-1.0-0 232-2
ii  libibus-1.0-5  1.5.19-4+deb10u1
ii  libkrb5-3  1.17-3
ii  libmm-glib01.10.0-1
ii  libnm0 1.14.6-2+deb10u1
ii  libnma01.8.20-1.1
ii  libpango-1.0-0 1.42.4-8~deb10u1
ii  libpangocairo-1.0-01.42.4-8~deb10u1
ii  libpolkit-gobject-1-0  0.105-25
ii  libpulse-mainloop-glib012.2-4+deb10u1
ii  libpulse0  12.2-4+deb10u1
ii  libpwquality1  1.4.0-3
ii  libsecret-1-0  0.18.7-1
ii  libsmbclient   2:4.9.5+dfsg-5+deb10u1
ii  libsoup2.4-1   2.64.2-2
ii  libupower-glib30.99.10-1
ii  libwacom2  0.32-1
ii  libwayland-server0 1.16.0-1
ii  libx11-6   2:1.6.7-1+deb10u1
ii  libxi6 2:1.7.9-1
ii  libxml22.9.4+dfsg1-7+b3

Versions of packages gnome-control-center recommends:
ii  cracklib-runtime  2.9.6-2
ii  cups-pk-helper0.2.6-1+b1
ii  gkbd-capplet  3.26.1-1
ii  gnome-online-accounts 3.30.1-2
ii  gnome-user-docs   3.30.2-1
ii  gnome-user-share  3.28.0-2
ii  iso-codes 4.2-1
ii  libcanberra-pulse 0.30-7
ii  libnss-myhostname 241-7~deb10u4
ii  mousetweaks   3.12.0-5
ii  network-manager-gnome 1.8.20-1.1
ii  policykit-1   0.105-25
ii  pulseaudio-module-bluetooth   12.2-4+deb10u1
ii  realmd0.16.3-2
ii  rygel 0.36.2-4
ii  rygel-tracker 0.36.2-4
ii  system-config-printer-common  1.5.11-4

Versions of packages gnome-control-center suggests:
ii  gnome-software   3.30.6-5
ii  gstreamer1.0-pulseaudio  1.14.4-1
pn  libcanberra-gtk-module   
ii  libcanberra-gtk3-module  0.30-7
ii  x11-xserver-utils7.7+8

-- no debconf information

Bug#971291: salutatoi: Switch to python3-pycryptodome

[Thomas Preud'homme]

I've contacted upstream who said they are planning an alpha in the next 
few weeks and a stable release later in the year. I'll try to upload the 
alpha to experimental and once the new release comes out upload it to 
unstable and close this bug.


Best regards,

Thomas

On 2020-09-28 23:26, Thomas Preud'homme wrote:

Upstream seems to have moved to the module cryptography:
https://repos.goffi.org/sat/rev/330a5f1d9eea. Unfortunately that
commit is not part of the 0.7 release. I wonder if we could persuade
upstream from cutting a minor release for us to package.

Best regards,

Thomas

On 2020-09-28 22:29, Sebastian Ramacher wrote:

Source: salutatoi
Version: 0.8.0~hg3247.f981c0e99220-2
Severity: important
Tags: sid bullseye
Usertags: pycrypto

Dear maintainer,

salutatoi currently Build-Depends or Depends on python3-crypto from
PyCrypto. This project is no longer maintained and PyCryptodome
(https://www.pycryptodome.org/en/latest/) provides a drop in
replacement. Please switch to python3-pycryptodome. I'd like to
remove python-crypto before the release of bullseye.

Cheers

Bug#971405: obs-studio feature request: build with caption support

[Tom L]

Package: obs-studio
Version: 25.0.8
Severity: wishlist

Currently obs-studio is built with caption support disabled as that used to
fail to compile on linux but that was now fixed in OBS a while ago
https://github.com/obsproject/obs-studio/pull/2099 and works without
problems now.

It would be great if it could now be built with -DBUILD_CAPTIONS=ON like is
the default on all their official releases on other platforms to allow
scripts and plugins to output closed captions to streams.

Thank you!

Bug#586415: ITA: tightvnc-java -- TightVNC java applet and command line program

[Mike Gabriel]

On  Di 29 Sep 2020 20:46:17 CEST, Sven Geuer wrote:


owner -1 debma...@g-e-u-e-r.de
retitle -1 ITA: tightvnc-java -- TightVNC java applet and cli program



[ ... @Ola ...]



Hi Mike,

I'd like to maintain tightvnc-java under the umbrella of the Debian
Remote Packaging Team as I already do for tightvnc. Please add the
tightvnc-java project to the team repository as soon as Ola gave his
OK.


Awesome! And yes, will do.


[1] https://salsa.debian.org/sven-geuer-guest/tightvnc-java


Mike

--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpKnlK_3WWcS.pgp
Description: Digitale PGP-Signatur

Bug#971404: python3-gnupg: support %no-protection for unattended key generation

[Martin]

Package: python3-gnupg
Version: 0.4.6-1
Severity: wishlist
Tags: patch upstream

For testing or other purposes, it is useful to create keys
without passphrase protection, esp. in batch mode. gnupg does
support this using the %no-protection control statement.

https://www.gnupg.org/documentation//manuals/gnupg/Unattended-GPG-key-generation.html

The attached patch adds a boolean parameter "no_protection" to
gen_key_input(). If set to True, %no-protection is used.

export_keys() can then export secret keys without protection,
using secret=True and expect_passphrase=False.
Description: Adds support for %no-protection to generate unprotected secret keys
Author: Martin 
Origin: vendor
Last-Update: 2020-09-29
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/gnupg.py
+++ b/gnupg.py
@@ -1462,6 +1462,7 @@
 Generate --gen-key input per gpg doc/DETAILS
 """
 parms = {}
+no_protection = kwargs.pop("no_protection", False)
 for key, val in list(kwargs.items()):
 key = key.replace('_','-').title()
 if str(val).strip():# skip empty strings
@@ -1478,6 +1479,8 @@
 out = "Key-Type: %s\n" % parms.pop('Key-Type')
 for key, val in list(parms.items()):
 out += "%s: %s\n" % (key, val)
+if no_protection:
+out += "%no-protection\n"
 out += "%commit\n"
 return out
 

Bug#971403: geeqie: fails to start with X error

[Lionel Elie Mamane]

Package: geeqie
Version: 1:1.5.1+git20200808-2a27c9ab-1
Severity: grave
Justification: renders package unusable

Seems to be since upgrade from 1:1.5.1-9 to 1:1.5.1+git20200808-2a27c9ab-1

$ geeqie 

(geeqie:26619): Gdk-ERROR **: 00:31:08.776: The program 'geeqie' received an X 
Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadContext'.
  (Details: serial 185 error_code 161 request_code 152 (GLX) minor_code 6)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap

-- System Information:
Debian Release: 10.6
  APT prefers stable
  APT policy: (500, 'stable'), (400, 'testing'), (200, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-9-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_LU.UTF-8, LC_CTYPE=fr_LU.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_LU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages geeqie depends on:
ii  geeqie-common1:1.5.1+git20200808-2a27c9ab-1
ii  libc62.31-3
ii  libcairo21.16.0-4
ii  libchamplain-0.12-0  0.12.16-3
ii  libchamplain-gtk-0.12-0  0.12.16-3
ii  libclutter-1.0-0 1.26.2+dfsg-10
ii  libclutter-gtk-1.0-0 1.8.4-4
ii  libcogl201.22.2-6
ii  libdjvulibre21   3.5.27.1-10
ii  libexiv2-27  0.27.3-3
ii  libffmpegthumbnailer4v5  2.1.1-0.2+b1
ii  libgcc-s110.2.0-7
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.66.0-2
ii  libgtk-3-0   3.24.5-1
ii  libheif1 1.8.0-1
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-3
ii  liblirc-client0  0.10.1-6.2~deb10u1
ii  liblua5.1-0  5.1.5-8.1+b2
ii  libopenjp2-7 2.3.0-2+deb10u1
ii  libpango-1.0-0   1.42.4-8~deb10u1
ii  libpangocairo-1.0-0  1.42.4-8~deb10u1
ii  libpoppler-glib8 0.71.0-5
ii  libstdc++6   10.2.0-7
ii  libtiff5 4.1.0+git191117-2~deb10u1
ii  libwebp6 0.6.1-2
ii  libx11-6 2:1.6.7-1
ii  sensible-utils   0.0.12

Versions of packages geeqie recommends:
ii  cups-bsd [lpr]   2.2.10-6+deb10u3
ii  exiftran 2.10-3
ii  exiv20.25-4+deb10u1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.23+dfsg-2.1+deb10u1
ii  librsvg2-common  2.44.10-2.1
ii  ufraw-batch  0.22-4
ii  zenity   3.30.0-2

Versions of packages geeqie suggests:
pn  geeqie-dbg   
ii  gimp 2.10.18-1+b1
ii  libjpeg-turbo-progs [libjpeg-progs]  1:1.5.2-2+b1
ii  ufraw0.22-4
ii  xpaint   2.9.1.4-3.2+b1

-- no debconf information

Bug#971027: gcc-10: regression in 10.2.0-9 causes segmentation fault in vlc

[Sebastian Ramacher]

On 2020-09-30 00:01:52 +0200, Ahzo wrote:
> 
> Sep 29, 2020, 07:14 by rguent...@suse.de:
> 
> > I've filed > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97236
> >
> > Someone needs to create a testcase or provide instructions how to
> > reproduce the bug.
> >
> 
> Thanks for taking care of this issue upstream.
> 
> Sep 29, 2020, 15:18 by d...@debian.org:
> 
> > On 9/29/20 12:30 PM, Matthias Klose wrote:
> > upstream now has a reduced test case.
> >
> > 10.2.0-12 is uploaded, reverting that commit for now.
> >
> Thanks for the quick upload. This should prevent further fallout, until 
> upstream finds a better solution.

I've confirmed that vlc works again after rebuilding it with gcc-10
10.2.0-12 and scheduled binNMUs of vlc which should hit the archive
soon.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#954794: New packages must not declare themselves Essential

[Javier Serrano Polo]

El dt 29 de 09 de 2020 a les 15:08 -0700, Josh Triplett va escriure:
> I want to avoid letting the problem get any worse.

So Essential packages are a problem. Do you want to remove Essential in
the long-term? If this goal is not clear, there is little point in
changing policy. New Essential packages will exist if there is a good-
enough reason.

smime.p7s
Description: S/MIME cryptographic signature

Bug#971401: texlive-binaries: triggers update-alternatives warning for bibtex

[Gabriele Stilli]

Package: texlive-binaries
Version: 2020.20200327.54578-5

Hello,

while configuring texlive-binaries, the following warning appeared:

update-alternatives: warning: forcing reinstallation of alternative
/usr/bin/bibtex.original because link group bibtex is broken
update-alternatives: warning: not replacing
/usr/share/man/man1/bibtex.1.gz with a link

The warning is reproducible on subsequent reinstallations.

Regards,
Gabriele Stilli

Bug#954794: New packages must not declare themselves Essential

[Josh Triplett]

On Mon, Sep 21, 2020 at 05:15:45PM +0200, Javier Serrano Polo wrote:
> On Mon, 23 Mar 2020 08:00:04 -0700 Josh Triplett  > wrote:
> > This change does not propose eliminating the concept of Essential,
> 
> What is the point of Essential? To omit declaring dependencies on the
> false assumption that some packages are always required by all systems;
> the concept is essentially ill. Thus, if you are not pursuing the
> elimination of Essential, your effort is virtually useless. Do you want
> to remove Essential?

I want to avoid letting the problem get any worse. Eliminating the
concept entirely would have substantial backwards-compatibility issues,
and would invite substantially more controversy. Right now, I'd just
like to propose not adding any *new* Essential packages.

Bug#971402: vboot-utils: FTBFS when fixfilepath is enabled from dpkg-buildflags

[Vagrant Cascadian]

Source: vboot-utils
Severity: normal
Version: 0~R81-12871.B-1
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: fixfilepath ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

When the dpkg-buildflags "fixfilepath" is enabled, vboot-utils FTBFS, as
clang does not support the -ffile-prefix-map argument:

  clang: clang: error: error: unknown argument: 
'-ffile-prefix-map=/<>=.'unknown argument: 
'-ffile-prefix-map=/<>=.'


This can be tested by passing the following DEB_BUILD_OPTIONS:

  DEB_BUILD_OPTIONS=reproducible=+fixfilepath

The "fixfilepath" is not currently enabled by dpkg-buildflags by
default, but might become the default at some point in the future.

The attached patch disables use of this feature in debian/rules and
enables the remaining reproducibility related build flags.


Thanks for maintaining vboot-utils!

live well,
  vagrant
From ec585212c265af22d69249459dcd05dbbc17b78f Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Tue, 29 Sep 2020 21:40:28 +
Subject: [PATCH 2/2] debian/rules: Disable use of fixfilepath with
 DEB_BUILD_MAINT_OPTIONS.

clang does not currently support it, and the build fails with:

  clang: clang: error: error: unknown argument: '-ffile-prefix-map=/<>=.'unknown argument: '-ffile-prefix-map=/<>=.'

Enable other reproducible related build flags (fixdebugpath,
timeless), as these still work and are the current defaults for
dpkg-buildflags.
---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 90bf280..a2c916e 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,6 +1,6 @@
 #!/usr/bin/make -f
 
-export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+export DEB_BUILD_MAINT_OPTIONS = hardening=+all reproducible=-fixfilepath,+fixdebugpath,+timeless
 export CC = clang-9
 
 override_dh_auto_build:
-- 
2.28.0



signature.asc
Description: PGP signature

Bug#971400: vboot-utils: Add patch to avoid embedding the username and time of the build.

[Vagrant Cascadian]

Source: vboot-utils
Severity: normal
Version: 0~R81-12871.B-1
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps username
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The "/usr/bin/futility" embeds differing information in the binary,
depending on when and what user built the package:

  unknown 2020-09-17 07:53:52 pbuilder1 vs. unknown 2021-10-21 16:19:17 
pbuilder2

This obviously breaks reproducible builds:

  https://reproducible-builds.org

The attached patch removes the user and time information from the
getversion.sh script used during build.


Thanks for maintaining vboot-utils!


live well,
  vagrant
From 163953ac2a68b76c7bc62449db3316f0db53ec94 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Tue, 29 Sep 2020 21:31:51 +
Subject: [PATCH 1/2] Add patch to avoid embedding the username and time of the
 build.

This should be unnecessary in the context of building the packages in
Debian, and breaks reproducible builds:

  https://reproducible-builds.org
---
 .../do-not-embed-user-and-time-in-version | 24 +++
 debian/patches/series |  1 +
 2 files changed, 25 insertions(+)
 create mode 100644 debian/patches/do-not-embed-user-and-time-in-version

diff --git a/debian/patches/do-not-embed-user-and-time-in-version b/debian/patches/do-not-embed-user-and-time-in-version
new file mode 100644
index 000..6c63f89
--- /dev/null
+++ b/debian/patches/do-not-embed-user-and-time-in-version
@@ -0,0 +1,24 @@
+From: Vagrant Cascadian 
+Subject: Avoid embedding user and time in version from getversion.sh
+Date: 2020-09-29
+
+The getversion.sh script embeds the build time and user who built the
+binary, which breaks reproducible builds:
+
+  https://reproducible-builds.org/
+
+Without this patch, "/usr/bin/futility" embeds differing information
+in the binary:
+
+  unknown 2020-09-17 07:53:52 pbuilder1 vs. unknown 2021-10-21 16:19:17 pbuilder2
+
+Index: vboot-utils/scripts/getversion.sh
+===
+--- vboot-utils.orig/scripts/getversion.sh
 vboot-utils/scripts/getversion.sh
+@@ -30,4 +30,4 @@ fi
+ 
+ date=$(date '+%F %T')
+ 
+-echo "const char futility_version[] = \"${ver} ${date} ${USER}\";";
++echo "const char futility_version[] = \"${ver}\";";
diff --git a/debian/patches/series b/debian/patches/series
index bb9d533..694943a 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -6,3 +6,4 @@
 0012-fix-spelling-errors.patch
 dont-build-with-werror.patch
 add-missing-flags-pie.patch
+do-not-embed-user-and-time-in-version
-- 
2.28.0



signature.asc
Description: PGP signature

Bug#971399: my_print_defaults: unknown option '--mariadbd'

[Bob Proulx]

Package: mariadb-server-10.5
Version: 1:10.5.5-1
Severity: normal

Since the daily Sid upgrade to mariadb-server-10.5 1:10.5.5-1
on Monday, 2020-09-28, one now receives the following from logrotate
due to the /etc/logrotate.d/mysql-server file.

my_print_defaults: unknown option '--mariadbd'

But my_print_defaults does not support that option.  This is due to
this change.  (Of course local editing of the file to revert this
change avoids the problem.)

-  if [ -f `my_print_defaults --mysqld | grep -oP 
"pid-file=\K[^$]+"` ]; then
+  if [ -f `my_print_defaults --mariadbd | grep -oP 
"pid-file=\K[^$]+"` ]; then

Upstream this seems to have been found already.

https://jira.mariadb.org/browse/MDEV-22659

Thank you for supporting MariaDB.

Bob


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

Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
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: sysvinit (via /sbin/init)

Versions of packages mariadb-server-10.5 depends on:
ii  adduser   3.118
ii  debconf [debconf-2.0] 1.5.74
ii  galera-4  26.4.5-1+b1
ii  gawk  1:5.0.1+dfsg-1
ii  iproute2  5.8.0-1
ii  libc6 2.31-3
ii  libdbi-perl   1.643-2
ii  libgnutls30   3.6.15-4
ii  libpam0g  1.3.1-5
ii  libstdc++610.2.0-11
ii  lsb-base  11.1.0
ii  lsof  4.93.2+dfsg-1
ii  mariadb-client-10.5   1:10.5.5-1
ii  mariadb-common1:10.5.5-1
ii  mariadb-server-core-10.5  1:10.5.5-1
ii  passwd1:4.8.1-1
ii  perl  5.30.3-4
ii  procps2:3.3.16-5
ii  psmisc23.3-1
ii  rsync 3.2.3-2
ii  socat 1.7.3.4-1
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages mariadb-server-10.5 recommends:
ii  libhtml-template-perl  2.97-1

Versions of packages mariadb-server-10.5 suggests:
ii  bsd-mailx [mailx]  8.1.2-0.20180807cvs-2
pn  mariadb-test   
ii  netcat-openbsd 1.217-2

-- Configuration Files:
/etc/logcheck/ignore.d.paranoid/mariadb-server-10_5 [Errno 13] Permission 
denied: '/etc/logcheck/ignore.d.paranoid/mariadb-server-10_5'
/etc/logcheck/ignore.d.server/mariadb-server-10_5 [Errno 13] Permission denied: 
'/etc/logcheck/ignore.d.server/mariadb-server-10_5'
/etc/logcheck/ignore.d.workstation/mariadb-server-10_5 [Errno 13] Permission 
denied: '/etc/logcheck/ignore.d.workstation/mariadb-server-10_5'

-- debconf information:
  mariadb-server-10.5/nis_warning:
  mariadb-server-10.5/postrm_remove_databases: false
  mariadb-server-10.5/old_data_directory_saved:

Bug#971398: Update to new version (0.11.X)

[Louis-Philippe Véronneau]

Package: sublime-music
Version: 0.9.1-2
Severity: wishlist
Owner: po...@debian.org

The upgrade to a new version is currently blocked by missing
dependencies in the archive (namely dataclasses-json).

Working on it, but those new packages will need to clear NEW before I
can make the update.

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



signature.asc
Description: OpenPGP digital signature

Bug#971367: mariadb-10.5 should not embed wolfssl

[Moritz Mühlenhoff]

On Tue, Sep 29, 2020 at 02:57:48PM +0200, Helmut Grohne wrote:
> Source: mariadb-10.5
> Version: 1:10.5.5-1
> Tags: security
> Severity: serious
> Justification: unsupportable by the Debian security team
> 
> Hi Otto,
> 
> I've hinted that the situation about an embedded ssl library might be
> suboptimal earlier. Since then, I've checked (using the buildd logs)
> that indeed mariadb does build an embedded copy of wolfssl. I've also
> checked with the Debian security team (Moritz Muehlenhoff in
> particular). Such an embedding is unsupportable by the security team.

Actually when I saw this in IRC, I thought the "-DWITH_SSL=bundled" referred
to MariaDB 10.5 having switched to a bundled version of OpenSSL.

Historically mariadb/mysql has always used a bundled copy of yassl
(now named wolfssl), so not switching to the shared src:wolfssl is
not a regression over the status quo in buster.

But by all means if we can find a way to fix the build to use the system-wide
WolfSSL, let's do it.

Cheers,
Moritz

Bug#920365: [debian-mysql] Bug#920365: Bug#920365: mariadb_config: improve cross compilation support

[Otto Kekäläinen]

> $ wget 
> http://deb.debian.org/debian/pool/main/m/mariadb-10.5/libmariadbd-dev_10.5.5-1_amd64.deb
> ...
> $ wget 
> http://deb.debian.org/debian/pool/main/m/mariadb-10.5/libmariadbd-dev_10.5.5-1_arm64.deb
> ...
> $ dpkg-deb -x libmariadbd-dev_10.5.5-1_amd64.deb amd64
> $ dpkg-deb -x libmariadbd-dev_10.5.5-1_arm64.deb arm64
> $ diff -u a*64/usr/include/mariadb/server/my_config.h
> --- amd64/usr/include/mariadb/server/my_config.h2020-09-25 
> 18:56:59.0 +0200
> +++ arm64/usr/include/mariadb/server/my_config.h2020-09-25 
> 18:56:59.0 +0200

$ diff -u a*64/usr/include/mariadb/server/my_config.h | diffstat
 my_config.h |   10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

OK, so they have custom contents based on arch, but just that header
file, nothing else.

> The usual solution to fix this is moving the header to a multiarch
> location (i.e. below /usr/include/${DEB_HOST_MULTIARCH}).

If I move just the header file but not all of
/usr/include/mariadb/server, will there be issues with paths at some
point?

I don't have any sample program to build and test against
libmariadbd-dev and I am not a C/C++ coder so this starts to be beyond
my level.

Bug#971367: [debian-mysql] Bug#971367: Bug#971367: mariadb-10.5 should not embed wolfssl

[Otto Kekäläinen]

Hello!

> Thank you for the background. Let me detail on the security side. The
> issue is not with using wolfssl. The issue is with using a bundled ssl
> library. Doing so means that a single bug in wolfssl must be uploaded
> several times in order to fix it. I think it would be ok to use the
> system copy of wolfssl. However, that's not what happens when you
> specifcy -DWITH_SSL=system it seems. Would
> -DWITH_SSL=/usr/include/wolfssl be an option?
>
> Does that look resolvable now?

I've tested this before and it didn't work, but I tested it again and
made sure to document it in the same upstream issue I referenced
earlier: 
https://jira.mariadb.org/browse/MDEV-21835?focusedCommentId=167192&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-167192

Seems the cmake/ssl.cmake expects to find OpenSSL then given a custom
path, and when it does not, it aborts the build in the configure
stage.

Bug#920365: [debian-mysql] Bug#920365: Bug#920365: mariadb_config: improve cross compilation support

[Helmut Grohne]

Hi Otto,

On Tue, Sep 29, 2020 at 11:46:26PM +0300, Otto Kekäläinen wrote:
> Multiarch-hinter says: libmariadbd-dev conflicts on
> /usr/include/mariadb/server/my_config.h on any two of amd64, arm64,
> armel, armhf, and 5 more
> 
> I don't understand this, since my_config.h is supposed to be an ASCII
> file and identical to all archs.
> 
> Running in Debian unstable to verify the file contents:
> 
> apt install libmariadbd-dev
> cat /usr/include/mariadb/server/my_config.h

$ wget 
http://deb.debian.org/debian/pool/main/m/mariadb-10.5/libmariadbd-dev_10.5.5-1_amd64.deb
...
$ wget 
http://deb.debian.org/debian/pool/main/m/mariadb-10.5/libmariadbd-dev_10.5.5-1_arm64.deb
...
$ dpkg-deb -x libmariadbd-dev_10.5.5-1_amd64.deb amd64
$ dpkg-deb -x libmariadbd-dev_10.5.5-1_arm64.deb arm64
$ diff -u a*64/usr/include/mariadb/server/my_config.h
--- amd64/usr/include/mariadb/server/my_config.h2020-09-25 
18:56:59.0 +0200
+++ arm64/usr/include/mariadb/server/my_config.h2020-09-25 
18:56:59.0 +0200
@@ -105,9 +105,9 @@
 /* #undef HAVE_CRC32_VPMSUM */
 
 /* Support ARMv8 crc + crypto  */
-/* #undef HAVE_ARMV8_CRC */
-/* #undef HAVE_ARMV8_CRYPTO */
-/* #undef HAVE_ARMV8_CRC_CRYPTO_INTRINSICS */
+#define HAVE_ARMV8_CRC 1
+#define HAVE_ARMV8_CRYPTO 1
+#define HAVE_ARMV8_CRC_CRYPTO_INTRINSICS 1
 
 /* Does "struct timespec" have a "sec" and "nsec" field? */
 /* #undef HAVE_TIMESPEC_TS_SEC */
@@ -395,8 +395,8 @@
 #define STACK_DIRECTION -1
 
 #define SYSTEM_TYPE "debian-linux-gnu"
-#define MACHINE_TYPE "x86_64"
-#define DEFAULT_MACHINE "x86_64"
+#define MACHINE_TYPE "aarch64"
+#define DEFAULT_MACHINE "aarch64"
 /* #undef HAVE_DTRACE */
 
 #define SIGNAL_WITH_VIO_CLOSE 1
$

The usual solution to fix this is moving the header to a multiarch
location (i.e. below /usr/include/${DEB_HOST_MULTIARCH}).

The next best solution is dropping Multi-Arch: same from libmariadb-dev.
Do note that Multi-Arch: same is not required for using libmariadb-dev
for cross building.

Hope this helps

Helmut

Bug#971385: courier-imap: thunderbird error: Unicode message and yout E-mail reader did not enable Unicode support

[Miquel Gual Torner]

Package: courier-imap
Version: 5.0.6+1.0.6-1
Severity: normal

Dear Maintainer,


* What led to the situation?
Mail server update to courier-imap version 5.0.6 + 1.0.6-1. Thunderbird shows 
the error:
"Message X appears to be a Unicode message and yout E-mail reader did not 
enable Unicode support. Please use an E-mail reader that supports IMAP with 
UTF-8 (see https://tools.ietf.org/html/rfc6855 .html) ".
Everything works correctly. Show the error.

# Option 1: downgrade
* What exactly did (or did not do) that was effective (or
  ineffective)?
If I downgrade the courier-imap version to a version 4 (debian 9).
  * What was the result of this action?
It does not show the error.

# Option 2: compile new version
  * What exactly did (or did not do) that was effective (or
  ineffective)?
Try compiling the courier-imap package.
* What was the result of this action?
I couldn't integrate it into the distribution.
* What result did you expect instead?
Integrate it and solve the problem.

# Option 3: Apply patch
  * What exactly did (or did not do) that was effective (or
  ineffective)?
I did not do 
https://github.com/svarshavchik/courier-libs/commit/a1d3a864cf488e9bd2c49dc01289e49d857fdeb7?branch=a1d3a864cf488e9bd2c49dc01289e49d857fdeb7&diffified

-
I think this patch would fix my problem with thunderbird:

https://github.com/svarshavchik/courier-libs/commit/a1d3a864cf488e9bd2c49dc01289e49d857fdeb7?branch=a1d3a864cf488e9bd2c49dc01289e49d857fdeb7&diffified
--> imapd.c 
}

dirsync(path);
+   if (utf8_error) {
+   writes("* OK [ALERT] Your IMAP client does not appear to "
+  "correctly implement Unicode messages, "
+  "see https://tools.ietf.org/html/rfc6855.html\r\n";);
+   }
writes(tag);
writes(" OK [APPENDUID ");
writen(new_uidv);
writes(" ");
writen(new_uid);
writes("] APPEND Ok.");
-   if (utf8_error) {
-   writes(" [ALERT] Your IMAP client does not appear to "
-   "correctly implement Unicode messages, "
-   "see https://tools.ietf.org/html/rfc6855.html";);
-   }
writes("\r\n");
return (0);
}



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

Kernel: Linux 5.3.13-1-pve (SMP w/20 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to ca_ES.UTF-8), LANGUAGE=ca_ES.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to ca_ES.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages courier-imap depends on:
ii  courier-authlib0.69.0-2
ii  courier-base   1.0.6-1
ii  debconf [debconf-2.0]  1.5.71
ii  exim4-daemon-heavy [mail-transport-agent]  4.92-8+deb10u4
ii  libc6  2.28-10
ii  libcourier-unicode42.1-3
ii  libgamin0 [libfam0]0.1.10-5+b1
ii  libgdbm6   1.18.1-4
ii  libidn11   1.33-2.2
ii  sysvinit-utils 2.93-8

courier-imap recommends no packages.

Versions of packages courier-imap suggests:
pn  courier-doc  
pn  imap-client  

-- Configuration Files:
/etc/courier/imapd changed:
ADDRESS=0
PORT=143
MAXDAEMONS=1000
MAXPERIP=1000
PIDFILE=/run/courier/imapd.pid
TCPDOPTS="-nodnslookup -noidentlookup"
IMAPACCESSFILE=/etc/courier/imapaccess
LOGGEROPTS="-name=imapd"
IMAP_CAPABILITY="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT 
THREAD=REFERENCES SORT QUOTA IDLE UTF8=ACCEPT"
IMAP_KEYWORDS=1
IMAP_ACL=1
IMAP_CAPABILITY_ORIG="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE 
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5 AUTH=CRAM-SHA1 
AUTH=CRAM-SHA256 IDLE UTF8=ACCEPT"
IMAP_PROXY=0
IMAP_PROXY_FOREIGN=0
IMAP_IDLE_TIMEOUT=60
IMAP_MAILBOX_SANITY_CHECK=0
IMAP_CAPABILITY_TLS="$IMAP_CAPABILITY AUTH=PLAIN"
IMAP_CAPABILITY_TLS_ORIG="$IMAP_CAPABILITY_ORIG AUTH=PLAIN"
IMAP_DISABLETHREADSORT=0
IMAP_CHECK_ALL_FOLDERS=1
IMAP_OBSOLETE_CLIENT=0
IMAP_UMASK=022
IMAP_ULIMITD=131072
IMAP_USELOCKS=1
IMAP_SHAREDINDEXFILE=/etc/courier/shared/index
IMAP_ENHANCEDIDLE=1
IMAP_TRASHFOLDERNAME=Trash
IMAP_EMPTYTRASH=Trash:7
IMAP_MOVE_EXPUNGE_TO_TRASH=0
SENDMAIL=/usr/sbin/sendmail
HEADERFROM=X-IMAP-Sender
IMAPDSTART=YES
MAILDIRPATH=Maildir

/etc/courier/imapd-ssl changed:
SSLPORT=993
SSLADDRESS=0
SSLPIDFILE=/run/courier/imapd-ssl.pid
SSLLOGGEROPTS="-name=imapd-ssl"
IMAPDSSLSTART=YES
IMAPDSTARTTLS=YES
IMAP_TLS_REQUIRED=0
COURIERTLS=/usr/bin/couriertls
TLS_STARTTLS_PROTOCOL="$TLS_PROTOCOL"
TLS_CERTFILE=/etc/courier/imapd.pem
TLS_DHPARAMS=/etc/courier/dhparams.pem
TLS_TRUSTCERTS=/etc/ssl/certs/ca-certificat

Bug#920365: [debian-mysql] Bug#920365: Bug#920365: mariadb_config: improve cross compilation support

[Otto Kekäläinen]

> > W dependency-is-not-multi-archified libmariadb-dev-compat depends on
> > libmariadb-dev (multi-arch: no)
> > W dependency-is-not-multi-archified libmariadbd-dev depends on
> > libmariadb-dev (multi-arch: no)
> > W dependency-is-not-multi-archified mariadb-plugin-gssapi-client
> > depends on mariadb-client-10.5 (multi-arch: no)
>
> I fear that there is little you can do here. The hinter likely told you
> that you can mark libmariadb-dev-compat Multi-Arch: same. Lintian told
> you that Multi-Arch: same is useless since libmariadb-dev is not thus
> marked. Both are correct. The idea of the hinter is that by
> parallelizing the addition of M-A:same, we get everything marked quicker
> while having some useless (but correct) markings in the interim. The
> lintian stance is that useless markings issue a warning.

Multiarch-hinter says: libmariadbd-dev conflicts on
/usr/include/mariadb/server/my_config.h on any two of amd64, arm64,
armel, armhf, and 5 more

I don't understand this, since my_config.h is supposed to be an ASCII
file and identical to all archs.

Running in Debian unstable to verify the file contents:

apt install libmariadbd-dev
cat /usr/include/mariadb/server/my_config.h

Bug#971396: md4c: CVE-2020-26148

[Salvatore Bonaccorso]

Source: md4c
Version: 0.4.5-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/mity/md4c/issues/130
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for md4c.

CVE-2020-26148[0]:
| md_push_block_bytes in md4c.c in md4c 0.4.5 allows attackers to
| trigger use of uninitialized memory, and cause a denial of service
| (e.g., assertion failure) via a malformed Markdown document.


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-26148
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26148
[1] https://github.com/mity/md4c/commit/22ca89a3008966c4316d6b0a158b1a49f9038df0
[2] https://github.com/mity/md4c/issues/130

Regards,
Salvatore

Bug#929707: [debian-mysql] Bug#929707: mariadb-client-10.1: import of "mysqldump --all-databases" fails with "ERROR 1062 (23000): Duplicate entry"

[Otto Kekäläinen]

Thanks!

Would you like to test with mariadb-10.5 in unstable as well?

Or perhaps contribute by writing a small autopkgtest extension (the
debian/tests files in the packaging repository at
https://salsa.debian.org/mariadb-team/mariadb-10.5) that runs this
dump and thus ensure forever that this feature will not regress?

Bug#933063: [debian-mysql] Bug#933063: character_set_client: latin1?

[Otto Kekäläinen]

I tested this but it did not at least directly work:

commit b8e537d55b467eb285a82842e73bb22732ef9ad6 (HEAD -> master-next)
Author: Otto Kekäläinen 
Date:   Tue Sep 29 21:27:02 2020 +0300

Use build flag to enforce default charset as utf8mb4 (Closes: ##933063)

diff --git a/debian/rules b/debian/rules
index 819ac6ea0..12b162002 100755
--- a/debian/rules
+++ b/debian/rules
@@ -101,6 +101,7 @@ endif
-DSYSTEM_TYPE="debian-$(DEB_HOST_GNU_SYSTEM)" \
-DBUILD_CONFIG=mysql_release \
-DWITH_SSL=bundled \
+  -DDEFAULT_CHARSET=utf8mb4 \
-DPLUGIN_TOKUDB=NO \
-DPLUGIN_CASSANDRA=NO \
-DPLUGIN_AWS_KEY_MANAGEMENT=NO \


--->


MariaDB [(none)]> status
--
mariadb  Ver 15.1 Distrib 10.5.5-MariaDB, for debian-linux-gnu
(x86_64) using readline 5.2

Connection id: 76
Current database:
Current user: root@localhost
SSL: Not in use
Current pager: stdout
Using outfile: ''
Using delimiter: ;
Server: MariaDB
Server version: 10.5.5-MariaDB-2-debug Debian 10
Protocol version: 10
Connection: Localhost via UNIX socket
Server characterset: utf8mb4
Db characterset: utf8mb4
Client characterset: latin1
Conn.  characterset: latin1
UNIX socket: /run/mysqld/mysqld.sock
Uptime: 27 sec

Threads: 22  Questions: 674  Slow queries: 0  Opens: 199  Open tables:
37  Queries per second avg: 24.962
--

Bug#965012: RFT: squid3 3.5.23-5+deb9u5, please test

[Roberto C . Sánchez]

On Tue, Sep 29, 2020 at 12:11:24AM +0200, Markus Koschany wrote:
> [adding Andreas and Kevin to CC who helped with testing past squid3 updates]
> 
> Hello,
> 
> I have uploaded a new version of squid3 for Stretch to people.debian.org.
> 
> https://people.debian.org/~apo/lts/squid3/stretch/
> 
> It contains fixes for CVE-2020-15049, CVE-2020-15810, CVE-2020-15811 and
> CVE-2020-24606. Let me know if you find any regressions from
> the current released version 3.5.23-5+deb9u4.
> 
The changes look excellent to me.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Bug#971397: dpkg-dev: dpkg-buildpackage -P option behavior change in update

[Elliott Mitchell]

Package: dpkg-dev
Version: 1.19.7
Severity: important

Between versions 1.19.6 and 1.19.7 the behavior of the -P option for
dpkg-buildpackage changed.  At 1.19.6 if there was no string directly on
the -P option, the following argument would be interpreted as the
profiles to set.  At 1.19.7 the string MUST be part of the same argument.

ie at 1.19.6, `dpkg-buildpackage -a arm64 -P cross` worked, while
1.19.7 *requires* `dpkg-buildpackage -a arm64 -Pcross` (the latter may
have worked with 1.19.6, but the former worked with 1.19.6)

I see good arguments both for and against allowing or not the profile
list being a separate argument.  Overtly user-visible behavior though
should NOT change with patch-level changes (should be minor-version).


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

Bug#971395: RFS: zipios++/2.2.5.0-1 -- small C++ library for reading zip files (documents)

[François Mazen]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "zipios++":

 * Package name: zipios++
   Version : 2.2.5.0-1
   Upstream Author : Thomas Sondergaard 
 * URL : http://zipios.sourceforge.net/
 * License : LGPL-2+
 * Vcs : https://salsa.debian.org/debian/zipios
   Section : devel

It builds those binary packages:

  libzipios-dev - small C++ library for reading zip files (development)
  libzipios2 - small C++ library for reading zip files (library)
  libzipios-doc - small C++ library for reading zip files (documents)

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

  https://mentors.debian.net/package/zipios++/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/z/zipios++/zipios++_2.2.5.0-1.dsc

Changes since the last upload:

 zipios++ (2.2.5.0-1) unstable; urgency=high
 .
   * Import new upstream release (Closes: #834171).
   * Rename library package from libzipios++0v5 to libzipios2
   * Add watch file
   * Fix reproducible issue with doxygen documentation
   * Add autopkgtest
   * Add upstream metadata
   * Bump standard version to 4.5.0
   * Forward patches to upstream
   * Remove documentation duplicate files
   * Update debhelper compatibility to 13 and ignore uninstalled test
binaries.
   * Fix privacy breach in html documentation.

Regards,


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

Bug#971394: libproxy: CVE-2020-25219

[Salvatore Bonaccorso]

Source: libproxy
Version: 0.4.15-14
Severity: important
Tags: security upstream
Forwarded: https://github.com/libproxy/libproxy/issues/134
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 0.4.15-13
Control: found -1 0.4.15-5

Hi,

The following vulnerability was published for libproxy.

CVE-2020-25219[0]:
| url::recvline in url.cpp in libproxy 0.4.x through 0.4.15 allows a
| remote HTTP server to trigger uncontrolled recursion via a response
| composed of an infinite stream that lacks a newline character. This
| leads to stack exhaustion.


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-25219
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25219
[1] https://github.com/libproxy/libproxy/issues/134

Regards,
Salvatore

Bug#971393: mbedtls: New upstream version (2.24.0) with TLS 1.3 support

[Antoni Villalonga]

Source: mbedtls
Severity: normal
X-Debbugs-Cc: ant...@friki.cat

Dear Maintainer,

Please consider upgrading package to newer versions with TLS 1.3 support
enabled.

Regards,

Bug#929707: [debian-mysql] Bug#929707: mariadb-client-10.1: import of "mysqldump --all-databases" fails with "ERROR 1062 (23000): Duplicate entry"

[Matija Nalis]

I've retested now quickly on different machine, and it *seems* to be working OK 
in Buster.

# mysqldump -uroot --max_allowed_packet=2147483648 --hex-blob --lock-all-tables 
--master-data --flush-privileges --databases video1 mysql > backup.sql
# mysql < backup.sql
# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 10 (buster)
Release:10
Codename:   buster
# dpkg -l | grep mariadb
ii  libmariadb3:amd641:10.3.23-0+deb10u1   
amd64MariaDB database client library
ii  mariadb-client   1:10.3.23-0+deb10u1   
all  MariaDB database client (metapackage depending on the latest 
version)
ii  mariadb-client-10.3  1:10.3.23-0+deb10u1   
amd64MariaDB database client binaries
ii  mariadb-client-core-10.3 1:10.3.23-0+deb10u1   
amd64MariaDB database core client binaries
ii  mariadb-common   1:10.3.23-0+deb10u1   
all  MariaDB common metapackage
ii  mariadb-server   1:10.3.23-0+deb10u1   
all  MariaDB database server (metapackage depending on the latest 
version)
ii  mariadb-server-10.3  1:10.3.23-0+deb10u1   
amd64MariaDB database server binaries
ii  mariadb-server-core-10.3 1:10.3.23-0+deb10u1   
amd64MariaDB database core server files

Bug#970984: linux-image-5.8.0-2-amd64: Please replace console scrollback

[Salvatore Bonaccorso]

Hi Asher,

On Mon, Sep 28, 2020 at 04:16:40PM -0400, Asher Gordon wrote:
> Control: forwarded -1 https://bugzilla.kernel.org/show_bug.cgi?id=209421
> 
> Hi Moritz,
> 
> Moritz Mühlenhoff  writes:
> 
> > Yeah, I'm also bitten by this for my day-to-day workflows, but
> > unfortunately this was removed upstream, this is not a Debian-specific
> > patch, so this needs to be fixed upstream, before it becomes available
> > in Debian again.
> 
> OK, I forwarded this upstream here:
> https://bugzilla.kernel.org/show_bug.cgi?id=209421

FTR, here is Linus statement on the removal and what needs to be done:
https://lore.kernel.org/stable/CAHk-=whe4zdtdcebnewqc4gsqzwsvj5-emg0bucogcwphoa...@mail.gmail.com/
 

Regards,
Salvatore

Bug#920365: [debian-mysql] Bug#920365: Bug#920365: mariadb_config: improve cross compilation support

[Helmut Grohne]

Hi Otto,

On Tue, Sep 29, 2020 at 08:59:49PM +0300, Otto Kekäläinen wrote:
> Tested patch in
> https://salsa.debian.org/mariadb-team/mariadb-10.5/-/commit/2a8304051a3107fe828314b66b33aca7ecb863d4
> 
> Builds went fine, so I'll add this commit on top of the master branch.

Cool. My build environment must be buggy then.

In any case, this change makes cross building mariadb a lot easier.

> The topic of cross-building tangents the multi-arch definitions in the
> control file which currently are not correct and I am not sure on how
> to correctly solve it without regressions:
> 
> W dependency-is-not-multi-archified libmariadb-dev-compat depends on
> libmariadb-dev (multi-arch: no)
> W dependency-is-not-multi-archified libmariadbd-dev depends on
> libmariadb-dev (multi-arch: no)
> W dependency-is-not-multi-archified mariadb-plugin-gssapi-client
> depends on mariadb-client-10.5 (multi-arch: no)

I fear that there is little you can do here. The hinter likely told you
that you can mark libmariadb-dev-compat Multi-Arch: same. Lintian told
you that Multi-Arch: same is useless since libmariadb-dev is not thus
marked. Both are correct. The idea of the hinter is that by
parallelizing the addition of M-A:same, we get everything marked quicker
while having some useless (but correct) markings in the interim. The
lintian stance is that useless markings issue a warning.

Helmut

Bug#971367: [debian-mysql] Bug#971367: mariadb-10.5 should not embed wolfssl

[Helmut Grohne]

On Tue, Sep 29, 2020 at 03:24:52PM +0100, Robie Basak wrote:
> The relevant previous bug is
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921488 where the
> packaging switched from "system" to "bundled". Switching back to
> "system" would regress that licensing problem.
> 
> Also relevant is
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924937 which is the
> same situation but for Postgres.
> 
> I don't know how to resolve this conflict between Debian's security
> position and Debian's licensing position, but hopefully the above
> references provide some background to help someone else figure this out.

Thank you for the background. Let me detail on the security side. The
issue is not with using wolfssl. The issue is with using a bundled ssl
library. Doing so means that a single bug in wolfssl must be uploaded
several times in order to fix it. I think it would be ok to use the
system copy of wolfssl. However, that's not what happens when you
specifcy -DWITH_SSL=system it seems. Would
-DWITH_SSL=/usr/include/wolfssl be an option?

Does that look resolvable now?

Helmut

Bug#958611: at: Build-Depends on deprecated dh-systemd which is going away

[Jose M Calhariz]

Hi,

You have my blessing for the NMU.  If it helps, you may remove from
DELAYED/14 and upload it
to normal queue.

Kind regards
Jose M Calhariz


On 29/09/2020 20:03, Michael Biebl wrote:
> Control: tags -1 + patch pending
>
> Hi,
>
> I've uploaded a minimal fix to DELAYED/14.
> Debdiff is attached.
>
> Please holler, if you want me to cancel the NMU.
>
> Regards,
> Michael

Bug#971392: buster-pu: package tigervnc/1.9.0+dfsg-3+deb10u3

[Joachim Falk]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

Security fix for CVE-2020-26117 as detailed in bug #971272.

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

Kernel: Linux 4.19.0-9-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru tigervnc-1.9.0+dfsg/debian/changelog 
tigervnc-1.9.0+dfsg/debian/changelog
--- tigervnc-1.9.0+dfsg/debian/changelog2020-06-16 21:36:31.0 
+0200
+++ tigervnc-1.9.0+dfsg/debian/changelog2020-09-29 20:21:20.0 
+0200
@@ -1,3 +1,13 @@
+tigervnc (1.9.0+dfsg-3+deb10u3) buster; urgency=high
+
+  [ Joachim Falk ]
+  * Properly store certificate exceptions in native and java VNC viewer. The
+VNC viewers stored the certificate exceptions as authorities, meaning that
+the owner of a certificate could impersonate any server after a client had
+added an exception. This is issue CVE-2020-26117 (Closes: #971272).
+
+ -- Joachim Falk   Tue, 29 Sep 2020 20:21:20 +0200
+
 tigervnc (1.9.0+dfsg-3+deb10u2) buster; urgency=medium

   [ Joachim Falk ]
diff -Nru tigervnc-1.9.0+dfsg/debian/patches/CVE-2020-26117.patch 
tigervnc-1.9.0+dfsg/debian/patches/CVE-2020-26117.patch
--- tigervnc-1.9.0+dfsg/debian/patches/CVE-2020-26117.patch 1970-01-01 
01:00:00.0 +0100
+++ tigervnc-1.9.0+dfsg/debian/patches/CVE-2020-26117.patch 2020-09-29 
20:21:20.0 +0200
@@ -0,0 +1,460 @@
+Description: Properly store certificate exceptions in native and java VNC 
viewer.
+ They stored the certificates as authorities, meaning that the owner of a
+ certificate could impersonate any server after a client had added an 
exception.
+Author: Pierre Ossman  and Brian P. Hinz 

+Abstract:
+ Properly store certificate exceptions
+ .
+ . git commit b30f10c681ec87720cff85d490f67098568a9cba
+ .
+ The previous method stored the certificates as authorities, meaning that
+ the owner of that certificate could impersonate any server it wanted
+ after a client had added an exception.
+ .
+ Handle this more properly by only storing exceptions for specific
+ hostname/certificate combinations, the same way browsers or SSH does
+ things.
+ .
+ . git commit f029745f63ac7d22fb91639b2cb5b3ab56134d6e
+ .
+ Like the native viewer, the Java viewer didn't store certificate
+ exceptions properly. Whilst not as bad as the native viewer, it still
+ failed to check that a stored certificate wouldn't be maliciously used
+ for another server. In practice this can in most cases be used to
+ impersonate another server.
+ .
+ Handle this like the native viewer by storing exceptions for a specific
+ hostname/certificate combination.
+ .
+ This issue is CVE-2020-26117.
+
+Index: pkg-tigervnc/common/rfb/CSecurityTLS.cxx
+===
+--- pkg-tigervnc.orig/common/rfb/CSecurityTLS.cxx
 pkg-tigervnc/common/rfb/CSecurityTLS.cxx
+@@ -232,22 +232,6 @@ void CSecurityTLS::setParam()
+ if (*cafile && 
gnutls_certificate_set_x509_trust_file(cert_cred,cafile,GNUTLS_X509_FMT_PEM) < 
0)
+   throw AuthFailureException("load of CA cert failed");
+
+-/* Load previously saved certs */
+-char *homeDir = NULL;
+-int err;
+-if (getvnchomedir(&homeDir) == -1)
+-  vlog.error("Could not obtain VNC home directory path");
+-else {
+-  CharArray caSave(strlen(homeDir) + 19 + 1);
+-  sprintf(caSave.buf, "%sx509_savedcerts.pem", homeDir);
+-  delete [] homeDir;
+-
+-  err = gnutls_certificate_set_x509_trust_file(cert_cred, caSave.buf,
+-   GNUTLS_X509_FMT_PEM);
+-  if (err < 0)
+-vlog.debug("Failed to load saved server certificates from %s", 
caSave.buf);
+-}
+-
+ if (*crlfile && 
gnutls_certificate_set_x509_crl_file(cert_cred,crlfile,GNUTLS_X509_FMT_PEM) < 0)
+   throw AuthFailureException("load of CRL failed");
+
+@@ -272,7 +256,10 @@ void CSecurityTLS::checkSession()
+   const gnutls_datum_t *cert_list;
+   unsigned int cert_list_size = 0;
+   int err;
++
++  char *homeDir;
+   gnutls_datum_t info;
++  size_t len;
+
+   if (anon)
+ return;
+@@ -315,13 +302,13 @@ void CSecurityTLS::checkSession()
+ throw AuthFailureException("decoding of certificate failed");
+
+   if (gnutls_x509_crt_check_hostname(crt, client->getServerName()) == 0) {
+-char buf[255];
++CharArray text;
+ vlog.debug("hostname mismatch");
+-snprintf(buf, sizeof(buf), "Hostname (%s) does not match any certificate, 
"
+- "do you want to continue?", 
client->getServerName());
+-buf[sizeof(buf) - 1] = '\0';
+-if (!msg->showMsgBox(UserMsgBox:

Bug#971381: bacula-director-mysql: db_name assignement properly

[Carsten Leonhardt]

Hi Josu,

> Please, do db_name assignement properly for scripts in
> /usr/share/bacula-director/ as in package bacula-director-pgsql
>
> It should be db_name=${db_name:-bacula} instead of db_name=@db_name@ in
> order to use enviroment variables
>
> As is, scritps can not be used

thank you for taking the time to report this bug.

However, it seems that you have answered the debconf questions about
your database. Your databases should have been set up / updated
automatically.

What exactly were you trying to do? And what is the exact error you are
getting?

The scripts you found there are only for people that don't want to have
their database handled automatically.

Regards,

Carsten

Bug#971391: gnome-core: version number is confusing

[David Bremner]

Package: gnome-core
Version: 1:3.30+3
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

It's confusing that the version of gnome-core is different from the
"gnome version" that it depends on.

According to https://wiki.debian.org/Gnome?action=show&redirect=GNOME,
gnome is currently 3.36.4 in unstable.

I hope this helps.

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

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

Versions of packages gnome-core depends on:
ii  adwaita-icon-theme3.38.0-1
ii  at-spi2-core  2.38.0-2
pn  baobab
pn  caribou   
ii  chromium  83.0.4103.116-3.1
pn  dconf-cli 
ii  dconf-gsettings-backend   0.38.0-1
pn  eog   
ii  evince3.38.0-1
pn  evolution-data-server 
ii  firefox   81.0-2
ii  firefox-esr   78.3.0esr-2
ii  fonts-cantarell   0.111-2
pn  gdm3  
pn  gedit 
pn  gkbd-capplet  
ii  glib-networking   2.64.3-2
pn  gnome-backgrounds 
pn  gnome-bluetooth   
pn  gnome-calculator  
pn  gnome-characters  
pn  gnome-contacts
pn  gnome-control-center  
pn  gnome-disk-utility
pn  gnome-font-viewer 
pn  gnome-keyring 
pn  gnome-logs
pn  gnome-menus   
pn  gnome-online-accounts 
pn  gnome-online-miners   
pn  gnome-session 
pn  gnome-settings-daemon 
pn  gnome-shell   
pn  gnome-shell-extensions
pn  gnome-software
pn  gnome-sushi   
pn  gnome-system-monitor  
pn  gnome-terminal
ii  gnome-themes-extra3.28-1
pn  gnome-user-docs   
pn  gnome-user-share  
ii  gsettings-desktop-schemas 3.36.1-1
pn  gstreamer1.0-packagekit   
ii  gstreamer1.0-plugins-base 1.18.0-2
ii  gstreamer1.0-plugins-good 1.18.0-1
ii  gstreamer1.0-pulseaudio   1.18.0-1
pn  gvfs-backends 
pn  gvfs-fuse 
pn  libatk-adaptor
pn  libcanberra-pulse 
ii  libglib2.0-bin2.66.0-2
pn  libpam-gnome-keyring  
pn  libproxy1-plugin-gsettings
pn  libproxy1-plugin-webkit   
ii  librsvg2-common   2.48.8+dfsg-1
pn  nautilus  
ii  pulseaudio13.0-5
pn  pulseaudio-module-bluetooth   
ii  sound-theme-freedesktop   0.8-2
ii  system-config-printer-common  1.5.12-1
ii  system-config-printer-udev1.5.12-1
pn  totem 
pn  tracker   
ii  yelp  3.38.0-1
ii  zenity3.32.0-5

Versions of packages gnome-core recommends:
pn  libproxy1-plugin-networkmanager  
pn  network-manager-gnome

Versions of packages gnome-core suggests:
pn  gnome  

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl9ziv8ACgkQA0U5G1Wq
FSEwGw/+N5K+ET+9uPgA9NHKZ+OnR23Ftap49iuu3NCCh3c166y8rIhl9r4mRV4j
FA406QNX4p9fGqFq1KTeWHdabJL21am+3Jz98LixnEurinGPnr/ixPAOf5GFa+1c
2zC+aLDG4Yq2GyZQKxQ246Y6+S07RqKa8CGR3cd88FrV/k39PVEEkkt+O7d5nyBA
hoXpbuS9Nz4qvaj8fYDmwYOxe5/szTKLk539KJ20vHOrd//lB5R7Rsu/QeslD/AG
E0rRCZXiVEfTenPWKNhcv05n7VAQczkc/Vs6JffnS8A7SMBndxJd1t6cKtrwY+9j
ecw9IzvCjy1voT+Y8EHe/wmA2idmhmUctzxGe8KdUL3nkHKBBtYKAv/FaVJHzKy0
u40oXcejEkzBj6MGnRq4Iz/fGC8152Eto9XDnm4u2GVuj2lzRoHbHdwKafmJD7qp
CiyT7lbPbjuTpJfmRG86eTPw7QuCMmE8YcMHZynJngZcGWigycsyMpH5I6dcK+Bd
UWj50DnBVlRkKq+FEZhgjDE6XPptzIlvx5ioEGX7m0p+x9roc4MnDpnCa5X60bsn
5iAEUL0cindefn4BcangQjgyj2C9yPsvqVxfD06gJQJOPPGbZeSzWZDlGccopYw9
3ZQqLxhZVi68HRAWLMP3o3RvW9isQJpRMvj8soQPDcb5aMewZoM=
=gRba
-END PGP SIGNATURE-

Bug#971375: libguestfs-tools depends on the kernel (linux-image-amd64) on amd64

[Hilko Bengen]

* Florian La Roche:

> libguestfs-tools depends on linux-image-amd64 for amd64 systems.
> If you only run within a container (lxc), there is usually no kernel
> installed at all.
> (Also you might have different kernels installed.)
>
> Can those dependencies be removed?

Libguestfs and all tools based on it use qemu to spin up a minimal Linux
system that is constructed using supermin. For this it needs a kernel
image and modules, among other things.

Cheers,
-Hilko

Bug#943302: zsnapd: Python2 removal in sid/bullseye

[Andreas Beckmann]

Control: found -1 0.8.11h-3

On Sun, 09 Aug 2020 22:39:52 +0200 Andreas Beckmann  wrote:
> zsnapd FTBFS in a minimal up-to-date sid chroot due to some more changes in
> the python ecosystem:
> 
>  fakeroot debian/rules clean
> dh clean
>dh_auto_clean
> dh_auto_clean: warning: Please use the third-party "pybuild" build system 
> instead of python-distutils
> dh_auto_clean: warning: This feature will be removed in compat 12.
> Can't exec "pyversions": No such file or directory at 
> /usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 124.
> dh_auto_clean: error: failed to run pyversions
> make: *** [debian/rules:14: clean] Error 25

Nothing has changed in -3.

https://buildd.debian.org/status/package.php?p=zsnapd&suite=unstable

> zsnapd (0.8.11h-3) unstable; urgency=medium
> .
>   * Really fix bug about being in wrong section. (Closes: #943302)

That incorrectly references this bug instead of #919595


Andreas

Bug#933063: [debian-mysql] Bug#933063: character_set_client: latin1?

[Georg Richter]

Hi Otto,

in server build you have to pass special options for C/C  - I need to check
it and will get back to you.

/Georg

On Tue, Sep 29, 2020 at 3:42 PM Otto Kekäläinen  wrote:

> Hi!
>
> ti 29. syysk. 2020 klo 7.39 Georg Richter (ge...@mariadb.com) kirjoitti:
> >
> > Hi,
> >
> > if server has default charset utf8mb4 on Debian, why don't you build C/C
> with -DDEFAULT_CHARSET=utf8mb4 ?
>
> Yes, that might be a good solution. I wasn't aware of such an option.
>
> The upstream MariaDB 10.5 has this identical case, should that build
> flag also be applied there and if so, on what branch do you suggest
> (10.6 for future or older)?
>


-- 
Georg Richter, Senior Software Engineer
MariaDB Corporation Ab

Bug#971375: libguestfs-tools depends on the kernel (linux-image-amd64) on amd64

[Florian La Roche]

Hello Hilko Bengen,

right, but the kernel/initrd can be used from any download and are often not
using from the installed system and its Debian packages.

I don't think this dependency makes sense.

best regards,

Florian La Roche

Bug#950329: can be closed

[Wolfram Sang]

Upstream provided version 0.9 with Python3 + Qt5 support. Already
available in Debian testing. Can be closed.



signature.asc
Description: PGP signature

Bug#971390: qemu: CVE-2020-25742

[Salvatore Bonaccorso]

Source: qemu
Version: 1:5.1+dfsg-4
Severity: important
Tags: security upstream
Forwarded: 
https://lists.nongnu.org/archive/html/qemu-devel/2020-09/msg05294.html
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for qemu, filling a bug to
track the issue in BTS.

CVE-2020-25742[0]:
| scsi: lsi: null pointer dereference during memory move

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-25742
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25742
[1] https://lists.nongnu.org/archive/html/qemu-devel/2020-09/msg05294.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#958611: at: Build-Depends on deprecated dh-systemd which is going away

[Michael Biebl]

Control: tags -1 + patch pending

Hi,

I've uploaded a minimal fix to DELAYED/14.
Debdiff is attached.

Please holler, if you want me to cancel the NMU.

Regards,
Michael
diff -Nru at-3.1.23/debian/changelog at-3.1.23/debian/changelog
--- at-3.1.23/debian/changelog  2018-07-24 11:17:21.0 +0200
+++ at-3.1.23/debian/changelog  2020-09-25 13:19:04.0 +0200
@@ -1,3 +1,11 @@
+at (3.1.23-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update Build-Depends to use debhelper (>= 9.20160709) instead of
+dh-systemd. (Closes: #958611)
+
+ -- Michael Biebl   Fri, 25 Sep 2020 13:19:04 +0200
+
 at (3.1.23-1) unstable; urgency=medium
 
   * New release 3.1.23:
diff -Nru at-3.1.23/debian/control at-3.1.23/debian/control
--- at-3.1.23/debian/control2018-07-24 11:17:21.0 +0200
+++ at-3.1.23/debian/control2020-09-25 13:18:33.0 +0200
@@ -6,8 +6,7 @@
 Standards-Version: 3.9.8
 Build-Depends: autotools-dev,
bison,
-   debhelper (>= 9.20160114),
-   dh-systemd,
+   debhelper (>= 9.20160709),
flex,
libfl-dev,
libpam0g-dev,


signature.asc
Description: OpenPGP digital signature

Bug#586415: ITA: tightvnc-java -- TightVNC java applet and command line program

[Sven Geuer]

owner -1 debma...@g-e-u-e-r.de
retitle -1 ITA: tightvnc-java -- TightVNC java applet and cli program

Hi Ola,

I started to work on a refreshed version of this package and intend to
adopt tightvnc-java. You find what I've done so far listed under my
personal salsa projects [1]. I understand that you wanted to let go of
tightvnc-java. Let me know if your intention is a different one today
and you want to keep maintaining the package.

Hi Mike,

I'd like to maintain tightvnc-java under the umbrella of the Debian
Remote Packaging Team as I already do for tightvnc. Please add the
tightvnc-java project to the team repository as soon as Ola gave his
OK.

Cheers,
Sven

[1] https://salsa.debian.org/sven-geuer-guest/tightvnc-java


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

Bug#971389: seascope: Dependency to 'python3-pyqt5.qtsvg' missing, does not start

[Wolfram Sang]

Package: seascope
Version: 0.9+8a669e0e-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

after upgrading to bullseye, starting seascope failed for me:

No module named 'PyQt5.QtSvg'
Error: failed to import supporting packages.
Error: program aborted.

After installing python3-pyqt5.qtsvg manually, the program worked fine.

Kind regards,

   Wolfram


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

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

Versions of packages seascope depends on:
ii  python3 3.8.2-3
ii  python3-pyqt5   5.15.0+dfsg-1+b1
ii  python3-pyqt5.qsci  2.11.2+dfsg-7

Versions of packages seascope recommends:
ii  cscope   15.9-1
ii  exuberant-ctags  1:5.9~svn20110310-13
ii  id-utils 4.6.28-20200521ss15dab+b1

seascope suggests no packages.

-- no debconf information

Bug#958637: slim: Build-Depends on deprecated dh-systemd which is going away

[Michael Biebl]

Control: tags -1 + patch pending

Hi,

I've uploaded a minimal fix to DELAYED/14.
Debdiff is attached.

Please holler, if you want me to cancel the NMU.

Regards,
Michael
diff -Nru slim-1.3.6/debian/changelog slim-1.3.6/debian/changelog
--- slim-1.3.6/debian/changelog 2017-05-02 15:48:36.0 +0200
+++ slim-1.3.6/debian/changelog 2020-09-25 13:22:22.0 +0200
@@ -1,3 +1,11 @@
+slim (1.3.6-5.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update Build-Depends to use debhelper (>= 9.20160709) instead of
+dh-systemd. (Closes: #958637)
+
+ -- Michael Biebl   Fri, 25 Sep 2020 13:22:22 +0200
+
 slim (1.3.6-5.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru slim-1.3.6/debian/control slim-1.3.6/debian/control
--- slim-1.3.6/debian/control   2017-05-02 15:42:52.0 +0200
+++ slim-1.3.6/debian/control   2020-09-25 13:22:20.0 +0200
@@ -3,9 +3,9 @@
 Priority: optional
 Maintainer: Nobuhiro Iwamatsu 
 Uploaders: Jens Peter Secher , Mateusz Łukasik 

-Build-Depends: debconf, debhelper (>= 9), libjpeg-dev, libpam0g-dev,
+Build-Depends: debconf, debhelper (>= 9.20160709), libjpeg-dev, libpam0g-dev,
libpng-dev, libxft-dev, libxmu-dev, po-debconf, sharutils, cmake,
-   freeglut3-dev, libpthread-stubs0-dev, libxrandr-dev, dh-systemd
+   freeglut3-dev, libpthread-stubs0-dev, libxrandr-dev
 Standards-Version: 3.9.6
 Homepage: http://sourceforge.net/projects/slim.berlios/
 


signature.asc
Description: OpenPGP digital signature

Bug#958179: create user-friendly startup configuration

[Francois Marier]

Hi Florian,

I agree it's tricky to get the docs right.

On 2020-09-24 at 19:25:35, Florian Schlichting wrote:
> Historically, the package has shipped a lot of infrastructure for
> running as a system service, and I think having mpd run on a headless
> box somewhere on the home network and being able to control one's music
> remotely is one of its big appeals.

That's closer to my use case, though not quite what I do. It's running on my
desktop computer which I also use as a "home server". My goal is to have:

- mpd working regardless of whether or not I am logged in
- sound working for my user account (e.g. in vlc) without having to stop the
  mpd service

That's probably not a reasonable default use case though.

> However I feel most users would probably be served better by deleting all
> of that infrastructure and configuring mpd to run from their user
> session, just like their pulseaudio, which in my understanding is the
> proper way to solve the permissions problem that Eduard mentions.

That might be the way to go for the default.

> Can we do sensible things for all of these use cases, or should we try
> to do less but have that work out of the box? And what's the default use
> case to be?

I'm sure how to tackle all of this, but perhaps we should identify a few
use cases and document them separately in the README. I can think of three:

1. systemd+pulseaudio in a user session
2. headless server
3. (whatever we call my use case)

Francois

-- 
https://fmarier.org/

Bug#920365: [debian-mysql] Bug#920365: Bug#920365: mariadb_config: improve cross compilation support

[Otto Kekäläinen]

Thanks!

Tested patch in
https://salsa.debian.org/mariadb-team/mariadb-10.5/-/commit/2a8304051a3107fe828314b66b33aca7ecb863d4

Builds went fine, so I'll add this commit on top of the master branch.


The topic of cross-building tangents the multi-arch definitions in the
control file which currently are not correct and I am not sure on how
to correctly solve it without regressions:

W dependency-is-not-multi-archified libmariadb-dev-compat depends on
libmariadb-dev (multi-arch: no)
W dependency-is-not-multi-archified libmariadbd-dev depends on
libmariadb-dev (multi-arch: no)
W dependency-is-not-multi-archified mariadb-plugin-gssapi-client
depends on mariadb-client-10.5 (multi-arch: no)

Bug#958630: numad: Build-Depends on deprecated dh-systemd which is going away

[Michael Biebl]

Control: tags -1 + patch pending

Hi,

I've uploaded a minimal fix to DELAYED/14.
Debdiff is attached.

Please holler, if you want me to cancel the NMU.

Regards,
Michael
diff -Nru numad-0.5+20150602/debian/changelog 
numad-0.5+20150602/debian/changelog
--- numad-0.5+20150602/debian/changelog 2016-11-25 19:44:08.0 +0100
+++ numad-0.5+20150602/debian/changelog 2020-09-25 13:31:42.0 +0200
@@ -1,3 +1,11 @@
+numad (0.5+20150602-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update Build-Depends to use debhelper (>= 9.20160709) instead of
+dh-systemd. (Closes: #958630)
+
+ -- Michael Biebl   Fri, 25 Sep 2020 13:31:42 +0200
+
 numad (0.5+20150602-5) unstable; urgency=medium
 
   * fix systemd doesn't read /etc/default/numad (Closes: #845447)
diff -Nru numad-0.5+20150602/debian/control numad-0.5+20150602/debian/control
--- numad-0.5+20150602/debian/control   2015-09-01 22:17:45.0 +0200
+++ numad-0.5+20150602/debian/control   2020-09-25 13:26:16.0 +0200
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Jeremías Casteglione 
 Uploaders: gustavo panizzo , Kamal Mostafa 

-Build-Depends: debhelper (>= 9),dh-systemd (>= 1.5)
+Build-Depends: debhelper (>= 9.20160709)
 Standards-Version: 3.9.6
 Homepage: https://git.fedorahosted.org/cgit/numad.git
 Vcs-Git: git://anonscm.debian.org/collab-maint/numad.git


signature.asc
Description: OpenPGP digital signature

Bug#953473: homer-api: diff for NMU version 5.0.6+dfsg2-3.2

[Tobias Frost]

Control: tags 953473 + patch
Control: tags 953473 + pending


Dear maintainer,

I've prepared an NMU for homer-api (versioned as 5.0.6+dfsg2-3.2) and
uploaded it to DELAYED/15. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru homer-api-5.0.6+dfsg2/debian/changelog homer-api-5.0.6+dfsg2/debian/changelog
--- homer-api-5.0.6+dfsg2/debian/changelog	2019-04-02 20:06:08.0 +0200
+++ homer-api-5.0.6+dfsg2/debian/changelog	2020-09-29 19:34:22.0 +0200
@@ -1,3 +1,11 @@
+homer-api (5.0.6+dfsg2-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update Uploaders List. Closes: #953473
+  * Update VCS fields to point to salsa.
+
+ -- Tobias Frost   Tue, 29 Sep 2020 19:34:22 +0200
+
 homer-api (5.0.6+dfsg2-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru homer-api-5.0.6+dfsg2/debian/control homer-api-5.0.6+dfsg2/debian/control
--- homer-api-5.0.6+dfsg2/debian/control	2016-09-24 18:55:27.0 +0200
+++ homer-api-5.0.6+dfsg2/debian/control	2020-09-29 19:33:45.0 +0200
@@ -2,14 +2,14 @@
 Section: net
 Priority: optional
 Maintainer: Debian VoIP Team 
-Uploaders: Victor Seva , Daniel Pocock , Konstantin S. Vishnivetsky 
+Uploaders: Victor Seva , Konstantin S. Vishnivetsky 
 Build-Depends:  debhelper (>= 9.0.0),
 debconf,
 dh-apache2, apache2-dev
 Standards-Version: 3.9.8
 Homepage: http://sipcapture.org
-Vcs-Git: git://anonscm.debian.org/git/pkg-voip/homer-api.git
-Vcs-Browser: https://anonscm.debian.org/cgit/pkg-voip/homer-api.git
+Vcs-Git: https://salsa.debian.org/pkg-voip-team/homer-api.git -b debian/sid
+Vcs-Browser: https://salsa.debian.org/pkg-voip-team/homer-api
 
 Package: homer-api
 Architecture: any

Bug#970653: Acknowledgement (ITP: vguitar -- Play Guitar in any term w/ MIDI synthesizer)

[Nick Strauss]

All,
I have updated the repo to version 2.7.
Changes include:
bending a note, strumming with alternate tunings, headless operation
both tab and strum, boxmode fret markings,  bugfix create
input if file not found, bugfix 21 frets.

Nick Strauss
http://apt.nick-strauss.com/apt/debian 
https://www.nick-strauss.com
(apt-key adv --keyserver keyserver.ubuntu.com --recv-keys AB406C34)

Bug#956836: Update: Bitwarden is a dependency headache

[calumlikesapplepie]

I figure I ought to post an update here.  It's not looking good.

There is a very nifty tool for repackaging node.js packages for Debian
(shockingly called npm2deb), however, it assumes upstream uploaded
their package to the npm registry.  The bitwarden upstream did not, as
it is a GUI application, and so they didn't know they even could.  They
did not want to, however.

I then patched npm2deb to handle packages that were only available as
tarballs (which I was quite proud of).  Though those changes have not
yet been merged in, they worked just fine-which was when I ran into the
showstopper.

Bitwarden has a long chain of dependencies, as it is an application
built on Angular.js and Electron.js.  npm2deb gave a list of 28
separate packages.  Although they are all node packages, and I am sure
npm2deb is up to the task, I am not sure if I could, or should, add
them all.  I pasted the relevant section of npm2deb output bellow.  

If someone could aid me in packaging and maintaining the dependent
packages, I'd be much more confident in continuing.  But I don't want
to wait for my 29th package to get one that I actually use.

(Obviously, many of these may be prepackaged, and just not be known to
npm2deb by their Debian name.  But there is a mechanism that attempts
to solve that (with a list that converts between them), and I assume it
is somewhat up-to-date.  Additionally, I did manually attempt to find
them with apt, and failed.)

[error]   @angular/animations: dependency node-@angular/animations not
in debian
 [error]   @angular/cdk: dependency node-@angular/cdk not in debian
 [error]   @angular/common: dependency node-@angular/common not in
debian
 [error]   @angular/compiler: dependency node-@angular/compiler not in
debian
 [error]   @angular/core: dependency node-@angular/core not in debian
 [error]   @angular/forms: dependency node-@angular/forms not in debian
 [error]   @angular/platform-browser: dependency node-@angular/platform
-browser not in debian
 [error]   @angular/platform-browser-dynamic: dependency node-@angular/
platform-browser-dynamic not in debian
 [error]   @angular/router: dependency node-@angular/router not in
debian
 [error]   @angular/upgrade: dependency node-@angular/upgrade not in
debian
 [error]   @microsoft/signalr: dependency node-@microsoft/signalr not
in debian
 [error]   @microsoft/signalr-protocol-msgpack: dependency 
node-@microsoft/signalr-protocol-msgpack not in debian
 [error]   @nodert-win10-rs4/windows.security.credentials.ui:
dependency node-@nodert-win10-rs4/windows.security.credentials.ui not
in debian
 [error]   angular2-toaster: dependency node-angular2-toaster not in
debian
 [error]   angulartics2: dependency node-angulartics2 not in debian
 [error]   big-integer: dependency node-big-integer not in debian
 [error]   desktop-idle: dependency node-desktop-idle not in debian
 [error]   duo_web_sdk: dependency node-duo_web_sdk not in debian
 [error]   electron-log: dependency node-electron-log not in debian
 [error]   electron-store: dependency node-electron-store not in debian
 [error]   electron-updater: dependency node-electron-updater not in
debian
 [error]   keytar: dependency node-keytar not in debian
 [error]   nord: dependency node-nord not in debian
 [error]   papaparse: dependency node-papaparse not in debian
 [error]   rxjs: dependency node-rxjs not in debian
 [error]   sweetalert2: dependency node-sweetalert2 not in debian
 [error]   zone.js: dependency node-zone.js not in debian
 [error]   zxcvbn: dependency node-zxcvbn not in debian



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

Bug#971388: RFS: golang-github-dkolbly-wl/0.0~git20180220.b06f57e-1 [ITP] -- Golang wayland protocol implementation. (library)

[Arun Kumar Pariyar]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "golang-github-dkolbly-wl":

 * Package name: golang-github-dkolbly-wl
   Version : 0.0~git20180220.b06f57e-1
   Upstream Author : https://github.com/dkolbly/wl/issues
 * URL : https://github.com/dkolbly/wl
 * License : BSD-2-clause
 * Vcs : 
https://salsa.debian.org/go-team/packages/golang-github-dkolbly-wl
   Section : devel

It builds those binary packages:

  golang-github-dkolbly-wl-dev - Golang wayland protocol implementation. 
(library)

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

  https://mentors.debian.net/package/golang-github-dkolbly-wl/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/g/golang-github-dkolbly-wl/golang-github-dkolbly-wl_0.0~git20180220.b06f57e-1.dsc

Changes for the initial release:

 golang-github-dkolbly-wl (0.0~git20180220.b06f57e-1) unstable; urgency=medium
 .
   * Initial release (Closes: #971042)

Regards,
--
  Arun Kumar Pariyar



signature.asc
Description: OpenPGP digital signature

Bug#813630: [libphonenumber6-dev] Missing 'template_util.h' from "base/memory/scoped_ptr.h"

[Tobias Frost]

Package: libphonenumber6-dev
Followup-For: Bug #813630
Control: fixed -1 7.1.0-5
Control: done -1

This seems to be fixed in libphonenumber7-dev, at least the file is there…
Marking as fixed in this version and closing the bug.
If you can reproduce it in this version, please feel free to reopen the bug.

Thanks!

Bug#934738: Experimental gettext 0.21 packages available

[Santiago Vila]

Thanks a lot for this work!

I think the best course of action is that I upload it almost "as is" for 
unstable.
(I see how you avoided the new binary packages).

Thanks.

Bug#971387: update-glx does not update libglx.so to NVIDIA's (340)

[Tomasz Wolak]

Package: update-glx
Version: 1.0.0
Severity: normal

Dear Maintainer,

After a recent update of the system (Debian 10, stable), which included updates
of
*nvidia* and *glx* packages, the GLX interface stopped working - Xorg's log:
--
[  2439.150] Loading extension GLX
(...)
[  2439.159] (EE) NVIDIA(0): Failed to initialize the GLX module; please check
i
n your X
[  2439.159] (EE) NVIDIA(0): log file that the GLX module has been loaded
in you
r X
[  2439.159] (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX
modul
e.  If
[  2439.159] (EE) NVIDIA(0): you continue to encounter problems, Please try
[  2439.159] (EE) NVIDIA(0): reinstalling the NVIDIA driver.
-
Reconfiguring using update-alternatives --config glx and setting as follows:

# update-alternatives --config glx
There are 3 choices for the alternative glx (providing /usr/lib/glx).

  SelectionPath   Priority   Status

  0/usr/lib/nvidia 100   auto mode
  1/usr/lib/mesa-diverted  5 manual mode
* 2/usr/lib/nvidia 100   manual mode
  3/usr/lib/nvidia/bumblebee   95manual mode

did not help. Also, reconfiguring nvidia's drivers (which are set to
/usr/lib/nvidia/legacy-340xx), made no change.

I found out that the problem was with the library:
/usr/lib/xorg/modules/extensions/libglx.so

which is loaded by the Xorg server.
My system has the following libglx libraries installed:

# dpkg -S libglx.so
xserver-xorg-core: /usr/lib/xorg/modules/extensions/libglx.so
xserver-xorg-video-nvidia-legacy-340xx:
/usr/lib/nvidia/legacy-340xx/libglx.so.340.108
xserver-xorg-video-nvidia-legacy-340xx: /usr/lib/nvidia/legacy-340xx/libglx.so

and manual overwriting the
/usr/lib/xorg/modules/extensions/libglx.so
with
/usr/lib/nvidia/legacy-340xx/libglx.so
fixed the issue.

As far as I know, these drivers (340) have no support from NVidia anymore,
so I do not know whether it will be maintained for Debian, but maybe it is
still
worth to fix...

One more thing - the problem existed also before (I fixed this on my box
in the same way some months ago).

Hope it helps.

Regards,
Tomasz



-- Package-specific info:
Diversions:
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.0.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.7.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.7.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.2.0 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.1.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLX_indirect.so.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLX_indirect.so.0 by 
glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.0.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.0.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.

Bug#971384: loganalyzer: diff for NMU version 4.1.5+dfsg-2.1

[Tobias Frost]

Package: loganalyzer
Version: 4.1.5+dfsg-2
Severity: normal
Tags: patch  pending


Dear maintainer,

I've prepared an NMU for loganalyzer (versioned as 4.1.5+dfsg-2.1) and
uploaded it to DELAYED/15. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru loganalyzer-4.1.5+dfsg/debian/changelog loganalyzer-4.1.5+dfsg/debian/changelog
--- loganalyzer-4.1.5+dfsg/debian/changelog	2017-04-17 09:07:36.0 +0200
+++ loganalyzer-4.1.5+dfsg/debian/changelog	2020-09-29 18:44:54.0 +0200
@@ -1,3 +1,11 @@
+loganalyzer (4.1.5+dfsg-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Updating the Uploaders list (Closes: #953497)
+  * Update VCS fields to pointto salsa (Closes: #971383)
+
+ -- Tobias Frost   Tue, 29 Sep 2020 18:44:54 +0200
+
 loganalyzer (4.1.5+dfsg-2) unstable; urgency=high
 
   * Add cron job to purge old records from database.
diff -Nru loganalyzer-4.1.5+dfsg/debian/control loganalyzer-4.1.5+dfsg/debian/control
--- loganalyzer-4.1.5+dfsg/debian/control	2017-04-17 08:34:28.0 +0200
+++ loganalyzer-4.1.5+dfsg/debian/control	2020-09-29 18:42:23.0 +0200
@@ -2,12 +2,11 @@
 Section: net
 Priority: optional
 Maintainer: Debian Monitoring Maintainers 
-Uploaders: Daniel Pocock 
 Homepage: http://loganalyzer.adiscon.com/
 Build-Depends: debhelper (>= 9.0.0), po-debconf
 Standards-Version: 3.9.5
-Vcs-Git: git://anonscm.debian.org/pkg-monitoring/loganalyzer.git
-Vcs-Browser: http://anonscm.debian.org/cgit/pkg-monitoring/loganalyzer.git
+Vcs-Git: https://salsa.debian.org/monitoring-team/loganalyzer.git
+Vcs-Browser: https://salsa.debian.org/monitoring-team/loganalyzer
 
 Package: loganalyzer
 Architecture: all

Bug#971386: RFS: golang-github-kelvins-sunrisesunset/1.0-1 [ITP] -- Go package that provides the sunrise and sunset equation.

[Arun Kumar Pariyar]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "golang-github-kelvins-sunrisesunset":

 * Package name: golang-github-kelvins-sunrisesunset
   Version : 1.0-1
   Upstream Author : Kelvin S. do Prado 
 * URL : https://github.com/kelvins/sunrisesunset
 * License : Expat
 * Vcs : 
https://salsa.debian.org/go-team/packages/golang-github-kelvins-sunrisesunset
   Section : devel

It builds those binary packages:

  golang-github-kelvins-sunrisesunset-dev - Go package that provides the 
sunrise and sunset equation. (library)

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

  https://mentors.debian.net/package/golang-github-kelvins-sunrisesunset/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/g/golang-github-kelvins-sunrisesunset/golang-github-kelvins-sunrisesunset_1.0-1.dsc

Changes for the initial release:

 golang-github-kelvins-sunrisesunset (1.0-1) unstable; urgency=medium
 .
   * Initial release (Closes: #971046)

Regards,
--
  Arun Kumar Pariyar



signature.asc
Description: OpenPGP digital signature

Bug#956621: loganalyzer: New upstream version 4.1.10 available.

[Tobias Frost]

Control: retitle -1 loganalyzer: New upstream version 4.1.11 available.

In the meantime, 4.1.11 has now been released.

Bug#971383: loganalyzer: VCS fields point to alioth, but there is a salsa repo.

[Tobias Frost]

Package: loganalyzer
Severity: normal

Repo @ Salsa:
https://salsa.debian.org/monitoring-team/loganalyzer

Bug#934738: Bug#968264: Experimental gettext 0.21 packages available

[Santiago Vila]

On Tue, Sep 29, 2020 at 11:52:49AM -0400, Zack Weinberg wrote:

> I did *not* change the set of binary packages at all,

I'm curious: How did you manage to update gettext *without* introducing
new binary packages? How this compares with my last attempt here?

https://people.debian.org/~sanvila/gettext/

Thanks.

Bug#953500: Updating the node-merge Uploaders list

[Tobias Frost]

Source: node-merge
Followup-For: Bug #953500
Control: tags -1 patch

Patch in MR: https://salsa.debian.org/js-team/node-merge/-/merge_requests/1

Bug#956620: node-util: New upstream version 0.12.2 available.

[Tobias Frost]

Control: retitle -1  node-util: New upstream version 0.12.3 available.

0.12.3 has been released in the meantime.

Bug#971382: node-websocket: New upstream release 1.0.32

[Tobias Frost]

Package: node-websocket
Severity: wishlist

Dear Maintainer,

There is a new upstream release (tagged on Aug 28th 2020)
Please package it for Debian!

-- 
Cheers,
tobi

Bug#971359: golang-google-api-dev: circular dependency with golang-google-cloud-dev

[Drew Parsons]

On 2020-09-29 22:47, Shengjing Zhu wrote:
On Tue, Sep 29, 2020 at 9:15 PM Drew Parsons  
wrote:


Package: golang-google-api-dev
Followup-For: Bug #971359

golang-google-api-dev and golang-google-cloud certainly do require
each other. The Go ecosystem is kind of stupid that way.

Requirements are declared in the go.mod files:

google.golang.org/api [0.28.0] requires cloud.google.com/go v0.56.0

cloud.google.com/go [0.56.0] requires google.golang.org/api v0.20.0

You can see it's a bootstrapping problem.



It does have bootstrapping issues.
But this circular complaint seems to be the -dev packages.
google.golang.org/api only needs cloud.google.com/go/compute/metadata
in its idtoken package.
We have golang-google-cloud-compute-metadata-dev which is to address 
this issue.



Thanks Shengjing, and thanks for uploading 0.28.0-2!

Drew

Bug#953504: Updating the node-websocket Uploaders list

[Tobias Frost]

Source: node-websocket
Followup-For: Bug #953504
Control: tags -1 patch

Patch in MR https://salsa.debian.org/js-team/node-websocket/-/merge_requests/2

Bug#934738: Experimental gettext 0.21 packages available

[Zack Weinberg]

Work I'm doing on Autoconf is now also blocked by the out-of-date
gettext in Debian, for reasons too tedious to get into, so I've
prepared experimental packages of gettext 0.21.  Get them from
https://research.owlfolio.org/scratchpad/debian -- this URL should
work as an apt source line, but beware that experimental packages of
the recent upstream beta of autoconf are also present.

I addressed a number of outstanding bugs and lintian complaints while
I was at it (the full changelog is at the bottom of this message, for
your interest); most importantly, I removed the dependency on libcroco
(bug #967028).  I did *not* change the set of binary packages at all,
because it wasn't clear to me what changes should be made.  Nor did I
revise the copyright file beyond updating the copyright years.  (I did
run scan-copyrights, the result of which is in
debian/copyright.dep5.raw, but it would clearly need a great deal of
manual revision and I don't have time for that any more than Santiago
does.  I've already spent two full days on this.)

I hope this is useful to at least some of you.  I don't plan to do any
further work on gettext myself, but please feel free to take what I
have done and build on it.

zw

gettext (0.21-0.1) experimental; urgency=medium

  * Non-maintainer upload to experimental.
  * New upstream version 0.21 released July 2020.
- xgettext can detect ‘(eval_)gettext -e’ in shell scripts. Closes: #507091.
-  compiles cleanly as C++. Closes: #547798.
- The unpacked usr/share/gettext/intl is no longer installed.
  If you were using these files, find them in
  /usr/share/gettext/archive.dir.tar.xz, which is part of the
  autopoint package.
- New upstream signing key added to signing-key.asc:
  "Bruno Haible (Open Source Development) "
  9001 B85A F9E1 B83D F1BD  A942 F5BE 8B26 7C6A 406D

  * Patches that are no longer necessary:
- 01-do-not-use-java-in-urlget.patch: Replaced with logic in debian/rules.
- 02-msgfmt-remove-pot-creation-date.patch: Merged upstream.
- 03-avoid-extraneous-nul-bytes.patch: Merged upstream.
- 04-fix-msgunfmt-heap-corruption.patch: Merged upstream.
- 05-fix-crash-xgettext-with-its.patch: Merged upstream.
- 06-java9-support.patch: Merged upstream.
- 07-java11-support.patch: Merged upstream.
- 08-java-future-support.patch: Merged upstream.
- 09-fix-crash-with-po-file-input.patch: Merged upstream.

  * New patches:
- NF-use-system-help2man.patch: Use system help2man instead of
  embedded help2man. Closes: #949338.
- NF-library-dependencies.patch: Link all libraries and
  executables against all of their dependencies, correctly.
  (Latent upstream bug, exposed by hardening.)
- NF-disable-libtextstyle.patch: Do not build libtextstyle.
  We never packaged it, and it depends on libcroco, which is
  unmaintained and has known security bugs.  Use the Gnulib
  libtextstyle-dummy module (already included in the upstream
  sources) to satisfy various programs’ use of libtextstyle.
  Note that this means those programs’ --color options
  silently do nothing. Closes: #967028.

  * Debhelper compat level 13 (current recommended).
- Switch to dh sequencing.
- Switch to Build-Depends: debhelper-compat.
- Switch to declarative package contents, using dh_install etc.
  dh-exec is needed for build profile filtering in a few places.
  (The old scripting is preserved in debian/rules.old.)
- Manual ldconfig triggers are no longer necessary.
- The HTML documentation and examples are now installed in
  /usr/share/doc/gettext instead of .../gettext-doc.

  * gettext-el is now created using dh_elpa, eliminating the need for
custom package scripts.

  * Standards-Version: 4.5.0.
- All lintian E-level diagnostics have been addressed, and
  many but not all of the W- and I-level diagnostics.
- I don’t *think* any specific changes were required besides the
  above, but I could have missed something.

Bug#971381: bacula-director-mysql: db_name assignement properly

[Josu]

Package: bacula-director-mysql
Version: 9.4.2-2+deb10u1
Severity: important

Dear Maintainer,

Please, do db_name assignement properly for scripts in
/usr/share/bacula-director/ as in package bacula-director-pgsql

It should be db_name=${db_name:-bacula} instead of db_name=@db_name@ in
order to use enviroment variables

As is, scritps can not be used

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

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

Versions of packages bacula-director-mysql depends on:
hi bacula-common-mysql 9.4.2-2+deb10u1
ii dbconfig-mysql 2.0.11+deb10u1
ii debconf [debconf-2.0] 1.5.71
ii default-mysql-client 1.0.5
ii mariadb-client-10.3 [virtual-mysql-client] 1:10.3.23-0+deb10u1

Versions of packages bacula-director-mysql recommends:
ii default-mysql-server 1.0.5
ii mariadb-server-10.3 [virtual-mysql-server] 1:10.3.23-0+deb10u1

Versions of packages bacula-director-mysql suggests:
ii gawk 1:4.2.1+dfsg-1

-- debconf information:
bacula-director-mysql/upgrade-error: abort
bacula-director-mysql/upgrade-backup: true
bacula-director-mysql/missing-db-package-error: abort
bacula-director-mysql/db/app-user: bacula@localhost
bacula-director-mysql/dbconfig-reinstall: false
bacula-director-mysql/mysql/method: Unix socket
bacula-director-mysql/remote/newhost:
bacula-director-mysql/dbconfig-remove: true
bacula-director-mysql/remote/host: localhost
bacula-director-mysql/purge: false
bacula-director-mysql/install-error: abort
bacula-director-mysql/remove-error: abort
* bacula-director-mysql/dbconfig-install: true
bacula-director-mysql/database-type: mysql
bacula-director-mysql/db/dbname: bacula
* bacula-director-mysql/mysql/admin-user: root
bacula-director-mysql/internal/reconfiguring: false
bacula-director-mysql/internal/skip-preseed: false
bacula-director-mysql/dbconfig-upgrade: true
bacula-director-mysql/passwords-do-not-match:
bacula-director-mysql/remote/port:

Bug#953502: Updating the node-typedarray-to-buffer Uploaders list

[Tobias Frost]

Source: node-typedarray-to-buffer
Followup-For: Bug #953502
Control: tags -1 patch

Patch in MR: Updating the Uploaders List (Closing: #953502)

Bug#953503: Fixed in MR1

[Tobias Frost]

Control: tags -1 patch

Fixes for both bugs are in this MR: 
https://salsa.debian.org/js-team/node-util/-/merge_requests/1

--
tobi



signature.asc
Description: PGP signature