boryeumao

Tried poking around but hadn't found anything that may allow volumes from a second vg to go into the archive - Has this been implemented (in 0.3.1 20220804)? (A related...

@tasket Thanks. I will check out "--meta-dir", now that I understand what it is (should've checked the code more closely), and also v4 alpha. If you could comment on the...

@tasket Ah Yes precisely I wanted to be aware of anything to watch out for with mixing tpools. Thanks for clarifying.

@marmarek - For me, switching default-mgmt-dvm to fedora-39 template did not fix the 'ModuleNotFoundError' for 'backports'. Also, neither workaround suggested by @vladimir-lu worked for me. Curiously, using the Qubes OS...

For reference: attached are two files logging the errors from running salt update on fedora-39-minimal template, one with default-mgmt-dvm based on debian-12-minimal as template and the other based on fedora-39....

It was fedora-39 (fully updated).  Yes I did see that urllib3 module is in the python3 site-packages directory (and could be imported successfully in a dummy python session), so the...

@qtc-de Confirmed (`salt` update is successful after installing `python-urllib3` in `fedora-39-minimal`, when `default-mgmt-dvm` runs on `fedora-39` template). This clues me on why I wasn't able to get the `backports.ssl_match_hostname` workaround...

The second `workaround` mentioned in @vladimir-lu was to patch `salt` (specifically in this case `salt/ext/tornado/netutil.py`, to call `urllib3` instead of `backports`). The advantage is that `qubesctl` won't need to "know"...

For additional information on the garbled text on dispvm console: the same string also appears in a Debian-13 based VM under Qubes OS 4.2.4.