Opened 14 years ago
Closed 14 years ago
#25848 closed defect (invalid)
Error: Port rubygems not found
Reported by: | junhui.liao@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.1 |
Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt), mr_bond@… | |
Port: | rb-rubygems |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Hi, my Mac has such a error when do the command. "sudo port install ruby19 rubygems".
OS, 10.5.8.
Xcoder, 314-2809.
Thanks a lot in advance!
wifi-secure1-63:~ junhuiliao$ sudo port install ruby19 rubygems ---> Computing dependencies for ruby19 ---> Dependencies to be installed: libiconv gperf ncurses ncursesw openssl zlib readline ---> Fetching gperf ---> Attempting to fetch gperf-3.0.4.tar.gz from http://lil.fr.distfiles.macports.org/gperf ---> Verifying checksum(s) for gperf ---> Extracting gperf ---> Configuring gperf ---> Building gperf ---> Staging gperf into destroot ---> Installing gperf @3.0.4_0 ---> Activating gperf @3.0.4_0 ---> Cleaning gperf ---> Fetching libiconv ---> Attempting to fetch libiconv-1.13.1.tar.gz from http://lil.fr.distfiles.macports.org/libiconv ---> Verifying checksum(s) for libiconv ---> Extracting libiconv ---> Applying patches to libiconv ---> Configuring libiconv ---> Building libiconv ---> Staging libiconv into destroot ---> Installing libiconv @1.13.1_0 ---> Activating libiconv @1.13.1_0 ---> Cleaning libiconv ---> Fetching ncursesw ---> Attempting to fetch ncurses-5.7.tar.gz from http://mirrors.kernel.org/gnu/ncurses ---> Verifying checksum(s) for ncursesw ---> Extracting ncursesw ---> Configuring ncursesw ---> Building ncursesw ---> Staging ncursesw into destroot ---> Installing ncursesw @5.7_0 ---> Activating ncursesw @5.7_0 ---> Cleaning ncursesw ---> Fetching ncurses ---> Verifying checksum(s) for ncurses ---> Extracting ncurses ---> Configuring ncurses ---> Building ncurses ---> Staging ncurses into destroot ---> Installing ncurses @5.7_0 ---> Activating ncurses @5.7_0 ---> Cleaning ncurses ---> Fetching zlib ---> Attempting to fetch zlib-1.2.5.tar.bz2 from http://lil.fr.distfiles.macports.org/zlib ---> Verifying checksum(s) for zlib ---> Extracting zlib ---> Applying patches to zlib ---> Configuring zlib ---> Building zlib ---> Staging zlib into destroot ---> Installing zlib @1.2.5_0 ---> Activating zlib @1.2.5_0 ---> Cleaning zlib ---> Fetching openssl ---> Attempting to fetch openssl-1.0.0a.tar.gz from http://lil.fr.distfiles.macports.org/openssl ---> Verifying checksum(s) for openssl ---> Extracting openssl ---> Applying patches to openssl ---> Configuring openssl ---> Building openssl ---> Staging openssl into destroot ---> Installing openssl @1.0.0a_0 ---> Activating openssl @1.0.0a_0 ---> Cleaning openssl ---> Fetching readline ---> Attempting to fetch readline-6.1.tar.gz from http://lil.fr.distfiles.macports.org/readline ---> Verifying checksum(s) for readline ---> Extracting readline ---> Applying patches to readline ---> Configuring readline ---> Building readline ---> Staging readline into destroot ---> Installing readline @6.1.000_1 ---> Activating readline @6.1.000_1 ---> Cleaning readline ---> Fetching ruby19 ---> Attempting to fetch ruby-1.9.1-p429.tar.bz2 from ftp://ftp.easynet.be/ruby/ruby/1.9 ---> Verifying checksum(s) for ruby19 ---> Extracting ruby19 ---> Applying patches to ruby19 ---> Configuring ruby19 ---> Building ruby19 ---> Staging ruby19 into destroot ---> Installing ruby19 @1.9.1-p429_1 ---> Activating ruby19 @1.9.1-p429_1 ---> Cleaning ruby19 Error: Port rubygems not found
Change History (2)
comment:1 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… mr_bond@… added |
---|---|
Description: | modified (diff) |
Port: | rb-rubygems added; rubygems removed |
comment:2 Changed 14 years ago by jmroot (Joshua Root)
Keywords: | Leopard removed |
---|---|
Resolution: | → invalid |
Status: | new → closed |
Type: | update → defect |
Note: See
TracTickets for help on using
tickets.
Please remember to use WikiFormatting so that your posts are legible.
The message you received is correct: there is no port called "rubygems". "port search rubygems" leads me to understand there is a port called "rb-rubygems", however. Perhaps that is what you were looking for?