All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valentin Popa <valentin.popa@intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: [PATCH] gtk+3: update RECIPE_NO_UPDATE_REASON
Date: Wed, 19 Feb 2014 18:26:29 +0200	[thread overview]
Message-ID: <5304DB35.4030904@intel.com> (raw)
In-Reply-To: <CAJTo0LZfPemAGtX7r79dV7L5dvsbLaqJqw7S_YRNEpBbhwLtjA@mail.gmail.com>

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.


      reply	other threads:[~2014-02-19 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 17:00 [PATCH] gtk+3: update RECIPE_NO_UPDATE_REASON Valentin Popa
2014-02-18 17:04 ` Burton, Ross
2014-02-19 16:26   ` Valentin Popa [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5304DB35.4030904@intel.com \
    --to=valentin.popa@intel.com \
    --cc=poky@yoctoproject.org \
    --cc=ross.burton@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.