date:20130721

Re: [yocto] linux-yocto fragments meta branch

2013-07-21 Thread Bruce Ashfield


On 13-07-22 1:12 AM, Sipke Vriend wrote:

Hi Bruce,

The linux-yocto orphaned meta branch commit
8ef9136539464c145963ac2b8ee0196fea1c2337
.gitignore: do not ignore meta directory

causes the linux-yocto targets in meta-xilinx/master to fail with the following
error(s):
 snip ---
[ERROR] unable to complete push
| ERROR. could not update git tree
| ERROR. Could not apply patches for zedboard.
|Patch failures can be resolved in the devshell (bitbake -c devshell 
linux-yocto)
| ERROR: Function failed: do_patch (log file is located at 
/home/sipkev/yocto/5-poky/build/tmp/work/zedboard-poky-linux-gnueabi/linux-yocto/3.8.13+gitAUTOINC+8ef9136539_f20047520a-r4.2/temp/log.do_patch.4403)
--- snip ---
(See full BUILD LOG below).

It seems the kernel tools scripts are seeing a change in the .gitignore file 
(see
TERMINAL OUTPUT below) and attempt a git push for which we don’t have access.

The diff of .gitignore in the working linux directory (see TERMINAL OUTPUT
below) is that of the commit above.
Checking linux-yocto-3.8 repository shows that the meta branch .gitignore
contains the commit, but the .gitignore in the master (or standard/meta) does
not.

Should the .gitignore files match between the linux-yocto-3.8 branches?
If not, can we do something in meta-xilinx to avoid the attempted git push?



Aha. I don't have all the tweaks to the tools in place, I knew I should
have wait on merging that change .. but yet, my tests passed.

You can't avoid the git push, or you won't have any changes made to the
tree :)

I'll revert that change for now, and synchronize it with my tools 
update. But yes, they really should match since with the meta directory

being untracked on purpose in the non-meta branches, we can't have the
gitignore different between the two.

I've pushed the change and will send a pull request later. But if you
update your SRCREV_meta to my latest for now, you should be good to go.

Cheers,

Bruce


Cheers
Sipke


=== BUILD LOG =
build$ bitbake linux-yocto
WARNING: Host distribution "Ubuntu-11.10" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. It is 
recommended that you use a tested distribution.
Parsing recipes: 100% 
|###|
 Time: 00:00:40
Parsing of 850 .bb files complete (0 cached, 850 parsed). 1177 targets, 47 
skipped, 0 masked, 0 errors.

Build Configuration:
BB_VERSION= "1.19.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-11.10"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "zedboard"
DISTRO= "poky"
DISTRO_VERSION= "1.4+snapshot-20130722"
TUNE_FEATURES = " armv7a vfp neon zynq"
TARGET_FPU= "vfp-neon"
meta
meta-yocto
meta-yocto-bsp= "master:31e6eee860b5f9f4ac9ef0889bcff5648de6e3f9"
meta-xilinx
meta-zedboard
meta-zc702
meta-kc705= "master:6e3ba04dbacc1d1d5bcad80f5e554e7fcc51f602"

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_patch (log file is located at 
/home/sipkev/yocto/5-poky/build/tmp/work/zedboard-poky-linux-gnueabi/linux-yocto/3.8.13+gitAUTOINC+8ef9136539_f20047520a-r4.2/temp/log.do_patch.4403)
ERROR: Logfile of failure stored in: 
/home/sipkev/yocto/5-poky/build/tmp/work/zedboard-poky-linux-gnueabi/linux-yocto/3.8.13+gitAUTOINC+8ef9136539_f20047520a-r4.2/temp/log.do_patch.4403
Log data follows:
| DEBUG: Executing shell function do_patch
| Branch meta-temp set up to track remote branch meta from origin by rebasing.
| Unstaged changes after reset:
| M .gitignore
| Deleted branch meta-temp (was 37fdb0c).
| [INFO] validating against known patches  (zedboard-standard-meta)
Branch standard/meta set up to track remote branch standard/base from origin by 
rebasing.
Uncommited changes detected. Refresh first.##] (-)(101 %))
| [ERROR] unable to complete push
| pending patches are:
| links/linux-yocto/xilinx-v14.5/0001-Zynq-specific-changes-to-arch-arm.patch
| links/linux-yocto/xilinx-v14.5/0002-Microblaze-changes-to-arch.patch
| links/linux-yocto/xilinx-v14.5/0003-PowerPC-changes-to-arch.patch
| 
links/linux-yocto/xilinx-v14.5/0004-Xilinx-modifications-to-driver-block-and-driver-char.patch
| 
links/linux-yocto/xilinx-v14.5/0005-Xilinx-modifications-to-drivers-clk-cpufreq-misc.patch
| links/linux-yocto/xilinx-v14.5/0006-Xilinx-modifications-to-drivers-dma.patch
| links/linux-yocto/xilinx-v14.5/0007-Xilinx-modifications-to-drivers-gpio.patch
| 
links/linux-yocto/xilinx-v14.5/0008-Xilinx-modifications-to-drivers-hwmon.patch
| 
links/linux-yocto/xilinx-v14.5/0009-Xilinx-modifications-to-drivers-media.patch
| 
links/linux-yocto/xilinx-v14.5/0010-Xilinx-modifications-to-drivers-memory.patch
| links/linux-yocto/xilinx-v14.5/0011-Xilinx-modificat

