Bug#993643: thunderbird: addon installation broken in 91

2021-09-03 Thread Carsten Schoenert

Control: forcemerge -1 993594

Hello Reuben,

Am 04.09.21 um 07:39 schrieb Reuben:

Package: thunderbird
Version: 1:91.0.2-1
Severity: important

https://bugzilla.mozilla.org/show_bug.cgi?id=1727113

Apparently it tries to verify as per upstream report.

It cam be fixed by compiling with
export MOZ_REQUIRE_SIGNING=


this was already reported on #993594. Fix is hopefully on the way.

https://bugs.debian.org/993594

Please check for existing bug reports before sending a new report. It 
costs time to manage various bug reports about the same topic.

Thanks!

--
Regards
Carsten



Bug#993644: Program search dirs contains many duplicated directories

2021-09-03 Thread Josh Triplett
Package: gcc-11
Version: 11.2.0-4
Severity: normal
X-Debbugs-Cc: j...@joshtriplett.org

The GCC program search dirs contain many duplicated directories. Every time GCC
has to search for a file, it's doing the same searches repeatedly, and
this adds up.

$ gcc-11 -print-search-dirs | grep '^programs:'
programs: 
=/usr/lib/gcc/x86_64-linux-gnu/11/:/usr/lib/gcc/x86_64-linux-gnu/11/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/11/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/11/../../../../x86_64-linux-gnu/bin/x86_64-linux-gnu/11/:/usr/lib/gcc/x86_64-linux-gnu/11/../../../../x86_64-linux-gnu/bin/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/11/../../../../x86_64-linux-gnu/bin/

The first five entries of this are:
/usr/lib/gcc/x86_64-linux-gnu/11/
/usr/lib/gcc/x86_64-linux-gnu/11/
/usr/lib/gcc/x86_64-linux-gnu/
/usr/lib/gcc/x86_64-linux-gnu/11/
/usr/lib/gcc/x86_64-linux-gnu/

