Re: MacPorts 2.8.0-beta1 now available for testing

[Chris Jones]

Hi Josh,

I've made some progress in understanding the cause of the hang ups I 
have been having. Its related to the use of a new feature in recent git 
versions


https://github.blog/2022-06-27-highlights-from-git-2-37/#a-builtin-filesystem-monitor-for-windows-and-macos

I enabled this feature a while back

> git config core.fsmonitor true

and forgot about it.

With macports 2.7.x I had no problems, but with 2.8.x I get the hangup 
immediately after the `git pull` step run by e.g. 'port -d sync'


If, during this hangup, I check the processes running I see this one

67138 s010  S+ 0:00.01 /opt/local/libexec/git-core/git 
fsmonitor--daemon run --detach --ipc-threads=8


and indeed if I manually kill that process the port sync command continues.

So... A simple reproducer for the issue is the following

1. Configure your macports installation to use a git clone of the ports 
tree in your personal user area, instead of the default tarball 
approach. In my case this is under /Users/chris/Projects/MacPorts/ports.


2. Install macports git

  > sudo port install git

3. Enable the fs monitor for the ports tree checkout you made in 1.

  > cd /Users/chris/Projects/MacPorts/ports
  > git config core.fsmonitor true

3. run 'port -d sync'

Hopefully then you should see the command hang up

Oberon ~/Projects/MacPorts/ports > sudo port -d sync
DEBUG: Copying /Users/chris/Library/Preferences/com.apple.dt.Xcode.plist 
to /opt/local/var/macports/home/Library/Preferences

--->  Updating the ports tree
Synchronizing local ports tree from 
file:///Users/chris/Projects/MacPorts/ports

DEBUG: euid/egid changed to: 501/20, env: HOME=/Users/chris
DEBUG: /opt/local/bin/git pull --rebase --autostash
DEBUG: system -W /Users/chris/Projects/MacPorts/ports: 
/opt/local/bin/git pull --rebase --autostash

Already up to date.


Of course, the simple work around is to just disable this git feature

> git config core.fsmonitor false

But I think we should figure out why its interacting badly with macports 
2.8.x ?


cheers Chris

On 20/10/2022 10:49 am, Christopher Jones wrote:

Hi,

I’m afraid I have no idea how to go about setting up a reproducer for this. It 
seems it randomly comes and goes, so perhaps is related to something else going 
on in the system (I am on macOS12 intel b.t.w.).

The best I can do is monitor it and see if I can spot any pattern as to when it 
happens or not. I am now on the official 2.8.0 release and still see it happen, 
so lets also see if any others start to see the same or not.

Chris


On 19 Oct 2022, at 2:07 am, Joshua Root  wrote:

I can't repro this. The VCS sync logic hasn't changed since the privilege 
dropping fix in April. The only thing I can think of that might have made a 
difference is the update to Tcl 8.6 and the associated update of all the 
try/catch blocks.

All that should be happening between running git and running portindex is the 
environment restore in VCSCleanup. You might have to do some more digging to 
figure out a repro recipe I'm afraid.

- Josh

On 2022-10-18 20:09 , Christopher Jones wrote:

Hi,
I’m not running the beta but the current master branch of base, but I guess its 
similar.
I’m noticing with the latest version  `sudo port sync` just hangs up after 
updating my local git clone. e.g.
Oberon ~/Projects/MacPorts/ports > sudo port -d sync
DEBUG: Copying /Users/chris/Library/Preferences/com.apple.dt.Xcode.plist to 
/opt/local/var/macports/home/Library/Preferences
--->  Updating the ports tree
Synchronizing local ports tree from file:///Users/chris/Projects/MacPorts/ports
DEBUG: euid/egid changed to: 501/20, env: HOME=/Users/chris 
SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.vx1uKV7YtR/Listeners
DEBUG: /opt/local/bin/git pull --rebase --autostash
DEBUG: system -W /Users/chris/Projects/MacPorts/ports: /opt/local/bin/git pull 
--rebase --autostash
Already up to date.
and thats it, it never gets any further and just hangs up there.
If I contrl-c the process I can get it to continue.
^CDEBUG: euid/egid restored to: 0/0, env restored
DEBUG: system: /opt/local/bin/portindex /Users/chris/Projects/MacPorts/ports
Creating port index in /Users/chris/Projects/MacPorts/ports
Total number of ports parsed:   0
Ports successfully parsed:  0
Ports failed:   0
Up-to-date ports skipped:   29934
any ideas what step its hanging up on ?
Chris

On 14 Oct 2022, at 12:57 am, Joshua Root  wrote:

Well, only one issue has been reported against the beta so far (the NULL 
cxx_stdlib error that Ken saw.) I guess I'll tag an RC soon.

- Josh

Re: MacPorts 2.8.0-beta1 now available for testing

[Chris Jones]

> On 20 Oct 2022, at 5:11 pm, Marius Schamschula  wrote:
> 
> 
> Chris,
> 
> Correct!
> 
> I don’t want to use —autostash, as it may clobber WIP files in my local tree 
> (per the git-pull man page).

My experience with the autostash option is it always works as advertised, so 
stashes your local changes, applies the update then reapplies the stash. Not 
using this option isn’t going to help you much if you do have conflicts with 
master, you are going to have to resolve them one way or anohter eventually, 
but not using it makes your life harder in the vast majority of cases where it 
works fine.

Just my 2pence worth, but I do not think you are doing yourself any favours 
avoiding it.

Chris

> 
> I ran
> 
> git branch --set-upstream-to=origin/master master
> 
> to get rid of the error.
> 
> However, I shouldn’t use port sync (or for that matter port selfupdate), 
> unless my local tree is clean.
> 
>> On Oct 20, 2022, at 10:37 AM, Chris Jones  wrote:
>> 
>> Hi
>> 
>> Go to your person checkout
>> 
>> /Users/marius/Development/MacPorts/ports
>> 
>> And then run
>> 
>> /opt/local/bin/git pull --rebase --autostash
>> 
>> You will I bet see the same issue, so the problem is nothing to do with 
>> macports but your local checkout.
>> 
>> Chris
>> 
>>> On 20 Oct 2022, at 3:22 pm, Marius Schamschula  
>>> wrote:
>>> 
>>> 
>>> Chris,
>>> 
>>> If I go to 
>>> 
>>> /opt/local/var/macports/sources/github.com/macports/macports-ports
>>> 
>>> and run
>>> 
>>> /opt/local/bin/git pull --rebase origin master
>>> 
>>> Which I do as part of a macro which also runs portindex on that directory, 
>>> everything works as expected.
>>> 
>>> The only part of port selfupdate that’s failing is the port sync:
>>> 
>>> marius@Mira macports-ports % sudo port -d sync  
>>> DEBUG: Copying /Users/marius/Library/Preferences/com.apple.dt.Xcode.plist 
>>> to /opt/local/var/macports/home/Library/Preferences
>>> --->  Updating the ports tree
>>> Synchronizing local ports tree from 
>>> file:///Users/marius/Development/MacPorts/ports
>>> DEBUG: euid/egid changed to: 501/20, env: HOME=/Users/marius 
>>> SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.084KBeK49L/Listeners
>>> DEBUG: /opt/local/bin/git pull --rebase --autostash
>>> DEBUG: system -W /Users/marius/Development/MacPorts/ports: 
>>> /opt/local/bin/git pull --rebase --autostash
>>> There is no tracking information for the current branch.
>>> Please specify which branch you want to rebase against.
>>> See git-pull(1) for details.
>>> 
>>> git pull  
>>> 
>>> If you wish to set tracking information for this branch you can do so with:
>>> 
>>> git branch --set-upstream-to=origin/ master
>>> 
>>> Command failed: /opt/local/bin/git pull --rebase --autostash
>>> Exit code: 1
>>> DEBUG: command execution failed
>>> while executing
>>> "system -W $dir $cmd"
>>> (procedure "macports::UpdateVCS" line 1)
>>> invoked from within
>>> "macports::UpdateVCS $cmd $dir"
>>> Syncing local Git ports tree failed
>>> DEBUG: euid/egid restored to: 0/0, env restored
>>> Synchronizing local ports tree from 
>>> file:///opt/local/var/macports/sources/github.com/macports/macports-ports/
>>> DEBUG: euid/egid changed to: 501/20, env: HOME=/Users/marius 
>>> SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.084KBeK49L/Listeners
>>> DEBUG: /opt/local/bin/git pull --rebase --autostash
>>> DEBUG: system -W 
>>> /opt/local/var/macports/sources/github.com/macports/macports-ports: 
>>> /opt/local/bin/git pull --rebase --autostash
>>> There is no tracking information for the current branch.
>>> Please specify which branch you want to rebase against.
>>> See git-pull(1) for details.
>>> 
>>> git pull  
>>> 
>>> If you wish to set tracking information for this branch you can do so with:
>>> 
>>> git branch --set-upstream-to=origin/ master
>>> 
>>> Command failed: /opt/local/bin/git pull --rebase --autostash
>>> Exit code: 1
>>> DEBUG: command execution failed
>>> while executing
>>> "system -W $dir $cmd"
>>> (procedure "macports::UpdateVCS" line 1)
>>> invoked from within
>>> "macports::UpdateVCS $cmd $dir"
>>> Syncing local Git ports tree failed
>>> DEBUG: euid/egid restored to: 0/0, env restored
>>> DEBUG: Synchronization of 2 sources failed
>>> while executing
>>> "mportsync [array get global_options]"
>>> port sync failed: Synchronization of 2 sources failed
>>> 
>>> Note: this error doesn’t happen under MacPorts 2.7.2, as I rechecked two of 
>>> my machines that haven’t been upgraded to MacPorts 2.8.0.
>>> 
 On Oct 20, 2022, at 8:31 AM, Christopher Jones  
 wrote:
 
 
 No, thats not what I am saying. What you are doing works just fine for me…
 
 My own checkout has
 
 Oberon ~/Projects/MacPorts/ports > git remote -v
 cjones g...@github.com:cjones051073/macports-ports.git (fetch)
 cjones g...@github.com:cjones051073/macports-ports.git (push)
 origin g...@github.com:macports/macports-ports.git (fetch)
 origin   

