On Fri, 18 May 2018 21:20:16 +0530 Pirate Praveen
<prav...@onenetbeyond.org> wrote:
libgit2 0.27 is now available in experimental. Please make sure your
package is ready for this version by the time we upload this package to
unstable in one to two weeks. The severity of this report will be raised
to serious once libgit2 0.27 is uploaded to unstable.
The build failed, but it could be a bug in libgit2 itself as new version
is supposed to be using mbedtls instead of openssl.
configure:19592: checking for GITCHANGEBAR
configure:19601: $PKG_CONFIG --exists --print-errors "$GP_GTK_PACKAGE >=
2.18
glib-2.0
libgit2 >= 0.21"
Package openssl was not found in the pkg-config search path.
Perhaps you should add the directory containing `openssl.pc'
to the PKG_CONFIG_PATH environment variable
Package 'openssl', required by 'libgit2', not found
configure:19606: $? = 1
configure:19624: $PKG_CONFIG --exists --print-errors "$GP_GTK_PACKAGE >=
2.18
glib-2.0
libgit2 >= 0.21"
Package openssl was not found in the pkg-config search path.
Perhaps you should add the directory containing `openssl.pc'
to the PKG_CONFIG_PATH environment variable
Package 'openssl', required by 'libgit2', not found
configure:19629: $? = 1
configure:19645: result: no
Package 'openssl', required by 'libgit2', not found
configure:19665: error: Package requirements (gtk+-3.0 >= 2.18
glib-2.0
libgit2 >= 0.21) were not met:
Package 'openssl', required by 'libgit2', not found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables GITCHANGEBAR_CFLAGS
and GITCHANGEBAR_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
