Revert of aws-cli

Revert of aws-cli

[Adolf Belka]

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

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.

Re: Revert of aws-cli

[Michael Tremer]

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

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…

-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.
> 
> 

Re: Revert of aws-cli

[Adolf Belka]

[-- 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

Re: Revert of aws-cli

[Michael Tremer]

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

Hello Adolf,

Thanks for looking into this again.

AWS CLI is a bit of a mess…

We are currently on the older Python version which seems to be deprecated for a long time. There is however a newer version that I have been trying to build, but I did not get very far. I cannot remember what I ran into, but I suppose I just gave up at some point because the older version was working just fine for me. I do have a branch with some of the changes I made which I would be happy to pass over if you want to give it a go.

But first back to this one: This version seems to be very unhappy if the version of botocore doesn’t exactly match. Sadly our current build system is not very good at tracking these things, but hopefully that will change in the very near future.

I added a small call of “aws help” to the LFS file, so that we will see if things are actually able to start up. That is pretty much all we can test, but looking back at the problems in the past that we have had with aws-cli, it simply won’t start if it isn’t happy. Once it starts and finds all its dependencies it is happy.

-Michael

P.S. This is the branch with some early things if you want to play around with it: https://git.ipfire.org/?p=people/ms/ipfire-2.x.git;a=shortlog;h=refs/heads/aws-cli

> On 24 Jan 2025, at 09:33, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> 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

Re: Revert of aws-cli

[Adolf Belka]

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

Hi Michael,

On 24/01/2025 11:05, Michael Tremer wrote:
> Hello Adolf,
> 
> Thanks for looking into this again.
> 
> AWS CLI is a bit of a mess…
> 
> We are currently on the older Python version which seems to be deprecated for a long time. There is however a newer version that I have been trying to build, but I did not get very far. I cannot remember what I ran into, but I suppose I just gave up at some point because the older version was working just fine for me. I do have a branch with some of the changes I made which I would be happy to pass over if you want to give it a go.
> 
> But first back to this one: This version seems to be very unhappy if the version of botocore doesn’t exactly match. Sadly our current build system is not very good at tracking these things, but hopefully that will change in the very near future.
> 
> I added a small call of “aws help” to the LFS file, so that we will see if things are actually able to start up. That is pretty much all we can test, but looking back at the problems in the past that we have had with aws-cli, it simply won’t start if it isn’t happy. Once it starts and finds all its dependencies it is happy.
> 
> -Michael
> 
> P.S. This is the branch with some early things if you want to play around with it: https://git.ipfire.org/?p=people/ms/ipfire-2.x.git;a=shortlog;h=refs/heads/aws-cli

I take it this is related to aws-cli-2.x

I had a quick look at that and found that they have a configure/make option in the tarball.

We can't use it directly as the combination also "helps" you to download and install all the required dependencies.

However I just ran a quick build that only had the ./configure in place as it gives you a list of all missing dependencies, which I now have.

So when I work on this later on, I now know which dependency packages I need to install as well.

Regards,
Adolf.

> 
>> On 24 Jan 2025, at 09:33, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> 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
> 
>