Bug 1276279

Summary:	libreoffice langpacks doesn't match core version
Product:	[Fedora] Fedora	Reporter:	Łukasz Posadowski <mail>
Component:	libreoffice	Assignee:	Caolan McNamara <caolanm>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	23	CC:	caolanm, dtardon, erack, fiedler_matthias, ltinkl, mstahl, sbergman
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-30 17:25:54 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 Łukasz Posadowski 2015-10-29 10:39:09 UTC

Description of problem:
version of libreoffice-core
libreoffice-core.x86_64 1:5.0.3.1-1.fc23 @updates-testing

version of langpacks
libreoffice-langpack-pl.x86_64 1:5.0.0.5-2.fc23 fedora

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


How reproducible:
always

Steps to Reproduce:
1. try to install libreoffice-pangpack-lang_of_your_choice
2. 
3.

Actual results:
dnf install libreoffice-langpack-pl
Error: package libreoffice-langpack-pl-1:5.0.0.5-2.fc23.x86_64 requires libreoffice-core = 1:5.0.0.5-2.fc23, but none of the providers can be installed
(try to add '--allowerasing' to command line to replace conflicting packages)


Expected results:
Installed langpack package.

Additional info:

Comment 1 David Tardon 2015-10-30 17:25:54 UTC

Until recently F-23 automatically enabled updates-testing repository (which is done for the convenience of testers). Either downgrade installed libreoffice packages to what is in the stable repository or use --enablerepo=*-testing .

Comment 2 Łukasz Posadowski 2015-10-31 08:56:48 UTC

Thank you.

Comment 3 Stephan Bergmann 2015-11-02 07:40:39 UTC

*** Bug 1276835 has been marked as a duplicate of this bug. ***