**** BEGIN LOGGING AT Mon Jan 24 02:59:56 2022
Jan 24 07:39:13 <mckoan> good morning
Jan 24 20:07:28 <marex> RP: kanavin: I have but one last question, I just noticed gstreamer 1.20 will likely be released very soon, is there any chance that one will still make it into kirkstone ?
Jan 24 20:07:38 <marex> or is the deadline for such major updates already past ?
Jan 24 20:07:57 <marex> it would help with those imx8m with hantro vpu
Jan 24 20:27:01 <kanavin> marex, the deadline would be end of february-ish, or basically M3 release
Jan 24 20:27:27 <kanavin> If you want to increase the chance of getting it in, prepare the updates now, with pre-releases if they're available
Jan 24 20:27:52 <kanavin> marex, after that, you can provide such updates via mixin layers
Jan 24 20:47:57 <marex> kanavin: ah, if the deadline is end of February, that's perfect, I'm adding it into the todo ...
Jan 24 21:09:32 <kanavin> marex, https://github.com/GStreamer/gstreamer/blob/master/NEWS does not fill one with confidence about any delivery dates
Jan 24 21:10:22 <kanavin> and I recommend you start it now, not add it to todo - you will need time to iron out all the issues
Jan 24 21:11:09 <marex> kanavin: hold on
Jan 24 21:11:48 <marex> kanavin: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests?label_name%5B%5D=Blocker there are two open blockers
Jan 24 21:12:37 <marex> kanavin: I am not sure about the decodebin one, once the other one is fixed, I suspect the release would happen
Jan 24 22:42:51 <Jin^eLD> hi, I am wondering if anyone ran into this issue: I have updated from dunfell to master and suddenly my devshell stopped working; first it tries "There is no screen to be resumed matching devshell_2618636." and repeats that a couple of times, then fails
Jan 24 22:43:04 <Jin^eLD> and the error in the end says: "Directory '/run/screen' must have mode 777"
Jan 24 22:43:20 <Jin^eLD> is that some pseudo issue or where is that coming from?
Jan 24 22:43:54 <Jin^eLD> fun fact: when I change it to 777 then it goes one step further but then starts complainint that its not 775, if  quickly change that to 775 while its repeating its attempts then I get a devshell session :)
Jan 24 22:44:28 <Jin^eLD> but the whole behavior does not make sense to me, since I did not really change anything on the build system before pulling master, I suspect its "something new" that I either need to configure or.. dunno?
Jan 24 22:44:29 <Jin^eLD> any hints?
**** ENDING LOGGING AT Tue Jan 25 02:59:56 2022