Possible corrupt PortIndex file for rsync...
I received this warning from out of the blue when doing an install of a port: 'Warning: It looks like your PortIndex file for rsync:// rsync.macports.org/release/tarballs/ports.tar may be corrupt.' I've never gotten this warning before, and now I am unable to install certain ports. How do I find out if it is, in fact corrupt and how to fix it? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Possible corrupt PortIndex file for rsync...
Let me clarify a bit...I don't know if this possible corruption issue is in any way connected to the fact I can't install a certain port. I was trying to install bashdb 4.2 to complement my bash 4.3 install from macports and there was an error in configuring the port...which when consulting the log for the configuration, revealed a warning that I was using bash 4.3...so there is possibly a version mismatch between bashdb 4.2 and bash 4.3... In short what I asked about the possibility of my PortIndex file being corrupt still stands as my question, I just don't know whether if it is connected at all to this specific issue of my installing this particular port. That said, I'd still like to know how to find out if there is some corruption issue with my PortIndex. On Fri, Mar 20, 2015 at 7:44 PM, Carlo Tambuatco oraclmas...@gmail.com wrote: I received this warning from out of the blue when doing an install of a port: 'Warning: It looks like your PortIndex file for rsync:// rsync.macports.org/release/tarballs/ports.tar may be corrupt.' I've never gotten this warning before, and now I am unable to install certain ports. How do I find out if it is, in fact corrupt and how to fix it? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
mod_unique_id: unable to find IPv4 address
Installed MacPorts for the first time, then installed apache2. When I run sudo port load apache2, an httpd process starts up, and even responds to requests (to http://localhost) if I get them in fast enough. But then the process exits (whether or not it received any requests). The error log shows this: [Fri Mar 20 11:40:41 2015] [warn] Init: Session Cache is not configured [hint: SSLSessionCache] [Fri Mar 20 11:40:46 2015] [alert] (EAI 8)nodename nor servname provided, or not known: mod_unique_id: unable to find IPv4 address of iMac.local Configuration Failed I’ve searched the archives of this list and I see several references to similar problems, but no resolutions. Any help would be appreciated! My computer: iMac (27-inch, Mid 2010), 4 GB OS X 10.10.2 Yosemite FWIW, I added a ServerName directive to /opt/local/apache2/conf/httpd.conf: # # ServerName gives the name and port that the server uses to identify itself. # This can often be determined automatically, but we recommend you specify # it explicitly to prevent problems during startup. # # If your host doesn't have a registered DNS name, enter its IP address here. # #ServerName www.example.com:80 ServerName localhost:80 and my /etc/hosts file contains ## # Host Database # # localhost is used to configure the loopback interface # when the system is booting. Do not change this entry. ## 127.0.0.1 localhost 255.255.255.255 broadcasthost ::1 localhost ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Possible corrupt PortIndex file for rsync...
Sorry, I hate sounding like I'm answering my own questions, but I did a selfupdate and I think that fixed the PortIndex issue...? My sources.conf uses the default rsync://rsync.macports.org/release/tarballs/ports.tar so I did a self update and that should fix the corruption issue, right? So I guess the only question I have left is about the bashdb thing mentioned previously. On Fri, Mar 20, 2015 at 7:50 PM, Carlo Tambuatco oraclmas...@gmail.com wrote: Let me clarify a bit...I don't know if this possible corruption issue is in any way connected to the fact I can't install a certain port. I was trying to install bashdb 4.2 to complement my bash 4.3 install from macports and there was an error in configuring the port...which when consulting the log for the configuration, revealed a warning that I was using bash 4.3...so there is possibly a version mismatch between bashdb 4.2 and bash 4.3... In short what I asked about the possibility of my PortIndex file being corrupt still stands as my question, I just don't know whether if it is connected at all to this specific issue of my installing this particular port. That said, I'd still like to know how to find out if there is some corruption issue with my PortIndex. On Fri, Mar 20, 2015 at 7:44 PM, Carlo Tambuatco oraclmas...@gmail.com wrote: I received this warning from out of the blue when doing an install of a port: 'Warning: It looks like your PortIndex file for rsync:// rsync.macports.org/release/tarballs/ports.tar may be corrupt.' I've never gotten this warning before, and now I am unable to install certain ports. How do I find out if it is, in fact corrupt and how to fix it? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Am I supposed to use gem from MacPorts to install ruby packages in /opt/local/lib/ruby2.2/gems/2.2.0?
Hi, If I use gem to install ruby packages, they will be installed in /opt/local/lib/ruby2.2/gems/2.2.0 by default. But I guess ruby packages installed by MacPorts will also use this directory. So this may cause some problem, is it so? If so, what is the recommended way to install ruby packages via gem? Thanks. -- Regards, Peng ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
about Qt 5.x and OS X 10.6
Hello, As you know I've been investing quite a bit of work in bringing Qt 5.4.x to MacPorts, and to make Qt 5 co-installable with Qt 4. In fact, I started with the latter, and then moved on to the former. And in that 2nd step I completely forgot that Qt 5.4.x no longer build on OS X 10.6 (and earlier). I don't like the idea of holding off on Qt 5.4 for the sake of SL (much as I love it), nor do I like the idea of dropping Qt 5 support for SL (because I love it too much for that :)) So I am now exploring an option that may be a bit unusual: OS-specific port versions. Nothing as fancy as it seems: for OS X 10.6 users port:qt5-mac-devel will appear to be at 5.3.2 and for all other users it will appear to be at 5.4.x . I'm posting this on macports-users (instead of ~-dev) to see if 1) this is a viable and acceptable approach (for the core devs) and 2) an appreciated approach (for the users). I'm aware that this could set precedence, because it might well be that Qt 5.5 will no longer build on OS X 10.7 (and 5.6 on 10.8 and so forth). As far as I'm concerned this approach allows me to centralise portfile development and maintenance in a single file. I foresee to re-evaluate the situation when Qt 5.5 is released; if necessary I'll create a qt53-mac port for SL and move Qt 5.4.x to the legacy fallback code in the qt5-mac port, but that's not the only option to keep the main portfile complexity in check. Thanks, R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
