MacPorts 2.4.3 has been released

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

MacPorts 2.4.3 has been released

Joshua Root-8
The MacPorts Project is pleased to announce the release of version
2.4.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 10.13 all the way back to 10.4 (10.6 is universal
i386/x86_64; 10.5 and 10.4 are 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.3>
[4] <https://trac.macports.org/wiki/jmr>
Reply | Threaded
Open this post in threaded view
|

Re: MacPorts 2.4.3 has been released

Lenore Horner-2


On Apr 10, 2018, at 22:10, Joshua Root <[hidden email]> wrote:

The MacPorts Project is pleased to announce the release of version
2.4.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
Both last night after receiving this announcement and this morning I have run sudo port selfupdate and received the following response.
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.4.2 installed,
MacPorts base version 2.4.2 downloaded.
--->  Updating the ports tree
--->  MacPorts base is already the latest version
Suggestions?
Thanks,
Lenore

Reply | Threaded
Open this post in threaded view
|

Re: MacPorts 2.4.3 has been released

Christopher Jones


On 11/04/18 14:20, Lenore Horner wrote:

>
>
>> On Apr 10, 2018, at 22:10, Joshua Root <[hidden email]
>> <mailto:[hidden email]>> wrote:
>>
>> The MacPorts Project is pleased to announce the release of version
>> 2.4.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
> Both last night after receiving this announcement and this morning I
> have run sudo port selfupdate and received the following response.
> --->  Updating MacPorts base sources using rsync
> MacPorts base version 2.4.2 installed,
> MacPorts base version 2.4.2 downloaded.
> --->  Updating the ports tree
> --->  MacPorts base is already the latest version

I see the same. selfupdate is not offering 2.4.3 as an update.

cheers Chris
Reply | Threaded
Open this post in threaded view
|

Re: MacPorts 2.4.3 has been released

Wahlstedt Jyrki
Same here 🤔

> On 11 Apr 2018, at 16.34, Chris Jones <[hidden email]> wrote:
>
>
>
> On 11/04/18 14:20, Lenore Horner wrote:
>>> On Apr 10, 2018, at 22:10, Joshua Root <[hidden email] <mailto:[hidden email]>> wrote:
>>>
>>> The MacPorts Project is pleased to announce the release of version
>>> 2.4.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
>> Both last night after receiving this announcement and this morning I have run sudo port selfupdate and received the following response.
>> --->  Updating MacPorts base sources using rsync
>> MacPorts base version 2.4.2 installed,
>> MacPorts base version 2.4.2 downloaded.
>> --->  Updating the ports tree
>> --->  MacPorts base is already the latest version
>
> I see the same. selfupdate is not offering 2.4.3 as an update.
>
> cheers Chris
>

Reply | Threaded
Open this post in threaded view
|

Re: MacPorts 2.4.3 has been released

pagani laurent via macports-users
In reply to this post by Lenore Horner-2
Hi,

Lenore Horner wrote:
> Both last night after receiving this announcement and this morning I
> have run sudo port selfupdate and received the following response.
> --->  Updating MacPorts base sources using rsync
> MacPorts base version 2.4.2 installed,
> MacPorts base version 2.4.2 downloaded.
> --->  Updating the ports tree
> --->  MacPorts base is already the latest version
> Suggestions?
>


me too!

Riccardo
Reply | Threaded
Open this post in threaded view
|

Re: MacPorts 2.4.3 has been released

Richard DeLaurell
Sorry to pile on, but same here.

On Wed, Apr 11, 2018 at 9:14 AM Riccardo Mottola via macports-users <[hidden email]> wrote:
Hi,

Lenore Horner wrote:
> Both last night after receiving this announcement and this morning I
> have run sudo port selfupdate and received the following response.
> --->  Updating MacPorts base sources using rsync
> MacPorts base version 2.4.2 installed,
> MacPorts base version 2.4.2 downloaded.
> --->  Updating the ports tree
> --->  MacPorts base is already the latest version
> Suggestions?
>


me too!

Riccardo
Reply | Threaded
Open this post in threaded view
|

Re: MacPorts 2.4.3 has been released

Davide Liessi-2
In reply to this post by Lenore Horner-2
2018-04-11 15:20 GMT+02:00 Lenore Horner <[hidden email]>:
> Both last night after receiving this announcement and this morning I have
> run sudo port selfupdate and received the following response.
> --->  Updating MacPorts base sources using rsync
> MacPorts base version 2.4.2 installed,
> MacPorts base version 2.4.2 downloaded.
> --->  Updating the ports tree
> --->  MacPorts base is already the latest version

The same also here.
Might it be related to the problem described on the macports-dev mailing list?
https://lists.macports.org/pipermail/macports-dev/2018-April/038216.html

Best wishes.
Davide
Reply | Threaded
Open this post in threaded view
|

Re: MacPorts 2.4.3 has been released

Joshua Root-8
On 2018-4-12 01:06 , Davide Liessi wrote:

> 2018-04-11 15:20 GMT+02:00 Lenore Horner <[hidden email]>:
>> Both last night after receiving this announcement and this morning I have
>> run sudo port selfupdate and received the following response.
>> --->  Updating MacPorts base sources using rsync
>> MacPorts base version 2.4.2 installed,
>> MacPorts base version 2.4.2 downloaded.
>> --->  Updating the ports tree
>> --->  MacPorts base is already the latest version
>
> The same also here.
> Might it be related to the problem described on the macports-dev mailing list?
> https://lists.macports.org/pipermail/macports-dev/2018-April/038216.html

No, rsync just hasn't updated yet. The ports are also a bit out of date.
Ryan should be able to take a look before too long.

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

Re: MacPorts 2.4.3 has been released

Ryan Schmidt-24

On Apr 11, 2018, at 10:23, Joshua Root wrote:

> No, rsync just hasn't updated yet. The ports are also a bit out of date.
> Ryan should be able to take a look before too long.

mprsyncup is failing with:

2018-04-11T02:10:34+0000 error: pathspec 'v2.4.3' did not match any file(s) known to git.


Reply | Threaded
Open this post in threaded view
|

Re: MacPorts 2.4.3 has been released

Joshua Root-8
On 2018-4-12 12:39 , Ryan Schmidt wrote:
>
> On Apr 11, 2018, at 10:23, Joshua Root wrote:
>
>> No, rsync just hasn't updated yet. The ports are also a bit out of date.
>> Ryan should be able to take a look before too long.
>
> mprsyncup is failing with:
>
> 2018-04-11T02:10:34+0000 error: pathspec 'v2.4.3' did not match any file(s) known to git.

I guess GitHub changed something? That's the format we've been using
since 2.3.5.

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

Re: MacPorts 2.4.3 has been released

Ryan Schmidt-24

On Apr 11, 2018, at 21:54, Joshua Root wrote:

> On 2018-4-12 12:39 , Ryan Schmidt wrote:
>>
>> On Apr 11, 2018, at 10:23, Joshua Root wrote:
>>
>>> No, rsync just hasn't updated yet. The ports are also a bit out of date.
>>> Ryan should be able to take a look before too long.
>>
>> mprsyncup is failing with:
>>
>> 2018-04-11T02:10:34+0000 error: pathspec 'v2.4.3' did not match any file(s) known to git.
>
> I guess GitHub changed something? That's the format we've been using
> since 2.3.5.

Maybe mprsyncup has not retrieved the new list of tags. We had that problem last time, and Rainer fixed it:

https://github.com/macports/macports-infrastructure/commit/bb8f7886c9c086d80cfdde35d6c7402bd61675b6

But I ran "git tag" in /Volumes/RAID/var/tmp/mprsyncup/release/base and it listed every tag up to v2.4.2 but not v2.4.3.

2018-04-12T03:16:17+0000 + read -r RELEASE_URL
2018-04-12T03:16:17+0000 + '[' -z https://github.com/macports/macports-base/tags/v2.4.3 ']'
2018-04-12T03:16:17+0000 + RBASE_CHANGED=1
2018-04-12T03:16:17+0000 + '[' -d /Volumes/RAID/var/tmp/mprsyncup/release/base/.git ']'
2018-04-12T03:16:17+0000 + cd /Volumes/RAID/var/tmp/mprsyncup/release/base
2018-04-12T03:16:17+0000 + /opt/local/bin/git fetch -q --tags
2018-04-12T03:16:18+0000 ++ /opt/local/bin/git rev-parse HEAD
2018-04-12T03:16:18+0000 + RBASE_OLD_REV=68708e1c5e2a4f21afa95e733c5d34cd0f5c71de
2018-04-12T03:16:18+0000 ++ /usr/bin/basename https://github.com/macports/macports-base/tags/v2.4.3
2018-04-12T03:16:18+0000 + /opt/local/bin/git checkout -q v2.4.3
2018-04-12T03:16:18+0000 error: pathspec 'v2.4.3' did not match any file(s) known to git.


Reply | Threaded
Open this post in threaded view
|

Re: MacPorts 2.4.3 has been released

Clemens Lang-2
Hi,

----- On 12 Apr, 2018, at 05:24, Ryan Schmidt [hidden email] wrote:

> 2018-04-12T03:16:17+0000 + read -r RELEASE_URL
> 2018-04-12T03:16:17+0000 + '[' -z
> https://github.com/macports/macports-base/tags/v2.4.3 ']'
> 2018-04-12T03:16:17+0000 + RBASE_CHANGED=1
> 2018-04-12T03:16:17+0000 + '[' -d
> /Volumes/RAID/var/tmp/mprsyncup/release/base/.git ']'
> 2018-04-12T03:16:17+0000 + cd /Volumes/RAID/var/tmp/mprsyncup/release/base
> 2018-04-12T03:16:17+0000 + /opt/local/bin/git fetch -q --tags
> 2018-04-12T03:16:18+0000 ++ /opt/local/bin/git rev-parse HEAD
> 2018-04-12T03:16:18+0000 +
> RBASE_OLD_REV=68708e1c5e2a4f21afa95e733c5d34cd0f5c71de

Can you remove the -q flag and/or retry running git fetch? That should give us
an idea what went wrong here.

--
Clemens Lang
Reply | Threaded
Open this post in threaded view
|

Re: MacPorts 2.4.3 has been released

Carlo Tambuatco
How goes the update? Any progress?


> On Apr 12, 2018, at 4:50 AM, Clemens Lang <[hidden email]> wrote:
>
> Hi,
>
> ----- On 12 Apr, 2018, at 05:24, Ryan Schmidt [hidden email] wrote:
>
>> 2018-04-12T03:16:17+0000 + read -r RELEASE_URL
>> 2018-04-12T03:16:17+0000 + '[' -z
>> https://github.com/macports/macports-base/tags/v2.4.3 ']'
>> 2018-04-12T03:16:17+0000 + RBASE_CHANGED=1
>> 2018-04-12T03:16:17+0000 + '[' -d
>> /Volumes/RAID/var/tmp/mprsyncup/release/base/.git ']'
>> 2018-04-12T03:16:17+0000 + cd /Volumes/RAID/var/tmp/mprsyncup/release/base
>> 2018-04-12T03:16:17+0000 + /opt/local/bin/git fetch -q --tags
>> 2018-04-12T03:16:18+0000 ++ /opt/local/bin/git rev-parse HEAD
>> 2018-04-12T03:16:18+0000 +
>> RBASE_OLD_REV=68708e1c5e2a4f21afa95e733c5d34cd0f5c71de
>
> Can you remove the -q flag and/or retry running git fetch? That should give us
> an idea what went wrong here.
>
> --
> Clemens Lang

Reply | Threaded
Open this post in threaded view
|

Re: MacPorts 2.4.3 has been released

Ryan Schmidt-24
In reply to this post by Clemens Lang-2
On Apr 12, 2018, at 03:50, Clemens Lang wrote:
>
> Can you remove the -q flag and/or retry running git fetch? That should give us
> an idea what went wrong here.

No change. No additional output is produced.
Reply | Threaded
Open this post in threaded view
|

Re: MacPorts 2.4.3 has been released

Christopher Jones
In reply to this post by Ryan Schmidt-24


On 12/04/18 04:24, Ryan Schmidt wrote:

>
> On Apr 11, 2018, at 21:54, Joshua Root wrote:
>
>> On 2018-4-12 12:39 , Ryan Schmidt wrote:
>>>
>>> On Apr 11, 2018, at 10:23, Joshua Root wrote:
>>>
>>>> No, rsync just hasn't updated yet. The ports are also a bit out of date.
>>>> Ryan should be able to take a look before too long.
>>>
>>> mprsyncup is failing with:
>>>
>>> 2018-04-11T02:10:34+0000 error: pathspec 'v2.4.3' did not match any file(s) known to git.
>>
>> I guess GitHub changed something? That's the format we've been using
>> since 2.3.5.
>
> Maybe mprsyncup has not retrieved the new list of tags. We had that problem last time, and Rainer fixed it:
>
> https://github.com/macports/macports-infrastructure/commit/bb8f7886c9c086d80cfdde35d6c7402bd61675b6
>
> But I ran "git tag" in /Volumes/RAID/var/tmp/mprsyncup/release/base and it listed every tag up to v2.4.2 but not v2.4.3.
>
> 2018-04-12T03:16:17+0000 + read -r RELEASE_URL
> 2018-04-12T03:16:17+0000 + '[' -z https://github.com/macports/macports-base/tags/v2.4.3 ']'
> 2018-04-12T03:16:17+0000 + RBASE_CHANGED=1
> 2018-04-12T03:16:17+0000 + '[' -d /Volumes/RAID/var/tmp/mprsyncup/release/base/.git ']'
> 2018-04-12T03:16:17+0000 + cd /Volumes/RAID/var/tmp/mprsyncup/release/base
> 2018-04-12T03:16:17+0000 + /opt/local/bin/git fetch -q --tags
> 2018-04-12T03:16:18+0000 ++ /opt/local/bin/git rev-parse HEAD
> 2018-04-12T03:16:18+0000 + RBASE_OLD_REV=68708e1c5e2a4f21afa95e733c5d34cd0f5c71de
> 2018-04-12T03:16:18+0000 ++ /usr/bin/basename https://github.com/macports/macports-base/tags/v2.4.3
> 2018-04-12T03:16:18+0000 + /opt/local/bin/git checkout -q v2.4.3
> 2018-04-12T03:16:18+0000 error: pathspec 'v2.4.3' did not match any file(s) known to git.

Maybe I am barking up the wrong tree, but does it mean anything that the
link

https://github.com/macports/macports-base/tags/v2.4.3

leads to "Not Found"

where as

https://github.com/macports/macports-base/tags/

lists the tags fine, and clicking on 2.4.3 leads to

https://github.com/macports/macports-base/releases/tag/v2.4.3

Is it just the link is wrong (changed) ??
Reply | Threaded
Open this post in threaded view
|

Re: MacPorts 2.4.3 has been released

Rainer Müller-4
In reply to this post by Ryan Schmidt-24
On 2018-04-12 17:42, Ryan Schmidt wrote:
> On Apr 12, 2018, at 03:50, Clemens Lang wrote:
>>
>> Can you remove the -q flag and/or retry running git fetch? That should give us
>> an idea what went wrong here.
>
> No change. No additional output is produced.

The problem is that ${RBASE} is fetching from ${TBASE} on the local
filesystem, but the former did not fetch any tags.

Hopefully fixed with:
https://github.com/macports/macports-infrastructure/commit/db64051c6dce12135eeb8114c6f77f320d5097f8

Rainer
Reply | Threaded
Open this post in threaded view
|

Re: MacPorts 2.4.3 has been released

Ryan Schmidt-24
In reply to this post by Christopher Jones

On Apr 12, 2018, at 11:05, Chris Jones wrote:

> On 12/04/18 04:24, Ryan Schmidt wrote:
>> On Apr 11, 2018, at 21:54, Joshua Root wrote:
>>> On 2018-4-12 12:39 , Ryan Schmidt wrote:
>>>>
>>>> On Apr 11, 2018, at 10:23, Joshua Root wrote:
>>>>
>>>>> No, rsync just hasn't updated yet. The ports are also a bit out of date.
>>>>> Ryan should be able to take a look before too long.
>>>>
>>>> mprsyncup is failing with:
>>>>
>>>> 2018-04-11T02:10:34+0000 error: pathspec 'v2.4.3' did not match any file(s) known to git.
>>>
>>> I guess GitHub changed something? That's the format we've been using
>>> since 2.3.5.
>> Maybe mprsyncup has not retrieved the new list of tags. We had that problem last time, and Rainer fixed it:
>> https://github.com/macports/macports-infrastructure/commit/bb8f7886c9c086d80cfdde35d6c7402bd61675b6
>> But I ran "git tag" in /Volumes/RAID/var/tmp/mprsyncup/release/base and it listed every tag up to v2.4.2 but not v2.4.3.
>> 2018-04-12T03:16:17+0000 + read -r RELEASE_URL
>> 2018-04-12T03:16:17+0000 + '[' -z https://github.com/macports/macports-base/tags/v2.4.3 ']'
>> 2018-04-12T03:16:17+0000 + RBASE_CHANGED=1
>> 2018-04-12T03:16:17+0000 + '[' -d /Volumes/RAID/var/tmp/mprsyncup/release/base/.git ']'
>> 2018-04-12T03:16:17+0000 + cd /Volumes/RAID/var/tmp/mprsyncup/release/base
>> 2018-04-12T03:16:17+0000 + /opt/local/bin/git fetch -q --tags
>> 2018-04-12T03:16:18+0000 ++ /opt/local/bin/git rev-parse HEAD
>> 2018-04-12T03:16:18+0000 + RBASE_OLD_REV=68708e1c5e2a4f21afa95e733c5d34cd0f5c71de
>> 2018-04-12T03:16:18+0000 ++ /usr/bin/basename https://github.com/macports/macports-base/tags/v2.4.3
>> 2018-04-12T03:16:18+0000 + /opt/local/bin/git checkout -q v2.4.3
>> 2018-04-12T03:16:18+0000 error: pathspec 'v2.4.3' did not match any file(s) known to git.
>
> Maybe I am barking up the wrong tree, but does it mean anything that the link
>
> https://github.com/macports/macports-base/tags/v2.4.3
>
> leads to "Not Found"
>
> where as
>
> https://github.com/macports/macports-base/tags/
>
> lists the tags fine, and clicking on 2.4.3 leads to
>
> https://github.com/macports/macports-base/releases/tag/v2.4.3
>
> Is it just the link is wrong (changed) ??

That doesn't matter. We don't use the full RELEASE_URL for anything anymore. Ever since we moved to GitHub in late 2016, we only use the last path component of the RELEASE_URL ("v2.4.3" here) as the name of the tag to check out.

The problem is that, although we told the git clone to fetch new tags with "git fetch --tags", it didn't.

We should change the RELEASE_URL to be valid, of course, for the benefit of anyone wanting to click it.

Maybe we should remove the RELEASE_URL entirely, and just use the GitHub API to determine the latest tag.

Reply | Threaded
Open this post in threaded view
|

Re: MacPorts 2.4.3 has been released

Ryan Schmidt-24
In reply to this post by Rainer Müller-4

On Apr 12, 2018, at 11:27, Rainer Müller wrote:

> On 2018-04-12 17:42, Ryan Schmidt wrote:
>> On Apr 12, 2018, at 03:50, Clemens Lang wrote:
>>>
>>> Can you remove the -q flag and/or retry running git fetch? That should give us
>>> an idea what went wrong here.
>>
>> No change. No additional output is produced.
>
> The problem is that ${RBASE} is fetching from ${TBASE} on the local
> filesystem,

Ah! I didn't realize we were doing that.

> but the former did not fetch any tags.
>
> Hopefully fixed with:
> https://github.com/macports/macports-infrastructure/commit/db64051c6dce12135eeb8114c6f77f320d5097f8

This doesn't appear to have helped.

2018-04-12T17:09:42+0000 + '[' '!' -d /Volumes/RAID/opt/local/var/rsync/macports ']'
2018-04-12T17:09:42+0000 + '[' -d /Volumes/RAID/var/tmp/mprsyncup/trunk/base/.git ']'
2018-04-12T17:09:42+0000 + /opt/local/bin/git -C /Volumes/RAID/var/tmp/mprsyncup/trunk/base pull -q
2018-04-12T17:09:44+0000 + /opt/local/bin/git -C /Volumes/RAID/var/tmp/mprsyncup/trunk/base fetch --tags
2018-04-12T17:09:44+0000 + /bin/mkdir -p /Volumes/RAID/opt/local/var/rsync/macports/trunk/base
2018-04-12T17:09:45+0000 + /opt/local/bin/rsync -q -aIC --delete /Volumes/RAID/var/tmp/mprsyncup/trunk/base/ /Volumes/RAID/opt/local/var/rsync/macports/trunk/base
2018-04-12T17:11:46+0000 + read -r RELEASE_URL
2018-04-12T17:11:46+0000 + '[' -z https://github.com/macports/macports-base/tags/v2.4.3 ']'
2018-04-12T17:11:46+0000 + RBASE_CHANGED=1
2018-04-12T17:11:46+0000 + '[' -d /Volumes/RAID/var/tmp/mprsyncup/release/base/.git ']'
2018-04-12T17:11:47+0000 + cd /Volumes/RAID/var/tmp/mprsyncup/release/base
2018-04-12T17:11:47+0000 + /opt/local/bin/git fetch --tags
2018-04-12T17:11:48+0000 ++ /opt/local/bin/git rev-parse HEAD
2018-04-12T17:11:48+0000 + RBASE_OLD_REV=68708e1c5e2a4f21afa95e733c5d34cd0f5c71de
2018-04-12T17:11:48+0000 ++ /usr/bin/basename https://github.com/macports/macports-base/tags/v2.4.3
2018-04-12T17:11:48+0000 + /opt/local/bin/git checkout -q v2.4.3
2018-04-12T17:11:48+0000 error: pathspec 'v2.4.3' did not match any file(s) known to git.


Reply | Threaded
Open this post in threaded view
|

MacPorts 2.4.3 has been released

Rainer Müller-4
On 2018-04-12 19:15, Ryan Schmidt wrote:

>
> On Apr 12, 2018, at 11:27, Rainer Müller wrote:
>
>> On 2018-04-12 17:42, Ryan Schmidt wrote:
>>> On Apr 12, 2018, at 03:50, Clemens Lang wrote:
>>>>
>>>> Can you remove the -q flag and/or retry running git fetch? That should give us
>>>> an idea what went wrong here.
>>>
>>> No change. No additional output is produced.
>>
>> The problem is that ${RBASE} is fetching from ${TBASE} on the local
>> filesystem,
>
> Ah! I didn't realize we were doing that.
>
>> but the former did not fetch any tags.
>>
>> Hopefully fixed with:
>> https://github.com/macports/macports-infrastructure/commit/db64051c6dce12135eeb8114c6f77f320d5097f8
>
> This doesn't appear to have helped.
>
> 2018-04-12T17:09:42+0000 + '[' '!' -d /Volumes/RAID/opt/local/var/rsync/macports ']'
> 2018-04-12T17:09:42+0000 + '[' -d /Volumes/RAID/var/tmp/mprsyncup/trunk/base/.git ']'
> 2018-04-12T17:09:42+0000 + /opt/local/bin/git -C /Volumes/RAID/var/tmp/mprsyncup/trunk/base pull -q
> 2018-04-12T17:09:44+0000 + /opt/local/bin/git -C /Volumes/RAID/var/tmp/mprsyncup/trunk/base fetch --tags
> 2018-04-12T17:09:44+0000 + /bin/mkdir -p /Volumes/RAID/opt/local/var/rsync/macports/trunk/base
> 2018-04-12T17:09:45+0000 + /opt/local/bin/rsync -q -aIC --delete /Volumes/RAID/var/tmp/mprsyncup/trunk/base/ /Volumes/RAID/opt/local/var/rsync/macports/trunk/base
> 2018-04-12T17:11:46+0000 + read -r RELEASE_URL
> 2018-04-12T17:11:46+0000 + '[' -z https://github.com/macports/macports-base/tags/v2.4.3 ']'
> 2018-04-12T17:11:46+0000 + RBASE_CHANGED=1
> 2018-04-12T17:11:46+0000 + '[' -d /Volumes/RAID/var/tmp/mprsyncup/release/base/.git ']'
> 2018-04-12T17:11:47+0000 + cd /Volumes/RAID/var/tmp/mprsyncup/release/base
> 2018-04-12T17:11:47+0000 + /opt/local/bin/git fetch --tags
> 2018-04-12T17:11:48+0000 ++ /opt/local/bin/git rev-parse HEAD
> 2018-04-12T17:11:48+0000 + RBASE_OLD_REV=68708e1c5e2a4f21afa95e733c5d34cd0f5c71de
> 2018-04-12T17:11:48+0000 ++ /usr/bin/basename https://github.com/macports/macports-base/tags/v2.4.3
> 2018-04-12T17:11:48+0000 + /opt/local/bin/git checkout -q v2.4.3
> 2018-04-12T17:11:48+0000 error: pathspec 'v2.4.3' did not match any file(s) known to git.

Please check:

Is the v2.4.3 tag in TBASE now?
$ git -C /Volumes/RAID/var/tmp/mprsyncup/trunk/base tag -l | grep v2.4.3
Expected: v2.4.3

Where is TBASE configured to sync from?
$ git -C /Volumes/RAID/var/tmp/mprsyncup/trunk/base config remote.origin.url
Expected: https://github.com/macports/macports-base.git

What is TBASE configured to sync?
$ git -C /Volumes/RAID/var/tmp/mprsyncup/trunk/base config remote.origin.fetch
Expected: +refs/heads/*:refs/remotes/origin/*


I tried to simulate this locally by deleting the v2.4.3 tag again,
but it works for me:


// start clean
$ rm -rf /var/tmp/macports/
# initialize repos
$ ./mprsyncup

// reset to the state of 2.4.2
$ git -C /var/tmp/macports/trunk/base/ tag -d v2.4.3
$ git -C /var/tmp/macports/release/base/ tag -d v2.4.3
$ git -C /var/tmp/macports/release/base/ reset --hard v2.4.2

// sync again
$ ./mprsyncup
...
+ '[' -d /var/tmp/macports/trunk/base/.git ']'
+ /opt/local/bin/git -C /var/tmp/macports/trunk/base pull -q
+ /opt/local/bin/git -C /var/tmp/macports/trunk/base fetch --tags
+ /bin/mkdir -p /var/tmp/rsync/macports/trunk/base
+ /opt/local/bin/rsync -q -aIC --delete /var/tmp/macports/trunk/base/
/var/tmp/rsync/macports/trunk/base
+ read -r RELEASE_URL
+ '[' -z https://github.com/macports/macports-base/tags/v2.4.3 ']'
+ RBASE_CHANGED=1
+ '[' -d /var/tmp/macports/release/base/.git ']'
+ cd /var/tmp/macports/release/base
+ /opt/local/bin/git fetch --tags
From /var/tmp/macports/trunk/base
 * [new tag]           v2.4.3     -> v2.4.3
++ /opt/local/bin/git rev-parse HEAD
+ RBASE_OLD_REV=68708e1c5e2a4f21afa95e733c5d34cd0f5c71de
++ /usr/bin/basename https://github.com/macports/macports-base/tags/v2.4.3
+ /opt/local/bin/git checkout -q v2.4.3
++ /opt/local/bin/git rev-parse HEAD
+ RBASE_NEW_REV=a393413460aae5ac9749b994681381087089cdb5
+ '[' 68708e1c5e2a4f21afa95e733c5d34cd0f5c71de =
a393413460aae5ac9749b994681381087089cdb5 ']'
+ /bin/mkdir -p /var/tmp/rsync/macports/release/base
+ /opt/local/bin/rsync -q -aIC --delete /var/tmp/macports/release/base/
/var/tmp/rsync/macports/release/base


Rainer
Reply | Threaded
Open this post in threaded view
|

Re: MacPorts 2.4.3 has been released

Ryan Schmidt-24
Thanks for the pointers! The problem was that release/base was configured to sync from the *old* location of trunk/base (from before I moved everything but the rsync data onto the SSD):

git -C /Volumes/RAID/var/tmp/mprsyncup/release/base config remote.origin.url
/var/tmp/mprsyncup/trunk/base

I changed it to the new location, /Volumes/RAID/var/tmp/mprsyncup/trunk/base, and it has finished running and the private rsync server has now updated properly. It should be on the public rsync server within 10 minutes.



On Apr 12, 2018, at 16:26, Joshua Root wrote:

> What does 'git tag --list' say in $RBASE and $TBASE?


On Apr 12, 2018, at 16:37, Rainer Müller wrote:

> Please check:
>
> Is the v2.4.3 tag in TBASE now?
> $ git -C /Volumes/RAID/var/tmp/mprsyncup/trunk/base tag -l | grep v2.4.3
> Expected: v2.4.3

Yes!


> Where is TBASE configured to sync from?
> $ git -C /Volumes/RAID/var/tmp/mprsyncup/trunk/base config remote.origin.url
> Expected: https://github.com/macports/macports-base.git

Yes: https://github.com/macports/macports-base.git


> What is TBASE configured to sync?
> $ git -C /Volumes/RAID/var/tmp/mprsyncup/trunk/base config remote.origin.fetch
> Expected: +refs/heads/*:refs/remotes/origin/*

Yes: +refs/heads/*:refs/remotes/origin/*



12