Bug 25398

Summary:	dnf autoremove and urpme --auto-orphans don't return the same things
Product:	Mageia	Reporter:	peter lawford <petlaw726>
Component:	RPM Packages	Assignee:	Neal Gompa <ngompa13>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	ouaurelien
Version:	6
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description peter lawford 2019-09-03 11:59:04 CEST

Description of problem:

[root@mag6 alain4]# LANGUAGE=C dnf autoremove
Last metadata expiration check: 0:05:17 ago on mar. 03 sept. 2019 11:48:39 CEST.
Dependencies resolved.
Nothing to do.
Complete!
[root@mag6 alain4]#

and 

[root@mag6 alain4]# LANGUAGE=C urpme --auto-orphans
To satisfy dependencies, the following 5 packages will be removed (2.6MB):
  
(orphan packages)
  lib64gltf0.1_1-0.1.0-2.mga6.x86_64
  lib64ixion0.12_0-0.12.2-1.mga6.x86_64
  lib64javascriptcore-gir3.0-2.4.10-3.mga6.x86_64
  lib64orcus0.12_0-0.12.1-2.mga6.x86_64
  lib64webkit-gir3.0-2.4.10-3.mga6.x86_64
Remove 5 packages? (y/N)

I didn't yet test for M7





Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Comment 1 Lewis Smith 2019-09-03 21:42:26 CEST

> dnf autoremove and urpme --auto-orphans don't return the same things
I suppose they should?

Trying this on Mageia 7, alas with no orphans available, gave identical results:
 # dnf autoremove
Last metadata expiration check: 0:03:13 ago on Dydd Mawrth 03 mis Medi 2019 21:32:58 CEST.
Dependencies resolved.
Nothing to do.
Complete!
 # urpme --auto-orphans
Dim pecynnau amddifad i'w tynnu        [no orphans to remove]

Assigning to Neal for dnf.

Summary: dnf remove and urpme --auto-orphans don't return the same things => dnf autoremove and urpme --auto-orphans don't return the same things
Assignee: bugsquad => ngompa13

Comment 2 peter lawford 2019-09-04 00:50:01 CEST

(In reply to Lewis Smith from comment #1)
> > dnf autoremove and urpme --auto-orphans don't return the same things
> I suppose they should?
> 
> Trying this on Mageia 7, alas with no orphans available, gave identical
> results:
>  # dnf autoremove
> Last metadata expiration check: 0:03:13 ago on Dydd Mawrth 03 mis Medi 2019
> 21:32:58 CEST.
> Dependencies resolved.
> Nothing to do.
> Complete!
>  # urpme --auto-orphans
> Dim pecynnau amddifad i'w tynnu        [no orphans to remove]
> 
> Assigning to Neal for dnf.

is this language gaelic? am I true? 
if there is no orphans, the fact that dnf remove and urpme --auto-orphans give the same result is obvious, but in the case here considered, why dnf remove didn't make its job?

Comment 3 Neal Gompa 2019-09-12 21:11:01 CEST

If packages were not installed by DNF, DNF assumes they were user-installed, and so they will *not* necessarily be eligible for consideration for dnf autoremove.

Were the packages in question installed by urpmi or dnf?

Comment 4 peter lawford 2019-09-13 16:00:49 CEST

(In reply to Neal Gompa from comment #3)
> If packages were not installed by DNF, DNF assumes they were user-installed,
> and so they will *not* necessarily be eligible for consideration for dnf
> autoremove.
> 
> Were the packages in question installed by urpmi or dnf?

I don't think there is 2 sorts of pkgs, those installed with dnf and those installed with urpmi; a package is a package, either it is an orphan either it is not

Comment 5 katnatek 2019-09-13 19:41:50 CEST

(In reply to peter lawford from comment #4)
> I don't think there is 2 sorts of pkgs, those installed with dnf and those
> installed with urpmi; a package is a package, either it is an orphan either
> it is not

Yes but as with metadata,i suppose that databases of urpmi and dnf are different

Comment 6 Aurelien Oudelet 2020-08-23 15:46:30 CEST

Hi, thanks for reporting this bug.
We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there.
As a result we are setting this bug to CLOSED:OLD

Resolution: (none) => OLD
CC: (none) => ouaurelien
Status: NEW => RESOLVED