<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><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class="">OSL in particular appears to be a problem on my machine. I've copied the newer version of the portfile directly to my local machine, and tried to build it, but it's failing to build because osl is indirectly dependent on opencolorio (by way of openimageio), and apparently there's a new problem with either opencolorio or openimageio:</div><div class=""><br class=""></div><div class="">:info:build dyld: Symbol not found: __ZN4YAML6detail9node_data12empty_scalarE<br class="">:info:build Referenced from: /opt/local/lib/libOpenColorIO.1.dylib</div><div class="">:info:build Expected in: /opt/local/lib/libyaml-cpp.0.6.dylib<br class="">:info:build in /opt/local/lib/libOpenColorIO.1.dylib<br class="">:info:build /bin/sh: line 1: 34490 Trace/BPT trap: 5</div><div class="">:info: build opt/local/var/macports/build/_Users_jasonliu_ports_graphics_osl/osl/work/build/bin/oslc -q -I/opt/local/var/macports/build/_Users_jasonliu_ports_graphics_osl/osl/work/OpenShadingLanguage-1.11.13.0/src/shaders -I/opt/local/var/macports/build/_Users_jasonliu_ports_graphics_osl/osl/work/OpenShadingLanguage-1.11.13.0/src/shaders -I/opt/local/var/macports/build/_Users_jasonliu_ports_graphics_osl/osl/work/OpenShadingLanguage-1.11.13.0/src/shaders /opt/local/var/macports/build/_Users_jasonliu_ports_graphics_osl/osl/work/OpenShadingLanguage-1.11.13.0/src/shaders/emitter.osl -o /opt/local/var/macports/build/_Users_jasonliu_ports_graphics_osl/osl/work/build/src/shaders/emitter.oso</div></div></div></div></blockquote><div><br class=""></div><div><br class=""></div><div>Did you also update all the other outdated ports on your ‘local’ machine, or did you just cherry-pick the updated osl from the current master ? </div><div><br class=""></div><div>If so it is really not a good idea to do that, as it means, as appears above, you could get an updated binary tarball install that was built against another updated port you do not have.</div><div><br class=""></div><div>You should *always* keep all your ports updated and consistent.</div><div><br class=""></div><div>if you run</div><div><br class=""></div><div>> sudo port -d sync</div><div>> sudo port update outdated</div><div><br class=""></div><div>does that help ></div><div><br class=""></div><div>Just finally to note, there is nothing wrong with the current osl builds, they are available (apart from arm) down to 10.9</div><div><br class=""></div><div><a href="https://ports.macports.org/port/osl/summary" class="">https://ports.macports.org/port/osl/summary</a></div><div><br class=""></div><div>Chris</div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class=""><div dir="ltr" data-smartmail="gmail_signature" class=""><div dir="ltr" class=""><div class="">-- </div><div class="">Jason Liu<br class=""></div></div></div></div><br class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 7, 2021 at 7:32 AM Ryan Schmidt <<a href="mailto:ryandesign@macports.org" target="_blank" class="">ryandesign@macports.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br class="">
<br class="">
On May 7, 2021, at 01:59, Jason Liu wrote:<br class="">
<br class="">
> I've run across a situation that has left me confused. I started updating some of the portfiles for which I'm the maintainer, and then I noticed that the portfiles seem to have already been updated in git. However, I can't find any PRs for such an update, and I was never notified that the ports for which I'm the maintainer was getting updated... usually, if someone submits a PR for a portfile for which I'm the maintainer, I get a notification through GitHub.<br class="">
<br class="">
If your ports are marked openmaintainer, that gives permission to others to make minor modifications to your ports without notifying you. Not all changes happen via PRs; some are committed directly to master.<br class="">
<br class="">
If there is an urgent issue that needs to be fixed in a port, someone else might make that fix, even if the port is not marked openmaintainer.<br class="">
<br class="">
If you let us know specifically which ports, we could take a look.<br class="">
<br class="">
<br class="">
> In addition, I have run a "port selfupdate" on my machine, and yet the MacPorts on my machine isn't seeing the new version of the port. Is something broken, either on my machine, or on GitHub?<br class="">
<br class="">
If your MacPorts is configured to get ports via rsync, it can take an hour for changes to propagate from git to the main rsync server, and up to a day longer for changes to propagate from there to other rsync mirrors.</blockquote></div></div>
</div></blockquote></div><br class=""></body></html>