[yocto] linux-yocto fragments meta branch

2013-07-21 Thread Sipke Vriend

Hi Bruce,

The linux-yocto orphaned meta branch commit 
8ef9136539464c145963ac2b8ee0196fea1c2337 
.gitignore: do not ignore meta directory

causes the linux-yocto targets in meta-xilinx/master to fail with the following 
error(s):
 snip ---
[ERROR] unable to complete push
| ERROR. could not update git tree
| ERROR. Could not apply patches for zedboard.
|Patch failures can be resolved in the devshell (bitbake -c devshell 
linux-yocto)
| ERROR: Function failed: do_patch (log file is located at 
/home/sipkev/yocto/5-poky/build/tmp/work/zedboard-poky-linux-gnueabi/linux-yocto/3.8.13+gitAUTOINC+8ef9136539_f20047520a-r4.2/temp/log.do_patch.4403)
--- snip ---
(See full BUILD LOG below).

It seems the kernel tools scripts are seeing a change in the .gitignore file 
(see 
TERMINAL OUTPUT below) and attempt a git push for which we don’t have access.

The diff of .gitignore in the working linux directory (see TERMINAL OUTPUT
below) is that of the commit above. 
Checking linux-yocto-3.8 repository shows that the meta branch .gitignore
contains the commit, but the .gitignore in the master (or standard/meta) does
not.

Should the .gitignore files match between the linux-yocto-3.8 branches? 
If not, can we do something in meta-xilinx to avoid the attempted git push?

Cheers
Sipke


=== BUILD LOG =
build$ bitbake linux-yocto
WARNING: Host distribution "Ubuntu-11.10" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Parsing recipes: 100% 
|###|
 Time: 00:00:40
Parsing of 850 .bb files complete (0 cached, 850 parsed). 1177 targets, 47 
skipped, 0 masked, 0 errors.

