[yocto] [Recipe reporting system] Upgradable recipe name list

[recipe-report]

This mail was sent out by Recipe reporting system.

This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade at this time, they can fill
RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder
until newer upstream version was detected.

Example:
RECIPE_NO_UPDATE_REASON = "Version 2.0 is unstable"

You can check the detail information at:

http://recipes.yoctoproject.org/

Package   Version   Upstream version  Maintainer   
NoUpgradeReason
      ---  
--
texinfo   6.0   6.1   Alejandro Hernandez
ruby  2.2.5 2.3.1 Alejandro Hernandez
perl  5.22.15.24.0Alejandro Hernandez
python-dbus   1.2.0 1.2.4 Alejandro Hernandez
python-git1.0.2 2.0.2 Alejandro Hernandez
python-mako   1.0.3 1.0.4 Alejandro Hernandez
python-numpy  1.10.41.11.0Alejandro Hernandez
python-pygobject  3.18.23.21.0Alejandro Hernandez
python-scons  2.4.1 2.5.0 Alejandro Hernandez
python3-pip   8.0.0 8.1.2 Alejandro Hernandez
python3-setuptools19.4  21.0.0Alejandro Hernandez
python-setuptools 19.4  21.0.0Alejandro Hernandez
perl-native   5.22.15.24.0Alejandro Hernandez
python-scons-native   2.4.1 2.5.0 Alejandro Hernandez
liberation-fonts  1.04  2.00.1Alexander Kanavin
2.x depends on fontforge pa...
gcr   3.18.03.20.0Alexander Kanavin
gnome-desktop33.18.23.20.2Alexander Kanavin
libsecret 0.18.40.18.5Alexander Kanavin
watchdog  5.14  5.15  Alexander Kanavin
kexec-tools   2.0.112.0.12Alexander Kanavin
btrfs-tools   4.4   4.5.3 Alexander Kanavin
sysprof   1.2.0+gitX3.20.0+gitAUTOINC...  Alexander Kanavin
systemtap-uprobes 2.9   3.0   Alexander Kanavin
systemtap 2.9   3.0   Alexander Kanavin
epiphany  3.18.43.20.2Alexander Kanavin
hwlatdetect   0.96  2.0   Alexander Kanavin
rt-tests  0.96  2.0   Alexander Kanavin
webkitgtk 2.12.12.12.2Alexander Kanavin
boost 1.60.01.61.0Alexander Kanavin
icu   56.1  57.1  Alexander Kanavin
bjam-native   1.60.01.61.0Alexander Kanavin
libksba   1.3.3 1.3.4 Alexander Kanavin
liburcu   0.9.1 0.9.2 Alexander Kanavin
babeltrace1.3.1 1.3.2 Alexander Kanavin
libarchive3.1.2 3.2.0 Alexander Kanavin
gnutls3.4.9 3.5.0 Alexander Kanavin
msmtp 1.6.3 1.6.4 Alexander Kanavin
mkelfimage4.0+gitX  4.4+gitAUTOINC+58...  Alexander Kanavin
mkelfimage has been removed...
iso-codes 3.65  3.68  Alexander Kanavin
apt   1.0.10.1  1.2.12Aníbal Limón
dpkg  1.18.41.18.7Aníbal Limón
qemu  2.5.1 2.6.0 Aníbal Limón
linux-libc-headers4.4   4.6   Bruce Ashfield
guilt-native  0.35+gitX 0.36+gitAUTOINC+2...  Bruce Ashfield
dbus-test 1.10.61.10.8Chen Qi
dbus  1.10.61.10.8Chen Qi
util-linux2.27.12.28  Chen Qi
curl  7.47.17.48.0Chen Qi
byacc 20150711  20160324  Chen Qi
gzip  1.6   1.8   Chen Qi
sudo  1.8.151.8.16Chen Qi
sysstat   11.2.011.3.4Chen Qi
grep  2.23  2.25  Chen Qi
build-appliance-i...  14.0.015.0.0Cristian Iorga
dhcp  4.3.3 4.3.4 Hongxu Jia
ncurses   6.0+20160213  6.0+20160319  Hongxu Jia
gnupg 2.1.112.1.12Hongxu Jia
pax-utils 1.1.5 1.1.6 

Re: [yocto] https://layers.openembedded.org/

[akuster]

On 5/15/16 3:22 PM, Paul Eggleton wrote:
> On Sun, 15 May 2016 14:17:26 akuster808 wrote:
>> Is the layer index down?
> 
> It has been yes - Michael has been looking into it and I believe he's located 
> the problem - for now it's still unavailable though I expect it will be back 
> imminently.

Working now. thanks.

 -armin
> 
> Cheers,
> Paul
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] https://layers.openembedded.org/

[Paul Eggleton]

On Sun, 15 May 2016 14:17:26 akuster808 wrote:
> Is the layer index down?

It has been yes - Michael has been looking into it and I believe he's located 
the problem - for now it's still unavailable though I expect it will be back 
imminently.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] https://layers.openembedded.org/

[akuster808]

Is the layer index down?


- armin



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Branch Maintenance process clarification

[Khem Raj]

On Sun, May 15, 2016 at 11:11 AM, akuster808  wrote:
> Hello,
>
> I am reviewing the stable branch maintenance for Yocto and would like
> some clarification on a few steps.
> https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance
>
> 6. Split out any bitbake changes and send them to the bitbake-devel
> mailing list (marking them with the appropriate stable version in the
> subject line e.g. [1.20])
>
> AK] I have not seen this being done in the past. Should we start doing
> this or update the process ?

I would also suggest to add OE-Core branchname along with bitbake version
[1.20][krogoth] or [krogoth/1.20] some thing like that

