Hello All,
Enjoy viewing the full Report for 2.4 RC1:
https://wiki.yoctoproject.org/wiki/WW40_-_2017-10-06_-_Full_Test_Cycle_2.4_RC1
=== Summary
The QA cycle for release 2.4 RC1 is complete. There are 18 new bugs from which
5 are high priority and are targeted to be fixed in
On Fri, Oct 6, 2017 at 3:08 PM, Gutierrez, Hernan Ildefonso (Boise
R&D, FW) wrote:
> Hi,
>
> We are planning to implement a mirror for both source code downloaded and
> sscache in our work environment.
>
> We are planning to use Nexus and Nuget to allow storage and versioning
> control. We don’t k
Hi,
We are planning to implement a mirror for both source code downloaded and
sscache in our work environment.
We are planning to use Nexus and Nuget to allow storage and versioning control.
We don't know if these are the right tools.
Since we are about to embark in this project, before starti
yep, that makes sense, thanks for the contribution
merged
On 10/05/2017 12:03 PM, Jeffrey Pautler wrote:
If the -f option is enabled, opkg-make-index will include user-defined
fields in the package index rather than discarding them. This change is
motivated by the fact that opkg now has suppo
On Fri, Oct 6, 2017 at 7:56 AM, Patrick Vacek
wrote:
> On 06.10.2017 15:36, Khem Raj wrote:
>> On Fri, Oct 6, 2017 at 5:05 AM, Patrick Vacek
>> wrote:
>>> Hello,
>>>
>>> I'm trying to understand how Yocto figures out which Boost libraries to
>>> install in an image. I've been studying the Boost r
Agreed, opkg-make-index spould not be formatting control files.
Description should be treated as any other field.
merged
On 10/05/2017 09:05 AM, Jeffrey Pautler wrote:
The Debian Policy Manual describes the format of the description field.
This includes information about how lines might be wr
Hi,
On 06.10.2017 15:40, richard_al...@keysight.com wrote:
I am build an image with read-only-rootfs
When enabled, during startup I get a
[FAILED] Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-tmpfiles-setup.service' for details.
● systemd-tmpfiles-set
I am build an image with read-only-rootfs
When enabled, during startup I get a
[FAILED] Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-tmpfiles-setup.service' for details.
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded:
On 06.10.2017 15:36, Khem Raj wrote:
> On Fri, Oct 6, 2017 at 5:05 AM, Patrick Vacek
> wrote:
>> Hello,
>>
>> I'm trying to understand how Yocto figures out which Boost libraries to
>> install in an image. I've been studying the Boost recipes and it looks
>> like RRECOMMENDS is used to specify all
On Thu, Oct 5, 2017 at 3:09 AM, Torsten Sievers
wrote:
> Hi guys,
>
> Here is the situation:
>
> I have two custom made recipes, one is a SDK , the other one is a set of
> examples that use the sdk.
>
> The examples recipe has DEPENDS and RDEPENDS set that point to artifacts
> that are produced by
On Fri, Oct 6, 2017 at 5:05 AM, Patrick Vacek
wrote:
> Hello,
>
> I'm trying to understand how Yocto figures out which Boost libraries to
> install in an image. I've been studying the Boost recipes and it looks
> like RRECOMMENDS is used to specify all of the libraries, but yet my
> image only get
On 10/05/2017 10:08 PM, Josef Holzmayr wrote:
Uhm. Be aware that your custom built distribution is *not* some kind of
Fedora-Light. Its an entirely different distribution, and mixing in
repositories from somewhere is most certainly disastrous - or do you
think using that OpenSuse repo plays a
siv...@easyarm.com
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Hello,
I'm trying to understand how Yocto figures out which Boost libraries to
install in an image. I've been studying the Boost recipes and it looks
like RRECOMMENDS is used to specify all of the libraries, but yet my
image only gets a subset of them. It's the subset that I typically need,
so it'
Hi Jeff,
Sorry to hear about the failure,
The change was part of adding merged /usr support for oecore.
'INSTALL_MOD_PATH' was using '/lib/modules/${KERNEL_VERSION}' as kernel modules
path, where as in merged /usr environments it would be
'/usr/lib/modules/${KERNEL_VERSION}'., And there is no
15 matches
Mail list logo