Hi, that is an interesting find! (And some sad code)
Am Wed, Oct 07, 2026 at 11:47:19PM -0600, schrieb Christian Noé Ramos López: > Two things would avoid it: computing the date with a calendar, or > passing "+1y", which sqv accepts as an offset (--policy-as-of +1y > exits 0 here). The former should be relatively easy (as far as dates are concerned) with what is available via <chrono> in C++20 and above (nowadays). The second option seems (at least for now) to be a usage error itself as the documentation (sqv manpage) for --policy-as-of says | The time is expressed as an ISO 8601 formatted timestamp. And earlier it expressed in general: | The TIMESTAMPs must be given in ISO 8601 format I presume that +1y works stems from --time which says: | Set the reference time as an ISO 8601 formatted timestamp or | relative offset. […] This time is also used as the default | value for --not-after and --policy-as-of […] "relative offset" does not seem defined through. Aside: I /suppose/ "PY1" would be a valid ISO 8601 (duration), but I haven't dared to try how sqv would react. Maybe its just me, but I would prefer the former (even if documentation of sqv is changed) as the wording --policy-as-of highly suggests an exact date for me… even if I realize as of 5 seconds later that this might be a valid way of speaking, too. Best regards David Kalnischkies
signature.asc
Description: PGP signature
