Arch Linux User Repository

PSA: I've started hosting this as a prebuilt package in my repository for those that want to install it using pacman without messing around with building from the AUR.

Last version 2.1.3 upon compilation and testing gives following error:

/usr/lib/python3.10/site-packages/pytest_asyncio/plugin.py:191: DeprecationWarning: The 'asyncio_mode' default value will change to 'strict' in future, please explicitly use 'asyncio_mode=strict' or 'asyncio_mode=auto' in pytest configuration file. config.issue_config_time_warning(LEGACY_MODE, stacklevel=2)

panflute/io.py:140 /home/user/.cache/yay/python-panflute/src/panflute-2.1.3/panflute/io.py:140: DeprecationWarning: invalid escape sequence '*' """

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html =========================== short test summary info ============================ FAILED tests/test_panfl.py::test_get_filter_dirs - AssertionError: assert ['/... =========== 1 failed, 29 passed, 1 deselected, 2 warnings in 13.71s ============ ==> ERROR: A failure occurred in check(). Aborting... -> error making: python-panflute

This indicates that panflute-2.1.3/panflute/io.py:140 probably needs to be patched, erasing an illegal character.

@tzok I would have loved to, but the AUR guidelines explicitly discourage bumping packages for rebuilds like that (even though it's by far the easiest and cleanest way to make sure it gets done and rolls out to everybody). I realize a lot of folks do it anyway, but I'd rather play by the rules (and lobby to get them changed). For now please rebuild yourself (if using yay for example, try yay --rebuild -S python-panflute).

Please bump the pkgrel, because with Python 3.9 in extra, this package needs a rebuild.

@rien333 Apparently the main culprit is tables. I've relaxed the dependency version restrition and added a warning on this package, but I've kept the restriction on python-pantable which is completely out in the cold with Pandoc 2.10.

I was trying to save anybody else from ending up in the same predicament in production where everything stops working on an update.

Pandoc 2.10 has been in the arch repos for almost 2 months, so I think most have either already found an alternative (e.g. downgrading pandoc) or are unaffected (I use my own panflute filters everyday, and have not noticed any problem). On the other hand, new users might be confused when panflute suddenly doesn't work.

It's your call, but you could also just print a warning for now. I can imagine that users might think that downgrading pandoc is a little too much hassle, especially because it has a lot of dependencies.

@rien333 If it's true that only some filters are problematic I might consider relaxing that restriction (although you can also choose to ignore it at install time if you insist on proceeding). My experience was that all my filter jobs across the board stopped working and the only way I got them back was downgrading Pandoc. I was trying to save anybody else from ending up in the same predicament in production where everything stops working on an update.

@caleb Ah, I see. Unlike some, I wasn't really hit by any compatibility issues (I guess only specific panflute scripts are affected).

@rien333 Yup, that's kind of the point. You can't upgrade this right now, and this requirement is to block systems that happen to have not ungraded Pandoc yet so that the user knows they have to choose between this and the latest Pandoc. They can't have both.

Until this is resolved upstream with Pandoc 2.10 support the only workaround is to find a Pandoc 2.9.x package on an Arch mirror that keeps old versions around (there are some that have archives) and use that to provide this dependency.

btw: I get

 -> Could not find all required packages:
    pandoc<2.10.0 (Wanted by: python-panflute)

when trying to upgrade this package to the newest version.

PSA: I've started hosting this as a prebuilt package in my repository for those that want to install it using pacman without messing around with building from the AUR.