Opened 5 years ago
Last modified 17 months ago
#60199 new update
sphinx4: update to 5prealpha
| Reported by: | chrstphrchvz (Christopher Chavez) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | sphinx4 |
Description (last modified by chrstphrchvz (Christopher Chavez))
Upstream project recommends using the latest release, 5prealpha (released in 2016).
There has also since been occasional development on the project's GitHub repository: https://github.com/cmusphinx/sphinx4
The upstream project's homepage also suggests using its newer Vosk/Kaldi libraries instead.
If this port is kept, it should be migrated to the Java portgroup and have its fallback dependency on deprecated port kaffe removed (#60206).
(I personally do not need this port.)
Change History (4)
comment:1 Changed 5 years ago by chrstphrchvz (Christopher Chavez)
| Description: | modified (diff) |
|---|
comment:2 follow-up: 4 Changed 2 years ago by nxg (Norman Gray)
comment:3 Changed 2 years ago by chrstphrchvz (Christopher Chavez)
Do not rely on https://packages.macports.org for determining whether a port can build; that site is only for prebuilt packages of ports which allow binary redistribution. Even if sphinx4 can build, MacPorts likely will not offer a prebuilt package for it since there is currently no license specified in its Portfile, and so no way for MacPorts to be certain binary redistribution is allowed.
If you want to check whether a port is known to build, please use https://ports.macports.org; in the case of sphinx4 this is mostly unknown because almost no builds of the port have been requested since the launch of https://ports.macports.org a few years ago.
comment:4 Changed 2 years ago by chrstphrchvz (Christopher Chavez)
Replying to nxg:
Currently sphinx4 fails to build, with messages which include:
---> Fetching archive for sphinx4 ---> Attempting to fetch sphinx4-1.0beta5_1.darwin_21.noarch.tbz2 from https://mse.uk.packages.macports.org/sphinx4 ---> Attempting to fetch sphinx4-1.0beta5_1.darwin_21.noarch.tbz2 from https://packages.macports.org/sphinx4 ---> Attempting to fetch sphinx4-1.0beta5_1.darwin_21.noarch.tbz2 from https://fra.de.packages.macports.org/sphinx4and in the log
:info:archivefetch ---> sphinx4-1.0beta5_1.darwin_21.noarch.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified :msg:archivefetch ---> Attempting to fetch sphinx4-1.0beta5_1.darwin_21.noarch.tbz2 from https://mse.uk.packages.macports.org/sphinx4 :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch sphinx4-1.0beta5_1.darwin_21.noarch.tbz2 from https://packages.macports.org/sphinx4 :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch sphinx4-1.0beta5_1.darwin_21.noarch.tbz2 from https://fra.de.packages.macports.org/sphinx4 :debug:archivefetch Fetching archive failed: The requested URL returned error: 404
These messages are expected any time a prebuilt binary archive for a port is unavailable and so normally the port will instead build locally from source. If the local build is failing then please go ahead and open a ticket and attach the full main.log for the build.
(I'm adding this as a comment to this bug, rather than a separate bug, because what I'm seeing might be a consequence of what looks like a slightly transitional state of this port).
Currently sphinx4 fails to build, with messages which include:
and in the log
And true enough, the link https://packages.macports.org/sphinx4 (etc) doesn't exist.