Package Details: flameshot-git r1629.0fe55916-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-git
Submitter: j1simon
Maintainer: mehrad (borgman_jeremy)
Last Packager: mehrad
Votes: 35
Popularity: 0.87
First Submitted: 2017-07-08 16:07 (UTC)
Last Updated: 2022-01-30 15:10 (UTC)

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

1 2 3 4 5 Next › Last »

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

earlybird commented on 2022-02-16 10:52 (UTC) (edited on 2022-02-16 10:52 (UTC) by earlybird)

I can confirm that we need kguiaddons as dependency for the app to work - please change the pkgbuild as such

alwyns42 commented on 2022-02-15 18:02 (UTC)

kguiaddons appears to be required as a runtime dependency on my system, but in PKGBUILD it is only listed as a compile time dependency. Perhaps it needs to be added to depends?

Alkaris commented on 2022-02-07 23:27 (UTC) (edited on 2022-02-07 23:28 (UTC) by Alkaris)

Since they removed the save buttons and copy to clipboard buttons, it's not worth updating for the new changes in v11.

This update is actually a downgrade. Don't fix what's not broke.

ElijahLynn commented on 2022-02-01 18:18 (UTC) (edited on 2022-02-01 18:20 (UTC) by ElijahLynn)

Rubber ducking here:

I just updated from 10.x to 11.x and now I can't save or copy to the clipboard. I think I was using another test branch at the time. Just ducking here in case anyone else had similar happen. I'll update this as I go along.

UPDATE1:
https://github.com/flameshot-org/flameshot/issues/2275 (Clipboard and Save to File buttons no longer appearing)
https://github.com/flameshot-org/flameshot/issues/2227 (V11.0 beta, Copy to clipboard / save shortcut doesn't work with flameshot gui --path)

mehrad commented on 2022-01-30 15:12 (UTC)

@abhijeetviswa Thanks for the reminder. For others that wonder about this change, please checkout https://github.com/flameshot-org/flameshot/issues/2276

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.