Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qubes-core-admin-client missing /usr/bin/qvm-block? #8786

Open
ddevz opened this issue Dec 21, 2023 · 2 comments · May be fixed by QubesOS/qubes-core-admin-client#269
Open

qubes-core-admin-client missing /usr/bin/qvm-block? #8786

ddevz opened this issue Dec 21, 2023 · 2 comments · May be fixed by QubesOS/qubes-core-admin-client#269
Labels
affects-4.1 This issue affects Qubes OS 4.1. C: core diagnosed Technical diagnosis has been performed (see issue comments). P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. pr submitted A pull request has been submitted for this issue. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@ddevz
Copy link

ddevz commented Dec 21, 2023

How to file a helpful issue

Qubes OS release

4.1

qubes-core-admin-client version:

Installed: 4.1.27-1+deb11u1
Candidate: 4.1.27-1+deb11u1
Version table:
*** 4.1.27-1+deb11u1 500
500 https://deb.qubes-os.org/r4.1/vm bullseye/main amd64 Packages
100 /var/lib/dpkg/status

Brief summary

Not sure if this is intended, but I believe that /usr/bin/qvm-block is supposed to be a symbolic link to /usr/bin/qvm-device . If it is supposed to be there, then since qvm-device was installed by qubes-core-admin-client, I'm guessing that qubes-core-admin-client was supposed to be the one to add the link.

Steps to reproduce

sudo apt install qubes-core-admin-client
ls -l /usr/bin/qvm-block

Expected behavior

see symbolic link to /usr/bin/qvm-device

Actual behavior

no such file

@ddevz ddevz added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. labels Dec 21, 2023
@andrewdavidwong andrewdavidwong added C: core needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. affects-4.1 This issue affects Qubes OS 4.1. labels Dec 21, 2023
DemiMarie added a commit to DemiMarie/qubes-core-admin-client that referenced this issue Dec 22, 2023
These were only in dom0, which is inconsistent.

Fixes: QubesOS/qubes-issues#8786
@DemiMarie
Copy link

Is there a clean way to make this work with package upgrades? The problem with the naive solution is that the new qubes-core-admin-client and the old qubes-core-dom0 can’t be installed simultaneously. I can, of course, make adding the symlinks conditional on the Fedora version being greater than 37 (R4.2’s dom0), but that’s ugly.

@DemiMarie DemiMarie added the diagnosed Technical diagnosis has been performed (see issue comments). label Dec 22, 2023
@DemiMarie
Copy link

@ddevz Simplest workaround is to use qvm-device block instead.

@DemiMarie DemiMarie removed the needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. label Dec 22, 2023
@DemiMarie DemiMarie self-assigned this Dec 22, 2023
@andrewdavidwong andrewdavidwong added the pr submitted A pull request has been submitted for this issue. label Dec 23, 2023
@DemiMarie DemiMarie removed their assignment Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.1 This issue affects Qubes OS 4.1. C: core diagnosed Technical diagnosis has been performed (see issue comments). P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. pr submitted A pull request has been submitted for this issue. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants