port version reports 2.4.2 when built from tag v2.4.3

[Jack Howarth]

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.

--->  Updating the ports tree

--->  MacPorts base is probably trunk or a release candidate


The ports tree has been updated. To upgrade your installed ports, you
should run

  port upgrade outdated

When I execute 'sudo port upgrade outdated', I get...

Nothing to upgrade.


On Thu, Apr 12, 2018 at 12:44 PM, Ryan Schmidt <ryandesign at macports.org>
wrote:

>
> On Apr 12, 2018, at 03:39, Enrico Maria Crisostomo wrote:
>
> > On 12 Apr 2018, at 02:30, Ryan Schmidt wrote:
> >
> >> On Apr 11, 2018, at 08:48, Enrico Maria Crisostomo wrote:
> >>
> >>> Well, I replicated it:
> >>>
> >>> * Clean the repo (e.g.: git clean -xfd)
> >>> * git checkout v2.4.2
> >>> * build and install 2.4.2:
> >>>
> >>>    $ export PATH=/bin:/sbin:/usr/bin:/usr/sbin
> >>>    $ MP_PREFIX=/opt/macports-2.4.2
> >>>    $ ./configure --prefix=$MP_PREFIX --with-applications-dir=$MP_
> PREFIX/Applications
> >>>    $ make
> >>>    $ sudo make install
> >>>
> >>> * open new terminal
> >>> * git checkout v2.4.3
> >>> * configure 2.4.3:
> >>>
> >>>    $ export PATH=/bin:/sbin:/usr/bin:/usr/sbin
> >>>    $ MP_PREFIX=/opt/macports-2.4.3
> >>>    $ ./configure --prefix=$MP_PREFIX --with-applications-dir=$MP_
> PREFIX/Applications
> >>>
> >>> * At this point src/macports1.0/macports_autoconf.tcl correctly
> contains `variable macports_version "2.4.3"`
> >>> * build and install 2.4.3:
> >>>
> >>>    $ make
> >>>    $ sudo make install
> >>>
> >>> * At this point /opt/macports-2.4.3/libexec/macports/lib/macports1.0/macports_autoconf.tcl
> correctly contains `variable macports_version "2.4.3"`.
> >>> * But port reports 2.4.2:
> >>>
> >>>    % echo path
> >>>    /opt/macports-2.4.3/bin:/opt/macports-2.4.3/sbin:/bin:/usr/
> bin:/usr/ucb:/usr/local/bin
> >>>    % type port
> >>>    port is /opt/macports-2.4.3/bin/port
> >>>    % port version
> >>>    Version: 2.4.2
> >>
> >> Just to be absolutely certain which `port' binary you're running:
> >>
> >> What happens if you run:
> >>
> >> /opt/macports-2.4.3/bin/port version
> >
> > Hi Ryan,
> >
> > This happens:
> >
> >    % /opt/macports-2.4.3-clean/bin/port version
> >    Version: 2.4.3
>
> Then I would say that MacPorts is working correctly. I would guess that
> the problem occurred because of your shell's cached lookup of the port
> command in the previous /opt/macports-2.4.2 location.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20180412/cb94901e/attachment-0001.html>