Summary: | Possible Python coding issue with Catalyst stage 2 processing | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Dan Foster <dsf> |
Component: | Catalyst | Assignee: | Gentoo Catalyst Developers <catalyst> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
My LiveCD Stage 2 specfile
emerge info output Stack trace of Python crashing in Catalyst stage 2 processing Proposed patch for /usr/lib/catalyst/modules/catalyst_support.py |
Description
Dan Foster
2005-05-01 15:05:59 UTC
Created attachment 57770 [details]
My LiveCD Stage 2 specfile
Created attachment 57771 [details]
emerge info output
Created attachment 57772 [details]
Stack trace of Python crashing in Catalyst stage 2 processing
Created attachment 57774 [details, diff]
Proposed patch for /usr/lib/catalyst/modules/catalyst_support.py
This shoehorns the list into a string type so that concatenation will succeed.
Catalyst build succeeds with this modification.
Note: this is against Catalyst 1.1.9.
Please close this 'bug'. It appears that I had some optional options in the spec file set to no value, which got propagated into Python via Catalyst, and broke stuff. Removing all options without a value set in the .spec file seems to have taken care of that. While I might posit this is perhaps (no offense) some missing defensive programming in the code, it's not an actual bug per se -- perhaps better done as a RFE (request for enhancement) or documentation improvement request. I may submit one of the two later after I ponder options and possibly a suggested patch to either the Catalyst Python module or to the Catalyst docs. Please disregard this and close it out. Thanks! Closing this bug. Your comments are appreciated and a new RFE might be more applicable as you already stated. |