So I was thinking about this, because the vast majority of the work consists of new uploads for S3 support... namely: > - s3-wagon-private "1.3.1" > - com.amazonaws/aws-java-sdk-core "1.11.184" > - com.amazonaws/aws-java-sdk-kms "1.11.184" > - com.amazonaws/aws-java-sdk-s3 "1.11.184" > - software.amazon.ion/ion-java "1.0.2" > - com.amazonaws/jmespath-java "1.11.184" > - org.springframework.build/aws-maven "4.8.0.RELEASE" Looking at the underlying code, it looks like patching out S3 support is very straightforward.[*] And since S3 support is mainly for private maven repos (i.e. to serve proprietary artifacts), I'm not too worried about leaving out support for this in Debian. Of course, if someone wants to package the Java SDK, they should feel free. In that case, the remaining work for tools.deps is: > Needs version bump: > - data-xml-clojure to 0.2.0-alpha5 > - libjsch-agent-proxy-java to 0.0.9 > - jgit to 4.10.0 > > Needs new upload: > - org.clojure/tools.gitlibs "0.2.64" That is a manageable workload and I'd love to make it happen. So I'll file an ITP for tools-gitlibs-clojure and version bump requests for the other three. - e [*]: https://github.com/clojure/tools.deps.alpha/blob/884d7ae5b9c228ff795e4385291708102f1cd46d/src/main/clojure/clojure/tools/deps/alpha/util/maven.clj#L105-L106
Attachment:
signature.asc
Description: Digital signature