When starting fwbackups in Mageia 7, it immediately crashes:
Traceback (most recent call last):
File "/usr/share/fwbackups/fwbackups-runapp.pyw", line 87, in <module>
raise fwbackups.fwbackupsError(_('Please install paramiko (python-paramiko)'))
fwbackupsError: u"Please install paramiko (python-paramiko)"
But trying to install python-paramiko-2.4.2-2 conflicts with the already installed python-paramiko-2.6.0-1.
Should fwbackups be recompiled to work with paramiko 2.6.0? fwbackups was working fine in Mageia 6. (pretty severe regression as I can no longer backup my system using it.)
This is curious. I did not have python-paramiko, so installed it - and it came in as 'python-paramiko-2.4.2-2.mga7', which is what is required.
# urpmq -i python-paramiko
Name : python-paramiko
Version : 2.4.2
Release : 2.mga7
Do you know how you got your 'python-paramiko-2.6.0-1' Frédéric?
# urpmi --test fwbackups
wrthi'n gosod fwbackups-1.43.7-1.mga7.noarch.rpm o /var/cache/urpmi/rpms
Wrthi'n paratoi... #############################################
Gellir gosod = It can be installed
So I suggest re-installing python-paramiko, either:
- If possible, UNinstall the version 2.6.0-1 (but this might take all sorts of other things with it):
# urpmi -e python-paramiko [or try first with --test parameter]
then re-install it - and check the version.
- # urpmi --downgrade python-paramiko
and see what version you get. If it is 2.4.2-2, good; if it is older, then you would have to update the system to bring it to this version. fwbackups should then be happy.
(In reply to Lewis Smith from comment #1)
> Do you know how you got your 'python-paramiko-2.6.0-1' Frédéric?
Probably because bug 25094 updated python-paramiko from 2.4.2 to 2.6.0 one month ago and renamed it to python2-paramiko? See https://advisories.mageia.org/MGAA-2019-0092.html for the advisory.
I do not want to downgrade it, for the reasons described in the advisory. So I think the right fix is to recompile fwbackups to work with the newer version of python-paramiko, and fix the dependency, if needed.
Thank you for your explanation.
By chance, I have just been fed the update of python-paramiko to
Re-naming packages like this is confusing; but it has certainly replaced
although the advisory made no mention of the name change.
For the record:
$ urpmq --whatrequires-recursive python-paramiko
$ urpmq --whatrequires-recursive python2-paramiko
$ urpmq --requires fwbackups
$ urpmq --requires-recursive fwbackups
Have to assign globally for fwbackups; CC'ing philippem for python-paramiko.
Any news on this? I still cannot do backups due to this issue.
I tried to rebuild it locally but it doesn't fix anything :(
Also fwbackups is a dead project and we have dropped it on Cauldron as it is not ported to python3.
The real issue is not about paramiko not installed but it is:
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
File "/usr/lib64/python2.7/atexit.py", line 24, in _run_exitfuncs
File "/usr/lib/python2.7/site-packages/paramiko/transport.py", line 120, in _join_lingering_threads
for thr in _active_threads:
TypeError: 'NoneType' object is not iterable
Error in sys.exitfunc:
<type 'exceptions.TypeError'>: 'NoneType' object is not iterable
(In reply to David GEIGER from comment #5)
> Also fwbackups is a dead project and we have dropped it on Cauldron as it is
> not ported to python3.
It has been replaced by which alternatives?
This is High priority bug for a good reason.
Making Mageia even better than ever is best direction.
In order to do right thing, this bug should be examined and fixed as soon as possible.
Packagers, please make the status to Assigned when you are working on this.
Feel free to reassign the bug if bad-triaged. Also, if bug is old, please close it.
On October 1st 2020, we will drop priority to normal.
I guess this is "won't fix" as the project is dead and has been removed from Mageia 8.