Github messages for voidlinux
 help / color / mirror / Atom feed
From: ram02z <ram02z@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] git-filter-repo: update to 2.33.0.
Date: Fri, 03 Sep 2021 18:53:12 +0200	[thread overview]
Message-ID: <20210903165312.egVwmTt1tFOrA1o5ypuWEygX7OlcFbPnhU48M-Pi17g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32818@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1505 bytes --]

There is an updated pull request by ram02z against master on the void-packages repository

https://github.com/ram02z/void-packages git_filter_repo
https://github.com/void-linux/void-packages/pull/32818

git-filter-repo: update to 2.33.0.
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->

#### Does it build and run successfully? 
- [x] I built this PR locally for my native architecture, (x86_64-musl)
<!--
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/32818.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-git_filter_repo-32818.patch --]
[-- Type: text/x-diff, Size: 1318 bytes --]

From ffdcbb9e455df1e9fc961c439596c6ad4497433b Mon Sep 17 00:00:00 2001
From: Omar Zeghouani <omarzeghouanii@gmail.com>
Date: Fri, 3 Sep 2021 15:05:18 +0100
Subject: [PATCH] git-filter-repo: update to 2.33.0.

---
 srcpkgs/git-filter-repo/template | 13 ++++---------
 1 file changed, 4 insertions(+), 9 deletions(-)

diff --git a/srcpkgs/git-filter-repo/template b/srcpkgs/git-filter-repo/template
index cc609004ea76..7755fee8bb20 100644
--- a/srcpkgs/git-filter-repo/template
+++ b/srcpkgs/git-filter-repo/template
@@ -1,7 +1,7 @@
 # Template file for 'git-filter-repo'
 pkgname=git-filter-repo
-version=2.27.0
-revision=2
+version=2.33.0
+revision=1
 depends="git python3"
 checkdepends="git python3 perl rsync dos2unix"
 short_desc="Versatile tool for rewriting git history"
@@ -9,15 +9,10 @@ maintainer="Cameron Nemo <cnemo@tutanota.com>"
 license="MIT"
 homepage="https://github.com/newren/git-filter-repo/"
 distfiles="https://github.com/newren/git-filter-repo/releases/download/v${version}/git-filter-repo-${version}.tar.xz"
-checksum=41edbb53eb83fce292eb28f044002dc772849ce72053c74715e882c8f1053eef
+checksum=7bcf11da134bbd82a4171f7fb28a3ab7bc4d478fe8ec3a3d9580e4bbdc32e6e9
 
 do_check() {
-	cd t
-	for f in ./t[0-9][0-9][0-9][0-9]-*.sh
-	do
-		echo "Running $f"
-		$f
-	done
+	t/run_tests
 }
 
 do_install() {

  parent reply	other threads:[~2021-09-03 16:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 14:13 [PR PATCH] " ram02z
2021-09-03 15:54 ` [PR REVIEW] " paper42
2021-09-03 16:53 ` ram02z [this message]
2021-09-03 17:33 ` ericonr
2021-09-04  1:54 ` CameronNemo
2021-09-05 10:26 ` [PR PATCH] [Merged]: " paper42

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210903165312.egVwmTt1tFOrA1o5ypuWEygX7OlcFbPnhU48M-Pi17g@z \
    --to=ram02z@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).