Issue with downloading Podman package via Nexus due to illegal character in dependency version

Hi,

I’m encountering an issue when trying to download the Podman package via my Nexus repository proxy. The problem occurs because one of the dependencies (passt) contains an illegal character (^) in its version string. I’m using AlmaLinux 9.

The error when trying to download through Nexus is:

wget http://*******/repository/yum-almalinux-proxy/9/AppStream/x86_64/os/Packages/passt-0%5E20240806.gee36266-2.el9.x86_64.rpm
--2024-11-22 12:15:34--  http://*******/repository/yum-almalinux-proxy/9/AppStream/x86_64/os/Packages/passt-0%5E20240806.gee36266-2.el9.x86_64.rpm 
Connecting to *******:80... connected.
HTTP request sent, awaiting response... 400 Invalid repository path
2024-11-22 12:15:34 ERROR 400: Invalid repository path.

And in the Nexus logs, I get this warning:

2024-11-22 12:15:34,947+0100 WARN  [qtp1272403974-3062]  *UNKNOWN org.sonatype.nexus.repository.yum.orient.internal.proxy.OrientYumProxyFacetImpl - Unable to resolve url. Reason: Illegal character in path at index 38: 9/AppStream/x86_64/os/Packages/passt-0^20240806.gee36266-2.el9.x86_64.rpm
2024-11-22 12:15:34,948+0100 WARN  [qtp1272403974-3062]  *UNKNOWN org.sonatype.nexus.repository.httpbridge.internal.ViewServlet - Bad request. Reason: Invalid repository path

When I try to download from the official AlmaLinux repository, it works fine:

wget https://repo.almalinux.org/almalinux/9/AppStream/x86_64/os/Packages/passt-0%5E20240806.gee36266-2.el9.x86_64.rpm

This issue didn’t occur a week ago when I was using the podman-4.9.4-16.el9_4.x86_64.rpm package, but now it’s only available as version 5.2.2-9.el9_5, which has this dependency issue.

Does anyone have experience with this or suggestions on how to resolve it? Is there a way to handle illegal characters like ^ in the version string when using Nexus as a proxy?

Additional info: I am using Nexus version OSS 3.51.0-01

Thanks in advance!

Are you using the latest version of Nexus? I recall a character encoding issue being fixed at some point though I can’t definitively say it was the issue you’re experiencing.

1 Like