Arch Linux User Repository

I just took over as maintainer of this package. I did some adjustments to the PKGBUILD, including removing some dependencies. If this has broken anything, please let me know!

Thanks for picking this up, was intending to do so once 0.14 was released.

A few remarks: You want python-yaml in your depends, not pyaml -- I recently pushed a commit to papis-git that fixes that. You might also want to pick up the optdepends from there. Also, licenses should be specified in SPDX nowadays, ie GPL-3.0-or-later.

I'm pretty sure you'll need to add python-chardet and switch python-arxiv2bib -> python-arxiv once 0.14 drops, though I don't 100% recall whether python-typing_extensions is necessary. (Actually, going over things like this makes me wonder at the status of python-chardet -- is it a hard or optdepend? Will need to contact upstream later today to check).

You may want to add at least the pytest checks, I added the others out of perfectionism.

Last and least, you probably want to sort the depends array and break makedepends into multiple lines -- that makes it more legible.

Thanks again for picking this up, I prefer only packaging things I actually use, which in my case is papis-git.

@ExpandingMan I don't know what happened in your case. The dependency is still in the PKGBUILD and every decent AUR helper should therefore install it.

That's it, sorry about that, was expecting all the dependencies to be installed with it. That seems to have been the case previously.

@ExpandingMan

Are you sure you have the dependency python-doi installed? pacman -Qs python-doi

getting

Error while loading entrypoint 'EntryPoint(name='add', value='papis.commands.add:cli', group='papis.command')': No module named 'doi'.
Error while loading entrypoint 'EntryPoint(name='addto', value='papis.commands.addto:cli', group='papis.command')': No module named 'doi'.
Error while loading entrypoint 'EntryPoint(name='bibtex', value='papis.commands.bibtex:cli', group='papis.command')': No module named 'doi'.
Error while loading entrypoint 'EntryPoint(name='citations', value='papis.commands.citations:cli', group='papis.command')': No module named 'doi'.
Error while loading entrypoint 'EntryPoint(name='explore', value='papis.commands.explore:cli', group='papis.command')': No module named 'doi'.
Error while loading entrypoint 'EntryPoint(name='crossref', value='papis.crossref:FromCrossrefImporter', group='papis.importer')': No module named 'doi'.
Error while loading entrypoint 'EntryPoint(name='doi', value='papis.crossref:Importer', group='papis.importer')': No module named 'doi'.
Error while loading entrypoint 'EntryPoint(name='folder', value='papis.commands.add:FromFolderImporter', group='papis.importer')': No module named 'doi'.
Error while loading entrypoint 'EntryPoint(name='isbn', value='papis.isbn:Importer', group='papis.importer')': No module named 'isbnlib'.
Error while loading entrypoint 'EntryPoint(name='lib', value='papis.commands.add:FromLibImporter', group='papis.importer')': No module named 'doi'.
Error while loading entrypoint 'EntryPoint(name='pdf2doi', value='papis.crossref:DoiFromPdfImporter', group='papis.importer')': No module named 'doi'.
Error while loading entrypoint 'EntryPoint(name='serve', value='papis.commands.serve:cli', group='papis.command')': No module named 'doi'.

on every call to papis.

I just took over as maintainer of this package. I did some adjustments to the PKGBUILD, including removing some dependencies. If this has broken anything, please let me know!

python-setuptools is necessary as a makedepend in a clean chroot

I was intrigued by the differences between "papis" and "papis-git" PKGBUILD, and the upcoming v0.14 version.

The maintainer of the "papis-git" PKGBUILD has left a very nice description of the differences in this comment, https://aur.archlinux.org/packages/papis-git#comment-959872

There is also the question of the maintenance of the many other possible papis addons, (scihub, zotero etc) in the AUR.

Would be nice if the maintainers of these two PKGBUILD's "papis" and "papis-git" collaborated and shared the maintanence of both PKGBUILDS.

These would avoid reduplicating work, and would provide more pairs of eyes watching this very usefull tool.

With enough votes and concentrated effort this might even one day turn into an official Arch package.

@JP-Ellis

Papis has this dependency on "python-bibtexparser", https://aur.archlinux.org/packages/python-bibtexparser

But "python-bibtexparser" is, an AUR dependency, is out of date and was ... orphaned ??? ...

I'm not very confortable with too may AUR dependencies, if they are not properly watched.

My naive question is:

Is there any way to "replace" this "python-bibtexparser" dependency for "papis" ? Could some sort of "replacement" from from the official Arch repos be used ?

I noticed this one,

extra/python-pybtex 0.24.0-5
    A BibTeX-compatible bibliography processor written in Python

Or is it really impossible to find a substitute, and this is really a mandatory thing for "papis" ?

@JP-Ellis

How are you yourself or other Arch users using "papis" ? Or some other text oriented or command line tool in this field ? Did you commmit to using it for a long time (years) ?

Can you recommend me some blog posts, personal experiences, wiki pages etc, from people describing their (academic) workflow using papis or some other command line bib manager ?

I cant find a place where Arch users, academics or not, share their experiences in this field. The "Arch way".That is, similar related simple tools, preferably cli, working in tandem with other simple tools.

I'm having a lot of trouble finding time tested, "real world" experiences, that last a life long. There is a lot of stuff on the Internet. And I personally know a lot of academic people that need to work with this on a dailly basis. But they are not Linux users. And they couldnt care less about using big bloated tools. They would never touch a command line or use a text oriented workflow.

I know papis from some years now. Read all the README's and wiki pages. Same thing for similar tools like "cobib" "pubs" etc. I'm trying to compare them. Cant decide which one to invest time in learning it properly. Zotero, Jabref, Calibre and all that. But I never commited to using one long term.

I have a distaste for propietary tools, GUI's, and browser based workflows . Spent too much time finding the tools, but have not yet decided where to invest my time. I am a power command line user, but I have never managed to integrate all of this in stable workflow.

Recently, for personal reasons, I've been amassing a ton of pdf's and bib references in a humanities field. I'm overwhelmed. I'm loosing control of my files and references collections.

I feel overloaded with information, and I am loosing stuff and redownloading pdf's. Also need to integrate with Zotero and all. I guess it is not so much a matter of the right tool, but more a matter of finding the right workflow.