The GIMP package hasn't been updated for several weeks now, and still contains the unstable 2.7.4 development snapshot. GIMP 2.8.0 stable has been released meanwhile. The package should be updated accordingly.
Priority: Normal => HighCC: (none) => sander.lepikHardware: i586 => AllAssignee: bugsquad => shlomif
Hi Frederic, (In reply to comment #0) > The GIMP package hasn't been updated for several weeks now, and still contains > the unstable 2.7.4 development snapshot. GIMP 2.8.0 stable has been released > meanwhile. The package should be updated accordingly. I don't see GIMP-2.8.0-stable on http://www.gimp.org/ - only GIMP-2.8.0-rc1. We may still need to package it though. Regards, -- Shlomi Fish
funda pushed the package in testing, please test
CC: (none) => fundawang
http://www.gimpusers.com/news/00420-gimp-2-8-finally-released - well, there now is a stable release too.
(In reply to comment #1) > I don't see GIMP-2.8.0-stable on http://www.gimp.org/ - only GIMP-2.8.0-rc1. Hum, 2.8.0 is mentioned on gimp.org.
Just wondering: why is gimp-2.8.0-1.mga2 in core/updates_testing instead of core/release as most other updated packages?
CC: (none) => bogusman222
(In reply to comment #5) > Just wondering: why is gimp-2.8.0-1.mga2 in core/updates_testing instead of > core/release as most other updated packages? Because we're deep inside version freeze and only bugfixes or security updates will be allowed through the freeze? Only possibility currently for packagers to submit new versions themselves is into updates_testing.
CC: (none) => doktor5000
(In reply to comment #6) > Because we're deep inside version freeze and only bugfixes or security updates > will be allowed through the freeze? Well, I think there should be no hesitation between a development snapshot and a stable release. A development snapshot is of beta quality and has much less testing coverage than a stable release. Also, a standard bugfix or some code cleanup between 2.7.4 and 2.8.0 could as well fix or prevent a future security bug, and if you are still running 2.7.4, you may be affected by this security bug while 2.8.0 is not affected.
Testing x86_64 in vbox The following 4 packages are going to be installed: - gimp-2.8.0-1.mga2.x86_64 - lib64babl0.1_0-0.1.10-1.mga2.x86_64 - lib64gegl0.2_0-0.2.0-2.mga2.x86_64 - lib64gimp2.0_0-2.8.0-1.mga2.x86_64 Performed various gegl operations, applied various filters, drew some boxes etc. All seems Ok.
In the newsgroup alt.os.linux.mageia, a Maurice Batey is reporting a bug in Gimp 2.7.4 in the action of the Text box. If I understand his description correctly, when entering text it appears in the image partition, but not in the text box itself. He reports that this particular bug is supposed to be fixed in Gimp 2.8.0. If you didn't have enough reason already to add the newer Gimp to the RC, this should help.
CC: (none) => andrewsfarm
I have tested the gimp 2.8.0 on a 64bit mag2 box and played around with 5/6 of the gegl effects on a 5.5 mb .jpg file. Worked ok.
CC: (none) => led43john
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
gimp-2.8.0-1.mga2 is available in Mageia 2.
Keywords: NEEDINFO => (none)Status: NEW => RESOLVEDResolution: (none) => FIXED
Version: Cauldron => 2