Troubles installing ports with Macports 2.3.1
On Jul 1, 2014, at 4:58 AM, Joël Brogniart wrote: I suppose that, during the Computing dependencies for auto-multiple-choice phase, a lot of http requests are made to obtain port information and that these requests are not fully closed either by Macports or by the proxy. As this problem is recent (at least for me), it is perhaps related to a recent Java update (the proxy is a java application). During computing dependencies, no http requests would be made by MacPorts, as far as I know. To determine whether build dependencies are required, it must know whether an archive is available, and to find that out, it (usually) must query the packages server. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: of KDE's kcookiejar and kded4 failing to launch automatically
On Jul 02, 2014, at 05:25, Ian Wadham wrote: Please feel free to join us on kde-mac as Marko has suggested. Maybe you would like to skim the recent archives there and on kde-devel [1] and [2]. What Boudewijn Rempt, a seasoned KDE developer, has to say is rather interesting. Lots of things that feel way over my head ... or that'd be just that if I jumped into the Qt+KDE ocean (I'm not exactly a seasoned C++ dev and hardly familiar with both APIs) :) I noticed you're looking into the fact that so many dialogs open behind the calling window. Wouldn't that be because the apps that open them are opened through your standard Unix/Posix calls like system() or execXX()? Case in point: if you launch an application like /Applications/MacPorts/KDE4/konqueror.app/Contents/MacOS/konqueror it will indeed open behind the terminal window in which you just typed that command. I'm not sure if the Cocoa functions for launching commands (in the NSTask) would accept arguments or pass arguments that are not files. R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Troubles installing ports with Macports 2.3.1
On Jul 2, 2014, at 2:25 AM, Joshua Root wrote: On Jul 1, 2014, at 4:58 AM, Joël Brogniart wrote: I suppose that, during the Computing dependencies for auto-multiple-choice phase, a lot of http requests are made to obtain port information and that these requests are not fully closed either by Macports or by the proxy. As this problem is recent (at least for me), it is perhaps related to a recent Java update (the proxy is a java application). During computing dependencies, no http requests would be made by MacPorts, as far as I know. To determine whether build dependencies are required, it must know whether an archive is available, and to find that out, it (usually) must query the packages server. Ok, but that would only be enough http requests to determine if an archive for the main port is available, right? So ideally 1 http request (in the case where the archive exists on the server it tried), or maybe a few requests (to check a few additional servers). It wouldn't be proportional to the number of dependencies. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: libffi refuses to upgrade
On Jun 30, 2014, at 6:46 PM, semaphor...@yahoo.com wrote: I found this bug in the list, but it is happening on a fully 64-bit platform. I don't get it. What else could be causing this problem? The developers of libffi have written code that is incompatible with your system or compiler and will have to fix it. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Issue with mirroring gnutls source files
HI all, I’ve been researching https://trac.macports.org/ticket/44199 It seems that the newest files on the MacPorts mirrors are for gnutls version 3.1.x. Why are the gnutls 3.3.x files not mirrored? How is mirroring enabled? Is there an issue if the master site is ftp based? Marius -- Marius Schamschula ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Issue with mirroring gnutls source files
On Jul 2, 2014, at 1:45 PM, Marius Schamschula wrote: I’ve been researching https://trac.macports.org/ticket/44199 It seems that the newest files on the MacPorts mirrors are for gnutls version 3.1.x. Why are the gnutls 3.3.x files not mirrored? How is mirroring enabled? It is enabled automatically, for all ports. If for any port you want files *not* to be mirrored you must email admin at macosforge dot org and ask them to place the port on a special mirroring blacklist. Is there an issue if the master site is ftp based? Yes, Apple's servers cannot talk to ftp servers (or rather: Apple's network blocks the port numbers that ftp traffic typically uses). We worked around this as follows: Daniel Luke is running a proxy server which can be talked to over a port number that Apple's network does have open, and the MacPorts servers are configured to use that proxy server for ftp traffic. There was a recent Apple network reconfiguration which interrupted that for some time. Then more recently, Daniel's proxy server was offline for some time. Everything should be working now, but it could be that gnutls was updated to 3.3.x during one of those outages. If so, committing any change to the port should cause the server to attempt to mirror it again, because there's supposed to be a post-commit hook that does that. There's also supposed to be a daily cronjob to mirror all distfiles, in case the post-commit missed something. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Issue with mirroring gnutls source files
On Jul 2, 2014, at 3:22 PM, Ryan Schmidt ryandes...@macports.org wrote: There was a recent Apple network reconfiguration which interrupted that for some time. Then more recently, Daniel's proxy server was offline for some time. Everything should be working now, but it could be that gnutls was updated to 3.3.x during one of those outages. If so, committing any change to the port should cause the server to attempt to mirror it again, because there's supposed to be a post-commit hook that does that. There's also supposed to be a daily cronjob to mirror all distfiles, in case the post-commit missed something. Also - For some reason my MacPorts installed ports don't stay loaded with `port load foo` on that machine (ie, when I reboot squid3 doesn't start up unless/until I do another `port load squid3`). I haven't had time to investigate why (yet). It wouldn't be (much) of an issue either, but I've been seeing a (widely reported) tcp stack bug on Mavericks which means I end up rebooting that machine way more often than I normally would have to. -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Help with DYLD_LIBRARY_PATH
Hi I wanted to install SAGA GIS and forcing MacPorts to build over already existing libraries. I edited the macports.conf file and added this line but MacPorts doesn't seem to care about… Is this correct? extra_env DYLD_LIBRARY_PATH=/Library/Frameworks/GEOS.framework/Versions/Current/unix/lib:/Library/Frameworks/GDAL.framework/Versions/Current/unix/lib: /Library/Frameworks/PROJ.framework/Versions/Current/unix/lib:/Library/Frameworks/PROJ.framework/Versions/Current/unix/lib:/opt/lib Best regards. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Issue with mirroring gnutls source files
On Jul 2, 2014, at 2:49 PM, Daniel J. Luke dl...@geeklair.net wrote: On Jul 2, 2014, at 3:22 PM, Ryan Schmidt ryandes...@macports.org wrote: There was a recent Apple network reconfiguration which interrupted that for some time. Then more recently, Daniel's proxy server was offline for some time. Everything should be working now, but it could be that gnutls was updated to 3.3.x during one of those outages. If so, committing any change to the port should cause the server to attempt to mirror it again, because there's supposed to be a post-commit hook that does that. There's also supposed to be a daily cronjob to mirror all distfiles, in case the post-commit missed something. Also - For some reason my MacPorts installed ports don't stay loaded with `port load foo` on that machine (ie, when I reboot squid3 doesn't start up unless/until I do another `port load squid3`). I haven't had time to investigate why (yet). It wouldn't be (much) of an issue either, but I've been seeing a (widely reported) tcp stack bug on Mavericks which means I end up rebooting that machine way more often than I normally would have to. Is your MacPorts prefix on a different volume than your OS X startup volume? That's apparently a problem now, in that launchd tries to load the plist before the volume that the plist is on has been mounted. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Issue with mirroring gnutls source files
On Jul 2, 2014, at 4:08 PM, Ryan Schmidt ryandes...@macports.org wrote: For some reason my MacPorts installed ports don't stay loaded with `port load foo` on that machine (ie, when I reboot squid3 doesn't start up unless/until I do another `port load squid3`). I haven't had time to investigate why (yet). It wouldn't be (much) of an issue either, but I've been seeing a (widely reported) tcp stack bug on Mavericks which means I end up rebooting that machine way more often than I normally would have to. Is your MacPorts prefix on a different volume than your OS X startup volume? That's apparently a problem now, in that launchd tries to load the plist before the volume that the plist is on has been mounted. yes, that's most likely the issue. I haven't bothered to copy the files over (or make my own launchd plists) to verify yet. -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Issue with mirroring gnutls source files
On Jul 2, 2014, at 3:15 PM, Daniel J. Luke dl...@geeklair.net wrote: On Jul 2, 2014, at 4:08 PM, Ryan Schmidt ryandes...@macports.org wrote: For some reason my MacPorts installed ports don't stay loaded with `port load foo` on that machine (ie, when I reboot squid3 doesn't start up unless/until I do another `port load squid3`). I haven't had time to investigate why (yet). It wouldn't be (much) of an issue either, but I've been seeing a (widely reported) tcp stack bug on Mavericks which means I end up rebooting that machine way more often than I normally would have to. Is your MacPorts prefix on a different volume than your OS X startup volume? That's apparently a problem now, in that launchd tries to load the plist before the volume that the plist is on has been mounted. yes, that's most likely the issue. I haven't bothered to copy the files over (or make my own launchd plists) to verify yet. We discussed this issue on the list some weeks back and there may be a way we could modify the way MacPorts generates the plists to overcome this problem but I haven't had time to try it out yet. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Troubles installing ports with Macports 2.3.1
Hi, Ok, but that would only be enough http requests to determine if an archive for the main port is available, right? So ideally 1 http request (in the case where the archive exists on the server it tried), or maybe a few requests (to check a few additional servers). It wouldn't be proportional to the number of dependencies. Yes it would. The check is run to find out whether an archive is available (in which case the build dependencies for this port can be skipped), but the same is not necessarily true for other dependencies. Consequently, the same check is run for every port in the dependency tree of the main port. I think this may be related to http://trac.macports.org/changeset/117022 where I changed from curl_easy_cleanup() to curl_easy_reset() and kept the handle alive for re-use instead of destroying it. From the manpage of curl_easy_reset: It does not change the following information kept in the handle: live connections, the Session ID cache, the DNS cache, the cookies and shares. So if your connections somehow never time out (e.g., after the HTTP HEAD request sent by CurlGetSizeCmd or CurlIsNewerCmd), this could cause these problems. We could work around this by - Reducing the timeout: I don't think that would help because even with only a few seconds of timeout, your computer still can open new connections quicker than they will reach the timeout, triggering the problem. - Calling curl_easy_cleanup() instead of curl_easy_reset() every ~10 calls: Might defeat the original purpose of the change, which was enabling re-use of HTTP connections. The original question remains, though: Why aren't your connections closed, or re-used? -- Clemens Lang ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Troubles installing ports with Macports 2.3.1
On 2014-7-3 04:38 , Ryan Schmidt wrote: On Jul 2, 2014, at 2:25 AM, Joshua Root wrote: On Jul 1, 2014, at 4:58 AM, Joël Brogniart wrote: I suppose that, during the Computing dependencies for auto-multiple-choice phase, a lot of http requests are made to obtain port information and that these requests are not fully closed either by Macports or by the proxy. As this problem is recent (at least for me), it is perhaps related to a recent Java update (the proxy is a java application). During computing dependencies, no http requests would be made by MacPorts, as far as I know. To determine whether build dependencies are required, it must know whether an archive is available, and to find that out, it (usually) must query the packages server. Ok, but that would only be enough http requests to determine if an archive for the main port is available, right? So ideally 1 http request (in the case where the archive exists on the server it tried), or maybe a few requests (to check a few additional servers). It wouldn't be proportional to the number of dependencies. Dependency calculation is a recursive process. Dependencies can have dependencies of their own. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
PIL + ReportLab vs Pillow
Hi, Is there a way that I can have both PIL and Pillow installed at the same time? PIL 1.1.7 has a bug that affects my code, and the bug is fixed in Pillow. The py27-pil and py27-Pillow packages are mutually exclusive so I can't have them both installed from MacPorts. I also need ReportLab, but it has a dependency on PIL so I can't just replace PIL with Pillow. Also I am unable to install Pillow from PyPI using pip because it gives an error: error: invalid command 'egg_info' and I assume that may not work anyway, even it did install. Is there a way around this? I am using Macports 2.3.1 with everything up to date as of today, on OS X 10.8.5. Glenn ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Troubles installing ports with Macports 2.3.1
On Jul 2, 2014, at 2:25 AM, Joshua Root wrote: On Jul 1, 2014, at 4:58 AM, Jo?l Brogniart wrote: I suppose that, during the Computing dependencies for auto-multiple-choice phase, a lot of http requests are made to obtain port information and that these requests are not fully closed either by Macports or by the proxy. As this problem is recent (at least for me), it is perhaps related to a recent Java update (the proxy is a java application). During computing dependencies, no http requests would be made by MacPorts, as far as I know. To determine whether build dependencies are required, it must know whether an archive is available, and to find that out, it (usually) must query the packages server. Ok, but that would only be enough http requests to determine if an archive for the main port is available, right? So ideally 1 http request (in the case where the archive exists on the server it tried), or maybe a few requests (to check a few additional servers). It wouldn't be proportional to the number of dependencies. Here is what my proxy log show. -- 2014-06-30 10:09:02 [113] HEAD http://packages.macports.org/auto-multiple-choice/auto-multiple-choice-1.2.1_1%2Blatex.darwin_13.x86_64.tbz2 2014-06-30 10:09:04 [114] HEAD http://packages.macports.org/dblatex/dblatex-0.3.5_0%2Bpython27.darwin_13.noarch.tbz2 2014-06-30 10:09:04 [115] HEAD http://packages.macports.org/texlive-math-extra/texlive-math-extra-30747_0%2Bdoc.darwin_13.noarch.tbz2 2014-06-30 10:09:05 [116] HEAD http://packages.macports.org/texlive-latex/texlive-latex-30738_0%2Bdoc.darwin_13.noarch.tbz2 2014-06-30 10:09:05 [117] HEAD http://packages.macports.org/texlive-basic/texlive-basic-30847_0%2Bdoc.darwin_13.noarch.tbz2 2014-06-30 10:09:06 [118] HEAD http://packages.macports.org/texlive-common/texlive-common-2013_0.darwin_13.noarch.tbz2 2014-06-30 10:09:06 [119] HEAD http://packages.macports.org/texlive-bin/texlive-bin-2013_6%2Bx11.darwin_13.x86_64.tbz2 2014-06-30 10:09:07 [120] HEAD http://packages.macports.org/fontconfig/fontconfig-2.11.1_0.darwin_13.x86_64.tbz2 2014-06-30 10:09:07 [121] HEAD http://packages.macports.org/libiconv/libiconv-1.14_0.darwin_13.x86_64.tbz2 2014-06-30 10:09:07 [122] HEAD http://packages.macports.org/expat/expat-2.1.0_0.darwin_13.x86_64.tbz2 … 2014-06-30 10:10:45 [366] HEAD http://packages.macports.org/texlive-latex-extra/texlive-latex-extra-30788_0%2Bdoc.darwin_13.noarch.tbz2 2014-06-30 10:10:46 [367] HEAD http://packages.macports.org/texlive-pictures/texlive-pictures-30637_0%2Bdoc.darwin_13.noarch.tbz2 2014-06-30 10:45:16 [375] HEAD http://packages.macports.org/m4/m4-1.4.16_0.darwin_13.x86_64.tbz2 2014-06-30 10:45:20 [376] GET http://lil.fr.packages.macports.org/m4/m4-1.4.16_0.darwin_13.x86_64.tbz2 2014-06-30 10:45:21 [377] GET http://lil.fr.packages.macports.org/m4/m4-1.4.16_0.darwin_13.x86_64.tbz2.rmd160 -- The port install failed after the last GET. There are 256 lines of HEAD. Joël signature.asc Description: Message signed with OpenPGP using GPGMail ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Help with DYLD_LIBRARY_PATH
On Jul 2, 2014, at 3:04 PM, M-Rick m.rick@gmail.com wrote: I wanted to install SAGA GIS and forcing MacPorts to build over already existing libraries. I edited the macports.conf file and added this line but MacPorts doesn't seem to care about… Is this correct? extra_env DYLD_LIBRARY_PATH=/Library/Frameworks/GEOS.framework/Versions/Current/unix/lib:/Library/Frameworks/GDAL.framework/Versions/Current/unix/lib: /Library/Frameworks/PROJ.framework/Versions/Current/unix/lib:/Library/Frameworks/PROJ.framework/Versions/Current/unix/lib:/opt/lib It is almost always incorrect for a user to try to set the DYLD_LIBRARY_PATH variable to any value. Could you explain in more detail exactly what you're trying to accomplish? Then maybe we can suggest the correct solution. You mentioned SAGA GIS. Is this something available in MacPorts? If so, what is the port name, or, if it is not yet an official port, where can the portfile be found? Or is it something you're compiling manually? If so, how does this relate to MacPorts? Are you using MacPorts ports as dependencies? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: PIL + ReportLab vs Pillow
On Jul 2, 2014, at 9:53 PM, Glenn Ramsey wrote: Is there a way that I can have both PIL and Pillow installed at the same time? PIL 1.1.7 has a bug that affects my code, and the bug is fixed in Pillow. 1.1.7 appears to be the latest version of pil available. Have you reported the problem to the developers of pil already? Or is pil no longer being developed? The py27-pil and py27-Pillow packages are mutually exclusive so I can't have them both installed from MacPorts. You've answered your own question there: pil and pillow conflict (i.e. install the same files), so they cannot be installed at the same time -- for the same version of python, that is. You can't install py27-pil and py27-pillow at the same time. But you should be able to install e.g. py26-pil and py27-pillow at the same time, since they are for different python versions. I also need ReportLab, but it has a dependency on PIL so I can't just replace PIL with Pillow. To be exact, py27-reportlab depends on py27-pil, while py33-reportlab and py34-reportlab depend on py33-Pillow and py34-Pillow respectively, and py24-reportlab, py25-reportlab and py26-reportlab depend on neither pil nor pillow. So if using different versions of python is acceptable to you, you should be able to get all the software you want installed and activated at the same time. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
