The CMakeLists.txt file for print-manager got updated recently and it has updated some of min_requirement of packages to higher version.
while some of the packages i was able to update. I am not able to update plasma version.
current plasma version: 6.2.3
required plasma version: 6.2.90
i tried sudo pkcon update but that did not work.
How can i update it?
Hmm interesting.
6.2.3 is the branch that was released in November (there are two updates since then and the current version is 6.2.3).
6.2.90 is the beta release for the upcoming 6.3 release which comes out next month (Feb 11th).
Are you using Neon for an OS? If so which version are you running?
I am using Neon as virtual machine.
Recently i got involved in kde as contributor and i needed a kde-distro to work on some stuff. Since, I was unable to dual boot, using Neon seemed easy as virtual machine.
here are the distro details:
RETTY_NAME=“KDE neon 6.2”
NAME=“KDE neon”
VERSION_ID=“24.04”
VERSION=“6.2”
VERSION_CODENAME=noble
ID=neon
ID_LIKE=“ubuntu debian”
shouldn’t you use Neon Developer Edition then? Search if you can switch to it I assume you can easily.
Yeah I agree with rockandstone. Maybe you should seek out the unstable dev version of the OS. It should have what you need 
I have never used a dev version of any distro before. Does all the packages in those gets updated regularly? Also if I had to update, lets say “plasma version” in that, would sudo pkcon update do the trick?
Are there any fallbacks of those unstable versions do I need to know about?
Neon Testing will have the more beta level releases, and Unstable/Dev will be more —wild, if you will.
I’d suggest Testing for now. This has the current Beta version you need. All of the neon versions are updated quite regularly. Daily, even for testing and Unstable, which might make your work a bit more difficult.
Whenever there is a new Plasma version, it would come as part of your normal updates.
I also suggest for these to not use pkcon, but use apt directly. pkcon is just a layer on top that uses apt. If there are packaging issues, which are not uncommon on a fast-moving environments, pkcon won’t provide enough tools to get around these.
I don’t know what you mean by fallback?
sorry, i wrote wrong. By “fallback” I meant drawback or some I have to definitely keep in mind while working with testing version?
But I guess you already explained it. Thank you.
I have not been active for a while so in a way I am also a “new contributor”
When I checked recommendations for development setup they pointed me to kde-builder.
That worked nicely on my regular KDE Neon installation a couple of weeks back.