IRC logs for #baserock for Wednesday, 2016-07-20

*** persia has quit IRC04:05
*** persia has joined #baserock04:08
*** paulwaters_ has joined #baserock06:02
*** paulwaters_ has joined #baserock07:01
*** fay has joined #baserock07:14
*** fay is now known as Guest4747807:14
*** toscalix has joined #baserock07:44
*** rdale has joined #baserock07:58
*** jonathanmaw has joined #baserock08:32
pedroalvarezanyone knows which apps from gnome use webkitgtk? so that I can test it?08:44
pedroalvarezall seems to work fine08:45
pedroalvarez`ldd foo | grep webkit`  is  helping08:48
pedroalvarezgnome-help08:53
pedroalvarezeven epiphany08:53
pedroalvarezall seems to work08:55
*** gtristan has joined #baserock09:00
pedroalvarezNew Changes:09:01
pedroalvarez  https://gerrit.baserock.org/2224 icu-common: Upgrade ICU to 52.109:01
pedroalvarez  https://gerrit.baserock.org/2225 gnome: Upgrade WebKitGtk to 2.12.309:01
pedroalvarezpaulsherwood, gtristan, jjardon ^09:02
jjardonpedroalvarez: if epiphany works everything should work09:03
pedroalvarezthe only thing that failed, was watchin a youtube video09:03
jjardonpedroalvarez: that can be gstreamer, probably the gst-vaapi plugins09:04
jjardonpedroalvarez: merged, thanks!09:05
pedroalvarezyehe!09:05
pedroalvarezthanks jjardon!09:05
pedroalvareznever expected that glibc could break webkit :/09:05
gtristanif it compiles, ship it !09:16
gtristannice to get rid of stale and old chunk morph committed into delta of icu09:17
pedroalvarezyup09:17
*** locallycompact has joined #baserock09:31
jjardonpedroalvarez: thanks for the review for webkitgtk1 lorry, patch updated10:14
*** Guest47478 is now known as faybrocklebank10:15
pedroalvarezjjardon: added some comments. Happy to continue the discussion here if needed10:18
pedroalvarezalso, if anyone else thinks that creating a different repo for earlier versions of webkitgtk  makes sense, I'm happy to approve10:21
pedroalvarezbut from my point of view,  early releases of a component, even if it's not API compatible, should go to the same repo..10:21
pedroalvarezwhich is  what would happen if we wouldn't be lorring from tarballs10:22
persiaSame repo is best.  If there are multiple supported tarball series, then branches are the right solution.10:27
pedroalvarezevery tarball would be a tag10:28
pedroalvarezthis is how it looks: http://git.baserock.org/cgit/delta/WebKitGtk-tarball.git/10:29
*** franred has joined #baserock10:46
*** faybrocklebank has quit IRC11:06
persiapedroalvarez: I was thinking branches for projects that did things like 2.4.0, 2.4.1, 2.4.2, 2.5.0, 2.4.3, 2.5.1, 2.4.4, 2.5.2, 2.4.5, 2.6.0, 2.5.3, 2.6.1, ...11:16
persia(as tarball releases, chronologically listed, by version number)11:17
pedroalvarezah, yes11:17
pedroalvarezI was just thinking about this concrete patch: https://gerrit.baserock.org/#/c/2222/211:17
persiaFor the concrete patch, I think same repo is correct: I was only considering the general case.  For that matter, if there is a working SVN, I think we should just lorry the SVN, rather than tarballs.11:19
*** fay has joined #baserock12:14
*** fay is now known as faybrocklebank12:14
*** franred has quit IRC12:49
*** franred has joined #baserock13:04
*** franred has joined #baserock13:04
*** jonathanmaw has quit IRC13:47
*** jonathanmaw has joined #baserock13:48
*** lachlanmackenzie has quit IRC15:22
*** lachlanmackenzie has joined #baserock15:22
*** jonathanmaw has quit IRC15:39
*** gtristan has quit IRC16:18
*** robtaylor has quit IRC16:21
*** locallycompact has quit IRC17:32
*** anahuelamo has quit IRC17:34
*** toscalix has quit IRC17:58
*** gtristan has joined #baserock20:22
jjardonI do not mind sane repo, but it's going to look weird when I upgrade it to put an older version20:25
*** gtristan has quit IRC21:56
pedroalvarezjjardon: yeah, feels weird, but we have done that in the past, and I think it's fine.22:02
pedroalvarezmaybe, tarball lorries should support various versions?22:03

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!