Yum is no longer available in AWS python images

[lirwin3007]

It doesn't look like AWS plans on making yum available in the python images going forward (aws/aws-lambda-base-images#124 (comment)), this leads to issues such as #1045

I think the solution to this could be either:

• Pin the python image used to one that includes yum
• or, update the yum commands to be dnf commands

I'll try and put together a PR to resolve this

[lirwin3007]

Update: I have tried changing yum -> dnf, and now get this error:

dnf: /var/lang/lib/liblzma.so.5: version `XZ_5.2' not found (required by /lib64/librpmio.so.9)

Which is again logged as an issue with the python image (aws/aws-lambda-base-images#127)

The AWS team say:

aws/aws-lambda-base-images#127 (comment)
The python runtime team is aware of the issue, and has root caused the problem. They'll be triggering a rollback in several hours during business hours in Dublin.
For now, please utilize the previous Python3.11 image

I think this comment is quite accurate 😆

aws/aws-lambda-base-images#127 (comment)
I never realised that pinning to tag 3.11 would mean it is rebuilt, with breaking changes.

For now I'll submit a PR that pins to a specific build, which should avoid this issue with 3.11 being updated with breaking changes.
I understand the maintainer may not wish to pin a particular build, but I'm not sure what else to do if tags like 3.11 can be updated with breaking changes...