http://bugzilla.wpkg.org/show_bug.cgi?id=129
Rainer Meier <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
--- Comment #1 from Rainer Meier <[EMAIL PROTECTED]> 2008-09-03 21:42:47 ---
Hmm, I will try to verify the problem. Could you try to verify if it is clearly
related to the number of package definitions or not (temporary remove some on a
test installation...)? Or could you at least tell us the exact number of
packages it requires to force this error? Is 100 enough? How many do you have
exactly?
It's a bit curious to me that an "out of stack" error occurs - and not a kind
of "out of memory". It could be related to some very deep recursion. Probably
it's related to the new dependency mechanisms. You might have some kind of
recursive dependency in your packages. Could you try to analyze your
dependencies?
Is it possible that some recursive dependency exists within your package tree?
In older WPKG versions WPKG would just "include" dependent packages to the
profile of the node it applies to. WPKG 1.x first applies the dependencies
before installing the actual package. If there is a recursive dependency, then
it will loop forever going deeper and deeper into recursive function calls -
which could lead to an out of stack memory exception.
I will consider including a recurse detection to WPKG 1.1.x to detect such
package errors.
br,
Rainer
--
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
[email protected]
http://lists.wpkg.org/mailman/listinfo/wpkg-users
