MacPorts 2.4.1 has been released

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

MacPorts 2.4.1 has been released

Joshua Root-8
The MacPorts Project is pleased to announce the release of version
2.4.1. 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 10.12,
10.11, 10.10, 10.9, 10.8, 10.7, 10.6 and 10.5 (10.6 is universal
i386/x86_64; 10.5 is i386/ppc, the rest are x86_64) 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] <https://github.com/macports/macports-base/blob/release-2.4/ChangeLog>
[2] <https://www.macports.org/install.php>
[3] <https://github.com/macports/macports-base/releases/tag/v2.4.1>
[4] <https://trac.macports.org/wiki/jmr>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: MacPorts 2.4.1 has been released

Al Varnell

On Sun, Feb 26, 2017 at 04:45 AM, Joshua Root wrote:

>
>
> The MacPorts Project is pleased to announce the release of version
> 2.4.1. 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 10.12,
> 10.11, 10.10, 10.9, 10.8, 10.7, 10.6 and 10.5 (10.6 is universal i386/x86_64; 10.5 is i386/ppc, the rest are x86_64) 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] <https://github.com/macports/macports-base/blob/release-2.4/ChangeLog>
> [2] <https://www.macports.org/install.php>
> [3] <https://github.com/macports/macports-base/releases/tag/v2.4.1>
> [4] <https://trac.macports.org/wiki/jmr>

Seem to be problems with the Seattle mirror again:

$ sudo port -v selfupdate
--->  Updating MacPorts base sources using rsync
###############################################################################

This mirror is managed by Pacific Northwest National Labratory.
It is located in Richland, WA.

If you have any questions, or problems, please email:
mirror at pnnl dot gov

###############################################################################


@ERROR: Unknown module 'macports'
rsync error: error starting client-server protocol (code 5) at /SourceCache/rsync/rsync-45/rsync/main.c(1398) [receiver=2.6.9]
Command failed: /usr/bin/rsync -rtzv --delete-after rsync://sea.us.rsync.macports.org/macports/release/tarballs/base.tar /opt/local/var/macports/sources/sea.us.rsync.macports.org/macports/release/tarballs
Exit code: 5


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: MacPorts 2.4.1 has been released

Ryan Schmidt-24

> On Feb 26, 2017, at 12:26, Al Varnell <[hidden email]> wrote:
>
>
> On Sun, Feb 26, 2017 at 04:45 AM, Joshua Root wrote:
>>
>>
>> The MacPorts Project is pleased to announce the release of version
>> 2.4.1. 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 10.12,
>> 10.11, 10.10, 10.9, 10.8, 10.7, 10.6 and 10.5 (10.6 is universal i386/x86_64; 10.5 is i386/ppc, the rest are x86_64) 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] <https://github.com/macports/macports-base/blob/release-2.4/ChangeLog>
>> [2] <https://www.macports.org/install.php>
>> [3] <https://github.com/macports/macports-base/releases/tag/v2.4.1>
>> [4] <https://trac.macports.org/wiki/jmr>
>
> Seem to be problems with the Seattle mirror again:
>
> $ sudo port -v selfupdate
> --->  Updating MacPorts base sources using rsync
> ###############################################################################
>
> This mirror is managed by Pacific Northwest National Labratory.
> It is located in Richland, WA.
>
> If you have any questions, or problems, please email:
> mirror at pnnl dot gov
>
> ###############################################################################
>
>
> @ERROR: Unknown module 'macports'
> rsync error: error starting client-server protocol (code 5) at /SourceCache/rsync/rsync-45/rsync/main.c(1398) [receiver=2.6.9]
> Command failed: /usr/bin/rsync -rtzv --delete-after rsync://sea.us.rsync.macports.org/macports/release/tarballs/base.tar /opt/local/var/macports/sources/sea.us.rsync.macports.org/macports/release/tarballs
> Exit code: 5
>
>

I think the only problem is that you're trying to access an rsync module called "macports", and the Seattle mirror doesn't provide a module by that name.

According to https://trac.macports.org/wiki/Mirrors , we've never claimed that they provide a module by that name. Consult that wiki page for the correct settings to use for that mirror.

It would be nice if the Seattle mirror would add a module called "macports", since that is what we do on our primary server and recommend mirror operators do as well. Mirror operators may learn more by reading https://trac.macports.org/wiki/Mirroring .


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: MacPorts 2.4.1 has been released

Al Varnell
On Sun, Feb 26, 2017 at 12:14 PM, Ryan Schmidt wrote:

>
> On Feb 26, 2017, at 12:26, Al Varnell wrote:
>> Seem to be problems with the Seattle mirror again:
>>
>> $ sudo port -v selfupdate
>> --->  Updating MacPorts base sources using rsync
>> ###############################################################################
>>
>> This mirror is managed by Pacific Northwest National Labratory.
>> It is located in Richland, WA.
>>
>> If you have any questions, or problems, please email:
>> mirror at pnnl dot gov
>>
>> ###############################################################################
>>
>> @ERROR: Unknown module 'macports'
>> rsync error: error starting client-server protocol (code 5) at /SourceCache/rsync/rsync-45/rsync/main.c(1398) [receiver=2.6.9]
>> Command failed: /usr/bin/rsync -rtzv --delete-after rsync://sea.us.rsync.macports.org/macports/release/tarballs/base.tar /opt/local/var/macports/sources/sea.us.rsync.macports.org/macports/release/tarballs
>> Exit code: 5
>
> I think the only problem is that you're trying to access an rsync module called "macports", and the Seattle mirror doesn't provide a module by that name.
>
> According to https://trac.macports.org/wiki/Mirrors , we've never claimed that they provide a module by that name. Consult that wiki page for the correct settings to use for that mirror.
>
> It would be nice if the Seattle mirror would add a module called "macports", since that is what we do on our primary server and recommend mirror operators do as well. Mirror operators may learn more by reading https://trac.macports.org/wiki/Mirroring .

Thanks.  Looks like I forgot to uncomment "release/tarballs/base.tar" in macports.conf on one of my boot drives the last time I switched.

-Al-




Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

FYI - AWS outage took down GitHub yesterday

William H. Magill-3
In reply to this post by Ryan Schmidt-24
Yesterday (Tuesday 28 February), Amazon Web Services, suffered a significant outage.

Among the services impacted was GitHub.


AWS's S3 outage was so bad Amazon couldn't get into its own dashboard to warn the world

https://www.theregister.co.uk/2017/03/01/aws_s3_outage/

Things were apparently recovered by evening EST.


T.T.F.N.
William H. Magill
# iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.12
# Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.12

[hidden email]
[hidden email]
[hidden email]








Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: FYI - AWS outage took down GitHub yesterday

Ryan Schmidt-24
On Mar 1, 2017, at 11:42, William H. Magill wrote:

Yesterday (Tuesday 28 February), Amazon Web Services, suffered a significant outage.

Among the services impacted was GitHub.

Yes, that's correct. The MacPorts 2.4.1 installers on GitHub could not be accessed during that time. The files have now been mirrored on our own infrastructure, as usual, at:



Loading...