Summary: | config-kernel error when /var/tmp/kernel-output doesn't exists. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Simone Gotti (RETIRED) <motaboy> |
Component: | [OLD] Core system | Assignee: | John Mylchreest (RETIRED) <johnm> |
Status: | RESOLVED REMIND | ||
Severity: | normal | CC: | tor.klingberg |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Simone Gotti (RETIRED)
2004-05-09 04:45:15 UTC
appologies for introducing this bug. there was a commit of the kernel-2 eclass which had a spurious DEPEND (config-kernel) which is right now, effectively useless for koutput. the changes should hopefully being made properly in the near future so keep your eyes peeled :) there will be an announcement in the GWN anyways to remind you. for now please ignore all koutput features for config-kernel. Don't worry. :-) By the way, after creating by hand the kernel-output dir all the features of config-kernel worked out of the box! I've emerged with no more sandbox violations the ipw2100 and the submount kernel modules. So keep up the good work! Bye! Also was hit by this bug. To avoid further user frustration, I'd suggest to modify line 238 of "ck_actions.py". Currently it says "os.mkdir(outputpath)", which should be replaced by "os.makedirs(outputpath)": mkdir requires all parent directories to exists, whilest makedirs creates them, when needed. suspending until config-kernel kouput is ready for the wild. Please fix this real soon. It is kind of disturbing since it whacks your /usr/src/linux structure without recreating it somewhere else. If, for some reason, you don't want to do this, then but a big warning on http://www.gentoo.org/doc/en/2.6-koutput-user.xml saying koutput is not ready to be used yet. |