Package Details: skippy-xd-git 2024.12.26.r0.gbb6fda7-1

Git Clone URL: https://aur.archlinux.org/skippy-xd-git.git (read-only, click to copy)
Package Base: skippy-xd-git
Description: A full-screen Exposé-style task switcher for X11
Upstream URL: https://github.com/felixfung/skippy-xd
Licenses: GPL-2.0-or-later
Conflicts: skippy-xd
Provides: skippy-xd
Submitter: dooblem
Maintainer: xiota
Last Packager: xiota
Votes: 51
Popularity: 0.003836
First Submitted: 2013-05-19 18:35 (UTC)
Last Updated: 2024-12-28 06:42 (UTC)

Latest Comments

1 2 3 Next › Last »

xiota commented on 2025-01-03 18:07 (UTC)

@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.

jrd commented on 2025-01-03 17:38 (UTC) (edited on 2025-01-03 17:38 (UTC) by jrd)

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"

purpleleaf commented on 2024-05-19 21:31 (UTC)

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:

xiota commented on 2024-02-06 03:35 (UTC)

@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.

ectospasm commented on 2024-02-06 02:37 (UTC)

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.

xiota commented on 2024-02-06 02:26 (UTC)

@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.

ectospasm commented on 2024-02-06 02:18 (UTC)

@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.

xiota commented on 2024-02-05 02:13 (UTC)

@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.

ectospasm commented on 2024-02-04 23:41 (UTC)

@xiota if you're the Maintainer you need to add your name and (possibly obfuscated) email address to the top of the PKGBUILD.

j.taala commented on 2023-05-26 23:09 (UTC)

@Vedun, I'm no longer a maintainer/co-maintainer of this package and hence can't remove tags.