Re: Rant about Debian reproducibility environment

2018-03-07 Thread Steffen Nurpmeso
Ian Jackson wrote: |Steffen Nurpmeso writes ("Re: Rant about Debian reproducibility environment"\ |): |> But despite that and the possibly correct observation that placing |> just about any environmental info in any non-system-dependent |> object you can close the issue t

Re: Rant about Debian reproducibility environment

2018-03-06 Thread Steffen Nurpmeso
Paride Legovini wrote: |On 2018-03-01 18:17, Steffen Nurpmeso wrote: |> But last week Paride committed "fixes"[1] after having been |> prodded by some third party, and indeed, now S-nail is |> reproducible on all Debian test boxes. The fix was to set the |> built-in identification for the OS

Re: Rant about Debian reproducibility environment

2018-03-06 Thread Paride Legovini
On 2018-03-01 18:17, Steffen Nurpmeso wrote: > > But last week Paride committed "fixes"[1] after having been > prodded by some third party, and indeed, now S-nail is > reproducible on all Debian test boxes. The fix was to set the > built-in identification for the OS build environment to all > "De

Re: Rant about Debian reproducibility environment

2018-03-05 Thread Ian Jackson
Steffen Nurpmeso writes ("Re: Rant about Debian reproducibility environment"): > But despite that and the possibly correct observation that placing > just about any environmental info in any non-system-dependent > object you can close the issue that is my rant, but will not

Re: Rant about Debian reproducibility environment

2018-03-02 Thread Steffen Nurpmeso
Paul Wise wrote: |On Fri, Mar 2, 2018 at 1:17 AM, Steffen Nurpmeso wrote: |> I try to make it short, but i want to say i am thankful for the |> spark that reproducible-build.org was for me. Even though i think |> it is a pity that $SOURCE_DATE_EPOCH is the sole indicator for |> reproducible

Re: Rant about Debian reproducibility environment

2018-03-02 Thread Steffen Nurpmeso
Simon McVittie wrote: |On Thu, 01 Mar 2018 at 19:49:13 +0100, Steffen Nurpmeso wrote: |> Simon McVittie wrote: |>|Why is the kernel version on the machine where s-nail was compiled useful |>|to you? |> |> This is indeed correct, and i have changed $OSENV to go for |> uname(1) -sm instead

Re: Rant about Debian reproducibility environment

2018-03-01 Thread Paul Wise
On Fri, Mar 2, 2018 at 1:17 AM, Steffen Nurpmeso wrote: > I try to make it short, but i want to say i am thankful for the > spark that reproducible-build.org was for me. Even though i think > it is a pity that $SOURCE_DATE_EPOCH is the sole indicator for > reproducible environments, since now tha

Re: Rant about Debian reproducibility environment

2018-03-01 Thread Simon McVittie
On Thu, 01 Mar 2018 at 19:49:13 +0100, Steffen Nurpmeso wrote: > Simon McVittie wrote: > |Why is the kernel version on the machine where s-nail was compiled useful > |to you? > > This is indeed correct, and i have changed $OSENV to go for > uname(1) -sm instead of -srm. Continuing that thought

Re: Rant about Debian reproducibility environment

2018-03-01 Thread Steffen Nurpmeso
Hello Simon, Simon McVittie wrote: |On Thu, 01 Mar 2018 at 18:17:20 +0100, Steffen Nurpmeso wrote: |> And, of course, if there is a different kernel version, or |> a different uname(1) output as such, then how could a dumb end |> producer[consumer, the author] like S-nail deal with that

Re: Rant about Debian reproducibility environment

2018-03-01 Thread Simon McVittie
On Thu, 01 Mar 2018 at 18:17:20 +0100, Steffen Nurpmeso wrote: > And, of course, if there is a different kernel version, or > a different uname(1) output as such, then how could a dumb end > producer[consumer, the author] like S-nail deal with that? We > hardwire those attributes into the