port version reports 2.4.2 when built from tag v2.4.3

classic Classic list List threaded Threaded
25 messages Options
12
Reply | Threaded
Open this post in threaded view
|

port version reports 2.4.2 when built from tag v2.4.3

Enrico Maria Crisostomo
Hi,

I've just created a new installation of macports-base from tag v2.4.3 following the instructions in the documentation (basically git checkout v2.4.3, ./configure ..., make and make install) and I've just noticed that `port` reports 2.4.2:

    % which port
    /opt/macports-2.4.3/bin/port
    % port version
    Version: 2.4.2

I built from:

    % git rev-parse HEAD
    a393413460aae5ac9749b994681381087089cdb5

which appears to be the correct v2.4.3:

    * commit a393413460aae5ac9749b994681381087089cdb5 (HEAD, tag: v2.4.3, upstream/release-2.4)
    | Author: Joshua Root <[hidden email]>
    | Date:   Wed Apr 11 10:23:40 2018 +1000
    |
    |     Bump branch version to 2.4.3

Am I missing something obvious or it this a typo?

Cheers,
-- Enrico

Reply | Threaded
Open this post in threaded view
|

Re: port version reports 2.4.2 when built from tag v2.4.3

Joshua Root-8
On 2018-4-11 18:52 , Enrico Maria Crisostomo wrote:

> Hi,
>
> I've just created a new installation of macports-base from tag v2.4.3 following the instructions in the documentation (basically git checkout v2.4.3, ./configure ..., make and make install) and I've just noticed that `port` reports 2.4.2:
>
>     % which port
>     /opt/macports-2.4.3/bin/port
>     % port version
>     Version: 2.4.2
>
> I built from:
>
>     % git rev-parse HEAD
>     a393413460aae5ac9749b994681381087089cdb5
>
> which appears to be the correct v2.4.3:
>
>     * commit a393413460aae5ac9749b994681381087089cdb5 (HEAD, tag: v2.4.3, upstream/release-2.4)
>     | Author: Joshua Root <[hidden email]>
>     | Date:   Wed Apr 11 10:23:40 2018 +1000
>     |
>     |     Bump branch version to 2.4.3
>
> Am I missing something obvious or it this a typo?

I'm not sure how that happened for you. Browsing the tag on GitHub, it
says 2.4.3 in the appropriate places.

<https://github.com/macports/macports-base/blob/v2.4.3/config/macports_version>
<https://github.com/macports/macports-base/blob/v2.4.3/configure#L2790>

Are you sure your shell didn't cache the location of port? Check with
'type port'. (Using 'which' tells you where it would be found if you
cleared the cache.)

- Josh
Reply | Threaded
Open this post in threaded view
|

Re: port version reports 2.4.2 when built from tag v2.4.3

Rainer Müller-4
In reply to this post by Enrico Maria Crisostomo
On 2018-04-11 10:52, Enrico Maria Crisostomo wrote:
> I've just created a new installation of macports-base from tag v2.4.3 following the instructions in the documentation (basically git checkout v2.4.3, ./configure ..., make and make install) and I've just noticed that `port` reports 2.4.2:

Hm, I cannot reproduce this problem. The configure script is supposed to
update the relevant file with the version number.

Check "macports_version" in src/macports1.0/macports_autoconf.tcl in
your working tree.

Rainer
Reply | Threaded
Open this post in threaded view
|

Re: port version reports 2.4.2 when built from tag v2.4.3

Enrico Maria Crisostomo
In reply to this post by Joshua Root-8
Hi Joshua,

Thanks.  The port script was the correct one.  I think I re-configured and built v2.4.3 over a previous v2.4.2 build but I can't confirm.  I cleaned the HEAD and rebuilt and the result is as expected.

I noticed in the documentation that "2.2.3 git install" instructs to make distclean after the build, while "2.2.4 Install multiple MacPorts Copies" does not.  Perhaps amending the documentation may help others not to stumble on this one, even if the blame is to be attributed to the user in this case.  I'll send a PR for that one.

Cheers,
--
Enrico

