Re: git: f819de75e10b - 2024Q4 - devel/git-filter-repo: Update to the latest development branch
- Reply: Cy Schubert : "Re: git: f819de75e10b - 2024Q4 - devel/git-filter-repo: Update to the latest development branch"
- In reply to: Cy Schubert : "git: f819de75e10b - 2024Q4 - devel/git-filter-repo: Update to the latest development branch"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 21 Oct 2024 22:45:30 UTC
On 2024-10-22T00:03:48.000+02:00, Cy Schubert <cy@FreeBSD.org> wrote: > The branch 2024Q4 has been updated by cy: > > URL: https://cgit.FreeBSD.org/ports/commit/?id=f819de75e10b663f628a6202649427869ae1b2ea > > commit f819de75e10b663f628a6202649427869ae1b2ea > > Author: Cy Schubert <cy@FreeBSD.org> > > AuthorDate: 2024-10-21 21:51:53 +0000 > > Commit: Cy Schubert <cy@FreeBSD.org> > > CommitDate: 2024-10-21 22:03:26 +0000 > > devel/git-filter-repo: Update to the latest development branch > > > > Point the upstream github hash that contains the 24+ commits that > > fix the data loss issue, making PORTREVISION=1 of this port the > > same as the -devel port. > > > > I don't normally like to have a GA port point to a devel branch but > > in this case backporting 24 commits leaves too much room for error. > > These changes will be removed when upstream releases a new version. > > > > Suggested by: diizzy > > MFH: 2024Q4 > > > > (cherry picked from commit 9cd03fae4c95c073f9b4a119ea37662db4355165) > > --- > > devel/git-filter-repo/Makefile | 2 ++ > > devel/git-filter-repo/distinfo | 6 +++--- > > 2 files changed, 5 insertions(+), 3 deletions(-) > > diff --git a/devel/git-filter-repo/Makefile b/devel/git-filter-repo/Makefile > > index 1ceb2eaee522..d8932bad06c1 100644 > > --- a/devel/git-filter-repo/Makefile > > +++ b/devel/git-filter-repo/Makefile > > @@ -1,6 +1,7 @@ > > PORTNAME= git-filter-repo > > DISTVERSIONPREFIX= v > > DISTVERSION= 2.45.0 > > +PORTREVISION= 1 > > CATEGORIES= devel > > > > MAINTAINER= cy@FreeBSD.org > > @@ -20,6 +21,7 @@ SHEBANG_FILES= git-filter-repo > > > > USE_GITHUB= yes > > GH_ACCOUNT= newren > > +GH_TAGNAME= a9093a6 > > Hi, This is incorrect approach, please follow "Example 18. Using USE_GITHUB to Access a Commit Between Two Versions" in Porters Handbook Best regards, Daniel