Conflict between linux-meta and linux617

[flutes]

Hi, I’m coming back to my Manjaro workstation after a while away and I’m getting an error with my big catch-up update. I’ve read a number of update threads and I can’t see this issue mentioned anywhere, though I noticed that 6.17 is EOL and that some people are having kernel issues. I’m used to just removing conflicting packages, but given this is the kernel, I really don’t want to mess around with it.

Here is the output of pacman -Syu:

:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
:: Starting full system upgrade...
:: Replace linux617 with core/linux-meta? [Y/n] 
resolving dependencies...
looking for conflicting packages...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: linux-meta-6.18-1 and linux617-6.17.13-1 are in conflict

Would really appreciate any guidance anyone can offer!

[Wollie]

What is the issue in just changing the kernel? Have you tried 6.12 or 6.18? Afterwards remove 6.17 and you should be fine with updating.

[Teo]

Hit Yes or Enter. Of course it has to be replaced or there will be no kernel at all.

[flutes]

I did hit enter - I tried both Y and n to confirm and got the same output each time.

As @Wollie suggested I am going to try to change kernels now.

Update: cannot install linux618 kernel without updating [long list of packages], which includes both linux617 and linux-meta.

[Teo]

Resorting the mirrors and syncing might help.

sudo pacman-mirrors -f

For the record: syncing a heavily out of date system is not exactly an “update” problem since it is by definition in an unsupported state. And if it is more than a couple of months it may be easier to reinstall.

[flutes]

Thanks for the help, everyone. I refreshed my mirrors, and then ran sudo pacman -Syu --ignore linux617, which gave me the option to safely remove the package during the full system update. I planned to switch kernels from the boot menu on reboot, but it just rebooted as normal and defaulted to 6.18. Hopefully I won’t have to go this long without an update again, but it’s good to know for the future!