public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "mikuback@linux.microsoft.com" <mikuback@linux.microsoft.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Sean Brogan <sean.brogan@microsoft.com>,
	"Barkelew, Bret" <bret.barkelew@microsoft.com>,
	"Gao, Liming" <gaoliming@byosoft.com.cn>
Subject: Re: [PATCH v1 1/1] .azurepipelines: Use Python 3.10.6+
Date: Tue, 30 Aug 2022 03:01:19 +0000	[thread overview]
Message-ID: <CO1PR11MB492925DEA73717C7B48F6C54D2799@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220825153658.944-1-mikuback@linux.microsoft.com>

Reviewed-by: Michael D Kinney <michael.d.kinney@intel.com>

Mike 

> -----Original Message-----
> From: mikuback@linux.microsoft.com <mikuback@linux.microsoft.com>
> Sent: Thursday, August 25, 2022 8:37 AM
> To: devel@edk2.groups.io
> Cc: Sean Brogan <sean.brogan@microsoft.com>; Barkelew, Bret <bret.barkelew@microsoft.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>; Gao, Liming <gaoliming@byosoft.com.cn>
> Subject: [PATCH v1 1/1] .azurepipelines: Use Python 3.10.6+
> 
> From: Michael Kubacki <michael.kubacki@microsoft.com>
> 
> REF:https://bugzilla.tianocore.org/show_bug.cgi?id=3891
> 
> Changes the Python version used in pipelines to 3.10.6 or greater
> since that version introduces a fix (bp0-47231) for inconsistent
> trailing slashes in tarfile longname directories.
> 
> This is required for stuart_update to succeed when handling a
> web_dependency (e.g. GCC ARM compilers).
> 
> Cc: Sean Brogan <sean.brogan@microsoft.com>
> Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Cc: Liming Gao <gaoliming@byosoft.com.cn>
> Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
> ---
> 
> Notes:
>     Build results with this change are available
>     in the following PR:
>     https://github.com/tianocore/edk2/pull/3240
> 
>  .azurepipelines/Ubuntu-PatchCheck.yml                  | 2 +-
>  .azurepipelines/templates/platform-build-run-steps.yml | 2 +-
>  .azurepipelines/templates/pr-gate-steps.yml            | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/.azurepipelines/Ubuntu-PatchCheck.yml b/.azurepipelines/Ubuntu-PatchCheck.yml
> index 1bc28176b6e8..b86d4bc3b93f 100644
> --- a/.azurepipelines/Ubuntu-PatchCheck.yml
> +++ b/.azurepipelines/Ubuntu-PatchCheck.yml
> @@ -27,7 +27,7 @@ steps:
> 
>  - task: UsePythonVersion@0
>    inputs:
> -    versionSpec: '3.8.x'
> +    versionSpec: '>=3.10.6'
>      architecture: 'x64'
> 
>  - script: |
> diff --git a/.azurepipelines/templates/platform-build-run-steps.yml b/.azurepipelines/templates/platform-build-run-steps.yml
> index 97e7faa26682..40a31a509fc5 100644
> --- a/.azurepipelines/templates/platform-build-run-steps.yml
> +++ b/.azurepipelines/templates/platform-build-run-steps.yml
> @@ -42,7 +42,7 @@ steps:
> 
>  - task: UsePythonVersion@0
>    inputs:
> -    versionSpec: "3.8.x"
> +    versionSpec: ">=3.10.6"
>      architecture: "x64"
> 
>  - script: pip install -r pip-requirements.txt --upgrade
> diff --git a/.azurepipelines/templates/pr-gate-steps.yml b/.azurepipelines/templates/pr-gate-steps.yml
> index 70c19a462194..cb431e53fcd1 100644
> --- a/.azurepipelines/templates/pr-gate-steps.yml
> +++ b/.azurepipelines/templates/pr-gate-steps.yml
> @@ -20,7 +20,7 @@ steps:
> 
>  - task: UsePythonVersion@0
>    inputs:
> -    versionSpec: '3.8.x'
> +    versionSpec: '>=3.10.6'
>      architecture: 'x64'
> 
>  - script: pip install -r pip-requirements.txt --upgrade
> --
> 2.28.0.windows.1


      reply	other threads:[~2022-08-30  3:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25 15:36 [PATCH v1 1/1] .azurepipelines: Use Python 3.10.6+ Michael Kubacki
2022-08-30  3:01 ` Michael D Kinney [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CO1PR11MB492925DEA73717C7B48F6C54D2799@CO1PR11MB4929.namprd11.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox