Search Criteria
Package Details: wormhole-rs 0.7.4-0
Package Actions
Git Clone URL: | https://aur.archlinux.org/wormhole-rs.git (read-only, click to copy) |
---|---|
Package Base: | wormhole-rs |
Description: | Rust implementation of Magic Wormhole, with new features and enhancements |
Upstream URL: | https://github.com/magic-wormhole/magic-wormhole.rs |
Licenses: | custom:EUPL-1.2+ |
Submitter: | Max1Truc |
Maintainer: | Max1Truc |
Last Packager: | Max1Truc |
Votes: | 7 |
Popularity: | 0.125237 |
First Submitted: | 2022-03-21 11:18 (UTC) |
Last Updated: | 2024-12-01 17:01 (UTC) |
Dependencies (2)
- libxcb (libxcb-gitAUR)
- cargo (rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup-stubAUR, rust, rustup) (make)
Latest Comments
1 2 Next › Last »
Max1Truc commented on 2024-11-27 21:22 (UTC) (edited on 2024-11-27 21:22 (UTC) by Max1Truc)
Upstream release is currently messed up: says 0.7.4 but is 1.7.4 in Git
I'll wait until this gets figured out.
https://github.com/magic-wormhole/magic-wormhole.rs/issues/275
https://github.com/Homebrew/homebrew-core/pull/198791
Max1Truc commented on 2024-05-25 12:54 (UTC)
@deraffe, I just issued a temporary fix by disabling lto
@xeruf, did you try building wormhole-rs with a more recent Rust version ? The 1.56.0-nightly version seems quite old, and I can't reproduce with rust 1.71.0.
xeruf commented on 2024-03-17 08:01 (UTC)
fails to build:
deraffe commented on 2024-02-12 17:09 (UTC)
Looks like this is affected by https://github.com/briansmith/ring/issues/1444
Max1Truc commented on 2022-12-26 13:25 (UTC) (edited on 2022-12-26 13:31 (UTC) by Max1Truc)
I just added the shell completions. However, the completions for zsh don't work for me, I'll debug this later.
PS: the bash and fish ones seem to work
alerque commented on 2022-12-22 08:47 (UTC) (edited on 2022-12-22 08:47 (UTC) by alerque)
One of the new features in 0.6.0 is shell completions. Can you please add those to the packaging?
Max1Truc commented on 2022-05-26 08:16 (UTC)
Yeah, never mind. I also prefer the plain-text patches. I guess, too, that tabs are replaced by spaces at some point, probably because of my editor or the AUR web interface.
Anyway, I agree it's not a big deal.
Migrating to [community] at some point would be really cool.
alerque commented on 2022-05-26 06:51 (UTC)
Sorry, I don't know what the deal is with
git am
for you. I recommend it a lot because it's one of the most robust ways I know of to send patches short of having a direct Git remote wired up somewhere. That doesn't mean it's bullet proof. I suspect though that you have your editor set to auto munge some spacing and that's getting into the patch before it is saved / passed to Git. The.SRCINFO
files are generated using the usual Arch tooling and I can see in the commit on my side and the patch content below they don't have the bogus spacing showing up in the commit on your side; on my side they are identical to what you are regenerating withmakepkg --printsrcinfo
.No sweat though, I appreciate this being maintained. It's on my list to consider migrating to [community] if it gets a little more AUR traction too.
Max1Truc commented on 2022-05-25 23:26 (UTC)
Thanks for the patch, but I guess my merging workflow is wrong.
I tried piping the email and copy-pasting the patch into a file, but I have to use
--ignore-space-change
withgit am
for it to work. Otherwise the patch can't apply andgit status
shows no conflicts.Anyway, I just pushed the new commits.
alerque commented on 2022-05-25 22:34 (UTC) (edited on 2022-05-25 22:37 (UTC) by alerque)
I don't think there were 3-space indents, but there were some tabs. I think your editor defaults must be for 3 space tabs. In any case cleaning up the indents to be all spaces is fine of course.
The patch I included is not in the upstream 0.5.0 release, so that can be dropped when bumping this:
1 2 Next › Last »