Le 15 janv. 07 à 14:28, Mark Duling a écrit :
What I find curious is that it's not even attempting to download
from the
site defined in master_sites. If it did, it would find the gem
with no
problems.
On Jan 13, 2007, at 5:28 PM, Altoine Barker wrote:
I manually downloaded the files myself. I assumed that too many
people
were attempting to download the from the same sources and that is why
you and I get that error. You will get it for other gem files that
are
needed by mongrel as well. I downloaded those files manually,
also, and
put them in the folder that port was looking for locally on my
hard drive.
That is odd. I haven't been following this thread, but you should
file a
bug if you haven't. The maintainer, Paul, knows the port and
probably the
base ruby code involved as well and could get to the bottom of it
if he's
alerted to the problem.
This port depends on code available in HEAD that haven't been ported
to the release branch (and that basically uses ruby gem to download
files). Last time we talked about releasing a new version of
MacPorts, we were looking for the notes James wrote about this
upgrade process and that were lost with the darwinports to macports
transition.
Paul
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users
