All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-architecture
	<openembedded-architecture@lists.openembedded.org>,
	Yocto-mailing-list <yocto@lists.yoctoproject.org>,
	OE-core <openembedded-core@lists.openembedded.org>,
	Stephen Jolley <sjolley.yp.pm@gmail.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [yocto] Y2038 proposal
Date: Wed, 30 Nov 2022 10:40:06 +0100	[thread overview]
Message-ID: <20221130104006.526c0c71@wsk> (raw)
In-Reply-To: <CANNYZj-31p1n_f_oh3+Le4O4vYrRLquvYxzdAk4uY+EOeS_V0A@mail.gmail.com>

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

Hi Alexander,

> On Wed, 30 Nov 2022 at 09:28, Lukasz Majewski <lukma@denx.de> wrote:
> > Please find a few comments:
> >
> > 1. There is already provided meta-y2038 [1] to test if 32 bit
> > systems correctly support Y2038 problem. It uses qemu machines from
> > OE/Yocto
> >
> > 2. There are ptest available [2] to validate if the Y2038 problem
> > works correctly.
> >
> > 3. Support for running ptests mentioned in point 2. is already
> > available in the poky repository [3].  
> 
> Thanks! So there should be a
> 
> d. 'glibc-tests-ptest' is executed across all architectures - probably
> as a machine-specific selftest, and as well with qemu time set into
> the future.

+1

> 
> > It looks like the meta-y2038 can be used out of the box (after
> > checking if it still works with newest poky) when added to the
> > Yocto Project build/test infrastructure.  
> 
> Unfortunately I do not think that layer can be easily added into the
> test matrix. It has its own distro and images. No, we need to maintain
> a poky branch where the same tweaks and fixes happen. Besides, those
> fixes would need to be merged into oe-core proper eventually anyway.
> 

It would be even better if the meta-y2038 could be dropped and _all_
its functionality could be merged to poky.

That would be _awesome_.

Please just be aware that this meta layer has some fixes for some
packages (for Y2038 ready glibc).

> Alex




Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-11-30  9:40 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 15:44 Yocto Project Status 29 November 2022 (WW48) sjolley.yp.pm
2022-11-30  8:07 ` Y2038 proposal Alexander Kanavin
2022-11-30  8:28   ` [yocto] " Lukasz Majewski
2022-11-30  9:07     ` Alexander Kanavin
2022-11-30  9:40       ` Lukasz Majewski [this message]
2022-11-30  9:48         ` Alexander Kanavin
2022-11-30 21:14     ` Alexander Kanavin
2022-12-01  8:28       ` Lukasz Majewski
2022-11-30 10:52   ` Stephen John Smoogen
2022-11-30 11:04     ` Lukasz Majewski
2022-11-30 12:09     ` Alexander Kanavin
2022-11-30 11:02   ` Alexandre Belloni
2022-11-30 11:40     ` [OE-core] " Richard Purdie
2022-11-30 12:07       ` Alexander Kanavin
2022-11-30 12:09         ` Lukasz Majewski
2022-11-30 12:11         ` Richard Purdie
2022-11-30 13:15   ` [Openembedded-architecture] " Richard Purdie
2022-11-30 13:36     ` [OE-core] " Lukasz Majewski
2022-11-30 14:20       ` Richard Purdie
2022-11-30 16:46         ` [yocto] " Ross Burton
2022-11-30 16:56           ` Alexandre Belloni
2022-11-30 16:59             ` Richard Purdie
2022-12-05 10:00               ` Ola x Nilsson
2022-12-05 11:04                 ` Richard Purdie
2022-12-05 11:05                   ` Ola x Nilsson
2022-12-01 10:27     ` Alexander Kanavin
2022-12-01 10:36       ` Richard Purdie
2022-11-30 16:38   ` Khem Raj
2022-12-02  8:54   ` [OE-core] " Matt Johnston
2022-12-05 23:24     ` Richard Purdie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221130104006.526c0c71@wsk \
    --to=lukma@denx.de \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-architecture@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=sjolley.yp.pm@gmail.com \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.