Debian Patches
Status for libuv1/1.53.0-1
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| add-support-for-loong64.patch | Add support for loong64 | Graham Inggs <ginggs@debian.org> | no | debian | ||
| sparc-skip-tcp_oob.diff | Workaround for test failure on old sparc kernels | Luca BRUNO <lucab@debian.org> | not-needed | |||
| disable_ipv6_test.patch | export RES_OPTIONS = attempts:0 makes this test fail | Jérémy Lal <kapouer@melix.org> | not-needed | 2017-10-12 | ||
| skip-multicast-test | Skip multicast test Skip muliticast test to avoid this error on all build daemons: . ok 346 - udp_multicast_interface6 not ok 347 - udp_multicast_join # timeout # Output from process `udp_multicast_join`: (no output) not ok 348 - udp_multicast_join6 # timeout # Output from process `udp_multicast_join6`: (no output) ok 349 - udp_multicast_ttl |
dod | not-needed | |||
| privacy-breach-generic.patch | remove iframe from html doc - avoid privacy breach | Jérémy Lal <kapouer@melix.org> | not-needed | |||
| fix-thread-priority-test | Fix thread priority test Test should not assume to be run at priority 0. . See upstream bug for more details. |
info@bnoordhuis.nl | yes | debian upstream | https://github.com/libuv/libuv/issues/4382 | |
| sh4-disable-io_uring.patch | build on sh4 fails with io_uring | John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> | yes | 2025-08-20 | ||
| test-hurd.patch | Hurd is not Linux | Jérémy Lal <kapouer@melix.org> | yes | 2026-05-26 | ||
| skip-sizeof-t64-test.patch | disable checks to avoid failure on i386 This is not a 32-bit issue. It's a t64-not-on-i386 issue. | Jérémy Lal <kapouer@melix.org> | yes | 2026-09-27 | ||
| 5328.patch | linux: fix value of UV_EFTYPE EFTYPE was never defined on Linux until 7.2. Now that newer kernel headers define it but older kernel headers don't, we get different values for UV_EFTYPE depending on where libuv is compiled: -4028 vs. -134, -136, -169 or -258; the exact value depends on the architecture. This commit technically breaks ABI because people that compile libuv against kernel headers will see the value of UV_EFTYPE flip, but since older kernels don't return the value, and downstream users therefore are unlikely to actually see or use it, it's probably fine. The alternative is to remap the new EFTYPE value to the old one everywhere but that's both a lot of work and it adds overhead. |
Ben Noordhuis <info@bnoordhuis.nl> | no | 2026-10-04 |
All known versions for source package 'libuv1'
- 1.53.0-1 (sid, forky)
- 1.50.0-2 (trixie)
- 1.44.2-1+deb12u1 (bookworm-security, bookworm)
