01:16:15 I liked Clipious too. But most, if not all invidious instances are now crippled, all thanks to Scroogle 01:32:36 yewtu.be still works 01:39:50 wondering how do i configure udp-encap esp when using setkey ? 09:08:49 is there any general rule of thumb when it comes to sharing files between jails? 09:21:33 drobban: ro or rw? 09:21:57 one jail need to be able to write, the other only needs read 09:28:54 nullfs ? 09:53:12 babz: perhaps. isnt that ro? 10:06:29 nullfs suports also rw 10:07:55 you also can normaly rw mount the dir in the jail which writes and nullfs mount it to the jail which needs to read from it 10:19:11 Any news on getting wifi working on RPi4? how do I go about debugging? 10:28:00 Success: https://freshbsd.org/freebsd/src/branch/main?q=BCM43438 doesn't look like it 10:28:01 Title: FreeBSD / src - FreshBSD 11:13:24 ahh, thx for the clarification satanist - will have a look at the nullfs manual 12:32:55 is upgrading from 12.4 to 14.0 once its out directly a bad idea? 12:39:43 sopparus: maybe upgrade to 13 until 14 is out? 12:40:25 i could but it would be extra work, hence the question :) 12:41:38 I'm sure someone has documented that somewhere 13:06:12 should work 13:06:22 ill just try, it has not much on it 13:17:52 just a drive by "thank you freebsd" for the calm and low maintenance life i enjoy 14:51:19 poudriere keeps rebuilding qutebrowser when i add some pkgs to my repo's list and relaunch bulk, is there some way to check what triggers those kinds of things (i assume qutebrowser needs to be reconfigured and thats why ?) 15:02:02 cedb: poudriere testport has a lot of debugging output. especially when you set DEVELOPER=yes, IIRC 15:04:45 meena: you just launch it like literally $(poudriere testport) ? 15:05:26 cedb: you launch it the same as `bulk` 15:05:41 right im asknig cause i just put a pkglist in my /usr/local/etc/poudriere.d/ as all the guides ive seen were saying but 15:06:30 there doesnt seem to be an obvious assoc between the previously built stuff and the current build (apart from the jail obv i mean in terms of seeing the delta between two builds) 15:06:53 poudriere testport takes a single port parameter 15:07:34 cedb: was the package for qutebrowser successfully created? 15:09:30 ahhh sorry didnt get that, yes it did get created properly! 15:10:20 its just been three times that i add a pkg to say foopkglist and do "poudriere bulk -j -p head -f foopkglist" and 15:11:05 cedb: so if poudriere decides to rebuild it, you should see a line in the output saying it deleted the pkg and why 15:12:13 hm i should rtfm and investigate a big more i thought this maybe would be one of thsoe things thats super obv for people ith a little experience (bsd's newbie here, mostly used binary pkgs and ports "by hand" so far) 15:12:27 RhodiumToad: gotcha ill look into the logs 15:13:56 which btw is there some "best practice" or conventino to manage the lgos( verbositiy, rotation)? a mostly self hosted desktop "daily driver" generates pretty impressive amounts 15:14:51 did you look at poudriere logclean? 15:15:54 yes ive run it on previous isntalls the emphasis is on "conventions" like just nuking everything after a successful build seems a bit harsh yk 15:37:36 RhodiumToad: im running the testport subcommand for qutebrowser is there some way to narrow down "what im looking for", my wild guess would be that an old failed build is polluting the jail and the successful build doesnt cancel that 15:38:03 the other thing would be ccache ive enabled according to the obvious defaults online but i dont know much about these tools ill check that after 15:38:29 testport will always build, it's no use for finding out why something builds when you didn't expect 15:38:54 you want a normal bulk run and at the start there should be a line saying why it deletes a package 15:38:56 the question is what message do you get when doing a bulk build 15:39:22 also make sure the bulk build isn't using -c or -C 15:39:23 "Deleting qutebrowser-3.0.0.pkg: stale package: unwanted origin www/qutebrowser@qt6" 15:40:46 what exact command did you use? 15:42:05 ah, report a bug, because the first entry in FLAVORS isn't the default flavour, but not sure if against www/qutebrowser or against poudriere (probably www/qutebrowser) 15:43:14 yeah, that's a bug in the port 15:47:10 cedb: did you put just www/qutebrowser in your list of ports to build? 15:47:26 cedb: putting www/qutebrowser@qt6 instead might be a workaround 15:47:42 (assuming the qt6 flavor is the one you want) 15:49:41 ya the whole qt6 vs qt5 thing is often a bit messy 15:50:13 nimaje: hell youre right! 15:50:27 the bug here is that the qutebrowser port has FLAVOR?=${FLAVORS:[2]} which is not allowed - the default flavor is always ${FLAVORS[1]} 15:50:29 ya no i didnt specify a flavor i didnt even know this was the proper syntax 15:51:00 interesting oh well well 15:51:46 i guess setting up tls for the nginx fronting the build wasnt worth it (hence the delay in answering) but in any case: poudriere.pynchon.me 15:53:25 nah, just someone didn't read properly that the first flavour has to be default one and having the ports themself having the FLAVOR?=${FLAVORS:[1]} line causes duplication and people thinking they can choose which one is the default, that logic should be moved into the framework and FLAVOR?= in the individual port makefiles disallowed 15:54:27 ya just surprised cause qutebrowser is pretty popular usually so yk, id expect some rude person to have already yelled at the poor maintainer 15:55:25 i still dont get why itd retrigger a build if its the same flavor, unless it says "stale-deleting->building" but really its just doing some basic sanity/smoke testing? 15:56:31 nimaje: that makes it unnecessarily hard to use ${FLAVOR} within the port makefile itself 15:57:02 cedb: it retriggers the build because there is disagreement over which flavor is the default 15:57:35 cedb: poudriere thinks it's supposed to build www/qutebrowser (default), but the package came from www/qutebrowser@qt6 15:58:01 sure but is there anything in that statement that says default=/qt6? 15:58:03 ah, yes if and stuff need the variables defined at parse time and can't do lazy eval 15:58:08 cedb: but when it builds it, the port builds the @qt6 flavor because of the incorrect FLAVOR?= 15:59:28 i guess to ask my question more pointedly: can you get this "im gonna decide this is incosistnt" because a port's "spec" is more specifically or explicitly asked for eventhough its the same in the end 15:59:44 damn ok my sentences suck sorry 16:00:30 nimaje: and you'd get into order-of-operations problems with things like OPTIONS_SLAVE or OPTIONS_EXCLUDE which need to be set before including the framework includes but which might need to be flavor-dependent 16:00:56 can poudriere .. bulk numbers@B trigger a rebuild even if default is A <: B ? 16:01:49 i guess im just linenoising at that point thanks RhodiumToad nimaje i would have pulled my hair on this one 16:01:53 cedb: flavors aren't versions, they don't compare 16:02:08 i meant that as a subtype relation 16:02:21 as in they could /contain/ 16:02:28 cedb: there is one default flavor which is the one you get if you don't specify @flavorname 16:02:41 there are no subtypes for flavours only equality 16:03:07 ya okay im overthinking this its a classic freebsd thing where i think this could all go horribly wrong but people are actually sensible so its fine 16:03:13 cedb: otherwise you can list flavors explicitly using cat/port@flavor (multiple times if needed) 16:03:55 right ya im considering starting this whole multiple jails multiple zfs dataset userlands thing 16:04:14 and ${FLAVORS:[1]} (what should be the default) != ${FLAVORS:[2]} (what is the default because of a faulty FLAVOR?= line) 16:04:25 yall have a favourite way to manage "ports list", i just have this textfile i edit in vim and ehhhh 16:04:40 I don't have a ports list, I create local metaports 16:05:02 nimaje: the throwing off part is that the logs say "deleting stale" which seems a bit scarier than it is (this qtwebkit stuff...) 16:05:42 RhodiumToad: i guess sameish question but for metaports? 16:05:44 there's only one problem case i've run into, which is that while poudriere can build misc/zoneinfo when it's listed as a port, it can't build it as a dependency of some other port 16:06:09 (because it installs in places that poudriere doesn't mount writably) 16:06:46 hmm that sounds a bit too far for me idk why youd want to include that in a build 16:07:14 ? 16:07:37 the reason to use zoneinfo from ports is that it's easier to update 16:08:16 sure just, does it need to be parametrized 16:08:53 ah, maybe I should start creating a overlay with local metaports as I already started to sort related stuff in my packages.list file and it makes it easier to install stuff 16:09:01 oh god, freshports last update: "Briefly: Egypt now uses DST again, from April through October." 16:09:31 damn people will /not let go/ of making calendars hellish on computers eh 16:09:33 if you've never looked at tzdata updates before, you would not believe how messy it is 16:10:04 like countries trying to change their DST rules on less than 1 week's notice 16:10:25 hmmm 16:10:43 every update is a mess, either a technological or a polite one that inspired it 16:10:57 funny part is my job i just quit was at a shop that does a pretty popular software for optimizing aircrew flight schedules 16:11:42 RhodiumToad: ok what the actual ... " Mexico will no longer observe DST except near the US border." 16:18:40 https://post.lurk.org/@acousticmirror/111008144295294599/embed <-- recently posted on the tz mailing list 16:29:10 fing lol 16:29:54 id ask who the hell willingly signs up for this but I tried to fix the moth ball of perl that we used for building at $work so i guess sometimes we just try to fix soemthing and get caught up 16:35:54 I subbed to the tz list to try and get some stuff deprecated 16:36:28 like W-SU, GB-Eire, etc 16:37:30 don't you want old timezone info present so you can retain the ability to deal with data expressed in those zones? 16:40:46 those are old alias names, not actual data 16:41:53 W-SU for example is just a link to Europe/Moscow 16:42:44 surely can't be as bad as this.... https://github.com/mpv-player/mpv/commit/1e70e82baa9193f6f027338b0fab0f5078971fbe 16:42:46 Title: stream_libarchive: workaround various types of locale braindeath · mpv-player/mpv@1e70e82 · GitHub 16:43:14 much worse. 16:43:31 * jmnbtslsQE subscribes 16:43:55 there are historical timezones which contain non-contiguous days 16:44:23 i.e. the current date goes forward, then backward, then forward again 16:45:06 what is the mailing list you referered to? 16:45:45 the iana tz list. but it's actually quite boring 16:45:56 OK 16:46:52 it's messy because every country in the world thinks it can just tweak its own timezone/DST rules and everyone will immediately follow 16:47:50 which is why there are 3 to 10 updates per year to a data file which ought to be predictable years in advance 16:53:04 ah 16:55:20 for an example of the kinds of breakage, see https://catless.ncl.ac.uk/Risks/32/16#subj9 16:55:21 Title: The RISKS Digest Volume 32 Issue 16 16:57:47 heh 16:57:59 <_xor> > CrtxReavr feels like cut(1) should have a way to select fields from the right. 16:58:14 so it was the fact that the birthdates were being defaulted to midnight? 16:58:23 <_xor> I usually use awk when cut won't CUT (heh) it heh. 16:59:22 RhodiumToad: i suppose that since it was such a long time ago, there was not necessarily a record of the actual birth time, so for those old birthdates, they just default to midnight 16:59:50 so i guess that's the reason for the idea "don't do timezone changes at midnight" since it's a natural point where a lot of default things might happen 17:00:02 jmnbtslsQE: the combination of representing a birthdate as a timestamp with a time of midnight, plus the fact that midnight didn't exist on that day due to DST mess 17:00:10 yeah 17:01:10 phew, need to make sure i don't have any daily zfs snapshots in Saskatoon on april 13 17:01:42 most places have learned not to do DST at midnight. I believe there are still some that do 17:02:37 e.g. Chile 17:37:32 _xor: does awk allow that? 17:38:04 <_xor> Sure, negative column index. 17:38:58 $(NF-2) 17:40:54 <_xor> I appreciate awk and have been using it more recently, but of the tools I use it's probably the one where the differences between GNU and BSD surface most frequently. 17:41:44 <_xor> Hmm, actually, it's between awk and make for me. Close call, though now that I think about it, I'm leaning more towards make. 18:05:07 how is C.UTF-8 not a thing? 18:05:31 ? 18:07:14 C doesn't need UTF8. 18:07:31 i'm confused because C.UTF-8 is definitely a thing 18:07:45 it's even the default since... freebsd 13? 18:07:50 where? it is the default on freebsd and I think on debian to, on arch the butchered the name to C.utf8 18:07:53 $ locale -a | head -n3 18:07:54 C 18:07:54 C.UTF-8 18:07:54 POSIX 18:07:57 weird 18:10:00 it's just a way to get sane sorting and multibyte recognition at the same time 18:17:14 TIL 18:24:44 kevans: according to https://github.com/mpv-player/mpv/commit/1e70e82baa9193f6f027338b0fab0f5078971fbe 18:24:46 Title: stream_libarchive: workaround various types of locale braindeath · mpv-player/mpv@1e70e82 · GitHub 18:30:27 meena: not a fan of this person already, and I'm only two paragraphs in 18:30:35 i don't think i'm interested in reading the rest of this 18:31:20 there are some good points in it 18:34:01 however, it is from 2017, and so it's out of date on some key points 18:37:51 the fact that functions like sprintf are locale-sensitive by default and don't have a locale_t parameter variant is a real problem 18:56:26 This is gonna sound dumb. say if I do `for p in "/bin/*"; do echo $p; done` I get `/bin/[ /bin/cat /bin/chflags /bin/chio ...`, but I'd like to get `[ cat chflags chio`. 18:58:23 how about cd /bin; for p in "*"; do …; done; cd - ? 18:58:46 nimaje that would work, indeed, excpet I have like 10+ dirs other than /bin :D 18:59:03 okay I have an idea 19:00:06 using $p like that probably isn't safe 19:01:07 hm, using % or #? I can't remember which one was for prefixes and which for postfixes 19:01:16 that's also not safe 19:01:44 why do you want the list to begin with? 19:02:55 id generate the paths outside the loop and feed it ? 19:04:10 like while read f; do foobar; done <(find *pretend i know how to use find properly*) ? 19:04:45 looks like `for prog in $(ls /bin /sbin)` works and is safe 19:05:19 however, ls(1) keeps printing the directory name as well 19:05:32 I guess I can just grep that out 19:05:46 nooo use bash expansion for nerd points 19:05:55 sorry aehm POSIX** expansion 19:06:10 antranigv: what do you need the list for? 19:06:11 nerd points :) lol 19:06:26 RhodiumToad to drop a page to the Wiki :)) 19:06:49 RhodiumToad try this: cd /bin && man * | awk '/^N.NA.AM.ME.E/{f=1;next};/^S.SY.YN.NO.O/{f=0};/^D.DE.ES.SC.CR.R/{f=0};/^D.DE.EP.PR.R/{f=0};/^Q.QU.UE.ER.RY.Y/{f=0};f;' |less 19:09:26 antranigv: ${foopath##${footpath%/*}} or something i always mess it up 19:09:43 ${foopath##*/} 19:09:44 wait no thats the opposite of what u ant 19:10:06 nono i was right 19:10:34 your version is wrong if the path contains any metacharacters 19:11:02 i knew there would be some shell edge case weirdos KNEW IT 19:11:18 its like googling the best way to parse cli args: the answer is just dont use bash 19:12:14 if i had infinite free time, I'd build a system where /etc was renamed to "/System Configuration" and see just how much of the system explodes as a result 19:13:34 if i had infinite time id write an anti-debasher in some fancy lang for formal verification that *proves* you cant escape the madness in posix with discipline and you should just abandon all hope and use fish 19:23:07 if I had infinite time I'd just create milions of web sites, and do SEO where FreeBSD would be mentioned more than Linux 19:23:11 beat them in their own game 20:07:56 don't you know FreeBSD is dead 20:08:27 netcraft said so 20:09:24 dkeav: lol netcraft 20:34:43 LOL 20:35:04 do we have a tool that allows us to get the src path of a program in base? 20:35:47 something like `srcwhich /bin/ls` that will print `/usr/src/bin/ls` ? 20:37:43 crest , you might know the answer to that ^ 20:40:37 not really, but for any specific tools it should be easy to find out 20:41:01 which ls # prints /bin/ls 20:41:17 cd /usr/src/bin/ls 20:42:15 replace the inner / in /usr/bin/... and /usr/sbin/... with a . 20:42:31 there are a few exceptions 20:42:50 i mean, sure, but zpool is not in sbin/zpool, it's in cddl/sbin/zpool 20:42:59 need a proper way to find them 20:44:06 i'm not aware of a good tool to map back from an executable to all the sources it's compiled from 20:44:31 maybe we need to generate a DB from the src 20:44:35 you may be able to extract it from the .meta files after building the source with meta mode enabled 20:46:03 e.g. parse the sources for /bin/ls from /usr/obj/usr/src/amd64.amd64/bin/ls/ls.meta 20:48:45 but do keep in mind that the .meta files reveal the ugly truth about which files compiler, binutils, etc. (may) have accessed to build a file 20:49:58 unless you want to learn that every executeable depends on $(CC) and all its sources 20:50:52 just computing the full transitive hull isn't useful unless you're the build system 21:25:59 oh no plz no more hulls folks i dropped out for a reason 21:26:32 cedb what's hulls? 21:32:52 cedb: ? 21:37:01 I'm not sure exactly what we're talking about, but I think it's the minimal set of dependencies *effectively necessary* for something 21:37:36 (as opposed to the dependencies explicitly set by the programmers) 22:13:29 RhodiumToad you're pretty active on the wiki. do you think this is worth publishing? https://antranigv.am/misc/wiki_baseutils0.png https://antranigv.am/misc/wiki_baseutils1.png 22:34:14 well, I did publish it. any thoughts would be nice https://wiki.freebsd.org/BaseUtils 22:34:15 Title: BaseUtils - FreeBSD Wiki 22:39:16 LxGHTNxNG: the first time i heard the term was in optimization for convex hulls 22:40:01 seems it was used sort of the same way when mentionning "hull of dependencies", rougly its just given a bunch of data find the shape of it 23:18:33 antranigv: while I'm not RhodiumToad, I think it's great! For me, this helps with the "discovery" of them. 23:33:32 TIL about `cu` command, hah, awesome