Bug 1581609 - [modularity] Removing a module does not erase version info from config file
Summary: [modularity] Removing a module does not erase version info from config file
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1478068 1581615
TreeView+ depends on / blocked
 
Reported: 2018-05-23 08:38 UTC by Rafael Fonseca
Modified: 2018-11-22 18:13 UTC (History)
5 users (show)

Fixed In Version: dnf-4.0.4
Clone Of:
: 1581615 (view as bug list)
Environment:
Last Closed: 2018-11-22 18:13:39 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Rafael Fonseca 2018-05-23 08:38:10 UTC 
Description of problem: If you remove an installed module, its config file continue showing 'version = X' even though there are no profiles installed.


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


How reproducible: always


Steps to Reproduce:
1. dnf module enable ModuleB:f26
2. dnf module install ModuleB/default
3. dnf module remove ModuleB:f26

Actual results: /etc/dnf/modules.d/ModuleB.module has 'version = 1'


Expected results: /etc/dnf/modules.d/ModuleB.module has 'version = -1'


Additional info:
Comment 1 Martin Hatina 2018-07-24 14:04:32 UTC 
https://github.com/rpm-software-management/dnf/pull/1144
Comment 2 Jan Kurik 2018-08-14 11:14:03 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.
Note You need to log in before you can comment on or make changes to this bug.