Re: MacPorts 2.8.0-beta1 now available for testing

[Marius Schamschula]

Chris,

Correct!

I don’t want to use —autostash, as it may clobber WIP files in my local tree 
(per the git-pull man page).

I ran

git branch --set-upstream-to=origin/master master

to get rid of the error.

However, I shouldn’t use port sync (or for that matter port selfupdate), unless 
my local tree is clean.

> On Oct 20, 2022, at 10:37 AM, Chris Jones  wrote:
> 
> Hi
> 
> Go to your person checkout
> 
> /Users/marius/Development/MacPorts/ports
> 
> And then run
> 
> /opt/local/bin/git pull --rebase --autostash
> 
> You will I bet see the same issue, so the problem is nothing to do with 
> macports but your local checkout.
> 
> Chris
> 
>> On 20 Oct 2022, at 3:22 pm, Marius Schamschula  wrote:
>> 
>> 
>> Chris,
>> 
>> If I go to 
>> 
>> /opt/local/var/macports/sources/github.com/macports/macports-ports 
>> 
>> 
>> and run
>> 
>> /opt/local/bin/git pull --rebase origin master
>> 
>> Which I do as part of a macro which also runs portindex on that directory, 
>> everything works as expected.
>> 
>> The only part of port selfupdate that’s failing is the port sync:
>> 
>> marius@Mira macports-ports % sudo port -d sync  
>> DEBUG: Copying /Users/marius/Library/Preferences/com.apple.dt.Xcode.plist to 
>> /opt/local/var/macports/home/Library/Preferences
>> --->  Updating the ports tree
>> Synchronizing local ports tree from 
>> file:///Users/marius/Development/MacPorts/ports 
>> 
>> DEBUG: euid/egid changed to: 501/20, env: HOME=/Users/marius 
>> SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.084KBeK49L/Listeners
>> DEBUG: /opt/local/bin/git pull --rebase --autostash
>> DEBUG: system -W /Users/marius/Development/MacPorts/ports: 
>> /opt/local/bin/git pull --rebase --autostash
>> There is no tracking information for the current branch.
>> Please specify which branch you want to rebase against.
>> See git-pull(1) for details.
>> 
>> git pull  
>> 
>> If you wish to set tracking information for this branch you can do so with:
>> 
>> git branch --set-upstream-to=origin/ master
>> 
>> Command failed: /opt/local/bin/git pull --rebase --autostash
>> Exit code: 1
>> DEBUG: command execution failed
>> while executing
>> "system -W $dir $cmd"
>> (procedure "macports::UpdateVCS" line 1)
>> invoked from within
>> "macports::UpdateVCS $cmd $dir"
>> Syncing local Git ports tree failed
>> DEBUG: euid/egid restored to: 0/0, env restored
>> Synchronizing local ports tree from 
>> file:///opt/local/var/macports/sources/github.com/macports/macports-ports/ 
>> 
>> DEBUG: euid/egid changed to: 501/20, env: HOME=/Users/marius 
>> SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.084KBeK49L/Listeners
>> DEBUG: /opt/local/bin/git pull --rebase --autostash
>> DEBUG: system -W 
>> /opt/local/var/macports/sources/github.com/macports/macports-ports: 
>>  /opt/local/bin/git pull 
>> --rebase --autostash
>> There is no tracking information for the current branch.
>> Please specify which branch you want to rebase against.
>> See git-pull(1) for details.
>> 
>> git pull  
>> 
>> If you wish to set tracking information for this branch you can do so with:
>> 
>> git branch --set-upstream-to=origin/ master
>> 
>> Command failed: /opt/local/bin/git pull --rebase --autostash
>> Exit code: 1
>> DEBUG: command execution failed
>> while executing
>> "system -W $dir $cmd"
>> (procedure "macports::UpdateVCS" line 1)
>> invoked from within
>> "macports::UpdateVCS $cmd $dir"
>> Syncing local Git ports tree failed
>> DEBUG: euid/egid restored to: 0/0, env restored
>> DEBUG: Synchronization of 2 sources failed
>> while executing
>> "mportsync [array get global_options]"
>> port sync failed: Synchronization of 2 sources failed
>> 
>> Note: this error doesn’t happen under MacPorts 2.7.2, as I rechecked two of 
>> my machines that haven’t been upgraded to MacPorts 2.8.0.
>> 
>>> On Oct 20, 2022, at 8:31 AM, Christopher Jones >> > wrote:
>>> 
>>> 
>>> No, thats not what I am saying. What you are doing works just fine for me…
>>> 
>>> My own checkout has
>>> 
>>> Oberon ~/Projects/MacPorts/ports > git remote -v
>>> cjones  g...@github.com 
>>> :cjones051073/macports-ports.git (fetch)
>>> cjones  g...@github.com 
>>> :cjones051073/macports-ports.git (push)
>>> origin  g...@github.com 
>>> :macports/macports-ports.git (fetch)
>>> origin  g...@github.com 
>>> :macports/macports-ports.git (push)
>>> 
>>> So I have set origin to be the main repo, and my own clone is the ‘clones’ 
>>> remote.
>>> 
>>> running port sync (or port selfupdate for that matter) works fine (at least 
>>> as far as the git pull part goes).
>>> 
>>> Oberon ~/Projects/MacPorts/ports > sudo port -d selfupdate
>>> DEBUG: Copying /Users/chris/Library/Preferences/com.apple.dt.Xcode.plist to 
>>> 

Re: MacPorts 2.8.0-beta1 now available for testing

[Chris Jones]

