Errors from MacPorts SVN tree -- unable to sync
Hi, In my organization, we synchronize the MacPorts port tree over SVN due to corporate firewall restrictions that block rsync. A new user attempting to check out the ports tree for the first time started reporting this error: $ svn co http://svn.macports.org/repository/macports/trunk/dports svn: E175002: Server sent unexpected return value (413 Request Entity Too Large) in response to PROPFIND request for '/repository/macports/trunk/dports' I was not able to reproduce this error at first, but now I am getting this error: $ svn co http://svn.macports.org/repository/macports/trunk/dports svn: E175002: Server sent unexpected return value (413 Request Entity Too Large) in response to REPORT request for '/repository/macports/!svn/vcc/default' Is there something going on with the SVN server's configuration right now? Thank you. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Errors from MacPorts SVN tree -- unable to sync
(Sorry, forgot to reply-all last time). On Fri, May 31, 2013 at 2:16 PM, William Siegrist wsiegr...@apple.comwrote: We already disable those limits. I also cannot reproduce. -Bil Thank you for checking; I was able to get outside of our corporate network and checkout successfully. I suspect that our corporate transparent HTTP proxy is rejecting these requests based on some internal size limit before they get to your Apache server. Hilariously enough, our guest Wifi network does not have the same restriction. Oh well, guess it's time to support syncing the tree over Git or something. Thanks, Andrew ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
ports.tar.gz update interval?
Like many people, I use MacPorts from behind a restrictive firewall that blocks rsync. It's also somewhat slow, so to update my ports tree, I have this configuration in ports.conf: file:///Users/atodd/dev/macports/ports/ [default] and I execute a script that looks like this: #!/usr/bin/env bash set -e set -o pipefail set -u set -x cd ~/dev/macports/ rm -rf ports* wget http://www.macports.org/files/ports.tar.gz tar xzf ports.tar.gz sudo port upgrade outdated Running it daily this week, I have always gotten this message: Error: No ports matched the given expression (Typically I only run it once a week, but I'm not used to the lack of updates). Did everyone go on vacation this week, or is the tarball out of date? Thanks. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
emacs-snapshot failing to download
Tried last week and this morning. --- Fetching emacs-snapshot --- Attempting to fetch emacs-snapshot_20120403.orig.tar.xz from http://emacs.naquadah.org/unstable/ --- Attempting to fetch emacs-snapshot_20120403.orig.tar.xz from http://distfiles.macports.org/emacs-snapshot --- Attempting to fetch emacs-snapshot_20120403.orig.tar.xz from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/emacs-snapshot --- Attempting to fetch emacs-snapshot_20120403.orig.tar.xz from http://her.gr.distfiles.macports.org/mirrors/macports/mpdistfiles/emacs-snapshot --- Attempting to fetch emacs-snapshot_20120403.orig.tar.xz from http://jog.id.distfiles.macports.org/macports/mpdistfiles/emacs-snapshot --- Attempting to fetch emacs-snapshot_20120403.orig.tar.xz from http://lil.fr.distfiles.macports.org/emacs-snapshot --- Attempting to fetch emacs-snapshot_20120403.orig.tar.xz from http://sea.us.distfiles.macports.org/macports/mpdistfiles/emacs-snapshot --- Attempting to fetch emacs-snapshot_20120403.orig.tar.xz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/emacs-snapshot --- Attempting to fetch emacs-snapshot_20120403.orig.tar.xz from http://svn.macports.org/repository/macports/distfiles/emacs-snapshot Error: Target org.macports.fetch returned: fetch failed Log for emacs-snapshot is at: /opt/local/var/macports/logs/_Users_atodd_dev_macports_ports_editors_emacs-snapshot/emacs-snapshot/main.log Error: Unable to upgrade port: 1 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: emacs-snapshot +gtk+x11 failing to run
Thanks, working for me now. On Tue, Oct 25, 2011 at 6:57 AM, Ryan Schmidt ryandes...@macports.org wrote: On Oct 24, 2011, at 08:37, Andrew Todd wrote: After a recent port upgrade outdated, I am no longer able to run emacs-snapshot. $ emacs-snapshot dyld: Library not loaded: /opt/local/lib/libMagickWand.4.dylib Referenced from: /opt/local/bin/emacs-snapshot Reason: image not found Trace/BPT trap Any ideas? Thanks. Rebuild emacs-snapshot. https://trac.macports.org/ticket/31760 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
emacs-snapshot +gtk+x11 failing to run
After a recent port upgrade outdated, I am no longer able to run emacs-snapshot. $ emacs-snapshot dyld: Library not loaded: /opt/local/lib/libMagickWand.4.dylib Referenced from: /opt/local/bin/emacs-snapshot Reason: image not found Trace/BPT trap Any ideas? Thanks. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Forum?
On Tue, Oct 11, 2011 at 12:30 PM, Dominik Reichardt domi...@gmail.com wrote: Anyway, I'd prefer a forum, it probably could be done as the libSDL people have done it, that the forum and ML go to the same address (ML posts go to the forum, forum posts go to the ML). Honestly, I'd just like to see the ML configured so that the default reply-to address is the list email rather than the author's email. I prefer mailing lists because they push topics to me; these days with a GMail account it's very easy to filter messages into queues to read. For more forum-like browsing, Archives are available canonically at: http://lists.macosforge.org/pipermail/macports-users/ Not to mention MARC http://marc.info/?l=macports-usersr=1w=2 and probably a few other places. Maybe integrating with MarkMail would be a good idea, too. http://markmail.org/ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: MacPorts design (curiosity)
On Wed, Oct 5, 2011 at 2:17 PM, Richard L. Hamilton rlha...@smart.net wrote: Although a lot of package systems bear some similarities, I'm not aware of a Linux distro that's using the ports system like either FreeBSD/NetBSD or the Mac does, although I don't exactly go around comparing distros, so I might have missed it. But ports on FreeBSD originated somewhere around 1993 or 1994, which makes it older than most Linux distros except maybe Slackware. I guess that Gentoo's Portage system would be an example of a system that borrows from BSD ports, but that's another path to walk down. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Error: Unable to open port: invalid command name installs_libs
On Fri, Aug 12, 2011 at 5:49 PM, Ryan Schmidt ryandes...@macports.org wrote: I am surprised a force-quit was necessary. What was the last thing in the installer's log window when this occurred? Didn't know that there was an installer log. Makes me feel a little better about Macs (I'm coming from Linux) -- at least I know now I have a chance at diagnosing the problem: Aug 15 09:14:54 LM-BWI-00712218 installd[4041]: ./postflight: --- Updating MacPorts base sources using rsync After this, I can't quit the installer because the installer is busy. Presumably there's nothing else of importance in the postflight script after this that I'm missing? What happens on your network when using rsync? Does it just hang? That could explain the installer hanging. But I would have expected rsync to exit with an error code if a problem occurred. Unfortunately, whatever the network is doing to block rsync doesn't result in an error; the command-line process just hangs as well. Given that's the case, I guess there's not much you can do about it. But thanks for looking into it. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Error: Unable to open port: invalid command name installs_libs
On Fri, Aug 12, 2011 at 1:52 PM, Ryan Schmidt ryandes...@macports.org wrote: Correct, selfupdate always uses rsync. There is no setting to change this. MacPorts 2.0.x does not change this. You can use the 2.0.1 .dmg installer to upgrade your MacPorts. This will not adversely affect any ports you have installed. Thanks, I was able to upgrade using the installer. Although I should mention that the installer still hangs near the end and requires a force-quit just as it did with 1.9.2 -- I presume because of the rsync issue. I realize that this is an edge case, but it's not exactly friendly failure. We don't appear to cache the homepage at all on our end (it's being re-generated by PHP every time it's accessed) and we updated the homepage to list version 2.0.1 right after it came out, 10 days ago. As soon as I explicitly told Firefox to reload the page, it came up as 2.0.1. I'm not well-versed enough in browser caching to figure out why it happened, but I wonder if there's a cache-control headers issue. Anyway, it's working again, and now this email thread will show up in Google if anyone else runs into this problem. Thanks. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Error: Unable to open port: invalid command name installs_libs
Error: Unable to open port: invalid command name installs_libs I've been seeing this error on some (but not all) ports that I try to install, upgrade, or clean lately. Renameutils, for instance. Using MacPorts 1.9.2, the most recent version. Any ideas? Thanks. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
