[FFe] Update glom to 1.12.1

You're not working on this are you huats? I've started updating some of it's dependencies now, so if you haven't already started work on it, then I will take this one :)

This will need a FFe now. Bumping importance also, because the current version is no longer installable due to missing dependencies, and it will no longer rebuild as pygda3 has gone from the archive. It is not really possible to reintroduce pygda3 as our version of gnome-python-extras is too new, and only provides pygda4. The current version of glom will not build against pygda4, but the new upstream version will

Right, there is a preliminary build of 1.11.2 in my PPA now (I can't upload yet until I have its dependencies in the archive sorted out and I've worked on the FF exception too).

Murray - I notice the libglom API version changed from 1.0 to 1.12 between 1.11.0 and 1.11.2, but the pkg-config file is still named glom-1.0.pc. Should this be renamed now, as it doesn't match the library name or the install location of the header files? If so, then I can rename this at build-time for now

The link to my PPA might help - https://edge.launchpad.net/~chrisccoulson/+archive/ppa

> Murray - I notice the libglom API version changed from 1.0 to 1.12 between 1.11.0 and 1.11.2, but the pkg-config file is
> still named glom-1.0.pc.

Thanks for mentioning that. I've just fixed it in git and it will be in a new tarball in a day or two.

Thanks for packaging - I hope we can get this into karmic.

Murray - thanks. This will probably have to wait until after Beta release now (as Beta Freeze starts tomorrow, and we still don't have pygda4 in the archive).

I'm having an issue with preliminary tests of the package though. When I create a new empty document, I get an error "Glom could not connect to the database server. Maybe you entered an incorrect user name or password, or maybe the postgres database server is not running". I've not had any time to look at this yet, but I just wondered if you had any idea off the top of your head what might be wrong (perhaps I've done something wrong with the build).

Thanks

> I create a new empty document, I get an error "Glom could not connect to the database server.

Is this with self-hosting (the default)? We've had some issue related to timing, that I think I know how to fix for self-hosting at least. Are your packages up for me to test?

Murray - the packages are in my PPA: https://launchpad.net/~chrisccoulson/+archive/ppa/+packages . I would appreciate it if you can try them out as I don't have much time to work on any issues at the moment, and there won't be a lot of time to fix issues before the final release once the feature-freeze exception is granted.

Thanks

OK. I'll try them, though there will be some delay while I update to Karmic in general.

If you are using PostgreSQL 8.4 then you probably need this small patch, until I have fixed it properly:
https://bugzilla.gnome.org/show_bug.cgi?id=595608

On Thu, 2009-09-24 at 14:26 +0000, Murray Cumming wrote:
> If you are using PostgreSQL 8.4 then you probably need this small patch, until I have fixed it properly:
> https://bugzilla.gnome.org/show_bug.cgi?id=595608
>
>
> ** Bug watch added: GNOME Bug Tracker #595608
> http://bugzilla.gnome.org/show_bug.cgi?id=595608
>
Murray,

Thanks - I've just uploaded a new version in my PPA with commit
27ae914f8856f97490573ae18ca3a464ebf8f5d1, and it seems to be working
better now.

This was fixed in upstream Glom in 1.12.0.
1.12.1, released today, even has a few more fixes, so I hope it gets into Karmic.

Sebastien, your call.

ack from me

IRC log on 5/10:

chrisccoulson: seb128 - would you mind ACK'ing bug 391664? (i think sistpoty subscribed you to it)
ubottu: Launchpad bug 391664 in glom "[FFe] Update glom to 1.12.1" [Medium,Triaged] https://launchpad.net/bugs/391664
seb128: there is a newer version upstream now
seb128: but update ack from me it was probably in the middle of the thousand weekend emails
chrisccoulson: i didn't realise there was a new upstream version now
chrisccoulson: i only packaged 1.12.1 at the weekend ;)
seb128: ok, feel free to upload this one or to do the new update

I'll get this uploaded once bug 406077 is closed

This bug was fixed in the package glom - 1.12.2-0ubuntu1

---------------
glom (1.12.2-0ubuntu1) karmic; urgency=low

  * New upstream version:
    - FFE LP: #391664
  * debian/control:
    - Bump python-gnome2-extras-dev build-dep to >= 2.25.3.
    - Bump libgdamm3.0-dev build-dep to libgdamm4.0-dev >= 3.99.14.
    - Change libgda3-dev build-dep to libgda-4.0-dev.
    - Change libgda3-postgres dependency to libgda-4.0-postgres.
    - Bump libgtkmm-2.4-dev build-dep to >= 2.14.
    - Add build-dep on libgconfmm-2.6-dev.
    - Bump libgoocanvasmm-dev build-dep to >= 0.14.0.
    - Remove build-dep on libbakery-2.6-dev.
    - Bump postgresql-8.3 dependency to postgresql-8.4.
    - Change scrollkeeper build-dep to rarian-compat.
    - Rename libglom{0,-dev} -> libglom-1.12-{0,dev}. Upstream include
      APIVER in the library name now.
  * debian/rules:
    - Update --with-postgres-utils configure flag to point to the new
      path.
    - Drop deprecated --disable-scrollkeeper configure flag.
    - Update DEB_SHLIBDEPS_INCLUDE with new libglom-1.12-0 package name.
    - Don't include /usr/share/cdbs/1/rules/simple-patchsys.mk - there
      are currently no patches.
  * debian/libglom-1.12-0.install:
    - Updated for new version.
  * debian/libglom-1.12-dev.install:
    - Install pc and header files.
  * debian/glom-doc.install:
    - Updated for new version.
  * debian/glom.install:
    - Updated for new version.
  * Fix debian/watch.
  * Dropped obsolete 10-distro-install-postgres-change.patch.
  * Built against latest libgoocanvasmm (LP: #428445).
  * Also closes LP: #230007, LP: #393229, LP: #393231, LP: #394507,
    LP: #394887, LP: #394894, LP: #397409, LP: #381563.

 -- Chris Coulson <email address hidden> Fri, 09 Oct 2009 16:50:36 +0100