* [ISSUE] [RFC] Using virtualpkg to pin a kernel version
@ 2021-09-04 16:30 tornaria
2021-09-04 20:13 ` ericonr
` (7 more replies)
0 siblings, 8 replies; 9+ messages in thread
From: tornaria @ 2021-09-04 16:30 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
New issue by tornaria on void-packages repository
https://github.com/void-linux/void-packages/issues/32833
Description:
Suppose I want to pin my kernel to 5.10, which is the latest LTS.
I can configure
```
virtualpkg=linux:linux5.10
virtualpkg=linux-headers:linux5.10-headers
```
in xbps.d. This works fine in the sense that `linux5.10` will be installed instead of `linux5.13` and it is future proof (contrary to `virtualpkg=linux5.13:linux5.10` which will break when kernel is switched to 5.14).
However, this results in the `linux-base` package as orphan. Of course, I can just change `linux-base` to manual and be done with it, but if I forget this could lead to a broken system and it is more steps to document (and since this is not documented, I don't know if something will change in the future that breaks my system).
I wonder if it would make sense to have a different meta package, say `linux-kernel`, whose only purpose is to depend on `linux${version}`, just like `linux-headers` only purpose is to depend on `linux${version}-headers`.
Then `linux` would be a meta package that depends on `linux-kernel` and `linux-base` (or the actual dependencies as linux-base might become superfluous), and linux kernel version can be pinned easily with virtualpkgs as above. This seems robust enough to be documented in the manual, etc.
---
In fact, it seems the current `linux-base` pkg could just be renamed `linux` adding `linux-kernel` dependency, and the current `linux` could just be renamed `linux-kernel`, keeping `linux-headers` as a subpkg of `linux-kernel`.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [RFC] Using virtualpkg to pin a kernel version
2021-09-04 16:30 [ISSUE] [RFC] Using virtualpkg to pin a kernel version tornaria
@ 2021-09-04 20:13 ` ericonr
2021-09-04 20:27 ` tornaria
` (6 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: ericonr @ 2021-09-04 20:13 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 375 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/32833#issuecomment-913034298
Comment:
My current plan with linux-base was to document removing `linux` and marking it manual, then choosing your preferred version for the kernel. There's an open issue about it in the void-docs repo. Do you think that's too error prone?
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [RFC] Using virtualpkg to pin a kernel version
2021-09-04 16:30 [ISSUE] [RFC] Using virtualpkg to pin a kernel version tornaria
2021-09-04 20:13 ` ericonr
@ 2021-09-04 20:27 ` tornaria
2021-09-04 20:32 ` Chocimier
` (5 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: tornaria @ 2021-09-04 20:27 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 491 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/issues/32833#issuecomment-913036160
Comment:
I just noticed that with `virtualpkg=linux-headers:linux5.10-headers`, when I install a package depending on `linux-headers` (say, `dkms`) it will force-reinstall `linux5.10-headers`. Is that a bug in `xbps-install`, or my misunderstanding?
The alternative would be to `ignorepkg=linux-headers` and then one can install/remove whatever version.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [RFC] Using virtualpkg to pin a kernel version
2021-09-04 16:30 [ISSUE] [RFC] Using virtualpkg to pin a kernel version tornaria
2021-09-04 20:13 ` ericonr
2021-09-04 20:27 ` tornaria
@ 2021-09-04 20:32 ` Chocimier
2021-09-04 20:32 ` tornaria
` (4 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: Chocimier @ 2021-09-04 20:32 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 331 bytes --]
New comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/issues/32833#issuecomment-913036719
Comment:
> it will force-reinstall `linux5.10-headers`
Yes, this is known, reported bug.
Isn't virtualpkg unreliable in general, especially compared to installing your own `linux` pkg spin?
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [RFC] Using virtualpkg to pin a kernel version
2021-09-04 16:30 [ISSUE] [RFC] Using virtualpkg to pin a kernel version tornaria
` (2 preceding siblings ...)
2021-09-04 20:32 ` Chocimier
@ 2021-09-04 20:32 ` tornaria
2021-09-04 20:32 ` tornaria
` (3 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: tornaria @ 2021-09-04 20:32 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 823 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/issues/32833#issuecomment-913036791
Comment:
> My current plan with linux-base was to document removing `linux` and marking it manual, then choosing your preferred version for the kernel. There's an open issue about it in the void-docs repo. Do you think that's too error prone?
Not too error prone, but if I'm not missing anything the way I propose is one step less.
1. current solution
- `ignorepkg=linux`
- mark `linux-base` manual
- remove `linux`
- install `linux5.10`
2. my proposal
-`ignorepkg=linux-kernel`
- remove `linux-kernel`
- install `linux5.10`
Not a big difference. Better imo would be if `virtualpkg=linux-kernel:linux5.10` followed by `xi -u` would be all that's needed.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [RFC] Using virtualpkg to pin a kernel version
2021-09-04 16:30 [ISSUE] [RFC] Using virtualpkg to pin a kernel version tornaria
` (3 preceding siblings ...)
2021-09-04 20:32 ` tornaria
@ 2021-09-04 20:32 ` tornaria
2021-09-04 20:36 ` tornaria
` (2 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: tornaria @ 2021-09-04 20:32 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 824 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/issues/32833#issuecomment-913036791
Comment:
> My current plan with linux-base was to document removing `linux` and marking it manual, then choosing your preferred version for the kernel. There's an open issue about it in the void-docs repo. Do you think that's too error prone?
Not too error prone, but if I'm not missing anything the way I propose is one step less.
1. current solution
- `ignorepkg=linux`
- mark `linux-base` manual
- remove `linux`
- install `linux5.10`
2. my proposal
- `ignorepkg=linux-kernel`
- remove `linux-kernel`
- install `linux5.10`
Not a big difference. Better imo would be if `virtualpkg=linux-kernel:linux5.10` followed by `xi -u` would be all that's needed.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [RFC] Using virtualpkg to pin a kernel version
2021-09-04 16:30 [ISSUE] [RFC] Using virtualpkg to pin a kernel version tornaria
` (4 preceding siblings ...)
2021-09-04 20:32 ` tornaria
@ 2021-09-04 20:36 ` tornaria
2022-06-05 2:14 ` github-actions
2022-06-19 2:15 ` [ISSUE] [CLOSED] " github-actions
7 siblings, 0 replies; 9+ messages in thread
From: tornaria @ 2021-09-04 20:36 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/issues/32833#issuecomment-913037339
Comment:
Point is: you don't have to mess with `linux` and `linux-base` which having different dependencies are a little bit less obvious to understand. You only mess with `linux-kernel` which is defined to be JUST a meta dependency to a particular kernel version and you replace it with a different kernel version.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [RFC] Using virtualpkg to pin a kernel version
2021-09-04 16:30 [ISSUE] [RFC] Using virtualpkg to pin a kernel version tornaria
` (5 preceding siblings ...)
2021-09-04 20:36 ` tornaria
@ 2022-06-05 2:14 ` github-actions
2022-06-19 2:15 ` [ISSUE] [CLOSED] " github-actions
7 siblings, 0 replies; 9+ messages in thread
From: github-actions @ 2022-06-05 2:14 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 293 bytes --]
New comment by github-actions[bot] on void-packages repository
https://github.com/void-linux/void-packages/issues/32833#issuecomment-1146724931
Comment:
Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [ISSUE] [CLOSED] [RFC] Using virtualpkg to pin a kernel version
2021-09-04 16:30 [ISSUE] [RFC] Using virtualpkg to pin a kernel version tornaria
` (6 preceding siblings ...)
2022-06-05 2:14 ` github-actions
@ 2022-06-19 2:15 ` github-actions
7 siblings, 0 replies; 9+ messages in thread
From: github-actions @ 2022-06-19 2:15 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1598 bytes --]
Closed issue by tornaria on void-packages repository
https://github.com/void-linux/void-packages/issues/32833
Description:
Suppose I want to pin my kernel to 5.10, which is the latest LTS.
I can configure
```
virtualpkg=linux:linux5.10
virtualpkg=linux-headers:linux5.10-headers
```
in xbps.d. This works fine in the sense that `linux5.10` will be installed instead of `linux5.13` and it is future proof (contrary to `virtualpkg=linux5.13:linux5.10` which will break when kernel is switched to 5.14).
However, this results in the `linux-base` package as orphan. Of course, I can just change `linux-base` to manual and be done with it, but if I forget this could lead to a broken system and it is more steps to document (and since this is not documented, I don't know if something will change in the future that breaks my system).
I wonder if it would make sense to have a different meta package, say `linux-kernel`, whose only purpose is to depend on `linux${version}`, just like `linux-headers` only purpose is to depend on `linux${version}-headers`.
Then `linux` would be a meta package that depends on `linux-kernel` and `linux-base` (or the actual dependencies as linux-base might become superfluous), and linux kernel version can be pinned easily with virtualpkgs as above. This seems robust enough to be documented in the manual, etc.
---
In fact, it seems the current `linux-base` pkg could just be renamed `linux` adding `linux-kernel` dependency, and the current `linux` could just be renamed `linux-kernel`, keeping `linux-headers` as a subpkg of `linux-kernel`.
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2022-06-19 2:15 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-09-04 16:30 [ISSUE] [RFC] Using virtualpkg to pin a kernel version tornaria
2021-09-04 20:13 ` ericonr
2021-09-04 20:27 ` tornaria
2021-09-04 20:32 ` Chocimier
2021-09-04 20:32 ` tornaria
2021-09-04 20:32 ` tornaria
2021-09-04 20:36 ` tornaria
2022-06-05 2:14 ` github-actions
2022-06-19 2:15 ` [ISSUE] [CLOSED] " github-actions
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).