Search Criteria
Package Details: clipboard 0.10.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/clipboard.git (read-only, click to copy) |
---|---|
Package Base: | clipboard |
Description: | Cut, copy, and paste anything in your terminal. |
Upstream URL: | https://getclipboard.app |
Licenses: | GPL-3.0-or-later |
Submitter: | Antiz |
Maintainer: | Antiz |
Last Packager: | Antiz |
Votes: | 14 |
Popularity: | 0.20 |
First Submitted: | 2022-12-11 10:14 (UTC) |
Last Updated: | 2024-11-17 18:58 (UTC) |
Dependencies (9)
- alsa-lib
- openssl (openssl-gitAUR, openssl-staticAUR)
- cmake (cmake-gitAUR) (make)
- libx11 (libx11-gitAUR) (make)
- wayland (wayland-gitAUR, wayland-asan-gitAUR, wayland-chromiumAUR) (make)
- wayland-protocols (wayland-protocols-gitAUR) (make)
- libx11 (libx11-gitAUR) (optional) – X11 support
- wayland (wayland-gitAUR, wayland-asan-gitAUR, wayland-chromiumAUR) (optional) – Wayland support
- wayland-protocols (wayland-protocols-gitAUR) (optional) – Wayland support
Latest Comments
Antiz commented on 2023-10-14 18:49 (UTC)
@dreieck Patch applied
Thanks for the heads up!
dreieck commented on 2023-10-05 16:58 (UTC) (edited on 2023-10-14 12:57 (UTC) by dreieck)
Seems this now needs specific older version of GCC to build, see ↗ this upstream comment.
Upstream does not seem to want to adapt to new GCC libraries.
EDIT 2023-10-14: ↗ Upstream has fixed it.
Antiz commented on 2023-01-09 14:02 (UTC) (edited on 2023-01-09 20:41 (UTC) by Antiz)
@hugo Indeed, thanks for raising this. This is due to this recent changes in the PKGBUILD, it should not happen again with any future upgrades.
Manual intervention:
Anyone that has
clipboard
v0.2.0-1 (or any prior version) currently installed and that didn't upgraded to the latest version yet will need to runrm /usr/bin/cb
(as root or with elevated privileges) before doing the upgrade.This will only be needed once and should not happen again with any future upgrades :)
hugo commented on 2023-01-09 12:35 (UTC)
When trying to upgrade the package I get this error:
The workaround is to just remove the file then upgrade, as expected.