Bug 330656

Summary:	yast interpreter silently uses the original YCP file when file in y2update fails
Product:	[openSUSE] openSUSE 10.3	Reporter:	Ladislav Slezák <lslezak>
Component:	YaST2	Assignee:	Martin Vidner <mvidner>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Ladislav Slezák 2007-10-04 08:07:33 UTC

When I was debugging a problem in SLES9-SP4 and I found that due to a compile error the YCP file from GM version was used instead of the SP version. See https://bugzilla.novell.com/show_bug.cgi?id=328732#c11

It was quite hard to find the cause or the wrong behavior.

When the required YCP script exists but it's wrong the interpreter should not try using another paths.

(The bug is reported against openSUSE10.3, but older versions/products are also affected.)

Comment 1 Martin Vidner 2007-10-04 15:10:17 UTC

Yes. The component creator cannot distinguish between "component does not exist" and "component is invalid" so it keeps looking for a valid one. That is also the reason why you usually see syntax errors repeated 4 times in the log.

I fixed it by introducing a dummy ErrorComponent.

Submitted yast2-core-2.16.1.