Marcin Cieślak

I think the answer to this one is that `pkg_jobs_add` [never gets called for a no-arg upgrade](https://github.com/freebsd/pkg/blob/14e1291b59bd6c024d7c7d04e43b35f16c2f1411/src/upgrade.c#L374) (I have verified this by adding a simple diagnostic emit and it does...

Seems to me that this is caused by the `#!/bin/bash` line in https://github.com/bonfire-networks/ember/blob/a4556d5a366c7f3621f5187e1c3f14d16ff9aadc/install.sh#L1 - it will not work on the systems where bash is installed somewhere else. Any special requirements...

rough plain sh version of ember [install.sh](https://github.com/bonfire-networks/ember/blob/013bb3634b0eb1d99da54a395e9e80c0b6f44e50/install.sh), no need for `functions.sh` ```sh #!/bin/sh src_root=`dirname "$0"` exec 3&2 'Overwrite existing file (y/N)?' read -r response &2 "${destfile}: will keep" break esac...

Will try again once I will come back to try bonfire...

Why this might have gone unnoticed: - Full installation with pip works in a virtual environment that only has python3.11 available. - CI and pre-commit seems to use python 3.13...

No, just a simple send and wait... but your theory from #1134 looks very plausible to me. May be in our case this is not a coordinator... At some point...