Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: postinst does not finish
Date: Fri, 19 Apr 2013 14:23:38 +0300	[thread overview]
Message-ID: <5171293A.5010300@intel.com> (raw)
In-Reply-To: <623CB95B-FD17-49A5-9547-71E0EFC316A7@dominion.thruhere.net>



On 04/19/2013 12:13 PM, Koen Kooi wrote:
> 
> Op 19 apr. 2013, om 10:52 heeft "Burton, Ross" <ross.burton@intel.com> het volgende geschreven:
> 
>> On 19 April 2013 09:38, Burton, Ross <ross.burton@intel.com> wrote:
>>> On 18 April 2013 19:45, Koen Kooi <koen@dominion.thruhere.net> wrote:
>>>> [koen@rrMBP 1.0-r0]$ grep "configuration required on target" temp/log.do_rootfs
>>>> gdk-pixbuf-loader-png.postinst returned 1, marking as unpacked only, configuration required on target.
>>> ..
>>>
>>> This is "usual" for postinsts that are intercepted and handled in a
>>> single go - scroll further down the log and you should see the package
>>> manager running the intercept scripts (i.e. fontcaches once, gconftool
>>> once).  I expect you'll see there that the gconftool intercept is
>>> breaking for some reason.
>>
>> Actually gconf isn't using triggers but it should happen on the host.
>>
>> I wonder if we're hitting a problem where the postinsts are doing some
>> actions on the host and then triggers are "erroring" out and it's all
>> falling back to the target.  Can you share the complete rootfs log for
>> this gnome image?
> 
> Here's the complete log: http://dominion.thruhere.net/koen/angstrom/beaglebone/log.do_rootfs
Do you think you can post the rootfs/var/lib/opkg/status file? This
would show us exactly what packages were postponed for first boot.

Thanks,
Laurentiu
> 
> Todays build is still building :(
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
> 



  reply	other threads:[~2013-04-19 11:41 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
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 [this message]
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=5171293A.5010300@intel.com \
    --to=laurentiu.palcu@intel.com \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.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