<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 22 Feb 2020, at 13:32, Christopher Jones <<a href="mailto:jonesc@hep.phy.cam.ac.uk" class="">jonesc@hep.phy.cam.ac.uk</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Have you told macports to use your git clone ?<div class=""><br class=""></div><div class="">i.e. </div><div class=""><br class=""></div><div class=""><div class=""> > cat /opt/local/etc/macports/sources.conf</div><div class=""><snip></div><div class="">#<a href="rsync://rsync.macports.org/macports/release/tarballs/ports.tar" class="">rsync://rsync.macports.org/macports/release/tarballs/ports.tar</a> [default]</div><div class=""><a href="file:///Users/chris/Projects/MacPorts/ports" class="">file:///Users/chris/Projects/MacPorts/ports</a> [default]</div><div class=""><br class=""></div></div></div></div></blockquote><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class="">where for me /Users/chris/Projects/MacPorts/ports is my local git clone.</div></div></div></div></blockquote><div><br class=""></div>Yes.<br class=""><div><br class=""></div><div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><a href="file:///Users/sysbh/MacPortsDev/macports-ports" class="">file:///Users/sysbh/MacPortsDev/macports-ports</a></span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><a href="rsync://rsync.macports.org/macports/release/tarballs/ports.tar" class="">rsync://rsync.macports.org/macports/release/tarballs/ports.tar</a> [default]</span></div><div class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div></div><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class="">b.t.w. Once you have done this, you don’t need to run all the git commands below. just running</div><div class=""><br class=""></div><div class="">> sudo port sync</div><div class=""><br class=""></div><div class="">will update your git clone, and run the portindex, for you.</div></div></div></div></blockquote><div><br class=""></div><div>With rsync, not with git. So what about branches etc? Suppose I create a branch in my fork to work in? And I want update my master to reflect the latest situation of the official repo?</div><div><br class=""></div><div>G</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class=""><br class=""></div><div class="">Chris</div><div class=""><br class=""><blockquote type="cite" class=""><div class="">On 22 Feb 2020, at 11:43 am, Gerben Wierda <<a href="mailto:gerben.wierda@rna.nl" class="">gerben.wierda@rna.nl</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I have my own fork of the macports-ports repository on GitHub so I can do maintenance. I have a local clone of that fork<div class=""><br class=""></div><div class="">When I want to update ports I do not maintain, do the following. First I make sure my clone is up to date with the upstream original, then I push the clone back to my GitHub fork. Then I run portindex. ‘upstream’ is the official repo, origin is my fork</div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">git fetch upstream</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">git checkout master</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">git reset --hard upstream/master</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">git push origin master --force</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">portindex</span></div><div class=""> </div><div class="">But when I do that, I still get:</div><div class=""><br class=""></div><div class=""><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">albus:macports-ports sysbh$ port list updated</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">Warning: port definitions are more than two weeks old, consider updating them by running 'port selfupdate'.</span></div></div><div class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div class="">(Should have said ‘outdated’ of course, this doesn’t give me a warning)</div><div class=""><br class=""></div><div class="">But port self update overwrites everything using rsync and doesn’t go via git. So, it is a parallel and possibly trouble-creating route. I want update my local tree entirely via git.</div><div class=""><br class=""></div><div class="">Still, with a clean clone of of an up-to-date fork, I can do it:</div><div class=""><br class=""></div><div class=""><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">sudo port selfupdate</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">Password:</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">---> Updating MacPorts base sources using rsync</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">MacPorts base version 2.6.2 installed,</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">MacPorts base version 2.6.2 downloaded.</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">---> Updating the ports tree</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">---> MacPorts base is already the latest version</span></div></div><div class=""><br class=""></div><div class="">What is the way to go when updating, using your own clone of your own fork of the git repo?</div><div class=""><br class=""></div><div class="">G</div></div></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></body></html>