You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the code of ltclass, all packages share the same macro \pkgcls@innerdate which is used by \IfTargetDateBefore. This may cause problems if there is a \RequirePackage with different rollback date before \IfTargetDateBefore.
The first \IfTargetDateBefore types out new but the second \IfTargetDateBefore types out old.
(demo.sty
Rollback for package 'demo' requested -> date 2022-02-02.
Best approximation is the release introduced on 2022-02-02.
Include code introduced on 2022-01-01
new
(pkg.sty
Rollback for package 'pkg' requested -> date 2021-12-12.
Best approximation is the release introduced on 2021-12-12.
)
Exclude code introduced on 2022-01-01
old
)
The text was updated successfully, but these errors were encountered:
I looked at this last night and I'm inclined to document this as a limitation of \IfTargetDateBefore, i.e., that you can't use it if your code is explicitly asking for a dated release of some other package. Otherwise one would maintain the information in a stack which seems overkill to me.
Brief outline of the bug
In the code of
ltclass
, all packages share the same macro\pkgcls@innerdate
which is used by\IfTargetDateBefore
. This may cause problems if there is a\RequirePackage
with different rollback date before\IfTargetDateBefore
.Minimal example showing the bug
Log file (required) and possibly PDF file
The first
\IfTargetDateBefore
types outnew
but the second\IfTargetDateBefore
types outold
.The text was updated successfully, but these errors were encountered: