**** BEGIN LOGGING AT Tue Apr 02 02:59:57 2019 Apr 02 17:12:23 khem: Fetched in submodule path 'sources/meta-96boards', but it did not contain 8d5680b425b63eaf58365871f970ad15e3c95860. Direct fetching of that commit failed. Apr 02 17:13:28 I'm trying yoe and tripped over that. Checkout a different branch like mut or ?? Apr 02 17:15:23 yeah, yoe/mut makes it passed the meta-96boards checkout Apr 02 17:18:47 *past Apr 02 19:20:30 hopefully RP's patch that changes the layer compatible string to warrior gets applied to meta-openembedded soon-ish :-) Apr 02 19:21:46 I've just pinned oe-core revision to second to latest (just before this commit) Apr 02 19:22:15 because e.g. meta-raspberrypi, meta-gplv2 will need similar change as well Apr 02 19:34:06 JaMa: I fixed meta-gplv2. I'd be tempted to fix meta-openembedded but I probably shouldn't Apr 02 19:41:52 RP: I've sent fix for meta-gplv2 but it probably got stuck in moderator approval Apr 02 19:42:08 RP: khem already sent a fix for meta-oe layers, it's on patchwork Apr 02 19:43:04 JaMa: I saw that patch but I fixed meta-gplv2 hours ago? Apr 02 19:44:05 JaMa: ah, it may have predated me doing that? Sorry, I guess it didn't arrive until later :/ Apr 02 19:44:26 anyway, gplv2 should be fixed, if not let me know Apr 02 19:44:28 no problem with that Apr 02 19:45:21 I got unsubscribed from yocto ML some time ago, so it was delayed by moderator approval, all is fine now Apr 02 19:47:20 RP: what is your take on having multiple releases listed in LAYERSERIES_COMPAT? Apr 02 19:47:52 RP: I've seen that you listed always only the latest (which makes sense to me even when it needs more coordination between layers around release) Apr 02 19:48:10 RP: khem on the other hand just added warrior at the end e.g. in https://github.com/agherzan/meta-raspberrypi/pull/406 Apr 02 19:49:05 RP: my opinion is somewhere in the middle, I'm tempted to just add warrior temporary (until I know that all layer users already upgraded) to currently latest oe-core/warrior revision which has the updated codename Apr 02 19:50:01 RP: and for some layers like meta-qt5 it's actually useful to list all compatible ones (as long as there is someone activelly using such combination and testing), because people like to mix different Qt and Yocto releases together (including us) Apr 02 19:51:57 RP: and adding more entries to LAYERSERIES_COMPAT from your integration layer is a bit complicated (I'm using extra meta-qt5-compat layer which overrides the LAYERSERIES_COMPAT from meta-qt5): Apr 02 19:52:01 # We made the neccessary changes to make meta-qt5 compatible with meta-webos Apr 02 19:52:03 LAYERSERIES_COMPAT_qt5-layer = "thud" Apr 02 19:52:46 but such shim layer needs to be in right place in BBLAYERS as well, so it's a bit unfortunate (or I'm missing some much simpler sollution) Apr 02 19:58:13 JaMa: My view is that we should really specifically state what we're being compatible with. I tend to think it should be a single release unless you actively test with mltiple releases Apr 02 19:58:22 I'm ok with transition but people forget to remove it later Apr 02 20:01:21 agreed Apr 02 20:05:05 JaMa: I should have done this earlier in the cycle with a bit more transition time but I simply forgot :( **** ENDING LOGGING AT Wed Apr 03 02:59:57 2019