Bug 1203699

Summary: installonly packages over installonly_limit should be removed only when transaction already contains them
Product: [Fedora] Fedora Reporter: Michael Mráka <mmraka>
Component: dnfAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: jsilhan, mluscon, packaging-team-maint, pnemade, rholy, tim.lauridsen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-21 11:33:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michael Mráka 2015-03-19 13:35:14 UTC 
Description of problem:
dnf tries to remove installonly packages over installonly_limit during a completely irrelevant transaction.

Version-Release number of selected component (if applicable):
dnf-0.6.4-2.fc22.noarch

How reproducible:
always

Steps to Reproduce:
1. install more than 3 versions of kernel (or set installonly_limit to one less than number of your installed kernels)
2. dnf update dnf

Actual results:
# dnf update dnf
Using metadata from Thu Mar 19 01:12:46 2015
Dependencies resolved.
==========================================================================================================
 Package                     Arch                Version                       Repository            Size
==========================================================================================================
Removing:
 kernel                      x86_64              3.17.4-301.fc21               @System                0  
 kernel-core                 x86_64              3.17.4-301.fc21               @System               40 M
 kernel-modules              x86_64              3.17.4-301.fc21               @System               17 M

Transaction Summary
==========================================================================================================
Remove  3 Packages

Installed size: 57 M
Is this ok [y/N]: 


Expected results:
# dnf update dnf
Using metadata from Thu Mar 19 01:12:46 2015
Error: No packages marked for upgrade.


Additional info:
The same behaviour observed for clean_requirements_on_remove set to both true and false.
At least clean_requirements_on_remove=false shouldn't do it.
Comment 1 Honza Silhan 2015-07-21 11:33:56 UTC 

*** This bug has been marked as a duplicate of bug 1160011 ***