Sync libgda4 4.0.8-1 (main) from Debian unstable (main)

Current libgda version (4.0.4) included in Karmic and proposed to be included in Lucid, is not stable enough for derived applications. Since Lucid is LTS, no single application could benefit much, from included Libgda 4.0.4.

Libgda 4.0.8 provides many important biugfixes:

 * better BLOBs support for SQLite and MySQL
 * backported information fetching about tables' indexes
 * fixed data corruption problem with GdaDataSelect object
 * lots of bug fixed and memory leaks removed

And also new gir1.0-gda package which is fundamental for derived applications in Gnome, since it provides GObject Introspection support.

libgda4-4 conflicts/replaces has been added in Debian unstable package's control file. As well, as MySQL client and server dependencies.

The package in Ubuntu has Ubuntu specific changes.

Either the Ubuntu changes can be dropped and this sync request should outline the reasons why the package can be synced from Debian.

Or the Ubuntu changes haven't been included in Debian and are still relevant in which case the package should be merged.

See https://wiki.ubuntu.com/UbuntuDevelopment/Merging for more information.

Since the new upstream release is a bug fix only relase there is no need to get a Feature Freeze Exception.

Unsubscribing the sponsor team for now. Resubscribe the team once the relevant information has been provided.

I think I provided all important changes in debian packages already:

# libgda4 (4.0.4-1ubuntu4) lucid; urgency=low

  * rebuild rest of main for armel armv7/thumb2 optimization;
    UbuntuSpec:mobile-lucid-arm-gcc-v7-thumb2

I am not sure what this change is for. At least can not find particular diff for rest of debian files.

# libgda4 (4.0.4-1ubuntu3) karmic; urgency=low

  * Don't run the testsuite on ia64. File #456131 for tracking the issue.

libgda4 (4.0.4-1ubuntu2) karmic; urgency=low

  * debian/rules: Enable test-suite.

Tests are enabled in debian packages. And AFAIK, #456131 is no longer valid.
(Has been fixed in latest bugfix releases).

# libgda4 (4.0.4-1ubuntu1) karmic; urgency=low

  * Re-base on Debian unstable (LP: #432169), remaining changes:
    - debian/control:
      + Change MySQL build-dep to 5.1 in main.
      + Add various conflicts/replaces to handle new binary package names.
      + Build-depend on rarian-compat rather than scrollkeeper.

I added MySQL 5.1 (both client and server) in debian packages already.
Packages naming conflicts/replaces has been added as well.
I do not think there's any issue with scrollkeeper being a build dependency.

Anyway, I am not Ubuntu maintainer and can not decide whether package should be synced or merged.
I'll be more than glad to help/do one of those as long as there's clear feedback from Ubuntu maintainer.
I think I provided enough changes in debian unstable packages to get package synced, with Ubuntu changes being dropped.

This can't be sync'd. The Debian and Ubuntu packages had different binary package names in the past, and in Karmic we adopted the Debian naming. This means that there will be a delta to keep the conflicts/replaces in the Ubuntu packaging, which we can't drop until next cycle

I added those conflicts/replaces in debian packages. So from this point of view, nothing will change for ubuntu packages.
http://svn.debian.org/viewsvn/pkg-gnome/packages/unstable/libgda4/debian/control.in?r1=23091&r2=23240
Changes are included in 4.0.8.

ack for sync from unstable, rdepends check out, builds fine in lucid and all ubuntu deltas have be moved upstream.

* Test builds done for i386 and x86_64
* Manually checked all existing Ubuntu deltas to ensure they were adopted upstream
* Manually checked rdepends and nothing will be effected by a bugfix release.
* Lintian clean with the exception of a recommendation to use quilt patch system ( no reason to change this late in the cycle )

Please sync

Sponsor ack. Current version we have in Lucid fails rebuild test. We should have this before final.

I missed a FTB on x86_64, please hold off on this sync

is that sync still being worked?

Libgda 4.0.9 has been released recently, which fixes FTB on x86_64. I can file new sync request, if required.

unsubscribing 537379 until confirmed

subscribing ubuntu-sponsors

libgda4 4.0.9-1 builds on maverick (log attached). We need a freeze exception. Please provide all other information described on [1] and resubscribe ubuntu-sponsors once the exception is granted.

[1] https://wiki.ubuntu.com/FreezeExceptionProcess

FFe granted, please go ahead.

This bug was fixed in the package libgda4 - 4.0.9-1

---------------
libgda4 (4.0.9-1) unstable; urgency=low

  [ Emilio Pozuelo Monfort ]
  * debian/control.in:
    - Let gir1.0-gda-4.0 depend on ${gir:Depends}.
    - Build depend on gir1.0-freedesktop and gir1.0-glib-2.0.
  * debian/rules:
    - Call dh_girepository for gir1.0-gda-4.0.
  * debian/rules,
    debian/source/format:
    - Switch to source format 3.0 (quilt).

  [ Piotr Pokora ]
  * New upstream. Closes: #577711

libgda4 (4.0.8-1) unstable; urgency=low

  [ Emilio Pozuelo Monfort ]
  * debian/rules:
    - Run the test suite during the build, but don't make it fatal (yet).

  [ Piotr Pokora ]
  * New upstream
  * Build depend on libmysqlclient-dev package.
  * Added libgda4 possible conflicts (also added to Replaces for save updates).
  * New gir1.0-gda-4.0 package
  * Dev package suggests doc one

libgda4 (4.0.7-1) unstable; urgency=low

  * New upstream
  * Removed libgda3-doc suggested package

libgda4 (4.0.6-1) unstable; urgency=low

  [ Emilio Pozuelo Monfort ]
  * Build depend on libreadline-dev rather than libreadline5-dev.
    Closes: #553798.

  [ Josselin Mouette ]
  * Explicitly disable java.

  [ Piotr Pokora ]
  * New upstream release
  * Removed duplicated libsqlite3-dev build dependency

  [ Emilio Pozuelo Monfort ]
  * Standards-Version is 3.8.4, no changes needed.
 -- Piotr Pokora <email address hidden> Fri, 16 Jul 2010 23:37:27 +0200