[Bug 751918] New: ERROR @ parsing zypper.conf after zypper v1.6.18 -> v1.6.21 update from 'official' update repo (d.o.o/update/12.1/)
https://bugzilla.novell.com/show_bug.cgi?id=751918 https://bugzilla.novell.com/show_bug.cgi?id=751918#c0 Summary: ERROR @ parsing zypper.conf after zypper v1.6.18 -> v1.6.21 update from 'official' update repo (d.o.o/update/12.1/) Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: All OS/Version: openSUSE 12.1 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: guest69878@fastem.com QAContact: qa@suse.de Found By: --- Blocker: --- 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.... 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=751918 https://bugzilla.novell.com/show_bug.cgi?id=751918#c guest 69878 <guest69878@fastem.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |libzypp AssignedTo|bnc-team-screening@forge.pr |zypp-maintainers@forge.prov |ovo.novell.com |o.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=751918 https://bugzilla.novell.com/show_bug.cgi?id=751918#c1 --- Comment #1 from Michael Andres <ma@suse.com> 2012-03-13 10:17:15 CET --- 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=751918 https://bugzilla.novell.com/show_bug.cgi?id=751918#c2 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #2 from Michael Andres <ma@suse.com> 2012-03-13 10:27:11 CET --- 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 *** http://bugzilla.novell.com/show_bug.cgi?id=748144 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com