From: Christian Storm <christian.storm@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: Minimizing isar-image-base
Date: Thu, 23 Aug 2018 08:29:36 +0200 [thread overview]
Message-ID: <20180823062936.rnjynpv7dorwywm7@MD1KR9XC.ww002.siemens.net> (raw)
In-Reply-To: <16563606f48.27ac.034a6b0541ed39b7fb4e17f4ac219eaa@ilbers.de>
Hi,
> >>>> - Why do we pre-install dbus?
> >>>
> >>> Again, IIRC, without dbus there was dirty boot log in QEMU, some
> >>> services failed to start.
> >>
> >> I'll recheck that with stretch.
> >
> > Removed it, but I'm not seeing any error messages nor does systemctl
> > report failed services.
> > Maybe the bug was solved in stretch. Christian,
> > you said there is a harder dependency in reality than the "recommends"
> > as Debian declares now. Any comments on this?
> >
> > If it is really no longer needed, we could push the dbus dependency into
> > debian-jessie.conf. Is raspbian-jessie on systemd as well? Then there as
> > well.
>
> One another thing changed since that time - migration from multistrap to
> debootstrap. Probably this could be the reason.
There was a bug when debootstrap'ing that you had to explicitly install
dbus in order to make systemd happy and that was not reflected in the
packages' dependencies, hence it broke. This might have been fixed
upstream by now...
Kind regards,
Christian
--
Dr. Christian Storm
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Otto-Hahn-Ring 6, 81739 M�nchen, Germany
next prev parent reply other threads:[~2018-08-23 6:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 7:22 Jan Kiszka
2018-08-20 7:24 ` Jan Kiszka
2018-08-21 19:36 ` Alexander Smirnov
2018-08-22 14:37 ` Jan Kiszka
2018-08-22 19:52 ` Jan Kiszka
2018-08-22 20:43 ` Alexander Smirnov
2018-08-23 6:29 ` Christian Storm [this message]
2018-08-28 13:45 ` Jan Kiszka
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=20180823062936.rnjynpv7dorwywm7@MD1KR9XC.ww002.siemens.net \
--to=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