| Git Clone URL: | https://aur.archlinux.org/papis-git.git (read-only, click to copy) |
|---|---|
| Package Base: | papis-git |
| Description: | Command-line document and bibliography manager |
| Upstream URL: | https://github.com/papis/papis |
| Licenses: | GPL-3.0-or-later |
| Conflicts: | papis |
| Provides: | papis |
| Submitter: | sonam |
| Maintainer: | sonam (gesh, tuurep) |
| Last Packager: | gesh |
| Votes: | 5 |
| Popularity: | 0.022306 |
| First Submitted: | 2020-12-29 06:22 (UTC) |
| Last Updated: | 2026-08-24 20:08 (UTC) |
@virgiliusm -- does anybody actually have a version bound on papis? I'll add it for consistency with my other -git packages, but I'm surprised you need it.
Also, VCS packages should only be flagged out-of-date if they fail to build against the project's HEAD -- it is understood they track the project's main development branch -- this is why pkgver() exists, after all.
provides=('papis') should probably be versioned as provides=("papis=${pkgver}"), otherwise papis-git cannot satisfy versioned dependencies such as papis>=0.15.
@m040601
Thanks for the kind words! It was indeed hard to get set up with this, and I needed to develop tooling for it. Thankfully, now that's done it's mostly a matter of code review, checking the tests don't break on Arch's bleeding edge, and keeping up to date with Python packaging best practices.
I'm glad you're finding the package useful!
And thanks for the head's up on the funding, will congratulate upstream for it.
@gesh
Thanks for continuing to maintain this python tool. Very much appreciated.
Just to let you know, I just updated to 0.15, and everything seems be working fine. One of my most time intensive and complicated python PKGBUILD's ... big huge compilation ... this must not be an easy PKGBUILD to maintain ... :)
Anyways, some good news also, seems like papis is getting some funding from the EU in March 2026, https://nlnet.nl/project/Papis/
Thanks for the great investigation
At a guess, this is unfortunately a problem with python-isbnlib -- it needs to have https://github.com/xlcnd/isbnlib/pull/145 merged to avoid this warning.
Unfortunately, its upstream seems abandoned -- the last commit there was in 2023-07. I'm similarly concerned about the maintenance status of python-whoosh -- https://github.com/mchaput/whoosh last updated 4y ago, https://github.com/Sygil-Dev/whoosh-reloaded abandoned the project, and https://github.com/de-odex/whoosh-novo said on 2025-05-22 that they won't be free to maintain the project for the next 6 months.
I will be flagging this with the papis upstream, hopefully they have good ideas.
EDIT: Done https://github.com/papis/papis/issues/1030
I'm getting this warning in the terminal when running any papis command, or when tab completing:
/usr/lib/python3.13/site-packages/isbnlib/registry.py:6: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.
from pkg_resources import iter_entry_points
but not when building papis from source on the latest commit, is this something that could be fixed here?
@gesh I've seen in the comments that you might want to take over papis (AUR), now that 0.14 is released
https://github.com/papis/papis/releases/tag/v0.14
The current maintainer asked if I want it but it looks like you may know what to do with it?
Oh yes, sorry for the confusion
That's the point -- the canonical name for the dependency is python-sphinx-design, and indeed python-sphinx_design provides python-sphinx-design.
That is why it appears in parentheses in the dependency list here in the webui. It is indeed one way of providing the required dependency, though another would be to just resurrect https://gitlab.archlinux.org/archlinux/packaging/packages/python-sphinx-design or download it from https://archive.archlinux.org/packages/p/python-sphinx-design/ (neither of which I recommend, though, given that nobody's maintaining them).
Pinned Comments
gesh commented on 2024-03-13 11:15 (UTC)
Note! Papis skips integration tests for certain optdeps if they aren't installed[1]. Since checkdeps should contain all the dependencies to check a standard build, I've added these to
checkdepends.If you're not planning on installing these optdeps and want to skip these specific tests, feel free to comment out the relevant lines in the
checkdependsarray. (This incidentally also goes for the multiple dependencies for themypytests, if they bother people).The relevant dependencies at this time are:
python-jinja,python-markdownify,python-whoosh[1] - https://github.com/papis/papis/issues/776#issuecomment-1991874151