Unable to install using fusepm
Closed this issue · 8 comments
Getting the following error when trying to install:
fusepm install https://github.com/bolav/fuse-sqlite
Found 2 unoproj files. Wanted 1
Any ideas?
You have 2 unoproj files in your current directory. Choose which one is the one you want to use by fusepm install https://github.com/bolav/fuse-sqlite --unoproj main.unoproj
Now something different is happening?
fusepm install https://github.com/bolav/fuse-sqlite --unoproj main.unoproj
Found 0 unoproj files. Wanted 1
I'm unclear on what you are trying to achieve? Are you trying to make the example work, or to install fuse-sqlite into one of your projects?
I'm just trying to install it in one of my projects, but it does not work?
Please excuse me if i'm a total noob...
On Wed, May 18, 2016 at 1:14 PM, bolav notifications@github.com wrote:
I'm unclear on what you are trying to achieve? Are you trying to make the
example work, or to install fuse-sqlite into one of your projects?—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#8 (comment)
If you write fusepm install https://github.com/bolav/fuse-sqlite
in your projects directory it should be ready to use.
I do that, but this happens:
fusepm install https://github.com/bolav/fuse-sqlite
Found 2 unoproj files. Wanted 1
On Wed, May 18, 2016 at 1:49 PM, bolav notifications@github.com wrote:
If you write fusepm install https://github.com/bolav/fuse-sqlite in your
projects directory it should be ready to use.—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#8 (comment)
That error message states that you have 2 .unoproj
files in the current directory.
Ooook, so the error is on my side, i presumed it was on the github side...
Many many apologies....
On Wed, May 18, 2016 at 1:59 PM, bolav notifications@github.com wrote:
That error message states that you have 2 .unoproj files in the current
directory.—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#8 (comment)