IRC logs for #baserock for Thursday, 2017-02-09

*** locallycompact has joined #baserock00:04
*** locallycompact has quit IRC00:25
*** rdale has quit IRC01:48
*** gtristan has joined #baserock06:43
*** jude_ has joined #baserock08:13
*** paulwaters_ has joined #baserock08:31
jjardonCan someone review please?08:36
*** ctbruce has joined #baserock08:37
*** fay has joined #baserock08:39
*** fay is now known as Guest2388508:39
*** rdale has joined #baserock08:55
*** jonathanmaw has joined #baserock09:14
*** toscalix has joined #baserock09:20
*** franred has joined #baserock09:43
pedroalvarez_CI is somehow broken:
*** cornel has joined #baserock10:00
*** ssam2 has joined #baserock10:00
*** ChanServ sets mode: +v ssam210:00
pedroalvarez_the previous attempt of that build failed in a weird way. Maybe this is a case of the runners being a bit broken?10:07
pedroalvarez_or full? or something?10:07
paulsherwoodwell it seems repeatable10:09
*** franred is now known as noisecell10:10
*** CTtpollard has joined #baserock10:11
*** leeming has quit IRC10:14
*** noisecell is now known as franred10:17
*** franred is now known as noisecell10:18
*** noisecell has quit IRC10:20
*** noisecell has joined #baserock10:22
*** leeming has joined #baserock10:29
jjardonthat's a new one :)10:39
*** locallycompact has joined #baserock10:40
jjardonpedroalvarez_: does this only happen in your branch?10:42
pedroalvarez_that only happened when retrying one build in my branch10:43
pedroalvarez_I will retry something in another branch10:43
jjardonanahuelamo: can you review as well ?10:43
anahuelamojjardon, done10:44
* pedroalvarez_ retries:
*** pedroalvarez_ is now known as pedroalvarez10:44
jjardoncool, fresh rootfs from master to everyone!10:45
pedroalvarezjjardon: same error in that one, which is not my branch10:46
jjardonmmm, no changes in ybd in the last 2 days so its not that10:50
toscalixyou can read the communication I just sent in the public GENIVI mailing list10:53
toscalixabout BAserock Baselines10:53
toscalixah, pedroalvarez is faster10:54
jjardonok, I think something have changed in some of the ybd python packages dependencies:
jjardonpedroalvarez: ^11:10
jjardonweird, taking in account we depend on specific versions now11:10
pedroalvarezi looked at rienman and protobuf and they were the same yesterday and today11:10
pedroalvarezthe previous attempt of one of my builds failed in a weird way and works locally. Maybe this is a case of the runners being a bit broken?11:11
jjardonhow come? they are pristine debian machines in every build11:15
jjardonI think protobuf actually changed: from protobuf-3.2.0-py2.py3-none-any.whl to protobuf-3.2.0-cp27-cp27mu-manylinux1_x86_64.whl11:16
pedroalvarezjjardon: hmm.. both of them part of the same version:
jjardonpedroalvarez: protobuf-3.2.0-py2.py3-none-any.whl was released on 2017-01-30 , but protobuf-3.2.0-cp27-cp27mu-manylinux1_x86_64.whl was released on  2017-02-08 (yesterday)11:23
pedroalvarezgah, i'm definitely blind11:24
pedroalvarezthis looks wrong to me. So even i force a version number, things can break11:27
pedroalvarezs/even i/even if we/11:31
jjardonseems so :/ I think next step is to specify the version of every single python package, not only the direct deprendencies11:31
noisecellare you using pip or apt for installing package?11:32
pedroalvarezthis one is being installed by pip11:33
* noisecell is not fan of pip11:33
noisecellor better, Im not fan of 2 package managers dealing with my packages11:34
noisecellcan you not avoid using pip and use just apt?11:34
pedroalvarezjjardon: thing is, that even in that case, things can break.11:34
* locallycompact finds it incredibly annoying for distributions to install packages that my language package manager can handle11:35
pedroalvarezyou could have specified protobuf 3.2.0  two days ago, and had that working. And yesterday... bang!11:35
jjardonall is installed with pip11:35
noisecellyou can define in the source list which debian releases you want your packages from11:36
noisecell(using apt)11:36
noisecelljjardon, any reason why?11:36
jjardondebian packages are too old11:36
locallycompactI don't want anything from a debian release, I like stable code11:37
noisecelllocallycompact, you can have testing if you fancy11:37
locallycompactI'm good thanks11:37
noisecelljjardon, then why not use something different than debian as you base distribution?11:37
pedroalvarezpip is easier if you want to support multiple OSs11:37
noisecelllocallycompact, debian release are very stable. But depending on your base release your packages can be old as jjardon said11:39
noisecellyou can list your_release-backports to get patches for these packages or use testing (which is not going to be stable)11:40
locallycompactI disagree, they are unstable because they are old11:40
pedroalvarezjjardon: the only quick solution I see here is to force protobuf 3.0.011:40
noisecelllocallycompact, they are stable because they are working in the same way, so their behaviour is expected11:41
locallycompactthe wrong behaviour11:41
noisecellbut stable ;-)11:41
locallycompactFSVO stable11:41
jjardonpedroalvarez: lets try that11:42
locallycompactimo how arch does it, rolling releases, stablizes the world more effectively11:42
locallycompactwhat debian stable does is not stability, because it can not adapt to microproblems11:43
locallycompactlike how a lift stabilizes11:44
locallycompactif a lift is 45 degrees on its side, maybe it's "stable", maybe it would stay there, but when are you going to put the lift back up straight please11:45
noisecellbackports do that for you, normally11:45
jjardonlocallycompact: +111:46
* noisecell is not a debian user anyway. I just worked with it and I didn't see a lot of problems.11:46
pedroalvarezyou should all use baserock11:47
noisecellfor what I did want to do11:47
jjardonnoisecell: backports done by who? with all the respect Id trust more the author of the package than a debian dev trying to backport stuff11:47
noisecellpedroalvarez, updates in a real system11:47
jjardonpedroalvarez: :)11:47
noisecellpedroalvarez, but :)11:47
noisecelljjardon, I agree with that view. But using the latest version of everything do not give you stability because all the packages maintainers do not test every package that use their package ;-), so you can end up waiting in multiple packages to cope with fixes from multiple packages11:50
noisecellas you can see today with protobuf11:50
ssam2the only issue with the rolling release model is that upstream aren't always making their software better, sometimes new releases are worse than the older ones :-)11:50
ssam2but it seems the best compromise to me11:50
locallycompactrolling has immediate feedback for anybody depending on it, my shit has suddenly broken because of an update to something that happened yesterday is easier analysed and fixed than why don't this work with "packages from 2009"11:52
pedroalvarezjjardon: that branch works11:52
jjardonpedroalvarez: cool, mind a review?11:52
pedroalvarezjjardon: i see no MR11:53
jjardonooop, sorry one sec11:55
tiagogomesI look forward to a package-less operating system with well-tested OS atomic updates for stability, and flatpack apps for having the latest and greatest stuff.11:57
jjardonpedroalvarez: paulsherwood
jjardonthat can be done with baserock with some effort11:58
paulsherwoodtiagogomes: does 'look forward' include 'would be happy to contribute to' ?12:26
paulsherwoodjjardon: approved12:27
*** lc__ has joined #baserock14:35
*** locallycompact has quit IRC14:37
*** gtristan has quit IRC14:39
*** gtristan has joined #baserock15:09
pedroalvarezjjardon: ready to merge now15:15
pedroalvarezmaybe paulsherwood around:
paulsherwoodthanks to you :)15:38
* pedroalvarez re-triggers a definitions build15:40
tiagogomespaulsherwood if only my employer allowed me time to contribute :)15:41
*** toscalix has quit IRC15:41
*** toscalix has joined #baserock15:42
*** noisecell has quit IRC16:27
*** noisecell has joined #baserock16:38
*** jude_ has quit IRC16:41
pedroalvarezjjardon: wow, those patches have been there for 2 months16:45
pedroalvarezno reviews :/16:45
jjardonyeah :(16:48
pedroalvarezmaybe 2 approvals is a bit to much/16:49
pedroalvarez(after being some time merging things with only one?)16:50
paulsherwoodwhich patches?17:00
*** noisecell has quit IRC17:03
pedroalvarezthat's the one that has been there for 2 months17:07
pedroalvarezthis one is a bit more recent:
*** jude_ has joined #baserock17:18
*** Guest23885 has quit IRC17:18
*** ctbruce has quit IRC17:20
*** jude_ has quit IRC17:28
paulsherwoodshall we close ?17:34
pedroalvarezhm.. why?17:35
pedroalvarezit includes more things17:35
* pedroalvarez waits for "rebase in progress..." in
*** jude_ has joined #baserock17:36
*** jonathanmaw has quit IRC17:36
pedroalvarez12 minutes already17:39
* pedroalvarez had to rebase manually:
pedroalvarezre-rebased by jjardon :)17:53
pedroalvarezhopefully tomorrow we can merge these things18:03
*** ssam2 has quit IRC18:09
*** toscalix has quit IRC18:16
*** lc__ has quit IRC18:31
*** ctbruce has joined #baserock18:33
*** tiagogomes has quit IRC18:42
jjardonyes, unfortunatelly a change in glibc needs to rebuild the word18:55
*** jude_ has quit IRC19:25
*** lc__ has joined #baserock19:28
*** rdale has quit IRC19:46
*** lc__ has quit IRC20:08
*** gtristan has quit IRC21:30
*** gtristan has joined #baserock22:13
*** ctbruce has quit IRC22:45
*** gtristan has quit IRC23:26

Generated by 2.15.3 by Marius Gedminas - find it at!