Github messages for voidlinux
 help / color / mirror / Atom feed
From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: RFC: Check for reproducible builds.
Date: Fri, 30 Apr 2021 18:59:08 +0200	[thread overview]
Message-ID: <20210430165908.0BJoC1WBRGZMGlEOXQA0cu9Yu_b3VVDKhmxCF1BI0Bk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30588@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/pull/30588#issuecomment-830230405

Comment:
1. I enjoy seeing effort to increase build reproducibility.
2. Ericonr is right that presence of `source-revisions` increases reproducibility, as it provides information on what dependencies, build tools and packaging tools, including xbps-src build-style and hooks, all affecting resulting package, was used. However guarantee of mismatching checksum of packages built from different commits, even if diff is unrelated to package, may still pose a problem.
3. Some packages will still come out identical even without reproducing every dependency recursively since foundation of distro. As I understand, this PR aims to assess is it closer 5 or 75 percent of packages.
4. How do you plan to use this hook? Is it filling variable locally, then observing hook messages on builder? Is it to store historical checksums in source repository? I am asking, because we already collect checksum of packages in binary repo, as sig files. If your workflow could be reversed to verify official signatures against packages reproduced outside of builders, then all packages are already checksummed, and this hook may be not necessary.

  parent reply	other threads:[~2021-04-30 16:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30  8:18 [PR PATCH] " Gottox
2021-04-30 12:53 ` [PR REVIEW] " ericonr
2021-04-30 13:01 ` ericonr
2021-04-30 15:55 ` ericonr
2021-04-30 16:59 ` Chocimier [this message]
2021-04-30 17:18 ` ericonr
2021-04-30 17:45 ` ericonr
2021-04-30 23:56 ` Gottox
2021-05-01  0:00 ` Gottox
2021-05-01  0:57 ` ericonr
2021-05-01  1:01 ` ericonr
2021-05-21 13:49 ` [PR PATCH] [Closed]: " Gottox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210430165908.0BJoC1WBRGZMGlEOXQA0cu9Yu_b3VVDKhmxCF1BI0Bk@z \
    --to=chocimier@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).