Hi, Unfortunately, it still failing. I'm trying to upload the patch file from https://issues.apache.org/jira/browse/RANGER-2317 . I've just found a recently filed bug for infra about similar issue: https://issues.apache.org/jira/browse/INFRA-17525 - it could be a general problem.
Regards, Zsombor On Wed, Jan 2, 2019 at 4:41 PM Ramesh Mani <[email protected]> wrote: > Zsombor, > > I was able to upload a test patch in review board now. > > Could you please check it again. > > Thanks, > Ramesh > > On 1/1/19, 2:49 AM, "Zs." <[email protected]> wrote: > > >Hi, > > > > Maybe the reviewboard is failing because of this change, I can't upload a > >review request, it throws an error: > >"fatal: git cat-file: could not get object info > >Line undefined: undefined" > > > >Is it just me, or a generic problem? > > > >Best regards, > > Zsombor > > > >On Tue, Jan 1, 2019 at 6:27 AM Don Bosco Durai <[email protected]> wrote: > > > >> Selva, thanks. > >> > >> Vel, do we need to do any changes on Jenkins or any other places? > >> > >> Thanks > >> > >> Bosco > >> > >> > >> On 12/28/18, 10:12 AM, "Selvamohan Neethiraj" <[email protected]> > >> wrote: > >> > >> All: > >> > >> I have created RANGER-2316 < > >> https://issues.apache.org/jira/browse/RANGER-2316> for updating repo > URL > >> in Quick Startup Guide and fixed it in the repo. > >> After update, I have followed the process mentioned in > >>docs/README.txt > >> to deploy the changes to documentation site, > >> http://ranger.apache.org/quick_start_guide.html > >> > >> > >> Thanks, > >> Selva- > >> > >> > On Dec 17, 2018, at 3:27 PM, Velmurugan Periasamy <[email protected] > > > >> wrote: > >> > > >> > Migration has been completed. > >> > > >> > New target URL(s): > >> > - https://gitbox.apache.org/repos/asf/ranger.git > >> > - https://github.com/apache/ranger > >> > > >> > > >> > > >> >> On Dec 17, 2018, at 2:47 PM, Velmurugan Periasamy > >><[email protected]> > >> wrote: > >> >> > >> >> Hello Rangers: > >> >> > >> >> Thank you for your responses. Since there is agreement in the dev > >> list (ref: > >> > >> > https://lists.apache.org/thread.html/fb07264b623c458389c8487e53d0a236341c > >>b733a2055e970e13e1e1@%3Cdev.ranger.apache.org%3E > >> < > >> > >> > https://lists.apache.org/thread.html/fb07264b623c458389c8487e53d0a236341c > >>b733a2055e970e13e1e1@%3Cdev.ranger.apache.org%3E>), > >> I will go ahead and open an Infra ticket to schedule the relocation of > >>git > >> repos. > >> >> > >> >> Thank you, > >> >> Vel > >> >> > >> >> ________________________________________ > >> >> From: Gautam Borad <[email protected] <mailto:[email protected] > >> > >> >> Sent: Wednesday, December 12, 2018 3:49 AM > >> >> To: [email protected] <mailto:[email protected]> > >> >> Subject: Re: Subject: [NOTICE] Mandatory relocation of Apache git > >> repositories on git-wip-us.apache.org <http://git-wip-us.apache.org/> > >> >> > >> >> +1 > >> >> > >> >> On Wed, Dec 12, 2018 at 2:45 AM Zs. <[email protected] <mailto: > >> [email protected]>> wrote: > >> >> > >> >>> +1 > >> >>> > >> >>> Regards, > >> >>> Zsombor > >> >>> > >> >>> On Tue, Dec 11, 2018 at 7:28 PM Sailaja Polavarapu < > >> >>> [email protected] > >><mailto:[email protected]>> > >> wrote: > >> >>> > >> >>>> +1 > >> >>>> > >> >>>> On 12/10/18, 1:22 PM, "Abhay Kulkarni" < > >> [email protected] <mailto:[email protected]>> > >> >>> wrote: > >> >>>> > >> >>>> +1 > >> >>>> > >> >>>> On 12/10/18, 12:06 PM, "Velmurugan Periasamy" > >><[email protected] > >> <mailto:[email protected]>> > >> >>> wrote: > >> >>>> > >> >>>>> Rangers: > >> >>>>> > >> >>>>> Please see below. I propose to move ranger repos over to > >>gitbox > >> >>> (from > >> >>>>> git-wip-us.apache.org <http://git-wip-us.apache.org/> < > >> http://git-wip-us.apache.org/ <http://git-wip-us.apache.org/>>) during > >>the > >> >>>> first > >> >>>>> phase (voluntary coordination). Please share your thoughts. > >> >>>>> > >> >>>>> Once there is agreement in dev list, I can open INFRA ticket > >>to > >> >>>> complete > >> >>>>> the move. Tentative target next week (week of Dec 17). > >> >>>>> > >> >>>>> Here¹s my +1. > >> >>>>> > >> >>>>> Thank you, > >> >>>>> Vel > >> >>>>> > >> >>>>> ________________________________________ > >> >>>>> From: Daniel Gruno <[email protected] <mailto: > >> [email protected]>> > >> >>>>> Sent: Friday, December 7, 2018 11:52 AM > >> >>>>> To: [email protected] <mailto:[email protected]> > >> >>>>> Subject: [NOTICE] Mandatory relocation of Apache git > >> repositories on > >> >>>>> git-wip-us.apache.org <http://git-wip-us.apache.org/> > >> >>>>> > >> >>>>> [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US > >> PLEASE > >> >>>>> DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE > >>PROJECTS] > >> >>>>> > >> >>>>> Hello Apache projects, > >> >>>>> > >> >>>>> I am writing to you because you may have git repositories on > >>the > >> >>>>> git-wip-us server, which is slated to be decommissioned in the > >> >>> coming > >> >>>>> months. All repositories will be moved to the new gitbox > >>service > >> >>> which > >> >>>>> includes direct write access on github as well as the standard > >> ASF > >> >>>>> commit access via gitbox.apache.org > >><http://gitbox.apache.org/>. > >> >>>>> > >> >>>>> ## Why this move? ## > >> >>>>> The move comes as a result of retiring the git-wip service, as > >> the > >> >>>>> hardware it runs on is longing for retirement. In lieu of > >>this, > >> we > >> >>>>> have decided to consolidate the two services (git-wip and > >> gitbox), > >> >>> to > >> >>>>> ease the management of our repository systems and future-proof > >> the > >> >>>>> underlying hardware. The move is fully automated, and ideally, > >> >>> nothing > >> >>>>> will change in your workflow other than added features and > >> access to > >> >>>>> GitHub. > >> >>>>> > >> >>>>> ## Timeframe for relocation ## > >> >>>>> Initially, we are asking that projects voluntarily request to > >> move > >> >>>>> their repositories to gitbox, hence this email. The voluntary > >> >>>>> timeframe is between now and January 9th 2019, during which > >> projects > >> >>>>> are free to either move over to gitbox or stay put on git-wip. > >> After > >> >>>>> this phase, we will be requiring the remaining projects to > >>move > >> >>> within > >> >>>>> one month, after which we will move the remaining projects > >>over. > >> >>>>> > >> >>>>> To have your project moved in this initial phase, you will > >>need: > >> >>>>> > >> >>>>> - Consensus in the project (documented via the mailing list) > >> >>>>> - File a JIRA ticket with INFRA to voluntarily move your > >>project > >> >>> repos > >> >>>>> over to gitbox (as stated, this is highly automated and will > >> take > >> >>>>> between a minute and an hour, depending on the size and > >>number > >> of > >> >>>>> your repositories) > >> >>>>> > >> >>>>> To sum up the preliminary timeline; > >> >>>>> > >> >>>>> - December 9th 2018 -> January 9th 2019: Voluntary > >>(coordinated) > >> >>>>> relocation > >> >>>>> - January 9th -> February 6th: Mandated (coordinated) > >>relocation > >> >>>>> - February 7th: All remaining repositories are mass migrated. > >> >>>>> > >> >>>>> This timeline may change to accommodate various scenarios. > >> >>>>> > >> >>>>> ## Using GitHub with ASF repositories ## > >> >>>>> When your project has moved, you are free to use either the > >>ASF > >> >>>>> repository system (gitbox.apache.org > >><http://gitbox.apache.org/>) > >> OR GitHub for your > >> >>> development > >> >>>>> and code pushes. To be able to use GitHub, please follow the > >> primer > >> >>>>> at: https://reference.apache.org/committer/github < > >> https://reference.apache.org/committer/github> > >> >>>>> > >> >>>>> > >> >>>>> We appreciate your understanding of this issue, and hope that > >> your > >> >>>>> project can coordinate voluntarily moving your repositories > >>in a > >> >>>>> timely manner. > >> >>>>> > >> >>>>> All settings, such as commit mail targets, issue linking, PR > >> >>>>> notification schemes etc will automatically be migrated to > >> gitbox as > >> >>>>> well. > >> >>>>> > >> >>>>> With regards, Daniel on behalf of ASF Infra. > >> >>>>> > >> >>>>> PS:For inquiries, please reply to [email protected] > >> <mailto:[email protected]>, not your > >> >>>>> project's dev list :-). > >> >>>>> > >> >>>>> > >> >>>> > >> >>>> > >> >>>> > >> >>>> > >> >>> > >> >> > >> > > >> > >> > >> > >> > >> > >
