Daniel Andrei R. Garcia
Daniel Andrei R. Garcia
Have the same problem. I just downloaded the AppImage from releases. Here's the error message: > WARNING: Could not find desktop file in AppDir, cannot create links for AppRun, desktop...
Thanks will try to get back to this.
docker build fails:  Dockerfile should be: ``` FROM ubuntu:focal ENV DEBIAN_FRONTEND=noninteractive RUN apt-get update && apt-get install --no-install-recommends -y git wget make autoconf automake libtool curl make g++ unzip...
Currently stuck with libfaketime errors  Trying again.
Third attempt to corroborate @Giszmo 's findings. In this **asciinema** cast file, you'll find that I used @Giszmo's Dockerfile settings and script. Same errors are reported. [rbdanny-onekey.touch_2023-12-12b.zip](https://github.com/OneKeyHQ/firmware/files/13645265/rbdanny-onekey.touch_2023-12-12b.zip)
The latest script is sending mixed messages, showing both `Failed` and `Success` messages on the same line. Checking again. ``` + export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/faketime/libfaketime.so.1 + LD_PRELOAD=/usr/lib/x86_64-linux-gnu/faketime/libfaketime.so.1 + export 'FAKETIME= 23:30:00' +...
After trying the latest script with `./onekey.sh 4.7.0 touch 1227 2023-12-27`, I get: ``` + export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/faketime/libfaketime.so.1 + LD_PRELOAD=/usr/lib/x86_64-linux-gnu/faketime/libfaketime.so.1 + export 'FAKETIME=2023-12-27 23:30:00' + FAKETIME='2023-12-27 23:30:00' + date Wed Dec...
1. **Non-Deterministic Build Processes**: Some build processes incorporate elements that can vary between builds, such as timestamps, filesystem paths, or data from the build environment. These variations can lead to...
> So, for reproducible builds it's best to use something like docker so everyone has the same build tools and the same versions of those build tools for example? Yes...
It would be more constructive for us to contribute to the discussion in walletscrutiny's gitlab issue for onekey. They have, in the past, replied extensively: https://gitlab.com/walletscrutiny/walletScrutinyCom/-/issues/469