From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Andreas Müller" <schnitzeltony@googlemail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: postinst does not finish
Date: Wed, 17 Apr 2013 10:37:50 +0100 [thread overview]
Message-ID: <3344072.3yQMCnL6TJ@helios> (raw)
In-Reply-To: <CALbNGRQpB3dqZBzsftXeYz_P7GW8h_Lq6C6SD-Qj79qHzea0tw@mail.gmail.com>
On Wednesday 17 April 2013 11:03:30 Andreas Müller wrote:
> On Wed, Apr 17, 2013 at 10:28 AM, Paul Eggleton
> <paul.eggleton@linux.intel.com> wrote:
> > On Tuesday 16 April 2013 23:42:08 Khem Raj wrote:
> >> On Apr 16, 2013, at 11:28 PM, Andreas Müller
> >> <schnitzeltony@googlemail.com>
> >>
> >> wrote:
> >> > sorry again me with another issue. I updated all layers from master
> >> > few hours ago and built from scratch. On first boot with systemd
> >> > postinst never finishes. I see only:
> >> >
> >> > [** } A start job is running for Run pending postinsts
> >> >
> >> > and ** are moving around.
> >> >
> >> > Does anybody else face this one?
> >>
> >> ran into same issue. I disabled post installs to run on boot
> >
> > Could you guys please try to debug this and find out what is hanging here,
> > because with core-image-minimal and systemd I don't see this problem, the
> > run- postinsts script finishes as expected.
>
> are you using opkg as I do?
I wasn't, however I was under the impression Khem was also using rpm. Now I am
using opkg, and what I can see is that run-postinsts does take some time on
boot but it does appear to eventually finish and I don't get any error
indicating it failed; systemctl doesn't appear to list run-postinsts (although
I don't know whether it should or not.)
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-04-17 9:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 6:28 postinst does not finish Andreas Müller
2013-04-17 6:42 ` Khem Raj
2013-04-17 8:28 ` Paul Eggleton
2013-04-17 9:03 ` Andreas Müller
2013-04-17 9:37 ` Paul Eggleton [this message]
2013-04-17 18:27 ` Koen Kooi
2013-04-17 18:55 ` Burton, Ross
2013-04-17 20:26 ` Koen Kooi
2013-04-17 20:28 ` Burton, Ross
2013-04-18 18:45 ` Koen Kooi
2013-04-19 7:53 ` Koen Kooi
2013-04-19 8:38 ` Burton, Ross
2013-04-19 8:52 ` Burton, Ross
2013-04-19 9:13 ` Koen Kooi
2013-04-19 11:23 ` Laurentiu Palcu
2013-04-19 11:38 ` Koen Kooi
2013-04-19 12:26 ` Laurentiu Palcu
2013-04-19 12:49 ` Koen Kooi
2013-04-19 13:03 ` Burton, Ross
2013-04-19 13:13 ` Koen Kooi
2013-04-19 13:37 ` Koen Kooi
2013-04-19 14:00 ` Koen Kooi
2013-04-19 14:07 ` Koen Kooi
2013-04-21 6:59 ` Koen Kooi
2013-04-21 15:09 ` Richard Purdie
2013-04-22 8:36 ` Koen Kooi
2013-04-23 7:27 ` Andreas Müller
2013-04-23 7:43 ` Andreas Müller
2013-04-24 10:01 ` Andreas Müller
2013-04-17 14:57 ` Khem Raj
2013-04-17 15:11 ` Paul Eggleton
2013-04-17 15:32 ` Stanacar, StefanX
2013-04-17 9:07 ` Martin Jansa
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=3344072.3yQMCnL6TJ@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=schnitzeltony@googlemail.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