I get the following when I try to remove 6.15:
linux615
linux615-headers
Starting
checking dependencies…
:: removing linux615-headers breaks dependency ‘linux615-headers’ required by linux-headers-meta
:: removing linux615 breaks dependency ‘linux615’ required by linux-meta
Done …
Try “sudo pacman -R linux-meta linux-headers-meta” first.
this is required by that - so:
first remove that - then you can also remove this
You can even do it in one command:
sudo pacman -Rns linux-meta linux-headers-meta linux615 linux615-headers
Edit Teo: Nachlese forgot the headers in the above command.
the one time I didn’t first try myself to verify … 
I should have left out the command instead of giving an incomplete one.
Thanks @Teo
Lets put it this way… What breaks if I do that? This is one package I don’t recall what it is for.
Update. Just updated the laptop, and same issue has popped up. This looks like a bug.
It makes sure that you always have the latest kernel version installed, just in case the mainline kernel you’re using reaches EOL.
Without the meta-package, people running an EOL kernel stand a risk of not having a kernel installed after updating their system, because the EOL kernel is removed during the update process.
Therefore, if you want to run a kernel version which is not an LTS kernel, you either need the linux-meta package — which is safest — or you need to uninstall the meta-package and manually install a kernel of choice.
Now, allow me to be Frank — since that is my name 
— if you really couldn’t figure out what the linux-meta package is for — which means that you haven’t bothered to learn how to properly use your package manager — then I would suggest keeping the 6.15 kernel on your system and not bothering with the removal of the meta-package.
Sorry for being so direct, but Manjaro is not a distribution for people who don’t want to take responsibility — there are other distributions catering to that market segment — simply due to the fact that Manjaro is based upon Arch.
Yes, it makes Arch a little friendlier, due to the presence of a graphical package manager, a tool for selecting the right Nvidia drivers and a graphical installer, but it’s still an Arch base underneath, and you will never be able to use it successfully unless you start reading some man pages, or even looking at the information for a package in your graphical package manager — the information is there, and it’ll tell you what packages it conflicts with, and what files it installs on the system, and what it depends on, what is is required for, et al.
It’s not. It’s a feature.
Has nothing to do with that. It is a package automatically installed by the kernel installer. I did not manually install the meta package. I was using Manjaro tools to install it. If Manjaro tools are broken in this regard, that is what I am reporting.
Typical Linux people. If you didn’t do XYZ, you are the one at fault.
In addition, after looking at the package installer, their seems to be no equivelent for 6.16. So many things broken here. If you install the Meta package, it pulls in 6.15. This is why i was asking if I clear this out if it breaks something as it is the only option.
So yes, I looked at the manual route. So would that also not be ‘broken’?
I am irritated the way you I assumed I didn’t do something.
Removing the Meta packages, which I did not install and an update must have installed, fixed the problem.
I tested adding 6.15 back in through the tool I mentioned above, and I was able to remove it. Someone on the Dev team has fixed it but I cannot say when it was fixed.
Will mark this one solved.
No, they are not broken. As explained to you already, the meta package exists so as to make sure you will always have a bootable kernel installed if your current kernel goes EOL.
And that’s exactly what’s going to happen with 6.15 in a short while. So when 6.15 is declared EOL, the meta package will pull in 6.16 or 6.17.
Typical Windows people; everything they don’t understand about GNU/Linux is broken.
