Bug 1561320 - [modularity] dnf module remove should remove everything from the module
Summary: [modularity] dnf module remove should remove everything from the module
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1478068
TreeView+ depends on / blocked
 
Reported: 2018-03-28 06:01 UTC by Remi Collet
Modified: 2018-04-19 19:05 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-03-28 11:19:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Remi Collet 2018-03-28 06:01:43 UTC
Reproducer

# install a module
dnf module install foo
# install some optional package from the module
dnf install bar
# remove the module
dnf module remove foo

Everything from the module should be removed.
For now some packages from the module are not removed.

Comment 1 Petr Šabata 2018-03-28 07:32:30 UTC
I would keep packages that are also part of other enabled (explicitly or by default) modules if some of those RPMs were shared.

Comment 2 Martin Hatina 2018-03-28 11:19:03 UTC
According to reproducer dnf installs foo:default_stream/default_profile, and removes foo:default_stream/default_profile, not whole stream (every installed profile from the stream). Also it doesn't remove rpm, which was explicitly installed by user (bar in reproducer). This is expected behaviour.

Comment 3 Petr Šabata 2018-03-28 11:30:51 UTC
To me the expected behavior would be removing all RPMs owned by that module (unless they're also owned by something else, as noted in comment #1), no matter whether they were installed via a profile or by their name.

Comment 4 Remi Collet 2018-03-28 11:37:29 UTC
(In reply to Petr Šabata from comment #3)
> To me the expected behavior would be removing all RPMs owned by that module
> (unless they're also owned by something else, as noted in comment #1), no
> matter whether they were installed via a profile or by their name.

+1

(In reply to Martin Hatina from comment #2)
> This is expected behaviour.

This is terribly confusing for users.


Note You need to log in before you can comment on or make changes to this bug.