Package Details: grim-git 1.4.0.r6.g1573b1020ce2-2

Git Clone URL: (read-only, click to copy)
Package Base: grim-git
Description: Grab images from a Wayland compositor
Upstream URL:
Keywords: screenshot
Licenses: MIT
Conflicts: grim
Provides: grim
Submitter: emersion
Maintainer: emersion
Last Packager: emersion
Votes: 16
Popularity: 0.003019
First Submitted: 2018-05-13 20:49 (UTC)
Last Updated: 2022-09-28 19:50 (UTC)

Required by (61)

Sources (1)

Latest Comments

1 2 Next › Last »

emersion commented on 2022-09-28 19:51 (UTC)

Done, and started a discussion on the wiki:

yrlf commented on 2022-09-28 19:31 (UTC)

@emersion: please add --abbrev=12 to the git describe call so that other users can consistently generate package versions that match with what is in your PKGBUILD.

Otherwise the package will always be detected as out of date, regardless of whether it was already updated a minute ago or not, which is annoying.

emersion commented on 2022-07-14 19:12 (UTC)

Yeah, probably due to core.abbrev, setup as indicated in (end of section). Would be nice to update the Arch wiki to provide more robust pkgver() functions.

yrlf commented on 2022-07-14 18:52 (UTC)

@emersion: please fix your package version. the version committed into PKGBUILD and .SRCINFO has a longer git hash than is generated by the pkgver() function on a default ArchLinux install, which causes the version in the AUR to always appear to be newer than what is installed, meaning every user of this package has to rebuild grim-git every time they update.

The easiest way to fix this is to run makepkg in your package directory and just using the version that is automatically updated into the PKGBUILD by pkgver().

If pkgver() generates a longer commit hash on your system then please either change the pkgver() function to explicitly generate hashes with a fixed length or fix your dev system.

tpkee commented on 2022-06-15 16:53 (UTC)

@justinesmithies same, I even tried reinstalling. It's annoying as hell

justinesmithies commented on 2022-06-04 15:28 (UTC)

Since this latest update no matter how many times i update this package always says there's an update but then goes onto say it's already upto date. I've tried removing from cache too but still the same.

Aur (1) grim-git-1.4.0.r6.g1573b1020ce2-1

Is the line i get and never clears.

unmellow commented on 2022-06-03 00:35 (UTC)

upstream has been moved to My random issue I mentioned in the out of date flag

was fixed via following the instructions at

and is unrelated to this

Scrumplex commented on 2022-02-09 19:23 (UTC)

Can you install the completions into their respective directory as well?

install -Dm644 contrib/completions/fish/ $pkgdir/usr/share/fish/vendor_completions.d/
install -Dm644 contrib/completions/bash/grim.bash $pkgdir/usr/share/bash-completion/completions/pass

1ace commented on 2018-08-07 09:53 (UTC) (edited on 2018-08-07 09:54 (UTC) by 1ace)

Hey :)

Just sent you a patch by email, but in case the address is wrong: You should fix the size of the commit hash in the version so that different people with different git default settings on their machine get the same package version, which avoids the package manager telling us that the package is out of date when it isn't.

You can do this by giving a value to the --short argument to git rev-parse, like so:

git rev-parse --short=7 HEAD

(7 seems to be the default value on your machine, so you won't see a difference)

I also just realized my email didn't mention which package this is for, but you should probably just do this in all of your -git packages :)

emersion commented on 2018-08-06 08:13 (UTC)

@wheatdog: thanks!