Hi

Go to your person checkout

/Users/marius/Development/MacPorts/ports

And then run

/opt/local/bin/git pull --rebase --autostash

You will I bet see the same issue, so the problem is nothing to do with 
macports but your local checkout.

Chris

> On 20 Oct 2022, at 3:22 pm, Marius Schamschula  wrote:
> 
> 
> Chris,
> 
> If I go to 
> 
> /opt/local/var/macports/sources/github.com/macports/macports-ports
> 
> and run
> 
> /opt/local/bin/git pull --rebase origin master
> 
> Which I do as part of a macro which also runs portindex on that directory, 
> everything works as expected.
> 
> The only part of port selfupdate that’s failing is the port sync:
> 
> marius@Mira macports-ports % sudo port -d sync  
> DEBUG: Copying /Users/marius/Library/Preferences/com.apple.dt.Xcode.plist to 
> /opt/local/var/macports/home/Library/Preferences
> --->  Updating the ports tree
> Synchronizing local ports tree from 
> file:///Users/marius/Development/MacPorts/ports
> DEBUG: euid/egid changed to: 501/20, env: HOME=/Users/marius 
> SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.084KBeK49L/Listeners
> DEBUG: /opt/local/bin/git pull --rebase --autostash
> DEBUG: system -W /Users/marius/Development/MacPorts/ports: /opt/local/bin/git 
> pull --rebase --autostash
> There is no tracking information for the current branch.
> Please specify which branch you want to rebase against.
> See git-pull(1) for details.
> 
> git pull  
> 
> If you wish to set tracking information for this branch you can do so with:
> 
> git branch --set-upstream-to=origin/ master
> 
> Command failed: /opt/local/bin/git pull --rebase --autostash
> Exit code: 1
> DEBUG: command execution failed
> while executing
> "system -W $dir $cmd"
> (procedure "macports::UpdateVCS" line 1)
> invoked from within
> "macports::UpdateVCS $cmd $dir"
> Syncing local Git ports tree failed
> DEBUG: euid/egid restored to: 0/0, env restored
> Synchronizing local ports tree from 
> file:///opt/local/var/macports/sources/github.com/macports/macports-ports/
> DEBUG: euid/egid changed to: 501/20, env: HOME=/Users/marius 
> SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.084KBeK49L/Listeners
> DEBUG: /opt/local/bin/git pull --rebase --autostash
> DEBUG: system -W 
> /opt/local/var/macports/sources/github.com/macports/macports-ports: 
> /opt/local/bin/git pull --rebase --autostash
> There is no tracking information for the current branch.
> Please specify which branch you want to rebase against.
> See git-pull(1) for details.
> 
> git pull  
> 
> If you wish to set tracking information for this branch you can do so with:
> 
> git branch --set-upstream-to=origin/ master
> 
> Command failed: /opt/local/bin/git pull --rebase --autostash
> Exit code: 1
> DEBUG: command execution failed
> while executing
> "system -W $dir $cmd"
> (procedure "macports::UpdateVCS" line 1)
> invoked from within
> "macports::UpdateVCS $cmd $dir"
> Syncing local Git ports tree failed
> DEBUG: euid/egid restored to: 0/0, env restored
> DEBUG: Synchronization of 2 sources failed
> while executing
> "mportsync [array get global_options]"
> port sync failed: Synchronization of 2 sources failed
> 
> Note: this error doesn’t happen under MacPorts 2.7.2, as I rechecked two of 
> my machines that haven’t been upgraded to MacPorts 2.8.0.
> 
>> On Oct 20, 2022, at 8:31 AM, Christopher Jones  
>> wrote:
>> 
>> 
>> No, thats not what I am saying. What you are doing works just fine for me…
>> 
>> My own checkout has
>> 
>> Oberon ~/Projects/MacPorts/ports > git remote -v
>> cjones   g...@github.com:cjones051073/macports-ports.git (fetch)
>> cjones   g...@github.com:cjones051073/macports-ports.git (push)
>> origin   g...@github.com:macports/macports-ports.git (fetch)
>> origin   g...@github.com:macports/macports-ports.git (push)
>> 
>> So I have set origin to be the main repo, and my own clone is the ‘clones’ 
>> remote.
>> 
>> running port sync (or port selfupdate for that matter) works fine (at least 
>> as far as the git pull part goes).
>> 
>> Oberon ~/Projects/MacPorts/ports > sudo port -d selfupdate
>> DEBUG: Copying /Users/chris/Library/Preferences/com.apple.dt.Xcode.plist to 
>> /opt/local/var/macports/home/Library/Preferences
>> DEBUG: MacPorts sources location: 
>> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs
>> --->  Updating MacPorts base sources using rsync
>> DEBUG: system: /usr/bin/rsync -rtzvl --delete-after --include=/base.tar 
>> --include=/base.tar.rmd160 --exclude=* 
>> rsync://rsync.macports.org/macports/release/tarballs/ 
>> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs
>> 
>> Willkommen auf dem RSYNC-server auf ftp.fau.de.
>> Nicht all unsere Mirror sind per rsync verfuegbar.
>> 
>> Welcome to the RSYNC daemon on ftp.fau.de.
>> Not all of our mirrors are available through rsync.
>> 
>> 
>> receiving file list ... done
>> ./
>> 
>> sent 66 bytes  received 98 bytes  109.33 bytes/sec

Re: MacPorts 2.8.0-beta1 now available for testing

[Marius Schamschula]

Chris,

If I go to 

/opt/local/var/macports/sources/github.com/macports/macports-ports 


and run

/opt/local/bin/git pull --rebase origin master

Which I do as part of a macro which also runs portindex on that directory, 
everything works as expected.

The only part of port selfupdate that’s failing is the port sync:

marius@Mira macports-ports % sudo port -d sync  
DEBUG: Copying /Users/marius/Library/Preferences/com.apple.dt.Xcode.plist to 
/opt/local/var/macports/home/Library/Preferences
--->  Updating the ports tree
Synchronizing local ports tree from 
file:///Users/marius/Development/MacPorts/ports
DEBUG: euid/egid changed to: 501/20, env: HOME=/Users/marius 
SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.084KBeK49L/Listeners
DEBUG: /opt/local/bin/git pull --rebase --autostash
DEBUG: system -W /Users/marius/Development/MacPorts/ports: /opt/local/bin/git 
pull --rebase --autostash
There is no tracking information for the current branch.
Please specify which branch you want to rebase against.
See git-pull(1) for details.

git pull  

If you wish to set tracking information for this branch you can do so with:

git branch --set-upstream-to=origin/ master

Command failed: /opt/local/bin/git pull --rebase --autostash
Exit code: 1
DEBUG: command execution failed
while executing
"system -W $dir $cmd"
(procedure "macports::UpdateVCS" line 1)
invoked from within
"macports::UpdateVCS $cmd $dir"
Syncing local Git ports tree failed
DEBUG: euid/egid restored to: 0/0, env restored
Synchronizing local ports tree from 
file:///opt/local/var/macports/sources/github.com/macports/macports-ports/
DEBUG: euid/egid changed to: 501/20, env: HOME=/Users/marius 
SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.084KBeK49L/Listeners
DEBUG: /opt/local/bin/git pull --rebase --autostash
DEBUG: system -W 
/opt/local/var/macports/sources/github.com/macports/macports-ports: 
/opt/local/bin/git pull --rebase --autostash
There is no tracking information for the current branch.
Please specify which branch you want to rebase against.
See git-pull(1) for details.

git pull  

If you wish to set tracking information for this branch you can do so with:

git branch --set-upstream-to=origin/ master

Command failed: /opt/local/bin/git pull --rebase --autostash
Exit code: 1
DEBUG: command execution failed
while executing
"system -W $dir $cmd"
(procedure "macports::UpdateVCS" line 1)
invoked from within
"macports::UpdateVCS $cmd $dir"
Syncing local Git ports tree failed
DEBUG: euid/egid restored to: 0/0, env restored
DEBUG: Synchronization of 2 sources failed
while executing
"mportsync [array get global_options]"
port sync failed: Synchronization of 2 sources failed

