Package Details: flameshot-git r1938.fa29bcb4-1

Git Clone URL: https://aur.archlinux.org/flameshot-git.git (read-only, click to copy)
Package Base: flameshot-git
Description: Powerful yet simple to use screenshot software
Upstream URL: https://github.com/flameshot-org/flameshot
Keywords: screenshot
Licenses: GPL
Conflicts: flameshot
Provides: flameshot
Submitter: j1simon
Maintainer: mehrad (borgman_jeremy)
Last Packager: mehrad
Votes: 41
Popularity: 0.34
First Submitted: 2017-07-08 16:07 (UTC)
Last Updated: 2023-11-10 14:16 (UTC)

Dependencies (11)

Required by (4)

Sources (1)

Pinned Comments

GC268DM commented on 2022-05-29 10:40 (UTC)

What worked for me was

pamac checkupdates -a --devel
pamac upgrade -a --devel

Where -a stands for aur and --devel for development packages.

Since the --devel flag checks if behind the development packages (like "*-git" packages) there are any newer versions, it will update to the latest version of the package in git and not require and update on the aur listing

mehrad commented on 2022-01-19 10:26 (UTC) (edited on 2022-01-19 10:28 (UTC) by mehrad)

Please stop flagging this AUR as out-of-date unless you have tried these:

If you use a proper AUR helper (e.g paru, yay) this AUR will be use the latest commit of the Github repo. If you use pamac, it will not update based on the latest commit automatically and you should do pamac install --upgrade flameshot-git to force it to check for upgrades. Therefore, this AUR cannot become out-of-date unless the Github URL or dependencies get out of date.

Latest Comments

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

abhijeetviswa commented on 2022-01-30 12:24 (UTC)

Please use the -DUSE_WAYLAND_CLIPBOARD=1 when running CMake. Without this flag, the clipboard functionality is broken on KDE. I believe the only reason for this flag is to disable clipboard support when packaging for snap/flatpak.

mehrad commented on 2022-01-27 11:52 (UTC)

@ian_eo Sorry about the confusion, but because this AUR build the latest commit in the master branch of the github repo, it is actually more misleading to change it to v11, because for instance the most recent commit as of writing this comment is 5ab76e2 which is 19 commits ahead of v11 which was the commit ad1bf28. Basically what I'm trying to say is that this AUR is always up to date as everything is automated. of course the version number (ie. r1629.0fe55916) is updated whenever we modify the PKGBUILD, but even without that, your AUR helper should always be able to check if there is a new commit in Github and build using that.

ian_eo commented on 2022-01-27 00:56 (UTC)

i hope you match the pkgver similar to what the version releases in github. it makes it easier to identify if there is an update.

ex. from pkgver=r1629.0fe55916 to pkgver=r0.11.

mehrad commented on 2022-01-19 10:26 (UTC) (edited on 2022-01-19 10:28 (UTC) by mehrad)

Please stop flagging this AUR as out-of-date unless you have tried these:

If you use a proper AUR helper (e.g paru, yay) this AUR will be use the latest commit of the Github repo. If you use pamac, it will not update based on the latest commit automatically and you should do pamac install --upgrade flameshot-git to force it to check for upgrades. Therefore, this AUR cannot become out-of-date unless the Github URL or dependencies get out of date.

allexj commented on 2022-01-14 21:03 (UTC)

@mehrad you are right, I removed that comment. If you want to go safe, flameshot-0.10.1-1 works. To install it you can go here: https://archive.archlinux.org/packages/f/flameshot/ copy the link and paste in terminal with pacman -U _link_ command

mehrad commented on 2022-01-14 14:19 (UTC)

@allexj and to everyone else. Of course you are free to choose what you install on your computer, but blindly advertising an AUR without knowing what are the code changes of that fork and how behind it is compared to the actual github repo is dead wrong. As a general good practice one should be always vigilant about what AUR and what codes are installed.

angordeyev commented on 2021-12-24 17:05 (UTC) (edited on 2021-12-24 17:05 (UTC) by angordeyev)

Did not run on Gnome Wayland, installing the following package fixed the issue sudo pacman -S xdg-desktop-portal

ritikrajdev commented on 2021-06-17 17:32 (UTC)

Please add grim as an optional dependency, as wlroots based compositors require grim to capture screenshot.

https://github.com/flameshot-org/flameshot/blob/bd2feadc65f2dc92675327244cc4f9cba5d411e5/docs/Sway%20and%20wlroots%20support.md#L5