> On 11 Apr 2018, at 14:17, Joshua Root <[hidden email]> wrote:
>
> On 2018-4-11 18:52 , Enrico Maria Crisostomo wrote:
>> Hi,
>>
>> I've just created a new installation of macports-base from tag v2.4.3 following the instructions in the documentation (basically git checkout v2.4.3, ./configure ..., make and make install) and I've just noticed that `port` reports 2.4.2:
>>
>>    % which port
>>    /opt/macports-2.4.3/bin/port
>>    % port version
>>    Version: 2.4.2
>>
>> I built from:
>>
>>    % git rev-parse HEAD
>>    a393413460aae5ac9749b994681381087089cdb5
>>
>> which appears to be the correct v2.4.3:
>>
>>    * commit a393413460aae5ac9749b994681381087089cdb5 (HEAD, tag: v2.4.3, upstream/release-2.4)
>>    | Author: Joshua Root <[hidden email]>
>>    | Date:   Wed Apr 11 10:23:40 2018 +1000
>>    |
>>    |     Bump branch version to 2.4.3
>>
>> Am I missing something obvious or it this a typo?
>
> I'm not sure how that happened for you. Browsing the tag on GitHub, it
> says 2.4.3 in the appropriate places.
>
> <https://github.com/macports/macports-base/blob/v2.4.3/config/macports_version>
> <https://github.com/macports/macports-base/blob/v2.4.3/configure#L2790>
>
> Are you sure your shell didn't cache the location of port? Check with
> 'type port'. (Using 'which' tells you where it would be found if you
> cleared the cache.)
>
> - Josh

Reply | Threaded
Open this post in threaded view
|

Re: port version reports 2.4.2 when built from tag v2.4.3

Enrico Maria Crisostomo
In reply to this post by Rainer Müller-4
Thanks Rainer,

I can't check it but as I said in my previous mail I think I had forgotten to run `make distclean` when I previously built `v2.4.2`.  And now I see that the `macports_autoconf.tcl` file you cite is an Autoconf config file.  Why this happen now makes sense.

Cheers,
--
Enrico

> On 11 Apr 2018, at 14:22, Rainer Müller <[hidden email]> wrote:
>
> On 2018-04-11 10:52, Enrico Maria Crisostomo wrote:
>> I've just created a new installation of macports-base from tag v2.4.3 following the instructions in the documentation (basically git checkout v2.4.3, ./configure ..., make and make install) and I've just noticed that `port` reports 2.4.2:
>
> Hm, I cannot reproduce this problem. The configure script is supposed to
> update the relevant file with the version number.
>
> Check "macports_version" in src/macports1.0/macports_autoconf.tcl in
> your working tree.
>
> Rainer

Reply | Threaded
Open this post in threaded view
|

Re: port version reports 2.4.2 when built from tag v2.4.3

Joshua Root-8
On 2018-4-11 23:27 , Enrico Maria Crisostomo wrote:
> Thanks Rainer,
>
> I can't check it but as I said in my previous mail I think I had forgotten to run `make distclean` when I previously built `v2.4.2`.  And now I see that the `macports_autoconf.tcl` file you cite is an Autoconf config file.  Why this happen now makes sense.

As Rainer said, running configure is supposed to update that file (and
in my experience it does).

- Josh
Reply | Threaded
Open this post in threaded view
|

Re: port version reports 2.4.2 when built from tag v2.4.3

Enrico Maria Crisostomo
Ok, now I'm sufficiently curious as to dig deeper and replicate what I think the sequence of events were.

> On 11 Apr 2018, at 15:32, Joshua Root <[hidden email]> wrote:
>
> On 2018-4-11 23:27 , Enrico Maria Crisostomo wrote:
>> Thanks Rainer,
>>
>> I can't check it but as I said in my previous mail I think I had forgotten to run `make distclean` when I previously built `v2.4.2`.  And now I see that the `macports_autoconf.tcl` file you cite is an Autoconf config file.  Why this happen now makes sense.
>
> As Rainer said, running configure is supposed to update that file (and
> in my experience it does).
>
> - Josh

Reply | Threaded
Open this post in threaded view
|

Re: port version reports 2.4.2 when built from tag v2.4.3

Enrico Maria Crisostomo
In reply to this post by Joshua Root-8
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

If I clean the repo between the builds, the problem does not happen.

Cheers,
--
Enrico

> On 11 Apr 2018, at 15:32, Joshua Root <[hidden email]> wrote:
>
> On 2018-4-11 23:27 , Enrico Maria Crisostomo wrote:
>> Thanks Rainer,
>>
>> I can't check it but as I said in my previous mail I think I had forgotten to run `make distclean` when I previously built `v2.4.2`.  And now I see that the `macports_autoconf.tcl` file you cite is an Autoconf config file.  Why this happen now makes sense.
>
> As Rainer said, running configure is supposed to update that file (and
> in my experience it does).
>
> - Josh

G A
Reply | Threaded
Open this post in threaded view
|

Re: port version reports 2.4.2 when built from tag v2.4.3

G A
Your path should have /opt/local/bin first.

On Wed, Apr 11, 2018 at 06:48 Enrico Maria Crisostomo <[hidden email]> 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

If I clean the repo between the builds, the problem does not happen.

Cheers,
--
Enrico

> On 11 Apr 2018, at 15:32, Joshua Root <[hidden email]> wrote:
>
> On 2018-4-11 23:27 , Enrico Maria Crisostomo wrote:
>> Thanks Rainer,
>>
>> I can't check it but as I said in my previous mail I think I had forgotten to run `make distclean` when I previously built `v2.4.2`.  And now I see that the `macports_autoconf.tcl` file you cite is an Autoconf config file.  Why this happen now makes sense.
>
> As Rainer said, running configure is supposed to update that file (and
> in my experience it does).
>
> - Josh

