Re: MacPorts 2.9.3 has been released

[Dave Horsfall]

On Mon, 8 Apr 2024, Dave Horsfall wrote:

> Smooth as usual on this ancient box...  Thanks, all.

And I've just realised that everything was installed from packages this 
time; I was wondering why it only took a quarter of an hour...

-- Dave

Re: MacPorts 2.9.3 has been released

[Dave Horsfall]

Smooth as usual on this ancient box...  Thanks, all.

-- Dave

Re: MacPorts 2.9.3 has been released

[Joshua Root]

Dave Horsfall wrote:


I hadn't got around to installing 2.9.2 yet (I do those admin tasks on
Mondays); will 2.9.3 drop cleanly onto 2.9.1?

I ask because I got bitten by a Linux upgrade; apparently Debian (if not
all of them) requires all intermediate upgrades be performed...


We aim for direct upgrades to work across gaps of up to one year. In 
practice, base upgrades often work with much longer gaps. Port upgrades 
often don't if there is any renaming or replacing involved.


- Josh

Re: MacPorts 2.9.3 has been released

[Joshua Root]

On 4/4/2024 15:29, Peter West wrote:
I’ve installed 2.9.3. As with 2.9.2, port selfupdate did not update the 
port install. Is this something you’re aware of?


It always takes a little time for releases to propagate to the rsync 
mirrors. 2.9.2 took longer than usual because of some downtime for the 
master server. 2.9.3 is on the mirrors now.


I’ve been installing these to try to fix the “missing m4” problem, but 
neither seemed to fix it. Should I add a comment to one of the number of 
issues in trac concerning this?


In any case, I’m downgrading to Xcode 15.1.


We don't ship m4 with MacPorts base, so a new base release won't do 
anything for missing m4 issues. Ultimately Apple needs to release a new 
command line tools version that includes m4 again, and in the meantime 
each port that uses m4 needs to either run it by the name 'gm4' instead 
(since Apple still included that), or declare a dependency on the m4 
port. If you notice a port is affected and there is no ticket open for 
it, please open one.


- Josh

Re: MacPorts 2.9.3 has been released

[Sriranga Veeraraghavan via macports-users]

I’m on Ventura 13.6.6 and Xcode 14.3 and I also observed that ‘port selfupdate’ 
didn’t update 2.9.1 to 2.9.2 or 2.9.2 to 2.9.3.  I installed the Ventura 
packages for 2.9.2 and 2.9.3 and both seemed to perform the update properly.

Thanks,

-ranga

> On Apr 3, 2024, at 9:29 PM, Peter West via macports-users 
>  wrote:
> 
> I’ve installed 2.9.3. As with 2.9.2, port selfupdate did not update the port 
> install. Is this something you’re aware of?
> 
> I’ve been installing these to try to fix the “missing m4” problem, but 
> neither seemed to fix it. Should I add a comment to one of the number of 
> issues in trac concerning this?
> 
> In any case, I’m downgrading to Xcode 15.1.
> 
> —
> Peter West
> p...@pbw.id.au
> `Mary Magdalene went and said to the disciples, “I have seen the Lord”; and 
> she told them that he had said these things to her.`
> 
>> On 4 Apr 2024, at 12:00 PM, Joshua Root  wrote:
>> 
>> The MacPorts Project is pleased to announce the release of version
>> 2.9.3. This is a bugfix release with small changes only. See the
>> ChangeLog [1] for the list of changes.
>> 
>> If you already have MacPorts installed, the preferred method for
>> updating is to run:
>> 
>>  sudo port selfupdate
>> 
>> For new installs, there are also package installers available for macOS
>> versions ranging from macOS 14 Sonoma all the way back to 10.4 at [2]. The 
>> source is also available as tarballs compressed with gzip or bzip2, or from 
>> the git tag [3].
>> 
>> Detached PGP signatures for the disk images, packages and source
>> tarballs have been made with my key, which is available on the
>> keyservers and my MacPorts wiki page [4], the fingerprint being:
>> 
>> 0x01FF673FB4AAE6CD: C403 7936 5723 6DCF 2E58  0C02 01FF 673F B4AA E6CD
>> 
>> Josh
>> (on behalf of the MacPorts Port Managers)
>> 
>> [1] 
>> [2] 
>> [3] 
>> [4] 
> 

Re: MacPorts 2.9.3 has been released

[Dave Horsfall]

On Thu, 4 Apr 2024, Joshua Root wrote:

> The MacPorts Project is pleased to announce the release of version 
> 2.9.3. This is a bugfix release with small changes only. See the 
> ChangeLog [1] for the list of changes.

[...]

I hadn't got around to installing 2.9.2 yet (I do those admin tasks on 
Mondays); will 2.9.3 drop cleanly onto 2.9.1?

I ask because I got bitten by a Linux upgrade; apparently Debian (if not 
all of them) requires all intermediate upgrades be performed...

-- Dave

Re: MacPorts 2.9.3 has been released

[Peter West via macports-users]

I’ve installed 2.9.3. As with 2.9.2, port selfupdate did not update the port 
install. Is this something you’re aware of?

I’ve been installing these to try to fix the “missing m4” problem, but neither 
seemed to fix it. Should I add a comment to one of the number of issues in trac 
concerning this?

In any case, I’m downgrading to Xcode 15.1.

—
Peter West
p...@pbw.id.au
`Mary Magdalene went and said to the disciples, “I have seen the Lord”; and she 
told them that he had said these things to her.`

> On 4 Apr 2024, at 12:00 PM, Joshua Root  wrote:
> 
> The MacPorts Project is pleased to announce the release of version
> 2.9.3. This is a bugfix release with small changes only. See the
> ChangeLog [1] for the list of changes.
> 
> If you already have MacPorts installed, the preferred method for
> updating is to run:
> 
>  sudo port selfupdate
> 
> For new installs, there are also package installers available for macOS
> versions ranging from macOS 14 Sonoma all the way back to 10.4 at [2]. The 
> source is also available as tarballs compressed with gzip or bzip2, or from 
> the git tag [3].
> 
> Detached PGP signatures for the disk images, packages and source
> tarballs have been made with my key, which is available on the
> keyservers and my MacPorts wiki page [4], the fingerprint being:
> 
> 0x01FF673FB4AAE6CD: C403 7936 5723 6DCF 2E58  0C02 01FF 673F B4AA E6CD
> 
> Josh
> (on behalf of the MacPorts Port Managers)
> 
> [1] 
> [2] 
> [3] 
> [4] 

MacPorts 2.9.3 has been released

[Joshua Root]

The MacPorts Project is pleased to announce the release of version
2.9.3. This is a bugfix release with small changes only. See the
ChangeLog [1] for the list of changes.

If you already have MacPorts installed, the preferred method for
updating is to run:

  sudo port selfupdate

For new installs, there are also package installers available for macOS
versions ranging from macOS 14 Sonoma all the way back to 10.4 at [2]. 
The source is also available as tarballs compressed with gzip or bzip2, 
or from the git tag [3].


Detached PGP signatures for the disk images, packages and source
tarballs have been made with my key, which is available on the
keyservers and my MacPorts wiki page [4], the fingerprint being:

0x01FF673FB4AAE6CD: C403 7936 5723 6DCF 2E58  0C02 01FF 673F B4AA E6CD

Josh
(on behalf of the MacPorts Port Managers)

[1] 
[2] 
[3] 
[4] 


OpenPGP_signature.asc
Description: OpenPGP digital signature