[06:15] <cpaelzer> good morning
[06:35] <utkarsh2102> cpaelzer: o/
[06:39] <cpaelzer> hi utkarsh2102
[06:43] <mirespace> good morning
[06:44] <utkarsh2102> mirespace: \o
[06:44] <mirespace> hi utkarsh o/
[07:03] <Intelo> while giving firewall rules in cloud/vps like ditigalocean etc. how to do something like 123.33.*.*?   do I need to enter like 123.33.0.0/32    or /24  or something else?
[07:24] <andol> Intelo: What you write as 123.33.*.* is usually written as a 123.33.0.0/16 CIDR, where the value after the slash is the number of bits needed to define the network.
[07:25] <Intelo> what does 16, 24, 32 mean?
[07:27] <andol> Intelo: As I said, it's the number of bits needed to define the network range. See also https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing
[07:28] <andol> Anyway, the magical keyword to lookup is CIDR.
[11:56] <athos> good morning!
[11:59] <mirespace> hi athos!
[12:20] <ahasenack> ugh, language-packs being imported
[12:20] <ahasenack> git-ubuntu really slows down
[12:54] <rbasak> ahasenack: I think I need to add a regexp-based auto prioritisaion thing :-/
[12:55] <rbasak> I've bumped language-pack-* down in priority again manually for now.
[12:57] <ahasenack> thx
[13:21] <rbasak> Also linux-* :-/
[14:48] <ahasenack> mirespace: hi, when you get a chance, could you please set this old MP to "merged"? For merges from debian, git-ubuntu doesn't do that automatically
[14:55] <mirespace> hi ahasenack... marking amavisd-new merge as merged :$
[14:56] <ahasenack> \o/
[14:56] <ahasenack> thx :)
[15:06] <mirespace> :)
[17:30] <lvoytek> cpaelzer: Do you think the FFe bug for swtpm is ready to be subscribed to ubuntu-release and set to new, or is there anything else I need to do to prepare it? https://bugs.launchpad.net/ubuntu/+source/swtpm/+bug/1950631
[17:30] <ubottu> Launchpad bug 1950631 in swtpm (Ubuntu) "[FFe] wrap swtpm in an apparmor profile" [High, In Progress]
[22:29] <bryceh> lvoytek, fwiw imho it looks fine to sub ubuntu-release.  It's not unlikely you'll need to ping that team in IRC anyway to get prioritized attention on it.
[22:30] <bryceh> one thing you might clarify, if known, is if the future MIR would target jammy or post-jammy.
[22:31] <lvoytek> Sounds good, thanks!