-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pkgcheck.base.PkgcheckException: pkgcheck scan: error: failed running git: fatal: ambiguous argument 'origin..HEAD': unknown revision or path not in the working tree. #107
Comments
First of all, I hope you feel better! Please give the output of Also, a good read is docs which explains some more things. Maybe you need to run |
I think that's already the case, as |
Can you check which is the upstream remote for master? It can follow another remote |
so I just noticed that the git command pkgdev constructs is
shouldn't it be
|
With such a variety of remotes, I wonder if the cache is getting corrupted in a way similar to pkgcore/pkgcheck#321 where multiple repos of the same name break the cache? |
Interesting, I seem to be hitting the same problem when pushing to ::musl (first time using
|
I had this issue as well. I used 'pkgcheck scan' and 'git push' instead. |
In my case
I only have one remote
Am checked out on master with one unpushed commit and unstaged changes.
|
This may be caused by the remote repository not setting the HEAD reference (i.e., the default branch). This seems to be true for https://github.com/gentoo/gentoo, as
where, for repositories that have a default branch set, it should look like
The GitHub documentation on how to set the default branch can be found at https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch |
Correction, everything seems right with github.com/gentoo/gentoo. I ran
appear. Now @ajakk Maybe this also solves it for you and ::musl? |
Tried my first
pkgdev push
and it failed withCurrently dealing with a cold, so I did not have the mental capacity to dig into this (but obviously I am fit enough to fill bug reports ;))
The text was updated successfully, but these errors were encountered: