Bug#986780: marked as done (unblock: email-reminder/0.8.1-3)
Your message dated Mon, 12 Apr 2021 07:04:53 + with message-id and subject line unblock email-reminder has caused the Debian Bug report #986780, regarding unblock: email-reminder/0.8.1-3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 986780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986780 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package email-reminder [ Reason ] The .desktop file is not installed (bug #986744). [ Impact ] A non-technical user likely won't be able to start the application at all. [ Tests ] Manual test: open gnome-shell and ensure it's displayed in the list of applications. [ Risks ] Minimal: one-line change which only affects the .desktop file. [ 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 email-reminder/0.8.1-3 diff -Nru email-reminder-0.8.1/debian/changelog email-reminder-0.8.1/debian/changelog --- email-reminder-0.8.1/debian/changelog 2021-01-18 22:01:41.0 -0800 +++ email-reminder-0.8.1/debian/changelog 2021-04-10 19:26:37.0 -0700 @@ -1,3 +1,9 @@ +email-reminder (0.8.1-3) unstable; urgency=medium + + * Add missing .desktop file (closes: #986744). + + -- Francois Marier Sat, 10 Apr 2021 19:26:37 -0700 + email-reminder (0.8.1-2) unstable; urgency=medium * Bump Standards-Version up to 4.5.1. diff -Nru email-reminder-0.8.1/debian/install email-reminder-0.8.1/debian/install --- email-reminder-0.8.1/debian/install 1969-12-31 16:00:00.0 -0800 +++ email-reminder-0.8.1/debian/install 2021-04-10 19:26:37.0 -0700 @@ -0,0 +1 @@ +email-reminder.desktop usr/share/applications --- End Message --- --- Begin Message --- Unblocked.--- End Message ---
Bug#986786: unblock: breeze/4:5.20.5-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: debian-...@lists.debian.org
Please unblock package breeze
This release cherry-picks a fix for KDE bug 431921 [1]
where splitter handles could interfer with each other, creating
black boxes and stop reacting to interaction.
The commit has been pushed by upstream into
- KDE Plasma 5.18 LTS [2]
- KDE Plasma 5.21 (for the next release) [3]
The current Debian release will apply the patch to the version
in Debian, 5.20.5 which is affected in the same way.
[ Reason ]
Fix for upstream bug that has been fixed in LTS versions and current
version.
[ Impact ]
GUI glitches and interaction problems.
[ Tests ]
Install and run tests, tried to reproduce it.
[ Risks ]
The only change is that three lines of code have been moved down a few
lines to make sure that the splitter data is correctly setup.
[ 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
[1] https://bugs.kde.org/show_bug.cgi?id=431921
[2]
https://invent.kde.org/plasma/breeze/commit/cc613558bae7c809e36951da89db3c7cc1a5a58e
[3]
https://invent.kde.org/plasma/breeze/commit/6c3a46e0f1abb697fb0900f21196cafcbd8ee37c
unblock breeze/4:5.20.5-3
Thanks
Norbert
--
PREINING Norbert https://www.preining.info
Fujitsu + IFMGA Guide + TU Wien + TeX Live + Debian Dev
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
diff -Nru breeze-5.20.5/debian/changelog breeze-5.20.5/debian/changelog
--- breeze-5.20.5/debian/changelog 2021-01-13 07:39:50.0 +0900
+++ breeze-5.20.5/debian/changelog 2021-04-12 09:50:56.0 +0900
@@ -1,3 +1,10 @@
+breeze (4:5.20.5-3) unstable; urgency=medium
+
+ [ Norbert Preining ]
+ * Cherry-pick upstream fix for KDE bug 431921.
+
+ -- Norbert Preining Mon, 12 Apr 2021 09:50:56 +0900
+
breeze (4:5.20.5-2) unstable; urgency=medium
* Fix disappearing wallpaper (from irc, patch provided by Rik Mills).
diff -Nru breeze-5.20.5/debian/patches/series
breeze-5.20.5/debian/patches/series
--- breeze-5.20.5/debian/patches/series 2021-01-12 18:34:00.0 +0900
+++ breeze-5.20.5/debian/patches/series 2021-04-12 09:49:08.0 +0900
@@ -1 +1,2 @@
fix-wallpaper-loss-on-breeze-change
+upstream-d201a1f1-fix-splitterproxy-not-clearing.patch
diff -Nru
breeze-5.20.5/debian/patches/upstream-d201a1f1-fix-splitterproxy-not-clearing.patch
breeze-5.20.5/debian/patches/upstream-d201a1f1-fix-splitterproxy-not-clearing.patch
---
breeze-5.20.5/debian/patches/upstream-d201a1f1-fix-splitterproxy-not-clearing.patch
1970-01-01 09:00:00.0 +0900
+++
breeze-5.20.5/debian/patches/upstream-d201a1f1-fix-splitterproxy-not-clearing.patch
2021-04-12 09:47:08.0 +0900
@@ -0,0 +1,57 @@
+From d201a1f187243da677f8fa6e94325c41c3b9007c Mon Sep 17 00:00:00 2001
+From: Fabian Vogt
+Date: Fri, 9 Apr 2021 11:17:28 +0200
+Subject: [PATCH] Fix SplitterProxy not clearing when above another
+ QSplitterHandle
+
+When two SplitterHandles are next to each other, like at the intersection of a
+horizontal and vertical splitter (|-), then it's possible that hiding the proxy
+of one of those handles causes the other handle to gain focus immediately,
+which activates the SplitterProxy again. Before this patch, it would then
+continue clearing after reenabling itself, leading to an inconsistent state.
+
+BUG: 431921
+---
+ kstyle/breezesplitterproxy.cpp | 12 ++--
+ 1 file changed, 6 insertions(+), 6 deletions(-)
+
+diff --git a/kstyle/breezesplitterproxy.cpp b/kstyle/breezesplitterproxy.cpp
+index 19adbcab..0cf5685f 100644
+--- a/kstyle/breezesplitterproxy.cpp
b/kstyle/breezesplitterproxy.cpp
+@@ -338,11 +338,6 @@ namespace Breeze
+ // release mouse
+ if( mouseGrabber() == this ) releaseMouse();
+
+-// hide
+-parentWidget()->setUpdatesEnabled(false);
+-hide();
+-parentWidget()->setUpdatesEnabled(true);
+-
+ // send hover event
+ if( _splitter )
+ {
+@@ -351,7 +346,6 @@ namespace Breeze
+ _splitter.data()->mapFromGlobal(QCursor::pos()), _hook);
+ QCoreApplication::sendEvent( _splitter.data(), &hoverEvent );
+ _splitter.clear();
+-
+ }
+
+ // kill timer if any
+@@ -361,6 +355,12 @@ namespace Breeze
+ _timerId = 0;
+ }
+
++// hide
++parentWidget()->setUpdatesEnabled(false);
++// Note: This sends a synthetic mouse event to the widget below (to
get focus), which might be
++// another SplitterHandle, therefore enabling this SplitterProxy
again!
++hide();
++parentWidget()->setUpdatesEnabled(true);
+ }
+
+ }
+--
+GitLab
+
Bug#986760: marked as done (unblock: seahorse/3.38.0.1-2)
Your message dated Mon, 12 Apr 2021 08:25:56 +
with message-id
and subject line unblock seahorse
has caused the Debian Bug report #986760,
regarding unblock: seahorse/3.38.0.1-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
986760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package seahorse.
[ Reason ]
Fix key import dialog to wait for the key to be imported, rather than
cancelling the action before it starts.
(#931558, Severity: important in my opinion)
[ Impact ]
If not fixed, GNOME users cannot import GPG keys via a GUI and must use
the command-line.
[ Tests ]
Manual test:
- Obtained a public key that was not in my keyring and attempted to
import it with 3.38.0.1-1, confirmed failure (dialog closes immediately,
new key not present when asking the gpg CLI).
- Upgraded to 3.38.0.1-2, re-imported the key, confirmed success (a
spinner appears in the Import button for a while before the dialog
closes, new key is visible to the gpg CLI afterwards).
[ Risks ]
Minimal risk. It's a targeted fix to a UI element that previously
didn't work at all, so even a partial or imperfect solution would be
an improvement.
[ 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 ]
If this cannot migrate in time for Debian 11.0, then I think a stable
update in 11.1 would be appropriate.
unblock seahorse/3.38.0.1-2
diffstat for seahorse-3.38.0.1 seahorse-3.38.0.1
changelog|9
gbp.conf |2 -
patches/ImportDialog-Fix-import-dialog.patch | 29 +++
patches/series |2 -
4 files changed, 40 insertions(+), 2 deletions(-)
diff -Nru seahorse-3.38.0.1/debian/changelog seahorse-3.38.0.1/debian/changelog
--- seahorse-3.38.0.1/debian/changelog 2020-12-12 08:56:34.0 +
+++ seahorse-3.38.0.1/debian/changelog 2021-04-11 17:28:09.0 +0100
@@ -1,3 +1,12 @@
+seahorse (3.38.0.1-2) unstable; urgency=medium
+
+ * Team upload
+ * d/p/ImportDialog-Fix-import-dialog.patch:
+Apply patch from upstream to fix GPG key import (Closes: #931558)
+ * d/gbp.conf: Switch branch to debian/bullseye
+
+ -- Simon McVittie Sun, 11 Apr 2021 17:28:09 +0100
+
seahorse (3.38.0.1-1) unstable; urgency=medium
* New upstream release
diff -Nru seahorse-3.38.0.1/debian/gbp.conf seahorse-3.38.0.1/debian/gbp.conf
--- seahorse-3.38.0.1/debian/gbp.conf 2020-12-12 08:56:34.0 +
+++ seahorse-3.38.0.1/debian/gbp.conf 2021-04-11 17:28:09.0 +0100
@@ -1,6 +1,6 @@
[DEFAULT]
pristine-tar = True
-debian-branch = debian/master
+debian-branch = debian/bullseye
upstream-branch = upstream/latest
[buildpackage]
diff -Nru seahorse-3.38.0.1/debian/patches/ImportDialog-Fix-import-dialog.patch seahorse-3.38.0.1/debian/patches/ImportDialog-Fix-import-dialog.patch
--- seahorse-3.38.0.1/debian/patches/ImportDialog-Fix-import-dialog.patch 1970-01-01 01:00:00.0 +0100
+++ seahorse-3.38.0.1/debian/patches/ImportDialog-Fix-import-dialog.patch 2021-04-11 17:28:09.0 +0100
@@ -0,0 +1,29 @@
+From: Jeremias Ortega
+Date: Mon, 9 Nov 2020 22:39:01 -0600
+Subject: ImportDialog: Fix import dialog
+
+The import dialog fails to import files without showing any warning.
+The dialog closes before it finishes the import process and cancels it.
+
+This is solved by making the import button not return a response directly.
+
+Bug: https://gitlab.gnome.org/GNOME/seahorse/-/issues/236
+Bug-Debian: https://bugs.debian.org/931558
+Origin: upstream, 40~alpha, commit:6cc0fe7381a4c9536123bf877b3e055774b2f0a9
+---
+ src/import-dialog.vala | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/import-dialog.vala b/src/import-dialog.vala
+index 983b7e4..650aaa2 100644
+--- a/src/import-dialog.vala
b/src/import-dialog.vala
+@@ -41,7 +41,7 @@ public class Seahorse.ImportDialog : Gtk.Dialog {
+ this.import.get_style_context().add_class("suggested-action");
+ this.import.importing.connect(() => this.viewer.clear_error());
+ this.import.imported.connect(on_import_button_imported);
+-add_action_widget(this.import, Gtk.ResponseType.OK);
++((Gtk.HeaderBar) get_header_bar()).pack_end(this.import);
+
+
Bug#986797: unblock: sauerbraten/0.0.20201227-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: a...@debian.org Dear release team, [ Reason ] Please unblock the sauerbraten content package for the cube2 engine in testing. The current version of sauerbraten in testing is not compatible with the cube2 engine version in testing. The sauerbraten package contains only images, sound files and configuration files. There are no code changes. [ Impact ] sauerbraten in testing would be broken. The only alternative is to fix the outdated configuration files, so that sauerbraten works out-of-the-box again. However some images and sounds may also be required to restore the gaming experience. Since there are no code changes and sauerbraten is a mere content package, there is no risk of breaking the game or other software. [ Tests ] There are no code changes. I have tested the game and confirm that it works for me. [ Risks ] sauerbraten is a leaf package and a game. There are no risks for breaking unrelated software packages. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [ ] attach debdiff against the package in testing I have not attached a debdiff because there were no code changes. unblock sauerbraten/0.0.20201227-1
Bug#986816: unblock: binoculars/0.0.5-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package binoculars It solves 3 important bugs, the later one is very important since it let the package completly unusable without the proposed fixes. 923859, 924024 , 986785 Since I am also the upstream of the software, I can affirm that it is better to have this version in Debian than the current 0.0.4 version. the user of our facilities expect to have a working version of binoculars available, and the 0.0.4 is not. there is very little risk to accept the 0.0.5 version, which was tested in our facility on buster and bullseye ewith real data's this is a leaf package so very few issue are expected due to this new upstream version. thanks for considering unblock binoculars/0.0.5-1 -- 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/24 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#986824: unblock: nvidia-graphics-drivers-legacy-390xx/390.141-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package nvidia-graphics-drivers-legacy-390xx
Let's synchronize the packaging with src:nvidia-graphics-drivers to ease
future stable updates.
These changes are already in src:nvidia-graphics-drivers in testing.
The missing libnvidia-ml.so symlink was spotted by enabling the nvml
plugin in hwloc-contrib and needs to be fixed in all driver packages.
Andreas
unblock nvidia-graphics-drivers-legacy-390xx/390.141-3
diff -Nru nvidia-graphics-drivers-legacy-390xx-390.141/debian/changelog
nvidia-graphics-drivers-legacy-390xx-390.141/debian/changelog
--- nvidia-graphics-drivers-legacy-390xx-390.141/debian/changelog
2021-01-12 02:08:48.0 +0100
+++ nvidia-graphics-drivers-legacy-390xx-390.141/debian/changelog
2021-03-13 22:39:29.0 +0100
@@ -1,3 +1,16 @@
+nvidia-graphics-drivers-legacy-390xx (390.141-3) unstable; urgency=medium
+
+ * nvidia-legacy-390xx-alternative: Add libnvidia-ml.so slave alternative if
+libnvidia-ml-dev is installed (460.56-2). (Closes: #984881)
+
+ -- Andreas Beckmann Sat, 13 Mar 2021 22:39:29 +0100
+
+nvidia-graphics-drivers-legacy-390xx (390.141-2~deb10u1) buster; urgency=medium
+
+ * Rebuild for buster.
+
+ -- Andreas Beckmann Sat, 23 Jan 2021 18:04:20 +0100
+
nvidia-graphics-drivers-legacy-390xx (390.141-2) unstable; urgency=medium
* Really re-enable building the nvidia-uvm module.
@@ -15,11 +28,12 @@
- Fixed a driver installation failure on Linux kernel 5.8 release
candidates, where the NVIDIA kernel module failed to build with error
"too many arguments to function '__vmalloc'".
+* Improved compatibility with recent Linux kernels.
[ Andreas Beckmann ]
* Re-enable building the nvidia-uvm module.
* Refresh patches.
- * Update symbols files.
+ * Update glvnd symbols files.
* Update lintian overrides.
-- Andreas Beckmann Sun, 10 Jan 2021 03:31:58 +0100
@@ -73,15 +87,6 @@
* Backport nv_vmalloc changes from 450.57
and work around mmap_{sem=>lock} rename
to fix kernel module build for Linux 5.8. (Partly addresses #969085)
- * Note: The nvidia-uvm kernel module will fail to build for Linux 5.8 due to
-licence incompatibility unless cfa6705d89b6562f79c40c249f8d94073c4276e4
-"radix-tree: Use local_lock for protection" (which effectively made
-radix_tree_preloads GPL-only) gets reverted in Linux 5.8 or NVIDIA
-switches the nvidia-uvm module license to "Dual MIT/GPL" as in 415.18.
- * Note: Building the nvidia-uvm module can be temporarily disabled by
-a) commenting the last paragraph in dkms.conf and
-b) building with NV_EXCLUDE_KERNEL_MODULES=nvidia-uvm set in the
- environment.
* Update lintian overrides.
[ Vincent Cheng ]
diff -Nru
nvidia-graphics-drivers-legacy-390xx-390.141/debian/libgl1-glvnd-nvidia-glx.symbols
nvidia-graphics-drivers-legacy-390xx-390.141/debian/libgl1-glvnd-nvidia-glx.symbols
---
nvidia-graphics-drivers-legacy-390xx-390.141/debian/libgl1-glvnd-nvidia-glx.symbols
2021-01-12 02:08:48.0 +0100
+++
nvidia-graphics-drivers-legacy-390xx-390.141/debian/libgl1-glvnd-nvidia-glx.symbols
2021-03-13 22:39:29.0 +0100
@@ -7,7 +7,7 @@
SplitString@Base 375
UnionExtensionStrings@Base 375.20
#MISSING: 384.111# __glXWrapperInit@Base 361
-#MISSING: 390.141# entry_generate_default_code@Base 361
+ (arch=ppc64el)entry_generate_default_code@Base 361
entry_get_patch_address@Base 390.141
#MISSING: 390.141# entry_get_patch_addresses@Base 361
entry_get_public@Base 361
diff -Nru
nvidia-graphics-drivers-legacy-390xx-390.141/debian/libgles1-glvnd-nvidia.symbols
nvidia-graphics-drivers-legacy-390xx-390.141/debian/libgles1-glvnd-nvidia.symbols
---
nvidia-graphics-drivers-legacy-390xx-390.141/debian/libgles1-glvnd-nvidia.symbols
2021-01-12 02:08:48.0 +0100
+++
nvidia-graphics-drivers-legacy-390xx-390.141/debian/libgles1-glvnd-nvidia.symbols
2021-03-13 22:39:29.0 +0100
@@ -7,7 +7,7 @@
#MISSING: 361# NvGlEsInit@Base 331
SplitString@Base 390.59
UnionExtensionStrings@Base 390.59
-#MISSING: 390.141# entry_generate_default_code@Base 390.59
+ (arch=ppc64el)entry_generate_default_code@Base 390.59
entry_get_patch_address@Base 390.141
#MISSING: 390.141# entry_get_patch_addresses@Base 390.59
entry_get_public@Base 390.59
diff -Nru
nvidia-graphics-drivers-legacy-390xx-390.141/debian/libgles2-glvnd-nvidia.symbols
nvidia-graphics-drivers-legacy-390xx-390.141/debian/libgles2-glvnd-nvidia.symbols
---
nvidia-graphics-drivers-legacy-390xx-390.141/debian/libgles2-glvnd-nvidia.symbols
2021-01-12 02:08:48.0 +0100
+++
nvidia-graphics-drivers-legacy-390xx-390.141/debian/libgles2-glvnd-nvidia.symbols
2021-03-13 22:39:29.0 +0100
@@ -8,7 +8,7 @@
#MISSING: 361# NvGlEs2Init@Base 331
SplitString@Base 390.59
UnionExtensionStrings@Base 390.59
-#MISSING: 390.141# entry_generat
Bug#986825: unblock: nvidia-graphics-drivers-tesla-418/418.181.07-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package nvidia-graphics-drivers-tesla-418
Let's synchronize the packaging with src:nvidia-graphics-drivers to ease
future stable updates.
These changes are already in src:nvidia-graphics-drivers in testing.
I've waited with the corresponding unblocks in case we would get another
new upstream release (with CVE fixes).
The missing libnvidia-ml.so symlink was spotted by enabling the nvml
plugin in hwloc-contrib and needs to be fixed in all driver packages.
The dkms changes are making my life easier and were in
src:nvidia-graphics-drivers early enough to migrate on their own.
Andreas
unblock nvidia-graphics-drivers-tesla-418/418.181.07-2
diff -Nru nvidia-graphics-drivers-tesla-418-418.181.07/debian/changelog
nvidia-graphics-drivers-tesla-418-418.181.07/debian/changelog
--- nvidia-graphics-drivers-tesla-418-418.181.07/debian/changelog
2021-01-22 14:01:39.0 +0100
+++ nvidia-graphics-drivers-tesla-418-418.181.07/debian/changelog
2021-03-12 20:11:00.0 +0100
@@ -1,3 +1,12 @@
+nvidia-graphics-drivers-tesla-418 (418.181.07-2) unstable; urgency=medium
+
+ * Switch to dh-sequence-dkms (460.56-1).
+ * Simplify dh_dkms usage (460.56-1).
+ * nvidia-tesla-418-alternative: Add libnvidia-ml.so slave alternative if
+libnvidia-ml-dev is installed (460.56-2). (Closes: #984881)
+
+ -- Andreas Beckmann Fri, 12 Mar 2021 20:11:00 +0100
+
nvidia-graphics-drivers-tesla-418 (418.181.07-1) unstable; urgency=medium
* New upstream Tesla release 418.181.07 (2021-01-19).
@@ -10,6 +19,33 @@
-- Andreas Beckmann Fri, 22 Jan 2021 14:01:39 +0100
+nvidia-graphics-drivers (418.181.07-1) buster; urgency=medium
+
+ * New upstream Tesla release 418.181.07 (2021-01-19).
+* Fixed CVE-2021-1056. (Closes: #979670)
+ https://nvidia.custhelp.com/app/answers/detail/a_id/5142
+* Improved compatibility with recent Linux kernels.
+
+ [ Andreas Beckmann ]
+ * Refresh patches.
+ * Allow alternative libnvidia-{tesla,legacy}-*-cfg1 packages to substitute
+libnvidia-cfg1 in third-party packages (450.57-2).
+- Add Provides: libnvidia-cfg.so.1 (= ${nvidia:Version}).
+- Generate alternative versioned dependency on libnvidia-cfg.so.1 through
+ the symbols file.
+ * Test that the patches can be applied to the module source (450.66-1).
+ * nvidia-kernel-dkms: Ship with unapplied patches and apply the patches
+while building kernel modules (450.66-1).
+ * Simplify generating the -source and -dkms packages (450.66-1).
+ * Bump watch file version to 4.
+ * Bump Standards-Version to 4.5.1. No changes needed.
+ * Upload to buster.
+
+ [ Vincent Cheng ]
+ * Remove myself from Uploaders.
+
+ -- Andreas Beckmann Sat, 23 Jan 2021 19:12:36 +0100
+
nvidia-graphics-drivers-tesla-418 (418.165.02-2) unstable; urgency=medium
* Bump watch file version to 4.
@@ -242,8 +278,8 @@
* Backport fixes for Linux 5.2/5.3 from 418.88.
* debian/gen-control.pl: Support substitutions in the Architecture field and
skip packages with empty or commented Architecture field (430.50-2).
- * Prepare infrastructure for packaging Tesla driver releases (available for
-amd64 (including some i386 libs) and ppc64el) (430.50-2).
+ * Prepare infrastructure for packaging Tesla 418 driver releases (available
+for amd64 (including some i386 libs) and ppc64el) (430.50-2).
* Fork as new source package, rename everything to include '-tesla'.
(Closes: #942149)
* Do not build 'unversioned' packages from this source.
diff -Nru nvidia-graphics-drivers-tesla-418-418.181.07/debian/control
nvidia-graphics-drivers-tesla-418-418.181.07/debian/control
--- nvidia-graphics-drivers-tesla-418-418.181.07/debian/control 2021-01-22
14:01:39.0 +0100
+++ nvidia-graphics-drivers-tesla-418-418.181.07/debian/control 2021-03-12
20:11:00.0 +0100
@@ -11,9 +11,9 @@
Vcs-Git: https://salsa.debian.org/nvidia-team/nvidia-graphics-drivers.git -b
tesla-418/master
Build-Depends:
debhelper-compat (= 13),
+ dh-sequence-dkms,
dh-exec,
xz-utils,
- dkms,
libvulkan1 (>= 1.0.42),
libxext6,
quilt,
diff -Nru nvidia-graphics-drivers-tesla-418-418.181.07/debian/control.in
nvidia-graphics-drivers-tesla-418-418.181.07/debian/control.in
--- nvidia-graphics-drivers-tesla-418-418.181.07/debian/control.in
2021-01-22 14:01:39.0 +0100
+++ nvidia-graphics-drivers-tesla-418-418.181.07/debian/control.in
2021-03-12 20:11:00.0 +0100
@@ -9,9 +9,9 @@
Vcs-Git: https://salsa.debian.org/nvidia-team/nvidia-graphics-drivers.git -b
tesla-418/master
Build-Depends:
debhelper-compat (= 13),
+ dh-sequence-dkms,
dh-exec,
xz-utils,
- dkms,
libvulkan1 (>= 1.0.42),
libxext6,
quilt,
diff -Nru nvidia-graphics-drivers-tesla-418-418.181.07/debian/control.md5sum
nvidia-graphics-drivers-tesla-418-418.181.07/debian/control.md5sum
--- nvidia-graphics-drive
Bug#986826: unblock: nvidia-graphics-drivers-tesla-450/450.102.04-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package nvidia-graphics-drivers-tesla-450 This is essentially the same diff as for nvidia-graphics-drivers-tesla-418. Let's synchronize the packaging with src:nvidia-graphics-drivers to ease future stable updates. These changes are already in src:nvidia-graphics-drivers in testing. I've waited with the corresponding unblocks in case we would get another new upstream release (with CVE fixes). The missing libnvidia-ml.so symlink was spotted by enabling the nvml plugin in hwloc-contrib and needs to be fixed in all driver packages. The dkms changes are making my life easier and were in src:nvidia-graphics-drivers early enough to migrate on their own. Andreas unblock nvidia-graphics-drivers-tesla-450/450.102.04-2 diff -Nru nvidia-graphics-drivers-tesla-450-450.102.04/debian/changelog nvidia-graphics-drivers-tesla-450-450.102.04/debian/changelog --- nvidia-graphics-drivers-tesla-450-450.102.04/debian/changelog 2021-01-25 18:21:19.0 +0100 +++ nvidia-graphics-drivers-tesla-450-450.102.04/debian/changelog 2021-03-13 18:43:15.0 +0100 @@ -1,3 +1,12 @@ +nvidia-graphics-drivers-tesla-450 (450.102.04-2) unstable; urgency=medium + + * Switch to dh-sequence-dkms (460.56-1). + * Simplify dh_dkms usage (460.56-1). + * nvidia-tesla-450-alternative: Add libnvidia-ml.so slave alternative if +libnvidia-ml-dev is installed (460.56-2). (Closes: #984881) + + -- Andreas Beckmann Sat, 13 Mar 2021 18:43:15 +0100 + nvidia-graphics-drivers-tesla-450 (450.102.04-1) unstable; urgency=medium * New upstream long lived branch release 450.102.04 (2021-01-07). @@ -271,6 +280,15 @@ -- Andreas Beckmann Wed, 01 Jul 2020 00:02:18 +0200 +nvidia-graphics-drivers-tesla-440 (440.118.02-4) unstable; urgency=medium + + * Switch to dh-sequence-dkms (460.56-1). + * Simplify dh_dkms usage (460.56-1). + * nvidia-tesla-440-alternative: Add libnvidia-ml.so slave alternative if +libnvidia-ml-dev is installed (460.56-2). (Closes: #984881) + + -- Andreas Beckmann Fri, 12 Mar 2021 21:03:13 +0100 + nvidia-graphics-drivers-tesla-440 (440.118.02-3) unstable; urgency=medium * Metadata updates. @@ -798,6 +816,15 @@ -- Andreas Beckmann Sat, 25 May 2019 13:49:09 +0200 +nvidia-graphics-drivers-tesla-418 (418.181.07-2) unstable; urgency=medium + + * Switch to dh-sequence-dkms (460.56-1). + * Simplify dh_dkms usage (460.56-1). + * nvidia-tesla-418-alternative: Add libnvidia-ml.so slave alternative if +libnvidia-ml-dev is installed (460.56-2). (Closes: #984881) + + -- Andreas Beckmann Fri, 12 Mar 2021 20:11:00 +0100 + nvidia-graphics-drivers-tesla-418 (418.181.07-1) unstable; urgency=medium * New upstream Tesla release 418.181.07 (2021-01-19). diff -Nru nvidia-graphics-drivers-tesla-450-450.102.04/debian/control nvidia-graphics-drivers-tesla-450-450.102.04/debian/control --- nvidia-graphics-drivers-tesla-450-450.102.04/debian/control 2021-01-25 18:21:19.0 +0100 +++ nvidia-graphics-drivers-tesla-450-450.102.04/debian/control 2021-03-13 18:43:15.0 +0100 @@ -11,9 +11,9 @@ Vcs-Git: https://salsa.debian.org/nvidia-team/nvidia-graphics-drivers.git -b tesla-450/master Build-Depends: debhelper-compat (= 13), + dh-sequence-dkms, dh-exec, xz-utils, - dkms, libvulkan1 (>= 1.0.42), libxext6, quilt, diff -Nru nvidia-graphics-drivers-tesla-450-450.102.04/debian/control.in nvidia-graphics-drivers-tesla-450-450.102.04/debian/control.in --- nvidia-graphics-drivers-tesla-450-450.102.04/debian/control.in 2021-01-25 18:21:19.0 +0100 +++ nvidia-graphics-drivers-tesla-450-450.102.04/debian/control.in 2021-03-13 18:43:15.0 +0100 @@ -9,9 +9,9 @@ Vcs-Git: https://salsa.debian.org/nvidia-team/nvidia-graphics-drivers.git -b tesla-450/master Build-Depends: debhelper-compat (= 13), + dh-sequence-dkms, dh-exec, xz-utils, - dkms, libvulkan1 (>= 1.0.42), libxext6, quilt, diff -Nru nvidia-graphics-drivers-tesla-450-450.102.04/debian/control.md5sum nvidia-graphics-drivers-tesla-450-450.102.04/debian/control.md5sum --- nvidia-graphics-drivers-tesla-450-450.102.04/debian/control.md5sum 2021-01-25 18:21:19.0 +0100 +++ nvidia-graphics-drivers-tesla-450-450.102.04/debian/control.md5sum 2021-03-13 18:43:15.0 +0100 @@ -1,5 +1,5 @@ -f0827841c95c5c08ce914ae43f8e5cef debian/control -3067d62ff95323b58086a48b4d5d8871 debian/control.in +f7eb3755f20b606b6c02febfa92cbb6d debian/control +807ae812aa88a6bd3515fc4e4ea95ce3 debian/control.in db12f898b07cdaf431ad34bd68a1662e debian/gen-control.pl -58159b3fe71cf113c18d2948937a3a3c debian/rules +94fc2cf02a896617e959f54edb431e36 debian/rules beb8fea9a88b05fd523f5c5d278b2267 debian/rules.defs diff -Nru nvidia-graphics-drivers-tesla-450-450.102.04/debian/nvidia-alternative.postinst.in nvidia-graphics-drivers-tesla-450-450.102.04/debian/nvidia-alternat
Bug#986827: unblock: nvidia-graphics-drivers-tesla-460/460.32.03-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package nvidia-graphics-drivers-tesla-460
This is essentially the same diff as for
nvidia-graphics-drivers-tesla-{418,450}.
Let's synchronize the packaging with src:nvidia-graphics-drivers to ease
future stable updates.
These changes are already in src:nvidia-graphics-drivers in testing.
I've waited with the corresponding unblocks in case we would get another
new upstream release (with CVE fixes).
The missing libnvidia-ml.so symlink was spotted by enabling the nvml
plugin in hwloc-contrib and needs to be fixed in all driver packages.
The dkms changes are making my life easier and were in
src:nvidia-graphics-drivers early enough to migrate on their own.
Andreas
unblock nvidia-graphics-drivers-tesla-460/460.32.03-3
diff -Nru nvidia-graphics-drivers-tesla-460-460.32.03/debian/changelog
nvidia-graphics-drivers-tesla-460-460.32.03/debian/changelog
--- nvidia-graphics-drivers-tesla-460-460.32.03/debian/changelog
2021-01-26 11:51:14.0 +0100
+++ nvidia-graphics-drivers-tesla-460-460.32.03/debian/changelog
2021-03-13 21:31:33.0 +0100
@@ -1,3 +1,12 @@
+nvidia-graphics-drivers-tesla-460 (460.32.03-3) unstable; urgency=medium
+
+ * Switch to dh-sequence-dkms (460.56-1).
+ * Simplify dh_dkms usage (460.56-1).
+ * nvidia-tesla-460-alternative: Add libnvidia-ml.so slave alternative if
+libnvidia-ml-dev is installed (460.56-2). (Closes: #984881)
+
+ -- Andreas Beckmann Sat, 13 Mar 2021 21:31:33 +0100
+
nvidia-graphics-drivers-tesla-460 (460.32.03-2) unstable; urgency=medium
* Rebuild as Tesla 460 driver.
@@ -226,6 +235,15 @@
-- Andreas Beckmann Thu, 24 Sep 2020 21:52:54 +0200
+nvidia-graphics-drivers-tesla-450 (450.102.04-2) unstable; urgency=medium
+
+ * Switch to dh-sequence-dkms (460.56-1).
+ * Simplify dh_dkms usage (460.56-1).
+ * nvidia-tesla-450-alternative: Add libnvidia-ml.so slave alternative if
+libnvidia-ml-dev is installed (460.56-2). (Closes: #984881)
+
+ -- Andreas Beckmann Sat, 13 Mar 2021 18:43:15 +0100
+
nvidia-graphics-drivers-tesla-450 (450.102.04-1) unstable; urgency=medium
* New upstream long lived branch release 450.102.04 (2021-01-07).
@@ -499,6 +517,15 @@
-- Andreas Beckmann Wed, 01 Jul 2020 00:02:18 +0200
+nvidia-graphics-drivers-tesla-440 (440.118.02-4) unstable; urgency=medium
+
+ * Switch to dh-sequence-dkms (460.56-1).
+ * Simplify dh_dkms usage (460.56-1).
+ * nvidia-tesla-440-alternative: Add libnvidia-ml.so slave alternative if
+libnvidia-ml-dev is installed (460.56-2). (Closes: #984881)
+
+ -- Andreas Beckmann Fri, 12 Mar 2021 21:03:13 +0100
+
nvidia-graphics-drivers-tesla-440 (440.118.02-3) unstable; urgency=medium
* Metadata updates.
@@ -1026,6 +1053,15 @@
-- Andreas Beckmann Sat, 25 May 2019 13:49:09 +0200
+nvidia-graphics-drivers-tesla-418 (418.181.07-2) unstable; urgency=medium
+
+ * Switch to dh-sequence-dkms (460.56-1).
+ * Simplify dh_dkms usage (460.56-1).
+ * nvidia-tesla-418-alternative: Add libnvidia-ml.so slave alternative if
+libnvidia-ml-dev is installed (460.56-2). (Closes: #984881)
+
+ -- Andreas Beckmann Fri, 12 Mar 2021 20:11:00 +0100
+
nvidia-graphics-drivers-tesla-418 (418.181.07-1) unstable; urgency=medium
* New upstream Tesla release 418.181.07 (2021-01-19).
diff -Nru nvidia-graphics-drivers-tesla-460-460.32.03/debian/control
nvidia-graphics-drivers-tesla-460-460.32.03/debian/control
--- nvidia-graphics-drivers-tesla-460-460.32.03/debian/control 2021-01-26
11:51:14.0 +0100
+++ nvidia-graphics-drivers-tesla-460-460.32.03/debian/control 2021-03-13
21:31:33.0 +0100
@@ -11,9 +11,9 @@
Vcs-Git: https://salsa.debian.org/nvidia-team/nvidia-graphics-drivers.git -b
tesla-450/master
Build-Depends:
debhelper-compat (= 13),
+ dh-sequence-dkms,
dh-exec,
xz-utils,
- dkms,
libvulkan1 (>= 1.0.42),
libxext6,
quilt,
diff -Nru nvidia-graphics-drivers-tesla-460-460.32.03/debian/control.in
nvidia-graphics-drivers-tesla-460-460.32.03/debian/control.in
--- nvidia-graphics-drivers-tesla-460-460.32.03/debian/control.in
2021-01-26 11:51:14.0 +0100
+++ nvidia-graphics-drivers-tesla-460-460.32.03/debian/control.in
2021-03-13 21:31:33.0 +0100
@@ -9,9 +9,9 @@
Vcs-Git: https://salsa.debian.org/nvidia-team/nvidia-graphics-drivers.git -b
tesla-450/master
Build-Depends:
debhelper-compat (= 13),
+ dh-sequence-dkms,
dh-exec,
xz-utils,
- dkms,
libvulkan1 (>= 1.0.42),
libxext6,
quilt,
diff -Nru nvidia-graphics-drivers-tesla-460-460.32.03/debian/control.md5sum
nvidia-graphics-drivers-tesla-460-460.32.03/debian/control.md5sum
--- nvidia-graphics-drivers-tesla-460-460.32.03/debian/control.md5sum
2021-01-26 11:51:14.0 +0100
+++ nvidia-graphics-drivers-tesla-460-460.32.03/debian/control.md5sum
2021-03-13 21:31:33.0 +0100
@@ -1,5 +1,5 @@
-52988eeaff5a78a224e8d2
Bug#986831: unblock: node-core-js/3.8.2-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package node-core-js [ Reason ] node-core-js provides a broken and useless symlink (#985697). [ Impact ] No real impact, just a uselss broken symlink [ Tests ] Test & autopkgtest still works [ Risks ] No risk [ 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 Cheers, Yadd unblock node-core-js/3.8.2-2 diff --git a/debian/changelog b/debian/changelog index 666b438..35d757b 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +node-core-js (3.8.2-2) unstable; urgency=medium + + * Team upload + * Remove useless and broken symlink (Closes: #985697) + + -- Yadd Mon, 22 Mar 2021 11:42:29 +0100 + node-core-js (3.8.2-1) unstable; urgency=medium * Team upload diff --git a/debian/copyright b/debian/copyright index 287bf91..6cce180 100644 --- a/debian/copyright +++ b/debian/copyright @@ -9,7 +9,7 @@ License: Expat Files: debian/* Copyright: 2016, Sruthi Chandran - 2019, Xavier Guimard + 2019, Yadd License: Expat License: Expat diff --git a/debian/rules b/debian/rules index af0314f..a7cb47a 100755 --- a/debian/rules +++ b/debian/rules @@ -9,7 +9,7 @@ override_dh_auto_build: node packages/core-js-compat/src/build-data node packages/core-js-compat/src/build-entries node packages/core-js-compat/src/build-modules-by-versions - for i in es features internals modules proposals scripts stable stage web configurator.js postinstall.js; do \ + for i in es features internals modules proposals stable stage web configurator.js postinstall.js; do \ ln -s ../../packages/core-js/$$i packages/core-js-pure/$$i; \ done cp packages/core-js/index.js packages/core-js-pure/
Bug#986832: unblock: svtplay-dl/3.0-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package svtplay-dl
[ Reason ]
svtplay-dl is a tool to download multimedia from various video websites,
especially targetting nordic demographics. Changes to the external service
svtplay.se required modifications to the svtplay-dl support for that
service to be able to work at all. Because unrelated significant work has
also been done upstream, I've isolated the fix for the service breakage
and backported it in the 3.0-2 package.
[ Impact ]
Users of an unmodified svtplay-dl are not able to use the tool when
interacting with svtplay.se. svtplay.se is the "flagship" service
supported by svtplay-dl. Support for other services is unaffected.
Many of the services covered by svtplay-dl are also covered by other
tools, including youtube-dl. (Though, they also suffer from the same
need for updates as external services change.)
[ Tests ]
Manual testing of svtplay-dl against the svtplay.se service. Changes are
limited to only this service. (The automated test suite of the package
does not catch service breakage.)
[ Risks ]
svtplay-dl is a leaf package and the changes are, while not trivial, at
least limited and scoped to the affected service. The changes are
backported and correspond to the service support in upstream version 3.2.
[ 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 ]
The changes are also available on salsa:
https://salsa.debian.org/olof/svtplay-dl/-/compare/debian%2F3.0-1...debian%2F3.0-2
Because of a misunderstanding with the freeze timelines/policies on my
part, the 3.0-2 package is already uploaded to unstable. My apologies if
this causes problems!
Thanks!
--
olofdiffstat for svtplay-dl-3.0 svtplay-dl-3.0
changelog |6
patches/debian-changes | 302 +
patches/series |1
3 files changed, 309 insertions(+)
No differences were encountered between the control files
diff -Nru svtplay-dl-3.0/debian/changelog svtplay-dl-3.0/debian/changelog
--- svtplay-dl-3.0/debian/changelog 2021-02-17 22:21:05.0 +0100
+++ svtplay-dl-3.0/debian/changelog 2021-03-12 19:21:49.0 +0100
@@ -1,3 +1,9 @@
+svtplay-dl (3.0-2) unstable; urgency=medium
+
+ * Backport fixes to svtplay service support from 3.2
+
+ -- Olof Johansson Fri, 12 Mar 2021 19:21:49 +0100
+
svtplay-dl (3.0-1) unstable; urgency=medium
* New upstream version 3.0
diff -Nru svtplay-dl-3.0/debian/patches/debian-changes svtplay-dl-3.0/debian/patches/debian-changes
--- svtplay-dl-3.0/debian/patches/debian-changes 1970-01-01 01:00:00.0 +0100
+++ svtplay-dl-3.0/debian/patches/debian-changes 2021-03-12 19:21:49.0 +0100
@@ -0,0 +1,302 @@
+Subject: Collected Debian patches for svtplay-dl
+Author: Olof Johansson
+
+The svtplay-dl package is maintained in Git rather than maintaining
+patches as separate files, and separating the patches doesn't seem to
+be worth the effort. They are therefore all included in this single
+Debian patch.
+
+For full commit history and separated commits, see the packaging Git
+repository.
+--- svtplay-dl-3.0.orig/lib/svtplay_dl/service/svtplay.py
svtplay-dl-3.0/lib/svtplay_dl/service/svtplay.py
+@@ -7,7 +7,6 @@ import json
+ import logging
+ import re
+ import time
+-from operator import itemgetter
+ from urllib.parse import parse_qs
+ from urllib.parse import urljoin
+ from urllib.parse import urlparse
+@@ -21,6 +20,13 @@ from svtplay_dl.subtitle import subtitle
+ from svtplay_dl.utils.text import filenamify
+
+ URL_VIDEO_API = "https://api.svt.se/video/";
++LIVE_CHANNELS = {
++"svtbarn": "ch-barnkanalen",
++"svt1": "ch-svt1",
++"svt2": "ch-svt2",
++"svt24": "ch-svt24",
++"kunskapskanalen": "ch-kunskapskanalen",
++}
+
+
+ class Svtplay(Service, MetadataThumbMixin):
+@@ -42,7 +48,7 @@ class Svtplay(Service, MetadataThumbMixi
+ urldata = self.get_urldata()
+
+ if parse.path[:8] == "/kanaler":
+-ch = "ch-{}".format(parse.path[parse.path.rfind("/") + 1 :])
++ch = LIVE_CHANNELS[parse.path[parse.path.rfind("/") + 1 :]]
+ _url = urljoin(URL_VIDEO_API, ch)
+ res = self.http.get(_url)
+ try:
+@@ -66,14 +72,12 @@ class Svtplay(Service, MetadataThumbMixi
+ for data_entry in janson["props"]["urqlState"].values():
+ entry = json.loads(data_entry["data"])
+ for key, data in entry.items():
+-if key == "listablesByEscenicId" and "videoSvtId" in data[0]:
+-video_data = data[0]
+-vid = video_data["videoSvtId"]
++if key == "detailsPage" and "moreDetails" in data:
++video_data = data
++vid = data["video"]["svtId"]
+
Bug#986835: [pre-approval] unblock: dpkg/1.20.8
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
This is a pre-approval unblock request for dpkg.
[ Reason ]
This includes an RC bug fix, and an old regression affecting apt
with auto-deconfiguring during upgrades for Protected/Essential
packages, a regression in the perl code ignoring exceptions, and a
couple of recent regressions in start-stop-daemon and dpkg-realpath.
Then a few fixes to the test suite, affecting mostly CPAN.
[ Impact ]
The ones affecting the code would not be good to let as is. The test
suite ones even though not affecting Debian directly should be safe,
otherwise they'd not pass. :)
[ Tests ]
The unit tests and the recently merged functional test suite all pass.
Not all the above are covered by these, but they have been tested
manually otherwise. I have tests for the exception trapping, but it
was too invasive so I've queued it for 1.21.x instead.
[ Risks ]
The changes either affect new features (s-s-d), new features breaking
other parts of the code (dpkg-realpath), or behavior that would
currently fail anyway (auto-deconfigure for Protected/Essential),
and that apt will need to workaround for now via --force options.
There should be no behavior changes during source package building,
except for restoring some error failures that were currently being
partially ignored (for dpkg-source, but then trapped by dpkg-buildpackage
f.ex.).
All changes are fairly minimal.
[ Checklist ]
[~] all changes are documented in the d/changelog
(except a silent indentation fix in one of the man pages,
covered in the ChangeLog file)
[√] I reviewed all changes and I approve them
[~] attach debdiff against the package in testing
(debdiff against 1.20.7 which is what's in git's master, instead
of 1.20.7.1 which was a source rebuild due to a botched tarball
and lived in the sid branch)
[ Other info ]
The other remaining RC I need to downgrade, as it looks like a wishlist
now, if I've understood the reopen reason correctly.
The debdiff includes lots of noise due to the po and generated translated
man pages, that's why I've included the relevant split patches excluding
translation updates. And the git branch is at:
https://git.hadrons.org/cgit/debian/dpkg/dpkg.git/log/?h=next/1.20.8
unblock dpkg/1.20.8
Thanks,
Guillem
dpkg-1.20.7--1.20.8.debdiff.xz
Description: application/xz
From 09b0b3ab99ba197a4fc5abf9363de32b472d9b61 Mon Sep 17 00:00:00 2001
From: Guillem Jover
Date: Sat, 16 Jan 2021 13:34:34 +0100
Subject: [PATCH 01/15] Test::Dpkg: Fix test data path fetching on CPAN
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
There is no guarantee that the perl used will have «.» in INC, so we
need to add an explicit «./» prefix, which we were already doing for
the autotools case. Unify the handling for autotools and CPAN, which
should fix the latter.
---
scripts/Test/Dpkg.pm | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/scripts/Test/Dpkg.pm b/scripts/Test/Dpkg.pm
index 937f333ba..a30168975 100644
--- a/scripts/Test/Dpkg.pm
+++ b/scripts/Test/Dpkg.pm
@@ -79,12 +79,10 @@ sub test_get_data_path
my $path = shift;
if (defined $path) {
-if ($test_mode eq 'cpan') {
-return $path;
-} else {
-my $srcdir = $ENV{srcdir} || '.';
-return "$srcdir/$path";
-}
+my $srcdir;
+$srcdir = $ENV{srcdir} if $test_mode ne 'cpan';
+$srcdir ||= '.';
+return "$srcdir/$path";
} else {
return _test_get_caller_dir();
}
--
2.31.0
From 1974f18a184a7425ffa75b70f0d24852ef61ecd1 Mon Sep 17 00:00:00 2001
From: Guillem Jover
Date: Sat, 16 Jan 2021 13:25:14 +0100
Subject: [PATCH 02/15] test: Set PERL in the perl test suite
There is no guarantee that the PERL environment variable will contain
the perl executable path or name. When running the test suite from the
autotools build system we always set the PERL environment variable,
but on CPAN we were not doing that, and some CPAN testers have PERL
set to its version.
---
scripts/Build.PL.in | 2 ++
1 file changed, 2 insertions(+)
diff --git a/scripts/Build.PL.in b/scripts/Build.PL.in
index 9846ffc91..c6be8c36a 100644
--- a/scripts/Build.PL.in
+++ b/scripts/Build.PL.in
@@ -17,6 +17,7 @@ if (-e 'Build.PL.in') {
my $class = Module::Build->subclass(
class => 'Module::Build::Dpkg',
code => q{
+require Config;
require IPC::Cmd;
sub find_command {
@@ -70,6 +71,7 @@ my $class = Module::Build->subclass(
local $ENV{LANG} = 'C';
local $ENV{LC_ALL} = 'C';
+local $ENV{PERL} = $Config{perlpath};
local $ENV{DPKG_TEST_MODE} = 'cpan';
local $ENV{DPKG_DATADIR} = 'data';
local $ENV{DPKG_ORIGINS_DIR} = 't/origins';
--
2.31.0
From 3844c38302396772f78a670bb8b4f678437600d5 Mon Sep 17 00:00:0
Bug#986838: unblock: openrc/0.42-2.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear Release Team, Please unblock package openrc. I uploaded a source NMU with a targeted fix to address RC bug #985509 8 days ago. No regressions have been reported and there has been no follow up from the maintainers. Openrc is scheduled to be autoremoved from bullseye on 19th April and migration before then to avoid this is desirable. The source debdiff is diff -Nru openrc-0.42/debian/changelog openrc-0.42/debian/changelog --- openrc-0.42/debian/changelog2020-11-27 08:48:35.0 + +++ openrc-0.42/debian/changelog2021-04-02 11:16:00.0 +0100 @@ -1,3 +1,11 @@ +openrc (0.42-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Make -dev package symlinks in /usr/lib target shared libraries in +/lib. (Closes: #985509). + + -- Mark Hindley Fri, 02 Apr 2021 11:16:00 +0100 + openrc (0.42-2) unstable; urgency=medium * Team upload. diff -Nru openrc-0.42/debian/libeinfo-dev.links.in openrc-0.42/debian/libeinfo-dev.links.in --- openrc-0.42/debian/libeinfo-dev.links.in1970-01-01 01:00:00.0 +0100 +++ openrc-0.42/debian/libeinfo-dev.links.in2021-04-02 11:16:00.0 +0100 @@ -0,0 +1 @@ +@SHLIBDIR@/libeinfo.so.1 @LIBDIR@/libeinfo.so diff -Nru openrc-0.42/debian/librc-dev.install.in openrc-0.42/debian/librc-dev.install.in --- openrc-0.42/debian/librc-dev.install.in 2020-11-27 08:48:35.0 + +++ openrc-0.42/debian/librc-dev.install.in 2021-04-02 11:16:00.0 +0100 @@ -1,4 +1,3 @@ -debian/tmp@SHLIBDIR@/librc.so /usr@SHLIBDIR@ debian/tmp/usr/include/rc.h /usr/include debian/tmp@LIBDIR@/pkgconfig/openrc.pc @LIBDIR@/pkgconfig debian/tmp/usr/share/man/man3/r*/usr/share/man/man3 diff -Nru openrc-0.42/debian/librc-dev.links.in openrc-0.42/debian/librc-dev.links.in --- openrc-0.42/debian/librc-dev.links.in 1970-01-01 01:00:00.0 +0100 +++ openrc-0.42/debian/librc-dev.links.in 2021-04-02 11:16:00.0 +0100 @@ -0,0 +1 @@ +@SHLIBDIR@/librc.so.1 @LIBDIR@/librc.so diff -Nru openrc-0.42/debian/rules openrc-0.42/debian/rules --- openrc-0.42/debian/rules2020-11-27 08:48:35.0 + +++ openrc-0.42/debian/rules2021-04-02 11:16:00.0 +0100 @@ -15,7 +15,7 @@ DEB_HOST_ARCH_OS ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_OS) DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) -DH_INSTALL_FILES = $(basename $(wildcard debian/*.install.in)) +DH_INSTALL_FILES = $(basename $(wildcard debian/*.install.in) $(wildcard debian/*.links.in)) export LIBDIR = /usr/lib/$(DEB_HOST_MULTIARCH) export SHLIBDIR = /lib/$(DEB_HOST_MULTIARCH) @@ -35,6 +35,9 @@ %.install: %.install.in sed -e 's;@SHLIBDIR@;$(SHLIBDIR);g' -e 's;@LIBDIR@;$(LIBDIR);g' <$< >$@ +%.links: %.links.in + sed -e 's;@SHLIBDIR@;$(SHLIBDIR);g' -e 's;@LIBDIR@;$(LIBDIR);g' <$< >$@ + override_dh_auto_clean: dh_auto_clean rm -f $(DH_INSTALL_FILES) The binary debdiff identifies the only change as the desired change in symlink target: [The following lists of changes regard files as different if they have different names, permissions or owners.] Files in second .changes but not in first - lrwxrwxrwx root/root /usr/lib/x86_64-linux-gnu/libeinfo.so -> /lib/x86_64-linux-gnu/libeinfo.so.1 lrwxrwxrwx root/root /usr/lib/x86_64-linux-gnu/librc.so -> /lib/x86_64-linux-gnu/librc.so.1 Files in first .changes but not in second - lrwxrwxrwx root/root /usr/lib/x86_64-linux-gnu/libeinfo.so -> libeinfo.so.1 lrwxrwxrwx root/root /usr/lib/x86_64-linux-gnu/librc.so -> librc.so.1 Thanks. Mark unblock openrc/0.42-2.1 -- System Information: Debian Release: 10.0 Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled
Processed: Re: Bug#986758: unblock: systemd/247.3-5
Processing control commands: > retitle -1 unblock: systemd/247.3-5 Bug #986758 [release.debian.org] unblock: systemd/247.3-4 Changed Bug title to 'unblock: systemd/247.3-5' from 'unblock: systemd/247.3-4'. -- 986758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986758: unblock: systemd/247.3-5
control: retitle -1 unblock: systemd/247.3-5
Am 11.04.21 um 18:48 schrieb Luca Boccassi:
Please unblock package systemd
As requested by Michael, opening unblock ticket. Debdiff attached. Two
high-impact patches are backported from upstream and should be included
in Bullseye.
Thanks Luca!
* Backport patch to fix assert with invalid LoadCredentials=
Regression introduced in v247, fixed in v249, see:
https://github.com/systemd/systemd/issues/19178
(Closes: #986302)
* network: Delay addition of IPv6 Proxy NDP addresses.
Fixes "IPv6 Proxy NDP addresses are being lost from interfaces after
networkd adds them". (Closes: #985510)
The first patch fixes a crash when a malformed option is set in any
unit.
unblock systemd/247.3-4
I decided to make a 247.3-5 upload to fix #975018 as well:
udev-udeb: setup /dev/fd, /dev/std{in,out,err} symlinks
As systemd-udevd no longer sets them up itself, we create them manually
after mounting devtmpfs. This avoids breaking applications which expect
Somehow this issue did not show up on the systemd bug tracker, so I
completely forgot about it. Apologies for that.
This fixes a regression which e.g. broke fetch-url and triggered a
workaround in debian-installer-utils_1.134:
[ Raphaël Hertzog ]
* Use /proc/self/fd/4 instead of /dev/fd/4 to unbreak fetch-url with
recent
udev versions that no longer setup the /dev/fd symlink. Closes: #967546
I'd rather see this fixed for good. It's possible that other
applications expect those symlinks as well.
This does affect udev-udeb, so kibi's ack would be appreciated.
Thanks for considering,
Michael
unblock systemd/247.3-5
diff --git a/debian/changelog b/debian/changelog
index 22a8ad2..0588fec 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,27 +1,3 @@
-systemd (247.3-5) unstable; urgency=medium
-
- * udev-udeb: setup /dev/fd, /dev/std{in,out,err} symlinks.
-As systemd-udevd no longer sets them up itself, we create them manually
-after mounting devtmpfs. This avoids breaking applications which expect
-those symlinks. (Closes: #975018)
-
- -- Michael Biebl Mon, 12 Apr 2021 20:21:24 +0200
-
-systemd (247.3-4) unstable; urgency=medium
-
- [ Luca Boccassi ]
- * Backport patch to fix assert with invalid LoadCredentials=
-Regression introduced in v247, fixed in v249, see:
-https://github.com/systemd/systemd/issues/19178
-(Closes: #986302)
-
- [ Michael Biebl ]
- * network: Delay addition of IPv6 Proxy NDP addresses.
-Fixes "IPv6 Proxy NDP addresses are being lost from interfaces after
-networkd adds them". (Closes: #985510)
-
- -- Michael Biebl Sun, 11 Apr 2021 16:06:46 +0200
-
systemd (247.3-3) unstable; urgency=medium
* pkg-config: make prefix overridable again (Closes: #984763)
diff --git a/debian/extra/start-udev b/debian/extra/start-udev
index 0a8b284..6048925 100755
--- a/debian/extra/start-udev
+++ b/debian/extra/start-udev
@@ -6,11 +6,6 @@ fi
if ! grep -E -q "^[^[:space:]]+ /dev devtmpfs" /proc/mounts; then
mount -n -o mode=0755 -t devtmpfs devtmpfs /dev
-# Setup a few /dev symlinks, see #975018
-[ ! -h /dev/fd ] && ln -s /proc/self/fd /dev/fd
-[ ! -h /dev/stdin ] && ln -s /proc/self/fd/0 /dev/stdin
-[ ! -h /dev/stdout ] && ln -s /proc/self/fd/1 /dev/stdout
-[ ! -h /dev/stderr ] && ln -s /proc/self/fd/2 /dev/stderr
fi
SYSTEMD_LOG_LEVEL=notice /lib/systemd/systemd-udevd --daemon
--resolve-names=never
diff --git
a/debian/patches/LoadCredentials-do-not-assert-on-invalid-syntax.patch
b/debian/patches/LoadCredentials-do-not-assert-on-invalid-syntax.patch
deleted file mode 100644
index c9e3500..000
--- a/debian/patches/LoadCredentials-do-not-assert-on-invalid-syntax.patch
+++ /dev/null
@@ -1,34 +0,0 @@
-From: Luca Boccassi
-Date: Thu, 1 Apr 2021 22:18:29 +0100
-Subject: LoadCredentials: do not assert on invalid syntax
-
-LoadCredentials=foo causes an assertion to be triggered, as we
-are not checking that the rvalue's right hand side part is non-empty
-before using it in unit_full_printf.
-
-Fixes #19178
-
-# printf [Service]nLoadCredential=passwd.hashed-password.rootn > hello.service
-# systemd-analyze verify ./hello.service
-...
-Assertion 'format' failed at src/core/unit-printf.c:232, function
unit_full_printf(). Aborting.
-Aborted (core dumped)
-
-(cherry picked from commit f7a6f1226e800f7695c2073675523062ea697aa4)
- src/core/load-fragment.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/src/core/load-fragment.c b/src/core/load-fragment.c
-index 4964249..5b66fb1 100644
a/src/core/load-fragment.c
-+++ b/src/core/load-fragment.c
-@@ -4569,7 +4569,7 @@ int config_parse_load_credential(
- r = extract_first_word(&p, &word, ":",
EXTRACT_DONT_COALESCE_SEPARATORS);
- if (r == -ENOMEM)
- return log_oom();
--if (r <= 0) {
-+if (r <= 0 || isempty(p)) {
- log_syntax(unit, LOG_WARNING, fil
Bug#986846: unblock: rabbitmq-server/3.8.9-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package rabbitmq-server
There's a nasty bug when rabbit parses its config file.
If rabbit missreads it, it may incorrectly size its memory
footpring, leading to a (maybe) non-functional service that
doesn't allocate enough memory.
The proposed new release includes a patch from upstream
to fix the situation.
Please unblock rabbitmq-server/3.8.9-3
Cheers,
Thomas Goirand (zigo)
diff -Nru rabbitmq-server-3.8.9/debian/changelog
rabbitmq-server-3.8.9/debian/changelog
--- rabbitmq-server-3.8.9/debian/changelog 2021-03-26 14:24:32.0
+0100
+++ rabbitmq-server-3.8.9/debian/changelog 2021-04-10 22:59:57.0
+0200
@@ -1,3 +1,10 @@
+rabbitmq-server (3.8.9-3) unstable; urgency=medium
+
+ [ Adam Cecile ]
+ * Merge upstream PR #2965 fixing rabbitmqctl parsing bug. (Closes: #986734)
+
+ -- Thomas Goirand Sat, 10 Apr 2021 22:59:57 +0200
+
rabbitmq-server (3.8.9-2) unstable; urgency=medium
* Do not use the /usr/sbin/rabbitmq-server wrapper in systemd service file
diff -Nru rabbitmq-server-3.8.9/debian/patches/series
rabbitmq-server-3.8.9/debian/patches/series
--- rabbitmq-server-3.8.9/debian/patches/series 2021-03-26 14:24:32.0
+0100
+++ rabbitmq-server-3.8.9/debian/patches/series 2021-04-10 22:59:57.0
+0200
@@ -1,2 +1,3 @@
lets-use-python3-not-python-binary.patch
rabbitmq-dist.mk.patch
+Upstream_PR2965_fixing_rabbitmqctl_parsing
diff -Nru
rabbitmq-server-3.8.9/debian/patches/Upstream_PR2965_fixing_rabbitmqctl_parsing
rabbitmq-server-3.8.9/debian/patches/Upstream_PR2965_fixing_rabbitmqctl_parsing
---
rabbitmq-server-3.8.9/debian/patches/Upstream_PR2965_fixing_rabbitmqctl_parsing
1970-01-01 01:00:00.0 +0100
+++
rabbitmq-server-3.8.9/debian/patches/Upstream_PR2965_fixing_rabbitmqctl_parsing
2021-04-10 22:59:57.0 +0200
@@ -0,0 +1,44 @@
+Description: Fix incorrect parsing of vm_memory_high_watermark
+ Upstream bug:
+ https://github.com/rabbitmq/rabbitmq-server/issues/2964
+Author: Michael Klishin
+Origin: upstream, https://github.com/rabbitmq/rabbitmq-server/pull/2965
+Bug-Debian: https://bugs.debian.org/986734
+Reviewed-By: Adam Cecile
+Last-Update: 2021-04-10
+
+--- rabbitmq-server-3.8.9.orig/deps/rabbit/src/rabbit_disk_monitor.erl
rabbitmq-server-3.8.9/deps/rabbit/src/rabbit_disk_monitor.erl
+@@ -66,7 +66,7 @@
+
+ %%
+
+--type disk_free_limit() :: (integer() | string() | {'mem_relative', float() |
integer()}).
++-type disk_free_limit() :: integer() | {'absolute', integer()} | string() |
{'mem_relative', float() | integer()}.
+
+ %%
+ %% Public API
+@@ -272,6 +272,8 @@ parse_free_win32(CommandResult) ->
+ interpret_limit({mem_relative, Relative})
+ when is_number(Relative) ->
+ round(Relative * vm_memory_monitor:get_total_memory());
++interpret_limit({absolute, Absolute}) ->
++interpret_limit(Absolute);
+ interpret_limit(Absolute) ->
+ case rabbit_resource_monitor_misc:parse_information_unit(Absolute) of
+ {ok, ParsedAbsolute} -> ParsedAbsolute;
+---
rabbitmq-server-3.8.9.orig/deps/rabbitmq_cli/lib/rabbitmq/cli/core/memory.ex
rabbitmq-server-3.8.9/deps/rabbitmq_cli/lib/rabbitmq/cli/core/memory.ex
+@@ -56,6 +56,12 @@ defmodule RabbitMQ.CLI.Core.Memory do
+ def formatted_watermark(val) when is_float(val) do
+ %{relative: val}
+ end
++ def formatted_watermark({:relative, val}) when is_float(val) do
++%{relative: val}
++ end
++ def formatted_watermark(:infinity) do
++%{relative: 1.0}
++ end
+ def formatted_watermark({:absolute, val}) do
+ %{absolute: parse_watermark(val)}
+ end
Bug#986847: unblock: network-manager/1.30.0-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package network-manager
It cherry-picks an upstream commit to fix
#986809 / CVE-2021-20297
Full debdiff attached.
Regards,
Michael
unblock network-manager/1.30.0-2
diff --git a/debian/changelog b/debian/changelog
index 44ae3264f7..3431459d47 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+network-manager (1.30.0-2) unstable; urgency=medium
+
+ * core: fix crash in nm_wildcard_match_check()
+(CVE-2021-20297, Closes: #986809)
+
+ -- Michael Biebl Mon, 12 Apr 2021 21:15:36 +0200
+
network-manager (1.30.0-1) unstable; urgency=medium
* New upstream version 1.30.0
diff --git a/debian/control b/debian/control
index 06146cd204..d95f09bd03 100644
--- a/debian/control
+++ b/debian/control
@@ -65,7 +65,7 @@ Breaks: ${misc:Breaks}
Description: network management framework (daemon and userspace tools)
NetworkManager is a system network service that manages your network devices
and connections, attempting to keep active network connectivity when
- available. It manages ethernet, WiFi, mobile broadband (WWAN), and PPPoE
+ available. It manages ethernet, Wi-Fi, mobile broadband (WWAN), and PPPoE
devices, and provides VPN integration with a variety of different VPN
services.
.
@@ -100,7 +100,7 @@ Depends: ${shlibs:Depends},
Description: GObject-based client library for NetworkManager
NetworkManager is a system network service that manages your network devices
and connections, attempting to keep active network connectivity when
- available. It manages ethernet, WiFi, mobile broadband (WWAN), and PPPoE
+ available. It manages ethernet, Wi-Fi, mobile broadband (WWAN), and PPPoE
devices, and provides VPN integration with a variety of different VPN
services.
.
@@ -118,7 +118,7 @@ Depends: ${misc:Depends},
Description: GObject-based client library for NetworkManager (development
files)
NetworkManager is a system network service that manages your network devices
and connections, attempting to keep active network connectivity when
- available. It manages ethernet, WiFi, mobile broadband (WWAN), and PPPoE
+ available. It manages ethernet, Wi-Fi, mobile broadband (WWAN), and PPPoE
devices, and provides VPN integration with a variety of different VPN
services.
.
@@ -136,7 +136,7 @@ Replaces: gir1.2-networkmanager-1.0 (<< 1.8.0-2)
Description: GObject introspection data for the libnm library
NetworkManager is a system network service that manages your network devices
and connections, attempting to keep active network connectivity when
- available. It manages ethernet, WiFi, mobile broadband (WWAN), and PPPoE
+ available. It manages ethernet, Wi-Fi, mobile broadband (WWAN), and PPPoE
devices, and provides VPN integration with a variety of different VPN
services.
.
diff --git a/debian/patches/core-fix-crash-in-nm_wildcard_match_check.patch
b/debian/patches/core-fix-crash-in-nm_wildcard_match_check.patch
new file mode 100644
index 00..02d4484dd0
--- /dev/null
+++ b/debian/patches/core-fix-crash-in-nm_wildcard_match_check.patch
@@ -0,0 +1,74 @@
+From: Thomas Haller
+Date: Wed, 24 Mar 2021 21:05:19 +0100
+Subject: core: fix crash in nm_wildcard_match_check()
+
+It's not entirely clear how to treat %NULL.
+Clearly "match.interface-name=eth0" should not
+match with an interface %NULL. But what about
+"match.interface-name=!eth0"? It's now implemented
+that negative matches still succeed against %NULL.
+What about "match.interface-name=*"? That probably
+should also match with %NULL. So we treat %NULL really
+like "".
+
+Against commit 11cd443448bc ('iwd: Don't call IWD methods when device
+unmanaged'), we got this backtrace:
+
+#0 0x7f1c164069f1 in __strnlen_avx2 () at
../sysdeps/x86_64/multiarch/strlen-avx2.S:62
+#1 0x7f1c1637ac9e in __fnmatch (pattern=,
string=, string@entry=0x0, flags=flags@entry=0) at fnmatch.c:379
+p = 0x0
+res =
+orig_pattern =
+n =
+wpattern = 0x7fff8d860730 L"pci-:03:00.0"
+ps = {__count = 0, __value = {__wch = 0, __wchb = "\000\000\000"}}
+wpattern_malloc = 0x0
+wstring_malloc = 0x0
+wstring =
+alloca_used = 80
+__PRETTY_FUNCTION__ = "__fnmatch"
+#2 0x564484a978bf in nm_wildcard_match_check (str=0x0,
patterns=, num_patterns=) at
src/core/nm-core-utils.c:1959
+is_inverted = 0
+is_mandatory = 0
+match =
+p = 0x564486c43fa0 "pci-:03:00.0"
+has_optional = 0
+has_any_optional = 0
+i =
+#3 0x564484bf4797 in check_connection_compatible (self=, connection=, error=0x0) at
src/core/devices/nm-device.c:7499
+patterns =
+device_driver = 0x564486c76bd0 "veth"
+num_patterns = 1
+priv = 0x564486cbe0b0
Bug#986846: marked as done (unblock: rabbitmq-server/3.8.9-3)
Your message dated Mon, 12 Apr 2021 20:11:53 +
with message-id
and subject line unblock rabbitmq-server
has caused the Debian Bug report #986846,
regarding unblock: rabbitmq-server/3.8.9-3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
986846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package rabbitmq-server
There's a nasty bug when rabbit parses its config file.
If rabbit missreads it, it may incorrectly size its memory
footpring, leading to a (maybe) non-functional service that
doesn't allocate enough memory.
The proposed new release includes a patch from upstream
to fix the situation.
Please unblock rabbitmq-server/3.8.9-3
Cheers,
Thomas Goirand (zigo)
diff -Nru rabbitmq-server-3.8.9/debian/changelog
rabbitmq-server-3.8.9/debian/changelog
--- rabbitmq-server-3.8.9/debian/changelog 2021-03-26 14:24:32.0
+0100
+++ rabbitmq-server-3.8.9/debian/changelog 2021-04-10 22:59:57.0
+0200
@@ -1,3 +1,10 @@
+rabbitmq-server (3.8.9-3) unstable; urgency=medium
+
+ [ Adam Cecile ]
+ * Merge upstream PR #2965 fixing rabbitmqctl parsing bug. (Closes: #986734)
+
+ -- Thomas Goirand Sat, 10 Apr 2021 22:59:57 +0200
+
rabbitmq-server (3.8.9-2) unstable; urgency=medium
* Do not use the /usr/sbin/rabbitmq-server wrapper in systemd service file
diff -Nru rabbitmq-server-3.8.9/debian/patches/series
rabbitmq-server-3.8.9/debian/patches/series
--- rabbitmq-server-3.8.9/debian/patches/series 2021-03-26 14:24:32.0
+0100
+++ rabbitmq-server-3.8.9/debian/patches/series 2021-04-10 22:59:57.0
+0200
@@ -1,2 +1,3 @@
lets-use-python3-not-python-binary.patch
rabbitmq-dist.mk.patch
+Upstream_PR2965_fixing_rabbitmqctl_parsing
diff -Nru
rabbitmq-server-3.8.9/debian/patches/Upstream_PR2965_fixing_rabbitmqctl_parsing
rabbitmq-server-3.8.9/debian/patches/Upstream_PR2965_fixing_rabbitmqctl_parsing
---
rabbitmq-server-3.8.9/debian/patches/Upstream_PR2965_fixing_rabbitmqctl_parsing
1970-01-01 01:00:00.0 +0100
+++
rabbitmq-server-3.8.9/debian/patches/Upstream_PR2965_fixing_rabbitmqctl_parsing
2021-04-10 22:59:57.0 +0200
@@ -0,0 +1,44 @@
+Description: Fix incorrect parsing of vm_memory_high_watermark
+ Upstream bug:
+ https://github.com/rabbitmq/rabbitmq-server/issues/2964
+Author: Michael Klishin
+Origin: upstream, https://github.com/rabbitmq/rabbitmq-server/pull/2965
+Bug-Debian: https://bugs.debian.org/986734
+Reviewed-By: Adam Cecile
+Last-Update: 2021-04-10
+
+--- rabbitmq-server-3.8.9.orig/deps/rabbit/src/rabbit_disk_monitor.erl
rabbitmq-server-3.8.9/deps/rabbit/src/rabbit_disk_monitor.erl
+@@ -66,7 +66,7 @@
+
+ %%
+
+--type disk_free_limit() :: (integer() | string() | {'mem_relative', float() |
integer()}).
++-type disk_free_limit() :: integer() | {'absolute', integer()} | string() |
{'mem_relative', float() | integer()}.
+
+ %%
+ %% Public API
+@@ -272,6 +272,8 @@ parse_free_win32(CommandResult) ->
+ interpret_limit({mem_relative, Relative})
+ when is_number(Relative) ->
+ round(Relative * vm_memory_monitor:get_total_memory());
++interpret_limit({absolute, Absolute}) ->
++interpret_limit(Absolute);
+ interpret_limit(Absolute) ->
+ case rabbit_resource_monitor_misc:parse_information_unit(Absolute) of
+ {ok, ParsedAbsolute} -> ParsedAbsolute;
+---
rabbitmq-server-3.8.9.orig/deps/rabbitmq_cli/lib/rabbitmq/cli/core/memory.ex
rabbitmq-server-3.8.9/deps/rabbitmq_cli/lib/rabbitmq/cli/core/memory.ex
+@@ -56,6 +56,12 @@ defmodule RabbitMQ.CLI.Core.Memory do
+ def formatted_watermark(val) when is_float(val) do
+ %{relative: val}
+ end
++ def formatted_watermark({:relative, val}) when is_float(val) do
++%{relative: val}
++ end
++ def formatted_watermark(:infinity) do
++%{relative: 1.0}
++ end
+ def formatted_watermark({:absolute, val}) do
+ %{absolute: parse_watermark(val)}
+ end
--- End Message ---
--- Begin Message ---
Unblocked.--- End Message ---
Bug#986831: marked as done (unblock: node-core-js/3.8.2-2)
Your message dated Mon, 12 Apr 2021 20:09:05 + with message-id and subject line unblock node-core-js has caused the Debian Bug report #986831, regarding unblock: node-core-js/3.8.2-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 986831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package node-core-js [ Reason ] node-core-js provides a broken and useless symlink (#985697). [ Impact ] No real impact, just a uselss broken symlink [ Tests ] Test & autopkgtest still works [ Risks ] No risk [ 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 Cheers, Yadd unblock node-core-js/3.8.2-2 diff --git a/debian/changelog b/debian/changelog index 666b438..35d757b 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +node-core-js (3.8.2-2) unstable; urgency=medium + + * Team upload + * Remove useless and broken symlink (Closes: #985697) + + -- Yadd Mon, 22 Mar 2021 11:42:29 +0100 + node-core-js (3.8.2-1) unstable; urgency=medium * Team upload diff --git a/debian/copyright b/debian/copyright index 287bf91..6cce180 100644 --- a/debian/copyright +++ b/debian/copyright @@ -9,7 +9,7 @@ License: Expat Files: debian/* Copyright: 2016, Sruthi Chandran - 2019, Xavier Guimard + 2019, Yadd License: Expat License: Expat diff --git a/debian/rules b/debian/rules index af0314f..a7cb47a 100755 --- a/debian/rules +++ b/debian/rules @@ -9,7 +9,7 @@ override_dh_auto_build: node packages/core-js-compat/src/build-data node packages/core-js-compat/src/build-entries node packages/core-js-compat/src/build-modules-by-versions - for i in es features internals modules proposals scripts stable stage web configurator.js postinstall.js; do \ + for i in es features internals modules proposals stable stage web configurator.js postinstall.js; do \ ln -s ../../packages/core-js/$$i packages/core-js-pure/$$i; \ done cp packages/core-js/index.js packages/core-js-pure/ --- End Message --- --- Begin Message --- Unblocked.--- End Message ---
Bug#986847: marked as done (unblock: network-manager/1.30.0-2)
Your message dated Mon, 12 Apr 2021 20:10:19 +
with message-id
and subject line unblock network-manager
has caused the Debian Bug report #986847,
regarding unblock: network-manager/1.30.0-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
986847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package network-manager
It cherry-picks an upstream commit to fix
#986809 / CVE-2021-20297
Full debdiff attached.
Regards,
Michael
unblock network-manager/1.30.0-2
diff --git a/debian/changelog b/debian/changelog
index 44ae3264f7..3431459d47 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+network-manager (1.30.0-2) unstable; urgency=medium
+
+ * core: fix crash in nm_wildcard_match_check()
+(CVE-2021-20297, Closes: #986809)
+
+ -- Michael Biebl Mon, 12 Apr 2021 21:15:36 +0200
+
network-manager (1.30.0-1) unstable; urgency=medium
* New upstream version 1.30.0
diff --git a/debian/control b/debian/control
index 06146cd204..d95f09bd03 100644
--- a/debian/control
+++ b/debian/control
@@ -65,7 +65,7 @@ Breaks: ${misc:Breaks}
Description: network management framework (daemon and userspace tools)
NetworkManager is a system network service that manages your network devices
and connections, attempting to keep active network connectivity when
- available. It manages ethernet, WiFi, mobile broadband (WWAN), and PPPoE
+ available. It manages ethernet, Wi-Fi, mobile broadband (WWAN), and PPPoE
devices, and provides VPN integration with a variety of different VPN
services.
.
@@ -100,7 +100,7 @@ Depends: ${shlibs:Depends},
Description: GObject-based client library for NetworkManager
NetworkManager is a system network service that manages your network devices
and connections, attempting to keep active network connectivity when
- available. It manages ethernet, WiFi, mobile broadband (WWAN), and PPPoE
+ available. It manages ethernet, Wi-Fi, mobile broadband (WWAN), and PPPoE
devices, and provides VPN integration with a variety of different VPN
services.
.
@@ -118,7 +118,7 @@ Depends: ${misc:Depends},
Description: GObject-based client library for NetworkManager (development
files)
NetworkManager is a system network service that manages your network devices
and connections, attempting to keep active network connectivity when
- available. It manages ethernet, WiFi, mobile broadband (WWAN), and PPPoE
+ available. It manages ethernet, Wi-Fi, mobile broadband (WWAN), and PPPoE
devices, and provides VPN integration with a variety of different VPN
services.
.
@@ -136,7 +136,7 @@ Replaces: gir1.2-networkmanager-1.0 (<< 1.8.0-2)
Description: GObject introspection data for the libnm library
NetworkManager is a system network service that manages your network devices
and connections, attempting to keep active network connectivity when
- available. It manages ethernet, WiFi, mobile broadband (WWAN), and PPPoE
+ available. It manages ethernet, Wi-Fi, mobile broadband (WWAN), and PPPoE
devices, and provides VPN integration with a variety of different VPN
services.
.
diff --git a/debian/patches/core-fix-crash-in-nm_wildcard_match_check.patch
b/debian/patches/core-fix-crash-in-nm_wildcard_match_check.patch
new file mode 100644
index 00..02d4484dd0
--- /dev/null
+++ b/debian/patches/core-fix-crash-in-nm_wildcard_match_check.patch
@@ -0,0 +1,74 @@
+From: Thomas Haller
+Date: Wed, 24 Mar 2021 21:05:19 +0100
+Subject: core: fix crash in nm_wildcard_match_check()
+
+It's not entirely clear how to treat %NULL.
+Clearly "match.interface-name=eth0" should not
+match with an interface %NULL. But what about
+"match.interface-name=!eth0"? It's now implemented
+that negative matches still succeed against %NULL.
+What about "match.interface-name=*"? That probably
+should also match with %NULL. So we treat %NULL really
+like "".
+
+Against commit 11cd443448bc ('iwd: Don't call IWD methods when device
+unmanaged'), we got this backtrace:
+
+#0 0x7f1c164069f1 in __strnlen_avx2 () at
../sysdeps/x86_64/multiarch/strlen-avx2.S:62
+#1 0x7f1c1637ac9e in __fnmatch (pattern=,
string=, string@entry=0x0, flags=flags@entry=0) at fnmatch.c:379
+p = 0x0
+res =
+orig_pattern =
+n =
+wpattern = 0x7fff8d860730 L"pci-:03:00.0"
+ps = {__count = 0, __value = {__wch = 0, __wchb = "\000\000\00
Bug#986766: marked as done (unblock: openbox/3.6.1-9+deb11u1)
Your message dated Mon, 12 Apr 2021 20:14:39 +
with message-id
and subject line unblock openbox
has caused the Debian Bug report #986766,
regarding unblock: openbox/3.6.1-9+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
986766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package openbox
[ Reason ]
This changes fixed infinite loop when openbox is running with > 2 screens
[ Impact ]
Same as above.
[ Tests ]
No tests affected.
[ Risks ]
Zero risks. Patch fixed multi monitor configuration.
diff -Nru openbox-3.6.1/debian/changelog openbox-3.6.1/debian/changelog
--- openbox-3.6.1/debian/changelog 2020-03-17 18:22:37.0 +0100
+++ openbox-3.6.1/debian/changelog 2021-03-18 22:11:13.0 +0100
@@ -1,3 +1,11 @@
+openbox (3.6.1-9+deb11u1) unstable; urgency=medium
+
+ [ dann frazier ]
+ * When running with > 2 screens, avoid calling XQueryPointer() in an
+infinite loop. (Closes: #983882)
+
+ -- Mateusz Łukasik Thu, 18 Mar 2021 22:11:13 +0100
+
openbox (3.6.1-9) unstable; urgency=medium
* Switch to python3. (Closes: #887122 #886716) (LP: #1816473)
diff -Nru
openbox-3.6.1/debian/patches/Fix-collision-between-iterator-and-throw-away-argume.patch
openbox-3.6.1/debian/patches/Fix-collision-between-iterator-and-throw-away-argume.patch
---
openbox-3.6.1/debian/patches/Fix-collision-between-iterator-and-throw-away-argume.patch
1970-01-01 01:00:00.0 +0100
+++
openbox-3.6.1/debian/patches/Fix-collision-between-iterator-and-throw-away-argume.patch
2021-03-18 22:10:53.0 +0100
@@ -0,0 +1,38 @@
+From: Alex Goins
+Date: Thu, 18 Feb 2021 21:25:22 -0600
+Subject: [PATCH] Fix collision between iterator and throw-away argument to
+ XQueryPointer()
+
+Without this, Openbox is unstable on any setup with more than 2 X screens, as
+the collision can make the loop infinitely call XQueryPointer() on X screen 1.
+
+Bug-Debian: https://bugs.debian.org/983882
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1917516
+Origin:
https://github.com/AlexGoinsNV/openbox-multiXscreen-bugfix/commit/2635c87d160aa5f6f9e91e290678e99111788d57
+Last-Updated: 2021-03-02
+
+Index: openbox-debian/openbox/screen.c
+===
+--- openbox-debian.orig/openbox/screen.c
openbox-debian/openbox/screen.c
+@@ -1908,16 +1908,16 @@ guint screen_monitor_pointer()
+ gboolean screen_pointer_pos(gint *x, gint *y)
+ {
+ Window w;
+-gint i;
++gint i, scrnindex;
+ guint u;
+ gboolean ret;
+
+ ret = !!XQueryPointer(obt_display, obt_root(ob_screen),
+ &w, &w, x, y, &i, &i, &u);
+ if (!ret) {
+-for (i = 0; i < ScreenCount(obt_display); ++i)
+-if (i != ob_screen)
+-if (XQueryPointer(obt_display, obt_root(i),
++for (scrnindex = 0; scrnindex < ScreenCount(obt_display); ++scrnindex)
++if (scrnindex != ob_screen)
++if (XQueryPointer(obt_display, obt_root(scrnindex),
+ &w, &w, x, y, &i, &i, &u))
+ break;
+ }
diff -Nru openbox-3.6.1/debian/patches/series
openbox-3.6.1/debian/patches/series
--- openbox-3.6.1/debian/patches/series 2020-03-15 17:26:18.0 +0100
+++ openbox-3.6.1/debian/patches/series 2021-03-18 22:11:00.0 +0100
@@ -22,3 +22,4 @@
887908.patch
917204_undecorated_maximized_no_border.patch
python3.patch
+Fix-collision-between-iterator-and-throw-away-argume.patch
--- End Message ---
--- Begin Message ---
Unblocked.--- End Message ---
Bug#986572: marked as done (unblock: osm2pgsql/1.4.1+ds-2 (pre-approval))
Your message dated Mon, 12 Apr 2021 20:14:59 +
with message-id
and subject line unblock osm2pgsql
has caused the Debian Bug report #986572,
regarding unblock: osm2pgsql/1.4.1+ds-2 (pre-approval)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
986572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
To fix two important issues affecting the version in bullseye,
I would like to upload these changes to unstable.
Do you agree that these changes are appropriate for a freeze exception?
[ Reason ]
Fixes important issues.
[ Impact ]
Poor performance and errors.
[ Tests ]
Upstream CI.
[ Risks ]
Low.
[ 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 ]
N/A
unblock osm2pgsql/1.4.1+ds-2
Kind Regards,
Bas
diff -Nru osm2pgsql-1.4.1+ds/debian/changelog
osm2pgsql-1.4.1+ds/debian/changelog
--- osm2pgsql-1.4.1+ds/debian/changelog 2021-02-04 05:23:03.0 +0100
+++ osm2pgsql-1.4.1+ds/debian/changelog 2021-04-07 15:59:14.0 +0200
@@ -1,3 +1,14 @@
+osm2pgsql (1.4.1+ds-2) unstable; urgency=medium
+
+ * Update watch file for GitHub URL changes.
+ * Add upstream patches:
+- 0001-Bugfix-Disable-expire-in-flex-output-when-not-used.patch
+ Important performance fix.
+- 0001-Bug-fix-Remove-schema-name-from-CREATE-INDEX.patch
+ Fix CREATE INDEX failure.
+
+ -- Bas Couwenberg Wed, 07 Apr 2021 15:59:14 +0200
+
osm2pgsql (1.4.1+ds-1) unstable; urgency=medium
* New upstream release.
diff -Nru
osm2pgsql-1.4.1+ds/debian/patches/0001-Bugfix-Disable-expire-in-flex-output-when-not-used.patch
osm2pgsql-1.4.1+ds/debian/patches/0001-Bugfix-Disable-expire-in-flex-output-when-not-used.patch
---
osm2pgsql-1.4.1+ds/debian/patches/0001-Bugfix-Disable-expire-in-flex-output-when-not-used.patch
1970-01-01 01:00:00.0 +0100
+++
osm2pgsql-1.4.1+ds/debian/patches/0001-Bugfix-Disable-expire-in-flex-output-when-not-used.patch
2021-04-07 15:56:01.0 +0200
@@ -0,0 +1,31 @@
+Description: Bugfix: Disable expire in flex output when not used
+ If we don't have expire enabled we never need to create an expire list.
+ But as a side effect of the two-stage processing we created such a list
+ which costs a lot of time and RAM. This commit disables this which
+ speeds up processing considerably.
+Author: Jochen Topf
+Origin: https://github.com/openstreetmap/osm2pgsql/issues/1436
+Bug: https://github.com/openstreetmap/osm2pgsql/issues/1436
+
+--- a/src/expire-tiles.hpp
b/src/expire-tiles.hpp
+@@ -60,6 +60,8 @@ struct expire_tiles
+ expire_tiles(uint32_t maxzoom, double maxbbox,
+ const std::shared_ptr &projection);
+
++bool enabled() const noexcept { return maxzoom != 0; }
++
+ int from_bbox(double min_lon, double min_lat, double max_lon,
+ double max_lat);
+ void from_wkb(char const *wkb, osmid_t osm_id);
+--- a/src/output-flex.cpp
b/src/output-flex.cpp
+@@ -1289,7 +1289,7 @@ void output_flex_t::delete_from_table(ta
+ assert(table_connection);
+ auto const id = table_connection->table().map_id(type, osm_id);
+
+-if (table_connection->table().has_geom_column()) {
++if (m_expire.enabled() && table_connection->table().has_geom_column()) {
+ auto const result = table_connection->get_geom_by_id(type, id);
+
+ if (result.num_tuples() == 0) {
diff -Nru
osm2pgsql-1.4.1+ds/debian/patches/0001-Bug-fix-Remove-schema-name-from-CREATE-INDEX.patch
osm2pgsql-1.4.1+ds/debian/patches/0001-Bug-fix-Remove-schema-name-from-CREATE-INDEX.patch
---
osm2pgsql-1.4.1+ds/debian/patches/0001-Bug-fix-Remove-schema-name-from-CREATE-INDEX.patch
1970-01-01 01:00:00.0 +0100
+++
osm2pgsql-1.4.1+ds/debian/patches/0001-Bug-fix-Remove-schema-name-from-CREATE-INDEX.patch
2021-04-07 15:56:19.0 +0200
@@ -0,0 +1,21 @@
+Description: Bug fix: Remove schema name from CREATE INDEX
+ Indexes are always created in the same schema as the table.
+Author: Jochen Topf
+Origin: https://github.com/openstreetmap/osm2pgsql/issues/1436
+Bug: https://github.com/openstreetmap/osm2pgsql/issues/1447
+
+--- a/src/middle-pgsql.cpp
b/src/middle-pgsql.cpp
+@@ -714,9 +714,9 @@ static table_sql sql_for_ways(bool has_b
+ " SELECT ARRAY(SELECT DISTINCT"
+ "unnest($1) >> {way_node_index_id_
Processed: Re: Bug#985958: [pre-approval] unblock: spip/3.2.11-2
Processing control commands: > tags -1 -moreinfo Bug #985958 [release.debian.org] [pre-approval] unblock: spip/3.2.11-2 Removed tag(s) moreinfo. -- 985958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985958 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#985958: [pre-approval] unblock: spip/3.2.11-2
Control: tags -1 -moreinfo Hi Paul, Thank you for your reply. Le 02/04/2021 à 16:41, Paul Gevers a écrit : On 26-03-2021 20:53, David Prévot wrote: Please unblock package spip This package does have a bit of a track record for security issues. Indeed. Since 3.3 will soon be released, the 3.2 branch (as currently in testing) should mostly only receive security updates starting from now (and as you already pointed out, it probably will rather sooner than later). Updating SPIP to 3.2.11 in Bullseye should make our lives less sad during the Bullseye lifetime, by allowing us to (hopefully) simply cherry-pick further security fixes (rather than backporting them due to changes between 3.2.10 and 3.2.11). [ Reason ] Upstream just released a new minor version to improve PHP 7.4 compat (latest version already improved PHP 7.3 compat). Since Bullseye ship with PHP 7.4, including those fixes should avoid future issues (I had to backport a PHP 7.3 compatibility issue with a buster-security upload already to fix a serious issue with plugins handling). If I read the upstream CHANGELOG correctly, it seems that this was all put together in a short time (days). Indeed, they finally realized that compatibility with current PHP version is useful (I’ve tried pushing for a while, but was not very successful). Are you aware of any tests in the package (I didn't spot them)? Does upstream have any testing infra? Nothing I’m aware of, unfortunately. On the other hand, this version has been released upstream more than two weeks ago and I’m not aware of any reported regression. I'm seriously doubting if we'd not introduce more issues than we solve here. I understand your concern, but SPIP 3.2.10, currently in Bullseye, is known to not be fully compatible with PHP 7.4, also in Bullseye. [ Impact ] On top of fixing possible problems, this update avoids filling the web server error.log due to multiple warnings and deprecation notices. Ack. Are those fixes cherry-pickable? That’s the main purpose of all the changes from 3.2.10 to 3.2.11 actually. [ Tests ] I only tested the package manually, but I’m keeping an eye on upstream issues that may arise about this new release. See above. This doesn't sound great. I understand, the timing of this release sucks, and I’ll trust the judgment of the release team. Regards David
Re: Finding a tentative bullseye release date
Hi,
Holger Wansing wrote (Sat, 10 Apr 2021 18:14:36 +0200):
> That's not just my opinion, but sort of consensus of the involved people.
> Going through the above mentioned thread shows that.
> There are also alternatives mentioned, but they all have their disadvantages,
> that's why the consensus.
May I submit a patch for this? (attached)
Holger
--
Holger Wansing
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
diff --git a/debian/changelog b/debian/changelog
index c1598e53..257aaf1e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,36 +1,46 @@
tasksel (3.66) UNRELEASED; urgency=medium
[ Shengjing Zhu ]
* Switch to fcitx5 for Simplified and Traditional Chinese desktop.
Fcitx5 works for Wayland. (Closes: #983704)
+ [ Holger Wansing]
+ * GNOME now depends on ibus. For some languages, there are additional
+packages needed, to make ibus work. Adding them for Amharic, Simplified
+chinese, Traditional chinese, Japanese, Kannada, Malayalam and Telugu.
+This requites new task-*-gnome-desktop packages to be added for Amharic,
+Simplified chinese, Traditional chinese, and Kannada.
+Thanks to Shengjing Zhu for working out the circumstances.
+ * ibus does not have default configurations for all languages, so force
+to create one via gnome-initial-setup for all the languages using ibus.
+
-- Holger Wansing Sat, 20 Mar 2021 16:22:17 +0800
tasksel (3.65) unstable; urgency=medium
* Team upload.
[ HIGUCHI Daisuke ]
* tasksel-japanese-desktop: prefer uim-mozc over uim-anthy (Closes: #982175)
[ Holger Wansing ]
* Re-add manpages-it to task-italian task (package is again available in
unstable/testing). Closes: #982043.
* Add manpages translations from newly introduced manpages-l10n package
(manpages-pt-br, manpages-nl, manpages-mk, manpages-ro, manpages-es)
to the respective language tasks (see #982043).
* Re-add synaptic to gnome desktop tasks. Closes: #983074
* Remove scim-qt-immodule from task-chinese-t-kde-desktop, since it's no
longer in the archive.
[ YOSHINO Yoshihito ]
* Let gnome-flashback-desktop task in Japanese pull
task-japanese-gnome-desktop. Closes: #983688
-- Holger Wansing Sat, 13 Mar 2021 16:26:46 +0100
tasksel (3.64) unstable; urgency=medium
* Team upload.
[ Holger Wansing ]
diff --git a/debian/control b/debian/control
index 30feb782..b4f39cd8 100644
--- a/debian/control
+++ b/debian/control
@@ -412,60 +412,70 @@ Architecture: all
Description: Albanian desktop
This task localises the desktop in Albanian.
Depends: ${misc:Depends},
Recommends:
firefox-esr-l10n-sq | firefox-l10n-sq,
myspell-sq,
Package: task-amharic
Architecture: all
Description: Amharic environment
This task installs programs, data files, fonts, and
documentation that makes it easier for Amharic speakers
to use Debian.
Depends: ${misc:Depends},
Recommends:
aspell-am
Package: task-amharic-desktop
Architecture: all
Description: Amharic desktop
This task localises the desktop in Amharic.
Depends: ${misc:Depends}
Recommends:
fonts-sil-abyssinica,
fcitx,
fcitx-table-amharic,
fcitx-frontend-gtk2,
fcitx-frontend-gtk3,
fcitx-config-gtk
+Package: task-amharic-gnome-desktop
+Architecture: all
+Description: Amharic GNOME desktop
+ This task localises the GNOME desktop in Amharic.
+Depends: ${misc:Depends}
+Recommends:
+ ibus-m17n,
+# ibus doesn't have a default config for all languages, so force creation
+ gnome-initial-setup
+
Package: task-amharic-kde-desktop
Architecture: all
Description: Amharic KDE Plasma desktop
This task localises the KDE Plasma desktop in Amharic.
Depends: ${misc:Depends},
Recommends:
fcitx-frontend-qt5,
kde-config-fcitx
Package: task-arabic
Architecture: all
Description: Arabic environment
This task installs programs, data files, fonts, and
documentation that makes it easier for Arabic speakers
to use Debian.
Depends: ${misc:Depends},
Recommends:
fonts-arabeyes,
aspell-ar,
aspell-ar-large,
itools
Package: task-arabic-desktop
Architecture: all
Description: Arabic desktop
This task localises the desktop in Arabic.
Depends: ${misc:Depends},
Recommends:
fonts-kacst,
fonts-farsiweb,
@@ -724,103 +734,123 @@ Recommends:
opencc,
zhcon,
manpages-zh,
Package: task-chinese-s-desktop
Architecture: all
Description: Simplified Chinese desktop
This task localises the desktop in Simplified Chinese.
Depends: ${misc:Depends},
Recommends:
# Input method stuff
im-config,
fcitx5,
fcitx5-chinese-addons,
# Fonts
fonts-noto,
fonts-noto-cjk,
# Software help and localization
libreoffice-l10n-zh-cn,
libreoffice-help-zh-cn,
firefox-esr-l10n-zh-cn | firefox-l10n-zh-cn,
# Dictionary
goldendict,
# poppler-data is needed to display
# Chinese on poppler applications.
poppler-data
Suggests:
fonts-arphic-ukai,
fonts-arphic-uming
+Package: task-chinese-s-gnome
Bug#986311: marked as done (unblock: debian-cloud-images/0.0.4)
Hi Ivo On Sun, Apr 11, 2021 at 12:39:05PM +, Debian Bug Tracking System wrote: > On Sat, Apr 03, 2021 at 09:29:03PM +0200, Paul Gevers wrote: > > What do you mean with "it's too late for that"? We *could* (not saying > > we should) drop the package. > I added a hint to remove the package. No thanks to you for dropping the key package that holds the cloud images ready for release. Now, what do you propose to fix this? Bastian -- Knowledge, sir, should be free to all! -- Harry Mudd, "I, Mudd", stardate 4513.3
Bug#986869: unblock: vala/0.48.17-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: ric...@ubuntu.com
Please unblock package vala
Vala 0.48.17
* Regression and bug fixes:
- codegen:
+ Don't free temp-var for element-access to array with boxed structs
[#1174]
+ Don't free unowned heap allocated struct
* Bindings:
- glib-2.0: Add simple_generics attribute to GenericArray.find_custom()
Vala 0.48.16
* Various improvements and bug fixes:
- codegen:
+ Improve handling of ellipsis parameter in get_ccode_name()
+ Fix default value of get_ccode_destroy_notify_pos()
+ Don't override valid target/destroy of previous lambda argument [#59]
+ Don't call *_instance_init() in compact class chainup
- vala: Mark tranformed static member-access as qualified [#270]
- girwriter: namespace expects "c:symbol-prefixes" attribute [#1038]
- girwriter: Don't use instance-parameter inside callback [#1167]
- girparser,libvaladoc/girimporter: Don't guess length of xml header, iterate
forward to
- libvaladoc/girimporter: parse_constant() use "c:identifier" attribute first
* Bindings:
- rest-0.7: Fix OAuthProxyAuthCallback binding
- gtk+-3.0: Fix ModuleInitFunc binding
- gio-2.0: Fix TlsPassword.get_value() binding
- Fix several bindings which lead to invalid code by using them in:
javascriptcoregtk-4.0, libusb, libusb-1.0, pixman-1,
webkit2gtk-web-extension-4.0, x11, zlib,
[ Reason ]
Vala 0.48.x series is a Long-Term support version and receives important bug
fixes and binding fixes.
[ Impact ]
The packages fixes two upstream regressions introduced with 0.48.14 and 0.48.15
pygobject regression by new instance-parameter gir output
https://gitlab.gnome.org/GNOME/vala/-/issues/1167
using (!) when dereferencing item in array of nullable structs frees item,
leading to double free
https://gitlab.gnome.org/GNOME/vala/-/issues/1174
[ Tests ]
The vala 0.48.x series is constantly used by current package set of Debian
testing.
The upstream test suite is extended with every release.
http://ci.vala-project.org:8010/builders/vala-0.48/builds/43
http://ci.vala-project.org:8010/builders/vala-0.48/builds/45
[ Risks ]
Vala is a compiler and affects every reverse-dependency.
[ Checklist ]
[X] all changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] There are no packaging changes other than the changelog itself
[X] A debdiff is not applicable due to generated C files
[ Other info ]
Upstream between 0.48.15 and 0.48.17
https://gitlab.gnome.org/GNOME/vala/-/compare/10166000cbf8963cfebae5e15fa0f13b15791308...7a59191b7fc5d4c7b77f42ab0e7806011a5c71dd
unblock vala/0.48.17-1
diff --git a/NEWS b/NEWS
index e78d744d0..4bf72f071 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,26 @@
+Vala 0.48.16
+
+ * Various improvements and bug fixes:
+ - codegen:
++ Improve handling of ellipsis parameter in get_ccode_name()
++ Fix default value of get_ccode_destroy_notify_pos()
++ Don't override valid target/destroy of previous lambda argument [#59]
++ Don't call *_instance_init() in compact class chainup
+ - vala: Mark tranformed static member-access as qualified [#270]
+ - girwriter: namespace expects "c:symbol-prefixes" attribute [#1038]
+ - girwriter: Don't use instance-parameter inside callback [#1167]
+ - girparser,libvaladoc/girimporter: Don't guess length of xml header, iterate
+forward to
+ - libvaladoc/girimporter: parse_constant() use "c:identifier" attribute first
+
+ * Bindings:
+ - rest-0.7: Fix OAuthProxyAuthCallback binding
+ - gtk+-3.0: Fix ModuleInitFunc binding
+ - gio-2.0: Fix TlsPassword.get_value() binding
+ - Fix several bindings which lead to invalid code by using them in:
+javascriptcoregtk-4.0, libusb, libusb-1.0, pixman-1,
+webkit2gtk-web-extension-4.0, x11, zlib,
+
Vala 0.48.15
* Various improvements and bug fixes:
diff --git a/codegen/valaccode.vala b/codegen/valaccode.vala
index 7671b2c50..9b1da33f7 100644
--- a/codegen/valaccode.vala
+++ b/codegen/valaccode.vala
@@ -365,12 +365,7 @@ namespace Vala {
if (a != null && a.has_argument ("destroy_notify_pos")) {
return a.get_double ("destroy_notify_pos");
}
- if (node is Parameter) {
- unowned Parameter param = (Parameter) node;
- return get_ccode_pos (param) + 0.1;
- } else {
- return -3;
- }
+ return get_ccode_delegate_target_pos (node) + 0.01;
}
public static bool get_ccode_delegate_target (CodeNode node) {
diff --git a/codegen/valaccodearraymodule.vala
b/codegen/valaccodearraymodule.vala
index 851778171..9bfe9db59 100644
--- a/codegen/valaccodearraymodule.vala
+++ b/codegen/valaccodearraymodule.vala
@@ -606,7 +606,7 @@ public class Vala.CCodeArrayModule : CCodeMe
Bug#986870: unblock: lrzip/0.641-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hi RMs,
While the current lrzip version in Bullseye (0.640-1) works, with some
100 MB+ sized files it has a big regression. For example a user
reported [1] the compression ratio dropped from 92% to 60%.
[ Reason ]
Fixes a big regression.
[ Impact ]
Poor compression ratio with large files.
[ Tests ]
Mostly upstream tests.
[ Risks ]
Low.
[ 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 ]
While not being an RC bug in Debian, upstream (Con Kolivas) call it
'critical bugfix' and ask for an update in Bullseye [2]. Original
fixing commit [3].
unblock lrzip/0.641-1
Thanks for consideration,
Laszlo/GCS
[1] https://bugs.debian.org/986396#5
[2] https://bugs.debian.org/986396#10
[3]
https://github.com/ckolivas/lrzip/commit/042eb57e034c05250a4ca8007f5cebee4068ec32
diff -Nru lrzip-0.640/configure.ac lrzip-0.641/configure.ac
--- lrzip-0.640/configure.ac 2021-02-16 05:53:30.0 +0100
+++ lrzip-0.641/configure.ac 2021-03-06 00:20:42.0 +0100
@@ -2,7 +2,7 @@
##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
m4_define([v_maj], [0])
m4_define([v_min], [6])
-m4_define([v_mic], [40])
+m4_define([v_mic], [41])
##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
m4_define([v_v], m4_join([], v_min, v_mic))
m4_define([v_ver], [v_maj.v_v])
diff -Nru lrzip-0.640/debian/changelog lrzip-0.641/debian/changelog
--- lrzip-0.640/debian/changelog 2021-02-19 17:38:21.0 +0100
+++ lrzip-0.641/debian/changelog 2021-04-09 17:50:44.0 +0200
@@ -1,3 +1,10 @@
+lrzip (0.641-1) unstable; urgency=medium
+
+ * New upstream release:
+- fix low compression ratio with large files (closes: #986396).
+
+ -- Laszlo Boszormenyi (GCS) Fri, 09 Apr 2021 17:50:44 +0200
+
lrzip (0.640-1) unstable; urgency=medium
* New upstream release:
diff -Nru lrzip-0.640/stream.c lrzip-0.641/stream.c
--- lrzip-0.640/stream.c 2021-02-16 05:53:30.0 +0100
+++ lrzip-0.641/stream.c 2021-03-06 00:20:42.0 +0100
@@ -1882,11 +1882,8 @@
so do not compress any block that is incompressible by lz4. */
static int lz4_compresses(rzip_control *control, uchar *s_buf, i64 s_len)
{
- int in_len, test_len = s_len, save_len = s_len;
- int dlen;
+ int dlen, test_len;
char *c_buf = NULL, *test_buf = (char *)s_buf;
- /* set minimum buffer test size based on the length of the test stream */
- int buftest_size = (test_len > 5 * STREAM_BUFSIZE ? STREAM_BUFSIZE : STREAM_BUFSIZE / 4096);
int ret = 0;
int workcounter = 0; /* count # of passes */
int best_dlen = INT_MAX; /* save best compression estimate */
@@ -1894,40 +1891,37 @@
if (!LZ4_TEST)
return 1;
- in_len = MIN(test_len, buftest_size);
- dlen = STREAM_BUFSIZE + STREAM_BUFSIZE / 16 + 64 + 3;
-
+ dlen = MIN(s_len, STREAM_BUFSIZE);
+ test_len = MIN(dlen, STREAM_BUFSIZE >> 8);
c_buf = malloc(dlen);
if (unlikely(!c_buf))
fatal_return(("Unable to allocate c_buf in lz4_compresses\n"), 0);
/* Test progressively larger blocks at a time and as soon as anything
compressible is found, jump out as a success */
- while (test_len > 0) {
+ do {
int lz4_ret;
workcounter++;
lz4_ret = LZ4_compress_default((const char *)test_buf, c_buf, test_len, dlen);
- if (!lz4_ret) // Bigger than dlen, no point going further
- break;
+ if (!lz4_ret) // Bigger than dlen
+ lz4_ret = test_len;
if (lz4_ret < best_dlen)
best_dlen = lz4_ret;
if (lz4_ret < test_len) {
ret = 1;
break;
}
- /* expand and move buffer */
- test_len -= in_len;
- if (test_len) {
- test_buf += (ptrdiff_t)in_len;
- if (buftest_size < STREAM_BUFSIZE)
-buftest_size <<= 1;
- in_len = MIN(test_len, buftest_size);
- }
+ /* expand test length */
+ test_len <<= 1;
+ } while (test_len <= dlen);
+
+ if (!ret)
+ print_maxverbose("lz4 testing FAILED for chunk %ld. %d Passes\n", workcounter);
+ else {
+ print_maxverbose("lz4 testing OK for chunk %ld. Compressed size = %5.2F%% of chunk, %d Passes\n",
+s_len, 100 * ((double) best_dlen / (double) test_len), workcounter);
}
- print_maxverbose("lz4 testing %s for chunk %ld. Compressed size = %5.2F%% of chunk, %d Passes\n",
- (ret == 0? "FAILED" : "OK"), save_len,
- 100 * ((double) best_dlen / (double) in_len), workcounter);
dealloc(c_buf);
diff -Nru lrzip-0.640/WHATS-NEW lrzip-0.641/WHATS-NEW
--- lrzip-0.640/WHATS-NEW 2021-02-16 05:53:30.0 +0100
+++ lrzip-0.641/WHATS-NEW 2021-03-06 00:20:42.0 +0100
@@ -1,6 +1,11 @@
Changelog will be moved to git entirely from this point forward.
-lrzip-0.650
+lrzip-0.641
+
+Critical bugfix for broken lz4 testing which would prevent secondary
+compression from being enabled.
+
+lrzip-0.640
Numerous bugfixes and build fixes.
lz4 now used for compressibility testing (only) making lz4
