Package Details: pop-shell-shortcuts-git 1:r27.a653635-1

Git Clone URL: https://aur.archlinux.org/pop-shell-shortcuts-git.git (read-only, click to copy)
Package Base: pop-shell-shortcuts-git
Description: Application for displaying and demoing Pop Shell shortcuts
Upstream URL: https://github.com/pop-os/shell-shortcuts
Licenses: GPL3
Conflicts: pop-shell-shortcuts
Provides: pop-shell-shortcuts
Submitter: ftsell
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 6
Popularity: 1.10
First Submitted: 2020-05-02 16:42
Last Updated: 2020-10-03 01:43

Latest Comments

1 2 3 Next › Last »

Icoo commented on 2021-02-13 20:01

@yochananmarqos you are right, that did the trick. Probably left overs from the r27.a653635 thing...

yochananmarqos commented on 2021-02-13 19:49

@lcoo: I can't reproduce it. Remove the shell-shortcuts & src folder and try again.

Icoo commented on 2021-02-13 19:44

Getting this error when installing:

==> Starting pkgver()...
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
fatal: Needed a single revision

yochananmarqos commented on 2020-10-03 01:29

@OnyxAzryn @core_contingency: I'm not quite sure what upstream did to cause that. Ugh, time for an epoch, I suppose.

core_contingency commented on 2020-10-02 20:12

Same thing is happening for me. printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)" is giving r27.a653635 which is used for the package version. This means that yay thinks that this package needs to be upgraded to r37.9280535-2 every time I run it, which is slightly inconvenient.

OnyxAzryn commented on 2020-10-02 19:40

I think the version might be incorrect. I keep coming up with the version being r27.a653635.

yochananmarqos commented on 2020-09-28 04:27

@tho: Build in a clean chroot instead of using Yay. Then you won't have to change your environment variables.

treeshateorcs commented on 2020-09-28 04:19

@yochananmarqos

aaah now i understand what's wrong. i'm actually a rust user, and i also use a CARGO_TARGET_DIR env variable. i'll try to figure out how to workaround this

thank you

yochananmarqos commented on 2020-09-28 04:17

@tho: Your error says it's not finding the binary in the $(BINARY_SRC) (target/release/) folder. Make sure you're using rust and not rustup or another package.

treeshateorcs commented on 2020-09-28 04:10

@yochananmarqos

hm this is weird. it gives me the same error. i tried to remove -git from pkgname to no avail