*** locallycompact has joined #baserock | 00:04 | |
*** locallycompact has quit IRC | 00:25 | |
*** rdale has quit IRC | 01:48 | |
*** gtristan has joined #baserock | 06:43 | |
*** jude_ has joined #baserock | 08:13 | |
*** paulwaters_ has joined #baserock | 08:31 | |
jjardon | Can someone review https://gitlab.com/baserock/definitions/merge_requests/25 please? | 08:36 |
---|---|---|
paulsherwood | done | 08:37 |
*** ctbruce has joined #baserock | 08:37 | |
*** fay has joined #baserock | 08:39 | |
*** fay is now known as Guest23885 | 08:39 | |
*** rdale has joined #baserock | 08:55 | |
*** jonathanmaw has joined #baserock | 09:14 | |
*** toscalix has joined #baserock | 09:20 | |
*** franred has joined #baserock | 09:43 | |
pedroalvarez_ | CI is somehow broken: https://gitlab.com/baserock/definitions/builds/10170973#down-build-trace | 09:58 |
paulsherwood | eek | 09:59 |
*** cornel has joined #baserock | 10:00 | |
*** ssam2 has joined #baserock | 10:00 | |
*** ChanServ sets mode: +v ssam2 | 10: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 |
paulsherwood | well it seems repeatable | 10:09 |
*** franred is now known as noisecell | 10:10 | |
*** CTtpollard has joined #baserock | 10:11 | |
*** leeming has quit IRC | 10:14 | |
*** noisecell is now known as franred | 10:17 | |
*** franred is now known as noisecell | 10:18 | |
*** noisecell has quit IRC | 10:20 | |
*** noisecell has joined #baserock | 10:22 | |
*** leeming has joined #baserock | 10:29 | |
jjardon | that's a new one :) | 10:39 |
*** locallycompact has joined #baserock | 10:40 | |
jjardon | pedroalvarez_: does this only happen in your branch? | 10:42 |
pedroalvarez_ | that only happened when retrying one build in my branch | 10:43 |
pedroalvarez_ | I will retry something in another branch | 10:43 |
jjardon | anahuelamo: can you review https://gitlab.com/baserock/definitions/merge_requests/25 as well ? | 10:43 |
anahuelamo | jjardon, done | 10:44 |
* pedroalvarez_ retries: https://gitlab.com/baserock/definitions/builds/10173970 | 10:44 | |
*** pedroalvarez_ is now known as pedroalvarez | 10:44 | |
jjardon | cool, fresh rootfs from master to everyone! | 10:45 |
pedroalvarez | jjardon: same error in that one, which is not my branch | 10:46 |
jjardon | mmm, no changes in ybd in the last 2 days so its not that | 10:50 |
toscalix | you can read the communication I just sent in the public GENIVI mailing list | 10:53 |
toscalix | about BAserock Baselines | 10:53 |
jjardon | link? | 10:53 |
pedroalvarez | http://lists.genivi.org/pipermail/genivi-projects/2017-February/005244.html | 10:54 |
toscalix | ah, pedroalvarez is faster | 10:54 |
jjardon | ok, I think something have changed in some of the ybd python packages dependencies: https://gitlab.com/baserock/ybd/builds/10174519 | 11:09 |
jjardon | pedroalvarez: ^ | 11:10 |
jjardon | weird, taking in account we depend on specific versions now | 11:10 |
pedroalvarez | i looked at rienman and protobuf and they were the same yesterday and today | 11:10 |
pedroalvarez | the 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 |
jjardon | how come? they are pristine debian machines in every build | 11:15 |
jjardon | I think protobuf actually changed: from protobuf-3.2.0-py2.py3-none-any.whl to protobuf-3.2.0-cp27-cp27mu-manylinux1_x86_64.whl | 11:16 |
pedroalvarez | jjardon: hmm.. both of them part of the same version: https://pypi.python.org/pypi/protobuf/3.2.0 | 11:21 |
jjardon | pedroalvarez: 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 |
pedroalvarez | gah, i'm definitely blind | 11:24 |
pedroalvarez | this looks wrong to me. So even i force a version number, things can break | 11:27 |
pedroalvarez | s/even i/even if we/ | 11:31 |
jjardon | seems so :/ I think next step is to specify the version of every single python package, not only the direct deprendencies | 11:31 |
noisecell | are you using pip or apt for installing package? | 11:32 |
pedroalvarez | this one is being installed by pip | 11:33 |
* noisecell is not fan of pip | 11:33 | |
noisecell | or better, Im not fan of 2 package managers dealing with my packages | 11:34 |
noisecell | can you not avoid using pip and use just apt? | 11:34 |
pedroalvarez | jjardon: 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 handle | 11:35 | |
pedroalvarez | you could have specified protobuf 3.2.0 two days ago, and had that working. And yesterday... bang! | 11:35 |
jjardon | all is installed with pip | 11:35 |
noisecell | you can define in the source list which debian releases you want your packages from | 11:36 |
noisecell | (using apt) | 11:36 |
noisecell | jjardon, any reason why? | 11:36 |
jjardon | debian packages are too old | 11:36 |
locallycompact | I don't want anything from a debian release, I like stable code | 11:37 |
noisecell | locallycompact, you can have testing if you fancy | 11:37 |
locallycompact | I'm good thanks | 11:37 |
noisecell | jjardon, then why not use something different than debian as you base distribution? | 11:37 |
pedroalvarez | pip is easier if you want to support multiple OSs | 11:37 |
noisecell | locallycompact, debian release are very stable. But depending on your base release your packages can be old as jjardon said | 11:39 |
noisecell | you can list your_release-backports to get patches for these packages or use testing (which is not going to be stable) | 11:40 |
locallycompact | I disagree, they are unstable because they are old | 11:40 |
pedroalvarez | jjardon: the only quick solution I see here is to force protobuf 3.0.0 | 11:40 |
noisecell | locallycompact, they are stable because they are working in the same way, so their behaviour is expected | 11:41 |
locallycompact | the wrong behaviour | 11:41 |
noisecell | but stable ;-) | 11:41 |
locallycompact | FSVO stable | 11:41 |
locallycompact | :) | 11:41 |
jjardon | pedroalvarez: lets try that | 11:42 |
locallycompact | imo how arch does it, rolling releases, stablizes the world more effectively | 11:42 |
locallycompact | what debian stable does is not stability, because it can not adapt to microproblems | 11:43 |
locallycompact | like how a lift stabilizes | 11:44 |
locallycompact | if 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 please | 11:45 |
noisecell | backports do that for you, normally | 11:45 |
jjardon | locallycompact: +1 | 11:46 |
locallycompact | maybe | 11:46 |
* noisecell is not a debian user anyway. I just worked with it and I didn't see a lot of problems. | 11:46 | |
pedroalvarez | you should all use baserock | 11:47 |
noisecell | for what I did want to do | 11:47 |
jjardon | noisecell: backports done by who? with all the respect Id trust more the author of the package than a debian dev trying to backport stuff | 11:47 |
noisecell | pedroalvarez, updates in a real system | 11:47 |
jjardon | pedroalvarez: :) | 11:47 |
noisecell | pedroalvarez, but :) | 11:47 |
noisecell | jjardon, 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 packages | 11:50 |
noisecell | as you can see today with protobuf | 11:50 |
noisecell | ;-) | 11:50 |
ssam2 | the 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 |
ssam2 | but it seems the best compromise to me | 11:50 |
locallycompact | rolling 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 |
pedroalvarez | jjardon: that branch works | 11:52 |
jjardon | pedroalvarez: cool, mind a review? | 11:52 |
pedroalvarez | jjardon: i see no MR | 11:53 |
jjardon | ooop, sorry one sec | 11:55 |
tiagogomes | I 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 |
jjardon | pedroalvarez: paulsherwood https://gitlab.com/baserock/ybd/merge_requests/303 | 11:57 |
jjardon | that can be done with baserock with some effort | 11:58 |
paulsherwood | tiagogomes: does 'look forward' include 'would be happy to contribute to' ? | 12:26 |
paulsherwood | jjardon: approved | 12:27 |
*** lc__ has joined #baserock | 14:35 | |
*** locallycompact has quit IRC | 14:37 | |
*** gtristan has quit IRC | 14:39 | |
*** gtristan has joined #baserock | 15:09 | |
pedroalvarez | jjardon: ready to merge now | 15:15 |
pedroalvarez | maybe paulsherwood around: https://gitlab.com/baserock/ybd/merge_requests/303 | 15:27 |
paulsherwood | merging | 15:31 |
pedroalvarez | thanks! | 15:37 |
paulsherwood | thanks to you :) | 15:38 |
* pedroalvarez re-triggers a definitions build | 15:40 | |
tiagogomes | paulsherwood if only my employer allowed me time to contribute :) | 15:41 |
paulsherwood | hah | 15:41 |
*** toscalix has quit IRC | 15:41 | |
*** toscalix has joined #baserock | 15:42 | |
*** noisecell has quit IRC | 16:27 | |
*** noisecell has joined #baserock | 16:38 | |
*** jude_ has quit IRC | 16:41 | |
pedroalvarez | jjardon: wow, those patches have been there for 2 months | 16:45 |
pedroalvarez | no reviews :/ | 16:45 |
jjardon | yeah :( | 16:48 |
pedroalvarez | maybe 2 approvals is a bit to much/ | 16:49 |
pedroalvarez | ? | 16:49 |
pedroalvarez | (after being some time merging things with only one?) | 16:50 |
paulsherwood | which patches? | 17:00 |
*** noisecell has quit IRC | 17:03 | |
pedroalvarez | https://gitlab.com/baserock/definitions/merge_requests/7 | 17:07 |
pedroalvarez | that's the one that has been there for 2 months | 17:07 |
pedroalvarez | this one is a bit more recent: https://gitlab.com/baserock/definitions/merge_requests/26 | 17:08 |
*** jude_ has joined #baserock | 17:18 | |
*** Guest23885 has quit IRC | 17:18 | |
*** ctbruce has quit IRC | 17:20 | |
paulsherwood | approved | 17:20 |
*** jude_ has quit IRC | 17:28 | |
paulsherwood | shall we close https://gitlab.com/baserock/definitions/merge_requests/30 ? | 17:34 |
pedroalvarez | hm.. why? | 17:35 |
pedroalvarez | it includes more things | 17:35 |
* pedroalvarez waits for "rebase in progress..." in https://gitlab.com/baserock/definitions/merge_requests/7 | 17:36 | |
*** jude_ has joined #baserock | 17:36 | |
*** jonathanmaw has quit IRC | 17:36 | |
pedroalvarez | 12 minutes already | 17:39 |
paulsherwood | ugh | 17:40 |
* pedroalvarez had to rebase manually: https://gitlab.com/baserock/definitions/merge_requests/7 | 17:49 | |
pedroalvarez | re-rebased by jjardon :) | 17:53 |
paulsherwood | approved | 17:53 |
pedroalvarez | hopefully tomorrow we can merge these things | 18:03 |
*** ssam2 has quit IRC | 18:09 | |
*** toscalix has quit IRC | 18:16 | |
*** lc__ has quit IRC | 18:31 | |
*** ctbruce has joined #baserock | 18:33 | |
*** tiagogomes has quit IRC | 18:42 | |
jjardon | yes, unfortunatelly a change in glibc needs to rebuild the word | 18:55 |
*** jude_ has quit IRC | 19:25 | |
*** lc__ has joined #baserock | 19:28 | |
*** rdale has quit IRC | 19:46 | |
*** lc__ has quit IRC | 20:08 | |
*** gtristan has quit IRC | 21:30 | |
*** gtristan has joined #baserock | 22:13 | |
*** ctbruce has quit IRC | 22:45 | |
*** gtristan has quit IRC | 23:26 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!