Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Aníbal Limón" <anibal.limon@linux.intel.com>,
	openembedded-core@lists.openembedded.org,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	poky@yoctoproject.org
Subject: Re: [poky] Automatic Upgrade Helper Announcement
Date: Fri, 26 Jun 2015 18:13:29 +0300	[thread overview]
Message-ID: <558D6C19.5030409@linux.intel.com> (raw)
In-Reply-To: <558C5E43.6010709@linux.intel.com>

On 06/25/2015 11:02 PM, Aníbal Limón wrote:
> I'm glad to announce the enabling of Automatic Upgrade Helper (a.k.a.
> AUH), the AUH is a service
> that provides recipe upgrades and will be run on weekly basis.
>
> If you are a maintainer (listed in [1]) you will receive AUH emails with
> Recipe upgrades when AUH
> detects that upgrade is needed.

I'm currently doing a related activity - going through oe-core recipes 
in alphabetical order, and making sure that upstream version information 
for them is correct.

I've found a few cases where the upstream check is performed on a stale 
directory (so the recipe is reported 'up to date' even though it's not), 
or the reported upstream version is totally bogus [1], or the upstream 
version is 'unknown' even though it can be retrieved with a correct 
entry in package_regex.inc. Expect patches to come this way soon.

[1] http://recipes.yoctoproject.org/rrs/recipedetail/155/


Alex


      parent reply	other threads:[~2015-06-26 15:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <558C5E43.6010709@linux.intel.com>
2015-06-26 13:17 ` [poky] Automatic Upgrade Helper Announcement Burton, Ross
2015-06-26 15:13 ` Alexander Kanavin [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=558D6C19.5030409@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=anibal.limon@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=poky@yoctoproject.org \
    --cc=yocto@yoctoproject.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox