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: How to submit a patch to source code for specific arch (apple silicon)

On Thu, Oct 20, 2022 at 6:56 AM Christopher Chavez wrote: > Sent: Wednesday, October 19, 2022 at 12:25 PM > From: "Alejandro Imass" > > > I found a problem with dia (GNU dia diagraming app) in Apple Silicon and > finally got it to compile and run. Was wondering what the process is to > submit a

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: Update ICU to 72

Folks, ICU 72.1 was released. To allow easy test it, I've updated only icu-devel port as https://github.com/macports/macports-ports/pull/16426 . The icu port will be updated in two weeks. I strongly suggest to try to install it to confirm

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: How to submit a patch to source code for specific arch (apple silicon)

Sent: Wednesday, October 19, 2022 at 12:25 PM From: "Alejandro Imass" > I found a problem with dia (GNU dia diagraming app) in Apple Silicon and > finally got it to compile and run. Was wondering what the process is to > submit a patch ? Are there any docs I can read that describe the process

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