Arch Linux User Repository

I am using pyenv (but it's using the system python). I wonder if that might be causing the issue. @amish are you using pyenv?

I got the same errors using yay, but could the packages build with ccm in a fresh sandbox. Nevertheless, it does not work afterwards...

So it is disturbed by an other installed package, but I have no clue at the moment which one this may be. The last version worked without an issue.

@amish: I was unable to reproduce the issue, so I'm left with stating "it works for me" on a freshly created Arch Linux virtual machine.

@Morbius - I could not gather from your reply if you were able to figure out the issue or you need some more information?

It seems easy enough to find information about what might cause these errors. What surprises me is that I don't see these errors during CI builds (using Python versions 3.7 through 3.11, inclusively). I also created a minimal Arch Linux VM and successfully installed this package using yay -S python-fangfrisch -- no errors there either, and Fangfrisch works fine after the installation process completes. I am stumped.

@amish: As visible in the Git repository, no new requirements have been introduced in Fangfrisch 1.6.0.

Most errors are related to db.py

@Morbius - is there a new module dependency?

Currently, dependencies are as follows: python-requests, python-sqlalchemy, python-setuptools

Is there any new module that needs to be added?

Hi @amish and @Morbius

Thanks for your response, here are the errors I'm getting.

@Morbius - you can wait till @Ferdinand and @emphire post their output.

For me, as I stated earlier, tests are running fine with OK at the end.

A number of test cases for Fangfrisch are supposed to result in errors. See CI build https://github.com/rseichter/fangfrisch/actions/runs/4213125243/jobs/7312635257 as an example. These particular errors are expected, and the Python test suite is expected to fail if no errors occur. As long as the test suite exits with OK, things are fine, as in the CI builds. I hope this helps. I don't currently have an Arch Linux host available for testing, and I would need detailed information/output before I consider investing time and effort in this matter. Just as @amish states that he is not a Python expert, I am no Arch Linux expert, and of AUR builds I know even less.

@Ferdinand and @emphire

For me check() runs fine. See output below.

So please provide complete check() output in your case.

@Morbius (fangfrisch author) - can you please check once they post errors. I am not python expert, so I would not be able to debug.

==> 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 16.687s

OK