Bug 19541

Summary:	Many orphaned packages after an upgrade from "Mageia 5" to "Mageia Cauldron".
Product:	Mageia	Reporter:	PC LX <mageia>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED INVALID	QA Contact:
Severity:	major
Priority:	Normal	CC:	mageia, marja11, zen25000
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	urpmi	CVE:
Status comment:
Attachments:	installed rpms before upgrade installed rpms before upgrade with list of packages that required them upgrade log, basically the output of "urpmi --auto-upgrade" installed rpms after the upgrade installed rpms after the upgrade with list of packages that required them installed rpms after the upgrade that considered orphaned (basically the output of "urpme --auto-orphans") before upgrade: /var/lib/rpm/installed-through-deps.list after upgrade: /var/lib/rpm/installed-through-deps.list

Description PC LX 2016-10-05 16:30:47 CEST

Description of problem:

I have been doing "Mageia 5" to cauldron upgrades and I've noticed an issue.

After an upgrade, "urpme --auto-orphans" reports 399 orphaned packages. Before the upgrade there were no orphaned packages. Once curious aspect is that of those 399, 232 are new (mga6) packages.

Some of those packages should not be considered orphans (e.g. digikam, kamera, 
keyutils, lm_sensors) as they were already installed and were not orphans 
before.

I'll attach list of installed packages for before and after the upgrade and a upgrade log (urpmi output).

I'm using btrfs subvolumes to do these upgrade tests so I can easily make more upgrade tests as needed.


How reproducible:

Probably always.


Steps to Reproduce:
1. Start with a fully up-to-date "Mageia 5" installation, with no orphaned packages.
2. Remove all "Mageia 5" repositories.
3. Add "Mageia Cauldron" repositories.
4. Run "urpmi --auto-update" and let it update the installation. I had to repeat this step a second time, due to a file conflict, until all packages were updated.
5. Run "urpme --auto-orphans" and see many (399 in my case) orphaned packages, including many mga6 packages (232 in my case).

Comment 1 PC LX 2016-10-05 16:31:18 CEST

Created attachment 8494 [details]
installed rpms before upgrade

Comment 2 PC LX 2016-10-05 16:32:09 CEST

Created attachment 8495 [details]
installed rpms before upgrade with list of packages that required them

Comment 3 PC LX 2016-10-05 16:32:58 CEST

Created attachment 8496 [details]
upgrade log, basically the output of "urpmi --auto-upgrade"

Comment 4 PC LX 2016-10-05 16:33:28 CEST

Created attachment 8497 [details]
installed rpms after the upgrade

Comment 5 PC LX 2016-10-05 16:33:55 CEST

Created attachment 8498 [details]
installed rpms after the upgrade with list of packages that required them

Comment 6 PC LX 2016-10-05 16:34:47 CEST

Created attachment 8499 [details]
installed rpms after the upgrade that considered orphaned (basically the output of "urpme --auto-orphans")

David Walser 2016-10-05 16:50:25 CEST

CC: (none) => mageia

Comment 7 PC LX 2016-10-05 17:07:43 CEST

Created attachment 8500 [details]
before upgrade: /var/lib/rpm/installed-through-deps.list

Comment 8 PC LX 2016-10-05 17:09:01 CEST

Created attachment 8501 [details]
after upgrade: /var/lib/rpm/installed-through-deps.list

Comment 9 Barry Jackson 2016-10-06 01:27:53 CEST

(In reply to PC LX from comment #6)
> Created attachment 8499 [details]
> installed rpms after the upgrade that considered orphaned (basically the
> output of "urpme --auto-orphans")

I can explain grub2-mageia-theme. It is not now recommended or required by grub2{,-efi} but is installed by the installer/drakboot as needed.

So maybe other packages that are installed by the installer as 'top level' packages i.e. not installed as deps of anything else, are not being considered as 'manually installed'?

CC: (none) => zen25000

Comment 10 Marja Van Waes 2016-10-07 11:35:47 CEST

Thierry will know :-)

CC: (none) => marja11
Assignee: bugsquad => thierry.vignaud
Source RPM: (none) => urpmi

Comment 11 Thierry Vignaud 2016-10-15 01:30:03 CEST

AFAIC the orphaned packages are orphaned b/c they're no more required or recommended.
The fact they are tagged mga6 as irrelevant.
Eg: libmesaegl1 was there before, it has been uptaded to the mga6 version but it's not actually needed anymore thus it's offered for cleaning

Status: NEW => RESOLVED
Resolution: (none) => INVALID