[13:49] <ahasenack> 'morning
[13:51] <Laibsch> Hello, I just noticed that focal has a more recent package for samba than jammy.  The reason for the newer package in focal is among others CVE-2021-43566 to which jammy is still vulnerable.  That left me wondering what the security policy is for ubuntu+1.  No security support or would this be considered a bug?  I was just wondering if I should open a ticket.  Obviously, I didn't think I'd open myself up to security pro
[13:51] <Laibsch> ting out ubuntu+1 before it's release.
[13:54] <ahasenack> Laibsch: we try to keep devel up-to-date, but sometimes fail
[13:55] <Laibsch> so it is a "bug"? should I file a ticket?
[13:55] <ahasenack> Laibsch: this is the bug requesting the update: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1946839
[13:55] <Laibsch> OK, it's already done. Even better.
[13:55] <ahasenack> it doesn't mention the cves specifically, it's a generic one to update samba in the devel release, and is how we keep track of it
[13:56] <ahasenack> in fact, it's on my plate to handle that, I think next week
[13:56] <ahasenack> it's a big change, because we will have to go ahead of debian again, in debian samba is asking for a new maintainer
[13:56] <ahasenack> or help, in general
[13:56] <ahasenack> I'm even working on smaller stuff this weekend so I have time for the big problems next week ;)
[13:57] <Laibsch> awesome. thank you for your work!
[13:58] <ahasenack> cheers
[20:14] <dima5> Hi. I'm looking at the Jammy release schedule. It says that the Debian import freeze is on Feb 24. I'm looking at a package that made it into Debian/sid around two weeks ago (mrcal), and it's not in jammy yet (as reported by packages.ubuntu.com). Is this just a matter of time, or does something need to happen to make sure that package is included? Thanks
[20:25] <Eickmeyer[m]> dima5: It's there: https://launchpad.net/ubuntu/+source/mrcal
[20:26] <Eickmeyer[m]> Of course, they left before I could respond. >.<
[20:26] <Eickmeyer> Meer seconds at that.
[20:49] <ahasenack> it's in proposed still, though
[20:50] <ahasenack> it failed to build
[20:50] <ahasenack> not sure what this error is: "Couldn't parse out argument kind at mrbuild/make-pod-from-help.pl line 94."
[21:18] <Eickmeyer> dima5: ^
[21:18] <Eickmeyer> ahasenack: Yeah, I let them know in a query.
[23:19] <dima5> ahasenack: it builds just fine in Debian. I'll look with a jammy chroot
[23:19] <dima5> How did you see that it failed to build? Did you just try it, or is there a status page somewhere?