Bug 1288216 - community-mysql: tmpfiles config incorrectly named
community-mysql: tmpfiles config incorrectly named
Product: Fedora
Classification: Fedora
Component: community-mysql (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jakub Dorňák
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-12-03 16:22 EST by Carl George
Modified: 2016-07-19 14:33 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-19 14:33:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
change tmpfiles configuration file name to match service unit file (1.02 KB, patch)
2015-12-03 16:22 EST, Carl George
no flags Details | Diff

  None (edit)
Description Carl George 2015-12-03 16:22:59 EST
Created attachment 1101975 [details]
change tmpfiles configuration file name to match service unit file

Description of problem:

systemd service unit files and tmpfiles configuration files should use matching names.  For example, the mariadb-server packages use the name "mariadb" for both.


In the community-mysql-server package, they do not match.


Additionally, the rawhide community-mysql-server package has another tmpfiles configuration file that doesn't match either name.


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


Suggested fix:

Patch for community-mysql.spec is attached.
Comment 2 Fedora End Of Life 2016-07-19 14:33:53 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.