=== sem2peie- is now known as sem2peie
=== seb128_ is now known as seb128
[12:05] <sil2100> seb128: thanks for the langpack reminder!
[12:05] <sil2100> seb128: as you probably saw, I pushed out the first base langpacks today
[12:46] <seb128> sil2100, hey, np, thank you for triggering a landing!
[13:23] <seb128> could someone remember me the vcs used to host the script that generate the rls incoming bug reports?
[15:30] <rbasak> seb128: it's not https://bazaar.launchpad.net/~ubuntu-reports-dev/ubuntu-reports/trunk/files is it?
[15:45] <seb128> rbasak, I don't think it is, that has no much recent activity
[15:46] <seb128> rbasak, the incoming report I meant is e.g http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html
[16:00] <Laney> eek
[16:00] <Laney> it took me ages to find that last time
[16:00] <Laney> ask bdmurray, that will be quickest
[16:01] <Laney> I want to say it is https://code.launchpad.net/~arsenal-devel/arsenal/2.x
[16:02] <bdmurray> That's the framework yes
[16:05] <seb128> Laney, bdmurray, thanks
[16:06] <seb128> hum, that has no commit for 6 years, that can't be right?
[16:06] <seb128> we added that new tag earlier this year to the report
[16:06] <Laney> Brian did it in some config file that's not in git
[16:06] <bdmurray> what are specifically looking to do?
[16:07] <Laney> the code is hard, I think that getting mentorship up front would be a good way to do it :-)
[16:07] <seb128> bdmurray, I was looking at making bugs that are still tagged but also targetted not listed
[16:07] <seb128> e.g http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html includes bug #1880508
[16:07] <ubottu> bug 1880508 in nvidia-graphics-drivers-440 (Ubuntu Groovy) "package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6" [Undecided,Confirmed] https://launchpad.net/bugs/1880508
[16:08] <seb128> we thought that those should probably be filtered out since they are basically handled if they are targetted for the serie and assigned
[16:08] <seb128> it's a bit late on a friday to start on something non trivial or do mentoring though
[16:11] <bdmurray> seb128: the backend is a launchpad bug search so I guess it'd be tag=rls-gg-incoming and not bugtask for groovy basically?
[16:17] <seb128> bdmurray, right
[17:54] <ItzSwirlz> Hey guys, does anybody know what the current Groovy wallpaper status us?
[17:56] <bdmurray> ItzSwirlz: that's usually a last minute thing so I wouldn't panic
[18:09] <ItzSwirlz> aight bc for UCR we typically colorize the groovy wallpaper to our #DD682A as our main and Lubuntu is entering beta (its in QA now)
[21:28] <bdmurray> Does vim FTBFS for anybody else on Groovy?
[22:06] <diddledan> what's the current status of 18.04 to 20.04.1 upgrades? I see there are no more blockers but my systems still aren't upgrading so I'm guessing there's something else happening? ref: https://discourse.ubuntu.com/t/focal-fossa-20-04-1-lts-point-release-status-tracking/17604
[22:07] <diddledan> is there anything that we onlookers can be helping with to get that unclocked?
[22:07] <diddledan> clogged*
[22:26] <bdmurray> diddledan: We are just doing some final testing and didn't want to turn on upgrades on Friday. We are planning for next week.
[22:37] <diddledan> roger that :-)