Build Configuration:
BB_VERSION= "1.19.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-11.10"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "zedboard"
DISTRO= "poky"
DISTRO_VERSION= "1.4+snapshot-20130722"
TUNE_FEATURES = " armv7a vfp neon zynq"
TARGET_FPU= "vfp-neon"
meta
meta-yocto
meta-yocto-bsp= "master:31e6eee860b5f9f4ac9ef0889bcff5648de6e3f9"
meta-xilinx
meta-zedboard
meta-zc702
meta-kc705= "master:6e3ba04dbacc1d1d5bcad80f5e554e7fcc51f602"

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_patch (log file is located at 
/home/sipkev/yocto/5-poky/build/tmp/work/zedboard-poky-linux-gnueabi/linux-yocto/3.8.13+gitAUTOINC+8ef9136539_f20047520a-r4.2/temp/log.do_patch.4403)
ERROR: Logfile of failure stored in: 
/home/sipkev/yocto/5-poky/build/tmp/work/zedboard-poky-linux-gnueabi/linux-yocto/3.8.13+gitAUTOINC+8ef9136539_f20047520a-r4.2/temp/log.do_patch.4403
Log data follows:
| DEBUG: Executing shell function do_patch
| Branch meta-temp set up to track remote branch meta from origin by rebasing.
| Unstaged changes after reset:
| M .gitignore
| Deleted branch meta-temp (was 37fdb0c).
| [INFO] validating against known patches  (zedboard-standard-meta)
Branch standard/meta set up to track remote branch standard/base from origin by 
rebasing.
Uncommited changes detected. Refresh first.##] (-)(101 %))
| [ERROR] unable to complete push
| pending patches are:
| links/linux-yocto/xilinx-v14.5/0001-Zynq-specific-changes-to-arch-arm.patch
| links/linux-yocto/xilinx-v14.5/0002-Microblaze-changes-to-arch.patch
| links/linux-yocto/xilinx-v14.5/0003-PowerPC-changes-to-arch.patch
| 
links/linux-yocto/xilinx-v14.5/0004-Xilinx-modifications-to-driver-block-and-driver-char.patch
| 
links/linux-yocto/xilinx-v14.5/0005-Xilinx-modifications-to-drivers-clk-cpufreq-misc.patch
| links/linux-yocto/xilinx-v14.5/0006-Xilinx-modifications-to-drivers-dma.patch
| links/linux-yocto/xilinx-v14.5/0007-Xilinx-modifications-to-drivers-gpio.patch
| 
links/linux-yocto/xilinx-v14.5/0008-Xilinx-modifications-to-drivers-hwmon.patch
| 
links/linux-yocto/xilinx-v14.5/0009-Xilinx-modifications-to-drivers-media.patch
| 
links/linux-yocto/xilinx-v14.5/0010-Xilinx-modifications-to-drivers-memory.patch
| links/linux-yocto/xilinx-v14.5/0011-Xilinx-modifications-to-drivers-mmc.patch
| links/linux-yocto/xilinx-v14.5/0012-Xilinx-modifications-to-drivers-mtd.patch
| links/linux-yocto/xilinx-v14.5/0013-Xilinx-modifications-to-drivers-net.patch
| 
links/linux-yocto/xilinx-v14.5/0014-Xilinx-modifications-to-drivers-remoteproc.patch
| 
links/linux-yocto/xilinx-v14.5/0015-Xilinx-modifications-to-drivers-rpmsg.patch
| 
links/linux-yocto/xilinx-v14.5/0016-Xilinx-modifications-to-drivers-spi-mfd-and-timerdal.patch
| links/linux-yocto/xilinx-v14.5/0017-Xilinx-modifications-to-drivers-tty.patch
| links/linux-yocto/xilinx-v14.5/0018-Xilinx-modifications-to-drivers-uio.patch
| 
links/linux-yocto/xilinx-v14.5/0019-Xilinx-mod

Re: [yocto] Regarding offline build

2013-07-21 Thread Amit Kumar

Hi Mr. Lee,
Thanks for replay.
I have still doubt to build offline. I have downloaded all the tar files, now 
what I should have to do? Do I need to modify all the *.bb files.
Do you have any example to build it offline.

I wants to build the MCSDK uses the Yocto Project. So for that I have download 
the mcsdk tar ball, which gives me all tar balls.
Now I am not getting how to process to build Yocto project.

If you have any idea please let me know.

Thanks & regards
Amit K


From: lee_ball...@dell.com [mailto:lee_ball...@dell.com]
Sent: Tuesday, July 16, 2013 7:58 PM
To: Amit Kumar; yocto@yoctoproject.org
Subject: RE: Regarding offline build

We do offline builds.  You need to download all the tar balls for all the open 
source recipes you build, or you can download pre-build images and SDK.  
Another way is to create a local mirror of all the tar balls you need.

Lee Ballard
Platform Software Principal Engineer
Dell | Enterprise Product Group


From: yocto-boun...@yoctoproject.org 
[mailto:yocto-boun...@yoctoproject.org] On Behalf Of Amit Kumar
Sent: Tuesday, July 16, 2013 6:22 AM
To: yocto@yoctoproject.org
Subject: [yocto] Regarding offline build

Hi,
I have quarry regarding the Yocto Project build offline.
Is that possible to build the Yocto Project with internet access?
I have download the poky-.tar.bz2, now I wants to build it 
independently without having internet connection.
Do I need to download any other packages also to build it offline?



Thanks & Regards
Amit K


The contents of this e-mail and any attachment(s) may contain confidential or 
privileged information for the intended recipient(s). Unintended recipients are 
prohibited from taking action on the basis of information in this e-mail and 
using or disseminating the information, and must notify the sender and delete 
it from their system. L&T Infotech will not accept responsibility or liability 
for the accuracy or completeness of, or the presence of any virus or disabling 
code in this e-mail"
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Arago project image fail to run in QEMU

2013-07-21 Thread Sudhangathan B S

