Package Details: picom-git 2189_11.172.gcc8e0a98_2024.02.29-1

Git Clone URL: https://aur.archlinux.org/picom-git.git (read-only, click to copy)
Package Base: picom-git
Description: X compositor (fork of compton) (git-version)
Upstream URL: https://github.com/yshui/picom
Licenses: MIT, MPL-2.0
Conflicts: compton, compton-git, picom
Provides: compton, compton-git, picom
Replaces: compton-git
Submitter: WorMzy
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 359
Popularity: 1.80
First Submitted: 2019-10-24 11:20 (UTC)
Last Updated: 2024-03-01 21:25 (UTC)

Required by (20)

Sources (1)

Latest Comments

1 2 3 4 5 6 .. 14 Next › Last »

kjkent commented on 2024-03-02 08:39 (UTC)

@WorMzy -- thank you! I assumed it was an issue with what I was running as there was a couple of other PKGBUILDs failing. Appreciate the response :)

WorMzy commented on 2024-03-01 15:48 (UTC) (edited on 2024-03-01 21:25 (UTC) by WorMzy)

Thanks for the heads up. Looks like epoxy was added as a dep a few weeks ago, so I just need to update the PKGBUILD.

https://github.com/yshui/picom/commit/642a43acbb5a92f00c31bd7487c07fab59ab18a9

In the meantime you should be able to just add 'libepoxy' to the dependency array locally.

EDIT: updated now.

kjkent commented on 2024-03-01 14:47 (UTC)

This is likely a me-problem, but I get a build error from meson specifically when I try to build in a chroot. Any thoughts as to why? 

# $ makechrootpkg -r /var/lib/aurbuild/x86_64 -D /var/lib/repo/aur -d /var/cache/pacman/pkg/ -d /var/lib/repo/aur -- -feA --noconfirm --noprepare --holdver

#...
Run-time dependency epoxy found: NO (tried pkgconfig and cmake)

src/meson.build:62:10: ERROR: Dependency "epoxy" not found, tried pkgconfig and cmake

pkg-config 2.1.0 and cmake 3.28.3 are both found successfully, and the lack of epoxy in the deps combined with the error message has me unsure how to proceed.

Thanking yall kindly.

xiota commented on 2023-09-20 09:39 (UTC)

Please remove replaces directive. Thank you. (No need to reply via comment; AUR now sends commit notifications.)

servimo commented on 2023-04-14 20:26 (UTC)

Although the version name is outdated I can compiled the latest picom, dont know if it have new dependencies, but in my computer looks like its working.

bidulock commented on 2022-04-11 03:23 (UTC)

i686 can stay. replaces should not be used in AUR packages.

willemw commented on 2022-04-07 08:02 (UTC)

If should not be necessary to list compton-git (if compton-git correctly provides compton):

provides=('compton' 'picom')
conflicts=('compton' 'picom')
replaces=('compton')

Maybe it is also not necessary to list compton in provides and conflicts, since this package already replaces compton.

i686 can be removed.

d_s commented on 2022-01-21 20:15 (UTC) (edited on 2022-01-21 20:16 (UTC) by d_s)

My git is configured to verify commit signatures by default, which causes this package to generate an invalid pkgver.

If anyone else has the issue, it can be fixed by adding --no-show-signature to the git log command.

==> Starting pkgver()...
==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.
==> ERROR: pkgver() generated an invalid version: 1651_Next.89.gaa57d3f_gpg: Signature made Wed 19 Jan 2022 18:01:36 GMT
gpg:                using RSA key 4AEE18F83AFDEB23
gpg: Good signature from "GitHub (web.flow commit signing) <noreply@github.com>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 5DE3 E050 9C47 EA3C F04A  42D3 4AEE 18F8 3AFD EB23
2022.01.19

WorMzy commented on 2019-12-10 19:08 (UTC)

Huh. Yeah, I'm not sure how that happened either. Thanks for pointing it out, it's fixed now.

ortango commented on 2019-12-10 18:28 (UTC)

hey WorMzy, idk what happened but the pkgbuild for picom-git is using the old build_docs option instead of with_docs.

thanks again for maintaining this.

1 2 3 4 5 6 .. 14 Next › Last »