Aneesh Karve

@dimaryaz a few questions just so I understand all the cases, is this correct? 1. Object in S3 already has checksum - use that checksum and it's reproducible via client...

> @dimaryaz does this PR supports `quilt3 verify` for packages with old hashes? > It does not. It's doable - we'd need to keep the old hashing code for that....

> > I am OK dropping support for `quilt3 verify` but in that case we should delete the code so users don't call it. > You mean, we don't need...

> @akarve: not sure I understand what you mean here: > > > ``` > > 2. Object in S3 does not have checksum, will not be copied - use...

> > As long as we have an error message for the "old package" case (we can use manifest version) then the new client can fail `quilt3 verify` on old...

It is possible and we have min.io on the [roadmap](https://github.com/quiltdata/quilt#roadmap). We invite you to try Quilt with a min.io endpoint and file bugs that you encounter, as we have yet...

Indeed. Just as a heads up we are still on the bleeding edge here and therefore haven't solicited people to try it, but if you are already using min.io and...

Per discussion we should merge this as part for quilt3 4.x so as not to merge a potentially breaking change into 3.x.

Yeah, the reason we did this is that package view truncates after 1K files. In any case, If you set your `quilt3.config(navigator_url="https://my-catalog")` then it'll print package URL out (instead of...

Good catch. Our users have definitely expressed that Python identifiers are too limiting for package names. I would suggest that we deprecate this feature, as there are other bugs in...