PURLs containing multiple namespaces segments parse incorrectly #5
Labels
bug
Something isn't working
Comments
giterlizzi
added a commit
that referenced
this issue
Nov 9, 2023
- Improved validation during encode and decode "purl" string - Fixed CPAN repository URL - FIX Qualifiers are case sensitive (#4) - FIX PURLs containing multiple namespaces segments parse incorrectly (#5) - FIX Incorrect parsing of PURLs that begin with "pkg:/" (#6) - Improved "t/99-official-purl-test-suite.t" test
|
FIXED in last release of URI::PackageURL $ purl-tool pkg:swift/github.com/Alamofire/Alamofire@5.4.3 --env
PURL="pkg:swift/github.com/Alamofire/Alamofire@5.4.3"
PURL_TYPE="swift"
PURL_NAMESPACE="github.com/Alamofire"
PURL_NAME="Alamofire"
PURL_VERSION="5.4.3"
PURL_SUBPATH=""
PURL_QUALIFIERS=""Thanks ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The PURL test suite contains the PURL
pkg:swift/github.com/Alamofire/Alamofire@5.4.3. perl-URI-PackageURL parses it as namespacegithub.comnameAlamofire/Alamofirebut it should be namespacegithub.com/AlamofirenameAlamofire.It also serializes incorrectly. The slash in the package name is not escaped, so serializing the incorrectly parsed PURL results in the original string again, even though it was constructed from a PURL structure that should have a different meaning.
The text was updated successfully, but these errors were encountered: