Krunner5 suddenly showing from `pacman -Qm`

[zbe]

You had them installed before, if not by you, then pulled by something else or with install .iso. And when something is dropped to AUR well… there you go, now it’s bunch of AUR stuff.

[bedna]

@soundofthunder

Perhaps some of the packages you have installed from AUR had some of those as dependencies

Unlikely, unless all of those dependencies got pushed like a few hours ago, I checked very recently and there was only “my” stuff in there.

@soundofthunder

Any news about RAR in Plasma6?

Yeah, they are working on it, should be fixed and pushed soon: 483748 – compressing using rar does not work

Example:

pacman -Qii krunner5                                                                                                                                                                                 ✔ 
Name            : krunner5
Version         : 5.115.0-1
Description     : Framework for providing different actions given a string query
Architecture    : x86_64
URL             : https://community.kde.org/Frameworks
Licenses        : LGPL
Groups          : kf5
Provides        : None
Depends On      : plasma-framework5  threadweaver5
Optional Deps   : None
Required By     : None
Optional For    : None
Conflicts With  : krunner<5.111
Replaces        : krunner<5.111
Installed Size  : 854,70 KiB
Packager        : Antonio Rojas <arojas@archlinux.org>
Build Date      : 2024-02-03T18:53:07 CET
Install Date    : 2024-02-12T07:06:09 CET
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : Signature
Backup Files    : None
Extended Data   : None

Should not plasma-framework5 have been removed in the upgrade to plasma 6?

I am 99% sure this was not there yesterday or I would have gotten the reminder then.

[Aragorn]

@dmt

Some seem related to kde, and every one I checked has been dropped from the repos.

It is possible that they were pushed out to the AUR when they were dropped from the repo.

Given that they may still be needed by remnants of Plasma 5 — or just generic qt5-based stuff — they may still receive updates from their respective upstream. After all, Plasma 5.27 is an LTS, and Manjaro Stable has only recently updated Plasma 5.27.10 to 5.27.11, while Plasma 6 was already being introduced in Manjaro Testing.

[bedna]

So what does that mean?

I just remove them?

@zbe

You had them installed before, if not by you, then pulled by something else or with install .iso. And when something is dropped to AUR well… there you go, now it’s bunch of AUR stuff.

I ask again, should those not have been removed in the update to plasma 6?

How should I have been aware that this would happen so I can take precautions against it in the future?
And how do I fix it now?

[Aragorn]

@bedna

I ask again, should those not have been removed in the update to plasma 6?

Not necessarily, no. If they are not listed as dependencies and they do not conflict with any of the new packages, then they will remain in place.

[soundofthunder]

@bedna

should be fixed and pushed soon

Indeed, seems it has been. One less annoyance solved.

@bedna

I am 99% sure this was not there yesterday or I would have gotten the reminder then.

@Aragorn

It is possible that they were pushed out to the AUR when they were dropped from the repo.

I’m experiencing some mild deja vu;
recalling the Qt4 <=> Qt5 shamozzle (is that a word?).

[bedna]

@Aragorn

Not necessarily, no. If they are not listed as dependencies and they do not conflict with any of the new packages, then they will remain in place.

Ok, I also have a laptop on testing, not really installed antyhing other than manly-git and vlc-pause-click-plugin from AUR and the same things are in pacman -Qm on that machine too, I just checked.

So I should just accept the manjaro installations are like that now, putting things from the AUR onto my installations hence making the installation “not supported”?

The laptop installation was less than 2 months ago, a completely fresh installation.

[dmt]

@bedna

So I should just accept the manjaro installations are like that now, putting things from the AUR onto my installations?

No. You should accept that your interpretation of the situation is wrong.

Those packages existed in the repos and on your system, they were probably installed with KDE. They have been removed from the repo.

You either keep the packages (which now come from the AUR), or you remove them and anything that depends upon them.

EDIT:
This is part of system maintenance, you should know this as you’re on unstable.

[bedna]

@dmt

Those packages existed in the repos and on your system, they were probably installed with KDE. They have been removed from the repo.

Absolutely, Manjaro installed them when I ran calamares and installed the OS, I have not manually installed anything from them OR what they are dependencies of.

[nikgnomic]

@bedna

it seems Manjaro just put things in there by itself.

Manjaro is not responsible for your AUR helper script

I am 99% sure this was not there yesterday

I suggest check /var/log/pacman.log

Manjaro installed them when I ran calamares and installed the OS

I suggest check /var/log/Calamares.log

[bedna]

@nikgnomic

Manjaro is not responsible for your AUR helper script

LMAO, are you saying “yay -Quaq” changed anything on my system?

I have NOT installed f.ex plasma-framework5 and threadweaver5 that is now holding krunner5, pretty sure MANJARO did that.

[dmt]

@bedna

Absolutely, Manjaro installed them when I ran calamares and installed the OS

Yes they were a part of your OS (which you installed), and those packages came from the repos, so you were ok with them.

Now they may still be part of your OS, but don’t exist in the repos, so yay is telling you they’re now from the AUR.

It’s simply a decision you need to make, keep them or not.

@bedna

LMAO, are you saying “yay -Quaq” changed anything on my system?

The change is not on your system, it’s in the repos.

[bedna]

@dmt

Yes they were a part of your OS, and came form the repos, so you were ok with them.

Ok.

To recap then.

AS A WARNING FOR EVERYBODY ELSE!

If you have an installation less than 2 months old, COMPLETELY CLEAN, Manjaro thinks it is on YOU that you are now in a unsupported state.

[dmt]

It’s up to you to maintain your system, which includes accounting for changes.

Unless you actually went through with the yay update, then you’re still using the versions in stable, at least kpeoplevcard is the same.

[bedna]

i did EXACTLY that, followed all advice in release thread, asked for help here, and the response is a toxic “YoU aRe ReSpOnSiBlE”.

I will now let other know about this.

[dmt]

We’re simply explaining what has happened, and how to deal with it. Apparently that’s toxic, but having a tantrum and calling everyone toxic is not…

[Aragorn]

@soundofthunder

shamozzle (is that a word?).

It is now.

[zbe]

@bedna

I will now let other know about this.

Like this is something new on arch-based distros.

[nikgnomic]

@bedna

are you saying “yay -Quaq” changed anything on my system?

Other yay commands may have installed AUR packages

I have NOT installed f.ex plasma-framework5 and threadweaver5 that is now holding krunner5, pretty sure MANJARO did that

proof would be in system logs

the response is a toxic “YoU aRe ReSpOnSiBlE”.

Only one person in this topic is using inappropriate capitals

@system

top violations are trolling, starting a flame-war, harassment/provocations including posts/PM/Public social media, or not “Remembering the human” aka being hostile or incredibly impolite.