Bug#944249: [Pkg-emacsen-addons] Bug#944249: gnuplot-mode does not work with emacs26

[Dima Kogan]

OK. I went through all the patches, and pushed a tree to git. Nicholas:
I took most of your stuff, except I don't want to rename the package
again.

I'll move the repo to the emacs team this week, and we can do an upload.
Nicholas: do you want to be an Uploader? And are you an emacs team
member? You can then get rights to write to the repo. And if you want
to, you can prepare the final package that I'll then upload for you.

Bug#945455: RFP: hardened-malloc -- hardened memory allocator

[Patrick Schleizer]

Package: wnpp
Severity: wishlist
X-Debbugs-CC: whonix-de...@whonix.org

* Package name: hardened-malloc
  Version : 2.0
  Upstream Author : Daniel Micay
* URL : https://github.com/GrapheneOS/hardened_malloc
* License : MIT
  Programming Lang: C
  Description : hardened memory allocator
This is a security-focused general purpose memory allocator providing
the malloc API along with various extensions. It provides substantial
hardening against heap corruption vulnerabilities. The security-focused
design also leads to much less metadata overhead and memory waste from
fragmentation than a more traditional allocator design. It aims to
provide decent overall performance with a focus on long-term performance
and memory usage rather than allocator micro-benchmarks. It offers
scalability via a configurable number of entirely independently arenas,
with the internal locking within arenas further divided up per size
class. It can be added as a preloaded library using /etc/ld.so.preload.

Bug#945258: In git for a while now

[Christian Ehrhardt]

Hi,
I saw the grave bump, but the comment still links to the v1 patches.
To make sure it is known - there was a v2:
https://www.mail-archive.com/qemu-block@nongnu.org/msg58098.html
And in the meantime things are accepted:
https://git.qemu.org/?p=qemu.git;a=commit;h=944f3d5dd216fcd8cb007eddd4f82dced0a15b3d
https://git.qemu.org/?p=qemu.git;a=commit;h=5e9785505210e2477e590e61b1ab100d0ec22b01

But OTOH 4.2 with this and much more fixes releases next Tuesday
https://wiki.qemu.org/Planning/4.2

If time doesn't permit a bug fix upload before that, going directly to
4.2 seems to be an option as well.

-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

Bug#936015: marked as done (ceph: CVE-2019-10222)

[Salvatore Bonaccorso]

Hi Bernd!

On Sun, Nov 24, 2019 at 09:17:25PM +0100, Bernd Zeimetz wrote:
> 
> 
> On 11/24/19 8:38 PM, Salvatore Bonaccorso wrote:
> > Hi Bernd,
> > 
> > On Mon, Nov 18, 2019 at 02:45:14PM +, Debian Bug Tracking System wrote:
> > [...]
> >> Version: 14.2.4-1
> >>
> >> Forgot to mention that bug in the changelog unfortunately.
> >>
> >> ceph (14.2.4-1) unstable; urgency=medium
> > 
> > Do you know where this upload got lost? It's not in NEW and it does
> > not appear to be in unstable either.
> 
> yeah, got auto-rejected as it missed some overrides.. (needs rpath to
> find libjvm...).
> 
> and while fixing that I found some issues in debian/copyright... will
> take a few more days unfortunately.

Ack, thanks for the status update!

Regards,
Salvatore

Bug#944819: docker-based tests

[Sébastien Delafond]

Hi Antonio,

the solution currently implemented does indeed test the installed
package: it will install it using
/etc/apt/sources.list.d/autopkgtest.list, and run the entire upstream
test suite against that. You are right that all of this happens in a
docker container.

This is because that all the dependencies and requirements for that test
suite to run are a bit complex, and upstream's solution uses docker for
setting all that up: our initial implementation therefore chose that as
well.

There is however an ongoing effort to rewrite it shell, so as to
directly use the underlying host. Once that effort is complete, disk
usage shouldn't be a problem anymore on the debci workers.

Cheers,

-- 
Seb

Bug#945454: elastix: FTBFS with current opencv and gdcm

[Steve Langasek]

Source: elastix
Version: 4.9.0-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

Dear maintainers,

The elastix package is not buildable in unstable with the current opencv and
gdcm:

[...]
arg [/usr/lib/gcc/x86_64-linux-gnu/9/crtendS.o] ==> ignore
arg [/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/crtn.o] ==> 
ignore
  collapse library dir [/usr/lib/gcc/x86_64-linux-gnu/9] ==> 
[/usr/lib/gcc/x86_64-linux-gnu/9]
  collapse library dir 
[/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu] ==> 
[/usr/lib/x86_64-linux-gnu]
  collapse library dir [/usr/lib/gcc/x86_64-linux-gnu/9/../../../../lib] ==> 
[/usr/lib]
  collapse library dir [/lib/x86_64-linux-gnu] ==> [/lib/x86_64-linux-gnu]
  collapse library dir [/lib/../lib] ==> [/lib]
  collapse library dir [/usr/lib/x86_64-linux-gnu] ==> 
[/usr/lib/x86_64-linux-gnu]
  collapse library dir [/usr/lib/../lib] ==> [/usr/lib]
  collapse library dir [/usr/lib/gcc/x86_64-linux-gnu/9/../../..] ==> [/usr/lib]
  implicit libs: [niftiio;stdc++;m;gcc_s;gcc;c;gcc_s;gcc]
  implicit dirs: 
[/usr/lib/gcc/x86_64-linux-gnu/9;/usr/lib/x86_64-linux-gnu;/usr/lib;/lib/x86_64-linux-gnu;/lib]
  implicit fwks: []


dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=RELEASE -DCMAKE_SKIP_RPATH=ON 
-DSOURCE_DATE_EPOCH=OURCE_DATE_EPOCH -DBUILD_DOCUMENTATION=ON 
-DELASTIX_USE_MEVISDICOMTIFF:BOOL=OFF 
-DUSE_KNNGraphAlphaMutualInformationMetric:BOOL=ON .. returned exit code 1
make[1]: *** [debian/rules:27: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:12: binary] Error 2
[...]

  (https://launchpad.net/ubuntu/+source/elastix/4.9.0-1build1/+build/18156068)

I see nothing in the cmake output that looks like an error to me, up until
the exit code, so I'm not sure what to make of this failure.

Please note that elastix has been removed from testing at some point,
allowing the new opencv + gdcm to transition there, but somehow this never
resulted in an RC bug filed against elastix.

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


signature.asc
Description: PGP signature

Bug#945451: [PATCH 4/4] email-print-mime-structure: Verify Python type annotations

[Daniel Kahn Gillmor]

Signed-off-by: Daniel Kahn Gillmor 
---
 Makefile   | 3 ++-
 debian/control | 1 +
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/Makefile b/Makefile
index de2a784..af30616 100644
--- a/Makefile
+++ b/Makefile
@@ -9,10 +9,11 @@ all: $(MANPAGES) $(COMPLETIONS)
 
 check:
./tests/email-print-mime-structure.sh
+   mypy --strict ./email-print-mime-structure
 
 clean:
rm -f $(MANPAGES)
-   rm -rf completions
+   rm -rf completions .mypy_cache
 
 %.1: %.1.pod
pod2man --section=1 --date="Debian Project" --center="User Commands" \
diff --git a/debian/control b/debian/control
index 0ef1ece..2e96d3e 100644
--- a/debian/control
+++ b/debian/control
@@ -10,6 +10,7 @@ Build-Depends:
  diffutils ,
  gpg ,
  gpg-agent ,
+ mypy ,
  perl,
  python3 ,
  python3-argcomplete,
-- 
2.24.0

Bug#945451: [PATCH 1/4] email-print-mime-structure: simple baseline test suite

[Daniel Kahn Gillmor]

I want to ensure that any changes don't ultimately break the behavior
of email-print-mime-structure.

Signed-off-by: Daniel Kahn Gillmor 
---
 Makefile  |  3 +++
 debian/control|  2 ++
 tests/email-print-mime-structure.sh   |  8 ++
 .../alternative.eml   | 18 +
 .../alternative.out   |  3 +++
 .../email-print-mime-structure/attachment.eml | 26 +++
 .../email-print-mime-structure/attachment.out |  5 
 tests/email-print-mime-structure/simple.eml   |  9 +++
 tests/email-print-mime-structure/simple.out   |  1 +
 9 files changed, 75 insertions(+)
 create mode 100755 tests/email-print-mime-structure.sh
 create mode 100644 tests/email-print-mime-structure/alternative.eml
 create mode 100644 tests/email-print-mime-structure/alternative.out
 create mode 100644 tests/email-print-mime-structure/attachment.eml
 create mode 100644 tests/email-print-mime-structure/attachment.out
 create mode 100644 tests/email-print-mime-structure/simple.eml
 create mode 100644 tests/email-print-mime-structure/simple.out

diff --git a/Makefile b/Makefile
index cd8f592..de2a784 100644
--- a/Makefile
+++ b/Makefile
@@ -7,6 +7,9 @@ COMPLETIONS=completions/bash/email-print-mime-structure
 
 all: $(MANPAGES) $(COMPLETIONS)
 
+check:
+   ./tests/email-print-mime-structure.sh
+
 clean:
rm -f $(MANPAGES)
rm -rf completions
diff --git a/debian/control b/debian/control
index 72b57c3..bf49458 100644
--- a/debian/control
+++ b/debian/control
@@ -7,7 +7,9 @@ Build-Depends:
  bash-completion,
  debhelper (>= 10),
  dh-elpa,
+ diffutils ,
  perl,
+ python3 ,
  python3-argcomplete,
 Vcs-Git: https://git.spwhitton.name/mailscripts
 Vcs-Browser: https://git.spwhitton.name/mailscripts
diff --git a/tests/email-print-mime-structure.sh 
b/tests/email-print-mime-structure.sh
new file mode 100755
index 000..5efa2ca
--- /dev/null
+++ b/tests/email-print-mime-structure.sh
@@ -0,0 +1,8 @@
+#!/bin/bash
+
+set -e
+
+for eml in tests/email-print-mime-structure/*.eml; do
+printf "Testing %s\n" "${eml##*/}"
+diff -u "${eml%%.eml}.out" <(./email-print-mime-structure < "$eml")
+done
diff --git a/tests/email-print-mime-structure/alternative.eml 
b/tests/email-print-mime-structure/alternative.eml
new file mode 100644
index 000..9b7723d
--- /dev/null
+++ b/tests/email-print-mime-structure/alternative.eml
@@ -0,0 +1,18 @@
+Date: Sun, 24 Nov 2019 21:13:45 -0500
+Subject: test message
+Message-ID: 
+From: Alice 
+To: Bob 
+Content-Type: multipart/alternative; boundary="abc123"
+
+--abc123
+Content-Type: text/plain
+
+This is a simple message
+
+--abc123
+Content-Type: text/html
+
+This is a simple message
+
+--abc123--
diff --git a/tests/email-print-mime-structure/alternative.out 
b/tests/email-print-mime-structure/alternative.out
new file mode 100644
index 000..1c0165a
--- /dev/null
+++ b/tests/email-print-mime-structure/alternative.out
@@ -0,0 +1,3 @@
+└┬╴multipart/alternative 414 bytes
+ ├─╴text/plain 26 bytes
+ └─╴text/html 72 bytes
diff --git a/tests/email-print-mime-structure/attachment.eml 
b/tests/email-print-mime-structure/attachment.eml
new file mode 100644
index 000..31baa7c
--- /dev/null
+++ b/tests/email-print-mime-structure/attachment.eml
@@ -0,0 +1,26 @@
+Date: Sun, 24 Nov 2019 21:13:45 -0500
+Subject: test message
+Message-ID: 
+From: Alice 
+To: Bob 
+Content-Type: multipart/mixed; boundary="xyz"
+
+--xyz
+Content-Type: multipart/alternative; boundary="abc123"
+
+--abc123
+Content-Type: text/plain
+
+This is a simple message
+
+--abc123
+Content-Type: text/html
+
+This is a simple message
+
+--abc123--
+--xyz
+Content-Type: text/plain
+Content-Disposition: attachment; filename="test.txt"
+
+This is a simple attachment file.
diff --git a/tests/email-print-mime-structure/attachment.out 
b/tests/email-print-mime-structure/attachment.out
new file mode 100644
index 000..f2ca543
--- /dev/null
+++ b/tests/email-print-mime-structure/attachment.out
@@ -0,0 +1,5 @@
+└┬╴multipart/mixed 594 bytes
+ ├┬╴multipart/alternative 234 bytes
+ │├─╴text/plain 26 bytes
+ │└─╴text/html 72 bytes
+ └─╴text/plain attachment [test.txt] 33 bytes
diff --git a/tests/email-print-mime-structure/simple.eml 
b/tests/email-print-mime-structure/simple.eml
new file mode 100644
index 000..36facec
--- /dev/null
+++ b/tests/email-print-mime-structure/simple.eml
@@ -0,0 +1,9 @@
+Date: Sun, 24 Nov 2019 21:13:45 -0500
+Subject: test message
+Message-ID: 
+From: Alice 
+To: Bob 
+
+This is a simple message
+
+
diff --git a/tests/email-print-mime-structure/simple.out 
b/tests/email-print-mime-structure/simple.out
new file mode 100644
index 000..7ac3514
--- /dev/null
+++ b/tests/email-print-mime-structure/simple.out
@@ -0,0 +1 @@
+└─╴text/plain 30 bytes
-- 
2.24.0

Bug#945451: [PATCH 2/4] email-print-mime-structure: added test for PGP/MIME decryption

[Daniel Kahn Gillmor]

The secret key material in this test comes from
https://datatracker.ietf.org/doc/draft-bre-openpgp-samples/

Signed-off-by: Daniel Kahn Gillmor 
---
 debian/control|  1 +
 tests/email-print-mime-structure.sh   | 17 +++-
 tests/email-print-mime-structure/bob.key  | 82 +++
 .../email-print-mime-structure/encrypted.eml  | 37 +
 .../email-print-mime-structure/encrypted.out  |  9 ++
 .../encrypted.pgpkey  |  1 +
 6 files changed, 145 insertions(+), 2 deletions(-)
 create mode 100644 tests/email-print-mime-structure/bob.key
 create mode 100644 tests/email-print-mime-structure/encrypted.eml
 create mode 100644 tests/email-print-mime-structure/encrypted.out
 create mode 12 tests/email-print-mime-structure/encrypted.pgpkey

diff --git a/debian/control b/debian/control
index bf49458..2576d6c 100644
--- a/debian/control
+++ b/debian/control
@@ -11,6 +11,7 @@ Build-Depends:
  perl,
  python3 ,
  python3-argcomplete,
+ python3-pgpy ,
 Vcs-Git: https://git.spwhitton.name/mailscripts
 Vcs-Browser: https://git.spwhitton.name/mailscripts
 
diff --git a/tests/email-print-mime-structure.sh 
b/tests/email-print-mime-structure.sh
index 5efa2ca..0c0bb50 100755
--- a/tests/email-print-mime-structure.sh
+++ b/tests/email-print-mime-structure.sh
@@ -2,7 +2,20 @@
 
 set -e
 
+test_eml() {
+message="$1"
+shift
+diff -u "$message.out" <(./email-print-mime-structure "$@" < 
"$message.eml")
+}
+
 for eml in tests/email-print-mime-structure/*.eml; do
-printf "Testing %s\n" "${eml##*/}"
-diff -u "${eml%%.eml}.out" <(./email-print-mime-structure < "$eml")
+base="${eml%%.eml}"
+pgpkey="$base.pgpkey"
+if [ -e "$pgpkey" ]; then
+printf "Testing %s (PGPy)\n" "${eml##*/}"
+test_eml "$base" --pgpkey "$pgpkey"
+else
+printf "Testing %s\n" "${eml##*/}"
+test_eml "$base"
+fi
 done
