Was just testing an import into stg.pagure.io (currently running 2.7), and got the following back from the hook when trying to push.
Presumably this is something todo with the new statuses in pagure 2.7 that arent in the stable 2.6 release.
remote: Files changed by new commits: remote: remote: repo: fedocal None None remote: To load: 8826b27fcd574f19af545c00822e08fc remote: To load: 614c0b78a3e64d9aa399bc7fcc202798 remote: Traceback (most recent call last): remote: File "./hooks/post-receive.pagure-ticket", line 105, in <module> remote: main(sys.argv[1:]) remote: File "./hooks/post-receive.pagure-ticket", line 101, in main remote: run_as_post_receive_hook() remote: File "./hooks/post-receive.pagure-ticket", line 97, in run_as_post_receive_hook remote: json_data=json_data) remote: File "/usr/lib/python2.7/site-packages/pagure/lib/git.py", line 454, in update_ticket_from_git remote: notify=False, remote: File "/usr/lib/python2.7/site-packages/pagure/lib/__init__.py", line 1198, in new_issue remote: session.flush() remote: File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/scoping.py", line 150, in do remote: return getattr(self.registry(), name)(*args, **kwargs) remote: File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/session.py", line 1919, in flush remote: self._flush(objects) remote: File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/session.py", line 2037, in _flush remote: transaction.rollback(_capture_exception=True) remote: File "/usr/lib64/python2.7/site-packages/sqlalchemy/util/langhelpers.py", line 60, in __exit__ remote: compat.reraise(exc_type, exc_value, exc_tb) remote: File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/session.py", line 2001, in _flush remote: flush_context.execute() remote: File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/unitofwork.py", line 372, in execute remote: rec.execute(self) remote: File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/unitofwork.py", line 526, in execute remote: uow remote: File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/persistence.py", line 65, in save_obj remote: mapper, table, insert) remote: File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/persistence.py", line 570, in _emit_insert_statements remote: execute(statement, multiparams) remote: File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 729, in execute remote: return meth(self, multiparams, params) remote: File "/usr/lib64/python2.7/site-packages/sqlalchemy/sql/elements.py", line 322, in _execute_on_connection remote: return connection._execute_clauseelement(self, multiparams, params) remote: File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 826, in _execute_clauseelement remote: compiled_sql, distilled_params remote: File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 958, in _execute_context remote: context) remote: File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1159, in _handle_dbapi_exception remote: exc_info remote: File "/usr/lib64/python2.7/site-packages/sqlalchemy/util/compat.py", line 199, in raise_from_cause remote: reraise(type(exception), exception, tb=exc_tb) remote: File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 951, in _execute_context remote: context) remote: File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py", line 436, in do_execute remote: cursor.execute(statement, parameters) remote: sqlalchemy.exc.IntegrityError: (IntegrityError) insert or update on table "issues" violates foreign key constraint "issues_status_fkey" remote: DETAIL: Key (status)=(Fixed) is not present in table "status_issue". remote: 'INSERT INTO issues (id, uid, project_id, title, content, user_id, assignee_id, status, private, priority, milestone, close_status, date_created, closed_at) VALUES (%(id)s, %(uid)s, %(project_id)s, %(title)s, %(content)s, %(user_id)s, %(assignee_id)s, %(status)s, %(private)s, %(priority)s, %(milestone)s, %(close_status)s, %(date_created)s, %(closed_at)s)' {'status': u'Fixed', 'content': u'If no group is specified as manager for a calendar, then everyone CLA+1 can add meetings.\r\n\r\nThis is currently broken and should be fixed for the release of 0.2.0', 'user_id': 2, 'uid': '614c0b78a3e64d9aa399bc7fcc202798', 'title': u'Fix add meeting when calendar allows CLA+1', 'private': False, 'id': 46, 'priority': None, 'assignee_id': None, 'milestone': None, 'date_created': datetime.datetime(2013, 8, 4, 22, 14, 10), 'project_id': 146, 'closed_at': None, 'close_status': None} remote: Hook ./hooks/post-receive.pagure-ticket failed with error code 1 To ssh://git@stg.pagure.io/tickets/fedocal.git
This should be fixed by #51
@cverna changed the status to Closed
Closed