From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka <adolf.belka@ipfire.org> To: development@lists.ipfire.org Subject: Re: Revert of aws-cli Date: Fri, 24 Jan 2025 16:27:51 +0100 Message-ID: <f6d0cb2e-4128-4136-bce4-388d7d62e244@ipfire.org> In-Reply-To: <E7D7DCB2-3890-49C8-99BE-367B76938038@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0398675078211316360==" List-Id: <development.lists.ipfire.org> --===============0398675078211316360== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, On 24/01/2025 11:05, Michael Tremer wrote: > Hello Adolf, >=20 > Thanks for looking into this again. >=20 > AWS CLI is a bit of a mess=E2=80=A6 >=20 > We are currently on the older Python version which seems to be deprecated f= or a long time. There is however a newer version that I have been trying to b= uild, but I did not get very far. I cannot remember what I ran into, but I su= ppose 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 woul= d be happy to pass over if you want to give it a go. >=20 > But first back to this one: This version seems to be very unhappy if the ve= rsion of botocore doesn=E2=80=99t exactly match. Sadly our current build syst= em is not very good at tracking these things, but hopefully that will change = in the very near future. >=20 > I added a small call of =E2=80=9Caws help=E2=80=9D 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 w= ith aws-cli, it simply won=E2=80=99t start if it isn=E2=80=99t happy. Once it= starts and finds all its dependencies it is happy. >=20 > -Michael >=20 > P.S. This is the branch with some early things if you want to play around w= ith it: https://git.ipfire.org/?p=3Dpeople/ms/ipfire-2.x.git;a=3Dshortlog;h= =3Drefs/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 i= n 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. >=20 >> 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=E2=80=99s see if that will be enough=E2=80=A6 >> >> 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 b= otocore and s3transfer and they are using the latest development branch of bo= th 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 >=3D0.10.0,<0.11.0 and we current= ly 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>=3D0.10,<0.17 but we are already on 0.19 for = that 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. >> >> Hopefully it is just botocore and s3transfer that need to be kept linked t= o 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 modul= e 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 need= s 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 tar= ball. >>>> >>>> Regards, >>>> >>>> Adolf. >>>> >>>> >> >> --=20 >> Sent from my laptop >=20 >=20 --===============0398675078211316360==--