diff --git a/tests/email-print-mime-structure/bob.key 
b/tests/email-print-mime-structure/bob.key
new file mode 100644
index 000..59e981b
--- /dev/null
+++ b/tests/email-print-mime-structure/bob.key
@@ -0,0 +1,82 @@
+-BEGIN PGP PRIVATE KEY BLOCK-
+Comment: Bob's OpenPGP Transferable Secret Key
+
+lQVYBF2lnPIBDAC5cL9PQoQLTMuhjbYvb4Ncuuo0bfmgPRFywX53jPhoFf4Zg6mv
+/seOXpgecTdOcVttfzC8ycIKrt3aQTiwOG/ctaR4Bk/t6ayNFfdUNxHWk4WCKzdz
+/56fW2O0F23qIRd8UUJp5IIlN4RDdRCtdhVQIAuzvp2oVy/LaS2kxQoKvph/5pQ/
+5whqsyroEWDJoSV0yOb25B/iwk/pLUFoyhDG9bj0kIzDxrEqW+7Ba8nocQlecMF3
+X5KMN5kp2zraLv9dlBBpWW43XktjcCZgMy20SouraVma8Je/ECwUWYUiAZxLIlMv
+9CurEOtxUw6N3RdOtLmYZS9uEnn5y1UkF88o8Nku890uk6BrewFzJyLAx5wRZ4F0
+qV/yq36UWQ0JB/AUGhHVPdFf6pl6eaxBwT5GXvbBUibtf8YI2og5RsgTWtXfU7eb
+SGXrl5ZMpbA6mbfhd0R8aPxWfmDWiIOhBufhMCvUHh1sApMKVZnvIff9/0Dca3wb
+vLIwa3T4CyshfT0AEQEAAQAL/RZqbJW2IqQDCnJi4Ozm++gPqBPiX1RhTWSjwxfM
+cJKUZfzLj414rMKm6Jh1cwwGY9jekROhB9WmwaaKT8HtcIgrZNAlYzANGRCM4TLK
+3VskxfSwKKna8l+s+mZglqbAjUg3wmFuf9Tj2xcUZYmyRm1DEmcN2ZzpvRtHgX7z
+Wn1mAKUlSDJZSQks0zjuMNbupcpyJokdlkUg2+wBznBOTKzgMxVNC9b2g5/tMPUs
+hGGWmF1UH+7AHMTaS6dlmr2ZBIyogdnfUqdNg5sZwsxSNrbglKP4sqe7X61uEAIQ
+bD7rT3LonLbhkrj3I8wilUD8usIwt5IecoHhd9HziqZjRCc1BUBkboUEoyedbDV4
+i4qfsFZ6CEWoLuD5pW7dEp0M+WeuHXO164Rc+LnH6i1VQrpb1Okl4qO6ejIpIjBI
+1t3GshtUu/mwGBBxs60KBX5g77mFQ9lLCRj8lSYqOsHRKBhUp4qM869VA+fD0BRP
+fqPT0I9IH4Oa/A3jYJcg622GwQYA1LhnP208Waf6PkQSJ6kyr8ymY1yVh9VBE/g6
+fRDYA+pkqKnw9wfH2Qho3ysAA+OmVOX8Hldg+Pc0Zs0e5pCavb0En8iFLvTA0Q2E
+LR5rLue9uD7aFuKFU/VdcddY9Ww/vo4k5p/tVGp7F8RYCFn9rSjIWbfvvZi1q5Tx
++akoZbga+4qQ4WYzB/obdX6SCmi6BndcQ1QdjCCQU6gpYx0MddVERbIp9+2SXDyL
+hpxjSyz+RGsZi/9UAshT4txP4+MZBgDfK3ZqtW+h2/eMRxkANqOJpxSjMyLO/FXN
+WxzTDYeWtHNYiAlOwlQZEPOydZFty9IVzzNFQCIUCGjQ/nNyhw7adSgUk3+BXEx/
+MyJPYY0BYuhLxLYcrfQ9nrhaVKxRJj25SVHj2ASsiwGJRZW4CC3uw40OYxfKEvNC
+mer/VxM3kg8qqGf9KUzJ1dVdAvjyx2Hz6jY2qWCyRQ6IMjWHyd43C4r3jxooYKUC
+YnstRQyb/gCSKahveSEjo07CiXMr88UGALwzEr3npFAsPW3osGaFLj49y1oRe11E
+he9gCHFm+fuzbXrWmdPjYU5/ZdqdojzDqfu4ThfnipknpVUM1o6MQqkjM896FHm8
+zbKVFSMhEP6DPHSCexMFrrSgN03PdwHTO6iBaIBBFqmGY01tmJ03SxvSpiBPON9P
+NVvy/6UZFedTq8A07OUAxO62YUSNtT5pmK2vzs3SAZJmbFbMh+NN204TRI72GlqT
+t5hcfkuv8hrmwPS/ZR6q312mKQ6w/1pqO9qitCFCb2IgQmFiYmFnZSA8Ym9iQG9w
+ZW5wZ3AuZXhhbXBsZT6JAc4EEwEKADgCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgEC
+F4AWIQTRpm4aI7GCyZgPeIz7/MgqAV5zMAUCXaWe+gAKCRD7/MgqAV5zMG9sC/9U
+2T3RrqEbw533FPNfEflhEVRIZ8gDXKM8hU6cqqEzCmzZT6xYTe6sv4y+PJBGXJFX
+yhj0g6FDkSyboM5litOcTupURObVqMgA/Y4UKERznm4fzzH9qek85c4ljtLyNufe
+doL2pp3vkGtn7eD0QFRaLLmnxPKQ/TlZKdLE1G3u8Uot8QHicaR6GnAdc5UXQJE3
+BiV7jZuDyWmZ1cUNwJkKL6oRtp+ZNDOQCrLNLecKHcgCqrpjSQG5oouba1I1Q6Vl
+sP44dhA1nkmLHtxlTOzpeHj4jnk1FaXmyasurrrI5CgU/L2Oi39DGKTH/A/cywDN
+4ZplIQ9zR8enkbXquUZvFDe+Xz+6xRXtb5MwQyWODB3nHw85HocLwRoIN9WdQEI+
+L8a/56AuOwhs8llkSuiITjR7r9SgKJC2WlAHl7E8lhJ3VDW3ELC56KH308d6mwOG
+ZRAqIAKzM1T5FGjMBhq7ZV0eqdEntBh3EcOIfj2M8rg1MzJv+0mHZOIjByawikad
+BVgEXaWc8gEMANYwv1xsYyunXYK0X1vY/rP1NNPvhLyLIE7NpK90YNBj+xS1ldGD
+bUdZqZeef2xJe8gMQg05DoD1DF3GipZ0Ies65beh+d5hegb7N4pzh0LzrBrVNHar

Bug#945451: [PATCH 3/4] email-print-mime-structure: Add test for --use-gpg-agent as well

[Daniel Kahn Gillmor]

Signed-off-by: Daniel Kahn Gillmor 
---
 debian/control  | 2 ++
 tests/email-print-mime-structure.sh | 6 ++
 2 files changed, 8 insertions(+)

diff --git a/debian/control b/debian/control
index 2576d6c..0ef1ece 100644
--- a/debian/control
+++ b/debian/control
@@ -8,6 +8,8 @@ Build-Depends:
  debhelper (>= 10),
  dh-elpa,
  diffutils ,
+ gpg ,
+ gpg-agent ,
  perl,
  python3 ,
  python3-argcomplete,
diff --git a/tests/email-print-mime-structure.sh 
b/tests/email-print-mime-structure.sh
index 0c0bb50..d3d8b0c 100755
--- a/tests/email-print-mime-structure.sh
+++ b/tests/email-print-mime-structure.sh
@@ -14,6 +14,12 @@ for eml in tests/email-print-mime-structure/*.eml; do
 if [ -e "$pgpkey" ]; then
 printf "Testing %s (PGPy)\n" "${eml##*/}"
 test_eml "$base" --pgpkey "$pgpkey"
+
+testgpghome=$(mktemp -d)
+printf "Testing %s (GnuPG)\n" "${eml##*/}"
+gpg --homedir="$testgpghome" --batch --quiet --import < "$pgpkey"
+GNUPGHOME="$testgpghome" test_eml "$base" --use-gpg-agent
+rm -rf "$testgpghome"
 else
 printf "Testing %s\n" "${eml##*/}"
 test_eml "$base"
-- 
2.24.0

Bug#929272: nmap-common: executable distributed in nmap-common detected as malware

[Gordon Fyodor Lyon]

Hi Kim-Alexander.  On behalf of the Nmap Project, I just wanted to say
thanks for submitting the false positive file to all the AV vendors.  That
really helps.

-Fyodor

Bug#945453: camitk: FTBFS, uninstallable build-deps in unstable

[Steve Langasek]

Source: camitk
Version: 4.1.2-3
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

Dear maintainers,

The camitk package is not buildable in unstable because it build-depends on
libgdcm2-dev and libvtkgdcm2-dev, which have been superseded by libgdcm-dev
and libvtkgdcm-dev.

After updating the build-dependencies, camitk still fails to build with an
error:

[...]
Determining if the CXX compiler accepts the flag -fPIC passed with the following
 output:
Change Dir: /<>/camitk-build/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/make cmTC_14e9e/fast && make[2]: Entering 
directory '/<>/camitk-build/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_14e9e.dir/build.make 
CMakeFiles/cmTC_14e9e.dir/build
make[3]: Entering directory '/<>/camitk-build/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_14e9e.dir/DummyCXXFile.cxx.o
/usr/bin/c++-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -fPIC   -o CMakeFiles/cmTC_14e9e.dir/DummyCXXFile.cxx.o -c 
/usr/share/cmake-3.15/Modules/DummyCXXFile.cxx
Linking CXX executable cmTC_14e9e
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_14e9e.dir/link.txt 
--verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -fPIC  -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed  -rdynamic CMakeFiles/cmTC_14e9e.dir/DummyCXXFile.cxx.o  -o 
cmTC_14e9e 
make[3]: Leaving directory '/<>/camitk-build/CMakeFiles/CMakeTmp'



dh_auto_configure: cd camitk-build && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_SKIP_RPATH:BOOL=TRUE 
-DCMAKE_INSTALL_RPATH_USE_LINK_PATH:BOOL=FALSE -DCMAKE_BUILD_TYPE:STRING=None 
-DCEP_IMAGING:BOOL=TRUE -DCEP_MODELING:BOOL=TRUE -DCEP_TUTORIALS:BOOL=TRUE 
-DAPIDOC_SDK:BOOL=TRUE .. returned exit code 1
make[1]: *** [debian/rules:66: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:63: build] Error 2

  (https://launchpad.net/ubuntu/+source/camitk/4.1.2-3ubuntu1/+build/18156646)

The build system output here is fairly inscrutable, I'm not clear on what is
actually failing.

In any case, camitk has been removed from testing at some point, allowing
the new opencv + gdcm to transition there, but somehow this never resulted
in an RC bug filed against camitk.

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


signature.asc
Description: PGP signature

Bug#945452: dh-make: use `python3 -m sphinx` instead of `sphinx3-build`

[Sandro Tosi]

Package: dh-make
Version: 2.201903
Severity: normal

Hello,
the preferred way to invoke sphinx is:

  python3 -m sphinx

please replace `sphinx3-build` in the template with that command.

thanks!

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

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

Versions of packages dh-make depends on:
ii  debhelper  12.3
ii  dpkg-dev   1.19.7
ii  make   4.2.1-1.2
ii  python33.7.5-3

dh-make recommends no packages.

Versions of packages dh-make suggests:
ii  build-essential  12.6

-- no debconf information

Bug#944851: tnef: CVE-2019-18849

[Utkarsh Gupta]

Hi all,

On Sat, 16 Nov 2019 11:57:19 +0100 Salvatore Bonaccorso
 wrote:
> Source: tnef
> Version: 1.4.12-1.2
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> Forwarded: https://github.com/verdammelt/tnef/pull/40
>
> Hi,
>
> The following vulnerability was published for tnef.
>
> CVE-2019-18849[0]:
> | In tnef before 1.4.18, an attacker may be able to write to the
> | victim's .ssh/authorized_keys file via an e-mail message with a
> | crafted winmail.dat application/ms-tnef attachment, because of a heap-
> | based buffer over-read involving strdup.

Whilst doing my LTS work, I fixed this for Jessie.
Therefore, attaching a patch to fix this for Stretch, Buster, Bullseye,
and Sid (since they're all at same version).
Thus also CCing the Security team (if that's okay, we could perhaps
upload the fix at the earliest :)).

Hope this helps and gets this fixed asap :)


Best,
Utkarsh
Description: This patch fixes CVE-2019-18849.
 Fix strdup() on possibly unterminated string.
Author: Paul Dreik
Author: Utkarsh Gupta 
Origin: https://github.com/verdammelt/tnef/pull/40
Bug-Debian: https://bugs.debian.org/944851
Last-Update: 2019-11-25

--- a/src/alloc.c
+++ b/src/alloc.c
@@ -72,13 +72,14 @@
 
 /* attempts to malloc memory, if fails print error and call abort */
 void*
