Bug#899036: libgit2 0.27 transition
On Fri, 25 May 2018 09:41:03 +0200 Moritz Muehlenhoff wrote: > On Fri, May 25, 2018 at 01:00:22PM +0530, Pirate Praveen wrote: > > The current TLS implementation is Debian specific and it was rejected by > > upstream. Switching to upstream supported implementation is better in the > > long run. > > Ok, thanks. > > Just adding the upstream pull request for completeness https://github.com/libgit2/libgit2/pull/4173 -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#899036: libgit2 0.27 transition
On Fri, May 25, 2018 at 01:00:22PM +0530, Pirate Praveen wrote: > >Don't simply switch the TLS implementation to workaround a not fully > >understood build failure :-/ > > > > The current TLS implementation is Debian specific and it was rejected by > upstream. Switching to upstream supported implementation is better in the > long run. Ok, thanks.
Bug#899036: libgit2 0.27 transition
On May 25, 2018 11:21:59 AM GMT+05:30, Moritz Muehlenhoff wrote: >On Mon, May 21, 2018 at 10:46:48PM +0530, Pirate Praveen wrote: >It doesn't state that anywhere in the changelog, in fact it explicitly >mentions recent OpenSSL changes. mbedTLS support is not part of 0.27 release, but merged after 0.27 release, hence it is missing from changelog. The patch is taken directly from upstream. >Don't simply switch the TLS implementation to workaround a not fully >understood build failure :-/ > The current TLS implementation is Debian specific and it was rejected by upstream. Switching to upstream supported implementation is better in the long run. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#899036: libgit2 0.27 transition
On Mon, May 21, 2018 at 10:46:48PM +0530, Pirate Praveen wrote: > Control: clone -1 -2 > Control: reassign -2 libgit2-dev > Control: retitle -2 libgit2.pc requires openssl even though we use > mbedtls now > Control: found -2 0.27.0+dfsg.1-0.1 > > On Mon, 21 May 2018 22:33:43 +0530 Pirate Praveen > wrote: > > >The build failed, but it could be a bug in libgit2 itself as new > >version is supposed to be using mbedtls instead of openssl. It doesn't state that anywhere in the changelog, in fact it explicitly mentions recent OpenSSL changes. Don't simply switch the TLS implementation to workaround a not fully understood build failure :-/ Cheers, Moritz
Bug#899036: libgit2 0.27 transition
On Mon, 21 May 2018 22:46:48 +0530 Pirate Praveen wrote: cloning and assigning to libgit2. Now with libgit2 fixed, we are hitting another issue, because mbedTLS does not support pkg-config (https://github.com/ARMmbed/mbedtls/issues/228). Package mbedtls was not found in the pkg-config search path. Perhaps you should add the directory containing `mbedtls.pc' to the PKG_CONFIG_PATH environment variable Package 'mbedtls', required by 'libgit2', not found Discussion with libgit2 upstream here https://github.com/libgit2/libgit2/issues/4651
Bug#899036: libgit2 0.27 transition
Control: clone -1 -2 Control: reassign -2 libgit2-dev Control: retitle -2 libgit2.pc requires openssl even though we use mbedtls now Control: found -2 0.27.0+dfsg.1-0.1 On Mon, 21 May 2018 22:33:43 +0530 Pirate Praveen wrote: The build failed, but it could be a bug in libgit2 itself as new version is supposed to be using mbedtls instead of openssl. cloning and assigning to libgit2.
Bug#899036: libgit2 0.27 transition
On Fri, 18 May 2018 21:20:16 +0530 Pirate Praveen 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.
Bug#899036: libgit2 0.27 transition
Package: geany-plugins Version: 1.33+dfsg-1 Severity: important Dear Maintainer, 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. Thanks Praveen
