pip was installed after i starting having issues (i think a serverfault forum thread sugested/confirmed a fix) but no go.
pip uninstalled, rpm -Va ran with only python-setuptools listed. reinstalled this pkg and now no results. same error - ContextualVersionConflict.
Certbot python2-cryptography version mismatch
[solved] Re: Certbot python2-cryptography version mismatch
got it sussed.
reinstalled pip then upgraded from within pip.
then i went with an upgrade of the cyrptography package from the 1.7.2 epel version, to whatever pip put me on (2.4.2)
re-ran certbot and all is good - cert has now been renewed.
i completely forgot how my home server was setup; centos host with 4 centos guest VM's on it. Some of those guests also have certbot running but i haven't got round to configuring yum-cron updates properly on them yet. those still ran certbot 0.26 rather than 0.29.1 that the host does so they've obviously changed the base levels which aren't satisfied with repo dependencies.
reinstalled pip then upgraded from within pip.
Code: Select all
sudo pip install -U pip
Code: Select all
sudo pip install cryptography --upgrade
i completely forgot how my home server was setup; centos host with 4 centos guest VM's on it. Some of those guests also have certbot running but i haven't got round to configuring yum-cron updates properly on them yet. those still ran certbot 0.26 rather than 0.29.1 that the host does so they've obviously changed the base levels which aren't satisfied with repo dependencies.
Re: Certbot python2-cryptography version mismatch
I do not think you have solved this issue, you've just made it worse and accidentally made the current symptoms go away. It will come back to bite you in the future instead.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Re: Certbot python2-cryptography version mismatch
While i've seen your thoughts are reflected with others on pip, i stumbled across the doucmentation of the cryptography module; https://cryptography.io/en/latest/faq/# ... to-install.
does say to update via pip. and unless i missed something in the output, it only said it installed a newer version of cryptography.
i'll raise with epel repos (iirc they use the redhat bug trac). they provide both certbot and it's dep pkgs. based on the output and my pip findings it is a version problem. I could probably prove it on one of those 4 guest VM's too, so good for the bug report.
does say to update via pip. and unless i missed something in the output, it only said it installed a newer version of cryptography.
i'll raise with epel repos (iirc they use the redhat bug trac). they provide both certbot and it's dep pkgs. based on the output and my pip findings it is a version problem. I could probably prove it on one of those 4 guest VM's too, so good for the bug report.
Re: Certbot python2-cryptography version mismatch
Before filing bugs, I would suggest setting up a fresh VM and then installing epel-release and certbot on it. I'm fairly certain that certbot would work out of the box on such a freshly installed system.
Re: Certbot python2-cryptography version mismatch
It does, I already tried it.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke