Lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: Branch creation - "before 4am on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[djc]

The failure here is probably because openssl-src got bumped from 111 to 300.

[rami3l]

Claim.

@djc Thanks for your pointers! This seems to be an OpenSSLv3-specific problem.
Possibly related to https://stackoverflow.com/q/70464585:
I believe the CI error is due to a Perl component IPC/Cmd.pm left uninstalled in the Docker image.

On a Debian system this should be reachable from perl-modules that comes with a full perl installation, but some packages only rely on perl-base with is a minimal subset of perl files and that's why the CI used to build.

However, looking at

rustup/ci/docker/x86_64-unknown-linux-gnu/Dockerfile

Line 1 in cd3a10f

FROM rust-x86_64-unknown-linux-gnu

I have no idea how Perl gets set up 🤔

cc openssl/openssl#14541, sfackler/rust-openssl#1550

[tgross35]

Some followup in https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/Get.20a.20Perl.20setup.20with.20.60IPC.2FCmd.2Epm.60.20in.20Rustup's.20CI.20image

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[rami3l]

Looking at #1815, the base image here seems to be https://github.com/rust-lang/rust/blob/e08de860365aa73653dc5fc45b09f194785f3e57/src/ci/docker/host-x86_64/dist-x86_64-linux/Dockerfile. Should we put this info in the docs somewhere?

[rami3l]

Leaving a note for my future self (or anyone else it may concern):

#1724 (comment) points to rust-lang/rust#59420, which implies that in ci/fetch-rust-docker.bash we are downloading an S3-cached Docker image provided by rustc's CI.

By referring to this map:

rustup/ci/fetch-rust-docker.bash

Lines 17 to 20 in cd3a10f

	# Use images from rustc master
	case "$TARGET" in
	aarch64-unknown-linux-gnu) image=dist-aarch64-linux ;;
	aarch64-unknown-linux-musl) image=dist-arm-linux ;;

we are actually referring to Dockerfiles located in https://github.com/rust-lang/rust/tree/master/src/ci/docker/host-x86_64.

For example,

rustup/ci/fetch-rust-docker.bash

Line 20 in cd3a10f

aarch64-unknown-linux-musl) image=dist-arm-linux ;;

means that for rust-aarch64-unknown-linux-musl:

rustup/ci/docker/aarch64-unknown-linux-musl/Dockerfile

Line 1 in cd3a10f

FROM rust-aarch64-unknown-linux-musl

we should refer to https://github.com/rust-lang/rust/blob/master/src/ci/docker/host-x86_64/dist-arm-linux/Dockerfile.

[alex]

CI change lgtm

[djc]

If I'm not misreading I only see comment changes, so how did the previous issues in CI actually get fixed?

[alex]

There's an additional perl package installed

…

On Sun, Oct 8, 2023, 3:07 PM Dirkjan Ochtman ***@***.***> wrote: If I'm not misreading I only see comment changes, so how did the previous issues in CI actually get fixed? — Reply to this email directly, view it on GitHub <#3478 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAAGBHZUUEHJA64A62PEP3X6L2YRAVCNFSM6AAAAAA4SS4KM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJSGEZTIMRYGI> . You are receiving this because you commented.Message ID: ***@***.***>

[djc]

Oops, missed that on my phone. LGTM!

For the future, might be nice to keep comment additions in a separate commit from the fix in the Dockerfile.

[rami3l]

@djc Oh I did exactly that to ensure both commits are green on CI.
I indeed forgot to add how the bug was fixed somewhere in this thread, really sorry about that!

[djc]

@rami3l sorry, I meant one more commit: one to add comments, and one for the fix to add the Perl dependency.