From: Henning Schild <henning.schild@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH 0/4 v5] Isar apt deployment
Date: Wed, 18 Oct 2017 15:44:04 +0200 [thread overview]
Message-ID: <20171018154404.25953ccd@md1em3qc> (raw)
In-Reply-To: <fef37a35-eae6-90a6-0285-e36b06a628ec@ilbers.de>
On Wed, 18 Oct 2017 14:06:53 +0300
Alexander Smirnov <asmirnov@ilbers.de> wrote:
> Hi,
>
> > i just tried it and the task do_cache_config was not executed before
> > the first do_populate.
>
> Could you please specify more details:
>
> - Build command
Well i am using layering, and so is Claudius. So the command wont help
you much. It should basically boil down to
bitbake multiconfig:qemuamd64-stretch:isar-image-base
> - Commit ID
f33e48bd07039032e3
I am guessing you can not reproduce the issue, we should find out why.
But since Claudius confirmend that he can not use these patches either,
and there are still some open points, i think you should remove those
patches from next.
Henning
> Alex
>
> >
> > I would suggest the following changes:
> > - create one task in dpkg-base.bbclass that does the following
> > - config and init reprepro if no other recipe did that before
> > - add package
> > - use bitkages task[lockfiles] to deal with races between recipes,
> > put distro into lockfile-name so we have one lock per distro
> > - drop do_populate
> > - call the new task instead of, or in do_deploy_deb
> >
> > Henning
> >
> > Am Thu, 5 Oct 2017 13:08:03 +0300
> > schrieb Alexander Smirnov <asmirnov@ilbers.de>:
> >
> >> Hi all,
> >>
> >> this series switch Isar internal binary package processing to apt
> >> repository. It performs this following:
> >>
> >> 1. Create repositories 'tmp/deploy/apt' for all architectures
> >> requested by multiconfig.
> >>
> >> 2. Generate reprepro database.
> >>
> >> 3. Put all the newly built packages to apt repository.
> >>
> >> 4. Pass this Isar repository to image multistrap.
> >>
> >> Documentation will be updated after agreement on this
> >> implementation.
> >>
> >> Changes since v4:
> >> - Drop meta-isar-bin layer.
> >>
> >> With best regards,
> >> Alex
> >>
> >> Alexander Smirnov (4):
> >> apt: Generate configs for apt
> >> apt: Generate Isar reprepro database
> >> apt: Populate Isar apt
> >> apt: Install packages via multistrap
> >>
> >> meta-isar/conf/layer.conf | 13 ++++-
> >> meta-isar/conf/local.conf.sample | 4 ++
> >> .../recipes-core/images/files/distributions.in | 3 +
> >> .../recipes-core/images/files/multistrap.conf.in | 9 ++-
> >> meta-isar/recipes-core/images/isar-image-base.bb | 6 +-
> >> meta/classes/ext4-img.bbclass | 2 +-
> >> meta/classes/image.bbclass | 65
> >> +++++++++++++++++++--- 7 files changed, 88 insertions(+), 14
> >> deletions(-) create mode 100644
> >> meta-isar/recipes-core/images/files/distributions.in
> >>
> >
>
next prev parent reply other threads:[~2017-10-18 13:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 10:08 Alexander Smirnov
2017-10-05 10:08 ` [PATCH 1/4] apt: Generate configs for apt Alexander Smirnov
2017-10-05 11:14 ` Claudius Heine
2017-10-05 11:43 ` Alexander Smirnov
2017-10-05 12:01 ` Claudius Heine
2017-10-05 10:08 ` [PATCH 2/4] apt: Generate Isar reprepro database Alexander Smirnov
2017-10-05 11:43 ` Claudius Heine
2017-10-09 12:04 ` Henning Schild
2017-10-05 10:08 ` [PATCH 3/4] apt: Populate Isar apt Alexander Smirnov
2017-10-05 10:08 ` [PATCH 4/4] apt: Install packages via multistrap Alexander Smirnov
2017-10-19 15:24 ` [PATCH 4/4 v6] " Alexander Smirnov
2017-10-09 12:00 ` [PATCH 0/4 v5] Isar apt deployment Henning Schild
2017-10-12 10:42 ` Claudius Heine
2017-10-18 11:06 ` Alexander Smirnov
2017-10-18 13:44 ` Henning Schild [this message]
2017-10-18 17:10 ` Alexander Smirnov
2017-10-18 17:14 ` Alexander Smirnov
2017-10-19 16:16 ` Henning Schild
2017-10-19 19:38 ` Alexander Smirnov
2017-10-19 8:41 ` Henning Schild
2017-10-19 9:54 ` Baurzhan Ismagulov
2017-10-19 13:30 ` Henning Schild
2017-10-19 15:14 ` Alexander Smirnov
2017-11-21 12:43 ` Christian Storm
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=20171018154404.25953ccd@md1em3qc \
--to=henning.schild@siemens.com \
--cc=asmirnov@ilbers.de \
--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