THat's pkg-version output?

skered: yes it is

good morning! how does people running slack on their FreeBSD desktop? whats the best solution?

i just you know, went to the site

rtprio: yeah maybe that´s the best solution.. today I using macOS and the slack-app.. what I missing in the browser-version is I dont have tha "quick" sidebard to switch workspace..

grandpa, what was chat like when you were young? just irc and having to type /window and no emoji or file uploads or jira integration

the way god intended

rtprio: if /usr/ports exists, pkg may decide to use that instead of the remote repository to find packages, which means all base packages will appear to be orphaned. i think there's an option to stop it from doing that

another reason to have the ports tree cloned somewhere else and not at /usr/ports yay

i think this is arguably a bug, because the existance of a random directory shouldn't cause its behaviour to change like that

javavmwrapper does it selection logic by looking up the default java version from the local ports tree, instead of the default java version it was build with (and why would I change anything for the local ports tree, that is there to look at the ports, but they are build on my builder)

I have this very large archive of METAR weather data (it's not important why) but it is mostly repetitive text. It's 14813572689 bytes in content. On ZFS with lz4 it uses 4470997 in disk space. I am really loving the zfs compressed file system.

can someone here recomend a good dockbar something similar macOS which do you guys recomend?

oh if you get an answer let me know

I can't help you since I don't run a Desktop Environment but only a regular X Windows window manager.

KDE here but I don't do anything fancy, mostly just use krunner

In addition to KDE I know that Xfce has both a system tray and a panel.

(except to start konsole because some twat changed the startup directory to / rather than $HOME)

I using evilwm, but want a dockbar :)

My search-fu says that cairo-dock and plank are dockbars available under FreeBSD.

rwp: I will take a look on plank

does anyone use FreeBSD/powerpc64? i think we've broken crypto in main, curious if anyone has an earlier version where it works

Hi, i'm working on HA tunnels using CARP VIP as an endpoint for GRE tunnels, but i am having issues reaching the VIP as it doesn't answer to pings, whereas GRE tunnels to public IPs answer with no issues, any hint on how to resolve this issue ?

ivy: i guess i could rename it and see

hey can we use libadwaita/gtk4 software in freebsd?

yes

I have used solvespace on freebsd recently

which is gtk4

Is solvespace some kind of AI site aggregator?

Hey there! Upgraded from 14.3p10 to 14.4, on reboot I end up booting to 14.3. There's nothing more to update. I saw there was errata, tried turning off kernel_autodetect, no luck.

checked you have the right boot environment?

Reinhilde: How do I do that?

wipt: man bectl

wipt, if you use ZFS, more information can be found at `man bectl` as lts said

Thanks!

rtprio, not to be an annoying onlooker, but i'm sure i'm not the only one who has a few fears about converting to pkgbase, so I'm eagerly awaiting your resolution to this :)

well, i did update the repo to latest from quarterly

which actually didn't seem to work as i expected

Installed packages to be DOWNGRADED: FreeBSD-zoneinfo: 15.0 -> 15.snap20260402113922 [FreeBSD-base]

rtprio: you've somehow switched from base_latest_0 (15.0-RELEASE) to base_latest (15.0-STABLE)

check what you have in /usr/local/etc/pkg/repos/FreeBSD-base.conf, it should just be "FreeBSD-base: { enabled: yes }" and nothing else should reference that repository, except /etc/pkg/FreeBSD.conf which you never edit

then perhaps i need a fresh one

oh, i mean base_release_0, not base_latest_0 (which isn't a thing)

i think i was aiming for the tip of the 15 branch, but staying with release i suppose is ok

I'm doing something wrong. Using "bectl activate" on the snapshot created by freebsd-update, it shows as status R. Rebooting puts me into the same enviroment, though.

well, if you want stable/15, it's expected that 15.0 to 15.snap is a "downgrade" -- it's a little confusing, but pkg considers "snap" to be older than "0"

despite being newer

it's because usually you go 16.snap (16.0-CURRENT) -> 16.0 -> 16.1 ..., but in the case of switching from release to stable it's the other way, i'm not sure if there's a good fix

perhaps the stable packages should be called 15.0+snapYYYYMMDD or something

i think my goal was to get the most up to date ports. so that should be done as an override in /usr/local/etc/pkg/repos/ eh

yes, just add the new "url" key to /usr/local/etc/pkg/repos/FreeBSD.conf, everything else will be inherited from /etc/pkg/FreeBSD.conf

(you need to update both FreeBSD-ports and FreeBSD-ports-kmods)

or you could call it FreeBSD-ports.conf, to be more clear

i think that's what confused me was the kmods straddling _latest and _release_0

Hmm, renamed the snapshots, looks like I'm booting the new one, but somehow it isn't the version it should be?

pkg.freebsd.org/FreeBSD:15:amd64 <- kmods_latest* and kmods_quarterly* are for the ports branch you want, the _0 is for 15.0 and the one without _0 is for 15-stable

so you probably want kmods_latest_${VERSION_MINOR} if you're on 15.0R

we could probably put some more examples of this in /etc/pkg/FreeBSD.conf

yeah, that would help

even a wiki page of a list of common senarios with a code block to slap into the overrides

freebsd-version -ku reports 14.4-RELEASE-p1, uname -a says I'm still on 14.3-RELEASE. I've done the freebsd-update upgrade, install, reboot, install again. I've activated the new snapshot with bectl that each install seems to make.

Rebooting doesn't seem to actually boot the new snapshot, it just boots default. If I change the new snapshot name to default, it will boot it, but it's like the install never happened.

I'm using KDE Plasma 6.6.3 on FreeBSD 15.0-RELEASE with i915kms loaded, but it is using llvmpipe according to glxinfo

the iGPU is Intel UHD Graphic 630 on an Intel i7-8700

s/el i/el core i

booted with verbose mode: p.swee.codes/swee/c31053bc77cf4f859febd791c3eaa28c dmesg | grep drm p.swee.codes/swee/79d31d26485b4c778924638af7c99911 dmesg | grep i915

wipt, You say "snapshot" but Boot Environments are "clones" of snapshots. The snapshot is part of it but snapshots are read-only so it needs to become a file system clone to be read-write and bootable as a Boot Environment.

Renaming a snapshot to default is the wrong thing to do. And being a snapshot name it won't affect the file system clone names and won't affect the BE. To boot a different BE activat it with bectl.

If you want to boot a different BE than activated then at boot time there is a Boot Environments option which will cycle through each of the available boot environments. It's a little tedious if you have many BEs but boot and select that and explicitly select the BE to boot so that you know which one you booted.

Please verify that to upgrade from 14.3-RELEASE to 14.4-RELEASE you used "freebsd-update -r 14.4-RELEASE upgrade" followed by "freebsd-update install" then "shutdown -r now" then "freebsd-update install" a second time. Then "pkg upgrade -y".

And also what does "freebdsd-version -kru" say?