So I'm not sure how to explain the behavior from Zypper.. If you can figure out a command line reproducer for this we can resolve it. If not, then we may need to start running things through a debugger.
(If possible, add "-vv" to the command line from Zypper to RPM.. This will add extended debug info that might help... comparing the output of the -vv from Zypper and from you running the command on the command line yourself might point out the issue)
(In reply to comment #4)
> When removing a package it should be valid to list all of the components or
> simply a subset.. i.e.
> rpm -e task-poky-sdk
> rpm -e task-poky-sdk-1.0-r5
these two passed in my image, manual execution
> rpm -e task-poky-sdk-1.0-r5.armv5te
this one failed with "error: package xxx is not installed", manual execution
> I was able to boot into a target and run similar commands to verify this.
> With the commands below added:
> --root / --dbpath /var/lib/rpm -e --allmatches --nodeps
> it still worked correctly on the target as well.
Yeah, I think they don't add anything different
Has this anything to do with armv5te and armv5tejl differences (see bug 489)
(In reply to comment #5)
> (In reply to comment #4)
> > When removing a package it should be valid to list all of the components or
> > simply a subset.. i.e.
> > rpm -e task-poky-sdk
> > rpm -e task-poky-sdk-1.0-r5
>
> these two passed in my image, manual execution
>
>
> > rpm -e task-poky-sdk-1.0-r5.armv5te
>
> this one failed with "error: package xxx is not installed", manual execution
>
talked with Jiajun, now we can confirm that, the arch is misrepresented in zypper
with --verbose parameter, it shows that
---
...
Check failed:
History:
- Command exited with status 129.
- Executing 'lsof' failed (129).
---
but lsof is not installed in the image
Is the missing of lsof causes this bug?