http://bugzilla.opensuse.org/show_bug.cgi?id=1139795 http://bugzilla.opensuse.org/show_bug.cgi?id=1139795#c1 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andre.ramnitz@mail.de Flags| |needinfo?(andre.ramnitz@mai | |l.de) --- Comment #1 from Michael Andres --- Libzypp does not deal with this file. The file is owned by the openSUSE-release package. If it is missing after your update the release-package (and product:openSUSE) maybe got removed. Or the release package got damaged.. Could you please attach the zipper.log (after the update) and the output of `rpm -V openSUSE-release'. --- (Re)installing the openSUSE-release package should bring back the file. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1139795 http://bugzilla.opensuse.org/show_bug.cgi?id=1139795#c3 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #3 from Michael Andres --- Thanks a lot. I stand corrected, libzypp deals with the file. It looks like the installed product:openSUSE-20190626 was slightly broken (no link to it's release package). Updating it wrongly triggers an attempt to repair it (which actually messes it up). AFAICS it happens only if you update FROM an installed 'product:openSUSE-20190626'. Reinstalling openSUSE-release (zypper in -f openSUSE-release) if the '/etc/products.d/baseproduct link is missing or broken' warnings occur should fix it. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1139795 http://bugzilla.opensuse.org/show_bug.cgi?id=1139795#c5 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #5 from Michael Andres --- Fixed in libzypp-17.12.1 -- You are receiving this mail because: You are on the CC list for the bug.