Package Details: picom-tryone-git 1417_Next.136.g7a3137b_2020.04.11-1

Git Clone URL: (read-only, click to copy)
Package Base: picom-tryone-git
Description: tryone144's picom fork with dual_kawase blur, an X compositor (fork of compton)
Upstream URL:
Keywords: blur compositor compton kawase picom
Licenses: MIT, MPL2
Conflicts: compton, compton-git, picom, picom-git
Provides: compton, compton-git, picom, picom-git
Submitter: frebib
Maintainer: frebib
Last Packager: frebib
Votes: 5
Popularity: 1.02
First Submitted: 2020-01-04 14:08
Last Updated: 2020-04-11 20:18

Required by (17)

Sources (1)

Latest Comments

1 2 Next › Last »

frebib commented on 2020-04-11 20:20

This build is expected to break a lot, sorry. If you'd rather, just build directly from tryone144's branch and don't rebase. I have tweaked how the rebase is performed, so cases like this it will just drop the conflict and carry on. I don't expect that to be much better, but it should at least reduce the chance of conflicts from causing failures.

gardotd426 commented on 2020-04-11 19:42

Once again, build is broken:

==> Making package: picom-tryone-git 1389_Next.108.g8877844_2020.04.09-1 (Sat 11 Apr 2020 03:40:47 PM EDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating picom git repo...
Fetching origin
==> Validating source files with md5sums...
    picom ... Skipped
==> Extracting sources...
  -> Creating working copy of picom git repo...
Reset branch 'makepkg'
==> Starting prepare()...
 * branch            next       -> FETCH_HEAD
fatal: It seems that there is already a rebase-merge directory, and
I wonder if you are in the middle of another rebase.  If that is the
case, please try
    git rebase (--continue | --abort | --skip)
If that is not the case, please
    rm -fr ".git/rebase-merge"
and run me again.  I am stopping in case you still have something
valuable there.

==> ERROR: A failure occurred in prepare(). Aborting...

frebib commented on 2020-04-09 21:28

Build is working again. This package is likely to be in-flux a lot due to upstream changes. If you'd rather, you can just remove the rebase against yshui/next when building the package. At the rate the development is going at the moment, I wouldn't be surprised if this functionality is upstreamed soon- a combination of upstream patches for the experimental backends by both tryone144 and others, this is becoming a lot more reliable and less crashy

NermaN commented on 2020-04-09 04:32

Not buildable due some merge conflict with

ortango commented on 2020-04-05 19:59

thanks frebib, you are quick!

  • also, maybe keeping replaces compton-git would be appropriate? im not sure.

frebib commented on 2020-04-05 19:28 Yeah looks like you're correct according to the documentation. I'll remove the replaces line

ortango commented on 2020-04-05 17:14

Hi, just a question:

why does replaces contain picom-git? isn't this a problem for repos? i removed the array completely, am i missing something?

MyopicPaideia commented on 2020-03-31 14:10

Fixed! Just tried the build and it works again now. Hopefully we can get this more stable. You guys are doing an excellent job maintaining this package.

frebib commented on 2020-03-31 14:08

Error fatal: remote yshui already exists. should be fixed

MyopicPaideia commented on 2020-03-31 04:49

This needs to be fixed is my guess:

 prepare() {
  cd "${srcdir}/${_gitname}"
  git config --local makepkg
  git config --local picom@makepkg.aur
  git remote add yshui
  git fetch yshui
  git rebase yshui/next