Closed andrewdavidwong closed 5 years ago
The place where message appears suggests the problem was with the old package, not the new one.
The place where message appears suggests the problem was with the old package, not the new one.
Oh, strange. Presumably, it's not trying to install a kernel module for the kernel it's erasing. Is the message just misleading?
I have the same message. Can this be ignored for the moment?
On Sun, Aug 12, 2018 at 05:48:16AM -0700, Boris Kourtoukov wrote:
I have the same message. Can this be ignored for the moment?
Yes.
Automated announcement from builder-github
The package qubes-core-dom0-linux-3.2.18-1.fc23
has been pushed to the r3.2
testing repository for dom0.
To test this update, please install it with the following command:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
Automated announcement from builder-github
The package qubes-core-dom0-linux-3.2.18-1.fc23
has been pushed to the r3.2
stable repository for dom0.
To install this update, please use the standard update command:
sudo qubes-dom0-update
Or update dom0 via Qubes Manager.
@andrewdavidwong @marmarek Looks like the change is in stable now, can this issue be closed, or is there more left to do?
Looks like the change is in stable now, can this issue be closed, or is there more left to do?
Normally, this would be closed from a commit. So, either there's still more to do, or someone forgot to include the appropriate close command in a commit message.
marmarek did put "Fixes QubesOS/qubes-issues#4181" in the commit message, but for some reason it didn't close this issue like it normally would
marmarek did put "Fixes #4181" in the commit message, but for some reason it didn't close this issue like it normally would
It won't close this issue until the commit is merged into the repo's default branch (master
):
https://help.github.com/articles/closing-issues-using-keywords/
You can see that if you hover over the "i" icon next to the commit line above.
Unfortunately related fix in master branch lack "Fixes" tag, so it won't close this issue automatically. It's here: QubesOS/qubes-core-admin-linux@68dd0135855aec06e9b9981dbed80f9b08aa07cc
Qubes OS version:
R3.2
Affected component(s):
kernel (module
salsa20-x86_64
)Steps to reproduce the behavior:
Use
qubes-dom0-update
to install:kernel-1000:4.14.57-1.pvops.qubes.x86_64
kernel-qubes-vm-1000:4.14.57-1.pvops.qubes.x86_64
Expected behavior:
No module installation failures.
Actual behavior:
Failed to install module salsa20-x86_64
More verbose log:
General notes:
Related issues: