Bug#1010995: RFP: test-generative-clojure -- Generative test runner for Clojure
Package: wnpp X-Debbugs-Cc: ehash...@debian.org Severity: wishlist * Package name: test-generative-clojure Version : 1.0.0 Upstream Author : Rich Hickey * URL : https://github.com/clojure/test.generative * License : EPL-1.0 Programming Lang: Clojure Description : Generative test runner for Clojure Needs packaging in order to run Clojure's build tests, possibly others. To be team-maintained by Clojure Team. signature.asc Description: PGP signature
Bug#891136: ITP: tools-deps-alpha-clojure -- functional API for dependency management and classpath creation
Okay, latest version is now 0.8.677. Let's reevaluate what's required for packaging. `lein deps :tree` now says: [org.clojure/tools.deps.alpha "0.8.677"] ;; I'm going to ignore these for now [com.cognitect.aws/api "0.8.408"] [com.cognitect/http-client "0.1.101"] [org.eclipse.jetty/jetty-client "9.4.15.v20190215"] [org.eclipse.jetty/jetty-io "9.4.15.v20190215"] [org.eclipse.jetty/jetty-http "9.4.15.v20190215"] [org.eclipse.jetty/jetty-util "9.4.15.v20190215"] [commons-codec "1.13"] [org.clojure/core.async "0.5.527"] [org.clojure/tools.analyzer.jvm "0.7.2"] [org.clojure/core.memoize "0.5.9"] [org.clojure/core.cache "0.6.5"] [org.clojure/data.priority-map "0.0.7"] [org.clojure/tools.analyzer "0.6.9"] [org.clojure/tools.reader "1.0.0-beta4"] [org.ow2.asm/asm-all "4.2"] [org.clojure/data.json "0.2.7"] [org.clojure/tools.logging "0.5.0"] [com.cognitect.aws/endpoints "1.1.11.705"] [com.cognitect.aws/s3 "784.2.593.0"] ;; inside libatinject-jsr330-api-java [javax.inject "1"] ;; libmaven-resolver-java == 1.4.1 in sid [org.apache.maven.resolver/maven-resolver-api "1.4.1"] [org.apache.maven.resolver/maven-resolver-connector-basic "1.4.1"] [org.apache.maven.resolver/maven-resolver-impl "1.4.1"] [org.slf4j/slf4j-api "1.7.25"] [org.apache.maven.resolver/maven-resolver-spi "1.4.1"] [org.apache.maven.resolver/maven-resolver-transport-file "1.4.1"] [org.apache.maven.resolver/maven-resolver-transport-http "1.4.1"] [org.apache.httpcomponents/httpclient "4.5.6" :exclusions [[commons-logging]]] [org.apache.httpcomponents/httpcore "4.4.10"] [org.slf4j/jcl-over-slf4j "1.7.25" :scope "runtime"] [org.apache.maven.resolver/maven-resolver-util "1.4.1"] ;; libmaven3-core-java == 3.6.3 in sid [org.apache.maven/maven-core "3.6.3"] [com.google.inject/guice "4.2.1" :classifier "no_aop"] [aopalliance "1.0"] [com.google.guava/guava "25.1-android"] [com.google.code.findbugs/jsr305 "3.0.2"] [com.google.errorprone/error_prone_annotations "2.1.3"] [com.google.j2objc/j2objc-annotations "1.1"] [org.checkerframework/checker-compat-qual "2.0.0"] [org.codehaus.mojo/animal-sniffer-annotations "1.14"] [org.apache.commons/commons-lang3 "3.8.1"] [org.apache.maven.shared/maven-shared-utils "3.2.1"] [commons-io "2.5"] [org.apache.maven/maven-artifact "3.6.3"] [org.apache.maven/maven-builder-support "3.6.3"] [org.apache.maven/maven-plugin-api "3.6.3"] [org.apache.maven/maven-settings-builder "3.6.3"] [org.sonatype.plexus/plexus-sec-dispatcher "1.4"] [org.sonatype.plexus/plexus-cipher "1.4"] [org.apache.maven/maven-settings "3.6.3"] [org.codehaus.plexus/plexus-classworlds "2.6.0"] [org.codehaus.plexus/plexus-component-annotations "2.1.0" :exclusions [[junit]]] [org.eclipse.sisu/org.eclipse.sisu.inject "0.3.4"] [org.eclipse.sisu/org.eclipse.sisu.plexus "0.3.4"] [javax.enterprise/cdi-api "1.0" :exclusions [[javax.el/el-api] [org.jboss.ejb3/jboss-ejb3-api] [org.jboss.interceptor/jboss-interceptor-api]]] [javax.annotation/jsr250-api "1.0"] ;; in libmaven3-core-java == 3.6.3 in sid [org.apache.maven/maven-resolver-provider "3.6.3"] [org.apache.maven/maven-model-builder "3.6.3"] [org.codehaus.plexus/plexus-interpolation "1.25"] [org.apache.maven/maven-model "3.6.3"] [org.apache.maven/maven-repository-metadata "3.6.3"] [org.codehaus.plexus/plexus-utils "3.2.1"] ;; in libdata-xml-clojure > 0.0.8 in sid ;; there's an incompatibility with leiningen issue in upgrading [org.clojure/data.xml "0.2.0-alpha6"] [org.clojure/data.codec "0.1.0"] ;; in libtools-cli-clojure > 0.3.5 in sid [org.clojure/tools.cli "0.4.2"] ;; NOT in Debian, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905543 [org.clojure/tools.gitlibs "0.2.64"] [com.jcraft/jsch.agentproxy.connector-factory "0.0.9"] [com.jcraft/jsch.agentproxy.core "0.0.9"] [com.jcraft/jsch.agentproxy.pageant "0.0.9"] [com.jcraft/jsch.agentproxy.sshagent "0.0.9"] [com.jcraft/jsch.agentproxy.usocket-jna "0.0.9"] [net.java.dev.jna/jna-platform "4.1.0"] [net.java.dev.jna/jna "4.1.0"] [com.jcraft/jsch.agentproxy.usocket-nc "0.0.9"] [com.jcraft/jsch.agentproxy.jsch "0.0.9"] [org.eclipse.jgit "4.10.0.201712302008-r"] [com.googlecode.javaewah/JavaEWAH "1.1.6"] [com.jcraft/jsch "0.1.54"] So in summary, we need the following new packages: - [org.clojure/tools.gitlibs "0.2.64"] And the following upgrades: - [org.clojure/data.xml "0.2.0-alpha6"] - [org.clojure/tools.cli "0.4.2"] Again, I'm going to skip all the AWS stuff and consider it a "recommends" rather than a "depends". Previously, clojure-tools-gitlibs also needed version
Bug#891141: ITP: clojure-cli -- upstream CLI entrypoints for Clojure
Latest upstream version is now 1.10.1.536 with a dependency on clojure.deps.alpha 0.8.677. signature.asc Description: PGP signature
Bug#920043: ITP: nrepl-clojure -- Clojure network REPL replacing tools.nrepl
Package: wnpp Owner: Elana Hashman Severity: wishlist * Package name: nrepl-clojure Version : 0.5.3 Upstream Author : 2010-2018 Chas Emerick, Bozhidar Batsov and contributors * URL : https://nrepl.org/ * License : EPL-1.0 Programming Lang: Clojure Description : Clojure network REPL replacing tools.nrepl nrepl provides a REPL server and client, along with some common APIs of use to IDEs and other tools that may need to evaluate Clojure code in remote environments. This package is required for updating leiningen-clojure to 2.8.3 and is intended to eventually replace tools-nrepl-clojure, which is no longer maintained upstream.
Bug#919930: ITP: lua-fennel -- a lisp that compiles to Lua
Package: wnpp Owner: Elana Hashman Severity: wishlist * Package name: lua-fennel Version : 0.2.0 Upstream Author : Calvin Rose * URL : https://fennel-lang.org/ * License : MIT Programming Lang: Lua Description : a lisp that compiles to Lua Fennel is a programming language that brings together the speed, simplicity, and reach of Lua with the flexibility of a lisp syntax and macro system. It aims to be easy to use, expressive, and has almost zero overhead compared to handwritten Lua. Anywhere you can run Lua code, you can run Fennel code. signature.asc Description: PGP signature
Bug#905543: ITP: tools-gitlibs-clojure -- Clojure API for programatically accessing git libraries
Package: wnpp Owner: Elana Hashman Severity: wishlist Control: block 891136 by -1 * Package name: tools-gitlibs-clojure Version : 0.2.64 Upstream Author : Rich Hickey * URL : https://github.com/clojure/tools.gitlibs * License : EPL-1.0 Programming Lang: Clojure Description : Clojure API for programatically accessing git libraries This is a dependency of tools-deps-alpha, the package resolver and manager for the new upstream clojure-cli. signature.asc Description: Digital signature
Bug#891136: ITP: tools-deps-alpha-clojure -- functional API for dependency management and classpath creation
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 signature.asc Description: Digital signature
Bug#891136: ITP: tools-deps-alpha-clojure -- functional API for dependency management and classpath creation
Okay, since I got a bug report about this, let's take a look at this
again for the latest tools.deps.alpha release 0.5.422. From deps.edn:
org.clojure/clojure {:mvn/version "1.9.0"}
* Good here: https://tracker.debian.org/pkg/clojure
org.apache.maven.resolver/maven-resolver-api {:mvn/version "1.1.1"}
org.apache.maven.resolver/maven-resolver-spi {:mvn/version "1.1.1"}
org.apache.maven.resolver/maven-resolver-impl {:mvn/version "1.1.1"}
org.apache.maven.resolver/maven-resolver-util {:mvn/version "1.1.1"}
org.apache.maven.resolver/maven-resolver-connector-basic {:mvn/version "1.1.1"}
org.apache.maven.resolver/maven-resolver-transport-file {:mvn/version "1.1.1"}
org.apache.maven.resolver/maven-resolver-transport-http {:mvn/version "1.1.1"}
org.apache.maven.resolver/maven-resolver-transport-wagon {:mvn/version "1.1.1"}
* Good here: https://tracker.debian.org/pkg/maven-resolver
org.apache.maven/maven-resolver-provider {:mvn/version "3.5.2"}
org.apache.maven/maven-core {:mvn/version "3.5.2"}
org.apache.maven/maven-settings-builder {:mvn/version "3.5.2"}
* We have 3.5.3, shouldn't be an issue: https://tracker.debian.org/pkg/maven
org.slf4j/slf4j-nop {:mvn/version "1.6.2"}
* We have 1.7.25, shouldn't be an issue:
https://tracker.debian.org/pkg/libslf4j-java
org.clojure/data.xml {:mvn/version "0.2.0-alpha5"}
* This one might be a little hairy. We currently have 0.0.8 in Debian.
Leiningen (and possibly other libraries) depend on it. If it's fully
backwards compatible, we can upgrade. But we might wanna try being
conservative and patch upstream.
s3-wagon-private {:mvn/version "1.3.1" :exclusions
[ch.qos.logback/logback-classic]}
* We do not have this one.
org.clojure/tools.gitlibs {:mvn/version "0.2.64"}
* We do not have this one.
org.clojure/tools.cli {:mvn/version "0.3.5"}
* Good here: https://tracker.debian.org/pkg/tools-cli-clojure
Okay, that leaves us with new uploads needed for:
s3-wagon-private {:mvn/version "1.3.1" :exclusions
[ch.qos.logback/logback-classic]}
org.clojure/tools.gitlibs {:mvn/version "0.2.64"}
Let's recurse. With the help of lein:
[s3-wagon-private "1.3.1"]
[com.amazonaws/aws-java-sdk-s3 "1.11.184" :exclusions
[[com.fasterxml.jackson.core/jackson-core]
[com.fasterxml.jackson.core/jackson-databind]]]
[com.amazonaws/aws-java-sdk-core "1.11.184"]
[com.fasterxml.jackson.dataformat/jackson-dataformat-cbor "2.6.7"]
[commons-logging "1.1.3"]
[joda-time "2.8.1"]
[software.amazon.ion/ion-java "1.0.2"]
[com.amazonaws/aws-java-sdk-kms "1.11.184"]
[com.amazonaws/jmespath-java "1.11.184"]
[com.fasterxml.jackson.core/jackson-core "2.5.5"]
[com.fasterxml.jackson.core/jackson-databind "2.5.5"]
[com.fasterxml.jackson.core/jackson-annotations "2.5.0"]
[org.springframework.build/aws-maven "4.8.0.RELEASE" :exclusions
[[com.amazonaws/aws-java-sdk]]]
[org.slf4j/jcl-over-slf4j "1.7.5"]
[org.slf4j/slf4j-api "1.7.5"]
Of s3-private-wagon's deps, we're also missing
com.amazonaws/aws-java-sdk-s3 (and its deps
com.amazonaws/aws-java-sdk-core software.amazon.ion/ion-java
com.amazonaws/aws-java-sdk-kms com.amazonaws/jmespath-java) and
org.springframework.build/aws-maven; everything else looks okay.
[org.clojure/tools.gitlibs "0.2.64"]
[com.jcraft/jsch.agentproxy.connector-factory "0.0.9"]
[com.jcraft/jsch.agentproxy.core "0.0.9"]
[com.jcraft/jsch.agentproxy.pageant "0.0.9"]
[com.jcraft/jsch.agentproxy.sshagent "0.0.9"]
[com.jcraft/jsch.agentproxy.usocket-jna "0.0.9"]
[net.java.dev.jna/jna-platform "4.1.0"]
[net.java.dev.jna/jna "4.1.0"]
[com.jcraft/jsch.agentproxy.usocket-nc "0.0.9"]
[com.jcraft/jsch.agentproxy.jsch "0.0.9"]
[org.eclipse.jgit "4.10.0.201712302008-r"]
[com.googlecode.javaewah/JavaEWAH "1.1.6"]
[com.jcraft/jsch "0.1.54"]
[org.apache.httpcomponents/httpclient "4.5.2"]
[commons-codec "1.9"]
[org.apache.httpcomponents/httpcore "4.4.4"]
libjsch-agent-proxy-java is in Debian but needs a version bump from
0.0.8 to 0.0.9. jgit is also in Debian but needs a major version bump
from 3.7.1 to 4.10.0.
In summary...
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:
- 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"
- org.clojure/tools.gitlibs "0.2.64"
I'm happy to package the two new Clojure dependencies, s3-wagon-private
and tools-gitlibs. Anyone wanna package some AWS Java stuff?
- e
signature.asc
Description: Digital signature
Bug#891136: tools-deps-alpha
Okay, this dependency tree is a lot hairier than I initially expected. `lein deps :tree` says: [org.clojure/tools.deps.alpha "0.5.398"] [org.apache.maven.resolver/maven-resolver-api "1.1.1"] [org.apache.maven.resolver/maven-resolver-connector-basic "1.1.1"] [org.apache.maven.resolver/maven-resolver-impl "1.1.1"] [org.apache.maven.resolver/maven-resolver-spi "1.1.1"] [org.apache.maven.resolver/maven-resolver-transport-file "1.1.1"] [org.apache.maven.resolver/maven-resolver-transport-http "1.1.1"] [org.apache.httpcomponents/httpclient "4.5.4" :exclusions [[commons-logging]]] [commons-codec "1.10"] [org.apache.httpcomponents/httpcore "4.4.8"] [org.slf4j/jcl-over-slf4j "1.7.25"] [org.apache.maven.resolver/maven-resolver-transport-wagon "1.1.1"] [org.apache.maven.wagon/wagon-provider-api "3.0.0"] [org.apache.maven.resolver/maven-resolver-util "1.1.1"] [org.apache.maven/maven-resolver-provider "3.5.2"] [com.google.guava/guava "20.0"] [javax.inject "1"] [org.apache.commons/commons-lang3 "3.5"] [org.apache.maven/maven-model-builder "3.5.2"] [org.apache.maven/maven-artifact "3.5.2"] [org.apache.maven/maven-builder-support "3.5.2"] [org.codehaus.plexus/plexus-component-annotations "1.7.1" :exclusions [[junit]]] [org.codehaus.plexus/plexus-interpolation "1.24"] [org.apache.maven/maven-model "3.5.2"] [org.apache.maven/maven-repository-metadata "3.5.2"] [org.codehaus.plexus/plexus-utils "3.1.0"] [org.clojure/data.xml "0.2.0-alpha5"] [org.clojure/data.codec "0.1.0"] [org.clojure/tools.cli "0.3.5"] [org.clojure/tools.gitlibs "0.2.59"] [com.jcraft/jsch.agentproxy.connector-factory "0.0.9"] [com.jcraft/jsch.agentproxy.core "0.0.9"] [com.jcraft/jsch.agentproxy.pageant "0.0.9"] [com.jcraft/jsch.agentproxy.sshagent "0.0.9"] [com.jcraft/jsch.agentproxy.usocket-jna "0.0.9"] [net.java.dev.jna/jna-platform "4.1.0"] [net.java.dev.jna/jna "4.1.0"] [com.jcraft/jsch.agentproxy.usocket-nc "0.0.9"] [com.jcraft/jsch.agentproxy.jsch "0.0.9"] [org.eclipse.jgit "4.10.0.201712302008-r"] [com.googlecode.javaewah/JavaEWAH "1.1.6"] [com.jcraft/jsch "0.1.54"] [org.slf4j/slf4j-nop "1.6.2"] [org.slf4j/slf4j-api "1.6.2"] [s3-wagon-private "1.3.1"] [com.amazonaws/aws-java-sdk-s3 "1.11.184" :exclusions [[com.fasterxml.jackson.core/jackson-core] [com.fasterxml.jackson.core/jackson-databind]]] [com.amazonaws/aws-java-sdk-core "1.11.184"] [com.fasterxml.jackson.dataformat/jackson-dataformat-cbor "2.6.7"] [commons-logging "1.1.3"] [joda-time "2.8.1"] [software.amazon.ion/ion-java "1.0.2"] [com.amazonaws/aws-java-sdk-kms "1.11.184"] [com.amazonaws/jmespath-java "1.11.184"] [com.fasterxml.jackson.core/jackson-core "2.5.5"] [com.fasterxml.jackson.core/jackson-databind "2.5.5"] [com.fasterxml.jackson.core/jackson-annotations "2.5.0"] [org.springframework.build/aws-maven "4.8.0.RELEASE" :exclusions [[com.amazonaws/aws-java-sdk]]] [ch.qos.logback/logback-classic "1.0.12"] [ch.qos.logback/logback-core "1.0.12"] This is leiningen-levels of dependency spaghetti. I'm going to put this ITP on hold while I regroup and figure out the details of the dependency management story. There's no way I'll be able to get this done before the Ubuntu 18.04 LTS feature freeze (Mar. 1, 2018); this will have to be an ongoing project, hopefully making it into the buster release. Perhaps we can backport it later. - e signature.asc Description: Digital signature
Bug#891136: deja vu
This ITP is currently blocked on https://dev.clojure.org/jira/browse/TDEPS-44 Upstream depends on a version of Maven that is unavailable in the archive. Because of significant API changes between Maven 3.3.9 (currently required) and Maven 3.5 (in Debian), it doesn't make sense for me to attempt a Debian-specific patch. - e signature.asc Description: Digital signature
Bug#891141: ITP: clojure-cli -- upstream CLI entrypoints for Clojure
Package: wnpp Severity: wishlist Owner: Elana Hashman <ehash...@debian.org> Control: block -1 by 891136 * Package name: clojure-cli Version : 1.9.0.341 Upstream Author : Rich Hickey * URL : https://github.com/clojure/brew-install * License : EPL-1.0 Description : upstream CLI entrypoints for Clojure Currently, Debian ships our own custom CLI entrypoints for Clojure (clojure and clojurec), under the `clojure` source package. With the 1.9 upstream release, the Clojure devs are now providing `clj` and `clojure` entrypoint scripts as part of the "brew-install" package. This name is a little misleading, as this package contains useful distro-agnostic scripts. We should do our best in Debian to mirror the behaviour in upstream. Hence, I plan on moving the "clojure" binary package (that contains our current entrypoints) to use this upstream source package instead, and will remove the custom Debian entrypoints (or possibly rename them to provide some backwards compatibility?) signature.asc Description: Digital signature
Bug#891136: ITP: tools-deps-alpha-clojure -- functional API for dependency management and classpath creation
Package: wnpp Owner: Elana Hashman <ehash...@debian.org> Severity: wishlist * Package name: tools-deps-alpha-clojure Version : 0.5.393 Upstream Author : Rich Hickey * URL : https://github.com/clojure/tools.deps.alpha * License : EPL-1.0 Programming Lang: Clojure Description : functional API for dependency management and classpath creation tools.deps.alpha makes it simple and easy to interactively consume JVM libraries with Clojure, without dragging in unrelated concerns of building programs or project management. It provides a functional API for transitive dependency graph expansion and the creation of classpaths. signature.asc Description: Digital signature
Bug#886562: ITP: core-specs-alpha-clojure -- specs to describe Clojure core macros and functions
Package: wnpp Severity: wishlist Owner: Elana Hashman <ehash...@debian.org> * Package name: core-specs-alpha-clojure Version : 0.1.24 Upstream Author : Rich Hickey * URL : https://github.com/clojure/core.specs.alpha * License : EPL-1.0 Programming Lang: Clojure Description : specs to describe Clojure core macros and functions core.specs.alpha is a Clojure library containining specs to describe Clojure core macros and functions. Clojure 1.9 depends on this library and provides it to users of Clojure. This dependency is required for the packaging of Clojure 1.9. signature.asc Description: Digital signature
Bug#886561: ITP: spec-alpha-clojure -- library to describe the structure of data and functions
Package: wnpp Owner: Elana Hashman <ehash...@debian.org> Severity: wishlist * Package name: spec-alpha-clojure Version : 0.1.143 Upstream Author : Rich Hickey * URL : https://github.com/clojure/spec.alpha * License : EPL-1.0 Programming Lang: Clojure Description : library to describe the structure of data and functions spec is a Clojure library to describe the structure of data and functions. Specs can be used to validate data, conform (destructure) data, explain invalid data, generate examples that conform to the specs, and automatically use generative testing to test functions. Clojure 1.9 depends on this library and provides it to users of Clojure. This dependency is required for the packaging of Clojure 1.9. signature.asc Description: Digital signature
Bug#819811: ITP: leiningen
For those that have been waiting for updates on this, I realize I have mostly been sending updates to pkg-clojure-maintainers, so let me also comment directly on the bug! I have preliminary packaging that builds up at https://anonscm.debian.org/git/pkg-clojure/leiningen-clojure.git/ Hopefully will be getting this uploaded soon. - e signature.asc Description: Digital signature
Bug#819811: ITP: leiningen -- simple build system for Clojure
All, We are getting very close! I have completed packaging for the three outstanding blocking bugs: - #862233: use maven 3.5.0 and upgrade to pomegranate 0.4.0-alpha1 https://anonscm.debian.org/cgit/pkg-clojure/pomegranate-clojure.git/ -- this one is complicated, wanted a few more eyes before upload, but I did test it - #712908: packaged stencil 0.5.0 https://anonscm.debian.org/cgit/pkg-clojure/stencil-clojure.git/ -- Barry Warsaw promised me he'd upload this at the PyCon sprints - #719664: packaged parsley 0.9.3 https://anonscm.debian.org/cgit/pkg-clojure/parsley-clojure.git/ -- just need a sponsor Once these all get uploaded and freeze is over, we should be able to get the leiningen packaging completed. Looking forward to that. - e
Bug#719664: ITP: parsley-clojure -- parser generator for context-free grammars
Finished packaging... https://anonscm.debian.org/cgit/pkg-clojure/parsley-clojure.git/ https://csclub.uwaterloo.ca/~ehashman/debian/libparsley-clojure/ Just need someone to check this over and sponsor, - e
Bug#819811: ITP: leiningen -- simple build system for Clojure
I mentioned this on IRC, but also wanted to send a message out to the bug list for posterity... I've hit a bit of a snag with the libpomegranate-clojure packaging (#852246). While I did get the package to build, it doesn't actually work. I realized it relies on maven 3.0.4, which is only packaged in old-stable. Jessie packages version 3.0.5, and testing/unstable has 3.3.9. There are many breaking changes between Maven 3.0.4 and 3.3.9. Maven 3.0.4 poses two problems: first, it is affected by a medium-severity CVE[1] and should be patched to 3.0.5. Second, it relies on an old version of Aether under org.sonotype. Aether moved from being maintained by Sonotype to being maintained by Eclipse in 2012, and then Eclipse archived the Aether project in 2016. The Aether changes are why pomegranate does not work against Maven 3.3.9; many classes have been renamed, refactored, and moved. The most recent Maven release, 3.5.0, covers the migration of the Aether code directly into the Maven project.[2] It was released very recently, at the beginning of April. I see there's been some community effort to migrate pomegranate to Maven 3.3.9, but it has not yet succeeded.[3] I took a look at doing that last night, and it turns out to be quite complex. Hence, I see the following possible paths forward: - Upgrade upstream (whether that involves changes in pomegranate or directly in leiningen) to use Maven 3.5.0, and wait for Maven 3.5.0 to be packaged for unstable. - Upgrade upstream to use Maven 3.3.9. I don't think that including a Maven 3.0.5 package just for leiningen is possible, and that would also just constitute a stopgap in my opinion. Upgrading to Maven 3.5.0 is, in my opinion, the best option, as 3.3.9 depends on orphaned versions of Aether. Thoughts? - e [1]: https://maven.apache.org/security.html [2]: https://maven.apache.org/docs/3.5.0/release-notes.html [3]: https://github.com/cemerick/pomegranate/pull/80
Bug#819811: ITP: leiningen -- simple build system for Clojure
Owner: Elana Hashman <deb...@hashman.ca> Hi all, Phil has done a bunch of great work significantly reducing the dependency profile of leiningen, so I have updated all the blocking issues and we are down to 8. Of those, two are addressed by packages sitting in NEW and I will have more to follow. I wrote a (janky, alpha) tool to assist in Clojure packaging, for anyone that might be interested: https://github.com/ehashman/clj-helper I just got added to the Debian Java and Debian Clojure packaging groups so I should be able to start working on some of the version upgrades as well. ChangZhuo, I'm going to claim this bug since I haven't heard anything from you in the last few months :) - e
Bug#754504: ITP: libpedantic-clojure -- Checkout dependency graphs for common unexpected cases
I have built a working package for version 0.2.0: https://github.com/ehashman/pedantic https://csclub.uwaterloo.ca/~ehashman/debian/libpedantic-clojure/ You can test it by installing the package and attempting an import in the REPL: $ clojure -cp /usr/share/java/pedantic.jar Clojure 1.8.0 user=> (use 'pedantic.core) nil user=> (doc set-ranges!) - pedantic.core/set-ranges! ([ranges paths]) Set ranges to contain all paths that asks for a version range You may note the dependency on libpomegranate-clojure version 0.2.0, which I requested an upgrade for in #852246. After chatting with Phil, I learned that when you build some project A with leiningen, and project A depends on project B, and both projects depend on different versions of project C (say C_A and C_B), then C_A, the version required by A, will be used in the build. Hence, there should be no problem with upgrading libpomegranate-clojure to 0.3.1, as it's currently working and tested in the lein builds. - e
Bug#698693: ITP: libclasslojure-clojure -- Clojure library to create a classloader with an alternate classpath
On 2017-02-28 23:37, Elana Hashman wrote: Hi, I took a stab at packaging this. This is my first package submitted to Debian so I don't know what I'm doing. All the debian/ stuff can be found here: https://github.com/ehashman/classlojure Let me know what you think! - e Oh, forgot to mention---I packaged version 0.7.1 as opposed to 0.6.6 as noted in the initial ITP, as 0.7.1 is needed for packaging leiningen2.
Bug#698693: RFP: libclasslojure-clojure -- Clojure library to create a classloader with an alternate classpath
Control: retitle -1 ITP: libclasslojure-clojure -- Clojure library to create a classloader with an alternate classpath Hi, I took a stab at packaging this. This is my first package submitted to Debian so I don't know what I'm doing. All the debian/ stuff can be found here: https://github.com/ehashman/classlojure Let me know what you think! - e
Bug#819811: ITP: leiningen -- simple build system for Clojure
All the first-degree dependencies should now be marked as blocking. Now for some packaging... There are a lot of deps and granddeps so if you're interested in helping out, please feel free to claim one (or many)! - e
Bug#855963: RFP: libreply-clojure -- A fitter, happier, more productive REPL for Clojure
Package: wnpp Severity: wishlist Control: block 819811 by -1 * Package name: libreply-clojure Version : 0.3.7 Upstream Author : Colin Jones * URL : https://github.com/trptcolin/reply * License : EPL 1.0 Programming Lang: Clojure Description : A fitter, happier, more productive REPL for Clojure This library is a build-dep for leiningen2.
Bug#819811: ITP: leiningen -- simple build system for Clojure
On 2017-01-19 16:12, Tom Marble wrote: I've created a new page on the Debian wiki for this purpose: https://wiki.debian.org/Clojure/Leiningen Thanks for the great work on the wiki page, Tom, Phil! I've gone ahead and filed version upgrade requests as blocking this bug for all the packages identified on the wiki as needing upgrades to support leiningen 2.7.2. Should I also go ahead and file RFPs for the missing packages for visibility? - e
Bug#819811: ITP: leiningen -- simple build system for Clojure
Hello! Finally following up with some conversations I had at Clojure/conj, I'd like to help get the ball rolling on this again. Based on leiningen 2.7.1's dependencies, here's what we'll need to package/upgrade to make this happen. Packages that have a higher version in Debian unstable than in leiningen 2.7.1: libdynapath-clojure aka org.tcrawley/dynapath (2.5.1 > 2.4.1) libmaven-indexer-java aka org.apache.maven.indexer/indexer-core (5.1.1 > 4.1.3) libcommons-io-java aka commons-io (2.5 > 2.4) All but libmaven-indexer-java have been upgraded to the correct versions on upstream leiningen master. I've submitted a pull request to upgrade that dependency: https://github.com/technomancy/leiningen/pull/2234 Packages that are in Debian with the right versions: librobert-hooke-clojure aka robert/hooke (1.3.0) libwagon2-java aka org.apache.maven.wagon/wagon-http (2.10) libcom-hypirion-io-clojure aka com.hypirion/io (0.3.1) libdata-xml-clojure aka org.clojure/data.xml (0.0.8) libcomplete-clojure aka clojure-complete (0.2.4) Packages that are in Debian, but need updates: libbultitude-clojure aka bultitude (0.2.7 < 0.2.8) libpomegranate-clojure aka com.cemerick/pomegranate (0.2.0 < 0.3.1) libslingshot-clojure aka slingshot (0.10.3 < 0.12.2) Here's the full dependency chains of all the missing packages (per `lein deps :tree`): [cheshire "5.6.3"] [com.fasterxml.jackson.core/jackson-core "2.7.5"] [com.fasterxml.jackson.dataformat/jackson-dataformat-cbor "2.7.5"] [com.fasterxml.jackson.dataformat/jackson-dataformat-smile "2.7.5"] [tigris "0.1.1"] [classlojure "0.6.6"] [useful "0.8.3-alpha8"] [org.clojure/tools.macro "0.1.1"] [clj-http "2.0.1"] [commons-codec "1.10" :exclusions [[org.clojure/clojure]]] [org.apache.httpcomponents/httpclient "4.5" :exclusions [[org.clojure/clojure]]] [org.apache.httpcomponents/httpcore "4.4.1" :exclusions [[org.clojure/clojure]]] [org.apache.httpcomponents/httpmime "4.5" :exclusions [[org.clojure/clojure]]] [potemkin "0.4.1" :exclusions [[org.clojure/clojure]]] [clj-tuple "0.2.2"] [riddley "0.1.10"] [pedantic "0.2.0"] [net.cgrand/parsley "0.9.3" :exclusions [[org.clojure/clojure]]] [net.cgrand/regex "1.1.0"] [org.clojure/tools.nrepl "0.2.12"] [reply "0.3.7" :exclusions [[ring/ring-core] [org.thnetos/cd-client]]] [clj-stacktrace "0.2.7"] [com.cemerick/drawbridge "0.0.6" :exclusions [[org.clojure/tools.nrepl]]] [jline "2.12.1"] [net.cgrand/sjacket "0.1.1" :exclusions [[org.clojure/clojure]]] [org.clojure/tools.cli "0.3.1"] [trptcolin/versioneer "0.1.1"] [stencil "0.5.0" :exclusions [[org.clojure/core.cache]]] [quoin "0.1.2"] [scout "0.1.0"] To make that slightly more legible, here are the (grand-)dependencies we need in Debian: libtools-macro-clojure (0.1.5 > 0.1.1) libcommons-codec-java (1.10) libhttpclient-java (4.5) libhttpcore-java (4.4.6 > 4.4.1) libhttpmime-java (4.5.2 > 4.5) libversioneer-clojure (0.1.1) libscout-clojure (0.1.1 > 0.1.0) Here are the ones that are in Debian but need upgrades: libclj-stacktrace-clojure (0.2.6 < 0.2.7) libtools-cli-clojure (0.2.4 < 0.3.1) libjline2-java (2.11 < 2.12.1) And last, here are all the missing ones, preserving dependency chains: [cheshire "5.6.3"] [com.fasterxml.jackson.core/jackson-core "2.7.5"] [com.fasterxml.jackson.dataformat/jackson-dataformat-cbor "2.7.5"] [com.fasterxml.jackson.dataformat/jackson-dataformat-smile "2.7.5"] [tigris "0.1.1"] [classlojure "0.6.6"] [useful "0.8.3-alpha8"] [clj-http "2.0.1"] [potemkin "0.4.1" :exclusions [[org.clojure/clojure]]] [clj-tuple "0.2.2"] [riddley "0.1.10"] [pedantic "0.2.0"] [net.cgrand/parsley "0.9.3" :exclusions [[org.clojure/clojure]]] [net.cgrand/regex "1.1.0"] [org.clojure/tools.nrepl "0.2.12"] [reply "0.3.7" :exclusions [[ring/ring-core] [org.thnetos/cd-client]]] [com.cemerick/drawbridge "0.0.6" :exclusions [[org.clojure/tools.nrepl]]] [net.cgrand/sjacket "0.1.1" :exclusions [[org.clojure/clojure]]] [stencil "0.5.0" :exclusions [[org.clojure/core.cache]]] [quoin "0.1.2"] Hope everyone finds this helpful. - e
