public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Maxin B. John" <maxin.john@intel.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/12] package upgrades
Date: Wed, 24 Jan 2018 11:01:58 +0200	[thread overview]
Message-ID: <20180124090157.GA29810@mbabyjoh-desk.ger.corp.intel.com> (raw)
In-Reply-To: <3c471c16-697f-df89-4d46-6d7d763244b2@linux.intel.com>

Hi Alex,

On Tue, Jan 23, 2018 at 04:06:11PM +0200, Alexander Kanavin wrote:
> On 01/23/2018 04:05 PM, Maxin B. John wrote:
> >Package upgrades including gtk+3
> 
> Btw, do give it a try to run AUH locally (without sending emails to anyone).

No, I didn't try to run AUH locally.

> Making local runs easy was one of my goals. You can give it a list of things
> to update on the command line, if you don't want it to go over all of
> oe-core, and it will test builds with musl and strange architectures etc.
> Now that you have also jku's packages, it should really help.

It looks like a very helpful tool. I am going to use it for next set of upgrades.

Notes:

Eventhough README in AUH is a good starting point, couldn't locate a quick-start
documentation in the wiki or official documentation. It will be useful. 

Link: https://git.yoctoproject.org/cgit/cgit.cgi/auto-upgrade-helper/tree/README

> Alex

Thanks and Regards,
Maxin


  reply	other threads:[~2018-01-24  9:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23 14:05 [PATCH 00/12] package upgrades Maxin B. John
2018-01-23 14:05 ` [PATCH 01/12] freetype: upgrade to version 2.9 Maxin B. John
2018-01-23 14:02   ` Alexander Kanavin
2018-01-23 14:05 ` [PATCH 02/12] libsoup-2.4: upgrade to version 2.61.2 Maxin B. John
2018-01-23 14:44   ` Burton, Ross
2018-01-24  9:25     ` Maxin B. John
2018-01-23 14:05 ` [PATCH 03/12] ofono: upgrade to version 1.22 Maxin B. John
2018-01-23 14:05 ` [PATCH 04/12] pango: upgrade to version 1.41.0 Maxin B. John
2018-01-23 14:45   ` Burton, Ross
2018-01-23 14:42     ` Alexander Kanavin
2018-01-23 14:54       ` Burton, Ross
2018-01-23 14:05 ` [PATCH 05/12] libtasn1: upgrade to version 4.13 Maxin B. John
2018-01-23 14:05 ` [PATCH 06/12] puzzles: upgrade to latest commit Maxin B. John
2018-01-23 14:05 ` [PATCH 07/12] sqlite3: upgrade to version 3.22.0 Maxin B. John
2018-01-23 14:05 ` [PATCH 08/12] vte: upgrade to version 0.50.2 Maxin B. John
2018-01-23 14:05 ` [PATCH 09/12] gtk+: upgrade to version 2.24.32 Maxin B. John
2018-01-23 14:05 ` [PATCH 10/12] gtk+3: upgrade to version 3.22.26 Maxin B. John
2018-01-23 14:05 ` [PATCH 11/12] gtk-icon-utils-native: " Maxin B. John
2018-01-23 14:05 ` [PATCH 12/12] atk: upgrade to version 2.26.1 Maxin B. John
2018-01-23 14:06 ` [PATCH 00/12] package upgrades Alexander Kanavin
2018-01-24  9:01   ` Maxin B. John [this message]
2018-01-25  7:09     ` Alexander Kanavin
  -- strict thread matches above, loose matches on Subject: below --
2014-04-29 13:29 Laurentiu Palcu
2013-06-28 15:53 [PATCH 00/12] Package upgrades Ionut Radu

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=20180124090157.GA29810@mbabyjoh-desk.ger.corp.intel.com \
    --to=maxin.john@intel.com \
    --cc=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.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