Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Joshua G Lock <joshua.g.lock@linux.intel.com>,
	oe-core <openembedded-core@lists.openembedded.org>
Cc: "Cetola, Stephano" <stephano.cetola@intel.com>
Subject: Re: PRServer's problem
Date: Wed, 18 May 2016 16:13:46 +0800	[thread overview]
Message-ID: <573C243A.8060405@windriver.com> (raw)
In-Reply-To: <1463556849.3966.3.camel@linux.intel.com>

Hi Joshua,

Thanks, I read packagefeed-stability.bbclass just now. If
we can change PRserver's checksum to consider RDEPENDS only
(or make it optional) I will run a testing on that script.

// Robert

On 05/18/2016 03:34 PM, Joshua G Lock wrote:
> Hi Robert,
>
> On Wed, 2016-05-18 at 14:09 +0800, Robert Yang wrote:
>> The PRServer bumps PR according to do_package's task hash, that
>> causes it bumps *all* packages' PR when recipes like pseudo-native
>> and rpm-native is changed. It is a very bad user experience when we
>> run "smart/opkg upgrade" on running target, for example, when we
>> apply
>> a CVE patch to pseudo-native or rpm-native, or do some slight changes
>> in their do_compile, "smart/opkg upgrade" will download/install *all*
>> the packages since all of the packages' PR are bumped.
>
> Paul began working to address the package feed churn issue some time
> back using the tool build-compare from the openSUSE project.
>
> You can find links to various trees and a summary of the progress so
> far in this bugzilla entry:
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=8318
>
> It still needs some more work; most notably I'd like to see some tests
> that validates the functionality.
>
> Regards,
>
> Joshua
>


  reply	other threads:[~2016-05-18  8:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18  6:09 PRServer's problem Robert Yang
2016-05-18  7:34 ` Joshua G Lock
2016-05-18  8:13   ` Robert Yang [this message]
2016-05-18  7:39 ` Martin Jansa
2016-05-18  8:03   ` Robert Yang
2016-05-18  9:20     ` Martin Jansa
2016-05-18  9:31       ` Robert Yang
2016-05-18 10:15         ` Martin Jansa
2016-05-19  2:33           ` Robert Yang
2016-05-19  3:10             ` Robert Yang
2016-05-19  9:45               ` Richard Purdie
2016-05-19 10:12                 ` Robert Yang
2016-05-19 10:17                   ` Richard Purdie
2016-05-20  2:27                     ` Robert Yang
2016-05-19 10:37                   ` Joshua G Lock
2016-05-19 11:10                     ` Paul Eggleton
2016-05-19  8:47             ` Martin Jansa
2016-05-19  9:40               ` Richard Purdie
2016-05-19  9:45               ` Robert Yang
2016-05-19 10:24                 ` Martin Jansa
2016-05-18 12:27         ` Sergey 'Jin' Bostandzhyan
2016-07-27  8:06           ` Robert Yang
2016-07-27  8:30             ` Sergey 'Jin' Bostandzhyan
2016-07-27  8:43               ` Robert Yang
2016-05-20 10:00 ` Mike Looijmans

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=573C243A.8060405@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=joshua.g.lock@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=stephano.cetola@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox