Bug 31216

Summary: urpmi loses "--no-recommends" option on automatic restart
Product: Mageia Reporter: Oleg Bosis <olelukoie>
Component: RPM PackagesAssignee: Mageia tools maintainers <mageiatools>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Normal CC: davidwhodgins
Version: 8   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard: CAULDRONTOO ?
Source RPM: urpmi-8.125-1.mga8 CVE:
Status comment:

Description Oleg Bosis 2022-12-04 10:10:01 CET 
Description of problem:

Trying to update packages I've noticed that urpmi got lost --no-recommends option after restart due to glibc update (sorry for non-English output, I've just forgot to add LC_ALL=C and now packages are already updated and I can not reproduce the situation for now for proper English text):

#urpmi --auto-update --no-recommends
....
Для удовлетворения зависимостей будут установлены следующие пакеты:
  Пакет                          Версия       Релиз         Платформа 
(источник «Core Updates (distrib3)»)
  glibc                          2.32         30.mga8       x86_64  
  glibc-devel                    2.32         30.mga8       x86_64  
Будет использовано 3.5КБ дополнительного дискового пространства.
....
Необходимо перезапустить компьютер для glibc
urpmi перезапускается                                               <<<<<---------- urpmi restarts here
Для удовлетворения зависимостей будут установлены следующие пакеты:
  Пакет                          Версия       Релиз         Платформа 
(источник «google-chrome»)
  google-chrome-stable           108.0.5359.> 1             x86_64  
(источник «Core Updates (distrib3)»)
  dkms-virtualbox                7.0.4        1.mga8        x86_64  
  nscd                           2.32         30.mga8       x86_64  
  virtualbox                     7.0.4        1.mga8        x86_64  
(источник «Core Backports (distrib7)»)
  virtualbox-kernel-6.0.9-deskt> 7.0.4        2.mga8        x86_64  <<<<---- This package is recommended
Будет использовано 878КБ дополнительного дискового пространства.
....

Tha last package here "virtualbox-kernel-6.0.9-deskt..." is a recommended one and had to be skipped but was not and it was not even marked as recommended.

Version-Release number of selected component (if applicable):
urpmi-8.125-1.mga8

How reproducible:
always

Steps to Reproduce:
1.
2.
3.
Comment 1 Lewis Smith 2022-12-04 20:05:29 CET 
Thank you for the report.

       --no-recommends
           With this option, urpmi will not install "recommended" packages.
           By default, urpmi will install (newly) recommended packages.

"Tha last package here 'virtualbox-kernel-6.0.9-deskt...' is a recommended one and had to be skipped but was not and it was not even marked as recommended"

Looking on M9, which is very probably the same as M8 for this, I can find no connection between virtualbox & virtualbox-kernel, even at the 'recommended' level; so the reported recommendation is in itself curious.

The main point is clear enough:
 #urpmi --auto-update --no-recommends
after an auto-restart (after glibc) does go on to include a package it thinks is recommended.

Assigning to Mageiatools.

Whiteboard: (none) => CAULDRONTOO ?
Assignee: bugsquad => mageiatools

Comment 2 Dave Hodgins 2022-12-04 21:37:08 CET 
On m8, the virtualbox-kernel package is selected based on
$ rpm -q --requires virtualbox|grep kmod
kmod(vboxdrv.ko) = 7.0.4

It is not based on a recommends ...
$ rpm -q --recommends virtualbox
virtualbox-doc

I suspect this is a duplicate of bug 29830, assuming the backports repo has
not been enabled.

CC: (none) => davidwhodgins