TW
It expects `/run/user/1000/pytest` directory to either exist or be creatable (so that files, like that socket, can be created in that directory). That directory is the "user runtime directory" returned...
@maricn The tests assume that the to-be-tested borg is installed. Usually `tox` creates a virtual env and installs borg into that and then runs the tests within that venv.
Issues: - no `ubuntu/noble64` box yet on vagrant cloud, see https://app.vagrantup.com/ubuntu - some other ubuntu 24.04 box had crashes with `virtualenv myenv` - it seemed to miss some pip wheel...
@LocutusOfBorg I'ld like to test borg on 24.04, but they still don't provide a vagrant box for that. Did they forget about that? Also, someone should fill out that profile,...
Looks like `bento` has a box, will test: https://portal.cloud.hashicorp.com/vagrant/discover/bento/ubuntu-24.04
@supercoder-dev Did you see my feedback?
About "pkg-config missing": `pkg-config` is the cli tool that is used internally by the python library `pkgconfig`. So we would need to check a requirement of a requirement... - maybe...
@infectormp no, that's something different (FAQ is about unexpected "M" status for the most recent file, but this is about "changed while we backed it up that single file"). @bojan-future...
The root cause is different in the FAQ item: there, the root cause is that borg intentionally deletes the freshest file from the files cache, so it will show "A"...