Learn more about these different git repos.
Other Git URLs
I've been seeing these on pushes the last couple days
remote: /usr/lib64/python2.7/site-packages/cffi/model.py:526: UserWarning: 'git_checkout_notify_t' has no values explicitly defined; next version will refuse to guess which integer type it is meant to be (unsigned/signed, int/long) remote: % self._get_c_name()) remote: /usr/lib64/python2.7/site-packages/cffi/model.py:526: UserWarning: 'git_merge_tree_flag_t' has no values explicitly defined; next version will refuse to guess which integer type it is meant to be (unsigned/signed, int/long) remote: % self._get_c_name())
These are annoying but safe to ignore for now. They are due to the mess we have between libgit2/pygit2 and libffi in epel :(
Just observed this with https://pagure.io/linux-cluster/foghorn:
$ git push --mirror pg [...] remote: /usr/lib64/python2.7/site-packages/cffi/model.py:526: UserWarning: 'git_checkout_notify_t' has no values explicitly defined; next version will refuse to guess which integer type it is meant to be (unsigned/signed, int/long) remote: % self._get_c_name()) remote: /usr/lib64/python2.7/site-packages/cffi/model.py:526: UserWarning: 'git_merge_tree_flag_t' has no values explicitly defined; next version will refuse to guess which integer type it is meant to be (unsigned/signed, int/long) remote: % self._get_c_name()) remote: Sending to redis to log activity To ssh://git@pagure.io/linux-cluster/foghorn.git * [new branch] master -> master * [new branch] origin/HEAD -> origin/HEAD * [new branch] origin/master -> origin/master * [new tag] v0.1.2 -> v0.1.2 * [new tag] v0.1.3 -> v0.1.3 * [new tag] v0.1.4 -> v0.1.4 * [new tag] v0.1.5 -> v0.1.5 * [new tag] v0.1.6 -> v0.1.
I believe this is fixed now :)
Metadata Update from @pingou: - Issue close_status updated to: Fixed
Login to comment on this ticket.