Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 136017 - dev-util/catalyst should be smarter about autoresume points
Summary: dev-util/catalyst should be smarter about autoresume points
Alias: None
Product: Gentoo Hosted Projects
Classification: Unclassified
Component: Catalyst (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Catalyst Developers
Depends on:
Reported: 2006-06-07 18:48 UTC by Andrew Gaffney (RETIRED)
Modified: 2012-09-07 04:35 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Gaffney (RETIRED) gentoo-dev 2006-06-07 18:48:45 UTC
Catalyst's current (2.0_rc46) handling of autoresume is a bit...dumb. I'm not saying that the design/implementation was done stupidly. It's just that catalyst is "dumb" about it.

For example, I had a messed up build at /var/tmp/catalyst2/tmp/default/stage3-i686-2006.1-pre/. I completely removed this directory. I neglected to remove the corresponding .autoresume directory for this build, so when I went to start the build again, catalyst died almost immediately saying that it could not execute /tmp/ (or whatever it it's called).

Basically, for each check for a file under self.settings["autoresume_path"], there should be a corresponding check for a file that *should* exist in the build directory if we are actually ready to resume at that spot in the build. It appears that some of the autoresume_path checks have corresponding sanity checks, but I've been bitten by this particular one twice.
Comment 1 Chris Gianelloni (RETIRED) gentoo-dev 2006-06-08 14:23:45 UTC

Patches?  *grin*