Summary: | sys-apps/openrc-0.4.3-r3: timestamp offseted by 1 day and 2 hrs | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Mokrejš <mmokrejs> |
Component: | [OLD] baselayout | Assignee: | Roy Marples <roy> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | base-system |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin Mokrejš
2009-09-16 20:50:21 UTC
*** This bug has been marked as a duplicate of bug 142850 *** # cat /etc/conf.d/clock cat: /etc/conf.d/clock: No such file or directory # I think this file went away with migration from baselayout-1 to -2. # emerge -pv e2fsprogs These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-fs/e2fsprogs-1.41.9 USE="nls" 0 kB [cut] # cat /etc/e2fsck.conf cat: /etc/e2fsck.conf: No such file or directory # I will play more with this and report back. >>> Emerging (4 of 20) dev-python/setuptools-0.6.3-r2 * distribute-0.6.3.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * * ERROR: dev-python/setuptools-0.6.3-r2 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * setuptools-0.6.3-r2.ebuild, line 30: Called die * The specific snippet of code: * die "<dev-python/setuptools-0.6.3-r2 must be uninstalled before installation of newer versions to avoid silent errors" * The die message: * <dev-python/setuptools-0.6.3-r2 must be uninstalled before installation of newer versions to avoid silent errors * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-python/setuptools-0.6.3-r2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-python/setuptools-0.6.3-r2/temp/die.env'. * >>> Failed to emerge dev-python/setuptools-0.6.3-r2, Log file: >>> '/var/tmp/portage/dev-python/setuptools-0.6.3-r2/temp/build.log' * Messages for package sys-libs/timezone-data-2009n: * You do not have TIMEZONE set in /etc/timezone. * Skipping auto-update of /etc/localtime. * Messages for package dev-python/setuptools-0.6.3-r2: * * ERROR: dev-python/setuptools-0.6.3-r2 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * setuptools-0.6.3-r2.ebuild, line 30: Called die * The specific snippet of code: * die "<dev-python/setuptools-0.6.3-r2 must be uninstalled before installation of newer versions to avoid silent errors" * The die message: * <dev-python/setuptools-0.6.3-r2 must be uninstalled before installation of newer versions to avoid silent errors * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-python/setuptools-0.6.3-r2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-python/setuptools-0.6.3-r2/temp/die.env'. * [cut] # ls -la /etc/timezone ls: cannot access /etc/timezone: No such file or directory # strings /etc/localtime TZif2 MEST TZif2 MEST MET-1MEST,M3.5.0,M10.5.0/3 # If I have a misconfigured system my apologies then. Maybe some while ago I failed to upgrade from baselayout-1? I would vote for more sanity checks in init scripts, there will be more users like I have then. setuptools failing is unrelated to this bug report if you upgraded baselayout early, you probably missed out on some of the automatic translations. you probably want to review the guide: http://www.gentoo.org/doc/en/openrc-migration.xml (In reply to comment #4) > setuptools failing is unrelated to this bug report Sorry, realized that too late in the submission process. ;) > if you upgraded baselayout early, you probably missed out on some of the I think really a long while ago, yes. > automatic translations. you probably want to review the guide: > http://www.gentoo.org/doc/en/openrc-migration.xml Yes, I just did. Will see if I get this again. Definitely am voting for more sanity checks in init scripts, something the timezone-data ebuild does for example? |