From: bobertlo <bobertlo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: aws-cli: update to 1.22.23
Date: Fri, 10 Dec 2021 08:13:54 +0100 [thread overview]
Message-ID: <20211210071354.oYxm_vjqaajP_3MvSV4OWFCq68y1IPqjmV0Z-n1XJhE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34457@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
New comment by bobertlo on void-packages repository
https://github.com/void-linux/void-packages/pull/34457#issuecomment-990674006
Comment:
I’ll try to get what I’ve got up soon. Just know botocore and s3transfer
are developed together with aws cli so if you run into any issues try
bumping those too. It usually is fine but has broken things before.
I think everything was working at the latest versions I was just working on
tests and seeing how awful the 2.x branch runtime is lol
On Thu, Dec 9, 2021 at 11:55 PM uhohspaghetios ***@***.***>
wrote:
> FYI I have a build of this ready with the dependencies updated also. I was
> just working on getting some of the tests running still. :)
>
> Oh sweet. I just undertook this one because it was mostly easy and I
> wanted the latest for an AWS course I started today. I can close this PR if
> appropriate.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/void-linux/void-packages/pull/34457#issuecomment-990639968>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAGWHGPRQWZEOPOGROIM5GLUQGI6NANCNFSM5JYHZMKQ>
> .
>
next prev parent reply other threads:[~2021-12-10 7:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 5:03 [PR PATCH] " uhohspaghetios
2021-12-10 5:24 ` bobertlo
2021-12-10 5:55 ` uhohspaghetios
2021-12-10 7:13 ` bobertlo [this message]
2021-12-12 4:01 ` bobertlo
2021-12-12 5:16 ` [PR PATCH] [Closed]: " uhohspaghetios
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211210071354.oYxm_vjqaajP_3MvSV4OWFCq68y1IPqjmV0Z-n1XJhE@z \
--to=bobertlo@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).