5.2 extension removal bug?

[malbo]

Not sure if this is the right board, but I marked alsa-modules-3.0.21 for deletion and in doing so v4l-dvb-3.8.13 and i2c-3.8.13 were also marked. The 3.0.21 versions were not grabbed.

I don't know if those are legitimately not needed anymore, but I figured they would be needed by alsa-modules-3.8.13.

Should that be the behavior?  Actually... I noticed there are a lot of <extension>-KERNEL.tcz dependencies out there... does that mean a lot of things have been baked into the kernel now?

Thanks!

[gerald_clark]

KERNEL gets replaced by the output of 'uname -r'.
This allowa a dep to specify that a certain module is required without tying itself to a specific kernel.

[malbo]

Got it.

So is it just up to the user to be cautious when deleting certain extensions?

Should I have done it differently? Is it best practice to remove old kernel versions before upgrading?

[gerald_clark]

Mark for deletion will also mark dependencies if they are not needed by another module.
For this reason, it is best to install the new modules before deleting the old ones.
Otherwise they will be re-downloaded and installed when the new modules are installed.

[malbo]

ok thanks!

[malbo]

By the way... Won't downloading the new versions first just cause the same issue I'm having, since they're just going to pull the latest KERNEL version? It won't pull the older ones, right?

[gerald_clark]

KERNEL is only expanded in deps processing.  If you select an extension to download, it downloads that extension.

[malbo]

Sorry I phrased this question poorly...

I mean if I download the new extensions first and then go to delete, using the deletions tool, I'll run into the same issue, where it will try to delete the newer one. Right?

[gerald_clark]

Try it and see.
You can view the deletions list, and clear it if you don't like what will be removed.