You are not logged in.
I wrongly pushed v1.0.2 _without_ .SRCINFO
Result: v1.0.2 is in AUR git repository _without_ .SRCINFO (not publically available), v1.0.1 is publically available, and I can't push a corrected v1.0.2
I tried "git rebase -i --root" + edit last commit ("git add .SRCINFO") + "git commit --amend"
The local repositoy looks fine, but I can't push the corrected v1.0.2 to AUR.
I have tried "git push" and "git push --force", but both commands are rejected by AUR.
Now I'm stuck, and need help (sorry, I'm no git pro)
How do I correct my mistake, so I can publish v1.0.2 for people to use, and become allowed to push further updates?
Cheers, Johnny ![]()
Last edited by johnnyn (2015-10-26 16:35:07)
Offline
Just add the .SRCINFO and push it as a new commit.
Offline
Thanks Scimmia ![]()
It solved my problem.
But before I mark it as solved, I need to ask what is meant by this, on the wiki:
https://wiki.archlinux.org/index.php/Ar … g_packages
Tip: If you forget to commit the .SRCINFO and add it in a later commit, the AUR will still reject your pushes because the .SRCINFO must exist for every commit. To solve this problem you can use git rebase with the --root option or git filter-branch with the --tree-filter option.
Cheers, Johnny ![]()
Last edited by johnnyn (2015-10-26 16:35:45)
Offline
It's talking about commits that don't have a .SRCINFO at all, not ones that are just outdated. If the first commit (for first X commits) doesn't include a .SRCINFO file, push will fail and you can edit the history. After a commit has been pushed, even with an old .SRCINFO, it cannot be edited.
Last edited by Scimmia (2015-10-26 16:03:33)
Offline
I see. So if any commit in the local commit history lacks a ref to a .SRCINFO blob, AUR will reject the push.
I think I understand now ![]()
Thanks for explaining, and thanks for helping me with my problem, Scimmia ![]()
Cheers, Johnny ![]()
Last edited by johnnyn (2015-10-26 16:36:14)
Offline