2022-05-01 03:44:42 <psykose> ikke: you broke the hook so bad nobody can merge anything :p
2022-05-01 03:46:35 <psykose> remote: date: invalid date '%Y-%m-%d'; probably missing the +
2022-05-01 05:52:29 <smcavoy> when someone has a chance please let me know what you think of ! 120524
2022-05-01 05:52:39 <smcavoy> !120524
2022-05-01 05:52:58 <ikke> one digit too many
2022-05-01 05:53:30 <smcavoy> ahem... staring at the wrong window.. 
2022-05-01 05:53:32 <smcavoy> !33784
2022-05-01 06:05:40 <ikke> smcavoy: it's still a draft?
2022-05-01 06:10:21 <smcavoy> yes, just wanted to get feedback. specifically on the initd stuff
2022-05-01 06:10:31 <ikke> ok
2022-05-01 06:40:58 <smcavoy> any suggetions on how to use `setcap` with a python script? exabgp would need to listen on 179/tcp
2022-05-01 06:52:48 <ikke> Using setcap is discouraged
2022-05-01 06:53:13 <ikke> But the question is, what is the alternative
2022-05-01 06:54:47 <psykose> can't do that, no
2022-05-01 07:40:18 <smcavoy> oh well..  good enough for now then.
2022-05-01 08:32:21 <ktprogra1> I'm thinking about packaging https://github.com/pop-os/wallpapers. In the README, it states that some of the photos are CC-BY-SA-4.0, while others (from Unsplash) are in the public domain. What should be put in the license field (what to use to refer to public domain)?
2022-05-01 08:44:58 <ikke> https://wiki.spdx.org/view/Legal_Team/Decisions/Dealing_with_Public_Domain_within_SPDX_Files
2022-05-01 09:01:55 <ktprogra1> ikke: I did find that page, although I can't see what the conclusion is. It seems like there isn't any single identifier, so what should be used?
2022-05-01 09:03:39 <ikke> You'd have to look at what exactly is specified and see if there is something that matches 
2022-05-01 09:04:01 <ikke> There is no single public domain declaration 
2022-05-01 09:29:54 <pabloyoyoista> ikke: any chance you can try to see if this: https://gitlab.alpinelinux.org/alpine/infra/docker/appstream-generator/-/merge_requests/4 fixes the permissions in the appstream container?
2022-05-01 11:36:51 <ikke> pabloyoyoista: fyi, I also wanted to check if I can get rid of the umask that causes this in the first place
2022-05-01 12:43:56 <ikke> psykose: fyi, your work-around will no longer work either :)
2022-05-01 12:44:08 <psykose> aware :)
2022-05-01 12:46:10 <ikke> It did check multiple commits, or at least, that was the intention
2022-05-01 12:46:31 <ikke> a premature break prevented thatt
2022-05-01 13:18:58 <Hello71> smcavoy: start the program as root and let it bind and drop privileges
2022-05-01 13:19:06 <Hello71> (check that it actually does drop privileges)
2022-05-01 13:21:58 <Hello71> ktprogra1: i kinda don't understand the point of packaging a large set of wallpapers. why can't you just download it manually? i see two benefits of packaging: one, you get automatic updates. that doesn't seem to apply here; the last update to any file was 5 years ago, except for one new file added 10 months ago. two, you can easily install all of the wallpapers at the same
2022-05-01 13:21:59 <Hello71> time. i guess this could be good if you want to automatically rotate between images. is that common?
2022-05-01 13:22:24 <Hello71> and if so, why can't you just download them as a zip and extract to your home directory?
2022-05-01 13:23:14 <ktprogra1> Hello71: No, I'm only using them on one computer, I just thought that since there's already some wallpapers packaged (although those are part of DEs) it would be okay/good to package these.
2022-05-01 13:23:51 <Hello71> i think packaging one upstream default wallpaper is reasonable
2022-05-01 13:24:15 <Hello71> but packaging a whole set of them which you still have to manually configure just doesn't seem easier than manually downloading and configuring
2022-05-01 13:24:48 <ktprogra1> Hello71: Ok, makes sense.
2022-05-01 17:28:34 <smcavoy> Hello71:  that is what it does now. I will leave that as is. thanks
2022-05-01 19:48:24 <ikke> If you have ideas to add, please do: https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.16.0
2022-05-01 21:24:15 <pabloyoyoista> ikke: Oh thanks, that would be very nice! :)
2022-05-01 21:27:23 <Ermine> There were some changes regarding sudo/doas
2022-05-01 21:30:19 <panekj> only that the sudo was moved to community
2022-05-02 03:46:21 <ktprograms> ikke: Should I mention the initramfs consoles switch fix? It's kinda major for getting OpenRC output on systems which use consoles that are compiled as modules (https://gitlab.alpinelinux.org/alpine/mkinitfs/-/merge_requests/99#note_229398), for example Virtualization.framework on macOS
2022-05-02 12:21:32 <pog> Is it possible to use a gpg key on a yubikey to sign packages with abuild? What would I put in the abuild.conf? 
2022-05-02 12:22:24 <ikke> abuild does not use GPG keys
2022-05-02 12:22:27 <ikke> nor apk
2022-05-02 12:22:40 <ikke> It uses rsa keys
2022-05-02 12:24:25 <pog> Thank you for the reply, forgive my ignorance. My understanding was that I might be able to use my RSA GPG keys on the yubikey for Alpine development, is this possible or am I getting confused here? 
2022-05-02 12:26:15 <a16bitsysop> ikke: how about ceph17 !33752 and postfix add redis support !33818 for 3.16
2022-05-02 12:27:59 <panekj> not possible by default, you would need to modify abuild to sign it with yubi
2022-05-02 12:29:40 <pog> @panekj How might I go about doing that? 
2022-05-02 12:30:33 <psykose> the signatures are made with `openssl dgst -sign thekey.rsa`
2022-05-02 12:30:37 <panekj> git clone https://gitlab.alpinelinux.org/alpine/abuild.git
2022-05-02 12:30:39 <psykose> a gpg key is.. not that
2022-05-02 12:30:56 <panekj> modify abuild-sign to use yubi
2022-05-02 12:34:22 <panekj> also you need to have rsa key in piv
2022-05-02 12:35:27 <pog> I see, won't be possible with my setup then. Thanks for the responses 
2022-05-02 23:18:29 <ashpool> #join alpine-linux
2022-05-03 10:42:46 <tmhoang> I'm pushing to my gitlab repo and got "shallow update not allowed" message. Any idea ? 
2022-05-03 10:43:13 <ikke> Did you clone with --depth?
2022-05-03 10:44:23 <tmhoang> looks like it - do I have to reclone or there is way out of  it ? 
2022-05-03 10:45:16 <ikke> git fetch --unshallow
2022-05-03 10:45:51 <tmhoang> thanks !
2022-05-03 12:10:35 <ncopa> Shiz: I just pushed kernel 3.15.37 to v3.15 branch. with early microvm hvc0 console support for -virt kernel
2022-05-03 12:10:47 <Shiz> \o/
2022-05-03 12:11:31 <ncopa> i  also verified that it works
2022-05-03 12:12:03 <ncopa> $ tpaste < microvm.sh 
2022-05-03 12:12:03 <ncopa> https://tpaste.us/QN04
2022-05-03 12:13:29 <ncopa> boots alpine in ~1 sec
2022-05-03 12:16:26 <ktprograms> ncopa: Will there be a new ISO release with it?
2022-05-03 12:16:42 <ncopa> maybe
2022-05-03 12:17:05 <ncopa> v3.16 will have it as well
2022-05-03 12:17:31 <ncopa> 6c9cbf27cbcbcc459c5453bbb3251a142884225d
2022-05-03 12:18:07 <ncopa> what I find somewhat challenging is that it works so different with arm
2022-05-03 12:22:24 <Shiz> ncopa: i'm not sure that's a sufficient test setup, as microvm by default still has an isa serial port
2022-05-03 12:23:01 <Shiz> afaik you want to at least pass ,isa-serial=off to -machine microvm
2022-05-03 12:23:46 <Shiz> but yay!
2022-05-03 13:23:59 <Piraty> too bad /etc/apk/world doesn't allow comments
2022-05-03 14:08:54 <Cogitri> Piraty: It does allow comments, but they have to be on separate lines
2022-05-03 14:09:19 <ikke> But does apk preserve them?
2022-05-03 14:10:33 <Piraty> apk fix choked on a comment line with #
2022-05-03 14:11:31 <Piraty> but https://git.alpinelinux.org/apk-tools/tree/src/database.c#n1288
2022-05-03 14:12:57 <ikke> That sounds like it's for /etc/apk/protected_paths.d
2022-05-03 14:13:15 <Piraty> yeah i'm looking at it
2022-05-03 16:39:05 <ncopa> I now have a test matrix with 18 different combinations per iso. bios/uefi boot, ext4,xfs,btrfs root fs, sys, crypt/lvmsys
2022-05-03 16:39:21 <ikke> wow, nice
2022-05-03 16:39:28 <ikke> Where are you running it, your own machine?
2022-05-03 16:39:33 <ncopa> yes
2022-05-03 16:39:44 <ncopa> https://github.com/ncopa/alpine-installer-testsuite/blob/main/tests/test_sys_install.py
2022-05-03 16:39:45 <ncopa> qemu
2022-05-03 16:40:11 <ncopa> currently i only test with a single disk
2022-05-03 16:40:20 <ncopa> should probably add a dual disk setup too, 
2022-05-03 16:40:49 <ncopa> and test nvme and maybe virtio
2022-05-03 16:41:45 <ncopa> shoudl work with both x86_64 and x86 isos
2022-05-03 16:42:07 <ncopa> shoudl work with either alpine-virt, alpine-extended and alpine-standard
2022-05-03 16:43:07 <ncopa> i plan to add tests for diskless and datadisks as well
2022-05-03 16:44:43 <ncopa> not sure which is most important: dualdisk/raid, nvme or diskless
2022-05-03 16:45:30 <ikke> nvme is where we have most issues atm (that I'm aware of)
2022-05-03 16:45:38 <ncopa> ok
2022-05-03 16:45:58 <ncopa> i know there are bugs or missing features for crypt combinations also
2022-05-03 16:46:19 <ncopa> i'd like to be able to typ type: 'cryptsys', simlar to how we do 'lvmsys'
2022-05-03 16:46:26 <ncopa> to avoid the second question
2022-05-03 16:53:02 <ncopa> would be nice if we could run them from gitlab-ci when creating release tags (for release candidates)
2022-05-03 16:57:49 <ikke> Yes, certainly
2022-05-03 17:07:41 <ikke> I think time-wise it will be after 3.16, but I can look in what we can deploy in Azure to help with this
2022-05-03 18:26:33 <anjan> not sure why this build is failing https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/28360 but it should be good to go ikke 
2022-05-03 18:28:02 <ikke>  11233 commits behind the target branch
2022-05-03 18:28:05 <ikke> please rebase :)
2022-05-03 18:29:29 <anjan> ikke: re: this https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/28671#note_233215
2022-05-03 18:29:35 <anjan> I used to use cura without building that
2022-05-03 18:29:51 <anjan> can we just put it in as a recipe that users have to "abuild -r" if they want it?
2022-05-03 18:30:43 <anjan> Id rather get that merged sooner rather than later because Ive fixed up that MR multiple times because it became unmergeable because of changes to master
2022-05-03 18:31:24 <anjan> nice, my maim MR builds properly
2022-05-03 18:31:26 <anjan> heh
2022-05-03 18:48:25 <ikke> We used to have non-free, but we decided to drop that (though, this is not even non-free)
2022-05-03 18:53:57 <anjan> ok lmk about your decision. Im ok with either or
2022-05-03 18:56:02 <ikke> anjan: if you want it merged quickly, I would first leave out that package, and then we can think about what to do with that later
2022-05-03 18:56:26 <anjan> ok sounds good. Ill do that tonight sometime
2022-05-03 18:56:33 <anjan> Thanks for advising ikke 
2022-05-03 20:17:19 <ddevault> should hare depend on binutils?
2022-05-03 20:17:33 <ddevault> binutils is part of alpine-sdk, but using hare alone requires binutils
2022-05-03 20:17:43 <ddevault> not sure if alpine-sdk stuff should be in dependencies or not
2022-05-03 20:19:37 <Cogitri> ddevault: It doesn’t hurt to add it, so I‘d say just do it
2022-05-03 20:19:47 <ddevault> ack
2022-05-03 20:20:25 <ikke> There are other packages that depend on binutils
2022-05-03 20:20:29 <ikke> go for example
2022-05-04 07:39:00 <clandmeter> do we have something in alpine that mimics `systemctl reboot --firmware-setup`?
2022-05-04 08:06:03 <ddevault> the pmOS guys may know something about that, since it's fairly common on android devices
2022-05-04 08:06:14 <ddevault> maybe there's some ACPI thing for x86
2022-05-04 08:06:31 <ddevault> I can recommend a good therapist for anyone who dives into ACPI to find out
2022-05-04 08:31:21 <skarnet> that's assuming they go back to the surface alive
2022-05-04 08:34:14 <clandmeter> from what i understand this sets something in efivars 
2022-05-04 08:35:59 <Daanct12> IIRC it might just be a standard linux thing
2022-05-04 08:36:21 <Daanct12> some syscall and then reboot using that syscall would do
2022-05-04 08:36:29 <Daanct12> this is the same thing pmos guys also use
2022-05-04 09:04:35 <clandmeter> https://github.com/systemd/systemd/blob/09541e49ebd17b41482e447dd8194942f39788c0/src/shared/efivars.c#L174
2022-05-04 09:05:39 <ktprogra1> Should I mention the initramfs consoles switch fix in the 3.16 release notes? It's kinda major for getting OpenRC output on systems which use consoles that are compiled as modules (https://gitlab.alpinelinux.org/alpine/mkinitfs/-/merge_requests/99#note_229398), for example Virtualization.framework on macOS.
2022-05-04 09:06:35 <clandmeter> i guess most pmos devices do not use efi firmware, so it must do something else
2022-05-04 09:18:01 <ikke> ktprogra1: feel free to add it. We will look later at what we will include in the release notes published on the website
2022-05-04 09:35:44 <ncopa> nmeum: I'd like to replace the patch for busybox udhcp retries/timeout
2022-05-04 09:36:20 <ncopa> we currently have 5 retries, with 3 seconds delay between (the helptext is currently wrong btw...)
2022-05-04 09:36:37 <ncopa> it means we wait totally 15 seconds
2022-05-04 09:36:43 <ncopa> which I think is good
2022-05-04 09:37:02 <ncopa> but I'd like to change it to 15 retries with 1 sec delay
2022-05-04 09:37:58 <ncopa> reason is that on ip link set dev eth0 up, it takes a second before the link get carrier, so the first try will always fail
2022-05-04 09:38:19 <ncopa> which means that it takes always minimum 3 seconds to get a dhcp lease
2022-05-04 09:39:52 <ncopa> the best thing would be to check for /sys/class/net/eth0/carrier to turn 1 before executing udhcpc (from ifupdown/ifupdown-ng)
2022-05-04 09:41:11 <ncopa> but that requires some sort of ugly hacks in busybox ifupdown *and* ifupdown-ng.
2022-05-04 09:42:16 <ncopa> trivial fix is to patch udhcpc to use default timeout to 1 sec instead of 3. It reduces the time to get a dhcp address from 3 to 1 sec
2022-05-04 09:55:38 <skarnet> ncopa: https://skarnet.org/software/bcnm/bcnm-waitif.html no ugly hacks needed
2022-05-04 09:55:50 <skarnet> notification is a good thing :)
2022-05-04 09:56:35 <skarnet> (I use this in conjunction to ifup when I have services that depend on the existence of an interface)
2022-05-04 09:58:22 <nmeum> ncopa: yes, I would ideally prefer something that could be upstreamed to busybox
2022-05-04 10:00:18 <ncopa> skarnet: yeah, that is the proper way to do it. not sure if its worth to add another dependency when we can tweak the udhcpc defaults
2022-05-04 10:01:21 <skarnet> the idea isn't to add another dependency but to use the same mechanism
2022-05-04 10:01:38 <skarnet> the code isn't huge or difficult, just annoying
2022-05-04 10:04:47 <ncopa> i could not find any way to do that using existing tools
2022-05-04 10:05:58 <skarnet> indeed there isn't, because if there were, I wouldn't have needed to write bcnm-waitif
2022-05-04 10:06:02 <skarnet> :thinking guy meme:
2022-05-04 10:06:57 <skarnet> but I guess you'd rather not try and upstream a 150-line patch to udhcpc
2022-05-04 10:07:07 <skarnet> so, yay more polling, I suppose
2022-05-04 10:08:08 <ncopa> we could add it to ifupdown-ng too
2022-05-04 10:08:44 <skarnet> ifmond will definitely have that mechanism
2022-05-04 11:51:21 <ktprogra1> ikke: Ok, thanks
2022-05-04 12:45:28 <Newbyte> does networkmanager-openrc no longer get pulled in automatically for anyone else?
2022-05-04 12:55:17 <Cogitri> Newbyte: Maybe open an issue and assign jirukta, they recently reworked NM
2022-05-04 13:03:39 <Newbyte> done: #13778
2022-05-04 13:18:26 <ktprograms> ncopa: I just noticed that setting VIRTIO_CONSOLE=y wasn't done for the lts kernels on edge, was that intended?
2022-05-04 13:19:59 <ktprograms> ikke: Is this okay? I couldn't think of any other way to phrase it. https://wiki.alpinelinux.org/w/index.php?title=Release_Notes_for_Alpine_3.16.0#Fixed_not_showing_boot_output_using_consoles_with_drivers_compiled_as_modules
2022-05-04 14:05:31 <ncopa> ktprograms: yes. thats intended. I dont think we want that for lts kernels?
2022-05-04 14:23:55 <ktprograms> ncopa: Isn't it enabled for linux-lts in 3.15?
2022-05-04 14:25:53 <ncopa> no. only for s390x
2022-05-04 14:42:19 <ktprograms> ncopa: This seems to set it for all? https://gitlab.alpinelinux.org/alpine/aports/-/commit/a84cd27a2892cb9207a1fc507247fee053874a5e
2022-05-04 15:03:23 <psykose> that's only virt
2022-05-04 15:24:34 <ncopa> yup, only for virt kernels
2022-05-04 15:24:57 <ncopa> my testsuite already found a couple of bugs in setup alpine
2022-05-04 15:25:16 <ncopa> mdadm on top of nvme woudl not pull in the nvme kernel module in initramfs
2022-05-04 15:26:23 <ikke> nice1
2022-05-04 15:44:08 <Hello71> also luks on nvme
2022-05-04 15:44:26 <Hello71> https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10498
2022-05-04 15:45:13 <Hello71> it works as a special case for lvm
2022-05-04 15:47:06 <ncopa> right
2022-05-04 15:47:33 <ncopa> is there some way to find the underlying device under luks?
2022-05-04 15:47:54 <Hello71> i think these bugs are already mostly known. as i see it, the benefit of a comprehensive test suite is that these bugs can be fixed with less worry of breaking other cases
2022-05-04 15:48:30 <ncopa> yeah
2022-05-04 16:04:15 <donoban> ncopa: 'cryptsetup status /dev/mapper/root' shows the device
2022-05-04 16:40:43 <Hello71> i vaguely recall this was discussed already in irc or issue tracker
2022-05-04 16:45:22 <Hello71> ah, right, setup-disk already gets it
2022-05-04 16:45:36 <Hello71> https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-disk.in#L631
2022-05-04 16:55:59 <ncopa> is lvm on crypt supposed to work?
2022-05-04 16:56:46 <psykose> yes
2022-05-04 17:24:23 <ncopa> i now have a test matrix of 108 different install combinations. uefi/bios, 1 or 2 disks (raid1), virtio/ide/nvme, sys/lvmsys/cryptsys (not yet lvmcryptsys), ext4/xfs/btrfs
2022-05-04 17:26:44 <ncopa> and I run out of diskspace of my /tmp
2022-05-04 17:28:06 <donoban> nice
2022-05-04 17:40:37 <dalias> any chance openscad package will ever be updated? :-p
2022-05-04 17:42:56 <omni> what's missing?
2022-05-04 17:44:41 <omni> they seem to take their time between releases...
2022-05-04 17:44:51 <dalias> there aren't releases just date tags
2022-05-04 17:45:31 <psykose> i don't see a newer one than 2021.01
2022-05-04 17:45:35 <dalias> ah, bleh
2022-05-04 17:45:43 <dalias> indeed
2022-05-04 17:45:54 <psykose> we have the same version arch does, but up to now it sure has had a few patches
2022-05-04 17:46:02 <psykose> if you have some specific bug you know the fix for it's easy to backport thigns
2022-05-04 17:46:31 <Ermine> Their landing page mentions 2021.01
2022-05-04 17:46:52 <omni> as does https://github.com/openscad/openscad/releases
2022-05-04 17:47:02 <dalias> yeah. checking with #openscad
2022-05-04 17:47:18 <dalias> hopefully they can tag something soon because there's a lot of new functionality ppl are using that's not in that release
2022-05-04 17:47:26 <psykose> hah, the classic
2022-05-04 17:47:54 <omni> perhaps they're working on the Perfect Release
2022-05-04 17:49:16 <dalias> :)
2022-05-04 17:49:44 <dalias> maybe i'll just try to learn how to use apk to build my own packagae
2022-05-04 18:46:22 <ncopa> ================================================ 90 passed, 18 skipped in 679.58s (0:11:19) =================================================
2022-05-04 18:49:24 <psykose> i-i think you can reduce the amount of === there
2022-05-04 18:49:51 <psykose> also nice :)
2022-05-04 18:50:52 <bl4ckb0ne> motion to make the number of = equals to the number of tests passed :D
2022-05-04 18:51:33 <c7s> that would make it smaller :(
2022-05-04 18:51:44 <bl4ckb0ne> you just have to write more tests
2022-05-04 18:51:59 <c7s> what better motivation than equals signs
2022-05-04 18:52:38 <psykose> that is less than 90
2022-05-04 18:54:46 <c7s> I make it 96, but who's counting
2022-05-04 18:55:20 <psykose> oh wow
2022-05-04 18:55:23 <psykose> it's actually 97
2022-05-04 18:55:23 <psykose> hah
2022-05-04 18:55:26 <psykose> my eyes don't work
2022-05-04 20:25:47 <dalias> i found this on my alpine system which is surely a packaging bug:
2022-05-04 20:25:47 <dalias> -r-sr-x---    1 root     root         31496 Jan 17  2021 /usr/lib/pppd/2.4.9/pppoe.so
2022-05-04 20:25:56 <dalias> there is no reason for a .so to have +s
2022-05-04 20:26:25 <Hello71> is it like libcap where it's directly invokable for some reason
2022-05-04 20:26:39 <dalias> i vaguely recall that might mean something on glibc, but it doesn't on musl
2022-05-04 20:26:46 <dalias> i don't think so
2022-05-04 20:27:14 <dalias> anyway it may give privilege escalation from gid=root to uid=root since it just runs whatever bogus code happens to be at the start of .text
2022-05-04 20:29:54 <Hello71> actually i don't understand how this becomes +s
2022-05-04 20:30:10 <dalias> some bogus install command i guess
2022-05-04 20:30:34 <dalias> i'm confused because i thought abuild had some gating to make sure suids can't get created without explicitly listing them
2022-05-04 20:31:38 <psykose> suid check is only for +x as well
2022-05-04 20:32:05 <Hello71> https://github.com/ppp-project/ppp/commit/c6869931feed37330a96715fecc0c2c75f3f5dc0
2022-05-04 20:32:07 <psykose> (which is the one that can be bypassed with options=suid)
2022-05-04 20:32:12 <psykose> and there is a pie check which can't
2022-05-04 20:32:12 <psykose> i=$(find "$dir" -type f -perm /6000 \
2022-05-04 20:32:12 <psykose> # check so we dont have any suid root binaries that are not PIE
2022-05-04 20:32:12 <psykose> | xargs scanelf --nobanner --etype ET_EXEC \
2022-05-04 20:32:12 <psykose> | sed "s|ET_EXEC $dir|\t|")
2022-05-04 20:32:14 <psykose> error "Found non-PIE files that has SUID:"
2022-05-04 20:32:14 <psykose> if [ -n "$i" ]; then
2022-05-04 20:32:16 <psykose> echo "$i"
2022-05-04 20:32:16 <psykose> e=1
2022-05-04 20:32:18 <psykose> fi
2022-05-04 20:32:18 <psykose> # test suid bit on executable
2022-05-04 20:32:20 <psykose> i=$(find "$dir" \( -perm -u+s -o -perm -g+s \) -a -type f \
2022-05-04 20:32:20 <psykose> if ! options_has "suid"; then
2022-05-04 20:32:22 <psykose> -a -perm -o+x)
2022-05-04 20:32:22 <psykose> if [ -n "$i" ]; then
2022-05-04 20:32:24 <psykose> error "Found executable files with SUID bit set:"
2022-05-04 20:32:26 <psykose> echo "$i"
2022-05-04 20:32:28 <psykose> e=1
2022-05-04 20:32:30 <psykose> fi
2022-05-04 20:32:32 <psykose> fi
2022-05-04 20:32:34 <psykose> oops
2022-05-04 20:32:36 <psykose> did not mean to paste that
2022-05-04 20:32:57 <Hello71> conveniently converted to dalias shell script format :p
2022-05-04 20:33:01 <psykose> LMAO
2022-05-04 20:33:30 <dalias> :-)
2022-05-04 20:34:57 <Hello71> i think the original reason for 4550 is lost to history
2022-05-04 20:36:16 <Hello71> is there any plausible way to get gid=0 without uid=0 anyways
2022-05-04 20:36:53 <psykose> well, the commit it's from is.. 2004
2022-05-04 20:37:01 <psykose> with just 'new plugin sent in by person'
2022-05-04 20:37:03 <psykose> indeed lost..
2022-05-04 20:38:48 <dalias> :-p
2022-05-04 20:39:14 <dalias> hello71, iirc glibc does something special with +s for shared libs
2022-05-04 20:39:31 <dalias> maybe something awful like letting you LD_PRELOAD a +s .so into a +s main program if it's in a trusted path?
2022-05-04 20:50:24 <Hello71> i think that's right
2022-05-04 20:51:13 <Hello71> https://github.com/bminor/glibc/blob/master/elf/dl-load.c#L1946
2022-05-04 20:56:57 <dalias> how did anyone think that was a good idea??
2022-05-04 21:39:43 <Hello71> it seems reasonable to have some sort of flag for this, although reusing the setuid bit is... not great
2022-05-04 21:40:07 <Hello71> also probably you shouldn't be preloading anything into suid binaries anyways
2022-05-04 21:57:05 <dalias> yeah, there is just utterly no way "arbitrary .so that's okay to preload into some suid binary" is "okay to preload into any suid binary"
2022-05-05 07:38:18 <ncopa> morning
2022-05-05 07:38:30 <panekj> hello
2022-05-05 07:38:40 <ikke> o/
2022-05-05 07:39:24 <ncopa> i will try add tests for diskless today
2022-05-05 07:39:47 <ncopa> one question with sys installs though
2022-05-05 07:39:59 <ikke> ncopa: would it make sense to create a repo on gitlab?
2022-05-05 07:40:19 <ncopa> currently, if you sepcify 2 disks in setup-disk, it will create an mdadm raid1 device
2022-05-05 07:40:35 <ncopa> if you add cryptsys, it will encrypt the raid device
2022-05-05 07:40:49 <ncopa> if you enable lvm it will add lvm on top of the raid device
2022-05-05 07:41:10 <ncopa> my question is: what should we do if you sepcify 3 or more disks?
2022-05-05 07:41:31 <ncopa> currently it will set up raid5, which I think might not be the best idea nowdays
2022-05-05 07:42:06 <ncopa> ikke: i gues it would. I can move it from github if you want
2022-05-05 08:13:16 <Daanct12> morning ncopa 
2022-05-05 09:03:05 <omni> 3-4 disks raidz1, 5-7 disks raidz2, 8+ disks raidz3 ;)
2022-05-05 09:10:53 <ikke> ncopa: any objection against !33801?
2022-05-05 12:19:28 <ncopa> ikke: it still forks
2022-05-05 12:20:14 <ikke> ncopa: where?
2022-05-05 12:20:49 <ikke> printf is a shell built-in, so it does not have to fork
2022-05-05 14:58:22 <psykose> i assume the $() subshell still counts as a fork
2022-05-05 14:59:06 <ikke> A subshell is not a fork
2022-05-05 14:59:55 <ikke> Or does not _have_ to be a fork 
2022-05-05 15:05:48 <ikke> ok, ash does fork on $()
2022-05-05 15:06:15 <ikke> I suppose what I was aiming at is no fork+exec
2022-05-05 15:21:18 <orbea> fwiw printf is not always a builtin depending on the shell, see mksh for instance
2022-05-05 15:22:01 <orbea> however posix strongly suggests using printf too...
2022-05-05 15:29:07 <ikke> Yes, but we're mostly targetting ash here
2022-05-05 15:29:37 <ikke> Or at least, something similar enough to ash
2022-05-05 18:12:10 <anjan> hey, does anyone know how this person managed to get the json from this secfixes webpage? https://gitlab.alpinelinux.org/ariadne/secfixes-tracker/-/issues/6
2022-05-05 18:12:31 <anjan> I tried curl https://security.alpinelinux.org/branch/3.11-main/maintainer-issues -H "Accept: application/json"
2022-05-05 18:13:19 <anjan> https://paste.sr.ht/~anjan/f177bf3e108c3642800ff82f5c10dabdc0b24bf5
2022-05-05 18:13:20 <Ariadne> application/json+ld
2022-05-05 18:13:41 <anjan> Ariadne: 406 Not Acceptable
2022-05-05 18:14:16 <Ariadne> Any URI on this tracker may be fetched with Accept: application/ld+json to get an equivalent JSON-LD document.
2022-05-05 18:14:19 <Ariadne> sorry, ld+json
2022-05-05 18:14:19 <Ariadne> :)
2022-05-05 18:15:08 <anjan> Ariadne: I got 500 Internal Server Error
2022-05-05 18:15:13 <Ariadne> cool
2022-05-05 18:15:35 <Ariadne> unfortunately i don't have time to investigate at the moment
2022-05-05 18:16:04 <ikke> TypeError: float() argument must be a string or a number, not 'NoneType'
2022-05-05 18:16:14 <anjan> ok no worries Ariadne 
2022-05-05 18:16:20 <ikke> https://tpaste.us/QN0z 
2022-05-05 18:16:25 <ikke> stacktrace ^
2022-05-05 18:18:17 <anjan> interesting, Ill open an issue ikke 
2022-05-05 18:20:08 <psykose> i guess there are no secfixes then. and that means, no bugs
2022-05-05 18:20:21 <psykose> or only bugs? you decide!
2022-05-05 18:20:46 <anjan> ah, craftyguy found that cvss3_score might not be a float https://gitlab.alpinelinux.org/ariadne/secfixes-tracker/-/blob/master/secfixes_tracker/models.py#L25
2022-05-05 18:21:33 <ikke> It's None
2022-05-05 18:21:43 <ikke> Which the stracktrace shows
2022-05-05 18:21:48 <ikke> It just needs to handle that
2022-05-05 18:21:53 <anjan> There we go
2022-05-05 18:21:55 <craftyguy> yeah just needs a guard for that
2022-05-05 18:21:59 <craftyguy> before casting
2022-05-05 18:22:03 <anjan> ok, Ill see if I can code and test something up
2022-05-05 18:22:14 <anjan> Ill submit a bug report so this time isnt atleast wasted
2022-05-05 18:22:31 <ikke> What should it return in that case?
2022-05-05 18:22:35 <ikke> Just an empty string?
2022-05-05 18:23:20 <ikke> Or null?
2022-05-05 18:24:14 <ikke> or 0
2022-05-05 18:28:07 <craftyguy> null seems appropriate if it's unknown, unless a score of 0 is valid / has meaning
2022-05-05 18:28:28 <craftyguy> or rather, if 0 doens't have meaning in this context, then maybe 0 instead of null
2022-05-05 18:35:42 <anjan> bugtracker here: https://gitlab.alpinelinux.org/ariadne/secfixes-tracker/-/issues/8
2022-05-05 18:36:05 <anjan> sorry, I must be pinging the author a bunch even though they said they were too busy
2022-05-05 18:36:17 <anjan> (cause it's in the url heh)
2022-05-05 18:38:51 <ikke> I've created an MR
2022-05-05 18:39:54 <anjan> thank you guys. I really appreciate it
2022-05-05 19:10:13 <ikke> Hmm, somethings afoot with gitlab (after upgrade)
2022-05-05 19:12:06 <psykose> still down
2022-05-05 19:12:51 <ikke> yes
2022-05-05 19:13:08 <psykose> what do you see?
2022-05-05 19:13:28 <skarnet> I see dead people
2022-05-05 19:13:40 <skarnet> (hopefully not because of gitlab)
2022-05-05 19:14:12 <psykose> i wish i saw dead people
2022-05-05 19:14:16 <psykose> teach me..
2022-05-05 19:16:42 <ikke> A migration that was expected to be finished but still active
2022-05-05 19:29:19 <ikke> ok, progress
2022-05-05 19:30:30 <ikke> ok, gitlab is starting again
2022-05-05 19:30:55 <psykose> did it just take that long
2022-05-05 19:30:58 <ikke> Nop
2022-05-05 19:31:03 <ikke> I had to manually run that task
2022-05-05 19:31:07 <psykose> rip
2022-05-05 19:31:39 <ikke> It's up again
2022-05-06 00:36:47 <megactl> Hello everyone
2022-05-06 00:37:31 <craftyguy> hi!
2022-05-06 00:37:54 <megactl> I'm struggling to make a diskless boot loads wifi driver
2022-05-06 00:38:10 <megactl> I would appreciate any comments
2022-05-06 00:38:16 <megactl> I'll describe what I have done so far
2022-05-06 00:41:02 <megactl> I upgraded to the latest kernel in full system environment, installed linux-lts-dev, alpine-sdk etc..I built the wifi driver using make install and it's loaded successfully.
2022-05-06 00:41:20 <megactl> I made setup-bootable usb drive then used update-kernel and I'm able to boot with new usb drive
2022-05-06 00:41:36 <megactl> however the wifi driver is not loaded
2022-05-06 00:42:40 <Hello71> what driver is this anyways
2022-05-06 00:43:08 <megactl> i have unsquashed modloop-lts and copied my full install files into it which are /lib/firmware, /lib/modules/KERNELVERSION, squashed it again and it's still not loaded
2022-05-06 00:43:14 <megactl> 88x2bu
2022-05-06 00:43:37 <megactl> https://github.com/RinCat/RTL88x2BU-Linux-Driver
2022-05-06 00:44:46 <megactl> the modloop-lts file has the files inside but when I boot as ramdisk the files don't exist in /lib/modules...
2022-05-06 00:45:36 <Hello71> sounds like it is mounting some other modloop
2022-05-06 00:46:22 <Hello71> seems like rtl88x2bu is packaged as -src in testing
2022-05-06 00:46:38 <Hello71> not sure how akms works with diskless though, my guess is not well
2022-05-06 00:47:31 <megactl> I'm not using akms ^^'
2022-05-06 00:48:00 <megactl> I want to load it with current kernel not as dynamic
2022-05-06 00:48:29 <megactl> I'll check if somehow I messed up with modloop file maybe it loads backed up modloop or something
2022-05-06 01:09:32 <megactl> I ended up with both installs not working somehow
2022-05-06 01:09:57 <megactl> But the last thing I did was deleting apks folder, it has old apk kernel files and linux-firmware
2022-05-06 01:10:22 <megactl> I think there is something old loaded and overwriting the files
2022-05-06 01:12:49 <megactl> I put new linux-firmware,kernel apk files but i'm still unable to boot, I think there are some traces of old files or configurations, starting from scratch with more care
2022-05-06 05:53:08 <anjan> How long till the secfixes with everything fixed is live at security.alpinelinux.org
2022-05-06 06:06:08 <ikke> The job runs hourly
2022-05-06 06:24:00 <anjan> ikke: I meant getting secfixes with the new commits with the fixes we found today
2022-05-06 06:24:39 <anjan> https://gitlab.alpinelinux.org/ariadne/secfixes-tracker/-/commit/df97d10bd16169246337a2d3488e518311688084
2022-05-06 06:24:42 <anjan> specifically that
2022-05-06 06:25:13 <Ariadne> christ
2022-05-06 06:25:25 <Ariadne> patience man
2022-05-06 06:27:32 <anjan> oh. sorry. I thought it was automated and something was up. My bad. If it requires input on your end, take your time.
2022-05-06 06:29:22 <anjan> also I didnt mean to tag you again.
2022-05-06 06:47:51 <ikke> Yeah, there is no automatic deployment
2022-05-06 07:14:46 <ddevault> what's the latest approach to dealing with stupid python bullshit again
2022-05-06 07:21:14 <ikke> python-installer
2022-05-06 07:31:52 <ddevault> thanks ikke 
2022-05-06 11:09:28 <ikke> clandmeter: any objection to merging !33891?
2022-05-06 12:53:10 <Hello71> seems like gitlab issue lists can no longer be viewed while logged out
2022-05-06 12:54:07 <psykose> in a very annoying way too
2022-05-06 12:54:14 <psykose> instead of just saying unauthorised it's a generic error
2022-05-06 12:54:23 <psykose> and everything in network returns 200 :p
2022-05-06 12:54:29 <ikke> :/
2022-05-06 13:10:06 <psykose> also the 'lint' stage always returns green in gitlab ci regardless of output
2022-05-06 13:10:49 <ikke> F.U.N.
2022-05-06 13:12:18 <Hello71> well the error is "Cannot return null for non-nullable field Issue.author" x 20
2022-05-06 13:16:41 <ikke> Where do you see that error?
2022-05-06 13:17:41 <ikke> Ah, found it
2022-05-06 13:17:46 <ikke> graphql
2022-05-06 13:42:40 <psykose> ikke: could you merge !33962
2022-05-06 14:27:15 <megactl> using update-kernel on full system install to a usb drive for diskless use doesn't copy the drivers, I'm struggling since yesterday to make the wifi driver work in diskless usb environment.
2022-05-06 14:27:57 <megactl> Editing modloop-lts manually to add all full system /lib/modules and lib/firmware gives same result
2022-05-06 14:28:47 <megactl> after booting diskless, /lib/modules doesn't reflect what's in modloop-lts file.. files aren't there not only not loaded
2022-05-06 14:32:48 <megactl> I started from scartch, installed full alpine in a system
2022-05-06 14:32:48 <megactl> added 3.16/edge repositories, upgraded packages, install linux-lts/linux-lts-dev , alpine-sdk and everything necessary to be able to 'make install' wifi driver
2022-05-06 14:32:49 <megactl> setup-bootable from iso image to usb, then update-kernel on usb/boot
2022-05-06 14:32:52 <megactl> Am I missing something?
2022-05-06 15:00:32 <megactl> Its working now!
2022-05-06 15:00:45 <ikke> megactl: What was the issue?
2022-05-06 15:02:20 <megactl> Seems when I edited modloop-lts I compressed it wrongly, because the only way I found on how to do it is from the wiki
2022-05-06 15:02:21 <megactl> https://wiki.alpinelinux.org/wiki/DIY_Fully_working_Alpine_Linux_for_Allwinner_and_Other_ARM_SOCs
2022-05-06 15:02:50 <megactl> I was using this
2022-05-06 15:02:50 <megactl> mksquashfs squashfs-temp/ modloop-sunxi -b 1048576 -comp xz -Xdict-size 100%
2022-05-06 15:03:02 <megactl> but when I did it as written in update-kernel script
2022-05-06 15:04:23 <megactl> https://github.com/alpinelinux/alpine-conf/blob/4b89713f216d0c07a84aaadfce4e503d115b3a34/update-kernel.in#L336
2022-05-06 15:04:23 <megactl> mksquashfs $MODLOOP "$STAGING/$MODIMG" -comp xz -exit-on-error $mksfs
2022-05-06 15:04:24 <megactl> where $mksfs = -Xbcj x86
2022-05-06 15:04:25 <megactl> it worked
2022-05-06 15:05:40 <megactl> also there is no way to add kernel drivers using update-kernel options, -e seems only for /lib/firmware files , not /lib/modules/$KERNELVERSION... drivers
2022-05-06 15:58:27 <ikke> Will restart gitlab to update to a new patch release
2022-05-07 10:32:52 <nmeum> ncopa: the busybox dhcp patch you commited actualyl made the situation worse for me, i.e. I often don't get a dhcp lease within the new time frame because the link isn't up yet
2022-05-07 10:33:51 <nmeum> I would really suggest that we solve this properly in ifupdown-ng (i.e. analog to bcnm-waitif) instead of using a timeout mechanism in busybox directly
2022-05-07 11:58:19 <omni> I noticed that if you have multiple repos configured in /etc/apk/repositories and apk fail to fetch the index from one of them it still tries to fetch packages from it and doesn't seem to fall back on the others when it fail to do so
2022-05-07 11:59:00 <ikke> omni: I suppose because it still has an index cached
2022-05-07 11:59:41 <ikke> Note that /etc/apk/repositories is not really meant to specify fallback repositories
2022-05-07 12:00:14 <omni> aha
2022-05-07 12:03:05 <ikke> As repositories don't really have an identity, it would be difficult to do that without resulting into gotchas
2022-05-07 12:51:39 <HRio> anybody else that have notices zfs zvol related instabilies since this weeks kernel update in v3.15?
2022-05-07 12:53:38 <HRio> more specifically nginx reverse proxy with /var/lib/nginx/tmp on a zvol seems broken
2022-05-07 13:11:58 <HRio> ahh https://github.com/openzfs/zfs/issues/12971#issuecomment-1119169481
2022-05-07 13:20:40 <ikke> Seems like linux stable has regressions quite regularly
2022-05-07 14:38:25 <martijnbraam> I just noticed x264enc is missing in gstreamer, looks like there's a flag required in gst-plugins-ugly to enable plugins that contain GPL code
2022-05-07 14:38:28 <martijnbraam> any reason that flag is missing?
2022-05-07 14:43:40 <ikke> maybe oversight?
2022-05-07 14:43:50 <ikke> what is the flag?
2022-05-07 14:45:19 <martijnbraam> -Dgpl=enabled
2022-05-07 14:45:52 <martijnbraam> looking at the history there were rebuilds for x264, so it worked once
2022-05-07 14:46:41 <martijnbraam> probably also an issue on -plugins-bad and -plugins-good
2022-05-07 14:56:30 <psykose> i noticed that error sometimes but also sometimes it just worked, which was strange
2022-05-07 15:01:09 <psykose> i enabled it anyway, with -Dgpl=enabled, since we're licencing it as gpl, so
2022-05-07 15:01:19 <psykose> i did disabled the cd/dvd ones it also enables though
2022-05-07 15:01:29 <psykose> should be there in a few minutes :)
2022-05-07 15:08:14 <HRio> looks like the zfs problem was handled in the zfs 2.1.3 changes for Linux 5.16 compat, maybe we shall bump zfs to 2.1.4 in stable? 
2022-05-07 15:08:16 <HRio> https://github.com/openzfs/zfs/pull/12975
2022-05-07 15:08:21 <HRio> https://github.com/openzfs/zfs/releases/tag/zfs-2.1.3
2022-05-07 15:09:09 <psykose> ah, that might fix it
2022-05-07 15:22:42 <EvTheFuture> nr
2022-05-07 15:23:24 <EvTheFuture> 
ACTION is sorry for accidentally sending junk...

