On 09/04/07, Naoki wrote:
On Mon, 2007-04-09 at 12:02 +0200, Michael Schwendt wrote:
On 09/04/07, Naoki wrote:
>
> Hi all,
>
> Bit of a cosmetic problem here.
>
> # rpm -qa selinux-policy-strict
> selinux-policy-strict-2.4.6-49.fc6
> selinux-policy-strict-2.2.34-3.fc5
>
>
> # rpm -qf /usr/share/selinux/strict/usbmodules.pp
> selinux-policy-strict-2.4.6-49.fc6
> selinux-policy-strict-2.2.34-3.fc5
>
>
> # rpm -e selinux-policy-strict-2.2.34-3.fc5
> libsemanage.semanage_direct_remove: Module dpkg was not
> found.
> semodule: Failed on dpkg!
> error:
%trigger(selinux-policy-strict-2.4.6-49.fc6.noarch)
> scriptlet failed, exit status 1
>
>
> Any idea what is going on there? rpm --rebuilddb didn't help, next option
> is a force but I never like those.
rpm -e --notriggers --noscripts
selinux-policy-strict-2.2.34-3.fc5
might suffice.
You are correct sir!
# rpm -qa selinux-policy-strict
selinux-policy-strict-2.4.6-49.fc6
selinux-policy-strict-2.2.34-3.fc5
# rpm -e --notriggers --noscripts
selinux-policy-strict-2.2.34-3.fc5
# rpm -qa selinux-policy-strict
selinux-policy-strict-2.4.6-49.fc6
Now the question is, how did it get itself into that state? I guess the
yum update from FC5->FC6 failed to remove the old package because of the
scripts error.
A yum update from FC5 to FC6 is not an official upgrade path. Further,
selinux-policy-strict-2.2.34-3.fc5 is not the latest update for FC5,
but one that is older than August 2006. Perhaps you can reconstruct
when the dpkg policy package was last present and whether the triggers
(watch the versions) in the rpm package were accurate. :)