Package Details: urbit 3.1-1

Git Clone URL: https://aur.archlinux.org/urbit.git (read-only, click to copy)
Package Base: urbit
Description: An operating function
Upstream URL: https://github.com/urbit/urbit
Keywords: arvo hoon nock urbit vere
Licenses: MIT
Conflicts: urbit-git
Submitter: akraut
Maintainer: tinnus-napbus
Last Packager: tinnus-napbus
Votes: 9
Popularity: 0.000001
First Submitted: 2016-11-04 04:37 (UTC)
Last Updated: 2024-08-24 14:47 (UTC)

Latest Comments

1 2 Next › Last »

tinnus-napbus commented on 2022-11-12 10:53 (UTC)

on second thoughts I have made the src filename the same as upstream eg vere-v1.11-x86_64-linux, that makes more sense

tinnus-napbus commented on 2022-11-12 10:43 (UTC)

ok I think there has been issues with the source filename not being unique. I have changed it to $pkgname-$pkgver-$pkgrel so there's no chance of it colliding with previously downloaded version. Hopefully this will fix the apparent sha256sum failure

tinnus-napbus commented on 2022-11-12 10:18 (UTC)

those are identical

shrigma commented on 2022-11-12 10:12 (UTC) (edited on 2022-11-12 10:23 (UTC) by shrigma)

wget https://bootstrap.urbit.org/vere/live/1.11/vere-v1.11-x86_64-linux..... Saving to: ‘vere-v1.11-x86_64-linux’

sha256sum vere-v1.11-x86_64-linux 8d0052fd7ff7a6137f0746c38485ad5d897df6538407bfd2af9120d89f80b882 vere-v1.11-x86_64-linux

And PKGBUILD contains exactly the same hashsum.

8d0052fd7ff7a6137f0746c38485ad5d897df6538407bfd2af9120d89f80b882'

I was able to update urbit using paru, not yay. Not sure why yay caused a problem.

cwtb commented on 2022-09-13 21:39 (UTC)

I'm getting a validity error too. Mind double checking? Happy to make a PR with the new checksum.

tinnus-napbus commented on 2022-08-08 06:23 (UTC)

I just checked and it still works fine & has the correct hash. Maybe yours was corrupted during download or something

burger commented on 2022-08-08 03:42 (UTC)

I'm getting the following error when upgrading, maybe the source files changed?

=> Validating source files with sha256sums...
    urbit ... FAILED
==> ERROR: One or more files did not pass the validity check!
error: failed to download sources for 'urbit-1.10-1': 
error: packages failed to build: urbit-1.10-1

mikecr commented on 2021-02-01 07:25 (UTC) (edited on 2021-02-01 07:26 (UTC) by mikecr)

v1.1 reintroduces the alternative 'urbit-king' haskell-based binary so it should also install that. Additionally, afaik the binaries are built statically linked so shouldn't have any dependencies, and I don't understand why this installs to /opt - there are only 3 binaries so they should just go straight in /usr/bin

chilledfrogs commented on 2020-07-06 17:43 (UTC)

@pepijndevos look at this: https://urbit.org/docs/tutorials/ship-troubleshooting/ for that "terminals database is inaccessible" issue, seems you should run it while being in /opt/urbit/ for now, bit dumb workaround but hey... I also flagged the package as out-of-date but managed to work around getting the latest version with a modified PKGBUILD in the meantime, fixes the ETH comet registration issue

omarroth commented on 2020-01-26 02:00 (UTC)

Issue with urbit-worker should be fixed. What command are you running?

1 2 Next › Last »