> Am 2019-10-20 um 13:51 schrieb Ryan Schmidt <ryandes...@macports.org>: > > On Oct 20, 2019, at 05:42, Henning Hraban Ramm wrote: > >> Hi, I’m using MacPorts for many years, but I’m new on this list. >> >> A few days ago I was building SCM Workbench[1] on MacPorts Python 3.7 >> (because the binary package was expecting python.org Frameworks to be >> installed). The project uses dmgbuild[2], and there were ports for all(?) >> versions of Python. >> >> py37-dmgbuild didn’t work, because the port used an old state of dmgbuild >> that was Py2 only, but py27-dmgbuild did the job. >> >> Today I wanted to document the process – and the ports were gone! >> >> I looked for "dmgbuild" in all mailing list, tracker and github commit >> messages and found only: >> >> * https://trac.macports.org/attachment/ticket/56662/main.log (dmgbuild used >> as an external tool) >> * https://trac.macports.org/attachment/ticket/59137/vlc_build_log_clang8.log >> (dmgbuild not found) >> >> (I used Google with "site:" as well as site searches.) >> >> Does anyone know why these ports were removed (instead of updated maybe) or >> how I could find out more? >> >> Best regards, Hraban >> >> [1] https://github.com/barry-scott/scm-workbench >> [2] https://github.com/al45tair/dmgbuild > > I also can't find any trace of a py-dmgbuild in MacPorts. Are you sure it > existed? If you had a py-dmgbuild portfile, is it possible you wrote it > yourself, or downloaded it from some place other than MacPorts?
No, I didn’t write it myself, and I’m sure it was there 3 days ago (see https://github.com/barry-scott/scm-workbench/issues/12), since I installed py37-dmgbuild first and then py27-dmgbuild. Strange. Seems like my Mac is infested... Best regards, Hraban BTW updating MacPorts today fixed poppler-qt5 again, yay! (That one makes trouble all the time.) But it destroyed all of my pips (py37-pip,py36-pip and py27-pip), I needed to reinstall them.
