Re: [arch-general] Wesnoth probably has wrong dependency
On 6/3/20 5:47 AM, Peter Nabbefeld wrote: > > Hello, > > as Python2 has been sunset since the beginning of this year > (https://www.python.org/doc/sunset-python-2/) I'm looking forward to > removing it. One of the packages still depending on python2 is wesnoth, > though due to https://wiki.wesnoth.org/Maintenance_tools it should work > with Python3 already. Of course, this should work, since Python3 is > installed already besides Python2, but it seems to be an unnecessary > dependency. Instead, the dependency should be updated to python. https://github.com/wesnoth/wesnoth/issues/1508 Try grepping the package for python2 or python3 shebangs: [eschwartz@dragon ~/wesnoth-extracted]$ ag --files-with-match python2 usr/share/wesnoth/data/tools/expand-terrain-macros.py usr/share/wesnoth/data/tools/journeylifter usr/share/wesnoth/data/tools/rmtrans/rmtrans.py usr/share/wesnoth/data/tools/scoutDefault.py usr/share/wesnoth/data/tools/trackplacer usr/share/wesnoth/data/tools/wesnoth/wmlgrammar.py usr/share/wesnoth/data/tools/wesnoth/wmldata.py usr/share/wesnoth/data/tools/wesnoth/wmliterator.py usr/share/wesnoth/data/tools/wesnoth/wmlparser2.py usr/share/wesnoth/data/tools/wesnoth/wmlparser.py usr/share/wesnoth/data/tools/wesnoth/wmltools.py usr/share/wesnoth/data/tools/wmlvalidator usr/share/wesnoth/data/tools/wmlflip [eschwartz@dragon ~/wesnoth-extracted]$ ag --files-with-match python3 usr/share/wesnoth/data/tools/addon_manager/__init__.py usr/share/wesnoth/data/tools/GUI.pyw usr/share/wesnoth/data/tools/about_cfg_to_wiki usr/share/wesnoth/data/tools/addon_manager/html.py usr/share/wesnoth/data/tools/campaign2wiki.py usr/share/wesnoth/data/tools/extractbindings usr/share/wesnoth/data/tools/hexometer.py usr/share/wesnoth/data/tools/imgcheck usr/share/wesnoth/data/tools/terrain2wiki.py usr/share/wesnoth/data/tools/unit_tree/__init__.py usr/share/wesnoth/data/tools/unit_tree/TeamColorizer usr/share/wesnoth/data/tools/steam-changelog usr/share/wesnoth/data/tools/unit_tree/update-wmlunits usr/share/wesnoth/data/tools/unit_tree/wiki_output.py usr/share/wesnoth/data/tools/unit_tree/animations.py usr/share/wesnoth/data/tools/unit_tree/helpers.py usr/share/wesnoth/data/tools/wesnoth/campaignserver_client.py usr/share/wesnoth/data/tools/wesnoth/libgithub.py usr/share/wesnoth/data/tools/wesnoth/wmliterator3.py usr/share/wesnoth/data/tools/unit_tree/overview.py usr/share/wesnoth/data/tools/unit_tree/html_output.py usr/share/wesnoth/data/tools/wesnoth_addon_manager usr/share/wesnoth/data/tools/wesnoth/wescamp.py usr/share/wesnoth/data/tools/wmlindent usr/share/wesnoth/data/tools/wesnoth/wmlparser3.py usr/share/wesnoth/data/tools/wesnoth/wmltools3.py usr/share/wesnoth/data/tools/wmlunits usr/share/wesnoth/data/tools/wmllint-1.4 usr/share/wesnoth/data/tools/wmlscope usr/share/wesnoth/data/tools/wmlxgettext usr/share/wesnoth/data/tools/wmllint -- Eli Schwartz Bug Wrangler and Trusted User signature.asc Description: OpenPGP digital signature
Re: [arch-general] Wesnoth probably has wrong dependency
Am 04.06.20 um 09:18 schrieb Bjoern Franke via arch-general: Hi, as Python2 has been sunset since the beginning of this year (https://www.python.org/doc/sunset-python-2/) I'm looking forward to removing it. One of the packages still depending on python2 is wesnoth, though due to https://wiki.wesnoth.org/Maintenance_tools it should work with Python3 already. Of course, this should work, since Python3 is installed already besides Python2, but it seems to be an unnecessary dependency. Instead, the dependency should be updated to python. so, why do you just don't file a bug report? Regards Bjoern Just because I don't have an account and don't want to create one every three years again or require a new password. Also, as I'm rarely looking at package definitions, I still may be wrong, so it'd be preferred if somebody else could have a look at this (somebody with more knowledge about packages maintenance). Kind regards, Peter
Re: [arch-general] Wesnoth probably has wrong dependency
Hi, > > as Python2 has been sunset since the beginning of this year > (https://www.python.org/doc/sunset-python-2/) I'm looking forward to > removing it. One of the packages still depending on python2 is wesnoth, > though due to https://wiki.wesnoth.org/Maintenance_tools it should work > with Python3 already. Of course, this should work, since Python3 is > installed already besides Python2, but it seems to be an unnecessary > dependency. Instead, the dependency should be updated to python. so, why do you just don't file a bug report? Regards Bjoern
[arch-general] Wesnoth probably has wrong dependency
Hello, as Python2 has been sunset since the beginning of this year (https://www.python.org/doc/sunset-python-2/) I'm looking forward to removing it. One of the packages still depending on python2 is wesnoth, though due to https://wiki.wesnoth.org/Maintenance_tools it should work with Python3 already. Of course, this should work, since Python3 is installed already besides Python2, but it seems to be an unnecessary dependency. Instead, the dependency should be updated to python. Kind regards Peter
