Package Details: starship 0.48.0-1

Git Clone URL: (read-only, click to copy)
Package Base: starship
Description: The cross-shell prompt for astronauts
Upstream URL:
Licenses: ISC
Provides: starship
Submitter: chipbuster
Maintainer: chipbuster (starship-bot)
Last Packager: chipbuster
Votes: 44
Popularity: 7.36
First Submitted: 2019-08-11 01:14
Last Updated: 2021-01-15 18:46

Latest Comments

1 2 3 4 5 6 ... Next › Last »

chipbuster commented on 2021-01-16 06:26

@nickelc Thanks for the info! I've altered the PKGBUILD accordingly.

nickelc commented on 2021-01-03 10:26

Hi, packaging fails if a custom target dir is set via the CARGO_TARGET_DIR env variable. This patch fixed it for me.

diff --git a/PKGBUILD b/PKGBUILD
@@ -29,6 +29,7 @@ check() {

 package() {
     cd "$pkgname-$pkgver"
-    install -Dm755 "target/release/starship" "$pkgdir/usr/bin/$pkgname"
+    targetdir=${CARGO_TARGET_DIR:-target}
+    install -Dm755 "$targetdir/release/starship" "$pkgdir/usr/bin/$pkgname"
     install -Dm644 "LICENSE" "$pkgdir/usr/share/licenses/$pkgname/LICENSE"

chipbuster commented on 2020-11-26 10:19

@WhyNotHugo The requirement is to have a working rust toolchain including a rustc and cargo. The rust package should provide this (my clean-chroot test builds are against rust, not rustup), but I was shooting at some weird packaging issues.

Of course, now that I'm thinking, the correct move would have been to ask for a list of installed packages and the compilation output...

@Hubro would you mind posting the output of pacman -Qs rust and the errors you get when trying to build?

WhyNotHugo commented on 2020-11-26 09:26

@chipbuster If the requirement is to have rustup, rather than rust, then dependencies should probably list the former, not the latter.

chipbuster commented on 2020-11-26 00:51

@Hubro Do you have rust or rustup installed? If rust, you might want to uninstall that, install rustup, and then run rustup update to get the latest version of rust.

You can also install starship-bin if you're having issues getting the toolchain to work.

joelpet commented on 2020-11-20 14:39

@Hubro My guess is that @silverben (like me) has the rust dependency of this package satisfied through rustup. You might have it satisfied through one of the other providers, e.g. rust-bin, which does not contain the rustup binary. One option for you could be to replace that with rustup and run rustup update, after which you should be able to install/upgrade this package.

It could be of interest to the maintainer of this AUR package which version of which rust provider you're currently using, since the error indicates a dependency problem.

Hubro commented on 2020-11-19 15:16

I am unable to update this package, and my current install got broken by the latest system update ( cannot open shared object file).

When I build this package, the compilation succeeds, the tests succeed, but when it gets to "Doc-tests", it crashes horribly with lots of errors. Any advise?

Hubro commented on 2020-11-19 15:14

@silverben10 I have the same issue. What do you mean "rustup update" fixed the issue? Where do you run it? I don't have that command available.

hvksmr1996 commented on 2020-11-01 04:27

The check function fails

schrieveslaach commented on 2020-10-18 10:32

Hey @chipbuster, could you enable the feature notify-rust for the package?