Processed: bullseye-pu: package node-webpack/4.43.0-6+deb11u1
Processing control commands: > affects -1 + src:node-webpack Bug #1032921 [release.debian.org] bullseye-pu: package node-webpack/4.43.0-6+deb11u1 Added indication that 1032921 affects src:node-webpack -- 1032921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032921 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032921: bullseye-pu: package node-webpack/4.43.0-6+deb11u1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: node-webp...@packages.debian.org
Control: affects -1 + src:node-webpack
[ Reason ]
node-webpack is vulnerable to cross-realm object access
(#1032904, CVE-2023-28154)
[ Impact ]
Medium security issue
[ Tests ]
Sadly webpack has no test in Bullseye
[ Risks ]
Low risk, patch is trivial
[ Checklist ]
[X] *all* changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in (old)stable
[X] the issue is verified as fixed in unstable
[ Changes ]
Better isolation in distinct Node.js vm for each object to parse before
setting keys in vulnerable object
Cheers,
Yadd
diff --git a/debian/changelog b/debian/changelog
index 4bbdc0d3..dcd60ee0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+node-webpack (4.43.0-6+deb11u1) bullseye; urgency=medium
+
+ * Team upload
+ * Avoid cross-realm object access (Closes: #1032904, CVE-2023-28154)
+
+ -- Yadd Tue, 14 Mar 2023 07:43:57 +0400
+
node-webpack (4.43.0-6) unstable; urgency=medium
* Team upload
diff --git a/debian/patches/CVE-2023-28154.patch
b/debian/patches/CVE-2023-28154.patch
new file mode 100644
index ..c239d37b
--- /dev/null
+++ b/debian/patches/CVE-2023-28154.patch
@@ -0,0 +1,72 @@
+Description: avoid cross-realm object access
+Author: Jack Works
+Bug: https://security-tracker.debian.org/tracker/CVE-2023-28154
+Bug-Debian: https://bugs.debian.org/1032904
+Forwarded: not-needed
+Applied-Upstream: 5.76.0, commit:4b4ca3bb
+Reviewed-By: Yadd
+Last-Update: 2023-03-14
+
+--- a/lib/Parser.js
b/lib/Parser.js
+@@ -2335,11 +2335,20 @@
+ if (value && webpackCommentRegExp.test(value)) {
+ // try compile only if webpack options comment
is present
+ try {
+- const val =
vm.runInNewContext(`(function(){return {${value}};})()`);
+- Object.assign(options, val);
++ for (let [key, val] of Object.entries(
++
vm.runInNewContext(`(function(){return {${value}};})()`)
++ )) {
++ if (typeof val === "object" &&
val !== null) {
++ if
(val.constructor.name === "RegExp") val = new RegExp(val);
++ else val =
JSON.parse(JSON.stringify(val));
++ }
++ options[key] = val;
++ }
+ } catch (e) {
+- e.comment = comment;
+- errors.push(e);
++ const newErr = new
Error(String(e.message));
++ newErr.stack = String(e.stack);
++ Object.assign(newErr, { comment });
++ errors.push(newErr);
+ }
+ }
+ }
+--- a/lib/dependencies/ImportParserPlugin.js
b/lib/dependencies/ImportParserPlugin.js
+@@ -127,7 +127,7 @@
+ if (importOptions.webpackInclude !== undefined)
{
+ if (
+ !importOptions.webpackInclude ||
+-
importOptions.webpackInclude.constructor.name !== "RegExp"
++ !(importOptions.webpackInclude
instanceof RegExp)
+ ) {
+
parser.state.module.warnings.push(
+ new
UnsupportedFeatureWarning(
+@@ -137,13 +137,13 @@
+ )
+ );
+ } else {
+- include = new
RegExp(importOptions.webpackInclude);
++ include =
importOptions.webpackInclude;
+ }
+ }
+ if (importOptions.webpackExclude !== undefined)
{
+ if (
+ !importOptions.webpackExclude ||
+-
importOptions.webpackExclude.constructor.name !== "RegExp"
++ !(importOptions.webpackExclude
instanceof RegExp)
+
Bug#1032913: unblock: mutter/43.3-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: mut...@packages.debian.org Control: affects -1 + src:mutter Please unblock package mutter [ Reason ] Fix X11 focus regressions (#1031945, possibly others) [ Impact ] If not accepted, for users of "GNOME on Xorg", switching keyboard layout or input method with Super+Space causes windows to lose focus (#1031945). The default GNOME session (using Wayland) is unaffected. There might be additional focus weirdness fixed by this. I had hoped that this would fix the related bug #1032388, but in fact that doesn't seem to have been the case (and I've opened a separate upstream bug for that). Additionally, this version expands build-time test coverage, by fixing a test script that failed on non-merged-/usr systems instead of disabling it, and updates some patches that were applied upstream to incorporate minor adjustments made by the upstream maintainer. [ Tests ] autopkgtests pass, and the proposed package has been in unstable for a week without apparent regressions. [ Risks ] Highly visible package (part of our default desktop environment), but the changes are isolated and have been taken from an upstream change in the GNOME 44 branch, confirmed to resolve similar issues. There have been no related fixes in the GNOME 44 branch (currently in upstream freeze) since then; if there are, they'll be backported to the GNOME 43 branch, either by upstream or in Debian. [ 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 current changelog claims to have fixed #1032388, which was subsequently reopened. I can do a new upload with the changelog clarified if the release team would prefer that, but it would need some more age-days. unblock mutter/43.3-5 diffstat for mutter-43.3 mutter-43.3 .gitlab-ci/checkout-gnome-shell.sh|2 .gitlab-ci/download-coverity-tarball.sh |2 debian/changelog | 19 ++ debian/patches/Revert-x11-Do-not-move-X11-input-focus-during-grabs.patch | 87 ++ debian/patches/Revert-x11-events-Do-not-update-focus-XWindow-during-grab.patch| 36 debian/patches/color-device-Don-t-close-lcms-profile-on-error-from-cd_ic.patch| 13 + debian/patches/color-device-Make-sure-lcms_context-is-not-NULL.patch | 15 + debian/patches/core-Avoid-focusing-windows-on-map-during-grabs.patch | 35 debian/patches/debian/Mark-xwayland-test-case-as-known-to-be-flaky-on-32-bit-AR.patch |2 debian/patches/debian/tests-Disable-restore-size-test.patch |2 debian/patches/debian/tests-Tag-unstable-tests-as-flaky.patch |2 debian/patches/series |8 debian/patches/tests-Disable-broken-test.patch| 50 - debian/patches/tests-Use-a-more-interoperable-path-to-bash.patch | 70 debian/patches/x11-Ignore-_NET_ACTIVE_WINDOW-client-messages-while-grabb.patch| 45 + src/backends/meta-color-device.c |2 src/core/events.c |4 src/core/window.c |9 + src/tests/kvm/run-kvm-test.sh |2 src/tests/kvm/virtme-run.sh |2 src/tests/meson.build | 28 +-- src/tests/x11-test.sh |2 src/x11/events.c |6 src/x11/meta-x11-display-private.h|2 src/x11/meta-x11-display.c| 20 -- src/x11/window-x11.c |3 26 files changed, 351 insertions(+), 117 deletions(-) diff -Nru mutter-43.3/debian/changelog mutter-43.3/debian/changelog --- mutter-43.3/debian/changelog 2023-03-02 08:50:50.0 + +++ mutter-43.3/debian/changelog 2023-03-06 11:35:23.0 + @@ -1,3 +1,22 @@ +mutter (43.3-5) unstable; urgency=medium + + * Team upload + * d/patches: Use the same order in which patches were applied upstream + * d/p/color-device-Make-sure-lcms_context-is-not-NULL.patch, +
Processed: unblock: mutter/43.3-5
Processing control commands: > affects -1 + src:mutter Bug #1032913 [release.debian.org] unblock: mutter/43.3-5 Added indication that 1032913 affects src:mutter -- 1032913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Processed: reassign 1031259 to release.debian.org
Processing control commands: > reassign -1 ddcutil 1.4.1-1 Bug #1031259 [release.debian.org] ddcutil requires module i2c-dev Bug reassigned from package 'release.debian.org' to 'ddcutil'. Ignoring request to alter found versions of bug #1031259 to the same values previously set Ignoring request to alter fixed versions of bug #1031259 to the same values previously set Bug #1031259 [ddcutil] ddcutil requires module i2c-dev Marked as found in versions ddcutil/1.4.1-1. -- 1031259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031259: Processed: reassign 1031259 to release.debian.org
Control: reassign -1 ddcutil 1.4.1-1 Hi Sanford On 2023-03-13 08:12:04 +, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > > reassign 1031259 release.debian.org #1032614 is already assigned to release.debian.org to discuss the pre-approval. Having a second bug assigned to release.debian.org for the same issue makes no sense. Please do not reassign back to release.debian.org Cheers -- Sebastian Ramacher
Bug#1032862: unblock: golang-github-tidwall-gjson/1.14.4-2 (pre-approval)
Control: tags -1 confirmed
On 2023-03-13 00:40:23 +0100, Cyril Brulebois wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: debian...@lists.debian.org
>
> Hi,
>
> Please consider ACKing a golang-github-tidwall-gjson upload catching up
> with newer upstream releases.
>
> [ Reason ]
> The golang-github-tidwall-gjson package currently in testing and
> unstable suffers from at least two CVEs (#1000225, #1011616).
>
> Currently, we have a 1.6.7 version, those bugs are supposed to be fixed
> in 1.9.x, and upstream is at 1.14.4…
>
> This library is about parsing JSON, is basically one big Go file (along
> with another one for the tests).
>
> Since that's about parsing things, I suppose it wouldn't be trivial to
> backport the security fixes from 1.9.2 and 1.9.3 without understanding
> how parsing works, and why it was buggy in 1.6.7. Shipping the latest
> 1.9.x would probably be safer. But then, if we're going to have a bump
> in upstream releases, it seemed (at least to Thorsten Alteholz on the
> debian-go@ list and to me) that considering the latest would make most
> sense. We would get those fixes, possible other ones, and that would
> minimize the delta whenever other security fixes come up.
>
> The reverse dependencies are somewhat limited:
> - dak lists 3 packages via Depends;
> - dak lists 5 packages via Build-Depends;
> - ratt finds 14 packages when it's time to rebuild all the things.
>
> [ Impact ]
> I'm not sure I would be able to backport security fixes (at all, or
> properly), and failing to get a fixed package into testing might get a
> bunch of packages kicked out. This includes crowdsec, which is my
> primary concern when it comes to Go packages.
>
> [ Tests ]
> ratt has been used to check that all 14 identified packages still build
> fine. Those are Go packages, so they usually come with a test suite (but
> I must admit I didn't check each one individually).
>
> Additionally, I've uploaded 1.14.4-1 to experimental to benefit from the
> automated autopkgtest runs (for Go packages that means building/testing
> on the considered arch), and those haven't uncovered any issues on any
> of the ci.debian.net archs, which is an extra reassurance compared to my
> initial build tests via ratt, only on amd64.
>
> [ Risks ]
> No regressions have been spotted thus far, either in the package or its
> reverse dependencies, and I'm signing up for investigating anything that
> might come up as a side effect of this update.
Thanks for performing all the tests and confirming that this should be a
low risk upload. It's still a big diff, but given since this a library
for parsing potentially untrusted input, let's take the new upstream
version with the CVE fixes.
So: please go ahead with the upload.
> [ 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 ]
> This is a Go package, so reverse dependencies will need to be rebuilt
> against the updated code. That being said, with the binNMU rounds
> happening to avoid keeping too many `Extra-Source-Only: yes` packages
> in testing, that might just happen automatically without requiring
> manual scheduling.
Indeed, it will be rebuilt on the next round of outdated ESO builds.
Cheers
> unblock golang-github-tidwall-gjson/1.14.4-2
>
>
> Cheers,
> --
> Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/
> diff --git a/README.md b/README.md
> index 8553273..c8db11f 100644
> --- a/README.md
> +++ b/README.md
> @@ -4,7 +4,9 @@
> width="240" height="78" border="0" alt="GJSON">
>
> https://godoc.org/github.com/tidwall/gjson;> src="https://img.shields.io/badge/api-reference-blue.svg?style=flat-square;
> alt="GoDoc">
> -http://tidwall.com/gjson-play;> src="https://img.shields.io/badge/%F0%9F%8F%90-playground-9900cc.svg?style=flat-square;
> alt="GJSON Playground">
> +https://tidwall.com/gjson-play;> src="https://img.shields.io/badge/%F0%9F%8F%90-playground-9900cc.svg?style=flat-square;
> alt="GJSON Playground">
> + src="https://img.shields.io/badge/{}-syntax-33aa33.svg?style=flat-square;
> alt="GJSON Syntax">
> +
>
>
> get json values quickly
> @@ -14,6 +16,10 @@ It has features such as [one line
> retrieval](#get-a-value), [dot notation paths]
>
> Also check out [SJSON](https://github.com/tidwall/sjson) for modifying json,
> and the [JJ](https://github.com/tidwall/jj) command line tool.
>
> +This README is a quick overview of how to use GJSON, for more information
> check out [GJSON Syntax](SYNTAX.md).
> +
> +GJSON is also available for [Python](https://github.com/volans-/gjson-py)
> and [Rust](https://github.com/tidwall/gjson.rs)
> +
> Getting Started
> ===
>
> @@ -123,11 +129,12 @@ nil, for JSON null
> To directly access the value:
>
> ```go
> -result.Type// can
Processed: Re: Bug#1032862: unblock: golang-github-tidwall-gjson/1.14.4-2 (pre-approval)
Processing control commands: > tags -1 confirmed Bug #1032862 [release.debian.org] unblock: golang-github-tidwall-gjson/1.14.4-2 (pre-approval) Added tag(s) confirmed. -- 1032862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032903: marked as done (unblock: liferea/1.14.1-1)
Your message dated Mon, 13 Mar 2023 21:18:22 + with message-id and subject line unblock liferea has caused the Debian Bug report #1032903, regarding unblock: liferea/1.14.1-1 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.) -- 1032903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032903 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 X-Debbugs-Cc: life...@packages.debian.org Control: affects -1 + src:liferea Please unblock package liferea [ Reason ] A CVE was discovered in liferea and upstream quickly released a new version including the fix. The new version also fixes a crash on double free. Unfortunately it also included one more less important improvement and an updated translation. Considering my options, I decided it was best to upload the new version instead of only fixing the CVE. https://security-tracker.debian.org/tracker/CVE-2023-1350 [ Impact ] The CVE is about a Remote Code Excecution of RSS feed information when the user has opted-in to "Extract full content from HTML5 and Google AMP". I believe that's pretty bad, but luckily it's not the default. [ Tests ] liferea doesn't have autopkgtests (yet), but I do activate the upstream tests during build. Unfortunately, that currently fails (because liferea isn't installed during build and if that's worked around something fails due to being root; sorry, haven't fixed that yet), but I ran the tests locally and then all regular tests pass. The memtest fails in the same way as before. I also eat my own dogfood as I'm a user of liferea and have the binaries installed since I built them. [ Risks ] In the end, the changes are a bit more than trivial, but the delta in this release is targetted to specific issues. I have a good relation with upstream and he even supported me in the discussion with the security team. Unfortunately, liferea isn't a leaf package as the bfh-desktop (new in bookworm) and progress-linux-desktop (already in bullseye) depend on it. [ 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 ] I recommend viewing the debdiff with the following filter to ignore upstream workflow items, the translation update and additional test cases added for the purpose of testing the fix: filterdiff -x '*/.gitignore' -x '*/.github/workflows/cb.yml' -x '*/po/fr.po' -x '*/src/tests' liferea_1.14.1-1.debdiff unblock liferea/1.14.1-1 Paul diff -Nru liferea-1.14.0/ChangeLog liferea-1.14.1/ChangeLog --- liferea-1.14.0/ChangeLog2023-01-10 21:12:42.0 +0100 +++ liferea-1.14.1/ChangeLog2023-03-12 21:00:51.0 +0100 @@ -1,3 +1,17 @@ +2023-03-12 Lars Windolf + + Version 1.14.1 + + * Fixes CVE-2023-1350: RCE vulnerability on feed enrichment + (patch by Alexander Erwin Ittner) + + * Fixes #1200: Crash on double free + (mozbugbox) + + * Improve #1192 be reordering widget creation order + (Lars Windolf) + + 2023-01-10 Lars Windolf Version 1.14.0 diff -Nru liferea-1.14.0/configure.ac liferea-1.14.1/configure.ac --- liferea-1.14.0/configure.ac 2023-01-10 21:12:42.0 +0100 +++ liferea-1.14.1/configure.ac 2023-03-12 21:00:51.0 +0100 @@ -1,6 +1,6 @@ dnl Process this file with autoconf to produce a configure script. -AC_INIT([liferea],[1.14.0],[liferea-de...@lists.sourceforge.net]) +AC_INIT([liferea],[1.14.1],[liferea-de...@lists.sourceforge.net]) AC_CANONICAL_HOST AC_CONFIG_SRCDIR([src/feedlist.c]) diff -Nru liferea-1.14.0/debian/changelog liferea-1.14.1/debian/changelog --- liferea-1.14.0/debian/changelog 2023-01-15 21:14:44.0 +0100 +++ liferea-1.14.1/debian/changelog 2023-03-12 21:32:33.0 +0100 @@ -1,3 +1,12 @@ +liferea (1.14.1-1) unstable; urgency=medium + + * New upstream version 1.14.1 +Contains fix for CVE-2023-1350 which is a RCE when the option "Extract +full content from HTML5 and Google AMP" is enable on a feed (Closes: +#1032822) + + -- Paul Gevers Sun, 12 Mar 2023 21:32:33 +0100 + liferea (1.14.0-1) unstable; urgency=medium * New upstream version 1.14.0 diff -Nru liferea-1.14.0/.github/workflows/cb.yml liferea-1.14.1/.github/workflows/cb.yml --- liferea-1.14.0/.github/workflows/cb.yml 2023-01-10 21:12:42.0 +0100 +++ liferea-1.14.1/.github/workflows/cb.yml 2023-03-12 21:00:51.0 +0100 @@ -24,7 +24,7 @@ - run:
Bug#1032888: marked as done (unblock: pubpaste/0.8.3)
Your message dated Mon, 13 Mar 2023 21:16:30 +
with message-id
and subject line unblock pubpaste
has caused the Debian Bug report #1032888,
regarding unblock: pubpaste/0.8.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.)
--
1032888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032888
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
X-Debbugs-Cc: pubpa...@packages.debian.org
Control: affects -1 + src:pubpaste
Please unblock package pubpaste
[ Reason ]
There are two serious crashes in pubpaste in testing right now, which
I haven't reported myself but have fixed, as the upstream.
[ Impact ]
Worst case: program crashes when doing a screenshot. Best case, it
works, but fails to copy unicode from Firefox.
[ Tests ]
I use this code daily, in graphical and console environment.
[ Risks ]
It's a leaf package, low popcon, low impact on the rest of the
ecosystem, really a convenience for the poor users.
[ 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 ]
I must apologize for this: I uploaded the package before the hard
freeze and miscalculated the transition time. I was expecting 0.8.3 to
land in bookworm before the hard freeze.
To be more accurate, I had the understanding that the freeze applied
to packages uploaded to sid *after* the hard freeze start. Maybe that
was engrained in my brain from a previous policy that had changed
since?
In any case, sorry about this! I hope you're not too swamped by all
the unblock requests.
(And yes, this package should really have autopkgtests, I only have
myself to blame for that one too...)
If this fails to unblock, I think it might be preferable to maintain
this through backports and simply remove it from bookworm.
unblock pubpaste/0.8.3
diff -Nru pubpaste-0.8.1/debian/changelog pubpaste-0.8.3/debian/changelog
--- pubpaste-0.8.1/debian/changelog 2023-02-21 11:27:35.0 -0500
+++ pubpaste-0.8.3/debian/changelog 2023-03-09 12:29:54.0 -0500
@@ -1,3 +1,16 @@
+pubpaste (0.8.3) unstable; urgency=medium
+
+ * fix crash when uploading badly-encoded unicode
+ * support for Firefox in HTML pastes
+
+ -- Antoine Beaupré Thu, 09 Mar 2023 12:29:54 -0500
+
+pubpaste (0.8.2) unstable; urgency=high
+
+ * fix regression in screenshots introduced in 0.8.1
+
+ -- Antoine Beaupré Mon, 06 Mar 2023 14:12:11 -0500
+
pubpaste (0.8.1) unstable; urgency=medium
* fix another crash when running without GTK
diff -Nru pubpaste-0.8.1/pubpaste.py pubpaste-0.8.3/pubpaste.py
--- pubpaste-0.8.1/pubpaste.py 2023-02-21 11:27:35.0 -0500
+++ pubpaste-0.8.3/pubpaste.py 2023-03-09 12:29:54.0 -0500
@@ -48,6 +48,11 @@
Type,
TypeVar,
)
+
+try:
+from typing import TypeAlias
+except ImportError:
+from typing_extensions import TypeAlias # Python 3.9 or earlier
from urllib.parse import quote
import yaml
@@ -76,7 +81,8 @@
gi.require_version("Gtk", "3.0")
from gi.repository import GLib, Gtk, Gdk, GdkPixbuf # type: ignore
-from Gtk import MessageDialog # type: ignore
+
+MessageDialog = Gtk.MessageDialog
except (ImportError, ValueError):
# "ValueError('Namespace %s not available' % namespace)"
gi = None
@@ -84,6 +90,7 @@
class MessageDialog: # type: ignore
pass
+
__epilog__ = """ This program will upload the provided files on the internet
and
notify the user when completed. The resulting URL will also be copied
to the clipboard. Preprocessors can do fancy things before (only
@@ -583,7 +590,7 @@
"""
-class TimerWindow(MessageDialog): # type: ignore[misc]
+class TimerWindow(MessageDialog): # type: ignore[misc, valid-type]
"""This widget will show a timer and a spinner in a window for the
given delay, then close the dialog.
@@ -1072,6 +1079,9 @@
return datetime.now().strftime("%Y-%m-%d"), secrets.token_urlsafe()
+SupportedExtensions: TypeAlias = Literal["png", "jpg", "txt", "html"]
+
+
class BaseClipboard:
def __init__(self, selection: Literal["CLIPBOARD", "PRIMARY"]) -> None:
"""configure the clipboard, based on whether the clipboard is PRIMARY
@@ -1088,7 +1098,7 @@
def put_image(self, path: bytes) -> bool:
raise NotImplementedError()
-def get(self) -> Tuple[Optional[bytes], Optional[Literal["png", "jpg",
"txt"]]]:
+def get(self) -> Tuple[Optional[bytes],
Bug#1032901: marked as done (unblock: crystal/1.6.0+dfsg-3)
Your message dated Mon, 13 Mar 2023 21:15:38 + with message-id and subject line unblock crystal has caused the Debian Bug report #1032901, regarding unblock: crystal/1.6.0+dfsg-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.) -- 1032901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032901 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 X-Debbugs-Cc: crys...@packages.debian.org, d...@debian.org Control: affects -1 + src:crystal Please unblock package crystal [ Reason ] The new version will fix #1031812 (the package lacks some dependencies), and unmark it from autoremovals. [ Impact ] Crystal will be removed from testing due to autoremovals. [ Tests ] The package was manually tested in a new and clean debian installation to check that the package has now all the needed dependecies to work. [ Risks ] The change is trivial, it only implies adding some runtime dependencies. [ 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 package was upload some days before the hard freeze so it couldn't get migrated automatically. unblock crystal/1.6.0+dfsg-3 --- End Message --- --- Begin Message --- Unblocked.--- End Message ---
Bug#1032909: marked as done (unblock: aiomysql/0.1.1-2)
Your message dated Mon, 13 Mar 2023 21:13:48 + with message-id and subject line unblock aiomysql has caused the Debian Bug report #1032909, regarding unblock: aiomysql/0.1.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.) -- 1032909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032909 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 X-Debbugs-Cc: aiomy...@packages.debian.org Control: affects -1 + src:aiomysql Please unblock package aiomysql [ Reason ] aiomysql 0.1.1-1 in bookworm is affected by RC bug #1030464. [ Impact ] aiomysql will be removed from bookworm if the RC bug is not addressed, but it doesn't look like it will pull much reverse dependencies out of bookworm as well. Overall impact looks low. [ Tests ] I force ran the autodep8-python3 for aiomysql 0.1.1-2 in both unstable and testing context and it raised no obvious issues: autopkgtest [21:12:53]: test autodep8-python3: [--- Testing with python3.11: autopkgtest [21:12:53]: test autodep8-python3: ---] but not much more apart from that as I don't use the package myself. [ Risks ] The change is minimal, so the risk of introducing a breakage looks pretty low. [ Checklist ] [*] all changes are documented in the d/changelog [*] I reviewed all changes and I approve them [*] attach debdiff against the package in testing [ Other info ] There is a side change with the RC bug fix: a fix for ftbfs when rebuilding the pakage; the issue initially comes from upstream mixing up doc and unix style end-of-lines. If this is deemed inappropriate, I may upload a 0.1.1-3 without the file removal after the dh_auto_clean target. unblock aiomysql/0.1.1-2 Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/6, please excuse my verbosity. On air: Frost* - Milliontown diff -Nru aiomysql-0.1.1/debian/changelog aiomysql-0.1.1/debian/changelog --- aiomysql-0.1.1/debian/changelog 2022-11-05 19:56:23.0 +0100 +++ aiomysql-0.1.1/debian/changelog 2023-03-07 22:13:05.0 +0100 @@ -1,3 +1,15 @@ +aiomysql (0.1.1-2) unstable; urgency=medium + + * Team upload. + * d/control: cleanup aiomysql/_scm_version.py. +This allows the package to be rebuildable from a clean state after a +first build attempt. + * d/control: build depends on python3-setuptools-scm. +This fixes a failure to build from source. +Thanks to s3v (Closes: #1030464) + + -- Étienne Mollier Tue, 07 Mar 2023 22:13:05 +0100 + aiomysql (0.1.1-1) unstable; urgency=medium * New upstream release diff -Nru aiomysql-0.1.1/debian/control aiomysql-0.1.1/debian/control --- aiomysql-0.1.1/debian/control 2022-11-05 19:56:23.0 +0100 +++ aiomysql-0.1.1/debian/control 2023-03-07 21:46:52.0 +0100 @@ -8,6 +8,7 @@ python3-all, python3-setuptools, python3-pymysql, + python3-setuptools-scm, python3-sphinx , python3-sphinxcontrib-asyncio , python3-sphinx-rtd-theme , diff -Nru aiomysql-0.1.1/debian/rules aiomysql-0.1.1/debian/rules --- aiomysql-0.1.1/debian/rules 2022-11-05 19:56:23.0 +0100 +++ aiomysql-0.1.1/debian/rules 2023-03-07 22:01:12.0 +0100 @@ -19,6 +19,7 @@ rm -rf .pytest_cache rm -f tests/fixtures/my.cnf rm -f docs/make.bat + rm -f aiomysql-0.1.1/aiomysql/_scm_version.py override_dh_auto_build: dh_auto_build signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Unblocked.--- End Message ---
Bug#1032905: marked as done (unblock: firmware-nonfree/20230210-4)
Your message dated Mon, 13 Mar 2023 21:13:01 + with message-id and subject line unblock firmware-nonfree has caused the Debian Bug report #1032905, regarding unblock: firmware-nonfree/20230210-4 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.) -- 1032905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032905 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 X-Debbugs-Cc: firmware-nonf...@packages.debian.org, Cyril Brulebois , car...@debian.org Control: affects -1 + src:firmware-nonfree Hi Release Team, Please unblock package firmware-nonfree On the way between bullseye and current testing, we did lost for brcm80211 some firmware files, more precisely links to the cypress named files, see #1032367. Additionally due to a packaging error, iwlwifi-so-a0-hr-b0-72.ucode got missed as well (#1032608). Not having this version unblocked for bookworm will cause some devices to not work. The debdiff inclused as well a small change to the description of firmware-atheros dropping the mentioning of ath9k_htc. unblock firmware-nonfree/20230210-4 Regards, Salvatore --- End Message --- --- Begin Message --- Unblocked.--- End Message ---
Bug#1032910: unblock: apt/2.6.0
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: a...@packages.debian.org, j...@debian.org Control: affects -1 + src:apt Please unblock package apt [ Reason ] APT 2.6.0 contains the final fixes for bookworm, adding non-free-firmware support, making the `changelog` command query the online servers for the truncated changelogs that are the default now, fixes a bug where Release files were stored that should have been rejected, translation updates, and licensing clarifications (which is an RC bug). I am sorry, Unfortunately due to various comment changes mostly, the diff is a bit unwieldly to look at, but the individual code changes are rather small, it might be easier to look at the commit diffs: https://salsa.debian.org/apt-team/apt/-/compare/2.5.6...2.6.0?from_project_id=228=false or grouped by the merges for code changes: non-free-firmware: https://salsa.debian.org/apt-team/apt/-/merge_requests/282 (updated ubuntu codename to lunar in followup) + https://salsa.debian.org/apt-team/apt/-/merge_requests/286 followup (minor tweaks to those changes) changelog: https://salsa.debian.org/apt-team/apt/-/merge_requests/288 do not store trusted Release file unconditionally: https://salsa.debian.org/apt-team/apt/-/merge_requests/289 copyright rework: https://salsa.debian.org/apt-team/apt/-/merge_requests/287 Unfortunately we lost a week or so because I was sick after FOSDEM :( Full Changelog: [ Cyril Brulebois ] * Teach apt-cdrom's scoring system about non-free-firmware (Closes: #1029751) . [ David Kalnischkies ] * More support for non-free-firmware - Have values in Section config trees refer to them in all components - Add non-free-firmware component in documentation - Suggest using non-free-firmware in update for Debian * other bookworm regressions: - Bump codenames in docs in preparation for Debian 12 - Detect trimmed changelogs and pick online instead (Closes: #1024457) * Do not store trusted=yes Release file unconditionally . [ Miroslav Kure ] * Czech program translation update (Closes: #1031008) . [ Bastian Germann ] * machine-readable version of COPYING (Closes: #1019273), initial version . [ Julian Andres Klode ] * Update lintian override info format in d/apt.lintian-overrides * Further work on machine-readable COPYING file and the source code comments to address licensing inadequacies: - Address statements of public domain - po/nb.po: Relicensing GPL-2.0 -> GPL-2.0+. Thanks Petter for chasing down the copyright holders and getting agreement. - COPYING: Group by license - Address translation licensing concerns - COPYING: Address RunScripts() - We do not believe rsh was supposed to exclude GPL-3 This unfortunately creates a bit of churn, but updating the COPYING file without addressing the actual licensing issues would not have solved the bug. [ Impact ] * `changelog` command only shows incomplete changelogs * non-free-firmware is not treated correctly * documentation references old codenames * czech translation incomplete * `debian/copyright` file and licensing is unreliable [ Tests ] (What automated or manual tests cover the affected code?) All changes have been accompanied by regression tests to the best of my knowledge. [ Risks ] The code changes are reasonably small and well tested. [ Checklist ] [!] all changes are documented in the d/changelog Sigh, two editorial changes were marked ignore in the git commits which I did not notice when merging: https://salsa.debian.org/apt-team/apt/-/commit/e90ba0afa2a27ecea792e8039b2917ec55647548 https://salsa.debian.org/apt-team/apt/-/commit/edcdc251c527141bddb502e799d9a3911a73841b They do not affect the binaries produced. Some changes were squashed together in the changelog editing as they were redundant (e.g. two Ubuntu codename update commits are squashed into "update codenames"). [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing [ Other info ] (Anything else the release team should know.) unblock apt/2.6.0 -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en signature.asc Description: PGP signature
Processed: unblock: apt/2.6.0
Processing control commands: > affects -1 + src:apt Bug #1032910 [release.debian.org] unblock: apt/2.6.0 Added indication that 1032910 affects src:apt -- 1032910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: testing security uploads to bookworm-security
Hi, On 2023-03-10 23:11, Salvatore Bonaccorso wrote: > Hi Aurelien, > > On Fri, Mar 10, 2023 at 05:59:08PM +0100, Aurelien Jarno wrote: > > Hi, > > > > On 2023-03-10 16:55, Salvatore Bonaccorso wrote: > > > Hi, > > > > > > On Thu, Mar 09, 2023 at 11:35:46AM +0100, Salvatore Bonaccorso wrote: > > > > Hi Ansgar, > > > > > > > > [Adding debian-wb-t...@lists.debian.org list] > > > > > > > > On Thu, Mar 09, 2023 at 01:16:21AM +0100, Ansgar wrote: > > > > > Hi, > > > > > > > > > > Salvatore Bonaccorso writes: > > > > > > python-cryptography/38.0.4-3~deb12u1 was uploaded to security-master > > > > > > as source only upload, the upload got rejected with: > > > > > > > > > > > > | Source-only uploads to NEW are not allowed. > > > > > > > > > > There were two issues: > > > > > > > > > > - The override sync from ftp-master to security-master was not > > > > > handling > > > > >the fancy new `-security` addition to suite names. > > > > > > > > > > - `bookworm-security` was still configured to not accept any uploads > > > > >(as was done when the suite was created to prevent accidental > > > > >uploads). > > > > > > > > > > Both issues are now solved and the python-cryptography source upload > > > > > was > > > > > processed successfully. > > > > > > > > Thank you for addressing both. I can confirm we have now partially > > > > builds on the embargoed queue. > > > > > > FTR, Steve as well uploaded src:shim to test the code signing > > > involving path, and looks fine AFAICS. To Steve's request we will > > > though not install those packages, so reject them from the embargoed > > > queues. > > > > > > > From what I see there are the mipsel and mips64el builds missing and > > > > according to a quick chat with Adam on IRC it is not that they are yet > > > > just missing because of buildd overloaded. Actually bookworm-security > > > > seems not yet configured to be handled by mipsel and mips64el buildds. > > > > > > > > Wanna-build team, can you have a look and check the mipsel, mips64el > > > > status (and actually if we are setup complete as well on buildd setup > > > > for bookworm-security)? > > > > Sorry to not have looked that earlier. Indeed none of the mips*el > > buildds were configured to build bookworm-security. I have enabled it on > > two buildds for now, but this has to be done for all buildds. We also > > need to check that it is the case for the other architectures. I have no > > time now, I'll keep you updated once done, but in the meantime you > > should be able to do tests with more packages. > > > > > This one would still need to be checked, looping in as well Debian > > > Build Daemon team alias. Buildd admins, chan you have a look? I still > > > would like to install for real python-crytpography, though we have > > > missed the window to do it earlier than the -3 upload migrated to > > > testing. It still should work I think. Otherwise we will do then > > > another test with another package. > > > > python-cryptography has now been uploaded on both mipsel and mips64el. > > Thanks, confirmed the two bulds arrived as well. > > Paul and release team, here is a summary: so I think we can confirm > that the bookworm-security side of things works now (modulo the above > checking by Aurelien). We did: I have checked and updated the buildds config. We now have all bookworm suites enabled consistently across all the buildds. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Processed: unblock: aiomysql/0.1.1-2
Processing control commands: > affects -1 + src:aiomysql Bug #1032909 [release.debian.org] unblock: aiomysql/0.1.1-2 Added indication that 1032909 affects src:aiomysql -- 1032909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032909: unblock: aiomysql/0.1.1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: aiomy...@packages.debian.org Control: affects -1 + src:aiomysql Please unblock package aiomysql [ Reason ] aiomysql 0.1.1-1 in bookworm is affected by RC bug #1030464. [ Impact ] aiomysql will be removed from bookworm if the RC bug is not addressed, but it doesn't look like it will pull much reverse dependencies out of bookworm as well. Overall impact looks low. [ Tests ] I force ran the autodep8-python3 for aiomysql 0.1.1-2 in both unstable and testing context and it raised no obvious issues: autopkgtest [21:12:53]: test autodep8-python3: [--- Testing with python3.11: autopkgtest [21:12:53]: test autodep8-python3: ---] but not much more apart from that as I don't use the package myself. [ Risks ] The change is minimal, so the risk of introducing a breakage looks pretty low. [ Checklist ] [*] all changes are documented in the d/changelog [*] I reviewed all changes and I approve them [*] attach debdiff against the package in testing [ Other info ] There is a side change with the RC bug fix: a fix for ftbfs when rebuilding the pakage; the issue initially comes from upstream mixing up doc and unix style end-of-lines. If this is deemed inappropriate, I may upload a 0.1.1-3 without the file removal after the dh_auto_clean target. unblock aiomysql/0.1.1-2 Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/6, please excuse my verbosity. On air: Frost* - Milliontown diff -Nru aiomysql-0.1.1/debian/changelog aiomysql-0.1.1/debian/changelog --- aiomysql-0.1.1/debian/changelog 2022-11-05 19:56:23.0 +0100 +++ aiomysql-0.1.1/debian/changelog 2023-03-07 22:13:05.0 +0100 @@ -1,3 +1,15 @@ +aiomysql (0.1.1-2) unstable; urgency=medium + + * Team upload. + * d/control: cleanup aiomysql/_scm_version.py. +This allows the package to be rebuildable from a clean state after a +first build attempt. + * d/control: build depends on python3-setuptools-scm. +This fixes a failure to build from source. +Thanks to s3v (Closes: #1030464) + + -- Étienne Mollier Tue, 07 Mar 2023 22:13:05 +0100 + aiomysql (0.1.1-1) unstable; urgency=medium * New upstream release diff -Nru aiomysql-0.1.1/debian/control aiomysql-0.1.1/debian/control --- aiomysql-0.1.1/debian/control 2022-11-05 19:56:23.0 +0100 +++ aiomysql-0.1.1/debian/control 2023-03-07 21:46:52.0 +0100 @@ -8,6 +8,7 @@ python3-all, python3-setuptools, python3-pymysql, + python3-setuptools-scm, python3-sphinx , python3-sphinxcontrib-asyncio , python3-sphinx-rtd-theme , diff -Nru aiomysql-0.1.1/debian/rules aiomysql-0.1.1/debian/rules --- aiomysql-0.1.1/debian/rules 2022-11-05 19:56:23.0 +0100 +++ aiomysql-0.1.1/debian/rules 2023-03-07 22:01:12.0 +0100 @@ -19,6 +19,7 @@ rm -rf .pytest_cache rm -f tests/fixtures/my.cnf rm -f docs/make.bat + rm -f aiomysql-0.1.1/aiomysql/_scm_version.py override_dh_auto_build: dh_auto_build signature.asc Description: PGP signature
Bug#1032905: unblock: firmware-nonfree/20230210-4
Hi, On Mon, Mar 13, 2023 at 08:36:21PM +0100, Salvatore Bonaccorso wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > X-Debbugs-Cc: firmware-nonf...@packages.debian.org, Cyril Brulebois > , car...@debian.org > Control: affects -1 + src:firmware-nonfree > > Hi Release Team, > > Please unblock package firmware-nonfree > > On the way between bullseye and current testing, we did lost for > brcm80211 some firmware files, more precisely links to the cypress > named files, see #1032367. > > Additionally due to a packaging error, iwlwifi-so-a0-hr-b0-72.ucode > got missed as well (#1032608). > > Not having this version unblocked for bookworm will cause some devices > to not work. > > The debdiff inclused as well a small change to the description of > firmware-atheros dropping the mentioning of ath9k_htc. > > unblock firmware-nonfree/20230210-4 *sigh*, apologies. Now *with* debdiff attached. Regards, Salvatore diff -Nru firmware-nonfree-20230210/debian/changelog firmware-nonfree-20230210/debian/changelog --- firmware-nonfree-20230210/debian/changelog 2023-02-25 18:02:15.0 +0100 +++ firmware-nonfree-20230210/debian/changelog 2023-03-11 15:15:03.0 +0100 @@ -1,3 +1,22 @@ +firmware-nonfree (20230210-4) unstable; urgency=medium + + * iwlwifi: Add missing files entry for iwlwifi-so-a0-hr-b0-72.ucode. +Thanks to Jonathan Klabunde Tomer (Closes: #1032608) + + -- Salvatore Bonaccorso Sat, 11 Mar 2023 15:15:03 +0100 + +firmware-nonfree (20230210-3) unstable; urgency=medium + + [ Bastian Germann ] + * firmware-atheros: Remove ath9k_htc from description + + [ Diederik de Haas ] + * Update to linux-support 6.1.0-6 + * brcm80211: brcm: Restore symlinks from cypress to brcm directory +(Closes: #1032367) + + -- Salvatore Bonaccorso Sat, 11 Mar 2023 14:29:56 +0100 + firmware-nonfree (20230210-2) unstable; urgency=medium [ Salvatore Bonaccorso ] diff -Nru firmware-nonfree-20230210/debian/config/atheros/defines firmware-nonfree-20230210/debian/config/atheros/defines --- firmware-nonfree-20230210/debian/config/atheros/defines 2023-02-25 17:37:27.0 +0100 +++ firmware-nonfree-20230210/debian/config/atheros/defines 2023-03-11 11:08:44.0 +0100 @@ -195,7 +195,7 @@ wil6210.brd wil6210.fw longdesc: USB wireless network and Bluetooth cards supported by the ar5523, - ath3k, ath6kl_sdio, ath6kl_usb, ath9k_htc, ath10k, or wilc6210 drivers + ath3k, ath6kl_sdio, ath6kl_usb, ath10k, or wilc6210 drivers [ar3k/AthrBT_0x01020001.dfu_base] desc: Atheros AR3012 rev 01020001 patch diff -Nru firmware-nonfree-20230210/debian/config/brcm80211/defines firmware-nonfree-20230210/debian/config/brcm80211/defines --- firmware-nonfree-20230210/debian/config/brcm80211/defines 2023-02-25 11:03:35.0 +0100 +++ firmware-nonfree-20230210/debian/config/brcm80211/defines 2023-03-11 14:25:34.0 +0100 @@ -30,6 +30,7 @@ brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-zero.txt brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-ultra.txt brcm/brcmfmac43430-sdio.sinovoip,bpi-m3.txt + brcm/brcmfmac4339-sdio.bin brcm/brcmfmac43430-sdio.bin brcm/brcmfmac43430-sdio.clm_blob brcm/brcmfmac43430a0-sdio.bin @@ -49,10 +50,14 @@ brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt brcm/brcmfmac4350c2-pcie.bin brcm/brcmfmac4350-pcie.bin + brcm/brcmfmac4354-sdio.bin brcm/brcmfmac4354-sdio.clm_blob brcm/brcmfmac43569.bin + brcm/brcmfmac4356-pcie.bin brcm/brcmfmac4356-pcie.gpd-win-pocket.txt + brcm/brcmfmac4356-sdio.bin brcm/brcmfmac4356-pcie.clm_blob + brcm/brcmfmac4356-sdio.bin brcm/brcmfmac4356-sdio.clm_blob brcm/brcmfmac4356-sdio.vamrs,rock960.txt brcm/brcmfmac4356-sdio.khadas,vim2.txt diff -Nru firmware-nonfree-20230210/debian/config/iwlwifi/defines firmware-nonfree-20230210/debian/config/iwlwifi/defines --- firmware-nonfree-20230210/debian/config/iwlwifi/defines 2023-02-11 21:18:38.0 +0100 +++ firmware-nonfree-20230210/debian/config/iwlwifi/defines 2023-03-11 14:52:14.0 +0100 @@ -112,6 +112,7 @@ iwlwifi-so-a0-gf-a0.pnvm iwlwifi-so-a0-gf4-a0-72.ucode iwlwifi-so-a0-gf4-a0.pnvm + iwlwifi-so-a0-hr-b0-72.ucode iwlwifi-so-a0-jf-b0-72.ucode longdesc: Intel Wireless cards supported by the iwl3945, iwl4965, and iwlwifi drivers diff -Nru firmware-nonfree-20230210/debian/control firmware-nonfree-20230210/debian/control --- firmware-nonfree-20230210/debian/control2023-02-25 18:02:15.0 +0100 +++ firmware-nonfree-20230210/debian/control2023-03-11 15:15:03.0 +0100 @@ -917,7 +917,7 @@ Description: Binary firmware for Qualcomm Atheros wireless cards This package contains the binary firmware for USB wireless network and Bluetooth cards supported by the ar5523, ath3k, ath6kl_sdio, ath6kl_usb, - ath9k_htc, ath10k, or wilc6210 drivers. + ath10k, or wilc6210 drivers. . Contents: * Atheros AR3012 rev 01020001 patch
Bug#1032905: unblock: firmware-nonfree/20230210-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: firmware-nonf...@packages.debian.org, Cyril Brulebois , car...@debian.org Control: affects -1 + src:firmware-nonfree Hi Release Team, Please unblock package firmware-nonfree On the way between bullseye and current testing, we did lost for brcm80211 some firmware files, more precisely links to the cypress named files, see #1032367. Additionally due to a packaging error, iwlwifi-so-a0-hr-b0-72.ucode got missed as well (#1032608). Not having this version unblocked for bookworm will cause some devices to not work. The debdiff inclused as well a small change to the description of firmware-atheros dropping the mentioning of ath9k_htc. unblock firmware-nonfree/20230210-4 Regards, Salvatore
Processed: unblock: firmware-nonfree/20230210-4
Processing control commands: > affects -1 + src:firmware-nonfree Bug #1032905 [release.debian.org] unblock: firmware-nonfree/20230210-4 Added indication that 1032905 affects src:firmware-nonfree -- 1032905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032885: unblock: debian-security-support/1:12+2023.03.05
On Mon, Mar 13, 2023 at 03:07:34PM +, Holger Levsen wrote: > On Mon, Mar 13, 2023 at 03:58:45PM +0100, Moritz Mühlenhoff wrote: > > Am Mon, Mar 13, 2023 at 01:43:11PM +0100 schrieb Holger Levsen: > > > * security-support-limited: > > > - for golang and openjdk-17, point to the bookworm manual instead the > > > one > > > for bullseye. > > That's wrong, though. (And the release notes need updating to, I'll file > > a bug soonish): In Bookworm openjdk-17 is the default Java and fully > > supported, but we need the equivalent note for openjdk-21 now. > > thanks, Moritz. I'll happily update d-s-s once the release manual is updated. > or i could update d-s-s now too, if it's really just about replacing 17 with > 21 in this line from security-support-limited : > > openjdk-17See > https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#openjdk-17 > > Are there any further updates expected from the security team's POV? Let me comb through past two years of issues, I'll get back to in the next days. Cheers, Moritz
Bug#1032903: unblock: liferea/1.14.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: life...@packages.debian.org Control: affects -1 + src:liferea Please unblock package liferea [ Reason ] A CVE was discovered in liferea and upstream quickly released a new version including the fix. The new version also fixes a crash on double free. Unfortunately it also included one more less important improvement and an updated translation. Considering my options, I decided it was best to upload the new version instead of only fixing the CVE. https://security-tracker.debian.org/tracker/CVE-2023-1350 [ Impact ] The CVE is about a Remote Code Excecution of RSS feed information when the user has opted-in to "Extract full content from HTML5 and Google AMP". I believe that's pretty bad, but luckily it's not the default. [ Tests ] liferea doesn't have autopkgtests (yet), but I do activate the upstream tests during build. Unfortunately, that currently fails (because liferea isn't installed during build and if that's worked around something fails due to being root; sorry, haven't fixed that yet), but I ran the tests locally and then all regular tests pass. The memtest fails in the same way as before. I also eat my own dogfood as I'm a user of liferea and have the binaries installed since I built them. [ Risks ] In the end, the changes are a bit more than trivial, but the delta in this release is targetted to specific issues. I have a good relation with upstream and he even supported me in the discussion with the security team. Unfortunately, liferea isn't a leaf package as the bfh-desktop (new in bookworm) and progress-linux-desktop (already in bullseye) depend on it. [ 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 ] I recommend viewing the debdiff with the following filter to ignore upstream workflow items, the translation update and additional test cases added for the purpose of testing the fix: filterdiff -x '*/.gitignore' -x '*/.github/workflows/cb.yml' -x '*/po/fr.po' -x '*/src/tests' liferea_1.14.1-1.debdiff unblock liferea/1.14.1-1 Paul diff -Nru liferea-1.14.0/ChangeLog liferea-1.14.1/ChangeLog --- liferea-1.14.0/ChangeLog2023-01-10 21:12:42.0 +0100 +++ liferea-1.14.1/ChangeLog2023-03-12 21:00:51.0 +0100 @@ -1,3 +1,17 @@ +2023-03-12 Lars Windolf + + Version 1.14.1 + + * Fixes CVE-2023-1350: RCE vulnerability on feed enrichment + (patch by Alexander Erwin Ittner) + + * Fixes #1200: Crash on double free + (mozbugbox) + + * Improve #1192 be reordering widget creation order + (Lars Windolf) + + 2023-01-10 Lars Windolf Version 1.14.0 diff -Nru liferea-1.14.0/configure.ac liferea-1.14.1/configure.ac --- liferea-1.14.0/configure.ac 2023-01-10 21:12:42.0 +0100 +++ liferea-1.14.1/configure.ac 2023-03-12 21:00:51.0 +0100 @@ -1,6 +1,6 @@ dnl Process this file with autoconf to produce a configure script. -AC_INIT([liferea],[1.14.0],[liferea-de...@lists.sourceforge.net]) +AC_INIT([liferea],[1.14.1],[liferea-de...@lists.sourceforge.net]) AC_CANONICAL_HOST AC_CONFIG_SRCDIR([src/feedlist.c]) diff -Nru liferea-1.14.0/debian/changelog liferea-1.14.1/debian/changelog --- liferea-1.14.0/debian/changelog 2023-01-15 21:14:44.0 +0100 +++ liferea-1.14.1/debian/changelog 2023-03-12 21:32:33.0 +0100 @@ -1,3 +1,12 @@ +liferea (1.14.1-1) unstable; urgency=medium + + * New upstream version 1.14.1 +Contains fix for CVE-2023-1350 which is a RCE when the option "Extract +full content from HTML5 and Google AMP" is enable on a feed (Closes: +#1032822) + + -- Paul Gevers Sun, 12 Mar 2023 21:32:33 +0100 + liferea (1.14.0-1) unstable; urgency=medium * New upstream version 1.14.0 diff -Nru liferea-1.14.0/.github/workflows/cb.yml liferea-1.14.1/.github/workflows/cb.yml --- liferea-1.14.0/.github/workflows/cb.yml 2023-01-10 21:12:42.0 +0100 +++ liferea-1.14.1/.github/workflows/cb.yml 2023-03-12 21:00:51.0 +0100 @@ -24,7 +24,7 @@ - run: | sudo apt-get update -qq - sudo apt-get install -y -qq libxml2-dev libxslt1-dev libsqlite3-dev libwebkit2gtk-4.0-dev libjson-glib-dev libgirepository1.0-dev libpeas-dev gsettings-desktop-schemas-dev python3 libtool intltool valgrind libfribidi-dev gla11y + sudo apt-get install -y -qq libxml2-dev libxslt1-dev libsqlite3-dev libwebkit2gtk-4.0-dev libjson-glib-dev libgirepository1.0-dev libpeas-dev gsettings-desktop-schemas-dev python3 libtool intltool valgrind libfribidi-dev gla11y appstream-util desktop-file-utils mkdir inst - run: | @@ -35,6 +35,8 @@ - run: make && make install - run: sudo cp net.sf.liferea.gschema.xml /usr/share/glib-2.0/schemas - run: sudo /usr/bin/glib-compile-schemas
Bug#1032901: unblock: crystal/1.6.0+dfsg-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: crys...@packages.debian.org, d...@debian.org Control: affects -1 + src:crystal Please unblock package crystal [ Reason ] The new version will fix #1031812 (the package lacks some dependencies), and unmark it from autoremovals. [ Impact ] Crystal will be removed from testing due to autoremovals. [ Tests ] The package was manually tested in a new and clean debian installation to check that the package has now all the needed dependecies to work. [ Risks ] The change is trivial, it only implies adding some runtime dependencies. [ 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 package was upload some days before the hard freeze so it couldn't get migrated automatically. unblock crystal/1.6.0+dfsg-3
Processed: unblock: crystal/1.6.0+dfsg-3
Processing control commands: > affects -1 + src:crystal Bug #1032901 [release.debian.org] unblock: crystal/1.6.0+dfsg-3 Added indication that 1032901 affects src:crystal -- 1032901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unblock: liferea/1.14.1-1
Processing control commands: > affects -1 + src:liferea Bug #1032903 [release.debian.org] unblock: liferea/1.14.1-1 Added indication that 1032903 affects src:liferea -- 1032903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032901: unblock: crystal/1.6.0+dfsg-3
Attaching debdiff.
diff -Nru crystal-1.6.0+dfsg/debian/changelog crystal-1.6.0+dfsg/debian/changelog
--- crystal-1.6.0+dfsg/debian/changelog 2022-10-11 21:08:52.0 +0200
+++ crystal-1.6.0+dfsg/debian/changelog 2023-03-03 19:03:34.0 +0100
@@ -1,3 +1,9 @@
+crystal (1.6.0+dfsg-3) unstable; urgency=medium
+
+ * Update runtime depends (Closes: #1031812).
+
+ -- David Suárez Fri, 03 Mar 2023 19:03:34 +0100
+
crystal (1.6.0+dfsg-2) unstable; urgency=medium
* Source upload.
diff -Nru crystal-1.6.0+dfsg/debian/control crystal-1.6.0+dfsg/debian/control
--- crystal-1.6.0+dfsg/debian/control 2022-10-11 21:08:52.0 +0200
+++ crystal-1.6.0+dfsg/debian/control 2023-03-03 19:03:34.0 +0100
@@ -27,10 +27,14 @@
Package: crystal
Architecture: amd64
-Depends: pkg-config,
- ${misc:Depends},
+Depends: ${misc:Depends},
${shlibs:Depends},
- libgc-dev
+ gcc,
+ libgc-dev,
+ pkg-config,
+ libpcre3-dev,
+ libevent-dev
+Recommends: libssl-dev, libz-dev, libxml2-dev, libgmp-dev, libyaml-dev
Suggests: crystal-doc, crystal-samples
Description: compiler of the Crystal object-oriented programming language
The Crystal's language syntax is inspired by Ruby, the language is statically
Re: Could I ask for unblock for 7 OBS plugins?
Em seg., 13 de mar. de 2023 às 15:21, Sebastian Ramacher escreveu: > > On 2023-03-13 15:10:40 -0300, Eriberto wrote: > > Em seg., 13 de mar. de 2023 às 15:01, Sebastian Ramacher > > escreveu: > > > > > > On 2023-03-13 14:20:54 -0300, Eriberto Mota wrote: > > > > Dear Release Managers, > > > > > > > > obs-text-slideshow was accepted in Debian in 2021-10-10[1] and removed > > > > in 2022-10-17[2] (ROM; FTBFS, dead upstream). However, yesterday, a > > > > user detected that the package was present in its machine running > > > > testing and this plugin was causing an abnormal behavior on > > > > obs-studio. After removing the package, the system was stable. > > > > > > > > I would like to add 'Breaks: obs-text-slideshow (<= 1.5.2-3)' to seven > > > > plugins (obs-downstream-keyer, obs-move-transition, > > > > obs-scene-collection-manager, obs-scene-notes-dock, obs-source-clone, > > > > obs-source-copy, obs-transition-table) to force a removing of the > > > > obs-text-slideshow on users machines, avoiding future issues. What you > > > > think about this action? If ok for you, I will send an ask for unblock > > > > per package, considering all these packages are using trivial > > > > autopkgtests only. > > > > > > Wouldn't it make more sense to add the Breaks to obs-studio itself? > > > > Yes, but it is a change in obs-studio on freeze and I thought you (as > > maintainer of obs-studio) was told me "no". So, I used some of my > > packages (with more relevance) as an alternative. Thanks a lot for > > your help. > > ? > > Do you have a reference for that? I don't remember anything regarding > Breaks in obs-studio from the last two to three months. > > Cheers > -- > Sebastian Ramacher Sorry, I am not English native and I think that the right is "I thought you would tell me no". I never asked for a Breaks in obs-studio. This problem occurred in the first time yesterday. I hope all right now. Cheers, Eriberto
Bug#1032849: marked as done (unblock: shim/15.7-1 (etc.))
Your message dated Mon, 13 Mar 2023 19:34:16 +0100 with message-id <2f62415e-b175-1e17-5d84-2bfa25944...@debian.org> and subject line Re: Bug#1032849: unblock: shim/15.7-1 (etc.) has caused the Debian Bug report #1032849, regarding unblock: shim/15.7-1 (etc.) 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.) -- 1032849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032849 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 X-Debbugs-Cc: debian-...@lists.debian.org Hi! Please unblock our stack of shim and shim-signed packages. We finally have new signed shim binaries and there's a lot of major bugfixes included which cascade down: shim (15.7-1) unstable; urgency=medium * New upstream release fixing more bugs * Add further patches from upstream: + Make sbat_var.S parse right with buggy gcc/binutils + Enable NX support at build time, as required by policy for signing new shim binaries. * Switch to using gcc-12. Closes: #1022180 * Update to Standards-Version 4.6.2 (no changes needed) * Block Debian grub binaries with sbat < 4 (see #1024617) shim-signed (1.39) unstable; urgency=medium * Build against new signed binaries corresponding to 15.7-1 + This syncs up build-deps again. Closes: #1016280 + We now have arm64 signed shims again \o/ Undo the hacky unsigned arm64 build Closes: #1008942, #992073, #991478 Pulls multiple other bugfixes in for the signed version: + Make sbat_var.S parse right with buggy gcc/binutils + Enable NX support at build time, as required by policy for signing new shim binaries. + Fixes argument handling bug with some firmware implementations. Closes: #995940 * Update build-dep on shim-unsigned to use 15.7-1 * Block Debian grub binaries with sbat < 4 (see #1024617) + Update Depends on grub2-common to match. * postinst/postrm: make config_item() more robust * Add pt_BR translation, thanks to Paulo Henrique de Lima Santana. Closes: #1026415 * Tweak dependencies unblock shim/15.7-1 unblock shim-signed/1.39 unblock shim-helpers-amd64-signed/1+15.7+1 unblock shim-helpers-arm64-signed/1+15.7+1 unblock shim-helpers-i386-signed/1+15.7+1 --- End Message --- --- Begin Message --- Hi Steve, On 12-03-2023 20:06, Paul Gevers wrote: As mentioned on IRC, I like to age it one or two days more, but the hints are already in my hints file (commented out), so I'll do that tomorrow or on Tuesday. Done now. Paul OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#1032887: unblock: llvm-toolchain-15/1:15.0.7-3
Le 13/03/2023 à 18:54, Sebastian Ramacher a écrit : Control: tags -1 moreinfo On 2023-03-13 14:27:52 +0100, Sylvestre Ledru wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: llvm-toolchain...@packages.debian.org Control: affects -1 + src:llvm-toolchain-15 Please unblock package llvm-toolchain-15 [ Reason ] Fixes autopkgtest issues and new version interesting for mesa (if I understood correctly) and fixes some wasm compiler bugs [ Impact ] Mesa issue ? [ Tests ] autopkgtest live on apt.llvm.org for a few days/weeks [ Risks ] Upstream is pretty careful with dot releases, so, i am not expecting regressions and I will be around [ 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 (quite long). can share if needed The debdiff includes: llvm-toolchain-15-15.0.7/build/CMakeCache.txt | 3215 llvm-toolchain-15-15.0.7/build/CMakeDoxyfile.in | 289 llvm-toolchain-15-15.0.7/build/CMakeDoxygenDefaults.cmake | 695 llvm-toolchain-15-15.0.7/build/CMakeFiles/3.24.3/CMakeASMCompiler.cmake | 20 llvm-toolchain-15-15.0.7/build/CMakeFiles/3.24.3/CMakeCCompiler.cmake | 72 llvm-toolchain-15-15.0.7/build/CMakeFiles/3.24.3/CMakeCXXCompiler.cmake | 83 llvm-toolchain-15-15.0.7/build/CMakeFiles/3.24.3/CMakeSystem.cmake | 15 llvm-toolchain-15-15.0.7/build/CMakeFiles/3.24.3/CompilerIdC/CMakeCCompilerId.c | 838 llvm-toolchain-15-15.0.7/build/CMakeFiles/3.24.3/CompilerIdCXX/CMakeCXXCompilerId.cpp | 826 llvm-toolchain-15-15.0.7/build/CMakeFiles/CMakeError.log | 712 llvm-toolchain-15-15.0.7/build/CMakeFiles/CMakeOutput.log | 2392 llvm-toolchain-15-15.0.7/build/CMakeFiles/CheckIncludeFiles/HAVE_INOTIFY.c |6 llvm-toolchain-15-15.0.7/build/CMakeFiles/TargetDirectories.txt |12436 llvm-toolchain-15-15.0.7/build/CMakeFiles/cmake.check_cache |1 llvm-toolchain-15-15.0.7/build/CMakeFiles/rules.ninja |14600 llvm-toolchain-15-15.0.7/build/CPackConfig.cmake | 78 llvm-toolchain-15-15.0.7/build/CPackSourceConfig.cmake | 86 llvm-toolchain-15-15.0.7/build/benchmarks/cmake_install.cmake | 44 llvm-toolchain-15-15.0.7/build/bin/flang-to-external-fc | 493 llvm-toolchain-15-15.0.7/build/bin/llvm-lit | 46 llvm-toolchain-15-15.0.7/build/bin/update_core_linalg_named_ops.sh | 32 llvm-toolchain-15-15.0.7/build/bindings/ocaml/all_backends/cmake_install.cmake | 66 llvm-toolchain-15-15.0.7/build/bindings/ocaml/analysis/cmake_install.cmake | 66 llvm-toolchain-15-15.0.7/build/bindings/ocaml/backends/X86_ocaml.c | 38 llvm-toolchain-15-15.0.7/build/bindings/ocaml/backends/cmake_install.cmake | 78 llvm-toolchain-15-15.0.7/build/bindings/ocaml/backends/llvm_X86.ml |9 llvm-toolchain-15-15.0.7/build/bindings/ocaml/backends/llvm_X86.mli | 18 llvm-toolchain-15-15.0.7/build/bindings/ocaml/bitreader/cmake_install.cmake
Re: Could I ask for unblock for 7 OBS plugins?
On 2023-03-13 15:10:40 -0300, Eriberto wrote: > Em seg., 13 de mar. de 2023 às 15:01, Sebastian Ramacher > escreveu: > > > > On 2023-03-13 14:20:54 -0300, Eriberto Mota wrote: > > > Dear Release Managers, > > > > > > obs-text-slideshow was accepted in Debian in 2021-10-10[1] and removed > > > in 2022-10-17[2] (ROM; FTBFS, dead upstream). However, yesterday, a > > > user detected that the package was present in its machine running > > > testing and this plugin was causing an abnormal behavior on > > > obs-studio. After removing the package, the system was stable. > > > > > > I would like to add 'Breaks: obs-text-slideshow (<= 1.5.2-3)' to seven > > > plugins (obs-downstream-keyer, obs-move-transition, > > > obs-scene-collection-manager, obs-scene-notes-dock, obs-source-clone, > > > obs-source-copy, obs-transition-table) to force a removing of the > > > obs-text-slideshow on users machines, avoiding future issues. What you > > > think about this action? If ok for you, I will send an ask for unblock > > > per package, considering all these packages are using trivial > > > autopkgtests only. > > > > Wouldn't it make more sense to add the Breaks to obs-studio itself? > > Yes, but it is a change in obs-studio on freeze and I thought you (as > maintainer of obs-studio) was told me "no". So, I used some of my > packages (with more relevance) as an alternative. Thanks a lot for > your help. ? Do you have a reference for that? I don't remember anything regarding Breaks in obs-studio from the last two to three months. Cheers -- Sebastian Ramacher
Re: Could I ask for unblock for 7 OBS plugins?
Em seg., 13 de mar. de 2023 às 15:01, Sebastian Ramacher escreveu: > > On 2023-03-13 14:20:54 -0300, Eriberto Mota wrote: > > Dear Release Managers, > > > > obs-text-slideshow was accepted in Debian in 2021-10-10[1] and removed > > in 2022-10-17[2] (ROM; FTBFS, dead upstream). However, yesterday, a > > user detected that the package was present in its machine running > > testing and this plugin was causing an abnormal behavior on > > obs-studio. After removing the package, the system was stable. > > > > I would like to add 'Breaks: obs-text-slideshow (<= 1.5.2-3)' to seven > > plugins (obs-downstream-keyer, obs-move-transition, > > obs-scene-collection-manager, obs-scene-notes-dock, obs-source-clone, > > obs-source-copy, obs-transition-table) to force a removing of the > > obs-text-slideshow on users machines, avoiding future issues. What you > > think about this action? If ok for you, I will send an ask for unblock > > per package, considering all these packages are using trivial > > autopkgtests only. > > Wouldn't it make more sense to add the Breaks to obs-studio itself? Yes, but it is a change in obs-studio on freeze and I thought you (as maintainer of obs-studio) was told me "no". So, I used some of my packages (with more relevance) as an alternative. Thanks a lot for your help.
Bug#1032614: ddcutil: pre-approval request ddcutil-1.4.2-1 fixes bug #1031259
On 2023-03-13 13:28:47 -0400, Sanford Rockowitz wrote: > On 3/13/23 07:42, Sebastian Ramacher wrote: > > On 2023-03-13 07:25:41 -0400, Sanford Rockowitz wrote: > > > On 3/13/23 05:33, Sebastian Ramacher wrote: > > > > On 2023-03-11 07:51:16 -0500, Sanford Rockowitz wrote: > > > > > [Reason ] > > > > > (Explain what the reason for the unblock request is.) > > > > > As noted, the unblock request addresses bug #1031259. ddcutil > > > > > requires > > > > > driver i2c-dev. If it happens not to be built into the kernel, this > > > > > entails > > > > > post-installation system configuration. Despite extensive > > > > > documentation and > > > > > application warnings if the driver is not loaded, this can be > > > > > challenging > > > > > for inexperienced users. > > > > > > > > > > > [ Impact ] > > > > > > (What is the impact for the user if the unblock isn't granted?) > > > > > Manual post installation configuration will continue to be required as > > > > > previously. > > > > > > [ Tests ] > > > > > > (What automated or manual tests cover the affected code?) > > > > > None > > > > > > [ Risks ] > > > > > > (Discussion of the risks involved. E.g. code is trivial or > > > > > > complex, key package vs leaf package, alternatives available.) > > > > > The changes are trivial, ensuring that driver i2c-dev is loaded if it > > > > > is not > > > > > already built into the kernel. Package libddccontrol0, an alternative > > > > > to > > > > > ddcutil for monitor control, installs file ddccontrol-i2c-dev.conf, > > > > > which > > > > > loads i2c-dev. The contents of that file, a single line containing > > > > > "i2c-dev", is identical to the contents of the files to be installed > > > > > by > > > > > ddcutil. Additional examples of packages that install files in > > > > > /user/lib/modules-load.d are fwupd, which installs file > > > > > fwupd-msc.conf, and > > > > > encryptfs-utils, which installs file ecryptfs.conf. > > > > The prpoposed changes also introduce a policy violation: > > > > /usr/lib/modules-load.d/libddcutil.conf installed in libddcutil4 is not > > > > versioned the same way as the shared library. See section 8.2 for more > > > > details. > > > > > > > > Cheers > > > > > > > > > If the installed conf file were incorrect, the only effect would be > > > > > an error > > > > > in the system log, and manual user configuration would still be > > > > > required as > > > > > before. > > > > > > > > > > The only (potential) known dependency within Debian is from KDE > > > > > PowerDevil. However, PowerDevil, as installed by Debian, is built > > > > > with use > > > > > of libddcutil if-tested out. (Recommended since its use of libddcutil > > > > > is > > > > > "proof of concept" level code.) > > > > > > > > > > > [ 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 ] > > > > > > (Anything else the release team should know.) > > > As I read section 8.2, there are two possibilities. The first is to > > > version > > > the name of the file installed in /usr/lib/modules-load.d, e.g. > > > libddcutil4.conf for package libddcutil4. The second is to create an > > > additional package, named e.g. libddcutil-aux, that installs > > > libddcutil.conf > > > and on which package libddcutil4 and successor packages libddcutilN > > > depend. > > > The former has the advantage that it doesn't introduce an additional > > > package > > > simply to install a single file, and the disadvantage that it relies on a > > > naming convention for the installed libddcutilN.conf file, which could > > > easily be overlooked when bumping the SONAME. > > As we're in hard freeze, option 2 is not an option for bookworm. > > > > > A third alternative is to not install a modules-load.d conf file for > > > libddcutil, and instead rely on packages using the shared library to > > > install > > > a conf file. But that would multiply the number of packages installing > > > files in modules-load.d, and the potential for errors. > > That doesn't really sound like a solution to the bug. It would leak > > implementation details of libddcutil to all the reverse dependencies. > > > > Cheers > Setting aside what's possible given the bookworm freeze, do you have a > strong opinion as to whether the naming convention or separate package is > preferable/acceptable? I don't feel strongly that the update has to go into > bookworm. I wanted to address the "bug report" promptly, but the change is > more of an enhancement. Nothing is really actually broken, it's just that a > post installation step is necessary for some users, which it would be kind > to avoid. An additional binary package for a file with one line is overkill, IMHO. Cheers -- Sebastian Ramacher
Re: Could I ask for unblock for 7 OBS plugins?
On 2023-03-13 14:20:54 -0300, Eriberto Mota wrote: > Dear Release Managers, > > obs-text-slideshow was accepted in Debian in 2021-10-10[1] and removed > in 2022-10-17[2] (ROM; FTBFS, dead upstream). However, yesterday, a > user detected that the package was present in its machine running > testing and this plugin was causing an abnormal behavior on > obs-studio. After removing the package, the system was stable. > > I would like to add 'Breaks: obs-text-slideshow (<= 1.5.2-3)' to seven > plugins (obs-downstream-keyer, obs-move-transition, > obs-scene-collection-manager, obs-scene-notes-dock, obs-source-clone, > obs-source-copy, obs-transition-table) to force a removing of the > obs-text-slideshow on users machines, avoiding future issues. What you > think about this action? If ok for you, I will send an ask for unblock > per package, considering all these packages are using trivial > autopkgtests only. Wouldn't it make more sense to add the Breaks to obs-studio itself? Cheers -- Sebastian Ramacher
Bug#1032870: marked as done (unblock tryton-sao/6.0.28+ds1-2)
Your message dated Mon, 13 Mar 2023 17:55:20 + with message-id and subject line unblock tryton-sao has caused the Debian Bug report #1032870, regarding unblock tryton-sao/6.0.28+ds1-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.) -- 1032870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032870 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 the package tryton-sao. tryton-sao/6.0.28+ds1-2 fixes https://bugs.debian.org/1032353 unblock: tryton-sao/6.0.28+ds1-2 -- Mathias Behrle PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6 AC29 7E5C 46B9 D0B6 1C71 7681 D6D0 9BE4 8405 BBF6 --- End Message --- --- Begin Message --- Unblocked.--- End Message ---
Processed: Re: Bug#1032887: unblock: llvm-toolchain-15/1:15.0.7-3
Processing control commands: > tags -1 moreinfo Bug #1032887 [release.debian.org] unblock: llvm-toolchain-15/1:15.0.7-3 Added tag(s) moreinfo. -- 1032887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032887: unblock: llvm-toolchain-15/1:15.0.7-3
Control: tags -1 moreinfo On 2023-03-13 14:27:52 +0100, Sylvestre Ledru wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > X-Debbugs-Cc: llvm-toolchain...@packages.debian.org > Control: affects -1 + src:llvm-toolchain-15 > > Please unblock package llvm-toolchain-15 > > [ Reason ] > Fixes autopkgtest issues and new version interesting for > mesa (if I understood correctly) > and fixes some wasm compiler bugs > > [ Impact ] > Mesa issue ? > > [ Tests ] > autopkgtest > live on apt.llvm.org for a few days/weeks > > [ Risks ] > Upstream is pretty careful with dot releases, > so, i am not expecting regressions > and I will be around > > > [ 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 > (quite long). can share if needed The debdiff includes: llvm-toolchain-15-15.0.7/build/CMakeCache.txt | 3215 llvm-toolchain-15-15.0.7/build/CMakeDoxyfile.in | 289 llvm-toolchain-15-15.0.7/build/CMakeDoxygenDefaults.cmake | 695 llvm-toolchain-15-15.0.7/build/CMakeFiles/3.24.3/CMakeASMCompiler.cmake | 20 llvm-toolchain-15-15.0.7/build/CMakeFiles/3.24.3/CMakeCCompiler.cmake | 72 llvm-toolchain-15-15.0.7/build/CMakeFiles/3.24.3/CMakeCXXCompiler.cmake | 83 llvm-toolchain-15-15.0.7/build/CMakeFiles/3.24.3/CMakeSystem.cmake | 15 llvm-toolchain-15-15.0.7/build/CMakeFiles/3.24.3/CompilerIdC/CMakeCCompilerId.c | 838 llvm-toolchain-15-15.0.7/build/CMakeFiles/3.24.3/CompilerIdCXX/CMakeCXXCompilerId.cpp | 826 llvm-toolchain-15-15.0.7/build/CMakeFiles/CMakeError.log | 712 llvm-toolchain-15-15.0.7/build/CMakeFiles/CMakeOutput.log | 2392 llvm-toolchain-15-15.0.7/build/CMakeFiles/CheckIncludeFiles/HAVE_INOTIFY.c |6 llvm-toolchain-15-15.0.7/build/CMakeFiles/TargetDirectories.txt |12436 llvm-toolchain-15-15.0.7/build/CMakeFiles/cmake.check_cache |1 llvm-toolchain-15-15.0.7/build/CMakeFiles/rules.ninja |14600 llvm-toolchain-15-15.0.7/build/CPackConfig.cmake | 78 llvm-toolchain-15-15.0.7/build/CPackSourceConfig.cmake | 86 llvm-toolchain-15-15.0.7/build/benchmarks/cmake_install.cmake | 44 llvm-toolchain-15-15.0.7/build/bin/flang-to-external-fc | 493 llvm-toolchain-15-15.0.7/build/bin/llvm-lit | 46 llvm-toolchain-15-15.0.7/build/bin/update_core_linalg_named_ops.sh | 32 llvm-toolchain-15-15.0.7/build/bindings/ocaml/all_backends/cmake_install.cmake | 66 llvm-toolchain-15-15.0.7/build/bindings/ocaml/analysis/cmake_install.cmake | 66 llvm-toolchain-15-15.0.7/build/bindings/ocaml/backends/X86_ocaml.c | 38 llvm-toolchain-15-15.0.7/build/bindings/ocaml/backends/cmake_install.cmake | 78 llvm-toolchain-15-15.0.7/build/bindings/ocaml/backends/llvm_X86.ml |9 llvm-toolchain-15-15.0.7/build/bindings/ocaml/backends/llvm_X86.mli | 18 llvm-toolchain-15-15.0.7/build/bindings/ocaml/bitreader/cmake_install.cmake
Bug#1032886: marked as done (unblock: ca-certificates/20230311)
Your message dated Mon, 13 Mar 2023 17:49:29 + with message-id and subject line unblock ca-certificates has caused the Debian Bug report #1032886, regarding unblock: ca-certificates/20230311 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.) -- 1032886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032886 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 X-Debbugs-Cc: ca-certifica...@packages.debian.org, jcris...@debian.org Control: affects -1 + src:ca-certificates Please unblock package ca-certificates [ Reason ] Update root CA store, and fix RC FTBFS bug. [ Impact ] Key package FTBFS, root store data is 2 years out of date. [ Tests ] N/A, the changes are 1) update to data files, 2) FTBFS fix by updating a build-time script, 3) trivial compat fix for update-ca-certificates. [ Risks ] Changes are reasonably minimal. [ 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 ca-certificates/20230311 Thanks, Julien --- End Message --- --- Begin Message --- Unblocked.--- End Message ---
Bug#1032874: marked as done (unblock: puppet-module-horizon/21.0.0-3)
Your message dated Mon, 13 Mar 2023 17:48:16 +
with message-id
and subject line unblock puppet-module-horizon
has caused the Debian Bug report #1032874,
regarding unblock: puppet-module-horizon/21.0.0-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.)
--
1032874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032874
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 puppet-module-horizon
I used to carry a patch in this package, fixing the path of
the wsgi.py script of Horizon. For a reason I can't explain,
this patch went away, and this broke this puppet module.
The latest Debian version of this package re-integrate the
patch correctly.
[ Reason ]
Fix path to wsgi.py
[ Impact ]
Broken puppet module, impossible to setup Horizon correctly
without the fix.
[ Tests ]
I manually tested this fixes the issue.
[ Risks ]
No risk, IMO.
[ 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 puppet-module-horizon/21.0.0-3
diff -Nru puppet-module-horizon-21.0.0/debian/changelog
puppet-module-horizon-21.0.0/debian/changelog
--- puppet-module-horizon-21.0.0/debian/changelog 2023-02-16
12:14:04.0 +0100
+++ puppet-module-horizon-21.0.0/debian/changelog 2023-03-06
14:12:07.0 +0100
@@ -1,3 +1,9 @@
+puppet-module-horizon (21.0.0-3) unstable; urgency=medium
+
+ * Fix bad path for Horizon's wsgi.py (due to wrong patch rebase).
+
+ -- Thomas Goirand Mon, 06 Mar 2023 14:12:07 +0100
+
puppet-module-horizon (21.0.0-2) unstable; urgency=medium
[ Olivier Chaze ]
diff -Nru
puppet-module-horizon-21.0.0/debian/patches/add_dns_v4_variables.patch
puppet-module-horizon-21.0.0/debian/patches/add_dns_v4_variables.patch
--- puppet-module-horizon-21.0.0/debian/patches/add_dns_v4_variables.patch
2023-02-16 12:14:04.0 +0100
+++ puppet-module-horizon-21.0.0/debian/patches/add_dns_v4_variables.patch
2023-03-06 14:12:07.0 +0100
@@ -3,8 +3,10 @@
Forwarded: no
Last-Update: 2022-12-06
puppet-module-horizon-21.0.0.orig/manifests/init.pp
-+++ puppet-module-horizon-21.0.0/manifests/init.pp
+Index: puppet-module-horizon/manifests/init.pp
+===
+--- puppet-module-horizon.orig/manifests/init.pp
puppet-module-horizon/manifests/init.pp
@@ -652,6 +652,8 @@ class horizon(
$horizon_upload_mode = undef,
$default_boot_source = undef,
diff -Nru puppet-module-horizon-21.0.0/debian/patches/debian-fixup.patch
puppet-module-horizon-21.0.0/debian/patches/debian-fixup.patch
--- puppet-module-horizon-21.0.0/debian/patches/debian-fixup.patch
2023-02-16 12:14:04.0 +0100
+++ puppet-module-horizon-21.0.0/debian/patches/debian-fixup.patch
2023-03-06 14:12:07.0 +0100
@@ -61,17 +61,18 @@
$memcache_package = 'python3-memcache'
$pymemcache_package = 'python3-pymemcache'
$designate_dashboard_package_name = 'python3-designate-dashboard'
-@@ -48,10 +46,15 @@ class horizon::params {
+@@ -48,10 +46,16 @@ class horizon::params {
'Debian': {
$package_name = 'openstack-dashboard-apache'
$httpd_config_file =
'/etc/apache2/sites-available/openstack-dashboard-alias-only.conf'
-+ $django_wsgi =
'/usr/share/openstack-dashboard/openstack_dashboard/wsgi.py'
++ $django_wsgi = '/usr/share/openstack-dashboard/wsgi.py'
+ $wsgi_user = 'www-data'
+ $wsgi_group= 'www-data'
}
default: {
$package_name = 'openstack-dashboard'
$httpd_config_file =
'/etc/apache2/conf-available/openstack-dashboard.conf'
++ $django_wsgi =
'/usr/share/openstack-dashboard/openstack_dashboard/wsgi.py'
+ $wsgi_user = 'horizon'
+ $wsgi_group= 'horizon'
}
--- End Message ---
--- Begin Message ---
Unblocked.--- End Message ---
Bug#1032873: marked as done (unblock: ceilometer-instance-poller/0.1.5-1)
Your message dated Mon, 13 Mar 2023 17:47:37 +
with message-id
and subject line unblock ceilometer-instance-poller
has caused the Debian Bug report #1032873,
regarding unblock: ceilometer-instance-poller/0.1.5-1
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.)
--
1032873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032873
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 ceilometer-instance-poller
The latest version 0.1.5 fixes a typo in both the README and the script
itself, that wrote:
"proudct" instead of "product"
Debdiff written inline at the bottom of this message.
Note that it's a "new upstream release", however:
- I'm the upstream... so fixing it in a new upstream release is less ugly
than adding a Debian patch
- The latest version only fixes this bug, no other changes included...
[ Impact ]
os_proudct_variant is kind of ugly, isn't it? :)
[ Tests ]
Manual test, it fixes it.
[ Risks ]
Not much...
[ 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 ceilometer-instance-poller/0.1.5-1
diff -Nru
ceilometer-instance-poller-0.1.4/ceilometer_instance_poller/instance_poller.py
ceilometer-instance-poller-0.1.5/ceilometer_instance_poller/instance_poller.py
---
ceilometer-instance-poller-0.1.4/ceilometer_instance_poller/instance_poller.py
2023-01-26 09:32:14.0 +0100
+++
ceilometer-instance-poller-0.1.5/ceilometer_instance_poller/instance_poller.py
2023-03-03 17:03:08.0 +0100
@@ -231,7 +231,7 @@
"os_version_major": 0,
"os_version_minor": 0,
"os_product_name": 'unknown',
-"os_proudct_variant": 'unknown',
+"os_product_variant": 'unknown',
}
else:
@@ -244,7 +244,7 @@
"os_version_major":
g.inspect_get_major_version(root),
"os_version_minor":
g.inspect_get_minor_version(root),
"os_product_name":
g.inspect_get_product_name(root),
-"os_proudct_variant":
g.inspect_get_product_variant(root),
+"os_product_variant":
g.inspect_get_product_variant(root),
}
g.umount_all()
g.close()
diff -Nru ceilometer-instance-poller-0.1.4/debian/changelog
ceilometer-instance-poller-0.1.5/debian/changelog
--- ceilometer-instance-poller-0.1.4/debian/changelog 2023-02-02
23:54:17.0 +0100
+++ ceilometer-instance-poller-0.1.5/debian/changelog 2023-03-03
17:03:43.0 +0100
@@ -1,3 +1,9 @@
+ceilometer-instance-poller (0.1.5-1) unstable; urgency=medium
+
+ * New upstream release (fixes minor typo in the json output).
+
+ -- Thomas Goirand Fri, 03 Mar 2023 17:03:43 +0100
+
ceilometer-instance-poller (0.1.4-2) unstable; urgency=medium
* Re-upload source-only.
diff -Nru ceilometer-instance-poller-0.1.4/README.md
ceilometer-instance-poller-0.1.5/README.md
--- ceilometer-instance-poller-0.1.4/README.md 2023-01-26 09:32:14.0
+0100
+++ ceilometer-instance-poller-0.1.5/README.md 2023-03-03 17:03:08.0
+0100
@@ -38,7 +38,7 @@
"os_version_major": 10,
"os_version_minor": 0,
"os_product_name": "Windows Server 2022 Datacenter Evaluation",
-"os_proudct_variant": "Server"
+"os_product_variant": "Server"
},
{
"resource_id": "9e92c509-0b48-43d0-a552-42de6f001e36",
@@ -48,7 +48,7 @@
"os_version_major": 11,
"os_version_minor": 2,
"os_product_name": "11.2",
-"os_proudct_variant": "unknown"
+"os_product_variant": "unknown"
}
]
```
--- End Message ---
--- Begin Message ---
Unblocked.--- End Message ---
Bug#1032871: marked as done (unblock: puppet-module-puppetlabs-haproxy/2.1.0-4)
Your message dated Mon, 13 Mar 2023 17:45:55 +
with message-id
and subject line unblock puppet-module-puppetlabs-haproxy
has caused the Debian Bug report #1032871,
regarding unblock: puppet-module-puppetlabs-haproxy/2.1.0-4
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.)
--
1032871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032871
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 puppet-module-puppetlabs-haproxy
[ Reason ]
The latest update fix haproxy version detection (ie: puppet fact).
[ Impact ]
Wrong haproxy detection and red line when the agent runs.
[ Tests ]
I did a manual check and it fixes the issue.
[ Risks ]
Not much risks: the fact is already broken in 2.1.0-4 and 2.1.0-5
fixes it. A broken fact doesn't break the puppet module.
[ 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 puppet-module-puppetlabs-haproxy/2.1.0-4
diff -Nru puppet-module-puppetlabs-haproxy-2.1.0/debian/changelog
puppet-module-puppetlabs-haproxy-2.1.0/debian/changelog
--- puppet-module-puppetlabs-haproxy-2.1.0/debian/changelog 2022-01-04
17:24:44.0 +0100
+++ puppet-module-puppetlabs-haproxy-2.1.0/debian/changelog 2023-03-13
09:01:56.0 +0100
@@ -1,3 +1,10 @@
+puppet-module-puppetlabs-haproxy (2.1.0-5) unstable; urgency=medium
+
+ * Add a fix for the haproxy fact, taking upstream latest version of the
+parsing.
+
+ -- Thomas Goirand Mon, 13 Mar 2023 09:01:56 +0100
+
puppet-module-puppetlabs-haproxy (2.1.0-4) unstable; urgency=medium
* Clean up update-alternatives handling (Closes: #989237).
diff -Nru
puppet-module-puppetlabs-haproxy-2.1.0/debian/patches/fix-haproxy-version-detection.patch
puppet-module-puppetlabs-haproxy-2.1.0/debian/patches/fix-haproxy-version-detection.patch
---
puppet-module-puppetlabs-haproxy-2.1.0/debian/patches/fix-haproxy-version-detection.patch
1970-01-01 01:00:00.0 +0100
+++
puppet-module-puppetlabs-haproxy-2.1.0/debian/patches/fix-haproxy-version-detection.patch
2023-03-13 09:01:56.0 +0100
@@ -0,0 +1,17 @@
+Description: Fix HAProxy version detection
+Author: Thomas Goirand
+Bug-Debian: https://bugs.debian.org/989237
+Origin: upstream
+Last-Update: 2023-03-13
+
+--- puppet-module-puppetlabs-haproxy-2.1.0.orig/lib/facter/haproxy_version.rb
puppet-module-puppetlabs-haproxy-2.1.0/lib/facter/haproxy_version.rb
+@@ -16,7 +16,7 @@ if defined?(Facter::Util::Resolution.whi
+ haproxy_version_cmd = 'haproxy -v 2>&1'
+ haproxy_version_result =
Facter::Util::Resolution.exec(haproxy_version_cmd)
+ setcode do
+-
haproxy_version_result.to_s.lines.first.strip.split(%r{HA-Proxy})[1].strip.split(%r{version})[1].strip.split(%r{((\d+\.){2,}\d+).*})[1]
++
haproxy_version_result.to_s.lines.first.strip.split(%r{HA?.Proxy})[1].strip.split(%r{version})[1].strip.split(%r{((\d+\.){2,}\d+).*})[1]
+ end
+ end
+ end
diff -Nru puppet-module-puppetlabs-haproxy-2.1.0/debian/patches/series
puppet-module-puppetlabs-haproxy-2.1.0/debian/patches/series
--- puppet-module-puppetlabs-haproxy-2.1.0/debian/patches/series
1970-01-01 01:00:00.0 +0100
+++ puppet-module-puppetlabs-haproxy-2.1.0/debian/patches/series
2023-03-13 09:01:56.0 +0100
@@ -0,0 +1 @@
+fix-haproxy-version-detection.patch
--- End Message ---
--- Begin Message ---
Unblocked.--- End Message ---
Bug#1032899: unblock: rocm-hipamd/5.2.3-6
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
X-Debbugs-Cc: debian...@lists.debian.org
Usertags: unblock
Control: affects -1 + src:rocm-hipamd
Please unblock package rocm-hipamd
rocm-hipamd 5.2.3-1 has been in testing for a few months now, so have
the following -2 and -3 revisions.
The three revisions since January were blocked from migrating by its
dependency src:llvm-toolchain-15, where a package split was introduced
to unstable, and one of the new packages was not allowed to migrate
because of an RC bug. This bug was recently fixed.
[ Reason ]
The changes in -2 to -6 are all just added patches, or packaging fixes.
[ Impact ]
The new versions are in far better shape: they've catched missing
dependencies, added patches, improved the build process, etc.
[ Tests ]
Manual tests, on the workstations of multpile maintainers. These
packages cannot be tested on debci because the tests require GPUs to work.
[ Risks ]
Given that there are no upstream changes other than added patches for
fixing this, the risks are minimal.
[ 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 rocm-hipamd/5.2.3-6diff -Nru rocm-hipamd-5.2.3/debian/changelog rocm-hipamd-5.2.3/debian/changelog
--- rocm-hipamd-5.2.3/debian/changelog 2022-10-20 21:20:33.0 +0200
+++ rocm-hipamd-5.2.3/debian/changelog 2023-03-10 23:38:51.0 +0100
@@ -1,3 +1,78 @@
+rocm-hipamd (5.2.3-6) unstable; urgency=medium
+
+ * Reduce arch to amd64, arm64, ppc64el
+ * libamdhip64-5: Add dependency on libamd-comgr2 (Closes: #1032677)
+ * Add myself to Uploaders
+ * Fix Maintainer (same list, different name)
+
+ -- Christian Kastner Fri, 10 Mar 2023 23:38:51 +0100
+
+rocm-hipamd (5.2.3-5) unstable; urgency=medium
+
+ * d/{libamdhip64-dev,rules}: fix version file
+Closes: #1031264
+ * add d/p/0020-replace-x86_64-with-variables.patch
+to fix build on aarch64
+ * d/control: add file to hipcc dependencies
+ * d/control: add dependencies for find_package(hip)
+Closes: #1031538
+ * add d/p/0021-fix-default-cmake-build-on-unsupported-gpus.patch
+to enable gpu arch autodetection with find_package(hip)
+ * d/not-installed: ignore doxygen docs
+ * d/p/000{4,8,9}*.patch: change hip-lang cmake files,
+to partially fix #1031540
+ * d/copyright: update copyright date
+ * d/control: add self to uploaders
+ * cleanup patch metadata
+
+ -- Cordell Bloor Sun, 19 Feb 2023 03:51:26 -0700
+
+rocm-hipamd (5.2.3-4) unstable; urgency=medium
+
+ * d/t/hipcc: also skip when no kfd driver is loaded.
+
+ -- Étienne Mollier Sat, 21 Jan 2023 12:54:49 +0100
+
+rocm-hipamd (5.2.3-3) unstable; urgency=medium
+
+ * d/control: build depends on libclang-rt-15-dev.
+ * d/control: hipcc depends on libclang-rt-15-dev.
+ * d/t/hipcc: add; basic script testing hipcc.
+ * d/t/hipconfig: add; script skipping hipconfig if no amdgpu is available.
+ * d/t/control: add hipcc to superficial autopkgtests.
+ * d/t/control: run the d/t/hipconfig test script instead of the command;
+this allows us to trigger conditions for when hardware is not available
+and the script has to be skipped.
+
+ -- Étienne Mollier Wed, 18 Jan 2023 20:35:17 +0100
+
+rocm-hipamd (5.2.3-2) unstable; urgency=medium
+
+ [ Cordell Bloor ]
+ * d/patches: add 0020-hipcc-remove-rpath-flags.patch
+Closes: #1021642
+ * d/rules: trim unnecessary rules
+ * d/rules: strip RUNPATH from libamdhip64.so
+ * debian/patches: backport 56b3260 from upstream
+Closes: #1021643
+ * d/rules: disable creation of duplicate files
+ * d/patches: fix search paths when building with g++
+ * d/patches: add 0002-fix-cmake-library-notfound-check.patch
+ * d/libamdhip64-dev.install: install /usr/share/hip/version
+
+ [ Étienne Mollier ]
+ * 0005-clang-15.patch: also adjust llc postfix.
+Thanks to Jakub Jaszewski
+ * d/t/control: check hipconfig doesn't output error messages.
+ * d/control: hipcc depends on rocminfo.
+ * d/control: declare compliance to standards version 4.6.2.
+ * d/copyright: update copyright year.
+ * d/rules: build tests in parallel.
+ * d/rules: set library path to find the freshly built library.
+ * d/rules: force run tests sequentially; avoid bus contention on the GPU.
+
+ -- Étienne Mollier Sat, 14 Jan 2023 11:16:01 +0100
+
rocm-hipamd (5.2.3-1) unstable; urgency=medium
* Migrate ROCm 5.2.3 to unstable.
diff -Nru rocm-hipamd-5.2.3/debian/control rocm-hipamd-5.2.3/debian/control
--- rocm-hipamd-5.2.3/debian/control2022-10-20 21:20:33.0 +0200
+++ rocm-hipamd-5.2.3/debian/control2023-03-10 23:38:51.0 +0100
@@ -6,12 +6,14 @@
Section: devel
Homepage: https://github.com/rocm-developer-tools/hipamd
Priority: optional
-Standards-Version: 4.6.1
+Standards-Version: 4.6.2
Vcs-Git: https://salsa.debian.org/rocm-team/rocm-hipamd.git
Vcs-Browser:
Bug#1032614: ddcutil: pre-approval request ddcutil-1.4.2-1 fixes bug #1031259
On 3/13/23 07:42, Sebastian Ramacher wrote: On 2023-03-13 07:25:41 -0400, Sanford Rockowitz wrote: On 3/13/23 05:33, Sebastian Ramacher wrote: On 2023-03-11 07:51:16 -0500, Sanford Rockowitz wrote: [Reason ] (Explain what the reason for the unblock request is.) As noted, the unblock request addresses bug #1031259. ddcutil requires driver i2c-dev. If it happens not to be built into the kernel, this entails post-installation system configuration. Despite extensive documentation and application warnings if the driver is not loaded, this can be challenging for inexperienced users. [ Impact ] (What is the impact for the user if the unblock isn't granted?) Manual post installation configuration will continue to be required as previously. [ Tests ] (What automated or manual tests cover the affected code?) None [ Risks ] (Discussion of the risks involved. E.g. code is trivial or complex, key package vs leaf package, alternatives available.) The changes are trivial, ensuring that driver i2c-dev is loaded if it is not already built into the kernel. Package libddccontrol0, an alternative to ddcutil for monitor control, installs file ddccontrol-i2c-dev.conf, which loads i2c-dev. The contents of that file, a single line containing "i2c-dev", is identical to the contents of the files to be installed by ddcutil. Additional examples of packages that install files in /user/lib/modules-load.d are fwupd, which installs file fwupd-msc.conf, and encryptfs-utils, which installs file ecryptfs.conf. The prpoposed changes also introduce a policy violation: /usr/lib/modules-load.d/libddcutil.conf installed in libddcutil4 is not versioned the same way as the shared library. See section 8.2 for more details. Cheers If the installed conf file were incorrect, the only effect would be an error in the system log, and manual user configuration would still be required as before. The only (potential) known dependency within Debian is from KDE PowerDevil. However, PowerDevil, as installed by Debian, is built with use of libddcutil if-tested out. (Recommended since its use of libddcutil is "proof of concept" level code.) [ 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 ] (Anything else the release team should know.) As I read section 8.2, there are two possibilities. The first is to version the name of the file installed in /usr/lib/modules-load.d, e.g. libddcutil4.conf for package libddcutil4. The second is to create an additional package, named e.g. libddcutil-aux, that installs libddcutil.conf and on which package libddcutil4 and successor packages libddcutilN depend. The former has the advantage that it doesn't introduce an additional package simply to install a single file, and the disadvantage that it relies on a naming convention for the installed libddcutilN.conf file, which could easily be overlooked when bumping the SONAME. As we're in hard freeze, option 2 is not an option for bookworm. A third alternative is to not install a modules-load.d conf file for libddcutil, and instead rely on packages using the shared library to install a conf file. But that would multiply the number of packages installing files in modules-load.d, and the potential for errors. That doesn't really sound like a solution to the bug. It would leak implementation details of libddcutil to all the reverse dependencies. Cheers Setting aside what's possible given the bookworm freeze, do you have a strong opinion as to whether the naming convention or separate package is preferable/acceptable? I don't feel strongly that the update has to go into bookworm. I wanted to address the "bug report" promptly, but the change is more of an enhancement. Nothing is really actually broken, it's just that a post installation step is necessary for some users, which it would be kind to avoid.
Processed: unblock: rocm-hipamd/5.2.3-6
Processing control commands: > affects -1 + src:rocm-hipamd Bug #1032899 [release.debian.org] unblock: rocm-hipamd/5.2.3-6 Added indication that 1032899 affects src:rocm-hipamd -- 1032899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Could I ask for unblock for 7 OBS plugins?
Dear Release Managers, obs-text-slideshow was accepted in Debian in 2021-10-10[1] and removed in 2022-10-17[2] (ROM; FTBFS, dead upstream). However, yesterday, a user detected that the package was present in its machine running testing and this plugin was causing an abnormal behavior on obs-studio. After removing the package, the system was stable. I would like to add 'Breaks: obs-text-slideshow (<= 1.5.2-3)' to seven plugins (obs-downstream-keyer, obs-move-transition, obs-scene-collection-manager, obs-scene-notes-dock, obs-source-clone, obs-source-copy, obs-transition-table) to force a removing of the obs-text-slideshow on users machines, avoiding future issues. What you think about this action? If ok for you, I will send an ask for unblock per package, considering all these packages are using trivial autopkgtests only. [1] https://tracker.debian.org/news/1275487/accepted-obs-text-slideshow-151-1-source-amd64-into-experimental-experimental/ [2] https://tracker.debian.org/news/1374607/removed-152-3-from-unstable/ Regards, Eriberto
Processed: unblock: libreswan/4.10-2
Processing control commands: > affects -1 + src:libreswan Bug #1032897 [release.debian.org] unblock: libreswan/4.10-2 Added indication that 1032897 affects src:libreswan -- 1032897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032885: unblock: debian-security-support/1:12+2023.03.05
On Mon, Mar 13, 2023 at 03:58:45PM +0100, Moritz Mühlenhoff wrote: > Am Mon, Mar 13, 2023 at 01:43:11PM +0100 schrieb Holger Levsen: > > * security-support-limited: > > - for golang and openjdk-17, point to the bookworm manual instead the > > one > > for bullseye. > That's wrong, though. (And the release notes need updating to, I'll file > a bug soonish): In Bookworm openjdk-17 is the default Java and fully > supported, but we need the equivalent note for openjdk-21 now. thanks, Moritz. I'll happily update d-s-s once the release manual is updated. or i could update d-s-s now too, if it's really just about replacing 17 with 21 in this line from security-support-limited : openjdk-17 See https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#openjdk-17 Are there any further updates expected from the security team's POV? -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ We need to learn to live with cholera. What is the alternative? Breaking up all streets, building drainage with toilets in every building? (@tadeas_) signature.asc Description: PGP signature
Bug#1032885: unblock: debian-security-support/1:12+2023.03.05
Am Mon, Mar 13, 2023 at 01:43:11PM +0100 schrieb Holger Levsen: > * security-support-limited: > - for golang and openjdk-17, point to the bookworm manual instead the one > for bullseye. That's wrong, though. (And the release notes need updating to, I'll file a bug soonish): In Bookworm openjdk-17 is the default Java and fully supported, but we need the equivalent note for openjdk-21 now. Cheers, Moritz
Bug#1032888: unblock: pubpaste/0.8.3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: pubpa...@packages.debian.org
Control: affects -1 + src:pubpaste
Please unblock package pubpaste
[ Reason ]
There are two serious crashes in pubpaste in testing right now, which
I haven't reported myself but have fixed, as the upstream.
[ Impact ]
Worst case: program crashes when doing a screenshot. Best case, it
works, but fails to copy unicode from Firefox.
[ Tests ]
I use this code daily, in graphical and console environment.
[ Risks ]
It's a leaf package, low popcon, low impact on the rest of the
ecosystem, really a convenience for the poor users.
[ 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 ]
I must apologize for this: I uploaded the package before the hard
freeze and miscalculated the transition time. I was expecting 0.8.3 to
land in bookworm before the hard freeze.
To be more accurate, I had the understanding that the freeze applied
to packages uploaded to sid *after* the hard freeze start. Maybe that
was engrained in my brain from a previous policy that had changed
since?
In any case, sorry about this! I hope you're not too swamped by all
the unblock requests.
(And yes, this package should really have autopkgtests, I only have
myself to blame for that one too...)
If this fails to unblock, I think it might be preferable to maintain
this through backports and simply remove it from bookworm.
unblock pubpaste/0.8.3
diff -Nru pubpaste-0.8.1/debian/changelog pubpaste-0.8.3/debian/changelog
--- pubpaste-0.8.1/debian/changelog 2023-02-21 11:27:35.0 -0500
+++ pubpaste-0.8.3/debian/changelog 2023-03-09 12:29:54.0 -0500
@@ -1,3 +1,16 @@
+pubpaste (0.8.3) unstable; urgency=medium
+
+ * fix crash when uploading badly-encoded unicode
+ * support for Firefox in HTML pastes
+
+ -- Antoine Beaupré Thu, 09 Mar 2023 12:29:54 -0500
+
+pubpaste (0.8.2) unstable; urgency=high
+
+ * fix regression in screenshots introduced in 0.8.1
+
+ -- Antoine Beaupré Mon, 06 Mar 2023 14:12:11 -0500
+
pubpaste (0.8.1) unstable; urgency=medium
* fix another crash when running without GTK
diff -Nru pubpaste-0.8.1/pubpaste.py pubpaste-0.8.3/pubpaste.py
--- pubpaste-0.8.1/pubpaste.py 2023-02-21 11:27:35.0 -0500
+++ pubpaste-0.8.3/pubpaste.py 2023-03-09 12:29:54.0 -0500
@@ -48,6 +48,11 @@
Type,
TypeVar,
)
+
+try:
+from typing import TypeAlias
+except ImportError:
+from typing_extensions import TypeAlias # Python 3.9 or earlier
from urllib.parse import quote
import yaml
@@ -76,7 +81,8 @@
gi.require_version("Gtk", "3.0")
from gi.repository import GLib, Gtk, Gdk, GdkPixbuf # type: ignore
-from Gtk import MessageDialog # type: ignore
+
+MessageDialog = Gtk.MessageDialog
except (ImportError, ValueError):
# "ValueError('Namespace %s not available' % namespace)"
gi = None
@@ -84,6 +90,7 @@
class MessageDialog: # type: ignore
pass
+
__epilog__ = """ This program will upload the provided files on the internet
and
notify the user when completed. The resulting URL will also be copied
to the clipboard. Preprocessors can do fancy things before (only
@@ -583,7 +590,7 @@
"""
-class TimerWindow(MessageDialog): # type: ignore[misc]
+class TimerWindow(MessageDialog): # type: ignore[misc, valid-type]
"""This widget will show a timer and a spinner in a window for the
given delay, then close the dialog.
@@ -1072,6 +1079,9 @@
return datetime.now().strftime("%Y-%m-%d"), secrets.token_urlsafe()
+SupportedExtensions: TypeAlias = Literal["png", "jpg", "txt", "html"]
+
+
class BaseClipboard:
def __init__(self, selection: Literal["CLIPBOARD", "PRIMARY"]) -> None:
"""configure the clipboard, based on whether the clipboard is PRIMARY
@@ -1088,7 +1098,7 @@
def put_image(self, path: bytes) -> bool:
raise NotImplementedError()
-def get(self) -> Tuple[Optional[bytes], Optional[Literal["png", "jpg",
"txt"]]]:
+def get(self) -> Tuple[Optional[bytes], Optional[SupportedExtensions]]:
raise NotImplementedError()
@@ -1181,7 +1191,7 @@
# we use _exit() to avoid firing atexit() in double
os._exit(0)
-def get(self) -> Tuple[Optional[bytes], Optional[Literal["png", "jpg",
"txt"]]]:
+def get(self) -> Tuple[Optional[bytes], Optional[Literal["png", "txt"]]]:
"""get the clipboard content, possible as an image or, failing that,
as text
GTK clipboards also support "rich text" and "URI", but I'm not
@@ -1243,12 +1253,12 @@
logging.warning("could not copy to clipboard with: %r", command)
return False
-def get(self) -> Tuple[Optional[bytes], Optional[Literal["png", "jpg",
"txt"]]]:
+def get(self) -> Tuple[Optional[bytes],
Processed: unblock: pubpaste/0.8.3
Processing control commands: > affects -1 + src:pubpaste Bug #1032888 [release.debian.org] unblock: pubpaste/0.8.3 Added indication that 1032888 affects src:pubpaste -- 1032888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unblock: llvm-toolchain-15/1:15.0.7-3
Processing control commands: > affects -1 + src:llvm-toolchain-15 Bug #1032887 [release.debian.org] unblock: llvm-toolchain-15/1:15.0.7-3 Added indication that 1032887 affects src:llvm-toolchain-15 -- 1032887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032887: unblock: llvm-toolchain-15/1:15.0.7-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: llvm-toolchain...@packages.debian.org Control: affects -1 + src:llvm-toolchain-15 Please unblock package llvm-toolchain-15 [ Reason ] Fixes autopkgtest issues and new version interesting for mesa (if I understood correctly) and fixes some wasm compiler bugs [ Impact ] Mesa issue ? [ Tests ] autopkgtest live on apt.llvm.org for a few days/weeks [ Risks ] Upstream is pretty careful with dot releases, so, i am not expecting regressions and I will be around [ 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 (quite long). can share if needed [ Other info ] It has been discussed with Sebastinas before this. unblock llvm-toolchain-15/1:15.0.7-3
Processed: unblock: ca-certificates/20230311
Processing control commands: > affects -1 + src:ca-certificates Bug #1032886 [release.debian.org] unblock: ca-certificates/20230311 Added indication that 1032886 affects src:ca-certificates -- 1032886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032886 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032886: unblock: ca-certificates/20230311
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: ca-certifica...@packages.debian.org, jcris...@debian.org Control: affects -1 + src:ca-certificates Please unblock package ca-certificates [ Reason ] Update root CA store, and fix RC FTBFS bug. [ Impact ] Key package FTBFS, root store data is 2 years out of date. [ Tests ] N/A, the changes are 1) update to data files, 2) FTBFS fix by updating a build-time script, 3) trivial compat fix for update-ca-certificates. [ Risks ] Changes are reasonably minimal. [ 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 ca-certificates/20230311 Thanks, Julien
Bug#1032885: unblock: debian-security-support/1:12+2023.03.05
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package debian-security-support, for some updated information about security-support-limited in bookworm and a new Romanian translation (plus 2 trivial packaging fixes). The complete diff is trivial and rather risk-free. [ 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 debian-security-support (1:12+2023.03.05) unstable; urgency=medium * security-support-limited: - for golang and openjdk-17, point to the bookworm manual instead the one for bullseye. - add mozjs102 based on package description (and #959804). - drop mozjs52 and mozjs60 as they were only present in buster. -- Holger Levsen Sun, 05 Mar 2023 20:39:38 +0100 debian-security-support (1:12+2022.08.23) unstable; urgency=medium * Add Romanian translation for debian-security-support debconf templates, thanks to Remus-Gabriel Chelu. Closes: #1031615. * Add Romanian translation for check-support-status, thanks to Remus-Gabriel Chelu. Closes: #1031617. * Fix mismatched lintian override, thanks lintian-brush. * Bump standards version to 4.6.2, no changes needed. -- Holger Levsen Sun, 05 Mar 2023 20:06:04 +0100 $ debdiff debian-security-support_12+2022.08.22.dsc debian-security-support_12+2023.03.05.dsc|diffstat debian/changelog | 21 ++ debian/control |2 - debian/debian-security-support.lintian-overrides |2 - debian/po/ro.po | 100 ++ po/ro.po | 142 security-support-limited |7 ++ 6 files changed, 268 insertions(+), 6 deletions(-) see attached full debdiff. unblock debian-security-support/1:12+2023.03.05 -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ Right-handed people commit 90% of all crime world-wide. diff -Nru debian-security-support-12+2022.08.22/debian/changelog debian-security-support-12+2023.03.05/debian/changelog --- debian-security-support-12+2022.08.22/debian/changelog 2022-08-22 14:59:42.0 +0200 +++ debian-security-support-12+2023.03.05/debian/changelog 2023-03-05 20:39:38.0 +0100 @@ -1,3 +1,24 @@ +debian-security-support (1:12+2023.03.05) unstable; urgency=medium + + * security-support-limited: +- for golang and openjdk-17, point to the bookworm manual instead the one + for bullseye. +- add mozjs102 based on package description (and #959804). +- drop mozjs52 and mozjs60 as they were only present in buster. + + -- Holger Levsen Sun, 05 Mar 2023 20:39:38 +0100 + +debian-security-support (1:12+2022.08.23) unstable; urgency=medium + + * Add Romanian translation for debian-security-support debconf templates, +thanks to Remus-Gabriel Chelu. Closes: #1031615. + * Add Romanian translation for check-support-status, thanks to +Remus-Gabriel Chelu. Closes: #1031617. + * Fix mismatched lintian override, thanks lintian-brush. + * Bump standards version to 4.6.2, no changes needed. + + -- Holger Levsen Sun, 05 Mar 2023 20:06:04 +0100 + debian-security-support (1:12+2022.08.22) unstable; urgency=medium * Revert "include /var/lib/debian-security-support in package.", thus diff -Nru debian-security-support-12+2022.08.22/debian/control debian-security-support-12+2023.03.05/debian/control --- debian-security-support-12+2022.08.22/debian/control 2022-08-22 13:17:16.0 +0200 +++ debian-security-support-12+2023.03.05/debian/control 2023-03-05 20:33:23.0 +0100 @@ -16,7 +16,7 @@ original-awk, po-debconf, xmlto, -Standards-Version: 4.6.1 +Standards-Version: 4.6.2 Rules-Requires-Root: no Vcs-Git: https://salsa.debian.org/debian/debian-security-support.git Vcs-Browser: https://salsa.debian.org/debian/debian-security-support diff -Nru debian-security-support-12+2022.08.22/debian/debian-security-support.lintian-overrides debian-security-support-12+2023.03.05/debian/debian-security-support.lintian-overrides --- debian-security-support-12+2022.08.22/debian/debian-security-support.lintian-overrides 2022-08-22 12:33:16.0 +0200 +++ debian-security-support-12+2023.03.05/debian/debian-security-support.lintian-overrides 2023-03-05 20:33:23.0 +0100 @@ -1,3 +1,3 @@ debian-security-support: no-debconf-config debian-security-support: postinst-uses-db-input -debian-security-support: debconf-is-not-a-registry
Bug#1032614: ddcutil: pre-approval request ddcutil-1.4.2-1 fixes bug #1031259
On 2023-03-13 07:25:41 -0400, Sanford Rockowitz wrote: > On 3/13/23 05:33, Sebastian Ramacher wrote: > > On 2023-03-11 07:51:16 -0500, Sanford Rockowitz wrote: > > > [Reason ] > > > (Explain what the reason for the unblock request is.) > > > As noted, the unblock request addresses bug #1031259. ddcutil requires > > > driver i2c-dev. If it happens not to be built into the kernel, this > > > entails > > > post-installation system configuration. Despite extensive documentation > > > and > > > application warnings if the driver is not loaded, this can be challenging > > > for inexperienced users. > > > > > > > [ Impact ] > > > > (What is the impact for the user if the unblock isn't granted?) > > > Manual post installation configuration will continue to be required as > > > previously. > > > > [ Tests ] > > > > (What automated or manual tests cover the affected code?) > > > None > > > > [ Risks ] > > > > (Discussion of the risks involved. E.g. code is trivial or > > > > complex, key package vs leaf package, alternatives available.) > > > The changes are trivial, ensuring that driver i2c-dev is loaded if it is > > > not > > > already built into the kernel. Package libddccontrol0, an alternative to > > > ddcutil for monitor control, installs file ddccontrol-i2c-dev.conf, which > > > loads i2c-dev. The contents of that file, a single line containing > > > "i2c-dev", is identical to the contents of the files to be installed by > > > ddcutil. Additional examples of packages that install files in > > > /user/lib/modules-load.d are fwupd, which installs file fwupd-msc.conf, > > > and > > > encryptfs-utils, which installs file ecryptfs.conf. > > The prpoposed changes also introduce a policy violation: > > /usr/lib/modules-load.d/libddcutil.conf installed in libddcutil4 is not > > versioned the same way as the shared library. See section 8.2 for more > > details. > > > > Cheers > > > > > If the installed conf file were incorrect, the only effect would be an > > > error > > > in the system log, and manual user configuration would still be required > > > as > > > before. > > > > > > The only (potential) known dependency within Debian is from KDE > > > PowerDevil. However, PowerDevil, as installed by Debian, is built with > > > use > > > of libddcutil if-tested out. (Recommended since its use of libddcutil is > > > "proof of concept" level code.) > > > > > > > [ 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 ] > > > > (Anything else the release team should know.) > > As I read section 8.2, there are two possibilities. The first is to version > the name of the file installed in /usr/lib/modules-load.d, e.g. > libddcutil4.conf for package libddcutil4. The second is to create an > additional package, named e.g. libddcutil-aux, that installs libddcutil.conf > and on which package libddcutil4 and successor packages libddcutilN depend. > The former has the advantage that it doesn't introduce an additional package > simply to install a single file, and the disadvantage that it relies on a > naming convention for the installed libddcutilN.conf file, which could > easily be overlooked when bumping the SONAME. As we're in hard freeze, option 2 is not an option for bookworm. > A third alternative is to not install a modules-load.d conf file for > libddcutil, and instead rely on packages using the shared library to install > a conf file. But that would multiply the number of packages installing > files in modules-load.d, and the potential for errors. That doesn't really sound like a solution to the bug. It would leak implementation details of libddcutil to all the reverse dependencies. Cheers -- Sebastian Ramacher
Bug#1032855: marked as done (unblock: scilab/6.1.1+dfsg2-5)
Your message dated Mon, 13 Mar 2023 11:34:24 + with message-id and subject line unblock scilab has caused the Debian Bug report #1032855, regarding unblock: scilab/6.1.1+dfsg2-5 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.) -- 1032855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032855 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 X-Debbugs-Cc: sci...@packages.debian.org Control: affects -1 + src:scilab Dear Release Team, Could you please unblock the key package scilab/6.1.1+dfsg2-5? [ Reason ] - scilab/6.1.1+dfsg2-4 is absolutely unusable as it cannot even start. - It FTBFS. - It looks for versioned artifacts so it breaks everytime a dependency is updated. [ Impact ] Staying with version 6.1.1+dfsg2-4 does not allow one to use scilab even in the naked CLI flavor. [ Tests ] I installed the version 6.1.1+dfsg2-5 on a Bookworm system: - scilab-cli and scilab-adv-cli work plainly, except for plots (bugs in dependencies); - the GUI scilab does not work. Blockers: bugs in dependency libjogl2-java and others still to investigate, as log messages are terse. [ Risks ] The changes are simple, can be easily grasped through the documented patches I added. scilab has only one reverse dependency which is not a Blends metapackage: cantor-backend-scilab, which is already broken as scilab/6.1.1+dfsg2-4 does not start. [ 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 scilab/6.1.1+dfsg2-5 Best, -- Pierre diff -Nru scilab-6.1.1+dfsg2/debian/changelog scilab-6.1.1+dfsg2/debian/changelog --- scilab-6.1.1+dfsg2/debian/changelog 2022-08-16 11:55:44.0 +0200 +++ scilab-6.1.1+dfsg2/debian/changelog 2023-03-11 16:23:07.0 +0100 @@ -1,3 +1,25 @@ +scilab (6.1.1+dfsg2-5) unstable; urgency=medium + + * Team upload + * Raising Standards version to 4.6.2 (no change) + * Adding missing dependencies on libfreehep-graphicsio-java and +libfreehep-util-java + * Fixing the FTBFS occurring during the doc build + * Enabling starting with OpenJDK 17 (Closes: #1012099) + * Selecting unversioned jars instead of versioned ones in the configure phase +(Closes: #1030205) + * Refreshing patches + * Removing unneeded older-than versioned dependencies + * Update lintian override info to new format: ++ debian/source/lintian-overrides: line 2, 4 ++ debian/scilab-minimal-bin.lintian-overrides: line 4 + * debian/copyright: use spaces rather than tabs to start continuation lines. + * Update renamed lintian tag names in lintian overrides. + * Set upstream metadata fields: Repository-Browse. + * Fix day-of-week for changelog entry 5.0.3-1. + + -- Pierre Gruet Sat, 11 Mar 2023 16:23:07 +0100 + scilab (6.1.1+dfsg2-4) unstable; urgency=medium * Add patch to disambiguate pause (Closes: #1017283). @@ -1348,7 +1370,7 @@ * Package moved to main since Scilab is free (CeCILL license) * modelicac, intersci and scilab manpages added - -- Sylvestre Ledru Fri, 1 Oct 2008 13:37:08 +0200 + -- Sylvestre Ledru Wed, 01 Oct 2008 13:37:08 +0200 scilab (4.1.2-6) unstable; urgency=low diff -Nru scilab-6.1.1+dfsg2/debian/control scilab-6.1.1+dfsg2/debian/control --- scilab-6.1.1+dfsg2/debian/control 2022-08-16 11:55:44.0 +0200 +++ scilab-6.1.1+dfsg2/debian/control 2023-03-10 23:21:05.0 +0100 @@ -3,38 +3,36 @@ Priority: optional Maintainer: Debian Science Team Uploaders: Julien Puydt -Build-Depends: debhelper-compat (= 13), gfortran, time, - default-jdk, chrpath, ocaml-nox (>= 3.11.2-3), libnum-ocaml-dev, fakeroot, - tcl-dev, tk-dev, libxml2-dev, libpcre3-dev, libcurl4-openssl-dev, - gettext, libreadline-dev, pkg-config, procps, dpkg-dev (>= 1.16.0), +Build-Depends: debhelper-compat (= 13), gfortran, time, default-jdk, chrpath, + ocaml-nox, libnum-ocaml-dev, fakeroot, tcl-dev, tk-dev, libxml2-dev, + libpcre3-dev, libcurl4-openssl-dev, gettext, libreadline-dev, pkg-config, + procps, dpkg-dev, # numerical libraries libblas-dev | librefblas3-dev | libatlas-base-dev, liblapack-dev, - libarpack2-dev (>= 3.0), libeigen3-dev, + libarpack2-dev, libeigen3-dev, # Java deps - default-jre-headless, libflexdock-java (>= 1.2.3), libjogl2-java (>= 2.3.2), - libgl1-mesa-dev, libjrosetta-java (>= 1.0.1), ant, libjgoodies-looks-java, - libskinlf-java, liblucene4.10-java, libactivation-java, libjaxb-java, +
Bug#1032878: marked as done (unblock: groff/1.22.4-10)
Your message dated Mon, 13 Mar 2023 11:24:14 +
with message-id
and subject line unblock groff
has caused the Debian Bug report #1032878,
regarding unblock: groff/1.22.4-10
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.)
--
1032878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032878
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
X-Debbugs-Cc: G. Branden Robinson
Please unblock package groff.
[ Reason ]
This upload, made before the full freeze but not quite in time to land
in testing before that, was in anticipation of documents being written
during the lifetime of bookworm that use new features of groff 1.23.
groff 1.23 itself will be too late for bookworm, but the added trivial
implementations of .MR and .cp will avoid some bad formatting
consequences (especially .MR, which would otherwise cause formatted text
not to be rendered at all).
[ Impact ]
Relatively minimal impact immediately, but as later updates are landed
in bookworm it's easy to foresee us ending up with misformatted man
pages.
[ Tests ]
No automatic tests. I've eyeballed some common man pages to ensure
they're still rendered reasonably.
[ Risks ]
Key package, and understanding the code does require an understanding of
*roff which is esoteric knowledge these days. However, it's essentially
defining two new names (one macro, one "register" or variable), which is
pretty harmless.
[ 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
unblock groff/1.22.4-10
Thanks,
--
Colin Watson (he/him) [cjwat...@debian.org]
diff -Nru groff-1.22.4/debian/.git-dpm groff-1.22.4/debian/.git-dpm
--- groff-1.22.4/debian/.git-dpm2022-11-15 15:30:39.0 +
+++ groff-1.22.4/debian/.git-dpm2023-03-07 09:38:03.0 +
@@ -1,6 +1,6 @@
# see git-dpm(1) from git-dpm package
-0c048e31d8ca2f23d799dc97789a6591e05c8a5b
-0c048e31d8ca2f23d799dc97789a6591e05c8a5b
+f2739609ee9db7e095761472c2b89518866f7cfb
+f2739609ee9db7e095761472c2b89518866f7cfb
ef16ff6c6e7ff7744b318b73feaeb9a2fadaa748
ef16ff6c6e7ff7744b318b73feaeb9a2fadaa748
groff_1.22.4.orig.tar.gz
diff -Nru groff-1.22.4/debian/changelog groff-1.22.4/debian/changelog
--- groff-1.22.4/debian/changelog 2022-11-15 15:30:39.0 +
+++ groff-1.22.4/debian/changelog 2023-03-07 09:38:03.0 +
@@ -1,3 +1,15 @@
+groff (1.22.4-10) unstable; urgency=medium
+
+ [ Colin Watson ]
+ * Set upstream metadata fields: Repository-Browse.
+
+ [ G. Branden Robinson ]
+ * debian/patches/add-groff-1.23-forward-compatibility.patch: Prevent
+formatter warnings and dropped man(7) document text when encountering
+documents written using new features of groff 1.23.
+
+ -- Colin Watson Tue, 07 Mar 2023 09:38:03 +
+
groff (1.22.4-9) unstable; urgency=medium
* Remove dh_missing override, no longer needed with debhelper v13.
diff -Nru
groff-1.22.4/debian/patches/add-groff-1.23-forward-compatibility.patch
groff-1.22.4/debian/patches/add-groff-1.23-forward-compatibility.patch
--- groff-1.22.4/debian/patches/add-groff-1.23-forward-compatibility.patch
1970-01-01 01:00:00.0 +0100
+++ groff-1.22.4/debian/patches/add-groff-1.23-forward-compatibility.patch
2023-03-07 09:38:03.0 +
@@ -0,0 +1,51 @@
+From f2739609ee9db7e095761472c2b89518866f7cfb Mon Sep 17 00:00:00 2001
+From: "G. Branden Robinson"
+Date: Sat, 4 Mar 2023 19:20:45 -0600
+Subject: tmac/{man.local,troffrc}: Add groff 1.23 fw compat
+
+Patch-Name: add-groff-1.23-forward-compatibility.patch
+---
+ tmac/man.local | 12
+ tmac/troffrc | 9 +
+ 2 files changed, 21 insertions(+)
+
+diff --git a/tmac/man.local b/tmac/man.local
+index 3030a84a..563d9a71 100644
+--- a/tmac/man.local
b/tmac/man.local
+@@ -2,3 +2,15 @@
+ .\"
+ .\" This file is loaded after an-old.tmac.
+ .\" Put any local modifications to an-old.tmac here.
++.\"
++.\" for forward compatibility with a groff 1.23 feature
++.if !d MR \{\
++. \" Provide a simple implementation of the new `MR` macro to avoid
++. \" loss of formatted text.
++. de MR
++.ie \\n(.$=1 \
++. I \%\\$1
++.el \
++. IR \%\\$1 (\\$2)\\$3
++. .
++.\}
+diff --git a/tmac/troffrc b/tmac/troffrc
+index 6dca1dbd..845352b2 100644
+--- a/tmac/troffrc
b/tmac/troffrc
+@@ -3,6 +3,15 @@
+ .\" This is tested by pic.
+ .nr 0p 0
+
Bug#1032614: ddcutil: pre-approval request ddcutil-1.4.2-1 fixes bug #1031259
On 3/13/23 05:33, Sebastian Ramacher wrote: On 2023-03-11 07:51:16 -0500, Sanford Rockowitz wrote: [Reason ] (Explain what the reason for the unblock request is.) As noted, the unblock request addresses bug #1031259. ddcutil requires driver i2c-dev. If it happens not to be built into the kernel, this entails post-installation system configuration. Despite extensive documentation and application warnings if the driver is not loaded, this can be challenging for inexperienced users. [ Impact ] (What is the impact for the user if the unblock isn't granted?) Manual post installation configuration will continue to be required as previously. [ Tests ] (What automated or manual tests cover the affected code?) None [ Risks ] (Discussion of the risks involved. E.g. code is trivial or complex, key package vs leaf package, alternatives available.) The changes are trivial, ensuring that driver i2c-dev is loaded if it is not already built into the kernel. Package libddccontrol0, an alternative to ddcutil for monitor control, installs file ddccontrol-i2c-dev.conf, which loads i2c-dev. The contents of that file, a single line containing "i2c-dev", is identical to the contents of the files to be installed by ddcutil. Additional examples of packages that install files in /user/lib/modules-load.d are fwupd, which installs file fwupd-msc.conf, and encryptfs-utils, which installs file ecryptfs.conf. The prpoposed changes also introduce a policy violation: /usr/lib/modules-load.d/libddcutil.conf installed in libddcutil4 is not versioned the same way as the shared library. See section 8.2 for more details. Cheers If the installed conf file were incorrect, the only effect would be an error in the system log, and manual user configuration would still be required as before. The only (potential) known dependency within Debian is from KDE PowerDevil. However, PowerDevil, as installed by Debian, is built with use of libddcutil if-tested out. (Recommended since its use of libddcutil is "proof of concept" level code.) [ 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 ] (Anything else the release team should know.) As I read section 8.2, there are two possibilities. The first is to version the name of the file installed in /usr/lib/modules-load.d, e.g. libddcutil4.conf for package libddcutil4. The second is to create an additional package, named e.g. libddcutil-aux, that installs libddcutil.conf and on which package libddcutil4 and successor packages libddcutilN depend. The former has the advantage that it doesn't introduce an additional package simply to install a single file, and the disadvantage that it relies on a naming convention for the installed libddcutilN.conf file, which could easily be overlooked when bumping the SONAME. A third alternative is to not install a modules-load.d conf file for libddcutil, and instead rely on packages using the shared library to install a conf file. But that would multiply the number of packages installing files in modules-load.d, and the potential for errors. Is one alternative clearly preferable to the others from the Debian perspective? Thank you. Whether or not this change makes it into bookworm, the review process has been helpful.
Bug#1032863: marked as done (unblock: mitmproxy/8.1.1-2)
Your message dated Mon, 13 Mar 2023 09:34:23 + with message-id and subject line unblock mitmproxy has caused the Debian Bug report #1032863, regarding unblock: mitmproxy/8.1.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.) -- 1032863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032863 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 X-Debbugs-Cc: mitmpr...@packages.debian.org Control: affects -1 + mitmproxy Dear Release Team, Could you unblock package mitmproxy/8.1.1-2, in this version it applies an upstream patch to fix Python 3.11 compatibility, otherwise the package would fail to start, although the original bug report (#1031787) wasn't marked RC. Regards, Aron diff -Nru mitmproxy-8.1.1/debian/changelog mitmproxy-8.1.1/debian/changelog --- mitmproxy-8.1.1/debian/changelog2023-02-06 00:00:42.0 +0800 +++ mitmproxy-8.1.1/debian/changelog2023-03-03 01:21:00.0 +0800 @@ -1,3 +1,10 @@ +mitmproxy (8.1.1-2) unstable; urgency=medium + + * Team upload. + * Add upstream patch to fix Python 3.11 compatibility (Closes: #1031787) + + -- Aron Xu Fri, 03 Mar 2023 01:21:00 +0800 + mitmproxy (8.1.1-1) unstable; urgency=high * Team upload diff -Nru mitmproxy-8.1.1/debian/patches/0007-use-default_factory-for-parser_options-field-5476.patch mitmproxy-8.1.1/debian/patches/0007-use-default_factory-for-parser_options-field-5476.patch --- mitmproxy-8.1.1/debian/patches/0007-use-default_factory-for-parser_options-field-5476.patch 1970-01-01 08:00:00.0 +0800 +++ mitmproxy-8.1.1/debian/patches/0007-use-default_factory-for-parser_options-field-5476.patch 2023-03-03 01:20:48.0 +0800 @@ -0,0 +1,34 @@ +From 55a64b7ad993fd52fbff19f33e3c6e153b3e8d9b Mon Sep 17 00:00:00 2001 +From: rathann +Date: Sat, 23 Jul 2022 10:15:03 +0200 +Subject: [PATCH] use default_factory for parser_options field (#5476) + +* use default_factory for field parser_options + +When running mitmproxy under python 3.11, the following exception +is thrown otherwise: +``` +ValueError: mutable default for field parser_options is not allowed: use default_factory +``` + +Fixes #5474. +--- + mitmproxy/contentviews/grpc.py | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/mitmproxy/contentviews/grpc.py b/mitmproxy/contentviews/grpc.py +index a5ef99708..5c73220c8 100644 +--- a/mitmproxy/contentviews/grpc.py b/mitmproxy/contentviews/grpc.py +@@ -951,7 +951,7 @@ def format_grpc( + + @dataclass + class ViewConfig: +-parser_options: ProtoParser.ParserOptions = ProtoParser.ParserOptions() ++parser_options: ProtoParser.ParserOptions = field(default_factory=ProtoParser.ParserOptions) + parser_rules: list[ProtoParser.ParserRule] = field(default_factory=list) + + +-- +2.30.2 + diff -Nru mitmproxy-8.1.1/debian/patches/series mitmproxy-8.1.1/debian/patches/series --- mitmproxy-8.1.1/debian/patches/series 2023-02-06 00:00:42.0 +0800 +++ mitmproxy-8.1.1/debian/patches/series 2023-03-03 01:19:49.0 +0800 @@ -3,3 +3,4 @@ 0004-Remove-test_cibuild.py.patch 0005-Remove-test_readfile.py.patch 0006-Delete-asciinema-for-which-we-only-have-minified-ver.patch +0007-use-default_factory-for-parser_options-field-5476.patch signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Unblocked.--- End Message ---
Bug#1032614: ddcutil: pre-approval request ddcutil-1.4.2-1 fixes bug #1031259
On 2023-03-11 07:51:16 -0500, Sanford Rockowitz wrote: > > [Reason ] > (Explain what the reason for the unblock request is.) > As noted, the unblock request addresses bug #1031259. ddcutil requires > driver i2c-dev. If it happens not to be built into the kernel, this entails > post-installation system configuration. Despite extensive documentation and > application warnings if the driver is not loaded, this can be challenging > for inexperienced users. > > > > > [ Impact ] > > (What is the impact for the user if the unblock isn't granted?) > > Manual post installation configuration will continue to be required as > previously. > > > > [ Tests ] > > (What automated or manual tests cover the affected code?) > > None > > > > [ Risks ] > > (Discussion of the risks involved. E.g. code is trivial or > > complex, key package vs leaf package, alternatives available.) > > The changes are trivial, ensuring that driver i2c-dev is loaded if it is not > already built into the kernel. Package libddccontrol0, an alternative to > ddcutil for monitor control, installs file ddccontrol-i2c-dev.conf, which > loads i2c-dev. The contents of that file, a single line containing > "i2c-dev", is identical to the contents of the files to be installed by > ddcutil. Additional examples of packages that install files in > /user/lib/modules-load.d are fwupd, which installs file fwupd-msc.conf, and > encryptfs-utils, which installs file ecryptfs.conf. The prpoposed changes also introduce a policy violation: /usr/lib/modules-load.d/libddcutil.conf installed in libddcutil4 is not versioned the same way as the shared library. See section 8.2 for more details. Cheers > > If the installed conf file were incorrect, the only effect would be an error > in the system log, and manual user configuration would still be required as > before. > > The only (potential) known dependency within Debian is from KDE > PowerDevil. However, PowerDevil, as installed by Debian, is built with use > of libddcutil if-tested out. (Recommended since its use of libddcutil is > "proof of concept" level code.) > > > > > [ 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 ] > > (Anything else the release team should know.) -- Sebastian Ramacher
Bug#1032878: unblock: groff/1.22.4-10
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: G. Branden Robinson
Please unblock package groff.
[ Reason ]
This upload, made before the full freeze but not quite in time to land
in testing before that, was in anticipation of documents being written
during the lifetime of bookworm that use new features of groff 1.23.
groff 1.23 itself will be too late for bookworm, but the added trivial
implementations of .MR and .cp will avoid some bad formatting
consequences (especially .MR, which would otherwise cause formatted text
not to be rendered at all).
[ Impact ]
Relatively minimal impact immediately, but as later updates are landed
in bookworm it's easy to foresee us ending up with misformatted man
pages.
[ Tests ]
No automatic tests. I've eyeballed some common man pages to ensure
they're still rendered reasonably.
[ Risks ]
Key package, and understanding the code does require an understanding of
*roff which is esoteric knowledge these days. However, it's essentially
defining two new names (one macro, one "register" or variable), which is
pretty harmless.
[ 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
unblock groff/1.22.4-10
Thanks,
--
Colin Watson (he/him) [cjwat...@debian.org]
diff -Nru groff-1.22.4/debian/.git-dpm groff-1.22.4/debian/.git-dpm
--- groff-1.22.4/debian/.git-dpm2022-11-15 15:30:39.0 +
+++ groff-1.22.4/debian/.git-dpm2023-03-07 09:38:03.0 +
@@ -1,6 +1,6 @@
# see git-dpm(1) from git-dpm package
-0c048e31d8ca2f23d799dc97789a6591e05c8a5b
-0c048e31d8ca2f23d799dc97789a6591e05c8a5b
+f2739609ee9db7e095761472c2b89518866f7cfb
+f2739609ee9db7e095761472c2b89518866f7cfb
ef16ff6c6e7ff7744b318b73feaeb9a2fadaa748
ef16ff6c6e7ff7744b318b73feaeb9a2fadaa748
groff_1.22.4.orig.tar.gz
diff -Nru groff-1.22.4/debian/changelog groff-1.22.4/debian/changelog
--- groff-1.22.4/debian/changelog 2022-11-15 15:30:39.0 +
+++ groff-1.22.4/debian/changelog 2023-03-07 09:38:03.0 +
@@ -1,3 +1,15 @@
+groff (1.22.4-10) unstable; urgency=medium
+
+ [ Colin Watson ]
+ * Set upstream metadata fields: Repository-Browse.
+
+ [ G. Branden Robinson ]
+ * debian/patches/add-groff-1.23-forward-compatibility.patch: Prevent
+formatter warnings and dropped man(7) document text when encountering
+documents written using new features of groff 1.23.
+
+ -- Colin Watson Tue, 07 Mar 2023 09:38:03 +
+
groff (1.22.4-9) unstable; urgency=medium
* Remove dh_missing override, no longer needed with debhelper v13.
diff -Nru
groff-1.22.4/debian/patches/add-groff-1.23-forward-compatibility.patch
groff-1.22.4/debian/patches/add-groff-1.23-forward-compatibility.patch
--- groff-1.22.4/debian/patches/add-groff-1.23-forward-compatibility.patch
1970-01-01 01:00:00.0 +0100
+++ groff-1.22.4/debian/patches/add-groff-1.23-forward-compatibility.patch
2023-03-07 09:38:03.0 +
@@ -0,0 +1,51 @@
+From f2739609ee9db7e095761472c2b89518866f7cfb Mon Sep 17 00:00:00 2001
+From: "G. Branden Robinson"
+Date: Sat, 4 Mar 2023 19:20:45 -0600
+Subject: tmac/{man.local,troffrc}: Add groff 1.23 fw compat
+
+Patch-Name: add-groff-1.23-forward-compatibility.patch
+---
+ tmac/man.local | 12
+ tmac/troffrc | 9 +
+ 2 files changed, 21 insertions(+)
+
+diff --git a/tmac/man.local b/tmac/man.local
+index 3030a84a..563d9a71 100644
+--- a/tmac/man.local
b/tmac/man.local
+@@ -2,3 +2,15 @@
+ .\"
+ .\" This file is loaded after an-old.tmac.
+ .\" Put any local modifications to an-old.tmac here.
++.\"
++.\" for forward compatibility with a groff 1.23 feature
++.if !d MR \{\
++. \" Provide a simple implementation of the new `MR` macro to avoid
++. \" loss of formatted text.
++. de MR
++.ie \\n(.$=1 \
++. I \%\\$1
++.el \
++. IR \%\\$1 (\\$2)\\$3
++. .
++.\}
+diff --git a/tmac/troffrc b/tmac/troffrc
+index 6dca1dbd..845352b2 100644
+--- a/tmac/troffrc
b/tmac/troffrc
+@@ -3,6 +3,15 @@
+ .\" This is tested by pic.
+ .nr 0p 0
+ .
++.\" for forward compatibility with a groff 1.23 feature
++.if !r .cp \{\
++. \" Construct an equivalent of groff 1.23's .cp register. Any
++. \" unlikely two-character register name will do.
++. nr }{ \n(.C
++. do nr .cp \n(}{
++. rr }{
++.\}
++.
+ .\" Load composite mappings.
+ .do mso composite.tmac
+ .
diff -Nru groff-1.22.4/debian/patches/series groff-1.22.4/debian/patches/series
--- groff-1.22.4/debian/patches/series 2022-11-15 15:30:39.0 +
+++ groff-1.22.4/debian/patches/series 2023-03-07 09:38:03.0 +
@@ -14,3 +14,4 @@
document-sgr.patch
destructor-segv.patch
clamp-negative-tab-stop-positions.patch
+add-groff-1.23-forward-compatibility.patch
diff -Nru groff-1.22.4/debian/upstream/metadata
Bug#1032873: unblock: ceilometer-instance-poller/0.1.5-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package ceilometer-instance-poller
The latest version 0.1.5 fixes a typo in both the README and the script
itself, that wrote:
"proudct" instead of "product"
Debdiff written inline at the bottom of this message.
Note that it's a "new upstream release", however:
- I'm the upstream... so fixing it in a new upstream release is less ugly
than adding a Debian patch
- The latest version only fixes this bug, no other changes included...
[ Impact ]
os_proudct_variant is kind of ugly, isn't it? :)
[ Tests ]
Manual test, it fixes it.
[ Risks ]
Not much...
[ 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 ceilometer-instance-poller/0.1.5-1
diff -Nru
ceilometer-instance-poller-0.1.4/ceilometer_instance_poller/instance_poller.py
ceilometer-instance-poller-0.1.5/ceilometer_instance_poller/instance_poller.py
---
ceilometer-instance-poller-0.1.4/ceilometer_instance_poller/instance_poller.py
2023-01-26 09:32:14.0 +0100
+++
ceilometer-instance-poller-0.1.5/ceilometer_instance_poller/instance_poller.py
2023-03-03 17:03:08.0 +0100
@@ -231,7 +231,7 @@
"os_version_major": 0,
"os_version_minor": 0,
"os_product_name": 'unknown',
-"os_proudct_variant": 'unknown',
+"os_product_variant": 'unknown',
}
else:
@@ -244,7 +244,7 @@
"os_version_major":
g.inspect_get_major_version(root),
"os_version_minor":
g.inspect_get_minor_version(root),
"os_product_name":
g.inspect_get_product_name(root),
-"os_proudct_variant":
g.inspect_get_product_variant(root),
+"os_product_variant":
g.inspect_get_product_variant(root),
}
g.umount_all()
g.close()
diff -Nru ceilometer-instance-poller-0.1.4/debian/changelog
ceilometer-instance-poller-0.1.5/debian/changelog
--- ceilometer-instance-poller-0.1.4/debian/changelog 2023-02-02
23:54:17.0 +0100
+++ ceilometer-instance-poller-0.1.5/debian/changelog 2023-03-03
17:03:43.0 +0100
@@ -1,3 +1,9 @@
+ceilometer-instance-poller (0.1.5-1) unstable; urgency=medium
+
+ * New upstream release (fixes minor typo in the json output).
+
+ -- Thomas Goirand Fri, 03 Mar 2023 17:03:43 +0100
+
ceilometer-instance-poller (0.1.4-2) unstable; urgency=medium
* Re-upload source-only.
diff -Nru ceilometer-instance-poller-0.1.4/README.md
ceilometer-instance-poller-0.1.5/README.md
--- ceilometer-instance-poller-0.1.4/README.md 2023-01-26 09:32:14.0
+0100
+++ ceilometer-instance-poller-0.1.5/README.md 2023-03-03 17:03:08.0
+0100
@@ -38,7 +38,7 @@
"os_version_major": 10,
"os_version_minor": 0,
"os_product_name": "Windows Server 2022 Datacenter Evaluation",
-"os_proudct_variant": "Server"
+"os_product_variant": "Server"
},
{
"resource_id": "9e92c509-0b48-43d0-a552-42de6f001e36",
@@ -48,7 +48,7 @@
"os_version_major": 11,
"os_version_minor": 2,
"os_product_name": "11.2",
-"os_proudct_variant": "unknown"
+"os_product_variant": "unknown"
}
]
```
Bug#1032874: unblock: puppet-module-horizon/21.0.0-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package puppet-module-horizon
I used to carry a patch in this package, fixing the path of
the wsgi.py script of Horizon. For a reason I can't explain,
this patch went away, and this broke this puppet module.
The latest Debian version of this package re-integrate the
patch correctly.
[ Reason ]
Fix path to wsgi.py
[ Impact ]
Broken puppet module, impossible to setup Horizon correctly
without the fix.
[ Tests ]
I manually tested this fixes the issue.
[ Risks ]
No risk, IMO.
[ 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 puppet-module-horizon/21.0.0-3
diff -Nru puppet-module-horizon-21.0.0/debian/changelog
puppet-module-horizon-21.0.0/debian/changelog
--- puppet-module-horizon-21.0.0/debian/changelog 2023-02-16
12:14:04.0 +0100
+++ puppet-module-horizon-21.0.0/debian/changelog 2023-03-06
14:12:07.0 +0100
@@ -1,3 +1,9 @@
+puppet-module-horizon (21.0.0-3) unstable; urgency=medium
+
+ * Fix bad path for Horizon's wsgi.py (due to wrong patch rebase).
+
+ -- Thomas Goirand Mon, 06 Mar 2023 14:12:07 +0100
+
puppet-module-horizon (21.0.0-2) unstable; urgency=medium
[ Olivier Chaze ]
diff -Nru
puppet-module-horizon-21.0.0/debian/patches/add_dns_v4_variables.patch
puppet-module-horizon-21.0.0/debian/patches/add_dns_v4_variables.patch
--- puppet-module-horizon-21.0.0/debian/patches/add_dns_v4_variables.patch
2023-02-16 12:14:04.0 +0100
+++ puppet-module-horizon-21.0.0/debian/patches/add_dns_v4_variables.patch
2023-03-06 14:12:07.0 +0100
@@ -3,8 +3,10 @@
Forwarded: no
Last-Update: 2022-12-06
puppet-module-horizon-21.0.0.orig/manifests/init.pp
-+++ puppet-module-horizon-21.0.0/manifests/init.pp
+Index: puppet-module-horizon/manifests/init.pp
+===
+--- puppet-module-horizon.orig/manifests/init.pp
puppet-module-horizon/manifests/init.pp
@@ -652,6 +652,8 @@ class horizon(
$horizon_upload_mode = undef,
$default_boot_source = undef,
diff -Nru puppet-module-horizon-21.0.0/debian/patches/debian-fixup.patch
puppet-module-horizon-21.0.0/debian/patches/debian-fixup.patch
--- puppet-module-horizon-21.0.0/debian/patches/debian-fixup.patch
2023-02-16 12:14:04.0 +0100
+++ puppet-module-horizon-21.0.0/debian/patches/debian-fixup.patch
2023-03-06 14:12:07.0 +0100
@@ -61,17 +61,18 @@
$memcache_package = 'python3-memcache'
$pymemcache_package = 'python3-pymemcache'
$designate_dashboard_package_name = 'python3-designate-dashboard'
-@@ -48,10 +46,15 @@ class horizon::params {
+@@ -48,10 +46,16 @@ class horizon::params {
'Debian': {
$package_name = 'openstack-dashboard-apache'
$httpd_config_file =
'/etc/apache2/sites-available/openstack-dashboard-alias-only.conf'
-+ $django_wsgi =
'/usr/share/openstack-dashboard/openstack_dashboard/wsgi.py'
++ $django_wsgi = '/usr/share/openstack-dashboard/wsgi.py'
+ $wsgi_user = 'www-data'
+ $wsgi_group= 'www-data'
}
default: {
$package_name = 'openstack-dashboard'
$httpd_config_file =
'/etc/apache2/conf-available/openstack-dashboard.conf'
++ $django_wsgi =
'/usr/share/openstack-dashboard/openstack_dashboard/wsgi.py'
+ $wsgi_user = 'horizon'
+ $wsgi_group= 'horizon'
}
Bug#1032872: unblock: puppet-module-puppetlabs-mysql/8.1.0-7
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package puppet-module-puppetlabs-mysql [ Reason ] The last version of MariaDB removes completely the use of /var/log/mysql, and uses exclusively journald. However, that's now how this puppet module configures MariaDB. As a consequence, creating a db fails, because the module expects to read the error in the error log. This latest version fixes the problem by creating /var/log/mysql. Note that currently, MariaDB maintainers refused to create the folder in their package, and wrote to me they prefer the puppet module to be fixed. See: https://bugs.debian.org/1032407 [ Impact ] Broken puppet module, impossible to create DBs. [ Tests ] I tested it manually and my patch fixes the issue. [ Risks ] Not much risk IMO. The patch only creates a folder... [ 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 puppet-module-puppetlabs-mysql/8.1.0-7
Bug#1032871: unblock: puppet-module-puppetlabs-haproxy/2.1.0-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package puppet-module-puppetlabs-haproxy
[ Reason ]
The latest update fix haproxy version detection (ie: puppet fact).
[ Impact ]
Wrong haproxy detection and red line when the agent runs.
[ Tests ]
I did a manual check and it fixes the issue.
[ Risks ]
Not much risks: the fact is already broken in 2.1.0-4 and 2.1.0-5
fixes it. A broken fact doesn't break the puppet module.
[ 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 puppet-module-puppetlabs-haproxy/2.1.0-4
diff -Nru puppet-module-puppetlabs-haproxy-2.1.0/debian/changelog
puppet-module-puppetlabs-haproxy-2.1.0/debian/changelog
--- puppet-module-puppetlabs-haproxy-2.1.0/debian/changelog 2022-01-04
17:24:44.0 +0100
+++ puppet-module-puppetlabs-haproxy-2.1.0/debian/changelog 2023-03-13
09:01:56.0 +0100
@@ -1,3 +1,10 @@
+puppet-module-puppetlabs-haproxy (2.1.0-5) unstable; urgency=medium
+
+ * Add a fix for the haproxy fact, taking upstream latest version of the
+parsing.
+
+ -- Thomas Goirand Mon, 13 Mar 2023 09:01:56 +0100
+
puppet-module-puppetlabs-haproxy (2.1.0-4) unstable; urgency=medium
* Clean up update-alternatives handling (Closes: #989237).
diff -Nru
puppet-module-puppetlabs-haproxy-2.1.0/debian/patches/fix-haproxy-version-detection.patch
puppet-module-puppetlabs-haproxy-2.1.0/debian/patches/fix-haproxy-version-detection.patch
---
puppet-module-puppetlabs-haproxy-2.1.0/debian/patches/fix-haproxy-version-detection.patch
1970-01-01 01:00:00.0 +0100
+++
puppet-module-puppetlabs-haproxy-2.1.0/debian/patches/fix-haproxy-version-detection.patch
2023-03-13 09:01:56.0 +0100
@@ -0,0 +1,17 @@
+Description: Fix HAProxy version detection
+Author: Thomas Goirand
+Bug-Debian: https://bugs.debian.org/989237
+Origin: upstream
+Last-Update: 2023-03-13
+
+--- puppet-module-puppetlabs-haproxy-2.1.0.orig/lib/facter/haproxy_version.rb
puppet-module-puppetlabs-haproxy-2.1.0/lib/facter/haproxy_version.rb
+@@ -16,7 +16,7 @@ if defined?(Facter::Util::Resolution.whi
+ haproxy_version_cmd = 'haproxy -v 2>&1'
+ haproxy_version_result =
Facter::Util::Resolution.exec(haproxy_version_cmd)
+ setcode do
+-
haproxy_version_result.to_s.lines.first.strip.split(%r{HA-Proxy})[1].strip.split(%r{version})[1].strip.split(%r{((\d+\.){2,}\d+).*})[1]
++
haproxy_version_result.to_s.lines.first.strip.split(%r{HA?.Proxy})[1].strip.split(%r{version})[1].strip.split(%r{((\d+\.){2,}\d+).*})[1]
+ end
+ end
+ end
diff -Nru puppet-module-puppetlabs-haproxy-2.1.0/debian/patches/series
puppet-module-puppetlabs-haproxy-2.1.0/debian/patches/series
--- puppet-module-puppetlabs-haproxy-2.1.0/debian/patches/series
1970-01-01 01:00:00.0 +0100
+++ puppet-module-puppetlabs-haproxy-2.1.0/debian/patches/series
2023-03-13 09:01:56.0 +0100
@@ -0,0 +1 @@
+fix-haproxy-version-detection.patch
Processed: reassign 1031259 to release.debian.org
Processing commands for cont...@bugs.debian.org: > reassign 1031259 release.debian.org Bug #1031259 [ddcutil] ddcutil requires module i2c-dev Bug reassigned from package 'ddcutil' to 'release.debian.org'. Ignoring request to alter found versions of bug #1031259 to the same values previously set Ignoring request to alter fixed versions of bug #1031259 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1031259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032870: unblock tryton-sao/6.0.28+ds1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock the package tryton-sao. tryton-sao/6.0.28+ds1-2 fixes https://bugs.debian.org/1032353 unblock: tryton-sao/6.0.28+ds1-2 -- Mathias Behrle PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6 AC29 7E5C 46B9 D0B6 1C71 7681 D6D0 9BE4 8405 BBF6
Bug#1032514: marked as done (unblock: quakespasm/0.95.1+dfsg-2)
Your message dated Mon, 13 Mar 2023 08:31:54 +0200 with message-id and subject line Re: Bug#1032514: unblock: quakespasm/0.95.1+dfsg-2 has caused the Debian Bug report #1032514, regarding unblock: quakespasm/0.95.1+dfsg-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.) -- 1032514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032514 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 X-Debbugs-Cc: quakesp...@packages.debian.org Control: affects -1 + src:quakespasm Please unblock package quakespasm [ Reason ] Fix #1032276 [ Impact ] If not fixed, when the quake-server package is installed and quakespasm is the selected alternative for quake-engine-server, the quake-server systemd service spams the system log with rapid "Console input too long" messages. [ Tests ] Manual test: can configure /etc/alternatives/quake-engine-server = /usr/games/quakespasm, systemctl restart quake-server.service, and connect a client with `quake --engine=quakespasm '+connect 127.0.0.1'`. With the version in bookworm, "Console input too long" messages appear until the server is stopped. With the proposed version, those messages do not appear. [ Risks ] Low risk: almost a leaf package (one of multiple options for contrib packages quake and quake-server), the patch is simple, and its small user base is indicated by the fact that it has taken this long for anyone to notice that the bug existed. [ 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 quakespasm/0.95.1+dfsg-2 diffstat for quakespasm-0.95.1+dfsg quakespasm-0.95.1+dfsg Quake/sys_sdl_unix.c | 14 ++ debian/.gitignore |5 debian/changelog |9 + debian/control|2 debian/patches/series |1 debian/patches/sys_sdl_unix-Stop-reading-from-stdin-when-EOF-is-reached.patch | 58 ++ 6 files changed, 87 insertions(+), 2 deletions(-) diff -Nru quakespasm-0.95.1+dfsg/debian/changelog quakespasm-0.95.1+dfsg/debian/changelog --- quakespasm-0.95.1+dfsg/debian/changelog 2022-11-08 07:57:52.0 + +++ quakespasm-0.95.1+dfsg/debian/changelog 2023-03-07 11:56:29.0 + @@ -1,3 +1,12 @@ +quakespasm (0.95.1+dfsg-2) unstable; urgency=medium + + * Add patch to fix running the server with /dev/null as stdin. +In particular, this makes it suitable for the systemd service in the +quake package. (Closes: #1032276) + * Standards-Version: 4.6.2 (no changes required) + + -- Simon McVittie Tue, 07 Mar 2023 11:56:29 + + quakespasm (0.95.1+dfsg-1) unstable; urgency=medium * New upstream release. diff -Nru quakespasm-0.95.1+dfsg/debian/control quakespasm-0.95.1+dfsg/debian/control --- quakespasm-0.95.1+dfsg/debian/control 2022-09-16 10:48:48.0 +0100 +++ quakespasm-0.95.1+dfsg/debian/control 2023-03-07 11:56:29.0 + @@ -13,7 +13,7 @@ libsdl2-dev, libvorbis-dev Rules-Requires-Root: no -Standards-Version: 4.6.1 +Standards-Version: 4.6.2 Vcs-Browser: https://salsa.debian.org/games-team/quakespasm Vcs-Git: https://salsa.debian.org/games-team/quakespasm.git Homepage: http://quakespasm.sourceforge.net/ diff -Nru quakespasm-0.95.1+dfsg/debian/.gitignore quakespasm-0.95.1+dfsg/debian/.gitignore --- quakespasm-0.95.1+dfsg/debian/.gitignore 1970-01-01 01:00:00.0 +0100 +++ quakespasm-0.95.1+dfsg/debian/.gitignore 2023-03-07 11:56:29.0 + @@ -0,0 +1,5 @@ +/*.debhelper.log +/*.substvars +/files +/quakespasm/ +/quakespasm-dbg/ diff -Nru quakespasm-0.95.1+dfsg/debian/patches/series quakespasm-0.95.1+dfsg/debian/patches/series --- quakespasm-0.95.1+dfsg/debian/patches/series 2022-09-16 10:48:48.0 +0100 +++ quakespasm-0.95.1+dfsg/debian/patches/series 2023-03-07 11:56:29.0 + @@ -4,3 +4,4 @@ mkpak-bashism.patch reproducible-build.patch rotfish-double-count.patch +sys_sdl_unix-Stop-reading-from-stdin-when-EOF-is-reached.patch diff -Nru quakespasm-0.95.1+dfsg/debian/patches/sys_sdl_unix-Stop-reading-from-stdin-when-EOF-is-reached.patch
