02:09:47 hi, 02:10:10 anyone can help me to configure redmine50 ? 02:15:04 Have you checked its website, https://www.redmine.org/ ? 02:15:05 Title: Overview - Redmine 02:15:14 yes 02:15:28 i try create db but : 02:15:41 ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) 02:16:00 and pkg check -d say me : 02:16:10 mysql80-server is missing a required shared library: libprotobuf.so.3.19.4 02:17:05 Sounds like your problem is with mysql, not redmine. 02:17:15 yes 02:17:23 but how correct it ? 02:18:01 i was delete sys on db of mysql 02:18:32 I'd reinstall mysql80-server. 02:18:46 try it 02:19:03 but the problem is same 02:19:13 i think can't purge conf file 02:19:46 I'm out of easy guesses, and that's all I know enough to suggest. 02:23:22 no more sggest ? 02:24:16 it's isn`t work i re-intall to 13.2 02:25:05 i don´t know how restart with clean distrib 02:28:23 white-wolf: this will install deps: pkg info -d mysql80-server | grep -v mysql80-server | xargs pkg install -y 02:29:36 The most recent versions of packages are already installed 02:34:55 i have a qemu guest running on arch with libvirt and dns has stopped working, im a freebsd newbie so i not sure where to draw the line in the problem betwen guest and host, heres the libvirt network config http://ix.io/4sn4 02:35:25 and my /etc/resolv.conf on the guest is "nameserver 192.168.122.1" 02:35:53 try with 1.1 or 0,1 02:36:23 you mean straight to gateway in resolv? 02:37:05 white-wolf: cheers it works, any idea why/how it got that way? 02:37:47 your box have a dns server 02:38:13 for more anonyme use opendns 02:38:20 yeah on the host libvirt starts a bunch of dnsmasq processes, 02:38:26 this would imply they are not working? 02:38:57 use NAT 02:42:23 well thats what i thought i did 07:16:06 Is there any explanation why 13.2 is delayed? 07:19:41 I wish to setup my laptop with freebsd 13.2 07:59:27 three extra RC builds... last minute changes/fixes... check https://cgit.freebsd.org/src/log/?h=releng/13.2. Why wait? You can install 13.2-RC6 and later update to RELEASE with freebsd-update or rebuild from src. 08:48:00 testing finds bugs. which is why we encourage testing 09:11:04 so, no testing, no bugs? 09:11:59 No testing, no known bugs 09:12:47 and unknown ones are just "undocumented features" 09:36:29 Good morning. I have migrated to a new disk using zfs send/recv, and ran an EFI update command from the same guide. The EFI is now bootable from the UEFI bootlist, but I still end up on the old zroot. I am guessing I need to rename the new zpool? Or is there another way? And is it simple to boot into a live USB and rename, or is it a can of worms? 09:53:09 What does "bectl list" show? 10:09:34 13.1-RELEASE_2023-03-12_160133 - - 105M 2023-03-12 16:01 10:09:34 default NR / 8.12G 2023-03-11 18:42 10:18:05 This is the guide I followed: https://people.freebsd.org/~dch/posts/2021-05-12-nvme-on-freebsd.html 10:18:06 Title: Adding a new nvme drive - Random Musings 10:18:12 ?? 10:35:40 zapata: I know I can install the release candidate but I wish to go directly with release so I only use stable stuff 11:05:53 lol, it that date again :D 11:07:45 Is there any integration for VS code like the docker one that works with jails 11:51:18 cristiioan: why not yet it, to make sure it will be stable — for your use-case, and report bugs if it isn't 11:52:37 morsing: did you set the new zpool as boot device? 11:52:54 meena: How do I do that? 11:54:24 https://man.freebsd.org/loader.conf(5) 11:54:25 Title: loader.conf(5) 11:55:48 vfs.root.mountfrom="zfs:/pool/fs" 11:57:28 meena: But /boot is on ZFS, the new pool. Catch-22? 11:59:17 I think this goes wrong even before the kernel is loaded. 12:00:49 I've run into a port that writes some files into /usr/local/etc/newsyslog.d but as far as I can see that should be /usr/local/etc/newsyslog.conf.d. I couldn't find too many references to newsyslog.d outside of a 2015 BSDCan paper referencing support for it has been added https://www.bsdcan.org/2015/schedule/attachments/327_AsiaBSDCon2015_paper.pdf. Can anyone shed some light on this before I submit a patch? 12:02:34 My best guess so far is at some point newsyslog.d was used and then replaced with newsyslog.conf.d 12:09:27 looks like it was introduced initially as newsyslog.conf.d (see b39df8fe2d85847497684b427a1b9c2908c4a576) 12:10:24 but it's /usr/local/etc/syslog.d for syslog itself, so someone must have confused the two 12:11:09 domlaut: I'm guessing /etc/newsyslog.conf history will have the answer 12:11:49 domlaut: also, I think it was at one time, all files, not just .conf 12:12:28 dvl: hey, you're actually the maintainer for the package :-) 12:13:12 lol 12:13:19 domlaut: which package? 12:14:40 acme.sh -- I have a patch ready, but I'm thinking whether the newsyslog.conf.d file should also be installed in share/examples as the cron.d file is 12:15:21 Oh yeah, that's an old one. I've also wanted to do a cron.d entry for that. 12:15:41 there is a cron installed, but missing a user. fixed that too 12:16:22 I checked mail/dta's cron file to see how they're doing it, and indeed its "* * * * * root ..." 12:16:22 Sorry I thought you said anvil, i got it. 12:17:04 acme.sh installs "* * * * *