Re: MacPorts 2.8.0-beta1 now available for testing

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

Re: MacPorts 2.8.0-beta1 now available for testing

> 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

Re: MacPorts 2.8.0-beta1 now available for testing

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

Re: MacPorts 2.8.0-beta1 now available for testing

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

Re: MacPorts 2.8.0-beta1 now available for testing

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.

Re: MacPorts 2.8.0-beta1 now available for testing

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

Re: MacPorts 2.8.0-beta1 now available for testing

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

Re: MacPorts 2.8.0-beta1 now available for testing

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

Re: MacPorts 2.8.0-beta1 now available for testing

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

Re: MacPorts 2.8.0-beta1 now available for testing

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,

Re: MacPorts 2.8.0-beta1 now available for testing

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

Re: MacPorts 2.8.0-beta1 now available for testing

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

Re: MacPorts 2.8.0-beta1 now available for testing

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

Re: MacPorts 2.8.0-beta1 now available for testing

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

Re: MacPorts 2.8.0-beta1 now available for testing

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

Re: MacPorts 2.8.0-beta1 now available for testing

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:

Re: MacPorts 2.8.0-beta1 now available for testing

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

Re: MacPorts 2.8.0-beta1 now available for testing

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,

Re: MacPorts 2.8.0-beta1 now available for testing

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

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