Reply | Threaded
Open this post in threaded view
|

Re: port version reports 2.4.2 when built from tag v2.4.3

Enrico Maria Crisostomo
Not if I'm installing a MacPorts instance from source _side-by-side_ with another one installed in /opt/local (e.g.: from the packages).  At least that's my understanding of the documentation.

> On 11 Apr 2018, at 15:52, G A <[hidden email]> wrote:
>
> Your path should have /opt/local/bin first.
>
> On Wed, Apr 11, 2018 at 06:48 Enrico Maria Crisostomo <[hidden email]> 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
>
> If I clean the repo between the builds, the problem does not happen.
>
> Cheers,
> --
> Enrico
>
> > On 11 Apr 2018, at 15:32, Joshua Root <[hidden email]> wrote:
> >
> > On 2018-4-11 23:27 , Enrico Maria Crisostomo wrote:
> >> Thanks Rainer,
> >>
> >> I can't check it but as I said in my previous mail I think I had forgotten to run `make distclean` when I previously built `v2.4.2`.  And now I see that the `macports_autoconf.tcl` file you cite is an Autoconf config file.  Why this happen now makes sense.
> >
> > As Rainer said, running configure is supposed to update that file (and
> > in my experience it does).
> >
> > - Josh
>

Reply | Threaded
Open this post in threaded view
|

Re: port version reports 2.4.2 when built from tag v2.4.3

Joshua Root-8
In reply to this post by Enrico Maria Crisostomo
On 2018-4-11 23:48 , Enrico Maria Crisostomo wrote:
>   * 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

Not sure what to tell you. The code could scarcely be simpler:

<https://github.com/macports/macports-base/blob/release-2.4/src/port/port.tcl#L2821>
<https://github.com/macports/macports-base/blob/release-2.4/src/macports1.0/macports.tcl#L94>

> If I clean the repo between the builds, the problem does not happen.

You could install both ways to different prefixes and do a recursive diff?

- Josh
Reply | Threaded
Open this post in threaded view
|

Re: port version reports 2.4.2 when built from tag v2.4.3

Ryan Schmidt-24
In reply to this post by Enrico Maria Crisostomo

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

Reply | Threaded
Open this post in threaded view
|

Re: port version reports 2.4.2 when built from tag v2.4.3

Enrico Maria Crisostomo


> On 12 Apr 2018, at 02:30, Ryan Schmidt <[hidden email]> 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


Reply | Threaded
Open this post in threaded view
|

Re: port version reports 2.4.2 when built from tag v2.4.3

Ryan Schmidt-24

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.


Reply | Threaded
Open this post in threaded view
|

Re: 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 <[hidden email]> 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.



Reply | Threaded
Open this post in threaded view
|

Re: port version reports 2.4.2 when built from tag v2.4.3

Ryan Schmidt-24

On Apr 12, 2018, at 17:42, Jack Howarth wrote:

> This issue

"This issue" isn't an issue, it's just a misunderstanding of how the shell caches information.

> 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.

That's a server problem that should be resolved within the hour.

Reply | Threaded
Open this post in threaded view
|

Re: port version reports 2.4.2 when built from tag v2.4.3

Rainer Müller-4
In reply to this post by Jack Howarth
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
Reply | Threaded
Open this post in threaded view
|

Re: port version reports 2.4.2 when built from tag v2.4.3

Jack Howarth


On Thu, Apr 12, 2018 at 6:47 PM, Rainer Müller <[hidden email]> 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? 

Reply | Threaded
Open this post in threaded view
|

Re: port version reports 2.4.2 when built from tag v2.4.3

Ryan Schmidt-24

On Apr 12, 2018, at 17:54, Jack Howarth wrote:

> On Thu, Apr 12, 2018 at 6:47 PM, Rainer Müller wrote:
>> 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
>
> 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?

What do you mean?

You already have MacPorts 2.4.3 installed. There is nothing left to do but to go forth and use it.


Reply | Threaded
Open this post in threaded view
|

Re: port version reports 2.4.2 when built from tag v2.4.3

Ryan Schmidt-24

On Apr 12, 2018, at 18:02, Jack Howarth wrote:

> Okay. I was confused as to whether the installer contained the complete ports repo or if it had to download that from the servers. I'm used to fink where the installer only provides a core set of the base package files and the rest have to be obtained from their servers.

MacPorts is the same. The installer installs the base code, and then runs "sudo port selfupdate" which updates base to the latest version *and* downloads the collection of portfiles. The collection of portfiles is not tied to a specific version of MacPorts, but is meant to always be used with the latest (or nearly the latest) version of MacPorts.


12