=== mIk3_09 is now known as mIk3_08
[13:00] <cpaelzer> hiho
[13:01] <cyphermox> hello
[13:01] <cyphermox> doko: jdstrand: didrocks:
[13:02] <cyphermox> ok didrocks is not going to be there
[13:02] <cyphermox> cpaelzer: I started looking at the bugs earlier, we have a few open
[13:03] <cyphermox> libheif is still in the list for Security to review
[13:04] <cyphermox> rygel I just assigned to the Desktop team (needs at least a chnge in Recommends, it's trivial, but also a look at some XML code)
[13:05] <cyphermox> gupnp-dlna I would have to look at the comments more to figure out what the next steps are
[13:06] <cpaelzer__> oh
[13:06] <cpaelzer__> cyphermox: am I back
[13:06] <cpaelzer__> vpn issues today keep on troubling me :-/
[13:06] <cpaelzer__> there is an older MIR on gupnp-dlna
[13:06] <cyphermox> cpaelzer__: ok
[13:07] <cpaelzer__> didrocks reviewed and they decided to punt it to next cycle
[13:07] <cpaelzer__> have you talked about that in the past?
[13:07] <cpaelzer__> as it was later reopened what seems to be a community member?
[13:07] <cpaelzer__> I think we should set https://bugs.launchpad.net/ubuntu/+source/gupnp-dlna/+bug/1785649 back to incomplete
[13:07] <ubottu> Launchpad bug 1785649 in gupnp-dlna (Ubuntu) "[MIR] gupnp-dlna" [Undecided,New]
[13:07] <cpaelzer__> what do you think?
[13:08] <cyphermox> I haven't stalked about it gain with the team
[13:08] <cyphermox> let's ask seb.
[13:08] <cyphermox> (I will)
[13:08] <cpaelzer__> ok
[13:08] <cyphermox> ah, and I will re-review libbluray
[13:08] <cpaelzer__> the other one open is libheif
[13:08] <cyphermox> cpaelzer__: still in security review
[13:09] <cyphermox> cpaelzer__: anything on your side for server?
[13:09] <cpaelzer__> nothing new
[13:09] <cpaelzer__> we have a few on securities queue
[13:09] <cpaelzer__> but nothing new opened/closed
[13:09] <cyphermox> ok
[13:09] <cpaelzer__> aynthing from you that needs help?
[13:10] <cyphermox> I had opened ec2-instance-connect, it needs help probably
[13:10] <cpaelzer__> I had reviewed that
[13:10] <cyphermox> but best check with fginther or someone in CPC
[13:10] <cyphermox> yeah
[13:10] <cpaelzer__> as well as security
[13:10] <cpaelzer__> and I have learned that rbasak has reviewed it before it was a MIR
[13:10] <cyphermox> but since I opened it and did the packaging maybe it's best if I don't go review that one
[13:10] <cyphermox> yes
[13:10] <cyphermox> AFAIK those are all known issues, but it's how that package works :/
[13:10] <cpaelzer__> IMHO until at least the major issues are addressed there isn't mcuh to do on our side
[13:11] <cyphermox> yeah ok
[13:11] <cpaelzer__> fginther should be the right one for driving this via the contact to the upstream authors
[13:11] <cyphermox> yep
[13:11] <cyphermox> okay then, I guess we're through the list
[13:11] <cpaelzer__> cyphermox: also the packaging wasn't the big issue
[13:11] <cyphermox> no, I know
[13:11] <cpaelzer__> yeah I'm ok for this week
[13:11] <cyphermox> the scripts are special.
[13:11] <cpaelzer__> "special" ... nicely put
[13:23] <doko> ouch, forgot ...
=== cpaelzer__ is now known as cpaelzer