2025-01-01 06:26:54 l0rd_hex: ok I might try it later 2025-01-01 09:58:12 hi, I did the system upgrade 3.16 -> 3.21, and encountered the following error with pppd: Error relocating /etc/ppp/plugins/rp-pppoe.so script_setenv: symbol not found. how can I fix it? 2025-01-01 10:39:43 make sure that all packages are actually updated 2025-01-01 11:24:54 hey, quick question since I can't seem to find the answer in the wiki: what exactly is needed for packages to be "finished" testing? In the wiki I only found _if there is positive feedback or for other good reasons_, if so, where could I add positive feedback? 2025-01-01 11:38:30 good question 2025-01-01 11:39:02 basically they need a maintainer, and someone that has given it a review 2025-01-01 11:39:45 historically, at a time when we didnt have CI, we pushed packages first to testing repo to verify that the package built not only on the developer machine 2025-01-01 11:39:57 it was also a way to get a package out early 2025-01-01 11:40:12 for example you coupld build a package with binary but without init.d script 2025-01-01 11:40:43 so people could test it while optimizing it (add init.d script, do package splitting properly etc) 2025-01-01 11:41:21 and it also gave a possibility to test that the package worked also when built on builder, and not only when built on developers machine 2025-01-01 11:41:43 but now that we have CI, the need for testing is not as it used to be 2025-01-01 11:42:17 now I think it is up to the maintainer to decide when it is ready to move from testing 2025-01-01 11:43:10 could be weeks, a few days, or even hours after added to testing 2025-01-01 11:43:37 basically it is when it is ready to be shipped with next alpine release 2025-01-01 11:45:09 well the "few weeks" are 3 years now for the lsd package ... and I believe an ls-like program doesn't necessarily need an init script 2025-01-01 11:45:31 it basically means that nobody cared enough 2025-01-01 11:46:04 we also talked about deleting packages in testing after 6 months, as the intention was never to have anything there permanent 2025-01-01 11:46:41 I suggest that you create a MR that moves it to community 2025-01-01 11:47:01 ok I will create an MR 2025-01-01 11:53:40 Don’t forget to visit my live cam: Join Mylive Cam chat: https://bit.ly/Mycamshow 2025-01-01 11:58:53 The maintainer should agree with moving it to community of course, because they are responsible for making sure it's a safe and up to date package in stable releases 2025-01-01 12:02:06 ok after git had to think for 9 minutes I managed to create an MR: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/77851 2025-01-01 12:02:29 but I don't really understand why gitlab thinks it must be rebased? there is only 1 commit to master since I branched off and that one doesn't conflict ... 2025-01-01 12:18:48 we use linear git history and no merge commits 2025-01-01 12:18:52 but dont worry about that 2025-01-01 12:19:32 ok thanks 2025-01-01 12:23:08 hey everyone! i'm trying to boot the mainline kernel linux-edge on an orange pi 5 plus (rk3588 chipset), but so far I'm failing. I think I'm missing one or more drivers, "spi_rockchip_sfc" especially... 2025-01-01 12:23:58 if i understand correctly, the alpine kernel is built in such a way that the driver should be loaded as a module (https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/main/linux-lts/lts.aarch64.config#L1500), but i have no such module in /lib/modules/...-edge 2025-01-01 12:24:24 would you have any idea on how i could proceed? 2025-01-01 12:43:35 green-penguin: since linux-edge is on same kernel version as linux-lts, perhaps use linux-lts. i believe lts has more drivers enabled, specifically the one you are looking for is not enabled for the edge kernel 2025-01-01 12:43:51 but is enabled for lts 2025-01-01 12:48:02 besides, until 6.13 moves to mainline/stable, 6.12 is both the mainline/stable and newest lts 2025-01-01 12:56:05 j_v: sounds like a great suggestion, gonna try that. i thought linux-lts was still on 6.6, but mixed it up with release 3.20... 2025-01-01 13:02:50 green-penguin: i find it easy to get those kind of things mixed, so understandable from my perspective 2025-01-01 13:29:11 It seems like linux-lts contains a UKI instead of a "regular" kernel image, which my old uboot can't get along with... I guess there's no trivial way to "unpack" the UKI? 2025-01-01 13:45:28 green-penguin: does you uboot support bootz instead of bootu? 2025-01-01 13:45:48 s/instead of/as well as/ 2025-01-01 13:47:57 j_v: it doesn't seem like it; the command is there, but does nothing: 2025-01-01 13:48:33 `bootz 0x00400000 0x0a200000 0x0a100000` on the uboot shell just sends me back to the shell, without any output 2025-01-01 13:50:05 until now, i booted with `booti 0x00400000 0x0a200000 0x0a100000`, although that now outputs: Bad Linux ARM64 Image magic! 2025-01-01 13:50:52 looking into it... 2025-01-01 13:51:51 i think it might have to do with the installkernel package 2025-01-01 13:52:04 i see 2025-01-01 13:52:16 which is build dep of kernel 2025-01-01 13:57:33 that's not it, kernel install just handles putting the files in the right place with consistant naming 2025-01-01 13:57:46 s/kernel install/kernelinstall/ 2025-01-01 13:58:05 hmm 2025-01-01 14:14:40 to be honest, im not quite sure i understand how/where the kernel in this efi/uki format is produced... i had a look at the build log, but didnt notice anything in particular 2025-01-01 14:15:21 but what's certain is that the .apk already contains this format, so i assume the kernel image is not converted by some postinstall script 2025-01-01 14:16:35 green-penguin: i don't believe it is uki, but it does appear to be efi, not to say that this is the case, but if it is ukified, it is in the kernel build system ithink. still looking into it. 2025-01-01 14:17:57 oh alright; i assumed it is because of the output of `file`: PE32+ executable for EFI (application), ARM64 (stripped to external PDB), 2 sections 2025-01-01 14:21:07 well, that doesn't mean it doesn't happen in the install hooks for the kernel, just like mkinitfs but for uki... i'm looking at https://wiki.alpinelinux.org/wiki/UEFI_Secure_Boot for some reference 2025-01-01 14:21:31 ahh, i see 2025-01-01 14:22:27 but looking at that wiki page suggests to me that in order to automate the uki stuff should take manual adjustment, but i may be wrong or it may have changed idk 2025-01-01 14:24:14 i think i am out of my depth, but i am willing to keep researching it, i have some time at the moment and i never mind a chance to learn 2025-01-01 14:26:22 i have some old scripts i can dig up that use uboot to start aarch64 qemu instances, will find those (i think i archived them, but should be accessable) and play around a bit... expect slowness at this point and maybe someone else who knows this stuff will jump in 2025-01-01 14:32:45 that's very nice of you, no need to rush anything, im learning quite a bit on the way too 2025-01-01 14:34:26 in the meanwhile im trying to boot collabora's fork of mainline (theyre on 6.13-something and have some patches waiting to be merged)... but they didnt include f2fs, which i use, so i have to reformat the partition 2025-01-01 14:35:01 if it works, ill have a nice base to compare linux-lts with, and see what it still might be missing... 2025-01-01 14:42:02 cool 2025-01-01 15:36:30 has anyone successfully booted a PineBook Pro (rk3399) with the latest release of towboot from an SDCard with the 3.21 uboot arm image? TowBoot works for Manjaro, but for the alpine uboot image, I see 2 potential issues. The first is that vmlinuz-lts seems to be a aarch64 PE32+ executable (EFI application) according to file. The second is that initramfs-lts only seems to contain PC firmware (no 2025-01-01 15:36:36 rockchip or brmc directories or blobs). As far as I can tell, TowBoot tries to read the extlinux/extlinux.conf file and fails to load vmlinuz-lts because it's not a valid kernel image. Then it falls back to grub config on the sd card and fails after the EFI stub messages. Thanks! 2025-01-01 15:45:50 jmsl: i have no experience with the rk3399, but im going through a similar situation with an orange pi 5 plus (rk3588); i was a bit more successful by switching from mkinitfs to dracut, which, by default, puts quite a lot in the initramfs 2025-01-01 15:47:20 that said, it would only solve your second issue... your first issue, why vmlinuz-lts gives us a PE32+ executable is a question i have yet to find an answer to... 2025-01-01 15:54:15 Thanks green-penguin! I'm currently experimenting with my own kernel builds to solve the first issue. I modified /extlinux/extlinux.conf to point to the new image and I'm rebuilding the initramfs by extracting it and editing the layout and re-compressing it. I was hoping I could raise this as an issue and help get it fixed for a future release, assuming it's not a TowBoot problem. 2025-01-01 15:55:19 The arm generic image based on the iso isn't working for me at all either. 2025-01-01 15:57:18 I did get the sd card to boot with substituting my own kernel image but the wireless didn't come up because I was missing the firmware from initramfs 2025-01-01 16:00:16 well, i have an alpine-3.21 aarch64 qemu vm up and running. it uses u-boot, which loads grub in efi mode. 2025-01-01 16:01:37 I see... in that case it might indeed be worth trying to generate a new initramfs from your kernel, but by including the necessary modules... if you know which ones you need, you might be able to stick with mkinitfs (on a running alpine machine, that said); you would have to adjust /etc/mkinitfs/mkinitfs.conf, and probably add an additional file in /etc/mkinitfs/features.d (which would point to the missing modules), or you could use dracut which 2025-01-01 16:01:39 includes more out of the box... Either way, you'd need a running linux somewhere with your kernel and your /lib/modules/ somewhere, to generate that initramfs 2025-01-01 16:01:57 (that was @jmsl) :) 2025-01-01 16:03:16 j_v: interesting, but if u-boot loads grub, i assume that means grub itself is loaded as an efi executable (which the u-boot on the orange pi cant, if im correct) 2025-01-01 16:03:44 that sounds plausible 2025-01-01 16:04:29 if somehow grub could be loaded as... something else (?), and then chainload the linux efi executable; that could work too... i wouldnt mind the extra boot time for more flexibility in terms of what can be booted 2025-01-01 16:05:22 hmmm, i will have to look into how i might emulate that for testing 2025-01-01 16:11:52 green-penguin: that is quite a sbc, the specs on that model are impressive 2025-01-01 16:13:56 the orange pi 5 plus? yea i love it :) i want to use it as a media center / streaming box; if i can get the drivers working (collabora's been doing an awesome job at improving support for that board) 2025-01-01 16:19:15 i'm looking at orange-pi's documentation and downloads section on their web page, trying to see if they have any utilities that would help either for installing images or for running an emulation 2025-01-01 16:25:28 green-penguin: can you get to the u-boot prompt, so that it doesn't try to load anything using defaults? 2025-01-01 17:13:34 j_v: sorry for the delay; yes you can get to the uboot shell by just not invoking any boot* command in your boot.cmd / boot.scr script 2025-01-01 17:14:38 what i usually do is, in my script, i load the vmlinuz, initramfs and dtb of my choice, but i call booti manually over uart serial, so that, if booting fails, i can inspect and/or correct 2025-01-01 17:23:47 well, i was wondering i the installed u-boot on the opi has the 'bootdev' cmd, as that would allow booting a boot loader from the device 2025-01-01 17:24:05 wondering i/ wondering if 2025-01-01 17:25:16 'bootdev list -p' gives list of devices 2025-01-01 17:25:16 hmm... that almost sounds too good to be trust, but i can have a look at it in a few moments out of curiosity 2025-01-01 17:29:13 s/trust/true/ 2025-01-01 17:30:38 ahh too bad, seems like my version doesn't have bootdev (yet?); it has boot, bootcmd, bootandroid, boot_fit, bootd, booti, bootm, bootp and bootz 2025-01-01 17:30:55 `version` outputs: U-Boot 2017.09-orangepi (Nov 15 2023 - 16:53:25 +0800) 2025-01-01 17:31:54 wonder why the o-pi ppl went with what seems to be such an old version of uboot... 2025-01-01 17:32:32 could be age, or could be configured build options 2025-01-01 17:33:43 my u-boot foo is pretty old, was just poking around the qemu vm booting 2025-01-01 17:37:39 but unfortunately, i don't know all of what is available on that opi 2025-01-01 17:37:52 for u-boot command 2025-01-01 17:37:54 for u-boot commands 2025-01-01 17:58:45 green-penguin: sorry, i'm out of ideas 2025-01-01 18:00:25 all good, it's part of the game hehe... @minimal just pointed out linux-lts is built with CONFIG_EFI_ZBOOT, so either i figure how to manually convert the kernel image to a regular one, or i flash the board (which i really dont want to do) 2025-01-01 18:01:28 or i fork aports, and build it myself... getting familiar with the alpine build tools has been on my todo list for quite a while anyway 2025-01-01 18:02:52 even though... if i understand it correctly, this issue probably affects a lot of SBCs that are not raspberry pi... maybe alpine will offer some degree of flexibility here in the future (a separate linux-* package?) 2025-01-01 18:03:17 green-penguin: one nice thing is you don't actually have to fork the whole of aport repo in order to build a modified or local aport 2025-01-01 18:04:43 i keep a mini repo for my local aports, mostly stuff that customized or tweaded to my prefs, so that are exotic stuff i figure would little interest from others 2025-01-01 18:04:59 s/tweaded/tweaked/ 2025-01-01 18:05:01 oh! good to know, that sounds very useful! 2025-01-01 18:05:41 i'm used to void linux where i'd have to clone/fetch the whole void packages repo, i didnt grow fond of that approach 2025-01-01 18:07:00 it doesn't hurt to at least do a shallow clone of aports but as long as I specify APORTSDIR=$my_repo_path when calling abuild rootbld, it works as I need it 2025-01-01 18:08:19 i've always meant to try void (and chimera also) just havent' gotten round tuit. i have a chimera chroot, i should set up a void chroot 2025-01-01 18:11:49 it can be nice, especially if you're looking for a very bare-metal rolling release... i also had things (e.g. kde, because of some inconsistencies in the build process) break badly due to the nature of how new package versions are released 2025-01-01 18:12:18 i still run it on my desktop, but i wouldnt choose it anymore, if i were to reinstall 2025-01-01 18:13:40 ah, yeah, for me, my DE needs are so basic, using wm plus mixture of utils that do what i like/need, breakage happens a lot less (usually the finger points back at me) 2025-01-01 18:36:07 @green-penguin, you may want to take a look at tow-boot, which will chain load other boot loaders from other devices. I use it on my PineBook 64 "Pro" because it gives me a boot menu for switching between, internal flash storage (64gb), the sd card, and usb. I can use "generic" arm (non-uboot) Manjaro efi images with it. It seems like the alpine uboot install image may also ship an old version of uboot 2025-01-01 18:36:13 that might have issues with the 3588 as well, I follwed the directions here https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/upstream_uboot.md to build my own copy of uboot for the 3399 and install it with the update-uboot script in the alpine uboot image. Now that I have my own kernel working, I should go back and see if my version of uboot replacing 2025-01-01 18:36:19 the one installed on the sd card with dd, actually improves anything. Tow-boot is supposed to allow any os for the architecture to load from any device without touching the firmware. The Pinebook pro has a separate 16meg firmware chip that is blank by default but can be selected by a hardware switch, so towboot comes up first, then defaults to emmc, but can be interrupted and changed to another 2025-01-01 18:36:25 removable device. Your orange-pi may be different though. 2025-01-01 18:37:05 the tow-boot gitlab issue list might be helpful too 2025-01-01 18:37:30 sorry, tow-boot github 2025-01-01 18:37:53 If nothing else I'm learning a lot about all the different arm boot methods lately :) 2025-01-01 18:38:51 Heh, same here... i haven't looked into tow-boot yet, seems like a nice idea! 2025-01-01 20:39:53 is there a default apkovl name that i can load anytime regardless of the hostname? am trying to raise a swarm 2025-01-01 20:52:11 nu[m]: I think localhost works that way 2025-01-01 21:28:31 looks like ${anything}.apkovl.tar.gz will get picked up, and the $anything doesnt influence what the end hostname will be 2025-01-01 21:30:05 no clue now why the docs tell that i need to put hostname there, seems to be pointless, anyway, glad it works! lbu is awesome 2025-01-01 23:28:07 hello 2025-01-01 23:28:16 I have a question 2025-01-01 23:28:21 I hope it is not too complex 2025-01-01 23:28:36 I have previously installed Alpine Linux on my laptop in a dualboot setup 2025-01-01 23:28:46 Due to reasons I had to remove linux off my laptop 2025-01-01 23:29:00 I have now decided to reinstall alpine using the 3.21 standard x86 64 image 2025-01-01 23:29:49 I did the install procedures (I may be missing something) of mounting my to-be root partition on /mnt, mounting my EFI/ESP Partition on /mnt/boot/efi and then running setup-disk -m sys /mnt 2025-01-01 23:30:08 why is alpine site looking like this? https://i.imgur.com/Vgc0Noo.png 2025-01-01 23:30:17 However what then happens is the install gives an error of not having the grub-install command 2025-01-02 01:14:49 userdocs: what url? 2025-01-02 01:34:37 looks like APKBUILD for gcc 2025-01-02 07:18:37 it's the dark theme for cgit 2025-01-02 10:15:05 hi all, apk question - can i defer 1) execution of scripts in apk 2) installation of dependencies 2025-01-02 10:20:46 case is, i have container which is installing python3, and lot of py3- packages which are depending on python3, those py3- packages are not updating frequently compared to python3 and its deps like sqlite-libs 2025-01-02 10:23:23 each group install having own "run apk add" to have 'own layer' so upgrade path will consume less traffic on heavily throttled line 2025-01-02 10:25:06 pj: yes it was from here https://git.alpinelinux.org/aports/tree/main/gcc/APKBUILD 2025-01-02 10:25:33 it looks the same on any browser i use 2025-01-02 10:25:48 the link doesn't matter, it's cgit theme that is broken 2025-01-02 10:27:42 i'm personally invested in that particular link. 2025-01-02 10:55:29 Is there way to use an alternative dhcp client ? udhcpc won't set the default route for some reason (from udhcpd on debian) 2025-01-02 10:56:02 xpufx: yeah, simply apk add dhcpcd and thats it 2025-01-02 11:00:06 ah. i didnt' realize that was a different name in the package list. thanks. 2025-01-02 11:06:45 that did not set the default route either. I will have to fix this on the server side i think. 2025-01-02 11:20:06 I think it doesn't like mixing 'option router' with 'static route' though there's a seemingly identical other server where it works fine 2025-01-02 11:20:53 on other distros 2025-01-02 11:23:22 is there an equivalent to the AUR (ArchLinux user repository) for alpine? In particular I am using hickory-dns on my arch system as a dns over tls resolver which I have packaged in the AUR so other ppl can use it as well and the package seems to be missing in alpine 2025-01-02 11:24:51 msrd0: there's the community repo 2025-01-02 11:25:20 can anyone be a maintainer there? 2025-01-02 11:25:32 I believe in arch you need to be some kind of trusted user for that 2025-01-02 11:25:59 "Packages in community repository are those made by users in team with the official developers and close to the Alpine package process. They are supported by those user(s) contributions and could end if the user(s) stops; they may also be removed in a future release due to lack of support by upstream authors. " 2025-01-02 11:26:21 it sounds like you have to tell somebody here that you want to package it, then follow the procedure and then have it accepted into Community 2025-01-02 11:37:02 Submitting packages to alpine isn't hard 2025-01-02 11:40:56 Create a build manifest and open merge request, apart from stylic choices and licencing there isn't much of a requirements/constraints 2025-01-02 12:09:14 https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package 2025-01-02 12:09:29 (and if something is missing on that page, please add it) 2025-01-02 12:17:01 as for my dhcp thing. it looks like static routes and router cannot be mixed and i need to push the default gw as a 0.0.0.0/24 static route. Tiny little bit of complication with dual nic dual dhcp nodes but i can fix that with 'metric' 2025-01-02 12:23:13 interesting. alpine doesn't seem to use that as default route. 2025-01-02 12:27:53 my bad. had to be 0.0.0.0/0 2025-01-02 14:32:04 Good afternoon. I am hoping to use an Alpine Linux 3.21 cloud image LXC container, but can't get sshd public key authentication to work. When I use the same cloud-init config with a debian image it works. I have set a root password but that doesn't make a difference. Can anybody help me with this? 2025-01-02 14:36:43 "(and if something is missing..." <- found something that is missing: how do I add a directory that should _not_ get replaced on update, similar to /etc? 2025-01-02 14:38:13 msrd0: depends on the usecasw 2025-01-02 14:39:01 for /etc we just install it similar to other package data. if the user changes the config, apk-tools wont override it and instead saves it to a .apk-new file instead 2025-01-02 14:39:38 The default config of hickory-dns configures some zones like example.com and locates the zone files in /var/named. So to have a the example config from upstream runnable I need to copy those files to /var/named 2025-01-02 14:39:48 but then I don't want user changes to those files get overwritten 2025-01-02 14:39:50 if you really only want to install a file on package installation, you can write the file inside a post-install script 2025-01-02 14:40:55 hm I found /etc/apk/protected_paths.d this sounds promising 2025-01-02 14:41:18 msrd0: you _could_ write to /var/named, but really shoudn't, since the distro shoudnt touch variable data. 2025-01-02 14:42:12 you can write the zones to something like /usr/share/hickory-dns/zones and tell the user in the post-install script to manually copy these files over 2025-01-02 14:42:14 fossdd[m]: so then what do you recommend? move the directory somewhere else? ship a different default config? 2025-01-02 14:43:50 and I agree the distro shouldn't touch it, basically I thought the package just puts it there in case nothing was there before and then never touches it again 2025-01-02 14:44:18 but then again I get the feeling that those files aren't really variable data by the program but more like part of the configuration so maybe I should move them to /etc to begin with? 2025-01-02 14:44:47 that sounds reasonable, if the zones location is configurable 2025-01-02 14:45:48 putting zones in /etc feels wrong, you also don't put a database directory under /etc 2025-01-02 14:47:24 steinex: yes but I don't manually write the content of the dabatase files 2025-01-02 14:48:50 I guess then I'll just install the files to /usr/share/hickory-dns/example and replace the line in the example config file to point there and then users that want to configure it themselves can just not set that directory and have it point to /var/named again 2025-01-02 19:33:30 Why is the firefox binary in /usr/lib/firefox/firefox? /usr/bin/firefox is just a shell script that exec's? 2025-01-02 19:38:32 WhyNotHugo: https://github.com/alpinelinux/aports/blob/cd49aca202848e1c012469da0855a3582987e450/community/firefox/APKBUILD#L744-L751 2025-01-02 19:39:53 I mean, unless you want 2+ copies of the firefox binary wasting space on your system :P 2025-01-02 19:41:17 I have vague memories of seeing this issue already, many years ago. 2025-01-02 19:42:04 I wouldn't want to copies, but having two copies was a hack in the first place to support Mozilla's updater 14 years ago. 2025-01-02 19:42:16 This updater isn't even relevant on distributions. 2025-01-02 23:12:26 WhyNotHugo: If I remember correctly the directory of the binary is used as appdata dir. So moving/symlinking the binary doesn't work. 2025-01-02 23:29:19 is the framebuffer usable as a daily driver? seems to cause some window cycling problems with feh and mpv, and qutebrowser wont show webpages, ff works tho 2025-01-03 07:54:05 finally got xorg/graphics to work well on rpi5, had to make a file in xorg.conf.d, search for "PrimaryGPU" on this page https://forums.gentoo.org/viewtopic-t-1166167.html?sid=129c421f6cd6c050a3d48a1f2eeeda79 dunno if it could be good to add it to the alpine raspberry wiki 2025-01-03 07:56:23 also if you use dtoverlay=vc4-fkms-v3d you get no soundcard through hdmi, if you use dtoverlay=vc4-kms-v3d you have to have edge it seems or you get no hdmi output, even with edge you only get hdmi output when its almost done booting. 2025-01-03 08:56:20 hmm, seems i can only play audio from _one_ source at the time through hdmi now tho (using only alsa) 2025-01-03 10:29:31 yeah, didnt work 2025-01-03 10:31:02 :( 2025-01-03 10:31:57 ups,wrong chan for that last comment 2025-01-03 14:03:17 sertonix[m]: yeah, i tied and it seems to be the case, looks like it hardcodes $(pwd) to find its data files 2025-01-03 15:39:04 not sure i notice great improvement going from rpi4 to rpi5... 2025-01-04 05:38:07 !next 2025-01-04 05:38:14 .next 2025-01-04 05:38:31 @next 2025-01-04 05:38:33 p = p->next; 2025-01-04 10:01:38 is there some tool to handle .apk-new files after an upgrade or do I need to do this manually? 2025-01-04 12:24:28 there is a script named update-conf from alpine-conf 2025-01-04 12:24:46 steinex: or you can just ignore them 2025-01-04 12:25:43 qaqland: thanks! 2025-01-04 12:26:29 you are welcome 2025-01-04 13:46:11 could somebody please confirm my gitlab account? the recaptcha crap makes it annoyingly hard to login/register 2025-01-04 15:21:12 hi; just wanted to know if it's true that Alpine compiles its packages with -Os. thanks 2025-01-04 15:22:26 is there an easy way to let apk cache all downloads and not just the index, similar to how pacman downloads all .pkg files to /var/cache/pacman? 2025-01-04 15:27:51 ppw: The default config for abuild sets -Os for all compilers and -O1 for the linker 2025-01-04 15:33:50 thanks 2025-01-04 15:54:15 ppw: there are certain exceptions where packages are compiled with -O2 due to it yielding much better performance vs size 2025-01-04 15:54:30 oh? is there a list? 2025-01-04 15:55:00 not really, it's kind of a mess currently since some packages have hardcoded -O2 in build manifest and some replace -Os with -O2 2025-01-04 15:55:12 few I recall are musl, python, perl 2025-01-04 15:55:48 what about gcc, clang, glibc, and the kernel 2025-01-04 15:56:13 oh, right, alpine doesn't use glibc 2025-01-04 15:57:22 gcc, clang also have -O2 2025-01-04 15:57:44 ah. and rust? 2025-01-04 15:57:47 linux has all flags unset 2025-01-04 15:57:57 rust has -Os 2025-01-04 15:58:04 I see, thanks 2025-01-04 15:58:17 i mean, rust packages have -Os, rust itself I think is also -O2 2025-01-04 15:58:43 yeah, it has -O2 hardcoded 2025-01-04 15:59:19 Im on alpine setup boot, first install, is there a way to change the resolution or font size? My 4k is terrible to read xD 2025-01-04 16:15:37 https://wiki.alpinelinux.org/wiki/Fonts#Changing_the_console_font 2025-01-04 16:15:38 this worked 2025-01-04 16:33:39 "is there an easy way to let..." <- https://wiki.alpinelinux.org/wiki/Local_APK_cache 2025-01-04 19:30:44 which text basic editor goes will(or recomended) with default xfce installation, gedit ? 2025-01-04 19:39:21 xfce has mousepad 2025-01-04 19:39:58 yes, thanks, removing gedit and installing mousepad 2025-01-04 23:57:35 Hi everyone, I'm facing an issue while installing Alpine Linux 3.21 (standard) on a Proxmox VM. During installation, at the step where I select how to use the disk (sys, data, crypt, lvm), after selecting 'sys', I encounter this error: ERROR: syslinux-6.04_pre1-r16: IO ERROR 2025-01-05 00:02:20 Hi everyone, I'm facing an issue while installing Alpine Linux 3.21 (standard) on a Proxmox VM. During installation, at the step where I select how to use the disk (sys, data, crypt, lvm), after selecting 'sys', I encounter this error: ERROR: syslinux-6.04_pre1-r16: IO ERROR 2025-01-05 00:51:36 Oh I got the broken sddm :( 2025-01-05 01:40:14 busybox fdisk doesn't support gpt, does it? 2025-01-05 02:40:50 WhyNotHugo: pretty sure not, but installer image should have sfdisk 2025-01-05 03:02:11 is there a quick way to install python3.13? 2025-01-05 03:03:28 I'm trying to build a homeassistant docker image with alpinelinux 3.21 as the base OS image and while homeassistant has moved on to python3.13 the alpinelinux package repo lists python3.12 as being the latest, even in edge 2025-01-05 03:04:58 python 3.13 only came out in like october. it's not a trivial update 2025-01-05 03:05:24 the short answer is, it'll get here eventually but you'll have to be patient 2025-01-05 03:05:36 okay, I can run an older release of homeassistant until then, thanks. 2025-01-05 03:05:51 cool 2025-01-05 03:06:23 all about the path of least resistance at this moment, enough challenges here (arch is riscv64) 2025-01-05 03:06:28 aye 2025-01-05 03:15:19 shadow: with a tool like uv, you can create a virtual env with a different python version (though it downloads a prebuilt copy of python for it) 2025-01-05 03:24:57 abby: last i checked, uv downloaded a dynamically linked python for gnu/linux, even on musl. did that change? 2025-01-05 03:32:32 I'm kind of new and unfamiliar with python. I'm iterating through a docker instance of alpinelinux, in which I set a venv and activate, then 'pip3 install homeassistant' ... so are you suggesting to venv within a venv ? I just don't know enough here to ask a good question 2025-01-05 03:33:32 shadow: usually, using pip to manage system python packages leads to overlap with system package and to breakage. 2025-01-05 03:34:09 In the case of docker, you can typically ignore this warning. Worst case you produce a broken image, rather than breaking your system 2025-01-05 03:35:53 curious. I might try this, uv is compiled for riscv64 and available in alpinelinux package repository 2025-01-05 03:37:00 WhyNotHugo: not sure, haven't checked that specifically 2025-01-05 03:37:34 you wouldn't be nesting venvs, you'd use uv to manage the venv (when you create the venv with uv you can tell it what python to use) 2025-01-05 05:52:37 $ uv python install 3.13 2025-01-05 05:52:37 error: uv does not yet provide musl Python distributions. See https://github.com/astral-sh/uv/issues/6890 to track support. 2025-01-05 05:52:56 aw i thought it did, alas 2025-01-05 06:09:46 sounds like uv should just build python in that instance 2025-01-05 06:09:52 it's not like it's a huge undertaking 2025-01-05 06:51:09 dwfreed: that depends on your hardware and may be surprising behavior 2025-01-05 06:52:10 I, for one, would not generally want opportunistic downloading of binaries: have a mode that downloads binaries and have a mode that builds 2025-01-05 07:05:08 it only downloads if you run the command to download it, iirc 2025-01-05 07:05:36 can uv build python? or that is a joke 2025-01-05 07:28:03 no 2025-01-05 07:28:31 pyenv is a similar tool that might be able to 2025-01-05 08:06:40 shadow: Looks like it might be close as the underlying project (python-build-standalone) that uv uses as the pre-built distros does have musl builds including for 3.13.1. Unless those builds are too limited due to the dynamic loading problems. 2025-01-05 14:07:59 now I got alpine on desktop I need to setup chroot or some sandbox for my packages build/build/dev 2025-01-05 15:36:34 i thought perhaps it was early for python 3.13, but some of our peers have moved on to it already 2025-01-05 16:00:02 Any chances of having "python311" or "python313" packages with only a minimal set of dependants (e.g.: those required to set up a virtualenv)? 2025-01-05 18:17:45 `depends="glibc"` 2025-01-05 18:18:04 will changing to musl work' 2025-01-05 18:22:30 https://paste.trom.tf/jiniyinisu.php 2025-01-05 18:24:22 https://paste.trom.tf/wubamozivo.makefile 2025-01-05 18:25:45 i have a really bad problem. after a reboot alpine boots into a old kernel that is not installed anymore 2025-01-05 18:25:51 no networking etc 2025-01-05 18:26:18 so what i tried is... mount /boot check vmlinz version with file... ran mkinits manually 2025-01-05 18:26:30 the files in /boot looks ok 2025-01-05 18:26:38 but it still boots an old kernel 2025-01-05 18:27:08 i checked extlinux boot prompt... the vmlinuz file is set... 2025-01-05 18:27:10 still... openrc .... old kerne 2025-01-05 18:27:11 l 2025-01-05 18:27:17 anyone with any ideas? 2025-01-05 18:27:24 its an mdraid setup 2025-01-05 18:27:26 check if you are looking at the correct boot partition 2025-01-05 18:28:02 at what level? i mean i mount it and the files look fine there 2025-01-05 18:28:34 i have just one boot partition and thats on a mdraid... 2025-01-05 18:28:34 according to your bootloader 2025-01-05 18:29:00 where to look? 2025-01-05 18:29:06 can i read out the mbr or something? 2025-01-05 18:30:22 or can i overwrite it complete? 2025-01-05 18:30:39 i even ran extlinux --install /boot 2025-01-05 18:31:07 try apk fix linux-lts while /boot is mounted 2025-01-05 18:31:16 (or whatever kernel you have installed) 2025-01-05 18:31:34 The kernel comes from the linux-lts package, not mkinitfs 2025-01-05 18:33:09 because i dont have network ( i guess that module is missing because of the wrong kernel) it ais apk unavailable skipped reinstalling linux-lts 2025-01-05 18:33:33 Is there actually something on the / fs in /boot? 2025-01-05 18:33:36 did somebody try to buil srm before? 2025-01-05 18:33:55 what i also tried. getting the apk and installing it via apk add --allow-unstrusted linux-lts... 2025-01-05 18:34:21 quinq: thats what i checked... i unmounted /boot and /boot is empty then 2025-01-05 18:34:25 ok :) 2025-01-05 18:36:03 What's your boot-loader? 2025-01-05 18:36:14 There you should be able to check what kernel it tries to load from where 2025-01-05 18:36:37 syslinux and extlinux 2025-01-05 18:36:47 it just says the vmlinuz file in there... without a version string 2025-01-05 18:37:04 but i checked it with file and it gives the the newer version 2025-01-05 18:37:09 boots still the old one 2025-01-05 18:37:33 and i dont have multiple vmlinuz files in /boot 2025-01-05 18:37:41 What's the path? 2025-01-05 18:39:25 /boot/vmlinuz-lts 2025-01-05 18:39:31 Does it work if you modify the configuration? 2025-01-05 18:39:38 to what? 2025-01-05 18:39:45 You could just cp /boot/vmlinuz-lts /boot/vmlinuz-lts-new 2025-01-05 18:39:48 And add an entry there 2025-01-05 18:39:59 Most likely it'll tell you it can't find it, but to advance a bit 2025-01-05 18:40:18 To check first that the modifications actually get applied (I suspect not), 2025-01-05 18:40:26 and then that it can find the kernel (I suspect even less) 2025-01-05 18:40:57 try it now 2025-01-05 18:41:48 nope cant find it 2025-01-05 18:41:56 But you get the new entry? 2025-01-05 18:41:57 so it checks for the wrong partition or something 2025-01-05 18:41:59 or? 2025-01-05 18:42:30 i edited it via TAB on boot and tried to boot vmlinuz-lts-foo (name of the copy) 2025-01-05 18:42:41 i dont know how to add new entries 2025-01-05 18:42:51 do i need to run extlinux --install /boot after it 2025-01-05 18:43:52 https://wiki.alpinelinux.org/wiki/Bootloaders says “The configuration file is located in /boot/extlinux.conf.” 2025-01-05 18:45:26 Are you booting with classical BIOS or with UEFI? 2025-01-05 18:45:35 classic 2025-01-05 18:45:40 doesnt add a new menu entry 2025-01-05 18:45:52 So you're booting from other medium 2025-01-05 18:47:01 no usb sticks inserted of whatever 2025-01-05 18:47:32 I mean in the broad sense, not necessarily physical media, but other partition somewhere 2025-01-05 18:48:27 maybe the apk fix would fix it for me... but i dont get networking here... i think of the missing kernel module 2025-01-05 18:49:27 so im really stuck here 2025-01-05 18:49:41 I don't think that apk fix would fix something 2025-01-05 18:49:47 The kernel is there 2025-01-05 18:49:57 Your boot-loader doesn't boot it though 2025-01-05 18:50:05 i mean i cant even find the old vmlinuz file somewhere in the filesystem 2025-01-05 18:51:47 cant i reforce a rewrite of the bootloader somehow 2025-01-05 18:55:57 what a failure to have boot on a raid 2025-01-05 18:56:08 i wonder if i can kick that out somehow 2025-01-05 18:56:39 i came a little further here 2025-01-05 18:56:49 now i have the second boot menu entry 2025-01-05 18:56:55 ah 2025-01-05 18:56:58 how? 2025-01-05 18:57:03 but it cant find the vmlinuz-lts-foo file 2025-01-05 18:57:07 that i created 2025-01-05 18:57:19 step by step :) 2025-01-05 18:57:32 so somehow it cant find the file in the boot filesystem i guess 2025-01-05 18:57:38 but now im stuck there anyway 2025-01-05 18:58:00 what did you do differently for the menu entry? 2025-01-05 18:58:31 ok if was missing the initramsfs there 2025-01-05 18:58:38 ok WTF 2025-01-05 18:58:42 it boots the copy 2025-01-05 18:58:48 with the new kernel and everything 2025-01-05 18:58:50 yeaah 2025-01-05 18:59:52 Persistence grants results :) 2025-01-05 19:00:40 ok but wtf 2025-01-05 19:01:13 like the copy plus an update-extlinux fixed something here 2025-01-05 19:01:38 Now you have a working system, you can continue on trying to fix it with apk tools, maybe 2025-01-05 19:04:24 you are right 2025-01-05 19:04:29 you helped me alot 2025-01-05 19:04:34 alot of love from me to you 2025-01-05 19:04:40 because it made me a really bad day 2025-01-05 19:06:52 You're welcome :) 2025-01-05 20:58:50 hello, world! 2025-01-05 21:13:03 "https://paste.trom.tf/wubamozivo..." <- is it possible to build srm in apline? 2025-01-06 01:34:47 hello, i have a problem with python3 and the rasperry pi3. all seems to work except python can't find the gpio package 2025-01-06 01:35:11 anybody tried this before 2025-01-06 02:03:11 Hello, is there a declarative way to prevent udhcpc from creating default routes and nameservers? In other words only accepting the address. All the proposed solutions I've found seem very hacky. 2025-01-06 04:17:28 network-noob: is that -O staticroutes ? 2025-01-06 04:18:20 though it seems that is not valid for busybox 2025-01-06 04:21:58 network-noob: https://udhcp.busybox.net/README.udhcpc hints you might try setting environment variable router=something 2025-01-06 04:22:41 likewise dns=something 2025-01-06 08:34:44 hello hello 2025-01-06 08:35:53 i'm trying to configure my apk repos but i got a timeout error for fetching the list 2025-01-06 08:36:54 does some one get the same error ? 2025-01-06 08:37:19 i'm connected to the wi-fi 2025-01-06 08:37:33 what's in your /etc/apk/repositories file? 2025-01-06 08:38:04 and if i do ping 8.8.8.8 the pachage are coming in 2025-01-06 08:38:34 aron: i have /media/sdb1/apks 2025-01-06 08:39:30 but i had to problem since the installation of Alpine 2025-01-06 08:39:37 how about: ping dl-cdn.alpinelinux.org 2025-01-06 08:40:40 aron: no package 2025-01-06 08:41:10 hm? 2025-01-06 08:41:46 can you ping dl-cdn.alpinelinux.org ? 2025-01-06 08:41:48 i have 75 packets sent 0 received 2025-01-06 08:42:09 ah, ok 2025-01-06 08:42:29 (package != packet) 2025-01-06 08:42:53 aron: yes sorry 2025-01-06 08:43:16 and ping 8.8.8.8 works fine, correct? 2025-01-06 08:43:24 yep 2025-01-06 08:43:50 but now i've just tryed ping google.com and is not working 2025-01-06 08:44:20 try this: ping 151.101.130.132 2025-01-06 08:44:29 (this is one of the servers behind dl-cdn.alpinelinux.org) 2025-01-06 08:44:48 yes that is working 2025-01-06 08:45:22 I think DNS resolution is to blame 2025-01-06 08:45:32 it's the first time i experience this on a fresh install 2025-01-06 08:46:01 when you ping dl-cdn.alpinelinux.org what is the resolved IP address? 2025-01-06 08:46:37 like: 2025-01-06 08:46:38 $ ping dl-cdn.alpinelinux.org 2025-01-06 08:46:39 PING dl-cdn.alpinelinux.org (151.101.194.132): 56 data bytes 2025-01-06 08:46:56 ^^^^^^^^^^^^^^^ 2025-01-06 08:47:36 is this one : 2a04:4e42::644 2025-01-06 08:48:19