Unfortunately I got the same result as OM :( Something is really wrong with
Maven central, cause I can't believe that we all have bad internet
connection. :)

https://paste.apache.org/eqN9

Piotr

pt., 12 paź 2018 o 19:14 Piotr Zarzycki <piotrzarzyck...@gmail.com>
napisał(a):

> The weirdest thing is that I cannot use anymore sourcetree after that
> update. I'm getting wrong password and user name on other repositories
> which are private.
>
> git version 2.19.1.windows.1
>
> However after update I was able to continue process of release. Update
> fixes for me some problems with gpg.
>
> Piotr
>
> pt., 12 paź 2018 o 18:47 Alex Harui <aha...@adobe.com.invalid> napisał(a):
>
>> I was able to delete the tag.  What version of Git are you using?  I'm
>> concerned other problems may arise.
>>
>> If you run into a problem like this again, you might want to try just
>> giving up on rc1 and calling it rc2 so the tag names don't conflict.
>>
>> HTH,
>> -Alex
>>
>> On 10/12/18, 9:42 AM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com>
>> wrote:
>>
>>     I would like to ask also someone for delete
>>     tag org.apache.royale.compiler-0.9.4-rc1 - I'm not sure what has
>> happened
>>     but after updating git I cannot do that. I can commit stuff, but doing
>>     delete tag I'm getting
>>
>>     remote: Permission to apache/royale-compiler.git denied to
>> piotrzarzycki21.
>>     fatal: unable to access '
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-compiler.git%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C07dbe5901e2d4ce7029e08d63061b209%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636749593496378092&amp;sdata=CXp64oo2O8qMuwV%2BXE14krbu71gQ7sWa1fIbuscajMA%3D&amp;reserved=0
>> ':
>>     The requested URL returned error: 403
>>
>>     If someone do this for me I can try release process again.
>>
>>     Thanks,
>>     Piotr
>>
>>     pt., 12 paź 2018 o 18:20 Alex Harui <aha...@adobe.com.invalid>
>> napisał(a):
>>
>>     > I was too focused on the credentials and didn't notice that your
>> settings
>>     > didn't have HTTPS.
>>     >
>>     >         <server>
>>     >             <id>apache.releases.https</id>
>>     >             <username>aharui</username>
>>     >             <password>...</password>
>>     >         </server>
>>     >         <server>
>>     >             <id>apache.snapshots.https</id>
>>     >             <username>aharui</username>
>>     >             <password>...</password>
>>     >         </server>
>>     >
>>     > HTH,
>>     > -Alex
>>     >
>>     > On 10/12/18, 9:13 AM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com>
>> wrote:
>>     >
>>     >     I logged in without the problem. Om was on the stage where he
>> was able
>>     > to
>>     >     upload something. I hope he will respond. Maybe he had some
>> special
>>     >     settings in file.
>>     >
>>     >     Piotr
>>     >
>>     >     pt., 12 paź 2018 o 17:55 Alex Harui <aha...@adobe.com.invalid>
>>     > napisał(a):
>>     >
>>     >     > Hi Piotr,
>>     >     >
>>     >     > Yes, I have the same settings (username aharui, password is
>> my apache
>>     >     > password).  Try logging into repository.apache.org from your
>>     > browser.  I
>>     >     > don't know for sure that repository.a.o uses LDAP, it might
>> be I
>>     > just used
>>     >     > the same username and password to be lazy).
>>     >     >
>>     >     > I will also say that Infra recently changed some setting on
>>     > repository.a.o
>>     >     > and I have not tried deploying since so maybe there is some
>>     > authorization
>>     >     > step we need to do.
>>     >     >
>>     >     > HTH,
>>     >     > -Alex
>>     >     >
>>     >     > On 10/12/18, 1:40 AM, "Piotr Zarzycki" <
>> piotrzarzyck...@gmail.com>
>>     > wrote:
>>     >     >
>>     >     >     Alex, Om,
>>     >     >
>>     >     >     I'm a bit farther. I had a lot of problems on my sight
>> with gpg,
>>     > but I
>>     >     > was
>>     >     >     able to configure it properly in GitBash. I reached point
>> with
>>     >     > artifacts
>>     >     >     upload. It's failed cause it looks like my password was
>>     > incorrect. I
>>     >     > would
>>     >     >     like to make sure that I'm having similar configuration
>> as you.
>>     >     >
>>     >     >     I have login and password Maven in
>>     > c:\Users\piotr\.m2\settings.xml
>>     >     > under
>>     >     >
>>     >     >     <servers>
>>     >     >       <server>
>>     >     >     <id>apache-release</id>
>>     >     >     <username>piotrz</username>
>>     >     >     <password>mypass</password>
>>     >     >       </server>
>>     >     >       <server>
>>     >     >     <id>apache-snapshots</id>
>>     >     >     <username>piotrz</username>
>>     >     >     <password>mypass</password>
>>     >     >       </server>
>>     >     >     </servers>
>>     >     >
>>     >     >     I'm getting following results right now [1] ->
>>     >     > compiler-build-tools-1.0.0.
>>     >     >     jar. Return code is: 401, ReasonPhrase: Unauthorized.
>>     >     >     It looks like I'm having problem with authorization to
>> maven
>>     > central.
>>     >     >
>>     >     >     The question is also - Do you use apache login and
>> password ?
>>     >     >
>>     >     >     [1]
>>     >     >
>>     >
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F5OOR&amp;data=02%7C01%7Caharui%40adobe.com%7C07dbe5901e2d4ce7029e08d63061b209%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636749593496378092&amp;sdata=tUV%2B3KLFgLlLcuCbPegsTa3iUsckEFyohfp898zMOis%3D&amp;reserved=0
>>     >     >
>>     >     >     Thanks,
>>     >     >     Piotr
>>     >     >
>>     >     >     pt., 12 paź 2018 o 07:39 Alex Harui
>> <aha...@adobe.com.invalid>
>>     >     > napisał(a):
>>     >     >
>>     >     >     > Hi Piotr,
>>     >     >     >
>>     >     >     > Well, it depends.  In looking at the repos, I do not
>> see the
>>     > 0.9.4
>>     >     > tag,
>>     >     >     > which is strange since Carlos's Git GUI client is
>> updating it.
>>     >     >     >
>>     >     >     > IMO, for sure, you should update releasecandidate.xml
>> per my
>>     > earlier
>>     >     >     > email, delete the repos out of the folder you are using
>> and
>>     > see how
>>     >     > far you
>>     >     >     > get.  Maybe there is a bad tag I can't see that Maven
>> will see
>>     > and
>>     >     > fail.
>>     >     >     > Not sure what to do in that case, maybe we'll have to
>> give up
>>     > on
>>     >     > 0.9.4 as a
>>     >     >     > version and try to upgrade the version to 0.9.5.  Or
>> maybe the
>>     > tag
>>     >     > never
>>     >     >     > got pushed and deleting the repos locally will resolve
>> the
>>     > issue.
>>     >     >     >
>>     >     >     > Good luck,
>>     >     >     > -Alex
>>     >     >     >
>>     >     >     > On 10/11/18, 10:24 PM, "Piotr Zarzycki" <
>>     > piotrzarzyck...@gmail.com>
>>     >     >     > wrote:
>>     >     >     >
>>     >     >     >     Alex,
>>     >     >     >
>>     >     >     >     In the other words If I have time today I can
>> continue
>>     > with the
>>     >     >     > process? We
>>     >     >     >     end up with situation where I need to remove tag
>> and try
>>     > again
>>     >     > as I
>>     >     >     >     remember?
>>     >     >     >
>>     >     >     >     Thanks,
>>     >     >     >     Piotr
>>     >     >     >
>>     >     >     >     On Fri, Oct 12, 2018, 7:12 AM Alex Harui
>>     >     > <aha...@adobe.com.invalid>
>>     >     >     > wrote:
>>     >     >     >
>>     >     >     >     > Hi Piotr,
>>     >     >     >     >
>>     >     >     >     > I agree with your sentiments.  However, I think
>> one
>>     > problem is
>>     >     > that
>>     >     >     > the
>>     >     >     >     > revert emails are misleading.  Unlike other
>> commits, the
>>     >     > subject of a
>>     >     >     >     > revert does not show what branch was changed, so
>> I think
>>     >     > Carlos was
>>     >     >     >     > reverting things in a branch.
>>     >     >     >     >
>>     >     >     >     > That said, it is still very troublesome that his
>> Git
>>     > tools are
>>     >     >     > changing
>>     >     >     >     > the tags.  IMO, Carlos will have to stop using
>> that tool.
>>     >     >     >     >
>>     >     >     >     > -Alex
>>     >     >     >     >
>>     >     >     >     > On 10/11/18, 9:57 PM, "Piotr Zarzycki" <
>>     >     > piotrzarzyck...@gmail.com>
>>     >     >     > wrote:
>>     >     >     >     >
>>     >     >     >     >     Carlos,
>>     >     >     >     >
>>     >     >     >     >     You are expecting from people who are
>> volunteers to
>>     > do some
>>     >     >     > things in
>>     >     >     >     > one
>>     >     >     >     >     day? It's impossible to do that. I'm not
>> working on
>>     > that
>>     >     > full
>>     >     >     > time. I
>>     >     >     >     > did
>>     >     >     >     >     first finally successful step for the release.
>>     > Everything
>>     >     > was
>>     >     >     > reported
>>     >     >     >     > on
>>     >     >     >     >     this list. I had problems and didn't have
>> time to
>>     > resolve
>>     >     > it.
>>     >     >     > Alex
>>     >     >     >     > provide
>>     >     >     >     >     solution - next RM should pickup it and
>> continue
>>     > release.
>>     >     > It can
>>     >     >     > take
>>     >     >     >     > days.
>>     >     >     >     >     If you have problems you should create branch
>> from
>>     > the last
>>     >     >     > stable
>>     >     >     >     > commit.
>>     >     >     >     >     Is it problem for you ?
>>     >     >     >     >
>>     >     >     >     >     How can we now get back to the previous state
>> now?
>>     >     >     >     >
>>     >     >     >     >     Piotr
>>     >     >     >     >
>>     >     >     >     >     pt., 12 paź 2018 o 02:09 Carlos Rovira <
>>     >     > carlosrov...@apache.org>
>>     >     >     >     > napisał(a):
>>     >     >     >     >
>>     >     >     >     >     > Hi Alex,
>>     >     >     >     >     > if you check in actual develop for
>>     > "0.9.5-SNAPSHOT" and
>>     >     >     >     > "0.9.4-SNAPSHOT"
>>     >     >     >     >     > you'll see maven build compiler and typedefs
>>     >     > 0.9.5-SNAPSHOT,
>>     >     >     > but
>>     >     >     >     > when build
>>     >     >     >     >     > framework, it downloads compiler and
>> typedefs
>>     >     > 0.9.4-SNAPSHOT
>>     >     >     > since
>>     >     >     >     > the
>>     >     >     >     >     > versions in framework are not updated. This
>> is the
>>     >     > reason you
>>     >     >     > don't
>>     >     >     >     > see any
>>     >     >     >     >     > fail when building with maven. If you
>> update all
>>     > to use
>>     >     > the
>>     >     >     > same
>>     >     >     >     > number it
>>     >     >     >     >     > will fail. I recommend you as well to
>> remove royale
>>     >     > folder in
>>     >     >     > your
>>     >     >     >     > local
>>     >     >     >     >     > .m2 to see how maven generates compiler and
>>     > typedefs and
>>     >     > then
>>     >     >     >     > download
>>     >     >     >     >     > other version.
>>     >     >     >     >     >
>>     >     >     >     >     > Maybe the rest of people didn't see this
>> because
>>     > they
>>     >     > use ANT
>>     >     >     > and
>>     >     >     >     > that
>>     >     >     >     >     > build system is not affected by the release
>>     > process. But
>>     >     > I
>>     >     >     > think we
>>     >     >     >     > can't
>>     >     >     >     >     > left the failed release process without
>> revert it
>>     > for
>>     >     > days,
>>     >     >     > since we
>>     >     >     >     > are
>>     >     >     >     >     > all seeing different things.
>>     >     >     >     >     >
>>     >     >     >     >     > For example, I was able to run your MX RO
>> example
>>     > with
>>     >     > ANT,
>>     >     >     > but I
>>     >     >     >     > can make
>>     >     >     >     >     > it work with Maven, what means to me that I
>> still
>>     > can't
>>     >     > use it
>>     >     >     > since
>>     >     >     >     > my
>>     >     >     >     >     > entire project is in maven.
>>     >     >     >     >     >
>>     >     >     >     >     > I'm trying to fix this for several hours
>> now and
>>     > still
>>     >     >     > couldn't test
>>     >     >     >     > mx RO
>>     >     >     >     >     > nor working on my project...
>>     >     >     >     >     >
>>     >     >     >     >     > I'm closing for today with all messed up.
>> Tomorrow
>>     > will
>>     >     > try
>>     >     >     > again,
>>     >     >     >     > or will
>>     >     >     >     >     > need to block me in a branch to be able to
>> continue
>>     >     > working.
>>     >     >     >     >     >
>>     >     >     >     >     > Thanks
>>     >     >     >     >     >
>>     >     >     >     >     > Carlos
>>     >     >     >     >     >
>>     >     >     >     >     >
>>     >     >     >     >     >
>>     >     >     >     >     >
>>     >     >     >     >     >
>>     >     >     >     >     > El vie., 12 oct. 2018 a las 1:53, Alex Harui
>>     >     >     >     > (<aha...@adobe.com.invalid>)
>>     >     >     >     >     > escribió:
>>     >     >     >     >     >
>>     >     >     >     >     > > The 0.9.4 release branch has been cut.  I
>> have
>>     > not
>>     >     > seen any
>>     >     >     >     > problems
>>     >     >     >     >     > > reported against it, so I don't know of
>> any
>>     > reason to
>>     >     > delete
>>     >     >     > it.
>>     >     >     >     > Thus,
>>     >     >     >     >     > the
>>     >     >     >     >     > > develop branch should be at
>> 0.9.5-SNAPSHOT.
>>     >     >     >     >     > >
>>     >     >     >     >     > > I noticed you messed around with the
>> versions so
>>     > I
>>     >     > have no
>>     >     >     > idea
>>     >     >     >     > what
>>     >     >     >     >     > state
>>     >     >     >     >     > > we are in, plus I continue to see that
>> tags are
>>     > being
>>     >     >     > updated.
>>     >     >     >     > You will
>>     >     >     >     >     > > probably have to stop using your Git
>> GUI.  We
>>     > cannot
>>     >     > have
>>     >     >     > tags be
>>     >     >     >     >     > modified.
>>     >     >     >     >     > >
>>     >     >     >     >     > > -Alex
>>     >     >     >     >     > >
>>     >     >     >     >     > > On 10/11/18, 3:14 PM, "Carlos Rovira" <
>>     >     >     > carlosrov...@apache.org>
>>     >     >     >     > wrote:
>>     >     >     >     >     > >
>>     >     >     >     >     > >     Hi,
>>     >     >     >     >     > >
>>     >     >     >     >     > >     I'm a bit confused with the actual
>> state of
>>     > the
>>     >     > repo. We
>>     >     >     >     > should stay
>>     >     >     >     >     > in
>>     >     >     >     >     > >     0.9.4-SNAPSHOT? or 0.9.5-SNAPSHOT?
>>     >     >     >     >     > >     I'm building with the latest since
>> 1-2 days
>>     > but
>>     >     > removed
>>     >     >     > all
>>     >     >     >     > royale
>>     >     >     >     >     > > folder
>>     >     >     >     >     > >     with all maven artifacts and rebuild
>> from
>>     > scratch,
>>     >     > makes
>>     >     >     > me
>>     >     >     >     > have
>>     >     >     >     >     > mixed
>>     >     >     >     >     > >     versions, since some artifacts are
>>     > downloading
>>     >     > 0.9.4
>>     >     >     > instead
>>     >     >     >     > of use
>>     >     >     >     >     > > 0.9.5
>>     >     >     >     >     > >
>>     >     >     >     >     > >     Piotr, seems nobody  take the request
>> to
>>     > continue
>>     >     > with
>>     >     >     > the
>>     >     >     >     > release
>>     >     >     >     >     > for
>>     >     >     >     >     > > now,
>>     >     >     >     >     > >     so I propose to stabilize the repo.
>>     >     >     >     >     > >
>>     >     >     >     >     > >     Thoughts?
>>     >     >     >     >     > >
>>     >     >     >     >     > >     Carlos
>>     >     >     >     >     > >
>>     >     >     >     >     > >
>>     >     >     >     >     > >
>>     >     >     >     >     > >
>>     >     >     >     >     > >
>>     >     >     >     >     > >     El jue., 11 oct. 2018 a las 20:33,
>> Piotr
>>     > Zarzycki
>>     >     > (<
>>     >     >     >     >     > >     piotrzarzyck...@gmail.com>) escribió:
>>     >     >     >     >     > >
>>     >     >     >     >     > >     > Hi Alex,
>>     >     >     >     >     > >     >
>>     >     >     >     >     > >     > Unfortunately in the next couple of
>> days I
>>     > won't
>>     >     > have
>>     >     >     > time
>>     >     >     >     > for
>>     >     >     >     >     > that.
>>     >     >     >     >     > > If
>>     >     >     >     >     > >     > someone can do that feel free jump
>> into it.
>>     >     >     >     >     > >     >
>>     >     >     >     >     > >     > Piotr
>>     >     >     >     >     > >     >
>>     >     >     >     >     > >     > On Thu, Oct 11, 2018, 6:43 PM Alex
>> Harui
>>     >     >     >     > <aha...@adobe.com.invalid
>>     >     >     >     >     > >
>>     >     >     >     >     > > wrote:
>>     >     >     >     >     > >     >
>>     >     >     >     >     > >     > > After digging through the output
>> you
>>     > pasted, it
>>     >     >     > appears
>>     >     >     >     > that the
>>     >     >     >     >     > >     > > "check-empty-folder" target isn't
>> quite
>>     > right
>>     >     > and
>>     >     >     > didn't
>>     >     >     >     > catch
>>     >     >     >     >     > > that you
>>     >     >     >     >     > >     > > didn't run "maven" against an
>> empty
>>     > folder.
>>     >     >     > Although I am
>>     >     >     >     > a bit
>>     >     >     >     >     > > puzzled
>>     >     >     >     >     > >     > > why there were modified files in
>> the
>>     > working
>>     >     > copy.
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > > Maven and the scripts have some
>>     > expectation
>>     >     > that you
>>     >     >     > are
>>     >     >     >     > starting
>>     >     >     >     >     > > from
>>     >     >     >     >     > >     > the
>>     >     >     >     >     > >     > > beginning, so if Maven got far
>> enough to
>>     >     > create a
>>     >     >     > tag and
>>     >     >     >     > you
>>     >     >     >     >     > have
>>     >     >     >     >     > > to
>>     >     >     >     >     > >     > start
>>     >     >     >     >     > >     > > over, you have to remove the
>> tag.  These
>>     >     > scripts are
>>     >     >     > still
>>     >     >     >     > under
>>     >     >     >     >     > >     > > development so you should not
>> expect
>>     > that every
>>     >     >     > situation
>>     >     >     >     > has
>>     >     >     >     >     > been
>>     >     >     >     >     > >     > > accounted for.
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > > So, go delete the tag.
>> Instructions for
>>     > doing
>>     >     > so
>>     >     >     > are in
>>     >     >     >     > the
>>     >     >     >     >     > > wiki.  Maybe
>>     >     >     >     >     > >     > > figure out why those files were
>>     > modified, but
>>     >     > maybe
>>     >     >     >     > because your
>>     >     >     >     >     > > earlier
>>     >     >     >     >     > >     > > run didn't have the right gpg
>> password.
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > > Try changing the
>> check-empty-folder to
>>     > also
>>     >     > test for:
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > >         <available
>>     >     >     >     > file="${basedir}/royale-asjs/build.properties"
>>     >     >     >     >     > >     > >             type="file"
>>     >     >     >     >     > >     > >
>>     >  property="found.build.properties"
>>     >     >     > value="true"
>>     >     >     >     > />
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > > Then it should catch you on the
>> steps
>>     > where
>>     >     > you are
>>     >     >     >     > supposed to
>>     >     >     >     >     > > start by
>>     >     >     >     >     > >     > > pulling down the repos again.
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > > If you don't have time for any of
>> that,
>>     > let us
>>     >     > know
>>     >     >     > here
>>     >     >     >     > so the
>>     >     >     >     >     > > next RM
>>     >     >     >     >     > >     > > can know where to start.
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > > -Alex
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > > On 10/11/18, 2:05 AM, "Piotr
>> Zarzycki" <
>>     >     >     >     >     > piotrzarzyck...@gmail.com>
>>     >     >     >     >     > >     > wrote:
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > >     I gave up again :) It costs
>> me to
>>     > much
>>     >     > time. I
>>     >     >     > thought
>>     >     >     >     > since
>>     >     >     >     >     > > Om did
>>     >     >     >     >     > >     > so
>>     >     >     >     >     > >     > > much
>>     >     >     >     >     > >     > >     progress I will launch the
>> script
>>     > and will
>>     >     > work.
>>     >     >     > It's
>>     >     >     >     > still
>>     >     >     >     >     > > failing.
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     >
>>     >     >     >     >     > >
>>     >     >     >     >     >
>>     >     >     >     >
>>     >     >     >
>>     >     >
>>     >
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FWJ44&amp;data=02%7C01%7Caharui%40adobe.com%7C07dbe5901e2d4ce7029e08d63061b209%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636749593496378092&amp;sdata=S5WpJNtjoQD2p%2B5eZRuZlxgfAVjWf20Yf0tdYltE78o%3D&amp;reserved=0
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > >     I run first time and had
>> problem
>>     > with gpg
>>     >     >     > password -
>>     >     >     >     > just
>>     >     >     >     >     > > forgot it,
>>     >     >     >     >     > >     > > but
>>     >     >     >     >     > >     > >     run it again and type correct
>>     > password.
>>     >     > Probably
>>     >     >     > first
>>     >     >     >     > time
>>     >     >     >     >     > > this tag
>>     >     >     >     >     > >     > > was
>>     >     >     >     >     > >     > >     created and now script
>> failing cause
>>     > tag
>>     >     > exits.
>>     >     >     > Never
>>     >     >     >     > ending
>>     >     >     >     >     > > story.
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > >     I'm in that step - If someone
>> would
>>     > like
>>     >     > to try
>>     >     >     > it out
>>     >     >     >     > let me
>>     >     >     >     >     > > know
>>     >     >     >     >     > >     > and
>>     >     >     >     >     > >     > > I
>>     >     >     >     >     > >     > >     won't revert anything for now:
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > >     ant -f releasecandidate.xml
>>     >     >     > -Drelease.version="0.9.4"
>>     >     >     >     >     > >     > > -Dbrowser="c:\Program
>>     >     >     >     >     > >     > >     Files\Mozilla
>> Firefox\firefox.exe"
>>     > -Drc=1
>>     >     > maven
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > >     Thanks,
>>     >     >     >     >     > >     > >     Piotr
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > >     czw., 11 paź 2018 o 10:13
>> Piotr
>>     > Zarzycki <
>>     >     >     >     >     > > piotrzarzyck...@gmail.com>
>>     >     >     >     >     > >     > >     napisał(a):
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > >     > Hi Alex,
>>     >     >     >     >     > >     > >     >
>>     >     >     >     >     > >     > >     > This is what I'm getting
>> for git
>>     > status
>>     >     > for
>>     >     >     >     > royale-compiler
>>     >     >     >     >     > > [1]
>>     >     >     >     >     > >     > >     >
>>     >     >     >     >     > >     > >     > [1]
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     >
>>     >     >     >     >     > >
>>     >     >     >     >     >
>>     >     >     >     >
>>     >     >     >
>>     >     >
>>     >
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FYuiH&amp;data=02%7C01%7Caharui%40adobe.com%7C07dbe5901e2d4ce7029e08d63061b209%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636749593496378092&amp;sdata=JjrhMROWRzdfQD6GYn98l7FK%2FWD6n5%2Fyghl4e6dUB10%3D&amp;reserved=0
>>     >     >     >     >     > >     > >     >
>>     >     >     >     >     > >     > >     > Thanks,
>>     >     >     >     >     > >     > >     > Piotr
>>     >     >     >     >     > >     > >     >
>>     >     >     >     >     > >     > >     > śr., 10 paź 2018 o 17:50
>> Alex Harui
>>     >     >     >     >     > <aha...@adobe.com.invalid
>>     >     >     >     >     > > >
>>     >     >     >     >     > >     > > napisał(a):
>>     >     >     >     >     > >     > >     >
>>     >     >     >     >     > >     > >     >> What does 'git status'
>> return for
>>     > that
>>     >     > local
>>     >     >     > copy
>>     >     >     >     > of the
>>     >     >     >     >     > >     > > royale-compiler
>>     >     >     >     >     > >     > >     >> repo?
>>     >     >     >     >     > >     > >     >>
>>     >     >     >     >     > >     > >     >> That part of the script is
>> trying
>>     > to
>>     >     > see if
>>     >     >     >     >     > > compiler-jburg-types
>>     >     >     >     >     > >     > and
>>     >     >     >     >     > >     > >     >> compiler-build-tools
>> needed a
>>     > version
>>     >     > update
>>     >     >     > that
>>     >     >     >     > needs to
>>     >     >     >     >     > > be
>>     >     >     >     >     > >     > > pushed.
>>     >     >     >     >     > >     > >     >> Those two projects should
>> be at
>>     > 1.0.0
>>     >     > since we
>>     >     >     >     > rarely, if
>>     >     >     >     >     > > ever,
>>     >     >     >     >     > >     > > will need
>>     >     >     >     >     > >     > >     >> to modify it.  There
>> shouldn't
>>     > have been
>>     >     >     >     > modifications in
>>     >     >     >     >     > > this
>>     >     >     >     >     > >     > > release, yet
>>     >     >     >     >     > >     > >     >> Git status is reporting
>>     > modifications
>>     >     > to some
>>     >     >     >     > file.  A
>>     >     >     >     >     > test
>>     >     >     >     >     > > is
>>     >     >     >     >     > >     > done
>>     >     >     >     >     > >     > > to
>>     >     >     >     >     > >     > >     >> check for the word
>> "modified:" in
>>     > the
>>     >     > 'git
>>     >     >     > status'
>>     >     >     >     > output,
>>     >     >     >     >     > > then
>>     >     >     >     >     > >     > that
>>     >     >     >     >     > >     > >     >> attempt to push is
>> executed.
>>     > Somehow,
>>     >     > the git
>>     >     >     >     > status is
>>     >     >     >     >     > > implying
>>     >     >     >     >     > >     > >     >> modifications but the
>> files we are
>>     >     > trying to
>>     >     >     > push
>>     >     >     >     > are not
>>     >     >     >     >     > >     > modified.
>>     >     >     >     >     > >     > >     >>
>>     >     >     >     >     > >     > >     >> The solutions should not
>> require
>>     >     > reverting of
>>     >     >     > the
>>     >     >     >     > release
>>     >     >     >     >     > > branch.
>>     >     >     >     >     > >     > > It
>>     >     >     >     >     > >     > >     >> looks like you have
>> successfully
>>     >     > created a
>>     >     >     > correct
>>     >     >     >     > set of
>>     >     >     >     >     > > branches
>>     >     >     >     >     > >     > > and the
>>     >     >     >     >     > >     > >     >> steps you are running
>> start by
>>     > pulling
>>     >     > down
>>     >     >     > the
>>     >     >     >     > release
>>     >     >     >     >     > > branch.  I
>>     >     >     >     >     > >     > > didn't
>>     >     >     >     >     > >     > >     >> see any commits to the
>> release
>>     > branch
>>     >     > from the
>>     >     >     >     > scripts, so
>>     >     >     >     >     > > to
>>     >     >     >     >     > >     > > re-start, it
>>     >     >     >     >     > >     > >     >> should just be manually
>> deleting
>>     > the
>>     >     > local
>>     >     >     > copies
>>     >     >     >     > of the
>>     >     >     >     >     > > repos and
>>     >     >     >     >     > >     > > running
>>     >     >     >     >     > >     > >     >> the Ant command again after
>>     > making one
>>     >     > of the
>>     >     >     >     > changes to
>>     >     >     >     >     > >     > >     >> releasecandidate.xml I will
>>     > describe
>>     >     > below:
>>     >     >     >     >     > >     > >     >>
>>     >     >     >     >     > >     > >     >> IMO, the choices are (and
>> there
>>     > may be
>>     >     > more
>>     >     >     > choices)
>>     >     >     >     >     > >     > >     >> 1.  Figure out how to be
>> smarter
>>     > about
>>     >     > what
>>     >     >     > 'git
>>     >     >     >     > status'
>>     >     >     >     >     > > output
>>     >     >     >     >     > >     > > will say
>>     >     >     >     >     > >     > >     >> so the test works correctly
>>     >     >     >     >     > >     > >     >> 2. Set failonerror="false"
>> on the
>>     > push
>>     >     > step
>>     >     >     > and not
>>     >     >     >     > care
>>     >     >     >     >     > if
>>     >     >     >     >     > > that
>>     >     >     >     >     > >     > > push
>>     >     >     >     >     > >     > >     >> succeeds.  This is
>> slightly risky
>>     > if we
>>     >     > ever
>>     >     >     > do
>>     >     >     >     > want to
>>     >     >     >     >     > push
>>     >     >     >     >     > >     > > changes, but
>>     >     >     >     >     > >     > >     >> again, that is low
>> probability,
>>     > IMO.
>>     >     >     >     >     > >     > >     >> 3. Comment out those steps
>> since
>>     > it
>>     >     > will be
>>     >     >     > rare we
>>     >     >     >     > will
>>     >     >     >     >     > > need
>>     >     >     >     >     > >     > > them.  If
>>     >     >     >     >     > >     > >     >> we do need them some day,
>> the RM
>>     > will
>>     >     > have to
>>     >     >     >     > remember to
>>     >     >     >     >     > >     > uncomment
>>     >     >     >     >     > >     > > those
>>     >     >     >     >     > >     > >     >> steps.
>>     >     >     >     >     > >     > >     >>
>>     >     >     >     >     > >     > >     >> HTH,
>>     >     >     >     >     > >     > >     >> -Alex
>>     >     >     >     >     > >     > >     >>
>>     >     >     >     >     > >     > >     >> On 10/10/18, 2:52 AM,
>> "Piotr
>>     > Zarzycki" <
>>     >     >     >     >     > > piotrzarzyck...@gmail.com
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     > >     >> wrote:
>>     >     >     >     >     > >     > >     >>
>>     >     >     >     >     > >     > >     >>     Ok It's failed :)
>> However I
>>     > passed
>>     >     > step 3
>>     >     >     > in
>>     >     >     >     >     > > instruction. Step
>>     >     >     >     >     > >     > > 4 is
>>     >     >     >     >     > >     > >     >> failing
>>     >     >     >     >     > >     > >     >>     [1] - if someone know
>> what
>>     > could it
>>     >     > be -
>>     >     >     > I will
>>     >     >     >     > wait
>>     >     >     >     >     > > with
>>     >     >     >     >     > >     > > reverting
>>     >     >     >     >     > >     > >     >> changes.
>>     >     >     >     >     > >     > >     >>
>>     >     >     >     >     > >     > >     >>     Lines in stacktrace are
>>     > pointing in
>>     >     > ant
>>     >     >     > script
>>     >     >     >     > to
>>     >     >     >     >     > > following
>>     >     >     >     >     > >     > > targets:
>>     >     >     >     >     > >     > >     >>
>>     >     >     >     >     > >     > >     >>     Line 556:
>>     > git-commit-and-push-utils
>>     >     >     >     >     > >     > >     >>     Line 487:
>>     >     >     > git-commit-and-push-utils-if-modified
>>     >     >     >     >     > >     > >     >>     Line 473:
>>     >     >     >     >     > >     > >     >>
>>     >     >     >     >     > >     > >     >>     <exec
>> executable="${git}"
>>     >     >     > dir="${compiler}"
>>     >     >     >     >     > >     > failonerror="true" >
>>     >     >     >     >     > >     > >     >>                 <arg
>>     > value="commit" />
>>     >     >     >     >     > >     > >     >>                 <arg
>> value="-m" />
>>     >     >     >     >     > >     > >     >>                 <arg
>> value="remove
>>     >     > SNAPSHOT
>>     >     >     > from
>>     >     >     >     >     > >     > > compiler-jburg-types and
>>     >     >     >     >     > >     > >     >>     compiler-build-tools
>>     > versions" />
>>     >     >     >     >     > >     > >     >>             </exec>
>>     >     >     >     >     > >     > >     >>
>>     >     >     >     >     > >     > >     >>     [1]
>>     >     >     >     >     > >     > >     >>
>>     >     >     >     >     > >     > >
>>     >     >     >     >     > >     >
>>     >     >     >     >     > >
>>     >     >     >     >     >
>>     >     >     >     >
>>     >     >     >
>>     >     >
>>     >
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fbg5e&amp;data=02%7C01%7Caharui%40adobe.com%7C07dbe5901e2d4ce7029e08d63061b209%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636749593496378092&amp;sdata=wPbQdj%2BP5duPo9YQNx4VJzOJilNCpoMvjbkAc54Qj7Y%3D&amp;reserved=0
>>     >     >     >     >     > >     > >     >>
>>     >     >     >     >     > >     > >     >>     Thanks,
>>     >     >     >     >     > >     > >     >>     Piotr
>>     >     >     >     >     > >     > >     >>
>>     >     >     >     >     > >     > >     >>
>>     >     >     >     >     > >     > >     >>     śr., 10 paź 2018 o
>> 11:34
>>     > Carlos
>>     >     > Rovira <
>>     >     >     >     >     > >     > carlosrov...@apache.org
>>     >     >     >     >     > >     > > >
>>     >     >     >     >     > >     > >     >> napisał(a):
>>     >     >     >     >     > >     > >     >>
>>     >     >     >     >     > >     > >     >>     > Ok Piotr, good luck!
>> :)
>>     >     >     >     >     > >     > >     >>     >
>>     >     >     >     >     > >     > >     >>     > El mié., 10 oct.
>> 2018 a las
>>     >     > 10:34, Piotr
>>     >     >     >     > Zarzycki (<
>>     >     >     >     >     > >     > >     >>     >
>> piotrzarzyck...@gmail.com>)
>>     >     > escribió:
>>     >     >     >     >     > >     > >     >>     >
>>     >     >     >     >     > >     > >     >>     > > Hi Guys,
>>     >     >     >     >     > >     > >     >>     > >
>>     >     >     >     >     > >     > >     >>     > > I will try right
>> now
>>     > process
>>     >     > from my
>>     >     >     > PC. We
>>     >     >     >     > will
>>     >     >     >     >     > > see how
>>     >     >     >     >     > >     > > far I
>>     >     >     >     >     > >     > >     >> will go
>>     >     >     >     >     > >     > >     >>     > with
>>     >     >     >     >     > >     > >     >>     > > that.
>>     >     >     >     >     > >     > >     >>     > >
>>     >     >     >     >     > >     > >     >>     > > Piotr
>>     >     >     >     >     > >     > >     >>     > >
>>     >     >     >     >     > >     > >     >>     > > czw., 4 paź 2018 o
>> 22:01
>>     > Alex
>>     >     > Harui
>>     >     >     >     >     > >     > > <aha...@adobe.com.invalid>
>>     >     >     >     >     > >     > >     >>     > napisał(a):
>>     >     >     >     >     > >     > >     >>     > >
>>     >     >     >     >     > >     > >     >>     > > > Hi Om,
>>     >     >     >     >     > >     > >     >>     > > >
>>     >     >     >     >     > >     > >     >>     > > > If make_branches
>>     > succeeds,
>>     >     > then you
>>     >     >     >     > shouldn't
>>     >     >     >     >     > > need to go
>>     >     >     >     >     > >     > > back
>>     >     >     >     >     > >     > >     >> and
>>     >     >     >     >     > >     > >     >>     > delete
>>     >     >     >     >     > >     > >     >>     > > > branches and
>> tags and
>>     > run
>>     >     >     > make_branches
>>     >     >     >     > again if
>>     >     >     >     >     > > the
>>     >     >     >     >     > >     > > "maven"
>>     >     >     >     >     > >     > >     >> step
>>     >     >     >     >     > >     > >     >>     > fails.
>>     >     >     >     >     > >     > >
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Reply via email to