>
> 7. Split out OE-Core changes and create an openembedded-core-contrib
> branch containing them; send the cover letter only (marking it as such
> in the subject) to the openembedded-core mailing list.
>
> AK] I don't have write access to do this, so this will be a problem.

Ask Michael to add your keys to contrib repo.

>
> 8. Split out any meta-yocto changes and create a poky-contrib branch
> containing them; send the cover letter only (marking it as such in the
> subject) to the poky mailing list.
>
> AK] Is this required?

yes.

>
> I do agree that the downstream repos are where the changes should be
> pushed first  then feed poky. This is not what I have seen happen in the
> past nor did I do it for dizzy either.

Usually changes flow into upstream layers and then get merged into
downstream distros
like poky and others.

>
> regards,
> Armin
>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] build yocto/linux under windows

[Khem Raj]

On Sun, May 15, 2016 at 10:42 AM, Peter Balazovic
 wrote:
> Dears,
>
> i'm looking for a way to build Yocto/Linux and develop for my embedded
> target i.mx processor platform under Windows?
> Is there a way to build Yocto/Linux under Windows and to have
> cross-compiler toolchain to be run under windows?
> Actually I would like to know how to run cross-compiler toolchain under 
> windows?

You can use http://git.yoctoproject.org/cgit/cgit.cgi/meta-mingw
in your layermix and build Cross SDKs for windows

>
> Thank you.
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] build yocto/linux under windows

[Andreas Enbacka]

Hello,

I have not actually tried this myself, but the latest build of Windows 10 
preview contains the Windows subsystem for Linux, which allows you to run bash 
session in a command prompt (based on Ubuntu). You can install packages via 
apt-get etc. so in theory at least it would be possible to use Yocto under 
Windows.

Regards,
Andreas

> 15 maj 2016 kl. 20:42 skrev Peter Balazovic :
> 
> Dears,
> 
> i'm looking for a way to build Yocto/Linux and develop for my embedded
> target i.mx processor platform under Windows?
> Is there a way to build Yocto/Linux under Windows and to have
> cross-compiler toolchain to be run under windows?
> Actually I would like to know how to run cross-compiler toolchain under 
> windows?
> 
> Thank you.
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Branch Maintenance process clarification

[akuster808]

Hello,

I am reviewing the stable branch maintenance for Yocto and would like
some clarification on a few steps.
https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance

6. Split out any bitbake changes and send them to the bitbake-devel
mailing list (marking them with the appropriate stable version in the
subject line e.g. [1.20])

AK] I have not seen this being done in the past. Should we start doing
this or update the process ?

7. Split out OE-Core changes and create an openembedded-core-contrib
branch containing them; send the cover letter only (marking it as such
in the subject) to the openembedded-core mailing list.

AK] I don't have write access to do this, so this will be a problem.

8. Split out any meta-yocto changes and create a poky-contrib branch
containing them; send the cover letter only (marking it as such in the
subject) to the poky mailing list.

AK] Is this required?

I do agree that the downstream repos are where the changes should be
pushed first  then feed poky. This is not what I have seen happen in the
past nor did I do it for dizzy either.

regards,
Armin



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] build yocto/linux under windows

[Peter Balazovic]

Dears,

i'm looking for a way to build Yocto/Linux and develop for my embedded
target i.mx processor platform under Windows?
Is there a way to build Yocto/Linux under Windows and to have
cross-compiler toolchain to be run under windows?
Actually I would like to know how to run cross-compiler toolchain under windows?

Thank you.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] machine arch files for Jetson TX1 (Quad-core ARMCortex-A57 MPCore Processor)

[Matt Madison]

On 15 May 2016, at 04:25 , Jack Mitchell  wrote:
> 
> On 14/05/16 23:46, Paul Knopf wrote:
>> This is what I am thinking.
>> 
>> DEFAULTTUNE = "cortexa9hf"
>> require conf/machine/include/tune-cortexa9.inc
>> 
>> Does this sound right? I am using "hf" because in the crosstools-ng
>> has CT_ARCH_FLOAT="hard", and cortexa9 because of
>> CT_ARCH_CPU="cortex-a9" and CT_ARCH_TUNE="cortex-a9".
>> 
>> Sorry, I'm that familiar with embedded processors. Any guidance would
>> be greatly appreciated.
>> 
> 
> Someone has already started having a go.
> 
> https://github.com/watatuki/meta-jetson-tx1
> 
> Easiest way to check for support in OE is to google meta + devboard name. 
> Usually turns something up :)

There’s also https://github.com/madisongh/meta-tegra. 

-Matt


> 
> Cheers,
> Jack.
> 
> ---
> Jack Mitchell
> Embedded Linux Consultant
> www.tuxable.co.uk
> 
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] machine arch files for Jetson TX1 (Quad-core ARMCortex-A57 MPCore Processor)

[Jack Mitchell]

On 14/05/16 23:46, Paul Knopf wrote:

This is what I am thinking.

DEFAULTTUNE = "cortexa9hf"
require conf/machine/include/tune-cortexa9.inc

Does this sound right? I am using "hf" because in the crosstools-ng
has CT_ARCH_FLOAT="hard", and cortexa9 because of
CT_ARCH_CPU="cortex-a9" and CT_ARCH_TUNE="cortex-a9".

Sorry, I'm that familiar with embedded processors. Any guidance would
be greatly appreciated.



Someone has already started having a go.

https://github.com/watatuki/meta-jetson-tx1

Easiest way to check for support in OE is to google meta + devboard 
name. Usually turns something up :)


Cheers,
Jack.

---
Jack Mitchell
Embedded Linux Consultant
www.tuxable.co.uk

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto