Competence

No. It will boot the previous kernel, but the user experience will be at least suboptimal if some packages have already been removed during the upgrade, but the upgrade stopped at some point because a downloaded package was corrupt, leaving lots of dependent packages unconfigured. In case networking doesn’t work, it’s also inconvenient to manually download the affected package on another machine and transfer it with a usb stick onto the computer to restart the upgrade.

Well, as I’m using Debian, maybe I’m a more cautious type.

If the update is successful. If there are failures in critical steps, well…

I do “;” to definitely run the shutdown after the update process exits.

If you’re able to successfully boot the machine afterwards is not your concern?

Yes, in this command one liner, the system should not power off when the update took too long.

Or is yes somehow supposed to take care of this?

No, yes is simply answering all questions asked during the update procedure (start upgrade, replace config files, restart services) with “yes”.

MSI files are actually comparable to Linux packages, from what I understand, in that the program that does the installing (and which gets root/admin permissions for that) comes with the OS itself.

Neat. I’ve always wondered why e.g. 7zip is distributed as both, MSI and exe installer. Now that makes somewhat sense to me.

@unknown1234_5@kbin.earth

I’d say it’s more about that Linux packages aren’t (distributed as) compiled binary installers (appimages are executables, but no installers), like msi or exe installers for Windows, but (as) essentially plain archives.

Actually, Elmo didn’t found Tesla.

The classic:
https://packages.debian.org/trixie/sl

But why does it say 2 - 53? Is it the due date and the bottle was manufactured in 1943?

You may also just add the LMDE repo (Faye is Bookworm, Gigi is Trixie) or the official Mozilla one and install the standard, non ESR version of Firefox from that one.

Yes, e.g. with Qemu or FEX.

I suppose it’s official, as it’s also on the Wikipedia page on WSL.

Sure, but as I understood, the question was how to do that “properly” with dpkg and apt-get, i.e. without the ‘new’ apt script.

@fluckx@lemmy.world

dpkg doesn’t resolve dependencies (that’s a feature of apt) which means that if you install a Debian package with dpkg, you’ll have to manually install all dependencies first, and they won’t be marked as automatically installed

Usually installing a manually downloaded package and its dependencies works like this:
# dpkg -i package-file.deb
# apt-get -f install

So apt-get can be used to install missing dependencies afterwards while marking them as automatically installed.

Any idea why flatpack doesn’t remove unused (automatically installed) dependencies automatically or at least give a hint, as e.g. apt does?

It says ‘run as root’, not installed using root privileges. You’d also need root privilege to dd an image onto a drive either.

Thanks.