Comment # 10 on bug 1231341 from Daniel Pecka

Hello Takashi-San,

and isn't then possible and reasonable to just stick with existing virtualbox

# zypper -vv se -xs -r kernel -r kernel-kmp kernel-default
virtualbox-kmp-default virtualbox
Verbosity: 3
Non-option program arguments: 'kernel-default' 'virtualbox-kmp-default'
'virtualbox' 
Initializing Target
Loading repository data...
Reading installed packages...

S  | Name                   | Type       | Version                             
    | Arch   | Repository
---+------------------------+------------+------------------------------------------+--------+-----------
il | kernel-default         | package    | 6.11.5-lp155.4.1.g4703d94           
    | x86_64 | kernel
   | kernel-default         | srcpackage | 6.11.5-lp155.4.1.g4703d94           
    | noarch | kernel
   | kernel-default         | srcpackage | 6.11.5-lp155.3.1.g6764933           
    | noarch | kernel
i+ | virtualbox             | package    | 7.0.20-lp155.2.31                   
    | x86_64 | kernel-kmp
   | virtualbox             | srcpackage | 7.0.20-lp155.2.31                   
    | noarch | kernel-kmp
il | virtualbox-kmp-default | package    |
7.1.4_k6.11.5_lp155.4.g4703d94-lp155.2.1 | x86_64 | kernel-kmp

and just build a virtualbox-kmp-default for 7.0.20-lp155.2.31 ?

I don't get why we're pushing into the repository packages that don't work ..
virtualbox-7.0.20-lp155.2.31 is latest and current vbox package in the
repository .. If we cannot build a newer due to some dependencies please build
along with updated kernel packages a virtualbox-kmp-default for current
virtualbox ..

thanks and regards, ~dan