2015-06-19 12:57:47 algitbot: hi 2015-06-19 12:59:32 algitbot: please be more reliable now... 2015-06-19 13:02:02 algitbot: i just pushed 2015-06-19 13:03:00 i changed it since last test 2015-06-19 13:07:37 build status will stay in devel? 2015-06-19 13:09:17 do we want that? 2015-06-19 13:10:37 i think in the long run we only want build errors in #alpine devel 2015-06-19 13:10:44 yep 2015-06-19 13:10:45 but i think for now, i just publish it all here 2015-06-19 13:10:48 and successes here 2015-06-19 13:11:08 or at least gather all build info, but it's probably impossible? 2015-06-19 13:11:17 no, its not impossible 2015-06-19 13:11:24 i need hack aports-build for that 2015-06-19 13:11:56 currently aports build sends to a 'irc/...' topic for things that should go to irc 2015-06-19 13:11:59 so message looks like "f93jf012 | x86_64: ok | x86: ok | armhf: failed (shortened url to logs)" 2015-06-19 13:12:00 but thats wrong 2015-06-19 13:12:17 then I could live with such message on #a-devel 2015-06-19 13:12:56 cannot collect all buildserver into same i think 2015-06-19 13:12:58 hum 2015-06-19 13:13:19 because armhf will take much more time that the others 2015-06-19 13:14:10 true 2015-06-19 13:14:14 just throwing ideas 2015-06-19 13:14:59 i will have the aports-build script to just thorow a message in mqtt topic 'build//errors' or similar 2015-06-19 13:15:07 so you can subscribe to only errors if you want 2015-06-19 13:15:53 if you want success you should be able to subscribe to 'mirror//' or similar 2015-06-19 13:16:28 so you in theory could apk upgrade on mqtt push 2015-06-19 13:39:28 algitbot: retry master 2015-06-19 13:40:25 algitbot: retry master 2015-06-19 13:41:13 algitbot: retry master 2015-06-19 13:41:29 algitbot: retry 3.2-stable 2015-06-19 13:42:06 doesn't seem to work? 2015-06-19 13:43:16 it works 2015-06-19 13:44:25 algitbot: retry 3.2-stable 2015-06-19 13:44:33 build/build-3-2-x86_64 pulling git 2015-06-19 13:44:33 build/build-3-2-x86 pulling git 2015-06-19 13:44:34 build/build-3-2-armhf pulling git 2015-06-19 13:44:34 build/build-3-2-x86_64 idle 2015-06-19 13:44:34 build/build-3-2-x86 idle 2015-06-19 13:44:34 build/build-3-2-armhf idle 2015-06-19 13:45:06 if you subscribe to build server activity you'll see they are pulling git, and then go to idle 2015-06-19 13:46:59 maybe we want it not give up if there are no new comits? 2015-06-19 13:47:29 the point of retry was repeat failed build 2015-06-19 13:47:42 if it works as the old retry did, it's fine 2015-06-19 13:47:55 i think it does 2015-06-19 13:48:34 hm 2015-06-19 13:53:15 I'm going home, I can check it later 2015-06-19 13:53:20 I mean, push something broken 8) 2015-06-19 13:53:44 it never worked better than this i think 2015-06-19 13:53:54 but i am thinking how to properly do this 2015-06-19 13:54:13 the problme is that the script will run in a loop 2015-06-19 13:54:28 clandmeter, thanks for xterm :) 2015-06-19 13:54:43 so if you do more pushes while it is building it will run again 2015-06-19 13:55:00 and it breaks out of the loop when there are no new git commits 2015-06-19 13:55:22 alacerda: yw 2015-06-19 13:55:49 ncopa: that's fine I guess 2015-06-19 13:55:53 it will also loop if the upload failed 2015-06-19 13:56:02 unless we introduce some magical keyword to commit message 2015-06-19 13:56:11 so no new commits are build unless it's found there 2015-06-19 13:56:19 yeah htat is what i am thinking of 2015-06-19 13:56:36 if it find 'retry' in the payload, then if makes a forced run 2015-06-19 13:56:37 or we shouldn't even accept new commits until CI is fixed 2015-06-19 13:56:52 but it's probably overkill 2015-06-19 13:57:15 how do you push the fix then? 2015-06-19 13:58:10 I think git can check commit message and reject it if some condition is not met? 2015-06-19 13:58:39 "main/something: fix build \n\n builders: force" 2015-06-19 13:58:42 or something 2015-06-19 13:59:18 my take on it is 2015-06-19 13:59:31 if something is broke, it will not help simply retry 2015-06-19 13:59:52 so what we really want is exact build log 2015-06-19 13:59:59 url to exact build log 2015-06-19 14:00:13 I'm going home, let's talk about it on monday 2015-06-19 14:00:16 ok 2015-06-19 14:00:22 see you 2015-06-19 14:00:28 have a nice weekend 2015-06-19 14:01:19 ncopa: before you go, can you check that build error i have? 2015-06-19 14:01:40 ok 2015-06-19 14:04:53 to.c:(.text+0x702): undefined reference to `inet_net_pton' 2015-06-19 14:04:53 to.c:(.text+0x759): undefined reference to `inet_net_pton' 2015-06-19 14:04:56 and 2015-06-19 14:05:16 lets take it in #alpine-devel 2015-06-19 14:27:49 ncopa: shouldn't dev.a.o logs for commits have algitbot msgs too ! 2015-06-19 14:30:56 vkris: http://dev.alpinelinux.org/irclogs/%23alpine-commits-2015-06.log 2015-06-19 14:48:01 I mean msgs from "algibot" 2015-06-23 07:35:11 ehm 2015-06-23 07:35:23 I don't think we want notifications from gitolite-admin 2015-06-23 07:35:27 ncopa: ↑ 2015-06-23 07:36:00 maybe not 2015-06-23 07:38:19 permissions of generated tarball is wrong too 2015-06-23 07:45:49 ay! 2015-06-23 07:46:16 oy! 2015-06-23 07:46:22 ey! 2015-06-23 07:47:42 algitbot: please dont try to be human... 2015-06-23 07:56:29 nice! 2015-06-23 07:56:48 in my git push console i see: 2015-06-23 07:56:55 remote: /archive/test/test-1.6.tar.xz created 2015-06-23 07:56:55 remote: http://dev.alpinelinux.org/archive/test/test-1.6.tar.xz 2015-06-23 08:07:14 ok, i think git messages are ok now 2015-06-23 08:07:32 i should deal with build server messages and build error messages 2015-06-23 08:07:49 but i think i need a permanent logfile location 2015-06-23 08:08:01 a central build log server 2015-06-23 10:43:15 why not all bots/andq 2015-06-23 10:43:41 in this channel 2015-06-23 10:44:08 define all 2015-06-23 10:44:14 we have both commit and build messages here 2015-06-23 10:44:29 that way we can watch it on one screen , eat popcorn and chat on -devel 2015-06-23 10:44:41 this is exactly what we do now 2015-06-23 10:44:42 I mean chat about it 2015-06-23 10:44:44 well, at least I do 2015-06-23 10:45:39 I mean a separate dedicated AL bot channel 2015-06-23 10:46:14 and enhanced algitbot 2015-06-23 10:47:04 if we want specific msg copied/diverted to -devel 2015-06-23 12:07:28 ncopa: im sure ppl are not fond of colors, but something to distinguish repo's msg would be nice. 2015-06-23 12:11:03 I don't mind it either 2015-06-23 12:11:12 colored messages by bots makes sense 2015-06-23 12:13:33 :1 2015-06-23 12:13:34 it would make the last to commits a bit easier to distinguish 2015-06-23 12:13:35 +1 2015-06-23 12:13:42 two even 2015-06-23 12:14:01 clandmeter: how do i do that 2015-06-23 12:14:23 you want the repo to be highlighted? 2015-06-23 12:18:25 abuild:master could be in another color (or the rest to limit colors) 2015-06-23 12:19:07 not sure if all repos including tags should have another color? 2015-06-23 12:19:54 test tags 2015-06-23 12:20:46 that bot is so intelligent 2015-06-23 12:21:57 I use multitail and clog 2015-06-23 12:24:11 is bold enough? 2015-06-23 12:24:27 or should I set a hard color? 2015-06-23 12:25:05 you make only aports bold? 2015-06-23 12:25:30 colors are \x0307nice\x03 2015-06-23 12:25:36 bah 2015-06-23 12:25:38 :) 2015-06-23 12:25:44 well, I don't really care about commit author, so it could be more gray or something 2015-06-23 12:26:15 colors are ^C03nice^C 2015-06-23 12:26:55 https://github.com/myano/jenni/wiki/IRC-String-Formatting 2015-06-23 12:27:05 seem like \x02 is bold 2015-06-23 12:27:56 test 2015-06-23 12:28:09 bold 2015-06-23 12:28:27 maybe colors are disabled in this channel? 2015-06-23 12:28:39 they are not, see my messages 2015-06-23 12:29:09 thats why i ask. you messages has no formatting :) 2015-06-23 12:29:20 oh well 2015-06-23 12:29:21 i suppose it my client that strips the colors 2015-06-23 12:29:25 looks like something with your client then 2015-06-23 12:29:33 ACTION doesn't see any colors with XChat 2015-06-23 12:31:08 no, not here 2015-06-23 12:31:13 neither 2015-06-23 12:31:20 hexchat 2015-06-23 12:31:22 red 2015-06-23 12:31:35 hexchat as well 2015-06-23 12:33:33 nope 2015-06-23 12:33:44 i dont know how to do it then 2015-06-23 12:34:41 ^14Colored Text^ — Grey colored text. 2015-06-23 12:36:03 \x03,04Test 2015-06-23 12:36:05 \x03test 2015-06-23 12:36:08 not really 2015-06-23 12:36:15 I guess my client escapes that 2015-06-23 12:36:21 %Ctest%O 2015-06-23 12:37:08 blabla \x035,12to be colored text and background\x03 blabla 2015-06-23 12:37:12 :) 2015-06-23 12:37:16 lol 2015-06-23 12:37:22 tes 2015-06-23 12:37:55 ^K8,4Goooo 2015-06-23 12:37:58 i feel like i am with a bunch of 3yrs kids who found color pencils :) 2015-06-23 12:38:01 :) 2015-06-23 12:38:07 hauiehaeuiea 2015-06-23 12:39:09 cmon algitbot, color our lives. 2015-06-23 12:39:15 ^C5,12Why not?^C 2015-06-23 12:40:44 '\x03what?' 2015-06-23 12:40:46 '\x03,what?' 2015-06-23 12:40:50 '\x03' 2015-06-23 12:41:39 \u000304A red message 2015-06-23 12:42:45 https://www.npmjs.com/package/irc-colors related ? 2015-06-23 12:43:29 no 2015-06-23 12:43:52 ncopa: broken pencils 2015-06-23 12:44:03 algitbot what is yout problem? 2015-06-23 12:44:26 '\x03'Won't you help us? 2015-06-23 12:45:00 ha 2015-06-23 12:45:06 ncopa, http://docs.dal.net/docs/modes.html#2.3 ? 2015-06-23 12:45:14 Hello 2015-06-23 12:45:15 at least it parses \x00 properly :) 2015-06-23 12:45:43 so mode -c ? 2015-06-23 12:46:23 ah that possible 2015-06-23 12:46:43 multitail view of this channel, http://i.imgur.com/KB1VE0l.png 2015-06-23 12:47:06 now how to set channel modes 2015-06-23 12:47:12 /mode -c ? 2015-06-23 12:47:24 i gues need to specificy channel 2015-06-23 12:47:34 i think only clandmeter can do that 2015-06-23 12:47:44 Channel #alpine-commits modes: +cnt 2015-06-23 12:47:47 :) 2015-06-23 12:47:59 ncopa, we need -c 2015-06-23 12:48:11 :D 2015-06-23 12:48:20 haha 2015-06-23 12:48:23 '\x03'color??? 2015-06-23 12:48:25 hehe 2015-06-23 12:48:32 freaking chanserv 2015-06-23 12:48:42 isnt +c color filter 2015-06-23 12:48:51 \x035,12restarting the color war 2015-06-23 12:48:58 yes but chanserv set it back 2015-06-23 12:49:01 need to set it global 2015-06-23 12:49:04 set it with chanserv 2015-06-23 12:49:06 The +c mode stands for colourless. 2015-06-23 12:49:10 :) 2015-06-23 12:49:11 oh 2015-06-23 12:49:32 + means less ?! 2015-06-23 12:49:34 weird! 2015-06-23 12:49:42 c 2015-06-23 12:49:42 (color filter) This mode activates the colour filter for the channel. This filters out bold, underline, reverse video, beeps, mIRC colour codes, and ANSI escapes. Note that escape sequences will sometimes leave cruft sent to the channel, just without the escape characters themselves. 2015-06-23 12:50:02 http://docs.dal.net/docs/modes.html#2.3 2015-06-23 12:50:04 :| 2015-06-23 12:50:11 hehe 2015-06-23 12:50:33 no 2015-06-23 12:50:35 \o/ 2015-06-23 12:50:35 ;-) 2015-06-23 12:51:04 so commit repo bold? 2015-06-23 12:51:22 red ? 2015-06-23 12:51:56 congrats, we have finally a bikeshedding! 2015-06-23 12:52:42 :) 2015-06-23 12:52:52 ncopa: what good would only repo bold do? 2015-06-23 12:53:51 make the commits stand out? 2015-06-23 12:54:57 yay 2015-06-23 12:55:00 like that? 2015-06-23 12:55:02 :) 2015-06-23 12:55:23 i was refering to this 2015-06-23 12:55:24 13:21 < algitbot> abuild:master (Natanael Copa) abuild: fix circular dependency for symlink deps | http://dup.pw/abuild/3f3281c8 2015-06-23 12:55:27 13:23 < algitbot> aports:master (Natanael Copa) main/abuild: fix circular dep problem for symlink deps | http://dup.pw/aports/7ab85b7a 2015-06-23 12:55:44 you want the entire line colored? 2015-06-23 12:55:45 i had to look twice to get it :) 2015-06-23 12:56:05 ncopa, give us a red sample 2015-06-23 12:56:48 no workey here 2015-06-23 12:56:53 whee 2015-06-23 12:57:03 imho colorize the entire line isn't a good idea 2015-06-23 12:57:10 thats what i thought too 2015-06-23 12:57:21 different color per repository? 2015-06-23 12:57:31 yes diff per repo 2015-06-23 12:57:39 or diff per repo and diff per user 2015-06-23 12:57:46 or user all have same color 2015-06-23 12:57:53 problem with color is that it might make it unreadable, depending on you colorscheme 2015-06-23 12:58:12 aslong its not white or black, it should be ok? 2015-06-23 12:58:25 if you have a black backtround it might be difficult to read blue 2015-06-23 12:58:28 if you have a pink background, you already have an issue. 2015-06-23 12:58:33 :D 2015-06-23 12:59:06 do all repo's report here? 2015-06-23 12:59:10 yes 2015-06-23 12:59:25 so let's hardcode it for official ones 2015-06-23 12:59:35 we want apk-tools, abuild and aports for start 2015-06-23 12:59:53 red, green, yellow and we're good to go 2015-06-23 13:00:10 that is why only small part of the line should be done, but should be bold/standout 2015-06-23 13:00:23 repo = red and aports = bold 2015-06-23 13:00:33 red+bold 2015-06-23 13:00:41 only bold != master 2015-06-23 13:01:08 what is it we want highlight, its the repo right? 2015-06-23 13:01:12 kkkk ncopa is going crazy 2015-06-23 13:01:22 i need coffe 2015-06-23 13:01:41 good idea... this is what i am going to do 2015-06-23 13:02:09 2015-06-23 13:02:19 neat but different color 2015-06-23 13:02:20 do we want specific repo to stand out? 2015-06-23 13:02:26 eg aports? 2015-06-23 13:02:31 as for 2015-06-23 13:02:49 ncopa: like barthalion said 2015-06-23 13:02:54 have those 3 colors maybe? 2015-06-23 13:02:58 or any color you like 2015-06-23 13:03:09 and let's make the rest grey 2015-06-23 13:03:16 uncolored 2015-06-23 13:03:30 sure 2015-06-23 13:03:35 just throwing my thoughts 2015-06-23 13:03:38 i wonder if it would be enough to only make 'aports' bold 2015-06-23 13:03:41 and nothing else 2015-06-23 13:03:49 i prefer color or bold 2015-06-23 13:04:03 it will stand out from the rest 2015-06-23 13:06:23 maybe a slight diff color for the rest? grey? 2015-06-23 13:06:56 ncopa: and green for build upload and red for build failure :) 2015-06-23 13:07:34 and blinking when we mention ncopa 2015-06-23 13:08:40 it blinks here when you mention ncopa already 2015-06-23 13:08:48 but green for uplaod and red for error sounds good 2015-06-23 13:25:57 2015-06-23 13:27:09 algitbot, am I sending files ^^ ? 2015-06-23 13:27:10 :P 2015-06-23 13:27:13 no 2015-06-23 13:27:16 hehe 2015-06-23 13:27:24 i am injecting testcommits 2015-06-23 13:27:46 any decision ? 2015-06-23 13:27:57 bold, red, yellow, pink ? 2015-06-23 13:28:22 I like clandmeter's idea: "and blinking when we mention ncopa" 2015-06-23 13:28:23 :) 2015-06-23 13:28:47 i actualy think you can configure your irc client for those things 2015-06-23 13:29:32 currently the goal is: bold for 'aports' commits and normal for everythign else 2015-06-23 13:29:49 successful upload green 2015-06-23 13:29:54 and build errors red 2015-06-23 13:31:33 if commit by user, then color () 2015-06-23 13:32:51 or maybe user commit should be grey line except the "()" 2015-06-23 13:32:54 grey is possible ? 2015-06-23 13:33:11 everything is possible 2015-06-23 13:33:17 the impossible just tames more time... 2015-06-23 13:33:21 takes* 2015-06-23 13:33:22 i think grey is uncolored, isn't it? 2015-06-23 13:33:41 depends on your color settings in your client i suppose 2015-06-23 13:42:24 ok 2015-06-23 13:43:10 im seeing an I with white bg infront of new file. 2015-06-23 13:44:24 are aports messages ok? 2015-06-23 13:45:41 ... |Natanael Copa| ... would be better 2015-06-23 13:46:18 thats trivial to fix 2015-06-23 13:46:23 so thats fixed now 2015-06-23 13:47:55 super! 2015-06-23 13:49:32 maybe even [Natanael Copa] 2015-06-23 13:54:26 wow 2015-06-23 13:55:41 remote: fatal: could not create archive file '/archive/setup-box/setup-box-1.0_rc5.tar': Permission denied 2015-06-23 14:31:02 do we get double msg all the time? 2015-06-23 14:36:41 clandmeter, the first is push second one is push --tags 2015-06-23 14:37:02 hun ?! 2015-06-23 14:37:10 dont mention tags 2015-06-23 14:37:17 kkkkk 2015-06-23 14:37:26 what happens if I say: tags ? 2015-06-23 14:37:48 alacerda: but should our tags bot mention it? 2015-06-23 14:38:43 what is the purpose of this behaviour when we mention tags ? 2015-06-23 14:41:44 I don't this out t a g s should be prompted here... donno if its trivial to fix 2015-06-23 14:42:08 s/I don't this out/ I don't think our/ 2015-06-23 14:42:41 what about donno? 2015-06-23 14:42:56 ¬¬" 2015-06-23 14:45:06 :) 2015-06-23 14:45:58 donna in italian is "female" 2015-06-23 14:46:03 maybe donno is "male" 2015-06-23 14:46:05 :) 2015-06-23 14:47:06 kkkk ok, ok s/donno/do not know/ 2015-06-23 14:47:07 :P 2015-06-23 14:47:19 its probably portugese :p 2015-06-23 14:47:51 i thinght donno in portugues was "owner" 2015-06-23 14:47:57 but thats maybe dono 2015-06-23 14:48:53 oh interesting 2015-06-23 14:48:56 i dont even know how to spell Portuguese :) 2015-06-23 14:49:06 commits are in reverse order 2015-06-23 14:56:14 is the source for algitbot available? 2015-06-23 15:00:19 its called sircbot 2015-06-24 13:29:20 clandmeter, it seems that duplication is not due to push --t a g s 2015-06-24 13:29:54 as I suggested yesterday 2015-06-25 13:16:38 ncopa, linux-grsec failed: 2015-06-25 13:16:38 make[1]: Leaving directory '/home/buildozer/aports/main/linux-grsec/src/build-virtgrsec' 2015-06-25 13:16:38 make: Leaving directory '/home/buildozer/aports/main/linux-grsec/src/linux-3.18' 2015-06-25 13:16:38 /home/buildozer/aports/main/linux-grsec/src/linux-3.18/Makefile:683: *** Your gcc installation does not support plugins. If the necessary headers for plugin support are missing, they should be installed. On Debian, apt-get install gcc--plugin-dev. If you choose to ignore this error and lessen the improvements provided by this patch, re-run make with the DISABLE_PAX_PLUGINS=y argument.. Stop. 2015-06-25 13:16:40 Makefile:145: recipe for target 'sub-make' failed 2015-06-25 13:17:18 maybe gcc5.1 renamed some files and they got lost? 2015-06-25 13:17:38 is this the first kernel compilewith gcc-5.1? 2015-06-25 13:18:06 huh 2015-06-25 13:18:33 $ gcc --version 2015-06-25 13:18:33 gcc (Alpine 5.1.0) 5.1.0 2015-06-25 13:18:58 i built it on my dev box 2015-06-25 13:19:24 yes, i think its the first gcc5 built kernel 2015-06-25 13:19:35 hmm 2015-06-25 13:20:24 could it be that some c++ prog needs to be rebuilt? 2015-06-25 13:21:19 mm 2015-06-25 13:21:23 yes 2015-06-25 13:21:26 gcc is c++ now 2015-06-25 13:21:29 or some buildtime dep is missing? 2015-06-25 13:21:31 g++ isprobably needed 2015-06-25 13:21:55 is g++ in build-base? 2015-06-25 13:22:01 should be 2015-06-25 13:22:15 weird, it does build on my dev box 2015-06-25 13:22:55 libgmpxx? 2015-06-25 13:23:32 maybe 2015-06-25 13:23:51 it was rebuilt 2015-06-25 13:23:54 commit 01f5888e5db5d540717ae440b883e0939d8d3df3 2015-06-25 13:23:54 Author: Natanael Copa 2015-06-25 13:23:54 Date: Mon Jun 22 08:48:11 2015 +0000 2015-06-25 13:23:54 main/gmp: rebuild with gcc5 libstdc++ ABI change 2015-06-25 15:03:56 really really weird that build servers does not build kernels 2015-06-25 15:04:10 i have no idea what is going on 2015-06-25 15:04:17 i cannot reproduce it on my dev box 2015-06-25 15:06:25 i will have to investigate that tomorrow 2015-06-26 07:11:18 ncopa, ^^^ so linux-grsec-dev needs to depend on those headers too? 2015-06-26 07:13:48 seems like unrelated 2015-06-26 07:13:58 /home/buildozer/aports/main/open-vm-tools-grsec/src/open-vm-tools-9.10.0-2476743/lib/include/vm_basic_asm_x86.h:439:19: fatal error: mul64.h: No such file or directory 2015-06-26 07:13:58 compilation terminated. 2015-06-26 07:15:00 http://sourceforge.net/p/open-vm-tools/mailman/message/34016246/ 2015-06-26 07:16:35 oh 2015-06-26 07:17:51 sigh: I think simplest workaround for you at this point is to use a GCC version >= 4.4 and < 5.0. 2015-06-26 07:18:07 yeah i saw 2015-06-26 07:18:12 i'll look at it soonish 2015-06-27 18:37:50 ACTION crosses his fingers 2015-06-27 18:45:09 yay 2015-06-27 18:49:38 ncopa: looking at build.al.o, armhf builder went postal 2015-06-27 18:49:50 shows completely unrelated packages 2015-06-27 18:49:54 and suddenly finished 2015-06-29 08:37:44 leo-unglaub: hi 2015-06-29 08:37:56 there you go^^^ 2015-06-29 08:38:05 hey, cool :) 2015-06-29 08:44:10 so this channel here is just for commit/bot logs? 2015-06-29 08:44:18 yep 2015-06-29 08:44:20 or do you discuss commits as well? 2015-06-29 08:44:35 very rarely 2015-06-29 08:44:55 its kind of new, and we dont have any rules set. 2015-06-29 08:46:07 and i would prefer not introduce any rules, unless necessary 2015-06-29 08:46:28 the idea with this channel was to remove the bot spam from #alpine-devel 2015-06-29 11:48:58 leo-unglaub: there comes the pidgin stuff^^^ 2015-06-29 11:49:58 great 2015-06-29 11:50:07 that should make the executable a lot smaller 2015-06-29 11:50:08 :) 2015-06-29 11:50:18 and get rid of gstreamer 0.10 entirely :) 2015-06-29 11:50:19 and fewer deps 2015-06-29 15:23:08 ncopa: blind push? 2015-06-29 15:43:14 hmm, gst-libav1 build fine for me 2015-06-29 15:46:12 hadn't bumped. duh! 2015-06-29 17:10:56 fwiw gst-libav1 bumped builds for me