3.9.5 release status update (a.k.a. fresh packages required)



Hi all,

I wasn't able to send it this morning (UTC time, of course), sorry, but here is a little update about current status of incoming development release.

Unfortunately we have two relevant issues:
  a) several modules lack a recent tarball release;
  b) some modules fails to build.

Let's start with missing modules... Here is the list of packages unchanged from previous 3.9.4 release:
core:ModemManager:0.7.991:
core:NetworkManager:0.9.8.2:
core:atk:2.9.3:
core:atkmm:2.22.7:
core:cantarell-fonts:0.0.13:
core:caribou:0.4.11:
core:clutter:1.15.2:
core:clutter-gtk:1.4.4:
core:empathy:3.9.4:
core:folks:0.9.3:
core:gcr:3.9.1:
core:gjs:1.37.4:
core:glibmm:2.37.4:
core:gmime:2.6.16:
core:gnome-backgrounds:3.8.1:
core:gnome-bluetooth:3.9.3:
core:gnome-calculator:3.9.4:
core:gnome-dictionary:3.8.0:
core:gnome-disk-utility:3.8.2:
core:gnome-font-viewer:3.8.0:
core:gnome-js-common:0.1.2:
core:gnome-keyring:3.9.1:
core:gnome-menus:3.8.0:
core:gnome-themes-standard:3.9.3:
core:gnome-user-docs:3.8.2:
core:gnome-video-effects:0.4.0:
core:gobject-introspection:1.37.4:
core:grilo:0.2.6:
core:grilo-plugins:0.2.8:
core:gtk+:2.24.20:
core:gtk-doc:1.19:
core:gtk-engines:2.20.2:
core:gupnp-igd:0.2.2:
core:gvfs:1.17.3:
core:json-glib:0.16.0:
core:libchamplain:0.12.4:
core:libcroco:0.6.8:
core:libgdata:0.13.3:
core:libgnome-keyring:3.9.1:
core:libgnomekbd:3.6.0:
core:libgsf:1.14.27:
core:libgtop:2.28.4:
core:libgxps:0.2.2:
core:libnotify:0.7.5:
core:libpeas:1.9.0:
core:libqmi:1.0:
core:rest:0.7.90:
core:librsvg:2.37.0:
core:libsecret:0.15:
core:libsigc++:2.3.1:
core:libwnck:3.4.5:
core:libzapojit:0.0.3:
core:mm-common:0.9.6:
core:mousetweaks:3.8.0:
core:nautilus:3.9.3:
core:network-manager-applet:0.9.8.2:
core:pango:1.35.0:
core:pangomm:2.34.0:
core:seed:3.8.1:
core:sushi:3.8.1:
core:totem-pl-parser:3.4.5:
core:tracker:0.16.1:
core:vala:0.20.1:
core:vino:3.9.3:
core:vte:0.34.7:
core:yelp:3.8.1:
core:zenity:3.8.0:
apps:accerciser:3.8.2:
apps:brasero:3.8.0:
apps:file-roller:3.9.4:
apps:five-or-more:3.8.2:
apps:four-in-a-row:3.8.1:
apps:glade:3.15.2:
apps:gnome-clocks:3.9.2:
apps:gnome-color-manager:3.8.2:
apps:gnome-devel-docs:3.8.1:
apps:gnome-documents:3.9.4:
apps:gnome-getting-started-docs:3.8.3:
apps:gnome-initial-setup:0.12:
apps:gnome-klotski:3.8.2:
apps:gnome-mahjongg:3.8.0:
apps:gnome-mines:3.8.1:
apps:gnome-nettool:3.8.1:
apps:gnome-nibbles:3.8.0:
apps:gnome-robots:3.8.1:
apps:gnome-sudoku:3.8.1:
apps:gnome-tetravex:3.8.1:
apps:iagno:3.8.1:
apps:lightsoff:3.8.0:
apps:nautilus-sendto:3.8.0:
apps:nemiver:0.9.4:
apps:seahorse:3.9.1:
apps:swell-foop:3.8.1:
apps:tali:3.8.0:

Yes, it's a really really long list, even if you count out the ones with no relevant changes on git.

The second issue is related to currently available (and outdated) packages for the following modules:
 * baobab
 * epiphany
 * glade
 * aisleriot
 * gnome-clocks
 * gnome-photos

Mostly they are related to deprecated stuff from gtk+ (tail of build log attached) and seem to ignore (apart epiphany) the --disable-maintainer-mode forced at configure time. Latest code from git seems to (at least) compile, but could need an updated vala release too.

So, considering the recent changes in GTK+ and the people's needs in order to reach GUADEC location, we can
  1) publish a partial release, basically a 3.9.4 with few updated modules
  2) set release team members (the ones in Brno) on module maintainers (the ones in Brno too) and coerce to make a new release ;-)

I personally choose for the second one, I prefer to delay for a couple of days and provide fresh code.



Attachment: gnome-clock-build-failure.log
Description: Binary data

Attachment: gnome-photo-build-failure.log
Description: Binary data

Attachment: glade-build-failure.log
Description: Binary data

Attachment: baobab-build-failure.log
Description: Binary data



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]