Package Details: pdfcpu 0.7.0-1

Git Clone URL: https://aur.archlinux.org/pdfcpu.git (read-only, click to copy)
Package Base: pdfcpu
Description: A PDF processor written in Go.
Upstream URL: https://github.com/hhrutter/pdfcpu
Keywords: cli go pdf
Licenses: Apache
Submitter: Rubo
Maintainer: Rubo
Last Packager: Rubo
Votes: 2
Popularity: 0.007039
First Submitted: 2022-09-26 18:26 (UTC)
Last Updated: 2024-03-05 19:12 (UTC)

Dependencies (1)

Required by (0)

Sources (1)

Latest Comments

Rubo commented on 2023-12-16 12:21 (UTC)

@alerque thanks, done.

alerque commented on 2023-12-16 12:16 (UTC)

This doesn't need to be marked as conflicting with anything at all as it is the base package name. All variants (VCS/bin/etc.) should conflict with this (and will automatically conflict with each other. As the base package name you don't need to specify any conflicts here.

alerque commented on 2023-12-10 11:57 (UTC)

@Rubo This is water under the bridge now, but your checksum for v0.5.0 was wrong. You can see in Git history you had b3c554918559db85662f8c9252d9a9a7e2ec3db2c177493bc2bc1f9627f35de69f28ab056d13c02ae05cfd9f3cfb40560f2970c6c5e757a72f0b7cd27344a27f, but you can verify this is incorrect with:

$ curl -s https://github.com/hhrutter/pdfcpu/archive/v0.5.0.tar.gz | b2sum
786a02f742015903c6c6fd852552d272912f4740e15847618a86e217f71f5419d25e1031afee585313896444934eb04b903a685b1448b755d56f701afe9be2ce  -

This generally happens because upstream re-tagged a release after you downloaded your sources. Just rebuilding isn't enough to catch this, you need to clear your sources cache (not just the src directory but the makepkg source cache dir if you have one).

Rubo commented on 2023-08-21 21:34 (UTC) (edited on 2023-08-21 21:45 (UTC) by Rubo)

@alerque I have just rebuilt it and I didn't get any mismatch on the checksum. Can you please provide more info about your issue? What is the actual output of makepkg?

alerque commented on 2023-08-21 20:13 (UTC)

I think upstream must have retagged. I get a different checksum than you did for 0.5.0? Can you look into what happened and tag a -2 pkgrel if nothing bad happened upstream so this can be buildable again?