Bug 486083 - Package Translate Toolkit 1.3.0 for F10 (Virtaal 0.3.0 in F10 had broken deps on 1.3.0)
Summary: Package Translate Toolkit 1.3.0 for F10 (Virtaal 0.3.0 in F10 had broken deps...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: translate-toolkit
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Roozbeh Pournader
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-18 09:40 UTC by Hans Ulrich Niedermann
Modified: 2009-02-21 11:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-02-21 11:18:11 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Hans Ulrich Niedermann 2009-02-18 09:40:15 UTC 
Description of problem:

  virtaal in F10 stable has broken depdencies. It depends
  on a translate-toolkit version which is NOT in F10 stable.

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

  virtaal-0.3.0-2.fc10.noarch

How reproducible:

  100%

Steps to Reproduce:
1. yum update
  
Actual results:

  Error: Missing Dependency: translate-toolkit >= 1.3 is needed by package virtaal-0.3.0-2.fc10.noarch (updates)

Expected results:

  Clean install.

Additional info:
Comment 1 Dwayne Bailey 2009-02-18 11:22:30 UTC 
Thanks for reporting this.  Darn how did I miss this one, was cautious about this release.
Comment 2 Dwayne Bailey 2009-02-18 11:31:54 UTC 
Changed to Translate Toolkit component as Virtaal 0.3.0 can't work with earlier versions of Translate Toolkit.
Comment 3 Hans Ulrich Niedermann 2009-02-18 11:41:30 UTC 
(In reply to comment #1)
> Thanks for reporting this.  Darn how did I miss this one, was cautious about
> this release.

More importantly... why does bodhi allow pushing a package with broken deps in the first place?
Comment 4 Dwayne Bailey 2009-02-18 14:56:23 UTC 
(In reply to comment #3)
> (In reply to comment #1)
> > Thanks for reporting this.  Darn how did I miss this one, was cautious about
> > this release.
> 
> More importantly... why does bodhi allow pushing a package with broken deps in
> the first place?

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