Updates For Qubes 4.3

[neoniobium]

Since Qubes 4.3 is stable now, some updates need to be made.

Commands with new subcommands and options:

• Most qvm-XXX and some qubes-XXX commands now have the --version option (version #43)
• qvm-pci, qvm-usb, qvm-block and qvm-device now have the assign and unassign subcommands. (assign #42)
• qvm-ls has new flags (qvm ls #35)
• qvm-pause has new flags (qvm pause #36)
• qubes-global-config has new flags (qubes global config #37)
• qubes-new-qube has new flags (qubes new qube #39)
• qubes-create has new flags (qubes create #38)

New Commands:

• qvm-notes (qvm notes #41)
• qubes-device-agent (qubes device agent #40)

New Commands without help and man entry:

• qubes-notification-proxy-server (Only need to be added in the preamble of the program with a comment --- no PR, can be done in the final cleanup step)

Misc:

• Add new features for qvm-feature (Can be found in manual) ([qvm-features] Features for 4.3 #33)
• Add new fields for qvm-prefs ([qvm-prefs] #34)
• The update tool itself qubes-dist-upgrade could have completion if desired. (Skipped for now since I do not know how stable the interface is between releases. There is certainly utility in having it but it is not part of the 4.3 release. Should be comment in the preamble if not implemented)

Steps to proceed:

• Check version #43 and decide if this approach to implementing --version is the right way to go. Otherwise decline
• Review and merge [qvm-features] Features for 4.3 #33 afterwards refactor with qvm ls #35. qvm-ls now support features hence a the list of all features for the body of function qvm-feature should be a global variable and used in qvm-ls (see option --prefs of qvm-ls)
• All other PRs can be reviewed and merged independently. Note that none implements the --version flag explicitly but will support the flag if version #43 is merged.
• Testing and cleanup. Especially check the --version flag.
• Make the release.

[neoniobium]

@jamke please decide if you would like to collect the updates for Q4.3 in a dedicated branch or directly in the main branch. Since there are release tags, the main branch seams fine to me.

[jamke]

Oh, I do not have R4.3 yet myself.

We can use main branch, as R4.2 is going to be supported for only about 5 next months.

Thanks for your effort.

[neoniobium]

I think I can do most, or all of the implementation this week. I there I anything already done but not pushed yet?

[jamke]

I there I anything already done but not pushed yet?

No, there is nothing not-pushed for R4.3 from me.

I am still migrating myself, and adding new arguments and commands happens when I'm sure about them being correctly working. So, I have not done it yet, and checking your valuable PRs would also take some time, if it's OK with you.

[neoniobium]

Fine with me.

[neoniobium]

@jamke Ok, I am finished for now. Every change for Q4.3 that I had listed before has a PR or comment to address it. I might change smaller things if I ran into something but each PR is ready for review (liked in the issue). Smaller things can be improved but I think all basic functionality is implemented.

See Steps to proceed for handling the PRs.

[neoniobium]

BTW: You might consider using shfmt for formatting the bash files. I don't think I can be used to mirror your style exactly but I find very convenient.