From: cedric_hombourger@mentor.com
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [ANNOUNCE] Upcoming ISAR release
Date: Tue, 26 Feb 2019 06:23:34 -0800 (PST) [thread overview]
Message-ID: <465e23f7-41bb-4162-af75-63160653425f@googlegroups.com> (raw)
In-Reply-To: <94924dd9-ae84-4e10-655f-a4afa86842a7@siemens.com>
[-- Attachment #1.1: Type: text/plain, Size: 1440 bytes --]
I agree that reproducible builds should be on the list.
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
>
[-- Attachment #1.2: Type: text/html, Size: 1777 bytes --]
prev parent reply other threads:[~2019-02-26 14:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 9:01 Maxim Yu. Osipov
2019-02-18 9:58 ` Claudius Heine
2019-02-18 10:29 ` Maxim Yu. Osipov
2019-02-18 11:52 ` Claudius Heine
2019-02-18 17:16 ` Henning Schild
2019-02-18 20:09 ` Jan Kiszka
2019-02-18 10:07 ` Henning Schild
2019-02-18 10:25 ` Jan Kiszka
2019-02-26 14:23 ` cedric_hombourger [this message]
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=465e23f7-41bb-4162-af75-63160653425f@googlegroups.com \
--to=cedric_hombourger@mentor.com \
--cc=isar-users@googlegroups.com \
/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