clojars

http://clojars.org discussion and “support”, see http://status.clojars.org for status.
danielcompton 2016-09-19T04:38:41.000186Z

FAIL in (repair-metadata-corrects-versions) (repair_metadata.clj:53)
creates the correct metadata
expected: (= ["0.1.0" "0.2.0" "0.4.0" "0.5.0-SNAPSHOT"] (.getVersions versioning))
  actual: (not (= ["0.1.0" "0.2.0" "0.4.0" "0.5.0-SNAPSHOT"] ["0.2.0" "0.5.0-SNAPSHOT" "0.1.0" "0.4.0"]))

danielcompton 2016-09-19T04:38:53.000187Z

this is failing on a new ubuntu server, but not on my Mac, or in CI

danielcompton 2016-09-19T04:38:59.000188Z

I’m a bit puzzled

2016-09-19T11:31:33.000189Z

.getVersions should return the versions in the order they appear in maven-metadata.xml (I think). We add them in dir last modified order (https://github.com/clojars/clojars-web/tree/master/src/clojars/tools/repair_metadata.clj#L66)

2016-09-19T11:32:47.000191Z

maybe the version of java or the underlying syscalls used by FileUtils/copyDirectory copy in a different order on the new machine: https://github.com/clojars/clojars-web/tree/master/test/clojars/test/unit/tools/repair_metadata.clj#L17

danielcompton 2016-09-19T20:29:49.000193Z

I may be doing something silly, but leiningen seems to hang when I put a clojars repo replacement in the :user profile

danielcompton 2016-09-19T20:29:59.000194Z

it downloads from Central fine though

danielcompton 2016-09-19T20:30:10.000195Z

oh wait

danielcompton 2016-09-19T20:30:14.000196Z

it was doing a lein-npm install