From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7304933055699877888 X-Received: by 2002:a05:6e02:1be5:b0:35d:3a75:1b6e with SMTP id y5-20020a056e021be500b0035d3a751b6emr1964796ilv.23.1701333939913; Thu, 30 Nov 2023 00:45:39 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:6e02:1a27:b0:35c:8345:23ef with SMTP id g7-20020a056e021a2700b0035c834523efls379236ile.0.-pod-prod-03-us; Thu, 30 Nov 2023 00:45:39 -0800 (PST) X-Google-Smtp-Source: AGHT+IFR17QwZWkjKdBqD8DYIbP5aa2301D3TPlSp3LeCb82qTb68MkaaeGM5aFo8TwXmQJzxXMZ X-Received: by 2002:a92:c534:0:b0:35d:3b79:7617 with SMTP id m20-20020a92c534000000b0035d3b797617mr1232406ili.0.1701333938997; Thu, 30 Nov 2023 00:45:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1701333938; cv=none; d=google.com; s=arc-20160816; b=M2TSECt+AY4gD8+FOKL36oKu2sW8OO8mBA/37nNCylU1PP3vh8gRtoi024Fz4BiQOe JGmvm0u+xFElph1vufZ23xmZ+cHmTg6rJxqIHwKsIvEyjaDMq5YxZMLWvPHeVxy5qs3R nn2WamSddNC5T0lwm+S0cOnHYKtAMvM49qkRjq3icQhpWzXSn+bANgSuBuO9PXp6R8BX lqW0PBFNBtJ81mkuW2qpizBHo1hdec6kxlx4ppqXz207ociJil3Fz/32M7xds0KwkKE/ vkUgoK8Fo9EtiCzfymO+zbO62wZUnsB955ohD5xu9KIhHTeBXFgsttECjCt267jsVHn3 XnXw== 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=njitj31d/c2DOFdUp6H3iSyOL1LR6X/NHrSHwsz1yw8=; fh=TZMi8RRN4QhF+gIkdHi+lN9D6i9OAj8nx66S67YGau0=; b=tb2D0bShKQKYx5cEdvu3xJum1XIbAZPt0aPAdFQh8dISAatcmkMmA31pn5BHg1jfJV YZjDHMZNJoplnGSnk5UonZ2OOugcClGNpCAPxL8hGC8GhuaY493KucJOd6Jof4+rJzgJ BME1TNFnmacuFax3pHPC+rmW6RfkV0Xhz70AFw2PQgvijQkhvqSRibvj0c9LmRji0Jw3 oWJ0+JkwU30FIvcwRgrvFUAsx9Wb5Iw1AlDHmN5ExPPJ5BkRWT/22e0vRGGrIiBeL+P1 hDIemPw9Kx+Kv2fT28hcltoluYhg6+pR5jzKwjUbq4QZFUilkA1mpk1IcP5s3fjic9J5 xPlw== 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 g10-20020a056e021e0a00b0035c8cf634b9si242128ila.0.2023.11.30.00.45.37 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Thu, 30 Nov 2023 00:45:38 -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 3AU8jVkI028822 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 30 Nov 2023 09:45:33 +0100 Date: Thu, 30 Nov 2023 09:45:31 +0100 From: Baurzhan Ismagulov To: isar-users@googlegroups.com Cc: "Kiszka, Jan" , "MOESSBAUER, Felix" 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, "Kiszka, Jan" , "MOESSBAUER, Felix" References: <20231124075037.655070-1-felix.moessbauer@siemens.com> <3417bbce-a07d-4280-afa3-cd5d9f825b88@siemens.com> <4a07c292ac87d6d8f261b019a6380e804b58c90c.camel@siemens.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4a07c292ac87d6d8f261b019a6380e804b58c90c.camel@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: rpWDBSq0h1c9 On 2023-11-30 02:48, MOESSBAUER, Felix wrote: > > 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). > > Hi, this sounds reasonable. Is there any documentation, where the > backported patches are tracked? We've thought about introducing bitbake/README.Isar, but it would still be something that one has to actively check, which is then not much better than e.g. git log --pretty=oneline --abbrev-commit --no-decorate bitbake: 2253ad4d bitbake: backport fetch2/aws: forward env-vars used in gitlab-ci K8s 05710647 bitbake: update to Bitbake 2.0.12 a9bbdeeb bitbake: update to Bitbake 2.0.5 2a10bbb9 utils: Ensure shell function failure in python logging is correct 01084712 bitbake-diffsigs: break on first dependent task difference a5bbc86f bitbake-diffsigs: make finding of changed signatures more robust 3c99609b bitbake: Update to 1.50.5 release c9252baf bitbake: Update to 1.50.4 release 522ac8f8 bitbake: Update to 1.46.2 release c2aae245 bitbake: update to version 1.44.0 ce34a501 bitbake: Update to fixed master revision 1fb4c991 bitbake: Update to the release 1.40.0 a6e101f5 Update bitbake from the upstream. 3a0254fc bitbake: Update to 1.31.2+g80f377e ff22b2b1 Add bitbake master 7c849be The better alternative would be a testcase. With kind regards, Baurzhan