Bug 1729976

Summary: Add perl-LWP-Protocol-connect to EPEL-7
Product: [Fedora] Fedora Reporter: Clément OUDOT <clem.oudot>
Component: perl-LWP-Protocol-connectAssignee: Petr Pisar <ppisar>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: extras-orphan, paul, perl-devel, ppisar, Sven.Nierlein
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: perl-LWP-Protocol-connect-6.09-26.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-05 15:23:24 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:

Description Clément OUDOT 2019-07-15 13:10:53 UTC
Description of problem:

Some HTTP proxies require to use the CONNECT method. This is possible with Perl using LWP-Protocol-connect, but this module is not packaged in EPEL.

Would it be possible to do it?

Comment 1 Petr Pisar 2019-07-15 13:40:12 UTC
This package is maintained by "sni" in Fedora. Maybe the Fedora maintainer could take care about this package in EPEL.

It looks like this package does not have any missing build and run time dependencies and adding it to EPEL is trivial.

Comment 2 Sven Nierlein 2019-07-15 13:45:28 UTC
i will have a look.

Comment 3 Ben Cotton 2019-08-13 16:53:39 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 4 Ben Cotton 2019-08-13 19:02:23 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 5 Fedora Admin XMLRPC Client 2020-01-09 16:18:25 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 6 Fedora Admin XMLRPC Client 2020-01-10 04:07:49 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 7 Fedora Admin XMLRPC Client 2020-01-10 16:16:59 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 8 Fedora Admin XMLRPC Client 2020-01-11 04:04:21 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 9 Fedora Admin XMLRPC Client 2020-01-11 16:13:50 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 10 Fedora Admin XMLRPC Client 2020-01-12 04:06:52 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 11 Fedora Admin XMLRPC Client 2020-01-12 16:12:05 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 12 Fedora Admin XMLRPC Client 2020-01-13 04:07:10 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 13 Fedora Admin user for bugzilla script actions 2023-04-26 00:24:35 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 15 Fedora Update System 2023-04-27 14:46:24 UTC
FEDORA-EPEL-2023-3df600316e has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-3df600316e

Comment 16 Fedora Update System 2023-04-28 03:56:48 UTC
FEDORA-EPEL-2023-3df600316e 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-2023-3df600316e

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

Comment 17 Fedora Update System 2023-05-05 15:23:24 UTC
FEDORA-EPEL-2023-3df600316e has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.