mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 16:25:55 +03:00
[GH-ISSUE #1002] Packaging lldap for openSUSE: building wasm-pack fails due to #365
Labels
No labels
backend
blocked
bug
cleanup
dependencies
docker
documentation
duplicate
enhancement
enhancement
frontend
github_actions
good first issue
help wanted
help wanted
integration
invalid
ldap
pull-request
question
rust
rust
tests
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lldap-lldap#365
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @johanneskastl on GitHub (Oct 16, 2024).
Original GitHub issue: https://github.com/lldap/lldap/issues/1002
Hi,
I found lldap, tested it and really liked it. I know that there are packages for openSUSE, but I would like to create a official package, that can be installed from the distribution. If it has been accepted to Tumbleweed, it would be possible to include it in the upcoming Leap 16.0 release.
I have a working package, the only thing is the wasm-pack. Running the
wasm-packcommand fails. I have no rust or wasm experience, thus any pointers would be highly appreciated.Thanks in advance!
Kind Regards,
Johannes
Building for openSUSE Tumbleweed, using wasm-pack-0.13.0~0-2.1, rust1.81-1.81.0-2.1 and cargo1.81-1.81.0-2.1, I get the error message further below when running the build command:
I am currently using the code from the main branch at commit
a6eac55, as the 0.5.0 release did not build properly with rust1.81.The complete log file is here:
https://build.opensuse.org/package/live_build_log/home:ojkastl_buildservice:Branch_network_ldap/lldap-with-wasm-pack/openSUSE_Tumbleweed/x86_64
This is the part of the log where it starts throwing errors.
@nitnelave commented on GitHub (Oct 16, 2024):
From a first investigation (build is still running), it comes from updating all the dependencies. Instead, you should use the versions described in the
Cargo.lockfile (precise versions that are known to be good) by passing--lockedafter the--offline.@nitnelave commented on GitHub (Oct 16, 2024):
Alright, I sent a PR that updates the dependencies and fixes the breaks, but still, for a reproducible package, you should use the
--lockedflag.@kastl-ars commented on GitHub (Oct 17, 2024):
Thanks Valentin! I am one step forward, no I get an error due to wasm-bindgen missing.
I'll try to package that, hope that helps.
@nitnelave commented on GitHub (Oct 17, 2024):
@kastl-ars did you see https://github.com/rustwasm/wasm-pack/issues/1138 ?
@kastl-ars commented on GitHub (Oct 17, 2024):
No, but thanks for the hint. Setting
export RUST_LOG=debuggives the following:@nitnelave commented on GitHub (Oct 17, 2024):
And if you
cargo install -f wasm-bindgen?
@kastl-ars commented on GitHub (Oct 17, 2024):
Won't work as the build happens offline, hence I have to vendor everything upfront (or install it from the distribution).
@nitnelave commented on GitHub (Oct 17, 2024):
I think you'll need to install/vendor that. Not sure how, though, I'm not used to offline builds.
@kastl-ars commented on GitHub (Oct 17, 2024):
That is what I am currently trying to do...
@kastl-ars commented on GitHub (Oct 17, 2024):
I have packaged wasm-bindgen (the CLI) for openSUSE, installing it in the VM where the build happens leads to a successful build!
Thanks for your help, @nitnelave !