Hide Forgot
Description of problem: Fedora22-supplied python3-msgpack dies on attempt to use on ppc64 box, as evidenced by borg (https://github.com/borgbackup/borg/), recompiling msgpack with pip locally makes the problem go away for both 0.4.6 (same version as in Fedora) and 0.4.7 (latest version). Version-Release number of selected component (if applicable): Name : python3-msgpack Arch : ppc64 Epoch : 0 Version : 0.4.6 Release : 1.fc22 How reproducible: 100% reproducible. Steps to Reproduce: install python3-msgpack (dnf install python3-msgpack) Install borg (pip3.4 install "borgbackup==1.0.1") borg init somehost:/tmp/backup Actual results: this crashes 100% of time with "Illegal instruction (core dumped)" abrt backtrace head is like this: { "signal": 4 , "executable": "/usr/bin/python3.4" , "stacktrace": [ { "crash_thread": true , "frames": [ { "address": 70366574793944 , "build_id": "b25b960673a0f2d02a6e873c24af1a5be471bc46" , "build_id_offset": 54488 , "function_name": "00000017.plt_call.PyBytes_AsString" , "file_name": "/usr/lib64/python3.4/site-packages/msgpack/_unpacker.cpython-34m.so" } , { "address": 70366714197868 , "build_id": "dbdd62cb43c5dce605c9b89e55227a8cf62666ee" , "build_id_offset": 1177452 , "file_name": "/lib64/libpython3.4m.so.1.0" } , { "address": 70366713679904 , "build_id": "dbdd62cb43c5dce605c9b89e55227a8cf62666ee" , "build_id_offset": 659488 , "function_name": "PyObject_Call" , "file_name": "/lib64/libpython3.4m.so.1.0" } Expected results: the repo should be initialized. Additional info: dnf remove python3-rpcmsg followed by pip3.4 install msgpack-python # Ths will compile a local version. makes the problem to go away, so I believe the issue is in how Fedora compiled this.
I also just checked and Fedora23 is fine in this regard.
Honestly, I doubt if anyone would investigate this issue for F22, considering that it's working for F23+. Maybe package rebuild can fix the issue, could you rebuild it and check it out?
I don't really have enough stuff installed to try for a rebuild and I am going to upgrade to F23 shortly myself anyway, so I guess this is not very important. But still good to have it reported so that if somebody else stumbles on this issue, they know what's going on.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.