Bug 2369048 (perl-App-cpm-el10)

Summary: Please branch and build perl-App-cpm in epel10
Product: [Fedora] Fedora EPEL Reporter: Peter Oliver <mavit>
Component: perl-App-cpmAssignee: Jitka Plesnikova <jplesnik>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel10CC: carl, jplesnik, perl-devel
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: perl-App-cpm-0.997.023-1.el10_1 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-06-21 02:40:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2372266, 2372267, 2372268, 2372269, 2372270, 2372271, 2372272, 2372274, 2372275    
Bug Blocks:    

Description Peter Oliver 2025-05-28 18:19:04 UTC
Please branch and build perl-App-cpm in epel10.

If you do not wish to maintain perl-App-cpm in epel10,
or do not think you will be able to do this in a timely manner,
I would be happy to be a co-maintainer of the package (FAS mavit);
please add me through https://src.fedoraproject.org/rpms/perl-App-cpm/adduser

Thanks.

Comment 1 Fedora Update System 2025-06-02 05:45:04 UTC
FEDORA-EPEL-2025-991c731b3e (perl-App-cpm-0.997.023-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-991c731b3e

Comment 2 Fedora Update System 2025-06-03 01:34:23 UTC
FEDORA-EPEL-2025-991c731b3e has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-991c731b3e

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

Comment 3 Fedora Update System 2025-06-11 00:30:28 UTC
FEDORA-EPEL-2025-991c731b3e (perl-App-cpm-0.997.023-1.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Carl George 🤠 2025-06-19 22:51:14 UTC
This package has missing dependencies.

Error: 
 Problem: conflicting requests
  - nothing provides perl(Command::Runner) >= 0.100 needed by perl-App-cpm-0.997.023-1.el10_1.noarch from epel
  - nothing provides perl(HTTP::Tinyish) >= 0.12 needed by perl-App-cpm-0.997.023-1.el10_1.noarch from epel
  - nothing provides perl(Menlo::CLI::Compat) >= 1.9021 needed by perl-App-cpm-0.997.023-1.el10_1.noarch from epel
  - nothing provides perl(Module::cpmfile) >= 0.001 needed by perl-App-cpm-0.997.023-1.el10_1.noarch from epel
  - nothing provides perl(Parallel::Pipes::App) >= 0.100 needed by perl-App-cpm-0.997.023-1.el10_1.noarch from epel
  - nothing provides perl(Carton::Snapshot) needed by perl-App-cpm-0.997.023-1.el10_1.noarch from epel
  - nothing provides perl(CPAN::02Packages::Search) needed by perl-App-cpm-0.997.023-1.el10_1.noarch from epel
  - nothing provides perl(Darwin::InitObjC) needed by perl-App-cpm-0.997.023-1.el10_1.noarch from epel
  - nothing provides perl(Menlo::Builder::Static) needed by perl-App-cpm-0.997.023-1.el10_1.noarch from epel
  - nothing provides perl(Proc::ForkSafe) needed by perl-App-cpm-0.997.023-1.el10_1.noarch from epel

I can see that those are available in epel-testing.  In the future, please submit the dependencies first, or in the same update, to avoid exposing users to uninstallable packages.

Comment 5 Fedora Update System 2025-06-19 22:52:44 UTC
FEDORA-EPEL-2025-7cb2ae40d0 (perl-App-FatPacker-0.010008-20.el10_1, perl-Carton-1.0.35-9.el10_1, and 8 more) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7cb2ae40d0

Comment 6 Fedora Update System 2025-06-21 02:40:02 UTC
FEDORA-EPEL-2025-7cb2ae40d0 (perl-App-FatPacker-0.010008-20.el10_1, perl-Carton-1.0.35-9.el10_1, and 8 more) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.