Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1016693 - updates-testing MODULE_COMPAT confusion
Summary: updates-testing MODULE_COMPAT confusion
Keywords:
Status: CLOSED DUPLICATE of bug 992666
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Language-Expr
Version: 20
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Miro Hrončok
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-08 14:26 UTC by Jay Woods
Modified: 2013-10-09 10:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-09 10:15:53 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jay Woods 2013-10-08 14:26:42 UTC 
Description of problem:
           Requires: perl(:MODULE_COMPAT_5.16.2)
           Removing: 4:perl-5.16.3-265.fc19.i686 (@updates/19)
               perl(:MODULE_COMPAT_5.16.2)
           Updated By: 4:perl-5.18.1-288.fc20.i686 (fedora)
              ~perl(:MODULE_COMPAT_5.18.1)
              ~perl(:MODULE_COMPAT_5.18.0)

Version-Release number of selected component (if applicable):
perl-Language-Expr-0.19-4.fc19.noarch
slic3r-0.9.10b-2.fc20.noarch
How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Paul Howarth 2013-10-08 20:49:00 UTC 
perl-Language-Expr is current incompatible with perl 5.18 in Fedora 20 (Bug #992666) so you'll have to remove it and anything that depends on it (e.g. slic3r) prior to attempting a yum upgrade from F19 to F20 (which is what it looks like you're trying to do).
Comment 2 Miro Hrončok 2013-10-09 10:15:53 UTC 

*** This bug has been marked as a duplicate of bug 992666 ***
Note You need to log in before you can comment on or make changes to this bug.