public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Alexander Smirnov <asmirnov@ilbers.de>
To: "Storm, Christian" <christian.storm@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: Reproducibility of builds
Date: Wed, 6 Dec 2017 19:21:21 +0300	[thread overview]
Message-ID: <861d2cde-e85a-6220-6867-188d5f520793@ilbers.de> (raw)
In-Reply-To: <adfca85e-53b6-8cc9-e8fd-5cd9f16c41c3@denx.de>

Hi Christian,

[...]

I've pushed my branch 'build_rep' which does the following:

1. Prepare list of packages being used by buildchroot, images and 
packages to be built;

2. Create local apt with the packages listed above.

3. Generate buildchroot and image from local apt.

So it uses only one 'downloading' session.

Could you please test this branch with your custom meta?

Alex

      reply	other threads:[~2017-12-06 16:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03  8:13 Claudius Heine
2017-08-21 11:23 ` Claudius Heine
2017-08-28 11:27   ` Claudius Heine
2017-09-05 10:05     ` Alexander Smirnov
2017-09-05 10:38       ` Jan Kiszka
2017-09-05 11:50         ` Alexander Smirnov
2017-09-05 11:54       ` Claudius Heine
2017-09-06 13:39         ` Claudius Heine
2017-09-18 15:05 ` Baurzhan Ismagulov
2017-09-19  8:55   ` Claudius Heine
2017-11-14 16:04 ` Christian Storm
2017-11-14 16:22   ` Claudius Heine
2017-11-17 16:53     ` [ext] Christian Storm
2017-11-17 18:14       ` Claudius Heine
2017-11-20  8:33         ` [ext] Christian Storm
2017-11-20  9:16           ` Claudius Heine
2017-11-29 18:53             ` Alexander Smirnov
2017-11-29 19:02               ` Jan Kiszka
2017-11-30  8:04                 ` Alexander Smirnov
2017-11-30 14:48                   ` Jan Kiszka
2017-11-30  9:31               ` Claudius Heine
2017-12-06 16:21                 ` Alexander Smirnov [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=861d2cde-e85a-6220-6867-188d5f520793@ilbers.de \
    --to=asmirnov@ilbers.de \
    --cc=christian.storm@siemens.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