I have a patch to the dpkg-raw class which I will submit shortly to avoid getting a new timestamp in debian/changelog with every build

In other words, there are two parallel tracks / work-packages towards reproducible builds (at least that I see):

(1) get fixed content from designated upstream sources (ie what is being delineated below)

(2) identify and fix areas where Isar is generating/building content in a non reproducible way

It would be really nice if we could come up with some tooling to report differences between two Isar builds (obviously leveraging tools used by the Debian project such as diffoscope)

Cedric

On Monday, February 18, 2019 at 11:25:06 AM UTC+1, Jan Kiszka wrote:

On 18.02.19 10:01, Maxim Yu. Osipov wrote:
> Hello everybody,
>
> Last release (v0.6) was made on 1st of October 2018.
>
> We plan to release the next version of ISAR on 1st of March, 2019.
>
> BTW, what do you think about making a 1.0 release?

At least reproducible build should be solved for that. I think we have currently
three open issues in that area:

  - switching between cached and non-cached builds on the fly
  - cache unconditionally (make related task implicit)
  - cache source package (re-)builds

Jan

--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux