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 <[email protected]> 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 <[email protected]> > 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 [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
