Bug#986180: Correction - current version on my system is 2.31-9
Small typo in the description above: my current installed version is 2.31-9, not 2.31-8 as stated in the description. i.e., Upgrade 2.31-9 -> 2.31-10 fails
Bug#986146: unblock: rabbitmq-server/3.8.9-2
Hello, Awesome, thanks for this upload, Thomas. I can confirm that this is a pure bug-fix release only and indeed fixes the problems raised, thereby making this package even better for bullseye. A huge +1 for unblocking. - u
Bug#986166: systemd: 'systemd --user' not functional. Regardless of user, org.freedesktop.systemd1 exits with status 1
Detail is provided to avoid https://xkcd.com/979/ from happening to anybody in the future. After a chat on IRC, we tested our a few scenarios, and found that _local_ users worked fine. The users that didn’t work were the LDAP users, which wouldn’t load systemd-user. I tried adding the one-shot at https://src.fedoraproject.org/rpms/nss_nis/blob/rawhide/f/nss_nis.conf to try a different restriction for the NSS service and systemd-user would work, however other things broke. We eventually determined that the end problem wasn’t systemd-user, but rather the local LDAP configuration, which is _old_, and uses services that probably should be replaced with sssd. That’s exactly what I did, and now sssd gets the users properly, and systemd-user starts with no problems. Of note is https://github.com/systemd/systemd/blob/v248/NEWS, which has a warning that: NOTE: This has a chance of breaking nss-ldap and similar NSS modules that embed a network facing module into any process using getpwuid() or related cal Which is exactly what happened. This issue can be closed. > On Mar 30, 2021, at 12:22 PM, Michael Biebl wrote: > > Am 30.03.2021 um 20:14 schrieb Troy Telford: >> Package: systemd >> Version: 247.3-3 >> Severity: normal >> Dear Maintainer, >>* What led up to the situation? >> This was probably due to an apt update/upgrade. I haven't been configuring my >> system, but about two weeks ago, "systemd --user" stopped working entirely - >> none of the user units start up upon user login. The first thing I noticed is >> no sound, but it didn't take long to find that systemd wasn't running any >> user >> units. >>* What exactly did you do (or not do) that was effective (or ineffective)? >> Initially, I found that XDG_RUNTIME_DIR wasn't being set anymore -- so I >> added >> `export XDG_RUNTIME_DIR=/run/user/$(id -u)` to my .xsessionrc. It didn't fix >> the issue for login, but I could at least run `systemd --user` and start up >> the >> processes after login. However, even that is broken now: I invariably get >> "Process org.freedesktop.systemd1 exited with status 1" >> /var/log/daemon.log has a corresponding message from DBUS about >> org.freedesktop.systemd1 being activated, but dying: >> Mar 30 12:08:01 pilot.pariahzero.net dbus-daemon[2025881]: [session uid=1000 >> pid=2025879] Activating service name='org.freedesktop.systemd1' requested by >> ':1.155' (uid=1000 pid=2433850 comm="systemctl --user --failed ") >> Mar 30 12:08:01 pilot.pariahzero.net dbus-daemon[2025881]: [session uid=1000 >> pid=2025879] Activated service 'org.freedesktop.systemd1' failed: Process >> org.freedesktop.systemd1 exited with status 1 >> The problem happens for all users on the system. >> I'll see if I can get more verbose logging to give any additional details >> about >> why org.freedesktop.systemd1 is exiting. If you know offhand, I'd definitely >> give it a try. > > What's the output of > apt-cache policy dbus-user-session > apt-cache policy dbus-x11
Bug#986177: unblock: freedombox/21.4.2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: jvalle...@mailbox.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Please unblock package freedombox.
I would like to request an "unblock" in order to shorten the migration
time to testing for freedombox 21.4.2. This is because it includes a
fix for a security issue. The other changes in this version are bug
fixes, documentation updates, and translations updates. Here is a list
of the fixes and links to more information about each:
1. Session hijack in first run wizard
Fix: Use session to verify first boot welcome step.
Security tracker:
https://security-tracker.debian.org/tracker/TEMP-000-3E4AC3
Issue: https://salsa.debian.org/freedombox-team/freedombox/-/issues/2074
Files modified: plinth/modules/first_boot/*
2. Deluge daemon user not in freedombox-share group
Fix: Add to freedombox-share group before running app setup.
Merge request:
https://salsa.debian.org/freedombox-team/freedombox/-/merge_requests/2042
File modified: plinth/modules/deluge/__init__.py
3. Permission denied writing to Samba share
Fix: Make file-sharing services depend on nslcd.service.
Issue: https://salsa.debian.org/freedombox-team/freedombox/-/issues/2061
Merge request:
https://salsa.debian.org/freedombox-team/freedombox/-/merge_requests/2041
Files modified:
plinth/modules/{deluge,mldonkey,syncthing,transmission}/data/lib/systemd/system/*.service.d/freedombox.conf
4. Flaky tests related to user home directory
Fix: Don't depend on particular user to be running tests.
Issue: https://salsa.debian.org/freedombox-team/freedombox/-/issues/2014
Merge request:
https://salsa.debian.org/freedombox-team/freedombox/-/merge_requests/2043
Files modified: plinth/modules/config/tests/*
5. Documentation and translation updates
Files modified: doc/*, locale/*
unblock freedombox/21.4.2
-BEGIN PGP SIGNATURE-
iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmBjnK8WHGp2YWxsZXJv
eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICHbND/4gdjbRuBLfumrsnT3PHZNhZNjH
39jjVI0FmFhJNnhuuNqPutFrHpu4dnXH4n6NoxoAyyJ0UkrOVlQNIQTmxZgjlUSo
u6khiPe2ziHaaxbKVzBrHABWt3sB2T194Fix52+QZESZNtgUpPnC9lPtHibBwZM2
f/tsOV+xROlmb8tDDVdDyLyQCInvdN4vL+pbvVXqf+WseMbtOIyMPAdJxuy2b4xf
JOzjP/pTyHAC8M6M2KD5R5JwaNie416j+x0ES8Ghkaabucp977bXoQqgZBcAZNyT
YWbPxXAksgX53CXOrsaElBnX9SBU8pqsEO40Nw/V+Oow4sAKWRDU/xtV+YRKbGA5
ij0PXb5pbzQdkKTE6EG+vr19kEDjDSd1+tAKtjH9hh76/SuP4T5K+YNyo+hClaxd
ee/TPXqbA5Nu6oSlIXlWgn4ipff/Tq9L2iTtqQ1alC2R4UV7abt5yFOtgQdJyOgF
eowYEYTZjDhZ4DG8oPX2a8Tr0BMQgVI2mRs8b4lrhZ0LF93E23qrOFBzsxPg/Vn9
jZYgfd0Iw36gPROFzQEt3F9Ox5FVOH0Id1X4Qe0+WmNBhe04ZEQqLZfclaVha6dG
/MAUYBNS3/ZFnrjHVccw3/8kasCVuYMjxrE+BVgTHD+LgH63OrUi0Q88q0zV8aqF
B7q8fB+d8z97cfhUjw==
=qdTO
-END PGP SIGNATURE-
diff -Nru freedombox-21.4/debian/changelog freedombox-21.4.2/debian/changelog
--- freedombox-21.4/debian/changelog2021-02-28 20:57:00.0 -0500
+++ freedombox-21.4.2/debian/changelog 2021-03-28 09:23:46.0 -0400
@@ -1,3 +1,61 @@
+freedombox (21.4.2) unstable; urgency=high
+
+ [ Burak Yavuz ]
+ * Translated using Weblate (Turkish)
+ * Translated using Weblate (Turkish)
+
+ [ nautilusx ]
+ * Translated using Weblate (German)
+
+ [ Michalis ]
+ * Translated using Weblate (Greek)
+
+ [ Reza Almanda ]
+ * Translated using Weblate (Indonesian)
+
+ [ Kirill Schmidt ]
+ * first_boot: Use session to verify first boot welcome step
+
+ [ James Valleroy ]
+ * doc: Fetch latest manual
+
+ -- James Valleroy Sun, 28 Mar 2021 09:23:46 -0400
+
+freedombox (21.4.1) unstable; urgency=medium
+
+ [ Dietmar ]
+ * Translated using Weblate (German)
+
+ [ Karol Werner ]
+ * Translated using Weblate (Polish)
+
+ [ Michalis ]
+ * Translated using Weblate (Greek)
+ * Translated using Weblate (Greek)
+
+ [ Fioddor Superconcentrado ]
+ * Generating developer documentation.
+ * config: Fix tests related to user home directory
+ * Translated using Weblate (Spanish)
+
+ [ ikmaak ]
+ * Translated using Weblate (Dutch)
+
+ [ Burak Yavuz ]
+ * Translated using Weblate (Turkish)
+
+ [ Veiko Aasa ]
+ * deluge, mldonkey, syncthing, transmission: Depend on nslcd.service
+ * deluge: Fix daemon user not in freedombox-share group after installation
+
+ [ Michael Breidenbach ]
+ * Translated using Weblate (Swedish)
+
+ [ James Valleroy ]
+ * doc: Fetch latest manual
+
+ -- James Valleroy Sat, 13 Mar 2021 11:55:40 -0500
+
freedombox (21.4) unstable; urgency=medium
[ Petter Reinholdtsen ]
diff -Nru freedombox-21.4/doc/manual/en/Contribute.raw.wiki
freedombox-21.4.2/doc/manual/en/Contribute.raw.wiki
--- freedombox-21.4/doc/manual/en/Contribute.raw.wiki 2021-02-28
20:57:00.0 -0500
+++ freedombox-21.4.2/doc/manual/en/Contribute.raw.wiki 2021-03-28
09:23:46.0 -0400
@@ -24,88 +24,125 @@
As a new contributor, you are more than welcome to introduce yourself to
others on the !FreedomBox
[[https://discuss.freedombox.org/c/development|discussion
Bug#986179: ITP: apksigcopier -- copy/extract/patch apk signatures
Package: wnpp Severity: wishlist Owner: "Felix C. Stegerman" X-Debbugs-Cc: debian-de...@lists.debian.org, f...@obfusk.net * Package name: apksigcopier Version : 0.3.0 Upstream Author : Felix C. Stegerman * URL : https://github.com/obfusk/apksigcopier * License : GPLv3+ Programming Lang: Python Description : copy/extract/patch apk signatures apksigcopier is a tool for copying APK signatures from a signed APK to an unsigned one (in order to verify reproducible builds). Its command-line tool offers three operations: * copy signatures directly from a signed to an unsigned APK * extract signatures from a signed APK to a directory * patch previously extracted signatures onto an unsigned APK The F-Droid reproducible builds & verification effort recently led [1] to the development of apksigcopier. I've started packaging it for Debian [2] and I have an offer from Holger Levsen to sponsor my uploads [3]. - Felix [1] https://lists.reproducible-builds.org/pipermail/rb-general/2021-March/002214.html [2] https://salsa.debian.org/obfusk/apksigcopier/-/commits/debian/sid [3] https://lists.reproducible-builds.org/pipermail/rb-general/2021-March/002215.html
Bug#986143: openstack-dashboard: fails to upgrade from 'buster': KeyError: 'django' in "/usr/lib/python3/dist-packages/django/template/utils.py", line 65
On 30/03/2021 17.33, Thomas Goirand wrote: Ah, sh**... What do you suggest then? (even: what do you suggest I test in a VM...) I just tried all packages involved in the failed upgrade one by one and activated the openstack-dashboard trigger after each one. python3-novaclient is our culprit. Use a buster chroot with openstack-dashboard and install python3-novaclient/bullseye to reproduce. Andreas
Bug#986178: debian-cd: Pass DEBOOTSTRAP_OPTS to all debootstrap calls
Package: debian-cd Version: 3.1.33 Severity: normal X-Debbugs-Cc: j24...@gmail.com Dear Maintainer, Building my own customised installers has lead me to discover that DEBOOTSTRAP_OPTS isn't passed to debootstrap in tools/make_disc_trees.pl , this breaks some more exotic use cases where passing options to DEBOOTSTRAP is required / wanted. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-5-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Enforcing - Policy name: bauen1-policy Versions of packages debian-cd depends on: ii apt2.2.2 ii bc 1.07.1-2+b2 ii bzip2 1.0.8-4 ii cpp4:10.2.1-1 ii curl 7.74.0-1.1 ii dctrl-tools [grep-dctrl] 2.24-3+b1 ii dpkg-dev 1.20.7.1 ii genisoimage9:1.1.11-3.2 pn libcompress-zlib-perl pn libdigest-md5-perl ii libdpkg-perl 1.20.7.1 ii lynx 2.9.0dev.6-2 ii make 4.3-4 ii perl [libdigest-sha-perl] 5.32.1-3 ii tofrodos 1.7.13+ds-5 ii wget 1.21-1+b1 ii xorriso1.5.2-1 Versions of packages debian-cd recommends: ii dosfstools 4.2-1 ii hfsutils 3.2.6-15 ii isolinux 3:6.04~git20190206.bf6db5b4+dfsg1-3 ii mtools 4.0.26-1 ii netpbm 2:10.0-15.4 ii syslinux-common 3:6.04~git20190206.bf6db5b4+dfsg1-3 ii syslinux-utils 3:6.04~git20190206.bf6db5b4+dfsg1-3 debian-cd suggests no packages. -- no debconf information
Bug#982935: Drop-Down Menus are still broken
Update:
My nginx-configuration had a link to /var/lib/mailman3/web/static.
Changing it to /usr/share/python3-django-postorius/static/ solved the
problem:
location /mailman3/static {
# alias /var/lib/mailman3/web/static;
alias /usr/share/python3-django-postorius/static/;
}
The /var/lib/mailman3/web/static has an old bootstrap.min.js stored
under /var/lib/mailman3/web/static/postorius/libs/bootstrap/js. This
file seems to belong to nobody:
# dpkg -S /var/lib/mailman3/web/static/postorius/
dpkg-query: no path found matching pattern
/var/lib/mailman3/web/static/postorius/
# dpkg -S /var/lib/mailman3/web/static
mailman3-web: /var/lib/mailman3/web/static
# dpkg -S /usr/share/python3-django-postorius
python3-django-postorius: /usr/share/python3-django-postorius
I suspect the file was installed at the time I ran Debian stable, as
first installed mailman3 under stable and migrated to testing after it.
I installed mailman3-web on a fresh Debian testing, but the alias in
nginx.conf ist still /var/lib/mailman3/web/static. In the fresh install,
the bootstrap.min.js under
/var/lib/mailman3/web/static/postorius/libs/bootstrap/js is now bootstrap 4.
I don't understand why there are two installations in parallel,
shouldn't everything be installed within the Package
python3-django-postorius?
Cheers,
Robert
Bug#986171: underscore: CVE-2021-23358
Le 30/03/2021 à 21:40, Salvatore Bonaccorso a écrit :
> Source: underscore
> Version: 1.9.1~dfsg-1
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> X-Debbugs-Cc: car...@debian.org, Debian Security Team
> ,y...@debian.org
>
> Hi,
>
> The following vulnerability was published for underscore.
>
> CVE-2021-23358[0]:
> | The package underscore from 1.13.0-0 and before 1.13.0-2, from 1.3.2
> | and before 1.12.1 are vulnerable to Arbitrary Code Execution via the
> | template function, particularly when a variable property is passed as
> | an argument as it is not sanitized.
>
> [1] provides a POC to verify the issue.
>
>
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
>
> For further information see:
>
> [0] https://security-tracker.debian.org/tracker/CVE-2021-23358
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23358
> [1] https://snyk.io/vuln/SNYK-JS-UNDERSCORE-1080984
>
> Regards,
> Salvatore
Hi,
here is a debdiff for buster including:
* backport of upstream patch
* autopkgtest file (tested)
Cheers,
Yadd
diff --git a/debian/changelog b/debian/changelog
index 02cd807..eb9fd68 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+underscore (1.9.1~dfsg-1+deb10u1) buster-security; urgency=high
+
+ * Team upload
+ * Fix arbitrary code execution (Closes: #986171)
+
+ -- Yadd Tue, 30 Mar 2021 22:54:09 +0200
+
underscore (1.9.1~dfsg-1) unstable; urgency=medium
[ upstream ]
diff --git a/debian/patches/CVE-2021-23358.patch
b/debian/patches/CVE-2021-23358.patch
new file mode 100644
index 000..2ba4118
--- /dev/null
+++ b/debian/patches/CVE-2021-23358.patch
@@ -0,0 +1,62 @@
+Description: fix arbitrary code execution
+Author: Julian Gonggrijp
+Origin: upstream, https://github.com/jashkenas/underscore/commit/4c73526d
+Bug: https://snyk.io/vuln/SNYK-JS-UNDERSCORE-1080984
+Bug-Debian: https://bugs.debian.org/986171
+Forwarded: not-needed
+Reviewed-By: Xavier Guimard
+Last-Update: 2021-03-30
+
+--- a/underscore.js
b/underscore.js
+@@ -1550,6 +1550,13 @@
+ return '\\' + escapes[match];
+ };
+
++ // In order to prevent third-party code injection through
++ // `_.templateSettings.variable`, we test it against the following regular
++ // expression. It is intentionally a bit more liberal than just matching
valid
++ // identifiers, but still prevents possible loopholes through defaults or
++ // destructuring assignment.
++ var bareIdentifier = /^\s*(\w|\$)+\s*$/;
++
+ // JavaScript micro-templating, similar to John Resig's implementation.
+ // Underscore templating handles arbitrary delimiters, preserves whitespace,
+ // and correctly escapes quotes within interpolated code.
+@@ -1585,8 +1592,17 @@
+ });
+ source += "';\n";
+
+-// If a variable is not specified, place data values in local scope.
+-if (!settings.variable) source = 'with(obj||{}){\n' + source + '}\n';
++var argument = settings.variable;
++if (argument) {
++ // Insure against third-party code injection.
++ if (!bareIdentifier.test(argument)) throw new Error(
++'variable is not a bare identifier: ' + argument
++ );
++} else {
++ // If a variable is not specified, place data values in local scope.
++ source = 'with(obj||{}){\n' + source + '}\n';
++ argument = 'obj';
++}
+
+ source = "var __t,__p='',__j=Array.prototype.join," +
+ "print=function(){__p+=__j.call(arguments,'');};\n" +
+@@ -1594,7 +1610,7 @@
+
+ var render;
+ try {
+- render = new Function(settings.variable || 'obj', '_', source);
++ render = new Function(argument, '_', source);
+ } catch (e) {
+ e.source = source;
+ throw e;
+@@ -1605,7 +1621,6 @@
+ };
+
+ // Provide the compiled source as a convenience for precompilation.
+-var argument = settings.variable || 'obj';
+ template.source = 'function(' + argument + '){\n' + source + '}';
+
+ return template;
diff --git a/debian/patches/series b/debian/patches/series
index da362d2..7ddac86 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
2001_docs_privacy.patch
+CVE-2021-23358.patch
diff --git a/debian/tests/CVE-2021-23358 b/debian/tests/CVE-2021-23358
new file mode 100755
index 000..a2ae590
--- /dev/null
+++ b/debian/tests/CVE-2021-23358
@@ -0,0 +1,11 @@
+#!/bin/sh
+
+if node debian/tests/CVE-2021-23358.js 2>/dev/null; then
+ rm -f HELLO
+ echo 'Vulnerable to CVE-2021-23358' >&2
+ exit 1
+else
+ echo
+ echo 'Not vulnerable to CVE-2021-23358'
+ exit 0
+fi
diff --git a/debian/tests/CVE-2021-23358.js b/debian/tests/CVE-2021-23358.js
new file mode 100644
index 000..fad7c77
--- /dev/null
+++ b/debian/tests/CVE-2021-23358.js
@@ -0,0 +1,3 @@
+const _ = require('underscore');
+_.templateSettings.variable = "a =
Bug#986176: openuniverse runs with crippled GUI, then crashes.
Package: openuniverse version: 1.0beta3.1+dfsg-6.1 When I started openuniverse, it put up a window with no menu items and no other control elements. It responded to '?' or 'H' keystrokes by putting up a short list of keystroke shortcuts - presumably corresponding to nonexistent menu options. These keystroke shortcuts seemed to work, but within a few minutes openuniverse crashed. I started it a few more times trying for a while to figure out what I did that made it crash, but it seemed random. Finally I started it and went looking online for any discussion of the problem. It crashed after no more than 5 minutes, before I had even turned away from the browser and tried to do anything with it. So I'm pretty sure it's not something I did. In dmesg it says: [406058.660546] openuniverse[242638]: segfault at 20 ip 7f86f454ad63 sp 7ffefd7050a0 error 4 in nouveau_dri.so[7f86f4517000+d46000] [406058.660565] Code: 48 48 89 c7 b9 02 00 00 00 ff 90 08 03 00 00 4c 8b 54 24 10 be ff 00 00 00 48 89 c7 49 89 82 70 12 00 00 49 8b 82 60 12 00 00 <8b> 50 20 c1 e2 05 e8 52 c9 fc ff 4c 8b 54 24 10 48 89 ea 4c 89 fe Which appears to implicate a conflict with nouveau. I have an nvidia 1050TI video card but I have not downloaded drivers from nvidia's site for it. OpenUniverse documentation strongly suggests the proprietary drivers I am not using. I am not familiar with openuniverse, but checking screenshots of it online I see many UI elements that simply are not present when I start it. It's even missing a basic icon for a launcher shortcut. Checking dependencies I see that it conflicts with openuniverse-common(<=1.0beta3.1-3). I have installed version 1.0beta3.1+dfsg-6.1. That looks to me like it should not have installed with the current version of openuniverse-common, but these version numbers are inconsistent in format so I'm not certain. Checking dependencies I also see that it requires libjpeg26-turbo >= 1.3.1 and my installed version is 1:2.0.6-4. Again it looks to me like it shouldn't have installed with this version, but because of the inconsistency in version number format I'm not sure. Finally I see in its dependencies that it suggests package 'celestia' which has no installation candidate in the Testing/Bullseye release. This is very sad. I like Celestia. I miss it ever since Jessie. I have sometimes gone out and gotten the .deb from their site and installed it - but not yet this time. I tried openuniverse first looking for an adequate in-distro replacement. This is a fresh install of Bullseye, made using 'grml-debootstrap' less than a week ago. I have absolutely no software installed on this machine that is not downloaded from the 'Bullseye' archive. Packages openuniverse depends on: openuniverse-common: Installed version is 1.0beta3.1+dfsg-6.1 freeglut3 >= 2.8.1: Installed version is 2.8.1-6 libc6 >= 2.14: Installed version is 2.31-10 libgcc-s1 >= 3.0: Installed version is 10.2.1-6 libglu1-mesa | libglu1: Installed version is libglu1-mesa libjpeg62-turbo >= 1.3.1: installed version is 1:2.0.6-4 libplib1: Installed version is 1.8.5-8 libstdc++6 >= 5 : installed version is 10.2.1-6 Hope this helps! Ray "Bear" Dillinger
Bug#986092: RFS: psftools/1.1.1-1 [ITP] -- PSF font tools
On Tue, Mar 30, 2021 at 09:28:22AM +0200, Gürkan Myczko wrote: > > There's a library included -- with headers and stuff, that should go > > into separate packages. > > True, fixed. This looks odd: lrwxrwxrwx root/root 0 2021-03-19 07:07 ./usr/lib/x86_64-linux-gnu/libpsf.so -> libpsf.so.0.1.2 in a binary package with no headers or anything. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ How to squander your resources: those silly Swedes have a sauce ⢿⡄⠘⠷⠚⠋⠀ named "hovmästarsås", the best thing ever to put on cheese, yet ⠈⠳⣄ they waste it solely on mere salmon.
Bug#982935: Drop-Down Menus are still broken
Hello, I'm sorry to inform you that I still have this bug. The Drop-Down-Menus are still not working in postorius. I reloaded the server, cleared my browser cache, tried another browser, nothing helped. I'm using debian testing (up to date), here are the package versions on the system. libjs-bootstrap (version 3) is needed by python3-djangorestframework, I can't deinstall it. # dpkg -l | grep mailman ii mailman3 3.3.3-1 all Mailing list management system ii mailman3-web 0+20200530-2 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django-mailman3 1.3.5-2 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-mailmanclient 3.3.2-1 all Python bindings for Mailman3 REST API (Python 3 version) # dpkg -l | grep postorius ii python3-django-postorius 1.3.4-2 all Web user interface to access GNU Mailman3 # dpkg -l | grep bootstrap ii libjs-bootstrap 3.4.1+dfsg-2 all HTML, CSS and JS framework ii libjs-bootstrap4 4.5.2+dfsg1-6 all HTML, CSS and JS framework Cheers & thanks for maintaining mailman3, Robert
Bug#986175: unblock: underscore/1.9.1~dfsg-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: pkg-javascript-de...@lists.alioth.debian.org
Please unblock package underscore
[ Reason ]
underscore is vulnerable to arbitrary code execution (#986171,
CVE-2021-23358)
[ Impact ]
CVE provided a PoC to prove arbitrary code execution
[ Tests ]
I added a test to prove that bug is fixed (based on PoC). Test fails
with 1.9.1~dfsg-1 and passes with 1.9.1~dfsg-2
[ Risks ]
Patch is trivial. Note: I imported also Janitor changes: this breaks
nothing
[ Checklist ]
[X] all changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in testing
[ Other ]
I downgrade autopkgtest to "superficial" since nothing was really tested
(just a node "require"). That's why I'm filing this ;-)
Regards,
Yadd
unblock underscore/1.9.1~dfsg-2
diff --git a/debian/changelog b/debian/changelog
index 02cd807..fed9aa8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,26 @@
+underscore (1.9.1~dfsg-2) unstable; urgency=medium
+
+ * Team upload
+
+ [ Debian Janitor ]
+ * Bump debhelper dependency to >= 9, since that's what is used in
+debian/compat.
+ * Bump debhelper from old 9 to 12.
+ * Set debhelper-compat version in Build-Depends.
+ * Set upstream metadata fields: Bug-Database, Repository, Repository-
+Browse.
+ * Update standards version to 4.4.1, no changes needed.
+ * Set upstream metadata fields: Bug-Submit.
+ * Update standards version to 4.5.0, no changes needed.
+ * Apply multi-arch hints.
++ node-underscore: Add Multi-Arch: foreign.
+
+ [ Yadd ]
+ * Mark autopkgtest as superficial
+ * Fix arbitrary code execution and add a test (Closes: #986171)
+
+ -- Yadd Tue, 30 Mar 2021 22:40:59 +0200
+
underscore (1.9.1~dfsg-1) unstable; urgency=medium
[ upstream ]
diff --git a/debian/compat b/debian/compat
deleted file mode 100644
index ec63514..000
--- a/debian/compat
+++ /dev/null
@@ -1 +0,0 @@
-9
diff --git a/debian/control b/debian/control
index cb1e7e9..fc1d26b 100644
--- a/debian/control
+++ b/debian/control
@@ -7,11 +7,11 @@ Uploaders:
David Paleino ,
Build-Depends:
brotli,
- debhelper,
+ debhelper-compat (= 12),
node-source-map,
pigz,
uglifyjs (>= 3),
-Standards-Version: 4.3.0
+Standards-Version: 4.5.0
Homepage: https://underscorejs.org/
Vcs-Browser: https://salsa.debian.org/js-team/underscore
Vcs-Git: https://salsa.debian.org/js-team/underscore.git
@@ -44,6 +44,7 @@ Depends:
libjs-underscore,
nodejs,
${misc:Depends},
+Multi-Arch: foreign
Description: JavaScript's functional programming helper library - NodeJS
Underscore is a utility-belt library for JavaScript that provides a lot
of the functional programming support that you would expect in
diff --git a/debian/patches/CVE-2021-23358.patch
b/debian/patches/CVE-2021-23358.patch
new file mode 100644
index 000..2ba4118
--- /dev/null
+++ b/debian/patches/CVE-2021-23358.patch
@@ -0,0 +1,62 @@
+Description: fix arbitrary code execution
+Author: Julian Gonggrijp
+Origin: upstream, https://github.com/jashkenas/underscore/commit/4c73526d
+Bug: https://snyk.io/vuln/SNYK-JS-UNDERSCORE-1080984
+Bug-Debian: https://bugs.debian.org/986171
+Forwarded: not-needed
+Reviewed-By: Xavier Guimard
+Last-Update: 2021-03-30
+
+--- a/underscore.js
b/underscore.js
+@@ -1550,6 +1550,13 @@
+ return '\\' + escapes[match];
+ };
+
++ // In order to prevent third-party code injection through
++ // `_.templateSettings.variable`, we test it against the following regular
++ // expression. It is intentionally a bit more liberal than just matching
valid
++ // identifiers, but still prevents possible loopholes through defaults or
++ // destructuring assignment.
++ var bareIdentifier = /^\s*(\w|\$)+\s*$/;
++
+ // JavaScript micro-templating, similar to John Resig's implementation.
+ // Underscore templating handles arbitrary delimiters, preserves whitespace,
+ // and correctly escapes quotes within interpolated code.
+@@ -1585,8 +1592,17 @@
+ });
+ source += "';\n";
+
+-// If a variable is not specified, place data values in local scope.
+-if (!settings.variable) source = 'with(obj||{}){\n' + source + '}\n';
++var argument = settings.variable;
++if (argument) {
++ // Insure against third-party code injection.
++ if (!bareIdentifier.test(argument)) throw new Error(
++'variable is not a bare identifier: ' + argument
++ );
++} else {
++ // If a variable is not specified, place data values in local scope.
++ source = 'with(obj||{}){\n' + source + '}\n';
++ argument = 'obj';
++}
+
+ source = "var __t,__p='',__j=Array.prototype.join," +
+ "print=function(){__p+=__j.call(arguments,'');};\n" +
+@@ -1594,7 +1610,7 @@
+
+ var render;
+ try {
+- render = new Function(settings.variable || 'obj', '_', source);
++ render = new
Bug#986174: subversion: FTBFS when building with Ruby support disabled
Source: subversion Severity: normal User: debian-i...@lists.debian.org Usertags: ia64 X-Debbugs-Cc: debian-i...@lists.debian.org Hello! Trying to build subversion with Ruby support disabled (i.e. DEB_BUILD_OPTIONS=no-ruby) fails with: /<>/BUILD/../subversion/bindings/swig/proxy/svn_wc_h.swg:290: Warning 900: FIXME: Missing argout typemap /<>/BUILD/../subversion/bindings/swig/proxy/svn_wc_h.swg:295: Warning 900: FIXME: Missing argout typemap cd .. && /usr/bin/python3 build/generator/swig/external_runtime.py build.conf /usr/bin/swig ruby Wrote subversion/bindings/swig/proxy/swig_ruby_external_runtime.swg SWIG ruby disabled at configure time: check config.log for details make[2]: *** [../build-outputs.mk:285: .swig_rb_checked] Error 1 make[2]: Leaving directory '/<>/BUILD' make[1]: *** [debian/rules:242: override_dh_auto_build-arch] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:181: binary-arch] Error 2 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 This was discovered when trying to build subversion for ia64 where Ruby should be disabled by default as Ruby is currently half-broken on this architecture. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#981190: sudo-ldap: Users files sudoers nopasswd stop working after update to 1.8.27-1+deb10u3
On Tue, Mar 30, 2021 at 10:17:11AM +, BRUN Eric wrote: > In my file nsswitch.conf, I have : > > sudoers: files ldap > > Before update, that worked , first try to find account in "files" > and then, if not found, try with ldap accounts. > > After update, it like "files" are ignored and ldap is directly used. > I read logs files for this analyse. This is not how sudo works by default. To quote the sudoers.ldap manpage: Sudo looks for a line beginning with sudoers: and uses this to determine the search order. Note that sudo does not stop searching after the first match and later matches take precedence over earlier ones. I suspect that before the upgrade the LDAP backend returned nothing, and after the upgrade it started to return one or more entries, but since those most likely do not have the "sudoOption: !authenticate" attribute sudo prompts for a password (this was the only way I could reproduce your observed behaviour). These lines in your sudo-ldap-debug.log seem to confirm this: ... sudo: adding search result sudo: result now has 1 entries ... Can you try if putting this sudoers: files [SUCCESS=return] ldap into /etc/nsswitch.conf fixes the issue? This way sudo stops processing if a successful match in /etc/sudoers is found first (this is not mentioned in the manpages, I learned of this by looking at the code). What do the LDAP entries for user nagios actually look like? I do must say though that using /etc/sudoers to specify exceptions to rules in an LDAP backend is an unorthodox way of using sudo with LDAP as it makes troubleshooting very complicated. If you want a command to be runnable only on a subset of hosts then using separate per-host entries in LDAP is the intended way. Otherwise someone looking just at the LDAP output has no way of knowing what other rules might be in effect or if the LDAP backend is overshadowed by a [SUCCESS=return]/[NOTFOUND=return]. Another issue: your sudo-ldap.conf specifies ldap: URIs whereas ldaps: is probably more applicable to ensure TLS. Otherwise an attacker who can manipulate packets in transit could use that to escalate his privileges. Regards, Dennis.
Bug#986172: unblock: dwarf-fortress/0.47.04+dfsg1-1
Control: retitle -1 unblock: dwarf-fortress/0.47.04+dfsg1-1 On Tue, 30 Mar 2021 22:32:08 +0200 Sven Bartscher wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package dwarf-fortress > > [...] > > unblock dwarf-fortress/0.47_04+dfsg1-1 I typoed the package version in my initial report. The version to be unblocked is: unblock dwarf-fortress/0.47.04+dfsg1-1 The updated version has not been uploaded to unstable yet. Regards Sven
Bug#986164: no upload is possible in droopy
Package: droopy Version: 0.20160830-3 Dopo aver avviato droopy, quando si prova
ad uppare un qualsiasi file, la connessione si annulla . Nel terminale da cui
si è eseguito droopy, appaiono queste scritte 192.168.1.xx - - [30/Mar/2021
17:36:02] Started file transfer 192.168.1.xx - - [30/Mar/2021 17:36:02]
TypeError('__init__() takes from 1 to 11 positional arguments but 12 were
given') 192.168.1.xx - - [30/Mar/2021 17:36:02] "POST / HTTP/1.1" 200 - e cosi
via ogni volta che si ritenta e niente viene uppato . Questo succede con
qualsiasi tipo di configurazione viene lanciato droopy. Sul browser (client)
appare "there has been a problem! Retry"
Bug#986118: unblock: rocksndiamonds/4.2.2.1+dfsg-2
Control: tags -1 -moreinfo On Tue, 30 Mar 2021 13:33:55 +0200, Sebastian Ramacher wrote: > On 2021-03-29 21:16:32, Stephen Kitt wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: unblock > > > > Hi, > > > > I’d like to upload an updated version of rocksndiamonds for Bullseye; > > the only change is an updated German debconf translation. The patch is > > attached. > > Looks good. Please remove the moreinfo tag once the new version is > available in unstable. Thanks, uploaded! Regards, Stephen pgpb2ni3Dvg5Y.pgp Description: OpenPGP digital signature
Bug#984975: Fw: Re: Bug#984975: gedit 3.30.2-2 segmentation fault
Sent from ProtonMail, encrypted email based in Switzerland.
‐‐‐ Original Message ‐‐‐
On Monday, March 29, 2021 11:15 PM, wrote:
> Hi Bernhard Übelacker,
> I hope I managed to create a proper backtrace, this is my first time.
>
> As for your question about rebuilt packages, I have no idea when this
> happened. I didn't build many things, I remember building ubuntu's Yaru theme.
>
> Sent from ProtonMail, encrypted email based in Switzerland.
>
> ‐‐‐ Original Message ‐‐‐
> On Sunday, March 28, 2021 11:00 AM, Bernhard Übelacker bernha...@mailbox.org
> wrote:
>
> > Hello Nenad Cvetkovic,
> > I tried to have a look at your core file.
> > It shows a crash with following backtrace [1].
> > The reason seems to be an invalid function pointer in variable "prepare".
> > The upstream issue in [2] shows a similar backtrace, but I
> > am not sure if they are related about what is causing it.
> > Investigation with a core file needs the same installed
> > package version, therefore the inspection at the host
> > creating the core has less chances for discrepancies.
> > Therefore, if you have gdb installed, you should be able
> > to generate a backtrace on your system too by e.g.:
> > coredumpctl list
> > coredumpctl gdb
> >
> > bt
> >
> >
> > This gets normally improved by installing the dbgsym packages
> > or setting the environment DEBUGINFOD_URLS,
> > both and more described in [3].
> > Therefore the question, is there a reason for what looks like
> > local rebuilt packages libenchant1c2a and libxml2
> > due to the "~1.gbp73138d" version postfix?
> > Kind regards,
> > Bernhard
> > [1]
> > Core was generated by `/usr/bin/gedit --gapplication-service'.
> > Program terminated with signal SIGSEGV, Segmentation fault.
> > #0 0x007f198f in ?? ()
> > [Current thread is 1 (Thread 0x7f7cde497a80 (LWP 15100))]
> > (gdb) bt
> > #0 0x007f198f in ?? ()
> > #1 0x7f7ce25f7669 in g_main_context_prepare
> > (context=context@entry=0x55ba65041ad0,
> > priority=priority@entry=0x7ffcb3349aa0) at ../../../glib/gmain.c:3492
> > #2 0x7f7ce25f806b in g_main_context_iterate
> > (context=context@entry=0x55ba65041ad0, block=block@entry=1,
> > dispatch=dispatch@entry=1, self=) at
> > ../../../glib/gmain.c:3900
> >
> > #3 0x7f7ce25f825c in g_main_context_iteration
> > (context=context@entry=0x55ba65041ad0, may_block=may_block@entry=1) at
> > ../../../glib/gmain.c:3981
> > #4 0x7f7ce37aea2d in g_application_run
> > (application=0x55ba650231e0, argc=, argv=0x7ffcb3349c88) at
> > ../../../gio/gapplication.c:2470
> >
> > #5 0x55ba63f271fa in main (argc=2, argv=0x7ffcb3349c88) at
> > gedit/gedit.c:146
> > (gdb) info local
> > No symbol table info available.
> > (gdb) up
> > #1 0x7f7ce25f7669 in g_main_context_prepare
> > (context=context@entry=0x55ba65041ad0,
> > priority=priority@entry=0x7ffcb3349aa0) at ../../../glib/gmain.c:3492
> > 3492 result = (* prepare) (source, _timeout);
> > (gdb) info local
> > result =
> >
> > prepare = 0x7f198f
> > source_timeout = -1
> > i =
> >
> > n_ready = 16
> > current_priority = 0
> > source = 0x55ba658e7d00
> > iter = {context = 0x55ba65041ad0, may_modify = 1, current_list =
> > 0x7f7cd00020e0, source = 0x55ba658e7d00}
> >
> >
> > https://sources.debian.org/src/glib2.0/2.58.3-2+deb10u2/glib/gmain.c/#L3492
> > [2]
> > https://gitlab.gnome.org/GNOME/gedit/-/issues/51
> > [3]
> > https://wiki.debian.org/HowToGetABacktrace
Thread 6 (Thread 0x7f770bfff700 (LWP 18325)):
#0 0x7f7716fb1819 in __GI___poll (fds=0x55e52c486b40, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 18446744073709551100
sc_cancel_oldtype = 0
#1 0x7f7715fef136 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7f7715fef25c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7f7710b25ffd in () at
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
#4 0x7f7716017415 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x7f7715e46fa3 in start_thread (arg=) at
pthread_create.c:486
ret =
pd =
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140149279160064,
-4816642476741125435, 140734018650862, 140734018650863, 140149279160064,
94442779747632, 4884662664485771973, 4884702345840794309}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call =
#6 0x7f7716fbc4cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 5 (Thread 0x7f770ad14700 (LWP 18327)):
#0 0x7f7716fb6f59 in syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7f77160390ba in g_cond_wait_until () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7f7715fc1091 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7f7716017ef2 in
Bug#986172: unblock: dwarf-fortress/0.47_04+dfsg1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package dwarf-fortress [ Reason ] It has been noted in #986119 that the upstream release tarballs for dwarf-fortress include shared libraries but no corresponding source code is available. The shared libraries in question are licensed under GPL and thus not distributable without source code. The affected files are not shipped in any binary packages. This update fixes the issue by repacking the source tarballs to exclude those files. [ Impact ] The package is not distributable in its current form, so it has to be either updated or entirely removed from testing to cease violating the licenses of the affected files. [ Tests ] The now excluded files were not shipped in any binary package or used in the build process. Their removal should not have any affect on the binary packages. I confirmed (using diffoscope) that the built debian packages do not differ in content except in expected ways due to changed package metadata and changes in the generaed manpage due to a newer pandoc version being used in the build. I also manually confirmed that the game can be successfully started and basic interactions inside the game still work. [ Risks ] Since the removed files are not part of any binary packages, it can be easily confirmed that their removal has no negative effect. I see virtually no risk introduced by this update. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing unblock dwarf-fortress/0.47_04+dfsg1-1 Binärdateien /tmp/x4E2O1qvMn/dwarf-fortress-0.47.04/amd64/libs/libgcc_s.so.1 und /tmp/ag24SxYJ0c/dwarf-fortress-0.47.04+dfsg1/amd64/libs/libgcc_s.so.1 sind verschieden. Binärdateien /tmp/x4E2O1qvMn/dwarf-fortress-0.47.04/amd64/libs/libstdc++.so.6 und /tmp/ag24SxYJ0c/dwarf-fortress-0.47.04+dfsg1/amd64/libs/libstdc++.so.6 sind verschieden. diff -Nru dwarf-fortress-0.47.04/debian/changelog dwarf-fortress-0.47.04+dfsg1/debian/changelog --- dwarf-fortress-0.47.04/debian/changelog 2020-03-28 18:48:06.0 +0100 +++ dwarf-fortress-0.47.04+dfsg1/debian/changelog 2021-03-30 19:04:37.0 +0200 @@ -1,3 +1,10 @@ +dwarf-fortress (0.47.04+dfsg1-1) unstable; urgency=high + + * Remove unnecessary code copies with license violations from source +tarball. (Closes: #986119) + + -- Sven Bartscher Tue, 30 Mar 2021 19:04:37 +0200 + dwarf-fortress (0.47.04-1) unstable; urgency=low * New upstream version diff -Nru dwarf-fortress-0.47.04/debian/copyright dwarf-fortress-0.47.04+dfsg1/debian/copyright --- dwarf-fortress-0.47.04/debian/copyright 2020-03-28 18:48:06.0 +0100 +++ dwarf-fortress-0.47.04+dfsg1/debian/copyright 2021-03-30 19:04:37.0 +0200 @@ -11,6 +11,15 @@ do not grant all freedoms required by the DFSG. No modifications of the included binaries are permitted, and the binaries are not distributed with source code. +Comment: + Some files have been removed from the original source tarballs, because + they are licensed under the GPL, but no source is available for them. +Files-Excluded-amd64: + libs/libgcc_s.so.1 + libs/libstdc++.so.6 +Files-Excluded-i386: + libs/libgcc_s.so.1 + libs/libstdc++.so.6 Files: * Copyright: 2002-2020 Tarn Adams. All rights reserved. diff -Nru dwarf-fortress-0.47.04/debian/watch dwarf-fortress-0.47.04+dfsg1/debian/watch --- dwarf-fortress-0.47.04/debian/watch 2020-03-28 18:48:06.0 +0100 +++ dwarf-fortress-0.47.04+dfsg1/debian/watch 2021-03-30 19:04:37.0 +0200 @@ -1,7 +1,7 @@ version=4 -opts="uversionmangle=s/^/0./,component=amd64" \ +opts="uversionmangle=s/^/0./,dversionmangle=s/\+dfsg\d+//,component=amd64" \ https://bay12games.com/dwarves/older_versions.html \ df_(\d+)_(\d+)_linux@ARCHIVE_EXT@ debian -opts="uversionmangle=s/^/0./,component=i386" \ +opts="uversionmangle=s/^/0./,dversionmangle=s/\+dfsg\d+//,component=i386" \ https://bay12games.com/dwarves/older_versions.html \ df_(\d+)_(\d+)_linux32@ARCHIVE_EXT@ same Binärdateien /tmp/x4E2O1qvMn/dwarf-fortress-0.47.04/i386/libs/libgcc_s.so.1 und /tmp/ag24SxYJ0c/dwarf-fortress-0.47.04+dfsg1/i386/libs/libgcc_s.so.1 sind verschieden. Binärdateien /tmp/x4E2O1qvMn/dwarf-fortress-0.47.04/i386/libs/libstdc++.so.6 und /tmp/ag24SxYJ0c/dwarf-fortress-0.47.04+dfsg1/i386/libs/libstdc++.so.6 sind verschieden.
Bug#986173: new upstream (14.2.19)
Package: ceph Severity: important Hi, 14.2.19 just got released, announcement says: ---snip--- This is a hotfix release to prevent daemons from binding to loopback network interfaces. All nautilus users are advised to upgrade to this release. [...] This release fixes a regression introduced in v14.2.18 whereby in certain environments, OSDs will bind to 127.0.0.1. See https://tracker.ceph.com/issues/49938. ---snap--- it would be nice if this makes it to the archive soon. Regards, Daniel
Bug#986161: no upload is possible in droopy
Package: droopy
Version: 0.20160830-3
Dopo aver avviato droopy, quando si prova ad uppare un qualsiasi file, la
connessione si annulla.
Nel terminale da cui si è eseguito droopy, appaiono queste scritte:
192.168.1.xx - - [30/Mar/2021 17:36:02] Started file transfer
192.168.1.xx - - [30/Mar/2021 17:36:02] TypeError('__init__() takes from 1 to
11 positional
arguments but 12 were given') 192.168.1.xx - - [30/Mar/2021 17:36:02] "POST /
HTTP/1.1" 200 -
e cosi via ogni volta che si ritenta e niente viene uppato.
Questo succede con qualsiasi tipo di configurazione viene lanciato droopy. Sul
browser (client)
appare "there has been a problem! Retry"
Sto usando Debian 11 Bullseye , kernel linux-image-5.10.0-5-amd64, python3
3.9.2-2
Bug#985590: (pre-approval) unblock: zfs-linux/2.0.3-2
Hi Aron,
On 30-03-2021 10:01, Aron Xu wrote:
> I have reverted 3, and attached is the new debdiff.
This looks wrong, no?
+# only automatically trim the nvme-only pools.
+POOLS=$(zpool list -H | awk '{print $1}')
+for pool in ${ZPOOLS[@]}; do
Variable is named POOLS, not ZPOOLS.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
Bug#986171: underscore: CVE-2021-23358
Source: underscore Version: 1.9.1~dfsg-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team ,y...@debian.org Hi, The following vulnerability was published for underscore. CVE-2021-23358[0]: | The package underscore from 1.13.0-0 and before 1.13.0-2, from 1.3.2 | and before 1.12.1 are vulnerable to Arbitrary Code Execution via the | template function, particularly when a variable property is passed as | an argument as it is not sanitized. [1] provides a POC to verify the issue. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-23358 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23358 [1] https://snyk.io/vuln/SNYK-JS-UNDERSCORE-1080984 Regards, Salvatore
Bug#986154: ITP: golang-github-mholt-acmez -- Premier ACME client library for Go
Control: merge -1 985878 I checked on wnpp.debian.net before filing the ITP, but apparently it's not frequently updated enough for that purpose...
Bug#986165: libcupsimage2: Upgrade fails with `m: cannot remove '/usr/share/doc/libcupsimage2': Directory not empty`
Dear Didier,
Am 30.03.21 um 19:59 schrieb Didier 'OdyX' Raboud:
Control: tags -1 +pending
Le mardi, 30 mars 2021, 19.11:07 h CEST Paul Menzel a écrit :
In a Debian 10 (buster) Docker container upgrading the package
*libcupsimage2* fails with the error below.
Thanks for your bugreport.
```
# apt full-upgrade
[…]
Preparing to unpack .../066-libcupsimage2_2.2.10-6+deb10u4_amd64.deb ...
rm: cannot remove '/usr/share/doc/libcupsimage2': Directory not empty
dpkg: error processing archive
/tmp/apt-dpkg-install-XQ7mPL/066-libcupsimage2_2.2.10-6+deb10u4_amd64.deb
(--unpack):
new libcupsimage2:amd64 package pre-installation script subprocess
returned error exit status 1
Preparing to unpack .../067-libavahi-common-data_0.7-4+deb10u1_amd64.deb ...
[…]
# ls /usr/share/doc/libcupsimage2
changelog.Debian.gz changelog.gz copyright
```
This seems to be because Debian Docker images setup dpkg to not unpack files
in /usr/share/doc,
But as shown above, there are three files in the `/u/s/doc/` directory.
but the various debian preinsts try to remove that
directory before installation. The current CUPS' libcupsimage2 preinst has the
following lines:
case "$1" in
upgrade)
if [ ! -L /usr/share/doc/libcupsimage2 ]; then
rm -rf /usr/share/doc/libcupsimage2
fi
;;
… These are the ones that fail.
Hmm, the force switch in `rm -rf` shouldn’t fail, shouldn’t it? But
indeed, that is the line present:
# grep rm /var/lib/dpkg/info/libcupsimage2\:amd64.*
/var/lib/dpkg/info/libcupsimage2:amd64.preinst: rm -rf
/usr/share/doc/libcupsimage2
```
# ls /etc/apt/apt.conf.d/
01autoremove70debconf docker-clean
docker-no-languages
50apt-file.conf docker-autoremove-suggests
docker-gzip-indexes
root@25f728ea4959:/# more /etc/apt/apt.conf.d/docker-clean
# Since for most Docker users, package installs happen in "docker build"
steps,
# they essentially become individual layers due to the way Docker handles
# layering, especially using CoW filesystems. What this means for us is
that
# the caches that APT keeps end up just wasting space in those layers,
making
# our layers unnecessarily large (especially since we'll normally never use
# these caches again and will instead just "docker build" again and make
a brand
# new image).
# Ideally, these would just be invoking "apt-get clean", but in our testing,
# that ended up being cyclic and we got stuck on APT's lock, so we get
this fun
# creation that's essentially just "apt-get clean".
DPkg::Post-Invoke { "rm -f /var/cache/apt/archives/*.deb
/var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true"; };
APT::Update::Post-Invoke { "rm -f /var/cache/apt/archives/*.deb
/var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true"; };
Dir::Cache::pkgcache "";
Dir::Cache::srcpkgcache "";
# Note that we do realize this isn't the ideal way to do this, and are
always
# open to better suggestions
(https://github.com/debuerreotype/debuerreotype/issues).
```
But they have been in CUPS' maintscripts since at least 2005, and I don't see
their point. If they were ever useful, there have been so many stable releases
since…
I'll remove these snippets and upload to experimental.
Sounds good.
Kind regards,
Paul
Bug#986170: ITP: r-bioc-ioniser -- Quality Assessment Tools for Oxford Nanopore MinION data
Package: wnpp Severity: wishlist Owner: Nilesh Patra X-Debbugs-Cc: debian-de...@lists.debian.org, nil...@debian.org * Package name: r-bioc-ioniser Version : 2.14.0+dfsg Upstream Author : Mike Smith * URL : https://bioconductor.org/packages/IONiseR * License : Expat Programming Lang: R Description : Quality Assessment Tools for Oxford Nanopore MinION data IONiseR provides tools for the quality assessment of Oxford Nanopore MinION data. It extracts summary statistics from a set of fast5 files and can be used either before or after base calling. In addition to standard summaries of the read-types produced, it provides a number of plots for visualising metrics relative to experiment run time or spatially over the surface of a flowcell. I shall maintain this package
Bug#986169: unblock: docx2txt/1.4-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package docx2txt [ Reason ] Address security issue: do not quote %s in mailcap entry. See: https://bugs.debian.org/985594 [ Impact ] Potential security issue with crafted filename. [ Tests ] n/a [ Risks ] - Code is trivial. - Leaf package. [ Checklist ] [X] all changes are documented in the d/changelog [X] I reviewed all changes and I approve them [X] attach debdiff against the package in testing [ Other info ] It's a two-character change. unblock docx2txt/1.4-5 diff -Nru docx2txt-1.4/debian/changelog docx2txt-1.4/debian/changelog --- docx2txt-1.4/debian/changelog 2020-12-11 21:56:27.0 + +++ docx2txt-1.4/debian/changelog 2021-03-20 17:13:44.0 + @@ -1,3 +1,9 @@ +docx2txt (1.4-5) unstable; urgency=medium + + * Address security issue: do not quote %s in mailcap entry (closes: #985594) + + -- Barak A. Pearlmutter Sat, 20 Mar 2021 17:13:44 + + docx2txt (1.4-4) unstable; urgency=medium * debian/rules does not require root diff -Nru docx2txt-1.4/debian/docx2txt.mime docx2txt-1.4/debian/docx2txt.mime --- docx2txt-1.4/debian/docx2txt.mime 2020-12-11 21:55:16.0 + +++ docx2txt-1.4/debian/docx2txt.mime 2021-03-20 17:12:47.0 + @@ -1 +1 @@ -application/vnd.openxmlformats-officedocument.wordprocessingml.document; docx2txt '%s' - ; copiousoutput; description=Office Open XML Document +application/vnd.openxmlformats-officedocument.wordprocessingml.document; docx2txt %s - ; copiousoutput; description=Office Open XML Document
Bug#986166: systemd: 'systemd --user' not functional. Regardless of user, org.freedesktop.systemd1 exits with status 1
> On Mar 30, 2021, at 12:22 PM, Michael Biebl wrote: > > What's the output of > apt-cache policy dbus-user-session > apt-cache policy dbus-x11 # apt-cache policy dbus-user-session dbus-user-session: Installed: 1.12.20-2 Candidate: 1.12.20-2 Version table: 1.13.18-2 1 1 http://ftp.debian.org/debian experimental/main amd64 Packages *** 1.12.20-2 500 500 http://ftp.us.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status # apt-cache policy dbus-x11 dbus-x11: Installed: 1.12.20-2 Candidate: 1.12.20-2 Version table: 1.13.18-2 1 1 http://ftp.debian.org/debian experimental/main amd64 Packages *** 1.12.20-2 500 500 http://ftp.us.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status
Bug#986168: cifs-utils: cifs.upcall, krb5.conf have different credential cache defaults, cifs.mount with sec=krb5 broken
Package: cifs-utils
Severity: normal
Hello,
I am unable to setup the appropriate environment to confirm that this
bug can be reproduced on Debian. I strongly believe it can, and that
someone familiar with the cifs.upcall code (or familiar with setting
up SMB or Active Directory file shares) should be easily able to
verify the problem. I have reproduced the bug on Ubuntu 18 and 20.
Given that the Debian and Ubuntu devs work together and based on my
limited attempts to compare the Debian and Ubuntu code I hope this bug
report will be useful to both distros. (And hold out vague hope that
the bug will be fixed for Bullseye.)
The problem is that the default Kerberos credential cache
is in a file with a name that looks like: /tmp/krb5cc_10011_r0AC1F
But cifs.upcall looks for credentials in a file with a name
that looks like: /tmp/krb5cc_10011
This creates problems with sec=krb5* cifs mounts, breaking the
"multiuser" option.
I see no options to adjust the credential cache file name
used by cifs.upcall. However, a work-around is to put:
[libdefaults]
default_ccache_name = FILE:/tmp/krb5cc_%{euid}
into /etc/krb5.conf.
I cannot speak to what effect the above work-around has on security.
As near as I can tell the Kerberos docs at MIT say that the default
credential cache name is "krb5cc_%{euid}", and have not determined
where, or why, the change was made.
Setting "log level = 3" in /etc/samba/smb.conf ([global]) is helpful
when debugging this. I found more detail in the journalctl logs than
in the syslogs, although I configured for syslogging.
FYI. The Ubuntu tests I ran were against an Microsoft Windows Active
Directory share.
After spending some time attempting to reproduce this on Debian and
failing to setup a SAMBA test environment, and failing to spend
enough time with the code to come up with a patch, and not having the
resources to reproduce the Ubuntu environments in a lab, I cannot
presently continue. It seems better to send in a partial bug report
than leave the problem outstanding.
This may be related to Debian bug #968943. It is almost surely
related to Ubuntu bug number # 1900856:
https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1900856
-- System Information:
Debian Release: 10.9
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-16-amd64 (SMP w/4 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)
LSM: AppArmor: enabled
Versions of packages cifs-utils depends on:
ii libc6 2.28-10
ii libcap-ng00.7.9-2
ii libkeyutils1 1.6-6
ii libkrb5-3 1.17-3+deb10u1
ii libpam0g 1.3.1-5
ii libtalloc22.1.14-2
ii libwbclient0 2:4.9.5+dfsg-5+deb10u1
cifs-utils recommends no packages.
Versions of packages cifs-utils suggests:
ii keyutils 1.6-6
ii smbclient 2:4.9.5+dfsg-5+deb10u1
pn winbind
Bug#986003: unblock: bc/1.07.1-3
On 2021-03-27 14:03:47 -0400, Ryan Kavanagh wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > X-Debbugs-Cc: r...@debian.org > > Please unblock package bc > > [ Reason ] > One user-visible change: > * Updated homepage field (Closes: #970615) > > Several other small housekeeping / cosmetic changes (mea culpa: I > prepared the upload in November but forgot to upload it): > * Bump standards version > * Removing trailing whitespace in changelog/control > * Update watch file > * Switch from 'compat' file to debhelper-compat (I did not >bump the compat version). > * Rules-Requires-Root: no > > All changes are cosmetic; none affect the functionality of the package. > > [ Impact ] > The only impact on users is an updated homepage. The remaining changes > are cosmetic. I think its too late for this type of changes and can wait for bookworm. Cheers > > [ Risks ] > Key package. No risk. Binaries build, install, and work after changes. > > [ Checklist ] > [x] all changes are documented in the d/changelog > [x] I reviewed all changes and I approve them > [x] attach debdiff against the package in testing > > [ Other info ] > Please let me know if I am free to upload to unstable, or if it's too > late for these changes. Thanks! > > unblock bc/1.07.1-3 > > -- > |)|/ Ryan Kavanagh | GPG: 4E46 9519 ED67 7734 268F > |\|\ https://rak.ac | BD95 8F7B F8FC 4A11 C97A > diff -Nru bc-1.07.1/debian/changelog bc-1.07.1/debian/changelog > --- bc-1.07.1/debian/changelog2018-03-22 12:20:34.0 -0400 > +++ bc-1.07.1/debian/changelog2021-03-27 13:30:28.0 -0400 > @@ -1,3 +1,22 @@ > +bc (1.07.1-3) unstable; urgency=medium > + > + [ Ondřej Nový ] > + * d/copyright: Use https protocol in Format field > + * d/changelog: Remove trailing whitespaces > + * d/control: Remove trailing whitespaces > + > + [ Ryan Kavanagh ] > + * drop unneeded phony target in rules > + * bump standards version to 4.5.1 > + * bump copyright years > + * update homepage (Closes: #970615) > + * Set Rules-Requires-Root: no > + * Drop compat file in favour of debhelper-compat > + * Let gbp dch use meta tag information > + * Update watch file > + > + -- Ryan Kavanagh Sat, 27 Mar 2021 13:30:28 -0400 > + > bc (1.07.1-2) unstable; urgency=medium > >* Fix circular dependency in Makefile, > 08_no-make-circular-dependencies.diff > @@ -104,23 +123,23 @@ > >* Applied patch from Paul Dwerryhouse. > Closes: #472250: please return support for .dcrc file > - > + >* Applied patch from Ian Jackson. > Closes: #488735: notice read and write errors on input and output > - > + >* Generated bc.html and dc.html but something is still wrong. > - > + >* Added homepage field to debian/control. > - > + >* I can't see the problem with hyphens. > - > + >* Fixed doc-base white space. > - > + >* Added watch file. > - > + >* I believe that the above changes deal with 558188. > Closes: #558188: Changes made in 1.06.94-3.1 NMU have been lost > - > + > -- John G. Hasler Fri, 22 Jun 2012 21:00:45 -0500 > > bc (1.06.95-2) unstable; urgency=low > @@ -129,14 +148,14 @@ > being correctly generated. > > -- John G. Hasler Thu, 15 Oct 2009 12:17:23 -0500 > - > + > bc (1.06.95-1) unstable; urgency=low > >* New upstream release > Closes: #538419: New bc upstream version 1.06.95 > - > + > Fixed libreadline build dependencies. > - > + > -- John Hasler Sat, 03 Oct 2009 21:21:04 -0500 > > bc (1.06.94-3.1) unstable; urgency=low > @@ -168,7 +187,7 @@ > bc (1.06.94-2) unstable; urgency=low > >* Uncommented dh_md5sums in debian/rules. > - > + >* Corrected menu entries. > > -- John Hasler Fri, 05 Oct 2007 12:29:18 -0500 > @@ -176,39 +195,39 @@ > bc (1.06.94-1) unstable; urgency=low > >* New upstream release > - > + > Code cleanup upstream has fixed these > -Closes: #357728: bc: Segfaults > -Closes: #221781: dc: precision >= 10 does not work > -Closes: #429156: dc: segfaults when generating primes > +Closes: #357728: bc: Segfaults > +Closes: #221781: dc: precision >= 10 does not work > +Closes: #429156: dc: segfaults when generating primes > Closes: #296232: dc directory' should print an error > Closes: #301921: 'man bc' typos: "environent", "specifing" > - > + >* Patched use_quit() in main.c to run rl_initialize(). > Closes: #287210: bc: Interrupt should reset the input line > - > + >* BC_LINE_LENGTH=0 disables the multi-line feature. > -Closes: #245899: bc: BC_LINE_LENGTH=0 or similar for ``do never split'' > +Closes: #245899: bc: BC_LINE_LENGTH=0 or similar for ``do never split'' > should be added, or the manpage should be fixed > - > + >* Upstream says this in correct POSIX behavior. > Closes: #388487: bc: scale
Bug#986155: ITP: zap -- Blazing fast, structured, leveled logging in Go
Package: wnpp
Severity: wishlist
Owner: ghost
Control: block 986154 by -1
X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org
* Package name: zap
Version : 1.16.0-1
Upstream Author : Uber Go
* URL : https://github.com/uber-go/zap
* License : Expat
Programming Lang: Go
Description : Blazing fast, structured, leveled logging in Go.
Build Blazing fast, structured, leveled logging in Go.
.
Performance
.
For applications that log in the hot path, reflection-based serialization
and string formatting are prohibitively expensive - they're CPU-intensive
and make many small allocations. Put differently, using encoding/json and
fmt.Fprintf to log tons of interface{}s makes your application slow.
.
Zap takes a different approach. It includes a reflection-free,
zero-allocation JSON encoder, and the base Logger strives to avoid
serialization overhead and allocations wherever possible. By building
the high-level SugaredLogger on that foundation, zap lets users choose
when they need to count every allocation and when they'd prefer a more
familiar, loosely typed API.
.
Note that zap only supports the two most recent minor versions of Go.
Bug#985467: marked as done (guix: Risk of local privilege escalation via guix-daemon)
On 2021-03-28, Debian Bug Tracking System wrote: > Date: Sat, 27 Mar 2021 19:18:29 -0700 > Source: guix > Architecture: source > Version: 1.2.0-4 > Distribution: unstable > Urgency: medium > Maintainer: Vagrant Cascadian > Changed-By: Vagrant Cascadian > Closes: 983248 985467 985916 > Changes: > guix (1.2.0-4) unstable; urgency=medium > . >* debian/patches: Fix privilege escalation issue in > guix-daemon. (Closes: #985467) Pinging to attempt to reset the autoremoval timer... live well, vagrant signature.asc Description: PGP signature
Bug#986167: debconf: [INTL:nl] Dutch translation for the debconf package
Package: debconf Severity: wishlist Tags: l10n patch Dear Maintainer, Please find attached the updated Dutch po file for the debconf package. It has been submitted for review to the debian-l10n-dutch mailing list. Please add it to your next package revision. It should be put as "po/nl.po" in your package build tree. -- Kind regards, Frans Spiesschaert nl.po.gz Description: application/gzip
Bug#986166: systemd: 'systemd --user' not functional. Regardless of user, org.freedesktop.systemd1 exits with status 1
Am 30.03.2021 um 20:14 schrieb Troy Telford: Package: systemd Version: 247.3-3 Severity: normal Dear Maintainer, * What led up to the situation? This was probably due to an apt update/upgrade. I haven't been configuring my system, but about two weeks ago, "systemd --user" stopped working entirely - none of the user units start up upon user login. The first thing I noticed is no sound, but it didn't take long to find that systemd wasn't running any user units. * What exactly did you do (or not do) that was effective (or ineffective)? Initially, I found that XDG_RUNTIME_DIR wasn't being set anymore -- so I added `export XDG_RUNTIME_DIR=/run/user/$(id -u)` to my .xsessionrc. It didn't fix the issue for login, but I could at least run `systemd --user` and start up the processes after login. However, even that is broken now: I invariably get "Process org.freedesktop.systemd1 exited with status 1" /var/log/daemon.log has a corresponding message from DBUS about org.freedesktop.systemd1 being activated, but dying: Mar 30 12:08:01 pilot.pariahzero.net dbus-daemon[2025881]: [session uid=1000 pid=2025879] Activating service name='org.freedesktop.systemd1' requested by ':1.155' (uid=1000 pid=2433850 comm="systemctl --user --failed ") Mar 30 12:08:01 pilot.pariahzero.net dbus-daemon[2025881]: [session uid=1000 pid=2025879] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 The problem happens for all users on the system. I'll see if I can get more verbose logging to give any additional details about why org.freedesktop.systemd1 is exiting. If you know offhand, I'd definitely give it a try. What's the output of apt-cache policy dbus-user-session apt-cache policy dbus-x11
Bug#986154: ITP: golang-github-mholt-acmez -- Premier ACME client library for Go
Package: wnpp
Severity: wishlist
Owner: ghost
Control: block 954793 by -1
X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org
* Package name: golang-github-mholt-acmez
Version : 0.1.3-1
Upstream Author : Matt Holt
* URL : https://github.com/mholt/acmez
* License : Apache-2.0
Programming Lang: Go
Description : Premier ACME client library for Go
acmez - ACME client library for Go
.
ACMEz ("ack-measy" or "acme-zee", whichever you prefer) is a
fully-compliant RFC 8555 (https://tools.ietf.org/html/rfc8555) (ACME)
implementation in pure Go. It is lightweight, has an elegant Go API,
and its retry logic is highly robust against external errors. ACMEz is
suitable for large-scale enterprise deployments.
.
NOTE: This module is for getting certificates, not managing
certificates. Most users probably want certificate management
(keeping certificates renewed) rather than to interface directly with
ACME. Developers who want to use certificates in their long-running Go
programs should use CertMagic instead; or, if their program is not
written in Go, Caddy can be used to manage certificates (even
without running an HTTP or TLS server).
Bug#986165: libcupsimage2: Upgrade fails with `m: cannot remove '/usr/share/doc/libcupsimage2': Directory not empty`
Control: tags -1 +pending Dear Paul, Le mardi, 30 mars 2021, 19.11:07 h CEST Paul Menzel a écrit : > In a Debian 10 (buster) Docker container upgrading the package > *libcupsimage2* fails with the error below. Thanks for your bugreport. > ``` > # apt full-upgrade > […] > Preparing to unpack .../066-libcupsimage2_2.2.10-6+deb10u4_amd64.deb ... > rm: cannot remove '/usr/share/doc/libcupsimage2': Directory not empty > dpkg: error processing archive > /tmp/apt-dpkg-install-XQ7mPL/066-libcupsimage2_2.2.10-6+deb10u4_amd64.deb > (--unpack): > new libcupsimage2:amd64 package pre-installation script subprocess > returned error exit status 1 > Preparing to unpack .../067-libavahi-common-data_0.7-4+deb10u1_amd64.deb ... > […] > # ls /usr/share/doc/libcupsimage2 > changelog.Debian.gz changelog.gz copyright > ``` This seems to be because Debian Docker images setup dpkg to not unpack files in /usr/share/doc, but the various debian preinsts try to remove that directory before installation. The current CUPS' libcupsimage2 preinst has the following lines: case "$1" in upgrade) if [ ! -L /usr/share/doc/libcupsimage2 ]; then rm -rf /usr/share/doc/libcupsimage2 fi ;; … These are the ones that fail. But they have been in CUPS' maintscripts since at least 2005, and I don't see their point. If they were ever useful, there have been so many stable releases since… I'll remove these snippets and upload to experimental. Best regards, OdyX signature.asc Description: This is a digitally signed message part.
Bug#954066: hplip (3.21.2+dfsg1-2) affected too
Le mardi, 30 mars 2021, 19.49:24 h CEST user2304 a écrit : > Dear Maintainer, > > just a quick note, after dist-upgrading my testing-system, version of hplip > changed to 3.21.2. > > File /usr/share/hplip/data/models/models.dat is changed back to wrong model- > name "[hp_laserjet_cp1025]" instead of "[hp_laserjet_cp_1025]". That's normal; files in /usr/share are not dpkg conffiles, and local modifications will get overwritten. Sorry, but this change won't make it in Debian bullseye; modifying upstream data files for such bugs is too risky (in that instance; where this looks like a parsing bug). Regards, OdyX signature.asc Description: This is a digitally signed message part.
Bug#954066: hplip (3.21.2+dfsg1-2) affected too
Dear Maintainer, just a quick note, after dist-upgrading my testing-system, version of hplip changed to 3.21.2. File /usr/share/hplip/data/models/models.dat is changed back to wrong model- name "[hp_laserjet_cp1025]" instead of "[hp_laserjet_cp_1025]". -- mail: user2...@web.de
Bug#986165: libcupsimage2: Upgrade fails with `m: cannot remove '/usr/share/doc/libcupsimage2': Directory not empty`
Package: libcupsimage2 Version: 2.2.10-6+deb10u4 Severity: normal Dear Debian folks, In a Debian 10 (buster) Docker container upgrading the package *libcupsimage2* fails with the error below. ``` # apt full-upgrade […] Preparing to unpack .../066-libcupsimage2_2.2.10-6+deb10u4_amd64.deb ... rm: cannot remove '/usr/share/doc/libcupsimage2': Directory not empty dpkg: error processing archive /tmp/apt-dpkg-install-XQ7mPL/066-libcupsimage2_2.2.10-6+deb10u4_amd64.deb (--unpack): new libcupsimage2:amd64 package pre-installation script subprocess returned error exit status 1 Preparing to unpack .../067-libavahi-common-data_0.7-4+deb10u1_amd64.deb ... […] # ls /usr/share/doc/libcupsimage2 changelog.Debian.gz changelog.gz copyright ``` I found one forum post from 2015 with the same error on Linux Mint upgrading *libcupsimage2:amd64* from 1.7.2-0ubuntu1.5 to 1.7.2-0ubuntu1.6. [1] System information: ``` # more /etc/os-release PRETTY_NAME="Debian GNU/Linux 10 (buster)" NAME="Debian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=debian HOME_URL="https://www.debian.org/; SUPPORT_URL="https://www.debian.org/support; BUG_REPORT_URL="https://bugs.debian.org/; # dpkg -l libcupsimage2 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---== ii libcupsimage2:amd64 2.2.10-6+deb10u2 amd64Common UNIX Printing System(tm) - Raster image library # apt-cache policy libcupsimage2 libcupsimage2: Installed: 2.2.10-6+deb10u2 Candidate: 2.2.10-6+deb10u4 Version table: 2.2.10-6+deb10u4 500 500 http://deb.debian.org/debian buster/main amd64 Packages *** 2.2.10-6+deb10u2 100 100 /var/lib/dpkg/status ``` Kind regards, Paul [1]: https://forums.linuxmint.com/viewtopic.php?t=201930
Bug#986163: mutt: opens mailboxes over sshfs readonly
Package: mutt Version: 2.0.5-3 Severity: normal Problem: Mutt opens mailboxes over sshfs readonly. How to reproduce: I mount my homedir of a remote machine onto the filesystem of my pc. sshfs -o idmap=user remotehost: /mnt/bartm/remotehost Then I use mutt on my pc to access the mailboxes on the remote machine. Expected behavior: Mutt should open mailboxes over sshfs readwrite. Just like vi opens them readwrite. Workaround: Disabling mutt_dotlock by undefining USE_DOTLOCK makes the problem disappear. At first sight lstat seems confused on sshfs' different uids and guids on local and remote machines. mutt 2.0.5-3 sshfs 3.7.1+repack-1
Bug#986130: fetchmailconf: No update/upgrade possible due to error
Am 30.03.21 um 09:04 schrieb dk8kk:
> Package: fetchmailconf
> Version: 6.4.0~beta4-3+deb10u1
> Severity: grave
> Tags: a11y
> Justification: renders package unusable
>
> Dear Maintainer,
>
> apt-get update/apt-get upgrade suggests these package for upgrade:
> - fetchmail (6.4.0~beta4-3+deb10u1)
> - fetchmailconf (6.4.0~beta4-3+deb10u1)
>
> Installation/Configurations fails afterwards because of the
> following error:
>
> fetchmail (6.4.0~beta4-3+deb10u1) wird eingerichtet ...
> Job for fetchmail.service failed because the control process exited with
> error code.
> See "systemctl status fetchmail.service" and "journalctl -xe" for details.
> invoke-rc.d: initscript fetchmail, action "restart" failed.
> ● fetchmail.service - LSB: init-Script for system wide fetchmail daemon
>Loaded: loaded (/etc/init.d/fetchmail; generated)
>Active: failed (Result: exit-code) since Tue 2021-03-30 08:59:33 CEST; 4ms
> ago
> Docs: man:systemd-sysv-generator(8)
> Process: 3556 ExecStart=/etc/init.d/fetchmail start (code=exited,
> status=1/FAILURE)
As external/upstream maintainer I cannot comment on this part.
> Mär 30 08:59:33 regulus.fritz.box systemd[1]: Starting LSB: init-Script for
> system wide fetchmail daemon...
> Mär 30 08:59:33 regulus.fritz.box fetchmail[3556]: Starting mail retriever
> agent: fetchmailfetchmail: es wurden keine Mailserver spezifiziert.
This means "no mail servers configured", i. e. virgin installation.
> Mär 30 08:59:33 regulus.fritz.box fetchmail[3556]: failed!
> Mär 30 08:59:33 regulus.fritz.box systemd[1]: fetchmail.service: Control
> process exited, code=exited, status=1/FAILURE
> Mär 30 08:59:33 regulus.fritz.box systemd[1]: fetchmail.service: Failed with
> result 'exit-code'.
> Mär 30 08:59:33 regulus.fritz.box systemd[1]: Failed to start LSB:
> init-Script for system wide fetchmail daemon.
> dpkg: Fehler beim Bearbeiten des Paketes fetchmail (--configure):
> »installiertes fetchmail-Skript des Paketes post-installation«-Unterprozess
> gab den Fehlerwert 1 zurück
> dpkg: Abhängigkeitsprobleme verhindern Konfiguration von fetchmailconf:
> fetchmailconf hängt ab von fetchmail (>= 6.4.0~beta4-3+deb10u1); aber:
> Paket fetchmail ist noch nicht konfiguriert.
This means fetchmailconf can't be configured while fetchmail is pending
configuration.
> dpkg: Fehler beim Bearbeiten des Paketes fetchmailconf (--configure):
> Abhängigkeitsprobleme - verbleibt unkonfiguriert
> Fehler traten auf beim Bearbeiten von:
> fetchmail
> fetchmailconf
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>
>
> Trying to configure fetchmailconf manually fails too:
>
> root@regulus:/etc# fetchmailconf --configure
> Traceback (most recent call last):
> File "/usr/lib/python2.7/dist-packages/fetchmailconf.py", line 2081, in
>
> "version"])
> File "/usr/lib/python2.7/getopt.py", line 88, in getopt
> opts, args = do_longs(opts, args[0][2:], longopts, args[1:])
> File "/usr/lib/python2.7/getopt.py", line 152, in do_longs
> has_arg, opt = long_has_args(opt, longopts)
> File "/usr/lib/python2.7/getopt.py", line 169, in long_has_args
> raise GetoptError('option --%s not recognized' % opt, opt)
> getopt.GetoptError: option --configure not recognized
To the submitter: That is expected and cannot possibly work.
If you were to manually try to configure fetchmailconf, you'd have to
run: dpkg --configure fetchmailconf.
fetchmailconf is a Python-Tk-(Tkinter)-based graphical configuration
utility.
Bug#986162: file-manager area-select is opaque
Package: clearlooks-phenix-theme
Version: 7.0.1-3
Using thunar in xfce or caja in mate, when selecting multiple files in
icon view by click and drag the mouse, the selected area is opaque and
covers the selected icons.
Releasing the mouse button shows that the files did get selected. You just
can't see the icons while you're selecting them.
Inserting one line in gtk-3.0/gtk-widgets.css seems to fix the problem.
--- gtk-widgets.css 2018-09-14 10:13:33.0 -0400
+++ gtk-widgets.css-new 2021-03-30 10:03:59.240908271 -0400
@@ -155,6 +155,7 @@
}
.rubberband,
+.view .rubberband,
view rubberband,
rubberband {
background-color: alpha (@theme_selected_bg_color, 0.35);
Bug#986160: command-not-found: Typing in "lsio" at the bash prompt results in "Sorry, command-not-found has crashed!"
Package: command-not-found Version: 20.10.1-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** When typing in the command "lsio" (in the same vein or spirit as "lscpu", "lsmem", etc.), I get the following error: -- $ lsio Sorry, command-not-found has crashed! Please file a bug report at: http://www.debian.org/Bugs/Reporting Please include the following information with the report: command-not-found version: 0.3 Python version: 3.9.2 final 0 Distributor ID: Kali Description:Kali GNU/Linux Rolling Release:2021.1 Codename: kali-rolling Exception information: unable to open database file Traceback (most recent call last): File "/usr/share/command-not-found/CommandNotFound/util.py", line 23, in crash_guard callback() File "/usr/lib/command-not-found", line 90, in main cnf = CommandNotFound.CommandNotFound(options.data_dir) File "/usr/share/command-not-found/CommandNotFound/CommandNotFound.py", line 79, in __init__ self.db = SqliteDatabase(dbpath) File "/usr/share/command-not-found/CommandNotFound/db/db.py", line 12, in __init__ self.con = sqlite3.connect(filename) sqlite3.OperationalError: unable to open database file -- Obviously, the result should've been a normal "command not found" error, optionally pointing to a package or packages that contained a command with the same spelling. -- System Information: Distributor ID: Kali Description:Kali GNU/Linux Rolling Release:2021.1 Codename: kali-rolling Architecture: x86_64 Kernel: Linux 5.10.0-kali5-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set nShell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages command-not-found depends on: ii apt-file 3.2.2 ii lsb-release 11.1.0 ii python3 3.9.2-2 ii python3-apt 2.1.7 cnommand-not-found recommends no packages. Versions of packages command-not-found suggests: pn snapd n -- no debconf information Best, Sean F. Leinen
Bug#986154: ITP: golang-github-mholt-acmez -- Premier ACME client library for Go
Hello.
I have already packaged this library
https://salsa.debian.org/go-team/packages/golang-github-mholt-acmez
On 3/30/21 7:42 PM, ghost wrote:
Package: wnpp
Severity: wishlist
Owner: ghost
Control: block 954793 by -1
X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org
* Package name: golang-github-mholt-acmez
Version : 0.1.3-1
Upstream Author : Matt Holt
* URL : https://github.com/mholt/acmez
* License : Apache-2.0
Programming Lang: Go
Description : Premier ACME client library for Go
acmez - ACME client library for Go
.
ACMEz ("ack-measy" or "acme-zee", whichever you prefer) is a
fully-compliant RFC 8555 (https://tools.ietf.org/html/rfc8555) (ACME)
implementation in pure Go. It is lightweight, has an elegant Go API,
and its retry logic is highly robust against external errors. ACMEz is
suitable for large-scale enterprise deployments.
.
NOTE: This module is for getting certificates, not managing
certificates. Most users probably want certificate management
(keeping certificates renewed) rather than to interface directly with
ACME. Developers who want to use certificates in their long-running Go
programs should use CertMagic instead; or, if their program is not
written in Go, Caddy can be used to manage certificates (even
without running an HTTP or TLS server).
OpenPGP_signature
Description: OpenPGP digital signature
Bug#986156: linux-image-5.10.0-5-rt-amd64: qemu/kvm caused trouble on the 5.10 PREMPT_RT kernel
Control: tags -1 + moreinfo Hi, On Tue, Mar 30, 2021 at 04:40:18PM +0200, Dr. Johann Pfefferl wrote: > Package: src:linux > Version: 5.10.24-1 > Severity: important > > Dear Maintainer, > >* What led up to the situation? >I used the tool debos https://github.com/go-debos/debos to create a >debian image on my machine. debos uses qemu to setup an install >environment for debian. After a while the process got stucked. >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? >I got a kernel warning > Mar 30 15:45:10 hpjp kernel: [ cut here ] > Mar 30 15:45:10 hpjp kernel: WARNING: CPU: 3 PID: 339240 at fs/eventfd.c:74 > eventfd_signal+0x7e/0x90 > Mar 30 15:45:10 hpjp kernel: Modules linked in: hid_plantronics nls_utf8 cifs > libdes rpcsec_gss_krb5 nfsv4 dns_resolver nfs nfs_ssc fscache nfsd au> > Mar 30 15:45:10 hpjp kernel: cpufreq_ondemand snd_soc_dmic cmac snd_sof_pci > algif_hash snd_sof_intel_byt algif_skcipher snd_sof_intel_ipc af_alg s> > Mar 30 15:45:10 hpjp kernel: videobuf2_v4l2 hid_sensor_als snd r8152 > hid_sensor_trigger mii soundcore drbg videobuf2_common cfg80211 hid_sensor_ii> > Mar 30 15:45:10 hpjp kernel: intel_ish_ipc i2c_i801 crct10dif_common > glue_helper intel_lpss i2c_hid i2c_smbus idma64 usb_common intel_ishtp hid wm> > Mar 30 15:45:10 hpjp kernel: CPU: 3 PID: 339240 Comm: qemu-system-x86 > Tainted: GW 5.10.0-5-rt-amd64 #1 Debian 5.10.24-1 > Mar 30 15:45:10 hpjp kernel: Hardware name: HP HP EliteBook 840 G7 Notebook > PC/8723, BIOS S70 Ver. 01.04.02 01/18/2021 > Mar 30 15:45:10 hpjp kernel: check_preemption_disabled: 44 callbacks > suppressed > Mar 30 15:45:10 hpjp kernel: BUG: using smp_processor_id() in preemptible > [] code: qemu-system-x86/339240 > Mar 30 15:45:10 hpjp kernel: caller is print_stop_info+0x1b/0x40 > Mar 30 15:45:10 hpjp kernel: CPU: 3 PID: 339240 Comm: qemu-system-x86 > Tainted: GW 5.10.0-5-rt-amd64 #1 Debian 5.10.24-1 > Mar 30 15:45:10 hpjp kernel: Hardware name: HP HP EliteBook 840 G7 Notebook > PC/8723, BIOS S70 Ver. 01.04.02 01/18/2021 > Mar 30 15:45:10 hpjp kernel: Call Trace: > Mar 30 15:45:10 hpjp kernel: dump_stack+0x6b/0x83 > Mar 30 15:45:10 hpjp kernel: check_preemption_disabled+0xcd/0xd0 > Mar 30 15:45:10 hpjp kernel: print_stop_info+0x1b/0x40 > Mar 30 15:45:10 hpjp kernel: ? eventfd_signal+0x7e/0x90 > Mar 30 15:45:10 hpjp kernel: show_regs+0x15/0x50 > Mar 30 15:45:10 hpjp kernel: __warn+0x7d/0xb0 > Mar 30 15:45:10 hpjp kernel: ? eventfd_signal+0x7e/0x90 > Mar 30 15:45:10 hpjp kernel: report_bug+0x9a/0xc0 > Mar 30 15:45:10 hpjp kernel: handle_bug+0x35/0x80 > Mar 30 15:45:10 hpjp kernel: exc_invalid_op+0x14/0x70 > Mar 30 15:45:10 hpjp kernel: asm_exc_invalid_op+0x12/0x20 > Mar 30 15:45:10 hpjp kernel: RIP: 0010:eventfd_signal+0x7e/0x90 > Mar 30 15:45:10 hpjp kernel: Code: 01 00 00 00 be 03 00 00 00 4c 89 ef e8 db > b0 db ff 65 ff 0d 74 e4 0f 7d 4c 89 ef e8 cc bd 5b 00 4c 89 e0 5b 5d 4> > Mar 30 15:45:10 hpjp kernel: RSP: 0018:b81b91d47d50 EFLAGS: 00010202 > Mar 30 15:45:10 hpjp kernel: RAX: 0001 RBX: 9da5c68d4000 RCX: > > Mar 30 15:45:10 hpjp kernel: RDX: fe007000 RSI: 0001 RDI: > 9da5c4c6fb40 > Mar 30 15:45:10 hpjp kernel: RBP: b81b91d47db0 R08: R09: > fe007000 > Mar 30 15:45:10 hpjp kernel: R10: R11: R12: > 0040 > Mar 30 15:45:10 hpjp kernel: R13: 9da7be878000 R14: R15: > 9da7be878038 > Mar 30 15:45:10 hpjp kernel: ioeventfd_write+0x51/0x80 [kvm] > Mar 30 15:45:10 hpjp kernel: __kvm_io_bus_write+0x88/0xb0 [kvm] > Mar 30 15:45:10 hpjp kernel: kvm_io_bus_write+0x54/0x80 [kvm] > Mar 30 15:45:10 hpjp kernel: handle_ept_misconfig+0x45/0x130 [kvm_intel] > Mar 30 15:45:10 hpjp kernel: kvm_arch_vcpu_ioctl_run+0xc9d/0x1780 [kvm] > Mar 30 15:45:10 hpjp kernel: kvm_vcpu_ioctl+0x239/0x5f0 [kvm] > Mar 30 15:45:10 hpjp kernel: __x64_sys_ioctl+0x83/0xb0 > Mar 30 15:45:10 hpjp kernel: do_syscall_64+0x33/0x80 > Mar 30 15:45:10 hpjp kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 > Mar 30 15:45:10 hpjp kernel: RIP: 0033:0x7f10d88fecc7 > Mar 30 15:45:10 hpjp kernel: Code: 00 00 00 48 8b 05 c9 91 0c 00 64 c7 00 26 > 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 0> > Mar 30 15:45:10 hpjp kernel: RSP: 002b:7f10d5d37508 EFLAGS: 0246 > ORIG_RAX: 0010 > Mar 30 15:45:10 hpjp kernel: RAX: ffda RBX: ae80 RCX: > 7f10d88fecc7 > Mar 30 15:45:10 hpjp kernel: RDX: RSI: ae80 RDI: > 000b > Mar 30 15:45:10 hpjp kernel: RBP: 560a90457d90 R08: 560a8f644618 R09: > > Mar 30 15:45:10 hpjp kernel: R10: 0001 R11: 0246 R12: > > Mar 30 15:45:10 hpjp kernel: R13:
Bug#986155: ITP: zap -- Blazing fast, structured, leveled logging in Go
Thanks for working on this.
But, this package is already available in Debian
https://packages.debian.org/buster/devel/golang-go.uber-zap-dev
On 3/30/21 7:53 PM, ghost wrote:
Package: wnpp
Severity: wishlist
Owner: ghost
Control: block 986154 by -1
X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org
* Package name: zap
Version : 1.16.0-1
Upstream Author : Uber Go
* URL : https://github.com/uber-go/zap
* License : Expat
Programming Lang: Go
Description : Blazing fast, structured, leveled logging in Go.
Build Blazing fast, structured, leveled logging in Go.
.
Performance
.
For applications that log in the hot path, reflection-based serialization
and string formatting are prohibitively expensive - they're CPU-intensive
and make many small allocations. Put differently, using encoding/json and
fmt.Fprintf to log tons of interface{}s makes your application slow.
.
Zap takes a different approach. It includes a reflection-free,
zero-allocation JSON encoder, and the base Logger strives to avoid
serialization overhead and allocations wherever possible. By building
the high-level SugaredLogger on that foundation, zap lets users choose
when they need to count every allocation and when they'd prefer a more
familiar, loosely typed API.
.
Note that zap only supports the two most recent minor versions of Go.
OpenPGP_signature
Description: OpenPGP digital signature
Bug#963025: fixing metadata
Control: found -1 20210315-2 Control: tags -1 moreinfo
Bug#986155: ITP: zap -- Blazing fast, structured, leveled logging in Go
Hi! Looks to me that this has been packaged already: https://tracker.debian.org/pkg/golang-go.uber-zap best regards, Peymaneh OpenPGP_signature Description: OpenPGP digital signature
Bug#986143: openstack-dashboard: fails to upgrade from 'buster': KeyError: 'django' in "/usr/lib/python3/dist-packages/django/template/utils.py", line 65
On 3/30/21 3:57 PM, Andreas Beckmann wrote: > On 30/03/2021 14.49, Thomas Goirand wrote: >> It's my opinion that the issue is probably a missing breaks: >> python3-django-horizon (<< 3:18.6.2) in python3-django. > > That doesn't help. Both packages are still at the buster version when > the failure happens. The only python3-django-* packages already upgraded > so far are: > > python3-django-appconf python3-django-babel python3-django-pyscss > > Andreas Ah, sh**... What do you suggest then? (even: what do you suggest I test in a VM...) Cheers, Thomas Goirand
Bug#981352: "VPN Connections" menu entry moves around and is frustrating to click
On Tue, Mar 30, 2021 at 02:28:08PM +0200, Michael Biebl wrote: > Since this is not a Debian specific / integration issue, but is likely to > require a UI redesign, this really needs input from upstream. > > Can you raise this at https://gitlab.gnome.org/GNOME/network-manager-applet/ > please and report back with the issue number. Done: https://gitlab.gnome.org/GNOME/network-manager-applet/-/issues/130 I referenced #83, which covers indeed only part of the problem. Enrico -- GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini
Bug#986136: perl: shasum treats read errors like end of file
Control: clone -1 libdigest-sha-perl 6.02-1 On Tue, 30 Mar 2021 11:43:43 +0200, Stefan Arnold wrote: > I noticed his while testing with an filesystem that should give "read error" > at > a certain point which did not happen but instead gives a hash output. The > easiest way to reproduce is shasuming a folder: > > strace -e trace=read shasum 0 ... > read(0, 0x56421603f620, 8192) = -1 EISDIR (Ist ein Verzeichnis) > da39a3ee5e6b4b0d3255bfef95601890afd80709 - > +++ exited with 0 +++ > > > Read gives a read error but shasum does not pass it. Thanks for your bug report. This seems to happen in Digest::SHA, but I leave the detailed investigation to someone faster :) I note that both /usr/bin/shasum and Digest::SHA are in both src:perl and libdigest-sha-perl, hence cloning the bug. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Led Zeppelin: Kashmir signature.asc Description: Digital Signature
Bug#986158: unblock: python-oslo.serialization/4.0.2-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package python-oslo.serialization
This is a bugfix point release from uptream. Debdiff
looks reasonable to me. Your thoughts?
Please unblock python-oslo.serialization/4.0.2-1
diff -Nru python-oslo.serialization-4.0.1/debian/changelog
python-oslo.serialization-4.0.2/debian/changelog
--- python-oslo.serialization-4.0.1/debian/changelog2020-10-16
10:09:28.0 +0200
+++ python-oslo.serialization-4.0.2/debian/changelog2021-03-30
16:51:52.0 +0200
@@ -1,3 +1,9 @@
+python-oslo.serialization (4.0.2-1) unstable; urgency=medium
+
+ * New upstream release.
+
+ -- Thomas Goirand Tue, 30 Mar 2021 16:51:52 +0200
+
python-oslo.serialization (4.0.1-2) unstable; urgency=medium
* Uploading to unstable.
diff -Nru python-oslo.serialization-4.0.1/.gitreview
python-oslo.serialization-4.0.2/.gitreview
--- python-oslo.serialization-4.0.1/.gitreview 2020-07-24 17:36:23.0
+0200
+++ python-oslo.serialization-4.0.2/.gitreview 2021-02-02 14:45:37.0
+0100
@@ -1,4 +1,5 @@
[gerrit]
host=review.opendev.org
port=29418
-project=openstack/oslo.serialization.git
\ No newline at end of file
+project=openstack/oslo.serialization.git
+defaultbranch=stable/victoria
diff -Nru python-oslo.serialization-4.0.1/lower-constraints.txt
python-oslo.serialization-4.0.2/lower-constraints.txt
--- python-oslo.serialization-4.0.1/lower-constraints.txt 2020-07-24
17:36:23.0 +0200
+++ python-oslo.serialization-4.0.2/lower-constraints.txt 1970-01-01
01:00:00.0 +0100
@@ -1,35 +0,0 @@
-appdirs==1.3.0
-Babel==2.3.4
-bandit==1.4.0
-coverage==4.0
-debtcollector==1.2.0
-extras==1.0.0
-fixtures==3.0.0
-gitdb==0.6.4
-GitPython==1.0.1
-ipaddress===1.0.17
-iso8601==0.1.11
-keystoneauth1==3.4.0
-linecache2==1.0.0
-mox3==0.20.0
-msgpack==0.5.2
-netaddr==0.7.18
-netifaces==0.10.4
-os-client-config==1.28.0
-oslo.i18n==3.15.3
-oslo.utils==3.33.0
-oslotest==3.2.0
-pbr==2.0.0
-pyparsing==2.1.0
-python-mimeparse==1.6.0
-python-subunit==1.0.0
-pytz==2013.6
-requests==2.14.2
-requestsexceptions==1.2.0
-smmap==0.9.0
-stestr==2.0.0
-stevedore==1.20.0
-testtools==2.2.0
-traceback2==1.4.0
-unittest2==1.1.0
-wrapt==1.7.0
diff -Nru python-oslo.serialization-4.0.1/oslo_serialization/jsonutils.py
python-oslo.serialization-4.0.2/oslo_serialization/jsonutils.py
--- python-oslo.serialization-4.0.1/oslo_serialization/jsonutils.py
2020-07-24 17:36:23.0 +0200
+++ python-oslo.serialization-4.0.2/oslo_serialization/jsonutils.py
2021-02-02 14:45:37.0 +0100
@@ -33,6 +33,7 @@
import datetime
import functools
import inspect
+import io
import itertools
import json
import uuid
@@ -161,7 +162,7 @@
# Python 3 does not have iteritems
elif hasattr(value, 'items'):
return recursive(dict(value.items()), level=level + 1)
-elif hasattr(value, '__iter__'):
+elif hasattr(value, '__iter__') and not isinstance(value, io.IOBase):
return list(map(recursive, value))
elif convert_instances and hasattr(value, '__dict__'):
# Likely an instance of something. Watch for cycles.
diff -Nru
python-oslo.serialization-4.0.1/oslo_serialization/tests/test_jsonutils.py
python-oslo.serialization-4.0.2/oslo_serialization/tests/test_jsonutils.py
--- python-oslo.serialization-4.0.1/oslo_serialization/tests/test_jsonutils.py
2020-07-24 17:36:23.0 +0200
+++ python-oslo.serialization-4.0.2/oslo_serialization/tests/test_jsonutils.py
2021-02-02 14:45:37.0 +0100
@@ -401,6 +401,16 @@
ret = jsonutils.to_primitive(obj, fallback=lambda _: 'fallback')
self.assertEqual('fallback', ret)
+def test_fallback_typeerror_IO_object(self):
+# IO Objects are not callable, cause a TypeError in to_primitive()
+obj = io.IOBase
+
+ret = jsonutils.to_primitive(obj)
+self.assertEqual(str(obj), ret)
+
+ret = jsonutils.to_primitive(obj, fallback=lambda _: 'fallback')
+self.assertEqual('fallback', ret)
+
def test_exception(self):
self.assertIn(jsonutils.to_primitive(ValueError("an exception")),
["ValueError('an exception',)",
diff -Nru
python-oslo.serialization-4.0.1/releasenotes/notes/bug-1908607-fix-json-to_primitive-IO-OBjects-04faff4a1b5cf48f.yaml
python-oslo.serialization-4.0.2/releasenotes/notes/bug-1908607-fix-json-to_primitive-IO-OBjects-04faff4a1b5cf48f.yaml
---
python-oslo.serialization-4.0.1/releasenotes/notes/bug-1908607-fix-json-to_primitive-IO-OBjects-04faff4a1b5cf48f.yaml
1970-01-01 01:00:00.0 +0100
+++
python-oslo.serialization-4.0.2/releasenotes/notes/bug-1908607-fix-json-to_primitive-IO-OBjects-04faff4a1b5cf48f.yaml
2021-02-02 14:45:37.0 +0100
@@ -0,0 +1,5 @@
+---
+fixes:
+ - |
+`Bug #1908607 `_: Fix
+json
Bug#986157: unblock: libchemistry-opensmiles-perl/0.4.3-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear release-team,
I am seeking pre-approval to upload libchemistry-opensmiles-perl/0.4.3-2.
[ Reason ]
libchemistry-opensmiles-perl/0.4.3-1 has a bug which has been fixed
upstream (also by me). The bug is in code logic detecting aromatic bonds
in chemical compounds, and as such is not specific to Debian. Fix has
been released in 0.4.5. libchemistry-opensmiles-perl/0.4.3-2 fixes this
bug in unstable via patch.
[ Impact ]
Without the fix, users of libchemistry-opensmiles-perl will observe
false-negatives in aromatic bond detection.
[ Tests ]
* Built on clean sid chroot;
* Upstream regression test for the bug passes.
[ Risks ]
Changes are minimal and are unlikely to affect other packages
negatively. Currently libchemistry-opensmiles-perl is a leaf package in
Debian.
[ Checklist ]
[*] all changes are documented in the d/changelog
[*] I reviewed all changes and I approve them
[*] attach debdiff against the package in testing
unblock libchemistry-opensmiles-perl/0.4.3-2
Best,
Andrius
diff -Nru libchemistry-opensmiles-perl-0.4.3/debian/changelog
libchemistry-opensmiles-perl-0.4.3/debian/changelog
--- libchemistry-opensmiles-perl-0.4.3/debian/changelog 2021-01-28
05:16:40.0 -0500
+++ libchemistry-opensmiles-perl-0.4.3/debian/changelog 2021-03-30
07:23:23.0 -0400
@@ -1,3 +1,10 @@
+libchemistry-opensmiles-perl (0.4.3-2) unstable; urgency=medium
+
+ * Applying upstream commit 6b8267f0bbc87d877bce87bfd28d4538c3f95ee5 as
+a patch fixing detection of aromatic bonds.
+
+ -- Andrius Merkys Tue, 30 Mar 2021 07:23:23 -0400
+
libchemistry-opensmiles-perl (0.4.3-1) unstable; urgency=medium
* New upstream version 0.4.3
diff -Nru
libchemistry-opensmiles-perl-0.4.3/debian/patches/6b8267f0bbc87d877bce87bfd28d4538c3f95ee5.patch
libchemistry-opensmiles-perl-0.4.3/debian/patches/6b8267f0bbc87d877bce87bfd28d4538c3f95ee5.patch
---
libchemistry-opensmiles-perl-0.4.3/debian/patches/6b8267f0bbc87d877bce87bfd28d4538c3f95ee5.patch
1969-12-31 19:00:00.0 -0500
+++
libchemistry-opensmiles-perl-0.4.3/debian/patches/6b8267f0bbc87d877bce87bfd28d4538c3f95ee5.patch
2021-03-30 07:19:40.0 -0400
@@ -0,0 +1,36 @@
+From 6b8267f0bbc87d877bce87bfd28d4538c3f95ee5 Mon Sep 17 00:00:00 2001
+From: Andrius Merkys
+Date: Thu, 25 Mar 2021 13:28:22 +0200
+Subject: [PATCH] Fixing a bug due to incorrectly identified aromatic bond.
+
+---
+ lib/Chemistry/OpenSMILES/Parser.yp | 2 +-
+ t/06_write.t | 2 ++
+ 2 files changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/lib/Chemistry/OpenSMILES/Parser.yp
b/lib/Chemistry/OpenSMILES/Parser.yp
+index 8094826..f0e0a13 100644
+--- a/lib/Chemistry/OpenSMILES/Parser.yp
b/lib/Chemistry/OpenSMILES/Parser.yp
+@@ -60,7 +60,7 @@ chain: atom
+
+ $_[2]->{graph}->add_edge( $_[1]->{last}, $_[2] );
+
+-if( is_aromatic $_[1]->{last} && is_aromatic $_[1]->{last} ) {
++if( is_aromatic $_[1]->{last} && is_aromatic $_[2] ) {
+ $_[2]->{graph}->set_edge_attribute( $_[1]->{last},
+ $_[2],
+ 'bond',
+diff --git a/t/06_write.t b/t/06_write.t
+index aee54c5..c0f4656 100644
+--- a/t/06_write.t
b/t/06_write.t
+@@ -19,6 +19,8 @@ my @cases = (
+ # Chirality information is preserved:
+ [ 'N[C@](Br)(O)C', 'N([C@](Br)(O)(C))' ],
+ [ 'N[C@@](Br)(O)C', 'N([C@@](Br)(O)(C))' ],
++# A regression test for previously incorrectly identified aromatic bond:
++[ 'c1(c(1)F)C(=O)[O-]', 'c:1(:c(:c(:c(:c(:c:1(F))(C(=O)([O-]))' ],
+ );
+
+ plan tests => 2 * scalar @cases;
diff -Nru libchemistry-opensmiles-perl-0.4.3/debian/patches/series
libchemistry-opensmiles-perl-0.4.3/debian/patches/series
--- libchemistry-opensmiles-perl-0.4.3/debian/patches/series1969-12-31
19:00:00.0 -0500
+++ libchemistry-opensmiles-perl-0.4.3/debian/patches/series2021-03-30
07:19:55.0 -0400
@@ -0,0 +1 @@
+6b8267f0bbc87d877bce87bfd28d4538c3f95ee5.patch
Bug#986156: linux-image-5.10.0-5-rt-amd64: qemu/kvm caused trouble on the 5.10 PREMPT_RT kernel
Package: src:linux Version: 5.10.24-1 Severity: important Dear Maintainer, * What led up to the situation? I used the tool debos https://github.com/go-debos/debos to create a debian image on my machine. debos uses qemu to setup an install environment for debian. After a while the process got stucked. * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? I got a kernel warning Mar 30 15:45:10 hpjp kernel: [ cut here ] Mar 30 15:45:10 hpjp kernel: WARNING: CPU: 3 PID: 339240 at fs/eventfd.c:74 eventfd_signal+0x7e/0x90 Mar 30 15:45:10 hpjp kernel: Modules linked in: hid_plantronics nls_utf8 cifs libdes rpcsec_gss_krb5 nfsv4 dns_resolver nfs nfs_ssc fscache nfsd au> Mar 30 15:45:10 hpjp kernel: cpufreq_ondemand snd_soc_dmic cmac snd_sof_pci algif_hash snd_sof_intel_byt algif_skcipher snd_sof_intel_ipc af_alg s> Mar 30 15:45:10 hpjp kernel: videobuf2_v4l2 hid_sensor_als snd r8152 hid_sensor_trigger mii soundcore drbg videobuf2_common cfg80211 hid_sensor_ii> Mar 30 15:45:10 hpjp kernel: intel_ish_ipc i2c_i801 crct10dif_common glue_helper intel_lpss i2c_hid i2c_smbus idma64 usb_common intel_ishtp hid wm> Mar 30 15:45:10 hpjp kernel: CPU: 3 PID: 339240 Comm: qemu-system-x86 Tainted: GW 5.10.0-5-rt-amd64 #1 Debian 5.10.24-1 Mar 30 15:45:10 hpjp kernel: Hardware name: HP HP EliteBook 840 G7 Notebook PC/8723, BIOS S70 Ver. 01.04.02 01/18/2021 Mar 30 15:45:10 hpjp kernel: check_preemption_disabled: 44 callbacks suppressed Mar 30 15:45:10 hpjp kernel: BUG: using smp_processor_id() in preemptible [] code: qemu-system-x86/339240 Mar 30 15:45:10 hpjp kernel: caller is print_stop_info+0x1b/0x40 Mar 30 15:45:10 hpjp kernel: CPU: 3 PID: 339240 Comm: qemu-system-x86 Tainted: GW 5.10.0-5-rt-amd64 #1 Debian 5.10.24-1 Mar 30 15:45:10 hpjp kernel: Hardware name: HP HP EliteBook 840 G7 Notebook PC/8723, BIOS S70 Ver. 01.04.02 01/18/2021 Mar 30 15:45:10 hpjp kernel: Call Trace: Mar 30 15:45:10 hpjp kernel: dump_stack+0x6b/0x83 Mar 30 15:45:10 hpjp kernel: check_preemption_disabled+0xcd/0xd0 Mar 30 15:45:10 hpjp kernel: print_stop_info+0x1b/0x40 Mar 30 15:45:10 hpjp kernel: ? eventfd_signal+0x7e/0x90 Mar 30 15:45:10 hpjp kernel: show_regs+0x15/0x50 Mar 30 15:45:10 hpjp kernel: __warn+0x7d/0xb0 Mar 30 15:45:10 hpjp kernel: ? eventfd_signal+0x7e/0x90 Mar 30 15:45:10 hpjp kernel: report_bug+0x9a/0xc0 Mar 30 15:45:10 hpjp kernel: handle_bug+0x35/0x80 Mar 30 15:45:10 hpjp kernel: exc_invalid_op+0x14/0x70 Mar 30 15:45:10 hpjp kernel: asm_exc_invalid_op+0x12/0x20 Mar 30 15:45:10 hpjp kernel: RIP: 0010:eventfd_signal+0x7e/0x90 Mar 30 15:45:10 hpjp kernel: Code: 01 00 00 00 be 03 00 00 00 4c 89 ef e8 db b0 db ff 65 ff 0d 74 e4 0f 7d 4c 89 ef e8 cc bd 5b 00 4c 89 e0 5b 5d 4> Mar 30 15:45:10 hpjp kernel: RSP: 0018:b81b91d47d50 EFLAGS: 00010202 Mar 30 15:45:10 hpjp kernel: RAX: 0001 RBX: 9da5c68d4000 RCX: Mar 30 15:45:10 hpjp kernel: RDX: fe007000 RSI: 0001 RDI: 9da5c4c6fb40 Mar 30 15:45:10 hpjp kernel: RBP: b81b91d47db0 R08: R09: fe007000 Mar 30 15:45:10 hpjp kernel: R10: R11: R12: 0040 Mar 30 15:45:10 hpjp kernel: R13: 9da7be878000 R14: R15: 9da7be878038 Mar 30 15:45:10 hpjp kernel: ioeventfd_write+0x51/0x80 [kvm] Mar 30 15:45:10 hpjp kernel: __kvm_io_bus_write+0x88/0xb0 [kvm] Mar 30 15:45:10 hpjp kernel: kvm_io_bus_write+0x54/0x80 [kvm] Mar 30 15:45:10 hpjp kernel: handle_ept_misconfig+0x45/0x130 [kvm_intel] Mar 30 15:45:10 hpjp kernel: kvm_arch_vcpu_ioctl_run+0xc9d/0x1780 [kvm] Mar 30 15:45:10 hpjp kernel: kvm_vcpu_ioctl+0x239/0x5f0 [kvm] Mar 30 15:45:10 hpjp kernel: __x64_sys_ioctl+0x83/0xb0 Mar 30 15:45:10 hpjp kernel: do_syscall_64+0x33/0x80 Mar 30 15:45:10 hpjp kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Mar 30 15:45:10 hpjp kernel: RIP: 0033:0x7f10d88fecc7 Mar 30 15:45:10 hpjp kernel: Code: 00 00 00 48 8b 05 c9 91 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 0> Mar 30 15:45:10 hpjp kernel: RSP: 002b:7f10d5d37508 EFLAGS: 0246 ORIG_RAX: 0010 Mar 30 15:45:10 hpjp kernel: RAX: ffda RBX: ae80 RCX: 7f10d88fecc7 Mar 30 15:45:10 hpjp kernel: RDX: RSI: ae80 RDI: 000b Mar 30 15:45:10 hpjp kernel: RBP: 560a90457d90 R08: 560a8f644618 R09: Mar 30 15:45:10 hpjp kernel: R10: 0001 R11: 0246 R12: Mar 30 15:45:10 hpjp kernel: R13: 560a8fa8aaa0 R14: R15: Mar 30 15:45:10 hpjp kernel: RIP: 0010:eventfd_signal+0x7e/0x90 Mar 30 15:45:10 hpjp kernel: Code: 01 00 00 00 be 03 00 00 00 4c 89 ef e8 db b0 db ff 65 ff 0d 74 e4 0f 7d 4c 89 ef e8 cc bd 5b 00 4c 89 e0 5b 5d 4>
Bug#838952: fixed in w3m 0.5.3-30
Control: retitle -1 w3m: fails to render over 32767 lines in the table Control: tags -1 + patch pending On 2016-10-31 at 21:16, Tatsuya Kinoshita wrote: > Control: reopen -1 > The patch for this bug causes stack smashing, so reverted for now. I've noticed the problematic type mismatch of check_cell_width(). Fixed in the Git repo. - https://salsa.debian.org/debian/w3m/-/commit/1a9bcdf202f062e89bb73aa9b0bfe6e3c9b4d5d9 - https://salsa.debian.org/debian/w3m/-/commit/540eb60fddd0869ef66b6cf5e107f1a0a1eec21a Thanks, -- Tatsuya Kinoshita pgpSWa3YsUbIv.pgp Description: PGP signature
Bug#985886: Acknowledgement (klick crashes after approx. 8 klicks)
Probably a user mistake. This can be closed.
Bug#986153: add support not to build udeb / don't use link optimization
Package: src:cairo Version: 1.16.0-5 Tags: patch while the package doesn't create udeb's with the noudeb profile, it still builds a separate tree. trying to enable link time optimization results into a failing test. Both Fedora and Opensuse kept lto enabled for cairo, but also ignoring test failures during the build. The line optimize=-lto currently doesn't have any affect for Debian, afaics. I didn't investigate the test failure itself. test and build log at https://launchpad.net/ubuntu/+archive/test-rebuild-20210325-hirsute/+build/21214109 patch at http://launchpadlibrarian.net/530874655/cairo_1.16.0-5build1_1.16.0-5ubuntu1.diff.gz
Bug#986152: RFH: shorewall -- Shoreline Firewall, netfilter configurator
Package: wnpp Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I request assistance with maintaining the shorewall package. The package description is: Shorewall allows firewall/gateway requirements to be described using entries in a set of configuration files. It reads those configuration files and, with the help of the iptables utility, configures netfilter to match these requirements. . Shorewall supports a wide range of router/firewall/gateway applications, traffic shaping and almost every type of VPN. I have maintained the Shorewall packages in Debian for quite a few years now, but my time to work on them has diminished. The reality is that there are several issues that require attention, which I cannot at the moment attend to. Over time the severity of these issues will likely increase and the eventual result is that the Shorewall packages could be removed from Debian. If someone were to be able to devote some effort toward helping, I could help with reviewing patches, sponsoring uploads, etc. It is still my hope that I will find additional time to work on the Shorewall Debian packages, but I do not want to make my inability to find enough time now cause users of Debian to lose out on access to good quality Shorewall packages. Note that this RFH really encompasses the shorewall, shorewall6, shorewall-lite, shorewall6-lite, shorewall-doc, and shorewall-core source packages. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEIYZ1DR4ae5UL01q7ldFmTdL1kUIFAmBjLvUACgkQldFmTdL1 kUI9pA/9FqVYHab6iWdVfUpMm8hzCDYLEs1SRk3cIDWyMWWkGS5Me/gXKi0tok+0 EIN/I6jjaTctM/atDFuq3u8c8exdqrCszeIrrjjPiS1uKhUwYPc0N+obu5RHohOt ns2F2vhg9C/pSMH1J4g1JWwQA5sqjxXWoP4WxhS8H5JdcxBI48pPETFuG4dsJQQx SiwmA53PqrBao8c1p3c0Z+efDhIZgUp5GRANS9lbzCtNsj0s7zH/tHqsjtP82Jy+ IKJccPv5u1X/ChRf6AITD7fI9Xsn3qcxikfZgD5O0Yd9/AGJtbsR590yw4jZHFYZ qIYFEOGJslYOXx4brAq5Cweevw9VzvIyjPeBjtKoOGYbSadH7+A357UIOqBUWvji ZEaMVeO2V0s29+2RYE4A1bvbqOSkuuDQ6WG9z1z8qE2UhN4G65sljw6tYPtDOGZ3 N2jkBHo1N+9+OuC2rjKkuCfF1yfgVNbvlSUjMidNnjWRiW+PA6o7cVK8c8fuYQK3 ML/Pvib2LvEoyeetTPWijcnePr/Wrw5U0OeRxCNAXxfFBw4/JSyqudF/wiuvEfUV hqEjttomIEkcSF8bf81DvQoxzjBnnQjrFS566esUR71VAjGuqEk4WVaL0ENhPNxL Fjkjt5xIckCJIdvmCDPaRz66MrSPMGY+JX3eBjvGp33wgKJLVsY= =apRC -END PGP SIGNATURE-
Bug#986151: please unblock firmware-nonfree 20210315-2
Package: release.debian.org Thanks For latest amd gpu support and newer iwlwifi firmware. Please find attached the source diff, which is mainly removal from upstreamed patches in 20210208-4. There are two known issues, which have no known upstream fix yet: 1) Raspberry Pi 4 5 Ghz failure #985632 (new cypress firmware regression, old brcm worked, raspberry pi distro has a newer firmware that is not pushed upstream yet) 3) iwlwifi still behaves like a bad boy in several setups #963025 thank you for giving it a pass into testing after 10d (: warm greetings! diff --git a/debian/changelog b/debian/changelog index 5dfb071..ef12a05 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,41 @@ +firmware-nonfree (20210315-2) unstable; urgency=medium + + * Support Cubietech Cubietruck and Jumper EZpad mini 3 tablet +(closes: #985740, #844056) + * Add firmware-atheros recommends to firmware-qcom-soc (closes: #985743) +Thanks to Andreas Beckmann + * Add missing brcmfmac4366c firmware. + * Add more missing BCM4334, BCM43340 and BCM43430 NVRAMS. + + -- maximilian attems Sat, 27 Mar 2021 13:03:31 +0100 + +firmware-nonfree (20210315-1) unstable; urgency=medium + + * Unstable upload of green sardine support (closes: #984874) + + -- maximilian attems Sat, 20 Mar 2021 19:14:23 +0100 + +firmware-nonfree (20210315-1~exp1) experimental; urgency=medium + + * New upstream version: +- rtw88: RTL8822C: Update normal firmware to v9.9.5 (closes: #983255) +- amdgpu: add initial firmware for green sardine (closes: #984852) +- silabs: add new firmware for WF200 +- brcm: Fix Raspberry Pi 4B NVRAM file +- Add symlink for BananaPi M2 to brcmfmac43430-sdio config +- WHENCE: add missing symlink for BananaPi M3 +- rtw89: 8852a: add firmware v0.9.12.2 +- linux-firmware: add frimware for mediatek bluetooth chip (MT7921) +- iwlwifi: update 7265D firmware +- iwlwifi: update 9000-family firmwares (closes: #963025) +- iwlwifi: add new FWs from core59-66 release +- rtw88: 8822c: Update normal firmware to v9.9.6 +- linux-firmware: Update firmware file for Intel Bluetooth AX201 +- linux-firmware: Update firmware file for Intel Bluetooth AX200 +- linux-firmware: Update firmware file for Intel Bluetooth AX210 + + -- maximilian attems Tue, 16 Mar 2021 16:56:56 +0100 + firmware-nonfree (20210208-4) unstable; urgency=medium * List MediaTek mt8183 firmware. diff --git a/debian/config/amd-graphics/defines b/debian/config/amd-graphics/defines index 0027f0d..e86494b 100644 --- a/debian/config/amd-graphics/defines +++ b/debian/config/amd-graphics/defines @@ -39,6 +39,17 @@ files: amdgpu/fiji_smc.bin amdgpu/fiji_uvd.bin amdgpu/fiji_vce.bin + amdgpu/green_sardine_asd.bin + amdgpu/green_sardine_ce.bin + amdgpu/green_sardine_dmcub.bin + amdgpu/green_sardine_me.bin + amdgpu/green_sardine_mec2.bin + amdgpu/green_sardine_mec.bin + amdgpu/green_sardine_pfp.bin + amdgpu/green_sardine_rlc.bin + amdgpu/green_sardine_sdma.bin + amdgpu/green_sardine_ta.bin + amdgpu/green_sardine_vcn.bin amdgpu/hainan_ce.bin amdgpu/hainan_k_smc.bin amdgpu/hainan_mc.bin @@ -731,6 +742,39 @@ version: 1.87.12 [amdgpu/fiji_vce.bin_base] desc: "Fiji" VCE firmware +[amdgpu/green_sardine_asd.bin_base] +desc: AMD RYZEN 5000 ASD firmware + +[amdgpu/green_sardine_ce.bin_base] +desc: AMD RYZEN 5000 CE firmware + +[amdgpu/green_sardine_dmcub.bin_base] +desc: AMD RYZEN 5000 DMCUB firmware + +[amdgpu/green_sardine_me.bin_base] +desc: AMD RYZEN 5000 ME firmware + +[amdgpu/green_sardine_mec2.bin_base] +desc: AMD RYZEN 5000 MEC2 firmware + +[amdgpu/green_sardine_mec.bin_base] +desc: AMD RYZEN 5000 MEC firmware + +[amdgpu/green_sardine_pfp.bin_base] +desc: AMD RYZEN 5000 PFP firmware + +[amdgpu/green_sardine_rlc.bin_base] +desc: AMD RYZEN 5000 RLC firmware + +[amdgpu/green_sardine_sdma.bin_base] +desc: AMD RYZEN 5000 SDMA firmware + +[amdgpu/green_sardine_ta.bin_base] +desc: AMD RYZEN 5000 TA firmware + +[amdgpu/green_sardine_vcn.bin_base] +desc: AMD RYZEN 5000 VCN firmware + [amdgpu/hainan_ce.bin_base] desc: Radeon HD 8500M series and R5 M200 CE microcode diff --git a/debian/config/brcm80211/defines b/debian/config/brcm80211/defines index ddba14d..522b4eb 100644 --- a/debian/config/brcm80211/defines +++ b/debian/config/brcm80211/defines @@ -14,11 +14,16 @@ files: brcm/brcmfmac43242a.bin brcm/brcmfmac4329-sdio.bin brcm/brcmfmac4330-sdio.bin + brcm/brcmfmac4330-sdio.Prowise-PT301.txt + brcm/brcmfmac43340-sdio.meegopad-t08.txt + brcm/brcmfmac43340-sdio.pov-tab-p1006w-data.txt brcm/brcmfmac4334-sdio.bin brcm/brcmfmac4335-sdio.bin brcm/brcmfmac43340-sdio.bin brcm/brcmfmac43362-sdio.bin + brcm/brcmfmac43362-sdio.cubietech,cubietruck.txt brcm/brcmfmac43362-sdio.lemaker,bananapro.txt + brcm/brcmfmac43430a0-sdio.jumper-ezpad-mini3.txt brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-plus.txt brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-zero.txt
Bug#986150: dnsmasq-base: Bugs in manpage
Package: dnsmasq-base Version: 2.80-1+deb10u1 Severity: minor Dear Maintainer, the manpage of dnsmasq has two bugs: --min-port= [..]the ports used will always to larger[..] ==> Replace "to" with "be". -S, --local, --server=[/[]/[domain/]][[#][@|[#]] ==> The number of parentheses is unbalanced, one closing paranthesis is missing here. I have no idea where it should be inserted. -- System Information: Debian Release: 10.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-16-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dnsmasq-base depends on: ii adduser 3.118 ii libc62.28-10 ii libdbus-1-3 1.12.20-0+deb10u1 ii libgmp10 2:6.1.2+dfsg-4 ii libhogweed4 3.4.1-1 ii libidn11 1.33-2.2 ii libnetfilter-conntrack3 1.0.7-1 ii libnettle6 3.4.1-1 ii libnfnetlink01.0.1-3+b1 Versions of packages dnsmasq-base recommends: ii dns-root-data 2019031302 dnsmasq-base suggests no packages. -- no debconf information
Bug#986143: openstack-dashboard: fails to upgrade from 'buster': KeyError: 'django' in "/usr/lib/python3/dist-packages/django/template/utils.py", line 65
On 30/03/2021 14.49, Thomas Goirand wrote: It's my opinion that the issue is probably a missing breaks: python3-django-horizon (<< 3:18.6.2) in python3-django. That doesn't help. Both packages are still at the buster version when the failure happens. The only python3-django-* packages already upgraded so far are: python3-django-appconf python3-django-babel python3-django-pyscss Andreas
Bug#986149: unblock: libgweather/3.36.1-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libgweather [ Reason ] met.no (Norwegian Weather institute) asked libgweather upstream to set in the User-Agent the application that is actually doing the request to their service. The version of the library in bullseye do not have the needed patch We have backported almost all the functional patches from 3.36.2 already, so an alternative would be to just update to 3.36.2 [ Impact ] With out that patch met.no could consider that we are not following their TOS and could block our user to use their service. [ Tests ] gnome-weather still shows the weather information. I didn't test with an application not providing a .desktop file, but the code seems to take that case into account [ Risks ] The code is self contained and at worst the string "null" will be added the user agent. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing unblock libgweather/3.36.1-3
Bug#986148: live-build uses stable-security/updates instead of stable-security
Package: live-build
Version: 1:20210329
Severity: important
Hi,
In upload of version 1:20210329, the file:
functions/sourcelist.sh
has line 91/92:
echo "deb ${PARENT_MIRROR_SECURITY} ${PARENT_DISTRIBUTION}-security/updates
${LB_PARENT_ARCHIVE_AREAS}" >> "${PARENT_LIST_FILE}"
echo "deb-src ${PARENT_MIRROR_SECURITY} ${PARENT_DISTRIBUTION}-security/updates
${LB_PARENT_ARCHIVE_AREAS}" >> "${PARENT_LIST_FILE}"
This is wrong, it should be ${PARENT_DISTRIBUTION}-security without the
lasting "/updates". It still works because Debian repositories have symlinks,
but Ansgar just confirmed what I thought: we shouldn't be using a lasting
/updates at the end. Please remove it.
Cheers,
Thomas Goirand (zigo)
Bug#986147: libpgplot-perl: pgplot demo in pdl does not work
Package: libpgplot-perl
Version: 1:2.24-1+b2
Severity: important
Dear Maintainer,
* What led up to the situation?
Installed this package and pdl and wanted to use the pgplot
functionality. On Debian Buster this worked as expected.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I called pdl and then I entered the command ´demo pgplot´
* What was the outcome of this action?
I got an error message.
Undefined subroutine ::Demos::PGPLOT_demo::run called at /usr/bin/perldl
line 453.
at /usr/bin/perldl line 453.
main::demo("pgplot") called at (eval 63) line 4
main::__ANON__() called at /usr/bin/perldl line 719
eval {...} called at /usr/bin/perldl line 719
main::eval_and_report("demo 'pgplot'\x{a}") called at /usr/bin/perldl
line 655
main::process_input() called at /usr/bin/perldl line 675
eval {...} called at /usr/bin/perldl line 675
* What outcome did you expect instead?
A graphical plot pops up on the desktop.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-5-rt-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libpgplot-perl depends on:
ii libc6 2.31-10
ii libcpgplot0 1.2.0-1
ii libpgplot0 1.2.0-1
ii perl5.32.1-3
ii perl-base [perlapi-5.32.0] 5.32.1-3
libpgplot-perl recommends no packages.
libpgplot-perl suggests no packages.
-- no debconf information
Bug#963025: fixed in firmware-nonfree 20210315-1~exp1
reopen 963025 found -1 20210315-2 tags -1 moreinfo stop > [18661.586025] CPU: 0 PID: 8408 Comm: hostapd Tainted: GW > 5.10.0-5-amd64 #1 Debian 5.10.24-1 > [18661.586029] Hardware name: LENOVO 20N2007GGE/20N2007GGE, BIOS N2IET81W > (1.59 ) 11/29/2019 Please could you upgrade the BIOS to latest for T490, 1.72 2021/03/17 to exclude this guy fault.
Bug#986143: openstack-dashboard: fails to upgrade from 'buster': KeyError: 'django' in "/usr/lib/python3/dist-packages/django/template/utils.py", line 65
On 30/03/2021 14.49, Thomas Goirand wrote: There are probably some missing versioned dependencies s.t. openstack-dashboard configuration is attempted with some packages still at the version from buster. Hi Andreas, I don't think that's what's going on. Horizon has some trigger mechanismes to run the collect-static and compress jobs, whenever some components are upgraded. Which is what happens when you do "apt-get upgrade". However, at this point, Horizon itself isn't upgraded (it's still the Buster release), and consequently, it fails. Correct: Processing triggers for openstack-dashboard (3:14.0.2-3+deb10u2) ... Deleting 'auth/auth.module.js' Deleting 'auth/login/login-finder.directive.js' [...several 1000 lines...] django.template.library.InvalidTemplateLibrary: Invalid template library specified. ImportError raised when trying to load 'openstack_dashboard.templatetags.context_selection': cannot import name 'list_extensions' from 'novaclient.v2' (/usr/lib/python3/dist-packages/novaclient/v2/__init__.py) dpkg: error processing package openstack-dashboard (--configure): installed openstack-dashboard package post-installation script subprocess returned error exit status 1 The dpkg error make me think "configure" failed and not "triggered" It's my opinion that the issue is probably a missing breaks: python3-django-horizon (<< 3:18.6.2) in python3-django. In such case, we probably should reassign the bug to Django, no? Your thoughts? I'll try if that fixes the the upgrade path ... Andreas PS: but its still "some versioned constraint is missing" ;-)
Bug#986146: unblock: rabbitmq-server/3.8.9-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package rabbitmq-server
rabbitmq-server used to need a restart whenever logs where rotated.
That's no longer the case anymore. So the attached debdiff stops
using a sharedscript, making the service survive better to log rotation.
No impact for the users, just a better rabbitmq-server.
Debdiff attached.
Please unblock rabbitmq-server/3.8.9-2
diff -Nru rabbitmq-server-3.8.9/debian/changelog
rabbitmq-server-3.8.9/debian/changelog
--- rabbitmq-server-3.8.9/debian/changelog 2020-10-01 09:30:46.0
+0200
+++ rabbitmq-server-3.8.9/debian/changelog 2021-03-26 14:24:32.0
+0100
@@ -1,3 +1,14 @@
+rabbitmq-server (3.8.9-2) unstable; urgency=medium
+
+ * Do not use the /usr/sbin/rabbitmq-server wrapper in systemd service file
+(Closes: #947873).
+ * Use logrotate daily instead of weekly, and do not override the number of
+logs, so we don't keep too much of them.
+ * Do not use a sharedscripts, as rabbitmq-server detects the log rotation
+by itself (LP: #1921425).
+
+ -- Thomas Goirand Fri, 26 Mar 2021 14:24:52 +0100
+
rabbitmq-server (3.8.9-1) unstable; urgency=medium
* New upstream release.
diff -Nru rabbitmq-server-3.8.9/debian/rabbitmq-server.logrotate
rabbitmq-server-3.8.9/debian/rabbitmq-server.logrotate
--- rabbitmq-server-3.8.9/debian/rabbitmq-server.logrotate 2020-10-01
09:30:46.0 +0200
+++ rabbitmq-server-3.8.9/debian/rabbitmq-server.logrotate 2021-03-26
14:24:32.0 +0100
@@ -1,12 +1,7 @@
/var/log/rabbitmq/*.log {
-weekly
-missingok
-rotate 20
-compress
-delaycompress
-notifempty
-sharedscripts
-postrotate
-/etc/init.d/rabbitmq-server rotate-logs > /dev/null
-endscript
+ daily
+ missingok
+ compress
+ delaycompress
+ notifempty
}
diff -Nru rabbitmq-server-3.8.9/debian/rabbitmq-server.service
rabbitmq-server-3.8.9/debian/rabbitmq-server.service
--- rabbitmq-server-3.8.9/debian/rabbitmq-server.service2020-10-01
09:30:46.0 +0200
+++ rabbitmq-server-3.8.9/debian/rabbitmq-server.service2021-03-26
14:24:32.0 +0100
@@ -15,8 +15,10 @@
Restart=on-failure
RestartSec=10
WorkingDirectory=/var/lib/rabbitmq
-ExecStart=/usr/sbin/rabbitmq-server
+ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server
ExecStop=/usr/sbin/rabbitmqctl stop
+StandardOutput=append:/var/log/rabbitmq/rabbitmq-server.log
+StandardError=append:/var/log/rabbitmq/rabbitmq-server.error.log
[Install]
WantedBy=multi-user.target
Bug#986143: openstack-dashboard: fails to upgrade from 'buster': KeyError: 'django' in "/usr/lib/python3/dist-packages/django/template/utils.py", line 65
Dear Django maintainers, I've just reassigned this bug to python3-django. Indeed, it is my opinion that python3-django must add: Breaks: python3-django-horizon (<< 3:18.3.3~) (3:18.3.3 is the first version of Horizon with support for Django 2.2) otherwise doing "apt-get upgrade" from Buster to Bullseye fails, as per anbe's bug report. If you believe I'm wrong or if there's another way to fix this bug, please let me know. Cheers, Thomas Goirand (zigo)
Bug#986143: openstack-dashboard: fails to upgrade from 'buster': KeyError: 'django' in "/usr/lib/python3/dist-packages/django/template/utils.py", line 65
On 3/30/21 1:46 PM, Andreas Beckmann wrote: > Package: openstack-dashboard > Version: 3:18.6.2-2 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'buster'. > It installed fine in 'buster', then the upgrade to 'bullseye' fails. > > This failure was observed during a two-stage upgrade starting with > 'apt-get upgrade'. (Since this has failed, the subsequent > 'apt-get dist-upgrade' was not run). > (A plain upgrade using 'apt-get dist-upgrade' is successful.) > > There are probably some missing versioned dependencies s.t. > openstack-dashboard configuration is attempted with some packages > still at the version from buster. Hi Andreas, I don't think that's what's going on. Horizon has some trigger mechanismes to run the collect-static and compress jobs, whenever some components are upgraded. Which is what happens when you do "apt-get upgrade". However, at this point, Horizon itself isn't upgraded (it's still the Buster release), and consequently, it fails. It's my opinion that the issue is probably a missing breaks: python3-django-horizon (<< 3:18.6.2) in python3-django. In such case, we probably should reassign the bug to Django, no? Your thoughts? Cheers, Thomas Goirand (zigo)
Bug#963025: fixed in firmware-nonfree 20210315-1~exp1
On 16.03.21 17:34, Debian FTP Masters wrote: > Source: firmware-nonfree > Source-Version: 20210315-1~exp1 > Done: maximilian attems > > We believe that the bug you reported is fixed in the latest version of > firmware-nonfree, which is due to be installed in the Debian FTP archive. > > A summary of the changes between this version and the previous one is > attached. > > Thank you for reporting the bug, which will now be closed. If you > have further comments please address them to 963...@bugs.debian.org, > and the maintainer will reopen the bug report if appropriate. > > Debian distribution maintenance software > pp. > maximilian attems (supplier of updated firmware-nonfree package) - snip - I cannot confirm that the bug is fixed. firmware-iwlwifi 20210315-2 is installed. dmesg output when wireless interface stopped working: [18654.227951] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [18654.228331] iwlwifi :00:14.3: Start IWL Error Log Dump: [18654.228339] iwlwifi :00:14.3: Status: 0x0040, count: 6 [18654.228345] iwlwifi :00:14.3: Loaded firmware version: 46.6f9f215c.0 9000-pu-b0-jf-b0-46.ucode [18654.228353] iwlwifi :00:14.3: 0x3203 | ADVANCED_SYSASSERT [18654.228358] iwlwifi :00:14.3: 0xA200 | trm_hw_status0 [18654.228363] iwlwifi :00:14.3: 0x | trm_hw_status1 [18654.228368] iwlwifi :00:14.3: 0x00488C0E | branchlink2 [18654.228373] iwlwifi :00:14.3: 0x00478EDE | interruptlink1 [18654.228378] iwlwifi :00:14.3: 0x | interruptlink2 [18654.228383] iwlwifi :00:14.3: 0x0004 | data1 [18654.228388] iwlwifi :00:14.3: 0xDEADBEEF | data2 [18654.228393] iwlwifi :00:14.3: 0xDEADBEEF | data3 [18654.228398] iwlwifi :00:14.3: 0x | beacon time [18654.228403] iwlwifi :00:14.3: 0x0290028A | tsf low [18654.228408] iwlwifi :00:14.3: 0x | tsf hi [18654.228412] iwlwifi :00:14.3: 0x | time gp1 [18654.228417] iwlwifi :00:14.3: 0x0290028B | time gp2 [18654.228422] iwlwifi :00:14.3: 0x0001 | uCode revision type [18654.228427] iwlwifi :00:14.3: 0x002E | uCode version major [18654.228432] iwlwifi :00:14.3: 0x6F9F215C | uCode version minor [18654.228437] iwlwifi :00:14.3: 0x0312 | hw version [18654.228442] iwlwifi :00:14.3: 0x00C89008 | board version [18654.228447] iwlwifi :00:14.3: 0x8073FC28 | hcmd [18654.228452] iwlwifi :00:14.3: 0x24022000 | isr0 [18654.228457] iwlwifi :00:14.3: 0x | isr1 [18654.228461] iwlwifi :00:14.3: 0x08201802 | isr2 [18654.228466] iwlwifi :00:14.3: 0x004168C0 | isr3 [18654.228471] iwlwifi :00:14.3: 0x | isr4 [18654.228476] iwlwifi :00:14.3: 0x0940001C | last cmd Id [18654.228480] iwlwifi :00:14.3: 0xCEB6 | wait_event [18654.228485] iwlwifi :00:14.3: 0x10D4 | l2p_control [18654.228490] iwlwifi :00:14.3: 0x00018034 | l2p_duration [18654.228495] iwlwifi :00:14.3: 0x0007 | l2p_mhvalid [18654.228500] iwlwifi :00:14.3: 0x8100 | l2p_addr_match [18654.228505] iwlwifi :00:14.3: 0x000D | lmpm_pmg_sel [18654.228510] iwlwifi :00:14.3: 0x28010905 | timestamp [18654.228514] iwlwifi :00:14.3: 0xD8B8 | flow_handler [18654.228663] iwlwifi :00:14.3: Start IWL Error Log Dump: [18654.228668] iwlwifi :00:14.3: Status: 0x0040, count: 7 [18654.228674] iwlwifi :00:14.3: 0x2070 | NMI_INTERRUPT_LMAC_FATAL [18654.228679] iwlwifi :00:14.3: 0x | umac branchlink1 [18654.228684] iwlwifi :00:14.3: 0xC0088BBE | umac branchlink2 [18654.228689] iwlwifi :00:14.3: 0xC0084458 | umac interruptlink1 [18654.228694] iwlwifi :00:14.3: 0xC0084458 | umac interruptlink2 [18654.228699] iwlwifi :00:14.3: 0x0800 | umac data1 [18654.228704] iwlwifi :00:14.3: 0xC0084458 | umac data2 [18654.228708] iwlwifi :00:14.3: 0xDEADBEEF | umac data3 [18654.228713] iwlwifi :00:14.3: 0x002E | umac major [18654.228718] iwlwifi :00:14.3: 0x6F9F215C | umac minor [18654.228723] iwlwifi :00:14.3: 0x029002A9 | frame pointer [18654.228728] iwlwifi :00:14.3: 0xC088627C | stack pointer [18654.228733] iwlwifi :00:14.3: 0x00660118 | last host cmd [18654.228737] iwlwifi :00:14.3: 0x | isr status reg [18654.228758] iwlwifi :00:14.3: Fseq Registers: [18654.228769] iwlwifi :00:14.3: 0xA7691BFB | FSEQ_ERROR_CODE [18654.228780] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION [18654.228791] iwlwifi :00:14.3: 0x58F7C241 | FSEQ_CNVIO_INIT_VERSION [18654.228802] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION [18654.228813] iwlwifi :00:14.3: 0x2B29C823 | FSEQ_TOP_CONTENT_VERSION [18654.228824] iwlwifi :00:14.3: 0x27FAB991 | FSEQ_ALIVE_TOKEN [18654.228835] iwlwifi :00:14.3: 0xD01B76C3 | FSEQ_CNVI_ID [18654.228846] iwlwifi :00:14.3: 0xC5454E1C | FSEQ_CNVR_ID [18654.228857] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP [18654.228870] iwlwifi :00:14.3:
Bug#981352: "VPN Connections" menu entry moves around and is frustrating to click
Am 30.03.2021 um 14:09 schrieb Enrico Zini: I'm attaching a screencast. It seems to play well at least with vlc. Ok, I see. The main difference is that you use a systray at the top Since this is not a Debian specific / integration issue, but is likely to require a UI redesign, this really needs input from upstream. Can you raise this at https://gitlab.gnome.org/GNOME/network-manager-applet/ please and report back with the issue number. Regards, Michael OpenPGP_signature Description: OpenPGP digital signature
Bug#986144: age: version number not set at build time
Package: age X-Debbugs-Cc: ni...@debian.org, jfle...@arcaik.net Version: 1.0.0~rc1-1 Severity: important Dear Maintainer, The age binary is currently built without version information. # age --version (unknown) This should be fixed by adding arguments like the following to the "go build" invocation. -ldflags "-X main.Version=v1.0.0-rc.1" Flagging as important because version information is a critical part of debugging and reporting issues. Thank you, Filippo
Bug#984614: snort in Bullseye
Hi, would it be possible to resolve this RC-bug and keep snort available in Bullseye? Thorsten
Bug#931477: Re: libhtp: Please replace Priority: extra with Priority: optional
> I will file a ticket to change the override soon. See #985816 [1] [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985816
Bug#986142: buster-pu: package h5py/2.8.0-3
Thank Adam. You're right, buster-backports is precisely what is intended. I was following the procedure at https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable linked from https://www.debian.org/releases/proposed-updates.html . Those pages seem to have a different procedure to the one in https://backports.debian.org/Contribute/. Perhaps https://www.debian.org/releases/proposed-updates.html needs to be updated to be more clear. I'll check and follow the buster-backports procedure at https://backports.debian.org/Contribute/ Drew On 2021-03-30 13:41, Adam D. Barratt wrote: Control: tags -1 + moreinfo On Tue, 2021-03-30 at 13:18 +0200, Drew Parsons wrote: [ Reason ] Bug#984638 has requested a backport of h5py to buster in order to support other packages used on it. Usually I'd expect that wording to mean an upload to buster-backports, rather than p-u, particularly when the difference between the two versions is not small. [✓] *all* changes are documented in the d/changelog [✓] I reviewed all changes and I approve them [o] attach debdiff against the package in testing (debdiff against package in stable is large) Unfortunately, for a stable update, the debdiff against stable is the one that's relevant. The diff against a different version of the package tells us very little about the impact on stable. In this case, the diff against stable is: 234 files changed, 1 insertions(+), 7584 deletions(-) This really feels like a candidate for a backports update, rather than a stable update. https://backports.debian.org/Contribute/ has more information, if you're not familiar with the process. Regards, Adam
Bug#986064: spamassassin: Security update failed tue to error in post-installation script
Hi, the same error here: Running sa-compile (may take a long time) chmod: Beim Setzen der Zugriffsrechte für '/var/lib/spamassassin/compil ed/5.024/3.004002/Mail/SpamAssassin/CompiledRegexps/body_0.pm': Die Ope ration ist nicht erlaubt The prob is that the user debian-spamd can not change the the rights: 112984212444 -r--r--r-- 1 root root 450878 Mär 28 08:22 /var/lib/spamassas sin/compiled/5.024/3.004002/Mail/SpamAssassin/CompiledRegexps/body_0.pm CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype: joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#986142: buster-pu: package h5py/2.8.0-3
Control: tags -1 + moreinfo On Tue, 2021-03-30 at 13:18 +0200, Drew Parsons wrote: > [ Reason ] > > Bug#984638 has requested a backport of h5py to buster in order to > support other packages used on it. Usually I'd expect that wording to mean an upload to buster-backports, rather than p-u, particularly when the difference between the two versions is not small. > [✓] *all* changes are documented in the d/changelog > [✓] I reviewed all changes and I approve them > [o] attach debdiff against the package in testing > (debdiff against package in stable is large) > Unfortunately, for a stable update, the debdiff against stable is the one that's relevant. The diff against a different version of the package tells us very little about the impact on stable. In this case, the diff against stable is: 234 files changed, 1 insertions(+), 7584 deletions(-) This really feels like a candidate for a backports update, rather than a stable update. https://backports.debian.org/Contribute/ has more information, if you're not familiar with the process. Regards, Adam
Bug#986118: unblock: rocksndiamonds/4.2.2.1+dfsg-2
Control: tags -1 confirmed moreinfo On 2021-03-29 21:16:32, Stephen Kitt wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Hi, > > I’d like to upload an updated version of rocksndiamonds for Bullseye; > the only change is an updated German debconf translation. The patch is > attached. Looks good. Please remove the moreinfo tag once the new version is available in unstable. Cheers > > Regards, > > Stephen > > unblock rocksndiamonds/4.2.2.1+dfsg-2 > > -- System Information: > Debian Release: 10.9 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, > 'stable'), (100, 'unstable-debug'), (100, 'testing-debug'), (100, > 'unstable'), (100, 'testing'), (1, 'experimental-debug'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386, arm64 > > Kernel: Linux 4.19.0-12-amd64 (SMP w/8 CPU cores) > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), > LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > diff --git a/debian/changelog b/debian/changelog > index 0e40a74..5afb4af 100644 > --- a/debian/changelog > +++ b/debian/changelog > @@ -1,3 +1,10 @@ > +rocksndiamonds (4.2.2.1+dfsg-2) unstable; urgency=medium > + > + * Updated German debconf template translation, thanks to Helge > +Kreutzmann. Closes: #980877. > + > + -- Stephen Kitt Mon, 29 Mar 2021 21:14:16 +0200 > + > rocksndiamonds (4.2.2.1+dfsg-1) unstable; urgency=medium > >* New upstream release. > diff --git a/debian/po/de.po b/debian/po/de.po > index c99bd2b..5b26cfa 100644 > --- a/debian/po/de.po > +++ b/debian/po/de.po > @@ -4,19 +4,19 @@ > # > # Matthias Julius , 2007. > # Thomas Mueller , 2009. > +# Helge Kreutzmann , 2021. > msgid "" > msgstr "" > -"Project-Id-Version: rocksndiamonds 3.2.2-12\n" > +"Project-Id-Version: rocksndiamonds 4.2.2.0+dfsg-1\n" > "Report-Msgid-Bugs-To: rocksndiamo...@packages.debian.org\n" > "POT-Creation-Date: 2020-12-25 21:14+0100\n" > -"PO-Revision-Date: 2009-09-05 08:48+0200\n" > -"Last-Translator: Thomas Mueller \n" > +"PO-Revision-Date: 2021-01-23 17:38+0100\n" > +"Last-Translator: Helge Kreutzmann \n" > "Language-Team: German \n" > "Language: de\n" > "MIME-Version: 1.0\n" > "Content-Type: text/plain; charset=UTF-8\n" > "Content-Transfer-Encoding: 8bit\n" > -"X-Generator: KBabel 1.11.4\n" > "Plural-Forms: nplurals=2; plural=(n != 1);\n" > > #. Type: boolean > @@ -34,9 +34,8 @@ msgid "" > "automatically downloaded from the Internet and installed locally." > msgstr "" > "Die Datendateien, die von rocksndiamonds benötigt werden, stehen unter " > -"keiner Lizenz, die eine Verteilung in einem Paket erlaubt. Wie auch immer, " > -"diese können automatisch aus dem Internet geladen und lokal installiert " > -"werden." > +"keiner Lizenz, die eine Verteilung in einem Paket erlaubt. Sie können > jedoch " > +"automatisch aus dem Internet heruntergeladen und lokal installiert werden." > > #. Type: boolean > #. Description > @@ -47,6 +46,10 @@ msgid "" > "Legend of Zelda (2.1 MiB), Legend of Zelda II (12 MiB), rnd_jue (18 MiB), " > "Snake Bite (6.3 MiB), Supaplex (7.2 MiB)." > msgstr "" > +"Einige dieser Downloads sind recht groß: BD2K3 (4,5 MiB), BD " > +"Dream (11 MiB), Contributions 1995 - 2006 (6 MiB), Emerald Mine Club (44 " > +"MiB), Legend of Zelda (2,1 MiB), Legend of Zelda II (12 MiB), rnd_jue (18 " > +"MiB), Snake Bite (6,3 MiB), Supaplex (7,2 MiB)." > > #. Type: multiselect > #. Description -- Sebastian Ramacher
Bug#986133: mirror submission for mirrors.layerbridge.com
Package: mirrors Severity: wishlist User: mirr...@packages.debian.org Usertags: mirror-submission Submission-Type: new Site: mirrors.layerbridge.com Type: leaf Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x Archive-http: /debian/ Archive-rsync: debian/ Maintainer: LayerBridge Country: RO Romania Location: Bucharest Sponsor: LayerBridge https://www.layerbridge.com Trace Url: http://mirrors.layerbridge.com/debian/project/trace/ Trace Url: http://mirrors.layerbridge.com/debian/project/trace/ftp-master.debian.org Trace Url: http://mirrors.layerbridge.com/debian/project/trace/mirrors.layerbridge.com
Bug#985088: Info received (snort in Bullseye)
Oops, sorry, wrong bug. Thorsten
Bug#981352: "VPN Connections" menu entry moves around and is frustrating to click
Control: tags -1 + moreinfo Can you attach a screenshot / screencast illustrating the issue? For me, the list of VPN is stable and so is the number of VPNs (IIRC nm-applet trims the list to 5). Regards, Michael signature.asc Description: This is a digitally signed message part
Bug#986142: buster-pu: package h5py/2.8.0-3
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: 984...@bugs.debian.org
[ Reason ]
Bug#984638 has requested a backport of h5py to buster in order to
support other packages used on it.
I've prepared a backport of 2.10.0-9 and am ready to upload if
approved.
Current h5py 2.10 from testing uses python3-mpi4py-dbg, which is not
available in buster. I therefore removed the python3-h5py-dbg package
(i.e. the build for python3-dbg) from the backport.
The backport builds cleanly in a pbuilder buster chroot, including
passing build-time tests.
[ Impact ]
If not approved, the bug requester will be unable to complete the
tasks they wanted to perform on buster.
[ Tests ]
Build-time tests pass. debian/tests is available.
[ Risks ]
Loses python3-h5py-dbg.
Build using the pkg-config hdf5-mpi.pc file set by alternatives had to
be dropped. The build uses the old mechanism of selected
hdf5-openmpi.pc or hdf5-mpich.pc, which should still work. Release
arches use hdf5-openmpi.pc, which is tested.
Dependent packages in buster have not been tested against this backport.
[ Checklist ]
[✓] *all* changes are documented in the d/changelog
[✓] I reviewed all changes and I approve them
[o] attach debdiff against the package in testing
(debdiff against package in stable is large)
[✓] the issue is verified as fixed in unstable
[ Changes ]
* Backport to stable (buster). Closes: #984638.
- Standards-Version: 4.3.0
- revert building python3-h5py-dbg from 2.9.0-7
(python3-mpi4py-dbg is not available on buster)
i.e. drop python3-h5py*-dbg packages,
drop Build-Depends: python3-all-dbg, cython3-dbg
- revert change in 2.10.0-6 using hdf5-mpi.pc as pkg-config file
(not available in libhdf5-mpi-dev 1.10.4+repack-10 for buster)
- revert use of system liblzf-dev from 2.10.0-8
* use wildcard for mathjax version when replacing references
(but only replace references if they are found)
diff -Nru h5py-2.10.0/debian/changelog h5py-2.10.0/debian/changelog
--- h5py-2.10.0/debian/changelog2020-08-17 13:54:50.0 +0200
+++ h5py-2.10.0/debian/changelog2021-03-30 13:01:26.0 +0200
@@ -1,3 +1,20 @@
+h5py (2.10.0-9~bpo1+buster1) stable; urgency=medium
+
+ * Team upload.
+ * Backport to stable (buster). Closes: #984638.
+- Standards-Version: 4.3.0
+- revert building python3-h5py-dbg from 2.9.0-7
+ (python3-mpi4py-dbg is not available on buster)
+ i.e. drop python3-h5py*-dbg packages,
+ drop Build-Depends: python3-all-dbg, cython3-dbg
+- revert change in 2.10.0-6 using hdf5-mpi.pc as pkg-config file
+ (not available in libhdf5-mpi-dev 1.10.4+repack-10 for buster)
+- revert use of system liblzf-dev from 2.10.0-8
+ * use wildcard for mathjax version when replacing references
+(but only replace references if they are found)
+
+ -- Drew Parsons Tue, 30 Mar 2021 13:01:26 +0200
+
h5py (2.10.0-9) unstable; urgency=medium
* Team upload.
diff -Nru h5py-2.10.0/debian/control h5py-2.10.0/debian/control
--- h5py-2.10.0/debian/control 2020-08-17 13:54:50.0 +0200
+++ h5py-2.10.0/debian/control 2021-03-30 13:01:26.0 +0200
@@ -5,28 +5,23 @@
Section: python
Priority: optional
Build-Depends: cython3,
- cython3-dbg,
debhelper-compat (= 12),
dh-python,
dpkg-dev (>= 1.17.14),
libhdf5-dev,
- libhdf5-mpi-dev (>= 1.10.6+repack-1),
+ libhdf5-mpi-dev,
libjs-mathjax,
- liblzf-dev,
mpi-default-dev,
- python3-all-dbg,
python3-all-dev,
python3-mpi4py,
- python3-mpi4py-dbg,
python3-numpy,
- python3-numpy-dbg,
python3-pkgconfig,
python3-pytest,
python3-setuptools,
python3-six,
python3-unittest2,
python3-sphinx
-Standards-Version: 4.5.0
+Standards-Version: 4.3.0
Vcs-Browser: https://salsa.debian.org/science-team/h5py
Vcs-Git: https://salsa.debian.org/science-team/h5py.git
Homepage: https://www.h5py.org/
@@ -115,97 +110,6 @@
This package provides the modules for Python 3, built with support
for MPI (multiprocessor) jobs.
-Package: python3-h5py-dbg
-Section: debug
-Architecture: all
-Depends: python3-h5py-serial-dbg | python3-h5py-mpi-dbg, ${misc:Depends}
-Suggests: python-h5py-doc
-Description: debug extensions for h5py (Python 3)
- HDF5 for Python (h5py) is a general-purpose Python interface to the
- Hierarchical Data Format library, version 5. HDF5 is a versatile, mature
- scientific software library designed for the fast, flexible storage of
- enormous amounts of data.
- .
- From a Python programmer's perspective, HDF5 provides a robust way to
- store data, organized by name in a tree-like
Bug#985088: snort in Bullseye
Hi, would it be possible to resolve this RC-bug and keep snort available in Bullseye? Thorsten
Bug#986016: Update libgweather to 3.36.2
On Sat, 27 Mar 2021 23:15:27 +0100 Amr Ibrahim wrote: > Package: libgweather > > Please update libgweather to 3.36.2. FTR, 3.36.1-2 contains all the patches from 3.36.2 except the translations and the following ones: https://gitlab.gnome.org/GNOME/libgweather/-/commit/f6db5b7021876d1403fb97b7d04a30e5aa9a7570: tests https://gitlab.gnome.org/GNOME/libgweather/-/commit/dba65e9709e1ab200f4c21da92b35988535754ee: some constant calculation issue, I think that will cause some application to no use the OWM provider but fixing that would require to rebuilt the rdeps using that constant https://gitlab.gnome.org/GNOME/libgweather/-/commit/46ce7f9cc674c086404077492fd329a5389cc673: use a per-application user-agent They should maybe be cherry-picked for bullseye, especially the last one
Bug#986141: ITP: snpeff -- genetic variant annotation and effect prediction toolbox
Package: wnpp Severity: wishlist Owner: Debian-med team X-Debbugs-Cc: debian-de...@lists.debian.org, debian-...@lists.debian.org * Package name: snpeff Version : 4.3t Upstream Author : Pablo Cingolani * URL : https://pcingola.github.io/SnpEff/ * License : LGPL-3 Programming Lang: Java Description : genetic variant annotation and effect prediction toolbox SnpEff is a variant annotation and effect prediction tool. It annotates and predicts the effects of variants on genes (such as amino acid changes). The inputs are predicted variants (SNPs, insertions, deletions and MNPs). The input file is usually obtained as a result of a sequencing experiment, and it is usually in variant call format (VCF). SnpEff analyzes the input variants. It annotates the variants and calculates the effects they produce on known genes (e.g. amino acid changes). This software is needed in many workflows in the Debian-med team. It will be maintained inside the team.
Bug#986140: Available on salsa
Package available on salsa: https://salsa.debian.org/python-team/packages/aiohttp-jwt
Bug#986140: ITP: aiohttp-jwt -- Aiohttp middleware and helpers for working with JSON web tokens
Package: wnpp Severity: wishlist Owner: Adam Cecile * Package name: aiohttp-jwt Version : 0.6.1 Upstream Author : Kuchuk Oleh * URL : https://github.com/hzlmn/aiohttp-jwt * License : Expat Programming Lang: Python Description : Aiohttp middleware and helpers for working with JSON web tokens This module inspired by official auth0/express-jwt middleware and express-jwt- permissions extension. I intend to maintain this package withing the Debian Python Module Team.
Bug#986139: offlineimap3 crashes with encoding error
Source: offlineimap3
Version: 0.0~git20210225.1e7ef9e+dfsg-3
Severity: important
Dear Sudip,
My offlineimap3 crashes when trying to retrieve some messages:
...
Last 11 debug messages logged for Copy message from
Riseup-Remote:origin-mail-dir prior to exception:
thread: Register new thread 'Copy message from Riseup-Remote:origin-mail-dir'
(account 'Riseup')
imap: 15:26.95 Copy message from Riseup-Remote:origin-mail-dir [async] UID
('FETCH', '1981', '(BODY.PEEK[])')
imap: 15:26.95 Copy message from Riseup-Remote:origin-mail-dir
state_change_pending.acquire
imap: 15:26.95 Copy message from Riseup-Remote:origin-mail-dir
state_change_pending.release
imap: 15:26.95 Copy message from Riseup-Remote:origin-mail-dir
_request_push(b'EPBL24', UID, {}) = b'EPBL24'
imap: 15:26.95 Copy message from Riseup-Remote:origin-mail-dir data=b'EPBL24
UID FETCH 1981 (BODY.PEEK[])'
imap: 15:26.96 Copy message from Riseup-Remote:origin-mail-dir
UID:b'EPBL24'.ready.wait
imap: 15:27.44 Copy message from Riseup-Remote:origin-mail-dir
_get_untagged_response(FETCH) => [(b'184 (UID 1981 BODY[] {6664}',
b'Return-Path: [(b'184 (UID 1981 BODY[] {6664}',
b'Return-Path:
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on towhee.riseup.net
X-Spam-Level:
X... v2.0
*
'
maildir: Write mail 'origin-mail-dir:1981' with flags set()
2021-03-30 10:15:27 INFO: OfflineIMAP 7.3.0
Licensed under the GNU GPL v2 or any later version (with an OpenSSL exception)
2021-03-30 10:15:27 WARNING: ERROR: Exceptions occurred during the run!
2021-03-30 10:15:27 WARNING: ERROR: Copying message 1981 [acc: Riseup]
'ascii' codec can't encode characters in position 3523-3525: ordinal not in
range(128)
2021-03-30 10:15:27 WARNING:
Traceback:
File "/usr/share/offlineimap3/offlineimap/folder/Base.py", line 807, in
copymessageto
new_uid = dstfolder.savemessage(uid, message, flags, rtime)
File "/usr/share/offlineimap3/offlineimap/folder/Maildir.py", line 380, in
savemessage
tmpname = self.save_to_tmp_file(messagename, msg)
File "/usr/share/offlineimap3/offlineimap/folder/Maildir.py", line 330, in
save_to_tmp_file
fd.write(msg.as_bytes(policy=output_policy))
File "/usr/lib/python3.9/email/message.py", line 178, in as_bytes
g.flatten(self, unixfrom=unixfrom)
File "/usr/lib/python3.9/email/generator.py", line 116, in flatten
self._write(msg)
File "/usr/lib/python3.9/email/generator.py", line 181, in _write
self._dispatch(msg)
File "/usr/lib/python3.9/email/generator.py", line 218, in _dispatch
meth(msg)
File "/usr/lib/python3.9/email/generator.py", line 268, in _handle_multipart
self.write(subparts)
File "/usr/lib/python3.9/email/generator.py", line 410, in write
self._fp.write(s.encode('ascii', 'surrogateescape'))
Tell me if more debug information is needed.
Cheers,
-- S
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500,
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-4-amd64 (SMP w/8 CPU threads)
Locale: LANG=es_CO.UTF-8, LC_CTYPE=es_CO.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-- no debconf information
signature.asc
Description: PGP signature
Bug#986126: ITP: click -- Click package management
Package: wnpp Severity: wishlist Owner: Mike Gabriel X-Debbugs-Cc: debian-de...@lists.debian.org, do...@ubports.com, mar...@ubports.com * Package name: click Version : 0.5.0 Upstream Author : Rodney Dawes * URL : https://gitlab.com/ubports/core/click/ * License : GPL-3, Python License Programming Lang: Vala, Python Description : Click package management Click is a simplified packaging format that installs in a separate part of the file system, suitable for third-party applications. . Click is used by apps specifically targetting the Lomiri Operating Environment. . This package will be maintained under the umbrella of the Debian UBports Packaging Team.
Bug#964603: notepadqq: FTBFS: Error copying /<>/out/release/appdata/extension_tools to /<>/debian/tmp/usr/share/notepadqq/extension_tools: Cannot open /<>/out/re
Control: tags -1 +patch
On Thu, Jul 09, 2020 at 01:26:51PM +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > [...]
> > /usr/lib/qt5/bin/qmake -install qinstall
> > /<>/out/release/appdata/extension_tools
> > /<>/debian/tmp/usr/share/notepadqq/extension_tools
> > Error copying /<>/out/release/appdata/extension_tools to
> > /<>/debian/tmp/usr/share/notepadqq/extension_tools: Cannot
> > open /<>/out/release/appdata/extension_tools for input
> > make[3]: *** [Makefile:2390: install_misc_data] Error 3
This can be fixed by amending the 0001-remove_extension_tools patch to also
remove make_extensionTools from PRE_TARGETDEPS in src/ui/ui.pro.
Updated version of debian/patches/0001-remove_extension_tools is attached.
--
Dmitry Shachnev
Since extension tools are removed from upstream sources, remove the installation from the makefile
--- a/src/extension_tools/Makefile
+++ b/src/extension_tools/Makefile
@@ -5,5 +5,3 @@
.PHONY: all
all:
- mkdir -p "$(DESTDIR)"
- cp -r node_modules install.js pack.js package.json readmanifest.js "$(DESTDIR)"/
--- a/src/ui/ui.pro
+++ b/src/ui/ui.pro
@@ -230,7 +230,7 @@
translationsTarget.commands = ($${LRELEASE} \"$${CURRFILE}\")
QMAKE_EXTRA_TARGETS += editorTarget extensionToolsTarget translationsTarget
-PRE_TARGETDEPS += make_editor make_extensionTools make_translations
+PRE_TARGETDEPS += make_editor make_translations
unix:!macx {
launchTarget.target = make_launch
Bug#986138: unblock: octavia/7.1.0-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package octavia The new version of Octavia in Bullseye uses a script called udp-masquerade.sh that the octavia-agent expects to find in /usr/local/bin. In production, we tried to spawn a load balancer, and it just failed because the script was missing. I therefore patched Octavia to use /usr/bin/octavia-agent-udp-masquerade instead of /usr/local/bin/udp-masquerade.sh, and packaged the missing script in the agent. Attached is the debdiff for this change. The debdiff also includes a slightly modified uwsgi configuration file to improve performances of the octavia-api (though I don't think this is very controvertial). Please unblock octavia/7.1.0-2 to fix the agent. Cheers, Thomas Goirand (zigo)
Bug#986125: ITP: libusermetrics -- library for exporting anonymous metrics about users
Package: wnpp Severity: wishlist Owner: Mike Gabriel X-Debbugs-Cc: debian-de...@lists.debian.org, do...@ubports.com, mar...@ubports.com * Package name: libusermetrics Version : 1.2.0 Upstream Author : Rodney Dawes * URL : https://gitlab.com/ubports/core/libusermetrics/ * License : LGPL-3 Programming Lang: C++ Description : library for exporting anonymous metrics about users Lomiri Operating Environment is a convergent work shell designed for use cases on phone, tablet or desktop devices. . The libusermetrics is a share library that gets used by Lomiri based applications. . This package will be maintained under the umbrella of the Debian UBports Packaging Team.
Bug#986137: ITP: pullseq -- Extract sequence from a fasta or fastq
Package: wnpp Severity: wishlist Owner: Nilesh Patra X-Debbugs-Cc: debian-de...@lists.debian.org, nil...@debian.org * Package name: pullseq Version : 1.0.2 Upstream Author : Brian C. Thomas * URL : https://github.com/bcthomas/pullseq/releases * License : Expat Programming Lang: C Description : Extract sequence from a fasta or fastq This is a utility to extract sequence from a fasta or fastq. Also helps filter sequences by a minimum length or maximum length. Fast, written in C, using kseq.h library. I shall maintain this package
Bug#986136: perl: shasum treats read errors like end of file
Package: perl Version: 5.28.1-6+deb10u1 Severity: normal I noticed his while testing with an filesystem that should give "read error" at a certain point which did not happen but instead gives a hash output. The easiest way to reproduce is shasuming a folder: strace -e trace=read shasum 0 pn libterm-readline-gnu-perl | libterm-readline-perl-perl ii make4.2.1-1.2 pn perl-doc ii perl-modules-5.24 [liblocale-codes-perl]5.24.1-3+deb9u5 -- no debconf information
Bug#986135: libnet-netmask-perl: CVE-2021-29424: mis-parses IP addresses in some situations
Package: libnet-netmask-perl Version: 1.9104-1 Severity: normal Dear Maintainer, https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29424 https://blog.urth.org/2021/03/29/security-issues-in-perl-ip-address-distros/ https://metacpan.org/changes/distribution/Net-Netmask#L11-22 Fix exists upstream, and should be trivially backportable. -- System Information: Debian Release: 10.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-14-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libnet-netmask-perl depends on: ii perl 5.28.1-6+deb10u1 libnet-netmask-perl recommends no packages. libnet-netmask-perl suggests no packages.
Bug#986134: acorn: please reintroduce node-acorn as transitional package
Source: acorn Version: 8.0.5+ds+~cs19.19.27-2 Severity: serious Tags: patch User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + node-buble Hi, during a test with piuparts I noticed node-buble fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails. The upgrade involves switching from the real package node-acorn to the (versioned) virtual package node-acorn, something that is usually difficult for apt and in this case apt fails to find a working upgrade path. Introducing a (real) transitional package node-acorn makes the whole process smooth. >From the attached log (scroll to the bottom...): Starting 2 pkgProblemResolver with broken count: 2 Investigating (0) libnode72:amd64 < none -> 12.21.0~dfsg-1 @un uN Ib > Broken libnode72:amd64 Breaks on libnode64:amd64 < 10.24.0~dfsg-1~deb10u1 @ii mK > Considering libnode64:amd64 -3 as a solution to libnode72:amd64 27 Added libnode64:amd64 to the remove list Fixing libnode72:amd64 via remove of libnode64:amd64 Investigating (0) node-debbundle-acorn:amd64 < none -> 8.0.5+ds+~cs19.19.27-1 @un uN Ib > Broken node-debbundle-acorn:amd64 Breaks on node-acorn:amd64 < 5.5.3+ds3-3 @ii mK > (< 6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-2~) Considering node-acorn:amd64 0 as a solution to node-debbundle-acorn:amd64 -1 Holding Back node-debbundle-acorn:amd64 rather than change node-acorn:amd64 Investigating (1) node-buble:amd64 < 0.19.4-3 -> 0.20.0+~0.19.2-3 @ii umU Ib > Broken node-buble:amd64 Depends on node-acorn:amd64 < 5.5.3+ds3-3 @ii mK > (>= 6.0~) Considering node-debbundle-acorn:amd64 -1 as a solution to node-buble:amd64 0 Holding Back node-buble:amd64 rather than change node-acorn:amd64 Investigating (2) node-magic-string:amd64 < 0.25.2-1 -> 0.25.7-4 @ii umU Ib > Broken node-magic-string:amd64 Breaks on node-buble:amd64 < 0.19.4-3 | 0.20.0+~0.19.2-3 @ii umH > (< 0.19.8-7~) Considering node-buble:amd64 0 as a solution to node-magic-string:amd64 1 Upgrading node-buble:amd64 due to Breaks field in node-magic-string:amd64 Investigating (2) node-buble:amd64 < 0.19.4-3 -> 0.20.0+~0.19.2-3 @ii umU Ib > Broken node-buble:amd64 Depends on node-acorn:amd64 < 5.5.3+ds3-3 @ii mK > (>= 6.0~) Considering node-debbundle-acorn:amd64 -1 as a solution to node-buble:amd64 0 Holding Back node-buble:amd64 rather than change node-acorn:amd64 Investigating (3) node-magic-string:amd64 < 0.25.2-1 -> 0.25.7-4 @ii umU Ib > Broken node-magic-string:amd64 Breaks on node-buble:amd64 < 0.19.4-3 | 0.20.0+~0.19.2-3 @ii umH > (< 0.19.8-7~) Considering node-buble:amd64 0 as a solution to node-magic-string:amd64 1 Upgrading node-buble:amd64 due to Breaks field in node-magic-string:amd64 Investigating (3) node-buble:amd64 < 0.19.4-3 -> 0.20.0+~0.19.2-3 @ii umU Ib > Broken node-buble:amd64 Depends on node-acorn:amd64 < 5.5.3+ds3-3 @ii mK > (>= 6.0~) Considering node-debbundle-acorn:amd64 -1 as a solution to node-buble:amd64 0 Holding Back node-buble:amd64 rather than change node-acorn:amd64 Investigating (4) node-magic-string:amd64 < 0.25.2-1 -> 0.25.7-4 @ii umU Ib > Broken node-magic-string:amd64 Breaks on node-buble:amd64 < 0.19.4-3 | 0.20.0+~0.19.2-3 @ii umH > (< 0.19.8-7~) Considering node-buble:amd64 0 as a solution to node-magic-string:amd64 1 Upgrading node-buble:amd64 due to Breaks field in node-magic-string:amd64 Investigating (4) node-buble:amd64 < 0.19.4-3 -> 0.20.0+~0.19.2-3 @ii umU Ib > Broken node-buble:amd64 Depends on node-acorn:amd64 < 5.5.3+ds3-3 @ii mK > (>= 6.0~) Considering node-debbundle-acorn:amd64 -1 as a solution to node-buble:amd64 0 Holding Back node-buble:amd64 rather than change node-acorn:amd64 Investigating (5) node-magic-string:amd64 < 0.25.2-1 -> 0.25.7-4 @ii umU Ib > Broken node-magic-string:amd64 Breaks on node-buble:amd64 < 0.19.4-3 | 0.20.0+~0.19.2-3 @ii umH > (< 0.19.8-7~) Considering node-buble:amd64 0 as a solution to node-magic-string:amd64 1 Upgrading node-buble:amd64 due to Breaks field in node-magic-string:amd64 Investigating (5) node-buble:amd64 < 0.19.4-3 -> 0.20.0+~0.19.2-3 @ii umU Ib > Broken node-buble:amd64 Depends on node-acorn:amd64 < 5.5.3+ds3-3 @ii mK > (>= 6.0~) Considering node-debbundle-acorn:amd64 -1 as a solution to node-buble:amd64 0 Holding Back node-buble:amd64 rather than change node-acorn:amd64 Investigating (6) node-magic-string:amd64 < 0.25.2-1 -> 0.25.7-4 @ii umU Ib > Broken node-magic-string:amd64 Breaks on node-buble:amd64 < 0.19.4-3 | 0.20.0+~0.19.2-3 @ii umH > (< 0.19.8-7~) Considering node-buble:amd64 0 as a solution to node-magic-string:amd64 1 Upgrading node-buble:amd64 due to Breaks field in node-magic-string:amd64 Investigating (6) node-buble:amd64 < 0.19.4-3 -> 0.20.0+~0.19.2-3 @ii umU Ib > Broken node-buble:amd64 Depends on node-acorn:amd64 < 5.5.3+ds3-3 @ii mK
Bug#984918: AskDNS problem with multi-valued resource records
Hi Noah, > Thanks for this report. I agree it would be good to fix for bullseye. > Since bullseye currently contains a 3.4.5 release candidate, and there'ѕ > been some rumbling upstream about finally pushing out a release, my hope > is to convince the SRMs to allow updating to 3.4.5 in a bullseye point > release when it's available. The changes should be small and targeted > enough to make this reasonable, and it'll be a lot easier to support a > proper release over bullseye's lifetime. Sounds great, 3.4.5 has been released a week ago. Bernhard
Bug#985590: (pre-approval) unblock: zfs-linux/2.0.3-2
Hi, On Tue, Mar 30, 2021 at 4:17 AM Paul Gevers wrote: > [...] > > > 3. Add new debconf questions, for the cron jobs of pool scrub and trim, with > >translation updates from debian-i18n people. > > But here, I think there's a serious issue. You seem to be querying the > debconf database during cron jobs, but debconf is not a registry. This > is not acceptable. Lintian warns about this too: > https://lintian.debian.org/tags/debconf-is-not-a-registry.html > > I suggest you prepare an upload with 1 and 2. I don't feel comfortable > with 3, even if you fix the debconf-is-not-a-registry issue. > I have reverted 3, and attached is the new debdiff. Thanks for the comments! Cheers, Aron zfs-linux_2.0.3-2.debdiff.gz Description: application/gzip
Bug#986092: RFS: psftools/1.1.1-1 [ITP] -- PSF font tools
Hi There's a library included -- with headers and stuff, that should go into separate packages. True, fixed. unimaps/mappings.tar.gz smuggles a lot of files under different copyrights. Removed and noted in d/copyright. Meow!