Note: this error doesn’t happen under MacPorts 2.7.2, as I rechecked two of my 
machines that haven’t been upgraded to MacPorts 2.8.0.

> On Oct 20, 2022, at 8:31 AM, Christopher Jones  
> wrote:
> 
> 
> No, thats not what I am saying. What you are doing works just fine for me…
> 
> My own checkout has
> 
> Oberon ~/Projects/MacPorts/ports > git remote -v
> cjonesg...@github.com 
> :cjones051073/macports-ports.git (fetch)
> cjonesg...@github.com 
> :cjones051073/macports-ports.git (push)
> origing...@github.com 
> :macports/macports-ports.git (fetch)
> origing...@github.com 
> :macports/macports-ports.git (push)
> 
> So I have set origin to be the main repo, and my own clone is the ‘clones’ 
> remote.
> 
> running port sync (or port selfupdate for that matter) works fine (at least 
> as far as the git pull part goes).
> 
> Oberon ~/Projects/MacPorts/ports > sudo port -d selfupdate
> DEBUG: Copying /Users/chris/Library/Preferences/com.apple.dt.Xcode.plist to 
> /opt/local/var/macports/home/Library/Preferences
> DEBUG: MacPorts sources location: 
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs 
> 
> --->  Updating MacPorts base sources using rsync
> DEBUG: system: /usr/bin/rsync -rtzvl --delete-after --include=/base.tar 
> --include=/base.tar.rmd160 --exclude=* 
> rsync://rsync.macports.org/macports/release/tarballs/ 
>  
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs 
> 
> 
> Willkommen auf dem RSYNC-server auf ftp.fau.de .
> Nicht all unsere Mirror sind per rsync verfuegbar.
> 
> Welcome to the RSYNC daemon on ftp.fau.de .
> Not all of our mirrors are available through rsync.
> 
> 
> receiving file list ... done
> ./
> 
> sent 66 bytes  received 98 bytes  109.33 bytes/sec
> total size is 113716736  speedup is 693394.73
> DEBUG: successful verification with key 
> /opt/local/share/macports/macports-pubkey.pem
> DEBUG: system: /usr/bin/tar -C 
> 

Re: MacPorts 2.8.0-beta1 now available for testing

[Christopher Jones]

No, thats not what I am saying. What you are doing works just fine for me…

My own checkout has

Oberon ~/Projects/MacPorts/ports > git remote -v
cjones  g...@github.com:cjones051073/macports-ports.git (fetch)
cjones  g...@github.com:cjones051073/macports-ports.git (push)
origin  g...@github.com:macports/macports-ports.git (fetch)
origin  g...@github.com:macports/macports-ports.git (push)

So I have set origin to be the main repo, and my own clone is the ‘clones’ 
remote.

running port sync (or port selfupdate for that matter) works fine (at least as 
far as the git pull part goes).

Oberon ~/Projects/MacPorts/ports > sudo port -d selfupdate
DEBUG: Copying /Users/chris/Library/Preferences/com.apple.dt.Xcode.plist to 
/opt/local/var/macports/home/Library/Preferences
DEBUG: MacPorts sources location: 
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs
--->  Updating MacPorts base sources using rsync
DEBUG: system: /usr/bin/rsync -rtzvl --delete-after --include=/base.tar 
--include=/base.tar.rmd160 --exclude=* 
rsync://rsync.macports.org/macports/release/tarballs/ 
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs

Willkommen auf dem RSYNC-server auf ftp.fau.de.
Nicht all unsere Mirror sind per rsync verfuegbar.

Welcome to the RSYNC daemon on ftp.fau.de.
Not all of our mirrors are available through rsync.


receiving file list ... done
./

sent 66 bytes  received 98 bytes  109.33 bytes/sec
total size is 113716736  speedup is 693394.73
DEBUG: successful verification with key 
/opt/local/share/macports/macports-pubkey.pem
DEBUG: system: /usr/bin/tar -C 
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/tmp
 -xf 
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base.tar
MacPorts base version 2.8.0 installed,
DEBUG: Rebuilding and reinstalling MacPorts if needed
MacPorts base version 2.8.0 downloaded.
--->  Updating the ports tree
Synchronizing local ports tree from file:///Users/chris/Projects/MacPorts/ports
DEBUG: euid/egid changed to: 501/20, env: HOME=/Users/chris 
SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.3Ry328lG9D/Listeners
DEBUG: /opt/local/bin/git pull --rebase --autostash
DEBUG: system -W /Users/chris/Projects/MacPorts/ports: /opt/local/bin/git pull 
--rebase --autostash
Already up to date.

So the git pull works just fine. ( It hangs after this but thats a different 
issue. )

Why you are having problems I cannot say, but you should start by checking how 
you have the remotes setup for your checkout.

Chris

