On Wed, Jun 13, 2012 at 5:47 AM, Chas Emerick <c...@cemerick.com> wrote: > On Jun 12, 2012, at 7:12 PM, Phil Hagelberg wrote: > >> On Mon, Jun 11, 2012 at 1:48 PM, Phil Hagelberg <p...@hagelb.org> wrote: >>> On Mon, Jun 11, 2012 at 9:36 AM, Phil Hagelberg <p...@hagelb.org> wrote: >>>> These will be removed once Central gets back to working order, but >>>> they should help stem the flow of catastrophic build failures. >>> >>> While this will allow most builds to work, it's a band-aid solution. >>> Is there anyone on the Clojure/core team with a contact among those >>> who run Central who could get them to look into this? >> >> Central is back to normal, so I've removed the workaround jars on Clojars.
I don't believe the issue is entirely fixed as the checksums still don't match. The sha1sum of maven-metadata.xml is 643fa0e8afd24c907e5e7f268943957846b13d25, while maven-metadata.xml.sha1 claims 92472231000f7b66ebf43cb412c74b4ba3cd7277. -John -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
