From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id CC47CC07E9D for ; Mon, 26 Sep 2022 11:21:56 +0000 (UTC) Received: from mail-wr1-f42.google.com (mail-wr1-f42.google.com [209.85.221.42]) by mx.groups.io with SMTP id smtpd.web08.27054.1664191312393280772 for ; Mon, 26 Sep 2022 04:21:52 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=bGLHy/By; spf=pass (domain: gmail.com, ip: 209.85.221.42, mailfrom: martin.jansa@gmail.com) Received: by mail-wr1-f42.google.com with SMTP id r7so9728777wrm.2 for ; Mon, 26 Sep 2022 04:21:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=aEV7K3gm2S/XJ2wp+ZeAHOhxJJW0GtE6t5odxVmCm8Y=; b=bGLHy/By4MsO/+zeoiI0r5piyKnbRIqAACY1MkjXDEJRrq2G66tn3puvdU4npmHry9 IJvuSvoLbwsDlOPyHtNTfyGjUbh+ndS6FzwXFVw1NsAe0+uYuoy54tM44KFsc2+nZU0e jNJ85p1DHGOxi9Sx7p3suFNM5gpPwl7VHYZ6QMDocZkEjpAE+DTXYTYQgwihHt16bhZD nkKQlhVih47RMdMILdrXk53a4ceeS3K9Tsr40ZcQXEhrLNQfOmKIDPMXp2Gpy0i1Z077 OdoR178y/l1UlFP65p2xAPeMXhHTLBk6nhU5Ppcw1xM0xs+l1NXMgKMtPZ5VAd2T2W1q TQwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=aEV7K3gm2S/XJ2wp+ZeAHOhxJJW0GtE6t5odxVmCm8Y=; b=3lIbGjhHe8c1YkCGmmDEzcmzUjPiTx3kEseeDCcISiA5VzjomKIA2AnmvDgPxrLhuD 0N9314cl5BU8Y6yIqdq/Q9JrpoiSTuNt8YQhIISLdnP6i0ul+mjsJGo4uos4tAFyOYqj qb3OlDvbClFwPYsYTEfdMqMk83JZjHE0SzJZ+iY16gXm7MkLxluhKZ9R7M54d5lQmqTT SeK/Gv/PKxc8tF6mMx/mI2W0+8Ec1GU0GQ9uexG1YtxgSF1a0BAaeA5NAqBdfqAwq14d 2WakAqz/B8P36JG/HupAMBrtFwyA7cQ8QLS/Dl4FsIxY4r7061U+KFEK750e19/8cg/F FpAQ== X-Gm-Message-State: ACrzQf2gV8cAtr2HXq+eVKlXzG4XvfzkzHywjq5xsbI1OkWRnTL6lBrw kQcIRngGdBTjXYuY++tKNItUdzSMj1F+lA3nVy0= X-Google-Smtp-Source: AMsMyM6yGmRirCJFxXnFPd7bnGIdnedGKQFMT1RTwAXpAdtfSUdj+P3/36D0liaEAQYtYy+4/ENMOqF4g1pjKwvVI3g= X-Received: by 2002:a5d:678a:0:b0:22a:c9d9:443d with SMTP id v10-20020a5d678a000000b0022ac9d9443dmr12523471wru.129.1664191310773; Mon, 26 Sep 2022 04:21:50 -0700 (PDT) MIME-Version: 1.0 References: <20220926090604.23397-1-andriy.danylovskyy@streamunlimited.com> <15447.1664183632584990375@lists.openembedded.org> In-Reply-To: <15447.1664183632584990375@lists.openembedded.org> From: Martin Jansa Date: Mon, 26 Sep 2022 13:21:38 +0200 Message-ID: Subject: Re: [OE-core] [PATCH] classes/patch: move QUILT_PC for patching consistency To: Andriy Danylovskyy Cc: openembedded-core@lists.openembedded.org Content-Type: multipart/alternative; boundary="000000000000eac16705e992bb3d" List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Mon, 26 Sep 2022 11:21:56 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/171061 --000000000000eac16705e992bb3d Content-Type: text/plain; charset="UTF-8" > I am aware of the "force-unpack + patch" scenario, discussed in https://lists.yoctoproject.org/g/yocto/topic/89948013#56602, and this patch, sadly, doesn't fix that. Wasn't this scenario fixed by: c9d36882044b1c633d8611a77df54cd68c9bee25 ? It was for me. On Mon, Sep 26, 2022 at 11:13 AM Andriy Danylovskyy < andriy.danylovskyy@streamunlimited.com> wrote: > I am aware of the "force-unpack + patch" scenario, discussed in > https://lists.yoctoproject.org/g/yocto/topic/89948013#56602, > and this patch, sadly, doesn't fix that. > But it does fix another face of it, which IMO is even worse than a failing > build - a false positive, where updates to a source are ignored, > and the package is "successfully" built from the previous version. > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#171055): > https://lists.openembedded.org/g/openembedded-core/message/171055 > Mute This Topic: https://lists.openembedded.org/mt/93922956/3617156 > Group Owner: openembedded-core+owner@lists.openembedded.org > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ > Martin.Jansa@gmail.com] > -=-=-=-=-=-=-=-=-=-=-=- > > --000000000000eac16705e992bb3d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> I am aware of the "force-unpack + patch&quo= t; scenario, discussed in=C2=A0https://list= s.yoctoproject.org/g/yocto/topic/89948013#56602, and this patch, sadly,= doesn't fix that.

Wasn't this scenario fi= xed by: c9d36882044b1c633d8611a77df54cd68c9bee25 ?

It was for me.

On Mon, Sep 26, 2022 at 11:13 AM Andriy Danylovskyy &l= t;andriy.danylovs= kyy@streamunlimited.com> wrote:
I am aware of the "force-unpack + patch&qu= ot; scenario, discussed in https://lists.yo= ctoproject.org/g/yocto/topic/89948013#56602,
and this patch, sadly, doesn't fix that.
But it does fix anothe= r face of it, which IMO is even worse than a failing build - a false positi= ve, where updates to a source are ignored,
and the package is "succ= essfully" built from the previous version.

-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
Links: You receive all messages sent to this group.
View/Reply Online (#171055): https:= //lists.openembedded.org/g/openembedded-core/message/171055
Mute This Topic: https://lists.openembedded.org/mt= /93922956/3617156
Group Owner: openembedded-core+owner@lists.openembedded.org<= br> Unsubscribe: https://lists.openembedded.org/= g/openembedded-core/unsub [Martin.Jansa@gmail.com]
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-

--000000000000eac16705e992bb3d--