Bug 5751

Summary: GIMP-2.8.0-1 from Mageia Core Updates Testing requires BABL version 0.1.10 or later, it looks like cauldron only has 0.1.6.
Product: Mageia Reporter: Italo Ramirez <gualadrake>
Component: RPM PackagesAssignee: Funda Wang <fundawang>
Status: RESOLVED INVALID QA Contact:
Severity: major    
Priority: Normal    
Version: Cauldron   
Target Milestone: Mageia 2   
Hardware: x86_64   
OS: Linux   
URL: http://imgh.us/MGA2Beta3_Gimp-2.8.no.runing.png
Whiteboard:
Source RPM: gimp-2.8.0-1.mga2.src.rpm CVE:
Status comment:

Description Italo Ramirez 2012-05-04 19:17:56 CEST 
Description of problem: GIMP-2.8.0-1 from Mageia Core Updates Testing not runing, it requires BABL version 0.1.10 or later.


Version-Release number of selected component (if applicable):  GIMP version 2.8.0-1 (unificated windows)


How reproducible: installing http://mirror.yandex.ru/mageia/distrib/cauldron/x86_64/media/core/updates_testing/gimp-2.8.0-1.mga2.x86_64.rpm and then run it from the menu.
Comment 1 Manuel Hiebel 2012-05-04 19:37:27 CEST 
you should not install a package in this way, better enable the testing, thenurpmi gimp

The needed package is in the same repository, 
ls pub/cauldron/x86_64/media/core/updates_testing/lib64b*
pub/cauldron/x86_64/media/core/updates_testing/lib64babl0.1_0-0.1.10-1.mga2.x86_64.rpm
pub/cauldron/x86_64/media/core/updates_testing/lib64babl0.1-devel-0.1.10-1.mga2.x86_64.rpm

from thomas on irc "but gimp should have versioned requires on it as it really needs it"

Component: Bugzilla => RPM Packages
Version: unspecified => Cauldron
Product: Infrastructure => Mageia
Target Milestone: --- => Mageia 2
Source RPM: http://mirror.yandex.ru/mageia/distrib/cauldron/SRPMS/core/updates_testing/gimp-2.8.0-1.mga2.src.rpm => gimp-2.8.0-1.mga2.src.rpm

Manuel Hiebel 2012-05-04 19:38:00 CEST

CC: mageia-webteam, sysadmin-bugs => (none)
Assignee: sysadmin-bugs => fundawang

Comment 2 Funda Wang 2012-05-04 19:41:24 CEST 
The packages is there, in updates_testing. You should use `urpmi --auto-select` to install those pacakges after enable corresponding repository.

Any, the package is mean to be moved to release after rc.

Status: NEW => RESOLVED
Resolution: (none) => INVALID