Bug#899035: libgit2 0.27 transition

[Pirate Praveen]

On Thu, 24 May 2018 22:51:13 +0530 Pirate Praveen  
wrote:
gitg (and geany-plugins) is failing to build because mbedtls does not 
provide a pkg-config file (#900015). libgit2 now supports mbedTLS 
backend as alternative to building against openssl. Earlier versions of 
libgit2 were using a debian specific patch to use curl with gnutls 
instead, but upstream does not want to use curl and prefers mbedTLS.





geany-plugins build passed after fixing libgit2.pc but gitg tests failed.

make  check-TESTS
make[3]: Entering directory '/<>'
make[4]: Entering directory '/<>'
./build-aux/test-driver: line 107: 25990 Segmentation fault  "$@" > 
$log_file 2>&1

FAIL: tests/libgitg/test-libgitg
PASS: tests/gitg/test-gitg
===
   gitg 3.26.0: ./test-suite.log
===

# TOTAL: 2
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: tests/libgitg/test-libgitg



(process:25990): Gtk-CRITICAL **: 12:17:35.131: 
gtk_style_context_add_provider_for_screen: assertion 'GDK_IS_SCREEN 
(screen)' failed

/LibGitgTestStage/file-status: OK
/LibGitgTestStage/stage: OK
/LibGitgTestStage/unstage: OK
/LibGitgTestStage/revert: OK
/LibGitgTestStage/delete: OK
/LibGitgTestDate/iso8601: OK
/LibGitgTestDate/rfc2822: OK
/LibGitgTestDate/internal: OK
/LibGitgTestCommit/commit: FAIL tests/libgitg/test-libgitg (exit status: 
139)



Testsuite summary for gitg 3.26.0

# TOTAL: 2
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to https://bugzilla.gnome.org/enter_bug.cgi?product=gitg

make[4]: *** [Makefile:5891: test-suite.log] Error 1
make[4]: Leaving directory '/<>'
make[3]: *** [Makefile:5999: check-TESTS] Error 2
make[3]: Leaving directory '/<>'
make[2]: *** [Makefile:6236: check-am] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:5776: check-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:7: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit 
status 2


Build finished at 2018-05-26T12:17:35Z

Bug#899035: libgit2 0.27 transition

[Pirate Praveen]

On Sat, 19 May 2018 10:37:53 +0530 Pirate Praveen 
 wrote:

On May 18, 2018 11:50:35 PM GMT+05:30, Simon McVittie  wrote:



>Have you tried building reverse-dependencies like gitg against the
>new libgit2?

I wanted to give a heads up earlier. I will rebuild all the reversed 
dependencies now.


I have started rebuilding reverse dependencies and closed bugs of those 
who succeeded to build against the new version (birdfont, callingra, 
fritzing, gall, gnuastro).


gitg (and geany-plugins) is failing to build because mbedtls does not 
provide a pkg-config file (#900015). libgit2 now supports mbedTLS 
backend as alternative to building against openssl. Earlier versions of 
libgit2 were using a debian specific patch to use curl with gnutls 
instead, but upstream does not want to use curl and prefers mbedTLS.

Bug#899035: libgit2 0.27 transition

[Pirate Praveen]

On May 18, 2018 11:50:35 PM GMT+05:30, Simon McVittie  wrote:
>On Fri, 18 May 2018 at 21:18:49 +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.
>
>Have you tried building reverse-dependencies like gitg against the
>new libgit2?

I wanted to give a heads up earlier. I will rebuild all the reversed 
dependencies now.

>How extensive are the API/ABI breaks in the new version of libgit2?

My main motivation was to get ruby-rugged 0.27 which required newer libgit2.

Only new symbols are added.

https://anonscm.debian.org/cgit/collab-maint/libgit2.git/commit/?id=814217455e3d06c9d7062e39f70352e96b595e64

>> The severity of this report will be raised to serious once
>> libgit2 0.27 is uploaded to unstable.
>
>This is not how transitions work. "This package is involved in
>a transition" is not a release-critical bug: packages affected by
>transitions are normally rebuilt by binNMUs scheduled by the release
>team, which cannot usefully close bugs. You should only open or
>escalate
>release-critical bugs if something is known to be wrong, such as gitg
>failing to build from source against the new version of libgit2.

This is first transition for me so I'm sure I missed some bits. That is also 
the reason to file bugs at this stage so people involved are aware.

>The release team are unlikely to give you a transition slot for
>uploading
>the new libgit version to unstable until/unless you can estimate how
>much
>breakage it will cause and how much effort is involved in fixing it.

Thanks for the tips, I will rebuild all reverse deps and escalate or close the 
bugs as required.

>Thanks,
>smcv

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#899035: libgit2 0.27 transition

[Simon McVittie]

On Fri, 18 May 2018 at 21:18:49 +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.

Have you tried building reverse-dependencies like gitg against the
new libgit2?

How extensive are the API/ABI breaks in the new version of libgit2?

> The severity of this report will be raised to serious once
> libgit2 0.27 is uploaded to unstable.

This is not how transitions work. "This package is involved in
a transition" is not a release-critical bug: packages affected by
transitions are normally rebuilt by binNMUs scheduled by the release
team, which cannot usefully close bugs. You should only open or escalate
release-critical bugs if something is known to be wrong, such as gitg
failing to build from source against the new version of libgit2.

The release team are unlikely to give you a transition slot for uploading
the new libgit version to unstable until/unless you can estimate how much
breakage it will cause and how much effort is involved in fixing it.

Thanks,
smcv

Bug#899035: libgit2 0.27 transition

[Pirate Praveen]

Package: gitg
Version: 3.26.0-5
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