Code: Select all
sudo apt install ./file-deb
Here's what I need to install: https://github.com/StarLabsLtd/packages ... /Debian/11
Code: Select all
sudo apt install ./file-deb
Code: Select all
# gdebi package.deb
or
# dpkg -i package.deb
Yes, I never install those packages, only those because are strictly necessary to update my firmware. I will try those, thanks a lot.Bulkley wrote: ↑2022-06-17 05:42Be careful what you take from non Debian repositories. Keep an accurate record so that you can undo any damage. I suggest you do a full backup first.Code: Select all
# gdebi package.deb or # dpkg -i package.deb
apt is the best way, as root or sudo:fch wrote: ↑2022-06-17 05:19 Hello, I need to install some .deb files but I keep getting dependencies errors, I was runningis it thebest/correct way to do it?Code: Select all
sudo apt install ./file-deb
Code: Select all
apt install ./package.deb
hmm I see, I will use apt then, simpler way to doing it. Those are packages made for Debian from starlabs in order to be able to update their coreboot firmware. It wish it was already in the Debian repos.sunrat wrote: ↑2022-06-17 05:57apt is the best way, as root or sudo:fch wrote: ↑2022-06-17 05:19 Hello, I need to install some .deb files but I keep getting dependencies errors, I was runningis it thebest/correct way to do it?Code: Select all
sudo apt install ./file-deb
Needs to be run from the same directory as the .deb file or give the full path.Code: Select all
apt install ./package.deb
Gdebi works but is not in a default install (maybe comes with some DEs but not here on mine)
dpkg works too but it won't resolve dependencies whereas apt and gdebi will.
If you are getting dependency errors, maybe they don't exist in the Debian repos you have active. No surprise if you are installing 3rd party packages. You should post the exact error messages if you want help with them.
.deb packages can be built for Ubuntu and not Debian so that's another possible nightmare.
libc6 in Bullseye is v2.31 so yes, it is too old. libc6 is a core system file so not able to be upgraded. That file is basically not installable on Bullseye.
Correct. Doesn't help OP who is running Bullseye.
I do not know excatly why but it'srequired a newer version of fwupd, and flashrom in order to update it, not only newer but different somehow. With those installed, it can be done using gnome-firmware gui for example. I did it on other distros, but always with their version of fwupd, flashrom.
It's not only a matter of having the newest version of fwupd, buttheir version of fwupd, as they have forked it: https://github.com/StarLabsLtd/fwupdHallvor wrote: ↑2022-06-18 13:19 I upgrade my BIOS from an iso, as documented here: viewtopic.php?f=16&t=149682
It seems you can use either flatpak https://github.com/fwupd/fwupd/wiki/fwupd-flatpak
or snaps: https://snapcraft.io/fwupd
I don't like them much, other than a last resort; however, they are better than breaking your system with dependencies from unstable.
I already did it, they will be working on it. My dream is that those packages will reach debian repo one day.stevepusser wrote: ↑2022-06-18 20:16 Jeesh, why you don't inform Starlabs that they have the wrong debs for download for Bullseye?
Code: Select all
sudo apt install -f ./file-deb
Why? Not saying you shouldn't, just wondering why you should. apt by itself will pull in dependencies without the -f option.zarathustra-f90 wrote: ↑2022-06-24 00:37 You need the -f option on your command to install dependencies, i.e...