-xmalloc (size_t num, size_t size)
+xmalloc (size_t num, size_t size, size_t extra)
 {
 size_t res;
 if (check_mul_overflow(num, size, ))
 abort();
-
-void *ptr = malloc (res);
+if (res + extra < res)
+abort();
+void *ptr = malloc (res + extra);
 if (!ptr
 && (size != 0)) /* some libc don't like size == 0 */
 {
@@ -90,41 +91,44 @@
 
 /* Allocates memory but only up to a limit */
 void*
-checked_xmalloc (size_t num, size_t size)
+checked_xmalloc (size_t num, size_t size, size_t extra)
 {
 size_t res;
 if (check_mul_overflow(num, size, ))
 abort();
-
+if (res + extra < res)
+abort();
 alloc_limit_assert ("checked_xmalloc", res);
-return xmalloc (num, size);
+return xmalloc (num, size, extra);
 }
 
 /* xmallocs memory and clears it out */
 void*
-xcalloc (size_t num, size_t size)
+xcalloc (size_t num, size_t size, size_t extra)
 {
 size_t res;
 if (check_mul_overflow(num, size, ))
 abort();
 
 void *ptr;
-ptr = malloc(res);
+if (res + extra < res)
+abort();
+ptr = malloc(res + extra);
 if (ptr)
 {
-memset (ptr, '\0', (res));
+memset (ptr, '\0', (res + extra));
 }
 return ptr;
 }
 
 /* xcallocs memory but only up to a limit */
 void*
-checked_xcalloc (size_t num, size_t size)
+checked_xcalloc (size_t num, size_t size, size_t extra)
 {
 size_t res;
 if (check_mul_overflow(num, size, ))
 abort();
 
 alloc_limit_assert ("checked_xcalloc", (res));
-return xcalloc (num, size);
+return xcalloc (num, size, extra);
 }
--- a/src/alloc.h
+++ b/src/alloc.h
@@ -35,19 +35,23 @@
 extern void set_alloc_limit (size_t size);
 extern size_t get_alloc_limit();
 extern void alloc_limit_assert (char *fn_name, size_t size);
-extern void* checked_xmalloc (size_t num, size_t size);
-extern void* xmalloc (size_t num, size_t size);
-extern void* checked_xcalloc (size_t num, size_t size);
-extern void* xcalloc (size_t num, size_t size);
+extern void* checked_xmalloc (size_t num, size_t size, size_t extra);
+extern void* xmalloc (size_t num, size_t size, size_t extra);
+extern void* checked_xcalloc (size_t num, size_t size, size_t extra);
+extern void* xcalloc (size_t num, size_t size, size_t extra);
 
 #define XMALLOC(_type,_num)			\
-((_type*)xmalloc((_num), sizeof(_type)))
+  ((_type*)xmalloc((_num), sizeof(_type), 0))
 #define XCALLOC(_type,_num) \
-((_type*)xcalloc((_num), sizeof (_type)))
+  ((_type*)xcalloc((_num), sizeof (_type), 0))
 #define CHECKED_XMALLOC(_type,_num) 			\
-((_type*)checked_xmalloc((_num),sizeof(_type)))
-#define CHECKED_XCALLOC(_type,_num) 			\
-((_type*)checked_xcalloc((_num),sizeof(_type)))
+  ((_type*)checked_xmalloc((_num),sizeof(_type),0))
+#define CHECKED_XMALLOC_ADDNULL(_type,_num) \
+  ((_type*)checked_xmalloc((_num),sizeof(_type),1))
+#define CHECKED_XCALLOC(_type,_num) \
+  ((_type*)checked_xcalloc((_num),sizeof(_type),0))
+#define CHECKED_XCALLOC_ADDNULL(_type,_num) \
+  ((_type*)checked_xcalloc((_num),sizeof(_type),1))
 #define XFREE(_ptr)		\
 do { if (_ptr) { free (_ptr); _ptr = 0; } } while (0)
 
--- a/src/attr.c
+++ b/src/attr.c
@@ -244,7 +244,11 @@
 attr->type = (type_and_name >> 16);
 attr->name = ((type_and_name << 16) >> 16);
 attr->len = geti32(in);
-attr->buf = CHECKED_XCALLOC (unsigned char, attr->len);
+/* Allocate an extra byte for the null terminator,
+   in case the input lacks it,
+   this avoids strdup() being invoked on possibly non-terminated
+   

Bug#945441: Info received (Bug#945441: Acknowledgement (isc-dhcp-client: dhclient fails to obtain address or routes, apparently because of mangled section in dhclient.leases))

[Michael Redman]

Hi Team,

Seeing that the "enx..." interface name was truncated and concatenated 
with "lease {" in the bad block in dhclient.leases, makes me wonder if 
the length of the interface name is relevant to the issue. The full name 
of that interface is "enx0015ff038700".


Kind regards,

Michael Redman

On 11/24/19 10:09 PM, Debian Bug Tracking System wrote:

Thank you for the additional information you have supplied regarding
this Bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
  Debian ISC DHCP Maintainers 

If you wish to submit further information on this problem, please
send it to 945...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

Bug#945451: email-print-mime-structure: add test suite

[Daniel Kahn Gillmor]

Package: mailscripts
Version: 0.15-1
Control: tags -1 patch

There are currently no test suites in mailscripts for anything.

I want to have at least a baseline test suite for
email-print-mime-structure, so that i can be sure that any changes or
refactoring i make don't break the expected output.

I have a short series of patches coming that will provide such a thing.

  --dkg


signature.asc
Description: PGP signature

Bug#944363: Please upgrade to version 1.49

[Robert Ancell]

Hi Laurent,

Sorry, I don't have upload rights, so I've just been updating the git repo.
If you are able to upload please do!

On Mon, Nov 11, 2019 at 12:26 AM Laurent Bigonville 
wrote:

> Hello Robert,
>
> On Fri, 08 Nov 2019 16:25:24 +0100 Laurent Bigonville 
> wrote:
>
> >
> > Hi,
> >
> > Could someone update snapd-glib to >= 1.49?
> >
>
> > This is blocking the upload of gnome-software in unstable
>
> I see that you were the last one to push a change in the git repository
> of snapd-glib, are there any hopes you could upload that to unstable?
>
> I can do it if you want,
>
> >
> > Kind regards,
> >
> > Laurent Bigonville
>
>

Bug#945450: python-urllib3: FTBFS under C locale

[Andreas Beckmann]

Source: python-urllib3
Version: 1.25.6-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

python-urllib3/experimental FTBFS under LC_ALL=C (which is set by
pbuilder) due to a failing test. It works if e.g. LC_ALL=C.UTF-8 is
exported from debian/rules.

=== FAILURES ===
__ TestResponse.test_io_textiowrapper __

self = 

def test_io_textiowrapper(self):
fp = BytesIO(b"\xc3\xa4\xc3\xb6\xc3\xbc\xc3\x9f")
resp = HTTPResponse(fp, preload_content=False)
br = TextIOWrapper(resp, encoding="utf8")

assert br.read() == u"äöüß"

br.close()
assert resp.closed

# HTTPResponse.read() by default closes the response
# https://github.com/urllib3/urllib3/issues/1305
fp = BytesIO(

b"\xc3\xa4\xc3\xb6\xc3\xbc\xc3\x9f\n\xce\xb1\xce\xb2\xce\xb3\xce\xb4"
)
resp = HTTPResponse(fp, preload_content=False)
with pytest.raises(ValueError) as ctx:
if six.PY2:
# py2's implementation of TextIOWrapper requires `read1`
# method which is provided by `BufferedReader` wrapper
resp = BufferedReader(resp)
list(TextIOWrapper(resp))
>   assert str(ctx.value) == "I/O operation on closed file."
E   assert "'ascii' code...in range(128)" == 'I/O operation on closed file.'
E - 'ascii' codec can't decode byte 0xc3 in position 0: ordinal not in 
range(128)
E + I/O operation on closed file.

test/test_response.py:416: AssertionError
 1 failed, 466 passed, 8 skipped, 1 deselected in 12.46 seconds 


Andreas

Bug#945449: ITP: sphinx-copybutton -- sphinx extension to add a "copy" button to code blocks.

[Sandro Tosi]

Package: wnpp
Severity: wishlist
Owner: Sandro Tosi 

* Package name: sphinx-copybutton
  Version : 0.2.5
  Upstream Author : Chris Holdgraf
* URL : https://github.com/choldgraf/sphinx-copybutton
* License : MIT
  Programming Lang: Python
  Description : sphinx extension to add a "copy" button to code blocks.

new build-dep of matplotlib

Bug#945055: intel-microcode: CPU runs at considerably higher temperatures

[Christoph Anton Mitterer]

On Sat, 2019-11-23 at 22:36 -0300, Henrique de Moraes Holschuh wrote:
> To make sure of that, we need to ensure the mitigations are enabled
> in the 5.2 kernel you are using.
> 
> Please send the output of the grep line:
> grep . /sys/devices/system/cpu/vulnerabilities/*
/sys/devices/system/cpu/vulnerabilities/l1tf:Mitigation: PTE Inversion; VMX: 
conditional cache flushes, SMT vulnerable
/sys/devices/system/cpu/vulnerabilities/mds:Mitigation: Clear CPU buffers; SMT 
vulnerable
/sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
/sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation: 
Speculative Store Bypass disabled via prctl and seccomp
/sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: usercopy/swapgs 
barriers and __user pointer sanitization
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full generic 
retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling


during:

> With the 5.2 kernel in the new microcode (20191115).

root@heisenberg:~# uname -a
Linux heisenberg 5.2.0-3-amd64 #1 SMP Debian 5.2.17-1 (2019-10-06) x86_64 
GNU/Linux
root@heisenberg:~# dmesg | head -n1
[0.00] microcode: microcode updated early to revision 0xca, date = 
2019-09-26

(which I think is the one from 20191115, right?

Cheers,
Chris.

Bug#944350: systemd: screen remains off after waking up from suspend

[Jiri Kanicky]

Further to the issue, when I set BIOS to discrete graphics only, I am 
experiencing the same issue when booting the system from shutdown state. 
The screen stays off, but the OS is booted and working.

Bug#945448: hostapd: bpo update fails to set service properly

[westlake]

Package: hostapd
Version: 2:2.4-1+deb9u4
Severity: important

using kernel 4.16.0-0.bpo.2-686-pae, the hostapd update to 
2:2.7+git20190128+0c1e29f-4~bpo9+2  causes wlan0 to no longer work


reverting back to 2:2.4-1+deb9u4 , allowed hostapd to run again correctly

/etc/network/interfaces
"auto wlan0
iface wlan0 inet static
 hostapd /etc/hostapd/hostapd.conf
 address 10.9.9.1
 netmask 255.255.255.0
 broadcast 10.9.9.255
"

fwiw, the module the wireless chipset is using is ath5k

observation:
- ifconfig lists wlan0
- A client scanning the AP will see it appear for a couple of seconds 
before it disappears, even though ifconfig still says that wlan0 is 
still up.


the issue is replicated for each of these release, tested multiple times 
and the result is the same for hostapd never working correctly with 
2:2.7+git20190128+0c1e29f-4~bpo9+2.

Bug#944806: gnome fails to start after gnome-shell upgrade, gnome-classic will start

[Wendy J. Elmer]

I see this line in the Xorg log when gnome fails to start and not with the 
downgraded packages and gnome starts.

(EE) modeset(0): failed to set mode: Permission denied

Does that have anything to do with why gnome fails to start?

Bug#942795: Acknowledgement (libsoxr: Building with "nocheck" results in a broken soxr.pc pkg-config file)

[John Paul Adrian Glaubitz]

Hi!

Could this bug get fixed soonish? We still can't build VLC on the affected
architectures because of this particular bug.

In my tests, removing the paragraph worked perfectly fine and still made
"nocheck" work.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#944150: 389-ds-base: CVE-2019-14824: Read permission check bypass via the deref plugin

[Utkarsh Gupta]

Hi Timo,

On Tue, 05 Nov 2019 07:22:06 +0100 Salvatore Bonaccorso
 wrote:
> Source: 389-ds-base
> Version: 1.4.1.6-4
> Severity: grave
> Tags: security upstream
>
> Hi,
>
> The following vulnerability was published for 389-ds-base.
>
> CVE-2019-14824[0]:
> Read permission check bypass via the deref plugin

As a part of my LTS work, I have fixed this in Jessie (upload remaining)
so attaching a patch for Buster, Bullseye, and Sid. Hope you might be
interested in the same :)

Also, while at it, this patch also works for Stretch (just a quilt
refresh) would be required :)
Requesting you to fix the same at the earliest.


Best,
Utkarsh
Description: Add patch to fix CVE-2019-14824.
 For deref plugin we are only concerned with "read" access, not
 "search" access.  Removed the SLAPI_ACL_SEARCH right flag when
 checking access for an attribute.
Author: Mark Reynolds
Author: Utkarsh Gupta 
Origin: https://pagure.io/389-ds-base/c/fca293427
Bug: https://pagure.io/389-ds-base/issue/50716
Bug-Debian: https://bugs.debian.org/944150
Last-Update: 2019-11-24

--- a/ldap/servers/plugins/deref/deref.c
+++ b/ldap/servers/plugins/deref/deref.c
@@ -573,7 +573,7 @@
 Slapi_Entry **entries = NULL;
 int rc;
 
-/*  If the access check on the attributes is done without retrieveing the entry
+/*  If the access check on the attributes is done without retrieving the entry
  *  it cannot handle acis which need teh entry, eg to apply a targetfilter rule
  *  So the determination of attrs which can be dereferenced is delayed
  */
@@ -596,7 +596,7 @@
 int ii;
 int needattrvals = 1; /* need attrvals sequence? */
 if (deref_check_access(pb, entries[0], derefdn, attrs, ,
-   (SLAPI_ACL_SEARCH | SLAPI_ACL_READ))) {
+   SLAPI_ACL_READ)) {
 slapi_log_err(SLAPI_LOG_PLUGIN, DEREF_PLUGIN_SUBSYSTEM,
   "deref_do_deref_attr - The client does not have permission to read the requested "
   "attributes in entry %s\n",
@@ -714,7 +714,7 @@
 attrs[1] = NULL;
 
 if (deref_check_access(pb, ent, NULL, attrs, ,
-   (SLAPI_ACL_SEARCH | SLAPI_ACL_READ))) {
+   SLAPI_ACL_READ)) {
 slapi_log_err(SLAPI_LOG_PLUGIN, DEREF_PLUGIN_SUBSYSTEM,
   "deref_pre_entry - The client does not have permission to read attribute %s in entry %s\n",
   spec->derefattr, slapi_entry_get_dn_const(ent));


signature.asc
Description: OpenPGP digital signature

Bug#945447: RFS: emacs-websocket/1.12+1.g74e4b82-1 [ITP] -- Emacs WebSocket client and server

[Nicholas D Steeves]

Package: sponsorship-requests
Severity: wishlist
Control: block 945329 by -1

Dear mentors,

I am looking for a sponsor for my package "emacs-websocket", which is
a required dependency of atomic-chrome-el (Bug #909336).

 * Package name: emacs-websocket
   Version : 1.12+1.g74e4b82-1
   Upstream Author : Andrew Hyatt 
 * URL : https://github.com/ahyatt/emacs-websocket
 * License : GPL-2+
 * Vcs : https://salsa.debian.org/emacsen-team/emacs-websocket
   Section : lisp

It builds this binary package:

  elpa-websocket - Emacs WebSocket client and server

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

  https://mentors.debian.net/package/emacs-websocket

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

  dget -x 
https://mentors.debian.net/debian/pool/main/e/emacs-websocket/emacs-websocket_1.12+1.g74e4b82-1.dsc

Alternatively clone the repo and get upstream source from tag using
gbp, or generate an orig tarball for other build systems:

  git clone g...@salsa.debian.org:emacsen-team/emacs-websocket.git
  cd emacs-websocket
  # optionally -> git deborig

Regards,
Nicholas

Bug#945446: efl: FTBFS on most architectures in experimental

[Andreas Beckmann]

Source: efl
Version: 1.23.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

efl/experimental FTBFS on most architectures while the version in sid
builds fine:

https://buildd.debian.org/status/package.php?p=efl=experimental

There are usually some failing tests.


Andreas

Bug#945445: lldb-8: incorrect python path output by "lldb-8 -P"

[Ximin Luo]

Package: lldb-8
Version: 1:8.0.1-4
Severity: normal

Dear Maintainer,

lldb -P is supposed to print the path to the python lldb module. This does not 
work
in Debian, the path was not overridden correctly in the packaging:

$ lldb-8 -P
/usr/lib/x86_64-linux-gnu/python3.7/site-packages
$ ls -la $(lldb-8 -P)
ls: cannot access '/usr/lib/x86_64-linux-gnu/python3.7/site-packages': No such 
file or directory
exit code 2
$ dpkg -L python3-lldb-8
[..]
/usr/lib/llvm-8/lib/python3.7/site-packages/lldb
[..]

The fix is to override "lldb-8 -P" so it outputs 
/usr/lib/llvm-8/lib/python3.7/site-packages

This will make it easier to package rust-lldb as well.

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

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

Versions of packages lldb-8 depends on:
ii  libc6  2.29-3
ii  libedit2   3.1-20191025-1
ii  libgcc11:9.2.1-19
ii  liblldb-8  1:8.0.1-4
ii  libllvm8   1:8.0.1-4
ii  libncurses66.1+20191019-1
ii  libpython3.7   3.7.5-2
ii  libstdc++6 9.2.1-19
ii  libtinfo6  6.1+20191019-1
ii  llvm-8-dev 1:8.0.1-4
ii  python-lldb-8  1:8.0.1-3+b1

lldb-8 recommends no packages.

lldb-8 suggests no packages.

-- no debconf information

Bug#942538: [Python-modules-team] Bug#936745: reducing matplotlib2 build-depends.

[Sandro Tosi]

> matplotlib2 still has python-qt4 and python-qt4-dbg in autopkgtest depends

arghhh sorry, just uploaded with that removed

> (and matplotlib too, even though it is Python 3 only).

will look at this later, in the coming days

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#945444: apt: Man page for apt-helper missing

[James Blanford]

Package: apt
Version: 1.8.2
Severity: normal

Dear Maintainer,

   * What led up to the situation?

I noticed that my system was trying to run apt-helper on a daily
basis and wanted to know what apt-helper does and peruse descriptions of
command line switches and options.

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

I typed "man apt-helper" in a bash terminal. I also looked in the man
page for apt.

   * What was the outcome of this action?

I received the message "No manual entry for apt-helper"

   * What outcome did you expect instead?

I expected the appropriate man page to be opened.

-- Package-specific info:

-- (no /etc/apt/preferences present) --


-- (/etc/apt/preferences.d/stable.pref present, but not submitted) --


-- /etc/apt/preferences.d/testing.pref --

Package: *
Pin: release a=testing
Pin-Priority: 795

-- (/etc/apt/sources.list present, but not submitted) --


-- (no /etc/apt/sources.list.d/* present) --


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

Kernel: Linux 4.19.85 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE=en_US 
(charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages apt depends on:
ii  adduser 3.118
ii  debian-archive-keyring  2019.1
ii  gpgv2.2.12-1+deb10u1
ii  libapt-pkg5.0   1.8.2
ii  libc6   2.28-10
ii  libgcc1 1:8.3.0-6
ii  libgnutls30 3.6.7-4
ii  libseccomp2 2.3.3-4
ii  libstdc++6  8.3.0-6

Versions of packages apt recommends:
ii  ca-certificates  20190110

Versions of packages apt suggests:
pn  apt-doc 
ii  aptitude0.8.11-7
ii  dpkg-dev1.19.7
ii  gnupg   2.2.12-1+deb10u1
ii  gnupg2  2.2.12-1+deb10u1
pn  powermgmt-base  

-- Configuration Files:
/etc/logrotate.d/apt changed [not included]

-- no debconf information

Bug#917613: Regression: Thunderbird dosen't open ("already running" error)

[H. Buchberger]

Hi there,

same problem here: After upgrading from Debian 9 (Stretch) to 10 
(Buster) Thunderbird stopped working.
Thanks to this bugreport I disabled the apparmor-profile "thunderbird" 
and thunderbird was running again as before.
When I tried to set the apparmor-profile to "complain", aa-complain gave 
the following error:


ERROR: /etc/apparmor.d/usr.bin.thunderbird doesn't contain a valid 
profile for /usr/bin/thunderbird (syntax error?)


Disabling the profile (see Philipp's post) worked without problems.

Regards
  Hansjörg


On Wed, 11 Sep 2019 09:18:23 +0200 Philipp Pilhofer 
 wrote:

Am 02.01.19 um 09:39 schrieb Carsten Schoenert:
>> The only things I don't understand, how was AppArmor enabled, and how 
>> was it working for years until the last update of kernel/TB/whatever; I 
>> have symlinked home dir for long time now... Could be that only the last 
>> TB update enabled it?
> 
> very very unlikely. We are in the middle of an ESR release and thus the

> packaging typically itself isn't changing much.
> The code responsible for this wasn't touched for over year now. But we
> won't get new information on this what really did happen on your system.
> Only if it is reproducible we would see if and were something is maybe
> broken and not correctly working.
> 


After updating from stretch to buster, I did have exactly that problem. After 
longer testing I found
it's apparmor. I never used apparmor at all or activated anything, so I don't 
know how this happened.

Switching off the profile as described here 
(https://help.ubuntu.com/community/AppArmor) made it
work again. Is this the way to go or is there anything else I have to take care 
of?


Thank you very much,
Philipp

Bug#945443: git-svn fails with "error: git-svn died of signal 11"

[christian_k...@gmx.net]

Package:    gtk-svn
Version:    1:2.20.1-2


When I call git svn fetch, git-svn returns an error message after operation

error: git-svn died of signal 11


Here is the transcript:

$ git svn fetch
org.kde.kwindowsystem: Could not find any platform plugin
error: git-svn died of signal 11
$


Best regards,
Christian

Bug#939951: keybinder, keybinder-3.0, kylin-burner: fails to build with gtk-doc 1.32

[Simon McVittie]

Control: tags -1 + upstream

On Tue, 10 Sep 2019 at 14:49:12 +0200, Andreas Henriksson wrote:
> Your package seems to fail to build from source with the new gtk-doc-tools 
> 1.32 (currently in experimental).
> The issue seems to be that your sgml files include a file that's no longer 
> being generated when there's no content to put in it.

Library maintainers can either solve this class of bug by not
attempting to include the object tree at all, which for example is
appropriate if the library does not include any GObject subclasses:
https://gitlab.freedesktop.org/gstreamer/gst-libav/merge_requests/40

or by adding an empty  inside the  element
for ../xml/tree_index.sgml (meaning "if you can't, substitute the empty
string instead") to return to the previous behaviour, which would look
something like this  in GTK's documentation:

  
Index of new symbols in 3.24

  

Please check whether the upstream project has already fixed this, and send
a patch upstream if not. This will affect any build with a new gtk-doc
version: not just Debian, but also any recently-updated distribution.

Regards,
smcv

Bug#939950: hkl: fails to build with gtk-doc 1.32

[Simon McVittie]

On Tue, 10 Sep 2019 at 14:49:05 +0200, Andreas Henriksson wrote:
> Your package seems to fail to build from source with the new gtk-doc-tools 
> 1.32 (currently in experimental).
> The issue seems to be that your sgml files include a file that's no longer 
> being generated when there's no content to put in it.

Library maintainers can either solve this class of bug by not
attempting to include the object tree at all, which for example is
appropriate if the library does not include any GObject subclasses:
https://gitlab.freedesktop.org/gstreamer/gst-libav/merge_requests/40

or by adding an empty  inside the  element
for ../xml/tree_index.sgml (meaning "if you can't, substitute the empty
string instead") to return to the previous behaviour, which would look
something like this  in GTK's documentation:

  
Index of new symbols in 3.24

  

Regards,
smcv

Bug#867341: Bug#939846: xymon: xymonnet segfaults (and completely stops working) if any URL to check is IPv6-only

[nicolas]

Hi Axel,

I re-read the bug description and realized i was using an ipv6 with conn
test (and not conn6)
so, the 2 bugs seem to be the same issue or at least related.

Regards,
Nicolas


On Mon, 9 Sep 2019 15:28:58 +0200 Axel Beckert wrote:
> Control: found 939846 4.3.30-1
>
> Hi,
>
> I wrote in #939846:
> > And since it seems to get this response
> > inbetween parsing hosts.cfg and conducting any tests, a single URL in
> > hosts.cfg may cause _all_ network tests to stop and go purple.
>
> https://bugs.debian.org/939846 and https://bugs.debian.org/867341 are
> probably related issues if not even the same issue. (867341: "all
> networks tests gone purple and reading xymonnet log, I discovered
> buffer overflow")
>
> It's though unclear to me relation to the (working for me) conn6 test
> from hobbit-plugins is — which works fine for me (with hostnames,
> though).
>
> Nicolas: Can you tell us where exactly in xymonnet the buffer overflow
> is? Is it in xymonnet/dns.c? Because that's where I experience the
> crashes with IPv6-only URLs on hosts.cfg.
>
> Additionally, I actually also have the issue with the last night
> uploaded 4.3.30-1 in Debian Unstable.
>
> Regards, Axel
> --
> ,''`. | Axel Beckert , https://people.debian.org/~abe/
> : :' : | Debian Developer, ftp.ch.debian.org Admin
> `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
> `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
>
>

Bug#944348: buster-pu: package schleuder/3.4.0-2+deb10u1

[Georg Faerber]

On 19-11-23 18:20:08, Julien Cristau wrote:
> That looks fine to me.  Go ahead.

Thanks -- uploaded accordingly: I've only fixed a typo in the proposed
changelog note, additionally.

Cheers,
Georg

Bug#945265: [Pkg-clamav-devel] Bug#945265: new upstream version 0.102.1 to fix CVE-2019-15961

[Sebastian Andrzej Siewior]

On 2019-11-24 11:24:45 [+0100], Hugo Lefeuvre wrote:
> Dear clamav maintainers,
Hi,

> are you planning to address this in stretch/buster via -updates?  I can
> provide some help if needed (and make sure this gets backported to
> jessie-security).

I just pushed 0.102.1 into git targeting unstable. This needs some
testing and then it can end up in unstable I think.
After that, I would plan to prepare updates for stretch/buster.

> thanks!
> 
> regards,
> Hugo
> 

Sebastian

Bug#945442: Possible to backspace past beginning of string, which appears to be identical to having pressed Enter immediately, without any backspace

[Andras Korn]

Package: neomutt
Version: 2019+dfsg.1-1
Severity: normal

Hi,

when mutt prompts for something (e.g. To: address, Subject etc.) it
previously was possibly to just keep pressing backspace until whatever
default text was there disappeared.

As of this version, it's possible to keep erasing back beyond the first
character of the string; for example, when composing mail, backspacing
beyond the beginning of the offered Subject brings up the editor
with the message being composed; saving and exiting shows that the Subject
is in fact not empty but the default (e.g. "Re: original subject").

Backspacing beyond the beginning of the To: prompt likewise confirms the
default To: address and goes to the Subject prompt.

This behaviour is completely counter-intuitive and hopefully not
intentional.

I can reproduce it with mutt -F /dev/null, leading me to beleive it's not a
problem with my configuration.

Andras

-- Package-specific info:
NeoMutt 2019
Copyright (C) 1996-2016 Michael R. Elkins and others.
NeoMutt comes with ABSOLUTELY NO WARRANTY; for details type 'neomutt -vv'.
NeoMutt is free software, and you are welcome to redistribute it
under certain conditions; type 'neomutt -vv' for details.

System: Linux 4.4.185-vs2.3.9.8+uksm (x86_64)
ncurses: ncurses 6.1.20191019 (compiled with 6.1.20191019)
libidn: 1.33 (compiled with 1.33)
GPGme: 1.13.1-unknown
hcache backends: tokyocabinet

Compiler:
Using built-in specs.
COLLECT_GCC=cc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-19' 
--with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-9 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib 
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch 
--disable-werror --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none,hsa --without-cuda-driver 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix
gcc version 9.2.1 20191109 (Debian 9.2.1-19) 

Configure options: --build=x86_64-linux-gnu --prefix=/usr 
{--includedir=${prefix}/include} {--mandir=${prefix}/share/man} 
{--infodir=${prefix}/share/info} --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules {--libdir=${prefix}/lib/x86_64-linux-gnu} 
{--libexecdir=${prefix}/lib/x86_64-linux-gnu} --disable-maintainer-mode 
--disable-dependency-tracking --mandir=/usr/share/man --libexecdir=/usr/libexec 
--with-mailpath=/var/mail --gpgme --lua --notmuch --with-ui --gnutls --gss 
--idn --mixmaster --sasl --tokyocabinet

Compilation CFLAGS: -g -O2 
-fdebug-prefix-map=/build/neomutt-jdVSn8/neomutt-2019+dfsg.1=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c99 
-D_ALL_SOURCE=1 -D_GNU_SOURCE=1 -D__EXTENSIONS__ -I/usr/include 
-I/usr/include/lua5.3 -DNCURSES_WIDECHAR -isystem /usr/include/mit-krb5

Default options:
  +attach_headers_color +compose_to_sender +compress +cond_date +debug 
  +encrypt_to_self +forgotten_attachments +forwref +ifdef +imap +index_color 
  +initials +limit_current_thread +multiple_fcc +nested_if +new_mail +nntp +pop 
  +progress +quasi_delete +regcomp +reply_with_xorig +sensible_browser +sidebar 
  +skip_quoted +smtp +status_color +timeout +tls_sni +trash 

Compile options:
  -autocrypt +bkgdset +color +curs_set +fcntl -flock -fmemopen +futimens 
  +getaddrinfo +gnutls +gpgme +gss +hcache -homespool +idn +inotify 
  -locales_hack +lua +meta +mixmaster +nls +notmuch -openssl +pgp +sasl +smime 
  -sqlite +start_color +sun_attachment +typeahead 
MAILPATH="/var/mail"
MIXMASTER="mixmaster"
PKGDATADIR="/usr/share/neomutt"
SENDMAIL="/usr/sbin/sendmail"
SYSCONFDIR="/etc"

To learn more about NeoMutt, visit: https://neomutt.org
If you find a bug in NeoMutt, please raise an issue at:
https://github.com/neomutt/neomutt/issues
or send an email to: 

-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (350, 'unstable'), (350, 'stable'), (98, 'eoan-updates'), (98, 
'eoan-security'), (98, 'eoan-proposed'), (98, 'eoan-backports'), (98, 'eoan'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.185-vs2.3.9.8+uksm (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)

Bug#813041: icedtea-netx should not depend on default-jre

[Marco Gamberoni]

In data sabato 23 novembre 2019 19:36:03 CET, hai scritto:
> 
> Hello Marco,
> 
> I agree about the hard dependency on default-jre.  
Hello Tony,
no, I did not say so: my wish is icedtea-netx depend on _provided_ java-runtime.

> That's the reason
> that the javaX-runtime virtual dependencies were created.  However, I'm
> not sure about creating a new java-runtime dependency, since I think
> that we're going to continue to have situations where we have to
> differentiate between JRE runtimes.
> 
Icedtea-netx is a program written in java, so it depends on a java runtime to
run. Its job is to download a java application described by a jnlp file that 
also
declares some JRE version under which the downloaded app wants to run.
While icedtea-netx must be compatible with any JRE, or it is its own bug, the
downloaded app JRE requirement is out of Debian packaging control, is
written in the jnlp file, and is icedtea-netx (javaws) business.
So the ipotetical need to differentiate between JRE runtimes in the dependency
list of icedtea-netx would be a bug in icedtea-netx.

> Since the default-jre going back to oldstable provides java8-runtime,
> would it be okay to have icedtea-web depend on java8-runtime, which can
Would work, but is less clean: the virtual package java8-runtime would 
be recycled to convey the semantics of java-runtime (="any JRE"), just because
currently (afaict) all available JRE packages provide java8-runtime; while, 
otoh,
openjdk-8-jre does not provide java-runtime. But it should, shouldn't it?
It seems to me, this is a packaging bug in openjdk-8-jre.

> be satisfied by default-jre for stretch and anything later?  This should
It is not default-jre's duty to provide java8-runtime, it is up to the JRE 
package
that is installed because default-jre depends on it.
I would argue that default-jre should not have a "Provides:" field at all.

> simplify your use case and continue to work until there is a default-jre
> that is for some reason unable to run older byte code.

> 
> Cheers,
> tony
> 

My facts:
 - default-jre is a REAL PACKAGE, which pulls in the current version of a JRE.
 - java-runtime and java8-runtime and java[0-9]+-runtime are virtual packages
 - icedtea-netx runs with openjdk-8-jre and openjdk-11-jre. Due to its role, it
   has to run with any JRE, or it is a bug.

My problem: install just any single JRE package _and_ icedtea-netx, nothing
else. No default-jre and none of its dependencies wanted.
My understanding of packaging logic is that to make this possible:
  - icedtea-netx should depend on java-runtime.
  - any package that installs a JRE should provide java-runtime

Also, as Java Web Start technology has been deprecated by Oracle after Java 8,
and support has been picked up as an open source project:
https://openwebstart.com/
which is endorsed by icedtea-netx upstream
   https://github.com/AdoptOpenJDK/IcedTea-Web
placing in default-jre a "suggest" to icedtea-netx seems a good thing. 
Following the changes in the upstream of the free implementation of Java Web
Start technology has been difficult. A suggest (perhaps also a recommend) is
good service to users.

Thanks for listening,

-- 
Marco Gamberoni

_

PGP Fingerprint: 945C CE09 7D11 E1A0 5D8D  306E DAE1 C4A6 0BB3 7A16

Bug#945441: Acknowledgement (isc-dhcp-client: dhclient fails to obtain address or routes, apparently because of mangled section in dhclient.leases)

[Michael Redman]

Hi Team,

I forgot to include, this bug seems similar to, but not exactly the same 
as, #851950 "unusual signs in dhclient.leases"


Kind regards,

Michael Redman

On 11/24/19 10:03 PM, Debian Bug Tracking System wrote:

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 945441: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945441.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

As you requested using X-Debbugs-CC, your message was also forwarded to
   michael.redma...@gmail.com
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
  Debian ISC DHCP Maintainers 

If you wish to submit further information on this problem, please
send it to 945...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

Bug#945441: isc-dhcp-client: dhclient fails to obtain address or routes, apparently because of mangled section in dhclient.leases

[Michael Redman]

Package: isc-dhcp-client
Version: 4.4.1-2
Severity: important

Dear Maintainer,

dhclient failed to renew address or set routes for me. I found the following in 
syslog:

Nov 24 19:08:41 orion dhclient[1840]: Can't allocate interface enx0015fflease 
{#012  interface .
Nov 24 19:08:41 orion dhclient[1840]: 
Nov 24 19:08:41 orion dhclient[1840]: If you think you have received this 
message due to a bug rather
Nov 24 19:08:41 orion dhclient[1840]: than a configuration issue please read 
the section on submitting
Nov 24 19:08:41 orion dhclient[1840]: bugs on either our web page at 
www.isc.org or in the README file
Nov 24 19:08:41 orion dhclient[1840]: before submitting a bug.  These pages 
explain the proper
Nov 24 19:08:41 orion dhclient[1840]: process and the information we find 
helpful for debugging.
Nov 24 19:08:41 orion dhclient[1840]: 
Nov 24 19:08:41 orion dhclient[1840]: exiting.

I recognized the "enx0015ff..." string as part of the name that a USB LTE modem 
I use gets, when it is attached to the system. It was not attached at the time 
dhclient was failing to work.

So then I looked in /var/lib/dhcp/dhclient.leases and found this section:

lease {
  interface "enx0015fflease {
  interface "wls1";
  fixed-address 172.16.0.70;
  option subnet-mask 255.255.254.0;
  option routers 172.16.0.1;
  option dhcp-lease-time 86400;
  option dhcp-option-overload 3;
  option dhcp-message-type 5;
  option domain-name-servers 172.16.0.1;
  option dhcp-server-identifier 172.16.0.1;
  renew 4 2019/11/21 08:00:31;
  rebind 4 2019/11/21 18:23:18;
  expire 4 2019/11/21 21:23:18;
}

which to me appears to have bad syntax in that the curly braces do not match 
and there are two interface names specified for one lease block.

When I deleted this bad block, dhclient worked fine again.

I had not previously made any manual modifications to the dhclient.leases file.

Kind regards,

Michael Redman

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

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

Versions of packages isc-dhcp-client depends on:
ii  debianutils4.8.6.1
ii  iproute2   4.20.0-2
ii  libc6  2.28-10
ii  libdns-export1104  1:9.11.5.P4+dfsg-5.1
ii  libisc-export1100  1:9.11.5.P4+dfsg-5.1

Versions of packages isc-dhcp-client recommends:
ii  isc-dhcp-common  4.4.1-2

Versions of packages isc-dhcp-client suggests:
ii  avahi-autoipd 0.7-4+b1
pn  isc-dhcp-client-ddns  
pn  resolvconf

-- no debconf information

Bug#945438: libaqbanking: Version 6 no longer works with ING DiBa bank

[Micha Lenk]

Control: forwarded -1 https://www.aquamaniac.de/rdm/issues/134

This is already tracked in the upstream bug tracker as 
https://www.aquamaniac.de/rdm/issues/134 (sorry, German only). So far it seems 
to be an unsolved issue.

Best regards,
Micha

Bug#834410: ITA: giflib -- library for GIF images

[David Suárez]

control: retitle -1 ITA: giflib -- library for GIF images
control: owner -1 david.sephi...@gmail.com

Bug#922566: FTBFS against opencv 4.0.1 (exp)

[Steve Langasek]

Package: actiona
Version: 3.10.0-1
Followup-For: Bug #922566
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Control: tags -1 + patch

Hello,

Attached is a patch to fix actiona for source compatibility with opencv 4. 
I have uploaded these changes to Ubuntu for the opencv4 transition.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru actiona-3.10.0/debian/patches/opencv4-compat.patch 
actiona-3.10.0/debian/patches/opencv4-compat.patch
--- actiona-3.10.0/debian/patches/opencv4-compat.patch  1969-12-31 
16:00:00.0 -0800
+++ actiona-3.10.0/debian/patches/opencv4-compat.patch  2019-11-24 
11:57:11.0 -0800
@@ -0,0 +1,71 @@
+Description: compatibility with opencv4
+ Some code assumes only opencv 2 and opencv 3 exist.
+Author: Steve Langasek 
+Last-Updated: 2019-11-24
+Bug-Debian: https://bugs.debian.org/922566
+
+Index: actiona-3.10.0/actiontools/opencvalgorithms_private.h
+===
+--- actiona-3.10.0.orig/actiontools/opencvalgorithms_private.h
 actiona-3.10.0/actiontools/opencvalgorithms_private.h
+@@ -23,6 +23,7 @@
+ #include "opencvalgorithms.h"
+ 
+ #include 
++#include 
+ 
+ #include 
+ 
+@@ -33,7 +34,7 @@
+ }
+ 
+ using Mat = cv::Mat;
+-#elif CV_MAJOR_VERSION == 3
++#elif CV_MAJOR_VERSION >= 3
+ namespace cv
+ {
+ class UMat;
+Index: actiona-3.10.0/actiontools/opencvalgorithms.cpp
+===
+--- actiona-3.10.0.orig/actiontools/opencvalgorithms.cpp
 actiona-3.10.0/actiontools/opencvalgorithms.cpp
+@@ -350,7 +350,7 @@
+ 
+ #if CV_MAJOR_VERSION == 2
+ const Mat  = image;
+-#elif CV_MAJOR_VERSION == 3
++#elif CV_MAJOR_VERSION >= 3
+ cv::Mat matImage = image.getMat(cv::ACCESS_READ);
+ #endif
+ 
+@@ -394,7 +394,7 @@
+   {
+ #if CV_MAJOR_VERSION == 2
+ const cv::Mat  = image;
+-#elif CV_MAJOR_VERSION == 3
++#elif CV_MAJOR_VERSION >= 3
+ cv::Mat matImage = image.getMat(cv::ACCESS_READ);
+ #endif
+ 
+@@ -411,7 +411,7 @@
+ 
+ #if CV_MAJOR_VERSION == 2
+ return back;
+-#elif CV_MAJOR_VERSION == 3
++#elif CV_MAJOR_VERSION >= 3
+ return back.getUMat(cv::ACCESS_RW);
+ #endif
+ }
+Index: actiona-3.10.0/actiontools/actiontools.pro
+===
+--- actiona-3.10.0.orig/actiontools/actiontools.pro
 actiona-3.10.0/actiontools/actiontools.pro
+@@ -6,7 +6,7 @@
+ TEMPLATE = lib
+ CONFIG += dll
+ unix:CONFIG += link_pkgconfig
+-unix:PKGCONFIG += opencv
++unix:PKGCONFIG += opencv4
+ DEFINES += ACTIONTOOLS_LIBRARY
+ TARGET = actiontools
+ DESTDIR = ..
diff -Nru actiona-3.10.0/debian/patches/series 
actiona-3.10.0/debian/patches/series
--- actiona-3.10.0/debian/patches/series2019-01-07 06:26:27.0 
-0800
+++ actiona-3.10.0/debian/patches/series2019-11-24 11:56:10.0 
-0800
@@ -0,0 +1 @@
+opencv4-compat.patch

Bug#945440: audacity: Bump to version 2.3.3

[Dennis Braun]

Package: audacity
Version: 2.3.2-2

please bump to version 2.3.3.
https://www.audacityteam.org/audacity-2-3-3-released/

check my patch for small changes in the debian files for 2.3.3.

i tested the build on my local machine with pbuilder.

diff -ruN audacity-2.3.2/debian/changelog audacity-2.3.3/debian/changelog
--- audacity-2.3.2/debian/changelog
+++ audacity-2.3.3/debian/changelog
@@ -1,3 +1,15 @@
+audacity (2.3.3-1) unstable; urgency=medium
+
+  * New upstream release.
+  * Bump debhelper-compat to 12.
+  * Bump Standards-Version to 4.4.1.
+  * Drop obsolete d/NEWS file.
+  * debian/patches:
++ 0002-workaround-wxwidgets-fit-recovery.patch: Drop, Obsolete.
++ 0005-Fix-building-against-the-system-portaudio-library.patch: Update. 
+
+ -- Dennis Braun   Thu, 21 Nov 2019 20:50:20 +0100
+
 audacity (2.3.2-2) unstable; urgency=medium
 
   * Team upload.
diff -ruN audacity-2.3.2/debian/control audacity-2.3.3/debian/control
--- audacity-2.3.2/debian/control
+++ audacity-2.3.3/debian/control
@@ -6,8 +6,8 @@
Benjamin Drung ,
David Henningsson ,
Jaromír Mikeš 
-Standards-Version: 4.4.0
-Build-Depends: debhelper-compat (= 11),
+Standards-Version: 4.4.1
+Build-Depends: debhelper-compat (= 12),
gettext,
libasound2-dev [linux-any],
libavcodec-dev (>= 6:0.8),
diff -ruN audacity-2.3.2/debian/NEWS audacity-2.3.3/debian/NEWS
--- audacity-2.3.2/debian/NEWS
+++ audacity-2.3.3/debian/NEWS
@@ -1,8 +0,0 @@
-audacity (1.3.6-3) unstable; urgency=low
-
-Explicitly built against the system libsamplerate, effectively disabling
-the internal libresample. This may break support for proprietary VST
-plug-ins!
-
- -- Fabian Greffrath   Tue, 20 Jan 2009 09:15:11 +0100
-
diff -ruN audacity-2.3.2/debian/patches/0005-Fix-building-against-the-system-portaudio-library.patch audacity-2.3.3/debian/patches/0005-Fix-building-against-the-system-portaudio-library.patch
--- audacity-2.3.2/debian/patches/0005-Fix-building-against-the-system-portaudio-library.patch
+++ audacity-2.3.3/debian/patches/0005-Fix-building-against-the-system-portaudio-library.patch
@@ -29,10 +29,10 @@
 
 --- a/src/AudioIO.cpp
 +++ b/src/AudioIO.cpp
-@@ -465,8 +465,23 @@ TimeTrack and AudioIOListener and whethe
+@@ -480,8 +480,23 @@
 #define ROUND(x) (int) ((x)+0.5)
 //#include 
-#include "../lib-src/portmidi/pm_common/portmidi.h"
+ //   #include "../lib-src/portmidi/pm_common/portmidi.h"
 -   #include "../lib-src/portaudio-v19/src/common/pa_util.h"
 #include "NoteTrack.h"
 +
diff -ruN audacity-2.3.2/debian/patches/series audacity-2.3.3/debian/patches/series
--- audacity-2.3.2/debian/patches/series
+++ audacity-2.3.3/debian/patches/series
@@ -1,5 +1,5 @@
 0001-fix-minsrc-autoreconf.patch
-0002-workaround-wxwidgets-fit-recovery.patch
+#0002-workaround-wxwidgets-fit-recovery.patch
 0004-desktop.patch
 0005-Fix-building-against-the-system-portaudio-library.patch
 0006-Link-atomic-if-needed.patch


signature.asc
Description: OpenPGP digital signature

Bug#944116: tasksel: Please make another source-only upload

[Boyuan Yang]

Hi Holger,

在 2019-11-24日的 12:15 +0100，Holger Wansing写道：
> Hi,
> 
> I have upload rights for d-i packages, so sponsoring not needed.
> But I need help with such an non-source-only upload, as it seems :-|
> 
> My amd64 binary upload was just rejected, I suspect because it does go
> through NEW:
> 
> 
> 
> =
> Date: Sun, 24 Nov 2019 10:53:57 +
> From: Debian FTP Masters 
> To: Holger Wansing , Anton Zinoviev <
> zinov...@debian.org>
> Subject: tasksel_3.57_amd64.changes REJECTED
> 
> 
> 
> 
> ACL dm: NEW uploads are not allowed
> 
> binary:task-chinese-s is NEW.
> binary:task-cyrillic-kde-desktop is NEW.
> binary:task-hebrew-desktop is NEW.
> binary:task-macedonian is NEW.
> binary:task-slovenian-kde-desktop is NEW.
> binary:task-chinese-s is NEW.
> binary:task-hebrew-desktop is NEW.
> binary:task-slovenian-kde-desktop is NEW.
> binary:task-cyrillic-kde-desktop is NEW.
> binary:task-macedonian is NEW.
> 
> 
> =
> 
> 
> 
> But I cannot find any documentation about how to define, if such upload
> should go through NEW (or maybe I have overlooked it?)

I believe it is like this. If:

1. You are making an upload onto Sid that contains binary package foo provided
by src:foobar,
2. The binary package foo is neither present in Sid nor in Experimental,

...then this upload must go through NEW, which is the same as our current
situation.

> In the past, I have only done source-only uploads.

I have elected to build tasksel 3.57 from git packaging repo (
https://salsa.debian.org/installer-team/tasksel) and made a non-source-only
upload onto DELAYED/2. It should enter the NEW queue 2 days later.

Dear FTP Masters: please review and accept this upload after it appears in the
NEW queue. As discussed in https://bugs.debian.org/944116 , no new packages
were actually introduced and this upload was made to circumvent a bug that
potentially lay in DAK; this bug should have been fixed by now.
Please let me know if further actions are needed.

-- 
Best,
Boyuan Yang

Bug#945439: ITP: python-pyluach -- Hebrew (Jewish) calendar dates and Hebrew-Gregorian conversions

[Michael Fladischer]

Package: wnpp
Severity: wishlist
Owner: Michael Fladischer 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: python-pyluach
  Version : 1.0.1
  Upstream Author : Meir S. List 
* URL : https://github.com/simlist/pyluach/
* License : Expat
  Programming Lang: Python
  Description : Hebrew (Jewish) calendar dates and Hebrew-Gregorian 
conversions

 Pyluach is a Python package for manipulating Hebrew (Jewish) calendar dates and
 Hebrew-Gregorian conversions.
 .
 Features:
  * Conversion between Hebrew and Gregorian dates
  * Finding the difference between two dates
  * Finding a date at a given duration from the given date
  * Rich comparisons between dates
  * Finding the weekday of a given date
  * Finding the weekly Parsha reading of a given date

I intend to maintain this as part of the DPMT as a prerequisite for a future
workalendar package.

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAl3a6P4RHGZsYWRpQGRl
Ymlhbi5vcmcACgkQ/9PIi5l90WozsQgAsHwIP5wnm1qWakwm1fJ3psHubfZkIRh3
TCMaBcP96AVTy30YYkOP9+OWIhrStI6sgtl1FCDSGbtpm/fU7Uxi9ZrJVZD3eIaW
PONtztSaOUUTSsorS3JPE5uubRgsVzAaPCgE/VHVtWeTF0TNZ3ZU4Sa6HZoKsllk
vYKG4BQ4c6xYdZq4gzUHhIBRXQq1CRsp//8JBawfpWODJDdqjF1bP85F/Q9Uc5FV
C84+OFe5uFxP7b107AAQv5w2k4Leg319JqFhwf96amGaQiRagW69utcYn9jNdKtm
4yr0TPKm03Q535b95oQfq7skiHjoqhN7Vg5aF7QBnEox3xg45pZ9kw==
=wMZi
-END PGP SIGNATURE-

Bug#945438: libaqbanking: Version 6 no longer works with ING DiBa bank

[John Paul Adrian Glaubitz]

Source: libaqbanking
Version: 5.99.43beta-2
Severity: normal
Tags: upstream

Hi!

The latest version of libaqbanking that the 3.7-2 package version of gnucash
depends on is currently incompatible with the German bank ING DiBa [1].

In order to get it to work again, I had to downgrade gnucash, gnucash-common
and libaqbanking-data to their previous versions and purge the libaqbanking45
package.

I have no checked yet whether upstream is working on a solution.

Adrian

> [1] 
> https://www.aquamaniac.de/rdm/projects/aqbanking/wiki/AqBanking6_Bankentabelle

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#944589: gsequencer: stalls system

[Joël Krähemann]

Hi,

I think there is no problem except the lack CPU resources,
GSequencer needs power and pulseaudio behaves
really bad on low CPU power.

Please, try the ALSA configuration as previously been told.

This always appears, even as loading builtin config:

/home/user/.gsequencer/ags.conf

This is not bad, just an information that gsequencer was
not able to set RT priorities:

sched_setscheduler failed: Operation not permitted

to set RT priorities a process needs the permission
to do so.

regards,
Joël

On Sun, Nov 24, 2019 at 8:55 PM westlake  wrote:
>
> ""** Message: 13:46:42.039: loading preferences for:
> /home/user/.gsequencer/ags.conf
> sched_setscheduler failed: Operation not permitted
> "
>
> I managed to get the full error message before gsequencer fully stalls
> the system..
>
> "timeout -s kill -k 30 30 gsequencer"[enter]
>
> something is wrong because the "timeout" command is not able to
> auto-shutdown the gsequencer process..

Bug#936015: marked as done (ceph: CVE-2019-10222)

[Bernd Zeimetz]

On 11/24/19 8:38 PM, Salvatore Bonaccorso wrote:
> Hi Bernd,
> 
> On Mon, Nov 18, 2019 at 02:45:14PM +, Debian Bug Tracking System wrote:
> [...]
>> Version: 14.2.4-1
>>
>> Forgot to mention that bug in the changelog unfortunately.
>>
>> ceph (14.2.4-1) unstable; urgency=medium
> 
> Do you know where this upload got lost? It's not in NEW and it does
> not appear to be in unstable either.

yeah, got auto-rejected as it missed some overrides.. (needs rpath to
find libjvm...).

and while fixing that I found some issues in debian/copyright... will
take a few more days unfortunately.



-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Bug#945437: RM: fslint -- RoQA; Orphaned; Python 2 only, not ported to Python 3

[Boyuan Yang]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove

Dear FTP Masters,

Package fslint (https://tracker.debian.org/pkg/fslint) is now orphaned and
python2 only with dependency on really obsoleted pygtk. Its upstream has no
intent to migrate the software onto Python 3 in the near future (see 
https://github.com/pixelb/fslint/issues/147). As a result, I am requesting a
package removal from Sid as part of the python2/pygtk removal effort.

Please remove package fslint from Sid. If there are any issues, please let me
know.

-- 
Regards,
Boyuan Yang


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

Bug#945243: libpsl FTBFS: ../libpsl-docs.sgml:27: element include: XInclude error : could not load ../xml/tree_index.sgml, and no fallback was found

[Simon McVittie]

Control: tags -1 + upstream

On Thu, 21 Nov 2019 at 19:49:37 +0100, Helmut Grohne wrote:
> libpsl recently (within the last seven days) started to FTBFS in
> unstable:
> | warning: failed to load external entity "../xml/tree_index.sgml"
> | ../libpsl-docs.sgml:27: element include: XInclude error : could not load 
> ../xml/tree_index.sgml, and no fallback was found

This is very likely to be a regression with gtk-doc 1.3x (1.30 I think?),
and will affect upstream builds equally. gtk-doc stopped generating files
that would previously have been generated empty. This is a deliberate
change by upstream (https://gitlab.gnome.org/GNOME/gtk-doc/issues/103)
so it is unlikely to be reverted.

The GNOME team tried to file bugs for this while gtk-doc 1.32 was only
in experimental, but the mass-rebuild must have missed libpsl.

Library maintainers can either solve this class of bug by not
attempting to include the object tree at all, which for example is
appropriate if the library does not include any GObject subclasses:
https://gitlab.freedesktop.org/gstreamer/gst-libav/merge_requests/40

or by adding an empty  inside the  element
for ../xml/tree_index.sgml (meaning "if you can't, substitute the empty
string instead") to return to the previous behaviour, similar to this
in GTK's documentation:

  
Index of new symbols in 3.24

  

Regards,
smcv

Bug#945436: rust-debcargo Build-Depends on package that doesn't exist: librust-git2-0.8+default-dev

[Paul Gevers]

Source: rust-debcargo
Version: 2.4.0-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainer,

Your package is part of the libgit2 transition and I scheduled binNMU's for
those. However, your package fails to build from source because it build
depends on a package that doesn't exist: librust-git2-0.8+default-dev.

Please fix the situation.

Paul

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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3a5FYACgkQnFyZ6wW9
dQozzggAmhSeSixKxfOMIJRi3N5rHVf/dAGjr1ChnwYO6C3ENaNwWWQAu2kg4sPp
eTJ/Z/0pkfYyNgwzZoQmE+0irBODI/vR7TrV8Wg3tF+57jYVotW8drXyKBev2BuB
CeHdtdLyh6FdbhUVFm6iyzPsI1gOi3IXBm+9XxG8sABTVo1moAUKWKk6knAw3YVu
GTjoGLiCCjnMiEb+Pdm25BYQdKwxY+DdSjVrb7W6Pc5zDyv7D2z4iTqXHZD2V2he
2xWmuBIs2y5+nqL4fiMbO2615kFDCfsUWMI1lwVzoUKD3xxssd8/xKptntH70+8X
0NE4XaPAxWGy6t7sA6jzCpf3iVMbTA==
=iUOI
-END PGP SIGNATURE-

Bug#944480: transition: libdvdread

[Paul Gevers]

Control: tags -1 confirmed

Hi Sebastian,

On 10-11-2019 18:08, Sebastian Ramacher wrote:
> libdvdread bumped its SONAME from 4 to 7. All reverse dependencies build
> fine against the new version.

Please go ahead in unstable.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#944589: gsequencer: stalls system

[westlake]

""** Message: 13:46:42.039: loading preferences for: 
/home/user/.gsequencer/ags.conf

sched_setscheduler failed: Operation not permitted
"

I managed to get the full error message before gsequencer fully stalls 
the system..


"timeout -s kill -k 30 30 gsequencer"[enter]

something is wrong because the "timeout" command is not able to 
auto-shutdown the gsequencer process..

Bug#945435: nototools Build-Depends on python-fonttools which isn't build from source anymore

[Paul Gevers]

Source: nototools
Version: 0~20170925-1
Severity: serious
Tags: ftbfs
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

nototools is involved in the Python 2 removal of Debian. Unfortunately, one of
your Build-Depends, python-fonttools has been removed already and currenty
isn't build from source in either unstable or testing. Also (indirect)
dependencies from python-fonttools are not build anymore, python-fs and
python-backports.fs. I fear the only solution is to quickly move to the Python
3 package that you already have prepared in experimental.

Thanks

Paul


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

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

Versions of packages python-nototools depends on:
ii  python2.7.17-2
pn  python-fonttools  
pn  unicode-data  

python-nototools recommends no packages.

python-nototools suggests no packages.

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3a3WQACgkQnFyZ6wW9
dQp/SQf/VuvJpeB/JcFUhil3aSrmgfjSg9HEI9XEbWXIOjjERPNOetPxCBN8w2Hy
Or5QDRQks0ThQ4L+ReexfUua4CjXS+Ydpm2fBJ97ZI0eJSBYTsBg/ZCElGVWqcNZ
B0Tf6mACg6lQegWi6EjxwO+S4Jc1ciWGl6LbRiXe8BXMT4A7ATiA0VsjMsgjx0Tj
7s+JzNCsiJO5Wi5k8pa7hT5heu125IMa6n3EPKf9Fv6PycjHIyQVrGEvIKLkGW6L
EIGKGfxI0Iaf5jY5+abVrt6J8zTbYv1TOxuppz/mvZsuxo2I/15fKPMC44jjsG9L
lv5nsBoJyU9qIJ1SvLAWJxNdkpivsw==
=kdnk
-END PGP SIGNATURE-

Bug#944396: transition: exiv2

[Paul Gevers]

Control: tags -1 confirmed

Hi Steve,

On 09-11-2019 05:50, Steve M. Robbins wrote:
> New upstream, new soversion.
> 
> Ben file:
> 
> title = "exiv2";
> is_affected = .depends ~ "libexiv2-14" | .depends ~ "libexiv2-27";
> is_good = .depends ~ "libexiv2-27";
> is_bad = .depends ~ "libexiv2-14";

Please go ahead in unstable.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#944760: ghostscript: CVE-2019-14869

[Salvatore Bonaccorso]

Hi Jonas,

On Mon, Nov 18, 2019 at 10:34:17PM +0100, Jonas Smedegaard wrote:
> Control: severity -1 important
> 
> Quoting Salvatore Bonaccorso (2019-11-14 22:47:49)
> > Source: ghostscript
> > Version: 9.50~dfsg-2
> > Severity: grave
> > Tags: security upstream
> > Control: found -1 9.26a~dfsg-0+deb9u5
> > Control: found -1 9.26a~dfsg-0+deb9u1
> > Control: found -1 9.27~dfsg-2+deb10u2
> > Control: found -1 9.27~dfsg-1
> > Control: found -1 9.27~dfsg-3.1
> > Control: fixed -1 9.26a~dfsg-0+deb9u6
> > Control: fixed -1 9.27~dfsg-2+deb10u3
> > 
> > Hi,
> > 
> > The following vulnerability was published for ghostscript. I can agree
> > the severity is not exaclty matching, as for 9.50 itself, it's not
> > anymore directly exploitable (unless with -dOLDSAFER). Still it cannot
> > be considred fixed, only after applying [1].
> 
> Lowering severity to avoid this blocking more grave security fixes 
> entering testing.

Possible tho cherry-pick as well the fixing commit so we can get the
CVE out of the radar for bullseye/sid?

Regards,
Salvatore

Bug#936015: marked as done (ceph: CVE-2019-10222)

[Salvatore Bonaccorso]

Hi Bernd,

On Mon, Nov 18, 2019 at 02:45:14PM +, Debian Bug Tracking System wrote:
[...]
> Version: 14.2.4-1
> 
> Forgot to mention that bug in the changelog unfortunately.
> 
> ceph (14.2.4-1) unstable; urgency=medium

Do you know where this upload got lost? It's not in NEW and it does
not appear to be in unstable either.

Regards,
Salvatore

Bug#754129: RFP: lutris -- An open gaming platform for Linux

[Stephan Lachnit]

I've been working to improve the upstream package compliance of Lutris, since 
it's an Ubuntu native package. The current state of my work can be seen here: 
https://github.com/lutris/lutris/pull/2476

In case this will be merged for the next version, I will upload a version will 
all the necessary Debian specific changes to salsa and ask for a sponsor. 
However there's still more work to do and any help is welcome, there's a TODO 
file in the debian directory if someone is interested, but really any review is 
welcome.

Regards,
Stephan

Bug#945433: FTBFS: Invalid SPIR-V binary version 1.3 for target environment SPIR-V 1.0 (under OpenGL 4.5 semantics)

[Simon McVittie]

Source: glslang
Version: 7.13.3496-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=glslang=amd64=7.13.3496-1=1574253637=0
(and all the other architectures):

> 1/1 Test #1: glslang-testsuite ***Failed7.43 sec
> Running reflection...
> Comparing single thread to multithread for all tests in current directory...
> Running entry-point renaming tests
> Running ill-defined uncalled function
> Tests Succeeded.
> Running explicit stage test and compound suffix tests
> Running hlsl offsets
> Running hlsl offsets
> Configuring HLSL descriptor set and binding number manually
> Testing per-descriptor-set IO map shift
> Testing SPV no location
> Testing SPV Debug Information
> 2,3d1
> < error: SPIRV-Tools Validation Errors
> < error: Invalid SPIR-V binary version 1.3 for target environment SPIR-V 1.0 
> (under OpenGL 4.5 semantics).
> Testing Includer
> Testing -D and -U
> Testing --client and --target-env
> spv.targetVulkan.vert
> spv.targetOpenGL.vert
> spv.targetVulkan.vert
> spv.targetVulkan.vert
> spv.targetOpenGL.vert
> spv.targetVulkan.vert
> spv.targetOpenGL.vert
> spv.targetVulkan.vert
> Testing GLSL entry point rename
> Testing remapper error handling
> Testing position Y inversion
> Testing hlsl_functionality1
> Testing HLSL-specific PP feature expansion
> Testing nan-clamp
> Tests Failed.

Bug#945434: /usr/bin/owncloudcmd: Abort on startup

[Nigel Horne]

Package: owncloud-client-cmd
Version: 2.2.4+dfsg-2
Severity: normal
File: /usr/bin/owncloudcmd

Resubmitting from correct e-mail address:

When I run

$ owncloudcmd -n --non-interactive --trust /foo/bar 
https://myserver/owncloud

I get

QIODevice::read (QFile, 
"/home/njh/.local/share/data//ownCloud//cookies.db"): device not open
Set proxy configuration to use system configuration
Cannot load system exclude list or list supplied via --exclude
Aborted


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

Kernel: Linux 4.9.0-9-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages owncloud-client-cmd depends on:
ii  libc6 2.24-11+deb9u4
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libowncloudsync0  2.2.4+dfsg-2
ii  libqt5core5a  5.7.1+dfsg-3+deb9u1
ii  libqt5network55.7.1+dfsg-3+deb9u1
ii  libqt5sql5-sqlite 5.7.1+dfsg-3+deb9u1
ii  libstdc++66.3.0-18+deb9u1
ii  owncloud-client-l10n  2.2.4+dfsg-2

owncloud-client-cmd recommends no packages.

owncloud-client-cmd suggests no packages.

-- no debconf information

Bug#945432: RFS: systune/0.5.10 -- kernel tuning through the /proc file system

[Sudip Mukherjee]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "systune"

 * Package name: systune
   Version : 0.5.10
   Upstream Author : NA
 * URL : NA
 * License : GPL-2.0+
 * Vcs : https://github.com/sudipm-mukherjee/systune.git
   Section : admin

It builds those binary packages:

  systune - kernel tuning through the /proc file system

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/systune/systune_0.5.10.dsc

Changes since the last upload:

   * Add error message to systunedump and option to dump all (Closes: #672283)


-- 
Regards
Sudip

Bug#765854: ecryptfs-utils: Private directory not automatically unmounted anymore on logout

[Adam Greene]

Based on some of the workarounds provided in this thread, the following
script (or documentation, half of it is comments and echo statements) will
get ecryptfs + per-user automounting/unmounting working on a Debian 10
(Buster) system

Use at your own risk, this is not official documentation but it has been
tested on at least one system. There may be a few apt dependencies missing,
but most should be included in the list in the script:

https://gist.github.com/mzpqnxow/ce8fbfb6fe10e5e722425ecd1d80d506

I suggest running it manually, one command at a time, to diagnose any
issues that may arise based on your system configuration

In summary:

1. Installs dependencies for building ecryptfs-utils-111
2. Builds and installs ecryptfs-utils-111 from source with /usr as a PREFIX
3. Sets /usr/sbin/mount.ecryptfs_private to 4755
4. Updates the PAM configuration for common-auth and common-session

It seems to work with a single session or multiple sessions, with the last
session logout properly triggering the unmount in my testing

This works well enough for me for now, but can we expect this to be
resolved any time soon? For some users, myself included, lacking
ecryptfs-utils and private directory encryption is a showstopper

Bug#945431: systemd: missing files

[westlake]

Package: systemd
Version: 242-8~bpo10
Severity: important

listing the contents of systemd_242-8~bpo10+1_amd64.deb shows that 
org.freedesktop.systemd1.service is missing from this package


please add this service file as it is needed for systemctl --user commands

thanks

Bug#945051: [debian-mysql] Bug#945051: galera-3: incompatible with fs.protected_regular = 1

[Alexander E. Patrakov]

Control: reassign -1 mariadb-server-10.3 1:10.3.18-0+deb10u1
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-21140

Also created a pull request upstream:
https://github.com/MariaDB/server/pull/1417

Bug#945430: guake: package does not tag python3-gi-cairo as a dependency

[Robert Matusewicz]

Package: guake
Version: 3.6.3-1
Severity: normal

Dear Maintainer,

It looks like Guake package does not tag python3-gi-cairo as a dependency.
Without it, Guake crash when user tries to show/hide it with error

TypeError: Couldn't find foreign struct converter for 'cairo.Context'

This bug was originally rasied by David Lee on Ubuntu Bug Tracker

Best regards
Robert Matusewicz



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

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

Versions of packages guake depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.34.0-1
ii  gir1.2-glib-2.0  1.62.0-1
ii  gir1.2-gtk-3.0   3.24.12-1ubuntu1
ii  gir1.2-keybinder-3.0 0.3.2-1
ii  gir1.2-notify-0.70.7.8-1ubuntu1
ii  gir1.2-pango-1.0 1.42.4-7
ii  gir1.2-vte-2.91  0.58.2-1ubuntu2
ii  libglib2.0-bin   2.62.1-1
ii  libutempter0 1.1.6-3
ii  python3  3.7.5-1
ii  python3-cairo1.16.2-1build2
ii  python3-dbus 1.2.12-1
ii  python3-gi   3.34.0-1
ii  python3-pbr  5.1.1-0ubuntu3

guake recommends no packages.

Versions of packages guake suggests:
pn  numix-gtk-theme  

-- no debconf information

Bug#693587: bind9: stop resolving

[Ondřej Surý]

Marco,

could you please fill an upstream issue?

Ondřej
--
Ondřej Surý 

> On 24 Nov 2019, at 19:30, Marco d'Itri  wrote:
> 
> On Feb 21, Marco d'Itri  wrote:
> 
>>> That TTL is extremely suspicious and is way longer than anything
>>> warranted by IT zone contents.  Looks like the clock went back almost
>>> seven days since the entry was added to the cache.
>> I cannot see how this could be possible: the hardware clock is correct 
>> and the laptop was shutdown at most for 1-2 hours.
>> I am not sure, but I think that the problem does not happen when it is 
>> shut down overnight, only when I commute.
>> There is no NTP daemon: in some locations rdate is started when 
>> connecting to the network, but I see from the log that it fails as well 
>> because of DNS issues, so it's not changing the clock.
> Is there anything else that I can do to help you debug this?
> Currently it happens almost every time I suspend, also overnight.
> 
> -- 
> ciao,
> Marco

Bug#942854: virtualbox: Guest additions ISO image fails to download

[Lucas Nussbaum]

Hi,

This seems to be tracked upstream as https://www.virtualbox.org/ticket/18653

(but that ticket isn't very helpful)

Lucas

Bug#945429: Please also package grass-addons

[積丹尼 Dan Jacobson]

Package: grass
Severity: wishlist

Please also package grass-addons:
https://github.com/OSGeo/grass-addons
https://grasswiki.osgeo.org/wiki/AddOns/GRASS_7

And grass-addons-doc:
https://grass.osgeo.org/documentation/manuals/
https://grass.osgeo.org/grass76/manuals/addons/

Thanks.

Bug#693587: bind9: stop resolving

[Marco d'Itri]

On Feb 21, Marco d'Itri  wrote:

> > That TTL is extremely suspicious and is way longer than anything
> > warranted by IT zone contents.  Looks like the clock went back almost
> > seven days since the entry was added to the cache.
> I cannot see how this could be possible: the hardware clock is correct 
> and the laptop was shutdown at most for 1-2 hours.
> I am not sure, but I think that the problem does not happen when it is 
> shut down overnight, only when I commute.
> There is no NTP daemon: in some locations rdate is started when 
> connecting to the network, but I see from the log that it fails as well 
> because of DNS issues, so it's not changing the clock.
Is there anything else that I can do to help you debug this?
Currently it happens almost every time I suspend, also overnight.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#944876: RFS: boogie 2.4.1-0.1 -- verifiable programming language [NMU, RC]

[Benjamin Barenblat]

As the current maintainer, I definitely do not object to this NMU (or
any other NMUs associated with this package). Sponsors, please feel free
to upload without delay.

Bug#945395: udev config disables /etc/systemd/network/ .link files for usb networking.

[Michael Biebl]

Control: forcemerge 941636 -1

basically a duplicate of #941636, so merging accordingly.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#945427: doxygen: improve rules to pick llvm version from the control file

[Norbert Lange]

Package: doxygen
Version: 1.8.16-0.1
Severity: wishlist

Dear Maintainer,

I am glad this package finally found a maintainer,
I cooked up my own versions meanwhile.

To make changing llvm versions (and supported archs),
this code would pick it up form the cntrols file:

llvm_ver = $(shell sed -n 's/.*\bllvm-\([^[:space:]]*\)-dev.*/\1/p' 
debian/control)
clang_archs = $(shell sed -n 
's/.*\bllvm-[^[:space:]]*-dev[[:space:]]*\[\(.*\)\].*/\1/p' debian/control)

export LLVM_DIR = /usr/lib/llvm-$(llvm_ver)/lib/cmake/llvm/
export Clang_DIR = /usr/lib/llvm-$(llvm_ver)/lib/cmake/clang/

Norbert

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

Kernel: Linux 5.2.0-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

Versions of packages doxygen depends on:
ii  libc62.29-3
ii  libclang1-8  1:8.0.1-4
ii  libgcc1  1:9.2.1-19
ii  libllvm8 1:8.0.1-4
ii  libstdc++6   9.2.1-19
ii  libxapian30  1.4.12-1
ii  zlib1g   1:1.2.11.dfsg-1+b1

doxygen recommends no packages.

Versions of packages doxygen suggests:
pn  doxygen-doc
pn  doxygen-gui
pn  doxygen-latex  
ii  graphviz   2.42.2-3

-- no debconf information

Bug#945391: asciidocapi: fails with AttributeError: 'NoneType' object has no attribute 'loader'

[Joseph Herlant]

Control: forwarded -1 https://github.com/asciidoc/asciidoc-py3/pull/86

Hi Simon,

Thanks a lot for the report!
I was able to reproduce the bug you described and I can confirm that
your patch works as expected.
Thanks a lot for that! :)

I forwarded your patch to the upstream repo:
https://github.com/asciidoc/asciidoc-py3/pull/86
I'll give them a few days for comments and style changes if they have
any and will release the new version after that.

Thanks again,
Joseph

Bug#754739: grub2: no grub menu and system does not boot if connected only with displayport

[Georg Lipps]

I do have a similar problem with display port. Grub set-up is correct 
since the error is only seen when using DP1.2 (and not DP1.1)


See also: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1853735

Regards



On Sun, 13 Jul 2014 14:54:48 -0400 js  wrote:

> Package: grub2
> Version: 2.00-22
> Severity: normal
>
> Dear Maintainer,
>
>
> 
=

>
> When my system is connected to a monitor with both a DVI cable and a 
dislayport cable,
> the system boots fine and after the BIOS screen I see the grub menu, 
can select the linux

> kernel to use and it boots without issue.
>
> However, if the system is connected to the monitor with only the 
displayport cable but no DVI,
> I still see the system BIOS screen after powering up, but then the 
grub menu no longer appears
> and the system does not boot. I verified this by checking 
/var/log/{syslog,messages,boot} after

> rebooting with the DVI cable inserted.
>
> If the system is connected to the monitor using only an HDMI cable, 
then again I see the BIOS
> screens, the GRUB menu is not visible but the system does boot and I 
can login via ssh.

>
> It seems this issue is restricted to using a displayport cable and 
grub, as even the default
> kernel in grub.cfg was not booted in this case, although it did boot 
when using only HDMI.

>
> [The system boots into a console without starting X and the console 
is not visible if the

> monitor input is either displayport or HDMI.]
>
> Here is the /etc/default/grub contents even though grub.cfg is 
attached as well

>
> # If you change this file, run 'update-grub' afterwards to update
> # /boot/grub/grub.cfg.
> # For full documentation of the options in this file, see:
> # info -f grub -n 'Simple configuration'
>
> GRUB_DEFAULT=0
>
> GRUB_DEFAULT="Advanced options for Debian GNU/Linux>Debian GNU/Linux, 
with Linux 3.2.0-4-686-pae"

> GRUB_TIMEOUT=11
>
> GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
> GRUB_CMDLINE_LINUX_DEFAULT="quiet"
> GRUB_CMDLINE_LINUX="splash nomodeset vga=normal loglevel=5"
> GRUB_BACKGROUND=/boot/grub/splash_images/js-active.png
>
> GRUB_GFXMODE=1600x1200x16,1600x1200,800x600x16,800x600,640x480,auto
> GRUB_GFXPAYLOAD_LINUX=text
>
> # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter 
to Linux

> GRUB_DISABLE_LINUX_UUID=true
>
> 
=

>
>
> -- Package-specific info:
>
> *** BEGIN /proc/mounts
> /dev/sda1 / ext4 
rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered 0 0

> /dev/sda3 /boot ext4 rw,relatime,user_xattr,barrier=1,data=ordered 0 0
> /dev/sda2 /usr1 ext4 rw,relatime,user_xattr,barrier=1,data=ordered 0 0
> /dev/sdb1 /usr2 ext4 rw,relatime,user_xattr,barrier=1,data=ordered 0 0

Bug#831770: smbclient: Problem still occurs

[Harald]

Package: smbclient
Version: 2:4.11.1+dfsg-3
Followup-For: Bug #831770

Dear Maintainer,

good afternoon!

I still run into this problem, even though I can use smbclient to access my 
shares. /run/samba is not existing. See here for an example session:

jupp:|home/harald > smbclient -U guest //pi/public
directory_create_or_exist: mkdir failed on directory /run/samba: Permission 
denied
Unable to initialize messaging context
directory_create_or_exist: mkdir failed on directory /run/samba: Permission 
denied
directory_create_or_exist: mkdir failed on directory /run/samba: Permission 
denied
directory_create_or_exist: mkdir failed on directory /run/samba: Permission 
denied
Enter WORKGROUP\guest's password: 
Try "help" to get a list of possible commands.
smb: \> quit

/run/samba is not existing.

In case I create it manually and give it sufficient permissions, the following 
files are created after a session:

jupp:|home/harald > smbclient -U guest //pi/public
Unable to initialize messaging context
Enter WORKGROUP\guest's password: 
Try "help" to get a list of possible commands.
smb: \> quit
jupp:|home/harald > ls -l /run/samba/
total 452
-rw-r--r-- 1 harald harald 462848 Nov 24 18:19 gencache.tdb
drwxr-xr-x 2 harald harald 40 Nov 24 18:19 msg.lock

Up to now I don't experience severe drawbacks from that being a single user.

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

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

Versions of packages smbclient depends on:
ii  dpkg  1.19.7
ii  libarchive13  3.4.0-1+b1
ii  libbsd0   0.10.0-1
ii  libc6 2.29-3
ii  libgnutls30   3.6.10-5
ii  libpopt0  1.16-14
ii  libreadline8  8.0-3
ii  libsmbclient  2:4.11.1+dfsg-3
ii  libtalloc22.3.0-3
ii  libtevent00.10.1-4
ii  libwbclient0  2:4.11.1+dfsg-3
ii  samba-common  2:4.11.1+dfsg-3
ii  samba-libs2:4.11.1+dfsg-3

smbclient recommends no packages.

Versions of packages smbclient suggests:
ii  cifs-utils   2:6.9-1
pn  heimdal-clients  

-- no debconf information

Bug#945426: pylint doesn't ship the test libraries anymore

[Joseph Herlant]

Package: pylint
Version: 2.4.4-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

Thanks a lot for the prompt upgrade of pylint the other day.
Unfortunately since the upgrade, it seems we lost the testing libraries that
other packages like pylint-django rely on.

This has been introduced by this upstream PR:
https://github.com/PyCQA/pylint/pull/2958 and this specific commit:
https://github.com/PyCQA/pylint/commit/33b8185a455c1686d038258697bb93005f2441c2
This change has been released in 2.4.0.

As they are in the Debian source package, do you think it would be possible to
either have them in a separate package or
add them back to where they were before please?


In the version currently in testing we have:
$ pylint --version
pylint 2.2.2
astroid 2.1.0
Python 3.7.5 (default, Oct 27 2019, 15:43:29)
[GCC 9.2.1 20191022]
$ ls -l /usr/lib/python3/dist-packages/pylint/test
total 376K
drwxr-xr-x  2 root root 4.0K Nov 24 08:51 acceptance
- -rw-r--r--  1 root root 1.1K Oct 11  2018 conftest.py
drwxr-xr-x  2 root root 4.0K Nov 24 08:51 data
drwxr-xr-x  3 root root 4.0K Nov 24 08:51 extensions
drwxr-xr-x  2 root root  56K Nov 24 08:51 functional
drwxr-xr-x  3 root root 4.0K Nov 24 08:51 input
drwxr-xr-x  2 root root 4.0K Nov 24 08:51 messages
drwxr-xr-x 10 root root 4.0K Nov 24 08:51 regrtest_data
- -rw-r--r--  1 root root 4.7K Oct 11  2018 test_func.py
- -rw-r--r--  1 root root  13K Nov 27  2018 test_functional.py
- -rw-r--r--  1 root root 2.3K Oct 11  2018 test_import_graph.py
- -rw-r--r--  1 root root 4.1K Oct 11  2018 test_regr.py
- -rw-r--r--  1 root root  20K Oct 11  2018 test_self.py
- -rw-r--r--  1 root root  18K Oct 11  2018 unittest_checker_base.py
- -rw-r--r--  1 root root 3.8K Oct 11  2018 unittest_checker_classes.py
- -rw-r--r--  1 root root 1.8K Oct 11  2018 unittest_checker_exceptions.py
- -rw-r--r--  1 root root  18K Oct 11  2018 unittest_checker_format.py
- -rw-r--r--  1 root root 4.3K Oct 11  2018 unittest_checker_imports.py
- -rw-r--r--  1 root root 2.6K Nov 28  2018 unittest_checker_logging.py
- -rw-r--r--  1 root root 3.1K Oct 11  2018 unittest_checker_misc.py
- -rw-r--r--  1 root root  39K Oct 11  2018 unittest_checker_python3.py
- -rw-r--r--  1 root root 4.7K Oct 11  2018 unittest_checker_similar.py
- -rw-r--r--  1 root root  11K Oct 11  2018 unittest_checker_spelling.py
- -rw-r--r--  1 root root 3.7K Oct 11  2018 unittest_checker_stdlib.py
- -rw-r--r--  1 root root 2.5K Oct 11  2018 unittest_checker_strings.py
- -rw-r--r--  1 root root 4.6K Oct 11  2018 unittest_checkers_utils.py
- -rw-r--r--  1 root root 9.5K Oct 11  2018 unittest_checker_typecheck.py
- -rw-r--r--  1 root root 8.6K Oct 11  2018 unittest_checker_variables.py
- -rw-r--r--  1 root root 2.0K Oct 11  2018 unittest_config.py
- -rw-r--r--  1 root root  27K Oct 11  2018 unittest_lint.py
- -rw-r--r--  1 root root 6.2K Oct 11  2018 unittest_pyreverse_diadefs.py
- -rw-r--r--  1 root root 3.8K Oct 11  2018 unittest_pyreverse_inspector.py
- -rw-r--r--  1 root root 3.9K Oct 11  2018 unittest_pyreverse_writer.py
- -rw-r--r--  1 root root 1.7K Oct 11  2018 unittest_reporters_json.py
- -rw-r--r--  1 root root 2.5K Oct 11  2018 unittest_reporting.py
- -rw-r--r--  1 root root  14K Oct 11  2018 unittest_utils.py


$ pylint --version
pylint 2.4.4
astroid 2.3.3
Python 3.7.5 (default, Oct 27 2019, 15:43:29)
[GCC 9.2.1 20191022]
$ ls -l /usr/lib/python3/dist-packages/pylint/test
ls: cannot access '/usr/lib/python3/dist-packages/pylint/test': No such file or
directory

Thanks a ton! :)

Joseph
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE6CPaER4i14V+HYZYY/eACiPXslIFAl3au34ACgkQY/eACiPX
slLHrA//bastkKdNJPQe/bVV3edXyX5T+YwmUOZ0OynQQWk589rnIqQeptMkoY7/
IzR5vav3QfVae6yQMm6wjErB7sPaVFUAvXfi+HIygdPITWt9o78laWcHteOLE4J1
Ee0tRPxIESX+6YpZbm8Twrppdg1klU9q0kKF61xpRbC2Ujk5LDqRktpHphhPxcjb
SsIsK8WMVyf/+x/BX9RRGxVQfmQL9w310zsXlGaMIUpWH2bpy5v7KSpSCXSjLXwd
l5t0kbcvCMie0tVSrFAWOpiKjIAiZDJbOistPzJ9RF7X3TWwf4qPuhHMDBWNEV2Y
UzetkI4jBFyl5CPhH3c3D7np41AjaWt8+z/+Mc+MVFWUDTGI7AmW4z3HqH82N8z7
tiVYVwFUAbYB/usy8PJs9HMFqDbgAb5jX1hYZeRlcakK+d+fGmDv6qrmQfTwpU4X
UO0ek9qwjNKkKvlUXpHTl5zKxdjijI6U1L5d6CwXd/XUtH7nLAaCrkWgLODZm45g
JjdmyZS9pklTyZPyCf/taZbqcdew3BF65KuRbn/bYwt0AwtpyNEQ3bl6K6EEOisa
98bB6cyL/iorvuZS9+2Gpw8o9U5atFyD7frLsuewp2dBvNnV6L55DrHjShRKka+V
fI5a+MbXf/+3PUi/NhQLIuMwFQ93AGFY2Yc5n+bpFiXcHPFEklw=
=r7+y
-END PGP SIGNATURE-



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores)
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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pylint depends on:
ii  python3 3.7.5-1
ii  python3-astroid 2.3.3-1
ii  

Bug#944538: buster-pu: package ganeti-instance-debootstrap/0.16-6.1

[Antoine Beaupré]

On 2019-11-23 18:34:25, Julien Cristau wrote:
> On Mon, Nov 11, 2019 at 10:40:58AM -0500, Antoine Beaupre wrote:
>> diff -Nru ganeti-instance-debootstrap-0.16/debian/changelog 
>> ganeti-instance-debootstrap-0.16/debian/changelog
>> --- ganeti-instance-debootstrap-0.16/debian/changelog2018-06-20 
>> 06:57:18.0 -0400
>> +++ ganeti-instance-debootstrap-0.16/debian/changelog2019-11-01 
>> 19:01:50.0 -0400
>> @@ -1,3 +1,10 @@
>> +ganeti-instance-debootstrap (0.16-6.1) unstable; urgency=medium
>
> Version number and distribution don't look right.

Ah yes, that would be 0.16-6+deb10u1, right?

>> +
>> +  * Non-maintainer upload
>> +  * add patch to respect linux caps (Closes: #942114)
>> +
>> + -- Antoine Beaupré   Fri, 01 Nov 2019 19:01:50 -0400
>> +
>>  ganeti-instance-debootstrap (0.16-6) unstable; urgency=medium
>>  
>>* Bump Standards-Version to 4.1.4; no changes needed
>> diff -Nru 
>> ganeti-instance-debootstrap-0.16/debian/patches/respect-Linux-capabilities-7-in-cache.patch
>>  
>> ganeti-instance-debootstrap-0.16/debian/patches/respect-Linux-capabilities-7-in-cache.patch
>> --- 
>> ganeti-instance-debootstrap-0.16/debian/patches/respect-Linux-capabilities-7-in-cache.patch
>>   1969-12-31 19:00:00.0 -0500
>> +++ 
>> ganeti-instance-debootstrap-0.16/debian/patches/respect-Linux-capabilities-7-in-cache.patch
>>   2019-11-01 19:01:50.0 -0400
>> @@ -0,0 +1,48 @@
>> +From cd34bcc48a2af92f484535b81fba2d46dad1dbb6 Mon Sep 17 00:00:00 2001
>> +From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= 
>> +Date: Thu, 10 Oct 2019 11:07:51 -0400
>> +Subject: [PATCH] respect Linux capabilities(7) in cache
>> +
>> +The default GNU tar configuration does not carry fancy extended
>> +attributes and that is where, among other things, stuff like Linux
>> +capabilities(7) are stored. This is kind of important because that's
>> +how ping(8) works for regular users.
>> +
>> +We shove --selinux and --acls in there while we're at it, because why
>> +not. We never know what the future might bring, and it seems
>> +silly *not* to create a complete archive.
>> +
>> +Note that --xattrs-include='*' is important because, by default, GNU
>> +tar will not include capabilities /even/ if --xattrs is specified on
>> +the commandline, see this bug report for details:
>> +
>
> I'm a bit uneasy about a blanket "include all", to be honest.  It's
> probably harmless since it's all coming straight out of debootstrap, but
> I'd have been happier with something like "include security.*" if that's
> what we expect to see.

What kind of problems would you expect with including too many ACLs?

A.

-- 
Qui vit sans folie n'est pas si sage qu'il croit.
- François de La Rochefoucauld

Bug#943505: mousepad: crashes when changing search direction

[Bernhard Übelacker]

Hello Geoff Tree,
I am not involved in packaging mousepad, but tried to reproduce
the issue. Unfortunately I could not trigger the crash.

Maybe you could install a coredump collector like systemd-coredump.
The last lines of the output of the command 'journalctl --no-pager'
should give the location where the next crash happened.

Some other hints about collecting more information
are in the following document:

https://wiki.debian.org/HowToGetABacktrace

Kind regards,
Bernhard

Bug#945425: zsh: should run all pipeline elements in subshell in sh mode

[brian m. carlson]

Package: zsh
Version: 5.7.1-1+b1
Severity: normal

POSIX mandates that all elements in a pipeline are run in subshells, but
permits extensions that run some or all of those elements in the main
shell environment instead.

zsh always runs the final element in a pipeline in the normal shell
environment, which breaks programs which expect to conform to POSIX.
For example, the Git testsuite fails in a variety of ways when zsh is
/bin/sh.

This behavior is fine as zsh, since in that case it's obvious that
extensions are being enabled, but when "emulate sh" is set, the final
element in a pipeline should also be run in a subshell for maximum
compatibility with POSIX.

As an example, the attached program should print "boo", "baz", and
"foo", in that order when run under "zsh --emulate sh", but does not:


% dash foo.sh
boo
baz
foo
% zsh --emulate sh foo.sh
boo
baz
baz


-- Package-specific info:

Packages which provide vendor completions:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version Architecture Description
+++-==-===--===
ii  curl   7.66.0-1+b1 amd64command line tool for 
transferring data with URL syntax
ii  docker-compose 1.25.0-1all  Punctual, lightweight 
development environments using Docker
ii  docker.io  19.03.4+dfsg2-2 amd64Linux container runtime
ii  pulseaudio 13.0-3  amd64PulseAudio sound server
ii  systemd243-8   amd64system and service manager
ii  tmuxinator 1.1.2-1 all  Create and manage tmux sessions 
easily
ii  udev   243-8   amd64/dev/ and hotplug management 
daemon
ii  vlc-bin3.0.8-3 amd64binaries from VLC

dpkg-query: no path found matching pattern /usr/share/zsh/vendor-functions/


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

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

Versions of packages zsh depends on:
ii  libc6   2.29-3
ii  libcap2 1:2.27-1
ii  libtinfo6   6.1+20191019-1
ii  zsh-common  5.7.1-1

Versions of packages zsh recommends:
ii  libc6 2.29-3
ii  libncursesw6  6.1+20191019-1
ii  libpcre3  2:8.39-12+b1

Versions of packages zsh suggests:
pn  zsh-doc  

-- no debconf information

-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204


foo.sh
Description: Bourne shell script


signature.asc
Description: PGP signature

Bug#945424: Port extfs scripts to python3

[Laurent Bigonville]

Package: mc
Version: 3:4.8.23-1
Severity: normal

Hello,

At least 2 extfs scripts are using python and it's not clear whether
they support python3.

As python2 is being removed, that should be checked and suggested
packages (python, python-boto, python-tz) should be switched to their
python3 counter parts.

Kind regards,

Laurent Bigonville

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

Kernel: Linux 5.3.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages mc depends on:
ii  libc6 2.29-3
ii  libext2fs21.45.4-1
ii  libglib2.0-0  2.62.2-3
ii  libgpm2   1.20.7-5+b1
ii  libslang2 2.3.2-4
ii  libssh2-1 1.8.0-2.1
ii  mc-data   3:4.8.23-1

Versions of packages mc recommends:
ii  mime-support  3.64
ii  perl  5.30.0-9
ii  unzip 6.0-25

Versions of packages mc suggests:
pn  arj  
ii  bzip21.0.8-2
pn  catdvi | texlive-binaries
pn  dbview   
pn  djvulibre-bin
pn  epub-utils   
ii  evince [pdf-viewer]  3.34.1-1
ii  file 1:5.37-6
ii  genisoimage  9:1.1.11-3+b2
pn  gv   
ii  imagemagick  8:6.9.10.23+dfsg-2.1+b2
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.23+dfsg-2.1+b2
pn  libaspell-dev
ii  lynx 2.9.0dev.4-1
pn  odt2txt  
ii  poppler-utils0.71.0-6
ii  python   2.7.17-2
ii  python-boto  2.49.0-2
ii  python-tz2019.3-1
ii  w3m  0.5.3-37+b1
ii  zip  3.0-11+b1

-- no debconf information

Bug#945353: Vagrant libvirt and virtualbox providers missing for buster64 10.1.0

[Emmanuel Kasper]

Le 24/11/2019 à 17:12, Emmanuel Kasper a écrit :
> The package cache for Base Boxes is anyway always updated,

I meant here always OUTDATED ...

-- 
You know an upstream is nice when they even accept m68k patches.
  - John Paul Adrian Glaubitz, Debian OpenJDK maintainer

Bug#945353: Vagrant libvirt and virtualbox providers missing for buster64 10.1.0

[Emmanuel Kasper]

Le 23/11/2019 à 14:17, Jonas Meurer a écrit :
> Package: cloud.debian.org
> Severity: important
> 
> Hello,
> 
> for some reason, boxes for providers 'libvirt' and 'virtualbox' are missing 
> for
> buster64 tag 'v10.1.0' from https://app.vagrantup.com/debian/boxes/buster64.
> 
> Unfortunately, this breaks inital setup of debian/buster64 boxes with those
> providers, as many packages from the 10.0.0 apt sources list caches don't 
> exist
> in the archives any longer.
> 
> Cheers
>  jonas
> 

Hi Jonas !

Thanks you for your interest for the Debian Vagrant Boxes.
Unfortunately we don't have point releases for Vagrant Boxes for Buster,
see here for the rationale:
https://lists.debian.org/debian-cloud/2019/09/msg00041.html
Note that LXC boxes are not concerned by this, as they use a different
tooling, and have currently a different maintainer.

The package cache for Base Boxes is anyway always updated, since we
don't rebuild the boxes after every security upgrade which has been
pushed to the archive.

Concerning the package cache, what prevents you from refreshing it
before installing new packages ?
I suppose most provisioning tools support this. For instance for ansible
you can have a package cache refresh by setting update_cache: yes for
the apt module in your yaml manifest.

Emmanuel

-- 
You know an upstream is nice when they even accept m68k patches.
  - John Paul Adrian Glaubitz, Debian OpenJDK maintainer

Bug#945423: duplicity fails tests with Python 3.8

[Matthias Klose]

Package: src:duplicity
Version: 0.8.07-1
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.8

duplicity fails tests with Python 3.8, all architectures:

[...]
testing/unit/test_diffdir.py::DDTest::test_dirdelta_write_sig
  /<>/duplicity/librsync.py:232: DeprecationWarning:
PY_SSIZE_T_CLEAN will be required for '#' formats
eof, len_buf_read, cycle_out = self.sig_maker.cycle(self.buffer)

-- Docs: https://docs.pytest.org/en/latest/warnings.html
= 10 failed, 410 passed, 10 skipped, 2628 warnings in 1288.64 seconds ==
/usr/lib/python3/dist-packages/setuptools/dist.py:472: UserWarning: Normalizing
'0.8.07' to '0.8.7'
  warnings.warn(
make[1]: *** [debian/rules:9: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:5: build-arch] Error 2

Bug#945421: pyside2 ftbfs on mips64el (failing tests)

[Matthias Klose]

Package: src:pyside2
Version: 5.13.2-2
Severity: serious
Tags: sid bullseye ftbfs

pyside2 ftbfs on mips64el (failing tests).


[...]
Total time of whole Python script = 804.31 sec

Traceback (most recent call last):
  File "testrunner.py", line 46, in 
testing.main()
  File "/<>/testing/command.py", line 334, in main
.format(err_crit))
ValueError: At least one failure was not blacklisted and met the criterion
'FAIL! >= 3'
make[1]: *** [debian/rules:61: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:28: build-arch] Error 2

Bug#945422: bowtie2: "imp" Python deprecation warning embedded into bowtie2-inspect(1) manpage

[Chris Lamb]

Package: bowtie2
Version: 2.3.5.1-1
Severity: minor
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

The /usr/share/man/man1/bowtie2-inspect.1.gz manpage contains
the following:

   
/build/bowtie2-pnYCyb/bowtie2-2.3.5.1/debian/bowtie2/usr/bin/bowtie2-inspect:24:
 Depre‐
   cationWarning: the imp module is deprecated in favour of importlib;  see 
 the  module's
   documentation for alternative uses…

Due to this utility using the Python "imp" module. This also makes
the build unreproducible as this embeds the build directory, hence
the usertags.


Best wishes,

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

Bug#945420: symbols file needs adjustments for mipsel and sparc64

[Matthias Klose]

Package: src:libkolabxml
Version: 1.1.6-5
Severity: serious
Tags: sid bullseye ftbfs

The symbols file needs adjustments for mipsel and sparc64, or else the package
will stay in unstable.

Bug#944636: insighttoolkit4: CMake missing files for imported targets

[Bas Couwenberg]

Source: insighttoolkit4
Version: 4.12.2-dfsg1-4+b2
Followup-For: Bug #944636
Control: tags -1 patch

Dear Maintainer,

At least part of the problem is that libminc-dev is only a build dependency and 
not being pulled in via the libinsighttoolkit4-dev dependencies.

This is fixed with the attached patch.

Kind Regards,

Bas
>From 9ec752547bb0319e30437ffa9b6c3ede61d0614c Mon Sep 17 00:00:00 2001
From: Bas Couwenberg 
Date: Sun, 24 Nov 2019 16:48:43 +0100
Subject: Add libminc-dev to libinsighttoolkit4-dev dependencies.


diff --git a/debian/changelog b/debian/changelog
index efa42876..1c776ff2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+insighttoolkit4 (4.13.2-dfsg1-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add libminc-dev to libinsighttoolkit4-dev dependencies.
+
+ -- Bas Couwenberg   Sun, 24 Nov 2019 16:48:06 +0100
+
 insighttoolkit4 (4.13.2-dfsg1-3) unstable; urgency=medium
 
   * d/rules: Fix lintian file generation
diff --git a/debian/control b/debian/control
index 069b9cdb..04cf6295 100644
--- a/debian/control
+++ b/debian/control
@@ -50,7 +50,7 @@ Description: Image processing toolkit for registration and 
segmentation - runtim
 Package: libinsighttoolkit4-dev
 Section: libdevel
 Architecture: amd64 i386
-Depends: ${shlibs:Depends}, ${misc:Depends}, libinsighttoolkit4.13 (= 
${binary:Version}), libgdcm-dev, libdcmtk-dev, libhdf5-dev, 
libdouble-conversion-dev, libexpat-dev, libnifti-dev
+Depends: ${shlibs:Depends}, ${misc:Depends}, libinsighttoolkit4.13 (= 
${binary:Version}), libgdcm-dev, libdcmtk-dev, libhdf5-dev, 
libdouble-conversion-dev, libexpat-dev, libminc-dev, libnifti-dev
 Recommends: libfftw3-dev, uuid-dev
 Conflicts: libinsighttoolkit-dev, libinsighttoolkit3-dev
 Replaces: libinsighttoolkit-dev
diff --git a/debian/control.in b/debian/control.in
index b6d19171..94253560 100644
--- a/debian/control.in
+++ b/debian/control.in
@@ -50,7 +50,7 @@ Description: Image processing toolkit for registration and 
segmentation - runtim
 Package: libinsighttoolkit@VER_MAJOR@-dev
 Section: libdevel
 Architecture: amd64 i386
-Depends: ${shlibs:Depends}, ${misc:Depends}, libinsighttoolkit@SOVERSION@ (= 
${binary:Version}), libgdcm-dev, libdcmtk-dev, libhdf5-dev, 
libdouble-conversion-dev, libexpat-dev, libnifti-dev
+Depends: ${shlibs:Depends}, ${misc:Depends}, libinsighttoolkit@SOVERSION@ (= 
${binary:Version}), libgdcm-dev, libdcmtk-dev, libhdf5-dev, 
libdouble-conversion-dev, libexpat-dev, libminc-dev, libnifti-dev
 Recommends: libfftw3-dev, uuid-dev
 Conflicts: libinsighttoolkit-dev, libinsighttoolkit3-dev
 Replaces: libinsighttoolkit-dev
-- 
2.20.1

Bug#945419: libpillowfight ftbfs on all architectures

[Matthias Klose]

Package: src:libpillowfight
Version: 0.3.0-1
Severity: serious
Tags: sid bullseye ftbfs

libpillowfight ftbfs on all architectures.

amd64:
[...]
dh_install: libpillowfight0 missing files: usr/lib/*/lib*.so.*
dh_install: missing files, aborting
install -d debian/.debhelper/generated/python3-pypillowfight
install -d debian/.debhelper/generated/libpillowfight-dev
install -d debian/.debhelper/generated/libpillowfight0
make: *** [debian/rules:16: binary-arch] Error 255
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

Bug#945376:

[Mateusz Skowroński]

Control: retitle -1 TypeError: 'Shiboken.ObjectType' object is not
iterable on Python 3.8

Bug#945418: RFS: golang-github-sabhiram-go-gitignore/1.0.2-1 [ITP] -- A gitignore parser for go

[Felix Lechner]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: David Steele 

Dear mentors,

I am looking for a sponsor for my package "golang-github-sabhiram-go-gitignore"

This is a required prerequisite for Gocryptfs starting in version
1.7.1, which is currently unpackaged, and up.

 * Package name: golang-github-sabhiram-go-gitignore
   Version : 1.0.2-1
   Upstream Author : Shaba Abhiram 
 * URL : https://github.com/sabhiram/go-gitignore
 * License : MIT
 * Vcs :
https://salsa.debian.org/go-team/packages/golang-github-sabhiram-go-gitignore
   Section : devel

It builds those binary packages:

  golang-github-sabhiram-go-gitignore-dev - A gitignore parser for go

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

  https://mentors.debian.net/package/golang-github-sabhiram-go-gitignore

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

  dget -x 
https://mentors.debian.net/debian/pool/main/g/golang-github-sabhiram-go-gitignore/golang-github-sabhiram-go-gitignore_1.0.2-1.dsc

Changes since the last upload:

   * Initial release (Closes: #945407)

Regards,

--
  Felix Lechner

Bug#945376:

[Mateusz Skowroński]

Control: retitle -1 TypeError: 'Shiboken.ObjectType' object is not
iterable on Python 3.8

Bug#888914: backintime adds current directory to path?

[Fabian Wolff]

Thanks for reporting this bug.

It appears to me that the issue you're referring to might have been fixed by 
this commit:

  
https://github.com/bit-team/backintime/commit/7795b40772c821805037664a559d96642b768391

Could you check again and confirm this, please? Then we could close this bug.

On Wed, 31 Jan 2018 06:18:35 + David Starner  wrote:
> Package:backintime-qt4
> Version:1.1.12-2
> 
> ~/RPG/Mine/Traveller/Traveller_USB $ backintime-qt4 &
> [1] 326
> ~/RPG/Mine/Traveller/Traveller_USB $ sh: 0: getcwd() failed: No such file
> or directory
> sh: 0: getcwd() failed: No such file or directory
> Traceback (most recent call last):
> File "/usr/share/backintime/qt4/app.py", line 46, in 
> import snapshotsdialog
> File "/usr/share/backintime/qt4/snapshotsdialog.py", line 32, in 
> if tools.check_command('meld'):
> File "/usr/share/backintime/common/tools.py", line 167, in check_command
> return not which(cmd) is None
> File "/usr/share/backintime/common/tools.py", line 173, in which
> path.insert(0, os.getcwd())
> FileNotFoundError: [Errno 2] No such file or directory
> 
> [1]+ Exit 1 backintime-qt4
> 
> I'm not going to trying to set up a proof-of-concept security hole with
> this, but it seems quite obvious that backintime-qt4 should not insert the
> current directory into the path for the same reasons that you don't insert
> the current directory into the path in bash. All a user has to do is insert
> the right executables into the current directory and then convince the
> admin to run backintime-qt4 from that directory (and the social part of
> that exploit seems simple enough).
> 
> If nothing else, getting a backtrace from a program is bad, and this would
> leave a non-programmer utterly baffled about what went wrong.

Bug#945417: udd: add more reproducible info

[Lucas Nussbaum]

Package: qa.debian.org
Severity: wishlist
User: qa.debian@packages.debian.org
Usertag: udd

Hi,

UDD uses reproducible-tracker.json instead of reproducible.json. It
should use the latter. DMD should be updated to limit the information it
displays to useful info, as described below.

- Lucas

- Forwarded message from Mattia Rizzolo  -

From: Mattia Rizzolo 
To: Lucas Nussbaum 
Cc: Holger Levsen , debian-de...@lists.debian.org
Date: Fri, 8 Nov 2019 18:50:47 +0100
Subject: Re: archive test rebuilds and reports for bullseye?
Message-ID: <20191108175047.gi24...@mapreri.org>
Mail-Followup-To: Lucas Nussbaum , Holger Levsen 
, debian-de...@lists.debian.org

On Fri, Nov 08, 2019 at 06:37:29PM +0100, Lucas Nussbaum wrote:
> UDD uses
> https://tests.reproducible-builds.org/debian/reproducible-tracker.json,
> but that only includes results for suite='bullseye'. Is that expected?

Yes, it's expected.  reproducible-tracker.json has only the data that is
supposed to be "useful" for maintainers without being distracting.  For
example, it also doesn't show blacklisted packages, or in other weird
states.
If you want all the data, that would be in reproducible.json with a
slight different structure; however in the past many times we received
complaints about unnecessary noise, so if you change I at least urge you
to limit what's displayed in DMD.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-



- End forwarded message -

Bug#945416: libb-cow-perl: fails to build (test failures) on some architectures

[gregor herrmann]

Source: libb-cow-perl
Version: 0.001-2
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As seen on 
https://buildd.debian.org/status/logs.php?pkg=libb-cow-perl=0.001-2
libb-cow-perl has failures in the test suite on various
architectures.

The error is:

#   Failed test 'hash key a cowrefcnt is 0'
#   at t/01-basic.t line 56.
#  got: '1'
# expected: '0'
SV = PV(0x2aa3deb4de0) at 0x2aa3ded7d80
  REFCNT = 2
  FLAGS = (POK,IsCOW,pPOK)
  PV = 0x2aa3e12ded0 "a"
  CUR = 1
  LEN = 0

#   Failed test 'hash key c cowrefcnt is 0'
#   at t/01-basic.t line 56.
#  got: '1'
# expected: '0'
SV = PV(0x2aa3e63ff30) at 0x2aa3e6387f0
  REFCNT = 2
  FLAGS = (POK,IsCOW,pPOK)
  PV = 0x2aa3e63a020 "c"
  CUR = 1
  LEN = 0
# Looks like you failed 2 tests of 23.
t/01-basic.t ... 
ok 1 - can cow with Perl 5.03
ok 2 - !is_cow(undef)
ok 3 - is_cow('abcdef')
ok 4 - cowrefcnt is set to 1
ok 5 - is_cow('abcdef')
ok 6 - cowrefcnt for b is set to 2
ok 7 - cowrefcnt for str is set to 2
ok 8 - cowrefcnt_max: might need to adjust...
ok 9 - b is_cow
ok 10 - c !is_cow
ok 11 - cowrefcnt on uncowed SvPV
ok 12
ok 13
ok 14
ok 15
ok 16
ok 17
ok 18 - cowrefcnt decrease to 100
ok 19 - cowrefcnt decrease to 100
ok 20 - key a is cowed
not ok 21 - hash key a cowrefcnt is 0
ok 22 - key c is cowed
not ok 23 - hash key c cowrefcnt is 0
1..23
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/23 subtests 

Test Summary Report
- ---
t/01-basic.t (Wstat: 512 Tests: 23 Failed: 2)
  Failed tests:  21, 23
  Non-zero exit status: 2
Files=3, Tests=25,  1 wallclock secs ( 0.02 usr  0.00 sys +  0.20 cusr  0.01 
csys =  0.23 CPU)
Result: FAIL


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl3aoNtfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgatvQ//VdHzAs1ODvDNFOuBmOIjl4CSxHwXaXbU8ZP96ROBl/xVCGcemjV4bkjb
tSxlb3UJdvDuGDQPHM7q167ZmYv1ljFXFLELhq5J2Ual/qwQK/yZo/qjH+so8uvU
bWuFB1QD4cHDCbDYSD99UZpHvc1fn5BeB4yVaJ6iccI0R4ZwPJvOLOPqvMZIiPrz
+x0NBsg2jpASDy21I4sQnGVJkjR+IBqschaeIriftYRq4a8JriSp6xKke4O3iUVs
MlVsRQU7kTL6oBxo5zyInq4uaIRlaDf9wiYblSbS8x1Yy5i19zN2x9DjKam4CDVH
+L9wMJJPAvnIWulsyjciVsd8iraQaq39hImqWJ6LbE6cu8qPuoT43qInAUp2MF1F
hCKnazMPxxauQZUBDlt8tBtCvC2st5CqoZROPdGijru90OIVBHU+gIPDQkrlqeiZ
MsAXTK+x8AIzaAlhVp/+JEvX3kh7nQHqUoYeWHGhiMG8MTrIFsOGnhePEVadTo+N
4iVKK4im0CfUxoq1sC7ojjWubelCrxNWwEWz3rt+b8iEbsYnwCe85YO61AyQZhtq
kYS4mCGjpVJ1kRUgQpoQL7yVMu8m5+mEWsTk7+LRr4/7gglldOQ+OMWHnPgKPUve
Qr5cqT+FYbptTvQ41VSbAQAgYZzVfQZqEGt3LCN1eEtJJUM6yfk=
=v/Ew
-END PGP SIGNATURE-

Bug#944589: gsequencer: stalls system

[Joël Krähemann]

Few days ago, someone reported a similar behavior, we figured out that
low CPU power and the use of pulseaudio caused problems.

Does it help if you put a different configuration in your:

$HOME/.gsequencer/ags.conf

As shown here:

http://nongnu.org/gsequencer/help.html

Or see attachment.

regards,
Joël


On Sun, Nov 24, 2019 at 9:44 AM westlake  wrote:
>
> I tested with bpo kernel 5.2.0-0.bpo.3-rt-amd64 and similar issue.
>
> I notice there's a set_schedul* something message along with "operation
> not permitted"... that might provide a hint..
>
> there's no ~/.gsequencer directory made yet, as the stall occurs either
> while still scanning ladspa or lv2 plugins.
>
> The point of the stall is random but it occurs during the plugin-scan..
>
> -- terminal text shows the point that it stalls is random..
>
> Sometimes I am able to do Ctl-c, sometimes not and I need to do a hard
> shutdown (power button)..
>


ags.conf
Description: Binary data

Bug#945415: gitano: FTBFS on unstable

[Antonio Terceiro]

Source: gitano
Version: 1.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hello,

gitano currently fails to build from source under sbuild. the relevant
part of the log is as follows:

8<8<8<-
Running scenario Simple case `gc` usage
DATADIR is /tmp/tmp4j9yNS/Simple_case_gc_usage/datadir
HOME for tests is /tmp/tmp4j9yNS/Simple_case_gc_usage/datadir/HOME
Running step "GIVEN a standard instance"
Running step "WHEN testinstance adminkey runs gc gitano-admin"
Running step "THEN stderr is empty"
ERROR: In scenario "Simple case `gc` usage"
step "THEN stderr is empty" failed,
with exit code 1:
Standard output from shell command:

Standard error from shell command:
+ grep -q . /tmp/tmp4j9yNS/Simple_case_gc_usage/datadir/stderr
+ false
8<8<8<-

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled


gitano-build.log.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#945414: gcr: FTBFS on sparc64 due to 64bit memory access alignment issues

[Gregor Riepl]

Source: gcr
Version: 3.18.0-1
Severity: normal
User: debian-sp...@lists.debian.org
Usertags: sparc64

Dear Maintainer,

The package build of gcr currently fails for the sparc64 architecture due to
misaligned access to 64-bit memory, as can be seen in the build log:
https://buildd.debian.org/status/fetch.php?pkg=gcr=sparc64=3.34.0-1=1571748585=0

The build errors do not directly break the build, but cause unit tests to
crash with a bus error, and will likely make the resulting library unusable.

The root of the problem are constructs like this, where value is a
const guchar * that can have arbitrary alignment:
*result = *((CK_ULONG*)value);

As an easy workaround, this can be replaced by:
memcpy(result, value, sizeof(CK_ULONG));

This will result in safe memory access, and is usualy optimised out by the
compiler, so there is no runtime cost.

I'm working on a patch that does this for all such constructs.

Regards,
Greg

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

Kernel: Linux 5.3.0-2-sparc64
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#945413: fast-histogram fails it's tests during the build

[Matthias Klose]

Package: src:fast-historgram
Version: 0.7-1
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.8

I: pybuild base:217: cd
/<>/.pybuild/cpython3_3.8_fast-histogram/build; python3.8 -m pytest
= test session starts ==
platform linux -- Python 3.8.0+, pytest-4.6.6, py-1.8.0, pluggy-0.13.0
hypothesis profile 'default' ->
database=DirectoryBasedExampleDatabase('/<>/.pybuild/cpython3_3.8_fast-histogram/build/.hypothesis/examples')
rootdir: /<>
plugins: hypothesis-4.36.2
collected 6 items

fast_histogram/tests/test_histogram.py FF[100%]

=== FAILURES ===
__ test_1d_compare_with_numpy __

@given(size=st.integers(0, 100),
>  nx=st.integers(1, 10),
   xmin=st.floats(-1e10, 1e10), xmax=st.floats(-1e10, 1e10),
   weights=st.booleans(),
   dtype=st.sampled_from(['>f4', 'f8', 'f4', shape=0, elements=floats(min_value=-1000,
max_value=1000))
random = not_set

def example(self, random=not_set):
# type: (UniqueIdentifier) -> Ex
"""Provide an example of the sort of value that this strategy
generates. This is biased to be slightly simpler than is typical for
values from this strategy, for clarity purposes.

This method shouldn't be taken too seriously. It's here for interactive
exploration of the API, not for any sort of real testing.

This method is part of the public API.
"""
if random is not not_set:
note_deprecation("The random argument does nothing", 
since="2019-07-08")

context = _current_build_context.value
if context is not None:
if context.data is not None and context.data.depth > 0:
raise HypothesisException(
"Using example() inside a strategy definition is a bad "
"idea. Instead consider using 
hypothesis.strategies.builds() "
"or @hypothesis.strategies.composite to define your 
strategy."
" See https://hypothesis.readthedocs.io/en/latest/data.html;
"#hypothesis.strategies.builds or "
"https://hypothesis.readthedocs.io/en/latest/data.html;
"#composite-strategies for more details."
)
else:
>   raise HypothesisException(
"Using example() inside a test function is a bad "
"idea. Instead consider using hypothesis.strategies.data() "
"to draw more examples during testing. See "
"https://hypothesis.readthedocs.io/en/latest/data.html;
"#drawing-interactively-in-tests for more details."
)
E   hypothesis.errors.HypothesisException: Using example() inside a
test function is a bad idea. Instead consider using hypothesis.strategies.data()
to draw more examples during testing. See
https://hypothesis.readthedocs.io/en/latest/data.html#drawing-interactively-in-tests
for more details.

/usr/lib/python3/dist-packages/hypothesis/searchstrategy/strategies.py:284:
HypothesisException
-- Hypothesis --
Falsifying example: test_1d_compare_with_numpy(size=0, nx=1,
xmin=-2.2204460492503135e-06, xmax=0.0, weights=False, dtype='>f4')
__ test_2d_compare_with_numpy __

>   ???

fast_histogram/tests/test_histogram.py:66:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/hypothesis/core.py:326: in 
execute_explicit_examples
test_runner(None, lambda data: test(*arguments, **example_kwargs))
/usr/lib/python3/dist-packages/hypothesis/executors.py:56: in
default_new_style_executor
return function(data)
/usr/lib/python3/dist-packages/hypothesis/core.py:326: in 
test_runner(None, lambda data: test(*arguments, **example_kwargs))
fast_histogram/tests/test_histogram.py:81: in test_2d_compare_with_numpy
x = arrays(dtype, size, elements=st.floats(-1000, 1000)).example()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = arrays(dtype=' Ex
"""Provide an example of the sort of value that this strategy
generates. This is biased to be slightly simpler than is typical for
values from this strategy, for clarity purposes.

This method shouldn't be taken too seriously. It's here for interactive
exploration of the API, not for any sort of real testing.

This method is part of the public API.
"""
if random is not not_set:
note_deprecation("The random argument does nothing", 
since="2019-07-08")

context = _current_build_context.value
if context