From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <auh@auh.yoctoproject.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [AUH] linux-yocto: upgrading to 4.15.7 FAILED
Date: Sat, 17 Mar 2018 17:32:42 -0400 [thread overview]
Message-ID: <f2d0bd91-81f9-ff08-2f0d-944e7eafa9c7@windriver.com> (raw)
In-Reply-To: <20180317204657.19574440002@auh.yoctoproject.org>
How do I get linux-libc-headers and linux-yocto removed from the
AUH list of recipes ?
These follow a specific cadence, and shouldn't be included in these
attempts.
Bruce
On 2018-03-17 4:46 PM, auh@auh.yoctoproject.org wrote:
> Hello,
>
> You are receiving this email because you are the maintainer
> of *linux-yocto* recipe and this is to let you know that the automatic attempt
> to upgrade the recipe to *4.15.7* has Failed (devtool error).
>
> Detailed error information:
>
> The following devtool command failed: upgrade linux-yocto -V 4.15.7 -S cb4a115a42867def71fdcbf0d7b714f268ff37fd
> NOTE: Starting bitbake server...
> Loading cache...done.
> Loaded 1281 entries from dependency cache.
> NOTE: Extracting current version source...
> NOTE: Resolving any missing task queue dependencies
>
> Build Configuration:
> BB_VERSION = "1.37.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "universal"
> TARGET_SYS = "i586-poky-linux"
> MACHINE = "qemux86"
> DISTRO = "poky"
> DISTRO_VERSION = "2.4+snapshot-20180317"
> TUNE_FEATURES = "m32 i586"
> TARGET_FPU = ""
> meta
> meta-poky
> meta-yocto-bsp = "tmp-auh-upgrades:096c67796ac50aa6059494f32104e6c1c520bbfc"
> workspace = "<unknown>:<unknown>"
>
> Initialising tasks...done.
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> NOTE: Tasks Summary: Attempted 367 tasks of which 358 didn't need to be rerun and all succeeded.
> NOTE: Writing buildhistory
> NOTE: Copying kernel config to srctree
> NOTE: Extracting upgraded version source...
> ERROR: Revision cb4a115a42867def71fdcbf0d7b714f268ff37fd was found on multiple branches:
> v4.15/base
> v4.15/standard/arm-versatile-926ejs
> v4.15/standard/base
> v4.15/standard/beaglebone
> v4.15/standard/edgerouter
> v4.15/standard/fsl-mpc8315e-rdb
> v4.15/standard/intel
> v4.15/standard/mti-malta32
> v4.15/standard/mti-malta64
> v4.15/standard/preempt-rt/base
> v4.15/standard/preempt-rt/intel
> v4.15/standard/qemuarm64
> v4.15/standard/qemuppc
> v4.15/standard/tiny/base
> v4.15/standard/tiny/common-pc
> v4.15/standard/tiny/intel
> Please provide the correct branch in the devtool command with "--srcbranch" or "-B" option.
> ERROR: Revision cb4a115a42867def71fdcbf0d7b714f268ff37fd was found on multiple branches:
> v4.15/base
> v4.15/standard/arm-versatile-926ejs
> v4.15/standard/base
> v4.15/standard/beaglebone
> v4.15/standard/edgerouter
> v4.15/standard/fsl-mpc8315e-rdb
> v4.15/standard/intel
> v4.15/standard/mti-malta32
> v4.15/standard/mti-malta64
> v4.15/standard/preempt-rt/base
> v4.15/standard/preempt-rt/intel
> v4.15/standard/qemuarm64
> v4.15/standard/qemuppc
> v4.15/standard/tiny/base
> v4.15/standard/tiny/common-pc
> v4.15/standard/tiny/intel
> Please provide the correct branch in the devtool command with "--srcbranch" or "-B" option.
>
>
>
> Please review the attached files for further information and build/update failures.
> Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
>
> Regards,
> The Upgrade Helper
>
next parent reply other threads:[~2018-03-17 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180317204657.19574440002@auh.yoctoproject.org>
2018-03-17 21:32 ` Bruce Ashfield [this message]
2018-03-19 8:54 ` [AUH] linux-yocto: upgrading to 4.15.7 FAILED Alexander Kanavin
2018-03-19 12:23 ` Bruce Ashfield
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=f2d0bd91-81f9-ff08-2f0d-944e7eafa9c7@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=auh@auh.yoctoproject.org \
--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