Control: tags -1 patch Hi,
Taking the approach of refreshing the test suite to match the output produced by the new libgit2 seems to do the job to address the test suite failure. I also checked this has no adverse effects on reverse dependencies. Variations between the reference and the new update are also minimal and seem to make sense. It would be welcome if someone else could have a look; maybe there are breakages I haven't seen. Also, upstream gave the impression that changes were maybe not that obvious, in which case it would be better to wait for an upcoming module version, compatible with the current libgit2 hopefully. In hope this helps, -- Étienne Mollier <emoll...@emlwks999.eu> Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/4, please excuse my verbosity.
Description: update test suite expectations to match libgit2 behavior. Author: Étienne Mollier <emoll...@debian.org> Bug: https://github.com/jacquesg/p5-Git-Raw/issues/222 Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009031 Last-Update: 2022-10-22 --- This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ --- libgit-raw-perl.orig/t/02-commit.t +++ libgit-raw-perl/t/02-commit.t @@ -296,7 +296,7 @@ $expected_patch = qq{ From $commit2_id Mon Sep 17 00:00:00 2001 From: Git::Raw author <git-xs\@example.com> -Subject: second commit +Subject: [1/2] second commit --- test2 | 1 + --- libgit-raw-perl.orig/t/15-merge.t +++ libgit-raw-perl/t/15-merge.t @@ -238,7 +238,7 @@ $index -> write; my $merge_msg = $repo -> message(); -is $merge_msg, "Merge branch 'branch2'\n\nConflicts:\n\ttest1\n"; +is $merge_msg, "Merge branch 'branch2'\n\n#Conflicts:\n#\ttest1\n"; my $target = $master -> target; $commit = $repo -> commit("Merge commit!", $me, $me, [$target, $commit2],
signature.asc
Description: PGP signature
