Opened 12 years ago
Closed 12 years ago
#38677 closed defect (fixed)
atlas failing to index
Reported by: | beany_kelly@… | Owned by: | Veence (Vincent) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.3 |
Keywords: | Cc: | jdgleeson, cooljeanius (Eric Gallager), leighharr@…, sean@… | |
Port: | atlas |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Has atlas been removed from the ports database altogether?
I just uninstalled it because of encountering the problem described in this ticket: #37415
... and planned to reinstall it built against gcc45. But it's no longer available via port install, and it doesn't turn up in a port search of the MacPorts site. Which leaves me kind of stuck.
Attachments (1)
Change History (10)
comment:1 follow-up: 3 Changed 12 years ago by jdgleeson
comment:3 Changed 12 years ago by beany_kelly@…
Replying to jdgleeson@…:
Try running
sudo port selfupdate
. That worked for me, and could get you going while the root problem is being solved.
I did a selfupdate an hour or so ago, and it didn't help -- but now it does. Atlas is back in the ports list, even though it's still not visible on the web search (at time of writing).
I note that it's not available with +gcc45 or earlier, which may be an issue. I'm trying with gcc46 anyway.
comment:4 Changed 12 years ago by jmroot (Joshua Root)
Keywords: | arlas removed |
---|---|
Owner: | changed from macports-tickets@… to vince@… |
Summary: | atlas no longer in ports database? → atlas failing to index |
Changed 12 years ago by jmroot (Joshua Root)
Attachment: | Portfile.diff added |
---|
comment:5 Changed 12 years ago by jmroot (Joshua Root)
It's probably the unsafe use of sysctl causing this. See attached patch. I've fixed this more than once before, so please be careful not to reintroduce similar problems in future.
comment:7 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | leighharr@… added |
---|---|
Description: | modified (diff) |
Has duplicate #38698.
comment:9 Changed 12 years ago by jmroot (Joshua Root)
Resolution: | → fixed |
---|---|
Status: | new → closed |
r105083 (maintainer timeout)
Try running
sudo port selfupdate
. That worked for me, and could get you going while the root problem is being solved.