2022-05-07 15:24:30 <psykose> gst-plugins-good doesn't have a gpl flag, and -bad has it but it's mostly junk again, the only thing in there is x265enc
2022-05-07 15:24:40 <psykose> i guess if you really want it i can add in x265enc too :)
2022-05-07 16:40:32 <martijnbraam> I don't think a lot of software uses x265enc and gstreamer, but it couldn't hurt
2022-05-07 17:57:23 <Saijin_Naib> psykose: Why are CD/DVD disabled?
2022-05-07 17:59:14 <psykose> if you know of literally anything that uses 'cdiocddasrc' to read audio cds via gstreamer i will happily enable it
2022-05-07 17:59:28 <psykose> it's probably two pieces of software in the whole universe :p
2022-05-07 18:34:58 <Saijin_Naib> Ahh, gotcha. Thought it was generic cd/DVD support which I definitely appreciate having.
2022-05-07 18:34:58 <Saijin_Naib> No idea what sources would use that codec, haha
2022-05-07 21:28:42 <nangel> Hey, I followed: https://wiki.alpinelinux.org/wiki/Creating_patches to create a MR:
2022-05-07 21:30:12 <nangel> https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/33853
2022-05-07 21:30:49 <nangel> That was 2 May 2022
2022-05-07 21:32:17 <nangel> Last night I was assigned a MR from J0WI (https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/34071) for the same thing.
2022-05-07 21:32:54 <nangel> Both MR's are effectively the same thing, so one can get merged, and the other deleted.
2022-05-07 21:33:49 <nangel> The problem is I am not a reviewer and (AFAIK) do not have rights to push to master (and if I DO have those rights, you need to revoke them <smile>)
2022-05-07 21:34:19 <panekj> psykose will probably merge it once she sees it
2022-05-07 21:34:32 <nangel> Any pointers on how to make sure a reviewer gets notified?
2022-05-07 21:35:19 <panekj> nangel: just wait, if it doesn't get merged or any comment, complain here
2022-05-07 21:35:58 <nangel> panekj: thanks.  Part of this is I am trying to work on the devloper's manual, and "going through the whole 'do 1,2, then 3'" steps will help all of us who don't drop MR's every week.
2022-05-07 21:38:27 <psykose> i mean.. shouldn't you have the rights, as a tsc member?
2022-05-07 21:40:32 <panekj> i haven't noticed that lol, you have dev role
2022-05-07 21:53:14 <nangel> psykose: I have messed up too many git repos to ever be allowed to touch aports.  It is for your own good.
2022-05-07 21:56:06 <nangel> Thanks for the input!
2022-05-08 04:39:06 <psykose> ikke: also for your amusement, stunnel is as stuck as it always is on s390x
2022-05-08 04:39:28 <ikke> Let's give it a stern look
2022-05-08 04:39:56 <psykose> :3
2022-05-08 04:40:45 <psykose> and it unstuckened itself when you did the usual
2022-05-08 04:40:48 <ikke> Yes
2022-05-08 04:40:53 <psykose> :3
2022-05-08 04:41:06 <ikke> Normally I kill the entire process tree, but it will just get stuck again
2022-05-08 04:41:15 <ikke> just killing the test and it continues ¯\_(ツ)_/¯
2022-05-08 04:49:49 <ikke> oh, you are also working on rsyslog
2022-05-08 04:50:51 <ikke> are you doing 3.14?
2022-05-08 04:52:06 <ikke> apparently
2022-05-08 04:53:34 <psykose> ah
2022-05-08 04:53:35 <psykose> didnt see
2022-05-08 04:53:37 <psykose> yeah i did them all
2022-05-08 04:53:44 <psykose> 3.12 does not have anything resembling the same code that i can find
2022-05-08 04:53:49 <ikke> ok
2022-05-08 05:05:18 <psykose> ah no, it was just missing one file
2022-05-08 05:07:40 <ikke> right
2022-05-08 05:07:50 <ikke> https://github.com/rsyslog/rsyslog/commit/01feb44bf1d091ec45ff425a096a0169f290da4b#diff-e666705dfe5af14795afb1d8d1b0a2089d34cdba4f7e601a251210f645866893 is in v8.2004.0
2022-05-08 05:09:02 <psykose> mhm
2022-05-08 05:09:05 <psykose> just the contrib thing wasnt
2022-05-08 06:22:50 <ikke> Hmm, for some reason x86 fails because the linker cannot find slapd-common.o
2022-05-08 06:22:52 <ikke> https://gitlab.alpinelinux.org/alpine/aports/-/jobs/714405
2022-05-08 06:23:22 <ikke> /usr/lib/gcc/i586-alpine-linux-musl/11.2.1/../../../../i586-alpine-linux-musl/bin/ld: cannot find slapd-common.o: No such file or directory
2022-05-08 06:24:19 <psykose> $10 it's fixed with -j1
2022-05-08 06:24:20 <ikke> perhaps concurrency issue / race condition?
2022-05-08 06:24:23 <ikke> yea
2022-05-08 06:24:27 <psykose> almost always is
2022-05-08 06:24:47 <ikke> which means there is a dependency for a target missing
2022-05-08 06:24:53 <psykose> yeah
2022-05-08 06:25:00 <psykose> it's quite common for this configure soup
2022-05-08 06:25:07 <psykose> we have quite a few of these as -j1
2022-05-08 06:25:30 <psykose> because they default to -j1 unless you pass it manually, and i guess nobody realised for a really long time
2022-05-08 06:26:46 <ikke> Just interesting it consistently happens on a single arch
2022-05-08 06:41:12 <psykose> consistently until it passes
2022-05-08 06:42:20 <ikke> trying to figure out how this works
2022-05-08 06:42:22 <ikke> it uses libtool
2022-05-08 06:42:58 <psykose> ldif-filter: ldif-filter.o $(XLIBS)
2022-05-08 06:42:58 <psykose> $(LTLINK) -o $@ ldif-filter.o $(OBJS) $(LIBS)
2022-05-08 06:43:06 <psykose> just add $(OBJS) to the top line
2022-05-08 06:43:08 <psykose> it will pass every time :)
2022-05-08 06:43:21 <psykose> tests/progs/Makefile.in
2022-05-08 06:43:41 <ikke> Like this?
2022-05-08 06:43:43 <ikke> slapd-tester: slapd-tester.o $(OBJS) $(XLIBS) 
2022-05-08 06:43:59 <ikke> Which is already the case
2022-05-08 06:44:17 <psykose> it's not the case on the ldif-filter line
2022-05-08 06:44:30 <ikke> ooh
2022-05-08 06:45:04 <psykose> (i mean i can also be wrong, but this is where it fails, since it tries to build that but links to OBJS in the line below without having it as a dep)
2022-05-08 06:45:17 <psykose> and it's the same thing from the logs
2022-05-08 06:45:29 <psykose> sadly make does not automatically lift deps
2022-05-08 06:45:43 <psykose> only the x: y line is the ordering
2022-05-08 07:22:31 <ikke> pipeline is fixed now
2022-05-08 07:23:48 <psykose> :)
2022-05-08 10:01:51 <nmeum> do we want to add skalibs and utmps to our bootstrap path or do we want to build busybox and openssh without utmps support when boostrapping?
2022-05-08 10:32:21 <skarnet> you probably don't need user accounting when bootstrapping, so I suggest keeping them out
2022-05-08 10:32:36 <skarnet> hmmm, openssh? in the bootstrap?
2022-05-08 10:33:12 <skarnet> if you need to ssh into an account while bootstrapping that's a different thing, but... why?
2022-05-08 10:34:20 <ikke> Only reason I can think of is to support a default builder setup
2022-05-08 10:37:38 <nmeum> https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/scripts/bootstrap.sh#L125
2022-05-08 10:37:42 <nmeum> I don't know, I haven't added it :D
2022-05-08 10:38:04 <nmeum> skarnet: right, only downside is that it makes the APKBUILD it bit more complex if you have to add if [ -z "$BOOTSTRAP" ]; then … everywhere
2022-05-08 10:40:02 <skarnet> nmeum: I have no horse either way in this race, skalibs and utmps are easy and quick to build so they wouldn't significantly impact the bootstrap, but as a matter of principle, *everything* that can be kept out of the bootstrap should be
2022-05-08 10:40:39 <nmeum> I tend to agree, I manually patched it out of my local tree for now
2022-05-08 10:41:41 <nmeum> trying once again to bootstrap rust for riscv64, so far I only had to patch the vendored libc create. let's so how far my motivation takes me this time…
2022-05-08 12:01:00 <nmeum> psykose: ping
2022-05-08 13:58:30 <nmeum> ok it looks good
2022-05-08 14:02:15 <nmeum> \o/ https://tpaste.us/jP05
2022-05-08 14:02:50 <nmeum> ikke: what would you need me to do to get a boostrapped rustc installed on the riscv64 builders, do you want to boostrap yourself or should I give you an apk?
2022-05-08 14:21:21 <ikke> nmeum: How hard is to do the bootstrapping from source?
2022-05-08 14:21:38 <ikke> I gather that you managed to build rust?
2022-05-08 14:22:09 <nmeum> yes, I boostrapped it using scripts/boostrap.sh with a few patches on top
2022-05-08 14:22:31 <nmeum> should be doable to do it form source
2022-05-08 14:22:51 <ikke> Ok, if you could give the steps, I could give it a try
2022-05-08 14:23:40 <nmeum> you need !34151 and you need to slightly modify scripts/bootstrap.sh since it is broken as usual: https://tpaste.us/DBxa
2022-05-08 14:24:06 <ikke> nmeum: Can't we push the fixes to bootstrap.sh?
2022-05-08 14:24:17 <nmeum> those are not fixes, just workarounds :p
2022-05-08 14:24:22 <ikke> aha, ok
2022-05-08 14:24:24 <nmeum> I pushed fixes for busybox, curl and openssh though
2022-05-08 14:24:37 <nmeum> for example, openrc doesn't boostrap currently because the buildsystem was switched to meson
2022-05-08 14:24:42 <nmeum> but you don't need it for rustc anyhow
2022-05-08 14:24:51 <ikke> Right, I saw that issue comming by
2022-05-08 14:25:28 <nmeum> I don't see an issue with just removing it from boostrap.sh locally for the rust boostrap
2022-05-08 14:25:38 <ikke> nod
2022-05-08 14:26:03 <nmeum> so the steps are: apply !34151, use https://tpaste.us/DBxa and run `CBUILDROOT=/var/tmp/riscv64 ./bootstrap.sh riscv64` that should be it
2022-05-08 14:26:13 <ikke> ok
2022-05-08 14:26:42 <nmeum> ok and you also need !34149
2022-05-08 14:31:37 <nmeum> do you have the time to start the boostrap today so we have results by tomorrow?
2022-05-08 14:33:09 <ikke> yes, working on it
2022-05-08 14:33:48 <nmeum> ty
2022-05-08 14:38:46 <ikke> nmeum: so is the idea that I first apply the patches, and once bootstrapped, we push it to make aports consistent?
2022-05-08 14:39:00 <ikke> I mean, the rust patches
2022-05-08 14:39:18 <nmeum> yes
2022-05-08 14:39:21 <ikke> ok
2022-05-08 14:39:23 <nmeum> I can also push the rust patches right now
2022-05-08 14:39:32 <nmeum> it's just that it won't build unles we bootstrap it first
2022-05-08 14:40:33 <nmeum> the rust patches are also trivial, just a few missing libc constants and an issue with an unsupported assembler directive
2022-05-08 14:43:29 <nmeum> bootstrape ich rust jetzt auch noch für s390x? 🤔
2022-05-08 14:43:55 <nmeum> oops wrong channel
2022-05-08 14:44:00 <ikke> haha
2022-05-08 14:44:53 <ikke> Should the llvm13 patch have a pkgrel bump?
2022-05-08 14:45:19 <ikke> I assume I should build llvm13
2022-05-08 14:46:33 <nmeum> I didn't bump pkgel because it shouldn't change anything for non-boostrap builds and scripts/boostrap.sh should build it without a pkgrel bump
2022-05-08 14:46:48 <ikke> ah, makes sense
2022-05-08 14:48:17 <ikke> ok, running the bootstrap script now
2022-05-08 14:49:02 <nmeum> great, thanks
2022-05-08 14:49:14 <nmeum> let me know if you run into any issues :)
2022-05-08 14:59:31 <ikke> nmeum: https://tpaste.us/BkW9 
2022-05-08 15:14:31 <ikke> Complete output https://tpaste.us/70DO 
2022-05-08 15:32:12 <ikke> When should g(cc|++)-riscv64 be built?
2022-05-08 15:45:25 <nmeum> > >>> gcc: Package is up to date
2022-05-08 15:45:35 <nmeum> did it not build gcc at all?
2022-05-08 15:46:12 <ikke> No
2022-05-08 15:47:21 <nmeum> strange. you are running the bootstrap on x86_64, yes?
2022-05-08 15:48:05 <ikke> No, on the builder, thought that was the idea
2022-05-08 15:48:23 <ikke> I misunderstood
2022-05-08 15:48:59 <nmeum> ah, yeah you have to run it on x86_64 to cross-compile rust for riscv64 from x86_64
2022-05-08 15:49:11 <nmeum> sorry, should have stated that more clearly
2022-05-08 16:00:51 <ikke> nmeum: and then we should install that package as -bootstrap and build rust?
2022-05-08 16:00:58 <ikke> (Not saying it's finished)
2022-05-08 16:12:50 <nmeum> yes, that's what i was thinking
2022-05-08 16:13:08 <ikke> ok
2022-05-08 16:13:24 <nmeum> (that should be how it was bootstrapped for other arches as well, at least that's my understanding)
2022-05-08 16:14:54 <ikke> q
2022-05-08 16:34:36 <ikke> nmeum: Running into this: https://tpaste.us/enrb 
2022-05-08 16:38:45 <nmeum> huh, that looks wild
2022-05-08 16:39:31 <ikke> yea
2022-05-08 16:39:50 <ikke> It's in a docker container, but abuild -r just works fine
2022-05-08 16:39:55 <ikke> x86_64
2022-05-08 16:40:12 <nmeum> I also boostrapped in a docker container
2022-05-08 16:42:13 <ikke> It's executing CTARGET=riscv64 BOOTSTRAP=nobase APKBUILD=/home/buildozer/aports/main/binutils/APKBUILD abuild -r
2022-05-08 16:42:18 <nmeum> the bootstrap script should actually run apk with initdb and initialize the apk database beforehand
2022-05-08 16:44:04 <ikke> Oh, I see, it checks if the directory already exists or not
2022-05-08 16:44:42 <ikke> Fixed
2022-05-08 16:45:13 <nmeum> sweet
2022-05-08 16:51:00 <ikke> ERROR: /usr/lib/libzstd.so.1.5.2: Could not find owner package
2022-05-08 16:51:24 <ikke> gcc-pass2-riscv64
2022-05-08 16:56:09 <ikke> should zstd be in the package list?
2022-05-08 16:57:52 <ikke> No, it already happens before it reaches that part
2022-05-08 17:01:18 <ikke> It happens when tracing dependencies btw
2022-05-08 17:03:07 <nmeum> hm, I didn't get that locally not sure
2022-05-08 17:05:54 <nmeum> might also be easier to just use my bootstraped version instead of boostraping again
2022-05-08 17:06:14 <nmeum> also: I am currently testing this with a few more complex aport and looks like it segfaults on some crates currently so need to address that as well
2022-05-08 17:13:26 <Newbyte> Do you get what this is about: https://gitlab.alpinelinux.org/Newbyte/aports/-/jobs/714894#L971
2022-05-08 17:14:18 <panekj> error: failed to run custom build command for `gmp-mpfr-sys v1.4.8`
2022-05-08 17:15:35 <Newbyte> yeah, but I don't really understand the error. I was wondering if someone could shed some light
2022-05-08 17:15:45 <Newbyte> I was thinking maybe I could try disabling LTO and all that for x86
2022-05-08 17:15:57 <ikke> nmeum: Where is the package that you bootstrapped?
2022-05-08 17:16:25 <nmeum> https://dev.alpinelinux.org/~nmeum/edge/riscv64/
2022-05-08 17:16:54 <nmeum> but as I said, there does seem to be some work left to do since it can't compile rust itself yet
2022-05-08 17:17:04 <ikke> ok
2022-05-08 17:17:24 <nmeum> I will ping you again once I am done with that (:
2022-05-08 17:19:45 <ikke> :)
2022-05-08 17:23:36 <panekj> Newbyte: i think it's due to we are running x86 on x64 but I might be wrong
2022-05-08 17:24:14 <panekj> from quick look at that project, there might be something leaking about x64 and it assumes it builds for x64
2022-05-08 17:24:46 <ikke> yeah, that's correct
2022-05-08 17:25:03 <ikke> So maybe there is a switch to force it to use x86
2022-05-08 17:28:01 <Newbyte> panekj: oh, that makes sense. thanks!
2022-05-08 17:28:13 <panekj> `--host=<target>` should work
2022-05-08 17:28:31 <panekj> but you would need to pass that somehow to gmp
2022-05-08 17:28:32 <Newbyte> panekj: would I give abuild-meson that?
2022-05-08 17:28:35 <Newbyte> oh, hm
2022-05-08 17:29:36 <panekj> oh, it's one of the gnome apps?
2022-05-08 17:30:26 <panekj> mhm, but since its just build.rs it shouldn't be a problem to patch for vendored dep
2022-05-08 17:34:12 <Newbyte> panekj: how would I patch a vendored dependency?
2022-05-08 17:36:47 <panekj> abuild unpack, go to builddir, dep should be somewhere around vendored/gmp-src probably, cp build.rs build.rs.orig, modify build.rs and diff it
2022-05-08 17:37:09 <panekj> I'm wondering though if it wouldn't be better to just link it so system libs
2022-05-08 17:37:15 <panekj> `gmp-dev`
2022-05-08 17:42:06 <Newbyte> panekj: yeah but would abuild be able to patch that considering that the dependency is downloaded in the build stage?
2022-05-08 17:43:21 <panekj> yes, if you provide prepare() function, which should be done for that aport
2022-05-08 17:44:09 <Newbyte> seems like it does support linking to a shared library if you add some option: https://gitlab.com/tspiteri/gmp-mpfr-sys/-/issues/21
2022-05-08 17:44:23 <panekj> CARGO_FEATURE_USE_SYSTEM_LIBS
2022-05-08 17:46:23 <panekj> I'm already building your branch with that
2022-05-08 17:48:34 <Newbyte> Yeah, I'm doing that locally right now as well
2022-05-08 17:48:47 <Newbyte> if gdm doesn't suspend my system
2022-05-08 17:49:04 <panekj> great project btw, tag is `0.6.0`, Cargo has `0.1.`
2022-05-08 17:49:16 <panekj> s/0.1./0.1.0
2022-05-08 17:49:16 <alpine-meetbot> panekj meant to say: great project btw, tag is `0.6.0`, Cargo has `0.1.0`
2022-05-08 17:50:38 <Newbyte> the build setup is definitely awkward in some places, but it's a nice music player
2022-05-08 17:53:47 <panekj> https://tpaste.us/Pjdx
2022-05-08 17:54:13 <panekj> but I would generally advise to patch out whatever meson is doing so it conforms to our standard
2022-05-08 17:55:17 <panekj> missed `mpfr-dev` in makedepends :')
2022-05-08 17:55:39 <Newbyte> was about to ask about that
2022-05-08 17:58:06 <panekj> I'm guessing from names to what it links, probably could look at source but I usually just let it build and errors will tell me
2022-05-08 17:58:50 <panekj> sadly my nixos vm is taking very sweet time grabbing packages for past 2 hours so I can't get into my standard alpine install and suffice with very slow WSL2 :c
2022-05-08 17:59:46 <Newbyte> I just delegated a spare PC to be my Alpine builder 
2022-05-08 18:00:35 <panekj> wish I could do that but all my other machines are <= 4t
2022-05-08 18:01:16 <panekj> `these paths will be fetched (2654.13 MiB download, 12494 MiB unpacked):` this might be the reason why it's so slow
2022-05-08 18:03:05 <Newbyte> seems like it doesn't like being built in offline mode
2022-05-08 18:41:59 <panekj> probably because it takes `true`/`false` string argument, instead of `1`
2022-05-08 18:42:09 <panekj> `error in environment variable `CARGO_NET_OFFLINE`: provided string was not `true` or `false``
2022-05-08 18:50:06 <ikke> nmeum: I removed alpine-sdk and installed just abuild and build-base, it seems to go further now
2022-05-08 18:50:56 <ikke> Not certain though
2022-05-08 18:51:35 <ikke> Oh no, still same error, it just continues and fails every package
2022-05-08 18:53:06 <sam_> [18:55:16]  <panekj> missed `mpfr-dev` in makedepends :')
2022-05-08 18:53:07 <sam_> this reminds me
2022-05-08 18:53:19 <sam_> for reasons unknown to me, mpfr don't do patch releases
2022-05-08 18:53:25 <sam_> instead, they dump a bunch of patches on their website
2022-05-08 18:53:43 <sam_> both fedora and gentoo (after I realised fedora were, and then looked into it) now apply a bunch, you might to as well
2022-05-08 18:53:45 <panekj> just like readline
2022-05-08 18:53:47 <sam_> https://www.mpfr.org/mpfr-current/#bugs
2022-05-08 18:54:02 <sam_> yeah, although at least readline and bash announce them!
2022-05-08 18:54:09 <sam_> afaict these were just silently added to the site :(
2022-05-08 19:16:46 <ddevault> do we have any alpine packages which include firefox addons
2022-05-08 19:49:49 <panekj> ddevault: https://pkgs.alpinelinux.org/contents?file=*.xpi&path=&name=&branch=edge
2022-05-08 19:50:12 <craftyguy> maybe browserpass?
2022-05-08 19:50:26 <ddevault> thanks panekj!
2022-05-08 19:51:59 <panekj> Newbyte: it doesn't build in offline mode because of CARGO_HOME in build-aux/cargo.sh 
2022-05-08 19:52:19 <panekj> I hate stupid scripts like that
2022-05-08 19:53:02 <panekj> imo, that package should be patched anyway so it builds offline and respects our fetch in prepare()
2022-05-08 20:03:43 <panekj> https://tpaste.us/6Ejl
2022-05-08 20:13:15 <panekj> + apkbuild https://tpaste.us/Vvd1
2022-05-08 20:35:03 <Newbyte> panekj: I doubt it's malice. from what I understand the author is new to Rust 
2022-05-08 20:35:31 <Newbyte> so he might be receptive to fixing this upstream
2022-05-08 21:05:27 <panekj> I'm not saying it's malice, I'm just a little frustrated when people do that :P
2022-05-08 21:05:42 <panekj> it's also not limited to rust
2022-05-08 21:20:27 <psykose> nmeum: pong
2022-05-08 21:20:32 <psykose> appears i broke all the bootstrapping eh :)
2022-05-09 07:11:27 <nmeum> psykose: breaking bootstrapping is fine, happens all the time :) just had some questions regarding the rust aport but I think I sorted those out
2022-05-09 07:11:50 <psykose> yeah, sadly i don't know why the compiler fails :c
2022-05-09 07:26:47 <nmeum> the stage2 builds fine but stage3 seems a bit messy, I think I will try to do build stage2 again without our alpine-specific triplet (and patches) and check if it also crashes and if so report that upstream?
2022-05-09 07:27:24 <nmeum> seems to me that rustc on riscv64 musl is not well tested in general since the stage2 didn't even compile without libc crate patches
2022-05-09 07:32:22 <psykose> mhm
2022-05-09 07:32:28 <psykose> i bet almost nobody has it working
2022-05-09 07:32:45 <psykose> so, would be nice if upstream looked at it
2022-05-09 07:36:13 <nmeum> right, but I bet rust upstream doesn't like bug reports with custom triplets
2022-05-09 07:38:00 <psykose> the only thing our custom triple sets is non-static crt default and pie, and then there's some stray patches
2022-05-09 07:38:04 <psykose> i don't think the triple really matters
2022-05-09 07:40:06 <psykose> (and fwiw they've already accepted the non-static crt default for musl upstream, just haven't actually made it yet, so that part is okay anyway)
2022-05-09 07:47:30 <nmeum> so you are suggesting just reporting this upstream as is?
2022-05-09 07:48:05 <nmeum> do you have a link for the "non-static crt default for musl" discussion upstream?
2022-05-09 07:55:43 <psykose> ttthis i think https://github.com/rust-lang/compiler-team/issues/422
2022-05-09 07:55:49 <psykose> but really this discussion spans like 30 issue pages
2022-05-09 07:56:52 <psykose> well, unless they explicitly close issues that are not unknown triples instantly, i think the people will understand that the triple is not the cause of the segfaults
2022-05-09 07:57:28 <psykose> and.. you can probably reproduce the same issue by just dropping the triple patch anyway, even with the slight difference
2022-05-09 08:00:11 <nmeum> alright, I guess I will write a bug report later today then. I suppose I can still build it without the patches if they explicitly ask me to do so. thanks :)
2022-05-09 21:30:39 <EvTheFuture> I upgraded edge today (have been to busy at work lately) and I just wonder if something have changed regarding kernel modules or kernel config or some other change that I have missed. I get some errors when booting on 5.15.36, things like unknown filesystem vfat when mounting /boot/efi. When reverting back to 5.15.24 it boots just fine. I also don't have any working wifi in
2022-05-09 21:30:41 <EvTheFuture> 5.15.36-lts but that also work in 5.15.24-lts.
2022-05-09 21:33:17 <xordspar0> HRio: Re zfs issues with Linux 5.15.37+, I built zfs-lts 2.1.4 from aports master, and I can confirm that it fixes the nginx sendfile issues.
2022-05-09 21:34:36 <xordspar0> I would vote to upgrade zfs-lts 2.1.2 -> 2.1.4 in stable.
2022-05-09 21:34:40 <craftyguy_> EvTheFuture: it kind of sounds like your upgrade wasn't successful, like /lib/modules/5.15.36 might be incomplete/missing on your system
2022-05-09 21:35:23 <craftyguy_> EvTheFuture: the changes today to upgrade to 5.15.37 were just a version bump and nothing to do with packaging really: https://git.alpinelinux.org/aports/commit/main/linux-lts?id=a79940306e76efb11382ab87dae551ed709cb0b1
2022-05-09 21:36:35 <EvTheFuture> craftyguy_: I haven't upgraded for some time so it might not be a recent change it can be a week or two or maybe even three weeks old.
2022-05-09 21:40:06 <EvTheFuture> Anyway, I got it working on the old 5.15.24 so I can work tomorrow. Will try to investigate tomorrow evening.
2022-05-09 21:41:39 <craftyguy> EvTheFuture: ah. maybe something in here broke it for you: https://git.alpinelinux.org/aports/commit/main/linux-lts?id=f2d708907ba2fccc8b499c588f713b47d5cba2ed
2022-05-09 21:42:03 <craftyguy> or something else in the git log since 5.15.24: https://git.alpinelinux.org/aports/log/main/linux-lts
2022-05-09 23:13:30 <malvo> /join #s6
2022-05-09 23:13:40 <Hello71> malvo: i'm ok, thanks
2022-05-09 23:13:55 <malvo> trying out a new irc client lmao
2022-05-09 23:13:57 <Hello71> EvTheFuture: you didn't reboot after upgrading
2022-05-10 00:04:14 <skarnet> malvo: excellent idea :D
2022-05-10 05:11:33 <HRio> xordspar0: Thanks I created #13797 to track this
2022-05-10 05:12:59 <xordspar0> HRio: Thanks!
2022-05-10 05:50:17 <EvTheFuture> Hello71: I did and when booting again is when it fails.
2022-05-10 08:45:52 <ncopa> I'm working on #13797
2022-05-10 09:13:21 <HRio> ncopa: thanks
2022-05-10 15:01:33 <Piraty> does abuild build in a (namespaced?) chroot by default?
2022-05-10 15:01:33 <Piraty> what's the abuild equivalent of `xbps-src pkg foo`? (in case anyone knows) i aim for the resulting apk file and https://wiki.alpinelinux.org/wiki/Abuild_and_Helpers#abuild didn't seem to produce one (or i don't know where to look
2022-05-10 15:10:47 <Piraty> found it. $HOME/packages . duh
2022-05-10 15:11:48 <ikke> Piraty: you need rootbld to build in a chroot
2022-05-10 15:12:46 <Piraty> so all the packages it is installing (due to -r) , are installed into / ?
2022-05-10 15:13:10 <ikke> yes
2022-05-10 15:13:16 <Piraty> >/
2022-05-10 15:13:17 <Piraty> ;/
2022-05-10 15:13:20 <ikke> and afterwards removed again
2022-05-10 15:13:22 <ikke> but yes
2022-05-10 15:13:29 <Piraty> odd
2022-05-10 15:22:48 <ncopa> 113 passed, 19 skipped in 617.09s (0:10:17) 
2022-05-10 15:23:04 <ncopa> i have added a few tests to test diskless installs
2022-05-10 15:23:16 <ncopa> i now only have data disk
2022-05-10 15:23:27 <ncopa> i now only have data disk left
2022-05-10 15:23:39 <ncopa> but I guess its enough to create to tag a rc?
2022-05-10 15:24:02 <ncopa> oh, I should also add a test for the xen iso
2022-05-10 15:24:36 <ncopa> i wonder if there are some easy way to create multiples qemu guest with a shared user network?
2022-05-10 15:25:41 <ikke> Create a bridge and connect them all to that bridge?
2022-05-10 15:26:14 <ikke> It does require root permissions though
2022-05-10 15:26:23 <panekj> slirp4netns?
2022-05-10 15:31:13 <Hello71> easy way is to use -net bridge, but requires root as ikke said
2022-05-10 15:32:18 <Hello71> -net user can be ok if you only want some limited ports
2022-05-10 15:32:46 <Hello71> -net socket is the general mechanism
2022-05-10 15:33:14 <Hello71> or -net vde, if you want to use vde
2022-05-10 15:33:33 <ncopa> looks like -net socket is the way to go
2022-05-10 15:33:50 <ncopa> i wonder if we should add a test for nfs server/client
2022-05-10 15:34:07 <ncopa> https://gitlab.alpinelinux.org/alpine/aports/-/issues/13789
2022-05-10 15:34:39 <ncopa> i guess that adding a test for that is not a high prio (yet)
2022-05-10 15:36:00 <ncopa> we do 3.16_rc1 then?
2022-05-10 15:36:16 <ncopa> riscv builder is still not idle, but I guess it never is?
2022-05-10 16:33:16 <andypost[m]> ncopa: better to wait a bit for removal php7 from community
2022-05-10 16:34:04 <andypost[m]> the blocker is #13460
2022-05-10 16:40:58 <ikke> andypost[m]: When I have time, I'll see if the latest release still has issues
2022-05-10 16:47:36 <Piraty> src/print.c:85:17: error: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result]
2022-05-10 16:47:40 <Piraty> -Werror ...
2022-05-10 16:53:00 <ikke> export CFLAGS="$CFLAGS -Wno-error"
2022-05-10 17:49:21 <andypost[m]> ikke: maybe we'll do switch and fix reports if they come in 3.16,  I wanna remove php7 before tagging RC
2022-05-10 17:50:00 <craftyguy> at what point do packaging changes merged into aports stop showing up in what will eventually become 3.16?
2022-05-10 17:50:43 <ikke> once ncopa created the 3.16-stable branch
2022-05-10 17:50:49 <craftyguy> like if I send a patch now to something in main or community in aports/master, will it show up in 3.16? or did I miss the cutoff (or is this mentioned somewhere and I missed it)
2022-05-10 17:50:51 <ikke> and switchees the buidlers over to follow that
2022-05-10 17:50:58 <ikke> No, that happes at release
2022-05-10 17:51:13 <ikke> so when v3.16.0 is tagged
2022-05-10 17:51:23 <craftyguy> ok I see. I just saw some mention of an RC earlier, *typically* in other projects that means there's already a branch, so I was confused :)
2022-05-10 17:51:41 <craftyguy> ikke: got it, thanks for clarifying :)
2022-05-10 17:54:38 <andypost[m]> ikke: is it ok to move php81 to community at this point? I think it's good to ship both releases
2022-05-10 17:55:12 <andypost[m]> In June php82 coming to testing
2022-05-10 17:55:33 <ikke> Yeah, I don't see why not
2022-05-10 17:56:28 <andypost[m]> Ubuntu'22 even set it default!?
2022-05-10 18:11:53 <psykose> that reminds me to move ceph17 to community
2022-05-10 20:52:54 <ikke> golang releases
2022-05-10 20:55:47 <psykose> just syscall fixes
2022-05-10 20:55:51 <psykose> security wise
2022-05-10 20:56:00 <psykose> where was that script to find everything to rebuild again
2022-05-10 20:57:17 <ikke> part of atools
2022-05-10 20:58:58 <psykose> ah, i see
2022-05-10 21:00:56 <psykose> i assume the golang.org/x/ packages are not the same as the ones from std?
2022-05-10 21:01:03 <psykose> this doesn't seem to print anything from go base
2022-05-10 21:01:16 <ikke> correct, they are external modules
2022-05-10 21:02:05 <psykose> well, that seems completely useless to find out what to rebuild then
2022-05-10 21:02:08 <psykose> unless i missed something
2022-05-10 21:02:39 <psykose> i guess there's no easy way at all then
2022-05-10 21:07:48 <psykose> and even if we used this for periodic scanning of external modules, it doesn't print versions of them, so it's not useful for that either
2022-05-10 21:08:11 <psykose> i guess the information is not there at all
2022-05-10 21:08:15 <psykose> unfortunate
2022-05-10 21:46:42 <EvTheFuture> I built linux-lts 5.15.35 and that boots just fine on my laptop. However something seems to have happened witn NM. I have to connect to wifi manually with wpa_supplicant. I'll try to build later versions to try to figure out if/when it stopped working.
2022-05-10 21:47:49 <craftyguy> EvTheFuture: networkmanager recently split off the wifi stuff into a separate subpackage, so make sure networkmanager-wifi is installed
2022-05-10 21:50:37 <EvTheFuture> craftyguy: Ah, thanks that must be it...
2022-05-10 21:55:42 <craftyguy> ya that one tripped up a few folks :P
2022-05-10 22:18:00 <EvTheFuture> It seems like the kernel issue was a false alarm as well. upgraded again (after have booted ith manually built linux-lts v 5.15.36) witj apk upgrade -a which installed the latest one which booted just fine. Weird... but I'm happy it works.
2022-05-11 05:33:56 <ncopa> morning
2022-05-11 05:35:26 <ncopa> craftyguy: the idea is that we push everythign to git master til we tag a release and do the branching then. The idea is to encourage everyone to help getting the release out rather than start work on next new features
2022-05-11 05:47:55 <craftyguy> ncopa: ah, that makes sense. thanks for explaining :)
2022-05-11 06:04:25 <EvTheFuture> Anyone more than me that got problems with the new version of PipeWire when using bluetooth headset profile? For me the source is starting up in SUSPENDED state and it looks like i can't resume the source... I have to test mor though...
2022-05-11 06:06:43 <craftyguy> hmm, not that I've noticed. how new is the pipewire update?
2022-05-11 06:07:05 <craftyguy> 
ACTION hasn't used his bluetooth headset in about a day, but it worked the last time

