Bug 1763313 - perfl-utf8-all not available in EPEL8
Summary: perfl-utf8-all not available in EPEL8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-utf8-all
Version: epel8
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Paul Howarth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1762233
TreeView+ depends on / blocked
 
Reported: 2019-10-18 18:16 UTC by abrandel
Modified: 2020-01-02 21:55 UTC (History)
5 users (show)

Fixed In Version: perl-utf8-all-0.024-7.el8
Clone Of:
Environment:
Last Closed: 2019-11-02 04:08:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description abrandel 2019-10-18 18:16:26 UTC
Doesn't look like there is a build of this package in EPEL8 testing or release yet. This is a dependency of the nagios-plugins-all package in EPEL, so right now nagios-plugins-all package throws the following:

 Problem: package nagios-plugins-all-2.2.2-2.20190926git1b8ad57.el8.x86_64 requires nagios-plugins-disk_smb, but none of the providers can be installed
  - conflicting requests
  - nothing provides perl(utf8::all) needed by nagios-plugins-disk_smb-2.2.2-2.20190926git1b8ad57.el8.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

I think this is a pretty commonly used package still, even given all the new monitoring system options out there.

Comment 1 Fedora Update System 2019-10-25 08:45:41 UTC
FEDORA-EPEL-2019-ce9e47baa6 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-ce9e47baa6

Comment 2 Fedora Update System 2019-11-02 04:08:33 UTC
perl-utf8-all-0.024-7.el8 has been pushed to the Fedora EPEL 8 stable repository. If problems still persist, please make note of it in this bug report.

Comment 3 Trunet 2019-12-05 12:03:22 UTC
I'm still having problems:

# yum install perl-utf8-all
Last metadata expiration check: 0:00:15 ago on Thu Dec  5 11:59:29 2019.
Error:
 Problem: conflicting requests
  - nothing provides perl(Import::Into) needed by perl-utf8-all-0.024-7.el8.noarch
  - nothing provides perl(PerlIO::utf8_strict) needed by perl-utf8-all-0.024-7.el8.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Comment 4 Petr Pisar 2019-12-05 13:17:16 UTC
You need to enable CodeReady Build / PowerTools repository <https://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F>.

Comment 5 Alexander Kohr 2019-12-30 14:53:29 UTC

(In reply to Petr Pisar from comment #4)
> You need to enable CodeReady Build / PowerTools repository
> <https://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F>.

For those Running Red Hat 8. 
As of 12/30/2019,  The referenced link has this documented in two places. 
As written on 12/30/2019, The first quickstart section instructions should only enable the needed "Red Hat CodeReady Linux Builder for RHEL 8 x86_64 (RPMs)." However the instructions under "How can I use these extra packages" section is written such that you enable, the normal Red Hat CodeReady Linux Builder for RHEL 8 ... repository plus the debug, and sources  versions of it. However The debug and sources repositories do not appear to need to be enabled to install nagios-plugins-disk_smb-2.2.2-2.20190926git1b8ad57.el8.x86_64, as I was able to install nagios-plugins-all and the required perl-utf8-all packages by only enabling the normal codeready-builder-for-rhel-8-x86_64-rpms repo on my box.

Comment 6 Petr Pisar 2020-01-02 13:55:10 UTC
Thank you for the notice. I corrected the "How can I use these extra packages" section.

Comment 7 Alexander Kohr 2020-01-02 21:55:04 UTC
(In reply to Petr Pisar from comment #6)
> Thank you for the notice. I corrected the "How can I use these extra
> packages" section

Now in the first section you have people set a variable of ARCH, In the second example you just use $(arch) in the command. Both should work but it seems one is a bit simpler. Anyway that you for making the previous update. 
  
-Alex


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