After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 712479 - Functions that accept arrays of pointers improperly bound
Functions that accept arrays of pointers improperly bound
Status: RESOLVED FIXED
Product: gexiv2
Classification: Other
Component: bindings
0.6
Other All
: High normal
: ---
Assigned To: Jim Nelson
Gexiv2 Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-02-25 11:41 UTC by Jim Nelson
Modified: 2013-05-01 06:35 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Lindsay 2013-11-16 14:44:24 UTC


---- Reported by jim@yorba.org 2011-02-25 15:41:00 -0800 ----

Original Redmine bug id: 3264
Original URL: http://redmine.yorba.org/issues/3264
Searchable id: yorba-bug-3264
Original author: Jim Nelson
Original description:

The following functions are improperly bound in gexiv2.vapi:

  * gexiv2_set_tag_multiple
  * gexiv2_set_iptc_tag_multiple
  * gexiv2_set_xmp_tag_multiple
  * gexiv2_set_keywords

The problem is with vapigen prior to 0.11. In those versions, the
array_null_terminated CCode is not added to the VAPI, even if specified in the
.metadata file. With Vala 0.11.6 (and possibly earlier versions of 0.11) this
is fixed and the CCode is added.

Since we distribute the VAPI file with the tarball, the solution is simply to
install 0.11.6, generate the VAPI, and commit.

Related issues:
related to gexiv2 - Feature #6169: Build and distribute .gir for Vala, not
VAPI (Open)
related to gexiv2 - Feature #6170: Solidify gexiv2 API (Fixed)



---- Additional Comments From valencia-maint@gnome.bugs 2013-05-01 11:35:00 -0700 ----

### History

####

#1

Updated by Jim Nelson over 2 years ago

This was discovered while working on #3257.

####

#2

Updated by Jim Nelson over 2 years ago

  * **Target version** set to _0.9_

####

#3

Updated by Adam Dingle over 2 years ago

  * **Target version** deleted (<strike>_0.9_</strike>)

####

#4

Updated by Jim Nelson 11 months ago

  * **Description** updated (diff)
  * **Target version** set to _0.6_

####

#5

Updated by Jim Nelson 11 months ago

  * **Category** set to _bindings_

####

#6

Updated by Jim Nelson 11 months ago

  * **Category** changed from _bindings_ to _24_

####

#7

Updated by Robert Park 11 months ago

Hah, I'm just reading this bug for the first time. When I wrote the
introspection annotations, I was referring very closely to the VAPI, so I can
assure you that any errors in the VAPI got copied verbatim into the
introspection annotations, and indeed this actually explains some of the
funkiness that I uncovered when I was writing the testsuite. So just be aware
of that, and try to fix the introspection annotations as you go ;-)

####

#8

Updated by Jim Nelson 10 months ago

  * **Category** changed from _24_ to _bindings_
  * **Keywords** set to _bite-sized_

####

#9

Updated by Jim Nelson 10 months ago

  * **Tracker** changed from _Bug_ to _Bite-sized_
  * **Status** changed from _Open_ to _5_
  * **Assignee** set to _Jim Nelson_
  * **Resolution** set to _fixed_

#6170 fixed this.

####

#10

Updated by Charles Lindsay 7 months ago

  * **Status** changed from _5_ to _Fixed_



--- Bug imported by chaz@yorba.org 2013-11-16 14:44 UTC  ---

This bug was previously known as _bug_ 3264 at http://redmine.yorba.org/show_bug.cgi?id=3264

Unknown milestone "unknown in product gexiv2. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.