Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debian Snapshot Archive Extremely Slow / Unavailable #8496

Closed
CoryRamsey opened this issue Jun 22, 2023 · 2 comments
Closed

Debian Snapshot Archive Extremely Slow / Unavailable #8496

CoryRamsey opened this issue Jun 22, 2023 · 2 comments

Comments

@CoryRamsey
Copy link

I'm on the second day of trying to do a wine build. The snapshot archive has been very slow, to the point of making it impossible to build. I'm on hour 5 of apt update with several timeouts already on my latest attempt. Obviously, I know no one here is in control of the snapshot repo, but I'm wondering if there is a known mirror for snapshots required for Electrum. Specifically, the debian/20230317T205011Z archive is what I'm referring to.

@SomberNight
Copy link
Member

Hi. This is a known issue. :/
Unfortunately snapshot.debian.org is often very slow and keeps timing out.
One alternative mirror is snapshot.notset.fr, but this does not work for the wine build specifically as it does not mirror the binary-i386 parts.

First of all, note that if you just want to build for yourself, you don't need to use these snapshot apt sources. You can just switch back to debian upstream. The snapshot mirrors are only needed for the reproducible builds.

If you do want reproducibility, then note that the ELECBUILD_NOCACHE=1 option is not expected to be needed anymore.
Setting that forces a rebuild of the docker image, which was needed to properly test historical reproducibility in the past, but since we switched to the snapshot apt sources, I expect it's redundant. So you can try without setting that -- and then at least you are only at the mercy of the snapshot apt mirrors once, and then the docker image will get cached.

@CoryRamsey
Copy link
Author

CoryRamsey commented Jun 22, 2023

I figured that was likely the case. I appreciate the response and additional info. That confirms what I thought I had sorted out while having plenty of time to poke around the build scripts and Dockerfile.

It's hard to complain about the snapshot archive. That's a pretty ridiculous thing to host. Thanks again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants