On Fri, Mar 07, 2008, Loïc Minier wrote:
>  crown-beach-config: normal update process, we have to update to the new
>  version; warning: latest version of the source is in hardy, not in the
>  ppa[1]

 Latest tarball wasn't zipped; I zipped it under the name 0.33~repack
 and uploaded to hardy and ppa (uupdate was enough here, but I also did
 packaging fixes).

>  gstreamer-dbus-media-service
>  moblin-media

 Waiting for the sun to shine more on a libmokoui port of moblin-media.

>  hildon-theme-mobile-basic: we have to update to the new version and
>  check we didn't have custom changes in the tarball

 Done and sent detailed notes to Rusty.

>  marquee-plugins: we have a 0.22 tarball in the ppa (!) probably with
>  custom changes in the tarball; releasing a dummy 0.23 upstream would be
>  nice, or we can remove from ppa and reupload

 0.4 in gutsy/hardy wasn't the same as 0.4 upstream; gutsy received an
 incomplete 0.4 and had the following changes by Matthew Garrett in the
 changelog:
  * Remove conffile fiddling
  * Upload to Ubuntu
 also, the diff showed that it had files generated by autogen (e.g.
 configure, config.sub etc.).  The above changes consisted of dropping
 contents of debian/marquee-plugins.postinst (except DEBHELPER stanza;
 but useless anyway).

 it also had this change:
--- src/nav-next-app-plugin.c 2008-04-09 17:41:03.000000000 +0200
+++ src/nav-next-app-plugin.c       2007-10-15 05:46:07.000000000 +0200
@@ -52,7 +52,7 @@ static void on_clicked (GtkWidget *butto
         {
             application = HD_WM_APPLICATION(iter->data);
             window = hd_wm_application_get_active_window (application);
-            g_warning ("app: %x; window: %x.\n", (unsigned int)application, 
(int)window);
+            g_warning ("app: %p; window: %p.\n", application, window);
             if (window == activewindow) {
                 new_entry = g_list_previous (iter);
                 if (!new_entry) {

 which is a 64-bits portability fix which doesn't apply to HEAD
 anymore (I grepped for %x).

 The version in the ppa didn't have the changes by Matthew Garrett and
 didn't match gaston's 0.22, nor did the 0.21 match, nor the 0.20; only
 the 0.19 did.  Reviewing the 0.19 -> 0.22 changes in the changelog from
 the ppa shows:

marquee-plugins (0.22) hardy; urgency=low

  * Use Type=default rather than Type=link in the .desktop files.

 -- Steve Kowalik <[EMAIL PROTECTED]>  Wed, 27 Feb 2008 17:48:56 +1100

marquee-plugins (0.21) hardy; urgency=low

  * Removed -Werror flag temporarily until rollback.

 -- Bob Spencer <[EMAIL PROTECTED]>  Thu, 21 Feb 2008 15:02:08 -0800

marquee-plugins (0.20) hardy; urgency=low

  * Removed calls to screen_changed until hildon-desktop update
    to support it (in PPA).  Re-pushing to PPA

 -- Bob Spencer <[EMAIL PROTECTED]>  Thu, 21 Feb 2008 12:20:58 -0800

 The diff shows the above changes as:
 - dropping -Werror from configure.ac
 - this change in src/clock-plugin.c:
-  item_class->screen_changed = clock_plugin_screen_changed;
+  //item_class->screen_changed = clock_plugin_screen_changed;
 - similar changes in src/close-app-plugin.c,
   src/drop-down-menu-plugin.c, src/showhome-plugin.c
 - this change in src/clock-plugin.desktop.in, src/close-app.desktop.in,
   src/drop-down-menu.desktop.in, src/dummy-panel.desktop.in,
   src/showhome-plugin.desktop.in:
-Type=Link
+Type=default

 I then reviewed the gaston-v0.19 -> gaston-v0.22 diff and saw that the
 Type=default changes were partially merged (except in dummy-panel).

 I took the latest gaston packaging and applied it on top of the
 released tarball, merged the sed from Matthew's 0.4 upload; extracted
 the other changes as patches, added a patch system.

 I think the current approach of shipping only the source files in the
 tarball is incorrect and that autogen should be run when making
 tarballs (e.g. with "make distcheck").

 It's pending upload though as it's crashing with some memory corruption
 ATM.

>  mobile-basic-flash: we have a 0.35 tarball in the ppa (!) probably with
>  custom changes in the tarball; releasing a dummy 0.36 upstream would be
>  nice, or we can remove from ppa and reupload

 I'll need a working flash file to continue this update.

>  moblin-keyboard-manager: we already have a 0.51 tarball in the ppa
>  probably with custom changes in the tarball, we will have a problem
>  replacing it with a different one; releasing a dummy 0.52 upstream
>  would be nice, or we can remove from ppa and reupload

 TBD.

>  moblin-media-browser-plugin

 Not really looking into this, I prefer working on midbrowser first.

>  ppm

 TBD.

>  samsung-q1-ultra-config: we need to update to the new version and check
>  we didn't have custom changes in the tarball

 TBD.

>  ume-config-common: we already have a 0.10+repack tarball in hardy
>  created from the 0.10 release and repacked to drop the .git and
>  debian/, we will have a problem replacing it with a smaller version;
>  releasing a dummy 0.11 upstream would be nice, or we can epoch the
>  version but that's painful.

 Done; similar to crown-beach-config; used 0.10+upstream as upstream
 version to replace the tarball.


 I'm taking help for the remaining modules; also I'm not sure the
 tarball-released modules are up-to-date, I'm happy to help shape
 moblin.org's scripts to achieve this.  Finally, we need to move to
 tarballs for the other modules as well.

-- 
Loïc Minier

-- 
Ubuntu-mobile mailing list
[email protected]
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile

Reply via email to