Package: aur.archlinux.org/libcs50
» git push Enter passphrase for key '/home/krakn/.ssh/id_rsa': git-receive-pack: permission denied: krakn fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
Remotes are as follows (I am able to clone the repository):
» git remote -v origin ssh://aur@aur.archlinux.org/libcs50 (fetch) origin ssh://aur@aur.archlinux.org/libcs50 (push)
I have no problems pushing to my other repositories. Is there something on the backend that might be preventing the push?
Thanks!
Le 04/04/2017 à 18:43, Dan B via aur-general a écrit :
Package: aur.archlinux.org/libcs50
» git push Enter passphrase for key '/home/krakn/.ssh/id_rsa': git-receive-pack: permission denied: krakn fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
Remotes are as follows (I am able to clone the repository):
» git remote -v origin ssh://aur@aur.archlinux.org/libcs50 (fetch) origin ssh://aur@aur.archlinux.org/libcs50 (push)
I have no problems pushing to my other repositories. Is there something on the backend that might be preventing the push?
Thanks!
This is strange… Are you on the same network than the one you’ve used some minutes ago for pushing the -git package? I expect so, but you never know…
Else I think you will have to wait for Lukas to step in if a retry doesn’t make it work.
BTW, the || exit 1 in your PKGBUILD should be removed. And the "${srcdir}" (and thus the quotes) are not necessary in your cd commands (cd ${gitname} will do).
Finally, the rsync command should not be here. Either use cp/install, or a make install target if there is one.
Regards, Bruno
On Wed, 05 Apr 2017 at 03:43:11, Dan B via aur-general wrote:
Package: aur.archlinux.org/libcs50
» git push Enter passphrase for key '/home/krakn/.ssh/id_rsa': git-receive-pack: permission denied: krakn fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
Remotes are as follows (I am able to clone the repository):
» git remote -v origin ssh://aur@aur.archlinux.org/libcs50 (fetch) origin ssh://aur@aur.archlinux.org/libcs50 (push)
I have no problems pushing to my other repositories. Is there something on the backend that might be preventing the push?
Well, the Git repository and the package base already exist [1, 2] and are maintained by somebody else. It is kind of strange that there is no package assigned to that package base, though (.SRCINFO does not contain a pkgname entry).
[1] https://aur.archlinux.org/cgit/aur.git/?h=libcs50 [2] https://aur.archlinux.org/pkgbase/libcs50
Le 04/04/2017 à 21:13, Lukas Fleischer a écrit :
On Wed, 05 Apr 2017 at 03:43:11, Dan B via aur-general wrote:
Package: aur.archlinux.org/libcs50
» git push Enter passphrase for key '/home/krakn/.ssh/id_rsa': git-receive-pack: permission denied: krakn fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
Remotes are as follows (I am able to clone the repository):
» git remote -v origin ssh://aur@aur.archlinux.org/libcs50 (fetch) origin ssh://aur@aur.archlinux.org/libcs50 (push)
I have no problems pushing to my other repositories. Is there something on the backend that might be preventing the push?
Well, the Git repository and the package base already exist [1, 2] and are maintained by somebody else. It is kind of strange that there is no package assigned to that package base, though (.SRCINFO does not contain a pkgname entry).
[1] https://aur.archlinux.org/cgit/aur.git/?h=libcs50 [2] https://aur.archlinux.org/pkgbase/libcs50
Hum… Didn’t think about searching for the $pkgbase. This kind of things should not happen, right? Maybe the git interface should check the presence of a pkgname in .SRCINFO (as well as mismatches with the PKGBUILD for all sorts of things)?
This would block such commits: https://aur.archlinux.org/cgit/aur.git/commit/?h=libcs50&id=57fe3f6e5de6...
Bruno
On Wed, 05 Apr 2017 at 08:01:19, Bruno Pagani via aur-general wrote:
Hum… Didn’t think about searching for the $pkgbase. This kind of things should not happen, right? Maybe the git interface should check the presence of a pkgname in .SRCINFO (as well as mismatches with the PKGBUILD for all sorts of things)?
We cannot parse PKGBUILD files, so we cannot ensure that the .SRCINFO meta data matches the PKGBUILD (not being able to parse PKGBUILD files was the reason .SRCINFO was introduced in the first place).
Checking for at least one package in the update hook sounds like a good idea to me. I will look into it, thanks!
This would block such commits: https://aur.archlinux.org/cgit/aur.git/commit/?h=libcs50&id=57fe3f6e5de6...
Bruno
aur-general@lists.archlinux.org