View previous topic :: View next topic |
Author |
Message |
qvasic n00b
Joined: 08 Mar 2013 Posts: 4
|
Posted: Fri Mar 08, 2013 12:16 pm Post subject: emerge gentoo-sources results in block |
|
|
hi all!
i'm installing gentoo for the first time, got a problem with installing kernel:
Code: |
puppypc31420 portage # emerge gentoo-sources
Calculating dependencies... done!
[ebuild U ] sys-libs/zlib-1.2.7 [1.2.5.1-r2]
[ebuild N ] dev-libs/libgpg-error-1.10 USE="nls -common-lisp -static-libs"
[ebuild N ] dev-libs/libgcrypt-1.5.0-r2 USE="-static-libs"
[ebuild N ] dev-libs/libxslt-1.1.28 USE="crypt -debug -python -static-libs"
[ebuild N ] sys-kernel/gentoo-sources-3.7.10 USE="-build -deblob -symlink"
[ebuild N ] sys-apps/kmod-12-r1 USE="tools zlib -debug -doc -lzma -static-libs"
[uninstall ] sys-apps/module-init-tools-3.16-r1
[blocks b ] sys-apps/kmod ("sys-apps/kmod" is blocking sys-apps/module-init-tools-3.16-r1)
[blocks b ] sys-apps/module-init-tools ("sys-apps/module-init-tools" is blocking sys-apps/kmod-12-r1)
[ebuild U ] sys-fs/udev-197-r8 [171-r6] USE="acl%* kmod%* openrc%* -doc% -static-libs%"
[ebuild N ] virtual/udev-197-r1 USE="kmod -gudev -hwdb -introspection -keymap (-selinux) -static-libs"
[ebuild N ] sys-fs/udev-init-scripts-23
[blocks B ] <sys-apps/openrc-0.9.9 ("<sys-apps/openrc-0.9.9" is blocking sys-fs/udev-197-r8)
* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.
(sys-apps/openrc-0.9.8.4::gentoo, installed) pulled in by
sys-apps/openrc required by (sys-apps/baselayout-2.1-r1::gentoo, installed)
sys-apps/openrc required by (sys-fs/udev-init-scripts-23::gentoo, ebuild scheduled for merge)
(sys-fs/udev-197-r8::gentoo, ebuild scheduled for merge) pulled in by
>=sys-fs/udev-197-r8[kmod] required by (virtual/udev-197-r1::gentoo, ebuild scheduled for merge)
For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked
|
information provided in the url from above doesn't help a little.
do i understand correctly, that there is something wrong with USE variable?
thanks in advance! |
|
Back to top |
|
|
qvasic n00b
Joined: 08 Mar 2013 Posts: 4
|
Posted: Fri Mar 08, 2013 12:23 pm Post subject: |
|
|
to make question clearer:
1. how can i choose which one of conflicting packages to install?
2. how can i know, which one of those conflicting packages i should install, and which one is not that necessary? |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Fri Mar 08, 2013 3:31 pm Post subject: |
|
|
packages.gentoo.org has openrc-11.8 listed as stable for all arch's Code: | equery depends openrc | here yields Quote: | e
* These packages depend on openrc:
dev-db/mysql-init-scripts-2.0_pre1-r2 (sys-apps/openrc)
sys-apps/baselayout-2.1-r1 (sys-apps/openrc)
sys-fs/udev-init-scripts-23 (sys-apps/openrc)
| suggest try and if needed Code: | emerge --nodeps openrc
emerge openrc | read the news item concerning udev before upgrading udev _________________ Defund the FCC. |
|
Back to top |
|
|
depontius Advocate
Joined: 05 May 2004 Posts: 3509
|
Posted: Fri Mar 08, 2013 5:01 pm Post subject: |
|
|
This sounds like you're installing from a rather old stage3. Do you know what the date on it is?
Your problem here really isn't gentoo-sources - it's that the system is out-of-date and is trying to update itself as you try to install gentoo-sources. Most of the time bringing a system up to date with portage is really easy - most of the time. You're seeing one of those times when it's a little tougher than normal - the recent udev upgrade. Since you're new to Gentoo I would suggest starting over with a more recent stage3 tarball, if you can. A more recent stage3 will be past this particular upgrade already, and let you focus on following the installation instructions. You may need to pick a different mirror to get a newer stage3 tarball.
If that can't/doesn't work for you...
First off, not all blocks are the same, notice that some are "b" and one is 'B'. Portage is able to figure out that some blocks are temporary and will be resolved once the full set of packages is installed, so it will blow past the 'b' and just work. If the block is a 'B' then portage can't figure its way past, and needs help. In your particular case, I suspect something about gentoo-sources has triggered the need for udev-197, which required kmod and udev-init-scripts, and removing module-init-tools. Portage could handle all of this, except that your openrc is too old for your udev.
Try "emerge -atv openrc udev" and see what happens. If it Blocks with a 'B' and refuses to continue, post back here. I suspect that it will change the openrc/udev 'B' to a 'b' and continue. Once that's done, you should be able to emerge gentoo-sources. _________________ .sigs waste space and bandwidth |
|
Back to top |
|
|
qvasic n00b
Joined: 08 Mar 2013 Posts: 4
|
Posted: Fri Mar 08, 2013 5:11 pm Post subject: |
|
|
depontius wrote: | This sounds like you're installing from a rather old stage3. Do you know what the date on it is? |
tarball date is 25 september 2012. i have chosen it thinking "older - more stable", i guess that wasn't the case.
i'll try starting over with newer tarball, i'll write a feedback here later.
thanks. |
|
Back to top |
|
|
depontius Advocate
Joined: 05 May 2004 Posts: 3509
|
Posted: Fri Mar 08, 2013 5:55 pm Post subject: |
|
|
I made the change from udev-171 to udev-197 on Jan 26 of this year. You want something "comfortably newer" than that.
Really, when you're talking "stable Gentoo" there's usually no advantage to getting something older for stability's sake. There are occasional hiccups that may take as long as a week to get flushed out. But if you were to get an older release, you just might get one in the midst of such a hiccup.
When I install a new system, which I haven't done in over a year, but may do again in the next month or two, I just go for the newest stage3 that I easily find. _________________ .sigs waste space and bandwidth |
|
Back to top |
|
|
qvasic n00b
Joined: 08 Mar 2013 Posts: 4
|
Posted: Sat Mar 09, 2013 12:22 pm Post subject: |
|
|
i tried emerge openrc as proposed by donahue, it resulted in error:
Code: | make[1]: Leaving directory `/var/tmp/portage/sys-apps/openrc-0.11.8/work/openrc-0.11.8/runlevels'
install -d /var/tmp/portage/sys-apps/openrc-0.11.8/image///lib/rc/tmp
echo "0.11.8" > /var/tmp/portage/sys-apps/openrc-0.11.8/image///lib/rc/version
cp: cannot stat ‘/var/tmp/portage/sys-apps/openrc-0.11.8/image//etc/runlevels’: No such file or directory
* ERROR: sys-apps/openrc-0.11.8 failed (install phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 93: Called src_install
* environment, line 2828: Called die
* The specific snippet of code:
* cp -PR "${ED}"/etc/runlevels "${ED}"/usr/share/${PN} || die;
*
* If you need support, post the output of `emerge --info '=sys-apps/openrc-0.11.8'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/openrc-0.11.8'`.
* The complete build log is located at '/var/tmp/portage/sys-apps/openrc-0.11.8/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/openrc-0.11.8/temp/environment'.
* Working directory: '/var/tmp/portage/sys-apps/openrc-0.11.8/work/openrc-0.11.8'
* S: '/var/tmp/portage/sys-apps/openrc-0.11.8/work/openrc-0.11.8'
>>> Failed to emerge sys-apps/openrc-0.11.8, Log file:
>>> '/var/tmp/portage/sys-apps/openrc-0.11.8/temp/build.log'
* Messages for package sys-apps/openrc-0.11.8:
* ERROR: sys-apps/openrc-0.11.8 failed (install phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 93: Called src_install
* environment, line 2828: Called die
* The specific snippet of code:
* cp -PR "${ED}"/etc/runlevels "${ED}"/usr/share/${PN} || die;
*
* If you need support, post the output of `emerge --info '=sys-apps/openrc-0.11.8'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/openrc-0.11.8'`.
* The complete build log is located at '/var/tmp/portage/sys-apps/openrc-0.11.8/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/openrc-0.11.8/temp/environment'.
* Working directory: '/var/tmp/portage/sys-apps/openrc-0.11.8/work/openrc-0.11.8'
* S: '/var/tmp/portage/sys-apps/openrc-0.11.8/work/openrc-0.11.8'
* GNU info directory index is up-to-date.
|
i'll try newer stage3 tarball now. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|