Persistent P3M metadata / binary mismatch on macOS

Dear P3M team,

I'd like to report what appears to be a persistent metadata/binary consistency issue on Posit Public Package Manager (P3M) affecting litedown on macOS.

Summary

  • The litedown 0.9 macOS binary is present on P3M.
  • However, P3M repository metadata still reports version 0.8.
  • As a result, pak resolves litedown (== 0.8) and fails during download, since the corresponding macOS binary is no longer available either from P3M or CRAN.
  • This breaks CI for downstream packages on macOS runners.

I initially assumed this was a transient sync lag, but the issue has persisted for 36+ hours, which suggests a deeper metadata sync problem rather than a temporary delay.

This GitHub issue has a minimal reproducible example, full logs, and discussion: Persistent P3M metadata/binary mismatch for litedown 0.9 on macOS ยท Issue #112 ยท yihui/litedown ยท GitHub

Happy to help validate a fix. Thanks for taking a look.

1 Like