Change Details

(Please edit this task with SWHIDv1 issues) * The way we format manifests for revisions/releases with negative non-integer timestamps is broken, because "200000 microseconds before timestamp 0" (aka 0 minus 1 seconds plus 800000 microseconds) is represented as "-1.8" in their git-like manifest. [[ https://forge.softwareheritage.org/D6325#inline-45442 | Discussed here ]] * No way to represent missing DAG nodes (discussion at T1957)

(Please edit this task with SWHIDv1 issues) * The way we format manifests for revisions/releases with negative non-integer timestamps is broken, because "200000 microseconds before timestamp 0" (aka 0 minus 1 seconds plus 800000 microseconds) is represented as "-1.8" in their git-like manifest. [[ https://forge.softwareheritage.org/D6325#inline-45442 | Discussed here ]] * No way to represent missing DAG nodes (discussion at T1957) * The same "abstract" object (especially directories) can have many Git representations, therefore multiple Git identifiers, making its SWHIDv1 non-unique (even if one is "more canonical" than others)

(Please edit this task with SWHIDv1 issues) * The way we format manifests for revisions/releases with negative non-integer timestamps is broken, because "200000 microseconds before timestamp 0" (aka 0 minus 1 seconds plus 800000 microseconds) is represented as "-1.8" in their git-like manifest. [[ https://forge.softwareheritage.org/D6325#inline-45442 | Discussed here ]] * No way to represent missing DAG nodes (discussion at T1957) * The same "abstract" object (especially directories) can have many Git representations, therefore multiple Git identifiers, making its SWHIDv1 non-unique (even if one is "more canonical" than others)