View previous topic :: View next topic |
Author |
Message |
ddc Guru
Joined: 29 Aug 2006 Posts: 522
|
Posted: Mon Feb 05, 2007 10:45 am Post subject: Updating Portage cache Cannot resolve a virtual pack |
|
|
Quote: | alluminium:~ root# emerge --sync
Updating Portage cache ....
Number of files: 144478
Number of files transferred: 492
Total file size: 159377144 bytes
Total transferred file size: 1745712 bytes
Literal data: 1745712 bytes
Matched data: 0 bytes
File list size: 3267059
Total bytes sent: 9989
Total bytes received: 5035583
sent 9989 bytes received 5035583 bytes 35160.78 bytes/sec
total size is 159377144 speedup is 31.59
>>> Updating Portage cache... \!!! Cannot resolve a virtual package name to an ebuild.
!!! This is a bug, please report it. (virtual/ghostscript-0)
|
emerge --sync
>>> Updating Portage cache... \!!! Cannot resolve a virtual package name to an ebuild.
!!! This is a bug, please report it. (virtual/ghostscript-0)
how to solve ? |
|
Back to top |
|
|
DavidJN n00b
Joined: 20 Jan 2005 Posts: 23
|
|
Back to top |
|
|
ddc Guru
Joined: 29 Aug 2006 Posts: 522
|
Posted: Tue Feb 06, 2007 7:46 am Post subject: |
|
|
i did, but the answare was: the emerge support to macosX portage is discontinuos
so, this is the reason why i post here: help to solve
does anybody use emerge ?
i know fink and macports are better working |
|
Back to top |
|
|
darthbator n00b
Joined: 07 Feb 2007 Posts: 9 Location: North Hollywood CA
|
Posted: Wed Feb 07, 2007 10:37 pm Post subject: |
|
|
it appears that portage for OS X is no longer available the way it was currently it appears that a bootstrap prefix version must now be installed to get portage to work. |
|
Back to top |
|
|
|