No kde5 in FreeBSD/latest

J

jb82

Hello guys,
have switched to FreeBSD because of OSS. Installed kde5 from quarterly but there's no kde5 in latest and I received this:

Please, is that bug, or expected? I just need KDE, wanted latest stuff, feels weird for a newcomer. Thank you.
Code: 
Installed packages to be REMOVED:
    kaddressbook: 22.12.0
    kalarm: 22.12.0
    kde5: 5.24.7.22.12.0
    kdepim: 22.12.0_1
    kdepim-addons: 22.12.0
    kdepim-runtime: 22.12.0
    kmail: 22.12.0
    korganizer: 22.12.0
 
Post the whole output. It's probably being removed due to a conflict with some other package.
 
It looks like it want to remove everything from desktutils/kdepim, if kdepim gets removed then kde5 has to be removed too. It's not as 'destructive' as you might think, x11/kde5 is a so-called meta-port. It doesn't contain anything of itself, it simply depends on a bunch of other ports/packages.

Still, not sure why it wants to remove almost everything from deskutils/kdepim though.
 
Yeah. Seems to be working just fine even without that. One tiny aspect of this issue is that all tutorials describe pkg install x11/kde5 as the correct way to install KDE but after switching to latest there's no such thing.
 
Welcome!

jb82 said:
Please, is that bug, or expected? I just need KDE, wanted latest stuff, feels weird for a newcomer. Thank you.
Click to expand...
This kind of breakage happens from time to time with latest, sometimes a package build fails and the affected package and its dependencies won't be installable for a few days, until the problem is fixed; packages will reappear in a subsequent build. You can check on FreshPorts the current availability of a given package for all architectures in both quarterly and latest branches.

If you don't need the packages that pkg wants to remove, just let it remove them, you can always reinstall them later. Otherwise, wait a few days before performing the upgrade.

By the way, if you don't want the whole KDE package but only the Plasma desktop, you can install the lighter x11/plasma5-plasma (I recommend adding x11/kde-baseapps too) instead of x11/kde5, and then add to the mix the KDE applications you actually use, either one by one or using other metapackages such as misc/kdeutils, graphics/kdegraphics, etc. Have a look at the dependencies of x11/kde5 to get an idea of the existing KDE subsets.
 
There is no package fallout for x11/kde5 right now. And even if there was, a missing package in the repositories will not remove your locally installed package. If you run pkg version -vR it will show up with a '?' to indicate it's 'orphaned'. This just means pkg(8) isn't going to touch it. It certainly won't delete it.

One downside of x11/kde5 being removed is that a pkg-autoremove(8) will remove everything else that was automatically installed as a dependency of kde5. Which is the entire KDE 5 install.

I suspect it's one or more of the packages that come with deskutils/kdepim are having build issues. That would result in the skipping of deskutils/kdepim and x11/kde5. That might explain why they're missing in the repos. But that doesn't explain why it wants to remove them on your system though.

bsduck said:
By the way, if you don't want the whole KDE package but only the Plasma desktop, you can install the lighter x11/plasma5-plasma
Click to expand...
For now I suggest doing a pkg set -A0 plasma5-plasma. That will mark it as 'non-automatic', so pkg-autoremove won't remove your entire KDE 5 desktop.
 
I checked the last build logs (dated: Thu, 09 Feb 2023 01:04:15 GMT) and both x11/kde5 and deskutils/kdepim are there. Not sure why they're not in the repositories though, it's been several days. Should be enough time for the mirrors to sync up. Maybe that's still going on. In any case, they both should appear in the repositories again some time soon.

http://beefy16.nyi.freebsd.org/build.html?mastername=131amd64-default&build=58633340e9ed
(You need IPv6 to access these logs)

meaw229a said:
It seems that KDE on FreeBSD just get an upgrade to 5.27 and may be therefore the older 5.24 port is not available anymore
as it gets replaced with 5.27.
Click to expand...
That might explain why they got removed on the OP's system. If any of the dependency libraries was updated it would trigger a removal of the old packages. Normally they would get replaced by the new versions of these packages but those were missing.
 
Alexander88207 said:
I know this only so if a pkg upgrade is made and a package is gone then it is also removed.
Click to expand...
No, that's not always the case. If the missing package doesn't have any (updated) dependencies then it would remain installed. pkg(8) doesn't remove installed packages because they've been orphaned.

What might have happened here is this dependency chain; A -> B -> C. So A is a dependency of B, and B is a dependency of C. If A gets updated, B and C need to be updated too. But both B and C were missing from the repositories. In that case an upgrade of A would trigger the removal of B, which in turn triggers a removal of C.
 
