Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 133368 - catalyst 1.1.10.10 unbind(self)
Summary: catalyst 1.1.10.10 unbind(self)
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Hosted Projects
Classification: Unclassified
Component: Catalyst (show other bugs)
Hardware: AMD64 Linux
: High normal
Assignee: Gentoo Catalyst Developers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-15 03:56 UTC by Martin Rehr
Modified: 2006-05-15 12:54 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Rehr 2006-05-15 03:56:18 UTC
I believe that line 294 in /usr/lib/catalyst/modules/generic_stage_target.py
should'nt be there as it makes the unbind(self) method raise CatalystError, even though catalyst succeeds in killing chroot process and actual unmount,
the dir that failed umount in line 291.
Comment 1 Andrew Gaffney (RETIRED) gentoo-dev 2006-05-15 04:51:56 UTC
Does this problem still exist in catalyst-2.0_rc45? The 1.x branch of catalyst is no longer supported. Where is the offending line in 2.0_rc45? What is the traceback you get?
Comment 2 Chris Gianelloni (RETIRED) gentoo-dev 2006-05-15 12:54:45 UTC
Well, it isn't so much that it isn't supported, just that we won't be doing any coding on it.  It's end of life so far as coding, but it *is* still the current "stable" version.

I've honestly considered stabilizing one of the catalyst 2.0 RC's and removing catalyst 1.x just so I don't ever have to hear about it again... ;]

Anyway, the solution here is to use catalyst 2.0 instead.  If it is still a problem there, REOPEN this bug and we'll fix it in the 2.0 branch.