I had to upgrade to 10.15 (wanted to postpone this further but ...) and recall that there were many
reports over the last months of problems with subsequent macports upgrade, recommendations to use
previous xcode releases with catalina and assorted package specific problems simply not being
solv
Hi,
I would say the situation with 10.15 is now similar to other OSes. Some
things work, some things do not. There are also some clear cases of
things not working, and cannot/willnot be fixed, such as 32 bit support.
At the end of the day though only you know which ports you really care
abou
Given my absolute lack of decent git skills (and it’s just too complicated for
a fast skill increase) I have the following setup (which so far worked)
I have a macports-ports clone on GitHub which I use locally. I need a clone or
I cannot create pull requests.
When I have to do a reset, I:
- s
If anyone else pushed between your fetch and push, you'll be out of date
again.
Not entirely sure what your workflow is, but you a current git should
let you do an autostash on pull (which might help your situation):
git pull --rebase --autostash && git push
On 1/9/20 4:34 PM, Gerben Wierd
Me too. We’re discussing MacPorts-relevant git commands in
https://github.com/macports/macports-ports/pull/6106 .
Easiest, most destructive to local:
# save all local files changed outside the git repo
git fetch --all
git reset --hard upstream/master
# restore all local files
> On Jan 9, 20
On 2020-01-09, at 2:33 PM, Steven Smith wrote:
> Me too. We’re discussing MacPorts-relevant git commands in
> https://github.com/macports/macports-ports/pull/6106 .
>
> Easiest, most destructive to local:
>
> # save all local files changed outside the git repo
>
> git fetch --all
> git reset
