I'm using an AMD Ryzen iGPU on Wayland. I switched to Testing because the support already existed, but the kernel and mesa versions in stable were buggy for my particular GPU and I didn't want to make a FrankenDebian.

I've honestly never wrestled with Secure Boot in this way; I usually disable it if it won't let me boot my preferred kernel. From my brief online searches, enrolling your own keys is possible, but that depends on the kernel modules being signed in the first place, and carries risk of bricking devices if not done correctly. So you might just want to disable Secure Boot, or otherwise stick to kernels provided by your distribution.

I honestly have only passing knowledge of it, but my understanding is that Open Build Service is more for sharing software whose source code you are allowed to distribute. If you aren't looking to distribute at all, the solutions other users suggested might be better.

There's also a way to create an APT repository entirely on your own system, without a web server, which I haven't tried myself, but a DuckDuckGo search found this: https://help.ubuntu.com/community/Repositories/Personal

Unsure if this is what you're looking for, but I've seen some FOSS projects use https://www.makedeb.org/ and https://openbuildservice.org/ to create public Debian repos.

I hope these shots aren't a good representation of the whole episode, because if they are, it's a 15 minute scene of L'Ak and Moll on a planet followed by 35 minutes of close-up shots of Rayner

It's just a future, and can be changed. I'm not aware of any objective in-universe measure of what is and isn't the prime timeline, it's really just what the writers choose to depict as such, which events are altered by time travelers and which ones stand. Since we've seen a full two seasons in this version of the 32nd century, it's more likely that future shows will try to keep consistent with it, but it's also possible they'll be "retconned" into an "alternate reality".

I was dualbooting 2 Linuxes for a long time. All that you need is to install GRUB once on one of the distros, but having two or more bootloaders in the same EFI System partition is generally harmless, and might happen due to how some distros' installers are written. In that case the BIOS boot order will decide which one to use. Either way, you only need one boot partition.

It is safe to delete all partitions on your hard drive if and only if you have backed up any important data on them. It's basically the same as installing a new hard drive. The installer for your distro will be able to re-create all of them.

I have personally never used a shared /home between multiple distros, but based on my experience switching desktop environments, there are likely to be conflicts between files that lead to bugs. Arch and Pop!_OS will have vastly different versions of most software, and it's possible that changes to a config file in one distro may break the program in the other. Shared /home is better for if you have just one OS installed, and reinstall it occasionally.

Definitely flatpak related then. Try running one of your flatpak apps from the terminal, and post the output here; might help pinpoint the issue. You can list the ones you have installed with flatpak list, then flatpak run .

Me too, but I also think it just looks cool. Sci-fi vibes.

oh it is still being updated! great.

Ah okay, that makes more sense.

Debian's preinstalled software on some desktops is one of my main problems with the distro and one of the reasons I hesitate to recommend it to newbies, so I like the idea behind something like this or SpiralLinux, but I wouldn't use either distro myself, because I find that the more a distro deviates from upstream and adds its own configurations, the harder it is to troubleshoot issues or configure them the way I like.

As for Xebian, I don't see the point of trying to make Debian Sid easier to install. It's a development release, guaranteed to have many bugs, and not really suitable for the average user. If you can't install and "declutter" sid yourself, it's better to be using the latest stable or even testing release.