Comment # 11 on bug 1029527 from
Hi,

I have a new information about this strange error: V3.

I have tried to upgrade system to tumbleweed again. Before this, I have
rebuilded a rpm database with the
rpmdb --rebulddb
command. It finished without error, so I have update first and second from
problematic packages, xrefres with the
zypper up xrefresh
and then
zypper up xkill
command. Both of them finished without error. I have continued with
zypper dup.
The first V3 error occured, when package alevt was upgraded. It is the next
problematic package in a row, so I have finished this upgrade with choosing
"ignore" option at all next problems. Again. A rpm command refuse to delete
some of old packages. I have forced zypper to install rpm package from
opensuse-42.3-update-oss repository (break all necessary dependencies), version
4.11.?? and there was no problem with removing old problematic packages with
rpm -e problematic_package-exact-version.
Then I have installed new rpm and run
zypper verify
command.
Malfunctions with deleting packages disappear, but when I have tried to
substitute a wine package installed from opensuse-tumbleweed repository a few
hours ago with a wine-staging package, rpm version 4.14 refused to delete the
package wine with V3 error.
So I have repeated this exercise with rpm packages several times, always rpm
from opensuse-42.3 repostiory works, but one from opensuse-tumbleweed
repository fail.

I have checked public certificates with 
rpm -vv -qf /etc
command and there was one old V3 certificate. I have deleted it and rpm stops
work entirely (version from opensuse-tumbleweed). Every using of this
application finished with SIGSEG fault.

Distribution 42.3 is upgraded to last version from repositories. Zypper claims,
there are some packages newer than equal packages from opensuse-tumbleweed
repository.

There are next possibilities how to upgrade this distribution, but only a few
now. I have a lot of configuration in this distribution, I don't want to find
all of them, backup them, and reinstall distribution entirely. Installation
system on CD is not working with LVM snapped and/or mirrored partitions. It can
not recognize them, so automatic moving of configurations is not possible.

May be, a solution is to lock rpm package at version 4.11.??.

I am sorry for bothering You.

Preema


You are receiving this mail because: