Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#50169 - [borg] PLEASE ENTER SUMMARY

Attached to Project: Community Packages
Opened by fd64 (fd64) - Wednesday, 27 July 2016, 17:54 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 27 July 2016, 23:47 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Could you please force borg use version 3 of python ?
I have made python2 the default on my system because I am using ansible which does not work with python3
If you are not aware of this you get a python error when you try to execute borg, and for most users it is not obvious what the solution is. You just have to modify the first line in /usr/sbin/borg so it uses /usr/bin/python3 instead of /usr/bin/python to make all users happy. Would be nice to get borg working out of the box without having to hack it.

Additional info:
* version 1.0.6-1
* config and/or log files etc.

Steps to reproduce:
# rm -f /usr/sbin/python
# ln -s /usr/sbin/python2.7 /usr/sbin/python2
# /usr/sbin/borg
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 27 July 2016, 23:47 GMT
Reason for closing:  Not a bug
Comment by Dave Reisner (falconindy) - Wednesday, 27 July 2016, 18:05 GMT
> I have made python2 the default on my system because I am using ansible which does not work with python3
You've entered unsupported territory... This wouldn't be a problem with only borg, but tons of packages. Via PEP 394, Arch has decided that "python" points to python3.
Comment by fd64 (fd64) - Wednesday, 27 July 2016, 18:28 GMT
Ok it's a shame if there is nothing we can do about this problem, but if this is a general policy I can understand it.
Comment by Doug Newgard (Scimmia) - Wednesday, 27 July 2016, 23:47 GMT
Ansible has other ways around this, changing the system symlink is a very bad idea.

Loading...