View previous topic :: View next topic |
Author |
Message |
Grahammm Tux's lil' helper
Joined: 01 Sep 2004 Posts: 84 Location: Berkshire UK
|
Posted: Tue May 10, 2005 9:58 pm Post subject: 2005.0 Stage1-stage2 emerge -e system gets merge order wrong |
|
|
I am currently performing a 2005.0 Stage 1 install on ~x86. After a succesful bootstrap, 'emerge -e system' is getting the dependency order wrong. The first 'failure' was when merging openssl, which complained that perl was not available. Then later, automake-1.8.5 failed because autoconf-2.58 or later was required. 'emerge =sys/devel/automake-1.8.5-r3' brought in the requred dependencies. |
|
Back to top |
|
|
Master Shake l33t
Joined: 10 Apr 2005 Posts: 755 Location: Wilmington, Delaware
|
Posted: Tue May 10, 2005 10:39 pm Post subject: |
|
|
Yeah it does that....It might be a bug in portage. _________________ System Specs:
64-bit gentoo linux
Q6600 @ 3.2Ghz
P35 Chipset
4 Gigs 800mhz 4-4-4-12
Nvidia GeForce 8800 GTX @ 630mhz |
|
Back to top |
|
|
xhixen n00b
Joined: 20 Apr 2005 Posts: 1
|
Posted: Wed May 11, 2005 6:27 am Post subject: Re: 2005.0 Stage1-stage2 emerge -e system gets merge order w |
|
|
Grahammm wrote: | I am currently performing a 2005.0 Stage 1 install on ~x86. After a succesful bootstrap, 'emerge -e system' is getting the dependency order wrong. The first 'failure' was when merging openssl, which complained that perl was not available. Then later, automake-1.8.5 failed because autoconf-2.58 or later was required. 'emerge =sys/devel/automake-1.8.5-r3' brought in the requred dependencies. |
I just wanted to bump this up and say that I'm having the exact same issue. |
|
Back to top |
|
|
Karsten from Berlin Guru
Joined: 28 Feb 2004 Posts: 446 Location: Berlin/Germany
|
Posted: Wed May 11, 2005 12:32 pm Post subject: |
|
|
My opinion is, that it is not recommended to try a stage<whatever>-install with completely unstable packages.
Maybe do the basic installing 'till the first boot with stable. After that try to set the ACCEPT_KEYWORDS in make.conf to upgrade to unstable packages.
If s.th. breaks always remember: There must be a reason that it is marked as unstable... maybe you found out why _________________ Heaven: The police are British, the chefs Italian, the mechanics German, the lovers French and it's organized by the Swiss.
Hell: The police are German, the chefs British, the mechanics French, the lovers Swiss and it's organized by the Italians. |
|
Back to top |
|
|
cyrillic Watchman
Joined: 19 Feb 2003 Posts: 7313 Location: Groton, Massachusetts USA
|
Posted: Wed May 11, 2005 1:59 pm Post subject: |
|
|
Master Shake wrote: | Yeah it does that....It might be a bug in portage. |
Actually, I think it is a bug in the documentation.
When I do a stage1 installation with ~x86, I use "emerge system" not "emerge -e system" after bootstrapping. |
|
Back to top |
|
|
stoker n00b
Joined: 13 May 2005 Posts: 28 Location: Williston, Vermont
|
Posted: Thu May 19, 2005 3:27 am Post subject: Re: 2005.0 Stage1-stage2 emerge -e system gets merge order w |
|
|
Grahammm wrote: | I am currently performing a 2005.0 Stage 1 install on ~x86. After a succesful bootstrap, 'emerge -e system' is getting the dependency order wrong. The first 'failure' was when merging openssl, which complained that perl was not available. Then later, automake-1.8.5 failed because autoconf-2.58 or later was required. 'emerge =sys/devel/automake-1.8.5-r3' brought in the requred dependencies. |
out of curiosity, how did you resolve your issue with openssl and perl? I've been banging my head against a wall all day trying to figure this one out. nothing seems to work right.
thanks - _________________ Check out my current Gentoo and FreeBSD projects at http://www.mattstorer.net |
|
Back to top |
|
|
xante Apprentice
Joined: 23 Aug 2004 Posts: 229
|
Posted: Thu May 19, 2005 5:19 am Post subject: |
|
|
stoker:
Until it breaks than
Code: | USE="-berkdb" emerge perl && emerge system && emerge -e system |
But now I'm having problems with alsa-drivers when doing "emerge system". Not to knock Gentoo scripters, but maybe we should rethink the new install...Im having more problems with this than I ever have, usually gentoo installs nicely my AMD Desktop...but this round, Ive had to resort to the gentoo forums over:
emerging perl
adding -svga to my use flags
and now im stuck on the alsa-driver issue...Could we combine the multiple problemed install forums into a new manual or something?
Happy gentooing (btw, out of all the distros Ive tried, gentoo is my lover, Im also running it on a compaq presario 3000 with all operations set to go ) |
|
Back to top |
|
|
cyrillic Watchman
Joined: 19 Feb 2003 Posts: 7313 Location: Groton, Massachusetts USA
|
Posted: Thu May 19, 2005 5:42 pm Post subject: |
|
|
xante wrote: | But now I'm having problems with alsa-drivers when doing "emerge system". Not to knock Gentoo scripters, but maybe we should rethink the new install...Im having more problems with this than I ever have, usually gentoo installs nicely my AMD Desktop...but this round, Ive had to resort to the gentoo forums over:
emerging perl
adding -svga to my use flags
and now im stuck on the alsa-driver issue... |
It sounds like you have added a bunch of USE flags before even getting the base system installed. This generally causes problems by pulling in unwanted dependencies. When I do a stage1 install, I bootstrap and emerge system with only USE="" or USE="nptl", nothing more. Then I boot my new installation before adding other USE flags and emerging the rest of the packages I want.
ps. alsa-driver is included in 2.6 kernels, so you don't need to emerge it (unless you are still running a 2.4 kernel). |
|
Back to top |
|
|
stoker n00b
Joined: 13 May 2005 Posts: 28 Location: Williston, Vermont
|
Posted: Thu May 19, 2005 7:09 pm Post subject: |
|
|
xante wrote: |
Could we combine the multiple problemed install forums into a new manual or something?
Happy gentooing (btw, out of all the distros Ive tried, gentoo is my lover, Im also running it on a compaq presario 3000 with all operations set to go ) |
yeah, no kidding. I broke down last night and performed a stage3 on my lappy, figured the precompiled binaries will be tight enough for a base system, and I can reemerge the system with my desired USE flags at a later date. but just to get through dependency hell. it would be very nice to know what specifically NOT to do during an install to cause these kinds of problems.
I guess (e.g.) the OpenSSL / Perl cyclic dependency issue is a long-standing one. my question to any portage developers who might read this thread: why has this not been resovled yet? every problem has a solution.
cyrillic wrote: | It sounds like you have added a bunch of USE flags before even getting the base system installed. This generally causes problems by pulling in unwanted dependencies. |
I can see that... I was perhaps a bit overzealous with my use of the flags, so that wouldn't surprise me... but still - something ought to be mentioned in the install docs, then, as to which USE flags may be used during an install, and which ones SHOULD NOT be used. if USE flags are the cause, that is. I haven't tried rebuilding the system from a stage1 without any USE flags, so I wouldn't know, but I'll take your word for it. _________________ Check out my current Gentoo and FreeBSD projects at http://www.mattstorer.net |
|
Back to top |
|
|
xante Apprentice
Joined: 23 Aug 2004 Posts: 229
|
Posted: Thu May 19, 2005 9:22 pm Post subject: |
|
|
Yeah, I did just copy an old make.conf over not realizing this I guess maybe I should of been more awake when installing but they do still say to set your use flags before bootstrapping...maybe this should be updated in the install manual like stoker suggested. |
|
Back to top |
|
|
|