[pkg-go] Bug#1110892: podman: Podman/Buildah build fails with corporate proxies when using ADD command in Dockerfile

[Alexander Merkle]

Package: podman
Version: 5.4.2+ds1-2+b1
Severity: normal

Dear Maintainer,

I noticed the version of podman & buildah in Debian trixie (by the time of
writing also forky/sid) does include a
regression regarding corporate proxies when building images. Basically I
submitted a patch to the `buildah` project
[1] that fixed the bug initially reported at [2].

The behavior is such that `Dockerfile`s that use the `ADD` command to 
download
a file do not work when a corporate proxy is in place
```
FROM <base>

ADD <URL> /file
```


[1] https://github.com/containers/buildah/pull/6274
[2] https://github.com/containers/podman/issues/25220


-- System Information:
Debian Release: 13.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.27+bpo-amd64 (SMP w/24 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages podman depends on:
ii conmon 2.1.12-4
ii containerd.io [runc] 1.7.27-1
ii crun 1.21-1
ii golang-github-containers-common 0.62.2+ds1-2
ii init-system-helpers 1.68
ii libc6 2.41-12
ii libgpgme11t64 1.24.2-3
ii libseccomp2 2.6.0-2
ii libsqlite3-0 3.46.1-7
ii libsubid5 1:4.17.4-2
ii netavark 1.14.0-2

Versions of packages podman recommends:
ii buildah 1.39.3+ds1-1+b6
ii ca-certificates 20250419
ii catatonit 0.2.1-2+b3
ii containers-storage 1.57.2+ds1-1+b2
ii criu 4.1.1-1
ii dbus-user-session 1.16.2-2
ii libcriu2 4.1.1-1
ii passt 0.0~git20250503.587980c-2
ii slirp4netns 1.2.1-1.1
ii uidmap 1:4.17.4-2

Versions of packages podman suggests:
pn containernetworking-plugins <none>
pn docker-compose <none>
ii iptables 1.8.11-2

-- no debconf information