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!
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!
FS#50132 - [libtorrent-rasterbar] Providing python-libtorrent-rasterbar
Attached to Project:
Arch Linux
Opened by Götz (goetzc) - Friday, 22 July 2016, 22:34 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 24 July 2016, 15:24 GMT
Opened by Götz (goetzc) - Friday, 22 July 2016, 22:34 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 24 July 2016, 15:24 GMT
|
DetailsDescription:
It seems that version 1.1-3 now includes the Python 3 bindings, and there is some doubts about this in the AUR package's comments.[1] Will this package now include the bindings, and the AUR package should/will be deleted, or not? Currently if python-libtorrent-rasterbar is installed, libtorrent-rasterbar can not be upgraded because of conflicting files. https://aur.archlinux.org/packages/python-libtorrent-rasterbar |
This task depends upon

Yes, this was intentional (how could it not be?). My question on the AUR page was simply asking if there was anything different about the AUR package that would justify keeping it around.