All of lore.kernel.org
 help / color / mirror / Atom feed
* 2038 time problem fix in yocto #kernel #linux #yocto #zeus
@ 2021-02-03  7:13 dhandhukiya.paresh
  2021-02-03 10:29 ` [yocto] " Robert Berger
  0 siblings, 1 reply; 3+ messages in thread
From: dhandhukiya.paresh @ 2021-02-03  7:13 UTC (permalink / raw)
  To: yocto

[-- Attachment #1: Type: text/plain, Size: 807 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 949 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [yocto] 2038 time problem fix in yocto #kernel #linux #yocto #zeus
  2021-02-03  7:13 2038 time problem fix in yocto #kernel #linux #yocto #zeus dhandhukiya.paresh
@ 2021-02-03 10:29 ` Robert Berger
  2021-02-04  4:53   ` dhandhukiya.paresh
  0 siblings, 1 reply; 3+ messages in thread
From: Robert Berger @ 2021-02-03 10:29 UTC (permalink / raw)
  To: dhandhukiya.paresh, yocto

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 2038 time problem fix in yocto #kernel #linux #yocto #zeus
  2021-02-03 10:29 ` [yocto] " Robert Berger
@ 2021-02-04  4:53   ` dhandhukiya.paresh
  0 siblings, 0 replies; 3+ messages in thread
From: dhandhukiya.paresh @ 2021-02-04  4:53 UTC (permalink / raw)
  To: yocto

[-- Attachment #1: Type: text/plain, Size: 301 bytes --]

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?

[-- Attachment #2: Type: text/html, Size: 309 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-02-04  4:53 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-02-03  7:13 2038 time problem fix in yocto #kernel #linux #yocto #zeus dhandhukiya.paresh
2021-02-03 10:29 ` [yocto] " Robert Berger
2021-02-04  4:53   ` dhandhukiya.paresh

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.