Arch Linux User Repository

@musqz No problem. I'll double check the package and update if I find anything.

@xiota Ah, I see — thanks a lot for clarifying!
I misunderstood how -git packages work and thought the version number needed to be bumped manually.
Good to know it’s already pulling the latest upstream commits.
Appreciate your maintenance and sorry for the noise!

@musqz -git packages update the version string on build. They're considered up to date as long as they can build and function. If you're aware of any issues, besides the version number, feel free to flag and describe the problem. Otherwise, last successful build was a few days ago. 2025.08.16.r0.g0946d14-1

Hi @xiota, thanks a lot for maintaining this package! 🙏

skippy-xd is now the default window picker in Mabox Linux.
The Mabox developer maintains the stable release in their repo, but doesn’t have time to also keep the -git version up to date.

Meanwhile, upstream has had quite a few commits since the last update here, including some major changes and fixes. For example:
- Improved expose animation flow
- Small config changes (e.g. tooltip is now label)
- Many more updates and improvements

A quick demo of the new functionality:
skippy-xd --expose --wm-class firefox --wm-class terminator

Would you mind updating this package to the latest version?

Thanks in advance! 🙂

This package now uses meson, which is not affected by the Makefile. However, as far as I can tell, the Makefile works as expected. The potential issue was reported upstream, and the developer was unable to replicate the problem.

There's a small bug in Makefile:5: when ccache is installed; it detects clang event if it's not installed on the system. Could we just add clang to makedepends as it is a preferred compiler since skippy-xd:5.2

@jrd I rebuilt the package with the PKGBUILD as-is. It works as expected. There may be some network or git config issue on your system. If multiple packages are affected, consider setting GITFLAGS in /etc/makepkg.conf.

I managed to clone the silly repository with the following diff:

diff --git a/PKGBUILD b/PKGBUILD
index 3396079..9abc0ae 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -5,7 +5,7 @@

 _pkgname="skippy-xd"
 pkgname="$_pkgname-git"
-pkgver=2024.12.26.r0.gbb6fda7
+pkgver=2024.12.26.r9.g9b6be85
 pkgrel=1
 pkgdesc="A full-screen Exposé-style task switcher for X11"
 url="https://github.com/felixfung/skippy-xd"
@@ -28,8 +28,16 @@ provides=("$_pkgname=${pkgver%%.r*}")
 conflicts=("$_pkgname")

 _pkgsrc="felixfung.skippy-xd"
-source=("$_pkgsrc"::"git+$url.git")
-sha256sums=('SKIP')
+
+prepare() {
+  git clone --depth 1 "$url.git" "$_pkgsrc"
+  cd "$_pkgsrc"
+  git config pack.depth 1
+  git config pack.window 1
+  git config http.version HTTP/1.1
+  git config http.postBuffer 10g
+  git fetch --unshallow
+}

 pkgver() {
   cd "$_pkgsrc"

Error in compilation:

fatal: No tags can describe 'c5a68d612a2e6fcf992f974768184c695f9e1589'. Try --always, or create some tags. ==> ERROR: pkgver is not allowed to be empty. ==> ERROR: pkgver() generated an invalid version:

@ectospasm Maintainer line is pretty meaningless because majority of orphaned packages have outdated info. The final arbiter of who maintains the package is aurweb.

Instead of demanding changes that have no effect on packaging, you could have explained the reason for your request. You could also have asked to co-maintain. Most of the packages I've adopted were defective. As long as they're kept in good shape, I don't care who pushes updates.