[MacPorts] #61060: unison @2.51.2_3 is actually version 2.31
MacPorts
noreply at macports.org
Mon Aug 24 18:55:36 UTC 2020
#61060: unison @2.51.2_3 is actually version 2.31
--------------------------+--------------------
Reporter: ShadSterling | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.6.3
Keywords: | Port: unison
--------------------------+--------------------
unison @2.51.2_3 has never actually been version 2.51 (even though that
version does exist), and now it seems to have changed to an even older
version.
I've been using Unison to sync files on my mac with files on an OpenSUSE
host, so I need to have matching versions on both hosts. Long ago that
was easy, but after the update to OCaml 4.01 (in 2015?) I started having
to jump through weird hoops to get matching versions.
Lately MacPorts unison @2.51.2_3 has actually been version 2.40, and I've
been able to keep the same version on the OpenSUSE host by keeping my own
copy of the obsolete OpenSUSE package. Yesterday or today MacPorts unison
@2.51.2_3 has changed to be version 2.31, which is old enough that I can't
find a copy of the old obsolete package for OpenSUSE.
MacPorts used to have unison @2.48 (that was actually Unison 2.48), and I
just had to rebuild the package using matching OCaml; I think it was with
a macOS update after which MacPorts dropped support for older GCC that
MacPorts unison changed to package version 2.51 but Unison version 2.40
and I changed to installing the matching obsolete package on OpenSUSE.
And now it looks like I can't do either.
Can I use macports to install Unison 2.40 or newer? How? What additional
information about my setup would help?
--
Ticket URL: <https://trac.macports.org/ticket/61060>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list