> On 20 Oct 2022, at 1:52 pm, Marius Schamschula  wrote:
> 
> Chris,
> 
> In other words, I shouldn’t ever run port selfupdate in my local repo (which 
> syncs to my personal GitHub repo), but rather in the 
> 
> /opt/local/var/macports/sources/github.com/macports/macports-ports 
> 
> 
> directory. Make sense, but the update has always worked in the past.
> 
>> On Oct 20, 2022, at 7:26 AM, Christopher Jones > > wrote:
>> 
>> The message
>> 
>> There is no tracking information for the current branch.
>> Please specify which branch you want to rebase against.
>> See git-pull(1) for details.
>> 
>> git pull  
>> 
>> If you wish to set tracking information for this branch you can do so with:
>> 
>> git branch --set-upstream-to=origin/ master
>> 
>> Indicates you have 
>> 
>> /Users/marius/Development/MacPorts/ports 
>> 
>> 
>> switched to a branch that does not have its tracking information set. This 
>> normally happens if you have a feature branch (e.g. for a PR) checked out, 
>> but the above is for master which is a bit weird.
>> 
>> running
>> 
>> git branch --set-upstream-to=origin/master master
>> 
>> might fix this, but again, it is a bit odd you need to do this for your 
>> master checkout, unless you have done something ‘odd’ to it such that it has 
>> lost its tracking info.
>> 
>> Chris
>> 
>>> On 20 Oct 2022, at 12:17 pm, Marius Schamschula >> > wrote:
>>> 
>>> I’m seeing something very similar with MacPorts 2.8.0 (release)
>>> 
>>> marius@Mira ports % sudo port selfupdate 
>>> --->  Updating MacPorts base sources using rsync
>>> MacPorts base version 2.7.2 installed,
>>> MacPorts base version 2.8.0 downloaded.
>>> --->  Updating the ports tree
>>> --->  MacPorts base is outdated, installing new version 2.8.0
>>> Installing new MacPorts release in /opt/local as root:wheel; permissions 
>>> 0755
>>> 
>>> Error: Couldn't change permissions of the MacPorts sources at 
>>> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base
>>>   to root: child 
>>> killed: kill signal
>>> Please run `port -v selfupdate' for details.
>>> Error: /opt/local/bin/port: port selfupdate failed: Couldn't change 
>>> permissions of the MacPorts sources at 
>>> 

Re: MacPorts 2.8.0-beta1 now available for testing

[Marius Schamschula]

Chris,

In other words, I shouldn’t ever run port selfupdate in my local repo (which 
syncs to my personal GitHub repo), but rather in the 

/opt/local/var/macports/sources/github.com/macports/macports-ports 


directory. Make sense, but the update has always worked in the past.

> On Oct 20, 2022, at 7:26 AM, Christopher Jones  
> wrote:
> 
> The message
> 
> There is no tracking information for the current branch.
> Please specify which branch you want to rebase against.
> See git-pull(1) for details.
> 
> git pull  
> 
> If you wish to set tracking information for this branch you can do so with:
> 
> git branch --set-upstream-to=origin/ master
> 
> Indicates you have 
> 
> /Users/marius/Development/MacPorts/ports 
> 
> 
> switched to a branch that does not have its tracking information set. This 
> normally happens if you have a feature branch (e.g. for a PR) checked out, 
> but the above is for master which is a bit weird.
> 
> running
> 
> git branch --set-upstream-to=origin/master master
> 
> might fix this, but again, it is a bit odd you need to do this for your 
> master checkout, unless you have done something ‘odd’ to it such that it has 
> lost its tracking info.
> 
> Chris
> 
>> On 20 Oct 2022, at 12:17 pm, Marius Schamschula > > wrote:
>> 
>> I’m seeing something very similar with MacPorts 2.8.0 (release)
>> 
>> marius@Mira ports % sudo port selfupdate 
>> --->  Updating MacPorts base sources using rsync
>> MacPorts base version 2.7.2 installed,
>> MacPorts base version 2.8.0 downloaded.
>> --->  Updating the ports tree
>> --->  MacPorts base is outdated, installing new version 2.8.0
>> Installing new MacPorts release in /opt/local as root:wheel; permissions 0755
>> 
>> Error: Couldn't change permissions of the MacPorts sources at 
>> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base
>>   to root: child 
>> killed: kill signal
>> Please run `port -v selfupdate' for details.
>> Error: /opt/local/bin/port: port selfupdate failed: Couldn't change 
>> permissions of the MacPorts sources at 
>> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base
>>   to root: child 
>> killed: kill signal
>> marius@Mira ports % sudo port -v selfupdate
>> --->  Updating MacPorts base sources using rsync
>> 
>> Willkommen auf dem RSYNC-server auf ftp.fau.de .
>> Nicht all unsere Mirror sind per rsync verfuegbar.
>> 
>> Welcome to the RSYNC daemon on ftp.fau.de .
>> Not all of our mirrors are available through rsync.
>> 
>> 
>> receiving file list ... done
>> ./
>> 
>> sent 66 bytes  received 98 bytes  109.33 bytes/sec
>> total size is 113716736  speedup is 693394.73
>> MacPorts base version 2.8.0 installed,
>> MacPorts base version 2.8.0 downloaded.
>> --->  Updating the ports tree
>> Synchronizing local ports tree from 
>> file:///Users/marius/Development/MacPorts/ports 
>> 
>> There is no tracking information for the current branch.
>> Please specify which branch you want to rebase against.
>> See git-pull(1) for details.
>> 
>> git pull  
>> 
>> If you wish to set tracking information for this branch you can do so with:
>> 
>> git branch --set-upstream-to=origin/ master
>> 
>> Command failed: /opt/local/bin/git pull --rebase --autostash
>> Exit code: 1
>> Syncing local Git ports tree failed
>> Synchronizing local ports tree from 
>> file:///opt/local/var/macports/sources/github.com/macports/macports-ports/ 
>> 
>> From github.com :macports/macports-ports
>>  * [new tag] PRE_DESTROOT_TARGET-> 
>> PRE_DESTROOT_TARGET
>>  * [new tag] jkh-destrootification-base -> 
>> jkh-destrootification-base
>>  * [new tag] kevin-target-api-base  -> 
>> kevin-target-api-base
>>  * [new tag] post-landon-trace  -> post-landon-trace
>>  * [new tag] pre-chain-remove   -> pre-chain-remove
>>  * [new tag] pre-landon-trace   -> pre-landon-trace
>>  * [new tag] release_1_2_0-archive  -> 
>> release_1_2_0-archive
>>  * [new tag] release_1_2_0-archive-rc1  -> 
>> release_1_2_0-archive-rc1
>>  * [new tag] release_1_2_0-rc2-archive  -> 
>> release_1_2_0-rc2-archive
>>  * [new tag] release_1_2_0-rc3-archive  -> 
>> release_1_2_0-rc3-archive
>>  * [new tag] release_1_2_1-archive  -> 
>> release_1_2_1-archive
>>  * [new tag] release_1_2_1-rc1-archive  -> 
>> release_1_2_1-rc1-archive
>>  * [new tag] release_1_3_0-archive  -> 
>> release_1_3_0-archive
>>  * [new tag] release_1_3_1-archive  -> 
>> release_1_3_1-archive
>>  * [new tag] 

Re: MacPorts 2.8.0-beta1 now available for testing

[Christopher Jones]

The message

There is no tracking information for the current branch.
Please specify which branch you want to rebase against.
See git-pull(1) for details.

git pull  

If you wish to set tracking information for this branch you can do so with:

git branch --set-upstream-to=origin/ master

Indicates you have 

/Users/marius/Development/MacPorts/ports 


switched to a branch that does not have its tracking information set. This 
normally happens if you have a feature branch (e.g. for a PR) checked out, but 
the above is for master which is a bit weird.

running

git branch --set-upstream-to=origin/master master

might fix this, but again, it is a bit odd you need to do this for your master 
checkout, unless you have done something ‘odd’ to it such that it has lost its 
tracking info.

Chris

