[PATCH] gtk+3: update RECIPE_NO_UPDATE_REASON

[PATCH] gtk+3: update RECIPE_NO_UPDATE_REASON

[Valentin Popa]

gtk+3 3.11.5 needs glib-2.0 >= 2.39.0 (which is unstable)
Let's wait for glib 2.40.

Signed-off-by: Valentin Popa <valentin.popa@intel.com>
---
 meta-yocto/conf/distro/include/upstream_tracking.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-yocto/conf/distro/include/upstream_tracking.inc b/meta-yocto/conf/distro/include/upstream_tracking.inc
index d80ede4..35a87e7 100644
--- a/meta-yocto/conf/distro/include/upstream_tracking.inc
+++ b/meta-yocto/conf/distro/include/upstream_tracking.inc
@@ -91,7 +91,7 @@ RECIPE_NO_UPDATE_REASON_pn-gst-plugins-bad = "not compatible with gst-fluendo 0.
 RECIPE_NO_UPDATE_REASON_pn-gst-plugins-good = "not compatible with gst-fluendo 0.10.x"
 RECIPE_NO_UPDATE_REASON_pn-gst-plugins-ugly = "not compatible with gst-fluendo 0.10.x"
 RECIPE_NO_UPDATE_REASON_pn-gstreamer=" not compatible with gst-fluendo 0.10.x "
-RECIPE_NO_UPDATE_REASON_pn-gtk+ = "Do not upgrade to version: 2.99.2 because prefer stable tree"
+RECIPE_NO_UPDATE_REASON_pn-gtk+ = "Waiting for glib 2.40 (stable)"
 RECIPE_NO_UPDATE_REASON_pn-gtk-doc-stub = "PRS Reports Incorrectly"
 RECIPE_UPSTREAM_VERSION_pn-gtk-engines = "2.91.1"
 RECIPE_UPSTREAM_DATE_pn-gtk-engines = "Oct 9, 2010"
-- 
1.8.3.2

Re: [PATCH] gtk+3: update RECIPE_NO_UPDATE_REASON

[Burton, Ross]

On 18 February 2014 17:00, Valentin Popa <valentin.popa@intel.com> wrote:
> gtk+3 3.11.5 needs glib-2.0 >= 2.39.0 (which is unstable)
> Let's wait for glib 2.40.

GTK+ 3.11 is a development release, can you instead update the regexes
to ignore odd numbers?

Ross

Re: [PATCH] gtk+3: update RECIPE_NO_UPDATE_REASON

[Valentin Popa]

On 02/18/2014 07:04 PM, Burton, Ross wrote:
> On 18 February 2014 17:00, Valentin Popa <valentin.popa@intel.com> wrote:
>> gtk+3 3.11.5 needs glib-2.0 >= 2.39.0 (which is unstable)
>> Let's wait for glib 2.40.
> GTK+ 3.11 is a development release, can you instead update the regexes
> to ignore odd numbers?
>
> Ross
Found that it's not working using just regex, because the package 
reporting system looks also for the latest dir first  (which might be a 
development version) and then applies the regex for the packages/files 
inside.