[yocto] bitbake is corrupting my files during unpacking

[MOHAMMAD RASIM]

Hi,

I'm new to openembedded and yocto. I'm using the openpli meta layers to 
build openembedded https://github.com/OpenPLi/openpli-oe-core

Now I'm trying to build a recipe for the kernel but I encountered a 
strange issue, bitbake is corrupting my source files when unpacking from 
zip file (http link of zip file) but not when using git to get the 
source the files are fine and not corrupted, the downloaded zip file 
itself is not corrupted and If I unzip it from the sources 
directory(outside bitbake environment) then the resulting files are not 
corrupted

The zip file I'm downloading 
https://github.com/PLi-metas/linux-amlogic/archive/amlogic-3.14-nougat.zip

examples of corruption I saw :

1- /drivers/w1/slaves/Kconfig (this file is converted to a broken 
symlink not to a path but to the content of the file itself, see:

file 
build/tmp/work-shared/k2pro_s905/kernel-source/drivers/w1/slaves/Kconfig
build/tmp/work-shared/k2pro_s905/kernel-source/drivers/w1/slaves/Kconfig: 
broken symbolic link to #\012# 1-wire slaves 
configuration\012#\012\012menu "1-wire Slaves"\012\012config 
W1_SLAVE_THERM\012\011tristate "Thermal family 
implementation"\012\011help\012\011  Say Y here if you want to connect 
1-wire thermal sensors to your\012\011 wire.\012\012config 
W1_SLAVE_SMEM\012\011tristate "Simple 64bit memory family 
implementation"\012\011help\012\011  Say Y here if you want to connect 
1-wire\012\011  simple 64bit memory rom(ds2401/ds2411/ds1990*) to your 
wire.\012\012config W1_SLAVE_DS2408\012\011tristate "8-Channel 
Addressable Switch (IO Expander) 0x29 family support 
(DS2408)"\012\011help\012\011 Say Y here if you want to use a 
1-wire\012\011  DS2408 8-Channel Addressable Switch device 
support\012\012config W1_SLAVE_DS2408_READBACK\012\011bool "Read-back 
values written to DS2408's output register"\012\011depends on 
W1_SLAVE_DS2408\012\011default y\012\011help\012\011  Enabling this will 
cause the driver to read back the values written\012\011  to the chip's 
output register in order to detect errors.\012\012\011  This is slower 
but useful when debugging chips and/or busses.\012\012config 
W1_SLAVE_DS2413\012\011tristate "Dual Channel Addressable Switch 0x3a 
family support (DS2413)"\012\011help\012\011  Say Y here if you want to 
use a 1-wire\012\011  DS2413 Dual Channel Addressable Switch device 
support\012\012config W1_SLAVE_DS2423\012\011tristate "Counter 1-wire 
device (DS2423)"\012\011select CRC16\012\011help\012\011  If you enable 
this you can read the counter values available\012\011  in the DS2423 
chipset from the w1_slave file under the\012\011  sys file 
system.\012\012\011  Say Y here if you want to use a 1-wire\012\011  
counter family device (DS2423).\012\012config 
W1_SLAVE_DS2431\012\011tristate "1kb EEPROM family support 
(DS2431)"\012\011help\012\011  Say Y here if you want to use a 
1-wire\012\011  1kb EEPROM family device (DS2431)\012\012config 
W1_SLAVE_DS2433\012\011tristate "4kb EEPROM family support 
(DS2433)"\012\011help\012\011  Say Y here if you want to use a 
1-wire\012\011  4kb EEPROM family device (DS2433).\012\012config 
W1_SLAVE_DS2433_CRC\012\011bool "Protect DS2433 data with a 
CRC16"\012\011depends on W1_SLAVE_DS2433\012\011select 
CRC16\012\011help\012\011  Say Y here to protect DS2433 data with a 
CRC16.\012\011  Each block has 30 bytes of data and a two byte 
CRC16.\012\011  Full block writes are only allowed if the CRC is 
valid.\012\012config W1_SLAVE_DS2760\012\011tristate "Dallas 2760 
battery monitor chip (HP iPAQ & others)"\012\011depends on 
W1\012\011help\012\011  If you enable this you will have the DS2760 
battery monitor\012\011  chip support.\012\012\011  The battery monitor 
chip is used in many batteries/devices\012\011  as the one who is 
responsible for charging/discharging/monitoring\012\011  Li+ 
batteries.\012\012\011  If you are unsure, say N.\012\012config 
W1_SLAVE_DS2780\012\011tristate "Dallas 2780 battery monitor 
chip"\012\011depends on W1\012\011help\012\011  If you enable this you 
will have the DS2780 battery monitor\012\011  chip support.\012\012\011  
The battery monitor chip is used in many batteries/devices\012\011  as 
the one who is responsible for charging/discharging/monitoring\012\011  
Li+ batteries.\012\012\011  If you are unsure, say N.\012\012config 
W1_SLAVE_DS2781\012\011tristate "Dallas 2781 battery monitor 
chip"\012\011depends on W1\012\011help\012\011  If you enable this you 
will have the DS2781 battery monitor\012\011  chip support.\012\012\011  
The battery monitor chip is used in many batteries/devices\012\011  as 
the one who is responsible for charging/discharging/monitoring\012\011  
Li+ batteries.\012\012\011  If you are unsure, say N.\012\012config 
W1_SLAVE_DS28E04\012\011tristate "4096-Bit Addressable 1-Wire EEPROM 
with PIO (DS28E04-100)"\012\011depends on W1\012\011select 
CRC16\012\011help\012\011  If you enable this you will have the 
DS28E04-100\012\011  chip support.\012\012\011  Say Y here if you want 
to use a 1-wire\012\011  4kb EEPROM with PIO family device 
(DS28E04).\012\012\011  If you are unsure, say N.\012\012config 
W1_SLAVE_BQ27000\012\011tristate "BQ27000 slave support"\012\011depends 
on W1\012\011help\012\011  Say Y here if you want to use a hdq\012\011  
bq27000 slave support.\012\012endmenu\012

2- /linux-amlogic-amlogic-3.14-nougat/security/keys/request_key_auth.c 
(this file is not extracted)


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20180721/d0c99e9f/attachment-0001.html>