Bug 489496 - taskjuggler-2.4.1-4.fc10 update includes broken Obsoletes
Summary: taskjuggler-2.4.1-4.fc10 update includes broken Obsoletes
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: taskjuggler
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ondrej Vasik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-10 13:54 UTC by Rex Dieter
Modified: 2009-03-16 19:49 UTC (History)
1 user (show)

Fixed In Version: 2.4.1-5.fc10
Clone Of:
Environment:
Last Closed: 2009-03-16 19:49:47 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Rex Dieter 2009-03-10 13:54:56 UTC 
taskjuggler-libs contains:
Obsoletes: %{name} < %{version}-%{release}

which is almost never a good idea.  In fact, breaks updates.

taskjuggler will get "updated" to taskjuggler-libs

My suggestion would be to make the Obsoletes versioned to when the split occurred, 
Obsoletes: taskjuggler < 2.4.0-7
and add to -libs
Requires: %{name} = %{version]-%{release}
Comment 1 Rex Dieter 2009-03-10 14:02:44 UTC 
With he added "Requires" in place, wouldn't be a bad idea to omit the Obsoletes altogether either.
Comment 2 Ondrej Vasik 2009-03-10 14:31:57 UTC 
Thanks for report, good point, will do...
Comment 3 Fedora Update System 2009-03-11 18:03:55 UTC 
taskjuggler-2.4.1-5.fc10, kdepim3-3.5.10-1.fc10 has been pushed to the Fedora 10 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update taskjuggler kdepim3'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-2544
Comment 4 Fedora Update System 2009-03-16 19:49:37 UTC 
taskjuggler-2.4.1-5.fc10, kdepim3-3.5.10-1.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.