Re: Revert of aws-cli

[Adolf Belka <adolf.belka@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 1937 bytes --]

Hi Michael,

On 23/01/2025 22:51, Michael Tremer wrote:
> Hello Adolf,
> 
> Thank you for reading the changes so fast. I already have a build running and updated botocore. Let’s see if that will be enough…

Looks like I didn't read enough of the info files in the aws-cli tarball.

There are 5 requirements files provided.

 From those I see that the development of aws-cli is done in tandem with 
botocore and s3transfer and they are using the latest development branch 
of both of those programs when working on aws-cli.

Another file has a range of requirements for other python files.

This indicates that s3transfer should be >=0.10.0,<0.11.0 and we 
currently have 0.6.0 but the latest available is 0.11.2 so maybe it has 
been further updated since the last version of aws-cli.

That file also says docutils>=0.10,<0.17 but we are already on 0.19 for 
that package and rsa>=3.1.2,<4.8 but we are already on 4.9 for some time.
So all the dependencies are not kept properly updated.

Hopefully it is just botocore and s3transfer that need to be kept linked 
to latest versions. I will try and remember that these need to be kept 
updated together with aws-cli.

Regards,

Adolf

> 
> -Michael
> 
>> On 23 Jan 2025, at 21:49, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi Michael,
>>
>> I saw that you had to revert the update of aws-cli due to a python module problem at run time. There was no failure or error message during the build unfortunately and nothing in the build log for aws-cli flagging up a too old package.
>>
>> Looking in some of the files in the source tarball it looks like it needs a newer version of python3-botocore.
>>
>> I will do that during my update of python, as the updated aws-cli looks to also require a python of at least 3.12 from another file in the source tarball.
>>
>> Regards,
>>
>> Adolf.
>>
>>
> 

-- 
Sent from my laptop