Package Details: papis 0.14.1-1

Git Clone URL: https://aur.archlinux.org/papis.git (read-only, click to copy)
Package Base: papis
Description: Command-line document and bibliography manager
Upstream URL: https://github.com/papis/papis
Licenses: GPL-3.0-or-later
Submitter: JP-Ellis
Maintainer: gesh (tuurep)
Last Packager: gesh
Votes: 18
Popularity: 0.42
First Submitted: 2018-08-13 20:42 (UTC)
Last Updated: 2025-03-16 19:12 (UTC)

Dependencies (44)

Sources (1)

Pinned Comments

Latest Comments

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

poshd commented on 2024-09-24 11:20 (UTC)

I am a new user of papis, and I've noticed that this package does not have the papis tag command mentioned on the documentation website.

ExpandingMan commented on 2024-05-22 13:48 (UTC)

Thanks @kkoyung, that worked! I thought clean build all would do whatever --rebuildtree does but I guess not.

For whatever it's worth, this is hardly the first time that I've had an apparently working package break on install because of inexplicably failing unit tests in the pkgbuild, so to me this seems like another data point disfavoring that practice.

kkoyung commented on 2024-05-22 04:53 (UTC) (edited on 2024-05-22 10:44 (UTC) by kkoyung)

@ExpandingMan I also had the problem of having many test errors during installing papis via yay. I guess it could be related to recent python 3.12.3 update in archlinux repo. After python major update, all python AUR packages has to be rebuilt.

Try yay -S --rebuildtree papis. (I don't know why --rebuildtree doesn't work on my machine. So, I first yay -Rs papis to remove papis and its dependencies, assuming no other package depends those dependencies, clear cache by yay -Sc and install them back by yay -S papis. This works for me.)

Edit: add a step to clean cache

gesh commented on 2024-05-21 20:05 (UTC)

--nocheck is a flag for makepkg. I was presuming, given the introductory warning in https://wiki.archlinux.org/title/AUR_helpers, that once yay failed, you'd be manually trying to build using makepkg.

Given that this builds for me using both makepkg and pkgctl, I'm presuming this is a bad interaction with yay, which I have absolutely no experience with.

That said, despite the "more than just a few errors", it may be of use to see the error logs.

ExpandingMan commented on 2024-05-21 18:45 (UTC)

This still breaks pretty spectacularly for me. There are more than just a few errors that I could report, in spite of the fact that it previously seemed to be working fine. What takes the --nocheck argument? I'm using yay and I'm not aware of anyway to bypass these tests.

gesh commented on 2024-05-21 16:07 (UTC)

Fair enough

BoostCookie commented on 2024-05-21 15:37 (UTC)

Yes, works for me now as well, even with test_arxiv.py. I don't know what went wrong previously. But I don't want to update the PKGBUILD again. Let's just keep it and reevaluate the tests when the next version releases.

gesh commented on 2024-05-21 15:13 (UTC) (edited on 2024-05-21 15:16 (UTC) by gesh)

For reference, I built with

pkgctl build \
    -I /home/gesh/.local/var/cache/pacman/packages/python-arxiv2bib-1.0.8-1-any.pkg.tar \
    -I /home/gesh/.local/var/cache/pacman/packages/python-bibtexparser-1.4.1-2-any.pkg.tar \
    -I /home/gesh/.local/var/cache/pacman/packages/python-doi-0.2.0-3-any.pkg.tar \
    -I /home/gesh/.local/var/cache/pacman/packages/python-habanero-1.2.6-3-any.pkg.tar \
    -I /home/gesh/.local/var/cache/pacman/packages/python-isbnlib-3.10.14-3-any.pkg.tar \
    -I /home/gesh/.local/var/cache/pacman/packages/python-markdownify-0.12.1-1-any.pkg.tar

and with

check() {
  cd "${pkgname}-${pkgver}"
  python -m pytest papis tests \
    -k 'not (test_config.py and test_get_configuration)'
}

gesh commented on 2024-05-21 15:08 (UTC)

Just checked again with the test_arxiv.py tests enabled, and tests pass for me. Are you guys sure you have the up-to-date python-arxiv2bib installed?

@ExpandingMan In re whether tests are necessary... it's a bit of a judgement call what tests to include in the PKGBUILD. My rule of thumb is that for binary packages, you only want to test the functionality testsuite (in this case, pytest), whereas for VCS packages (which are more at risk of breakage) you test everything upstream usually tests (hence why in the -git package I also added flake8 and mypy tests, though the former is probably less necessary than the latter). After all, upstream's testing resources are finite, and some breakage might slip through the cracks.

You can always --nocheck if you're willing to take upstream at their word that things are fine, though.

gesh commented on 2024-05-20 20:04 (UTC)

Could you both try https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot ?

I.e. having installed devtools, build with pkgctl build, passing -I $pacmanPkgCache/$PKG.pkg.tar… for each AUR dependency.

In my case, this built perfectly fine yesterday, haven't yet checked against latest updates.

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