On 5/20/07, André Costa <blueser@xxxxxxxxx> wrote:
On 5/19/07, Kam Leo <kam.leo@xxxxxxxxx> wrote: > On 5/19/07, Daniel J Walsh <dwalsh@xxxxxxxxxx> wrote: > > André Costa wrote: > > > Hi, > > > > > > for some reason, I still have a FC5 SELinux package laying around: > > > > > > ~ rpm -qa selinux-policy-strict\* > > > selinux-policy-strict-2.4.6-62.fc6 > > > selinux-policy-strict-2.2.34-3.fc5 > > > > > > If I try to remove the stray FC5 package, something goes wrong: > > > > > > # rpm -ev 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-62.fc6.noarch) scriptlet > > > failed, exit status 1 > > > > > > Any clues? Should I try 'rpm -ev --notriggers > > > selinux-policy-strict-2.2.34-3.fc5' and then force FC6 package > > > reinstallation? > > > > > > TIA > > > > > > Andre > > > > > That should work. > > How about using "--noscripts"? I thought about "--notriggers "because error msg shows "error: %trigger(...)". Would it be safer if I used "--noscripts" instead? Regards, Andre
Well, I decided to give "--notriggers" a try anyway. Removal went by just fine, but reinstallation of FC6 package failed: # rpm -i --force selinux-policy-strict-2.4.6-62.fc6.noarch.rpm libsepol.scope_copy_callback: authlogin: Duplicate declaration in module: type/attribute system_chkpwd_t libsemanage.semanage_link_sandbox: Link packages failed semodule: Failed! Now I must confess I am clueless... any help will be appreciated. Regards, Andre
