lsb

LSB5 import lets glib usage of "struct _Foo" creep in where should be "Foo"

Bug #1329514 reported by Jeff Johnson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lsb
Fix Committed
Medium
Unassigned
Mandriva
Fix Released
Medium

Bug Description

In the imports for LSB 5.0, a usage of _GError has crept is that is not
like upstream, "const struct _GError *" when upstream in these circumstances
uses "const GError *". At the moment, this appears only in function parameters.

There's a place in the DB where this crept in:

INSERT INTO `Type` VALUES (40924,'const _GError
*','Pointer',0,'','No','No','No',NULL,'libglib-2.0',0);

where the existing type define would have been fine:

INSERT INTO `Type` VALUES (11419,'const GError
*','Pointer',609,'','No','No','Yes',NULL,'libglib-2.0',0);

Usage appears only for 5.0, the fix would be simple and requires no errata:

UPDATE Parameter SET Ptype=11491 WHERE Ptype=40924;

there should be five hits.

probably best to remove type 40924 at the same time.

Here's one example;

    extern void g_simple_async_result_set_from_error(GSimpleAsyncResult *
simple,
                                                     const struct _GError
*error);
++ should be
void g_simple_async_result_set_from_error (GSimpleAsyncResult
    *simple,
                                                            const GError
    *error);

Tags: spec gtk3 zclose
Changed in mandriva:
importance: Unknown → Medium
status: Unknown → In Progress
Jeff Johnson (n3npq)
tags: added: zclose
tags: added: gtk3
Changed in mandriva:
status: In Progress → Fix Released
Jeff Johnson (n3npq)
Changed in lsb:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.