Debian Patches
Status for docker-buildx/0.29.1+ds1-4
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-Skip-tests-that-assume-a-git-repo-or-network-access.patch | Skip tests that assume a git repo or network access The TestGit test assumes that we are in a git repository, which is not always the case when building Debian packages. |
Nicolas Peugnet <nicolas@club1.fr> | no | 2025-02-02 | ||
| 0003-Add-an-option-to-generate-the-manual-pages.patch | Add an option to generate the manual pages For an unknown reason, Docker authors disabled the manual pages generation from their docs generator. This patch allows to use it. |
Nicolas Peugnet <nicolas.peugnet@lip6.fr> | not-needed | 2025-02-18 | ||
| 0003-Disable-history-trace-command-due-to-missing-depende.patch | Disable history trace command due to missing dependency As Debian is currently missing the github.com/tonistiigi/jaeger-ui-rest package and it is only used by a single command (docker buildx history trace), I decided to patch out this command to leave more time for packaging this missing dependency. This patch can be safely dropped once this dependency has been packaged in Debian. |
Nicolas Peugnet <nicolas@club1.fr> | not-needed | 2026-01-18 | ||
| 0004-Skip-one-test-that-depends-on-golang-opentelemetry-o.patch | Skip one test that depends on golang-opentelemetry-otel-dev >= 1.32 This test needs the "Attribute" property of the instrumentation.Scope struct. This attribute is only existing since otel >=1.32, as it has been added in [30c0f3f]. Drop this patch when golang-opentelemetry-otel-dev is update to >= 1.32 in Debian. [30c0f3f]: https://github.com/open-telemetry/opentelemetry-go/commit/30c0f3fa6efc1f73657087e610b608dbadcb1805 |
Nicolas Peugnet <nicolas@club1.fr> | not-needed | 2026-02-15 | ||
| 0005-dap-fix-the-race-condition-in-the-dap-unit-tests.patch | dap: fix the race condition in the dap unit tests The context used for serving the dap server was being canceled too early because it used defer which would initiate at the end of the function while every other cleanup function used `t.Cleanup` which executes in its own goroutine. One possible solution was to move the cancel to the cleanup, but the context being passed to serve and start doesn't make sense because if it ever does get canceled, it'll likely cause a similar race condition with `Stop`. This removes the context from the methods that were causing this issue in favor of just relying on the caller calling `Stop` when they are done with the adapter and server. This seems to have only affected tests and I don't believe it affected the actual dap command. * Remove hunks from non-yet-existing TestSetBreakpoints function |
"Jonathan A. Sternberg" <jonathan.sternberg@docker.com> | no | debian | upstream, https://github.com/docker/buildx/commit/ca9df87014e50137830d4ce37411a108f1a91ae7.patch | 2026-03-10 |
All known versions for source package 'docker-buildx'
- 0.29.1+ds1-4 (sid, forky)
- 0.13.1+ds1-3 (trixie)
