All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
	OpenEmbedded Core Mailing List
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] go-dep: Add 0.3.0 release
Date: Mon, 4 Sep 2017 14:46:50 -0300	[thread overview]
Message-ID: <CAP9ODKoTRR0e-7MrkN=u5rt928y=Weh2VV_wwdqBSzpV0rK7zA@mail.gmail.com> (raw)
In-Reply-To: <CAJTo0LbPBn=TmjGb6ozkVjsMdF8H+MaYF32DhZi8Evs7N=n5sA@mail.gmail.com>

On Mon, Sep 4, 2017 at 7:09 AM, Burton, Ross <ross.burton@intel.com> wrote:
> On 3 September 2017 at 20:25, Otavio Salvador <otavio@ossystems.com.br>
> wrote:
>>
>> This is the Golang dependency management tool under development; it is
>> ready for production use and intended to be merged onto Golang
>> 1.10. Until that, projects are starting to use it and making it
>> available on OE-Core reduces the Golang integration work for new
>> recipes.
>
>
> ERROR: go-dep-0.3.0-r0 do_package: QA Issue: go-dep: Files/directories were
> installed but not shipped in any package:
>   /usr/lib64/x86_64-poky-linux/go/bin/dep
> Please set FILES such that these items are packaged. Alternatively if they
> are unneeded, avoid installing them or delete them within do_install.
> go-dep: 1 installed and not shipped files. [installed-vs-shipped]

I know and this is an issue with our Go toolchain support. It fails
when we are building for same architecture than our build host.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


  reply	other threads:[~2017-09-04 17:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-03 19:25 [PATCH v2] go-dep: Add 0.3.0 release Otavio Salvador
2017-09-04 10:09 ` Burton, Ross
2017-09-04 17:46   ` Otavio Salvador [this message]
2017-09-04 19:29     ` Burton, Ross
2017-09-04 19:33       ` Otavio Salvador

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='CAP9ODKoTRR0e-7MrkN=u5rt928y=Weh2VV_wwdqBSzpV0rK7zA@mail.gmail.com' \
    --to=otavio.salvador@ossystems.com.br \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --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.