aom @3.9.1 cannot be built on PPC Leopard, Mac OS X 10.5.8, because git clone does not work

[ballapete (Peter "Pete" Dyballa)]

When using the original Portfile downloading the source fails with:

fatal: unable to access 'https://aomedia.googlesource.com/aom.git/': Could not resolve host: aomedia.googlesource.com

while ping has no problem:

pete 226 /\  ping aomedia.googlesource.com
PING aomedia.googlesource.com (74.125.206.82): 56 data bytes
64 bytes from 74.125.206.82: icmp_seq=0 ttl=60 time=13.419 ms
64 bytes from 74.125.206.82: icmp_seq=1 ttl=60 time=12.664 ms
64 bytes from 74.125.206.82: icmp_seq=2 ttl=60 time=13.197 ms
64 bytes from 74.125.206.82: icmp_seq=3 ttl=60 time=12.715 ms
^C
--- aomedia.googlesource.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 12.664/12.999/13.419/0.320 ms

[ballapete (Peter "Pete" Dyballa)]

Main.log from PPC Leopard, Mac OS X 10.5.8, for original Portfile

[ballapete (Peter "Pete" Dyballa)]

When I change the IP name with its address in Portfile I get:

Cloning into '/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_multimedia_aom/aom/work/aom-3.9.1'...
fatal: unable to access 'https://74.125.206.82/aom.git/': SSL certificate problem: self-signed certificate
Command failed: /opt/local/bin/git clone --progress https://74.125.206.82/aom.git /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_multimedia_aom/aom/work/aom-3.9.1 2>&1
Exit code: 128

[ballapete (Peter "Pete" Dyballa)]

Main.log from PPC Leopard, Mac OS X 10.5.8, with IP name exchanged with IP address

[ballapete (Peter "Pete" Dyballa)]

With this block in Portfile

homepage            https://storage.googleapis.com/aom-releases/
distname            lib${name}-${version}

checksums           rmd160  e0a04f5b7491c4b395e70f6c476f5fa580ad8c95 \
                    sha256  dba99fc1c28aaade28dda59821166b2fa91c06162d1bc99fde0ddaad7cecc50e \                    size    5524048

the source archive can be fetched and upgraded.

[ryandesign (Ryan Carsten Schmidt)]

Replying to ballapete:

When using the original Portfile downloading the source fails with:

fatal: unable to access 'https://aomedia.googlesource.com/aom.git/': Could not resolve host: aomedia.googlesource.com

It works for me on macOS 12, but:

Replying to ballapete:

With this block in Portfile

homepage            https://storage.googleapis.com/aom-releases/
distname            lib${name}-${version}

checksums           rmd160  e0a04f5b7491c4b395e70f6c476f5fa580ad8c95 \
                    sha256  dba99fc1c28aaade28dda59821166b2fa91c06162d1bc99fde0ddaad7cecc50e \                    size    5524048

the source archive can be fetched and upgraded.

Fetching from a distfile is definitely preferred. The portfile says the reason why we didn't do that is:

# use git fetch rather than downloading a snapshot tarball
# which delivers a different checksum and size on each download
# see https://github.com/google/gitiles/issues/84

However that refers to downloading an automatically-generated tarball from their git system. You appear to have found a source for proper release tarballs that should not have that problem. How did you discover these release tarballs? I can't find them mentioned on the project's homepage.

[ballapete (Peter "Pete" Dyballa)]

After it was clear that git clone does not work on PPC Leopard and neither manually, not even when supplying an environment variable to not check (self-made) certificates, no matter whether I give an I address, an IP name, or an IPv6 address, I just google'd for aom-1.9.2.tar.gz (and also for the xz variant). I checked two sites, Linux related repositories, one provided an MD5 checksum, the second just had the file for download which gave the same checksum on my PowerBook. (On a PowerBook you have a great amount of time to perform other things while a port is being upgraded!)

I think the Linux repo with the MD5 checksum provided the "path name" to the original site which i then used in my patched Portfile.