pkg upgrade breaks kde/plasma again

B

bgroper

Using 14.3
Latest pkg upgrade removes plasma6-plasma-workspace, but doesn't install updated package.
Was a long build from ports.
Also session plasma renamed as plasmax11
Is this normal ?

Edit. It seems the missing plasma6-plasma-workspace-6.6.3 has arrived in the pkg repo overnight.
 
KDE is a fast-moving dumpsterfire. It often drops out of the pkg repositories due to build errors; even more often for the 'latest' ports tree.
If you need something reliable, don't use KDE.
And as always: always check what pkg intends to upgrade or remove and if in doubt, check for fallout/build errors for the affected packages on freshports.
 
DON'T BLINDLY HIT "Y" KEY ON UPGRADES!
Always confirm carefully to see there are no unintentional deletions before hitting "y" on upgrades.

If you're specifying "-y" option for pkg upgrade, never attempt to use the terrible option! Even think of using it!

The option is only for managed environments that admins are managing local repository and putting safe-to-upgrading things into the local repo.
Otherwise, the option could be catastrophic!
 
sko said:
If you need something reliable, don't use KDE.
Click to expand...

I find this conclusion dead wrong.

sko said:
always check what pkg intends to upgrade or remove and if in doubt, check for fallout/build errors for the affected packages on freshports.
Click to expand...

And this one is very right.
Any kind of software with multiple packages is susceptible to fallout. KDE being big and with quite a few packages, the chance increases.
 
This is a risk you run when using Latest package repository. I swear, almost every "X package got deleted!!!!" post would not be needed if people were using Quarterly. If you can't handle things occasionally breaking, or don't want to put in the time to verify what you are doing, don't run latest.

I do run Latest repo, but I learned early on to:
T-Aoki said:
DON'T BLINDLY HIT "Y" KEY ON UPGRADES!
Always confirm carefully to see there are no unintentional deletions before hitting "y" on upgrades.

If you're specifying "-y" option for pkg upgrade, never attempt to use the terrible option! Even think of using it!

The option is only for managed environments that admins are managing local repository and putting safe-to-upgrading things into the local repo.
Otherwise, the option could be catastrophic!
Click to expand...

I don't have system breaking problems running Latest, because I pay attention to what it is doing. If something is getting removed that I don't want to be removed, I can investigate why. That usually comes down to a couple of things - 1. build problems with the ports or 2. certain dependencies have been updated but the port hasn't yet been updated to use those dependencies. In these cases, simply waiting a couple of days resolves the problem.
 
jardows said:
I swear, almost every "X package got deleted!!!!" post would not be needed if people were using Quarterly.
Click to expand...
Unfortunately, it's not specific for latest.
Even on quarterly, if any huge one got upgraded with security fixes (something like www/chromium, for example), there can be broken window that previous versions are deleted but the upgraded ones are not yet finished building.
 
T-Aoki said:
previous versions are deleted but the upgraded ones are not yet finished building.
Click to expand...
creation/updating of ports repositories is an atomic operation with poudriere. otherwise it would be a constant hell of dependency issues.

After the whole ports tree was built by poudriere, it recreates the pkg repository. every port that couldn't be built for whatever reason is missing from packages - short and simple.


Zare said:
I find this conclusion dead wrong.
Click to expand...
It's a completely linux-centric (to put it *very* mildly) project with WAY too many moving parts and dependencies that are often heavily linux-specific. While for most developers in the UNIX (i.e. BSD, solaris/illumos) world "production safe first" is still a thing, the first rule of development in linux-land for many years has been "break stuff, maybe fix later (but it runs on my laptop, so I don't care), but push as many new versions per week as possible". And if you don't run systemd/linux your bug reports are usually invalid to them anyways.
 
Thanks for all the replies and suggestions.
I'm committed to both FreeBSD and KDE/plasma for various reasons, personal prejudice included.
Over some years and many updates I've learnt that KDE is potentially fragile on FreeBSD.
Suggested solution/s include some or all of the following :
- accept greater personal responsibility for the whole upgrade process
- never use pkg upgrade -y
- be vigilant regarding KDE packages being removed and replaced, especially removed and NOT replaced
- don't rely solely on the pkg repos
- be prepared to build from ports if necessary
- delay helps. avoid being an early adopter, let other users find problems in repo pkgs before upgrading.
'nuf sed and YMMV
 
You must log in or register to reply here.
Back
Top