From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Revert of aws-cli Date: Fri, 24 Jan 2025 10:05:33 +0000 Message-ID: In-Reply-To: <1750b145-4c42-40ab-962e-797d1b831b0c@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6514428910520804684==" List-Id: --===============6514428910520804684== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Adolf, Thanks for looking into this again. AWS CLI is a bit of a mess=E2=80=A6 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 bui= ld, but I did not get very far. I cannot remember what I ran into, but I supp= ose I just gave up at some point because the older version was working just f= ine 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 vers= ion of botocore doesn=E2=80=99t 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 =E2=80=9Caws help=E2=80=9D to the LFS file, so that w= e will see if things are actually able to start up. That is pretty much all w= e can test, but looking back at the problems in the past that we have had wit= h aws-cli, it simply won=E2=80=99t start if it isn=E2=80=99t happy. Once it s= tarts 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 wit= h it: https://git.ipfire.org/?p=3Dpeople/ms/ipfire-2.x.git;a=3Dshortlog;h=3Dr= efs/heads/aws-cli > On 24 Jan 2025, at 09:33, Adolf Belka wrote: >=20 > Hi Michael, >=20 > 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=E2=80=99s see if that will be enough=E2=80=A6 >=20 > Looks like I didn't read enough of the info files in the aws-cli tarball. >=20 > There are 5 requirements files provided. >=20 > From those I see that the development of aws-cli is done in tandem with bot= ocore and s3transfer and they are using the latest development branch of both= of those programs when working on aws-cli. >=20 > Another file has a range of requirements for other python files. >=20 > This indicates that s3transfer should be >=3D0.10.0,<0.11.0 and we currentl= y 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. >=20 > That file also says docutils>=3D0.10,<0.17 but we are already on 0.19 for t= hat package and rsa>=3D3.1.2,<4.8 but we are already on 4.9 for some time. > So all the dependencies are not kept properly updated. >=20 > 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. >=20 > Regards, >=20 > Adolf >=20 >> -Michael >>> On 23 Jan 2025, at 21:49, Adolf Belka wrote: >>>=20 >>> Hi Michael, >>>=20 >>> 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. >>>=20 >>> Looking in some of the files in the source tarball it looks like it needs= a newer version of python3-botocore. >>>=20 >>> I will do that during my update of python, as the updated aws-cli looks t= o also require a python of at least 3.12 from another file in the source tarb= all. >>>=20 >>> Regards, >>>=20 >>> Adolf. >>>=20 >>>=20 >=20 > --=20 > Sent from my laptop --===============6514428910520804684==--