I have an error from the installer about dependencies. It appears to not like my pkgproxy server as it is reporting a 404 error yet when I use curl on the URL it downloads the file just fine.
Strange - tl-setupuses standard dnf hooks, so if it works outside of ThinLinc then it should work with tl-setup too. Does a normal dnf update (perhaps with a dnf clean all first) work?
Hi Aaron,
Yes, a normal dnf update works fine. I tried running “dnf clean all” followed by “dnf update --refresh,” but the installer still crashed with the same error.
However, after I modified my repo file in /etc/yum.repos.d to bypass pkgproxy, the installation succeeded. It appears the installer has an issue with the dnf proxy called pkgproxy.
Best,
Gene
It appears the installer has an issue with the dnf proxy called pkgproxy.
There’s at least one thing going on that isn’t the proxy: tl-setup isn’t using the same dnf as your shell. On Fedora 41+ the dnf command is dnf5, while tl-setup drives the old dnf4 Python API (python3-dnf). Separate library, separate cache (/var/cache/dnf vs /var/cache/libdnf5), which is why dnf clean all made no difference. It cleaned a cache tl-setup never looks at. So “works with dnf, fails in tl-setup” is unfortunately not as strange as it sounds.
As for the 404 itself, I don’t know yet. One guess worth ruling out: both failing files are .zck (zchunk) metadata, which dnf fetches with HTTP byte-range requests rather than a plain GET, so your curl test may not have hit the same path. If you get a chance, on a URL the proxy hasn’t cached yet:
curl -s -o /dev/null -w '%{http_code}\n' -r 0-255 <zck-url>
curl -s -o /dev/null -w '%{http_code}\n' <zck-url>
If those differ, that would point at range handling somewhere between dnf and the proxy. If they’re the same, my guess is wrong and the proxy’s access log for those two requests would help.
Either way, one thing I did confirm: tl-setup doesn’t read /etc/dnf/dnf.conf at all, only /etc/yum.repos.d. So if you were relying on anything set there, it wouldn’t apply.