Arch Linux User Repository

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.

I'm just saying looking at the PKGBUILD makes it look like there's no maintainer. I was going to adopt the orphaned package because of it, since I didn't realize it wasn't orphaned until I looked back at aurweb.

You do what you want, but I can see others having this same problem.

@ectospasm That point starts "Please..." It is a request, not a requirement.

Do not leave anymore comments on this or any of my other packages unless you have a legitimate packaging issue.

@xiota: You are clearly not following the AUR Rules of Submission, see here:

Rules of Submission

There are explicit instructions to do this towards the end of this section; if you are assuming the role of Maintainer for this AUR package, please put your name and your email address at the top of the PKGBUILD, as demonstrated in this section. You can obfuscate your email address, it's what I do for my own AUR submissions.

@ectospasm Current and previous maintainers are recorded on the aurweb page and change log. If you have a legitimate packaging issue, you may leave flag or comment.