I just created https://pagure.io/dotnet-sig/dotnet9.0. I tried pushing my existing set of commits to it, and got this error:
$ git push -u dotnet-sig main Enumerating objects: 569, done. Counting objects: 100% (569/569), done. Delta compression using up to 20 threads Compressing objects: 100% (249/249), done. Writing objects: 100% (569/569), 300.39 KiB | 42.91 MiB/s, done. Total 569 (delta 307), reused 559 (delta 303), pack-reused 0 (from 0) remote: Resolving deltas: 100% (307/307), done. remote: Has commit access: True remote: Has commit access: True remote: ERROR: ['git', 'rev-list', 'd6645fff9ea88dced36d0dbbf906af5c273ea9c0', '^HEAD'] =-- 128 remote: remote: fatal: bad revision '^HEAD' remote: remote: Sending to redis to send commit notification emails To ssh://pagure.io/dotnet-sig/dotnet9.0.git * [new branch] main -> main branch 'main' set up to track 'dotnet-sig/main'.
And nothing would show up at https://pagure.io/dotnet-sig/dotnet9.0.
So I deleted the project, and re-created it. This time, pushing the initial set of commits leads to:
$ git push -u origin main Enumerating objects: 569, done. Counting objects: 100% (569/569), done. Delta compression using up to 20 threads Compressing objects: 100% (249/249), done. Writing objects: 100% (569/569), 300.39 KiB | 37.55 MiB/s, done. Total 569 (delta 307), reused 559 (delta 303), pack-reused 0 (from 0) remote: Resolving deltas: 100% (307/307), done. remote: Has commit access: True remote: Has commit access: True remote: Sending to redis to log activity and send commit notification emails remote: ERROR: ['git', 'diff', '--name-status', '-z', '^0000000000000000000000000000000000000000', 'd39668a409bd4abf8206b93d8173f0f2584ed887'] =-- 128 remote: remote: fatal: bad object 0000000000000000000000000000000000000000 remote: remote: * Publishing information for 113 commits To ssh://pagure.io/dotnet-sig/dotnet9.0.git * [new branch] main -> main branch 'main' set up to track 'origin/main'.
Though the repo seems to be publicly visible on https://pagure.io/dotnet-sig/dotnet9.0 with history and contents. Is the latest error message safe to ignore?
Fixed by https://pagure.io/pagure/pull-request/5459
Metadata Update from @wombelix: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)