02:48:42 polarian: i still have stuff at Jump as well 07:08:51 it looks like meta_mode does not work nice with pkgbase and release or rather vice versa 07:09:03 i can reproduce #283679 07:09:47 angry_vincent: please file a separate PR for the pkgbase issue and cc ivy⊙fo 07:10:01 pkgbase is not part of release, so those are probably separate bugs 07:12:36 when i run make release i seeing pkgbase-repo.tar in TARGETS 07:14:00 added in afdc022deb9124e47a8d623417fb487d6ea89862 07:14:11 no idea it is related to the pkgbase itself 07:14:21 yes, release/Makefile builds some pkgbase-related files, but pkgbase itself (i.e., the 'make packages' target) is not part of release 07:14:34 so if make packages fails with meta mode, that's not releated to any bugs in release 07:14:46 related 07:15:32 i will try make packages now 07:18:11 https://bpa.st/QBFQ 07:18:35 please file a PR with the full log of all make targets you used (not just make packages) 07:19:14 i did not use any targets. but i have /etc/src.conf with some stuff disabled. and i use META_MODE 07:19:45 if you ran "make buildworld packages", then the targets are "buildworld" and "packages". you can't run make in src without any targets 07:20:37 and if you have a custom src.conf, also include that in the PR please 07:20:41 i did run `make packages` 08:32:00 ivy: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290010 08:41:51 angry_vincent: can you please include the full output of "make buildworld"? i will try to reproduce the issue here, but having the logs makes it much easier 08:42:21 (that's why i asked for the logs of all targets you used, "buildworld" is a target) 08:45:18 damn someone constantly updates Makefile.inc1 i have patches applied onto eh 08:45:20 :) 08:46:20 ketas: not that often: https://cgit.freebsd.org/src/log/Makefile.inc1 - but this does contain pkgbase targets which are receiving a lot of updates right now in preparation for 15.0 08:46:55 i wonder why pkgbase didn't all that attention years ago 08:47:15 because we were all very surprised when releng announced it will be the default in 15.0 08:47:42 in my case i have this patch turns src package off if commandef 08:47:43 d 08:47:45 which resulted in FreeBSD Inc. hiring someone to fix bsdinstall, and Colin and i working basically full on time on pkgbase for the last month to get it ready 08:48:02 i did not see existing option 08:48:10 is there one? 08:48:29 no, but patches accepted 08:51:15 called the option WITHOUT_SOURCE_PACKAGES after a short thinking 08:51:25 unsure 08:52:19 or maybe better focus on releases eh 08:54:56 i have already filed few prs with patches that were sitting around 10y or some were recent, were good i heard, one needed work i don't know how to do 08:54:59 ivy: hello 08:55:00 but unsure eh 08:55:10 scottpedia: moin 08:55:31 i am interested in contributing to freebsd cause I have a nice idea to see implementation. 08:55:47 where do you think I should start? ivy 08:55:50 lets see the idea 08:56:27 ketas: you wanna hear about it here? 08:56:31 scottpedia: write the code and put it in bugzilla. if it's a significant change to how the system works, you should ask arch@ first which is where that sort of change is discussed 08:56:52 what's arch@? 08:57:04 scottpedia: https://lists.freebsd.org/subscription/freebsd-arch 08:57:13 okay alright 08:57:24 thanks man 08:57:51 how likely that my feature may get merged into master? 08:58:17 zero, since we don't have a "master" branch, but i assume you mean main. in which case i have no idea since i don't know what your feature is 08:59:00 is there any sort of screening process? I can assure you my feature is useful but not sure to which extent. 08:59:18 uh, like do we screen contributors to determine if they're worth of contributing? no 08:59:45 okay alright 08:59:51 proposed changes are decided on technical merit, but significant changes to how the system works should be discussed on arch@ 09:00:17 what's "technical merit"? 09:00:33 a change which is bad will not be merged 09:00:56 tbh if you have some time I may talk about my proposal with you. is that okay for you now? 09:01:11 again, if you are unsure about whether a change is acceptable, arch@ is the right place to discuss this 09:01:24 okay 09:01:34 but if you want to summarise it here someone might reply 09:01:48 alright 09:02:12 scottpedia: one of my small change is here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283457 09:02:29 still aren't sure either 09:02:41 okay 09:02:47 apparently got over my head 09:03:52 you mind PM? ketas 09:04:47 no 09:04:57 everyone can pm me :p 09:05:14 noone ever does so i don't limit those 09:05:34 but i don't have any other or hidden info for you 09:05:42 you accept one PM and like a week later you're getting marriage proposals 09:05:58 hmm 09:06:09 :p 09:06:21 how many did you get 09:06:22 ivy: you read too much into it my friend 09:06:25 :) 09:06:34 yep, marriage proposals on FreeBSD channel are quite frequent issues 09:06:35 i am not reading anything into anything, i was making a joke 09:07:12 most of us here are of the same sex 09:07:23 and I am not homosexual 09:07:49 i oncd got that proposal as well 09:07:54 not on fbsd channel 09:08:08 had to decline eh 09:08:58 so i guess i could add that patch to bugzilla as well? 09:09:01 makefile one 09:09:04 scottpedia: don't worry, i think there are some guys here too 09:09:14 it's not big arch change 09:09:22 ketas: bro you read my PMs? 09:09:33 ketas: yes, that's fine, you don't need to ask arch@ about that 09:09:37 ivy: what? I implied that most of us here are guys. 09:09:48 i hoped someone would pick it up from current@ 09:09:59 wrong idea maybe 09:10:14 scottpedia: oh. speak for yourself, i guess 09:11:06 bugzilla has huge backlog 09:11:31 i often find those 09:11:39 ketas: bugzilla tickets are not processed in order. if you have a simple change which is clearly correct there is a good chance it will committed quickly 09:11:48 ketas: for pkgbase issues, add ivy⊙fo to cc 09:12:06 then i check on top if it'a fixed and often it's not 09:12:08 well yes 09:12:17 importance etc 11:03:11 hi! I'm running makewhatis -p to generate my man page db to use apropos, but I keep seeing that almost everything gives me a name missing in NAME section 11:03:27 am I doing something wrong? 11:07:15 hi guys, im installing freebsd on my desktop for the first time and i desperately cant get the amdgpu driver working 11:07:43 always hangs at boot or kernel panics when loaded manually 11:08:27 is the old drm-510-kmod driver still a good option? 11:10:38 lil_lasagna: I believe it just doesn't like the compressed man pages 11:12:19 cyric: true, all of these pages in question are compressed 11:14:17 so mandoc can read/display those, but makewhatis (which is a hardlink to mandoc) can't for some reason 11:14:26 then idk what to do about it. if pkg installs them compressed and makewhatis does not like them compressed, how does the system usually populate it's mandocdb? 11:23:10 lil_lasagna: or my guess is completely wrong and it's about the symlinks, where the page's name doesn't appear in .Nm 11:25:19 s/symlinks/hardlinks/ 11:26:10 e.g. there's uma(9) man page that has '.Nm UMA' and a lot of links to it, all of those seem to be reported 12:53:38 how's 15 shaping up? 13:18:17 Hmm. I can no longer find hyprland on FreeBSD 14.3. Has it been removed? 13:20:03 1 14:43:16 oh dang, I'm definitely failing to keep up with development at all anymore.. this is the first I've heard of pkgbase and it's already included in 15-REL 14:51:24 lol. "a call for testing was made in March 2016" 16:34:41 Regarding hyprland, I had to switch to "latest" branch for pkg. 17:21:02 what's the "right" way to add rust as a build dependency to a port: BUILD_DEPENDS= rustc:lang/${RUST_DEFAULT} is ok, if I don't know of any version constraints? 17:25:33 BUILD_DEPENDS+= rust>0:lang/rust 17:25:48 thank you 17:28:06 I saw most ports use sth like: ${RUST_DEFAULT}>=1.35:lang/${RUST_DEFAULT} with some version... 17:29:13 and: RUST_DEFAULT?= rust, in the Mk files 17:39:11 Yesterday I discovered sysutils/lnav, quite nice log file viewer. But I've stumbled upon some bugs which I resolved with upstream. But trying to build the current git HEAD from fails without rust, so the question. The current version in ports is somewhat oldish 17:40:29 Makes a nice IRC log viewer too :), search for messages by a nick, browse by day.. 18:31:59 Hi 18:32:42 Look at the vermaden work https://vermaden.wordpress.com/2021/04/02/ufs-boot-environments/ 18:33:19 no zfs needed 19:49:40 ibs was hearing good things about hyprland. like it? 20:29:39 Guys 20:29:49 I want some help here 20:30:36 Searching for alot of time, I find that ZFS won't help in anything (just consuming more time) 20:30:58 I will not change the system disk 20:32:21 to ZFS the only option here is to create a pool for only 2 partitions; bec. the other disk is a ntfs, and the third one currently disconnected 20:33:30 I think it will be more better if I just buy a 1TB disk move all data from the third one, and create a ZFS pool there 20:34:47 and as I can see I can get an UFS boot environment.. 20:39:35 But why the fsck only runs only on the root partition in boot? 20:40:07 not the others, I need to do it manually 20:44:09 man fstab, search for fs_passno 20:50:09 Ah thank you 20:50:22 It was set to 0 20:50:50 divlamir: should now make it 2? 20:53:39 you choose the order, but 1 is reserved for the root filesystem, so yes, 2 is ok 20:58:57 Oh it's an order 20:59:31 so it should be 3; due to efi takes the num 2 21:00:27 Oh, no dump is set to 0, isn't that eats more space? 22:54:45 Remilia: Might be worth installing a system with ZFS in a VM, or on spare hardware, right from the start, so you can get a feel for what it's like running ZFS. 22:54:59 Mistab. I guess Retrofan is gone.