On Fri, Nov 04, 2022 at 02:56:45PM -0700, Noah Meyerhans wrote:
> Given the number of packages involved, though, I expect it'll take a
> while for everything to have a properly managed SONAME. Given that, I
> see a few alternatives:
>
> 1. We package aws-crt-python with all the aws-c-* packages
On Fri, Nov 04, 2022 at 05:37:21PM +0100, Bastian Blank wrote:
> > > Are you sure this library can have a 1 as ABI? Can you please reproduce
> > > the ABI stability promisses?
> > Allegedly upstream has recently committed to proper SONAME and ABI
> > management in support of efforts to get these
On Fri, Nov 04, 2022 at 09:08:22AM -0700, Noah Meyerhans wrote:
> > Are you sure this library can have a 1 as ABI? Can you please reproduce
> > the ABI stability promisses?
> Allegedly upstream has recently committed to proper SONAME and ABI
> management in support of efforts to get these
On Fri, Nov 04, 2022 at 08:32:25AM +0100, Bastian Blank wrote:
> > My first pass only produces -dev packages with headers and static libraries.
> > To test them out, build the debian/sid branch from these repos, in this
> > order:
> > - https://salsa.debian.org/rvandegrift/aws-c-common
>
> Are
On Tue, Oct 05, 2021 at 11:10:43PM -0600, Ross Vandegrift wrote:
> My first pass only produces -dev packages with headers and static libraries.
> To test them out, build the debian/sid branch from these repos, in this order:
> - https://salsa.debian.org/rvandegrift/aws-c-common
Are you sure this
On Thu, Nov 03, 2022 at 09:35:14PM -0700, Ross Vandegrift wrote:
> > Honestly, filing some of the ITPs would be quite helpful at this point.
> > We'll need to get the following projects packaged:
> >
> > aws-c-auth
> > aws-c-cal
> > aws-c-compression
> > aws-c-event-stream
> > aws-c-http
>
> I
On Wed, Nov 02, 2022 at 10:26:50PM -0700, Noah Meyerhans wrote:
> Honestly, filing some of the ITPs would be quite helpful at this point.
> We'll need to get the following projects packaged:
>
> aws-c-auth
> aws-c-cal
> aws-c-compression
> aws-c-event-stream
> aws-c-http
I got this far, and
On Wed, Nov 02, 2022 at 07:55:51PM -0700, Ross Vandegrift wrote:
> > > - the aws-cli2-temp repo is based on upstream, not our awscli repo. I was
> > > intentionally being sloppy to quickly get through a test.
> >
> > Same. I essentially Debianized the upstream v2 repo from scratch,
> >
Hi Noah,
On Mon, Oct 31, 2022 at 10:50:19PM -0700, Noah Meyerhans wrote:
> On Tue, Oct 05, 2021 at 11:10:43PM -0600, Ross Vandegrift wrote:
> > > awscli v2 remains quite difficult to package, but it seems that upstream
> > > is looking to address this. See
> > >
On Mon, Oct 31, 2022 at 10:50:19PM -0700, Noah Meyerhans wrote:
> > aws-crt-python is the hard part. It depends on a bunch of C libraries which
> > follow a more modern development style. They:
> > - provide no abi/api stability guarantees.
> > - have versioned releases, but no one cares about
Hi Ross,
On Tue, Oct 05, 2021 at 11:10:43PM -0600, Ross Vandegrift wrote:
> > awscli v2 remains quite difficult to package, but it seems that upstream
> > is looking to address this. See
> > https://github.com/aws/aws-cli/issues/6186 for details and tracking.
>
> Using the source dist poc from
On Tue, Oct 05, 2021 at 11:10:48PM -0600, Ross Vandegrift wrote:
> A few known issues:
>
> - some repos have tests disabled due to failing during builds. So far, I
> don't
> know if these are real failures, or if upstream's build method.
>
> - copyright attribution for aws-lc is very hard.
On Thu, Jun 17, 2021 at 09:56:10AM -0700, Noah Meyerhans wrote:
> awscli v2 remains quite difficult to package, but it seems that upstream
> is looking to address this. See
> https://github.com/aws/aws-cli/issues/6186 for details and tracking.
Using the source dist poc from
Control: severity -1 wishlist
Control: forwarded -1 https://github.com/aws/aws-cli/issues/6186
awscli v2 remains quite difficult to package, but it seems that upstream
is looking to address this. See
https://github.com/aws/aws-cli/issues/6186 for details and tracking.
We'll continue to track
14 matches
Mail list logo
