Heya folks! This sync brings an updated and reworked PAM stack, as well as a change to the jack audio server package.
Jack server users will now need to install the jack-audio-connection-kit-server
package to run the full server.
@ReillyBrogan has updated our PAM stack, a critical set of packages which helps with authentication. There are a few things to be aware of when updating:
- If you have any custom PAM configuration in
/etc/pam.d
, they will likely need to be modified.
/etc/environment
must be in a key=value format, or else Bad Things:tm: will happen! export key=value
(Shell form) is invalid and will result in services failing to start with a critical PAM error.
- Sudo will print the administrator admonition message the first time it is ran after the update.
When eopkg
updates some PAM related packages, you will see messages about file conflicts for the libeconf
, pam
, and shadow
packages. This is normal and expected. For example, here is what those messages look like for libeconf
:
Installing libeconf, version 0.6.0, release 4
Upgrading to new upstream version
Extracting the files of libeconf
Upgraded libeconf
Installing 2 / 33
pam-1.5.3-27-1-x86_64.eopkg [cached]
Installing pam, version 1.5.3, release 27
File conflicts:
/usr/share/defaults/etc/pam.d/other from shadow gets replaced by pam package
/usr/share/defaults/etc/pam.d/system-auth from shadow gets replaced by pam package
This also brings an updated libeconf
, which includes built-in support for hermetic-usr configuration, a concept that Solus calls "stateless" configuration. If you aren't familiar with hermetic /usr/ or Statelessness, it largely boils down to this: All vendor files (files provided by the distribution, i.e. Solus) should live in the /usr/
file tree, including configuration defaults that can then be overridden by files in /etc/
or the user's home directory. This last bit is the tricky part; a lot of software doesn't support this concept, requiring us to patch their source code so that they do. The support introduced in libeconf
will hopefully make this easier because software that uses it for configuration file management will gain this support out of the box.
In case you haven't seen it, we are looking for your input on what your devices support when it comes to BIOS and UEFI. This will help inform us on where and what technologies we should focus on when it comes to the bootloader. Check out this thread by @TraceyC for more information, as well as the poll.
Other updates this sync include: https://pastes.io/y8lr6cvoh9
(There were so many updated packages, the forum won't let me post them all!)
That’s all for this time, folks! Check back next time for another round of sync news!