Update perl-LWP-Protocol-https to version 6.14-1

[kevin-b-lockwood]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

What does the PR accomplish, why was it needed?

Build/Dependency Information

Please build the following packages with perl-LWP-Protocol-https:
perl-Mozilla-CA

Change Log

• Version bump
• License verified.
• Drop LWP-Protocol-https-6.06-Debian-746576-don-t-disale-verification-if-only-host.patch
• Drop LWP-Protocol-https-6.06-Debian-746576-fix-test-make-it-workable-for-Crypt-SS.patch

Both patches were merged into master here:
libwww-perl/LWP-Protocol-https#14

Does this affect the toolchain?

NO

Test Methodology

• Local build.

[0xba1a]

Buddy Build failed with Unresolved Dependency

INFO[0001][scheduler] Blocked SRPMs:                               
INFO[0001][scheduler] --> perl-LWP-Protocol-https-6.14-1.azl3.src.rpm 
INFO[0001][scheduler] Blocked SRPMs tests:                         
INFO[0001][scheduler] --> perl-LWP-Protocol-https-6.14-1.azl3.src.rpm 
INFO[0001][scheduler] ---------------------------                  
INFO[0001][scheduler] --------- Summary ---------                  
INFO[0001][scheduler] ---------------------------                  
INFO[0001][scheduler] Number of prebuilt SRPMs:              0     
INFO[0001][scheduler] Number of prebuilt delta SRPMs:        0     
INFO[0001][scheduler] Number of skipped SRPMs tests:         0     
INFO[0001][scheduler] Number of built SRPMs:                 0     
INFO[0001][scheduler] Number of passed SRPMs tests:          0     
ERRO[0001][scheduler] Number of unresolved dependencies:     1     
ERRO[0001][scheduler] Number of blocked SRPMs:               1     
ERRO[0001][scheduler] Number of blocked SRPMs tests:         1     
INFO[0001][scheduler] Number of failed SRPMs:                0     
INFO[0001][scheduler] Number of failed SRPMs tests:          0     
INFO[0001][scheduler] Number of SRPMs with license errors:   0     
INFO[0001][scheduler] Number of SRPMs with license warnings: 0     
INFO[0001][scheduler] Number of toolchain RPM conflicts:     0     
INFO[0001][scheduler] Number of toolchain SRPM conflicts:    0     

[kevin-b-lockwood]

@0xba1a

Buddy Build failed with Unresolved Dependency

How do I resolve this issue? When I build the package in my local build and tell it to also build perl-Mozilla-CA at the same time, the build succeeds. Is there some way of indicating this beyond just putting it as a BuildRequires:?

[suresh-thelkar]

Code changes look good to me. Install/uninstall tests from the buddy build are failing. Can you please take a look.
If you have already verified them in an Azure Linux 3.0 container, please share the screenshot for the same.

[kevin-b-lockwood]

Code changes look good to me. Install/uninstall tests from the buddy build are failing. Can you please take a look. If you have already verified them in an Azure Linux 3.0 container, please share the screenshot for the same.

I was able to build this successfully

[kevin-b-lockwood]

@suresh-thelkar Is this what you were asking for? What do I need to get this PR moving again?