| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| Adjust-mirrorbits.conf-for-Debian.patch | Adjust mirrorbits.conf for Debian - Default templates path - Default GeoIP database location |
Arnaud Rebillout <arnaudr@kali.org> | not-needed | 2023-06-14 | ||
| Add-more-details-to-test-failure-message.patch | Add more details to test failure message On armel, this test failed with a puzzling error message: === RUN TestRefreshNodeList 2023/07/14 03:29:41 Cluster starting... 2023/07/14 03:29:41 <- Node meh-4242 left the cluster cluster_test.go:104: Node meh-4242 should have left 2023/07/14 03:29:41 Cluster stopped --- FAIL: TestRefreshNodeList (0.00s) At first I thought about a flaky test (time-related), but looking at the code, I'm at a loss, the two log messages contradict each other... Plus, I can't reproduce it on a porter box (abel.debian.org). Let's try to add a bit more details to the logs, and do another upload. |
Arnaud Rebillout <arnaudr@kali.org> | not-needed | 2023-07-14 | ||
| set-proto-package-name.patch | set proto package name | Reinhard Tartler <siretart@tauware.de> | not-needed | 2024-07-28 |