Update gssproxy.git with issue :77/156 Update gssproxy.git with issue :78/156 Update gssproxy.git with issue :79/156 Traceback (most recent call last): File "/home/bos/rharwood/.venv/bin/pgimport", line 11, in <module> sys.exit(app()) File "/home/bos/rharwood/.venv/local/lib/python2.7/site-packages/click/core.py", line 716, in __call__ return self.main(*args, **kwargs) File "/home/bos/rharwood/.venv/local/lib/python2.7/site-packages/click/core.py", line 696, in main rv = self.invoke(ctx) File "/home/bos/rharwood/.venv/local/lib/python2.7/site-packages/click/core.py", line 1060, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/home/bos/rharwood/.venv/local/lib/python2.7/site-packages/click/core.py", line 889, in invoke return ctx.invoke(self.callback, **ctx.params) File "/home/bos/rharwood/.venv/local/lib/python2.7/site-packages/click/core.py", line 534, in invoke return callback(*args, **kwargs) File "/home/bos/rharwood/.venv/local/lib/python2.7/site-packages/pagure_importer/commands/fedorahosted.py", line 29, in fedorahosted tags=tags) File "/home/bos/rharwood/.venv/local/lib/python2.7/site-packages/pagure_importer/utils/importer_trac.py", line 33, in import_issues update_git(pagure_issue, repo_name, repo_folder) File "/home/bos/rharwood/.venv/local/lib/python2.7/site-packages/pagure_importer/utils/git.py", line 28, in update_git new_repo = pygit2.clone_repository(repopath, newpath) File "/home/bos/rharwood/.venv/local/lib/python2.7/site-packages/pygit2/__init__.py", line 255, in clone_repository check_error(err) File "/home/bos/rharwood/.venv/local/lib/python2.7/site-packages/pygit2/errors.py", line 64, in check_error raise GitError(message) _pygit2.GitError: Could not open '/tmp/pagure-RqEIam/56a673bdbe9c4696a488c8aa633773f6' for writing: Too many open files fatal: This operation must be run in a work tree
@rharwood this shouldn't the problem with the latest version - 1.2.0 . Are you sure you are using the latest one? If you used pip then it would have been 1.1.0, i just now updated it with the latest one.
pip
vivekanand1101 wrote:
@rharwood this shouldn't the problem with the latest version - 1.2.0 . A= re you sure you are using the latest one? If you used ```pip``` then it wou= ld have been 1.1.0, i just now updated it with the latest one.=20
I used pip. With 1.2.0, this does succeed.
However! After I pgimport push, there are no tickets in the repository. I'm testing with gssproxy: you can see this here https://stg.pagure.io/gssproxy/issues
pgimport push
Additionally, git seems to be really unhappy about the state of the tree:
$ git status fatal: This operation must be run in a work tree $ git branch * master $ git log HEAD~1.. commit 5899dc6609faac12809b6196d4321b4ea446aabc Author: pagure <pagure> Date: Wed Sep 7 16:22:14 2016 -0400 Updated issue 70b8e74a908648db98f6f4e1556e14cb: GSS-Proxy s4u permissions $ =20=20=20=20
did you enable Pagure Tickets hook from your pagure projects' settings page before pushing?
Pagure Tickets
pagure@pagure.io writes:
vivekanand1101 added a new comment to an issue you are following: did you enable ```Pagure Tickets``` hook from your pagure projects' settings page before pushing?
did you enable ```Pagure Tickets``` hook from your pagure projects' settings page before pushing?
As it happens I did not. However, there was no warning or anything on the push command (there needs to be), and when I try to push now, nothing happens (so I can't fix it without starting over).
Deleting the project and starting over causes it to work.
@rharwood this was there in the overview page in How to run section. With #39 i have included this just above the pgimport push command as well. This should be good enough.
How to run
@vivekanand1101 changed the status to Fixed
Fixed
Login to comment on this ticket.