Skip to content

[Backport staging-21.11] python38: 3.8.12 -> 3.8.13; python37: 3.7.12 -> 3.7.13#164540

Merged
mweinelt merged 2 commits intostaging-21.11from
backport-164487-to-staging-21.11
Mar 17, 2022
Merged

[Backport staging-21.11] python38: 3.8.12 -> 3.8.13; python37: 3.7.12 -> 3.7.13#164540
mweinelt merged 2 commits intostaging-21.11from
backport-164487-to-staging-21.11

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Bot-based backport to staging-21.11, triggered by a label in #164487.

  • Before merging, ensure that this backport complies with the Criteria for Backporting.
    • Even as a non-commiter, if you find that it does not comply, leave a comment.

@github-actions github-actions bot requested a review from FRidh as a code owner March 17, 2022 06:43
@FRidh FRidh requested a review from mweinelt March 17, 2022 06:54
@ofborg ofborg bot added 10.rebuild-darwin: 501+ This PR causes many rebuilds on Darwin and should normally target the staging branches. 10.rebuild-darwin: 2501-5000 This PR causes many rebuilds on Darwin and should target the staging branches. 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-linux: 2501-5000 This PR causes many rebuilds on Linux and should target the staging branches. labels Mar 17, 2022
@mweinelt mweinelt added the 1.severity: security Issues which raise a security issue, or PRs that fix one label Mar 17, 2022
@mweinelt
Copy link
Copy Markdown
Member

Merging as the passthru tests have been completed by ofBorg.

@mweinelt mweinelt merged commit 6044ee5 into staging-21.11 Mar 17, 2022
@mweinelt mweinelt deleted the backport-164487-to-staging-21.11 branch March 17, 2022 23:46
suffix = "";
};
sha256 = "1si8hw2xpagh4iji89zdx69p3dv5mjqwwbx2x2sl6lrp41jaglxi";
};
Copy link
Copy Markdown
Member

@mweinelt mweinelt Mar 18, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah wait. When do we remove versions from the sources attrset again? Isn't this where we track the two currently supported ones? I don't know where they are referenced.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They are referenced in the same file. The reason the source details were split into separate sets is for the minimal build for bootstrapping.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

1.severity: security Issues which raise a security issue, or PRs that fix one 10.rebuild-darwin: 501+ This PR causes many rebuilds on Darwin and should normally target the staging branches. 10.rebuild-darwin: 2501-5000 This PR causes many rebuilds on Darwin and should target the staging branches. 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-linux: 2501-5000 This PR causes many rebuilds on Linux and should target the staging branches.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants