18:02:55 <Meths> jperkin: There doesn't appear to be a snort package in 202304, firstly, is that correct or did I miss something?  Secondly is this a build failure that is waiting to be fixed or is there another reason it's not available?
18:30:15 <jperkin> it's not in my required packages list so it's not something I'd notice, I can add it (and am happy to add anything else that folks depend on)
18:30:36 <jperkin> the only reasons a package won't be available are build issues or that distribution of binary packages is not permitted by the license
18:31:20 <jperkin> according to https://us-central.manta.mnx.io/pkgsrc/public/reports/2023Q4/x86_64/20240508.1627/meta/report.html it's unavailable due to a dependency on daq
18:31:40 <jperkin> the daq build failure is a trivial one to fix, I'll get that patched
18:35:14 <jperkin> (software that is still using pre-C99 int types, insert eye roll emoji)
18:59:55 <Meths> Thanks.  How do the build cycles work?  Will that appear in 202304 when fixed or will it be in the next quarter's packages?
19:01:19 <jperkin> I apply the fix to trunk first (so it'll show up there in the next build), and then on request I'll backport to LTS as required
19:01:47 <jperkin> daq is fixed, snort may take longer, it's grovelling around in bits of netinet that it shouldn't be
19:41:14 <jperkin> ok, so I guess I don't have anything better to do on a Friday night ;)
19:41:17 <jperkin> => Signing binary package /home/pbulk/build/net/snort/work/.packages/snort-2.9.16.1nb6.tgz (GPG)