 *drops a grenade*
 The_LoudSpeaker I'd have to review the package first and get an idea for how maintainable it is, etc.  One of the things we're working on behind the scenes is that there's a dedicated developer willing to maintain the software
 even while in backports (you can't just backport and forget, security concerns and what not)
 but the process hasn't been finalized yet
 and right now backports are selectively approved/handled
[18:29] <The_LoudSpeaker> so you are saying you can look into the package and approve it?
 i can look into the package
 but then I have to talk to Laney about it
 *and* it needs someone with upload privs to be willing to maintain it
 long term and provide security updates, etc. backporting where needed
 backports isn't going to be as simple as 'oh ok we can backport it' anymore in the future :P
[18:30] <The_LoudSpeaker> also, its in universe rn so it will stay in universe itself? or migrate into backports?
[18:30] <The_LoudSpeaker> you don't have the upload rights?
[18:32] <The_LoudSpeaker> also, you can look at the source via a apt source micro on focal or groovy. focal has 2.0.1 and groovy has 2.0.6 afaik. 
[18:32] <The_LoudSpeaker> need to get 2.0.6 in focal
 oh i have upload rights the question is "do I really want to maintain this going forward"
 as i just said
 backports is no longer an "upload and forget"
 whoever wants it in backports (i.e. me, etc.) needs to be willing to maintain the package, patches, etc. going forward.  it ALSO needs to build with minimal changes.
 and right now backports is pretty stagnant/dead right now
[18:33] <The_LoudSpeaker> yeah for the same reason I asked if it really needs to go to backports? 
[18:33] <The_LoudSpeaker> its already in universe repos of focal
 > micro maintained
 what exactly is 'micro maintained' lol
[18:36] <The_LoudSpeaker> what I mean is can someone update micro which right now is sitting in focal-universe to the latest version thats present in groovy-universe ?
[18:37] <The_LoudSpeaker> it was " a package named micro, maintained in debian by a friend" not "micro maintained". wouldn't make sense.
 yeah well you weren't clear ;P
[18:38] <The_LoudSpeaker> well you haven't provided me my coffee yet. maybe that's why.
 the source package is named 'micro' yes?
[18:38] <The_LoudSpeaker> yes!
 NACK
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964271
[18:38] <The_LoudSpeaker> its a text editor.
 autoremoval on the 17th
 unless your friend and the Debian Go Packaging Team are willing to *fix* this grave RC bug
 i'm not backporting it
 hell I'll even request it's removal from Ubuntu if the issue is grave enough :P
 (welcome to the security centric mindset I have)
[18:40] <The_LoudSpeaker> okay. I will let them know about this RC bug.
 if they read the package tracker like I do
 they'd already know it
 tell em to read https://tracker.debian.org/pkg/micro regularly
 I do this with ALL my packages I maintain in Debian
[18:41] <The_LoudSpeaker> noted.
 should point out that notice has been on the tracker since the 7th of July
 and it's a month since then
 soooooooooooooooooooooooooooo
[18:42] <The_LoudSpeaker> yeah yeah I got it.
 the issue is also in a go-dependent package so
 the dep on golang-x-text is the problem since that has the grave RC bug
 if you can't work with the package without golang-x-text and the Debian Go Package Team and Upstream don't fix the CVE then the package gets removed from testing
[18:44] <The_LoudSpeaker> I think you should join us in #debian-golang on oftc and remind them.
 not my job to look after packages I don't have a vested interest in :P
 YOU however can make that notice yourself
 that said
 they may be waiting on Upstream to patch it
 or for upstream to make a major version release because https://github.com/golang/go/issues/39491 is marked 'fixed'
[18:46] <The_LoudSpeaker> yeah just saw
[18:46] <The_LoudSpeaker> they are pobably waiting for a new release
 still labeled 'needs fixed' upstream but the issue is closed so
 well unless they release by the 17th that apcakge and its rdeps get purged from testing
[18:47] <The_LoudSpeaker> and after that from groovy-universe?
[18:49] <The_LoudSpeaker> well @teward001  check this: 
 utkarsh2102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964271 is important for micro it seems.
[18:49] <The_LoudSpeaker> [zwiebelbot] Debian#964271: golang-x-text: CVE-2020-14040 - https://bugs.debian.org/964271
 The_LoudSpeaker: there's no need to fix this here
 It's already fixed in golang-golang-x-text.
 the fix is in debian? i mean uploaded?
 In the next upload of micro, we'll switch from golang-x-text to golang-golang-x-text.
 yep.
 okay. once you do that let me know. I got you a sponsor for it in focal-universe
 It was fixed and uploaded on 15th July.
 The_LoudSpeaker: perfect!
 no you haven't gotten a sponsor yet
[18:50] <The_LoudSpeaker> XD
 oh ALSO
 NACK becuase E:MissingDependencies
[19:04] <The_LoudSpeaker> this is gonna be a chain of SRUs then.
 yep