View previous topic :: View next topic |
Author |
Message |
natrix Guru
Joined: 23 Aug 2013 Posts: 556
|
Posted: Tue Aug 27, 2013 11:18 pm Post subject: Issues with emerge @world |
|
|
Hello!!
I have this problem:
The sentences show this:
emerge --update --deep @world
http://pastebin.com/eK5bKbnx
This "bad script" begin to show after of run "emerge virtualbox" but virtualbox compile failed.
What is the problem?
Thank!!!! |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9653 Location: almost Mile High in the USA
|
Posted: Wed Aug 28, 2013 12:09 am Post subject: |
|
|
It looks like you broadly unmasked unstable versions of everything. This can cause a lot of pain as you can see. You should mark unstables for only packages you want instead of everything.
The two things that portage are complaining about:
1. mercurial has a circular dependency. If you don't need it, could you remove the keyword unmask for gvim and see if it works then? I haven't tracked down the circle but easier to just not use the 9999 version of gvim.
2. version conflict for libpng. Could you stop the newer version of ghostscript-gpl from emerging for now, I think jbig2dec has a ebuild bug if I'm not mistaken... _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
natrix Guru
Joined: 23 Aug 2013 Posts: 556
|
|
Back to top |
|
|
jburns Veteran
Joined: 18 Jan 2007 Posts: 1213 Location: Massachusetts USA
|
Posted: Wed Aug 28, 2013 3:20 am Post subject: |
|
|
You cannot emerge dev-vcs/mercurial-9999 as a new package. You need to install a normal version of dev-vcs/mercurial and then update it to dev-vcs/mercurial-9999.
dev-vcs/mercurial-9999 uses mercurial to get the source files. |
|
Back to top |
|
|
natrix Guru
Joined: 23 Aug 2013 Posts: 556
|
Posted: Wed Aug 28, 2013 5:23 pm Post subject: |
|
|
Solved!!!
Thank a lot!!! |
|
Back to top |
|
|
|