Bug 1397297

Summary: [RFE] Display source repository of package in reports
Product: [Fedora] Fedora Reporter: Vít Ondruch <vondruch>
Component: libsolvAssignee: rpm-software-management
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: ignatenko, jmracek, mluscon, packaging-team-maint, pnemade, rpm-software-management, vmukhame
Target Milestone: ---Keywords: FutureFeature, Reopened, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-21 11:11:52 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:

Description Vít Ondruch 2016-11-22 08:41:24 UTC
Description of problem:
It bug 1263888, there are error messages such as:

```
- cannot install both vim-minimal-2:8.0.086-1.fc26.x86_64 and vim-minimal-2:8.0.094-1.fc26.x86_64
```

The problem with this message is that it is not clear where the package comes from. It would be useful, it the message stated the repository as well.


Version-Release number of selected component (if applicable):
$ rpm -q dnf
dnf-2.0.0-0.rc1.4.fc26.noarch


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
- cannot install both vim-minimal-2:8.0.086-1.fc26.x86_64 and vim-minimal-2:8.0.094-1.fc26.x86_64

Expected results:
- cannot install both vim-minimal-2:8.0.086-1.fc26.x86_64@@commandline and vim-minimal-2:8.0.094-1.fc26.x86_64@fedora

Additional info:

Comment 1 Igor Gnatenko 2016-11-28 11:13:53 UTC
This probably needs some support from libsolv side (probably only from that side), though Michael Mraka should know better.

Comment 2 Jaroslav Mracek 2017-06-08 11:30:40 UTC
We refactored error reports from libsolv in dnf-2.5.0. In this version if you get error like presented by you just run the same command with --skip-broken and you should see the transaction table with skipped packages with information that you requested. Hope that the information is sufficient. Please if you will not like it, or some problems appears, don't hesitate to reopen the bug report.

Comment 3 Igor Gnatenko 2017-06-14 10:26:56 UTC
1. We don't generate our own messages, so whatever has been done in 2.5.0 doesn't affect this bug
2. Until we generate our own messages, libsolv should report repo from which package has conflict

Comment 4 Vít Ondruch 2017-06-14 10:44:00 UTC
(In reply to Igor Gnatenko from comment #3)
Thx for checking this.

I tried the reproducer from bug 1263888, but it does not work anymore, since the bug was resolved. Not sure how to test it now ... but hopefully I'll find some reproducer soon :)

Comment 5 Igor Gnatenko 2017-06-21 11:11:52 UTC
Let's track it in upstream.