These simple steps should do..

change your local.conf file to appear like this:

#
# Machine Selection
#
# You need to select a specific machine to target the build with. There are
a selection
# of emulated machines available which can boot and run in the QEMU
emulator:
#
MACHINE ?= "qemuarm" < note this
#MACHINE ?= "qemumips"
#MACHINE ?= "qemuppc"
#MACHINE ?= "qemux86"
#MACHINE ?= "qemux86-64"
#
# There are also the following hardware board target machines included for
# demonstration purposes:
#
#MACHINE ?= "atom-pc"
#MACHINE ?= "beagleboard"
#MACHINE ?= "mpc8315e-rdb"
#MACHINE ?= "routerstationpro"
#
# This sets the default machine to be qemux86 if no other machine is
selected:
#MACHINE ??= "qemux86"

now run (internet/downloading is necessary):
"bitbake "
you can find the built images in deploy/images folder, which you don't need
to
access, then to start the virtual machine, just type (from the same path as
bitbake):
"runqemu qemuarm"
Type *your user password when asked for. Done.

Best,
-
Sudhangathan BS
Ph:(+91) 9731-905-205
-


On Mon, Jul 22, 2013 at 8:02 AM, amit kumar  wrote:

> Hi Sudhangathan
> Thanks for replay.
> So i have to build a separate image to run under the QEMU, for that do i
> need to build it with my yocto project build environment with adding the
> layers.
> Or do i need to use the same build environment and just change the
> local.conf file?
> Keystone-II is a arm processor.
>
>
> Thanks & Regards
> Amit K
>
>
>
>
>
> On Sat, Jul 20, 2013 at 8:41 AM, Sudhangathan BS 
> wrote:
>
>> Hi Amit,
>>
>> You have to build separate images to be run on qemu.. You have to set it
>> in your local.conf file.. i.e. u have to change your build-target..
>>
>> Images built to run on hardware cannot be run on qemu right now..
>>
>> Virtualization is only available upto processor level, and not the
>> complete hardware...!
>>
>> Which processor is keystone-II using..?
>>
>> Best,
>> Sudhangathan B S
>>
>>
>> amit kumar  wrote:
>>>
>>>
>>> Hi,
>>>
>>> I have built the Arago project for keystone-II successfully. The images
>>> are available under the deploy/Images dir.
>>>
>>> I have already added my module into the kernel and recompiled the kernel
>>> image.
>>>
>>>
>>>
>>> Now my doubt is before putting the image on actual hardware I want to
>>> run it on QEMU. Is it possible to run the built images on QEMU?
>>>
>>> I tried to run using the following command but getting an error-
>>>
>>>
>>>  /**/
>>>
>>> amit@amit-HP:~/OE/MCSDK/mcsdk/build$ runqemu
>>> arago-tmp-external-linaro-toolchain/deploy/images/uImage-keystone-evm.bin
>>> arago-tmp-external-linaro-toolchain/deploy/images/core-image-minimal-keystone-evm-20130718181345.rootfs.ubi
>>> Error: unknown file arg
>>> [arago-tmp-external-linaro-toolchain/deploy/images/core-image-minimal-keystone-evm-20130718181345.rootfs.ubi]
>>>
>>> Usage: you can run this script with any valid combination
>>> of the following options (in any order):
>>>   QEMUARCH - the qemu machine architecture to use
>>>   KERNEL - the kernel image file to use
>>>   ROOTFS - the rootfs image file or nfsroot directory to use
>>>   MACHINE - the machine name (optional, autodetected from KERNEL
>>> filename if unspecified)
>>>   RAMFS - boot a ramfs-based image
>>>   Simplified QEMU command-line options can be passed with:
>>> nographic - disables video console
>>> serial - enables a serial console on /dev/ttyS0
>>> kvm - enables KVM when running qemux86/qemux86-64 (VT-capable CPU
>>> required)
>>>   qemuparams="xyz" - specify custom parameters to QEMU
>>>   bootparams="xyz" - specify custom kernel parameters during boot
>>>
>>> Examples:
>>>   runqemu qemuarm
>>>   runqemu qemux86-64 core-image-sato ext3
>>>   runqemu path/to/bzImage-qemux86.bin path/to/nfsrootdir/ serial
>>>   runqemu qemux86 ramfs
>>>   runqemu qemux86 qemuparams="-m 256"
>>>   runqemu qemux86 bootparams="psplash=false"
>>> amit@amit-HP:~/OE/MCSDK/mcsdk/build$
>>>
>>> /**/
>>>
>>> The build step I followed from the arago project build link-
>>>
>>> "http://arago-project.org/wiki/index.php/Setting_Up_Build_Environment";
>>>
>>>
>>> Please let me know if I have to do something else to run the image under
>>> QEMU.
>>>
>>> --
>>> Thanks & Regards
>>> Amit Kumar
>>>
>>> --
>>>
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>>
>> --
>> Sent from Kaiten Mail. Please excuse my brevity.
>>
>
>
>
> --
> Thanks & Regards
> Amit Kumar
>
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Arago project image fail to run in QEMU

