openembedded-core.git/meta/recipes-devtools/pseudo, branch fido Mirror of openembedded-core pseudo_1.6.x.bb/pseudo_git.bb: Pseudo 1.6.4 2015-01-28T21:22:21+00:00 Peter Seebach peter.seebach@windriver.com 2015-01-23T02:23:56+00:00 67298d4fe6d96692a4e0578a44cc1a0bbf2cdc2b pseudo 1.6.3 merges (with some changes) the changes from Peter A. Bigot to make --without-fallback-passwd work. It also adds a proposed fix for Yocto bug #7097, which has passed the obvious tests I could think of. pseudo 1.6.4 fixes a silly configure bug introduced with 1.6.3. [YOCTO: #7097] Signed-off-by: Peter Seebach <peter.seebach@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
pseudo 1.6.3 merges (with some changes) the changes from
Peter A. Bigot to make --without-fallback-passwd work. It
also adds a proposed fix for Yocto bug #7097, which has
passed the obvious tests I could think of.

pseudo 1.6.4 fixes a silly configure bug introduced with
1.6.3.

[YOCTO: #7097]

Signed-off-by: Peter Seebach <peter.seebach@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
pseudo: remove older version and patches 2014-12-03T12:22:40+00:00 Saul Wold sgw@linux.intel.com 2014-11-19T18:22:52+00:00 73f418ce10a801f0befc06ffe54864563aea986c Signed-off-by: Saul Wold <sgw@linux.intel.com> 
Signed-off-by: Saul Wold <sgw@linux.intel.com>
pseudo: provide fallback passwd and group files 2014-11-25T12:58:21+00:00 Peter A. Bigot pab@pabigot.com 2014-11-01T11:48:03+00:00 91443426246fbe13083c19801b7c74365e041271 Normally pseudo is built with --without-passwd-fallback, which requires that somebody provide target passwd and group files. Those come from base-passwd in OE, but base-passwd cannot be built without first invoking operations under pseudo that require getpw*/getgr*. Provide the absolute minimum stub files, matching in content what will eventually be on the target, that can be used in the cases where the target files are not yet available. The requirements for minimum stub are the usernames and groups identified in meta/files/fs-perms.txt. Signed-off-by: Peter A. Bigot <pab@pabigot.com> 
Normally pseudo is built with --without-passwd-fallback, which requires
that somebody provide target passwd and group files.  Those come from
base-passwd in OE, but base-passwd cannot be built without first
invoking operations under pseudo that require getpw*/getgr*.

Provide the absolute minimum stub files, matching in content what will
eventually be on the target, that can be used in the cases where the
target files are not yet available.  The requirements for minimum stub
are the usernames and groups identified in meta/files/fs-perms.txt.

Signed-off-by: Peter A. Bigot <pab@pabigot.com>
pseudo: default --without-passwd-fallback 2014-11-25T12:58:21+00:00 Peter A. Bigot pab@pabigot.com 2014-10-31T18:13:19+00:00 899fe3d1d05054a10e4d427810c20ad1e34f916a No good reason exists to fall back to the build host /etc files when attempting to resolve user and group information. Recipe dependencies should be updated so the correct target files are available. Signed-off-by: Peter A. Bigot <pab@pabigot.com> 
No good reason exists to fall back to the build host /etc files when
attempting to resolve user and group information.  Recipe dependencies
should be updated so the correct target files are available.

Signed-off-by: Peter A. Bigot <pab@pabigot.com>
pseudo: support multiple search directories in PSEUDO_PASSWD 2014-11-25T12:58:20+00:00 Peter A. Bigot pab@pabigot.com 2014-10-12T21:58:52+00:00 15b3b796d6e06fb7a7867d132b234d783e733531 This makes it possible to use --without-passwd-fallback when building images where the preferred passwd files are not available until after installation has begun. Signed-off-by: Peter A. Bigot <pab@pabigot.com> 
This makes it possible to use --without-passwd-fallback when building
images where the preferred passwd files are not available until after
installation has begun.

Signed-off-by: Peter A. Bigot <pab@pabigot.com>
pseudo: support --without-passwd-fallback configuration option 2014-11-25T12:58:20+00:00 Peter A. Bigot pab@pabigot.com 2014-10-12T21:54:34+00:00 eb5b99e4fbfdf31497a4606fc55cab268ec8d654 A bug in pseudo 1.6.2 results in lock failures if this option is present. Signed-off-by: Peter A. Bigot <pab@pabigot.com> 
A bug in pseudo 1.6.2 results in lock failures if this option is
present.

Signed-off-by: Peter A. Bigot <pab@pabigot.com>
pseudo*.bb: update to pseudo 1.6.2 2014-10-06T14:07:59+00:00 Peter Seebach peter.seebach@windriver.com 2014-10-03T22:58:31+00:00 b2c6a032d6e5deb07e76ed75fcd0931fad6a748c pseudo 1.6.2 fixes problems with 64-bit inodes and some underlying issues involving file renames that could occasionally cause very strange behaviors files being deleted, linked, or renamed, mostly observed as strange recovery if an inode got reused. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
pseudo 1.6.2 fixes problems with 64-bit inodes and some underlying issues
involving file renames that could occasionally cause very strange behaviors
files being deleted, linked, or renamed, mostly observed as strange
recovery if an inode got reused.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
pseudo: uprev to 1.6.1 2014-07-18T23:16:33+00:00 Peter Seebach peter.seebach@windriver.com 2014-07-18T18:49:25+00:00 f3b5421a9c95b5516e5810285729affe80729135 Pseudo now automatically tries to shut down the server after running single commands under pseudo ("pseudo <cmd>"), which means it can print a useless "server already offline" message in some cases. The message has been changed to a debugging message only. The glibc symbol versions for memcpy were being applied to non-x86 targets, unintentionally, which broke builds for at least some targets. (But pseudo doesn't usually get built for targets so it didn't get noticed right away.) Signed-off-by: Peter Seebach <peter.seebach@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Pseudo now automatically tries to shut down the server after running
single commands under pseudo ("pseudo <cmd>"), which means it can
print a useless "server already offline" message in some cases. The
message has been changed to a debugging message only.

The glibc symbol versions for memcpy were being applied to non-x86
targets, unintentionally, which broke builds for at least some targets.
(But pseudo doesn't usually get built for targets so it didn't
get noticed right away.)

Signed-off-by: Peter Seebach <peter.seebach@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
pseudo_1.6.0.bb: uprev to pseudo 1.6 2014-07-16T09:13:13+00:00 Peter Seebach peter.seebach@windriver.com 2014-07-14T19:12:29+00:00 b8f5d6b493ec759a97b92cf9b4c07ad8a8114de6 This uprevs pseudo to 1.6. This merges in all of the existing fixes, and also adds partial support for extended attributes, including storing arbitrary extended attributes in the database, and also interpreting the posix permissions ACLs as chmod requests. The extended attribute support means we need xattr.h, the simplest way to be sure of this is to build attr before pseudo, which doesn't take long. Signed-off-by: Peter Seebach <peter.seebach@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
This uprevs pseudo to 1.6. This merges in all of the existing
fixes, and also adds partial support for extended attributes,
including storing arbitrary extended attributes in the database,
and also interpreting the posix permissions ACLs as chmod
requests.

The extended attribute support means we need xattr.h, the simplest
way to be sure of this is to build attr before pseudo, which doesn't
take long.

Signed-off-by: Peter Seebach <peter.seebach@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
pseudo: Honor umask again 2014-05-28T07:19:16+00:00 Peter Seebach peter.seebach@windriver.com 2014-05-28T00:14:46+00:00 ce23c1cc33a015fbd184df6c16658353334ab611 The fchmodat-permissions patch was fine for the fchmod case, but had the unintended side effect of disregarding umask settings for open, mknod, mkdir, and their close relatives. Start tracking umask and masking the umask bits out where appropriate. Signed-off-by: Peter Seebach <peter.seebach@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
The fchmodat-permissions patch was fine for the fchmod case, but
had the unintended side effect of disregarding umask settings for
open, mknod, mkdir, and their close relatives. Start tracking umask
and masking the umask bits out where appropriate.

Signed-off-by: Peter Seebach <peter.seebach@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>