Open InnovativeInventor opened 4 years ago
Thanks for looking into this, but I have several questions:
chromium
source package. I'm having troubles seeing how a Dockerfile would be appropriate here. Maybe ungoogled-software/contrib would be a better place?I don't believe it is necessary to pin the exact hashes, but doing so ensures that everybody starts off with the same image, eliminating a source of non-reproducible. I have no clue what kind of optimizations the compiler does, but I felt that a reproducible build environment is a good step towards reproducible builds.
Yet another update: Can't seem to get the same .deb files -- planning on trying some other ideas from: https://reproducible-builds.org/tools/
Particularly: https://salsa.debian.org/reproducible-builds/strip-nondeterminism (add-on to debhelper)
To answer your question, I'll get other architectures (and Ubuntu) built once I manage to figure out how to make builds reproducible. There isn't a reason to use GitHub Actions if OBS works and GitHub Actions didn't in the past.
I've opened up a PR in ungoogled-software/contrib. (https://github.com/ungoogled-software/contrib/pull/2)
Has the Dockerfile ever been made available?
Has the Dockerfile ever been made available?
It's in the PR linked above your comment.
It seems like it has been stalled since 2020.
From: https://github.com/Eloston/ungoogled-chromium/issues/743
I've dockerized the build process on debian (so we can pin exact hashes of the version of debian we're building on). This is intended to aid in the production of reproducible binaries.
Once this is complete, we can use GitHub Actions to build it (a neutral, trusted platform) and have volunteers verify that the GitHub Actions build matches their own local build.
Note: Currently the build only targets
amd64
I'll be submitting a pull request once the build finishes (since an end-to-end dockerfile would be useful anyways to have).