Package Details: starship 0.50.0-1

Git Clone URL: https://aur.archlinux.org/starship.git (read-only, click to copy)
Package Base: starship
Description: The cross-shell prompt for astronauts
Upstream URL: https://starship.rs/
Licenses: ISC
Provides: starship
Submitter: chipbuster
Maintainer: chipbuster (starship-bot)
Last Packager: chipbuster
Votes: 54
Popularity: 9.61
First Submitted: 2019-08-11 01:14
Last Updated: 2021-02-04 22:59

Latest Comments

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

chipbuster commented on 2021-02-10 21:02

@alycryd No objections from me! Never had this done before--is there anything particular I'd need to do?

I presume the PKGBUILD for the community package would be maintained by the TU team in that case. Would you need/prefer updates from the starship team if the build changes?

alucryd commented on 2021-02-10 20:29

@chipbuster Hi there, I'd like to push this to [community] if that's okay with you.

geezus commented on 2021-02-05 15:56

Using paru I was able to get it to work by passing the --nocheck flag. I don't see the same/similar flag for yay.

chipbuster commented on 2021-02-04 22:45

My guess is that it's upstream. If you want to just get it installed, it's probably safe to just disable the tests by modifying PKGBUILD. Those tests are usually only run in GH Actions upstream, and it's quite likely that some configuration that wasn't anticipated is breaking it.

geezus commented on 2021-02-04 16:10

Can anyone tell me if this is an issue with the AUR build or the package itself?

failures:

---- modules::git_commit::tests::test_latest_tag_shown_with_tag_enabled stdout ---- thread 'modules::git_commit::tests::test_latest_tag_shown_with_tag_enabled' panicked at 'assertion failed: (left == right) left: 22, right: 4', library/std/src/sys/unix/thread.rs:165:21 note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

failures: modules::git_commit::tests::test_latest_tag_shown_with_tag_enabled

test result: FAILED. 521 passed; 1 failed; 28 ignored; 0 measured; 0 filtered out

geezus commented on 2021-02-02 21:03

Please update

https://github.com/starship/starship/releases/tag/v0.50.0

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