Bug 1402165

Summary:	sagemath conflict causes dnf system-upgrade to fail
Product:	[Fedora] Fedora	Reporter:	Paul DeStefano <prd-fedora>
Component:	sagemath	Assignee:	Paulo Andrade <paulo.cesar.pereira.de.andrade>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	24	CC:	paulo.cesar.pereira.de.andrade
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-21 17:10:58 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:

Description Paul DeStefano 2016-12-07 00:10:11 UTC

Description of problem:
dnf system-upgrade download fails with these errors at the very end. "Error summary" section is empty.

  file /usr/share/doc/sagemath/output from install of sagemath-doc-7.3-6.fc25.x86_64 conflicts with file from package sagemath-doc-6.8-14.fc24.x86_64
  file /usr/lib64/python2.7/site-packages/sagenb/data/mathjax from install of sagemath-notebook-7.3-6.fc25.x86_64 conflicts with file from package sagemath-notebook-6.8-14.fc24.x86_64


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


How reproducible:
Sort of a one-time test.  Not sure if others are experiencing it.

Steps to Reproduce:
1. Install F24
2. install sagemath
3. dnf system-upgrade download --releasever=25 --allowerasing

Actual results:
see above error

Expected results:
no error

Additional info:

I think this is the third system upgrade (F22->23,23->24,24-25) that failed due to problems sagemath.  F22->F23 occurred but then sage was broken.  At least these are getting caught, now.

Comment 1 Paulo Andrade 2016-12-21 17:10:58 UTC

Sorry for the issue.
An update should be available soon, that will at least
fix it for people updating after the sagemath update.

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