From: Arthur Zamarin <arthurzam@gentoo.org>
To: gentoo-dev@lists.gentoo.org,
Andrey Grozin <grozin@woodpecker.gentoo.org>
Subject: Re: [gentoo-dev] pkgcheck scan: error: failed running git log: fatal: unrecognized argument: --no-find-copies
Date: Fri, 16 Feb 2024 18:53:24 +0200 [thread overview]
Message-ID: <b8f20f71-6a92-464f-a207-e78cbc8f723e@gentoo.org> (raw)
In-Reply-To: <e5e1bc6d-f8df-1206-2bc5-9e85bbe2194a@woodpecker.gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 937 bytes --]
On 16/02/2024 18.51, Andrey Grozin wrote:
> I'm trying to bump master-pdf-editor and get
>
> grozin@bilbo /home/gentoo/app-text/master-pdf-editor $ pkgcheck scan
> pkgcheck scan: error: failed running git log: fatal: unrecognized
> argument: --no-find-copies
> grozin@bilbo /home/gentoo/app-text/master-pdf-editor $ pkgdev commit -m
> 'bump to 5.9.82'
> pkgdev commit: error: failed running git log: fatal: unrecognized
> argument: --no-find-copies
> grozin@bilbo /home/gentoo/app-text/master-pdf-editor $
>
> What has happened with pkgcheck scan?
>
> Andrey
>
Happened with today's bump to dev-vcs/git [1]. Please downgrade git
until I fix pkgcheck (currently v2.43.2 got masked [2] cause of this
reason).
[1] https://bugs.gentoo.org/924718
[2] https://packages.gentoo.org/packages/dev-vcs/git
--
Arthur Zamarin
arthurzam@gentoo.org
Gentoo Linux developer (Python, pkgcore stack, Arch Teams, GURU)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-02-16 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 16:51 [gentoo-dev] pkgcheck scan: error: failed running git log: fatal: unrecognized argument: --no-find-copies Andrey Grozin
2024-02-16 16:53 ` Arthur Zamarin [this message]
2024-02-16 17:00 ` Michał Górny
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=b8f20f71-6a92-464f-a207-e78cbc8f723e@gentoo.org \
--to=arthurzam@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=grozin@woodpecker.gentoo.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