public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v5 0/5] Debootstrap integration
Date: Tue, 10 Apr 2018 13:38:26 +0200	[thread overview]
Message-ID: <687b0519-4be6-b1a8-87d8-47179bd8c574@siemens.com> (raw)
In-Reply-To: <20180409124853.GA4414@yssyq.radix50.net>

Hi,

On 04/09/2018 02:48 PM, Baurzhan Ismagulov wrote:
> On Mon, Apr 09, 2018 at 12:50:56PM +0200, Jan Kiszka wrote:
>> what's the status of this series from upstream perspective now? Claudius
>> sent a documentation update. Any further requirements that need to be
>> fulfilled prior to this becoming ready for merge?
> 
> Sorry for the delay, I'm still investigating the following issues:
> 
> 1. CI fails with the series applied, and
> 
> 2. The series drops Pre-Depends support and daemon starting prevention.
> 
> 
> Regarding (1): As the series removes hostname setting, the image inherits the
> hostname of the build host. I.e., images generated on different build hosts
> have different hostnames. CI already checks the hostname and fails.
> 
> I'd suggest to restore at least the one-liner setting the hostname, possibly in
> {debian,raspbian}-configscript.sh.

I just send a patch that sets the hostname in the example-raw recipe.

> 
> Regarding (2): The motivation for the old configscript.sh / setup.sh
> distinction was to support Pre-Depends. "Sometimes, unpacking one package
> requires that another package be first unpacked and configured. In this case,
> the depending package must specify this dependency in the Pre-Depends control
> field." [1].
> 
> Besides that, setup.sh prevented daemons from being started during the
> configuration, which they otherwise are.
> 
> The series happens to work with Isar's minimal set of packages. ATM, I'm not
> sure about the implications for real projects with more packages. What should
> we do with this?

I took a look at those configscripts and some cleanup there might be 
necessary. For instance I don't know if:

     dpkg --configure -a

is still necessary to be done here, since all packages should be 
installed via apt now.

So maybe I should also prepare a patch that removes all those presumably 
unnecessary commands.

Cheers,
Claudius

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

  parent reply	other threads:[~2018-04-10 11:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-03 10:07 claudius.heine.ext
2018-04-03 10:07 ` [PATCH v5 1/5] implement isar-bootstrap using debootstrap claudius.heine.ext
2018-04-03 10:07 ` [PATCH v5 2/5] meta/isar-bootstrap-helper.bbclass: handle rfs customization centrally claudius.heine.ext
2018-04-03 10:08 ` [PATCH v5 3/5] meta/buildchroot: switch to using isar-bootstrap claudius.heine.ext
2018-04-03 10:08 ` [PATCH v5 4/5] meta-isar/isar-image-base: " claudius.heine.ext
2018-04-03 10:08 ` [PATCH v5 5/5] meta-isar/multiconfig: remove multistrap references claudius.heine.ext
2018-04-04 20:34 ` [PATCH v5 0/5] Debootstrap integration Baurzhan Ismagulov
2018-04-05  8:03   ` Claudius Heine
2018-04-05  9:16     ` Jan Kiszka
2018-04-11  6:28       ` Baurzhan Ismagulov
2018-04-11  6:58         ` Jan Kiszka
2018-04-11  7:04         ` Claudius Heine
2018-04-09 10:50     ` Jan Kiszka
2018-04-09 12:48       ` Baurzhan Ismagulov
2018-04-09 14:47         ` Jan Kiszka
2018-04-10 11:38         ` Claudius Heine [this message]
2018-04-10 20:49           ` Baurzhan Ismagulov
2018-04-11  5:59 ` Baurzhan Ismagulov

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=687b0519-4be6-b1a8-87d8-47179bd8c574@siemens.com \
    --to=claudius.heine.ext@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