> On 20 Oct 2022, at 12:17 pm, Marius Schamschula  wrote:
> 
> I’m seeing something very similar with MacPorts 2.8.0 (release)
> 
> marius@Mira ports % sudo port selfupdate 
> --->  Updating MacPorts base sources using rsync
> MacPorts base version 2.7.2 installed,
> MacPorts base version 2.8.0 downloaded.
> --->  Updating the ports tree
> --->  MacPorts base is outdated, installing new version 2.8.0
> Installing new MacPorts release in /opt/local as root:wheel; permissions 0755
> 
> Error: Couldn't change permissions of the MacPorts sources at 
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base
>   to root: child 
> killed: kill signal
> Please run `port -v selfupdate' for details.
> Error: /opt/local/bin/port: port selfupdate failed: Couldn't change 
> permissions of the MacPorts sources at 
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base
>   to root: child 
> killed: kill signal
> marius@Mira ports % sudo port -v selfupdate
> --->  Updating MacPorts base sources using rsync
> 
> Willkommen auf dem RSYNC-server auf ftp.fau.de .
> Nicht all unsere Mirror sind per rsync verfuegbar.
> 
> Welcome to the RSYNC daemon on ftp.fau.de .
> Not all of our mirrors are available through rsync.
> 
> 
> receiving file list ... done
> ./
> 
> sent 66 bytes  received 98 bytes  109.33 bytes/sec
> total size is 113716736  speedup is 693394.73
> MacPorts base version 2.8.0 installed,
> MacPorts base version 2.8.0 downloaded.
> --->  Updating the ports tree
> Synchronizing local ports tree from 
> file:///Users/marius/Development/MacPorts/ports 
> 
> There is no tracking information for the current branch.
> Please specify which branch you want to rebase against.
> See git-pull(1) for details.
> 
> git pull  
> 
> If you wish to set tracking information for this branch you can do so with:
> 
> git branch --set-upstream-to=origin/ master
> 
> Command failed: /opt/local/bin/git pull --rebase --autostash
> Exit code: 1
> Syncing local Git ports tree failed
> Synchronizing local ports tree from 
> file:///opt/local/var/macports/sources/github.com/macports/macports-ports/ 
> 
> From github.com :macports/macports-ports
>  * [new tag] PRE_DESTROOT_TARGET-> PRE_DESTROOT_TARGET
>  * [new tag] jkh-destrootification-base -> 
> jkh-destrootification-base
>  * [new tag] kevin-target-api-base  -> 
> kevin-target-api-base
>  * [new tag] post-landon-trace  -> post-landon-trace
>  * [new tag] pre-chain-remove   -> pre-chain-remove
>  * [new tag] pre-landon-trace   -> pre-landon-trace
>  * [new tag] release_1_2_0-archive  -> 
> release_1_2_0-archive
>  * [new tag] release_1_2_0-archive-rc1  -> 
> release_1_2_0-archive-rc1
>  * [new tag] release_1_2_0-rc2-archive  -> 
> release_1_2_0-rc2-archive
>  * [new tag] release_1_2_0-rc3-archive  -> 
> release_1_2_0-rc3-archive
>  * [new tag] release_1_2_1-archive  -> 
> release_1_2_1-archive
>  * [new tag] release_1_2_1-rc1-archive  -> 
> release_1_2_1-rc1-archive
>  * [new tag] release_1_3_0-archive  -> 
> release_1_3_0-archive
>  * [new tag] release_1_3_1-archive  -> 
> release_1_3_1-archive
>  * [new tag] release_1_3_2-archive  -> 
> release_1_3_2-archive
>  * [new tag] release_1_4_0-archive  -> 
> release_1_4_0-archive
>  * [new tag] release_1_5_0-archive  -> 
> release_1_5_0-archive
>  * [new tag] release_1_6_0-archive  -> 
> release_1_6_0-archive
>  * [new tag] release_1_7_0-archive  -> 
> release_1_7_0-archive
>  * [new tag] release_1_8_0-archive  -> 
> release_1_8_0-archive
>  * [new tag] release_1_9_0-archive  -> 
> release_1_9_0-archive
>  * 

Re: MacPorts 2.8.0-beta1 now available for testing

[Christopher Jones]

Hi,

On the face of it that does not look the same to me.

What  happens if you run

> sudo port -d sync

For me, it hangs up after running the git pull to update my git checkout of the 
ports tree, but before running portindex.

Oberon ~/Projects/MacPorts/ports > sudo port -d sync
DEBUG: Copying /Users/chris/Library/Preferences/com.apple.dt.Xcode.plist to 
/opt/local/var/macports/home/Library/Preferences
--->  Updating the ports tree
Synchronizing local ports tree from file:///Users/chris/Projects/MacPorts/ports
DEBUG: euid/egid changed to: 501/20, env: HOME=/Users/chris 
SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.3Ry328lG9D/Listeners
DEBUG: /opt/local/bin/git pull --rebase --autostash
DEBUG: system -W /Users/chris/Projects/MacPorts/ports: /opt/local/bin/git pull 
--rebase --autostash
From github.com:macports/macports-ports
   19aaa181d68..0c36130193e  master -> origin/master
Updating 19aaa181d68..0c36130193e
Fast-forward
 python/hatch/Portfile |  8 
 www/nginx/Portfile| 10 +-
 2 files changed, 9 insertions(+), 9 deletions(-)


Chris


> On 20 Oct 2022, at 12:17 pm, Marius Schamschula  wrote:
> 
> I’m seeing something very similar with MacPorts 2.8.0 (release)
> 
> marius@Mira ports % sudo port selfupdate 
> --->  Updating MacPorts base sources using rsync
> MacPorts base version 2.7.2 installed,
> MacPorts base version 2.8.0 downloaded.
> --->  Updating the ports tree
> --->  MacPorts base is outdated, installing new version 2.8.0
> Installing new MacPorts release in /opt/local as root:wheel; permissions 0755
> 
> Error: Couldn't change permissions of the MacPorts sources at 
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base
>   to root: child 
> killed: kill signal
> Please run `port -v selfupdate' for details.
> Error: /opt/local/bin/port: port selfupdate failed: Couldn't change 
> permissions of the MacPorts sources at 
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base
>   to root: child 
> killed: kill signal
> marius@Mira ports % sudo port -v selfupdate
> --->  Updating MacPorts base sources using rsync
> 
> Willkommen auf dem RSYNC-server auf ftp.fau.de .
> Nicht all unsere Mirror sind per rsync verfuegbar.
> 
> Welcome to the RSYNC daemon on ftp.fau.de .
> Not all of our mirrors are available through rsync.
> 
> 
> receiving file list ... done
> ./
> 
> sent 66 bytes  received 98 bytes  109.33 bytes/sec
> total size is 113716736  speedup is 693394.73
> MacPorts base version 2.8.0 installed,
> MacPorts base version 2.8.0 downloaded.
> --->  Updating the ports tree
> Synchronizing local ports tree from 
> file:///Users/marius/Development/MacPorts/ports 
> 
> There is no tracking information for the current branch.
> Please specify which branch you want to rebase against.
> See git-pull(1) for details.
> 
> git pull  
> 
> If you wish to set tracking information for this branch you can do so with:
> 
> git branch --set-upstream-to=origin/ master
> 
> Command failed: /opt/local/bin/git pull --rebase --autostash
> Exit code: 1
> Syncing local Git ports tree failed
> Synchronizing local ports tree from 
> file:///opt/local/var/macports/sources/github.com/macports/macports-ports/ 
> 
> From github.com :macports/macports-ports
>  * [new tag] PRE_DESTROOT_TARGET-> PRE_DESTROOT_TARGET
>  * [new tag] jkh-destrootification-base -> 
> jkh-destrootification-base
>  * [new tag] kevin-target-api-base  -> 
> kevin-target-api-base
>  * [new tag] post-landon-trace  -> post-landon-trace
>  * [new tag] pre-chain-remove   -> pre-chain-remove
>  * [new tag] pre-landon-trace   -> pre-landon-trace
>  * [new tag] release_1_2_0-archive  -> 
> release_1_2_0-archive
>  * [new tag] release_1_2_0-archive-rc1  -> 
> release_1_2_0-archive-rc1
>  * [new tag] release_1_2_0-rc2-archive  -> 
> release_1_2_0-rc2-archive
>  * [new tag] release_1_2_0-rc3-archive  -> 
> release_1_2_0-rc3-archive
>  * [new tag] release_1_2_1-archive  -> 
> release_1_2_1-archive
>  * [new tag] release_1_2_1-rc1-archive  -> 
> release_1_2_1-rc1-archive
>  * [new tag] release_1_3_0-archive  -> 
> release_1_3_0-archive
>  * [new tag] release_1_3_1-archive  -> 
> release_1_3_1-archive
>  * [new tag] release_1_3_2-archive  -> 
> release_1_3_2-archive
>  * [new tag] release_1_4_0-archive  -> 
> release_1_4_0-archive
>  * [new tag] release_1_5_0-archive  -> 
> release_1_5_0-archive
>  * [new tag] release_1_6_0-archive  -> 
> 

Re: MacPorts 2.8.0-beta1 now available for testing

[Marius Schamschula]

I’m seeing something very similar with MacPorts 2.8.0 (release)

marius@Mira ports % sudo port selfupdate 
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.7.2 installed,
MacPorts base version 2.8.0 downloaded.
--->  Updating the ports tree
--->  MacPorts base is outdated, installing new version 2.8.0
Installing new MacPorts release in /opt/local as root:wheel; permissions 0755

Error: Couldn't change permissions of the MacPorts sources at 
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base
  to root: child 
