[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#600210: marked as done (Freeze Exception: libgda4)

Your message dated Mon, 25 Oct 2010 20:44:41 +0100
with message-id <1288035881.28180.792.camel@hathi.jungle.funky-badger.org>
and subject line Re: Bug#600210: Freeze Exception: libgda4
has caused the Debian Bug report #600210,
regarding Freeze Exception: libgda4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

600210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600210
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: freeze-exception

Please consider freeze exception for libgda4 package.
Recent, maintenance release fixes critical GObject Introspection issue.
Without this release, any derived application or library breaks to build with GObject Introspection enabled.

Debian changelog for 4.0.12-1

libgda4 (4.0.12-1) unstable; urgency=low

  * New upstream release.

 -- Josselin Mouette <joss@debian.org>  Tue, 12 Oct 2010 18:58:26 +0200

Upstream changelog:



--- End Message ---
--- Begin Message ---
On Mon, 2010-10-25 at 21:01 +0200, Piotr Pokora wrote:
> On 25.10.2010 20:36, Adam D. Barratt wrote:
> >>> Which of the fixes mentioned in upstream's changelog does the above
> >>> refer to?
> >>
> >> * libgda/gda-debug-macros.h, libgda/gda-transaction-status.c: Removed
> >> 	internal debug macros
> >
> > Both of those changes are to code which is in "#ifdef GDA_DEBUG" blocks.
> > Surely not everything builds with GDA_DEBUG turned on?
> http://git.gnome.org/browse/libgda/commit/?h=LIBGDA_4.0&id=a7a073f2bdb4d02faa876388fc4e7dd257259d90

Thanks, although as I said I'd already worked out what the changes were.
As the git commit just includes those changes and the same message as
the changelog, it wasn't very helpful. :-/

Some Googling suggests
http://osdir.com/ml/gnome-db-list/2010-02/msg00000.html might be more
relevant, although that doesn't explain why the issue wasn't fixed
rather than the constants removed.

> It's not about building or code itself.
> g-ir-scanner (and friends) generates GIR files, parsing the code.
> Part of #ifdef has been removed because of obvious g-ir-xyz tool issue.

It might be obvious if you're familiar with GIR.  When you're not, it's
very much not obvious.

In any case, unblocked.



--- End Message ---

Reply to: