[12:27] <teward> so https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1979917 is tagge
[12:27] <teward> marked as security bug.  should we do a security upload patch or just SRU?
[12:27] <teward> also i hate typing on phones >.<
[12:29] <amurray> teward: hmm in general we prefer to suggest in these cases to get CVEs assigned then we can just follow the usual process (which I see you have already done) - but an SRU would also be okay (although it wouldn't end up in the security pocket without special attention)
[12:30] <teward> amurray: i havent gone the cve issuance route nor checked if one was issued
[12:30] <teward> i have enough to do without breaking my back with MITRE rules :P
[12:31] <amurray> teward: oh I thought I had seen you ask them if a CVE had been assigned... perhaps I was thinking of some other bug (I wasn't suggesting that you go through that process, more that we suggest to the reported to go and do that)
[12:31] <teward> given fancy_index is not included in the main nginx-core and only default-ships in universe nginx-extras i'm not tooooooo concerned.  yet :P
[12:33] <amurray> ahh ok - I always get confused about packages which have different binaries split across main vs universe
[12:36] <teward> yep
[12:36] <teward> amurray: re: nginx thats a question you can always poke me on :P
[20:29] <ahasenack> sbeattie: hi, I'm doing an nfs-utils merge for kinetic, and while going over bugs I could perhaps close with the update I found https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1918312
[20:29] <ahasenack> I think that is something that should be fixed upstream
[20:30] <ahasenack> if you agree, maybe could you add a comment asking the reporter to try to revive the upstream thread?