killed: kill signal
Please run `port -v selfupdate' for details.
Error: /opt/local/bin/port: port selfupdate failed: Couldn't change permissions 
of the MacPorts sources at 
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base
  to root: child 
killed: kill signal
marius@Mira ports % sudo port -v selfupdate
--->  Updating MacPorts base sources using rsync

Willkommen auf dem RSYNC-server auf ftp.fau.de .
Nicht all unsere Mirror sind per rsync verfuegbar.

Welcome to the RSYNC daemon on ftp.fau.de .
Not all of our mirrors are available through rsync.


receiving file list ... done
./

sent 66 bytes  received 98 bytes  109.33 bytes/sec
total size is 113716736  speedup is 693394.73
MacPorts base version 2.8.0 installed,
MacPorts base version 2.8.0 downloaded.
--->  Updating the ports tree
Synchronizing local ports tree from 
file:///Users/marius/Development/MacPorts/ports 

There is no tracking information for the current branch.
Please specify which branch you want to rebase against.
See git-pull(1) for details.

git pull  

If you wish to set tracking information for this branch you can do so with:

git branch --set-upstream-to=origin/ master

Command failed: /opt/local/bin/git pull --rebase --autostash
Exit code: 1
Syncing local Git ports tree failed
Synchronizing local ports tree from 
file:///opt/local/var/macports/sources/github.com/macports/macports-ports/ 

From github.com :macports/macports-ports
 * [new tag] PRE_DESTROOT_TARGET-> PRE_DESTROOT_TARGET
 * [new tag] jkh-destrootification-base -> 
jkh-destrootification-base
 * [new tag] kevin-target-api-base  -> kevin-target-api-base
 * [new tag] post-landon-trace  -> post-landon-trace
 * [new tag] pre-chain-remove   -> pre-chain-remove
 * [new tag] pre-landon-trace   -> pre-landon-trace
 * [new tag] release_1_2_0-archive  -> release_1_2_0-archive
 * [new tag] release_1_2_0-archive-rc1  -> 
release_1_2_0-archive-rc1
 * [new tag] release_1_2_0-rc2-archive  -> 
release_1_2_0-rc2-archive
 * [new tag] release_1_2_0-rc3-archive  -> 
release_1_2_0-rc3-archive
 * [new tag] release_1_2_1-archive  -> release_1_2_1-archive
 * [new tag] release_1_2_1-rc1-archive  -> 
release_1_2_1-rc1-archive
 * [new tag] release_1_3_0-archive  -> release_1_3_0-archive
 * [new tag] release_1_3_1-archive  -> release_1_3_1-archive
 * [new tag] release_1_3_2-archive  -> release_1_3_2-archive
 * [new tag] release_1_4_0-archive  -> release_1_4_0-archive
 * [new tag] release_1_5_0-archive  -> release_1_5_0-archive
 * [new tag] release_1_6_0-archive  -> release_1_6_0-archive
 * [new tag] release_1_7_0-archive  -> release_1_7_0-archive
 * [new tag] release_1_8_0-archive  -> release_1_8_0-archive
 * [new tag] release_1_9_0-archive  -> release_1_9_0-archive
 * [new tag] release_2_0_0-archive  -> release_2_0_0-archive
 * [new tag] release_2_1_0-archive  -> release_2_1_0-archive
 * [new tag] release_2_2_0-archive  -> release_2_2_0-archive
 * [new tag] release_2_3_0-archive  -> release_2_3_0-archive
 * [new tag] v2.4.0-archive -> v2.4.0-archive
 * [new tag] v2.5.0-archive -> v2.5.0-archive
 * [new tag] v2.6.0-archive -> v2.6.0-archive
 * [new tag] v2.7.0-archive -> v2.7.0-archive
 * [new tag] v2.8.0-archive -> v2.8.0-archive
There is no tracking information for the current branch.
Please specify which branch you want to rebase against.
See git-pull(1) for details.

git pull  

If you wish to set tracking information for this branch you can do so with:

git branch --set-upstream-to=origin/ master

Command failed: /opt/local/bin/git pull --rebase --autostash
Exit code: 1
Syncing local Git ports 

Re: MacPorts 2.8.0-beta1 now available for testing

[Christopher Jones]

Hi,

I’m afraid I have no idea how to go about setting up a reproducer for this. It 
seems it randomly comes and goes, so perhaps is related to something else going 
on in the system (I am on macOS12 intel b.t.w.).

The best I can do is monitor it and see if I can spot any pattern as to when it 
happens or not. I am now on the official 2.8.0 release and still see it happen, 
so lets also see if any others start to see the same or not.

Chris

> On 19 Oct 2022, at 2:07 am, Joshua Root  wrote:
> 
> I can't repro this. The VCS sync logic hasn't changed since the privilege 
> dropping fix in April. The only thing I can think of that might have made a 
> difference is the update to Tcl 8.6 and the associated update of all the 
> try/catch blocks.
> 
> All that should be happening between running git and running portindex is the 
> environment restore in VCSCleanup. You might have to do some more digging to 
> figure out a repro recipe I'm afraid.
> 
> - Josh
> 
> On 2022-10-18 20:09 , Christopher Jones wrote:
>> Hi,
>> I’m not running the beta but the current master branch of base, but I guess 
>> its similar.
>> I’m noticing with the latest version  `sudo port sync` just hangs up after 
>> updating my local git clone. e.g.
>> Oberon ~/Projects/MacPorts/ports > sudo port -d sync
>> DEBUG: Copying /Users/chris/Library/Preferences/com.apple.dt.Xcode.plist to 
>> /opt/local/var/macports/home/Library/Preferences
>> --->  Updating the ports tree
>> Synchronizing local ports tree from 
>> file:///Users/chris/Projects/MacPorts/ports
>> DEBUG: euid/egid changed to: 501/20, env: HOME=/Users/chris 
>> SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.vx1uKV7YtR/Listeners
>> DEBUG: /opt/local/bin/git pull --rebase --autostash
>> DEBUG: system -W /Users/chris/Projects/MacPorts/ports: /opt/local/bin/git 
>> pull --rebase --autostash
>> Already up to date.
>> and thats it, it never gets any further and just hangs up there.
>> If I contrl-c the process I can get it to continue.
>> ^CDEBUG: euid/egid restored to: 0/0, env restored
>> DEBUG: system: /opt/local/bin/portindex /Users/chris/Projects/MacPorts/ports
>> Creating port index in /Users/chris/Projects/MacPorts/ports
>> Total number of ports parsed:0
>> Ports successfully parsed:   0
>> Ports failed:0
>> Up-to-date ports skipped:29934
>> any ideas what step its hanging up on ?
>> Chris
>>> On 14 Oct 2022, at 12:57 am, Joshua Root  wrote:
>>> 
>>> Well, only one issue has been reported against the beta so far (the NULL 
>>> cxx_stdlib error that Ken saw.) I guess I'll tag an RC soon.
>>> 
>>> - Josh
> 

Re: MacPorts 2.8.0-beta1 now available for testing

[Joshua Root]

I can't repro this. The VCS sync logic hasn't changed since the 
privilege dropping fix in April. The only thing I can think of that 
might have made a difference is the update to Tcl 8.6 and the associated 
update of all the try/catch blocks.


All that should be happening between running git and running portindex 
is the environment restore in VCSCleanup. You might have to do some more 
digging to figure out a repro recipe I'm afraid.


- Josh

On 2022-10-18 20:09 , Christopher Jones wrote:

Hi,

I’m not running the beta but the current master branch of base, but I guess its 
similar.

I’m noticing with the latest version  `sudo port sync` just hangs up after 
updating my local git clone. e.g.

Oberon ~/Projects/MacPorts/ports > sudo port -d sync
DEBUG: Copying /Users/chris/Library/Preferences/com.apple.dt.Xcode.plist to 
/opt/local/var/macports/home/Library/Preferences
--->  Updating the ports tree
Synchronizing local ports tree from file:///Users/chris/Projects/MacPorts/ports
DEBUG: euid/egid changed to: 501/20, env: HOME=/Users/chris 
SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.vx1uKV7YtR/Listeners
DEBUG: /opt/local/bin/git pull --rebase --autostash
DEBUG: system -W /Users/chris/Projects/MacPorts/ports: /opt/local/bin/git pull 
--rebase --autostash
Already up to date.


and thats it, it never gets any further and just hangs up there.

If I contrl-c the process I can get it to continue.

^CDEBUG: euid/egid restored to: 0/0, env restored
DEBUG: system: /opt/local/bin/portindex /Users/chris/Projects/MacPorts/ports
Creating port index in /Users/chris/Projects/MacPorts/ports

Total number of ports parsed:   0
Ports successfully parsed:  0
Ports failed:   0
Up-to-date ports skipped:   29934

any ideas what step its hanging up on ?

Chris



On 14 Oct 2022, at 12:57 am, Joshua Root  wrote:

Well, only one issue has been reported against the beta so far (the NULL 
cxx_stdlib error that Ken saw.) I guess I'll tag an RC soon.

- Josh

Re: MacPorts 2.8.0-beta1 now available for testing

[Christopher Jones]

Hi,

I’m not running the beta but the current master branch of base, but I guess its 
similar.

I’m noticing with the latest version  `sudo port sync` just hangs up after 
updating my local git clone. e.g.

Oberon ~/Projects/MacPorts/ports > sudo port -d sync
DEBUG: Copying /Users/chris/Library/Preferences/com.apple.dt.Xcode.plist to 
/opt/local/var/macports/home/Library/Preferences
--->  Updating the ports tree
Synchronizing local ports tree from file:///Users/chris/Projects/MacPorts/ports
DEBUG: euid/egid changed to: 501/20, env: HOME=/Users/chris 
SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.vx1uKV7YtR/Listeners
DEBUG: /opt/local/bin/git pull --rebase --autostash
DEBUG: system -W /Users/chris/Projects/MacPorts/ports: /opt/local/bin/git pull 
--rebase --autostash
Already up to date.


and thats it, it never gets any further and just hangs up there.

If I contrl-c the process I can get it to continue.

^CDEBUG: euid/egid restored to: 0/0, env restored
DEBUG: system: /opt/local/bin/portindex /Users/chris/Projects/MacPorts/ports
Creating port index in /Users/chris/Projects/MacPorts/ports

Total number of ports parsed:   0 
Ports successfully parsed:  0 
Ports failed:   0 
Up-to-date ports skipped:   29934

any ideas what step its hanging up on ?

Chris


> On 14 Oct 2022, at 12:57 am, Joshua Root  wrote:
> 
> Well, only one issue has been reported against the beta so far (the NULL 
> cxx_stdlib error that Ken saw.) I guess I'll tag an RC soon.
> 
> - Josh

Re: MacPorts 2.8.0-beta1 now available for testing

[Fred Wright]

On Sat, 15 Oct 2022, Joshua Root wrote:

On 2022-10-15 13:20 , Fred Wright wrote:


IMO, it should ask before following replaced_by, since replaced_by is 
sometimes a matter of opinion.  For example, sometimes "port X is replaced 
by port Y" really means "We don't want to bother supporting port X any 
more, so you should use port Y instead; if it doesn't meet your needs then 
that's too bad."


Typically a port with replaced_by set will have been converted to a stub that 
does nothing but error out if you try to install it, so the ability to bypass 
this feature doesn't help you much. But there is a --no-replace flag in case 
it's needed.


Sure, but the inverted default is inconsistent with the way dependencies 
are handled.  If one attempts to install a port with missing dependencies, 
it asks about the dependencies, and if one answers no, then the port isn't 
installed, without having to predict this possible scenario in advance and 
providing an extra option.  I don't see why installing a port instead of 
what the user requested should be more aggressive than installing a port 
in addition to what the user requested.


Fred Wright

Re: MacPorts 2.8.0-beta1 now available for testing

[Joshua Root]

On 2022-10-15 13:20 , Fred Wright wrote:


IMO, it should ask before following replaced_by, since replaced_by is 
sometimes a matter of opinion.  For example, sometimes "port X is 
replaced by port Y" really means "We don't want to bother supporting 
port X any more, so you should use port Y instead; if it doesn't meet 
your needs then that's too bad."


Typically a port with replaced_by set will have been converted to a stub 
that does nothing but error out if you try to install it, so the ability 
to bypass this feature doesn't help you much. But there is a 
--no-replace flag in case it's needed.


- Josh

Re: MacPorts 2.8.0-beta1 now available for testing

[Fred Wright]

On Sat, 15 Oct 2022, Joshua Root wrote:

On 2022-10-14 18:13 , Ken Cunningham wrote:
the only other thing I noticed was that these helpful pre-fetch messages 
were no longer being displayed:


https://github.com/macports/macports-ports/blob/c7a8d3cf75b8b48a90139cbb35e385bb7bcbd165/x11/xorg-server/Portfile#L103 




Instead there was just a message saying the build was known to fail, but 
try anyway?


But the instructions about what to actually do are gone now…

Perhaps no way around that?


In that particular case, the solution is to set `replaced_by 
xorg-server-legacy` instead of erroring in pre-fetch. As of 2.8, replaced_by 
will be followed when installing as well as when upgrading.


IMO, it should ask before following replaced_by, since replaced_by is 
sometimes a matter of opinion.  For example, sometimes "port X is replaced 
by port Y" really means "We don't want to bother supporting port X any 
more, so you should use port Y instead; if it doesn't meet your needs then 
that's too bad."


I can see why the ability to give an explanation more than "this is broken" 
is appealing, but it can't (easily) be done via pre-fetch messages while 
still resolving . We need to figure 
out that ports are known_fail before processing their dependencies.


One annoyance that I've encountered is when a fetch dependency needs to be 
satisfied even when the distfile archive(s) is/are already present.


Fred Wright

Re: MacPorts 2.8.0-beta1 now available for testing

[Joshua Root]

On 2022-10-14 18:13 , Ken Cunningham wrote:
the only other thing I noticed was that these helpful pre-fetch messages 
were no longer being displayed:


https://github.com/macports/macports-ports/blob/c7a8d3cf75b8b48a90139cbb35e385bb7bcbd165/x11/xorg-server/Portfile#L103
 



Instead there was just a message saying the build was known to fail, but 
try anyway?


But the instructions about what to actually do are gone now…

Perhaps no way around that?


In that particular case, the solution is to set `replaced_by 
xorg-server-legacy` instead of erroring in pre-fetch. As of 2.8, 
replaced_by will be followed when installing as well as when upgrading.


I can see why the ability to give an explanation more than "this is 
broken" is appealing, but it can't (easily) be done via pre-fetch 
messages while still resolving . 
We need to figure out that ports are known_fail before processing their 
dependencies.


The fact is that known_fail is almost always set based on platform, and 
the information about what platforms are supported is now available in 
'port info' output. Cases where something can be fixed by the user (like 
"your Xcode version is too old" or "you need to install this SDK") 
should not be setting known_fail anyway.


- Josh

Re: MacPorts 2.8.0-beta1 now available for testing

[Ken Cunningham]

the only other thing I noticed was that these helpful pre-fetch messages were 
no longer being displayed:

https://github.com/macports/macports-ports/blob/c7a8d3cf75b8b48a90139cbb35e385bb7bcbd165/x11/xorg-server/Portfile#L103


Instead there was just a message saying the build was known to fail, but try 
anyway?

But the instructions about what to actually do are gone now…

Perhaps no way around that?

K

Re: MacPorts 2.8.0-beta1 now available for testing

[Joshua Root]

Well, only one issue has been reported against the beta so far (the NULL 
cxx_stdlib error that Ken saw.) I guess I'll tag an RC soon.


- Josh

MacPorts 2.8.0-beta1 now available for testing

[Joshua Root]

Source code and pkgs for MacPorts 2.8.0-beta1 are now
available [1]. Testing of either of these install methods is helpful.

Be prepared to encounter bugs. As always, having a recent backup would
be wise. Please report any bugs that you find [2] (after first searching
Trac [3], of course!)

There are a large number of changes in this release. See the ChangeLog
[4] for a list of most of the major ones. You may like to focus your
testing on the new features in that list, as well as your normal usage.

Cheers,
Josh

[1] <https://github.com/macports/macports-base/releases/tag/v2.8.0-beta1>
[2] <https://trac.macports.org/newticket>
[3] <https://trac.macports.org/search>
[4] <https://github.com/macports/macports-base/blob/release-2.8/ChangeLog>


OpenPGP_signature
Description: OpenPGP digital signature