2013-07-21 Thread amit kumar

Hi Sudhangathan
Thanks for replay.
So i have to build a separate image to run under the QEMU, for that do i
need to build it with my yocto project build environment with adding the
layers.
Or do i need to use the same build environment and just change the
local.conf file?
Keystone-II is a arm processor.


Thanks & Regards
Amit K





On Sat, Jul 20, 2013 at 8:41 AM, Sudhangathan BS wrote:

> Hi Amit,
>
> You have to build separate images to be run on qemu.. You have to set it
> in your local.conf file.. i.e. u have to change your build-target..
>
> Images built to run on hardware cannot be run on qemu right now..
>
> Virtualization is only available upto processor level, and not the
> complete hardware...!
>
> Which processor is keystone-II using..?
>
> Best,
> Sudhangathan B S
>
>
> amit kumar  wrote:
>>
>>
>> Hi,
>>
>> I have built the Arago project for keystone-II successfully. The images
>> are available under the deploy/Images dir.
>>
>> I have already added my module into the kernel and recompiled the kernel
>> image.
>>
>>
>>
>> Now my doubt is before putting the image on actual hardware I want to run
>> it on QEMU. Is it possible to run the built images on QEMU?
>>
>> I tried to run using the following command but getting an error-
>>
>>
>>  /**/
>>
>> amit@amit-HP:~/OE/MCSDK/mcsdk/build$ runqemu
>> arago-tmp-external-linaro-toolchain/deploy/images/uImage-keystone-evm.bin
>> arago-tmp-external-linaro-toolchain/deploy/images/core-image-minimal-keystone-evm-20130718181345.rootfs.ubi
>> Error: unknown file arg
>> [arago-tmp-external-linaro-toolchain/deploy/images/core-image-minimal-keystone-evm-20130718181345.rootfs.ubi]
>>
>> Usage: you can run this script with any valid combination
>> of the following options (in any order):
>>   QEMUARCH - the qemu machine architecture to use
>>   KERNEL - the kernel image file to use
>>   ROOTFS - the rootfs image file or nfsroot directory to use
>>   MACHINE - the machine name (optional, autodetected from KERNEL filename
>> if unspecified)
>>   RAMFS - boot a ramfs-based image
>>   Simplified QEMU command-line options can be passed with:
>> nographic - disables video console
>> serial - enables a serial console on /dev/ttyS0
>> kvm - enables KVM when running qemux86/qemux86-64 (VT-capable CPU
>> required)
>>   qemuparams="xyz" - specify custom parameters to QEMU
>>   bootparams="xyz" - specify custom kernel parameters during boot
>>
>> Examples:
>>   runqemu qemuarm
>>   runqemu qemux86-64 core-image-sato ext3
>>   runqemu path/to/bzImage-qemux86.bin path/to/nfsrootdir/ serial
>>   runqemu qemux86 ramfs
>>   runqemu qemux86 qemuparams="-m 256"
>>   runqemu qemux86 bootparams="psplash=false"
>> amit@amit-HP:~/OE/MCSDK/mcsdk/build$
>>
>> /**/
>>
>> The build step I followed from the arago project build link-
>>
>> "http://arago-project.org/wiki/index.php/Setting_Up_Build_Environment";
>>
>>
>> Please let me know if I have to do something else to run the image under
>> QEMU.
>>
>> --
>> Thanks & Regards
>> Amit Kumar
>>
>> --
>>
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
> --
> Sent from Kaiten Mail. Please excuse my brevity.
>



-- 
Thanks & Regards
Amit Kumar
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [Package Report System]Manual check recipes name list

2013-07-21 Thread Yocto Project Package Report System

This mail was sent out by Package Report System.
It will list all the recipes which can't check upstream version by script, and 
will show how long it is since their last mannual version check.
You can check the detail information at 
http://packages.yoctoproject.org/manuallychkinfo


