This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # arachne (1)
- # aws (1)
- # beginners (43)
- # boot (67)
- # cider (7)
- # cljs-dev (14)
- # cljsjs (6)
- # clojure (215)
- # clojure-czech (2)
- # clojure-dev (12)
- # clojure-dusseldorf (2)
- # clojure-italy (1)
- # clojure-russia (22)
- # clojure-spec (2)
- # clojure-uk (33)
- # clojurescript (85)
- # cryogen (2)
- # cursive (1)
- # datascript (22)
- # datomic (18)
- # dirac (8)
- # hoplon (9)
- # klipse (1)
- # lein-figwheel (5)
- # leiningen (126)
- # off-topic (1)
- # om (57)
- # onyx (159)
- # pedestal (33)
- # planck (2)
- # re-frame (52)
- # reagent (3)
- # ring (2)
- # ring-swagger (16)
- # test-check (12)
- # testing (5)
- # untangled (86)
- # vim (6)
hi. i've been trying to get checkouts to work for the first time all weekend with quite a degree of frustration and wondering if anyone is around who could help. i suspect it could be a problem with my symlink: i know i'm creating it correctly, although it's appearing incorrectly in osx finder (not always reliable). however, it's my understanding lein should fall back on maven's cached version as it's up to date. it does appear to be doing so, in face i'm receiving two messages for checkouts failing as well as a built-in function i have overridden, except it's throwing an error in the linked library i do not get when running that library on its own. ...so you can imagine with all these variables how my head is spinning quite a bit by now
@mping sorry for disappearing. a lot of this was usual piss poor error messages i needed a very experienced clojurian to talk me through. so at this point seems the only issue is the checkout failing, not anything else i referred to. and, rather unfortunate for me, but i suspect that's due to the symlink being screwed up...which i can only explain from creating a .bash_profile against best practices 😞
@sophiago: it might help to post the two projects (the main project and the checkout one) along with the directory structure under the root project (specifically the
checkouts directory). and also the command you're using to create the symlink. that way we can try and rule out any symlink issues and/or issues with the specific libraries
@trptcolin i'm 99% certain i know the bash is correct: ln -s target location
the problem i see in osx finder is it shows up as a file that when examined is an alias to itself
@sophiago i swear i get the
ln -s syntax mixed up at least half the time because my puny brain can't distinguish the meaning of "target" & "location"
however in terminal it does appear to include 8 items, which would be accurate for the checkout project
ls -l checkouts show you what you expect? a symlink to the root directory of the project that you want as a checkout dependency?
yes, that's the thing. it does. only in finder does it appear screwed up. so i obviously trust terminal not finder
you know what. idk why i pushed back on just posting both for you to examine if you offered
that's what i was just thinking - might help to verify if it's an issue totally confined to your machine, in which case that narrows the scope of possible issues down
@trptcolin lol so i realized i back everything up on dropbox daily and just had to back it up now and create a public link to share 😛
also re: the symlink issue, i was just assuming it must have been due to editing my .bash_profile all along while not remembering what was in there...i just checked and it's two lines: one with some corny ascii art for my term prompt and another to correct the color profile on ansi terms
ok, so yeah, i see these
Could not find artifact symbolic-algebra:symbolic-algebra:jar:0.1.0 errors after adding the symlink. is that the one you saw? just to confirm before proceeding
i didn't check, but assume so since i ran lein install on the dep and it's up to date
(WARN ignoring checkouts directory /Users/sophiagold/Desktop/Clojure/power-series/checkouts/.DS_Store as it does not contain a project.clj file.) (WARN ignoring checkouts directory /Users/sophiagold/Desktop/Clojure/power-series/checkouts/symbolic-algebra_sparse as it does not contain a project.clj file.)
/Users/sophiagold/Desktop/Clojure/power-series/checkouts/.DS_Store is the one that's complaining, so i was just saying that one
maybe, but i'm a bit confused about that second error: what do you get when you do:
ls -l /Users/sophiagold/Desktop/Clojure/power-series/checkouts/symbolic-algebra_sparse
ls -l /Users/sophiagold/Desktop/Clojure/power-series/checkouts/symbolic-algebra_sparse/
same for both... shows the last attempt at creating that symlink, appears to have worked
for the second command, i see here a project.clj file among the rest of the directory listings
lrwxr-xr-x 1 sophiagold staff 23 Oct 24 11:32 /Users/sophiagold/Desktop/Clojure/power-series/checkouts/symbolic-algebra_sparse/ -> symbolic-algebra_sparse
relative paths in symlinks aren't something i've got a full mental model of, but i think that means it points to itself. i'd try deleting the symlink & re-creating w/ the absolute path as the target.
i got help with this on #macosx and was told i did it correctly and not to trust the finder, but they also called the linux folks in #bash "idiots" and then proceeded on some creepy rant about "SJWs" that would have fit in on silicon valley
once i do the
lein install on the dependency, i get to that same duplicated
-main issue, which is because of the
:refer :all in
remove that (and update one non-ns-qualified reference to
sub) and you should be golden
oh, both arguments to
ln, i see. yeah can't hurt (assuming you're only using this symlink locally)
@trptcolin and the message you said could be eliminated by deleting that .DS_Store? i still have one of those. doesn't seem to be a real concern, but could you elucidate at all?
sure. i've never had any bad effects from deleting .DS_Store 🙂 http://apple.stackexchange.com/questions/69467/consequences-of-deleting-ds-store
sorry, yeah i guess there's some action you can do in finder, maybe even just viewing certain directories, that'll make it return ¯\(ツ)/¯
either way, it's just a warning and it should be ignoring that directory anyway so you should be 👍 on that
well, looks like i'm good (not really, i have a very confusing error...just doesn't seem lein related). thanks so much for your help!
hah, looks like i'm still #3 on the commit chart, but i bet it's mostly small changes (repl version bumps)
ah ok. i asked because i'm kind of "lone wolf" status rn and lein is not exactly my ideal project, but it's so amazingly well organized and they have all those issues that are tagged as not requiring much knowledge of the codebase. so i've obviously considered just jumping in and starting patching stuff since it seems like the #1 easiest way for me to do semi-large scale open source work at this point
and even if it's not my interest, contributing to a build tool must be a great learning experience, right?
like if my long term interests involve PLT and compiler design and such? and i'm i no way above grunt work? i would think this is not a bad choice. i just waffle to some degree because i'm deeply ambivalent about the jvm seeing as i really don't like java one bit and that limits what i'll eventually do in this area
sure. yeah, definitely lots of organizational / git / compatibility stuff that'll cross over into any other project
i'm at the very beginning of learning Haskell so i just may put it off to see what the ecosystem is like over there as far as opportunities...as well as my ability to do anything with them in a reasonable time frame...
anyway, i deeply appreciate your help today. and i suppose it also reflects on my view of lein organization-wise as extremely positive, whether i end up contributing or not 😄
G'day everyone! I hate to be that guy, but I was wondering whether it would be possible to get an ETA on this: https://github.com/technomancy/lein-licenses/pull/6 ?
This is holding me up, and while I can test locally using a hand-rolled build of @bcarrell's change, that doesn't work so well for externally hosted tooling (Travis CI, etc.).
hmm, tricky issue: lein changes an
:internal API, and this plugin breaks. which lein versions should this plugin work with?
it's not like people have lein version managers and run 2 different lein versions (i think / hope)
i'll add a comment to the PR, just verified it. afaik only technomancy has access here.
Thanks @trptcolin !