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 9C5B1C76196 for ; Thu, 6 Apr 2023 10:21:04 +0000 (UTC) Received: from smtpout.cvg.de (smtpout.cvg.de [87.128.211.67]) by mx.groups.io with SMTP id smtpd.web11.154927.1680776456819242970 for ; Thu, 06 Apr 2023 03:21:01 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@sigma-chemnitz.de header.s=v2022040800 header.b=kw7uAtCo; spf=pass (domain: sigma-chemnitz.de, ip: 87.128.211.67, mailfrom: enrico.scholz@sigma-chemnitz.de) Received: from mail-mta-2.intern.sigma-chemnitz.de (mail-mta-2.intern.sigma-chemnitz.de [192.168.12.70]) by mail-out-2.intern.sigma-chemnitz.de (8.16.1/8.16.1) with ESMTPS id 336AKqgb1317970 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=OK) for ; Thu, 6 Apr 2023 12:20:52 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sigma-chemnitz.de; s=v2022040800; t=1680776452; bh=0TpaNGl2SrgQxCA+7jMIG+uAhA0xi6lMDq0LMERtX/I=; l=1518; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=kw7uAtCoJc5DOH79JUFuY/bLJZtn+MsTfBl4Kim6vBkOWFnprjoR61Iv4qhvqMf3N y6b6FWH5xk2ngKrNCEJdjEQNwcc1+8nWN4b5+V0MKFmghNq2Vixdx8vEmonDgNbh45 8FwvUjBLcDlifJ7QoNJfSFmSvqDvkUPGn/GjchZhzMYqgtNyPacSibI8DglEYmmWlp qNVuErB9VJ99ffzaUysHZkB0KVgYkOFd4qEpnsaJkSpwNdn0RyaMOK4wYoma1rdURj NIDuNHwr5kcU8Gk3EQcxvWlbo+uJ4JgCgKTOk/g8i9Uc73KL6OqvXqAS5Svl0r1drM MUyg4MJq1eI0Q== Received: from reddoxx.intern.sigma-chemnitz.de (reddoxx.sigma.local [192.168.16.32]) by mail-mta-2.intern.sigma-chemnitz.de (8.16.1/8.16.1) with ESMTP id 336AKkXT1675974 for from enrico.scholz@sigma-chemnitz.de; Thu, 6 Apr 2023 12:20:46 +0200 Received: from mail-msa-2.intern.sigma-chemnitz.de ([192.168.12.72]) by reddoxx.intern.sigma-chemnitz.de with ESMTP id 60P2BMO3MH; Thu, 06 Apr 2023 12:20:46 +0200 Received: from ensc-pc.intern.sigma-chemnitz.de (ensc-pc.intern.sigma-chemnitz.de [192.168.3.24]) by mail-msa-2.intern.sigma-chemnitz.de (8.16.1/8.16.1) with ESMTPS id 336AKjwh1279212 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 6 Apr 2023 12:20:45 +0200 Received: from ensc by ensc-pc.intern.sigma-chemnitz.de with local (Exim 4.96) (envelope-from ) id 1pkMjV-00070B-2L; Thu, 06 Apr 2023 12:20:45 +0200 From: Enrico Scholz To: Richard Purdie Cc: Frederic Martinsons , bitbake-devel@lists.openembedded.org Subject: Re: [bitbake-devel] [PATCH] fetch:crate: create versioned 'name' entries References: <20230405101609.3309660-1-enrico.scholz@sigma-chemnitz.de> <17530ADB1695B5D1.3977@lists.openembedded.org> <088f748bc07ec93c833dbdbf1a941225de62f553.camel@linuxfoundation.org> Date: Thu, 06 Apr 2023 12:20:45 +0200 In-Reply-To: <088f748bc07ec93c833dbdbf1a941225de62f553.camel@linuxfoundation.org> (Richard Purdie's message of "Thu, 06 Apr 2023 09:45:10 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Sender: Enrico Scholz X-REDDOXX-Id: 642e9cfe5038ce378780d0cc 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 ; Thu, 06 Apr 2023 10:21:04 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/bitbake-devel/message/14668 Richard Purdie writes: >> > It will break cargo related recipes which were created between >> > 2023-03-16 and 2023-03-31.=C2=A0 Packages before this date do not >> > contain sha256sum and after this date, they have an explicit >> > 'name' (which matches the one generated by my patch). >>=20 >> Ok, I guess these dates match my patches series, if I do things >> rights, I handle all the recipes I know of (in meta-openembedded and >> openembedded-core at least)=C2=A0 > > This now gives me a problem as rc1 for 4.2 built yesterday. I'm > guessing we don't want a stable release series with one form for urls > for six months and a different one in master? > > Does this mean I need to scrap rc1, merge this, wait for the recipe > updates and then rebuild the release? To avoid breaking builds: 1. OE recipes without explicit ';name=3D' need to be updated; this can be done by 'bitbake -c update_crates'. Afais, this affects only =20=20=20 | meta/recipes-devtools/python/python3-bcrypt_4.0.1.bb | meta/recipes-devtools/python/python3-cryptography_39.0.2.bb and in oe-meta | meta-oe/recipes-core/uutils-coreutils/uutils-coreutils_0.0.17.bb | meta-python/recipes-devtools/python/python3-pyruvate_1.1.2.bb 2. the patch can be applied to bitbake 3. [optionally] change cargo-update-recipe-crates.bbclass to remove the explicit (and now redundant) ';name=3D' from generated SRC_URI list. This can be done post-mickledore Enrico