Arch Linux User Repository

@Morbius - I believe it would affect any distribution which uses python-alchemy 1.3 instead of 1.4. But its your choice, if to make it backward compatible or not.

@amish: Also, you will probably understand me when I say that I won’t change Fangfrisch to deal with a problem that only affects one particular Linux distribution.

python-sqlachemy1.3 provides python-sqlachemy but it appears that tests are not compatible with python-sqlachemy 1.3 but requires 1.4.

So either @Morbius needs to update tests to succeed on python-sqlalchemy 1.3 version OR people move to its version 1.4

Based on Arch's "always up-to-date" principle, I would say that people need to move to python-alchemy 1.4 as eventually 1.3 will be removed from repos anyway.

Can confirm from my end that replacing python-sqlalchemy1.3 with python-sqlalchemy allows the check() to succeed:

==> Starting check()...
....................CRITICAL: Database table automx2 is not empty
CRITICAL: Database table automx2 is not empty
.........CRITICAL: Unexpected database version (expected 2, got -1)
CRITICAL: Unexpected database version (expected 2, got -1)
CRITICAL: Please try running "initdb"
CRITICAL: Please try running "initdb"
............................................
----------------------------------------------------------------------
Ran 73 tests in 9.643s

OK

So python-sqlalchemy needs to be in checkdepends as well as in depends? Hopefully this won't cause too much conflict. Looks like in the official repos only pgadmin4, pychess, and sopel depend on python-sqlalchemy1.3 specifically.

Given that the changes in Fangfrisch 1.6.0 are mostly related to the way SQLAlchemy sessions are handled, as stated in the change log, @emphire is probably on the right track.

@amish I tried it with the python packages you listed and the tests passed. I had to uninstall python-sqlalchemy1.3 to get python-sqlalchemy installed and if I had to guess I'd be guessing that one is the culprit.

Can those getting error, install python-* packages mentioned in my previous comment.

And then test if it works. If yes then we need to figure out which package is dependency.

Little bit of manual work required but it should resolve the issue

Sorry for the late reply.

Here are the errors I get after running 'makepkg -sric': http://ix.io/4oLj

No pyenv, and no VM or container or anything. Python 3.10.9.

I also deleted and re-cloned the repository, and tried again, but get the same errors.

@emphire - no I am not using pyenv.

I am building directly (without chroot or sandbox or container)

And it builds fine.

Here is the list of python related packages in my system. If that helps in anyway.

i.e. output of: pacman -Qqs ^python

ansible-core
dbus-python
pyalpm
python
python-autocommand
python-bcrypt
python-cairo
python-certifi
python-cffi
python-chardet
python-cryptography
python-deprecation
python-distro
python-eyed3
python-fastjsonschema
python-filetype
python-gobject
python-greenlet
python-idna
python-inflect
python-jaraco.context
python-jaraco.functools
python-jaraco.text
python-jinja
python-markupsafe
python-more-itertools
python-ordered-set
python-packaging
python-paramiko
python-platformdirs
python-ply
python-psutil
python-pycparser
python-pycups
python-pycurl
python-pydantic
python-pyelftools
python-pyinotify
python-pynacl
python-requests
python-resolvelib
python-setuptools
python-shiboken2
python-six
python-sqlalchemy
python-systemd
python-tomli
python-trove-classifiers
python-typing_extensions
python-urllib3
python-validate-pyproject
python-yaml
zbar

If it helps, here is my makepkg output using system Python 3.10.9 (no pyenv, venv, conda env): https://pastebin.com/77QRqEDk