Newest at the top
| 2026-02-24 00:24:19 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2026-02-24 00:24:00 +0100 | v0id_7 | (~v0id_7@user/v0id-7:62772) (Quit: whatever u sick fcks) |
| 2026-02-24 00:23:06 +0100 | Googulator | (~Googulato@2a01-036d-0106-499d-1c5a-0e4b-5795-d7e3.pool6.digikabel.hu) |
| 2026-02-24 00:22:49 +0100 | Googulator | (~Googulato@2a01-036d-0106-499d-1c5a-0e4b-5795-d7e3.pool6.digikabel.hu) (Quit: Client closed) |
| 2026-02-24 00:21:39 +0100 | dutchie | (~dutchie@user/dutchie) dutchie |
| 2026-02-24 00:21:26 +0100 | dutchie | (~dutchie@user/dutchie) (Server closed connection) |
| 2026-02-24 00:19:44 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-24 00:18:08 +0100 | <Leary> | geekosaur: I got two of them revised eariler, but now the refined invocation looks like this: <https://gist.github.com/LSLeary/52377ecaa9e9090c7e26b91945f6d587>. I'm not sure I have it in me. <.< |
| 2026-02-24 00:13:32 +0100 | peterbecich | (~Thunderbi@71.84.33.135) (Quit: peterbecich) |
| 2026-02-24 00:11:25 +0100 | Anarchos | (~Anarchos@91-161-254-16.subs.proxad.net) (Quit: Vision[]: i've been blurred!) |
| 2026-02-24 00:08:39 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds) |
| 2026-02-24 00:06:46 +0100 | tromp | (~textual@2001:1c00:3487:1b00:1a7:fa86:12e2:7e3d) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2026-02-24 00:04:22 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-23 23:53:43 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2026-02-23 23:50:03 +0100 | jtnuttall | (~jeremy@user/jeremyn) jeremyn |
| 2026-02-23 23:48:59 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-23 23:48:25 +0100 | user363627 | (~user@user/user363627) (Remote host closed the connection) |
| 2026-02-23 23:43:57 +0100 | jtnuttall | (~jeremy@user/jeremyn) (Ping timeout: 255 seconds) |
| 2026-02-23 23:40:29 +0100 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) Lord_of_Life |
| 2026-02-23 23:39:36 +0100 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) (Quit: Laa shay'a waqi'un moutlaq bale kouloun moumkine) |
| 2026-02-23 23:38:06 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 255 seconds) |
| 2026-02-23 23:36:35 +0100 | <geekosaur> | if you have tested it and it works with 4.22, I'd allow it; dependencies are their problem (but as a courtesy I generally file issues against them requesting bounds updates) |
| 2026-02-23 23:36:20 +0100 | <tomsmeding> | the only argument against that I can see is that it's potentially confusing for a user: the package supports 4.22 but can't actually be built with it |
| 2026-02-23 23:35:49 +0100 | s4msung | (QGVxIqNFjX@user/s4msung) s4msung |
| 2026-02-23 23:35:29 +0100 | <tomsmeding> | Leary: tentative opinion that you can include 4.22 |
| 2026-02-23 23:35:26 +0100 | s4msung | (koCZlVvn6A@user/s4msung) (Server closed connection) |
| 2026-02-23 23:34:54 +0100 | Milan_Vanca | (~milan@user/Milan-Vanca:32634) (Quit: WeeChat 4.7.2) |
| 2026-02-23 23:33:37 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-23 23:30:36 +0100 | ursa-major | (114efe6c39@2a03:6000:1812:100::11f3) ursa-major |
| 2026-02-23 23:29:23 +0100 | ursa-major | (114efe6c39@2a03:6000:1812:100::11f3) (Ping timeout: 268 seconds) |
| 2026-02-23 23:24:27 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 268 seconds) |
| 2026-02-23 23:22:36 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 268 seconds) |
| 2026-02-23 23:19:06 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) |
| 2026-02-23 23:16:48 +0100 | michalz | (~michalz@185.246.207.215) (Remote host closed the connection) |
| 2026-02-23 23:16:11 +0100 | __monty__ | (~toonn@user/toonn) (Quit: leaving) |
| 2026-02-23 23:15:34 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-23 23:15:06 +0100 | polykernel_ | polykernel |
| 2026-02-23 23:15:05 +0100 | polykernel | (~polykerne@user/polykernel) (Ping timeout: 248 seconds) |
| 2026-02-23 23:12:21 +0100 | polykernel_ | (~polykerne@user/polykernel) polykernel |
| 2026-02-23 23:07:44 +0100 | peterbecich | (~Thunderbi@71.84.33.135) peterbecich |
| 2026-02-23 23:06:59 +0100 | <int-e> | Oh I meant it could be broken specifically because of a change in base. |
| 2026-02-23 23:06:36 +0100 | <Clint> | if the dependencies get fixed then you'd be excluding it for no reason |
| 2026-02-23 23:05:49 +0100 | <int-e> | Leary: It could build but still be broken. (Not very likely, but it would be a reason to exclude 4.22) |
| 2026-02-23 23:05:34 +0100 | <Leary> | I don't know, accurately representing buildability? I'm leaning towards allowing 4.22, I'm just not sure I should. |
| 2026-02-23 23:05:00 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds) |
| 2026-02-23 23:02:15 +0100 | CiaoSen | (~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) (Ping timeout: 268 seconds) |
| 2026-02-23 23:01:57 +0100 | <Clint> | what purpose would that serve? |
| 2026-02-23 23:00:12 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-23 22:57:52 +0100 | emmanuelux | (~em@user/emmanuelux) emmanuelux |
| 2026-02-23 22:56:10 +0100 | <Leary> | Suppose I have a package that fails to build with base 4.22 but succeeds with `--allow-newer=all:base`, i.e. only because its dependencies require revision to allow it. Should its bounds exclude 4.22? |