Yeah, I trapped into the patch file problem you were describing.
> Am 28.03.2025 um 12:48 schrieb Christoph Kukulies via macports-users > <macports-users@lists.macports.org>: > > Thanks. I followed the instructions in that link to the Wiki. > Unfortunately I'm getting: > > ---> Applying patches to opencascade > Error: Failed to patch opencascade: command execution failed > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_opencascade/opencascade/main.log > for details. > Error: Follow https://guide.macports.org/#project.tickets > <https://guide.macports.org/#project.tickets> if you believe there is a bug. > Error: Processing of port opencascade failed > > <main.log> > > >> Am 28.03.2025 um 12:24 schrieb Ryan Carsten Schmidt <ryandes...@macports.org >> <mailto:ryandes...@macports.org>>: >> >> On Mar 28, 2025, at 04:32, Christoph Kukulies wrote: >>> >>> % port livecheck opencascade >>> opencascade seems to have been updated (port version: 7.8.0, new version: >>> 7.9.0 >>> >>> How do I activate 7.9.0 ? >> >> The high-level overview is that one would change the Portfile and the files >> directory in whatever way is necessary to allow the new version to install. >> That's intentionally vague because the specifics vary from port to port and >> often even from one version of a port to another. Figuring out what is >> needed to update a port to a new version is the bulk of the work done by >> MacPorts contributors. >> >> Ideally the port's maintainer timely notices when new updates are available >> and updates it. If they don't or for ports with no maintainer, anyone can >> submit an update as a pull request (ideally) or by attaching a diff to a >> ticket. >> >> In the simplest case, the version field would be updated to the new version >> and the checksums field would be updated to match. These most basic steps >> are explained in detail here: >> >> https://trac.macports.org/wiki/howto/Upgrade >> <https://trac.macports.org/wiki/howto/Upgrade> >> >> If the port has tests enabled, ideally one would run them and see if any new >> test failures appear as a result of the update. >> >> Often, more than that will be needed. For example, an existing patch file >> may need to be updated so that it continues to work with the new version. Or >> the patch may no longer be needed because it was already incorporated into >> the new version. Or a new patch may be needed to fix a new bug that wasn't >> present in the old version. The new version may have new dependencies or it >> may no longer need existing dependencies. Etc, etc. >> >
signature.asc
Description: Message signed with OpenPGP
