#15676 closed defect (fixed)
port install error rb-rubygems -- can't read "categories"
Reported by: | stevemid@… | Owned by: | mr_bond@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.6.0 |
Keywords: | Cc: | ||
Port: |
Description
I received the following error message attempting to install rb-rubygems:
Steve$ sudo port install rb-rubygems rb-termios Password: ---> Fetching rb-rubygems ---> Verifying checksum(s) for rb-rubygems ---> Extracting rb-rubygems ---> Applying patches to rb-rubygems ---> Configuring rb-rubygems ---> Building rb-rubygems with target all ---> Staging rb-rubygems into destroot ---> Installing rb-rubygems 1.1.1_2 Error: Target org.macports.install returned: can't read "categories": no such variable Error: Status 1 encountered during processing.
In spite of much experimentation, including wiping /opt/local completely on my development machine and deleting the files recommended in the macports wiki for an absolutely clean install, I keep receiving the same error. This, after my latest install attempt
Steve$ sudo port install rb-rubygems Password: ---> Fetching rb-rubygems ---> Attempting to fetch rubygems-1.1.1.tgz from http://rubyforge.org/frs/download.php/35283/ ---> Verifying checksum(s) for rb-rubygems ---> Extracting rb-rubygems ---> Applying patches to rb-rubygems ---> Configuring rb-rubygems ---> Building rb-rubygems with target all ---> Staging rb-rubygems into destroot ---> Installing rb-rubygems 1.1.1_2 Error: Target org.macports.install returned: can't read "categories": no such variable Error: Status 1 encountered during processing.
Is changeset 37668 related to this? "contains Message: Fixed categories"
I am stumped and would greatly appreciate any assistance.
Change History (3)
comment:1 Changed 16 years ago by jmroot (Joshua Root)
Milestone: | MacPorts 1.6.1 → Port Bugs |
---|---|
Owner: | changed from macports-tickets@… to mr_bond@… |
comment:2 Changed 16 years ago by mr_bond@…
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Fixed in r37668