2024-10-01 07:46:37 ptrc: main as default? 2024-10-01 07:51:42 https://pkgs.alpinelinux.org/contents 2024-10-01 07:51:53 The main repo is already selected 2024-10-01 08:23:01 ah 2024-10-01 08:23:24 need to update that part as well 2024-10-02 18:31:49 i dont think every maintainer got an email from pkgs.a.o. seems i didnt handle the exceptions correctly 2024-10-02 18:32:30 clandmeter: did you see the issue created today? 2024-10-02 18:32:52 yes it was created after the fix :) 2024-10-02 18:33:11 ah ok, because I received a similar e-mail after the issue was created 2024-10-02 18:33:39 similar email? 2024-10-02 18:33:41 from pkgs? 2024-10-02 18:33:45 yes 2024-10-02 18:33:53 the email should be before 2024-10-02 18:34:03 else i dont know how this user could have known 2024-10-02 18:34:05 Let me check 2024-10-02 18:34:34 right, 6 minutes before 2024-10-02 18:35:24 oh the issue was first :) 2024-10-02 18:35:33 but i did fix it already locally 2024-10-02 18:35:42 i saw the mail coming in and noticed the error 2024-10-02 18:36:03 ok :) 2024-10-02 22:03:54 ikke: the update failed kind of, looks like python oomed 2024-10-02 22:04:18 so i set init = true which will always process all indexes 2024-10-02 23:41:45 not sure if it's already been reported, but the gitlab history button returns 500 error on some aports directories. noticed it recently due to new apkbrowser's "Git repository" link now points to gitlab.a.o instead of git.a.o 2024-10-02 23:42:10 e.g. https://gitlab.alpinelinux.org/alpine/aports/-/commits/master/community/libwacom compared to https://git.alpinelinux.org/aports/log/community/libwacom 2024-10-03 06:53:26 there seem to be an issue with Anitya and version numbers for getmail6, upstream releases are of this format 6.19.04, but Anitya thinks this == 6.19.4 and therefor nags that the package it not latest versio 2024-10-03 06:54:33 https://github.com/getmail6/getmail6/tags 2024-10-03 06:56:29 You just upgraded it to 6.19.05 though 2024-10-03 06:58:11 yes, but guess it will nag in a few hours again 2024-10-03 06:58:22 Ok 2024-10-03 06:58:46 Maybe more than a few hours, depending on how quickly fortify-headers is fixed 2024-10-03 07:00:09 "getmail6 current: 6.19.04-r0 new: 6.19.4" 2024-10-03 07:00:16 was the last nag 2024-10-03 07:00:16 (fortify issues are preventing 5 archs from proceeding to testing/) 2024-10-03 07:00:18 Ok 2024-10-03 07:03:02 As for me, Anitya nags me to upgrade Perl to an odd-numbered dev version, but not sure how you would solve that without a special exception for Perl that ignores dev versions 2024-10-03 07:06:19 ah thats also anoying, I guess I will only get one nag per release, but you will get it everytime they do a new dev release? 2024-10-03 07:07:08 Thankfully Perl dev releases are not made that often 2024-10-03 08:37:57 HRio: yes i noticed some version issues 2024-10-03 08:38:12 I am just using apk version comparison logic 2024-10-03 08:44:43 i am wondering how often we need to send these emails 2024-10-03 08:44:47 every day, every week? 2024-10-03 08:46:26 If it's going to keep sending emails for all outdated packages, at most once a week 2024-10-03 08:48:17 Previously it would just send one email per version 2024-10-03 09:39:21 it will only send email when a pkg is flagged 2024-10-03 09:39:37 so when pkg is updated the flag is reset 2024-10-03 09:42:51 it could be an option to include the previous flagged packages, but only send on new. 2024-10-03 09:43:04 previously it would send one email per pkg 2024-10-03 13:37:30 I think the fortify upgrade is causing Go test to fail: https://gitlab.alpinelinux.org/fabricionaweb/aports/-/jobs/1542801 2024-10-03 13:40:51 better for #-devel? 2024-10-03 13:42:47 Not in there for the time being, there will probably be others that fail on the same thing 2024-10-03 13:43:12 ACTION remembers yyjson, goes to try a rebuild 2024-10-03 13:50:25 yyjson already has -Wno-stringop-overflow from the last time a fortify upgrade was attempted 2024-10-03 14:08:32 Anyway, it seems this has been reported: https://github.com/jvoisin/fortify-headers/issues/68 2024-10-03 14:11:12 Hehe, as usual, ppc64le is not affected (looking at the Go MR) 2024-10-03 14:53:03 same issue as https://github.com/jvoisin/fortify-headers/issues/68 2024-10-03 14:54:11 do we have smaller testcases? 2024-10-03 14:59:38 Are you asking for other aports that fail with the strongop-overflow error? 2024-10-03 14:59:44 Aports simpler than Go and the kernel 2024-10-03 15:00:07 Probably an isolated test case? 2024-10-03 15:00:39 If so, then yyjson, after removing -DCMAKE_C_FLAGS and -DCMAKE_CXX_FLAGS 2024-10-03 15:01:15 That was a reply to simpler aports, not isolated test cases 2024-10-03 15:03:25 I think even libindi (!72922) has -Wstringop-overflow, but it's not treated as an error 2024-10-04 06:33:14 ACTION found that several previous problems in new pkgs.a.o have been fixed \o/ 2024-10-04 08:37:17 Oh I see pkgs.a.o has been switched to apkbrowser. Nice! 2024-10-04 08:52:24 Yes 2024-10-04 09:01:54 huh, abuuld segfaults https://tpaste.us/qYMw 2024-10-04 09:02:02 abuild* 2024-10-04 09:03:11 It's not abuild that segfaults 2024-10-04 09:04:02 It's modpost that is segfaulting 2024-10-04 09:07:55 right 2024-10-04 09:08:37 but first time see segfaults when building kernel, i.e. more than 30 years 2024-10-04 09:16:13 first time ofc if my memory still work :) 2024-10-04 09:18:18 looks like fortify-headers are buggy 2024-10-04 09:29:26 as expected, downgrading fortify-headers fixes this problem 2024-10-04 09:31:02 ah, looks like ncopa did something about this 2024-10-04 09:35:14 looks like I have to add cron task to do `apk upgrade` every 5 minutes ;) 2024-10-04 10:24:18 apk add apk-cron 2024-10-04 10:24:26 but will only do it daily iirc 2024-10-04 10:28:34 this was joke, I prefer manual upgrade