I was trying to use these instructions from June 22 and get the response that core, extra, and multilib are up to date but error: target not found: plasma-x11-session
Did something else change afterward? Thank you.
That package does not exist yet in the Stable branch. It only exists in Plasma 6.4, which is still only in the Unstable branch for now.
2 Likes
Thank you. I thought something had changed on this machine and couldn’t figure out what could have been the cause; but, now that you explain this, I remember that I switched to unstable branch and then switched back to stable. I thought I did the switch back in a way that was supposed to not leave anything from unstable that had not yet reached stable; but, evidently, I didn’t do it correctly or misunderstood.
The only reason I noticed something different is that the mouse pointer kept growing if moved around a bit. Thanks.
1 Like
You better restore a Timeshift snapshot in this case, because reverting packages on major updates is likely to mess with the config files and you may end up in many issue because of the update config files.
1 Like
Thank you very much for the warning. I’ll look into that. The instructions for switching to unstable branch and back make it sound quite simple; but, apparently, there are a few items to be wary of, especially if one’s knowledge in this area is small, such as in my case.
No, it is really simply one command to go back from Unstable to Stable. You probably switched to Stable branch but did not force downgrading the packages so you stayed with packages from Unstable.
To force downgrading packages after switching back to Stable branch just do the command sudo pacman -Syyuu (the double yy is to force refreshing the mirror packages list, and the double uu is to force the downgrade of packages).
But as said on major updates there are often changes in some configuration files, and downgrading packages will not revert these changes, this is why I recommend in this case to restore a Timeshift snapshot instead of downgrading, so the old configuration files are also restored so you do not have issues regarding new modified configurations that were in the previous major update (from Unstable).
2 Likes
Thanks again. I believe I followed these instructions and tried to downgrade packages; but there is only one y shown in that command near the very bottom.
I could have made a mistake also and left off a u; it’s been a couple weeks, now, and do not recall what I typed but I do recall following those instructions and wanting to downgrade. I switched to unstable for about ten minutes to see if the repository might have a newer version of an application I wanted. The new version was not available; so, I switched back.
You typically don’t need the second y nowadays.
You can check without switching - just use branch compare.
3 Likes
When switching branches, you do need -Syyu, and when switching from a more bleeding-edge one to a more stable one, you need -Syyuu. 
2 Likes
I just checked on my laptop and desktop. I didn’t actually downgrade to stable just switched branches and checked if it picked up the differences.
Laptop needed the extra y for switching to stable, and didn’t need it for switching back to unstable.
Desktop didn’t need it at all.
Neither had been updated in a while, so perhaps that may be relevant.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.