[01:01] <callmepk> good morning
[05:02] <jibel> Good morning 
[05:47] <oSoMoN> good morning desktoppers
[05:53] <jibel> salut oSoMoN 
[05:57] <Maik> good morning all
[06:03] <didrocks> good morning
[06:06] <Maik> heya didrocks
[06:06] <didrocks> hey Maik 
[06:09] <oSoMoN> salut jibel, hey Maik, salut didrocks 
[06:10] <Maik> hi there oSoMoN
[06:11] <Maik> and jibel too :)
[06:11] <didrocks> salut oSoMoN 
[06:31] <KGB-1> mozjs debian/78/master Julien Cristau * [open] merge request !3: Update configure flag --disable-ion to --disable-jit on mipsen to fix FTBFS. * https://deb.li/kMcs
[06:58] <marcustomlinson> morning callmepk jibel oSoMoN Maik didrocks
[06:59] <Maik> marcustomlinson: hey :)
[07:00] <didrocks> hey Maik 
[07:00] <didrocks> oupss
[07:00] <didrocks> marcustomlinson*
[07:00] <marcustomlinson> :)
[07:00] <didrocks> ma[tab] -> not enough letters :)
[07:58] <KGB-0> mozjs debian/78/master Simon McVittie * [merge] merge request !3: Update configure flag --disable-ion to --disable-jit on mipsen to fix FTBFS. * https://deb.li/kMcs
[08:02] <Laney> greetZ
[08:02] <marcustomlinson> hey Laney
[08:10] <seb128> goood morning desktopers
[08:11] <Laney> hey marcustomlinson & seb128 
[08:11] <Laney> happy friday to you
[08:12] <seb128> hey Laney, how are you? happy friday!
[08:16] <oSoMoN> good morning marcustomlinson, Laney, seb128 
[08:16] <seb128> lut oSoMoN, comment ça va ?
[08:16] <oSoMoN> seb128, bien, et toi?
[08:17] <seb128> ça va ! encore un peu malade et fatigué
[08:17] <seb128> not looking forward the weekend, dunno if I've the energy for it atm :-p
[08:21] <Laney> /o\
[08:21] <Laney> you need a sprint to use as a rest
[08:23] <Laney> hey oSoMoN 
[09:48] <KGB-1> mozjs pristine-tar a9ab827 Simon McVittie mozjs78_78.3.0.orig.tar.xz.delta mozjs78_78.3.0.orig.tar.xz.id * pristine-tar data for mozjs78_78.3.0.orig.tar.xz * https://deb.li/rVLG
[09:48] <KGB-1> mozjs upstream/78 ca76201 Simon McVittie (6 files in 5 dirs) * New upstream version 78.3.0 * https://deb.li/3Ix6M
[13:51] <seb128> Laney, do you have any hint to display the update_excuses.yaml section corresponding to a specific component?
[13:52] <seb128> I just browse with gedit but I find always a bit annoying to know where the component section starts and end
[14:39] <KGB-2> mozjs tags f98b390 Simon McVittie upstream/78.3.0 * Upstream version 78.3.0 * https://deb.li/3xWVx
[15:14] <Laney> seb128: what do you mean?
[15:15] <Laney> like show all of the packages in main?
[15:43] <seb128> Laney, no, like 'display me the section corresponding to the gnome-control-center package'
[15:44] <seb128> the section start by - component: universe
[15:44] <seb128> so if you search for e.g "item-name: something"
[15:44] <seb128> you are in the middle of the something entries
[15:45] <seb128> then need to scroll back up to the beginning, often past screens of autopkgtests items, easy to get lost
[15:46] <Laney> right, it's not really optimised for human reading
[15:46] <Laney> you might want a script for that?
[15:47] <Laney> section might be missing btw, in that case it means main
[15:47] <seb128> right, that was my question, before I re-invent the wheel I was asked if people who work more with those reports than me have tools I don't know about
[15:47] <Laney> component*
[15:47] <seb128> asking*
[15:47] <seb128> seems not that you know about then
[15:47] <seb128> thanks for the reply!
[15:47] <Laney> not me, I've not wanted to use the excuses yaml like that
[15:47] <Laney> I would use rmadison to find out the component for a package
[15:48] <seb128> well, usually I try to figure out what property I can use to improve the team reports :p
[15:49] <seb128> so I browse the sections and properties to see if I find something useful
[15:49] <Laney> I see
[15:49] <Laney> makes sense
[15:49] <seb128> I just did one for component mismatch, so that didn't have a split information ready to use
[15:49] <Laney> is this for verisons?
[15:49] <seb128> I ended up parsing reasons
[15:49] <seb128> no, it's for https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#desktop-packages
[15:50] <Laney> I see
[15:50] <Laney> that has universe package on it?
[15:50] <seb128> see lintian on that one now https://people.canonical.com/~seb128/reportmismatch.html
[15:50] <seb128> no, sorry my "component: universe" comment was probably confusing earlier
[15:51] <seb128> $ head update_excuses.yaml 
[15:51] <seb128> generated-date: 2020-09-25 13:13:35.575091
[15:51] <seb128> sources:
[15:51] <seb128> - component: universe
[15:51] <seb128>  
[15:51] <seb128> ...
[15:51] <seb128> head doesn't even have the item-name
[15:52] <seb128> so you can't search for an item-name and scroll down is all I meant there :)
[15:52] <seb128> that one for example has its first section starting with a component entry
[15:52] <Laney> ah
[15:52] <seb128> I with it was
[15:52] <seb128> sources:
[15:52] <seb128>  - item-name: bla
[15:52] <seb128> ...
[15:53] <seb128> - item-name: gnomish
[15:53] <Laney> I guess it's alphabetical order?
[15:53] <seb128> ...
[15:53] <seb128> looks like it yes
[15:55] <Laney> it's likely that component mismatch check I wrote in proposed-migration should move to a policy
[15:55] <Laney> don't think I could upstream it in the current implementation
[15:56] <Laney> https://git.launchpad.net/~ubuntu-release/britney/+git/britney2-ubuntu/commit/?id=7ad785d983a15c771745123859cc937aa97a97cb
[15:57] <Laney> oops, there's an unrelated change there (test_autopkgtest.py)
[15:57] <seb128> I assume that would be something like that because Ubuntu specific
[15:57] <seb128> well, I built on what we have in https://code.launchpad.net/~seb128/ubuntu-archive-scripts/display-components-mismatch/+merge/391370
[15:58] <Laney> it doesn't have to be ubuntu specific, debian would want this for main -> restricted
[15:58] <seb128> easiest way
[15:58] <seb128> right, I was just wondering about non-free
[15:58] <Laney> umm non-free yah
[15:58] <seb128> :)
[15:58] <seb128> btw I think you can also help me on #ubuntu-devel :p
[15:59] <Laney> but mainly I am mentioning this because if I did make that change that way of reading the yaml would probably break
[15:59] <Laney> maybe not
[15:59]  * Laney goes to devel
[16:03] <seb128> Laney, it would perhaps stop working but probably not error out the way it's written
[16:04] <Laney> correct
[16:05] <seb128> oh, slyon found a reproducer for bug #1871538
[16:05] <seb128> slyon, nice one!
[16:09] <Laney> w00t
[16:18] <seb128> unsure if that's the same bug than the upgrade one though after reading it, it's something than can lead to gdm being unhappy but that doesn't seem something an upgrade would be doing?
[16:19] <Laney> wait what
[16:19] <Laney> not sure about that
[16:19] <Laney> let me try this
[16:24] <Laney> I think it's basically saying that root can signal stuff
[16:24] <Laney> and kill(-1) basically means kill all the things
[16:26] <juliank> all things in the process group?
[16:27] <juliank> ah no, all it can send kill to
[16:27] <juliank> kill(0) was the group thing
[16:27] <juliank> kill -1 as root is ... evil
[16:28] <Laney> that is a nicely malicious dbus method, indeed
[16:28] <Laney> but not a reproducer for the bug
[16:29] <juliank> true
[16:29] <Laney> I'm wondering what slyon was writing to be trying kill(-1) :>
[16:29] <juliank> maybe netplan has a kill going wrong somewhere
[16:29] <Laney> "I was trying to write a remote killswitch into netplan, and ..." :D
[16:30] <juliank> i don't see a wrong kill in there
[16:30] <Laney> in where?
[16:31] <juliank> Laney: in netplan
[16:31] <Laney> I assume/hope that it was only ever local and didn't get committed
[16:31] <Laney> it says "while developing some netplan code" in the comment
[16:32] <juliank> yup
[16:32] <Laney> otherwise, eek²
[16:45] <ry> Hello everyone, running Ubuntu 20.04.1 w/ gnome-shell 3.36 and wondering how I can view a historcial desktop notifications log, or create one? (cli/text would be fine) I've done a lot of searching but everything seems to come back to very old projects incompatible with Ubuntu 20.04.