Package Details: luxtorpeda-git 61.0.0.r373.e192991-1

Git Clone URL: https://aur.archlinux.org/luxtorpeda-git.git (read-only, click to copy)
Package Base: luxtorpeda-git
Description: Steam Play compatibility tool to run games using native Linux engines
Upstream URL: https://github.com/luxtorpeda-dev/luxtorpeda
Keywords: games steam
Licenses: GPL2
Conflicts: luxtorpeda
Provides: luxtorpeda
Submitter: D1SoveR
Maintainer: D1SoveR
Last Packager: D1SoveR
Votes: 6
Popularity: 0.001937
First Submitted: 2020-02-24 23:13 (UTC)
Last Updated: 2022-11-30 08:47 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

d10sfan commented on 2021-11-05 19:03 (UTC)

There will be a 46 coming out soon: https://github.com/luxtorpeda-dev/luxtorpeda/pull/117

that will have a workaround for the cargo bug.

d10sfan commented on 2021-11-05 15:25 (UTC) (edited on 2021-11-05 15:26 (UTC) by d10sfan)

I'm the developer of luxtorpeda-dev

The bit-wise errors are due to a rust cargo bug introduced recently: https://github.com/rust-lang/cargo/issues/9885

I'm not sure if/when they've released a new cargo that fixes it. I'm on rustup and downloaded the latest cargo that way and haven't had any issues building with that.

Let me know if there's anything I can do on that to help.

D1SoveR commented on 2021-11-05 15:00 (UTC)

@liamdawe, I can't account for any issues with your local setup. If installing from yay, pacaur, or other helper doesn't work, then use the following commands to build and install the package:

git clone https://aur.archlinux.org/luxtorpeda-git.git && cd luxtorpeda-git && makepkg -sci

liamdawe commented on 2021-11-05 14:56 (UTC)

Seems the package is broken?

:: (0/1) Downloaded PKGBUILD: luxtorpeda-git -> error fetching luxtorpeda-git: error: Your local changes to the following files would be overwritten by merge: PKGBUILD Please commit your changes or stash them before you merge. Aborting context: exit status 1

<deleted-account> commented on 2021-11-04 18:15 (UTC)

alright, after running cargo install cargo-download I got this:

warning: be sure to add `/home/benji/.cargo/bin` to your PATH to be able to run the installed binaries

seems like just a warning, no errors yet. I continued to do the other two commands which returned:

/home/benji/.cargo/bin/cargo-download bit-set==0.2.0 > /dev/null
INFO: cargo-download v0.1.2
INFO: Crate `bit-set==0.2.0` downloaded successfully
/home/benji/.cargo/bin/cargo-download bit-vec==0.6.3 > /dev/null
INFO: cargo-download v0.1.2
INFO: Crate `bit-vec==0.6.3` downloaded successfully

and finally, running yay -S luxtorpeda-git and cleanBuilding concluded with this:

Downloaded bit-set v0.2.0
error: failed to parse manifest at `/home/benji/.cargo/registry/src/github.com-1ecc6299db9ec823/bit-set-0.2.0/Cargo.toml`

Caused by:
  dependency (bit-vec) specified without providing a local path, Git repository, or version to use.
make: *** [Makefile:41: release] Error 101
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: luxtorpeda-git

am I missing something in ~/.cargo/bin? I apologize for my lack of knowledge, never really used Rust before.

D1SoveR commented on 2021-11-04 10:21 (UTC) (edited on 2021-11-04 10:22 (UTC) by D1SoveR)

@gshinguji, I'm little bit stumped, to be honest - I've tried the build on another machine altogether, with different internet connection, and it passes.

I've reintroduced the flag for reproducible build (grabbing one very specific version of the package as opposed to what's currently the latest one); if you could remove the cargo cache with rm -rf /home/benji/.cargo and try to build again to see if it helps (apologies for the runaround, unfortunately I can't seem to be able to reproduce the issue on my end).

If that still fails, maybe there's some issue with access to cargo repository on your network. If that's the case, can you try the following:

  • Run cargo install cargo-download
  • Run /home/benji/.cargo/bin/cargo-download bit-set==0.2.0 > /dev/null and see if it throws any errors
  • Run /home/benji/.cargo/bin/cargo-download bit-vec==0.6.3 > /dev/null and see if it throws any errors

<deleted-account> commented on 2021-11-03 22:55 (UTC)

ok I ran both of those commands and now this is what I get:

==> Starting build()...
cargo build --release
    Updating git repository `https://github.com/luxtorpeda-dev/egui.git`
    Updating crates.io index
    Updating git repository `https://github.com/ArjunNair/egui_sdl2_gl.git`
    Updating git repository `https://github.com/luxtorpeda-dev/steamlocate-rs`
    Updating git repository `https://github.com/luxtorpeda-dev/steamy`
  Downloaded aho-corasick v0.7.18
  Downloaded pest_generator v2.1.3
  Downloaded ab_glyph_rasterizer v0.1.4
  Downloaded bit-set v0.2.0
error: failed to parse manifest at `/home/benji/.cargo/registry/src/github.com-1ecc6299db9ec823/bit-set-0.2.0/Cargo.toml`

Caused by:
  dependency (bit-vec) specified without providing a local path, Git repository, or version to use.
make: *** [Makefile:41: release] Error 101
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: luxtorpeda-git

D1SoveR commented on 2021-11-03 10:53 (UTC)

@gshinguji, I cannot seem to reproduce the issue, even when building in completely clean chroot.

It appears like there might've been an issue with rust's cargo downloading one of the dependencies from its registry. Could you try to sudo pacman -Syyu first to make sure that rust is up-to-date, then rm -rf /home/benji/.cargo to remove the cache, and then try to build the package again?

<deleted-account> commented on 2021-11-03 01:03 (UTC)

fails to build:

==> Starting build()...
cargo build --release
 Downloading crates ...
error: failed to download `bit-set v0.2.0`

Caused by:
  unable to get packages from source

Caused by:
  failed to parse manifest at `/home/benji/.cargo/registry/src/github.com-1ecc6299db9ec823/bit-set-0.2.0/Cargo.toml`

Caused by:
  dependency (bit-vec) specified without providing a local path, Git repository, or version to use.
make: *** [Makefile:41: release] Error 101
==> ERROR: A failure occurred in build().
    Aborting...

D1SoveR commented on 2021-11-03 00:45 (UTC)

@thaewrapt, thank you for the heads-up, the dependencies have been updated!