Bug 1288771

Summary: After installing Fedora 23 Mate I cannot do the first update via DNF
Product: [Fedora] Fedora Reporter: Jxanti.jx
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: 23CC: jmracek, jsilhan, Jxanti.jx, mdomonko, mluscon, packaging-team-maint, pnemade, vmukhame
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-12-14 13:28:57 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:
Attachments:
Description Flags
two screenshots of the dnf errors
none
requested dnf.log none

Description Jxanti.jx 2015-12-05 22:49:17 UTC
Created attachment 1102637 [details]
two screenshots of the dnf errors

Description of problem: After installing Fedora 23 Mate I cannot do the first update via DNF


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


How reproducible:see above 


Steps to Reproduce:
1.Install Fedora 23 Mate and do the first update via DNF
2.See attachment dnferror.tar.gz with two screenshots.
3.

Actual results:


Expected results:


Additional info:
Finally I did the update via the old yumex without problems.

Comment 1 Michal Luscon 2015-12-09 10:29:44 UTC
Could you please append a relevant dnf.log file?

Comment 2 Jxanti.jx 2015-12-09 10:50:27 UTC
Created attachment 1103826 [details]
requested dnf.log

equested dnf.log

Comment 3 Jaroslav Mracek 2015-12-14 13:28:57 UTC
Please use command dnf group install <groupname>.
If you will experience further problem, please provide us additional information with commands and their output. Also please provide dnf version. Than we can reproduce it and fix it.

Comment 4 Honza Silhan 2015-12-14 16:48:44 UTC
I believe comment 3 belonged to (bug 1288839)

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