Package: zeromq3 / 4.3.4-1+deb11u1
Metadata
| Package | Version | Patches format |
|---|---|---|
| zeromq3 | 4.3.4-1+deb11u1 | 3.0 (quilt) |
Patch series
view the series file| Patch | File delta | Description |
|---|---|---|
| disable test_security_curve.patch | (download) |
Makefile.am |
4 2 + 2 - 0 ! |
disable test_security_curve It hangs in buildds that not x86/x64 based. |
| tests_testutil.cpp.patch | (download) |
tests/testutil.cpp |
15 12 + 3 - 0 ! |
--- |
| test_hwm_pubsub tcp fix.patch | (download) |
tests/test_hwm_pubsub.cpp |
18 16 + 2 - 0 ! |
fix flaky test_hwm_pubsub on riscv64 The failure has occasionally been seen on other architectures too, but shows up very frequently on riscv64, particularly in qemu, so is likely timing-dependent. . Upstream has been investigating the flakiness for years, but don't have a perfect fix. The rejected upstream PR this was ported from apparently fails on Windows, but we don't care about that. |
| fix maybe uninitialized.patch | (download) |
tests/test_security_gssapi.cpp |
2 1 + 1 - 0 ! |
--- |
| fix_fork_detection_with_gcc_7.patch | (download) |
RELICENSE/hewlett_packard_enterprise.md |
6 4 + 2 - 0 ! |
[patch 1/2] problem: fix fork detection on gcc 7 Solution: When compiling with gcc 7 and newer, the program produced by AC_CHECK_FUNCS(fork) produces a warning, which results in configure incorrectly disabling fork support. Fix the issue by using an AC_COMPILE_IFELSE which correctly detects fork availability. Tested by running configure and make check on a system with gcc 7 installed, and verifying that HAVE_FORK was defined correctly. See issue #3313. |
1
