 "Pratham Patel, this is with..." <- Yep, I got the tarballs from kernel.org and ofc verified the signature. After `make olddefconfig`, I do get `CONFIG_RUST=y` from the `.config` file.
[01:16] <thefossguy> Even after booting in the new kernel, I get `CONFIG_RUST=y` from `/boot/config-$(uname -r)`
 "(although all flavours should..." <- Why? Different flavors target different use cases which might have different kernel needs. Ubuntu Studio for example wants the low-latency kernel. 
[04:42] <alkisg> juergh: I don't think that was a deliberate choice, I think they just weren't notified to update their seeds
[04:43] <alkisg> When there's a deliberate choice, sure; but e.g. if you ask martin now "does mate deliberately offer a different kernel than ubuntu"? He'll probably answer "wut?" :D
[04:44] <juergh> he. fair enough.
[04:46] <alkisg> So, to sum up my problems are two, (1) why, when someone starts with -generic, they end up getting -hwe with plain updates, and (2) why some of them end up with -oem too, i.e. 3 different kernel series in parallel
[04:47] <alkisg> Since this isn't a known issue, I'll try to investigate the apt logs of affected machines when I next get a chance
[14:28] <Eickmeyer> alkisg: Ubuntu Studio wanting the lowlatency kernel is a deliberate choice.
[14:38] <alkisg> Eickmeyer: yeh, I know about that one