upstreaming of reproducibility related patches

  • Done
  • quality assurance status badge
Details
3 participants
  • Jan Nieuwenhuizen
  • Ludovic Courtès
  • ng0
Owner
unassigned
Submitted by
ng0
Severity
normal
N
(address . bug-guix@gnu.org)
20171107171720.3qk5hhbbxsy3nclg@abyayala
Hi,

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.
Attached to it: the usual conversation, outreach,
public relations, discussions thing.

We have no list for this so far, so we should first
look into the patch-file patches (the obvious ones,
in gnu/packages/patches/), and after that into some
maybe not so obvious fixes we keep in the definitions
themselves (via substitute etc).
So we need a list, and then motivated people can work
on this. Even if people is just a couple. It helps.

We need to share this, to avoid duplicate work elsewhere.
--
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAloB6qAACgkQ4i+bv+40
hYihEw//SfijSlzBEPCiSMNI4rORAjb5OsPjSn9WY3CnEN0hNcimypJMrO9EY+Xl
vT0fFoPjH7kQeAiLQqRj+OcR/4vPwybk9VQ3oAktv35299xERJaWg5dZssyPZhwU
44IPA6RBi9HBc2OWJh2Auodub80OafjEO/MyWunpaRoS/lLj4BVCELHDP1i02SkK
rEBsUqN+zjun0gymLWY+PZgl9ay2Gkh96hIQeEE+vkpiw0UtJ46dWIrZvPFOOHpH
Jc1rRsmGsb6gez+i/RfbfLAqgfoYzi2uUF60IfJlgKGgrbvhFlQDOMnmDHOkk6R4
8RfCefx1krZhERqU+htd5Gry92EkTpWB3yyU/Bn55Uo4kJYg5Mziy5elR8I/0r0e
385KfuZwzWXFfl6Olxz6oSuwYTtkAbAwB1CJkARjm/T76BZ2ed9q3PgME1hiCNHE
rTvIyJQja87FKE0v+nZqvBbsqmdcYbthUx1qDj6E3tgzoR6Z7dttiCgy1c1P0pn+
r8hy8lb4Tfs+9mA2QhanAB5KGsTwGZzifk3R2NE6Lx+tQb6NnkRi50i7AvMKWobf
tF8ha/2G5+a/IVM35YbLVUJ1dKYeuNITFuv61eN5fWwYLtPVnioh4SizMAFCkYfN
vswpq8CbXcq5nD+wDj5+H10t9GGEsVVYCFbBtmdxwYidtoxU+ZU=
=v4/1
-----END PGP SIGNATURE-----


J
J
Jan Nieuwenhuizen wrote on 7 Nov 2017 19:08
(name . ng0)(address . ng0@infotropique.org)(address . 29196@debbugs.gnu.org)
878tfim06i.fsf@gnu.org
ng0 writes:

Toggle quote (8 lines)
> 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?

General discussions about reproducible builds <rb-general@lists.reproducible-builds.org>

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

--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com| Avatar® http://AvatarAcademy.com
N
(name . Jan Nieuwenhuizen)(address . janneke@gnu.org)
20171108051243.2y52u2bo46oze6r3@abyayala
Jan Nieuwenhuizen transcribed 1.0K bytes:
Toggle quote (12 lines)
> 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?

Well, list as in a list that lists our patches, not a mailinglist ;)

Toggle quote (17 lines)
> General discussions about reproducible builds <rb-general@lists.reproducible-builds.org>
>
> 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
>
> --
> Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
> Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
>

--
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAloCkksACgkQ4i+bv+40
hYgt/w//fZtieQRSF/f3Vh3fwx0crU/Z4lj3a3/Rqiq5Dyv8dpIR7CwAOyKIEdQF
HHAOgoTlkeKpq7+YE7eNU0lQMq6qPM5svJopNlFK1ug0AdYQrt1LrVbVjg83cCQn
ndsuIlOKdhbwA6IsJh7Gh3hd3BdrAtmDI9cV75aMoNr/YSSnF+HuQ9fnOP+3I0+f
uEaMjXsxztZ+ovf8YxtV92Vech+JfznFwqLR9047PAj3RWerIU/DqkZ2nibhFHkK
Vc5hLL+CgCNdnu+7y36rbMgq/466AzR5qnKk5EI9i0lLIKSRKMOPZrqWUG/usmWU
MFoYFTC94vUG6fnzdM4INS6rRuQXdSWFrdcFRHYai+bjLoaSypVdWGLXgXGdg1cY
SYz78WwqyaOtP/6Cc8PRzS8SC3jg0xbh6wpViSAoJFLcH0GXqmsaCMQ2Z/Jkm1iR
CyWLbDHKHIw1NiSUS9X88T4yQ0+zHtnhy4JyPSMA0QaIOGM27hfvOIRERM3NYZPz
CRRrVTxw1xojmKpehfBURtpX1gQ2aAp94zzCWjq5Jjz5Irytn/N8LigOTCg3CaSj
t6WCMz2HoJc9xTbkGWN9JN8dHWqsQoepIUvI2iC52nhzHtV68044Mynt7fMzkY9L
o90gDQKEgZoOK/MRiMYhJ56yi9WiQAZOBjYqDOcJukTqM0RW7Ds=
=vUqu
-----END PGP SIGNATURE-----


L
L
Ludovic Courtès wrote on 14 Nov 2017 23:06
(name . Jan Nieuwenhuizen)(address . janneke@gnu.org)
87vaicldlm.fsf@gnu.org
Hello,

Jan Nieuwenhuizen <janneke@gnu.org> skribis:

Toggle quote (15 lines)
> 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 <rb-general@lists.reproducible-builds.org>

Indeed. There’s also the issue database initiated by Debian, which we
can contribute to and borrow from:


Since this is not a bug, please follow-up to guix-devel.

Thanks,
Ludo’.
L
L
Ludovic Courtès wrote on 14 Nov 2017 23:06
control message for bug #29196
(address . control@debbugs.gnu.org)
87tvxwldle.fsf@gnu.org
tags 29196 notabug
close 29196
?
Your comment

This issue is archived.

To comment on this conversation send an email to 29196@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 29196
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch