04:42:24 any elixir enthusiasts in here? if so - write to me in priv if you have time over for a couple of questions. 07:18:17 I will install openjdk-jre21 from ports,and running 'make config-recursive' but notice it will install cups, why doesn openjdk-jre21 cups installed? 07:35:54 nwe: I've had pretty good luck with using portmaster. https://docs.freebsd.org/en/books/handbook/ports/#portmaster 08:15:59 Hi 08:17:11 I need some help in upgradeing 08:18:45 pkg: Fail to rename /compat/linux/usr/share/.pkgtemp.icons.zITfg1E7EDDm -> /compat/linux/usr/share/icons:Is a directory 08:19:18 should I do it manually? 08:29:47 all my system now is broke :( execpt hexchat 08:36:18 Done manually.. 08:51:03 system is still broke after upgrades :( 08:51:15 ld-elf.so.1: /usr/local/lib/libinotify.so.0: Undefined symbol "kqueue1@FBSD_1.7" 08:51:32 I have no browser please help.. 08:56:52 Looks like libinotify needs an update? 08:58:40 All packages are up to date.. 08:59:05 update as in a rebuild 08:59:24 I installed it via pkg 08:59:28 not ports 09:00:00 my ports collection itself needs updates 09:00:44 Notify the maintainer(s) if you're sure it's a FreeBSD-wide error. 09:01:31 wait.. look like my linux-seamonkey is working I will try to search.. 09:39:25 TommyC: My browser is broke agian.. how to notify them? 09:59:49 any help guys please.. 10:02:41 is it good idea to use both pkgs and ports at once? 10:03:01 Yeah, I am doing that 10:03:13 But not for main libs 10:03:29 I found that is a libc problem.. 10:04:27 la_mettrie: If used ports libs.. I think your pain will more at upgrading 10:05:48 generly Unix is designed to make you suffer, but some choices make it less 10:07:58 Unix is designed to do just what you tell it to do. Nothing more, nothing less - so if you give it bad instructions, expect bad behaviour. :°) 10:08:46 yeah, but sometimes noone knows the good instruction in some new things 10:09:58 some stuff unexpected will come out 10:10:41 Possibly. But the above still applies in full, regardless 10:14:33 yeah 10:14:55 BUT now my libc is broke, and don't know what to do? 10:17:25 Can't be of much assistance I'm afraid. I've encountered people screwing up their libc through source installs on Linux before, and they all ended up having to reinstall the OS. 10:18:28 I want to get my beautiful system back to work :( 10:20:02 Alver: No, my problem is simpler.. kernel is up to date, every thing is working; except some important apps for me.. 10:20:33 the error of libc is only with libinotify 10:21:46 maybe I need to build it from ports with latest..? 10:22:38 those ones is chrome, rox, gimp... 10:22:43 Retrofan: the first step will be figuring out what it is that is not working in those specific apps. "Not working" is not useful 10:24:26 not only those apps.. some others wich make use of libinotify 10:25:08 my whole X11 system will be broke without fixing that 10:25:39 this my main os, I never used any other for years ago 10:28:36 Did you try reinstalling all packages, like in: pkg upgrade -f 10:32:14 Yeah 10:32:32 and I fixed alot of problems 10:33:02 except that one 10:33:50 I want to say that I didn't fully upgrade my system from 13.2 to 13.5 10:34:40 I only Installed the letest updates for 13.2; to make it possable for a safe upgrade.. 10:35:13 For kernel, base and other stuff.. 10:35:21 And you are now on 14.3 ? 10:35:30 huh 10:35:34 I am 13.2 10:35:43 I want to go for 13.5 10:36:02 My system didn't touch any updates for years 10:36:42 Oh, ok.. Can you rollback, do you use zfs and boot environments? 10:36:54 I only installed patches 10:37:08 divlamir: rollback why? 10:37:49 zfs and boot environments: no 10:39:25 I tried a year ago upgrading.. but faced same problems; and didn't know about rollback, so I removed newer stuff manualy and installed old ones with right version, and it worked! 10:40:32 and forget about upgrading, but now I feel may get hacked and I need some newer apps 10:45:31 o_0 10:46:18 Almost sounds like backing up/keeping home drive and doing a clean install is the way to go 10:47:17 I don't thing this problem is big enough for clean install 10:47:42 We here not using windows 10:48:15 After my old manualy rollback, my system was so clean 11:03:36 Retrofan: Can you check what version of FreeBSD was your libinotify built on? 11:04:15 As 13.2 is unsupported it may not work if your package is built on later version 11:05:01 Ah, I forget about that.. 11:05:59 For example the package from the latest branch on 14.3 is built on 14.2 11:07:41 here we go 11:09:01 it was built on FreeBSD_version: 1305000 11:09:45 Well, here you go 11:09:58 is this 13.5? 11:10:05 No way it's gonna work before you get your base system there 11:10:09 Yep 11:10:28 so I need to upgrade now 11:10:35 all my packages is same 11:10:43 If your base system is in good shape, yes 11:10:57 And the rebuild ALL packages in the end 11:11:17 pkg upgrade -f ? 11:11:46 Can't have new libs on unsupported system, yeah after you've done the kernel and base upgrade 11:12:08 And any ports installed manually too 11:12:25 Ports is an other very big story 11:12:38 I have ports from early 2000s 11:12:42 I don't want to hear it :))) 11:13:40 dont worry I will fix it by myself ;) 11:14:11 I don't install any main libs from ports; so system can work without them 11:14:16 *didn't 11:14:54 Keep us posted but you should be fine once you get to a supported release 11:15:11 divlamir: I am really scared from upgrading 11:15:52 Do a clean install on zfs then, it's good to have a safety net and go back to a working state if it goes wrong 11:16:15 I really want to try zfs 11:16:26 but they say that is eating ram 11:16:56 You should be more scared living in unsupported releases 11:17:04 yeah 11:17:16 Well, it does eat a chunk, but even on a small VPS it runs ok 11:17:43 But I can't now.. I need upgrade first and take the risk 11:17:59 I will do that for freebsd 14 upgrade 11:18:03 Maybe backup first :) 11:18:18 you mean my data in Home 11:18:25 I had done that 11:18:33 and all my conf files 11:18:40 is safe 11:19:50 other big stuff is on different hard disk 11:20:41 divlamir: are you in dev team? 11:21:40 Not at all, just a regular user 11:22:21 I was just wondering why they removed seamonkey back in 2019 11:22:36 I had very good time with it 11:24:26 and started a project for re port it (with plugin support) 11:25:22 Here's the commit reason: https://mail-archive.freebsd.org/cgi/getmsg.cgi?fetch=2795546+0+archive/2019/svn-ports-all/20190707.svn-ports-all 11:25:30 I see that alot of old ports that removed was really good, that's way I have ports form 2000s 11:25:45 security? 11:26:20 I can't open any browser :( 11:26:46 Just too much burden security wise, according to the message 11:27:02 yeah 11:27:17 but we surly can make safe 11:27:28 they choose the easy path 11:27:44 There are browsers like plain Firefox that do not need linux compat, why not go native? 11:28:05 I am retro guy ;) 11:28:17 But yeah, I can understand being attached to some piece of software... 11:28:18 I like the old mozilla style and stuff 11:28:52 i could not compile seamonkey last i tried, gone a couple days 11:28:59 I am a usenet user + irc and I really make use of flash and java daily 11:29:14 and seamomkey was doning all of that 11:29:17 Well deserved nick then :) 11:29:36 I heard about palemoon 11:29:47 thay have native version for freebsd 11:29:56 but no usenet or irc 11:30:42 anything you can't find in regular web, you will find on usenet.. 11:31:42 Reinhilde: need new patches 11:32:42 try seamonkey 5.20, I compiled here on 13.2 11:33:28 *2.53.20 11:33:31 my bad 11:33:56 2.53.21 have problem with gtk 11:47:23 Now the freebsd-update(8) utility can fetch bits belonging to 13.5-RELEASE. During this process freebsd-update(8) will ask for help in merging configuration files. 11:47:32 haha 11:47:59 the right way to upgrade was on the offical freebsd website 12:41:54 gruh. 12:42:17 Retrofan, i actually yanked the latest released version. but maybe that's my problem 12:42:41 latest is 2.53.21 12:43:44 I have some problems here 12:45:42 the command want me to edit conf files manualy, and opened it in vi 12:45:58 and don't know what to do 12:46:42 as it only saying current file above with only two lines, and the newer file 14:18:15 for fuck's sake we need more package build capacity 14:18:36 for almost a month freebsd current hasn't had usable package repos 14:18:43 *sigh* 14:21:46 yeah, stay away from current 14:22:43 Retrofan: some of us have no choice :) 14:22:53 how? 14:23:12 you mean new software 14:23:14 ARM64/RISC-V non standard machine devs 14:23:28 ah 14:23:47 I don't even do x86 on Linux 14:23:49 heheh 14:24:13 In my opnion netbsd is better for that 14:24:17 I have one x86 and it runs all non-x86 virts lol 14:24:44 I don't know I feel freebsd is for workstion desktops 14:24:44 I haven 14:24:50 *why 14:24:59 openbsd for servers 14:25:04 oops I haven't been an active x86* user in 10+ years' 14:25:17 I use MacOS ironicly for my desktop 14:25:35 (It is afterall Unixish underneath) 14:25:54 Back in the day RISC was the strongest for work 14:25:59 Yep 14:26:01 Mimps 14:26:10 SGI 14:26:15 I was a Unix admin back in my day job 14:26:27 I'm retired now so judst a hobbyist.. 14:26:34 s/judst/just 14:27:08 every time I see xerox stuff 14:27:20 what it reached in 80s 14:27:31 Retrofan: I'm n old NCR/AT&T/Lucent geek lol 14:28:08 Imagine if they worked on a unix version of viewpoint 14:28:30 it will make the strongest ever workstation.. 14:28:33 Heh imagine if we still used microchannel and such.... 14:28:40 It would be scary... 14:28:49 yeah 14:29:09 I just built FreeBSD on a VisionFive2 RISC-V box this morning 14:29:19 xerox is like nokia 14:29:27 maybe worse 14:29:56 selling there tech for other company like apple 14:30:08 *companys 14:30:36 Tenkawa: Morning compile :) 14:30:44 heh indeed 14:30:54 oops... it couldn't reboot itself.. lol 14:30:55 Rebooting... 14:30:56 pmic_ops: cannot read pmic power register 14:33:01 Look like your experience is big ;) 14:34:35 Retrofan: I worked a long time with this yes and its a lot of fun... 14:34:52 Thats why I keep doing it 14:35:54 https://virtuallyfun.com/ 14:36:07 You will like this blog so much 14:36:08 pkg/ports for risc-v.. now "that" is a bit behind lol 14:36:55 I really love those toys.. but no money :( 14:37:14 1000 of dollars 14:37:28 Nod. 14:39:39 so emulating is the best :) 14:40:20 Tenkawa: can you help me in my problem :) 14:40:28 Retrofan Whats up? 14:40:36 (missed it) 14:40:50 upgrading my freebsd system 14:41:02 from/to ? 14:41:07 from 13.2 to 13.5 14:41:20 updated and applied all patches for 13.2 14:41:28 and now upgrading 14:41:30 but.. 14:41:56 the command ask me to manually edit conf 14:42:16 "/etc/group" 14:42:40 yeah... 14:42:45 got diffs 14:43:01 open in vi, only saying current file above with only two lines from it, and the newer file down... 14:43:15 I know how to edit in vi 14:43:43 I don't have any browsers working now 14:44:01 also I am not smartphones user ;) 14:44:54 but what it wants from me; for example deleting that only two lines 14:44:56 does it not give you dialog to merge changes or are they too diverse to merge? 14:45:21 It should give you the ability to do it through the dialog 14:45:28 and replace it with newer files, or something else 14:45:42 dialog? you mean x11 14:45:48 or in shell 14:45:58 no.. dialog meaning questions/choices 14:46:22 it should ask you if you want to merge/overwrite/ignore 14:46:36 s 14:46:41 t 14:46:53 armin: wrong terminal ^^ 14:47:02 ah yeah he said press enter to merge.. 14:47:06 nwe: nope, RIGHT one! \o/ 14:47:12 =) 14:47:19 =) 14:48:07 and I need to merege; there some new stuff in the new one 14:48:22 I had to do that 120 times manually for one update yesterday lol 14:48:58 hit merge.. enter over and over 14:50:37 Tenkawa:No problem, a while ago I messed up my sytem, needed it to install 367 pkgs manually with right version ;) 14:50:59 Yeah its a pain 14:51:44 mine was valid sadly. 14:57:43 Tenkawa: "enter over and over" but how merge it? 14:58:14 I had to manually tell the prompt yes to merge.. over and over 14:58:27 It should be one of the selections 14:58:28 NO 14:58:48 it wants me to merge it manualy in vi 14:59:28 You're running mergemaster? 14:59:35 If it does then you have too diverging changing or you didn't run the pre step to get the mergemaster changes 14:59:53 I think thats being deprecated at some point though 15:00:05 FYI, mergmaster doesn't explictly use vi, it uses what you have set as $EDITOR. 15:00:21 yeah, my main is vi 15:00:34 but what it want from me 15:00:42 CrtxReavr: It has been giving me a deprecation messae recently... is there a timeline on it yet? 15:00:47 er message 15:01:07 Tenkawa, "It?" 15:02:15 it only shows first 2 lines of orginal file 15:02:30 that mergemaster process.. I see its planned to be replaced with etcupdate with what I read... 15:02:36 unless thats changed. 15:02:49 OH. . . I don't know about any timeline. 15:02:57 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252417 15:02:58 Though, I'm mostly happy with mergemaster. 15:03:10 There was an annoying change to the CLI options for it a few years ago. 15:03:19 <<<<<<< current version 15:03:19 # $FreeBSD$ 15:03:19 # 15:03:19 wheel:*:0:root,mosaid,operator,vboxusers 15:03:19 ======= 15:03:20 wheel:*:0:root 15:03:22 >>>>>>> 13.5-RELEASE 15:03:24 daemon:*:1: 15:03:34 and so on 15:03:40 hasn't been touched since last year so I'm not convinced it will happen.... 15:03:47 r 15:04:04 but note the last comment 15:04:36 So should I delete those first lines, and add there stuff? 15:04:44 No browser :( 15:05:03 ahh its the release line 15:05:25 weird 15:05:49 wheel of course since you added users to the group should be diff 15:06:12 just make group "correct" then remove the temp "file" 15:06:25 then it will stop complaining 15:06:57 and what is "=======" 15:07:08 it's not in the orginal file? 15:07:39 I feel like I will mess it up 15:08:48 Tenkawa: I wanted to mention, I own a group for retro stuff if you wnated to join ;) 15:08:55 https://www.facebook.com/groups/old.computer.club/ 15:09:16 Nice... I'll bookmark that 15:11:44 Ok the next fun tricky part... getting pkg to work on this risc-v.. it cant seem to acknowkedge its own existence 15:13:02 ok.. there "are" no pkgs yet 15:13:13 just looked at the pkg lists 15:13:35 its not in the Tier 1 or 2 arch list 15:14:28 "You know your hardware is shit when not even the NetBSD people want it." 15:15:30 Tenkawa: could I edit the conf out from what file the command gived me? 15:15:38 CrtxReavr: yeah 15:17:06 CrtxReavr: NetBSD supports more than FreeBSD 15:17:07 BeagleBoard BeagleV 15:17:07 StarFive VisionFive 2 15:17:07 Milk-V Mars CM https://dmesgd.nycbug.org/index.cgi?do=view&id=8029 15:17:47 I have the last 2 + a few others 15:18:37 The one neither supports that has much better potential is based on the Spacemit K1 SoC 15:19:06 I have one of those running Linux and its fairly powerful 15:21:01 More often than not, running jurassic hardware just means you're burning more electricity. 15:22:00 Jurassic? You do realize these are almost new right? 15:22:27 CrtxReavr: look like your not vintage ;) 15:22:29 They are super power efficient to compared to most architectures 15:22:49 "especially" x86/64 15:23:18 For their day, maybe. . . but for what you could do in a VM on modern hardware, probably not. 15:23:47 he is having fun, leave him ;) 15:27:05 hi, anyone here using poudriere to build their own ports getting failures with a selection of ports "/bin/sh: ccache: not found" ? 15:41:50 Tenkawa: I merged it manualy in other editor 15:42:17 but after I exit vi, it still ask me to merge it.. 15:46:43 Merge conflict markers remain in: /etc/group 15:46:56 should I delete the temp file? 16:27:29 that would make me think that I should double check for "<<<", ">>>", or "===" 16:28:09 Is this for me? 16:32:59 CrtxReavr: the VisionFive 2 is only 3 years old... what counts as "modern" to you? 16:41:00 the Mars CM seems to be even newer, less than two years old 16:42:09 ivy: I'm going to "attempt" to see what I can do with that one here in a little while.. 16:42:46 Tenkawa: I merged it manualy in other editor but after I exit vi, it still ask me to merge it.. should I delete the temp file? 16:43:06 It has some strange device tree changes that I might have to make.. 16:43:29 Tenkawa: have you measured the perf/watt of these devices against an N100/N150? i'm personally not convinced the improvement is enough to justify the hassle 16:43:51 Retrofan: I can't tell you really... I've never had it behave quite that way 16:44:08 Ok :( 16:44:08 i mean, they're interesting, but i don't think i'd buy another sbc with a crappy fdt / cheap ethernet controller / whatever 16:44:12 ivy: I don't use any x86 architecture in general... 16:45:02 I have one however I haven't "written/coded" on x86 in 10+ years 16:45:46 The machnie I'm typing on is an arm so.... 16:46:09 Retrofan: if you're using a Bourne shell run the merge with `EDITOR=ee merge-command-here` and it'll use ee instead of Vi 16:46:14 s/machnie/machine 16:46:51 Remilia: No problem with vi at all 16:47:10 I edit the file out the merge command 16:47:23 but it still asking for merge 16:47:25 that's likely the issue 16:47:37 how? 16:47:54 depending on what you are using it is not looking at /etc/group 16:48:20 exactly.. its still using the mergemaster prepared compare right? 16:48:38 it is looking at the temp file 16:48:38 I might be misremembering but freebsd-update works on copies while you are doing the merge 16:48:57 so should I edit the temp or delete? 16:49:18 you should merge it during the upgrade process 16:49:22 wait.. is it want me to edit the copy for merging it with orginal 16:49:32 not outside 16:49:47 or edit the original 16:49:49 or find the copy that it is working on 16:50:00 I found it.. 16:50:12 so editing it or remove? 16:50:44 "/var/db/freebsd-update/merge/new//etc/group" 16:51:33 Remilia: so editing the temp? 16:56:37 Retrofan: Just edit the members of the wheel group and delete the extra merge lines, done 16:57:05 in that vi.. then ok 16:57:28 I was only understanding 16:57:34 Just make it look something like: 16:57:36 wheel:*:0:root,mosaid 16:57:40 daemon:*:1: 16:57:48 I know 16:57:55 I only wanted to make sure 16:58:07 I have no browser working right now 16:59:02 Try installing w3m 16:59:11 and afraid from doing anything bad, which may will case pain for me for long time 16:59:12 If you are stuck in a terminal 16:59:37 lynx is better 16:59:51 Yeah, whatever does the job for you 16:59:57 but freebsd forum is using js/css 17:01:09 I have experience with text browser, those modern website will never work with them, or everything will be messed up 17:01:16 *browsers 17:02:49 Links actualy works half decent on js websites ... 17:02:54 vi is so hard.. but powerful 17:03:01 s/actualy/actually 17:03:13 at editing 17:15:07 In any case you shouldn't be editing the files in /var/db/freebsd-update directly, but do it as part of the process when ypou run freebsd-update 17:15:18 done 17:15:23 using vi 17:48:58 Now.. 17:49:05 I only need to run /usr/sbin/freebsd-update install 17:49:38 two or three times.. 17:52:51 Good luck this time! 17:53:36 hexchat is deleted, only working from memory 17:53:45 so I Will go for now 17:54:20 See u in a bit on 13.5 then :) 17:54:53 I wish :) If every thing worked 17:55:15 I don't have even a smartphone, so my all work on this pc 17:55:50 Don't forget reinstalling all packages, it will be fine 17:56:31 yeah, I have the instructions on txt file 17:57:36 Well forums is working on lynx 17:57:39 this good 17:58:33 Bye! 18:03:38 if anyone is running 15.0 and uses pkg.f.o, do not update to the latest ports build, it only includes a core subset of packages for re@ and will remove all your ports packages. next full build will be 1-2 weeks 18:06:37 ivy: "is" there a ports tree that I can currently pull for risc-v? I will definitely need it since there are no prebuilt pkgs currently outside of base 18:07:14 Tenkawa: if you compile yourself you're fine. this is only for people using ports packages from pkg.f.o 18:07:15 I'll store it off to the side and just replicate it as needed. 18:07:20 ok 18:07:35 yeah risc-v has no precompiled currently 18:07:57 (at least not according to the status page) 18:08:34 curious, i wonder how they build the installer snapshot without a pkg package 18:08:43 maybe it builds it from source 18:09:02 It "could" be the mirror too I'm hitting 18:09:19 is there a master url I can check? 18:09:43 i don't think that's publically accessible, but http://pkg0.nyi.freebsd.org/FreeBSD:15:riscv64/ is the primary mirror and i don't see any ports there 18:10:03 there probably isn't any RISC-V hardware fast enough to do a ports build, tbh 18:10:05 yeah chi didn't either 18:36:25 it would be published on https://pkg.freebsd.org/ if any output was expected to be useful 18:36:57