Just as an example, I installed Apache from my own repository:
Code: 
root@fbsd-test:~ # pkg version -vR
Updating dicelan repository catalogue...
dicelan repository is up to date.
All repositories are up to date.
apache24-2.4.55                    =   up-to-date with remote
apr-1.7.0.1.6.1_2                  =   up-to-date with remote
ca_root_nss-3.88.1                 =   up-to-date with remote
curl-7.87.0_1                      =   up-to-date with remote
expat-2.5.0                        =   up-to-date with remote
gdbm-1.23                          =   up-to-date with remote
gettext-runtime-0.21.1             =   up-to-date with remote
indexinfo-0.3.1                    =   up-to-date with remote
jansson-2.14                       =   up-to-date with remote
libidn2-2.3.4                      =   up-to-date with remote
libnghttp2-1.51.0_1                =   up-to-date with remote
libpsl-0.21.2_2                    =   up-to-date with remote
libunistring-1.1                   =   up-to-date with remote
libxml2-2.10.3_1                   =   up-to-date with remote
pcre2-10.42                        =   up-to-date with remote
perl5-5.32.1_3                     =   up-to-date with remote
pkg-1.19.1_1                       =   up-to-date with remote
readline-8.2.0                     =   up-to-date with remote
Everything's up to date. Now I'm going to remove the apache package from my repository to simulate a package going missing.
Code: 
root@fbsd-test:~ # pkg version -vR
Updating dicelan repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01
Fetching packagesite.pkg: 100%  302 KiB 309.2kB/s    00:01
Processing entries: 100%
dicelan repository update completed. 1334 packages processed.
All repositories are up to date.
apache24-2.4.55                    ?   orphaned: www/apache24
apr-1.7.0.1.6.1_2                  =   up-to-date with remote
ca_root_nss-3.88.1                 =   up-to-date with remote
curl-7.87.0_1                      =   up-to-date with remote
expat-2.5.0                        =   up-to-date with remote
gdbm-1.23                          =   up-to-date with remote
gettext-runtime-0.21.1             =   up-to-date with remote
indexinfo-0.3.1                    =   up-to-date with remote
jansson-2.14                       =   up-to-date with remote
libidn2-2.3.4                      =   up-to-date with remote
libnghttp2-1.51.0_1                =   up-to-date with remote
libpsl-0.21.2_2                    =   up-to-date with remote
libunistring-1.1                   =   up-to-date with remote
libxml2-2.10.3_1                   =   up-to-date with remote
pcre2-10.42                        =   up-to-date with remote
perl5-5.32.1_3                     =   up-to-date with remote
pkg-1.19.1_1                       =   up-to-date with remote
readline-8.2.0                     =   up-to-date with remote
See how it's now marked as 'orphaned'? Lets do a pkg upgrade and check what it does.
Code: 
root@fbsd-test:~ # pkg upgrade
Updating dicelan repository catalogue...
dicelan repository is up to date.
All repositories are up to date.
Checking for upgrades (1 candidates): 100%
Processing candidates (1 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.
root@fbsd-test:~ # pkg version -vR
Updating dicelan repository catalogue...
dicelan repository is up to date.
All repositories are up to date.
apache24-2.4.55                    ?   orphaned: www/apache24
apr-1.7.0.1.6.1_2                  =   up-to-date with remote
ca_root_nss-3.88.1                 =   up-to-date with remote
curl-7.87.0_1                      =   up-to-date with remote
expat-2.5.0                        =   up-to-date with remote
gdbm-1.23                          =   up-to-date with remote
gettext-runtime-0.21.1             =   up-to-date with remote
indexinfo-0.3.1                    =   up-to-date with remote
jansson-2.14                       =   up-to-date with remote
libidn2-2.3.4                      =   up-to-date with remote
libnghttp2-1.51.0_1                =   up-to-date with remote
libpsl-0.21.2_2                    =   up-to-date with remote
libunistring-1.1                   =   up-to-date with remote
libxml2-2.10.3_1                   =   up-to-date with remote
pcre2-10.42                        =   up-to-date with remote
perl5-5.32.1_3                     =   up-to-date with remote
pkg-1.19.1_1                       =   up-to-date with remote
readline-8.2.0                     =   up-to-date with remote
See? Nothing happened to the installed apache24 package. So the fact that a package is missing in the repository doesn't imply it gets removed.
 
KDE 5.26.5 in the latest, everything seems to be working smoothly. Pleasant FreeBSD experience so far! (well, modulo Wifi but that was expected :-) ). Thanks guys!
 
You must log in or register to reply here.
Back
Top