Skip to content

Commit bb76bcb

Browse files
committed
queue: liteparse in-review (#2333)
1 parent 1c4e70c commit bb76bcb

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

‎.queue.yml‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5944,9 +5944,9 @@ packages:
59445944
version: 2.14.2
59455945
home: https://github.com/run-llama/liteparse
59465946
repo: https://github.com/run-llama/liteparse
5947-
status: queued
5948-
pr: null
5949-
notes: '3 Linux wheels upstream (abi: cp310); no riscv64 on PyPI or pypi.riseproject.dev.'
5947+
status: in-review
5948+
pr: 2333
5949+
notes: 'PyO3/maturin abi3-py310 extension (cp310-abi3 wheels, not a single cp310 build) with tesseract 5.3.4/leptonica 1.84.1 built from source and statically linked by tesseract-rs, plus a dlopen()ed libpdfium.so bundled in the wheel. That libpdfium comes from run-llama/pdfium-binaries (a PDFium fork adding FPDFText_GetCharInfoBatch, FPDFFont_GetType etc. that the extension hard-requires, so pypdfium2''s riscv64 libpdfium cannot substitute), which ships no linux-riscv64 asset. Workflow reruns the fork''s own build.yml steps at the tag liteparse pins (chromium/8028, read from crates/pdfium-sys/build.rs) with PDFium_TARGET_CPU=riscv64, cross-compiled on ubuntu-24.04 x64 like the fork''s linux-arm64 asset (Chromium clang ships riscv64-unknown-linux-gnu runtimes; debian_trixie_riscv64 sysroot is glibc-reversioned to 2.33), and stages it at vendor/pdfium/release where pdfium-sys build.rs picks it up; the wheel is then built natively with upstream''s maturin-action job and tested with upstream''s test-wheels steps. Licences for PDFium + its third-party notices, tesseract and leptonica are staged next to pyproject.toml (maturin auto-glob). Latest on PyPI is 2.14.7. PR #2333 opened; CI running.'
59505950
- pkg: shfmt-py
59515951
version: 4.1.0
59525952
home: https://github.com/MaxWinterstein/shfmt-py

0 commit comments

Comments
 (0)