[OE-core] [PATCH 1/1] pseudo_1.7.1.bb: New version of pseudo

[Peter Seebach]

On Thu, 3 Sep 2015 09:43:50 +0100
Richard Purdie <richard.purdie at linuxfoundation.org> wrote:

> This is better however opkg is still unhappy. This is build with this
> pseudo patch applied:
> 
> https://autobuilder.yoctoproject.org/main/builders/nightly-ipk/builds/469

I've found the cause of that particular bit. During my attempts to reproduce
this, I ran into segfaults in cross-localedef that I cannot now reproduce.

The cause of this was fixing up filesystem modes for the case where umask
contains 0200, which wasn't originally expected to work, but which was
breaking the xattrdb code. (There are a few things in the system which create
files with umask 0777, it turns out; this is arguably bad, but now there's a
workaround.)

But when I put in the workaround, I used 0600 as the "definitely at least
these bits" mode, instead of the requested mode, and that breaks scripts
which were expecting, say, 0700. So the things which have a specified mode
now use that | 0600 instead of just 0600.

I want to run a couple more things to see whether I can get any of the other
failures to come back again.

I also partially know why I wasn't seeing this on one of my systems, but only
partially. When I do my builds on CentOS 6.5, the .postinst files in question
either don't come into existence, or get run successfully anyway. So far as
I can tell, opkg is doing "sh -c /path/to/script" on those, which requires
0700 to run. I'm not sure what's causing the difference between the hosts.

-s
-- 
Listen, get this.  Nobody with a good compiler needs to be justified.