Re: skip mismatching check for pages requires the linux tarball

On Sun, 2025-08-31 at 14:54 +0200, Pierre Labastie wrote:
> On Sun, 2025-08-31 at 17:23 +0800, Zhang Wen wrote:
> > Since we're using patch tarball for the kernel in LFS, the check
> > just
> > cannot pass.
> 
> For some reason, replies to this mail are dated earlier than the
> original post. But I have seen all.

We have:

Received: from rivendell.linuxfromscratch.org (rivendell.linuxfromscratch.org [208.118.68.85])
        (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
         key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384
         client-signature RSA-PSS (2048 bits) client-digest SHA256)
        (Client CN "linuxfromscratch.org", Issuer "R13" (verified OK))
        by xry111.site (Postfix) with ESMTPS id 2C5BC66A04
        for <[email protected]>; Sat, 30 Aug 2025 20:50:25 -0400 (EDT)

Received: from mail-ej1-f49.google.com (mail-ej1-f49.google.com [209.85.218.49])
        (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
         key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256
         client-signature RSA-PSS (2048 bits) client-digest SHA256)
        (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK))
        by rivendell.linuxfromscratch.org (Postfix) with ESMTPS id 53ED61C0DC3
        for <[email protected]>; Sun, 31 Aug 2025 00:50:15 +0000 (GMT)

Received: by mail-ej1-f49.google.com with SMTP id a640c23a62f3a-b0418f6fc27so26074966b.3
        for <[email protected]>; Sat, 30 Aug 2025 17:50:15 -0700 (PDT)

So my server, the linuxfromscratch.org server, and the Google server all
agree the mail is delivered around 31 Aug 2025 00:50 GMT.  But then:

Date: Sun, 31 Aug 2025 17:23:53 +0800

So it's claimed to be sent later than we receive it.

Either it traveled faster than light, or the local time of the OP is
incorrect, or we have a bug in the OP's mail client.

-- 
Xi Ruoyao <[email protected]>

-- 
http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
Unsubscribe: See the above information page