linux/poky.git/meta/recipes-core/base-files, branch master

The poky repository master branch is no longer being updated.

2025-11-07T13:31:53+00:00

You can either: a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs b) use the new bitbake-setup You can find information about either approach in our documentation: https://docs.yoctoproject.org/ Note that "poky" the distro setting is still available in meta-yocto as before and we continue to use and maintain that. Long live Poky! Some further information on the background of this change can be found in: https://lists.openembedded.org/g/openembedded-architecture/message/2179 Signed-off-by: Richard Purdie

meta: set S from UNPACKDIR in recipes that use only local files

2025-06-20T11:07:26+00:00

There is no need to have two assignments; also setting S from UNPACKDIR (and not vice versa) is more logical as unpack task comes first, and tasks that come after unpack use S to access unpack results. Also adjust reference test data in selftest/recipeutils to reflect changes in test recipes. (From OE-Core rev: f64b7e5fb3181734c8dde87b27e872a026261a74) Signed-off-by: Alexander Kanavin Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

base-files: add nsswitch-resolved.conf and remove nsswitch patch

2025-05-27T08:01:17+00:00

Due to changes to nsswitch.conf file on commit 0cb122f17cf2 ("base-files: add gshadow entry in nsswitch.conf"), the current patch does not apply anymore due to patch fuzz. This fuzz wasn't detected before because this is a conditional patch, and will be hard to detect if nsswitch.conf changes again. Instead, add a new version of nsswitch.conf, called nsswitch-resolved.conf, which will later be renamed accordingly based on the DISTRO_FEATURES variable. This file contains the necessary changes which were applied by the patch before. (From OE-Core rev: f3f68874f0edd16c4a85df76e34cc905c41d47f0) Signed-off-by: Hiago De Franco Suggested-by: Alexander Kanavin Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

base-files: Make PATH retain the existing value

2025-04-24T10:47:23+00:00

We may set the PATH variable such as in /etc/environment for ssh session, so make PATH retain the previous existing value to fix the gap. (From OE-Core rev: 4340cd7da25c69424915f29c2bb9531fc33617e6) Signed-off-by: Mingli Yu Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

base-files: add gshadow entry in nsswitch.conf

2025-04-08T14:49:17+00:00

We encountered a newgrp regression in shadow 4.17.3: root@qemux86-64:~# groupadd g1 root@qemux86-64:~# useradd t1 root@qemux86-64:~# gpasswd g1 Changing the password for group g1 New Password: Re-enter new password: root@qemux86-64:~# sudo -u t1 newgrp g1 Password: Invalid password. root@qemux86-64:~# In versions prior to shadow 4.17.3, shadow used an internal implementation to support shadow group because it could not correctly detect whether glibc supports shadow group in a cross-compilation environment. In 4.17.3, it can correctly check whether glibc supports shadow group even in a cross-compilation environment[1]. If supported, shadow will use it instead of its own internal implementation. Shadow group support in glibc requires adding a gshadow entry in nsswitch.conf. After the patch: root@qemux86-64:~# groupadd g1 root@qemux86-64:~# useradd t1 root@qemux86-64:~# gpasswd g1 Changing the password for group g1 New Password: Re-enter new password: root@qemux86-64:~# sudo -u t1 newgrp g1 Password: t1@qemux86-64:/home/root$ [1] https://github.com/shadow-maint/shadow/commit/da6b9cff02d583ef169a0bc0c1014b19b5fad2fb (From OE-Core rev: 0cb122f17cf264ef904880351db1c0bb325fe5a6) Signed-off-by: Yi Zhao Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

base-files: Drop /bin/sh dependency

2025-01-27T15:47:09+00:00

Remove /bin/sh from bash RPROVIDES as this has a side-effect which confuses rpm package manager when also busybox provides /bin/sh and base-files depend on /bin/sh . The problem is broken down below. First, bash depends on base-files and bash pkg_postinst must run after base-files was installed, because it requires /etc/shells provided by base-files to be in place. Second, base-files depends on /bin/sh, which is provided by either bash or busybox in this case. This is the actual problem here, if bash is selected as /bin/sh provider, then there is cyclic dependency between bash and base-files, and that confuses dnf which may install the packages in the wrong order, bash first and base-files second . To make this worse, if busybox is also /bin/sh provider, it can and does happen that some systems pick busybox as the /bin/sh provider, while others pick bash as the /bin/sh provider, and that cyclic dependency does not always appear. Attempt to break this dependency, remove pre-inst script from the base-files recipe, which removes its dependency on /bin/sh and allows it to be installed very early, and always before bash. (From OE-Core rev: e71b64a9b22c7db316e92e78a4bce8b9f994a4ae) Signed-off-by: Marek Vasut Signed-off-by: Richard Purdie

bitbake.conf: drop VOLATILE_TMP_DIR, use FILESYSTEM_PERMS_TABLES instead

2024-08-28T08:14:26+00:00

* Drop VOLATILE_TMP_DIR, use FILESYSTEM_PERMS_TABLES instead. By default, FILESYSTEM_PERMS_TABLES ?= "files/fs-perms.txt \ files/fs-perms-volatile-log.txt \ files/fs-perms-volatile-tmp.txt" it contains 'files/fs-perms-volatile-tmp.txt', which means volatile tmp is enabled. User can disable volatile tmp by remove 'files/fs-perms-volatile-tmp.txt' from FILESYSTEM_PERMS_TABLES. * If volatile tmp is disabled, both /tmp and /var/tmp are persistent (From OE-Core rev: 8d1ae67b89c45f78162e070228086c7ef88c3264) Signed-off-by: Changqing Li Signed-off-by: Richard Purdie

bitbake.conf: drop VOLATILE_LOG_DIR, use FILESYSTEM_PERMS_TABLES instead

2024-08-28T08:14:26+00:00

Drop VOLATILE_LOG_DIR, use FILESYSTEM_PERMS_TABLES instead. By default, it contains 'files/fs-perms-volatile-log.txt', which means volatile log is enabled. User can disable volatile log by remove 'files/fs-perms-volatile-log.txt' from FILESYSTEM_PERMS_TABLES. (From OE-Core rev: 91128c6517066715f2afe6b46aa3206c7cf3653e) Signed-off-by: Changqing Li Signed-off-by: Richard Purdie

base-files: profile: fix error sh: 1: unknown operand

2024-05-22T09:21:26+00:00

Handle errors when SHLVL isn't set. (From OE-Core rev: 5df53fcfe3b70a5312fced3fcc1ba6290f2ee794) Signed-off-by: Felix Nilsson Signed-off-by: Richard Purdie

recipes: Switch away from S = WORKDIR

2024-05-21T11:08:04+00:00

Where recipes use S = ${WORKDIR}, change them to set UNPACKDIR to a subdir of WORKDIR and make S point at this instead. I've chosen not to force S into any standard UNPACKDIR we may pick in future just so the S = UNPACKDIR case is clearly visible by the directory naming under WORKDIR as that should aid usability. (From OE-Core rev: d9328e3b0b062f0621de3d114584b44f384a1c02) Signed-off-by: Richard Purdie