Update pypy3.9-7.3.13 checksums

[ecerulm]

The checksum for https://downloads.python.org/pypy/pypy3.9-v7.3.13-macos_x86_64.tar.bz2 should be updated

curl -O https://downloads.python.org/pypy/pypy3.9-v7.3.13-macos_x86_64.tar.bz2
shasum  -a 256 pypy3.9-v7.3.13-macos_x86_64.tar.bz2
180802aa0122d4a05ec480bf3130c78591ba88fdde25d8e65a92d4a798b318a3  pypy3.9-v7.3.13-macos_x86_64.tar.bz2

The https://www.pypy.org/checksums.html says also

18ad7c9cb91c5e8ef9d40442b2fd1f6392ae113794c5b6b7d3a45e04f19edec6  pypy3.9-v7.3.15-macos_x86_64.tar.bz2

but pyenv is expecting fb1ff67340353e837498102fec2b0b45744bb189dced57ee2e00045785e69662

---

Too many issues will kill our team's development velocity, drastically.
Make sure you have checked all steps below.

Prerequisite

• Make sure your problem is not listed in the common build problems.
• Make sure no duplicated issue has already been reported in the pyenv issues. You should look for closed issues, too.
• Make sure you are not asking us to help solving your specific issue.
  • GitHub issues is opened mainly for development purposes. If you want to ask someone to help solving your problem, go to some community site like Gitter, StackOverflow, etc.
• Make sure your problem is not derived from packaging (e.g. Homebrew).
  • Please refer to the package documentation for the installation issues, etc.
• [ x Make sure your problem is not derived from plugins.
  • This repository is maintaining pyenv and the default python-build plugin only. Please refrain from reporting issues of other plugins here.

Description

• Platform information: macOS Sonoma 14.2.1

• OS architecture (e.g. amd64): amd64

• pyenv version: 2.3.35

• Python version:

• C Compiler information (e.g. gcc 7.3):

• Please attach the debug trace of the failing command as a gist:

  • https://gist.github.com/ecerulm/13fadcc47491907f557831d12eb861c5

• If you have a problem with installing Python, please also attach config.log from the build directory

  • The build directory is reported after the "BUILD FAILED" message and is usually under /tmp.

• If the build succeeds but the problem is still with the build process (e.g. the resulting Python is missing a feature), please attach

  • the debug trace from reinstalling the faulty version with env PYENV_DEBUG=1 pyenv install -f -k -v <version> 2>&1 | tee trace.log
  • config.log from the build directory. When using pyenv install with -k as per above, the build directory will be under $PYENV_ROOT/sources.

[ecerulm]

@native-api , I see that you merged a similar issue #2208 some time ago, so maybe you can look into this one too?

[native-api]

Since the CI passed on 7.3.13, the releases must've been reuploaded upstream.
This is definitely not a copy-paste issue from a previous script.