https://bugzilla.suse.com/show_bug.cgi?id=1183711
https://bugzilla.suse.com/show_bug.cgi?id=1183711#c14
Ladislav Slez�k
It seems that libzypp/solv has already opened /mnt/var/cache/zypp/solv/@System, and then a different /var/cache/zypp/solv/@System is copyied to it. Which sounds like there is some fundamental problem somewhere else.
OK, that is probably the reason, the /mnt/var/.../@System is the original file from the upgraded system, the /var/.../@System file from the inst-sys which is probably just an empty database. So there are basically these options: 1) Just skip copying the @System file at upgrade, copy the other files 2) Copy the caches only in a fresh installation, do not do that at upgrade 3) Do not copy the cache at all The option 3) is the safest but does help to save any RAM, the 2) ensures we either copy all or nothing so the data should be more consistent, 1) is just a solution for the broken @System file, though I do not know if that's enough. I'm not sure which solution to pick, which one is OK for libzypp. If we do not know than the safe option is to revert the cache patches completely. Michaels? -- You are receiving this mail because: You are on the CC list for the bug.