Perl 6 - the future is here, just unevenly distributed

IRC log for #darcs, 2014-10-08

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

All times shown according to UTC.

Time Nick Message
00:41 mizu_no_oto joined #darcs
01:28 Mempko joined #darcs
02:27 mizu_no_oto joined #darcs
05:40 dolio joined #darcs
05:47 lelit joined #darcs
08:39 gal_bolle joined #darcs
11:06 mizu_no_oto joined #darcs
11:11 carter joined #darcs
11:11 wavis joined #darcs
11:11 wavis joined #darcs
11:13 vikraman joined #darcs
11:38 mizu_no_oto joined #darcs
12:00 mizu_no_oto joined #darcs
12:35 gh_ joined #darcs
12:50 mizu_no_oto joined #darcs
13:20 sm g'day all
13:21 sm I'm back from vacation and working on darcs hub.. which begins with building darcs head (screened)
13:21 sm I'm wondering if I should add -fterminfo and/or -fcolor when I do that ?
13:24 mizu_no_oto joined #darcs
13:38 mizu_no_oto joined #darcs
13:45 gh_ sm, I did not even know about terminfo
13:45 sm also, can I retroactively apply a tag for eg the old ssh-0.12.2.1 release, without reordering the history in the published repo ?
13:45 sm hi gh_
13:45 gh_ hmm
13:45 gh_ try it locally
13:46 gh_ it should not provoke any reordering
13:46 gh_ by default darcs does not attempt to reorder patches
13:46 sm locally, my first thought is to pull up to the desired patch in a second copy, add the new tag, pull the rest
13:48 sm and from there I could just push to the repo on hub, and the new tag will go there - it'll appear out of order in the changes view, but it'll have the right dependencies ? that seems right
13:50 sm or, maybe I can do it without a second copy using darcs tag OLDTAG -m OLDPATCH
13:50 sm but after trying it I don't see any effect from using -m
13:52 sm confused.. nm
13:53 sm ah right, -m just sets the name of the tag
14:03 gh_ sm, yes it will have the right dependencies
14:07 sm I've released ssh-0.2.13.1, if anyone would like to take it over please do
14:10 sm (cc alexsuraci)
14:28 mizu_no_oto joined #darcs
14:28 byorgey joined #darcs
14:35 sm why is darcs-2.9.9 log now showing "patch HASH" for each patch ?
14:42 gh_ I did it.. let me recollect the reasons
14:43 gh_ there were several persons showing up on IRC and asking for a way to refer to a patch using a hash
14:45 sm ah, makes sense. It looked a bit like debug output, maybe "Hash: HASH" below the date would be even nicer
14:45 gh_ that hash (the patch hash) is more unique than a patch/tag name
14:45 sm huh, I you were following git style which shows it just that way
14:45 gh_ and the only way to see it was to use log --xml
14:45 sm I guess
14:46 gh_ yes, that's what I did. it does not have to be that way forever, though.
14:49 gh_ I found the line-by-line format practical for grepping through the output of log
14:49 sm I need to update my darcsoneline filter script somehow
14:49 sm I'm really missing --oneline, -N, and --grep from git
14:51 gh_ you mean git has --oneline and you are missing it in darcs?
14:51 sm yes, exactly
14:51 sm I used to always darcs changes | grep '*', then I made a better script which also shows tags
14:52 sm the great majority of the time a compact one line per patch listing is more useful for me
14:54 gh_ implementing it in darcs will probably cost you more time than updating the script, but in the long term it would be more useful :)
14:55 sm I dunno man, I can't make much sense of this (one line) bash script :)
14:56 sm alias darcsoneline="egrep '^\w' -A1 | egrep -v '^(--|The remote repository has|Would pu)' | sed '$!N;s/\n/ /'"
14:56 sm seems like it should have been unaffected by this change
14:57 sm don't waste any cycles on it, I just share it for fun
15:03 sm stulli, Heffalump: I've deployed your patches at hub.darcs.net, thanks a lot!
15:03 sm it's built with latest darcs-screened, but still GHC 7.6
15:06 sm building darcsden with GHC 7.8 has problems with MonadCatchIO-mtl, haskell-src-exts, and lens
15:07 sm when we can iron those out I'll do a darcsden release
15:16 sm we also need to release darcs 2.9, or repair darcsden's darcs-2.8 compatibility
15:21 sm the bad news: viewing any patch on darcs hub now fails :(
15:25 sm and, since I deployed twice this morning I've lost the old binary. drat.
15:25 gh_ \o/
15:35 sm to fetch the "require ssh 0.2.13+" patch at http://hub.darcs.net/simon/darcsden/changes , it requests http://hub.darcs.net/simon/darcsden/renderedpatch/20140505210004-3c3f9
15:36 gh_ ah, this is because the hash format changed in screened
15:36 sm yeah, it seems so
15:37 gh_ before the "hash in darcs log" patch, the hash has the A-B-C format, darcsden currently uses only the A-B part, but now the hash is just C
15:38 sm I think some part of libdarcs is still providing the old hash format, which darcsden's changes links are using
15:44 amgarchIn9 joined #darcs
15:45 gh_ sm, there is only one function providing the A-B-C format, it is there to give the file name in old-fashioned repositories. so you probably don't want to use it.
15:46 gh_ s/there//
15:46 sm naturally that will be the one we're using :)
15:46 sm is it "makeFilename" ?
15:47 sm should it use makePatchname now ?
15:48 sm yep
15:49 sm hopefully darcsden doesn't keep old hashes in the db at all
15:54 sm deployed that change, still not working. I think I'll have to build with older darcs-screened for today
15:57 stulli joined #darcs
15:59 sm ugh, that'll be waste-work.
16:01 sm and I'm out of time for today.. if anyone has some, see if you can get patch a3458df589a9d6df9ccfc41764eb9b92304646ea in hub.darcs.net:simon/darcsden ("use latest darcs's hashes for patch ids, instead of old filename ids (WIP, will be rewritten)") working
16:02 sm that kind of change will also break existing links to patches, eg on issue pages, which is a pity. Maybe there's a way to keep the old ids working too.
16:07 amgarchIn9 joined #darcs
16:08 sm noted as http://hub.darcs.net/simon/darcsden/issue/111 . later all
16:51 gh_ joined #darcs
16:58 Heffalump sm: I actually have a prototype "--ask-deps" flag to darcs tag to do ewxactly what you wanted above
17:16 byorgey joined #darcs
17:18 stepkut joined #darcs
17:18 gh_ joined #darcs
17:32 amgarchIn9 joined #darcs
17:51 amgarchIn9 joined #darcs
18:30 byorgey joined #darcs
19:49 amgarchIn9 joined #darcs
19:55 stepkut joined #darcs
19:56 amgarching joined #darcs
20:39 byorgey joined #darcs
21:22 Heffalump sm: when you say release 2.9, do you mean as a beta, or as a stable version (2.10)?
22:06 siel joined #darcs
22:16 mizu_no_oto joined #darcs
22:38 sm Heffalump: hi, I just mean a hackage release, so that the darcsden release will be installable from hackage
22:51 siel joined #darcs
23:24 Thaalos joined #darcs
23:34 siel joined #darcs
23:46 mizu_no_oto joined #darcs
23:48 siel joined #darcs
23:59 ggherdov` joined #darcs

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