[Bug 364630] Re: [FFe] Clutter 0.8 -> 1.0 transition

[Andrew Starr-Bochicchio]

Re-subscribing ubuntu-archive. geeqie 1.0~beta2-2 in Debian unstable has
been patched to build correctly against Clutter 1.0 and libchamplain
0.4. Please sync.

http://git.debian.org/?p=collab-
maint/geeqie.git;a=blob;f=debian/patches/clutter-1.0.patch;h=7e2d2bf3ba70e7e7585cc1da831320ae1985a43a;hb=HEAD

http://git.debian.org/?p=collab-
maint/geeqie.git;a=blob;f=debian/patches/champlain-0.4.patch;h=4a80d025e2b856137e86bfde9292e1a3eedc93bd;hb=HEAD

I was trying to attach a successful build log but LP seems to hate me
right now. You'll just have to believe me. ;-)

** Description changed:

  In order to get the archive into a consistent state, we should complete
  the transition from Clutter 0.8 to 1.0
  
  Remaining reverse depends on 0.8:
  
  libclutter-0.8-0
  Reverse Depends:
    python-clutter
    liblua5.1-gnome-0
    libclutter-perl
    libclutter-gst-0.8-0
    libclutter-cairo-0.8-0
    libchamplain-gtk-0.3-1
    libchamplain-0.3-1
    geeqie
    libclutter-0.8-dev
    libclutter-0.8-dbg
    gobject-introspection-repository
  
  Actions needed:
  
- pyclutter - sync 1.0.0-1 from unstable
- libchamplain - sync 0.4.0-1 from unstable
+ pyclutter - sync 1.0.0-1 from unstable DONE
+ libchamplain - sync 0.4.0-1 from unstable DONE
+ geeqie - sync  1.0~beta2-2 from unstable
  
  clutter-gst - upgrade to new release (package ready for upload) DONE
  clutter-perl - upgrade to new release (depends on clutter-gst)
  
- lua-gtk - patch in upstream CVS
- 
- geeqie - make sure it works with new libchamplain / clutter
+ lua-gtk - patch in upstream CVS DONE
  
  gir-repository - further investigation needed
  
  clutter-cairo - deprecated upstream, can be remove from archive once
  transition is complete
  
  
  ----------------------
  Original report:
  
  
  "The Python bindings for the Clutter core and integration libraries have been released. this release of the Python bindings map the Clutter 1.0 API cycle."
  http://www.clutter-project.org/blog/?p=82
  
  http://www.clutter-
  project.org/sources/pyclutter/1.0/pyclutter-1.0.0.tar.gz
  
  Release notes
  
      * This is the first stable release of the 1.* cycle
      * Requires Clutter core >= 1.0.0
      * The bindings for Clutter-GStreamer and Clutter-GTK have been dropped from the PyClutter module, and they will be shipped separately as PyClutter-GStreamer (pyclutter-gst) and PyClutter-GTK (pyclutter-gtk). The new modules are already available as separate repositories.
  
  Changes from 0.8
  
      * Require Clutter core >= 1.0.0
      * Provide better bindings for the Cogl API
      * Add more examples ported from the clutter core interactive tests
      * Dropped the in-tree bindings of clutter-gtk and clutter-gst: you will have to install pyclutter-gtk and pyclutter-gst respectively to be able to import cluttergtk and cluttergst.
      * Allow accessing child properties for clutter.Container
      * Allow iterating over the children of a clutter.Container using the native Python iterator support
      * Allow creating custom ChildMeta classes from Python
      * Mark the classes removed from upstream Clutter as “deprecated”; trying to instantiate one of the deprecated classes will result in the equivalent class in Clutter 1.0 to be created and a warning printed out on the console
      * Override the __repr__ and __str__ methods for clutter.Color: the former will print out a wtring that can be used through eval() to create a copy of the color; the latter will print out the hexadecimal representation of the color.
      * Override the __str__ method of clutter.Event: it will now print more information on the event (type, time, source actor) and per-event type fields (button, key, related actor, etc.).
      * Deprecated clutter.stage_get_default() in favour of an optional argument to clutter.Stage(); calling:
  
            >>> clutter.Stage(default=True)
  
        will return the default Stage singleton; the default argument is optional and it defaults to False.
      * Allow passing the following values to methods accepting a clutter.Color:
            o a clutter.Color (e.g.: clutter.Color(255, 0, 0, 255))
            o a 4-tuple of RGBA values (e.g.: (255, 0, 0, 255))
            o a hexadecimal representation of the color (e.g.: ‘#ff0000ff’)

-- 
[FFe] Clutter 0.8 -> 1.0 transition
https://bugs.launchpad.net/bugs/364630
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs