port version reports 2.4.2 when built from tag v2.4.3

Jack Howarth howarth.at.macports at gmail.com
Thu Apr 12 22:54:10 UTC 2018


On Thu, Apr 12, 2018 at 6:47 PM, Rainer Müller <raimue at macports.org> wrote:

> On 2018-04-13 00:42, Jack Howarth wrote:
> > This issue might also be impacting the High Sierra macports 2.4.3
> > installer image as well. After installing it on a machine with no
> > /opt/local, I get the following from 'sudo port self update'...
> >
> > --->  Updating MacPorts base sources using rsync
> >
> > MacPorts base version 2.4.3 installed,
> >
> > MacPorts base version 2.4.2 downloaded.
>
> It is actually an unrelated problem. The new version is not yet
> available over selfupdate. The script that is supposed to update the
> rsync server is failing.
>
> Check this and following messages in the thread on macports-users:
> https://lists.macports.org/pipermail/macports-users/2018-April/044969.html
>
> Rainer
>

So I assume there is no simple way to just reconfigure the installed 2.4.3
macports to use a 2.4.3 branch git repo?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20180412/12becb7f/attachment.html>


More information about the macports-dev mailing list