Bug#960065: Please put this on hold
> > This does not affect the rest of open-vm-tools 11.1.0 , so the update can > go ahead without the plugin. Note that it's not built by default. > https://salsa.debian.org/vmware-packaging-team/pkg-open-vm-tools/-/merge_requests/6 is a PR dropping sdmp for now
Bug#870641: Solved?
I have been struggling for a long time with a laptop sometimes not waking up after sleep. I read some stuff here and indeed strange this bug is still there. I just installed LightDM 1.30, but as I don't fully understand the problem I am not sure if that would solve the problem. Pressing keys (CTRL-FX) and such doesn't seem to help, as some people sugget. I am happy to help, but as said, I don't fully understand the problem where I saw some people do.
Bug#960715: cunit: diff for NMU version 2.1-3-dfsg-2.1
Control: tags 960715 + patch Control: tags 960715 + pending Dear maintainer, I've prepared an NMU for cunit (versioned as 2.1-3-dfsg-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer or cancel the NMU. Regards, Regis Fernandes Gontijo --- cunit-2.1-3-dfsg/debian/changelog 2015-12-26 22:22:24.0 + +++ cunit-2.1-3-dfsg/debian/changelog 2020-06-08 04:49:43.0 + @@ -1,3 +1,13 @@ +cunit (2.1-3-dfsg-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/tests/: (Closes: #960715) + - control: set 'Depends: gcc' because autopkgtest needs to build +a binary to run the CI test. + - test.sh: fixed gcc build command. + + -- Regis Fernandes Gontijo Mon, 08 Jun 2020 04:49:43 + + cunit (2.1-3-dfsg-2) unstable; urgency=medium * Remove doc/headers/*.h, since they will be generated from CUnit/Headers @@ -137,4 +147,3 @@ * Initial release (Closes: #293009) -- Philipp Benner Mon, 18 Sep 2006 19:58:21 +0200 - diff -Nru cunit-2.1-3-dfsg/debian/tests/control cunit-2.1-3-dfsg/debian/tests/control --- cunit-2.1-3-dfsg/debian/tests/control 2015-10-12 20:15:36.0 + +++ cunit-2.1-3-dfsg/debian/tests/control 2020-06-08 04:49:43.0 + @@ -1,3 +1,3 @@ Tests: test.sh -Depends: +Depends: gcc Restrictions: build-needed diff -Nru cunit-2.1-3-dfsg/debian/tests/test.sh cunit-2.1-3-dfsg/debian/tests/test.sh --- cunit-2.1-3-dfsg/debian/tests/test.sh 2015-10-12 20:15:36.0 + +++ cunit-2.1-3-dfsg/debian/tests/test.sh 2020-06-08 04:49:43.0 + @@ -4,6 +4,6 @@ LIB="$(echo "$PWD/$d"/usr/lib/*)" INC="$PWD/$d/usr/include" -gcc -Wall -L"$LIB" -I"$INC" -lcunit -o "$ADTTMP/test" debian/tests/test.c +gcc debian/tests/test.c -Wall -L"$LIB" -I"$INC" -lcunit -o "$ADTTMP/test" LD_LIBRARY_PATH="$LIB" "$ADTTMP/test" done
Bug#960636: deb-why-removed is very slow
Package: devscripts
Version: 2.20.3
Followup-For: Bug #960636
In addition to the speed of parsing the file, it could download less
data by using the per-year indexes. Also getting compressed indexes on
ftp-master would be good. Adding a removals API to dak would be best.
$ rm -rf ~/.cache/devscripts/deb-why-removed ; time deb-why-removed nsntrace
Date: Sun, 01 Sep 2019 19:27:26 +
Ftpmaster: Scott Kitterman
Suite: unstable
Sources:
nsntrace_0~20160806-1
Binaries:
nsntrace_0~20160806-1+b1 [amd64, arm64, armel, armhf, i386, mips64el, mipsel,
ppc64el, s390x]
Reason: dead upstream, FTBFS with GCC 9
Bug: 939086
Also-Bugs: 832268 835485 925789
real0m29.239s
user0m17.186s
sys 0m1.534s
$ rm -rf ~/.cache/devscripts/deb-why-removed ; time bash -c 'deb-why-removed
--url https://ftp-master.debian.org/removals.822 nsntrace
for y in {2019..2001} ; do
if deb-why-removed --url https://ftp-master.debian.org/removals-$y.822
nsntrace | grep . ; then
break
fi
done'
Date: Sun, 01 Sep 2019 19:27:26 +
Ftpmaster: Scott Kitterman
Suite: unstable
Sources:
nsntrace_0~20160806-1
Binaries:
nsntrace_0~20160806-1+b1 [amd64, arm64, armel, armhf, i386, mips64el, mipsel,
ppc64el, s390x]
Reason: dead upstream, FTBFS with GCC 9
Bug: 939086
Also-Bugs: 832268 835485 925789
real0m9.803s
user0m2.534s
sys 0m0.070s
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Bug#962513: RFS: gexiv2/0.12.1-1 -- GObject-based wrapper around the Exiv2 library
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "gexiv2" * Package name: gexiv2 Version : 0.12.1-1 Upstream Author : gexiv2-l...@gnome.org * URL : https://wiki.gnome.org/Projects/gexiv2 * License : GPL-2+ * Vcs : https://salsa.debian.org/debian/gexiv2 Section : libs It builds those binary packages: libgexiv2-2 - GObject-based wrapper around the Exiv2 library gir1.2-gexiv2-0.10 - GObject-based wrapper around the Exiv2 library - introspection data libgexiv2-dev - GObject-based wrapper around the Exiv2 library - development files libgexiv2-doc - GObject-based wrapper around the Exiv2 library - documentation To access further information about this package, please visit the following URL: https://mentors.debian.net/package/gexiv2 Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/gexiv2/gexiv2_0.12.1-1.dsc Changes since the last upload: * Update d/copyright * Remove python2 dependency. Remove the override file for the python2 bindings because python2 support is being phased out. (Closes: #943093, #960711) * Update symbols * Remove "-Wl,--as-needed" linker flag. The bullseye toolchain defaults to linking with as-needed so this is no longer necessary. * Update debhelper-compat to 13 Regards, -- Jason Crain
Bug#959842: tweeper: warnings with Facebook: Attribute data-referrer redefined in Entity
On Tue, 2020-06-09 at 00:17 +0200, Antonio Ospite wrote: > For now the code is in the master branch on: > > https://git.ao2.it/tweeper.git/ > > I still need to fix a couple of issues and then I'll update the > Debian package in the next few days. Great, thanks for your work :) -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#962478: [Pkg-fonts-devel] Bug#962478: fonts-firacode: Provide TTF instead of OTF font files. The former embed hinting instructions and thus are rendered sharper on (low-res) screens.
On Mon, Jun 8, 2020 at 3:03 PM Salim B wrote: > The FiraCode author explicitly states[1]: > > > I think at some point OTF was superior to TTF, but now they are mostly the > > same. The difference between OTF and TTF is that TTF can embed hinting > > instructions, which are essential for rendering on low-res displays. > > Therefore I think it would *really* make sense to switch to the TTF variant > of the font since it's mainly intended for "on-screen" usage anyway (in > contrast to print) and thus sharp rendering is very important. Pango/HarfBuzz is dropping support for low-res displays and hinting so I'm not sure how useful this is. https://lwn.net/Articles/821016/ https://www.phoronix.com/scan.php?page=news_item=HarfBuzz-Hinting-Woe https://gitlab.gnome.org/GNOME/pango/issues/463 https://github.com/harfbuzz/harfbuzz/issues/2394 -- bye, pabs https://wiki.debian.org/PaulWise
Bug#934160: Bug#962254: NFS(v4) broken at 4.19.118-2
Control: tags 962254 +security -unreproducible Control: severity 962254 grave On Fri, Jun 05, 2020 at 08:36:31PM +0200, Salvatore Bonaccorso wrote: > This now let some rings bell, the described scenario is very similar > to what was reported in https://bugs.debian.org/934160 > > Respectively > https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1779736 and > https://bugzilla.redhat.com/show_bug.cgi?id=1667761 . Upon more experimentation I continue to favor this being a kernel bug (src:linux, bug #962254) and not a bug with nfs-common. Setting vers=4.1 works around the issue, so this is *strictly* NFSv4.2. I was able to reproduce this issue on a system with nfs-common 1:1.3.4-2.1 and a 4.19.118-2 kernel. Based upon what I've observed I believe this requires a recent kernel on *both* NFS client and NFS server. A NFS client with 4.9 connecting to a NFS server with 4.19 does NOT experience this issue. I suspect my earlier assessment of this appearing between 4.19.98-1 and 4.19.118-2 was erroneous. I think I was mislead by the order of computers being updated, and a NFS client with 4.19 connecting to a NFS server with 4.9 also does not experience this issue. >From https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1779736 this bug appeared somewhere between Linux kernels 4.9 and 4.15. I concur with John Goerzen's assessment of this qualifying as grave due to its security implications. -- (\___(\___(\__ --=> 8-) EHM <=-- __/)___/)___/) \BS (| ehem+sig...@m5p.com PGP 87145445 |) / \_CS\ | _ -O #include O- _ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
Bug#962512: nethack: Security issues in Buster's nethack 3.6.1
Source: nethack Severity: grave Tags: security Justification: user security hole Dear Maintainer, Debian 10 (Buster) currently uses nethack 3.6.1. The website for nethack at https://nethack.org/security/index.html shows security issues have resulted in multiple (up to now 5) point releases fixing things like buffer overflow vulnerabilities, including some that can lead to escalation of privileges. The upstream maintainers recommend "upgrade as soon as possible" for many of the CVE documented issues. Seems like the vunerabilities are important enough to warrant an upgrade in Buster. -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-9-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#962511: New upstream release
Package: calcurse Severity: wishlist Version 4.6.0 (2020-03-27) -- Martin Michlmayr https://www.cyrius.com/
Bug#962510: postgresql-filedump: autopkgtest fails on big endian
Source: postgresql-filedump
Version: 12.0-2
Severity: normal
Tags: patch
Dear Maintainer,
I don't think Debian currently runs autopkgtests on any big endian
architecture but Ubuntu does (on s390x) and the postgresql-filedump
tests fail. On inspection this is because the tests use an include
pg_dump file, and those are endian dependent. I've uploaded the attached
patch to Ubuntu, which just skips the test on a big endian system.
Cheers,
mwh
-- System Information:
Debian Release: bullseye/sid
APT prefers focal-updates
APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'),
(400, 'focal-proposed'), (100, 'focal-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.4.0-33-generic (SMP w/8 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
diff -Nru postgresql-filedump-12.0/debian/changelog
postgresql-filedump-12.0/debian/changelog
--- postgresql-filedump-12.0/debian/changelog 2019-11-29 23:53:23.0
+1300
+++ postgresql-filedump-12.0/debian/changelog 2020-06-09 12:12:25.0
+1200
@@ -1,3 +1,9 @@
+postgresql-filedump (12.0-2ubuntu1) groovy; urgency=medium
+
+ * d/tests/installcheck: skip test on big endian systems.
+
+ -- Michael Hudson-Doyle Tue, 09 Jun 2020
12:12:25 +1200
+
postgresql-filedump (12.0-2) unstable; urgency=medium
* tests: Depend on postgresql-server-dev-all for pg_config.
diff -Nru postgresql-filedump-12.0/debian/control
postgresql-filedump-12.0/debian/control
--- postgresql-filedump-12.0/debian/control 2019-11-29 23:53:23.0
+1300
+++ postgresql-filedump-12.0/debian/control 2020-06-09 12:12:25.0
+1200
@@ -1,7 +1,8 @@
Source: postgresql-filedump
Section: database
Priority: optional
-Maintainer: Debian PostgreSQL Maintainers
+Maintainer: Ubuntu Developers
+XSBC-Original-Maintainer: Debian PostgreSQL Maintainers
Uploaders: Michael Meskes , Christoph Berg
Build-Depends: debhelper (>= 9), postgresql-server-dev-all
Standards-Version: 4.4.0
diff -Nru postgresql-filedump-12.0/debian/tests/installcheck
postgresql-filedump-12.0/debian/tests/installcheck
--- postgresql-filedump-12.0/debian/tests/installcheck 2019-11-29
03:07:20.0 +1300
+++ postgresql-filedump-12.0/debian/tests/installcheck 2020-06-09
12:12:15.0 +1200
@@ -1,5 +1,11 @@
#!/bin/sh
+if [ $(lscpu | grep "Byte Order" | awk '{ print $3; }') = "Big" ]; then
+# The testdata is a dump file generated on a little endian system
+# and dump files are endian-dependent.
+exit 0
+fi
+
if ! pg_virtualenv make installcheck; then
cat regression.diffs
exit 1
Bug#962497: r-base breaks r-cran-data.table autopkgtest: 'origin' must be supplied
As a follow-up, I may have found the one commit for fixing the "'origin' must be supplied" issue (from reading the upstream NEWS [1] backwards landing at #4428 [2] Dirk [1] https://rdatatable.gitlab.io/data.table/news/index.html [2] https://github.com/Rdatatable/data.table/pull/4428 -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#951667: src:check: fails to migrate to testing for too long
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, At Wed, 03 Jun 2020, maintainer made a new upload[0], that should close this bug. [0] https://tracker.debian.org/news/1148171/accepted-check-0120-02-source-into-unstable/ cheers - -- Daniel Lenharo de Souza Curitiba - Brasil -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEMdgFCUYO+zHfS5Yp+w4TLdsKpbEFAl7evv8ACgkQ+w4TLdsK pbEf/xAAl/9yz3092fO48ar6bx/kjcDuBvaQDwnTsYPXRUMokm0cLR+QtvASehIg Vfjc3u9FIHwaEYekOO8QlyKV7hJPs7VUbOjZ16EJUANKRLs+PV2HXv3Ws7dRMryD sOX5fm4NRQqJ5Kmbi8aEgEPxKOZpOnBBgcHFeqdLijCD8Uradbtbcirid539wGMi 2kxIWVmm5MJ6rUjtflbcOVfvstgP+VbecSoO/4flT+IhcFia1TeF60BKfSX19lCh hX/Dk7NVFbmJUSLN9edAUoazI2vLRpAs8pJX5DJx7HIkKAZsqmsateCq2ge0/aou Lty8Ks3r6ijZ7JOe48RgkrqJwd+NAPvNFqzP4JQKNa8cFIfyqHC4sLSjcnQrElRw 9DuF+69qUqgSE/Fi2N8A5P7AXHmu9LNN8ilDsQzQgoWpcXq6ATjqpAzZ3fUlKr/i m8q2tKAbmIO+VFXMBHOxp0h3agI5RiU8epd1Gm5c0ikNk7l5loHptWmYJlAFsDkZ qcYNFgYdyrF61nIgO+2V8sbeRBt0EIoOlUhUzUIOu2mQr9N9E8Uy09fl+xoIaKos Sv4EhpzhWwC6IwLXwIBuBKrntD3GJOIIOhdLbKIzda00MjsidhELmZ0yeYKiqfLl rFr3Lr1za3emqR4O4DVNCeTnNG+hBVmqaAHuU9q8hxwnDwNZTWQ= =ohN9 -END PGP SIGNATURE-
Bug#930543: chromium-driver: Will not start browser if a newer chrome is installed
I have this problem on my workstation as well. Here's the error message this time around: selenium.common.exceptions.SessionNotCreatedException: Message: session not created: This version of ChromeDriver only supports Chrome version 81 I fixed it by adding an alternative with a higher priority for chromium: # update-alternatives --install /etc/alternatives/google-chrome google-chrome /usr/bin/chromium 500
Bug#962509: Not always boot arguments must include a root= parameter
Package: initramfs-tools Version: 0.133+deb10u1 Hi, after the change introduced in f8ceeb90 both zfs and http booting methods are not working anymore, it stops on the message: No root device specified. Boot arguments must include a root= parameter. See the related issues: - https://forum.proxmox.com/threads/zfs-boot-stuck-at-initramfs-no-root-device-specified.64147/ - https://askubuntu.com/questions/1211769/how-do-i-fix-initramfs-not-finding-root - https://forum.proxmox.com/threads/proxmox-will-not-boot-from-zfs-uefi-mode-no-root-device-specified.63752/ The mentioned commit: https://salsa.debian.org/kernel-team/initramfs-tools/-/commit/f8ceeb90abeeb5e84eff950b39d397b4570be2db - kvaps
Bug#962508: switch libcurl to openssl by default
Package: cargo Version: 0.43.1-3 Severity: wishlist Hello fellow Rustaceans! Because cargo has a direct dependency on OpenSSL, it seems logical that we should switch the priority of openssl and gnutls so Cargo, at least by default, isn't building against two different TLS implementations. This is especially important considering GnuTLS has had some painful security incidents recently: CVE-2020-13777 in particular. Should just require switching the order of the libcurl dep in d/control. Sincerely, -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-2-amd64 (SMP w/4 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 cargo depends on: ii binutils2.34-8 ii gcc [c-compiler]4:9.2.1-3.1 ii gcc-8 [c-compiler] 8.4.0-4 ii gcc-9 [c-compiler] 9.3.0-13 ii libc6 2.30-8 ii libcurl3-gnutls 7.68.0-1 ii libgcc-s1 10.1.0-1 ii libgit2-28 0.28.5+dfsg.1-1 ii libssh2-1 1.8.0-2.1 ii libssl1.1 1.1.1g-1 ii rustc 1.42.0+dfsg1-1 ii zlib1g 1:1.2.11.dfsg-2 cargo recommends no packages. Versions of packages cargo suggests: pn cargo-doc ii python33.8.2-3 -- no debconf information
Bug#958156: slic3r: diff for NMU version 1.3.0+dfsg1-3.1
Control: tags 958156 + pending
Dear maintainer,
I've prepared an NMU for slic3r (versioned as 1.3.0+dfsg1-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru slic3r-1.3.0+dfsg1/debian/changelog slic3r-1.3.0+dfsg1/debian/changelog
--- slic3r-1.3.0+dfsg1/debian/changelog 2018-11-08 12:19:10.0 +0100
+++ slic3r-1.3.0+dfsg1/debian/changelog 2020-06-09 00:34:00.0 +0200
@@ -1,3 +1,12 @@
+slic3r (1.3.0+dfsg1-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Giovanni Mascellani ]
+ * Fix FTBFS with Boost 1.71. (Closes: #958156)
+
+ -- Sebastian Ramacher Tue, 09 Jun 2020 00:34:00 +0200
+
slic3r (1.3.0+dfsg1-3) unstable; urgency=medium
* [b61cf9b] Import patch to fix admesh compilation bug (Closes: #907346)
diff -Nru slic3r-1.3.0+dfsg1/debian/patches/0006-Fix-FTBFS-with-Boost-1.71.patch slic3r-1.3.0+dfsg1/debian/patches/0006-Fix-FTBFS-with-Boost-1.71.patch
--- slic3r-1.3.0+dfsg1/debian/patches/0006-Fix-FTBFS-with-Boost-1.71.patch 1970-01-01 01:00:00.0 +0100
+++ slic3r-1.3.0+dfsg1/debian/patches/0006-Fix-FTBFS-with-Boost-1.71.patch 2020-06-09 00:33:58.0 +0200
@@ -0,0 +1,20 @@
+From: Giovanni Mascellani
+Date: Sun, 19 Apr 2020 08:31:04 +0200
+Subject: Fix FTBFS with Boost 1.71.
+
+---
+ xs/src/libslic3r/GCodeSender.hpp | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/xs/src/libslic3r/GCodeSender.hpp b/xs/src/libslic3r/GCodeSender.hpp
+index cc0b298..0f39f5a 100644
+--- a/xs/src/libslic3r/GCodeSender.hpp
b/xs/src/libslic3r/GCodeSender.hpp
+@@ -9,6 +9,7 @@
+ #include
+ #include
+ #include
++#include
+
+ namespace Slic3r {
+
diff -Nru slic3r-1.3.0+dfsg1/debian/patches/series slic3r-1.3.0+dfsg1/debian/patches/series
--- slic3r-1.3.0+dfsg1/debian/patches/series 2018-11-08 12:19:10.0 +0100
+++ slic3r-1.3.0+dfsg1/debian/patches/series 2020-06-09 00:33:58.0 +0200
@@ -3,3 +3,4 @@
Add-usr-lib-slic3r-to-lib-search-path.patch
Use-system-expat.h.patch
Drop-error-admesh-works-correctly-on-little-endian-machin.patch
+0006-Fix-FTBFS-with-Boost-1.71.patch
signature.asc
Description: PGP signature
Bug#948207: kio-gdrive: New Google drive authorisation fail with stable package
Package: kio-gdrive Version: 1.2.5+fixedtarball-1 Followup-For: Bug #948207 Dear Maintainer, I just discovered this bug by reading this opened subject. I requested an new authorization thanks to google account security website and the problem appeared indicating that Google need to validate this app The actual stable revision package of kio-gdrive and kaccounts-integration need maybe to be upgraded according this discussion where i see that a fix is available (requiring unstable packages unfortunately: 19.x). Debian stable buster is using for information. Thanks. -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kio-gdrive depends on: ii kaccounts-integration 4:17.08.3-1 ii kio5.54.1-1 ii libaccounts-qt5-1 1.15-2 ii libc6 2.28-10 ii libkaccounts1 4:17.08.3-1 ii libkf5coreaddons5 5.54.0-1 ii libkf5i18n55.54.0-1 ii libkf5kiocore5 5.54.1-1 ii libkf5kiowidgets5 5.54.1-1 ii libkf5notifications5 5.54.0-1 ii libkpimgapicore5abi1 18.08.3-2 ii libkpimgapidrive5 18.08.3-2 ii libqt5core5a 5.11.3+dfsg1-1+deb10u3 ii libqt5widgets5 5.11.3+dfsg1-1+deb10u3 ii libstdc++6 8.3.0-6 kio-gdrive recommends no packages. kio-gdrive suggests no packages. -- no debconf information
Bug#956018: iptables-converter: diff for NMU version 0.9.8-1.2
Control: tags 956018 + patch Control: tags 956018 + pending Dear maintainer, I've prepared an NMU for iptables-converter (versioned as 0.9.8-1.2) and uploaded it to mentors for sponsoring. Please feel free to tell me if I should remove it. -- Regards Sudip diff -Nru iptables-converter-0.9.8/debian/changelog iptables-converter-0.9.8/debian/changelog --- iptables-converter-0.9.8/debian/changelog 2020-03-22 12:01:11.0 + +++ iptables-converter-0.9.8/debian/changelog 2020-06-08 23:50:33.0 +0100 @@ -1,3 +1,11 @@ +iptables-converter (0.9.8-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Source only upload. (Closes: #956018) +- No change in source. + + -- Sudip Mukherjee Mon, 08 Jun 2020 23:50:33 +0100 + iptables-converter (0.9.8-1.1) unstable; urgency=medium * Non-maintainer upload.
Bug#962507: RFS: iptables-converter/0.9.8-1.2 [NMU, RC] -- convert iptables-commands from a file to iptables-save format
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "iptables-converter" * Package name: iptables-converter Version : 0.9.8-1.2 Upstream Author : Johannes Hubertz * URL : https://github.com/sl0/conv.git * License : GPL-3+ * Vcs : None Section : utils It builds those binary packages: iptables-converter - convert iptables-commands from a file to iptables-save format iptables-converter-doc - convert iptables-commands from a file to iptables-save format - doc To access further information about this package, please visit the following URL: https://mentors.debian.net/package/iptables-converter Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/i/iptables-converter/iptables-converter_0.9.8-1.2.dsc Changes since the last upload: * Non-maintainer upload. * Source only upload. (Closes: #956018) - No change in source. -- Regards Sudip
Bug#962506: grub: grub-install puts wrong partition to `load.cfg`
Dear Debian folks, Am 09.06.20 um 00:40 schrieb Paul Menzel: Package: grub-efi Version: 2.04-8 Severity: normal The x86 Dell system with UEFI firmware has the partitions below, where the first one is the ESP (and /boot), and the second one is encrypted with LUKS. $ lsblk -o NAME,UUID,LABEL,PTTYPE NAME UUID LABEL PTTYPE nvme0n1 gpt ├─nvme0n1p1 D34D-47A3 ESP gpt └─nvme0n1p2 b88be798-13e3-4884-9748-bf7a23f0ae87 gpt └─nvme0n1p2_crypt c9342a55-b747-4442-b2f4-bc03eb7a51cf With Debian Sid/unstable, the wrong partition UUID is put into `load.cfg`. $ sudo grub-install -v […] grub-install: info: grub-mkimage --directory '/usr/lib/grub/x86_64-efi' --prefix '/boot/grub' --output '/boot/grub/x86_64-efi/core.efi' --dtb '' --format 'x86_64-efi' --compression 'auto' --config '/boot/grub/x86_64-efi/load.cfg' 'ext2' 'search_fs_uuid' […] $ more /boot/grub/x86_64-efi/load.cfg search.fs_uuid c9342a55-b747-4442-b2f4-bc03eb7a51cf root set prefix=($root)'/boot/grub' GRUB then says, it can’t find c9342a55-b747-4442-b2f4-bc03eb7a51cf and drops into rescue mode. For whatever reason, the partitions are not detected, and GRUB only sees `(hd0)`. Of course, no modules can be loaded, and I am unable to check what modules are loaded.a `grub-install --boot-directory=/boot --efi-directory /boot/efi` doesn’t make a difference either. $ sudo strings /boot/efi/EFI/debian/grubx64.efi | grep gpt $ sudo strings /boot/efi/EFI/debian/grubx64.efi | grep -C 3 c93 .module_license .bss .modname search.fs_uuid c9342a55-b747-4442-b2f4-bc03eb7a51cf root set prefix=($root)'/boot/grub' /boot/grub Interestingly, starting a live system, like Grml (daily), chroot’ing into the system `/mnt` (with `/dev/nvme0n1p1` mounted under `/mnt/boot/`), running `grub-install --efi-directory /boot/efi` creates a working image. $ sudo strings /boot/efi/EFI/debian-backup/grubx64.efi | grep gpt partmap/gpt.c part_gpt grub_gpt_partition_map_iterate (,gpt1)/grub Please find the verbose output attached. That was for the non-working case with the installed Debian Sid/unstable. Kind regards, Paul
Bug#955581: xmms2: diff for NMU version 0.8+dfsg-18.3
Control: tags 955581 + patch Dear maintainer, I've prepared an NMU for xmms2 (versioned as 0.8+dfsg-18.3). The diff is attached to this message. Cheers -- Sebastian Ramacher diff -Nru xmms2-0.8+dfsg/debian/changelog xmms2-0.8+dfsg/debian/changelog --- xmms2-0.8+dfsg/debian/changelog 2019-02-25 08:12:48.0 +0100 +++ xmms2-0.8+dfsg/debian/changelog 2020-06-09 00:19:53.0 +0200 @@ -1,3 +1,10 @@ +xmms2 (0.8+dfsg-18.3) unstable; urgency=medium + + * Non-maintainer upload. + * Remove liboost-signals-dev from Build-Depends. (Closes: #955581) + + -- Sebastian Ramacher Tue, 09 Jun 2020 00:19:53 +0200 + xmms2 (0.8+dfsg-18.2) unstable; urgency=high * Non-maintainer upload. diff -Nru xmms2-0.8+dfsg/debian/control xmms2-0.8+dfsg/debian/control --- xmms2-0.8+dfsg/debian/control 2019-02-25 08:12:48.0 +0100 +++ xmms2-0.8+dfsg/debian/control 2020-06-09 00:17:02.0 +0200 @@ -12,7 +12,6 @@ libavahi-glib-dev, libavcodec-dev (>= 6:10~), libboost-dev, - libboost-signals-dev, libcdio-cdda-dev, libcurl4-openssl-dev, libdiscid-dev, signature.asc Description: PGP signature
Bug#959842: tweeper: warnings with Facebook: Attribute data-referrer redefined in Entity
On Mon, 11 May 2020 11:14:06 +0800 Paul Wise wrote: > On Mon, 2020-05-11 at 00:26 +0200, Antonio Ospite wrote: > > > these warnings are kind of expected, it's the PHP XML parser which > > tells that the document may not be 100% standard compliant. > > I see, that seems reasonable I guess. > > > If they are too distracting maybe I can add a verbose option and silence > > them by default. I am the upstream too. > > For compatibility with scripts that may be using those warnings in some > way, I would instead add an option to silence the warnings. > I added a '-v <0|1>' option to tweeper that can be used to silence the verbose output, you can pass '-v 0' to disable the ouptut of those XML validation errors. I also restored some support for scraping twitter.com which stopped working after the twitter UI update from June 1st 2020. For now the code is in the master branch on: https://git.ao2.it/tweeper.git/ I still need to fix a couple of issues and then I'll update the Debian package in the next few days. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#955531: llvm-10-toolchain: mesa/intel-opencl-clang fails to build with llvm-10: undefined reference to `getPollyPluginInfo()'
Package: libllvm10 Version: 1:10.0.0-4 Followup-For: Bug #955531 I started seeing the same issue today when trying to compile Mesa master: Debian, amd64, testing. This started maybe today or yesterday, as it was working find for me before that: ``` [1461/1469] Linking target src/gallium/targets/opencl/libMesaOpenCL.so.1.0.0 FAILED: src/gallium/targets/opencl/libMesaOpenCL.so.1.0.0 /usr/bin/x86_64-linux-gnu-g++-9 -o src/gallium/targets/opencl/libMesaOpenCL.so.1.0.0 -Wl,--as-needed -Wl,--no-undefined -shared -fPIC -Wl,--start-group -Wl,-soname,libMesaOpenCL.so.1 -Wl,--whole-archive src/gallium/state_trackers/clover/libclover.a -Wl,--no-whole-archive src/gallium/auxiliary/pipe-loader/libpipe_loader_dynamic.a src/loader/libloader.a src/util/libxmlconfig.a src/util/libmesa_util.a src/util/format/libmesa_format.a src/gallium/auxiliary/libgallium.a src/compiler/nir/libnir.a src/compiler/libcompiler.a src/gallium/state_trackers/clover/libclllvm.a src/gallium/state_trackers/clover/libclspirv.a src/gallium/state_trackers/clover/libclnir.a -Wl,--gc-sections -Wl,--version-script /home/user/mesa-git/src/gallium/targets/opencl/opencl.sym /usr/lib/x86_64-linux-gnu/libz.so -pthread -lm -ldl /usr/lib/x86_64-linux-gnu/libunwind.so /usr/lib/x86_64-linux-gnu/libelf.so /usr/lib/llvm-10/lib/libclangCodeGen.a /usr/lib/llvm-10/lib/libclangFrontendTool.a /usr/lib/llvm-10/lib/libclangFrontend.a /usr/lib/llvm-10/lib/libclangDriver.a /usr/lib/llvm-10/lib/libclangSerialization.a /usr/lib/llvm-10/lib/libclangParse.a /usr/lib/llvm-10/lib/libclangSema.a /usr/lib/llvm-10/lib/libclangAnalysis.a /usr/lib/llvm-10/lib/libclangAST.a /usr/lib/llvm-10/lib/libclangASTMatchers.a /usr/lib/llvm-10/lib/libclangEdit.a /usr/lib/llvm-10/lib/libclangLex.a /usr/lib/llvm-10/lib/libclangBasic.a /usr/lib/x86_64-linux-gnu/libdrm.so /usr/lib/x86_64-linux-gnu/libexpat.so -L/usr/lib/llvm-10/lib -lLLVM-10 -lsensors -L/usr/lib/llvm-10/lib -lLLVM-10 /usr/lib/libLLVMSPIRVLib.so /usr/lib/x86_64-linux-gnu/libSPIRV-Tools-opt.a /usr/lib/x86_64-linux-gnu/libSPIRV-Tools.a /usr/lib/x86_64-linux-gnu/libSPIRV-Tools-link.a -Wl,--end-group '-Wl,-rpath,$ORIGIN/../../auxiliary/pipe-loader:$ORIGIN/../../../loader:$ORIGIN/../../../util:$ORIGIN/../../../util/format:$ORIGIN/../../auxiliary:$ORIGIN/../../../compiler/nir:$ORIGIN/../../../compiler' -Wl,-rpath-link,/home/user/mesa-git/builddir/build-amd64-opt/src/gallium/auxiliary/pipe-loader -Wl,-rpath-link,/home/user/mesa-git/builddir/build-amd64-opt/src/loader -Wl,-rpath-link,/home/user/mesa-git/builddir/build-amd64-opt/src/util -Wl,-rpath-link,/home/user/mesa-git/builddir/build-amd64-opt/src/util/format -Wl,-rpath-link,/home/user/mesa-git/builddir/build-amd64-opt/src/gallium/auxiliary -Wl,-rpath-link,/home/user/mesa-git/builddir/build-amd64-opt/src/compiler/nir -Wl,-rpath-link,/home/user/mesa-git/builddir/build-amd64-opt/src/compiler /usr/bin/ld: /usr/lib/llvm-10/lib/libclangCodeGen.a(BackendUtil.cpp.o): in function `(anonymous namespace)::EmitAssemblyHelper::EmitAssemblyWithNewPassManager(clang::BackendAction, std::unique_ptr >)': (.text._ZN12_GLOBAL__N_118EmitAssemblyHelper30EmitAssemblyWithNewPassManagerEN5clang13BackendActionESt10unique_ptrIN4llvm17raw_pwrite_streamESt14default_deleteIS5_EE+0x1f15): undefined reference to `getPollyPluginInfo()' collect2: error: ld returned 1 exit status ``` Tested with LLVM 10.0.0-4 packages, and gcc 9.3.0 and gcc 10.1.0. I know I was able to compile opencl/clover just few days ago just fine. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-1-amd64 (SMP w/32 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 libllvm10 depends on: ii libc6 2.30-8 ii libedit23.1-20191231-1 ii libffi7 3.3-4 ii libgcc-s1 10.1.0-3 ii libstdc++6 10.1.0-3 ii libtinfo6 6.2-1 ii libz3-4 4.8.7-4 ii zlib1g 1:1.2.11.dfsg-2 libllvm10 recommends no packages. libllvm10 suggests no packages. -- no debconf information
Bug#962300: dmraid: dmraid fails do install in a debootstrapped chroot
Control: tag -1 moreinfo On Fri, 05 Jun 2020 21:30:50 +0200 =?utf-8?Q?=C5=81ukasz_Stelmach?= wrote: > On an amd64 host I created armel chroot with qemu-debootstrap. I > attempted to install dracut which pulled dmraid and other > packages. After installing all packages but dmraid apt install shows > following messages (with set -x added to dmraid.postinst) I have a qemu-debootstrap armhf chroot (tarball) that I use for some tests with pbuilder. Execution of foreign binaries happens with qemu-user(-static). Installing dmraid there works: # apt-get install dmraid Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: dmsetup libdevmapper1.02.1 libdmraid1.0.0.rc16 libkmod2 udev The following NEW packages will be installed: dmraid dmsetup libdevmapper1.02.1 libdmraid1.0.0.rc16 libkmod2 udev 0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. Need to get 126 kB/1845 kB of archives. After this operation, 9592 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://ftp.de.debian.org/debian unstable/main armhf libdmraid1.0.0.rc16 armhf 1.0.0.rc16-8 [90.8 kB] Get:2 http://ftp.de.debian.org/debian unstable/main armhf dmraid armhf 1.0.0.rc16-8 [35.0 kB] Fetched 126 kB in 0s (606 kB/s) debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76, <> line 6.) debconf: falling back to frontend: Readline Selecting previously unselected package libkmod2:armhf. (Reading database ... 13583 files and directories currently installed.) Preparing to unpack .../0-libkmod2_27+20200310-2_armhf.deb ... Unpacking libkmod2:armhf (27+20200310-2) ... Selecting previously unselected package udev. Preparing to unpack .../1-udev_245.5-3_armhf.deb ... Unpacking udev (245.5-3) ... Selecting previously unselected package dmsetup. Preparing to unpack .../2-dmsetup_2%3a1.02.167-1+b1_armhf.deb ... Unpacking dmsetup (2:1.02.167-1+b1) ... Selecting previously unselected package libdevmapper1.02.1:armhf. Preparing to unpack .../3-libdevmapper1.02.1_2%3a1.02.167-1+b1_armhf.deb ... Unpacking libdevmapper1.02.1:armhf (2:1.02.167-1+b1) ... Selecting previously unselected package libdmraid1.0.0.rc16. Preparing to unpack .../4-libdmraid1.0.0.rc16_1.0.0.rc16-8_armhf.deb ... Unpacking libdmraid1.0.0.rc16 (1.0.0.rc16-8) ... Selecting previously unselected package dmraid. Preparing to unpack .../5-dmraid_1.0.0.rc16-8_armhf.deb ... Unpacking dmraid (1.0.0.rc16-8) ... Setting up libkmod2:armhf (27+20200310-2) ... Setting up udev (245.5-3) ... A chroot environment has been detected, udev not started. Setting up libdevmapper1.02.1:armhf (2:1.02.167-1+b1) ... Setting up dmsetup (2:1.02.167-1+b1) ... Setting up libdmraid1.0.0.rc16 (1.0.0.rc16-8) ... Setting up dmraid (1.0.0.rc16-8) ... Running in chroot, ignoring request. Processing triggers for libc-bin (2.30-8) ... > Setting up dmraid (1.0.0.rc16-8) ... > + command -v update-initramfs > + udevadm trigger --subsystem-match=block --action=change > Failed to scan devices: No such file or directory > dpkg: error processing package dmraid (--configure): In your case, udev does not seem to recognice that is it running in a chroot. So the failure is in udev and not dmraid. But the error is probably somewhere in your chroot setup ... these foreign chroots are a bit tricky. Andreas
Bug#959437: sslsniff: diff for NMU version 0.8-8.1
Control: tags 959437 + pending
Dear maintainer,
I've prepared an NMU for sslsniff (versioned as 0.8-8.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru sslsniff-0.8/debian/changelog sslsniff-0.8/debian/changelog
--- sslsniff-0.8/debian/changelog 2018-08-31 09:54:26.0 +0200
+++ sslsniff-0.8/debian/changelog 2020-06-08 23:32:00.0 +0200
@@ -1,3 +1,12 @@
+sslsniff (0.8-8.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Giovanni Mascellani ]
+ * Fix FTBFS with Boost 1.71. (Closes: #959437)
+
+ -- Sebastian Ramacher Mon, 08 Jun 2020 23:32:00 +0200
+
sslsniff (0.8-8) unstable; urgency=medium
* Fix build with wl,asneeded (Closes: #849695)
diff -Nru sslsniff-0.8/debian/patches/Fix-FTBFS-with-Boost-1.71.patch sslsniff-0.8/debian/patches/Fix-FTBFS-with-Boost-1.71.patch
--- sslsniff-0.8/debian/patches/Fix-FTBFS-with-Boost-1.71.patch 1970-01-01 01:00:00.0 +0100
+++ sslsniff-0.8/debian/patches/Fix-FTBFS-with-Boost-1.71.patch 2020-06-08 23:31:58.0 +0200
@@ -0,0 +1,181 @@
+From: Giovanni Mascellani
+Date: Sat, 2 May 2020 11:24:55 +0200
+Subject: Fix FTBFS with Boost 1.71.
+
+---
+ RawBridge.hpp | 21 +
+ SSLConnectionManager.cpp | 6 +++---
+ http/HttpBridge.hpp| 25 +
+ http/HttpConnectionManager.cpp | 4 ++--
+ 4 files changed, 51 insertions(+), 5 deletions(-)
+
+diff --git a/RawBridge.hpp b/RawBridge.hpp
+index 9206faa..7a1255e 100644
+--- a/RawBridge.hpp
b/RawBridge.hpp
+@@ -36,6 +36,16 @@ private:
+ ip::tcp::socket serverSocket;
+ ip::tcp::endpoint destination;
+
++#if BOOST_VERSION >= 107000
++ const boost::asio::executor
++
++ RawBridge(boost::shared_ptr clientSocket,
++ ip::tcp::endpoint& destination,
++ const boost::asio::executor & executor) :
++clientSocket(clientSocket), serverSocket(executor),
++executor(executor), destination(destination), closed(0)
++ {}
++#else
+ boost::asio::io_service _service;
+
+ RawBridge(boost::shared_ptr clientSocket,
+@@ -44,6 +54,7 @@ private:
+ clientSocket(clientSocket), serverSocket(io_service),
+ io_service(io_service), destination(destination), closed(0)
+ {}
++#endif
+
+ void handleConnect(Bridge::ptr bridge, const boost::system::error_code ) {
+ if (!error) Bridge::shuttle(&(*clientSocket), );
+@@ -55,6 +66,15 @@ protected:
+
+ public:
+
++#if BOOST_VERSION >= 107000
++ static ptr create(boost::shared_ptr clientSocket,
++ ip::tcp::endpoint& destination,
++ const boost::asio::executor & executor)
++
++ {
++return ptr(new RawBridge(clientSocket, destination, executor));
++ }
++#else
+ static ptr create(boost::shared_ptr clientSocket,
+ ip::tcp::endpoint& destination,
+ boost::asio::io_service & io_service)
+@@ -62,6 +82,7 @@ public:
+ {
+ return ptr(new RawBridge(clientSocket, destination, io_service));
+ }
++#endif
+
+ virtual ip::tcp::socket& getClientSocket() {
+ return *clientSocket;
+diff --git a/SSLConnectionManager.cpp b/SSLConnectionManager.cpp
+index 9beed10..6087f65 100644
+--- a/SSLConnectionManager.cpp
b/SSLConnectionManager.cpp
+@@ -44,7 +44,7 @@ SSLConnectionManager::SSLConnectionManager(io_service _service,
+ }
+
+ void SSLConnectionManager::acceptIncomingConnection() {
+- boost::shared_ptr socket(new ip::tcp::socket(acceptor.get_io_service()));
++ boost::shared_ptr socket(new ip::tcp::socket(acceptor.get_executor()));
+
+ acceptor.async_accept(*socket, boost::bind(::handleClientConnection,
+ this, socket, placeholders::error));
+@@ -76,7 +76,7 @@ void SSLConnectionManager::shuttleConnection(boost::shared_ptr
+ ip::tcp::endpoint )
+
+ {
+- Bridge::ptr bridge = RawBridge::create(clientSocket, destination, acceptor.get_io_service());
++ Bridge::ptr bridge = RawBridge::create(clientSocket, destination, acceptor.get_executor());
+ bridge->shuttle();
+ }
+
+@@ -134,7 +134,7 @@ void SSLConnectionManager::interceptSSL(boost::shared_ptr clien
+ ip::tcp::endpoint ,
+ bool wildcardOK)
+ {
+- ip::tcp::socket serverSocket(acceptor.get_io_service());
++ ip::tcp::socket serverSocket(acceptor.get_executor());
+ boost::system::error_code error;
+ serverSocket.connect(destination, error);
+
+diff --git a/http/HttpBridge.hpp b/http/HttpBridge.hpp
+index 863db21..edcffa1 100644
+--- a/http/HttpBridge.hpp
b/http/HttpBridge.hpp
+@@ -40,12 +40,21 @@ class HttpBridge : public Bridge {
+
+ public:
+
++#if BOOST_VERSION >= 107000
++ static ptr create(boost::shared_ptr clientSocket,
++ const executor& executor,
++ HttpBridgeListener *listener)
++ {
++return ptr(new HttpBridge(clientSocket, executor, listener));
++ }
++#else
+ static ptr create(boost::shared_ptr clientSocket,
+ io_service& io_service,
+ HttpBridgeListener *listener)
+ {
+ return ptr(new
Bug#962505: pygments: Newer version available
Source: pygments Version: 2.3.1+dfsg-3 Severity: wishlist Control: block 962239 by -1 Dear Maintainer, A new upstream version v2.6.1 is available. Please consider packaging the new version. -- Regards Sudip
Bug#806464: ITP: trufont -- cross-platform ufo3 font editor
On Sun, Jun 07, 2020 at 01:15:00PM +0200, Jonas Smedegaard wrote: > What is the status of initially packaging trufont? > > Any particular blockers you might need help with? Hi, Well, there's no particularly weird blockers on my side, but instead I saw this project is updated since last Septemper. I will retry packaging this along with two NEW dependencies (ufo-extractor: #891390, hsluv: #891391) again. Thanks for nudging, Yao Wei signature.asc Description: PGP signature
Bug#955579: sinfo: diff for NMU version 0.0.48-2.1
Control: tags 955579 + pending Dear maintainer, I've prepared an NMU for sinfo (versioned as 0.0.48-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru sinfo-0.0.48/debian/changelog sinfo-0.0.48/debian/changelog --- sinfo-0.0.48/debian/changelog 2018-12-02 16:15:05.0 +0100 +++ sinfo-0.0.48/debian/changelog 2020-06-08 23:29:50.0 +0200 @@ -1,3 +1,13 @@ +sinfo (0.0.48-2.1) unstable; urgency=medium + + * Non-maintainer upload. + + [ Giovanni Mascellani ] + * Remove dependency on libboost-signals-dev, which was removed. (Closes: +#955579) + + -- Sebastian Ramacher Mon, 08 Jun 2020 23:29:50 +0200 + sinfo (0.0.48-2) unstable; urgency=medium * [38b4d44] pt_BR debconf template translation (Closes: #844667) diff -Nru sinfo-0.0.48/debian/control sinfo-0.0.48/debian/control --- sinfo-0.0.48/debian/control 2018-12-02 16:13:43.0 +0100 +++ sinfo-0.0.48/debian/control 2020-06-08 23:25:52.0 +0200 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Jürgen Rinas Uploaders: Gaudenz Steinlin -Build-Depends: debhelper (>= 9.20160709~), autotools-dev, libncurses5-dev, libboost-dev, libboost-signals-dev, libboost-regex-dev, libboost-system-dev, po-debconf, groff +Build-Depends: debhelper (>= 9.20160709~), autotools-dev, libncurses5-dev, libboost-dev, libboost-regex-dev, libboost-system-dev, po-debconf, groff Standards-Version: 4.2.1 Vcs-Git: https://salsa.debian.org/debian/sinfo.git Vcs-Browser: https://salsa.debian.org/debian/sinfo signature.asc Description: PGP signature
Bug#962468: ppp: Missing /dev/ppp. ppp_generic kernel module not loaded.
Control: tags -1 + patch Control: affects -1 + network-manager-fortisslvpn El lun., 8 jun. 2020 a las 15:43, Agustin Martin () escribió: > pppd[56889]: Couldn't open the /dev/ppp device: No such file or directory > > This causes the VPN initialization to fail. > > The reason for this is that ppp_generic mode is not loaded. Seems that > there are some reasons why this is not done by udev (See #263079 for > old standalone udev package). Please find attached the patch I am using to deal with this. Regards, -- Agustin From 822670b95c35b61f66ee36a845f77b711832bd27 Mon Sep 17 00:00:00 2001 From: Agustin Martin Domingo Date: Mon, 8 Jun 2020 16:05:18 +0200 Subject: [PATCH] Make /dev/ppp available by installing ppp_generic module on boot or package configuration. Signed-off-by: Agustin Martin Domingo --- debian/ppp-modules.conf | 3 +++ debian/ppp.install | 1 + debian/ppp.postinst | 8 +++- 3 files changed, 11 insertions(+), 1 deletion(-) create mode 100644 debian/ppp-modules.conf diff --git a/debian/ppp-modules.conf b/debian/ppp-modules.conf new file mode 100644 index 000..96de26a --- /dev/null +++ b/debian/ppp-modules.conf @@ -0,0 +1,3 @@ +# At least needed to have /dev/ppp available. udev seems not to create it. +# This is not straighforward, see #263079 for old standalone udev package +ppp_generic diff --git a/debian/ppp.install b/debian/ppp.install index 63668e9..737e6c8 100644 --- a/debian/ppp.install +++ b/debian/ppp.install @@ -18,3 +18,4 @@ debian/extra/provider.peer usr/share/ppp/ debian/tmp-ppp/usr/lib/pppd/* usr/lib/pppd/ debian/tmp-ppp/usr/sbin/* usr/sbin/ debian/tmp-ppp/usr/share/man/* usr/share/man/ +debian/ppp-modules.conf etc/modules-load.d/ diff --git a/debian/ppp.postinst b/debian/ppp.postinst index 357364a..5f42cff 100644 --- a/debian/ppp.postinst +++ b/debian/ppp.postinst @@ -37,6 +37,13 @@ for file in $LOG_FILES; do chmod 640 $file done +# Make sure /dev/ppp is available by installing ppp_generic module +if ! ischroot 2>/dev/null; then +modprobe -q ppp_generic || true +else +echo "chroot environment detected - not running 'modprobe ppp_generic'" +fi + } case "$1" in @@ -56,4 +63,3 @@ esac #DEBHELPER# exit 0 - -- 2.27.0
Bug#962504: New upstream, package improvements
Package: screenkey Severity: wishlist A new upstream version of screenkey (1.1) is officially available, which should fix bug #962118 as well. Additionally, the package dependencies are incomplete. screenkey should also depend explicitly on required GI interface gir1.2-gtk-3.0. I would also recommend the following packages: fonts-font-awesome gir1.2-appindicator3-0.1 slop I'm thorn whether slop and fonts-font-awesome should be a recommended or be a straight dependency, since the GUI selection behavior depends on it. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-2-rt-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages screenkey depends on: ii libx11-6 2:1.6.9-2+b1 ii python33.8.2-3 ii python3-cairo 1.16.2-3 ii python3-gi 3.36.0-3 screenkey recommends no packages. screenkey suggests no packages.
Bug#962503: cenon.app: FTBFS with gnustep-gui/0.28: /usr/include/GNUstep/AppKit/NSApplication.h:131:44: error: expected ‘)’ before ‘;’ token
Source: cenon.app Version: 4.0.6+ds1-2 Severity: important Tags: sid bullseye User: pkg-gnustep-maintain...@lists.alioth.debian.org Usertags: gnustep-gui0.28-transition gnustep-transition This package fails to build on amd64 with gnustep-gui/0.28.0-1 from experimental: gcc DocView.m -c \ -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 -fno-strict-aliasing -fexceptions -fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS -pthread -fPIC -Wall -DGSWARN -DGSDIAGNOSE -Wno-import -g -O2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -I../../Source/x86_64/linux-gnu -fconstant-string-class=NSConstantString -I. -I. -I/usr/local/include/GNUstep -I/usr/include/GNUstep \ -o obj/Cenon.obj/DocView.m.o In file included from /usr/include/GNUstep/AppKit/AppKit.h:52, from DocView.m:70: DocView.m: In function ‘-[DocView draw:]’: /usr/include/GNUstep/AppKit/NSApplication.h:131:44: error: expected ‘)’ before ‘;’ token 131 | #define NSAppKitVersionNumber10_8 1187; |^ DocView.m:1807:45: note: in expansion of macro ‘NSAppKitVersionNumber10_8’ 1807 | if ( floor(NSAppKitVersionNumber) > NSAppKitVersionNumber10_8 && | ^ DocView.m:1807:12: note: to match this ‘(’ 1807 | if ( floor(NSAppKitVersionNumber) > NSAppKitVersionNumber10_8 && |^ ... make[5]: *** [/usr/share/GNUstep/Makefiles/rules.make:515: obj/Cenon.obj/DocView.m.o] Error 1
Bug#962496: uwsgi-plugin-php: autopkgtest failure: Segmentation Fault
Hi, > You recently added an autopkgtest to your package uwsgi-plugin-php, > great. However, it fails. Currently this failure is blocking the > migration to testing [1]. Can you please investigate the situation and > fix it? This is the same as #962186 which should be fixed by the freshly uploaded 0.0.9 version. Waiting for the CI results to close. Thanks for reporting, Alex
Bug#962239: RFP: jc -- converts command output to JSON
Ah yes, the minimum pygments version should probably be v2.4.2.
> On Jun 8, 2020, at 1:37 PM, Sudip Mukherjee
> wrote:
>
> On Thu, Jun 04, 2020 at 03:03:35PM -0700, Kelly Brazil wrote:
>> Package: wnpp
>> Severity: wishlist
>>
>> I am the developer of jc, which is now packaged on OpenSUSE, NixOS, macOS
>> (Homebrew), and FreeBSD (ports). jc is currently in process for packaging on
>> Fedora.
>>
>> jc is licensed under the MIT license.
>>
>> https://github.com/kellyjonbrazil/jc
>> https://pypi.org/project/jc/
>>
>> JSON CLI output utility
>
> I do not use this personally, but I think this might be a good package
> to be in Debian. I made an initial packaging, but getting error while
> trying to use that.
>
> $ ls -l /usr/bin | jc --ls
>
> Traceback (most recent call last):
> File "/usr/bin/jc", line 11, in
>load_entry_point('jc==1.11.2', 'console_scripts', 'jc')()
> File "/usr/lib/python3/dist-packages/jc/cli.py", line 401, in main
>json_out(result, pretty=pretty, mono=mono, piped_out=piped_output())
> File "/usr/lib/python3/dist-packages/jc/cli.py", line 249, in json_out
>class JcStyle(Style):
> File "/usr/lib/python3/dist-packages/pygments/style.py", line 101, in __new__
>ndef[0] = colorformat(styledef)
> File "/usr/lib/python3/dist-packages/pygments/style.py", line 58, in
> colorformat
>assert False, "wrong color format %r" % text
> AssertionError: wrong color format 'ansiblue'
>
> I have also tried with ls -l /usr/bin | jc --ls -m
>
> Note: This works fine when I install Pygments from pip3 (v2.6.1) rather
> than using the Debian version which is v2.3.1
>
>
> --
> Regards
> Sudip
Bug#962239: RFP: jc -- converts command output to JSON
On Thu, Jun 04, 2020 at 03:03:35PM -0700, Kelly Brazil wrote:
> Package: wnpp
> Severity: wishlist
>
> I am the developer of jc, which is now packaged on OpenSUSE, NixOS, macOS
> (Homebrew), and FreeBSD (ports). jc is currently in process for packaging on
> Fedora.
>
> jc is licensed under the MIT license.
>
> https://github.com/kellyjonbrazil/jc
> https://pypi.org/project/jc/
>
> JSON CLI output utility
I do not use this personally, but I think this might be a good package
to be in Debian. I made an initial packaging, but getting error while
trying to use that.
$ ls -l /usr/bin | jc --ls
Traceback (most recent call last):
File "/usr/bin/jc", line 11, in
load_entry_point('jc==1.11.2', 'console_scripts', 'jc')()
File "/usr/lib/python3/dist-packages/jc/cli.py", line 401, in main
json_out(result, pretty=pretty, mono=mono, piped_out=piped_output())
File "/usr/lib/python3/dist-packages/jc/cli.py", line 249, in json_out
class JcStyle(Style):
File "/usr/lib/python3/dist-packages/pygments/style.py", line 101, in __new__
ndef[0] = colorformat(styledef)
File "/usr/lib/python3/dist-packages/pygments/style.py", line 58, in
colorformat
assert False, "wrong color format %r" % text
AssertionError: wrong color format 'ansiblue'
I have also tried with ls -l /usr/bin | jc --ls -m
Note: This works fine when I install Pygments from pip3 (v2.6.1) rather
than using the Debian version which is v2.3.1
--
Regards
Sudip
Bug#958566: Minor comment
Andreas, thanks for the bug fix. It is working. But there still is a minor cosmetic bug, not influencing the correct working of the package. The display of an unknown card will never work, because it displays the list of unsupported cards. Besides the lspci-command also detects the wired network connection from broadcom. lspci -n -d 14e4: | grep -o "14e4:[1234567890abcdef]\+" 14e4:1600 14e4:4312 So if the construction worked it would incorrectly display card 1600 as unknown. Although I also prefer the check for an unknown card, I have the impression this check cannot be simply made because of the weird card naming of Broadcom.
Bug#962478: [Pkg-fonts-devel] Bug#962478: fonts-firacode: Provide TTF instead of OTF font files. The former embed hinting instructions and thus are rendered sharper on (low-res) screens.
Hi Salim, Am Montag, den 08.06.2020, 17:01 +0200 schrieb Salim B: > Therefore I think it would *really* make sense to switch to the TTF > variant of the font since it's mainly intended for "on-screen" usage > anyway (in contrast to print) and thus sharp rendering is very > important. sounds reasonable, I'll consider it for the next revision. I hope we have all the pre-requisites for building the TTF variants in Debian, their build chain contains some more steps than the one for the OTF variants. Cheers, - Fabian signature.asc Description: This is a digitally signed message part
Bug#962502: libowfat0: Newer version available
Package: libowfat0 Version: 0.30-2 Severity: wishlist Dear Maintainer, The current version in Debian is from 2015, and newer versions have since been released. As or writing, the latest version is 0.32, released 2018-10-02. Please consider packaging the newer version. Thank you. -- System Information: Debian Release: 10.4 APT prefers stable APT policy: (900, 'stable'), (500, 'testing') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 4.19.0-0.bpo.5-amd64 (SMP w/8 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 libowfat0 depends on: ii libc6 2.28-10 libowfat0 recommends no packages. libowfat0 suggests no packages. -- no debconf information
Bug#962497: r-base breaks r-cran-data.table autopkgtest: 'origin' must be supplied
On 8 June 2020 at 21:25, Paul Gevers wrote: | Source: r-base, r-cran-data.table | Control: found -1 r-base/4.0.1-1 | Control: found -1 r-cran-data.table/1.12.8+dfsg-1 | Severity: serious | Tags: sid bullseye | X-Debbugs-CC: debian...@lists.debian.org | User: debian...@lists.debian.org | Usertags: breaks needs-update | | Dear maintainer(s), | | With a recent upload of r-base the autopkgtest of r-cran-data.table | fails in testing when that autopkgtest is run with the binary packages | of r-base from unstable. It passes when run with only packages from | testing. In tabular form: | |passfail | r-base from testing4.0.1-1 | r-cran-data.table from testing1.12.8+dfsg-1 | versioned deps [0] from testingfrom unstable | all others from testingfrom testing | | I copied some of the output at the bottom of this report. | | Currently this regression is blocking the migration of r-base to testing | [1]. Due to the nature of this issue, I filed this bug report against | both packages. Can you please investigate the situation and reassign the | bug to the right package? The "'origin' must be supplied" message makes it *extremely* likely that is in fact a change made by R 4.0.0. R is released once a year as a new minor (plus patch releases) and *extremely* carefully vetted / prepared (and folks who upload packages to CRAN always test against the coming version. So the data.table team upstream surely had this fixed as well. The _released_ version of data.table still has the problem too as we can see at CRAN: https://cloud.r-project.org/web/checks/check_results_data.table.html I would expect the next version to be fixed. In the mean time the bug could be fixed in the test(s), or the tests could be (temporarily) suspended. (I had a quick look at the code around tests 1390.* (in file inst/tests/tests.Raw) but didn't immediately come up with a fix. Dirk | | More information about this bug and the reason for filing it can be found on | https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation | | Paul | | [0] You can see what packages were added from the second line of the log | file quoted below. The migration software adds source package from | unstable to the list if they are needed to install packages from | r-base/4.0.1-1. I.e. due to versioned dependencies or breaks/conflicts. | [1] https://qa.debian.org/excuses.php?package=r-base | | https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-data.table/5803495/log.gz | | BEGIN TEST main.R | | R version 4.0.1 (2020-06-06) -- "See Things Now" | Copyright (C) 2020 The R Foundation for Statistical Computing | Platform: x86_64-pc-linux-gnu (64-bit) | | R is free software and comes with ABSOLUTELY NO WARRANTY. | You are welcome to redistribute it under certain conditions. | Type 'license()' or 'licence()' for distribution details. | | R is a collaborative project with many contributors. | Type 'contributors()' for more information and | 'citation()' on how to cite R or R packages in publications. | | Type 'demo()' for some demos, 'help()' for on-line help, or | 'help.start()' for an HTML browser interface to help. | Type 'q()' to quit R. | | > require(data.table) | Loading required package: data.table | > | > test.data.table() # runs the main test suite of 5,000+ tests in | /inst/tests/tests.Rraw | getDTthreads(verbose=TRUE): | omp_get_num_procs()2 | R_DATATABLE_NUM_PROCS_PERCENT unset (default 50) | R_DATATABLE_NUM_THREADSunset | omp_get_thread_limit() 2147483647 | omp_get_max_threads() 2 | OMP_THREAD_LIMIT unset | OMP_NUM_THREADSunset | RestoreAfterFork true | data.table is using 1 threads. See ?setDTthreads. | test.data.table() running: | /usr/lib/R/site-library/data.table/tests/tests.Rraw.bz2 | | Suggested package bit64 is not installed. Tests using it will be | skipped. | | | Suggested package xts is not installed. Tests using it will be skipped. | | | Suggested package nanotime is not installed. Tests using it will be | skipped. | | | Suggested package R.utils is not installed. Tests using it will be | skipped. | | | Suggested package yaml is not installed. Tests using it will be | skipped. | | Test 1390.3 produced 1 errors but expected 0 | Expected: | Observed: 'origin' must be supplied | Test 1390.4 produced 1 errors but expected 0 | Expected: | Observed: 'origin' must be supplied | Test 1390.5 produced 1 errors but expected 0 | Expected: | Observed: 'origin' must be supplied | Test 1760 not run because this session either has no OpenMP or has been | limited to one thread (e.g. under UBSAN and ASAN) | | 10 longest running tests took 15s (38% of 40s) | ID time nTest | 1: 1888 2.860 9 | 2: 1848 1.766 1 | 3: 1874 1.753 5 | 4: 1438 1.564 354 | 5: 1912 1.530 2 | 6: 1223
Bug#962501: gnome-terminal: Closing a terminal window at a root promt will crash the Gnome session.
Package: gnome-terminal Version: 3.30.2-2 Severity: normal Closing a terminal window at a root prompt will crash the Gnome session. * What led up to the situation? Open a Gnome-Terminal window sudo su - close window Click "Close Terminal" on the "Close this terminal?" dialog box * What exactly did you do (or not do) that was effective (or ineffective)? If you remember to exit to your user prompt it will not crash. * What was the outcome of this action? I think it crashes the gnome-session. On wayland it will crash everything and locks up the computer. You can't even cntl+alt+fn key to another console On X it seems to restart the session. The screen freezes for a couple of seconds and comeback. -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-0.bpo.2-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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-terminal depends on: ii dbus-user-session [default-dbus-session-bus] 1.12.16-1 ii dbus-x11 [dbus-session-bus] 1.12.16-1 ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii gnome-terminal-data 3.30.2-2 ii gsettings-desktop-schemas 3.28.1-1 ii libatk1.0-0 2.30.0-2 ii libc6 2.28-10 ii libdconf1 0.30.1-2 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgtk-3-03.24.5-1 ii libpango-1.0-01.42.4-8~deb10u1 ii libuuid1 2.33.1-0.1 ii libvte-2.91-0 0.54.2-2 ii libx11-6 2:1.6.7-1 Versions of packages gnome-terminal recommends: ii gvfs 1.38.1-5 ii nautilus-extension-gnome-terminal 3.30.2-2 ii yelp 3.31.90-1 gnome-terminal suggests no packages. -- no debconf information
Bug#962500: firmware-nonfree: Please update firmware-nonfree to >=20200519 to enable support for many modern nics and gpus
Source: firmware-nonfree Severity: important Dear Maintainer, Please consider this a catchall bug report for multiple new debian users who needed to download the linux-firmware tarball from upstream in order to support wifi nics and gpus that are too new to be supported by the binary blobs from July 2019, the most recent available in any debian branch. I see some recent activity in the kernel-team salsa repo, so maybe you are waiting for some milestone, but a release sooner rather than later would be better for everyone. We are linking https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git on a weekly basis in the support channel(s). Thank you for your attention, sney -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#962495: php7.3-cli, php7.4-cli: segfault on openssl_pkey_get_details
retitle 962495 php7.3-cli, php7.4-cli: segfault on openssl_pkey_get_details reassign 962495 php7.3-cli,php7.4-cli found 962495 7.4.5-1+b1 found 962495 7.3.14-1~deb10u1 notfound 962495 7.0.33-0+deb9u7 thanks On Mon, 8 Jun 2020, Thorsten Glaser wrote: > Package: php7.4-cli > Version: 7.4.5-1+b1 7.3.14-1~deb10u1 (buster) also crashes. 7.0.33-0+deb9u7 (stretch) does not crash. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Bug#962499: keepassxc: Block 2.6.0 beta from migrating
Package: keepassxc Version: 2.6.0~beta1-1 Severity: serious We don't want 2.6.0~beta1-1 to enter testing, and probably want to wait for final 2.6.0. -- System Information: Debian Release: bullseye/sid APT prefers groovy APT policy: (991, 'groovy'), (500, 'groovy'), (500, 'focal-security') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-31-generic (SMP w/8 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 /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages keepassxc depends on: ii libargon2-10~20171227-0.2 ii libc6 2.31-0ubuntu9 ii libgcrypt201.8.5-5ubuntu1 ii libqrencode4 4.0.2-2 ii libqt5concurrent5 5.14.2+dfsg-2ubuntu1 ii libqt5core5a 5.14.2+dfsg-2ubuntu1 ii libqt5dbus55.14.2+dfsg-2ubuntu1 ii libqt5gui5 5.14.2+dfsg-2ubuntu1 ii libqt5network5 5.14.2+dfsg-2ubuntu1 ii libqt5svg5 5.14.2-1 ii libqt5widgets5 5.14.2+dfsg-2ubuntu1 ii libqt5x11extras5 5.14.2-1 ii libreadline5 5.2+dfsg-3build3 ii libsodium231.0.18-1 ii libstdc++6 10.1.0-3ubuntu1 ii libx11-6 2:1.6.9-2ubuntu1 ii libxi6 2:1.7.10-0ubuntu1 ii libxtst6 2:1.2.3-1 ii libykpers-1-1 1.20.0-2 ii libzxcvbn0 2.4+dfsg-2 ii zlib1g 1:1.2.11.dfsg-2ubuntu1 keepassxc recommends no packages. Versions of packages keepassxc suggests: pn webext-keepassxc-browser ii xclip 0.13-1 -- no debconf information -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#962498: please install OpenBabel3Config.cmake module
Package: libopenbabel-dev Version: 3.1.1+dfsg-1 Severity: normal Control: block 953630 by -1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, OpenBabel 3.1 added an OpenBabel 3 CMake module proper, but it seems it's not included: > dh_missing: warning: usr/bin/roundtrip exists in debian/tmp but is not > installed to anywhere > dh_missing: warning: usr/share/man/man1/roundtrip.1 exists in debian/tmp but > is not installed to anywhere > dh_missing: warning: usr/lib/cmake/openbabel3/OpenBabel3ConfigVersion.cmake > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: usr/lib/cmake/openbabel3/OpenBabel3Config.cmake exists > in debian/tmp but is not installed to anywhere > dh_missing: warning: usr/lib/cmake/openbabel3/OpenBabel3_EXPORTS-none.cmake > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: usr/lib/cmake/openbabel3/OpenBabel3_EXPORTS.cmake exists > in debian/tmp but is not installed to anywhere Please add them; Kalzium has added OpenBabel 3 support this way. - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (2, 'unstable'), (1, 'testing-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libopenbabel-dev depends on: ii libopenbabel7 3.1.1+dfsg-2 libopenbabel-dev recommends no packages. Versions of packages libopenbabel-dev suggests: pn libopenbabel-doc - -- no debconf information -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQT287WtmxUhmhucNnhyvHFIwKstpwUCXt6ReAAKCRByvHFIwKst p8X3AQDBFfFIFcv2IhlVuSQEFVgbGb1mDs9Yr2/UOxmbzTchpQD/SZokog3TMkaf SN27xxYAMyH5bvIVBgJDeQxTCwO4MQc= =aLdu -END PGP SIGNATURE-
Bug#962497: r-base breaks r-cran-data.table autopkgtest: 'origin' must be supplied
Source: r-base, r-cran-data.table Control: found -1 r-base/4.0.1-1 Control: found -1 r-cran-data.table/1.12.8+dfsg-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of r-base the autopkgtest of r-cran-data.table fails in testing when that autopkgtest is run with the binary packages of r-base from unstable. It passes when run with only packages from testing. In tabular form: passfail r-base from testing4.0.1-1 r-cran-data.table from testing1.12.8+dfsg-1 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of r-base to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from r-base/4.0.1-1. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=r-base https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-data.table/5803495/log.gz BEGIN TEST main.R R version 4.0.1 (2020-06-06) -- "See Things Now" Copyright (C) 2020 The R Foundation for Statistical Computing Platform: x86_64-pc-linux-gnu (64-bit) R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under certain conditions. Type 'license()' or 'licence()' for distribution details. R is a collaborative project with many contributors. Type 'contributors()' for more information and 'citation()' on how to cite R or R packages in publications. Type 'demo()' for some demos, 'help()' for on-line help, or 'help.start()' for an HTML browser interface to help. Type 'q()' to quit R. > require(data.table) Loading required package: data.table > > test.data.table() # runs the main test suite of 5,000+ tests in /inst/tests/tests.Rraw getDTthreads(verbose=TRUE): omp_get_num_procs()2 R_DATATABLE_NUM_PROCS_PERCENT unset (default 50) R_DATATABLE_NUM_THREADSunset omp_get_thread_limit() 2147483647 omp_get_max_threads() 2 OMP_THREAD_LIMIT unset OMP_NUM_THREADSunset RestoreAfterFork true data.table is using 1 threads. See ?setDTthreads. test.data.table() running: /usr/lib/R/site-library/data.table/tests/tests.Rraw.bz2 Suggested package bit64 is not installed. Tests using it will be skipped. Suggested package xts is not installed. Tests using it will be skipped. Suggested package nanotime is not installed. Tests using it will be skipped. Suggested package R.utils is not installed. Tests using it will be skipped. Suggested package yaml is not installed. Tests using it will be skipped. Test 1390.3 produced 1 errors but expected 0 Expected: Observed: 'origin' must be supplied Test 1390.4 produced 1 errors but expected 0 Expected: Observed: 'origin' must be supplied Test 1390.5 produced 1 errors but expected 0 Expected: Observed: 'origin' must be supplied Test 1760 not run because this session either has no OpenMP or has been limited to one thread (e.g. under UBSAN and ASAN) 10 longest running tests took 15s (38% of 40s) ID time nTest 1: 1888 2.860 9 2: 1848 1.766 1 3: 1874 1.753 5 4: 1438 1.564 354 5: 1912 1.530 2 6: 1223 1.186 728 7: 1648 1.17145 8: 1650 1.15845 9: 1652 1.14345 10: 1437 1.11636 Error in test.data.table() : 3 errors out of 7311 in 40.4s elapsed (38.2s cpu) on Sun Jun 7 09:33:45 2020. [endian==little, sizeof(long double)==16, sizeof(pointer)==8, TZ=Etc/UTC, locale='C', l10n_info()='MBCS=FALSE; UTF-8=FALSE; Latin-1=FALSE', getDTthreads()='omp_get_num_procs()==2; R_DATATABLE_NUM_PROCS_PERCENT==unset (default 50); R_DATATABLE_NUM_THREADS==unset; omp_get_thread_limit()==2147483647; omp_get_max_threads()==2; OMP_THREAD_LIMIT==unset; OMP_NUM_THREADS==unset; RestoreAfterFork==true; data.table is using 1 threads. See ?setDTthreads.']. Search tests/tests.Rraw.bz2 for test numbers: 1390.3, 1390.4, 1390.5. In addition: Warning messages: 1: In parse(n = -1, file = file, srcfile = NULL, keep.source = FALSE) : invalid input found on input connection '/usr/lib/R/site-library/data.table/tests/tests.Rraw.bz2' 2: In parse(n = -1, file = file, srcfile = NULL, keep.source = FALSE) : invalid input found on input connection
Bug#960065: Please put this on hold
Hi, because of "netstat" being widely deprecated now, we are going to change the sdmp plugin to use "ss" instead. There is no point in continuing with the current version of sdmp in 11.1.0, so please put this on hold. We are going to have a fixed version in our next release, and may provide a patch for 11.1.0. This does not affect the rest of open-vm-tools 11.1.0 , so the update can go ahead without the plugin. Note that it's not built by default. Thanks, Oliver
Bug#962496: uwsgi-plugin-php: autopkgtest failure: Segmentation Fault
Source: uwsgi-plugin-php Version: 0.0.8 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package uwsgi-plugin-php, great. However, it fails. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=uwsgi-plugin-php https://ci.debian.net/data/autopkgtest/testing/amd64/u/uwsgi-plugin-php/5752337/log.gz autopkgtest [17:23:42]: test smoke: [--- [uWSGI] getting INI configuration from debian/tests/php.ini % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (52) Empty reply from server - uwsgi logfile *** Starting uWSGI 2.0.18-debian (64bit) on [Wed Jun 3 17:23:42 2020] *** compiled with version: 9.3.0 on 25 May 2020 12:47:36 os: Linux-4.19.0-9-amd64 #1 SMP Debian 4.19.118-2 (2020-04-29) nodename: ci-155-77b9aeba machine: x86_64 clock source: unix pcre jit disabled detected number of CPU cores: 2 current working directory: /tmp/autopkgtest-lxc.gf8ting2/downtmp/build.FfV/src detected binary path: /usr/bin/uwsgi-core chdir() to /tmp/autopkgtest-lxc.gf8ting2/downtmp/build.FfV/src/debian/tests//htdocs *** WARNING: you are running uWSGI without its master process manager *** your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) creating a new cache store file: /tmp/tmp.12ZxrQ8m3S/uwsgi.cache [uwsgi-cache] restored 0 items *** Cache "sessions" initialized: 1MB (key: 2136 bytes, keys: 64080 bytes, data: 1966080 bytes, bitmap: 0 bytes) preallocated *** uwsgi socket 0 bound to TCP address localhost:9090 fd 4 PHP document root set to /tmp/autopkgtest-lxc.gf8ting2/downtmp/build.FfV/src/debian/tests/htdocs PHP 7.4.5 initialized your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 72920 bytes (71 KB) for 1 cores *** Operational MODE: single process *** *** no app loaded. going in full dynamic mode *** *** uWSGI is running in multiple interpreter mode *** spawned uWSGI worker 1 (and the only) (pid: 13224, cores: 1) writing pidfile to /tmp/tmp.12ZxrQ8m3S/uwsgi.pid !!! uWSGI process 13224 got Segmentation Fault !!! *** backtrace of 13224 *** uwsgi(uwsgi_backtrace+0x2a) [0x55f6838d06aa] uwsgi(uwsgi_segfault+0x23) [0x55f6838d0a93] /lib/x86_64-linux-gnu/libc.so.6(+0x3b800) [0x7f94b286c800] /lib/x86_64-linux-gnu/libc.so.6(+0x15e711) [0x7f94b298f711] /lib/libphp7.so(virtual_chdir_file+0x31) [0x7f94b086bd41] /lib/libphp7.so(php_execute_script+0xf5) [0x7f94b07e18d5] /usr/lib/uwsgi/plugins/php_plugin.so(uwsgi_php_request+0xbd3) [0x7f94b0a365b3] uwsgi(wsgi_req_recv+0xad) [0x55f68388105d] uwsgi(simple_loop_run+0xc4) [0x55f6838cc424] uwsgi(simple_loop+0x10) [0x55f6838cc200] uwsgi(uwsgi_ignition+0x294) [0x55f6838d0de4] uwsgi(uwsgi_worker_run+0x266) [0x55f6838d4266] uwsgi(uwsgi_run+0x454) [0x55f6838d47e4] uwsgi(+0x2b68e) [0x55f68388068e] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f94b2857e0b] uwsgi(_start+0x2a) [0x55f6838806ba] *** end of backtrace *** signal_pidfile()/kill(): No such process [core/uwsgi.c line 1694] signature.asc Description: OpenPGP digital signature
Bug#569049: Fixed upstream
My bad, the latest commit didn't fix this issue. It was actually fixed back in 2014, and this fix is available in the the release 1.4. Here is the link to the exact commit that fixed it. https://github.com/raas/mbw/commit/6346daa765f85d47caa39685fb452701d82446d5 Best regards, Celelibi
Bug#962495: php7.4-cli: segfault on openssl_pkey_get_details
Package: php7.4-cli Version: 7.4.5-1+b1 Severity: important tglase@tglase-nb:~ $ cat y.php 384]); print_r(openssl_pkey_get_details($x)); tglase@tglase-nb:~ $ php7.4 y.php Segmentation fault (core dumped) Jun 8 21:01:40 tglase-nb vmunix: [181591.846132] php7.4[29402]: segfault at 8 ip 7f57530b2df1 sp 7ffc73577b70 error 4 in libcrypto.so.1.1[7f5753068000+19f000] Jun 8 21:01:40 tglase-nb vmunix: [181591.846149] Code: e0 c3 0f 1f 80 00 00 00 00 8b 57 08 31 c0 85 d2 0f 94 c0 c3 0f 1f 44 00 00 41 57 41 56 41 55 41 54 55 53 48 89 fb 48 83 ec 18 <44> 8b 77 08 44 8b 67 14 45 8d 6e ff 41 83 e4 04 75 3d e8 88 88 fb -- Package-specific info: Additional PHP 7.4 information PHP 7.4 SAPI (php7.4query -S): PHP 7.4 Extensions (php7.4query -M -v): Configuration files: [PHP] engine = On short_open_tag = Off precision = 14 output_buffering = 4096 zlib.output_compression = Off implicit_flush = Off unserialize_callback_func = serialize_precision = -1 disable_functions = disable_classes = zend.enable_gc = On zend.exception_ignore_args = On expose_php = On max_execution_time = 30 max_input_time = 60 memory_limit = -1 error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT display_errors = Off display_startup_errors = Off log_errors = On log_errors_max_len = 1024 ignore_repeated_errors = Off ignore_repeated_source = Off report_memleaks = On variables_order = "GPCS" request_order = "GP" register_argc_argv = Off auto_globals_jit = On post_max_size = 8M auto_prepend_file = auto_append_file = default_mimetype = "text/html" default_charset = "UTF-8" doc_root = user_dir = enable_dl = Off file_uploads = On upload_max_filesize = 2M max_file_uploads = 20 allow_url_fopen = On allow_url_include = Off default_socket_timeout = 60 [CLI Server] cli_server.color = On [Date] [filter] [iconv] [imap] [intl] [sqlite3] [Pcre] [Pdo] [Pdo_mysql] pdo_mysql.default_socket= [Phar] [mail function] SMTP = localhost smtp_port = 25 mail.add_x_header = Off [ODBC] odbc.allow_persistent = On odbc.check_persistent = On odbc.max_persistent = -1 odbc.max_links = -1 odbc.defaultlrl = 4096 odbc.defaultbinmode = 1 [MySQLi] mysqli.max_persistent = -1 mysqli.allow_persistent = On mysqli.max_links = -1 mysqli.default_port = 3306 mysqli.default_socket = mysqli.default_host = mysqli.default_user = mysqli.default_pw = mysqli.reconnect = Off [mysqlnd] mysqlnd.collect_statistics = On mysqlnd.collect_memory_statistics = Off [OCI8] [PostgreSQL] pgsql.allow_persistent = On pgsql.auto_reset_persistent = Off pgsql.max_persistent = -1 pgsql.max_links = -1 pgsql.ignore_notice = 0 pgsql.log_notice = 0 [bcmath] bcmath.scale = 0 [browscap] [Session] session.save_handler = files session.use_strict_mode = 0 session.use_cookies = 1 session.use_only_cookies = 1 session.name = PHPSESSID session.auto_start = 0 session.cookie_lifetime = 0 session.cookie_path = / session.cookie_domain = session.cookie_httponly = session.cookie_samesite = session.serialize_handler = php session.gc_probability = 0 session.gc_divisor = 1000 session.gc_maxlifetime = 1440 session.referer_check = session.cache_limiter = nocache session.cache_expire = 180 session.use_trans_sid = 0 session.sid_length = 26 session.trans_sid_tags = "a=href,area=href,frame=src,form=" session.sid_bits_per_character = 5 [Assertion] zend.assertions = -1 [COM] [mbstring] [gd] [exif] [Tidy] tidy.clean_output = Off [soap] soap.wsdl_cache_enabled=1 soap.wsdl_cache_dir="/tmp" soap.wsdl_cache_ttl=86400 soap.wsdl_cache_limit = 5 [sysvshm] [ldap] ldap.max_links = -1 [dba] [opcache] [curl] [openssl] [ffi] /etc/php/7.4/cli/conf.d/20-ftp.ini extension=ftp.so /etc/php/7.4/cli/conf.d/20-gettext.ini extension=gettext.so /etc/php/7.4/cli/conf.d/20-sysvsem.ini extension=sysvsem.so /etc/php/7.4/cli/conf.d/20-readline.ini extension=readline.so /etc/php/7.4/cli/conf.d/20-xsl.ini extension=xsl.so /etc/php/7.4/cli/conf.d/10-opcache.ini zend_extension=opcache.so /etc/php/7.4/cli/conf.d/15-xml.ini extension=xml.so /etc/php/7.4/cli/conf.d/20-xmlreader.ini extension=xmlreader.so /etc/php/7.4/cli/conf.d/20-mbstring.ini extension=mbstring.so /etc/php/7.4/cli/conf.d/20-exif.ini extension=exif.so /etc/php/7.4/cli/conf.d/20-sysvshm.ini extension=sysvshm.so /etc/php/7.4/cli/conf.d/20-posix.ini extension=posix.so /etc/php/7.4/cli/conf.d/20-sysvmsg.ini extension=sysvmsg.so /etc/php/7.4/cli/conf.d/20-gd.ini extension=gd.so /etc/php/7.4/cli/conf.d/20-dom.ini extension=dom.so /etc/php/7.4/cli/conf.d/20-xmlwriter.ini extension=xmlwriter.so /etc/php/7.4/cli/conf.d/20-phar.ini extension=phar.so /etc/php/7.4/cli/conf.d/20-json.ini extension=json.so /etc/php/7.4/cli/conf.d/20-pgsql.ini extension=pgsql.so /etc/php/7.4/cli/conf.d/20-ctype.ini extension=ctype.so /etc/php/7.4/cli/conf.d/20-pdo_pgsql.ini
Bug#962478: fonts-firacode: Provide TTF instead of OTF font files. The former embed hinting instructions and thus are rendered sharper on (low-res) screens.
Package: fonts-firacode Version: 2+dfsg1-1 Severity: important Dear Maintainer, More information about this issue can be found in the official FiraCode bug tracker: https://github.com/tonsky/FiraCode/issues/939 The FiraCode author explicitly states[1]: > I think at some point OTF was superior to TTF, but now they are mostly the > same. The difference between OTF and TTF is that TTF can embed hinting > instructions, which are essential for rendering on low-res displays. Therefore I think it would *really* make sense to switch to the TTF variant of the font since it's mainly intended for "on-screen" usage anyway (in contrast to print) and thus sharp rendering is very important. Kind regards, Salim Brüggemann [1]: https://github.com/tonsky/FiraCode/issues/939#issuecomment-640665878 -- System Information: Debian Release: bullseye/sid APT prefers focal-updates APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (100, 'focal-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-33-generic (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#962494: python3-backports.weakref seems to be useless
Package: python3-backports.weakref Version: 1.0-3 Severity: serious Control: block -1 by 962493 This backports functionality that is already in python3 in oldoldstable, after removal of the python2 module there is not much point in providing this package. This package was only needed for python-backports.tempfile.
Bug#962493: python3-backports.tempfile seems to be useless
Package: python3-backports.tempfile Version: 1.0-4 Severity: serious This backports functionality that is already in python3 in oldoldstable, after removal of the python2 module there is not much point in providing this package. moto only requires it for older Python versions.
Bug#962186: uwsgi-plugin-php: CI fails with SIG_SEGV in bullseye
Quoting Alexandre Rossi (2020-06-08 20:15:32) > > > > Sorry, I was too fast - indeed we don't do the above (we do not > > > > probe for and tie to a specific package version) - but I am > > > > confused: why is it not reliable to use the provided ABI? > > > > > > The uwsgi-plugin-php is a sort of special case, as the > > > phpapi- can be resolved with any SAPI (CLI, CGI, apache2, > > > FCGI) and you need to depend on a specific SAPI. > > > > > > Or just wait for php-default 76 to migrate as that solves the > > > problem > > Then do we depend on libphp7.4-embed (my patch) or do we let the > problem solve itself when php-default migrates? Should I revert my > proposed fix? Oh sorry, I missed your fix - looks good to me! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#962492: Missing copyright attributions and other problems in debian/copyright
Source: vde2 Version: 2.3.2+r586-2.2+b1 Severity: serious Justification: Policy ยง12.5 Greetings, during the review of this package in the NEW queue I discovered various issues that are already present in the current unstable version of the package as outlined below. These files are marked in the copyright file as BSD-4-clause, but the files themselves only contain 3 clauses: * src/slirpvde/cksum.c * src/slirpvde/ip.h * src/slirpvde/ip_icmp.c * src/slirpvde/ip_icmp.h * src/slirpvde/ip_input.c * src/slirpvde/ip_output.c * src/slirpvde/mbuf.h * src/slirpvde/misc.c * src/slirpvde/qemu-queue.h * src/slirpvde/tcp.h * src/slirpvde/tcp_input.c * src/slirpvde/tcp_output.c * src/slirpvde/tcp_subr.c * src/slirpvde/tcp_timer.c * src/slirpvde/tcp_timer.h * src/slirpvde/tcp_var.h * src/slirpvde/tcpip.h * src/slirpvde/udp.c * src/slirpvde/udp.h The following authors are not attributed in the copyright file for files that list them as copyright holders. This list is not necessarily exhaustive. Please check every file and make sure all authors in the files are attributed in debian/copyright. 2002 Yon Uriarte, Jeff Dike: * README 2014 Renzo Davoli, Alessandro Ghedini VirtualSquare: * src/vde_vxlan/plug.h 2001,2002 Jeff Dike: * src/kvde_switch/consmgmt.h * src/kvde_switch/datasock.h * src/kvde_switch/kvde_switch.c * src/vde_switch/consmgmt.h * src/vde_switch/datasock.h * src/vde_switch/fstp.h * src/vde_switch/hash.c * src/vde_switch/hash.h * src/vde_switch/port.c * src/vde_switch/port.h * src/vde_switch/switch.h * src/vde_switch/tuntap.h * src/vde_switch/vde_switch.c * src/vde_tunctl.c * src/vde_tunctl.c 2004 Mattia Belletti: * src/kvde_switch/consmgmt.c * src/kvde_switch/datasock.c * src/kvde_switch/sockutils.c * src/kvde_switch/sockutils.h * src/vde_switch/consmgmt.c * src/vde_switch/datasock.c * src/vde_switch/sockutils.c * src/vde_switch/sockutils.h * src/vde_switch/tuntap.c * src/vde_switch/vde_switch.c 2007 Luca Bigliardi: * include/cmdparse.h * include/libvdemgmt.h * src/common/cmdparse.c * src/lib/libvdemgmt.c * src/lib/libvdesnmp.c * src/unixcmd.c * src/vde_pcapplug.c 2006-2011 Daniele Lacamera: * src/lib/python/VdePlug.py * src/lib/python/vdeplug_python.c * src/vde_cryptcab/crc32.c * src/vde_cryptcab/crc32.h * src/vde_cryptcab/cryptcab.c * src/vde_cryptcab/cryptcab.h * src/vde_cryptcab/vde_cryptcab_client.c * src/vde_cryptcab/vde_cryptcab_server.c * src/vde_l3/vde_buff.h * src/vde_l3/vde_l3.c * src/vde_router/vde_headers.h * src/vde_router/vde_router.c * src/vde_router/vde_router.h * src/vde_router/vder_arp.c * src/vde_router/vder_arp.h * src/vde_router/vder_datalink.c * src/vde_router/vder_datalink.h * src/vde_router/vder_icmp.c * src/vde_router/vder_icmp.h * src/vde_router/vder_olsr.c * src/vde_router/vder_packet.c * src/vde_router/vder_packet.h * src/vde_router/vder_queue.c * src/vde_router/vder_queue.h 2005 Ludovico Gargenghi: * src/common/canonicalize.c * src/common/poll.c 2005 Richard Kettlewell: * src/common/open_memstream.c 2007 Filippo Giunchedi: * include/libvdesnmp.h 2004-2008 Fabrice Bellard: * src/slirpvde/bootp.c * src/slirpvde/slirp.c 2004 Magnus Damm: * src/slirbvde/tftp.c 2007 Daniel Lacamera, 200 Florian Heinz, Julien Oster: * src/vde_over_ns/dns.c * src/vde_over_ns/dns.h * src/vde_over_ns/dns_proto.h * src/vde_over_ns/encode.c * src/vde_over_ns/fun.h * src/vde_over_ns/pstack.c * src/vde_over_ns/pstack.h * src/vde_over_ns/queue.c * src/vde_over_ns/util.c * src/vde_over_ns/vde_io.c * src/vde_over_ns/vde_over_ns.c 1999 Andrea Arcangeli: * src/vde_router/rbtree.c * src/vde_router/rbtree.h 2002 David Woodhouse: * src/vde_router/rbtree.c Allessandro Ghedini VirtualSquare: * src/vde_vxlan/log.c * src/vde_vxlan/log.h * src/vde_vxlan/plug.c * src/vde_vxlan/plug.h * src/vde_vxlan/vde_vxlan.c * src/vde_vxlan/vxlan.c * src/vde_vxlan/vxlan.h * src/vde_vxlan/vxlan_hash.c * src/vde_vxlan/vxlan_hash.h And finally a matter of personal taste: debian/copyright contains the following line: > Licenses for some components in src/slirpvde in addition to GPL-2: and then goes on to list the licenses that apply to some files in that directory. I think this fullfills the requirement of stating the license conditions for those files, but it doesn't really help me if I want to know *which* files these license conditions apply to. Stating the files each of these licenses applies to explicitly would make the statement more helpful, especially to ftp-masters doing future reviews of this package. Regards Sven -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (990, 'testing-debug'), (990, 'testing'), (102, 'unstable-debug'), (102, 'unstable'), (101, 'experimental-debug'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8
Bug#962186: uwsgi-plugin-php: CI fails with SIG_SEGV in bullseye
Maybe keep the patch until the PHP-defaults migrates and then you can drop it? The migration is getting stuck on various different autopkgtests, so I actually don’t know why it hasn’t migrated yet. Ondrej On Mon, 8 Jun 2020 at 20:18, Alexandre Rossi wrote: > Hi, > > > > > Sorry, I was too fast - indeed we don't do the above (we do not > > > > probe for and tie to a specific package version) - but I am > > > > confused: why is it not reliable to use the provided ABI? > > > > > > The uwsgi-plugin-php is a sort of special case, as the phpapi- > > > can be resolved with any SAPI (CLI, CGI, apache2, FCGI) and you need > > > to depend on a specific SAPI. > > > > > > Or just wait for php-default 76 to migrate as that solves the problem > > Then do we depend on libphp7.4-embed (my patch) or do we let the problem > solve itself when php-default migrates? Should I revert my proposed fix? > > Thanks, > > Alex > > -- -- Ondřej Surý
Bug#962491: RFS: xplc/0.3.13-8 [QA] -- Light weight component system
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "xplc" * Package name: xplc Version : 0.3.13-8 Upstream Author : Pierre Phaneuf * URL : http://xplc.sourceforge.net/ * License : LGPL-2.1 * Vcs : https://salsa.debian.org/debian/xplc Section : libs It builds those binary packages: libxplc0.3.13 - Light weight component system libxplc0.3.13-dev - Light weight component system (Development libraries and headers) uuidcdef - Universally Unique Identifier (UUID) generator To access further information about this package, please visit the following URL: https://mentors.debian.net/package/xplc Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/x/xplc/xplc_0.3.13-8.dsc Changes since the last upload: * QA upload. * Update Standards-Version to 4.5.0 * Use debhelper-compat. - Update to compat level 13. - Remove cdbs. - Remove dh-autoreconf. - Simplify d/rules. - List files not installed. - Adjust the path for mutiarch location. * Mark Vcs to salsa. * Remove whitespace from changelog. -- Regards Sudip
Bug#962186: uwsgi-plugin-php: CI fails with SIG_SEGV in bullseye
Hi, > > > Sorry, I was too fast - indeed we don't do the above (we do not > > > probe for and tie to a specific package version) - but I am > > > confused: why is it not reliable to use the provided ABI? > > > > The uwsgi-plugin-php is a sort of special case, as the phpapi- > > can be resolved with any SAPI (CLI, CGI, apache2, FCGI) and you need > > to depend on a specific SAPI. > > > > Or just wait for php-default 76 to migrate as that solves the problem Then do we depend on libphp7.4-embed (my patch) or do we let the problem solve itself when php-default migrates? Should I revert my proposed fix? Thanks, Alex
Bug#948281: anytun: diff for NMU version 0.3.7-1.2
Control: tags 948281 + pending
Dear maintainer,
I've prepared an NMU for anytun (versioned as 0.3.7-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer or cancel the NMU.
Regards,
Fabio Tobich
diff -Nru anytun-0.3.7/debian/changelog anytun-0.3.7/debian/changelog
--- anytun-0.3.7/debian/changelog 2018-11-17 19:21:25.0 -0200
+++ anytun-0.3.7/debian/changelog 2020-06-08 14:11:32.0 -0300
@@ -1,3 +1,11 @@
+anytun (0.3.7-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches/20_fix-build-with-boost1.71.patch: added to fix FTBFS
+against boost1.71. Thanks Giovanni Mascellani. (Closes: #948281)
+
+ -- Fabio Augusto De Muzio Tobich Mon, 08 Jun 2020
14:11:32 -0300
+
anytun (0.3.7-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru anytun-0.3.7/debian/patches/20_fix-build-with-boost1.71.patch
anytun-0.3.7/debian/patches/20_fix-build-with-boost1.71.patch
--- anytun-0.3.7/debian/patches/20_fix-build-with-boost1.71.patch
1969-12-31 21:00:00.0 -0300
+++ anytun-0.3.7/debian/patches/20_fix-build-with-boost1.71.patch
2020-06-08 14:11:32.0 -0300
@@ -0,0 +1,69 @@
+Description: Fix build with Boost 1.71.
+Author: Giovanni Mascellani
+Bug-Debian: https://bugs.debian.org/948281
+Last-Update: 2020-01-06
+--- anytun-0.3.7.orig/src/syncServer.cpp
anytun-0.3.7/src/syncServer.cpp
+@@ -125,7 +125,11 @@ void SyncServer::start_accept()
+ std::list::iterator it = acceptors_.begin();
+ for(; it != acceptors_.end(); ++it) {
+ if(!it->started_) {
++#if BOOST_VERSION >= 107000
++ SyncTcpConnection::pointer new_connection =
SyncTcpConnection::create(it->acceptor_->get_executor());
++#else
+ SyncTcpConnection::pointer new_connection =
SyncTcpConnection::create(it->acceptor_->get_io_service());
++#endif
+ conns_.push_back(new_connection);
+ it->acceptor_->async_accept(new_connection->socket(),
+ boost::bind(::handle_accept,
this, new_connection, boost::asio::placeholders::error, it));
+--- anytun-0.3.7.orig/src/syncTcpConnection.cpp
anytun-0.3.7/src/syncTcpConnection.cpp
+@@ -66,10 +66,18 @@ void SyncTcpConnection::Send(std::string
+boost::asio::placeholders::error,
+
boost::asio::placeholders::bytes_transferred));
+ }
++
++#if BOOST_VERSION >= 107000
++SyncTcpConnection::SyncTcpConnection(const boost::asio::executor& executor)
++ : socket_(executor)
++{
++}
++#else
+ SyncTcpConnection::SyncTcpConnection(boost::asio::io_service& io_service)
+ : socket_(io_service)
+ {
+ }
++#endif
+
+ void SyncTcpConnection::handle_write(const boost::system::error_code&
/*error*/,
+ size_t /*bytes_transferred*/)
+--- anytun-0.3.7.orig/src/syncTcpConnection.h
anytun-0.3.7/src/syncTcpConnection.h
+@@ -60,9 +60,15 @@ public:
+ typedef boost::shared_ptr pointer;
+ typedef boost::asio::ip::tcp proto;
+
++#if BOOST_VERSION >= 107000
++ static pointer create(const boost::asio::executor& executor) {
++return pointer(new SyncTcpConnection(executor));
++ };
++#else
+ static pointer create(boost::asio::io_service& io_service) {
+ return pointer(new SyncTcpConnection(io_service));
+ };
++#endif
+
+ boost::function onConnect;
+ proto::socket& socket();
+@@ -70,7 +76,11 @@ public:
+ void start();
+ void Send(std::string message);
+ private:
++#if BOOST_VERSION >= 107000
++ SyncTcpConnection(const boost::asio::executor& executor);
++#else
+ SyncTcpConnection(boost::asio::io_service& io_service);
++#endif
+
+ void handle_write(const boost::system::error_code & /*error*/,
+ size_t /*bytes_transferred*/);
diff -Nru anytun-0.3.7/debian/patches/series anytun-0.3.7/debian/patches/series
--- anytun-0.3.7/debian/patches/series 2018-07-23 10:12:55.0 -0300
+++ anytun-0.3.7/debian/patches/series 2020-06-08 14:11:24.0 -0300
@@ -1,2 +1,3 @@
01-fix-typos
10_fix_boost167_compilation.patch
+20_fix-build-with-boost1.71.patch
Bug#962490: RM: mysql-utilities -- RoQA; Orphaned, abandoned upstream, depends on Python 2
Package: ftp.debian.org Severity: normal Please remove mysql-utilities. It's orphaned since 2018 without an adopter, end-of-lifed by Oracle (877856), RC-buggy since 2017 and depends on Python 2, which won't get fixed due to it being EOLed. Cheers, Moritz
Bug#942622: Would the Games Team adopt Lightyears (pygame based, Python 3 port available)?
On Thu, Feb 20, 2020 at 11:44:28AM -0500, Olek Wojnar wrote: > Hi Steve, > > On Thu, Feb 13, 2020, 14:42 Steve Cotton wrote: > > > Hi all in the Games Team, > > > > One of the Debian games affected by the python3 transition is 2 > > Lightyears > > Into Space, source package name "lightyears". I've ported it to > > python3-pygame, > > and opened an upstream issue for merging it (sadly this doesn't have an > > upstream response yet). > > > > The Debian package isn't currently maintained by the Games Team, but one > > of the > > serious bugs is "Maintainer email address not working". I'm wondering if > > the > > Games Team would adopt it and apply my python3 port? > > > > That's a great game, I've played it quite a few times over the years. I'll > be happy to sponsor the upload under the Games Team umbrella. > > However, have you tried contacting the maintainer and the uploader team to > make sure they're ok with transferring the package to the Games Team? I > think it makes sense for us to have it but we need to check with them > first. If you have already obtained that permission, please forward the > email to these lists so that we have it for reference. > > Debian bugs: > > #942622 src:lightyears: Maintainer email address not working > > #912488 lightyears: Please migrate to python3-pygame > > #936945 lightyears: Python2 removal in sid/bullseye > > > > Upstream pull request: > > https://github.com/20kly/20kly/issues/2 > > https://github.com/stevecotton/20kly/tree/version1.4/python3 > > > > The Debian package's "copyright" file cleans up some of the oddities of the > > upstream README.md's licensing section, I'm sure it's distributable but > > expect > > it to get some questions if it went through the NEW queue. Oddities such as > > attributing an image as "copyright NASA" instead of saying that it's one of > > NASA's public domain images. I'm happy to put some effort in to fixing > > that. > > > > Please do (pending approval to move the package)! Let me know what you need > from me (off-lists is fine for coordinating details). Has there been any update wrt lightyears/Py3 being moved to the Debian Games Team? Cheers, Moritz
Bug#937483: pymtbl: Python2 removal in sid/bullseye
On Mon, Jun 08, 2020 at 01:42:29PM -0400, Robert Edmonds wrote: > Moritz Mühlenhoff wrote: > > On Fri, Aug 30, 2019 at 07:34:31AM +, Matthias Klose wrote: > > > Package: src:pymtbl > > > Version: 0.4.0-1 > > > Severity: normal > > > Tags: sid bullseye > > > User: debian-pyt...@lists.debian.org > > > Usertags: py2removal > > > > > > Python2 becomes end-of-live upstream, and Debian aims to remove > > > Python2 from the distribution, as discussed in > > > https://lists.debian.org/debian-python/2019/07/msg00080.html > > > > There's no movement on https://github.com/farsightsec/pymtbl/issues/4, the > > last > > commit is from 2017 and there are no reverse deps, let's remove? > > > > Cheers, > > Moritz > > Sounds good to me. Filed an RM bug and CCed you. Cheers, Moritz
Bug#962489: RM: pymtbl -- RoQA; Depends on Python 2, no reverse deps
Package: ftp.debian.org Severity: normal Please remove pymtbl, it depends on Python 2, there are no reverse deps and there's no upstream movement towards a Py3 port. Acked by the maintainer in #937483. Cheers, Moritz
Bug#516394: removal of djbdns ?
Hi, I see djbdns is removed from testing, due to unarchiving of critical bug #516394 However, as source package djbdns 1:1.05-11 builds several binary packages (axfrdns, djbdns-conf, djbdns-utils, rbldns, tinydns, walldns) and the bug is only in (if not patched) dnscache, would other packages reenter testing and later new stable Debian? I don't particularly care about dnscache, but use other parts of djbdns (tinydns, axfrdns, djbdns-utils...) often. I don't know if only some binary packages sharing same source package can be blocked from entering testing, or how this should reasonably be handled so other binary packages remain in Debian (lowering severity to important, as much of the binaries are non-affected? patching dnscache with provided patches?) I am not DD/DM, but have some experience with creating Debian packages, so am willing to help if needed. Thanks! -- Opinions above are GNU-copylefted.
Bug#962486: additional info
Sorry for the typos in my report. kdialog --passivepopup "Helloworld" 5 kdialog --msgbox "Helloworld" creates a two-line formatted output. In version 19.12 both variants process html tags. Thx, volker
Bug#962488: fonts-tlwg: description should explain when TTF vs. OTF is more suitable
Source: fonts-tlwg Version: 1:0.7.2-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, fonts-tlwg are provided as both Truetype and Opentype, but package descriptions lack any mention of when either format is more suitable. Maybe Truetype fonts include hinting omitted from Opentype fonts. Maybe Opentype fonts include feature sets lacking in Truetype fonts. Maybe they are technically equal but consuming applications vary in their support for accessing all features of either format. Please add mention of which format is better when. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl7eeUcACgkQLHwxRsGg ASFAow//TW1tdBZozMKIMmQuN5RIXr+4V9/UQ3MSKYAwRCXSwYbSqCqqJ2NrASDe wTcH0lioDQkxcN44jah86DD1kkCUEvONL6KkFSv/6uaTYkX2g94+1rMjvXVdrKjf mlTnXDcLZRNpjPtY3u6fODzicqDhz8ohbgIBZKCebEqKc/YXpXVdmgFPVfUmpN/i hUd4fUXEhqrAE9F3evhjLwAYm2BneeJ9n5x7rdP6/Gkq/zn1BUkF18oEYgffxNJ7 hHlfHtsbAbCKtj50Xjsomuf0De7WQXef84Y2HqLTdR2UAm5yWePy2R/OKDGuAdqU aBdmcn7iip8ZWI5sy5xLxE+2BWqN9JQeDQ4RIRmfmM65U10Rx5300O/Od9kLy1Ii OcTAvIlwlpeGXju6dNAGy8t6MWnL61aAq6R44wD38UuM46Zc660lmjFQX4UOrQZ2 QgqgzT/sl9ni/i5gC/e2tTPJaKk/LaUF9EbjNHf0cNleQGcEt2DdV1QJyj3kTH6L gg/3wy8Q8xOXwuGXwweHK4eu3N95vanSB0ZUTYINy6YnFda6nLdLlZfgVc573Lj5 5O9UdSxMmHxMwyB9RZJwndxrd8bmHzWetKn/pncSzEkLQxPY9xdB8m17+FwfMANY f4/e3L1NHcEc595NUDw6jVw6fj8Ca7cORZGgHISUqirEzV3lPmg= =Z2vI -END PGP SIGNATURE-
Bug#937483: pymtbl: Python2 removal in sid/bullseye
Moritz Mühlenhoff wrote: > On Fri, Aug 30, 2019 at 07:34:31AM +, Matthias Klose wrote: > > Package: src:pymtbl > > Version: 0.4.0-1 > > Severity: normal > > Tags: sid bullseye > > User: debian-pyt...@lists.debian.org > > Usertags: py2removal > > > > Python2 becomes end-of-live upstream, and Debian aims to remove > > Python2 from the distribution, as discussed in > > https://lists.debian.org/debian-python/2019/07/msg00080.html > > There's no movement on https://github.com/farsightsec/pymtbl/issues/4, the > last > commit is from 2017 and there are no reverse deps, let's remove? > > Cheers, > Moritz Sounds good to me. -- Robert Edmonds edmo...@debian.org
Bug#937483: pymtbl: Python2 removal in sid/bullseye
On Fri, Aug 30, 2019 at 07:34:31AM +, Matthias Klose wrote: > Package: src:pymtbl > Version: 0.4.0-1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html There's no movement on https://github.com/farsightsec/pymtbl/issues/4, the last commit is from 2017 and there are no reverse deps, let's remove? Cheers, Moritz
Bug#962487: RM: python-sqlite -- RoQA; Obsolete, Python 2
Package: ftp.debian.org Severity: normal Please remove python-sqlite. It depends on Python 2, it's obsolete and dead upstream (removal has also been suggested by the maintainer in #938192) Cheers, Moritz
Bug#938192: your mail
On Sat, Dec 28, 2019 at 03:38:24PM +0100, Joel Rosdahl wrote: > I think that it's time to remove python-sqlite from Debian: it's a > module for the obsolete SQLite 2 API and there's (understandably) no > upstream activity. Makes sense, I've just filed an RM bug. Cheers, Moritz
Bug#962486: kdialog --passivepopup does not process html tags
Package: kdialog Version: 4:20.04.0-1 Severity: normal Hi, kdialog --passivepopup "Helloworld" 5 print plain text "Helloworld" kdialog --msgbox "Helloworld" 5 -- System Information: Debian Release: bullseye/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kdialog depends on: ii kio 5.70.1-1 ii libc6 2.30-8 ii libkf5configcore5 5.70.0-1 ii libkf5coreaddons5 5.70.0-1 ii libkf5dbusaddons5 5.70.0-1 ii libkf5guiaddons5 5.70.0-2 ii libkf5i18n5 5.70.0-1 ii libkf5iconthemes5 5.70.0-1 ii libkf5kiocore55.70.1-1 ii libkf5notifications5 5.70.0-1 ii libkf5textwidgets55.70.0-1 ii libkf5widgetsaddons5 5.70.0-1 ii libkf5windowsystem5 5.70.0-1 ii libqt5core5a 5.12.5+dfsg-10+b1 ii libqt5dbus5 5.12.5+dfsg-10+b1 ii libqt5gui55.12.5+dfsg-10+b1 ii libqt5widgets55.12.5+dfsg-10+b1 ii libstdc++610.1.0-3 ii libx11-6 2:1.6.9-2+b1 kdialog recommends no packages. kdialog suggests no packages. -- no debconf information
Bug#962467: severe memory issue in gnutls
Package: gnutls30 there's a memory leak in gnutls in conjunction with AES CCM mode. For details see also https://bugzilla.samba.org/show_bug.cgi?id=14399 https://gitlab.com/gnutls/gnutls/-/merge_requests/1277 please ship that fix from https://gitlab.com/gnutls/gnutls/-/merge_requests/1278 please ship this fix as soon as possible
Bug#962484: ITP: deblur -- deconvolution for Illumina amplicon sequencing
Package: wnpp Severity: wishlist Subject: ITP: deblur -- deconvolution for Illumina amplicon sequencing Package: wnpp Owner: Steffen Moeller Severity: wishlist * Package name: deblur Version : 1.1.0 Upstream Author : , Deblur development team * URL : https://github.com/biocore/deblur * License : BSD-3 Programming Lang: Python Description : deconvolution for Illumina amplicon sequencing Deblur is a greedy deconvolution algorithm for amplicon sequencing based on Illumina Miseq/Hiseq error profiles. The authors recommend using Deblur via the QIIME2 plugin q2-deblur. Examples of its use can be found within the plugin itself. However, Deblur itself does not depend on QIIME2. . The input to Deblur workflow is a directory of FASTA or FASTQ files (1 per sample) or a single demultiplexed FASTA or FASTQ file. These files can be gzip'd. The output directory will contain three BIOM tables in which the observation IDs are the Deblurred sequences. The outputs are contingent on the reference databases used and a more focused discussion on them is in the subsequent README section titled "Positive and Negative Filtering." The output files are as follows: . * reference-hit.biom : contains only Deblurred reads matching the positive filtering database. By default, a reference composed of 16S sequences is used, and this resulting table will contain only those reads which recruit at a coarse level to it will be retained. Reads are also filtered against the negative reference, which by default will remove any read which appears to be PhiX or adapter. . * reference-hit.seqs.fa : a fasta file containing all the sequences in reference-hit.biom . * reference-non-hit.biom : contains only Deblurred reads that did not align to the positive filtering database. Negative filtering is also appied to this table, so by default, PhiX and adapter are removed. . * reference-non-hit.seqs.fa : a fasta file containing all the sequences in reference-non-hit.biom . * all.biom : contains all Deblurred reads. This file represents the union of the "reference-hit.biom" and "reference-non-hit.biom" tables. . * all.seqs.fa : a fasta file containing all the sequences in all.biom . Deblur uses two types of filtering on the sequences: . * Negative mode - removes known artifact sequences (i.e. sequences aligning to PhiX or Adapter with >=95% identity and coverage). . * Positive mode - keeps only sequences similar to a reference database (by default known 16S sequences). SortMeRNA is used, and any sequence with an e-value <= 10 is retained. Deblur also outputs a BIOM table without this positive filtering step (named all.biom). . The FASTA files for both of these filtering steps can be supplied via the --neg-ref-fp and --pos-ref-fp options. By default, the negative database is composed of PhiX and adapter sequence and the positive database of known 16S sequences. . Deblur uses negative mode filtering to remove known artifact (i.e. PhiX and Adapter sequences) prior to denoising. The output of Deblur contains three files: all.biom, which includes all sOTUs, reference-hit.biom, which contains the output of positive filtering of the sOTUs (default only sOTUs similar to 16S sequences), and reference-non-hit.biom, which contains only sOTUs failing the positive filtering (default only non-16S sOTUs). Remark: This package is maintained by Debian Med Packaging Team at https://salsa.debian.org/med-team/deblur
Bug#960674: golang-go: "fatal error: gc_trigger underflow" on mipsel
Control: clone -1 -2 Control: reassign -2 src:linux 4.19.118-1 Control: found -2 5.4.6-1 Control: notforwarded -2 Control: severity -2 serious Control: retitle -2 Please revert CONFIG_MIPS_O32_FP64_SUPPORT change On Fri, May 29, 2020 at 11:03:14PM +0200, Aurelien Jarno wrote: > On 2020-05-28 09:04, YunQiang Su wrote: > > Adrian Bunk 于2020年5月21日周四 下午3:40写道： > > > On Thu, May 21, 2020 at 06:41:34AM +0800, YunQiang Su wrote: > > > > Adrian Bunk 于2020年5月21日周四 上午4:44写道： > > > > > On Tue, May 19, 2020 at 11:43:30AM +0800, Shengjing Zhu wrote: > > > > > > > > > > > > FTR, after giving back golang-1.14 mipsel several times, it's > > > > > > finally > > > > > > built, by a longson builder. > > > > > > So I guess it only occurs on octeon. Since the porterbox eller is > > > > > > also > > > > > > octeon, it also can't build any go program. > > > > > > > > > > On eller golang-1.14 fails to build both in sid and buster chroots. > > > > > > > > > > golang-1.11 also fails to build in a buster chroot with floating point > > > > > test errors. > > > > > > > > > > golang-1.14 gets unbroken by GOMIPS=softfloat. > > > > > > > > > > The only kernel configuration change on eller in the buster point > > > > > release is CONFIG_MIPS_O32_FP64_SUPPORT=y, everything observed would > > > > > make sense if the problem is that golang-1.11 and golang-1.14 are > > > > > not compatible with CONFIG_MIPS_O32_FP64_SUPPORT. > > > > > > > > It is just support O32_FP64. I don't expect it will have any effect. > > > > Since currently, the toolchain/libraries are all FPXX. > > > > > > Only the gcc/binutils toolchain/libraries or also the Go toolchain? > > > > you are right. the current golang still output FP32 object... > > So, we think that it is buggy. > > > > Since Loongson CPU has some strange behaviour, it even can work... > > Let's try to patch golang to support FPXX or FP64. > > > > https://github.com/golang/go/issues/39289 > > That's probably a solution for bullseye/sid, however we can't backport > such changes and rebuild the go world in buster. I therefore think that > for buster the kernel change has to be reverted. What is clear at this point is that the kernel change should be reverted in buster since it causes a regression (including build failures on buildds). I am cloning this bug for a revert in the kernel of https://salsa.debian.org/kernel-team/linux/-/commit/947fbc66183d022fe3de7871dfb262d2b87af826 I am marking the version in bullseye as found since we might run into the same problem again when buster DSAs will be built on machines running the bullseye kernel after the release of bullseye. It might be possible to mitigate this problem (e.g. in the kernel or by keeping some buildd running with the buster kernel), but without an open bug this issue might get forgotten and then resurface after the bullseye release. > Aurelien cu Adrian
Bug#961852: python-matrix-nio: autopkgtest failure: No module named 'matrix_nio'
Dear, Please find attached an updated patch which is cleaner than the first one. Best regards, Henry-Nicolas Tourneur Matrix id: @hntourne:matrix.nilux.be Le lun 8 juin 2020 à 12:34, Henry-Nicolas Tourneur a écrit : Dear Matrix-team maintainers, As discussed over the matrix room #debian-matrix:matrix.org, please find in attachment a patch to solve this bug. Basically, this happened because autodep8 tries to derive the Python module name from the package name. In this case, the module name is nio while autodep8 tries to import matrix_nio from the package name, which fails. The patch attached does the following: - Remove the autodep8 autopkgtest - Add a custom autopkgtest (debian/test/control and debian/test/pytest): This autopkgtest is actually using the upstream test cases (pytest-3 tests/), going further than a regular module import. - Adding a debian/salsa-ci.yml file so you can enable CI on your Salsa repo and use that file to validate autopkgtests works fine before uploading to main - Document the changes in debian/changelog Best regards, Henry-Nicolas Tourneur Matrix id: @hntourne:matrix.nilux.be diff --git a/debian/changelog b/debian/changelog index 04ff6e2..05483c4 100644 --- a/debian/changelog +++ b/debian/changelog @@ -7,6 +7,9 @@ python-matrix-nio (0.12.0-1) unstable; urgency=medium * Update changelog entry for release 0.10.0-2 to mention changes to descriptions + [ Henry-Nicolas Tourneur ] + * Replace autodep8 autopkgtest with new autopkg test suite (Closes: #961852) + -- Jonas Smedegaard Sat, 30 May 2020 13:18:16 +0200 python-matrix-nio (0.11.2-2) unstable; urgency=medium diff --git a/debian/control b/debian/control index 51f2b56..de49591 100644 --- a/debian/control +++ b/debian/control @@ -40,7 +40,6 @@ Homepage: https://github.com/poljar/matrix-nio Vcs-Git: https://salsa.debian.org/matrix-team/python-matrix-nio.git Vcs-Browser: https://salsa.debian.org/matrix-team/python-matrix-nio Rules-Requires-Root: no -Testsuite: autopkgtest-pkg-python Package: python3-matrix-nio Architecture: all diff --git a/debian/salsa-ci.yml b/debian/salsa-ci.yml new file mode 100644 index 000..a5957e7 --- /dev/null +++ b/debian/salsa-ci.yml @@ -0,0 +1,8 @@ +--- +include: + - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml + - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml + +variables: + SALSA_CI_DISABLE_BLHC: 1 + SALSA_CI_DISABLE_BUILD_PACKAGE_ANY: 1 diff --git a/debian/tests/control b/debian/tests/control new file mode 100644 index 000..2f944a9 --- /dev/null +++ b/debian/tests/control @@ -0,0 +1,27 @@ +Test-Command: pytest-3 tests/ +Restrictions: allow-stderr +Depends: python3-aiofiles, + python3-aiohttp, + python3-aioresponses, + python3-all, + python3-atomicwrites, + python3-cachetools, + python3-fake-factory, + python3-h11, + python3-h2, + python3-hpack, + python3-hyperframe, + python3-hypothesis, + python3-jsonschema, + python3-logbook, + python3-mypy, + python3-mypy-extensions, + python3-olm, + python3-peewee, + python3-pip, + python3-pycryptodome, + python3-pytest, + python3-pytest-benchmark, + python3-pytest-cov, + python3-unpaddedbase64, + @
Bug#962441: RFS: siconos/4.3.0+dfsg-1 [RC] -- modeling and simulation of nonsmooth dynamical systems (simulation runner tool)
Hi Adam, Thanks for taking a look. On Mon, Jun 8, 2020 at 5:29 PM Adam Borowski wrote: > > On Mon, Jun 08, 2020 at 07:37:26AM +0200, Stephen Sinclair wrote: > > * Package name: siconos > >Version : 4.3.0+dfsg-1 > > But > > > Testing this package requires fclib 3.1.0+dfsg-1, which also needs > > sponsorship. It can be found here: > > > > https://mentors.debian.net/package/fclib > > so thats actually two RFSes in one. And there are problems with fclib. I'm not sure what the right protocol is in this case, to be honest. Should I have issued two RFSes or done this one differently? > > Changes since the last upload: > > > >* New upstream version. (Closes: #962219) (Closes: #961735) > >* Add dependencies libboost-timer-dev, libboost-chrono-dev. > >* Depend on openblas and lapacke instead of atlas. > >* Require fclib 3.1.0 > >* Update location of install paths. > >* Enable WITH_GENERATION, now required for serialization. > >* Install new siconos_export_raw_data tool. > >* Fix cmake import targets to allow independent packages. > >* Update patches for new upstream version. > >* Add a flag for gfortran to avoid a regression in GCC-10. > > (Closes: #957794) > >* Remove unused build rule for swig3.0 symlink. > >* Remove non-existent files from debian/copyright. > >* Rewrite patch descriptions using gbp pq. > >* Fix a Python warning about using 'is' with a literal. > > It looked ok on my box, and passed both all automated and manual review I've > done. But, it fails on some of official buildds: at least on amd64 arm64 > x32. > > I seem unable to reproduce the FTBFS locally -- in 15 tries on amd64, 1 on > arm64, all passed. > > Thus, you'd need to investigate and fix that one in fclib first. I'm very confused about the error on buildd because I have indeed built the package many times with a fresh debootstrap without such a segfault. I will investigate and try to reproduce. I did my best to avoid problems but it seems I have missed something, I'd like to understand the difference between buildd and my own configuration to avoid this happening in the future. By the way Siconos due to its nature has been quite hard to get working on any architecture other than amd64 unfortunately. Is there a way to mark the package as amd64-only? In the meantime I try to find solutions for other architectures but it is slow going. > It'd be good if you filed a separate RFS for that. Let's leave this one > for siconos 4.3.0+dfsg-1 Okay that sounds like a reasonable approach given this problem. regards, Steve
Bug#961833: buster-pu: package openstack-debian-images/1.36
On 5/30/20 2:10 AM, Thomas Goirand wrote: > Package: release.debian.org > Severity: normal > Tags: buster > User: release.debian@packages.debian.org > Usertags: pu > > Dear release team, > > tl;dr: if not using a DHCP to boot VMs, cloud-init would get the DNS > addresses from the configdrive, which only works if resolvconf is > installed. The attached patch fixes this. > > I'd like to add the "resolvconf" package to the official Debian OpenStack > image for Buster. Doing so is done by simply adding the package to the list > in openstack-debian-images/1.36. See attached debdiff. Once the package > reaches Buster, the new OpenStack image will include resolv.conf. Hopefully, > I can ask Steve to use the updated openstack-debian-images/1.36+deb10u1 > before openstack-debian-images moves from proposed-updates to Buster. > > Rational for fixing this can be found here: > https://bugs.launchpad.net/cloud-init/+bug/1850310 > > and in this debian-cloud thread (not only the first message, but also > the follow-ups): > https://lists.debian.org/debian-cloud/2020/05/msg00086.html > > Also, the launchpad bug above mention tests from multiple people, which > is why it feels like a safe change. > > Since I don't think a DHCP-less cloud system is uncommon, it'd be really > nice to fix this (by adding the resolvconf package in the default > OpenStack image, which implies fixing the openstack-debian-images in > Buster). > > Your thoughts? > > Cheers, > > Thomas Goirand (zigo) Ping? Please don't reply just and only right before the point release... Cheers, Thomas Goirand (zigo)
Bug#962482: FTBFS: test failure in t/db-object-manager.t
Source: librose-db-object-perl
Version: 1:0.817-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
As first noticed by ci.d.n, librose-db-object-perl fails its
testsuite:
# Failed test 'get_objects() 8 - sqlite'
# at t/db-object-manager.t line 10114.
# got: '0'
# expected: '1'
# Looks like you failed 1 test of 3917.
t/db-object-manager.t ..
1..3917
…
ok 2560 - get_objects() 7 - sqlite
not ok 2561 - get_objects() 8 - sqlite
ok 2562 - foreign object 6 - sqlite
…
Test Summary Report
- ---
t/db-object-manager.t(Wstat: 256 Tests: 3917 Failed: 1)
Failed test: 2561
Non-zero exit status: 1
Files=67, Tests=15327, 88 wallclock secs ( 2.14 usr 0.25 sys + 63.06 cusr
4.66 csys = 70.11 CPU)
Result: FAIL
Failed 1/67 test programs. 1/15327 subtests failed.
make[1]: *** [Makefile:1159: test_dynamic] Error 255
make[1]: Leaving directory '/build/librose-db-object-perl-0.817'
dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2
make: *** [debian/rules:7: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
This _might_ be related to the new sqlite3 version 3.32.2-{1,2} which
was uploaded to unstable 2 days ago.
This failure also appears in the latest cpantesters report:
http://www.cpantesters.org/cpan/report/ed07ece8-a855-11ea-a404-d4a0c0ab4f88
Cheers,
gregor
-BEGIN PGP SIGNATURE-
iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl7eX4lfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgboEw/8DTEwTtNNYHQX6nUmF/1HpyAOsi3sghqP4mvW3FkgxSfb23ZuHkrOsmfT
RhN3Z/AwTzwyYAPJLWUluYQcwaLBxYQbROVOdoB59ZycpFS8etpp/0Q/rnCg5/bT
SAod5I7pEFNKgGSUtZWrySthiroe6oQyZ0mULNInW7Ygcju9mKgoauREQIG75PGu
lzCFWJDAUlrmwPK6eLQnBl/36mIbGS+75bZC6c6dSBY2QeGfHdMXuO5y4VKx6N5g
YZm9QCzuNLnjOxp4Esc7I22qjyPyYLK2y9yUbFasiEunb0z5QKiYFSjorOvOEj4v
5I+ZVk3sA1Gn2zAzyqGf74QEcKFv3bpeuJ171JNIuWQD9v4BwgPlsZg4Wlj7CCih
SXKwh24r7xs6HOdYlOfOi7rC5B3ZaVQ1kmLJ6eV07MxaP0/yGbTabQm1VKCdIBDp
++dk55zg9QVB/NNej9H4twpnM97fQDfoNVMQNm0vmfBX5ux1KeYftK/CkbUjUcs7
K58lzUom283FxHU5ozPmGhrzstkGTG+IE1CInbNNwZjE412nm3YwtLZ8lxZOnT2N
xV1TlKS5dA56Ntc55yWYca1F0+AKju0FVtCW40LVP2CDqRcKpMmdQRZp2Jx8JEzt
ltSaa/xs2UIvEup3ScJPer0A8qAQXDWYh59NS+ZO0AAVv1HO6lc=
=/zRG
-END PGP SIGNATURE-
Bug#962346: CVE-2020-0181
Hi, https://github.com/libexif/libexif/commit/ce03ad7ef4e8aeefce79192bf5b6f69fae396f0c Ciao, Marcus
Bug#962441: RFS: siconos/4.3.0+dfsg-1 [RC] -- modeling and simulation of nonsmooth dynamical systems (simulation runner tool)
On Mon, Jun 08, 2020 at 07:37:26AM +0200, Stephen Sinclair wrote: > * Package name: siconos >Version : 4.3.0+dfsg-1 But > Testing this package requires fclib 3.1.0+dfsg-1, which also needs > sponsorship. It can be found here: > > https://mentors.debian.net/package/fclib so thats actually two RFSes in one. And there are problems with fclib. > Changes since the last upload: > >* New upstream version. (Closes: #962219) (Closes: #961735) >* Add dependencies libboost-timer-dev, libboost-chrono-dev. >* Depend on openblas and lapacke instead of atlas. >* Require fclib 3.1.0 >* Update location of install paths. >* Enable WITH_GENERATION, now required for serialization. >* Install new siconos_export_raw_data tool. >* Fix cmake import targets to allow independent packages. >* Update patches for new upstream version. >* Add a flag for gfortran to avoid a regression in GCC-10. > (Closes: #957794) >* Remove unused build rule for swig3.0 symlink. >* Remove non-existent files from debian/copyright. >* Rewrite patch descriptions using gbp pq. >* Fix a Python warning about using 'is' with a literal. It looked ok on my box, and passed both all automated and manual review I've done. But, it fails on some of official buildds: at least on amd64 arm64 x32. I seem unable to reproduce the FTBFS locally -- in 15 tries on amd64, 1 on arm64, all passed. Thus, you'd need to investigate and fix that one in fclib first. It'd be good if you filed a separate RFS for that. Let's leave this one for siconos 4.3.0+dfsg-1 Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good. ⢿⡄⠘⠷⠚⠋⠀ -- on #linux-sunxi ⠈⠳⣄
Bug#962481: Printing to PDF makes files twenty million times bigger
Package: chromium Version: 81.0.4044.92-1 As noted in https://bugs.chromium.org/p/chromium/issues/detail?id=1087707 this must be a Debian bug.
Bug#962479: RFP: microsocks -- tiny, portable SOCKS5 server with very moderate resource usage
Package: wnpp Severity: wishlist * Package name: microsocks Version : master Upstream Author : rofl0r * URL : https://github.com/rofl0r/microsocks/ * License : MIT Programming Lang: C Description : tiny, portable SOCKS5 server with very moderate resource usage A SOCKS5 service that you can run on your remote boxes to tunnel connections through them, if for some reason SSH doesn't cut it for you. It's very lightweight, and very light on resources too: For every client, a thread with a stack size of 8KB is spawned. the main process basically doesn't consume any resources at all. The only limits are the amount of file descriptors and the RAM. It's also designed to be robust: it handles resource exhaustion gracefully by simply denying new connections, instead of calling abort() as most other programs do these days. Another plus is ease-of-use: no config file necessary, everything can be done from the command line and doesn't even need any parameters for quick setup. It's really a simple socks5 server, that doesn't have complicated configures and only needs libc.
Bug#962480: libnghttp2-dev: please include libnghttp2_asio
Package: libnghttp2-dev Version: 1.41.0-2 Severity: wishlist Dear Maintainer, Please include libnghttp2_asio in the -dev package. libnghttp2_asio is the C++ api (see https://nghttp2.org/documentation/libnghttp2_asio.html ) -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: armhf, i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_SOFTLOCKUP 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 libnghttp2-dev depends on: ii libnghttp2-14 1.41.0-2 ii pkg-config 0.29-4+b1 libnghttp2-dev recommends no packages. Versions of packages libnghttp2-dev suggests: pn libnghttp2-doc -- no debconf information
Bug#962474: CMAKE_SKIP_RPATH=ON improves reproducibility of CMake builds
For some reason, the downloaded output from
tests.reproducible-builds.org was double-gzipped.
Here is the properly uncompressed text.
---
/srv/reproducible-results/rbuild-debian/tmp.xJYgDafRbo/b1/qhull_2019.1-5_amd64.changes
+++
/srv/reproducible-results/rbuild-debian/tmp.xJYgDafRbo/b2/qhull_2019.1-5_amd64.changes
├── Files
│ @@ -1,11 +1,11 @@
│
│ 041d4bd6e7ca3d9c2d084aba4c2a2a51 455784 libdevel optional
libqhull-dev_2019.1-5_amd64.deb
│ 5bb0c7f9a4aaeff49d15abe4cf5d5ee7 276048 doc optional
libqhull-doc_2019.1-5_all.deb
│ f5cc0b783287e8987edb2b84554b60e3 312616 debug optional
libqhull-r7deb1-dbgsym_2019.1-5_amd64.deb
│ 75fdb7fb92f855987e4d907572854628 243096 libs optional
libqhull-r7deb1_2019.1-5_amd64.deb
│ 79341e85a770de9f9ca750a20424f220 293268 debug optional
libqhull7deb1-dbgsym_2019.1-5_amd64.deb
│ 5a3b8870d1af8d7a5c7bfc211fb60921 241048 libs optional
libqhull7deb1_2019.1-5_amd64.deb
│ - 55095384a735b603c0999294438c0411 520484 debug optional
libqhullcpp7deb1-dbgsym_2019.1-5_amd64.deb
│ - 2530d91667aee70b67c485b5f94ab7ac 104240 libs optional
libqhullcpp7deb1_2019.1-5_amd64.deb
│ + 25d2ed322f5b5daa873ec63849901039 520488 debug optional
libqhullcpp7deb1-dbgsym_2019.1-5_amd64.deb
│ + 075608429f542b46d7ec16e34007929c 104448 libs optional
libqhullcpp7deb1_2019.1-5_amd64.deb
│ 0def6de5d02be4b63c76473a92e626d4 1479480 debug optional
qhull-bin-dbgsym_2019.1-5_amd64.deb
│ fbf4f5abab361de0e9a0e26ddef7434c 475436 math optional
qhull-bin_2019.1-5_amd64.deb
├── libqhullcpp7deb1_2019.1-5_amd64.deb
│ ├── file list
│ │ @@ -1,3 +1,3 @@
│ │ -rw-r--r-- 0004 2020-04-29 08:15:52.00
debian-binary
│ │ -rw-r--r-- 000 2988 2020-04-29 08:15:52.00
control.tar.xz
│ │ --rw-r--r-- 000 101060 2020-04-29 08:15:52.00
data.tar.xz
│ │ +-rw-r--r-- 000 101268 2020-04-29 08:15:52.00
data.tar.xz
│ ├── control.tar.xz
│ │ ├── control.tar
│ │ │ ├── ./md5sums
│ │ │ │ ├── ./md5sums
│ │ │ │ │┄ Files differ
│ ├── data.tar.xz
│ │ ├── data.tar
│ │ │ ├── ./usr/lib/x86_64-linux-gnu/libqhullcpp.so.7.3.2
│ │ │ │ ├── readelf --wide --program-header {}
│ │ │ │ │ @@ -1,15 +1,15 @@
│ │ │ │ │
│ │ │ │ │ Elf file type is DYN (Shared object file)
│ │ │ │ │ Entry point 0x9ba0
│ │ │ │ │ There are 9 program headers, starting at offset 64
│ │ │ │ │
│ │ │ │ │ Program Headers:
│ │ │ │ │Type Offset VirtAddr PhysAddr
FileSiz MemSiz Flg Align
│ │ │ │ │ - LOAD 0x00 0x 0x
0x008be0 0x008be0 R 0x1000
│ │ │ │ │ + LOAD 0x00 0x 0x
0x008be8 0x008be8 R 0x1000
│ │ │ │ │LOAD 0x009000 0x9000 0x9000
0x00e151 0x00e151 R E 0x1000
│ │ │ │ │LOAD 0x018000 0x00018000 0x00018000
0x005f85 0x005f85 R 0x1000
│ │ │ │ │LOAD 0x01e610 0x0001f610 0x0001f610
0x000a08 0x000cd0 RW 0x1000
│ │ │ │ │DYNAMIC0x01e738 0x0001f738 0x0001f738
0x000240 0x000240 RW 0x8
│ │ │ │ │NOTE 0x000238 0x0238 0x0238
0x24 0x24 R 0x4
│ │ │ │ │GNU_EH_FRAME 0x019a4c 0x00019a4c 0x00019a4c
0x0009bc 0x0009bc R 0x4
│ │ │ │ │GNU_STACK 0x00 0x 0x
0x00 0x00 RW 0x10
│ │ │ │ ├── readelf --wide --sections {}
│ │ │ │ │ @@ -2,19 +2,19 @@
│ │ │ │ │
│ │ │ │ │ Section Headers:
│ │ │ │ │[Nr] Name TypeAddress Off
Size ES Flg Lk Inf Al
│ │ │ │ │[ 0] NULL 00
00 00 0 0 0
│ │ │ │ │[ 1] .note.gnu.build-id NOTE0238 000238
24 00 A 0 0 4
│ │ │ │ │[ 2] .gnu.hash GNU_HASH0260 000260
0009ac 00 A 3 0 8
│ │ │ │ │[ 3] .dynsym DYNSYM 0c10 000c10
002520 18 A 4 1 8
│ │ │ │ │ - [ 4] .dynstr STRTAB 3130 003130
003f97 00 A 0 0 1
│ │ │ │ │ - [ 5] .gnu.version VERSYM 70c8 0070c8
000318 02 A 3 0 2
│ │ │ │ │ - [ 6] .gnu.version_rVERNEED 73e0 0073e0
000120 00 A 4 4 8
│ │ │ │ │ - [ 7] .rela.dyn RELA7500 007500
0005d0 18 A 3 0 8
│ │ │ │ │ - [ 8] .rela.plt RELA7ad0 007ad0
001110 18 AI 3 22 8
│ │ │ │ │ + [ 4] .dynstr STRTAB 3130 003130
003f99 00 A 0 0 1
│ │ │ │ │ + [ 5] .gnu.version VERSYM 70ca 0070ca
000318 02 A 3 0 2
│ │ │ │ │ + [ 6] .gnu.version_rVERNEED 73e8 0073e8
000120 00 A 4 4 8
│ │ │ │ │ + [ 7] .rela.dyn RELA7508 007508
0005d0 18 A 3 0 8
│ │ │ │ │ + [ 8] .rela.plt
Bug#962372: linux-image-5.7.0-rc5-amd64: Silead module not installed
Dear Maintainer, bug #925424 seems to be about the same issue. Kind regards, Bernhard
Bug#962476: prometheus-node-exporter: Please only listen on localhost in default setup
Package: prometheus-node-exporter Version: 0.18.1+ds-2 Severity: normal I think it would be reasonable to make prometheus-node-exporter only listen on loopback interface by default for security reasons. Something like this in /etc/default/prometheus-node-exporter ARGS='--web.listen-address="[::1]:9100"' Yes, main use of the prometheus-node-exporter is to access it from the other machine, but also there are situtations where the this package could be installed, and not used, and just sit there possibly unupdated for long time. Also, sometimes people install it on routers with multiple interfaces, and start using it as is, because it does work, but that leaves it also accessible from other interfaces, which is not desirable. By changing default in debian to only listen on loopback, will force people (and me) to actually specify manually what they want before using it blindly. I understand this can make some setup more tedious (install package + edit file + restart the deamon) for some, but I think it is worth for a bit of extra concious security. Thanks! -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-1-amd64 (SMP w/32 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 prometheus-node-exporter depends on: ii libc6 2.30-8 ii systemd-sysv 245.5-3 Versions of packages prometheus-node-exporter recommends: ii dbus 1.12.18-1 ii prometheus-node-exporter-collectors 0+git20200110.fc91c86-1 prometheus-node-exporter suggests no packages. -- no debconf information
Bug#962472: ITP: param -- Make your Python code clearer and more reliable by declaring Parameters
Quoting Sebastien Delafond (2020-06-08 16:33:47) > Package: wnpp > Severity: wishlist > Owner: Sebastien Delafond > > * Package name: param > Version : 1.9.3 > Upstream Author : HoloViz team > * URL : https://github.com/holoviz/param/releases > * License : BSD-3 > Programming Lang: Python > Description : Make your Python code clearer and more reliable by > declaring Parameters > > Param is a library providing Parameters: Python attributes extended to > have features such as type and range checking, dynamically generated > values, documentation strings, default values, etc., each of which is > inherited from parent classes if not specified in a subclass. Please use the name python-param for the source package, to not pollute the common package namespace with such rather generic name. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#962477: artha: Please migrate away from enchant(1) to enchant-2
Source: artha Version: 1.0.3-3 Tags: sid bullseye X-Debbugs-CC: ti...@debian.org legend...@yahoo.com Dear Debian artha maintainers, Current artha 1.0.3 in Debian still recommends libenchant1c2a as optional dependency. This library is due to be removed in the Bulleye cycle[1]. The new enchant-2 library will be replacing it. Please consider working with artha upstream to add support of using enchant-2 library. [1] https://bugs.debian.org/956881 -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#962474: CMAKE_SKIP_RPATH=ON improves reproducibility of CMake builds
Package: debhelper
Version: 13
Severity: wishlist
By default, CMake adds an RPATH entry to ELF binaries and deletes it
again at install time. However, due to the limitations of some
platforms, CMake will actually zero out the RPATH entry in the binary,
leaking the original path length and thus making the build not
reproducible (see the attached diffoscope output for an example).
CMAKE_SKIP_RPATH disables the RPATH machinery and fixes the issue, and
since most package won't ever ship with an RPATH entry anyway, I propose
adding -DCMAKE_SKIP_RPATH=ON to the default build options.
Cheers
Timo
í\ÝrÛ8¾î~
ÜÅnE2$¨Úb+ºm9m)Îlui@´¹#nNìÞÚª©}¾Ü§ë'Ùúå¿ì¤{«¢ØRßwÎÁÁÁH¢Ûí¢8úxÛ(ôîÜÀn$â»yDÎ]0÷ºp¾#¶{¸kÌøÂ3iϽáËkÛét&Õпÿö¿¿ÿößð^sõÿ¡/P?ÇuÔß/T-Jÿ"b:),ëíOc;ºn`D
ÃbÍÇ Å
·I.ù\Ö(Y@Ôûòô¾á8kù6§ ߧ¶
îêúga!beÈ Ý"èÐÝÏ·}Ãu5Çb:a`6üñ â0:¦¤cbbÁ7î® #
Îà®ç\Çrù-Ã÷ Ëwlâ3Ã4Ô³5Ë°3¨I"T×lSâÆ¥,ð¶N±`·,Ͷo»Ü24N4J¨OiÑLëc@¹Ï<®åø.ÁØKÙX¶A±tah¶¡ÏXºpº«Ù¶MlJuæsad2à@%¸··Mè"bègcÓ´8¸æKá¾
îjqai3DM~ð="< @=Î¥ ×Ål[Ãn§z°GêÑAà;û%5=K¸Ø:Õ4 ì¦ô ¥Q§thOø¦'
O#ÐÍ Sw-Z:·0éQ©eS¦í+ú«,kÝÉw|êC'ænbOhÂæ h
¶¨N]D-êðä¦ ¿x·*ºù¾'Yý*âé2àé«x§DïFºQWþHC¡ì?
hDëj´Kl¤±>6úéiêÒÈ,5áÑCKlbU`»á2Ây/áQïþ×5x·8/5µJÁyÂ÷;Íej
¼j
/Ø:»}EïdáñÝ"Þ;ßôýþÛÿ¤Ã!òßÑEfÉ-î.NÀiOî93iw ,ïî»×Ë»-OîÅaÏêé=R¡B$¸'æ>´õ§ÀP@np ñE÷FÐþWn«ÑÝP£»±ííÛ¿¨¸v|ªû$·1:û0FG
Î7QçK¾M÷nÃ` íÞv¸V|ÝôFD(²Q¦Jµ£ËkÄú~,dÒ6J¼Íߤýâ«@
©ãæsr!ô>çE[çÞÞ<Ä{UÒ&Á¯]
*Ñ«ù5Ìëe!!t§óËÁÙvõÕÁæSVÅ ±up¥@0,dì<#Û Ô0¢BF;_U%0$ë+4lÍY¾²ÊLnspXx Þ¯ªâZjUÍõ
ÿVÇÝpp1:Ýa´t¶_U%S¡õAÊÈÊèÆÓá¾Û}ì*B7©IiÝëñ»ÙðÍìÕÕàbiÓwOÊ*ÛÙ:h@7N8¸Sì ¬¯M,!BWEqò Û¨£þ¶â¼6 þû8úùb;
æã"OÄñN¤D=yÝp¢"ßù?ÑhéC ,eCÚÏ(ÿ¿;?ßþÞà{Å&_
ÿzË0={{é :ðö]å½w](<5 -§#@'nx|³F®öf0ySÌf*²ÂËMOÙX9lÞÃÒò-]
JL>\èæbEæ.³Ê®+ÙhÆléÕtð²MǺ¤Y¾mí[³%?ïJ7V÷ëRÝ,Í
À
Ù±$)g3wÙfQÆ6 ÏÙt9¯
H
µµnTMª,i[$æ\s~5< ù$Lþ[Zh0[·[¥(6¶b»'Íظ§ØÒc²
F2¶ÎÓxÝÌK:zG뢹tõÖEs/é ê% æ^Ò9ÔKZͽDE.Øeì
o¯._¿ M'Elib¸*/%De CÎZ
ØHʦ
ͱ@· 6l³áw &
Ù [±¥èÛÑÜX8¸oaI¡uáíY²J79âøÐpMÙ°
)àg
¢oÑn2D¡k7dKù¬Ð°J
wbNÊÙd,73 fbvMóªØÒÄ3+²ì³>S(Í¡÷
n\=£·å¾e&ؽÀ\%YÆ#˳¶v¯F¹øÂHKMLæQ=vÚ!³æÈ»sñÍË°2MÍÃÂ
çÏbôÏïÄÖÿUÛ¬XzÅ´¹yÚ~&
³ßÙOjMg&ãtô~Ê>©khØãh°×¿|9;LKæP³Ùõ²µ´6ÉM(ÅÚЦÑr4½Eâ:M/NçáRL¹3Ù7
íÙÿ>I¨+¢èÅëóÑËÓ~é=ÚÙßèm À<}?$ÖlæÞßCnd8<\0},¯;äNÝ ÍIW=\¨S?Þª_ÏC
Ì[ÐçDÞVEY[Æ6:GÓÙàêjðáxk
^å¬MQmÉßW8Ò-è,ÇM8:zP
ò8åq·Q6ò°ÆÒ0
úÂ7ÐÑjÅõxçþEiÊ_átÍêx'¾j÷rª) .
@ÜFêæ1¸dcu#Ë®4L§
Ã-\snÃñtж@::z{>}}9Ý7ôl5E!
Òñ]í¨n²¶ÎLWP»ÉT¿a£a }ñ6fM[ @$ç^cesôM^) kê7U4n!ì{ Oµt;
Úw¾Ö¾DóÁëÉf/Gã³ÙøòoÍï;Ì ï ½óë¸Êºy
'[M>Þ3´.ê¼kª¿¿»ØàЦhêû!r~YZSMª@xSM2g9½|·ã.Doêm
¼;÷þVɼY³¶GåÚ my÷,!|Oʤ~x·ôP°ìÜ÷,o\~ZhéâL.»Æòîî7g"v£@=²Wv
FÜüêÇÊ~3Îä üòÝèül6:CGwËà¢(ÑT80V³ããoT ÌêûH÷\Ïúkê¦O©¯9Ôµ N ÃÐ
ÛØ%áe·6>d"ÉÁÇã
ÆLÊ\fù¾"3×÷_ÏòÚøIvk©ÈÙ^õÃ]z¸Kké0ï³;e±Æ[³×;[Ï6óUÝ6«ç«]õh@¯ã¨Û°Ù46=ÖËB¢£ìÆuYòRÉs¼)fý÷ÕÂüÑw2··êÔ>lÍS\SÎA9ôï÷H:X<õKQè³WSÎãö
é.³}\xÕÌHôrm°j½« å67×d lÖË5Á´ië7j«r ÖobñBæ&/û¿ÍÔÚqZÎ ¶,Þw=
õ5å îçç`Úà _ãs·GuÔ_
áÄüY´õéA1_>
³UMi¨UÌNìc²¦ëþÊ}ù|j·/ß)¸vÝY, ÃÊÓ%àR{-Qr)µ^BÕÖYþ2\
´EbT2yR³,ú¶,Y&«Â¢eâ¸ÛâÐ*£@ ZjJÍÌ(\e·Zn¸¸U1v»7â¾ëÝ-nÿ²z\©*ÛÒ°®î½§ey¼M×{
Ã×u"tàÖ1Ì#¨n0Q(¡6ÆH.÷VÃW ¬|C(XùE(Nñä«mp``´{!±Wklu©MI&¤DSÒ
PÁi´3Ü÷^×Á2H$¤DDR' {
Jm´=Îê¨ÖÖP
*aWFÞ{PÖ¨Ù§k
ùÞÞ§ÖyBØîÖÍÞ®BëT¡m=dC+ÄkÛé`ä©wÍæÉKú|E'N<EÈÂúÇ¡àÿèÁg}4¢0áE=¾¨îWÃd°DÉ@êëS3KÎ̬³7â IéQèïÐMõ«ÝB5LuëÔ¤yt¨*øE¦©S&ÚQ×ÁÂ,S×LßÕå(|ÝPÿ4y`¤½y ,ïbèÒ"Ó0eÖÆÓù}O¡¾oȱ9qaú U|ê;bWÆè
R85¬ap¢ýu:XiO°L· Q Y,ÙLTÖ
U
1
´¿P ö̾ "Y&-±gº*QcÏÎ=ázÏâ¦WmÏ_¯lÖ¼@úg{s³Û
Û0ÌÏôæ¦mK7?ÇJlrØbSú¾]ómáWÏêÈ?¡]ÀÌGÎ~ gÊ'ÐÄ
ÄÒ[§bôo¿Äé¹îbsî
ôÚ¸ÇçAÜôÒëzatý×<ÙRN> ¯+_ éË÷åó
ù°BÜÏõ%tô´êGùÏêÕ~ú2÷·ïFa$ýõ{ØÖ¸'Aw¹7}C2^$ÝzU8cZ/*úa9ÐU+©ÝTðàEÞÎÈë±ûâ" Í
#¯ð¢,àA¸+K!º«×ÙOÖ ü'ºwÒ̽b×P&-7ôfÞªócBóÅpäEüQ1*
· Ì?ÒóëpVÅz'_H¶Ç%ÿÅ Soûh7NS_X ½H½· 0ÄÓêm%*exTé|aAdÊËð
mvXtü2 ˽Nþ J/t
hçVý|FÚùêþµ>5xÍçê «AMîøõÙüiÄÁ"óR´ø6HDe×Åè(vÃRPü ÍÃO";~,
fõÅã¯Û|ݤ;Äp¿ìö$ÛnO¢µÛDÛÙ§äíI
kw,yÜö$Ör{5õ¡Û2ÖìXòÿg{õbDíIÖÝäëö$íIÆÛ/8lOb¸O´=I%[¶=IÊöÛT±e;NdlO±=IÛj_ÌO°=I%[¶/IÆöÛT²eûdlO°=I%[º/IƶÞx"c;d{V^òèíIj¼ â%C½ â%C½ â%C½ â%åÛT±eûà§Û¤l³=Áö$lé¾$Ý ½=I5ßb{íI*ØVû¬u{üö$UllÇKb{*¶l_nÝduo§:d*d¥É`úF2JÔ Ïz
[
Bug#962448: mailing-list-obsolete-in-debian-infrastructure: Please ignore the Debian Java Maintainers address
Hi Chris, On Mon, Jun 8, 2020 at 7:24 AM Chris Lamb wrote: > > (Felix, please consider reverting your change to 12cd485d until we > have consensus here.) Forgive me, but I do not follow your logic. We do not fix experimental tags? How are they supposed to get better? I would agree to a reversal only if the tag becomes a classification. Kind regards Felix Lechner
Bug#962475: ITP: pyct -- Python packaging Common Tasks
Package: wnpp Severity: wishlist Owner: Sebastien Delafond * Package name: pyct Version : 0.4.6 Upstream Author : PyViz * URL : https://github.com/pyviz-dev/pyct * License : BSD-3 Programming Lang: Python Description : Python packaging Common Tasks A utility package that includes: * pyct.cmd: Makes various commands available to other packages. (Currently no sophisticated plugin system, just a try import/except in the other packages.) The same commands are available from within python. Can either add new subcommands to an existing argparse based command if the module has an existing command, or create the entire command if the module has no existing command. Currently, there are commands for copying examples and fetching data. See * pyct.build: Provides various commands to help package building, primarily as a convenience for project maintainers.
Bug#962472: ITP: param -- Make your Python code clearer and more reliable by declaring Parameters
Package: wnpp Severity: wishlist Owner: Sebastien Delafond * Package name: param Version : 1.9.3 Upstream Author : HoloViz team * URL : https://github.com/holoviz/param/releases * License : BSD-3 Programming Lang: Python Description : Make your Python code clearer and more reliable by declaring Parameters Param is a library providing Parameters: Python attributes extended to have features such as type and range checking, dynamically generated values, documentation strings, default values, etc., each of which is inherited from parent classes if not specified in a subclass.
Bug#962473: fonts-konatu: please mention in short/long description that font is japanese
Package: fonts-konatu Version: 20121218-10 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Looking at the Homepage, this font seems to mainly cover glyphs for japanese scripts. Please mention that in short and/or long description. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl7eTDUACgkQLHwxRsGg ASFOBQ/9E0WVXFghRUTm3GCCxNUsi0QNeKTQQK4O/xmpL8SwvPzWxCrSmVYFldGr llvPtvSbjlZuARQHmegoheyrOD2+xcwH+9W3wbnDwneyHiS3RhKDKQACpcS5ram9 MTLu8BshXSTWUTTwo7/I/TGLAZ0Q3rz9GR03568oX060bAvphMqUld6UShlISPgl tn2eFaYqRXv1Y/4hCcvGuniWKEQJ65uxhefbghxBKZPMj+Gb2isZoxvPeg5YrlA8 c7MDtLf7KSvsEhZ7hUBTUBIb13Q4plTyPDnA22rRXJm06DkgP0HWZ0C+SdstwKdT XmuQs4623Ue+/kdWdVoKMj6USBKKFkKMBm/hwYCX6ssVkevA3HQ4lrKQcJ9AhtAa xYP2CkV3EJJw15RO2PMdeXfAeiE/xkZ21uu9i3E6Tnrk0bNp2m9R1e/Fb73BlSoM q8Y4sqBtvB4ihmwOfes2xU1jdAF8dxJR+obRBmyvS4HYO+cZHseC41qzeBrxNjWA /H4kIPU536/R9TyS77rkfUOJn1hArsh8g9SqUQYiP111S0sGw3qdHXc7wwzmF2hu J0qxlFA7hgIhhhuU+4QFigCmx9ByzpTSjTV19Xhv6nljZLHjlXT/SKtMFGDAJE+X 6+uafkqq0JEPVcpHqF1ErCMUuQoVMazCfLdBFBJDKglUMRVa71U= =Ub1e -END PGP SIGNATURE-
Bug#962177: epiphany-browser: Does not recognize djview-plugin
On Thu, Jun 04, 2020 at 11:08:36AM +0200, Janusz S. Bień wrote: > According to Léon Bottou it should do and really does on Ubuntu 18.04: > > https://sourceforge.net/p/djvu/bugs/319/#c805/b347 > > Although djview-plugin is installed, about:plugins shows nothing and the > DjVu documents are downloaded, not opened. > > When I start epiphany browser, I get Epiphany removed support for NPAPI plugins a couple of years ago, but as far as I'm aware WebKitGTK still supports them (as long as they don't use GTK2), so maybe you can try with a different webkitgtk-based browser. Berto
Bug#962448: mailing-list-obsolete-in-debian-infrastructure: Please ignore the Debian Java Maintainers address
tags 962448 + moreinfo tags 962448 - pending thanks Hi, > mailing-list-obsolete-in-debian-infrastructure Debian Java > Maintainers > > The address is valid and the team doesn't plan to migrate 1000+ packages > to a different address. You appear to be running Lintian configured to show "Experimental: yes" tags. This is not recommended and you are likely seeing many other completely bogus or otherwise unactionable tags. Experimental tags are mostly a development/debugging aid — a way to have tags implemented but hidden from users for the time being or just to see how many packages would be affected. A playground or zoo of sorts, and not something developers should care about or even see when preparing packages. Putting it another way, I agree about not migrating so many packages, but that is exactly why it's an experimental tag. Indeed, there is nothing special about the Java team's packages here when you look at it this way; I am sure there are other teams this would apply to. I would therefore suggest that the fix here is actually that you do not run Lintian in "experimental" mode. If there are tags in that mode that you find useful, do let us know as this is a sign that they should be promoted.. rather than maintain a specific "allow" list. (Felix, please consider reverting your change to 12cd485d until we have consensus here.) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#950646: Update on this issue?
I experience the same problem. Any update or feasible workaround is appreciated.
Bug#962470: krb5: binary-all FTBFS
Thanks. I am in the middle of fixing. Apologies I didn't get a fix uploaded before you filed a bug.
Bug#962471: unattended-upgrades: Duplicate log lines
Package: unattended-upgrades Version: 2.4 Severity: normal Dear Debian folks, Looking through `/var/log/unattended-upgrades/unattended-upgrades.log`, there are duplicate lines (last four warning lines): 2020-06-06 15:48:38,161 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2020-06-06 15:48:47,354 INFO While building minimal partition: cache has not allowed changes 2020-06-06 16:02:43,082 INFO All upgrades installed 2020-06-06 16:02:46,990 WARNING Keeping auto-removable libboost-system1.67.0 package(s) because it would also remove the following packages which should be kept in this step: libboost-chrono1.67.0 liborcus-0.14-0 2020-06-06 16:02:47,623 WARNING Keeping auto-removable libboost-filesystem1.67.0 package(s) because it would also remove the following packages which should be kept in this step: liborcus-0.14-0 2020-06-06 16:02:50,622 WARNING Keeping auto-removable libboost-iostreams1.67.0 package(s) because it would also remove the following packages which should be kept in this step: liborcus-0.14-0 2020-06-06 16:02:53,437 INFO Packages that were successfully auto-removed: libboost-date-time1.67.0 libboost-locale1.67.0 libboost-thread1.67.0 python3-gst-1.0 2020-06-06 16:02:53,437 INFO Packages that are kept back: libboost-filesystem1.67.0 libboost-iostreams1.67.0 libboost-system1.67.0 2020-06-06 16:02:53,636 INFO Package cpp-8 is kept back because a related package is kept back or due to local apt_preferences(5). 2020-06-06 16:02:53,662 INFO Package gcc-8-base is kept back because a related package is kept back or due to local apt_preferences(5). 2020-06-06 16:02:53,710 INFO Package libboost-dev is kept back because a related package is kept back or due to local apt_preferences(5). 2020-06-06 16:02:53,733 INFO Package libgcc1 is kept back because a related package is kept back or due to local apt_preferences(5). 2020-06-06 16:02:53,793 INFO Package libmpx2 is kept back because a related package is kept back or due to local apt_preferences(5). 2020-06-06 16:02:53,979 INFO Package sshfs is kept back because a related package is kept back or due to local apt_preferences(5). 2020-06-06 16:02:59,108 INFO Checking if system is running on battery is skipped. Please install powermgmt-base package to check power status and skip installing updates when the system is running on battery. 2020-06-06 16:02:59,113 INFO Starting unattended upgrades script 2020-06-06 16:02:59,113 INFO Allowed origins are: origin=Debian,codename=sid,label=Debian, origin=Debian,codename=sid,label=Debian-Security, origin=Debian,codename=sid-security,label=Debian-Security 2020-06-06 16:02:59,113 INFO Initial blacklist: 2020-06-06 16:02:59,114 INFO Initial whitelist (not strict): 2020-06-06 16:03:00,568 WARNING package cpp-8 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2020-06-06 16:03:01,885 WARNING package cpp-8 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2020-06-06 16:03:07,462 WARNING package libmpx2 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2020-06-06 16:03:08,536 WARNING package libmpx2 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) This is confusing. If the duplicates are useful, it’d be great to have more context in the log. Kind regards, Paul
Bug#962470: krb5: binary-all FTBFS
Source: krb5 Version: 1.17-8 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=krb5=all=1.17-8=1591623815=0 ... dh_clean build-indep-stamp debian/rules build-indep cd build/doc && make PYTHON=python3 substhtml substpdf /bin/bash: line 0: cd: build/doc: No such file or directory make: *** [debian/rules:57: build-indep-stamp] Error 1
Bug#960756: python-biopython FTBFS on 32bit: test_NCBI_BLAST_tools.BlastDB failures
Hi, any voluntee to follow this hint of upstream? > Perhaps makeblastdb itself failed (and our wrapper didn't notice)? Those > are the first files looked for after calling makeblastdb, to see if it > could make a BLAST database. Are there any GenBank/NC_005816.fna.n* or > GenBank/NC_005816.faa.p* files present? > > If it helps, the commands our script was trying to run were: > > $ makeblastdb -dbtype nucl -in GenBank/NC_005816.fna \ > -parse_seqids -hash_index -max_file_sz 20MB -taxid 10 > > and: > > $ makeblastdb -dbtype prot -in GenBank/NC_005816.faa \ > -parse_seqids -hash_index -max_file_sz 20MB -taxid 10 > > I'm not sure I have remote access to any 32bit machines right now... Kind regards Andreas. -- http://fam-tille.de
Bug#961798: python-pyaudio: FTBFS for doc package
Tags: patch The attached patch fixes the issue. The problem is that libjs-jquery doesn't contain files relevant here anymore and uses symlinks itself instead. Which dh_linktree doesn't seem support. Switching to node-jquery and the relevant path fixes the build error Index: python-pyaudio-0.2.11/debian/control === --- python-pyaudio-0.2.11.orig/debian/control +++ python-pyaudio-0.2.11/debian/control @@ -2,7 +2,7 @@ Source: python-pyaudio Section: python Priority: optional Standards-Version: 3.9.8 -Build-Depends: python3-all-dev, debhelper(>= 9), portaudio19-dev, python3-sphinx, dh-linktree, dh-python, libjs-jquery, libjs-underscore +Build-Depends: python3-all-dev, debhelper(>= 9), portaudio19-dev, python3-sphinx, dh-linktree, dh-python, node-jquery, libjs-underscore Maintainer: Hubert Pham Uploaders: Felipe Sateler , Justin Mazzola Paluska Homepage: https://people.csail.mit.edu/hubert/pyaudio/ Index: python-pyaudio-0.2.11/debian/python-pyaudio-doc.linktrees === --- python-pyaudio-0.2.11.orig/debian/python-pyaudio-doc.linktrees +++ python-pyaudio-0.2.11/debian/python-pyaudio-doc.linktrees @@ -1,3 +1,3 @@ -replace usr/share/javascript/jquery usr/share/doc/python-pyaudio-doc/docs/_static +replace usr/share/nodejs/jquery/dist usr/share/doc/python-pyaudio-doc/docs/_static replace usr/share/javascript/underscore usr/share/doc/python-pyaudio-doc/docs/_static
