Description of problem:
play with koji I found mock -r koji/dist-f20-rpmfusion_free-build-14-19 --init
give me this error and yum remove rpm-plugin-selinux-18.104.22.168-4.fc21.i686
Version-Release number of selected component:
cmdline: /usr/bin/python /usr/bin/yum --installroot /var/lib/mock/dist-f20-rpmfusion_free-build-14-19/root/ groupinstall build
runlevel: N 5
transaction.py:72:addInstall:error: adding package to transaction failed
Traceback (most recent call last):
File "/usr/bin/yum", line 29, in <module>
File "/usr/share/yum-cli/yummain.py", line 371, in user_main
errcode = main(args)
File "/usr/share/yum-cli/yummain.py", line 277, in main
return_code = base.doTransaction(inhibit=inhibit)
File "/usr/share/yum-cli/cli.py", line 704, in doTransaction
self.populateTs(keepold=0) # sigh
File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 304, in populateTs
self.ts.addInstall(hdr, cbkey, txmbr.ts_state)
File "/usr/lib64/python2.7/site-packages/rpm/transaction.py", line 72, in addInstall
raise rpm.error("adding package to transaction failed")
error: adding package to transaction failed
Local variables in innermost frame:
item: <rpm.hdr object at 0x7f546a0d9090>
self: <rpm.transaction.TransactionSet object at 0x7f546b04b390>
header: <rpm.hdr object at 0x7f546a0d9090>
key: <TransactionMember : perl.i686 4:5.18.1-288.fc20 - u (0x7f546922ccb0)>
Created attachment 999422 [details]
Created attachment 999423 [details]
well mock prints this before traceback which is the problem
error: Failed to dlopen /usr/lib/rpm-plugins/selinux.so /usr/lib/rpm-plugins/selinux.so: wrong ELF class: ELFCLASS32
why I got rpm-plugin-selinux.i686 on system I don't know ... and
yum remove rpm-plugin-selinux-22.214.171.124-4.fc21.i686
fixes this issue .
This makes it impossible to create a 32bit mock root on 64bit linux now unless you remove the 32bit rpm libs (rpm-plugin-selinux.i686 which removes rpm-libs.i686)
is there some flag that mock should be specifying to yum to disable the loading of this plugin when it's creating a mock root?
Yeah, I just ran into that issue as well and ended up just creating a 32-bit VM in the meantime, though deleting rpm-plugin-selinux.i686 is probably a less drastic workaround. It'd be nice if there was a flag or something to allow it to work without deleting packages...
This is a bug in the rpm pluginsystem. Right now it uses
which depends on the architecture given to rpm not the architecture rpm is build for.
On the rpm cli --noplugins can be used to disable the plugins as a workaround.
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 21 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.