Package Details: python-fangfrisch 1.9.0-5

Git Clone URL: https://aur.archlinux.org/python-fangfrisch.git (read-only, click to copy)
Package Base: python-fangfrisch
Description: Freshclam like utility that allows downloading unofficial virus definition files
Upstream URL: https://rseichter.github.io/fangfrisch/
Licenses: GPL
Conflicts: clamav-unofficial-sigs
Provides: clamav-unofficial-sigs
Submitter: amish
Maintainer: amish (Morbius)
Last Packager: amish
Votes: 27
Popularity: 0.048060
First Submitted: 2020-02-22 16:48 (UTC)
Last Updated: 2024-12-28 11:19 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

Morbius commented on 2023-02-21 14:28 (UTC) (edited on 2023-02-21 15:25 (UTC) by Morbius)

@amish: I just released Fangfrisch 1.6.1, which now lists SQLAlchemy >= 1.4.0 as a requirement. There are no other changes relative to version 1.6.0.

As a side note, I suggest you consider changing the timer to invoke Fangfrisch every 5-10 minutes instead of hourly. Fangfrisch tracks when files were last downloaded for each data source, so it won't cause undue traffic. The current "hourly" setting in the timer file prevents sources to be contacted more frequently even if the user configures something like "every 15 minutes" in fangfrisch.conf, which can cause confusion, because this Arch Linux specific limitation is undocumented.

amish commented on 2023-02-21 13:49 (UTC)

@Morbius - Ah! Ok. Fair enough :)

Morbius commented on 2023-02-21 10:38 (UTC) (edited on 2023-02-21 10:41 (UTC) by Morbius)

@amish: The current version of SQLAlchemy is 2.0.4, with 1.4.0 released in March 2021. I was unaware that any distribution still bundled version 1.3, which is to my knowledge no longer being maintained by the SQLAlchemy developers. Still, I realise that I forgot to modify setup.py to list 1.4 as a minimal requirement, and I shall fix that later today. Sorry, I should have thought of that.

amish commented on 2023-02-21 10:12 (UTC)

@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.

Morbius commented on 2023-02-21 09:21 (UTC)

@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.

amish commented on 2023-02-21 09:04 (UTC) (edited on 2023-02-21 09:05 (UTC) by amish)

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.

samueldy commented on 2023-02-21 09:01 (UTC) (edited on 2023-02-21 10:22 (UTC) by samueldy)

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.

Morbius commented on 2023-02-21 08:48 (UTC)

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.

emphire commented on 2023-02-21 08:32 (UTC)

@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.

amish commented on 2023-02-21 08:16 (UTC)

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