commit c6904e435ce9e62e6fbbaf6c9312759eb4e9ae3d
Author: Andres Salomon <dilinger@queued.net>
Date: Wed Mar 11 05:05:56 2026 -0400
fix a glic-related missing dependency build failure
commit 60684d36ee51dc27c77265c2aae0157a1a5b3b70
Author: Daniel Richard G. <skunk@iSKUNK.ORG>
Date: Wed Mar 11 00:26:00 2026 -0400
Add changelog entry for my last commit
commit 9cac506e9471cabade9f421f20d21a5df7197b9a
Author: Andres Salomon <dilinger@queued.net>
Date: Tue Mar 10 21:28:35 2026 -0400
update rust jxl patches for new upstream changes
Okay, I realized that I can add the unsafe{} block to the macro
definition rather than having to add it to each and every spot that's
using the macro. That will make future maintenance easier, as we drop
those blocks.
Unfortunately the normal function definitions still need their unsafe
block, but there are fewer of those.
commit a33ff2bd1e453e0fb74e612c1ac6e54f74ec7788
Author: Daniel Richard G. <skunk@iSKUNK.ORG>
Date: Tue Mar 10 12:13:49 2026 -0400
Update patches needed for jammy build
commit 393752625ade5224664b9a46ee7e683939d41726
Author: Andres Salomon <dilinger@queued.net>
Date: Mon Mar 9 23:46:37 2026 -0400
another update to glic.patch
I ended up just going through u-c's
fix-building-with-prunned-binaries.patch in order to pull all of the
glic stuff, as this was turning into a bit of a mess. This patch will
hopefully go away soon!
commit e66a5020b1cf1d666d57f7736a3a80e2b8a9fdc3
Author: Andres Salomon <dilinger@queued.net>
Date: Mon Mar 9 23:41:11 2026 -0400
add another value_or() clang-19 build fix (and move patch to llvm-19/)
commit c974492adb3b6b740e12271c0975d90df2cd6957
Author: Andres Salomon <dilinger@queued.net>
Date: Mon Mar 9 07:47:43 2026 -0400
'nother glic removal fix
commit d22518e5630fa5b46bae8e440669299617089be1
Author: Andres Salomon <dilinger@queued.net>
Date: Mon Mar 9 07:14:45 2026 -0400
pull a build fix from upstream
commit 6ec072bf513e151d6e1c2be3fac6b164db1f0c74
Author: Andres Salomon <dilinger@queued.net>
Date: Mon Mar 9 06:52:47 2026 -0400
add another build fix for clang-19
commit 115ab4b21eeb692aad898e0220bfb20f87041f70
Author: Andres Salomon <dilinger@queued.net>
Date: Mon Mar 9 06:49:40 2026 -0400
add more glic-related removals
Since we're not going to enable glic, it doesn't matter if we're doing
commit 76b2967200b09b1aa857a5cfb4cdf97c3c2ef3f9
Author: Andres Salomon <dilinger@queued.net>
Date: Mon Mar 9 02:45:40 2026 -0400
another clang-19 build fix
I'm not certain that this is correct, tbh. The code is new and I'm not
sure whether to care about that assertion yet.
commit a856ce51f1541d0261c4b09fe94bb64573b4f592
Author: Andres Salomon <dilinger@queued.net>
Date: Mon Mar 9 02:43:16 2026 -0400
update llvm-19/clang-19-crash.patch to hopefully build.
Not fully tested yet, as I'm not as far as linking.
commit 52e8df3486ea5e162b02f213b82ce215cbf23cf5
Author: Andres Salomon <dilinger@queued.net>
Date: Mon Mar 9 00:26:15 2026 -0400
refresh a few ppc64/loong64 patches, & also fix the prior commit.
Accidentally typoed the path for the llvm-22 fix.
commit 219d419698a0a60f896d1d63c0c7b4ca4f764be3
Author: Andres Salomon <dilinger@queued.net>
Date: Mon Mar 9 00:19:57 2026 -0400
move/rename the clang-22 build fix into a new llvm-22 directory
The assumption is that we will backport llvm-22 to stable & oldstable.
commit 22e741af28710d13671ac8f09be6683a12b9a52d
Author: Andres Salomon <dilinger@queued.net>
Date: Mon Mar 9 00:15:59 2026 -0400
move clang-19 crash fix into the llvm-19 directory
commit 738f9f0d0b5f5efe2ca8ec45e68c7c748c37ff80
Author: Andres Salomon <dilinger@queued.net>
Date: Mon Mar 9 00:11:46 2026 -0400
fix another clang-19 issue
commit 0c2a859146b35639f3e99b47bd1b9620db090d7f
Author: Timothy Pearson <tpearson@raptorengineering.com>
Date: Sun Mar 8 20:27:53 2026 -0500
More ppc64el build fixes
commit 39b78522761df03a5d5d4eedef36c36b0cbb1123
Author: Timothy Pearson <tpearson@raptorengineering.com>
Date: Sun Mar 8 13:50:56 2026 -0500
Actually fix powerpc64 boringssl build failures
commit f5b28f27de638e12934fd38e900c1a99e593d8ec
Author: Timothy Pearson <tpearson@raptorengineering.com>
Date: Sun Mar 8 13:23:25 2026 -0500
Fix powerpc64 boringssl build failures
commit 6b9459f8a48cd23d7381037b0501620563519b27
Author: Timothy Pearson <tpearson@raptorengineering.com>
Date: Sun Mar 8 13:07:46 2026 -0500
Initial ppc64 patch updates
Not yet compile tested
commit c269c860118e84440e33d9aa505d0efc09ef1c3b
Author: Andres Salomon <dilinger@queued.net>
Date: Sun Mar 8 13:49:43 2026 -0400
stop clang-19 from crashing
commit 9221cc93c8a62e5ad5f0bdad931e36cf85abdea9
Author: Andres Salomon <dilinger@queued.net>
Date: Sun Mar 8 08:06:38 2026 -0400
fix disable/glic.patch
Somehow I committed an older one?
commit ec82c8c03c16a23d51856e5062a4cab14fc1b646
Author: Andres Salomon <dilinger@queued.net>
Date: Sun Mar 8 08:01:33 2026 -0400
add bytemuck fix
commit e5646e7d449eb6d28523d748b28a39544b834bde
Author: Andres Salomon <dilinger@queued.net>
Date: Sun Mar 8 07:56:50 2026 -0400
drop compiler flag added in https://chromium-review.googlesource.com/c/chromium/src/+/7539408
commit 60e4c9edef11e5cb524ab38b21ea5e62f66db01f
Author: Andres Salomon <dilinger@queued.net>
Date: Sun Mar 8 07:51:19 2026 -0400
drop fixes/force-rust-nightly.patch
Upstream's now using build_with_chromium, which should be true for our
builds; no need to manually set rustc_nightly_capability to true.
commit b144c636b11b84e2d26b99dc0156ed7ff9269b0d
Author: Andres Salomon <dilinger@queued.net>
Date: Sun Mar 8 07:49:16 2026 -0400
truncate rustc --version string, and replace spaces with dashes
commit 66036419924e2067222f8ec44cc465897060de1b
Author: Andres Salomon <dilinger@queued.net>
Date: Sun Mar 8 07:27:18 2026 -0400
fix another capapult reference
We really need to stop deleting catapult. One of these days..
commit 106c74464c8306475c526fd1f537653c4c7e6778
Author: Andres Salomon <dilinger@queued.net>
Date: Sun Mar 8 07:08:45 2026 -0400
update disable/glic.patch for upstream changes
commit c989a48ad25462ffd5a5cd478dc3b493e8753987
Author: Andres Salomon <dilinger@queued.net>
Date: Sun Mar 8 06:55:39 2026 -0400
start prep'ing v146
Among the 127 debian patches available in version 145.0.7632.159-1 of the package, we noticed the following issues:
![[bug history graph]](https://qa.debian.org/data/bts/graphs/c/chromium.png){kind=link}