On November 9, 2014 12:07:14 PM Tomaz Canabrava <tcanabr...@kde.org> wrote:
On Sun, Nov 9, 2014 at 3:43 PM, Dirk Hohndel <d...@hohndel.org> wrote: > > > On Nov 9, 2014, at 6:07 AM, Cristian Ionescu-Idbohrn < > cristian.ionescu-idbo...@axis.com> wrote: > > > > Answer to myself: > > > > $ pkg-config --print-errors --exists libgit2 > > Package libssh2 was not found in the pkg-config search path. > > Perhaps you should add the directory containing `libssh2.pc' > > to the PKG_CONFIG_PATH environment variable > > Package 'libssh2', required by 'libgit2', not found > > > > I needed to install package libssh2-1-dev. Patch attached. > > INSTALL needs to be updated too. > > I don’t see Subsurface requiring libssh2. A quick git grep shows no > mention. Is it possible that this is an issue with libgit2 packaging on > Debian? > Looks so. But if some compile libgit with ssh and others don't, it's not safer to require both?
I'd prefer to understand what's going on. To me it seems packaging is broken for that package if it requires another package but doesn't have a dependency
/D _______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
