Bug 1426956 - typo in pcp-selinux postinstallscript
Summary: typo in pcp-selinux postinstallscript
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pcp
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lukas Berk
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-26 19:55 UTC by David Juran
Modified: 2017-04-11 04:51 UTC (History)
7 users (show)

Fixed In Version: pcp-3.11.8-2.fc25 pcp-3.11.9-1.fc24
Clone Of:
Environment:
Last Closed: 2017-04-11 04:51:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description David Juran 2017-02-26 19:55:12 UTC
Description of problem:

There's a typo in the pcp-selinux postinstall script:

  Installing  : pcp-selinux-3.11.8-1.fc25.x86_64                                                                                                                                                          538/1497 
libsemanage.map_file: Unable to open %{localstatedir}/lib/pcp/selinux/pcpupstream.pp
 (No such file or directory).
libsemanage.semanage_direct_install_file: Unable to read file %{localstatedir}/lib/pcp/selinux/pcpupstream.pp
 (No such file or directory).
semodule:  Failed on %{localstatedir}/lib/pcp/selinux/pcpupstream.pp!
warning: %post(pcp-selinux-3.11.8-1.fc25.x86_64) scriptlet failed, exit status 1
Non-fatal POSTIN scriptlet failure in rpm package pcp-selinux
Non-fatal POSTIN scriptlet failure in rpm package pcp-selinux




[david@localhost ~]$ rpm -q --scripts pcp-selinux
postinstall scriptlet (using /bin/sh):
    semodule -X 400 -i %{localstatedir}/lib/pcp/selinux/pcpupstream.pp


Do note the macro has not expanded...

Version-Release number of selected component (if applicable):
pcp-selinux-3.11.8-1.fc25.x86_64

Comment 1 Fedora Update System 2017-02-27 18:19:51 UTC
pcp-3.11.8-2.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-1975774439

Comment 2 Fedora Update System 2017-02-27 18:25:26 UTC
pcp-3.11.8-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-3b25af744f

Comment 3 Fedora Update System 2017-03-01 02:50:51 UTC
pcp-3.11.8-2.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-3b25af744f

Comment 4 Fedora Update System 2017-03-01 02:53:42 UTC
pcp-3.11.8-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-1975774439

Comment 5 Fedora Update System 2017-03-02 01:21:49 UTC
pcp-3.11.8-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

Comment 6 Fedora Update System 2017-04-02 05:17:01 UTC
pcp-3.11.9-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-c6c3616693

Comment 7 Fedora Update System 2017-04-03 02:22:26 UTC
pcp-3.11.9-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-c6c3616693

Comment 8 Fedora Update System 2017-04-11 04:51:25 UTC
pcp-3.11.9-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.


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