Processed: unblock: mitmproxy/8.1.1-2
Processing control commands: > affects -1 + mitmproxy Bug #1032863 [release.debian.org] unblock: mitmproxy/8.1.1-2 Added indication that 1032863 affects mitmproxy -- 1032863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032863: unblock: mitmproxy/8.1.1-2
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
Bug#1032862: unblock: golang-github-tidwall-gjson/1.14.4-2 (pre-approval)
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.
[ 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.
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;>https://img.shields.io/badge/api-reference-blue.svg?style=flat-square;
alt="GoDoc">
-http://tidwall.com/gjson-play;>https://img.shields.io/badge/%F0%9F%8F%90-playground-9900cc.svg?style=flat-square;
alt="GJSON Playground">
+https://tidwall.com/gjson-play;>https://img.shields.io/badge/%F0%9F%8F%90-playground-9900cc.svg?style=flat-square;
alt="GJSON Playground">
+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 be String, Number, True, False, Null, or JSON
-result.Str // holds the string
-result.Num // holds the float64 number
-result.Raw // holds the raw json
-result.Index // index of raw value in original json, zero means index unknown
+result.Type // can be String, Number, True, False, Null, or JSON
+result.Str// holds the string
+result.Num// holds the float64 number
+result.Raw// holds the raw json
+result.Index // index of raw value in original json, zero means index
unknown
+result.Indexes// indexes of all the elements that match on a path
containing the '#' query character.
```
There are a
Bug#1031325: marked as done (e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible)
Your message dated Sun, 12 Mar 2023 23:23:29 +0100 with message-id and subject line Re: Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible has caused the Debian Bug report #1031325, regarding e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible 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.) -- 1031325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031325 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 A week ago, Theodore Ts'o uploaded e2fsprogs 1.47.0 into Debian unstable. This version contains a unannounced change that basically breaks grub2 (and grub-install). This issue has been reported as #1030939 [1] and #1030846 [2]. To "fix" the issue, instead of turning the feature off, a patch to grub2 in Sid has been committed recently. Unfortunately, that only fixes grub in Sid. Grub in Bullseye or any current Ubuntu release *cannot* deal with a filesystem created by this version of e2fsprogs. This basically breaks the debootstrap method of installing a Debian or Ubuntu. If e2fsprogs 1.47.0 is allowed into Testing, we can no longer use the debootstrap method to install a Debian Bullseye (or older) or any Ubuntu release. It requires to manually change the filesystem features before it can be used again. It also makes e.g. vmdb2 in Sid unusable to create images of Bullseye or older Debian releases, or Ubuntu releases. The gain of enabling the metadata_csum_seed feature by default is not noteworthy. It is a feature that hardly anybody needs. I have not seen one use-case nor even relevant search hits. But the loss is heavy. User's can no longer simply follow [3] to install any Debian or Ubuntu system if the filesystem has been created with e2fsprogs 1.47.0. It also breaks software in the midst of the freeze. I hereby ask the release team to step in and either make sure that the metadata_csum_seed feature is not turned on by default in e2fsprogs in Bookworm or that version 1.47.0 is not shipped as part of Bookworm. Reasons: - - this breaks existing tools for no apparant reason - - introducing this breaking change is too late in the release cycle to deal with it properly - - the metadata_csum_seed feature is hardly useful or requested; it can be turned on if necessary; no need to make it the default in Bookworm - - there is no grub upstream release with support for it; only patched grub versions can cope with it - - the change makes it impossible to create filesystems with this version of e2fsprogs and then run a grub-install from a target system that does not cope with that feature; basically breaking the debootstrap method of installing Debian or Ubuntu onto a server (violating #4 of the Debian social contract) - - to cope with the former issues, users will have to know about that incompatibility and ways to deal with it; none of that is prepared; the package maintainer even refuses a NEWS entry - - it breaks vmdb2, only allowing to make images of Debian Bookworm and Sid (if grub is involved) - - pushing this metadata_csum_seed feature violates #4 of the Debian social contract Instead, turning on this feature should be postponed for the next release cycle where a proper transition can be done. [1] https://bugs.debian.org/1030939 [2] https://bugs.debian.org/1030846 [3] https://www.debian.org/releases/stable/amd64/apds03 Daniel Leidert -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPsE8UACgkQS80FZ8KW 0F0Aug/+Kb6xrQcILq+VYpKk/161UXgQA47ccydz78uT3r1eRBVJIPReULZPdjvk W4PDDOYypScsx4+EahdOVViAMiOyzI0eroivZmDItxY1HR6LpKdeQFPLET6FdbfM pDHezFKXqsulYQWLu5M6yPCtMWGCmAtiH9NeppzUY7+dnBr2yzZGitH4pPSh7MmS 9jxRIKG0xGa3wF+a1yEgHE0nPvqD5a97GlwL5+MTg580k/e1VRpaQaYrTRr3CHyK EJbVOu70K+qXgP837x6B5eyYmihJWiNBMxm9JqF1TrwTKXwk26zpZ2+T1uKVgVKj Y5AlZX8Gypdxq0Q3uFPSlzBhetd2wvrUt9hKEb52fdzw3L4AsY2Ken98sAhqy7Xi PGVdihiUSAT5gslthm3qB3fGQQMIEXI3UdHqSx7ARgZJ6Gkf/zIjk5sKl/xiGe+t jJExPdCR7H8+tPNZhJEhx6BLtLs8tLm+zhOAr3rZVekEn3PJJAHOKPs1KPBWinYr FsVBsWBWzOgKNARu31u/o4s5BFV99M45gZqHLs3Mp5TvJqIxkbwS0FDoCa/TausP vojuW4kDPM7Jjw568W4O8csXBiI/qEcEPXZGPrgGVs3Yo1hV/KkJUOkQ9y/VvRps POx+RwF400ov8zOxGPqETkqDjl/2JQ47OOvogJMi6FDRQk+YE2w= =bKh7 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- On 2023-02-22 21:36:05 +0100, Paul Gevers
Bug#1032855: unblock: scilab/6.1.1+dfsg2-5
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, + default-jre-headless, libflexdock-java, libjogl2-java, libgl1-mesa-dev, + libjrosetta-java, ant, libjgoodies-looks-java, libskinlf-java, + liblucene4.10-java, libactivation-java, libjaxb-java, # graphic - libfreehep-graphics2d-java, libfreehep-graphicsio-java, libfreehep-graphicsio-emf-java, - libfreehep-util-java, + libfreehep-graphics2d-java, libfreehep-graphicsio-java, + libfreehep-graphicsio-emf-java, libfreehep-util-java, # Documentation - libjeuclid-core-java (>= 3.1.3), libbatik-java (>= 1.7), fop (>= 0.95), - javahelp2, libsaxon-java, libavalon-framework-java, docbook-xsl, - libxml-commons-external-java, + libjeuclid-core-java, libbatik-java, fop, javahelp2, libsaxon-java, + libavalon-framework-java, docbook-xsl, libxml-commons-external-java, # Optional Scilab features -
Processed: unblock: scilab/6.1.1+dfsg2-5
Processing control commands: > affects -1 + src:scilab Bug #1032855 [release.debian.org] unblock: scilab/6.1.1+dfsg2-5 Added indication that 1032855 affects src:scilab -- 1032855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032853: unblock: isenkram/0.50
Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal Please unblock package isenkram The changes between the version in testing (0.49) and in unstable (0.51) are all related to changes in the Debian archive, and relates to files with content extracted from the Debian archve. In addition I adjusted a lintian override to match the latest message structure. This version update the list of firmware file to reflect the latest updates in the Debian archive, as well as hardware mappings extracted using appstream from the Debian archive. [ Reason ] The isenkram package is a key package. [ Impact ] The update make sure isenkram users get package proposals relecting the current status of the packages in the ARchive. [ Tests ] The change can be tested using /usr/sbin/isenkram-autoinstall-firmware and isenkram-lookup on relevant hardware platforms. [ Risks ] The risks are low, as this only is making already existing information in the archive easlier available. [ 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 isenkram/0.50 diff --git a/debian/changelog b/debian/changelog index 71ef7e3..0e2c3f3 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,18 @@ +isenkram (0.51) unstable; urgency=medium + + * Bump version number in python library to fix build problem. + + -- Petter Reinholdtsen Sun, 12 Mar 2023 22:03:04 +0100 + +isenkram (0.50) unstable; urgency=medium + + * Adjusted lintian override to match current versions. + * Corrected comment in lookup code. + * Updated modaliases file from appstream data in sid using appstream2modaliases. + * Updated generated firmware lists. + + -- Petter Reinholdtsen Sun, 12 Mar 2023 09:56:32 +0100 + isenkram (0.49) unstable; urgency=medium * Updated Standards-Version from 4.5.1 to 4.6.2. diff --git a/debian/isenkram-cli.lintian-overrides b/debian/isenkram-cli.lintian-overrides index 7b3f0c9..db6242d 100644 --- a/debian/isenkram-cli.lintian-overrides +++ b/debian/isenkram-cli.lintian-overrides @@ -1,2 +1,2 @@ isenkram-cli: no-debconf-config -isenkram-cli: debconf-is-not-a-registry usr/sbin/isenkram-pkginstall +isenkram-cli: debconf-is-not-a-registry [usr/sbin/isenkram-pkginstall:27] diff --git a/generated/Fw-Contents-all-bookworm-main b/generated/Fw-Contents-all-bookworm-main index 0b34313..38c54ca 100644 --- a/generated/Fw-Contents-all-bookworm-main +++ b/generated/Fw-Contents-all-bookworm-main @@ -1,5 +1,5 @@ -lib/firmware/ath9k_htc/htc_7010-1.dev.0.fw misc/firmware-ath9k-htc -lib/firmware/ath9k_htc/htc_9271-1.dev.0.fw misc/firmware-ath9k-htc +lib/firmware/ath9k_htc/htc_7010-1.4.0.fwmisc/firmware-ath9k-htc +lib/firmware/ath9k_htc/htc_9271-1.4.0.fwmisc/firmware-ath9k-htc lib/firmware/av7110/bootcode.bin kernel/firmware-linux-free lib/firmware/carl9170-1.fw kernel/firmware-linux-free lib/firmware/cis/3CCFEM556.cis kernel/firmware-linux-free diff --git a/generated/Fw-Contents-all-bookworm-non-free b/generated/Fw-Contents-all-bookworm-non-free deleted file mode 100644 index 00d7a66..000 --- a/generated/Fw-Contents-all-bookworm-non-free +++ /dev/null @@ -1,10 +0,0 @@ -lib/firmware/zd1211/zd1211_ub non-free/kernel/firmware-zd1211 -lib/firmware/zd1211/zd1211_uph non-free/kernel/firmware-zd1211 -lib/firmware/zd1211/zd1211_uphm non-free/kernel/firmware-zd1211 -lib/firmware/zd1211/zd1211_uphr non-free/kernel/firmware-zd1211 -lib/firmware/zd1211/zd1211_ur non-free/kernel/firmware-zd1211 -lib/firmware/zd1211/zd1211b_ub non-free/kernel/firmware-zd1211 -lib/firmware/zd1211/zd1211b_uph non-free/kernel/firmware-zd1211 -lib/firmware/zd1211/zd1211b_uphm non-free/kernel/firmware-zd1211 -lib/firmware/zd1211/zd1211b_uphr non-free/kernel/firmware-zd1211 -lib/firmware/zd1211/zd1211b_ur non-free/kernel/firmware-zd1211 diff --git a/generated/Fw-Contents-all-bookworm-non-free-firmware b/generated/Fw-Contents-all-bookworm-non-free-firmware index 6d5d912..c34c0b3 100644 --- a/generated/Fw-Contents-all-bookworm-non-free-firmware +++ b/generated/Fw-Contents-all-bookworm-non-free-firmware @@ -77,9 +77,11 @@ lib/firmware/amdgpu/cyan_skillfish2_pfp.bin non-free-firmware/kernel lib/firmware/amdgpu/cyan_skillfish2_rlc.bin non-free-firmware/kernel/firmware-amd-graphics lib/firmware/amdgpu/cyan_skillfish2_sdma.bin non-free-firmware/kernel/firmware-amd-graphics lib/firmware/amdgpu/cyan_skillfish2_sdma1.bin non-free-firmware/kernel/firmware-amd-graphics
Bug#1032848: marked as done (unblock: network-manager-pptp/1.2.12-1)
Your message dated Sun, 12 Mar 2023 19:07:15 + with message-id and subject line unblock network-manager-pptp has caused the Debian Bug report #1032848, regarding unblock: network-manager-pptp/1.2.12-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.) -- 1032848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032848 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: network-manager-p...@packages.debian.org Control: affects -1 + src:network-manager-pptp Please unblock package network-manager-pptp The latest upload of network-manager-pptp is a minor update, consisting of 90% translation updates and a bit of build system cleanups. The regression potential is close to zero as there are not code related changes. Regards, Michael --- End Message --- --- Begin Message --- Unblocked.--- End Message ---
Processed: Re: Bug#1032849: unblock: shim/15.7-1 (etc.)
Processing control commands: > tags -1 pending Bug #1032849 [release.debian.org] unblock: shim/15.7-1 (etc.) Added tag(s) pending. -- 1032849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032849: unblock: shim/15.7-1 (etc.)
Control: tags -1 pending Hi Steve, On 12-03-2023 19:56, Steve McIntyre wrote: Please unblock our stack of shim and shim-signed packages. 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. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1032849: unblock: shim/15.7-1 (etc.)
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
Processed: unblock: network-manager-pptp/1.2.12-1
Processing control commands: > affects -1 + src:network-manager-pptp Bug #1032848 [release.debian.org] unblock: network-manager-pptp/1.2.12-1 Added indication that 1032848 affects src:network-manager-pptp -- 1032848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032848: unblock: network-manager-pptp/1.2.12-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: network-manager-p...@packages.debian.org Control: affects -1 + src:network-manager-pptp Please unblock package network-manager-pptp The latest upload of network-manager-pptp is a minor update, consisting of 90% translation updates and a bit of build system cleanups. The regression potential is close to zero as there are not code related changes. Regards, Michael
Bug#1032847: unblock: intel-microcode/3.20230214.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: intel-microc...@packages.debian.org, t...@security.debian.org Control: affects -1 + src:intel-microcode I've uploaded intel-microcode to DELAYED/5, ETA will be Mar 17 ~18:00 CET Please unblock package intel-microcode once it hits unstable. The upload updates intel microcodes to target (See #1031334) - INTEL-SA-00700: CVE-2022-21216 - INTEL-SA-00730: CVE-2022-33972 - INTEL-SA-00738: CVE-2022-33196 - INTEL-SA-00767: CVE-2022-38090 the CVEs are information disclosure via local access vulnerbilities and potential privilege escalations. I plan to provide updated packages for bullseye (security team in CC). As well as LTS (buster) and ELTS (stretch an jessie) as part of the freexian LTS/ELTS project) To keep the fixes consistent, I'd like to let them flow from sid -> jessie… [ Tests ] I've tested that the package works on Intel hardware that I have access to. [ 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 intel-microcode/3.20230214.1 -- tobi diff -Nru intel-microcode-3.20221108.2/debian/changelog intel-microcode-3.20230214.1/debian/changelog --- intel-microcode-3.20221108.2/debian/changelog 2023-02-17 01:12:52.0 +0100 +++ intel-microcode-3.20230214.1/debian/changelog 2023-03-12 18:16:50.0 +0100 @@ -1,3 +1,52 @@ +intel-microcode (3.20230214.1) unstable; urgency=medium + + * Non-maintainer upload. + * New upstream microcode datafile 20230214 +- Includes Fixes for: (Closes: #1031334) + - INTEL-SA-00700: CVE-2022-21216 + - INTEL-SA-00730: CVE-2022-33972 + - INTEL-SA-00738: CVE-2022-33196 + - INTEL-SA-00767: CVE-2022-38090 + * New Microcodes: +sig 0x000806f4, pf_mask 0x10, 2022-12-19, rev 0x2c000170 +sig 0x000806f4, pf_mask 0x87, 2022-12-27, rev 0x2b000181 +sig 0x000806f5, pf_mask 0x10, 2022-12-19, rev 0x2c000170 +sig 0x000806f5, pf_mask 0x87, 2022-12-27, rev 0x2b000181 +sig 0x000806f6, pf_mask 0x10, 2022-12-19, rev 0x2c000170 +sig 0x000806f6, pf_mask 0x87, 2022-12-27, rev 0x2b000181 +sig 0x000806f7, pf_mask 0x87, 2022-12-27, rev 0x2b000181 +sig 0x000806f8, pf_mask 0x10, 2022-12-19, rev 0x2c000170 +sig 0x000806f8, pf_mask 0x10, 2022-12-19, rev 0x2c000170, size 600064 +sig 0x000806f8, pf_mask 0x87, 2022-12-27, rev 0x2b000181 +sig 0x000806f8, pf_mask 0x87, 2022-12-27, rev 0x2b000181, size 561152 +sig 0x000b06a2, pf_mask 0xc0, 2022-12-08, rev 0x410e +sig 0x000b06a2, pf_mask 0xc0, 2022-12-08, rev 0x410e, size 212992 +sig 0x000b06a3, pf_mask 0xc0, 2022-12-08, rev 0x410e + * Updated Microcodes: +sig 0x00050653, pf_mask 0x97, 2022-08-30, rev 0x1000161, size 36864 +sig 0x00050656, pf_mask 0xbf, 2022-08-26, rev 0x4003303, size 37888 +sig 0x00050657, pf_mask 0xbf, 2022-08-26, rev 0x5003303, size 37888 +sig 0x0005065b, pf_mask 0xbf, 2022-08-26, rev 0x7002503, size 29696 +sig 0x000606a6, pf_mask 0x87, 2022-10-09, rev 0xd000389, size 296960 +sig 0x000606c1, pf_mask 0x10, 2022-09-23, rev 0x1000211, size 289792 +sig 0x000706a1, pf_mask 0x01, 2022-09-16, rev 0x003e, size 75776 +sig 0x000706a8, pf_mask 0x01, 2022-09-20, rev 0x0022, size 76800 +sig 0x000706e5, pf_mask 0x80, 2022-08-31, rev 0x00b8, size 113664 +sig 0x000806a1, pf_mask 0x10, 2022-09-07, rev 0x0032, size 34816 +sig 0x00090672, pf_mask 0x07, 2023-01-04, rev 0x002c +sig 0x00090672, pf_mask 0x07, 2023-01-04, rev 0x002c, size 219136 +sig 0x00090675, pf_mask 0x07, 2023-01-04, rev 0x002c +sig 0x000906a3, pf_mask 0x80, 2023-01-11, rev 0x0429 +sig 0x000906a3, pf_mask 0x80, 2023-01-11, rev 0x0429, size 218112 +sig 0x000906a4, pf_mask 0x80, 2023-01-11, rev 0x0429 +sig 0x000906c0, pf_mask 0x01, 2022-09-02, rev 0x2424, size 20480 +sig 0x000a0671, pf_mask 0x02, 2022-08-31, rev 0x0057, size 103424 +sig 0x000b0671, pf_mask 0x32, 2022-12-19, rev 0x0112, size 207872 +sig 0x000b06f2, pf_mask 0x07, 2023-01-04, rev 0x002c +sig 0x000b06f5, pf_mask 0x07, 2023-01-04, rev 0x002c + + -- Tobias Frost Sun, 12 Mar 2023 18:16:50 +0100 + intel-microcode (3.20221108.2) unstable; urgency=medium * Move source and binary from non-free/admin to non-free-firmware/admin Binary files /tmp/qNbFv9J1ty/intel-microcode-3.20221108.2/intel-ucode/06-55-03 and /tmp/Ekjb2KZejs/intel-microcode-3.20230214.1/intel-ucode/06-55-03 differ Binary files /tmp/qNbFv9J1ty/intel-microcode-3.20221108.2/intel-ucode/06-55-06 and /tmp/Ekjb2KZejs/intel-microcode-3.20230214.1/intel-ucode/06-55-06 differ Binary files /tmp/qNbFv9J1ty/intel-microcode-3.20221108.2/intel-ucode/06-55-07 and /tmp/Ekjb2KZejs/intel-microcode-3.20230214.1/intel-ucode/06-55-07 differ Binary files /tmp/qNbFv9J1ty/intel-microcode-3.20221108.2/intel-ucode/06-55-0b
Processed: unblock: intel-microcode/3.20230214.1
Processing control commands: > affects -1 + src:intel-microcode Bug #1032847 [release.debian.org] unblock: intel-microcode/3.20230214.1 Added indication that 1032847 affects src:intel-microcode -- 1032847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032827: marked as done (unblock: golang-golang-x-text/0.7.0-1)
Your message dated Sun, 12 Mar 2023 11:26:58 + with message-id and subject line unblock golang-golang-x-text has caused the Debian Bug report #1032827, regarding unblock: golang-golang-x-text/0.7.0-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.) -- 1032827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032827 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 [ Filing as suggested by Sebastian.] Hi, This package was uploaded to unstable a few days ago, with the following changelog, which a cursory look at `d`'s output seems to confirm: * New upstream version 0.7.0 (with fixes to README.md and comments; no code change from 0.5.0) This is rather unfortunate because it doesn't fit the freeze guidelines, and coupled with the ongoing “let's trigger binNMUs to lower the amount of source packages kept in testing just to satisfy Built-Using” rounds of binNMUs, this is keeping some packages out of testing. That's the case for crowdsec 1.4.6-1 which was scheduled to migrate yesterday evening, which now has 1.4.6-1+b1 for all archs, and will need to wait on golang-golang-x-text (only 3/10). I haven't conducted any kind of deeper analysis about possible other packages being held back specifically due to a Built-Using on that package, but a grep on excuses.yaml suggests 957 packages (counting binNMUs for all archs included) and 108 unique source packages getting impacted by that upload. I'll leave it up to the release team to implement whatever they feel is best at this point. An age-days would help clear that new dependency for many packages, but it feels wrong to ask for it given the upload wasn't quite appropriate… Keeping the reportbug-generated hint for now: unblock golang-golang-x-text/0.7.0-1 Thanks for your help! Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/ --- End Message --- --- Begin Message --- Unblocked.--- End Message ---
Bug#1032827: unblock: golang-golang-x-text/0.7.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: debian...@lists.debian.org [ Filing as suggested by Sebastian.] Hi, This package was uploaded to unstable a few days ago, with the following changelog, which a cursory look at `d`'s output seems to confirm: * New upstream version 0.7.0 (with fixes to README.md and comments; no code change from 0.5.0) This is rather unfortunate because it doesn't fit the freeze guidelines, and coupled with the ongoing “let's trigger binNMUs to lower the amount of source packages kept in testing just to satisfy Built-Using” rounds of binNMUs, this is keeping some packages out of testing. That's the case for crowdsec 1.4.6-1 which was scheduled to migrate yesterday evening, which now has 1.4.6-1+b1 for all archs, and will need to wait on golang-golang-x-text (only 3/10). I haven't conducted any kind of deeper analysis about possible other packages being held back specifically due to a Built-Using on that package, but a grep on excuses.yaml suggests 957 packages (counting binNMUs for all archs included) and 108 unique source packages getting impacted by that upload. I'll leave it up to the release team to implement whatever they feel is best at this point. An age-days would help clear that new dependency for many packages, but it feels wrong to ask for it given the upload wasn't quite appropriate… Keeping the reportbug-generated hint for now: unblock golang-golang-x-text/0.7.0-1 Thanks for your help! Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/
Processed: unblock: flask-security/5.1.1-1
Processing control commands: > affects -1 + src:flask-security Bug #1032824 [release.debian.org] unblock: flask-security/5.1.1-1 Added indication that 1032824 affects src:flask-security -- 1032824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