PackageName  Version LastChkVersion  LastChkTime
  Maintainer  NoUpgradeReason   
cups 1.6.2   1.6.2   41 days
  Saul Wold  
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [Package Report System]Upgrade recipes name list

2013-07-21 Thread Yocto Project Package Report System

This mail was sent out by Package Report System.
This message list those recipes which need to be upgraded. If maintainers 
believe some of them needn't to upgrade this time, they can fill in 
RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this 
recipe remainder until newer upstream version was detected.
Example:
RECIPE_NO_UPDATE_REASON_pn-"xxx" = "Not upgrade to 2.0 because the new version 
is unstable"
You can check the detail information at 
http://packages.yoctoproject.org/upgradepkgname


PackageName   Version   UpVersion   
  MaintainerNoUpgradeReason 
  
lsb   4.1   1.4 
  Yi Zhao
chkconfig-alternatives-native 1.3.59+AUTOINC+cd437ecbd8 6   
  Wenzong Fan
ccache3.1.8 3.1.9   
  Wenzong Fan
gettext   0.18.20.18.3  
  Wenzong Fan
systemtap-uprobes 2.1+gitAUTOINC+addec81
2.2.1+gitAUTOINC+b1c0ba9  Tom Zanussi
swabber-native0.0+gitAUTOINC+2d1fe36
0.0+gitAUTOINC+2d1fe36Saul Wold   
 
acl   2.2.512.2.52  
  Saul Wold
kconfig-frontends 3.9.0 3.10.0.0
  Saul WoldPRS Reports 
Incorrectly   
glib-networking   2.36.22.37.2  
  Saul WoldPending Glib-2.0 
Update   
docbook-sgml-dtd-4.1-native   1.0   41  
  Saul WoldPRS Reports 
Incorrectly   
docbook-sgml-dtd-3.1-native   1.0   31  
  Saul WoldPRS Reports 
Incorrectly   
createrepo0.4.110.9.9   
  Saul WoldVersions after 
0.9.* use YUM,...
guilt-native  0.33  0.35
  Saul Wold
gtk-doc-stub  0.0+gitAUTOINC+3dfd0a0
0.0+gitAUTOINC+3dfd0a0Saul Wold   
 PRS Reports Incorrectly   
vte   0.28.20.34.7  
  Saul WoldPending Glib-2.0 
Update   
oprofileui-server 0.0+gitAUTOINC+f168b8b
0.0+gitAUTOINC+f168b8bSaul Wold   
 PRS Reports Incorrectly   
texinfo   4.13a 5.1 
  Saul WoldChecking script 
parses direct...
build-appliance-image 8.0   9.0.1.  
  Saul Wold
tzcode-native 2013c 2013d   
  Saul Wold
man-pages 3.50  3.52
  Saul Wold
sato-screenshot   0.1+gitAUTOINC+3a9688e
0.1+gitAUTOINC+3a9688eSaul Wold   
 PRS Reports Incorrectly   
docbook-sgml-dtd-4.5-native   1.0   4.5 
  Saul WoldPRS Reports 
Incorrectly   
mx-1.01.4.7+gitAUTOINC+9b1db6b  
1.99.4+gitAUTOINC+6a5a7ff Saul Wold   
 PRS 1.99 is dev version   
attr  2.4.462.4.47  
  Saul Wold
cmake 2.8.11.1  2.8.11.2
  Saul Wold
clutter-gst-1.0   1.6.0 2.0.4   
  Ross Burton
clutter-gtk-1.0   1.4.2 1.4.4   
  Ross Burton
mtdev 1.1.2 1.1.3   
  Ross Burton
weston1.1.0 1.1.1   
  Ross Burton
iputils   s20101006 s20121221   
  Radu Moisan
unzip 6.0   60  
  Radu Moisan
elfutils  0.148 1.7.4   
  Radu Moisan
rxvt-unicode  9.17  9.18

Re: [yocto] linux-yocto fragments meta branch

[yocto] linux-yocto fragments meta branch

Re: [yocto] Regarding offline build

Re: [yocto] Arago project image fail to run in QEMU

Re: [yocto] Arago project image fail to run in QEMU

[yocto] [Package Report System]Manual check recipes name list

[yocto] [Package Report System]Upgrade recipes name list

7 matches

Site Navigation

Mail list logo

Footer information