All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Regression bug: dbus messagebus user generation is wrong
Date: Thu, 22 Dec 2011 12:08:36 +0000	[thread overview]
Message-ID: <1324555716.24604.13.camel@ted> (raw)
In-Reply-To: <20111222091041.GI12791@jama.jama.net>

On Thu, 2011-12-22 at 10:10 +0100, Martin Jansa wrote:
> See http://bugzilla.pokylinux.org/show_bug.cgi?id=1711
> but it's still broken in some cases (on my buildhost 3 from 5 machines
> are broken, 2 are working after last opkg changes).

Do we have any more details on what is broken or how this is happening?
I'm at a loss as to how to help with this.

> Good test is to enable testlab and run this in your deploy/images directory
> find . ! -type l -name \*tar.gz`; do 
>   echo $i; 
>   tar -tvf $i | grep dbus-daemon-launch; 
>   tar --numeric-owner -tvf $i | grep dbus-daemon-launch; 
>   tar xzvpf $i ./etc/group; 
>   grep messagebus ./etc/group; 
> done | tee -a image.test
> 
> And working image needs to have not only messagebus as owner but also
> matching GID in 2nd line and last line from packaged /etc/group. With
> latest opkg fixes it seems to work, but only if there is messagebus in
> packaged /etc/group at all, reported here:
> http://lists.linuxtogo.org/pipermail/openembedded-core/2011-December/014619.html
> but probably got lost in other issues with new opkg, like this one
> http://lists.linuxtogo.org/pipermail/openembedded-core/2011-December/014654.html
> (if D is not needed to be set from opkg then why was offlineroot_varname.patch
> added in first place? and I have updated this after
> offlineroot_varname.patch removal and new version is in shr branch)

I added offlineroot_varname at a point when the export D in
rootfs_ipk.bbclass was later. In the final version I moved it and the
other exports earlier to fix different problems. The patch still looked
like a good idea at that point. When a problem appeared with the patch I
decided just to drop it. We should probably continue to export PKG_ROOT
for compatibility and maybe export D in addition to that.

Cheers,

Richard





  parent reply	other threads:[~2011-12-22 12:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-22  8:49 Regression bug: dbus messagebus user generation is wrong Bernhard Guillon
2011-12-22  9:02 ` Richard Purdie
2011-12-22  9:10 ` Martin Jansa
2011-12-22 10:06   ` Bernhard Guillon
2011-12-22 10:26   ` Koen Kooi
2011-12-22 12:04     ` Richard Purdie
2011-12-22 12:08   ` Richard Purdie [this message]
2011-12-22 13:17   ` Martin Jansa
2011-12-22 15:52     ` Mark Hatle
2011-12-22 16:10       ` Martin Jansa
2011-12-22 18:02       ` Richard Purdie

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=1324555716.24604.13.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.