Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: dbus broken again
Date: Wed, 2 Nov 2011 11:55:28 +0100	[thread overview]
Message-ID: <20111102105528.GE9949@jama.jama.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 2381 bytes --]

After last attempt to fix dbus there is new issue

I have talked with Richard on IRC already, but will repeat it here just
to warn other dbus users.

Updated list of available packages in /var/lib/opkg/lists/jama-om_gta02.
Upgrading dbus-1 on root from 1.4.12-r2 to 1.4.12-r7...
Downloading
http://jama.dyndns-home.com/org.openembedded.shr-core//armv4t/dbus-1_1.4.12-r7_armv4t.ipk.
Running groupadd commands...
Note: group netdev already exists, not re-creating it
Running useradd commands...
Note: username messagebus already exists, not re-creating it
Upgrading libdbus-1-3 on root from 1.4.12-r2 to 1.4.12-r7...
Downloading
http://jama.dyndns-home.com/org.openembedded.shr-core//armv4t/libdbus-1-3_1.4.12-r7_armv4t.ipk.
Upgrading libglib-2.0-0 on root from 1:2.30.0-r2 to 1:2.30.0-r3...
Downloading
http://jama.dyndns-home.com/org.openembedded.shr-core//armv4t/libglib-2.0-0_2.30.0-r3_armv4t.ipk.
Configuring dbus-1.
 System startup links for /etc/init.d/dbus-1 already exist.
Configuring libdbus-1-3.
Configuring libglib-2.0-0.

SHR root@gjama / $ ll /usr/libexec/dbus-daemon-launch-helper
-rwsr-xr-- 1 root 998 142748 Nov  2 10:12
/usr/libexec/dbus-daemon-launch-helper

SHR root@gjama / $ ll -d /var/lib/dbus
drwxr-xr-x 2 999 998 4096 Nov  2 10:12 /var/lib/dbus

SHR root@gjama / $ grep message /etc/group
messagebus:x:101:
SHR root@gjama / $ grep message /etc/passwd
messagebus:x:42:101:Linux User,,,:/var/run/dbus:/bin/sh


and that's because useradd.bbclass is using UID/GID from sysroots
OE om-gta02@shr ~/shr-core $ grep message tmp/sysroots/om-gta02/etc/group
messagebus:x:998:
OE om-gta02@shr ~/shr-core $ grep message tmp/sysroots/om-gta02/etc/passwd
messagebus:!:999:998::/var/lib/dbus:

and nothing is updating /etc/passwd /etc/group IDs on target.

The possible solution would be to force specified UID/GID in
useradd.bbclass to make it consistent during rebuild from scratch or
teach useradd postinst to update UID/GIDs and chown all runtime created
files to new values instead of skiping useradd/groupadd commnads when
user already exists, like it did now:
Note: username messagebus already exists, not re-creating it
Note: group netdev already exists, not re-creating it

Also reported here:
http://bugzilla.pokylinux.org/show_bug.cgi?id=1711

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

                 reply	other threads:[~2011-11-02 11:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20111102105528.GE9949@jama.jama.net \
    --to=martin.jansa@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox