Behavior

After upgrading my PopOS to version 20.10: When I try to install Boost Note v0.16.1 I get the following error:

The following packages have unmet dependecies: boostnote: Depends on: gvfs-bin but it is not installable

As I found out: gvfs-bin is discontinued and not part of the newest ubuntu version.

Expected behavior

I expect the install manager Eddy to install Boost Note.

Steps to reproduce

1. Upgrade your Ubuntu System to the newest version 20.10
2. Try to install the current version of Boost Note (v0.16.1)
3. Get error message

Environment

• Boostnote version: v0.16.1
• OS version and name: Pop!_OS 20.10

I solve this issue by using this method

sudo apt install libsecret-1-dev gconf2 python2 python-is-python2 sudo dpkg --ignore-depends=gvfs-bin -i boostnote_0.15.1_amd64.deb

Hope this can solve your issue

Thanks @yulibu. I will try your fix, but this can't be the solution. I don't really want to change my default python version and guess the dependency to a deprecated package just needs to be resolved. Atom seemed to have had the same issue.

If that case just try to use sudo dpkg --ignore-depends=gvfs-bin -i boostnote_0.15.1_amd64.deb

hope it's working for you because gvfs-bin replaced with gfvs

@riskysciolism Is there anything that still needs to be done to wrap up this issue? Or is the solution provided by yulibu sufficient?

The suggested fix using --ignore-depends=gvfs-bin in the dpkg command does allow to install Boostnote (in Ubuntu 20.10 in my case). However, after that, the package manager and apt keep complaining of having a broken package. So I don't think that's acceptable as a fix.

I am sorry for the late answer, but I second @naimo. I don't think that this is a solution. As I stated earlier, Atom seemed to have had the same issue, which they resolved.

After Boostnote been installed with --ignore-depends=gvfs-bin, edit the file /var/lib/dpkg/status, search gvfs-bin in the boostnote section, delete the string gvfs-bin.. The broken package issue will be fixed.

Agreeing with @naimo and @riskysciolism here. To expect users to fuddle with their dpkg files is introducing a whole world of risk that is not sane, and especially so considering the gvfs-bin dependency is met, but with a different package.

Other apps have already resolved this issue, as others have mentioned, but from what I am finding the way Mailspring handled it seems best and may be applicable here as well; https://github.com/Foundry376/Mailspring/pull/2220

Remove gvfs-bin from node_modules/electron-installer-debian/src/installer.js before you build the deb package. It's just a workaround though. I used this command.

sed -i -e "s/'gvfs-bin',//" node_modules/electron-installer-debian/src/installer.js