Because py-bcrypt conflicts with python2-bcrypt, it's not possible to simultaneously install packages dependent on the former (for example matrix-synapse) and packages dependent on the latter (e.g. bzr, deja-dup). Matrix is one of the most promising federated instant messaging protocols under development (potentially IRC without the XEP mess, or Signal without being forced to use a single company's servers), and having its reference server (matrix-synapse) in Fedora is great for ease of adoption. Having to remove default-installed backup software to install a Matrix server works against this unfortunately, so would be great if there's a way of fixing this.
Identical Arch bug: https://bugs.archlinux.org/task/54475
So far as I can tell python-bcrypt is only used by python-paramiko, whereas py-bcrypt is used by matrix-synapse, pagure, python-totpcgi, and commissaire-client. python-bcrypt is the more actively maintained, so in a perfect world I'd like to see everything move to python-bcrypt, but I don't know how feasible that is. If that's possible, that should happen and py-bcrypt should be retired. Do you know anything about how compatible the modules are?
Yes but a bunch of stuff requires python-paramiko (unfortunately the --tree option of 'dnf repoquery' doesn't work properly to list them). According to the readme of the bcrypt module (aka python-bcrypt) https://github.com/pyca/bcrypt/blob/master/README.rst: "This library should be compatible with py-bcrypt and it will run on Python 2.6+, 3.3+, and PyPy 2.6+." I had a quick chat with a dev on #matrix-dev on Freenode and informally they think it should be compatible too.
So if I change the Requires on matrix-synapse, pagure, python-totpcgi and commissaire-client to python-bcrypt, set the proper obsoletes/provides on python-bcrypt, and retire py-bcrypt, we should be good?
Yes in theory sounds about right, but I haven't tested it ;)
Ok, I've got the changes ready and will push and build. I've CCd the relevant maintainers. In a few days I'll push this to f26.
I'm not retiring py-pcrypt until both this is confirmed, and retire works following the pagure.io move.
python-bcrypt is not a drop-in replacement for py-bcrypt, try running pagure's unit-tests with it and you will see. So sorry but I'm un-doing your commit on the pagure package until pagure is ready to cope with this change.
(In reply to Pierre-YvesChibon from comment #8) > python-bcrypt is not a drop-in replacement for py-bcrypt, try running > pagure's unit-tests with it and you will see. Useful to know. Do you know what the incompatibilities are? Has there been discussion with upstream python-bcrypt about remedying them, since their README says it "should be compatible"? Or has addressing them been WONTFIXed by them?
IIRC the difference has to do with bytes vs unicode, I don't remember more details from the top of my head though.
Has it been discussed with upstream python-bcrypt?
(In reply to Pierre-YvesChibon from comment #8) > python-bcrypt is not a drop-in replacement for py-bcrypt, try running > pagure's unit-tests with it and you will see. > > So sorry but I'm un-doing your commit on the pagure package until pagure is > ready to cope with this change. Did you undo any other commits? The commits to python-bcrypt will need to be reverted.
> Has it been discussed with upstream python-bcrypt? I didn't, don't know if someone else did. > Did you undo any other commits? I just reverted the BuildRequires/Requires changes on pagure.spec, nothing else.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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' of '26'. 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 26 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.
It seams, that the same (or similar?) error still exists in Fedora 28. # LANG=C dnf install python2-py-bcrypt python2-bcrypt ... Error: Transaction check error: file /usr/lib64/python2.7/site-packages/bcrypt/__init__.py from install of python2-py-bcrypt-0.4-15.fc28.x86_64 conflicts with file from package python2-bcrypt-3.1.4-3.fc28.x86_64 file /usr/lib64/python2.7/site-packages/bcrypt/__init__.pyc from install of python2-py-bcrypt-0.4-15.fc28.x86_64 conflicts with file from package python2-bcrypt-3.1.4-3.fc28.x86_64 file /usr/lib64/python2.7/site-packages/bcrypt/__init__.pyo from install of python2-py-bcrypt-0.4-15.fc28.x86_64 conflicts with file from package python2-bcrypt-3.1.4-3.fc28.x86_64 file /usr/lib64/python2.7/site-packages/bcrypt/_bcrypt.so from install of python2-py-bcrypt-0.4-15.fc28.x86_64 conflicts with file from package python2-bcrypt-3.1.4-3.fc28.x86_64
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.