2038 time problem fix in yocto #yocto #linux #kernel #zeus


dhandhukiya.paresh@...
 

Hi,

We need to have a fix for 2038 problem for out 32 bit based product which is running Yocto (Linux).
2038 time problem was fixed in Linux kernel recently https://www.theregister.com/2020/10/19/linux_5_10_y2k38_fixes/

This issue is fixed and kernel and glibc, these version of kernel is not part of the yocto yet.
Does anyone know the timeline for this?

Also, There are other packages also affected by 2038 time problem in Linux.
Is there any timeline to fix these issues in other packages.
Its understandable that yocto project include these packages when new version of the package comes and doesnt maintain it.
But is there any central monitoring in yocto community about fixing this issue throughout yocto ?
Can any one please help me with above detail?

Thanks,
Paresh Dhandhukiya


Robert Berger
 

Hi,

On 03/02/2021 09:13, dhandhukiya.paresh@gmail.com wrote:
Hi,
We need to have a fix for 2038 problem for out 32 bit based product which is running Yocto (Linux).
2038 time problem was fixed in Linux kernel recently https://www.theregister.com/2020/10/19/linux_5_10_y2k38_fixes/
How about switching to a more recent version of the YP then zeus?

A recent version uses the 5.10.x kernel.

... but it does not automatically fix everything.

Regards,

Robert


dhandhukiya.paresh@...
 

As you mentioned updating the kernel does not fix the other packages.
And we don't have know how about each linux package so its not that easy to fix it by ourself.
So, I am trying to know if there is any concrete plan in Yocto Community to fix this issue at yocto level and any timeline to do it?