Closed KlfJoat closed 5 months ago
Is it possible to bump this?
Your SPDX tool is outputting non-conformant SPDX files. Seems an important bug to fix.
Found the cause of this bug. Thanks for reporting @KlfJoat
With utcnow()
deprecated, I changed to now(tz=...utc)
in bc49936a107f4b0aff779ab1c998a194b1e30a88, but this is ever subtly different, because utcnow()
didn't create a datetime object with UTC tzinfo, but the latter does. And a datetime object with tzinfo has a different output for isoformat()
.
The time value output by
reuse spdx
is wrong.reuse --version
=reuse 3.0.1
Steps to reproduce
reuse lint
passes as okay.reuse spdx > myfile
myfile
to have the same time value as me:Created: 2024-02-22T01:21:17+00:00Z
myfile
Expected result
A pop-up saying...
Actual result
An error pop-up with the following message...
ISO 8601 conformance
For one, I'm pretty sure that using
+00:00Z
is not allowed in ISO 8601. IIRC either+00:00
(or acceptable variants like+0000
&+00
) is allowed ORZ
is allowed, but not both. So that's one bug for sure.Spec conformance
Per the spec, only
Z
is allowed, not a timeshift offset.