From: "Michal Suchánek" <msuchanek@suse.de>
To: git@vger.kernel.org
Subject: Re: pygit2 claims repository does not exist on GIT_DIR_INVALID_OWNERSHIP
Date: Thu, 19 Oct 2023 14:07:28 +0200 [thread overview]
Message-ID: <20231019120728.GV6241@kitsune.suse.cz> (raw)
In-Reply-To: <20231019093344.GS6241@kitsune.suse.cz>
On Thu, Oct 19, 2023 at 11:33:44AM +0200, Michal Suchánek wrote:
> Hello,
>
> after upgrade from git 2.26 to git 2.35 pygit would claim that my
> repository does not exist:
>
> :~> git ls-remote /srv/git/kernel-source.git | head -n3
> 41037b9c54949ab7df9d32e8bc753c059b27c66c HEAD
> 7a68c4c0c640ac07b89722271f866287b9047459 refs/heads/ALP-current
> 4993d1b0a96a0fa7fb0e87d3b1725bc775162283 refs/heads/ALP-current-RT
> :~> python3
> Python 3.6.15 (default, Sep 23 2021, 15:41:43) [GCC] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import pygit2
> >>> pygit2.Repository("/srv/git/kernel-source.git")
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> File "/usr/lib64/python3.6/site-packages/pygit2/repository.py", line 1498, in __init__
> path_backend = init_file_backend(path, flags)
> _pygit2.GitError: Repository not found at /srv/git/kernel-source.git
> >>>
>
> Could a reasonable diagnostic be provided?
It turns out that I have relatively recent python3-pygit2 but it's
linked against ancient libgit2 causing this error.
Rebuilding python3-pygit2 fixes the problem.
Sorry about the noise.
Thanks
Michal
prev parent reply other threads:[~2023-10-19 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 9:33 pygit2 claims repository does not exist on GIT_DIR_INVALID_OWNERSHIP Michal Suchánek
2023-10-19 10:10 ` Konstantin Khomoutov
2023-10-19 12:07 ` Michal Suchánek [this message]
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=20231019120728.GV6241@kitsune.suse.cz \
--to=msuchanek@suse.de \
--cc=git@vger.kernel.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