[yocto] bitbake is corrupting my files during unpacking

[MOHAMMAD RASIM]

Yes I made a pull request to the master branch 
https://github.com/openembedded/openembedded-core/pull/34

note that this issue can be replicated by unzipping any linux-kernel (I 
think), I tested that it exist in the zip file of torvalds tree 
https://github.com/torvalds/linux/archive/master.zip

so it's easy to replicate and test

Also, to anyone how face the same issue and find this message, I solved 
the issue without patching unzip by using tar.gz file instead of unzip 
file (thanks to github for providing that) so instead of 
https://github.com/torvalds/linux/archive/master.zip use 
https://github.com/torvalds/linux/archive/master.tar.gz


Thanks


On 07/23/2018 09:51 PM, Burton, Ross wrote:
> Yes, please do.  Mohammad, as you can replicate this on demand, would
> you be able to fix the unzip recipe with the patch in that bug and
> send a patch?
>
> Ross
>
> On 23 July 2018 at 19:42, Andre McCurdy <armccurdy at gmail.com> wrote:
>> On Sat, Jul 21, 2018 at 12:55 AM, MOHAMMAD RASIM
>> <mohammad.rasim96 at gmail.com> wrote:
>>> well apparently this is caused by the unzip binary that is compiled by the
>>> openembedded unzip recipe.
>>> If I unzip the same zip file with the unzip binary that is shipped with my
>>> system(manjaro) then the files are not corrupted but when I use the unzip
>>> binary compiled by the openembedded recipe I get error and file corruptions.
>>> These are some of the errors I get when unzipping with the openembedded
>>> unzip:
>>> ...
>>> symlink error: File name too long
>>>
>>> This error happens to multiple files where the file is symlinked to the
>>> content of the file and not to a path !
>>> Where should I report this bug ? openembedded ? unzip upstream ?
>> If you google the "symlink error" you should find multiple hits, which
>> all indicate a known bug in upstream unzip 6.0.
>>
>> So, it should be reported upstream. However, given that the last unzip
>> release is now over 9 years old and there doesn't appear to be a
>> public upstream development branch, the chances of getting a timely
>> response don't look too good.
>>
>> We should probably add the fix to the unzip recipe in oe-core:
>>
>>    https://bugzilla.redhat.com/show_bug.cgi?id=972427
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto