Thorsten Schwander

I think this is due to git-lfs resolving/not resolving large file references in the repos being downloaded When I set `export GIT_LFS_SKIP_SMUDGE=1` the build succeeds and the checked out zip...

so I wonder if golang or k9s could avoid lfs dereferencing by default to avoid this kind of confusion ?

I use ``` $ go version go version go1.21.7 linux/amd64 ``` Anyhow, avoiding git-lfs dereferencing of files via `export GIT_LFS_SKIP_SMUDGE=1` is the workaround.

@michamos any comment on this? seems ok, if inefficient, to me

/opt/cds-invenio/var/log/bibsched/116/bibsched_task_1161260.log changed 4805 records to `physics.acc-ph` /opt/cds-invenio/var/log/bibsched/116/bibsched_task_1161266.log changed 377 records to `physics.atom-ph` /opt/cds-invenio/var/log/bibsched/116/bibsched_task_1161268.log changed 120 records to `nlin.CD` /opt/cds-invenio/var/log/bibsched/116/bibsched_task_1161269.log changed 307 records to `physics.med-ph` /opt/cds-invenio/var/log/bibsched/116/bibsched_task_1161273.log changed 73 records to `physics.ao-ph`...

the commit message is not very informative `Bibcheck: added regexp_replace rules to rules.cfg` better would be: `BibCheck: rules to normalize HepNames subjects` for display in short log. Also, subtitles or...

very good comments @michamos thanks

right, I agree that schema_utils shouldn't deal with encoding issues -- which means there will be some sanitizing of random input in the crawler. It's not like the remote end...

@michamos as per standup discussion

fine with me if it ever comes to that, by it didn't sound like "report" was considered equivalent to "techreport". so this patch simply ensures that the code is clear...