From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Nieuwenhuizen Subject: bug#29196: upstreaming of reproducibility related patches Date: Tue, 07 Nov 2017 19:08:21 +0100 Message-ID: <878tfim06i.fsf@gnu.org> References: <20171107171720.3qk5hhbbxsy3nclg@abyayala> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45913) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eC8J9-0002ne-8o for bug-guix@gnu.org; Tue, 07 Nov 2017 13:09:13 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eC8J5-0007Le-Tw for bug-guix@gnu.org; Tue, 07 Nov 2017 13:09:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:48275) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eC8J5-0007LJ-RK for bug-guix@gnu.org; Tue, 07 Nov 2017 13:09:03 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eC8J4-0000A9-9C for bug-guix@gnu.org; Tue, 07 Nov 2017 13:09:03 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20171107171720.3qk5hhbbxsy3nclg@abyayala> (ng0@infotropique.org's message of "Tue, 7 Nov 2017 17:17:20 +0000") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: ng0 Cc: 29196@debbugs.gnu.org ng0 writes: > as I wrote in #29135, we should upstream the patches we > gather for reproducibility. Share with upstream what is > applicable to more software than just Guix included > definitions of the software etc. > We have no list for this so far > We need to share this, to avoid duplicate work elsewhere. What about the reproducible builds list? https://lists.reproducible-builds.org/listinfo/rb-general General discussions about reproducible builds At the reproducible-builds summit last week in Berlin some work has been done on the topic of upstreaming patches. I think some effort has gone (is going?) into a email template that starts by explaining what reproducible-builds is, why it is important and why upstream should consider taking the patch. Greetings, janneke --=20 Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar=C2=AE http://AvatarAcademy.com