$ sudo apt install ./mailspring-1.3.0-amd64.deb
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'mailspring' instead of './mailspring-1.3.0-amd64.deb'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
mailspring : Depends: gir1.2-gnomekeyring-1.0 but it is not installable
E: Unable to correct problems, you have held broken packages.
Hey folks—it looks like they deprecated gnome-keyring in favor of libsecret, and we actually already use libsecret. Libsecret just maps to your underlying keyring, and I think that Mailspring installs gnome-keyring to ensure that you have at least /some/ keyring installed on your system.
Could you try installing the dpkg manually and force-ignoring that dependency? The app may just work, and we need to update the package config to mark that the dependency is optional.
Ooops, I just noticed, now debian complains about unmet dependencies:
$ sudo apt install httpie
Reading package lists... Done
Building dependency tree
Reading state information... Done
httpie is already the newest version (0.9.8-2).
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
mailspring : Depends: gir1.2-gnomekeyring-1.0 but it is not installable
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
Any suggestions to ignore that too? (if I run apt --fix-broken install, mailspring gets removed )
Edit - fixed
Fixed it by (1) unpacking the .deb, (2) deleting gir1.2-gnomekeyring-1.0 from the list of dependencies, and (3) repackaging the new .deb ¹.