Perl 6 - the future is here, just unevenly distributed

IRC log for #darcs, 2017-11-22

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
02:55 ilbot3 joined #darcs
02:55 Topic for #darcs is now http://darcs.net/ | logs: http://irclog.perlgeek.de/darcs/ | darcs 2.12.5 is out http://darcs.net/Releases/2.12
06:56 ThomasLocke joined #darcs
06:56 ThomasLocke joined #darcs
08:36 Weltraumschaf joined #darcs
11:39 Igloo joined #darcs
12:32 Igloo joined #darcs
12:50 Igloo joined #darcs
14:34 Igloo joined #darcs
17:01 sm hi dino-
17:02 sm I'm running couchdb 1.6.0-0ubuntu7 on darcs hub
17:06 sm also, I see code changes this year (eg Jul 2)
17:07 sm the released darcsden is too old, you'll want HEAD
17:08 sm and by the way thank you for your support
17:12 dino- Ah, so maybe the breakage isn't in the CouchDB library.
17:12 dino- There's a lot of forking in that guy, not sure who's in charge of it atm.
17:13 dino- What's happened here is, my boss got tired of hearing me bitch about git for several years and wants to give darcs a try at work. But the catch is, he's not thrilled about putting our source on hub.darcs.net and tasked me with putting a private server up for us.
17:13 dino- So I need to make this work OR ELSE.
17:20 dino- sm: Thank you as well for running things and the server resources. I set up a $15/mo auto Paypal thing which is I think what Github would charge if one wants to have private repos. I use hub.darcs.net for all of my work.
17:23 dino- sm: I did get the latest darcsden from Jul 3, patch 6ed1d03e79465531e93d71e5a416195001957e93
17:26 sm dino-: nice! it's actually not that hard to set up
17:27 sm try the latest
17:27 dino- I do have the latest darcsden. But it may be built against a too-old CouchDB lib, I think stack probably got it from hackage. Trying to switch that to a much more modern one on github.
17:28 sm oh you did. Then I'm confused.
17:28 sm darcs hub has CouchDB 1.2.2 from stackage
17:28 sm from hackage, as you say
17:29 sm I'll rebuild and confirm
17:29 dino- ok, thank you
17:30 dino- But yeah, I see it right there in the stack.yaml
17:43 dino- I'm going to also try to determine if this CouchDB is working right. All I have is the apt-get install and positive-looking info from systemctl
18:04 byorgey joined #darcs
18:04 byorgey joined #darcs
18:13 sm back.. this thing built
18:13 sm when does it go wrong for you dino-
18:18 sm runs too
18:24 sm by the way, I guess it's progress that GHC gave you a line number there :)
18:25 sm https://github.com/hsenag/haskell-couchdb/blob/CouchDB-1.2.2/src/Database/CouchDB/Unsafe.hs#L374
18:25 sm I wonder what value it showed
18:26 sm also, which readme says compatible with CouchDB 1.2 ? and is that talking about the haskell package or the db ?
18:28 dino- The Haskell library, The README, but that could have been just ignored forever.
18:28 sm oh, https://github.com/hsenag/haskell-couchdb/blob/master/README
18:28 dino- It goes wrong when I try to hit the main url, http://localhost:8900 with a web client
18:29 sm maybe you haven't set up the initial db ?
18:29 dino- I see this error in the darcsden error.log
18:29 dino- That could definitely be, yeah
18:31 dino- I didn't do anything to couch other than start it up.
18:31 sm https://hub.darcs.net/simon/darcsden#to-install has details
18:32 dino- I followed the darcsden README.md
18:33 sm (or http://hackage.haskell.org/package/darcsden#readme). I think you missed the darcsden --install step
18:33 dino- Aha, I thought that only for if I changed the ports. Now it makes sense.
18:34 sm aha. The README could use an edit then
18:35 sm well, that's a redundant statement. What README couldn't use an edit ?
18:35 dino- Excellent, that worked. Thank you so much for helping
18:36 sm no problem
18:38 sm good luck, I hope it's a big success and you make lots of improvements :)
18:39 sm out of interest, did you consider any other VCS, like fossil ?
18:40 sm recent fossil and VCS discussion: https://news.ycombinator.com/item?id=15752725
18:43 sm stirrings of discontent in the VCS world, time for another cycle of disruption!
18:46 dino- I did not even know that existed.
18:48 dino- Thanks for that. I figured sooner or later there would be discontent. We don't even use any of the many tools people lay on top of git at the office, which are part of it.
18:49 dino- Just git-o-lite, which massages the users, perms, directory stuff
19:58 byorgey joined #darcs
19:58 byorgey joined #darcs
20:00 Cthulhux i totally prefer darcs to fossil
20:32 Riastradh joined #darcs
20:45 dino- Is this still a real problem with darcs since darcs2? "A major problem with Darcs is poor time-complexity"
20:45 dino- This is from that recent Fossil thread on ycomb linked above
20:59 dino- I guess it is still a problem sometimes. I never see it but I don't work with super enormous groups and hairy merges
21:04 sm dino-: it's sadly hard to give a simple answer to that. But effectively, no, it is never a problem in normal usage
21:06 sm probably darcs users do not (or have learned to not) do hairy merges
21:08 sm also, I guess it's now possible to use darcs rebase to make them non-hairy
21:10 sm why, Cthulhux ?
21:10 Cthulhux shouldnt i? :x
21:11 sm there's no should :)
21:11 sm did you use fossil for long ?
21:11 Cthulhux not really
21:12 sm I haven't either, but I admire it
21:12 Cthulhux i saw one project using fossil, it was fresh IDE IIRC
21:12 Cthulhux i like the web interface, but that's pretty much it
21:12 sm and I expect their NG version will be great
21:12 Cthulhux installed, played with it for half an hour, got rid of it again
21:12 Cthulhux maybe ;-)
21:16 Cthulhux good night :)
21:16 sm o/
21:45 sm urgh, must.. fight.. the fossil-envy..
21:46 Riastradh sm: Fossil's command-line UI is so atrocious it won't take much effort to fight that if you ever actually try to use it.
21:48 sm Riastradh: oh really.. some folks seem to like it
21:50 * sm takes note
21:56 mizu_no__ joined #darcs

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | summary