new upstream version (4.0.9)

I've uploaded 4.0.9 packages to my PPA: https://launchpad.net/~hannesw/+archive

What can we do to push this ahead? Having 4.0.7 in Universe is rather disconcerting, since none of the online tutorials work with that version anymore.

Well, given:

  Maintainer: Ubuntu MOTU Developers <email address hidden>

I suppose we have to somehow get the attention of MOTU (https://wiki.ubuntu.com/MOTU). I believe that the process is the one described here: https://wiki.edubuntu.org/SponsorshipProcess, and we do have Ubuntu Sponsors for Universe subscribed, which is the documented process.

I have nominated this bug for Intrepid and Jaunty. Anyone believe that it should be a backport for Hardy? I'd say yes, but have not checked the dependencies closely enough to be sure.

Hannes, I've never built a PPA package. If you'll be so kind as to tell me what you did to build this for Intrepid, I could make a Jaunty build of it my first PPA. I've reviewed https://help.launchpad.net/PPA101, but having your steps as a concrete example would be helpful. :-)

I have contacted the debian maintainers of this package, and they said they were going to commit the new package. Since ubuntu is using the unmodified debian package, my understanding is that it will flow into ubuntu universe automatically eventually - is this right?

Noel, the basic steps to update the package were:
- Fetched the source via apt-get source java-gnome
- Got the new upstream tar.gz file
- Transfer the debian info using uupdate as described in chapter 9.2 in http://www.debian.org/doc/manuals/maint-guide/index.html
- Make a few tweaks like removing unnecessary patch
- Build the package using debuild -S
- upload the source package using dput

I don't think you have to do any of the patching, you should be able to build for other versions using the source package from my archive. You need to have the development packages set up and configured - the Learning MOTU videos on youtube are a great resource for that, and for the uploading part there's https://help.launchpad.net/Packaging/PPA

A few things:
 - can you please forward the changes to Debian too? https://wiki.ubuntu.com/Bugs/Debian
 - Bumping the Standards-Version for packages that are not maintained in Ubuntu is unnecessary: it's a change that has no effect and needs to be merged manually the next time again
 - Unnecessary to mention the DebianMaintainerField change, we need to do it each time we change from Debian anyway.
 - debian/02_dont_export_pango_backend_funcs.diff: you drop the whole change (would have been easier to just drop it from debian/patches/series), but to me it seems like the patch needs updating instead of dropping - the only thing that changed upstream was the commenting of get_shape_engine_type.

I contacted the debian packagers and they already committed the changes to svn:

http://svn.debian.org/viewsvn/pkg-java/trunk/java-gnome/

I'm not too familiar with the debian release process, but from my understanding it should eventually be uploaded. Is that right?

Regarding the pango patch: I just checked again, and all 3 declarations the patch removes are commented out in 4.0.9: "get_shape_engine_type" in src/defs/PangoFontMap.defs and "pango_context_new" and "add_fong_map" in src/defs/PangoContext.defs. I didn't know that I should have just removed the patch from debian/patches/series and keep the patch itself in place. Is that the usual way of handling obsolete patches? I'm just a beginner at this, always glad to learn something new.

I guess the other issues relate to Alessandro's patch (which I only discovered after I did my own version).

1) Best to just ask when they're going to upload it - we can either sync it, or add a necessary patch on top of it.

2) Regarding the Pango patch - this is how I came to my conclusion - let me know if I'm wrong.
$ diff -u java-gnome-4.0.{7,9}/src/defs/PangoFontMap.defs
--- java-gnome-4.0.7/src/defs/PangoFontMap.defs 2008-04-30 04:52:30.000000000 +0200
+++ java-gnome-4.0.9/src/defs/PangoFontMap.defs 2008-10-13 11:36:36.000000000 +0200
@@ -36,11 +36,11 @@
   )
 )

-(define-method get_shape_engine_type
- (of-object "PangoFontMap")
- (c-name "pango_font_map_get_shape_engine_type")
- (return-type "const-char*")
-)
+;;(define-method get_shape_engine_type
+;; (of-object "PangoFontMap")
+;; (c-name "pango_font_map_get_shape_engine_type")
+;; (return-type "const-char*")
+;;)

 (define-virtual load_font
   (of-object "PangoFontMap")
$

The remaining changes in that patch are in a different file, src/defs/PangoContext.defs:

diff -u java-gnome-4.0.{7,9}/src/defs/PangoContext.defs
--- java-gnome-4.0.7/src/defs/PangoContext.defs 2008-04-30 04:52:30.000000000 +0200
+++ java-gnome-4.0.9/src/defs/PangoContext.defs 2008-10-13 11:36:36.000000000 +0200
@@ -5,21 +5,26 @@
   (gtype-id "PANGO_TYPE_CONTEXT")
 )

-(define-function pango_context_new
- (is-constructor-of "PangoContext")
- (c-name "pango_context_new")
- (caller-owns-return #t)
- (return-type "PangoContext*")
-)
-
-(define-method add_font_map
- (of-object "PangoContext")
- (c-name "pango_context_set_font_map")
- (return-type "none")
- (parameters
- '("PangoFontMap*" "font_map")
- )
-)
+;;This function is only used when constructing a new Pango backend which
+;;applications shouldn't do, and relies on a special #define to be present in
+;;the C API. This is not planned to be exposed in java-gnome so it is
+;;commented out and fixes bug #528282
+
+;;(define-function pango_context_new
+;; (is-constructor-of "PangoContext")
+;; (c-name "pango_context_new")
+;; (caller-owns-return #t)
+;; (return-type "PangoContext*")
+;;)
+
+;;(define-method add_font_map
+;; (of-object "PangoContext")
+;; (c-name "pango_context_set_font_map")
+;; (return-type "none")
+;; (parameters
+;; '("PangoFontMap*" "font_map")
+;; )
+;;)

 (define-method get_font_map
   (of-object "PangoContext")

Alright - thanks. Let me take a look at the package again.

Maybe you can forward the watch file to Debian and please file a sync request once it's been merged and the new version entered Debian?

https://wiki.ubuntu.com/SyncRequestProcess

This bug was fixed in the package java-gnome - 4.0.9-0ubuntu1

---------------
java-gnome (4.0.9-0ubuntu1) jaunty; urgency=low

  * New upstream release (LP: #260751)
  * disable debian/02_dont_export_pango_backend_funcs.diff because PangoFontMap.defs
    there isn't in /src/defs in this new version
  * add debian/watch file

 -- Alessandro Ghersi <email address hidden> Tue, 25 Nov 2008 04:04:03 +0100