Just also a reminder: We are for sure not "Arch GNU/Linux" any longer and our compatibility is and will going to vanish very soon. Even though packages like img2pdf are not included for a reason: They are impossible to build correct in a clean chroot-environment as their dependency is also not possible to be resolved (meaning therefore the dependencies). Here is a log from earlier tryouts: | WARNING: The pip package is not available, falling back to EasyInstall for handling setup_requires/test_requires; this is deprecated and will be removed in a future version.
| Download error on https://pypi.org/simple/setuptools_scm_git_archive/: [Errno -3] Temporary failure in name resolution -- Some packages may not be found!
| Download error on https://pypi.org/simple/setuptools-scm-git-archive/: [Errno -3] Temporary failure in name resolution -- Some packages may not be found!
| Couldn't find index page for 'setuptools_scm_git_archive' (maybe misspelled?)
To explain: Even to have some stable tarball does not mean the concurrent package is respecting no further download. This is not supported within our build-environment and therefore it is not possible to include those packages, to be called for sure not clean for building. And yes: I understand absolutely the point to include more packages at a time and using the PKGBUILD-scripts back from Arch GNU/Linux at all. 
Nevertheless: The warning stays as to be seen above. Those packages and PKGBUILD-scripts can be only source for further ways from now on. Many are not designed very good or even worse just built without any clean environment and just uploaded as finished package. So there is this illusion they work in some way. They do not work and will not ever work for real!
The best way for testing is to setup libretools and use a chroot-environment. The commands makepkg and libremakepkg are not fully comparable at all, right from the beginning makepkg is absolutely tolerant for anything to be downloaded in between. But the chroot-environment is for sure not and very strict: One phase for collecting, afterwards building, checking and packaging without any further connection. Missing dependencies? Or wrong defined parameters will lead to an immediate ending of the process while makepkg stay a bit longer or tolerate them through downloading (to be seen in the log above as difference). And makepkg is using local installed files and packages, even when not defined within depends or makedepends. The result is not a clean package at all, not possible for used within chroot-environments and therefore also not possible to be included within the repositories. That's the reasoning when we exclude packages besides being incompatible, unfree, insecure or more. And with the dependency-example above: There is the deprecated-warning for everyone being alarmed that our way without python-pip is not possible for long with it. It is just rational to left out those packages as they are of no use and other applications using them the same.
]]>