Bug 1540189 - [modularity] info for a profile is not profile-specific
Summary: [modularity] info for a profile is not profile-specific
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 28
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1478068
TreeView+ depends on / blocked
 
Reported: 2018-01-30 12:54 UTC by Eva Mrakova
Modified: 2018-11-22 18:24 UTC (History)
5 users (show)

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


Attachments (Terms of Use)

Description Eva Mrakova 2018-01-30 12:54:57 UTC
Description of problem:
when a profile is a part of 'dnf modularity info' argument, printed info 
is not profile-specific. The output is the same for all profiles, even 
for non-existent ones.

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

How reproducible:
always

Steps to Reproduce:
1. create a module with multiple profiles
   (e.g. ModuleA/client, server, default, devel, minimal)
2. enable the module 
3. run 'dnf module info' for various arguments, e.g.
   dnf module info ModuleA
   dnf module info ModuleA:f26
   dnf module info ModuleA:f26/client
   dnf module info ModuleA:f26/default
   dnf module info ModuleA:f26/non-existent-profile
   
Actual results:
the output is the same for all commands mentioned above  

Expected results:
info for profiles should be profile-specific 
or at least a warning should be printed that the profile is ignored

Comment 1 Fedora End Of Life 2018-02-20 15:32:11 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.


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