According to the SWHID specification, it is not forbidden for a qualifier
value to contain a '=' character (for instance in origin URL).
So update parsing code to handle that special case.
Differential D5487
identifiers: Fix parsing of SWHID qualifier value containing '=' anlambert on Apr 12 2021, 5:48 PM. Authored by
Details
According to the SWHID specification, it is not forbidden for a qualifier So update parsing code to handle that special case.
Diff Detail
Event Timeline
Comment Actions Build is green Patch application report for D5487 (id=19621)Rebasing onto f2dba177ad... First, rewinding head to replay your work on top of it... Applying: identifiers: Fix parsing of SWHID qualifier value containing '=' Changes applied before testcommit 7ec3890a8466d1f25d89a8f575a9f76e19e2eb3c Author: Antoine Lambert <antoine.lambert@inria.fr> Date: Mon Apr 12 17:44:20 2021 +0200 identifiers: Fix parsing of SWHID qualifier value containing '=' According to the SWHID specification, it is not forbidden for a qualifier value to contain a '=' character (for instance in origin URL). So update parsing code to handle that special case. See https://jenkins.softwareheritage.org/job/DMOD/job/tests-on-diff/311/ for more details.
Comment Actions Build is green Patch application report for D5487 (id=19622)Rebasing onto f2dba177ad... First, rewinding head to replay your work on top of it... Applying: identifiers: Fix parsing of SWHID qualifier value containing '=' Changes applied before testcommit cc5e73ab507bc7d287304787dcf3eef8c9317fad Author: Antoine Lambert <antoine.lambert@inria.fr> Date: Mon Apr 12 17:44:20 2021 +0200 identifiers: Fix parsing of SWHID qualifier value containing '=' According to the SWHID specification, it is not forbidden for a qualifier value to contain a '=' character (for instance in origin URL). So update parsing code to handle that special case. See https://jenkins.softwareheritage.org/job/DMOD/job/tests-on-diff/312/ for more details. Comment Actions Build is green Patch application report for D5487 (id=19623)Rebasing onto f2dba177ad... First, rewinding head to replay your work on top of it... Applying: identifiers: Fix parsing of SWHID qualifier value containing '=' Changes applied before testcommit 2b824e68b3605df89d5e6fff63470c813c1b9ba7 Author: Antoine Lambert <antoine.lambert@inria.fr> Date: Mon Apr 12 17:44:20 2021 +0200 identifiers: Fix parsing of SWHID qualifier value containing '=' According to the SWHID specification, it is not forbidden for a qualifier value to contain a '=' character (for instance in origin URL). So update parsing code to handle that special case. See https://jenkins.softwareheritage.org/job/DMOD/job/tests-on-diff/313/ for more details. Comment Actions In the webapp, origin URL with a = character in it also got percent encoded to avoid generating invalid browse URL: https://archive.softwareheritage.org/browse/origin/directory/?origin_url=https://cran.r-project.org/package%3Dtelegram.bot. I am wondering if we should not also force to percent encode = in qualifier value as we do for ;; Comment Actions Too late for that; we can't know if there are SWHIDs in the wild with unescaped equal signs in them. Comment Actions Ack, good news is that diff will fix SWHID resolution in the webapp when the = character in an origin URL is not percent encoded (currently it fails as expected). Comment Actions Build is green Patch application report for D5487 (id=19638)Rebasing onto 15d5bab512... Current branch diff-target is up to date. Changes applied before testcommit 74b024f5e0b862e8cff12c62406d06b22d258c84 Author: Antoine Lambert <antoine.lambert@inria.fr> Date: Mon Apr 12 17:44:20 2021 +0200 identifiers: Fix parsing of SWHID qualifier value containing '=' According to the SWHID specification, it is not forbidden for a qualifier value to contain a '=' character (for instance in origin URL). So update parsing code to handle that special case. See https://jenkins.softwareheritage.org/job/DMOD/job/tests-on-diff/315/ for more details. |