problems installing rb-daemons
I'm trying to install rb-mongrel (via MacPorts on OSX 10.4.8), but one of the dependencies is failing - namely rb-daemons. The following is what i'm receiving from the command-line when trying to install rb-daemons on it's own;
$ sudo port install rb-daemons ---> Fetching rb-daemons ---> Attempting to fetch daemons-1.0.3.gem from http://distfiles-od.opendarwin.org/ruby ---> Attempting to fetch daemons-1.0.3.gem from http://distfiles-msn.opendarwin.org/ruby ---> Attempting to fetch daemons-1.0.3.gem from http://distfiles-bay13.opendarwin.org/ruby ---> Attempting to fetch daemons-1.0.3.gem from http://distfiles-od.opendarwin.org/ ---> Attempting to fetch daemons-1.0.3.gem from http://distfiles-msn.opendarwin.org/ ---> Attempting to fetch daemons-1.0.3.gem from http://distfiles-bay13.opendarwin.org/ Error: Target com.apple.fetch returned: fetch failed Error: Status 1 encountered during processing.
After reading man port, I guessed the port list may be out of date, so I ran sudo port sync, but am still having the same issue. Any help/suggestions would be greatly appreciated, as I'd rather avoid using gem to install it (I gather from reading other posts on the mailing list that mixing port installs with gem installs is something that should be avoided). Thanks, Cam
Actually, it appears 1.0.3 is the current version of the daemons library. The problem, it appears, is the livecheck.regex in the ruby group. It doesn't match anything on the daemons project page. I'm wondering if perhaps RubyForge changed slightly? I'll look into this further Incidentally, I always install ruby libraries using gem. I install ruby via MacPorts, then rb-rubygems. Everything else I install via gem, or by hand. I find this to be very clean - if I have a third- party ruby library installed, it's not being managed by MacPorts. And since gem can update itself, I don't have to worry about updating it via MacPorts. If you were to install some things via MacPorts and some via gem I'd say that's a problem. But if you're avoiding that, then that's fine. On Jan 11, 2007, at 12:14 PM, Cameron Yule wrote:
I'm trying to install rb-mongrel (via MacPorts on OSX 10.4.8), but one of the dependencies is failing - namely rb-daemons.
The following is what i'm receiving from the command-line when trying to install rb-daemons on it's own;
$ sudo port install rb-daemons ---> Fetching rb-daemons ---> Attempting to fetch daemons-1.0.3.gem from http://distfiles- od.opendarwin.org/ruby ---> Attempting to fetch daemons-1.0.3.gem from http://distfiles- msn.opendarwin.org/ruby ---> Attempting to fetch daemons-1.0.3.gem from http://distfiles- bay13.opendarwin.org/ruby ---> Attempting to fetch daemons-1.0.3.gem from http://distfiles- od.opendarwin.org/ ---> Attempting to fetch daemons-1.0.3.gem from http://distfiles- msn.opendarwin.org/ ---> Attempting to fetch daemons-1.0.3.gem from http://distfiles- bay13.opendarwin.org/ Error: Target com.apple.fetch returned: fetch failed Error: Status 1 encountered during processing.
After reading man port, I guessed the port list may be out of date, so I ran sudo port sync, but am still having the same issue.
Any help/suggestions would be greatly appreciated, as I'd rather avoid using gem to install it (I gather from reading other posts on the mailing list that mixing port installs with gem installs is something that should be avoided).
-- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com
Actually, I take it back. While I firmly believe this is a problem, when I do a port fetch rb-daemons myself, it's not even triggering the livecheck (passing the -d switch should show you if it does). So I'm really not sure why it's bypassing gem. On Jan 11, 2007, at 5:41 PM, Kevin Ballard wrote:
The problem, it appears, is the livecheck.regex in the ruby group. It doesn't match anything on the daemons project page. I'm wondering if perhaps RubyForge changed slightly? I'll look into this further
-- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com
Bah, I keep hitting send and then immediately finding more info. Regarding livecheck, I'd never heard of it before. I'm guessing right now that it's an action you have to trigger manually? And actually, trying to do so gives an error regarding master_sites. In any case, the problem it seems is that it's immediately trying to fetch the gem file from a mirror rather than from the master site. This is kinda weird. I would not expect gem files to be mirrored like regular downloads are. So that's the problem. On Jan 11, 2007, at 5:51 PM, Kevin Ballard wrote:
Actually, I take it back. While I firmly believe this is a problem, when I do a port fetch rb-daemons myself, it's not even triggering the livecheck (passing the -d switch should show you if it does). So I'm really not sure why it's bypassing gem.
-- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com
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. HTH Altoine Cameron Yule wrote:
I'm trying to install rb-mongrel (via MacPorts on OSX 10.4.8), but one of the dependencies is failing - namely rb-daemons.
The following is what i'm receiving from the command-line when trying to install rb-daemons on it's own;
$ sudo port install rb-daemons ---> Fetching rb-daemons ---> Attempting to fetch daemons-1.0.3.gem from http://distfiles-od.opendarwin.org/ruby ---> Attempting to fetch daemons-1.0.3.gem from http://distfiles-msn.opendarwin.org/ruby ---> Attempting to fetch daemons-1.0.3.gem from http://distfiles-bay13.opendarwin.org/ruby ---> Attempting to fetch daemons-1.0.3.gem from http://distfiles-od.opendarwin.org/ ---> Attempting to fetch daemons-1.0.3.gem from http://distfiles-msn.opendarwin.org/ ---> Attempting to fetch daemons-1.0.3.gem from http://distfiles-bay13.opendarwin.org/ Error: Target com.apple.fetch returned: fetch failed Error: Status 1 encountered during processing.
After reading man port, I guessed the port list may be out of date, so I ran sudo port sync, but am still having the same issue.
Any help/suggestions would be greatly appreciated, as I'd rather avoid using gem to install it (I gather from reading other posts on the mailing list that mixing port installs with gem installs is something that should be avoided).
Thanks,
Cam
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
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.
-- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com
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. Mark
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
Ahh, that explains why I couldn't figure out the problem when inspecting the code for MacPorts - I was looking at HEAD, not at the release version I had installed. On Jan 15, 2007, at 12:31 AM, Paul Guyot wrote:
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.
-- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com
FYI, the changeset is the following: http://trac.macports.org/projects/macports/changeset/20544 Paul Le 15 janv. 07 à 14:35, Kevin Ballard a écrit :
Ahh, that explains why I couldn't figure out the problem when inspecting the code for MacPorts - I was looking at HEAD, not at the release version I had installed.
On Jan 15, 2007, at 12:31 AM, Paul Guyot wrote:
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.
participants (5)
-
Altoine Barker
-
Cameron Yule
-
Kevin Ballard
-
Mark Duling
-
Paul Guyot