Net result, as seen in strace from just one gcc invocation:
24060 stat("/usr/lib/gcc/x86_64-linux-gnu/11/x86_64-linux-gnu-as", 
0x7ffe844509a0) = -1 ENOENT (No such file or directory)
24060 stat("/usr/lib/gcc/x86_64-linux-gnu/11/as", 0x7ffe844509f0) = -1 ENOENT 
(No such file or directory)
24060 stat("/usr/lib/gcc/x86_64-linux-gnu/11/x86_64-linux-gnu-as", 
0x7ffe844509a0) = -1 ENOENT (No such file or directory)
24060 stat("/usr/lib/gcc/x86_64-linux-gnu/11/as", 0x7ffe844509f0) = -1 ENOENT 
(No such file or directory)
24060 stat("/usr/lib/gcc/x86_64-linux-gnu/x86_64-linux-gnu-as", 0x7ffe844509a0) 
= -1 ENOENT (No such file or directory)
24060 stat("/usr/lib/gcc/x86_64-linux-gnu/as", 0x7ffe844509f0) = -1 ENOENT (No 
such file or directory)
24060 stat("/usr/lib/gcc/x86_64-linux-gnu/11/x86_64-linux-gnu-as", 
0x7ffe844509a0) = -1 ENOENT (No such file or directory)
24060 stat("/usr/lib/gcc/x86_64-linux-gnu/11/as", 0x7ffe844509f0) = -1 ENOENT 
(No such file or directory)
24060 stat("/usr/lib/gcc/x86_64-linux-gnu/x86_64-linux-gnu-as", 0x7ffe844509a0) 
= -1 ENOENT (No such file or directory)
24060 stat("/usr/lib/gcc/x86_64-linux-gnu/as", 0x7ffe844509f0) = -1 ENOENT (No 
such file or directory)
...
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/11/real-ld", 0x7ffd16d67830) = -1 
ENOENT (No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/11/real-ld", 0x7ffd16d67830) = -1 
ENOENT (No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/real-ld", 0x7ffd16d67830) = -1 ENOENT 
(No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/11/real-ld", 0x7ffd16d67830) = -1 
ENOENT (No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/real-ld", 0x7ffd16d67830) = -1 ENOENT 
(No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/11/collect-ld", 0x7ffd16d67830) = -1 
ENOENT (No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/11/collect-ld", 0x7ffd16d67830) = -1 
ENOENT (No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/collect-ld", 0x7ffd16d67830) = -1 
ENOENT (No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/11/collect-ld", 0x7ffd16d67830) = -1 
ENOENT (No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/collect-ld", 0x7ffd16d67830) = -1 
ENOENT (No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/11/ld", 0x7ffd16d67830) = -1 ENOENT 
(No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/11/ld", 0x7ffd16d67830) = -1 ENOENT 
(No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/ld", 0x7ffd16d67830) = -1 ENOENT (No 
such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/11/ld", 0x7ffd16d67830) = -1 ENOENT 
(No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/ld", 0x7ffd16d67830) = -1 ENOENT (No 
such file or directory)
...
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/11/gnm", 0x7ffd16d67830) = -1 ENOENT 
(No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/11/gnm", 0x7ffd16d67830) = -1 ENOENT 
(No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/gnm", 0x7ffd16d67830) = -1 ENOENT (No 
such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/11/gnm", 0x7ffd16d67830) = -1 ENOENT 
(No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/gnm", 0x7ffd16d67830) = -1 ENOENT (No 
such file or directory)
...
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/11/nm", 0x7ffd16d67830) = -1 ENOENT 
(No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/11/nm", 0x7ffd16d67830) = -1 ENOENT 
(No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/nm", 0x7ffd16d67830) = -1 ENOENT (No 
such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/11/nm", 0x7ffd16d67830) = -1 ENOENT 
(No such file or directory)
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/nm", 0x7ffd16d67830) = -1 ENOENT (No 
such file or directory)
...
24063 stat("/usr/lib/gcc/x86_64-linux-gnu/11/gstrip", 0x7ffd16d67830) = -1 
ENOENT (No such file or directory)
24063 

Bug#993507: libgnutls30: fails to negotiate X25519 where NSS & OpenSSL succeed, success with X448

2021-09-03 Thread Andreas Metzler
On 2021-09-02 Lionel Élie Mamane  wrote:
> tags 993507 +upstream
> forwarded 993507 https://gitlab.com/gnutls/gnutls/-/issues/1249
> retitle 993507 libgnutls30: client 'illegal parameter' error when both X25519 
> and X448 are enabled and the server picks one of those
[...]
> It is not immediately obvious to me in what released version that
> upstream bug is fixed.

Hello Lionel,

None, the bug was closed (via merge frequest) on June 25, the latest
release (3.7.2) dates back to May 29.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



Bug#993633: [Pkg-rust-maintainers] Bug#993633: debcargo does not honour global summary/description

2021-09-03 Thread Wolfgang Silbermayr
On 9/4/21 12:58 AM, Ian Jackson wrote:

> Here is the fix.  This in the form of a git-formwat-patch.
> Obviously, I used git.  The vcs-git pointed to the debcargo-conf tree,
> so I just used the .dsc import that dgit gave me.

Thanks for the fix, gave it a test run and it looks good to me.

I imported the patchset into a MR on the debcargo project on Salsa.
https://salsa.debian.org/rust-team/debcargo/-/merge_requests/33



Bug#991778: dlint: Dlint fails to find version number of dig

2021-09-03 Thread Paul Wise
Control: severity -1 important
Control: tags -1 + unreproducible

On Sun, 01 Aug 2021 19:00:34 +0200 Patrik Schindler wrote:

> On my Debian Buster system, dig fails to work with
> 
> ;; This program requires DiG version 2.1 or newer, which I cannot find.

I can't reproduce this in a Debian buster chroot.

Could you investigate more closely why it fails on your system?

> Checking on this, I saw that the "ver" call in line 109 doesn't output a
> version number anymore. So I changed that to dig -v.

The command there still works for me in buster:

$ dig localhost any | grep DiG | head -1 | sed -e 's/.*DiG \([0-9.]*\).*/\1/'
9.11.5

> The following replacement for line 109 works for me.
> 
> ver=`dig -v 2>&1 | grep DiG | head -1 | sed -e 's/^DiG \([0-9.]\+\).*$/\1/'`

This seems like a much more correct way to check the version,
so it should be used instead anyway.

> Versions of packages dlint depends on:
> ii  dnsutils  1:9.11.5.P4+dfsg-5.1+deb10u5

I also have 1:9.11.5.P4+dfsg-5.1+deb10u5.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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


Bug#993594: thunderbird: No (official) extension can be installed anymore

2021-09-03 Thread Carsten Schoenert
Control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1727113
Control: tags -1 upstream

Hello Vincent,

Am 03.09.21 um 15:53 schrieb Vincent Danjean:
>   Hi,
> 
>   I just tried thunderbird 91.0.2 from experimental. Once upgraded,
> no extension can be installed / upgraded anymore.
> 
>   To check that this does not come from my profile/setup, I
> installed thunderbird/experimental in a fresh virtual machine.
> Then, I tried to install some of the recommended add-ons (from
> the thunderbird add-on manager). I got popup with the following
> error messages:
> "Thunderbird has prevented this site from installing an
> unverified add-on"
> I tried the following extension (the first proposed):
> - Addon Compatibility Check for TB 91
> - Thunderbird Conversations
> - Quecktext
> - Dictionary for recipient
> - CardBook

this is upstream issue 1727113 [1] which is already marked as fixed
upstream, but targeted for 93.0b1 and 91.1.1. I'll try to backport the
fix into 91.1.0.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1727113

-- 
Regards
Carsten



Bug#993641: linux: enable 64-bit tmpfs inode allocation

2021-09-03 Thread Harlan Lieberman-Berg
On Sat, Sep 4, 2021 at 12:00 AM Harlan Lieberman-Berg
 wrote:
> I will be making an MR in Gitlab to this effect.

This has been done as
https://salsa.debian.org/kernel-team/linux/-/merge_requests/389.

Sincerely,
-- 
Harlan Lieberman-Berg
~hlieberman



Bug#993642: ceph: FTBFS on powerpc

2021-09-03 Thread Mattias Ellert
Source: ceph
Version: 14.2.21-1
Severity: important
Tags: ftbfs fixed-upstream patch
Control: forwarded -1 https://github.com/ceph/ceph/pull/42962
Control: found -1 14.2.20-2
Control: found -1 14.2.20-1
Control: found -1 14.2.18-1
Control: found -1 14.2.16-2
Control: found -1 14.2.16-1
Control: found -1 14.2.15-4
Control: found -1 14.2.15-3
Control: found -1 14.2.15-2
Control: found -1 14.2.15-1
Control: found -1 14.2.9-1
Control: found -1 14.2.8-2
Control: found -1 14.2.8-1
Control: found -1 14.2.7-1
Control: found -1 14.2.6-5
Control: found -1 14.2.6-4
Control: found -1 14.2.6-3
Control: found -1 14.2.6-2
Control: found -1 14.2.6-1
Control: found -1 14.2.5-3
Control: found -1 14.2.5-2
Control: found -1 14.2.5-1
Control: found -1 14.2.4-9
Control: found -1 14.2.4-8
Control: found -1 14.2.4-7
Control: found -1 14.2.4-6
Control: found -1 14.2.4-5
Control: found -1 14.2.4-4
Control: found -1 14.2.4-3
Control: found -1 14.2.4-2
Control: found -1 12.2.11+dfsg1-2.1
Control: found -1 12.2.11+dfsg1-2
Control: found -1 12.2.11+dfsg1-1
Control: found -1 12.2.10+dfsg1-1
Control: found -1 12.2.8+dfsg1-5
Control: found -1 12.2.8+dfsg1-4
Control: found -1 12.2.8+dfsg1-3
Control: found -1 12.2.8+dfsg1-2
Control: found -1 12.2.8+dfsg1-1

I filed a merge request on salsa a week ago (Aug 26) regarding this:
https://salsa.debian.org/ceph-team/ceph/-/merge_requests/7

It has not received any comments so far.

Since the fix has now been merged upstream, are there any objections to
me uploading an NMU with the fix?

The patch with the fix from upstream is in the merge request.

Mattias



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


Bug#993641: linux: enable 64-bit tmpfs inode allocation

2021-09-03 Thread Harlan Lieberman-Berg
Source: linux
Version: 5.10.46-4
Severity: normal
Tags: patch
X-Debbugs-Cc: hlieber...@debian.org

Hello Kernel maintainers,

Due to a bug in tmpfs handling of inodes, it's possible to run into inode
collisions on heavily loaded tmpfs filesystems. This problem is described in
detail in
https://chrisdown.name/2021/07/02/tmpfs-inode-corruption-introducing-inode64.html
and has been applied by default in Arch.

Considering the potential for extremely hard to track failures and the fact that
this has been widely deployed already, I suggest that we enable
CONFIG_TMPFS_INODE64 by default.

I will be making an MR in Gitlab to this effect.

Sincerely,

--
Harlan Lieberman-Berg
~hlieberman



Bug#993639: bullseye-pu: package pyx3/0.15-3+deb11u1

2021-09-03 Thread Stuart Prescott
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: stu...@debian.org

Dear Release Team,

I would like to update the pyx3 source package in bullseye to fix a nasty
bug in its text layout that makes it more-or-less unusable at present
(#992656).

[ Reason ]
An incompatibility between the pyx3 and texlive in the bullseye release
means that text box alignment is broken in plots generated by pyx. The
result is unreadable plots where, for example, the tick labels are vertically
displaced, with the y-tick labels perhaps being next to the wrong tick
mark, and the x-tick labels being cropped off the bottom of the image.
Upstream reported this bug and even indicated the appropriate patch to
cherry-pick (see #992656).

[ Impact ]
pyx3 in bullseye is not usable with the 'LatexEngine' text engine; the
alternative text engine (typesetting using plain TeX) is fine for some work,
but many users would use LatexEngine as the text engine across all plots.
While it is not the default text engine that it is broken, it widely used
such that it is worth updating in bullseye.

[ Tests ]
PyX has a test suite that is run and passes at build time. However, the test
suite does not check for the visual correctness of the output which is where
this bug lies. I have manually tested the updated packages using the test case
provided by upstream in #992656 to verify that the bug is indeed fixed. I
have also checked other output from the update pyx3 package.

[ Risks ]
This is an upstream patch that was identified by upstream as being appropriate
for the bullseye-pu. The actual change is a single line of LaTeX macro usage
in configuring the text engine.

[ Checklist ]
  [✔] *all* changes are documented in the d/changelog
  [✔] I reviewed all changes and I approve them
  [✔] attach debdiff against the package in (old)stable
  [✔] the issue is verified as fixed in unstable

[ Changes ]
Only one change: The LatexEngine configuration is switched to use a different
PyX macro that allows the correct alignment of the text in the output.

[ Other info ]
This bug is already fixed in unstable and testing (version 0.15-4); the only
difference between the version in unstable and the debdiff proposed here is
the changelog entry. My manual testing of this fix was undertaken against both
the 0.15-3+deb11u1 and 0.15-4 packages installed into their respective
releases.

Thanks for your assistance with this bullseye-pu.
Stuart
diff -Nru pyx3-0.15/debian/changelog pyx3-0.15/debian/changelog
--- pyx3-0.15/debian/changelog  2020-03-23 10:05:15.0 +1100
+++ pyx3-0.15/debian/changelog  2021-09-04 12:51:47.0 +1000
@@ -1,3 +1,11 @@
+pyx3 (0.15-3+deb11u1) bullseye; urgency=medium
+
+  * Fix horizontal font alignment issue with texlive 2020. Cherry-pick patch
+from upstream, with thanks to Andre Wobst and Joerg Lehmann
+(Closes: #992656).
+
+ -- Stuart Prescott   Sat, 04 Sep 2021 12:51:47 +1000
+
 pyx3 (0.15-3) unstable; urgency=medium
 
   * Fix autopkgtest failure due to use of py3versions -i, with thanks to Scott
diff -Nru pyx3-0.15/debian/patches/series pyx3-0.15/debian/patches/series
--- pyx3-0.15/debian/patches/series 2020-03-23 10:05:15.0 +1100
+++ pyx3-0.15/debian/patches/series 2021-09-04 12:51:47.0 +1000
@@ -9,3 +9,4 @@
 reproducible-timestamps.patch
 reproducible-image-name.patch
 reproducible-elements.patch
+texlive2020-horiz-alignment.patch
diff -Nru pyx3-0.15/debian/patches/texlive2020-horiz-alignment.patch 
pyx3-0.15/debian/patches/texlive2020-horiz-alignment.patch
--- pyx3-0.15/debian/patches/texlive2020-horiz-alignment.patch  1970-01-01 
10:00:00.0 +1000
+++ pyx3-0.15/debian/patches/texlive2020-horiz-alignment.patch  2021-09-04 
12:51:47.0 +1000
@@ -0,0 +1,31 @@
+From 82f82028ec5bc166ff2bb5bfa416ed94486b2775 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Andr=C3=A9=20Wobst?= 
+Date: Sat, 21 Aug 2021 13:46:28 +0200
+Subject: [PATCH] Make alignment work with texlive 2020
+
+The LaTeX shipout macro has recently been changed in unboxing and
+reboxing the content. This resulted in a misplacment in vertical
+direction by ignoring that PyX sets the height to zero.
+
+This bug has been reported by Thomas Bending.
+---
+ pyx/text.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/pyx/text.py b/pyx/text.py
+index 9ecd0768..68539743 100644
+--- a/pyx/text.py
 b/pyx/text.py
+@@ -1202,8 +1202,8 @@ class SingleEngine:
+   
"rt=\\the\\PyXDimenHAlignRT,"
+   "ht=\\the\\ht\\PyXBox,"
+   "dp=\\the\\dp\\PyXBox:}%\n"
++  "\\ht\\PyXBox0pt%\n" # baseline alignment (hight to 
zero)
+   
"\\setbox\\PyXBoxHAligned=\\hbox{\\kern-\\PyXDimenHAlignLT\\box\\PyXBox}%\n" # 
align horizontally
+-  

Bug#993560: closed by Bastian Blank (Re: Bug#993560: FTBFS on arch-any)

2021-09-03 Thread Daniel Baumann

reopen 993560
thanks

On 9/3/21 16:24, Debian Bug Tracking System wrote:

Yes, we know.


Great, thanks and looking forward to the upload that will fixes it.

Regards,
Daniel



Bug#978890: quvi: diff for NMU version 0.9.4-1.2

2021-09-03 Thread Boyuan Yang
Control: tags 978890 + patch
Control: tags 978890 + pending
X-Debbugs-CC: ans...@debian.org

Dear maintainer,

I've prepared an NMU for quvi (versioned as 0.9.4-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards,
Boyuan Yang

diff -Nru quvi-0.9.4/debian/changelog quvi-0.9.4/debian/changelog
--- quvi-0.9.4/debian/changelog 2016-02-18 10:51:44.0 -0500
+++ quvi-0.9.4/debian/changelog 2021-09-03 23:17:49.0 -0400
@@ -1,3 +1,11 @@
+quvi (0.9.4-1.2) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * debian/control: Update Vcs-* fields.
+  * debian/patches/0001: Fix FTBFS with autoconf 2.70 (Closes: #978890).
+
+ -- Boyuan Yang   Fri, 03 Sep 2021 23:17:49 -0400
+
 quvi (0.9.4-1.1) unstable; urgency=medium
 
   * Non-maintainer upload with maintainer permission.
diff -Nru quvi-0.9.4/debian/control quvi-0.9.4/debian/control
--- quvi-0.9.4/debian/control   2016-02-18 10:49:00.0 -0500
+++ quvi-0.9.4/debian/control   2021-09-03 23:14:49.0 -0400
@@ -2,8 +2,8 @@
 Section: utils
 Priority: optional
 Maintainer: Ansgar Burchardt 
-Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/quvi.git
-Vcs-Git: git://anonscm.debian.org/collab-maint/quvi.git
+Vcs-Git: https://salsa.debian.org/debian/quvi.git
+Vcs-Browser: https://salsa.debian.org/debian/quvi
 Homepage: http://quvi.sourceforge.net
 Standards-Version: 3.9.4
 Build-Depends: debhelper (>= 9), dh-autoreconf, pkg-config, asciidoc,
diff -Nru quvi-0.9.4/debian/patches/0001-Fix-FTBFS-with-autoconf-2.70.patch
quvi-0.9.4/debian/patches/0001-Fix-FTBFS-with-autoconf-2.70.patch
--- quvi-0.9.4/debian/patches/0001-Fix-FTBFS-with-autoconf-2.70.patch   1969-
12-31 19:00:00.0 -0500
+++ quvi-0.9.4/debian/patches/0001-Fix-FTBFS-with-autoconf-2.70.patch   2021-
09-03 23:16:58.0 -0400
@@ -0,0 +1,24 @@
+From: Boyuan Yang 
+Date: Fri, 3 Sep 2021 23:16:08 -0400
+Subject: Fix FTBFS with autoconf 2.70
+
+See also https://bugs.gentoo.org/68
+
+Bug-Debian: https://bugs.debian.org/978890
+---
+ configure.ac | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/configure.ac b/configure.ac
+index c45d4d8..d64f00d 100644
+--- a/configure.ac
 b/configure.ac
+@@ -6,7 +6,7 @@ AC_PREREQ([2.69])
+ AC_INIT([quvi], m4_esyscmd([./gen-ver.sh -c | tr -d '\n']),
+ [http://quvi.sf.net/bugs/],[],[http://quvi.sf.net/])
+ 
+-AC_DEFINE_UNQUOTED([BUILD_OPTS], "$@",
++AC_DEFINE_UNQUOTED([BUILD_OPTS], "$*",
+   [Define to configure invocation command line options])
+ 
+ AC_CONFIG_SRCDIR([src/main.c])
diff -Nru quvi-0.9.4/debian/patches/series quvi-0.9.4/debian/patches/series
--- quvi-0.9.4/debian/patches/series1969-12-31 19:00:00.0 -0500
+++ quvi-0.9.4/debian/patches/series2021-09-03 23:16:58.0 -0400
@@ -0,0 +1 @@
+0001-Fix-FTBFS-with-autoconf-2.70.patch


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


Bug#993632: Replace x11-utils dependency by a range of options that includes zenity and kdialog

2021-09-03 Thread Alexis PM
Package: thunderbird
Version: 1:78.13.0-1
Severity: normal

Hello

In order to avoid unnecessary dependencies, please consider replacing the 
strict x11-tools dependency with a range of options including zenity and 
kdialog. 
thunderbird-wrapper-helper.sh already supports zenity and kdialog, only the 
package dependency declaration needs to be modified.

Thank you very much.



Bug#988672: RM: rkt -- RoQA; NPOASR; FTBFS; upstream discontinued 2 years ago

2021-09-03 Thread Dmitry Smirnov
On Tuesday, 18 May 2021 3:57:01 AM AEST Shengjing Zhu wrote:
> Please remove rkt from unstable, it FTBFS for a long time, and upstream has
> discontinued its development 2 years ago. Users can migrate to podman[1]
> 
> [1] https://packages.debian.org/unstable/podman

I second that. "rkt" was an awesome technology and for a while I was hoping
someone would fork it to keep it alive. Unfortunately it did not happen
so this obsolete and unmaintained package should be removed.

Red Hat wasted out time once again with intentional destruction of competing
technology through acquisition. :(

-- 
Kind regards,
 Dmitry Smirnov
 GPG key : 4096R/52B6BBD953968D1B

---

And how long a lockdown is enough? If we open now, will lockdown recur in
autumn? Next year? Whenever authoritarianism so wishes? No dictatorship
could imagine a better precedent for absolute control.
 -- https://www.bmj.com/content/369/bmj.m1924.long
:: BMJ 2020;369:m1924 "Should governments continue lockdown to slow the 
spread of covid-19?"


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


Bug#993638: libxml2: XHTML 1.0 validation is broken

2021-09-03 Thread Vincent Lefevre
Package: libxml2
Version: 2.9.12+dfsg-3
Severity: grave
Justification: renders package unusable

After the upgrade to 2.9.12+dfsg-3, XHTML 1.0 validation is broken.
There was no such issue with 2.9.10+dfsg-6.7.

Testcase:


http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
http://www.w3.org/1999/xhtml;>
title
text


$ xmllint --noout --loaddtd --valid test.html
error : xmlAddEntity: invalid redeclaration of predefined entity
error : xmlAddEntity: invalid redeclaration of predefined entity

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

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

Versions of packages libxml2 depends on:
ii  libc6 2.31-17
ii  libicu67  67.1-7
ii  liblzma5  5.2.5-2
ii  zlib1g1:1.2.11.dfsg-2

libxml2 recommends no packages.

libxml2 suggests no packages.

-- no debconf information

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



Bug#993637: ecasound: LV2 plugins no longer supported

2021-09-03 Thread Rev. Johnny Healey
Package: ecasound
Version: 2.9.3-2
Severity: important
X-Debbugs-Cc: rev.n...@gmail.com

Dear Maintainer,

I recently updated to debian bullseye and found that numerous invocations of
ecasound that worked in buster. Specifically, LV2 plugins seem to no longer be
working in the binary built for bullseye.

A quick test to confirm this is to run `echo 'lv2-register' | /a/bin/ecasound`.
This command should list out all of the available plugins, but shows nothing.

I attempted to rebuild the package from source, but that did not seem to
resolve the issue. I poked at the config log a bit and noticed that it can't
find lv2core, which I think was in older versions of debian but has been
deprecated by the lv2-dev package. By hunch though is that it's just failing
to find the lv2 libraries when building and that is why the plugins are no
longer showing up.

Thanks for maintaining the package.

--Johnny

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

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

Versions of packages ecasound depends on:
ii  libasound21.2.4-1.1
ii  libaudiofile1 0.3.6-5
ii  libc6 2.31-13
ii  libgcc-s1 10.2.1-6
ii  libjack-jackd2-0 [libjack-0.125]  1.9.17~dfsg-1
ii  liblo70.31-1
ii  libreadline8  8.1-1
ii  libsamplerate00.2.1+ds0-1
ii  libsndfile1   1.0.31-2
ii  libstdc++610.2.1-6
ii  libtinfo6 6.2+20201114-2

Versions of packages ecasound recommends:
ii  faad 2.10.0-1
ii  lame 3.100-3
ii  mikmod   3.2.8-3
ii  mpg321 [mpg123]  0.3.2-3.1
ii  timidity 2.14.0-8
ii  vorbis-tools 1.4.0-11+b1

Versions of packages ecasound suggests:
ii  ecatools2.9.3-2
ii  ladspa-sdk [ladspa-plugin]  1.15-2
ii  lsp-plugins-ladspa [ladspa-plugin]  1.1.29-1
ii  nama1.216-1
ii  swh-plugins [ladspa-plugin] 0.4.17-2

-- no debconf information



Bug#965326: Changelogs of 'linux' package in stretch+buster are 404

2021-09-03 Thread Paul Wise
On Fri, 2021-09-03 at 15:37 +0100, Neil Williams wrote:

> Just a note that I'm working on a possible solution for this
> long-standing bug.

FYI, someone took a look at the ftp-master side of this and came to the
conclusion that its just a misconfigured rsync/mirror setup:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490848#56

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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


Bug#834945: libquvi: please make the build reproducible

2021-09-03 Thread Chris Lamb
Hi Boyuan,

> Looks like your patch is not enough. After merging the new patch, the updated
> libquvi/0.9.3-2 still fails to build reproducibly. Can you take a look into
> it?

So this is because since I wrote this patch in 2016, Debian is
injecting the build path into the CFLAGS variable. Here is an updated
version of the 0005-Make-the-build-reproducible.patch file to filter
this:

§

From: Chris Lamb 
Date: Sat, 20 Aug 2016 20:55:08 +0100
Subject: Make the build reproducible

Last-Update: 2016-08-20
Bug-Debian: https://bugs.debian.org/834945
---
 configure.ac | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- libquvi-0.9.3.orig/configure.ac
+++ libquvi-0.9.3/configure.ac
@@ -57,7 +57,9 @@ LT_PREREQ([2.2.6])
 AC_PROG_CC
 AM_PROG_CC_C_O
 
-AC_DEFINE_UNQUOTED([CFLAGS], "$CFLAGS", [Define to compiler flags])
+PWD=`pwd`
+FILTERED_CFLAGS=`echo $CFLAGS | sed -e "s@$PWD@«BUILDDIR»@g"`
+AC_DEFINE_UNQUOTED([CFLAGS], "$FILTERED_CFLAGS", [Define to compiler flags])
 AC_DEFINE_UNQUOTED([CC], "$CC", [Define to compiler])
 
 AC_PATH_PROG([DOXYGEN], [doxygen], [no])
@@ -71,7 +73,7 @@ AS_IF([test x"$A2X" = "xno" && test -d "
   AC_MSG_ERROR([a2x is required to create man pages when building from git])])
 
 AC_PATH_PROG([DATE], [date], [no])
-AS_IF([test x"$DATE" != "xno"], [build_time=`$DATE +"%F %T %z"`])
+AS_IF([test x"$DATE" != "xno" && test x"$SOURCE_DATE_EPOCH" = "x" ], 
[build_time=`$DATE +"%F %T %z"`])
 AC_DEFINE_UNQUOTED([BUILD_TIME], ["$build_time"], [We have build time])
 
 BUILD_TIME="$build_time"

§

(You might know of a cleaner way of doing this in automake.)


Regards,

--
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-



Bug#993636: printer-driver-pnm2ppa: Problem installation this version.

2021-09-03 Thread Santiago José López Borrazás
Package: printer-driver-pnm2ppa
Version: 1.13-11
Severity: important

Dear Maintainer,

Fail installation only this error script:

Preparando para desempaquetar printer-driver-pnm2ppa_1.13-11_amd64.deb ...
Desempaquetando printer-driver-pnm2ppa (1.13-11) sobre (1.13-11) ...
Configurando printer-driver-pnm2ppa (1.13-11) ...
/var/lib/dpkg/info/printer-driver-pnm2ppa.postinst: 1: tempfile: not found
dpkg: error al procesar el paquete printer-driver-pnm2ppa (--install):
 el subproceso instalado paquete printer-driver-pnm2ppa script 
post-installation devolvió el código de salida de error 127
Procesando disparadores para doc-base (0.11.1) ...
Processing 3 changed doc-base files...
Procesando disparadores para man-db (2.9.4-2) ...
Se encontraron errores al procesar:
 printer-driver-pnm2ppa

This fail is only package. Others packages is not necessary.

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

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

Versions of packages printer-driver-pnm2ppa depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  ghostscript9.53.3~dfsg-7+b1
ii  libc6  2.31-17

printer-driver-pnm2ppa recommends no packages.

Versions of packages printer-driver-pnm2ppa suggests:
pn  magicfilter | apsfilter  

-- debconf information:
  pnm2ppa/use_debconf: true
  pnm2ppa/create_magicfilter: false
  pnm2ppa/printer_model: 710


Bug#993635: Some time agodebian-i18n: Mixed format locale settings pop an "unable to set locale" message, and selection of the (correct) defaullt locale.

2021-09-03 Thread Peter Trenholme
Package: debian-i18n
Severity: minor
Tags: l10n
X-Debbugs-Cc: ptrenho...@comcast.net

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


*** /home/peter/minor_locale_problem.txt
I prefer to use a 24 hour clock, and, several years ago, the option to specify
the time format
was removed to the system setting options. As a work-around I specify a LC_TIME
value from a country
with a sensible time format -- France, Canada, . . . -- but the "locale"
setting (or selection - I
don't know where this is coming from) seems to want to use LC_ALL instead of
the specific LC_... settings.
I've tried setting LC_ALL to "C," which does use a 24 hour format, but its a
weird MMDD date format
(It doesn't sort correctly.)

So, this is quite minor, but really also quite unnecessary, assumption made in
the locale settings.

Here's an example of the (ubiquitous) prevalence of of the silly messages.
(Comments added by hand.)

Oh, and why isn't LC_ALL=C supported?

[peter ~]$ sudo apt install gir1.2-vte-2.91
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
gir1.2-vte-2.91
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 28.1 kB of archives.
After this operation, 60.4 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main amd64 gir1.2-vte-2.91 amd64
0.62.3-1 [28.1 kB]
Fetched 28.1 kB in 0s (259 kB/s)
#
# THIS IS THE UNNECESSARY MESSAGE -
apt-listchanges: Can't set locale; make sure $LC_* and $LANG are correct!
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US.UTF-8",
LC_ALL = (unset),
LC_TIME = "en_CX.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
locale: Cannot set LC_ALL to default locale: No such file or directory
# END OF GARBAGE
#
Selecting previously unselected package gir1.2-vte-2.91:amd64.
(Reading database ... 232759 files and directories currently installed.)
Preparing to unpack .../gir1.2-vte-2.91_0.62.3-1_amd64.deb ...
Unpacking gir1.2-vte-2.91:amd64 (0.62.3-1) ...
Setting up gir1.2-vte-2.91:amd64 (0.62.3-1) ...

[peter ~]$ reportbug
#
# AND HERE'S ANOTHER EXAMPLE --
(reportbug:12539): Gtk-WARNING **: 14:55:29.954: Locale not supported by C
library.
Using the fallback 'C' locale.
*** Warning: unsupported locale setting
#



Bug#993633: debcargo does not honour global summary/description

2021-09-03 Thread Ian Jackson
Control: tags -1 + patch

Here is the fix.  This in the form of a git-formwat-patch.
Obviously, I used git.  The vcs-git pointed to the debcargo-conf tree,
so I just used the .dsc import that dgit gave me.

Thanks,
Ian.



0001-Do-summary-length-checking-per-package-after-applyin.patch
Description: Binary data


0002-Factor-out-summary_suffix-and-description_suffix.patch
Description: Binary data


0003-config-make-global-summary-and-description-be-Option.patch
Description: Binary data


0004-description-summary-Assemble-them-much-later-out-of-.patch
Description: Binary data


0005-Honour-summary-and-description-in-global-section.patch
Description: Binary data


0006-introduce-Description-type.patch
Description: Binary data


0007-refactor-breaking-out-Description-apply_overrides.patch
Description: Binary data


0008-refactor-breaking-out-impl-Display-for-Description.patch
Description: Binary data


-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.


Bug#993571: oomd intervenes only after a desktop system has been frozen for several minutes

2021-09-03 Thread Christoph Groth
Yangfl wrote:

> Not a bug but an opinion or a question. See
> https://bugs.launchpad.net/ubuntu/+source/oomd/+bug/1898155 , discuss
> with the upstream or come up with your config proposal.

Thanks for the pointer.  I did not know that the default config that is
shipped by Debian is provided by upstream.  (I did check the upstream
code repository but didn’t find it.)

Given the above, I agree with your assessment in principle, although it’s
a pity that this apparently means that a package is not very useful by
default.

Incidentally, I experienced a memory leak in a Firefox tab today that
froze my system.  After waiting for ten minutes, I finally pulled the
plug and after rebooting purged oomd and switched back to earlyoom which
seems to work out-of-the-box.


signature.asc
Description: PGP signature


Bug#993612: bugs.debian.org: Socionext SynQuacer fails to mount rootfs after upgrade to Bullseye

2021-09-03 Thread Don Armstrong
Control: reassign -1 linux-signed-arm64
Control: found -1 5.10.46+4, 5.10.46+4~bpo10+1
Control: tag -1 moreinfo
Control: severity -1 important


On Fri, 03 Sep 2021, Luca Di Stefano wrote:
> A few days ago I tried to upgrade one of the six Socionext SynQuacers
> that we have to the latest Debian release.
> 
> It was running fine on Buster using the 4.19 kernel and had no previous 
> issues.

[...]

> The next boot sequence would start and get to the point where it would
> look for the rootfs without finding it and going into initramfs
> 
> I've then proceeded to reinstall buster on that machine and it just
> worked fine, then also tried installing the kernel from backports
> linux- image-5.10.0-0.bpo.8-arm64 and after reboot it caused the same
> problem not finding the rootfs and going into initramfs.

I'm not familiar with the hardware of this particular device, but I
suspect that some necessary driver was (likely inadvertently) excluded
from the configuration of the 5.10 kernel, but included in 4.19.

Looking at the output from the boot of both kernels should give you an
idea of what module/device is broken, and providing that to this bug
will give one of the maintainers of the arm64 kernel a chance of helping
fix the issue.

-- 
Don Armstrong  https://www.donarmstrong.com

If a nation values anything more than freedom, it will lose its
freedom; and the irony of it is that if it is comfort or money it
values more, it will lose that, too.
 -- W. Somerset Maugham



Bug#993634: xfdesktop4 doesn't always change backgrounds at specified intervals. Regression?

2021-09-03 Thread Charles Curley
Package: xfdesktop4
Version: 4.16.0-1
Severity: normal
X-Debbugs-Cc: charlescur...@charlescurley.com

Dear Maintainer,

   * What led up to the situation?

Using the Desktop program on Buster, one may set the background to change every 
day, and it does so.

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

New installation on two Lenovo T-61 laptops. Went into the Desktop program as 
usual to (among other things) set the background and frequency of change of the 
background. I was able to set the background correctly. I then selected my 
usual "Change the background every day". I also select "Random Order".

   * What was the outcome of this action?

Background did not change. I waited several days; no change.

   * What outcome did you expect instead?

The background should change overnight.


Further information:

* Setting the frequency to one hour works correctly. Setting it to 24 hours 
does not work. I am experimenting with other hourly values to see what happens.

* On a dual headed setup, this problem appears on both monitors. I can set up 
the background for both monitors correctly, and one and two hour rotations of 
the background work.



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

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

Versions of packages xfdesktop4 depends on:
ii  exo-utils4.16.0-1
ii  libc62.31-13
ii  libcairo21.16.0-5
ii  libexo-2-0   4.16.0-1
ii  libgarcon-1-04.16.1-1
ii  libgarcon-gtk3-1-0   4.16.1-1
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.8-1
ii  libgtk-3-0   3.24.24-4
ii  libnotify4   0.7.9-3
ii  libpango-1.0-0   1.46.2-3
ii  libthunarx-3-0   4.16.8-1
ii  libwnck-3-0  3.36.0-1
ii  libx11-6 2:1.7.2-1
ii  libxfce4ui-2-0   4.16.0-1
ii  libxfce4util74.16.0-1
ii  libxfconf-0-34.16.0-2
ii  xfdesktop4-data  4.16.0-1

Versions of packages xfdesktop4 recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.12.20-2
ii  librsvg2-common   2.50.3+dfsg-1
ii  tumbler   4.16.0-1
ii  xdg-user-dirs 0.17-2

xfdesktop4 suggests no packages.

-- no debconf information



Bug#993633: debcargo does not honour global summary/description

2021-09-03 Thread Ian Jackson
Package: debcargo
Version: 2.4.4-1

Steps to reproduce:

 git clone g...@salsa.debian.org:rust-team/debcargo-conf
 cd debcargo-conf
 git checkout d93204a10e6901c9ce30f581d33fd6770ce36241
 ./update.sh toml
 # ^C at the prompt which offers to show a diff

Note that src/toml/debian/debcargo.toml contains this:

  overlay = "."
  uploaders = ["kpcyrd "]

  # The auto-generated summary is too long.
  summary = "Native encoder and decoder of TOML-formatted data"

Expected results:

 The override is honoured.
 The generated build/toml/debian/control contains these
   Description: Native encoder and decoder of TOML-formatted data
   Description: Native encoder and decoder of TOML-formatted data - feature 
"indexmap" and 1 more
 as found in the Debian archive, 0.5.5-1.
 No FIXME is generated.

Actual results:

 The override is ignored.  A FIXME is generated.

I am working on a fix.

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.



Bug#993631: cfgrib FTBFS: test failures

2021-09-03 Thread Alastair McKinstry
This is a bug in python3-eccodes which now depends on ecmwflibs.
Ecmwflibs in now in the NEW queue

On 03/09/2021, 21:51, "Adrian Bunk"  wrote:

Source: cfgrib
Version: 0.9.9.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=cfgrib=0.9.9.0-1



Bug#993629: error: : cannot open

2021-09-03 Thread Nicholas Guriev
Hello!

On Пт, 2021-09-03 at 17:23 -0300, Wellington Almeida wrote:
> When running the application after a few moments it unexpectedly closes with
> the following error message.

Could you please attach Telegram logs after the crash, file
~/.local/share/TelegramDesktop/log.txt ?

Do you have the qt5-image-formats-plugins package installed?



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


Bug#993552: RFS: proton-caller/2.3.2-1 [ITP] -- Run any Windows program through Proton

2021-09-03 Thread BenTheTechGuy
>   The license is MIT.  Please correct debian/copyright.

The author switched the license from GPL3 to MIT without telling me, fixed.

>   The program depends on non-free Steam, thus it can't go into the main
>   archive.  It is a nice specimen of a "contrib" package, though.
>   You can put it there by changing Section to contrib/XXX.

I didn't know that specifying the section by itself implied main, fixed.

>   The package fails to build:
>   .
>   cargo build --release --locked
>   make: cargo: No such file or directory
>   `
>   Fix: Build-Depends: cargo

I didn't realize cargo was only a recommended dependency of rustc, fixed.

>   For a new package, there should be only one changelog entry (unless the
>   package already exists in a repository used by actual other people).

I forgot to mention that I already maintain this on the project's
GitHub Releases page.
However, I have removed all previous changelog entries.

>   The long descriptions really should be longer than one line.  It'd be nice
>   if you could write something more what is it good for (as I understand,
>   it's an equivalent to "wine freecell.exe"), what's the diff from Wine, etc.

A better long description has been added.

>   An upload to Debian must be targetted at "unstable" or "experimental"
>   (other options being irrelevant for now), you currently have it set to
>   "UNRELEASED".

It has been changed to unstable.

>   debian/rules is missing a lot of functionality: mandatory targets like
>   {build,binary}-arch; passing build flags, handling cross builds, etc.
>   All of this would be much better done with dh (like the vast majority
>   of packages in Debian do) -- it does know how to use cargo, etc.
>   Likewise, there's no need to run install by hand.

I can't get it to work without manually telling dh_build to run cargo.
If someone can point me in the right direction of how to format my
debian/rules to build with cargo then put binaries, config files, and
such in the right place (there is nothing about that in Cargo.toml)
that would be very helpful.

Thank you so much Adam for helping me get some things straightened
out, the latest upload
https://mentors.debian.net/debian/pool/main/p/proton-caller/proton-caller_2.3.2-2.dsc
fixes all the problems you pointed out!



Bug#993631: cfgrib FTBFS: test failures

2021-09-03 Thread Adrian Bunk
Source: cfgrib
Version: 0.9.9.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=cfgrib=0.9.9.0-1

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
for p in python3.9; do \
PY3VERNUM=`echo $p | sed -e 's/python//' `; \
pybuild --test --test-pytest -i $p -p $PY3VERNUM  ;  \
done
I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9_cfgrib/build; 
python3.9 -m pytest tests
= test session starts ==
platform linux -- Python 3.9.7, pytest-6.0.2, py-1.10.0, pluggy-0.13.0
rootdir: /<>, configfile: pyproject.toml
collected 6 items / 9 errors / 2 skipped

 ERRORS 
__ ERROR collecting .pybuild/cpython3_3.9_cfgrib/build/tests/test_20_main.py ___
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.9_cfgrib/build/tests/test_20_main.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3/dist-packages/gribapi/bindings.py:28: in 
import ecmwflibs as findlibs
E   ModuleNotFoundError: No module named 'ecmwflibs'

During handling of the above exception, another exception occurred:
/usr/lib/python3.9/importlib/__init__.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/test_20_main.py:3: in 
from cfgrib import __main__
cfgrib/__init__.py:19: in 
from .cfmessage import CfMessage
cfgrib/cfmessage.py:29: in 
from . import messages
cfgrib/messages.py:28: in 
import eccodes  # type: ignore
/usr/lib/python3/dist-packages/eccodes/__init__.py:13: in 
from .eccodes import *  # noqa
/usr/lib/python3/dist-packages/eccodes/eccodes.py:12: in 
from gribapi import (
/usr/lib/python3/dist-packages/gribapi/__init__.py:13: in 
from .gribapi import *  # noqa
/usr/lib/python3/dist-packages/gribapi/gribapi.py:34: in 
from . import errors
/usr/lib/python3/dist-packages/gribapi/errors.py:16: in 
from .bindings import ENC, ffi, lib
/usr/lib/python3/dist-packages/gribapi/bindings.py:30: in 
import findlibs
E   ModuleNotFoundError: No module named 'findlibs'
...
=== short test summary info 
ERROR tests/test_20_main.py
ERROR tests/test_20_messages.py
ERROR tests/test_25_cfmessage.py
ERROR tests/test_30_dataset.py
ERROR tests/test_40_xarray_store.py
ERROR tests/test_40_xarray_to_grib_regular_ll.py
ERROR tests/test_50_datamodels.py
ERROR tests/test_50_sample_data.py
ERROR tests/test_50_xarray_getitem.py
!!! Interrupted: 9 errors during collection 
= 2 skipped, 9 errors in 1.97s =
E: pybuild pybuild:353: test: plugin distutils failed with: exit code=2: cd 
/<>/.pybuild/cpython3_3.9_cfgrib/build; python3.9 -m pytest tests
make[1]: *** [debian/rules:19: override_dh_auto_test] Error 13



(m68k builds with nocheck)



Bug#993630: isso depends on deprecated node-jade which is going to be removed

2021-09-03 Thread Yadd
Package: isso
Severity: serious

Hi,

isso depends on node-jade which is no more maintained.

Cheers,
Yadd



Bug#993629: error: : cannot open

2021-09-03 Thread Wellington Almeida
Package: telegram-desktop
Version: 2.6.1+ds-1
Severity: normal

When running the application after a few moments it unexpectedly closes with
the following error message.

** (process:9534): WARNING **: 17:10:36.422: Unfortunately, GTK
integration conflicts with qgtk2 platformtheme and style. Therefore,
QT_QPA_PLATFORMTHEME and QT_STYLE_OVERRIDE will be unset.
** Message: 17:10:36.422: This can be ignored by setting
DESKTOP_APP_I_KNOW_ABOUT_GTK_INCOMPATIBILITY environment variable to
any value, however, if qgtk2 theme or style is used, this will lead to
a crash.
** Message: 17:10:36.422: GTK integration can be disabled by setting
DESKTOP_APP_DISABLE_GTK_INTEGRATION to any value. Keep in mind that
this will lead to some features being unavailable.

(process:9534): Telegram-WARNING **: 17:10:36.422: Application has
been built with foreign rlottie, animated emojis won't be colored to
the selected pack.

(process:9534): Telegram-WARNING **: 17:10:36.422: Application was
built without embedded fonts, this may lead to font issues. On
Debian-based systems, make sure you have the fonts-open-sans package
installed
error: : cannot open
error: : cannot open
error: : cannot open
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
Abortado

-- 
Wellington Almeida
Rio de Janeiro - Brasil


Bug#993575: heartbeat: Heartbeat not starting due to missing directory after bullseye upgrade

2021-09-03 Thread Valentin Vidic
On Fri, Sep 03, 2021 at 11:18:08AM +0200, Gael Le Mignot wrote:
> After upgrading from buster to bullseye on several hosts, "heartbeat"
> doesn't start. It tries to create a /run/heartbeat/register socket in
> a non-existing /run/heartbeat/ directory.

Thanks for the report, it seems we have lost this config in the latest
version:

  /usr/lib/tmpfiles.d/heartbeat.conf

and that will cause startup problems after reboot. I will restore it
back now.

-- 
Valentin



Bug#993628: openvdb FTBFS: Could NOT find GTest

2021-09-03 Thread Adrian Bunk
Source: openvdb
Version: 8.1.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=openvdb=8.1.0-1

...
-- 
-- --- Configuring OpenVDBUnitTests ---
-- 
CMake Error at 
/usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:165 (message):
  Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR
  GTEST_MAIN_LIBRARY) (Required is at least version "1.8")
Call Stack (most recent call first):
  /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:458 
(_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-3.18/Modules/FindGTest.cmake:205 
(FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  openvdb/openvdb/unittest/CMakeLists.txt:40 (find_package)


-- Configuring incomplete, errors occurred!



Bug#993627: ndpi: Bus error on armhf when built on 64bit hardware

2021-09-03 Thread Adrian Bunk
Source: ndpi
Version: 4.0-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=ndpi=armhf

...
Bus error
openvpn.pcapERROR
...
make[1]: *** [debian/rules:35: override_dh_auto_test] Error 1


This is likely an alignment problem, similar to the fixed #917238.



Bug#987378: yara breaks golang-github-hillu-go-yara autopkgtest + ftbfs

2021-09-03 Thread Paul Gevers
Hi Hilko,

On 02-09-2021 23:39, Hilko Bengen wrote:
> * Paul Gevers:
> 
>> On Thu, 2 Sep 2021 10:17:22 +0200 Sascha Steinbiss  wrote:
>>> I think this is done now. With YARA 4.1.2 and 
>>> golang-github-hillu-go-yara 4.1.0 now in unstable, the build works again 
>>> as the build-time tests complete fine.
>>>
>>> @Hilko any other comments?
>>
>> If there are incompatible API changes, the soname needs to be bumped.
> 
> The soname was bumped, from 4 to 8.

Sorry, I somehow missed that. So if I understand it, you just forgot to
close the bug?

Paul



OpenPGP_signature
Description: OpenPGP digital signature


Bug#993626: Please --enable-cet on x86-64

2021-09-03 Thread Josh Triplett
Source: gcc-11
Version: 11.2.0-4
Severity: normal
X-Debbugs-Cc: j...@joshtriplett.org

The fix for #993162 disabled CET on i386, amd64, and x32. However, as
far as I can tell, the CPUs that don't support long NOPs are all
32-bit-only CPUs; all 64-bit CPUs should support long NOPs. Given that,
please consider re-enabling CET on amd64 and x32, and only disabling it
on i386.

- Josh Triplett



Bug#992829: spamassassin: "spamassassin -r" fails with permission problem

2021-09-03 Thread Francois Marier
As far as I can tell, I was able to fix this successfully by doing:

  chmod a+rx /var/lib/spamassassin

Not sure why this changed recently (after the bullseye release), but perhaps
that's something that the package needs to set.

Francois



Bug#993415: libpinyin: Switch from Berkeley DB to Kyotocabinet?

2021-09-03 Thread Gunnar Hjalmarsson

On 2021-09-01 01:57, Boyuan Yang wrote:

However, I am not sure what would users experience when database
format is switched (e.g., will all data previously stored in old
db be lost? Is that a severe issue?).


I think we should make a serious attempt to avoid such an interruption 
before accomplishing a switch to some other db format. There seems to be 
plenty of time.


--
Gunnar



Bug#993625: RFP: wezterm -- A GPU-accelerated cross-platform terminal emulator in rust

2021-09-03 Thread Vipul Chawhan
Package: wnpp
Severity: wishlist
1.Here's what he had so say,
"I'd suggest pointing them to:
https://github.com/wez/wezterm/blob/main/ci/deploy.sh#L131-L151 so they can
see what we put in our .deb"
2. Link to the deb files
https://github.com/wez/wezterm/releases
3. The license they use is MIT
https://github.com/wez/wezterm/blob/main/LICENSE.md
4. The dev can be contacted via github issues section
https://github.com/wez/wezterm/issues


Bug#993219: [debian-mysql] Bug#993219: mariadb-server-core: Akonadi database - mysql_upgrade fails always with "FATAL ERROR: Can't execute 'mysqlcheck'"

2021-09-03 Thread Ulrich Beckmann
The user in the forum has already  recovered his mails and data, so he won't 
risk the test.

My point is, that in 2 of my 3 debian installations there are errors in the 
MariaDB system tables (see mysql.err). Only the fresh Bullseye installation is 
without errors. Akonadi/Contact/KMail works in any case.

Any attempt to check and correct the tables with mysql_upgrade fails, see the 
attached files. I tested other distributions, ie openSUSE 15.3 e Fedora 34. 
There you can invoke mysql_upgrade as a user without any problem.

Btw. a successful migration should also take care of  the redo logs. The user 
normally does not know, whether the database was shut down correctly or not.

Regards,
Ulrichbeq-testing@deb-testing:~$ cat .local/share/akonadi/db_data/mysql.err
2021-08-29 16:19:15 0 [Note] InnoDB: Using Linux native AIO
2021-08-29 16:19:15 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-08-29 16:19:15 0 [Note] InnoDB: Uses event mutexes
2021-08-29 16:19:15 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-08-29 16:19:15 0 [Note] InnoDB: Number of pools: 1
2021-08-29 16:19:15 0 [Note] InnoDB: Using SSE2 crc32 instructions
2021-08-29 16:19:16 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-08-29 16:19:16 0 [Note] InnoDB: Completed initialization of buffer pool
2021-08-29 16:19:16 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-08-29 16:19:19 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2021-08-29 16:19:19 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2021-08-29 16:19:19 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2021-08-29 16:19:19 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2021-08-29 16:19:19 0 [Note] InnoDB: 10.3.24 started; log sequence number 682212237; transaction id 6333
2021-08-29 16:19:19 0 [Note] InnoDB: Loading buffer pool(s) from /home/beq-testing/.local/share/akonadi/db_data/ib_buffer_pool
2021-08-29 16:19:19 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-08-29 16:19:20 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
2021-08-29 16:19:20 0 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
2021-08-29 16:19:20 6 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1017: Can't find file: './mysql/' (errno: 2 "No such file or directory")
2021-08-29 16:19:20 0 [Note] Reading of all Master_info entries succeeded
2021-08-29 16:19:20 0 [Note] Added new Master_info '' to hash table
2021-08-29 16:19:20 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.3.24-MariaDB-2'  socket: '/run/user/1002/akonadi/mysql.socket'  port: 0  Debian buildd-unstable
2021-08-29 16:19:21 9 [ERROR] InnoDB: Table `mysql`.`innodb_table_stats` not found.
2021-08-29 16:19:34 0 [Note] InnoDB: Buffer pool(s) load completed at 210829 16:19:34
beq-testing@deb-testing:~$
beq-testing@deb-testing:~$ akonadictl status
Akonadi Control: running
Akonadi Server: running
Akonadi Server Search Support: available (Remote Search, Akonadi Search Plugin)
Available Agent Types: akonadi_akonotes_resource, akonadi_archivemail_agent, akonadi_birthdays_resource, akonadi_contacts_resource, akonadi_davgroupware_resource, akonadi_ews_resource, akonadi_ewsmta_resource, akonadi_followupreminder_agent, akonadi_google_resource, akonadi_ical_resource, akonadi_icaldir_resource, akonadi_imap_resource, akonadi_indexing_agent, akonadi_kalarm_dir_resource, akonadi_kalarm_resource, akonadi_kolab_resource, akonadi_maildir_resource, akonadi_maildispatcher_agent, akonadi_mailfilter_agent, akonadi_mbox_resource, akonadi_migration_agent, akonadi_mixedmaildir_resource, akonadi_newmailnotifier_agent, akonadi_notes_agent, akonadi_notes_resource, akonadi_openxchange_resource, akonadi_pop3_resource, akonadi_sendlater_agent, akonadi_tomboynotes_resource, akonadi_unifiedmailbox_agent, akonadi_vcard_resource, akonadi_vcarddir_resource
beq-testing@deb-testing:~$
beq-testing@deb-testing:~$ mysql_upgrade --defaults-file=/home/beq-testing/.local/share/akonadi/mysql.conf --socket=/run/user/1002/akonadi/mysql.socket -v
Looking for 'mysql' as: mysql
Looking for 'mysqlcheck' as: mysqlcheck
FATAL ERROR: Can't execute 'mysqlcheck'
beq-testing@deb-testing:~$
beq-testing@deb-testing:~$ dpkg -l | egrep 'mysql|mariadb' | sort
ii  akonadi-backend-mysql 4:20.08.3-3all  MySQL storage backend for Akonadi
ii  default-mysql-client-core 1.0.7  all  MySQL database core client binaries (metapackage)
ii  libmariadb3:amd64 1:10.5.12-1amd64MariaDB database client library
ii  libqt5sql5-mysql:amd64

Bug#993624: RM: eckit [armel i386 armhf mipsel] -- ROM; 32-bit archs no longer supported

2021-09-03 Thread Alastair McKinstry
Package: ftp.debian.org
Severity: normal

Please remove the 32-bit archs - they are no longer supported upstream



Bug#993607: xfce4-panel: forder menu do not display custom icon (not coming from theme/system icons repo)

2021-09-03 Thread Pierre Colombier
Package: xfce4-panel
Version: 4.16.2-1
Severity: normal

Dear Maintainer,

I used to have some "foler menu" in my xfce taskbar and I used custom icons
from /home/myusername/mycusomicons to distinguish them

I recently upgraded from Debian buster to bullseye and now all the custom icons
display the theme's 'image-missing' instead

( in my case /usr/share/icons/breeze-dark/status/64/image-missing.svg )

it seems the same problem occurs with the lauchers.

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

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

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

xfce4-panel recommends no packages.

xfce4-panel suggests no packages.



Bug#993623: python-seqcluster: Switch to myst-parser instead of recommonmark

2021-09-03 Thread Emmanuel Arias
Source: python-seqcluster
Version: 1.2.7+ds-1
Severity: wishlist
X-Debbugs-Cc: eam...@yaerobi.com

Dear Maintainer,

python-seqcluster currently Build-Depends or Depends on python3-recommonmark
from recommonmark. This project is deprecated and upstream recommend the use
of and MyST [0][1] (see ITP: #993553). Please switch to MyST-Parse (when is
Ready).


[0] https://github.com/readthedocs/recommonmark

[1] https://github.com/executablebooks/MyST-Parser


Cheers
Emmanuel



Bug#990194: RM: libphonenumber|geocoding7 -- RoQA; replcaed by libphonenumber|geocoding8

2021-09-03 Thread Juhani Numminen
Control: retitle -1 RM: libphonenumber7-java -- RoQA; NBS; replaced by 
libphonenumber8-java

On Tue, 22 Jun 2021 16:22:41 +0200 Jochen Sprickerhof  
wrote:
> please clean up libphonenumber 7.1.0-7 from unstable, it got replaced by
> version 8 and dak did not clean up the old libraries.

The only remaining binary for libphonenumber 7.1.0-7 is libphonenumber7-java[1].
I have changed the bug title to be something simpler so that it is better 
understood
by the software for the removals.html page[2].

[1] 
https://qa.debian.org/madison.php?package=libphonenumber=debian===unstable%2Ctesting=on#
[2] https://ftp-master.debian.org/removals.html

Cheers,
--
Juhani



Bug#993622: python3-open3d: Missing dependency on python3-numpy

2021-09-03 Thread Shane Loretz
Package: python3-open3d
Version: 0.9.0+ds-5+b2
Severity: normal
X-Debbugs-Cc: slor...@openrobotics.org

Dear Maintainer,

It appears python3-open3d is missing a dependency on python3-numpy.
The module can't be imported until it's manually installed.

On a fresh bullseye container I installed python3-open3d 

bullseye:root> apt install libopen3d-dev/stable libopen3d0d/stable 
python3-open3d/stable
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '0.9.0+ds-5+b2' (Debian:11.0/stable [amd64]) for 
'libopen3d-dev'
Selected version '0.9.0+ds-5+b2' (Debian:11.0/stable [amd64]) for 
'libopen3d0d'
Selected version '0.9.0+ds-5+b2' (Debian:11.0/stable [amd64]) for 
'python3-open3d'
...

But I encountered an ImportError:

>>> import open3d
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/open3d/__init__.py", line 3, in 

from .open3d import *
ImportError: ModuleNotFoundError: No module named 'numpy'

So I installed python3-numpy, and afterwards I was able to import
open3d.

>>> import open3d
>>>

Would you be willing to add this dependency to the Debian package?


Cheers,
Shane

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

Kernel: Linux 5.11.0-27-generic (SMP w/24 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages python3-open3d depends on:
ii  libc62.31-13
ii  libgcc-s110.2.1-6
ii  libopen3d0d  0.9.0+ds-5+b2
ii  libstdc++6   10.2.1-6
ii  python3  3.9.2-3

python3-open3d recommends no packages.

Versions of packages python3-open3d suggests:
pn  open3d-doc  

-- no debconf information



Bug#991516: nvidia-graphics-drivers 418.211.00-1 flagged for acceptance

2021-09-03 Thread Adam D Barratt
package release.debian.org
tags 991516 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: nvidia-graphics-drivers
Version: 418.211.00-1

Explanation: new upstream stable release; fix denial of service issues 
[CVE-2021-1093 CVE-2021-1094 CVE-2021-1095]; nvidia-driver-libs: Add 
Recommends: libnvidia-encode1



Bug#991514: nvidia-graphics-drivers-legacy-390xx 390.144-1~deb10u1 flagged for acceptance

2021-09-03 Thread Adam D Barratt
package release.debian.org
tags 991514 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: nvidia-graphics-drivers-legacy-390xx
Version: 390.144-1~deb10u1

Explanation: new upstream stable release; fix denial of service issues 
[CVE-2021-1093 CVE-2021-1094 CVE-2021-1095]; nvidia-legacy-390xx-driver-libs: 
Add Recommends: libnvidia-legacy-390xx-encode1



Bug#993388: [Pkg-tcltk-devel] Bug#993388: tcl8.6: nested dicts: with lappend you can duplicate and than remove intermediate values

2021-09-03 Thread Davide Prina

Hi Sergei,

On 31/08/21 18:29, Sergei Golovan wrote:


As far as I can see, there's nothing wrong with Tcl here.


I'm very sorry for my mistakes :-(

Thanks for your explanation.

On nested dict there are very few documentation and, at first, I don't 
have fully understand the examples on the man page. So I have search and 
found a site that tell that the only way to modify a nested dict is with 
"dict with"... and I have make some mistakes...


I have try to understand dict better and found that you can modify 
nested dict also with "dict set"


I think now I have understand nested dict.

# create a nested dict
% set MyDict [dict create l0a 1 l0b1 1 l0c {l1a 2 l1b {l2a {l3a 4 l3b 4} 
l2b 3} l1c 2 l1d 2} l0d 1 l0e 1]
l0a 1 l0b1 1 l0c {l1a 2 l1b {l2a {l3a 4 l3b 4} l2b 3} l1c 2 l1d 2} l0d 1 
l0e 1


# you can add new values or update with dict set
% dict set MyDict l0c l1b l2d {l3A 4 l3B 4}
l0a 1 l0b1 1 l0c {l1a 2 l1b {l2a {l3a 4 l3b 4} l2b 3 l2d {l3A 4 l3B 4}} 
l1c 2 l1d 2} l0d 1 l0e 1


# you can append new value with dict lappend and dict with
% dict with MyDict l0c l1b {dict lappend l2d l3C 4}
l3A 4 l3B 4 l3C 4

% echo $MyDict
l0a 1 l0b1 1 l0c {l1a 2 l1b {l2a {l3a 4 l3b 4} l2b 3 l2d {l3A 4 l3B 4 
l3C 4}} l1c 2 l1d 2} l0d 1 l0e 1


You can close this bug report.

Ciao
Davide



Bug#987177: lockfile-progs: lockfile creation failing on cifs mounts

2021-09-03 Thread Rob Browning
Nils  writes:

> lockfile creation fails on a cifs mounted drive with "lockfile
> creation failed: Value too large for defined data type"

Hmm, lockfile-create is really a very simple wrapper around a call to
lockfile_create(1), and offhand, I don't see any obvious way the
arguments being passed could be causing an EOVERFLOW.

Offhand, I wonder if it's the liblockfile version difference.  From a
quick glance I see some upstream commits involving EOVERFLOW.
If you can still reproduce the problem, you might be able to verify that
by testing with dotlock instead of lockfile-create.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4



Bug#993621: printer-driver-pnm2ppa: postinst failed: tempfile: not found

2021-09-03 Thread Boyuan Yang
Package: printer-driver-pnm2ppa
Severity: grave
Version: 1.13-10
X-Debbugs-CC: o...@debian.org
Tags: sid bookworm

Dear Debian Printer Team members,

Package printer-driver-pnm2ppa failed to install due to errors in postinst:

/var/lib/dpkg/info/printer-driver-pnm2ppa.postinst: 1: tempfile: not found

The tempfile command is no longer available after Debian 11 release. Please
consider using "mktemp" from coreutils instead. This bug does not affect
packages in released Debian 11 stable.

-- 
Thanks,
Boyuan Yang


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


Bug#993620: vip-manager: test failure with some network configurations

2021-09-03 Thread Dan Bungert
Package: vip-manager
Version: 1.0.1-4
Severity: normal
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu impish

Dear Maintainer,

vip-manager behavior_test can fail, depending on the device network
configuration.  If the test device has a network device of type ether
and a zero hardware address, and it selects this network device as the
one to use, the tests will fail.

Example failure:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/v/vip-manager/20210901_213607_5779b@/log.gz
2021/09/01 21:35:37 Problems with generating the virtual ip manager: Cannot run 
vip-manager on the loopback device
as its hardware address is the local address (00:00:00:00:00:00),
which prohibits sending of gratuitous ARP messages

Here is abbreviated output of 'ip link show' for one such test device:
3: gretap0@NONE:  mtu 1476 qdisc noop state DOWN mode 
DEFAULT group default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
44262: eth0@if44263:  mtu 1458 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
link/ether 00:16:3e:0f:a3:f7 brd ff:ff:ff:ff:ff:ff link-netnsid 0

In this example, gretap0 will be the chosen network device, but will
fail at runtime of vip-manager due to the all-zeros mac address.
Instead, eth0 should be chosen.

Please see the attached patch, which I will be looking to get integrated
to Ubuntu, which seems to address the above problem for Ubuntu armhf
autopkgtest.

This bug report was also filed in Ubuntu and can be found at
https://launchpad.net/bugs/1942375

-Dan
Description: Improved test device selection
Author:  Dan Bungert 
Bug-Ubuntu:  https://bugs.launchpad.net/bugs/1942375
Last-Update: 2021-09-03
--- a/test/behaviour_test.sh
+++ b/test/behaviour_test.sh
@@ -7,9 +7,29 @@
 NC='\033[0m' # No Color
 
 # testing parameters
-dev=`ip link show | grep -B1 ether | cut -d ":" -f2 | head -n1 | cut -d " " -f2 | sed s/@.*//`
 vip=10.0.2.123
 
+function get_dev {
+# select a suitable device for testing purposes
+# * a device that is an "ether"
+# * and isn't a nil hardware address
+
+# https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
+ARPHRD_ETHER=1
+
+for dev in /sys/class/net/* ; do
+test ! -e "$dev/address" && continue
+test "$(cat $dev/address)" = "00:00:00:00:00:00" && continue
+test "$(cat $dev/type)" != "$ARPHRD_ETHER" && continue
+basename "$dev"
+break
+done
+}
+
+dev="$(get_dev)"
+# prerequisite test - do we have a suitable device?
+test -n "$dev"
+
 #cleanup
 function cleanup {
 if test -f .ncatPid
@@ -35,7 +55,7 @@
 }
 trap cleanup EXIT
 
-# prerequisite test 0: vip should not yet be registered
+# prerequisite test: vip should not yet be registered
 ! ip address show dev $dev | grep $vip
 
 # run etcd with podman/docker maybe?


Bug#993618: RFS: openldap/2.4.59+dfsg-1~bpo11+1

2021-09-03 Thread Utkarsh Gupta
Hi Ryan,

On Fri, Sep 3, 2021 at 11:33 PM Ryan Tandy  wrote:
> As with previous releases, I am looking for a sponsor to perform the
> initial upload of openldap to bullseye-backports since it will be NEW. I
> am DM for the package and can take care of future uploads myself.

Uploaded, will coordinate other things via IRC. Thank you!


- u



Bug#993619: Remmina crashed in remmina-plugin-rdp.so

2021-09-03 Thread Mihai Hanor
Package: remmina-plugin-rdp
Version: 1.4.20+dfsg-4
Severity: normal
File: /usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so
X-Debbugs-Cc: quake2i...@gmail.com

Dear Maintainer,

   * What led up to the situation?
After the existing RDP connection was lost, possibly interacted with the
existing RDP window.

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

   * What was the outcome of this action?
Crash occured at:
#0  remmina_rdp_event_queue_ui (gp=0x555f8a99aaa0, ui=0x7f0c741f87c0) at
./plugins/rdp/rdp_event.c:1341
#1  0x7f0c885b0a5c in remmina_rdp_event_queue_ui_async (gp=, ui=) at ./plugins/rdp/rdp_event.c:1385
#2  0x7f0c885a9975 in remmina_rdp_post_connect
(instance=0x555f8a70e490) at ./plugins/rdp/rdp_plugin.c:734
#3  0x7f0c884651f4 in freerdp_connect (instance=0x555f8a70e490) at
./libfreerdp/core/freerdp.c:217
#4  0x7f0c885ab602 in remmina_rdp_main (gp=) at
./plugins/rdp/rdp_plugin.c:2033
#5  remmina_rdp_main_thread (data=) at
./plugins/rdp/rdp_plugin.c:2238
#6  0x7f0c8d609ea7 in start_thread () at
/lib/x86_64-linux-gnu/libpthread.so.0
#7  0x7f0c8cebfdef in clone () at /lib/x86_64-linux-gnu/libc.so.6

>From xsession-errors:
[17:45:32:240] [5719:6849] [ERROR][com.freerdp.core] -
rdp_set_error_info:freerdp_set_last_error_ex
ERRINFO_DISCONNECTED_BY_OTHER_CONNECTION [0x00010005]
/usr/bin/remmina-file-wrapper: line 35:  5719 Segmentation fault  (core
dumped) "$REMMINA" "${@}"

coredumpctl dump Timestamp: Fri 2021-09-03 17:45:34 EEST

   * What outcome did you expect instead?
No crash.


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

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

Versions of packages remmina-plugin-rdp:amd64 depends on:
ii  libc6 2.31-17
ii  libcairo2 1.16.0-5
ii  libcups2  2.3.3op2-6
ii  libfreerdp-client2-2  2.3.0+dfsg1-2
ii  libfreerdp2-2 2.3.0+dfsg1-2
ii  libgdk-pixbuf-2.0-0   2.42.6+dfsg-2
ii  libglib2.0-0  2.68.4-1
ii  libgtk-3-03.24.30-2
ii  libwinpr2-2   2.3.0+dfsg1-2
ii  libx11-6  2:1.7.2-1
ii  remmina   1.4.20+dfsg-4

remmina-plugin-rdp:amd64 recommends no packages.

remmina-plugin-rdp:amd64 suggests no packages.

-- no debconf information


Bug#993618: RFS: openldap/2.4.59+dfsg-1~bpo11+1

2021-09-03 Thread Ryan Tandy

Package: sponsorship-requests
Severity: normal

Dear mentors and backporters,

As with previous releases, I am looking for a sponsor to perform the 
initial upload of openldap to bullseye-backports since it will be NEW. I 
am DM for the package and can take care of future uploads myself.


Rationale for backporting: while the client library (libldap) is mature 
and stable, the OpenLDAP server (slapd) is more actively developed, so 
advanced slapd users often prefer to run the latest upstream version.


The backport is a simple rebuild, no changes needed.

The package can be found on mentors.debian.net:

https://mentors.debian.net/package/openldap/
https://mentors.debian.net/debian/pool/main/o/openldap/openldap_2.4.59+dfsg-1~bpo11+1.dsc

The changes since stable are:

openldap (2.4.59+dfsg-1~bpo11+1) bullseye-backports; urgency=medium
.
  * Rebuild for bullseye-backports.
.
openldap (2.4.59+dfsg-1) unstable; urgency=medium
.
  * New upstream release.
  * Fix FTBFS with autoconf 2.71 (Closes: #993032):
- Backport upstream changes to support Autoconf 2.69 instead of simply
  disabling automake in debian/rules. Fixes FTBFS due to autoreconf
  thinking files required by Automake are missing, even though Automake is
  not actually used.
- Stop running autoreconf in contrib/ldapc++ since we don't build it.
- Drop custom config.{guess,sub} handling. dh_update_autotools_config does
  the right thing for us.
  * Update Standards-Version to 4.6.0; no changes required.
  * Add a superficial autopkgtest for smbk5pwd.
  * Stop disabling test060-mt-hot on ppc64el. The underlying kernel bug
(#866122) is fixed in all relevant suites by now.

Thank you,
Ryan



Bug#993617: Unable to play any video streaming site using Firefox 91

2021-09-03 Thread shirish शिरीष
Package: firefox-esr
Version: 91.0.1esr-1
Severity: normal

Dear Maintainer,

I have been unable to view any video streaming sites, e.g. youtube and
few others. I tried them both in normal mode and safe-mode but the
videos refuse to stream at all. It is possible that it may be due to
#993308 or it may be a completely different matter altogether. Hence
filing it as a new bug.

-- Package-specific info:

-- Extensions information
Name: Amazon.com
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Bing
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Certificate Viewer for Humans
Location: ${PROFILE_EXTENSIONS}/{13c639b4-1c39-478e-8f12-34f03412f43c}.xpi
Status: enabled

Name: Dark theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled

Name: DoH Roll-Out
Location: /usr/lib/firefox-esr/browser/features/doh-roll...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: DuckDuckGo
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Firefox Alpenglow theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled

Name: Firefox Screenshots
Location: /usr/lib/firefox-esr/browser/features/screensh...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: Form Autofill
Location: /usr/lib/firefox-esr/browser/features/formautof...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: Google
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Grammar and Spell Checker — LanguageTool
Location: ${PROFILE_EXTENSIONS}/languagetool-webextens...@languagetool.org.xpi
Status: enabled

Name: Grammarly for Firefox
Location: ${PROFILE_EXTENSIONS}/87677a2c52b84ad3a151a4a72f5bd...@jetpack.xpi
Status: enabled

Name: HTTPS Everywhere
Location: ${PROFILE_EXTENSIONS}/https-everywh...@eff.org.xpi
Status: enabled

Name: IndicateTLS
Location: ${PROFILE_EXTENSIONS}/{252ee273-8c8d-4609-b54d-62ae345be0a1}.xpi
Status: enabled

Name: Light theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled

Name: Mute Tab
Location: ${PROFILE_EXTENSIONS}/{95c22bd8-268a-4956-9969-c7e9ba2865a9}.xpi
Status: enabled

Name: Picture-In-Picture
Location: /usr/lib/firefox-esr/browser/features/pictureinpict...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: Reddit Enhancement Suite
Location: ${PROFILE_EXTENSIONS}/jid1-xufzosoflzs...@jetpack.xpi
Status: enabled

Name: RegretsReporter
Location: ${PROFILE_EXTENSIONS}/regrets-repor...@mozillafoundation.org.xpi
Status: enabled

Name: System theme theme
Location: /usr/lib/firefox-esr/omni.ja
Package: firefox-esr
Status: enabled

Name: Tree Style Tab
Location: /usr/share/webext/tree-style-tab
Package: webext-treestyletab
Status: user-disabled

Name: uBlock Origin
Location: ${PROFILE_EXTENSIONS}/ublo...@raymondhill.net.xpi
Status: enabled

Name: uMatrix
Location: ${PROFILE_EXTENSIONS}/umat...@raymondhill.net.xpi
Status: user-disabled

Name: Web Compatibility Interventions
Location: /usr/lib/firefox-esr/browser/features/webcom...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: WebCompat Reporter
Location: 
/usr/lib/firefox-esr/browser/features/webcompat-repor...@mozilla.org.xpi
Package: firefox-esr
Status: user-disabled

Name: Wikipedia (en)
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled


-- Addons package information
ii  firefox-esr 91.0.1esr-1  amd64Mozilla Firefox web
browser - Extended Support Release (ESR)
ii  webext-treestyletab 3.5.20-1 all  Show browser tabs like a tree

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'testing-debug'), (100,
'unstable-debug'), (100, 'experimental'), (100, 'unstable'), (50,
'experimental-debug')
Architecture: amd64 (x86_64)

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

Versions of packages firefox-esr depends on:
ii  debianutils  4.11.2
ii  fontconfig   2.13.1-4.2
ii  libatk1.0-0  2.36.0-2
ii  libc62.31-9
ii  libcairo-gobject21.16.0-5
ii  libcairo21.16.0-5
ii  libdbus-1-3  1.12.20-2
ii  libdbus-glib-1-2 0.110-6
ii  libevent-2.1-7   2.1.12-stable-1
ii  libffi7  3.3-6
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgcc-s110.2.0-9
ii  libgdk-pixbuf-2.0-0  2.42.6+dfsg-2
ii  libglib2.0-0 2.68.4-1
ii  libgtk-3-0   3.24.30-2
ii  libnspr4 2:4.32-1
ii  libnss3  2:3.68-1
ii  libpango-1.0-0   1.48.9+ds1-2
ii  libstdc++6   10.2.0-9
ii  libvpx6  1.9.0-1
ii  libx11-6 2:1.7.2-1
ii  

Bug#993606: RFP: libnet-sftp-perl -- pure-Perl implementation of the Secure File Transfer Protocol (SFTP)

2021-09-03 Thread Jonas Smedegaard
Quoting Jonathan Wiltshire (2021-09-03 17:35:24)
> Package: wnpp
> Severity: wishlist
> X-Debbugs-CC: debian-p...@lists.debian.org
> 
> * Package name: libnet-sftp-perl
>Version : 0.12
>Upstream Author : David Robins 
> * URL : https://metacpan.org/pod/Net::SFTP
> * License : Perl
>Programming Lang: Perl
>Description : pure-Perl implementation of the Secure File 
> Transfer Protocol (SFTP)
> 
> Upstream description:
> 
> Net::SFTP is a pure-Perl implementation of the Secure File Transfer
> Protocol (SFTP) - file transfer built on top of the SSH2 protocol.
> Net::SFTP uses Net::SSH::Perl to build a secure, encrypted tunnel
> through which files can be transferred and managed. It provides a subset
> of the commands listed in the SSH File Transfer Protocol IETF draft,
> which can be found at
> http://www.openssh.com/txt/draft-ietf-secsh-filexfer-00.txt.
> 
> SFTP stands for Secure File Transfer Protocol and is a method of
> transferring files between machines over a secure, encrypted connection
> (as opposed to regular FTP, which functions over an insecure
> connection). The security in SFTP comes through its integration with
> SSH, which provides an encrypted transport layer over which the SFTP
> commands are executed, and over which files can be transferred. The SFTP
> protocol defines a client and a server; only the client, not the server,
> is implemented in Net::SFTP.
> 
> Because it is built upon SSH, SFTP inherits all of the built-in
> functionality provided by Net::SSH::Perl: encrypted communications
> between client and server, multiple supported authentication methods
> (eg. password, public key, etc.).

Debian has multiple sftp implementations, an one of the differences is 
which versions of the protocol is supported (relevant e.g. for 
file-locking supported only in recent versions).

Please therefore mention in long description of the package which sftp 
protocol versions are supported.  This might be helpful:



 - Jonas

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

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

signature.asc
Description: signature


Bug#993615: ITP: golang-github-slack-go-slack -- This is Slack API in Go

2021-09-03 Thread Takuma Shibuya
Package: wnppSeverity: wishlistOwner: Takuma Shibuya
* Package name: golang-github-slack-go-slack
Version : 0.9.4-1  Upstream Author : Norberto Lopes
* URL :
https://github.com/slack-go/slack* License : BSD-2-clause
Programming Lang: Go  Description: This is Slack API in Go  This is
the original Slack library for Go created by Norberto Lopes,
transferred to a Github organization  .  This library supports most if
not all of the api.slack.com REST calls, as well as the Real-Time
Messaging protocol over websocket, in a fully managed way


Bug#993614: libbloom: Please restrict the valgrind build dependency

2021-09-03 Thread Adrian Bunk
Source: libbloom
Version: 1.6-4
Severity: serious
Tags: ftbfs

Please add an architecture restriction
[amd64 arm64 armhf i386 mipsel mips64el powerpc ppc64 ppc64el s390x]
to the valgrind build dependency.

This allows building libbloom on architectures without valgrind.

Severity set to RC since the build dependencies no longer being
fulfillable on armel blocks testing migration.



Bug#993613: lintian: Complex regular subexpression recursion limit exceeded in cruft check

2021-09-03 Thread Felix Lechner
Package: lintian

Hi,

A bunch of packages run for a very long time and show output similar to that:

Complex regular subexpression recursion limit (65534) exceeded at
/tmp/Lintian-OK2cEF3W/Lintian/lib/Lintian/Check/Cruft.pm line 760.

This is a known consequence of changes made to the cruft check in this
commit [1] although the source has not been identified. Most likely,
the license parsing will have to be rewritten with modern probability
techniques for text matching or by using a specialized tool. [2]

Kind regards
Felix Lechner

[1] 
https://salsa.debian.org/lintian/lintian/-/commit/3410cb55a647aa3844d5f1b189a6f73975059a74
[2] https://wiki.debian.org/CopyrightReviewTools



Bug#981446: Possible adoption of logcheck

2021-09-03 Thread Jose M Calhariz
Hi,


On Thu, Sep 02, 2021 at 09:55:36PM +0200, Hannes von Haugwitz wrote:
> Hi Jose,
> 
> On Mon, Aug 30, 2021 at 07:58:21PM +0100, Jose M Calhariz wrote:
> > I am a user of logckeck as I use on all my machines that I sysadmin
> > and I maintain some packages on Debian like for example at and amanda.
> > 
> > As now I would like to offer my help to package and fix logcheck as a
> > learning experience for a possibility in the future to be the
> > maintainer of logcheck.
> 
> This is great news!
> 
> The logcheck VCS repo is in the `debian` group on salsa.debina.org[0];
> so (as DD) you can just start to work on the package.
> 
> Please let me know if you have any questions or want some review.

Thank you for accepting me.

For now my question is:  Who is the upstream that you are using?


> 
> Best regards
> 
> Hannes
> 
> [0] https://salsa.debian.org/debian/logcheck/
> 


Kind regards
Jose M Calhariz


-- 
--

A história sugere que o capitalismo é uma condição necessária para a liberdade 
política. Evidentemente, não é uma condição suficiente

--Milton Friedmann


signature.asc
Description: PGP signature


Bug#834945: libquvi: please make the build reproducible

2021-09-03 Thread Boyuan Yang
Control: tags -1 +moreinfo
X-Debbugs-CC: la...@debian.org

Hi lamby,

On Sat, 20 Aug 2016 21:00:32 +0100 Chris Lamb  wrote:
> Source: libquvi
> Version: 0.9.3-1.2
> Severity: wishlist
> Tags: patch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: timestamps
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Hi,
> 
> Whilst working on the Reproducible Builds effort [0], I noticed
> that libquvi could not be built reproducibly.
> 
> Patch attached.

Looks like your patch is not enough. After merging the new patch, the updated
libquvi/0.9.3-2 still fails to build reproducibly. Can you take a look into
it?

Thanks,
Boyuan Yang


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


Bug#834945: libquvi: please make the build reproducible

2021-09-03 Thread Boyuan Yang
Control: tags -1 +moreinfo

Hi lamby,

On Sat, 20 Aug 2016 21:00:32 +0100 Chris Lamb  wrote:
> Source: libquvi
> Version: 0.9.3-1.2
> Severity: wishlist
> Tags: patch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: timestamps
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Hi,
> 
> Whilst working on the Reproducible Builds effort [0], I noticed
> that libquvi could not be built reproducibly.
> 
> Patch attached.

Looks like your patch is not enough. After merging the new patch, the updated
libquvi/0.9.3-2 still seems fail to build reproducibly. Can you take a look
into it?

Thanks,
Boyuan Yang


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


Bug#993587: qalculate-qt: QT interface for Qalculate!

2021-09-03 Thread Damir R. Islamov
Package: qalculate-gtk
Version: 3.20.1+git20210814-1
Severity: wishlist

Dear Maintainer,

A new Qt interface is available for Qalculate!
Please create a new package qalculate-qt.
Upstream: https://github.com/Qalculate/qalculate-qt

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

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

Versions of packages qalculate-qt depends on:
ii  libc6   2.31-17
ii  libgcc-s1   11.2.0-3
ii  libqalculate22  3.20.1-0.1
ii  libqt5core5a5.15.2+dfsg-10
ii  libqt5gui5  5.15.2+dfsg-10
ii  libqt5network5  5.15.2+dfsg-10
ii  libqt5widgets5  5.15.2+dfsg-10
ii  libstdc++6  11.2.0-3
ii  qalc3.20.1-0.1

Versions of packages qalculate-qt recommends:
ii  gnuplot-qt [gnuplot-x11]  5.4.1+dfsg1-1

qalculate-qt suggests no packages.

-- no debconf information



Bug#993612: bugs.debian.org: Socionext SynQuacer fails to mount rootfs after upgrade to Bullseye

2021-09-03 Thread Luca Di Stefano
Package: bugs.debian.org
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

A few days ago I tried to upgrade one of the six Socionext SynQuacers that we
have to the latest Debian release.

It was running fine on Buster using the 4.19 kernel and had no previous issues.

I followed the normal procedure for updating Debian to the next release:

- apt update; apt upgrade for the current OS and reboot
- changing the release's codename of all apt sources to bullseye
- apt update again
- apt upgrade; apt dist-upgrade
- reboot

The next boot sequence would start and get to the point where it would look for
the rootfs without finding it
and going into initramfs

I've then proceeded to reinstall buster on that machine and it just worked
fine, then also tried installing the kernel from backports linux-
image-5.10.0-0.bpo.8-arm64
 and after reboot it caused the same problem not finding the rootfs and going
into initramfs.

Searching about SynQuacer related issues i found Bug#891787
https://lists.debian.org/debian-kernel/2018/02/msg00348.html
and verified that those options mentioned in the bug report were enabled
correctly in both kernel config file for bullseye and for teh backported
kernel.

Thank you very much.

Luca







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

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



Bug#993611: xrootd FTBFS on 32bit: error: no matching function for call to ‘max(off64_t, uint64_t&)’

2021-09-03 Thread Adrian Bunk
Source: xrootd
Version: 5.3.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=xrootd=5.3.1-1

...
/<>/src/XrdCeph/src/XrdCeph/XrdCephPosix.cc: In function ‘ssize_t 
ceph_posix_pwrite(int, const void*, size_t, off64_t)’:
/<>/src/XrdCeph/src/XrdCeph/XrdCephPosix.cc:803:97: error: no 
matching function for call to ‘max(off64_t, uint64_t&)’
  803 | if (offset + count) fr->maxOffsetWritten = std::max(offset + count 
- 1, fr->maxOffsetWritten);
  | 
^
In file included from /usr/include/c++/10/memory:63,
 from 
/<>/src/XrdCeph/src/XrdCeph/XrdCephPosix.cc:36:
/usr/include/c++/10/bits/stl_algobase.h:254:5: note: candidate: ‘template constexpr const _Tp& std::max(const _Tp&, const _Tp&)’
  254 | max(const _Tp& __a, const _Tp& __b)
  | ^~~
/usr/include/c++/10/bits/stl_algobase.h:254:5: note:   template argument 
deduction/substitution failed:
/<>/src/XrdCeph/src/XrdCeph/XrdCephPosix.cc:803:97: note:   
deduced conflicting types for parameter ‘const _Tp’ (‘long long int’ and 
‘uint64_t’ {aka ‘long long unsigned int’})
  803 | if (offset + count) fr->maxOffsetWritten = std::max(offset + count 
- 1, fr->maxOffsetWritten);
  | 
^
In file included from /usr/include/c++/10/memory:63,
 from 
/<>/src/XrdCeph/src/XrdCeph/XrdCephPosix.cc:36:
/usr/include/c++/10/bits/stl_algobase.h:300:5: note: candidate: ‘template constexpr const _Tp& std::max(const _Tp&, const _Tp&, 
_Compare)’
  300 | max(const _Tp& __a, const _Tp& __b, _Compare __comp)
  | ^~~
/usr/include/c++/10/bits/stl_algobase.h:300:5: note:   template argument 
deduction/substitution failed:
/<>/src/XrdCeph/src/XrdCeph/XrdCephPosix.cc:803:97: note:   
deduced conflicting types for parameter ‘const _Tp’ (‘long long int’ and 
‘uint64_t’ {aka ‘long long unsigned int’})
  803 | if (offset + count) fr->maxOffsetWritten = std::max(offset + count 
- 1, fr->maxOffsetWritten);
  | 
^
...


Bug#993610: crafty: Potential Integer Overflow in tbdecode.h

2021-09-03 Thread Potential Buffer Overflow vulnerability in xfig-3.2.7b
Package: crafty
Version: 23.4
Severity: normal

Dear Maintainer,

There seems to exist potential integer overflow in tbdecode.h .


In line 647,
(647) if (fread(temp, 1, HEADER_SIZE, fd) != HEADER_SIZE)
...
(651) ptr = temp;
(652) #  define R4(i) \
(653) ((ptr[i] << 24) + (ptr[(i) + 1] << 16) + (ptr[(i) + 2] << 8) + (ptr[(i) + 
3]))
...
(661) n_blk = R4(72)
...
(683) n = sizeof(unsigned) * (1+n_blk)
...
(686) blk = (unsigned *)malloc(n);


temp is read from external source. ptr has the same value as temp, and n_blk is 
the result of R4(72).
Thus, arbitrary value of temp can cause n_blk to be a large number, which can 
cause integer overflow in line 683.
When allocating memory in 686, the value may not be as intended. 

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

Kernel: Linux 4.4.0-19041-Microsoft
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect



Bug#993415: libpinyin: Switch from Berkeley DB to Kyotocabinet?

2021-09-03 Thread Boyuan Yang
Hi,

在 2021-09-03星期五的 23:51 +0800,Shengjing Zhu写道:
> On Wed, Sep 1, 2021 at 8:00 AM Boyuan Yang  wrote:
> > 
> > Source: libpinyin
> > Version: 2.6.0-1
> > Severity: normal
> > Tags: sid bookworm
> > X-Debbugs-CC: czc...@debian.org alexep...@gmail.com
> > 
> > Dear Debian Input Method team members,
> > 
> > Currently libpinyin in Debian is using Berkeley DB (libdb-dev). After the
> > release of Debian 11, Debian has a release goal proposal to remove
> > Berkeley DB
> > due to its problematic AGPLv3 license issue (for details, see
> > https://bugs.debian.org/987013 ).
> 
> Please don't misread the bug, this is not a goal  that is confirmed by
> the Release team.

Indeed; that's why I wrote "release goal proposal" instead of "release goal".

Anyway, personally I expect it to occur sometime in future, sooner or later.
We already have a transition slot tracking the removal of libdb at
https://release.debian.org/transitions/html/db5.3-rm.html .

Thanks,
Boyuan Yang


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


Bug#993608: xfce4: blank screen after login after changing resolution

2021-09-03 Thread Claude Heiland-Allen

More information:

I am starting QEMU like this:

qemu-system-x86_64 \
-m 8G -hda hda.img -cpu host -accel kvm -smp 8 \
-vga virtio -display gtk,gl=on,show-cursor=on \
-usb -device usb-tablet \
-audiodev id=pa,driver=pa,in.frequency=44100,out.frequency=44100 \
-device intel-hda -device hda-duplex,audiodev=pa

The host is running Bullseye (previously testing), configured with 
amdgpu (OpenGL 4.6) and PipeWire.




Bug#992216: thunderbird: Version 91 available upstream and fixes security problems

2021-09-03 Thread Carsten Schoenert

Hello,

Am 03.09.21 um 11:28 schrieb Dimitris Pitsioris:

Thank you for informing me. I did update it and it works. A minor issue
I had remains though, but that's not important.

Sorry for complaining, but I do not know how ftp masters works. All I
know is to check these 2 for new packages in unstable and experimental

https://packages.debian.org/unstable/newpkg

https://packages.debian.org/experimental/newpkg


for me the most practical view for any package is quite always the
tracker site. For Thunderbird this can be found on this URL

https://tracker.debian.org/pkg/thunderbird

Now there is version 1:91.0.2-1 visible for the experimental release.
Before you would have found a URL with a link text of "NEW/experimental
$(version)" which points to package within the NEW queue.

The complete NEW queue itself can be found here:

https://ftp-master.debian.org/new.html

--
Regards
Carsten



Bug#993608: xfce4: blank screen after login after changing resolution

2021-09-03 Thread Claude Heiland-Allen
Package: xfce4
Version: 4.16
Severity: normal
X-Debbugs-Cc: cla...@mathr.co.uk

Dear Maintainer,

   * What led up to the situation?

I installed Debian 11.0 amd64 netinst in a QEMU virtual machine.
I deselected GNOME and selected XFCE4.

On first boot, after login, I changed screen resolution to 1440x900
using XFCE4 display settings user interface.

The display was fine at the new resolution until the next time I started
the virtual machine, at which point after LightDM login the screen went
black (at the 1440x900 size).

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

I created a new user which allowed me to log in graphically, but the
default video resolution is tiny and unsuitable for what I need the VM for.

   * What outcome did you expect instead?

I expected the desktop still to work after a reboot.


Thanks for any help,


Claude


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

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

Versions of packages xfce4 depends on:
ii  libxfce4ui-utils 4.16.0-1
ii  thunar   4.16.8-1
ii  xfce4-appfinder  4.16.1-1
ii  xfce4-panel  4.16.2-1
ii  xfce4-pulseaudio-plugin  0.4.3-1
ii  xfce4-session4.16.0-1
ii  xfce4-settings   4.16.0-1
ii  xfconf   4.16.0-2
ii  xfdesktop4   4.16.0-1
ii  xfwm44.16.1-1

Versions of packages xfce4 recommends:
ii  desktop-base  11.0.3
ii  tango-icon-theme  0.8.90-8
ii  thunar-volman 4.16.0-1
ii  xfce4-notifyd 0.6.2-1
ii  xorg  1:7.7+22

Versions of packages xfce4 suggests:
ii  xfce4-goodies4.14.0
ii  xfce4-power-manager  4.16.0-1

-- no debconf information
Xsession: X session started for claude at Fri  3 Sep 16:31:42 BST 2021
WARNING: tempfile is deprecated; consider using mktemp instead.
dbus-update-activation-environment: setting 
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/claude/.Xauthority
localuser:claude being added to access control list
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
/usr/bin/x-session-manager: X server already running on display :0
/usr/bin/iceauth:  creating new authority file /run/user/1000/ICEauthority
xfce4-session-Message: 16:31:43.041: SSH authentication agent is already running
gpg-agent: a gpg-agent is already running - not starting a new one

** (xfce4-power-manager:802): WARNING **: 16:31:43.791: Failed to get name 
owner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get 
owner of name 'org.xfce.PowerManager': no such name


** (xfce4-power-manager:802): WARNING **: 16:31:43.791: Failed to get name 
owner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get 
owner of name 'org.freedesktop.PowerManagement': no such name

Xfce power manager is not running
Xfce Power Manager: Another power manager is already running

(xfce4-power-manager:802): GLib-GObject-WARNING **: 16:31:43.898: 
../../../gobject/gsignal.c:2614: signal 'Changed' is invalid for instance 
'0x55f61b3bb0b0' of type 'GDBusProxy'
Another notification daemon is running, exiting

(xfce4-power-manager:802): xfce4-power-manager-WARNING **: 16:31:43.910: could 
not map keysym 1008ffa8 to keycode


** (xfce4-power-manager:802): WARNING **: 16:31:43.914: No outputs have 
backlight property

(xfce4-power-manager:802): xfce4-power-manager-WARNING **: 16:31:43.919: Failed 
to get keyboard max brightness level : 
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
“org.freedesktop.UPower.KbdBacklight” on object at path 
/org/freedesktop/UPower/KbdBacklight

(xfce4-panel:790): garcon-CRITICAL **: 16:31:44.082: 
garcon_gtk_menu_get_desktop_actions_menu: assertion 'actions != NULL' failed

(xfce4-panel:790): garcon-CRITICAL **: 16:31:44.107: 
garcon_gtk_menu_get_desktop_actions_menu: assertion 'actions != NULL' failed

(xfce4-panel:790): garcon-CRITICAL **: 16:31:44.135: 
garcon_gtk_menu_get_desktop_actions_menu: assertion 'actions != NULL' failed

(xfce4-panel:790): garcon-CRITICAL **: 16:31:44.161: 
garcon_gtk_menu_get_desktop_actions_menu: assertion 'actions != NULL' failed

** (wrapper-2.0:852): WARNING **: 16:31:44.252: No outputs have backlight 
property

(wrapper-2.0:853): GLib-GIO-CRITICAL **: 16:31:44.287: g_file_new_for_path: 
assertion 'path != NULL' failed

(wrapper-2.0:853): GLib-GIO-CRITICAL **: 16:31:44.287: g_file_monitor_file: 
assertion 'G_IS_FILE (file)' failed

(wrapper-2.0:853): GLib-GObject-WARNING 

Bug#993415: libpinyin: Switch from Berkeley DB to Kyotocabinet?

2021-09-03 Thread Shengjing Zhu
On Wed, Sep 1, 2021 at 8:00 AM Boyuan Yang  wrote:
>
> Source: libpinyin
> Version: 2.6.0-1
> Severity: normal
> Tags: sid bookworm
> X-Debbugs-CC: czc...@debian.org alexep...@gmail.com
>
> Dear Debian Input Method team members,
>
> Currently libpinyin in Debian is using Berkeley DB (libdb-dev). After the
> release of Debian 11, Debian has a release goal proposal to remove Berkeley DB
> due to its problematic AGPLv3 license issue (for details, see
> https://bugs.debian.org/987013 ).

Please don't misread the bug, this is not a goal  that is confirmed by
the Release team.

-- 
Shengjing Zhu



Bug#993606: RFP: libnet-sftp-perl -- pure-Perl implementation of the Secure File Transfer Protocol (SFTP)

2021-09-03 Thread Jonathan Wiltshire

Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-p...@lists.debian.org

* Package name: libnet-sftp-perl
  Version : 0.12
  Upstream Author : David Robins 
* URL : https://metacpan.org/pod/Net::SFTP
* License : Perl
  Programming Lang: Perl
  Description : pure-Perl implementation of the Secure File 
Transfer Protocol (SFTP)


Upstream description:

Net::SFTP is a pure-Perl implementation of the Secure File Transfer
Protocol (SFTP) - file transfer built on top of the SSH2 protocol.
Net::SFTP uses Net::SSH::Perl to build a secure, encrypted tunnel
through which files can be transferred and managed. It provides a subset
of the commands listed in the SSH File Transfer Protocol IETF draft,
which can be found at
http://www.openssh.com/txt/draft-ietf-secsh-filexfer-00.txt.

SFTP stands for Secure File Transfer Protocol and is a method of
transferring files between machines over a secure, encrypted connection
(as opposed to regular FTP, which functions over an insecure
connection). The security in SFTP comes through its integration with
SSH, which provides an encrypted transport layer over which the SFTP
commands are executed, and over which files can be transferred. The SFTP
protocol defines a client and a server; only the client, not the server,
is implemented in Net::SFTP.

Because it is built upon SSH, SFTP inherits all of the built-in
functionality provided by Net::SSH::Perl: encrypted communications
between client and server, multiple supported authentication methods
(eg. password, public key, etc.).



Bug#993605: lxml.etree.tostring() trailing junk

2021-09-03 Thread Jakub Wilk

Package: python3-lxml
Version: 4.6.3+dfsg-0.1
Control: affects -1 + urlwatch

After upgrading libxml2 to 2.9.12+dfsg-3, the tostring() function 
started returning strings with some trailing junk:


  >>> import lxml.etree
  >>> html = lxml.etree.fromstring('P')
  >>> lxml.etree.tostring(html[0])
  b'P'

This worked fine with libxml2 2.9.10+dfsg-6.7:

  >>> lxml.etree.tostring(html[0])
  b'P'


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

Versions of packages python3-lxml depends on:
ii  libc6   2.31-17
ii  libxml2 2.9.12+dfsg-3
ii  libxslt1.1  1.1.34-4
ii  python3 3.9.2-3

--
Jakub Wilk



Bug#915541: Removal of upstream "--will-cite" functionality has been reverted

2021-09-03 Thread Felix Lechner
Hi,

On Fri, Sep 3, 2021 at 7:50 AM Tobias Frost  wrote:
>
> But as said earlier: This is not a license issue; the license of GNU parallel
> would allow removal, but this would make upstream sad.
> The status quo is likely to mke our users sad, though.

Maybe the debconf system can provide a choice? The default could be
consistent with Debian's standards.

Kind regards
Felix Lechner



Bug#993604: bullseye-pu: package freeradius/3.0.21+dfsg-2.2+deb11u1

2021-09-03 Thread Bernhard Schmidt
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu

[ Reason ]
This update will fix two bugs in the bullseye package by cherry-picking
two upstream commits

Bug#992207 is a missing line continuation in the default config for the
freeradius-postgresql binary package that causes FreeRADIUS to fail to start

Bug#992036 is a crash bug in certain situations due to non-threadsafe memory
allocation. It is apparently not happening often, but it effectively broke
FreeRADIUS 3.x for my employer for several years. The fixed version has been
working great for several weeks now.

[ Impact ]
Bug#992207 broken default config
Bug#992036 frequent crash 

[ Tests ]
Package in sid has these patches as well and has passed autopkgtest. Proposed
update backported to buster has been running on my employers server for several
weeks.

[ Risks ]
One-line and two-line patch taken from upstream git repo, first one is
obviously correct, second patch comes from the main developer and is working
well.

[ Checklist ]
  [X] *all* changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in (old)stable
  [X] the issue is verified as fixed in unstable

[ Changes ]
see above

[ Other info ]
(Anything else the release team should know.)
diff -Nru freeradius-3.0.21+dfsg/debian/changelog 
freeradius-3.0.21+dfsg/debian/changelog
--- freeradius-3.0.21+dfsg/debian/changelog 2021-07-28 12:28:32.0 
+0200
+++ freeradius-3.0.21+dfsg/debian/changelog 2021-09-03 16:47:35.0 
+0200
@@ -1,3 +1,12 @@
+freeradius (3.0.21+dfsg-2.2+deb11u1) bullseye; urgency=medium
+
+  * Cherry-Pick upstream fix for a crash bug (Closes: #992036)
+  * Cherry-pick upstream fix to add missing continuation in postgresql
+sample config (Closes: #992207)
+  * d/gbp.conf for the debian/bullseye branch
+
+ -- Bernhard Schmidt   Fri, 03 Sep 2021 16:47:35 +0200
+
 freeradius (3.0.21+dfsg-2.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru freeradius-3.0.21+dfsg/debian/gbp.conf 
freeradius-3.0.21+dfsg/debian/gbp.conf
--- freeradius-3.0.21+dfsg/debian/gbp.conf  1970-01-01 01:00:00.0 
+0100
+++ freeradius-3.0.21+dfsg/debian/gbp.conf  2021-09-03 16:47:35.0 
+0200
@@ -0,0 +1,3 @@
+[DEFAULT]
+debian-branch = debian/bullseye
+
diff -Nru freeradius-3.0.21+dfsg/debian/patches/allocate-from-the-request.diff 
freeradius-3.0.21+dfsg/debian/patches/allocate-from-the-request.diff
--- freeradius-3.0.21+dfsg/debian/patches/allocate-from-the-request.diff
1970-01-01 01:00:00.0 +0100
+++ freeradius-3.0.21+dfsg/debian/patches/allocate-from-the-request.diff
2021-09-03 16:47:35.0 +0200
@@ -0,0 +1,34 @@
+From 7875ca06d1e312f55107c5e369097c7cb5369b53 Mon Sep 17 00:00:00 2001
+From: "Alan T. DeKok" 
+Date: Thu, 5 Aug 2021 11:22:12 -0400
+Subject: [PATCH] allocate from the request, which is thread-safe.  Helps with
+ #3188
+
+The "check" item is taken from the "huntgroups" file.  It's in
+a statically allocated list which doesn't change, and shouldn't
+change during run-time.  Allocating memory in its context is
+not thread-safe, and can cause issues
+---
+ src/main/pair.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/src/main/pair.c b/src/main/pair.c
+index 2f736d74cf7..3725ba1e10b 100644
+--- a/src/main/pair.c
 b/src/main/pair.c
+@@ -84,13 +84,13 @@ int radius_compare_vps(UNUSED REQUEST *request, VALUE_PAIR 
*check, VALUE_PAIR *v
+   if (check->da->type == PW_TYPE_STRING) {
+   expr_p = check->vp_strvalue;
+   } else {
+-  expr_p = expr = vp_aprints_value(check, check, '\0');
++  expr_p = expr = vp_aprints_value(request, check, '\0');
+   }
+ 
+   if (vp->da->type == PW_TYPE_STRING) {
+   value_p = vp->vp_strvalue;
+   } else {
+-  value_p = value = vp_aprints_value(vp, vp, '\0');
++  value_p = value = vp_aprints_value(request, vp, '\0');
+   }
+ 
+   if (!expr_p || !value_p) {
diff -Nru 
freeradius-3.0.21+dfsg/debian/patches/fix-postgresql-sample-config.diff 
freeradius-3.0.21+dfsg/debian/patches/fix-postgresql-sample-config.diff
--- freeradius-3.0.21+dfsg/debian/patches/fix-postgresql-sample-config.diff 
1970-01-01 01:00:00.0 +0100
+++ freeradius-3.0.21+dfsg/debian/patches/fix-postgresql-sample-config.diff 
2021-09-03 16:47:35.0 +0200
@@ -0,0 +1,28 @@
+From eef366956e2e4a689ab33a0d1f265eb15f749d8d Mon Sep 17 00:00:00 2001
+From: Alejandro Perez 
+Date: Mon, 6 Apr 2020 15:52:38 +0200
+Subject: [PATCH] Add missing backslash that precluded server from starting
+
+Server did not start, because it found an unterminated string. Adding the 
previous-existing backslash fixed it.
+```
+including configuration file 

Bug#993603: RM: sip5 -- ROM; superseded by sip6

2021-09-03 Thread Dmitry Shachnev
Package: ftp.debian.org
Severity: normal

Dear FTP Masters,

Please remove sip5 source package from unstable.

python3-sipbuild and python3-sipbuild-dbg are now built by sip6 source.
sip5-tools is replaced by sip-tools. No packages B-D on sip5-tools in sid.
sip5-doc is replaced by sip6-doc.

--
Dmitry Shachnev


signature.asc
Description: PGP signature


Bug#915541: Removal of upstream "--will-cite" functionality has been reverted

2021-09-03 Thread Tobias Frost
On Fri, Sep 03, 2021 at 08:44:49AM -0600, Sam Hartman wrote:
> > "Tobias" == Tobias Frost  writes:
> 
> Tobias> as explained earlier: click-wraps are no-no's.
> By this dxo you mean
> 
> 1) clip wraps are incompatible with the DFSG?  (I agree only if
> something in the license prevents you from removing them)
> 
> 2) Click wraps are a no-go in something you maintain?  (okay, sure,
> sounds good)
> 
> 3) Click wraps are incompatible with some written Debian policy or
> rules?  (I disagree)
> 
> 4) A lot of Debian maintainers might choose to remove click wraps or not
> package software with them (I agree)

1, 2 and 4 ;-)

But as said earlier: This is not a license issue; the license of GNU parallel
would allow removal, but this would make upstream sad.
The status quo is likely to mke our users sad, though.
(my 2 cents...)

-- 
tobi



Bug#983236: magics++: FTBFS with PROJ 8.0.0

2021-09-03 Thread Sebastiaan Couwenberg
Looks like this is fixed in 4.9.0-1 which built successfully with PROJ
8.1.1.

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



Bug#993602: /etc/runit/nosync should not have been moved to /run

2021-09-03 Thread Andras Korn
Package: runit
Version: 2.1.2-42
Severity: normal

Hi,

I'm the guy who originally submitted the patch to support a 'nosync' flag
file to avoid syncing on shutdown.

I noted with some amazement in the changelog for version 2.1.2-42 that this
file had been moved to /run sometime in the past, with no mention in the
changelog.

I think this change should be reverted.

The use case of the nosync flag file is when running runit in a container
like LXC or linux-vserver. When you stop one of these (or hundreds of these
simultaneously), you don't want them to sync() because the host itself isn't
stopping, so there is neither a need nor a benefit to invoking sync().

Not wanting to invoke sync() on shutdown is a permanent property of a
system, not an ephemeral one. Thus, the flag file for this behaviour should
be in a permanent location (like /etc/runit, where it originally was), not
under /run, where it would need to be created on every boot.

Best regards,

András

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

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /bin/bash
Init: runit (via /run/runit.stopit)
LSM: AppArmor: enabled

-- 
  A computer's attention span is as long as it's power cord.



Bug#915541: Removal of upstream "--will-cite" functionality has been reverted

2021-09-03 Thread Sam Hartman
> "Tobias" == Tobias Frost  writes:

Tobias> as explained earlier: click-wraps are no-no's.
By this dxo you mean

1) clip wraps are incompatible with the DFSG?  (I agree only if
something in the license prevents you from removing them)

2) Click wraps are a no-go in something you maintain?  (okay, sure,
sounds good)

3) Click wraps are incompatible with some written Debian policy or
rules?  (I disagree)

4) A lot of Debian maintainers might choose to remove click wraps or not
package software with them (I agree)



Bug#993601: O: libopenaptx -- Audio Processing Technology codec (aptX), shared libraries

2021-09-03 Thread Didier 'OdyX' Raboud
Package: wnpp
Severity: normal
X-Debbugs-Cc: libopena...@packages.debian.org
Control: affects -1 src:libopenaptx


I have orphaned the libopenaptx package for reasons independant of this 
package, or
of Debian.

The package description is:
 Support for aptX and aptX HD codec variants; they both operate on raw 24-bit
 signed stereo audio sample; at 6:1 fixed compress ratio for aptX; at 4:1 fixed
 compress ratio for aptX HD.
 .
 This package contains the shared libraries.


Bug#965326: Changelogs of 'linux' package in stretch+buster are 404

2021-09-03 Thread Neil Williams
On Tue, 10 Nov 2020 13:52:21 +0800 Paul Wise  wrote:
> On Mon, 09 Nov 2020 17:47:48 + Ben Hutchings wrote:
> 
> > I think this is true for all security uploads, unfortunately.  I
> > thought I had reported this bug previously, but can't find such a
> > report.
> 
> Indeed, the bug report (and many other merged duplicates) is:
> 
> https://bugs.debian.org/490848
> 
> > tracker.debian.org publishes changelogs from both main and security
> > archives, so I think packages.debian.org should link to those
> > instead of metadata.ftp-master.debian.org.

Just a note that I'm working on a possible solution for this
long-standing bug.

A tweak to distro-tracker makes it easier for packages.d.o to use the
tracker URLs. Once the review of that change is complete, I'll make a
merge request for the change to packages.d.o


-- 
Neil Williams
=
https://linux.codehelp.co.uk/


pgp6eq4iZfNX5.pgp
Description: OpenPGP digital signature


Bug#993600: obs-plugins: Please, add "studio" to description

2021-09-03 Thread Joao Eriberto Mota Filho
Package: obs-plugins
Version: 27.0.1+dfsg1-1
Severity: normal
X-Debbugs-Cc: eribe...@debian.org

Dear Maintainer,

When searching for "obs studio" I was not able to find the package obs-plugins.
Please, consider to add the word "studio" in description.

Regards,

Eriberto



Bug#993574: python3-virtualsmartcard: Cannot import virtualsmartcard module

2021-09-03 Thread Guinness
Hi,

It seems very logical to me that it cannot import virtualsmartcard if
it's in site-packages and not dist-packages.
I'll have a look at the debian rules to patch it and upload it here, or
if Philippe allows me, package it and have it uploaded by my mentor
nicoo.

Best regards,
-- 
Guinness


signature.asc
Description: PGP signature


Bug#993599: O: jimtcl -- small-footprint implementation of Tcl named Jim

2021-09-03 Thread Didier 'OdyX' Raboud
Package: wnpp
Severity: normal
X-Debbugs-Cc: jim...@packages.debian.org
Control: affects -1 src:jimtcl

I have orphaned the jimtcl package for reasons independant of this package, or
of Debian.

The package description is:
 Jim is an opensource small-footprint implementation of the Tcl programming
 language. It implements a large subset of Tcl and adds new features like
 references with garbage collection, closures, built-in Object Oriented
 Programming system, Functional Programming commands, first-class arrays and
 UTF-8 support. All this with a binary size of about 100-200kB (depending upon
 selected options).
 .
 This package provides the Jim interactive shell.



Bug#993598: ITP: libadwaita -- Building blocks for modern GNOME applications

2021-09-03 Thread Guido Günther
Package: wnpp
Severity: wishlist
Owner: Guido Günther 
X-Debbugs-Cc: debian-de...@lists.debian.org, 
pkg-gnome-maintain...@lists.alioth.debian.org

* Package name: libadwaita
  Version : 1.0.0~alpha.2
  Upstream Author : Alexander Mikhaylenko  and more
* URL : https://gitlab.gnome.org/GNOME/libadwaita/
* License : LGPL
  Programming Lang: C
  Description : Building blocks for modern GNOME applications

libadwaita is a collection of GTK widgets for adaptive applications targeting
form-factors from mobile to desktop.
It also offers widgets following the GNOME design guidelines.

The package will be maintained withing gnome-team on salsa.

Cheers,
 -- Guido



Bug#970380: (kein Betreff)

2021-09-03 Thread c . buhtz

1. Unclear log message about "Security Layer"
I assume this as upstream related so I opened an Issue there.
https://github.com/neutrinolabs/xrdp/issues/1974


Is fixed and merged in upstream.
https://github.com/neutrinolabs/xrdp/pull/1975#event-5252991803



Bug#993597: xdvik-ja: fails to show Japanese characters

2021-09-03 Thread Atsuhito Kohda
Package: xdvik-ja
Version: 22.87.05+j1.42-2
Severity: normal

Dear Maintainer,

I need to view rather old DVI file generated by pTeX.
So I installed xdvik-ja and try "xdvi test.dvi".
But it shows only English texts and mathematical equations
but fails to show Japanese characters completely.

I forget how xdvik-ja finds Japanese fonts but 
it seems xdvik-ja reads kanjix.map and it sets;

rml H !Ryumin-Light

and I think Ryumin-Light should be mapped to a real fonts,
for example, ipaexm.ttf but I can't find what file does that.
Is some extra setting necessary for xdvik-ja to work properly?

Thanks for your maintenance.

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

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.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 xdvik-ja depends on:
ii  fontconfig  2.13.1-4.2
ii  fonts-ipaexfont-gothic [fonts-japanese-gothic]  00401-3
ii  fonts-ipaexfont-mincho [fonts-japanese-mincho]  00401-3
ii  fonts-ipafont-gothic [fonts-japanese-gothic]00303-23
ii  fonts-ipafont-mincho [fonts-japanese-mincho]00303-23
ii  fonts-takao-gothic [fonts-japanese-gothic]  00303.01-3
ii  fonts-takao-mincho [fonts-japanese-mincho]  00303.01-3
ii  fonts-vlgothic [fonts-japanese-gothic]  20200720-1
ii  libc6   2.31-17
ii  libfreetype62.10.4+dfsg-1
ii  libkpathsea62020.20200327.54578-7
ii  libx11-62:1.7.2-1
ii  libxaw7 2:1.0.13-1.1
ii  libxi6  2:1.7.10-1
ii  libxmu6 2:1.1.2-2+b3
ii  libxpm4 1:3.5.12-1
ii  libxt6  1:1.2.0-1
ii  texlive-binaries2020.20200327.54578-7

xdvik-ja recommends no packages.

xdvik-ja suggests no packages.

-- no debconf information



Bug#993596: futatabi: potential integer overflow vulnerability in util.cpp

2021-09-03 Thread Wooseok Kang
Package: futatabi
Severity: normal
X-Debbugs-Cc: kangwoos...@gmail.com

Dear Maintainer,

I found a potential integer overflow vulnerability in util.cpp.

At line 14 to 15, the program reads the value of 'width' and 'height' using 
fread.
Since there is no bound checking, it may cause an integer overflow by 
maliciously crafted input file.
Then it leads a small buffer allocation which may cause buggy behavior.

14 fread(, sizeof(width), 1, flowfp);
15 fread(, sizeof(height), 1, flowfp);
16
17 unique_ptr flow(new Vec2[width * height]);

Thank you.

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

Kernel: Linux 5.10.16.3-microsoft-standard-WSL2 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages futatabi depends on:
pn  libasound2   
pn  libavcodec58 
pn  libavformat58
pn  libavutil56  
ii  libc62.31-17
ii  libepoxy01.5.8-1
ii  libgcc-s111.2.0-3
ii  libjpeg62-turbo  1:2.0.6-4
pn  libmicrohttpd12  
pn  libmovit8
pn  libprotobuf23
ii  libqt5core5a 5.15.2+dfsg-10
ii  libqt5gui5   5.15.2+dfsg-10
ii  libqt5network5   5.15.2+dfsg-10
pn  libqt5opengl5
ii  libqt5widgets5   5.15.2+dfsg-10
ii  libsqlite3-0 3.36.0-2
ii  libstdc++6   11.2.0-3
pn  libswscale5  
pn  libva-drm2   
pn  libva-x11-2  
pn  libva2   
ii  libx11-6 2:1.7.2-1

futatabi recommends no packages.

futatabi suggests no packages.



Bug#993595: RM: bcachefs-tools/experimental -- NVIU; crufty package in experimental

2021-09-03 Thread Jonathan Carter
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: j...@debian.org

Dear FTP masters

Please remove crufty version of bcachefs-tools (0.1+git20190829.aa2a42b-1~exp1) 
in experimental,
since a newer version exists in unstable.

thanks,

-Jonathan



Bug#993594: thunderbird: No (official) extension can be installed anymore

2021-09-03 Thread Vincent Danjean
Package: thunderbird
Version: 1:91.0.2-1
Severity: important

  Hi,

  I just tried thunderbird 91.0.2 from experimental. Once upgraded,
no extension can be installed / upgraded anymore.

  To check that this does not come from my profile/setup, I
installed thunderbird/experimental in a fresh virtual machine.
Then, I tried to install some of the recommended add-ons (from
the thunderbird add-on manager). I got popup with the following
error messages:
"Thunderbird has prevented this site from installing an
unverified add-on"
I tried the following extension (the first proposed):
- Addon Compatibility Check for TB 91
- Thunderbird Conversations
- Quecktext
- Dictionary for recipient
- CardBook

  Regards,
Vincent


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

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

Versions of packages thunderbird depends on:
ii  debianutils  4.11.2
ii  fontconfig   2.13.1-4.2
ii  libatk1.0-0  2.36.0-2
ii  libbotan-2-172.17.3+dfsg-3
ii  libbz2-1.0   1.0.8-4
ii  libc62.31-13
ii  libcairo-gobject21.16.0-5
ii  libcairo21.16.0-5
ii  libdbus-1-3  1.12.20-2
ii  libdbus-glib-1-2 0.110-6
ii  libevent-2.1-7   2.1.12-stable-1
ii  libffi7  3.3-6
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.8-1
ii  libgtk-3-0   3.24.24-4
ii  libicu69 69.1-2
ii  libjson-c5   0.15-2
ii  libnspr4 2:4.32-1
ii  libnss3  2:3.68-1
ii  libpango-1.0-0   1.46.2-3
ii  libstdc++6   10.2.1-6
ii  libvpx6  1.10.0+really1.8.1-dmo1
ii  libx11-6 2:1.7.2-1
ii  libx11-xcb1  2:1.7.2-1
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3
ii  libxext6 2:1.3.3-1.1
ii  libxrender1  1:0.9.10-1
ii  psmisc   23.4-2
ii  x11-utils7.7+5
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages thunderbird recommends:
ii  hunspell-fr-classical [hunspell-dictionary]  1:7.0-1
ii  myspell-en-us [myspell-dictionary]   1:3.3.0-4+deb8u1

Versions of packages thunderbird suggests:
ii  apparmor  2.13.6-10
ii  fonts-lyx 2.3.6-1
ii  libgssapi-krb5-2  1.18.3-6

-- no debconf information



Bug#993373: Use-after-free bug in realpath()

2021-09-03 Thread Madie K. Mckeel
Dear Antonin

Thanks for your replay.

On Tuesday, August 31, 2021 4:04 PM, Antonin Décimo  
wrote:

> Last year I wrote a lot of patches for pmount, amongst which two
> remove the bundled implementation of realpath and switch to the
> "modern" interface
>
> char *realpath(const char *restrict path, NULL);

> [...]
> Instead of the patch you send, why not drop it completely like I did?

Definitely the better option in any regard! I feared the packages is not
well-maintained, so I opted for a patch which doesn't touch much hoping
to reduce maintenance burden and get this fixed easily. (And also because
I don't program C and don't know the (often subtle) differences in those
implementations).

> I'm also afraid that the Debian package is unmaintained.

Sad news. So I guess the best is to avoid pmount packages for now.

> I wasn't ready to release my updated pmount as the current head commit
> is broken, and I haven't had time to fix it. I also need to convince
> myself that the commit history looks good and that I haven't
> introduced more bugs than I've fixed.
>
> If you have some time to spare, please take a look!

Nice to see that someone gave some love to pmount in the last years!
I tested your HEAD but as you mentioned it's doesn't work.
As I said, I don't program C, so probably can't help you with that problem.
I hope you're fork will become the source eventually.
Maybe linking to your repo instead of a dead alioth-archive page would rise
its visibility, getting one step closer to that goal.

Regards
Madie

Bug#991266: postinst: Can't exec systemctl: No such file or directory

2021-09-03 Thread Hilmar Preuße

Am 19.07.2021 um 10:23 teilte Lorenzo Puliti mit:

Hi Lorenzo, hi Francesco,


[...]
Setting up proftpd-core (1.3.7b+dfsg-1) ...
usermod: no changes
Can't exec "systemctl": No such file or directory at 
/usr/bin/deb-systemd-invoke line 110.
sh: 1: systemctl: not found
Can't exec "systemctl": No such file or directory at 
/usr/bin/deb-systemd-invoke line 94.
proftpd.service is a disabled or a static unit not running, not starting it.
insserv: warning: current start runlevel(s) (empty) of script `proftpd' 
overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `proftpd' 
overrides LSB defaults (0 1 6).
insserv: Script `lvm2' has overlapping Default-Start and Default-Stop runlevels 
(S) and (S). This should be fixed.
Stopping ftp server: proftpd.
Starting ftp server: proftpd.
[...]

Not a tragic issue since it looks that postinst script proceeds anyway with the 
rest
of the configuration, but if you look at snippets from debhelper 
deb-systemd-invoke is always
called only if systemd is PID1. The patch at the bottom should fix the issue.


Thanks for the patch!

On the other hand the dh_installsystemd command adds the following code 
block below to the postinst script.


I'm missing here the "deb-systemd-invoke restart" command here, but I'm 
not sure if it is really needed. I tend to remove completely our hand 
written code and leave the job to debhelper.


Hilmar



# Automatically added by dh_installsystemd/13.5.1
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then

if deb-systemd-helper debian-installed 'proftpd.service'; then
# This will only remove masks created by d-s-h on 
package removal.
deb-systemd-helper unmask 'proftpd.service' >/dev/null 
|| true


if deb-systemd-helper --quiet was-enabled 
'proftpd.service'; then

# Create new symlinks, if any.
deb-systemd-helper enable 'proftpd.service' 
>/dev/null || true

fi
fi

# Update the statefile to add new symlinks (if any), which need 
to be cleaned

# up on purge. Also remove old symlinks.
deb-systemd-helper update-state 'proftpd.service' >/dev/null || 
true

fi
# End automatically added section

--
sigfault




OpenPGP_signature
Description: OpenPGP digital signature


Bug#993593: refind: bullseye installs with qemu boot problems

2021-09-03 Thread Marc Leeman
Package: refind
Version: 0.12.0-1
Severity: important

Dear Maintainer,

(also posted on
https://sourceforge.net/p/refind/discussion/general/thread/1188d50b6c/)

I am having 2 strange problems when running the combination of debian 11
(bullseye) in qemu with UEFI/refind.

The first one is that, contrary to the versions in debian 10, I cannot
boot the system anymore without attaching a graphics environment to
it. The system just gives me a screen dump and refuses to boot.

sudo qemu-system-x86_64 -enable-kvm -drive
if=pflash,format=raw,readonly,file=/usr/share/OVMF/OVMF_CODE.fd -drive
if=pflash,format=raw,file=./bullseye-unstable-1.04.12-amd64-20210903-114025.nvars.fd
-drive
format=qcow2,file=./bullseye-unstable-1.04.12-amd64-20210903-114025.qcow2
-drive format=qcow2,file=ssd-disk.qcow2 -device
e1000,netdev=net0,mac=52:54:82:8b:e9:ed -netdev tap,id=net0 -device
e1000,netdev=net1,mac=52:54:4f:84:9c:24 -netdev tap,id=net1 -m 4G -cpu host
-smp 2

add the -nographic flag and the system, and the system is drops a
shell dump.

13:36:28
 
�[2J�[01;01H�[=3h�[2J�[01;01H�[2J�[01;01H�[=3h�[2J�[01;01H�[2J�[01;01H�[=3h�[2J�[01;01H�[0m�[35m�[40m�[2J�[01;01H�[=3h�[2J�[01;01H�[0m�[37m�[40m
X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - 

13:36:28  ExceptionData - 
13:36:28  RIP - BFF1411A, CS - 0038, RFLAGS -
00010206
13:36:28  RAX - 0004, RCX - 0010, RDX -
0002
13:36:28  RBX - AFAFAFAFAFAFAFAF, RSP - BFF039C0, RBP -
BFF03A9C
13:36:28  RSI - BFF03A9C, RDI - AFAFAFAFAFAFAFAF
13:36:28  R8 - 0002, R9 - , R10 -

13:36:28  R11 - 0C80, R12 - BFF03B68, R13 -
BE370C80
13:36:28  R14 - BE36F100, R15 - BFF03B60
13:36:28  DS - 0030, ES - 0030, FS -
0030
13:36:28  GS - 0030, SS - 0030
13:36:28  CR0 - 80010033, CR2 - , CR3 -
BFC01000
13:36:28  CR4 - 0668, CR8 - 
13:36:28  DR0 - , DR1 - , DR2 -

13:36:28  DR3 - , DR6 - 0FF0, DR7 -
0400
13:36:28  GDTR - BFBEE698 0047, LDTR - 
13:36:28  IDTR - BF2A2018 0FFF, TR - 
13:36:28  FXSAVE_STATE - BFF03620
13:36:28   Find image based on IP(0xBFF1411A)
/build/edk2-fUa9k0/edk2-0~20181115.85588389/Build/OvmfX64/RELEASE_GCC49/X64/MdeModulePkg/Core/Dxe/DxeMain/DEBUG/DxeCore.dll
(ImageBase=BFF04000, EntryPoint=BFF062A0) 

This is annoying for automated testing and integration.

However, the major nuisance, and I've not been able to resolve this or
debug it, is that a system that was installed with a debian installler iso
file does not seem to boot anymore with refind, using the same command
line as above, while performing exactly the same install/script with
buster does allow the system to boot and a real HW system (installed
with the same iso file) does boot with refind (both buster and bullseye).

Actually, small correction, it boots with refind (as it shows the
background, cf. config), but it does not show the menu, nor does it
perform any action.

menuentry "Linux A" {
icon /EFI/refind/icons/os_debian.png
volume   boot_a
loader   /vmlinuz-5.10.0-8-amd64
initrd   /initrd.img-5.10.0-8-amd64
options  "root=/dev/mapper/dsk00-root_a ro quiet consoleblank=0
fsprotect fsck.mode=skip console=ttyS0 reboot=pci"
}

banner banner.png
banner_scale fillscreen
default_selection "Linux A,"

One small modification I needed to do (while porting for bullseye),
was to add the slash in front of the loader/initrd (was not needed in
buster) to get it to boot on hardware with debian 11 and a small fix to
the installer script [1].

However after booting the same system (so installed with debian
netinst/refind/no-grub), installing grub in rescue mode (grub-mkdconfig,
grub-install), does allow to boot the system (using grub).

This only happens in bullseye (debian 11), not in buster (debian 10).

I am wondering if I have missed a configuration change or perhaps am
using a wrong configuration setting that got deprecated in the debian 11
version.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991945



-- 
g. Marc


Bug#993592: libgda5: CVE-2021-39359

2021-09-03 Thread Salvatore Bonaccorso
Source: libgda5
Version: 5.2.9-2
Severity: important
Tags: security upstream
Forwarded: https://gitlab.gnome.org/GNOME/libgda/-/issues/249
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for libgda5.

CVE-2021-39359[0]:
| In GNOME libgda through 6.0.0, gda-web-provider.c does not enable TLS
| certificate verification on the SoupSessionSync objects it creates,
| leaving users vulnerable to network MITM attacks. NOTE: this is
| similar to CVE-2016-20011.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-39359
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39359
[1] https://gitlab.gnome.org/GNOME/libgda/-/issues/249

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore



Bug#952950: nss: Replace PKCS11 headers provided by OASIS

2021-09-03 Thread Bastian Germann

Control: severity -1 normal

On Thu, 1 Apr 2021 23:48:51 +0200 Timo Röhling  wrote:

On Tue, 23 Mar 2021 00:44:07 +0100 Bastian Germann  
wrote:
> As far as I can see, the license for NSS's PKCS#11 headers is MPL 2.0
> (DFSG-free) and not the OASIS IPR.
Well, I can see from the discussion you linked that the OASIS IPR
license is intended to apply to their work products, and not the shared
code. And they do have separate rules for their open repositories, which
default to BSD-3-Clause license unless stated otherwise [1].

However, the PKCS#11 repository [2] is not in the linked "oasis-open"
namespace on Github, there is an explicit reference to the IPR
license in that repository.

As for the MPL 2.0 license, the Mozilla upstream added that to their
version of the headers after stating that bug 1618918 had clarified the
situation, but I can't seem to access that bug [3].

Cheers
Timo

[1] https://www.oasis-open.org/open-repositories/#licensingRules
[2] https://github.com/oasis-tcs/pkcs11
[3] https://bugzilla.mozilla.org/show_bug.cgi?id=1618918


The nss PKCS#11 files have a different provenance from the OASIS ones. If Mozilla decides to license 
them as MPL 2.0, that is their choice. They have a legal department who was involved and decided 
they go this way. The point is, the license of the files is not the OASIS one as suggested by the 
bug submitter, so the bug is invalid. I do not think the license was OASIS in any of the public NSS 
releases, even though it might have been in some patch submission.




Bug#993591: borgmatic: systemd unit not shipped (related to #989322)

2021-09-03 Thread kaliko
Package: borgmatic
Version: 1.5.18-1
Severity: important
Tags: patch

Dear Maintainer,

I believe building 1.5.18-1 from salsa ends up with wrong systemd units.

usr/lib/systemd/system/borgmatic.sercice:
   sample/systemd/borgmatic.service

and usr/lib/systemd/system/borgmatic.timer:
   sample/systemd/borgmatic.timer

Here is a patch (also on salsa
https://salsa.debian.org/debian/borgmatic/-/merge_requests/4)

Please review
Thanks

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

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

Versions of packages borgmatic depends on:
ii  borgbackup 1.1.16-3
ii  python33.9.2-3
ii  python3-colorama   0.4.4-1
ii  python3-jsonschema 3.2.0-3
ii  python3-pkg-resources  52.0.0-4
ii  python3-requests   2.25.1+dfsg-2
ii  python3-ruamel.yaml0.16.12-2

borgmatic recommends no packages.

borgmatic suggests no packages.

-- no debconf information
diff --git a/debian/borgmatic.install b/debian/borgmatic.install
new file mode 100644
index 000..3551078
--- /dev/null
+++ b/debian/borgmatic.install
@@ -0,0 +1,2 @@
+sample/systemd/borgmatic.service usr/lib/systemd/system
+sample/systemd/borgmatic.timer   usr/lib/systemd/system
diff --git a/debian/borgmatic.service b/debian/borgmatic.service
deleted file mode 100644
index 75647e0..000
--- a/debian/borgmatic.service
+++ /dev/null
@@ -1 +0,0 @@
-sample/systemd/borgmatic.service
diff --git a/debian/borgmatic.timer b/debian/borgmatic.timer
deleted file mode 100644
index a643e4f..000
--- a/debian/borgmatic.timer
+++ /dev/null
@@ -1 +0,0 @@
-sample/systemd/borgmatic.timer


Bug#993574: python3-virtualsmartcard: Cannot import virtualsmartcard module

2021-09-03 Thread Robin Krahl
Package: python3-virtualsmartcard
Version: 3.3+dfsg-2
Severity: important

Dear Maintainer,

after installing the python3-virtualsmartcard package, I cannot import
it with python3:

$ python3
Python 3.9.2 (default, Feb 28 2021, 17:03:44)
[GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import virtualsmartcard
Traceback (most recent call last):
  File "", line 1, in 
ModuleNotFoundError: No module named 'virtualsmartcard'

As far as I see, this is because the package is installed into
/usr/lib/python3/site-packages instead of <..>/dist-packages:

$ apt-file show python3-virtualsmartcard | grep __init__.py
python3-virtualsmartcard: 
/usr/lib/python3/site-packages/virtualsmartcard/virtualsmartcard/__init__.py
python3-virtualsmartcard: 
/usr/lib/python3/site-packages/virtualsmartcard/virtualsmartcard/cards/__init__.py

$ python3 -m site
sys.path = [
'/home/robin',
'/usr/lib/python39.zip',
'/usr/lib/python3.9',
'/usr/lib/python3.9/lib-dynload',
'/usr/local/lib/python3.9/dist-packages',
'/usr/lib/python3/dist-packages',
]
USER_BASE: '/home/robin/.local' (exists)
USER_SITE: '/home/robin/.local/lib/python3.9/site-packages' (doesn't exist)
ENABLE_USER_SITE: True

If I manually put that folder in the Python path, for example by linking
/usr/lib/python3/site-packages/virtualsmartcard/virtualsmartcard to
~/.local/lib/python3.9/site-package/virtualsmartcard, I can at least
import the virtualsmartcard module.  But there seem to be missing
dependencies:

>>> import virtualsmartcard.VirtualSmartcard
Traceback (most recent call last):
  File 
"/home/robin/.local/lib/python3.9/site-packages/virtualsmartcard/CryptoUtils.py",
 line 29, in 
from Crypto.Cipher import DES3, DES, AES, ARC4  # @UnusedImport
ModuleNotFoundError: No module named 'Crypto'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "", line 1, in 
  File 
"/home/robin/.local/lib/python3.9/site-packages/virtualsmartcard/VirtualSmartcard.py",
 line 31, in 
from virtualsmartcard.CardGenerator import CardGenerator
  File 
"/home/robin/.local/lib/python3.9/site-packages/virtualsmartcard/CardGenerator.py",
 line 34, in 
from virtualsmartcard.SmartcardSAM import SAM
  File 
"/home/robin/.local/lib/python3.9/site-packages/virtualsmartcard/SmartcardSAM.py",
 line 24, in 
import virtualsmartcard.CryptoUtils as vsCrypto
  File 
"/home/robin/.local/lib/python3.9/site-packages/virtualsmartcard/CryptoUtils.py",
 line 35, in 
import sha as SHA1
ModuleNotFoundError: No module named 'sha'

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

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

Versions of packages python3-virtualsmartcard depends on:
ii  python3  3.9.2-3

python3-virtualsmartcard recommends no packages.

python3-virtualsmartcard suggests no packages.

-- no debconf information



Bug#993527: mariadb-server: At full-upgrade from buster to bullseye mariadb-server (and also client) are removed.

2021-09-03 Thread Tobias Frost
Hi Otto,

was helping Sven with triaging, so bit more info what I did...

First I tried the pinning setup like Sven did, but as I'm not 100%
sure that my pinning works as intended, I also tried another approach

The base for those experiments was a buster pbuilder chroot with
mariadb installed manually and then adding sources for bullseye and testing.
After pinning so that only '*mariadb*' and '*mysql'* packages might be pulled
from testing, apt policy maradb-server showed me the version from testing is
candidate while all other packages are not pulled from testing.

However, apt dist-upgrade still thought the solution is to remove 
mysql-server...

As I am not 100% sure that I understood pinning correctly, I did another 
approach:

I've repbuilt the packge from testing for bullseye, kind of something that 
would be
good for stable-proposed-updates. Rebuild has been done in a bullseye pbuilder 
env
without any changes, as in:

apt source mariadb-10.5
DIST=bullseye pbuilder build mariadb-10.5_10.5.12-1.dsc

I've placed the resulting packages in a local apt repository; and then loged in 
into
an buster pbuilder chroot (DIST=buster pbuilder login)
There, I installed mariadb and then activated in sources.list the local repo 
and bullseye,
followed by apt dist-upgrade.

Unfortunatly, this also tries to remove mariadb-server:

root@isildor:/# apt dist-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  iproute2 libaio1 libapt-inst2.0 libboost-iostreams1.67.0 
libboost-system1.67.0 libbpf0 libbsd0
  libcap2 libcap2-bin libconfig-inifiles-perl libcwidget3v5 libdbi-perl libelf1 
libmd0 libmnl0
  libncurses6 libpopt0 libreadline5 libreadline7 libsnappy1v5 libwrap0 
libxtables12 lsof
  mariadb-common mariadb-server-core-10.3 mysql-common psmisc rsync socat
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  g++-8 galera-3 gcc-8 libgcc-8-dev libstdc++-8-dev mariadb-client-10.3 
mariadb-client-core-10.3
  mariadb-server mariadb-server-10.3
The following NEW packages will be installed:
  cpp-10 g++-10 gcc-10 gcc-10-base gcc-9-base libapt-pkg6.0 libasan6 
libboost-iostreams1.74.0 libbpf0
  libbsd0 libcrypt-dev libcrypt1 libctf-nobfd0 libctf0 libcwidget4 libffi7 
libgcc-10-dev libgcc-s1
  libgssapi-krb5-2 libhogweed6 libisl23 libk5crypto3 libkeyutils1 libkrb5-3 
libkrb5support0 libmd0
  libnettle8 libnsl-dev libnsl2 libpcre2-8-0 libperl5.32 libreadline8 
libstdc++-10-dev libtirpc-common
  libtirpc-dev libtirpc3 libxxhash0 logsave perl-modules-5.32
The following packages will be upgraded:
  apt apt-utils aptitude aptitude-common base-files base-passwd bash binutils 
binutils-common
  binutils-x86-64-linux-gnu bsdutils build-essential bzip2 ccache coreutils cpp 
dash debconf
  debian-archive-keyring debianutils diffutils dpkg dpkg-dev e2fsprogs fdisk 
findutils g++ gawk gcc
  gpgv grep gzip hostname init-system-helpers iproute2 libacl1 libaio1 libasan5 
libatomic1 libattr1
  libaudit-common libaudit1 libbinutils libblkid1 libbz2-1.0 libc-bin 
libc-dev-bin libc6 libc6-dev
  libcap-ng0 libcap2 libcap2-bin libcc1-0 libcom-err2 libconfig-inifiles-perl 
libdb5.3 libdbi-perl
  libdebconfclient0 libdpkg-perl libelf1 libext2fs2 libfdisk1 libgcrypt20 
libgdbm-compat4 libgdbm6
  libgmp10 libgnutls30 libgomp1 libgpg-error0 libgpm2 libidn2-0 libitm1 
liblsan0 liblz4-1 liblzma5
  libmnl0 libmount1 libmpc3 libmpfr6 libncurses6 libncursesw6 libp11-kit0 
libpam-modules
  libpam-modules-bin libpam-runtime libpam0g libpcre3 libpopt0 libquadmath0 
libseccomp2 libselinux1
  libsemanage-common libsemanage1 libsepol1 libsigc++-2.0-0v5 libsigsegv2 
libsmartcols1 libsnappy1v5
  libsqlite3-0 libss2 libssl1.1 libstdc++6 libsystemd0 libtasn1-6 libtinfo6 
libtsan0 libubsan1
  libudev1 libunistring2 libuuid1 libwrap0 libxapian30 libxtables12 libzstd1 
linux-libc-dev login
  lsb-base lsof make mariadb-common mawk mount mysql-common ncurses-base 
ncurses-bin passwd patch perl
  perl-base psmisc readline-common rsync socat sysvinit-utils tar tzdata 
util-linux vim vim-common
  vim-runtime xxd xz-utils zlib1g
143 upgraded, 39 newly installed, 9 to remove and 0 not upgraded.
Need to get 0 B/125 MB of archives.
After this operation, 22.7 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.
root@isildor:/# apt policy mariadb-server
mariadb-server:
  Installed: 1:10.3.29-0+deb10u1
  Candidate: 1:10.5.12-1
  Version table:
 1:10.5.12-1 500
500 file:/home/tobi/pbuilder_repo/deps ./ Packages
 1:10.5.11-1 500
500 http://ftp.de.debian.org/debian bullseye/main amd64 Packages
 *** 1:10.3.29-0+deb10u1 500
500 http://ftp.de.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status

apt -s -o Debug::pkgProblemResolver=yes dist-upgrade 2>&1 | tee 
/tmp/apt-resolver

(apt-resolver is attachd to this 

Bug#993590: distro-info-data: Store a mapping from distro to gpg keyring

2021-09-03 Thread Johannes Schauer Marin Rodrigues
Package: distro-info-data
Version: 0.51
Severity: normal

Hi,

please consider storing a mapping from distro to keyring in
/usr/share/keyring. Currently there is no reliable way to retrieve the
authoritative keyring for a given distro name. Even when limiting
oneself to only Debian, it is not obvious for which suites one needs
/usr/share/keyrings/debian-archive-keyring.gpg and for which one needs
/usr/share/keyrings/debian-archive-removed-keys.gpg.

Thanks!

cheers, josch



  1   2   >