Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1618784 - nut-monitor.service references non-existant /etc/tmpfiles.d/nut-run.conf
Summary: nut-monitor.service references non-existant /etc/tmpfiles.d/nut-run.conf
Keywords:
Status: ON_QA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: nut
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michal Hlavinka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-17 15:05 UTC by Orion Poplawski
Modified: 2020-06-03 03:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Orion Poplawski 2018-08-17 15:05:38 UTC
Description of problem:

systemd-tmpfiles[1631]: Failed to open '/etc/tmpfiles.d/nut-run.conf', ignoring: No such file or directory

Version-Release number of selected component (if applicable):
nut-client-2.7.2-4.el7.x86_64

Looks like this has been fixed in the Fedora package.  Can we have an EPEL7 update please?

Comment 1 Fedora Update System 2020-06-02 17:44:26 UTC
FEDORA-EPEL-2020-f76f9220f4 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-f76f9220f4

Comment 2 Fedora Update System 2020-06-03 03:40:40 UTC
FEDORA-EPEL-2020-f76f9220f4 has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-f76f9220f4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.


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