Re: py311+-mysqlclient
Am 09.01.24 um 22:32 schrieb Craig Treleaven: On Jan 9, 2024, at 3:55 PM, Henning Hraban Ramm wrote: Hi, is there a reason there’s no py311 or py312 version of mysqlclient? Hraban I created it for something I used to work on. The other thing has gone by the wayside. Our user stats didn’t show anybody else using it so I hadn’t really thought about it for some time. Now that I look, I see that upstream has made some non-trivial updates. https://ports.macports.org/port/py-mysqlclient/details/ I’ll have a go at updating it. May take a few days. Thank you! I have MacPort’s Python 3.11 as my default Python. Additionally installed 3.10 now and made a virtualenv with it where I needed mysqlclient (a local test environment for a Django app that I wanted to check on different Python versions); I couldn’t get mysqlclient (3.10) working, since the global one isn’t available in the venv and pip can’t install it (I guess the mysql-dev libs are missing). I symlinked the one from MacPorts’ Python framework into the venv’s site-packages, and it works so far, but I don’t like such hacks, since now my requirements.txt doesn’t work for the local installation any more. If you had hints how to resolve this situation better, I’d be glad. (I found nothing helpful on the internet, search engine results just aren’t usable any more…) (I’m still on Mojave BTW.) Hraban OpenPGP_0x1D6502AA1C9B22FD.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
py311+-mysqlclient
Hi, is there a reason there’s no py311 or py312 version of mysqlclient? Hraban OpenPGP_0x1D6502AA1C9B22FD.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Re: Unistalling gmic-gimp macport
Am 11.10.23 um 07:34 schrieb Michal Sidorczyk: I know there are some upgrade instructions, but I did not follow them, I admit. Having the problem with disk space I do not put even more overhead of it, without being certain that eventually I will get rid of this extra 10GB space. Can you help me with my problem to remove gmic-gimp from my drive? Just remove the complete MacPorts installation (/opt/local), you can’t use it anyway on a different platform. Otherwise don’t complain if you are not willing to follow exsting documentation. Hraban OpenPGP_0x1D6502AA1C9B22FD.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: meld quartz breakage
Am 07.10.23 um 00:00 schrieb Riccardo Mottola via macports-users: Hi, as I opened this bug report some months ago, at a certain point meld stopped working properly on Mac Quartz https://trac.macports.org/ticket/67169 File tree displays randomly with blank and flashes when moving the mouse over, sometimes revealing the file. What is even more interesting is that left and right tree might display exclusively the file name. Interestingly, breakage does not appear to be related to a new version of meld itself (I also tried reverting) but it must be one of the many dependencies. When it broke, it happened on all systems I had access and got it compiling: 10.6, 10.7, 10.11 and 10.13 Could someone test on their systems? I know that on linux it works. It works for me on 10.14 under XQuartz; I remember having strange problems with meld on some linux machine where it didn’t fill its window… Hraban OpenPGP_0x1D6502AA1C9B22FD.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: Thanks for efforts
Am 29.11.22 um 15:13 schrieb Stanton Sanderson: Much appreciate the fix for qt5-qtwebengine - successful update on OS 11.7.1 Same here on 10.14.6 – but py310-pyqt5-webengine still fails. Hraban OpenPGP_0x1D6502AA1C9B22FD.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: fullscreen mode(s) in 10.11 and up (not MP-related)
Am 09.08.22 um 20:43 schrieb René J.V. Bertin: I've been doing some maintenance an an in-law's 2011 iMac, upgrading it from 10.11 to 10.13. At some point I noticed that the fullscreen widget was missing from the right corner of the window title bars, and that the "maximise" button apparently toggles fullscreen mode. You get the usual maximize behavior if you press alt. Which begs the question what happens on a multi-head set-up where you don't give a "Space" to each screen. Does putting a window/app in fullscreen mode still black out all other screens as it does on 10.9 (where you at least have the option to maximise the window instead)? Don’t know. Hraban OpenPGP_0x1D6502AA1C9B22FD.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: certificate update for old Macs
Am 04.01.22 um 21:11 schrieb Richard L. Hamilton: Everyone just says "As long as the roots are good you can trust the chain", and that's never made sense to me. The whole "trust what strangers say" system seems more like "Find a way for companies to make money" than any good security system. Certificates are similar to passports – if you look at a person’s passport you must decide if you trust the issuer. If it’s a known country and the passport is valid (and looks legit as far as you can guess), you will trust it. If it’s from a country you never heard of, you might doubt its validity. If it’s from a separatist organization you find trustworthy, you might trust it anyway (similar to the CAcert case). Hraban OpenPGP_0x1D6502AA1C9B22FD.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: provide latest OS root certificates via port?
> Am 01.11.2021 um 00:32 schrieb raf : > > On Sun, Oct 31, 2021 at 11:46:46AM +0100, Henning Hraban Ramm > wrote: >> >> I’m working on a 2013 Mac mini and can’t upgrade further than 10.14 (don’t >> want to loose my 32 bit software, and I seem too stupid for VMs). >> (I also just upgraded a 2010 Thinkpad Edge with a SSD and current Ubuntu, >> but that’s a different story.) >> >>> Is anyone else on old systems >>> able to run "/opt/local/libexec/mpstats submit"? I read somewhere that >>> errors >>> are silently ignored during automatic submission. >> >> It’s not installed. To which port does the command belong? > > It's the "mpstats" port. I could have guessed. Actually I tried "port search", and nothing turned up – today it did. Probably I mistyped. $ /opt/local/libexec/mpstats submit Submitting data to https://ports.macports.org/statistics/submit/ ... Error: Peer certificate cannot be authenticated with given CA certificates while executing "curl post "submission\[data\]=$json" $stats_url" So I can confirm the issue on 10.4, even after installing the ISRG Root certificate in the System keychain. Sláinte, Hraban signature.asc Description: Message signed with OpenPGP
Re: provide latest OS root certificates via port?
> Am 31.10.2021 um 10:37 schrieb raf : > > On Fri, Oct 29, 2021 at 09:02:34AM -0700, Michael wrote: > > And this will happen again and again as every root certificate becomes > ancient and expires. So it would be nice to have an easy way to to keep > a system's root certificates up to date, and hopefully, one day, operating > system vendors will agree. :-) It'll get on the news when everyone's smart > TVs stop working. :-) These TVs will have stopped working long before their certificates expire. ;) Then it’s just a problem for the restaurators in technical museums. > But since it seems that there are few people using old macOS systems, > it might remain a manual process. I guess there are more than few people, but not everyone complains publicly. I just silently installed the necessary root cert. I’m working on a 2013 Mac mini and can’t upgrade further than 10.14 (don’t want to loose my 32 bit software, and I seem too stupid for VMs). (I also just upgraded a 2012 Thinkpad Edge with a SSD and current Ubuntu, but that’s a different story.) > Is anyone else on old systems > able to run "/opt/local/libexec/mpstats submit"? I read somewhere that errors > are silently ignored during automatic submission. It’s not installed. To which port does the command belong? Hraban signature.asc Description: Message signed with OpenPGP
Re: Why does git branch -a
Hi Gerben! > Am 23.10.2021 um 11:58 schrieb Gerben Wierda via macports-users > : > > # remotes: > # upstream: github/macports/macports-ports is the original macports.org > repo in github > # origin: github/gctwnl/macports-ports is my FORK of > github/macports/macports-ports on github > # local: > # ~/MacPortsDev/macports-ports is the local CLONE of > github/gctwnl/macports-ports > > albus:macports-ports sysbh$ git branch -a > dovecot-2.3.16 > * master > upstream > remotes/origin/HEAD -> origin/master > remotes/origin/dovecot-2.3.16 > remotes/origin/master > remotes/origin/multiple-unbounds > remotes/upstream/boost_1.72.0_update > remotes/upstream/dar > remotes/upstream/kencu-py-sphinxcontrib-svg2pdfconverter > remotes/upstream/master > remotes/upstream/py38-reproject > remotes/upstream/wireshark3-3-0-5 > > But I do not fully understand the remotes/origin ones. Specifically: > remotes/origin/multiple-unbounds. I did some work on unbound as well > (enabling to run multiple parallel unbound resolvers from launchd) and this > has been pulled into the main repository. When that had happened, I deleted > my branch. Apparently I forgot to do something because it still shows up in > remotes/origin. Why, though? What did I forget to do? Origin is your fork of upstream, and when you deleted your local branch, you apparently didn’t delete the same branch on origin. Each repository is independent. HTH Hraban signature.asc Description: Message signed with OpenPGP
Re: Zint port?
> Am 05.09.2021 um 15:14 schrieb Masc Guy : > > > The barcode maker/library zint (https://zint.org.uk) is only available via > > Homebrew yet. It depends on cmake and libpng-dev, but if I try to compile > > the sources with MacPorts libs, it fails to find stdio.h > > Zint was just added as a new port yesterday, by one of our members. > > Enjoy! Great, thank you (and them)! And thank you, Frank, for the portfile hints! Hraban signature.asc Description: Message signed with OpenPGP
Zint port?
The barcode maker/library zint (https://zint.org.uk) is only available via Homebrew yet. It depends on cmake and libpng-dev, but if I try to compile the sources with MacPorts libs, it fails to find stdio.h I don’t speak C... I’d appreciate a zint port, but a hint what environment variables I should set or whatever else I should try would be nice enough. Best regards, Hraban signature.asc Description: Message signed with OpenPGP
Re: MacPorts 2.7.0 has been released
> Am 19.05.2021 um 12:15 schrieb Joshua Root : > > The MacPorts Project is happy to announce that the 2.7.0 version has now > been released. It is available via the usual methods: $ sudo port selfupdate Password: ---> Updating MacPorts base sources using rsync MacPorts base version 2.6.4 installed, MacPorts base version 2.7.0 downloaded. ---> Updating the ports tree ---> MacPorts base is outdated, installing new version 2.7.0 Installing new MacPorts release in /opt/local as root:wheel; permissions 0755 $ sudo port upgrade outdated Password: sqlite error: near "COLUMN": syntax error (1) while executing query: ALTER TABLE registry.ports RENAME COLUMN negated_variants TO requested_variants while executing "registry::open $db_path" (procedure "mportinit" line 712) invoked from within "mportinit ui_options global_options global_variations" Error: /opt/local/bin/port: Failed to initialize MacPorts, sqlite error: near "COLUMN": syntax error (1) while executing query: ALTER TABLE registry.ports RENAME COLUMN negated_variants TO requested_variants What can I do to fix this? I used "port upgrade outdated" just yesterday, so everything should be quite recent. (macOS 10.14.6) Hraban signature.asc Description: Message signed with OpenPGP
Re: updating TeX Live
Hi Mojca! > Am 12.02.2021 um 02:37 schrieb Mojca Miklavec : > > On Thu, 11 Feb 2021 at 22:34, Henning Hraban Ramm wrote: >> >> Hi, is there a possibility to update the MacPorts version of TeX Live 2020? > > It depends on whether you are willing to wait for TeX Live 2021, or > willing to volunteer to create devel subports yourself. See: >https://github.com/macports/macports-ports/tree/master/tex > > Otherwise ... not really. Thanks, that’s what I feared, but expected. >> (I’m debugging at a customer’s LaTeX project, colleagues and build server >> have different versions of TeX Live 2020. I installed the MacPorts version >> because I needed it as a dependency anyway, but now I’d need an update, and >> I don’t dare to just overwrite anything in /opt/local/) > > If you need the latest version, go for > http://www.tug.org/texlive/acquire-netinstall.html or MacTeX. Yes, of course. (Seems there’s some bug in the TL2020 mac binary of luatex in combination with luaotfload that affects LaTeX’s draft mode.) Hraban signature.asc Description: Message signed with OpenPGP
updating TeX Live
Hi, is there a possibility to update the MacPorts version of TeX Live 2020? Usually you would use "tlmgr update --self --all". There are fixes for several packages, and even the LuaTeX binary got a fix, I was told. (I’m debugging at a customer’s LaTeX project, colleagues and build server have different versions of TeX Live 2020. I installed the MacPorts version because I needed it as a dependency anyway, but now I’d need an update, and I don’t dare to just overwrite anything in /opt/local/) Best, Hraban signature.asc Description: Message signed with OpenPGP
Re: SDK does not appear to be installed
For MacOS 10.14 (XCode 11.3) I solved the same problem by downloading the CLI tools from developer.apple.com and installing them. Hraban > Am 03.02.2021 um 21:12 schrieb Marius Schamschula : > > Indeed! > > I just upgraded a machine to Big Sur, installed Xcode and the CLI tools. I > got the same message. I used the reinstall procedure - no change. > > My guess is that the CLI tools for 11.2 are not out yet. > >> On Feb 3, 2021, at 2:08 PM, Tom wrote: >> >> Hello people, >> >> what was the solution to this problem? >> I cannot find the e-mail anymore. >> >>> Warning: The macOS 11.2 SDK does not appear to be installed. Ports may not >>> build correctly. >>> Warning: You can install it as part of the Xcode Command Line Tools package >>> by running `xcode-select --install'. signature.asc Description: Message signed with OpenPGP
Re: macOS security update has changed some permissions for apache2 server...?
> Am 02.02.2021 um 13:20 schrieb Carlo Tambuatco : > > This might seem like a small issue, but it bothers me because I just can’t > find > what changed... > > It seems the latest security update to macOS has rendered me unable to view > the > apache manual pages installed on my local webserver. It worked fine before the > update, but now when I open up a browser to http://localhost:8080/manual, I > get > 403 Forbidden, you don’t have permission to access this resource. > > I checked my httpd.conf file, and my extra/httpd-manual.conf file which > contain the > apache directives for viewing and handling the manual pages, but as far as I > can tell, > nothing changed. It seems apache2 can find the directory, but it now says I > don’t > have permission to view it? What possibly could have changed? Did you check if Apache is allowed to access (and serve) the folder and files of the manual pages? Best, Hraban signature.asc Description: Message signed with OpenPGP
Re: 'LANG=' produces German output
> Am 2020-02-13 um 23:11 schrieb Werner LEMBERG : > >>> I'm not sure whether I like this feature. At least on the command >>> line, I consider it surprising. >> >> There is the opposite expectation: "I have set that I want the >> programs to talk to me in German. Why do I need to specify it a >> second time, through an environment variable, for the command-line >> programs?" > > Because we did this the last 20 years? As written above, I consider > it surprising, not necessarily bad... It’s just a DE-fault ;) Hraban
Re: XCode 11 on Mojave problem, again
> Am 2019-11-09 um 17:45 schrieb Ryan Schmidt : > >>> That is a bad idea, pretending a 10.15 SDK is a 10.14 one could lead to >>> unforeseen side effects. So this is not something we recommend anyone does. >> >> I’m a cowboy coder ;) > > Well, please revert the change so that it doesn't cause you trouble, since we > don't want to receive tech support questions in the future that might arise > from it. Ok. Don’t worry. >>> Have you tried installing the CLT ? That should provide a 10.14 SDK that >>> the latest MacPorts release will use. >> >> I thought CLT was installed with XCode. > > It was prior to Xcode 4. These days it is a separate install. We recommend > you install it. > >> I tried now and it didn’t change the SDKs. > > It won't change which SDKs are available in Xcode, but it will install a > separate SDK that matches your OS version in the CLT directory. Now that > you've installed the CLT, whichever port(s) you have installed that contain > baked-in references to Xcode 10's 10.14 SDK will have to be rebuilt so that > they instead use either Xcode 11's 10.15 SDK (if the port says "use_xcode > yes") or the CLT's 10.14 SDK (if not). Ah, thanks. I didn’t find them, let’s hope it’ll work. Best, Hraban
Re: XCode 11 on Mojave problem, again
> Am 2019-11-09 um 15:07 schrieb Chris Jones : > >> On 9 Nov 2019, at 1:50 pm, Henning Hraban Ramm wrote: >> >> Hi, >> I also had problems on Mojave, since at least cctools was expecting a >> MacOSX10.14.sdk in >> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs; >> on Mojave there’s only the 10.15 SDK. >> I had XCode 10.something and updated yesterday to 11.latest; that needed >> some hours... >> >> Since I didn’t find a way to install a 10.14 SDK, I just made a symlink to >> the 10.15 SDK under the name of MacOSX10.14.sdk, and it works so far! > > That is a bad idea, pretending a 10.15 SDK is a 10.14 one could lead to > unforeseen side effects. So this is not something we recommend anyone does. I’m a cowboy coder ;) > Have you tried installing the CLT ? That should provide a 10.14 SDK that the > latest MacPorts release will use. I thought CLT was installed with XCode. I tried now and it didn’t change the SDKs. HR
Re: XCode 11 on Mojave problem, again
Hi, I also had problems on Mojave, since at least cctools was expecting a MacOSX10.14.sdk in /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs; on Mojave there’s only the 10.15 SDK. I had XCode 10.something and updated yesterday to 11.latest; that needed some hours... Since I didn’t find a way to install a 10.14 SDK, I just made a symlink to the 10.15 SDK under the name of MacOSX10.14.sdk, and it works so far! All the ports that didn’t compile previously, like cctools, ImageMagick, Inkscape (maybe unrelated) and MariaDB10.* ran through. Greetlings, Hraban BTW: Hello Mojca! ;) > Am 2019-11-09 um 10:39 schrieb Ruben Di Battista : > > Ehi Mojca, > > Thanks for the message. :) > > I managed to fix it. I got confused because recently I updated Xcode, but in > facts the problem was completely unrelated: I had a project header file named > “math.h”. :) Very noob mistake! Interestingly enough, this bug does not > pop-out on Linux (using GCC). > > So I just renamed “math.h” to a custom name, and now everything is back as > before (Ah, pay attention! Most of macOS systems have a case-insensitive > filesystem… I firstly renamed the file from “math.h” -> “Math.h”, but it > didn’t work either and it took a while to realize that on macOS “math.h” and > “Math.h” are the same if the FS is case-insensitive. signature.asc Description: Message signed with OpenPGP
Re: dmgbuild ports disappeared
> Am 2019-10-20 um 15:15 schrieb Christopher Jones : > > Hi, > > Running > > git log -Sdmgbuild > > on my clone of the ports repo returns nothing. I hate to disagree with you, > but think this means there has never been any relating the dmgbuild in the > ports tree, at least as far as the current git history goes back. Ok, seems like it was my imagination. Probably I unconsciously used pip-3.7 and pip-2.7. Sorry for the noise. Best regards, Hraban smime.p7s Description: S/MIME cryptographic signature
Re: dmgbuild ports disappeared
> Am 2019-10-20 um 13:51 schrieb Ryan Schmidt : > > 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.
Re: dmgbuild ports disappeared
> Am 2019-10-20 um 12:53 schrieb Werner LEMBERG : >> I looked for "dmgbuild" in all mailing list, tracker and github >> commit messages and found only: > > What about > https://pypi.org/project/dmgbuild/ > Doesn't it work to install with pip (or pip2/pip3)? Yes it works. I can also just clone the git repository. But I wanted to understand why the ports were removed and why I couldn’t find anything about that. Best regards, Hraban
dmgbuild ports disappeared
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
