Bug 751918

Summary:	ERROR @ parsing zypper.conf after zypper v1.6.18 -> v1.6.21 update from 'official' update repo (d.o.o/update/12.1/)
Product:	[openSUSE] openSUSE 12.1	Reporter:	guest 69878 <guest69878>
Component:	libzypp	Assignee:	E-mail List <zypp-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	All
OS:	openSUSE 12.1
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description guest 69878 2012-03-13 03:29:02 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2

on opensuse 12.1/x86_64, i currently have installed

	zypper-1.6.18-5.8.1.x86_64.rpm

'zypper up' works fine.
	
i'm subscribed to 'update' repo,

	opensuse/update/12.1/x86_64

an upgrade has been available since Feb 20, to

	zypper-1.6.21-5.14.1.x86_64.rpm

if

	zypper up zypper
	rpm -q zypper
		zypper-1.6.21-5.14.1.x86_64

now

	zypper up
		Error parsing zypper.conf:
		/etc/zypp/zypper.conf: Input string does not match at all
		*** Augeas exception. No config read, sticking with defaults.
		Loading repository data...
		Reading installed packages...

fails to read the existing zypper.conf,

	cat /etc/zypp/zypper.conf
		[main]
		
		[solver]
		forceResolutionCommands = remove
		installRecommends = yes
		
		[color]
		useColors = autodetect
		background = light
		msgError = red
		msgStatus = grey
		msgWarning = yellow
		result = black
		negative = red
		highlight = lightcyan
		positive = green
		promptOption = grey
		
		[obs]

downgrading back to v1.6.18,

	rpm -Uvh --force http://suse.mirrors.tds.net/pub/opensuse/update/12.1/x86_64/zypper-1.6.18-5.8.1.x86_64.rpm
	rpm -q zypper
		zypper-1.6.18-5.8.1.x86_64

fixes 'zypper up',

	zypper up
		Loading repository data...
		Reading installed packages...

so it's back to normal.

i can reproduce this on other i586 & x86_64 machines.

workaround for now is to add a lock

	cat /etc/zypp/locks
		type: package
		match_type: glob
		case_sensitive: on
		solvable_name: zypper

to prevent the upgrade	

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1 Michael Andres 2012-03-13 09:17:15 UTC

You don't need to lock zypper. 

Actaully the parse error also exists in older zypper versions, but older zypper versions silently ignored such an error. They are now reported so we can detect and fix them.

Comment 2 Michael Andres 2012-03-13 09:27:11 UTC

It will most probably work if you put an empty line in front of '[main]'. This is fixed for 12.1 in zypper-1.6.22.

*** This bug has been marked as a duplicate of bug 748144 ***