Robert Sachunsky

> So ocrd_network complains that it cannot import `MpxReq` from `ocrd.mets_server`. @MehmedGIT do you know what's going on? Ouch! I am seeing: ``` #12 41.65 . /usr/local/sub-venv/headless-tf1/bin/activate && sem -q...

So IIUC there are multiple things going on: 1. we neglected publishing our aliased packages ocrd_utils, ocrd_models, ocrd_network etc to PyPI in addition to ocrd (remember we just wanted to...

> Just deleting the `~/.parallel` folder if existing at the beginning of the build? Is there anything wrong by doing that? I am not sure. > Right, it does not...

Ok, we are still failing, but this time ocr-fileformat is the culprit: ``` #12 85.98 Collecting ocrd-utils (from textract2page==0.2.dev12+g3f28e31) #12 86.00 Downloading ocrd_utils-2.64.0-py3-none-any.whl.metadata (8.8 kB) #12 86.20 Collecting ocrd-models (from...

I'll update to [OCR-D/ocrd_fileformat#186](https://github.com/OCR-D/ocrd_fileformat/pull/55). Good news is that with -j4 we reduced build time by another 10min.

Next [CI failure](https://app.circleci.com/pipelines/github/OCR-D/ocrd_all/1095/workflows/ff18a538-3434-469d-ace4-210d2462bfb7/jobs/1506?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-checks-link&utm_content=summary) almost feels great! I think I've seen those already. IINM https://github.com/OCR-D/core/pull/1243 should fix them. But ocrd_all is not the place for this. So from my side, this...

Note: I've cancelled the CircleCI workflow for the latest change, which only affects the GH Actions workflow for the Docker build (in similar fashion). I manually triggered that [here](https://github.com/OCR-D/ocrd_all/actions/runs/9785272430/job/27017963815).

note: 60c7f7a is in preparation of https://github.com/OCR-D/core/pull/1250 (but perhaps we should also do something similar in native installations...)

> > (but perhaps we should also do something similar in native installations...) > > That would be ideal. So perhaps we should embed `ocrd-all-tool.json` and `ocrd-all-module-dir.json` into a recipe...

> But if someone merely updates a single tool _without_ running the ocrd-all-tool.json recipe afterwards, then indeed there will be an inconsistency. We could rewrite our documentation to say that...