Your message dated Sat, 31 Aug 2024 07:31:06 +0100
with message-id
<32bab11a8f4c6ca3e3dbd10b3a95299eab4ad752.ca...@adam-barratt.org.uk>
and subject line Re: Bug#1080021: trixie-pu: package
chromium/128.0.6613.113-1~deb13u1
has caused the Debian Bug report #1080021,
regarding trixie-pu: package chromium/128.0.6613.113-1~deb13u1
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 [email protected]
immediately.)
--
1080021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080021
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: trixie
User: [email protected]
Usertags: pu
As we discussed on IRC, Saturday's bookworm point release would be made
easier if chromium in trixie were up-to-date with what's in bookworm.
Given that chromium also has an additional 23 CVEs and 128 is already in
pretty good shape, let's do another tpu.
The packaging changes between 127.0.6533.119-1 in sid and
127.0.6533.119-1~deb13u1 remain the same as in past tpus (eg, #1076396).
See attached.
Thanks,
Andres
--
I'm available for contract & employment work, please contact me if
interested.
diff -urN chromium-128.0.6613.113-orig/debian/changelog chromium-128.0.6613.113/debian/changelog
--- chromium-128.0.6613.113-orig/debian/changelog 2024-08-14 17:11:25.000000000 +0000
+++ chromium-128.0.6613.113/debian/changelog 2024-08-18 01:43:13.173141364 +0000
@@ -1,3 +1,11 @@
+chromium (128.0.6613.113-1~deb13u1) trixie; urgency=high
+
+ * Rebuild for trixie.
+ * Revert libxml2-dev versioned build-dep, and re-add
+ d/patches/bookworm/libxml/parseerr.patch.
+
+ -- Andres Salomon <[email protected]> Sun, 18 Aug 2024 01:41:43 +0000
+
chromium (128.0.6613.113-1) unstable; urgency=high
[ Andres Salomon ]
diff -urN chromium-128.0.6613.113-orig/debian/control chromium-128.0.6613.113/debian/control
--- chromium-128.0.6613.113-orig/debian/control 2024-08-08 04:17:58.000000000 +0000
+++ chromium-128.0.6613.113/debian/control 2024-08-18 01:43:49.953192381 +0000
@@ -72,7 +72,7 @@
libopus-dev,
libxtst-dev,
libjpeg-dev,
- libxml2-dev (>= 2.12),
+ libxml2-dev,
libgtk-3-dev,
libxslt1-dev,
liblcms2-dev,
diff -urN chromium-128.0.6613.113-orig/debian/patches/series chromium-128.0.6613.113/debian/patches/series
--- chromium-128.0.6613.113-orig/debian/patches/series 2024-08-14 03:41:47.000000000 +0000
+++ chromium-128.0.6613.113/debian/patches/series 2024-08-18 01:43:37.225174796 +0000
@@ -139,3 +139,6 @@
# These patches enable full POWER ISA 3.0 (POWER9) acceleration when applied
# They will not work on POWER8 (ISA 2.07) or below
#ppc64le/core/baseline-isa-3-0.patch
+
+# build for trixie
+bookworm/libxml-parseerr.patch
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On Thu, 2024-08-29 at 19:53 +0200, Paul Gevers wrote:
> Control: tags -1 cconfirmed
>
> Hi Andres,
>
> On 29-08-2024 18:32, Andres Salomon wrote:
> > As we discussed on IRC, Saturday's bookworm point release would be
> > made
> > easier if chromium in trixie were up-to-date with what's in
> > bookworm.
> > Given that chromium also has an additional 23 CVEs and 128 is
> > already in
> > pretty good shape, let's do another tpu.
> >
> > The packaging changes between 127.0.6533.119-1 in sid and
> > 127.0.6533.119-1~deb13u1 remain the same as in past tpus (eg,
> > #1076396).
> > See attached.
>
> Please go ahead and upload and lets check tomorrow evening where we
> stand before hinting it in.
The package migrated; thanks:
chromium | 128.0.6613.113-1~deb13u1 | testing |
source, amd64, arm64, armhf, i386, ppc64el
Regards,
Adam
--- End Message ---
