Arch Linux User Repository

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 checkdepends array. (This incidentally also goes for the multiple dependencies for the mypy tests, 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

Hi, not quite sure what happened to papis-sphinx-design (extra) but it looks like it has been removed:

https://archlinux.org/packages/extra/any/python-sphinx-design/

(note: page 404s)

There's no papis-sphinx-design in the AUR, but there does exist a papis-sphinx_design (note the underscore)

Indeed, the dep was added in ee408cda0183d8a54ab61eaf41907e6c6dacb5cf. Thanks for flagging this, @homocomputeris! The python-flake8-pyproject build failure is a problem in that package, I'm working on a patch for that to be posted there.

The pkg fails to build:

error: can't build papis-git-0.13.r443.gb6fe8962-4, deps not satisfied: python-flake8-pyproject
error: packages failed to build: python-flake8-pyproject-1.2.3-2  papis-git-0.13.r443.gb6fe8962-4

==> Making package: python-flake8-pyproject 1.2.3-2 (Сб 28 сен 2024 16:36:43)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found 1.2.3.tar.gz
==> Validating source files with sha256sums...
    1.2.3.tar.gz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting 1.2.3.tar.gz with bsdtar
==> Sources are ready.
python-flake8-pyproject-1.2.3-2: parsing pkg list...
==> Making package: python-flake8-pyproject 1.2.3-2 (Сб 28 сен 2024 16:36:46)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting build()...
* Getting build dependencies for wheel...

ERROR Missing dependencies:
    Flake8>=5
    pycodestyle>=2.12.0
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'python-flake8-pyproject-1.2.3-2': 

Seems like we require python-sphinx-design for papis to build now. Could you verify and add to the builddeps?

@m040601 Sorry for the delay in answering. Given the drift in dependencies since the last version, I think I'll wait to adopt the package until the next release, if no one else picks it up by then. It shouldn't be too much of a burden, just freezing a version of the -git PKGBUILD upon each release.

You may have noticed I've adopted python-doi and python-habanero. I had forgotten you pointed it out to me, so this was a fortunate accident (this is also part of why I didn't adopt python-arxiv2bib, the other being that it's not a dependency of papis-git.)

Thanks for the heads' up and for keeping me posted!

@gesh:

Jp-Ellis just abandoned the "papis" PKGBUILD, https://aur.archlinux.org/packages/papis.

Would you like to adopt it ? That would be great if you could.

I personally dont have the skills to this task. But I can of course help with testing and keeping a close watch.

• python-arxiv2bib
• python-doi
• python-habanero

were also abandoned.

Yeah, https://github.com/papis/papis/pull/607 changed over to pyprojecct and I haven't yet had time (probably won't for next week or two either) to update it. Thanks for the report, it'll make it easier when I do get arouund to it!

flake8 test was failing. Although max-line-length = 88 was set on pyproject.toml flake8 kept on throwing the E501: line too long (82>79).

Learned from vscode-flake8 that python-flake8-pyproject was required for flake8 to read from pyproject.toml

After installing it flake8 succeeded.

Is this just my issue or is someone else facing the same? flake8 - 1:7.0.0-1

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 checkdepends array. (This incidentally also goes for the multiple dependencies for the mypy tests, 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

@gesh

Thanks for the detailed clarification. As an AUR end user, it's very nice to know that you take this "job" serious. And make an effort to at least check out what the "papis" PKGBUILD is doing.

I left a notice there, so that the "papis" PKGBUILD" maintainers can be aware of that clarification and choices.

Hope you guys can collaborate and share work.

  • Not sure what your complaint is in re optdeps -- my original comment was iirc in re the optdepends all being written
    in one line, not much more.

Yeah. My fault, just forget it. My misreading. I saw the word "break" and got that wrong. I misread the sentence and was "afraid" of optional stuff being force pushed.

... optdeps like the scihub and libgen integration ...

And html. And also "zotero" integration.

All my talk about this is because I realized many of these are reallly "killer" addons for "papis". But they need to be well maintained and monitored on the AUR.

The "zotero" integration for example, is called "zotero" but can do much more than just deal with zotero import/export.

"papis zotero serve"

It is a little buried in the docs, but it lets you press the extension button in Firefox, and have your bib entry in the Papis database, completely bypassing Zotero. It's not quite evident from the name that it can do that. Zotero (the GUI, the sqlited db app) is irrelevant in that case. Only the "connector" Zotere firefox extension matters and does the astonishing heavy work of pulling structured information from thousands of different kinds of webpages as a ready made bib entry. That will directly land into your nice papis yaml file.

I really should put this stuff in the Arch wiki. I think not many people are aware.

The other thing with these papis "scripts" and extensions is that they dont get the same attention as the main repo by the papis devs themselves and lag many commits behind.

That might also be understandable in the case of 'libgen' and 'scihub' because of eventual legal issues. But that's also why I want to make sure that stuff in the AUR does get monitored regurlarly.

  • What breakage have you seen that you say

    This is not the easiest PKGBUILD to maintain. It breaks easly.

I basically meant to say that because of its necessary many dependencies on the AUR, the chances of one of them being out of date or unmaintained are higher. Not "papis" PKGBUILD itself fault. But it still affects it. I see this a lot with other python tools on the AUR.

So, thank again for the work in the PKGBUILD.

That's also why i really hope that one day one of the Arch official maintainers could adopt this tool. I've been following it and others (cobib, pubs) for some years now.

But only now did "papis" start to "click" for me. Because it is thought from the ground up to integrate well with others. It has seen a tremendous amount of cumulative work in the last years.

Would be usefull for so many people in Arch doing bib management. It is a really well maintained, moving forward, underrated project in my opinion. But I guess not many people are aware of it. And Zotero "steals" a lot of attention.

  • While you can install plugins via pip, I'd recommend against mixing vendoring options like that

I did not say 'pip'. I said 'pipx'. I never use neither 'pip' , nor 'pip --user'.

But pipx is a different beast.Is an interesting "clean" solution for those cases where that rare AUR PKGBUILD is hopelessly abandonedd unmaitained , and you do need the tool. It's more for "little cli" tools and less for "little libs". So it works for papis scihub/libgen, but not for papis zotero.