Package Details: picom-git 2017_11_2024.01.20-1

Git Clone URL: (read-only, click to copy)
Package Base: picom-git
Description: X compositor (fork of compton) (git-version)
Upstream URL:
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: 358
Popularity: 0.82
First Submitted: 2019-10-24 11:20 (UTC)
Last Updated: 2024-01-20 19:22 (UTC)

Required by (21)

Sources (1)

Latest Comments

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

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')

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) <>" [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

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.

WorMzy commented on 2019-10-24 13:41 (UTC) (edited on 2019-10-24 13:44 (UTC) by WorMzy)

@ortango: I already submitted a merge request. :)

For clarity's sake -- people should jump over to if they're using compton-git currently.

ortango commented on 2019-10-24 12:51 (UTC)

yshui has changed the project name to picom.

not sure if you want to move onto picom-git, but regardless the pkgbuild needs an update currently because compton.sample.conf has changed names.

WorMzy commented on 2019-07-27 09:23 (UTC)

Thanks for the heads up, the upstream change didn't cause a build failure so I wouldn't have noticed otherwise!