2025-04-01 21:01:03 when trying to upgrade deno, it fails to build due to undefined systems when expecteding icu 76, but icu-dev-76 is pulled, so idk why that would fail 2025-04-01 21:01:05 https://gitlab.alpinelinux.org/Matthias/aports/-/jobs/1792220#L1158 2025-04-01 21:02:40 or maybe the better approach for now is to just disable tests, idk 2025-04-01 21:02:49 and keep the current version 2025-04-01 22:37:51 after !82206 and !82208 we could theoretically drop llvm/clang 17 2025-04-02 00:49:56 From Trusted and Vouched Dealers... (full message at ) 2025-04-02 00:54:08 @ikke @ncopa ^^ 2025-04-02 05:38:22 ikke!82037 is ready for review/merge, and then I guess subsequent move to Community, if you wish, since it works great on my two craptops here the past few days 2025-04-02 05:57:27 pj 2025-04-02 07:52:54 fossdd[m]: don't see any spam and pj is not op so nothing can be done I guess 2025-04-02 07:53:09 besides the matrix.org bridge will be going down anyway 2025-04-02 07:53:34 the spam was on the matrix side and pj is op on the matrix side 2025-04-02 07:53:37 but its removed now 2025-04-02 07:53:40 oh, ok nice 2025-04-02 08:31:38 I built electron and got signal-desktop back. many thanks to the electron maintainer! 2025-04-02 08:38:14 Praise “secure” applications working on a web browser :> 2025-04-02 08:41:01 Electron is a beast 42000 objects to build, 2.2 GB in ccache! 2025-04-02 08:46:24 :D 2025-04-02 09:02:06 No wonder it's so fast at runtime! 2025-04-02 09:54:06 I think !82234 is a sensible solution while we figure out how to get the latest deno release to build 2025-04-02 10:34:45 WANTED: Alpine Package Maintainer for GUI/CLI program - hardinfo2 - system information and benchmarks. 2025-04-02 10:35:33 See https://hardinfo2.org - source code: https://github.com/hardinfo2/hardinfo2 - contact create issue on github, thanx. 2025-04-02 10:46:54 Build instructions for Alpine Linux/PostMarketOS - https://github.com/hardinfo2/hardinfo2/discussions/87 - see bottom. 2025-04-02 10:48:59 hwspeedy: the easiest would be to start a package yourself https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package :p 2025-04-02 10:54:54 Thanx, I know - but you run out of time as project maintainer - sofar it is used from 91 different distros, 11 architectures - so hoping a nice Alpine package maintainer would take the challenge and enable it for postmarketos as well, thanx. 2025-04-02 11:00:24 hwspeedy: best to package it yourself I believe. Then later if someone else wants to takeover they can. 2025-04-02 11:04:40 open an issue, sometimes people pick requests from the issues 2025-04-02 11:07:27 that works too 2025-04-02 11:47:44 Thanx, Created Alpine Packaging issue: https://gitlab.alpinelinux.org/alpine/aports/-/issues/17052 2025-04-02 13:21:50 could someone review this mr? https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/81012 2025-04-02 15:37:01 I'm trying to better understand the upgrade from icu 74.2 -> 76.1, as https://gitlab.alpinelinux.org/alpine/aports/-/commit/ba5442d4932d09139948f4e9d8d106c75c501cc7?page=3 shows that php83 was rebuilt against icu 76.1, but I keep having riscv pipelines failing and https://pkgs.alpinelinux.org/packages?name=php83&branch=edge&repo=&arch shows 8.3.19-r0 for riscv while it shows the rebuilt one for all the other architectures. How does 2025-04-02 15:37:01 the riscv php83 get updated? 2025-04-02 15:37:44 the builder is still busy see https://build.alpinelinux.org/ 2025-04-02 15:37:49 but at this point i think its stuck 2025-04-02 16:04:29 jahway603[m]: it gets updated the same way as the other arches. builder's running now but it'll take some time for it to get to community/ packages. just check back later 2025-04-02 16:11:13 ahoy! an idle merge request notification invited me to come here, so here I am. https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/80024 2025-04-02 16:18:14 Funny how as soon as deno builds are fixed, something else goes and breaks 2025-04-02 16:21:36 I wonder if paast 404 is to do with ip range ban due to AI crawlers recently 2025-04-02 16:21:40 https://build.alpinelinux.org/buildlogs/build-edge-x86_64/community/passt/passt-2025.03.20-r0.log 2025-04-02 16:21:56 Since I can download the archive with curl no problems 2025-04-02 16:34:34 Would reverting the commit where it is upgraded cause a rebuild? 2025-04-02 16:35:13 omni 2025-04-02 16:35:24 If pkgver and rel match what's in the repo, then not 2025-04-02 16:52:50 ikke: sertonix ncopa did you receive the poll I sent you for the APK meeting? Or maybe there were some issues with the bridge? 2025-04-02 16:55:20 PabloCorreaGomez[m]: received it 2025-04-02 17:19:48 speaking of bridges do you still want one after the matrix.orf bridge's shut down? Just curious 2025-04-02 17:19:53 matrix.org* 2025-04-02 17:24:26 actually maybe wrong channel 2025-04-02 17:24:33 I'll ask in -infra 2025-04-02 17:56:59 @f_ i would appreciate a matrix bridge. Saves me setting up a BNC 2025-04-02 18:17:50 Saijin_Naib[m]: we moved to -infra 2025-04-02 18:35:39 !82256 2025-04-02 18:47:03 It's strange that only the x86(_64) builders have timed out, despite the others succeeding 2025-04-02 18:52:15 Is it possible to bump up the CI time allocation for a given pull request to aports 2025-04-02 18:52:54 AledCuda[m]: you have to increase it for your fork 2025-04-02 18:53:16 I'm attempting to bring up alpine on the zynqmpsoc but the 1hr timeout is just under whats needed for the aarch64 runner to finish building the kernel https://gitlab.alpinelinux.org/ld-cd/aports/-/pipelines/312819 2025-04-02 18:53:18 Ah ok 2025-04-02 18:53:41 I presume passing in CI is a prerequisite for getting merged? 2025-04-02 18:54:21 Except for certain exceptions, yes 2025-04-02 18:58:32 Ok I believe I have set that correctl 2025-04-02 18:59:10 This is my first time contributing to alpine 2025-04-02 18:59:30 is there any other information I should include about the change beyond what I've included here: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/82218 2025-04-02 19:00:01 1) you should increase the `pkgrel` field 2025-04-02 19:00:26 2) Updating the linux-lts package also requires to rebuild some out-of-tree modules 2025-04-02 19:01:02 Should I squash that into a single commit with the config change? 2025-04-02 19:01:08 Hmm 2025-04-02 19:01:11 the pkgrel bump, yes 2025-04-02 19:01:29 The _krel bump for those other modules requires separate commits 2025-04-02 19:01:53 If 2) is the case and I have one other change to the config should I close this and reopen with that change as well 2025-04-02 19:01:58 or favor smaller change sets 2025-04-02 19:03:06 You don't need to recreate MRs, and these changes should be a single MR 2025-04-02 19:03:33 Sounds good 2025-04-02 19:03:45 is there a list of out of tree modules I can reference somewhere? 2025-04-02 19:05:13 All *-lts packages that have a _krel field 2025-04-02 19:05:24 https://tpaste.us/4vrX 2025-04-02 19:08:53 One commit updating the LTS package and _pkgrel and then one commit bumping the _krels all in one MR? 2025-04-02 19:09:52 one commit per package 2025-04-02 19:10:22 AledCuda[m]: https://gitlab.alpinelinux.org/alpine/aports/-/commits/master?search=kernel 2025-04-02 19:23:48 Thanks 2025-04-02 19:25:09 Kladky: that revert is no longer necessary 2025-04-02 19:26:12 ikke: do you know what the issue was then? 2025-04-02 19:27:00 no 2025-04-02 19:31:33 Seems like it's art_standalone's turn to cause builders to fail 2025-04-02 19:32:18 And zaproxy too 2025-04-02 19:56:24 Or I guess not... 2025-04-02 20:29:27 Alright assuming the CI passes does this look correct: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/82218 2025-04-02 21:50:14 Do I need to rerun the pipeline everytime I rebase? 2025-04-02 23:36:43 https://gitlab.alpinelinux.org/ld-cd/aports/-/jobs/1794050 2025-04-02 23:36:51 Alright it passes in CI 2025-04-02 23:37:18 I think this is ready to merge if anybody has the bandwidth 2025-04-02 23:37:35 And if the changes make sense 2025-04-02 23:38:15 I feel bad for sucking down so many hours of CI time