Hi Gregor, I just triggered the git sync from the selfservice[1] . Can you check if the issue is still there?
If the issue is still there you may need ping for infra team by sending the email to us...@infra.apache.org If you cannot get the response in few hours, you may use the Hipchat[2] to find the support from infra through the chat. [1]https://selfserve.apache.org [2]http://infra.chat/ Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Jul 9, 2018 at 3:58 AM, Gregor Zurowski <gre...@list.zurowski.org> wrote: > Hi, > > Unfortunately I was not able to cut the release due to the following > problems with the Git repository when trying to push changes: > > remote: This repository has been locked due to synchronization issues: > remote: - /x1/gitbox/broken/camel.txt exists due to a previous error, > and prevents pushes. > remote: This could either be a benign issue, or the repositories could > be out of sync. > remote: Please contact us...@infra.apache.org to have infrastructure > resolve the issue. > remote: > To https://gitbox.apache.org/repos/asf/camel.git > ! [remote rejected] release/2.21.2 -> release/2.21.2 (pre-receive > hook declined) > error: failed to push some refs to > 'https://gitbox.apache.org/repos/asf/camel.git' > > Did anybody experience this in the past? > > Thanks in advance, > Gregor > > > On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski > <gre...@list.zurowski.org> wrote: > > Sure, I can take care of the release this weekend. > > > > Thanks, > > Gregor > > > > > > On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <claus.ib...@gmail.com> > wrote: > >> Hi > >> > >> After the Camel 2.22.0 release, then I think we should work on getting > >> a new patch release out of the 2.21.x branch, eg 2.21.2. There are 38 > >> JIRAs fixed for this version and we will get a couple of more which > >> are pending to be backported. > >> > >> > >> > >> -- > >> Claus Ibsen > >> ----------------- > >> http://davsclaus.com @davsclaus > >> Camel in Action 2: https://www.manning.com/ibsen2 >
