http://bugzilla.opensuse.org/show_bug.cgi?id=1191351 http://bugzilla.opensuse.org/show_bug.cgi?id=1191351#c3 --- Comment #3 from Markus Elfring --- Will the chances grow for corresponding software fixes also by the means of more detailed source code analysis and review? https://github.com/yast/yast-yast2/blob/4f0560a55f0b4ece41ed50063fd7baf00cd8... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1191351 http://bugzilla.opensuse.org/show_bug.cgi?id=1191351#c5 Knut Alejandro Anderssen Gonz��lez changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #5 from Knut Alejandro Anderssen Gonz��lez --- (In reply to Markus Elfring from comment #4)

I imagine that another source code inspection can help for the desired clarification of the reported issue.

At which code places is it tried so far to call the method ���path��� (eventually also for the class ���Y2Packager::Resolvable���)?

Ok, I was trying to reproduce the error and was able to raise the same exception in a console: So apparently the problem is cause by products which do not have the "path" attribute which should be optional: From the logs at least these two: ,��� # -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1191351 Knut Alejandro Anderssen Gonz�lez changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1191351 http://bugzilla.opensuse.org/show_bug.cgi?id=1191351#c7 --- Comment #7 from Knut Alejandro Anderssen Gonz��lez --- (In reply to Markus Elfring from comment #6)

(In reply to Knut Alejandro Anderssen Gonz��lez from comment #5)

...

Ok, I was trying to reproduce the error and was able to raise the same exception in a console:

Thanks for such a constructive feedback.

...

So apparently the problem is cause by products which do not have the "path" attribute which should be optional:

I would wonder why this questionable attribute access was reported as a call of an ���undefined method���. Will any test cases be extended accordingly?

(In reply to Markus Elfring from comment #4)

I imagine that another source code inspection can help for the desired clarification of the reported issue.

At which code places is it tried so far to call the method ���path��� (eventually also for the class ���Y2Packager::Resolvable���)?

It uses meta-programming to expose the attribute methods, in our case, there is some products data information that is filled here: https://github.com/yast/yast-packager/blob/master/src/lib/y2packager/install... As it is documented in the Resolvable class, not all the attributes are mandatory because resolvable works with different kind of resolvable objects, and that is why path is optional and should exist only with packages and products as stated here: https://github.com/yast/yast-yast2/blob/master/library/packages/src/lib/y2pa... But as the Product mentioned before (openSUSE-Addon-NonOss version 13.2) does not have the path attribute and can not obtain or set the instance variable it calls the method in the line reported (https://github.com/yast/yast-yast2/blob/master/library/packages/src/lib/y2pa...) by the super call. And yep, with the proper fix we will also provide a test covering this case. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1191351 http://bugzilla.opensuse.org/show_bug.cgi?id=1191351#c9 --- Comment #9 from Markus Elfring --- (In reply to Knut Alejandro Anderssen Gonz�lez from comment #8) How will chances evolve to optimise the dependency resolution any further for the involved components (also for my next software distribution upgrade attempts)? -- You are receiving this mail because: You are on the CC list for the bug.