[Slackbuilds-users] Updates - 20170715.1 ownership

[Matteo Bernardini]

2017-07-15 3:15 GMT+02:00 Andrzej Telszewski <atelszewski at gmail.com>:
> On 15/07/17 02:53, Willy Sudiarto Raharjo wrote:
>>
>> We are back to our normal weekend public updates and not so many updates
>> this time, but we do have ownership fixes from Sebastian. This is also a
>> good reminder for all maintainers NOT TO USE cp -a when trying to copy
>> something from $CWD or else it will have a strange owner instead of
>> root. If you want to copy things from the directory that the source
>> created, cp -a is fine. Since this is harmless, i didn't bump the BUILD
>> number.
>
>
>> If you want to copy things from the directory that the source
>> created, cp -a is fine.
>
>
> It is fine as long as the source creates correct ownership.
> We have some examples of upstream tarballs that are packaged in a way that
> for example only 'owner' has read/write set, the rest has no permissions at
> all.
>
> Just a heads up.

to clarify: one of the first things we do in our templates, just after
uncompressing the upstream tarball, is executing this block

chown -R root:root .
find -L . \
 \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
  -o -perm 511 \) -exec chmod 755 {} \; -o \
 \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
  -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;

after running this ownership and permissions are fine in the sources
directory, so it's safe to execute cp -a from there (I think Willy
meant that).

Matteo