Bug 486083

Summary: Package Translate Toolkit 1.3.0 for F10 (Virtaal 0.3.0 in F10 had broken deps on 1.3.0)
Product: [Fedora] Fedora Reporter: Hans Ulrich Niedermann <rhbugs>
Component: translate-toolkitAssignee: Roozbeh Pournader <roozbeh>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 10CC: dwayne, i18n-bugs, roozbeh
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-02-21 11:18:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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