morningman opened a new pull request, #66821: URL: https://github.com/apache/doris/pull/66821
## Proposed changes Two download mirrors in `thirdparty/vars.sh` on this branch are dead, and they break every third party build: | package | current URL | status | |---|---|---| | lzo | `https://fossies.org/linux/misc/lzo-2.10.tar.gz` | **410 Gone** | | libuuid | `https://nchc.dl.sourceforge.net/project/libuuid/libuuid-1.0.3.tar.gz` | unreachable (TLS handshake fails) | The failure is not a clean one. `wget -O` creates its output file before the transfer, so a dead URL leaves a 0-byte archive behind; the md5 check then fails and the retry hits the same dead URL: ``` thirdparty/src/lzo-2.10.tar.gz md5sum check failed! except-md5 39d3f3f9c55c87b1e5d6888e1420f4b5 actual-md5 d41d8cd98f00b204e9800998ecf8427e <- md5 of an empty file Downloading lzo-2.10.tar.gz from https://fossies.org/linux/misc/lzo-2.10.tar.gz Failed to download lzo-2.10.tar.gz. attemp: 2 Failed to download lzo-2.10.tar.gz ``` This has been failing the `apache/doris-thirdparty` prebuilt pipeline for this branch on every scheduled run since 2026-08-13 — 28 out of 28 runs red in the last 15 hours alone. It also hits anyone building `thirdparty/` from source on this branch. This PR points both at the mirrors `master` already uses: - lzo → `https://www.oberhumer.com/opensource/lzo/download/lzo-2.10.tar.gz` (upstream) - libuuid → `https://downloads.sourceforge.net/project/libuuid/libuuid-1.0.3.tar.gz` (generic SourceForge redirector) Both serve byte-identical archives, verified against the checksums already in `vars.sh`, so `LZO2_MD5SUM` and `LIBUUID_MD5SUM` are unchanged: ``` lzo-2.10.tar.gz 39d3f3f9c55c87b1e5d6888e1420f4b5 (LZO2_MD5SUM, 600622 bytes) libuuid-1.0.3.tar.gz d44d866d06286c08ba0846aba1086d68 (LIBUUID_MD5SUM, 318256 bytes) ``` `master` and `branch-4.0` already carry the lzo fix; this is the missing backport. A companion PR fixes libuuid on `branch-4.0`. Issue Number: close #xxx -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