2022-05-11 06:07:44 <craftyguy> ah the last pipewire update is >1 week
2022-05-11 06:09:22 <EvTheFuture> pipewire-0.3.51-r0 x86_64 {pipewire} (LGPL-2.1-or-later) [installed]
2022-05-11 06:11:12 <EvTheFuture> At the moment I have to use the internal microphone in the computer since the headset source always end up in the state SUSPENDED... wonder if any config files have changed... I'll dig into it when I have more time after all meetings :)
2022-05-11 06:38:05 <EvTheFuture> When looking at the pipewire log, it looks like it goes straight from creating to suspended when the headset is being connected: impl-node.c:  379 node_update_state()] (bluez_input.XX_XX_XX_XX_XX_XX.headset-head-unit-268) creating -> suspended
2022-05-11 06:50:41 <indy> hi all any plans for 3.16?
2022-05-11 06:51:06 <ikke> Yes, it's in the works
2022-05-11 06:51:24 <ikke> ncopa wants to tag the first rc soon
2022-05-11 06:51:27 <indy> ikke, is there any tracker on gitlab?
2022-05-11 06:52:02 <indy> i saw this - https://gitlab.alpinelinux.org/alpine/tsc/-/issues/40
2022-05-11 06:52:08 <HRio> morning need help merging https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/34275 into main
2022-05-11 06:52:58 <indy> ikke, ncopa but it looks like far from release
2022-05-11 06:59:22 <ikke> https://gitlab.alpinelinux.org/alpine/aports/-/milestones/183#tab-issues
2022-05-11 07:00:07 <ikke> But not all issues in that milestone will be fixed before release
2022-05-11 07:28:58 <indy> psykose, hi, i was looking for !33100 ci job but was not able to find it, tried pipelines, jobs (your message from 2022-04-11 15:58:30 )
2022-05-11 07:29:19 <indy> ha
2022-05-11 07:29:33 <indy> it was merge request :)
2022-05-11 07:29:43 <indy> algitbot, thanks :)
2022-05-11 07:47:06 <indy> psykose, ignore it, it is already in edge, great
2022-05-11 14:17:46 <EvTheFuture> Just a quick update of my headset problem. I reverted back to pipewire 0.3.50 and now the bluetooth headset source is in state RUNNING and it can be used. In version 0.3.51 it immedietly goes from CREATING to SUSPENDED... Have anyone heard if anyone else have seen this issue?
2022-05-11 17:17:17 <craftyguy> EvTheFuture: the changelog for 0.3.51 mentions only 1 bluetooth change: https://github.com/PipeWire/pipewire/blob/master/NEWS#L78
2022-05-11 17:17:23 <craftyguy> but maybe it is a regression?
2022-05-11 17:17:47 <craftyguy> I'd probably report it upstream at this point, if reverting back to 0.3.50 "fixes" it
2022-05-11 17:19:22 <craftyguy> oops here's the upstream link: https://gitlab.freedesktop.org/pipewire/pipewire/-/blob/master/NEWS#L78
2022-05-11 17:19:30 <craftyguy> stupid github mirrors polluting search results
2022-05-11 17:19:39 <psykose> if you know how to bisect you can try that :)
2022-05-11 17:20:56 <craftyguy> ya that's honestly the best way to move forward on that problem :D
2022-05-11 17:22:17 <EvTheFuture> craftyg: Thanks. I also saw that there where no obvious changes to this, but just wanted to know if anyone else stumbled upon this. I might have a bit of a different setup than most people since I use Alpine as a KVM host and run everything in separate VMs and push the audio via a separate network interface from the VMs. Might have been some config changes, bit I checked earlier
2022-05-11 17:22:19 <EvTheFuture> and nothing obvious had changed. But I suspect it might have something to do with suspend when idle maybe.
2022-05-11 17:24:11 <EvTheFuture> psykose: the biggest challenge I guess is finding time :D
2022-05-11 18:56:28 <ncopa> Ariadne: btw... I have been testing kyua a bit today. its pretty nice
2022-05-11 18:56:34 <ncopa> nicer than bats
2022-05-11 18:56:40 <Ariadne> yeah kyua is great
2022-05-11 18:57:34 <ncopa> i did find it a bit higher entry bar to get started, but once passed the initial "hello world" its pretty straightforward
2022-05-11 18:57:56 <ncopa> i think I will use much more of it in the future
2022-05-11 20:34:05 <craftyguy> ncopa: probably a silly question, but will the linux-lts kernel in edge be the same linux-lts kernel in 3.16 (i.e. kconfig enabled now in edge linux-lts will be also enabled in the 3.16 linux-lts) ?
2022-05-11 20:34:25 <ikke> yes
2022-05-11 20:34:34 <ikke> they are exactly the same atm
2022-05-11 20:34:52 <craftyguy> asking because there are some differences between the two lts kernels in edge vs 3.15, specifically some options not enabled in the 3.15 kernel that are on edge
2022-05-11 20:35:17 <craftyguy> ok, I kind of expected that answer :P
2022-05-11 20:35:18 <ikke> Enabled options are not backported by default
2022-05-11 20:35:44 <craftyguy> ok. I submitted a patch to 'backport' one option to 3.15's linux-lts
2022-05-12 11:38:35 <ncopa> im adding unit tests for alpine-conf. this is a huge improvement. now we test that `setup-* -h` is consistent. print to stdout, exit with success (instaed of error) etc
2022-05-12 11:39:06 <ncopa> and im finding bugs while at it
2022-05-12 11:39:22 <ncopa> for example `setup-proxy none` would not remove configured proxies
2022-05-12 11:40:33 <psykose> that is a giga amount of fixes right there
2022-05-12 11:40:38 <psykose> proud of you ncopa :)
2022-05-12 11:41:38 <ncopa> the best thing is that i will be much more confident when reviewing merge requests
2022-05-12 11:42:03 <ncopa> my biggest regret is that i didnt do this way sooner
2022-05-12 11:57:29 <skarnet> I want to believe my insistence played a part in motivating you to do it :)
2022-05-12 13:49:03 <Ermine> Great job guys!
2022-05-12 14:25:55 <Nulo> Is there a reason why a patch release for 3.15 hasn't been released along with the openssl patch?
2022-05-12 14:26:20 <Nulo> Also: why weren't other branches patched?
2022-05-12 14:27:19 <ncopa> which openssl patch?
2022-05-12 14:28:02 <ncopa> this? 9dac81a0eecfa45770f930d15a84793a31625a06
2022-05-12 14:29:14 <ncopa> looks like we were not affected by it
2022-05-12 14:30:33 <ikke> !34181 no additional details though
2022-05-12 14:31:43 <Nulo> ncopa: where does it say that?
2022-05-12 14:32:02 <ncopa> https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/34181/diffs#ec642615cc0564dfdbb98166ff142d5ef9e81ca7_51_51
2022-05-12 14:32:14 <ncopa> fixed in version '0'
2022-05-12 14:32:24 <ncopa> which means it never affected us
2022-05-12 14:32:32 <Nulo> Huh.
2022-05-12 14:32:49 <ncopa> also https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1292
2022-05-12 14:33:26 <ncopa> "The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner ..."
2022-05-12 14:33:29 <ikke> Oh, we don't ship that script
2022-05-12 14:33:31 <ikke> that;s why
2022-05-12 14:33:36 <ncopa> we dont use the c_rehash script
2022-05-12 14:33:50 <ncopa> but at some point we did, so i think the secixes info is technically wrong
2022-05-12 14:34:11 <Nulo> Yeah, it gets explicitly deleted in the package
2022-05-12 14:34:18 <Nulo> s/package/APKBUILD
2022-05-12 14:34:18 <alpine-meetbot> Nulo meant to say: Yeah, it gets explicitly deleted in the APKBUILD
2022-05-12 14:35:01 <Nulo> All other CVEs in https://www.openssl.org/news/secadv/20220503.txt are for OpenSSL 3.0. I guess Alpine dodged that bullet (?)
2022-05-12 14:35:46 <panekj> or we have good devs :)
2022-05-12 14:36:11 <Nulo> Dodged the bullet _because_ of good technical decisions
2022-05-12 14:36:30 <ncopa> aa83340f268830cb09ffae6d2af3f0b87f8b56bd
2022-05-12 14:36:47 <Nulo> Ah, I thought OpenSSL 3 wasn't packaged at all
2022-05-12 14:36:54 <ncopa> but, yeah, no hurry to make new release
2022-05-12 14:41:26 <Nulo> As far as I can tell, only spdk in testing depends on openssl3 https://pkgs.alpinelinux.org/package/edge/testing/x86_64/spdk
2022-05-12 14:49:10 <Hello71> amusing bug: alpine hangs when booting in qemu with -vga virtio, but only when the window is maximized.
2022-05-12 14:50:40 <Hello71> it prints "Kernel panic - not syncing: System is deadlocked on memory", but only to serial
2022-05-12 14:51:34 <Hello71> i wonder if this is related to people reporting that alpine hangs on boot; something is going wrong and kernel panics but for some reason doesn't display the message
2022-05-12 14:52:05 <Hello71> i wonder if possibly mkinitfs is doing something that causes the errors to not be displayed
2022-05-12 23:50:48 <psykose> ncopa: i tried to find the first version, actually
2022-05-12 23:50:55 <psykose> but i found that script was being deleted like 6 years ago
2022-05-12 23:50:58 <psykose> or.. more
2022-05-12 23:51:04 <psykose> i think it was since 2.x days, or maybe 3.0
2022-05-12 23:51:23 <psykose> so i thought 0: made more sense as otherwise it's some ancient version anyway, but i suppose it can be updated
2022-05-13 03:38:56 <ikke> psykose: but the stable branches were never affected at least
2022-05-13 03:39:08 <psykose> not the current ones, no
2022-05-13 03:39:31 <ikke> nod
2022-05-13 05:37:48 <craftyguy> psykose: thank you for the help with the boost1.77 patches :D
2022-05-13 05:37:53 <psykose> :)
2022-05-13 05:37:58 <psykose> i am also working in boost 1.78 right now
2022-05-13 05:38:19 <psykose> seems to be unordinary so if the rebuilds work then i guess i will send it
2022-05-13 05:38:33 <craftyguy> are those patches in 1.78?
2022-05-13 05:38:56 <psykose> they are backported from 1.78
2022-05-13 05:39:04 <craftyguy> ah nice
2022-05-13 05:39:09 <psykose> (or boost-math-standalone-1.77, technically since they are there too)
2022-05-13 05:39:30 <psykose> and the geometry one no idea, but it is in 1.78 as well
2022-05-13 05:39:38 <craftyguy> ok
2022-05-13 05:53:55 <craftyguy> is this an acceptable backport to 3.15? https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/34264
2022-05-13 05:54:29 <psykose> only if ncopa is fine with it
2022-05-13 05:54:44 <psykose> note it will also need a pkgrel bump for all the -lts kernel module packages
2022-05-13 05:56:11 <craftyguy> ah
2022-05-13 05:58:57 <craftyguy> probably best to make that change then when the lts kernel gets another bump(?)
2022-05-13 05:59:09 <craftyguy> (assuming ncopa is OK with it, heh)
2022-05-13 05:59:58 <psykose> more or less
2022-05-13 06:48:46 <ncopa> morning
2022-05-13 06:49:47 <ncopa> craftyguy: yeah, i think that is acceptable. will have a look at it, but not sure if it will be today
2022-05-13 06:50:21 <ncopa> and yes, i will do it with the next kernel bump. 5.15.39 is out already, so it should be in too far future
2022-05-13 06:51:45 <ncopa> btw, you dont need to bother bump pkgrel for that. I cna manually cherry-pick it together with the version bump.
2022-05-13 06:51:58 <ncopa> the reason is that we also need to rebuild the 3dparty kernel modules
2022-05-13 14:59:21 <ddevault> Ariadne: did you ever have another go at rust on rv64
2022-05-13 15:09:34 <ikke> ddevault: nmeum_ tried the other day
2022-05-13 15:09:38 <ikke> got to stage2
2022-05-13 15:10:09 <ikke> stage2 was not working properly though
2022-05-13 15:27:18 <ddevault> aight
2022-05-13 15:27:28 <Piraty> wl-clipboard-x11 and xclip have conflicting path /usr/bin/xclip
2022-05-13 15:28:51 <Piraty> APKBUILD doesn't have a mechanism to propagate that to apk ?
2022-05-13 15:29:30 <ikke> propegate what?
2022-05-13 15:30:07 <panekj> why would you have xclip installed together with wl-clipboard-x11 ?
2022-05-13 15:30:29 <Piraty> package conflict, so apk-add will not install one (or remove the other, depending on if it's an implict dependency or explicit one)
2022-05-13 15:30:45 <panekj> it has `provides` and `replaces`
2022-05-13 15:30:45 <ikke> You can specify these packages conflict
2022-05-13 15:35:51 <Piraty> ok it does have https://git.alpinelinux.org/aports/tree/testing/wl-clipboard-x11/APKBUILD#n15 yet apk-add allows to install both and one remains broken
2022-05-13 15:37:30 <ikke> That just means you can run apk add cmd:xclip and it can select this package
2022-05-13 15:37:41 <ikke> They should directly conflict
2022-05-13 15:38:01 <ikke> by adding !xclip to the depends of wl-clipboard-x11
2022-05-13 15:40:24 <Piraty> i wasn't aware that !foo means confligs=foo
2022-05-13 15:40:40 <Piraty> conflicts=foo ofc
2022-05-13 16:56:21 <synack> I'd like to update testing/gprbuild... the package in aports is "2019" but upstream has switched to using semver and the new version is "22.0.0"... how should I handle this?
2022-05-13 16:56:51 <synack> to clarify, I'm referring to the pkgver field
2022-05-13 17:01:47 <ikke> synack: One options is to just do it
2022-05-13 17:02:02 <ikke> ie, just start using the new version scheme
2022-05-13 17:02:33 <ikke> At least when upgrading to a new major version, users are advised to use --available, which means apk will 'downgrade' it
2022-05-13 17:02:48 <synack> ooh, interesting
2022-05-13 17:34:16 <ncopa> seems like the builders are busy
2022-05-13 17:34:42 <ncopa> I was about to tag 3.16.0_rc1 but maybe I should wait til Monday
2022-05-13 17:55:33 <skarnet> it's 19:55 on a Friday evening SHIP IT
2022-05-13 18:08:44 <omni> it's just an rc... ;)
2022-05-13 18:18:48 <omni> but if you say you'll tag it on monday, perhaps folks will scrable to get heir commits in before that
2022-05-13 18:34:55 <ikke> It's just that ncopa wants the builders to be idle before making a release (to make sure there are no broken packages)
2022-05-13 18:40:14 <nmeum_> ddevault: https://github.com/rust-lang/rust/issues/96876
2022-05-13 18:41:41 <nmeum_> the stage2 packages are here https://dev.alpinelinux.org/~nmeum/edge/riscv64/ but as described in the bug report it segfaults on more complex inputs and I am simple not familiar enough with rust compiler internals to fix that on my own
2022-05-13 18:42:08 <nmeum_> *simply
2022-05-13 18:45:05 <ddevault> thanks nmeum_!
2022-05-13 18:46:54 <Ariadne> nmeum_: did you upstream the libc crate patches you had to make?
2022-05-13 18:49:11 <nmeum_> yes, I was just minor change though the biggest issue was that rustc-1.6.0 vendors an older version of the libc crate, thus I had to backport a few patches which were already upstream by someone else
2022-05-13 18:49:16 <nmeum_> *it was jist a minor change
2022-05-14 08:11:14 <Ermine> Can one move more than 1 packages between repos in a single mr? (!34395)
2022-05-14 08:20:12 <ikke> Sure, if the packages are related, it makes sense to move them at the same time
2022-05-15 01:02:26 <mochaa> I made a (rushed) acf responsive skin poc and here (https://fars.ee/-Is-) are some screenshots
2022-05-15 01:02:56 <panekj> great work
2022-05-15 01:02:57 <mochaa> if anyone have ideas or suggestions on the design please tell me ^^
2022-05-15 08:17:19 <ca1f> hello, I'm using the aports repository to build my own customized alpinelinux livecd and that's working really lovely so far but what would be the right approach to modify packages and build and add my own packages for the livecd environment?
2022-05-15 08:44:02 <ncopa> Looks like openjdk18 is stuck on ppc64le
2022-05-15 08:52:05 <psykose> it is
2022-05-15 10:20:27 <ikke> Now not anymore
2022-05-15 18:41:21 <JuniorJPDJ> test
2022-05-15 18:41:43 <panekj> failed successfully 
2022-05-15 18:59:31 <psykose> failure successed failfully
2022-05-15 19:00:30 <JuniorJPDJ> woho, it works
2022-05-15 19:00:33 <JuniorJPDJ> thanks :D
2022-05-15 19:07:09 <JuniorJPDJ> could someone take a look?
2022-05-15 19:07:09 <JuniorJPDJ> https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/34416
2022-05-15 19:07:23 <JuniorJPDJ> maintainer seems to be inactive for a year
2022-05-15 19:48:47 <sam_> heh
2022-05-15 19:48:49 <sam_> https://github.com/fabaff "sporadically on.."
2022-05-15 19:51:21 <ikke> it's not untrue
2022-05-15 19:55:06 <ikke> Seems they are active in nix packages 
2022-05-16 04:57:42 <skarnet> ncopa: good morning, whenever you arrive, and thanks for publishing alpine-conf-3.14.0_rc2! this makes it possible for me to send the big thing.
2022-05-16 04:57:49 <skarnet> So, folks, here we go:
2022-05-16 04:58:02 <skarnet> !34459
2022-05-16 05:00:55 <skarnet> Full description and rationale of the changes in the MR; this impacts busybox-initscripts, alpine-base, eudev, udev-init-scripts, and cloud-init, and creates new and exciting packages; not for the sheer fun of it, but because the end layout is much more rational and logical than it was before, so please don't be afraid.
2022-05-16 05:04:17 <skarnet> merging this will also allow minimal to push his changes to cloud-init in an easier way. :)
2022-05-16 06:11:11 <ikke> I suppose ncopa will not being an rc today either
2022-05-16 06:20:20 <skarnet> not being an rc?
2022-05-16 06:20:55 <ikke> doing*
2022-05-16 06:25:47 <skarnet> as long as someone merges my MR it doesn't matter to me if an rc goes out today or not :P
2022-05-16 06:26:08 <ikke> fyi, this was not a reaction to your MR