Bug 7239 - Update validation request - libgdiplus
Summary: Update validation request - libgdiplus
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: has_procedure mga2-64-OK mga2-32-OK
Keywords: validated_update
Depends on:
Blocks: 5683
  Show dependency tree / graph
 
Reported: 2012-08-29 11:57 CEST by Matteo Pasotti
Modified: 2012-09-04 21:35 CEST (History)
5 users (show)

See Also:
Source RPM: libgdiplus-2.10-3.mga2.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Matteo Pasotti 2012-08-29 11:57:42 CEST 
I have uploaded a patched package of libgdiplus for Mageia 2.

You can easily test this following the gendarme-wizard (provided by the mono-tools package) verifying that all the text labels are displayed correctly.

bug 5683 contains (as attachment) a screenshot of this issue.

Suggested advisory:
========================

Updated libgdiplus package fixes bug 5683 :

Application using System.Windows.Forms (built on/for windows) doens't behave/show correctly on Mageia if libdgiplus is compiled using the pango flag.

References:
https://bugs.mageia.org/show_bug.cgi?id=5683

========================

Updated package in core/updates_testing:
========================
lib(64)gdiplus0-2.10-3.1.mga2

Source RPM: 
libgdiplus-2.10-3.1.mga2.src.rpm
Manuel Hiebel 2012-08-30 00:18:23 CEST

Blocks: (none) => 5683

Comment 1 Eduard Beliaev 2012-08-31 02:22:47 CEST 
I have installed libgdiplus-2.10-3.1.mga2.src.rpm and text labels are not displayed correcly, the same as bug 5683.

Tested on Mageia 2 x86_64.

CC: (none) => ed_rus099

Comment 2 Matteo Pasotti 2012-08-31 11:49:32 CEST 
Can you confirm me that you installed lib64gdiplus0 on Mageia 2 x86_64, please?
Comment 3 Mirko Ghersi 2012-08-31 13:42:31 CEST 
Tested on Mageia 2 x86_64. It works. Thanks

CC: (none) => m.ghersi

Comment 4 claire robinson 2012-08-31 18:21:58 CEST 
Thankyou Mirko. Are you able to test i586 too?

Whiteboard: (none) => has_procedure mga2-64-OK

Comment 5 Eduard Beliaev 2012-09-01 03:50:17 CEST 
(In reply to comment #2)
> Can you confirm me that you installed lib64gdiplus0 on Mageia 2 x86_64, please?

Yes.
$ rpm -qi lib64gdiplus0
Name        : lib64gdiplus0
Version     : 2.10
Release     : 3.mga2
Architecture: x86_64
Install Date: mar 29 may 2012 16:10:49 ART
Group       : System/Libraries
Size        : 411995
License     : MIT
Signature   : RSA/SHA1, vie 23 dic 2011 00:21:11 ART, Key ID b742fa8b80420f66
Source RPM  : libgdiplus-2.10-3.mga2.src.rpm
Build Date  : vie 23 dic 2011 00:18:15 ART
Build Host  : jonund
Relocations : (not relocatable)
Packager    : Mageia Team <http://www.mageia.org>
Vendor      : Mageia.Org
URL         : http://go-mono.com
Summary     : An Open Source implementation of the GDI+ API
Description :
An Open Source implementation of the GDI+ API.
This is part of the Mono project.
Comment 6 Matteo Pasotti 2012-09-01 11:31:11 CEST 
it seems you have installed Release 3.mga2 and not 3.1.mga2 from updates_testing. Can you check, please?
Comment 7 Tolhildan Karker 2012-09-01 15:42:57 CEST 
Tested on MGA2, 32-bits. Works!

CC: (none) => tolhildan_123

Comment 8 Manuel Hiebel 2012-09-01 16:14:19 CEST 
waiting of Eduard to really validated

Whiteboard: has_procedure mga2-64-OK => has_procedure mga2-64-OK mga2-32-OK

Comment 9 Eduard Beliaev 2012-09-02 02:49:41 CEST 
Yes, it was my mistake, now it is working ok. You can validate the update.
Comment 10 Manuel Hiebel 2012-09-02 12:53:27 CEST 
Update validated.

See comment 0 for the advisory and SRPM

Could sysadmin please push from core/updates_testing to core/updates

Thankyou!

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Comment 11 Thomas Backlund 2012-09-04 21:35:39 CEST 
Update pushed:
https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0182

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.