[MacPorts] #71364: libcdio-paranoia @2.0.1: Unable to verify file checksums

[MacPorts]

#71364: libcdio-paranoia @2.0.1: Unable to verify file checksums
-------------------------------+--------------------
  Reporter:  telemachus        |      Owner:  (none)
      Type:  defect            |     Status:  new
  Priority:  Normal            |  Milestone:
 Component:  ports             |    Version:  2.10.4
Resolution:                    |   Keywords:
      Port:  libcdio-paranoia  |
-------------------------------+--------------------

Comment (by ryandesign):

 The file we mirrored in October 2019 that is still on our distfiles
 servers today has the right checksums. The one available from GitHub today
 has different checksums.

 The two archives are identical except that the name of the enclosing
 directory has changed from `rocky-libcdio-paranoia-db4dfff` to `libcdio-
 libcdio-paranoia-db4dfff`. This is what happens when a project moves from
 one GitHub developer to another if the port uses the old deprecated
 download method, which this port does by not specifying a value for
 `github.tarball_from`.

 Version 10.2+2.0.2 was released in May 2024. We should update to this
 version which will solve the problem. When we do, since the project offers
 release downloads, we should use it by specifying `github.tarball_from
 releases` and, since they offer a bzip2-compressed release download,
 `use_bzip2 yes`. Release downloads don't change unless the developer
 changes them.

 If the release download is not suitable for some reason and we need to
 continue to use an automatically-generated tarball, we should specify
 `github.tarball_from archive`; archive downloads are not susceptible to
 top-level directory renaming when the author changes as the older download
 method is.

-- 
Ticket URL: <https://trac.macports.org/ticket/71364#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS