Debian Patches
Status for golang-github-go-git-go-git/5.19.2-1
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-use-another-gcfg.patch | Use src-d/gcfg instead of go-git/gcfg Debian packages github.com/src-d/gcfg (golang-github-src-d-gcfg-dev) rather than github.com/go-git/gcfg. Replace the import path in plumbing/format/config/decoder.go to use the packaged version. |
Pirate Praveen <praveen@debian.org> | not-needed | 2021-11-09 | ||
| 0002-disable-test-with-unreliable-tilde-expansion.patch | Disable gitignore test with unreliable tilde expansion Disable gitignore test that relies on ~user tilde expansion, which fails in isolated Debian build chroots where user home directory lookup is unreliable. |
Maytham Alsudany <maytha8thedev@gmail.com> | not-needed | 2024-03-27 | ||
| 0003-use-explicit-localhost-ip.patch | Use explicit loopback IP instead of localhost Tests were failing because they were attempting to connect to a DNS server (which requires internet) and looking up "localhost". This patch changes out "localhost" for the more explicit "127.0.0.1" loopback IP. |
Maytham Alsudany <maytha8thedev@gmail.com> | not-needed | 2024-06-10 | ||
| 0004-Compute-zlib-output-in-tests-instead-of-hardcoding-i.patch | *: Compute zlib output in tests instead of hardcoding it Go 1.27 changed the deflate output for small inputs: the stored-block sync marker is no longer emitted on close. That broke two tests which hardcoded the zlib bytes of an empty object and the size of a loose object file. Compress the same content within the test and compare against that, so the assertions hold across toolchains. |
Paulo Gomes <paulo@entire.io> | not-needed | debian | backport, https://github.com/go-git/go-git/commit/4ae786a01dfb96289854ddc6460981531a6fe53c | 2026-09-07 |
| 0005-Move-defaultSignature-test-helper-to-common_test.go.patch | Move defaultSignature test helper to common_test.go Move defaultSignature from worktree_commit_test.go into common_test.go so it remains accessible to other test suites in package git (such as worktree_fs_test.go) even if worktree_commit_test.go is not compiled. |
Reinhard Tartler <siretart@tauware.de> | not-needed | 2026-09-20 | ||
| 0006-plumbing-format-packfile-Do-not-run-fixture-extracti.patch | plumbing/format/packfile: Do not run fixture extraction tests in parallel go-git-fixtures uses an unsynchronized package-level global map to cache extracted fixture files. When TestChecksumMismatch and TestMalformedPack run concurrently, simultaneous writes to this map cause a fatal Go runtime panic ("fatal error: concurrent map writes", Debian bug #1138090). Remove t.Parallel() from these two tests so they run sequentially. |
Reinhard Tartler <siretart@tauware.de> | yes | debian upstream | 2026-09-21 | |
| 0007-utils-ioutil-Respect-context-cancellation-after-read.patch | utils/ioutil: Respect context cancellation in NewContextReader/Writer In NewContextReader and NewContextWriter, reading or writing after context cancellation can non-deterministically succeed with data rather than returning (0, ctx.Err()) (Debian bug #1142868). In the v5.x series, these helpers delegate to the legacy, unmaintained github.com/jbenet/go-context/io (ctxio) library. Its Read() implementation selects between a worker goroutine channel and <-ctx.Done(). For non-blocking inputs like in-memory buffers, both channels are ready simultaneously, and Go's select pseudo-randomly picks the data channel instead of the cancelled context. In v6, upstream dropped the ctxio dependency (commit 21fd3e1d) and inlined context.go, fixing this race in commit 6e16689 (#1323) by verifying ctx.Err(). Rather than backporting the intrusive v6 refactor to v5.x, this patch adapts upstream's fix by wrapping ctxio in utils/ioutil/common.go to check ctx.Err() before and after I/O. |
Reinhard Tartler <siretart@tauware.de> | not-needed | debian upstream | vendor, based on https://github.com/go-git/go-git/commit/6e1668944ca7ecf52656c6044987c01b89b4d6c5 | 2026-09-21 |