Package Details: pop-shell-shortcuts-git 1:r30.52cc83f-2

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: 10
Popularity: 0.165086
First Submitted: 2020-05-02 16:42 (UTC)
Last Updated: 2021-11-19 20:03 (UTC)

Latest Comments

f0rdprefect commented on 2022-02-21 11:50 (UTC)

I also had the error @holzhaus is reporting. and also a rustup update solves it.

amfern commented on 2022-01-19 12:10 (UTC) (edited on 2022-01-19 12:32 (UTC) by amfern)

this fails to build for me:

error[E0658]: `#[doc(alias)]` is experimental
   --> /home/ilya/.cargo/registry/src/github.com-1ecc6299db9ec823/glib-macros-0.14.1/src/clone.rs:202:1
    |
202 | #[doc(alias = "get_full_ident")]
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: see issue #50146 <https://github.com/rust-lang/rust/issues/50146> for more information

Edit: removing export RUSTUP_TOOLCHAIN=stable from PKGBUILD fixes it

Edit: I had this error because of outdated rust toolchain, doing rustup update solved it

Holzhaus commented on 2021-11-19 19:36 (UTC)

This fails to build for me:

error[E0599]: no function or associated item named `increment_strong_count` found for struct `Arc<_>` in the current scope
  --> /home/jan/.cargo/registry/src/github.com-1ecc6299db9ec823/glib-0.14.2/src/subclass/shared.rs:29:25
   |
29 |         std::sync::Arc::increment_strong_count(this);
   |                         ^^^^^^^^^^^^^^^^^^^^^^
   |                         |
   |                         function or associated item not found in `Arc<_>`
   |                         help: there is an associated function with a similar name: `incr_strong_count`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0599`.
error: could not compile `glib`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
make: *** [Makefile:57: target/release/pop-shell-shortcuts] Error 101
==> ERROR: A failure occurred in build().
    Aborting...

yochananmarqos commented on 2021-08-30 14:43 (UTC)

@VeryGeneric: I just built it with neither a warning nor an error.

VeryGeneric commented on 2021-08-30 02:27 (UTC)

Anyone else getting a glib build error with this pkgbuild?

I'm able to build manually following the upstream README, though.

Icoo commented on 2021-02-13 20:01 (UTC)

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

yochananmarqos commented on 2021-02-13 19:49 (UTC)

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

Icoo commented on 2021-02-13 19:44 (UTC)

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 (UTC)

@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 (UTC)

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 (UTC)

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 (UTC)

@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 (UTC)

@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 (UTC)

@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 (UTC)

@yochananmarqos

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

yochananmarqos commented on 2020-09-28 04:06 (UTC) (edited on 2020-09-28 04:06 (UTC) by yochananmarqos)

@tho: Oh, sorry. My PKGBUILD isn't using the -git suffix, forgot about that.

I was behind a commit, so I just rebuilt it now and had no issues.

Try this PKGBUILD.

treeshateorcs commented on 2020-09-28 03:33 (UTC) (edited on 2020-09-28 03:35 (UTC) by treeshateorcs)

@yochananmarqos

nope. still doesn't work. same error

but i left the "_dir"s as they were, because "pkgname#pop-" gave me another error

/home/tho/.cache/yay/pop-shell-shortcuts-git/PKGBUILD: line 30: cd: /home/tho/.cache/yay/pop-shell-shortcuts-git/src/shell-shortcuts-git: No such file or directory

yochananmarqos commented on 2020-09-28 01:21 (UTC) (edited on 2020-09-28 03:56 (UTC) by yochananmarqos)

@tho: Replace the build() and package() functions with the following:

build() {
    cd "$srcdir/${pkgname#pop-}"
    make prefix=/usr
}

package() {
    cd "$srcdir/${pkgname#pop-}"
    make prefix=/usr DESTDIR="$pkgdir" install
}

treeshateorcs commented on 2020-09-28 01:17 (UTC)

...
warning: function is never used: `settings_reference`
   --> src/app.rs:342:4
    |
342 | fn settings_reference() -> gtk::Box {
    |    ^^^^^^^^^^^^^^^^^^

    Finished release [optimized] target(s) in 0.04s
install -Dm755 target/release/pop-shell-shortcuts /home/tho/dev/ts/pop-shell-shortcuts-git/pkg/pop-shell-shortcuts-git//usr/local/bin/pop-shell-shortcuts
install: cannot stat 'target/release/pop-shell-shortcuts': No such file or directory
make: *** [Makefile:38: install] Error 1
==> ERROR: A failure occurred in package().
    Aborting...

yochananmarqos commented on 2020-09-03 22:41 (UTC)

This currently installs to /usr/local/bin/. It should be installed to /usr/bin/ using make prefix=/usr.

Edgeworth commented on 2020-08-27 08:14 (UTC)

@user2342342 that’s odd, it works for me, could you post up what worked on your end as well for the benefit of others? Or Point out how to correct my comment?

user2342342 commented on 2020-08-08 04:24 (UTC) (edited on 2020-08-08 04:35 (UTC) by user2342342)

@Edgeworth you forgot a semicolon ya dumb bitch

EDIT: this also doesn't work so you're a double dumb bitch

Edgeworth commented on 2020-07-22 01:41 (UTC) (edited on 2020-08-27 08:35 (UTC) by Edgeworth)

@iSpicyCurry, in order for the shortcuts to be applied it is necessary to run the install.sh script, so try something like this:

cd $(mktemp -d)
git clone https://aur.archlinux.org/pop-shell-shortcuts-git.git
git clone https://aur.archlinux.org/gnome-shell-extension-pop-shell-git.git
cd pop-shell-shortcuts-git; makepkg -si; cd ..

cd gnome-shell-extension-pop-shell-git/; makepkg -si

cd src/shell/
sh rebuild.sh

I also had to change s-m to toggle maximize state rather than maximize window

ftsell commented on 2020-06-26 08:41 (UTC)

Sorry but I'm only packaging this and don't know why your shortcuts are not applying :( You could file an Issue upstream if you believe this to be a bug.

iSpicyCurry commented on 2020-06-22 20:21 (UTC)

Not sure why but not all of the pop shell shortcuts are applying. For example, super + M is not maximizing a window but instead opening the calendar. Any idea how to fix this so it is applied correctly?

xamerin commented on 2020-05-05 13:53 (UTC)

Works great, thanks.

ftsell commented on 2020-05-05 13:04 (UTC)

Thanks for the notice, I have removed the glib dependency since the packages does build without it.

xamerin commented on 2020-05-03 14:41 (UTC)

Have a look at this link. It doesn't need glib or glib2. Looks like rust and gtk3 is sufficient for Arch Linux.

https://www.linuxuprising.com/2020/05/how-to-install-pop-shell-tiling.html

jemzipx commented on 2020-05-03 13:56 (UTC)

I think 'glib' in depends should be changed to 'glib2'. glib pacakge is not found.

psi commented on 2020-05-03 08:55 (UTC)

I believe that "glib" is not the correct dependency as it refers to GTK1 (or maybe GTK2?).