[Bug 260751] Re: new upstream version (4.0.9)
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). -- new upstream version (4.0.9) https://bugs.launchpad.net/bugs/260751 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 260751] Re: new upstream version (4.0.9)
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.0 +0200 +++ java-gnome-4.0.9/src/defs/PangoContext.defs 2008-10-13 11:36:36.0 +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) -- new upstream version (4.0.9) https://bugs.launchpad.net/bugs/260751 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 260751] Re: 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. -- new upstream version (4.0.9) https://bugs.launchpad.net/bugs/260751 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 260751] Re: new upstream version (4.0.9)
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 -- new upstream version (4.0.9) https://bugs.launchpad.net/bugs/260751 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 217615] Re: Alternate console screens during installation are working only once
solved with 8.04 rc -- Alternate console screens during installation are working only once https://bugs.launchpad.net/bugs/217615 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 217615] [NEW] Alternate console screens during installation are working only once
Public bug reported: 8.04 Beta, 64bit server ( 2.6.24-16-server #1 SMP Thu Apr 10 13:15:38 UTC 2008 x86_64 GNU/Linux) If you try to switch to an alternate console with alt-f2 during installation does this work only one time. If you switch back to the installation screen, you can't open the alternate console again with alt-f2. ** Affects: ubuntu Importance: Undecided Status: New -- Alternate console screens during installation are working only once https://bugs.launchpad.net/bugs/217615 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs