Bug 612021 - tasks-0.16-2.fc12 (still in FC13) requires old evolution-data-server libedataserver-1.2.so.11
tasks-0.16-2.fc12 (still in FC13) requires old evolution-data-server libedata...
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: tasks (Show other bugs)
13
All Linux
low Severity medium
: ---
: ---
Assigned To: Dan Young
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-07 00:52 EDT by J. Randall Owens
Modified: 2010-12-21 18:13 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-12-21 18:13:43 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description J. Randall Owens 2010-07-07 00:52:35 EDT
Description of problem:
tasks requires libedataserver-1.2.so.11, but the new evolution-data-server-2.30.2-2.fc13 provides libedataserver-1.2.so.13 instead.  tasks was painfully holding up my updates for a couple of weeks until I finally took the time to narrow down the dependency that wasn't letting evolution stuff update.

Version-Release number of selected component (if applicable):
tasks-0.16-2.fc12

How reproducible:
attempt to install tasks on an updated F(C)13 machine, or attempt to update a machine with tasks & evolution installed.

Additional info:
Just checked koji & then updates-testing, and 0-16.3-3.fc13 seems to fix it.  I'll make this bug report anyway, but expect it'll be fixed.  I'll go give it some good karma to get it moving along, assuming it works as expected.
Comment 1 Dan Young 2010-12-21 18:13:43 EST
This was fixed:
http://lists.fedoraproject.org/pipermail/test/2010-July/091839.html

A soname bump on libedataserver went out by accident. Someone rebuilt tasks in my absence. Sorry this bug hung out there open so long. Was on vacation when it happened and missed it all this time somehow. My apologies.

I'm closing this now.

Note You need to log in before you can comment on or make changes to this bug.