From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7304933055699877888 X-Received: by 2002:a17:90a:9b82:b0:285:7e36:a6ab with SMTP id g2-20020a17090a9b8200b002857e36a6abmr17922233pjp.2.1701252676427; Wed, 29 Nov 2023 02:11:16 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a17:90a:fa89:b0:285:12aa:ad9c with SMTP id cu9-20020a17090afa8900b0028512aaad9cls65912pjb.0.-pod-prod-07-us; Wed, 29 Nov 2023 02:11:15 -0800 (PST) X-Google-Smtp-Source: AGHT+IFNmPaY0o/XRgXtJTmb6zWAWwQ9G6jDSmjK6TfeUfhpUPnBNdtbYUBDFyiS2HzZ6eUaGMo5 X-Received: by 2002:a17:90a:49:b0:280:6b5b:3f40 with SMTP id 9-20020a17090a004900b002806b5b3f40mr16418774pjb.8.1701252675262; Wed, 29 Nov 2023 02:11:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1701252675; cv=none; d=google.com; s=arc-20160816; b=MG1sNDiJ8JD+L3YQgM93H+t3uRec5/pVkYIzqI9Y/X0jCm1Q0vzf/D2vX2pYslvZ96 ZEYIgm1QzqykJEzgTY8AEbAvJReJmqX49qaW4SAnpUq20I6O9iwga5HKb927I+vh9mRP B5ECZP7jh23GOYk94M7YuoE2MGnxFNh9eoy5hUlSa0/aXN98pA6avYk+O7fsmkY3h6wn mXJ/VaQDR9WlP4LTN9silkYXQFhEg6rQa+RiU8I1UcW+ZeW+XD1JbWQJYQINSKrZq1nR vN7H60VC5kC/5Y8IpvnVrqwoiiNnO5rxY8nGfgXKo1LMeItOC5g1CB4uR/6gsqqbFCnk SHbg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:cc:to:from:date; bh=FkttTG9Zde9vF7bZlopAZoTuTrnue2qXz0DgdzVFA5A=; fh=ayfAe8qmvuhnFlecYJaCAyE02arlonJgV2H/zKorYgo=; b=b+9eU3w09AEO8TLwitOUeeSjymDxbOgsePEKFzaWnbAYWWHIorjuOLwwSgi5BiuolP gPoEDZpvkqc20xoPFbMlWopR5f242eSdru7pIvtO0zGp3AdbI8VdfLh2IY5Sl1EbHdv4 F00ricKZsdXfo2f5dl4m8bTXIDZVB1MUEX3LovvS2LBljZIAX/B0rYHoPNPAlO6zCkg5 VUaOm8okH0drLqAg1wolPrDsRWiYtEpFf+Ah59nGPAWdooiC9+VRqqkjzROLY+P7bgKP 2Q8ilwJKr1IC1JytsyyJGJkD70/IKY1Ftgn7jE97X8nzivPnzyjJ9Yc/5VODRmrx6UOo jTIg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of ibr@radix50.net designates 85.214.156.166 as permitted sender) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id t19-20020a170902d29300b001c9dae59993si722118plc.13.2023.11.29.02.11.13 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Wed, 29 Nov 2023 02:11:15 -0800 (PST) Received-SPF: pass (google.com: domain of ibr@radix50.net designates 85.214.156.166 as permitted sender) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ibr@radix50.net designates 85.214.156.166 as permitted sender) smtp.mailfrom=ibr@radix50.net Received: from ilbers.de (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8+deb9u1) with ESMTPSA id 3ATAB89X024229 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 29 Nov 2023 11:11:09 +0100 Date: Wed, 29 Nov 2023 11:11:07 +0100 From: Baurzhan Ismagulov To: isar-users@googlegroups.com Cc: Jan Kiszka Subject: Re: [PATCH 1/1] bitbake: backport fetch2/aws: forward env-vars used in gitlab-ci K8s Message-ID: Mail-Followup-To: isar-users@googlegroups.com, Jan Kiszka References: <20231124075037.655070-1-felix.moessbauer@siemens.com> <3417bbce-a07d-4280-afa3-cd5d9f825b88@siemens.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3417bbce-a07d-4280-afa3-cd5d9f825b88@siemens.com> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: mUKzK8CdWav9 On 2023-11-25 16:19, 'Jan Kiszka' via isar-users wrote: > As discussed with Felix already in person: The only issue would be if we > decided to update once more in the current stable series. Then there is > the risk that we forget about this patch and overwrite it because > upstream stable will not see it (it's a feature, not a fix). Or is 2.0.x > EOL anyway? I think that we as maintainers should take care of forward-porting the change whenever we update bitbake. Currently, we use 2.0 due to the LTS. We estimate that the upstream change might become part of 2.6.1, which would mean we might still have 2.4, 2.6 and / or 2.8 (which is the next LTS). With kind regards, Baurzhan