Search Criteria
Package Details: grim-git 1.4.0.r6.g1573b1020ce2-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/grim-git.git (read-only, click to copy) |
---|---|
Package Base: | grim-git |
Description: | Grab images from a Wayland compositor |
Upstream URL: | https://sr.ht/~emersion/grim |
Keywords: | screenshot |
Licenses: | MIT |
Conflicts: | grim |
Provides: | grim |
Submitter: | emersion |
Maintainer: | emersion |
Last Packager: | emersion |
Votes: | 17 |
Popularity: | 0.020126 |
First Submitted: | 2018-05-13 20:49 (UTC) |
Last Updated: | 2022-09-28 19:50 (UTC) |
Dependencies (7)
- libjpeg-turbo (mozjpeg-gitAUR, libjpeg-turbo-gitAUR, mozjpegAUR)
- pango (pango-gitAUR)
- wayland (wayland-gitAUR, wayland-asan-gitAUR, wayland-chromiumAUR)
- wayland-protocols (wayland-protocols-gitAUR)
- git (git-gitAUR, git-glAUR) (make)
- meson (meson-gitAUR) (make)
- scdoc (scdoc-gitAUR) (make)
Required by (55)
- coretoppings (requires grim) (optional)
- drop (requires grim)
- ezc (requires grim)
- farge-git (requires grim) (optional)
- flameshot-git (requires grim) (optional)
- flameshot-old (requires grim) (optional)
- flowinity-flameshot (requires grim) (optional)
- focal-hyprland-git (requires grim)
- focal-sway-git (requires grim)
- gnome-screenshot-stub (requires grim)
- grimblast-git (requires grim)
- grimshot-bin-sway (requires grim)
- hyprland-interactive-screenshot (requires grim)
- hyprshot (requires grim)
- hyprshot-git (requires grim)
- kamite-bin (requires grim) (optional)
- kidex-git (requires grim)
- nextshot (requires grim) (optional)
- nwg-shell-git (requires grim)
- pix2tex (requires grim) (optional)
- Show 35 more...
Latest Comments
1 2 Next › Last »
emersion commented on 2022-09-28 19:51 (UTC)
Done, and started a discussion on the wiki:
https://wiki.archlinux.org/title/Talk:VCS_package_guidelines#git:_core.abbrev_results_in_non-deterministic_git-describe_output
yrlf commented on 2022-09-28 19:31 (UTC)
@emersion: please add
--abbrev=12
to thegit 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 https://www.kernel.org/doc/html/latest/process/submitting-patches.html#describe-your-changes (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 thePKGBUILD
bypkgver()
.If
pkgver()
generates a longer commit hash on your system then please either change thepkgver()
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 https://sr.ht/~emersion/grim/ My random issue I mentioned in the out of date flag
was fixed via following the instructions at https://github.com/flameshot-org/flameshot/blob/master/docs/Sway%20and%20wlroots%20support.md
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?
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 togit 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!
1 2 Next › Last »