Description of problem:

The following change removed the tmpfiles.d configuration that created the directory in /var/run where mariadb keeps its pid file:

https://src.fedoraproject.org/rpms/mariadb10.11/c/9f34c645431d3d3308369071e4a7948d1979032f?branch=f42

The comment on that commit indicates that rpm can create and own that directory, but /var/run is a tmpfs, so nothing that rpm owns will survive a reboot.

/usr/lib/tmpfiles.d is owned by the "filesystem" rpm, so it should be fine to include the tmpfiles configuration, even if the package is intended for use in containers. It simply won't have any effect in a container deployment.

Version-Release number of selected component (if applicable):

mariadb.x86_64 3:10.11.15-1.fc42

How reproducible:

Always.

Steps to Reproduce:
1. Install Fedora 42 with mariadb.x86_64 3:10.11.11-1.fc42
2. Set up a default configuration
3. Upgrade to mariadb.x86_64 3:10.11.15-1.fc42
4. Try to start mariadb

Actual results:

 2026-01-15 11:50:36 0 [ERROR] mariadbd: Can't create/write to file '/run/mariadb/mariadb.pid' (Errcode: 13 "Permission denied") 

Expected results:

mariadb should start

Additional info: