 you're also missing 100% of the standard SRU policy for Ubuntu - open a Launchpad bug requesting the SRU with the template, get approval from the Ubuntu Release Team, etc.
 SRU is *not* Lubuntu Only
 What are you refering to? Was there a deleted message? 😅 (re @teward001: you're also missing 100% of the standard SRU policy for Ubuntu - open a Launchpad bug requesting the SRU with the template, get approval from the Ubuntu Release Team, etc.)
 No, I gave him a ping about something yesterday. (re @Halis: What are you refering to? Was there a deleted message? 😅)
 Should the existing bug get converted to a SRU or should a new bug get created? (re @teward001: you're also missing 100% of the standard SRU policy for Ubuntu - open a Launchpad bug requesting the SRU with the template, get approval from the Ubuntu Release Team, etc.)
 i don't see the preexisting bug?
 is there an LP bug?
 there it is
 There is an existing launchpad bug report with the template described in the SRU wiki. I have also added the debdiffs.
 Once the packages are in proposed, I will add the lp tags (re @teward001: you're also missing 100% of the standard SRU policy for Ubuntu - open a Launchpad bug requesting the SRU with the template, get approval from the Ubuntu Release Team, etc.)
 so you're simply asking for a sponsor
 not many of those on the Lubuntu group right now :P
 i can do it but i'm in the middle of some work stuff at FT job
 question: why was sponsors NOT subscribed here?
 (part of the SRU process)
 'cause without being in sponsors NOBODY is going to pick it up unless they have upload rights and specifically are informed about it like here
 (it won't show up in the sponsoring report)
 Because the sponsoring is/was done Lubuntu internally via phab.
 gonna be honest, I think that's a bit of a broken process, because i think only really Walter and Simon truly understood how that works
 @kc2bez I think this falls in your purview?
 since you have to do changes, etc. on the phab side
 and there's dev work there that I just don't touch regarding merging into specific branches and such
 but with Phab starting to go the way of the dodo 'soon' we need a new process.
 I can handle the phab stuff. I was just hoping you could look over the other stuff to make sure it was on track.
 ok i'll have to review the diffs then
 FT job is keeping me headache levels busy atm
 I appreciate your help.
 When you get a chance of course.
 No need to hurry and thanks in advance
 @aptghetto revisions required
 we don't alter the package standards version when we're SRUing
 the rest looked ok though
 Thanks, will do it tomorrow