2021-04-05 16:51:34 clandmeter: https://gitlab.alpinelinux.org/alpine/infra/turbo-paste/-/issues/4 2021-04-05 16:52:23 nmeum: thanks 2021-04-05 17:07:01 np 2021-04-06 12:15:54 ncopa: ping 2021-04-06 14:36:19 clandmeter: pong 2021-04-06 15:55:34 ncopa: https://github.com/lxc/lxc/issues/3640 2021-04-06 15:55:42 wonder if thats related to our issue 2021-04-06 17:52:34 clandmeter: Hi friend 2021-04-06 17:52:52 looks like this fixes CAP_SYS_ADMIN 2021-04-06 17:53:27 just applied it and tested locally, looks like it works fine 2021-04-06 17:53:58 mps: which commit did you pick? clandmeter said it did not apply 2021-04-06 17:54:16 I have 'lxc.cap.drop = sys_admin' in lxc config 2021-04-06 17:54:25 first one 2021-04-06 17:54:40 https://github.com/brauner/lxc/commit/d524a35c49bdbf7132f91ac7678cbb9876091a68.patch 2021-04-06 17:54:40 So https://github.com/brauner/lxc/commit/d524a35c49bdbf7132f91ac7678cbb9876091a68 2021-04-06 17:54:44 right 2021-04-06 17:55:12 lxc started without any issue 2021-04-06 17:55:35 should I prepare MR? 2021-04-06 17:55:41 fine with me 2021-04-06 17:56:17 ok, after coffee break 2021-04-06 17:56:17 (gotta love commits without context: "fix cgroups mounting" 2021-04-06 17:56:30 heh, I just grabbed a coffee myself) 2021-04-06 18:07:29 ikke: btw, do we have bug opened for this issue 2021-04-06 18:07:55 https://gitlab.alpinelinux.org/alpine/aports/-/issues/12281 2021-04-06 18:08:08 12281 2021-04-06 18:08:12 :) 2021-04-06 18:08:32 ah, still don't know good method to search bugs 2021-04-06 18:08:52 I just searched for lxc cgroup 2021-04-06 18:08:54 only know for 'brute force', i.e. string 2021-04-06 18:09:00 https://gitlab.alpinelinux.org/alpine/aports/-/issues 2021-04-06 18:09:14 hmm, I searched for 'lxc' only 2021-04-06 18:09:25 even then, it's the first result for me 2021-04-06 18:09:31 yes 2021-04-06 18:09:36 also for me 2021-04-06 18:09:54 Funny enough, this mentioned they _need_ to drop SYS_CAP_ADMIN 2021-04-06 18:11:27 believe me that using this web interface is quite annoying and complicated on my workstation with only touchpad and not real mice 2021-04-06 18:12:17 glab issue list --search lxc 2021-04-06 18:15:39 installed glab but didn't setup it 2021-04-06 18:16:42 !20206 2021-04-06 18:25:51 !20207 is for 3.13-stable 2021-04-06 18:26:56 mps: 'CAP_SYS_ADMIN not working' is misleading btw :) 2021-04-06 18:27:14 the problem is that it's not working _without_ it 2021-04-06 18:28:09 right 2021-04-06 18:28:31 maybe 'fix mounting cgroups without SYS_CAP_ADMIN'? 2021-04-06 18:28:35 my bad english 2021-04-06 18:29:52 not sure I understand this sentence 2021-04-06 18:30:46 but please, update MRs commit msgs however you think is best 2021-04-06 18:30:51 "fix mounting cgroups" 2021-04-06 18:31:00 the issue that we face 2021-04-06 18:31:13 "without SYS_CAP_ADMIN", the condition that causes this issue 2021-04-06 18:31:40 aha, patch msg is ' fix cgroup mounting' 2021-04-06 18:31:47 yeah 2021-04-06 18:32:02 That's the error that it gives when it fails 2021-04-06 18:32:07 let me reword it and push update 2021-04-06 18:32:19 conf.c: lxc_mount_auto_mounts: 728 Cross-device link - Failed to mount "/sys/fs/cgroup" 2021-04-06 18:33:24 'main/lxc: fix cgroup mounting, close #12281' ? 2021-04-06 18:34:05 with one space less :) 2021-04-06 18:34:28 does this sounds correct? 2021-04-06 18:35:06 or just 'main/lxc: fix cgroup mounting' 2021-04-06 19:05:39 Hello 2021-04-06 19:05:45 o/ 2021-04-06 19:05:52 Glad you guys solved it 2021-04-06 19:05:55 :) 2021-04-06 19:05:58 can you test it? 2021-04-06 19:06:03 if you still have your env 2021-04-06 19:06:06 Nope 2021-04-06 19:06:09 ok 2021-04-06 19:06:12 I'm on phone 2021-04-06 19:06:17 That's hard 2021-04-06 19:06:21 Kinda difficult, yes 2021-04-06 19:06:32 Would be nice 2021-04-06 19:06:39 Android lxc 2021-04-06 19:07:35 I tested and it works in my case, but would be good if someone else can test 2021-04-06 19:09:02 interesting 'part' is that I looked this patch when the issue is reported and we discussed it, but commit msg mislead me 2021-04-06 20:18:12 mps: the fix is in edge? 2021-04-06 20:18:18 or also in stable? 2021-04-06 20:21:18 they are still MRs 2021-04-06 20:21:20 not merged yet 2021-04-06 20:21:30 but there is an MR for 3.13 2021-04-06 20:30:54 maybe apply it to edge? 2021-04-06 20:31:01 else im not sure how i can try 2021-04-06 20:31:21 grab the package from CI? :P 2021-04-06 20:33:46 ikke: I assigned it to you 2021-04-06 20:33:56 they* 2021-04-06 20:34:03 huh 2021-04-06 20:34:38 I think edge could be merged, it is 'edge' at the end 2021-04-06 20:35:55 ikke: do you agree? 2021-04-06 20:36:53 yes 2021-04-06 20:38:08 ok 2021-04-07 06:10:21 morning. i tested lxc from edge and it seems like dropping sys_admin caps works. good job mps! 2021-04-07 06:19:53 Nice 2021-04-07 06:46:08 good morning 2021-04-07 06:47:21 good job is done by clandmeter by reminding me to try patch. rest was just 'manual work' 2021-04-07 06:49:40 we should also merge MR for 3.13-stable? 3.12-stable version is ok, iirc 2021-04-07 07:17:01 morning friends 2021-04-07 07:18:16 good morning my friend, nice to see you active :) 2021-04-07 07:18:22 i think we also need to fix the lxc alpine template 2021-04-07 07:18:46 or am i the only one bumping into these mkdev issues? 2021-04-07 07:19:04 what issue? 2021-04-07 07:20:02 when creating an alpine container 2021-04-07 07:20:09 with -t alpine 2021-04-07 07:21:08 with lxc-create? 2021-04-07 07:21:16 si 2021-04-07 07:21:53 could you give complete cmd line, so I can check this evening 2021-04-07 07:23:28 not check, but confirm. I don't have any doubt in whatever you say 2021-04-07 07:23:50 lxc-create -t alpine foobar 2021-04-07 07:24:09 thanks 2021-04-07 07:26:24 https://imgur.com/a/alkl6XX 2021-04-07 07:27:05 i think more recent rootfs has default devices included 2021-04-07 07:30:48 looks like you are right (as usual) 2021-04-07 09:39:02 ikke: im unable to fetch my ssh keys again from gitlab? 2021-04-07 09:39:26 Sign 2021-04-07 09:39:46 Sigh* 2021-04-07 09:40:03 sign in is the soluition yes :) 2021-04-07 09:40:26 Hehe 2021-04-07 09:40:56 Should add an acceptance test for that 2021-04-07 09:48:13 Should be fixed in 13.9 2021-04-07 09:48:39 i thoughjt it was already fixed? 2021-04-07 09:50:36 https://gitlab.com/gitlab-org/gitlab/-/issues/296620 2021-04-07 09:50:46 Yes, and then regressed again 2021-04-07 09:54:22 ncopa: did you get issues with lxc-create and device creations? 2021-04-07 09:55:21 i think ive seen it before where devices are already existing, or they are regular files by some mistake. 2021-04-07 09:57:15 i made a patch to add some checks. https://tpaste.us/ejBX 2021-04-07 10:16:22 I recall him getting the same errors 2021-04-07 10:16:33 And I ran into it to 2021-04-07 11:36:54 yup, i bumped into the same 2021-04-07 18:16:57 clandmeter: yes, 'lxc-create -t alpine foobar' says 'mknod: dev/zero: File exists' 2021-04-07 18:55:27 when a secfix is recorded, i would like our system to email an advisory to a mailing list. 2021-04-07 18:55:47 should we create a list for security advisories, or use the announce list for this? 2021-04-07 18:59:31 Good question, not sure what the expectation is from people who are subscribed to the announce list 2021-04-07 19:08:08 i guess lets make a list for security announcements 2021-04-07 19:11:12 right 2021-04-07 19:11:44 security-announcements? 2021-04-07 19:49:24 sure 2021-04-07 19:54:00 mps: clandmeter I guess that should be easy enough to fix, not? 2021-04-07 19:55:50 ikke: clandmeter posted this https://imgur.com/a/alkl6XX this morning 2021-04-07 19:56:10 uh 2021-04-07 19:56:14 yes, that's what I was referring to 2021-04-07 19:56:15 no, sorry 2021-04-07 19:56:17 ok 2021-04-07 19:57:32 he posted something to tpaste but I can't find it now 2021-04-07 19:57:53 https://tpaste.us/ejBX 2021-04-07 19:58:08 yes, this 2021-04-07 19:58:24 looks as safe change to me 2021-04-07 20:16:35 ikke: let me know once the security-announcements list is ready :) 2021-04-07 20:24:19 https://lists.alpinelinux.org/~alpine/security-announcements 2021-04-07 20:36:42 thx 2021-04-07 20:36:55 I've restriced access to posting there 2021-04-07 20:38:45 yes, we will a specific email for the bot 2021-04-07 20:38:57 whatever you want it to be, it will be in the config file for the service 2021-04-09 07:43:48 terraform is pretty cool 2021-04-09 07:44:03 i got it running here on my local machine with libvirt 2021-04-09 07:44:17 i can spin up N ubuntu vms in less than a minute 2021-04-09 13:38:35 distfiles.a.o https' cert has run out I think 2021-04-09 13:55:29 Hmm 2021-04-09 13:56:19 So it appears 2021-04-09 13:56:35 It still has a dedicated cert 2021-04-09 17:11:01 Cogitri: cert is fixed, but not sure why it was not renewed 2021-04-09 17:21:27 ikke: Thanks for looking into it :) 2021-04-09 17:26:54 can we block ledest@gmail.com from posting 2021-04-09 17:26:55 thx 2021-04-09 17:27:09 this is the third time he decided to violate our CoC in the past week 2021-04-09 17:43:46 Is it fair to give one final warning? 2021-04-09 17:44:07 I agree that this inappropriate 2021-04-09 17:44:26 I'll respond 2021-04-09 17:44:27 can somebody else do so then? :) 2021-04-09 17:44:29 yes 2021-04-09 17:45:35 i mean, i only revived a topic that was pushed down the pipeline for further discussion later :p 2021-04-09 17:45:54 These are just ad-hominem remarks without any substance 2021-04-09 17:47:13 and i do not really care if we change the version number to 15 or to 4 or keep it as 3.x tbh 2021-04-09 17:47:46 i would prefer to drop the 3.x but :P 2021-04-09 17:48:18 I do kind see value in being able to signal major changes 2021-04-09 17:48:22 kind of* 2021-04-09 17:48:27 but alas 2021-04-09 17:49:59 huh, not good 2021-04-09 17:52:35 what is "not good" 2021-04-09 17:52:46 that Led person has been harassing me all week 2021-04-09 17:53:02 i have kindly asked him to stop several times now 2021-04-09 17:54:04 hmmm 2021-04-09 17:54:41 I would ignore such things 2021-04-09 17:55:25 you are free to do so, i would like to have a community where that is not needed :) 2021-04-09 17:56:02 We try to keep Alpine Linux a friendly community. For one person it's easier to shrug these kind of comments of as for another 2021-04-09 17:56:30 community is amorphous entity 2021-04-09 17:56:34 yes 2021-04-09 17:57:02 the other thing is, if people do not push back against that, it discourages other people from participating 2021-04-09 17:57:03 But at least on the communication channels that we procide, we expect people to be nice to eachother 2021-04-09 17:57:09 ofc, also I don't like to see bad people around 2021-04-09 17:57:20 Yeah, it creates a bad atmosphere 2021-04-09 17:57:26 there are a lot of people who can easily have their confidence broken by such crap 2021-04-09 17:57:31 which is why that person is doing it 2021-04-09 17:58:04 there are some which I dislike to be around but never wanted to ask ban on them 2021-04-09 17:58:36 mps: are these people personally harassing you? 2021-04-09 17:58:41 I simply ignore 2021-04-09 17:58:51 ikke: yes 2021-04-09 17:58:58 who are they? 2021-04-09 17:59:09 will not say 2021-04-09 17:59:10 cause that's not cool 2021-04-09 17:59:26 as I told I don't care 2021-04-09 17:59:43 well, do know that i appreciate your work on alpine even if we sometimes disagree :) 2021-04-09 18:00:16 Ariadne: no, you are not one of these, no worries :) 2021-04-09 18:00:50 we disagree sometimes and I don't think this is bad 'thing' 2021-04-09 18:01:40 No, certainly not 2021-04-09 18:02:17 well, for example, this started with that person jumping on me for proposing we look at netbsd curses as a lighterweight and simpler (thus more secure) alternative to GNU ncurses 2021-04-09 18:02:33 and implied i hated GNU and then asked why 2021-04-09 18:02:36 yes 2021-04-09 18:02:38 I'm trying to follow late Jon Postels robustness principle for the internet: be liberal in what you receive, be conservative in what you send 2021-04-09 18:02:56 https://lists.alpinelinux.org/~alpine/devel/%3Ce12847f2-4cea-c3e8-84c3-e98b92553f8e%40dereferenced.org%3E#%3CCAAO3vZ_EDSvMtM5Xg0qK3aAKi3nhaXYLHsUiHSfy4hvO1oXSmA@mail.gmail.com%3E 2021-04-09 18:02:59 i just hate crappy code regardless of where it comes from 2021-04-09 18:03:11 unfortunately there is a lot of crappy code in GNU :) 2021-04-09 18:03:32 yes, because most code is GNU ;) 2021-04-09 18:04:01 though MIT starting to prevail nowadays 2021-04-09 18:04:22 but I didn't made any statistics, tbh 2021-04-09 18:07:12 well using GPL does not mean something is GNU :p 2021-04-09 18:07:15 apk is GPL 2021-04-09 18:10:42 you know what I mean, I'm sure :) 2021-04-09 18:11:46 well the MIT X Server is certainly a pile of crap too :) 2021-04-10 05:07:07 build-edge-s390x seems MIA 2021-04-10 05:07:24 can someone check it? 2021-04-10 06:48:22 mps: checking 2021-04-10 06:48:26 \ar* 2021-04-10 06:48:28 Ariadne: * 2021-04-10 06:48:58 stuck on pygls 2021-04-10 06:49:04 ah 2021-04-10 06:49:05 somehow pytest still hangs from time to time 2021-04-10 13:01:56 clandmeter: upgraded nld5 to alpine 3.13 :) 2021-04-10 13:36:53 .1 2021-04-10 15:44:24 ikke: Nice 2021-04-10 15:44:56 Al ok with Ampere? 2021-04-10 15:46:23 sorry? 2021-04-10 15:47:26 The new box 2021-04-10 15:49:24 mtjade 2021-04-10 15:49:42 clandmeter: I backported your fix for lxc-templates-lxc 2021-04-10 15:50:00 We still need to sync all containers to this box 2021-04-10 15:50:36 clandmeter: I'm testing terraform + linode 2021-04-10 15:51:13 https://tpaste.us/axKl 2021-04-10 15:54:42 Right 2021-04-10 15:54:50 Didn't I try that before 2021-04-10 15:54:56 I don't remember 2021-04-10 15:55:01 Getting old 2021-04-10 15:58:37 I created a bucket in the storage account where the state is kept 2021-04-10 15:58:55 So we could run it in a pipeline and maintain the dns records in gitlab 2021-04-10 18:38:25 clandmeter: https://gitlab.alpinelinux.org/alpine/infra/linode-tf/-/jobs/368601 2021-04-11 08:16:42 clandmeter: https://gitlab-test.alpinelinux.org/clandmeter.keys 2021-04-12 06:34:42 ncopa: played a bit with tf this weekend ^ 2021-04-12 06:35:20 i plan to have an initial version of the security tracker ready for deploy at end of week 2021-04-12 06:35:48 how does the infra team deploy services? docker, right? 2021-04-12 06:36:04 Yes, docker + compose 2021-04-12 06:38:03 ncopa: we should be ready to migrate to usa9 2021-04-12 06:40:37 this application has a lot of tasks that need to be run as cron jobs 2021-04-12 06:48:09 We usually have a dedicated cron container for those kinds of jobs 2021-04-12 06:57:49 ok 2021-04-12 06:58:06 well more urgently, what the f is going on with our edge s390x builder 2021-04-12 06:58:18 because i can rebuild gdk-pixbuf just fine on my s390x machine 2021-04-12 06:58:43 I can look into it later today 2021-04-12 06:58:56 well can you just do 2021-04-12 06:59:03 head -n1 /usr/bin/meson 2021-04-12 06:59:42 on that container 2021-04-12 07:03:39 There is no meson binary 2021-04-12 07:03:54 Someone reported it was missing 2021-04-12 07:05:44 what the mcfuck 2021-04-12 07:05:57 but i have a meson binary on my s390x machine 2021-04-12 07:07:57 Sorry, the builder uninstalled the deps again 2021-04-12 07:09:23 Still missing 2021-04-12 07:09:33 Only abuild-meson 2021-04-12 07:43:56 Ariadne: I think you still have the old version, while the builder is using the latest version which has not been synced yet 2021-04-12 08:07:13 ikke: great! I'll move the arm contaienrs today then 2021-04-12 08:07:54 so, I have to make backups, just in case 2021-04-12 08:08:09 good. thanks 2021-04-12 08:08:55 heh, I mean my devel containers, not system wide 2021-04-12 08:09:06 yeah, i figured 2021-04-12 08:09:08 ikke: are all ci's going to run in qemu? 2021-04-12 08:09:14 I don't have access to bare metal there 2021-04-12 08:09:41 clandmeter: same as now, I guess? 2021-04-12 08:09:50 i dont know :) 2021-04-12 08:10:02 i hear libvirt and similar 2021-04-12 08:11:53 libvirt needs a bit more work 2021-04-12 08:12:03 need to fix the ovmf stuff for arm 2021-04-12 08:12:10 and add 32 bit arm 2021-04-12 08:13:07 ikke: i dont know if we are still using old ways to gen le certs, but here $work some certs expired due to ACMEv1 is eol. 2021-04-12 08:13:39 Jirutka had an init file for qemu vms right? 2021-04-12 08:13:52 its a project yes 2021-04-12 08:14:00 i think you can apk add it 2021-04-12 08:14:06 qe,u-openrc 2021-04-12 08:14:11 openrc-qemu or similar 2021-04-12 08:14:24 yeah qemu-openrc 2021-04-12 08:15:40 ovmf is broken? 2021-04-12 08:15:46 i know its missing arm32 2021-04-12 08:15:57 but last time i tried ovmf it worked 2021-04-12 08:16:00 well, depends on how you define "broken" 2021-04-12 08:16:17 iirc the first issue was that the files was not installed/named the way libvirt expected 2021-04-12 08:16:22 i guess a symlink fixes that 2021-04-12 08:16:23 its a bit of pain in the ass to build it i believe. 2021-04-12 08:16:39 oh yes thats possible 2021-04-12 08:16:54 i think i added a symlink before to the pkg 2021-04-12 08:17:10 but then i discovered that the APKBUILD is kinda broken as it builds old version, and not the version pkgver indicates 2021-04-12 08:17:30 yes i think mps did something iirc 2021-04-12 08:17:52 and then i discovered that latest version does not build 2021-04-12 08:17:54 so... 2021-04-12 08:17:57 i looked into ovms 2021-04-12 08:17:57 needs some work 2021-04-12 08:18:03 f 2021-04-12 08:18:16 but like you said, it does not just build 2021-04-12 08:19:05 i played with terraform and libvirt last week. its pretty nice 2021-04-12 08:19:22 I made !18588 2021-04-12 08:19:53 mps: thank you. seems like it does not build also 2021-04-12 08:20:09 but this error with python is 'showstopper' for me, I don't understand much of pythin 2021-04-12 08:20:16 python* 2021-04-12 08:20:32 i don think i will have time to look at ovmf today, but hopefully later this week 2021-04-12 08:21:23 maybe we can use 'binary release' temporarily, idk 2021-04-12 08:22:30 ncopa: I mean error with python in edk2, not python in general 2021-04-12 08:23:06 i think nomad also looks nice 2021-04-12 08:23:11 it also supports qemu 2021-04-12 08:27:53 havent looked at nomad 2021-04-12 11:17:24 Ariadne: fixed meson on s390x 2021-04-12 17:04:33 ikke: alright 2021-04-12 17:08:35 If you want, I can help with packaging the security tracker 2021-04-13 11:29:31 so, arm devs lxcs are not yet moved to new host? 2021-04-13 12:06:15 mps, i dont think thats an priority atm 2021-04-13 12:14:10 I could already do that 2021-04-13 12:14:59 ncopa takes care of the build containers 2021-04-13 12:21:49 ok, I'm not in a hurry, but stopped yesterday to use mine in hope it will be easier to move 2021-04-13 12:53:40 easier would be, you wake up and its done ;-) 2021-04-13 12:57:04 you mean, wake up after winter hibernation? I need something like this 2021-04-13 14:38:40 not done yet. sorry 2021-04-13 14:38:51 was busy with other stuff today. 2021-04-13 14:39:14 i did start with my lxc containers though... (to make sure they still work after move) 2021-04-13 14:39:46 it might be there is need for minor config change to make them run on new host 2021-04-13 14:49:10 np, as I told I'm not in any hurry 2021-04-13 14:56:05 I'll do the dev containers tonight 2021-04-13 16:01:55 that's an old commit 2021-04-14 08:02:01 do we have any developer docs for on-boarding new committers? 2021-04-14 08:02:12 i think we dont 2021-04-14 08:02:41 hum i should ask in #alpine-devel 2021-04-16 07:47:41 ikke: i found a few edge cases i want to fix, can we postpone to tomorrow or monday? 2021-04-16 07:48:24 Sure 2021-04-16 07:48:41 thx 2021-04-16 20:25:15 ikke: equinix block storage is going eol 2021-04-16 20:26:10 hmm 2021-04-16 20:26:15 are we using it for something? 2021-04-16 20:26:19 qemu storage? 2021-04-16 20:26:57 Yes 2021-04-16 20:27:10 Iscsi based 2021-04-16 20:27:26 hmm, 2021-04-16 20:27:43 I guess only for the arm based vms, right? 2021-04-16 20:27:58 Nod 2021-04-16 20:28:15 So we will move that anyway soon 2021-04-16 20:29:25 Probably 2021-04-16 20:29:30 Check mail 2021-04-16 20:31:09 Going to bed. Gnite 2021-04-16 20:31:14 nite 2021-04-17 13:25:09 clandmeter: updating directories when starting gitlab takes a long time, I assume because there are quite many files/directories nowayds 2021-04-17 13:25:12 nowadays 2021-04-17 13:37:21 Ariadne: I've already created a security.a.o domain record 2021-04-17 13:47:10 clandmeter: also, I'm managing linode domain records via terraform 2021-04-17 15:59:27 ikke: does it come from our scripts the updates? 2021-04-17 16:00:22 clandmeter: https://gitlab.alpinelinux.org/alpine/infra/docker/gitlab/-/blob/13.7-stable/overlay/usr/local/bin/entrypoint.sh#L130 2021-04-17 23:22:15 ikke: great :) 2021-04-18 11:13:11 clandmeter: I notice there are many empty artifact directories, that can explain 2021-04-18 11:24:21 clandmeter: gitlab has been upgraded to 13.9 2021-04-18 11:50:49 Maybe delete the empty dirs 2021-04-18 11:51:21 I did 2021-04-18 14:02:08 clandmeter: btw, I've also upgraded the host to alpine 3.13 2021-04-18 20:35:38 clandmeter: https://netbox-new.alpin.pw/ 2021-04-18 20:36:00 (if you resolve it to 172.16.14.1, it works) 2021-04-18 20:36:12 netbox 2.11 2021-04-19 06:20:47 morning 2021-04-19 06:21:02 usa1.alpinelinux.org was out of diskspace 2021-04-19 06:21:22 i have cleaned it up a bit and are now copying over build-edge-aarch64 to usa9 2021-04-19 08:19:05 👍 2021-04-19 08:40:31 im moving the build-edge-a* to usa9, all of them 2021-04-19 08:46:58 https://gitlab.alpinelinux.org/alpine/abuild/-/issues/10026 2021-04-19 08:47:09 This will become more relevant on usa9 2021-04-19 08:47:26 I wonder why the flock is not solving this 2021-04-19 09:19:41 im planning to have a look at it soonish 2021-04-19 09:19:54 we should try reproduce it in a testcase 2021-04-19 09:51:32 Yes, good plan 2021-04-19 09:52:48 question is how 2021-04-19 10:07:22 ikke: you already moved kdaudt-edge-aarch64 to usa9? 2021-04-19 10:17:07 Yes 2021-04-19 10:17:15 You can remove the old one 2021-04-19 10:23:28 deleted 2021-04-19 10:51:28 ^ is also an issue 2021-04-19 10:52:30 yeah 2021-04-19 10:52:35 not sure how to solve it 2021-04-19 10:53:22 I wonder if we still need the mirrors there 2021-04-19 10:53:43 We have 2 dedicated mirror hosts 2021-04-19 10:54:00 But I'm not sure if that has been switched over yet or not 2021-04-19 10:54:43 clandmeter: ^ 2021-04-19 18:16:14 netbox now has a journal for items 2021-04-19 20:34:14 ikke: hi 2021-04-19 20:34:41 hey! 2021-04-19 20:37:22 nice work on gitlab and netbox! 2021-04-19 20:38:37 did we start using the new linode mirrors with geodns? 2021-04-19 20:38:39 thanks 2021-04-19 20:38:43 I have no idea 2021-04-19 20:38:52 heh 2021-04-19 20:38:58 I suspect not yet 2021-04-19 20:39:01 well if you didnt enable it, i guess that means no 2021-04-19 20:39:13 i think i verified geodns worked 2021-04-19 20:41:34 clandmeter: did you also see that we can manage all DNS records with terraform? 2021-04-19 20:41:40 for alpinelinux.org 2021-04-19 20:41:48 i think i saw something 2021-04-19 20:42:30 https://gitlab.alpinelinux.org/alpine/infra/linode-tf 2021-04-19 20:45:34 is this in production? 2021-04-19 20:46:18 Yes 2021-04-19 20:46:42 In the sense that, when you make changes and run the deploy pipeline (manual trigger), then it would apply it 2021-04-19 20:47:21 You basically run 2 steps. first you create a plan, which shows you what would be changed 2021-04-19 20:47:28 and then you apply that plan, which makes the actual changes 2021-04-19 20:47:37 The basic idea is quite simple 2021-04-19 20:49:34 when you make no changes, nothing happens 2021-04-19 20:52:01 clandmeter: btw, do you have access to dmvpn2? 2021-04-19 20:52:52 i guess so 2021-04-19 20:53:16 trying to keep our infra up-to-date 2021-04-19 20:56:10 try now 2021-04-19 20:57:45 thanks, I'm in 2021-04-19 20:59:55 I already found a bug in netbox 2.11.0, which also has been fixed already :P 2021-04-19 21:04:04 journal, as in an audit / change log? 2021-04-19 21:04:17 manual changelog 2021-04-19 21:04:30 separate from the automatic changelog 2021-04-19 21:21:44 ah i see, that could be very useful 2021-04-19 21:22:08 where i work we're preparing to move off a Nokia IPAM in favor of netbox 2021-04-19 21:25:14 Aha 2021-04-19 21:30:33 Ariadne: need help with docker-compose? 2021-04-20 00:44:27 ikke: docker in general melts my brain :) 2021-04-20 04:26:53 Ariadne: maybe I can try to build it in docker? 2021-04-20 04:27:18 sounds like a good plan. i should have the final version ready shortly 2021-04-20 04:27:46 i am just writing some basic rewrite rules for the CPEs right now, so it will automatically map python CVEs to py-XXX source packages and so on 2021-04-20 04:28:32 alright 2021-04-20 07:23:15 Ariadne: sounds like progress, nice! 2021-04-20 11:11:06 either our secfixes data is woefully incomplete, or 3.13 has a lot of unpatched packages :( 2021-04-20 11:11:37 :-/ 2021-04-20 11:11:38 probably a mix of both, but still 2021-04-20 11:22:16 okay, so our secfixes data covers ~70% of identified vulnerabilities 2021-04-20 11:22:22 that is not too bad 2021-04-20 11:57:20 hmmph 2021-04-20 11:57:21 I: Evaluating for against 2021-04-20 11:57:22 I: No fix recorded against any version for 2021-04-20 12:03:04 D: wut? True 2021-04-20 12:03:07 u wot m8 2021-04-20 12:09:55 oic 2021-04-20 12:11:34 fixed it 2021-04-20 12:11:44 ctypes was passing it as wchar_t :D 2021-04-20 14:16:49 ikke: can you make https://gitlab.alpinelinux.org/kaniini/secfixes-tracker public? 2021-04-20 14:16:57 ikke: also the readme should cover what needs to be dockerized 2021-04-20 14:17:10 I can do it in a bit 2021-04-20 14:18:22 for the cron, you only need to run the `import-nvd recent` task 2021-04-20 14:18:33 you don't have to reimport the yearly feeds :p 2021-04-20 15:11:46 ikke: i wonder if you can help me setting up a CI for abuild git repo, that runs `make && make check` basically 2021-04-20 15:27:40 ncopa: sure 2021-04-20 15:51:29 Ariadne: repo is public 2021-04-20 16:12:47 Ariadne: it seems the example config file is missing 2021-04-20 17:49:17 hmm 2021-04-20 18:00:16 where is this nld9? in NL? 2021-04-20 18:00:34 yes 2021-04-20 18:00:49 and it is new developers box? 2021-04-20 18:01:06 it's the x86_64 builder 2021-04-20 18:01:17 ah, ok 2021-04-20 18:01:31 thanks for info 2021-04-20 18:01:35 usa9 is the arm/aarch builder 2021-04-20 18:02:21 RTT to usa is somewhat annoying when typing 2021-04-20 18:03:44 Yes, usa9 is in delaware 2021-04-20 18:04:02 Sorry, Dallas 2021-04-20 18:04:33 I mean, usa4 developers arm host 2021-04-20 18:04:47 but probably same RTT 2021-04-20 18:05:15 That one is New-York, so it might increase a bit even 2021-04-20 18:05:29 Newark 2021-04-20 18:06:43 linode in Frankfurt is fast 2021-04-20 18:06:53 for me ofc :) 2021-04-20 18:06:57 yes, for me as well 2021-04-20 18:07:49 ok, move all builders to usa and dev hosts to frankfurt :) 2021-04-20 20:46:09 Ariadne: https://security.alpinelinux.org/ 2021-04-20 20:49:14 No cron-jobs yet 2021-04-21 02:10:57 ikke: sick 2021-04-21 02:12:26 i wonder what the CPE is for https://security.alpinelinux.org/vuln/CVE-2021-28832 hahaha 2021-04-21 02:13:10 cpe:2.3:a:vim_project:vim:*:*:*:*:*:visual_studio_code:*:* 2021-04-21 02:13:14 WTF 2021-04-21 02:13:43 well, that's what secfixes-exclude is going to be for :p 2021-04-21 04:32:11 Ariadne: this is the docker project: https://gitlab.alpinelinux.org/alpine/infra/docker/secfixes-tracker 2021-04-21 04:44:14 btw, for some reason, uwsgi does not like the . imports in __init__.py 2021-04-21 06:15:04 what is secfixes-exclude? 2021-04-21 06:15:21 i think in the past version 0 has been used as "exclude" 2021-04-21 06:15:45 so CVE-this-and-that fixed in version 0 2021-04-21 06:16:04 to indicate that it never affected us 2021-04-21 06:22:03 good job on the secfixes thingy 2021-04-21 06:22:53 i guess there is no point in marking the sec known isses in gitlab as confidential 2021-04-21 06:24:08 the thinking behind making them confidential, even if the issues are publicly known, was to not provide a source for automatted attacks 2021-04-21 06:24:54 it would ofc be fully possible to create a list for automatted attacks from known sources, but the attacker would need to do the job. 2021-04-21 06:26:05 that was the reasoning at least 2021-04-21 06:26:58 is the update db a costly operation? would it be possible to update it on every git push? 2021-04-21 06:27:18 i mean, would it make sense to update it on git push 2021-04-21 06:27:47 then will updated secfixes data be visible directly after push and not up to 24 hours later 2021-04-21 06:55:11 it is not terribly costly 2021-04-21 06:55:27 importing the NVD feed is the costliest 2021-04-21 06:56:30 2019 should be imported now 2021-04-21 06:57:49 How far back do we want to go? 2021-04-21 07:10:49 i wouldn't go back too far yet 2021-04-21 07:11:02 i'm going to have to change the schema to support the maintainer reports Cogitri requested 2021-04-21 07:13:52 Ok 2021-04-21 07:14:18 Thanks for looking into it! :) 2021-04-21 07:15:10 Ariadne: I used sqlite for now, should not be an issue, right? 2021-04-21 07:15:19 i've been testing with sqlitee 2021-04-21 07:15:26 postgresql would be speedier of course 2021-04-21 07:16:00 Once it's settled, we can switch to pg 2021-04-21 07:17:11 yep 2021-04-21 07:17:21 makes sense, since i have not used alembic 2021-04-21 07:17:38 (i just didn't see the point in using alembic, since the database is meant to be reconstructed anyway) 2021-04-21 08:19:26 this is kinda interesting also https://repology.org/projects/?inrepo=alpine_edge&vulnerable=1 2021-04-21 08:32:13 Ariadne: nice work! 2021-04-21 08:33:07 ncopa: yes, repology takes a similar approach as mine 2021-04-21 08:34:31 Ariadne: the branch page is bit slower compared to other pages, is it caused by the db? 2021-04-21 08:35:09 clandmeter: yes, it scans the branch for vulnerabilities at the time of generating the report 2021-04-21 08:35:17 one possibility might be to add caching 2021-04-21 08:35:39 its using indexes properly? 2021-04-21 08:35:40 SQL is not really my area of expertise so there's probably some stupid shit i am doing too :) 2021-04-21 08:35:50 :D 2021-04-21 08:35:58 clandmeter: it could be optimized with a join, but i have not figured out how to do joins in sqlalchemy 2021-04-21 08:36:37 its not that bad, i dont think anybody will notice it. 2021-04-21 08:37:00 i am sure sombody will come along and optimize it 2021-04-21 08:37:42 well what we notice is that sec related services tend to get hammered by the community. 2021-04-21 08:37:54 Yup 2021-04-21 08:38:12 clandmeter: the hot paths are all optimized :) 2021-04-21 08:38:20 and we can just cache the reports 2021-04-21 08:38:41 or optimize with a join :) 2021-04-21 08:38:55 i'm sure it is not that hard to do a join in sqlalchemy, just have not looked into it yet 2021-04-21 08:39:17 writing 'web' stuff is not really what i usually do 2021-04-21 08:39:44 i'm just doing this so that we have the tool 2021-04-21 08:39:59 so we can move onto more interesting initiatives 2021-04-21 08:49:53 ikke: tagged v0.1.1 2021-04-21 08:51:31 Alright, will deploy in a bit 2021-04-21 08:58:34 ikke: cd ;-) 2021-04-21 08:58:52 ? 2021-04-21 08:59:32 Continuous deployment I guess 2021-04-21 09:01:00 yup 2021-04-21 09:01:05 perfect world senario 2021-04-21 09:02:10 I could deploy a gitlab runner that does the deployment 2021-04-21 09:45:33 Ariadne: docs is a false positive 2021-04-21 09:46:06 It's matched to the docker docs image 2021-04-21 09:48:29 :D 2021-04-21 09:48:45 i'm thinking we add a config item that lists packages which should be excluded entirely 2021-04-21 09:48:47 like docs 2021-04-21 09:48:48 :) 2021-04-21 09:51:31 I guess any virtual package? 2021-04-21 10:05:57 yes 2021-04-21 10:06:03 i'll add a heuristic for that 2021-04-21 10:23:35 i've also added: 2021-04-21 10:23:37 CUSTOM_REWRITERS = { 2021-04-21 10:23:37 } 2021-04-21 10:23:37 'jenkins:*': lambda x: 'jenkins', 2021-04-21 10:23:41 this allows us to uhh 2021-04-21 10:23:51 mitigate some of these really dumb CPE rules 2021-04-21 10:38:21 Ariadne: running import-nvd recent, import-apkindex, import-secfixes, update-states in sequence hourly should suffice for the cronjobs? 2021-04-21 10:38:27 yes 2021-04-21 10:42:43 working on merging the JSON-LD stuff 2021-04-21 10:51:22 hmm, what would be the best way to run crond scripts (or commands) as a specific user 2021-04-21 10:51:38 maybe easiest to use a crontab with a user specification? 2021-04-21 10:55:53 ikke: in docker? 2021-04-21 10:55:59 yes 2021-04-21 10:56:40 i dont think crond can run as a different user? 2021-04-21 10:57:32 or use su-exec 2021-04-21 10:57:44 if you want to run from root 2021-04-21 10:58:00 easiest would be a /etc/periodic/hourly script 2021-04-21 10:58:29 maybe that script should su-exec itself if run as root? 2021-04-21 11:05:13 i guess you can run the container as a different user? 2021-04-21 11:06:04 The uwsgi process runs as a normal user 2021-04-21 11:06:15 then I need a cron container with crond 2021-04-21 11:06:23 which afaik needs to run as root 2021-04-21 11:07:27 i just tried it and it runs as a diff user 2021-04-21 11:07:35 this is the part which melts my brain :p 2021-04-21 11:07:37 https://tpaste.us/oPzE 2021-04-21 11:07:59 import-apkdb? 2021-04-21 11:08:02 its apkindex 2021-04-21 11:08:06 ah, thanks 2021-04-21 11:08:24 you need a container which uses that same uid as the other process 2021-04-21 11:08:32 I will reuse the same image 2021-04-21 11:08:42 yes, thats what i normally do 2021-04-21 11:08:51 because it needs all the dependencies as well 2021-04-21 11:08:55 nod 2021-04-21 11:09:06 I learned from the best :P 2021-04-21 11:09:16 and the uids are the same :) 2021-04-21 11:22:42 Ariadne: deployed v0.1.1, I'll finish the crond part later 2021-04-21 11:24:55 Ariadne: oh, I guess the db would need to be created 2021-04-21 11:25:05 :P 2021-04-21 11:36:27 yes, uhh 2021-04-21 11:36:33 seems to not be working :p 2021-04-21 11:36:39 is that DB still down? :p 2021-04-21 12:06:05 F5 2021-04-21 12:11:56 i just tagged v0.2 with the json-ld stuff; no schema change 2021-04-21 12:16:48 imo if some security company abuses this service, we should ban them 2021-04-21 12:17:05 because the code is available, the data is available, they have no excuse not to run their own API server :p 2021-04-21 12:17:14 We already did for git.a.o secdb 2021-04-21 12:17:32 Through user agent 2021-04-21 12:17:34 :D 2021-04-21 12:17:52 i mean, bluntly, they can set up their own API server 2021-04-21 12:17:58 the code is FOSS 2021-04-21 12:18:00 the data is public 2021-04-21 15:27:23 Ariadne: 0.2 is deployed 2021-04-21 16:08:16 clandmeter: you can add user crontabs in /var/spool/cron/crontabs/ 2021-04-21 16:20:32 Ariadne: I have cron working, testing to see if it can properly update packages, and will be deploying that 2021-04-21 16:20:57 yep 2021-04-21 16:37:16 Ok, it's doing somethin now :) 2021-04-21 16:45:08 Ariadne: Should it be possible to run any of the jobs concurrently? 2021-04-21 16:45:28 sure as long as the update-states runs after the import jobs 2021-04-21 16:46:00 right, was expecting that 2021-04-21 16:48:23 btw, getting this warning: https://tpaste.us/DMJz 2021-04-21 16:48:28 just fyi 2021-04-21 16:54:52 yes known issue 2021-04-21 16:55:00 ok 2021-04-21 16:57:21 ok, crons should be in place now 2021-04-21 16:57:28 or cron :) 2021-04-21 16:58:41 https://gitlab.alpinelinux.org/alpine/infra/docker/secfixes-tracker/-/commit/f83f00e95857dc0e666bd7a994648bb8bb4b6b42 2021-04-22 08:06:47 Ariadne: are there any estimate when 3.11-main and 3.10-main will show up on security.a.o? 2021-04-22 08:10:56 It needs to be configured 2021-04-22 08:31:21 is security.a.o supposed to create issues in the bugtracker? 2021-04-22 08:31:36 Not yet 2021-04-22 08:32:01 It currently only lists them 2021-04-22 08:33:41 i mean is there a plan to make it create issues? 2021-04-22 08:35:05 it seems like we can no longer expect alicha create issues, so i think we sort of depend on security.a.o now 2021-04-22 08:36:06 so i think its kinda high prio to fix the remaining things in security.a.o now 2021-04-22 08:41:05 another issue: https://security.alpinelinux.org/vuln/CVE-2021-3121 2021-04-22 08:42:45 reports that protobuf before 1.3.2 is vulnerable to that specific CVE, but also state that it has version 3.13.0-r2 2021-04-22 08:46:24 i guess it means i have to spend time create the #secfixes entry for historical CVE issue that has not affected anyone ever (first protobuf version seems to 2.4.0) 2021-04-22 08:47:27 actually, it is different package 2021-04-22 08:47:32 its gogo protobuf 2021-04-22 08:50:23 hum.... seems that i created a MR to my fork not to Ariadne's git repo https://gitlab.alpinelinux.org/ncopa/secfixes-tracker/-/merge_requests/1 2021-04-22 08:51:14 This merge request is from an internal project to a public project. 2021-04-22 08:51:14 Review the target project before submitting to avoid exposing internal changes. 2021-04-22 08:52:16 ncopa: i can have it create issues :) 2021-04-22 08:56:19 i added an (untested) MR for adding a search in our bugtracker 2021-04-22 08:56:35 might be convenient to search if anyone already reported it 2021-04-22 09:00:52 i can share a bit what the thinking behind the previous, manual, process was 2021-04-22 09:01:30 the URI template looks ok 2021-04-22 09:02:09 the idea was to make sure that as many as possible real vulnerabilities was actually fixed 2021-04-22 09:02:18 yes 2021-04-22 09:02:24 eg reduce the number of unfixed issues as possible 2021-04-22 09:02:43 right now we are in the "teach the system what real vulnerabilities are" stage 2021-04-22 09:02:50 which is why i dont want it to open bugs quite yet 2021-04-22 09:02:58 to achieve that, i wanted to make it as easy as possible to fix them 2021-04-22 09:03:07 ok. i was only wondring if that was on the roadmap or not 2021-04-22 09:03:37 yep, it is, i just don't want to set it loose on the bug tracker until we have mitigations in place for some of these really awful CPE strings 2021-04-22 09:03:46 like cpe:2.3:a:vim_project:vim:*:*:*:*:*:visual_studio_code:*:* for vscodium :) 2021-04-22 09:04:09 right now, it looks at vim_project:vim and goes "ok, this affects vim" 2021-04-22 09:04:20 because somebody at NVD decided it did 2021-04-22 09:05:21 if there was a lot steps involved for the devs to fix them, or if there were many false positives, the fear was that the devs would not care in the end 2021-04-22 09:05:41 yep 2021-04-22 09:05:53 the goal is to keep the workflow exactly the same 2021-04-22 09:06:01 e.g. patch bug, put it in secfixes 2021-04-22 09:06:26 that is also why we added the secfixes in the APKBUILD, because the dev would need to go in there to bump the version anyway 2021-04-22 09:06:27 secfixes-exclude was supposed to be a way to allow maintainers to reject CVEs 2021-04-22 09:06:35 so less resistance to update the "db" 2021-04-22 09:06:52 brb... 2021-04-22 09:18:49 what is secfixes-exclude? i previously thought that setting version '0' as the fixed version to be "exclude" 2021-04-22 09:19:48 to keep things simple 2021-04-22 09:20:12 that approach also works :) 2021-04-22 09:21:26 however, i am looking at some of these CPE nodes in the NVD feed and i think i might be able to clean some of this up heuristically 2021-04-22 09:21:36 for example mosquitto 2021-04-22 09:21:56 good 2021-04-22 09:21:56 we are given a CPE that matches all versions, but there is an additional annotation in the JSON 2021-04-22 09:22:11 so i am going to pull the annotations from the JSON if available 2021-04-22 09:22:17 instead of depending on the CPE version field 2021-04-22 09:22:36 sorry if i sound a bit grumpy. changes are always hard. i think we are on right track with security.a.o 2021-04-22 09:22:52 and thank you for taking care of organizing a security response team 2021-04-22 09:28:14 beats porting alpine to weird machines :p 2021-04-22 09:28:36 we need to talk about riscv though 2021-04-22 09:28:44 people want the port, but the builder situation is, well 2021-04-22 09:28:47 not good :D 2021-04-22 09:29:11 i think we should just hold our nose and use qemu-user on a threadripper 2021-04-22 09:29:13 is qemu 'good enough' 2021-04-22 09:29:22 ah 2021-04-22 09:29:31 mps: for riscv, i think so, considering riscv foundation says it is a reference simulator 2021-04-22 09:29:54 however i am a bit skeptical of course 2021-04-22 09:30:00 I'm interested in risc-v 2021-04-22 09:30:16 when i was bootstrapping the mips64 port, i found that qemu would hang in cases where real hardware would not 2021-04-22 09:30:18 but for now I can only try with qemu 2021-04-22 09:31:05 and best machine I have is i7 with 8GB ram 2021-04-22 09:31:10 not much 2021-04-22 09:31:16 random quirkiness with s390x on qemu is also a thing 2021-04-22 09:31:34 which is why i asked that java bug reporter yesterday if they were running on qemu 2021-04-22 09:31:52 but for riscv i guess it is "production quality" 2021-04-22 09:31:59 I just would like to get some feeling about risc-v, even if it is emulator 2021-04-22 09:33:21 kernel 5.13 will have some improvements for risc-v, would be nice if we can test it 2021-04-22 09:33:28 ncopa: anyway i appreciate alicha's work on this 2021-04-22 09:33:41 hopefully they are not too miffed 2021-04-22 09:33:55 btw, I always wonder is alicha real person or bot 2021-04-22 09:34:28 no comment! 2021-04-22 09:34:42 i mean i did get to the bottom of that 2021-04-22 09:34:42 hmm? 2021-04-22 09:35:04 it is a person related to an alpine developer, but they choose to remain anonymous 2021-04-22 09:35:14 so i am not going to say who it is, though i do know :) 2021-04-22 09:35:18 ah, thanks for explanation 2021-04-22 09:35:43 I can only guess 2021-04-22 09:36:14 it is also a pseudonym 2021-04-22 09:36:43 my brain pointed me to .... :) 2021-04-22 09:39:30 testing things out with these annotations 2021-04-22 09:41:34 this apkindex parser is so slow :( 2021-04-22 09:41:48 i should figure out how to hook into libapk 2021-04-22 09:42:04 as i do for version compare 2021-04-22 09:43:00 i should also mark all packages in a given repo as unpublished before crawling the APKINDEX data 2021-04-22 09:43:16 e.g. https://security.alpinelinux.org/vuln/CVE-2021-20272 is fixed 2021-04-22 09:43:33 but 3.0.31-r0 is still marked "published" 2021-04-22 09:43:39 so the branch is "vulnerable" 2021-04-22 10:30:30 okay i think i got our false positive rate down to something realistic 2021-04-22 10:31:07 Let me know if I should deploy something 2021-04-22 10:33:31 th boltcms issue needs a rewrite rule (which is a config thing) 2021-04-22 10:51:13 clandmeter: when you have time, can we look at the new mirror setup? 2021-04-22 11:12:53 Ariadne: what was the reason '"jenkins:*": lambda x: "jenkins",' again? 2021-04-22 11:13:22 are those plugins all belonging to jenkins? 2021-04-22 11:16:28 yes 2021-04-22 11:16:48 after config changes, should any jobs be run? 2021-04-22 11:16:49 same for boltcms:* 2021-04-22 11:16:50 update-states? 2021-04-22 11:17:13 yes 2021-04-22 11:17:23 you'll have to rebuild the DB 2021-04-22 11:17:37 because the rewrite happens when the match rules are created 2021-04-22 11:17:40 right 2021-04-22 11:17:51 i would wait a bit, i am about to cut 0.3 2021-04-22 11:17:56 which improves a lot 2021-04-22 11:17:58 ok 2021-04-22 11:18:13 I'm currently adding all config in the docker/secfixes-tracker project 2021-04-22 11:18:42 yeah anything where an override is appropriate should go there 2021-04-22 11:18:44 imo 2021-04-22 11:18:49 Ariadne: thinking about it, we maybe also need a way / audit things that do not match 2021-04-22 11:19:21 problem is, not much i can do about situation where 2 different projects use same name 2021-04-22 11:19:36 other than rewrite one 2021-04-22 11:19:37 :) 2021-04-22 11:19:41 just like aports 2021-04-22 11:19:48 yeah, nod 2021-04-22 11:19:56 repology has tons of rewrites 2021-04-22 11:21:27 0.3 shows the CPE rule that was supplied to us 2021-04-22 11:21:33 aha, nice 2021-04-22 11:21:38 so it should make configuring the rewrites a lot easier :) 2021-04-22 11:22:40 a tool to remove stale matchers is something we should add 2021-04-22 11:22:48 but i haven't the slightest idea how to do that yet 2021-04-22 11:23:34 Ariadne: https://gitlab.alpinelinux.org/alpine/infra/docker/secfixes-tracker/-/compare/master...config-in-repo 2021-04-22 11:23:53 have to go now 2021-04-22 11:25:13 yep 2021-04-22 11:25:15 looks good 2021-04-22 11:28:57 ikke: just pushed 0.3 whenever you wanna rebuild the DB :p 2021-04-22 16:22:42 Ariadne: 0.3 is deployed 2021-04-22 16:24:20 i think things look pretty good 2021-04-22 16:24:49 2021 is still importing 2021-04-22 16:25:42 ah :) 2021-04-22 16:29:09 done 2021-04-22 16:29:53 0 false positives in main :) 2021-04-22 16:30:03 :) 2021-04-22 20:33:37 I've added 3.11 and 3.10 repos as well 2021-04-23 08:28:06 morning! 2021-04-23 08:28:22 im moving machines from usa4 to usa9 now 2021-04-23 08:28:28 starting with build-edge-armv7 2021-04-23 08:32:04 where will be arm developors lxcs after this 2021-04-23 08:37:40 i was thinking the build-3* after edge, but i can move the *-mos first if you prefer 2021-04-23 08:42:18 no, do how you planed. I'm not in a hurry, just curious 2021-04-23 10:28:56 Hello everyone, I have a "GreyXor" account on alpine's gitlab. I created this account not with the email but with the association of my gitlab.com account. but now I deleted and recreated a new gitlab account, I'm afraid that my greyxor account of alpine is not available anymore. can you help me with this case? 2021-04-23 10:30:45 GreyXor: hello 2021-04-23 10:31:52 ikke hello, it is this account : https://gitlab.alpinelinux.org/greyxor 2021-04-23 10:32:00 There is an e-mail address associated with that account 2021-04-23 10:32:47 I created it by associating it with my gitlab.com account. but I have since deleted and recreated my gitlab.com account. so I'm afraid it will be a problem and I want to keep my name "GreyXor" on the alpine gitlab 2021-04-23 10:32:57 Right 2021-04-23 10:33:28 What can i do ? To be sure to recover access ? maybe you can delete account and i just recreate it ? 2021-04-23 10:35:23 I sent an e-mail to you 2021-04-23 10:37:37 I send you the token via /msg 2021-04-23 10:38:02 For some reason I did not receive it 2021-04-23 15:16:38 Ariadne: https://gitlab.alpinelinux.org/alpine/infra/gitlab-tf/-/merge_requests/1 2021-04-23 16:26:43 seems like something is happening with the ppc64le host 2021-04-23 16:27:02 maybe the openjdk13 build made it catch fire... 2021-04-23 16:27:06 hmm 2021-04-23 16:27:36 seems to happen every once in a while 2021-04-23 16:27:50 ncopa: btw, I think we should be able to use cgroups to limit a container to a certain numa domain 2021-04-23 16:27:59 oh cool 2021-04-23 16:28:28 but that also means no container gets more than 80 cores.... 2021-04-23 16:28:46 which is kind of what we want, not? 2021-04-23 16:28:52 i guess 2021-04-23 16:28:57 using more adds little more 2021-04-23 16:29:13 the idea is that it's very expensive to switch numa domains 2021-04-23 16:30:02 "The “cpuset” controller provides a mechanism for constraining the CPU and memory node placement of tasks to only the resources specified in the cpuset interface files in a task’s current cgroup. This is especially valuable on large NUMA systems where placing jobs on properly sized subsets of the systems with careful processor and memory placement to reduce cross-node memory access and contention can improve overall system performance." 2021-04-23 16:30:04 https://www.kernel.org/doc/html/v5.4/admin-guide/cgroup-v2.html 2021-04-23 16:31:55 guess that is what we want 2021-04-23 16:32:43 I guess we do not have oob access to the ppc64le builder? 2021-04-23 16:33:00 not that i know 2021-04-23 16:33:04 ok 2021-04-23 16:33:21 im not even sure who is our contact in ibm either anymore 2021-04-23 16:33:25 I'm heading out now, it's nice weather 2021-04-23 16:33:31 enjoy! 2021-04-23 16:45:43 ikke: sick :) 2021-04-23 17:07:37 Ariadne: idea is that people can make merge requests against that repo 2021-04-23 17:07:55 i like it 2021-04-23 17:08:08 so if somebody wants to add somebody to a team 2021-04-23 17:08:12 just a MR 2021-04-23 17:08:13 they just open an MR 2021-04-23 17:08:26 hmm, and that makes nominating developers an open process too :) 2021-04-23 17:08:31 yes 2021-04-23 17:21:24 arm lxcs from usa4 are moved? 2021-04-23 17:43:59 mps: yes 2021-04-23 17:44:40 oh, sorry, usa4 not yet 2021-04-23 17:44:47 at least, not the dev containers 2021-04-23 17:58:50 i tagged secfixes-tracker 0.3.1 with some minor tweaks to the reports 2021-04-23 17:59:08 i think we will be able to test gitlab monday :) 2021-04-23 18:01:45 ikke: I can't access them 2021-04-23 18:02:27 seems like ncopa was still working on it, they are stopped 2021-04-23 18:02:39 aha, ok 2021-04-23 18:04:31 i assume that people are largely happy with the format of the bug reports alicha used to file, right? 2021-04-23 18:10:26 mps: you should be able to reach your containers on usa9-dev1.alpinelinux.org ports 22110 22111 2021-04-23 18:24:43 ncopa: lxc.cgroup.cpuset.cpus = 0-79 in the container config seems to work 2021-04-23 18:24:56 ikke: thanks, lets check 2021-04-23 18:25:04 physcpubind: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 2021-04-23 18:25:06 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 7 2021-04-23 18:25:08 8 79 2021-04-23 18:28:49 ikke: ssh hangs on 'debug1: Connecting to usa9-dev1.alpinelinux.org [147.75.35.197] port 22111' 2021-04-23 18:29:08 Hmm, let's see 2021-04-23 19:01:09 ikke: this terraform stuff looks pretty great 2021-04-23 19:01:17 i'll write up some docs for it 2021-04-23 19:01:20 yeah 2021-04-23 19:01:40 it's conceptually quite simple 2021-04-23 19:04:30 configuration-defined governance :) 2021-04-23 19:05:25 yeah, I saw your twee 2021-04-23 19:05:28 t 2021-04-23 19:05:37 programming by configuring 2021-04-23 19:06:17 i mean, we're not quite there, but this gets us pretty close 2021-04-23 19:07:55 literally being able to nominate new developers through an MR is a big fucking deal though 2021-04-23 19:13:44 mps: can you try again? 2021-04-23 19:15:53 ikke: same result 2021-04-23 19:17:16 anoying, in htop, our new builder, when I switch to tree mode, I suddenly only see the processes of one container, the processes of other containers disappear 2021-04-23 19:18:43 weird 2021-04-23 19:19:01 yes 2021-04-23 19:43:36 mps: I guess ncopa needs to look at it 2021-04-23 19:43:46 I cannot find where the traffic is blocked 2021-04-23 19:44:31 ikke: ok, thanks for trying 2021-04-23 19:56:30 Ariadne: https://gitlab.alpinelinux.org/groups/team/security/-/group_members :) 2021-04-23 20:58:22 mps. sorry i moved it 2021-04-23 20:59:05 ncopa: portforwarding is not working for some reason 2021-04-23 20:59:47 ikke: did you start them all? 2021-04-23 20:59:58 no, just those from mps 2021-04-23 21:00:28 ok 2021-04-23 21:03:28 I've alreayd started setting numa settings for some builders 2021-04-23 21:03:33 ok good 2021-04-23 21:03:50 i've started the rest now i think 2021-04-23 21:04:06 now its only the qemu vms left to move 2021-04-23 21:04:29 i guess we should at some point also try reboot it to see that all containers comes up as expected 2021-04-23 21:04:33 but not today 2021-04-23 21:04:35 right 2021-04-23 21:04:59 ncopa: we need some way to devide the different containers over the 2 CPUs' 2021-04-23 21:05:43 no opinion there 2021-04-23 21:05:59 we could do 64 bit vs 32 bit, but we have both armv7 and armhf 2021-04-23 21:06:14 or we coudl do build-* vs dev boxes 2021-04-23 21:06:17 and htop is acting strange on this host when I switch to tree view :( 2021-04-23 21:06:30 or odd/even on ip addr 2021-04-23 21:07:51 ok? strange how? 2021-04-23 21:08:14 normal view, I see processes for all countainers 2021-04-23 21:08:24 in tree-view, only one container remains 2021-04-23 21:08:45 Missing lots of processes 2021-04-23 21:09:15 indeed. interesting 2021-04-23 21:11:47 im going to bed. have a nice weekend! 2021-04-23 21:11:59 o/ 2021-04-23 21:13:26 ncopa: ikke: np, no hurries 2021-04-24 07:33:56 ppc64le host is still awol 2021-04-24 13:57:30 Ariadne: what do we need for alpineconf, maybe we can host it ourselves? 2021-04-24 14:26:18 i was hoping to use bigbluebutton, since it allows for people to just jump in and ask questions 2021-04-24 14:26:24 but we could use jitsi or something else 2021-04-24 14:26:40 bigbluebutton is the nicest one i've seen, and its just some java application 2021-04-24 14:27:37 the other thing is, we do need to plan for some reasonably large amount of viewers 2021-04-24 14:27:47 which consumes bandwidth 2021-04-24 14:28:02 i have friends at CCC, i am considering asking them to see if they could help us with this 2021-04-24 14:28:21 they have all of this already set up :) 2021-04-24 14:28:39 right, makes sense 2021-04-24 14:29:03 fosshost got scared when i said we might have 3000+ viewers at any time 2021-04-24 14:29:19 (i don't know if we will have that much, but for capacity planning you want to overshoot, not undershoot) 2021-04-24 15:09:08 ikke: Hej, just tagged a first release of aports-qa-bot. I think you mentioned that we could tag the docker images with the tag of aports-qa-bot so we could rollback in case things go wrong, not sure where to start with that though 2021-04-24 15:12:07 If you create a tag in the repo, it will push a tagged image with that version 2021-04-24 15:16:05 Ah, so I just create the same tag in the docker repo and it should just work? 2021-04-24 15:20:38 https://gitlab.alpinelinux.org/alpine/infra/docker/aports-qa-bot/-/jobs/378917 2021-04-24 15:20:49 > Please specify $DOCKER_PASSWORD 2021-04-24 15:20:55 I guess the repo is missing a secret? 2021-04-24 15:22:25 are you doing it in a fork? 2021-04-24 15:22:54 No, I pushed directly to that repo 2021-04-24 15:23:05 https://gitlab.alpinelinux.org/alpine/infra/docker/aports-qa-bot/-/commits/0.1.0 2021-04-24 15:46:44 ah, tags need to be protected 2021-04-24 15:49:53 Cogitri: now it works 2021-04-24 15:50:24 Created manifest list docker.io/alpinelinux/aports-qa-bot:0.1.0 2021-04-24 15:55:13 Oh great, thanks :) 2021-04-24 15:57:02 Maybe you could pull the compose too, adjust the config and restart the bot? 2021-04-24 15:57:57 Instead of a DryRun: true it now has per-action toggles for Disabled/DryRun/Enabled 2021-04-24 15:58:27 With the new release the auto maintainer thingie and cancelling MR pipelines when a MR is merged/closed was added, maybe you could set those to DryRun and the rest to Enabled 2021-04-24 16:00:44 Cogitri: should I now use the tagged version? 2021-04-24 16:01:04 or just latest? 2021-04-24 16:03:20 Yup 2021-04-24 16:03:26 Yup to tagged version :) 2021-04-24 16:03:33 We'll use tags now for future releases 2021-04-24 16:03:56 ok 2021-04-24 16:05:50 Ok, updated 2021-04-24 16:10:37 Thanks :) 2021-04-24 16:11:10 I guess we can take a look at the logs tomorrow to check that the new features behave in dry run and then enable them too 2021-04-24 16:14:29 I had AutoCancel set to enabled (changed it now) 2021-04-24 16:14:35 2021/04/24 16:10:13 Couldn't cancel MR pipeline due to error POST https://gitlab.alpinelinux.org/api/v4/projects/1/pipelines/79955/cancel: 404 {message: 404 Not found} 2021-04-24 16:18:16 Cogitri: You might have received another mention about the mentors group, I accidentaly removed it (yay automation :P) 2021-04-24 16:25:20 Oh yes, wondered what that was about already :D 2021-04-24 16:25:47 ikke: Oh, thanks for the notification, maybe AutoCancel needs more work to work with forks, I had hoped it'd work as-is 2021-04-24 17:46:41 clandmeter: upgraded gbr2-dev1 to alpine 3.13 2021-04-24 18:02:11 fwiw i think danieli should be added to the security team if he wishes to be 2021-04-24 18:03:04 btw, there is also #alpine-security 2021-04-24 18:07:26 Ariadne: feel free to open an MR :P 2021-04-24 18:08:00 he should really be in on this if he wants to be 2021-04-24 18:08:06 yes 2021-04-24 18:08:07 he did try to make this happen sooner, afte all 2021-04-24 18:08:14 But not sure if he has the time 2021-04-24 18:09:36 well he can be honorarily involved :D 2021-04-24 18:34:12 Ariadne: I'm not sure I have the trust from the community or developers after being out of the picture for so long, but I'll gladly help out wherever I can 2021-04-24 18:34:33 I'd recommend joining ##distro-security, it can be a nice forum to discuss overarching issues and ask for input 2021-04-24 18:36:49 well, i trust you :p 2021-04-24 18:37:00 that should count for something 2021-04-24 18:37:40 I suppose, I just want to help improving things and make alpine better 2021-04-24 18:39:13 I still could use help with alpine infra, especially now that clandmeter is quite busy 2021-04-24 18:39:21 (which is also sucurity related) 2021-04-24 18:39:55 fair enough, i have a lot on my plate at work, but it's not nearly as draining as my last dayjob 2021-04-24 18:40:16 are there any major changes worth mentioning since the last time i was actively involved? 2021-04-24 18:40:28 I pop by and read the backlog a few times a week but it's not fresh in memory 2021-04-24 18:41:24 No major changes 2021-04-24 18:41:45 just stuff moving around, changing names, new versions? 2021-04-24 18:41:52 started to use terraform to manage things in applications 2021-04-24 18:41:55 yes 2021-04-24 18:42:06 did you ever get the time to delve into ansible? 2021-04-24 18:42:11 or are you thinking of using terraform instead 2021-04-24 18:42:29 terraform does not handle the OS layer 2021-04-24 18:43:41 clandmeter set something up with ansible in gitlab 2021-04-24 18:48:25 danieli: do you still have access to netbox? 2021-04-24 18:48:50 I used to, but I gave clandmeter a list of all my alpine accounts around the time I left so they could be disabled 2021-04-24 18:48:57 the VPN profile has probably expired long ago 2021-04-24 18:51:54 I have gitlab, linode, mediawiki, netbox, patchwork, redmine, the lounge and zabbix listed in my password manager under the 'alpine' folder 2021-04-24 18:52:05 lately I have been slowly upgrading our infra 2021-04-24 18:52:13 many hosts were still alpine 3.10/11 2021-04-24 18:52:34 focusing more on upgrading the OS or the software? 2021-04-24 18:52:37 OS 2021-04-24 18:52:46 and keeping gitlab up-to-date 2021-04-24 18:52:52 netbox has been upgraded 2021-04-24 19:02:12 well, we are building a whole new chapter for the project imo 2021-04-24 19:19:13 so much great stuff happening lately :D 2021-04-24 19:19:37 heh 2021-04-24 19:23:30 danieli: what is your gitlab username 2021-04-24 19:23:37 i'mma try this out 2021-04-24 19:24:19 @daniel 2021-04-24 19:24:23 Ariadne: iirc @daniel 2021-04-24 19:24:29 i registered pretty early on 2021-04-24 19:24:41 yes it is 2021-04-24 19:42:01 Ariadne: fyi, CI is still a bit of an issue, because it requires credentials 2021-04-24 19:42:23 yeah obviously we don't want to have it go and like 2021-04-24 19:42:28 do the thing 2021-04-24 19:42:38 based on some random idiot (me) opening an MR 2021-04-24 19:42:40 :D 2021-04-24 19:43:00 Right, but it would nice to be able to see the plan (ie, the changes it would do) 2021-04-24 19:43:08 but even for the plan, you need full access 2021-04-24 19:43:37 anyway i opened an MR 2021-04-24 19:43:40 to do the thing 2021-04-24 19:44:01 nod 2021-04-24 20:19:36 ikke: i just moved places :) 2021-04-24 20:19:46 aha 2021-04-24 20:19:49 so i think i will have some more time 2021-04-24 20:19:58 we can look at the mirror setup 2021-04-24 20:20:05 but not today :) 2021-04-24 20:23:21 clandmeter: fyi, the ppc64le builder is awol 2021-04-24 20:23:29 No response yet from ibm 2021-04-24 20:23:36 I saw your email 2021-04-24 20:33:30 clandmeter: do you mind generating a new cert for daniel? 2021-04-24 20:33:47 ovpn? 2021-04-24 20:33:49 yes 2021-04-24 20:33:56 yes i can do that tmomorrow 2021-04-24 20:34:00 im going to bed 2021-04-24 20:34:04 sure 2021-04-24 20:34:08 bit tired after moving 2021-04-24 20:34:12 no hurry 2021-04-24 20:46:44 Ariadne: fyi, the scraping of secdb@git.a.o is still going on 2021-04-24 20:46:59 replace with rickroll.mp4 2021-04-24 20:47:00 tbh 2021-04-24 20:47:14 We return http 429 atm 2021-04-24 20:47:37 Ariadne: does http4s-blaze 2021-04-24 20:47:40 user agent 2021-04-24 20:47:48 ring any bell? 2021-04-24 20:51:11 nope 2021-04-24 20:51:14 k 2021-04-24 20:51:27 https://github.com/http4s/blaze 2021-04-24 20:51:35 seems to be some java shite 2021-04-24 20:51:47 yeah, but a generic library 2021-04-24 20:51:50 so could be anythign 2021-04-24 21:23:16 clandmeter: congrats on the nwe place then :) 2021-04-24 21:39:03 ikke: any ip blocks? 2021-04-24 21:39:14 comes from all over the world 2021-04-24 21:40:24 wtf URIs do they fetch? 2021-04-24 21:40:31 i dont even see secdb on cgit anymore 2021-04-24 21:40:49 this must be some garbage tier security scanner 2021-04-24 21:40:51 Oh, it's not secdb actually 2021-04-24 21:41:05 "GET /aports/log/?ofs=103500 HTTP/1.1 2021-04-24 21:47:00 Ariadne: seems like they do respond to 429 now 2021-04-25 06:12:23 danieli: thx 2021-04-25 06:43:28 ikke: :D 2021-04-25 06:46:07 cpu usage of that host dropped significantly 2021-04-25 07:14:07 which host 2021-04-25 07:14:58 that hosts cgit (deu1) 2021-04-25 07:15:11 ah 2021-04-25 07:16:27 and apparently they scrape that for a list of recent commits I guess? 2021-04-25 07:16:34 which, in bulk, is quite costly 2021-04-25 07:17:10 /cgit/aports/log/?qt=grep&q=cve&showmsg=1 2021-04-25 07:17:34 Well, they don't get any of that anymore 2021-04-26 06:28:19 so the ppc64le machine hasn't returned. Do we know who to contact at IBM? 2021-04-26 06:28:43 I have an email from august 2020 i could try 2021-04-26 06:29:28 I think ikke tried by mail 2021-04-26 06:33:51 ah, good i found it now - after i knew what to search for :) 2021-04-26 06:43:35 ncopa: my arm lxcs are not accessible, ssh hangs on this msg: debug1: Connecting to usa9-dev1.alpinelinux.org [147.75.35.197] port 22110 2021-04-26 06:43:49 when you find time, no hurries 2021-04-26 07:11:04 oh, ok. i wonder if you have vpn access? 2021-04-26 07:12:18 yes, I have 2021-04-26 07:12:32 but also didn't worked 2021-04-26 07:14:31 mps-edge-aarch64.usa9.alpin.pw 2021-04-26 07:15:24 ssh: Could not resolve hostname mps-edge-aarch64.usa9.alpin.pw: Name does not resolve 2021-04-26 07:15:48 I don't use alpin.pw resolver 2021-04-26 07:16:08 172.16.23.110 2021-04-26 07:16:16 And 111 2021-04-26 07:17:02 it ask password 'mps@172.16.23.110's password:' 2021-04-26 07:20:29 ikke: I connected to one 2021-04-26 07:20:39 logged in, i mean 2021-04-26 07:21:04 had to change IP aliases for new ip addresses 2021-04-26 07:21:33 though I swapped them :) 2021-04-26 07:25:06 both 'works' now. thank you both :) 2021-04-26 07:32:10 512GB RAM? :) 2021-04-26 07:33:53 and first 'Illegal instruction', trying to run cpufetch ;) 2021-04-26 07:37:16 160 CPUs, huhu 2021-04-26 08:45:06 what cpu number we should use in abuild.conf on this machine? 2021-04-26 08:45:35 64? :) 2021-04-26 08:48:39 5 min to build kernel!? aiee! :) 2021-04-26 08:49:20 I need to write praise letter to those who gave this machine to alpine 2021-04-26 08:56:23 mps: send email to arm :) 2021-04-26 08:57:13 is it from arm company? 2021-04-26 08:57:34 I mean, they 'donated' it to alpine? 2021-04-26 08:59:06 hehe, they have to write praise letter to me^Wall of us because we work hard for distro to run very good on arm 2021-04-26 08:59:11 arm supports the community yes 2021-04-26 08:59:40 previously it was WoA program, not sure its still the same. 2021-04-26 09:10:22 mps: we will limit your container to a single cpu 2021-04-26 09:10:39 (80 cores) 2021-04-26 09:11:51 ikke: iiuc I can set 80 in abuild.conf ;) 2021-04-26 09:13:05 Yes, but we do this for performance reasons. They recommend limiting applications to a single NUMA domain 2021-04-26 09:20:18 for me 16 is usually ok, maybe sometimes 32 will help, don't need so much cpus 2021-04-26 09:20:53 anyway thanks for generosity 2021-04-26 09:22:06 Yes, you can still do that 2021-04-26 09:22:45 mps: thanks for helping with alpine! hopefully the new machine will make your alpine work more fun :) 2021-04-26 09:23:45 and don´t be afraid of using cpu cores, specially if the builders are idle 2021-04-26 09:23:58 fun is a bonus, usability and quality are main incetive 2021-04-26 09:24:24 ah, builders are there also 2021-04-26 09:24:34 everythign is there now 2021-04-26 09:24:45 well, not CI - yet 2021-04-26 09:24:57 good to know to be 'kind citizen' 2021-04-26 09:25:06 appreciate that 2021-04-26 09:25:49 but now, breakfast is waiting ;) 2021-04-26 09:26:00 but please dont be afraid of doing 5min kernel builds. no need to restrict to 32 cores for that 2021-04-26 09:26:23 5 min was with -j16 2021-04-26 09:26:41 try -j80 or something 2021-04-26 09:26:57 sure, but breakfast is waiting 2021-04-26 09:27:04 enjoy! 2021-04-26 09:27:10 thaks 2021-04-26 12:12:28 [00:28:18] so the ppc64le machine hasn't returned. Do we know who to contact at IBM? 2021-04-26 12:12:52 worst case scenario, i can get my power8 machine back up 2021-04-26 12:14:23 i presently have it powered down because it's at equinix and i don't want to pay for additional power there, but i can have somebody it move it to my main colo 2021-04-26 12:14:53 the only ppc64 machine i have up right now is my blackbird because its low power 2021-04-26 12:15:07 but thats only quad coree 2021-04-26 12:31:56 We just got a reply, they're looking into it 2021-04-26 13:16:10 also if we need s390x backup, i can do that too 2021-04-26 13:16:29 i'm confident in the stability of my frankenframe 2021-04-26 13:16:30 ;) 2021-04-26 13:49:47 useslove onereer 2021-04-26 13:58:34 ? 2021-04-26 14:14:59 sounds like PICCORO needs to change password :) 2021-04-26 14:16:41 probably 2021-04-26 14:26:52 XD XD XD .. ncopa is ther pidgin notification.. it raised the windo and i typed XD XD XD 2021-04-26 14:29:33 Ariadne ncopa the pidgin client where I have centralized everything including telegram is raised each notification their own window 2021-04-26 14:29:33 because IRC protocol sends too many messages of everything, making me write in the channel, I have already deactivated the notifications XD XD ... I had not done it because I was lazy. 2021-04-26 14:41:18 you are not the first one... :) 2021-04-26 15:03:27 They need to physically access the ppc64le machine 2021-04-26 15:32:28 mps ncopa ikke still there's no way to autodetect the default kernel of a brand/release of alpine? 2021-04-26 15:33:05 at the packagin build time? 2021-04-26 15:33:33 Look at how other kernel module packages are built 2021-04-26 15:34:57 For example, zfs-lts 2021-04-26 15:38:08 thanks ikke 2021-04-26 17:34:15 https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/21 for whoever wants to deal with that :) 2021-04-26 20:09:51 ikke: Pushed new aports-qa-bot release (0.1.1), could you pull the new image and restart the bot please? :) 2021-04-26 20:10:00 In a bit 2021-04-26 20:28:49 Sure, thanks for looking into it :) 2021-04-26 20:33:43 Cogitri: I'm maybe missing something, but docker-compose says the container is up-to-date 2021-04-26 20:34:20 Oh, maybe some arch isn't done building the container yet, and as such it didn't upload it yet, sorry 2021-04-26 20:35:15 Started the build at 10pm (so 30 minutes ago) and just assumed it'd be finished by now - I guess 0.1.1 should show up tomorrow then. No need to update it immediately anyway, I suppose :) 2021-04-27 08:59:39 ikke: I think 0.1.1 should be tagged now on dockerhub 2021-04-27 10:39:44 Also, I was looking into the artifacts downloading API for the bot (for commenting changed files/sonames) and it seems like we have the choice between either downloading the entire archive or only downloading a single file whose name we already know 2021-04-27 10:40:46 Since the checkapk logs are named after the package they checked (so we don't know the name) and gitlab doesn't have API for listing the files in the artifacts we'd have to download the entire archive which would be less than optimal since the included .apks could be huge 2021-04-27 10:41:11 Maybe we can put the checkapk output into another archive which has a predictable name? 2021-04-27 10:41:17 right, that should be possible 2021-04-27 10:41:21 Or just concact all checkapk files together and name it checkapk.log ? 2021-04-27 10:42:54 Cogitri: deployed v0.1.1 2021-04-27 10:44:47 Thanks 👍️ 2021-04-27 10:48:45 Hmm, no log output, I would expect at least something? 2021-04-27 10:54:40 Cogitri: https://gitlab.alpinelinux.org/alpine/infra/compose/aports-qa-bot/-/merge_requests/1 2021-04-27 11:23:41 ikke: Oh, whoops, I think I forgot to add the log info key to the config 2021-04-27 11:24:28 https://gitlab.alpinelinux.org/alpine/infra/compose/aports-qa-bot/-/commit/8929965d7b57ca15fa54c60cef30e09744432121 2021-04-27 11:42:49 OK will add that later 2021-04-27 11:46:09 👍 2021-04-27 11:47:32 Cogitri: so if you want to deploy a new version, you can bump it in that override.yml 2021-04-27 11:47:47 prod.yml 2021-04-27 11:48:13 Oh okie 2021-04-27 17:57:06 clandmeter: for secdb, what is the reason you use nq to run the generate script, rather than running it directly? 2021-04-27 18:03:44 ikke: Btw, have you looked at the configs of the bot? Any errors left? If not, we could enable the services which are currently set to DryRun 2021-04-27 18:04:00 Ah, needed to enable the logs again 2021-04-27 18:04:22 Okie 👍️ 2021-04-27 18:05:35 I've added the loglevel to conf.override.json, but it still does not log 2021-04-27 18:07:23 Huh 2021-04-27 18:07:37 I don't think you need to specify it in the override, should be in the base config now 2021-04-27 18:08:43 right, I pulled now 2021-04-27 18:09:52 Ok, now getting log output again 2021-04-27 18:10:09 Colored output, nice :) 2021-04-27 18:10:26 What library are you using? 2021-04-28 05:23:40 ikke: to prevent it from running multiple times at ones from mqtt i think 2021-04-28 05:26:57 clandmeter: ok, I see 2021-04-28 06:10:23 ikke: Ah, we're using zerolog now, it's pretty nice since it offers structured logging 2021-04-28 06:10:30 Nice that logging works now :) 2021-04-28 08:02:32 ikke: if you can find a nicer way to handle a queue, let me know. 2021-04-28 08:03:44 No, was just thinking about how to get the output of the generate command 2021-04-28 08:04:49 docker and nq does not play that nice with output 2021-04-28 08:04:55 Nod 2021-04-28 08:06:30 i searched high and low for something easy that just outputs to stdout 2021-04-28 08:14:22 But it should also wait until the previous invocation finished 2021-04-28 08:14:45 What about flock? 2021-04-28 08:16:18 you could use flock, but you would mis invocations. 2021-04-28 08:17:04 lets say it runs and you get another run but its locked, it would not run the missing one. you will need to wait for the next one. 2021-04-28 08:17:58 for mirror rsync, i would use flock and run one every hour or so to catch missing ones. 2021-04-28 08:18:19 flock waits until it can get the lock 2021-04-28 08:20:53 what happens of multiple flocks are waiting? 2021-04-28 08:20:58 if 2021-04-28 08:21:25 I think the order is not defined 2021-04-28 08:23:37 if you think just using flock will work, please go ahead and change it. 2021-04-28 17:21:57 Cogitri: I've enabled the remaining options 2021-04-28 18:28:26 ikke: Nice, let's hope nothing blows up (but I'm fairly sure that it'll be fine :) 2021-04-28 18:34:49 Cogitri: I guess this can be closed now / soon: https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10691 2021-04-28 18:41:10 Yup, maybe we'll want to wait a day or so and see if it works nicely 2021-04-28 18:42:25 fine with me 2021-04-29 07:24:52 ikke: Seems like automaintainer doesn't quite work yet, could you fetch the logs so we can work on fixing it? Maybe something in the email search doesn't work yet since we can't test that without admin permissions 2021-04-29 07:25:02 ikke: git gets hammered again? 2021-04-29 08:53:05 Ah, we found the bug in aports-qa-bot, there's a 0.1.2 release now which should fix it. 2021-04-29 11:22:06 sigh 2021-04-29 11:23:15 restart uwsgi, should make it stable again 2021-04-29 11:25:56 what is the cause? 2021-04-29 15:24:28 clandmeter: Not sure, but every so often uwsi starts becoming unstable and does not respond to requests 2021-04-29 19:57:10 ikke: Have you looked into updating the bot already? :) 2021-04-29 19:57:36 Cogitri: no, thanks for reminding me 2021-04-29 19:59:28 done 2021-04-29 20:03:12 Thanks 👍 2021-04-30 04:45:53 Cogitri: ERR Failed to assign maintainer error="author and maintainer are the same" MR=20990 Project=1 component="MergeRequestJob Processor" service=AutoMaintainer 2021-04-30 06:50:36 ikke: what do you want to do with those mirrors? 2021-04-30 06:51:09 Which? 2021-04-30 06:51:39 you mention me few days ago 2021-04-30 06:52:12 I guess we need to finish the distributed mirror setup? 2021-04-30 06:52:23 we need to finish many things :) 2021-04-30 06:52:37 Yes, but that as well 2021-04-30 06:52:44 nod 2021-04-30 06:52:53 should be simple i think to finish up 2021-04-30 06:53:05 and we need to finish the arm server part 2021-04-30 06:53:11 i think they will sh ortly msg us again 2021-04-30 06:54:31 Cpu usage is still not good I think 2021-04-30 06:55:37 ikke: Oh, I suppose we should downgrade that message to INFO, it's not really an error, it's just unnecessary to assign the author to the MR 2021-04-30 06:55:53 Cogitri: I suspected as much 2021-04-30 08:18:52 im gonna send a ping to the ppc64le ppl 2021-04-30 12:10:01 Oof, hardware failure 2021-04-30 12:43:19 do i need to get my POWER8 machine up? 2021-04-30 12:45:52 though if i do, that's going to suck 2021-04-30 12:46:00 since i guess we would have to rebuild all of edge 2021-04-30 13:28:48 anyone seen the mips64 machine recently? it also seems to be missing 2021-04-30 13:29:40 i will poke aag about that one 2021-04-30 13:30:33 i am planning to get a replacement ubiquiti edgerouter infinity and put it in my colo 2021-04-30 13:31:10 to replace the sketchy setup we have now for mips64 :) 2021-04-30 13:35:45 i said that a ppc64le vm would be ok, but actually, i think it would be good if we could have a physical machine so we can test alpine in ppc64le vms 2021-04-30 13:35:54 we havent done that so far though 2021-04-30 14:15:10 ikke: ouch 2021-04-30 18:04:22 could a GitLab admin create a cloud sub-group under the alpine project and make mcrute the owner/admin of that? I don't think I have permission to do that 2021-04-30 18:26:18 someone asked me to set up the lists.sr.ht <> gitlab mirror for gitlab.a.o+lists.a.o 2021-04-30 18:26:21 do we want to pick that back up? 2021-04-30 21:01:30 it seems reasonable. i have heard some complaints from users on slow connections (central american users in the unofficial alpine telegram chat) that gitlab is quite painful for them to interact with just to send in a patch