Arch Linux User Repository

Thanks for providing that package. It would be great if you could either set the !debug option so the debug package is not build or specify that you're building the debug package by providing a separate package-function for the debug package. Otherwise other packages have hard time if they conflict with this package and want to build a debug package, too (as the system then doesn't know that this package is responsible for the debug package).

If possible, please remove the dependency on python-furure/ make the package working without python-future:

WARNING: python-future package is not compatible with Python 3.13

The python-future project was created in 2013 to attempt to save Python from the schism of version incompatibility that was threatening to tear apart the language (as Perl 6 contributed to the death of Perl).

That time is now past. Thanks to a huge porting effort across the Python community, Python 3 eventually thrived. Python 2 reached its end of life in 2020 and the python-future package should no longer be necessary. Use it to help with porting legacy code to Python 3 but don’t depend on it for new code.

If you use packages that depend on it, please contact maintainers and/or upstream of these packages and try to work out whether this dependency is really needed.

Regards and thanks for this package!

Hi, I have the following message error

gcc -DNDEBUG -g -fwrapv -O3 -Wall -march=x86-64 -mtune=generic -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -g -ffile-prefix-map=/build/python/src=/usr/src/debug/python -flto=auto -ffat-lto-objects -march=x86-64 -mtune=generic -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -g -ffile-prefix-map=/build/python/src=/usr/src/debug/python -flto=auto -march=x86-64 -mtune=generic -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -g -ffile-prefix-map=/build/python/src=/usr/src/debug/python -flto=auto -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fPIC -I/usr/lib/python3.11/site-packages/pybind11/include -I/usr/lib/python3.11/site-packages/pybind11/include -Isrc -I/usr/include/python3.11 -c src/args.cc -o build/temp.linux-x86_64-cpython-311/src/args.o -DVERSION_INFO=\"0.9.2\" -std=c++14 -fvisibility=hidden
src/args.cc: In member function ‘void fasttext::Args::parseArgs(const std::vector<std::__cxx11::basic_string<char> >&)’:
src/args.cc:120:23: warning: comparison of integer expressions of different signedness: ‘int’ and ‘std::vector<std::__cxx11::basic_string<char> >::size_type’ {aka ‘long unsigned int’} [-Wsign-compare]
  120 |   for (int ai = 2; ai < args.size(); ai += 2) {
      |                    ~~~^~~~~~~~~~~~~
src/args.cc:221:19: warning: catching polymorphic type ‘class std::out_of_range’ by value [-Wcatch-value=]
  221 |     } catch (std::out_of_range) {
      |                   ^~~~~~~~~~~~
src/args.cc: In member function ‘int64_t fasttext::Args::getAutotuneModelSize() const’:
src/args.cc:468:3: error: ‘uint64_t’ was not declared in this scope
  468 |   uint64_t multiplier = 1;
      |   ^~~~~~~~
src/args.cc:17:1: note: ‘uint64_t’ is defined in header ‘<cstdint>’; did you forget to ‘#include <cstdint>’?

in this line

Thanks for noticing this, @sparrowhawk. Not sure how python2-setuptools managed to stay in the makedepends, but they definitely don’t belong there.

That said, namcap prints some cryptic warnings, referencing Python 2 packages:

python-fasttext W: Referenced library 'urllib2' is an uninstalled dependency
...

Not sure what to make out of this, but, then again, the fasttext Python module’s code is not exactly best-practice, in general.

Dear @peippo,

Is there a reason to keep both python2-setuptools and python-setuptools in the makedepends ? As far as I can tell, the python2 is not required but filling it means installing python2, even though they have been removed from the official repositories.

Cheers,