All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: openembedded-core@lists.openembedded.org, sgw@linux.intel.com,
	scott.a.garman@intel.com, richard.purdie@linuxfoundation.org
Cc: Darren Hart <dvhart@linux.intel.com>
Subject: [PATCH 0/1] [YOCTO 1211]: revert sudo upgrade to fix rootless X
Date: Fri, 15 Jul 2011 22:42:47 -0700	[thread overview]
Message-ID: <cover.1310794521.git.dvhart@linux.intel.com> (raw)

I found the recent sudo upgrade to be the cause of Yocto Bug 1211. I have
reviewed the sudo changelogs and didn't notice any changes to indicate that the
xserver-nodm init script was misusing sudo. Reverting the upgrade resolves the
issue. As the commit message doesn't indicate it was anything other than a
routine upgrade (and not a bug fix) I suggest we revert it until it can be shown
to work properly with xserver-nodm for rootless X.


The following changes since commit fa4bcfdb73167f8159b88e5a4d711c0d37627a70:

  bb-matrix: correct BB and PM number canonicalization (2011-07-14 22:23:09 +0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib dvhart/sudo
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dvhart/sudo

Darren Hart (1):
  Revert "sudo: upgrade to v1.8.1p2"

 meta/recipes-extended/sudo/sudo.inc                |   27 +++++++++++--------
 .../sudo/{sudo_1.8.1p2.bb => sudo_1.7.4p6.bb}      |    4 +-
 2 files changed, 18 insertions(+), 13 deletions(-)
 rename meta/recipes-extended/sudo/{sudo_1.8.1p2.bb => sudo_1.7.4p6.bb} (52%)




             reply	other threads:[~2011-07-16  5:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-16  5:42 Darren Hart [this message]
2011-07-16  5:42 ` [PATCH 1/1] Revert "sudo: upgrade to v1.8.1p2" Darren Hart

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=cover.1310794521.git.dvhart@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=scott.a.garman@intel.com \
    --cc=sgw@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 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.